*DTAQs do not have a CCSID associated with them as there is no
external definition of the messages that the system is aware of.  At
any given offset into the message you may have character data, you
may have integer data, or you may have ???.  Without a data definition
being available there is no good way for the system to provide CCSID
processing.  If you do need CCSID processing of *DTAQ messages, then
I would suggest you include the CCSID value within the message and
do the necessary conversions within the receiving job.


>I've been trying to create data queues with specific CCSIDs, but I can
>see no way to set the value.  There's no CCSID parameter on the CRTDTAQ
>command, for example.  The Java Toolbox classes have methods for setting
>and getting the CCSID, but setting it doesn't appear to make any
>I presume that, on creation, the data queue inherits the CCSID of the
>creating job.  Or is it that when data is put onto the queue, the entry
>has the CCSID of the sending job?
>All in all, they're not behaving quite as I'd expect, the IBM docs are
>of little help, and I haven't come up with anything useful on various
>web searches.  Has anyone got any experience of this?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.