CONFIGURATION RECORD FOR PROCESSOR 00 IS MISSING!

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

Symptoms:

We've been asked to change the Logical SYSID's for our VM systems in CPLXSID - When testing the changes we abend with the following message in the MICSLOG: 

CONFIGURATION RECORD FOR PROCESSOR 00 IS MISSING! 

 

Resolution:

This error occurs because the data in the suspend files contains the previous SYSID which does not match the new data.

Since SYSID is a sequence element in the suspend files, I recommend using the retrofit code from the CA MICS documentation (SMG Guide) for Value Change with Order Change. 

Here is how you can modify the retrofit sample from the documentation. Fill in the old SYSID value for 'xxxx' and the new value for 'yyyy' in the DATA step. You can add any other required logic in this section of the code. You can also substitute your unit identifier for 'd' in the JCL and in the code. If there are other suspend files that I missed, just repeat the %RETFIT macro for each of the files. 

 

//xxx JOB (your job card) 

//STEP1 EXEC MICSDBd where d is the unit id 

//SYSIN DD * 

%INCLUDE USOURCE($BASMSTR); 

%MACRO RETFIT(DDN,III,FFF,CYC,TSPAN); 

%LOCAL FILEID; 

%LET FILEID = &III&FFF&CYC; 

DATA WORK.&FILEID (KEEP= 

%&FFF.KEEP(TS=&TSPAN) 

);;;; 

SET &DDN..&FILEID; 

IF SYSID='xxxx' then SYSID='yyyy'; 

 

RUN; 

PROC SORT DATA=WORK.&FILEID 

OUT=&DDN..&FILEID(%&FFF.FILE(OP=FILEOPTS,TS=&TSPAN)); 

BY %&FFF.SEQ(TS=&TSPAN); RUN; 

%MEND RETFIT; 

 

/* RETROFIT DETAIL VMXSGS - VMX System Global Suspend File */ 

%RETFIT(&dVMXX,VMX,SGS,01,DETAIL); 

 

/* RETROFIT DETAIL VMXVSF - VMX Shared Activity Suspend File */ 

%RETFIT(&dVMXX,VMX,VSF,01,DETAIL); 

 

/* RETROFIT DETAIL VMXSPS - VMX System Processor Suspend File*/ 

 

%RETFIT(&dVMXX,VMX,SPS,01,DETAIL); 

 

Additional Information:

 

Refer to the Retrofitting Data Files section in the System Modification Guide located here