SAGI* - Batch Initialization Messages (z/VSE Only)

These messages are written to the operator console and to SYSLST by the optional Adabas job exit. See the Adabas Installation documentation for more information.

Overview of Messages

SAGI001 | SAGI005 | SAGI006 | SAGI010 | SAGI016 | SAGI091 | SAGI092 | SAGI093 | SAGI095 | SAGI096 | SAGI097 | SAGI098 | SAGI099 | SAGI101 | SAGI102

SAGI001 Software AG job exit Vv installed
Explanation

The Software AG job control exit is active.

Action

SAGUSER control statements will be processed.


SAGI005 Table allocated (low) ADDR=addr
Explanation

The SAGUSER table was allocated in system GETVIS below the 16-MB line at the address indicated.


SAGI006 Table allocated (high) ADDR=addr
Explanation

The SAGUSER table was allocated in system GETVIS above the 16-MB line at the address indicated.


SAGI010 Software AG job exit already installed
Explanation

The Software AG job control exit can be installed only once.

Action

No action is required if the Software AG job exit is actually installed. If it is not, perform an IPL and reestablish the job control exit chain.


SAGI016 Table already allocated ADDR=addr
Explanation

The program SAGINST has already allocated the DD name table.

Action:

No action is required if the Software AG job exit is actually installed. If it is not, perform an IPL and reestablish the job control exit chain.


SAGI091 Unable to locate $JOBEXIT in SDL
Explanation

The entry for phase $JOBEXIT was not found in the SDL.

The Software AG job exit cannot be installed.

Action:

Get information on the version, release, and service pack number of the operating system and call Software AG for support.


SAGI092 Unable to locate SAGJBXT in SDL
Explanation

The entry for phase SAGJBXT was not found in the SDL.

The Software AG job exit cannot be installed.

Action

Verify that phase SAGJBXT was loaded into the SVA.


SAGI093 Phase SAGJBXT in error
Explanation

The phase SAGJBXT loaded into the SVA is not the job control exit supplied by Software AG.

The Software AG job exit cannot be installed.

Action

Verify a probable error during the linkage edit of SAGJBXT.


SAGI095 Unable to determine VSE level
Explanation

Information about z/VSE (i.e., version and release) could not be found in the supervisor.

The Software AG job exit cannot be installed. A storage dump is produced.

Action

Obtain the z/VSE version and release level; call Software AG for support.


SAGI096 SAGJBXT ID not found in $JOBEXIT table
Explanation

An entry for SAGJBXT was not found in the $JOBEXIT table (for z/VSE 1.2 and above).

The Software AG job exit cannot be installed.

Action:

Add an entry for SAGJBXT in $JOBEXIT and retry the program SAGINST.


SAGI097 SAGJBXT phase phase not found
Explanation

The phase for SAGJBXT was found in the $JOBEXIT table (for z/VSE 1.2 and above), but the phase has not been loaded into the SVA.

The Software AG job exit cannot be installed.

Action

Verify that phase SAGJBXT was loaded into the SVA.


SAGI098 SAGJBXT phase phase not in SVA
Explanation

The phase for SAGJBXT was found in the $JOBEXIT table (for z/VSE 1.2 and above) and has been loaded, but not into the SVA.

The Software AG job exit cannot be installed.

Action:

Verify that phase SAGJBXT was loaded into the SVA.


SAGI099 SAGJBXT phase phase not valid
Explanation

The phase for SAGJBXT was found in the $JOBEXIT table (for z/VSE 1.2 and above) and has been loaded, but not into the SVA.

The Software AG job exit cannot be installed.

Action:

Verify that phase SAGJBXT was loaded into the SVA.


SAGI101 Allocation error (high) RC=ret-code
Explanation

An attempt to allocate space for the DD name table in 31-bit mode failed. The return code is from the GETVIS macro.

The Software AG job exit will not process SAGUSER statements.

Action:

Verify that enough storage is available in the SVA for the DD name table; then rerun SAGINST.


SAGI102 Allocation error (low) RC=ret-code
Explanation

An attempt to allocate space for the DD name table in 24-bit mode failed. The return code is from the GETVIS macro.

The Software AG job exit will not process SAGUSER statements.

Action:

Verify that enough storage is available in the SVA for the DD name table; then rerun SAGINST.