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


  1.  Home
  2. MIDRANGE-L
  3. December 2019

Re: CCSID of QSHELL generated file not getting set

H Brad

Here's the thing I did to get UTF-8 output in QShell, which doesn't natively do that - this is in a RPGLE program where I have to modify a value in an XML file (for and XLSX file) that I don't know until I've finished processing all the rows.

sedCmd = 'QSH CMD(+
                    ''export QIBM_CCSID=1208 +
                      && sed "' + %char(pLineFrom) + ',' +
                                  %char(pLineTo) +
                              ' s/' + pSearchFor +
                              '/' + pReplaceWith + '/';

        if pReplaceAll;
          sedCmd += 'g';
        endif;

       sedCmd += '" ' + pFile + ' > /tmp/temp' + jobNbr + '.tmp +
                     && mv /tmp/temp' + jobNbr + '.tmp ' + pFile + ''')';

The command becomes something like this -

export QIBM_CCSID=1208 && sed "5, 6 s/tagname/realvalue/g" pFile > /tmp/temp123456.tmp && mv /tmp/temp123456.tmp pFile

The point here is that the && continuations put everything in the same QShell job - I think that mattered when I first found this solution for replacing the changes from sed into the from file - Qshell version of sed does not have the "replace-in-place" option that other versions of sed do - and I don't remember if PASE' version does, or if there were other problems I had.

On 12/27/2019 9:11 AM, B Stone wrote:
It's not a deal breaker... I can still view the logs with WRKLNK. Just
would be nice to view them with a text editor.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #6 <https://www.bvstools.com/mailtool.html>: Easily send
group emails with Distribution Lists

On Fri, Dec 27, 2019 at 8:30 AM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

I hate work arounds:

CPY OBJ('/tmp/QSHELL_output') TOOBJ('/debug/file_unzip.log')
TOCCSID(*PCASCII) DTAFMT(*TEXT) REPLACE(*YES)

extra step like the pre-creation of the file.


Is there a way to run you unzip procedure in a PASE shell?



Yuck,
Bryan



Kevin Bucknum wrote on 12/27/2019 8:11 AM:
I haven't found a way while playing around with this for the file to not
be created with the job's ccsid. None of the environment variables seem to
affect this. It look like it is time to ask IBM if it is an intended
behavior or not. Creating the file beforehand and using FILEAPPEND does
seem to work.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of B Stone
Sent: Thursday, December 26, 2019 5:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Re: CCSID of QSHELL generated file not getting set

unzip. Installed using YUM.


On Thu, Dec 26, 2019 at 3:55 PM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

what command are you running from QSH?

it would be interesting to try it out.

Bryan


B Stone wrote on 12/26/2019 4:27 PM:
Thanks, Mark. That wasn't it either.

QIBM_CCSID is documented, from what I can tell, as the environment
variable to use for this.

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzahz/rzah
zvariable.htm
The CCSID of the files created is 37, the job's CCSID (which matches
the description for the QIBM_CCSID env var), not 819 or 1208 which
is the default for QIBM_PASE_CCSID depending on OS version.

Scott K even mentions QIBM_CCSID here:
https://archive.midrange.com/midrange-l/200611/msg01064.html

Actually in thinking about these environment variables and how we
need to adjust them for this and that so much now, it's almost like
multiple LDAs now with the same dangers (ie, packaged software
changes or removes them causing issues with home grown software, or
vice versa).


I do recall having an issue for the PASE CCSID before

On Thu, Dec 26, 2019 at 1:01 PM Mark Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

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/rzaq
9osPASEccsid.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,

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 the
process.
I am using unzip in QSH.

When I set debug on for the process it will output the zip
results to
a
log
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
the
unzip.

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
ability
to use an IFS stream file as the body of the email (either text
or
html).
--
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

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

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

[https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin
Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com



CONFIDENTIALITY NOTICE

This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any other
party and is required to destroy the information after its stated need has
been fulfilled. If you are not the intended recipient, or the employee of
agent responsible to deliver it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or action taken in
reliance on the contents of these documents is STRICTLY PROHIBITED. If you
have received this email in error, please notify the sender immediately to
arrange for return or destruction of these documents.
--
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 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.