Received Abend SIT002 with IBM's z/VM z17 compatibility CP APAR's VM66823 (7.3) or CP VM66824 (7.4)

Products

• VM:Secure for z/VM
• Mainframe VM Product Manager

Issue/Introduction

I received SIT002 from applying APAR VM66823 (7.3) / CP VM66824 (7.4) while IPLing my LPAR. 

Environment

VM:Secure 3.2

VM:Manager 1.2

z/VM 7.3 or z/VM 7.4

Cause

If you apply and IPL with CP APAR's VM66823 (7.3) or CP VM66824 (7.4) you could receive an SIT002 Abend. 

You will hit the SIT002 if the proper installation steps are not followed for Implementing the Directory Reader and System Information Diagnose Code associated with VM:Product Manager IBM z17 Hardware Compatibility (LU16422)

Likewise you will hit the SIT002 for not following the all correct steps for Installing Access Control Interface Exits in the VM Control Program associated with VM:Secure CP ACI ROUTINE UPDATES (LU16430)

Resolution

You need the following two fixes. VM:Product Manager IBM z17 Hardware Compatibility (LU16422) and VM:Secure CP ACI ROUTINE UPDATES (LU16430).

See the following steps:

For VM:Manager (LU16422) please follow our VM:Manager servicing your product guide followed by our Implementing the Directory Reader and System Information Diagnose Code Guide.

For VM:Secure (LU16430) please follow our VM:Secure servicing your product guide followed by our Installing Access Control Interface Exits in the VM Control Program guide.

If you do receive a SIT002 ABEND you can IPL and specify the NOAUTOLOG parameter at the Start prompt:

 

04:18:47 Start ((Warm|Force|COLD|CLEAN) (DRain) (DIsable)  (NODIRect)

      (NOAUTOlog)) or (SHUTDOWN)

04:18:52 HCPPCC2582I Storage reconfiguration by SYSTEM is complete. Permanent = 2G Reconfigurable = 0

04:19:08 FORCE NOAUTOLOG

 

Specifying the NOAUTOLOG option at IPL will prevent the AUTOLOG of various Broadcom products at IPL time. The products use VMNDLK and will cause the SIT002 ABEND.

Coming up with NOAUTOLOG will give you the chance to investigate the system to determine if the correct VMNDLKnn TEXT file is in place on the CP PARM disk. You can use the VMNDLKVI Command to verify that Version 5 of VMNDLK is what is being loaded at IPL time. The VMNDLKVI MODULE (Command) and the most current VMNDLKxx TEXT files are located on the VMANAGER 195 (code) minidisk:

 

VMNDLKVI

VMNDLK: Broadcom Directory Reader - Diagnose Code=100; Class=E; Version=5

Ready; T=0.01/0.01 14:47:13

If the VMNDLKVI Command indicates a VMNDLK version less than Version=5, then you must replace the VMNDLKnn TEXT file on your CP PARM disk with version that is installed after you deploy PTF LU16422. Then you can either re-IPL, or use CPXUNLOAD to remove the back-level VMNDLK, then CPXLOAD to reload the correct version after it has been placed on the CP PARM disk.

If VMNDLK is not the problem, then the problem must be that the VM:Secure service procedure for Installing Access Control Interface Exits in the VM Control Program was not completed after PTF LU16430 was deployed. You must re-ipl with your previous CPLOAD MODULE. This will allow you to complete regenerating the CPLOAD MODULE with the deployed TEXT files from PTF LU16430. After you complete the SERVICE CP BUILD and PUT2PROD steps, you should then be able to IPL with the new CPLOAD MODULE