× 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.



I usually use this technique, but in my CL program I just use FTP DUMMY,
works fine.
cjg

Carl Galgano
EDI Consulting Services, Inc.
540 Powder Springs Street
Suite C19
Marietta, GA  30064
770-422-2995
mailto: cgalgano@ediconsulting.com
http://www.ediconsulting.com
EDI, Communications and AS400 Technical Consulting

-----Original Message-----
From: Jim Langston <jlangston@conexfreight.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Monday, February 14, 2000 5:56 PM
Subject: Re: Batch FTP


>Ahhh, okay, now it makes sense.
>
>The programmer wanted to put the IP address of the remote
>system into the command input file instead of the source file,
>for very good reason.  If the IP address ever changes, or you
>want to send to another place, it is much easier to find the
>command input file and change it, then to find the source code,
>change it and recompile.
>
>The reason s/he put in LOOPBACK is because you can not
>FTP without putting in a remote location name.  To get around
>this s/he just used the local machine to kick it off.
>
>Then they had the input file script close the connection, and open
>the real connection.
>
>It was just their way of doing things, and one that I think probably
>is a pretty good idea.  On a PC you can just run the command FTP.EXE
>without putting in the remote location, and then run the open command.
>
>Should be that way on the AS/400 also, IMO.
>
>Regards,
>
>Jim Langston
>
>SHISHIRKSINGH wrote:
>
>> The scenario is like this :
>>
>> I have a PC IP '192.168.45.90' to which I will be doing FTP from
>> AS400(LOOPBACK is the local host - 127.0.0.1).
>>
>> I can do it in 2 ways,
>>
>> a) FTP RMTSYS('192.168.45.90')
>>
>>         and then in the command input file the code will be
>>                 zzzzzz aaaaaaa
>>                 PUT .....
>>                 ---------
>>                 CLOSE
>>
>>         where zzzzzz is the user and aaaaaa is the password
>>
>> b) FTP RMTSYS(LOOPBACK)
>>         and then in the command input file the code will be something
like
>> this :
>>
>>                 XXXXXXX **********      -> This is the dummy
login/Password
>>                 close
>>                 OPEN '192.168.45.90'
>>                 USER  zzzzzz aaaaaa
>>                 PUT ....
>>                 -------
>>                 -------
>>                 CLOSE
>>
>>
>> I have the 2nd method being used at lot of places. Is there any specific
>> advantage of using the 2nd method?
>>
>> But then 1st method gives me more flexibility as far as FTP server IP
>> address is concerned. Is there any security aspect involved?  IBM manual
too
>> does not say much other than stating that these are the 2 ways of doing
it.
>>
>> Thanks
>> Shishir
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.