Your SlideShare is downloading. ×
0
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

IMS12 IMS DRD and the Repository - IMS UG June 2013 Sydney

549

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
549
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Dynamic Resource Definition with the IMS Repository June 2013 Alison Coughtrie - European IMS Architecture Team
  • 2. Important Disclaimer © Copyright IBM Corporation 2013. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. THE INFORMATION ON NEW PRODUCTS IS FOR INFORMATIONAL PURPOSES ONLY AND MAY NOT BE INCORPORATED INTO ANY CONTRACT. THE INFORMATION ON ANY NEW PRODUCTS IS NOT A COMMITMENT, PROMISE, OR LEGAL OBLIGATION TO DELIVER ANY MATERIAL, CODE OR FUNCTIONALITY. THE DEVELOPMENT, RELEASE, AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR OUR PRODUCTS REMAINS AT THE SOLE DISCRETION OF IBM. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY © 2013 IBM Corporation1 FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE. IBM, the IBM logo, ibm.com, Information Management, IMS, and z/OS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at ibm.com/legal/copytrade.shtml Other company, product, or service names may be trademarks or service marks of others.
  • 3. • OBJECTIVE: Improve the availability of the IMS online environment • Allow user to dynamically define and enable MODBLKS resource definitions – Databases – Programs – Transactions – Fast Path Routing Codes Dynamic Resource Definition (DRD) Review © 2013 IBM Corporation2 – Fast Path 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, QUERY, EXPORT, IMPORT
  • 4. Modifying MODBLKS Resources without DRD //MODBLKSx During IMS restart processing, resource definitions are loaded from the active MODBLKS library (cold start) or from the IMS log (warm/emergency restart). OLDS WARM START DATABASE APPLCTN TRANSACT RTCODE Log Records DDIRs PDIRs SMBs RCTEs © 2013 IBM Corporation3 Control Blocks DDIRs PDIRs SMBs RCTEs COLD START or OLC OLC SYSGEN Process IMS Control Region After restart, these can only be added, changed, or deleted through the ONLINE CHANGE process or another RESTART (some definitions can be updated by command). WARM START EMERGENCY RESTART RESTART RTCODE Command and CHKPT Logging
  • 5. Modifying MODBLKS Resources with DRD and RDDS DATABASE APPLCTN TRANSACT “System” RDDS During IMS cold start processing, resource definitions may be IMPORTed from a Resource Definition Data Set (RDDS). Definitions can be dynamically created, updated, or deleted using new or enhanced Type-2 commands. Definitions can be EXPORTed to a Resource Definition Data Set. Definitions can be IMPORTed from a Resource Definition Data Set. COLD START OLDS WARM START or /ERE (Stored Resource Definitions) Log Records DDIRs PDIRs SMBs RCTEs © 2013 IBM Corporation4 TRANSACT RTCODE Control Blocks DDIRs PDIRs SMBs RCTEs COLD START (AUTOIMPORT) or IMPORT command AUTOEXPORT or EXPORT command CREATE UPDATE DELETE QUERY IMPORT EXPORT WARM START or /ERE (Runtime Resource Definitions) IMS CONTROL REGION Command and CHKPT Logging DATABASE APPLCTN TRANSACT RTCODE Non-System RDDS EXPORT & IMPORT commands
  • 6. Commands Used in Dynamic Resource Definition • Type-2 commands entered through Operations Manager (OM) interface to – QUERY, CREATE, UPDATE, DELETE, IMPORT or EXPORT resources and descriptors • A descriptor is a model for defining (creating) a resource or another descriptor – Establishes defaults for attributes not set in the CREATE command Command Short Form Purpose © 2013 IBM Corporation5 Command Short Form Purpose CREATE CRE Create resource or descriptor definition DELETE DEL Delete resource or descriptor definition UPDATE UPD Update attributes of resource or descriptor definition Update status of resource QUERY QRY Query attributes of resource or descriptor definition Query status of resource IMPORT IMP Import resource or descriptor definitions from RDDS or Repository EXPORT EXP Export resource or descriptor definitions to RDDS or Repository
  • 7. General Format for Command Entry and Response • Commands must be entered through the OM interface – OM will consolidate responses from all IMSs in IMSplex • If any IMS returns a non-zero return and reason code to OM – OM returns a non-zero return and reason code to SPOC, plus a completion code for each resource • If CC not 0, CCText explains reason – SPOC displays completion code and text for each IMS and resource © 2013 IBM Corporation6 – SPOC displays completion code and text for each IMS and resource • Sample command input and response – PGM2 created even though command failed for PGM1 CREATE PGM NAME(PGM1,PGM2) SET(SCHDTYPE(SERIAL),...) PgmName MbrName CC CCText PGM1 IMS1 11 RESOURCE ALREADY EXISTS PGM2 IMS1 0
  • 8. General Format for Command Entry and Response • In some cases, error text will also be returned • “IMS Commands” publication documents, for each command – Return and reason codes – CC (Completion Codes) – CCText (meaning of completion code – if non-zero) – ErrorText (further explanation – if applicable) • © 2013 IBM Corporation7 • Sample command input and response – PSB for ACCTUPDT references ACCTMSTR DB DELETE DB NAME(ACCTMSTR,CUSTMSTR) DBName MbrName CC CCText ErrorText ACCTMSTR IMS1 11 REFERENCED BY PROGRAM ACCTUPDT CUSTMSTR IMS1 0
  • 9. DRD Descriptors • A model (template) for creating a resource or another descriptor – Establishes values for attributes not explicitly SET in the CREATE command • As with a resource, every attribute has a value – Used as an alternative to an actual resource in CREATE ….. LIKE …. • IMS-defined descriptors – Provided with the IMS product • DFSDSDB1(for Database), DFSDSPG1 (for Program), DFSDSTR1 (for Transaction), DBFDSRT1 (for FP Routing Code) – Cannot be deleted or updated © 2013 IBM Corporation8 – Cannot be deleted or updated – Ensures there is always at least one descriptor of each type • User-defined descriptors – Created by the user • Default descriptors – Each resource type will have one, and only one, current default descriptor • Can be the IMS-defined or a user-defined descriptor – Used when a CREATE does NOT specify “LIKE”
  • 10. Creating Resources Overview • Example based on Transactions TRAND Atrib1 = ……. Atrib2 = ……. Atrib3 = ……. etc. TRANC Atrib1 = ……. Atrib2 = ……. Atrib3 = ……. etc. TRANB Atrib1 = ……. Atrib2 = ……. Atrib3 = ……. TRANA Atrib1 = ……. Atrib2 = ……. MyTrDS2 Atrib1 = ……. Atrib2 = ……. Atrib3 = ……. etc. MyTrDS1 Atrib1 = ……. Atrib2 = ……. Atrib3 = ……. DFSDSTR1 (IBM provided) Atrib1 = ……. Atrib2 = ……. TRANSACTIONS (SMBs) TRANSACTION DESCRIPTORS © 2013 IBM Corporation9 etc.Atrib3 = ……. etc. Atrib2 = ……. Atrib3 = ……. etc. etc.Atrib3 = ……. etc. CREATE TRAN NAME(TRANX) LIKE (RSC(TRANA)) SET (Atrib1=xyz, Atrib3=pqr) CREATE TRAN NAME(TRANY) LIKE (DESC(MyTrDS2)) SET (Atrib1=wxy, Atrib4=rst) CREATE TRAN NAME(TRANZ) SET (Atrib3=jkl) One descriptor will be defined as the “default”
  • 11. Invoking TSO SPOC Application for DRD Commands DFSAPPL IMS Application Menu Command ===> Select an application and press Enter. 1 Single Point of Control (SPOC) 2 Manage resources 3 Reserved for future use 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) © 2013 IBM Corporation10 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) 6 Installation Verification Program (IVP) 7 IVP Export Utility (IVPEX) 8 IPCS with IMS Dump Formatter (IPCS) 9 Abend Search and Notification (ASN) To exit the application, press F3.
  • 12. Invoking TSO SPOC Application for DRD Commands … © 2013 IBM Corporation11
  • 13. Dynamically Creating a Program Resource © 2013 IBM Corporation12
  • 14. Manage Resources Interface • Manage Resources User Interface – Subfunction of the ISPF SPOC program • Screens have same look and feel • Greatly reduces the user’s need to - – Format CREATE, DELETE, UPDATE, and QUERY commands – Know names and valid values for attributes • © 2013 IBM Corporation13 • Provides two views – List view for less skilled operators • Requires more screens (in most cases) – Command syntax view for more skilled operators • Generally requires a single screen
  • 15. Invoking the Manage Resources Interface • DRD Resources can also be managed through the TSO SPOC “Manage Resources” panels DFSAPPL IMS Application Menu Command ===> Select an application and press Enter. 1 Single Point of Control (SPOC) © 2013 IBM Corporation14 1 Single Point of Control (SPOC) 2 Manage resources 3 Reserved for future use 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) 6 Installation Verification Program (IVP) 7 IVP Export Utility (IVPEX) 8 IPCS with IMS Dump Formatter (IPCS) 9 Abend Search and Notification (ASN) To exit the application, press F3. Select “Manage Resources”
  • 16. Manage Resources List View • Example using CREATE TRAN File Action Manage resources SPOC View Options Help IMS Create Transactions Command ===> Plex . . Route . . Wait . . Press Enter to continue More: + * NAME Transaction name . . TESTRAN SET “LIST” View – requires more screens in most cases © 2013 IBM Corporation15 AOCMD AOI command option . . . . . . . N CMD,N,Tran,Y CLASS Class. . . . . . . . . . . . . . 1 1-999 CMTMODE Commit mode. . . . . . . . . . . SNGL Sngl, Mult CONV Conversational . . . . . . . . . N Y, N DCLWA Log write-ahead option . . . . . Y Y, N DIRROUTE MSC direct routing option. . . . N Y, N EDITRTN Input edit routine . . . . . . . EDITUC Edit to uppercase. . . . . . . . Y Y, N EMHBSZ EMH buffer size. . . . . . . . . 12-30720
  • 17. Manage Resources Command Syntax View File Action Manage resources SPOC View Options Help IMS Create Transactions Top of data Command ===> Plex . . Route . . Wait . . Press Enter to continue CREATE TRAN NAME( TESTRAN ) SET( AOCMD( N ) CLASS( 1 ) CMTMODE( SNGL ) CONV( N ) DCLWA( Y ) “COMMAND SYNTAX View” – one screen • Example using CREATE TRAN © 2013 IBM Corporation16 SET( AOCMD( N ) CLASS( 1 ) CMTMODE( SNGL ) CONV( N ) DCLWA( Y ) DIRROUTE( N ) EDITRTN( ) EDITUC( Y ) EMHBSZ( ) FP( N ) INQ( N ) LCT( 65535 ) LPRI( 1 ) MAXRGN( 0 ) MSGTYPE( MULTSEG ) MSNAME( ) NPRI( 1 ) PARLIM( 65535 ) PGM( ) PLCT( 65535 ) PLCTTIME( 6553500 ) RECOVER( Y ) REMOTE( N ) RESP( N ) SEGNO( 0 ) SEGSZ( 0 ) SERIAL( N ) SIDL( 0 ) SIDR( 0 ) SPASZ( ) SPATRUNC( ) TRANSTAT( N ) WFI( N )) F1=Help F3=Exit F4=Showlog F6=Expand F9=Retrieve
  • 18. Batch SPOC DRD Updates • For Change management process that requires batch updates – Use Batch SPOC utility to submit DRD commands to IMS systems • Run in batch, commands submitted via SYSIN statements – Example //SPOCJOB JOB , //MSGCLASS=H,NOTIFY=&SYSUID,USER=&SYSUID //SPOC EXEC PGM=CSLUSPOC, © 2013 IBM Corporation17 // PARM=('IMSPLEX=PLEX1,ROUTE=(IM1A,IM2A),WAIT=5,F=BYCOL') //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)) /*EOF
  • 19. Recoverability • Resources and descriptors – Exist for the life of IMS or until deleted – Are recovered from logs across warm and emergency restart • Log records (x’22’) are written when resources and descriptors are created, updated, or deleted • Resource and descriptor definitions are logged at checkpoint time © 2013 IBM Corporation18 • Resource and descriptor definitions are logged at checkpoint time – Are lost across cold start unless ... • Previously exported to RDDS < and then > • Imported during cold start
  • 20. Autoexport and RDDS • Allows all resource and descriptor definitions for an IMS to be exported to a system RDDS data set automatically at checkpoint time (simple or shutdown) • Enabling Automatic Export is optional • Export is only done if one or more definitions have been added, © 2013 IBM Corporation19 • Export is only done if one or more definitions have been added, changed or deleted since the last checkpoint – Overwrites entire contents of oldest system RDDS with IMS’s definitions • Automatic Export is always done following the restart checkpoint
  • 21. System Resource Definition Datasets • Defined in the <SECTION=DYNAMIC_RESOURCES> section of DFSDFxxx PROCLIB member • A set of BSAM data sets that contain MODBLKS resource and descriptor definitions for one IMS – None or a minimum of 2 System RDDSs must be defined • 3 is recommended © 2013 IBM Corporation20 • 3 is recommended – Each IMS has its own set of System RDDSs • Header record contains IMSID and last update timestamp – Dynamically allocated by IMS when needed • Opened one at a time • Closed immediately after use – Can easily be scratched and reallocated while IMS online
  • 22. DFSDFxxx Sample for DRD with RDDS <SECTION=DYNAMIC_RESOURCES> DCLWA=Y /* Log write-ahead */ RDDSDSN=(IMS10.RDDSDSN1,IMS10.RDDSDSN2,IMS10.RDDSDSN3,IMS10.RDDSDSN4), AUTOEXPORT=AUTO, AUTOIMPORT=AUTO, IMPORTERR=ABORT, RDDSERR=ABORT <SECTION=DIAGNOSTICS_STATISTICS> TRANSTAT=Y, /* Transaction Level Statistics */ IASNPROC=DFSIASN0, /* Abend Search & Notification PROC */ MSG0826=SUPPBLDL, /*Message suppression */ MSG0830=SUPPBLDL /*Message Suppression */ <SECTION=SHARED_QUEUES> CQS=CQSCW1, /* CQS name */ CQSSSN=CQS1, /* CQS subsystem name */ © 2013 IBM Corporation21 CQSSSN=CQS1, /* CQS subsystem name */ EMHQ=IMSEMHQ01, /* EMHQ structure name */ MSGQ=IMSMSGQ01, /* MSGQ structure name */ SQGROUP=GRUP1 /* XCF group name */ <SECTION=COMMON_SERVICE_LAYER> CMDSEC=N, /* No cmd authorization checking */ IMSPLEX=PLEX1, /* IMSplex name */ OLC=GLOBAL, /* GLOBAL online change */ OLCSTAT=IMSTESTS.IMS01.OLCSTAT, /* OLCSTAT data set name */ MODBLKS=DYN, /* DRD ENABLED; OLC DISABLED */ PLEXPARM=(), /* GLOBAL resource status */ UOM=MTO /* Unsolicited output message support */ <SECTION=USER_EXITS> EXITDEF=(TYPE=RESTART, /* Restart User Exit */ EXITS=(UEXIT1,UEXIT2,UEXIT3)) /* Exit list */
  • 23. “Non-System” Resource Definition data sets (RDDSs) • Can be shared between IMSs • May contain a subset of an IMS’s resource and descriptor definitions • Referred to explicitly on EXPORT and IMPORT commands – EXPORT DEFN TARGET(RDDS) TYPE() NAME() RDDSDSN(TEST1.NONSYSTEM.RDDS1) OPTION() © 2013 IBM Corporation22
  • 24. DRD Utilities • Set of offline utilities to perform the following DRD-related functions: DFSURCL0 Existing RDDS DFSURCP0DFSURCM0 MODBLKS IMS Log DFSURST0 SYSGEN DFSURDD0 RDDS © 2013 IBM Corporation23 • Utilities can be invoked through the Manage Resources panels RDDSRDDS RDDS DFSURCL0DFSURCP0DFSURCM0 RDDS DFSURST0 •Stage 1 Macro statements •Type 2 CREATE commands •QUERY DFSURDD0
  • 25. DRD and the Repository • In IMS 12, the resource and descriptor definitions for Dynamic Resource Definition (DRD) can be stored in an IMS repository – Contains resource definitions for programs/transactions/databases/FP routing codes & descriptors – Called the IMSRSC (IMS resource) definition repository © 2013 IBM Corporation24 – Called the IMSRSC (IMS resource) definition repository – Provides an alternative to using RDDSs (resource definition data sets) for DRD • Replaces one or more sets of RDDSs in an IMSplex with a single repository
  • 26. IMS Repository Function Usage … • In IMS 12, the resource and descriptor definitions for Dynamic Resource Definition (DRD) can be stored in an IMS repository (cont’d) – Eliminates the need to manually coordinate and manage separate RDDSs per IMS across a multiple-IMS IMSplex – Provides an alternative to using MODBLKS with SYSGEN and online change © 2013 IBM Corporation25 change – Considered a strategic alternative to the RDDS • IMS 12 can retrieve the stored resource definitions from the IMSRSC repository to dynamically generate runtime resources for DRD
  • 27. Some Possible Types of DRD Configuration in IMS 12 • The IMS 10/11 option – only RDDS (system RDDS and optionally Non- system RDDS) – AUTOEXPORT will update the system RDDS at system checkpoint following commands that have been used to change the runtime resources • Using Repository with no RDDS – There is no such feature as AUTOEXPORT to the Repository • Repository content is determined by EXPORT and DELETE commands • © 2013 IBM Corporation26 • Using Repository and RDDS with AUTOEXPORT to RDDS – Might use the RDDS to hold “temporary updates” while AUTOIMPORT from the Repository at a cold start will always restore to a known initial state • Using Repository with Non-system RDDS only – Allows complete control of copying resources between systems that don’t share a Repository (e.g. test to production)
  • 28. Modifying MODBLKS Resources with DRD & Repository IMS Repository During IMS cold start processing, resource definitions may be IMPORTed from the IMS Repository Definitions can be dynamically created, updated, or deleted using Type-2 commands. Definitions can be EXPORTed to the Repository. Definitions can be IMPORTed from the Repository. Definitions can be deleted & queried in the Repository COLD START WARM START or /ERE Log Records DDIRs PDIRs SMBs RCTEs OLDS Known as “Stored” Resource Definitions DATABASE APPLCTN TRANSACT RTCODE © 2013 IBM Corporation27 Control Blocks DDIRs PDIRs SMBs RCTEs COLD START (AUTOIMPORT) or IMPORT command EXPORT & Delete DEFN command CREATE UPDATE DELETE QUERY IMPORT EXPORT WARM START or /ERE Known as “Runtime” Resource Definitions IMS CONTROL REGION Command and CHKPT Logging DATABASE APPLCTN TRANSACT RTCODE Non System RDDS EXPORT & IMPORT commands System RDDS Auto EXPORT & Export, Import commandsDATABASE APPLCTN TRANSACT RTCODE
  • 29. Resource Definitions • DRD Resources in IMS’s memory, i.e. those being used by the online IMS system, are referred to as - – Runtime Resources or Runtime Resource Definitions • DRD Resources saved in a Repository or RDDS are referred to as - – Stored Resources or Stored Resource Definitions • EXPORT command copies Runtime Resources to Stored Resources orororor © 2013 IBM Corporation28 – Can EXPORT to RDDS orororor Repository – Executed on one IMS, it can specify that resource definitions exported to the Repository are to apply to multiple named IMS systems • But doesn’t change any runtime resource definitions • IMPORT command copies Stored Resources to Runtime Resources – Executed on one IMS, it can specify that stored resource definitions from the Repository are to become runtime resource definitions in multiple IMS systems
  • 30. Value of the IMS 12 repository for DRD • Full support for populating, managing, storing, sharing, and retrieving a consistent set of DRD stored resource definitions for multiple-IMS IMSplexes and single-IMS IMSplexes in a single place • Provides improved availability – Repository can be enabled/disabled without an IMS outage via command © 2013 IBM Corporation29 command – Duplexing of data plus spare capability improves data availability • Provides single source consistency for DRD stored resource definitions – No need for multiple sets of RDDSs in a multiple-IMS IMSplex – No need for coordinating multiple sets of RDDSs in a multiple-IMS IMSplex – Repository architecture controls consistency and integrity of data
  • 31. Value of the IMS 12 Repository for DRD • Provides improved functionality and flexibility for managing resources across an IMSplex – Generic resource definition plus IMS-specific resource definitions – EXPORT process is a single unit or work for entire IMSplex, all succeeds or all fails – EXPORT process controlled by user (no AUTOEXPORT) • Can select CHANGESONLY or by time periods © 2013 IBM Corporation30 • Can select CHANGESONLY or by time periods – DELETE of stored resource definitions controlled by user – Can UPDATE an existing runtime definition via IMPORT – EXPORT reflected in all IMSs in an IMSplex, whether up or down at the time – QUERY will display stored resource definitions from repository – DFSINSX0 (Destination Creation Exit) supports export to repository
  • 32. • Provides support for both test and production environments – Repository Server can include data from different IMSplexes though one per IMSplex recommended – Multiple IMSRSC repositories can exist within one Repository Server though one per Repository Server recommended – Migration and fallback utilities available based on RDDSs Value of the IMS 12 Repository for DRD © 2013 IBM Corporation31 – Migration and fallback utilities available based on RDDSs • Previously available DRD RDDS utilities can be used in backup/recovery scenarios – IVP available to assist with installation of repository – Supported by TSO SPOC Manage Resources application
  • 33. • Provides security capabilities for auditing and compliance – Full support for RACF (SAF) interfaces – Repository audit log (optional) • Includes both online and batch access – OM type-2 repository commands optionally found in OM Audit Trail • Value of the IMS 12 Repository for DRD © 2013 IBM Corporation32 • Provides comprehensive set of repository administration tools – Includes batch utilities and command interfaces for repository management • Can be performed when IMS is down • A strategic IMS architectural direction – Based upon BPE, CSL, IMSplex architecture
  • 34. IMS Repository Function Components • Repository Server (RS) Address Space/s • Repositories – Catalog repository – IMSRSC repository • Common Service Layer (CSL) IMSplex configuration consisting of – Operations Manager (OM) – Resource Manager (RM) © 2013 IBM Corporation33 – Resource Manager (RM) – Structured Call Interface (SCI) – SPOC for entering type-2 commands – Optional resource structure with CQS address space • Batch utilities – Batch ADMIN utility – RDDS to / from repository utilities
  • 35. IMS Repository Function Components Operations Manager (OM) Structured Call Interface Resource Manager (RM) Repository Server SCI SCI SCI X C F AuditLog CSLURP10 / CSLURP20 XC F RDDS RS Catalog Repository “Stored” Definitions SPOC Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 OM Audit Log Repository Server XC © 2013 IBM Corporation34 IMS Control Region Server (RS) SCI SCI XCF Batch ADMIN Utility (FRPBATCH) Repository Server Commands (z/OS Modify) AuditLog X C F F IMSRSC Repository “Runtime” Definitions z/OS Modify Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional Empty Server (RS) XC F
  • 36. Sample IMS Configuration • zTec Montpellier – 2 IMS Version 12 data sharing, shared queue systems SPOCSPOC RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member IMSRSC Repository Primary/Copy1 data sets Secondary/Copy 2 data sets I1 M1 M2 I2 Spare data sets “Stored” Definitions SPARE Repository Server (RS) XC F Repository Server (RS) XC F © 2013 IBM Corporation35 IMB1 Control Region S C I S C I CQS SCI SCI Communications SCI Operations Manager (OM) SCI Structured Call Interface (SCI) SCI Resource Manager (RM) Resource Structure CF IMB2 Control Region S C I S C I CQS SCI Communications SCI Structured Call Interface (SCI) SCI Operations Manager (OM) data sets Index/Member data sets Index/Member data sets Index/Member X C F X C F SCI Resource Manager (RM) RDDS RDDS
  • 37. Multi-IMS Configuration SCI SPOCSPOC Operations Manager Structured Call Resource Manager Resource Structured Call Operations RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member IMSRSC Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional SPARE Repository Server (RS) Audit Log XC F Repository Server (RS) XC F X © 2013 IBM Corporation36 IMS Control Region S C I S C I CQS SCI Communications SCI Manager (OM) SCI Interface (SCI) SCI Manager (RM) Resource CF IMS Control Region S C I S C I CQS SCI Communications SCI Resource Manager (RM) SCI Call Interface (SCI) SCI Operations Manager (OM) X C F X C F
  • 38. IMS Repository Function Components … • Repository Server (RS) – New BPE-based address space • Access to RS is managed by the Resource Manager (RM) • RS is NOT a CSL address space – Two types • Master Repository Server – Single instance – Resource Manager (RM) Repository Server (RS) SCI X C F AuditLog XC F RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Repository Server (RS) XC F © 2013 IBM Corporation37 – Manages access to repository data sets – First RS address space to access repository • Subordinate Repository Server – One or more instances – Used if master Repository Server goes down – Optional but recommended – User must start the Repository Server address space/s Batch ADMIN Utility (FRPBATCH) Repository Server Commands (z/OS Modify) AuditLog X C F IMSRSC Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional (RS)
  • 39. IMS Repository Function Components … • Repository data sets – Multiple sets of VSAM KSDS data sets – Each set composed of • Repository index data set • Repository member data set • Each of these has a primary and secondary data set (duplexed) – Optional spare set (third) can be defined Repository Server (RS) AuditLog XC F RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 © 2013 IBM Corporation38 – Optional spare set (third) can be defined – Two types of repository data sets • Catalog repository data sets • IMS repository data sets AuditLog IMSRSC Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional
  • 40. IMS Repository Function Components … • Catalog repository (RS catalog data sets) – Required per Repository Server • Must be allocated before RS can startup – Manages the Repository Server (RS) functions – Manages information about IMS repository data sets – Composed of two pairs of data sets (no spare capability) • Primary index data set and primary member data set (required) © 2013 IBM Corporation39 • Primary index data set and primary member data set (required) • Secondary index data set and secondary member data set (required) RS Catalog data sets Primary Member and Index data sets Secondary Member and Index data sets I1 M1 I2 M2
  • 41. IMS Repository Function Components … • IMSRSC repository … • Composed of up to three pairs of data sets – Primary index data set and primary member data set (required) (COPY1) – Secondary index data set and secondary member data set (required) (COPY2) – Spare index data set and spare member data set (optional) (SPARE) © 2013 IBM Corporation40 IMSRSC Repository data sets Primary Member and Index data sets Secondary Member and Index data sets Optional Spare Member & Index Stored Definitions Stored Definitions Empty COPY1 COPY2 SPARE
  • 42. IMS Repository Function Components … • IMSRSC repository data sets contain • Stored resource definitions for DRD resources for one or more DRD- enabled IMS systems – Programs / transactions / databases / FP routing codes and descriptors • Resource lists for each IMS – Contains resource names and resource types that can be © 2013 IBM Corporation41 processed by an IMS system • IMS Change lists – new in IMS 13 – Contain resource and descriptor names that were imported using the IMPORT SCOPE(ALL) command when an IMS was down – Behind the scenes, a separate IMS change list is actually created for each resource/descriptor type – Applied at next warm/emergency restart after IMS log is processed – internal import is done – IMS change list is deleted at the end of warm/emergency restart and at end of coldstart
  • 43. IMS Repository Function Components … • A Common Service Layer (CSL) IMSplex configuration consisting of – Operations Manager (OM) • Used for new/modified type-2 commands for repository functions – Resource Manager (RM) • Used for managing the new Repository Server (RS) address space • online access © 2013 IBM Corporation42 • All online access to Repository Server is through RM address space • New type-2 commands for managing the Repository Server – UPDATE RM – enable or disable RM to use IMSRSC dynamically – QUERY RM – info. about IMSRSC repositories managed – UPDATE IMS – to enable IMS to use IMSRSC dynamically • RM is enabled to the repository by specifying a Repository Section in the RM initialization member (CSLRIxxx) and with the UPDATE RM command
  • 44. IMS Repository Function Components … • Resource Manager … – Optionally, a resource structure in a Coupling Facility • Used for repository name and repository type consistency if present • Managed by a Common Queue Server (CQS) address space • Multiple RMs in an IMSplex require that a resource structure exists – Structured Call Interface (SCI) © 2013 IBM Corporation43 – Structured Call Interface (SCI) • Used for communications within the CSL • Not used for communications between RM and the RS – uses XCF • RS is not considered a CSL manager – SPOC (single point of control) for entering type-2 commands • Manage Resources panels support repository – Can be a single-IMS IMSplex or a multi-IMS IMSplex
  • 45. IMS Repository Function Components … • Batch utilities – Batch ADMIN utility (FRPBATCH) • Commands for managing IMSRSC repositories – Functions such as ADDing a new IMSRSC repository, LISTing the characteristics of an IMSRSC repository, STARTing or STOPping an IMSRSC repository Resource Manager (RM) Repository Server (RS) SCI X C F AuditLog CSLURP10 / CSLURP20 XC F RDDS RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 © 2013 IBM Corporation44 IMSRSC repository – RDDS to / from repository utilities (Batch RM utilities) • RDDS to Repository Utility (CSLURP10) – For migration • Repository to RDDS Utility (CSLURP20) – For fallback/backup (RS) Batch ADMIN Utility (FRPBATCH) Repository Server Commands (z/OS Modify) AuditLog X C F F IMSRSC Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional
  • 46. IMS Repository Function Components … • Audit Log –Optional – z/OS Log stream – Examples of events that create audit log entries • Security errors • Registration and connection events • Access to repository Repository Server (RS) AuditLog XC F RS Catalog Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 © 2013 IBM Corporation45 • Access to repository – Can print audit log records with DFSERA10 (RS) AuditLog IMSRSC Repository Primary/Copy1 data sets Index/Member Secondary/Copy 2 data sets Index/Member I1 M1 M2 I2 Spare data sets Index/Member “Stored” Definitions Optional
  • 47. IMS Repository Setup • Repository Server – Create RS Catalog and IMSRSC repository data sets – Set up BPE configuration member (optional) – Set up FRPCFG configuration member • Repository Server settings • Audit log definitions • Define security © 2013 IBM Corporation46 • Define security
  • 48. IMS Repository Setup - FRPCFG configuration member © 2013 IBM Corporation47
  • 49. IMS Repository Setup – IMS CSLRIxxx – Set up the CSL • RM needs new CSLRIxxx repository section © 2013 IBM Corporation48
  • 50. IMS Repository Setup – IMS DFSCGxxx © 2013 IBM Corporation49
  • 51. IMS Repository Setup – IMS DFSDFxxx © 2013 IBM Corporation50
  • 52. IMS Repository Setup – Start the master Repository Server – Start subordinate Repository Servers (optional) © 2013 IBM Corporation51
  • 53. Enabling an IMSRSC repository for DRD • Define security for IMS repository • Define the IMSRSC repository to the Repository Server • Start the IMSRSC repository • Cold start IMS (to enable DRD) • Populate the IMSRSC repository © 2013 IBM Corporation52 – If IMS is up, populate using the EXPORT DEFN TARGET(REPO) command to add DRD stored resource definitions to the IMSRSC repository
  • 54. Repository Startup Sequence Guidelines • Recommended start up sequence with all CSL components – SCI – OM – CQS – RS (Master) – RS (Subordinate) © 2013 IBM Corporation53 – RM – IMS • DBRC – SPOC – ODBM – IMS Connect
  • 55. IMSRSC Repository is Active/Populated • Begin to use type-2 DRD repository commands that access/update stored resource definitions in the repository EXPORT DEFN TARGET(REPO) TYPE(ALL) NAME(*) IMPORT DEFN SOURCE(REPO) TYPE(DB) NAME(DBABC) OPTION(UPDATE) © 2013 IBM Corporation54 DELETE DEFN TARGET(REPO) TYPE(DB) NAME(DBXYZ) QUERY IMS QUERY DB/PGM/TRAN/RTC SHOW(DEFN)
  • 56. Query Command Enhancements Example • Now displays: – Stored IMS resource definitions in the repository – Runtime IMS-specific resource definitions – The IMS systems that have the specified resources defined © 2013 IBM Corporation55
  • 57. Installation Verification Program (IVP) • IVP has been enhanced to include sample JCL to create the Repository Server catalog repository data sets and a user repository – Repository Server configuration file – Repository Server startup procedure – JCL to execute the following: • Start a Repository Server • Add a user repository to the RS catalog repository © 2013 IBM Corporation56 • Add a user repository to the RS catalog repository • List user repository status information • Populate a user repository • Rename a user repository in the RS catalog repository • List detailed information for a single user repository • Modify and update user repository definitions • Delete a user repository in the RS catalog repository • Delete actual RS catalog repository and user repository data sets
  • 58. IVP Repository Enhancements … • Enhancement contained within U series of steps within IVP • No change to IVP system definition process (C series) • Updated jobs/tasks – IV_D201T and IV_D202T: updated to APF-authorize and place the FPQCSSI2/FPQCXCF2 modules into LPA (if required) – Job IV_E302J: updated to add the new user repository server procedure and the server configuration member into PROCLIB © 2013 IBM Corporation57 procedure and the server configuration member into PROCLIB – Job IV_U101J: updated to create RS catalog repository data sets and user repository data sets • New jobs/tasks – IV_U104J: starts the Repository Server – IV_U105J: adds a user repository to the RS catalog repository – IV_U202J: lists user repository status information – IV_U204J: populates the user repository
  • 59. IVP Repository Enhancements • New jobs/tasks – IV_U205J: renames a user repository in the RS catalog repository – IV_U206J: lists detailed information for a single user repository – IV_U207J: modifies and updates definitions for a user repository – IV_U208J: deletes a user repository in the RS catalog repository – IV_U209J: requests the Repository Server to start a user repository © 2013 IBM Corporation58 already deleted – IV_U401T: stops Repository Server – IV_U402J: deletes RS catalog repository and user repository data sets
  • 60. IMS 12 Redbooks • Available for free download at redbooks.ibm.com – IBM IMS Version 12 Technical Overview • Discusses all IMS 12 capabilities from a user perspective © 2013 IBM Corporation59
  • 61. Questions? © 2013 IBM Corporation60
  • 62. 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 © 2013 IBM Corporation61
  • 63. Learning Type-2 Commands • How do you find that table? • Type “Equivalent IMS type-1 and type-2 commands” into a search engine and the first result leads to this page: © 2013 IBM Corporation62
  • 64. IMS Repository Commands • IMS and RM IMSplex commands issued from SPOC or Manage Resources panels • Batch ADMIN commands • Repository Server commands issued through z/OS Modify interface RepositoryResource OMType-2 Command © 2013 IBM Corporation63 Repository Server Batch ADMIN Utility MODIFY command Resource Manager Command SPOC or Manage Resource Panels Console
  • 65. IMS and RM IMSplex Commands issued from SPOC or Manage Resources panels • IMS type-2 commands – UPDATE IMS – QUERY IMS – EXPORT DEFN TARGET(REPO) For management of repository and RDDS functions For status of IMS For working with DRD stored resource definitions in the repository © 2013 IBM Corporation64 – IMPORT DEFN SOURCE(REPO) – DELETE DEFN – QUERY DB/DBDESC/PGM/PGMDESC/TRAN/TRANDESC/RTC/RTCDESC SHOW(DEFN) definitions in the repository For displaying stored resource definitions in the repository and their attributes Remember: CREATE/UPDATE/DELETE commands work with runtime definitions Remember: CREATE/UPDATE/DELETE commands work with runtime definitions
  • 66. IMS and RM IMSplex Commands issued from SPOC or Manage Resources panels… • RM type-2 commands – UPDATE RM – QUERY RM For management of repository and RDDS functions For status of RM © 2013 IBM Corporation65
  • 67. • Commands for managing repositories (IMSRSC) – ADD – UPDATE – RENAME – DELETE Add a new repository definition, update an existing repository definition, rename an existing repository definition, remove an existing repository definition. Change data set disposition Batch ADMIN commands (FRPBATCH) (RM not used) © 2013 IBM Corporation66 – DSCHANGE – LIST – START – STOP List repository information Start or stop a repository Repository Server FRPBATCH (Batch ADMIN) Catalog Repository
  • 68. Repository Server Commands Issued Through the z/OS Modify Interface - (RM not used) • Functions for managing a Repository Server (RS) and its repositories (IMSRSC) – ADMIN – AUDIT Administrative functions for IMSRSC repositories – change data set disposition, display data sets, start/stop repositories Dynamically turn auditing on or off © 2013 IBM Corporation67 – SECURITY – SHUTDOWN – STOP Refresh in-storage RACF profile definitions Shutdown Repository Server address space(s) Stop/shutdown Repository Server

×