Rob; good points.
Nothing like a "benign error" to mess with a person's head when
something is not working and the log is used to find the cause/fix.
Also, +1 about Scott.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, August 06, 2013 5:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: FTP GET into IFS
Scott eloquently stated it (as usual). I will add that you might not want to just ignore the error but to get in the habit of using the LOCSITE (or whatever is applicable in that situation). At some time you will start scripting your sql. Then you'll start checking for errors in the output.
Instead of ignoring certain errors, if you use the appropriate command, you won't have the error in the first place.
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: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/05/2013 07:55 PM
Subject: Re: FTP GET into IFS
Sent by: midrange-l-bounces@xxxxxxxxxxxx
LOCSITE NAMEFMT 1 would change it for the IBM i client.
SITE NAMeFMT 1 would change it for a server
NAMEFMT 1 (without SITE or LOCSITE) changes it on both ends.
So it really depends on what you're doing. If you're using the IBM i
client, and getting from a Windows/Unix FTP server, you'd want to use
LOCSITE. (Otherwise, the server will return an error, since it doesn't
understand "namefmt"... tho, you could also just ignore the error.)
If transferring from the IFS of one IBM i to another IBM i, you'd want
to simply use NAMEFMT so it changes both servers to IFS.
If getting from the IFS on an IBM i server to the library system of an
IBM i server, you'd want SITE, so it only changes the namefmt on the
server, not the client.
If putting from Windows or Unix, you'd need to use SITE NAMEFMT 1 (or
QUOTE SITE NAMEFMT 1 for some FTP clients that don't understand SITE)
since the client doesn't understand namefmt.
Hopefully you get the idea...
On 8/5/2013 4:47 PM, Gary Thompson wrote:
Thank you. NAMEFMT 1 did the trick
(not sure but maybe LOCSITE is optional ?)
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, August 05, 2013 3:43 PM
To: Midrange Systems Technical Discussion
Subject: Re: FTP GET into IFS
On 8/5/13 2:34 PM, Gary Thompson wrote:
Working on an FTP GET command to get a text file onto a folder in our
IFS
Here is our command and the error:
GET /RETURNFILES/CompSurveyReturn.csv /PAT/COMPSURVEYRETURN
(REPLACE
File name format not valid. Use the format: library/file.member or
file.member.
Any suggestions much appreciated!
You're in the QSYS.LIB file system and naming convention.
I think you're looking for:
LOCSITE NAMEFMT 1
LCD /
--
JHHL
--
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.
midrange.com
