gtps4m34System Generation

RAM

The RAM macro is used to specify the resource allocation characteristics.

The RAM macro is required.

Format




Notes:

  1. The following parameters are only used by SIP Stage I processing.

  2. The following parameter is used by the offline FACE table generator as well as by SIP Stage I processing.

  3. The following parameter is used by the offline FACE table generator alone.

GFENS=n
Specifies the number of slots to be created in the General File Module Table (must be greater than the highest data set number specified in the GENFIL macro but less than 61). This value also represents the number of general file pseudo module numbers allowed on the system, and it is used to determine the number of Module File Status Table entries to generate for use of general files.

GFMOD=230|n
Specifies the starting general file symbolic module number (must be three decimal characters).

ECBNL
Designates whether the number of program nesting levels is limited or not through the use of overflow blocks.

NOLIMIT
The number of program nesting levels is unlimited through the use of overflow blocks.

LIMIT
The number of program nesting levels is limited to the area provided in the ECB.

PHTBL=97|n
Number of primary hold table entries. To take full advantage of the system's hashing algorithm, this should be a prime number.
Note:
In a system with the multiple database function (MDBF) this parameter is necessary only for the basic subsystem generation. (BSSGEN=YES in the SSDEF macro.) All subsystems will use the value from the basic subsystem.

OHTBL=37|n
Number of overflow hold table entries. To take full advantage of the system's hashing algorithm, this should be a prime number.
Note:
In a system with the multiple database function (MDBF) this parameter is necessary only for the basic subsystem generation. (BSSGEN=YES in the SSDEF macro.) All subsystems will use the value from the basic subsystem.

GSON=1|n
Specifies the number of Module File Status Table entries to be created for use with general datasets. 'n' must be in the range 0-3997.
Note:
The summation of GFENS and GSON may not exceed 3998. Also, keep in mind that the ZAVSN/ZDVSN commands require an available general dataset entry in the Module File Status Table (MFST).

OLDXPAT=1000|n
Specifies the number of extra program allocation table (PAT) slots to allocate for the E-type loader. Use the following formula to help determine how many extra PAT slots are needed:
A(B + C(D - 1))

Where:

A
Maximum number of active loadsets for a given processor.

B
Average number of programs in a loadset.

C
Average number of I-stream unique programs in a loadset.

D
Number of I-streams in the system.

In addition to using the formula, it is important to remember that when a loadset is deactivated, the PAT slots used by that loadset remain in use until there is no more activity on the loadset. Therefore, consider increasing the number of PAT slots determined by the formula by approximately 10% to accommodate this situation.

This parameter is subsystem unique. The value of this parameter is stored in keypoint A (CTKA).

NFBACK=0|n
Specify the number of fallback keypoint areas desired in the #KEYPT record area. This option is for use in an MDBF system where the basic subsystem is generated on a small number of packs. If specified in a non-MDBF system, the fallback areas cannot be used to IPL the system. This parameter is supported for coexistence of systems with and without 32-way loosely coupled processor support. Once migration to 32-way loosely coupled processor support is completed, the number of fallback extents will be controlled by the #KFBXn RAMFIL definitions in the FACE table (FCTB). See TPF Main Supervisor Reference for more information about keypoints.

HASHSZ=0|n
Defines the number of 4-byte entries of the hash table used for the symbolic resolution of FACE IDs by program FACS. If HASHSZ is not specified or is coded as 0, the offline FACE table generator will attempt to build a table with no synonyms. The table size is unpredictable, although it is less than 32 767 entries. Coding a valid hash table size will fix the size of the hash table. The smallest value that may be coded for this parameter is one more than the number of unique record types. If the value is coded, it should be coded as a prime number. The largest value for this parameter is 128KB-1 (131 071).

Examples

None.

References

None.