OPSCON - Operations Configuration File
The Operations Configuration File (OPSCON) identifies configuration changes and when they occurred. The OPSCON file only exists as one DETAIL time-span cycle.
micsrm140cd
The OPSCON file is derived from the following SMF records:
- I/O Configuration (type 8)
- Vary Online type 9)
- Allocation Recovery type 10)
- Vary Offline type 11)
- Configuration type 22)
OPSCON 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.OPSCON Sort Sequence and Data Granularity Chart
+---------+-------------------------------------------------+ |Timespan | Level of Data Granularity | +---------+-------------------------------------------------+ | | | | DETAIL |SYSID YEAR MONTH DAY HOUR | | |ENDTS EVENT DEVCLASS DEVTYPE CONADDR | | | | | 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.
OPSCON 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 CONADDR - Device Address (Numeric) X.....E DAY - Day of Month X.....E DEVCLASS - Device Class X.....E DEVTYPE - Device Type X.....E ENDTS - End Time Stamp X.....E EVENT - SMF Incident Event 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 DEVADDR - Device Address X.....E MICSVER -MICSVersion Number X.....E ORGSYSID - Originating System Identification X.....E STARTTS - Start Time Stamp Retained Data Elements X.....E CONDESC - Detail Description Accumulated Data Elements X.....E CONCOUNT - Configuration Count
For a detailed description of individual data dictionary elements, see Operations Configuration File (OPSCON).
OPSCON Usage Considerations
The following list provides special considerations or techniques related to using the OPSCON file :
- The data for the IPL event is obtained from the SMF record type 8 - I/O Configuration.
- The data for the VARY ONLINE event is obtained from the SMF record type 9 - VARY ONLINE.
- The data for the VARY OFFLINE event is obtained from the SMF record type 11 - VARY OFFLINE.
- The data for the ALLOC RECOV event is obtained from the SMF record type 10 Allocation Recovery. The CONDESC data element contains the job name and RDRTS of the job causing the allocation recovery.
- The SMF record type 22 - Configuration also causes IPL, VARY ONLINE, and VARY OFFLINE events for the CONFIG CPU, CONFIG CHP, CONFIG VF, CONFIG STOR, CONFIG PFID, CONFIG ONLINE,S or CONFIG OFFLINE,S operator commands.
- If the event pertains to STORAGE, DESCR provides the address of the lowest page in real contiguous storage and the number of pages in real contiguous storage.
- Events relative to CPUs, CHANNEL paths, STORAGE and 3990 controllers sets the following variables accordingly:
+---------+------------+------------+ | DEVADDR | DEVCLASS | DEVTYPE | +---------+------------+------------+ CPU | '000n' | 'CPU ' | 'CPU ' | CHP | ' ' | 'CHP ' | 'CHP ' | PFID | ' ' | 'PCIE ' | 'PCIE ' | STOR | ' ' | 'STORAGE ' | 'STORAGE ' | 3990 | 'nnnn' | 'STORAGE ' | 'STORAGE ' | +---------+------------+------------+ +-------------------------------------------------+ | CONDESC | +-------------------------------------------------+ CPU |'CPUMODEL=nnnnn, CPUAD=nnn, CPUID=nn' | |'CPUMODEL=nnnnn, CPUAD=nnn, VECTOR FACILITY' | CHP |'CHPID=nnn, OWNED=yes/no, ONLINE=yes/no' | PFID |'PCIE FUNCTION ID=nn, RECONFIGURED | STOR |'LOWEST PAGE=nnnnnnn, PAGES=nnnnn' | 3990 |'SUBSYSTEM=nnnn, MODEL=nn, VOLSER=nnnnnn' | +-------------------------------------------------+
- For more information about how this statement affects the OPSCON file, see the SMFOPS parameter's CONFIGLIMIT statement in the CONFIGLIMIT - CONFIGURATION File Retention Limit section.
OPSCON Retrieval Examples
This section presents a typical OPSCON retrieval example.
- Print all the VARY CPU commands that are on the file.
DATA; SET &pOPSD..OPSCON01; IF DEVCLASS ='CPU'; PROC PRINT; VAR SYSID EVENT STARTTS ENDTS DEVTYPE;