OpenTP1 Version 7 Tester and UAP Trace User's Guide

[Contents][Index][Back][Next]

2.8.1 Collecting UAP trace information

The online tester collects UAP trace information for the UAP running in test mode at the entrance and exit of each OpenTP1 function. This is called collecting UAP trace information.

The functions provided by OpenTP1 that access a user server, an RPC function, a DAM file, or a TAM file can use an online tester facility that collects a trace of all the I/O data specified in the function. This is called collecting of the complete I/O data trace.

Table 2-4 shows the functions that can use an online tester facility that collects the complete I/O data trace.

Table 2-4 Functions that can use the complete I/O data trace collection facility

Facility Function name
C format COBOL format
User server Service function start Service program start
Service function end Service program end
Service function start (at retry) Service program start (at retry)
Service function end (at retry) Service program end (at retry)
Remote procedure call
dc_rpc_call
CBLDCRPC('CALL    ')
dc_rpc_cltsend
CBLDCRPC('CLTSEND ')
DAM file service
dc_dam_read
CBLDCDAM('DCDAMSVC', 'READ')
dc_dam_rewrite
CBLDCDAM('DCDAMSVC', 'REWT')
dc_dam_write
CBLDCDAM('DCDAMSVC', 'WRIT')
TAM file service
dc_tam_read
CBLDCTAM('FxxR')('FxxU')
dc_tam_rewrite
CBLDCTAM('MFY ')('MFYS')('STR ')
dc_tam_write
 
IST service
dc_ist_read
CBLDCIST('DCISTSVC', 'READ')
dc_ist_write
CBLDCIST('DCISTSVC', 'WRIT')
User journal collection
dc_jnl_ujput
CBLDCJNL('UJPUT  ')

The complete I/O data trace is collected at different times depending on the function, as shown below.

UAP trace information is collected in trace files. A trace file is created automatically for each OpenTP1 system when the online tester collects the first trace information. When full, the trace file is swapped with another file.

Trace information for a number of OpenTP1 functions is collected in one file at completion of a service function, for example. Also, if the UAP terminates abnormally, trace information is extracted from the core file and saved in the trace file. For this reason, trace information may not be collected if the online tester is immediately terminated during UAP execution or if no core file is collected at abnormal UAP termination.