SMF Type 30 Record
This table shows the record layout for type 30 SMF records (Common Address Space Work).
We also have some tips for working with SMF type 30 records.
And you can see a sample report made from SMF records.
| Offset (Dec.) | Offset (Hex) | Name | Length | Format | Description |
| 0 | 0 | SMF30LEN | 2 | binary | Record Length. This field along with the next, are referred to as the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 2 | 2 | SMF30SEG | 2 | binary | Segment descriptor (see record length field).
|
| 4 | 4 | SMF30FLG | 1 | binary | System indicator: Bit Meaning When Set 0 Subsystem identification follows system identification 1 Subtypes used 2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 5 | 5 | SMF30RTY | 1 | binary | Record type 30 (X'1E').
|
| 6 | 6 | SMF30TME | 4 | binary | Time since midnight, in hundredths of a second, that the record was moved to the SMF buffer.
|
| 10 | A | SMF30DTE | 4 | packed | Date that the record was moved to the SMF buffer, in the form 0cyydddF (in local time). See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 14 | E | SMF30SID | 4 | EBCDIC | System identification (from the SID parameter).
|
| 18 | 12 | SMF30WID | 4 | EBCDIC | Work type indicator for the address space. The value identifies the type of address space that is being reported on (for example: “STC” for started tasks and system address spaces, “TSO” for TSO/E users, etc).
|
| 22 | 16 | SMF30STP | 2 | binary | Record subtype. For a list of the record subtypes, see page 13-118.
|
| 24 | 18 | SMF30SOF | 4 | binary | Offset to subsystem section from start of record, including the record descriptor word (RDW).
|
| 28 | 1C | SMF30SLN | 2 | binary | Length of subsystem section.
|
| 30 | 1E | SMF30SON | 2 | binary | Number of subsystem sections.
|
| 32 | 20 | SMF30IOF | 4 | binary | Offset to identification section from start of record, including the record descriptor word (RDW).
|
| 36 | 24 | SMF30ILN | 2 | binary | Length of identification section.
|
| 38 | 26 | SMF30ION | 2 | binary | Number of identification sections.
|
| 40 | 28 | SMF30UOF | 4 | binary | Offset to I/O activity section from start of record, including the record descriptor word (RDW).
|
| 44 | 2C | SMF30ULN | 2 | binary | Length of I/O activity section.
|
| 46 | 2E | SMF30UON | 2 | binary | Number of I/O activity sections.
|
| 48 | 30 | SMF30TOF | 4 | binary | Offset to completion section from start of record, including the record descriptor word (RDW).
|
| 52 | 34 | SMF30TLN | 2 | binary | Length of completion section.
|
| 54 | 36 | SMF30TON | 2 | binary | Number of completion sections.
|
| 56 | 38 | SMF30COF | 4 | binary | Offset to processor section from start of record, including the record descriptor word (RDW).
|
| 60 | 3C | SMF30CLN | 2 | binary | Length of processor section.
|
| 62 | 3E | SMF30CON | 2 | binary | Number of processor sections.
|
| 64 | 40 | SMF30AOF | 4 | binary | Offset to accounting section from start of record, including the record descriptor word (RDW).
|
| 68 | 44 | SMF30ALN | 2 | binary | Total length of the single accounting section.
|
| 70 | 46 | SMF30AON | 2 | binary | Number of variable length text segments.
|
| 72 | 48 | SMF30ROF | 4 | binary | Offset to storage section from start of record, including the record descriptor word (RDW).
|
| 76 | 4C | SMF30RLN | 2 | binary | Length of storage section.
|
| 78 | 4E | SMF30RON | 2 | binary | Number of storage sections.
|
| 80 | 50 | SMF30POF | 4 | binary | Offset to performance section from start of record, including the record descriptor word (RDW).
|
| 84 | 54 | SMF30PLN | 2 | binary | Length of the performance section.
|
| 86 | 56 | SMF30PON | 2 | binary | Number of performance sections.
|
| 88 | 58 | SMF30OOF | 4 | binary | Offset to operator section from start of record, including the record descriptor word (RDW).
|
| 92 | 5C | SMF30OLN | 2 | binary | Length of the operator section.
|
| 94 | 5E | SMF30OON | 2 | binary | Number of operator sections.
|
| 96 | 60 | SMF30EOF | 4 | binary | Offset to the execute channel program (EXCP) section from start of record, including the record descriptor word (RDW).
|
| 100 | 64 | SMF30ELN | 2 | binary | Length of the execute channel program (EXCP) section, in this record.
|
| 102 | 66 | SMF30EON | 2 | binary | Number of execute channel program (EXCP) sections in this record.
|
| 104 | 68 | SMF30EOR | 2 | binary | Number of execute channel program (EXCP) sections in subsequent records. When this number exceeds two bytes, it is invalid. See SMF30EOS for the correct value.
|
| 106 | 6A | SMF30RVD | 2 | -- | Reserved.
|
| 108 | 6C | SMF30EOS | 4 | binary | Number of execute channel program (EXCP) sections in subsequent records.
|
| 112 | 70 | SMF30DRO | 4 | binary | Offset to APPC/MVS resource section from start of record, including the record descriptor word (RDW).
|
| 116 | 74 | SMF30DRL | 2 | binary | Length of APPC/MVS resource section.
|
| 118 | 76 | SMF30DRN | 2 | binary | Number of APPC/MVS resource sections in this record (this number is 0 or 1).
|
| 120 | 78 | SMF30ARO | 4 | binary | Offset to APPC/MVS cumulative resource section from start of record, including the record descriptor word (RDW).
|
| 124 | 7C | SMF30ARL | 2 | binary | Length of APPC/MVS cumulative resource section.
|
| 126 | 7E | SMF30ARN | 2 | binary | Number of APPC/MVS cumulative resource sections in this record (this number is 0 or 1).
|
| 128 | 80 | SMF30OPO | 4 | binary | Offset to OpenMVS process section.
|
| 132 | 84 | SMF30OPL | 2 | binary | Length of OpenMVS process section.
|
| 134 | 86 | SMF30OPN | 2 | binary | Number of OpenMVS process sections on current record.
|
| 136 | 88 | SMF30OPM | 4 | binary | Number of OpenMVS process sections on subsequent records.
|
| 140 | 8C | SMF30UDO | 4 | binary | Offset to first usage data section from the start of the record, including the record descriptor word (RDW).
|
| 144 | 90 | SMF30UDL | 2 | binary | Length of each usage data section - ‘76’.
|
| 146 | 92 | SMF30UDN | 2 | binary | Number of usage data sections in this record.
|
| 148 | 94 | SMF30UDS | 4 | binary | Number of usage data sections in subsequent records.
|
| 152 | 98 | SMF30RMO | 4 | binary | Offset to first automatic restart management section.
|
| 156 | 9C | SMF30RML | 2 | binary | Length of automatic restart management section.
|
| 158 | 9E | SMF30RMN | 2 | binary | Number of automatic restart management sections.
|
| 160 | A0 | SMF30RMS | 4 | binary | Number of automatic restart management sections in subsequent records.
|
| 164 | A4 | SMF30MOF | 4 | binary | Offset to the Multisystem Enclave Remote Data section.
|
| 168 | A8 | SMF30MLN | 2 | binary | Length of MultiSystem Enclave Remote System Data section.
|
| 170 | AA | SMF30MNO | 2 | binary | Number of MultiSystem Enclave Remote System Data sections in this record.
|
| 172 | AC | SMF30MOS | 4 | binary | Number of MultiSystem Enclave Remote System Data sections in subsequent records.
|
| 0 | 0 | SMF30TYP | 2 | binary | Subtype identification Value Meaning 1 Job start or start of other work unit. 2 Activity since previous interval ended. Produced only when interval recording is active. 3 Activity for the last interval before step termination. Produced only when interval recording is active. 4 Step total 5 Job termination or termination of other work unit. 6 System address space.
|
| 2 | 2 | SMF30RS1 | 2 | -- | Reserved.
|
| 4 | 4 | SMF30RVN | 2 | EBCDIC | Record version number Value Meaning C’05’ MVS/SP Version 5 X'04' MVS/SP Version 4 X'03' MVS/SP Version 3 X'02' MVS/SP Version 2 X'01' VS2
|
| 6 | 6 | SMF30PNM | 8 | EBCDIC | Subsystem or product name, for example SMF.
|
| 14 | E | SMF30OSL | 8 | EBCDIC | MVS software level (consists of an acronym and the version, release, and modification level numbers).
|
| 22 | 16 | SMF30SYN | 8 | EBCDIC | System name (from the SYSNAME parameter in the IEASYSxx parmlib member).
|
| 30 | 1E | SMF30SYP | 8 | EBCDIC | Sysplex name (from the SYSPLEX parameter in the COUPLExx parmlib member).
|
| 0 | 0 | SMF30JBN | 8 | EBCDIC | Job or session name. The job name, time and date that the reader recognized the JOB card (for this job) constitute the job log identification.
|
| 8 | 8 | SMF30PGM | 8 | EBCDIC | Program name (taken from PGM= parameter on EXEC card). If a backward reference was used, this field contains PGM=*.DD.
|
| 16 | 10 | SMF30STM | 8 | EBCDIC | Step name (taken from name on EXEC card).
|
| 24 | 18 | SMF30UIF | 8 | EBCDIC | User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement).
|
| 32 | 20 | SMF30JNM | 8 | EBCDIC | JES job identifier. Jobs scheduled by the APPC/MVS transaction scheduler (ASCH) start with an “A” followed by a seven-digit number.
|
| 40 | 28 | SMF30STN | 2 | binary | Step number (first step = 1, etc.).
|
| 42 | 2A | SMF30CLS | 1 | binary | Job class (blank for TSO/E session or started tasks). 43 2B 1 Reserved.
|
| 44 | 2C | SMF30PGN | 2 | binary | Beginning with z/OS V1R3, this field is always zero.
|
| 46 | 2E | SMF30JPT | 2 | binary | JES input priority. If no value is specified for the PRTY parameter (on the JOB card), this field contains: v For JES3, the default priority specified on the JES3 STANDARDS initialization card v For JES2, a zero.Note that JES2 does not use the priority value reported in the field. (The JES2 job selection priority is requested via the JES2 PRIORITY control statement.)
|
| 48 | 30 | SMF30AST | 4 | binary | Device allocation start time, in hundredths of a second.
|
| 52 | 34 | SMF30PPS | 4 | binary | Problem program start time, in hundredths of a second.
|
| 56 | 38 | SMF30SIT | 4 | binary | Time since midnight, in hundredths of a second, that the initiator selected this step or job.
|
| 60 | 3C | SMF30STD | 4 | packed | Date that the initiator selected this step, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 64 | 40 | SMF30RST | 4 | binary | Time since midnight, in hundredths of a second, that the reader recognized the JOB card (for this job).
|
| 68 | 44 | SMF30RSD | 4 | packed | Date that the reader recognized the JOB card (for this job), in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 72 | 48 | SMF30RET | 4 | binary | Time since midnight, in hundredths of a second, that the reader recognized the end of the job or started task (reader stop time). For TSO/E this is the logon enqueue time.
|
| 76 | 4C | SMF30RED | 4 | packed | Date that the reader recognized the end of the batch job or started task (reader stop date), in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 80 | 50 | SMF30USR | 20 | EBCDIC | Programmer’s name.
|
| 100 | 64 | SMF30GRP | 8 | EBCDIC | RACF group ID. 0 = RACF is not active.
|
| 108 | 6C | SMF30RUD | 8 | EBCDIC | RACF user ID. 0 = RACF is not active.
|
| 116 | 74 | SMF30TID | 8 | EBCDIC | RACF terminal ID. This field is zero if RACF is not active (or the user is not a terminal user).
|
| 124 | 7C | SMF30TSN | 8 | EBCDIC | Terminal symbolic name.
|
| 132 | 84 | SMF30PSN | 8 | EBCDIC | The name of the step that invoked the procedure. This field contains blanks if not part of a procedure.
|
| 140 | 8C | SMF30CL8 | 8 | EBCDIC | 8-character job class (left justified, padded with blanks). For JES2, taken from the SMF30CLS field (if not specified), blank for TSO session or started tasks. For JES3, taken from CLASS= parameter on //* MAIN card (if valid), or the default (JES3BATCH).
|
| 148 | 94 | SMF30ISS | 8 | binary | Time and date that the interval started for subtype 2 and 3 records, in time-of-day (TOD) format, an unsigned 64-bit fixed-point number where bit 51 is equivalent to 1 microsecond. The representation of this value in local time is stored in SMF30IST and SMF30IDT. Variations in setting the local time can make the times appear to be out of synchronization.
|
| 156 | 9C | SMF30IET | 8 | binary | Time and date that the interval ended for subtype 2 and 3 records, in time-of-day (TOD) format, an unsigned 64-bit fixed-point number where bit 51 is equivalent to 1 microsecond. If you requested synchronized interval recording, you can use this field to compare this record with other records generated at the end of the same interval. If the address space being reported was not swapped in when the interval ended then the time contained in this field might be earlier than the time that the record was generated.
|
| 164 | A4 | SMF30SSN | 4 | binary | Substep number. This field is set to zero for non-OpenMVS steps. When the OpenMVS exec function is requested, a new substep is begun and this value is incremented.
|
| 168 | A8 | SMF30EXN | 16 | binary | Program name. For an OpenEdition program, this contains the name, for up to 16 bytes, starting after the last slash in the filename, of the program that was run. The OpenEdition name ends with the null character X'00'. For an MVS program, it is an unqualified name of up to 8 characters of the program that was executed. The MVS program name is padded with blanks to a length of 16 characters. For example, for an OpenEdition name of /usr/joe/somepgm, the field in SMF record type 30 is somepgm ended by X'00'. For an OpenEdition name of /usr/joe/someverylongprogramname, the field is truncated to someverylongprog.
|
| 0 | 0 | SMF30INP | 4 | binary | Number of card-image records in DD DATA and DD* data sets read by the reader for the map. This field is not set for subtypes 2 or 3. Offsets Name Length Format Description
|
| 4 | 4 | SMF30TEP | 4 | binary | Total blocks transferred (accumulated execute channel program (EXCP) counts).
|
| 8 | 8 | SMF30TPT | 4 | binary | Number of TPUTS (terminal writes) for a TSO/E session. If a batch job or a started task successfully processes TPUTs, this field might be non-zero for batch jobs or started tasks.
|
| 12 | C | SMF30TGT | 4 | binary | Number of TGETS (terminal reads) for a TSO/E session.
|
| 16 | 10 | SMF30RDR | 1 | binary | Reader device class as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.
|
| 17 | 11 | SMF30RDT | 1 | binary | Reader device type as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.
|
| 18 | 12 | SMF30TCN | 4 | binary | Total device connect time (in 128 micro-second units) for this address space. For a DIV object, this field contains total device connect time for reads, writes, and re-reads.
|
| 22 | 16 | SMF30DCF | 4 | binary | Flag word Bit Meaning When Set 0 Device connect time may be incorrect 1-31 Reserved.If this flag is set, the system resources manager (SRM) disabled the channel measurement while the job was running. If channel measurement is disabled, device connect time is not recorded. Thus, if this bit is set, SMF30TCN and SMF30DCT reflect less than the actual total connect time.
|
| 26 | 1A | SMF30RSB | 2 | -- | Reserved.
|
| 28 | 1C | SMF30TRR | 4 | binary | Total address space REREAD count.
|
| 32 | 20 | SMF30AIC | 4 | binary | DASD I/O connect time, in 128-microsecond units, for address space plus dependent enclaves.
|
| 36 | 24 | SMF30AID | 4 | binary | DASD I/O disconnect time, in 128-microsecond units, for address space plus dependent enclaves.
|
| 40 | 28 | SMF30AIW | 4 | binary | DASD I/O pending plus control unit queue time, in 128-microsecond units, for address space plus dependent enclaves.
|
| 44 | 2C | SMF30AIS | 4 | binary | DASD I/O start subchannel count for address space plus dependent enclaves.
|
| 48 | 30 | SMF30EIC | 4 | binary | DASD I/O connect time, in 128-microsecond units, for indpendent enclaves owned by the address space.
|
| 52 | 34 | SMF30EID | 4 | binary | DASD I/O disconnect time, in 128-microsecond units, for independent enclaves owned by the address space.
|
| 56 | 38 | SMF30EIW | 4 | binary | DASD I/O pending plus control unit queue time, in 128-microsecond units, for independent enclaves owned by the address space.
|
| 60 | 3C | SMF30EIS | 4 | binary | DASD I/O start subchannel count for independent enclaves.
|
| 0 | 0 | SMF30SCC | 2 | binary | Step completion code: X'0ccc' indicates system abnormal end of task (abend) in the job step where ccc is the system abend code. (See z/OS MVS System Codes.) X'8ccc' indicates user abend in the job step where ccc is the user abend code. X'nnnn' indicates normal completion where nnnn is the contents of the two low-order bytes in register 15 at termination. X'0000' indicates either: 1. The job step was flushed (not processed) because of an error during allocation or in a preceding job step, or 2. Normal job completion with a return code of 0. Use this field in conjunction with the job/step termination indicator field, SMF30STI.Job completion code: X'0ccc' indicates system ABEND in the last job step where ccc is the system abend code. (See z/OS MVS System Codes.) X'8ccc' indicates user abend in the job step where ccc is the user abend code. X'nnnn' indicates normal completion where nnnn is the contents of the two low-order bytes in register 15 at termination. X'0000' indicates either: (see note) 1. The last job step was flushed (not processed) because of an error during allocation or in a preceding job step, or 2. Normal job completion with a return code of 0. Use this field in conjunction with the job/step termination indicator field, SMF30STI.Note: When a step in a multi-step job terminates abnormally, the subsequent steps, whether executed or flushed, do not propagate the step abend code for processing this record. The code appears in the step termination record (subtype 4). In this case, the field, SMF30SCC, can contain X'nnnn' or X'0000'. If an abend occurred in the job, the job termination indicator (bit 7 in the SMF30STI field).
|
| 2 | 2 | SMF30STI | 2 | binary | Step/Job termination indicator Bit Meaning When Set 0 Reserved 1 Canceled by exit IEFUJV 2 Canceled by exit IEFUJI 3 Canceled by exit IEFUSI 4 Canceled by exit IEFACTRT 5 Step is to be restarted 6 If zero, then normal completion. If 1, then abnormal end of task (abend). If step completion code equals 0322 or 0522, then IEFUTL caused the abend. If step completion code equals 0722, then IEFUSO caused the abend. 7 If zero, then normal completion. If 1, then step was flushed. 8 EXCP counts might be incorrect because the record did not include all the DD statements. 9 Previous interval record was not written because an error occurred. The cumulative count might be incorrect because the counters were cleared. 10 EXCP sections were not merged from the interval to the step record or from the step to the job record 11 Step completed with a “post execution” error. Post-execution errors include a failure that occurred because the ALLOCxx parmlib member specified CATLG_ERR FAILJOB(YES). 12 Step completed due to OpenMVS exec function request. 13 JOB abnormally ended because of COND= condition on the JOB card. This flag will be set on in the subtype 5 job termination record only. 14-15 Reserved.
|
| 4 | 4 | SMF30ARC | 4 | binary | Abend reason code.
|
| 0 | 0 | SMF30PTY | 2 | binary | Reserved.
|
| 2 | 2 | SMF30TFL | 2 | binary | Invalid timer flags Bit Meaning When Set 0 Indicates that timer flags are used. 1 SMF30CPT has an invalid value due to a timer value calculation error. 2 SMF30CPS has an invalid value due to a timer value calculation error. 3 SMF30JVU has an invalid value due to a timer value calculation error. 4 SMF30JVA has an invalid value due to a timer value calculation error. 5 SMF30ISB has an invalid value due to a timer value calculation error. 6 SMF30ICU has an invalid value due to a timer value calculation error. 7 SMF30IVU has an invalid value due to a timer value calculation error. 8 SMF30IVA has an invalid value due to a timer value calculation error. 9 SMF30IIP has an invalid value due to a timer value calculation error. 10 SMF30HPT has an invalid value due to a timer value calculation error. 11 SMF30RCT has an invalid value due to a timer value calculation error. 12 SMF30ASR has an invalid value due to a timer value calculation error. 13 SMF30ENC has an invalid value due to a timer value calculation error. 14 SMF30DET has an invalid value due to a timer value calculation error. 15 Reserved.
|
| 4 | 4 | SMF30CPT | 4 | binary | All standard CPU step time in hundredths of a second. Includes enclave time, preemptable class SRB time, client SRB time. Also includes time consumed by IFA eligible work running on a standard processor. For time spent on an IFA, see SMF30_TIME_ON_IFA. Note that a workload may generate different values for SMF30CPT if some IFA eligible work runs on a standard processor. If a repeatable value is more desirable than the possible performance benefits of letting IFA eligible work run on both IFAs and standard processors, specify IFACROSSOVER=NO in the IEAOPTxx parmlib member.
|
| 8 | 8 | SMF30CPS | 4 | binary | Step CPU time under the service request block (SRB), in hundredths of a second.
|
| 12 | C | SMF30ICU | 4 | binary | Initiator CPU time under the task control block (TCB), in hundredths of a second. This field is set at step termination.
|
| 16 | 10 | SMF30ISB | 4 | binary | Initiator CPU time under the service request block (SRB), in hundredths of a second. This field is set at step termination.
|
| 20 | 14 | SMF30JVU | 4 | binary | Step vector CPU time, in hundredths of a second.
|
| 24 | 18 | SMF30IVU | 4 | binary | Initiator vector CPU time, in hundredths of a second. This field is set at step termination.
|
| 28 | 1C | SMF30JVA | 4 | binary | Step vector affinity time, in hundredths of a second.
|
| 32 | 20 | SMF30IVA | 4 | binary | Initiator vector affinity time, in hundredths of a second. This field is set at step termination.
|
| 36 | 24 | SMF30IST | 4 | binary | Interval start time for type 30 subtype 2 and 3 records, in hundredths of a second.
|
| 40 | 28 | SMF30IDT | 4 | packed | Interval start date for type 30 subtype 2 and 3 records, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 44 | 2C | SMF30IIP | 4 | binary | Amount of CPU time used to process I/O interrupts, in hundredths of a second.
|
| 48 | 30 | SMF30RCT | 4 | binary | Amount of CPU time used by the region control task (RCT), in hundredths of a second.
|
| 52 | 34 | SMF30HPT | 4 | binary | CPU time consumed for the step, in hundredths of a second, to support requests for data to be transferred between a hiperspace and an address space, when the hiperspace is backed by expanded storage. The CPU time may vary depending on the availability of expanded storage.
|
| 56 | 38 | SMF30CSC | 4 | binary | Integrated Cryptographic Service Facility/MVS (ICSF/MVS) service count. This is the number of cryptographic instructions executed on behalf of caller (within caller’s address space).
|
| 60 | 3C | SMF30DMI | 4 | binary | ADMF-Number of pages moved with ADMF WRITE operation.
|
| 64 | 40 | SMF30DMO | 4 | binary | ADMF-Number of pages moved with ADMF READ operation.
|
| 68 | 44 | SMF30ASR | 4 | binary | Additional CPU time accumulated by the preemptable SRBs and client SRBs for this job, in hundredths of a second. This value is also included in the value in SMF30CPT.
|
| 72 | 48 | SMF30ENC | 4 | binary | CPU time used by the independent enclave, but only when in the WLM enclave. Note that independent enclave time on an IFA is not included. See field SMF30_ENCLAVE_TIME_ON_IFA for that value. SMF30ENC is also part of the value in SMF30CPT.
|
| 76 | 4C | SMF30DET | 4 | binary | CPU time used by the dependent enclave, but only when in the WLM enclave. Note that dependent enclave time on an IFA is not included - see field SMF30_DEP_ENCLAVE_TIME_ON_IFA for that value. SMF30DET is also part of the value in SMF30CPT.
|
| 80 | 50 | SMF30CEP | 4 | binary | CPU time consumed for an address space or job while enqueue promoted (in 1.024 millisecond units).
|
| 82 | 52 | SMF30TF2 | 2 | binary | Additional timer flags Bit Meaning When Set 0 SMF30_TIME_ON_IFA has an invalid value due to a timer value calculation error. 1 SMF30_ENCLAVE_TIME_ON_IFA has an invalid value due to a timer value calculation error. 2 SMF30_DEP_ENCLAVE_TIME_ON_IFA has an invalid value due to a timer value calculation error. 3 SMF30_TIME_IFA_ON_CP has an invalid value due to a timer value calculation error. 4 SMF30_ENCLAVE_TIME_IFA_ON _CP has an invalid value due to a timer value calculation error. 5 SMF30_DEP_ENCLAVE_TIME_IFA_ON _CP has an invalid value due to a timer value calculation error.
|
| 84 | 54 | SMF30_ TIME_ ON_ IFA | 4 | binary | CPU time spent on IFA in hundredths of a second (including enclave time).
|
| 88 | 58 | SMF30_ ENCLAVE_ TIME_ ON_ IFA | 4 | binary | Enclave time spent on IFA in hundredths of a second.
|
| 92 | 5C | SMF30_ DEP_ ENCLAVE_ TIME_ ON_ IFA | 4 | binary | Dependent enclave time spent on IFA in hundredths of a second.
|
| 96 | 60 | SMF30_ TIME_ IFA_ ON_ CP | 4 | binary | CPU time spent running IFA eligible work on a standard CP in hundredths of a second (including enclave time).
|
| 100 | 64 | SMF30_ ENCLAVE_ TIME_ IFA_ ON_ CP | 4 | binary | IFA Enclave time spent on a standard CP in hundredths of a second.
|
| 104 | 68 | SMF30_ DEP_ ENCLAVE_ TIME_ IFA_ ON_ CP | 4 | binary | IFA Dependent enclave time spent on a standard CP in hundredths of a second.
|
| 0 | 0 | SMF30DEV | 1 | binary | Device class.
|
| 1 | 1 | SMF30UTP | 1 | binary | Unit type.
|
| 2 | 2 | SMF30CUA | 2 | binary | Device number.
|
| 4 | 4 | SMF30DDN | 8 | EBCDIC | DD Name used to access the data set.
|
| 12 | C | SMF30BLK | 4 | binary | Count of blocks issued for the device against the data set.
|
| 16 | 10 | SMF30BSZ | 2 | binary | Largest blocksize of the data set Bit Meaning When Set 0 Indicated changed blocksize for the data set. Post processors should use this field to avoid the possibility of negative numbers. 1-15 Largest blocksize of the data set.
|
| 18 | 12 | SMF30DCT | 4 | binary | Device connect time for this data set (in 128 micro-second units). For DIV object, device connect time is not collected by SMF; however, this field may not always be zero. For example, if a user is using a DIV data set and calls a VSAM utility to process it using the same DD statement, this will result in device connect time being charged by VSAM to the DIV object.
|
| 22 | 18 | SMF30XBS | 8 | binary | Block size value.
|
| 0 | 0 | SMF30ACL | 1 | binary | Length of accounting section (excluding this field).
|
| 1 | 1 | SMF30ACT | variable | EBCDIC | Job or step accounting field.
|
| 0 | 0 | SMF30RSV | 2 | Reserved. | Note that SMF30RGN, formerly a two-byte field at this offset, has been increased to four bytes and moved to the end of the Storage and Paging Section.
|
| 2 | 2 | SMF30SFL | 1 | binary | Storage Flags. If storage was not allocated (job step was flushed), these fields equal zero. Bit Meaning When Set 0 V=R is specified. This bit has no meaning for subtype 5 records. 1 IEFUSI changed region limit values for the extended private area 2 IEFUSI changed memlimit value. 3-7 Reserved.
|
| 3 | 3 | SMF30SPK | 1 | binary | Storage protect key, in the form xxxx0000 where xxxx is the key.
|
| 4 | 4 | SMF30PRV | 2 | binary | Largest amount of storage used from bottom of private area, in 1 K units. This storage area includes subpools 0-127, 129–132, 244, 251 and 252. If ADDRSPC=REAL is specified, this field equals the amount of contiguous real storage that was used.
|
| 6 | 6 | SMF30SYS | 2 | binary | Largest amount of storage used from top of private area, in 1K units. This storage area includes the local system queue area (LSQA) and the SWA — subpools 229, 230, 236, 237, 249, and 253-255. If ADDRSPC=REAL is specified, this field equals the amount of storage used that was not from the contiguous real storage reserved for the program.
|
| 8 | 8 | SMF30PGI | 4 | binary | Number of pages that were paged in from auxiliary storage.
|
| 12 | C | SMF30PGO | 4 | binary | Number of pages that were paged out to auxiliary storage.
|
| 16 | 10 | SMF30CPM | 4 | binary | Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.
|
| 20 | 14 | SMF30NSW | 4 | binary | Number of address space swap sequences. (A swap sequence consists of an address space swap-out and swap-in. Logical swap-out and swap-in are not included.)
|
| 24 | 18 | SMF30PSI | 4 | binary | Number of pages swapped in from auxiliary storage to central storage. This field includes: (local system queue area (LSQA), fixed pages, and pages that the real storage manager determined to be active when the address space was swapping in. It does not include page reclaims or pages found in storage during the swap-in process (such as pages brought in by the service request blocks (SRB), started after completion of swap-in Stage 1 processing).
|
| 28 | 1C | SMF30PSO | 4 | binary | Number of pages swapped out from central storage to auxiliary storage. This field includes: local system queue area (LSQA), private area fixed pages, and private area non-fixed changed pages.
|
| 32 | 20 | SMF30VPI | 4 | binary | Number of VIO page-ins from auxiliary storage to central storage for this step. This field includes page-ins resulting from page faults or specific page requests on a VIO window. It does not include VIO swap-ins or page-ins for the common area.
|
| 36 | 24 | SMF30VPO | 4 | binary | Number of VIO page-outs from central storage to auxiliary storage for this step. This field includes page-outs resulting from specific page requests on a VIO window as well as those pages stolen by the paging supervisor through infrequent use. It does not include VIO swap-outs or page-outs for the common area.
|
| 40 | 28 | SMF30VPR | 4 | binary | Number of VIO reclaims.
|
| 44 | 2C | SMF30CPI | 4 | binary | Number of common area page-ins (LPA + CSA) from auxiliary storage to central storage.
|
| 48 | 30 | SMF30HPI | 4 | binary | Number of hiperspace page-ins from auxiliary to processor storage.
|
| 52 | 34 | SMF30LPI | 4 | binary | Number of LPA page-ins from auxiliary storage to central storage.
|
| 56 | 38 | SMF30HPO | 4 | binary | Number of hiperspace page-outs from processor to auxiliary storage.
|
| 60 | 3C | SMF30PST | 4 | binary | Number of pages stolen from this address space.
|
| 64 | 40 | SMF30PSC | 8 | binary | Number of CPU page seconds for this address space, in page millisecond units. (A page millisecond unit equals 1.024 milliseconds.)
|
| 72 | 48 | SMF30RGB | 4 | binary | Private area size in bytes (less than 16 megabytes).
|
| 76 | 40 | SMF30ERG | 4 | binary | Private area size in bytes (greater than 16 megabytes).
|
| 80 | 50 | SMF30ARB | 4 | binary | Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (less than 16 megabytes).
|
| 84 | 54 | SMF30EAR | 4 | binary | Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (greater than 16 megabytes).
|
| 88 | 58 | SMF30URB | 4 | binary | Maximum virtual storage in bytes allocated from the user subpools (less than 16 megabytes).
|
| 92 | 5C | SMF30EUR | 4 | binary | Maximum virtual storage in bytes allocated from the user subpools (greater than 16 megabytes).
|
| 96 | 60 | SMF30RGN | 4 | binary | Region size established, in 1K units, rounded up to a 4K boundary. The contents of this field is determined as follows: v If the ADDRSPC=REAL parameter is specified in the JCL, the contents of this field equals the amount of contiguous central storage reserved for the program. v If the REGION= parameter value in the JCL exceeds 16 megabytes: – If the IEFUSI exit changes the region limit or size above 16 megabytes, the contents of this field equals the changed region limit or size – Otherwise, the contents of this field equals the REGION parameter value (minimum value of 32 megabytes).v If the REGION= parameter value in the JCL equals or is less than 16 megabytes: – If the IEFUSI exit changes the region limit or size below 16 megabytes, the contents of this field equals the changed region limit or size – Otherwise, the contents of this field equals the REGION parameter value.Note: If both the region limit and size are changed, but do not match, the contents of this field equals the smaller of the changed region limit or size.
|
| 100 | 64 | SMF30DSV | 4 | binary | Amount of user key data space and hiperspace virtual storage (high water mark) used during the step/job (in megabytes).
|
| 104 | 68 | SMF30PIE | 4 | binary | Number of unblocked pages that were paged in from expanded storage.
|
| 108 | 6C | SMF30POE | 4 | binary | Number of unblocked pages that were paged out to expanded storage.
|
| 112 | 70 | SMF30BIA | 4 | binary | Number of blocked pages that were paged in from auxiliary storage.
|
| 116 | 74 | SMF30BOA | 4 | binary | Number of blocked pages that were paged out to auxiliary storage.
|
| 120 | 78 | SMF30BIE | 4 | binary | Number of blocked pages that were paged in from expanded storage.
|
| 124 | 7C | SMF30BOE | 4 | binary | Number of blocked pages that were paged out to expanded storage.
|
| 128 | 80 | SMF30KIA | 4 | binary | Number of blocks that were paged in from auxiliary storage.
|
| 132 | 84 | SMF30KOA | 4 | binary | Number of blocks that were paged out to auxiliary storage.
|
| 136 | 88 | SMF30KIE | 4 | binary | Number of blocks that were paged in from expanded storage.
|
| 140 | 8C | SMF30KOE | 4 | binary | Number of blocks that were paged out to expanded storage.
|
| 144 | 90 | SMF30PSF | 8 | binary | Number of CPU page seconds for the IARVSERV shared central storage frames in use by this address space, in page milliseconds.
|
| 152 | 98 | SMF30PAI | 4 | binary | Number of IARVSERV shared pages that were paged in from auxiliary storage in this address space.
|
| 156 | 9C | SMF30PEI | 4 | binary | Number of IARVSERV shared pages that were paged in from expanded storage in this address space.
|
| 160 | A0 | SMF30ERS | 8 | binary | Expanded storage page residency time in page-milliseconds.
|
| 168 | A8 | SMF30MEM | 8 | binary | Memlimit value (in MB).
|
| 176 | B0 | SMF30MLS | 1 | binary | Source of Memlimit, which is one of the following: Value Meaning 01 MEMLIMIT set by SMF. 02 MEMLIMIT set explicitly in the JCL with MEMLIMIT parameter on JOB or EXEC statement. 03 MEMLIMIT is unlimited based on REGION=0 specification. 04 MEMLIMIT set by IEFUSI. 177 B1 23 Reserved.
|
| 0 | 0 | SMF30SRV | 4 | binary | Total service units.
|
| 4 | 4 | SMF30CSU | 4 | binary | CPU service units.
|
| 8 | 8 | SMF30SRB | 4 | binary | Service request block (SRB) service units.
|
| 12 | C | SMF30IO | 4 | binary | I/O service units.
|
| 16 | 10 | SMF30MSO | 4 | binary | Main storage occupancy (MSO) service units.
|
| 20 | 14 | SMF30TAT | 4 | binary | System resources manager (SRM) transaction active time, in 1024-microsecond units.
|
| 24 | 18 | SMF30SUS | 4 | binary | Copy of RmctAdjC when this SMF record was produced, number of sixteenths of one CPU microsecond per CPU service unit.
|
| 28 | 1C | SMF30RES | 4 | binary | System resources manager (SRM) transaction residency time, in 1024-microsecond units. That is the amount of time the SRM transaction was in real storage.
|
| 32 | 20 | SMF30TRS | 4 | binary | Number of system resources manager (SRM) transactions.
|
| 36 | 24 | SMF30WLM | 8 | EBCDIC | Workload name. This field is blank (X‘40’) when in workload management compatibility mode.
|
| 44 | 2C | SMF30SCN | 8 | EBCDIC | Service class name. This field will contain ’SYSOTHER’ during the time of a WLM POLICY switch.
|
| 52 | 34 | SMF30GRN | 8 | EBCDIC | Resource group name.
|
| 60 | 3C | SMF30RCN | 8 | EBCDIC | Report class name. This field is blank (X‘40’) during the time of a WLM POLICY switch.
|
| 68 | 44 | SMF30ETA | 4 | binary | Independent enclave transaction active time in 1024-microsecond units.
|
| 72 | 48 | SMF30ESU | 4 | binary | Independent enclave CPU service units.
|
| 76 | 4C | SMF30ETC | 4 | binary | Independent enclave transaction count.
|
| 80 | 50 | SMF30PFL | 16 | EBCDIC | Scheduling environment name. Binary zeros if no scheduling environment is specified.
|
| 96 | 60 | SMF30JQT | 4 | binary | Job preparation time. This is the elapsed time before the job was first queued for execution. It excludes time to read the job into the system. It includes delays incurred waiting for and during conversion, such as when eligible systems are not active to convert the job. If the JOB statement specified TYPRUN=JCLHOLD, this time is 0. The time is in 1024-microsecond units. It is available with OS/390 JES2 Release 4 and higher.
|
| 100 | 64 | SMF30RQT | 4 | binary | Time following job preparation when the job was ineligible for execution due to either the job’s eligible systems being inactive or the job’s scheduling environment not being available. The time is in 1024-microsecond units. It is available on OS/390 JES2 Release 4 and higher.
|
| 104 | 68 | SMF30HQT | 4 | binary | Time following job preparation when the job was ineligible for execution for reasons not included in SMF30RQT. This includes job hold, job class hold, job queue hold, duplicate jobname serialization, and job class execution limits. If the JOB statement specified TYPRUN=HOLD, the time that the job is held for this reason is not included. The time is in 1024-microsecond units. It is available with OS/390 JES2 Release 4 and higher.
|
| 108 | 6C | SMF30SQT | 4 | binary | Time the job was eligible for execution. This is the amount of time the job waited for an initiator. The time is in 1024-microsecond units. Prior to OS/390 JES2 Release 4, and for all JES3 releases, this field includes time the job was ineligible for execution.
|
| 112 | 70 | SMF30PF1 | 1 | EBCDIC | Performance section flag byte: X’80’ (SMF30PFJ) Job service class association was modified by a system operator prior to job initiation. X’40’ (SMF30PFR) Job service class association was modified by a system operator during job execution. X’20’ (SMF30PFF) Job initiation forced by a system operator. X’10’ (SMF30RTR) Job has been restarted. There is one set of SMF30 records for each time the job is restarted. X’08’ (SMF30MSI) Remote system data is incomplete. X’04’ (SMF30WMI) Job is executing in a workload manager batch initiator. X’02’ (SMF30CCP) Service class assigned to the address space was designated CPU-critical in the WLM service definition. X’01’ (SMF30CSP) Service class assigned to the address space was designated storage-critical in the WLM service definition.
|
| 113 | 71 | SMF30PF2 | 1 | EBCDIC | Performance section flag byte: X’80’ (SMF30ASP) Address space was designated storage-critical. X’40’ (SMF30SME) Address space cannot be managed to transaction goals, because “manage region to goals of region” was specified in the WLM service definition. X’20’ (SMF30CPR) Address space is currently CPU-protected. X’10’ (SMF30SPR) Address space is currently storage-protected.
|
| 114 | 72 | SMF30RS4 | 2 | EBCDIC | Reserved.
|
| 116 | 74 | SMF30JPN | 8 | EBCDIC | Subsystem collection name from IWMCLSFY SUBCOLN
|
| 0 | 0 | SMF30PDM | 4 | binary | Number of non-specific DASD mounts.
|
| 4 | 4 | SMF30PRD | 4 | binary | Number of specific DASD mounts.
|
| 8 | 8 | SMF30PTM | 4 | binary | Number of non-specific tape mounts.
|
| 12 | C | SMF30TPR | 4 | binary | Number of specific tape mounts.
|
| 16 | 10 | SMF30MTM | 4 | binary | Number of non-specific MSS mounts. As of MVS/SP4.1, this field is no longer valid, and contains zeroes.
|
| 20 | 14 | SMF30MSR | 4 | binary | Number of specific MSS mounts. As of MVS/SP4.1, this field is no longer valid, and contains zeroes.
|
| 0 | 0 | SMF30DC | 4 | binary | Number of conversations, both currently active and deallocated, associated with the transaction program ID.
|
| 4 | 4 | SMF30DCA | 4 | binary | Number of all conversations allocated.
|
| 8 | 8 | SMF30DSC | 4 | binary | Number of times the transaction program issued a Send call. Note: Because an interval or step might end in the middle of a Send call, this field might contain zero while SMF30DDS contains a nonzero value.
|
| 12 | C | SMF30DDS | 8 | long | floating point hex Amount of data, in bytes, sent by the transaction program.
|
| 20 | 14 | SMF30DRC | 4 | binary | Number of times the transaction program issued a Receive call. Note: Because an interval or step might end in the middle of a Receive call, this field might contain zero while SMF30DDR contains a nonzero value.
|
| 24 | 18 | SMF30DDR | 8 | long | floating point hex Amount of data, in bytes, received by the transaction program.
|
| 32 | 20 | SMF30DAC | 4 | binary | Number of active conversations.
|
| 36 | 24 | SMF30DTR | 4 | binary | Number of APPC/MVS transactions programs scheduled by the APPC/MVS transaction scheduler (ASCH).
|
| 0 | 0 | SMF30CN | 4 | binary | Total number of conversations associated with the transaction program (TP) ID, both currently active and deallocated.
|
| 4 | 4 | SMF30CNA | 4 | binary | Total number of all conversations allocated.
|
| 8 | 8 | SMF30SEN | 4 | binary | Total number of times the transaction program (TP) issued a Send call.
|
| 12 | C | SMF30DAT | 8 | long | floating point hex Total amount of data sent by the transaction program (TP) in bytes (long floating point).
|
| 20 | 14 | SMF30REC | 4 | binary | Total number of times the transaction program (TP) issued a Receive call.
|
| 24 | 18 | SMF30DAR | 8 | long | floating point hex Total amount of data received by the transaction program (TP) in bytes (long floating point).
|
| 32 | 20 | SMF30TAC | 4 | binary | Total number of active conversations.
|
| 36 | 24 | SMF30ATR | 4 | binary | Total number of APPC/MVS transactions programs scheduled by the APPC/MVS transaction scheduler (ASCH).
|
| 0 | 0 | SMF30OPI | 4 | binary | OpenMVS process ID.
|
| 4 | 4 | SMF30OPG | 4 | binary | OpenMVS process group ID.
|
| 8 | 8 | SMF30OUI | 4 | binary | OpenMVS process user ID.
|
| 12 | C | SMF30OUG | 4 | binary | OpenMVS process user group ID.
|
| 16 | 10 | SMF30OSI | 4 | binary | OpenMVS process session ID.
|
| 20 | 14 | SMF30OSC | 4 | binary | Number of OpenMVS services requested by the process.
|
| 24 | 18 | SMF30OST | 4 | binary | Total CPU time (in hundredths of a second) accumulated by OpenMVS services requested by the process.
|
| 28 | 1C | SMF30ODR | 4 | binary | Number of OpenMVS directory reads for the process.
|
| 32 | 20 | SMF30OFR | 4 | binary | Number of reads from OpenMVS HFS regular files.
|
| 36 | 24 | SMF30OFW | 4 | binary | Number of writes to OpenMVS HFS regular files.
|
| 40 | 28 | SMF30OPR | 4 | binary | Number of reads from OpenMVS HFS pipe.
|
| 44 | 2C | SMF30OPW | 4 | binary | Number of writes to OpenMVS HFS pipe.
|
| 48 | 30 | SMF30OSR | 4 | binary | Number of reads from OpenMVS HFS special files.
|
| 52 | 34 | SMF30OSW | 4 | binary | Number of writes to OpenMVS HFS special files.
|
| 56 | 38 | SMF30OLL | 4 | binary | Number of pathname lookup calls to the logical file system.
|
| 60 | 3C | SMF30OLP | 4 | binary | Number of pathname lookup calls to the physical file system.
|
| 64 | 40 | SMF30OGL | 4 | binary | Number of pathname generation calls to the logical file system.
|
| 68 | 44 | SMF30OGP | 4 | binary | Number of pathname generation calls to the physical file system to determine a pathname.
|
| 72 | 48 | SMF30OPP | 4 | binary | Parent process ID.
|
| 76 | 4C | SMF30OKR | 4 | binary | Number of reads for network socket.
|
| 80 | 50 | SMF30OKW | 4 | binary | Number of writes for network socket.
|
| 84 | 54 | SMF30OMS | 4 | binary | Number of bytes that message queues sent.
|
| 88 | 58 | SMF30OMR | 4 | binary | Number of bytes that message queues received.
|
| 92 | 5C | SMF30OSY | 4 | binary | Number of times the sync() function was called.
|
| 0 | 0 | SMF30RNM | 16 | EBCDIC | Element name.
|
| 16 | 10 | SMF30RTP | 8 | EBCDIC | Element type.
|
| 24 | 18 | SMF30RRG | 16 | EBCDIC | Restart group for element in SMF30RNM.
|
| 40 | 28 | SMF30RSN | 8 | EBCDIC | The system name for the system on which the element was initially started; blank, for the initial start. Note: The current system name is in the SMF30SYN field.
|
| 48 | 30 | SMF30RGT | 4 | binary | The time (local) when the element issued the IXCARM macro with the REGISTER parameter, in hundredths of a second.
|
| 52 | 34 | SMF30RGD | 4 | binary | The date when the element issued the REGISTER request, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
|
| 56 | 38 | SMF30RWT | 4 | binary | The time (local) when the element issued the IXCARM macro with the WAITPRED parameter, in hundredths of a second. This field will be zero if this function was not requested.
|
| 60 | 3C | SMF30RWD | 4 | binary | The date when the element issued IXCARM with the WAITPRED parameter, in the form 0cyydddF (where ‘F’ is the sign). This field will be zero if this function was not requested.
|
| 64 | 40 | SMF30RYT | 4 | binary | The time (local) when the element issued the IXCARM macro with the READY parameter, in hundredths of a second.
|
| 68 | 44 | SMF30RYD | 4 | binary | The date when this element issued the IXCARM macro with the READY parameter, in the format 0cyydddF (where ‘F’ is the sign).
|
| 72 | 48 | SMF30RTT | 4 | binary | The time (local) when the element was deregistered, in hundredths of a second. This field will be zero if this element is not yet deregistered or if it ended abnormally.
|
| 76 | 4C | SMF30RTD | 4 | binary | The date when this element was deregistered, in the format 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description. This field will be zero if this element is not yet deregistered or if it ended abnormally.
|
| 0 | 0 | SMF30UPO | 16 | EBCDIC | Product owner or vendor name (specified on the PRODOWNER option of the IFAUSAGE macro).
|
| 16 | 10 | SMF30UPN | 16 | EBCDIC | Product name (specified on the PRODNAME option of the IFAUSAGE macro).
|
| 32 | 20 | SMF30UPV | 8 | EBCDIC | Product version (if specified on the PRODVERS option of the IFAUSAGE macro or ‘NONE’).
|
| 40 | 28 | SMF30UPQ | 8 | EBCDIC | Product qualifier (if specified on the PRODQUAL option of the IFAUSAGE macro or ‘NONE’).
|
| 48 | 30 | SMF30UPI | 8 | EBCDIC | Product ID (if specified on the PRODID option of the IFAUSAGE macro or ‘NONE’).
|
| 56 | 38 | SMF30UCT | 4 | binary | Product TCB Time (in hundredths of a second).
|
| 60 | 3C | SMF30UCS | 4 | binary | Product SRB Time (in hundredths of a second). 64 40 SMF30URD 8 various Product specific resource data (specified on the DATA option on the IFAUSAGE macro FUNCTIONDATA request). SMF30UDF identifies the format of the data in this field.
|
| 72 | 48 | SMF30UDF | 1 | binary | Data format of value in SMF30URD Value Meaning 0 No data specified. 1 CPU time in long floating Point (in hundredths of a second). 2 Binary (64-bit). 3 Long floating point.
|
| 73 | 49 | SMF30UFG | 1 | binary | Usage entry flags Bit Meaning when set 0 Unauthorized register 1-7 Unused 74 4A 2 Reserved.
|
| 0 | 0 | SMF30MRS | 8 | EBCDIC | System name on which enclaves created by this address space executed.
|
| 8 | 8 | SMF30MRA | 4 | binary | CPU rate adjustment factor for the system named by SMF30MRS. This is the number of sixteenths of one microsecond of CPU time per CPU service unit.
|
| 12 | C | SMF30MRD | 4 | binary | CPU time, in hundredths of a second, accumulated by dependent enclaves that executed on the system named by SMF30MRS.
|
| 16 | 10 | SMF30MRI | 4 | binary | CPU time, in hundredths of a second, accumulated by independent enclaves that executed on the system named by SMF30MRS.
|
The above table is a slightly modified version of the description provided by IBM in their "MVS Systems Management Facilities (SMF)" manual.
Below are the Spectrum SMF Writer records definitions for the SMF type 30 record.
 
|
File Definition for Type 30 SMF Records Common Address Space Work
******************************************************************** * SPECTRUM SMF WRITER -- FILE DEFINITION STATEMENTS * * SMF30 - SMF TYPE 30 RECORD "COMMON ADDRESS SPACE WORK" * ******************************************************************** |
 
 
SMF Type 0 |
SMF Type 2 |
SMF Type 3 |
SMF Type 4 |
SMF Type 5 |
SMF Type 14 |
SMF Type 15 |
SMF Type 30




