Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
EZA1725I z/OS Communications Server: IP Messages Volume 1 (EZA) SC27-3654-00 |
|
subcommand fails -- localFile is not a named pipe ExplanationThe subcommand that you issued specified a file in the client z/OS® UNIX file system as the local file. The local file is not a z/OS UNIX named pipe, and UNIXFILETYPE=FIFO is configured. A local file in the z/OS UNIX file system must be a named pipe when UNIXFILETYPE=FIFO is configured. For more information
about the UNIXFILETYPE configuration option, see the following sources:
In the message text:
System actionFTP stops processing subcommand, and prompts you to enter the next subcommand. Operator responseNone. System programmer responseNone. User responseIf you intended to specify a named pipe, do one
of the following:
If you did not intend to specify a named pipe, issue the LOCSIte subcommand with the UNIXFILETYPE=FILE parameter. Then issue the subcommand again. Problem determinationTo determine whether a z/OS UNIX file is a regular file or a named pipe, use the z/OS UNIX ls command. To create a named pipe, use the z/OS UNIX mkfifo or mknode command. See the information about the long output format in z/OS UNIX System Services Command Reference. Sourcez/OS Communications Server TCP/IP: FTP Moduleezaftpcg Routing code10 Descriptor code12 AutomationNot applicable. Example
|
Copyright IBM Corporation 1990, 2014
|