|
I'm not sure if by 'terminal session' you mean the terminal device or the terminal job. For the device you could use Retrieve Device Description (QDCRDEVD) API, for the job Retrieve Job Information (QUSRJOBI). If working with the device description you should be careful about the job/*dspf/*pnlgrp parameters associated with CHRID and CHRIDCTL as implicit conversions may be taking place on your behalf. For Unicode/EBCDIC conversion you could use APIs such as QTQCVRT or the MI instruction XLATEMB. There are various encodings for Unicode (UCS-2, UTF-16, UTF-8, etc.) and each can represent a given character in different ways. All three of these are supported by the API and MI interfaces. "James H H Lampert" <jamesl@xxxxxxxxx To om> <mi400@xxxxxxxxxxxx> Sent by: cc mi400-bounces@mid range.com Subject [MI400] Unicode translations 09/10/2004 11:01 AM Please respond to MI Programming on the AS400 / iSeries Fellow MI geeks: I'm just beginning to research a Unicode support project, and was wondering if anybody can point me in the direction of a quick-and-easy way for an OPM MI program to identify the codepage of a terminal session (I may already be doing that), and to translate strings between Unicode and whatever EBCDIC codepage is in use. Also, I recall reading that there are 2 different Unicode codepages; are there any differences between how they code the characters representable in EBCDIC? -- JHHL _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mi400 or email: MI400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
As an Amazon Associate we earn from qualifying purchases.
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.