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



this was the ticket! thank you Robert!

Jay

On Thu, Jun 11, 2020 at 7:55 AM Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:

Jay, to add to what Vernon said I just checked and on our Presto instance
we have
DefaultFsCCSID 00037
DefaultNetCCSID 01208

I'm not sure what they do but I thought this may help.

Rob


On Wed, Jun 10, 2020 at 10:48 PM Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Hey Jay!

Reason code 3 says 37 is not a valid ASCII CCSID - which is true - the
setting I saw on our machine was 1208, UTF-8, which I'd expect when
coming from the Web.

The details of the message suggest there are lots of places to set a
CCSID for the HTTP Server - I certainly don't know what they all mean,
but there are clues, right?

Good luck!
Vern

On 6/10/2020 9:10 PM, Jay Vaughn wrote:
I did. No difference. :(

Jay


On Jun 10, 2020, at 10:07 PM, Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:

Jay, try DefaultNetCCSID 00037

Rob

On Wed, Jun 10, 2020 at 8:16 PM Jay Vaughn <
jeffersonvaughn@xxxxxxxxx>
wrote:

thanks Vernon,

I have tried putting DefaultNetCCSID 37 in the httpd.conf but when I
start
the server instance it fails with this in the joblog...


Message . . . . : CCSID value is not correct.

Cause . . . . . : CCSID value 37 is not correct. The reason code
is
3.

Reason codes and their meanings follow: 01 -- The -netccsid startup
value

did not specify a valid ASCII CCSID. 02 -- The -fsccsid startup
value did

not specify a valid EBCDIC CCSID. 03 -- The DefaultNetCCSID
directive did

not specify a valid ASCII CCSID. 04 -- The DefaultFsCCSID directive
did
not
specify a valid EBCDIC CCSID. 05 -- The CCSID value specified on
the

CHGHTTPA command is not a valid ASCII CCSID. 08 -- The CGIJobCCSID
directive
did not specify a valid EBCDIC CCSID. Recovery . . . : Correct
the
CCSID
value and start the HTTP server again.



37 isn't a valid EBCDIC CCSID?

thank!

Jay






On Wed, Jun 10, 2020 at 7:08 PM Vernon Hamberg <
vhamberg@xxxxxxxxxxxxxxx>
wrote:

I believe there are attributes that can be set for HTTP server
instances. In the web-based admin client, in General server
properties,
I think, advanced properties, I see client and server CCSIDs can be
set,
optionally. Here is a bit of the help text you can see there -

*Note:*The server can obtain CCSID information from several
sources:
1) from what is passed in on the STRTCPSVR command. 2) from what is
specified in the HTTP Server (powered by Apache) configuration
file.
3) from what is specified in the CHGHTTPA global attributes. 4)
from
the QCCSID system value.
I think one must be very aware of what will happen if you set these.

There are directives in the httpd.conf file - I just saw this -
DefaultNetCCSID 1208 - in one of the setups on one of our IBM i's.

HTH
Vern

On 6/10/2020 4:54 PM, Nathan Andelin wrote:
On Wed, Jun 10, 2020 at 8:52 AM Jay Vaughn <
jeffersonvaughn@xxxxxxxxx>
wrote:

when a server instance is started, how does the job determine the
ccsid
to
be used? And how can it be overridden?

It's a bit of a mystery how HTTP server Job CCSIDs are set because
IBM
decides that. IBM could set the CCSID explicitly on the SBMJOB
command,
or
use the QCCSID system value, or use the CCSID of the QTHMHTTP User
Profile.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.