If both program A and program B were compiled using the same CCSID then 
they should match.  As these are constants the job CCSID at run time would 
not come into play, it's the CCSID of when they were compiled.

Bruce Vining




David Gibbs <david@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/26/2006 04:51 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
CCSID quandry






Folks:

I've got another CCSID problem.

On a system that is set to default CCSID 277 ...

One CL program is calling another ... with a 'variant' character in the
parameter.

For example:

Program a: call pgm(b) parm('#ABCDEF')

Program b: pgm (&parm1)
                                 dcl &parm1 *char (10)
 
                                 if (&parm1 *eq '#ABCDEF') then(do) /* 
something */

The problem is, when program B gets control, and does the comparison,
parm1's value doesn't match the constant.

Obviously the programs were written (and tested) with CCSID 37, where
'#' is a valid character.

My question is: Why don't the two constants in the two programs match
when running under CCSID 37?

Thanks!

david



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.