2. MICF Options › 2.6 Data Set Allocation Parameters
2.6 Data Set Allocation Parameters
Data set allocation parameters control the allocation and
cataloging of data sets created by MICF. These parameters
include the amount of disk space allocated for the data set
and the unit/volume specification for data set allocation.
You can also change the data set name assigned to selected
MICF data sets.
When you select the Data Set Allocation Parameters option, a
scrollable list of MICF-related data sets is displayed. The
most commonly modified data set allocation parameters are
displayed on this panel. If you need to change additional
parameters, you can select a row from this scrollable display
to access a fixed panel containing all of the data set
allocation parameters.
Below are data set allocation parameters for the following
MICF data sets:
o BDTFOUT - Batch inquiry output staging CSV file output
o BICFUSER - Batch inquiry output staging catalog color
graphics outputs
o BLOG - Batch inquiry output staging catalog SAS log
o BMICSLOG - Batch inquiry output staging catalog CA MICS
log
o BREPORT - Batch inquiry output staging catalog printed
reports
o CAPACITY - Capacity planning database files
o CAPPDS - Capacity planning control members
o DTFINDEX - Index to cataloged inquiry CSV file outputs
o DTFOUT - Cataloged inquiry CSV file outputs
o LOG - Current inquiry SAS log
o MAFCNTL - MAF batch job control data set
o MICSLOG - Current inquiry MICSLOG
o OUTPUT - Cataloged inquiry outputs (reports, MICSLOG,
and SAS log)
o PCATALOG - Production catalog table data set
o PDTFINDX - Index to production inquiry output catalog
CSV file outputs
o PIXFOUT - Production inquiry output catalog CSV file
outputs
o PMICSLOG - MICF production reporting temporary MICSLOG
data set
o PMWFPDS - Production inquiry output catalog printed
reports
o PMWFSAS - Production inquiry output catalog color
graphics outputs
o PREPORT - MICF production reporting temporary printed
report data set
o PRINT - Print inquiry output with batch job staging
file
o REPORT - Current inquiry reports
o SASPROF - SAS user profile data set
o SORTWK - Sort work files
o TEMPFILE - Temporary data sets (for example, FT15F00x)
o TEMPSAS - Temporary SAS data sets such as the temporary
MCOLIB and pMUOLIB data sets
o UCATALOG - User reporting catalog table data set
o UDTFINDX - Index to user reporting inquiry output catalog
CSV file outputs
o UIXFOUT - User reporting inquiry output catalog CSV file
outputs
o UMICSLOG - MICF user reporting temporary MICSLOG data set
o UMWFPDS - User reporting inquiry output catalog printed
reports
o UMWFSAS - User reporting inquiry output catalog color
graphics outputs
o UREPORT - MICF user reporting temporary printed report
data set
o USER - SAS file - cataloged graphics and saved files
o UTILLOG - SAS log for color graphics replay and other
SAS utility processing
o UTILMLOG - MICSLOG for color graphics replay and other
SAS utility processing
o WORK - SAS work file
Any changes to the default values for the CAPACITY, CAPPDS,
DTFOUT, DTFINDEX, OUTPUT, and USER data sets must be made
before the data sets are allocated:
o CAPACITY is allocated the first time you update a capacity
planning database file or the first time you save a
forecast.
o CAPPDS is allocated the first time it is needed in the
Capacity Planner application.
o DTFOUT is allocated the first time you execute an inquiry
in foreground that creates CSV outputs or move a batch CSV
inquiry output to your private inquiry output catalog.
o DTFINDEX is allocated the first time you catalog an
inquiry output that contains CSV files or move a batch
inquiry CSV file output to your private inquiry output
catalog.
o OUTPUT is allocated the first time you catalog
an inquiry output.
o USER is allocated the first time you execute a MICF
inquiry.
Changes to BICFUSER, BLOG, BMICSLOG, BREPORT, PCATALOG,
PDTFINDX, PIXFOUT, PMWFPDS, PMWFSAS, PMICSLOG, PREPORT
UCATALOG, UDTFINDX, UIXFOUT, UMWFPDS, UMWFSAS, UMICSLOG, or
UREPORT entries take effect for the next allocation of an
associated batch staging, production, or user reporting data
set. The other data sets are reallocated for each MICF
session, so revised specifications should be effective on
your next MICF session.
The data set allocation parameters for each data set are:
DSN suffix
Required for permanent MICF user data sets. Must be
blank for temporary data sets and for MICF production and
user reporting data sets (xCATALOG, xDTFINDX, xIXFOUT,
xMWFPDS, xMWFSAS, xMICSLOG, xREPORT). The user data set
prefix specified for your data center is appended to this
parameter in order to generate the data set name. Some
entries apply to a generic set of data sets (for example,
PRINT applies to the print inquiry output staging data
sets) and are allocated with data set names containing a
logical version or cycle number. Include one or more
asterisks (*) in the data set name suffix for these data
sets to indicate where the logical version number should
appear.
The results of changing this parameter for the CAPACITY,
DTFOUT, OUTPUT, or USER data sets after the data set has
been allocated are unpredictable.
Space units
The type of space allocation for this data set. Specify
BLK, CYL, or TRK (may be abbreviated as B, C, or T
respectively).
Primary quantity
The initial amount of space to be allocated (that is, the
number of cylinders, tracks, or blocks). Specify a
number between 1 and 99999.
Secondary quantity
The amount of space to be allocated when the space
specified in primary quantity has been used. Specify a
number between 1 and 99999 for the secondary allocation.
Leave this parameter blank (or specify 0) to limit the
data set to the primary quantity.
Directory blocks
The number of partitioned data set directory blocks to be
allocated. Specify a number between 1 and 999 if data
set organization is PO or POU. Leave this parameter
blank if data set organization is PS, PSU, DA, or DAU.
Round block alloc.
Specify YES, or Y, to round block allocation up or down
to the cylinder boundary.
Specify NO, or N, for block allocation without rounding.
You must specify NO when space units are CYL or TRK.
Block size
The size of the physical blocks of records for this data
set. Specify a number between 1 and 32760.
o If record format is F, block size must equal record
length.
o If record format is FB or FS, block size must be
divisible by record length.
o If record format is V, block size must be equal to
record length plus four.
o If record format is VB, block size minus four must be
greater than or equal to record length.
Record length
The length of the records for this data set. If record
format is V, this is the maximum record length. Record
length cannot be changed.
Volume serial
Specify a 1-6 character volume serial number to allocate
this data set on a specific DASD volume. The volume
serial number may be optional or defaulted at your site,
or in some cases it may be implicitly assigned based on
the specification of the unit name.
Data set org.
The type of data set being allocated (for example, PO,
PS, DA). Data set org cannot be changed.
Expiration date
Data set expiration date in yyddd or yyyy/ddd format
(note that yyyy/ddd format is supported with MVS/XA and
above). Specify this parameter if your data center
requires expiration dates for DASD data set allocations.
Record format
The format of records in this data set. Record format
cannot be changed.
Retention period
The number of days (1-99999) the data set should be kept
before it is deleted by your data center's DASD
management routines. Retention period must be blank when
expiration date is specified.
Generic unit
The 1-8 character DASD unit name specification for data
set allocation. This parameter should match the unit
specification you normally use when allocating data sets.
It may be optional at your site, but when specified will
usually have a value such as SYSDA. See your data center
standards for valid values.
Storage Class
The 1-8 character name specification for storage class
(STORCLAS) to be used for data set allocation. Refer to
your data center standards for valid values.
Data Class
The 1-8 character name specification for data class
(DATACLAS) to be used for data set allocation. Refer to
your data center standards for valid values.
Management Class
The 1-8 character name specification for management class
(MGMTCLAS) to be used for data set allocation. Refer to
your data center standards for valid values.
Additional allocation parameters
Additional parameters your data center requires to
allocate new DASD data sets. Specify these parameters in
JCL statement format, separated by commas. Two data
entry fields are provided:
o DCB parameters - DCB subparameters, for example,
OPTCD=W)
o Other parameters - SMS parameters and other data set
allocation constructs, for example,
VOL=REF=dsname
