gtpm1m2f | TPF V4R1 Migration Guide: 3.1 to 4.1 |
In the TPF 4.1 system minor changes were made to pool directories. In this release there are two new fields.
Be aware that the ordinal is used to access the file address compute program (FACE) table. The file address in the directory is no longer used. The ordinal/record code check (RCC) is now written to the RTA for a released long-term pool type rather than the file address. In addition, you should use the SONIC or ESFAC macros to check the record attributes, rather than testing bits in the file address because some of the control bits disappear in FARF4 and they all disappear in FARF5.
The TPF 3.1 pool directories can be used as in the TPF 4.1 system. As the pool directories are brought into main storage during reorder, the CYAR segment initializes the new fields. The ZPOOL command should not be used to convert pool directories.
DYOPM, the offline pool maintenance program, always generates the TPF 4.1 fields. DYOPM also fills in the TPF 3.1 fields when the TPF 4.1 system is still in migration mode. Migration mode exists while in the FARF3 to FARF4 migration stage. Once the TPF 4.1 system is in the FARF4 to FARF5 migration stage, fallback is no longer possible.
Attention: There are no major changes to the pool record layout in the TPF 4.1 system. You can use the same pool data structures as used in the TPF 3.1 system. If you choose to use the TPF 3.1 pool data structures, do not load a new keypoint 9 (CTK9). In addition, for ease of migration, CTK9 should have the same MCHR as found in the TPF 3.1 system.
One suggested method for migrating imbedded pool file addresses is to remove imbedded pool file addresses and replace them with pool ordinal numbers and pool record type indicators. The FACE/FACS/FACZC macros were enhanced to accept a pool record type and a pool ordinal number (as follows here) and return a file address. You can use the following pool type names as if there were fixed record type names.