In order to update the DBTTs of the database, one work file is required by BPGSIZE for each record type contained in the realm being converted.
These work files have the following names:
UTI.BPGSIZE.dbname.realmref.recref
dbname | |
Name of the database being converted | |
realmref | |
Three-digit internal number of the realm being converted | |
recref | |
Five-digit internal number of the record type | |
A work file with recref 0 is also required for each realm for the handling of SYSTEM sets. A work file with realmref 0 and recref 0 that is shared by all realms is required for completion processing.
These files are created by BPGSIZE during conversion on a public volume by default and with a primary allocation of 129 PAM pages and a secondary allocation of 25 PAM pages.
If desired, you can use the BS2000 CREATE-FILE command before executing BPGSIZE to create the work files independently under a specific catalog ID or on private disk. Note, however, that you must always use the standard file names. The internal realm and record reference numbers and their corresponding assignments can be determined with the BPSIA utility routine (see the “Recovery, Information and Reorganization” manual). The data population for buffering is calculated for the record-specific work files using the following formula:
Number of records of the record type in the relevant realm *Number of DBTT columns of the record type * 9 Bytes
If the DBTT of a record type lies in the same realm as all records of that type, BPGSIZE processed the associated work file together with the realm and then deletes the work file. Otherwise, BPGSIZE deletes the work file only after all realms (including the DBDIR and DBCOM) and possibly the COBOL subschema directory (COSSD; see next section) have been successfully converted.
The LMS library SIPLIB.UDS-SQL-T.024 contains the example procedure P.GEN-FILE-BPGSIZE which uses CSV output data from the BPSIA and BSTATUS utility routines to create the record-specific work files.