After upgrading to z/VM 7.2 and configuring SMAPI-services in the same manner as for z/VM 7.1, it no longer starts.
When starting up VMSGUARD the below errors are shown.
Config looks okay and SMAPI workers have access to the VMANAGER 193 disk
Also verified the DMSSICNF COPY file on MAINT's 193 has the DM_exit set to VMXSIXDM.
ENV_INFO = No Directory Manager configured in DMSSISVR NAMES, rc: 4
* MSG FROM VSMGUARD: SMSTATUS issues a request to your directory
* MSG FROM VSMGUARD: manager. If you see VM READ at the
* MSG FROM VSMGUARD: right bottom of your screen, please
* MSG FROM VSMGUARD: type your password and hit enter to
* MSG FROM VSMGUARD: allow SMSTATUS to continue processing.
Execute rc:8 rx:3015
Error Data is:COMMAND_IN_ERR=DMSWSCHK EXEC,rc:20040
210 +++ myrs = C2D(myrs)
DMSREX475E Error 40 running DMSWSCHK EXEC, line 210: Incorrect call to routine
Routine DMSWSESM loaded at 07DFA420 size 00000BE0
R07DFA420 47F0F018 13C4D4E2 E6E2C5E2 D4F2F04B F6 *.00..DMSWSESM20.*
VM:Secure 3.2 running in z/VM 7.2 environment.
Lacking VM:Secure Rules for DIAGD4 and DIAG88.
You must add the following VM:Secure Rules for DIAGD4 and DIAG88;
The complete section for: