ABEND Codes
Available Languages
Table Of Contents
ABEND Codes
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:
•
ABEND - Standard OS User ABENDs
•
•
This chapter includes these sections:
Includes ABEND codes 001 through F11.
Includes the return codes set by the FTP and FTP2 programs when they terminate.
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.
ABEND Codes
This section includes ABEND codes in alphanumeric order from 001 through F11.
IABEND 001 (U1)
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.
IABEND 002 (U2)
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.
IABEND 003 (U3)
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.
ABEND 008 (U8)
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.
ABEND 009 (U9)
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.
ABEND 00B (U11)
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.
ABEND 00E (U14)
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.
ABEND 012 (U18)
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.
ABEND 013 (U19)
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.
ABEND 014 (U20)
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.
ABEND 015 (U21)
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.
IABEND 016
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.
PABEND 080 (U128)
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.
PABEND 100 (U256)
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.
IABEND 101 (U257)
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.
IABEND 102 (U258)
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.
ABEND 104 (U260)
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.
PABEND 107 (U263)
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.
ABEND 108 (U264)
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.
ABEND 109 (U265)
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.
ABEND 10D (U269)
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.
IABEND 10E (U270)
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.
ABEND 110 (U272)
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.
ABEND 111 (U273)
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.
ABEND 112 (U274)
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.
ABEND 113 (U275)
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.
IABEND 116
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
ABEND 142 (U322)
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.
IABEND 16D (U365)
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.
PABEND 180 (U384)
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.
PABEND 200 (U512)
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.
PABEND 201 (UC9)
Explanation A ptask issued a PWAIT call while still having an active PFRR set.
Recommended Action Contact Customer Support.
ABEND 204 (U516)
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.
PABEND 207 (U519)
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.
ABEND 209 (U521)
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.
ABEND 20D (U525)
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.
ABEND 210 (U528)
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.
ABEND 211 (U529)
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.
ABEND 212 (U530)
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.
ABEND 213 (U531)
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.
IABEND 216
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
IABEND 26D (U621)
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.
PABEND 307 (U775)
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.
ABEND 309 (U777)
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.
ABEND 311 (U785)
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.
ABEND 313 (U787)
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.
ABEND 314 (U788)
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.
ABEND 315 (U789)
Explanation The PDRVER is called. The PDRVER P-service can perform these functions:
•
•
•
A PC routine fails to update the UCB and DEB control blocks. The calling PTASK ABENDs.
Recommended Action Save all output from the Cisco IOS for S/390 job. Contact Customer Support.
IABEND 316
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.
IABEND 36D (U877)
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.
ABEND 3E8 (U1000)
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.
ABEND 3F2 (U1010)
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.
PABEND 400 (U1024)
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.
ABEND 403 (U1027)
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.
ABEND 404 (U1028)
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.
ABEND 405 (U1029)
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.
IABEND 406 (U1030)
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.
IABEND 411 (U1041)
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.
IABEND 416
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.
ABEND 444 (U1092)
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.
ABEND 44C (U1100)
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.
ABEND 456 (U1110)
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.
ABEND 457 (U1111)
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 458 (U1112)
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 459 (U1113)
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 45A (U1114)
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 4B0-4D8 (U1200-1240)
Explanation ABEND codes in the range 1200 to 1240 are issued by the SAS/C runtime routines. This table provides a brief summary:
Recommended Action Refer to your SAS/C Documentation for further information or call Customer Support.
ABEND 4E2 (U1250)
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.
IABEND 511 (U1297)
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.
ABEND 51E (U1310)
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.
ABEND 582 (U1410)
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.
ABEND 706 (U1798)
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.
ABEND 7CF (U1999)
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.
ABEND 7D0 (U2000)
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.
ABEND 7D3 (U2003)
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.
ABEND 7D7 (U2007)
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.
ABEND 7DD (U2013)
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.
ABEND 7E2 (U2018)
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.
ABEND 7EE (U2030)
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.
ABEND 7EF (U2031)
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.
ABEND 800 (U2048)
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.
ABEND 834 (U2100)
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.
ABEND 837 (U2103)
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.
ABEND 83B (U2107)
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.
ABEND 846 (U2118)
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.
ABEND 852 (U2130)
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.
ABEND 853 (U2131)
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.
ABEND 8AA (U2218)
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.
ABEND 8B7 (U2231)
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.
ABEND 906 (U2310)
Explanation A module load use count overflows.
Recommended Action Determine if module was created correctly.
ABEND 90E (U2318)
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.
ABEND 91B (U2331)
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.
ABEND 972 (U2418)
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.
ABEND 9D6 (U2518)
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.
ABEND A3A (U2618)
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.
ABEND A9E (U2718)
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.
ABEND B02 (U2818)
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.
ABEND B0F (U2831)
Explanation The commutator encounters a stack overflow.
Recommended Action Contact Customer Support.
ABEND B66 (U2918)
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.
AABEND BB7 (U2999)
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.
ABEND C06 (U3078)
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.
ABEND C64 (U3172)
Explanation The driver issues this user ABEND under a variety of severe error conditions. This table lists the reason codes and descriptions:
Recommended Action Collect all job output, including dumps, and contact Customer Support.
ABEND D06 (U3334)
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.
ABEND E04 (U3588)
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.
ABEND E06 (U3590)
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.
ABEND E07 (U3591)
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.
ABEND E0D (U3597)
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.
ABEND E10 (U3600)
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.
ABEND E11 (U3601)
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.
ABEND F06 (U3846)
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.
ABEND F10 (U3856)
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.
ABEND F11 (U3857)
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.
FTP Return Codes
Programs FTP and FTP2 can terminate and set these different return codes:
Table 1-2 Return Codes That Can Be Terminated and Set by FTP and FTP2
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)