jnledit (Edit and output unload journal files or global archive unload journal files)

-e edit-type~<<f>>

Specifies the editing type:

r: Edit in units of records

b: Edit in units of blocks

f: Output a file listing

-t [begin][,end]

Specifies the editing range in terms of the journal block output begin and end times. In "begin", specify the edit start time. In "end", specify the edit end time. When r is specified for the -e option, journal record output times must be specified; when b is specified, journal block output times must be specified.

For begin, specify a time between 00:00:00 on January 1, 1970 and the current year, month, day, and time.

The start time and end time cannot both be omitted. When the start time is omitted, the editing range is from the beginning of the file to the specified end time. When the end time is omitted, the editing range is from the specified start time to the end of the file.

The begin and end times are expressed in the format hhmmss[MMDD[YYYY]]:

hh: Hour ((00 hh 23); cannot be omitted

mm: Minute (00 mm 59); cannot be omitted

ss: Second (00 ss 59): cannot be omitted

MM: Month (01 MM 12); can be omitted^#

DD: Day (01 DD 31); can be omitted^#

YYYY: Year (4-digit year from 1970); can be omitted^#

#: If the year is omitted from the begin or end time, the specified month, day, and time of the current year are assumed. If the year, month, and day are omitted, the current year, month, and day, and the specified time are assumed. You cannot omit only the month and day, or the month or the day. Doing so causes an option error. If you want to omit the month or the day, then omit the year, the month, and the day (all three).

If the -t option is omitted, all information in the specified file is edited and output.

-j record-type

Specifies the type of journal records to be edited.

Following are the specification values for the record types:

Record type	Specification	Description	Remarks
PJ	p	Transaction commit processing startup information	Synchronous point journal
HJ	h	Transaction temporary synchronous point information
BJ	b	Transaction rollback information
TJ	t	Transaction synchronous point processing termination information
DJ	d	Heuristic decision information
FJ	f	DAM file update information	Recovery journal
CJ	c	Update information for a table subject to recovery
XJ	x	System service-specific recovery information
SJ	s	System statistics	Statistical journal
AJ	a	Send completion information
IJ	I	Messages cataloged into the input queue
OJ	o	Messages cataloged into the output queue
MJ	m	Message journal
GJ	g	Receive information
UJ	u	User-specific information	User journal

When this option is omitted, all journal record types become subject to editing.

-s server-name~<1-8 alphanumeric characters>

Specifies the name of a server whose contents are to be edited.

When this option is omitted, all servers are subject to editing.

-v service-name~<1-31 alphanumeric characters>

Specifies the name of a service whose contents are to be edited.

When this option is omitted, all services become subject to editing.

-u transaction-global-identifier [, transaction-branch-identifier]~<33 alphanumeric characters, special character, and hexadecimal digits>

Specifies the transaction identifier of a transaction whose contents are to be edited. The transaction identifier must be specified in the format "transaction-global-identifier, transaction-branch-identifier".

When specification of a transaction identifier is omitted, all transaction identifiers become subject to editing.

-o journal-collection-mode

Specifies a journal collection mode. Multiple modes can be specified.

c: Edits and outputs journals in transaction test mode whose attribute is commit, or journals in MCF nontransaction test mode.

r: Edits and outputs journals in transaction test mode whose attribute is rollback.

s: Edits and outputs journals in other than online test mode.

If this option is omitted, journals in all journal collection modes are edited and output.

-m logical-terminal-name~<1-16 alphanumeric characters>

Specifies the name of the logical terminal for which the information is to be edited and output. This option takes effect when the record type is a, g, i, m, or o.

When this option is omitted, edited data is output for all the logical terminals.

-w characters~<unsigned integer> ((80-132)) <<80>>

Specifies the number of characters per line.

-l lines~<unsigned integer> ((12-256)) <<24>>

Specifies the number of output lines per page.

-c

Specifies that editing is to be in both hexadecimal and character formats.

When this option is omitted, information is edited in hexadecimal format only.

(1)-c option specified

[Figure]

This information is displayed as many times as there are specified records.

aa...aa

Unload journal file name

bbb

File type:

sys: System journal file

jar: Global archive unload journal file

cc...cc

Unload journal file creation date and time, in the format YY/MM/DD hh:mm:ss

dddddddd

Block number (8 hexadecimal digits)

eeeeeeee

Record number (8 hexadecimal digits)

ff...ff

Date and time of editing in units of records

The date and time is output in the format of year-month-day hour: minutes: seconds.microseconds (microseconds are displayed as a decimal number from 0 through 999999). However, if you edit a journal before TP1/Server Base 06-01, 0 is output as the microsecond value.

gg

Record type (2 alphabetic characters)

h

Record type: (1 alphanumeric character)

ii...ii

Journal collection mode (1-13 alphabetic characters)

jj...jj

Transaction global identifier (8 alphanumeric and special characters plus 8 hexadecimal digits)

kk...kk

Transaction branch identifier (8 alphanumeric and special characters plus 8 hexadecimal digits)

ll...ll

Journal record (32-96 hexadecimal digits and 16-32 characters)

If a journal record contains only management information, only the title is output.

mm...mm

Date and time that an MCF record is created

The date and time when the message control facility created a journal record are output.

The date and time are output in the year-month-day hour: minutes: seconds.microseconds format (microseconds is a decimal number from 0 to 999999).

nn...nn

Date and time that a transaction branch is started

The date and time are output in the year-month-day hour: minutes: seconds.microseconds format (microseconds is a decimal number from 0 to 999999).

vv-rr

Version number-revision number

yyyy

Page

(2) jnledit -e f specified

[Figure]

#1: When the file type is jar, 0x******** is displayed for the first block number and the first record number.

#2: If each generation end information is invalid or has not been set up, *...* is displayed in each of its entry.

As many files as specified are displayed.
The information in this section is displayed when the specified file is the global archive unload journal file.
The information in this section is displayed when the specified file is acquired by specifying the -t option in the jnlunlfg command.

aa...aa

File name

bb...bb

File creation date and time

ccc

Journal file type:

sys: System journal file

jar: Global archive unload journal file

dd...dd

Node identifier

eeeeeeee

Journal server run ID (8 hexadecimal digits, prefixed by 0x)

ff...ff

Usage startup date and time

gggggggg

Begin generation number (8 hexadecimal digits, prefixed by 0x)

hhhhhhhh

End generation number (8 hexadecimal digits, prefixed by 0x)

iiiiiiii

Begin block number (8 hexadecimal digits, prefixed by 0x)

jjjjjjjj

Begin record number (8 hexadecimal digits, prefixed by 0x)

kkkkkkkk

Resource name (1-8 alphanumeric characters)

llllllll

file generation number (8 hexadecimal digits, prefixed by 0x)

mmmmmmmm

Block number (8 hexadecimal digits, prefixed by 0x)

nn...nn

server-side journal data collection date and time

oo...oo

Start time and date that are specified in the -t option in the jnlunlfg command (*...* is displayed when the -t option is omitted)

pp...pp

End time and date that are specified in the -t option in the jnlunlfg command (*...* is displayed when the -t option is omitted)

vv-rr

Version number-revision number

yyyy

Page number

Message ID	Description	Output destination
KFCA02600-E	An error occurred while the unload journal file was being accessed.	Standard error output
KFCA02601-E	The unload journal file is invalid.	Standard error output
KFCA02602-E	The journal block is invalid.	Standard error output
KFCA02603-E	The journal record is invalid.	Standard error output
KFCA02604-E	Memory cannot be allocated.	Standard error output
KFCA02640-I	Help message	Standard output, standard error output
KFCA02641-E	A parameter in the jnledit command is invalid or its value exceeds the limit.	Standard error output
KFCA02642-E	The combination of options in the jnledit command is invalid.	Standard error output
KFCA02643-E	An option in the jnledit command is specified incorrectly.	Standard error output
KFCA02644-E	A file name in the jnledit command is specified incorrectly.	Standard error output

If an editing range is specified but no journal record corresponds to the specified begin or end time, the journal records between the begin and end positions are to be edited.
If an editing range is specified and no journal record corresponds to the specified begin or end time, the journal records between the begin and end positions are to be edited.
If the editing range is specified in terms of time and the start time value is greater than the end time value, the month and day or the month, day, and year must be specified so that the end time is after the start time. If the requisite information is omitted, an error occurs. If the date is omitted, the date the jnledit command is entered is assumed; therefore, if the editing range does not fit within the current day, either the month and day or the month, day, and year must be specified.
When no file name is specified, the standard input is assumed. Therefore, the input file must be specified by piping, redirecting, etc.
Editing is performed so that the total length fits within the length specified with the -w option by setting hexadecimal digits to a multiple of (8 digits x 4 blocks) and characters to a multiple of (4 characters x 4 blocks).
When editing a user journal (UJ) in units of records or blocks, the user-specified value plus 8 bytes is adjusted to fit in the 4-byte boundary, and then edited and output. If the user-specified value does not fit in the 4-byte boundary, null data follows the output user-specified data.
The data actually output by the user is 8 bytes shorter than the data length specified in the first 4 bytes of the editing data, and begins with the 8th byte of the editing data.
The number of characters you can enter in this command is determined by your OS. If the number of entered characters exceeds the upper limit, an error occurs.
An error occurs when the number of opened files exceeds the maximum number of files that can be opened for one process, including when the specified number of files is less than 256.