Subject: | |
From: | |
Reply To: | |
Date: | Mon, 15 May 2000 15:17:14 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
George,
As you have 'cut out' part of the $stdlist I am unable to tell if you 1) had
any other commands after the PUT, 1) used the EXITONERROR command.
Regards,
Robert W.Mills (Windsong Services)
-----Original Message-----
From: George Willis [mailto:[log in to unmask]]
Sent: Monday, May 15, 2000 2:48 PM
To: [log in to unmask]
Subject: Problems in FTP Error trapping
I'm looking for suggestions on why FTP does not set an error condition when
it encounters a "SOCKERR". How can we catch this and not allow the job to
continue?
PUT AMODSUB.DBASE.DVTEMP AmodSub.Dat
200 PORT command successful.
150 Opening BINARY mode data connection for AmodSub.Dat.
425 Can't open data connection.
Error 0 (SOCKERR)
END OF PROGRAM
:IF FTPLASTERR <> 0
*** EXPRESSION FALSE: COMMANDS IGNORED UNTIL MATCHING ELSEIF/ELSE
/ENDIF
: TELLOP ** FTP Contains a problem
: SETAPAGE
: SETVAR ADDR "!GJWP," + "!WFKP," + "!HDDP"
: MAILER "!ADDR" "[FS1] WHFTP Contains errors."
: FLUSHME
:ENDIF
Here are the environment variables at the time of this event:
FTPLASTERR = 0
FTPXFERFILES = 1
FTPREQFILES = 1
FTPREPLACE = TRUE
FTPLASTREPLY = 425 Can't open data connection.
FTPLASTMSG = Error 0 (SOCKERR)
George Willis
Fayez Sarofim & Co
713-308-2803
|
|
|