S813 Abend

The error occurred during processing of an OPEN macro instruction for a data set on magnetic tape.

-- possible cause --

  • Wrong DSNAME or volume serial - JCL disagrees with label
  • Incorrect record format or block size
  • The requested drive was not switched to this machine

Check out IEC149I message for more details

View all Abend Codes

S822 Abend

During initialization of a job, the initiator could not obtain a region required to run the step.

Check out IEF186I or IEF085I message for more details

View all Abend Codes

S837 Abend

The error occurred at an end-of-volume for a sequential data set.

Check out IEC028I message for more details

Reason codeExplanation
04

The unit is not capable of handling the requested density.

08

The volume serial number was not found in the JFCB.

0C

Another data set on the volume was in use.

10

The device does not support the selected recording mode.

14

The tape volume does not conform to the single recording mode rules. for input, the violation occurred when the tape was written when the rules could not be enforced. for output, the abend prevents any violation from happening.

View all Abend Codes

S878 Abend

The error occurred when the system was trying to do one of the following:

  • Satisfy a request made through the STORAGE macro
  • Process an RU or VRU form of the GETMAIN macro
  • Process an RU form of the FREEMAIN macro

Check out IEA705I message for more details

A reason code in the SDWACRC field of the system diagnostic work area (SDWA) explains the error:

Reason codeExplanation
04

There is not enough virtual system queue area (SQA) storage available to satisfy the request.

08

There is not enough virtual common service area (CSA) storage available to satisfy the request.

0C

There is not enough virtual local system queue area (LSQA) storage available to satisfy the request.

10

There is not enough virtual private area storage available to satisfy the request. This is due to one of the following:

  • A program is requesting virtual storage, but not subsequently freeing the storage.
  • The region size specified is too small
  • An installation exit is requesting virtual storage from a V=R region before initialization of the region has completed.
14

A negative amount of storage was specified on a GETMAIN macro.

18

A negative amount of storage was specified on the FREEMAIN or STORAGE macro.

1C

During request processing, the system tried to get LSQA virtual storage for virtual storage management’s (VSM) cell pool. There was not enough LSQA virtual storage available.

20

There is not enough virtual storage in the LSQA to build a new address queue anchor table (AQAT) stack.

24

A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword specified failed for one of the following reasons:

  • Part of the requested area was already allocated.
  • Storage was already allocated in the same page as this request, but one of the following characteristics of the storage was different:1.The Subpool 2.The Key 3.Central storage backing
28

A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword specified failed because part of the requested area exceeds the bounds of the region.

View all Abend Codes

S905 Abend

An error occurred when the system tried to process an EC, EU, LC, LU, VC, or VU form of the FREEMAIN macro.

A reason code in the SDWACRC field of the system diagnostic work area (SDWA) explains the error:

Check out IEA705I message for more details

Reason codeExplanation
04

The virtual storage area that the FREEMAIN macro tried to release is not on a double word boundary.

View all Abend Codes
suggestion / complaint / feedback Web Statistics