27 CODES
S0C1SYSTEM ABENDOperation exceptionThe processor tried to run bytes that are not a valid instruction, almost always because control jumped to the wrong place.S0C2SYSTEM ABENDPrivileged-operation exceptionA program running in problem state tried to run a privileged instruction it is not allowed to use.S0C4SYSTEM ABENDProtection exceptionThe program used a storage address it is not allowed to use, or one that is not mapped in the address space.S0C5SYSTEM ABENDAddressing exceptionAn instruction referred to an address that does not exist in the storage available to the system.S0C6SYSTEM ABENDSpecification exceptionAn instruction was used in a way the architecture does not allow, such as a wrongly aligned operand or address.S0C7SYSTEM ABENDData exceptionA decimal instruction hit a field that is not a valid packed or zoned number.S0C9SYSTEM ABENDFixed-point divide exceptionA binary (fixed-point) divide failed, usually because the divisor was zero.S0CASYSTEM ABENDDecimal-overflow exceptionA decimal result was too large for its target field and the program was set to treat that as an error.S0CBSYSTEM ABENDDecimal-divide exceptionA packed-decimal divide failed, almost always because the divisor was zero.S001SYSTEM ABENDI/O error (IEC020I)A sequential or other non-VSAM file hit an I/O error or a record-attribute problem, and the program had no way to handle it.S013SYSTEM ABENDData set OPEN failed (IEC141I)A data set could not be opened, usually because its attributes conflict with the program or JCL, or a member does not exist.S106SYSTEM ABENDProgram fetch errorThe system found the program but could not bring it into storage, because of lack of storage, a damaged module or an I/O error.S122SYSTEM ABENDOperator cancel with dumpThe job was cancelled by the operator or an authorised user, and a dump was requested.S213SYSTEM ABENDOPEN error on a DASD data set (IEC143I)OPEN failed for a data set on disk.S222SYSTEM ABENDOperator cancelThe job was cancelled by an operator or an authorised user, without a dump.S322SYSTEM ABENDCPU time limit exceededThe job or step used more processor (CPU) time than it was allowed.S413SYSTEM ABENDOPEN error on tape or DASD volume (IEC145I)OPEN failed for a tape or disk data set, often because the volume could not be mounted or no volume serial was given.S522SYSTEM ABENDWait time limit exceededEvery task in the step stayed in a wait longer than the site's continuous wait limit (JWT).S806SYSTEM ABENDModule not foundz/OS could not find the program to run or load in any library the step searched.S80ASYSTEM ABENDNot enough virtual storage (R-form GETMAIN/FREEMAIN)A storage request through an R-form GETMAIN or FREEMAIN could not be met because the area ran out of virtual storage.S878SYSTEM ABENDNot enough virtual storageA GETMAIN or STORAGE request failed because there was not enough virtual storage in the area requested, usually the job's private region.S913SYSTEM ABENDSecurity authorization failure on OPENThe job was not authorized to open a data set in the way it asked.SA22SYSTEM ABENDJob ended by FORCE commandThe operator used the FORCE command to end the job's address space, usually after a normal CANCEL failed.SB37SYSTEM ABENDOut of space (end of volume)An output data set needed more space and the system could not give it any more on the volume.SD37SYSTEM ABENDOut of space, no secondary allocationAn output data set filled its primary space and no secondary space was requested, so it could not grow.SE37SYSTEM ABENDOut of space on all volumesAn output data set ran out of space on every volume it could use, or a PDS hit its space or extent limit.U4038LANGUAGE ENVIRONMENT USER ABENDUnhandled condition, run unit endedLanguage Environment ended the program after an unhandled run-time error.