Learn it on Mainframe Path. Do it with MainframeKit.Learn on Mainframe Path ▸
MainframeKit

S737

Error at end of volume or when taking extra spaceSYSTEM ABEND

An error occurred when the system moved to the next volume or tried to get extra disk space for a data set. Message IEC027I gives the return code.

MOST LIKELY

Return code 04 or 40: an I/O error reading the format-1 DSCB, or the DSCB was not found where expected, often a wrong data set name or volume on the DD.

FIRST CHECK

Find message IEC027I in the job log and note the return code first.

TRY IT ▸

Block size and space calculator

What it means

A 737 abend is reported with message IEC027I. It means a problem during end-of-volume (EOV) processing, or while the system was allocating a secondary space amount asked for on the SPACE parameter of a DD statement.

The task ends unless a DCB ABEND exit routine chooses to ignore the error. In that case the system tries to close the DCB and hands control back to the program. The return code in IEC027I tells you the real cause.

Typical causes

  • Return code 04 or 40: an I/O error reading the format-1 DSCB, or the DSCB was not found where expected, often a wrong data set name or volume on the DD.
  • Return codes 08, 0C, 10, 14 and 1C: I/O errors on a disk volume label, a DSCB or a file mark, which can point to a faulty volume or device.
  • Return code 24: BLDL could not find a member name while looking up a concatenated member.
  • Return code 28: a subsystem interface (IEFSSREQ) error, where JES3 hit a problem it could not process.
  • Return code 2C: FEOV could not write a file mark because the DCB disk address (DCBFDAD) pointed past the data set's last extent.
  • Return codes 44 and 45: a large-format sequential data set with more than 65535 tracks on a volume was accessed by EXCP, or by BSAM with NOTE or POINT, without BLOCKTOKENSIZE=LARGE on the DCBE (45 also needs BLOCKTOKENSIZE(REQUIRE) in IGDSMSxx).

How to fix it

  1. Find message IEC027I in the job log and note the return code first.
  2. For 04 or 40, check the DSNAME and VOLUME parameters on the DD statement.
  3. For other I/O errors, save the output, then rerun with a different volume or device, or change the UNIT parameter.
  4. For 28, tell your system programmer, because it is a subsystem interface problem.
  5. For 2C, make sure the program does not change the DCB disk address before issuing FEOV.
  6. For 44 or 45, point the DCB at a DCBE that specifies BLOCKTOKENSIZE=LARGE and update the program to handle large-format data sets; or, if the data set has 65535 or fewer tracks, open it as INPUT (BSAM or EXCP) or UPDAT (BSAM).

Example

Illustrative only; names and values are invented.

IEC027I 737-04,IFG0554A,ORDJOB03,STEP020,INDD01,0B34,VOL002,TEST.ORDERS.HISTORY
IEF450I ORDJOB03 STEP020 - ABEND=S737 U0000 REASON=00000004