A program unit is terminated abnormally by openUTM in the following situations:
A PEND ER or FR was programmed.
A UTM call supplied a KDCS return code >=70Z. In this case, openUTM internally sets PEND ER.
In both situations, openUTM aborts the service. If a PEND FR was programmed, then openUTM does not take any other action.
If the service was terminated by a PEND ER (in a program or internally), then openUTM creates
a UTM dump with REASON=PENDER, which only conveys the data of KDCROOT.
a memory dump of the class 5 and class 6 memory. This can be analyzed using the BS2000 utility DAMP.
By default, this memory dump is suppressed because openUTM runs as an ENTER process. If you want the memory dumps of the class 5 and class 6 memory to be created, specify the following command in the start procedure (see "Starting the application") before the application program is loaded:
/MODIFY-TEST-OPTIONS DUMP=YES
openUTM then terminates the affected application program. This prevents follow-up errors arising due to the possible overwriting of an application program.
With a branch statement in the start procedure, the application program can be loaded dynamically and openUTM can continue running with the desired number of tasks.
CAUTION!
If there is no branch statement, the task is terminated and, in the case of the last task, the application is terminated.