The BPGSIZE utility can be used to convert a database to a format with the same or a higher page length. The database to be converted may be the original database or any shadow database (i.e. a database copy) with a copy name other than NEW (suffix). The database to be converted must be consistent and is not altered by BPGSIZE. The consistency of a database to be converted can be verified with the BCHECK utility routine (see the “Recovery, Information and Reorganization” manual).
BPGSIZE creates the converted database as a shadow database with the copy name (suffix) NEW. During the conversion with BPGSIZE, other UDS/SQL utility routines and UDS/SQL sessions are allowed read access to the database.
The BPGSIZE utility routine operates without AFIM logging. Consequently, if AFIM logging has been turned on for the database to be converted, BPGSIZE reports the fact during conversion and also issues a warning at the end of processing. Both AFIM logging and online backup capability are always turned off for the converted database.
Following the BPGSIZE run, a number of additional measures are required (see section "Preparing the converted database for DB operation") to prepare the converted database for use in the running UDS/SQL mode.
When it starts BPGSIZE takes into account any UDS/SQL pubset declaration which is assigned (see the “Database Operation” manual, Pubset declaration job variable). Faulty assignment results in the program aborting.