How do I RECEIVE DBCS field with explicit Shift-out and Shift-In characters?

BROWSE BY TAG CICS Newsletter,   VIEW ALL TAGS

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT CICS Newsletter New statistics for CICS Transaction Server 3.2 Manage CICS workloads with transaction classes Run CICS in batch to beat a shrinking batch window Ensuring CICS security with the Web Services Security standard Use DFHLS2WS to expose CICS applications as a Web service Using IBM IPCS to battle software bugs CICS and Web services: Ready to go Using External Call Interface (EXCI) to access CICS Using CICS event monitoring points (EMPs) for tuning and debugging Implementing CICS managed data tables

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

The whole point of pure DBCS fields (defined as PS=8 on the DFHMDF macro) is that such fields are not encapsulated by Shift in (SI) and Shift out (SO) characters. This is defined by the 3270 Datastream architecture When an application issues a BMS RECEIVE command, the terminal returns pure DBCS fields without SO and SI, since this is how they are stored in the device buffer.

The 3270 READ command issued by CICS terminal control on behalf of BMS is such that 3270 extended field attributes are not returned by the device and hence CICS has no idea whether any field is defined as PS=8 or not. Even if CICS had this knowledge, it cannot wrap SO and SI characters around these fields because existing pure DBCS-capable applications would cease to work. I think that UCTRAN=NO must be specified for terminals which are DBCS capable. The CICS Terminal Control and BMS functions both provide Global User Exits which could be used to perform uppercase translation based on the customers' knowledge of their applications, or upper case translation could be performed in the application programs themselves. I appreciate that this is not a satisfactory solution, but I do not know what else to suggest.