I recently upgraded from WS_FTP Pro 6.60 to the 7.02 version and now some of
my batch files are not working. I have changed to the new syntax
requirements according to articles posted on the Knowledge Base but
transfers which involve profiles without the password hardcoded simply fail
(in the prior version, we received a password prompt) and destination
filenames on our IBM MVS remote site cannot be found. For anyone interested
in the detail, it is provided below. Any help you could offer would be
greatly appreciated. Note: it appears as if my old profiles were retained
just fine during the upgrade, however, I recreated them anyway to rule that
out as being the culprit.

Examples:

What was working under 6.60:

"C:\Program Files\WS_FTP Pro\ftp95pro.exe" -i original.ini -p zip -s
zip:'GPKI.KIMR002.SP.DWN1' -d local:download.dat

What is now not working under 7.02 and corresponding log files:

Attempt #1  (This attempt was performed with no changes to the existing
profile where the password is not saved as we cannot hard code mainframe
passwords for security reasons. I was never prompted for my password as I
should have been according to documentation.)

"C:\Program Files\WS_FTP Pro\wsftppro.exe" -s
original!zip:'GPKI.KIMR002.SP.DWN1' -d local:download.dat
"C:\Program Files\WS_FTP Pro\wsftppro.exe" -s
MySites!zip:'GPKI.KIMR002.SP.DWN1' -d local:download.dat

 <<Attempt #1.log>> 

Attempt #2  (During this attempt, I saved the mainframe password in the
profile so I could at least log on to the remote server. However, there was
a failure getting to the source file which I have verified is there and
transferred manually with WS_FTP.)

"C:\Program Files\WS_FTP Pro\wsftppro.exe" -s
MySites!zip:'GPKI.KIMR002.SP.DWN1' -d local:download.dat

 <<Attempt #2.log>> 

Attachment: WS_FTPSession.log
Description: Attempt #1.log

Attachment: WS_FTPSession.log
Description: Attempt #2.log

Reply via email to