Embed Size (px)
Citation preview
Charlotte
IMS User Group
IMS Installation & Migration Considerations
12/11/2013
IBM SILICON VALLEY LABORATORY
IMS SOFTWARE SERVICE DELIVERY
1
IMS SOFTWARE SERVICE DELIVERY
555 BAILEY AVENUE
SAN JOSE, CALIFORNIA 95141
John Butterweck
(408) 463-4896
�The objectives of this session are:
�Discuss the installation and packaging for IMS Version 12 & 13
�Discuss migration considerations when migrating to IMS Version
12 or 13
�Questions are good. We all learn from them, so don’t hold back
Objectives
2
�Questions are good. We all learn from them, so don’t hold back
Packaging
Packaging
�Packaging
�No major changes in packaging since IMS 8.1
�Installation via CBPDO, ServerPac or CustomPac
�All FMIDs are installed using SMP/E RECEIVE, APPLY, ACCEPT
Packaging
4
�All FMIDs are installed using SMP/E RECEIVE, APPLY, ACCEPT
–Conform to packaging standards
–Results in multiple SMP/E messages indicating no target library for parts
defined by SYSGEN
�Program Directory contains message id's
–Sample jobs provided will process service as well as FMIDs
�SMP/E Processing
•Always RECEIVE current Enhanced HOLDDATA prior to SMP/E processing
–For complete descriptive information relating to Enhanced Holddata see
Internet address: http://service.boulder.ibm.com/390holddata.html
•Be sure to resolve PE's during processing
SMP/E Processing
5
•Be sure to resolve PE's during processing
� Contact the IBM Support Center for assistance as needed
�Only IRLM 2.3 (FMID HIR2230) provided
•Works with all supported releases of IMS
�In IMS V12 both IRLM 2.3(FMID HIR2230) and IRLM 2.2 (FMID HIR2220)
may be provided
•Depending on how IMS is ordered
–
V13 Changes - IRLM
6
–Both with CBPDO
–IRLM 2.3 with ServerPac
� IVP Dialog Changes – V13
�Variables added which are used to build proclib member HWSCFGxx for ISC link
V13 Changes – IVP
7
The current naming convention used for paths allows for more granularity
The following shows the old and new path names
DDNAME V13 Path Name V12 Path Name
-------- --------------------------------- -------------------------------------------------------
SDFSIC4J /usr/lpp/ims/ims13/ico/IBM/ /usr/lpp/ims/ims12/ico/IBM/
SDFSJCIC /usr/lpp/ims/ims13/imsjava/classic/cics/IBM/ /usr/lpp/ims/ims12/imsjava/classic/cics/IBM/
SDFSJCPI /usr/lpp/ims/ims13/imsjava/classic/IBM/ /usr/lpp/ims/ims12/imsjava/classic/IBM/
SDFSJCPS /usr/lpp/ims/ims13/imsjava/classic/ivp/IBM/ /usr/lpp/ims/ims12/imsjava/classic/ivp/IBM/
SDFSJHFS /usr/lpp/ims/ims13/imsjava/IBM/ /usr/lpp/ims/ims12/imsjava/IBM/
/usr/lpp/ims/ims13/imsjava/rar/IBM/ /usr/lpp/ims/ims12/imsjava/IBM/
V13 Changes - Path Name Changes (V12 to V13)
8
SDFSJRAR /usr/lpp/ims/ims13/imsjava/rar/IBM/ /usr/lpp/ims/ims12/imsjava/IBM/
SDFSJSAM /usr/lpp/ims/ims13/imsjava/ivp/IBM/ /usr/lpp/ims/ims12/imsjava/ivp/IBM/
SDFSJ2CI /usr/lpp/ims/ims13/imsjava/cics/IBM /usr/lpp/ims/ims12/imsjava/cics/IBM
NOTE: More may be added by maintenance
�Both IRLM 2.3(FMID HIR2230) and IRLM 2.2 (FMID HIR2220) may be
provided in IMS V12
•Depending on how IMS is ordered
–Both with CBPDO
–IRLM 2.3 with ServerPac
V12 Changes - IRLM
9
•Both versions work with all supported releases of IMS
•Both work in 32 and 64 bit processing mode
�MSC Channel Appendage
•IMS V11 and below module IGG019zz had to be placed in the LPA
concatenation
•IGG019zz is created during SYSGEN when the APNDG keyword was
specified in the IMSCTF macro
•IMS V12 and above module DFSCMC10 is loaded during control
V12 Changes - MSC Channel Appendage
10
•IMS V12 and above module DFSCMC10 is loaded during control
region initialization
–IGG019xx no longer needed
�No longer an LPA requirement for IGG019zz
�No user setup is required
–This change was introduced by PTF UK71482
The naming convention used for paths has been changed to allow more granularity
The following shows the old and new path names
DDNAME V12 Path Name V11 Path Name
-------- --------------------------------- -------------------------------------------------------
SDFSIC4J /usr/lpp/ims/ims12/ico/IBM/ /usr/lpp/ims/ims11/ico/IBM/
SDFSJCIC /usr/lpp/ims/ims12/imsjava/classic/cics/IBM/ /usr/lpp/ims/ims11/imsjava/classic/cics/IBM/
SDFSJCPI /usr/lpp/ims/ims12/imsjava/classic/IBM/ /usr/lpp/ims/ims11/imsjava/classic/IBM/
SDFSJCPS /usr/lpp/ims/ims12/imsjava/classic/ivp/IBM/ /usr/lpp/ims/ims11/imsjava/classic/ivp/IBM/
SDFSJHFS /usr/lpp/ims/ims12/imsjava/IBM/ /usr/lpp/ims/ims11/imsjava/IBM/
SDFSJHWS N/A /usr/lpp/ims/ims11/hws/IBM/
V12 Changes - Path Name Changes (V11 to V12)
11
SDFSJHWS N/A /usr/lpp/ims/ims11/hws/IBM/
SDFSJIOG N/A /usr/lpp/ims/ims11/iog/IBM/
SDFSJRAR /usr/lpp/ims/ims12/imsjava/rar/IBM/ /usr/lpp/ims/ims11/imsjava/rar/IBM/
SDFSJSAM /usr/lpp/ims/ims12/imsjava/ivp/IBM/ /usr/lpp/ims/ims11/imsjava/ivp/IBM/
SDFSJTOL N/A /usr/lpp/ims/ims11/imsjava/classic/dlimodel/IBM/
SDFSJ2CI /usr/lpp/ims/ims12/imsjava/cics/IBM (UK72694) N/A
NOTE: More may be added by maintenance
� IVP Dialog Changes – V12
�Option to use IMSRSC Repository
�IMS Catalog
V12 Changes – IVP
12
–Added via service (PTF UK78071)
Installation
Installation
�The IMS product can be distributed by a variety of methods. Which are as follows:
�CBPDO - DBS Feature distribution tapes
�SERVERPAC - DBS Feature pre-built SMP/E, DLIBs and TLIBs
�SYSTEMPAC – DBS Feature may be customized
Distribution Media
�ShopZseries delivery schedules can be found at the following:
https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp?action=glcrad
� SUP is a roll up of maintenance into the FMID’s
• Ease installation
• Existing customers do not need to reinstall
• Maintenance continues to be distributed as usual
• May be used as a way to upgrade maintenance
• All product orders filled after the SUP is available will be built at the
SUP level
• PSP buckets contain the details of the SUP
IMS SUP
• PSP buckets contain the details of the SUP
–List of APARs included in the FMDs
� IMS V12 SUP available 5/17/2013
• Service thru 2/2013 included in the base of the corresponding FMIDs
� Installation Documentation Precedence
�Documentation provided with CBPDO, ServerPac, etc.
�PSP Bucket
–Contains the latest information
Documentation Precedence
�Program Directory
�IMS Installation
�The following is a list of the SMP/E Setup and SMP/E sample jobs provided:
�DFSALA - Allocate and initialize new CSI datasets (optional but recommended)
�DFSALB - Initialize SMP/E zones allocated (optional but recommended)
–Ensure ACCJCLIN is specified in DLIB zone before processing FMIDs
�RECEIVE - Receive job provided by CBPDO
–Program Directory contains instructions for obtaining the JCL
�DFSALLOC - Allocate target and distribution libraries
�DFSJSMKD - Invoke DFSJMKDR EXEC to allocate ZFS/HFS paths for IMS JAVA
SMP/E Setup and SMP/E Jobs (CBPDO)
�DFSJSMKD - Invoke DFSJMKDR EXEC to allocate ZFS/HFS paths for IMS JAVA
�DFSDDEF1 - Define SMP/E DDDEFs for core IMS
�DFSDDEF2 - Define SMP/E DDDEFs for IMS On Demand
�DFSAPPLY - SMP/E APPLY of FMID's and service
–Be sure to resolve PE's
�DFSACCEP - SMP/E ACCEPT of FMID's and service
–Be sure to resolve PE's
�Optional jobs provided to install IMS in its own unique SMP/E environment
(GLOBAL Zone)
�DFSALA - Allocate and initialize new CSI
�DFSALB - Initialize CSI zones, allocate SMP/E datasets, build DDDEF
entries for SMP/E
Optional Sample Jobs (CBPDO)
�Recommend using these jobs
� If these jobs are NOT used, be sure ACCJCLIN is set in the IMS
distribution zone prior to ACCEPT processing
–ACCJCLIN is set in sample job DFSALB
–SMP/E OPTION and UTILITY entries added in sample job DFSALB
�JCL provided in Program Directory to unload sample jobs to perform
SMP/E processing and setup
�Each job contains instructions for customization
�Same variables in multiple jobs so may want to save in a separate file
to use copy and paste
SMP/E Setup and SMP/E Jobs (CBPDO)
to use copy and paste
– C #globalcsi IMS.V13.GLOBAL.CSI all
– C targlib IMS13T all
The following is an example of the instructions for customization of the sample
jobs:
//* NOTES: */
//* 1) REVIEW THE SMP CONTROL STATEMENTS BEFORE SUBMITTING */
//* THIS JOB. */
//* 2) ADD A JOB CARD TO MEET YOUR SYSTEM'S REQUIREMENTS. */
//* 3) CHANGE #globalcsi TO THE DATASET NAME OF YOUR GLOBAL */
//* CSI DATA SET. */
//* 4) CHANGE targlib TO THE NAME OF YOUR TARGET ZONE. */
//* 5) REMOVE THOSE FMIDs THAT YOU DO NOT WISH TO APPLY FROM */
Sample Installation Job Customization (CBPDO)
20
//* 5) REMOVE THOSE FMIDs THAT YOU DO NOT WISH TO APPLY FROM */
//* THE SELECT AND FORFMID OPERANDS OF THE APPLY STATEMENT. */
//* HMK1300 <======= FMID to be installed */
//* HIR2230 <======= FMID to be installed */
//* JMK1301 <======= FMID to be installed */
//* JMK1302 <======= FMID to be installed */
//* JMK1303 <======= FMID to be installed */
//* JMK1304 <======= FMID to be installed */
//* JMK1305 <======= FMID to be installed */
//* JMK1306 <======= FMID to be installed */
NOTE - The lower case characters. Be sure to specify 'CAPS ON' as appropriate HFS path
names need to be in lower case characters
�SMP/E GENERATE command
�Used to create JCL to build elements in target libraries from elements in distribution libraries
– When run before ANY SMP/E JCLIN processing after sysgen, JCL created will be that to
build non-sysgen elements only
– When run after ANY SMP/E JCLIN processing after sysgen, JCL created will be to build
both non-sysgen elements and sysgen elements
� Will encounter errors indicating no DLIB for non IMS macros
– Dependent on ACCJCLIN being set up in distribution zone BEFORE processing FMID's
– Sample command:
SMP/E GENERATE
21
– Sample command:
SET BDY(targlib) .
GENERATE JOBCARD(CNTL,J) REPLACE .
** (NOTE: This sample requires DD CNTL to contain member 'J' which is a sample job
card)
�Used as part processing of service via ACCEPT BYPASS APPLYCHECK or when target
environment needs to be rebuilt from the distribution environment
– Not needed when processing using RECEIVE, APPLY, ACCEPT
– See Informational APARS II13024 & II14567 (On Demand)
� User Exit Packaging
�Optional user exits now in SDFSSMPL
�User exits created as ++SRC type part
Allows line updates during SMP/E processing of service as opposed to complete
replacement
�Corresponding ++MOD parts (Object Code) NOT shipped
User Exits
22
�Corresponding ++MOD parts (Object Code) NOT shipped
– No MOD to LMOD relationships are created during IMS install so SMP/E will not
automatically assemble and bind the parts during APPLY processing
– If the user creates the MOD to LMOD relationship then SMP/E APPLY
processing will automatically assemble and bind these exits
�Working toward all having user exits handled the same way
�There are issues when a module is part of various load modules some built by
SYSGEN and some built in USERMODS as part of a USER Exit
IMS Migration
Considerations
Migration Considerations
Considerations
�Verify software and hardware requisites
•Program Directory
�Migration/Coexistence maintenance
•REPORT MISSINGFIX (FIXCAT)
•PSP Bucket
�Review IMS Release Planning guide for this release and any release being skipped
Migration Tasks
24
�Review PSP Buckets (UPGRADE: IMS1300 | IMS1200)
�Install new version of IMS
�Possible upgrade to IMS tools and related products
•See http://tinyurl.com/br8y2o7
�Install z/OS interface modules
�Perform any D/B recoveries that have Extended Error Queue Elements (EEQE's)
•/DIS DB EEQE
�Upgrade RECONs
•When MINVER changed to 10.1 need to create IC before running Change Accuum
– When upgrading to IMS V12 MINVER may be set to 10.1
�System definition (ALL)
�ACBGEN
�Possible changes to procedures or jobs – Ensure DRA Client address spaces (CICS,DB2
Migration Tasks - 2
25
�Possible changes to procedures or jobs – Ensure DRA Client address spaces (CICS,DB2 SPAS, etc.) point to correct SDFSRESL (DRA and JCL)
�Re-assemble any user code that accesses IMS control blocks or log records
•Re-work USERMODS as necessary
•Don’t forget about DFSIDEF0
�Ensure appropriate Dynamic Allocation members and exits are available to the new
environment
•Compare members in current SDFSRESL to those in new SDFSRESL
�Consider changes to execution parms that may affect performance
�AIB INQY ENVIRON call, application I/O area from a minimum of 100 bytes to 108 bytes• AIBOALEN minimum of 160 recommend make larger for future expansion (512)
– INQY ENVIRON data 108 bytes – Length of Recovery token 2 bytes– Recovery token 16 bytes– Length of APARM section 2 bytes– APARM data 32 bytes
-------------
Migration Tasks - 3
26
-------------160 bytes (minimum)
NOTE: Recovery Token and APARM are optional fields which if present follow ENVIRON data. Do NOT use offset to get to Recovery Token or APARM, use pointers contained within the ENVIRON data otherwise will need adjust application as needed to accommodate offset changes
•Application programs may need to be modified if recommendations not followed. •V12 and above
•IMS V12 - after UK78069 (PUT1204)
�See PM71860 for additional details
�AG status code
�SECURITY macro removed from SYSGEN (V13)
•Parms in DFSPBxxx and DFSDCxxx
•Exits DFSCSGN0, DFSCTRN0, DFSCTSE0 no longer in DFSVNUCx
– Standalone loaded at startup
– If the exit routines cannot be linked separately or cannot use a common
Migration Tasks - 4
27
– If the exit routines cannot be linked separately or cannot use a common work area, they must be linked in the following manner:
�If the CSECT of DFSCTSE0 is part of DFSCTRN0 source, DFSCTSE0 must be linked as an ALIAS of DFSCTRN0.
�If virtual address spaces are used to exchange data between DFSCSGN0, DFSCTRN0, and DFSCTSE0, both DFSCTSE0 and DFSCSGN0 must be linked as an ALIAS of DFSCTRN0.
�IMS V9 is the last release to support SMU
•Plan ahead as this may be an issue
�Consider changes in IMS commands
�Monitor changes in storage utilization (CSA/ECSA/PRIVATE/EPRIVATE)
�Prepare and test a fallback plan
�Cold start (/NRE CHKPT 0 FORMAT ALL)
Migration Tasks - 5
28
�Cold start (/NRE CHKPT 0 FORMAT ALL)
�Recommend initial migration be done without implementing optional new functions.
•Once stable in production then take advantage of new functions
–Initially turn off the Threadsafe function
�The option is specified in the DFSPZPxx member. The DFSPRP parm is OPENTHRD=CCTL | DISABLE – (V12 UK81843 - PUT1209)
–If FPBP64=Y specified, initially turn off 64-BIT DEDB buffer compression/pre-expansion.
�Service for UK92995 (1304) changes default to ‘N’
�In DFSDFxxx specify FPBP64C=N and FPBP64E=N
�
Migration Considerations
29
�Migration Overview:
�Similar tasks as previous IMS release-to-release migrations
–Application programs continue to work without any change or recompile
�Databases do not have to be changed, upgraded, reorged, image copied, etc.
–Potential exception with Change Accuum when MINVER initial changing to 10.1
�Migrating to V12
�Log records have been modified and added
–Products which read logs may need to be updated
–User written programs may need to be modified
–ILOGREC macro may be assembled to map DSECTs for most IMS log records
�ILOGREC RECID=ALL
�CQS (Shared Queues)
•IMS V13 cannot register with a pre IMS V13 CQS
�IMS V12 cannot register with a pre IMS V12 CQS
�IMS V11 or IMS V12 can register with an IMS V13 CQS
�User or vendor written CQS clients that want to register with IMS V13 CQS must use
CQS macros from IMS V11, IMS V12 or IMS V13
�User or vendor written CQS clients that are assembled with IMS V13 CQS macros
cannot register with a PRE IMS V13 CQS
�A V11, V12 or V13 CQS can connect to the same coupling facility
Coexistence
30
�A V11, V12 or V13 CQS can connect to the same coupling facility
�CSL
•If running a mixed version IMSplex recommend using SCI and OM from the latest version of IMS
�Data Sharing
�IMS databases may be shared between supported IMS releases
�Database Recovery Utilities
�IMS V13 Database Recovery utility (DFSURDB0) and Database Change Accumulation
utility (DFSUCUM0)
–Accepts logs, Image Copy and Change Accumulation datasets from IMS V11 or later
�Utility inputs
�Batch Backout, Log Archive, Log Recovery, Log Analysis
–Use utility from IMS release which produced the log
Coexistence - Cont
31
–Use utility from IMS release which produced the log
�IMS V13 RECONs may be used by all supported IMS releases
–With compatibility service
�Extended checkpoints
•Cannot be used to restart applications across different IMS versions
�See Release Planning Guide for additional considerations
Fallback
�A system may fallback to a previous release after upgrade
�Upgraded RECONs are used
�Additional considerations:
–Database recoveries use latest IMS version utilities
–Always use ACBLIB built at the level of the running system
Fallback
–Always use ACBLIB built at the level of the running system
–Cold start (/NRE CHKPT 0 FORMAT ALL)
�The following SVC's are used by IMS
�T2 DFSVC200 (IGCxxx)
–Downward compatible. Can use the one from the highest level of IMS with previous versions
–SVC number specified in SYSGEN
�SVCNO keyword on IMSCTF macro
�DFSPBxxx member
– Can be updated dynamically for life of the IPL using DFSUSVC0
IMS SVCs
– Can be updated dynamically for life of the IPL using DFSUSVC0
�T4 DSP00MVS (IGC00xxx)
–Downward compatible. Can use the one from the highest level of
IMS with previous versions
–SVC number specified in SYSGEN
�SVCNO keyword on IMSCTF macro
– Can be updated dynamically for life of the IPL using DFSUSVC0
�IMS Utility DFSUSVC0 can be used to update both the IMS T2 and IMS T4 SVC dynamically
�Lasts for the life of the IPL
–Loads SVC in CSA/ECSA and updates z/OS SVCTABLE to point to new module
–T2 SVC processing
�Checks IMS SVC directory table to determine if any IMS tasks/jobs currently running and if so request to update T2 SVC fails
–T4 SVC processing
�Load a new copy in ECSA each time DFSUSVC0 run requesting T4 SVC to be
DFSUSVC0
�Load a new copy in ECSA each time DFSUSVC0 run requesting T4 SVC to be updated
–The following shows an example of the JCL which for executing DFSUSVC0://STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(2,4)'
//*STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(2)'
//*STEP1 EXEC PGM=DFSUSVC0,PARM='SVCTYPE=(4)'
//STEPLIB DD DSN=IMS.SDFSRESL,DISP=SHR
//DFSRESLB DD DSN=IMS.SDFSRESL,DISP=SHR
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121)
�In IMS V12 and above the CTC appendage module DFSCMC10 resides in
SDFSRESL
• No longer defined in SYSGEN
–IGG019zz no longer created
IGG019zz
–No longer requirement to have the module in LPA
�For an IMS V11 and below system using MSC with the CTC option module
IGG019zz is required
�Specified during SYSGEN
–APNDG keyword on IMSCTF macro
�Contact the IMS Level 2 for assistance
•We are here to help and your success is our reason for being
Migration/Installation Assistance
36
Acknowledgements and Disclaimers
Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
© Copyright IBM Corporation 2013. All rights reserved.
•U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, ibm.com, and IMS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM atthe time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml
Other company, product, or service names may be trademarks or service marks of others.
Questions ?
