Messages K102 - K103

K102

Interrupt weight &CIW at program count &CPC &CDSPL. Instruction length code : &CILC program mask : &CPM condition code : &CCC AMODE : &CAMODE R0 &CR0 R1 &CR1 R2 &CR2 R3 &CR3 R4 &CR4 The messages K102 and K103 are output together (see explanation of the message K103).

K103

R5 &CR5 R6 &CR6 R7 &CR7 R8 &CR8 R9 &CR9 R10 &CR10 R11 &CR11 R12 &CR12 R13 &CR13 R14 &CR14 R15 &CR15 Outputs the context when an STXIT occurs (see also the table in the section "Message inserts"). Interrupt weight 48: If the STXIT event 48 occurs with the program KDCS + 8, this means that an address that cannot be accessed was specified for the KDCS parameter area when the KDCS interface was called. Action: Change the application program unit. Interrupt weight 90: If a termination attempt is made in a program unit (e.g. with the "exit (1)" statement in a C++ or C program), a number of runtime modules are called before openUTM receives control of the application program. For this reason, the most recently available register record is interpreted when the register record is displayed. You can then find the module responsible for termination via stack chaining if you register 13 points to a valid save area.