vbs2.trace

All connection-relevant information and all messages emanating from ROBAR-CL are logged in the file vbs2.trace.

First, the device allocation is queried for each BS2000 system setting up a connection (SHOW-DEVICE-STATUS with TYPE=MBK and ATTRIBUTE=ATTACHED, see “Introduction to System Administration” [2]).
If no device is attached in the BS2000 system <<MNEM;L VSN>>, else <<MNEM;L VSN>;<TH;>;<TI;>> is logged to the trace file (see also example on the next page).

Then, during the rest of the ROBAR session, a trace entry is generated for every message which leads to a ROBAR job.

Extract from a vbs2.trace file.
The file corresponds to the trace file on "robar.trace".

Example

RSV1057 Trace file (ROBAR ver>) created at  :  <date> <time>
<070628150356>  RSV1055 ROBAR session started 
<070628150408>  1. START:  partner-id = PAD5EDXX
<070628150433>  PAD5EDXX:  SHOW-DEV  <<MNEM;L VSN>;<TH;>;<TI;>>
<070628150433>  SYSSTART:  partner-id = PAD5EDXX,  host = D17Z19,  status = A
<070628150433>  PAD5EDXX:  TH ATTACHED
<070628150433>  PAD5EDXX:  TI ATTACHED
<070628150618>  PAD5EDXX:  <NKVT013;?;0HDM;000062;TH; ;SPECIAL;LIST TAPE-U4 
                           ,VSN=000062>
<070628150640>  PAD5EDXX:  <NKVT010;%;  TM;000062;TH>
<070628150640>  PAD5EDXX:  <NKVT017;%;0HDM;TH>
<070628150645>  PAD5EDXX:  <NKVT097;%;  TM;000062;TH>
|               |          |
1               17         28
Column

Meaning of entries:

Col. 1:	Time stamp	(Format: <yymmddhhmmss>)
Col. 17:	1. START :	for the 1st BS2000 system that sets up a connection
	RESTART :	for the 2nd and all subsequent BS2000 systems that set up a connection
	SYSSTART :	A connection has been set up as a result of a SHOW-DEVICE-STATUS command
	SYSEND :	Close connection
	-------- :	Message is not processed by ROBAR
	xxxxxxxx :	TNS remote name of BS2000 host (message is processed by ROBAR)
Col. 28:	Console message, or for 1. START, SYSSTART and SYSEND: partner-id =TNS partner name, host = host name status = A (connection set up) or D (connection closed)