4. Operation › 4.4 Administering CA MICS › 4.4.8 CA MICS Administration in SMS-Controlled Environment › 4.4.8.3 Data Set Naming Conventions

4.4.8.3 Data Set Naming Conventions

Most ACS routines rely heavily on the data set name when
making allocation decisions.  This should work well in the
CA MICS environment, because CA MICS generally provides
adequate flexibility for most data set naming requirements.

Problems can arise when a CA MICS data set name conflicts
with another standard already in place.  For instance, your
Data Class ACS routine may force all *.CLIST data sets to
have RECFM=VB and LRECL=255.  This would conflict with the
attributes expected for the CA MICS CLIST data set, and could
cause failures or unexpected results.

You can avoid this type of error by having separate rules for
CA MICS data sets (see Section 4.4.8.4, Identifying CA MICS
and SAS in SMS ACS Routines), or by avoiding ACS routine
testing that is too general.

Refer to Sections 2.3.3.3 and 2.3.3.3.2.3 for information
about using JCLNAMES to override default data set names.