5. MICF Administration › 5.1 Tasks Performed During Installation › 5.1.1 Administrator Facility Parameters › 5.1.1.4 Data Set Allocation Parameters
5.1.1.4 Data Set Allocation Parameters
Data set allocation parameters control the allocation and
cataloging of data sets created by CA MICS. 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
CA MICS data sets.
When you select the Data Set Allocation Parameters option, a
scrollable list of CA MICS-related data sets is displayed.
The most commonly modified data set allocation parameters are
displayed on this panel. If you must 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.
Data set allocation parameters for the following data sets
are of particular importance to MICF users. MICF users
cannot override your specifications for these data sets.
o TABLES - Private (user-level) ISPF Tables Data Set
The data set allocation parameters you specify for the
TABLES data set become the default values that appear
on the "Welcome New User" panel whenever someone
invokes the CA MICS Workstation Facility for the first
time.
You should specify default allocation parameters that
provide adequate space for your users, as most users
will accept your defaults. The private ISPF tables
data set contains the user's private inquiry catalog.
The distributed defaults should provide room for 10 to
15 average inquiries. If you expect your users to
define a large number of inquiries, you must allow
them additional space.
o ISPCTLX - ISPF Temporary Control Data Sets
The ISPCTLx data sets are used in part to build the
inquiry program from the panel specifications. If
insufficient space is allocated, users will not be
able to execute large inquiries. When they attempt to
do so, they will receive messages indicating a failure
in the file tailoring service. Use the distributed
default values as a starting point and raise the space
parameters if this type of failure occurs.
You can tailor the MICF data set allocation parameters to
meet your data center standards.
o You may want to alter the data set names per
data center standards. Any changes to the data set
name should be made before the first MICF user
executes an inquiry. If the data set name parameter
is altered after a user has executed an inquiry in
foreground mode, the user will lose access to saved
inquiry outputs and saved intermediate files.
o You may want to specify a specific unit type for MICF
data sets, or even a specific volume for MICF users.
o You may want to alter the space allocations for the
type of DASD devices at your data center.
Remember to make your changes for all MICF data sets.
Allocation parameters are specified for the following:
BDTFOUT - Batch Inquiry Output Staging CSV File
Outputs
This data set contains CSV file outputs from MICF
inquiries executed in batch mode when you tell MICF to
hold inquiry output for later online review. One data
set is allocated for each CSV inquiry execution. The
asterisks (*) in the DSN suffix are replaced with a
number to generate a unique data set name. The number
of asterisks (*) in the DSN suffix limits the number
of entries that can be kept in the batch staging
inquiry output catalog. CSV file staging data sets
are deleted when you delete a batch staging catalog
entry or move an entry to your private inquiry output
catalog. If this data set is too small, inquiries
that generate large CSV files (or numerous CSV files)
could fail with a system ABEND.
BICFUSER - Batch Inquiry Output Staging Color Graphics
This data set contains color graphics outputs from
MICF inquiries executed in batch mode when you tell
MICF to hold inquiry output for later online review.
One data set is allocated for each color graphics
inquiry execution. The asterisks (*) in the DSN
suffix are replaced with a number to generate a unique
data set name. The number of asterisks (*) in the DSN
suffix limits the number of entries that can be kept
in the batch staging inquiry output catalog. Color
graphics staging data sets are deleted when you delete
a batch staging catalog entry or move an entry to your
private inquiry output catalog. Free space is
released when execution completes. If this data set
is too small, large color graphics inquiry executions
could fail with a system ABEND.
BLOG - Batch Inquiry Output Staging SAS Log
This data set contains the SAS log from MICF inquiries
executed in batch mode when you tell MICF to hold
inquiry output for later online review. One data set
is allocated for each inquiry execution. The
asterisks (*) in the DSN suffix are replaced with a
number to generate a unique data set name. The number
of asterisks (*) in the DSN suffix limits the number
of entries that can be kept in the batch staging
inquiry output catalog. SAS log staging data sets are
deleted when you delete a batch staging catalog entry
or move an entry to your private inquiry output
catalog. Free space is released when execution
completes. If this data set is too small, large
inquiry executions could fail with a system ABEND.
BMICSLOG - Batch Inquiry Output Staging MICSLOG
This data set contains the MICSLOG from MICF
inquiries executed in batch mode when you tell MICF to
hold inquiry output for later online review. One data
set is allocated for each inquiry execution. The
asterisks (*) in the DSN suffix are replaced with a
number to generate a unique data set name. The number
of asterisks (*) in the DSN suffix limits the number
of entries that can be kept in the batch staging
inquiry output catalog. MICSLOG staging data sets
are deleted when you delete a batch staging catalog
entry or move an entry to your private inquiry output
catalog. Free space is released when execution
completes. If this data set is too small, large
inquiry executions could fail with a system ABEND.
BREPORT - Batch Inquiry Output Staging Printed Reports
This data set contains printed reports from MICF
inquiries executed in batch mode when you tell MICF to
hold inquiry output for later online review. One data
set is allocated for each printed report inquiry
execution. The asterisks (*) in the DSN suffix are
replaced with a number to generate a unique data set
name. The number of asterisks (*) in the DSN suffix
limits the number of entries that can be kept in the
batch staging inquiry output catalog. Printed report
staging data sets are deleted when you delete a batch
staging catalog entry or move an entry to your private
inquiry output catalog. Free space is released when
execution completes. If this data set is too small,
large printed report inquiry executions could fail
with a system ABEND.
CAPACITY - Capacity Planning Database Files
This data set contains the capacity planning database
files defined and loaded by the Capacity Planner
online facility. If you expect that your users will
use Capacity Planner facilities heavily, you may want
to increase the default allocation for this data set.
CAPPDS - Capacity Planning Control Members
This data set contains the capacity planning control
members defined and loaded by the Capacity Planner
online facility. If you expect that your users will
use Capacity Planner facilities heavily, you may want
to increase the default allocation for this data set.
DTFINDEX - Index to cataloged CSV file inquiry outputs
This data set is part of the inquiry output catalog
and contains a directory of all CSV files that have
been saved by the user. The default allocation for
this data set should be sufficient in most cases since
this data set is only the directory and does not
contain the actual CSV files. Also, since the data
set is only allocated when a user actually runs and
then saves CSV output, there is no data set overhead
for those who do not create CSV files.
DTFOUT - Cataloged inquiry output CSV files
This data set is part of the inquiry output catalog
and contains the actual CSV file outputs that have
been saved by the user. Inquiries can create zero,
one, or more members in the CSV file catalog data set.
The names of inquiries that create CSV files and the
CSV file member names are tracked in the DTFINDEX data
set. DASD space requirements vary depending upon the
number and size of the CSV file members. If you
expect that your users will save a large number of
inquiry CSV files, you may want to increase the
default allocation for this data set. Since this data
set is only allocated when a user actually runs and
then saves CSV output, there is no data set overhead
for those who do not create CSV files.
LOG - Current Inquiry SAS Log
This data set is allocated for each MICF session and
contains the SAS log for foreground inquiry execution.
If this data set is too small, large inquiry
executions could fail with a system ABEND.
MICSLOG - Current Inquiry MICSLOG
This data set is allocated for each MICF session and
contains the MICSLOG for foreground inquiry execution.
If this data set is too small, large inquiry
executions could fail with a system ABEND.
OUTPUT - Cataloged Inquiry Outputs (reports/log)
This data set is part of the inquiry output catalog
and contains printed reports that have been saved by
the user. If you expect that your users will save a
large number of inquiry outputs, you may want to
increase the default allocation for this data set.
MAFCNTL - MAF Batch Job Control Data Set
This data set is used to communicate between batch and
online CA MICS Administrator Facility (MAF)
processing. The asterisks (*) in the DSN suffix are
replaced with a unique number in order to allocate a
unique data set for each situation where communication
between MAF batch and online processing is required.
The data set is deleted after use. The number of
asterisks (*) in the DSN suffix limits the number of
concurrent processes MAF can control. The default
space allocation should be sufficient for MAF
processing.
PCATALOG - Production Catalog Table Data Set
This data set is the primary anchor for MICF
production inquiry output catalogs (or production
reporting job stream definitions) and the MICF inquiry
production interface. A production catalog table data
set is allocated for each production catalog. It
contains the production inquiry output catalog ISPF
table and the production reporting job stream ISPF
table. Data set name is specified when the production
reporting job stream is defined. DASD space
requirements will vary depending upon the number of
inquiries in the production reporting job stream and
the number of output cycles (or job stream executions)
retained.
PDTFINDX - Index to Production Inquiry Output Catalog
CSV file outputs
This data set is part of the production reporting
inquiry output catalog and contains a directory of all
CSV files that have been created by all inquiries
associated with all executions of the production
reporting job stream. The data set is created during
the execution of any production reporting job stream
capable of creating CSV outputs. The default
allocation for this data set should be sufficient in
most cases since this data set is only the directory
and does not contain the actual CSV data files. Also,
since the data set is only allocated when the
production reporting job stream creates CSV output,
there is no data set overhead for job streams that do
not create CSV output.
PIXFOUT - Production Inquiry Output Catalog CSV Files
Production reporting CSV files are saved in the CSV
catalog data set. If a production reporting job
stream is capable of creating CSV outputs, a separate
data set is allocated for each production reporting
job stream execution. Inquiries run under the
production reporting job stream can create zero, one,
or more members in the CSV catalog data set. The
names of inquiries that create CSV output and the CSV
output member names are tracked in the PDTFINDX data
set. DASD space requirements vary depending upon the
number and size of the CSV members. You will need one
directory block for each 18 CSV members created by the
production reporting job stream.
PMICSLOG - MICF Production Reporting Temporary MICSLOG
Data Set
The MICSLOG is written to the temporary MICSLOG data
set during MICF inquiry production report processing
(set-up, allocation, execution, and post-execution
processing). The MICSLOG is copied to the printed
report catalog data set after processing completes. A
separate data set is allocated for each production
reporting job stream execution and deleted after
execution processing completes. DASD space sufficient
for 500 records (about 50 Kbytes) is generally
required.
PMWFPDS - Production Inquiry Output Catalog Printed
Reports
Production reporting printed reports, MICSLOG, and SAS
log are saved in the printed reports catalog data set.
A separate data set is allocated for each production
reporting job stream execution. Each production
reporting inquiry adds three members to the printed
reports catalog data set: printed report (Rn),
MICSLOG (Mn), and SAS log (Ln). Member name suffix
(n) is the logical inquiry number (that is, the first
inquiry generates members R1, M1, L1; the second R2,
M2, and L2; and so on). DASD space requirements vary
depending upon the number of inquiries, the size of
printed reports (number and length of lines), and the
length of the MICSLOG and the SAS log. You will need
one directory block for each six inquiries in the
production reporting job stream.
PMWFSAS - Production Inquiry Output Catalog Color
Graphics Outputs
Production reporting color graphics outputs are saved
in the color graphics catalog data set. A separate
data set is allocated for each production reporting
job stream execution. Each production reporting
inquiry adds a SAS/GRAPH GREPLAY catalog to the color
graphics catalog data set. The SAS/GRAPH GREPLAY
catalogs are named Gn, where the member name suffix
(n) is the logical inquiry number (that is, the first
color graphics inquiry generates catalog G1, the
second G2, and so on). DASD space requirements vary
depending upon the number of inquiries, the number of
graphs in each inquiry, and the complexity of color
graphics outputs.
PREPORT - MICF Production Reporting Temporary Report
Data Set
Printed reports are written to the temporary report
staging data set during MICF inquiry production report
inquiry execution. After execution completes, the
printed report is copied to the printed report catalog
data set. A separate data set is allocated for each
production reporting job stream execution and deleted
after execution processing completes. The printed
report staging data set must be large enough to hold
the largest printed report in the production reporting
job stream.
PRINT - Print Inquiry Output Staging Data Set
This data set is allocated each time you select the
Print Inquiry Output with Batch Job option from the
Print Inquiry Output menu. The asterisks (*) in the
DSN suffix are replaced with a unique number in order
to allocate a unique data set for each print request.
The staging data set is deleted when the batch job
completes. The number of asterisks (*) in the DSN
suffix limits the number of print requests the user
can issue before the generated batch jobs complete.
Also, if this data set is too small, your users will
be unable to print large inquiry outputs.
REPORT - Current Inquiry Reports
This data set is allocated for each MICF session and
contains printed reports for foreground inquiry
execution. If this data set is too small, large
inquiry executions could fail with a system ABEND.
SASPROF - SAS User Profile Data Set
This data set is allocated for MICF inquiry execution
and is used by SAS to save user profile information
such as tailored PF key definitions.
SORTWK - Sort WORK files
This data set is allocated for each MICF session and
is used for sort work space for foreground inquiry
execution. This also defines the temporary space
allocation for batch inquiry execution. If this data
set is too small, large inquiry executions could fail
with a system ABEND.
TEMPFILE - Temporary Data Sets (for example, FT15F00x)
This entry provides data set allocation parameters for
temporary work data sets required for inquiry
processing. If this data set is too small, complex
executions could fail.
TEMPSAS - Temporary SAS Data Sets
This entry provides data set allocation parameters for
temporary SAS data sets required for inquiry
processing. For example, the TEMPSAS entry is used to
allocate the temporary MCOLIB and pMUOLIB data sets
that hold the CA MICS user-defined SAS formats copied
from sharedprefix.MICS.MCOLIB and prefix.MICS.MUOLIB
for inquiry execution. If this data set is too small,
all inquiry executions will fail.
USER - SAS File - Cataloged Graphics and Saved Files
This data set is part of the inquiry output catalog
and contains color graphics that have been saved by
the user. Saved intermediate files are also stored in
this data set. If you expect that your users will
save a large number of inquiry outputs or use a large
number of saved files, you may want to increase the
default allocation for this data set.
UTILLOG - SAS Log for Color Graphics Replay, etc.
This data set is allocated for each MICF session and
contains the SAS log for color graphics replay and
other utility SAS invocations.
UTILMLOG - MICSLOG for Color Graphics Replay, etc.
This data set is allocated for each MICF session and
contains the MICSLOG for color graphics replay and
other utility SAS invocations.
WORK - SAS WORK File
This data set is allocated for each MICF session and
is used for intermediate files and SAS work space for
foreground inquiry execution. This also defines the
temporary space allocation for batch inquiry
execution. If this data set is too small, large
inquiry executions could fail with a system ABEND.
