Re: Mainframe FTP

On Tue, 4 Sep 2007 22:17:15 -0400, John S. Giltner, Jr. wrote:

Bill Godfrey wrote:
On Tue, 4 Sep 2007 14:21:18 -0500, McKown, John wrote:

-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@xxxxxxxxxxx] On Behalf Of Philip Miscione
Sent: Tuesday, September 04, 2007 2:07 PM
To: IBM-MAIN@xxxxxxxxxxx
Subject: Mainframe FTP
Sensitivity: Private

I am trying to figure out where or how the port command gets built in
this FTP job, I want to change it to

PORT 161,221,112,120,8,158

I can't find it anywhere in the JCL or sysin ?

331 Password required for mainframe.

EZA1701I >>> PASS

230 User mainframe logged in.

EZA1460I Command:

EZA1736I get deposits.txt 'P.SXA2X0.XD01.XXXX.BDEPOS(0)' (r

EZA1701I >>> PORT 161,221,112,20,8,158

200 PORT command successful.

TIA
That is dynamically generated by the FTP server. I am not aware of any
way to "hard code" it to some other value. In fact, it may (and likely
will) vary over time. This is a part of the "passive" or "firewall
friendly" protocol for ftp.


The PORT command is not used in "passive" ftp.
In "passive" ftp, the port information for the data connection is passed from
server to client in the "227 Entering passive mode" message.

Bill


When using passive FTP both sides tell the other side what port it will
use. The client tells the server what port it will use to initiate the
connection on the PASV command, the server tells the client in "227"
message.


The PASV command has no operands. At the time the server sends the "227"
message to the client, the server has no information about the client port. It
won't have that information until the client actually connects to the port
specified in the "227" message.

I should say that the "PORT" command can in fact be used in "passive" ftp,
but that is for transfers between two servers A and B controlled by client C. I
don't think that's what this thread is about, although there's not enough
information in the OP's message for me to be completely sure.

Bill

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • RE: Telnet/ftp problems SBS2000
    ... Please make sure your client computers are configured as both Firewall ... will find two options "Enable folder view for FTP sites" and "Use Passive ... that the control connection has been successfully established, ... (other than port 21) ...
    (microsoft.public.windows.server.sbs)
  • Re: Telnet/ftp problems SBS2000
    ... the client became desperate so we had to find a ... the software communicates on port 308. ... So I don't really know if telnet or ftp ... the connection can be established ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft FTP Server problem on W2K?
    ... I have technical responsibility for this FTP implementation, ... Since PASV voids PORT, the client side ... connect to the server from" isn't implied by the text of the RFC. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ftp problem
    ... The remote end will have to have port 20 and 21 ... Check it with another ftp site to make sure. ... The remote FTP server is on a remote ... >> a client to be able to ftp out. ...
    (microsoft.public.windows.server.sbs)
  • Re: iptables blocking ftp clients
    ... > I am running a zope FTP server on port 8021 on a host that is running ... > access the server fine, so there is no problem with the server. ... specific high port, namely 8021 - how else can they use your FTP service? ... ports for a _client_, not a server. ...
    (comp.os.linux.security)