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



Strangely enough, I am unable to change the CCSID of the messages in my
message file to 37. It starts at *JOB, and if I change it to 37 it remains
at *JOB, and when displayed it is still 65535.

On Thu, May 24, 2018 at 8:23 AM, Mark Murphy <jmarkmurphy@xxxxxxxxx> wrote:

I know. It isn't my decision. I have tried to get that changed, but the
powers that be are a apprehensive about changing it. They think changing it
will break something.

On Thu, May 24, 2018 at 8:20 AM, Mark Murphy <jmarkmurphy@xxxxxxxxx>
wrote:

IBM i: 7.1
RDi: 9.6.0.3
iSphere: 3.3.0.r

I have finally gotten iSphere loaded, and I am liking it. But, I am
having a problem with the Message File Editor. I cannot Preview or Display,
or Change messages. It just does nothing. If I double-click on a message I
get the following error:

An error has occurred. See error log for more details. Parameter
'ccsid' must not be [null].

Our system has QCCSID set to 65535.

Jobs have:
Coded character set identifier . . . . . . . . . : 65535
Default coded character set identifier . . . . . : 37

Unfortunately messages in the message file also have CCSID 65535.

I am guessing that is the problem. Could we have a preference to state
which CCSID we are using to replace the 65535? Or is there an easy way to
change the CCSID of messages?







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.