Troubleshooting
The FTP adapter can reference up to 1024 temporary files during process execution.
For error codes and messages the adapter returns, see Return Codes and Error Messages.
Various troubleshooting tools are available in case of problems using the FTP adapter for data sources or targets for a map. For example, if you attempt to run a map that uses the FTP adapter and encounter problems or do not receive the expected results, use the following adapter troubleshooting tools:
- adapter audit log (.log)
- adapter trace file (.mtr)
Adapter audit log
The adapter audit log is a text file created during the adapter execution that records information about the events that occurred during the adapter activity. Use the adapter command (-AUDIT) to produce adapter audit log. The default log name is m4ftp.log, located in the map directory. See Trace (-T or -TRACE) for more information about the Trace command.
The adapter audit log contains information including the following:
- host identifier
- files sent or received
- size of each file
- elapsed time
- retry count for each file
Sample FTP adapter audit log
BEGIN FTP AUDIT
Receiving from Host: localhost
Filename Filesize Time Retry
-------------------------------- ---------- ---- -----
rollback.gif 183 KBytes 000s 0
END FTP AUDIT
Adapter trace file
The adapter trace file contains detailed information the adapter provides and records the actions taking place, such as connections established and statements executed. The trace file is produced during the adapter execution and can be used as a debugging aid. To produce a trace file for the adapter, use the (-TRACE) adapter command. The default adapter trace file name is m4ftp.mtr, located in the map directory. See Audit (-A or -AUDIT) for more information about the Audit command.
Sample FTP adapter trace file
Retry Count is 0. Retry Interval is 0. Rollback is OFF.
Fetch Unit is 0. Burst Mode is OFF
Run Started at 08: 49: 38.911 on 03/28/00.
>220- (S)
>220-This is a demo version of the Vermillion FTP Daemon, licensed only for (S)
>220-a 30 day evaluation period. For continued use, you must purchase a (S)
>220-license. For more information or to download the latest version, please (S)
>220-visit Arcane Software on the web at `http: //www.arcanesoft.com'. (S)
>220- (S)
>220-Note: This session is limited to 15 minutes. If you are transferring a (S)
>220- file at that time, the system will wait until it is complete (S)
>220- before automatically disconnecting you. (S)
>220 (S)
<USER sls
>331 Password required for sls. (S)
<PASS sls>
230 User sls logged in. (S)
<SYST
>215 UNIX Type: L8 (S)
Setting AIX/UNIX-specific parameters.
<CWD /d:
>250 CWD command successful. (S)
<TYPE I
>200 Type set to I. (S)
<PASV
>227 Entering passive mode (127,0,0,1,8,230) (S)
Using port `2278' for the connection.
Connecting to `127.0.0.1'.
Socket Opened.
Connected.
<RETR rollback.gif
>150 Opening BINARY mode data connection for rollback.gif (187714 bytes). (S)
(187714 bytes received)
Socket Closed.
Connection closed.
>226 Transfer Complete. (S)
<QUIT
>221 Goodbye. (S)
Socket Closed.
Connection closed.
Winsock Client ID 1 disabled.
Read 187714 bytes from /d: /rollback.gif.
Data in E: \167.tmp kept.
Run Completed at 08: 49: 39.742 on 03/28/00.
Temporary file limit
During a PUT or output card operation, the FTP adapter transfers files at the end of a successful map execution. When a run map invokes the FTP adapter, and the FTP operation is set to Card scope, the adapter transfers the files after the run map completes.
The default FTP operation is Map scope. When a run map invokes the FTP adapter, and the FTP operation is set to Map scope, the FTP adapter stores the contents in a temporary file. After the top-level map completes successfully, the FTP adapter sends all the temporary files to the target FTP server. If the number of FTP temporary files in all executing maps exceeds the limit of 1024, the adapter writes a message to the trace file and returns an adapter error message.