Link to home
Avatar of D B
D BFlag for United States of America

asked on

Not Connected in FTP log file

I am using the generic Windows ftp.exe program to transfer a file from mainframe to PC. It has been working like a champ. I have a script file that is identified on the command line and output from the command is redirected to a log file (ftp.exe .... > logfile.log). The contents of the log file is shown below. I cannot determine why I get the "Not connected." message (obviously, the file does not get transferred).

This process has run daily for months, and when I ran it again about 30 minutes later, it ran successfully. This is all being run within an ActiveX vbscript, and I would like to automate error reporting, etc. I parse the log file after the transfer, and am taking almost everything into account, except for this. I would like to provide a short verbose reason for the failure.

Can someone explain under what circumstances this particular scenarion occurs?
220-XXXXXX21 IBM FTP CS V1R8 at 1S01.CORP.INTRANET, 08:29:07 on 2008-07-22.
220- -----------------------------------------------------------
220- This is a secured system.  Any unauthorized access to this
220- system will be prosecuted to the fullest extent of the law.
220- If you are so authorized, WELCOME.
220- -----------------------------------------------------------
220 Connection will close if idle for more than 60 minutes.
ftp> USER #ABCDEF
331 Send password please.
ftp>
Not connected.
ftp> GET 'DATA0000.ES01.HOUSEXTR.XI.G1191V00' "\\pkdw####l\ourteam\Staging\House\HOUSEXTR.XI.G1191V00"
 
ftp> BYE
221 Quit command received. Goodbye.

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of giltjr
giltjr
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of D B

ASKER

This is the first time I've ever seen it happen. Hopefully the last. This is actually part of a SQL Server DTS package that dynamically builds the FTP statements and script files. There are 9 files that are transferred daily. I have received other error messages, and I parse the log file after the session ends to determine if the file successfully transferred, or specifically what error occurred. As I indicated, I've never seen this before. It happeneed with all nine files, but like I said, when I ran it again about 30 minutes later, everything worked fine.

Maybe a network glitch?
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of D B

ASKER

Since it was a one-time deal, I am not going to loose any sleep over it. I'll attribute it to network glitch, high humidity and lack of cold beer! Thanks for the input.