MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

Re: Using FTP to transmit a file in the IFS



fixed

All,
I managed to solve the problem.
It appears that even though I used the locsite namefmt 1 command and set
the local directory using the lcd command, the put command needs the full
path name with the file or I get errors.
Once I used the full path name, and surrounded the file name with single
quotes, it worked fine.

Thanks to everyone for their suggestions.

Jeff Young
Sr. Programmer Analyst


On Tue, Jul 15, 2014 at 9:22 AM, <rob@xxxxxxxxx> wrote:

Almost sounds like you're still trying to use locsite.
And the problem is that it's assuming that one side is a stream file, but
the other side is going into DB2. And DB2 object names have a 10
character limitation. (skipping the discussion of long object names vs
short object names for tables created with SQL.)


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Young <jyoung0950@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/15/2014 09:15 AM
Subject: Re: Using FTP to transmit a file in the IFS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I managed to solve the initial issue with the database extension, but now
have another problem.
The file that I am attempting to send has embedded blanks in the name, and
is a long name - 15012014 Creation Report.txt
I have tried to place quotes around it, but it still can not find the
file.
When I change the name to use the _ character instead of blank, I receive
an error 5012014_Creation not found. Is there a limit on the size of the
file name in the PUT sub command?

Jeff Young
Sr. Programmer Analyst


On Tue, Jul 15, 2014 at 9:06 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

+1 on keeping it simple - exactly right, man!


On 7/15/2014 7:47 AM, Bradley Stone wrote:

Jeff,

If you're FTPing from your IBMi then just do this:

ftp 'site.name'
user
password
namefmt 1
cd <remote directory>
put /path1/path2/filename.ext
close

optionally you could do:
ftp 'site.name'
user
password
namefmt 1
cd <remote directory>
lcd /path1/path2
put filename.ext
close

I think the namefmt 1 is what you're looking for to get out of "library
mode" on the client side (the IBMi)

Brad
www.bvstools.com


On Tue, Jul 15, 2014 at 7:20 AM, <rob@xxxxxxxxx> wrote:

Need some clarification.
Who is the client? For example, if you are running the ftp command
from
IBM i then IBM i is the client. However, if you are running ftp from
a
PC
or something else then that is the client.
So, if IBM i is the client then locsite namefmt 1 is correct.
Otherwise,
locsite is all wrong.

Are you sending this from one IBM i to another? If so, then do not
use
locsite. Instead just use namefmt 1.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Young <jyoung0950@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 07/15/2014 08:13 AM
Subject: Using FTP to transmit a file in the IFS
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I need to transmit a file in a directory in the IFS using FTP from the
IBM
i server.
I have used the locsite namefmt 1 command to set my naming format on
the
client.
When I use the put command, I receive an error indicating an unknown
database extension.

What am I missing?


Jeff Young
Sr. Programmer Analyst
--
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.


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



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


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


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







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact