Transfer CFT interprets the size of a logical record (FLRECL= and NRECL=) to adapt the size of exchanged articles.If this parameter is not present, V is the default value. Transfer CFT interprets the file format (FRECFM= and NRECFM=) to select a data exchange method.For this reason, parameter settings must take into account the following: Transfer CFT uses these parameter characteristics as a basis for ensuring data management for a transfer. The RECFM, LRECL and BLKSIZE parameters retain their characteristics when they are conveyed between heterogeneous partners. RECFM, LRECL, and BLKSIZE characteristics If the parameter is not present, the binary file type becomes the default type. Enables sending a text file that contains records that are larger than 32 KB.Transfer CFT treats the data in continuous flow.Transfer CFT treats the data in record mode.The FTYPE= and NTYPE= parameters convey the file type. HFS files are specified by their type, depending on whether they contain text (structured) or are binary (non-structured). To select all files in all of the folders, for example: FNAME =/home/qualcft/**Ī single asterisk * only selects the file in the immediate folder. To enable recursive processing for a group of files, use the following syntax ** (two asterisks). However, as the value for the NFNAME= parameter is not converted to upper case, it should not be coded between quotes “…”.įNAME ="/home/qualcft/send/" This means that the files values for the parameters associated with FNAME=, and WFNAME= parameters must be coded between quotes “…”. The CFTUTIL utility COPYFILE function does not work with HFS files.įile names coded in the FNAME=, WFNAME=, and NFNAME= parameters must follow the UNIX conventions for file identification.Does not support generic sending of HFS in homogeneous mode.This excludes any other use in the Transfer CFT. Transfer CFT z/OS can only access HFS files for a transfer. As a result, parameter settings must take these characteristics into account when characteristics are conveyed between heterogeneous partners. However, Transfer CFT uses these characteristics as a basis for ensuring the data management and the transmission of file characteristics towards the receiver for a transfer. The z/OS file characteristics, such as format (RECFM), record size (LRECL), and block size (BLKSIZE) are meaningless for an HFS file. The complete name is limited to 248 characters.
All file name components are separated by the ‘/’ character. Transfer CFT only accepts the complete name from the root directory. HFS files are managed either by applications that work in an UNIX/OMVS environment, or by applications that use the USS UNIX System Services, such as the management and access interface. The HFS files are installed in hierarchical disk spaces, and divided into directories and sub-directories according to UNIX conventions. The HFS Hierarchical File System data architecture is consecutive and non-structured for records and blocks.