A UTM application is terminated abnormally by any of the following events:
internal UTM error
error in the system environment, e.g. database system not available
UTM administration command KDCSHUT KILL (or by the corresponding WinAdmin/WebAdmin or KDCADMI function)
UTM generation error
The following actions are performed when a UTM application is terminated abnormally:
All transactions currently being processed by the individual processes are aborted immediately.
The connections to all communication partners of the application are shut down.
The connection to the database system is shut down.
A UTM-specific dump is created for each work process of the application. See also the openUTM manual “Messages, Debugging and Diagnostics on BS2000 Systems”.
All processes of the application are terminated and all files are closed. No attempt is made to bring the KDCFILE to a consistent state. This does not occur until the application is restarted.
If the UTM application was being monitored by a job variable (see "Restarting after an abnormal application termination"), the first column of the job variable is set to “T” and the second to “A”.
Following an abnormal termination of the application, you must first determine the cause of the crash. To find the cause, look for message K060 in the SYSLST log. This message contains the dump error code as an insert. This error code gives precise information regarding the cause of the abnormal termination. You can also find the cause for the dump as part of the name of the UTM dump file. The meanings of the dump error codes are described in the openUTM manual “Messages, Debugging and Diagnostics on BS2000 Systems”. There are three possibilities:
The dump error code indicates that a KDCDEF operand must be modified.In this case, the KDCFILE must be regenerated. If you want to retain the application data in the page pool, proceed as follows:
warm start with ASYNTASKS=0, TASKS=1
terminate the application normally with KDCSHUT NORMAL
new KDCDEF generation with the modified operand
transfer the application data from the old to the new KDCFILE using KDCUPD
start the application with the new, updated KDCFILE
The dump error code cites the cause as:
DMS error
memory bottleneck
the database system is currently not available
When the error has been rectified, you can restart the application, and openUTM executes a warm start automatically.
Otherwise (if the dump error code is not described) a system error has occurred. In this case, produce diagnostic documentation and write a problem report to the system support personnel. Please refer to section "Diagnostic documentation for a problem report" for information on which documentation is required by system support.
A warm start with the same KDCFILE is not always successful in this case. If a warm start cannot be performed, you must regenerate the KDCFILE using KDCDEF.