Filter
Top Products
4. Create a file on the system that you are planning to store data into. Set the
proper record length, number of members, and number of increments. Try the
data transfer again and verify that it was successful.
5. Make sure that you are authorized to use the file and the file members.
6. Check to see if the transfer file contains packed decimal or soned decimal data.
If yes, then make sure that the transfer is done as described in ″Transferring
Files that Contain Packed Decimal Data″.
7. If you are transferring a Save file, verify that the appropriate method was used
as described in ″Transferring Save Files″.
Cause List C
1. Check file size limits on the remote system.
2. Check to see if the FTP server timer ended. The AS/400 server time-out value
can be set using the QUOTE TIME command.
3. Use the NETSTAT command to verify that the *LOOPBACK interface is active.
Then re-create the problem doing FTP LOOPBACK (AS/400-to-AS/400
internally).
v If the problem cannot be recreated, it is probably a remote system problem.
v If you can re-create the problem, do the following:
a. If the problem is an FTP server problem, then start the FTP server trace
using the TRCTCPAPP command.
b. Create the problem again.
c. End the FTP connection.
d. End the FTP server trace using the TRCTCPAPP command.
e. Find a spooled file with a file name of QTMFFTRC and the user name set
to the name of the user issuing the TRCTCPAPP command which
stopped and formatted the trace. The trace is a spooled file in the default
output queue of the system associated with the FTP server job.
f. Send in that spooled file.
g. If the problem was on the AS/400 FTP client, a trace can be obtained
using the DEBUG 100 client subcommand.
h. When running the FTP client interactively, use the F6 (Print) key to create
a spool file that contains a history of the FTP client subcommands
entered, and the associated FTP server replies. When the FTP client is
run in batch unattended mode, then this history of subcommands and
server replies is written to the specified OUTPUT file. For more details,
see ″FTP as Batch Job″.
Materials Required for Reporting FTP Problems
Any FTP problem reported to IBM should include the following:
v A communications trace from the time of the failure (Request TCP/IP data only)
formatted twice: once for ASCII and once for EBCDIC. If you are not familiar with
the procedure for collecting a communications trace, refer to “Collecting a
Communications Trace” on page 493 and “Formatting and Saving the
Communications Trace” on page 499.
v If the FTP client or server has logged software error data, submit the data.
Note: The system value QSFWERRLOG must be set to *LOG for software error
logging to take place. If an error occurs while QSFWERRLOG is set to
*NOLOG, change the value to *LOG, try to re-create the error, and submit
452 OS/400 TCP/IP Configuration and Reference V4R4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|