MainframeKit

S106

Program fetch errorSYSTEM ABEND

The system found the program but could not bring it into storage, because of lack of storage, a damaged module or an I/O error.

MOST LIKELY

Region too small to hold the module (0C with reason 14).

FIRST CHECK

Read the return and reason codes in the abend message.

TRY IT ▸

Block size and space calculator

What it means

Abend 106 means the system failed while fetching a requested program into virtual storage during LINK, LOAD, ATTACH or XCTL. Register 15 holds a return code that names the problem.

Key return codes: 0C means not enough storage (reason 14 means no storage for the module itself); 0D means the load module has an invalid record type; 0E means an address problem, and reason 20 often means another job changed the library's extents; 0F means an I/O error while reading the module.

Typical causes

  • Region too small to hold the module (0C with reason 14).
  • A library updated or compressed while the job was running (0E reason 20).
  • A damaged or invalid load module (0D, or 0E reason 24 or 28).
  • An I/O error on the library (0F).

How to fix it

  1. Read the return and reason codes in the abend message.
  2. For 0C reason 14, increase the REGION on the JOB or EXEC statement.
  3. For 0E reason 20, rerun the job so the library extents are reread.
  4. For 0D or 0E reason 24/28, relink the module and check the library is not damaged.
  5. For 0F, involve the system programmer to trace the I/O error.

Example

Illustrative only; names and values are invented.

IEF450I PAYJOB01 STEP020 - ABEND=S106 U0000 REASON=00000014