gtpd1m0s | Database Reference |
This section provides a general description for the following pool maintenance functions:
Input to pool generation is in the form of constants and equates in the system configuration macro (SYCON) built by the system initialization program (SIP). See TPF System Generation for details about SIP. Pool support allows as many as 4 device types that can be used for pools. SYCON values should be specified for all equates to prevent assembly errors even though fewer than 4 devices exist on the system.
The labels pertinent to pool support are shown in Table 1.
Table 1. SYCON Values for Pool Support
Label | Description |
---|---|
&CGDEV(1) &CGDEV(2) &CGDEV(3) &CGDEV(4) | These are global SET symbols used to assign each device a name. They must be set to blanks if the device is not supported. Otherwise, they must contain the device name. For example, if 3350s are supported as the first device for pools then &CGDEV(1) = 3350. |
CSONCMA CSONCMB CSONCMC CSONCMD | These define the number of cylinders per module for pool devices 1, 2, 3, and 4 respectively. |
CSONHCA CSONHCB CSONHCC CSONHCD | These symbols define the number of tracks per cylinder for each device. |
CSONSRA CSONSRB CSONSRC CSONSRD | These symbols define the number of small records per track for each device. |
CSONLRA CSONLRB CSONLRC CSONLRD | These symbols define the number of large records per track for each device. |
CSON4RA CSON4RB CSON4RC CSON4RD | These symbols define the number of 4KB records per track for each device. |
CSONPNMA CSONPNMB CSONPNMC CSONPNMD | The number of modules used for pool records in each device type. These values are used with the increments (CSONPLBA, CSONPSBA, and so on) to determine the small, large, and 4KB file address ranges for each device type. These ranges must not overlap among device types; otherwise, an ambiguity could be created when trying to associate an address with a device type. |
Pool definition information is part of the FACE table that is generated by the FACE table generator (FCTBG).
The record code check (RCC) is used throughout pool support to identify
specific pool types and to index pool-specific tables in the control
program. The RCC indicates the pool type as shown in Table 2. The intersection of pool type and device
type gives the RCC. Support is provided for 4 device types.
Table 2. Record Code Check Values
Pool Type | Device Type | |||
---|---|---|---|---|
A | B | C | D | |
Small Long-Term | 04 | 28 | 4C | 70 |
Small Short-Term | 08 | 2C | 50 | 74 |
Small, Long-Term Duplicate | 0C | 30 | 54 | 78 |
Large Long-Term | 10 | 34 | 58 | 7C |
Large Short-Term | 14 | 38 | 5C | 80 |
Large, Long-Term Duplicate | 18 | 3C | 60 | 84 |
4K Long-Term | 1C | 40 | 64 | 88 |
4K Short Term | 20 | 44 | 68 | 8C |
4K Long-Term Duplicate | 24 | 48 | 6C | 90 |
4K Long-Term Duplicate FARF6 | 94 | 98 | 9C | A0 |
The beginning ordinal number is the ordinal number assigned to the first record in the pool segment. Successive ordinal numbers are assigned to the remaining records in the segment. These ordinal numbers must be unique in the pool type. In addition, in FARF3/FARF4 mode, because large and 4-KB records share ordinal number ranges, there can be no ordinal number duplication in these two pool types when they also have equivalent retention and duplication definitions.
The pool generation and reallocation procedure can be used to create an initial pool configuration or change an existing pool configuration. If you are deleting pool files from your configuration, you must deactivate pool directories before changing your existing pool configuration.
See TPF Migration Guide: Program Update Tapes for more information about migrating to 32-way loosely coupled pool support and converting pool data structures to 32-way loosely coupled pool support format.
To generate or reallocate a pool configuration, do the following:
See TPF Operations for more information about the ZPMIG command.
8-Byte File Address Support |
---|
To activate FARF6 8-byte file addressing, enter ZMODE 6 so that 4D6 pools can be generated. See TPF Operations for more information about the ZMODE command. |
Pool directory update (PDU) functions are run by doing the procedures that follow.
The recoup function is used to reconcile long-term file pool directory records with the actual status of the file pool records. See Recoup for more information about recoup.
File pool count reconciliation functions are run by entering the ZRFPC command.
Online directory capture and restore functions are a part of normal recoup processing and can also be run by entering the ZRDIR CAPTURE and ZRDIR START RESTORE commands.