z/OS Communications Server
Diagnosing FTP Client Problems


Now that you have decided to start the investigation with the FTP Client, the next step is to determine at what point in the client process the error occurs (click here to skip the tutorial information). A typical FTP session can be broken into four phases:

The following output shows a typical FTP session, broken into these four categories:

CLIENT INITIALIZATION
    READY
  ftp mvs057.tcp.raleigh.ibm.com
    EZY2640I Using 'USER2.FTP.DATA' for local site configuration parameters.
    EZA1450I IBM FTP CS V1R6
    EZA1466I FTP: using TCPCS

CONNECTION ESTABLISHMENT
    EZA1554I Connecting to: mvs057.tcp.raleigh.ibm.com 9.42.104.19 port: 21.
    220-FTPD1 IBM FTP CS V1R6 at MVS057, 15:17:06 on 2005-05-12.
    220 Connection will close if idle for more than 45 minutes.

LOGON PROCESS
    EZA1459I NAME (mvs057.tcp.raleigh.ibm.com:USER2):
  user2
    EZA1701I >>> USER user2
    331 Send password please.
    EZA1789I PASSWORD:

    EZA1701I >>> PASS
    230 USER2 is logged on. Working directory is "/etc".
    EZA1460I Command:

POST-LOGON PROCESS
  cd /tmp
    EZA1701I >>> CWD /tmp
    250 HFS directory /tmp is the current working directory
    EZA1460I Command:
  ls
    EZA1701I >>> PORT 9,42,104,19,4,37
    200 Port request OK.
    EZA1701I >>> NLST
    125 List started OK
    EZA2284I 68283-70FB.LF.txt EZA2284I 68283-70FB.txt
    EZA2284I CTRACE.txt
    EZA2284I user36
    EZA2284I vbs.txt
    250 List completed successfully.
    EZA1460I Command:
  quit
    EZA1701I >>> QUIT
    221 Quit command received. Goodbye.
    READY

Review the client's output, and use this to determine in which phase the error occured.


In which of the following phases does the error occur?