Re: Jobs that use 65535 CCSID... Why?

[Brad Stone <bvstone@xxxxxxxxx>]

Mine shows the same.


On Tue, Jan 4, 2022 at 9:06 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> I'm guessing it's to frustrate you enough to get you to change it.  :-)
>
> On one of my newest LPARs, I just did a WRKSYSVAL OUTPUT(*PRINT).
> "Shipped Value" for QCCSID is 65535.
> "Current Value" is 37
> This lpar was created from scratch from install media.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Brad Stone
> Sent: Tuesday, January 4, 2022 9:21 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Jobs that use 65535 CCSID... Why?
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> In another thread on the RPG list the job CCSID of  65535 came up.  Niels
> called it the "no translation" CCSID.
>
> It made me think of a question I've been wondering about for a while.  Why
> is this CCSID used?  I've never seen it do anything but cause translation
> errors when working with stream files or sockets.
>
> Should this CCSID be treated differently than others when working with
> translations?  Or would it make sense to have the user set their job's
> CCSID to something more "meaningful"?
>
> I see it used more and more... what is the purpose of this, and why does it
> seem to almost be a default on some systems (mostly non US from what I
> see).
>
> Bradley V. Stone
> www.bvstools.com
> Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
> Provider!
> --
> 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@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com