Re: CCSID of objects in IFS

Thanks again Scott.
I delayed my response in hopes of doing some testing with setting CCSID's and then extracting the files but I haven't had a chance because I am traveling.

If I get all of it sorted out, I think WILL just use the sav and rst commands and provide a zipped save file for deployment in the future. First though, I need to sort out some of the issues I am seeing and determine what is causing them. I'll have access to a "clean" box this afternoon and I am going to walk through each step. That should clarify the issues for me.

If I run into any unanswerable questions though, or finally sort this out, I'll be sure to post back here.

Pete


Scott Klement wrote:

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