gtpm4m1qMessages (System Error and Offline)

RAM0-RES0

RAM007THE NUMBER OF DEFINED GENERAL MFST SLOTS EXCEEDS THE ALLOWED MAXIMUM. IT HAS BEEN RESET TO xxxx.

Where:

xxxx
The maximum number of defined general MFST slots.

Severity: 0

Explanation: The GSON and GFENS parameters reserve entries in the MFST for general data set and general file support. However, they add up to an amount greater than the maximum allowed. It was reset to the maximum.

System Action: None.

User Response: No action is required since xxxx is the largest number allowed. However, if a smaller number is desired, do the following:

  1. Recode GSON and GFENS.
  2. Rerun SIP stage I.

RAM008A VALUE OF 0 WAS CODED FOR OLDXPAT. BECAUSE OF THIS YOU WILL BE UNABLE TO

Severity: 0

Explanation: No extra program allocation table (PAT) slots were defined for the E-type loader. In order to use the E-type loader, one or more extra PAT slots must be specifically defined for it.

User Response: Do the following:

  1. Code a value of one or more for the OLDXPAT parameter to use the E-type loader.
  2. Rerun SIP stage I.

RAM009A VALUE OF n WAS CODED FOR NFBACK. THIS PARAMETER IS FOR COEXISTENCE WITH PRE 32 WAY LOOSELY COUPLED CODE ONLY.

Where:

n
The value of the NFBACK parameter of the RAM macro. This defines the number of keypoint fallback extents in the #KEYPT record area.

Severity: 0

Explanation: When a loosely coupled complex is expanded to more than eight processors, all processors must be running 32-way loosely coupled processor support and the migration of the loosely coupled complex has been completed. Once migration to 32-way loosely coupled processor support has been completed, the fallback extents in the #KEYPT area defined by NFBACK can no longer be used. You are generating a system with 32-way loosely coupled processor support in coexistence mode.

User Response: When generating a loosely coupled complex with more than eight processors, or once all processors are running with 32-way loosely coupled processor support and migration has been completed, set the value of NFBACK to 0. The fallback extents will be controlled by the #KFBXn RAMFIL definitions in the FACE table (FCTB).

RES001OPERAND xxxx OUT OF yyyy RANGE, POSSIBLE ERROR

Where:

xxxx
The operand.

yyyy
The normal range that is allowed.

Severity: 0

Explanation: The value specified for the operand in the message is not within the normal range indicated in the message. This is a suspected error.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the value specified is in error.