The IBM® supplied model for the primary job log file is QAMHJLPR in library QSYS. The primary record format is QMHPFT.
A detailed description of this format follows:
Field Order | Field Name | Data Type | Length in Bytes | Field Description |
---|---|---|---|---|
1 | QMHJDT | DATE | 10 | Date job log created |
2 | QMHJTM | TIME | 8 | Time job log created |
3 | QMHMRK | CHAR | 4 | Message reference key |
4 | QMHTYP | CHAR | 10 | Message type |
5 | QMHSEV | BIN | 4 | Message severity |
6 | QMHMID | CHAR | 7 | Message ID |
7 | QMHDAT | DATE | 10 | Message sent date |
8 | QMHTIM | TIME | 8 | Message sent time |
9 | QMHMF | CHAR | 20 | Message file name |
10 | QMHRPY | CHAR | 4 | Reply reference key |
11 | QMHRQS | CHAR | 1 | Request Message Status |
12 | QMHSTY | CHAR | 1 | Sending program type |
13 | QMHRTY | CHAR | 1 | Receiving program type |
14 | QMHSSN | BIN | 4 | Number of statements for sending program |
15 | QMHRSN | BIN | 4 | Number of statements for receiving program |
16 | QMHCID | BIN | 4 | CCSID of the message data or immediate message |
17 | QMHPRL | CHAR | 1 | Message percolated indicator |
18 | QMHSPR | VAR CHAR | 256 MAX | Sending procedure name |
19 | QMHSMD | CHAR | 10 | Sending module name |
20 | QMHSPG | CHAR | 12 | Sending program name |
21 | QMHSLB | CHAR | 10 | Sending library name |
22 | QMHSTM | CHAR | 30 | Statement number(s) for sending program |
23 | QMHRPR | VAR CHAR | 256 MAX | Receiving procedure name |
24 | QMHRMD | CHAR | 10 | Receiving module name |
25 | QMHRPG | CHAR | 10 | Receiving program name |
26 | QMHRLB | CHAR | 10 | Receiving program library name |
27 | QMHRTM | CHAR | 30 | Statement number(s) for receiving program |
28 | QMHSYS | CHAR | 8 | System name |
29 | QMHJOB | CHAR | 26 | Qualified Job name |
30 | QMHMDT | VAR CHAR | 3000 MAX | Message data or immediate message |
31 | QMHCSP | VAR CHAR | 4096 MAX | Complete sending procedure name |
32 | QMHCRP | VAR CHAR | 4096 MAX | Complete receiving procedure name |
33 | QMHLSP | VAR CHAR | 6144 MAX | Long sending program name |
34 | QMHTID | CHAR | 8 | Thread |
35 | QMHMSC | ZONED | 6,0 | Microseconds |
36 | QMHFUS | CHAR | 10 | From user |
The definition of the fields in this record are as follows:
The date the production of the job log began. The field is a date field in the database record. The format of the date is *ISO. A value in this date field is in the format yyyy-mm-dd. Each record produced for the same job log will have the same value in this field.
The time the production of the job log began. This field is defined as a time field in the database record. The format of the time is defined to be *ISO. A value in this time field is in the format hh.mm.ss. Each record produced for the same job log will have the same value in this field.
The message reference key the related message had in the job message queue. The records are placed in the primary database file in strictly ascending sequence by message reference key. Within the set of records produced for a single job log, this field is unique for each record and thus can be used as a unique key for the record. If the records for two or more job logs are placed into the same member, the key may no longer be unique.
The severity the message has. This is a value from 0 through 99.
The message ID for the message. This field will contain the special value *IMMED if the message is an immediate message which has no message ID.
The date the message was sent. This field is defined as a date field in the database record. The format of the date is *ISO. A value in this field is in the format yyyy-mm-dd.
The time the message was sent. The field is defined as a time field in the database record. The format of the time is defined to be *ISO. A value in this field is in the format hh.mm.ss.
The name of the message file that is to be used to obtain the message description for the message. The first 10 characters of the field contain the message file name. The second 10 characters contain the library name. If the field QMHMID contains *IMMED to indicate an immediate message, this field will contain all blanks.
In order to maintain the strictly ascending sequence by message reference key, the record for the reply message may not immediately follow the record for the inquiry, notify, or sender's copy message.
An indicator with the following values that shows whether the sending program was an OPM program or an ILE program.
An indicator with the following values that shows the type of the receiving program:
The number of statement numbers for sending program.
The value provided in this field defines how many statement numbers are in the field QMHSTM.
The number of statement numbers for receiving program.
The CCSID of the message data or immediate message that is contained in the field QMHMDT.
An indicator that shows whether the message was percolated to the receiving program or not.
Message percolation can only occur within an ILE program. Therefore, this field contains a one only if the receiving program type field QMHRTY contains a one ('F1'X) or a two ('F2'X).
This field can contain a nested procedure name for a sending program type of one ('F1'X) or two ('F2'X); each procedure name is separated by a colon. The outer-most procedure name is identified first and is followed by the procedures contained in it. The inner-most procedures are identified last in the string.
The name of the library that the sending program was contained in.
The statement number(s) at which the sending program sent the message. Each statement number is 10 characters in length.
This field can contain a nested procedure name for a receiving program type of one ('F1'X) or two ('F2'X); each procedure name is separated by a colon. The outer-most procedure name is identified first and is followed by the procedures contained in it. The inner-most procedures are identified last in the string.
The program name of the OPM or ILE program to which the message was sent.
The name of the library that the receiving program was in.
The statement number(s) at which the receiving program was stopped when the message was sent. Each statement number is 10 characters in length.
The name of the system that the job log was produced on.
The fully qualified name of the job for which the message is being logged for. The first 10 positions contain the job name, the next 10 positions the user name, and the last six positions the job number.
If the field QMHMID contains the special value *IMMED, this field contains an immediate message. Otherwise, this field contains the message data that was used when the message was sent. This field can contain a maximum of 3000 characters. If the immediate message or message data is longer, it is truncated to 3000 characters.
If the message data contains pointers, the pointers is invalidated before the message data is written to the database file.
This field can contain a nested procedure name where each procedure name is separated by a colon. The outer-most procedure name is identified first and is followed by the procedures contained in it. The inner-most procedures are identified last in the string.
The field can contain a nested procedure name where each procedure name is separated by a colon. The outer-most procedure name is identified first and is followed by the procedures contained in it. The inner-most procedures are identified last in the string.
This field contains the entire sending program name from which the message was sent for all sending program types. The name can be a maximum of 6144 characters in length.
This field identifies the thread within the job that sent the message.
This is the microseconds portion of the time the message was sent. It can be used to determine with more precision the time the message was sent.
The name of the user profile that the thread was running under when the message was sent.
The IBM supplied model for the secondary job log file is QAMHJLSC in library QSYS. The secondary record format name is QMHSFT. A detailed description of the secondary record format follows:
Field Order | Field Name | Data Type | Length in Bytes | Field Description |
---|---|---|---|---|
1 | QMHJDS | DATE | 10 | Date job log created |
2 | QMHJTS | TIME | 8 | Time job log created |
3 | QMHMKS | CHAR | 4 | Message reference key |
7 | QMHSYN | CHAR | 8 | System name |
8 | QMHJBN | CHAR | 26 | Qualified job name |
4 | QMHLNN | BIN | 4 | Message line number |
5 | QMHSID | BIN | 4 | CCSID of text line |
6 | QMHTTY | CHAR | 1 | Message text indicator |
9 | QMHLIN | CHAR | 78 | Message text line |
The length of the field indicates the number of total bytes for the field.
The definition of the fields in this record are as follows:
The date the production of the job log began. The field is a date field in the database record. The format of the date is *ISO. A value in this field is in the format yyyy-mm-dd. Each record produced for the same job log will have the same value in this field.
The time the production of the job log began. This field is defined as a time field in the database record. The format of the time is defined to be *ISO. A value in this field is in the format hh.mm.ss. Each record produced for the same job log will have the same value in this field.
The message reference key the related message had in the job message queue. The records are placed in the secondary database file in ascending sequence by message reference key. There can be more than one secondary record for a specific message reference key. This field also exists in the related primary record. Therefore, once the message reference key is obtained from a primary record, it can be used to read the related records from the secondary file.
The name of the system that the job log was produced on.
The fully qualified name of the job for which the message is being logged for. The first 10 positions contain the job name, the next 10 positions the user name, and the last six positions the job number.
The line number of the line within the text type. For both the first and second level text, the line number starts at one for the first line of the text and is incremented by one for each additional line within that level.
The CCSID of the message text line that is contained in field QMHLIN.
An indicator which specifies whether field QMHLIN contains a line of the first or second level text. This field will contain one of the following values:
This field contains one line of the first or second level text.