IMS V10 Installation and Migration

Considerations

IBM SILICON VALLEY LABORATORYIMS SOFTWARE SERVICE DELIVERY

555 BAILEY AVENUESAN JOSE, CALIFORNIA 95141

John Butterweck(408) 463-4896

jbutterw@us.ibm.com

DisclaimerImportantDisclaimer

THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.

WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.

IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE.

IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.

NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:

CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE.

3

�The objectives of this session are:

�Discuss the installation and packaging changes for IMS Version 10

�Discuss migration considerations

�Provide hints and tips to aid with a smooth migration

Objectives

4

Installation and Packaging Changes

Installation & Packaging

5

�No major changes in the installation process since IMS 8.1•Standard SMP/E RECEIVE, APPLY, ACCEPT processing used•Product tapes (ISD) no longer available

–Installation via CBPDO, ServerPac or CustomPac

�IMS Publication reorganization

�Changes in packaging and installation process from IMS V9 to IMS V10•Only IRLM 2.2 provided

–IRLM 2.1 no longer provided

�Changes in packaging and installation process from IMS V8 to IMS V9•IMS Connect now packaged as part IMS product•Dynamic Resource Cleanup module DFSMRC20 provided•IVP dialog can now EXPORT and IMPORT variables

Packaging and Installation Changes - Summary

6

�SMP/E Processing

�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

•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

•Resolve PE's during processing

•Contact the IBM Support Center for assistance as needed

SMP/E Processing

7

�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 */ //* THE SELECT AND FORFMID OPERANDS OF THE APPLY STATEMENT. */ //* HMK1010 <======= FMID to be installed */ //* HIR2220 <======= FMID to be installed */ //* JMK1011 <======= FMID to be installed */ //* JMK1012 <======= FMID to be installed */ //* JMK1013 <======= FMID to be installed */ //* JMK1014 <======= FMID to be installed */ //* JMK1015 <======= FMID to be installed */ //* JMK1016 <======= 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

Job Customization

8

�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

�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

Optional Sample Jobs

9

�The IMS Library is being reorganized and restructured

•Goal is to have in a task oriented structure

–Example - Activities needed to accomplish an IMS SYSGEN in one place as opposed to having to go to several different manuals to find them

•An adjustment to the way to locate information

•Work in process

IMS Library Reconstruction in Process

10

�Only IRLM 2.2 (HIR2220) provided

�Works with all supported releases of IMS

•Works in both 32 and 64 bit processing mode

IRLM

11

�IMS Connect now packaged as part IMS product

•Introduced in IMS V9–If IMS installed target/distribution zone containing IMS Connect, IMS

Connect FMIDs will be deleted

�IMS Connect packaged as part of services FMID HMK1010–Formerly FMID HIC2210 for IMS Connect 2.1–Formerly FMID HIC2220 for IMS Connect 2.2

�IMS Connector for Java (IC4J) packaged as part of IMS Java on Demand Features (FMID JMK1016)–Formerly FMID HIC2211 for IMS Connect 2.1–Formerly FMID HIC2221 for IMS Connect 2.2

IMS CONNECT

12

�Dynamic resource cleanup module DFSMRC20 provided�No user setup is required�IMS V9 and above�Eliminates need to ZAP z/OS CSECT IEAVTRML in module IGC0001C to

contain the name DFSMRCL0–Cause of many S1 problems

�Eliminates need to have DFSMRCL0 in LPA

�If running with versions of IMS prior to V9 still need DFSMRCL0 and all it's associated requirements�DFSMRCL0 provided with IMS V10 and IMS V9 per customer request

–Not used by IMS V9 and above

�Installation Volume 1 contains sample to uninstall DFSMRCL0�Should be done when ALL IMS systems are V9 and above

DFSMRC20

13

EX 'IMS.V10.SDFSEXEC(DFSIVPEX)' 'HLQ(IMS.V10)'

IVP Export

IVP Variable Export Utility Command ===>

Enter the following information, then press enter.

_ 1. Select the IVP Environment 1. DBB - Database Management (Batch) 2. DBC - Database Management (DBCTL) 3. DBT - Database and Transaction Management (DB/DC) 4. XRF - DB/DC with Extended Recovery Facility (DB/DC with XRF) 5. DCC - Transaction Management (DCCTL)

2. Specify the IVP High Level Qualifier (IVP) of the INSTATBL dataset

IMS91___________________________ 3. Specify the Export Dataset. (If the dataset does not exist, you will

be prompted to create the dataset)

'IMS91.EXPORT'_____________________________________________

14

�Exported dataset can be modified using ISPF to change variables in mass

�Can use ISPF edit command for example to change all occurances of 91 to 10:C 91 10 all

–Example of data from an EXPORT:

<var>IXUUTLHQ</var> <val>IVPUTL91</val> <var>IXUEXEHQ</var> <val>IVPEXE91</val> <var>IXUSYSHQ</var> <val>J93.I91A2A.DBDC</val> <var>IXUDLBHQ</var> <val>J93.I91A2A.DBDC</val> <var>IXUSMPHQ</var> <val>IVPSMP91</val> <var>IXURLMHQ</var> <val>IVPRLM91</val> <var>IXUIVPHQ</var> <val>JBUTTER.IMS910C</val>

�Can export variables from IMS V6 thru IMS V10

IVP Export - cont.

15

�IVP Import function an Action Code in Variable Gathering

IVP Import

IVP Variable Gathering (LST Mode) - DBT .. Row 1 to 8 of 176Command ===> Scroll ===> CSR

Action Codes: Chg Doc eNt Rfr Imp Exp -- CHG is default if item modified

Variable = Value.................................................. Var-Title......................................................

I IXUIVPHQ = JBUTTER.IMS10C IVP - High level DSNAME qualifier for IVP (IVP) data sets

! IXURLMHQ = IVPRLM10 IVP - High level DSNAME qualifier for IRLM (RLM) data sets

* IXUDLBHQ = IMSSST.I10APAR.DBDC.M.CM1 IVP - High level DSNAME qualifier for IMS DLIB (DLB) data sets

* IXUSYSHQ = IMSSST.I10APAR.DBDC.M.CM1 IVP - High level DSNAME qualifier for IMS System (SYS) data sets

! IXUEXEHQ = IVPEXE10

�Imports all variables from an exported dataset

16

IMS Migration Considerations

Migration Considerations

17

Migration Considerations

�Recommend initial migration be done without implementing optional new functions�Once stable in production then take advantage of new functions

�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.

�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

Migration Considerations

18

�Migration Tasks�Verify software and hardware requisites

–Program Directory�Migration/Coexistence maintenance �Review IMS Release Planning guide for this release and any release being skipped�Review PSP Bucket�Install new version of IMS�Possible upgrade to IMS tools and related products

–See PSP bucket�Install z/OS interface modules�Perform any D/B recoveries that have Extended Error Queue Elements (EEQE's)�Upgrade RECONs�System definition�ACBGEN�Possible modifications to procedures or jobs�Re-assemble any user code that accesses IMS control blocks or log records�Consider changes to execution parms that may affect performance�Consider changes in IMS commands�Prepare a fallback plan�Cold start

Migration Tasks

19

Coexistence with previous releases�CQS

• IMS V10 CQS cannot register with a pre IMS V10 CQS�IMS V9 CQS cannot register with a pre IMS V9 CQS�IMS V8 or IMS V9 CQS can register with an IMS V10 CQS�User or vendor written CQS clients that want to register with IMS V10 CQS must use CQS macros from

IMS V8, IMS V9 or IMS V10�User or vendor written CQS clients that are assembles with IMS V10 CQS macros cannot register with a

PRE IMS V10 CQS�A V8, V9 or V10 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 V10 Database Recovery utility and Database Change Accumulation utility

–Accepts logs, Image Copy and Change Accumulation datasets from IMS V9 and IMS V8�Utility inputs

�Batch Backout, Log Archive, Log Recovery, Log Analysis–Use utility from IMS release which produced the log

�IMS V10 RECONs may be used by all supported IMS releases –With compatibility service

Coexistence

20

Coexistence with previous releases - Cont.

�Extended checkpoints�Cannot be used to restart applications across different IMS versions

�See Release Planning Guide for additional considerations

�See the PSP bucket for most current information•UPGRADE: IMS1010

Coexistence - 2

21

Fallback

�A system may fallback to a previous release after upgrade

�Upgraded RECONs are used

�If MINVERS= '10.1‘ had been specified–Ensure all V10 subsystem records are removed (see RPG)–Use DELETE.LOG and DELETE.ALLOC to remove V10 log records–Change RECON MINVERS (‘8.1’/’’91’)–Image copy to establish new recovery points

�Additional considerations:–Database recoveries use latest IMS version utilities–Always use ACBLIB built at the level of the running system–Cold start

Fallback

22

�The following modules are unique to each z/OS system:

�DFSAFMD0 - Abend Formatting Routine – Online dump formatter. Not normally used depends on FMTO option

specified (or defaulted to). Recommend use default of FMTO=D – Must be zapped into module IGC0805A CSECT IEAVADFM– Consider providing SYSMDUMP in JCL as opposed to

SYSUDUMP/SYSABEND in the online regions

�DFSMRCL0 - Resource Cleanup Manager - NO LONGER NEEDED WHEN ALL SYSTEMS ON IMS V9 OR ABOVE

–DFSMRC20 used for IMS V9 and above, dynamically added via RESMGR macroƒCleans up environment after termination

–Use either the V9/V10 version of DFSMRCL0, or the version of DFSMRCL0 from the highest pre V9 level

z/OS Routines

23

�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ƒRequires that no tasks or jobs are currently executing that are using it

�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

ƒBeginning with IMS V9ƒNew copy in ECSA each time

IMS SVCs

24

�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

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)

–Prior to IMS V9 can only update T2 SVC

DFSUSVC0

25

Hints and Tips

Hints & Tips

26

� IVP Dialog Changes – V10

�Options to include RACF added

�Option to include JAVA added

�Dynamic Resource Definition User Interface (DRD)

�IMS Connect

�DB setup for XQUERY

�SPOC Audit Trail (in progress)

IVP Changes – V10

27

� IVP Dialog Changes - V9

�CQS (Shared Queues) optional samples provided

�Enhanced Command Environment Samples added–SPOC samples with SCI & OM automatically started and without RM

�Samples for the setup of the IMS dump formatter and to provide examples of using the IMS dump formatter to process an IMS dump

�Sample for setting up z/OS dump options

�A new and separate high-level-qualifier variable for VSAM data sets

�SMS Storage Class and SMS Management Class parameters are available for allocating all data sets

IVP Changes - V9

28

�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

–DFSJCLIN no longer necessary–Dependent on ACCJCLIN being set up in distribution zone BEFORE processing FMID's–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 APAR II13024

SMP/E GENERATE

29

�User Exits

�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

–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

User Exits

30

�The following is an example of a technique that can be used to have SMP/E Assemble and Bind one of the sample exits:

++ USERMOD (XYZUMOD) . ++ VER (P115)

FMID(HMK1010) . ++ JCLIN. //INJCLIN JOB . . . //LKED EXEC PGM=IEWL, // PARM='('SIZE=(880K,64K)',RENT,REFR,NCAL,LET,XREF,LIST) //ADFSLOAD DD DSN=IMS.ADFSLOAD,DISP=SHR //SYSPUNCH DD DSN=IMS.OBJDSET,DISP=SHR //SYSUT1 DD UNIT=(SYSDA,SEP=(SYSLMOD,SYSLIN)),SPACE=(1024,(200,20)) //SYSPRINT DD SYSOUT=A //SYSLMOD DD DSN=IMS.SDFSRESL,DISP=SHR //SYSLIN DD *

INCLUDE ADFSLOAD(DFSCSI00) INCLUDE SYSPUNCH(DFSGMSG0) ENTRY DFSGMSG0 NAME DFSGMSG0(R)

++ SRC (DFSGMSG0) SYSLIB(SDFSSMPL) DISTLIB(ADFSSMPL) . DFSGMSG0 TITLE 'DFSGMSG0 -- GREETING MESSAGES USER EXIT' . . . . . .

Sample User Exit Technique

31

� The following sample can be used to assemble and bind DFSIDEF0//ASSEMBLE EXEC PGM=ASMA90,PARM='NOOBJ,DECK' //SYSLIB DD DSN=IMS.SDFSMAC,DISP=SHR //SYSPUNCH DD DISP=OLD,DSN=IMS.OBJDSET(DFSIDEF0) //SYSPRINT DD SYSOUT=* //SYSUT1 DD UNIT=SYSDA,DISP=(,DELETE),SPACE=(CYL,(15,15))//SYSIN DD * IDEF0 TITLE 'DFSIDEF0 - IMS INSTALLATION DEFAULTS BLOCK'DFSIDEF0 CSECT

DFSIDEF TYPE=BEGIN DFSIDEF TYPE=PARM,DBRC=YES

***** DFSIDEF TYPE=PARM,DBRC=NO ***** DFSIDEF TYPE=PARM,DBRC=FORCE

DFSIDEF TYPE=END END DFSIDEF0

//STEP1 EXEC PGM=IEWL, // PARM='SIZE=(880K,64K),NCAL,LET,REUS,XREF,LIST' //SYSPRINT DD SYSOUT=* //SYSPUNCH DD DSN=IMS.OBJDSET,DISP=SHR //SYSLMOD DD DSN=IMS.SDFSRESL,DISP=SHR //SYSUT1 DD UNIT=(SYSDA,SEP=(SYSLMOD,SYSPUNCH)),SPACE=(CYL,(10,1)//SYSLIN DD * INCLUDE SYSPUNCH(DFSIDEF0) NAME DFSIDEF0(R)

DFSIDEF0 Sample

32

�The IMS Application Menu (DFSAPPL) can be used to invoke the growing number of IMS ISPF applications–EX 'IMS.V10.SDFSEXEC(DFSAPPL)' 'HLQ(IMS.V10)'

IMS Application Menu

IMS Application Menu command ===> _______________________________________________

Select the desired application and press Enter.

1 Single Point of Control (SPOC)2 Manage resources3 Knowledge-Based Log Analysis (KBLA) 4 HALDB Partition Definition Utility (PDU) 5 Syntax Checker for IMS parameters (SC) 6 Installation Verification Program (IVP) 7 IVP Export Utility (IVPEX) 8 IPCS with IMS Dump Formatter (IPCS) 9 Abend Search and Notification (ASN)

To exit the application, press F3.

-------------------------------------------------------| (C) Copyright IBM Corp. 2003. All rights reserved. | -------------------------------------------------------

33

Thank You