VMXMSG0177W Rules facility initialization failed; wrong version of CP component.

Products

• VM:Secure for z/VM

Issue/Introduction

Tried upgrading to z/VM 7.2.0

Even though VM:Secure has "AUTOUSER AUTOLOG2", the autolog2 was not autologged.

The OPERATOR console log shows messages:

VMXMSG0177W Rules facility initialization failed , wrong version of CP component.                                                

VMXEIT0078W Rules facility initialization failed , IUCV connect error 2.    

 

Do you have any suggestions how to validate the HCPxxx modules ?                                                    

Environment

Release : 3.2

Component : CA VM:Secure for z/VM

Resolution

While the "offending" CP nucleus is IPL'd, you can issue the VMXCPNUC command:

z/VM Version 7 Release 2.0, service level 2101 (64-bit)
Generated at 08/12/21 18:13:20 EDT
IPL at 09/25/21 20:24:35 EDT
CP DATA: HCPRPD (VMXRPD) - EME207 (z/VM7.2) - VM:Secure 03.2 (04/01/21 08.59)
CP DATA: HCPRPG (VMXRPG) - EME207 (z/VM7.2) - VM:Secure 03.2 (08/12/20 15.54)
CP DATA: HCPRPI (VMXRPI) - EME207 (z/VM7.2) - VM:Secure 03.2 (04/01/21 08.54)
CP DATA: HCPRPW (VMXRPW) - EME207 (z/VM7.2) - VM:Secure 03.2 (08/12/20 16.00)
CP DATA: HCPRWA (VMXRWA) - Version: VMXE03.2
CP DATA: HCPRWA (VMXRWA) - MixedPW8: YES
CP DATA: HCPRWA (VMXRWA) - MixedPWP: YES
CP DATA: HCPRWA (VMXRWA) - Encrypt: SHA-256

The VMXCPNUC EXEC is located on the VMSECURE ADMIN disk (usually VMSECURE 176). The Utility does not require VM:Secure to be running, it reads the information it provides out of the CP nucleus that was loaded into storage at IPL. So this tells you for sure what is in the currently loaded CP nucleus.

 

If you can't re-IPL to run VMXCPNUC, the next best thing to do is check the CPLOAD MAP file that corresponds to the "offending" CPLOAD MODULE. XEDIT the CPLOAD MAP file, then issue ... ALL /LX032/ ... that should locate all of the VMSECURE TEXT file replacements:

 CPLOAD   MAP      K5  VP 133  Trunc=133 Size=95624 Line=21937 Col=1 Alt=0

21937 0:READ  HCPRPG   TXTLX032 E1 MNT2C4 04/27/21  14:26
21938                                  LCLX032 LCL LCLX032 * (RPG720) LEVEL: SO1
4443 -CA VM:SECURE- DATE: 27 AP
21939 --------------------  27  line(s) not displayed --------------------
21966 0:READ  HCPRPI   TXTLX032 E1 MNT2C4 04/27/21  14:26
21967                                  LCLX032 LCL LCLX032 * (RPI720) LEVEL: LU0
0778 -CA VM:SECURE- DATE: 27 AP
21968 --------------------  295  line(s) not displayed --------------------
22263 0:READ  HCPRWA   TXTLX032 E1 MNT2C4 04/27/21  14:27
22264                                  LCLX032 LCL LCLX032 * (RWA720) LEVEL: SO1
4443 -CA VM:SECURE- DATE: 27 AP
22265 --------------------  18126  line(s) not displayed --------------------
40391 0:READ  HCPRPD   TXTLX032 E1 MNT2C4 04/27/21  14:27
40392                                  LCLX032 LCL LCLX032 * (RPD720) LEVEL: LU0
0778 -CA VM:SECURE- DATE: 27 AP
40393 --------------------  39  line(s) not displayed --------------------
40432 0:READ  HCPRPW   TXTLX032 E1 MNT2C4 04/27/21  14:27
40433                                  LCLX032 LCL LCLX032 * (RPW720) LEVEL: SO1
4443 -CA VM:SECURE- DATE: 27 AP
40434 --------------------  55191  line(s) not displayed --------------------
95625 * * * End of File * * *

 

The problem with this method is you can't be 100% sure the CPLOAD MAP file matches what was IPL'd at the time, but usually this can help you identify the problem too.

Additional Information

Customer determined that the CMS portion of VMSECURE was not at the correct level.