The offline tester uses pipe and shared memory facilities to control processes.

If the offline tester is terminated abnormally in an irregular manner by pressing the interrupt key, for example, the shared memory area and any temporary files in current use are saved as allocated. The offline starter can still be restarted, but the shared memory area and temporary files should be deleted if resource efficiency is likely to be affected.

The offline tester uses the following names for temporary files:

• shmxxxx (in the /tmp directory)
• cpixxxx (in the /tmp directory)
• ppixxxx (in the /tmp directory)
• tttttttt (in the /tmp directory)
• aaaaaaaaxxxx (in the /tmp directory)

Legend:

xxxx

Hexadecimal display of process ID at execution

tttttttt

Same name as logical terminal name returned when the dc_mcf_receive function receives the first segment. (Up to 8 characters)

aaaaaaaa

Same name (up to 8 characters) as the IST table name specified in the offline tester environment definition file.

Example:

• shm4e7
• cpi3e9
• ppi3e8
• termnalA

If the offline tester terminates abnormally, the UAP process and debugger process (if a debugger is connected) may still be active, depending on the termination timing. In such cases, execute the kill command to terminate the processes.

Table 12-1 sets out the upper limits of the offline tester.

Table 12-1 Upper limits of offline tester

Item	Description	Upper limit	Processing when upper limit is exceeded
UAP startup wait time	Time from generation to activation of a UAP process (dc_rpc_open function) when starting the offline tester or executing the start subcommand	60 minutes	An error message is output and the process is forcibly terminated.#1
UAP stop wait time	Time from a termination request to actual termination of a UAP process when stopping the offline tester or executing the stop subcommand. Or, if debugger connection is specified for the UAP, time until the debugger process terminates.	10 minutes	Forcibly terminate the UAP process or debugger process.
Command line length	Length of command lines in offline tester subcommands. Or, length of definition lines in the continuous execution command file	254 bytes	An error message is output and the command is rejected.
Definition line length	Length of definition lines in the offline tester environment definition file or in the function return values file	510 bytes	An error message is output. The line is ignored and definition analysis continues.#2
Length of pathname information	Length of directory names and pathnames specified in the offline tester environment definitions and commands	255 bytes	An error message is output and the specification is ignored.
Number of function return value definitions	Number of function return values defined in the function return values file	200	An error message is output. Subsequent lines are ignored and processing continues.
Number of DAM files	Number of DAM files opened by the dc_dam_open or dc_dam_create function in a UAP	200	An error message is output and the dc_dam_open or dc_dam_create function returns an error value.
Number of TAM files	Number of TAM files opened by the dc_tam_open function in a UAP	200	An error message is output and the dc_tam_open function returns an error value.
Number of dc_rpc_call functions	Number of UAP executions of the dc_rpc_call function with DCRPC_NOWAIT specified when dc_rpc_poll_any_replies is not issued	200	An error message is output and the dc_rpc_call function returns an error value.
Number of synchronous message send/receive functions	Number of executions of the dc_mcf_sendrecv and dc_mcf_recvsync function in a service	100	An error message is output and the dc_mcf_sendrecv or dc_mcf_recvsync function returns an error value.

#1: Excluding UAPs for which debugger connection is specified.

#2: When definition analysis is completed, the system waits for command input to continue or cancel offline tester startup.

Using the offline tester, the dc_rpc_call function can be used to execute nested services within a service function. However, a service can only be called once within nested services that belong to the same service group.

Figure 12-3 illustrates the use of recursive calls using the offline tester.

Figure 12-3 Recursive calls using the offline tester

The offline tester outputs an error message and an error value is returned when one of the following functions is issued before or after a service call (before the dc_rpc_mainloop or dc_mcf_mainloop function is issued or after the dc_rpc_mainloop or dc_mcf_mainloop function returns):

• dc_rpc_call
• dc_adm_call_command
• MCF function other than dc_mcf_open, dc_mcf_close, or dc_mcf_mainloop

Of the functions related to user exit routines, the offline tester does not support the dc_mcf_svstart function. To test a UAP that includes this function, create and link a dummy function of the same name.

The offline tester does not support accessing of TAM tables in DAM file access functions. Operation is not guaranteed if access is attempted.

The offline tester does not support processing that depends on whether the process is inside or outside a transaction.

The tpsend function cannot be used for event notification in interactive service requests using an XATMI interface. To check UAP events, use the function return values file.

The IST simulation facility of the offline tester stores IST table contents in a temporary file for reference or update. This may cause a file access error that does not occur otherwise.

When this error occurs, the system issues an error message. The function that caused the file access error returns with an error condition. The return value corresponds to one of error return values returned by that function.