Migrating an ADCD z/OS release: datasets

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.