Analyzing the vector log file dump

The vector log file dump displays the flow of data between CICS applications and a virtual terminal.

About this task

The vector file dump can contain the header structures, the inbound and outbound vectors, and optionally the vector data.

Procedure

  1. Review the header of the vector file dump to find the context of where the error occurred. For example, it tells you the request name that was being processed when the error occurred, the name of the Link3270 server adapter program, the BTS process type and name that the server adapter was running under. This header is then followed by the vectors and flow of data that occurred.
  2. Check each inbound and outbound vector message structure (BRIV). Each one is preceded by the Link3270 bridge header structure, BRIH.
    1. Check the Return code fields to see if the value is zero or another number. If it is not zero, the Link3270 bridge mechanism has reported an error. This error is the result of an earlier inbound ALLOCATE facility message, DELETE facility message, or inbound vector message (BRIV) sent from CICS Service Flow Runtime to the Link3270 bridge mechanism, (DFHL3270).
    2. Check the completion and reason codes. If these are not 0, look up the codes in the CICS External Interfaces Guide Version 2 Release 2 to find an indication of what error occurred.

Example

For an annotated example of the vector log file, see Vector file dump.


usinglink3270vectorlogfile.html | Timestamp icon Last updated: Sunday, 4 June 2017