System Log Record Formats

The rest of this chapter includes the format of the log records. Notes following the log records describe the significant fields in the records.

Log failure record, type 100

Table 7-7 Log Record Heading Format

Length, in 16-bit Words	Record Content
1	Record type (100)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
2	Missing log records*
1	Missing job initiations*
1	Missing job terminations*
1	Missing I/O records*

* Lost when system logging is suspended or disabled.

System up record, type 101

Table 7-8 System Up Record Format

Length, in 16-bit Words	Record Content
1	Record type (101)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
4	Version ID (v.uu.ff)/Last 8 bits unused
2	Maximum number of concurrent jobs and sessions
2	Boot code
16	Boot device
16	Configuration group used for boot
2	NL checksum
2	Config checksum
2	SL checksum
128	Operating system nonvolatile storage

NOTES:

Boot code:

0: = Start with recovery.
1: = Start with no recovery.
2: = Update with a configuration change.
3: = Update without a configuration change.
4: = Install (new operating system loaded).

Configuration group used for boot (ASCII)

Name of group containing configuration data files used when START was invoked.

The NL, Config, and SL checksums fields are set to 0.

Operating system nonvolatile storage contains the following:

Table 7-9 ISL Data for Last Boot (128 bytes)

Reserved	36 bytes
Boot path	32 bytes
ISL revision	4 bytes
Time stamp (# seconds since 1970)	4 bytes
LIF utility entries entered	48 bytes
Pointer to last utility	1 byte
Word alignment	3 bytes

Table 7-10 MPE/iX Operating System System-Dependent Data (128 bytes)

Time stamp (# seconds since 1970)	4 bytes
# microseconds since last second	4 bytes
GR2 (caller's PC)	4 bytes
MPE/iX status:	4 bytes
For system abort, this contains failure number:
(1) Error (2 bytes)
(2) Subsystem (2 bytes)
MPE/iX version (`vv.uu.ff`)	8 bytes
Message string (if any)*	64 bytes
Halt number	2 bytes
Lockup error code	2 bytes
Reserved	36 bytes

*Identifies entity logging this entry (abort or shutdown).

Boot Device

Indicates the primary boot path, as follows:

Word 1:
Bits	(0:8)	Flags
	(8:8)	Bus Converter 0
Word 2:
Bits	(0:8)	Bus Converter 1
	(8:8)	Bus Converter 2
Word 3:
Bits	(0:8)	Bus Converter 3
	(8:8)	Bus Converter 4
Word 4:
Bits	(0:8)	Bus Converter 5
	(8:8)	Physical Module

Words 5 and 6: Logical Module
Words 7-16: Device-dependent

Job initiation record, type 102

Table 7-11 Job Initiation Record Format

Length, in 16-bit Words	Record Content
1	Record type (102)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	Job name
8	User name
8	Home group name
8	Account name
8	Logon group name
1	Input logical device number
1	Output logical device number
1	Reserved (bits 0-7)/Logon queue (bits 8-15)
2	CPU time limit
1	Inpri (bits 0-7)/Outpri (bits 8-15)
8	CI program name
8	CI program group name
8	CI program account name
2	MPE/iX logon status

NOTES:

Logon queue

Execution queue the job will run on.

CPU time limit

CPU time limit (in number of seconds) given by user on JOB or HELLO command, as follows:

          0 = not given

          # = number given

MPE/iX status

If failure occurred during job initiation, the MPE/iX status indicates an error. This field can be any MPE/iX status from the OS. If successful, value is zero.
Unlike MPE V, unsuccessful logon attempts are logged in MPE/iX system logging.

Job termination record, type 103

Table 7-12 Job Termination Record Format

Length, in 16-bit Words	Record Content
1	Record type (103)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Maximum priority
1	Number of creations
2	CPU time in seconds
2	Connect time

Process termination record, type 104

Table 7-13 Process Termination Record Format

Length, in 16-bit Words	Record Content
1	Record type (104)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
2	CPU time in milliseconds
2	Native mode stack size in bytes
2	Native mode heap size in bytes
1	CM mas stack in 16-bit words
1	Termination type
8	Reserved

NOTES:

Termination types:

0 =: Normal
1 =: Dependency (This process depends upon a terminated process.)
2 =: Killed (This process was terminated by another using KILL.)
3 =: Quit (This process called the QUIT intrinsic.)
4 =: Quitprog (This process called the QUITPROG intrinsic.)
5 =: Softfault (This process terminated due to a fault.)

NM File close record, type 105

Table 7-14 File Close Record Format

Length, in 16-bit Words	Record Content
1	Record type (105)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
4	Number of logical reads
4	Number of byes read
4	Number of logical writes
4	Number of bytes written
8	File name
8	Group name
8	Account name
8	Creator name
8	User name
8	User group
8	User account
10	Unique file identifier (UFID)
2	Reserved
2	Close disposition
2	Open domain
2	File size in bytes
4	File open count

NM File close record, type 205

The type 205 record has a "maximum path exceeded" flag.

The LDEV number of a file is also included in the log record. In most cases this is the LDEV number of the file's label and initial extent since files are not usually restricted to one volume.

Table 7-15 “Record Type 205” illustrates the format of the type 205 record.

Table 7-15 Record Type 205

Length, in 16-bit Words	Record Content
1	Record type 205
1	Event version
1	Record length
1	PIN
2	Job type/Job number
2	Time stamp time
1	Time stamp date
1	Login type (if 1, logon name is in the format 16-byte user 16-byte acct)
18	Logon name
8	Job/session name
4	Reserved
4	# logical reads
4	# bytes read
4	# logical writes
4	# bytes written
8	Creator user name (from flabel: `user.acct` for new files)
10	UFID
2	Close disposition
2	Open domain
2	File size
2	File number
4	File open count
4	Number records read
4	Number records written
1	File LDEV #
1	"Maximum path exceeded" flag (true if full path not recordable)
##	Variable-length name buffer (file name terminated with a 0 )

NOTES:

Unique file identifier (UFID)

Internal file identifier. Internal data structure that uniquely identifies a file. This entity is printed in hex.

Disposition field

Close Disposition (bits 13:3)	Open Domain
`0` No change.	`0` New file.
`1` Save permanent.	`1` Old permanent file.
`2` Save temporary - rewound.	`2` Old temporary file.
`3` Save temp - not rewound.	`3` Old job or sys.
`4` Delete.
`5` Make temporary.

Disk Space Disposition (bits 11:2)

`0`	Do not return disk space allocated beyond EOF.
`1`	Return disk space allocated beyond EOF to system; EOF becomes file limit.
`2`	Return disk space allocated beyond EOF to system; file limit remains the same (NM file types only).

The Disposition field in an NM file close record can have values from 0-9, 8-13, and 16-21. The number 255 is also a valid value for the Disposition field. Any files left open during process termination are closed by the system and given a disposition of 255.

Shutdown record, type 106

Table 7-16 Shutdown Record Format

Length, in 16-bit Words	Record Content
1	Record type (106)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Number of jobs
1	Number of sessions

Power failure record, type 107

Table 7-17 Power Failure Record Format

Length, in 16-bit Words	Record Content
1	Record type (107)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number

I/O error record, type 111

Table 7-18 I/O Error Record Format

Length, in 16-bit Words	Record Content
1	Record type (111)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
20	Hardware product number
20	Physical path description
20	Logical device name
1	Device class identifier
1	Diagnostic message class (bits 0-7)/Not used (bits 8-15)
2	I/O manager status
1	Reserved (bits 0-6) LAR (bit 7)/\Reserved (bits 8-14) RA (bit 15)
1	Reserved (bits 0-6) IW (bit 7)/\Reserved (bits 8-14) AD (bit 15)
1	Retry count
1	Reserved
2	I/O manager port number
2	Transaction number
1	Hardware status length
1	Not used
20	Hardware status
1	Length of I/O manager data
1	ID of I/O manager
36	I/O manager-specific data

NOTES:

Hardware product number is the number of the device; for example, 7935.

Physical path description is the hardware path to the device; for example, 2/4.0.1 (2 = bus, 4 = channel, 0 = device adapter, and 1 = device). It is hardware dependent.

Logical device name is the LDEV number.

Device class identifier identifies the type of device, such as disk, tape drive, or printer.

Diagnostic message class specifies the reason for logging this error:

0: = Hardware event
1: = Software event
2: = Other

I/O manager status is the LLIO status from the driver. It gives the reason for the I/O error.

LAR: = Log all retries requested by I/O manager
RA: = Retry again - I/O manager attempts retry
IW: = I/O worked - Retry was successful
AD: = Auto-diagnostic requested by I/O manager

Retry count varies depending on the value of LAR. If LAR is true, then the retry count is the number for the nth retry. If LAR is false, it is the number of retries performed.

I/O manager port number is the IPC port number of the device manager. It is usually a negative number.

Transaction number is the number of the I/O request.

Hardware status length specifies how much of the hardware status field contains valid data.

Hardware status contains status bytes from the device. The field may contain up to 40 bytes of error information. The information is device dependent.

Length of I/O manager data specifies how much of the I/O manager specific data field contains valid data.

ID of I/O manager is the subsystem number.

I/O manager specific data is driver-specific data that relates to the I/O error. It can contain up to 72 bytes of information.

Physical mount/dismount record, type 112

Table 7-19 Physical Mount/Dismount Format

Length, in 16-bit Words	Record Content
1	Record type (112)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Mount/Dismount type
1	Volume type
2	Logical device number
1	MV table ID (bits 0-5)/Not used (6-15)
1	Vol ID (bits 0-7)/Not used (8-15)
2	Volume identification
8	Volume name
16	Volume set name

NOTES:

Mount/Dismount Values	Log Volume Types
`0` = Device- or user-initiated mount	`1` = Master volume
`1` = Device-initiated dismount	`3` = Loner volume
	`6` = Scratch volume
	`7` = Unknown volume

Logical mount/dismount record, type 113

Table 7-20 Logical Mount/Dismount Record Format

Length, in 16-bit Words	Record Content
1	Record type (113)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Mount/Dismount
1	Request type
8	User name
8	Group name
8	Account name
16	Volume set name
1	Number of volumes in set
1	Logical device of first volume
1	Logical device of next volume
1	Logical device of next volume
1	Logical device of next volume
1	Logical device of next volume
1	Logical device of next volume
1	Logical device of next volume
1	Logical device of next volume

NOTES:

Mount/Dismount	Request Types
`0` = Logical mount	`0` = User
`1` = Logical dismount	`1` = Operator

Tape labels record, type 114

Table 7-21 Tape Labels Record Format

Length, in 16-bit Words	Record Content
1	Record type (114)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Logical device number
1	File sequence number
1	File number (bits 0-7)/Sq type (bits 8, 9) /Type (bits 10, 11)/Reserved (bits 12-15)
1	Not used (bits 0-7)/Volume sequence number (bits 8-15)
1	Expiration date
9	File name/Not used (last 8 bits)
4	Lockword
3	Volume set ID
3	Volume ID
1	PIN *

* PIN of the process making the tape label request.

NOTES:

Sq Type (2 bits)

0: = Search for match on file name
1: = Next or default
2: = Add file to end of volume set
3: = Specified file sequence number

Type (2 bits)

2: = ANSI standard label
3: = IBM standard label

Console log record, type 115

Table 7-22 Console Log Record Format

Length, in 16-bit Words	Record Content
1	Record type (115)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Byte length of console line
Up to 140	Console input or output line

* If length is less than zero, console message is input. If length is greater than zero, console message is output.

Program file event record, type 116

Table 7-23 Program File Event Record Format

Length, in 16-bit Words	Record Content
1	Record type (116)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Event type
1	Delta P
1	Status
25	Program file name
2	Native mode offset
1	Type (bits 0-3)/Calling location (bits 4-15)

NOTES:

This record appears only during execution of unusual Compatibility Mode code to provide a trap warning, or from the Run-Time Event Monitor (compatibility mode process).

Event Type

<0 = Compatibility mode trap warning
>0 = Run-time event monitor (RTEM) error

Native Mode Offset:

Applicable only for negative event type numbers.

Calling Location

Applicable only for positive event type numbers.

Type

0 = System SL
1 = Pub SL
2 = Group SL
3 = Program file

Bits 4-12 = Segment number

NMS spoolfile done log record, type 120 (input)

Table 7-24 Spoolfile Done Log Record Format (Input)

Length, in 16-bit Words	Record Content
1	Record type (120)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
4	User name
4	Reserved
4	Account name
4	Reserved
4	Job name
4	Reserved
4	File name
4	Reserved
2	Job type/job number
2	Spoolid (all of word 1, bits 0-14 of word 2)/I/O (bit 15 of word 2)
4	Device name
4	Reserved
2	Number of records in spoolfile
2	Number of sectors in spoolfile
1	Device type (bits 0-7)/Device subtype (bits 8-15)
1	Reserved (bits 0=7)/All 0s (bits 8-15)
1	All 0s
1	All 0s (bits 0-7)/Reserved (bits 8-11)/File disposition (bits 12-15)
2	All 0s

NMS spoolfile done log record, type 120 (output)

Table 7-25 Spoolfile Done Log Record Format (Output)

Length, in 16-bit Words	Record Content
1	Record type (120)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
4	User name
4	Reserved
4	Account name
4	Reserved
4	Job name
4	Reserved
4	File name
4	Reserved
2	Job type/job number
2	Spoolid (all of word 1, bits 0-14 of word 2)/I/O (bit 15 of word 2)
4	Device name
4	Reserved
2	Number of records processed
2	Number of sectors in spoolfile
1	Device type (bits 0-7)/Device subtype (bits 8-15)
1	Reserved (bits 0=7)/Output priority (bits 8-15)
1	Current copy number
1	Logical pages per physical page (bits 0-7)/Reserved (bits 8-11)/File disposition (bits 12-15)
2	Number of physical pages

NOTES:

Input spoolfile done log records are generated for every spoolfile that is generated.

One output spoolfile done log record is generated and added to the log records for every file copy (or partial file copy) that is printed.

The top two bits of the job type/job number field are the job type, which refers to the spoolfile, as follows:

00: = Spoolfile originally created by a session on another system or another startup of this system (S')
01: = Spoolfile created by a session on a startup of this system (S)
10: = Spoolfile created by a job on a startup of this system (J)
11: = Spoolfile originally created by a job on another system or another startup of this system (J')

I/O :: 0 = Input spoolfile
: 1 = Output spoolfile

Func :: 0 = Normal completion
: 1 = Delete spoolfile
: 2 = Defer spoolfile
: 3 = Relink spoolfile

Number of records processed may be greater than the number of records in the file if internal looping or powerfail occurs.

For serial printers, the number of physical pages is always 0.

Processor launch information log record, type 131

Table 7-26 Processor Launch Information Log Record Format

Length, in 16-bit Words	Record Content
1	Record type (131)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	Processor id
8	Hard physical address
8	Launch status

NOTES:

Each processor (except the one that is used to launch the system) logs a processor launch information record.

Processor id

Identifies the type of processor.

Hard physical address (HFA)

The hard physical address of the processor.

Launch status

1: = Can't create interrupt control stack; usually not enough memory.
-2: = Processor launch error; a hardware error.
-1: = Processor already configured.
0: = All OK.

Password changes log record, type 134

Table 7-27 Password Changes Log Record Format

Length, in 16-bit words	Record Content
1	Record type (134)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	Target user name
8	Target group name
8	Target account name
1	Type changed
1	Input LDEV number
25	Executed from
3	Reserved
8	User name
8	Group name
8	Account name
8	Job/session name

System logging configuration record, type 135

Table 7-28 System Logging Configuration Record Format

Length, in 16-bit words	Record Content
1	Record type (135)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	(Reserved)
1	LDEV number
4	System logging masking words
8	User name
8	Group name
8	Account name
8	Job/session name

Restore log record, type 136

Table 7-29 Restore Log Record Format

Length, in 16-bit words	Record Content
1	Record type (136)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	File name
8	File group
8	File account
8	Creator
17	Volume identification
1	Access type
8	User name
8	Group name
8	Account name
8	Job/session name

Restore log record, type 236

The type 236 record has a "maximum path exceeded" flag.

The type 236 record is only used by native mode RESTORE since compatibility mode RESTORE uses only MPE name syntax. Compatibility mode RESTORE continues to use the type 136 record.

Table 7-30 “Record Type 236” illustrates the 236 record type.

Table 7-30 Record Type 236

Length, in 16-bit words	Record Content
2	Record type 236
2	Event version
2	Record length
2	PIN
4	Job type/Job number
4	Time stamp time
2	Time stamp date
2	Login type (If , logon name is in the format 16-byte user 16-byte acct)
36	Logon name
16	Job/Session name
8	Reserved
16	Creator user name ( `user.account` for new file names )
34	Volume ID
2	Access type
2	"Maximum path exceeded" flag
##	Variable-length buffer (file name terminated by a 0)

NOTES:

The restore log record traces file restorations. Files can be restored from tape or serial disk. This logging record can be enabled by SYSGEN, followed by a START command.

Printer access failure log record, type 137

Table 7-31 Printer Access Failure Log Record Format

Length, in 16-bit words	Record Content
1	Record type (137)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
2	Creator job number
8	Creator job name
8	Creator user name
8	Creator account name
25	Spoolfile name
8	Target device name/class
1	(Reserved)
2	File size
1	Status
8	User name
8	Group name
8	Account name
8	Job/session name

NOTES:

This log keeps track of failed attempts attaching spoolfiles to printers. New spoolfiles, which are logged by FOPEN as event #144, are not logged here.

This log is initially disabled, but can be enabled by SYSGEN, followed by a START command.

ACD changes log record, type 138

Table 7-32 ACD Changes Log Record Format

Length, in 16-bit words	Record Content
1	Record type (138)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
25	Target object name
25	Source object name
4	Function
25	Executed from
2	Status
8	User name
8	Group name
8	Account name
8	Job/session name

Type 238

The format of the ACD record has been modified to handle variable-length file names and hierarchical pathnames. The target object name and the source object name fields are variable in length to handle files with expanded names.

Table 7-33 “Record Type 238” illustrates the format of the type 238 record.

Table 7-33 Record Type 238

Length, in 16-bit words	Record Content
2	Record type 238
2	Event version
2	Record length
2	PIN
4	Job type/Job number
4	Time stamp time
2	Time stamp date
2	Login type (If 1, logon name is in the format 16-byte user 16-byte acct)
36	Logon name
16	Job/Session name
8	Reserved
8	ACD function
4	Status
##	Variable-length buffer

NOTES:

This log type is activated when ACDs are changed (created, deleted, copied, or modified) with MPE commands or intrinsics.

The log can be enabled by SYSGEN, followed by a START command.

Job stream initiation log record, type 139

Table 7-34 Stream Initiation Log Record Format

Length, in 16-bit words	Record Content
1	Record type (139)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
1	Input LDEV
25	Job file name
2	Job logon Job/session number
8	Job logon user
8	Job logon group
8	Job logon account
8	Job name
2	Input spoolfile ID
1	Scheduled date
2	Scheduled time
8	User name
8	Group name
8	Account name
8	Job/session name

User logging record, type 140

Table 7-35 User Logging Record Format

Length, in 16-bit words	Record Content
1	Record type (140)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
25	Program file name
4	Intrinsic
2	Index
4	LOG ID*
1	Mode
1	Status
8	User name
8	Group name
8	Account name
8	Job/session name

*The LOG ID field in the log record contains "XXXXXX" for the CLOSELOG intrinsic when the index is bad.

NOTES:

The user logging record log keeps track of all OPENLOG and CLOSELOG intrinsic calls. The system manager can use it to see who accesses, or tries to access, the user logging facility.

This log is initially disabled, but can be enabled by SYSGEN, followed by a START command.

Process creation log record, type 141

Table 7-36 Process Creation Record Format

Length, in 16-bit words	Record Content
1	Record type (141)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
25	File name
1	(Reserved)
2	Priority
2	Process Space ID
4	Parent PID
2	NM_Heap_Size
2	Capabilities mask*
8	(Reserved)
8	User name
8	Group name
8	Account name
8	Job/session name

*The capabilities mask is read as follows:

     User              File access          Program/group

bit    capability    bit   capability      bit   capability

 0        SM          6       CV            23      BA

 1        AM          7       UV            24      IA

 2        AL          8       LG            25      PM

 3        GL          9       SP            28      MR

 4        DI         10       PS            30      DS

 5        OP         11       NA            31      PH

                     12       NM

                     13       CS

                     14       ND

                     15       SF

Internal Data Structure, type 242

The data structure of log record type 242 for Security Configuration Changes is as follows:

Table 7-37 Internal Data Structure

Length, in 16-bit words	Record Content
1	Record type (242)
1	Event Version (1)
1	Record length
1	PIN
2	Job type/job number
2	Time stamp time
1	Time stamp date
1	Login type
18	Logon name format
8	Job/session name
8	Future place of the UID & GID
20	Security Configuration feature
20	Old value
20	New Value

Change group record, type 143

Table 7-38 Change Group Record Format

Length, in 16-bit Words	Record Content
1	Record type (143)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	Old group name
8	New group name
2	CPU time
2	Connect time

File open record, type 144*

Table 7-39 File Open Record Format

Length, in 16-bit Words	Record Content
1	Record type (144)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
8	User name
8	User's account name
8	User's logon group name
2	User ID
8	File name
8	File group name
8	File account name
8	File creator name
10	File UFID
2	File number
1	Foptions
1	File code
1	Reserved (bits 0-5)/Access privileges (bits 6-7)/ Security mask (bits 8-15)
1	Reserved
2	HPE status
2	Object size (current)
2	File Limit
3	File descriptor
7	Reserved

File open record, type 244

The file creator name has been modified to log the "user.account" string instead of just the user string for files that are created.

Table 7-40 “Record Type 244” illustrates the format of record type 244.

Table 7-40 Record Type 244

Length, in 16-bit Words	Record Content
1	Record type 244
1	Event version
1	Record length
1	PIN
2	Job type/Job number
2	Time stamp time
1	Time stamp date
1	Login type (If 1, logon name is in the format 16-byte user 16-byte acct)
18	Logon name
8	Job/Session name
4	Reserved
10	UFID
2	File number
1	Foptions
1	File code
2	File domain
2	File record format
2	File type
6bit	Reserved
2bit	Access priv level
8bit	MPE security mask
2	Open status
2	Object size
2	File limit
3	File descriptor
8	File creator (user.account for new files)
2	"Maximum path exceeded" flag
##	Variable length name buffer (format: file name0 )

The file open record is only logged when an error is detected during FOPEN; therefore, the values in the record are not always valid. Specifically, values in the File Limit and Object Size fields are only valid after an error is detected during FOPEN.

Configurable Command Logging

Through the Security Configuration Utility, system managers can specify which MPE commands, when executed, are to be logged by the system logging facility. Log record type 245 will be used to log command execution and its status.

The default setting for this system logging event is "ON".

Table 7-41 Record Type 245

Length, in 16-bit Words	Record Content
1	Record type 245
1	Event version
1	Record length
1	PIN
2	Job type/Job number
2	Time stamp time
1	Time stamp date
1	Login type (If 1, logon name is in the format 16-byte user 16-byte acct)
18	Logon name
8	Job/Session name
8	Reserved
1	CIERR
1	stdin Ldev
14	Program file name or CI
1	Command Length
140	Command image (variable length)

Maintenance Request Record Format, type 146

Table 7-42 Maintenance Request Record Format

Length, in 16-bit Words	Record Content
1	Record type (146)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
20	Device ID
20	PDEV
20	LDEV
2	Format ID
2	Log type
2	Head - reserved
948	Data

NOTES:

Field	Length (Bytes)	Description
Device ID	32	Identifies the device; for example, HP7935 (+8 bytes for Pascal string).
PDEV	32	Physical path to the device; for example, 8.0.0 (+8 bytes for Pascal string).
LDEV	32	Logical device file name (+8 bytes for Pascal string).
Format ID	4	1 = data is HP-IB format
		2 = data is FLEX format
		3 = data is NIO format
Logtype	4	0 = no data; no logging errors found
		101 = data is a run-time error data log record
		102 = data is a fault error data log record
Head/Reserved	4	101 = head number
		0 or 102 = reserved
Data	1896	Up to 1896 bytes are allowed

Diagnostic information records, type 150

Table 7-43 Auto-Diagnostic Record Format

Length, in 16-bit Words	Record Content
1	Record type (150)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
2	Type number
16	Hardware product number
16	Physical path description
16	Logical device name
1	Device class identifier
50	Diagnostic messages

NOTES:

There are two different formats for type 150 diagnostic information records: one is the auto-diagnostic record format and the other is the diagnostic system information record format. You can determine which format is used by looking at the type number field just after the header.

Type Number

0 = Auto-diagnostic record format
3 = Diagnostic system information record format

In the diagnostic messages field, a continuation flag indicates whether another related message was placed into the log file.

Diagnostic system information record, type 150

Table 7-44 Diagnostic System Information Record Format

Length,in 16-bit Words	Record Content
1	Record type (150)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
2	Type number
Up to 128	Diagnostic system messages or status information

NOTES:

Type Number

*0 = Auto-diagnostic record format
*3 = Diagnostic system information record format

The diagnostic system information can include information about which users requested single-user mode (SUM). It can also record internal diagnostic system errors detected when no user exists to report them to. This can occur when an I/O error is logged, for example.

High-priority machine check, type 151

Table 7-45 High-Priority Machine Check Record Format

Length, in 16-bit Words	Record Content
1	Record type (151)
1	Record length
1	Process identification number
3	Time stamp
2	Job type (bits 0-1)/job number (bits 2-15 of word 1, bits 0-15 of word 2)
2	Hardware ID
2	Number of bytes in record
2	GR 0
2	:
2	GR31
2	CR0
2	:
2	CR31
2	SR0
2	:
2	SR7
2	Interrupting instruction address space
2	Interrupting instruction address offset
2	0 Check type word (bits 0-4 of word 1)/Reserved (bits 5-15 of word 1, bits 0-15 of word 2)
2	0 CPU state word (bits 0-5 of word 1)/Reserved (bits 6-15, bits 0-12 of word 2)/Past OK (bit 13 of word 2)/Error cleared (bits 14-15 of word 1, all word 2)
2	0 Detected by word (bits 0-2 of word 1)/Reserved (bits 3-15 of word 1, all word 2)
2	0 Cache check word (bits 0-3 of word 1)/Reserved (bits 4-15 of word 1, all word 2)
2	0 TLB check word (bits 0-4 of word 1)/Reserved (bits 5-15 of word 1, all word 2)
2	0 Bus check word (bits 0-9 of word 1)/Reserved (bits 10-15, all word 2)
2	0 Assist check word (bits 0-2 of word 1)/Reserved (bits 3-15 of word 1, all word 2)
2	0 Processor check word - reserved
2	Reserved (all word 1, bits 0-12 of word 2)/Assist ID word (bits 13-15 of word 2)
Varies	System-dependent portion of PIM

NOTES:

Fields starting with GR0 to the end of the record contain processor internal memory (PIM). Record type 151 contains HPMC PIM and record type 152 contains LPMC.

The first PIM fields contain information from the registers (such as general registers, GR0-31, and control registers, CR0-31). The length of the last PIM field (system-dependent portion of PIM) is hardware dependent. However, the total length of a logging record is restricted to 2KB. Refer to the appropriate hardware manuals for more information.

The nature of a high-priority machine check is passed by setting nonzero values in the appropriate fields of the record. The layout of these error parameters is as follows:

Check type word

Bits	Definition
0:1	Cache system check
1:1	TLB check
2:1	Bus transaction check
3:1	Assists check
4:1	Processor internal check

CPU state word

Bits	Definition
0:1	Interrupting instruction address queue valid
1:1	Interrupting instruction address queue fault
2:1	IPRs valid
3:1	General registers valid
4:1	Control registers valid
5:1	Space registers valid

Detected by word

Bits	Definition
0:1	Instruction fetch
1:1	Load
2:1	Load and clear
3:1	Store
4:1	Flush I-cache
5:1	Flush D-cache
6:1	Purge D-cache
7:1	Copyout of dirty cache line
8:1	Instruction prefetch
9:1	Data prefetch
10:1	Remote cache consistency check
11:1	Local purge TLB
12:1	Remote purge TLB
13:1	Probe read access
14:1	Probe write access
15:1	Coprocessor operation
16:1	SFU operation
17:1	Insert I or D TLB protection or access

Cache check word

Bits	Definition
0:1	I-cache check
1:1	D-cache check
2:1	Tag check
3:1	Data check

TLB check word

Bits	Definition
0:1	I-TLB check
1:1	D-TLB check

Bus check word

Bits	Definition
0:1	Address error
1:1	Data slave error
2:1	Data parity error
3:1	Data protocol error
4:1	Read transaction
5:1	Write transaction
6:1	Memory space transaction
7:1	I/O space transaction
8:1	Processor was master in transaction
9:1	Processor was slave in transaction

Assists check word

Bits	Definition
0:1	Coprocessor check
1:1	SFU check
2:1	Assist ID valid

Processor check word

All fields of this word are currently reserved.

Assist ID word

The 3-bit unit ID field of the failing SFU or coprocessor is stored right-justified in bits 29:3 of the assist ID word.

Low-priority machine check, type 152

Table 7-46 Low-Priority Machine Check Record Format

Length, in 16-bit Words	Record Content
1	Record type (152)
1	Record length
1	Process identification number
3	Time stamp
2	Job type (bits 0-1)/job number (bits 2-15 of word 1, bits 0-15 of word 2)
2	Hardware ID
2	Number of bytes in record
2	GR 0
2	:
2	GR31
2	CR0
2	:
2	CR31
2	SR0
2	:
2	SR7
2	Interrupting instruction address space
2	Interrupting instruction address offset
2	0 Check type word (bits 0-4 of word 1)/Reserved (bits 5-15 of word 1, bits 0-15 of word 2)
2	0 CPU state word (bits 0-5 of word 1)/Reserved (bits 6-15, bits 0-12 of word 2)/Past OK (bit 13 of word 2)/Error cleared (bits 14-15 of word 1, all word 2)
2	0 Detected by word (bits 0-2 of word 1)/Reserved (bits 3-15 of word 1, all word 2)
2	0 Cache check word (bits 0-3 of word 1)/Reserved (bits 4-15 of word 1, all word 2)
2	0 TLB check word (bits 0-4 of word 1)/Reserved (bits 5-15 of word 1, all word 2)
2	0 Bus check word (bits 0-9 of word 1)/Reserved (bits 10-15, all word 2)
2	0 Assist check word (bits 0-2 of word 1)/Reserved (bits 3-15 of word 1, all word 2)
2	0 Processor check word - reserved
2	Reserved (all word 1, bits 0-12 of word 2)/Assist ID word (bits 13-15 of word 2)
Varies	System-dependent portion of PIM

NOTES:

The fields in this record are the same as the corresponding fields in the high-priority machine check record (type 151). See the notes following the record.

CM file close record, type 160

Table 7-47 CM File Close Record Format

Length, in 16-bit Words	Record Content
1	Record type (160)
1	Record length
1	Process identification number
3	Time stamp
2	Job type/job number
13	File name - format of fname.group.acct
1	Reserved
1	Disposition (bits 0-7)/Domain (bits 8-15)
2	Number of sectors allocated
1	Device type (bits 0-7)/Unused (bits 8-15
2	Number of records transferred
2	Number of blocks transferred
1	Logical device number

NOTES:

Close Disposition (bits 13:3)	Open Domain
`0` No change	`0` New file
`1` Save permanent	`1` Old permanent file
`2` Save temporary - rewound	`2` Old temporary file
`3` Save temp - not rewound	`3` Old job or sys
`4` Delete
`5` Make temporary

Disk Space Disposition (bits 11:2)

`0`	Do not return disk space allocated beyond EOF.
`1`	Return disk space allocated beyond EOF to system; EOF becomes file limit.
`2`	Return disk space allocated beyond EOF to system; file limit remains the same (NM file types only).

The Disposition field in a CM file close record can have values from 0-4, 8-12, and 255. Any files left open during process termination are closed by the system and given a disposition of 255.

System Log Record Formats

Technical documentation

» Table of Contents

» Index

Log failure record, type 100

System up record, type 101

Job initiation record, type 102

Logon queue

CPU time limit

MPE/iX status

Job termination record, type 103

Process termination record, type 104

NM File close record, type 105

NM File close record, type 205

Unique file identifier (UFID)

Disposition field

Shutdown record, type 106

Power failure record, type 107

I/O error record, type 111

Physical mount/dismount record, type 112

Logical mount/dismount record, type 113

Tape labels record, type 114

Console log record, type 115

Program file event record, type 116

NMS spoolfile done log record, type 120 (input)

NMS spoolfile done log record, type 120 (output)

Processor launch information log record, type 131

Password changes log record, type 134

System logging configuration record, type 135

Restore log record, type 136

Restore log record, type 236

Printer access failure log record, type 137

ACD changes log record, type 138

Type 238

Job stream initiation log record, type 139

User logging record, type 140

Process creation log record, type 141

Internal Data Structure, type 242

Change group record, type 143

File open record, type 144*

File open record, type 244

Configurable Command Logging

Maintenance Request Record Format, type 146

Diagnostic information records, type 150

Diagnostic system information record, type 150

High-priority machine check, type 151

Check type word

CPU state word

Detected by word

Cache check word

TLB check word

Bus check word

Assists check word

Processor check word

Assist ID word

Low-priority machine check, type 152

CM file close record, type 160