In the DBLOG Menu, you can activate or deactivate logging and specify which Adabas commands, SQL statements, or VSAM calls are to be logged.
To invoke the DBLOG Menu
Enter one of the following Natural system commands:
For Adabas:
TEST DBLOG MENU
For SQL:
TEST DBLOG Q MENU
For VSAM:
TEST DBLOG V MENU
This section covers the following topics:
The functions provided in the DBLOG Menu are described in the following section. You can execute a function by either entering the code that corresponds to the required function in the Code field or pressing the PF key that corresponds to the required function.
Code or |
Function | Explanation |
---|---|---|
B
or PF4 |
Activates the DBLOG logging of the Adabas commands, SQL statements, or VSAM
calls that match the selection criteria.
See also alternative commands in TEST DBLOG Command. |
|
E
or PF5 |
Deactivates logging and displays the DBLOG Trace screen
of the current log record if data exists in the Natural DBLOG buffer. Current log
data is kept in the Natural DBLOG buffer.
See also alternative commands in TEST DBLOG Command. |
|
S
or PF6 |
Adabas: Interrupts a program at a specified Adabas command and displays
detailed information on this command only: see Snapshot Function for Adabas
Commands.
SQL and VSAM: Collects detailed information on a specified SQL statement or VSAM call: see Snapshot Function for SQL Statements and Snapshot Function for VSAM Calls. |
|
W
or PF7 |
Writes the logged data contained in the Natural DBLOG buffer to a work file.
The file structure (columns and log sequence) corresponds to the structure of the
DBLOG Trace screen described in DBLOG Trace Screen.
When you choose this function, a Work File Selection window prompts you for the following information:
|
|
Only applicable to Adabas commands.
Selects additional
Adabas buffers to be logged when using function code |
||
PF3 | Exits the DBLOG Menu. The current log records are kept in the Natural DBLOG buffer. | |
PF12 | Clears the Natural DBLOG buffer, leaves the DBLOG Menu and returns to the NEXT prompt. |
This section describes the input fields the DBLOG Menu provides for specifying selection criteria to restrict logging:
Field | Explanation |
---|---|
Skip | Only applicable with function code S .
Number of commands, calls or statements to be skipped before logging is to start. |
Program | Restricts logging to commands, calls or statements issued by the program specified. |
DBID | Only applicable to Adabas commands.
Restricts logging to commands issued for the database ID specified. |
FNR | Only applicable to Adabas commands.
Restricts logging to commands issued for the file number specified. |
Line from |
Restricts logging to commands, calls or statements within the range of the source line numbers specified. |
Low Resp |
Only applicable to Adabas commands and VSAM calls.
Restricts logging to commands which result in a response code (Adabas) or return code (VSAM) within the range specified. |
Low SQLC |
Only applicable to SQL statements.
Restricts logging to statements which result in an SQL return code within the range specified. |
Only applicable to Adabas commands.
The Adabas control block is logged by default. It is either the classic Adabas control block (ACB) or the extended Adabas control block (ACBX) depending on the command executed. For detailed information on Adabas control blocks, see Adabas Control Block Structures (ACB and ACBX) in the Adabas for mainframes documentation.
In addition to the control block, you can log one or more Adabas buffers listed in the DBLOG Menu:
FB | Format buffer |
RB | Record buffer |
SB | Search buffer |
VB | Value buffer |
IB | ISN buffer |
You enable logging of these buffers and specify the range of bytes to be logged by using the input fields below the buffer names:
Mark the buffer(s) to be logged by entering any character next to the required buffer(s). By default, a maximum of 80 bytes (from 0 to 79) is logged per buffer if no value is entered in the From and To fields.
You can enter a start number (for example, 100
) that determines from
which byte the buffer is logged.
If you want to log an entire buffer (maximum is 32 KB), enter X
or
*
(asterisk) and leave the To field blank.
You can enter an end number (for example, 200
) that determines up to
which byte the buffer is logged. The maximum input value is 32767
(32
KB).
If the length of the buffer(s) to be logged exceeds the total limit of 2097151 KB (2 GB - 1 byte), Natural issues an appropriate message as described in Data Processing and Storage.
The logs of the buffers can be displayed on the DBLOG Trace screen as described in Displaying Adabas Buffers.
Note:
The snapshot function (see the relevant section) logs all Adabas buffers by default.
Therefore, you need not mark any of the optional buffers before you execute this
function.