pulse2014 1092

RELATIONAL DATA SERVICES

»Definition and use cases for System Automation‘s RDS feature

02.01.2014 Dietmar Achim Knodel SEITE 2 ∙ RDS RELATIONAL DATA SERVICES

1. What are RDS 2. Setup 3. Basics 4. Use Case #1 – JES2 NJE Links 5. Use Case #2 – DB2 and IMS „dynamic subsystems“ 6. Future thoughts 7. Conclusion

1. What are RDS

SEITE 3 02.01.2014 Dietmar Achim Knodel ∙ RDS RELATIONAL DATA SERVICES

What are RDS

02.01.2014 ∙ Dietmar Achim Knodel SEITE 4 ∙ RDS RELATIONAL DATA SERVICES

services providing data access

‚lightweight‘ data services system

tables kept in NetView storage during runtime

tables can be archived using a VSAM data set

access provided via two APIs (INGRDS command or ISPF table-

editor command INGRCRDX)

initially developed to serve SA‘s automation emulators

2. Setup

SEITE 5 02.01.2014 ∙ Dietmar Achim Knodel ∙ RDS RELATIONAL DATA SERVICES

Setup


two autotasks (AUTRDSEV and AUTRDSAR) and a VSAM KSDS

(DD INGEMUGL) per system

APL definition (RDSARCH) to achieve automatic archiving

activation requires NetView to be restarted

REXX library required for ISPF table-editor (ING.SINGTREX)

INGPAUTH must be authorized TSO command (define in

IKJTSOnn parmlib member)

Setup


ISPF table editor can be RACF-protected RACF FACILITY profile <hlq>.EMULATOR.SQL, UPDATE access required

<hlq> set via advanced automation option AOF_AAO_RDS_TSO_RACFHLQ -

max. 26 bytes, can contain dots, set to #RACFHLQ# to disable RACF checking

RDS working data set required to use ISPF table editor define LRECL as long as maximum estimated sum of column definitions

RACF UPDATE access required for both TSO user and NetView

DSN set via advanced automation option AOF_AAO_RDS_TSO_DSN

3. Basics


Basics


INGRDS is NetView‘s API into RDS

comes with different keywords create/drop tables

insert/delete entries of tables

update entries of tables

import/export/copy tables

lock/unlock tables

query tables

list defined tables

Basics


SQL-like concept and language no relational data integrity

no primary key support (insert/update/delete!)

no sort functionality (ORDER BY…)

Basics


INGRCRDX is interface used from TSO/ISPF main usage to view/edit tables (INGRCRDX EDIT <tablename>)

can be used with other keywords, too

(e.g. INGRCRDX QUERY <tablename> WHERE(NUM=‘1‘) )

view/edit keywords invoke ISPF view-/edit-session

other keywords return line mode data

4. Use Case #1 – JES2 NJE Links


JES2 NJE Links


NJE links defined as type TCP

dependant from start of JES2‘s NETSRV address-space NETSRV address-space dependant on TCPIP address-space

need line-, port-, IPaddr- and socket-definitions

definitions done in several places of the JES2 init deck

would be a mess to define to automation policy no longer dynamic when done this way

JES2 NJE Links


two commands defined to maintain dynamic changes NJETBMGR to maintain and manage RDS table

NJEIPMON to monitor NJE links

two general purpose functions RDSTBCHK to check existence of a table

RDSTBDEF to define a table according to parms passed to the function

JES2 NJE Links


NJETBMGR defined as PRESTART command for NETSRV checks existence of NJETABLE, defines table if not already done

queries active JES2 parameters (nodes, lines, sockets, IPaddrs)

compares active setup with stored values in table

updates table according to queried results (add and delete)

can be called manually after dynamic changes to JES2 parameters have been

applied

JES2 NJE Links


NJEIPMON defined as link monitoring routine queries NJETABLE for links to be monitored

only acts for systems found to be active (verified via CNMEPING-command)

if link found to be active no further action determined via ‚$DNODE(num),STATUS‘ command (if STATUS contains ‚VIA‘

then connection exists)

if link inactive then $SN,SOCKET=sockname is issued

up to now no special monitoring for success of activation

JES2 NJE Links


excerpt from NJETABLE queried via INGRDS

JES2 NJE Links


excerpt from NJETABLE queried via INGRCRDX

JES2 NJE Links


NJE link monitoring not already finished

additional features to be implemented special monitoring to control activation of links

notification of other nodes when own node is being shut down

alerting if any mandatory links are missing/inactive

5. Use Case #2 – DB2 and IMS „dynamic subsystems“


DB2 and IMS „dynamic subsystems“


production data needed for test environment time by time

DB2 and IMS use production subsystems on test LPARs to

anonymize data flashcopy volumes from production varied online to test environment

production IEFSSNxx- and APF-entries must be added

may be available ONLY for duration of anonymization

anonymization almost completely automated



process needed to ‚automatically‘ add and delete APF- and SSN-

entries

anonymization process defined to job scheduler

requirement: no interference with job JCL

RDS chosen to store data for APF and SSN DB2 and IMS teams can change entries using INGRCRDX

SA does not need access rights for data sets



defined two tables SSNTABLE holds data for SETSSI command

APFTABLE holds data for SETPROG APF command

defined two service routines DYNDB2UT to service DB2 subsystems

DYNIMSUT to service IMS subsystems



type of service can be chosen TYPE=APF to handle APF entries

TYPE=SSN to handle IEFSSNxx entries

TYPE=ALL or no specification to handle both (default)

(de)activation can be chosen

IMSPlex/DB2 data sharing group must be specified identification criterion for entries in RDS tables



Example for Job JCL



General purpose procedure SABATCH



Excerpt from APFTABLE



Excerpt from SSNTABLE



scheduler jobs include JCL conditionals if any of the routines ends with RC <> 0 no further execution

no command issued if SSI already active

deactivation after job chain has finished

no security issues (APF definitions without existing data sets)

SSIs can‘t be deleted dynamically test systems have to be reIPLed to get rid of SSI definitions

6. Future thoughts


Future thoughts


APAR OA43387 for RDS significantly enhances performance of RDS functions

reduces overhead of external function calls by usage of stem-vars

change to stem-usage for all mass-update work

change input data sets to RDS tables where applicable

provide an ISPF application for structured input

6. Conclusion


Conclusion


externalization of RDS is a major point in SA 3.4

ability to store structured data no fiddling around with Cglobals

data kept when NV goes down (depending on archive intervals and technique)

complex queries within one function call

more storage consumption as tables are kept in NV storage

tables local to system – synchronization left to the user

Vielen Dank.

Finanz Informatik Technologie Service Richard-Reitzner-Allee 8 85540 Haar www.f-i-ts.de


http://www.f-i-ts.de/





pulse2014 1092

Technology

dietmar achim knodelseite

rds seite

relational data integrity

rds table njeipmon

jes2 nje links seite

line mode data

vsam data set access

system automations rds