Shadow MUF doesn't take over until primary MUF is cancelled

Document ID : KB000013560
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

I issued an EOJ command to the currently primary MUF but the shadow MUF doesn't appear to take over. I had to cancel the primary region and then shadow finally took over. 

Question:

Why do I have to cancel the primary in order to shadow to take over?

 

Answer:

The primary MUF correctly received the EOJ command but there were some active jobs that delayed the EOJ process:

DB01311I - COMM EOJ (USING MVS STOP 'P')
DB01335I - CONSOLE SCHEDULED - COMM EOJ (USING MVS STOP 'P')
DB00247I - EOJ REQUESTED, NO NEW CONNECTIONS, EOJOFF AVAILABLE
DB00244I   EOJ DELAYED, ACTIVE TASKS, JOB1

Primary MUF will complete the EOJ process when JOB1 ends or disconnects from MUF. 

If JOB1 is a CICS region, then issuing a DBEC DISConnect releases the Datacom tasks in use and MUF will shut down cleanly. 

If it's a batch job (or a TSO user), you can wait till it completes or cancel it. 

If it's a Datacom Server region, it must be shut down.

If it's a CA Solution, you should close or suspend it, to free the Datacom threads.