gtps4m2oSystem Generation

CORREQ

The CORREQ macro specifies main storage requirements for the online system. Many of the values defined with this macro can be altered in the online system by issuing operator commands. See the ZCTKA command in TPF Operations. The CORREQ macro is required.

Format




APSIZ24=75|size
Size (in 1KB blocks) of the program area for core resident programs that execute in 24-bit addressing mode. This area is carved below the 16MB boundary.

The sum of the values coded for APSIZ24 and APSIZ31 must be greater than or equal to 1000.

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

APSIZ31=1000|size
Size (in 1KB blocks) of the program area for core resident programs that execute in 31-bit addressing mode. This area is carved above the 16M boundary.

In addition to core resident assembly language programs running in 31-bit mode, the application area above the line contains all C language programs. You may need to increase the size of the 31-bit core resident program area (CRPA) to accommodate E-type loader versions of C load modules. The sum of the values coded for APSIZ24 and APSIZ31 must be greater than or equal to 1000.

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

IOBLK=100|n
Number of I/O Control blocks (IOBs). IOBLK must be greater than zero.

SWB=100|n
Number of system work blocks to be used by the online system. SWB must be greater than zero.

Some functions that require SWBs include:

MPIF
Output messages are queued using SWBs. See Storage Required For Control Blocks for more information.

SNA
SNA uses SWBs for scheduling post interrupt routines. You need three SWBs for each CTC link. No SWBs are used for NCPs.

TPF MQSeries
The local queue manager uses SWBs for messages within processor unique queues.

Messages in a memory queue reside in chained SWBs. The first SWB in a message chain can contain up to approximately 300 bytes of message data and subsequent SWBs in the message chain can hold up to approximately 950 bytes of message data.

FRAME=200|n
Number of 4KB frames.

Keep in mind that many components in the TPF system use frames. If your TPF system uses the E-type loader, C load modules, and the system heap facility, use the following formulas to ensure that you have enough frames allocated for these components. Use data collection and reduction to assist you in determining the overall number of frames that your TPF system requires.

COMMON=50|n
Number of 4KB common blocks.

Should the DCL list overflow then common blocks may be depleted. An additional 5 to 10 blocks should be allocated to handle this unlikely condition.

You may need to increase the number of common blocks that are allocated for ISO-C. Common blocks are used in ISO-C to hold new versions of arrays of library addresses (AOLAs) when a loadset that contains a library is activated using the ZOLDR ACTIVATE command. Use the following formula to estimate the approximate number of additional common blocks you need.

Number of
additional    = (maximum number of active loadsets containing libraries) * 2
common blocks

The multiplication factor of 2 in the previous formula takes into account deactivating (using the ZOLDR DEACTIVATE command) loadsets that contain libraries as well as excluding libraries from active loadsets. For these, the activation number is increased, a new EAT slot is created, and a new AOLA in a common block is created.

ECBS=100|n
Number of 12KB ECBs.

PTV
Specify one of the following:

NO
Online system not in test mode.

YES
Online system is in test mode and program test vehicle (PTV) is present. See the TPF Program Development Support Reference.

STV
Phase I/Phase III of PTV is not required. (This value is currently used by IPARS users only.)

SSPS=10|size
Size (in 1-MB units) of the system heap area. In TPF systems with 2 GB of storage, the system heap area is permanently backed with real storage. In TPF systems with less than 2 GB of storage, if there is no need to remove the real storage to make room for system heap virtual addresses, the system heap area is backed with 4 KB frames as each system heap storage request is made.

Common blocks must end on a megabyte boundary because frames have to start on a megabyte boundary. (Frames have to start on a megabyte boundary to limit the number of page tables required in the TPF system in order to improve performance.) If the common blocks must end on a megabyte boundary, then increasing the amount of storage to, for instance, 14MB or 16MB may push the common block area above a megabyte boundary. As a result, more common blocks would be created to fill the megabyte area remaining. When the common block area increases, VFA decreases. The other block types increase in proportion as storage increases; the common blocks do not because of the megabyte alignment.

For more information about the CORREQ macro, see TPF Main Storage Layout.

Examples

None.

References

None.