Troubleshooting
Problem
After issuing the OMVS shutdown command, BPXI055I, BPXI064E and BPXI060I messages are issued and OMVS does not shutdown.
Symptom
During an IPL, when shutting down OMVS as recommended using the MVS "F OMVS,SHUTDOWN" command, the Automation Manager for z/OS (AM) is blocking the OMVS shutdown:
F OMVS,SHUTDOWN
BPXI055I OMVS SHUTDOWN REQUEST ACCEPTED
BPXI064E OMVS SHUTDOWN REQUEST DELAYED
BPXI060I T530HSAM RUNNING IN ADDRESS SPACE 003B IS BLOCKING SHUTDOWN
This causes a situation in that SA/zOS needs to be running so it can do the IPL, but OMVS can't shutdown because SA/zOS is running.
Resolving The Problem
This issue was resolved by invoking the supplied SA/zOS exit AOFEXC14, see comments below.
The SA/zOS AM does not provide the shutdown reply, the SA/zOS NetView for z/OS region does the actual reply.
The only implication here is if the system being terminated houses the PAM (Primary AM), and after the PAM is stopped the SA/zOS REXX INGRGDPS is invoked, at which point you can use the supplied SA/zOS exit AOFEXC14 to drive additional local processing as required.
INGRGDPS will determine if the AM being stopped is the PAM, and if so, it will arrange a 'takeover' to another active AM within the sysplex.
The AOFEXC14 exit is called by the SA GDPS termination routine (INGRGDPS) after stopping the PAM or selecting a SAM to become the PAM.
Refer to the sample exit for details of the return codes.
Was this topic helpful?
Document Information
Modified date:
08 August 2018
UID
swg21396508