Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Bay Area Regional User Group Meeting                                     October 18, 2012    Simplifying IMS Dynamic    Re...
Bay Area Regional User Group Meeting                                  DRD Review2     2                                 Ba...
Bay Area Regional User Group Meeting    Modifying MODBLKS Resources without DRD                                      Durin...
Bay Area Regional User Group Meeting                   Basic DRD Components6    6                            Bay Area Regi...
Bay Area Regional User Group Meeting                    Simplified DRD Setup8    8                           Bay Area Regi...
Bay Area Regional User Group MeetingSample JCL for RDDS Allocation10     10                   Bay Area Regional User Group...
Bay Area Regional User Group Meeting     DFSDFxxx – CSL Settings                                          Specify the IMSp...
Bay Area Regional User Group Meeting     DFSDFxxx – CSL Settings                                        OMPROC and SCIPROC...
Bay Area Regional User Group Meeting     CSLOIxxx - OM Initialization                                            Specify t...
Bay Area Regional User Group Meeting     CSLSIxxx - SCI Initialization                                            Specify ...
Bay Area Regional User Group Meeting     DFSDFxxx – DRD Enablement for IMS                                               A...
Bay Area Regional User Group Meeting     DFSDFxxx – DRD Enablement for IMS                                                ...
Bay Area Regional User Group Meeting          TSO SPOC & DRD Commands24     24                     Bay Area Regional User ...
Bay Area Regional User Group Meeting     Invoking TSO SPOC Application for Commands26     26                     Bay Area ...
Bay Area Regional User Group Meeting     Invoking TSO SPOC Application for Commands28     28                      Bay Area...
Bay Area Regional User Group Meeting     Updating a Resource Attribute Value30     30                     Bay Area Regiona...
Bay Area Regional User Group Meeting     Dynamically Deleting a Resource32     32                     Bay Area Regional Us...
Bay Area Regional User Group MeetingDRD Flow                                                                    z/OS 1    ...
Bay Area Regional User Group Meeting                         Best Practices for                        Migration and Usage...
Bay Area Regional User Group Meeting     Managing Data Sets During Migration     • Keep MODBLKS data set and system RDDS s...
Bay Area Regional User Group Meeting     Deleting/Updating Resources with DRD     • Resource cannot be “in use”, for examp...
Bay Area Regional User Group Meeting     Learning Type-2 Commands     • How do you find that neat table?     • Type “Equiv...
Bay Area Regional User Group Meeting Creating New Databases     • Connect other IMS resources to newly created database,  ...
Bay Area Regional User Group Meeting     Batch DRD Updates     • Change management process that requires batch updates    ...
Bay Area Regional User Group MeetingOM Audit Trail Showing DRD Activity     • Enable OM Audit Trail to track IMSplex activ...
Bay Area Regional User Group Meeting     OM Audit Trail Showing DRD Activity     • Includes type-1 and type-2 command inpu...
Bay Area Regional User Group Meeting     Contact Information     Angelique Greenhaw     415-545-2184     greenhaw@us.ibm.c...
Upcoming SlideShare
Loading in …5
×

Simplifying Dynamic Resource Definition - IMS UG October 2012 San Ramon

397 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Simplifying Dynamic Resource Definition - IMS UG October 2012 San Ramon

  1. 1. Bay Area Regional User Group Meeting October 18, 2012 Simplifying IMS Dynamic Resource Definition: A Basic Approach with Best Practices Angelique Greenhaw IMS Advanced Technical Skills IBM Corporation greenhaw@us.ibm.com © 2012 IBM Corporation Bay Area Regional User Group Meeting Agenda • DRD review • Basic components of a DRD environment • System Resource Definition Data Set (RDDS) • Common Service Layer (CSL) • DRD-enabled IMS system(s) • Single Point of Control (SPOC) • Simplified setup of DRD components • RDDS allocation • PROCLIB members • DFSDFxxx – IMS • CSLOIxxx – OM • CSLSIxxx – SCI • RDDS population • TSO SPOC application and DRD commands • Best practices for migration and usage1 1 1
  2. 2. Bay Area Regional User Group Meeting DRD Review2 2 Bay Area Regional User Group Meeting DRD Review • OBJECTIVE: Improve the availability of the IMS online environment • Allow user to dynamically define and enable MODBLKS resource definitions • Databases • Programs • Transactions • Routing Codes • Benefits • No requirement for MODBLKS SYSGEN • No requirement for IMS restart/MODBLKS online change • Limitations associated with these methods eliminated • Increased resource availability • Type-2 commands: CREATE, DELETE, UPDATE, EXPORT, IMPORT3 3 2
  3. 3. Bay Area Regional User Group Meeting Modifying MODBLKS Resources without DRD During IMS restart processing, //MODBLKSx resource definitions are loaded from the active MODBLKS library (cold start) or from the IMS log (warm/emergency OLDS restart). (stored resource definitions) WARM START COLD START EMERGENCY RESTART OLC IMS Control Region IMS Control Region RESTART Control Blocks After restart, these can only DDIRs be added, changed, or deleted through the ONLINE PDIRs CHANGE process or SMBs SYSGEN Process another RESTART (some RTCEs definitions can be updated (runtime resource definitions) by command).4 4 Bay Area Regional User Group Meeting Modifying MODBLKS Resources with DRD During IMS cold start processing, resource definitions may be IMPORTed from a Resource Definition Data Set. System RDDS Definitions can be EXPORTed OLDS to a Resource Definition Data Set. (stored resource Definitions can be dynamically created, definitions) updated, or deleted using new or WARM START enhanced Type-2 commands. EMERGENCY RESTART IMPORT IMS CONTROL REGION IMS CONTROL REGION EXPORT Control Blocks DDIRs PDIRs CREATE SMBs UPDATE DELETE RTCEs QUERY (runtime resource definitions)5 5 3
  4. 4. Bay Area Regional User Group Meeting Basic DRD Components6 6 Bay Area Regional User Group Meeting Basic DRD Environment Components • System RDDS • Data set that contains stored resource definitions for transactions, programs, databases, and routing codes • CSL • Structured Call Interface (SCI) enables communication between IMSplex address spaces • Operations Manager (OM) does command routing/response to/from IMS • IMS systems enabled for DRD to allow dynamic resource management • SPOC • Command origin point and response formatter • Interface between user and OM7 7 4
  5. 5. Bay Area Regional User Group Meeting Simplified DRD Setup8 8 Bay Area Regional User Group Meeting System RDDS • Provides a single system view of an IMSs resources and descriptors • Contains all resource and descriptor definitions for an IMS • Each IMS must define its own set of system RDDS data sets • A set of system RDDS data sets must be defined for automatic import and automatic export • BSAM data set • Minimum of 2 system RDDSs, but ideal to have 39 9 5
  6. 6. Bay Area Regional User Group MeetingSample JCL for RDDS Allocation10 10 Bay Area Regional User Group Meeting DFSDFxxx – CSL Settings11 11 6
  7. 7. Bay Area Regional User Group Meeting DFSDFxxx – CSL Settings Specify the IMSplex name with IMSPLEX=, which should match the IMSplex name setting in the OM/SCI initialization PROCLIB members12 12 Bay Area Regional User Group Meeting DFSDFxxx – CSL Settings RMENV=N activates the enhanced command environment, in which OM and SCI are automatically started during IMS initialization13 13 7
  8. 8. Bay Area Regional User Group Meeting DFSDFxxx – CSL Settings OMPROC and SCIPROC indicate which procedures will be invoked to start the OM and SCI address spaces during IMS initialization14 14 Bay Area Regional User Group Meeting Sample CSLOM Procedure OMINIT=00D specifies the suffix of the CSLOIxxx initialization member that will be read during OM startup: CSLOI00D15 15 8
  9. 9. Bay Area Regional User Group Meeting CSLOIxxx - OM Initialization Specify the IMSplex name with IMSPLEX=, which should match the IMSplex name setting in the DFSDFxxx and CSLSIxxx members16 16 Bay Area Regional User Group Meeting Sample CSLSCI Procedure SCIINIT=00D specifies the suffix of the CSLSIxxx initialization member that will be read during SCI startup: CSLSI00D17 17 9
  10. 10. Bay Area Regional User Group Meeting CSLSIxxx - SCI Initialization Specify the IMSplex name with IMSPLEX=, which should match the IMSplex name setting in the DFSDFxxx and CSLOIxxx members18 18 Bay Area Regional User Group Meeting DFSDFxxx – DRD Enablement for IMS MODBLKS=DYN indicates that DRD will be used to manage MODBLKS resource definitions instead of online change19 19 10
  11. 11. Bay Area Regional User Group Meeting DFSDFxxx – DRD Enablement for IMS AUTOEXPORT=AUTO will cause IMS to automatically export all resource and descriptor definitions to the system RDDS at every system checkpoint, including right after coldstart20 20 Bay Area Regional User Group Meeting DFSDFxxx – DRD Enablement for IMS AUTOIMPORT=AUTO will cause IMS to read resource and descriptor definitions from the system RDDS during coldstart, and from MODBLKS if RDDS is empty21 21 11
  12. 12. Bay Area Regional User Group Meeting DFSDFxxx – DRD Enablement for IMS Use RDDSDSN= to specify system RDDS names that you previously allocated22 22 Bay Area Regional User Group Meeting Populating System RDDS First Time • AUTOIMPORT=AUTO and AUTOEXPORT=AUTO will populate RDDS with definitions from MODBLKS • When coldstarting IMS for the first time after enabling DRD, its system RDDS will be empty, so IMS will autoimport definitions from MODBLKS dataset • Autoexport will occur after coldstart complete, populating the system RDDS with the definitions just read in from MODBLKS data set • At next coldstart, IMS will autoimport from the system RDDS since it now contains definitions23 23 12
  13. 13. Bay Area Regional User Group Meeting TSO SPOC & DRD Commands24 24 Bay Area Regional User Group Meeting Invoking TSO SPOC Application for Commands25 25 13
  14. 14. Bay Area Regional User Group Meeting Invoking TSO SPOC Application for Commands26 26 Bay Area Regional User Group Meeting Invoking TSO SPOC Application for Commands27 27 14
  15. 15. Bay Area Regional User Group Meeting Invoking TSO SPOC Application for Commands28 28 Bay Area Regional User Group Meeting Dynamically Creating a Program Resource29 29 15
  16. 16. Bay Area Regional User Group Meeting Updating a Resource Attribute Value30 30 Bay Area Regional User Group Meeting Updating a Resource Status31 31 16
  17. 17. Bay Area Regional User Group Meeting Dynamically Deleting a Resource32 32 Bay Area Regional User Group Meeting DRD in Action!33 33 17
  18. 18. Bay Area Regional User Group MeetingDRD Flow z/OS 1 CC = 0 IMS1 TRANA SCI CREATE TRAN NAME(TRANA) CREATE TRAN NAME(TRANA) z/OS 2IMS1 CC = 0 CC = 0IMS2 CC = 0 SPOC OperationsIMS3 CC = 0 CC = 0 Manager SCI IMS2 SCI (OM) TRANA z/OS 3 SCI CC = 0 IMS3 TRANA34 34 Bay Area Regional User Group Meeting z/OS 1 SCI enables communication between the SPOC/OM as well IMS1 as OM/IMS TRANA SCI z/OS 2IMS1 CC = 0IMS2 CC = 0 SPOC OperationsIMS3 CC = 0 Manager SCI IMS2 SCI (OM) TRANA OM routes command to each z/OS 3 IMS to create the SCI TRANA transaction resource and consolidates the IMS3 command response TRANA from each system35 35 18
  19. 19. Bay Area Regional User Group Meeting Best Practices for Migration and Usage36 36 Bay Area Regional User Group Meeting Managing Data Sets During Migration • Keep MODBLKS data set and system RDDS synchronized during migration process • Why? • Enables fallback to OLC with MODBLKS data set in case DRD needs to be disabled • How? • Keep an up-to-date MODBLKS data set that matches most recently updated system RDDS • Use Extract RDDS Contents utility to generate STAGE1 macro definitions that reflect system RDDS contents • Generate MODBLKS data set with these STAGE1 definitions that are synchronized with the system RDDS37 37 19
  20. 20. Bay Area Regional User Group Meeting Managing Data Sets During Migration • Keep MODBLKS data set and system RDDS synchronized during migration process • When? • Every time resource changes are made with DRD, keep MODBLKS data set up-to-date until migration process has been completed38 38 Bay Area Regional User Group Meeting Managing Data Sets After Migration • Data set cleanup • System RDDS (most current) used for automatic import when IMS coldstarts • Delete MODBLKS data sets once DRD migration complete with successful testing39 39 20
  21. 21. Bay Area Regional User Group Meeting Deleting/Updating Resources with DRD • Resource cannot be “in use”, for example: • Transaction with messages queued • Database referenced by a scheduled program • Recommendation for deleting or updating a resource: • QUERY the resources with SHOW(WORK) specified to confirm no work in progress exists for resource • Stop resource before attempting to delete or update40 40 Bay Area Regional User Group Meeting Learning Type-2 Commands • Become familiar with DRD commands • UPDATE and QUERY commands all have type-1 command equivalents • See the IMS Commands manual for a chart that lists type-1 commands with their type-2 DRD command equivalents • Sneak Peek:41 41 21
  22. 22. Bay Area Regional User Group Meeting Learning Type-2 Commands • How do you find that neat table? • Type “Equivalent IMS type-1 and type-2 commands” into a search engine and the first result leads to this page:42 42 Bay Area Regional User Group Meeting Creating New Databases • When adding a new database with DRD, create a corresponding DBD in ACBLIB using online change • Traditional (local) OLC • Global OLC • Member OLC • Highest availability, quiesces least amount of members • Does not support MSDBs • Otherwise: newly created database will have a NOTINIT status until this ACBLIB step is completed43 43 22
  23. 23. Bay Area Regional User Group Meeting Creating New Databases • Connect other IMS resources to newly created database, such as programs and transactions • Choose to use DRD for managing MODBLKS resources or online change • Coldstart required to switch between the two, which can impact availability44 44 Bay Area Regional User Group Meeting Resources Created using LIKE() • If updating a resource/descriptor, resources previously created from it will not automatically be updated • Use Batch SPOC utility to submit UPDATE commands against resources requiring update separately • Example: • CREATE TRANDESC NAME(TDESC1) SET(SERIAL(N)) • CREATE TRAN NAME(TRAN1, TRAN2, …) LIKE(TDESC1) • UPDATE TRANDESC NAME(TDESC1) SET(SERIAL(Y)) • UPDATE TRAN NAME(TRAN1,TRAN2) SET(SERIAL(Y)) • TRAN1, TRAN2, … will still have SERIAL=N so must update separately45 45 23
  24. 24. Bay Area Regional User Group Meeting Batch DRD Updates • Change management process that requires batch updates • Use Batch SPOC utility to submit DRD commands to IMS systems • Run in batch, commands submitted via JCL statements • Example //SPOCJOB JOB , //MSGCLASS=H,NOTIFY=&SYSUID,USER=&SYSUID //SPOC EXEC PGM=CSLUSPOC, // PARM=(IMSPLEX=PLEX1,ROUTE=IMS3,WAIT=30) //STEPLIB DD DISP=SHR,DSN=IMS.SDFSRESL //SYSPRINT DD SYSOUT=* //SYSIN DD * CREATE TRAN NAME(TRAN1,TRAN2) SET(SERIAL(Y)) UPDATE TRAN NAME(TRAN3) SET(PARLIM(65535)) /*EOF46 46 Bay Area Regional User Group Meeting Track DRD Activity with OM Audit Trail • Enable OM Audit Trail to track IMSplex activity, including resources being dynamically managed • Displays DRD input commands + responses • Includes timestamps • Example showing an updated database and program…47 47 24
  25. 25. Bay Area Regional User Group MeetingOM Audit Trail Showing DRD Activity • Enable OM Audit Trail to track IMSplex activity, including resources being dynamically managed • Tracks DRD input commands/responses + timestamps48 48 Bay Area Regional User Group Meeting OM Audit Trail Showing DRD Activity • Filter by user ID49 49 25
  26. 26. Bay Area Regional User Group Meeting OM Audit Trail Showing DRD Activity • Includes type-1 and type-2 command input/response as well as unsolicited messages (anything that goes through OM)50 50 Bay Area Regional User Group Meeting Summary • DRD review • Basic components of a DRD environment • System Resource Definition Data Set (RDDS) • Common Service Layer (CSL) • DRD-enabled IMS system(s) • Single Point of Control (SPOC) • Simplified setup of DRD components • RDDS allocation • PROCLIB members • DFSDFxxx – IMS • CSLOIxxx – OM • CSLSIxxx – SCI • RDDS population • TSO SPOC application and DRD commands • Best practices for migration and usage51 51 26
  27. 27. Bay Area Regional User Group Meeting Contact Information Angelique Greenhaw 415-545-2184 greenhaw@us.ibm.com52 52 Bay Area Regional User Group Meeting Questions?53 53 27

×