Tips & Tricks
IMS V12 Repository and Catalog - IMS UG September 2012 LA DC Jax
Like this document? Why not share!
Rcreeee @ beirut energy forum posts...
by Ki Kecheng
Power Cable Joints for Hazardous Ar...
by Thorne & Derrick
Dr. Falk Pharma GmbH-Company Report
Good Business Email
by St John
Steve pickering title 22 three part...
Email sent successfully!
Show related SlideShares at end
IMS V12 Repository and Catalog - IMS UG September 2012 LA DC Jax
Sep 20, 2012
Comment goes here.
12 hours ago
Are you sure you want to
Your message goes here
Be the first to comment
Be the first to like this
Number of Embeds
No notes for slide
Transcript of "IMS V12 Repository and Catalog - IMS UG September 2012 LA DC Jax"
1. 9/19/12Kevin Hite – IMS Performance Test Lead19 September 2012IMS Version 12:Catalog and Repository © 2012 IBM CorporationDisclaimer © Copyright IBM Corporation 2012. 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. IBM SHALL NOT BE RESPONSIBLE 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, and IMS 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. © 2012 IBM Corporation 1
9/19/12Agenda § IMS Catalog – IMS Catalog Overview – IMS Catalog Enablement – IMS Catalog Lifecycle – IMS Catalog Access § IMS Repository Overview3 © 2012 IBM Corporation IMS Catalog Overview4 © 2012 IBM Corporation 2
9/19/12IMS Catalog Availability in IMS 12§ The IMS Catalog, a key feature of IMS 12 was made generally available effective April 23, 2012 – APAR PM45935/UK77995 (and additional pre-reqs) – After April 27, 2012 the supporting documentation for the IMS catalog function will be available online in the fully updated IMS Version 12 library in the Information Management Software for z/OS Solutions Information Center at: http://publib.boulder.ibm.com/infocenter/imzic.Information Center © 2012 IBM CorporationBenefits § Business Value – Offers a trusted and comprehensive view of IMS database metadata managed by IMS using standard interfaces • IMS Universal Drivers (SQL and DLI) • Traditional IMS DLI database queries – Opens up metadata discovery and exchange for IMS Open Database and the IMS Explorer – Permits future IMS integration with IBM tools • Cognos • Optim Development Studio • Rational Asset Analyzer • InfoSphere Data Architect – Enables scalable and flexible IMS Open Database solutions • Applications no longer need to maintain local Java metadata • Applications can reference the online IMS catalog © 2012 IBM Corporation 6 3
9/19/12Types of IMS Technical Metadata and Storage Method § DB – PSB/DBD resources • Database structure definitions • Physical database definitions • Segment definitions • Field definitions IMS Catalog – Application • Data types IMS HALDB • Application defined fields • Encodings Database • Redefines • User defined types • Structures § TM – MODBLKS resources • Program definitions Repository VSAM • Transaction definitions Primary • Database definitions Repository • Routing Code definitions Secondary Repository – MFS FORMAT resources Spare – Application RDDS • Input/output message definitions BSAM © 2012 IBM Corporation 7Applications Before the IMS Catalog § Databases partially defined in the IMS DBD – Only key/searchable fields needed by applications – Remaining segment data is not defined § Remaining database definition is within Applications – COBOL COPYBOOKs and PL/I INCLUDEs map all the segment data – Applications can have different mappings for one segment – IMS – User maintained COBOL/PLI PSBLIB ACBLIB DBDLIB source DLIModel Utility PSB source DBD source or IMS Explorer Java classes IMS Metadata © 2012 IBM Corporation 8 4
9/19/12With the IMS Catalog§ Updates to the IMS catalog are done only via integrated IMS processes - Catalog Populate Utility (initial catalog load and member update) - PSBGEN, DBDGEN and ACBGEN§ Catalog metadata can be used to: – Enhance understanding of the data – Improve consistency of the data – Improve impact analysis of the data – Improve development productivity – Improve data governance§ Key component of the IMS growth strategy: – Simplification – Integration © 2012 IBM Corporation 9The IMS Catalog Database§ Contains metadata related to an IMS system’s databases and programs – DBDs and PSBs and Application info§ IMS PHIDAM/OSAM HALDB database – Defined with 4 DSGs (Data Set Groups)§ Has one Secondary Index§ Unique features – DBRC use is optional for the IMS Catalog HALDB database • ONLY HALDB that isn’t required to be defined in the DBRC RECONs – IMS can manage allocation/creation of catalog database data sets • Uses parameters in the “CATALOG” section of DFSDFxxx PROCLIB member © 2012 IBM Corporation 10 5
9/19/12The IMS Catalog Database § IMS provides DBD and PSB source code for the Catalog database § IMS provides object code for the Catalog DBDs and PSBs § PHIDAM DBD reserved name is DFSCD000 § PSINDEX DBD reserved name is DFSCX000 – Used to connect DBDs to PSBs that reference them § PSBs provided to load, read and update the Catalog database – DFSCPL00 is used for initial load process • Used by the Catalog Populate Utility – DFSCP000 (COBOL/HLASM), DFSCP002 (PL/I), and DFSCP003 (PASCAL) , are used for read access – DFSCP001 is used for update access • Used by ACBGEN and Catalog Populate Utility § IMS automatically adds a PCB for the IMS catalog to each user PSB at run time (when the catalog is enabled) – Default catalog PCB is DFSCAT00 § ACBGEN required for all catalog PSBs © 2012 IBM Corporation 11Physical Catalog Structure HEADER (RESOURCE HEADER) DBD RESERVED RESERVED PSB RESERVED … DSET DBDRMK PSBRMK(DATASET) AREA CAPXDBD DBDVEND SEGM DBDXREF PSBVEND PCB (REMARKS) (REMARKS)DSETRMK AREARMK FLD SEGMRMK MAP PCBRMK SS(REMARKS) (REMARKS) (FIELD) CAPXSEGM LCHILD (REMARKS) (DFSMAP) (REMARKS) (SENSEG)FLDRMK MAR LCHRMK LCH2IDX MAPRMK CASE SSRMK SF (DFSMARSH) (INDEX NAME) XDFLD (REMAKRS) (SENFLD)(REMARKS) (REMARKS) (REMARKS) (DFSCASE) SFRMKMARRMK PROP CASERMK CFLD (REMARKS)(REMARKS) (PROPERTIES) XDFLDRMK (REMARKS) (FIELD) (REMARKS) Secondary CFLDRMK CMAR Index (REMARKS) (DFSMARSH) DFSCX000 CMARRMK CPROP (REMARKS) (PROPERTIES) DSG A DSG B DSG C DSG D © 2012 IBM Corporation 6
9/19/12 IMS Catalog Database Restriction WARNING: Coexistence with previous IMS releases is not supported ! Access to the IMS Catalog Database from any IMS subsystem, program, utility or client executing or utilizing an IMS release earlier than IMS 12 is not supported ! – For Example: • Access to the Catalog database from an IMS 10 or IMS 11 online subsystem is not supported • Access to the Catalog database from the IMS Explorer via an IMS 10 or IMS 11 subsystem is not supported • Access to the Catalog database from an IMS 10 or IMS 11 DFSDDLT0 utility job is not supported © 2012 IBM Corporation 13 IMS Catalog Enablement14 © 2012 IBM Corporation 7
9/19/12IMS Catalog Enablement § Add catalog DBDs and PSBs to your DBDLIB, PSBLIB & ACBLIB – Copy DBD and PSB object code from SDFSRESL to your DBDLIB and PSBLIB //CPYCMEM EXEC PGM=IEBCOPY //SDFSRESL DD DSN=SDFSRESL,DISP=SHR //DBDLIB DD DSN=MYIMS.DBDLIB,DISP=OLD //PSBLIB DD DSN=MYIMS.PSBLIB,DISP=OLD //SYSIN DD * COPY OUTDD=DBDLIB,INDD=((SDFSRESL,R)),LIST=YES SELECT MEMBER=(DFSCD000,DFSCX000) COPY OUTDD=PSBLIB,INDD=((SDFSRESL,R)),LIST=YES SELECT MEMBER=(DFSCPL00,DFSCP000,DFSCP001,DFSCP002,DFSCP003) – ACBGEN the catalog DBD and PSB resources into your ACBLIB //CATACB EXEC PGM=DFSRRC00,PARM=UPB //STEPLIB DD DSN=SDFSRESL,DISP=SHR //DFSRESLB DD DSN=SDFSRESL,DISP=SHR //IMS DD DSN=MYIMS.DBDLIB,DISP=SHR // DD DSN=MYIMS.DBDLIB,DISP=SHR //IMSACB DD DSN=IMS.ACBLIB,DISP=OLD //SYSIN DD * BUILD PSB=(DFSCPL00) BUILD PSB=(DFSCP001) BUILD PSB=(DFSCP000) IVP provides sample jobs and tasks that BUILD PSB=(DFSCP002) demonstrate how to access a simple IMS catalog. BUILD PSB=(DFSCP003) (See Task IV_O254T) N.B. The MODBLKS resources for the Catalog databases and Programs do not need to be defined! © 2012 IBM Corporation15IMS Catalog Enablement§ Modify DFSDFxxx PROCLIB Member – New CATALOG section(s) for catalog related parameters • Single section format <SECTION=CATALOG> • Multiple section format <SECTION=CATALOGimsid> – Multiple IMS systems sharing one DFSDFxxx PROCLIB member – imsid suffix must be a four character IMS ID – CATALOG section parameters • CATALOG=N | Y – Catalog is disabled or enabled – If enabled, IMS automatically creates catalog DDIR & PDIRs at IMS startup • ALIAS=DFSC | xxxx (no default value) – Specifies any 1-4 alphanumeric value used as a Catalog database name prefix – Enables use of non-shared, aliased, Catalog databases within an IMSplex • Use in a data sharing environment where each IMS has its own Catalog database and all are registered in a single set of RECONs – At runtime, the alias Catalog database names are dynamically replaced with internal database names DFSCD000 and DFSCX000 – For standalone IMS system use ‘‘DFSC’’ which is the standard Catalog database name prefix à DFSCD000 and DFSCX000 © 2012 IBM Corporation 8
9/19/12IMS Catalog EnablementDFSDFxxx PROCLIB Member – CATALOG section parameters (continued) • Information used by Catalog Populate Utility to automatically allocate the Catalog database data sets – DATACLAS • Optional data class for SMS managed data sets – MGMTCLAS • Optional management class for SMS managed data sets – STORCLAS • Required storage class for SMS managed data sets – IXVOLSER • Volume serial number for primary and secondary catalog indices • Required for non-SMS managed data sets – SPACEALLOC • Free space % (0 to 9999) added to the IMS-computed size of the primary & secondary data set allocations – SMSVOLCT • Number of volumes (1-20) created by the Catalog Populate utility for SMS-managed © 2012 IBM Corporation 17IMS Catalog Enablement DFSDFxxx PROCLIB Member CATALOG section parameters (continued) § RETENTION=(MAX=2 | nnn) or RETENTION=(PERIOD=0 | nnn) • Specifies retention schedule for metadata in the IMS catalog • By default IMS keeps only two copies of the DBD or PSB in catalog • MAX=2 | nnn • Maximum number of versions of a DBD or PSB to be stored before they are replaced first-in first-out • PERIOD=0 | nnn • Maximum number of days a version of a DBD or PSB is to be stored before it can be replaced • Metadata versions older than the specified retention period are not automatically deleted, but available for removal when new version of metadata is added • Default value of “0” disables this feature You need to run the Catalog Purge Utility to delete DBDs and PSBs from the Catalog – it doesn’t happen automatically. © 2012 IBM Corporation 9
9/19/12IMS Catalog Enablement § DFSDFxxx PROCLIB Member – Enabling the IMS catalog for IMS batch processing – Specify DFSDFxxx member on job EXEC parm – Requires JCL change to implement – User Exit Routine – Optional Catalog Definition user exit routine, DFS3CDX0 – Alternative to specifying DFSDFxxx member through job JCL – Available if users cannot or choose not to modify job JCL © 2012 IBM Corporation 19IMS Catalog Enablement § Definition of the HALDB structure – Partitioning of the catalog is the users responsibility • Minimum of 1 partition is required • Last partition must be able to contain the highest-key PSB record • Catalog HALDB uses the high-key selection method No use of Partition Selection Exit is allowed – Catalog Database Definition • For systems that use DBRC Catalog database can be defined to the RECONs with the DBRC utility and commands • For systems that do not use DBRC Catalog database must be defined to the Catalog Partition Definition data set using the Catalog Partition Definition Data Set utility, DFS3UCD0 • If an ALIAS is used in the CATALOG sections of the DFSDFxxx member, each alias Catalog database must be defined20 © 2012 IBM Corporation20 10
9/19/12IMS Catalog Enablement § Using DBRC DSPURX00 utility and commands to define the Catalog database to the RECONs //DEFCAT EXEC PGM=DSPURX00 //STEPLIB DD DSN=IMS.SDFSRESL,DISP=SHR //SYSPRINT DD SYSOUT=* //IMS DD DSN=IMS.DBDLIB,DISP=SHR //SYSIN DD * INIT.DB DBD(DFSCD000) TYPHALDB SHARELVL(3) INIT.PART DBD(DFSCD000) PART(DFSCD01) – DSNPREFX(dsnprefix.DFSCD000) – BLOCKSZE(4096) – KEYSTRNG(XFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF) INIT.DB DBD(DFSCX000) TYPHALDB SHARELVL(3) INIT.PART DBD(DFSCX000) PART(DFSCX01) – DSNPREFX(dsnprefix.DFSCX000) - KEYSTRNG(XFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF) /* – If using a catalog alias prefix, replace DFSC in the database and partition names for the catalog and the catalog secondary index with the four character ALIAS name prefix – You might need to define multiple alias name databases to the RECONs © 2012 IBM Corporation 21 IMS Catalog Lifecycle22 © 2012 IBM Corporation 11
9/19/12IMS Catalog Lifecycle Populate Utility will populate catalog from COBOL/PLI ACBLIB – source PSB++ source – PSB source PSBGEN PSBLIB++ PSBLIB ACBLIB++ ACBLIB ACBGENIMS Explorer DFS3PU00 DBD++source – DBD source DBDGEN DBDLIB++ DBDLIB Catalog DB Client Route § ACBGEN will populate ACBLIB and catalog in same UOW • Populates ACBLIB with standard ACB info and extended info • Populates the catalog with extended info § Key points • Only way to update catalog is via the Populate Utility or ACBGEN process • Extended info is acquired via the IMS Explorer • Extended info stored in ACBLIB members for recoverability © 2012 IBM Corporation 23PSB and DBD statements changes © 2012 IBM Corporation 12
9/19/12PSB PCB statements changes§ PCB – EXTERNALNAME= • An optional alias for the PCB label or the PCBNAME= parameter • Java application programs use the external name to refer to the PCB – REMARKS= • Optional user comments. A 1- to 256-character field. Added to PSBGEN statements © 2012 IBM CorporationDBD statement changes § DBD – ENCODING= • Specifies the default encoding of all character data in the database defined by this DBD. • This value can be overridden in individual segments or fields. § SEGM – EXTERNALNAME= • An optional alias for the NAME= parameter used by Java application programs to refer to the segment. § FIELD – CASENAME= • The name of the map case when alternative mappings are defined for the fields in a segment – DATATYPE= • Specifies the external data type of the field. – EXTERNALNAME= • An optional alias for the NAME= parameter used by Java application programs to refer to the field. § DFSMARSH – Specifies the DATATYPE converter routine to transform binary data to external data format § DFSMAP – Defines alternative field mappings in a segment. § DFSCASE – Defines a map case for a segment type that uses DFSMAP alternative field mapping. § REMARKS= • Optional user comments. A 1- to 256-character field. Added to DBDGEN statements © 2012 IBM Corporation 13
9/19/12IMS Catalog Creation§ Populate the IMS Catalog – Load the IMS Catalog using IMS Catalog Populate utility, DFS3PU00 • Each ACB member is decoded, converted to catalog format, loaded into the catalog – Reads ACBLIB, DBDLIB and PSBLIB datasets as input • Data sets can be concatenated but only first occurrence of an ACB member is used • DBDLIB needed for Logical databases and GSAM databases • PSBLIB needed to determine which GSAM databases go into the catalog – Catalog database DBD and PSB segments will have a version and contain a timestamp that matches the ACB member timestamp • Used to associate an ACB member with a catalog member • Timestamp exceptions DBDGEN timestamp for Logical and GSAM DBs PSBGEN timestamp for GSAM only PSBs © 2012 IBM Corporation 27IMS Catalog Creation§ Populate the IMS Catalog … – If any of the database data sets do not exist, the DFS3PU00 utility creates them automatically: i.e. the DFSCD000 database data sets which are: • The primary index data set • The indirect list data set (ILDS) • Four data set group data sets for the segments of the IMS catalog • DFSCX000 secondary index data set – DFS3PU00 calculates the size of the database data sets based on both the size of the ACB library and the expansion percentages that you can specify in the DFSDFxxx PROCLIB member • The DFSDFxxx member is also where you specify the volume serial number for the VSAM key-sequenced data sets or the SMS storage class, data class, and management class for all data sets © 2012 IBM Corporation28 14
9/19/12IMS Catalog Creation § IMS Catalog Populate utility – Can run as a typical IMS Batch or BMP job • Requires IMS logs for backout / recovery • Requires IRLM if catalog is shared and catalog active in an IMS subsystem - Business as usual for data sharing • Requires DBRC if catalog is defined in the RECON • If using Catalog Partition Definition Data Set - User’s responsible to ensure online catalog access has ceased - Business as usual for non-registered full function DB – Can also be used to insert additional records to an existing Catalog database29 © 2012 IBM Corporation29IMS Catalog Creation § Load the IMS Catalog using the new ACB Generation and Catalog Populate utility, DFS3UACB – Generates the ACB library members and loads the IMS catalog metadata in the same job step – Not recommended if ACBLIB is already valid • No need to recreate the ACBLIB, just populate the catalog30 © 2012 IBM Corporation30 15
9/19/12Catalog Populate Utility – DFS3PU00 If you need to know how much DASD storage the IMS catalog data sets will use before they are created, you can run the DFS3PU00 utility without populating the IMS catalog to generate only the DFSDFxxx statistics report. PROCLIB SYSPRINT//IMSACB01 DD RECONs//IMSACBnn DD Member ACBLIBs Catalog Catalog Populate Utility DBDLIBs DFS3PU00 PSB DFSCPL00 for initial load PSB DFSCP001 for inserting additional records LOGs PSBLIBs Take an Image Copy of the Catalog database after the initial populate ! (Required if using DBRC) © 2012 IBM Corporation 31IMS Catalog Members After Populate Utility ACBLIB Catalog DB1 TS0 Catalog Populate Utility DB1 TS0 DB2 TS0 DFS3PU00 DB2 TS0 DB3 TS0 DB3 TS0 • There are 3 members in an ACBLIB • Run the Catalog Populate Utility, DFS3PU00 • The catalog members will have a timestamp TS0 • This is the ACB member timestamp © 2012 IBM Corporation 32 16
9/19/12 Adding IMS Catalog Metadata§ New ACB Generation and Catalog Populate utility, DFS3UACB – Replaces existing ACBGEN Utility, DFSUACB0, if IMS catalog enabled – Generate ACBLIB member and create catalog metadata in a single job • Phase 1 – ACBGEN - DBDLIB and PSBLIB members used as input - Validation is unchanged - ACB member is written to ACBLIB with new ACBGEN timestamp • Phase 2 – IMS catalog update -Generated ACB is decoded, converted to catalog format, loaded into the catalog - DBD and PSB metadata created and inserted - Corresponding ACB member timestamp saved as timestamp in catalog DBD and PSB segments - Ensures validity and consistency of ACBLIB and catalog§ New ACBGEN (DFS3UACB) and new Catalog Populate (DFS3PU00) utilities are the only updaters of the IMS catalog – IMS online and IMS batch regions will never update catalog data – IMS online and IMS batch regions will only retrieve data from the catalog © 2012 IBM Corporation 33IMS Catalog Additions Via New ACBGEN & Populate Utility DFSDFxxx SYSPRINT PROCLIB RECONs Member //IMSACB DD and ACBLIB //IMSACB01 DD PSBLIB ACBGEN & CAT POP DFS3UACB Catalog DBDLIB Logs • New integrated ACBGEN process includes update to the IMS catalog • DFSDFxxx PROCLIB member has the catalog information • DFSMDA member used to dynamically allocate the catalog datasets (if not using DBRC for the Catalog)34 © 2012 IBM Corporation34 17
9/19/12ACBLIB and Catalog After New ACBGEN ACBLIB PSBLIB DB1 TS0 DB2 TS0 DBDLIB Phase 1 DB3 TS0 TS1 DB1 ACBGEN & DB2 CAT POP DFS3UACB Catalog DB3 Phase 2 DB1 TS0 DB2 TS0§ User makes a change to DB3 and runs ACBGEN DB3 TS0 1. Creates updated DB3 ACB member with DB3 TS1 new timestamp 2. Creates new DB3 member in the catalog with new timestamp © 2012 IBM CorporationCatalog Member Timestamps § Application request is made to read DB3 1. IMS determines active DB3 member has timestamp TS0 2. Internal DL/I call issued to retrieve member DB3 from IMS catalog 3. IMS retrieves catalog member DB3 with timestamp TS0 Inactive ACBLIBB Catalog DB1 TS0 IMS Active DB2 TS0 DB3 TS1 DB1 TS0 ACBLIBA DMB pool DB2 TS0 DB1 TS0 DB3 TS0 DB2 TS0 DB3 TS0 Catalo DB3 TS0 DB3 TS1 g © 2012 IBM Corporation 18
9/19/12Catalog Member Timestamps § Initiate OLC to switch from ACBLIBA to ACBLIBB – Activates DB3 ACB with timestamp TS1 § Application request is made to read DB3 1. Internal DL/I call issued to retrieve member DB3 from IMS catalog 2. IMS determines active DB3 member has timestamp TS1 3. IMS retrieves catalog member DB3 with timestamp TS1 Inactive Active Catalog ACBLIBB IMS Inactive Active DB1 TS0 DB1 TS0 ACBLIBA DB2 TS0 DMB pool DB2 TS0 DB3 TS1 DB1 TS0 DB3 TS1 DB3 TS0 DB2 TS0 DB3 TS0 Catalog DB3 TS0 DB3 TS1 © 2012 IBM Corporation IMS Catalog Access38 © 2012 IBM Corporation 19
9/19/12GUR Call§ In addition to traditional DL/I read access to the IMS Catalog using PSB DFSCP000, IMS provides a new “GUR” DL/I call – Get Unique Record – Restricted to use with IMS Catalog database§ Functions like a GU followed by a series of GNP calls§ Returns the entire database record in one call – Saves overhead of issuing GU & GNP to retrieve all the metadata for a catalog member – Using an AIB token, the call can be continued if the I/O area is too small for entire catalog database record§ Data returned will be in XML format – Matches the XML schema§ Results cached for runtime performance © 2012 IBM CorporationGUR CallCALL=GUR SEG=HEADER FIELD=RHDRSEQ OPER=== VALUE=DBD IVPDB2 ) 337 276776 32323226 6 66 6324733332277 6 632767233SEGMENT =(CF8_%065239?>D21E0205>3?49>7D23010472034/>4/%?>5D29532FE<ns2:dbd xmlns:ns2="http://www.ibm.com/ims/D) (BD" dbdName="IVPDB2" timestamp="1225417233260" version="04/09/0313.16" xmlSchemaVersion="1"><access ) (dbType="HDAM"><hdam datxexit="N" password="N" osAccess="VSAM"><rmName name="DFSHDC40"><subOptions an) (chorPoints="40" maxRBN="100" bytes="0"/></rmName><dataSetContainer><dataSet ddname="DFSIVD2" label=) ("DSG1" searchA="0" scan="3"><block size="0"/><size size="0"/><frspc fspf="0" fbff="0"/></dataSet></d) (ataSetContainer></hdam></access><segment imsName="A1111111" name="A1111111" encoding="Cp1047"><hdam ) (label="DSG1"><bytes maxBytes="40"/><rules insertionRule="L" deletionRule="L" replacementRule="L" ins) (ertionLocation="LAST"/><pointer physicalPointer="TWIN" lparnt="N" ctr="N" paired="N"/></hdam><field ) (imsDatatype="C" imsName="A1111111" name="A1111111" seqType="U"><startPos>1</startPos><bytes>10</byte) (s><marshaller encoding="Cp1047"><typeConverter>CHAR</typeConverter></marshaller><applicationDatatype) ( datatype="CHAR"/></field><field imsDatatype="C" name="FIRSTNAME"><startPos>11</startPos><bytes>10</) (bytes><marshaller encoding="Cp1047"><typeConverter>CHAR</typeConverter></marshaller><applicationData) (type datatype="CHAR"/></field><field imsDatatype="C" name="EXTENSION"><startPos>21</startPos><bytes>) (10</bytes><marshaller encoding="Cp1047"><typeConverter>CHAR</typeConverter></marshaller><application) (Datatype datatype="CHAR"/></field><field imsDatatype="C" name="ZIPCODE"><startPos>31</startPos><byte) (s>7</bytes><marshaller encoding="Cp1047"><typeConverter>CHAR</typeConverter></marshaller><applicatio) (nDatatype datatype="CHAR"/></field></segment></ns2:dbd>) © 2012 IBM Corporation 20
9/19/12 IMS Catalog Supported Interfaces § Open systems – Universal drivers - Type 4 • SQL and DLI interfaces directly to the catalog • XML - render catalog information as XML instance document § z/OS – Universal drivers - Type 2 and Type 4 • SQL and DLI interfaces directly to the catalog • XML - render catalog information as XML instance document – Traditional IMS languages • DLI access directly to the catalog • Batch access supported 41 © 2012 IBM Corporation IMS Catalog Runtime Access UsersIMS Explorer DRDA/TCPIP IMS SQL/DLI Type 4 IMS Connect DEP Regions: Universal Drivers MPP, JMP, IFP, (SQL/DLI/XML) BMP & JBP Tools SCI Catalog DB ODBM SQL/DLI DB DLIApplications SQL/DLI DRDA/TCPIP WAS z CICS Type 2 Type 2 DB2 z SP Universal Universal Type 4 Drivers Drivers Universal (SQL/DLI/XML (SQL/DLI/XML) Drivers (SQL/DLI/XML) 42 © 2012 IBM Corporation 21
9/19/12IMS Explorer For Development43 © 2012 IBM Corporation IMS Explorer for Development44 © 2012 IBM Corporation 22
9/19/12IMS Explorer – 184.108.40.206 Available§ New version made available for download from IMS Website on 06/22/2012 – Includes enhancements for use with the IMS 12 Catalog§ Download as part of IMS Enterprise Suite – ibm.com/ims – à Click on IMS Enterprise Suite Latest version is 220.127.116.11 Made available on 06/22/2012 Download the IMS Explorer ibm.com/ims à Click on IMS Enterprise Suite © 2012 IBM CorporationImmediate Benefits§ All Universal drivers leverage the IMS catalog – Trusted online (IMS) source for metadata used by the drivers – Direct access to IMS metadata in the catalog – No longer require the separate Java metadata class • Virtual deployment support – No longer file-system dependent for metadata • Virtual deployment support – Metadata is trusted and up-to-date © 2012 IBM Corporation 23
9/19/12Redbooks – IMS Catalog – “Redpiece”§ Document on the IMS Catalog has been updated, and is available for download atredbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/redp4812.html?Open © 2012 IBM Corporation IMS Repository Function Overview © 2012 IBM Corporation 24
9/19/12Types of IMS Technical Metadata and Storage Method § DB – PSB/DBD resources • Database structure definitions • Physical database definitions • Segment definitions • Field definitions IMS Catalog – Application • Data types IMS HALDB • Application defined fields • Encodings Database • Redefines • User defined types • Structures § TM – MODBLKS resources • Program definitions Repository VSAM • Transaction definitions Primary • Database definitions Repository • Routing Code definitions Secondary Repository – MFS FORMAT resources Spare – Application RDDS • Input/output message definitions BSAM © 2012 IBM Corporation 49IMS Repository Function Overview§ A ‘repository’ is a generalized data storage facility that can be used to store various types of information§ The IMS repository function is a centralized method for storing and retrieving resource definitions in an IMSplex – Enables multiple IMS systems in a multiple-IMS IMSplex to manage, 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 resource management aspects of handling IMS resource definitions – Across multiple IMSs or for a single standalone IMS – For test systems, for production systems © 2012 IBM Corporation 25
9/19/12IMS Repository Function Usage§ In IMS 12, the IMS repository – 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 – 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 © 2012 IBM CorporationIMS 12 Support for the DRD Function …§ DRD users in IMS 10 and IMS 11 moving to IMS 12 – Can use existing RDDSs from IMS 10 or IMS 11 for stored resource definitions in IMS 12 – Can use existing RDDSs from IMS 10 and IMS 11 for stored resource definitions at initial migration to IMS 12, then can migrate to the new IMSRSC repository – Can use the new IMSRSC repository to store definitions in IMS 12 © 2012 IBM Corporation 26
9/19/12IMS 12 Support for the DRD Function§ Users in IMS 10 and IMS 11 without DRD can – implement DRD with RDDSs – implement DRD using the repository – con5nue to use SYSGEN/online change to manage MODBLKS deﬁni5ons § Both RDDSs (system and non-system) and the IMSRSC repository can exist together during migration to the IMSRSC repository © 2012 IBM CorporationIMS Repository Function Components …§ Repository Server (RS)§ Repositories – Catalog repository (not to be confused with the IMS Catalog) – IMSRSC repository(s)§ 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 © 2012 IBM Corporation 27
9/19/12IMS Repository Function Architecture CSLURP10 / RS Catalog Repository CSLURP20 Operations Resource Structured X Primary/Secondary Manager Manager Call Interface C (OM) (RM) F SCI SCI SCI Audit Log X Repository C Server F (RS) SCI IMS Batch ADMIN X Control Utility C Region (FRPBATCH) F IMSRSC Repository z/OS mod int Repository Server SCI Commands Primary/Secondary XCF © 2012 IBM CorporationIMS Repository Function Components …§ Repository Server (RS) – New BPE-based address space • Managed by the RM CSL address space – Two types • Master Repository Server - Single instance - 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 © 2012 IBM Corporation 28
9/19/12IMS Repository Function Components …§ Repository Server (RS) – Uses VSAM KSDS data sets to store information – Recommendation • One master Repository Server address space per IMSplex – Has its own internal repository called the ‘catalog repository’ – Manages IMS repositories (IMSRSC for DRD) – Ensures repository data integrity – Uses SAF (RACF) to restrict access to repositories – Provides an audit trail using the z/OS logger – Provides tracing capabilities via BPE © 2012 IBM CorporationIMS Repository Function Components …§ IMS repositories – IMSRSC repository contains • 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 by an IMS system – Typically one IMSRSC repository per Repository Server (RS) per IMSplex © 2012 IBM Corporation 29
9/19/12IMS Repository Function Components …§ IMS repositories – IMSRSC repository • Composed of up to three pairs of data sets Primary index data set and primary member data set (required) Secondary index data set and secondary member data set (required) Spare index data set and spare member data set (optional) IMSRSC repository data sets Secondary Secondary (optional) Primary Primary (optional) Spare Spare Index Data Sets Member Data Sets © 2012 IBM CorporationIMS 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 QUERY RM • RM is enabled to the repository by specifying a Repository Section in the RM initialization member (CSLRIxxx) © 2012 IBM Corporation 30
9/19/12IMS Repository Function Components …§ A Common Service Layer (CSL) IMSplex configuration consisting of – Structured Call Interface (SCI) • Used for communications within the CSL • Not used for communications between RM and the RS • RS is not considered a CSL 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 – SPOC (single point of control) for entering type-2 commands – Can be a single-IMS IMSplex or a multiple-IMS IMSplex © 2012 IBM CorporationIMS Repository Function Components§ Batch utilities – Batch ADMIN utility (FRPBATCH) • Commands for managing IMSRSC repositories - Functions such as ADD a new IMSRSC repository, LIST the characteristics of an IMSRSC repository, START or STOP 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 © 2012 IBM Corporation 31
9/19/12IMS Repository Function Benefits§ Consolidation of resource definitions in a single place, the repository§ DRD definitions are the initial implementation of the IMS repository function (to replace RDDSs)§ 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§ Manual coordination of multiple RDDSs in a multiple-IMS IMSplex eliminated, replaced by basic functioning of the IMS repository§ Improvements in IMSplex systems and resource management with the repository§ A strategic direction for IMS architecture © 2012 IBM CorporationIMS 12 Redbook Announcement§ Just released!§ Discusses all IMS 12 capabilities from a user perspective§ Draft available for free download at http://www.redbooks.ibm.com © 2012 IBM Corporation 32
9/19/12Questions? © 2012 IBM Corporation 33