Re: CCSID of objects in IFS

Hi Pete,


> What I am trying to test is a deployment of these files in both a
> V5R3M0 environment and in a V5R4M0 environment. I am trying to do
> exactly the same steps on the two platforms so that if there are any
> differences I'll document them.


If you do the following from QShell, I would expect them to work the same:

export QIBM_CCSID=819 (or 37, or whatever your data is)
tar xvf mytarball.tar

This will force the CCSID of the extracted files to be 819 on both
systems.

Having said that, I don't think the JDBC error you reported has anything
whatsoever to do with the CCSID of the IFS files you're extracting.
Instead, it's more likely that the job has a 65535 CCSID like Marty
suggested.

Though, if this is a System i deployment (as opposed to extracting a
Unix archive you downloaded from someone else) I wonder why you don't
use the SAV and RST CL commands? That would preserve all of the file
information (including the CCSID) instead of just the ones that make
sense under Unix (like TAR).

But, again, I don't think this'll solve the JDBC error...

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