Re: Literals (Was: OPNQRY reference book)

R
Hello Barbara,

You wrote:
>For CCSID to CCSID portability, you shouldn't code literals in your source
>unless they are invariant characters (apostrophe is invariant).  Instead,
>you should put your "literals" in a file and read them in at runtime.

Just to make sure I clearly understand this:  If I store variant characters 
in a file tagged with CCSID 37 and compile my program on a system under 
CCSID 37 and then restore both objects on a system with a different CCSID 
the data in the file will be converted into the CCSID associated with the 
job when the program is invoked and reads the file?  So this is making use 
of standard database CCSID support?

What I've done is code the literals as a constant in the program and call 
the NLS APIs to translate them into the CCSID of the job before use.  That 
approach seems fine in the limited testing I've done.  Comments?

I'm sure there's a bit more to it because not all CCSID tables map 
perfectly.  I have ordered the CDRA Level 2 documentation.  Hopefully there 
is a bit more information in them.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---