
	Version 7.4.4	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

Command Log Formats

This document provides the two command log formats that Adabas supports.

The first format (invoked by CLOGLAYOUT=4) has been in use since Adabas version 4.

The second format (invoked by CLOGLAYOUT=5) is supported only in versions 5.2 and above and is the default format. It includes additional information.

The tables in this appendix refer to the following command types:

Update	A1/A4, E1/E4, N1/N2
Simple	All non-update commands with a single search argument.
Complex	All non-update commands with more than one search argument.

The command type field may contain other information that is unrelated to commands. The flags should therefore be tested with a binary mask

B'xxxx xusc'

where "u" is the update flag bit, "s" is the simple flag bit, and "c" is the complex flag bit.

CLOGLAYOUT=4

Offset

Item Length/Format/Description

Hex.

Dec.

Bytes

Format

Explanation

binary

record length (inclusive)

binary

x '0000'

binary

record type (see note 1):

x '00' basic record only

x '01' includes control block

x '02' includes format buffer

x '04' includes record buffer

x '08' includes search buffer

x '10' includes value buffer

x '20' includes ISN buffer

x '40' includes I/O list

binary

user priority (from operating system)

binary

command type flags (simple, complex, update):

x '01' simple command

x '02' complex command

x '04' update command

binary

number of posted ECBs in command queue

binary

reserved

binary

thread number

binary

number of descriptors updated

alphanumeric

job name

binary

user ID (see note 2)

binary

wall clock time (STCK-format) at the point the command processing is completed by the nucleus

binary

duration (in units of 16 microseconds)

8
(4 * 2)

binary

ASSO/DATA/WORK I/O counts for this command (except blocked ET command I/Os to WORK)

binary

Additions 2 field after command execution (can contain response subcodes)

alphanumeric

command option 1 and 2 fields

alphanumeric

command code

binary

command ID

binary

file number

binary

response code

binary

ISN

end of basic record

alpha./binary

Rest of control block starting with ISN lower limit

binary
alphanumeric

format buffer length (inclusive)
format buffer

binary
alphanumeric

record buffer length (inclusive)
record buffer

binary
alphanumeric

search buffer length (inclusive)
search buffer

binary
alphanumeric

value buffer length (inclusive)
value buffer

binary
alphanumeric

ISN buffer length (inclusive)
ISN buffer

binary

I/O list length (inclusive)

(n x 4)

binary

I/O list for this command; 4 or 5 bytes are used for each I/O operation, depending on the RABN length used in the database (RABNSIZE):

If RABNSIZE=3, byte 1 contains:

01 = Associator read

02 = Associator write

03 = Data read

04 = Data write

05 = Work read

06 = Work write

Bytes 2-4 contain the 3-byte RABN that is read or updated.

If RABNSIZE = 4, byte 1 contains:

81 = Associator read

82 = Associator write

83 = Data read

84 = Data write

85 = Work read

86 = Work write

Bytes 2-5 contain the 4-byte RABN that is read or updated.

Notes:

The value in the record type field (offset +4) determines which parts of the record mentioned above are present.
For CICS, Shadow, and Westi TP monitor users, Adabas version 5 does not provide a unique ID value in this field. Users of these TP monitors must revise programs requiring a unique ID value to obtain it from the command queue element's (CQE's) CQEUID field. User exit 4 provides the CQE address at location 12(R1).

CLOGLAYOUT=5

Explanation of Log Record Types

Command log layout 5 comprises two log record types:

the basic log record type (x'0001') is produced for all commands processed on noncluster nuclei and for those that arrive from a remote nucleus and run under internal command queue elements (ICQEs).
the asynchronous request log record type (x'0002') is created on a nucleus that sends a command to another nucleus. This record type is used in Adabas nucleus cluster environments only.

Fields with Alternate Interpretations
Remote Nucleus ID Field
Command-Executing Nucleus ID Field
Zap AY742008: Enhanced I/O-List

Fields with Alternate Interpretations

The following fields have alternate interpretations for each log record type:

for the basic log record type (x'0001'):

Offset		Item Length/Format/Description
Hex.	Dec.	Bytes	Format	Explanation
46	70	2	binary	Associator I/O operation count
48	72	2	binary	Data I/O operation count
4A	74	2	binary	Work I/O operation count

for the asynchronous request log record type (x'0002'):

Offset		Item Length/Format/Description
Hex.	Dec.	Bytes	Format	Explanation
46	70	2	binary	number of internucleus destinations
48	72	2	binary	internucleus messaging return code
4A	74	2	binary	internucleus messaging reason code

Remote Nucleus ID Field

A field has been added at offset 4C for both log record types:

Offset		Item Length/Format/Description
Hex.	Dec.	Bytes	Format	Explanation
4C	76	2	binary	the ID of the remote nucleus

For the basic log record type (x'0001') where the command originates in another nucleus, this field contains the ID of the nucleus that sent the command. It remains zero for locally-executed commands and noncluster nuclei.
For the asynchronous request log record type (x'0002'), this field contains the ID of the nucleus to which the command is sent. It is zero for implicit broadcasts (GLOBAL and SYSTEM) and contains the ID of the first destination for explicit broadcasts (list of destinations). The CLOG record contains the Adabas control block and buffers related to the first (or only) destination, and the job name and communications ID of the initiator of the request.

Command-Executing Nucleus ID Field

A field has been added at offset 58 for both log record types:

Offset		Item Length/Format/Description
Hex.	Dec.	Bytes	Format	Explanation
58	88	2	binary	the ID of the nucleus executing the command
60	90	2	-	reserved (x'0000 0000')

For both log record types, this field provides the ID of the nucleus executing the command. In a cluster environment, the nucleus ID is either the SMPID or the PLXID; in a noncluster environment, the nucleus ID is zero (0).

Zap AY742008: Enhanced I/O-List

If you apply optional zap AY742008, the enhanced I/O-List is displayed. In this case, an I/O-List element contains not only the control byte and the RABN, but also the name of the volume where the RABN resides.

With zap AY742008, the control byte is changed. The X'40' bit is switched on. Six-byte volume names are attached after the I/O list.

For example, if RABNSIZE = 3 and byte 1 contains:

41 = Associator read
42 = Associator write
...
46 = Work write

In this case, bytes 2-4 contain the three-byte RABN that is read or updated and bytes 5-10 contain the volume name where the RABN resides.

In another example, if RABNSIZE = 4 and byte 1 contains:

C1 = Associator read
C2 = Associator write
... 
C6 = Work write

Bytes 2-5 contain the four-byte RABN that is read or updated and bytes 6-11 contain the volume name where the RABN resides.

Adabas Basic Log Record Type (x'0001')

Offset

Item Length/Format/Description

Hex.

Dec.

Bytes

Format

Explanation

binary

record length (inclusive)

reserved (x '0000')

binary

og record type:

x '0001': Adabas basic log record

reserved (x '0000')

binary

time in store clock (STCK) format when request was logged

binary

buffer types:

x '00' basic record only

x'01' includes Adabas control block

x '02' includes format buffer

x '04' includes record buffer

x '08' includes search buffer

x '10' includes value buffer

x '20' includes ISN buffer

x '40' includes I/O list

x '80' includes user exit B data

binary

dispatching priority (from operating system)

binary

command type (simple, complex, update - see note):

x '01' simple command

x '02' complex command

x '04' update command

binary

number of posted ECBs in command queue

binary

thread number

binary

user buffer (UB) flag (see DSECT "UB")

binary

number of descriptors updated

alphanumeric

job name

binary

communication ID

binary

elapsed time for request in command queue (in units of 16 microseconds)

binary

unique command sequence number

binary

database ID

binary

Associator I/O operation count

binary

Data I/O operation count

binary

Work I/O operation count

binary

ID of the remote nucleus that sent the command

binary

architecture byte of caller (reserved)

reserved (x'0000 0000 00')

binary

Adabas Review

binary

ID of the nucleus executing the command

reserved (x'0000 0000')

(Beginning of Adabas control block log area:)

reserved (x'0000')

alphanumeric

command code

alphanumeric

command ID

100

binary

file number

102

binary

response code

104

binary

ISN

108

binary

ISN lower limit

112

binary

ISN quantity

116

binary

format buffer length

118

binary

record buffer length

120

binary

search buffer length

122

binary

value buffer length

124

binary

ISN buffer length

126

alphanumeric

command option 1

127

alphanumeric

command option 2

128

alphanumeric

additions 1 field

136

alphanumeric

additions 2 field (returned lengths and response subcodes)

140

alphanumeric

additions 3 field (password)

148

alphanumeric

additions 4 field (cipher code)

156

alphanumeric

additions 5 field (global format ID/OPEN: timeout values)

164

binary

command time in thread (in units of 16 microseconds)

168

binary

user area

(Beginning of optional log record area:)

172

binary
alphanumeric

format buffer length (inclusive)

174

binary
alphanumeric

record buffer length (inclusive)

176

binary
alphanumeric

search buffer length (inclusive)

178

binary
alphanumeric

value buffer length (inclusive)

180

binary
alphanumeric

ISN buffer length (inclusive)

B6...

182..

binary

I/O list length (inclusive)

(n x 4)

binary

I/O list for this command; 4 or 5 bytes are used for each I/O operation, depending on the RABN length used in the database (RABNSIZE):

If RABNSIZE = 3, byte 1 contains

01 = Associator read

02 = Associator write

03 = Data read

04 = Data write

05 = Work read

06 = Work write

Bytes 2-4 contain the 3-byte RABN that is read or updated.

If RABNSIZE = 4, byte 1 contains

81 = Associator read

82 = Associator write

83 = Data read

84 = Data write

85 = Work read

86 = Work write

Bytes 2-5 contain the 4-byte RABN that is read or updated.

Asynchronous Request Log Record Type (x'0002')

Offset

Item Length/Format/Description

Hex.

Dec.

Bytes

Format

Explanation

binary

record length (inclusive)

reserved (x '0000')

binary

log record type:

x '0002': asynchronous request log record

reserved (x '0000')

binary

time in store clock (STCK) format when request was logged

binary

buffer types:

x '00' basic record only

x'01' includes Adabas control block

x '02' includes format buffer

x '04' includes record buffer

x '08' includes search buffer

x '10' includes value buffer

x '20' includes ISN buffer

x '40' includes I/O list

x '80' includes user exit B data

binary

dispatching priority (from operating system)

binary

command type (simple, complex, update - see note):

x '01' simple command

x '02' complex command

x '04' update command

binary

number of posted ECBs in command queue

binary

thread number

binary

user buffer (UB) flag (see DSECT "UB")

binary

number of descriptors updated

alphanumeric

job name

binary

communication ID

binary

elapsed time for request in command queue (in units of 16 microseconds)

binary

unique command sequence number

binary

database ID

binary

number of internucleus destinations

binary

internucleus messaging return code

binary

internucleus messaging reason code

binary

ID of the remote nucleus to which the command is sent

binary

architecture byte of caller (reserved)

reserved (x'0000 0000 00')

binary

Adabas Review

binary

ID of the nucleus executing the command

reserved (x'0000 0000')

(Beginning of Adabas control block log area:)

reserved (x'0000')

alphanumeric

command code

alphanumeric

command ID

100

binary

file number

102

binary

response code

104

binary

ISN

108

binary

ISN lower limit

112

binary

ISN quantity

116

binary

format buffer length

118

binary

record buffer length

120

binary

search buffer length

122

binary

value buffer length

124

binary

ISN buffer length

126

alphanumeric

command option 1

127

alphanumeric

command option 2

128

alphanumeric

additions 1 field

136

alphanumeric

additions 2 field (returned lengths and response subcodes)

140

alphanumeric

additions 3 field (password)

148

alphanumeric

additions 4 field (cipher code)

156

alphanumeric

additions 5 field (global format ID/OPEN: timeout values)

164

binary

command time in thread (in units of 16 microseconds)

168

binary

user area

(Beginning of optional log record area:)

172

binary
alphanumeric

format buffer length (inclusive)

174

binary
alphanumeric

record buffer length (inclusive)

176

binary
alphanumeric

search buffer length (inclusive)

178

binary
alphanumeric

value buffer length (inclusive)

180

binary
alphanumeric

ISN buffer length (inclusive)

B6...

182..

binary

I/O list length (inclusive)

(n x 4)

binary

I/O list for this command; 4 or 5 bytes are used for each I/O operation, depending on the RABN length used in the database (RABNSIZE):

If RABNSIZE = 3, byte 1 contains:

01 = Associator read

02 = Associator write

03 = Data read

04 = Data write

05 = Work read

06 = Work write

Bytes 2-4 contain the 3-byte RABN that is read or updated.

If RABNSIZE = 4, byte 1 contains:

81 = Associator read

82 = Associator write

83 = Data read

84 = Data write

85 = Work read

86 = Work write

Bytes 2-5 contain the 4-byte RABN that is read or updated.

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT