HFS File Support

The platform server supports the transfer of HFS files. Both send and receive operations are supported.

See the following restrictions for this support:
  • The platform server started task user must be defined as a superuser.
  • Users initiating a request for an HFS file must have the OMVS segment defined so that they are recognized as OMVS users.
  • For a file create operation, the HFS directory must exist. The platform server for z/OS will not create a directory.
  • The user associated with a file transfer request must have the necessary authority to read or update an existing file depending on whether a send or receive transfer is performed.
  • For a file create operation, the user must have write authorization for the directory that the file is written to.

The platform server supports file names of up to 256 characters long. The platform server creates the security environment for a transfer request by validating the user ID and password through RACF. After the security environment is established, standard OMVS security validation is performed.

During text record processing, line feed (LF) is inserted at the end of each record. LF is not inserted on binary transfers. All text transfers store data in EBCDIC.