More info on [ to ^...

Brad,

The terminal being used to look at the character is most likely running
in a code page, like 285, where x'BA' is ^ and no CCSID conversion is
being done from the file CCSID to the device CCSID/CHRID.

The initial places to look are:

1.  What is the CCSID of the file?  Is it one, like 37, where [ = x'BA'?
2.  What is the CCSID of the job?  Is it 65535 so that no converion from
    the file CCSID to the job will take place?
3.  What is the CHRID of the *DSPF?  Is it *DEVD so that no conversion
    will take place from the job to the device?

If the file is 285 but the data is encoded with 37 (ie x'BA') you may
have your type of problem.

If the file is 37, the job is 65535, and the device 285, you will have
your type of problem.

If the job is 37, the device 285, and the *DSPF *DEVD you may have your
type of problem.

If you have some combination of the above, you may have your (or a
bigger) problem.  More data is really needed to clearly determine the
cause.

Bruce

>
>WEll, the file has the right EBCDIC hex code, which is BA.  But it isn't the
>right character.  It shows ^ instead of [.
>
>any idea what this is caused by?  My program writes out a "[", but on this
>machine it shows up as a carrot.
>
>Brad
>


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---