IBM: z/VM UGCRC01 utility

UPGCRC01 utility setup and usage.

Updated: 23 July 2025

To be effective, this utility must be acquired and in place before the INSTUPGR STAGE2 (COMMIT command is first used. In addition, modifications to the upgrade process $STAGE2$ $TABLE$ file are required so this utility is invoked accordingly, at specific points, when the INSTUPGR STAGE2 (COMMIT command is run. A second utility — MDSTG2TB — is provided here as well, to effect the necessary $STAGE2$ $TABLE$ file modifications.

To obtain the UPGCRC01 utility:

Download a binary copy of the UPGCRC01 BIN sample file (Last update: 22 Jul 2025)
Log on to the MIGMAINT user ID for the z/VM release in use.
Place a copy of the UPGCRC01 BIN file on the MIGMAINT 191 disk through appropriate means (for example, FTP), such that a FIXed-format, LRECL 1024 file is created.
Confirm the 191 disk-resident UPGCRC01 BIN file has the correct attributes:
```
listfile upgcrc01 bin a (isodate
```
The listed file should be reported as:
```
FILENAME FILETYPE FM FORMAT LRECL       RECS     BLOCKS     DATE     TIME
UPGCRC01 BIN      fm F       1024         nn         nn yyyy-mm-dd hh:mm:ss
```
If the BIN file is a FIXed-format, LRECL 80 file, reformat the file accordingly using this CMS PIPELINE command:
```
pipe < upgcrc01 bin a | fblock 1024 00 | > upgcrc01 bin a f 1024
```
Again, confirm the 191 disk-resident UPGCRC01 BIN file has the correct attributes, using the previously used LISTFILE command.
After the subject file has the correct format, copy this file to create a UPGCRC01 EXEC file:
```
  copyfile upgcrc01 bin a = exec = (unpack olddate replace
```

To obtain the MDSTG2TB utility:

Download a binary copy of the MDSTG2TB BIN sample file (Last update: 22 Jul 2025)
Log on to the MIGMAINT user ID for the z/VM release in use.
Place a copy of the MDSTG2TB BIN file on the MIGMAINT 191 disk through appropriate means (for example, FTP), such that a FIXed-format, LRECL 1024 file is created.
Confirm the 191 disk-resident MDSTG2TB BIN file has the correct attributes:
```
listfile mdstg2tb bin a (isodate
```
The listed file should be reported as:
```
FILENAME FILETYPE FM FORMAT LRECL       RECS     BLOCKS     DATE     TIME
MDSTG2TB BIN      fm F       1024         nn         nn yyyy-mm-dd hh:mm:ss
```
If the BIN file is a FIXed-format, LRECL 80 file, reformat the file accordingly using this CMS PIPELINE command:
```
pipe < mdstg2tb bin a | fblock 1024 00 | > mdstg2tb bin a f 1024
```
Again, confirm the 191 disk-resident MDSTG2TB BIN file has the correct attributes, using the previously used LISTFILE command.
After the subject file has the correct format, copy this file to create a MDSTG2TB EXEC file:
```
  copyfile mdstg2tb bin a = exec = (unpack olddate replace
```

To modify the $STAGE2$ $TABLE$ file for UPGCRC01 use, invoke the MDSTG2TB exec as described here.

Note:
Upon first use, the MDSTG2TB utility will create a backup copy of this table prior to attempting the intended modifications. If additional invocations are attempted or necessary, the intitial (or, successive) backup file created from a prior invocation will need to be renamed before a new MDSTG2TB invocation is attempted.

Confirm you are logged on the MIGMAINT user ID.
Issue command: access 2cf0 e
Issue command: mdstg2tb mod-table

Important:

If the MDSTG2TB utility does not complete with a zero (0) return code, contact the IBM Support group for assistance with resolving any problems. If MDSTG2TB utility errors are encountered, do not continue with use of the UPGCRC01 utility until all $STAGE2$ $TABLE$ file updates have been implemented, and if necessary, confirmed.

With all necessary $STAGE2$ $TABLE$ file modifications in place, you now should be ready for an initial run of the command:


  instupgr stage2 (commit

Note:

As the INSTUPGR STAGE2 (COMMIT command is processed, and the 190 disk of the current system is updated, it is a normal occurrence to encounter these messages:

  IUGUPG8529I The 190 disk on the current system has been upgraded.
  IUGUPG8529I You must IPL the 190 disk to access the new files.
  IUGUPG8529I To complete commit processing:
  IUGUPG8529I   IPL 190 PARM AUTOCR
  IUGUPG8529I   ACCESS 24CC C
  IUGUPG8529I and then re-issue:
  IUGUPG8529I   INSTUPGR STAGE2 (COMMIT

With the preceding $STAGE2$ $TABLE$ file modifications in place, one can also expect this message to be produced:

  DMSMOD104S Error 3 reading file READCARD MODULE from disk or directory

This error message can be dismissed; it is an expected result that cannot be mitigated with UPGCRC01 circumventive command processing.

Important:

The UPGCRC01 utility also should be invoked directly — during the upgrade completion process — to correct any VMSES/E table content issues that are possible when the MIGR51D utility is used, as outlined in:

Chapter 21. Finish your upgrade installation
Step 5. Migrate Licensed Product Inventory Files

This command: UPGCRC01 VMSES-SYSFILEMOD DELSUPCOPY
should be issued after Step 8 and before Step 9, as documented in this section:

8. Release the software inventory disk for your current system (attached as FFF and accessed as file mode Z. release z ( detach

upgcrc01 vmses-sysfilemod delsupcopy

9. MIGR51D updated the 7.4 VMSES/E system software inventory files on your new 51D minidisk...