Program errors are errors in the programming of the KDCS interface (see chapter "KDCS return codes in KCRCCC"), formatting errors or errors that lead to STXIT events. openUTM then generates messages that are output by default to SYSOUT, SYSLST and generally also to SYSLOG (see "Destinations of UTM messages").
Formatting errors
Whenever there are formatting errors, openUTM issues message K087 and - if the formatting system requests it - message K153. If there are formatting errors when an asynchronous message is output, openUTM also issues message K063. If there are formatting errors in the dialog, openUTM issues message K015 in cases where the formatting error does not lead to abnormal termination of the service.
When errors occur in the FORMAT event exit, openUTM enters the return code FRxx in the KCRCDC field. The FORMAT exit defines the meaning of these return codes.
If serious formatting errors occur while formatting with FHS, openUTM reports these with an internal return code KCRCDC = FHxx, e.g. ’FH01’. In this case, the message contains the 4-byte, printable, secondary FHS return code described in the manual “FHS Format Handling System for openUTM, TIAM, DCAM”.
These messages contain the following entries:
K015 Formatting error &RCDC &RCF2A - input pleasecontains the entries
&RCDC : internal return code in the KCRCDC field&RCF2A :secondary FHS return code or VTSU return codeK063 Formatting error &RCF1A &RCF2A for format &FMTN asynchronous messagefor LTERM = <RMcontains the entries
&RCF1A : internal return code in the KCRCDC field&RCF2A : secondary FHS return code&FMTN : format name<RM : name of the LTERM to which the message was sentK087 Error in the interoperation of UTM and format handling system:opcode = &OPCD3, return code = &ERCD4 &ERCD5contains the entries
&OPCD3 : operation code at the interface IUTMFORM&ERCD4 : internal return code FHxx in the KCRCDC field&ERCD : secondary FHS return code
Example
Message
K015 Formatting error FH01 080C - input please
means that the format is not available (see also sample dump "Sample dump K326"). In this way, an MSGTAC service which is intended to react to a formatting error can access the secondary return code simply and conveniently.
Abnormal termination of a service
If a dialog service is terminated abnormally, openUTM issues message K017. If an asynchronous service is terminated abnormally, it issues message K055.
These messages contain return codes that indicate the cause of the error:
K017 Service &TCVG terminated by UTM (&RCCC/&RCDC &RCF2A) - input pleaseThe entries in the message have the following meanings:
&TCVG : TAC with which the service was started&RCCC : KDCS return code in the KCRCCC field&RCDC : internal return code in the KCRCDC field&RCF2A : secondary FHS return codeK055 Asynchronous service &ATAC1 terminated by UTM; KCRCCC= &RCCC ; KCRCDC=&RCDC ; USER= &USER ; LTERM= <RMThe entries in the message have the following meanings:
&ATAC1 : TAC with which the asynchronous service was started &RCCC : KDCS return code in the KCRCCC field &RCDC : internal return code in the KCRCDC field &USER : user ID that created the asynchronous Service <RM : LTERM partner that generated the asynchronous service
Errors in the INPUT exit
When there are errors in the INPUT exit, openUTM generally issues message K098 to the terminal. You will find an explanation of the error codes contained in K098 in section "Messages K071 - K101".
STXIT events
When STXIT events occur, openUTM issues messages K102 and K103 and terminates the service abnormally. The messages are described in section "Messages K071 - K101".
- For a better diagnosis of STXIT events an extended STXIT logging can be activated via the administration interface (KDCDIAG) or via start parameter STXIT-LOG.