The following rules govern the definition of the attributes for a new receive file, regardless of the type of the receive file (PS data set, VSAM file etc. (i.e. cases "N", "D + N" and "O" in the above table):
File structure
The file structure of the receive file is derived from the prefix specified as part of the file name in the NCOPY command. The following prefixes can be used (see also "Attributes of receive files"):
:S: | for PS |
:V: | for VSAM (of the type "entry sequenced") |
:L: | for PO or PDSE |
:O: | for PO |
:E: | for PDSE |
In the case of prefixes :L:, :O: and :E: the structure of the file name is also important:
:L:filename, :O:filename and :E:filename represent a complete PO or PDSE data set, while :L:filename(membername), :O:filename(membername) and :E:filename(membername) represent a member of a data set.
If complete PO or PDSE data sets are to be transferred homogeneously and in one of the systems openFT < V10 is used then the receive file must always be specified with the corresponding type :O: or :E: in the request since otherwise a PS file is created.
If the file structure of the receive file is not clearly defined by the file name specified in the NCOPY command (i.e. it does not contain a prefix or it contains the prefix :L:, which can stand for PO or PDSE), it is determined by predefined values entered by the
FT administrator (for more information, refer to the manual "openFT (z/OS) - Installation and Operation") or openFT-internal default values or system defaults. These are:
filename
represents a sequential file; the FT administrator can specify the file structure PS or VSAM (of the type "entry sequenced"); if the FT administrator has not entered a predefined value, the following applies:
in the event of a homogeneous link between two openFT systems as of V10, the file organization of the send file is taken if it is not a PO or PDSE or an openEdition file.
in all other cases, PS is the default. (Exception: If the existing file is of the type "VSAM entry sequenced", a VSAM file is again created by default.)
:L:filename
represents a complete PO or PDSE data set; the FT administrator can specify the file structure PO or PDSE; if the FT administrator has not entered a predefined value, the following default values are used:
if the IBM software product DFSMS (Data Facility System-Managed Storage) is not installed, PO is the default
if DFSMS is active: the default is specified with an ACS routine or SYS1.PARMLIB (please consult your z/OS system administrator)
filename(membername) or :L:filename(membername)
represents a member of a PO or PDSE data set; for the selection of the exact file structure, the same principle applies as for a complete PO or PDSE data set (specification :L:filename)
File name
The file name is defined by the specification in the NCOPY command (FILE-NAME operand). If the file name specified in the NCOPY command is enclosed in single quotes, it is interpreted as a fully qualified file name (including "first level qualifier"). If the file name specified in the NCOPY command is not enclosed in single quotes, the user ID from the TRANSFER-ADMISSION of the system involved is prefixed to it as the "first level qualifier".
In the case of a VSAM file, the name formed in this way is used as a cluster name. The data name also required is assigned by IDCAMS (usually the cluster name together with the suffix .DATA). The "first level qualifier" must reference an existing VSAM or ICF catalog as an alias.
Volume
A distinction is made here between new files ("N" in the above table) on the one hand, and files which are overwritten ("O") on the other hand.
In the case of new receive files, the FT administrator can specify the volume (which remains the same for all transfer requests). If the FT administrator has not specified a volume, the volume is determined by the system defaults for new files.
If, however, the receive file overwrites a file of the same name (not as a result of deletion and re-creation), the volume specified for the old file applies.
Storage allocation
For both homogeneous and heterogeneous links, the allocation of disk storage to the receive file is determined by the transferred file size of the send file (see “Primary andsecondary allocation” (Transferring z/OS files)).
Exception
In cases where an existing PS data set is actually overwritten (entry "O" in the above table), no new disk storage is initially allocated. The storage space already used is overwritten and additional storage, if required, is requested during transfer,
However, the z/OS data management system only permits 16 “extents” for PS and PO files. In the case of PDSE and VSAM files this number is 123. If this is insufficient, file transfer is canceled with an error message. The Data Management System also issues an error message in the job logging facility.
Data access control
File protection attributes of the send file are not transferred to the receive system.
openFT does not assign any data access control attributes to new files. In particular, no file password is passed on to the system and the so-called "RACF bit" in the DSCB (data set control block) is not set by openFT. If a new file is to be immediately protected against unauthorized access in z/OS, use of the RACF function "generic profile" is recommended (see openFT manual "Concepts and Functions" under „Access protection for send and receive files“).
openFT does not set any retention period for a new file.