4. Operation › 4.3 Operations Reference › 4.3.10 Data Set Names
4.3.10 Data Set Names
This section summarizes the data sets and data set names used
by the CA MICS system. You can change the names of the data
sets as described in the CA MICS User Names Table (JCLNAMES)
section (2.3.3.3.2.3) of this guide.
CA MICS uses four types of data sets:
o shared data sets used by all unit databases
o data sets specific to one unit database
o tape-resident (archival) data sets specific to one unit
database
o MVS system data sets
Shared data sets used by all CA MICS database units are:
sharedprefix.MICS.ASM
sharedprefix.MICS.BIN
sharedprefix.MICS.CLIST
sharedprefix.MICS.CNTL
sharedprefix.MICS.DIC.TEXT
sharedprefix.MICS.DOC.TEXT
sharedprefix.MICS.DTF.INDEX
sharedprefix.MICS.GENLIB
sharedprefix.MICS.HOLD.PARMS
sharedprefix.MICS.HOLD.USER.SOURCE
sharedprefix.MICS.INC.TEXT
sharedprefix.MICS.INCLLIB
sharedprefix.MICS.ISPHLIB
sharedprefix.MICS.ISPMLIB
sharedprefix.MICS.ISPPLIB
sharedprefix.MICS.ISPSLIB
sharedprefix.MICS.ISPTLIB
sharedprefix.MICS.LIBLOAD.CNTL
sharedprefix.MICS.LOAD
sharedprefix.MICS.LOCALMOD.CNTL
sharedprefix.MICS.MACAUTOS
sharedprefix.MICS.MACLIB
sharedprefix.MICS.MCOLIB
sharedprefix.MICS.MQR.TEMPLATE
sharedprefix.MICS.MWFPDS.DATA
sharedprefix.MICS.MWFSAS.DATA
sharedprefix.MICS.OBJ
sharedprefix.MICS.PARMS
sharedprefix.MICS.PROTOLIB
sharedprefix.MICS.SASFLS
sharedprefix.MICS.SCREENS
sharedprefix.MICS.SOURCE
sharedprefix.MICS.TABLES
sharedprefix.MICS.TEST.INCLLIB
sharedprefix.MICS.TEST.SOURCE
sharedprefix.MICS.USER.SOURCE
DASD data sets for use with a specific database are:
prefix.MICS.CHECKPT.DATA
prefix.MICS.CNTL
prefix.MICS.IMSSUS1
prefix.MICS.IMSSUS2
prefix.MICS.MODEL
prefix.MICS.MUOLIB
prefix.MICS.PARMS
prefix.MICS.RESTART.CNTL
prefix.MICS.USER.SOURCE
prefix.MICS.SPECIAL.SOURCE
prefix.MICS.DETAIL
prefix.MICS.DAYS
prefix.MICS.WEEKS
prefix.MICS.MONTHS
prefix.MICS.YEARS
The DAYSMF step of the DAILY job splits the input data into
work data sets for the CA MICS products in the unit database.
The work data sets are named as follows, where ccc is the
corresponding component ID:
prefix.MICS.ccc.DATA
See the prefix.MICS.PARMS(JCLDEF) SMFRECORDING parameter for
a list of the ccc values for a unit database. Your
prefix.MICS.PARMS(JCLDEF) DAYSMF parameter specification
controls whether the DAYSMF work data sets are permanent data
sets or whether they are scratched after the DAILY job
completes.
When incremental update is enabled for a Data Integration
Application, the corresponding INCRccc and DAILY database
update job steps allocate the following data sets:
$SMEM @BASIPDS
prefix.MICS.ccc.IUCKPT
prefix.MICS.ccc.IUDETAIL
prefix.MICS.ccc.IUTAPE
tapeprefix.MICS.ccc.IUXTAPE.GggggV00
tapeprefix.MICS.ccc.IUDTAPE.GggggV00
Note: In the list above, ccc is the component ID.
The IUXTAPE and IUDTAPE Generation Data
Group data sets apply to the optional INCRDB
TAPE option.
The SPLITSMF job splits the input data into work data sets
for processing in the INCRccc jobs of those CA MICS products
in the unit database that have both INCRUPDATE YES and
INCRSPLIT USE parameters specified in the cccOPS parameter
member. The work data sets are named as follows, where ccc
is the corresponding component ID:
prefix.MICS.ccc.IUSPLTDS
See the prefix.MICS.PARMS(JCLDEF) SMFRECORDING parameter for
a list of the potential ccc values for a unit database. Then
check prefix.MICS.PARMS(cccOPS) for the INCRUPDATE YES and
INCRSPLIT USE options.
When internal step restart is enabled for a Data Integration
Application, the corresponding DAILY database update job step
dynamically allocates the following data sets:
$SMEM @BASRPDS
prefix.MICS.cccXCKPT
prefix.MICS.cccXWORK
prefix.MICS.cccWRKnn
Note: In the list above, ccc is the component ID
and nn the work file number (01 - 99).
If default archiving definitions are used, the archive tape
data sets used by a specific unit are:
tapeprefix.MICS.AUDIT.iiifff.GggggV00
tapeprefix.MICS.BACKUP.tttttt.GggggV00
tapeprefix.MICS.BACKUP.CHECKPT.GggggV00
tapeprefix.MICS.HISTW.iiifff.GggggV00
tapeprefix.MICS.HISTM.iiifff.GggggV00
tapeprefix.MICS.MBACKUP.tttttt.GggggV00
tapeprefix.MICS.MBACKUP.CHECKPT.GggggV00
Note: In the list above, iiifff represents a
CA MICS file name and tttttt is a time-span or can
be SCREENS, TABLES, CAPACITY, CIMANAGE, or ISPTLIB.
MVS system data sets that are updated for CA MICS are:
o MVS system or user catalog
o SYS1.PROCLIB or other cataloged procedure data set
Another way to look at the data sets listed above is to
consider their functions in a running CA MICS system.
CA MICS data sets can be subdivided by what they contain:
o Programs in both source and load module form. With SAS,
programs are run from their source version. The load
libraries are used for CA MICS routines coded in IBM
assembly language.
o Data, both online and offline.
o Documentation in both machine-readable and printable form.
o Control Information, whether maintained in CA MICS files
or MVS system files (for example, prefix.MICS.PARMS or
SYS1.PROCLIB).
o Test Libraries for testing modifications to CA MICS.
Each of these functions is described in detail in the
sections below.
PROGRAMS
sharedprefix.MICS.ASM
A source library containing the source for some modules in
the CA MICS system written in assembly language.
sharedprefix.MICS.BIN
A binary object distribution library for CA MICS
distributed system, UNIX Systems Services (USS), and
facilities related to CA's U.S. Patented Neugents(R)
technology. The members in this library are generally
"downloaded" to distributed systems and/or UNIX Systems
Services HFS sub-directories.
sharedprefix.MICS.MACLIB
A source library containing the assembly language macros
for the CA MICS system.
sharedprefix.MICS.OBJ
An OS/390 object module distribution library for CA MICS
distributed system, UNIX Systems Services (USS), and
Neugents related facilities. The members in this library
are frequently processed by the OS/390 linkage editor on
your system to install CA MICS facilities that operate
under UNIX Systems Services.
sharedprefix.MICS.LOAD
A load module library containing routines that perform
CA MICS functions not implementable in SAS (such as those
that update the Checkpoint data set in place), CA MICS
extensions to the SAS language (such as new FORMATs and
INFORMATs), and CA MICS extensions to IBM's ISPF (such as
MADA).
sharedprefix.MICS.ISPxLIB
A set of libraries containing the ISPF panels, messages,
tutorials, and tables used by the CA MICS online
facilities.
These libraries include:
sharedprefix.MICS.ISPHLIB - ISPF tutorial and help panels
sharedprefix.MICS.ISPMLIB - ISPF messages
sharedprefix.MICS.ISPPLIB - ISPF panels
sharedprefix.MICS.ISPSLIB - ISPF skeletons
sharedprefix.MICS.ISPTLIB - ISPF tables
sharedprefix.MICS.INCLLIB
A library containing SAS source members that consist
primarily of SAS %INCLUDE statements. These members are
used in place of concatenated SYSIN DD statements to allow
conditional selection of SAS modules.
sharedprefix.MICS.MACAUTOS
A library containing the source for SAS macros in the
CA MICS system. This is a SAS autocall macro library.
sharedprefix.MICS.MQR.TEMPLATE
A library containing the templates used by the CA MICS
Mainframe Server associated with Q&R Workstation.
sharedprefix.MICS.SOURCE
A library containing the source for modules in the CA MICS
system written in SAS.
sharedprefix.MICS.USER.SOURCE
A library containing complex-level source code modules
intended to be modified by the user (e.g., those that
generate exception reports) and SAS macros produced as part
of the CA MICS installation and generation processes.
sharedprefix.MICS.HOLD.USER.SOURCE
A source library containing the source modules copied by
the COPYLIBS and COPYLIBU jobs when a new unit database is
created.
prefix.MICS.USER.SOURCE
A library containing unit-level source code modules
intended to be modified by the user (e.g., those that
generate exception reports) and SAS macros produced as part
of the CA MICS installation and generation processes.
sharedprefix.MICS.CLIST
A library containing source modules other than assembler,
SAS, or ISPF dialog manager code.
DATA (Online)
The following data sets comprise the CA MICS database. If
you must break up any of the following data sets in order to
provide enough space to hold all of your data, refer to the
CA MICS Database Split Table (DBSPLIT) section (2.3.3.3.2.4)
of this guide. For products that have their own guides,
refer to the information contained in those guides for
information specific to the product.
sharedprefix.MICS.ACTAUDIT
A data set used by CA MICS Accounting and Chargeback.
Refer to the product guide for more information about this
data set.
sharedprefix.MICS.CAPACITY
A SAS-managed data set containing files used by the CA MICS
Capacity Planner. See the product guide for more
information about this data set.
sharedprefix.MICS.DTF.INDEX
A sequential data set used as a directory of all Comma
Separated Value (CSV) extract files available to other
applications. See the CA MICS Q&R Workstation User Guide
for more information about this data set.
sharedprefix.MICS.TABLES
A SAS-managed data set containing data for CA MICS files in
the Accounting and Operations information areas. These
files are not organized by timespan; data is entered into
the files manually or by monthly Accounting and Chargeback
processing.
sharedprefix.MICS.MWFPDS.DATA
A library used by the CA MICS Information Center Facility
(MICF) Shared Inquiry Output Catalog feature to save
printed reports and the SAS log from CA MICS inquiry
execution for later review.
sharedprefix.MICS.MWFSAS.DATA
A SAS-managed data set used by the CA MICS Information
Center Facility (MICF) Shared Inquiry Output Catalog
feature to save color graphics from MICF inquiry execution
for later review.
prefix.MICS.DETAIL
A SAS-managed data set holding all of the SAS files that
make up the DETAIL timespan of the CA MICS database.
prefix.MICS.DAYS
A SAS-managed data set holding all of the SAS files that
make up the DAYS timespan of the CA MICS database.
prefix.MICS.WEEKS
A SAS-managed data set holding all of the SAS files that
make up the WEEKS timespan of the CA MICS database.
prefix.MICS.MONTHS
A SAS-managed data set holding all of the SAS files that
make up the MONTHS timespan of the CA MICS database.
prefix.MICS.YEARS
A SAS-managed data set holding all of the SAS files that
make up the YEARS timespan of the CA MICS database.
Summarizing data at the YEARS level is optional. A small
YEARS file is kept in the database if you set the YEARS
timespan to inactive in prefix.MICS.PARMS(SITE) or in
sharedprefix.MICS.PARMS(CPLXDEF). The YEARS file contains
empty cycles (or zero observations) of CA MICS files
supported at the YEARS timespan.
If you set the YEARS timespan to inactive by setting the
YEARS timespan flag to No for each file in
sharedprefix.MICS.GENLIB(cccGENIN) (where ccc is the three-
letter component identifier), no YEARS files are kept in
the database.
Incremental Update Data Sets
When incremental update is enabled for a Data Integration
Application, the corresponding INCRccc and DAILY database
update job steps allocate the data sets listed below.
Depending on the options selected, these data sets can be one
of the following:
o Permanent.
o Allocated at the beginning of the INCRccc or DAILY
job step and then deleted after being copied to tape.
o Allocated at the beginning of the day and then
deleted when the DAILY job completes successfully.
Note: ccc is the Data Integration Application Component ID.
prefix.MICS.ccc.IUDETAIL
A SAS-managed data set holding the current day's
incremental update DETAIL timespan SAS files for the ccc
product.
prefix.MICS.ccc.IUDAYS
A SAS-managed data set holding the current day's
incremental update DAYS timespan SAS files for the ccc
product.
prefix.MICS.ccc.IUCKPT
The ccc product's incremental update checkpoint file is
used to keep track of the status of incremental update
processing for this product. Both the status of the last
incremental update step to complete and the low and high
date/time stamps associated with input data processed
to-date are kept here. This data set allows CA MICS to
maintain database integrity during incremental update
processing.
Internal Step Restart Data Sets
When internal step restart is enabled for a Data Integration
Application, the corresponding DAILY database update job step
dynamically allocates the following data sets.
These data sets are allocated and cataloged at the beginning
of the database update job step, and then are deleted at
normal end of job. However, if the job step abends, the data
sets are retained for restart.
Note: ccc is the Data Integration Application Component ID.
prefix.MICS.cccXCKPT
A SAS-managed data set holding the SAS files that comprise
the internal step restart checkpoint for this database
update step. These include the internal step restart
control file, the internal step restart data set status
file, and last completed database update processing phase
checkpoint files.
prefix.MICS.cccXWORK
The SAS work file for this database update step.
prefix.MICS.cccWRKnn
The multiple work file support data sets for this database
update step, where nn is the work file number (01 - 99).
DATA (Offline)
All of the following data sets are named using the tapeprefix
to associate them with other data sets specific to one
CA MICS unit database.
The value of tapeprefix is set by the TAPEPREFIX option of
prefix.MICS.PARMS(JCLDEF). You can set tapeprefix equal to
prefix or it can be different if required to meet your site's
JCL standards for the naming of data sets stored on tape.
CA MICS packs multiple, related tape data sets onto a single
tape in order to conserve tape volumes.
In the following data set names:
o timespan is either DETAIL, DAYS, WEEKS, MONTHS, YEARS,
CAPACITY, CIMANAGE, ISPTLIB, SCREENS, or TABLES
o gggg is the generation number
o nn is the volume number
o iiifff is the name of a CA MICS file (e.g., HARCPU)
o ccc is the CA MICS product identifier (e.g., SMF)
tapeprefix.MICS.BACKUP.timespan.GggggVnn
CA MICS backs up the online database as specified in
prefix.MICS.PARMS(JCLDEF). Each time a backup is made, a
new Generation Data Group (GDG) catalog entry is created
for each of the timespans (DETAIL, DAYS, WEEKS, MONTHS,
YEARS). The Checkpoint data set associated with the online
database is also backed up since it must be kept
synchronized with the database. For the BACKUP job in the
PRIMARY unit, complex data sets are also backed up. These
include the sharedprefix.MICS CAPACITY, CIMANAGE, ISPTLIB,
SCREENS, and TABLES data sets.
tapeprefix.MICS.MBACKUP.timespan.GggggVnn
CA MICS takes an additional backup of the online database
and its checkpoint file each month as an added precaution
against catastrophic data loss. These data sets are
patterned after the normal backup data sets discussed
above.
tapeprefix.MICS.AUDIT.iiifff.GggggVnn
CA MICS supports the creation of archive audit files. This
support allows you to keep information about individual
units available for far longer periods of time than can be
managed in the online database.
If ARCHIVE AUDIT YES is specified in
prefix.MICS.PARMS(JCLDEF), the AUDIT flag is set to Yes in
sharedprefix.MICS.GENLIB(cccGENIN), and audit archive is
active for this file in prefix.MICS.PARMS(DBMODEL); then
each week thereafter, a data set with a name in the form
shown above is created. This data set contains a copy of
the entire week's DETAIL-level data (or DAYS-level data if
the DETAIL timespan is not supported) for user-related (as
opposed to system-related) files.
tapeprefix.MICS.HISTW.iiifff.GggggVnn
CA MICS supports the creation of archive history files.
This support allows you to keep information in the WEEKS
timespan available for far longer periods of time than can
be managed in the online database.
If ARCHIVE HISTW YES is specified in
prefix.MICS.PARMS(JCLDEF), the HISTW flag is set to Yes in
sharedprefix.MICS.GENLIB(cccGENIN) and weekly history
archive is active for this file in
prefix.MICS.PARMS(DBMODEL). Then, each week thereafter, a
data set with a name in the form shown above is created.
This data set contains all of the WEEKS data previously
gathered for each file plus data from the week just ended
(subject to the cutoff limit specified in
prefix.MICS.PARMS(DBMODEL)).
tapeprefix.MICS.HISTM.iiifff.GggggVnn
CA MICS supports the creation of archive history files.
This support allows you to keep information in the MONTHS
timespan available for far longer periods of time than can
be managed in the online database.
If ARCHIVE HISTM YES is specified in
prefix.MICS.PARMS(JCLDEF), the HISTM flag is set to Yes in
sharedprefix.MICS.GENLIB(cccGENIN), and monthly history
archive is active for this file in
prefix.MICS.PARMS(DBMODEL); then each month thereafter, a
data set with a name in the form shown above is created.
This data set contains all of the MONTHS data previously
gathered for each file plus that from the month just ended
(subject to the cutoff limit specified in
prefix.MICS.PARMS(DBMODEL)).
tapeprefix.MICS.ccc.IUXTAPE.GggggVnn
The CA MICS incremental update facility supports the option
to offload incremental update data to tape between INCRccc
and DAILY job executions. With this option, data processed
since the beginning of the day is online only when needed.
This tape data set stores DETAIL timespan data from
incremental update processing.
tapeprefix.MICS.ccc.IUDTAPE.GggggVnn
The CA MICS incremental update facility supports the option
to offload incremental update data to tape between INCRccc
and DAILY job executions. With this option, data processed
since the beginning of the day is online only when needed.
This tape data set stores DAYS timespan data from
incremental update processing.
DOCUMENTATION
The text for all CA MICS documentation is available in the
following libraries. JCL and programs are supplied with
CA MICS to format this text into printable guides or it can
be browsed online using the Documentation Access option from
the CA MICS Workstation Facility.
sharedprefix.MICS.DOC.TEXT
This data set contains all CA MICS documentation that is
not generated or is not a data element definition. It is a
variable blocked, LRECL=137 library containing single
column text (columns 2-62) and figures (to column 133).
The members of this library have stylized names:
o the first one or two characters are the CA MICS manual
identifier
o the remaining characters denote the chapter and section
in the guide.
For example, the text you are reading is found in member
L43A, where
o L is the (arbitrary) code for the CA MICS Planning,
Installation, Operation, and Maintenance Guide
o 43A denotes chapter 4, section 3.10. Prefaces are
denoted as X0, appendices as XA and so forth. Section
numbers above 9 are coded as letters, where A=10, B=11,
and so forth.
Members used in multiple guides or sections have names
different from the structure noted above. For example,
sample ISPF panel members use the same name as in the
ISPPLIB library.
CA MICS manual identifiers are:
AH - CA MICS Tandem Option Guide
AI - CA MICS CA ASTEX Option Guide
BE - CA MICS How to Use the PSP
BS - CA MICS System Administrator Guide
C - CA MICS Network Analyzer Option Guide
CK - CA MICS Space Collector Option Guide
CL - CA MICS IMS Log Data Extractor Option Guide
CM - CA MICS Data Transfer Option for VM/CMS Guide
FB - CA MICS Analyzer for TSO Guide
FC - CA MICS Hardware and SCP Analyzer Guide
FD - CA MICS Batch and Operations Analyzer Guide
FE - CA MICS Analyzer Option for CICS Guide
FG - CA MICS Analyzer Option for IMS Guide
FH - CA MICS System Reliability Analyzer Option Guide
FI - CA MICS Analyzer Option for VM/CMS Guide
FJ - CA MICS Space Analyzer Option Guide
FM - CA MICS Analyzer Option for MeasureWare Guide
FN - CA MICS Analyzer Option for DB2 Guide
FO - CA MICS Analyzer Option for MQSeries Guide
FQ - CA MICS Analyzer Option for VSE/Power Guide
FT - CA MICS Tape Analyzer Option Guide
FV - CA MICS Analyzer Option for VAX/VMS Guide
FW - CA MICS Web Analyzer Option Guide
H - CA MICS Standard Reports Guide
I - CA MICS Database Structure and Content Guide
JD - CA MICS Document Access Guide
JR - CA MICS MICF Reference Guide
JU - CA MICS MICF User Guide
L - CA MICS Planning, Installation, Operation, and
Maintenance Guide
M - CA MICS System Modification Guide
PA - CA MICS Capacity Planner Option Guide
PD - CA MICS Performance Manager Option Guide
PG - CA MICS StorageMate Option Guide
PK - CA MICS Accounting and Chargeback Option
Concepts and Overview Guide
PL - CA MICS Accounting and Chargeback Option User Guide
W - CA MICS Analyzer Option for CA IDMS Guide
sharedprefix.MICS.DIC.TEXT
The text for the Data Dictionary resides in its own data
set. The member names in this library are the names of the
data elements themselves. Data elements are defined in the
cccGENIN members of sharedprefix.MICS.GENLIB. For example,
the element EXCCODE identified in BASGENIN is documented in
this data set as member EXCCODE.
sharedprefix.MICS.INC.TEXT
This library holds documentation members that are copied by
one or more documentation members during printing. Most
members in this library are generated by the CA MICS
Component Generator.
CONTROL INFORMATION
Every application system has a large amount of control
information associated with it. Some of this information
serves to guide the operation of the system's own programming
(such as parameter cards), while a good deal of it exists to
guide the operation of various operating system facilities
(such as entries in catalogs, VTOCs, the JCL PROCLIBs, etc.)
needed by the system.
CA MICS employs some very common control techniques (e.g.,
use of GDGs for related data sets) and some innovative ones
(e.g., generation of tailored SAS code as a means of
implementing CA MICS generation parameters). The following
data sets are used to control the CA MICS system.
MVS System Catalog
CA MICS employs the MVS catalog mechanism for the standard
purpose of locating its data sets. All CA MICS tape data
sets (see above) are cataloged using the Generation Data
Group facility.
SYS1.PROCLIB or Other Cataloged Procedure Data Set
CA MICS creates JCL procedures that are used by its
operational jobs (e.g., DAILY) and to allow user inquiry
into the Database. These PROCs are placed in the members
PROCJOBx of prefix.MICS.CNTL. The PROCJOBx jobs (also in
prefix.MICS.CNTL) move the JCL procedures to one of your
cataloged procedure (PROCLIB) data sets (it need not
actually be SYS1.PROCLIB).
sharedprefix.MICS.CLIST
A library containing CA MICS installation CLISTs and user-
defined CLISTs for CA MICS ISPF applications startup.
prefix.MICS.CHECKPT.DATA
The Checkpoint data set is used by CA MICS operational jobs
(e.g., the DAILY update job) to keep track of the operating
status of the system. Information such as the last job
step to complete and the low and high date/time stamps
associated with input data processed by each installed
component is kept here. This data set allows CA MICS to
maintain database integrity by refusing to restart an
operational job in any spot but the correct one.
prefix.MICS.CNTL
A JCL library containing generated batch jobs for a unit
database.
sharedprefix.MICS.CNTL
A JCL library containing distributed and generated batch
jobs that apply to the entire CA MICS complex.
sharedprefix.MICS.GENLIB
GENLIB contains control information used principally by the
CA MICS Component Generator. The generator input
statements for each product are located in this library.
It also contains one member, DBTABLE, that is used by
CA MICS for cross-checking parameters between unit
databases.
sharedprefix.MICS.HOLD.PARMS
A library containing a standard set of parameter members
that are copied by the COPYLIBS and COPYLIBU jobs when a
creating a new unit database.
sharedprefix.MICS.LOCALMOD.CNTL
Store your local modifications (e.g., IEBUPDTE modification
jobs) to CA MICS in this library. Refer to the System
Modification Guide before modifying CA MICS programs.
prefix.MICS.MODEL
When the SYSTEMMODEL JCLGEN option cannot be used at your
site, the DCB attributes of the prefix.MICS.MODEL data set
are used to create new archive and backup file generation
data groups. Since this data set never contains data, it
frequently becomes the target of DASD cleanup programs and
can be inadvertently scratched from time to time.
sharedprefix.MICS.PROTOLIB
A library of prototype JCL jobs and JCL procedures (PROCs).
Users with extraordinary JCL tailoring needs and a good
knowledge of the workings of the CA MICS JCLGEN process can
modify members in this library to make changes in generated
jobs.
Although sharedprefix libraries are shared by all CA MICS
units maintained at your site, unit-specific changes are
possible through use of Generation Control Language (GCL).
Refer to the JCLGEN Parameters for Special Requirements
section (2.3.3.3) of this guide.
prefix.MICS.PARMS
This library's members contain the numerous parameter
specifications you must make to tailor CA MICS to your
site's requirements. Some of the members contain parameter
statements and others are exits you must code in SAS.
Parameter statements do not become effective until a
generation takes place (e.g., JCLGEN or ALLPGEN). Exits
become effective immediately.
sharedprefix.MICS.PARMS
This library is similar to prefix.MICS.PARMS in function,
but is used to perform JCL generation at the CA MICS
complex level rather than the unit database level.
sharedprefix.MICS.SASFLS
A SAS-managed data set used to ship the contents of the
TABLES, SCREENS, and MWFSAS.DATA data sets. During the
installation of CA MICS, the SASFLS data set is used to
create and populate these data sets. This data set is not
used after the other data sets are created.
sharedprefix.MICS.SCREENS
A SAS-managed data set containing the screen formats for
the SAS Full Screen Product (FSP). SAS/FSP is used to
enter data for CA MICS files that allow manual data entry.
TEST LIBRARIES
sharedprefix.MICS.TEST.INCLLIB
sharedprefix.MICS.TEST.LOAD
sharedprefix.MICS.TEST.SOURCE
These libraries are provided to facilitate testing user
modifications with a TEST unit database.
