Literals (Was: OPNQRY reference book)

[bvining@xxxxxxxxxxxx]

The job default CCSID really removed that requirement (from the point
of view of DRDA, ODBC, and JDBC anyway).  With the default job CCSID
being used by database, since V3R1, to CCSID tag database files at
creation time (and the associated tagging of pre-V3R1 database files when
upgrading to V3R1 or later releases) the database access services have
a way to identify the CCSID and so the system/job CCSID is not needed
(in this specific scenario -- they are still valuable for other
services).

Bruce

>
>Thanks for the CCSID comments.  You make an excellent point regarding using
>the default CCSID for systems set to 65535.  I am surprised that lots of
>systems still have 65535 set.  I would have thought that remote data access
>is quite common now and using DRDA, ODBC, JDBC, etc requires the system CCSID
>to be other than 65535 -- or has the job default CCSID removed that
>requirement?
>
>I prefer the API approach anyway because it results in one less object in the
>application and can be completely controlled programmatically.  I have a set
>of wrapppers to handle the conversions with sensible default values.
>


+---
| 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
+---