As the client was creating what would be a static database (no additional report collection or backup processing), the space needs for the database can be obtained from the runnng of a SARDBASE STATUS FULL:
//XXXXXXXX JOB ...
//SARDBASE EXEC PGM=SARDBASE,PARM='VIEW_HLQ' <=== MODIFY DB NAME
//STEPLIB DD DISP=SHR,DSN=VIEW.CVDELOAD <=== MODIFY, IF USED
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
If you multiply the number of Total Cylinders by the Percentage Usage, you will come up with (for INDEX and DATA), the number of cylinders needed for the target database.
The target database would be created using SARDBASE ADDDS INDEX and ADDDS DATA to allocate the index and data portions, respectively.
It is suggested to stop the activity on the source database, using "/P sarstc".
Once the dataset from the SARDBASE UNLOAD of the source database is available, a SARDBASE LOAD can be used to populate the target database.
As a SARDBASE UNLOAD is a snapshot of a database, and asthe target database would be static, there will be no impact on the source database with doing a SARDBASE LOAD.