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



WRKSYSVAL

QCCSID: Default CCSID (mine is 65535)
QLANGID: Language (mine is ENU)
QCHRID: Character ID/Code Page (mine is 697, 37)

I'm not real sure how all these fit together, especially the CCSID.  You can
specifiy the CCSID when you create a file, or it is supposed to use the job.
But when I create a data file on my machine, I end up with a default CCSID
of 37.

Not sure why.

Joe

> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of David Gibbs
> Sent: Wednesday, September 26, 2001 10:44 AM
> To: 'Midrange Mailing List'
> Subject: RE: CPYTOSTMF character translation
>
>
> Returning to this problem again ...
>
> > 1. User enters some free form data into a source physical file
> > 2. Under program control, the src-pf member is copied to a file
> > on the IFS using the CPYTOSTMF (using code page 437).
> > Pretty simple, eh?  Well, the odd part is ... if the user enters
> > a dollar sign "$" into the source physical file, it gets translated
> > incorrectly in the stream file on the IFS.
>
> I haven't worked with international machines much ... can someone tell me
> where the default language, code page, & CCSID information is
> stored on the
> system ... and how can it be displayed (if at all).
>
> Also, if possible, could someone with a system in the UK, try the above
> scenario?  I'd be interested to see what results you get.
>
> Thanks!
>
> david



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.