× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.