MICS daily production jobs may fail with a U0999 abend in the DAYALL step.
The SAS log indicates an "Apparent invocation of macro BASFMTCP not resolved" (Error 180-322).
+%BASFMTCP;
_
180
WARNING: Apparent invocation of macro BASFMTCP not resolved.
ERROR 180-322: Statement is not valid or it is used out of proper order.
This issue typically indicates that the environment cannot access the required macro member within
the MACAUTOS dataset due to security or authorization restrictions.
MICS Resource Management
Insufficient authorization access to one or more of the datasets in the SASAUTOS DD defined in the MICS proc being executed, often caused by changes to
security profiles (e.g., ACF2, RACF, or Top Secret) affecting the job user's access rights.
Verify access permissions for the user or ACID running the MICS jobs. Ensure read access is granted to the dataset(s) defined in the SASAUTOS DD concatenation and that the macro member BASFMTCP is present in the sharedprefix.MACAUTOS library.
//SAS EXEC MICSSHRx,REGION=0M,OPTIONS='VERBOSE ECHOAUTO'
//SASEXEC DD *
OPTIONS SOURCE SOURCE2 MPRINT SYMBOLGEN;
%INCLUDE SASAUTOS(BASFMTCP);
%BASFMTCP ;
ENDSAS;
If this fails with authorization errors, coordinate with your site security team to update the relevant profiles.
Example concatenation of the SASAUTOS DD in the MICS proc being executed.
//SASAUTOS DD DCB=BLKSIZE=32720,
// DISP=SHR,DSN=&USOURCE
// DD DISP=SHR,DSN=sharedprefix.MACAUTOS
// DD DISP=SHR,DSN=&SASAUTOS