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



On a command-line, type the following request exactly as it appears below, and then press Enter:

CHGPRF ??CCSID()

What the CCSID for the signed-on user should appear where the cursor is positioned. Based on the symptoms, I expect the value will be one of *HEX, 65535, or *SYSVAL; if the latter, then the system value QCCSID is presumably 65535 [or *HEX]. The CCSID for a user profile is also available from the DSPUSRPRF via any of the specified OUTPUT; for the outfile, the field is UPCCSI. The CCSID has been a part of the *USRPRF user profile object at least since some V2 release of AS/400, though possibly even before.

Regards, Chuck

On 23 Aug 2013 12:44, Hoteltravelfundotcom wrote:
in User profiles I don't see anything for this. Maybe it's in a
later version (we are still 5.4) or I don;'t have the authority to
see that CCSID?

On Fri, Aug 23, 2013 at 3:14 PM, CRPence wrote:

<<SNIP>> since every user profile should [long since before the
prior decade] already have an explicit CCSID, the easiest
resolution is to perform a request to CHGPRF
CCSID(appropriate_value) for which that appropriate CCSID value
will be established for all future jobs started by that user
profile. If a desirable CCSID is set in the User Profile(s),
there is effectively no need to any specific value for the QCCSID
system value; i.e. it can remain 65535 [aka *HEX].

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.