2. Administrative Information Area Files › 2.5 Space Utilization File
2.5 Space Utilization File
FILENAME=ADMSPC01
The Space Utilization File contains data identifying the
space usage of the DAILY operational jobs, such as
incremental and DAILY update.
The following three sections describe the file's
organization, list the data elements maintained, and provide
usage hints.
1 - File Organization
2 - Data Elements List
3 - Usage Considerations
2.5.1 File Organization
The table below identifies data elements by which the file is
sequenced and summarized in each timespan. N/A indicates
that the file is not supported in a timespan. At the DETAIL
level, data is sequenced but not summarized.
NOTE: The timespans in which a file is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS system
at your installation.
+---------+-------------------------------------------------+
|Timespan | Level of Data Granularity |
+---------+-------------------------------------------------+
| | |
| DETAIL | N/A |
| | |
| DAYS |SPCRUNTS |
| | |
| WEEKS | N/A |
| | |
| MONTHS | N/A |
| | |
| YEARS | N/A |
| | |
+---------+-------------------------------------------------+
| TABLES | N/A |
+---------+-------------------------------------------------+
NOTE: This file was generated with ESSENTIAL=ALL
option in effect. All data elements defined in
the file are generated.
NOTE: This file was generated with DERIVED=DISK
option in effect. All computed data elements
are kept on the file on auxiliary storage.
Figure 2-2. ADMSPC Timespan Granularity Chart
2.5.2 Data Elements List
The table below identifies data elements contained in this
file. The entries for each data element are:
TIMESPAN: Defines the timespans in which the data element
is supported. The timespans are indicated by
the letters "XDWMYT" as follows:
X - DETAIL
D - DAYS
W - WEEKS
M - MONTHS
Y - YEARS
T - TABLES AREA
. - File is not supported
The timespan field also indicates Essential Elements with
the letter E, if applicable.
DATA ELEMENT: The data element name.
DATA ELEMENT DESCRIPTION: The data element's long name.
The timespans in which a data element is supported are
defined by each installation when CA MICS is installed.
Therefore, this table has been generated as part of the
installation process to accurately reflect the CA MICS
system at your installation.
Note: Essential data elements are identified by an "E"
under the Timespan asterisk (*) column.
Time- Data Data Element
Span * Element Description (LABEL)
------- -------- ----------------------------------------
Sequence/Summary Data Elements
.D....E SPCRUNTS - Space Reporting Run Time Stamp
Common Data Elements
.D....E DAY - Day of Month
.D....E DAYNAME - Name of Day of Week
.D....E DSNAME - Data Set Name
.D....E HOUR - Hour of Day
.D....E LIBNAME - SAS Libname
.D....E MICSCOMP - CA MICS Component Identification
.D....E MONTH - Month of Year
.D....E WEEK - Week of Year
.D....E YEAR - Year of Century
.D....E ZONE - Time Zone
Retained Data Elements
.D....E SPCALLOC - Tracks Allocated
.D....E SPCBLKS - Blocks Per Track
.D....E SPCBLKSZ - Block Size
.D....E SPCDVTYP - Device Type
.D....E SPCFREE - Tracks Free
.D....E SPCMEMCT - Number of Members
.D....E SPCPCMAX - Max Percent Tracks Used
.D....E SPCPCUSD - Percent Tracks Used
.D....E SPCSTEP - Job step
.D....E SPCTYPE - Library Type
.D....E SPCUSED - Tracks Used
.D....E SPCVOL - Number of Volumes
Maximum Data Elements
.D....E SPCMXUSD - Max Tracks Used
2.5.3 Usage Considerations
This section identifies any special considerations or
techniques related to using the ADMSPC file. Additionally,
retrieval examples are provided to facilitate the use of this
file. MICF inquiry BASLA5 is also available to report on
this file.
In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan. For the examples, a database
identifier of P is used. The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.
Special Considerations/Techniques
1. This file is only available at the DAYS timespan. It
is sequenced by the SPCRUNTS data element but is not
summarized.
2. This file is a spin file. This means only one cycle
can exist, so when new observations are added to the
file, older observations are removed based on the
SPCUTILLIMIT specified in prefix.MICS.PARMS(EXECDEF).
3. Each observation is a snapshot of the space used by
the file type (see SPCTYPE) during the operational
update job step. The space utilization of the CA
MICS database itself is reported prior to cycle
aging, and may not reflect the space used at the end
of the step (and job).
Retrieval Examples
1. Retrieve the work space usage for the DAY030 step
executed yesterday:
DATA TEMP ;
SET &PADMD..ADMSPC01;
IF DATEPART(SPCRUNTS)=TODAY()-1 AND
LIBNAME =: 'WORK' and SPCSTEP = 'DAY030' ;
RUN;
PROC PRINT;
VAR MICSCOMP SPCSTEP LIBNAME
SPCALLOC SPCUSED SPCMXUSD SPCPCUSD SPCPCMAX ;
RUN;
2. Retrieve all the observations from yesterday and
order by MICS Component, step and execution
date/time:
DATA TEMP ;
SET N0days.ADMSPC01;
IF DATEPART(SPCRUNTS)=TODAY()-5 ;
RUN;
PROC SORT IN=TEMP OUT=SORTED ;
BY MICSCOMP SPCSTEP descending spcrunts ;
RUN;
PROC PRINT;
VAR MICSCOMP SPCSTEP SPCRUNTS LIBNAME
SPCALLOC SPCUSED SPCMXUSD SPCPCUSD SPCPCMAX ;
RUN;
