I finally figured out the syntax to upload files to 'our' mainframe:
wsftppro -s local:e:\stat\test\ftp\upldsprd\*.dat -d "ptu4:- BDTB0.B1MXESD."
Thanks for useful hints.
| [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 07/13/2005 11:28 AM
|
To: WSFTP_Forum@list.ipswitch.com cc: Subject: RE: [WS_FTP Forum] Wildcard * |
Michael,
It would be worth to have a look into the mainframe FTP server log. This may give a clue on how it should be done on the FTP client side.
Regards,
Erich
-----Original Message-----
From: [EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 5:21 PM
To: [EMAIL PROTECTED]
Cc: WSFTP_Forum@list.ipswitch.com
Subject: RE: [WS_FTP Forum] Wildcard *
It worked fine with release 6.* (ftp95pro.exe) and stopped working since 7.* (wsftppro.exe). I suspect line command for mainframe is not working at all now.
| [EMAIL PROTECTED]
07/12/2005 02:20 PM | To: [EMAIL PROTECTED] cc: Subject: RE: [WS_FTP Forum] Wildcard * |
Michael,
Unfortunately I'm not a user of a current WS_FTP Pro version, but quite experienced with WS_FTP Server and with FTP on several platforms in general.
500 means: Syntax error, command unrecognized. This may include errors such as command line too long.
257 is rather a positive response and means: "PATHNAME" created. The "BDTB0.B1MXESD" seems to be something very platform specific and looks a little bit like coming from an MVS mainframe, which would be consistent with your term ".... connecting to mainframe".
In case the destination is really an MVS mainframe, you may be unable to use Unix style path names like ptu4:/, where "/" probably means the FTP root on destination ptu4. The MVS operating system may not know about an FTP root at all. I would like to propose to just omit the "/", or to enter the destination file name instead:
wsftppro -s local:e:\stat\test\ftp\upldsprd\stat003.dat -d ptu4:
or
wsftppro -s local:e:\stat\test\ftp\upldsprd\stat003.dat -d ptu4:STAT003.DAT
(or what other file name you would like to use, without running against MVS catalogue restrictions.)
The WS_FTP Pro GUI usually looks for the O/S of the remote server ('SYST') and adapts it's behaviour accordingly. Not so if you are using the command line, you have to do it yourself. This may explain the difference.
Please let me know of any progress with this.
Regards,
Erich
-----Original Message-----
From: [EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 7:43 PM
To: WSFTP_Forum@list.ipswitch.com
Cc: [EMAIL PROTECTED]
Subject: RE: [WS_FTP Forum] Wildcard *
Another problem connecting to mainframe (wildcard is removed).
wsftppro -s local:e:\stat\test\ftp\upldsprd\stat003.dat -d ptu4:/
The error:
[2005.07.12 13:37:18.219] 257 - BDTB0.B1MXESD
Failed to get destination folder
By the way, if I do it from the GUI it works.
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/12/2005 11:51 AM
Please respond to WSFTP_Forum
To: WSFTP_Forum@list.ipswitch.com
cc:
Subject: RE: [WS_FTP Forum] Wildcard *
Michael,
I rather suspect that the FTP server really didn't understand one of the generic FTP commands associated with this complex action (500 COMMAND UNRECOGNIZED). The FTP server log may enlighten this situation.
The next message ("Destination filename ...") comes from WS_FTP Pro and seems to be the desperate attempt of interpreting what could have happened here... Very misleading.
Regards,
Erich
-----Original Message-----
From: [EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 5:22 PM
To: WSFTP_Forum@list.ipswitch.com
Subject: [WS_FTP Forum] Wildcard *
When executing the line command (dos) (files are sent to the mainframe site ptu4):
wsftppro -s local:e:\stat\test\ftp\upldsprd\stat*.dat -d ptu4:/
the following error issued in 2006:
[2005.07.12 11:15:35.907] 500 COMMAND UNRECOGNIZED
Destination filename may not be specified when source filename contains wildcards ('*' or '?').
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/wsftp_forum%40list.ipswitch.com/
