IBM: z/VM 7.4 Upgrade Problem Manual Fix Information

United States

Site map

Search

z/VM
News
About z/VM
Events calendar
Products and features
Downloads
Technical resources
Library
How to buy
Install
Service
Support
Education
z/VM Change logs
Site map
Site search
Notify me
Contact z/VM

Overview
Upgrade
SDO
Resources
News
Tips

z/VM 7.4 Upgrade problem manual fix information

Updated: 24 July 2025

When upgrading to z/VM 7.4, multiple errors can occur, some of which are dependent upon the configuration of the system being upgraded. Errors that might be produced, when the UPGCRC01 utility has not been used in conjunction with the INSTUPGR STAGE2 (COMMIT command, are cited here. Manual corrective actions for mitigating a listed error message or condition also are provided.

Message DMSABE141TE produced after DDR processing of the MAINT 190 disk:

  ...
  Now processing line nnn of mmm
  ...
  z/VM DASD DUMP/RESTORE PROGRAM
  COPYING   MNT190
  COPYING DATA  11/25/24 AT 11.14.23  GMT FROM MNT190 TO MNT190
  INPUT CYLINDER EXTENTS      OUTPUT CYLINDER EXTENTS
        START       STOP         START        STOP
            0        213             0         213
  END OF COPY
  END OF JOB
  DMSABE141T Protection exception occurred at xxxxxxxx in routine EXECDROP

Corrective Action:

While still logged on the MIGMAINT user ID, resume the upgrade process using these commands:
```
 ipl 190 parm autocr
 access 24cc c
 instupgr stage2 (commit
```

Message VMFBLD1836E produced when command VMFINS BUILD PPF SERVP2P VMSES (SERVICED LINK is invoked by INSTUPGR:

Console messages:

  ...
  IUG2EX8508I Record: SESCMD FINSBLD VMFINS BUILD PPF SERVP2P VMSES (SERVICED LINK
  IUG2EX8342E Command 'VMFINS BUILD PPF SERVP2P VMSES (SERVICED LINK' failed with RC=8
  IUGUPG8342E Command 'INSTS2EX 740' failed with RC=100
  IUGUPG8376E INSTUPGR STAGE2 ( COMMIT ended in error.
  ...

VMFINS command ($VMFINS) $MSGLOG messages:

  ...
  VMFINB2603I Building product :PPF SERVP2P VMSES :PRODID 7VMSES40%VMSES
  ...
  VMFBLD2760I VMFBLD processing started
  VMFBLD1836E This program requires BUILD8 5E6 to be accessed as R/W because it is a target of build lists
  ...

Corrective Action:

Logoff the MIGMAINT user ID, then again logon this same user ID.

Resume the upgrade process:

 access 24cc c
 instupgr stage2 (commit

Messages DMSPCL386E and VMFSRV1965E (among others) produced when command SERVICE CP BLDNUC is invoked by INSTUPGR, or, when a SERVICE command is used to install new service after having completed a z/VM 7.4 system upgrade:
Console messages:
```
  ...
  IUG2EX8508I Record: SESCMD BLDNUC SERVICE CP BLDNUC
  IUG2EX8342E Command 'SERVICE CP BLDNUC' failed with RC=100
  ...
```
SERVICE command ($VMFSRV) $MSGLOG messages:
```
  ...
  ST:VMFSRV2760I SERVICE processing completed successfully for CP BUILD
  ...
  CK:VMFSRV1233I The following products have been serviced.
  CK:VMFSRV1233I CP
  ST:VMFUTL2767I Reading VMFINS DEFAULTS B for additional options
  ST:VMFBMP2760I VMFBTMAP processing started
  ST:VMFBMP2760I VMFBTMAP processing started for
  SV:DMSPCL386E Missing operand(s)
  SV:VMFSET2760E VMFSETUP processing completed unsuccessfully (RC=24)
  ...
```
Corrective Action:
- Aquire the UPGCRC01 utility as described here:
  1. Download a binary copy of the UPGCRC01 BIN sample file (Last update: 22 Jul 2025)
  2. Log on to the MIGMAINT user ID for the z/VM release in use.
  3. 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.
  4. 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.
  5. 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
```
- After logon of the MAINT740 user ID, place a copy of this utility EXEC on the 191 disk.
- Invoke the UPGRCRC01 exec as follows:
  upgcrc01 vmses-sysfilemod delsupcopy
- If the system upgrade still is in process, logoff the MAINT740 user ID, then resume the upgrade process after having logged on the MIGMAINT user ID. If this problem instead was encountered when attempting to apply new service to an upgraded z/VM 7.4 system, restart the affected SERVICE command accordingly.

To avoid the aforementioned errors with future system upgrades, or upgrades of additional SSI cluster systems, it is recommended that the UPGCRC01 utility be used for such endeavors. More information about this utility is available here: UPGCRC01 Utility setup and usage

Footer links

Contact
Privacy
Terms of use
Accessibility