|
|
This chapter lists ABEND codes that can be caused by Cisco IOS for S/390. These types of ABENDs can take place in Cisco IOS for S/390:
This chapter includes these sections:
In this chapter, ABENDs are identified with the ABEND number in hexadecimal followed by a Uxxx number, where xxx is the OS User ABEND code in decimal.
This section includes ABEND codes in alphanumeric order from 001 through F11.
Explanation The commutator is validating an IECB or ILIST but the IECB or ILIST is invalid.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The commutator is validating an ECB for use by the PPOST facility but finds the ECB is not valid, usually not fullword aligned. This ABEND happens through a program exception.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The commutator's I/O services routine was called with an invalid entry code.
Recommended Action Collect all job output from the Cisco IOS for S/390 job including maps and dumps, and contact Customer Support.
Explanation The PATTACH P-service is called with a bad parameter list or PTA address. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support. If you are writing applications using P-services, check your PATTACH parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PSTATUS P-service is called with an invalid entry code in register R0. The entry code is larger than the maximum allowable entry code. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PSTATUS calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PSNAP P-service is called with a bad parameter list. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PSNAP parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PDEBUG P-service is called with a bad parameter list. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PDEBUG parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PSTOP P-service is called with a bad parameter list. The service code in register R0 contains a number greater than 2. The only valid register 0 values are 0, 1, and 2. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PSTOP parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation PATTN, the install/remove IOS attention handler service, is called with an invalid DCB address or unopened DCB. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PATTN parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation PDMIH P-service to disable the missing attention handler is called with an invalid DCB address or unopened DCB. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PDMIH parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PDRVER P-service is called with an invalid DCB address or unopened DCB. The PDRVER P-service can do these functions:
The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PDRVER parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PPDSENQ P-service was called with a bad parameter list address. This may generate unexpected program checks. The calling ptask ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PPDSENQ parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The stdin and stdout connections will not open. The VTAM connection cannot be opened for some reason. A PABEND of x'80' ABENDs the PTASK.
Recommended Action Check to make sure the Cisco IOS for S/390 VTAM APPLs have been defined to VTAM. Check to make sure you are using the correct ACBNAME parameter in the APPCFGxx member.
Explanation The stderr connection will not open. Cisco IOS for S/390 error log cannot be written. A PABEND of x'100' ABENDs the PTASK.
Recommended Action Make sure the Cisco IOS for S/390 job has all its WTOLOGxx DD statements.
Explanation The commutator is validating an ECB or ECBLIST but the ECB or ELIST is invalid.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The commutator finds that the PSTA INDEX or PTA address for an ECB is not valid. This ABEND happens through a program exception.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A CALL is made to PCOREF to "free" PCORE storage, but the storage is not owned by PRSMGR.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PTASK calls the PACCESS P-service with a bad parameter list. The PTASK ABENDs with an X'107'.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PATTACH TYPE=ADD P-service is called with a PTA address of the parent PTASK. The PTA address of the parent PTASK is actually a descendant of the PTASK that issued the PATTACH TYPE=ADD. This is a logic error by the programmer (for if the parent PTASK ends, there is no PTASK to post). The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check your logic. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PSTATUS NEXT P-service is called out of sequence. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PSTATUS calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PRSMGR DELETE P-service call is made. Module PRSMGRD is called to delete an RE# element. The RE# address is not found. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PRSMGR calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PDEBUG P-service is called with a bad request type in the parameter list. The request type could either be an undefined type or a request to delete or replace a PDEBUG intercept that does not exist. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PDEBUG calls for a correct request type in the PDEBUG parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A call is made to EXTGIVE to "give" an EXCH window, but the PTA address is invalid. This ABEND is a result of a PEXCH P-service call. The PEXCH P-service call is valid only in an MVT environment. Application developers should not be using the PEXCH P-service. This ABEND should never occur.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation ACDYNAL is called to open or close a list of ACBs or DCBs but lists are not allowed.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation PSTOP is called for set application stop ECB address. The ECB address is invalid. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support. If you are writing applications using P-services, check the ECB address of the calling PSTOP parameter list.
Explanation PATTN, the install/remove IOS attention handler service, is called. The CVTJESCT in the CVT does not point to a JES2 or JES3. Cisco IOS for S/390 cannot find an unused attention index. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The PPDSENQ P-service was called to enqueue a resource; however, after completion of the process the dequeue failed and the resource remained enqueued. The calling ptask ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PPDSENQ parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support
Explanation A PTASK has consumed more than the maximum allowable CPU time. Cisco IOS for S/390 believes the PTASK is looping. Cisco IOS for S/390 terminates the PTASK and dumps related storage to the PTASK.
Recommended Action Save all output from the Cisco IOS for S/390 job. A dump of a related PTASK before the 142 PTASK ABEND may be related to this looping problem. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation ACHSM is called to recall a migrated data set, but the PDYNAL parameter list is invalid.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-services. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The TCP connection will not open. ATOPN has failed for this process. A PABEND of x'180' ABENDs the PTASK.
Recommended Action Check that the other host Cisco IOS for S/390 is trying to connect to is up on the network. If the remote host is up, save all output from the job. Contact Customer Support.
Explanation The program requests an amount of storage through PCORE. The storage is not available. The PTASK decides to ABEND rather than wait. The PTASK ABENDs with an x'200'.
Recommended Action Retry the task. Save all output from the job.
Explanation A ptask issued a PWAIT call while still having an active PFRR set.
Recommended Action Contact Customer Support.
Explanation A call is made to PC$GIVE to "give" PCORE storage, but the PTA is invalid.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PTASK calls the PACCESS TYPE=LOGOFF P-service trying to logoff, yet the PTASK is not logged on to Cisco IOS for S/390. A PABEND of x'207' occurs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation During processing of a PSTATUS P-service, an invalid PTA address is returned from ICKPTA. The PSTATUS P-service cannot continue. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PSTATUS calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation Either the PRSMGR NEXT or PRSMGR DLTCUR P-service is called in an invalid sequence. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PRSMGR calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A call is made to EX$FND to find a RE resource for a window, but the window ID is not known. This ABEND is a result of a PEXCH P-service call. The PEXCH P-service call is valid only in an MVT environment. Application developers should not be using the PEXCH P-service. This ABEND should never occur.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation ACDYNAL is called with an invalid parameter list.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PSTOP P-service is processing a PSTOP exit request when a logic error is uncovered that prevents further processing. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation PATTN, the install/remove IOS attention handler service, is called. The attention index that Cisco IOS for S/390 was going to use is reserved or invalid. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The PPDSENQ P-service was called to enqueue a resource; however, after completion of the process the dequeue failed and the resource remained enqueued. The calling ptask ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PPDSENQ parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support
Explanation ACHSM is called to recall a migrated data set, but the conditional GETMAIN fails to obtain storage.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-services. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PTASK calls the PACCESS TYPE=LOGOFF P-service trying to logoff; the ACEE pointer is invalid or the logoff fails. A PABEND of x'307' occurs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation During processing of a PSTATUS STOP P-service, 250 related PTASKs are found. The maximum number of descendants that PSTATUS STOP processes is 249. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PSTATUS calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation ACDYNAL is attempting to find a RE# resource element for an ACB or DCB but none is found.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation PATTN, the install/remove IOS attention handler service, is called. A PC call to update the UCB or ATTN fails. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation PDMIH, the disable/enable missing interrupt handler service, is called. A PC call to update the UCB fails. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The PDRVER is called. The PDRVER P-service can perform these functions:
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The PPDSENQ P-service was called to enqueue a resource, but the corresponding flag in the PPDSENQ parameter list had not been set up correctly. This is detected as a logic error. The calling ptask ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PPDSENQ parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation ACHSM is called to recall a migrated data set, but OS attach for the recall task fails.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Verify the recall task ACRECALL is link-edited within ACCOM. If the problem persists, contact Customer Support.
Explanation A PTASK tries to perform a P-service while on the BYPASS task. PTASKs can issue P-services only while on the commutator task. The PTASK is ABENDed with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PTASK calls program IQCELLG to allocate quick cell memory. Not enough memory exists for the request. A conditional GETMAIN is issued by Cisco IOS for S/390 for more storage. Less than 72 bytes of storage are returned from the GETMAIN. Cisco IOS for S/390 is out of memory for the PTASK. No storage is available from quick cell storage. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Examine the storage in the dump for a proliferation of any type of storage throughout memory. Check the WTO and job logs for any related messages. Raise the region parameter on the Cisco IOS for S/390 start-up JCL step. If the problem persists, contact Customer Support.
Explanation The input initialization parameters are invalid. The program cannot execute any further. An ABEND of x'400' causes the PTASK to ABEND.
Recommended Action Check APPCFGxx input. Contact Customer Support.
Explanation During startup for the TCP base product, an attempt was made to perform a SETLOCK OBTAIN for the LOCAL lock, but failed. Startup for the TCP base product terminates.
Recommended Action Save the output of the TCP base product job. Contact Customer Support.
Explanation During startup for the TCP base product, an attempt was made to GETMAIN SUBPOOL 241 Key 0 CSA storage, but failed. Startup for the TCP base product is then terminated.
Recommended Action Save the output of the TCP base product job. Contact Customer Support.
Explanation During startup for the TCP base product, an attempt was made to perform a SETLOCK RELEASE for the LOCAL lock, but failed. Startup for the TCP base product terminates.
Recommended Action Save the output of the TCP base product job. Contact Customer Support.
Explanation ACLOAD attempted to load a module but failed due to insufficient virtual storage.
Recommended Action Increase the virtual storage available to the Cisco IOS for S/390 address space and restart Cisco IOS for S/390.
Explanation ACDYNAL is called to allocate a migrated data set, but the PDYNAL parameter list is invalid.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-services. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The P-service FREE RESOURCE routine failed to dequeue an enqueued resource. The calling ptask ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. If you are writing applications using P-services, check your PPDSENQ parameter list. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation Program SPOOL#4 found an error condition that normally would cause SPOOL#4 to terminate without a dump; however ACTEST command SPOOLDMP ON was entered. When SPOOLDMP is ON, program SPOOL#4 terminates ptask SPOOL#4 and dumps under certain error conditions (having to do with open, close, dynamic allocation, etc.).
Recommended Action SPOOLDMP ON generally should only be used to debug other problems within SPOOL#4 at the direction of Customer Support.
Explanation A PTASK tries to perform a P-service with an invalid PTA address in register R11. By convention, R11 should contain the caller's PTA address. The PTASK ABENDs with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation A PTASK calls program IQCELLG to allocate quick cell memory. The storage amount requested is either greater than x'FFFFFF' or zero. A bad parameter has been passed. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The quick cell get logic detected that the next pointer in the chain of free quick cells was corrupted. An attempt is made to salvage the chain, then the currently executing PTASK abends.
Recommended Action This indicates an internal error within Cisco IOS for S/390 and requires the SVC dump output to diagnose.
Explanation The quick cell get logic detected that the next pointer in the chain of free quick cells was corrupted. An attempt is made to salvage the chain, then the currently executing PTASK abends.
Recommended Action This indicates an internal error within Cisco IOS for S/390 and requires the SVC dump output to diagnose.
Explanation The quick cell get logic detected that the next pointer in the chain of free quick cells was corrupted. An attempt is made to salvage the chain, then the currently executing PTASK abends.
Recommended Action This indicates an internal error within Cisco IOS for S/390 and requires the SVC dump output to diagnose.
Explanation The quick cell get logic detected that the next pointer in the chain of free quick cells was corrupted. An attempt is made to salvage the chain, then the currently executing PTASK abends.
Recommended Action This indicates an internal error within Cisco IOS for S/390 and requires the SVC dump output to diagnose.
ABEND codes in the range 1200 to 1240 are issued by the SAS/C runtime routines. This table provides a brief summary:
| Code | Description |
|---|---|
| 1200 | Corruption of auto storage control blocks while DSA was being freed |
| 1201 | Corruption of auto storage control blocks during new DSA allocation |
| 1202 | During program termination, program stored past end of automatic storage stack |
| 1203 | Corruption of auto storage control blocks while freeing automatic storage |
| 1204 | Target of a longjmp cannot be found |
| 1205 | Corruption of heap storage control blocks during calloc/malloc |
| 1206 | Corruption of heap storage control blocks when calloc/malloc tried to reuse portion of heap |
| 1207 | Corruption of heap storage control blocks detected by free |
| 1208 | Free detected invalid pointer to a block |
| 1209 | Corruption of head storage control blocks during program termination |
| 1210 | SIGABRT is raised and default handling in effect |
| 1211 | Invalid argument to unloadm |
| 1212 | Required transient runtime functions cannot be loaded |
| 1213 | Subordinate C load module is called directly |
| 1214 | More than one recursive error occurred during diagnostic message processing |
| 1215 | (CMS) tried to delete storage occupied by dynamically loaded module |
| 1216 | (CMS) invalid library control block during call to unloadm |
| 1217 | (CMS) invalid library control block during call to loadm |
| 1218 | (CMS) error trying to delete a buffer during dynamic loading |
| 1219 | Error in interface between debugger and library |
| 1220 | Abort debugger command executed |
| 1221 | (CMS) CP detected error loading a library segment |
| 1222 | Library framework manager detected an error |
| 1223 | Indicates system problem in TSO SUBCOM interface |
| 1224 | longjmp or exit attempted to terminate a non-C routine |
| 1225 | SIGALARM or SIGIUCV lacks a handler |
| 1226 | Full-Screen Support library detected an internal error |
| 1227 | Library error occurred, terminating a process |
| 1228 | Insufficient storage to extend the internal queue of IUCV messages |
| 1233 | Internal error in inter-language communication support routines |
| 1234 | Call was made from C program to another high-level language but framework not created |
| 1235 | Inter-language communication feature usage error |
| 1240 | Unexpected program check during library ABEND analysis |
Recommended Action Refer to your SAS/C Documentation for further information or call Customer Support.
Explanation A PTASK calls program IQCELLF to release quick cell memory. The storage address is not on the list of allocated quick cell pools. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation ACDYNAL is called to allocate a migrated data set, but ACQCELL get fails to obtain storage for the HSM recall.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Check the region size of Cisco IOS for S/390. If the problem persists, contact Customer Support.
Explanation A PTASK calls program IQCELLF to release quick cell memory. The storage amount to be released does not end on a double word boundary. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation PTASK calls program IQCELLF to release quick cell memory. The storage amount to be released is either larger than x'FFFFFF' or zero. Bad parameters have been passed to IQCELLF. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation ACLOAD attempts to load a module that is identified as non-executable.
Recommended Action Determine the problem with the module and restart Cisco IOS for S/390.
Explanation A PTASK issues the XPOST P-service and not enough storage is available from IQCELLG to allocate an XAE for the service. Cisco IOS for S/390 is out of storage. The PTASK terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check storage for a proliferation of one type of storage to see if there might be some kind of storage allocation loop. Check the WTO and job logs for any related messages. If the problem persists, contact Customer Support.
Explanation The commutator is attempting to build a list of ECBs from PTA ECB lists, but not enough stack storage is available to hold the entire list.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation Subroutine IERRWAIT detects all PTASKs in an error wait condition. No work can be performed. Cisco IOS for S/390 terminates.
Recommended Action Save all output from the Cisco IOS for S/390 job. U2003 ABENDs indicate some function within Cisco IOS for S/390 has repeatedly failed. Check the Cisco IOS for S/390 WTO and job logs for related messages. Contact Customer Support.
Explanation A PTASK is attempting to call the ACSECPC routine when it discovers that the ACSSCB pointer is zero. The ACSSCB pointer has been overwritten. DORACFPC subroutine discovers this problem. Cisco IOS for S/390 can no longer provide an external security interface. An ABEND of x'7D7' occurs. . Cisco IOS for S/390 terminates from this ABEND.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation Routine IQCELLG is called to allocate a RE#. No storage is available from quick cell storage. The PRSMGR routine cannot continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If there is a proliferation of the same kind of storage, a PTASK may be allocating storage in a loop.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again bring Cisco IOS for S/390 down. Raise the region size on the Cisco IOS for S/390 job. Start up Cisco IOS for S/390. Retry the operation again. If the error recurs, contact Customer Support.
Explanation Two conditions can cause a U2018 to occur: ACDEBUG's SPIE exit is called with an invalid PTA address or the Bypass task ABENDs. Cisco IOS for S/390 terminates with a dump.
Recommended Action Restart the Cisco IOS for S/390 job. Save all output from the Cisco IOS for S/390 job. Check Cisco IOS for S/390 WTO and job logs for related information. Contact Customer Support.
Explanation Not enough initial core is available to build the Cisco IOS for S/390 control blocks. Cisco IOS for S/390 terminates with a dump.
Recommended Action Increase the REGION parameter on the Cisco IOS for S/390 job step. Restart the Cisco IOS for S/390 job. If the problem persists, contact Customer Support.
Explanation Cisco IOS for S/390 cannot successfully open the DCB for either the ACSNAP or the ACLOG DD statement. The ACLOG DD is the ICT logging file. The ACSNAP DD contains formatted dumps of any ABENDing PTASKs. Cisco IOS for S/390 cannot continue and terminates with a dump.
Recommended Action Check the Cisco IOS for S/390 start-up JCL for ACSNAP and ACLOG DD statements.
Explanation A serious error occurred (an ABEND of x'800'), causing Cisco IOS for S/390 to terminate. Cisco IOS for S/390 control blocks have been corrupted.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The commutator is attempting to ACALL the BYPASS tasks but is unsuccessful because the current TCB is not the BYPASS task TCB.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation During termination processing, subroutine TSK$DEL discovers PTASKs in an error wait condition. Cisco IOS for S/390 terminates and a dump is taken.
Recommended Action Save all output from the Cisco IOS for S/390 job. U2103 ABENDs indicate some function within Cisco IOS for S/390 has failed. Check the Cisco IOS for S/390 WTO and job logs for related messages.
Explanation A PTASK attempting to call the ACSECPC routine discovers that the ACSSCB pointer is either invalid or has been violated by another program. DORACFPC subroutine discovered this problem. Cisco IOS for S/390 can no longer provide an external security interface. An ABEND of x'83B' occurs. Cisco IOS for S/390 terminates from this ABEND.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation No RE# element can be allocated in ACDEBUG's STAE exit. No storage is available from quick cell storage. The STAE exit cannot continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If there is a proliferation of the same kind of storage, a PTASK may be allocating storage in a loop.
Retry the operation first on the current version of Cisco IOS for S/390. If it fails again, bring Cisco IOS for S/390 down and increase the region size on the Cisco IOS for S/390 job. Restart Cisco IOS for S/390 and retry the operation. If the error recurs, contact Customer Support.
Explanation The save area passed to module ACCONFG is not the first save area. ACCONFG is an initialization module. No PTASK should ever call module ACCONFG. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If you are using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
If the problem occurs after start-up, submit the Cisco IOS for S/390 job. Check the logs for related messages. If the problem persists, contact Customer Support.
Explanation Initialization and termination module ACCALL tries to allocate quick cell storage from IQCELLG. No storage is available from quick cell storage. Cisco IOS for S/390 terminates with a dump.
Recommended Action Restart the Cisco IOS for S/390 job. Save all output from the Cisco IOS for S/390 job. Examine the storage in the dump for a proliferation of any type of storage throughout memory. Check the WTO and job logs for any related messages. If the failure occurs during Cisco IOS for S/390 initialization, raise the region parameter on the Cisco IOS for S/390 start-up JCL step. If the problem persists, contact Customer Support.
Explanation No DB#A element can be allocated in GETPDA for ACDEBUG's STAE, SPIE PABEND, or DB$FREE routines. No storage is available from quick cell storage. The exit cannot continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Restart the Cisco IOS for S/390 job. Save all output from the Cisco IOS for S/390 job. Examine the storage in the dump for a proliferation of any type of storage throughout memory. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation Initialization module ACCALL tries to IDENTIFY the IOSSUB routine but fails. Cisco IOS for S/390 terminates with a dump.
Recommended Action Restart the Cisco IOS for S/390 job. Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the problem persists, contact Customer Support.
Explanation A module load use count overflows.
Recommended Action Determine if module was created correctly.
Explanation A recursive call to Cisco IOS for S/390 SPIE exit is made. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the SYSABEND DD for any related dump. Check the WTO and job logs for any related messages.Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation Initialization module ACCALL issues an ATTACH for the commutator task. The ATTACH fails. Cisco IOS for S/390 cannot continue without a commutator task. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Examine the dump. Restart the Cisco IOS for S/390 job. If the problem persists, contact Customer Support.
Explanation A recursive call to Cisco IOS for S/390 STAE exit is made. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation Cisco IOS for S/390 is looping. No PTASK seems to be active on the commutator. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation On return from PDEBUG's exception exit, the RE# element cannot be located. Processing cannot continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation Cisco IOS for S/390 STAE initialization call fails. Processing can no longer continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages.Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation A program exception occurs on the commutator task. Cisco IOS for S/390 finds that its IRB chain has been corrupted. Processing can no longer continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. The previous ABEND may have corrupted Cisco IOS for S/390 IRB chain. Restart the Cisco IOS for S/390 job. Contact Customer Support.
Explanation The commutator encounters a stack overflow.
Recommended Action Contact Customer Support.
Explanation A critical Cisco IOS for S/390 PTASK ABENDs. Processing can no longer continue. Cisco IOS for S/390 terminates with a dump.
Recommended Action Restart the Cisco IOS for S/390 job. Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation An ACTEST user issues the ABEND command. Cisco IOS for S/390 terminates with a dump.
Recommended Action None, if the ACTEST user intended to terminate Cisco IOS for S/390. If ACTEST is not protected by command security and a curious user entered the command (and terminated Cisco IOS for S/390), the system programmer responsible for Cisco IOS for S/390 might consider implementing command security for ACTEST.
Explanation ACLOAD attempts to load a module but the module is found to contain invalid attributes.
Recommended Action The module must be generated without an overlay structure or similar attribute.
The driver issues this user ABEND under a variety of severe error conditions. This table lists the reason codes and descriptions:
| Code | Description |
|---|---|
| 1 | The DIE exit was unable to translate the real CCW address to a virtual CCW address, either because the end of the LNIO chain was reached or the command chaining bit in LNIOCCW1 was not set. |
| 2 | During DIE processing, an LRA (load real address) instruction returned a non-zero return code, indicating that the page was not page-fixed. This can be caused by either the page being page-freed prematurely or a logic error in this program not using the correct value with the LRA. |
| 3 | After determining which LNIO was the last to complete, a check indicated that there was another LNIO on the chain. This indicates the channel program was not built correctly. |
| 4 | An attempt was made to enqueue an I/O request on the ready queue, but the test and set (TS) of LNIOFLG2 indicated that this I/O was already queued. |
| 5 | During I/O processing, an LRA (load real address) instruction returned a non-zero return code indicating that the storage was not page-fixed. |
| 6 | An attempt was made to enqueue an I/O request on the free queue, but the test and set (TS) of LNIOFLG2 indicated that this I/O was already queued. |
| 7 | An attempt was made to enqueue an I/O request on an output queue, but the test and set (TS) of LNIOFLG2 indicated that this I/O was already queued. |
| 8 | An attempt was made to enqueue an I/O request on a free queue, but the test and set (TS) of LNIOFLG2 indicated that this I/O was already queued. |
| 9 | LIOREAD was called when another read was already active. |
| 10 | After successfully dynamically allocating an I/O device, the TIOT could not be located for it. |
| 11 | During driver initialization, an LRA (load real address) instruction returned a non-zero return code indicating that the storage was not page-fixed. |
| 12 | Termination was requested for a specific LNI but the LCSDEV resource element could not be located. |
| 13 | Termination was requested for a specific LNI but the LNI anchor block was not found in the table of active LNIs. |
| 14 | A loop was detected in the LNIO output chain. |
Recommended Action Collect all job output, including dumps, and contact Customer Support.
Explanation A DLBL I/O error is encountered while attempting to load a module.
Recommended Action Examine the module to determine possible cause of problem or recreate module and restart Cisco IOS for S/390.
Explanation The parameter list passed to PCOREG or PCOREF is invalid. Probable causes include bad storage length or storage address or an invalid PCORE entry code.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation While attempting to load a module, the module use count and chain of LD#M blocks do not agree.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
Explanation A PTASK calls the PACCESS P-service with an invalid PENTRY code. An ABEND of x'E07' occurs. Cisco IOS for S/390 terminates from this ABEND.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The PRSMGR P-service is called with an invalid entry code in register R0. The entry code is larger than the maximum allowable entry code. Register R3 in the dump should contain the entry code passed in R0 to PRSMGR
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for related messages. If you are writing applications using P-services, check the logic of your PRSMGR calls and parameter lists. If you are using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation The entry code parameter passed to PEXSRV is invalid. This ABEND is a result of a PEXCH P-service call. The PEXCH P-service call is valid only in an MVT environment. Application developers should not be using the PEXCH P-service. This ABEND should never occur.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation ACDYNAL is called with an invalid entry code parameter.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. If the user is using P-services to create an application, check the program logic of the failing PTASK. Check the parameter lists passed to the P-service. If the user is using the default Cisco IOS for S/390 applications, contact Customer Support.
Explanation While attempting to load a module, an error occurs causing entry into ACLOAD debug exit.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation A call to IQCELLG for cell storage to be used as a work area fails. This ABEND is a result of a PEXCH P-service call. The PEXCH P-service call is valid only in an MVT environment. Application developers should not be using the PEXCH P-service. This ABEND should never occur.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Contact Customer Support.
Explanation A call to ACDYNAL is made to perform a close but the close fails.
Recommended Action Save all output from the Cisco IOS for S/390 job. Check the WTO and job logs for any related messages. Contact Customer Support.
Programs FTP and FTP2 can terminate and set these different return codes:
| Code | Description |
|---|---|
| 0 | FTP successful |
| 8 | An error occurred in processing the FTP commands, a remote host disconnected, or a file transfer failed. Check the SYSPUT data output for the problem. |
| 16 | A file allocation error occurred. Check that the SYSGET and SYSPUT files are in the batch JCL. Also, check to make sure that the FIOS option was entered in the PARMS passed to FTP. When running FTP2 in batch, unless the NOA option is specified, a return code of 16 can be returned when there is no NETRC file. |
|
|