Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
File transfers to the BatchPipe subsystem fail z/OS Communications Server: IP Diagnosis Guide GC27-3652-02 |
|
If a file transfer to a batch pipe fails, the problem could be that the batch pipe reader has not been started. Verify that the batch pipe reader is active. Guideline: In a JESMAS environment, if you use FTP to submit a job
starting the batch pipe reader, the job can run on any system in the
JESMAS environment unless you include this JCL statement in your job:
If your file transfer
runs on a different system in the JESMAS environment, the JWT time
limit will expire, and the FTP server JOB will appear to hang. You
can avoid this by adding the JCL statement:
to your batch pipe job.When a file transfer to a batch pipe
fails with an allocation error, the problem could be that the BatchPipe
subsystem has not been started. Verify that the BatchPipe subsystem
is started. For example:
You can activate the FTP server trace to obtain more information about the failure. See Diagnosing FTP server problems with traces for information about activating the FTP server trace. Inspect the SYSLOG output for messages related to the file transfer failure. A sample syslog output is:
Error code 04AC means that the subsystem is not operational. When FTPLOGGING is set to TRUE in the servers FTP.DATA file, the error messages will be logged in SYSLOGD. You can look up the messages and error codes. |
Copyright IBM Corporation 1990, 2014
|