Re: MPE FTP transfer into HFS namespace - Hewlett Packard

This is a discussion on Re: MPE FTP transfer into HFS namespace - Hewlett Packard ; alas, it appears that james has indeed hit a bug in mpe's ftp for mget :-( -------------------- :# build some empty test hfs files and prove they exist : listfile ./TEST.1@,2 PATH= /SYS/PUB/ CODE ------------LOGICAL RECORD----------- ----SPACE---- FILENAME SIZE TYP ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: MPE FTP transfer into HFS namespace

  1. Re: MPE FTP transfer into HFS namespace

    alas, it appears that james has indeed hit a bug in mpe's ftp for mget :-(

    --------------------
    :# build some empty test hfs files and prove they exist
    : listfile ./TEST.1@,2
    PATH= /SYS/PUB/

    CODE ------------LOGICAL RECORD----------- ----SPACE---- FILENAME
    SIZE TYP EOF LIMIT R/B SECTORS #X MX

    128W FB 0 1023 1 0 0 * TEST.1.1
    128W FB 0 1023 1 0 0 * TEST.1.2
    128W FB 0 1023 1 0 0 * TEST.1.3

    :# amber is a redhat linux server
    :# show that put works
    :# then show that mput works for hfs files from mpe to linux
    : ftp amber

    File Transfer Protocol [A0012H14] (C) Hewlett-Packard Co. 2002 [PASSIVE
    SUPPORT]

    220 (vsFTPd 2.0.1)
    Connected to amber (1.1.1.1). (FTPINFO 40)
    Name(manager): root
    331 Please specify the password.
    Password:
    230 Login successful.
    Remote system type is UNIX
    ftp> dir
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    drwxr-xr-x 2 0 0 4096 Sep 17 2007 junk
    226 Directory send OK.
    635 bytes received in 0.04 seconds (17.23 Kbytes/sec)
    ftp> cd junk
    250 Directory successfully changed.
    ftp> dir
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    226 Directory send OK.
    0 bytes received in 0.00 seconds (NaN Kbytes/sec)
    ftp> put ./TEST.1.1
    200 PORT command successful. Consider using PASV.
    150 Ok to send data.
    226 File receive OK.
    0 bytes sent in 1.99 seconds (0.00 Kbytes/sec)
    ftp> dir
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    -rw-r--r-- 1 0 0 0 Sep 26 19:02 TEST.1.1
    226 Directory send OK.
    66 bytes received in 0.00 seconds (+INF Kbytes/sec)
    ftp> mput ./TEST.1*
    mput ./TEST.1.1? y
    200 PORT command successful. Consider using PASV.
    150 Ok to send data.
    226 File receive OK.
    0 bytes sent in 2.00 seconds (0.00 Kbytes/sec)
    mput ./TEST.1.2? y
    200 PORT command successful. Consider using PASV.
    150 Ok to send data.
    226 File receive OK.
    0 bytes sent in 1.99 seconds (0.00 Kbytes/sec)
    mput ./TEST.1.3? y
    200 PORT command successful. Consider using PASV.
    150 Ok to send data.
    226 File receive OK.
    0 bytes sent in 2.00 seconds (0.00 Kbytes/sec)
    ftp> dir
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    -rw-r--r-- 1 0 0 0 Sep 26 19:03 TEST.1.1
    -rw-r--r-- 1 0 0 0 Sep 26 19:03 TEST.1.2
    -rw-r--r-- 1 0 0 0 Sep 26 19:03 TEST.1.3
    226 Directory send OK.
    198 bytes received in 0.00 seconds (193.36 Kbytes/sec)
    ftp> quit
    221 Goodbye.

    :# with the files on amber, purge then from the mpe system
    :# and try to mget them back
    : purge ./TEST.1@
    3 files matched
    Continue PURGE ? (YES/NO)y
    3 selected. 3 succeeded. 0 failed.
    : ftp amber

    File Transfer Protocol [A0012H14] (C) Hewlett-Packard Co. 2002 [PASSIVE
    SUPPORT]

    220 (vsFTPd 2.0.1)
    Connected to amber (1.1.1.1). (FTPINFO 40)
    Name(manager): root
    331 Please specify the password.
    Password:
    230 Login successful.
    Remote system type is UNIX
    ftp> cd junk
    250 Directory successfully changed.
    ftp> mget ./TEST.1*
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    226 Directory send OK.
    30 bytes received in 0.00 seconds (14.65 Kbytes/sec)
    mget TEST.1.1? y
    The group name provided did not start with an alphabetic character.
    (FILE SYSTEM ERROR -117)
    mget TEST.1.2? y
    mget TEST.1.3? y
    ftp> quit
    221 Goodbye.

    END OF PROGRAM
    : listfile ./TEST.1@,2
    No match found for the pathname. (CIWARN 9043)

    :# will it work to retrieve them one by one?
    : ftp amber

    File Transfer Protocol [A0012H14] (C) Hewlett-Packard Co. 2002 [PASSIVE
    SUPPORT]

    220 (vsFTPd 2.0.1)
    Connected to amber (1.1.1.1). (FTPINFO 40)
    Name(manager): root
    331 Please specify the password.
    Password:
    230 Login successful.
    Remote system type is UNIX
    ftp> cd junk
    250 Directory successfully changed.
    ftp> get ./TEST.1.1
    200 PORT command successful. Consider using PASV.
    150 Opening BINARY mode data connection for ./TEST.1.1 (0 bytes).
    226 File send OK.
    0 bytes received in 0.00 seconds (0.00 Kbytes/sec)
    ftp> get ./TEST.1.2
    200 PORT command successful. Consider using PASV.
    150 Opening BINARY mode data connection for ./TEST.1.2 (0 bytes).
    226 File send OK.
    0 bytes received in 0.00 seconds (NaN Kbytes/sec)
    ftp> get ./TEST.1.3
    200 PORT command successful. Consider using PASV.
    150 Opening BINARY mode data connection for ./TEST.1.3 (0 bytes).
    226 File send OK.
    0 bytes received in 0.00 seconds (NaN Kbytes/sec)
    ftp> quit
    221 Goodbye.

    END OF PROGRAM
    Mombi: listfile ./TEST.1@,2
    PATH= /SYS/PUB/

    CODE ------------LOGICAL RECORD----------- ----SPACE---- FILENAME
    SIZE TYP EOF LIMIT R/B SECTORS #X MX

    80B FA 0 204800 1 0 0 8 TEST.1.1
    80B FA 0 204800 1 0 0 8 TEST.1.2
    80B FA 0 204800 1 0 0 8 TEST.1.3
    --------------------

    some additional testing showed that the result are identical for hp-ux BUT
    mget of hfs file from another mpe system works fine.

    this is NOT something we want to discover this late in mpe's supported life
    :-(

    I strongly encourage *everyone* with a software support contract (including
    folks with contracts with someone other than hp) to call this problem in.
    I'm concerned that hp will need some convincing to repair this problem.
    additionally, I'm worried that even if the problem is fixed it may take some
    time to get it gr'd. so if you call this in -- you've got to be willing to
    apply a beta patch!

    (I think I've exhaustively shown that it's easy to patch ftp. It's just as
    easy to backdate ftp. remember that quick backup?? just restore it....and
    your old ftp is back)

    for james -- the best advice I can give is to get your files one at a time.
    hopefully this is only a workaround.

    - d

    ---
    Donna Hofmeister
    Allegro Consultants, Inc.
    408-252-2330


    > -----Original Message-----
    > From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU] On
    > Behalf Of Bob Schlosser
    > Sent: Friday, September 26, 2008 11:53 AM
    > To: HP3000-L@RAVEN.UTC.EDU
    > Subject: Re: [HP3000-L] MPE FTP transfer into HFS namespace
    >
    > James
    >
    > I do not believe that t is FPT barking at you but rather MPE itself.
    > Look at the file name it is trying to save TEST.1.1 and that looks a
    > lot like filename.group.account. I do not know how to fix this except
    > to transfer each file separately (get rid of mget) and specify the
    > target
    > file name as ./TEST.1.1 or what ever you need.
    >
    > HTH
    >
    > Robert Schlosser
    > Global Business Systems
    > Premier Farnell plc
    > T 864 487-1362
    > F 864.487.1904
    > E rschlosser@premierfarnell.com
    > Your #1 source for RoHS compliant products & information.
    > www.newark.com
    >
    >
    >
    > -----Original Message-----
    > From: HP-3000 Systems Discussion [mailto:HP3000-L@RAVEN.UTC.EDU]On
    > Behalf Of James B. Byrne
    > Sent: Friday, September 26, 2008 2:46 PM
    > To: HP3000-L@RAVEN.UTC.EDU
    > Subject: Re: [HP3000-L] MPE FTP transfer into HFS namespace
    >
    >
    > First of all, thank you Donna for excellent instructions and for the
    > time
    > that you took to do this (even if as you claim it was only 5 minutes it
    > was worth an eternity to me). Your message will remain an invaluable
    > aide
    > memoire for this process.
    >
    > However, the update has not changed the behaviour of the ftp client:
    >
    > :ftp
    > File Transfer Protocol [A0012H14] (C) Hewlett-Packard Co. 2002 [PASSIVE
    > SUPPORT]
    > ftp> open 192.168.219.1
    > 220 (vsFTPd 2.0.5)
    > Connected to 192.168.219.1. (FTPINFO 40)
    > Name(manager): anonymous
    > 331 Please specify the password.
    > Password:
    > 230 Login successful.
    > Remote system type is UNIX
    > ftp> byte
    > 200 Switching to Binary mode.
    > ftp> cd ftp-drop
    > 250 Directory successfully changed.
    > ftp> dir
    > 200 PORT command successful. Consider using PASV.
    > 150 Here comes the directory listing.
    > -rw-r----- 1 14 50 506740992 Sep 26 08:07 STDHAL.1.1
    > -rw-r----- 1 14 50 325265920 Sep 26 08:19 STDHAL.2.1
    > -rw-r----- 1 14 50 561713920 Sep 26 08:41 STDHAL.3.1
    > -rw-r----- 1 14 50 564188160 Sep 26 09:03 STDHAL.4.1
    > -rw-r----- 1 14 50 9747456 Sep 25 18:03 TEST.1.1
    > -rw-r----- 1 14 50 18894848 Sep 25 18:04 TEST.2.1
    > -rw-r----- 1 14 50 7290624 Sep 25 18:04 TEST.3.1
    > -rw-r----- 1 14 50 8643840 Sep 25 18:04 TEST.4.1
    > 226 Directory send OK.
    > 540 bytes received in 0.06 seconds (8.11 Kbytes/sec)
    > ftp> mget ./TEST*
    > 200 PORT command successful. Consider using PASV.
    > 150 Here comes the directory listing.
    > 226 Directory send OK.
    > 40 bytes received in 0.04 seconds (1.03 Kbytes/sec)
    > mget TEST.1.1? y
    > The group name provided did not start with an alphabetic character.
    > (FILE SYSTEM ERROR -117)
    >
    > Any ideas?


    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


  2. Re: MPE FTP transfer into HFS namespace

    On Fri, September 26, 2008 15:41, donna hofmeister wrote:
    > alas, it appears that james has indeed hit a bug in mpe's ftp for mget :-(


    :ftp
    File Transfer Protocol [A0012H14] (C) Hewlett-Packard Co. 2002 [PASSIVE
    SUPPORT]
    ftp> open 192.168.219.1
    220 (vsFTPd 2.0.5)
    Connected to 192.168.219.1. (FTPINFO 40)
    Name(manager): anonymous
    331 Please specify the password.
    Password:
    230 Login successful.
    Remote system type is UNIX
    ftp> byte
    200 Switching to Binary mode.
    ftp> cd ftp-drop
    250 Directory successfully changed.
    ftp> dir
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    -rw-r--r-- 1 14 50 506740992 Sep 26 08:07 STDHAL.1.1
    -rw-r--r-- 1 14 50 325265920 Sep 26 08:19 STDHAL.2.1
    -rw-r--r-- 1 14 50 561713920 Sep 26 08:41 STDHAL.3.1
    -rw-r--r-- 1 14 50 564188160 Sep 26 09:03 STDHAL.4.1
    -rw-r--r-- 1 14 50 9747456 Sep 25 18:03 TEST.1.1
    -rw-r--r-- 1 14 50 18894848 Sep 25 18:04 TEST.2.1
    -rw-r--r-- 1 14 50 7290624 Sep 25 18:04 TEST.3.1
    -rw-r--r-- 1 14 50 8643840 Sep 25 18:04 TEST.4.1
    226 Directory send OK.
    540 bytes received in 0.02 seconds (32.96 Kbytes/sec)
    ftp> mget ./TEST*1.1
    200 PORT command successful. Consider using PASV.
    150 Here comes the directory listing.
    226 Directory send OK.
    40 bytes received in 0.02 seconds (1.86 Kbytes/sec)
    mget TEST.1.1? y
    The group name provided did not start with an alphabetic character.
    (FILE SYSTEM ERROR -117)
    mget TEST.2.1? y
    mget TEST.3.1? y
    mget TEST.4.1? y
    ftp> get ./TEST.1.1 ./TEST.1.1
    200 PORT command successful. Consider using PASV.
    150 Opening BINARY mode data connection for ./TEST.1.1 (9747456 bytes).
    226 File send OK.
    9747456 bytes received in 13.69 seconds (695.43 Kbytes/sec)
    ftp>

    Moving files one at a time using get and prefacing the target name with ./
    evidently works. The lost of mput is an inconvenience, not a show
    stopper. I can script a dynamic command builder to handle the n file
    problem. The ftpcmd input file is built on the fly inside the job anyway.

    Sigh. I was working on this back in September of 2005 and was
    interrupted. It too bad that I did not get a few more weeks to work on it
    then otherwise this would have been discovered much earlier.

    That terrible word, if...

    Thanks for the help.

    Regards,

    --
    *** E-Mail is NOT a SECURE channel ***
    James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
    Harte & Lyne Limited http://www.harte-lyne.ca
    9 Brockley Drive vox: +1 905 561 1241
    Hamilton, Ontario fax: +1 905 561 0757
    Canada L8E 3C3

    * To join/leave the list, search archives, change list settings, *
    * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


+ Reply to Thread