Steps to save a file as a named pipe in the z/OS FTP client UNIX file system
Before you begin
Procedure
Results
You know that you have completed these steps correctly
when the following events occur:
- The client receives reply 226 or 250 from the server, which indicates that the server sent the file.
- The client issues message EZA2536I or EZA1617I to indicate the total number of bytes that it received.
Tips:
- You do not need to create the named pipe with FTP before you initiate the transfer. FTP creates the named pipe during file transfer if the named pipe is not already in the file system. However, FTP is not able to transfer data into a named pipe that it creates until another process on the FTP client host opens the named pipe for reading.
- If the FTP client creates the named pipe for you, the configured umask value determines the file permissions. See the UMASK parameter information in LOCSIte subcommand—Specify site information to the local host, or the UMASK (FTP client and server) statement information in z/OS Communications Server: IP Configuration Reference for more details about the UMASK statement.