FileZilla client 3.44.2 and z/OS-SFTP dataset support

Moderator: Project members

Post Reply
Message
Author
fagu
500 Command not understood
Posts: 1
Joined: 2019-09-12 08:57
First name: Gustav
Last name: Fagerholm

FileZilla client 3.44.2 and z/OS-SFTP dataset support

#1 Post by fagu » 2019-09-12 11:21

Hej!

FileZilla client V3.44.2 still have "old" problem with supporting z/OS-SFTP and z/OS-MVS datasets.

It look like the handling of "//..." is the problem, FileZilla is doing "//..." ==> "/..." and we have a problem.

Many z/OS customers use and require SFTP instead of unsecure FTP. Though FTPS (FTP-over-SSL/TLS) is easily implemented with z/OS-PAGENT services, customers usually do not want the "extra" work installing on LUW the FTPS-server and supporting certificate maintenamce.

Dovetailed Technologies https://dovetail.com/solutions.html and SSH Communications Security https://www.ssh.com/manuals/server-zos- ... rison.html when installed on z/OS Mainframe do make direct access to z/OS-MVS datasets possible also with SFTP.

IBM z/OS-OpenSSH is part of z/OS base services, but unfortunately only support z/OS-UNIX files, not z/OS-MVS datasets.

Same problem is also with MFT support of z/OS-SFTP dataset services...

In this case we use Dovetailed Technologies Co:Z SFTP services, and I'll refer to this SW product, and FileZilla client and PuTTY-psftp as reference.

Dovetailed Technologies
==>
"Co:Z SFTP is a port of OpenSSH SFTP for z/OS which adds support for z/OS datasets, catalogs, spool files, SMF, etc. This product is designed to work with secure SSH connections provided by z/OS OpenSSH...".
==>
z/OS OpenSSH is now part of z/OS basic installation, but IBM unfortunately only have support for z/OS-UNIX files, not z/OS-MVS datasets.


...z/OS predefined

BROWSE /u/fagu/.ssh/sftp-server.rc Line 0000000012 Col
Command ===> Scroll ==
export SFTP_ZOS_OPTIONS="mode=text,servercp=ibm-1143,clientcp=iso8859-15"
export SFTP_ZOS_INITIAL_DIR=//FAGU.ZOS
******************************** Bottom of Data *************************

...FileZilla client log
==>
Status: Connecting to 10.10.10.100...
Status: Connected to 10.10.10.100
Status: Retrieving directory listing...
Status: Listing directory //FAGU.ZOS
Status: Directory listing of "/FAGU.ZOS" successful
Status: Connecting to 10.10.10.100...
Status: Connecting to 10.10.10.100...
Status: Connected to 10.10.10.100
Status: Connected to 10.10.10.100
Status: Starting download of /FAGU.ZOS/B190910.ROAMING.TXT
Status: Starting download of /FAGU.ZOS/B190911.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190911.ROAMING.TXT"
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190910.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190911.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190911.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190911.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190910.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190910.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190910.ROAMING.TXT"
Error: /FAGU.ZOS/B190910.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Error: /FAGU.ZOS/B190911.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190910.ROAMING.TXT
Status: Starting download of /FAGU.ZOS/B190911.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190910.ROAMING.TXT"
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190911.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190910.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190910.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190910.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190911.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190911.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190911.ROAMING.TXT"
Error: /FAGU.ZOS/B190910.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190910.ROAMING.TXT
Error: /FAGU.ZOS/B190911.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190911.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190910.ROAMING.TXT"
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190911.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190910.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190910.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190910.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190911.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190911.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190911.ROAMING.TXT"
Error: /FAGU.ZOS/B190910.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Error: /FAGU.ZOS/B190911.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Disconnected from server


...or just one dataset

Status: Connecting to 10.10.10.100...
Status: Connected to 10.10.10.100
Status: Retrieving directory listing...
Status: Listing directory //FAGU.ZOS
Status: Directory listing of "/FAGU.ZOS" successful
Status: Connecting to 10.10.10.100...
Status: Connected to 10.10.10.100
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed
Status: Starting download of /FAGU.ZOS/B190912.ROAMING.TXT
Command: cd "/FAGU.ZOS"
Error: Directory /FAGU.ZOS: no such file or directory
Command: mtime "/FAGU.ZOS/B190912.ROAMING.TXT"
Error: get attrs for /FAGU.ZOS/B190912.ROAMING.TXT: no such file or directory
Command: get "/FAGU.ZOS/B190912.ROAMING.TXT" "C:\ftp\zOS\lpar\MGET\B190912.ROAMING.TXT"
Error: /FAGU.ZOS/B190912.ROAMING.TXT: open for read: no such file or directory
Error: File transfer failed


...PuTTY ... "psftp" is more fléxible and can send commands to z/OS Co:Z SFTP server that change LRECL, encoding, ...
...this command should work and be supported in FileZilla Client:
ls /+mode=text,servercp=ibm-1143,clientcp=iso8859-15
ls /+lrecl=300,recfm=fb,space=cyl.100.100,release
cd //fagu.zos
lcd C:\ftp\zOS\lpar

Remote working directory is //FAGU.ZOS
psftp>
psftp> lcd C:\ftp\zOS\lpar
New local directory is C:\ftp\zOS\lpar
psftp> pwd
Remote directory is //FAGU.ZOS
psftp> lpwd
Current local directory is C:\ftp\zOS\lpar
psftp> dir
Listing directory //FAGU.ZOS
Volume Referred Ext Tracks Used Recfm Lrecl BlkSz Dsorg Dsname
BEBA13 2019/09/06 1 4830 4830 FB 300 27900 PS FAGU.ZOS.B190831.ROAMING.TXT
BEBA05 2019/09/06 2 5250 5245 FB 300 27900 PS FAGU.ZOS.B190901.ROAMING.TXT
BEBA18 2019/09/06 1 4905 4903 FB 300 27900 PS FAGU.ZOS.B190902.ROAMING.TXT
BEBA34 2019/09/06 1 4710 4704 FB 300 27900 PS FAGU.ZOS.B190903.ROAMING.TXT
BEBA28 2019/09/06 1 4785 4784 FB 300 27900 PS FAGU.ZOS.B190904.ROAMING.TXT
BEBA39 2019/09/06 1 4905 4903 FB 300 27900 PS FAGU.ZOS.B190905.ROAMING.TXT
BEBA01 2019/09/06 1 5385 5384 FB 300 27900 PS FAGU.ZOS.B190906.ROAMING.TXT
psftp>
psftp> mget //FAGU.ZOS.B*.ROAMING.TXT
ignoring potentially dangerous server-supplied filename '...'
//FAGU.ZOS.B*.ROAMING.TXT: nothing matched
psftp>
psftp> mget B*.ROAMING.TXT
remote://FAGU.ZOS.B190831.ROAMING.TXT => local:B190831.ROAMING.TXT
remote://FAGU.ZOS.B190901.ROAMING.TXT => local:B190901.ROAMING.TXT
remote://FAGU.ZOS.B190902.ROAMING.TXT => local:B190902.ROAMING.TXT
remote://FAGU.ZOS.B190903.ROAMING.TXT => local:B190903.ROAMING.TXT
remote://FAGU.ZOS.B190904.ROAMING.TXT => local:B190904.ROAMING.TXT
remote://FAGU.ZOS.B190905.ROAMING.TXT => local:B190905.ROAMING.TXT
remote://FAGU.ZOS.B190906.ROAMING.TXT => local:B190906.ROAMING.TXT
psftp>

...next some explanation from the vendor
==>
----------------------------------------------------------------------
dovetail.com/tickets/
...some part and modified answers to my question
...NOTE that same proble is with "get in out"
==>
The answer to your question is that the "mget" command works very differently
under the FTP protocol and the SFTP protocol. Under POSIX file systems, these
differences don't show up very often, but under the data set space they can
cause confusing results.

I'll try to explain what's going on and then offer a suggestion which may help
with your original question.

=========== What is happening =============

Under FTP, the client sends the mget command along with its argument to the
server to process, so the z/OS FTP server sees this command:

mget 'FAGU.ZOS.B*.ROAMING.TXT'

The z/OS FTP server then does a catalog search using the quoted string, finds
the matching datasets and returns them to the client.

Under SFTP, the client (psftp) reads the command:

mget //FAGU.ZOS.B*.ROAMING.TXT

And -- before sending anything to the server -- determines what directory to ask
the SFTP server to list. Once the client gets the directory listing, it uses a
file "globbing" (filtering) technique to match the returned files to the file
pattern. When the client has the matched file list, it sends back one read
request at a time for each matched file.

So in this case, the psftp client strips the entire suffix of
"FAGU.ZOS.B*.ROAMING.TXT" off the command and sends just the remaining
directory to the server. It should actually send "//", but psftp only sends a
single "/" in this case because it believes the second "/" is redundant. So on
line 180 of your log, we see this:

[26.242] opendir "/"

The Co:Z SFTP server simply returns the contents of the root directory (lines
186-205):

[26.373] debug1: request 256: count= 0 name= "." long_name= "drwxr-xr-x 15
BPXROOT OMVSGRP 8192 Sep 13 2018 ."
[26.373] debug1: request 256: count= 1 name= ".." long_name= "drwxr-xr-x 15
BPXROOT OMVSGRP 8192 Sep 13 2018 .."
[26.373] debug1: request 256: count= 2 name= "etc" long_name= "lrwxrwxrwx 1
BPXROOT OMVSGRP 12 Mar 20 2018 etc"
[26.373] debug1: request 256: count= 3 name= "usr" long_name= "drwxr-xr-x 10
BPXROOT OMVSGRP 8192 Sep 26 2017 usr"
[26.373] debug1: request 256: count= 4 name= "var" long_name= "lrwxrwxrwx 1
BPXROOT OMVSGRP 12 Mar 20 2018 var"
[26.373] debug1: request 256: count= 5 name= "Service" long_name= "drwxr-xr-x
2 BPXROOT OMVSGRP 8192 Mar 26 2018 Service"
[26.373] debug1: request 256: count= 6 name= "u" long_name= "drwxr-xr-x 79
BPXROOT SYSTT 8192 May 8 15:53 u"
[26.373] debug1: request 256: count= 7 name= "lib" long_name= "drwxr-xr-x 2
BPXROOT OMVSGRP 8192 Mar 1 2018 lib"
[26.374] debug1: request 256: count= 8 name= "bin" long_name= "drwxr-xr-x 4
BPXROOT OMVSGRP 16384 Mar 20 11:26 bin"
[26.374] debug1: request 256: count= 9 name= "samples" long_name= "drwxr-xr-x
4 BPXROOT OMVSGRP 8192 Jan 10 2019 samples"
[26.374] debug1: request 256: count= 10 name= "global" long_name= "drwxr-xr-x
2 BPXROOT OMVSGRP 8192 Sep 26 2017 global"
[26.374] debug1: request 256: count= 11 name= "SYSTEM" long_name= "drwxr-xr-x
6 BPXROOT OMVSGRP 8192 Sep 26 2017 SYSTEM"
[26.374] debug1: request 256: count= 12 name= "opt" long_name= "drwxr-xr-x 2
BPXROOT OMVSGRP 8192 Sep 26 2017 opt"
[26.374] debug1: request 256: count= 13 name= "dev" long_name= "lrwxrwxrwx 1
BPXROOT OMVSGRP 12 Mar 20 2018 dev"
[26.374] debug1: request 256: count= 14 name= "tmp" long_name= "lrwxrwxrwx 1
BPXROOT OMVSGRP 12 Mar 20 2018 tmp"
[26.374] debug1: request 256: count= 15 name= "..." long_name= "dr-xr-xr-x 2
BPXROOT OMVSGRP 8192 Sep 26 2017 ..."
[26.374] debug1: request 256: count= 16 name= "Srvc" long_name= "drwxr-xr-x 4
BPXROOT OMVSGRP 8192 Mar 26 2018 Srvc"
[26.374] debug1: request 256: count= 17 name= "tc" long_name= "drwxr-xr-x 13
BPXROOT OMVSGRP 8192 Oct 25 2018 tc"
[26.374] debug1: request 256: count= 18 name= "smpnts" long_name= "drwxrwxr-x
2 BPXROOT OMVSGRP 0 Mar 27 2018 smpnts"
[26.374] debug1: request 256: count= 19 name= "U" long_name= "lrwxrwxrwx 1
BPXROOT OMVSGRP 2 May 14 2018 U"

The psftp client tries to match these files to the globbing filter of
"FAGU.ZOS.B*.ROAMING.TXT", but none match so the client issues the message
that you see:

//FAGU.ZOS.B*.ROAMING.TXT: nothing matched

If you were using a different client like OpenSSH sftp, it would do something
similar, but would send the directory "//" instead of "/". However, even this
won't work with Co:Z because it isn't valid to list the entire catalog - you
must supply at least one qualifier. In that case, you would see an error on the
server side like this:

ZosDir[E]: Invalid dsn or catalog search: ""

Given the differences between the two protocols, you can see that SFTP can
potentially create a lot more network traffic in these cases than FTP because
the server does not get to do any filtering of results.

=========== What you can do =============

You should be able to get close to what you want by changing your original
"mget" request to the following:

mget //FAGU.ZOS/B*.ROAMING.TXT

Note that I've replaced the "." between ZOS and B with a "/". By doing this, the
psftp client will send the data set directory "FAGU.ZOS" to the server which
will return just the names below that level. The client will then match those
results with the globbing filter: "B*.ROAMING.TXT" and you will get the results
you are looking for. Or you can can use the other technique, which is to change
to the data set directory above the filter and issue the relative mget command:

cd //FAGU.ZOS
mget B*.ROAMING.TXT

Please also note that when the client does the file globbing, it is case
sensitive! So this command will work:

mget //FAGU.ZOS/B*.ROAMING.TXT

but this will not:

mget //FAGU.ZOS/b*.roaming.txt

I apologize for the length of this answer, but I hope it explains what is going
on.

Issue History
Date Modified Username Field Change
======================================================================
...
2019-09-06 07:02 Co:Zsupport
======================================================================



Remote working directory is //FAGU.ZOS
psftp>
psftp> cd //FAGU.ZOS
Remote directory is now //FAGU.ZOS
psftp> lcd C:\ftp\zOS\lpar\MGET
New local directory is C:\ftp\zOS\lpar\MGET
psftp>
psftp> ls /+mode=text,servercp=ibm-1143,clientcp=iso8859-15
Listing directory /+mode=text,servercp=ibm-1143,clientcp=iso8859-15
clientcp=iso8859-15
mode=text
servercp=ibm-1143
psftp> ls /+lrecl=300,recfm=fb,space=cyl.100.100,release
Listing directory /+lrecl=300,recfm=fb,space=cyl.100.100,release
lrecl=300
recfm=fb
release
space=cyl.100.100
psftp> ls /+
Listing directory /+
.newoption=
clientcp=iso8859-15
error.log
gdgnt
loglevel=I
lrecl=300
mode=text
recfm=fb
release
servercp=ibm-1143
space=cyl.100.100
trim
psftp>
psftp> pwd
Remote directory is //FAGU.ZOS
psftp> lpwd
Current local directory is C:\ftp\zOS\lpar\MGET
psftp>
psftp> dir
Listing directory //FAGU.ZOS
Volume Referred Ext Tracks Used Recfm Lrecl BlkSz Dsorg Dsname
BEBA05 2019/09/12 1 5835 5826 FB 300 27900 PS FAGU.ZOS.B190910.ROAMING.TXT
BEBA40 2019/09/12 1 7050 7040 FB 300 27900 PS FAGU.ZOS.B190911.ROAMING.TXT
BEBA44 2019/09/12 2 6555 6555 FB 300 27900 PS FAGU.ZOS.B190912.ROAMING.TXT
psftp>
psftp> ls
Listing directory //FAGU.ZOS
Volume Referred Ext Tracks Used Recfm Lrecl BlkSz Dsorg Dsname
BEBA05 2019/09/12 1 5835 5826 FB 300 27900 PS FAGU.ZOS.B190910.ROAMING.TXT
BEBA40 2019/09/12 1 7050 7040 FB 300 27900 PS FAGU.ZOS.B190911.ROAMING.TXT
BEBA44 2019/09/12 2 6555 6555 FB 300 27900 PS FAGU.ZOS.B190912.ROAMING.TXT
psftp>
psftp> mget //FAGU.ZOS/B*.ROAMING.TXT
remote://FAGU.ZOS.B190910.ROAMING.TXT => local:B190910.ROAMING.TXT
...osv jne

User avatar
botg
Site Admin
Posts: 32423
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: FileZilla client 3.44.2 and z/OS-SFTP dataset support

#2 Post by botg » 2019-09-12 12:39

FileZilla client V3.44.2 still have "old" problem with supporting z/OS-SFTP and z/OS-MVS datasets.

It look like the handling of "//..." is the problem, FileZilla is doing "//..." ==> "/..." and we have a problem.
That's not going to change, would cause too much breakage to support the occasional freak server.

In particular, there is no way to distinguish "/" (the absolute root) from "/" (the directory with the empty name relative to the root) which would have to be distinct.

Please update your SFTP server software to one that translates the exotic native path syntax of the server system into a sane, POSIX(-like) path syntax.

For example your server could easily map "//..." to something like "/doubleslashtripledotprefix" that is understood by all clients, without having to deal with platform-specific oddities client-side.


...PuTTY ... "psftp" is more fléxible and can send commands to z/OS Co:Z SFTP server that change LRECL, encoding, ...
...this command should work and be supported in FileZilla Client:
ls /+mode=text,servercp=ibm-1143,clientcp=iso8859-15
ls /+lrecl=300,recfm=fb,space=cyl.100.100,release
According to the SFTP specifications, SSH_FXP_OPENDIR only accepts a filename. Your server interpreting parts of the filename as something other than a filename is in violation of the protocol. For setting custom parameters the SSH_FXP_EXTENDED command needs to be used.
psftp> ls /+lrecl=300,recfm=fb,space=cyl.100.100,release
Listing directory /+lrecl=300,recfm=fb,space=cyl.100.100,release
lrecl=300
recfm=fb
release
Based on this output, "lrecl=300", "recfm=fb" and "release" are actual files in the directory "/+lrecl=300,recfm=fb,space=cyl.100.100,release". The protocol is clear on that.
psftp> ls
Listing directory //FAGU.ZOS
Volume Referred Ext Tracks Used Recfm Lrecl BlkSz Dsorg Dsname
Interesting, there is a file with the longname "Volume Referred Ext Tracks Used Recfm Lrecl BlkSz Dsorg Dsname" Very peculiar, I wonder what the corresponding filename and attrs are to this longname.

An "mget *" would actually try to download that.

The answer to your question is that the "mget" command works very differently
under the FTP protocol and the SFTP protocol.
[...]
Under FTP, the client sends the mget command along with its argument to the
server to process, so the z/OS FTP server sees this command:

mget 'FAGU.ZOS.B*.ROAMING.TXT'
That's just wrong. mget is not part of the protocols to begin with. It is a client-side command implemented entirely in the client. What the command does differs from client to client.

Post Reply