Allocation behavior
Support for files >= 32 GB is only possible for non-PAMKEY files on pubsets where LARGE_OBJECTS=TRUE and LARGE_FILES_ALLOWED=TRUE.
Thus, PAMKEY files on these pubsets may not exceed previous allocation limits for reasons of compatibility. The PAMKEY property of a file is not binding at the point at which FILE is executed; it only becomes definitive when the file is accessed using OPEN.
The behavior for files on all other pubsets (LARGE_OBJECTS=FALSE or TRUE, LARGE_FILES_ALLOWED=FALSE) does not change, i.e. the FILE interface rejects an allocation that exceeds the 32 GB limit.
Indicating whether large files are permitted
At program level, the EXC32GB operand controls whether large files are permitted. The operand does not affect the allocation behavior of the FILE interface.
Operation | Operands |
|
|
EXC32GB
Only for disk files; only for non-PAMKEY files:
The EXC32GB operand determines whether or not the file size may exceed 32 GB when the file is processed. The operand is entered in the TFT (Task File Table) and is only evaluated when the file is opened using OPEN.
During processing, EXC32GB does not affect the space assignment of the FILE call.
= FORBIDDEN
The file size may not exceed 32 GB.
= ALLOWED
The file size may exceed 32 GB.