• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Pulse2014 1092
 

Pulse2014 1092

on

  • 31 views

 

Statistics

Views

Total Views
31
Views on SlideShare
31
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Pulse2014 1092 Pulse2014 1092 Presentation Transcript

    • RELATIONAL DATA SERVICES »Definition and use cases for System Automation‘s RDS feature
    • 02.01.2014 Dietmar Achim KnodelSEITE 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 KnodelSEITE 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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 6 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 7 ∙ RDS RELATIONAL DATA SERVICES  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 SEITE 8 02.01.2014 ∙ Dietmar Achim Knodel∙ RDS RELATIONAL DATA SERVICES
    • Basics 02.01.2014 ∙ Dietmar Achim KnodelSEITE 9 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 10 ∙ RDS RELATIONAL DATA SERVICES  SQL-like concept and language  no relational data integrity  no primary key support (insert/update/delete!)  no sort functionality (ORDER BY…)
    • Basics 02.01.2014 ∙ Dietmar Achim KnodelSEITE 11 ∙ RDS RELATIONAL DATA SERVICES  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 SEITE 12 02.01.2014 ∙ Dietmar Achim Knodel∙ RDS RELATIONAL DATA SERVICES
    • JES2 NJE Links 02.01.2014 ∙ Dietmar Achim KnodelSEITE 13 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 14 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 15 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 16 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 17 ∙ RDS RELATIONAL DATA SERVICES  excerpt from NJETABLE queried via INGRDS
    • JES2 NJE Links 02.01.2014 ∙ Dietmar Achim KnodelSEITE 18 ∙ RDS RELATIONAL DATA SERVICES  excerpt from NJETABLE queried via INGRCRDX
    • JES2 NJE Links 02.01.2014 ∙ Dietmar Achim KnodelSEITE 19 ∙ RDS RELATIONAL DATA SERVICES  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“ SEITE 20 02.01.2014 ∙ Dietmar Achim Knodel∙ RDS RELATIONAL DATA SERVICES
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 21 ∙ RDS RELATIONAL DATA SERVICES  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
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 22 ∙ RDS RELATIONAL DATA SERVICES  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
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 23 ∙ RDS RELATIONAL DATA SERVICES  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
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 24 ∙ RDS RELATIONAL DATA SERVICES  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
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 25 ∙ RDS RELATIONAL DATA SERVICES  Example for Job JCL
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 26 ∙ RDS RELATIONAL DATA SERVICES  General purpose procedure SABATCH
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 27 ∙ RDS RELATIONAL DATA SERVICES  Excerpt from APFTABLE
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 28 ∙ RDS RELATIONAL DATA SERVICES  Excerpt from SSNTABLE
    • DB2 and IMS „dynamic subsystems“ 02.01.2014 ∙ Dietmar Achim KnodelSEITE 29 ∙ RDS RELATIONAL DATA SERVICES  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 SEITE 30 02.01.2014 ∙ Dietmar Achim Knodel∙ RDS RELATIONAL DATA SERVICES
    • Future thoughts 02.01.2014 ∙ Dietmar Achim KnodelSEITE 31 ∙ RDS RELATIONAL DATA SERVICES  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 SEITE 32 02.01.2014 ∙ Dietmar Achim Knodel∙ RDS RELATIONAL DATA SERVICES
    • Conclusion 02.01.2014 ∙ Dietmar Achim KnodelSEITE 33 ∙ RDS RELATIONAL DATA SERVICES  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 02.01.2014 ∙ Dietmar Achim KnodelSEITE 34 ∙ RDS RELATIONAL DATA SERVICES