IMS DRD - IMS UG June 2013 Sao Paulo

466 views

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
466
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS DRD - IMS UG June 2013 Sao Paulo

  1. 1. IMS Dynamic Resource DefinitionJune 2013Betty Patterson – IBM Distinguished Engineer
  2. 2. © 2013 IBM Corporation1 2013Acknowledgements and Disclaimers:© Copyright IBM Corporation 2013. All rights reserved.– U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.IBM, the IBM logo, ibm.com, and IMS are trademarks or registered trademarks of International Business Machines Corporation in theUnited States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this informationwith a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBMtrademarks is available on the Web at “Copyright and trademark information” at ibm.com/legal/copytrade.shtmlOther company, product, or service names may be trademarks or service marks of others.Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in allcountries in which IBM operates.The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They areprovided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or adviceto any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it isprovided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of,or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have theeffect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of theapplicable license agreement governing the use of IBM software.All customer examples described are presented as illustrations of how those customers have used IBM products and the results they mayhave achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in thesematerials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specificsales, revenue growth or other results.
  3. 3. © 2013 IBM Corporation2 2013IMS Dynamic Resource Definition Agenda•Overview of Dynamic Resource Definition with ResourceDefinition Data Sets (RDDS)•Overview of the IMS Repository function•IMS Repository setup
  4. 4. © 2013 IBM Corporation3 2013Dynamic Resource Definition (DRD) Review• 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• 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
  5. 5. © 2013 IBM Corporation4 2013Modifying MODBLKS Resources without DRD//MODBLKSxControl BlocksDDIRsPDIRsSMBsRTCEsDuring IMS restart processing,resource definitions are loaded fromthe active MODBLKS library (cold start)or from the IMS log (warm/emergencyrestart).COLD START or OLCOLCSYSGEN ProcessIMS Control RegionIMS Control RegionAfter restart, these can onlybe added, changed, ordeleted through the ONLINECHANGE process oranother RESTART (somedefinitions can be updatedby command).OLDSWARM STARTEMERGENCY RESTART(Runtime Resource Definitions)(Stored ResourceDefinitions)RESTARTDATABASEAPPLCTNTRANSACTRTCODELog RecordsDDIRsPDIRsSMBsRCTEsCommandandCHKPTLogging
  6. 6. © 2013 IBM Corporation5 2013Modifying MODBLKS Resources with DRDDATABASEAPPLCTNTRANSACTRTCODERDDSControl BlocksDDIRsPDIRsSMBsRCTEsDuring IMS cold start processing,resource definitions may be IMPORTedfrom a Resource Definition Data Set (RDDS).Definitions can be dynamically created,updated, or deleted using new orenhanced Type-2 commands.Definitions can be EXPORTedto a Resource Definition Data Set.Definitions can be IMPORTedfrom a Resource Definition Data Set.COLD START(AUTOIMPORT)or IMPORTcommandAUTOEXPORT orEXPORTcommandCREATEUPDATEDELETEQUERYIMPORTEXPORTOLDSWARM START or /ERE(Stored ResourceDefinitions)(Runtime ResourceDefinitions)Log RecordsDDIRsPDIRsSMBsRCTEsIMS CONTROL REGIONIMS CONTROL REGIONCommandandCHKPTLogging
  7. 7. © 2013 IBM Corporation6 2013Dynamic Resource Definition OverviewIMS SystemDefinitionProcessIMSAIMS.MODBLKSAutomaticImport (cold start)IMPORTcommandCREATE,DELETE,EXPORT,IMPORT,orUPDATEcommandsResourceDefinitionDatasetIMSA SYSTEMResourceDefinitionDatasets(RDDS)EXPORTcommandAutomaticexportControl BlocksDDIRsPDIRsSMBsRCTEsOM InterfaceNon-systemRDDSEXPORTcommandIMPORTcommand1 First cold start2 435OLDS“Runtime”Resources“Stored”Resources“Stored”ResourcesLog RecordsDDIRsPDIRsSMBsRCTEsCommandandCHKPTLoggingWARM or/ERERESTART
  8. 8. © 2013 IBM Corporation7 2013Commands Used in Dynamic Resource Definition• Type-2 commands entered through Operations Manager interface to– QUERY, CREATE, UPDATE, DELETE, IMPORT or EXPORTresources and descriptors• A descriptor is a model for defining (creating) a resource or anotherdescriptor– Establishes defaults for attributes not set in the CREATE commandDelete resource or descriptor definitionDELDELETEEXPIMPQRYUPDCREShort FormUpdate attributes of resource or descriptor definitionUpdate status of resourceUPDATECreate resource or descriptor definitionCREATEExport resource or descriptor definitions to RDDS or RepositoryEXPORTImport resource or descriptor definitions from RDDS or RepositoryIMPORTQuery attributes of resource or descriptor definitionQuery status of resourceQUERYPurposeCommand
  9. 9. © 2013 IBM Corporation8 2013General 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 acompletion code for each resource• If CC not 0, CCText explains reason– SPOC displays completion code and text for each IMS and resource• Sample command input and response– PGM2 created even though command failed for PGM1CCTextCCMbrNamePgmName0IMS1PGM2RESOURCE ALREADY EXISTS11IMS1PGM1CREATE PGM NAME(PGM1,PGM2) SET(SCHDTYPE(SERIAL),...)
  10. 10. © 2013 IBM Corporation9 2013General 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)• Sample command input and response– PSB for ACCTUPDT references ACCTMSTR DBACCTUPDTErrorTextCCTextCCMbrNameDBName0IMS1CUSTMSTRREFERENCED BY PROGRAM11IMS1ACCTMSTRDELETE DB NAME(ACCTMSTR,CUSTMSTR)
  11. 11. © 2013 IBM Corporation10 2013DRD 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, DFSDSPG1, DFSDSTR1, DBFDSRT1– Can not 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”
  12. 12. © 2013 IBM Corporation11 2013Creating Resources OverviewTRANDAtrib1 = …….Atrib2 = …….Atrib3 = …….etc.TRANCAtrib1 = …….Atrib2 = …….Atrib3 = …….etc.TRANBAtrib1 = …….Atrib2 = …….Atrib3 = …….etc.• Example based on TransactionsTRANAAtrib1 = …….Atrib2 = …….Atrib3 = …….etc.MyTrDS2Atrib1 = …….Atrib2 = …….Atrib3 = …….etc.MyTrDS1Atrib1 = …….Atrib2 = …….Atrib3 = …….etc.DFSDSTR1 (IBM provided)Atrib1 = …….Atrib2 = …….Atrib3 = …….etc.DefaultTRANSACTIONS (SMBs) TRANSACTIONDESCRIPTORSCREATE 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 bedefined as the “default”
  13. 13. © 2013 IBM Corporation12 2013System Resource Definition Datasets (RDDSs)• Defined in the <SECTION=DYNAMIC_RESOURCES> section ofDFSDFxxx PROCLIB member• A set of BSAM data sets that contain MODBLKS resource anddescriptor definitions for one IMS– None or a minimum of 2 System RDDSs must be defined• 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
  14. 14. © 2013 IBM Corporation13 2013“Non-System” Resource Definition Datasets (RDDSs)• Non-System RDDS– Can be shared between IMSs– May contain a subset of an IMS’s resource and descriptordefinitions– Referred to explicitly on Export and Import commandsEXPORT DEFN TARGET(RDDS) TYPE() NAME()RDDSDSN(TEST1.NONSYSTEM.RDDS1) OPTION()
  15. 15. © 2013 IBM Corporation14 2013COLD START Options with DRD (IMS 10)• DRD is enabled by parameter in <SECTION=COMMON_SERVICE_LAYER>section of DFSDFxxx (or in DFSCGxxx)– MODBLKS=DYN  use DRD– MODBLKS=OLC  use MODBLKS Dataset and Online Change forMODBLKS• Cold Start action is determined by parameters in<SECTION=DYNAMIC_RESOURCES> section of DFSDFxxx– AUTOIMPORT=AUTO|RDDS|MODBLKS|NO• There are three possible cold start actions when DRD has been enabled– Auto-import resources from last-used RDDS• If RDDS has not yet been populated (first cold start after enabling DRD), thenresources are read from active MODBLKS dataset– Always read resources from MODBLKS dataset– Do not load any resource definitions• Could add resources later via CREATE commands or IMPORT command
  16. 16. © 2013 IBM Corporation15 2013DFSDFxxx Sample<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*/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 */
  17. 17. © 2013 IBM Corporation16 2013Recoverability• 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 arecreated, updated, or deleted• Resource and descriptor definitions are logged at checkpoint time– Are lost across cold start unless ...• Previously exported to RDDS (by Export command or AUTOEXPORT)< and then >• Imported during cold start
  18. 18. © 2013 IBM Corporation17 2013Autoexport=AUTO• Allows all resource and descriptor definitions for an IMS to be exportedto a system RDDS data set automatically at checkpoint time (simple orshutdown)• Enabling Automatic Export is optional• 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’sdefinitions• Automatic Export is always done following the restart checkpoint
  19. 19. © 2013 IBM Corporation18 2013EXPORT and IMPORT Commands with RDDS• Non-System RDDSs (user defined RDDSs) can be used– Not defined to IMS, but are referenced by name on commands– Can hold all or subset of resources from one or multiple IMS systems• EXPORT CommandEXPORT DEFN TARGET(RDDS) TYPE() NAME() RDDSDSN() OPTION()– Named resources written to specified RDDS (default is System RDDS)• If System RDDS, then all resources are exported• IMPORT CommandIMPORT DEFN SOURCE(RDDS) TYPE() NAME() RDDSDSN() OPTION()– Named resources read into memory from specified RDDS (default is SystemRDDS)• If System RDDS, then all resources are imported– From IMS 12, supports CREATE of new MODBLKS resources and UPDATE(optional) of existing resources
  20. 20. © 2013 IBM Corporation19 2013Invoking TSO SPOC Application for CommandsDFSAPPL IMS Application MenuCommand ===>Select an application and press Enter.1 Single Point of Control (SPOC)2 Manage resources3 Reserved for future use4 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.
  21. 21. © 2013 IBM Corporation20 2013Invoking TSO SPOC Application for Commands
  22. 22. © 2013 IBM Corporation21 2013Dynamically Creating a Program Resource
  23. 23. © 2013 IBM Corporation22 2013Updating a Resource Attribute Value
  24. 24. © 2013 IBM Corporation23 2013Updating a Resource Status
  25. 25. © 2013 IBM Corporation24 2013Dynamically Deleting a Resource
  26. 26. © 2013 IBM Corporation25 2013Manage 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• 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
  27. 27. © 2013 IBM Corporation26 2013Manage Resources Panels• DRD Resources can also be managed through the TSO SPOC“Manage Resources” panelsDFSAPPL IMS Application MenuCommand ===>Select an application and press Enter.1 Single Point of Control (SPOC)2 Manage resources3 Reserved for future use4 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“ManageResources”
  28. 28. © 2013 IBM Corporation27 2013Manage Resources List View• Example using CREATE TRANFile Action Manage resources SPOC View Options HelpIMS Create TransactionsCommand ===>Plex . . Route . . Wait . .Press Enter to continue More: +* NAME Transaction name . . TESTRANSETAOCMD AOI command option . . . . . . . N CMD,N,Tran,YCLASS Class. . . . . . . . . . . . . . 1 1-999CMTMODE Commit mode. . . . . . . . . . . SNGL Sngl, MultCONV Conversational . . . . . . . . . N Y, NDCLWA Log write-ahead option . . . . . Y Y, NDIRROUTE MSC direct routing option. . . . N Y, NEDITRTN Input edit routine . . . . . . .EDITUC Edit to uppercase. . . . . . . . Y Y, NEMHBSZ EMH buffer size. . . . . . . . . 12-30720“LIST” View – requiresmore screens in mostcases
  29. 29. © 2013 IBM Corporation28 2013Manage Resources Command Syntax ViewFile Action Manage resources SPOC View Options HelpIMS Create Transactions Top of dataCommand ===>Plex . . Route . . Wait . .Press Enter to continueCREATE TRAN NAME( TESTRAN )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“COMMAND SYNTAXView” – one screen
  30. 30. © 2013 IBM Corporation29 2013Manage Resources Panels ….• All DRD commands and utilities that work with RDDSs can be invokedthrough the panelsIM11A IMS Manage ResourcesCommand ===>Select an action and press Enter.* Action . . . . . . 1. Create new resources2. Delete resources3. Query resources4. Update resources5. Export resources6. Import resources7. Manage RDDS
  31. 31. © 2013 IBM Corporation30 2013Batch SPOC 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 SYSIN statements• Example//SPOCJOB JOB ,//MSGCLASS=H,NOTIFY=&SYSUID,USER=&SYSUID//SPOC EXEC PGM=CSLUSPOC,// 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
  32. 32. © 2013 IBM Corporation31 2013DRD Utilities• Set of offline utilities to perform the following DRD-related functions:• Utilities can be invoked through Manage Resources panelsRDDSRDDS RDDSDFSURCL0ExistingRDDSDFSURCP0DFSURCM0MODBLKS IMS LogRDDSDFSURST0SYSGEN•Stage 1 Macro statements•Type 2 CREATE commands•QUERYDFSURDD0RDDS
  33. 33. © 2013 IBM Corporation2013IMS Repository Function Overview
  34. 34. © 2013 IBM Corporation33 2013IMS Repository Function Overview• The IMS repository function is a centralized method for storing andretrieving resource definitions in an IMSplex*– Enables multiple IMS systems in a multiple-IMS IMSplex tomanage, store, share, and retrieve resource definitions– Enables a single IMS system in a single-IMS IMSplex to manage,store, share, and retrieve resource definitions• Focus is on improving the systems management and resourcemanagement aspects of handling IMS resource definitions– Across multiple IMSs or for a single standalone IMS– For test systems, for production systems *An “IMSplex”is an IMS with theCommon ServiceLayerComponentsSCI, RM and OMdefined*An “IMSplex”is an IMS with theCommon ServiceLayerComponentsSCI, RM and OMdefined
  35. 35. © 2013 IBM Corporation34 2013IMS Repository Function Usage …• In IMS 12, the resource and descriptor definitions for Dynamic ResourceDefinition (DRD) can be stored in an IMS repository– Contains resource definitions forprograms/transactions/databases/FP routing codes &descriptors– Called the IMSRSC (IMS resource) definition repository– Provides an alternative to using RDDSs (resource definition datasets) for DRD• Replaces one or more sets of RDDSs in an IMSplex with a singlerepository
  36. 36. © 2013 IBM Corporation35 2013IMS Repository Function Usage …• In IMS 12, the resource and descriptor definitions for Dynamic ResourceDefinition (DRD) can be stored in an IMS repository (cont’d)– Eliminates the need to manually coordinate and manage separateRDDSs per IMS across a multiple-IMS IMSplex– Provides an alternative to using MODBLKS with SYSGEN and onlinechange– Considered a strategic alternative to the RDDS• IMS 12 can retrieve the stored resource definitions from the IMSRSCrepository to dynamically generate runtime resources for DRD
  37. 37. © 2013 IBM Corporation36 2013Resource 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– Can EXPORT to RDDS or Repository– Executed on one IMS, it can specify that resource definitions exported toThe 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 fromThe Repository are to become runtime resource definitions in multiple IMS systems
  38. 38. © 2013 IBM Corporation37 2013Some 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 checkpointfollowing 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• Using Repository and RDDS with AUTOEXPORT to RDDS– Might use the RDDS to hold “temporary updates” while AUTOIMPORTfrom the Repository at a cold start will always restore to a known initialstate• Using Repository with Non-system RDDS only– Allows complete control of copying resources between systems that don’tshare a Repository (e.g. test to production)
  39. 39. © 2013 IBM Corporation38 2013Value of the IMS 12 repository for DRD• Full support for populating, managing, storing, sharing, and retrieving aconsistent set of DRD stored resource definitions for multiple-IMSIMSplexes and single-IMS IMSplexes in a single place• Provides improved availability– Repository can be enabled/disabled without an IMS outage viacommand– 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-IMSIMSplex– Repository architecture controls consistency and integrity of data
  40. 40. © 2013 IBM Corporation39 2013Value of the IMS 12 Repository for DRD• Provides improved functionality and flexibility for managing resourcesacross 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– 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
  41. 41. © 2013 IBM Corporation40 2013Value of the IMS 12 Repository for DRD• Provides support for both test and production environments– Repository Server can include data from different IMSplexesthough one per IMSplex recommended– Multiple IMSRSC repositories can exist within one RepositoryServer though one per Repository Server recommended– Migration and fallback utilities available based on RDDSs• Previously available DRD RDDS utilities can be used inbackup/recovery scenarios– IVP available to assist with installation of repository– Supported by TSO SPOC Manage Resources application
  42. 42. © 2013 IBM Corporation41 2013Value of the IMS 12 Repository for DRD• 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• Provides comprehensive set of repository administration tools– Includes batch utilities and command interfaces for repositorymanagement• Can be performed when IMS is down• A strategic IMS architectural direction– Based upon BPE, CSL, IMSplex architecture
  43. 43. © 2013 IBM Corporation42 2013IMS 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)– 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– New DRD utilities (PM41218)• MODBLKS to IMSRSC repository• IMS log to IMSRSC repository
  44. 44. © 2013 IBM Corporation43 2013IMS Repository Function ComponentsOperationsManager(OM)StructuredCallInterfaceResourceManager(RM)IMS Control RegionRepositoryServer(RS)SCI SCI SCISCISCIXCFXCFBatch ADMINUtility(FRPBATCH)RepositoryServerCommands(z/OS Modify)AuditLogXCFCSLURP10 /CSLURP20XCFRDDSRS Catalog RepositoryIMSRSC Repository“Runtime”Definitions“Stored”Definitionsz/OS ModifySPOCPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberI1M1 M2I2Primary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions OptionalOM Audit LogEmptyRepositoryServer(RS)XCF
  45. 45. © 2013 IBM Corporation44 2013Multi-IMS Sysplex ConfigurationIMSControlRegionSCISCICQSSCISPOCSPOCSCICommunicationsSCIOperationsManager(OM)SCIStructuredCallInterface(SCI)SCIResourceManager(RM)ResourceCFIMSControlRegionSCISCICQSSCICommunicationsSCIResourceManager(RM)SCIStructuredCallInterface(SCI)SCIOperationsManager(OM)RS Catalog RepositoryPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberIMSRSC RepositoryPrimary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions OptionalSPARERepositoryServer(RS)Audit LogXCFRepositoryServer(RS)XCFXCFXCF
  46. 46. © 2013 IBM Corporation45 2013IMS Repository Function Components …• Repository Server (RS)– New BPE-based address space• Access to RS is managed by theResource Manager (RM)• RS is NOT a CSL address space– Two types• Master Repository Server– Single instance– Manages access to repositorydata sets– First RS address space toaccess repository• Subordinate Repository Server– One or more instances– Used if master RepositoryServer goes down– Optional but recommended– User must start the RepositoryServer address space/sResourceManager(RM)RepositoryServer(RS)SCIXCFBatch ADMINUtility(FRPBATCH)RepositoryServerCommands(z/OS Modify)AuditLogXCFXCFRS Catalog RepositoryPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberI1M1 M2I2IMSRSC RepositoryPrimary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions OptionalRepositoryServer(RS)XCF
  47. 47. © 2013 IBM Corporation46 2013• Repository data sets– Multiple sets of VSAM KSDS datasets– Each set composed of• Repository index data set• Repository member data set• Each of these has a primary andsecondary data set (duplexed)– Optional spare set (third) canbe defined– Two types of repository data sets• Catalog repository data sets• IMS repository data setsIMS Repository Function Components …RepositoryServer(RS)AuditLogXCFRS Catalog RepositoryPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberI1M1 M2I2IMSRSC RepositoryPrimary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions Optional
  48. 48. © 2013 IBM Corporation47 2013IMS 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 setsIMS repository data sets– Composed of two pairs of data sets (no spare capability)• Primary index data set and primary member data set (required)• Secondary index data set and secondary member data set (required)• No spare capabilityRS Catalog data setsPrimary Member and Index data sets Secondary Member and Index data setsI1M1 I2M2
  49. 49. © 2013 IBM Corporation48 2013IMS Repository Function Components …• IMSRSC repository datasets 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 processed byan IMS system• IMS Change lists – new in IMS 13– Contain resource and descriptor names that were imported using theIMPORT SCOPE(ALL) command when an IMS was down– Behind the scenes, a separate IMS change list is actually created foreach 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 atend of coldstart
  50. 50. © 2013 IBM Corporation49 2013IMS 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)IMSRSC Repository data setsPrimary Member and Index data sets Secondary Member and Index data sets Optional Spare Member & IndexStoredDefinitionsStoredDefinitionsEmptyCOPY1 COPY2 SPARE
  51. 51. © 2013 IBM Corporation50 2013IMS 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• 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 inthe RM initialization member (CSLRIxxx) and with the UPDATE RMcommand
  52. 52. © 2013 IBM Corporation51 2013IMS 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)• 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
  53. 53. © 2013 IBM Corporation52 2013IMS Repository Function Components …• Batch utilities– Batch ADMIN utility (FRPBATCH)• Commands for managing IMSRSCrepositories– Functions such as ADDing a newIMSRSC repository, LISTing thecharacteristics of an IMSRSCrepository, STARTing orSTOPping an IMSRSC repository– RDDS to / from repository utilities(Batch RM utilities)• RDDS to Repository Utility(CSLURP10)– For migration• Repository to RDDS Utility(CSLURP20)– For fallback/backupResourceManager(RM)RepositoryServer(RS)SCIXCFBatch ADMINUtility(FRPBATCH)RepositoryServerCommands(z/OS Modify)AuditLogXCFCSLURP10 /CSLURP20XCFRDDSRS Catalog RepositoryIMSRSC RepositoryPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberI1M1 M2I2Primary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions Optional
  54. 54. © 2013 IBM Corporation53 2013IMS Repository Function Components …• Audit Log –Optional– z/OS Log stream– Examples of events that create audit logentries• Security errors• Registration and connection events• Access to repository– Can print audit log records with DFSERA10RepositoryServer(RS)AuditLogXCFRS Catalog RepositoryIMSRSC RepositoryPrimary/Copy1 DatasetsIndex/MemberSecondary/Copy 2 DatasetsIndex/MemberI1M1 M2I2Primary/Copy1DatasetsIndex/MemberSecondary/Copy 2DatasetsIndex/MemberI1M1 M2I2SpareDatasetsIndex/Member“Stored” Definitions Optional
  55. 55. © 2013 IBM Corporation54 2013IMS 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– Set up the CSL• RM needs new CSLRIxxx repository section– Set up IMS• DFSDFxxx needs new repository section– Start the master Repository Server– Start subordinate Repository Servers (optional)
  56. 56. © 2013 IBM Corporation55 2013Enabling an IMSRSC repository for DRD• Define security for IMS repository• Define the IMSRSC repository to the Repository Server• Start the IMSRSC repository• Enable RM and IMS to use the IMSRSC repository• Populate the IMSRSC repository– If IMS is up, populate using the EXPORT DEFN TARGET(REPO)command to add DRD stored resource definitions to the IMSRSCrepository– If IMS is down, use the batch RDDS to Repository Utility (CSLURP10)to populate the IMSRSC repository
  57. 57. © 2013 IBM Corporation56 2013IMSRSC Repository is Active/Populated• Begin to use type-2 DRD repository commands that access/updatestored resource definitions in the repositoryEXPORT DEFN TARGET(REPO) TYPE(ALL) NAME(*)IMPORT DEFN SOURCE(REPO) TYPE(DB) NAME(DBABC) OPTION(UPDATE)DELETE DEFN TARGET(REPO) TYPE(DB) NAME(DBXYZ)QUERY IMSQUERY DB/PGM/TRAN/RTC SHOW(DEFN)
  58. 58. © 2013 IBM Corporation57 2013Query 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
  59. 59. © 2013 IBM Corporation58 2013IMS Repository Function Benefits• Consolidation of resource definitions in a single place, the repository• DRD definitions are the initial implementation of the IMS repositoryfunction (to replace RDDSs)• Full support for populating, managing, storing, sharing, and retrieving aconsistent set of DRD stored resource definitions for multiple-IMSIMSplexes and single-IMS IMSplexes• Manual coordination of multiple RDDSs in a multiple-IMS IMSplexeliminated, replaced by basic functioning of the IMS repository• Improvements in IMSplex systems and resource management with therepository• A strategic direction for IMS architecture
  60. 60. © 2013 IBM Corporation59 2013Questions?
  61. 61. © 2013 IBM Corporation60 2013APPENDIX
  62. 62. © 2013 IBM Corporation61 2013Comparison of DRD Use with the RDDSVersus the Repository
  63. 63. © 2013 IBM Corporation62 2013Deleting Resources – RDDS Versus Repository DRD• RDDS DRD deleting– To delete a resource, issue a DELETE command at each IMSsystem that contains the runtime resource definition• Example: DELETE TRAN NAME(TRANA)– Automatic export will occur at system checkpoint and remove thedeleted resource from the system RDDS– EXPORT command can be issued at an IMS that deletes wereperformed on, to remove the deleted resource from thesystem/non-system RDDS• Example: EXPORT DEFN TARGET(RDDS) …
  64. 64. © 2013 IBM Corporation63 2013Deleting Resources – RDDS Versus Repository DRD• Repository DRD deleting– To delete a resource, issue a DELETE command at each IMSsystem that contains the runtime resource definition (same asRDDS DRD)– Issue a DELETE DEFN command, specifying FOR(IMSID()) toindicate which IMS systems that the deletes were performed on– EXPORT command cannot harden deleted resources to repositoryQUERY PGM NAME(PGM1) SHOW(WORK)UPDATE PGM NAME(PGM1) STOP(SCHD)DELETE PGM NAME(PGM1)DELETE DEFN TARGET(REPO) TYPE(PGM) NAME(PGM1)FOR(IMSID(IMS1,IMS2))Deletes Runtime DefinitionDeletes Repository Definition
  65. 65. © 2013 IBM Corporation64 2013Importing Resources – RDDS Versus Repository DRD• RDDS DRD importing– IMPORT DEFN SOURCE(RDDS) is processed at each IMS it isrouted to, and each IMS reads in definitions from the specifiedRDDS data set• Repository DRD importing– IMPORT DEFN SOURCE(REPO) is processed at each IMS it isrouted to, and each system reads in stored definitions from its IMSresource list within the shared repository– SCOPE(ALL) new parameter in IMS 13 for IMPORT only applies torepository DRD• Enables inactive IMSs to apply changes at /NRE or /ERE• Both RDDS DRD and repository DRD can create new and updateexisting runtime resource definitions using an IMPORT command…
  66. 66. © 2013 IBM Corporation65 2013Exporting Resources – RDDS Versus Repository DRD• RDDS DRD exporting– Handles resource additions, changes and deletions– Automatic export can occur at system checkpoint, which overwritesentire contents of oldest system RDDS with the IMS’s definitions– Each IMS has its own system RDDS that contains its entire set ofdefinitions– EXPORT DEFN TARGET(RDDS) command can overwrite anentire system/non-system RDDS or append to it (non-system)– EXPORT only applies to active IMS systems• No way of applying DRD activity occurring in IMSplex to an inactiveIMS
  67. 67. © 2013 IBM Corporation66 2013Exporting Resources – RDDS Versus Repository DRD• Repository DRD exporting– Handles only resource additions and changes (no deletions)– Automatic export not supported; to achieve same effect withinrepository, issue:• EXPORT to repository with CHANGESONLY option orSTARTTIME/ENDTIME, routing command to targeted IMS• DELETE DEFN with NAME() specifying runtime resources that havebeen deleted with DELETE command and FOR(IMSID()) specifyingwhich IMS resource lists should remove these resources– Each IMS has its own IMS resource list within one sharedrepository that contains its entire set of definitions
  68. 68. © 2013 IBM Corporation67 2013Exporting Resources – RDDS Versus Repository DRD• Repository DRD exporting– Can export definitions to an IMS that is inactive – resourcechanges will be applied when the IMS coldstarts• Issue EXPORT with SET(IMSID()) specified, including the IMSID ofthe inactive IMS• The inactive IMS’s stored resource definitions and resource list will beupdated with the exported definitions (additions and changes only)– If there have been deletions that should be reflected in theinactive IMS system, issue DELETE DEFN specifying the nameon FOR(IMSID())
  69. 69. © 2013 IBM Corporation68 2013Exporting Resources – RDDS Versus Repository DRD• Repository DRD exporting …• All resource definitions are exported as a single unit of work– Export will fail if one resource is in error and no other resources willbe exported• Processed by one command master IMS– Writing to one shared repository is beneficial because EXPORT willsucceed for all specified IMSs or none– Different than RDDS DRD, where EXPORT can be processed bymultiple IMS systems, possibly succeeding on some and failing onothers
  70. 70. © 2013 IBM Corporation69 2013Exporting Resources – RDDS Versus Repository DRD• New parameters only applicable to repository DRD– STARTTIME() and ENDTIME()– OPTION(CHANGESONLY)• Parameters applicable to RDDS DRD (non-system RDDS)– OPTION(APPEND)– OPTION(OVERWRITE)
  71. 71. © 2013 IBM Corporation70 2013Additional Information
  72. 72. © 2013 IBM Corporation71 2013Repository Startup Sequence Guidelines• Recommended start up sequence with all CSL components– SCI– OM– CQS– RS address space/s– RM– IMS• DBRC– SPOC– ODBM– IMS Connect
  73. 73. © 2013 IBM Corporation72 2013Learning 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-1commands with their type-2 DRD command equivalents
  74. 74. © 2013 IBM Corporation73 2013Learning Type-2 Commands• How do you find that table?• Type “Equivalent IMS type-1 and type-2 commands” into a searchengine and the first result leads to this page:
  75. 75. © 2013 IBM Corporation74 2013Track DRD Activity with OM Audit Trail• Enable OM Audit Trail to track IMSplex activity, including resourcesbeing dynamically managed– Displays DRD input commands + responses– Includes timestamps– Example showing an updated database and program…
  76. 76. © 2013 IBM Corporation75 2013• Enable OM Audit Trail to track IMSplex activity, including resources beingdynamically managed• Tracks DRD input commands/responses + timestampsOM Audit Trail Showing DRD Activity
  77. 77. © 2013 IBM Corporation76 2013• Filter by user IDOM Audit Trail Showing DRD Activity
  78. 78. © 2013 IBM Corporation77 2013• Includes type-1 and type-2 command input/response as well asunsolicited messages (anything that goes through OM)OM Audit Trail Showing DRD Activity
  79. 79. © 2013 IBM Corporation78 2013IMS Repository Commands• IMS and RM IMSplex commands issued from SPOC or ManageResources panels• Batch ADMIN commands• Repository Server commands issued through z/OS Modify interfaceRepositoryServerBatchADMINUtilityMODIFYcommandResourceManagerOMType-2CommandSPOC orManageResourcePanelsConsole
  80. 80. © 2013 IBM Corporation79 2013IMS and RM IMSplex Commands issued from SPOC orManage Resources panels• IMS type-2 commands– UPDATE IMS– QUERY IMS– EXPORT DEFN TARGET(REPO)– IMPORT DEFN SOURCE(REPO)– DELETE DEFN– QUERY DB/DBDESC/PGM/PGMDESC/TRAN/TRANDESC/RTC/RTCDESCSHOW(DEFN)For management of repository and RDDS functionsFor status of IMSFor working with DRD stored resourcedefinitions in the repositoryFor displaying stored resource definitionsin the repository and their attributesRemember:CREATE/UPDATE/DELETEcommands work withruntime definitionsRemember:CREATE/UPDATE/DELETEcommands work withruntime definitions
  81. 81. © 2013 IBM Corporation80 2013IMS and RM IMSplex Commands issued from SPOC orManage Resources panels…• RM type-2 commands– UPDATE RM– QUERY RMFor management of repository and RDDS functionsFor status of RM
  82. 82. © 2013 IBM Corporation81 2013Batch ADMIN commands (FRPBATCH) (RM not used)• Commands for managing repositories (IMSRSC)– ADD– UPDATE– RENAME– DELETE– DSCHANGE– LIST– START– STOPAdd a new repository definition, update an existing repositorydefinition, rename an existing repository definition, remove anexisting repository definition.Change data set dispositionList repository informationStart or stop a repositoryRepositoryServerFRPBATCH(Batch ADMIN)CatalogRepository
  83. 83. © 2013 IBM Corporation82 2013Repository Server Commands Issued Through the z/OSModify Interface - (RM not used)• Functions for managing a Repository Server (RS) and its repositories(IMSRSC)– ADMIN– AUDIT– SECURITY– SHUTDOWN– STOPAdministrative functions for IMSRSC repositories –change data set disposition, display data sets,start/stop repositoriesDynamically turn auditing on or offRefresh in-storage RACF profile definitionsShutdown Repository Server address space(s)Stop/shutdown Repository Server
  84. 84. © 2013 IBM Corporation83 2013IMS 12 Redbook Announcement• Discusses all IMS 12 capabilitiesfrom a user perspective• Available for free download atredbooks.ibm.com

×