Locks can be placed on each DAM or TAM file. This means that a deadlock may occur between UAPs which can normally be executed in parallel without a deadlock occurring (because the UAPs have exclusive access to separate blocks within a DAM file, for example).

If a deadlock occurs, take one of the following actions:

• Suppress lock in the offline tester environment definition.
• Suppress update by specifying the -c option in the utfstart command.
• Prevent the UAPs from running in parallel by entering the start subcommand to start the UAPs sequentially after the offline tester starts.

The offline tester processes files by block, regardless of the value set as the number of batch processing blocks when issuing the dc_dam_create or dc_dam_iopen function. However, no processing is performed when the specified value is less than zero.

Always issue the dc_dam_close or dc_tam_close function after issuing the dc_dam_open or dc_tam_open function.

If the service group is terminated without issuing the dc_dam_close or dc_tam_close function, a duplicate open error or lock error may occur at the DAM (or TAM) file when the service is re-executed. If an error occurs, enter the stop subcommand to terminate the service (or service group), then enter the start subcommand to reactivate the service.

COBOL UAPs cannot place locks on TAM files. When creating a UAP in COBOL, specify suppression of lock in the TAM definition statement in the offline tester environment definition.

If suppression is not specified, a lock error may occur when a service that accesses a TAM file is restarted. If an error occurs, enter the stop subcommand to terminate the service (or service group), then enter the start subcommand to restart the service.