Re: FTP weirdness

Scott,

Thanks for the explanation which, as always, makes perfect sense.

You are right. This has been a crazy day, a perfect ending to a crazy and
hectic week :-) In Venezuela we have a saying that goes something like:
"There are some days when you shouldn't get out of the bed". This has been
one of those...


Thanks again,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--



On Fri, Aug 26, 2011 at 6:08 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

Hi Luis,

You are referring to a scenario where a client is doing a PUT request to
the IBM FTP Server for i. In your scenario (which is different from the
one the OP has implied) the client doesn't matter, because the file is
being created by the server program. And the IBM server program is
indeed configured via the CHGFTPA command.

And in your scenario, you're absolutely right... it doesn't matter what
the client is. It doesn't matter at all because the client isn't
creating the file! The server is, because you're doing a PUT request.

But the OP specifically said that the server is a Sterling Integrator
FTP server -- so he's not using the IBM server!

Presumably, he's using the IBM FTP Client for i, and doing a GET request
from the Sterling Integrator server. Since we know the server is not on
his box, and since we know that the CCSID in question _is_ being
assigned on his box, it's implied that he's doing a GET request, and in
a GET request, it's the client that creates the file, not the server.

I hope this is clear, I know you're having a crazy day, and that might
be why you're getting confused.

Anyway, you're absolutely right about the way CRTCCSID works -- but
CHGFTPA won't matter, because that's the server, not the client!
You have to change the CRTCCSID with a LOCSITE command to change it for
the client, or specify a different ASCII CCSID on the FTP command
parameter. (again, changing the CCSID on the CHGFTPA won't help)

Your message did make me think about things more thoroughly, and now I
do understand why he's getting a 500. (Because 500 is the EBCDIC that
corresponds to 819, which is the default on the FTP CCSID(xyz) parameter.)


On 8/26/2011 2:34 PM, Luis Rodriguez wrote:

I'm just a little curious about your assertion that the CHGFTPA

parameters

don't do any difference here. As I see it (and it could be an error of
my part interpreting the help text of the command), CRTCCSID works every
time the file is created (in the "library" file system), regardless of

who

the client is.

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