Vector file dump
This output is an example of a vector file dump that has been taken after implementing vector logging for a Link3270 server adapter. It includes annotations to explain the important information.
The vector file dump is formatted using the copybook DFHMARLV.
08/04/06 CICS SFR Link3270 Navigator Vector Dump PAGE 1
--------------------------------------------------------------------------------------------------------------------------
**************************************************************************************************************************
Userid: SFRUSR Applid: IYCWZCHV Tranid: CMA0 Eibtaskn: 0006551 1
Request: MAIVPREQ Service: Program: DFHMAVCL
Proctype: DFHMAINA Process: SFRUSR0000037003363677417180
Date: 08/04/06 Time: 14:54 Abstime: 003287832894400 Record seq#: 1
**************************************************************************************************************************
*** ALLOCATE FACILITY ***
Structure: BRIH
Version: 1
Structure length: 180
Facilitytoken: (NEW)
Netname: (DEFAULT)
Terminal: (DEFAULT)
Transactionid: CBRA (Allocate facility)
Datalength: 0
Getwaitinterval: 4200000
Facilitykeeptime: 300
Facilitylike: (DEFAULT)
AID: ENTER (' )
Startcode: TD (Terminput)
Cancelcode: (NONE)
ADSDescriptor: 0 (NO)
Conversationaltask: 1 (YES)
Cursorposition: 0 (DEFAULT)
******************************************************************************************************************************
Date: 08/04/06 Time: 10:50 Abstime: 003363677428600 Record seq#: 2
******************************************************************************************************************************
*** ALLOCATE FACILITY RESPONSE ***
Structure: BRIH
Version: 2 (Extended)
Structure length: 180
Facilitytoken: X'0094000100000001'
Region ID: ZCHV
Netname: AAA}
Terminal: AAA}
Transactionid: CBRA (Allocate facility)
Datalength: 0
Return code: 0 (OK )
Comp code: 0
Reason code: 0
Function: ******************************************************************************************************************************
Date: 08/04/06 Time: 10:50 Abstime: 003363677428600 Record seq#: 3
******************************************************************************************************************************
*** INBOUND ***
Structure: BRIH 2
Version: 2 (Extended)
Structure length: 180
Facilitytoken: X'0094000100000001'
Region ID: ZCHV
Netname: AAA}
Terminal: AAA}
Transactionid: CMAV
Datalength: 180
Getwaitinterval: 4200000 3
Facilitykeeptime: 300
Facilitylike: (DEFAULT)
AID: ENTER (' )
Startcode: TD (Terminput)
Cancelcode: (NONE)
ADSDescriptor: 0 (NO)
Conversationaltask: 1 (YES)
Cursorposition: 5
******************************************************************************************************************************
Date: 08/04/06 Time: 10:50 Abstime: 003363677428730 Record seq#: 4
******************************************************************************************************************************
*** OUTBOUND SEND MAP (1804) ***
Structure: BRIH
Version: 2 (Extended)
Structure length: 180
Facilitytoken: X'0094000100000001'
Region ID: ZCHV
Netname: AAA}
Terminal: AAA}
Transactionid: CMAV
Datalength: 1156
Return code: 0 (OK ) 4
Comp code: 0
Reason code: 0
Function:
Abendcode: (NONE)
Taskendstatus: 65536 (Endtask)
Remainingdatalength: 0
08/04/06 CICS SFR Link3270 Navigator Vector Dump
-----------------------------------------------------------------------------------------------------------------------------
SYSID: ZCHV
Nexttransactionid: CMAV
Nexttranidsource: 0 (Normal)
Erroroffset: 0
Seqno: 1
BRIV vector length: 976 5
SM Erase indicator: ERASE
SM ERASEAUP: NO
SM Free Keyboard: NO
SM Alarm: NO
SM FRSET: NO
SM Last: NO
SM Wait indicator: NO
SM cursor position: -1 (DYNAMIC)
SM MSR data: NONE
SM Mapset: DFHMAB1
SM Map: MAPA
SM data indicator: DEFAULT
SM data length: 882
SM data offset: 92
SM ADSD length: 0
SM ADSD offset: 0
SM ACCUM: NO
(partial ADS from dump) 6
0 : | 00000000 00000000 00000000 0000F000 00005C5C 5C40C3E4 | | ..............0...*** CU |
24 : | E2E3D6D4 C5D940C9 C4C5D5E3 C9C6C9C3 C1E3C9D6 D5405C5C | | STOMER IDENTIFICATION ** |
48 : | 5C0000F0 000000C3 C9C6E2F0 F1404040 400000F0 00000000 | | *..0...CIFS01 ..0.... |
72 : | 00000000 00000000 000000C8 00F40040 40404040 00006000 | | ...........H.4. ..-. |
- This section is the header for the dump file and includes the following
fields:
Field name Description Userid The user ID under which the vector log file records were written and service flow processing was running. Applid The APPLID of the CICS region where the Link3270 server adapter was running. Eibtaskn The task number assigned by CICS to the Link3270 server adapter transaction. Request The name of the request that was being processed. This field corresponds to the request name of the service flow. Service The service name used in the Link3270 server adapter. This field can be blank. If specified, it is used to provide part of the Link3270 state file key when multiple bridge facilities are allocated, and remain in use for a specific user ID in adapter server processing. Program The name of the Link3270 server adapter. Proctype The BTS process type of the request or the process under which the Link3270 server adapter was running. Process The process name of the request processing instance under which the Link3270 server adapter was running. Date The date that the records were written to the vector log file. Time The time that the records were written to the vector log file. Abstime The time as reported by CICS when the vector log file records were written. This time is retrieved using an EXEC CICS ASKTIME command. Record seq# The sequential count of the specific record written to the vector log file by the Link3270 server adapter. - The fields Structure down to Datalength are common to both inbound and outbound messages.
- The fields Getwaitinterval down to Cursorposition are used only for inbound messages.
- The field Return code and onwards refer to inbound or outbound response messages only.
- SEND MAP vector. The format is different for inbound and outbound vectors. Only one appears for every record. Each inbound and outbound vector message structure, BRIV, is preceded by the Link3270 bridge header structure BRIH.
- The beginning of the application data structure (ADS) or screen buffer. This data is provided when you run full vector logging. If you have selected vector logging trace, you do not get this information. When using full vector logging, the vector data that is displayed as contents in the vector dump is the accumulated map buffer, text data, or screen buffer that is returned to the generated Link3270 navigator. The buffer contents in the vector dump might not always contain the individual vector data returned from the Link3270 bridge.