IIRC, 5.5PP4 introduced a change in the way ftp handles formerly "benign"
error conditions, such as what you're experiencing.  We ran into this, and
had to change the way we use EXITONERROR.  I'd recommend that you toggle
EXITONERROR off just before you call your delete command, then back on
afterward if needed.

This isn't a bug ... just a largely undocumented fix to make ftp adhere
more to standards -- or so I was told by HP.

Lee Gunter
Regence BlueCross BlueShield of Oregon / Regence HMO Oregon
==========================================================
The opinions expressed, here, are mine and mine alone.



From: Steve Hammond <[log in to unmask]> on 05/14/99 09:41 AM

Please respond to Steve Hammond <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  [HP3000-L] FTP problems




I have just upgraded to 5.5 pp6 and I remember seeing some traffic about
problems w/FTP in pp6.

Here is my screnario:

- we want to move file XYZ.TXT to a network (novell) drive in a job stream
- FTP starts and logs in without a problem
-  do a delete of XYZ.TXT to make sure that file does not already exist,
although 95% of the time the file does not exist
- put XYZ.TXT
- exit

This always worked in the past, but since the upgrade, the job chokes on
the delete. To use MPE jargon, it's like there used to be a 'CONTINUE'
before the delete, but now there is not.

Is this one of the identified bugs in FTP on pp6?

thx
steve hammond
[log in to unmask]