|
Brad,
I think you need to be looking at these environment variables:
PASE_LANG QIBM_PASE_CCSID
Note that it does not seem to pay any attention to whatever you might set
in QIBM_CCSID.
See also:
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzaq9/rzaq9osPASEccsid.htm
Hope that helps,
Mark S. Waterbury
On Thursday, December 26, 2019, 1:53:27 PM EST, B Stone <
bvstone@xxxxxxxxx> wrote:
I can try, but environment variable QIBM_CCSID is supposed to do this.
that's why I'm wondering if I should look for a PTF or if I am misreading
something.
On Thu, Dec 26, 2019 at 12:43 PM mlazarus <mlazarus@xxxxxxxxxxxx> wrote:
Bradley,the
Try creating an empty file with the proper CCSID of 1252 (EDTF should
have that ability) and see if that resolves the issue. I'm assuming
that sysval QCCSID is set correctly to a specific ID (e.g. 37).
-mark
On 12/26/2019 10:58 AM, B Stone wrote:
I am working on a project that requires to unzip files during theprocess.
I am using unzip in QSH.log
When I set debug on for the process it will output the zip results to a
file. But that file is always created with CCSID of 37.
I found the QIBM_CCSID environment variable but that seems to have no
affect.... here is info from my job:
QIBM_CCSID '1252'
QIBM_QSH_CMD_OUTPUT 'FILE=/debug/file_unzip.log'
The first env var is set, then the second so we store the results of
html).unzip.ability
It is view-able using WRKLNK but I'd rather use a text editor, and it's
garbage of course when viewing from the IFS.
Is there something else I need to set? This seems to be the way it's
done... This is a V7R4 system right now.
TIA.
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #13<https://www.bvstools.com/mailtool.html>: The
to use an IFS stream file as the body of the email (either text or
list--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.