• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
IMS V12 and V13 Overview 2013 - IMS UG May 2013 Omaha
 

IMS V12 and V13 Overview 2013 - IMS UG May 2013 Omaha

on

  • 2,880 views

 

Statistics

Views

Total Views
2,880
Views on SlideShare
2,880
Embed Views
0

Actions

Likes
0
Downloads
17
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    IMS V12 and V13 Overview 2013 - IMS UG May 2013 Omaha IMS V12 and V13 Overview 2013 - IMS UG May 2013 Omaha Presentation Transcript

    • ®IMS Version 13IMS V12 & V13 OverviewMay 14, 2013© 2013 IBM CorporationJosh Newell – newelljo@us.ibm.comIMS Level 2 Support
    • Status of IMS Versions• IMS Version 9• End of service was November 7, 2010• IMS Version 10• Generally available on October 26, 2007• End of service was November 5, 2012• IMS Version 11• Generally available on October 30, 20092 2• Generally available on October 30, 2009• End of service has not been announced• IMS Version 12• Generally available on October 28, 2011• End of service has not been announced• IMS Version 13• Announced on October 3, 2012• Currently in QPP program• General availability has not been announced
    • IMS 12 Highlights- IMS Repository andUsage for DRD Resources- IMPORT CommandEnhancement- ACB Member Online ChangeSystems Management-IMS to IMS TCP/IPCommunications- MSC TCP/IP SupportTransaction Managementand ConnectivityFull Function Database- FF Dynamic DB Buffers- FF DB Storage Enhancement- Additional FF EnhancementsDatabase Management3- ACB Member Online ChangeEnhancement- Logger Enhancements- Syntax CheckerEnhancements- CCTL/DRAOpen Thread TCB Support- Extended Address Volume- VSAM Control Area Reclaim- OTMA TCP/IP Support- IMS Connect Type-2Commands Support- Additional ConnectEnhancements- OTMA Security Enhancements- APPC/OTMA Synch SQ- Enhanced CQS TraceabilityFast Path- FP Buffer Manager 64 bitEnhancements- FP DEDB Secondary IndexEnablement- Additional FP EnhancementsDBRC- DBRC Enhancements- Migration/Coexistence
    • IMS Version 12• Announced on October 5, 2010• General Availability 4Q2011• Hardware Prerequisites• IMS 12 runs only on 64 bit processors running in z/Architecture mode• Minimum Software Prerequisites• z/OS V1R11 (5694-A01)• High Level Assembler Toolkit (5696-234), Version 1 Release 54• SMP/E V3R5• RACF, or ISV equivalent (if security used)• IRLM 2.2 (if IRLM used)• Minimum software levels for optional functions:• Parallel RECON Access requires Transactional VSAM• Java Dependent Regions require JDK 6.0• The IMS Universal Drivers require JDK 6.0• EAV support for non-VSAM data sets requires z/OS V1R12• VSAM Control Area Reclaim requires z/OS V1R12
    • IMS Version 12• Miscellaneous Requirements• System-managed CF Duplexing requires CF level 12 and bidirectional CF to CF links• Extended Address Volume (EAV) support for non-VSAM data sets requires a DS8000or DS8700 Storage Subsystem• Additional line item requirement information see the IMS 12 Release Planningmanual IBM IM Info Center• Supported Migrations and Coexistence5• Supported Migrations and Coexistence• CHANGE.RECON UPGRADE command supported• IMS 11 to IMS 12• Upgrade RECONs from IMS 11 to IMS 12• Databases are compatible• Application programs are compatible• IMS 10 to IMS 12• Upgrade RECONs from IMS 10 to IMS 12• Databases are compatible• Application programs are compatible
    • IMS 12Catalog6
    • Agenda• IMS Metadata• Local File Metadata vs. IMS Catalog Metadata• IMS Catalog Database• Enablement and Implementation of the IMS Catalog• Application Programming with the Catalog77
    • IMS Metadata• Databases partially defined in the IMS DBD• Only key/searchable fields needed by applications• Remaining segment data is not defined• Remaining database segment definition is within Applications• COBOL COPYBOOKs and PL/I INCLUDEs map all the segment data• Applications can have different mappings for one segmentIMS User maintained88PSBLIB DBDLIBACBLIBCOBOL/PLIsourceDBD sourcePSB sourceIMS User maintainedDL/I model utilityJava classesIMS Metadata
    • DBD + PSB = IMS DB SchemaDA BB DCDBD, PCB,CopybooksPhysical Disk DataIMS HierarchyProgram I/O AreaA B C99a b c de f j k lAB Dh iC DBD/PCB Schemag
    • IMS MetadataDefined inDBDDefined inAppl Copylibs(IMS Java)01010100101111010101000010011101001011111011011001000101001101011101110001100100100110100010111001010110101011011001010100101010010101010100001110111011001010111010100000101010111011000100110101110101001001101100000101001001101011101011001001001001ord# lastName firstName payment type dateINT CHAR CHAR CHAR CHAR DATE1010(IMS Java)Defined inXML Schema:Local file orIMS Catalog<PurchaseOrder number=“ ”><lastName> </lastName><firstName> </firstName><date> </date><payment type=“ ”> </payment>113246IBMIMS04/26/1968MC 5414 2263 4895 1145
    • Changes to DBD Statement• DBD• ENCODING=• Specifies default encoding of all character data in the database defined by this DBD• Value can be overridden in individual segments or fields• SEGM• EXTERNALNAME=• Optional alias for NAME= parameter used by Java application programs to refer to segment• FIELD• CASENAME=• Name of the map case when alternative mappings are defined for fields in a segment• DATATYPE=1111• DATATYPE=• Specifies the external data type of the field• EXTERNALNAME=• Optional alias for the NAME= parameter used by Java application programs to refer to 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: 1- to 256-character field added to DBDGEN statement
    • Data Types• Data types have multiple metadata elements• 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 thedatabase• 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 knowthis)1212this)• 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 byUniversal drivers to marshal/unmarshal data• Can be part of a Struct or Array element
    • Changes to PSB PCB Statement• PCB• EXTERNALNAME=• Optional alias for the PCB label or the PCBNAME= parameter• Java application programs use the external name to refer to the PCB• REMARKS=1313• REMARKS=• Optional user comments: 1- to 256-character field added to PSBGENstatements
    • DBD sourceLocal File for IMS Java MetadataLocalFilePSB sourceIMS ExplorerCOBOL/PLIsource1414FilePSBNAMEDataBaseView.jarIMS Explorer parses DBD, PSB and COBOL or PL/I source code• Generates PSBNAMEDataBaseView.java and .class files• Export as .jar file to file system where application is deployedKey points• Metadata deployed to multiple file locations• Metadata offline and not guaranteed to be current
    • IMS Catalog for IMS Java MetadataContains IMS program & database resources, and relevant application metadataDatabase DefinitionsSegmentsFieldsIMS Catalog MetadataApplication Program SpecificationsArrays and StructuresField data types and data type conversionField redefinesAlternative Field maps for a segment1515IMS Catalog MetadataExtendedPSB sourceCOBOL & PLIsourceIMS ExplorerExtendedDBD sourceACBLIBDBDGEN / PSBGEN / ACBGENPSB & DBDsource
    • ExtendedDBD sourceIMS Catalog LifecycleCatalogExtendedPSB source PSBLIB++DBDLIB++PSBGENDBDGENACBGENIMS ExplorerCOBOL/PLIsourceDFS3PU00ACBLIB++PSBLIBDBDLIBACBLIBPopulate Utility willpopulate catalogfrom ACBLIB1616DB Client RouteACBGEN will populate ACBLIB and catalog in same UOW• Populates ACBLIB with standard ACB info and extended info• Populates the catalog with extended infoKey points• Trusted, online, IMS metadata stored in the IMS catalog• 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
    • The IMS Catalog Database• Contains metadata related to an IMS system’s databases & programs• DBD and PSB and Application information• IMS PHIDAM/OSAM HALDB database• Defined with 4 Data Set Groups (DSGs)• One Secondary Index• Unique feature –> “Unregistered Catalog Database”• DBRC use is optional for the IMS Catalog database1717• DBRC use is optional for the IMS Catalog database• Only HALDB that isn’t required to be defined to DBRC• IMS can manage allocation/creation of catalog database• Done via parameters in the “CATALOG” section of DFSDFxxxPROCLIB member
    • New Utilities for the IMS Catalog• IMS Catalog Populate utility (DFS3PU00)• Loads or inserts records into the IMS catalog• Estimates the size of the IMS catalog data sets• ACB Generation and Catalog Populate utility (DFS3UACB)• Generates the ACBLIB members and loads the IMS catalog metadata in one unitof work• IMS Catalog Alias Names utility (DFS3ALI0)• Defines a complete list of catalog aliases to IMS• IMS Catalog Copy utility (DFS3CCE0, DFS3CCI0)1818• IMS Catalog Copy utility (DFS3CCE0, DFS3CCI0)• Copies IMS catalog database definitions and metadata between IMS systems• Migrate an IMS catalog database from a test to production environment• Copy a production IMS catalog database to another installation for system cloning or DRpurposes (etc…)• IMS Catalog Partition Definition Data Set utility (DFS3UCD0)• When DBRC is not used to manage the catalog database: creates the IMScatalog partition definition data set and populates it with information about theIMS catalog HALDB partitions• IMS Catalog Record Purge utility (DFS3PU10)• Removes unnecessary versions of IMS catalog records from the IMS catalogdatabase based on criteria that you specify
    • Application Programming with IMS Catalog• IMS catalog PSBs resident for application programs• DFSCP000 - High-level assembler and COBOL applications• DFSCP002 - PL/I applications• DFSCP003 - PASCAL applications• PCBs included to support different catalog processing models:• DFSCAT00 - Primary PCB to access all data in the catalog database1919• DFSCATSX – Used access the catalog database via the catalog 2nd index• DFSCATX0 – Used to access the catalog 2nd index as a database• All catalog processing is performed with PROCOPT=G• New “GUR” DL/I call to access Catalog DB records• Application programs can use the GUR call
    • NEW “GUR” DL/I Call• Get Unique Record• Retrieves an XML formatted Catalog database “record”• Restricted to use with the IMS Catalog database• Functions like a GU followed by a series of GNP calls• Less overhead than issuing GU & GNP to retrieve all the metadata for acatalog member• Returns the entire database DBD or PSB record in one call2020• Using an AIB token, the call can be continued if the I/O area is too small forthe entire catalog database record• Data returned in XML format• The XML schemas are included in the IMS.ADFSSMPL data set:• DFS3XDBD.xsd (for DBD records)• DFS3XPSB.xsd (for PSB records)• Support added for DFSDDLT0 and IMS REXX
    • • New SSA command code “O”• Non-key field definitions not required in the DBD• Allows fields defined in database metadata to be used• Search by position and length vs. field name• 4 byte position, hex value• 4 byte length, hex valueIMS 12APAR PM65139PTF UK81837 orPTF UK81838SSA Command Code “O”: Qualify by Position2121• 4 byte length, hex value• Valid for HDAM, HIDAM, PHDAM, PHIDAM and DEBD databases• Valid for GU, GHU, GN, GNP, GHNP, ISRT calls• Plays well with other command codes• “GE” status code returned if field not found• Support for DFSDDLT0 and IMS REXX• Performance will be the same as non-key field search
    • SSA with command code, position and length0 1 2 3123456789012345678901235678901234567LAST1 FIRST1 555-1111 1999999LAST2 FIRST2 555-2222 2999999LAST3 FIRST3 555-3333 3999999Database SegmentsField Offset LenLASTNAME 1 10DBD• SSA with “O” command code, position and length2222COBOL CopybookGU TELEBOOK*--(LASTNAME=LAST2 )GU TELEBOOK*O-(000000010000000A=LAST3 )GU TELEBOOK*O-(0000000B0000000A=FIRST1 )Field Offset LenLASTNAME 1 10FIRSTNME 11 10EXTENSIN 21 10ZIPCODE 31 7Offset Length‘bb‘ Status Code: segments returned successfully(Offset is relative to 1 vs. zero)
    • • Support for IMS Universal Drivers• Allows users to issue queries qualified on non-searchablefields and have a field’s position and length generatedautomatically in the qualified SSA• SQLIMS12APAR PM69378PTF UK81917SSA Command Code “O”: Qualify by Position2323• Universal Drivers will detect a non-searchable field in the whereclause based on database metadata and will internally convertthe SSAList qualification• DLI• Universal Drivers will detect a non-searchable field in theSSAList based on database metadata and will internally convertthe SSAList qualification
    • IMS Catalog Benefits• Trusted, online source for IMS metadata• Direct access to IMS metadata in the catalog• Leveraged by the Universal Database Drivers• No need for “local” Java metadata classes2424
    • IMS 12Database Enhancements25
    • Dynamic Full Function Database Buffer PoolsSolution• Provide for dynamic change to an OSAM or VSAM buffer poolwithout recycling the IMS system to pick up the change• Change number of buffers in a buffer pool• Add or delete a buffer pool• Reassign database data set to another buffer pool• Commands used to add, change, or delete buffer pools• DFSDFxxx – OSAMxxx and VSAMxxx sections w/POOLID=• UPD POOL TYPE(DBAS) SECTION(OSAMDAY)26• UPD POOL TYPE(DBAS) SECTION(OSAMDAY)• Affected pool activity is quiesced• VSAM DB data sets closed and reopened• OSAM DB data sets are not closed• Affected pools are destroyed and rebuiltValue• Ability to dynamically adjust buffer pools to meet business needs• Eliminates system down time for buffer pool definition changes• Improves application performance with improved DB performance
    • Increased VSAM Buffer PoolsSolution• Provide for 255 VSAM database buffer pools• Previously VSAM was limited to 16 pools• Specify up to 255 POOLID statements in DFSVSMxx orDFSVSAMP data setValue27Value• More VSAM database buffer pools increases capability to tuneVSAM pools for better database performance• Improves application performance with improved DB performance
    • Solution• Storage for selected pools can now be page fixed in 64-bit realstorage• IMS PSB Scheduling pools (TM/DB, DBCTL, DCCTL)PSB CSA pool PSB Work Pool• Pools related to Full Function Database usage (TM/DB, DBCTL)DLI PSB pool DMB Pool DB Work poolFull Function DB Storage Enhancement28• Pools continue to be allocated in 31-bit virtualValue• Could reduce use of 31-bit fixed real frames, relieves 31-bit realstorage constraint, and improve application scheduling performance• Customers with large pools who previously could not page fix thesepools due to storage constraints may now be able to page fix dueto an increase in available real storage
    • Additional Full Function Database EnhancementsSolution• Status of randomizers and partition selection exit routines• Displayed when FF database is Opened/Closed via command• New DFS2291I diagnostic message for abend U3310 for long locksituation• Provides information about lock resource holder and timeout victim• RACF user ID is saved in log type 9904 for batch jobs• DFS0730I message replaces IMS U0080 abend for open/close/EOV errors29• DFS0730I message replaces IMS U0080 abend for open/close/EOV errors• DLI Batch jobs wait rather than terminate in the event of a Coupling Facilityswitch• Eliminates the U3303 abend in this situation• HALDB Partition reuse after structure change• Reuse of HALDB partition DB names for non-HALDB databases• Improved use of local DMB numbers to stay within 32,767 limit• Reuse of numbers so that a cold start is not required when these numbersreach the maximum
    • Additional Full Function Database EnhancementsSolution (cont’d)• Message DFS993I (CSA PSB|DLS PSB|PSBM pool too small) is sent tothe system console• In previous releases, IMS systems without a master terminal (e.g. DBCTL)would not receive this message• Universal Drivers support• Arrays and structs• Segment maps30• Segment maps• Variable-length database segmentsValue• Scalability by reusing unused local DMB numbers• Serviceability by providing additional information• Availability by reuse of DMB numbers and eliminating of some hangs• Enhance the availability and usability for HALDB, OLR and batch users of IMS
    • DRA Open Thread TCBEnablement for CICS ThreadsafeSolution• Enables DBCTL support for CICS Open Transaction Environment TCBs(CICS Threadsafe)• Allows EXEC DLI and CALL DLI from CICS applications to run on aCICS thread• Eliminates the creation of DRA Thread TCBsPerformance31• Eliminates the creation of DRA Thread TCBs• Requires CICS TS 4.2• Compatibility APARs for use of CICS TS 4.2 with IMS 10 and 11IMS 10 (PM31730) IMS 11 (PM31729)Value• Eliminates costly TCB switches• Reduces CPU usage• Increases throughput for CICS / DBCTL users• Reduces use of 24-bit Local System Queue Area (LSQA)
    • IMS 12 Fast Path Enhancements32
    • Fast Path 64-bit EnhancementsSolution• Fast Path subpools made more dynamic• Pools are expanded before buffers are needed• Pools may be compressed• User may set initial size of pools• Additional buffers are moved from ECSA to 64-bit storage• FLD calls33• FLD calls• SDEP calls during /ERE and XRF tracking• QUERY POOL command enhancements• Summary statistics available (ie, subpool status)• SHOW(ALL) output reformattedValue• Reduce ECSA usage• Smarter usage of subpools
    • Fast Path Data Entry Database (DEDB)Secondary Index EnablementSolution• Secondary indexing infrastructure provided for Fast Path DEDBdatabases similar to existing IMS FF database secondary indexfunction• HISAM and SHISAM database structures supported34• Tools or utilities to build a secondary index database for DEDBdatabases exploiting this function could be separately offeredby IBM or other vendorsValue• Usability enhanced by providing Fast Path DEDB secondaryindexing infrastructure in IMS to access a DEDB databaseusing a secondary key sequence• Access via an alternate key
    • Fast Path Logging Enhancement• Solution• FULLSEG option is available on DBRC commands• INIT.DB, INIT.DBDS, CHANGE.DB, CHANGE.DBDS• Option to log entire segment for update calls in x‘5950’ logrecord (instead of just changed data)• EXIT parameter on the DBD and SEGM statements forDEDBs35DEDBs• Option to not log DLET and REPL call “before images” inx’99’ log record• Value• Segment extraction from transaction log facilitated, CDC exitnot needed to retrieve the full replaced segment any more• Decreased logging overhead and performance improvementwhere logging is a constraint
    • Fast Path ServiceabilitySolution• DEDB data sharing enhancement• When an IMS system sends a notify message to its datasharing partner systems, new message DFS0066I is issuedfor each responding system• Any partner that fails to respond causes the IMS that originallyServiceability36• Any partner that fails to respond causes the IMS that originallysent the notify message to issue DFS3770W• User may need to cancel the IMS for which there is noDFS0066I messageValue• User can determine which IMS is non-responsive, providing afaster response to a system hang
    • IMS 12 SystemsManagement Enhancements37
    • IMS Repository and Usage for Dynamic ResourceDefinition (DRD) ResourcesSolution• Simplifies IMSplex DRD resource management• Provides a single centralized store for the DRD resource definitions• Usage of IMS repository is optional, DRD users can continue to useResource Definition Data Set (RDDS) instead of the repository• IMS Repository can be shared• Allows DRD resource definition changes to be made in repository and rolled38• Allows DRD resource definition changes to be made in repository and rolledto one or more active IMS systems• Uses a “Catalog Repository” to manage resource repositories• Requires OM, RM, SCI and new Repository ServerValue• Provides a central source of information about IMS resources• Simplified management of DRD resource definitions• Eliminates the need for managing multiple Resource Definition Data Sets(RDDS) for each IMS
    • Import Command EnhancementSolution• IMPORT command may be used to update resources• Previously, IMPORT was not allowed for existing resources• Updates required resource deletion then IMPORT• IMS 12 allows IMPORT for existing resources• OPTION(UPDATE) must be included in command39• OPTION(UPDATE) must be included in command• Resource is updated if it already existsValue• Usability of IMPORT and DRD is enhanced
    • ACB Member Online ChangeNAMEONLY Option• OPTION(NAMEONLY) added for member online change• Command processes only the named member(s) of the stagingACBLIB (to be used for new or existing PSBs, and new DBDs)INIT OLC TYPE(ACBMBR) PHASE(PREPARE) NAME(name1,name2,…)OPTION(NAMEONLY)40• Benefit• Performance enhancement• Significantly reduces processing time and I/Os used to process OnlineChange function• Without OPTION(NAMEONLY)• Command reads all members of staging and active ACBLIBs• With OPTION(NAMEONLY)• Command processes only the specified member and DBDs inPSB intent list
    • Extended Address Volume (EAV) Enhancement• Add Extended Address Volume support for OSAM and non-VSAMsystem data sets• Data sets can be allocated in the Extended Address Space (EAS) of an EAVvolume• Addressable disk storage increased beyond 65K cylinders• New architecture will support 100’s of Terabytes on single volume• Uses new 28-bit cylinder/track addresses• Provide EAV support for the following data sets, and more…41• Provide EAV support for the following data sets, and more…• OSAM (Overflow Sequential Access Method) DB data sets• OSAM Database Data Sets• Restart Data Set (RDS)• Message Queue Blocks Data Set, Long/Short Message Queue Data Sets• Online Log (OLDS), System Log (SLDS) and Write Ahead (WADS) Data Sets• IMS SPOOL Data Sets• BPE External Trace Data Sets
    • Extended Address Volume (EAV)• Past volume growth limited by existingtrack addressing architecture• EAV = a volume with more than 65,520cylinders• 3390 Model A• 1 to 268,434,453 cylinders423390-3 3390-93390-273390-543390-A“EAV”3 GBMax cyls: 3,3399 GBMax cyls: 10,01727 GBMax cyls: 32,76054 GBMax cyls: 65,520 100s of TBsMaximum Sizes• 1 to 268,434,453 cylinders• Architectural EAV maximum
    • EAV Key Design PointsCylinder-managedspace(Cyls Beyond First 65,520)• EAV maintains 3390 track format• Track-managed space:• Area on EAV within the first 65,520 cyls• Space allocated in track or cyl increments• Storage for “small” data sets43EAVTrack-managedspace(Cyls Beyond First 65,520)(First 65,520 Cyls)• Cylinder-managed space:• Area on EAV located above first 65,520 cyls• Space is allocated in multicylinder units• Storage for “large” data sets• New DSCB format type to identify EAS data sets• New formats (Format 8 and 9) in VTOC• Data set resides in cylinder-managed space
    • IMS Data Sets with EAV Support (both non-VSAM & VSAM)• BPE external trace data sets• OSAM database data sets• VSAM database data sets• Online Log Data Sets (OLDSs), includinglarge OLDS (ie. greater than 64 KB tracks)• Write Ahead Data Sets (WADSs)• Restart Data Sets (RDSs)• Message Queue Blocks data sets• Long and Short Message data sets• Terminal devices with UNITYPE = SPOOL• Database Image Copy utility (DFSUDMP0)data sets• Database Image Copy 2 utility (DFSUDMT0)data sets• Database Change Accumulation utility(DFSUCUM0) data sets• Local online change data sets(IMS.MODSTAT)• Global online change data sets(IMS.OLCSTAT)44• Terminal devices with UNITYPE = SPOOLor DISK• RESLIB data sets (IMS.SDFSRESL)• MODBLKS data sets for Online Change(IMS.MODBLKSA and IMS.MODBLKSB)• Application Control Block library (ACBLIB)data sets• DBRC RECON data sets (non-PRA)• Partitioned Data Set Extended (PDSE) datasets (IMS.SDFSJLIB, PGMLIB, SMPLTS, andExternal Subsystem Attach Facility (ESAF) loadlibraries)(IMS.OLCSTAT)• Time-Controlled Operations (TCO) data sets• System Log Data Sets (SLDSs)• Recovery Log Data Sets (RLDSs)• HALDB Indirect List Data Sets (ILDSs)• IMS Repository data sets• MFS map library data sets produced by theMFS Language and Service utilities(IMS.FORMAT)• IMS Trace facility external trace data sets• IMS Monitor output data setsGSAM data sets cannot be allocated on an EAV volume !
    • Extended Address Volume (EAV)Enhancement for Non-VSAM Data Sets• Prerequisites• Software requirements• z/OS 1.12• Hardware requirements• DS8000, DS8700• 3390 Model A45• 3390 Model A• Benefits• Provide relief to customers running out of addressable disk storage• Supports the placement of more data sets on a single volume• Allow users to manage fewer numbers of larger volumes• Less need for multi-volume OSAM
    • Logger EnhancementsSolution• Extended Format support for OLDS and SLDS• Allows OLDS and SLDS to be striped• Striping allows multiple concurrent I/Os for sequential processing• Data set is spread across multiple volumes• Increased logging rates / throughput• OLDS buffers may be in 64-bit virtual storage (frees ECSA)• WADS management changed to be more efficient46• WADS management changed to be more efficient• Track groups no longer used• WADS written in simple wrap-around fashionValue• Increased logging speed and bandwidth• Reduced ECSA usage• Smaller WADS• Better use of storage system cache by WADS withnew wrap-around fashion
    • Command Enhancements• Enhancements to existing commands and new commands• CQS trace command enhancements• DBRC command enhancements• Dynamic database buffer pool command enhancements• Dynamic resource definition (DRD) command enhancements• Fast Path secondary index command enhancements47• Fast Path secondary index command enhancements• HALDB command enhancements• IMS Connect command enhancements• MSC command enhancements• IMS repository function command enhancements• OTMA command enhancements
    • Command Enhancements• Enhancements are focused on type-2 commands for theOperations Manager (OM) environment• Benefits• Support of new IMS 12 functions48• Improved manageability
    • Syntax Checker Enhancements• Supports PROCLIB members for IMS 12 / 11 / 10• IMS 9 PROCLIB members are not supported• All previously supported members are supported• Newly added parameters of these members are supported• Support added for Repository Server configuration member• Support added to view/save parameters in a custom order49• Support added to view/save parameters in a custom order• Prior to IMS 12, only alphabetical order was allowed• Benefits• Support of new IMS 12 PROCLIB members• Improved usability with custom order of parameters
    • CQS Traceability Enhancements• Preserve CQS structure event trace entries by separatingand categorizing trace data into new trace tables• Existing CQS structure trace table (STR) can quickly fill, wraparound, and lose critical trace entries• Two new BPE trace tables are available to track events• CQS Structure Event trace table (SEVT) – for structure events• CQS Structure Overflow trace table (OFLW) – for overflow events50• CQS Structure Overflow trace table (OFLW) – for overflow events• Benefits• Improves CQS serviceability• Retains critical trace data for longer periods of time• Improve diagnostics for certain Shared Message Queuestructure-related problems
    • IMS Scheduling Log Record EnhancementsSolution• Enhanced 07, 56FA and 0A07 log records• New fields to show combined System z Application AssistProcessors (zAAP) and System z Integrated InformationProcessor (zIIP) specialty engine time• Existing time field now used only for general CP timeUsability51Value• For IMS applications that include Java processing, the IMS logrecords will now indicate how much of the application processingtime is on a specialty engine vs. a general processor
    • VSAM Control Area Reclaim• When VSAM control areas (CIs) in a control area become free• Control area is automatically reused for new inserted records• No need to reorganize the data sets• IMS Version 12 exploits VSAM CA ReclaimReq’s z/OS 1.1252• IMS Version 12 exploits VSAM CA Reclaim
    • IMS 12 Transaction Managementand Connectivity Enhancements53
    • Sysplex Serial ProgramManagement Disablement OptionSolution• For IMS Shared Queues users with a Resource Structure• Provide new parameter to allow Sysplex Serial ProgramManagement to be an option• User can disable the functionUsability54• User can disable the function• Default is to use SSPM as with previous IMS versionsValue• Provides a way to turn off the function for customers who do notwish to use it
    • Asynchronous IMS to IMS TCP/IP Messages• IMS applications may send messages via TCP/IP to other IMSsystems• Message is sent with ISRT call using ALT-PCB• OTMA destination descriptor or DFSYDRU0 exit routine selectsdestination• Message invokes IMS transaction on receiving IMS system55• Message invokes IMS transaction on receiving IMS systemIMS1 IMS Connect1 IMS2IMS Connect2ISRT ALTPCBDescriptorICON1OTMAXCF XCFTCP/IPOTMATRANPGM
    • Asynchronous IMS to IMS TCP/IP Messages …• Value• Eliminates need for customer RYO gateway application to receiveoutput message and send it to the other IMSIMS1 IMS Connect1 IMS2IMS Connect2CustomerGateway ApplicationResume Tpipe OISRT ALTPCBO56IMS1 IMS Connect1 IMS2IMS Connect2ISRT ALTPCBDescriptorICON1OTMAXCF XCFTCP/IPTran output SendOnlyTMAXCF XCFTCP/IP TCP/IPISRT ALTPCBDescriptorICON1OTMAOTMA
    • Multiple Systems Coupling (MSC) TCP/IP LinkSolution• MSC adds a new physical link (MSPLINK), TYPE = TCPIP• MSC communicates with IMS Connect via Structured Call Interface(SCI) within a IMSplex to send/receive transaction messages andresponses via the TCP/IP network• IMS Connect manages the TCP/IP communications• MSC manages the message processing57Value• Increased usability by providing additional link type, allows installations tostandardize on TCP/IP• Increased availability if VTAM/SNA and TCP/IP are used together for backup• Expect greater bandwidth than VTAMIMS1 IMS2IMSConnectIMSConnectSCI SCITCP/IP
    • IMS Connect Type-2 CommandsSolution• Type-2 commands may be used with IMS Connect• Commands are issued from OM client• TSO SPOC, IMS Control Center, REXX SPOC API, Batch SPOC• New Type-2 commands for IMS Connect resources• QUERY IMSCON and UPDATE IMSCON• IMS Connect Resources58• IMS Connect Resources• Datastore, Link, Port, Alias, Converter, etc.• Can coexist with the previous WTOR and z/OS Modify commands• All functionality is included in the type-2 commandsValue• IMS and IMS Connect may be controlled from a single point of control• One command may receive consolidated output from multiple IMS Connects
    • Additional IMS Connect EnhancementsSolution• Ability to refresh XML converters without restarting IMSConnect• Provide RACF Userid caching – reduces MIPS• Return actual RACF return codes – more info for securityerrors• Recorder Trace data capture – new trace points• Commit Mode 0 (CM0) ACK NoWait for RYO clients59• Commit Mode 0 (CM0) ACK NoWait for RYO clients• Partial read status – new client connection status indicatingread/wait• Load modules for IMS-provided exits – no need toassemble/bindValue• Enable customers to use IMS Connect more easily whileproviding better performance and diagnostics
    • Enhanced APPC/OTMA Synchronous Shared QueuesSolution• Provide option to use MVS Cross Coupling Facility (XCF) forcommunication instead of RRS between Shared Queues Front-End and Back-End systems• IMS is the sync point manager rather than RRS• AOS= parameter specifies new options to use XCF• New AOSLOG= parameter to request 6701 log record60• New AOSLOG= parameter to request 6701 log record• Remove RRS dependency for APPC’s synchronousconversation and OTMA’s Commit Mode 1 (send-then-commit)with sync level of NONE or CONFIRMValue• Improve performance and simplify the syncpoint process byusing XCF
    • Enhanced OTMA SecuritySolution• One RACF ACEE for the same userid is created and cached forall of the OTMA clients• New maximum ACEE aging value of 99,999 secondsValue61Value• Reduce the system storage for RACF ACEEs while providingbetter security and performance• More efficient usage of storage for caching RACF ACEEs• Earlier notification of OTMA clients when IMS is terminating• Higher IMS availability for applications
    • IMS 12 Database RecoveryControl Enhancements62
    • DBRC EnhancementsSolution• Output for /RMLIST command entered through the OM API can exceed theprevious 32K limitation• Output size is restricted by the DBRC private storage available for buffering theoutput message or OM limitations• Enhancements to DBRC commands:• CLEANUP.RECON – now includes CA record data• LIST.HISTORY – increased timestamp precision/new data• INIT.CA, INIT.IC, NOTIFY.CA, NOTIFY.IC – VOLLIST parameter now optional ifdata sets catalogedIMSRECONIMSIMS63data sets cataloged• LIST.DB/LIST.DBDS – new NORCVINF suppresses ALLOC,IC,RECOV,REORG• INIT.CAGRP, CHANGE.CAGRP – retention period added to GRPMAX• GENJCL – userkeys increased from 32 to 64 and new %DBTYPE kwd added• Add user data fields to the DBDS recovery records (IC, RECOV, REORG,and CA)Value• Improved reliability, availability, maintainability, serviceability, and usabilityof DBRC and the RECON data sets• Increased /RMLIST data available for OM API users (e.g. TSO SPOC)• Better able to maintain clean RECON data sets
    • DBRC Migration/CoexistenceSolution• Provide support for migration and coexistence from IMS 10 and11 to IMS 12• All database records are read during upgrade of the RECON dataset to IMS 1264set to IMS 12Value• Eases migration to IMS 12
    • IMS 12 Additional References65
    • • Discusses all IMS 12capabilities from a userperspective• Draft available for freeIMS 12 Redbook Announcement66• Draft available for freedownload at IBM Redbooks
    • • Updated to include IMS10, IMS 11 and IMS 12functionsAn Introduction to IMS – Second Edition67
    • IMS 12 Performance White Paper is Available• Detailed results of ourinternal performance tests• Environment, functionstested, MIPS and throughputresults68results• Available for download atIMS Version 12Performance Summary
    • IMS 12 Announcement Letter 210-315http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-315IMS 12 Article in IBMSystems Magazinehttp://www.ibmsystemsmag.com/mainframe/IMS_v12/34748p1.aspxIMS 12 Information69http://www.ibmsystemsmag.com/mainframe/IMS_v12/34748p1.aspxIMS 12 Info Center & Release Planning(GC19-3019)http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.ims12.doc/imshome_v12.htm
    • Data Management Communities for IMSData Management Community – share and interact on all DataManagement topics with peers around the worldwww.ibm.com/software/data/management/community.htmlIMS Community – share and interact with IMS peers around the worldhttp://www-01.ibm.com/software/data/ims/community/IMS Regional User Groups – find a meeting near youwww.ibm.com/software/data/ims/usergroups.htmlIMS Application Development Forum70IMS Application Development Forumwww.ibm.com/developerworks/forums/forum.jspa?forumID=1632Information Champions – recognizes individuals who have made themost outstanding contributions to the Information Managementcommunitywww.ibm.com/software/data/championRational Cafes – for host application programming languageswww.ibm.com/software/rational/cafe/index.jspaCOBOL Cafe – IMS Hub for application programmerswww.ibm.com/software/rational/cafe/community/cobol/ims?view=overview
    • IMS 12 Summary- IMS Repository andUsage for DRD Resources- IMPORT CommandEnhancement- ACB Member Online ChangeSystems Management-IMS to IMS TCP/IPCommunications- MSC TCP/IP SupportTransaction Managementand ConnectivityFull Function Database- FF Dynamic DB Buffers- FF DB Storage Enhancement- Additional FF EnhancementsDatabase ManagementUsabilityScalabilityPerformanceReliabilityServiceability71- ACB Member Online ChangeEnhancement- Logger Enhancements- Syntax CheckerEnhancements- CCTL/DRAOpen Thread TCB Support- Extended Address Volume- VSAM Control Area Reclaim- OTMA TCP/IP Support- IMS Connect Type-2Commands Support- Additional ConnectEnhancements- OTMA Security Enhancements- APPC/OTMA Synch SQ- Enhanced CQS TraceabilityFast Path- FP Buffer Manager 64 bitEnhancements- FP DEDB Secondary IndexEnablement- Additional FP EnhancementsDBRC- DBRC Enhancements- Migration/Coexistence
    • IMS Version 13IMS 13 - AgendaStatus of IMS VersionsMigration and CoexistenceSystem EnhancementsDatabase and DBRC EnhancementsTransaction Manager and Connectivity Enhancements72Transaction Manager and Connectivity Enhancements72
    • IMS Version 13Supported Migrations and CoexistenceIMS 12 to IMS 13– Upgrade RECONs from IMS 12 to IMS 13– Databases are compatible– Application programs are compatible73IMS 11 to IMS 13– Upgrade RECONs from IMS 11 to IMS 13– Databases are compatible– Application programs are compatibleCheck Release Planning documentation at GA for additionalprerequisites/coexistence/migration items
    • IMS Version 13Software PrerequisitesMinimum software level prerequisites– z/OS V1R13 (5694-A01)• RACF (included in separately orderable SecureWay Security Server), orequivalent, if security is used• High Level Assembler Toolkit Release 5 (5696-234)• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V1374• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V13– IRLM 2.3 if the IRLM is used* subject to change
    • IMS Version 13Software Prerequisites ...Minimum software levels for optional functions– Java Dependent Regions requires JDK 6.0.1– ISC TCP/IP requires CICS 5.1– Depending on the environment, the IMS Universal Drivers require:• IBM JDK 6.0.1 or later• DB2 V9.1 or later75• WAS V7 or later• CICS V4.1 or later– DB Versioning requires implementation of the IMS Catalog* subject to change
    • IMS Version 13Software Prerequisites ...Minimum software levels for optional functions ...– IMS 13 supports interactions with• DB2: Versions 9, 10• CICS: Versions 3.2, 4.1, 4.2, 5.1– CICS 5.1 (newly announced) is required for ISC TCP/IP support• Requires z/OS 1.1376• Requires z/OS 1.13• MQ for z/OS: Versions V7.0.1, V7.1– Note V6 EOS was September 2012– 7.01 introduced MQ message expiry interfacing with IMS transaction expiration– 7.1 enhanced the expiry support and support for OTMA resource monitoringprotocol messages* subject to change
    • IMS Version 13Hardware PrerequisitesIMS 13 runs only on 64 bit processors running in z/Architecture mode– Processors must also support the Long-Displacement Facility of thez/Architecture– ESA mode is not supported– For a list of z/Series machines see: www.ibm.com/systems/z/hardware/z900 machines must be at GA2 level (microcode level 3G or later)77z900 machines must be at GA2 level (microcode level 3G or later)
    • IMS Version 13Hardware Prerequisites ...Sysplex Data Sharing (including Data Caching and VSO Data Sharing)– Coupling Facility (CF) level 9, or laterShared Queues and Shared EMH support– Coupling Facility level 9 or later– System-managed CF Duplexing78• CF level 12, or later and bidirectional CF to CF linksEAV support for non-VSAM data sets– EAVs are supported on DS8000 at microcode level R4.0 via bundle64.0.175.0 (Sept 2008) or higher
    • IMS Version 13IMS 13 System EnhancementsReduced Total Cost of Ownership (TCO)Concurrent Application ThreadsIMS Command EnhancementsIMS CQS EnhancementIMS DRD Enhancement79IMS DRD EnhancementIMS User Exit EnhancementsIMS Security Enhancements/DIAG Command Enhancements
    • IMS Version 13Reduced Total Cost of OwnershipCross-platform focus on reducing mainframe software costsMajor focus on reducing CPU usageChanges throughout IMS to improve performance, reduce storageusage and reduce CPU used to run IMS– Using more efficient storage services– Improved algorithms– Reducing pathlength80– Reducing pathlength– Optimizing frequently used processes– Latch / lock improvements– Storage reductions– Use of zEnterprise hardware functionsBenefits– Improved performance, lower cost per transaction, reduced cost ofownership.
    • IMS Version 13Specific Reduced TCO EnhancementsIMS logger LOG latch contention reduction– Improves usage of log latch and log buffer management for increased loggingbandwidth and more efficient processingShared queues local first optimization now applies to program-to-program switch messages as well as ordinary input messages– Avoids false scheduling on another IMS when the local IMS can process theprogram-to-program switch messageExploitation of pageable 1M pages81Exploitation of pageable 1M pages– Based on usage of new zEC12 processors with Flash Express storage andz/OS 1.13 (Dec. 2012)– Provides improvements in dynamic address translation and usage oftranslation lookaside buffer (TLB)DB Space Management Block Serialization Latch Improvements– Split from single to multiple latches to improve heavy BMP workloadsMEMDSENQMGMT Exploitation– More efficient memory-based data set ENQ management improves allocationof large number of data sets
    • IMS Version 13Other Reduced TCO EnhancementsOTMA YTIB chain changed from a single linked list to a hash table, toimprove FINDDEST performance.Convert OTMA and IMS Connect STORAGE calls to CPOOLRemove unnecessary clearing of OTMA buffersDFSCPY00 improved SVC directory entry search algorithm and removalof IVSK instructions.OSAM CML Lock Reduction82OSAM CML Lock ReductionGeneral instruction optimization (replacing STCK with STCKF, longdisplacement facility exploitation)IMS cache manager spin loop eliminationCQS mainline modules changed to use branch-relative branchingCache efficiency improvements (DPST blocks packed into a singleIPAGE to keep cache references localized)IMS page load service algorithm optimizationIMS dispatcher optimizations
    • IMS Version 13Concurrent Application Threads EnhancementPartition Specification Table (PST) used for– Active dependent regions (MSG/BMP/IFP/JMP/JBP)– CICS/DBCTL threads– Open Database Access threadsCustomers continue to require more PSTs!– 31 dependent regions - 1980 (IMS 1.1.6)83– 31 dependent regions - 1980 (IMS 1.1.6)– 999 dependent regions - 1995 (IMS 5.1)– 4095 dependent regions - 2013 (IMS 13)Related parameters– MAXPST=– PST=– MAXTHRDS= for ODBM– MAXTHRDS=, MINTHRDS= for DBCTL
    • IMS Version 13MAXPST= parameterUsed in DBC, DCC, and IMS procedures– Specifies the maximum number of PSTs for an online IMS controlregion– Default is 255 (no change)– Maximum value is 4095 in IMS 13 (quadrupled)84Controls maximum number of– Active dependent regions (MSG/BMP/IFP/JMP/JBP)– CICS/DBCTL threads– Open Database Access threadsReducing MAXPST= requires a cold start
    • IMS Version 13Benefits of the Concurrent Thread Enhancement(Increasing MAXPST)Customers can now have increased capacity/scalability for their IMSsystems– Larger capacity for mergers/acquisitions• Without having to add more IMS images– Increased workloads with latest zEnterprise hardware• Room for vertical growth85• Room for vertical growth– More regions for IMS 13 synchronous program switch function, alsosynchronous callout, distributed syncpoint/etc.• Longer region occupanciesMAXPST should no longer be a limiting factor in IMS growth
    • IMS Version 13ESAF support in Java Dependent Regions (JDR)With IMS 13, there are two methods for accessing DB2 from JDRs– Access via the previously existing DB2 RRSAF interface– Access via the standard ESAF interfaceWith IMS 13, the ESAF interface can be used in JMP/JBP regions toaccess any ESAF defined to the IMS control region– WebSphere MQ, DB2, WOLA (WebSphere Optimized Local Adapter)86Support for the SSM= parameter on the JMP/JBP dependent regionstartup JCLOnly one ESS connection method allowed per JMP/JBP– Default ESS connection method is DB2 RRSAF• No impact to existing usersBenefits– Simpler, more efficient, and more consistent interface
    • IMS Version 13IMS Command Enhancements OverviewDBRC command enhancementsDEDB Alter command enhancements/DIAGNOSE SNAP command enhancementHALDB command enhancementsIMS Connect type-2 command enhancements87IMS Connect type-2 command enhancements– Dynamically create data store definitions (CREATE IMSCONTYPE(DATASTORE))– Dynamically create port definitions (CREATE IMSCON TYPE(PORT))– Query XML converters loaded in IMS Connect (QUERY IMSCONTYPE(CONVERTER)
    • IMS Version 13IMS Command EnhancementsEnhancements are focused on type-2 commands for the OperationsManager (OM) environmentBenefits– Support of new IMS 13 functions88– Improved manageability
    • IMS Version 13IMS CQS EnhancementWhen IMS Common Queue Server (CQS) rejects a z/OS STOPcqsjobname command because CQS clients are still connected(CQS0300I), CQS issues a new message, CQS0301I, for eachconnected client– Enables the operator to shut down or quiesce the connected CQS clientsso that the CQS address space can be stopped89Benefits– Improved manageability for CQS
    • IMS Version 13IMS DRD EnhancementSupport for the IMS repository (a single centralized store for resourcedefinitions in an IMSplex) enhanced to validate resource attributesbetween associated resources when a resource definition is addedto, updated in, or deleted from the IMSRSC Repository– Validates transaction, routing code, and program attributesAlso provided through the IMS 12 service process90Also provided through the IMS 12 service process– APAR PM32805 / PTF UX75915Benefits– Simplifies management of the DRD resources
    • IMS Version 13IMS 13 User Exit EnhancementsEnhanced user exit services extended to additional IMS controlregion user exitsUsers can now dynamically refresh more IMS user exit routines tobring in an updated version of the exit (or add/delete)– Significantly reduces downtime since IMS control region no longerrequires restart91Users can now display information about more user exits that aredefined in the USER_EXITS section of DFSDFxxx– Provides useful exit information to the userUsers can now code an exit to leverage IMS’s ability to call multipleroutines of the same type from a single point within the exit
    • IMS Version 13BSEX (DFSBSEX0, Build Security Environment Exit)NDMX (DFSNDMX0, Non-Discardable Message Exit)RASE (DFSRAS00, Resource Access Security Exit)OTMAYPRX (DFSYPRX0, OTMA Destination Resolution Exit)Enhanced User Exit Services Added to More ControlRegion Exit Types92OTMARTUX (DFSYRTUX, OTMA Resume TPIPE Security Exit)OTMAIOED (DFSYIOE0, OTMA Input/Output Edit Exit)LOGWRT (DFSFLGX0, Logger Exit)LOGEDIT (DFSFLGE0, Log Edit Exit)
    • IMS Version 13IMS Security EnhancementsAll IMS security settings can now be defined as IMS startupparameters– Updates to SECURITY macro in system definition (SYSGEN) no longerrequired due to its removal– Previously, certain settings could only be defined in SECURITY macro93Move security user exits out of the IMS nucleus into 31-bit storage– DFSCSGN0– DFSCTRN0– DFSCTSE0
    • IMS Version 13New IMS Startup Security ParametersRCLASS parameter added to DFSPBxxx PROCLIB member– RCLASS support in DFSDCxxx PROCLIB member will remain• DFSPBxxx RCLASS parameter value will override DFSDCxxx ifspecified in bothSECCNT parameter added to DFSDCxxx PROCLIB memberRetrofit SPE APARs/PTFs available for IMS startup securityparameter enhancement activation in IMS 11 and IMS 1294parameter enhancement activation in IMS 11 and IMS 12– PM48203/UK74050 (IMS 11)– PM48204/UK74051 (IMS 12)– If specifying RCLASS in DFSPBxxx/DFSDCxxx, can also have thefollowing APARs/PTFs applied to avoid an error message being issuedwhen it shouldn’t be• PM72199/UK82616 (IMS 11)• PM73558/UK82617 (IMS 12)
    • IMS Version 13/DIAGNOSE Command EnhancementsProcess for capturing diagnostic data used in troubleshooting IMSissues has been simplified– SYSOUT option now available for /DIAGNOSE SNAP output• Documentation can be gathered/stored in a readable format that is easy toretrieve and send to IBM support• Time-consuming SYSLOG searches and manual data formatting prior totransmission no longer required95transmission no longer required– /DIAGNOSE SNAP command extended to include more resources + morecoverage of existing resources• SHOW() support added for LTERM, NODE and USER• BLOCK – can now specify multiple single instance blocks and more blockscan be snapped• More blocks can be snapped for DB, LINE, LINK• MSNAME support added
    • IMS Version 13/DIAGNOSE Command EnhancementsBenefits– Cost effective, non-disruptive alternative to console dumps– /DIAGNOSE command is now more interactive• Can be used more as a tool for easing the real-time diagnosis process– Decreased time and effort required in capturing diagnostic information– Improved turn-around time in problem resolution96– Improved turn-around time in problem resolution
    • IMS Version 13IMS 13 Database and DBRC EnhancementsDatabase VersioningHALDB AlterDEDB AlterDBRC Enhancements97
    • IMS Version 13Database Versioning OverviewDatabase Versioning provides the ability to assign user-definedversion identifiers to different versions of a database structure– Enables structural changes to a database while providing multiple views ofthe physical IMS data to application programsApplications referencing a new physical database structure can bebrought online without affecting applications that use previousdatabase structures98database structures– Applications which do not require sensitivity to the new physical structure,do not need to be modified and can continue to access the databaseBenefit– Minimizes impact and reduces cost associated with making andcoordinating coding changes to affected application programs when aphysical database structure changes
    • IMS Version 13Database Versioning OverviewDatabase Versioning supports the following database types– DEDB– HDAM– HIDAM– PHDAM– PHIDAM99Can be used in conjunction with the database alter functions to keeptrack of different versions of the structure of a database– only supports the following database structure changes• For all supported database types– Increasing the length of a segment– Adding a new field to space at the end of a segment• For Full-Function and HALDB database types– Adding new field(s) that remap existing field(s) and space at the end of asegment
    • IMS Version 13Database Versioning must be enabled in DFSDFxxx DATABASEsectionVersioning is at the DBD level– Users define the version of a database definition on the DBD– Version numbers must be maintained in incremented valuesDatabase Versioning requires enablement of the IMS catalogDatabase Versioning Requirements100Database Versioning requires enablement of the IMS catalog– DBD definitions for versioned databases must be in the IMS catalogApplication programs can elect the desired database version– Specifying the version number on the PCB of the PSB– Specifying the version number on a DL/I INIT VERSION call
    • IMS Version 13DFSDFxxx PROCLIB: new DATABASE section keywords– Specify whether database versioning is enabled and default version• DBVERSION=• DBLEVEL=Database and Program Generation Statements– Specify the database version numberDatabase Versioning Implementation101– Specify the database version number• DBD: DBVER=• PCB: DBVER=– Override the default versioning specified in DFSDFxxx• PSBGEN: DBLEVEL=“INIT VERSION” DL/I Call– Overrides the version number that is specified on the PCB statement– Must be issued before issuing a DL/I DB call to the database
    • IMS Version 13HALDB Alter Overview …Structural changes can be made to HALDB databases while thedatabase remains online– Add a new field to space at the end of an existing segment– Increase the length of an existing segment– Define new fields that remap existing fields and space in an existingsegment102Benefit– Make structural changes to a database while maintaining databaseavailability
    • IMS Version 13HALDB Alter OverviewHALDB Alter is only supported for database types:– PHDAM– PHIDAMAfter changes are made to the DBD segment definition– Type-2 INITIATE OLREORG command is used to alter a database fromthe current structure to the new structure103the current structure to the new structure• Type-1 command /INITIATE OLREORG does not support altering aHALDB– Online Change commands are used to bring the changed ACBLIB DBDmember online– Application programs can start using the new database structure
    • IMS Version 13FIELD 1FIELD 2 SpaceFIELD 2 SpaceNewFIELD 3Add a new field to space at the end of a segmentExample 1FIELD 1104FIELD 1FIELD 3Example 2FIELD 1 FIELD 2FIELD 2 SpaceNewFIELD 3Space
    • IMS Version 13FIELD 1FIELD 2New SpaceFIELD 2Increase the length of an existing segmentExample 1FIELD 1105FIELD 1Example 2FIELD 1 FIELD 2FIELD 2New SpaceSpaceSpace
    • IMS Version 13HALDB Alter PrerequisitesSoftware requirements– CSL• SCI• OM– DBRC RECON MINVERS (‘13.1’)106
    • IMS Version 13DEDB AlterIMS 13 adds ability to dynamically change DEDB specifications– Users can dynamically change UOW, SIZE, ROOT, Randomizer while DEDB isonline– New DEDB Alter utility is used for DEDB changes– DRD is not required for DEDB Alter– Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executed107– Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executedBenefits– Improved management of DEDB definitions• Eliminate system down time for modifications to DEDB definitions• Improve data availability since changes are done while DEDB is online
    • IMS Version 13DEDB Alter UtilityThe new DEDB Alter utility is used to change the following itemswithout taking the area offline– The SIZE, UOW, or ROOT specifications of a DEDB area– The randomizer that is used for the DEDB areaRequirements108Requirements– A two-stage randomizer must be used, which enables areas to beprocessed individually.– DEDBs to be altered must be registered to DBRC– The MINVERS value in the RECON data set for all IMS subsystems thatshare the DEDB area must be at “13.1” or later– If SDEPS present, only the randomizer name can be changed
    • IMS Version 13DBRC EnhancementsCommand support for HALDB AlterCommand support for DEDB AlterMINVERS value of ’13.1’ must be set to use HALDB Alter, DEDB Alter,or synchronous program switch in a shared queues environmentSupported Migration and Coexistence– IMS 11 to IMS 13109– IMS 11 to IMS 13• Apply DBRC coexistence SPE APAR PM53134 to IMS 11– PTF UK80026• Allow IMS 11 to understand IMS 13 RECON records– IMS 12 to IMS 13• Apply DBRC coexistence SPE APAR PM53139 to IMS 12– PTF UK80027• Allow IMS 12 to understand IMS 13 RECON records
    • IMS Version 13IMS Connect EnhancementsXML Converter EnhancementsAuto-restart of the Language Environment (LE)Expanded Recorder Trace RecordsUse of RACF Event Notification Facility (ENF) Support forcached RACF UserIDs (UID)110Reporting of overall health to Workload Manager (WLM)
    • IMS Version 13XML Converter EnhancementsSupport for extending the current limit of 100 up to 2000 for themaximum number of XML converters• New IMS Connect configuration parameter MAXCVRTADAPTER(…, MAXCVRT= value)• IMS 12 (PM64487 / UK79728)Capability to view converters that are currently loaded– New Type-2 Command: QUERY IMSCON TYPE(CONVERTER)111– New Type-2 Command: QUERY IMSCON TYPE(CONVERTER)• Requests detailed information about XML converters in IMS ConnectBenefits– Enhances the flexibility of converter usage• Directly impacts IMS Soap Gateway environments
    • IMS Version 13Auto-restart of the Language Environment (LE)Automated mechanism to reinitialize the Language Environmentwhen an XML converter ABENDs– Without restarting IMS Connect– Converters will be reloaded as they are neededAutomatic refresh of the BPE User Exit for the XML Adapters(HWSXMLA0) after the ABEND limit ABLIM has been reached112(HWSXMLA0) after the ABEND limit ABLIM has been reachedBenefit– Improved efficiencies during error conditions• Eliminates IMS Connect restart and user interactions
    • IMS Version 13Expanded Recorder Trace RecordsThe IMS Connect Recorder trace records have been expanded to:– Capture entire messages sent and received using:• All TCP/IP communications– Including DRDA sockets and ISC TCP/IP• SCI (OM, ODBM, MSC, and ISC communications)• Requires a Trace Level HIGH and use of the external trace data set113• Requires a Trace Level HIGH and use of the external trace data setUPDATE TRACETABLE NAME(RCTR) OWNER(HWS) LEVEL(HIGH) EXTERNAL(YES | NO)Benefits– Improved diagnostics and problem determination
    • IMS Version 13RACF Event Notification Facility (ENF) SupportBackground– IMS Connect V12 provided the option to cache RACF UserIDs (UIDs) alongwith a command to refresh themIMS Connect V13: RACF ENF Support for Cached UserIDs (UID)– Automatically refreshes cached UIDs by listening to RACF events (ENFsignals) indicating that a change has been made to a UID114signals) indicating that a change has been made to a UID– NOTE: This function applies only when RACF UID caching has beenenabled in IMS ConnectBenefit– Allows IMS Connect to listen for certain RACF events indicating that achange has been made to a specific UserID• Avoids manual intervention
    • IMS Version 13Reporting of Overall Health to WLMWLM (Workload Manager) Health Report– New function to automatically report the overall health of IMS Connect• Allows Sysplex Distributor to use and take into account thisinformation for workload balancingBenefit– Allows WLM to know when resources are constrained or available115– Allows WLM to know when resources are constrained or available– Minimizes the possibility of Sysplex Distributor assigning work that IMSConnect is unable to handle
    • IMS Version 13IMS 13 Transaction Manager and ConnectivityEnhancementsCallout function enhancementsISC Over TCP/IPOTMA enhancements116
    • IMS Version 13Callout function enhancementsSynchronous program switchOTMA destination descriptors support asynchronous messages that aregoing to IBM WebSphere® MQ117
    • IMS Version 13BackgroundDL/I ICAL support from previous IMS releases– Provided synchronous callout capability to resources outside IMSz/OSIMSOTMATM/CTLWebSphereIMS TM resource adapterApplicationProgramMPP/JMP/IFP/BMP/JBP118IMS SOAP GATEWAYDatabaseDBServicesOTMATM/CTLServicesIMSConnectTCP/IPuser-written ClientProgramICALOTMADescriptorOTMADescriptor
    • IMS Version 13Synchronous Program SwitchNew capability that enhances the DL/I ICAL support– Allows an IMS application program to synchronously call and wait for a replyfrom another IMS application program• Within the calling program’s UOWIMS dependentWebSphere119DatabaseIMS DBservicesIMS dependentregionIMS TMservicesMPP, JMPIFP, MD BMPOTMAApplicationProgramICALIMS SOAP GATEWAYIMSConnectTCP/IPuser-written ClientWebSphereIMS TM resource adapter
    • IMS Version 13Synchronous Program Switch...Highlights– An enhancement to the DL/I ICAL to invoke another IMS application• In the same IMS• In a different IMS– In a Shared Queues back-end– Across an MSC linkMPP1MPP4MPP3ICALICALICALIMS1MPP2IMS XIMS2MSCSharedMsg Queues120– Across an MSC link– And synchronously receive the response back during the same UOW– IMS internally schedules the transaction initiated by the ICAL call as an OTMAtransaction• Uses a new type of OTMA destination descriptor (TYPE=IMSTRAN) whichhas been introduced specifically for synchronous program switch support– And the target transaction can be• An IFP, MPP, MD BMP, or JMP in IMS TM or TM/DB environmentsMPP4
    • IMS Version 13Synchronous Program Switch...Usage examples– Applications can issue multiple ICALs to different destination TYPEs• Synchronous callout• Synchronous program switchTRANAIMS CTL RegionIMSWebSphereIMS TMRAOTMA1 GU, IOPCB121ICAL DEST1ICAL TRANBIMSConnectIMS SOAPGatewayTCP/IPRYO pgmMSG-QDestinationDescriptorTYPE(IMSCON)TRANBGU IOPCBISRT IOPCBDestinationDescriptorTYPE(IMSTRAN)1234567GU, IOPCB
    • IMS Version 13Synchronous Program Switch...Considerations– To use synchronous program switch in a shared queues environment, allof the participating IMS systems must be Version 13 or later and have aMINVERS value of 13.1– New design implications• Timeout values• Transaction Expiration122• Transaction Expiration• Late Responses• LTERM Override• ALTPCB destinations• Multiple ICALs• Recursive requests• Holding database locks across an ICAL request– Increased importance for performance tooling
    • IMS Version 13ISC Over TCP/IPISC Over TCP/IP value proposition– New option that supports TCP/IP network connectivity for IntersystemCommunication (ISC) connections• IMS – CICSProvides a strategic protocol alternative to SNA/VTAM• Allows an all inclusive TCP/IP solution for networks123• Allows an all inclusive TCP/IP solution for networks
    • IMS Version 13ISC Over TCP/IPHighlights– Supports both static and dynamic terminals• Static terminal definitions– SYSGEN stage 1 TYPE, TERMINAL, SUBPOOL macros– DFSDCxxx PROCLIB member• Dynamic terminal specification124• Dynamic terminal specification– Logon descriptors in the DFSDSCMx or DFSDSCTy PROCLIB member– Leverages IMS Connect• Enhancements to the HWSCFGxx configuration member– No IMS Connect user message exit changes– Uses CSL to communicate between IMS and IMS Connect• Requires Structured Call Interface (SCI) and Operation Manager (OM)– Requires CICS Transaction Server for z/OS 5.1
    • IMS Version 13OTMA Enhancements …OTMA destination descriptor enhancements– TYPE={MQSERIES}• Provides asynchronous callout and messaging support (ISRT ALTPCB)– EXIT={YES | NO}• Specifies whether or not the OTMA exits are to be calledCorresponding enhancement to IMS Type-2 OTMADESC commands125Corresponding enhancement to IMS Type-2 OTMADESC commands– [CREATE | UPDATE | DELETE |QUERY] OTMADESC• Recovered across warm and emergency restartsBenefits– Simplifies asynchronous messaging to WMQ– Removes the need to code the OTMA exits, DFSYPRX0 and DFSYDRU0– Provides dynamic change capability with the Type-2 commands
    • IMS Version 13IMS 13 HighlightsSystem– IMS CONNECT enhancements• XML Converter Enhancements• Expanded Recorder TraceRecords• Reporting of overall health toWorkload Manager (WLM)Database and DBRC– HALDB Alter– DEDB Alter– Database Versioning– DBRC support for HALDB Alter andDEDB AlterTM and Connectivity126Workload Manager (WLM)– Concurrent application threads– Reduced Total Cost of Ownership(TCO)– Elimination of SECURITY Macro– User Exit enhancements– JDR support for ESAF– DIAG command enhancementsTM and Connectivity– Synchronous program switch– ISC TCP/IP Links– OTMA destination descriptorenhancementsIMS 13 Web PageIBM IM InfoCenter126