The following example is based on the assumption that the TRAVEL database is initially available in a 2-Kbyte format. The example shows the conversion of this 2-Kbyte database to the 4-Kbyte format. Since a small database is involved, it makes sense to convert this database in a single BPGSIZE run. The work files are created automatically by BPGSIZE.
/ADD-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=TRAVEL.DBDIR
/CREATE-FILE FILE-NAME=TRAVEL.DBDIR.NEW,SUPPORT=PUBLIC-DISK(SPACE=RELATIVE -/ (PRIMARY-ALLOCATION=200,SECONDARY-ALLOCATION=50))/CREATE-FILE FILE-NAME=TRAVEL.DBCOM.NEW,SUPPORT=PUBLIC-DISK(SPACE=RELATIVE -/ (PRIMARY-ALLOCATION=550,SECONDARY-ALLOCATION=50))/CREATE-FILE FILE-NAME=TRAVEL.TRAVEL-RLM.NEW,SUPPORT=PUBLIC-DISK( -/ SPACE=RELATIVE(PRIMARY-ALLOCATION=250,SECONDARY-ALLOCATION=50))/ADD-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=TRAVEL.DBDIR/SELECT-PRODUCT-VERSION PRODUCT-NAME=UDS-SQL, VERSION=02.9B00/START-UDS-BPGSIZE
***** START BPGSIZE (UDS/SQL V2.9 1801 ) 2019-01-29 09:27:01
//CONVERT-DATABASE REALM-NAME=*ALL,DATABASE-PAGE-LENGTH=4KB
//END
***** BEGIN FUNCTION CONVERT DATABASE AT 2019-01-29 09:27:01
***** CONVERSION OF REALM DBDIR STARTED
CALC FOR RECORD USERGROUP-RECORD CONVERTED
CALC FOR RECORD SUBSCHEMA-RECORD CONVERTED
CALC FOR RECORD ERROR-MESSAGE CONVERTED
***** CONVERSION OF REALM DBDIR FINISHED
***** CONVERSION OF REALM DBCOM STARTED
***** CONVERSION OF REALM DBCOM FINISHED
***** CONVERSION OF REALM TRAVEL-RLM STARTED
CALC FOR RECORD TRANSPORTATION CONVERTED
CALC FOR RECORD ARRANGEMENT CONVERTED
CALC FOR RECORD HOTEL CONVERTED
***** CONVERSION OF REALM TRAVEL-RLM FINISHED
***** NORMAL END FUNCTION CONVERT DATABASE AT 2019-01-29 09:27:02
***** DIAGNOSTIC SUMMARY OF BPGSIZE
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 345
***** NORMAL END BPGSIZE (UDS/SQL V2.9 1801 ) 2019-01-29 09:27:02