1# ftp -v vic135
2EZY2640I Using 'USER1.FTP.DATA' for local site configuration parameters.
3EZYFT46E Error in 'USER1.FTP.DATA' file: line 580 near column 11.
4EZYFT25I Using //'TPOUSER.STANDARD.TCPXLBIN' for FTP translation tables for
		the control connection.
5EZYFT75I Using internal translate tables for the data connection.
6EZA1450I IBM FTP CS V1R7
7EZA1466I FTP: using TCPCS
8EZYFT18I Using catalog '/usr/lib/nls/msg/C/ftpdmsg.cat' for FTP messages.
9EZA1554I Connecting to: vic135.tcp.raleigh.ibm.com 9.42.103.37 port: 21.
10220-FTPD1 IBM FTP CS V1R7 at VIC135.tcp.raleigh.ibm.com, 21:21:49 on 2004-11-08.
11220 Connection will not timeout.
12EZA1459I NAME (vic135:USER1):
13EZA1701I >>> USER USER1
14331 Send password please.
15EZA1789I PASSWORD:
16230 USER1 is logged on. Working directory is "USER1.".
17EZA1460I Command: 
18debug all
19PC0346 parseCmd: subcommand: debug 
20PC0371 parseCmd: parameter 1: all
21EZA2923I Active client traces - FLO CMD PAR INT ACC UTL SEC FSC(1) SOC(1) SQL
22SC3392 resetLastReply: entered
23PC0657 parseCmd: using primary session.
24CU0307 getCommand: entered
25EZA1460I Command:
26debug time
27PC0346 parseCmd: subcommand: debug
28PC0693 fndCmd: entered with debug
29PC0775 fndCmd: command found is debug
30PC0371 parseCmd: parameter 1: time
31PC0404 parseCmd: fndCmd returned the cmdrecord for debug 
32PC0536 parseCmd: using primary session
33CL0205 debug: entered
34GU2981 setDebug: entered
35EZA2923I Active client traces - FLO CMD PAR INT ACC UTL SEC FSC(1) SOC(1) SQL
3616:54:46 SC3392 resetLastReply: entered
3716:54:46 PC0657 parseCmd: using primary session.
3816:54:46 CU0307 getCommand: entered 
39EZA1460I Command:

Following are descriptions of the numbered items in the example.

1

This is the command that starts the FTP client. The -v option directs FTP to precede each client message with its unique 7-character identifier.

For more information about FTP start options, see FTP command — Entering the FTP environment.

2 to 9

These are FTP client messages, whose identifiers are always 8 characters long. The message identifier appears only when you start FTP with the -v option. After you have started FTP, you can use the client subcommand, verbose, to toggle display of client message identifiers on and off.

The first three characters are always one of the following strings:

• EZA
• EZY
• EZZ

The final character can be E, I, or W.

See z/OS Communications Server: IP Messages Volume 1 (EZA), z/OS Communications Server: IP Messages Volume 3 (EZY), and z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM)for more information about FTP client messages.

10, 11

These are replies from the FTP server. FTP server replies are always prefixed with a 3-digit numeric reply code, in the range 100 - 555. For the meaning of the reply code, see RFC 959. If the server is a z/OS FTP server, you will also find the FTP server reply code and reply text documented in z/OS Communications Server: IP and SNA Codes.

12, 13, 15, 17, 21, 25, 39

These are FTP client messages, as indicated by the 3-letter prefix.

14, 16

These are FTP server replies, as indicated by the 3-digit prefix.

18

This is the echo of input entered in response to the FTP client command prompt at line 17. The debug subcommand turns on the FTP client trace.

19, 20, 22 to 24

This is FTP client trace output. FTP client trace output lines are always composed of a 2-letter prefix with a 4-digit numeral. The FTP client trace is for the use of the IBM® Service Center.

26

This is the echo of input entered in response to the FTP client command prompt at line 25. The time option of the debug subcommand causes the FTP client trace to be time-stamped

27 to 34

This is client trace generated by the client processing the debug subcommand. This trace is not time-stamped because the client has not yet recognized that it is processing the TIME option.

35

This is a client message issued in response to the debug subcommand.

36 to 38

This is client trace output. At this point, the client has recognized the TIME option entered at line 26 and client trace is now time-stamped.