Out of the box, RMSMASTR behaves very badly on a signal shutdown of your VM system.
We have to use this to mount tapes in the VTS. RMSMASTR has files in VMSYSU: and VMSYS:, which both use signal shutdown by default. RMSMASTR hangs up the shutdown of VMSYS: until your system default shutdown time is up. That could be very long time. Or not, but not getting all the way down has required us to need FORCE starts on some systems on occasions, so a shorter time isn't even helpful. So we wrote our own SHUTTRAP thing to issue a DMSMSRM STOP command. This doesn't reliably work either. It's very timing dependent since this service machine gets the signal at the same time as VMSERVR and VMSERVS and if they beat it, the DFSMSRM STOP says not authorized (the auth file is in VMSYSU:) I opened a PMR once upon a time and it was rejected. We're trying to get things automated enough so that operations does nothing on the VM side and GDPS which signals the processor controller to shutdown the LPAR is sufficient. Does anyone else think this should be considered a defect? We'll probably work around it by one of these things 1. Use CA VM:Operator to FORCE RMSMASTR upon message "HCPSHU6018I The processor controller has sent a shutdown signal with a timeout interval of 300 seconds" 2. Use FORCE if dfsmsrm stop fails with "DGTUDR2016E User not authorized to issue this command" 3. Put NOSHUTDOWNSIGNAL in the parms file for VMSERVS and VMSERVU. Not nice to them, but what would we lose? Not much I think. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
