Version 4.6.2
 —  Adabas Review Reference  —

Field Reference

This part of the documentation describes the fields that may be used when creating Adabas Review reports using the Edit Report (ER) command.

The Adabas Review field reference documentation is organized in the following topics:


Field Categories

The fields used in Adabas Review reports are grouped into the following categories:

Code Category Includes report fields . . . Special Considerations
CB Adabas Control Block Fields that correspond to or are derived from Adabas control block fields.
CLOG Adabas Command Log Fields that are derived from the Adabas command log.
CMON Client Reporting Fields that are derived from client reporting log records.
BUF Adabas Buffer Fields that correspond to segments of the format, ISN, record, search, and value buffers. When you specify a field from this category, Adabas Review automatically requires this information from the Adabas nucleus. This leads to more data to be sent from the Adabas nucleus to Adabas Review.

Note:
To limit the size of the transferred data the ADARUN REVLOGBMAX or REVLOGMAX parameters can be used. Missing data might also be associated with the setting of these parameters.

If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGxx parameter. For example, for FBSEG01 you need to specify LOGFB=YES.

IT Interval and Time Fields that establish intervals for control breaks. Fields in this category also display specific times for Adabas command processing.
I/O Adabas I/O Fields for analyzing the I/O operations that are performed against the Adabas Associator, Data Storage, and Work data sets. When you specify a field from this category, Adabas Review automatically requires this information from the Adabas nucleus. This leads to more data to be sent from the Adabas nucleus to Adabas Review and creates additional CPU overhead in the Adabas nucleus address space.

If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGIO=YES.

NAT Natural Fields for determining information about the Natural programs issuing Adabas calls. When you specify a field from this category, you must also specify the Natural profile parameter ADAPRM=ON for your Natural user working environment.

If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGCLEX=YES.

NUC Adabas Nucleus Fields for analyzing Adabas nucleus information. If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGCLEX=YES.
OS Operating System Fields for displaying operating system-related information. If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGCLEX=YES.
TP Transaction Processing Monitor Fields for displaying information about the transaction processing monitor used with applications issuing Adabas calls. If you are running Adabas Review in batch, the Adabas nucleus session that created the command log needs to run with the associated ADARUN parameter LOGCLEX=YES.
UF User Fields defined by the user that contain user-specified data for reporting. A maximum of five Adabas Review user fields can be defined, with the names USERFLD1 through USERFLD5.

Notes:

  1. References to an Adabas session pertain to a user's session with Adabas.. References to an Adabas nucleus session pertain to the duration that Adabas is active. When Natural utilities issue Adabas calls, the values of NATLIB, NATPROG, and NATSTMT do not denote user applications objects.
  2. When a Natural object is invoked by means of a CALLNAT, PERFORM or FETCH statement, Natural may generate Adabas calls to load the invoked programming object into the buffer pool. In such a situation, the value of may be incorrect. Ignore Adabas calls to FNAT and FUSER to avoid misinterpretation of the value.
  3. When a program is executed by means of the RUN command, the values of NATLIB, NATPROG and NATSTMT may be incorrect, because it is e.g. possible to RUN a nameless object from within the Natural program editor. Use the EXECUTE command to obtain correct values When a Natural programming object contains copy codes, NATSTMT may contain the line number within a copy code.

Top of page

Alphabetic Listing

The following alphabetic listing of all reporting fields also indicates the category, field length, and the format (B=binary, C=alphanumeric, and T=the first four bytes of store clock value) of each field.

Note:
Descriptions of each field can be found in the category field listings. Click on the category name in the following tables to find the description of the field.

A C E G I L N P R T V Y
B D F H J M O Q S U W Number

-A-

Field System Name Category Field Length Format Alternate Names Description
ABALLOC NUC 4 B The number of bytes of attached buffer space currently used. An attached buffer is an internal buffer used for interregion communication.
ABDATE NUC 8 C The date (in YYYY-MM-DD format) when the attached buffer high-water mark was reached.
ABENT NUC 4 B The current number of attached buffer entries.
ABPCT NUC 4 B The maximum percentage of attached buffer space used during the Adabas nucleus session.
ABSIZE NUC 4 B The total amount (in bytes) of attached buffer space allocated at Adabas nucleus startup.
ABTIME NUC 8 C The time (in HH:MM:SS format) that the attached buffer high-water mark was reached.
ABUSED NUC 4 B The maximum number (in bytes) of attached buffer space used during the Adabas nucleus session.
ACBUSER CB 4 B This field, comprising the last four bytes of the ACB, contains user data that is passed with the Adabas call. It is referred to as the user area field in the ACB, and is neither used nor modified by Adabas.
ACCTINF2 OS 16 C Accounting information about the user that issued the Adabas call for z/OS batch jobs. This field will contain the second value specified in the account field of the job card.
ACCTINFO OS 16 C Accounting information about the user that issued the Adabas call.
For z/OS batch jobs, the field will contain the first value specified in the account field of the job card.
For Com-plete users, the field will contain the account information specified in the user's Com-plete profile.
ACINAME TP 8 C CURENPGM The program name of the Adabas CICS link routine for the DCI interface: ADADCI.
ADADURA IT 4 B Adabas duration. Corresponds to the DURATION field. This field contains the amount of time (in seconds) that the command spent in the Adabas thread, including the time spent waiting for the completion of I/O operations. The ADADURA field differs from the DURATION and ORGDURA fields in that the time is computed to 6 decimal places instead of 4 decimal places.
AD1 CB 8 B ADD1

ADDIT1

Alternate name for ADDIT1.
AD2 CB 4 B ADD2

ADDIT2

Alternate name for ADDIT2.
AD3 CB 8 B ADD3

ADDIT3

Alternate name for ADDIT3.
AD4 CB 8 B ADD4

ADDIT4

Alternate name for ADDIT4.
AD5 CB 8 B ADD5

ADDIT5

Alternate name for ADDIT5.
ADD1 CB 8 B AD1

ADDIT1

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT1.
ADD2 CB 4 B AD2

ADDIT2

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT2.
ADD3 CB 8 B AD3

ADDIT3

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT3.
ADD4 CB 8 B AD4

ADDIT4

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT4.
ADD5 CB 8 B AD5

ADDIT5

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT5.
ADDIT1 CB 8 B ADD1 (used in summary record)

AD1

Corresponds to the ACB field additions 1. The command to be executed determines whether this field is used and what the contents represent.
ADDIT2 CB 4 B ADD2 (used in summary record)

AD2

Corresponds to the ACB field additions 2. The command to be executed determines whether this field is used and what the contents represent.

When ADARUN parameter CLOGLAYOUT is set to 8, the content of this field is taken from the ACBX structure. Note that there are differences in meaning of the Additions 2 field in the ACBX and in the ACB.

In the ACBX, some information that was formally available in the Additions 2 field is now split into several fields. For example, the error-related subcode information that was originally provided in the Additions 2 in the ACB is now provided in the Adabas ACBXSUBS (Subcomponent Response Subcode) field. The Additions 2 field will contain the transaction sequence number for an OP (open) and RE (read ET data) command. In Adabas Review, if the ADARUN parameter CLOGLAYOUT is set to 8, you will find the information from the older ACB Additions 2 structure in the following separate Adabas Review fields:

  • CMPRECL contains the compressed record length.

  • ERRFLDNM contains the error field name.

  • RSPSUB contains the subcode for an Adabas response code.

  • UCMPRECL contains the uncompressed record length.

ADDIT3 CB 8 B ADD3 (used in summary record)

AD3

Corresponds to the ACB field additions 3. The command to be executed determines whether this field is used and what the contents represent.
ADDIT4 CB 8 B ADD4 (used in summary record)

AD4

Corresponds to the ACB field additions 4. The command to be executed determines whether this field is used and what the contents represent.
ADDIT5 CB 8 B ADD5 (used in summary record)

AD5

Corresponds to the ACB field additions 5. The command to be executed determines whether this field is used and what the contents represent.
ASSOIO CLOG 2 B ASSO-IO The number of asynchronous Associator read I/Os for this command.
ASSO-IO CLOG 2 B ASSOIO Alternate name for ASSOIO.
ASSOREAD I/O 4 B ---- Associator read. The total number of Associator read I/Os that occurred during the Adabas session. This value is updated every minute and not when each command is issued.
ASSOWRIT I/O 4 B Associator write. The total number of Associator write I/Os that occurred during the Adabas session. This value is updated every minute and not when each command is issued.

-B-

Field System Name Category Field Length Format Alternate Names Description
BUFFEFF NUC 4 B Buffer efficiency. Contains the ratio of the number of calls to the Adabas buffer pool manager to the number of Adabas physical read requests made to the Associator and the Data Storage devices. For example, if the number of read I/Os is 100 and the number of calls to the buffer pool manager is 500, the buffer efficiency is 500/100 or 5. The higher the buffer efficiency number, the more efficient is the use of buffer space. If the buffer efficiency number is low, it is recommended that you increase the LBP (length of buffer pool) ADARUN parameter.
BUFFLUSH NUC 4 B The number of times that the Adabas buffer pool (LBP) was flushed during the Adabas nucleus session.
BUFFWAIT NUC 4 B The number of times that Adabas Review had to wait for a buffer.

-C-

Field System Name Category Field Length Format Alternate Names Description
CALLPGM TP 8 C The program that executed the last EXEC CICS LINK or XCTL command.
  • In non-DCI situations, this is the program calling the Adabas CICS link routine via EXEC CICS LINK

  • In DCI interface situations (used by Natural), this is the name of the executing program if there was no previous EXEC CICS LINK or, if there was a previous EXEC CICS LINK, the name of the program that executed the last EXEC CICS LINK.

CALLTYPE CLOG 8 C Contains the type of the Adabas call that was issued. Possible values are:
  • "PHYSICAL": indicates a standard Adabas call

  • "REMOTE": indicates a call arriving via Entire Net-Work.

CDURA CMON 8 B The total client duration time. This is the total time (in seconds) in which the client waits for the command to be processed by the server and the time it takes the ADALNK portion of the client to retrieve the command results. CDURA is the sum of the CRCVDURA and CWRKDURA fields.

Measurement for this field starts immediately after the command is passed to the server (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 router processing is performed). Measurement stops when the client picks up the command result information from the server (performing SVC-16 router processing within the Adabas link routine).

CID CB 8 C Corresponds to the hexadecimal value of the ACB field command ID. This field serves important functions, determined by the command, during command execution. For example, during a sequential read, the command ID is used to return the records to the user in the proper sequence. This field displays the value of the CID in hexadecimal format (for example, if CID=ABCD, it is displayed in this field as "C1C2C3C4").
CIDALPHA CB 4 C Corresponds to the alphanumeric value of the ACB field command ID. This field serves important functions, determined by the command, during command execution. For example, during a sequential read, the command ID is used to return the records to the user in the proper sequence. This field displays the value of the CID in alphanumeric format.
CMD CB 2 C COMMAND Corresponds to the ACB field command code.
CMDNAME CB 14 C CNAME A translation of the 2-byte Adabas command code to a 14-byte string. For example, the command code BT is translated to "Backout Trans".
CMDRESP CB 4 B CMDRSP

MCR

The time, in milliseconds, required to process the Adabas call. In the command table, Adabas Review stores the minimum Adabas duration for each command type returning a zero response code. The command table is updated whenever a lower duration value is encountered. Command response time is thus based on the command time field in the Adabas command log.

The values for CMDRESP in the history file are automatically stored in seconds. To display them correctly, they must be converted to milliseconds. For more information on this conversion, read Migration from Previous Versions .

If you need to continue using the old scale and the old calculation algorithm for history data, contact your Software AG support representative.

Due to changes in the display programs in SYSREVDB, you cannot use SYSREVDB in Adabas Review 4.4 (or earlier versions) to display the field contents of CMDRESP correctly, unless you stay with the old scale and algorithm.

CMDRSP CB 4 B CMDRESP

MCR

Alternate name for CMDRESP.
CMDSTAT CB 8 C Contains the Adabas internal status for an Adabas command. For example, the Adabas command L3 has an internal status of SIMPLE and S1 has an internal status of COMPLEX.
CMDTYPE CLOG 1 B TYPECMD

CMD-TYPE

The 1-byte command type field of the Adabas command log record that describes the internal Adabas status for the command. For example, a command type of 01 is a simple command and a command type of 42 is a complex command. The CMDSTAT field provides this translation.
CMD-TYPE CLOG 1 B CMDTYPE

TYPECMD

Alternate name for CMDTYPE.
CMPRECL CB 2 B Contains the compressed record length of the record returned by a READ or a FIND command.
CNAME CB 14 C CMDNAME Alternate name for CMDNAME.
COMMAND CB 2 C CMD Alternate name for CMD.
COMMANDS CB 8 B The number of Adabas commands processed for the control break.
COP1 CB 1 C OP1 Corresponds to the ACB field command option 1. The contents of this field is determined by the command being issued.
COP2 CB 1 C OP2 Corresponds to the ACB field command option 2. The contents of this field is determined by the command being issued.
CPUID OS 8 B The internal identifying serial number of the CPU from which the Adabas call was issued.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

CQALLOC NUC 4 B The number of bytes of command queue space currently used.
CQDATE NUC 8 C The date (in YYYY-MM-DD format) when the command queue high-water mark was reached.
CQDURA IT 4 B Command queue duration. Contains the amount of time (in seconds) that a command waited in the command queue before being dispatched into an Adabas thread.
CQENT NUC 4 B The current number of command queue entries.
CQEUID TP 28 B Contains the 28-byte Adabas communication user ID for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

CQJOB NUC 8 C The job or started task name for the user obtained from the user's command queue element.
CQMAXENT NUC 4 B The maximum number of entries that have been in the command queue for the Adabas nucleus session.
CQPCT NUC 4 B The maximum percentage of command queue space used during the Adabas nucleus session.
CQSIZE NUC 4 B The total number of bytes of command queue space allocated at Adabas nucleus startup.
CQTIME NUC 8 B The time (in HH:MM:SS format) when the command queue high-water mark was reached.
CQUQADDR NUC 8 B The address of the User Queue Element found in the CQE.
CQUSED NUC 4 B The maximum number of bytes of command queue space used during the Adabas nucleus session.
CRCVDURA CMON 8 B The client receive time. This is the time (in seconds) it takes the Adabas link routine to retrieve a processed command from the server.

Measurement for this field starts immediately after the server posts the Adabas link routine to retrieve the command result information (performing SVC-12 router processing) . Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-16 router processing).

CURENPGM TP 8 C ACINAME Alternate name for ACINAME.
CWRKDURA CMON 8 B The client wait time, or the time in which the server works for the client. This is the time (in seconds) in which the client waits for the command to be processed by the server.

Measurement for this field starts immediately after the command is passed to the server for processing (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 processing is performed). Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-12 router processing).

-D-

Field System Name Category Field Length Format Alternate Names Description
DATAIO CLOG 2 B DATA-IO The number of asynchronous Data Storage read I/Os for this command.
DATA-IO CLOG 2 B DATAIO Alternate name for DATAIO.
DATAREAD I/O 4 B The total number of Adabas Data Storage read I/Os for the Adabas session. This value is updated every minute and not when each command is issued.
DATAWRIT I/O 4 B The total number of Adabas Data Storage write I/Os for the Adabas session. This value is updated every minute and not when each command is issued.
DATE IT 8 C The date (in YYYY-MM-DD format) when the Adabas command was processed.
DAY IT 1 B The day number (within a month) when the Adabas command was processed.
DBID CB 2 B The unique Adabas database identification number.
DBNAME NUC 16 C The 16-character name assigned to the database when it was created.
DES CLOG 2 B DESUPD Alternate name for DESUPD.
DESUPD CLOG 2 B DES Contains the number of descriptors that were updated for an Adabas call.
DUR CLOG 4 B DURATION

DURAT

Alternate name for DURATION.
DURAT CLOG 4 B DURATION

DUR

Alternate name for DURATION.
DURATION CLOG 4 B DURAT

DUR

The amount of time that the command spent in the Adabas thread, including time spent waiting for I/O operations to complete. This field is expressed in seconds and is accurate to 4 decimal places. The field ADADURA contains the same value accurate to 6 decimal places.

-E-

Field System Name Category Field Length Format Alternate Names Description
ENDDATE IT 4 T The date (in YYYY-MM-DD format) when the last Adabas command was processed within the current report control break.
ENDTIME IT 4 T The time (in 24-hour format) when the last Adabas command was processed within the current report control break.
ERRFLDNM CB 2 C Error field name. Contains the Adabas 2-character name for a field that has been found to be in error in the Adabas format or search buffer.
ESTCPU IT 6.6 N --- The estimated CPU time used by each Adabas command. The values shown in this field are only relative approximations of the CPU time used; they are not based on any actual CPU times and are calculated, instead, based on an algorithm. The algorithm used varies for each Adabas command type and is based on the number of instructions, I/Os, descriptors, and fields used.

This field can be used as a SUM, MIN, MAX and/or AVG field.

ETID TP 8 C The Adabas ET (end transaction) ID that was established during the OP (open) call to Adabas. The contents of the field is determined by the calling program.

If the first character provided for the ETID is smaller than "A" through "9", Adabas Review will show null value (blanks) in this field. If the first character is in the range "A" through "9", but the following characters are nonprintable characters, Adabas Review will display them in alphanumeric format, which might result in blanks or special characters. To display this field in hexadecimal, an Adabas Review user field can be used.

-F-

Field System Name Category Field Length Format Alternate Names Description
FB BUF 32 C The contents of the Adabas format buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole format buffer is displayed.

The FBSEGnn field may be used to display parts of the format buffer if it is more than 32 bytes long. Only one FBSEGnn field is allowed for each report.

FBFIELDS BUF 2 C FBF Format buffer fields. Contains the Adabas 2-character name for each field contained in the Adabas format buffer. This field can only be used in Summary reports.
FBL BUF 2 B Corresponds to the ACB field format buffer length. The contents of this field is determined by the Adabas command issued.
FBSEGnn BUF 64 C Represents a format buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field FBSEG01 you obtain the first 64 bytes of the format buffer. The segment number may be a value between 01 and 32, inclusive. The field FBSEGnn is available for summary reports only; use the field FB for detail reports.
FILE CB 2 B FNR (used in summary record) Corresponds to the ACB field file number. The function of this field is determined by the Adabas command being issued.
FILENAME NUC 16 C --- Contains the 16-character name assigned to the Adabas file, and is obtained from the Adabas file control block (FCB). If the file name is not available, the field contains "FCB-UNAVAILABLE".
FILETYPE NUC 6 C --- Contains the 6-character type assigned to the Adabas file. This field contains the string "USER" if the file is a user file or "SYSTEM" if the Adabas Checkpoint file was read or updated.
FNR CB 2 B FILE This name is used in the schema portion of the summary record. It is an alternate name for FILE.
FORMATOW NUC 4 B --- The total number of Adabas internal format overwrites that have occurred during the Adabas nucleus session.
FORMATTR NUC 4 B --- The total number of Adabas internal format translations that have occurred during the Adabas nucleus session.
FULLSTCK IT 8 T --- The 8-byte store clock value taken when the Adabas command was processed.

-G-

Field System Name Category Field Length Format Alternate Names Description
GLOBFMID CB 8 B --- Contains the global internal format buffer ID for the Adabas call within a sequence of Adabas calls. This field is derived from ADDIT5 field.

-H-

Field System Name Category Field Length Format Alternate Names Description
HOLDISN NUC 2 B --- The numbers of ISNs which are in HOLD status by the user at the time this command is executed. The number is obtained after the execution of this command.
HOUR IT 5 C HR The hour (in 24-hour format) when the Adabas command was processed.
HQDATE NUC 8 C --- The date (in YYYY-MM-DD format) that the hold queue high-water mark was reached.
HQENT NUC 4 B --- The current number of hold queue entries.
HQPCT NUC 4 B --- The maximum percentage of hold queue space used during the Adabas nucleus session.
HQSIZE NUC 4 B --- The total number of bytes allocated to the hold queue at Adabas nucleus startup.
HQTIME NUC 8 C --- The time (in HH:MM:SS format) that the hold queue high-water mark was reached.
HQUSED NUC 4 B --- The maximum number of bytes of hold queue space used during the Adabas nucleus session.
HQUSRENT NUC 4 B --- The number of hold queue user entries.
HR IT 5 C HOUR Alternate name for HOUR.

-I-

Field System Name Category Field Length Format Alternate Names Description
IB BUF 32 C --- The contents of the Adabas ISN buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole ISN buffer is displayed.

The IBSEGnn field may be used to display parts of the ISN buffer if it is more than 32 bytes long.

IBL BUF 2 B --- Corresponds to the ACB field ISN buffer length. The use of this field is determined by the command being issued.
IBSEGnn BUF 64 C --- Represents an ISN buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field IBSEG01, you obtain the first 64 bytes of the ISN buffer. The segment number may be a value between 01 and 32, inclusive. The field IBSEGnn is available for summary reports only; use the field IB for detail reports.
IO I/O 2 B IOS This name is used in the schema portion of the summary record. It is an alternate name for IOS.
IOS I/O 2 B IO (used in summary record) The total number of I/Os for the command processed; it is the sum of ASSOIO, DATAIO and WORKIO.
IOCOMP I/O 3 C --- Identifies the Adabas component against which the I/O was issued. For example, if the I/O is issued against Data Storage extent 1, the field contains DS1. If the I/O is issued against address converter extent 3, the field contains AC3.
IOFUNC I/O 5 C --- The type of I/O operation performed against an Adabas component. The values for this field are "READ" or "WRITE".
IOLIST I/O 10 C --- The hexadecimal I/O list for a command obtained from the Adabas command log record. Four bytes are allocated for each I/O list entry.
IOPHYS I/O 16 C --- A translation of the I/O list entry from the Adabas command log record. The format for this field is comp-x nnnnnn, where:

comp is the Adabas component (ASSO, DATA, or WORK)

x is the type of I/O, ("R" for read or "W" for write)

nnnnnn is the RABN (relative Adabas block number)

IORABN I/O 8 C --- The relative Adabas block number against which the I/O was performed.
IOTOCMD I/O 4 B --- The ratio of the total number of I/O operations performed to the total number of commands processed.
IOTYPE I/O 4 C --- Identifies the component against which the I/O operation was performed. Values for this field may be ASSO 'Associator', DATA 'Data Storage', or WORK 'Work data set'.
IOVOLSER I/O 6 C --- Contains the volume serial number against which the I/O operation was performed. This field may be used to show Adabas I/O distribution. For WORK I/Os (see the IOTYPE field) the IOVOLSER field will contain the text "UNKNWN". If the data is obtained from blocks that are stored in the Adabas buffer pool and therefore no physical I/Os are made, this field will be empty.
ISN CB 4 B --- Corresponds to the ACB field ISN. The use of this field is determined by the command being issued.
ISNLL CB 4 B --- Corresponds to the ACB field ISN lower limit. The field contains the lowest ISN that Adabas returns when retrieving ISN lists. The use of this field is determined by the command being issued.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNLL as well as ISNQ are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

ISNQ CB 4 B --- Corresponds to a modification of the ACB field ISN quantity. The field is modified based on command type, and is suitable for performing mathematical calculations such as SUM and AVERAGE. The unmodified data can be found in the ORGISNQ field.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNQ as well as ISNLL are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

-J-

Field System Name Category Field Length Format Alternate Names Description
JMREDATE OS 10 C --- The date (in YYYY-MM-DD format) when the batch job was entered in JES or from the job information macro.
JOB OS 8 C JOBNAME Alternate name for JOBNAME.
JOBCLASS OS 1 B --- (z/OS only) The one-byte character of the CLASS parameter in the job card.
JOBID OS 8 C --- A combination of the job identifier and the job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE:
  • Under z/OS, the field will contain JOB, STC, or TSU as the job identifier followed by a 5-byte JES job number.

  • Under z/VSE, the field will contain JOB as the identifier, followed by the 5-byte POWER job number.

JOBNAME OS 8 C JOB The name of the job or task from which the Adabas call was issued. This field is the contents of the JOBNAME from the Adabas command log record and may not reflect the actual JOBNAME of the task that issued the Adabas call.
JOBNUM OS 5 C --- The job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE. The field will contain an alphanumeric, 5-byte value for the JES (z/OS) or POWER (z/VSE) job number.

-L-

Field System Name Category Field Length Format Alternate Names Description
LEVEL NAT 2 B NATLEVEL Alternate name for NATLEVEL.
LFPALLOC NUC 4 B --- The number of bytes currently used in the format pool.
LFPENT NUC 4 B --- The current number of entries in the format pool.
LFPMAX NUC 4 B --- The maximum number of bytes of format pool space used during the Adabas nucleus session.
LFPPCT NUC 4 B --- The maximum percentage of format pool space used during the Adabas nucleus session.
LFPSIZE NUC 4 B --- The total number of bytes allocated to the format pool at Adabas nucleus startup.
LFPUSED NUC 4 B --- The maximum number of bytes of format pool space used during the Adabas nucleus session.
LIB NAT 8 C NATLIB Alternate name for NATLIB.
LOG NAT 8 C NATAPPL

LOGON

This name is used in the schema portion of the summary record. It is an alternate name for NATAPPL.
LOGON NAT 8 C NATAPPL

LOG (used in summary record)

Alternate name for NATAPPL.
LPARNAME OS 8 C --- The system LPAR or partition name (in z/OS or z/VSE environments) or the environment name from the job information macro (in BS2000 environments).
LUNAME OS 8 C --- The VTAM LU (logical unit) name of the user who issued the Adabas call. If the TP system is Com-plete, the LUNAME field contains the Com-plete ID:
  • The first 3 bytes of the ID represent the Com-pass stack level

  • The fourth byte is the Com-plete patch character

  • The last 4 bytes identify the Com-plete terminal ID number in hexadecimal format.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

LWPALLOC NUC 4 B --- The number of bytes of the work pool currently in use.
LWPENT NUC 4 B --- The current number of work pool entries.
LWPMAX NUC 4 B --- The maximum number of bytes of work pool space used during the Adabas nucleus session.
LWPMXENT NUC 4 B --- The maximum number of work pool entries used during the Adabas nucleus session.
LWPPCT NUC 4 B --- The maximum percentage of work pool space used during the Adabas nucleus session.
LWPSIZE NUC 4 B --- The number of bytes that were allocated to the work pool at Adabas nucleus startup.
LWPUSED NUC 4 B --- The maximum number of bytes of work pool space used during the Adabas nucleus session.

-M-

Field System Name Category Field Length Format Alternate Names Description
M15 IT 5 C 15M Alternate name for 15M.
M5 IT 5 C 5M Alternate name for 5M.
MCR CB 4 B CMDRESP

CMDRSP

Alternate name for CMDRESP.
MIN IT 5 C 1M

MINUTE

Alternate name for 1M.
MINUTE IT 5 C 1M

MIN

Alternate name for 1M.
MO IT 1 B MONTH

MON

Alternate name for MONTH.
MON IT 1 B MON

MO

Alternate name for MONTH.
MONAME IT 3 C --- The name of the month when the Adabas command was processed.
MONTH IT 1 B MON

MO

The number of the month when the Adabas command was processed.
MULTICNT NUC 8 N --- The number of multifetch records returned.

For all read calls (Lx commands), multifetch returns a group of records in the record buffer and a description of these records in either the caller's ISN buffer (for ACB interface direct calls) or the caller's multifetch buffer (for ACBX interface direct calls). Multifetch records are only returned if the ACB or ACBX call contain an <literalvalue>M</literalvalue> in Command Option 1.

-N-

Field System Name Category Field Length Format Alternate Names Description
NATAPPL NAT 8 C LOGON

LOG (used in summary record)

The Natural application name (or library) to which the user issued a LOGON. This field does not necessarily show the library of the Natural object from which the Adabas call is issued. Under SQL, this field contains the library name.
NATCLTID NAT 8 C --- NATCLTID displays the client user ID of a user using a Natural server. NATCLTID only contains a value if an RPC client request is executed in a Natural RPC server session. In all other cases the field is empty.
NATCOUNT NAT 2 B --- The total number of Adabas calls generated by the user application since the last terminal I/O.
NATEXEC NAT 2 B --- The number of times a Natural object that issues Adabas calls has been executed. NATEXEC is "1" if the Natural object has issued an Adabas call for the first time on this level; for each subsequent Adabas call on this level the value will be set to zero. You can use the SUM statement to total the values of this field to obtain the total number of times a specific Natural object has been called.
NATGRP NAT 8 C --- The current Natural security group to which the user belongs.
NATLEVEL NAT 2 B LEVEL The Natural call level of the Natural program issuing the Adabas call. For example, a CALLNAT routine that is called from a program and issues an Adabas call has a Natural level of 2.
NATLIB NAT 8 C LIB The name of the Natural library where the object is located that is currently executed.
NATPROG NAT 8 C PROGRAM

PRO (used in summary record)

The name of the Natural program that issued the Adabas call. When Natural internally issues Adabas calls to load Natural objects, this value is not updated. Under SQL, this field contains the program name.
NATRPCID NAT 16 C --- The 16-byte alphanumeric value for the store clock value used as identification of the Natural RPC Server.
NATRPCCO NAT 16 C --- The 16-byte alphanumeric value of the conversation ID from the Natural RPC Server.
NATSTMT NAT 4 C --- The Natural statement number where the Adabas command is processed. This line number is the line in the Natural program displayed by NATPROG. When the processed Adabas command is in the copy code portion of the Natural program, the line number refers to the copy code. The name of the copy code is not available at this time.
NATUID NAT 8 C --- The name of the Natural library to which the user is currently logged on. This is the value of the Natural system variable *APPLIC-ID.
NUCID NUC 3 B SMP (used in summary record) The ID of an Adabas nucleus in an Adabas Parallel Services or Adabas Cluster Services environment.

-O-

Field System Name Category Field Length Format Alternate Names Description
OP1 CB 1 C COP1 Alternate name for COP1.
OP2 CB 1 C COP2 Alternate name for COP2.
OPSYSID OS 4 B --- The operating system ID. The address of the ASCB (address space control block) for the job or task that issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

OPSYSNAM OS 8 C --- The operating system name (SYSNAME) that is specified in the SYS1.PARMLIB and which will be obtained from the CVT (in z/OS environments) or the operating system name and version number (in BS2000 environments).
ORGDURA CLOG 4 B --- The (original) value of the "duration" field contained in the command log record. The time is expressed in units of 16 microseconds.

-P-

Field System Name Category Field Length Format Alternate Names Description
PRI CLOG 1 B PRIORITY

PRIO

Alternate name for PRIORITY.
PRIO CLOG 1 B PRIORITY

PRI

Alternate name for PRIORITY.
PRIORITY CLOG 1 B PRI

PRIO

The operating system priority for the user issuing the Adabas call.
PRO NAT 8 C NATPROG

PROGRAM

This name is used in the schema portion of the summary record. It is an alternate name for NATPROG.
PROGRAM NAT 8 C NATPROG

PRO (used in summary record)

Alternate name for NATPROG.

-Q-

Field System Name Category Field Length Format Alternate Names Description
QTR IT 1 B QUARTER

QUAR

Alternate name for QUARTER.
QUAR IT 1 B QUARTER

QTR

Alternate name for QUARTER.
QUARTER IT 1 B QUAR

QTR

The quarter of the year in which the Adabas command was processed.

-R-

Field System Name Category Field Length Format Alternate Names Description
RB BUF 32 C --- The contents of the Adabas record buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole record buffer is displayed.

The RBSEGnn field may be used to display parts of the record buffer if it is more than 32 bytes long.

RBL BUF 2 B --- Corresponds to the ACB field record buffer length. The record buffer is used primarily with read, search, and update commands.
RBSEGnn BUF 64 C --- Represents a record buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field RBSEG01, you obtain the first 64 bytes of the record buffer. The segment number may be a number between 01 and 32, inclusive. The field RBSEGnn is available for summary reports only; use the field RB for detail reports.
ROUTDURA OS 8 B ROUTTIME The amount of time between the time a command was issued by the application and the time it was queued in the Adabas command queue. For Adabas 8.1 and earlier, this field is expressed in seconds; for Adabas 8.2 and later releases, this field is expressed in milliseconds.
ROUTTIME OS 8 B ROUTDURA Alternate name for ROUTDURA.
RSP CB 2 B   Corresponds to the ACB field response code. A response code of 0 indicates that the command executed successfully. This name is used in the schema portion of the summary record.
RSPSUB CB 4 B --- Contains the Adabas response code subcode from the ACB field Additions 2 or the ACBX field ACBXERRC for certain nonzero Adabas response codes.

-S-

Field System Name Category Field Length Format Alternate Names Description
SB BUF 32 C --- The contents of the Adabas search buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole search buffer is displayed.

The SBSEGnn field may be used to display parts of the search buffer if it is more than 32 bytes long.

SBFIELDS BUF 2 C --- Search buffer fields. Contains the Adabas 2-character field name for each field contained in the Adabas search buffer. This field can only be used in Summary reports.
SBL BUF 2 B --- Corresponds to the ACB field search buffer length.
SBSEGnn BUF 64 C --- Represents a search buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field SBSEG01, you obtain the first 64 bytes of the search buffer. The segment number may be a number between 01 and 32, inclusive. The field SBSEGnn is available for summary reports only; use the field SB for detail reports.
SECGID TP 8 C --- Contains the security system group ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
SECUID TP 8 C --- Contains the security system user ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
SEQ CLOG 4 B SEQUENCE Alternate name for SEQUENCE.
SEQUENCE CLOG 4 B SEQ The Adabas command sequence number. The value is incremented by one for each Adabas command processed.
SMP NUC 3 B NUCID This name is used in the schema portion of the summary record. It is an alternate name for NUCID.
SRCHTYPE CLOG 8 C --- The type of search or search algorithm. This field contains one of the following values if the Adabas command log is for version 8.2 SP2 or later:
  • ALGO-1: Search algorithm 1 was used.

  • ALGO-2: Search algorithm 2 was used.

  • ALGO-3: Search algorithm 3 was used.

  • ALGO-4: Search algorithm 4 was used.

  • MIXED: A nondescriptor search combined with a descriptor search was used.

  • NONDES: A nondescriptor search occurred.

If the Adabas command log is for an older Adabas release (8.2 SP1 or earlier), the value of the SRCHTYPE field will be blank.
STEPNAME OS 8 C --- The name of the job step or task step that issued the Adabas call. This step is only available in z/OS environments.
STRTDATE IT 4 T --- The date (in YYYY-MM-DD format) when the first Adabas command was processed within the current report control break.
STRTTIME IT 4 T --- The time (in 24-hour format) when the first Adabas command was processed within the current report control break.
SVC NUC 1 B --- The Adabas SVC (supervisor call) number used for interregion communication between the user's address space and the Adabas nucleus address space.
SYSCMD NUC 4 B --- The number of Adabas system commands that have been executed. Adabas system commands execute in Adabas threads 0 and -1.

-T-

Field System Name Category Field Length Format Alternate Names Description
THD CLOG 1 B THREAD Alternate name for THREAD.
THDNUM NUC 4 B --- The number of 8K Adabas threads in the nucleus. The number includes the two Adabas system threads (threads 0 and -1).
THDURA CB 8 B THTIME The active thread time for a command. This is the time, in milliseconds, required to process the Adabas call, not including the wait time caused by I/O or other required resources. The value of this field is obtained from the command time field in the Adabas command log (LOX1CTME).
THREAD CLOG 1 B THD The Adabas thread number in which the Adabas command was processed.
THREADSW NUC 4 B --- The number of thread switches that have occurred during the Adabas nucleus session.
THROWBKS NUC 4 B --- The number of command throwbacks that have occurred during the Adabas nucleus session. Throwbacks occur when the record you wish to retrieve has been placed on hold by another user. The command you issued is placed on the command queue ("thrown back") for reprocessing.
THTIME CB 8 B THDURA Alternate name for THDURA.
TIALLOC NUC 4 B --- The number of bytes of LI (ISN list table) space currently used.
TID TP 2 B --- The Com-plete terminal ID number of the user who issued the Adabas call.
TIDATE NUC 8 C --- The date (in YYYY-MM-DD format) when the LI (ISN list table) high-water mark was reached.
TIENT NUC 4 B --- The current number of entries used in the LI (ISN list table).
TIME IT 8 C --- The time (in 24-hour format) when the first Adabas call was processed.
TIPCT NUC 4 B --- The maximum percentage of LI (ISN list table) space used during the Adabas nucleus session.
TISIZE NUC 4 B --- The number of bytes allocated to the LI (ISN list table) at Adabas nucleus startup.
TITIME NUC 8 C --- The time (in HH:MM:SS format) that the LI (ISN list table) high-water mark was reached.
TIUSED NUC 4 B --- The maximum number of bytes of LI (ISN list table) space used during the Adabas nucleus session.
TOTALCMD NUC 4 B --- The total number of Adabas system and user commands that have been processed during the Adabas nucleus session.
TOTALIOS I/O 4 B --- Contains the total number of I/Os performed against all Adabas components for the Adabas session; the sum of ASSOREAD, ASSOWRIT, DATAREAD, DATAWRIT, WORKREAD, and WORKWRIT. This value is updated every minute and not when each command is issued.
TOTDURA IT 4 B --- Total duration. Contains the amount of time the command was in the Adabas thread plus the amount of time the command waited in the command queue. The TOTDURA field is the sum of the ADADURA and CQDURA field values expressed in seconds.
TPTRANCT TP 4 B --- A transaction count field. Possible values for this field are either "1" or "0" (zero).

A transaction is started with a TP terminal read and completed with a TP terminal write. For the first command of a transaction by a user, this field is set to "1". For all subsequent calls of the same transaction for the same user, this field is set to "0".

This field is most useful as a SUM field in conjunction with the field TRANSID. Used in this manner, you can determine the work rate per transaction.

TPTRANNM TP 4 B --- The transaction number as established by the user's TP system for the transaction that issued the Adabas call.
TPUSER TP 8 C TPUSERID Alternate name for TPUSERID.
TPUSERID TP 8 C TPUSER The user ID on the TP monitor from which the Adabas call was issued.
TRANSID TP 8 C --- The name of the root transaction or program that issued the Adabas call.
TRUENAME TP 8 C --- The name of the Adabas CICS link routine TRUE exit.
TSALLOC NUC 4 B --- The number of bytes in the LQ (table of sequential commands) currently being used.
TSDATE NUC 8 C --- The date (in YYYY-MM-DD format) when the LQ (table of sequential commands) high-water mark was reached.
TSENT NUC 4 B --- The current number of entries in the LQ (table of sequential commands).
TSPCT NUC 4 B --- The maximum percentage of LQ (table of sequential commands) space used during the Adabas nucleus session.
TSSIZE NUC 4 B --- The number of bytes allocated to the LQ (table of sequential commands) at Adabas nucleus startup.
TSTIME NUC 8 C --- The time (in HH:MM:SS format) when the LQ (table of sequential commands) high-water mark was reached.
TSUSED NUC 4 B --- The maximum number of bytes used in the LQ (table of sequential commands) during the Adabas nucleus session.
TYPECMD CLOG 1 B CMDTYPE

CMD-TYPE

Alternate name for CMDTYPE.

-U-

Field System Name Category Field Length Format Alternate Names Description
UBUID TP 8 C --- Contains the last 8 bytes of the 28-byte Adabas communication ID (CQEUID) for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

UCMPRECL CB 2 B --- Uncompressed record length. The uncompressed length of the Adabas format or search buffer field.
UOWID TP 8 C --- Contains the instance number and the sequence number of the CICS field NETUOWID, which is 27 bytes long. This field can only be filled in by CICS. The evaluation of this field requires a large amount of CPU time and, therefore, can only be activated by a special zap. Following is a description of the bytes in NETUOWID:
  • Offset 0 (Length 1): The length (L) of the Logical-Unit-of-Work-Identifier-Field, not including this field. The NETUOWID contains Logical-Unit-of-Work-Identifier-Field plus padding bytes. Values: 0 or 10 < = L < = 26.

  • Offset 1 (Length 1): The length of Network Name, not including this field, m = L - 9 , 1 < = m < = 17.

  • Offset 2 (Length m): Network name, format: ABCDEFGH.ABCDEFGH, Networkid.Luname.

  • Offset m + 2 (Length 6): Instance number.

  • Offset m + 2 + 6 (Length 2): Sequence number.

  • Offset m + 2 + 6 + 2 (Length until 27): Residual data.

UQALLOC NUC 4 B --- The number of bytes of user queue space currently in use.
UQDATE NUC 8 C --- The date (in YYYY-MM-DD) format when the user queue high-water mark was reached.
UQENT NUC 4 B --- The current number of user queue entries.
UQPCT NUC 4 B --- The maximum percentage of user queue space used during the Adabas nucleus session.
UQSIZE NUC 4 B --- The number of bytes allocated to the user queue at Adabas nucleus startup.
UQTIME NUC 8 C --- The time (in HH:MM:SS format) when the user queue high-water mark was reached.
UQUID TP 4 B --- Contains the unique 4-byte UQE (user queue element) user ID for the user who issued the Adabas call. This value is allocated in numerically ascending sequence for each UQE allocated by the Adabas nucleus.
UQUSED NUC 4 B --- The maximum number of bytes of user queue space ever used.
USERCMD NUC 4 B --- The total number of Adabas commands issued by users and processed during the Adabas nucleus session.
USERFLD1 UF user-defined user-defined --- An Adabas Review user field, containing user-specified data for reports.
USERFLD2 UF user-defined user-defined --- An Adabas Review user field, containing user-specified data for reports.
USERFLD3 UF user-defined user-defined --- An Adabas Review user field, containing user-specified data for reports.
USERFLD4 UF user-defined user-defined --- An Adabas Review user field, containing user-specified data for reports.
USERFLD5 UF user-defined user-defined --- An Adabas Review user field, containing user-specified data for reports.
USERID CLOG 28 B USER-ID The 28-byte Adabas communication ID of the user for whom the command was processed.
USER-ID CLOG 28 B USERID Alternate name for USERID.
USERTYPE TP 8 C --- The type of TP system from which the Adabas call was issued. For example, if the Adabas call was issued from a CICS session, the USERTYPE field contains "CICS".

-V-

Field System Name Category Field Length Format Alternate Names Description
VB BUF 32 C --- The contents of the Adabas value buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole value buffer is displayed.

The VBSEGnn field may be used to display parts of the value buffer if it is more than 32 bytes long.

VBL BUF 2 B --- Corresponds to the ACB field value buffer length field. The value buffer contains the value used in search commands.
VBSEGnn BUF 64 C --- Represents a value buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field VBSEG01, you obtain the first 64 bytes of the value buffer. The segment number may be a number between 01 and 32, inclusive. The field VBSEGnn is available for summary reports only; use the field VB for detail reports.

-W-

Field System Name Category Field Length Format Alternate Names Description
WEEK IT 1 B WK The week number of the week in which the Adabas command was processed.
WEEKDAY IT 3 C WEEK-DAY The name of the day on which the Adabas command was processed.
WEEK-DAY IT 3 C WEEKDAY Alternate name for WEEKDAY.
WK IT 1 B WEEK Alternate name for WEEK.
WORKIO CLOG 2 B WORK-IO The number of I/O operations performed against the Adabas Work data set for this command.
WORK-IO CLOG 2 B WORKIO Alternate name for WORKIO.
WORKREAD I/O 4 B --- Contains the total number of Work read I/O operations performed during the Adabas session. This value is updated every minute and not when each command is issued.
WORKWRIT I/O 4 B --- The total number of Work write I/O operations performed during the Adabas session. This value is updated every minute and not when each command is issued.

-Y-

Field System Name Category Field Length Format Alternate Names Description
YEAR IT 1 B YR The year (in YYYY format) in which the Adabas command was processed.
YR IT 1 B YEAR Alternate name for YEAR.

-Number-

Field System Name Category Field Length Format Alternate Names Description
1M IT 5 C MINUTE

MIN

Establishes 1-minute intervals for the collection of Adabas data.
5M IT 5 C M5 Establishes 5-minute intervals for the collection of Adabas data.
15M IT 5 C M15 Establishes 15-minute intervals for the collection of Adabas data.

Top of page

Adabas Control Block Field Category (CB)

Fields in this category are derived from the Adabas control block (ACB). Refer to the Adabas Command Reference Guide supplied with your version of Adabas for more information.

Field System Name Field Length Format Alternate Names Description
ACBUSER 4 B --- This field, comprising the last four bytes of the ACB, contains user data that is passed with the Adabas call. It is referred to as the user area field in the ACB, and is neither used nor modified by Adabas.
AD1 8 B ADD1

ADDIT1

Alternate name for ADDIT1.
AD2 4 B ADD2

ADDIT2

Alternate name for ADDIT2.
AD3 8 B ADD3

ADDIT3

Alternate name for ADDIT3.
AD4 8 B ADD4

ADDIT4

Alternate name for ADDIT4.
AD5 8 B ADD5

ADDIT5

Alternate name for ADDIT5.
ADD1 8 B AD1

ADDIT1

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT1.
ADD2 4 B AD2

ADDIT2

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT2.
ADD3 8 B AD3

ADDIT3

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT3.
ADD4 8 B AD4

ADDIT4

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT4.
ADD5 8 B AD5

ADDIT5

This name is used in the schema portion of the summary record. It is an alternate name for ADDIT5.
ADDIT1 8 B ADD1 (used in summary record)

AD1

Corresponds to the ACB field additions 1. The command to be executed determines whether this field is used and what the contents represent.
ADDIT2 4 B ADD2 (used in summary record)

AD2

Corresponds to the ACB field additions 2. The command to be executed determines whether this field is used and what the contents represent.

When ADARUN parameter CLOGLAYOUT is set to 8, the content of this field is taken from the ACBX structure. Note that there are differences in meaning of the Additions 2 field in the ACBX and in the ACB.

In the ACBX, some information that was formally available in the Additions 2 field is now split into several fields. For example, the error-related subcode information that was originally provided in the Additions 2 in the ACB is now provided in the Adabas ACBXSUBS (Subcomponent Response Subcode) field. The Additions 2 field will contain the transaction sequence number for an OP (open) and RE (read ET data) command. In Adabas Review, if the ADARUN parameter CLOGLAYOUT is set to 8, you will find the information from the older ACB Additions 2 structure in the following separate Adabas Review fields:

  • CMPRECL contains the compressed record length.

  • ERRFLDNM contains the error field name.

  • RSPSUB contains the subcode for an Adabas response code.

  • UCMPRECL contains the uncompressed record length.

ADDIT3 8 B ADD3 (used in summary record)

AD3

Corresponds to the ACB field additions 3. The command to be executed determines whether this field is used and what the contents represent.
ADDIT4 8 B ADD4 (used in summary record)

AD4

Corresponds to the ACB field additions 4. The command to be executed determines whether this field is used and what the contents represent.
ADDIT5 8 B ADD5 (used in summary record)

AD5

Corresponds to the ACB field additions 5. The command to be executed determines whether this field is used and what the contents represent.
CID 8 C --- Corresponds to the hexadecimal value of the ACB field command ID. This field serves important functions, determined by the command, during command execution. For example, during a sequential read, the command ID is used to return the records to the user in the proper sequence. This field displays the value of the CID in hexadecimal format (for example, if CID=ABCD, it is displayed in this field as "C1C2C3C4").
CIDALPHA 4 C --- Corresponds to the alphanumeric value of the ACB field command ID. This field serves important functions, determined by the command, during command execution. For example, during a sequential read, the command ID is used to return the records to the user in the proper sequence. This field displays the value of the CID in alphanumeric format.
CMD 2 C COMMAND Corresponds to the ACB field command code.
CMDNAME 14 C CNAME A translation of the 2-byte Adabas command code to a 14-byte string. For example, the command code BT is translated to "Backout Trans".
CMDRESP 4 B CMDRSP

MCR

The time, in milliseconds, required to process the Adabas call. In the command table, Adabas Review stores the minimum Adabas duration for each command type returning a zero response code. The command table is updated whenever a lower duration value is encountered. Command response time is thus based on the command time field in the Adabas command log.

The values for CMDRESP in the history file are automatically stored in seconds. To display them correctly, they must be converted to milliseconds. For more information on this conversion, read Migration from Previous Versions .

If you need to continue using the old scale and the old calculation algorithm for history data, contact your Software AG support representative.

Due to changes in the display programs in SYSREVDB, you cannot use SYSREVDB in Adabas Review 4.4 (or earlier versions) to display the field contents of CMDRESP correctly, unless you stay with the old scale and algorithm.

CMDRSP 4 B CMDRESP

MCR

Alternate name for CMDRESP.
CMDSTAT 8 C --- Contains the Adabas internal status for an Adabas command. For example, the Adabas command L3 has an internal status of SIMPLE and S1 has an internal status of COMPLEX.
CMPRECL 2 B --- Contains the compressed record length of the record returned by a READ or a FIND command.
CNAME 14 C CMDNAME Alternate name for CMDNAME.
COMMAND 2 C CMD Alternate name for CMD.
COMMANDS 8 B --- The number of Adabas commands processed for the control break.
COP1 1 C OP1 Corresponds to the ACB field command option 1. The contents of this field is determined by the command being issued.
COP2 1 C OP2 Corresponds to the ACB field command option 2. The contents of this field is determined by the command being issued.
DBID 2 B --- The unique Adabas database identification number.
ERRFLDNM 2 C --- Error field name. Contains the Adabas 2-character name for a field that has been found to be in error in the Adabas format or search buffer.
FILE 2 B FNR (used in summary record) Corresponds to the ACB field file number. The function of this field is determined by the Adabas command being issued.
FNR 2 B FILE This name is used in the schema portion of the summary record. It is an alternate name for FILE.
GLOBFMID 8 B --- Contains the global internal format buffer ID for the Adabas call within a sequence of Adabas calls. This field is derived from ADDIT5 field.
ISN 4 B --- Corresponds to the ACB field ISN. The use of this field is determined by the command being issued.
ISNLL 4 B --- Corresponds to the ACB field ISN lower limit. The field contains the lowest ISN that Adabas returns when retrieving ISN lists. The use of this field is determined by the command being issued.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNLL as well as ISNQ are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

ISNQ 4 B --- Corresponds to a modification of the ACB field ISN quantity. The field is modified based on command type, and is suitable for performing mathematical calculations such as SUM and AVERAGE. The unmodified data can be found in the ORGISNQ field.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNQ as well as ISNLL are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

MCR 4 B CMDRESP

CMDRSP

Alternate name for CMDRESP.
OP1 1 C COP1 Alternate name for COP1.
OP2 1 C COP2 Alternate name for COP2.
RSP 2 B   Corresponds to the ACB field response code. A response code of 0 indicates that the command executed successfully. This name is used in the schema portion of the summary record.
RSPSUB 4 B --- Contains the Adabas response code subcode from the ACB field Additions 2 or the ACBX field ACBXERRC for certain nonzero Adabas response codes.
THDURA 8 B THTIME The active thread time for a command. This is the time, in milliseconds, required to process the Adabas call, not including the wait time caused by I/O or other required resources. The value of this field is obtained from the command time field in the Adabas command log (LOX1CTME).
THTIME 8 B THDURA Alternate name for THDURA.
UCMPRECL 2 B --- Uncompressed record length. The uncompressed length of the Adabas format or search buffer field.

Top of page

Adabas Command Log Field Category (CLOG)

Field System Name Field Length Format Alternate Names Description
ASSOIO 2 B ASSO-IO The number of asynchronous Associator read I/Os for this command.
ASSO-IO 2 B ASSOIO Alternate name for ASSOIO.
CALLTYPE 8 C --- Contains the type of the Adabas call that was issued. Possible values are:
  • "PHYSICAL": indicates a standard Adabas call

  • "REMOTE": indicates a call arriving via Entire Net-Work.

CMDTYPE 1 B TYPECMD

CMD-TYPE

The 1-byte command type field of the Adabas command log record that describes the internal Adabas status for the command. For example, a command type of 01 is a simple command and a command type of 42 is a complex command. The CMDSTAT field provides this translation.
CMD-TYPE 1 B CMDTYPE

TYPECMD

Alternate name for CMDTYPE.
DATAIO 2 B DATA-IO The number of asynchronous Data Storage read I/Os for this command.
DATA-IO 2 B DATAIO Alternate name for DATAIO.
DES 2 B DESUPD Alternate name for DESUPD.
DESUPD 2 B DES Contains the number of descriptors that were updated for an Adabas call.
DUR 4 B DURATION

DURAT

Alternate name for DURATION.
DURAT 4 B DURATION

DUR

Alternate name for DURATION.
DURATION 4 B DURAT

DUR

The amount of time that the command spent in the Adabas thread, including time spent waiting for I/O operations to complete. This field is expressed in seconds and is accurate to 4 decimal places. The field ADADURA contains the same value accurate to 6 decimal places.
ORGDURA 4 B --- The (original) value of the "duration" field contained in the command log record. The time is expressed in units of 16 microseconds.
PRI 1 B PRIORITY

PRIO

Alternate name for PRIORITY.
PRIO 1 B PRIORITY

PRI

Alternate name for PRIORITY.
PRIORITY 1 B PRI

PRIO

The operating system priority for the user issuing the Adabas call.
SEQ 4 B SEQUENCE Alternate name for SEQUENCE.
SEQUENCE 4 B SEQ The Adabas command sequence number. The value is incremented by one for each Adabas command processed.
SRCHTYPE 8 C --- The type of search or search algorithm. This field contains one of the following values if the Adabas command log is for version 8.2 SP2 or later:
  • ALGO-1: Search algorithm 1 was used.

  • ALGO-2: Search algorithm 2 was used.

  • ALGO-3: Search algorithm 3 was used.

  • ALGO-4: Search algorithm 4 was used.

  • MIXED: A nondescriptor search combined with a descriptor search was used.

  • NONDES: A nondescriptor search occurred.

If the Adabas command log is for an older Adabas release (8.2 SP1 or earlier), the value of the SRCHTYPE field will be blank.
THD 1 B THREAD Alternate name for THREAD.
THREAD 1 B THD The Adabas thread number in which the Adabas command was processed.
TYPECMD 1 B CMDTYPE

CMD-TYPE

Alternate name for CMDTYPE.
USERID 28 B USER-ID The 28-byte Adabas communication ID of the user for whom the command was processed.
USER-ID 28 B USERID Alternate name for USERID.
WORKIO 2 B WORK-IO The number of I/O operations performed against the Adabas Work data set for this command.
WORK-IO 2 B WORKIO Alternate name for WORKIO.

Top of page

Adabas Buffer Field Category (BUF)

Note:
The data in the buffers may be meaningless if the Adabas response code is not zero.

Field System Name Field Length Format Alternate Names Description
FB 32 C --- The contents of the Adabas format buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole format buffer is displayed.

The FBSEGnn field may be used to display parts of the format buffer if it is more than 32 bytes long. Only one FBSEGnn field is allowed for each report.

FBFIELDS 2 C FBF Format buffer fields. Contains the Adabas 2-character name for each field contained in the Adabas format buffer. This field can only be used in Summary reports.
FBL 2 B --- Corresponds to the ACB field format buffer length. The contents of this field is determined by the Adabas command issued.
FBSEGnn 64 C --- Represents a format buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field FBSEG01 you obtain the first 64 bytes of the format buffer. The segment number may be a value between 01 and 32, inclusive. The field FBSEGnn is available for summary reports only; use the field FB for detail reports.
IB 32 C --- The contents of the Adabas ISN buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole ISN buffer is displayed.

The IBSEGnn field may be used to display parts of the ISN buffer if it is more than 32 bytes long.

IBL 2 B --- Corresponds to the ACB field ISN buffer length. The use of this field is determined by the command being issued.
IBSEGnn 64 C --- Represents an ISN buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field IBSEG01, you obtain the first 64 bytes of the ISN buffer. The segment number may be a value between 01 and 32, inclusive. The field IBSEGnn is available for summary reports only; use the field IB for detail reports.
RB 32 C --- The contents of the Adabas record buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole record buffer is displayed.

The RBSEGnn field may be used to display parts of the record buffer if it is more than 32 bytes long.

RBL 2 B --- Corresponds to the ACB field record buffer length. The record buffer is used primarily with read, search, and update commands.
RBSEGnn 64 C --- Represents a record buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field RBSEG01, you obtain the first 64 bytes of the record buffer. The segment number may be a number between 01 and 32, inclusive. The field RBSEGnn is available for summary reports only; use the field RB for detail reports.
SB 32 C --- The contents of the Adabas search buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole search buffer is displayed.

The SBSEGnn field may be used to display parts of the search buffer if it is more than 32 bytes long.

SBFIELDS 2 C --- Search buffer fields. Contains the Adabas 2-character field name for each field contained in the Adabas search buffer. This field can only be used in Summary reports.
SBL 2 B --- Corresponds to the ACB field search buffer length.
SBSEGnn 64 C --- Represents a search buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field SBSEG01, you obtain the first 64 bytes of the search buffer. The segment number may be a number between 01 and 32, inclusive. The field SBSEGnn is available for summary reports only; use the field SB for detail reports.
VB 32 C --- The contents of the Adabas value buffer if one exists for the Adabas call.

When used in a summary report, only the first 32 bytes of this field are displayed. When used in a detail report, the whole value buffer is displayed.

The VBSEGnn field may be used to display parts of the value buffer if it is more than 32 bytes long.

VBL 2 B --- Corresponds to the ACB field value buffer length field. The value buffer contains the value used in search commands.
VBSEGnn 64 C --- Represents a value buffer segment of 64 bytes. The nn suffix is the segment number. For example, by specifying the field VBSEG01, you obtain the first 64 bytes of the value buffer. The segment number may be a number between 01 and 32, inclusive. The field VBSEGnn is available for summary reports only; use the field VB for detail reports.

Top of page

Client Reporting Field Category (CMON)

Note:
For information on how duration fields are calculated, read Adabas Review Duration Field Derivations.

Field System Name Field Length Format Alternate Names Description
CDURA 8 B --- The total client duration time. This is the total time (in seconds) in which the client waits for the command to be processed by the server and the time it takes the ADALNK portion of the client to retrieve the command results. CDURA is the sum of the CRCVDURA and CWRKDURA fields.

Measurement for this field starts immediately after the command is passed to the server (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 router processing is performed). Measurement stops when the client picks up the command result information from the server (performing SVC-16 router processing within the Adabas link routine).

CRCVDURA 8 B --- The client receive time. This is the time (in seconds) it takes the Adabas link routine to retrieve a processed command from the server.

Measurement for this field starts immediately after the server posts the Adabas link routine to retrieve the command result information (performing SVC-12 router processing) . Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-16 router processing).

CWRKDURA 8 B --- The client wait time, or the time in which the server works for the client. This is the time (in seconds) in which the client waits for the command to be processed by the server.

Measurement for this field starts immediately after the command is passed to the server for processing (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 processing is performed). Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-12 router processing).

Top of page

Interval and Time Field Category (IT)

Note:
For information on how duration fields are calculated, read Adabas Review Duration Field Derivations.

Field System Name Field Length Format Alternate Names Description
15M 5 C M15 Establishes 15-minute intervals for the collection of Adabas data.
1M 5 C MINUTE

MIN

Establishes 1-minute intervals for the collection of Adabas data.
5M 5 C M5 Establishes 5-minute intervals for the collection of Adabas data.
ADADURA 4 B --- Adabas duration. Corresponds to the DURATION field. This field contains the amount of time (in seconds) that the command spent in the Adabas thread, including the time spent waiting for the completion of I/O operations. The ADADURA field differs from the DURATION and ORGDURA fields in that the time is computed to 6 decimal places instead of 4 decimal places.
CQDURA 4 B --- Command queue duration. Contains the amount of time (in seconds) that a command waited in the command queue before being dispatched into an Adabas thread.
DATE 8 C --- The date (in YYYY-MM-DD format) when the Adabas command was processed.
DAY 1 B --- The day number (within a month) when the Adabas command was processed.
ENDDATE 4 T --- The date (in YYYY-MM-DD format) when the last Adabas command was processed within the current report control break.
ENDTIME 4 T --- The time (in 24-hour format) when the last Adabas command was processed within the current report control break.
ESTCPU 6.6 N --- The estimated CPU time used by each Adabas command. The values shown in this field are only relative approximations of the CPU time used; they are not based on any actual CPU times and are calculated, instead, based on an algorithm. The algorithm used varies for each Adabas command type and is based on the number of instructions, I/Os, descriptors, and fields used.

This field can be used as a SUM, MIN, MAX and/or AVG field.

FULLSTCK 8 T --- The 8-byte store clock value taken when the Adabas command was processed.
HOUR 5 C HR The hour (in 24-hour format) when the Adabas command was processed.
HR 5 C HOUR Alternate name for HOUR.
M15 5 C 15M Alternate name for 15M.
M5 5 C 5M Alternate name for 5M.
MIN 5 C 1M

MINUTE

Alternate name for 1M.
MINUTE 5 C 1M

MIN

Alternate name for 1M.
MO 1 B MONTH

MON

Alternate name for MONTH.
MON 1 B MON

MO

Alternate name for MONTH.
MONAME 3 C --- The name of the month when the Adabas command was processed.
MONTH 1 B MON

MO

The number of the month when the Adabas command was processed.
QTR 1 B QUARTER

QUAR

Alternate name for QUARTER.
QUAR 1 B QUARTER

QTR

Alternate name for QUARTER.
QUARTER 1 B QUAR

QTR

The quarter of the year in which the Adabas command was processed.
STRTDATE 4 T --- The date (in YYYY-MM-DD format) when the first Adabas command was processed within the current report control break.
STRTTIME 4 T --- The time (in 24-hour format) when the first Adabas command was processed within the current report control break.
TIME 8 C --- The time (in 24-hour format) when the first Adabas call was processed.
TOTDURA 4 B --- Total duration. Contains the amount of time the command was in the Adabas thread plus the amount of time the command waited in the command queue. The TOTDURA field is the sum of the ADADURA and CQDURA field values expressed in seconds.
WEEK 1 B WK The week number of the week in which the Adabas command was processed.
WEEKDAY 3 C WEEK-DAY The name of the day on which the Adabas command was processed.
WEEK-DAY 3 C WEEKDAY Alternate name for WEEKDAY.
WK 1 B WEEK Alternate name for WEEK.
YEAR 1 B YR The year (in YYYY format) in which the Adabas command was processed.
YR 1 B YEAR Alternate name for YEAR.

Top of page

Adabas I/O Field Category (I/O)

Field System Name Field Length Format Alternate Names Description
ASSOREAD 4 B ---- Associator read. The total number of Associator read I/Os that occurred during the Adabas session. This value is updated every minute and not when each command is issued.
ASSOWRIT 4 B --- Associator write. The total number of Associator write I/Os that occurred during the Adabas session. This value is updated every minute and not when each command is issued.
DATAREAD 4 B --- The total number of Adabas Data Storage read I/Os for the Adabas session. This value is updated every minute and not when each command is issued.
DATAWRIT 4 B --- The total number of Adabas Data Storage write I/Os for the Adabas session. This value is updated every minute and not when each command is issued.
IO 2 B IOS This name is used in the schema portion of the summary record. It is an alternate name for IOS.
IOS 2 B IO (used in summary record) The total number of I/Os for the command processed; it is the sum of ASSOIO, DATAIO and WORKIO.
IOCOMP 3 C --- Identifies the Adabas component against which the I/O was issued. For example, if the I/O is issued against Data Storage extent 1, the field contains DS1. If the I/O is issued against address converter extent 3, the field contains AC3.
IOFUNC 5 C --- The type of I/O operation performed against an Adabas component. The values for this field are "READ" or "WRITE".
IOLIST 10 C --- The hexadecimal I/O list for a command obtained from the Adabas command log record. Four bytes are allocated for each I/O list entry.
IOPHYS 16 C --- A translation of the I/O list entry from the Adabas command log record. The format for this field is comp-x nnnnnn, where:

comp is the Adabas component (ASSO, DATA, or WORK)

x is the type of I/O, ("R" for read or "W" for write)

nnnnnn is the RABN (relative Adabas block number)

IORABN 8 C --- The relative Adabas block number against which the I/O was performed.
IOTOCMD 4 B --- The ratio of the total number of I/O operations performed to the total number of commands processed.
IOTYPE 4 C --- Identifies the component against which the I/O operation was performed. Values for this field may be ASSO 'Associator', DATA 'Data Storage', or WORK 'Work data set'.
IOVOLSER 6 C --- Contains the volume serial number against which the I/O operation was performed. This field may be used to show Adabas I/O distribution. For WORK I/Os (see the IOTYPE field) the IOVOLSER field will contain the text "UNKNWN". If the data is obtained from blocks that are stored in the Adabas buffer pool and therefore no physical I/Os are made, this field will be empty.
TOTALIOS 4 B --- Contains the total number of I/Os performed against all Adabas components for the Adabas session; the sum of ASSOREAD, ASSOWRIT, DATAREAD, DATAWRIT, WORKREAD, and WORKWRIT. This value is updated every minute and not when each command is issued.
WORKREAD 4 B --- Contains the total number of Work read I/O operations performed during the Adabas session. This value is updated every minute and not when each command is issued.
WORKWRIT 4 B --- The total number of Work write I/O operations performed during the Adabas session. This value is updated every minute and not when each command is issued.

Top of page

Natural Field Category (NAT)

Field System Name Field Length Format Alternate Names Description
LEVEL 2 B NATLEVEL Alternate name for NATLEVEL.
LIB 8 C NATLIB Alternate name for NATLIB.
LOG 8 C NATAPPL

LOGON

This name is used in the schema portion of the summary record. It is an alternate name for NATAPPL.
LOGON 8 C NATAPPL

LOG (used in summary record)

Alternate name for NATAPPL.
NATAPPL 8 C LOGON

LOG (used in summary record)

The Natural application name (or library) to which the user issued a LOGON. This field does not necessarily show the library of the Natural object from which the Adabas call is issued. Under SQL, this field contains the library name.
NATCLTID 8 C --- NATCLTID displays the client user ID of a user using a Natural server. NATCLTID only contains a value if an RPC client request is executed in a Natural RPC server session. In all other cases the field is empty.
NATCOUNT 2 B --- The total number of Adabas calls generated by the user application since the last terminal I/O.
NATEXEC 2 B --- The number of times a Natural object that issues Adabas calls has been executed. NATEXEC is "1" if the Natural object has issued an Adabas call for the first time on this level; for each subsequent Adabas call on this level the value will be set to zero. You can use the SUM statement to total the values of this field to obtain the total number of times a specific Natural object has been called.
NATGRP 8 C --- The current Natural security group to which the user belongs.
NATLEVEL 2 B LEVEL The Natural call level of the Natural program issuing the Adabas call. For example, a CALLNAT routine that is called from a program and issues an Adabas call has a Natural level of 2.
NATLIB 8 C LIB The name of the Natural library where the object is located that is currently executed.
NATPROG 8 C PROGRAM

PRO (used in summary record)

The name of the Natural program that issued the Adabas call. When Natural internally issues Adabas calls to load Natural objects, this value is not updated. Under SQL, this field contains the program name.
NATRPCCO 16 C --- The 16-byte alphanumeric value of the conversation ID from the Natural RPC Server.
NATRPCID 16 C --- The 16-byte alphanumeric value for the store clock value used as identification of the Natural RPC Server.
NATSTMT 4 C --- The Natural statement number where the Adabas command is processed. This line number is the line in the Natural program displayed by NATPROG. When the processed Adabas command is in the copy code portion of the Natural program, the line number refers to the copy code. The name of the copy code is not available at this time.
NATUID 8 C --- The name of the Natural library to which the user is currently logged on. This is the value of the Natural system variable *APPLIC-ID.
PRO 8 C NATPROG

PROGRAM

This name is used in the schema portion of the summary record. It is an alternate name for NATPROG.
PROGRAM 8 C NATPROG

PRO (used in summary record)

Alternate name for NATPROG.

Top of page

Adabas Nucleus Field Category (NUC)

Field System Name Field Length Format Alternate Names Description
ABALLOC 4 B --- The number of bytes of attached buffer space currently used. An attached buffer is an internal buffer used for interregion communication.
ABDATE 8 C --- The date (in YYYY-MM-DD format) when the attached buffer high-water mark was reached.
ABENT 4 B --- The current number of attached buffer entries.
ABPCT 4 B --- The maximum percentage of attached buffer space used during the Adabas nucleus session.
ABSIZE 4 B --- The total amount (in bytes) of attached buffer space allocated at Adabas nucleus startup.
ABTIME 8 C --- The time (in HH:MM:SS format) that the attached buffer high-water mark was reached.
ABUSED 4 B --- The maximum number (in bytes) of attached buffer space used during the Adabas nucleus session.
BUFFEFF 4 B --- Buffer efficiency. Contains the ratio of the number of calls to the Adabas buffer pool manager to the number of Adabas physical read requests made to the Associator and the Data Storage devices. For example, if the number of read I/Os is 100 and the number of calls to the buffer pool manager is 500, the buffer efficiency is 500/100 or 5. The higher the buffer efficiency number, the more efficient is the use of buffer space. If the buffer efficiency number is low, it is recommended that you increase the LBP (length of buffer pool) ADARUN parameter.
BUFFLUSH 4 B --- The number of times that the Adabas buffer pool (LBP) was flushed during the Adabas nucleus session.
BUFFWAIT 4 B --- The number of times that Adabas Review had to wait for a buffer.
CQALLOC 4 B --- The number of bytes of command queue space currently used.
CQDATE 8 C --- The date (in YYYY-MM-DD format) when the command queue high-water mark was reached.
CQENT 4 B --- The current number of command queue entries.
CQJOB 8 C --- The job or started task name for the user obtained from the user's command queue element.
CQMAXENT 4 B --- The maximum number of entries that have been in the command queue for the Adabas nucleus session.
CQPCT 4 B --- The maximum percentage of command queue space used during the Adabas nucleus session.
CQSIZE 4 B --- The total number of bytes of command queue space allocated at Adabas nucleus startup.
CQTIME 8 B --- The time (in HH:MM:SS format) when the command queue high-water mark was reached.
CQUQADDR 8 B --- The address of the User Queue Element found in the CQE.
CQUSED 4 B --- The maximum number of bytes of command queue space used during the Adabas nucleus session.
DBNAME 16 C --- The 16-character name assigned to the database when it was created.
FILENAME 16 C --- Contains the 16-character name assigned to the Adabas file, and is obtained from the Adabas file control block (FCB). If the file name is not available, the field contains "FCB-UNAVAILABLE".
FILETYPE 6 C --- Contains the 6-character type assigned to the Adabas file. This field contains the string "USER" if the file is a user file or "SYSTEM" if the Adabas Checkpoint file was read or updated.
FORMATOW 4 B --- The total number of Adabas internal format overwrites that have occurred during the Adabas nucleus session.
FORMATTR 4 B --- The total number of Adabas internal format translations that have occurred during the Adabas nucleus session.
HOLDISN 2 B --- The numbers of ISNs which are in HOLD status by the user at the time this command is executed. The number is obtained after the execution of this command.
HQDATE 8 C --- The date (in YYYY-MM-DD format) that the hold queue high-water mark was reached.
HQENT 4 B --- The current number of hold queue entries.
HQPCT 4 B --- The maximum percentage of hold queue space used during the Adabas nucleus session.
HQSIZE 4 B --- The total number of bytes allocated to the hold queue at Adabas nucleus startup.
HQTIME 8 C --- The time (in HH:MM:SS format) that the hold queue high-water mark was reached.
HQUSED 4 B --- The maximum number of bytes of hold queue space used during the Adabas nucleus session.
HQUSRENT 4 B --- The number of hold queue user entries.
LFPALLOC 4 B --- The number of bytes currently used in the format pool.
LFPENT 4 B --- The current number of entries in the format pool.
LFPMAX 4 B --- The maximum number of bytes of format pool space used during the Adabas nucleus session.
LFPPCT 4 B --- The maximum percentage of format pool space used during the Adabas nucleus session.
LFPSIZE 4 B --- The total number of bytes allocated to the format pool at Adabas nucleus startup.
LFPUSED 4 B --- The maximum number of bytes of format pool space used during the Adabas nucleus session.
LWPALLOC 4 B --- The number of bytes of the work pool currently in use.
LWPENT 4 B --- The current number of work pool entries.
LWPMAX 4 B --- The maximum number of bytes of work pool space used during the Adabas nucleus session.
LWPMXENT 4 B --- The maximum number of work pool entries used during the Adabas nucleus session.
LWPPCT 4 B --- The maximum percentage of work pool space used during the Adabas nucleus session.
LWPSIZE 4 B --- The number of bytes that were allocated to the work pool at Adabas nucleus startup.
LWPUSED 4 B --- The maximum number of bytes of work pool space used during the Adabas nucleus session.
MULTICNT 8 N -- The number of multifetch records returned.

For all read calls (Lx commands), multifetch returns a group of records in the record buffer and a description of these records in either the caller's ISN buffer (for ACB interface direct calls) or the caller's multifetch buffer (for ACBX interface direct calls). Multifetch records are only returned if the ACB or ACBX call contain an <literalvalue>M</literalvalue> in Command Option 1.

NUCID 3 B SMP (used in summary record) The ID of an Adabas nucleus in an Adabas Parallel Services or Adabas Cluster Services environment.
SMP 3 B NUCID This name is used in the schema portion of the summary record. It is an alternate name for NUCID.
SVC 1 B --- The Adabas SVC (supervisor call) number used for interregion communication between the user's address space and the Adabas nucleus address space.
SYSCMD 4 B --- The number of Adabas system commands that have been executed. Adabas system commands execute in Adabas threads 0 and -1.
THDNUM 4 B --- The number of 8K Adabas threads in the nucleus. The number includes the two Adabas system threads (threads 0 and -1).
THREADSW 4 B --- The number of thread switches that have occurred during the Adabas nucleus session.
THROWBKS 4 B --- The number of command throwbacks that have occurred during the Adabas nucleus session. Throwbacks occur when the record you wish to retrieve has been placed on hold by another user. The command you issued is placed on the command queue ("thrown back") for reprocessing.
TIALLOC 4 B --- The number of bytes of LI (ISN list table) space currently used.
TIDATE 8 C --- The date (in YYYY-MM-DD format) when the LI (ISN list table) high-water mark was reached.
TIENT 4 B --- The current number of entries used in the LI (ISN list table).
TIPCT 4 B --- The maximum percentage of LI (ISN list table) space used during the Adabas nucleus session.
TISIZE 4 B --- The number of bytes allocated to the LI (ISN list table) at Adabas nucleus startup.
TITIME 8 C --- The time (in HH:MM:SS format) that the LI (ISN list table) high-water mark was reached.
TIUSED 4 B --- The maximum number of bytes of LI (ISN list table) space used during the Adabas nucleus session.
TOTALCMD 4 B --- The total number of Adabas system and user commands that have been processed during the Adabas nucleus session.
TSALLOC 4 B --- The number of bytes in the LQ (table of sequential commands) currently being used.
TSDATE 8 C --- The date (in YYYY-MM-DD format) when the LQ (table of sequential commands) high-water mark was reached.
TSENT 4 B --- The current number of entries in the LQ (table of sequential commands).
TSPCT 4 B --- The maximum percentage of LQ (table of sequential commands) space used during the Adabas nucleus session.
TSSIZE 4 B --- The number of bytes allocated to the LQ (table of sequential commands) at Adabas nucleus startup.
TSTIME 8 C --- The time (in HH:MM:SS format) when the LQ (table of sequential commands) high-water mark was reached.
TSUSED 4 B --- The maximum number of bytes used in the LQ (table of sequential commands) during the Adabas nucleus session.
UQALLOC 4 B --- The number of bytes of user queue space currently in use.
UQDATE 8 C --- The date (in YYYY-MM-DD) format when the user queue high-water mark was reached.
UQENT 4 B --- The current number of user queue entries.
UQPCT 4 B --- The maximum percentage of user queue space used during the Adabas nucleus session.
UQSIZE 4 B --- The number of bytes allocated to the user queue at Adabas nucleus startup.
UQTIME 8 C --- The time (in HH:MM:SS format) when the user queue high-water mark was reached.
UQUSED 4 B --- The maximum number of bytes of user queue space ever used.
USERCMD 4 B --- The total number of Adabas commands issued by users and processed during the Adabas nucleus session.

Top of page

Operating System Field Category (OS)

Note:
For information on how duration fields are calculated, read Adabas Review Duration Field Derivations.

Field System Name Field Length Format Alternate Names Description
ACCTINF2 16 C --- Accounting information about the user that issued the Adabas call for z/OS batch jobs. This field will contain the second value specified in the account field of the job card.
ACCTINFO 16 C --- Accounting information about the user that issued the Adabas call.
For z/OS batch jobs, the field will contain the first value specified in the account field of the job card.
For Com-plete users, the field will contain the account information specified in the user's Com-plete profile.
CPUID 8 B --- The internal identifying serial number of the CPU from which the Adabas call was issued.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

JMREDATE 10 C --- The date (in YYYY-MM-DD format) when the batch job was entered in JES or from the job information macro.
JOB 8 C JOBNAME Alternate name for JOBNAME.
JOBCLASS 1 B --- (z/OS only) The one-byte character of the CLASS parameter in the job card.
JOBID 8 C --- A combination of the job identifier and the job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE:
  • Under z/OS, the field will contain JOB, STC, or TSU as the job identifier followed by a 5-byte JES job number.

  • Under z/VSE, the field will contain JOB as the identifier, followed by the 5-byte POWER job number.

JOBNAME 8 C JOB The name of the job or task from which the Adabas call was issued. This field is the contents of the JOBNAME from the Adabas command log record and may not reflect the actual JOBNAME of the task that issued the Adabas call.
JOBNUM 5 C --- The job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE. The field will contain an alphanumeric, 5-byte value for the JES (z/OS) or POWER (z/VSE) job number.
LPARNAME 8 C --- The system LPAR or partition name (in z/OS or z/VSE environments) or the environment name from the job information macro (in BS2000 environments).
LUNAME 8 C --- The VTAM LU (logical unit) name of the user who issued the Adabas call. If the TP system is Com-plete, the LUNAME field contains the Com-plete ID:
  • The first 3 bytes of the ID represent the Com-pass stack level

  • The fourth byte is the Com-plete patch character

  • The last 4 bytes identify the Com-plete terminal ID number in hexadecimal format.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

OPSYSID 4 B --- The operating system ID. The address of the ASCB (address space control block) for the job or task that issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

OPSYSNAM 8 C --- The operating system name (SYSNAME) that is specified in the SYS1.PARMLIB and which will be obtained from the CVT (in z/OS environments) or the operating system name and version number (in BS2000 environments).
ROUTDURA 8 B ROUTTIME The amount of time between the time a command was issued by the application and the time it was queued in the Adabas command queue. For Adabas 8.1 and earlier, this field is expressed in seconds; for Adabas 8.2 and later releases, this field is expressed in milliseconds.
ROUTTIME 8 B ROUTDURA Alternate name for ROUTDURA.
STEPNAME 8 C --- The name of the job step or task step that issued the Adabas call. This step is only available in z/OS environments.

Top of page

Transaction Processing Monitor Field Category (TP)

Field System Name Field Length Format Alternate Names Description
ACINAME 8 C CURENPGM The program name of the Adabas CICS link routine for the DCI interface: ADADCI.
CALLPGM 8 C --- The program that executed the last EXEC CICS LINK or XCTL command.
  • In non-DCI situations, this is the program calling the Adabas CICS link routine via EXEC CICS LINK

  • In DCI interface situations (used by Natural), this is the name of the executing program if there was no previous EXEC CICS LINK or, if there was a previous EXEC CICS LINK, the name of the program that executed the last EXEC CICS LINK.

CQEUID 28 B --- Contains the 28-byte Adabas communication user ID for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

CURENPGM 8 C ACINAME Alternate name for ACINAME.
ETID 8 C --- The Adabas ET (end transaction) ID that was established during the OP (open) call to Adabas. The contents of the field is determined by the calling program.

If the first character provided for the ETID is smaller than "A" through "9", Adabas Review will show null value (blanks) in this field. If the first character is in the range "A" through "9", but the following characters are nonprintable characters, Adabas Review will display them in alphanumeric format, which might result in blanks or special characters. To display this field in hexadecimal, an Adabas Review user field can be used.

SECGID 8 C --- Contains the security system group ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
SECUID 8 C --- Contains the security system user ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
TID 2 B --- The Com-plete terminal ID number of the user who issued the Adabas call.
TPTRANCT 4 B --- A transaction count field. Possible values for this field are either "1" or "0" (zero).

A transaction is started with a TP terminal read and completed with a TP terminal write. For the first command of a transaction by a user, this field is set to "1". For all subsequent calls of the same transaction for the same user, this field is set to "0".

This field is most useful as a SUM field in conjunction with the field TRANSID. Used in this manner, you can determine the work rate per transaction.

TPTRANNM 4 B --- The transaction number as established by the user's TP system for the transaction that issued the Adabas call.
TPUSER 8 C TPUSERID Alternate name for TPUSERID.
TPUSERID 8 C TPUSER The user ID on the TP monitor from which the Adabas call was issued.
TRANSID 8 C --- The name of the root transaction or program that issued the Adabas call.
TRUENAME 8 C --- The name of the Adabas CICS link routine TRUE exit.
UBUID 8 C --- Contains the last 8 bytes of the 28-byte Adabas communication ID (CQEUID) for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

UOWID 8 C --- Contains the instance number and the sequence number of the CICS field NETUOWID, which is 27 bytes long. This field can only be filled in by CICS. The evaluation of this field requires a large amount of CPU time and, therefore, can only be activated by a special zap. Following is a description of the bytes in NETUOWID:
  • Offset 0 (Length 1): The length (L) of the Logical-Unit-of-Work-Identifier-Field, not including this field. The NETUOWID contains Logical-Unit-of-Work-Identifier-Field plus padding bytes. Values: 0 or 10 < = L < = 26.

  • Offset 1 (Length 1): The length of Network Name, not including this field, m = L - 9 , 1 < = m < = 17.

  • Offset 2 (Length m): Network name, format: ABCDEFGH.ABCDEFGH, Networkid.Luname.

  • Offset m + 2 (Length 6): Instance number.

  • Offset m + 2 + 6 (Length 2): Sequence number.

  • Offset m + 2 + 6 + 2 (Length until 27): Residual data.

UQUID 4 B --- Contains the unique 4-byte UQE (user queue element) user ID for the user who issued the Adabas call. This value is allocated in numerically ascending sequence for each UQE allocated by the Adabas nucleus.
USERTYPE 8 C --- The type of TP system from which the Adabas call was issued. For example, if the Adabas call was issued from a CICS session, the USERTYPE field contains "CICS".

Top of page

User Field Category (UF)

Field System Name Field Length Format Alternate Names Description
USERFLD1 through USERFLD5 user-defined user-defined --- These are user fields, made available to you so you can report on data you choose. For complete information about defining and using Adabas Review user fields, read Defining Adabas Review User Fields.

Top of page

Fields Available for Client Reporting Reports

The following table summarizes all of the fields available for client reporting reports. This represents the fields in the CMON category as well as a subset of the fields in other field categories.

Field Name Category Description
5M IT Establishes 5-minute intervals for the collection of Adabas data.
15M IT Establishes 15-minute intervals for the collection of Adabas data.
ACCTINF2 Operating System Fields (OS) Accounting information about the user that issued the Adabas call for z/OS batch jobs. This field will contain the second value specified in the account field of the job card.
ACCTINFO Operating System Fields (OS) Accounting information about the user that issued the Adabas call.
For z/OS batch jobs, the field will contain the first value specified in the account field of the job card.
For Com-plete users, the field will contain the account information specified in the user's Com-plete profile.
ACINAME Transaction Processing Monitor Fields (TP) The program name of the Adabas CICS link routine for the DCI interface: ADADCI.
ADADURA Interval and Time Fields (IT) Adabas duration. Corresponds to the DURATION field. This field contains the amount of time (in seconds) that the command spent in the Adabas thread, including the time spent waiting for the completion of I/O operations. The ADADURA field differs from the DURATION and ORGDURA fields in that the time is computed to 6 decimal places instead of 4 decimal places.
ADD1 Adabas Control Block Fields (CB) Corresponds to the ACB field additions 1. The command to be executed determines whether this field is used and what the contents represent.
ADD2 Adabas Control Block Fields (CB) Corresponds to the ACB field additions 2. The command to be executed determines whether this field is used and what the contents represent.

When ADARUN parameter CLOGLAYOUT is set to 8, the content of this field is taken from the ACBX structure. Note that there are differences in meaning of the Additions 2 field in the ACBX and in the ACB.

In the ACBX, some information that was formally available in the Additions 2 field is now split into several fields. For example, the error-related subcode information that was originally provided in the Additions 2 in the ACB is now provided in the Adabas ACBXSUBS (Subcomponent Response Subcode) field. The Additions 2 field will contain the transaction sequence number for an OP (open) and RE (read ET data) command. In Adabas Review, if the ADARUN parameter CLOGLAYOUT is set to 8, you will find the information from the older ACB Additions 2 structure in the following separate Adabas Review fields:

  • CMPRECL contains the compressed record length.

  • ERRFLDNM contains the error field name.

  • RSPSUB contains the subcode for an Adabas response code.

  • UCMPRECL contains the uncompressed record length.

ADD3 Adabas Control Block Fields (CB) Corresponds to the ACB field additions 3. The command to be executed determines whether this field is used and what the contents represent.
ADD4 Adabas Control Block Fields (CB) Corresponds to the ACB field additions 4. The command to be executed determines whether this field is used and what the contents represent.
ADD5 Adabas Control Block Fields (CB) Corresponds to the ACB field additions 5. The command to be executed determines whether this field is used and what the contents represent.
CALLPGM Transaction Processing Monitor Fields (TP) The program that executed the last EXEC CICS LINK or XCTL command.
  • In non-DCI situations, this is the program calling the Adabas CICS link routine via EXEC CICS LINK

  • In DCI interface situations (used by Natural), this is the name of the executing program if there was no previous EXEC CICS LINK or, if there was a previous EXEC CICS LINK, the name of the program that executed the last EXEC CICS LINK.

CALLTYPE Adabas Command Log Fields (CLOG) Contains the type of the Adabas call that was issued. Possible values are:
  • "PHYSICAL": indicates a standard Adabas call

  • "REMOTE": indicates a call arriving via Entire Net-Work.

CDURA Client Reporting Fields (CMON) The total client duration time. This is the total time (in seconds) in which the client waits for the command to be processed by the server and the time it takes the ADALNK portion of the client to retrieve the command results. CDURA is the sum of the CRCVDURA and CWRKDURA fields.
CID Adabas Control Block Fields (CB) Corresponds to the hexadecimal value of the ACB field command ID. This field serves important functions, determined by the command, during command execution. For example, during a sequential read, the command ID is used to return the records to the user in the proper sequence. This field displays the value of the CID in hexadecimal format (for example, if CID=ABCD, it is displayed in this field as "C1C2C3C4").
CMD Adabas Control Block Fields (CB) Corresponds to the ACB field command code.
CMPRECL Adabas Control Block Fields (CB) Contains the compressed record length of the record returned by a READ or a FIND command.
COMMANDS Adabas Control Block Fields (CB) The number of Adabas commands processed for the control break.
CQDURA Interval and Time Fields (IT) Command queue duration. Contains the amount of time (in seconds) that a command waited in the command queue before being dispatched into an Adabas thread.
CRCVDURA Client Reporting Fields (CMON) The client receive time. This is the time (in seconds) it takes the Adabas link routine to retrieve a processed command from the server.
CWRKDURA Client Reporting Fields (CMON) The client wait time, or the time in which the server works for the client. This is the time (in seconds) in which the client waits for the command to be processed by the server.
DATE Interval and Time Fields (IT) The date (in YYYY-MM-DD format) when the Adabas command was processed.
DAY Interval and Time Fields (IT) The day number (within a month) when the Adabas command was processed.
DBID Adabas Control Block Fields (CB) The unique Adabas database identification number.
DURATION Adabas Command Log Fields (CLOG) The amount of time that the command spent in the Adabas thread, including time spent waiting for I/O operations to complete. This field is expressed in seconds and is accurate to 4 decimal places. The field ADADURA contains the same value accurate to 6 decimal places.
ENDDATE Interval and Time Fields (IT) The date (in YYYY-MM-DD format) when the last Adabas command was processed within the current report control break.
ENDTIME Interval and Time Fields (IT) The time (in 24-hour format) when the last Adabas command was processed within the current report control break.
ERRFLDNM Adabas Control Block Fields (CB) Error field name. Contains the Adabas 2-character name for a field that has been found to be in error in the Adabas format or search buffer.
FILE Adabas Control Block Fields (CB) Corresponds to the ACB field file number. The function of this field is determined by the Adabas command being issued. Fields FILE and FNR are alternate names for the same data; you can use either field in your reports.
FNR Adabas Control Block Fields (CB) Corresponds to the ACB field file number. The function of this field is determined by the Adabas command being issued. Fields FILE and FNR are alternate names for the same data; you can use either field in your reports.
FULLSTCK Interval and Time Fields (IT) The 8-byte store clock value taken when the Adabas command was processed.
HOUR Interval and Time Fields (IT) The hour (in 24-hour format) when the Adabas command was processed.
ISN Adabas Control Block Fields (CB) Corresponds to the ACB field ISN. The use of this field is determined by the command being issued.
ISNLL Adabas Control Block Fields (CB) Corresponds to the ACB field ISN lower limit. The field contains the lowest ISN that Adabas returns when retrieving ISN lists. The use of this field is determined by the command being issued.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNLL as well as ISNQ are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

ISNQ Adabas Control Block Fields (CB) Corresponds to a modification of the ACB field ISN quantity. The field is modified based on command type, and is suitable for performing mathematical calculations such as SUM and AVERAGE. The unmodified data can be found in the ORGISNQ field.

Note:
This field could be misinterpreted when used at the OP command, since the value of ISNQ as well as ISNLL are used for purposes other than the ISN lower limit or ISN quantity. Please refer to the Adabas Command Reference manual for further information.

JMREDATE Operating System Fields (OS) The date (in YYYY-MM-DD format) when the batch job was entered in JES or from the job information macro.
JOBCLASS Operating System Fields (OS) (z/OS only) The one-byte character of the CLASS parameter in the job card.
JOBID Operating System Fields (OS) A combination of the job identifier and the job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE:
  • Under z/OS, the field will contain JOB, STC, or TSU as the job identifier followed by a 5-byte JES job number.

  • Under z/VSE, the field will contain JOB as the identifier, followed by the 5-byte POWER job number.

JOBNAME Operating System Fields (OS) The name of the job or task from which the Adabas call was issued. This field is the contents of the JOBNAME from the Adabas command log record and may not reflect the actual JOBNAME of the task that issued the Adabas call.
JOBNUM OS The job number of the user who issued the Adabas call. This field is available under z/OS and z/VSE. The field will contain an alphanumeric, 5-byte value for the JES (z/OS) or POWER (z/VSE) job number.
LPARNAME Operating System Fields (OS) The system LPAR or partition name (in z/OS or z/VSE environments) or the environment name from the job information macro (in BS2000 environments).
MONAME Interval and Time Fields (IT) The name of the month when the Adabas command was processed.
MONTH Interval and Time Fields (IT) The number of the month when the Adabas command was processed.
NATAPPL Natural Fields (NAT) The Natural application name (or library) to which the user issued a LOGON. This field does not necessarily show the library of the Natural object from which the Adabas call is issued. Under SQL, this field contains the library name.
NATCLTID Natural Fields (NAT) NATCLTID displays the client user ID of a user using a Natural server. NATCLTID only contains a value if an RPC client request is executed in a Natural RPC server session. In all other cases the field is empty.
NATCOUNT Natural Fields (NAT) The total number of Adabas calls generated by the user application since the last terminal I/O.
NATEXEC Natural Fields (NAT) The number of times a Natural object that issues Adabas calls has been executed. NATEXEC is "1" if the Natural object has issued an Adabas call for the first time on this level; for each subsequent Adabas call on this level the value will be set to zero. You can use the SUM statement to total the values of this field to obtain the total number of times a specific Natural object has been called.
NATGRP Natural Fields (NAT) The current Natural security group to which the user belongs.
NATLEVEL Natural Fields (NAT) The Natural call level of the Natural program issuing the Adabas call. For example, a CALLNAT routine that is called from a program and issues an Adabas call has a Natural level of 2.
NATLIB Natural Fields (NAT) The name of the Natural library where the object is located that is currently executed.
NATPROG Natural Fields (NAT) The name of the Natural program that issued the Adabas call. When Natural internally issues Adabas calls to load Natural objects, this value is not updated. Under SQL, this field contains the program name.
NATRPCCO Natural Fields (NAT) The 16-byte alphanumeric value for the store clock value used as identification of the Natural RPC Server.
NATRPCID Natural Fields (NAT) The 16-byte alphanumeric value of the conversation ID from the Natural RPC Server.
NATSTMT Natural Fields (NAT) The Natural statement number where the Adabas command is processed. This line number is the line in the Natural program displayed by NATPROG. When the processed Adabas command is in the copy code portion of the Natural program, the line number refers to the copy code. The name of the copy code is not available at this time.
NATUID Natural Fields (NAT) The name of the Natural library to which the user is currently logged on. This is the value of the Natural system variable *APPLIC-ID.
NUCID Adabas Nucleus Fields (NUC) The ID of an Adabas nucleus in an Adabas Parallel Services or Adabas Cluster Services environment.
OP1 Adabas Control Block Fields (CB) Corresponds to the ACB field command option 1. The contents of this field is determined by the command being issued.
OP2 Adabas Control Block Fields (CB) Corresponds to the ACB field command option 2. The contents of this field is determined by the command being issued.
OPSYSNAM Operating System Fields (OS) The operating system name (SYSNAME) that is specified in the SYS1.PARMLIB and which will be obtained from the CVT (in z/OS environments) or the operating system name and version number (in BS2000 environments).
ORGDURA Adabas Command Log Fields (CLOG) The (original) value of the "duration" field contained in the command log record. The time is expressed in units of 16 microseconds.
QUARTER Interval and Time Fields (IT) The quarter of the year in which the Adabas command was processed.
ROUTDURA Operating System Fields (OS) The amount of time between the time a command was issued by the application and the time it was queued in the Adabas command queue. For Adabas 8.1 and earlier, this field is expressed in seconds; for Adabas 8.2 and later releases, this field is expressed in milliseconds. The ROUTDURA and ROUTTIME fields are alternate names for the same data; you can use either field in your reports.
ROUTTIME Operating System Fields (OS) Alternate name for ROUTDURA.
RSP Adabas Control Block Fields (CB) Corresponds to the ACB field response code. A response code of 0 indicates that the command executed successfully. This name is used in the schema portion of the summary record.
RSPSUB Adabas Control Block Fields (CB) Contains the Adabas response code subcode from the ACB field Additions 2 or the ACBX field ACBXERRC for certain nonzero Adabas response codes.
SECGID Transaction Processing Monitor Fields (TP) Contains the security system group ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
SECUID Transaction Processing Monitor Fields (TP) Contains the security system user ID for the user who issued the Adabas call. This field is available under z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).
SEQ Adabas Command Log Fields (CLOG) The Adabas command sequence number. The value is incremented by one for each Adabas command processed.Fields SEQ and SEQUENCE are alternate names for the same data; you can use either field in your reports.
SEQUENCE Adabas Command Log Fields (CLOG) The Adabas command sequence number. The value is incremented by one for each Adabas command processed.Fields SEQ and SEQUENCE are alternate names for the same data; you can use either field in your reports.
SRCHTYPE Adabas Command Log Fields (CLOG) The type of search or search algorithm. This field contains one of the following values if the Adabas command log is for version 8.2 SP2 or later:
  • ALGO-1: Search algorithm 1 was used.

  • ALGO-2: Search algorithm 2 was used.

  • ALGO-3: Search algorithm 3 was used.

  • ALGO-4: Search algorithm 4 was used.

  • MIXED: A nondescriptor search combined with a descriptor search was used.

  • NONDES: A nondescriptor search occurred.

If the Adabas command log is for an older Adabas release (8.2 SP1 or earlier), the value of the SRCHTYPE field will be blank.
STEPNAME Operating System Fields (OS) The name of the job step or task step that issued the Adabas call. This step is only available in z/OS environments.
STRTDATE Interval and Time Fields (IT) The date (in YYYY-MM-DD format) when the first Adabas command was processed within the current report control break.
STRTTIME Interval and Time Fields (IT) The time (in 24-hour format) when the first Adabas command was processed within the current report control break.
THDURA Adabas Control Block Fields (CB) The active thread time for a command. This is the time, in milliseconds, required to process the Adabas call, not including the wait time caused by I/O or other required resources. The value of this field is obtained from the command time field in the Adabas command log (LOX1CTME).
THTIME Adabas Control Block Fields (CB) Alternate name for THDURA.
TID Transaction Processing Monitor Fields (TP) The Com-plete terminal ID number of the user who issued the Adabas call.
TIME Interval and Time Fields (IT) The time (in 24-hour format) when the first Adabas call was processed.
TOTDURA Interval and Time Fields (IT) Total duration. Contains the amount of time the command was in the Adabas thread plus the amount of time the command waited in the command queue. The TOTDURA field is the sum of the ADADURA and CQDURA field values expressed in seconds.
TPTRANNM Transaction Processing Monitor Fields (TP) The transaction number as established by the user's TP system for the transaction that issued the Adabas call.
TPUSERID Transaction Processing Monitor Fields (TP) The user ID on the TP monitor from which the Adabas call was issued.
TRANSID Transaction Processing Monitor Fields (TP) The name of the root transaction or program that issued the Adabas call.
TRUENAME Transaction Processing Monitor Fields (TP) The name of the Adabas CICS link routine TRUE exit.
UCMPRECL Adabas Control Block Fields (CB) Uncompressed record length. The uncompressed length of the Adabas format or search buffer field.
UOWID Transaction Processing Monitor Fields (TP) Contains the instance number and the sequence number of the CICS field NETUOWID, which is 27 bytes long. This field can only be filled in by CICS. The evaluation of this field requires a large amount of CPU time and, therefore, can only be activated by a special zap. Following is a description of the bytes in NETUOWID:
  • Offset 0 (Length 1): The length (L) of the Logical-Unit-of-Work-Identifier-Field, not including this field. The NETUOWID contains Logical-Unit-of-Work-Identifier-Field plus padding bytes. Values: 0 or 10 < = L < = 26.

  • Offset 1 (Length 1): The length of Network Name, not including this field, m = L - 9 , 1 < = m < = 17.

  • Offset 2 (Length m): Network name, format: ABCDEFGH.ABCDEFGH, Networkid.Luname.

  • Offset m + 2 (Length 6): Instance number.

  • Offset m + 2 + 6 (Length 2): Sequence number.

  • Offset m + 2 + 6 + 2 (Length until 27): Residual data.

USERID Adabas Command Log Fields (CLOG) The 28-byte Adabas communication ID of the user for whom the command was processed.
USERTYPE Transaction Processing Monitor Fields (TP) The type of TP system from which the Adabas call was issued. For example, if the Adabas call was issued from a CICS session, the USERTYPE field contains "CICS".
WEEK Interval and Time Fields (IT) The week number of the week in which the Adabas command was processed.
WEEKDAY Interval and Time Fields (IT) The name of the day on which the Adabas command was processed.
YEAR Interval and Time Fields (IT) The year (in YYYY format) in which the Adabas command was processed.

Top of page

Adabas Review Duration Field Derivations

In Adabas Review, fields containing times as well as durations are recorded. Time fields represent the time of day at which something occurred; duration fields are calculated and represent the length of time it took a process to occur. The following duration fields are calculated by Adabas Review processing.

Field System Name Category Field Length Format Alternate Names Description
ADADURA IT 4 B --- Adabas duration. Corresponds to the DURATION field. This field contains the amount of time (in seconds) that the command spent in the Adabas thread, including the time spent waiting for the completion of I/O operations. The ADADURA field differs from the DURATION and ORGDURA fields in that the time is computed to 6 decimal places instead of 4 decimal places.
CDURA CMON 8 B --- The total client duration time. This is the total time (in seconds) in which the client waits for the command to be processed by the server and the time it takes the ADALNK portion of the client to retrieve the command results. CDURA is the sum of the CRCVDURA and CWRKDURA fields.

Measurement for this field starts immediately after the command is passed to the server (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 router processing is performed). Measurement stops when the client picks up the command result information from the server (performing SVC-16 router processing within the Adabas link routine).

CMDRESP CB 4 B CMDRSP

MCR

The time, in milliseconds, required to process the Adabas call. In the command table, Adabas Review stores the minimum Adabas duration for each command type returning a zero response code. The command table is updated whenever a lower duration value is encountered. Command response time is thus based on the command time field in the Adabas command log.

The values for CMDRESP in the history file are automatically stored in seconds. To display them correctly, they must be converted to milliseconds. For more information on this conversion, read Migration from Previous Versions .

If you need to continue using the old scale and the old calculation algorithm for history data, contact your Software AG support representative.

Due to changes in the display programs in SYSREVDB, you cannot use SYSREVDB in Adabas Review 4.4 (or earlier versions) to display the field contents of CMDRESP correctly, unless you stay with the old scale and algorithm.

CQDURA IT 4 B --- Command queue duration. Contains the amount of time (in seconds) that a command waited in the command queue before being dispatched into an Adabas thread.
CRCVDURA CMON 8 B --- The client receive time. This is the time (in seconds) it takes the Adabas link routine to retrieve a processed command from the server.

Measurement for this field starts immediately after the server posts the Adabas link routine to retrieve the command result information (performing SVC-12 router processing) . Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-16 router processing).

CWRKDURA CMON 8 B --- The client wait time, or the time in which the server works for the client. This is the time (in seconds) in which the client waits for the command to be processed by the server.

Measurement for this field starts immediately after the command is passed to the server for processing (when it is posted from the Adabas link routine to the Adabas address space and SVC-4 processing is performed). Measurement stops when the Adabas link routine retrieves the command information from the server address space (performing SVC-12 router processing).

ESTCPU IT 6.6 N --- The estimated CPU time used by each Adabas command. The values shown in this field are only relative approximations of the CPU time used; they are not based on any actual CPU times and are calculated, instead, based on an algorithm. The algorithm used varies for each Adabas command type and is based on the number of instructions, I/Os, descriptors, and fields used.

This field can be used as a SUM, MIN, MAX and/or AVG field.

ROUTDURA OS 8 B ROUTTIME The amount of time between the time a command was issued by the application and the time it was queued in the Adabas command queue. For Adabas 8.1 and earlier, this field is expressed in seconds; for Adabas 8.2 and later releases, this field is expressed in milliseconds.
THDURA CB 8 B THTIME The active thread time for a command. This is the time, in milliseconds, required to process the Adabas call, not including the wait time caused by I/O or other required resources. The value of this field is obtained from the command time field in the Adabas command log (LOX1CTME).
TOTDURA IT 4 B --- Total duration. Contains the amount of time the command was in the Adabas thread plus the amount of time the command waited in the command queue. The TOTDURA field is the sum of the ADADURA and CQDURA field values expressed in seconds.

The following diagram depicts how these duration fields are calculated by Adabas Review:

graphics/timefld_process.png

**: The REVEXIT entry points REVEXIT1 (formerly REVEXITB) and REVEXIT2 are generated and linked to the ADALNK link routine when you install the components of Adabas Review that depend on a particular TP monitor. For more information, read about installation phase 2 in your Adabas Review installation documentation.

Top of page