The Major Type 1, Minor Type 25 (File Statistics) entry contains information for processes using anonymous file accounting. For further information, refer to “Using Anonymous Task and File Accounting” in Section 1.
Use the FILE option in LOGANALYZER to obtain a list of these entries as well as open, close, and interval file entries.
Table 5–23. Major Type 1–Minor Type 25 (LOGMIN_FILESTATSV)
Word Field Value Description
0–3 As described in Table 2–2, “First Four Log Entry Words Version 1 Format”
4 Number of disk files used 5 Elapsed I/O time for disk files
6 Transaction count (number of logical I/O operations) for disk files
7 Physical read count for disk files 8 Physical write count for disk files 9 Number of nondisk files used 10 Elapsed I/O time for nondisk files
11 Transaction count (number of logical I/O operations) for nondisk files
12 Physical read count for nondisk files 13 Physical write count for nondisk files
Major Type 1 – Job or Task Entry
Major Type 1–Minor Type 26 (Program Event)
The Major Type 1, Minor Type 26 (Program Event) entry contains the following information:
• The resources used by the program dump, if a task has initiated a program dump. • The resources used by the sort operations, if a task uses the SORT intrinsic. • The amount of elapsed time that the program waited, if a task resumes after it has
been waiting for a response to an AX system command.
• The amount of elapsed time that the task waited, if a task resumes after being suspended because of an RSVP request.
For example, if a program is waiting for an input file with an RSVP message and the file becomes available, a log entry is generated that records the amount of elapsed time that the task was waiting.
Use the STATUS option in LOGANALYZER to obtain information about these log entries.
The following table describes the format and contents of this entry.
Table 5–24. Major Type 1–Minor Type 26 (LOGMIN_TASKSTATUSV)
Word Field Value Description
0–3 As described in Table 2–2, “First Four Log Entry Words Version 1 Format”
4 LINK to name of program (standard form).
5 The I/O time that was used by the program because of the event.
6 Effective processor time. This is the apparent time a processor was in use by a task. This value is returned by the ?TI and the A operator commands.
Effective time includes processor resources used for the task and processor throttling associated with the performance level.
The normalized processor time is returned in word 14. Refer to the description of word 14 for further details.
7 The elapsed time required for the program event. 8 The number of initial p-bits used by the program
because of the event.
9 Effective initial p-bit time. This is the apparent time a processor was handling initial p-bits for a task. Effective time includes processor resources used for the task and processor throttling associated with the performance level.
The normalized initial p-bit time is returned in word 15. Refer to the description of word 15 for further details.
Table 5–24. Major Type 1–Minor Type 26 (LOGMIN_TASKSTATUSV)
Word Field Value Description
1 The program has completed a program dump to disk. 2 The program has completed a program dump to
printer.
3 The program was suspended on an RSVP message and has resumed.
4 The program has completed a call on the SORT intrinsic.
5 The program has resumed after waiting for an AX response from the operator.
6 The memory dump was unloaded to a MEMORY/DUMP tape.
7 The memory dump was unloaded to a raw DP file on disk.
8 The memory dump was unloaded and processed as a SAVEDUMP.
11 The stack number of the process.
12 LINK to Electronic Service Request information. (Refer to the information following this table for the format of the Electronic Service Request data.) 13 Program or memory dump name LINK word
(standard form).
14 Normalized processor time. This reflects the processor resources used by a task, independent of the performance level of the processor.
Normalized processor time is expressed in constant- value processor seconds that are not affected by the actual performance level of the processor. This time is an estimate and might have a small margin of error. The normalized processor time can be used with back-end process billing.
On MCPvm systems, normalized processor time is equal to the effective processor time returned in word 6. On all other systems, normalized processor time is returned.
Major Type 1 – Job or Task Entry
Table 5–24. Major Type 1–Minor Type 26 (LOGMIN_TASKSTATUSV)
Word Field Value Description
15 Normalized initial p-bit time. This reflects the processor resources used by a task, independent of the performance level of the processor.
Normalized initial p-bit time is expressed in constant- value processor seconds that are not affected by the actual performance level of the processor. This time is an estimate and might have a small margin of error. The normalized time can be used with back-end process billing.
On MCPvm systems, normalized initial p-bit time is equal to the effective initial p-bit time returned in word 9. On all other systems, normalized initial p-bit time is returned.
16–end Variable data pointed to by the LINKs in this record.
The Electronic Service Request data in the SUMLOG record contains information identifying the software product that might have caused the event leading to the creation of the SUMLOG record. Words 12 and 13 are only used for event type equal to 1 (program dump to disk) or types 6-8 (memory dump unloaded). The format of the variable length data is a string of character data resembling an MCP system file title. For all affected records, the Electronic Service Request data has the following format:
Word Field Value Meaning
0 Options word [47:39] Reserved
[08:01] 0 Electronic Service Request information present 1 No Electronic Service Request information present [07:08] Version (currently=1)
1–n Four-node display form name node 1 – application node 2 – product node 3 – component node 4 – product level