Layouts for variable-length portion of journal entries
The following tables contain the variable-length portion of the layouts for journal entries.
Allow use with partial transactions (F MO) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Reason code | Char (1) |
|
2 | Reserved | Char (3) | Reserved. Set to zeros. |
5 | Number commit IDs | Bin (32) | The number of commit identifiers. |
9 | Reserved | Char (72) | Reserved. Set to zeros. |
81 | Commit IDs | Bin (64) [*] | The array of commit cycle identifiers for partial transactions that remain in the object. |
APYJRNCHG (B AT, D DD, E EQ, F AY, Q QH, Y YH) and RMVJRNCHG (E EX, F RC) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Count or Relative Record Number (JOCTRR) | Zoned (10,0) | Contains the number of journal entries applied or removed. For *TYPE5 output files, the format of this field is Char (20). | |
Flag (JOFLAG) | Char (1) | The results of the apply or remove operation:
|
|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | First entry applied or removed | Zoned (10,0) | The sequence number of the first entry actually applied or removed. This field is set to -1 if the actual value is larger than 9 999 999 999. See the First entry applied or removed--large field for the actual value. |
11 | Last entry applied or removed. | Zoned (10,0) | The sequence number of the last entry actually applied or removed. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Last entry applied or removed--large field for the actual value. |
21 | Starting receiver name | Char (10) | The name of the first receiver from which entries were applied or removed. |
31 | Library name | Char (10) | The name of the library for the starting journal receiver. |
41 | Ending receiver name | Char (10) | The name of the last or ending receiver from which entries were applied or removed. |
51 | Library name | Char (10) | The library for the ending journal receiver. |
61 | Starting sequence number | Char (10) | The specified starting sequence number for the apply or remove operation. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Starting sequence number--large field for the actual value. |
71 | Ending sequence number | Char (10) | The specified ending sequence number for the apply or remove operation. This field is set to -1 if the actual value is larger than 9 999 999 999. See the Ending sequence number--large field for the actual value. |
81 | Incomplete commit transaction not applied or removed | Char (1) |
|
82 | First entry applied or removed--large | Char (20) | The sequence number of the first entry actually applied or removed. This field always contains a sequence number. |
102 | Last entry applied or removed--large | Char (20) | The sequence number of the last entry actually applied or removed. This field always contains a sequence number. |
122 | Starting sequence number--large | Char (20) | The specified starting sequence number for the apply or remove operation. This field always contains a sequence number. |
142 | Ending sequence number--large | Char (20) | The specified ending sequence number for the apply or remove operation. This field always contains a sequence number. |
162 | Number of entries | Char (20) | The number of entries that were applied or removed. |
182 | Partial transaction starting sequence number | Char (20) | Starting sequence number for any partial transactions that were removed. For integrated file system objects and data areas, this field is always zero. |
202 | Partial transaction ending sequence number | Char (20) | Ending sequence number for any partial transactions that were removed. For integrated file system objects and data areas, this field is always zero. |
222 | Number of partial transaction removed | Char (20) | Count of number of entries removed for partial transactions. For integrated file system objects and data areas, this number is always zero. |
242 | Object deleted | Char (1) | Indicates that the object was deleted during the apply or remove
operation.
|
243 | Object created | Char (1) | Indicates that the object was created during the apply operation.
|
244 | Early end | Char (1) | Indicates if the apply or remove operation ended early for
this object.
|
245 | Change not made | Char (1) | Indicates that a change was found for this object after an
early end to the apply operation.
|
246 | End reason code | Char (1) | Reason code for early end. See message MCH4801 for the possible values. |
247 | End message ID | Char (7) | The message identifier associated with an early end to the apply operation. |
254 | Error condition | Bin (31) | The error condition code associated with an early end to the apply operation. |
258 | Partial transactions remain | Char (1) | Indicates that partial transactions remain for this object.
|
259 | Partial transactions removed | Char (1) | Indicates that at least some partial transactions were removed
during the apply operation.
|
Auditing Change (E ZT, J ZT, Q ZT, Y ZT) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Audit value | Char (10) | Object audit value |
Change authority (E ZA, J ZA, Q ZA, Y ZA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
1 | User | Char (10) | The user profile or REFUSER on GRTUSRAUT command. |
11 | Authorization list | Char (10) | The name of the authorization list name. |
21 | Object existence authority | Char (1) |
|
22 | Object management authority | Char (1) |
|
23 | Object operational authority | Char (1) |
|
24 | Authorization list management authority | Char (1) | Blank if user does not have authorization list management authority to the object. |
25 | Authorization list *PUBLIC authority | Char (1) |
|
26 | Read authority | Char (1) |
|
27 | Add authority | Char (1) |
|
28 | Update authority | Char (1) |
|
29 | Delete authority | Char (1) |
|
30 | Exclude authority | Char (1) |
|
31 | Execute authority | Char (1) |
|
32 | Object alter authority | Char (1) |
|
33 | Object reference authority | Char (1) |
|
34 | Reserved | Char (4) | Reserved. |
38 | Operation type | Char (3) | Possible values are:
|
Change distribution queues (S CF) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for QSNADS journal. |
17 | Entry type | Char(2) | Always CF for distribution queue change. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user profile name associated with the job. |
146 | Job number | Zoned(6,0) | The job number. |
152 | Distribution queue | Char(16) | The distribution queue that was added, changed, or removed during configuration. |
168 | Network identifier | Char(8) | The system name of the remote system to which the distributions are sent. |
176 | Remote location | Char(8) | The name of the logical location in an APPN communications route where distributions are sent to a remote system. |
184 | Mode | Char(8) | The mode name further qualifies the remote location name. |
192 | Queue type | Char(2) |
The default is *NETATR. |
194 | Local location | Char(8) | Name used to identify your system to remote systems in the network. |
202 | Send queue | Char(1) | Specifies whether, when a SNADS receiver becomes active, a SNADS sender is started on the same connection (Y or N). |
203 | (Reserved area) | Char(6) | |
209 | Normal from time | Char(4) | The time specified to start sending distributions from the normal priority queue. |
213 | Normal to time | Char(4) | The time specified to stop sending distributions from the normal priority queue. |
217 | Normal force time | Char(4) | The time specified to send any distributions from the normal priority queue regardless of the queue depth. |
221 | Normal send depth | Char(3) | The queue depth specified to start sending distributions from the normal priority queue when that many distributions are queued. |
224 | High from time | Char(4) | The time specified to start sending distributions from the high priority queue. |
228 | High to time | Char(4) | The time specified to stop sending distributions from the high priority queue. |
232 | High force time | Char(4) | The time specified to send any distributions from the high priority queue regardless of queue depth. |
236 | High send depth | Char(3) | The queue depth specified to start sending distributions from the high priority queue when that many distributions are queued. |
239 | Function | Char(1) | Function (distribution queue change)
that was entered:
|
240 | Number of tries | Zoned (4,0) | The number of times the system should try to resend the distribution. |
244 | Number of minutes between tries | Zoned (4,0) | The elapsed time that should occur between retries. |
248 | (Reserved area) | Char(9) |
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry, including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for MSF entries. |
17 | Entry type | Char(2) | Always CF for MSF configuration change entries. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user profile name associated with the job. |
146 | Job number | Zoned(6,0) | The job number. |
152 | Program name | Char(8) | The name of the MSF program that made the journal entry. |
160 | Function identifier | Char(1) | Function that was being performed
when the entry was made. The possible values are:
|
161 | Data length | Zoned(5,0) | The length of the logged data. |
166 | Logged data | Char(256) | The data logged by MSF when the function
identifier is:
|
Change end of data (F CE) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Count or relative record number (JOCTRR) | Zoned (10,0) | The relative record number of the last record kept in the physical file member. |
Change journaled object attributes (B JA, D DJ, E EK, F JC, Q QF, Y YK) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Attribute changed | Char (1) | Identifies which journal attribute was changed:
|
2 | New attributes value | Char (10) | The new value for the attribute that changed. The valid values
for each attribute are as follows:
Note: Only the characters in the parenthesis appear in this field.
|
12 | Displacement to inherit rules | Bin(16) unsigned short integer | Displacement to inheritance rules, 0 if Attribute changed field is not '4'. |
Offset determined by Displacement to Inherit Rules | Inherit Rules | See Journal Inherit Rules |
Change library attributes (Y YA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Library type | Char (10) | blanks if *SAME |
11 | Create authority | Char (10) | blanks if *SAME |
21 | Create object auditing | Char (10) | blanks if *SAME |
Change object attribute (E ZB, D ZB, J ZB, Q ZB, Y ZB) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Number of records | Bin (4) | The number of variable length records that follow. |
5 | Key | Bin (4) | The field of an object attribute to change. See Change Object Description (QLICOBJD) API. |
9 | Length of data | Bin (4) | The length of the data used to change a specific field of an object attribute. |
13 | Data | Char (*) | The data used to change a specific field of an object attribute. |
Change primary group (E ZP, J ZP, Q ZP, Y ZP) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Old group | Char (10) | The name of the old primary group. |
11 | New group | Char (10) | The name of the new primary group. |
21 | Object existence authority | Char (1) |
|
22 | Object management authority | Char (1) |
|
23 | Object operational authority | Char (1) |
|
24 | Object alter authority | Char (1) |
|
25 | Object reference authority | Char (1) |
|
26 | Reserved | Char (10) | Reserved. Set to blank. |
36 | Authorization list management | Char (1) | Blank if user does not have authorization list management authority to the object. |
37 | Read authority | Char (1) |
|
38 | Add authority | Char (1) |
|
39 | Update authority | Char (1) |
|
40 | Delete authority | Char (1) |
|
41 | Execute authority | Char (1) |
|
42 | Reserved | Char (10) | Reserved. Set to blank. |
52 | Exclude authority | Char (1) |
|
53 | Revoke | Char (1) |
|
Change routing table and secondary system name table (S RT) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for QSNADS journal. |
17 | Entry type | Char(2) | Always RT for routing or secondary system name table change. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user-profile name associated with the job. |
146 | Job number | Zoned(6,0) | The job number. |
152 | Destination system name | Char(16) | The system name of the destination system that is routed to using this entry. If this entry is a secondary system name table change, this is the name of the secondary system name. |
168 | Service priority (see note) | Char(1) | The value that indicates the service
level priority value. This is currently used to maintain sequential
ordering of service level. The possible values are:
|
169 | Service level (see note) | Char(8) | The service level for which the entry
was made. When a routing table entry is added or changed, one entry
will be made for each service level. The possible values are:
|
177 | Distribution queue name (see note) | Char(16) | The name of the distribution queue used to forward distributions to the destination system using the service level specified by this routing table entry. |
193 | Hop count (see note) | Zoned(4,0) | The hop count specified to be assigned to an originating distribution. If this value is *DFT, then the current system default hop count at the time of the distribution is used. |
197 | Description | Char(50) | Text description of this routing or secondary system name table entry. |
247 | Table | Char(1) | The table that was changed when this
entry was made.
|
248 | Function | Char(1) | Function (routing or secondary system
name table change) that was entered:
|
249 | (Reserved area) | Char(25) |
CHGJRN (J NR, J PR) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Count or relative record number (JOCTRR) | Zoned (10,0) | Contains the number of receivers attached or detached. | |
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | First receiver name | Char (10) | The name of the first receiver that is attached or detached. |
11 | First receiver library name | Char (10) | The name of the library for the first receiver that is attached or detached. |
21 | Dual receiver name | Char (10) | The name of the dual receiver that is attached or detached. Blank if only one receiver is used for the journal. |
31 | Dual receiver library name | Char (10) | The name of the library for the dual receiver that is attached or detached. Blank if only one receiver is used for the journal. |
COMMIT (C CM) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Count or relative record number (JOCTRR) | Zoned (10,0) | Contains the length of the commit identification. | |
Flag (JOFLAG) | Char (1) | Whether the commit operation was initiated by the system or
the user:
|
|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Commit ID | Char (*) | Contains the commit identification specified by the operation. The Count field specifies the length of this field. |
Completed distributions (S LG) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for QSNADS journals |
17 | Entry type | Char(2) | Always LG for SNADS distributions entered. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Program name | Char(8) | The name of the program that made the journal entry. |
134 | Job name | Char(10) | The name of the job that caused the entry to occur. |
144 | User name | Char(10) | The user-profile name associated with the job. |
154 | Job number | Zoned(6,0) | The job number. |
160 | Origin system name/group | Char(16) | The system name/group of the system that the distribution originated on. |
176 | Origin user ID/address | Char(16) | The user ID/address that originated the distribution. This is not set if the distribution is a status distribution caused by a SNADS error. |
192 | Sequence number | Zoned(4,0) | The sequence number of the distribution entry. This is 0000 if the distribution is a status distribution. |
196 | Date/time stamp | Char(8) | A representation of the date and time of origin of the distribution. |
204 | Correlation ID | Char(44) | The correlation ID of the distribution. |
248 | Prefix correlation ID | Char(16) | The prefix correlation ID of the distribution. |
264 | Priority | Char(1) | The priority of the queue that the distribution is on (N for normal or P for high queue). Not used if function is X'01'. |
265 | Destination TP Name | Char(64) | The destination transaction program
name of the distribution entered.
|
329 | Function | Char(1) | Function that was being performed
when the error entry was made. The possible values are:
|
330 | Number of recipients | Zoned(5,0) | The number of recipients for the distribution. This is set only when function is equal to X'01' (SNADS router). |
335 | Number of errors | Zoned(5,0) | The number of recipients that resulted in errors for the distribution. This is set only when function is equal to X'01' (SNADS router). There should be an ER type entry in the QSNADS journal for every recipient that caused an error during routing. |
340 | Send size | Char(4) | The total number of bytes sent when the distribution was sent to another system. The number has a 4-byte, unsigned binary format. |
344 | Queue name | Char(17) | The distribution queue name. |
361 | Send size packed | Packed(15,0) | |
376 | Distribution type | Char(1) | The distribution type of the distribution
being sent.
|
377 | Extension offset | Char(2) | The offset to the log entry extension. The number has a 2-byte, signed format. |
379 | Internal sequence number | Char(4) | The internal sequence number of the distribution entry. This number applies only to *SVDS distributions. The number has a 4-byte, signed binary format. |
383 | Message unit ID | Char(4) | The message unit ID assigned by the transport layer to *SVDS distributions. The number has a 4-byte, signed binary format. |
387 | Message unit instance number | Char(2) | The instance number assigned by the transport layer to *SVDS distributions only. The number has a 2-byte, signed binary format. |
389 | Number of logged recipients | Zoned(5,0) | The number of recipients that are logged (up to 10). |
394 | (Reserved area) | Char(320) |
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry, including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for MSF entries. |
17 | Entry type | Char(2) | Always LG for MSF message entries. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user profile name associated with the job. |
142 | Job number | Zoned(6,0) | The job number. |
150 | Program name | Char(8) | The name of the MSF program that made the journal entry. |
158 | Function identifier | Char(1) | Function that was being performed
when the entry was made. The possible values are:
|
159 | MSF message ID | Char(32) | The MSF message ID logged. |
191 | Length of entry data | Zoned(5,0) | The length of the logged data. |
196 | Logged data | Char(256) | The data logged by MSF when the function
identifier is:
|
Create data area (E EE) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Create time of day and date | Char (8) | The date and timestamp when the data area was created. |
9 | Data area name | Char (10) | The data area name. |
19 | Data area library name | Char (10) | The data area library name. |
29 | Data area type | Char (5) | The created data area type. The valid types
are:
|
34 | Reserved | Char (3) | The filler to maintain alignment. |
37 | Number of elements | Bin (32) | The number of elements. If the type is *CHAR or *LGL, only Length will contain a value. If the type is *DEC, both Length and Fraction length will contain values. |
41 | Length | Bin (32) | The declared length. |
45 | Fraction length | Bin (32) | The decimal positions. |
49 | Actual value length | Bin (32) | The length of entered data as seen by the user. |
53 | Value | Char (2000) | The data or value. |
2053 | Public authority | Char (10) | The public authority. The valid authorities
are:
|
2063 | Text description | Text (50) | The description or text. |
2113 | Owner | Char (10) | Object owner. |
2123 | Object existence authority | Char (1) |
|
2124 | Object management authority | Char (1) |
|
2125 | Object operational authority | Char (1) |
|
2126 | Reserved | Char (4) | Reserved. Set to blank. |
2130 | Authorization list management | Char (1) |
|
2131 | Read authority | Char (1) |
|
2132 | Add authority | Char (1) |
|
2133 | Update authority | Char (1) |
|
2134 | Delete authority | Char (1) |
|
2135 | Exclude authority | Char (1) |
|
2136 | Execute authority | Char (1) |
|
2137 | Object alter authority | Char (1) |
|
2138 | Object reference authority | Char (1) |
|
2139 | Resulting authority | Char (10) | The public authority resulting from the processing of the Create Data Area (CRTDTAARA) command. The value can be *CHANGE, *ALL, *USE, *EXCLUDE, or an authorization list name if the Authorization list management field in this journal entry is Y. For example, if *LIBCRTAUT was specified for the AUTHORITY keyword on the CRTDTAARA command, the value *LIBCRTAUT would be in the Public authority field and a value such as *USE could be found in this Resulting authority field. And the *USE value in this field could be specified for the AUTHORITY keyword on a subsequent CRTDTAARA command. If an error occurred, this field could be blank or a value that could not be specified for the AUTHORITY keyword on the CRTDTAARA command. |
2149 | Reserved | Char(2) | |
The following authority fields pertain to the object owner's authority for the data area associated with this journal entry. | |||
2151 | Object existence authority | Char(1) |
|
2152 | Object management authority | Char (1) |
|
2153 | Object operational authority | Char (1) |
|
2154 | Reserved | Char (2) | |
2156 | Read authority | Char (1) |
|
2157 | Add authority | Char (1) |
|
2158 | Update authority | Char (1) |
|
2159 | Delete authority | Char (1) |
|
2160 | Exclude authority | Char (1) |
|
2161 | Execute authority | Char (1) |
|
2162 | Object alter authority | Char (1) |
|
2163 | Object reference authority | Char (1) |
|
2164 | Reserved | Char(2) | |
The following authority fields pertain to the primary group's authority for the data area associated with this journal entry. If the primary group is *NONE the following authority fields will be blank. | |||
2166 | Primary group | Char (10) | This will be *NONE if there is no primary group associated with the object. |
2167 | Object existence authority | Char(1) |
|
2168 | Object management authority | Char (1) |
|
2169 | Object operational authority | Char (1) |
|
2170 | Reserved | Char (2) | |
2172 | Read authority | Char (1) |
|
2173 | Add authority | Char (1) |
|
2174 | Update authority | Char (1) |
|
2175 | Delete authority | Char (1) |
|
2176 | Exclude authority | Char (1) |
|
2177 | Execute authority | Char (1) |
|
2178 | Object alter authority | Char (1) |
|
2179 | Object reference authority | Char (1) |
|
2180 | Reserved | Char(2) | |
The following fields are used when replaying an E EE (create) journal entry. If the journal ID and name/library are not available in the entry-specific data when an entry is replayed, then the object would be created but journaling would not automatically be started for the object. | |||
2182 | Journal identifier (JOJID) | Char (10) | Journal identifier for the data area associated with this journal entry. |
2192 | Journal name | Char (10) | The journal name. |
2202 | Journal library | Char (10) | The journal library. |
2203 | Images | Char (1) | Images value that the data area received when
it started journaling
|
2204 | Remote journal filter | Char (1) | Remote journal filter value that the data area
received when it started journaling
|
Create data queue (Q QA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Create time of day and date | Char (8) | The date and timestamp when the data queue was created. |
9 | Data queue name | Char (10) | The data queue name. |
19 | Data queue library | Char (10) | The library containing the data queue. |
29 | Maximum entry length | Bin (32) | Maximum entry length. Possible values are 1 through 64512. |
33 | Force auxiliary storage | Char (1) | Force queue to auxiliary storage on send and
receive:
|
34 | Reserved | Char (8) | Reserved. |
42 | Sequence | Char (1) | Sequence in which entries are received from
the data queue:
|
43 | Key length | Bin (16) | Key length of a keyed queue. Possible values are 1 through 256. |
45 | Include sender ID | Char (1) | Attach a sender ID to each entry sent to the
queue:
|
46 | Queue type | Char (1) | Type of data queue:
Note: DDM data queues cannot be journaled
|
47 | Reserved | Bin (32) | Reserved. This field is set to zero. |
51 | Queue size maximum entries | Bin (32) | The maximum number of entries to allow:
|
55 | Queue size initial entries | Bin (32) | Initial number of entries to allocate. Note: The
default on the CRTDTAQ command is 16.
|
59 | Automatic reclaim | Char (1) | The settings for this field are:
|
60 | Reserved | Char (481) | Reserved. This field is set to zero. |
541 | Public authority | Char (10) | The public authority to the data queue. |
551 | Text | Char (50) | Text description. |
601 | Owner | Char (10) | Object owner. |
611 | Object existence authority | Char (1) |
|
612 | Object management authority | Char (1) |
|
613 | Object operational authority | Char (1) |
|
614 | Reserved | Char (4) | Reserved. Set to blank. |
618 | Authorization list management | Char (1) |
|
619 | Read authority | Char (1) |
|
620 | Add authority | Char (1) |
|
621 | Update authority | Char (1) |
|
622 | Delete authority | Char (1) |
|
623 | Exclude authority | Char (1) |
|
624 | Execute authority | Char (1) |
|
625 | Object alter authority | Char (1) |
|
626 | Object reference authority | Char (1) |
|
627 | Resulting authority | Char (10) | The public authority resulting from the processing of the Create Data Queue (CRTDTAQ) command. The value can be *CHANGE, *ALL, *USE, *EXCLUDE, or an authorization list name if the Authorization list management field in this journal entry is Y. For example, if *LIBCRTAUT was specified for the AUTHORITY keyword on the CRTDTAQ command, the value *LIBCRTAUT would be in the Public authority field and a value such as *USE could be found in this Resulting authority field. And the *USE value in this field could be specified for the AUTHORITY keyword on a subsequent CRTDTAQ command. If an error occurred, this field could be blank or a value that could not be specified for the AUTHORITY keyword on the CRTDTAQ command. |
The following authority fields pertain to the object owner's authority for the data area associated with this journal entry. | |||
2151 | Object existence authority | Char(1) |
|
2152 | Object management authority | Char (1) |
|
2153 | Object operational authority | Char (1) |
|
2154 | Reserved | Char (2) | |
2156 | Read authority | Char (1) |
|
2157 | Add authority | Char (1) |
|
2158 | Update authority | Char (1) |
|
2159 | Delete authority | Char (1) |
|
2160 | Exclude authority | Char (1) |
|
2161 | Execute authority | Char (1) |
|
2162 | Object alter authority | Char (1) |
|
2163 | Object reference authority | Char (1) |
|
2164 | Reserved | Char(2) | |
The following authority fields pertain to the primary group's authority for the data area associated with this journal entry. If the primary group is *NONE the following authority fields will be blank. | |||
2166 | Primary group | Char (10) | This will be *NONE if there is no primary group associated with the object. |
2167 | Object existence authority | Char(1) |
|
2168 | Object management authority | Char (1) |
|
2169 | Object operational authority | Char (1) |
|
2170 | Reserved | Char (2) | |
2172 | Read authority | Char (1) |
|
2173 | Add authority | Char (1) |
|
2174 | Update authority | Char (1) |
|
2175 | Delete authority | Char (1) |
|
2176 | Exclude authority | Char (1) |
|
2177 | Execute authority | Char (1) |
|
2178 | Object alter authority | Char (1) |
|
2179 | Object reference authority | Char (1) |
|
2180 | Reserved | Char(2) | |
The following fields are used when replaying a Q QA (create) journal entry. If the journal ID and name/library are not available in the entry-specific data when an entry is replayed, then the object would be created but journaling would not automatically be started for the object. | |||
2182 | Journal identifier (JOJID) | Char (10) | Journal identifier for the data area associated with this journal entry. |
2192 | Journal name | Char (10) | The journal name. |
2202 | Journal library | Char (10) | The journal library. |
2212 | Remote journal filter | Char (1) | Remote journal filter value that the data area
received when it started journaling
|
Data queue attributes changed (Q QG) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Enforce data queue locks | Char(1) | Identifies whether IBM-supplied data queue operations
will enforce a lock on the data queue. Possible values are:
|
2 | Automatic reclaim | Char(1) | Identifies whether allocated storage is automatically
reclaimed (released) when the queue is empty:
|
Data queue cleared, has key (Q QJ) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Reserved | Char (2) | Reserved for future use. |
3 | Key length | Bin (16) | The number of characters in the key. |
5 | Key order | Char (2) |
|
7 | Key | Char (*) | The data to be used to remove a message from the data queue. |
Delete access path (F PD) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Journal identifier (JOJID) | Char (10) | The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API. |
Delete receiver (J RD, J RF) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Journal identifier (JOJID) | Char (10) | The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API. |
Database file OPEN (F OP) and database file CLOSE (F CL) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats. | |||
1 | File name | Char (10) | The name of the file that was opened or closed. If a physical file is opened, this field and the JOOBJ field are the same. If a logical file is opened, this field contains the name of the logical file. JOOBJ field contains the name of the physical file. |
11 | Library name | Char (10) | The library containing the file. |
21 | Member name | Char (10) | The file member that was opened of closed. |
31 | Open options | Char (4) | Only used for file open (entry type OP). Values of the bytes follow: |
31 | Input | Char (1) | Whether the file was opened for input:
|
32 | Output | Char (1) | Whether the file was opened for output:
|
33 | Update | Char (1) | Whether the file was opened for update:
|
34 | Delete | Char (1) | Indicates if the file was opened for delete:
|
Distribution errors (S ER) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for QSNADS journal. |
17 | Entry type | Char(2) | Always ER for SNADS errors entered. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user-profile name associated with the job. |
146 | Job number | Zoned(6,0) | The job number. |
152 | Origin system name/group | Char(16) | The system name/group of the system that the distribution originated on. |
168 | Origin user ID/address | Char(16) | The user ID/address of the user that originated the distribution. This is not set if the distribution is a status distribution caused by a SNADS error. |
184 | Sequence number | Zoned(4,0) | The sequence number of the distribution entered. This is 0000 if the distribution is a status distribution. |
188 | Date/time stamp | Char(8) | A representation of the date and time of origin of the distribution. |
196 | Correlation ID | Char(44) | The correlation ID of the distribution. |
200 | Prefix correlation ID | Char(16) | The prefix correlation ID of the distribution. |
216 | Error queue | Char(17) | The SNADS queue that the distribution was on when the error occurred. |
233 | Exception class | Char(1) | Class of the exception that occurred.
Note: Applies only to errors entered by SNADS sender and receiver
jobs.
The possible values are:
|
234 | Condition code | Char(1) | Code that provides additional qualification
pertaining to the exception class. These apply only to errors entered
by SNADS sender and receiver jobs. The possible values are:
|
235 | Exception object | Char(1) | Code that indicates what part of
a DIU was being sent or received when the error that is entered occurred.
Note: Applies only to errors entered by SNADS sender and receiver
jobs.
The possible values are:
|
236 | Status condition codes | Char(2) | These condition codes identify errors
that occur during the handling of a distribution.
|
238 | Status condition codes (continued) | Char(2) | These condition codes identify errors
that occur during the handling of a distribution.
|
240 | Receiving system name/group | Char(16) | The system name/group of the SNADS node that was receiving a DIU when the error occurred. This applies only to errors entered by SNADS sender and receiver jobs. |
256 | Exception data | Char(247) | If the entry was made by the SNADS router, this field contains the distribution recipient's system name/group and user ID/address and the recipient will not receive the distribution. Otherwise this may contain data that is associated with the error entered. |
503 | Function | Char(1) | Function that was being performed
when the error occurred. The possible values are:
|
504 | Destination TPN | Char(8) | The destination transaction program name of the distribution entered. |
512 | Distribution type | Char(1) | The distribution type of the distribution
being sent.
|
513 | Program name | Char(8) | The name of the SNADS program that made the journal entry. |
521 | Internal sequence number | Char(4) | The internal sequence number of the distribution entry. This number applies only to *SVDS distributions. The number has a 4-byte signed binary format. |
525 | Message unit ID | Char(4) | The message unit ID assigned by the transport layer to *SVDS distributions only. The number has a 4-byte signed binary format. |
529 | Message unit instance number | Char(2) | The instance number assigned by the transport layer to *SVDS distributions only. The number has a 2-byte signed binary format. |
531 | SNA response code | Char(4) | The SNA response code for an *SVDS distribution. See the SNA/Distribution Services Reference for possible values. |
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry, including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for MSF entries. |
17 | Entry type | Char(2) | Always ER for MSF message error entries. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user profile name associated with the job. |
142 | Job number | Zoned(6,0) | The job number. |
150 | Program name | Char(8) | The name of the MSF program that made the journal entry. |
158 | Error ID | Char(1) | The MSF error ID. The possible values
are:
|
159 | MSF message ID | Char(32) | The MSF message ID logged. |
191 | Data length | Char(5) | The length of the logged data. |
196 | Logged data | Char(256) | The data logged by MSF when the error
ID is:
|
Distribution errors (S XE) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Length of Entry | Zoned(5,0) | Total length of the journal entry including the entry length field. |
5 | Sequence Number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset to 1 when a new receiver is attached. |
16 | Journal Code | Char(1) | Always S. |
17 | Entry Type | Char(2) | Always XE for DSNX-logged errors. |
19 | Date of Entry | Char(6) | The system date that the entry was made. |
25 | Time of Entry | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved Area) | Char(95) | |
126 | Program Name | Char(8) | The name of the DSNX program that made the journal entry. |
134 | Name of Job | Char(10) | The name of the job that caused the entry to be generated. |
144 | User Name | Char(10) | The user profile name associated with the job. |
154 | Job Number | Zoned(6,0) | The job number. |
160 | Function | Char(1) | DSNX function that was being performed
when the logged entry was made. The possible values are:
|
161 | Correlation ID | Char(44) | Identifier of the logged DSNX distribution. |
205 | Exception Data | Char(297) |
DSNX log (S XL) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Length of Entry | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence Number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset to 1 when a new receiver is attached. |
16 | Journal Code | Char(1) | Always S. |
17 | Entry Type | Char(2) | Always XL for DSNX-logged event. |
19 | Date of Entry | Char(6) | The system date that the entry was made. |
25 | Time of Entry | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved Area) | Char(95) | |
126 | Program Name | Char(8) | The name of the DSNX program that made the journal entry. |
134 | Name of Job | Char(10) | The name of the job that caused the entry to be generated. |
144 | User Name | Char(10) | The user profile name associated with the job. |
154 | Job Number | Zoned(6,0) | The job number. |
160 | Function | Char(1) | DSNX function that was being performed
when the logged entry was made. The possible values are:
|
161 | Correlation ID | Char(44) | Identifier of the logged DSNX distribution. |
205 | Logged Data | Char(100) |
Force data to auxiliary storage (F FD) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Job name (JOJOB) | Char (10) | Blank if the entry is written during IPL or vary on of an independent disk pool. | |
Job number (JONBR) | Zoned (6,0) | Zero if entry is written during IPL or vary on of an independent disk pool. | |
Program name (JOPGM) | Char (10) | Blank if the entry is written during IPL or vary on of an independent disk pool. |
Integrated file system begin create (B B0) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object name offset | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Object name field. |
5 | Object type | Char (7) | The object type that was created. |
12 | Start journaling indicator | Char (1) | Indicates whether journaling will be started.
|
13 | Reserved | Bin (32) | Reserved. This field is set to zero. |
17 | Object name | Char (*) | See the Object name table for the layout of this field. |
Integrated file system bytes cleared, after-image (B B6) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
17 | Data length | Bin (64) | The length of the data. |
25 | Offset | Bin (64) | The offset to begin write of hex zeros (clear). |
33 | Reserved | Char (16) | Reserved. Set to zeros. |
Integrated file system change audit attribute (B AA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry type | Char (1) | The type of entry is as follows:
|
2 | Object name | Char (10) | The name of the object for which the auditing attributes were changed. *N if the object is not in a library. |
12 | Library name | Char (10) | The name of the library for the object. *N if the object is not in a library. |
22 | Object type | Char (8) | The type of object. |
30 | Auditing value | Char (10) | The new value specified on the Change Auditing Value CHGAUD command. |
40 | Reserved | Char (135) | Reserved. This field is set to blanks. |
175 | Object name CCSID | Bin (31) | The coded character set identifier (CCSID) for the object name. |
179 | Reserved | Char (8) | Reserved. This field is set to blanks. |
187 | Parent FID | Char (16) | The file identifier of the parent directory. |
203 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system change object authority (B OA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry type | Char (1) | The type of entry.
|
2 | Object name | Char (10) | The object name. *N if the object is not in a library. |
12 | Library name | Char (10) | The library name. *N if the object is not in a library. |
22 | Object type | Char (8) | The type of object. |
30 | User name | Char (10) | The name of the user profile whose authorization is being granted or revoked. |
40 | Authorization list name | Char (10) | The name of the authorization list. |
50 | Object existence authority | Char (1) |
|
51 | Object management authority | Char (1) |
|
52 | Object operational authority | Char (1) |
|
53 | Authorization list management | Char (1) | Blank if user does not authorization list management to the object. |
54 | Authorization list *PUBLIC authority | Char (1) |
|
55 | Read authority | Char (1) |
|
56 | Add authority | Char (1) |
|
57 | Update authority | Char (1) |
|
58 | Delete authority | Char (1) |
|
59 | Exclude authority | Char (1) |
|
60 | Execute authority | Char (1) |
|
61 | Object alter authority | Char (1) |
|
62 | Object reference | Char (1) |
|
63 | Reserved | Char (4) | Reserved. Set to blanks. |
67 | Operation type | Char (3) | Possible values are:
|
70 | Reserved | Char (149) | Reserved. Set to blanks. |
19 | Object name CCSID | Bin (31) | The coded character set identifier (CCSID) for the object name. |
223 | Reserved | Char (8) | Reserved. Set to blanks. |
231 | Parent FID | Char (16) | The file identifier of the parent directory. This field is not set or used. |
247 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system change object owner (B OO) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry type | Char (1) | The type of entry.
|
2 | Object name | Char (10) | The object name. *N if object is not in a library. |
12 | Library name | Char (10) | The library name. *N if object is not in a library. |
22 | Object type | Char (8) | The object type. |
30 | Old owner | Char (10) | The old owner. |
40 | New owner | Char (10) | The new owner. |
50 | Reserved | Char (143) | Reserved. Set to blanks. |
193 | Object name CCSID | Bin (31) | The coded character set identifier (CCSID) for the object name. |
197 | Reserved | Char (8) | Reserved. Set to blanks. |
205 | Parent FID | Char (16) | The file identifier of the parent directory. |
221 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system change primary group (B OG) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry type | Char (1) | Type of entry
|
2 | Object name | Char (10) | The object name. *N if object is not in a library. |
12 | Library name | Char (10) | The library name. *N if object is not in a library. |
22 | Object type | Char (8) | The type of object. |
30 | Old primary group | Char (10) | The old primary group. |
40 | New primary group | Char (10) | The new primary group. |
50 | Object existence authority | Char (1) |
|
51 | Object management authority | Char (1) |
|
52 | Object operational authority | Char (1) |
|
53 | Object alter authority | Char (1) |
|
54 | Object reference authority | Char (1) |
|
55 | Reserved | Char (10) | Reserved. Set to blanks. |
65 | Authorization list management | Char (1) | Blank if new primary group does not authorization list management to the object. |
66 | Read authority | Char (1) |
|
67 | Add authority | Char (1) |
|
68 | Update authority | Char (1) |
|
69 | Delete authority | Char (1) |
|
70 | Execute authority | Char (1) |
|
71 | Reserved | Char (10) | Reserved. Set to blanks. |
81 | Exclude authority | Char (1) |
|
82 | Revoke previous primary group authority | Char (1) |
|
83 | Reserved | Char 143 | Reserved. Set to blanks. |
226 | Object name CCSID | Bin (31) | The coded character set identifier (CCSID) for the object name. |
230 | Reserved | Char (8) | Reserved. Set to blanks. |
238 | Parent FID | Char (16) | The file identifier of the parent directory. |
254 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system created object authority (B B7) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the created object. |
17 | Number of authorities | Bin (32) | The number of private authorities in this entry. |
21 | Offset to object name | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Object name field. |
25 | Offset to path name | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Path name field. |
29 | Offset to authority information | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Authority information field. |
33 | Format indicator | Char (1) | The format indicator is set to the following:
|
34 | Reserved | Char (15) | Reserved. Set to zeros. |
* | Object name | Char (*) | See the Object name table for the layout of this field. |
* | Path name | Char (*) | See the Path name table for the layout of this field. |
* | Authority information | Char (*) | The array of private authority information that has been set for the created object. See the Private authority table for the layout of one array element in this field. If the incomplete data indicator is off, the information is a character string. Otherwise, it is a pointer to the actual data. See Working with pointers in journal entries for more information. |
Integrated file system create-summary (B B1) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Offset to name | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Object name field. |
5 | Offset to path name | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Path name field. |
9 | Offset to symbolic link contents field. | Bin (32) | The offset from the beginning of the entry-specific data to the beginning of the Symbolic link contents field. |
13 | Object type | Char (7) | The object type that was created. |
20 | Scan attribute | Char (1) | If the new object is a stream file (*STMF), this field is the scan (QP0L_ATTR_SCAN) attribute as described in the Set Attributes (Qp0lSetAttr()) API. If the new object is a directory (*DIR), this field is the create object scanning (QP0L_ATTR_CRTOBJSCAN) attribute of the Qp0lSetAttr()) API. |
21 | File ID of object | Char (16) | The new object file identifier. |
37 | Owner name | Char (10) | The user profile name of the owner. |
47 | Group name | Char (10) | The primary group profile name. |
57 | Auditing value | Char (10) | The auditing value of the new object. |
67 | Object CCSID | Bin (16) | The coded character set identifier (CCSID) for the object. |
69 | Owner private authority | Char (12) | Private authorities assigned to the owner. See the Private authority information table. |
81 | Primary group private authority | Char (12) | Private authorities assigned to the primary group. See the Private authorities for specified profile table. |
93 | *PUBLIC private authority | Char (12) | Private authorities assigned to the *PUBLIC. See the Private authorities for specified profile table.. |
105 | Authorization list name | Char (10) | The authorization list name for the new object. |
115 | Authorization list *PUBLIC | Char (1) | The authorization List *PUBLIC authority. Possible values are Y or blank. |
116 | Format indicator | Char (1) | The format indicator is set to one of the following values:
For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
117 | PC read-only | Char (1) | The PC read Only flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
118 | PC hidden | Char (1) | The PC hidden flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
119 | PC system | Char (1) | The PC System file flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
120 | PC changed | Char (1) | The PC changed flag. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API.. |
121 | Journal information | Char (36) | The journaling information for the new object. This field indicates if journaling is now active on the new object. If so, it also contains the information the information used to start journaling. See the Journal information table for the layout of this field. |
157 | Device ID | Bin (64) | This field is only valid when the object type is *CHRSF. |
165 | Create object auditing | Char (10) | The create object auditing value. This value only applies to directories (*DIR). |
175 | S_ISVTX value | Char (1) | The restricted rename and unlink (S_ISVTX) mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
176 | S_ISUID value | Char (1) | The S_ISUID mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
177 | S_ISGID value | Char (1) | The S_ISGID mode bit. For information about the values in this field see the Get Attributes (Qp0lGetAttr()) API. |
178 | Object name | Char (*) | See the Object name table for the layout of this field. |
* | Path name | Char (*) | See the Path name table for the layout of this field. |
* | Symbolic link contents | Char (*) | See the Symbolic link contents table for the layout of this field. |
Integrated file system end journaling for object (B ET) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system link to existing object (B B2) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the existing object. |
17 | Link offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Link name field. |
21 | Path offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Path name field. |
25 | Start journaling | Char (1) | The start journaling indicator.
|
26 | Summary | Char (1) | The summary record indicator.
|
27 | Reserved | Char (2) | Reserved. Set to zero. |
29 | Journal information | Char (36) | The journaling information for the new object. This field is defined in the Journal information table. |
65 | Link name | Char (*) | The name of the new link to the object. See the Object name table for the layout of this field. |
* | Path name | Char (*) | The existing object path name. If this B2 journal entry was deposited as a result of a rollback of a B5 entry, then this will actually be the path to the parent directory to which the link is being added. See the Path name table for the layout of this field. |
Integrated file system object attribute changed (B FA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
17 | Parent FID | Char (16) | The file identifier of the parent directory. |
33 | Object type | Char (7) | The type of object. |
40 | Reserved | Char (9) | Reserved. This field is set to hex zeros. |
49 | Next attribute offset | Bin (32) | The offset to the next attribute. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry. |
53 | Attribute identifier | Bin (32) | The attribute identifier. See the Set Attributes (Qp0lSetAttr()) API for information about the structure and content of this field. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry. |
57 | Attribute data size | Char (32) | Size of attribute data in bytes. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry. |
61 | Reserved | Char (4) | Reserved. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry. |
65 | Changed data | Char (*) | The data that was changed. All of the offsets 49, 53, 57, 61, and 65 will repeat for each attribute set for this entry. |
Integrated file system object closed (B CS) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Open flags | Bin (31) | Open flags. See the Open API for a description of these flags. |
Integrated file system object deleted (B BD) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system object forced (B FC) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
Integrated file system object opened (B OF) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Open flags | Bin (31) | Open flags. See the Open API for a description of these flags. |
Integrated file system object truncated (B TR) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
17 | Old size | Bin (64) | The size of the object in bytes before it was truncated. |
25 | New size | Bin (64) | The size of the object in bytes after it was truncated. |
Integrated file system remove link (link) (B B5) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the existing object. |
17 | Parent FID | Char (16) | The file identifier of the object parent directory. |
33 | Link offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Link name field. |
37 | Parent path offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Parent path field. |
41 | Parent directory JID | Char (10) | The journal identifier of parent directory. |
51 | Object type | Char (7) | The type of the object. |
58 | Reserved | Char (3) | Reserved. Set to zero. |
61 | Internal data offset | Bin (32) | The offset from beginning of this field to the beginning of Internal data field. |
65 | Link name | Char (*) | The name of link. See the Object name layout of this field. |
* | Parent path | Char (*) | The path to the parent that used to contain this link. See the Path name layout of this field. |
* | Internal data | Char (*) | Internal data. |
Integrated file system remove link (parent directory) (B B4) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the existing object. |
17 | Parent FID | Char (16) | The parent directory of the link file identifier. |
33 | Link offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Link name field. |
37 | Object JID | Char (10) | The journal identifier of the object. |
47 | Object type | Char (7) | The type of the object. |
54 | Reserved | Char (7) | Reserved. Set to zero. |
61 | System offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of Internal data. |
65 | Link name | Char (*) | The name of link. See the Object name layout of this field. |
* | Internal data | Char (*) | Internal data. |
Integrated file system rename file identifier (B RN) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Old FID | Char (16) | The file identifier of the object before the rename operation. |
17 | Reserved | Char (14) | Reserved. Set to blanks. |
31 | New FID | Char (16) | The file identifier of the object after the rename operation. |
47 | Reserved | Char (14) | Reserved. Set to blanks. |
Integrated file system rename, move object (B B3) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object for the renamed link. |
17 | Source parent FID | Char (16) | The file identifier of the source object directory. |
33 | Target parent FID | Char (16) | The file identifier of the target object directory. |
49 | Replaced object FID | Char (16) | The file identifier of the object that was replaced by this operation. This field contains all hex zeros if no object was replaced. |
65 | Source offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Source name field. |
69 | Target offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Target name field. |
73 | Source parent offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Source parent path field. |
77 | Target parent offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of the Target parent path field. |
81 | Start journaling | Char (1) | The start journaling indicator:
|
82 | Summary | Char (1) | The summary record indicator:
|
83 | Replace | Char (1) | The replace indicator. Indicates if the target was replaced
as a result of this operation.
|
84 | Journal entry flags | Bin (32) | The fields for journal entry flags are as follows:
|
88 | Reserved | Char (4) | Reserved field. |
92 | Journal information | Char (37) | The journaling information for the new object. This field is defined in Journal information. |
129 | System offset | Bin (32) | The offset from beginning of this entry-specific data to the beginning of Internal data field. |
133 | Source name | Char (*) | The name of object being renamed or moved. See the Object name layout of this field. |
* | Target name | Char (*) | The new name of object after being renamed or moved. See the Object name layout. |
* | Source parent path | Char (*) | The path to the parent directory from which the object previously belonged. See Path name for the layout of this field. |
* | Target parent path | Char (*) | The path to the parent directory to which the object now belongs. See Path name for the layout of this field. |
* | Internal data | Char (*) | Internal data. |
Integrated file system storage for object freed (B FF) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
17 | Old size | Bin (64) | The old size of the object. |
Integrated file system write, after-image (B WA) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object FID | Char (16) | The file identifier of the object. |
17 | Data length | Bin (64) | Length of the data. |
25 | Offset | Bin (64) | The offset to begin write. |
33 | Reserved | Char (16) | Reserved. |
49 | Data | Char (*) | The actual data that was written. If the incomplete data indicator is off, the information is a character string. Otherwise, it is a pointer to the actual data. See Work with pointers in journal entries for more information. |
Identity Value (F IT) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Version | Bin(15) | Version number |
3 | Identity Value | DECIMAL(31,0) | The last identity value allocated in the current CACHE |
INZPFM (F IZ) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Count or relative record number (JOCTRR) | Zoned (10,0) | Contains the number of records specified on the TOTRCDS parameter of the Initialize Physical File Member (INZPFM) command. | |
Flag (JOFLAG) | Char (1) | Indicates the type of record initialization that was done:
|
|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry-specific data | If the member is initialized with default records, this field contains the default record image. |
IP NAT rules actions (M TN) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always “M” |
17 | Entry type | Char(2) | Always “TN” |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Line description | Char(10) | “*ALL” if TFREVT is “U*”. Blank if TFREVT is “L*”. Line name if TFREVT is “L”. |
136 | Rule Event | Char(2) | “L*” or “L” when rules are loaded. “U*” when rules are unloaded. “A”when filter action. |
138 | IP Packet Direction | Char(1) | “O” is outbound. “I” is inbound. |
139 | Rule Number | Char(5) | Applies to the rule number in the active rules file. |
144 | Transport Protocol | Char(4) |
|
149 | Source IP Address | Char(15) | |
164 | Source Port | Char(5) | |
169 | Destination IP Address | Char(15) | |
184 | Destination Port | Char(5) | |
189 | Translated IP Address | Char(15) | |
204 | Translated source port | Char(5) | |
209 | Translated Destination IP | Char(15) | |
224 | Translated Destination Port | Char(5) | |
229 | Text Information | Char(76) | Contains description if TFREVT = “L*” or “L” or “U*” |
IP Packet Filter (M TF) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always “M” |
17 | Entry type | Char(2) | Always “TF” |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Line description | Char(10) | “*ALL” if TFREVT is “U*”. Blank if TFREVT is “L*”. Line name if TFREVT is “L”. |
136 | Rule Event | Char(2) | “L*” or “L” when rules are loaded. “U” when rules unloaded. “A” when filter action. |
138 | IP Packet Direction | Char(1) | “O” is outbound. “I” is inbound. |
139 | Rule Number | Char(5) | Applies to the rule number in the active rules file. |
144 | Filter Action Taken | Char(6) | “PERMIT” or “DENY” |
148 | Transport Protocol | Char(4) |
|
152 | Source IP Address | Char(15) | |
157 | Source Port | Char(5) | Garbage if TFPROT =1 (ICMP) |
162 | Destination IP Address | Char(15) | |
177 | Destination Port | Char(5) | Garbage if TFPROT =1 (ICMP) |
182 | Additional Text | Char(76) | Contains description if TFRVET = “L*” or “L” or "U" |
IPL (J IA, J IN) and in-use (B OI, C BA, D ID, E EI, F IU, I DA, J JI, Q QI) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Time stamp (JOTIME) | Zoned (6,0) | The timestamp created at IPL is read from the battery-powered clock. If the battery-powered clock cannot be read, the time is that of the system power down, not the time of the IPL, because the system time has not yet been updated at the time the journal entry is written. | |
Flag (JOFLAG) | Char (1) | For in-use entries, indicates whether the object was synchronized
with the journal:
|
Journal code R, all journal entry types except IL
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Flag (JOFLAG) | Char (1) | Whether a before-image is present1:
|
|
Journal identifier (JOJID) | Char (10) | The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API. | |
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Entry-specific data | Char (*) | After-image of the record for entry types PT, PX, UP, or UR. Before-image of the record for entry types UB, DL, BR, or DR if before-images are being journaled and the record was not previously deleted. |
Note: 1The flag does
not apply to these entry types: PT, PX, UP, and UR.
|
Journaling for library started (Y YB) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Omit journal entries | Char (1) | Identifies whether entries are to be omitted from journaling:
|
2 | New objects inherit journaling | Char (1) | Identifies whether new objects created within
a library or directory should inherit journaling
|
3 | Reserved | Char(4) | |
6 | Displacement to additional information | Bin(16) unsigned short integer | |
Offset determined by Displacement to additional information | Version | Bin(32) unsigned integer | Version number for this structure |
Displacement to Inherit Rules | Bin(32) unsigned integer | Displacement to Inherit Rules information from the beginning of the Version field | |
Offset determined by Displacement to Inherit Rules | Inherit Rules | See Journal Inherit Rules |
License key not valid (L LK) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Product ID | Char (7) | The ID of the product whose license key was not valid. |
8 | License term | Char (6) | The term of the license. |
14 | Feature | Char (4) | The product feature code. |
18 | Usage limit | Zoned (6,0) | The usage limit for the product. |
24 | License key | Char (18) | The license key for the product. |
42 | Expiration date | Char (7) | The expiration date for the license key. |
49 | Vendor data | Char (8) | Data placed in the entry by the product vendor. |
57 | Processor group | Char (3) | The processor group for the license key. |
Library renamed (Y YN) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Old library name | Char(10) | |
11 | Reserved | Char(20) | |
31 | New library name | Char(10) | |
41 | Reserved | Char(20) |
Logical file associated with the library or based on physical file (D LF, Y LF) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Logical file name | Char(10) | |
11 | Logical file library name | Char(10) | |
21 | Logical file journal identifier | Char(10) |
Logical unit of work (C LW) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | LUW header portion | 416 | The header portion of the entry-specific data contains general information about the logical unit of work (LUW). The layout for the Logical unit of work (C LW) journal entry - header record describes the contents of the header portion. |
After the header portion | LUW local portion | 80 | Information about local resources that participated in the LUW. The entry might have 0 to n records for local locations. Each local record is 48 characters long. The layout for the Logical unit of work (C LW) journal entry - local record describes the local record. |
After the local portion | LUW API portion | 112 | Information about API resources that participated in the LUW. The entry might have 0 to n records for API resources. Each API resource record is 80 characters long. The layout for the 0 Logical unit of work (C LW) journal entry - API record describes the API record. |
After the API portion | LUW DDL portion | 96 | Information about DDL resources that participated in the LUW. The entry might have 0 to n records for DDL resources. Each DDL resource record is 80 characters long. The layout for the Logical unit of work (C LW) journal entry - DDL record describes the DDL record. |
After the DDL portion | LUW remote portion | 128 | Information about remote locations that participated in the LUW. The entry might have 0 to n records for remote locations. Each remote location record is 128 characters long. The layout for the Logical unit of work (C LW) journal entry - RMT record describes the remote record. |
After the remote portion | LUW DDM portion | 96 | Information about DDM resources that participated in the LUW. The entry might have 0 to n records for DDM resources. Each DDM resource record is 96 characters long. The layout for the Logical unit of work (C LW) journal entry - DDM record describes the DDM record. |
Logical unit of work (C LW) journal entry - API record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Type of record:
|
5 | Record length | Bin (15) | Length of record. Currently 80 for API record. |
7 | Record position | (4) 1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Resource location position | (4)1 | This identifies the position in the LUW journal entry where
the LCL record starts for this API resource's location. It is made
up of two numbers:
|
15 | Next resource position | (4)1 | This identifies the position in the LUW journal entry where
the next API or DDL record starts for this API resource's location.
It is made up of two numbers:
Position 0 0 indicates that this is the last resource for this API resource's location. |
19 | API resource | Char (10) | Name of API resource. |
29 | API program | Char (20) | Name of the exit program for the API resource:
|
49 | Journal | Char (20) | Journal related to the location for this resource:
|
69 | Commit cycle ID | Bin (31) | The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Commit cycle ID Long field always contains the correct value. |
73 | Commit protocol | Char (1) | The commit protocol for this resource:
|
74 | Resource usage | Char (2) | The currently allowed access for this resource. The allowed
access for some resources can change from one LUW to another depending
on whether one-phase resources are registered:
|
76 | API state | Char (2) | Indicates whether the API resource was committed or rolled
back successfully:
|
78 | API last agent flag | Char (1) | Whether this resource is to be selected as the last agent during
all commit requests:
|
79 | Allow remote resources | Char (1) | Whether remote resources are allowed to participate in a LUW
with this resource:
|
80 | Save while active flag | Char (1) | Whether this resource will hold out a save-while-active request
until a commitment boundary is reached:
|
81 | Commit cycle ID long | Zoned (20,0) | The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. |
101 | Reserved | Char (12) | Reserved for future use. |
Note: 1The format for
this field is in the description.
|
Logical unit of work (C LW) journal entry - DDL record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Type of record:
|
5 | Record length | Bin (15) | Length of record. Currently 624 for DDL record. |
7 | Record position | (4)1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Resource location position | (4)1 | This identifies the position in the LUW journal entry where
the LCL record starts for this DDL resource's location. It is made
up of two numbers:
|
15 | Next resource position | (4)1 | This identifies the position in the LUW journal entry where
the next API or DDL record starts for this DDL resource's location.
It is made up of two numbers:
Position 0 0 indicates that this is the last resource for this DDL resource's location. |
19 | DDL resource information | Char (29) | Object identification and operation performed on object:
The possible object operations and their meanings are the following:
|
48 | Reserved | Char (1) | Reserved for future use. |
49 | Journal | Char (20) | Journal related to the location for this resource:
|
69 | Commit cycle ID | Bin (31) | The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Commit cycle ID Long field always contains the correct value. |
73 | Commit protocol | Char (1) | The commit protocol for this resource:
|
74 | DDL state | Char (2) | Indicates whether the DDL resource was committed or rolled
back successfully:
|
76 | Commit cycle ID long | Zoned (20,0) | The commit cycle identifier for the journal. This is 0 if this resource belongs to the location with no journal. |
96 | Object name | Char (288) | The full object name. |
384 | Reserved | Char (1) | Reserved for future use. |
Note: 1The format for
this field is in the description.
|
Logical unit of work (C LW) journal entry - DDM record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Type of record:
|
5 | Record length | Bin (15) | Length of record. Currently 96 for DDM record. |
7 | Record position | (4) 1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Resource location position | (4) 1 | This identifies the position in the LUW journal entry where
the RMT record starts for this DDM file's location. It is made up
of two numbers:
|
15 | Next resource position | (4)1 | This identifies the position in the LUW journal entry where
the next DDM record starts for this DDM file's location. It is made
up of two numbers:
|
19 | DDM file | Char (20) | Name of the DDM file and library for the open remote file:
|
29 | Remote position information | Char (54) | Identification of the remote location and communication information
for this resource's location:
|
93 | Open flag | Char (1) | Whether the DDM file was open or closed when this LUW ended:
|
94 | Commit protocol | Char (1) | The commit protocol for this resource:
|
95 | Resource usage | Char (2) | The currently allowed access for this resource. The allowed
access for some resources can change from one LUW to another depending
on whether one-phase resources are registered:
Note: This does not indicate whether updates were actually
made during the LUW. It only indicates whether updates are allowed,
given the other resources currently registered.
|
Note: 1The format for
this field is in the description.
|
Logical unit of work (C LW) journal entry - header record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Type of record:
|
5 | Record length | Bin (15) | Length of record. Currently 400 for HDR record. |
7 | Record position | (4)1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Number of journal entries | Bin (15) | The number of actual journal entries sent for this LUW journal entry. This is 1 unless the LUW journal entry is greater than 32K-1 bytes. |
13 | position with no journal position | (4) 1 | This identifies the position in the LUW journal entry where
the LCL record starts for the local location with no journal. It is
made up of two numbers:
Position 0 0 means that there is no local location that does not have a journal. |
17 | First location with journal position | (4)1 | This identifies the position in the LUW journal entry where
the LCL record starts for the first local location with a journal.
It is made up of two numbers:
Position 0 0 means that there are no local locations with a journal. |
21 | First remote location position | (4)1 | This identifies the position in the LUW journal entry where
the RMT record starts for the first remote location. It is made up
of two numbers:
Position 0 0 means there are no remote locations. |
25 | LUW operation | Char (2) | The operation that was performed to end this LUW:
|
27 | Protected logical unit of work identifier (LUWID) | Char (41) | The format for the LUWID is:
|
68 | Unprotected logical unit of work identifier | Char (41) | The format for the LUWID for unprotected conversations is the same as for protected conversations. |
109 | Default journal commit cycle ID | Bin (31) | The commit cycle identifier for the default journal for this LUW. This is 0 if no commit cycle was started for this journal during this LUW. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Default Journal Commit cycle ID Long field always contains the correct value. |
113 | Commitment definition name | Char (10) | The name of the commitment definition for which this LUW took place. |
123 | Commitment definition identifier | Char (10) | The commitment definition identifier of the commitment definition. This is not useful to the user. |
133 | Qualified job name | Char (26) | The job that created the commitment definition. |
159 | Reserved | Char (1) | Reserved for future use. Currently always blank. |
160 | Commitment definition scope | Char (1) | The scope of the commitment definition:
|
161 | Activation group mark | Bin (31) | The activation group mark for the commitment definition:
|
165 | Notify object | Char (37) | The notify object for the commitment definition:
|
202 | Default journal | Char (20) | The default journal for the commitment definition:
|
222 | Initiation type | Char (1) | Whether this commit or rollback operation was initiated by
the user or by the system:
If the LUW was finished after a system end, this is set to I, even if an explicit commit or rollback operation was running at the time the system ended. |
223 | LUW end status | Char (1) | Indication of when this LUW ended with respect to the job that
created the commitment definition for which this LUW took place:
|
224 | Sync-point role | Char (1) | The sync-point role played by this location during a commit
operation:
|
225 | Partner role | Char (1) | The partner role played by this location during a commit:
|
226 | LUW disposition | Char (2) | The overall disposition of the LUW:
When heuristic damage occurs, the following LUW journal entry records can be checked to learn the status of the changes made during the LUW to individual resources:
|
228 | Heuristic operation indicator | Char (1) | Whether a heuristic commit or rollback operation occurred at
this location while a commit request was being performed for this
LUW:
A heuristic commit operation or rollback operation means that the operator took explicit action (while this location was waiting for the commit or rollback decision from the initiator or the last agent) to commit or to roll back the resources at this location and all prepared downstream locations. Heuristic operations can result in some resources committing while others roll back. The LUW Disposition field can be checked to see if this has happened (it would be HD). The Resync In Progress indicator field can also be checked. If it is O, heuristic damage might have occurred or it might still occur because the state of the resources at the locations where resynchronization is still going on is unknown. Messages are written to the history log and to the system database server job logs when the resynchronization processes complete to indicate whether damage occurred. If damage occurs, messages are also sent to the system operator when it is detected. |
229 | Resync in progress indicator | Char (1) | Whether resync to one or more remote locations was still ongoing
when the LUW ended:
|
230 | Wait for outcome | Char (1) | The value of the Wait for outcome commitment option. This indicates
whether to wait for resynchronization to complete if a communication
or system failure occurs during a commit or rollback.
|
231 | Action if problems | Char (1) | The value of the Action if problems commitment option. This
indicates whether to commit or rollback when problems occur during
a two-phase commit.
|
232 | Vote read-only permitted | Char (1) | The value of the Vote read-only permitted commitment option.
This indicates whether this commitment definition is allowed to return
a read-only vote to a remote initiator during a two-phase commit.
|
233 | Action if ENDJOB | Char (1) | The value of the Action if ENDJOB commitment option. This indicates
the action to take for changes associated with the LUW when the job
the LUW is a part of is ended.
|
234 | OK to leave out | Char (1) | The value of the OK to leave out commitment option. This indicates
whether this location is allowed to be left out during the next commit/rollback
if no activity occurred to this location during the LUW.
|
235 | Last agent permitted | Char (1) | The value of the Last agent permitted commitment option. This
indicates whether last agent optimization may be used.
|
236 | Accept vote reliable | Char (1) | The value of the Accept vote reliable commitment option. This
indicates whether the vote reliable indicator received from agents
during a commit operation is accepted by this location. If an agent
votes reliable, and this location accepts it, control is returned
to the application before the committed wave is completed for that
agent. If this location does not accept vote reliable, control is
returned to the application only after the LUW is completely committed
or rolled back.
|
237 | Resolved wait for outcome value | Char (1) | This indicates the actual wait for outcome value that was used
during the commit or rollback of this LUW. If the Wait for outcome
commitment option is L or U, this value might have been inherited
from this location's initiator.
|
238 | XA transaction manager | Char (10) | If this was an X/Open transaction, this is the name of the XA Transaction Manager that was specified on the db2xa_open API. This field will be hex zeros if this was not an XA transaction. |
248 | XID | Char (140) | If this was an X/Open Transaction, this is the X/Open Transaction
Identifier associated with this transaction. This field will be hex
zeros if this was not an X/Open transaction, or if it was an X/Open
local transaction. The format of this field is as follows:
|
388 | Default journal commit cycle ID long | Zoned (20,0) | The commit cycle identifier for the default journal for this LUW. This is 0 if no commit cycle was started for this journal during this LUW. |
408 | Reserved | Char (9) | Reserved for future use. |
Note: 1The format for
this field is in the description.
|
Logical unit of work (C LW) journal entry - local record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Type of record:
|
5 | Record length | Bin (15) | Length of record. Currently 48 for LCL record. |
7 | Record position | (4)1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Next local location position | (4) 1 | This identifies the position in the LUW journal entry where
the next LCL record starts. It is made up of two numbers:
Position 0 0 indicates that this is the last local location. |
15 | First resource position | (4)1 | This identifies the position in the LUW journal entry where
the first API or DDL record starts for this location. It is made up
of two numbers:
|
19 | Record I/O state | Char (2) | Indicates whether the record I/O performed during this LUW
for files journaled to the journal related to this location was committed
or rolled back successfully:
|
21 | Journal | Char (20) | Journal related to this location:
|
41 | Commit cycle ID | Bin (31) | The commit cycle identifier for the journal. This is 0 for the location with no journal. It might be 0 for the location related to the default journal if there were no resources for that location during this LUW. This is -1 if the actual commit cycle identifier value is larger than 2 147 483 647. The Default Journal Commit cycle ID Long field always contains the correct value. |
45 | Default journal flag | Char (1) | Indicates whether the journal related to this location is the
default journal:
|
46 | Commit cycle ID Long | Zoned (20,0) | The commit cycle identifier for the journal. This is 0 for the location with no journal. It might be 0 for the location related to the default journal if there were no resources for that location during this LUW. |
66 | Reserved | Char (15) | Reserved for future use. |
Note: 1The
format for this field is in the description.
|
Logical unit of work (C LW) journal entry - RMT record
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Record type | Char (4) | Remote position (RMT) record. |
5 | Record length | Bin (15) | RMT record is currently 128. |
7 | Record position | (4)1 | This identifies the position in the LUW journal entry where
this record starts. It is made up of two numbers:
|
11 | Next Rrmote location position | (4)1 | This identifies the position in the LUW journal entry where
the next RMT record starts. It is made up of two numbers:
Position 0 0 indicates that this is the last remote location. |
15 | First resource position | (4) 1 | This identifies the position in the LUW journal entry where
the first DDM record starts for this location. It is made up of two
numbers:
Position 0 0 indicates that there are no DDM records for this location. |
19 | Remote position information | Char (54) | Identification of the remote location and communication information
for this location:
|
73 | Relational database name | Char (18) | The name of the relational database opened at this remote location (blank if no relational database has been opened). |
91 | Conversation deallocation flag | Char (1) | Whether the conversation was deallocated because of this LUW:
|
92 | Commit protocol | Char (1) | The commit protocol for the resources at this location:
|
93 | Resource usage | Char (2) | The currently allowed access for this resource. The allowed
access for some resources can change from one LUW to another depending
on whether one-phase resources are registered:
Note: This does not indicate whether updates were actually
made during the LUW. It indicates only whether updates are allowed,
given the other resources currently registered.
|
95 | Resource state | Char (2) | The state of the resources at this location:
|
97 | Allocator flag | Char (1) | Indicates whether this is the allocator location, for example,
the location that called the transaction program running on this system:
|
98 | Remote last agent flag | Char (1) | Indicates whether this location was selected as the last agent
if a commit request was performed to end this LUW:
Note: A last agent will not be selected at this location unless
the Partner Role field in the HDR record is I or L.
|
99 | Two-phase protocol | Char (1) | The two-phase commit protocol options supported at this location.
|
100 | Resync initiator | Char (1) | If resync with this location is still ongoing (the Resource
State field is RI), this value indicates whether the local location
is initiating the resync attempts.
|
101 | Voted reliable | Char (1) | Whether this location voted reliable during the commit of this
LUW.
|
102 | OK to leave out | Char (1) | Whether this location indicated it may be left out of the next
commit or rollback operation if no communications flows occur to that
location during the next LUW.
|
103 | Left out | Char (1) | Whether this location was left out of the LUW that was just
committed or rolled back.
|
104 | Initiator flag | Char (1) | Indicates whether this location is the initiator location,
i.e. the location that sent the commit or rollback request to this
system.
Note: The system cannot determine the initiator location if the
initiator does not support two-phase commit protocols. This field
will always be set to N for locations that do not support two-phase
commit protocols.
|
105 | Reserved | Char (24) | Reserved for future use. |
Note: 1The format for
this field is in the description.
|
Mail server framework system level events (S SY) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Entry length | Zoned(5,0) | Total length of the journal entry, including the entry length field. |
6 | Sequence number | Zoned(10,0) | Applied to each journal entry. Initially set to 1 for each new or restored journal. Reset when a new receiver is attached. |
16 | Journal code | Char(1) | Always S for MSF entries. |
17 | Entry type | Char(2) | Always SY for MSF system level events entries. |
19 | Date stamp | Char(6) | The system date that the entry was made. |
25 | Time stamp | Zoned(6,0) | The system time that the entry was made. |
31 | (Reserved area) | Char(95) | |
126 | Job name | Char(10) | The name of the job that caused the entry to occur. |
136 | User name | Char(10) | The user-profile name associated with the job. |
146 | Job number | Zoned(6,0) | The job number. |
152 | Program name | Char(8) | The name of the MSF program that made the journal entry. |
160 | Function identifier | Char(1) | Function that was being performed
when the entry was made. The possible values are:
|
161 | Data length | Zoned(5,0) | The length of the logged data. |
166 | Logged data | Char(256) | The data logged by MSF when the function
identifier is:
|
Moving and renaming objects (D FM, D FN, E EM, E EN, F MM, F MN, F PM, F PN, J MJ, Q QM, Q QN) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Journal identifier (JOJID) | Char (10) | Records for the entries will have a journal identifier. The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API. | |
Flag (JOFLAG) | Char (1) | The status of the object's library:
|
|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object name before | Char (10) | The name of the object before the object was moved or renamed. |
11 | Library name before | Char (10) | The name of the library before the object was moved or renamed. |
21 | Member name before | Char (10) | The name of the member before it was moved or renamed. This field is blank if the object is not a physical database file. |
31 | Object name after | Char (10) | The name of the object after the object was moved or renamed. |
41 | Library name after | Char (10) | The name of the library after the object was moved or renamed. |
51 | Member name after | Char (10) | The name of the member after it was moved or renamed. This field is blank if the object is not a physical database file. |
61 | Internal data | Char (*) | Internal system information. Note: This field does
not apply to E EM, E EN, Q QM, or Q QN entries.
|
Object added to library (Y YO) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object name | Char (10) | |
11 | Object type | Char (10) | |
21 | Reserved | Char (20) | |
31 | Insert operation | Char (1) | Insert operation:
|
41 | Object JID | Char (10) | Object's journal identifier |
51 | Inherit journaling | Char (1) | Did object inherit journaling from library:
|
Object level (D AC, D CG, D CT, D DC, D DT, D GC, D GO, D GT, D RV, D TC, D TD, D TG, D TQ, F DM, F MC) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Object name | Char (10) | The name of the object that was operated on. |
11 | Library name | Char (10) | The name of the library for the object that was operated on. |
21 | Member name | Char (10) | The name of the member that was operated on, if applicable. This field is blank if it does not apply. |
31 | New Object name | Char (10) | The new name of the file if this is a rename file, rename member or move file operation. This field is blank if it does not apply. |
41 | New object library | Char (10) | The new name of the lib if this is a move file, rename file or rename member operation. This field is blank if it does not apply. |
51 | New member name | Char (10) | The new name of the member if this is a rename member operation. This field is blank if it does not apply. |
61 | Reserved | Char (12) | Reserved |
73 | Apply length | Bin (31) | The length of the extra ESD data pointed to by the teraspace pointer if the incomplete flag is on. |
77 | Reserved | Char (32) | Reserved |
109 | Change field type | Char (1) | The type of Change file operation:
The type of Change Trigger operation:
If the journal entry is CT or MC, these subtype values are returned:
If the journal entry is CB, the following subtype values are returned:
If the journal entry is GC, the following subtype values are returned:
This field is not applicable if the entry type is not CG, CT, MC, TG, CB, or GC. |
110 | Reserved | Char (3) | Reserved. |
113 | Length of trigger library name | Bin (15) | The length of the trigger library name for a Change Trigger operation. Contains 0 if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG. |
115 | Offset to trigger library name | Bin (31) | The offset to the trigger library name for a Change Trigger operation from the beginning of the journal entry specific data. Contains hex zeros if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG. |
119 | Length of trigger name | Bin (15) | Length of the trigger name for a Change Trigger operation. Contains 0 if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG. |
121 | Offset to trigger name | Bin (31) | The offset to the trigger name for a Change Trigger operation from the beginning of the journal entry specific data. Contains hex zeros if the Change Trigger operation includes multiple triggers. This field is not applicable if the entry type is not TG. |
These fields only exist in V5R4 or later journal entries. | |||
125 | Object attribute | Char (10) | OIR attribute of the object (for example: PF, LF, etc.) |
135 | Number of based on physical files | Bin (15) | Number of based on physical files. This field is only applicable to logical file CT entries. |
137 | Offset to name of first based on physical file | Bin (31) | Offset to 20 byte field consisting of a 10 byte
file name followed by 10 byte library name. The file name is the first
based on physical file of the logical file. The offset is from the
beginning of the journal entry specific data. Note:
This field
is only applicable for logical file CT entries. |
141 | Next offset | Bin (15) | Offset from start of prior based on file name
to the next based on file name. Note:
This field is only applicable
for logical file CT entries. |
143 | Not logged indicator | Char (1) | This entry applies only to CT (create database
file) and CG (change database file) entries.
For a CT entry, journaling will be started for the members when the transaction is committed. For a CG entry, journaling was ended for the members and will be restarted when the transaction is committed or rolled back. |
144 | Source file indicator | Char (1) |
|
145 | Internal data | Char(*) | Internal system information |
Notes:
|
Object restored (B FR, D DZ, E EL, F MR, J RR, Q QZ, Y YZ) and receiver saved (J RS) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Journal identifier (JOJID) | Char (10) | Records for the entries will have a journal identifier. The JID is not provided with the *TYPE1, *TYPE2, and *TYPE3 formats. It can be used with the QJORJIDI API. | |
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Media type | Char (3) | The type of media used for the save or restore operation:
|
4 | First volume ID | Char (6) | The ID of the first volume used. The optical volume ID might contain up to 32 characters of which the first six characters are displayed. |
10 | Start save or restore date | Char (6)1 | The date the save or restore operation was started. The date is in the format of the DATFMT attribute of the job that performed the save or restore operation. |
16 | Start save or restore time | Zoned (6,0) | The time the save or restore operation was started. |
22 | Update history | Char (1) | Whether the save history is updated:
|
23 | Save file name | Char (10) | The name of the save file used for the operation. This field is blank if a save file was not used. |
33 | Save file library | Char (10) | The name of the library for the save file. This field is blank if a save file was not used. |
43 | Media file identifier2 | Char (16) | File identifier for the integrated file system object on the media. This applies only to B FR entries. |
59 | Restored file identifier | Char (16) | File identifier for the restored integrated file system object. This applies only to B FR entries. |
75 | Restored over file identifier | Char (16) | File identifier for the integrated file system object that was restored over. This applies only to B FR entries. |
Note:
|
Object saved (B FS, D DH, E ES, F MS, Q QY, Y YS) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Media type | Char (3) | The type of media used to save the object:
|
4 | First volume ID | Char (6) | The ID of the first volume used to save the object. The optical volume ID might contain up to 32 characters of which the first six characters are displayed. |
10 | Start save date | Char (6) 1 | The date the save operation was started. The date is in the format of the DATFMT attribute of the job that saved the object. |
16 | Start save time | Zoned (6,0) | The time the save operation was started. |
22 | Update history | Char (1) | Whether the save history is updated:
|
23 | Save file name | Char (10) | The name of the save file used for the operation. This field is blank if a save file was not used. |
33 | Save file library | Char (10) | The name of the library for the save file. This field is blank if a save file was not used. |
43 | Save active value | Char (10) | The value specified for the SAVACT parameter on the SAVOBJ, SAVCHGOBJ, SAV, or SAVLIB command. |
53 | Start save active date | Char (6) 1 | For a save-while-active operation, this is the date when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start date. |
59 | Start save active time | Zoned (6,0) | For a save-while-active operation, this is the time when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start time. |
65 | Primary receiver name | Char (10) | The name of the first of dual receivers that contains the start-of-save entry. |
75 | Primary receiver Library | Char (10) | The name of the library containing the primary receiver. |
85 | Dual receiver name | Char (10) | The name of the second of dual receivers that contains the start-of-save entry. This entry is blank if only a single receiver was used when the start-of-save entry was added. |
95 | Dual receiver library | Char (10) | The name of the library containing the dual receiver. This entry is blank if only a single receiver was used when the start-of-save entry was added. |
105 | Sequence number of matching start-of-save entry | Zoned (10, 0) | For a save-while-active operation, the sequence number of the corresponding start-of-save entry. For a normal save operation, this is the sequence number of the current object saved entry. A -1 is returned if the sequence number is greater than 9 999 999 999. If -1, see Large sequence number of matching start-of-save entry. |
115 | File ID of object or reserved | Char (16) | The file identifier for the object for B FS entries, otherwise blank.4 |
131 | Large sequence number of matching start-of-save entry | Char (20) | For a save-while-active operation, the sequence number of the corresponding start-of-save entry. For a normal save operation, this is the sequence number of the current object saved entry. |
151 | Library ASP device | Char (10) | The ASP device on which the library that contains the primary receiver resides. |
161 | Contents saved | Char(1) | Whether the contents of the data queue were
saved:
Note: This field only applies to Q QY entries.
|
Notes:
|
Ownership change (E ZO, J ZO, Q ZO, Y ZO) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Old owner | Char (10) | The name of the old owner. |
11 | New owner | Char (10) | The name of the new owner. |
Prepare commit (C PC) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Reserved | Char (1) | Reserved field |
2 | Journal count | Bin (16) | The number of journals on this system that participated in the transaction |
Received data queue, has key (Q QL) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Reserved | Char (18) | Reserved for future use. |
19 | Key length | Bin (16) | The number of characters in the key. |
21 | Key order | Char (2) | The Key order is as follows:
|
23 | Key | Char (*) | The data to be used to receive a message from the data queue. |
ROLLBACK (C RB) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Job name (JOJOB) | Char (10) | Blank if the entry was added during an IPL vary on of an independent disk pool. | |
Program name (JOPGM) | Char (10) | Blank if the entry was added during an IPL or vary on of an independent disk pool. | |
Flag (JOFLAG) | Char (1) | How the rollback operation was initiated and whether it was
successful:
|
Rollback ended early (C CN, F C1) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | User profile | Char (10) | The user profile that requested to end the rollback. |
11 | Process | Char (26) | The process that requested to end the rollback. |
RGZPFM (F RG) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | File name | Char (10) | The name of the file specified for the KEYFILE parameter on the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank. |
11 | Library name | Char (10) | The name of the library specified in the KEYFILE parameter of the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank. |
21 | Member name | Char (10) | The name of the member specified in the KEYFILE parameter of the RGZPFM command. If KEYFILE(*NONE) was specified, this field is blank. |
Savepoint released (C SQ) and savepoint rolled back (C SU) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Sequence number | Char (20) | The sequence number where the savepoint was established |
Send data queue, has key (Q QK) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Data length | Bin (32) | The length of the Data field (which is the last field in the ESD of this journal entry). When replicating a data queue entry with this journal entry, this length field should be specified on the QSNDDTAQ API in association with the Data field below. See the details in the description of the Data field. |
5 | Offset to data | Bin (32) | Offset to the Data field (which is the last field in the ESD of this journal entry). The offset is calculated from the beginning of the entry-specific data (ESD). |
9 | Reserved | Char (2) | Reserved for future use. |
11 | Key length | Bin (16) | The number of characters in a key. |
13 | Reserved | Char (4) | Reserved for future use. |
17 | Key | Char (*) | A prefix added to an entry by its sender. |
Reserved | Char (*) | Padding to align fields. | |
Offset to data | Data | Char (*) | The first 16 bytes of the Data field are API information required by the Send Data Queue (QSNDDTAQ) API. When replicating a data queue entry with this journal entry, this entire Data field (including the 16 bytes of API information) must be passed to the QSNDDTAQ API when it is called with parameter eight (Data is from a journal entry) set to *YES. These 16 bytes are not placed on the data queue. The remainder of the Data field is placed on the data queue. |
Send data queue, no key (Q QS) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Reserved | Char (28) | Reserved for future use. |
29 | Data length | Bin (32) | The length of the Data field (which is the last field in the ESD of this journal entry). When replicating a data queue entry with this journal entry, this length field should be specified on the QSNDDTAQ API in association with the Data field below. See the details in the description of the Data field. |
33 | Data | Char (*) | The first 16 bytes of the Data field are API information required by the Send Data Queue (QSNDDTAQ) API. When replicating a data queue entry with this journal entry, this entire Data field (including the 16 bytes of API information) must be passed to the QSNDDTAQ API when it is called with parameter eight (Data is from a journal entry) set to *YES. These 16 bytes are not placed on the data queue. The remainder of the Data field is placed on the data queue. |
Start of save-while-active (B FW, D DW, E EW, F SS, Q QX, Y YW) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Media type | Char (3) | The type of media used to save the object:
|
4 | First volume ID | Char (6) | The ID of the first volume used to save the object. The optical volume ID might contain up to 32 characters of which the first six characters are displayed. This field will be blank for the Y YW entry. |
10 | Start save date | Char (6) 1 | The date the save operation was started. The date is in the format of the DATFMT attribute of the job that saved the object. |
16 | Start save Time | Zoned (6,0) | The time the save operation was started. |
22 | Update history | Char (1) | Whether the save history is updated:
|
23 | Save file name | Char (10) | The name of the save file used for the operation. This field is blank if a save file was not used. |
33 | Save file library | Char (10) | The name of the library for the save file. This field is blank if a save file was not used. |
43 | Save active value | Char (10) | The value specified for the SAVACT parameter on the SAVOBJ, SAVCHGOBJ, SAV, or SAVLIB command. |
53 | Save active date | Char (6)1 | For a save-while-active operation, this is the date when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start date. |
59 | Save active Time | Char (6) | For a save-while-active operation, this is the time when checkpoint processing was completed for the object. For a normal save operation, this is the same as the start time. |
65 | Object file ID4 | Char (16) | The file identifier of the integrated file system object. This applies only to B FW entries. |
Notes:
|
Start journal (B JT, D JF, E EG, F JM, Q QB) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Specific values for this entry type: | |||
Flag (JOFLAG) | Char (1) | Indicates the type of images selected:
|
|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Omit journal entry | Char (1) | Indicates the value of the OMTJRNE parameter on the Start Journal
command.
|
2 | New object inherit journaling | Char (1) | Specifies whether journaling starts automatically for new objects
created in the directory.
|
3 | Remote journal filter | Char (1) |
|
4 | Reserved | Char (5) | Reserved field |
9 | File identifier | Char (16) | The file identifier for the integrated file system object. This only applies to B JT entries. |
25 | Path name | Char (*) | The path name information optionally follows the file identifier. This only applies to BJT entries. |
Usage limit changed (L LL) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Product ID | Char (7) | The ID of the product whose usage limit was changed. |
8 | License term | Char (6) | The term of the license. |
14 | Feature | Char (4) | The product feature code. |
18 | Previous usage limit | Zoned (6,0) | The usage limit before the change. |
24 | Current usage limit | Zoned (6,0) | The usage limit after the change. |
30 | Old expiration date | Char (7) | The expiration date before the change. |
37 | New expiration date | Char (7) | The expiration date after the change. |
Usage limit exceeded (L LU) journal entry
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Product ID | Char (7) | The ID of the product whose usage limit was exceeded. |
8 | License term | Char (6) | The term of the license. |
14 | Feature | Char (4) | The product feature code. |
18 | Usage limit | Zoned (6,0) | The usage limit for the product. |
24 | Request flag | Char (1) | Whether the request was successful:
|
25 | Number of licensed users | Zoned (6,0) | The number of users currently licensed for the product. |
31 | Licensed user name | Char (26) x 100 | The names of up to 100 users who are licensed for the product. |
Update data area (E EA, E EB) journal entries
Relative offset | Field | Format | Description |
---|---|---|---|
Entry-specific data. This data appears as one field in the standard output formats: | |||
1 | Starting position | Bin (32) | Starting position of change as specified by the user (1 for decimal). |
5 | Length of change | Bin (32) | Length of change to be applied as specified by the user. |
9 | Number | Bin (32) | Number of decimal positions as specified by the user. |
13 | Offset to change | Bin (32) | Offset to change value field from the beginning of the entry-specific data (ESD). |
17 | Type | Char (10) | Type of data area. Data area types are *CHAR, *DEC, and *LGL. |
Padding for alignment | Char (*) | Padding to align fields. | |
Offset to change | Change value | Char (*) | Value of the change. |
Common fields
The following tables contain fields of entry-specific data that are common to more than one journal entry layout.
Journal information
This table contains entry-specific data for journal information. For an explanation of these fields, see the Get Attributes (Qp0lGetAttr()) API.
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Journaling status | Char (1) | Indicates whether the object is journaled. |
2 | Options | Char (1) | The journaling options or attributes. |
3 | JID | Char (10) | The journal identifier. |
13 | Journal name | Char (10) | The journal name. |
23 | Journal library | Char (10) | The journal library. |
33 | Time journaling was last started | Bin (32) | Time journaling was last started. |
Object name
This table contains entry-specific data for the name of an integrated file system object. For more information about the object name see Path name format in the API topic.
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Length | Bin (32) | The length of the object name field. |
5 | Path name CCSID | Bin (31) | The coded character set identifier (CCSID) for the object name. |
9 | Object name country ID | Char (2) | The country identifier for national language support. |
11 | Object name language ID | Char (3) | The language identifier for national language support. |
14 | Reserved | Char (3) | Reserved. This field contains all hex zeros. |
17 | Object name | Char (*) | The object name. The field is of variable length. |
Path name
This table contains entry-specific data for the path name of an integrated file system object. For more information about the path name see Path name format in the API topic.
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Path indicator | Char (1) | The absolute or relative path indicator. This field uses one
of the following values:
|
2 | Relative directory FID | Char (16) | If the path indicator is 1, this is the file identifier for the directory that contains the object indicated in the path name field. Otherwise, this will be zeros. |
18 | Path name CCSID | Bin (31) | The coded character set identifier (CCSID) for the path name. |
22 | Path name country ID | Char (2) | The country identifier for national language support. |
24 | Path name language ID | Char (3) | The language identifier for national language support. |
27 | Reserved | Char (3) | Reserved. This field contains all hex zeros. |
30 | Path name type | Bin (32) | The path name type uses one of the following values:
|
34 | Path length | Bin (31) | The path length. |
38 | Path name delimiter | Char (2) | The path name delimiter. |
40 | Reserved | Char (10) | Reserved. Set to blanks. |
50 | Path name | Char (*) | The object path name. This field is of variable length. |
Private authority information
This table contains entry-specific data for the private authority information that has been set for an integrated file system object when an object is created.
Relative offset | Field | Format | Description |
---|---|---|---|
1 | User name | Char (10) | The name of the user profile whose authority is being granted. |
11 | Operation type | Char (3) | GRT = Grant authority. |
14 | Reserved | Char (7) | Reserved. Set to zeros. |
21 | Private authority | Char (12) | Private authorities assigned to the given user profile. |
Private authorities for specified profile
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Object existence authority | Char (1) |
|
2 | Object management authority | Char (1) |
|
3 | Object operational authority | Char (1) |
|
4 | Object alter authority | Char (1) |
|
5 | Object reference authority | Char (1) |
|
6 | Read authority | Char (1) |
|
7 | Add authority | Char (1) |
|
8 | Update authority | Char (1) |
|
9 | Delete authority | Char (1) |
|
10 | Exclude authority | Char (1) |
|
11 | Execute authority | Char (1) |
|
12 | Reserved | Char (1) | Reserved. Set to blank. |
Symbolic link contents
Relative offset | Field | Format | Description |
---|---|---|---|
1 | Contents included | Char (1) | Indicates if the entire symbolic link contents are included
in the Contents field. The possible values are:
|
2 | Contents CCSID | Bin (31) | The coded character set identifier (CCSID) for the symbolic link contents. |
6 | Contents country ID | Char (2) | The country identifier for national language support for the symbolic link contents. |
8 | Contents language ID | Char (3) | The language identifier for national language support for the symbolic link contents. |
11 | Reserved | Char (3) | Reserved. This field contains all hex zeros. |
14 | Contents path type | Bin (32) | The possible values for the contents path type are:
|
18 | Contents path length | Bin (31) | The path length for the symbolic link contents. |
22 | Contents path name delimiter | Char (2) | The path name delimiter for the symbolic link contents. |
24 | Reserved | Char (10) | Reserved. This field contains all hex zeros. |
34 | Symbolic link contents | Char (*) | The symbolic link contents. This field is of variable length. |