Corrupted data when using channels and containers

Data corruption when using channels and containers can occur if an incorrect CCSID is specified.

Symptom

Unexpected or corrupt data is returned to the client application when using an IPIC connection and channels and containers.

Probable cause

  • The wrong CCSID is specified on the client application channel and has been inherited by the container.
  • The wrong CCSID is specified on the container.

Action

  1. If corrupted or unexpected data is returned, run a Gateway daemon trace to find out which code page the JVM is running on. Look in the System Properties section at the top of the trace.
  2. For Java applications, use the setCCSID method to set the required code page on the channel. You must explicitly specify a CCSID when creating the container. For C or .NET applications, specify a CCSID when creating a CHAR container.

For more information on how to find the code page that the Client has sent to the server, see Data conversion.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/codepageproblems.html