Ims catalog user groupkb
description
Transcript of Ims catalog user groupkb
IMS Version 14 IMS 14
IMS Catalog
Kenny Blackman –zGrowth IMS Washington Systems Center
IMS Version 14 IMS 14
2
Agenda
IMS Catalog– IMS Catalog Overview– IMS Catalog Enablement – IMS Catalog Lifecycle– IMS Catalog Access
IMS Version 14 IMS 14
3
IMS Catalog Overview
IMS Version 14 IMS 14
IMS 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
IMS Version 14 IMS 14
Benefits
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
5
IMS Version 14 IMS 14
RepositorySpare
RepositorySecondary
Types of IMS Technical Metadata and Storage Method DB
– PSB/DBD resources• Database structure definitions• Physical database definitions• Segment definitions• Field definitions
– Application• Data types• Application defined fields• Encodings• Redefines• User defined types• Structures
TM– MODBLKS resources
• Program definitions• Transaction definitions• Database definitions• Routing Code definitions
– MFS FORMAT resources– Application
• Input/output message definitions
IMS HALDBDatabase
VSAM
6
RepositoryPrimary
BSAMRDDS
IMS Catalog
IMS Version 14 IMS 14
Applications 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
PSBLIB DBDLIBACBLIBCOBOL/PLI
source
DBD sourcePSB source
–IMS –User maintained
DLIModel Utility or IMS Explorer
Java classes
IMS Metadata7
IMS Version 14 IMS 14
Data types Data types have several metadata elements associated with them
– Application data type• Universal drivers use application data type to present data to clients
– Physical data type• Universal drivers use physical data type to marshal/unmarshal data to and from the database
– Example• Application data type is DECIMAL(10,2) [decimal with precision 10 and scale 2]• Physical data type is a signed packed decimal (AD community doesn’t need to know this)
New data type support– Structs (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– Arrays (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– User-defined
• Name of UDT can be defined to the catalog and intended to be used at runtime by Universal drivers to marshal/unmarshal data
• Can be part of a Struct or Array element
IMS Version 14 IMS 14
Maps
Mapping support– A Map is metadata that describes how a field (or set of fields) are mapped for a particular
segment instance– Metadata captures the various cases and for each case defines the set of fields to be
used for that case– Maps can be defined to the catalog– Maps are intended to be interpreted at runtime by the Universal drivers and the proper
data elements are returned based on the runtime case of the segment instance– Example: Insurance segment mapped multiple ways depending on value of Policy Type
control field
Policy Type
Property Type
Rooms Value Address Make Model Year Value Color
M - - - - Ford Escort 1989 2K Red
H Single Family 5 500K
555 Disk Drive Way,
95141- - - - -
IMS Version 14 IMS 14
With 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
10
IMS Version 14 IMS 14
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
The IMS Catalog Database
11
IMS Version 14 IMS 14
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
The IMS Catalog Database
12
IMS Version 14 IMS 14
Physical Catalog Structure
HEADER(RESOURCE HEADER)
SS(SENSEG)
PCB
PSB
SF(SENFLD)
PSBVENDPSBRMK(REMARKS)
PCBRMK(REMARKS)
SFRMK(REMARKS)
SSRMK(REMAKRS)
XDFLD
LCHILD
AREA CAPXDBD SEGMDSET(DATASET)
DBD
MAP(DFSMAP)
DBDRMK(REMARKS)
CAPXSEGM
CASE(DFSCASE)
LCHRMK(REMARKS)
SEGMRMK(REMARKS)
CMAR(DFSMARSH)
CPROP(PROPERTIES)
CFLD(FIELD)
DBDVEND
CFLDRMK(REMARKS)
CMARRMK(REMARKS)
DBDXREF
DSETRMK(REMARKS)
AREARMK(REMARKS)
FLD(FIELD)
MAR(DFSMARSH)
FLDRMK(REMARKS)
PROP(PROPERTIES)
MARRMK(REMARKS)
MAPRMK(REMARKS)
CASERMK(REMARKS)
RESERVED RESERVED
LCH2IDX(INDEX NAME)
XDFLDRMK(REMARKS)
…RESERVED
DSG A DSG B DSG DDSG C
DFSCX000
SecondaryIndex
IMS Version 14 IMS 14
14
IMS Catalog Enablement
IMS Version 14 IMS 14
IMS 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) BUILD PSB=(DFSCP002)
BUILD PSB=(DFSCP003)
15
N.B. The MODBLKS resources for the Catalog databases and Programs do not need to be defined!
IVP provides sample jobs and tasks that demonstrate how to access a simple IMS catalog. (See Task IV_O254T)
IMS Version 14 IMS 14
IMS 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
IMS Version 14 IMS 14
IMS Catalog Enablement
DFSDFxxx 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
17
IMS Version 14 IMS 14
IMS 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.
IMS Version 14 IMS 14
IMS 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
19
IMS Version 14 IMS 14
20
IMS 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 DBRCCatalog 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 defined
20
IMS Version 14 IMS 14
IMS Catalog Enablement
Using DBRC DSPURX00 utility and commands to define the Catalog database to the RECONs
– 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
21
//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(X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF') INIT.DB DBD(DFSCX000) TYPHALDB SHARELVL(3) INIT.PART DBD(DFSCX000) PART(DFSCX01) – DSNPREFX(dsnprefix.DFSCX000) - KEYSTRNG(X'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF') /*
IMS Version 14 IMS 14
22
IMS Catalog Lifecycle
IMS Version 14 IMS 14
DBD++ source
IMS Catalog Lifecycle
Catalog
PSB++ sourcePSBLIB++
DBDLIB++
PSBGEN
DBDGEN
ACBGENIMS Explorer DFS3PU00
DB Client Route
ACBLIB++PSBLIB
DBDLIB
ACBLIB
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
Populate Utility will populate catalog from ACBLIB
23
IMS Version 14 IMS 14 PSB and DBD statements changes
IMS Version 14 IMS 14
PSB 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
IMS Version 14 IMS 14
DBD 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
IMS Version 14 IMS 14
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 DBsPSBGEN timestamp for GSAM only PSBs
IMS Catalog Creation
27
IMS Version 14 IMS 14
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
IMS Catalog Creation
28
IMS Version 14 IMS 14
29
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 database
29
IMS Catalog Creation
IMS Version 14 IMS 14
30
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 catalog
30
IMS Catalog Creation
IMS Version 14 IMS 14
Catalog Populate Utility – DFS3PU00
PSB DFSCPL00 for initial loadPSB DFSCP001 for inserting additional records
31
Take an Image Copy of the Catalog database after the initial populate ! (Required if using DBRC)
ACBLIBs
DBDLIBs
PSBLIBs
Catalog Populate Utility
DFS3PU00
DFSDFxxx PROCLIB Member
Catalog
LOGs
SYSPRINTRECONs//IMSACB01 DD//IMSACBnn DD
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 statistics report.
IMS Version 14 IMS 14
IMS Catalog Members After Populate Utility
Catalog Populate Utility
DFS3PU00
DB1 TS0DB2 TS0DB3 TS0
DB1 TS0DB2 TS0DB3 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
CatalogACBLIB
32
IMS Version 14 IMS 14
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
33
IMS Version 14 IMS 14
34
PSBLIB
DBDLIB
ACBGEN &CAT POP
DFS3UACBCatalog
ACBLIB
Logs
DFSDFxxxPROCLIBMember
IMS Catalog Additions Via New ACBGEN & Populate Utility
SYSPRINT
RECONs
• 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)
//IMSACB DD and //IMSACB01 DD
34
IMS Version 14 IMS 14
ACBLIB and Catalog After New ACBGEN
ACBGEN &CAT POP
DFS3UACB
DB1DB2DB3
DB1 TS0 DB2 TS0 DB3 TS1
DB1 TS0DB2 TS0DB3 TS0
Catalog
ACBLIB
DBDLIB
DB3 TS1
DB3 TS0 Phase 1
Phase 2
PSBLIB
User makes a change to DB3 and runs ACBGEN1. Creates updated DB3 ACB member with
new timestamp2. Creates new DB3 member in the catalog
with new timestamp
IMS Version 14 IMS 14
Catalog Member Timestamps
Active
Catalog
Application request is made to read DB31. IMS determines active DB3 member has timestamp TS02. Internal DL/I call issued to retrieve member DB3 from
IMS catalog 3. IMS retrieves catalog member DB3 with timestamp TS0
DB1 TS0 DB1 TS0DB2 TS0DB3 TS0
CatalogACBLIBB
DB3 TS1
DB2 TS0 DB3 TS1
DB1 TS0
ACBLIBA
DB2 TS0 DB3 TS0
Inactive
IMS
DMB pool
DB3 TS0
IMS Version 14 IMS 14
Catalog Member Timestamps
Active
Catalog
Initiate OLC to switch from ACBLIBA to ACBLIBB– Activates DB3 ACB with timestamp TS1
Application request is made to read DB31. Internal DL/I call issued to retrieve member DB3 from IMS
catalog 2. IMS determines active DB3 member has timestamp TS13. IMS retrieves catalog member DB3 with timestamp TS1
DB1 TS0 DB1 TS0DB2 TS0DB3 TS0
CatalogACBLIBB
DB3 TS1
DB2 TS0 DB3 TS1
DB1 TS0
ACBLIBA
DB2 TS0 DB3 TS0
Inactive
InactiveActive
IMS
DMB pool
DB3 TS1 DB3 TS0
IMS Version 14 IMS 14
38
IMS Catalog Access
IMS Version 14 IMS 14
GUR 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
IMS Version 14 IMS 14
GUR Call
CALL=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>)
IMS Version 14 IMS 14
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
IMS Version 14 IMS 14
IMS Catalog Runtime Access
DBDB
WAS zType 2
UniversalDrivers
(SQL/DLI/XML
DRDA/TCPIP
SQL/DLI
SQL/DLI
DRDA/TCPIP
DLI
UsersIMS Explorer
Tools
Type 4UniversalDrivers
(SQL/DLI/XML)
Applications
SQL/DLI
SCI
DB2 z SPType 4
UniversalDrivers
(SQL/DLI/XML)
Catalog
CICSType 2
UniversalDrivers
(SQL/DLI/XML)
42
DEP Regions:
MPP, JMP, IFP,BMP & JBP
IMS Version 14 IMS 14
43
IMS Explorer For Development
IMS Version 14 IMS 14
44
IMS Explorer for Development
IMS Version 14 IMS 14
Immediate 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
IMS Version 14 IMS 14
IMS Explorer – 3.1.1.1 Available
New version made available for download from IMS Website on 10/14/2014
Includes enhancements for use with the IMS 13 Catalog
Download as part of IMS Enterprise Suite– ibm.com/ims– Click on IMS Enterprise Suite
Download the IMS Explorer ibm.com/ims Click on IMS Enterprise Suite
Latest version is 3.1.1.1Made available on 06/22/2012
IMS Version 14 IMS 14
IMS 13 Catalog Versioning Process Flow
DBJK21DBJK22DBJK23
Application
IMS
DBJK21 V3DBJK22 V3DBJK23 V3
ACBLI B
DBJK21 V0,V1,V2,V3DBJK22 V0,V1,V2,V3DBJK23 V0,V1,V2,V3
IMS Catalog
DBJK21 V3DBJK22 V3DBJK23 V3
DBDLIB
PSBJK
PSBLIBPSBGEN DBLEVL=CURR--------------------------PCB--------------------------DBJK21 V1DBJK22 DBJK23 V2
PSB=PSBJK Source
DBJK21 V3
DBD Source
DBJK22 V3
DBJK23 V3
DBDGEN
PSBGEN
DBJK21 V3DBJK22 V3DBJK23 V3
DBJK21 V3DBJK22 V2DBJK23 V1
DLI
Retrieve DBJK22 & DBJK23 from Catalog
Active
ACBGEN
Version “V3” of DBDs put into ACBLIB & Catalog
Database Versioning enabled -> data returned to app at V1, V2 & V3 levels
DBJK21
DBJK22
DBJK23
INIT VERSION(DBJK21=3,DBJK22=2,DBJK23=1)
47
IMS Version 14 IMS 14
IMS 14 Catalog DDL interface• Foundational component that offers dynamic capabilities for
IMS database• New IMS operational database in moments
• Focus on the “horizontal DBA”• Standard DDL interface for schema change
• Operational scalability for cloud solution deployments
PSBLIB
CatalogIMS ExplorerDDL
ACBLIB
DBDLIB
PSB source
DBDsource
IMS
Optional – no longer used by IMS
© 2014 IBM Corporation2014
IMS 14 Catalog DDL...• Foundational component that offers dynamic capabilities for
IMS database• New IMS operational database in moments
• Focus on the “horizontal DBA”• Standard DDL interface for schema change
• Operational scalability for cloud solution deployments
PSBLIB
CatalogIMS ExplorerDDL
ACBLIB
DBDLIB
PSB source
DBDsource
IMS
Optional – no longer used by IMS
IMS Version 14
50
IMS 14
IBM IMS Data Provider for Microsoft .NET
DRDAIMS Application Server
ODBMDATASTORE
(NAME=IMSA)
ALIAS (NAME=IMS)
z/OS
TCP/IPDDM
IMS ConnectTCPIP
DRDA
PORT
8888
SCI
DRDA
DLIcalls
SCIOM
IMS DB
IMS CatalogPSB1
Command
SQL + Parameters
DataReader
Connection
DRDA Client
ADO.NET Applications
Connection Pool
drdaserver.ims.com
Result set data
DataAdapter DataSet
IMS Version 14 IMS 14
COGNOS – Operational BI and Reporting
IMS Universal JDBC or DL/I Driver
IMS
ODBM
IMSIMS ConnecConnec
tt IMS
IMS DB IMS
Catalog
IMS Version 14 IMS 14 52
IMS Open Database:•IMS allows distributed access over TCP/IP using the IMS Universal Database Driver (JDBC)
•IMS Connect and Open Database Manager now work together as a DRDA server for IMS data
Workstation
Windows, Linux, and the Macz/OS
QMF IMS
Universal
Database Driver
TCPIP
TCPIP
IMS Connect
SCI
ODBM
SCI
DRA CTL IMS
DB
DL/IPC
IMS
DRDATCPIP
IMS 12 Catalog Metadata IMS 11 Local file Metadata
jdbc:ims://host:port/class://dfsivp37.DFSIVP37DatabaseView:dbViewLocation=C:/share/IMS Universal Drivers Metadata;fetchSize=0;
jdbc:ims://host:port/DFSCP000:dpsbOnCommit=true
IMS Integration with QMF
IMS Version 14 IMS 14
DataPower to IMS DB
DataPower
IMS
JDBC
Driver
Routing/
data
transformation
SQL
sends /
receives
DRDA
sends /
receives
IMS DB
ODBMIMSConnect
IMSCatalog
IMS DB
IMSCatalog
DRDASQL
DLI
Back
End
services
IMS 13
IMS Version 14 IMS 14
IBM Worklight and IMS Databases
Server
IMSIMSCONNECTCONNECT
Database
Database
manager
OD
BMIMS Universal
JDBC Driver
IMS Catalog
IMSIMS
DRDA protocolsDRDA protocols
TCP/IPTCP/IP SQL Adapter