Hello George,

There have been a number of problems reported in recent times with the
operation of EXITONERROR and setting of the FTP@ variables.  Later this
week we will be releasing 5.5 patch FTPFDR3 and 6.0 patch FTPFDP3 which
will resolve all of the known problems of this type.

Regards,
Damian Coffey,
HP Australia.

George Willis wrote:
>
> 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