|
SMF Type 96 RecordThis table shows the record layout for type 96 SMF records
|
It's easy to report on SMF 96 data! | |
Spectrum SMF Writer handles the difficult SMF record parsing for you automatically. You just specify which fields you want to see. Spectrum SMF Writer also converts the arcane date and time fields and reformats them into an attractive report. Plus, Spectrum SMF Writer can export SMF data as comma delimited files to use on your PC.
|
Offset (Dec.) | Offset (Hex) | Name | Length | Format | Description | ||||||||
0 | 0 | SMF96LEN | 2 | binary | Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word).
| ||||||||
02 | 02 | SMF96SEG | 2 | binary | Segment descriptor (see record length field).
| ||||||||
4 | 4 | SMF96FLG | 1 | binary | System indicator:
| ||||||||
5 | 5 | SMF96RTY | 1 | binary | Record type 96 (X'60').
| ||||||||
6 | 6 | SMF96TME | 4 | binary | Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
| ||||||||
10 | 0A | SMF96DTE | 4 | packed | Date when the record was moved into the SMF buffer, in the form 0cyydddF.
| ||||||||
14 | 0E | SMF96SID | 4 | EBCDIC | System identification (from the SID parameter).
| ||||||||
18 | 12 | SMF96WID | 4 | EBCDIC | Subsystem identifier.
| ||||||||
22 | 16 | SMF96STP | 4 | binary | Record subtype.
| ||||||||
24 | 18 | SMF96JMR | 2 | binary | Displacement to the start of the requestor’s JMR data. This includes the RDW. This is also the length of the standard SMF header.
| ||||||||
28 | 1C | SMF96JL | 4 | binary | Length of the JMR data.
| ||||||||
32 | 20 | SMF96PSI | 2 | binary | Displacement to start of the provider’s data section (includes RDW).
| ||||||||
36 | 24 | SMF96PI | 2 | binary | Length of provider’s data.
| ||||||||
40 | 28 | SMF96RCS | 4 | binary | Displacement to start of the subtype data areas (includes RDW).
| ||||||||
0 | 0 | SMF96JBN | 8 | EBCDIC | Requestor’s JMRJOB data including the record descriptor word (RDW).
| ||||||||
8 | 8 | SMF96RST | 4 | binary | Requestor’s JMRENTRY.
| ||||||||
12 | 0C | SMF96RDS | 4 | packed | Requestor’s JMREDATE.
| ||||||||
16 | 10 | SMF96UIF | 8 | EBCDIC | Requestor’s JMUSEID.
| ||||||||
This section contains user information. | |||||||||||||
0 | 0 | SMF96PID | 8 | EBCDIC | “Product” name within subsystem.
| ||||||||
8 | 8 | SMF96PNM | 4 | EBCDIC | Knowledge Application name.
| ||||||||
16 | 10 | SMF96TID | 8 | EBCDIC | User/terminal identifier.
| ||||||||
28 | 1C | SMF96URT | 4 | EBCDIC | User environment.
| ||||||||
Note: Date and Time are in the same format as TIME DEC. | |||||||||||||
0 | 0 | SMF96DL | 4 | binary | Length of detail record.
| ||||||||
4 | 4 | SMF96CPU | 4 | binary | CPU time in .01 seconds.
| ||||||||
8 | 8 | SMF96DVF | 4 | binary | Vector time in .01 seconds.
| ||||||||
12 | 0C | SMF96STM | 4 | binary | Time consultation started.
| ||||||||
16 | 10 | SMF96ADT | 4 | packed | Date consultation started.
| ||||||||
Note: Date and Time are in the same format as TIME DEC. | |||||||||||||
0 | 0 | SMF96SL | 4 | binary | Length of detail record.
| ||||||||
4 | 4 | SMF96TPU | 4 | binary | CPU time in .01 seconds.
| ||||||||
8 | 8 | SMF96SVF | 4 | binary | Vector time in .01 seconds.
| ||||||||
12 | 0C | SMF96TI | 4 | binary | Time session started.
| ||||||||
16 | 10 | SMF96DI | 4 | packed | Date session started.
| ||||||||
20 | 14 | SMF96TE | 4 | binary | Time session ended.
| ||||||||
24 | 18 | SMF96DE | 4 | packed | Date session ended.
| ||||||||
28 | 1C | SMF96NOC | 4 | binary | Number of interactions with requestor during this session.
| ||||||||
32 | 20 | SMF96SAC | 2 | binary | System abend code, if any.
| ||||||||
34 | 22 | SMF96UAC | 2 | binary | User abend code, if any.
|
The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.
Home |
Products |
Prices |
Documentation |
30-Day Trials |
Customer Reviews |
Company
| FAQ
| Sample Reports
| SMF Records
Send Your Comments or Questions