A user space (and also the catalog space) which is created (with CREATE SPACE, CREATE CATALOG or RECOVER TO) with SESAM/SQL on a pubset which supports “large files” can be up to 4 TB in size (“large space”).
Otherwise it can be up to 64 GB in size.
The maximum space size can be ascertained from the SYS_INFO_SCHEMA. For this purpose the SYS_SPACE_PROPERTIES view (in the utility monitor via the SNF function) displays the highest possible page number with MAX_POSSIBLE_PAGE:
1,073,741,822 (X'3FFFFFFE') for spaces up to 4 TB
16,777,214 (X'00FFFFFE') for spaces up to 64 GB
Spaces from earlier SESAM/SQL versions can be migrated to “large spaces” using the utility statement REORG SPACE provided the spaces are located on a pubset which supports large files. After migration you should create a SESAM backup.
If no SESAM backup is created after migration, the space in ongoing operation exceeds the 64 GB limit and the space subsequently needs to be recovered, a backup of the “old” space must be used. The recovery will be aborted because the 64 GB limit was exceeded while the logging files were being recovered.
You can bypass this problem by initially generating a replica from the backup of the “old” space. The replica is then reorganized with REORG SPACE, and the recovery is subsequently implemented with the replica (RECOVER ... USING REPLICATION).