When Mainframe Access detects a condition that prevents the program from continuing, it requests z/OS to begin abend processing for a user abend. Many of these conditions are detected by Mainframe Access initialization or by the item library format utility. z/OS reports user abends using a code consisting of the letter U identifying a user abend and four decimal digits, for example, U2111. The user abend codes that can be issued by Mainframe Access and recommended actions are listed in the following table.
| User Abend Code | Description of Cause | Recommended Action |
|---|---|---|
| 99 | Issued when a Data Set Services ISPI module cannot determine the invocation reason. | Contact our Product Support. |
| 801 | Processing to establish or remove a Mainframe Access ESTAEX error recovery routine has failed. | Contact our Product Support. |
| 996 | The MFA Server DSS Services component failed to initialize properly. This is a should not occur condition. | Contact our Product Support. |
| 997 | An Endevor error has occurred in the application server address space. Common causes include a general setup failure, MSGLOG allocation failure, or the Endevor C1DEFLTS module could not be found. Endevor requests cannot be processed. | Examine the joblog and syslog for system messages and server messages that can help identify the specific error.
Contact our Product Support if you are unable to resolve the problem |
| 998 | There is a difference between the Endevor support modules available to the MFA Server control region and the Endevor support modules available in the MFA Server application server region(s). Different versions of Endevor are being referenced by the regions. Endevor requests cannot be processed. | This is most likely caused by differences in the STEPLIB or JOBLIB concatenations in the JCL used to start the regions.
Contact our Product Support if you are unable to resolve the problem. |
| 999 | This abend code indicates that the Endevor support modules are not available to MFA Server. Endevor requests cannot be processed. | The Endevor AUTHLIB and CONLIB data sets must be included in the MFA started task JCL (for both the control region and the
application server regions) or these data sets must be available in the standard system LNKLST specifications.
Contact our Product Support if you are unable to resolve the problem. |
| 2100 | Processing to establish or remove a Mainframe Access ESTAEX error recovery routine has failed. | Contact our Product Support. |
| 3100 | Processing associated with Mainframe Access' dependent addresss space services has encountered a should not occur condition. | Contact our Product Support. |
| 3101 | Work order allocation for a dependent address space service has failed. This is a should not occur condition. | Contact our Product Support. |
| 3102 | Allocation for a dependent address space service program call block has failed. This is a should not occur condition. | Contact our Product Support. |
| 3103 | Work order queuing for a dependent address space service has failed. This is a should not occur condition. | Contact our Product Support. |