lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MVS FTP interface (Was: Re: LYNX-DEV Two bugs in Lynx)


From: Foteos Macrides
Subject: Re: MVS FTP interface (Was: Re: LYNX-DEV Two bugs in Lynx)
Date: Thu, 20 Feb 1997 15:32:49 -0500 (EST)

"Jim Spath (Webmaster Jim)" <address@hidden> wrote:
>On Thu, 20 Feb 1997, Foteos Macrides wrote:
>> >> >> >BTW, does anyone know an MVS anonymous FTP server I can test on?
>> >> >>        ftp://epaibm.rtpnc.epa.gov/
>> >I've just run a trace to the above address, and it appears one
>> >problem is the use of slashes.
>> >...
>> >MVS has no concept of subdirectories (as we know them), and the 
>> >only "CWD" command that would apply would be to set the prefix.
>>      You've shown a trace which confirms that, in the absence of
>> adequately successful support for MVS ftp servers, setting it to
>> "generic" will ensure a clean failure.
>
>Yes, it does fail.  What do we need to do to make this work?
>I apologize if this in the archives.  Here's some standard ftp
>commands to that system:
>
>/jes> ftp epaibm.rtpnc.epa.gov
>Connected to epaibm.rtpnc.epa.gov.
>220-#TCPFTP IBM MVS V3R1 at EPAIBM.RTPNC.EPA.GOV, 12:53:53 on 1997/02/20
>220 Connection will close if idle for more than 15 minutes.
>Name (epaibm.rtpnc.epa.gov:jspath): XXX
>230 XXX is logged on.  Working directory is "XXXYYYY.".
>ftp> cd PUBLIC.
>250 "'XXXYYYY.PUBLIC.'" is working directory name prefix
>ftp> cd 'PUBLIC.'
>250 "'PUBLIC.'" is working directory name prefix
>ftp> dir
>200 Port request OK.
>125 List started OK.
>Volume Unit    Referred Ext Used Recfm Lrecl BlkSz Dsorg Dsname
>OVH101 3390   1997/02/20  1   60  FB      80 23200  PO  MICSFILE.CLIST
>OVH131 3390   1997/02/20  1    1  FB      80 23200  PO  MICSFILE.MSGS
>...
>
>My presumption is that Lynx needs to know:
>
>*) what commands are proper for this type system
>
>*) how to display the dataset names as possible links
>
>*) how to tell text from binary
>
>*) how to retrieve these files (e.g., file type, retrieval commands, etc.) 

        My advice is still to study and understand the ftp gateway
support for CMS/VM servers first, since that support appears to have
been fully successful, and has a lot of what you need to support MVS.

        Also, make sure you understand URL syntax, and use that.  The
gateway should translate the URLs, and then use the MVS file system
syntax in it's communications with the MVS server.  Don't resort to
bastard URLs. (That's what a "gateway" is.  It translates between
different communication protocols and syntaxes.)

        MVS servers do adhere, correctly, to the ftp protocol, so
track down the ftp RFCs, and make sure you've studied and understand
those as well.

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]