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

I have covered datasets, aliases and catalogs in One minute mvs: catalogs and datasets.

If your master catalog is a mess

If you have your personal data sets in the master catalog instead of a user catalog, see Here’s another nice mess I’ve gotten into!

You could start again on the new system and do it properly.

Note down which volumes your data sets are on. On the new system define a user catalog and alias, and use ISPF 3.4, to list the contents of the volume and use the C local command to catalog the data set.

I found the easiest way of doing VSAM datasets is a backup and restore

If you have a user catalog for your user data sets

You need to get a list of the user aliases in the master catalog on the old system, and the user catalogs the aliases refer to, before trying to import them into the new system. I could not find a way to list the master catalog from another system. See here for example JCL

To access your data sets in a user catalog you need to import the catalog into the master catalog on the new system, and define the aliases for your data to the catalog.

On your new system, you will not have immediate access to your data sets, so you either need

• to access a dataset, and specify the volser information,
• or you need to have a copy of the JCL to import a user catalog, and define alias, stored in a note pad area outside of z/OS. Edit a member such as USER.*.PROCLIB(TEMP) and paste the import catalog JCL. When that has worked, paste in the add alias to your datasets ( COLIN.*). Once you have done this, you can use ISPF 3.4 and use COLIN.* to locate your data sets.

Once you have your list of aliases and user catalogs, you can IPL the new system and import the user catalogs, and define the aliases.

Product data sets

There is usually an alias in the master catalog for a program product. The alias may have the product release as part of the name. If you have customised any of the product owned datasets, you may need to copy the data off.

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

What to you need to think about?

ADCD provided data sets you may have changed

This should only be USER.*.* data sets, but you may have updated ADCD data sets. You should copy any changes into the USER.*. data sets. On the new system, you can copy this to the newer (and empty) USER.*.* data sets.

Some of the data sets I updated are

• USER.Z24C.PARMLIB
• USER.Z24C.PROCLIB
• USER.Z24C.CLIST
• USER.Z24C.SYSEXEC
• USER.Z24C.TCPPARMS
• USER.Z24C.VTAMLST
• ADCD.Z24C.PARMLIB(JES*)
• ADCD.Z24C.TCPPARMS. I should have create a copy of the TCPIP procedure in USER.Z24C.PROCLIB, and changed ADCD.Z24C.TCPPARMS to USER.Z24C.TCPPARMS

You can use ISPF 3.4 to display the contents of a PDS, and use sort changed or tab to the Changed column and press enter. Check the date and userid.

If you haven’t changed the ADCD.* members, compare the old and new, and change your USER.* to incorporate any changes if necessary. You can use the ISPF editor command “compare” to show you the differences between members.

User data

I have a lot of data sets with a high level qualifier of COLIN. Fortunately I set up an IDCAMS alias so all COLIN.** data sets were cataloged in a user catalog. On the new system, I just have to import the catalog.

If you did not set up a user catalog for your personal data sets.

You could set up a user catalog on the old system, set up an alias such as COLIN1, then rename all COLIN.* to COLIN1. On the new system you import the user catalog, and define the alias COLIN1. Set up a new user catalog, and a new alias, then copy/rename the data set from COLIN1 to COLIN.

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

It is not very easy to copy VSAM files from one system to another.

Backup

You can backup files, including VSAM files using DFDSS, DUMP DATASET command

//IBMDFDSS JOB 1,MSGCLASS=H 
//  SET BACKUP=COLIN.BACKUP.CSF 
//SDE EXEC PGM=IEFBR14,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,DELETE), 
//         SPACE=(CYL,(1,1)) 

//S1  EXEC PGM=ADRDSSU,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,CATLG), 
//         SPACE=(CYL,(50,50),RLSE) 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * 
 DUMP  - 
    DATASET(INCLUDE(CSF.CSFCKDS.NEW,             - 
                    CSF.CSFPKDS.NEW,             - 
                    CSF.CSFTKDS.NEW            ) - 
            BY(DSCHA,EQ,1))  - 
    RESET - 
    OUTDDNAME(TARGET) - 
    COMPRESS 
/* 

• If you specify REGION=0M,PARM=’TYPRUN=SCAN’ it will check the syntax of the commands without executing them.
• You can use BY(DSCHA… to do incremental backups – so backup what has changed. It is the data-set-changed flag is on or off.

The DSCHA,EQ,1To perform incremental backups with DFSMSdss, you can filter with
BY(DSCHA,EQ,1) to dump only data sets that have changed since the last dump was taken. If you also code the RESET keyword, DFSMSdss changes the data-set-changed indicator (DSCHA) after successfully dumping the data set. For more information about the RESET keyword

The RESET says if the dump was successful, reset the data-set-changed flag to off.

The output was

ADR101I TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP '
ADR109I 2024.002 12:04:53 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED
ADR016I RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I 2024.002 12:04:53 EXECUTION BEGINS
ADR788I PROCESSING COMPLETED FOR CLUSTER CSF.CSFCKDS.NEW, 1 RECORD(S) PROCESSED, REASON 0
ADR788I PROCESSING COMPLETED FOR CLUSTER CSF.CSFPKDS.NEW, 6 RECORD(S) PROCESSED, REASON 0
ADR788I PROCESSING COMPLETED FOR CLUSTER CSF.CSFTKDS.NEW, 987 RECORD(S) PROCESSED, REASON 0
ADR801I 2024.002 12:04:53 DATA SET FILTERING IS COMPLETE. 3 OF 3 DATA SETS WERE SELECTED: 
  0 FAILED SERIALIZATION
  AND 0 FAILED FOR OTHER REASONS
ADR454I THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED
  CLUSTER NAME CSF.CSFCKDS.NEW
  CATALOG NAME CATALOG.Z24C.MASTER
  COMPONENT NAME CSF.CSFCKDS.NEW.DATA
  COMPONENT NAME CSF.CSFCKDS.NEW.INDEX
  CLUSTER NAME CSF.CSFPKDS.NEW
  CATALOG NAME CATALOG.Z24C.MASTER
  COMPONENT NAME CSF.CSFPKDS.NEW.DATA
  COMPONENT NAME CSF.CSFPKDS.NEW.INDEX
  CLUSTER NAME CSF.CSFTKDS.NEW
  CATALOG NAME   CATALOG.Z24C.MASTER                                          
  COMPONENT NAME CSF.CSFTKDS.NEW.DATA                                         
  COMPONENT NAME CSF.CSFTKDS.NEW.INDEX                                        
ADR006I 2024.002 12:04:53 EXECUTION ENDS                                             
ADR013I 2024.002 12:04:53 TASK COMPLETED WITH RETURN CODE 0000                       
ADR012I 2024.002 12:04:53 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0000  

When I reran the job I got

ADR383W DATA SET CSF.CSFCKDS.NEW NOT SELECTED, 01                               
ADR383W DATA SET CSF.CSFPKDS.NEW NOT SELECTED, 01                               
ADR383W DATA SET CSF.CSFTKDS.NEW NOT SELECTED, 01                               
ADR415W NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM ANY VOLUME           
ADR006I 2024.002 12:28:48 EXECUTION ENDS                                        
ADR013I 2024.002 12:28:48 TASK COMPLETED WITH RETURN CODE 0004                       

Where ADR383W reason code 1 is

The data set was not selected due to the following reason (reason_code):
01 The fully qualified data set name did not pass the INCLUDE, EXCLUDE, and/or BY filtering criteria.

because the VSAM file had not been changed since the previous backup.

To always backup remove the reset and BY() statement

DUMP  - 
   DATASET(INCLUDE(CSF.CSFCKDS.NEW,             - 
                   CSF.CSFPKDS.NEW,             - 
                   CSF.CSFTKDS.NEW            ) - 
          )    - 
   OUTDDNAME(TARGET) - 
   COMPRESS

Restore

The RESTORE command has many parameters

//IBMDFDSS JOB 1,MSGCLASS=H 
//S1  EXEC PGM=ADRDSSU,REGION=0M,PARM='TYPRUN=NORUN' 
//TARGET   DD DSN=COLIN.BACKUP.CSF,DISP=SHR 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * 
 RESTORE - 
    RENAME(COLINN) - 
    DATASET(INCLUDE(**)      )                   - 
    INDDNAME(TARGET) 
/*                                                                

• If you specify TYPRUN=NORUN, it will list what datasets would be restored – to allow you to check. Remove TYPRUN=NORUN to execute and restore the data.
• The RENAME says replace the HLQ with COLINN. This way you do not overwrite any existing data sets.

The output of the job was

ADR489I (001)-TDLOG(02), CLUSTER COLINN.CSFCKDS.NEW WAS SELECTED                   
                          CATALOG        CATALOG.Z24C.MASTER                       
                          COMPONENT      COLINN.CSFCKDS.NEW.DATA                   
                          COMPONENT      COLINN.CSFCKDS.NEW.INDEX                  
ADR489I (001)-TDLOG(02), CLUSTER COLINN.CSFPKDS.NEW WAS SELECTED                   
                          CATALOG        CATALOG.Z24C.MASTER                       
                          COMPONENT      COLINN.CSFPKDS.NEW.DATA                   
                          COMPONENT      COLINN.CSFPKDS.NEW.INDEX                  
ADR489I (001)-TDLOG(02), CLUSTER COLINN.CSFTKDS.NEW WAS SELECTED                   
                          CATALOG        CATALOG.Z24C.MASTER                       
                          COMPONENT      COLINN.CSFTKDS.NEW.DATA                   
                          COMPONENT      COLINN.CSFTKDS.NEW.INDEX                  
ADR040I (001)-TDLOG(01), PROCESSING BYPASSED DUE TO NORUN OPTION                   

Without TYPRUN=NORUN, the output was like

ADR711I DATA SET CSF.CSFPKDS.NEW HAS BEEN ALLOCATED WITH NEWNAME COLINN.CSFPKDS.NEW 
USING STORCLAS SCBASE, NO DATACLAS, AND NO MGMTCLAS
ADR788I PROCESSING COMPLETED FOR CLUSTER CSF.CSFPKDS.NEW, 6 RECORD(S) PROCESSED

When I reran the restore job I got

ADR380E DATA SET CSF.CSFCKDS.NEW NOT PROCESSED, 37

where code 37 means

The new name specified with RENAME or RENAMEUNCONDITIONAL already exists on the volume and the REPLACEUNCONDITIONAL keyword was not specified. The REPLACE keyword cannot be used to replace a data set that is being renamed.

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

Depending on your setup, migrating ICSF to a newer level can be trivial.

With my original ADCD system, it had ICSF set up to use data sets like CSF.CSFCKDS. When I moved to a new level of ADCD, there were the same data set names.

I backed up the datasets, and restored them on the new system with a new name

//IBMDFDSS JOB 1,MSGCLASS=H 
//  SET BACKUP=COLIN.CSF.Z24C.BACKUP 
//SDE EXEC PGM=IEFBR14,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,DELETE), 
//         SPACE=(CYL,(1,1)) 
//S1  EXEC PGM=ADRDSSU,REGION=0M 
//TARGET   DD DSN=&BACKUP,DISP=(MOD,CATLG), 
//         SPACE=(CYL,(50,50),RLSE) 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * 
 DUMP  - 
    DATASET(INCLUDE(CSF.SCSFCKDS,        - 
                    CSF.SCSFPKDS,    - 
                    CSF.SCSFTKDS  )- 
           )    - 
    OUTDDNAME(TARGET) - 
    COMPRESS 
/* 

I restored them on the same system using

//IBMDFDSS JOB 1,MSGCLASS=H                           
//S1  EXEC PGM=ADRDSSU,REGION=0M PARM='TYPRUN=NORUN'  
//TARGET   DD DISP=SHR,DSN=COLIN.CSF.Z24C.BACKUP      
//SYSPRINT DD SYSOUT=*                                
//SYSIN DD *                                          
 RESTORE -                                            
    DATASET(INCLUDE(**)      )                   -    
    RENAME(COLIN ) -                                  
    INDDNAME(TARGET)                                  
/*                                                    

I now had data sets like COLIN.SCSFPKDS.

Remember to change your backup processes to backup the new data sets.

The default CSF procedure is

//CSF PROC 
//CSF EXEC PGM=CSFINIT,REGION=0M,TIME=1440,MEMLIMIT=NOLIMIT 
//CSFPARM DD DSN=ADCD.&SYSVER..PARMLIB(CSFPRM00),DISP=SHR 

Which does not easily allow you to override it. In USER…PROCLIB(CSF) I created

//CSF  PROC PRM=CP 
//CSF  EXEC PGM=CSFINIT,PARM=&PRM,REGION=0M,TIME=1440,MEMLIMIT=NOLIMIT 

and in USER….PARMLIB(CSFPRMCP) created

CKDSN(COLIN.SCSFCKDS) 
PKDSN(COLIN.SCSFPKDS) 
TKDSN(COLIN.SCSFTKDS) 
DOMAIN(0) 
COMPAT(NO) 
SSM(NO) 
CHECKAUTH(NO) 
CTRACE(CTICSF00) 
USERPARM(USERPARM) 
REASONCODES(ICSF) f

Compared to the ADCD provided member, my member has

• Different dataset names
• A TKDSN dataset
• DOMAIN(0)

Creating a TKDS

As part of my use of ICSF tokens for certificates I had to create a TKDS.

I used Steps to create the TKDS, using data set name COLIN.SCSFTKDS.

Don’t forget to add it to your list of data sets to backup regularly.

Starting ICSF

With the ADCD system you start ICSF using the operator command S CSF or S CSF,PRM=xx .

From ISPF go to option 6 TSO and use the @ICSF command

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

There are several parts to migrating OMVS.

• Making your user file systems available to the new level of z/OS
• Making data from your old system file systems available to the new level of z/OS. Files I updated and copied include
  • /etc csssmtp.env this is used in the mail protocol procedure CSSMTP
  • /etc/hosts this is used in TCPV4 name query lookup
  • /etc/pkiserv/… for the PKI Server for managing digital certificates
  • /etc/resolv.conf this is used in TCPIP DNS
  • /etc/gskssl/… for system ssl.
  • /etc/syslog.conf for managing the SYSLOGD daemon, and where (TCPIP) Unix tasks write their output in the file system
  • /etc/zexpl/… for use with RSEAPI procedure, and z/OS Explorer
• Copying any customisation from the old system to the new system. This should be in the /etc directory, or in the JCL procedures.
• Checking your overall OMVS configuration is consistent

The ZFS for /etc is ZFS.S0W1.ETC. This is the same on the Z31A, and the Z25D systems, so cannot you use both copies on the same system. This means you need to use backup and restore; or copy the files to a ZFS which can be used on both systems.

Making your user file systems available to the new level of z/OS

This should just be a matter of making sure your BPXPRMxx with your mount statements is used in the new system, and IPLing with the correct IEASYS member.

HFS is not supported on z/OS 3.1 so you will need to migrate these to ZFS before you try to migrate; and remove and HFS definition statements.

Making your old system file systems available to the new level of z/OS.

On the old system I found all the files I had changed in /etc, and backed them up to a PAX file. I could have copied the directories to a user ZFS file system.

The potential directories of interest are

• /etc this has configuration files for system tasks such as syslogd
• /var this contains log files etc as used by system tasks. You usually do not want to copy the files across.
• /opt program product information which you usually do not want to copy across

How do you find changed files?

See How do I diff on Z/OS with Unix files and directories for a full description.

You can use the command ls -ltr . to list files in the current directory, with the latest changes at the bottom of the list. Or you can use the find command

find . -mtime -100 -a -type f

which lists the files within the last 100 days (-mtime -100); -mtime 100 is exactly 100 days ago; -mtime +100 is over 100 days ago. This way is not very helpful. You can say find files newer than ‘this’ file.

You can create an empty file and set the date on it using

touch -t 2401181400 ~/Jan182024.file    

Where the -t value is yymmddhhmm

You can list files changed more recently than this file file using

find . -newer ~/Jan182024.file  -a -type f

This gives you a list of files

You can use a command to do more processing. The following also lists information about the files.

find . -newer ~/Jan182024.file   -a -type f -exec ls -al {} \;   

How to backup files

You can pipe the information from the find command into other commands such as pax. This takes the stream of filenames, and copies the file contents into a PAX fiile.

find . -newer ~/Jan182024.file  -a -type f | pax -W "seqparms='space=(cyl,(30,30))'" -wzvf "//'COLIN.PAX.TEST2'" -x os390

On the other system you can read the pax file and load the files.

How to see what’s in a pax file

You can see what is in the pax file use

pax   -vf "//'COLIN.PAX.TEST2'" 

Note of warning. You should be careful backing up and restoring when using absolute path names. See Oh p*x, I’ve lost my changes.

How to restore the data

pax -rfk  "//'COLIN.PAX.TEST2'"  

Where the -k option means do not overwrite.

Checking your overall OMVS configuration is consistent

You can use the D OMVS,PFS command to display the in use physical file systems. Issue this command on both old and new systems, and compare the output

z/OS 2.5D D OMVS,PFS output

The -FS GFSCINIT data is for an HFS file system. You need to remove any FILESYSTYPE TYPE(HFS) ENTRYPOINT(GFSCINIT) … entries from systems before using z/OS 3.1

OMVS     0010 ACTIVE             OMVS=(TC,00,01,BP,IZ,RZ,BB,ZW,US)                               
PFS CONFIGURATION INFORMATION                                                                    
 PFS TYPE   ENTRY      ASNAME    DESC      ST    START/EXIT TIME                                 
  -FS       GFSCINIT   N/A                 U     2024/08/29 12.56.04                             
  INET      EZBPFINI   N/A       SOCKETS   I                                                     
  -FS       GFSCINIT   N/A                 U     2024/08/29 12.56.03                             
  ZFS       IOEFSCM    N/A       LOCAL     A     2024/08/29 12.55.59                             
  AUTOMNT   BPXTAMD    N/A       LOCAL     A     2024/08/29 12.55.59                             
  UDS       BPXTUINT   N/A       SOCKETS   A     2024/08/29 12.55.59                             
  CINET     BPXTCINT   N/A       SOCKETS   A     2024/08/29 12.55.59                             
                                                                                                 
 PFS TYPE  DOMAIN        MAXSOCK  OPNSOCK  HIGHUSED                                              
  UDS      AF_UNIX         10000        2         2                                              
  CINET    AF_INET6        50000        4         4                                              
           AF_INET         64000        8         9                                              
                                                                                                 
 SUBTYPES OF COMMON INET                                                                         
 PFS NAME   ENTRY      START/EXIT TIME       STATUS  FLAGS                                       
  TCPIP      EZBPFINI   2024/08/29 12.56.24   ACT     SC                                         
  TCPIP2     EZBPFINI                         INACT                                              
  TCPIP3     EZBPFINI                         INACT                                              
  TCPIP4     EZBPFINI                         INACT                                              

z/OS 3.1A D OMVS,PFS output

Note the missing entry for -FS GFSCINIT.

OMVS     0010 ACTIVE             OMVS=(TC,00,01,BP,IZ,RZ,BB,ZW,US)      
PFS CONFIGURATION INFORMATION                                           
 PFS TYPE   ENTRY      ASNAME    DESC      ST    START/EXIT TIME        
  INET      EZBPFINI   N/A       SOCKETS   I                            
  ZFS       IOEFSCM    ZFS       LOCAL     A     2024/08/29 13.00.24    
  AUTOMNT   BPXTAMD    N/A       LOCAL     A     2024/08/29 13.00.24    
  UDS       BPXTUINT   N/A       SOCKETS   A     2024/08/29 13.00.24    
  CINET     BPXTCINT   N/A       SOCKETS   A     2024/08/29 13.00.24    
                                                                        
 PFS TYPE  DOMAIN        MAXSOCK  OPNSOCK  HIGHUSED                     
  UDS      AF_UNIX         10000        2         3                     
  CINET    AF_INET6        50000        4         4                     
           AF_INET         64000        8         8                     
                                                                        
 SUBTYPES OF COMMON INET                                                
 PFS NAME   ENTRY      START/EXIT TIME       STATUS  FLAGS              
  TCPIP      EZBPFINI   2024/08/29 13.01.05   ACT     SC                
  TCPIP2     EZBPFINI                         INACT                     
  TCPIP3     EZBPFINI                         INACT                     
  TCPIP4     EZBPFINI                         INACT                     

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

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

The ADCD supplied proclib members may change from release to release, for example the volser of disks will change from D5SYS1 to A3SYS1, and you may have a copy in user…proclib which overrides the ADCD supplied members.

What is different between your USER.Z25D.PROCLIB and ADCD.Z25D.PROCLIB?

It is good practice to see what you have changed in the USER.*.PROCLIB.

Use ISPF 3.4 to look at ADCD.Z25D.PROCLIB, display the members, and sort on changed. If you were careful you have not changed anything in this library, but made your changes in USER.Z25D.PROCLIB.

Compare USER.Z25D.PROCLIB and ADCD.Z25D.PROCLIB

You can use ISPF 3.13, the SuperCE utility to compare the members.

I specified

• New DS Name . . . ‘USER.Z25D.PROCLIB’
• Old DS Name . . . ‘ADCD.Z25D.PROCLIB’
• Compare Type 2
• Listing Type 2

There are several sections to the output

• Changes between members found in both libraries
• CHNG MEMBERS-COMPARED and which members were common, and how many lines different there were
• NON-PAIRED NEW FILE MEMBERS (files only in USER.Z25D.PROCLIB) | NON-PAIRED OLD FILE MEMBERS (files only in ADCD.Z25D.PROCLIB)

For example

...
NEW: USER.Z25D.PROCLIB        OLD: ADCD.Z25D.PROCLIB                                         
                                                    
CHNG MEMBERS-COMPARED NEW-PROC OLD-PROC  MATCHED NEW-INS OLD-DEL 
                                                                                             
**   CSF                     2        5        0       2       5 
**   FTPD                   16       14       12       4       2 
**   HZSPROC                42       42       41       1       1 
**   TCPIP                  14       71       10       4      61 
**   VTAM00                  7        6        6       1       0 
                                                                                             
    5   TOTAL MEMBER(S) PROCESSED AS A PDS 
    5   TOTAL MEMBER(S) PROCESSED HAD CHANGES 
    0   TOTAL MEMBER(S) PROCESSED HAD NO CHANGES 
   11   TOTAL NEW FILE MEMBER(S) NOT PAIRED 
  281   TOTAL OLD FILE MEMBER(S) NOT PAIRED 
NON-PAIRED NEW FILE MEMBERS         |   NON-PAIRED OLD FILE MEMBERS
    AZF#IN00                        |       ASMAC 
    AZF#IN01                        |       ASMACG 
    BACKUP                          |       ASMACL  
    ...                             |       ...    

Once you understand the changes between the USER.Z25D.PROCLIB and ADCD.Z25D.PROCLIB, you can do a similar exercise between USER.Z25D.PROCLIB and ADCD.Z31A.PROCLIB

The changes I had made to USER.*.PROCLIB include

Specifying a PRM to ICSF in member CSF

//CSF  PROC PRM=CP                                                       
//CSF  EXEC PGM=CSFINIT,PARM=&PRM,REGION=0M,TIME=1440,MEMLIMIT=NOLIMIT   

This uses the CSFPRMCP in the Parmlib concatentation.

This had

CKDSN(COLIN.SCSFCKDS) 
PKDSN(COLIN.SCSFPKDS) 
TKDSN(COLIN.SCSFTKDS) 
DOMAIN(0) 
COMPAT(NO) 
SSM(NO) 
CHECKAUTH(NO) 
CTRACE(CTICSF00) 
USERPARM(USERPARM) 
REASONCODES(ICSF) 

Health Checker HZSPROC

This had //HZSPROC PROC HZSPRM=‘(AD,US)’ instead of //HZSPROC PROC HZSPRM=’AD‘

Where USER.Z25D.PARMLIB(HZSPRMUS) has

ADDREPLACE POLICY STATEMENT(COLINS) 
UPDATE   CHECK(IBMRACF,RACF_SYSPLEX_COMMUNICATION) 
         DATE(20240120) 
         INACTIVE 
         REASON('COLIN - Test/Development env') 
                                                                      
ADDREPLACE POLICY 
UPDATE   CHECK(IBMRACF,RACF_PROTECTALL_FAIL) 
         DATE(20240120) 
         INACTIVE 
         REASON('COLIN2- do not want in one person system') 
                                                                      
ADDREPLACE POLICY 
UPDATE   CHECK(IBMXCF,XCF_TCLASS_CLASSLEN) 
         DATE(20240120) 
         INACTIVE 
         REASON('COLIN - NON sysplex no xcf message buffers  ') 

to prevent unnecessary health check messages from being produced.

TCPIP

• Remove the TSO step with RACFCRT CRTHOST_.
• Remove the comments
• Change the PROFILE
• Change the SYSTCPD statement.

FTPD

VTAM00

This procedure issues commands as part of the z/OS start up. It executes commands in parmlib member VTAM00

Add DSN=USER.&SYSVER..PARMLIB(&M),DISP=SHR to the parmlib definition

My USER.Z31A.PARMLIB(VTAM00) has

* Make the operator console nice
K A,NONE,L=L700 
* FOR HEALTH CHECK MESSAGE 
$T CKPTDEF,OPVERIFY=NO