MICSLS1- BASCPYVR step ends with a RC=4 causing remaining steps to flush

Products

• MICS Resource Management

Issue/Introduction

As part of SAS upgrade to a newer version, is the MICS job, MICSLS1, which converts MICS to use a newer version of SAS. 
The job is ending with a RC=4 in the very first step of the job (BASCPYVR).
As a result, all of the remaining steps in the job are flushed. 

Cause

Missing MABATCH9 member in the 'sharedprefix.PARMS' dataset

The SAS LOG contains the following:

     SAS PROC PDSCOPY VERSION 9.40    
  
     INPUT  DSNAME=xxxx.xxx.xxxx.PARMS  VOL=SER=xxxxx
     OUTPUT DSNAME=xxxx.xxxx.xxxx.TEMPPARM  VOL=SER=xxxx
  
     MEMBER     TRACKS       SIZE
       ALIAS
  
     ICFBTCH9    0.2         7360    
     ICFDMS9     0.2         7520    
     MATSO9      0.2         7440    
     MQRBTCH9    0.1         5200    

 WARNING:  no members found to match MABATCH9

Resolution

The MABATCH9 parms member was copied over from another MICS complex and then the job was resubmitted and completed successfully. 

Note about MABATCH/MABATCH9.
It is recommended that a local modification is made to the MICS-shipped SAS CONFIG member for V9 'sp.MICS.PARMS(MABATCH9)' instead of directly modifying the MABATCH member.  Then submit the job in 'sharedprefix.CNTL(MICSLS1).  Directly updating the MABATCH member in 'sp.MICS.PARMS' is not recommended as any future submissions of MICSLS1 will overwrite any user modifications made to the MABATCH member.