CACM632E - MCPU=NO,BUT MCPU WORKLOAD DETECTED starting Scheduler

Products

• Scheduler Job Management

Issue/Introduction

What caused this message and how to correct it:

CACM632 MCPU=NO, BUT MCPU WORKLOAD DETECTED, SCHEDULER IS SHUTTING DOWN

 

 

Cause

CACM632 MCPU=NO, BUT MCPU WORKLOAD DETECTED, SCHEDULER IS SHUTTING DOWN

Reason: The CAS9 CAIJGEN options indicate that Scheduler is in a single system environment, but the active workload has entries for multiple SYSIDs. Scheduler shuts down.

 

Resolution

When Scheduler is started, it reads the active workload for schedules that belong to the local Scheduler system SYSID.

When the SYSID value found on the CPU records in the active workload is not the same as the current local SYSID, message CACM632 is issued.  Incorrect SYSID on the CPU records occurs when the Scheduler data base is copied from one Scheduler system to another Scheduler running on a different LPAR.   

To resolve this problem, use one of the following resolutions:

1.  Change the SYSID on the CPU records:  

   // EXEC CAJUTIL0 
   //SYSIN DD * 
   ALTER SYSID FROM=xxxx,TO=yyyy 
   //* where xxxx is the old SYSID and yyyy is the new SYSID. 

2.  Empty the active workload if you are willing to clear all outstanding schedules/jobs (active and backlogged) and restart Scheduler.  An AUTOSCAN is necessary to bring in the new workload.

JOB1:

//BACKUP  EXEC CAJUTIL0                                   
//SYSPRINT DD SYSOUT=*                                   
//CAIJBRK  DD DSN=HLQ.CAIJTRK.DATE.BACKUP,DISP=(,CATLG), 
//     SPACE=(CYL,(XX,Y),RLSE),UNIT=SYSDA  

//SYSIN DD*

 BACKUP CAIJTRK                

 

JOB2:

//FORMAT  EXEC CAJUTIL0         
//SYSIN    DD   *              
 FORMAT CAIJTRK