SYSTEM/LOG
Use the following COMS commands to capture OLTP diagnostic information in the SYSTEM/LOG file.
To start collection of diagnostic information for a program list programlist:
LOGDIAG + programlist
To stop collection for a program list programlist:
LOGDIAG - programlist
To print the diagnostic information, use the following command, which initiates selective reporting of the SYSTEM/LOG file using the LOGANALYZER program:
LOG [PRINTER] DIAG(DTP(AP))
EXAMINER
The EXAMINER program can process records identifying the start and completion of an OLTP AUTO; WRITE within a client application. The following table displays the code and id associated with the initiation and receipt of an OLTP message.
Code | Id | Meaning |
---|---|---|
435 | 0 | Initiation of OLTP message |
430 | 8 | Receipt of OLTP message |
OLTP transactions within a server application appears in normal input transactions without unique identification. The figure below shows the EXAMINER transaction flow.
EXAMINER Transaction flow
For COMSTP programs, EXAMINER data is captured before an OLTP client initiates an OLTP TRANSACTION; request, and after it receives the associated reply.
Within an OLTP Server, EXAMINER data is captured as it processes the transaction.
However, there is no information in EXAMINER data that enables you to associate an OLTP TRANSACTION; command with a particular OLTP transaction being processed by the server.