Version 7.4.4
 —  Messages and Codes  —

SAGEnn-VSE/ESA Batch Job Exit Utility Messages

These messages are written over the redisplayed SAGUSER batch control statements, starting in column 26, by the Software AG job exit utility (batch) for VSE/ESA systems.

Overview of Messages

SAGE020 | SAGE021 | SAGE022 | SAGE023 | SAGE024 | SAGE025

SAGE020 - SAGIPT NOT FOUND IN THE SDL
Explanation:

An entry for the phase SAGIPT was not found in the SDL.

Action:

The SAGUSER control statements cannot be processed.

User Action:

Verify that the phase SAGIPT was loaded into the SVA (using the SET SDL command). Load the phase if required, run the program SAGINST, and resubmit the job.


SAGE021 - DD NAME TABLE NOT FOUND
Explanation:

The control table used by the job control exit cannot be found.

Action:

The SAGUSER control statements cannot be processed.

User Action:

Verify that the program SAGINST ran correctly. If not, rerun it and verify that one of the following messages is displayed: SAGI005, SAGI006, or SAGI016.


SAGE022 - NO ROOM IN DD NAME TABLE
Explanation:

The control table used by the job control exit is full.

Action:

The SAGUSER control statements cannot be processed.

User Action:

Wait until some of the currently running jobs have completed and rerun the job that received the error message.


SAGE023 - INVALID OR MISSING FILE=
Explanation:

The SAGUSER control statement does not contain a "FILE=" parameter.

Action:

The SAGUSER control statement cannot be processed.

User Action:

Add the correct file designation to the control statement and rerun the job.


SAGE024 - INVALID OR MISSING MEMBER=
Explanation:

The SAGUSER control statement does not contain a "MEMBER=" parameter.

Action:

The SAGUSER control statement cannot be processed.

User Action:

Add the correct member designation to the control statement and rerun the job.


SAGE025 - INVALID SAGUSER CONTROL STATEMENT
Explanation:

The SAGUSER control statement does not contain any valid keyword parameters.

Action:

The SAGUSER control statement cannot be processed.

User Action:

Add the correct parameters to the control statement and rerun the job.


Top of page