FALLOC

Synopsis

HELP:   Platform dependent file allocation parameter
TYPE:   OBJECT
SYNTAX: FALLOC(ORGANIZATION=SEQ/PS/LIB/PDS/USS/EDS/ESDS/KDS/KSDS/RDS/RRDS,BLKSIZE=num,RECFORMAT=NONE/BIN/TXT/TXT-ASA/TXT-MCC/DLM/DLM-ASA/DLM-MCC/VAR/VAR-ASA/VAR-MCC/FIX/FIX-ASA/FIX-MCC/VAR-REL/VAR-REL-ASA/VAR-REL-MCC/FIX-REL/FIX-REL-ASA/FIX-REL-MCC/F/FA/FM/FS/FSA/FSM/FB/FBA/FBM/FBS/FBSA/FBSM/FE/FEA/FEM/FK/FKA/FKM/FR/FRA/FRM/U/UA/UM/V/VA/VM/VS/VSA/VSM/VB/VBA/VBM/VBS/VBSA/VBSM/VE/VEA/VEM/VK/VKA/VKM/VR/VRA/VRM/ORG,RECLENGTH=num,KEYDISP=OLD/NEW/DEL,KEYPOSITION=num,KEYLENGTH=num,SUBSYSTEM(),SYSOUT(),SPACE(),LIKE='str',RENEW,PERFILE)

Description

The file allocation object collects several parameters for platforms which are record oriented based on a catalog system like z/OS® and where the space, volume and other things must be predefined. The supported parameters are platform dependent. Only parameters relevant for a certain platform are used. This way its possible to store files on special volumes, units, and with SMS-classes without any JCL usage on z/OS®.

But also on distributed platforms like (WIN, UNIX, MAC, ...) FLAM supports record oriented file types to keep the record information on such platforms. For this case the different record format for the open world can be defined. To read such a special file format on an open platform the correct record format must also be defined. On a catalog based system, this is not required. If the record format in the catalog are not the same as specified an error will occur.

Arguments