Session Monitor User-Abend Codes
The following table lists all Session Monitor mainframe user-abend codes in decimal and hexadecimal. It explains each code and the appropriate action to take for resolution.
Session Monitor User-Abend Codes
Dec | Hex | Explanation | User Response |
|---|---|---|---|
200 | C8 | Unknown VTAM request was made to the Session Monitor SCIP exit. | If the error persists, contact BMC Support for assistance. |
123 | 7B | Session Monitor cannot support your z/OS release. | For supported releases of z/OS, see Getting started. If you have recently installed a new version of z/OS, contact BMC Support for assistance. |
100 | 64 | During program execution, the corruption of a program save area was detected. | Contact BMC Support for assistance. |
345 | 159 | An unexpected error occurred while processing the attributes of a data set. | If the error persists, contact BMC Support for assistance. |
769 | 301 | During program execution, a stack underflow condition was detected, or an internal subroutine was not entered properly. | Contact BMC Support for assistance. |
770 | 302 | During program execution, a stack overflow condition was detected or an internal subroutine was not exited properly. | If the error persists, contact BMC Support for assistance. |
777 | 309 | The release of a user-generated default parameter table does not agree with the current Session Monitor release. | You must apply the values of the previous default table to the current version of Session Monitor. Do not copy the old table — it must be regenerated. Also, ensure that the correct table is being used. If you have further problems, contact BMC Support for assistance. |
817 | 331 | Session Monitor has detected a problem based on your module and its displacement. | Contact BMC Support for assistance. |
1009 | 3F1 | This is an unexpected return code from the VTAM CHECK macro. The VTAM subsystem may have terminated unexpectedly. | If the VTAM subsystem was still active at the time of the abend, report the problem to BMC Support. If the VTAM subsystem was not active, repeat the test while it is active. |
4094 | FFE | An unknown VTAM request was made to the Session Monitor SYNAD exit. This may be caused by the VTAM subsystem terminating unexpectedly. | If the VTAM subsystem was still active at the time of the abend, report the problem to BMC Support. If the VTAM subsystem was not active, repeat the test while it is active. |