Shutting down Datacom Shadow MUF only

Products

• Datacom
• DATACOM - AD
• COMMON SERVICES FOR Z/OS
• 90S SERVICES

Issue/Introduction

Datacom primary Multi-User Facility (called MUF) is running on one LPAR.  A Shadow MUF was inadvertently started on the wrong LPAR. The Shadow MUF needs to be shut down so it can be started on the correct LPAR.

 

Resolution

In order to set up the Shadow MUF for processing,  the XCF functionality needs to be enabled within the MUF.  This means jobs can run on any other LPAR in the Sysplex, (provided the necessary Common Services/CAS9 pieces are in place), and the job will communicate with the primary MUF.

Because this process is in place, the only way to shut down the Shadow MUF is to run the DBUTLTY command COMM OPTION=EOJ, or issue the console command /F mufname,EOJ on the LPAR where the Shadow MUF is running. When the job is run, it looks to see if there is a corresponding MUF on the local LPAR first, and it will shut down the Shadow on that LPAR. If the job runs on any other LPAR, the command will be passed to the Primary MUF, shutting down the operational MUF.

If the MUF is started on the "wrong" LPAR, the best way to guarantee this process works as desired is to manually issue the EOJ command from the console on the "wrong" LPAR.  Many sites use workload management policies that might move a batch DBUTLTY job to an unexpected LPAR. However, if the batch job can be controlled to run on a specific system, submitting the DBUTLTY will work fine.