Migrating an ADCD z/OS release to the next release: Parmlib members

Start here:Migrating an ADCD z/OS release to the next release.

The ADCD supplied parmlib members may change from release to release, for example the volser of disks will change from D5SYS1 to A3SYS1.

Some of the parmlib members you create, in USER.*.PARMLIB, may not be compatible with the new version, for example you explicitly refer to Z25D data sets, and the new data sets are Z31A data sets.

• You need to compare the new ADCD supplied parmlib, with your current ADCD parmlib, and check there are no surprise.
• You need to review your current user parmlib. You should be able to parameterise your library, for example using &SYSVER. instead of Z31A or Z25D. You can also identity which members you actually use, and only copy those to the new system.

How to see the new ADCD libraries on the old system.

I used ISPF 3.4 with prefix ADCD on volser A3SYS1, then used the local command C to catalog the data sets of interest (including CLIST, PARMLIB, and PROCLIB) . Once cataloged you can use ISPF 3.4 and specify ADCD.*.PARMLIB to list them both

How to find what parmlib members you use

In your old system, look at the joblog. Start from the start of IPL message IEE042I SYSTEM LOG DATA SET INITIALIZED.

After this, you get messages like

IEE252I MEMBER IEASYM00 FOUND IN USER.Z25D.PARMLIB

On my old system, I used SDSF S.;STATUS for JOBNAME SYSLOG. You can use the SE prefix command to edit the syslog file. I used X ALL;F IEE252I ALL;DEL ALL X to show all of the parmlib members used.

I made a backup of the parmlib, and deleted the parmlib members which were not used, so the user….parmlib contained only the definitions I needed.

I IPLed the system to make sure they worked.

I used the ISPF command SRCHFOR on the user parmlib , and user proclib, to search for Z25D (the release I was running), and changed all values to &SYSVER. When you IPL with a different version of z/OS the value of the &SYSRES for the new system, will be used.

As part of the clean up you may want to compare your members with the ADCD provided members for example edit a user….parmlib member and use the ISPF command COMPARE ‘adcd.z25D.parmlib(…)’ exclude to see the difference.

You can compare members in a PDS see How do I compare two PDS on z/OS.

You might want to see if your user… members can be deleted as they are the same as provided by ADCD.

You can look at the dates on the members, and you only need to check members with a “recent” date (since you got the system).

Parmlib changes

Some of of the my parmlib members changed include

• AUTOR… for automatic replies to z/OS messages
• BPXPRM to mount my OMVS file systems.
• CLOCK00 to change the time zone to E.00.00.00 ( GMT)
• CSFPRM for ICSF
• IEASYM00 to add symbols used by TCPIP
• IEASYM00 with my IPL changes
• IGDSMS00 to add PDSE… and PDSE1… definitions
• IKJTSO00 to add entries for ICSF panel processing. CSFDPKDS and CSFDPKDS
• IRRPRM to put the definitions of the RACF database into parmlib
• PFKTAB00 to change the default PF keys on the console
• PROGxx members for APF and LNKLIST
• SCHED

ReIPL the new system and check there are no unexpected messages. You can IPL your old system to fix the problems.

Copy your parmlib members

You can copy your parmlib members from USER.Z25D.PARMLIB to USER.Z31D.PARMLIB.

Update SYS1.IPLPARM

You need to update SYS1.IPLPARM (on A3SYS1) to add and entry for the load parm you use.

I copied LOAD00, and used

SYSPARM CP
IEASYM (00,CP)

This will use USER…PARMLIB(IEASYSCP), and will use the ADCD provided IEASYM00, and my IEASYMCP in USER…PARMLIB

IPL the new system

I used

ipl 0ac8 parm 0acfCP

to use the member LOADCP in SYS1.IPLPARM