× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Got it, but with one problem

When I enter ftp  my.ip.address.01  myport

I get back a list of all the parameters for ftp

It's the help window you usually request when you are not sure of the
parameters for a DOS command

If I ftp without the port I am prompted for my user Id and password
But then I am not on the right port
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Rich
Sent: Thursday, September 11, 2003 2:36 PM
To: Midrange Systems Technical Discussion
Subject: Re: Socket program problem

John Allen wrote:
> You say
> 
> Try something like this:
> 
> 1.  Start the server program on the iSeries.
> I did
> 
> 2.  Use telnet to connect to the server program.  For example:
>        telnet myas400 4543    (this assumes that your server program 
> runs on port 4543)
> I did (using my 400 and the correct port)
> 
> 3.  In telnet, send to the iSeries the command the PC would normally 
> send to initiate the file transfer.
> Not sure how to do this?

Here is an example.  I have a little socket program I wrote for testing. 
  It runs on port 3490.  It waits for connections and when it receives 
one sends a little message to the client.  Then it waits for the client 
to send something back.  Upon receiving something, it sends a little 
message saying it got it.  So I test it with telnet like so:

telnet localhost 3490
<the program sends me a little message that says "Hello there!">
<then I type in something>: this is a test
<the program sends back a message that says "Hearing you loud and clear!">

You can test your program the same way.  say that the server program 
runs on port 3490 on your as400.  Also suppose that your client program 
would normally send "filename1" to the as/400 to initiate a transfer. 
then do this:

telnet myas400 3490
<type in "filename1"> filename1

Now the as/400 should start sending you the file.  You should see it go 
scrolling past you on the screen.  If it doesn't, you know something is 
wrong.  If it only gets so far, then the problem is on the as/400.  You 
are just using telnet as a substitute for your client program.

James Rich

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.