Re: QHTTPSVR/QZHBMAIN

So changing the https.conf from 37 to 273 ccsid did not solve our problem.
Didn’t think it would but thought worth a try.

So what we still have is a USA based software package (relying on 37 ccsid) on a ccsid(273) system.

When the http instance tries to start (as described first post), it fails.

What I think the resolution will be is for the initial qhttpsvr/qzhmain job run under ccsid(37).

Anyone know how to make that specification?

Tia

Jay

On Jun 5, 2020, at 2:40 PM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:


appreciate the CL option... it is more to what I am accustomed to if you could not guess... so thanks!

Jay

On Fri, Jun 5, 2020 at 2:14 PM John Yeung <gallium.arsenide@xxxxxxxxx> wrote:
On Fri, Jun 5, 2020 at 11:05 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

I'm sure it boils down to me floundering around in Unix command syntax. :)

Though you eventually worked it out with Jack's help, you could also
stick with CL commands if that's more comfortable.

CPY can translate text (actual contents of a stream file) from one
CCSID to another, while CHGATR can change the metadata (including the
CCSID "label") of a stream file.

John Y.
--
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