MainframeKit

S522

Wait time limit exceededSYSTEM ABEND

Every task in the step stayed in a wait longer than the site's continuous wait limit (JWT).

MOST LIKELY

The program waited for an event that was never posted.

FIRST CHECK

Find out what the step was waiting for when it was ended.

TRY IT ▸

MainframeKit assistant

What it means

The system limits how long a job step may sit in one continuous wait. The limit is the JWT value set by the site in SMF parameters. If all tasks in the step wait longer than that, the system ends the step with 522.

It is not about CPU use. The job was idle: waiting for an event, a reply, a resource or a tape mount that never came. TIME=1440 or TIME=NOLIMIT removes the limit for that step.

Typical causes

  • The program waited for an event that was never posted.
  • A TSO user or interactive job left idle.
  • A long wait for a resource held by another job.
  • A started task or long-running server that is meant to wait, without TIME=1440.

How to fix it

  1. Find out what the step was waiting for when it was ended.
  2. Fix the program logic if it waited on the wrong event.
  3. Check for contention on data sets or other resources at that time.
  4. For tasks that are designed to wait, code TIME=1440 or TIME=NOLIMIT on the EXEC statement, following site rules.

Example

Illustrative only; names and values are invented.

IEF450I SRVJOB01 STEP010 - ABEND=S522 U0000 REASON=00000000