Mainframe Access' C language components are built with the SAS/C compiler and use the associated SAS/C run-time libraries during execution. Some software problems can be detected by the SAS/C run-time library routines. These SAS/C routines issue the following specific user abend codes to indicate the nature of the problem and create a storage dump. This list may not be complete; for a full up-to-date list of codes please see the SAS Web site http://www.sas.com. If you receive any of these abend codes contact our Product Support.
| User Abend Code | Description of Cause |
|---|---|
| 1200 | Storage corruption detected while freeing DSA. |
| 1201 | Storage corruption detected while allocating DSA. |
| 1202 | Storage corruption in the automatic storage stack. |
| 1203 | Storage corruption detected while freeing automatic storage at the end of program execution. |
| 1204 | Target of a longjmp cannot be found. |
| 1205 | Storage corruption detected in heap storage during execution of calloc/malloc. |
| 1206 | Storage corruption detected when attempting to reuse free heap storage. |
| 1207 | Storage corruption detected while releasing a tract of heap storage. |
| 1208 | Pointer to storage block to be freed is not valid. |
| 1209 | Storage corruption of heap storage control blocks is detected during program termination. |
| 1210 | The SIGABRT signal is raised and default handling is in effect. |
| 1211 | The argument to unloadm does not address a function in a module previously loaded by loadm. |
| 1212 | Required transient run-time functions cannot be loaded. Under z/OS, the transient library must have been installed into the system link list or be defined as part of STEPLIB or CTRANS. |
| 1213 | A subordinate C load module is abused by calling it directly (for example, via EXEC PGM=) as if it were a main program. |
| 1214 | More than one recursive error occurs during diagnostic message processing. This is probably a run-time library error. |
| 1215 | CMS: an error occurs while trying to delete the storage occupied by a dynamically loaded module during a call to unloadm. The most likely cause is a storage overlay. |
| 1216 | CMS: an invalid library control block is encountered during a call to unloadm. This is probably caused by a storage overlay. |
| 1217 | CMS: an invalid library control block is encountered during a call to loadm. This is probably caused by a storage overlay. |
| 1218 | CMS: an error occurs while trying to delete a buffer during dynamic loading. The most likely cause is a storage overlay. |
| 1219 | The interface between the debugger and the library detects an error in its own processing or in the debugger. |
| 1220 | The abort debugger command is executed, or multiple attention interrupts occur and the debugger is unable to respond normally due to a program loop or system slowdown. |
| 1221 | CMS: an error is detected by CP while loading a library segment. It is probably an indication of a CP system error. |
| 1222 | The library framework Access detects an error in its use. This is most likely a library error, but it can be caused by overlay of library control blocks. |
| 1223 | TSO: indicates a system problem in the TSO SUBCOM interface. This is most likely a library or TSO error. |
| 1224 | longjmp or exit attempts to terminate a non-C routine. |
| 1225 | There is no handler for an asynchronous signal, such as SIGALRM, for which the default action is termination. |
| 1226 | The Full-Screen Support Library detects an internal error. |
| 1227 | A library error occurs terminating a co-process. |
| 1228 | There is not enough storage available to extend the internal queue of IUCV or socket communication messages. The probable cause is that the number of incoming interrupts is greater than the program can handle. |
| 1229 | CICS: not enough storage available for an unconditional GETMAIN. |
| 1230 | A POSIX function cannot be executed because OpenEdition is not installed or active, but the function does not have any defined error conditions. |
| 1231 | No TWA is defined for a CICS Indep Application. |
| 1233 | An internal error occurred in the inter-language communication support routines. This is most likely a library error, but could be caused by an overlay of library control blocks. |
| 1234 | A call is made from a C program to a routine written in another high-level language or from a program in another high-level language to a C function, but the framework for the called language has not been created. |
| 1235 | An inter-language communication feature usage error. The error is explained by a preceding message. |
| 1239 | CICS: an unexpected internal error is encountered during abnormal termination processing. |
| 1240 | An unexpected program check occurs during library abend analysis. Possible storage overlay or a problem in the analysis routine. |