OPSAVL - System Availability File
The System Availability File (OPSAVL) quantifies the amount of time that the MVS control program was not active. It is derived from the SMF System Status Record (type 90 subtype 8) and from manual update.
micsrm140
OPSAVL File Organization
The following table identifies the sequence and summarization data elements for each timespan. N/A indicates that the file is not supported in a timespan. At the DETAIL level, data are sequenced but not summarized.
The timespans, in which a file is supported, are defined by each data center when
MICS
is installed. Therefore, this table has been generated as part of the installation process to reflect the MICS
system at your data center.OPSAVL Sort Sequence and Data Granularity Chart
+---------+-------------------------------------------------+ |Timespan | Level of Data Granularity | +---------+-------------------------------------------------+ | | | | DETAIL |SYSID YEAR MONTH DAY HOUR | | |ENDTS | | | | | DAYS | N/A | | | | | WEEKS | N/A | | | | | MONTHS | N/A | | | | | YEARS | N/A | | | | +---------+-------------------------------------------------+ | TABLES | N/A | +---------+-------------------------------------------------+ Generation Date: Tue, May 12, 2014
This file was generated with ESSENTIAL=ALL option in effect. All data elements defined in the file are generated.
This file was generated with DERIVED=DEFault option in effect. The complex definition of the DERIVED option controls whether the data elements are kept on the file on auxiliary storage or not.
OPSAVL Data Elements List
This section identifies data elements that are contained in this file. See the Data Element Naming Conventions section for details.
GENERATION DATE: Tue, May 12, 2014 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 X.....E DAY - Day of Month X.....E ENDTS - End Time Stamp X.....E HOUR - Hour of Day X.....E MONTH - Month of Year X.....E SYSID - System Identifier X.....E WEEK - Week of Year X.....E YEAR - Year of Century X.....E ZONE - Time Zone Common Data Elements X.....E DAYNAME - Name of Day of Week X.....E MICSVER -MICSVersion Number X.....E ORGSYSID - Originating System Identification X.....E STARTTS - Start Time Stamp Retained Data Elements X..... AVLONM - Operator Name X.....E AVLORCD - Operator Reason Code For Down Time X.....E AVLORSN - Operator Reason For Down Time X..... AVLPNM - Post Entry Name X..... AVLPRCD - Post Reason Code For Down Time X..... AVLPRSN - Post Reason For Down Time Accumulated Data Elements X.....E AVLCOUNT - Down Time Count X.....E AVLODTM - Operator Reported Down Time
For a detailed description of individual data dictionary elements, see System Availability File (OPSAVL).
OPSAVL Usage Considerations
To facilitate trend analysis, we recommend use of an IPL reason code, whether entered by the console operator at the time of IPL, after a complete analysis of the cause of IPL, or both. For the list of suggested IPL reason codes, see SMF Operations Information Area.
The Operations Availability File (OPSAVL) is built during normal SMF daily processing in the DETAIL file if input data contains the SMF type 90 subtype 8 records. These records document the system operator's reason for IPL, the amount of time the system was down, the time of the IPL, and the operator's name. SMF Operations Information Area provides suggestions for automating data entry. Access is made to this file through the
MICS
data entry process to permit data center personnel to record post-analysis reason codes and descriptions for the IPL.Data centers not producing the SMF type 90 subtype 8 record or not permitting operator specification of IPL reason code via the IPL PROMPT option can use this file to manually enter records of IPLs.
To manually enter data, do the following:
- Select the SAS WithMICSLibraries (MSAS) option from theMICS Workstation Facilitymenu as discussed in Entering Data IntoMICS.
- Select theMICSData Entry option from the SAS WithMICSLibraries (MSAS) menu.
The
MICS
Data Entry menu is then displayed. Specify the mode of operation (B-Browse, D-Data Entry, or S-Screen Modification) in the Function field and the number of the file to be processed (1 in this case) in the Data Source field. To update the System Availability File, choose Function D and Data Source 1, and press ENTER.The MICF Execution-Time Parameters panel is displayed for you to select a unit database that contains the Batch and Operations Analyzer with the OPSAVL file that you intend to modify. If you are uncertain which unit databases contain the OPSAVL file, enter a ? (question mark) for database ID and MICF will display a selection list of just those unit databases that contain the OPSAVL file. Use the S (Select) line command and press ENTER to select a unit database. Enter the END command (or press the END PFkey) on the Execution-Time Parameters panel to continue.
Interactive SAS will be invoked and the first observation in the data set will be displayed. If no data exists in the file, an empty observation will be displayed if you requested Data Entry mode. If you requested Browse mode, SAS/FSP will display the following message on the second line of the screen:
Error======> There are no observations to BROWSE
When the first observation is displayed, you can modify any field on the screen. If you are adding a new observation to the file, you must supply TIME OF THE IPL and LOGICAL SYSTEM IDENTIFICATION. If you are updating an existing entry, you can enter any applicable fields.
There are several methods to view another observation in the file:
- You can view the next observation in the file by pressing PF8.
- You can go directly to an observation by typing the observation number on the command line and pressing ENTER.
- You can search for a specific observation using the F (Find) or L (Locate) commands.
To exit the update or browse process, use the PF3 key. Then issue the BYE command to return to the
MICS
Data Entry panel.OPSAVL Retrieval Examples
This section presents a typical OPSAVL retrieval example.
- Print all the downtime occurrences.
DATA; SET &pOPSD..OPSAVL01; PROC PRINT; VAR STARTTS ENDTS AVLCOUNT AVLODTM AVLONM AVLORCD AVLORSN AVLPNM AVLPRCD AVLPRSN;