®     Victoria IMS Users GroupIMS 12 System Enhancements and MigrationDiane GoffIMS Advanced Technical Skillsdgoff@us.ibm....
Victoria IMS Users GroupSystem Enhancements … Dynamic resource definition (DRD) enhancements zAAP/zIIP times in accounting...
Victoria IMS Users GroupSystem Enhancements Command enhancements System usability enhancements – IMS 11 SPE User Exit Enha...
Victoria IMS Users GroupDynamic Resource Definition (DRD) Enhancements New UPDATE option for IMPORT command – Previously, ...
Victoria IMS Users GroupzAAP/zIIP Times in Accounting Log Records zAAP/zIIP time field is added to the x’07’, x’0A07’ and ...
Victoria IMS Users GroupzIIP support for some CQS processing Request response processing for authorized CQS clients is eli...
Victoria IMS Users GroupMember Online Change NAMEONLY Option OPTION(NAMEONLY) added for member online change INIT OLC TYPE...
Victoria IMS Users GroupExtended Address Volume (EAV) for Non-VSAM Data Sets IMS 12 adds EAV support for some non-VSAM sys...
Victoria IMS Users Group          Logging Enhancements                                 9
Victoria IMS Users GroupLogging Enhancements Extended Format Support for OLDS and SLDS – Optional – Allows OLDS and SLDS t...
Victoria IMS Users GroupStriping of OLDS and SLDS Use of extended format data sets allows striping – Striping allows multi...
Victoria IMS Users GroupOLDS Buffers Specifications OLDS buffers above 2-gigabyte boundary – Specified with BUFSTOR=64 on ...
Victoria IMS Users GroupMigration to Buffers above the 2G Bar All OLDS must be extended format for the buffers to be above...
Victoria IMS Users GroupMigration to Striping and Buffers in 64-bit Storage   First possible set of migration steps to imp...
Victoria IMS Users GroupMigration to Striping and Buffers in 64-bit Storage  Another set of possible migration steps to im...
Victoria IMS Users GroupWADS Management The concept of WADS track groups is not used by IMS 12 – WADS should be sized to p...
Victoria IMS Users GroupLogging Enhancements Summary Benefits – OLDS buffers in 64-bit virtual storage – Simplified defini...
Victoria IMS Users GroupSystem Pools in 64-bit Real Storage The following pools are moved to 64-bit real storage    • Thes...
Victoria IMS Users GroupSysplex Serial Program Management (SSPM) Disabling Optional capability to disable Sysplex Serial P...
Victoria IMS Users GroupLog Archiving for Non-Recoverable Databases                 SPEs: IMS 10 PM18093; IMS 11 PM19363; ...
Victoria IMS Users GroupLog Archiving for Non-Recoverable Databases Problem addressed by this enhancement – Online backout...
Victoria IMS Users GroupCommand Enhancements Enhancements to existing commands and new commands – CQS trace command enhanc...
Victoria IMS Users GroupCommand Enhancements Enhancements are focused on type-2 commands for the Operations Manager (OM) e...
Victoria IMS Users GroupSystem Usability Enhancements IMS 11 SPE User Exit Enhancements – Enables support for multiple ins...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements                            IMS 11 APAR PM04456 /                ...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS Initialization/Termination Exit – Available to all IMS regio...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS CQS Event Exit – Available to IMS regions: TM/DB and DCCTL –...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS CQS Structure Event Exit – Available to IMS regions: TM/DB a...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Partner Product Exit – DFSPPUE0 – Support added for the new user...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Restart Exit – Support added for the new user exit services   • ...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements QUERY USEREXIT Command – Type-2 command to display information a...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Miscellaneous Information – Sample exit code provided in IMS.SDF...
Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Benefits – Three new IMS User exit types   •   INITTERM - IMS In...
Victoria IMS Users GroupRAS Enhancements IMS 12 CQS Traceability – Creates two new BPE trace tables to track CQS structure...
Victoria IMS Users GroupRAS Enhancements IMS 11 SPE BPE Trace Selective Initialization – Creates a new BPE trace table fea...
Victoria IMS Users GroupRAS Enhancements /DIAGNOSE Command SNAP Function Enhancements – Added six new resource types to th...
Victoria IMS Users GroupIMS 12 CQS Traceability Background – IMS Shared Queues environments can produce a high volume of  ...
Victoria IMS Users GroupIMS 12 CQS Traceability New CQS Trace Tables – BPE based tracing – Track CQS structure events base...
Victoria IMS Users GroupIMS 11 SPE BPE Trace Selective Initialization  Background  – IMS Connect Recorder Trace facility d...
Victoria IMS Users GroupIMS 11 SPE BPE Trace Selective Initialization                          IMS 11 APAR PK98125        ...
Victoria IMS Users GroupIMS Dump Formatter Enhancements Dump Formatter Support for IMS Repository – Support added to IMS D...
Victoria IMS Users GroupReduce IMS Module Aliases in RESLIB Reduced module aliases in RESLIB, where possible For remaining...
Victoria IMS Users GroupEOM / EOT Tracing Facility Enhancement Created a step trace function in the End-of-Task (EOT) proc...
Victoria IMS Users GroupNew /DIAGNOSE Command SET AOSLOG Function Support for the APPC / OTMA Synchronous Shared Queues en...
Victoria IMS Users GroupNew /DIAGNOSE Command SNAP Functions Six new SNAP resource types  Resource Type             SNAP C...
Victoria IMS Users GroupRAS Enhancements Benefits – Diagnose problems interactively – Non-disruptive alternatives to produ...
Victoria IMS Users GroupMIPS reduction enhancements CICS threadsafe support CICS and ODBA users have new DFSRAS00 exit cap...
Victoria IMS Users GroupIMS Repository Overview of the IMS Repository Function IMS Repository Function Components – Reposi...
Victoria IMS Users GroupIMS Repository Function Overview A ‘repository’ is a generalized data storage facility that can be...
Victoria IMS Users GroupIMS Repository Function Usage The various components of the IMS repository function provide a cent...
Victoria IMS Users GroupIMS 12 support for the DRD function DRD users in IMS 10 and IMS 11 moving to IMS 12 – Can use exis...
Victoria IMS Users GroupIMS Repository Function components A Repository Server (RS) – A new BPE-based address space manage...
Victoria IMS Users GroupIMS Repository Function Benefits Consolidation of resource definitions in a single place, the repo...
Victoria IMS Users GroupIMS Repository Function components … A Repository Server (RS) – A new BPE-based address space   • ...
Victoria IMS Users GroupIMS Repository Function components … A Repository Server (RS) – Uses VSAM KSDS data sets to store ...
Victoria IMS Users GroupIMS Repository Function components Repository data sets – Multiple sets of VSAM KSDS data sets – E...
Victoria IMS Users GroupIMS Repository Function components … Catalog repository (RS catalog data sets) – Required per repo...
Victoria IMS Users GroupIMS Repository Function components … IMS repositories – IMSRSC repository   • Contains the stored ...
Victoria IMS Users GroupIMS Repository Function components … IMS repositories – IMSRSC repository   • Composed of up to th...
Victoria IMS Users GroupIMS Repository Function components A Common Service Layer (CSL) IMSplex configuration consisting o...
Victoria IMS Users GroupIMS Repository Function components Batch utilities – Batch ADMIN utility (FRPBATCH)   • Commands f...
Victoria IMS Users GroupIMS Repository Function Configuration                                                             ...
Victoria IMS Users GroupSummary of System Enhancements … Dynamic resource definition (DRD) enhancements zAAP/zIIP times in...
Victoria IMS Users GroupSummary of System Enhancements Command enhancements System usability enhancements – IMS 11 SPE Use...
Victoria IMS Users GroupInstallation and Migration  Packaging, Prerequisites and Coexistence  IMS Publications Changes  IM...
Victoria IMS Users GroupIMS 12 Packaging  IMS 12 product number: 5635-A03     FMID            Feature Description     HMK1...
Victoria IMS Users GroupIMS 12 Hardware Prerequisites IMS 12 requires the following hardware: – A 64-bit IBM zSeries® proc...
Victoria IMS Users GroupIMS 12 Software Prerequisites Minimum software level prerequisites – z/OS V1R11 (5694-A01) – DFSMS...
Victoria IMS Users GroupIMS Enterprise Suite for z/OS, V2.1 (5655-T62)  Available October 28, 2011  The SOAP Gateway, Conn...
Victoria IMS Users GroupAdditional IMS 12 Prerequisites  See the IMS 12 Release Planning (GC19-3019-01) for additional  re...
Victoria IMS Users GroupPrerequisite Maintenance Fixes for Migration Download enhanced holddata – Run SMPE: REPORT MISSING...
Victoria IMS Users GroupSupport Status of IMS Versions      IMS Version 9      – End of service was November 7, 2010      ...
Victoria IMS Users GroupWithdrawn Support IMS 11 is the last release to support the SMU-to-RACF utilities – IMS 9 was the ...
Victoria IMS Users GroupWithdrawn Support IMS 11 is the last release to support the Knowledge Based Log Analysis (KBLA) fa...
Victoria IMS Users GroupIMS 12 Supported Connections DB2 connections are supported with – DB2 for z/OS 10, 9 and 8 DBCTL c...
Victoria IMS Users GroupIMS 12 Supported Connections ISC is supported with – IMS 12, IMS 11, and IMS 10 – CICS Transaction...
Victoria IMS Users GroupSupported Migrations and Coexistence - DBRC IMS 11 to IMS 12 – Upgrade RECONs from IMS 11 to IMS 1...
Victoria IMS Users GroupIRLM 2.3 IRLM 2.3 and IRLM 2.2 are both shipped with IMS 12 IRLM 2.3 and IRLM 2.2 may be used with...
Victoria IMS Users GroupDBCTL, ODBA and ODBM Migration The DRA interface modules must be at the same version as IMS – Copy...
Victoria IMS Users GroupMigration with DRD IMS 12 system may be cold started with RDDS from IMS 11 or IMS 10 – IMSID must ...
Victoria IMS Users GroupCSL Coexistence IMS 12, IMS 11 and IMS 10 – CSL address spaces and IMS may be at mixed levels   • ...
Victoria IMS Users GroupCoexistence Maintenance See Chapter 4 of IMS 12 Release Planning (GC19-3019-01) for coexistence ma...
Victoria IMS Users GroupCoexistence - IMS Utilities  Batch Backout, Log Archive, and Log Recovery  – Use the utility from ...
Victoria IMS Users GroupRemote Site Recovery (RSR) Migration/Coexistence IMS 12 RSR tracking system can process logs creat...
Victoria IMS Users GroupLog Records Change in log suffix – Timestamp in log record suffix is no longer necessarily unique ...
Victoria IMS Users GroupIMS Publications IMS publications structure and titles remain the same as in IMS 11 – PDF master i...
Victoria IMS Users GroupIMS Library  The Information Center contains information on IMS 12  http://publib.boulder.ibm.com/...
Victoria IMS Users GroupIMS 12 Redbook Announcement                                  Just released!                       ...
Victoria IMS Users GroupIMS Tools Migration/Coexistence Some products may require updates  – Contact your vendors for info...
Victoria IMS Users Group IBM IMS Tools - Highlights     New IMS Tools Solution Packs      – In general, IBM will support t...
Victoria IMS Users GroupIVP Enhancements Repository usage for DRD is added to IVP – IVP provides sample JCL to create repo...
Victoria IMS Users GroupSyntax Checker Enhancements Syntax Checker supports PROCLIB members for IMS 12, IMS 11 and IMS 10 ...
Victoria IMS Users GroupInstallation and Migration Tasks   Migration Tasks   – Review the IMS 12 Release Planning publicat...
Victoria IMS Users GroupInstallation and Migration Tasks  Migration Tasks (continued)  – Evaluate and update IMS exit rout...
Victoria IMS Users GroupInstallation and Migration Tasks  Migration Tasks (continued)  – Install the Type 2 and Type 4 SVC...
Victoria IMS Users GroupInstallation and Migration Summary Packaging, Prerequisites and Coexistence IMS Publications Chang...
Upcoming SlideShare
Loading in...5
×

IMS 12 System Enhancements and Migration Considerations - IMS UG April 2012 Victoria

1,126

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
1,126
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS 12 System Enhancements and Migration Considerations - IMS UG April 2012 Victoria

  1. 1. ® Victoria IMS Users GroupIMS 12 System Enhancements and MigrationDiane GoffIMS Advanced Technical Skillsdgoff@us.ibm.com © 2012 IBM Corporation
  2. 2. Victoria IMS Users GroupSystem Enhancements … Dynamic resource definition (DRD) enhancements zAAP/zIIP times in accounting log records zIIP support for some CQS processing Member online change NAMEONLY option EAV support for non-VSAM data sets IMS logging enhancements – Extended-format data set support for OLDS/SLDS – IMS log buffers in 64-bit virtual storage – Simplified WADS management System pools in 64-bit real storage Sysplex Serial Program Management (SSPM) Disabling SPE for log archiving of non-recoverable databases 2
  3. 3. Victoria IMS Users GroupSystem Enhancements Command enhancements System usability enhancements – IMS 11 SPE User Exit Enhancements RAS enhancements – CQS traceability enhancements – IMS Dump Formatter enhancements – Reduce IMS Module Aliases in RESLIB – End-Of-Memory / End-Of-Task (EOT) Tracing Facility – IMS 11 SPE BPE Trace Selective Initialization – /DIAGNOSE SNAP command enhancements MIPS reduction enhancements 3
  4. 4. Victoria IMS Users GroupDynamic Resource Definition (DRD) Enhancements New UPDATE option for IMPORT command – Previously, IMPORT could only be used for adding runtime resource definitions/descriptors that did not exist in the target IMS system – New IMPORT .. OPTION(UPDATE) allows existing runtime resource definitions/descriptors in the the target IMS to be changed • Command fails if changed definition is in use DRD usage of the IMS repository function – Previously, stored resource definitions/descriptors were kept in resource definition data sets (RDDSs) – New IMS repository function provides an additional method for storing stored resource definitions/descriptors – IMS repository will be described in a later topic Benefits – Improved manageability for DRD 4
  5. 5. Victoria IMS Users GroupzAAP/zIIP Times in Accounting Log Records zAAP/zIIP time field is added to the x’07’, x’0A07’ and x’56FA’ log records – X’07’ program termination – X’0A07’ CPIC program termination – X’56FA’ optional transaction level statistics record CPU time field is changed to include only the standard CP (central processor) time, not zAAP/zIIP time – Sum of CP and zAAP/zIIP times is the total CPU time Benefits – Users can distinguish between CP and zAAP/zIIP times • Could be used for accounting or charge out purposes • Significant for software licensing • Most significant for JMP and JBP regions 5
  6. 6. Victoria IMS Users GroupzIIP support for some CQS processing Request response processing for authorized CQS clients is eligible to run on a zIIP Examples – When the IMS control region is running with IMS Shared Message Queues or Shared IMS Fast Path Message Queues enabled – When the IMS Resource Manager address space is using a resource structure 6
  7. 7. Victoria IMS Users GroupMember Online Change NAMEONLY Option OPTION(NAMEONLY) added for member online change INIT OLC TYPE(ACBMBR) PHASE(PREPARE) NAME(name1,name2,…) OPTION(NAMEONLY) – Command processes only the named member(s) of the staging ACBLIB • Without this option, the command processes related members which have been changed – For example, DBDs in intent list of PSB – OPTION(NAMEONLY) may be used for: • New DBDs – These DBDs cannot reference existing DBDs which have been modified • New or changed PSBs which do not reference changed DBDs in their intent lists Benefit – Performance enhancement • This option provides a performance benefit when there are many members in the staging and active ACB libraries. 7
  8. 8. Victoria IMS Users GroupExtended Address Volume (EAV) for Non-VSAM Data Sets IMS 12 adds EAV support for some non-VSAM system data sets – IMS OSAM database data sets – Restart Data Set (RDS) – Message Queue data sets (queue blocks, long message and short message) – Logs (OLDS, SLDS and WADS) – IMS SPOOL data sets (UNITYPE=DISK and UNITYPE=SPOOL) – BPE External Trace Data Sets z/OS 1.12 is required for these data sets EATTR=OPT must be specified on allocation JCL Large sequential data set support added for IMS SPOOL data sets – UNITYPE=SPOOL or UNITYPE=DISK on LINEGRP macro Benefits – Support 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 8
  9. 9. Victoria IMS Users Group Logging Enhancements 9
  10. 10. Victoria IMS Users GroupLogging Enhancements Extended Format Support for OLDS and SLDS – Optional – Allows OLDS and SLDS to be striped • Increased logging speed Log buffers moved above the 2-gigabyte boundary (“bar”) in virtual – Optional – Frees substantial amount of ECSA Simplified WADS management – Improved WADS performance 10
  11. 11. Victoria IMS Users GroupStriping of OLDS and SLDS Use of extended format data sets allows striping – Striping allows multiple concurrent I/Os for sequential processing • Data set is spread across multiple volumes • Increased logging rates IMS 12 allows OLDS and SLDS to be defined as extended format data sets • Extended format is specified with data set type of ‘EXT’ – JCL allocation requires DATACLAS and STORCLAS parameters on DD statement • Striping is invoked for extended format data sets when the storage class has Sustained Data Rate (SDR) value of 5 or higher 11
  12. 12. Victoria IMS Users GroupOLDS Buffers Specifications OLDS buffers above 2-gigabyte boundary – Specified with BUFSTOR=64 on OLDSDEF statement in DFSVSMxx • Puts buffers in 64-bit virtual storage – Requires that block size is 4K multiple • OLDS must be extended format • Frees substantial amount of ECSA OLDS block size – Optionally specified with BLKSZ parameter on OLDSDEF statement in DFSVSMxx member • Previously, it was set only from the data set characteristics – BLKSZ= is recommended If BLKSZ and BUFSTOR=64 are both specified – IMS will round up number of buffers (BUFNO=) to a megabyte boundary • 64-bit storage is acquired in megabyte increments • Maximizes number of buffers in acquired storage 12
  13. 13. Victoria IMS Users GroupMigration to Buffers above the 2G Bar All OLDS must be extended format for the buffers to be above the 2G bar If Logger Exit (DFSFLGX0) or RSR Log Filter Exit (DFSFTFX0) is used – Ensure they are capable of handling buffers above 2G • The IMS supplied DFSFTFX0 exit is capable BUFSTOR=64 must be specified on the OLDSDEF statement OLDS block size is multiple of 4K IMS must be restarted – Restart may be cold or warm 13
  14. 14. Victoria IMS Users GroupMigration to Striping and Buffers in 64-bit Storage First possible set of migration steps to implement striping with OLDS and buffers in 64-bit storage 1. Define new OLDS data sets with extended formatting • Use data class in which data set type is ‘EXT’ • Use storage class with SDR >= 5MB/second • Define MDA members for dynamic allocation 2. Start new OLDS data sets with /START OLDS commands • Striping will be used for these data sets • A mixture of extended format, basic format and large format OLDS is OK when buffers are below the 2G bar 3. Stop old OLDS data sets with /STOP OLDS commands 4. Specify BUFSTOR=64 on OLDSDEF statement • Also specify BLKSZ= on OLDSDEF statement 5. Terminate and restart IMS to get buffers above the bar 14
  15. 15. Victoria IMS Users GroupMigration to Striping and Buffers in 64-bit Storage Another set of possible migration steps to implement striping with OLDS and buffers in 64-bit storage 1. Terminate IMS 2. Rename the OLDS data sets 3. Define new OLDS data sets using the old data set names • Use data class in which data set type is ‘EXT’ • Use storage class with SDR >= 5MB/second 4. Copy the old OLDS data sets to the new OLDS data sets 5. Specify BUFSTOR=64 and BLKSZ= on OLDSDEF statement 6. Restart IMS • Striping will be used on all OLDS • Buffers will be above the bar 15
  16. 16. Victoria IMS Users GroupWADS Management The concept of WADS track groups is not used by IMS 12 – WADS should be sized to provide enough space for any OLDS buffers not yet written at any time plus one track – WADS use 4K block size – WADS writes are changed from previous IMS versions • WADS writes are sequential • WADS written in wrap-around fashion Performance – WADS sequential writes generally improve usage of cache in storage systems – WADS should be kept in cache in storage subsystem 16
  17. 17. Victoria IMS Users GroupLogging Enhancements Summary Benefits – OLDS buffers in 64-bit virtual storage – Simplified definition of OLDS block size – Increased maximum logging rate – ECSA constraint relief 17
  18. 18. Victoria IMS Users GroupSystem Pools in 64-bit Real Storage The following pools are moved to 64-bit real storage • These pools remain in 31-bit virtual storage – DBWP – Database work pool – DLDP – DMB pool – DLMP – CSA PSB pool – DPSB – DLI PSB pool – PSBW – PSB work pool Benefits – Reduction in 31-bit fixed real frames for fixed pools – Some users will now be able to fix these pools • Previously, they were constrained by 31-bit real storage 18
  19. 19. Victoria IMS Users GroupSysplex Serial Program Management (SSPM) Disabling Optional capability to disable Sysplex Serial Program Management – Before IMS 12 • Serial programs (SCHDTYPE=SERIAL on APPLCTN macro or DEFINE PGM command) enforce serialization of PSB scheduling when: – RM is used – RM structure is defined • Serialization is enforced across the shared queues group – Does not apply to CICS or ODBA application schedules – IMS 12 adds option not to enforce serialization • Option is specified with control statement – GBL_SERIAL_PGM=N | Y • Specified in DFSDFxxx member COMMON_SERIVCE_LAYER section or • DFSCGxxx member – GBL_SERIAL_PGM=N turns off serialization across the shared queues group 19
  20. 20. Victoria IMS Users GroupLog Archiving for Non-Recoverable Databases SPEs: IMS 10 PM18093; IMS 11 PM19363; IMS 12 PM54945 Archive (DFSUARC0) is enhanced to write “undo” records for non- recoverable full function databases – Previously, “undo” records were not archived – New control statement option not to archive “undo” records • Required to write these records as was done previously Non-recoverable database logging: – “After image” log records are not written for non-recoverable databases – “Undo” log records are written to OLDS for non-recoverable full function databases • This allows uncommitted updates to be backed out – “Undo” log records are not archived from OLDS before this enhancement • They are archived with this enhancement unless overridden by control statement 20
  21. 21. Victoria IMS Users GroupLog Archiving for Non-Recoverable Databases Problem addressed by this enhancement – Online backout using archived log stops when it encounters a “missing” log record • Backout is incomplete, other database updates may not be backed out and will be stopped – Batch backout using archived log does not backout updates to non- recoverable database but sets no flags in DBRC to prevent its use Control statement not to archive non-recoverable database log records – Option applies to specified databases SLDS CMPRSNR((dbd1,ddn1)(dbd2,ddn2),...|ALL) Benefit – Eliminates potential database integrity and operational problems 21
  22. 22. Victoria IMS Users GroupCommand 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 enhancements – HALDB command enhancements – IMS Connect command enhancements – MSC command enhancements – IMS repository function command enhancements – OTMA command enhancements 22
  23. 23. Victoria IMS Users GroupCommand Enhancements Enhancements are focused on type-2 commands for the Operations Manager (OM) environment Benefits – Support of new IMS 12 functions – Improved manageability 23
  24. 24. Victoria IMS Users GroupSystem Usability Enhancements IMS 11 SPE User Exit Enhancements – Enables support for multiple instances of a user exit type – Provides support for 3 new exits – Implements the QUERY USEREXIT command – Included in IMS V12 24
  25. 25. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS 11 APAR PM04456 / PTF UK67199 Ability to run multiple instances of a supported user exit type • No longer need user or vendor written code to manage multiple exits Three new IMS user exit types • IMS Initialization/Termination - INITTERM • IMS CQS Event - ICQSEVNT • IMS CQS Structure Event - ICQSSTEV Existing User Exits eligible to use new exit services • Product Partner Exit DFSPPUE0 - PPUE • Restart Exit DFSRSTX0 (available in IMS 10) – RESTART Implements the QUERY USEREXIT command 25
  26. 26. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS Initialization/Termination Exit – Available to all IMS regions: TM/DB, DBCTL, DCCTL, and FDBR – Exit called during … • Early IMS initialization • Normal and abnormal IMS termination – Exit routine(s) must be defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member • EXITDEF=(TYPE=INITTERM,EXITS=(exitnames)) • Exit routines called in the order listed • No default exit name – Exit load module must be included in an authorized library in the JOBLIB, STEPLIB, or LINKLIST concatenation – This exit is eligible to use IMS Callable Services 26
  27. 27. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS CQS Event Exit – Available to IMS regions: TM/DB and DCCTL – Exit called when IMS receives notification of a CQS event – Exit routine(s) must be defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member • EXITDEF=(TYPE=ICQSEVNT,EXITS=(exitnames)) • Exit routines called in the order listed • No default exit name – Exit load module must be included in an authorized library in the JOBLIB, STEPLIB, or LINKLIST concatenation – This exit is eligible to use IMS Callable Services 27
  28. 28. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements IMS CQS Structure Event Exit – Available to IMS regions: TM/DB and DCCTL – Exit called when IMS receives notification of a CQS structure event – Exit routine(s) must be defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member • EXITDEF=(TYPE=ICQSSTEV,EXITS=(exitnames)) • Exit routines called in the order listed • No default exit name – Exit load module must be included in an authorized library in the JOBLIB, STEPLIB, or LINKLIST concatenation – This exit is eligible to use IMS Callable Services 28
  29. 29. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Partner Product Exit – DFSPPUE0 – Support added for the new user exit services • Capability to define multiple user exit routines called at the PPUE exit point • Capability to use QUERY USEREXIT for PPUE – Available to IMS regions: TM/DB, DBCTL and DCCTL – Exit routine(s) must be defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member • EXITDEF=(TYPE=PPUE,EXITS=(exitnames)) • Exit routines called in the order listed • No default exit name – Exit can be named DFSPPUE0 and must be linked into a library in the STEPLIB concatenation – Can continue using old user exit services for PPUE 29
  30. 30. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Restart Exit – Support added for the new user exit services • Capability to define multiple user exit routines called at RESTART exit point • Capability to use QUERY USEREXIT for RESTART – Available to IMS regions: TM/DB, DBCTL, and DCCTL – Exit routine(s) must be defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member • EXITDEF=(TYPE=RESTART,EXITS=(exitnames)) • Exit routines called in the order listed • No default exit name – Exit load module must be included in an authorized library in the JOBLIB, STEPLIB, or LINKLIST concatenation – Can continue using old user exit services for RESTART 30
  31. 31. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements QUERY USEREXIT Command – Type-2 command to display information about user exits defined in the EXITDEF parameter in the USER_EXITS section of the DFSDFxxx member – Command is not available for user exits not defined in EXITDEF parameter – Default command routing to all IMSs in the IMSplex – Sample information returned for requested user exit type: Module Name(s) Entry Point Address Module Size Number of Calls (since initialization) Total Elapsed Time Spent in Exit Routine (since initialization) IMS member name that created the output for the exit – Security authorization • Resource name is IMS.plxname.QRY.USEREXIT • Consider setting similar to other OM QUERY commands 31
  32. 32. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Miscellaneous Information – Sample exit code provided in IMS.SDFSSMPL Exit Type Sample Code INITTERM DFSITMX0 ICQSEVNT DFSCQEX0 ICQSSTEV DFSCSEX0 PPUE DFSPPEX0 RESTART DFSRSTX0 – New x’4517’ log record • Log record created at checkpoint • Mapped by DSECT DFSL4517 • Contains relevant user exit data – Further information at Technote: https://www.ibm.com/support/docview.wss?uid=swg27021341 32
  33. 33. Victoria IMS Users GroupIMS 11 SPE User Exit Enhancements Benefits – Three new IMS User exit types • INITTERM - IMS Initialization/Termination • ICQSEVNT - CQS Event • ICQSSTEV - CQS Structure Event – Ability to execute multiple exit routines for supported IMS User exit types • INITTERM • ICQSEVNT • ICQSSTEV • PPUE • RESTART – New QUERY USEREXIT command 33
  34. 34. Victoria IMS Users GroupRAS Enhancements IMS 12 CQS Traceability – Creates two new BPE trace tables to track CQS structure events IMS Dump Formatter Enhancements – Support for the Repository Server and the Repository Client address spaces – Support for the OTMA C/I Reduce IMS Module Aliases in RESLIB – Begins a process to reduce IMS load module aliases End-Of-Memory / End-Of-Task (EOT) Tracing Facility – Created a step trace function in the End-of-Task (EOT) process 34
  35. 35. Victoria IMS Users GroupRAS Enhancements IMS 11 SPE BPE Trace Selective Initialization – Creates a new BPE trace table feature that allows a trace table to be defined to require explicit commands • IMS Connect Recorder Trace, RCTR, trace table definition has been updated to enable the new explicit commands feature New /DIAGNOSE Command SET AOSLOG Function – Enable and disable log record capture of events related to APPC and OTMA synchronous transactions in a shared-queues environment 35
  36. 36. Victoria IMS Users GroupRAS Enhancements /DIAGNOSE Command SNAP Function Enhancements – Added six new resource types to the SNAP function – Provided DISPLAY option to route output back to issuing LTERM – Provided LIMIT option to restrict number of lines of output going to LTERM – Provided SHOW parameter to control type and amount of output produced 36
  37. 37. Victoria IMS Users GroupIMS 12 CQS Traceability Background – IMS Shared Queues environments can produce a high volume of trace data • Can quickly fill in-core trace table • Table wrap around technique can cause the loss of important trace data – Need to preserve trace entries for structure events • Lack of trace data can slow down the diagnostic process Solution – Create two new BPE trace tables to track CQS structure events Benefits – Preserve more trace entries for CQS structure events – Improve the time to diagnose CQS problems 37
  38. 38. Victoria IMS Users GroupIMS 12 CQS Traceability New CQS Trace Tables – BPE based tracing – Track CQS structure events based on structure event characteristics • Structure Event trace table (SEVT) tracks structure events • Structure Overflow trace table (OFLW) tracks overflow events – The existing CQS structure trace table (STR) will track client request activity only • No longer tracks structure events 38
  39. 39. Victoria IMS Users GroupIMS 11 SPE BPE Trace Selective Initialization Background – IMS Connect Recorder Trace facility delivered in IMS V11 uses a BPE trace table – Inadvertent activation of BPE tracing is possible • If BPE trace initialization encounters a generic type (*) on the TRCLEV statement in the HWS BPE configuration member: TRCLEV=(*,HIGH,HWS) • Performance problems could result from running Recorder Trace inadvertently – Different than activating the original IMS Connect Recorder Trace • Explicit IMS Connect “OPEN” command 39
  40. 40. Victoria IMS Users GroupIMS 11 SPE BPE Trace Selective Initialization IMS 11 APAR PK98125 / PTF UK53814 Creates a new BPE trace selective initialization feature that allows a trace table to be defined as requiring explicit command activation • IMS Connect Recorder Trace, RCTR, trace table definition updated to enable the new explicit commands feature • No inadvertent starting of IMS Connect Recorder Trace • Configure the RCTR trace table differently: TRCLEV=(RCTR,MEDIUM,HWS) vs. TRCLEV=(*,HIGH,HWS) Adds explicit command logic to BPE trace table update command • Trace table types requiring explicit commands are processed only when the NAME parameter explicitly specifies the trace table name UPDATE TRACETABLE NAME(RCTR) OWNER(HWS) LEVEL(MEDIUM) UPDATE TRACETABLE NAME(RCTR) OWNER(HWS) EXTERNAL(NO) Benefits – No inadvertent activation of BPE supported IMS Connect Recorder Trace 40
  41. 41. Victoria IMS Users GroupIMS Dump Formatter Enhancements Dump Formatter Support for IMS Repository – Support added to IMS Dump Formatter for the Repository Server address space • Via the Other IMS Components (6) section of the Dump Formatter – Support added to IMS Dump Formatter for the Repository Client address space • Via the Other IMS-Related Products (7) section of the Dump Formatter OTMA C/I Serviceability Enhancements – Currently has no dump formatting or tracing capabilities – Enhances the IMS Dump Formatter by adding support for OTMA C/I • Via the Other IMS Components (6) section of the Dump Formatter 41
  42. 42. Victoria IMS Users GroupReduce IMS Module Aliases in RESLIB Reduced module aliases in RESLIB, where possible For remaining aliases, doc provided on module to alias dependencies Should help reduce errors when implementing selected service – Fewer aliases that can be overlooked when modules manually copied 42
  43. 43. Victoria IMS Users GroupEOM / EOT Tracing Facility Enhancement Created a step trace function in the End-of-Task (EOT) process similar to that employed by the End-of-Memory (EOM) process – Traces the step-by-step flow through the EOT process • Updates a nibble trace in the regions IDT with a unique marker – For each successful step processed – For each decision point reached and evaluated – Message DFS0798I is issued at the end of the process to externally document the results of EOT processing 43
  44. 44. Victoria IMS Users GroupNew /DIAGNOSE Command SET AOSLOG Function Support for the APPC / OTMA Synchronous Shared Queues enhancement to use XCF communications for IMS systems in a SQ Group – AOSLOG=Y|N is a new keyword in the DFSDCxxx proclib member • applicable to a Front End system only – Enable or disable the logging of x6701 records to capture events related to APPC / OTMA synchronous transactions in a shared-queues environment IMS Log Records – Front End system writes x’6701’ log trace record when response message from Back End system is received – New ID of “TIB3” is added to the x’6701’ log record Benefits – Enhanced problem diagnostic capability and quicker problem resolution 44
  45. 45. Victoria IMS Users GroupNew /DIAGNOSE Command SNAP Functions Six new SNAP resource types Resource Type SNAP Captures… AREA control block information for fast path areas DB control block information for full function databases LINE control block information for communication lines LINK control block information for MSC logical links PGM control block information for programs REGION / JOBNAME control block information for dependent regions – Support for multiple resource name parameters separated by a comma or a blank /DIAGNOSE SNAP AREA(areaname,areaname,areaname) /DIAGNOSE SNAP DB(dbname dbname dbname) 45
  46. 46. Victoria IMS Users GroupRAS Enhancements Benefits – Diagnose problems interactively – Non-disruptive alternatives to producing console dumps – Reduce time and effort to capture and analyze IMS diagnostic information – Help reduce time to resolve problems – Satisfy several customer and IBM requirements 46
  47. 47. Victoria IMS Users GroupMIPS reduction enhancements CICS threadsafe support CICS and ODBA users have new DFSRAS00 exit capability to designate a user as trusted, bypassing RACF or equivalent security checks Usage of newer, more efficient hardware instructions when available – Long displacement facility / Store Clock Fast (STCKF) facility Replacing GETMAIN storage allocation calls with more efficient IMS internal storage management calls for APPC/OTMA scheduling Supporting native 64-bit invocation of several highly used IMS internal macro services, reducing AMODE switching for 64-bit modules Efficiency/pathlength reductions in CQS inform exit processing and OTMA processing Improving IMS shutdown time by reducing OTMA/APPC shutdown quiesce waits Benefits – Improved Performance 47
  48. 48. Victoria IMS Users GroupIMS Repository Overview of the IMS Repository Function IMS Repository Function Components – Repository Server (RS) Address Space – Repository catalog data sets – Repository data sets – CSL requirements and RM usage 48
  49. 49. Victoria IMS Users GroupIMS 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 49
  50. 50. Victoria IMS Users GroupIMS Repository Function Usage The various components of the IMS repository function provide a centralized storage and retrieval solution for resource definitions In IMS 12, the resource and descriptor definitions for Dynamic Resource Definition (DRD) can be stored in an IMS repository – Contains resource definitions for programs/transactions/databases/FP routing codes & descriptors – Called the IMSRSC, the IMS resource definition repository – Provides an alternative to using RDDSs (resource definition data sets) for DRD – Replaces one or more sets of RDDSs in an IMSplex with a single repository – 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 50
  51. 51. Victoria IMS Users GroupIMS 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 or dynamically enable an IMSRSC repository via type-2 command – Can use the new IMSRSC repository to store definitions in IMS 12 Users in IMS 10 and IMS 11 without DRD – Can use the new IMSRSC repository for stored resource definitions in IMS 12 – Can create new RDDSs for stored resource definitions in IMS 12 Both RDDSs (system and non-system) and the IMSRSC repository can exist together during migration to the IMSRSC repository – Once migration is complete, use online commands to disable RDDSs 51
  52. 52. Victoria IMS Users GroupIMS Repository Function components A Repository Server (RS) – A new BPE-based address space managed by the Resource Manager (RM) CSL address space Repositories – Catalog repository • Used by the Repository Server – IMSRSC repository(s) • Contains DRD stored resource definitions A 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 – DRD utilities 52
  53. 53. Victoria IMS Users GroupIMS 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 – Repository can be implemented without an outage 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 – Via commands (3 types) – Via batch utilities (3 functions) A strategic direction for IMS architecture 53
  54. 54. Victoria IMS Users GroupIMS Repository Function components … A Repository Server (RS) – A 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 54
  55. 55. Victoria IMS Users GroupIMS Repository Function components … A Repository Server (RS) – Uses VSAM KSDS data sets to store information – Has its own internal repository called the ‘catalog repository’ – Manages IMS repositories (IMSRSC for DRD) – Manages registrations and connections to the repository – Ensures repository data integrity – Uses SAF to restrict access to repositories – Provides an audit trail using the z/OS logger – Provides tracing capabilities via BPE – Recommendation • One master repostiory server address space per IMSplex 55
  56. 56. Victoria IMS Users GroupIMS Repository Function components Repository data sets – Multiple sets of VSAM KSDS data sets – Each set composed of • Repository index data set • Repository member data set repository index • Each of these has a primary and data sets secondary data set (duplexed) (primary / secondary) – Optional spare set (third) can be defined – Two types of repository data sets • Catalog repository data sets • IMS repository data sets repository member data sets (primary / secondary) 56
  57. 57. Victoria IMS Users GroupIMS Repository Function components … Catalog repository (RS catalog data sets) – Required per repository server – Manages the Repository Server (RS) functions – Manages information about IMS repository data sets – Composed of two pairs of data sets • Primary index data set and primary member data set (required) • Secondary index data set and secondary member data set (required) • No spare capability RS catalog data sets Primary and secondary index data sets Primary and secondary member data sets 57
  58. 58. Victoria IMS Users GroupIMS Repository Function components … IMS repositories – IMSRSC repository • Contains the stored resource definitions for DRD resources for one or more DRD-enabled IMS systems – Resource lists for each IMS – Stored resource definitions (programs/transactions/databases/FP routing codes) • Supports different attribute values for a particular resource definition in different IMSs (generic / IMS-specific) • Typically one IMSRSC repository per Repository Server (RS) per IMSplex 58
  59. 59. Victoria IMS Users GroupIMS 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) (COPY1) – Secondary index data set and secondary member data set (required) (COPY2) – Spare index data set and spare member data set (optional) (SPARE) IMSRSC repository data sets Primary/secondary/ spare (optional) Primary/secondary/ spare (optional) index data sets member data sets 59
  60. 60. Victoria IMS Users GroupIMS 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 – Structured Call Interface (SCI) • Used for communications within the CSL – Optionally, a resource structure in a Coupling Facility – SPOC (single point of control) for entering type-2 commands – Can be a single-IMS IMSplex or a multiple-IMS IMSplex 60
  61. 61. Victoria IMS Users GroupIMS 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 – DRD utilities (PM41281) • MODBLKS to IMSRSC repository • IMS log to IMSRSC repository 61
  62. 62. Victoria IMS Users GroupIMS Repository Function Configuration RS Catalog Repository Operations Structured Resource Manager Call X Primary/Secondary Manager (OM) Interface C (RM) F SCI SCI SCI X Repository C Server SCI F (RS) IMS Control Region IMSRSC Repository Batch ADMIN RM Utilities SCI Utility CSLUPR10/ CSLRUP20 Primary/Secondary/Spare XCF 62
  63. 63. Victoria IMS Users GroupSummary of System Enhancements … Dynamic resource definition (DRD) enhancements zAAP/zIIP times in accounting log records zIIP support for some CQS processing Member online change NAMEONLY option EAV support for non-VSAM data sets IMS logging enhancements – Extended-format data set support for OLDS/SLDS – IMS log buffers in 64-bit virtual storage – Simplified WADS management System pools in 64-bit real storage Sysplex Serial Program Management (SSPM) Disabling SPE for log archiving of non-recoverable databases 63
  64. 64. Victoria IMS Users GroupSummary of System Enhancements Command enhancements System usability enhancements – IMS 11 SPE User Exit Enhancements RAS enhancements – CQS traceability enhancements – IMS Dump Formatter enhancements – Reduce IMS Module Aliases in RESLIB – End-Of-Memory / End-Of-Task (EOT) Tracing Facility – IMS 11 SPE BPE Trace Selective Initialization – /DIAGNOSE SNAP command enhancements MIPS reduction enhancements 64
  65. 65. Victoria IMS Users GroupInstallation and Migration Packaging, Prerequisites and Coexistence IMS Publications Changes IMS Tools support IVP and Syntax Checker Enhancements Installation and Migration Tasks 65
  66. 66. Victoria IMS Users GroupIMS 12 Packaging IMS 12 product number: 5635-A03 FMID Feature Description HMK1200 System Services JMK1201 Database Manager JMK1202 Transaction Manager JMK1203 Extended Terminal Option (ETO) JMK1204 Recovery Level Tracking (RSR) JMK1205 Database Level Tracking (RSR) JMK1206 IMS Java and On Demand HIR2220 IRLM 2.2 HIR2230 IRLM 2.3 66
  67. 67. Victoria IMS Users GroupIMS 12 Hardware Prerequisites IMS 12 requires the following hardware: – A 64-bit IBM zSeries® processor running in z/Architecture® mode (ESA mode is not supported by IMS 12) – Capable of running z/OS Version 1 Release 11 or later – A processor that supports the Long Displacement Facility of the z/Architecture Sysplex data sharing – Requires Coupling Facility (CF) level 9 or later Shared Queues and Shared EMH – Require Coupling Facility (CF) level 9 or later – System managed duplexing requires CF level 12 or later and bidirectional CF to CF links 67
  68. 68. Victoria IMS Users GroupIMS 12 Software Prerequisites Minimum software level prerequisites – z/OS V1R11 (5694-A01) – DFSMS APAR OA33409 for V1R11 – High Level Assembler Toolkit (5696-234), Version 1 Release 5 – SMP/E V3R5 – RACF, or equivalent, if security is used – IRLM 2.2, if IRLM is 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 – Greater than 16 VSAM pools requires DFSMS APAR OA32318 – CA Reclaim requires z/OS V1R12 – EAV support for non-VSAM data sets requires z/OS V1R12 68
  69. 69. Victoria IMS Users GroupIMS Enterprise Suite for z/OS, V2.1 (5655-T62) Available October 28, 2011 The SOAP Gateway, Connect API for Java™, Java Message Services (JMS) API, and Base Services components for running in the z/OS environments are orderable IMS Explorer (NEW), DLIModel Utility, Connect API for C, SOAP Gateway, Connect API for Java components for running in Windows® or Linux® environments can be downloaded from the IMS website Details at: http://www.ibm.com/ims 69
  70. 70. Victoria IMS Users GroupAdditional IMS 12 Prerequisites See the IMS 12 Release Planning (GC19-3019-01) for additional requirements – Available at: https://www- 304.ibm.com/support/docview.wss?uid=swg27019860 – Available in the Information Center at: http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp 70
  71. 71. Victoria IMS Users GroupPrerequisite Maintenance Fixes for Migration Download enhanced holddata – Run SMPE: REPORT MISSINGFIX (FIXCAT)The following are the categories that we have defined for IMS (the ones in red wereset up for tools to use in their service):Category: IBM.Coexistence.IMS.V10 Keywords: IMSV10COEX/K Description: Fixes that allow IMS V8 and V9 to coexist with, and fallback from, IMS V10.Category: IBM.Coexistence.IMS.V11 Keywords: IMSV11COEX/K Description: Fixes that allow IMS V9 and V10 to coexist with, and fallback from, IMS V11.Category: IBM.Coexistence.IMS.V12 Keywords: IMSV12COEX/K Description: Fixes that allow IMS V10 and V11 to coexist with, and fallback from, IMS V12.Category: IBM.TargetSystem-RequiredService.IMS.V10 Keywords: IMSV10TGT/K Description: Fix required on other IBM products to allow them to run with IMS V10.Category: IBM.TargetSystem-RequiredService.IMS.V11 Keywords: IMSV11TGT/K Description: Fixes required on other IBM products to allow them to run with IMS V11.Category: IBM.TargetSystem-RequiredService.IMS.V12 Keywords: IMSV12TGT/K Description: Fixes required on other IBM products to allow them to run with IMS V12. http://www-03.ibm.com/systems/z/os/zos/smpe/fixcategory.html 71
  72. 72. Victoria IMS Users GroupSupport 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 is November 5, 2012 - NEW IMS Version 11 – Generally available on October 30, 2009 – End of service has not been announced IMS Version 12 – Generally availability on October 28, 2011 – End of service has not been announced 72
  73. 73. Victoria IMS Users GroupWithdrawn Support IMS 11 is the last release to support the SMU-to-RACF utilities – IMS 9 was the last version of IMS to support SMU – Migration from SMU to RACF or an equivalent product should be done on IMS 9 or earlier IMS 10 is the last release to support z/OS-based batch DLIModel utility – IMS Enterprise Suite V1.1 DLI Model Utility plug-in should be used with IMS 12 IMS 12 is the last release to support the SECURITY macro in system definition – Use the initialization parameters 73
  74. 74. Victoria IMS Users GroupWithdrawn Support IMS 11 is the last release to support the Knowledge Based Log Analysis (KBLA) facility – Customers using this function should migrate to use other IMS-provided analysis utilities and reports, such as • Fast Path Log Analysis utility (DBFULTA0) • File Select and Formatting Print utility (DFSERA10) • IMS Monitor Report Print utility (DFSUTR20) • Log Transaction Analysis utility (DFSILTA0) • Offline Dump Formatter utility (DFSOFMD0) • Statistical Analysis utility (DFSISTS0), • Other complementary products, such as IMS Problem Investigator, IMS Performance Analyzer, or similar products. 74
  75. 75. Victoria IMS Users GroupIMS 12 Supported Connections DB2 connections are supported with – DB2 for z/OS 10, 9 and 8 DBCTL connections are supported with – CICS Transaction Server V 4.2, V4.1, V3.2 and V3.1 Java application programs using JDBC access to IMS DB from WebSphere Application Server for z/OS require – WebSphere Application Server for z/OS 7.0.1 or later IRLM 2.3 and IRLM 2.2 are supported – IMS 12, IMS 11 and IMS 10 may use either IRLM 2.2 or IRLM 2.3 – IRLM 2.3 and IRLM 2.2 may participate in the same data sharing group and connect to the same lock structure 75
  76. 76. Victoria IMS Users GroupIMS 12 Supported Connections ISC is supported with – IMS 12, IMS 11, and IMS 10 – CICS Transaction Server V 4.2, V4.1, V3.2 and V3.1 – User-written software MSC is supported with – IMS 12 – IMS 11 – IMS 10 Shared Queues is supported with – IMS 12 – IMS 11 – IMS 10 76
  77. 77. Victoria IMS Users GroupSupported Migrations and Coexistence - DBRC IMS 11 to IMS 12 – Upgrade RECONs from IMS 11 to IMS 12 • IMS 11 SPE PM05244 / UK62971 allows IMS 11 to use IMS 12 RECONs – Databases are compatible – Application programs are compatible IMS 10 to IMS 12 – Upgrade RECONs from IMS 10 to IMS 12 • IMS 10 SPE PM05243 / UK62970 allows IMS 10 to use IMS 12 RECONs – Databases are compatible – Application programs are compatible 77
  78. 78. Victoria IMS Users GroupIRLM 2.3 IRLM 2.3 and IRLM 2.2 are both shipped with IMS 12 IRLM 2.3 and IRLM 2.2 may be used with any supported version of IMS – IRLM 2.3 is required by DB2 Version 10 • IRLM 2.3 has 64-bit caller interface – IMS continues to use the 31-bit caller interface – IRLM 2.3 requires z/OS 1.10 or higher IRLM 2.3 provides improved performance for some requests – We do not expect a substantial performance improvement with IRLM 2.3 with IMS 78
  79. 79. Victoria IMS Users GroupDBCTL, ODBA and ODBM Migration The DRA interface modules must be at the same version as IMS – Copy DFSPRRC0 and DFSPZPxx load modules to the address spaces which communicate with IMS • Include these modules from IMS 12 in the CICS, ODBM and ODBA (DB2 Stored Procedures, WebSphere Application Server, etc.) address spaces 79
  80. 80. Victoria IMS Users GroupMigration with DRD IMS 12 system may be cold started with RDDS from IMS 11 or IMS 10 – IMSID must remain the same IMS 11 or IMS 10 system may be cold started with RDDS from IMS 12 for fall back – IMSID must remain the same 80
  81. 81. Victoria IMS Users GroupCSL Coexistence IMS 12, IMS 11 and IMS 10 – CSL address spaces and IMS may be at mixed levels • SCI, OM, RM, ODBM and IMS subsystems may be at IMS 12, IMS 11 and IMS 10 – IMS 12 is recommended for the CSL address spaces IMS Repository requires IMS 12 RM – Migration SPEs for IMS Repository: • Ensure that all RMs are at IMS 12 level for users of Repository 81
  82. 82. Victoria IMS Users GroupCoexistence Maintenance See Chapter 4 of IMS 12 Release Planning (GC19-3019-01) for coexistence maintenance requirements – Available at: https://www- 304.ibm.com/support/docview.wss?uid=swg27019860 – Available in the Information Center at: http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp 82
  83. 83. Victoria IMS Users GroupCoexistence - IMS Utilities Batch Backout, Log Archive, and Log Recovery – Use the utility from the IMS release that created the log IMS 12 Database Recovery utility – Accepts Image Copies produced by IMS 12, IMS 11 and IMS 10 – Accepts HISAM Unloads produced by IMS 12, IMS 11 and IMS 10 – Accepts Change Accum data sets produced by IMS 12, IMS 11 and IMS 10 – Accepts logs produced by IMS 12, IMS 11 and IMS 10 IMS 12 Change Accumulation utility – Accepts logs produced by IMS 12, IMS 11 and IMS 10 – Accepts Change Accum data sets produced by IMS 12, IMS 11 and IMS 10 83
  84. 84. Victoria IMS Users GroupRemote Site Recovery (RSR) Migration/Coexistence IMS 12 RSR tracking system can process logs created by IMS 12, IMS 11, or IMS 10 IMS 12 RSR Isolated Log Sender can send logs created by IMS 12, IMS 11, or IMS 10 Logs created by IMS 12 cannot be processed by IMS 11 or IMS 10 tracking system or Isolated Log Sender Migration steps – Upgrade the RSR tracking system RECONs to IMS 12 – Migrate RSR tracking system to IMS 12 – Upgrade the active system RECONs to IMS 12 – Migrate active system Transport Manager Subsystem (TMS) running Isolated Log Sender to IMS 12 – Migrate active IMS to IMS 12 84
  85. 85. Victoria IMS Users GroupLog Records Change in log suffix – Timestamp in log record suffix is no longer necessarily unique • Previous versions produced unique timestamps • Sequence number is unique Some log records have changed New log records have been added DSECTS for most IMS log records may be generated by assembling: – ILOGREC RECID=ALL 85
  86. 86. Victoria IMS Users GroupIMS Publications IMS publications structure and titles remain the same as in IMS 11 – PDF master index and glossary are not available – Master index and glossary are included in the information center – Bookmanager format publications will not be published (same as IMS 11) All publications will be available in hardcopy for an additional charge 86
  87. 87. Victoria IMS Users GroupIMS Library The Information Center contains information on IMS 12 http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp 87
  88. 88. Victoria IMS Users GroupIMS 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 88
  89. 89. Victoria IMS Users GroupIMS Tools Migration/Coexistence Some products may require updates – Contact your vendors for information on requirements – IBM has a web site with consolidated information about requirements for IBM IMS tools with IMS 12 • https://www- 304.ibm.com/support/docview.wss?rs=434&uid=swg21296180 89
  90. 90. Victoria IMS Users Group IBM IMS Tools - Highlights New IMS Tools Solution Packs – In general, IBM will support the latest stand-alone version of every tool as well as their Solution Pack counterpart if one exists • Special circumstances not withstanding – Latest versions of TOSI, Generic Exits, IMS Tools Knowledge Base, and HD Compression Extended are only supported in the IMS Tools Base Pack for z/OS. – Fast Path Secondary Index creation tool is included in the IMS Fast Path Solution Pack for z/OS, V1.290 90
  91. 91. Victoria IMS Users GroupIVP Enhancements Repository usage for DRD is added to IVP – IVP provides sample JCL to create repository catalog data sets and the IMS repository – IVP provides sample repository server PROC and its configuration file – Sample JCL is provided to: • Add an IMS repository into the repository catalog • Rename a repository in the repository catalog • Delete a repository in the repository catalog • List the status information for all repositories • List the detailed information for a single repository 91
  92. 92. Victoria IMS Users GroupSyntax Checker Enhancements Syntax Checker supports PROCLIB members for IMS 12, IMS 11 and IMS 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 for dynamic full-function database buffer pools Support added to view and save parameters of members in a custom order – Formerly, only alphabetical order was used – Delivered through the IMS service process (PM30599/UK74973) 92
  93. 93. Victoria IMS Users GroupInstallation and Migration Tasks Migration Tasks – Review the IMS 12 Release Planning publication – Check PSP bucket • PSP upgrade name is IMS1200 • Use SMP FIXCAT HOLDDATA to simplify identifying required service from PSP buckets – Review the Program Directory • Available through the Info Center – Review the installation information in Chapter 1 of the Installation publication – Install prerequisite software and maintenance • Check your IMS tools and related products – Apply coexistence maintenance to other IMS systems 93
  94. 94. Victoria IMS Users GroupInstallation and Migration Tasks Migration Tasks (continued) – Evaluate and update IMS exit routines • RECON I/O Exit Routine (DSPCEXT0) • If migrating from IMS 10 – DFSMSCE0 must be reassembled – All IMS Connect exits must be reassembled when migrating IMS Connect – HWSIMSO0 and HWSIMSO1 are not shipped with IMS 12 • Recommendation – Reassemble all exit routines which use IMS macros – Install IMS 12 using SMP/E installation process • CBPDO or ServerPac may be used – System definition • “ALL” sysgen 94
  95. 95. Victoria IMS Users GroupInstallation and Migration Tasks Migration Tasks (continued) – Install the Type 2 and Type 4 SVCs – Upgrade RECONs – ACBGEN – Run the IVP – Include DFSPRRC0 and DFSPZPxx modules in CICS, ODBM and ODBA address spaces 95
  96. 96. Victoria IMS Users GroupInstallation and Migration Summary Packaging, Prerequisites and Coexistence IMS Publications Changes IMS Tools support IVP and Syntax Checker Enhancements Installation and Migration Tasks 96
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×