Before you begin
You must start an application that can write to the named
pipe, and it must open the named pipe, before FTP can transfer data
from the named pipe.
Procedure
- Create the named pipe on the server host. You
can use FTP to create the named pipe, or another process on the server
host can create the named pipe.
To create the named pipe using
FTP:
- Issue the SIte subcommand to configure the server UMASK value.
For example, site UMASK=<mask>.
You can also configure the server UMASK value by coding
the UMASK statement in FTP.DATA. See the UMASK
(FTP client and server) statement information in z/OS Communications Server: IP Configuration
Reference for more details about the UMASK statement.
Tip: After you create the named pipe, you can change
the file permissions by issuing the SIte subcommand with the CHMOD
parameter.
- From the z/OS® FTP client,
issue the MKFifo subcommand to create the named pipe. For example, mkfifo <pathname>.
See MKFifo subcommand—Create a named pipe at the FTP server host for information about the MKFifo
subcommand.
Tip: After you create a named pipe, you
can display and manipulate it with the following FTP subcommands:
- DELEte
- DIr
- Ls
- REName
- SIte subcommand with the CHMOD parameter
- Do one of the following to set the UNIXFILETYPE FIFO value
at the server host:
- Do one of the following to set the FILETYPE configuration
option to the value SEQ at the server host:
Tip: SEQ is the default value for
the FILETYPE configuration option. You can issue the stat
(filetype subcommand from the z/OS FTP client to determine whether
you need to reset the FILETYPE value.
- Optional: Do one of the following to set FIFOOPENTIME
and FIFOIOTIME values at the server:
The FTP server uses the default values for the FIFOOPENTIME
and FIFOIOTIME configuration options if you do not configure these
values explicitly.
- On the FTP server host, start the process that writes to
the named pipe.
- Issue the Get subcommand to retrieve data from the named
pipe. For example, get <named pipe>.
Results
You know that you have completed these steps correctly
when both of the following events occur:
- The server sends reply 226 or 250 to the client to indicate that
it sent the file successfully.
- The client issues message EZA2536I or EZA1617I to indicate the
total number of bytes that it received.
Guidelines: Use these guidelines
for using any FTP client to retrieve from a named pipe in the z/OS FTP server UNIX file system: