DSNE345I WARNING: DB2 DATA CORRUPTION CAN RESULT FROM THIS SPUFI SESSION BECAUSE THE CCSID USED BY THE TERMINAL IS NOT THE SAME AS THE CCSID USED BY SPUFI. TERMINAL CCSID terminal-ccsid. SPUFI CCSID: spufi-ccsid. NOTIFY THE DB2 SYSTEM ADMINISTRATOR.

Explanation

The current SPUFI session was initiated on a TSO terminal that uses a coded character set identifier (CCSID) of terminal-ccsid. However, SPUFI was bound on the local Db2 server using a CCSID of spufi-ccsid. This discrepancy can lead to unexpected data conversion, affecting any characters that do not map to the same code point in the two CCSIDs.

If terminal-ccsid is blank, then the terminal code page and character set cannot be queried or they are not supported by ISPF. Possible reasons why the terminal code page and character set cannot be queried include:
  • Hardware limitation such as use of older terminals
  • Improper configuration of the terminal emulator software
  • Improper BTAM or control unit setup

A blank spufi-ccsid indicates that SPUFI might have received an unexpected SQLCODE when it attempted to query the current application encoding scheme. Diagnostics for that SQLCODE appear directly after the DSNE345I message in the message warning panel.

System action

SPUFI waits for the user to indicate whether to continue or quit.

System programmer response

On the local Db2, SPUFI expects to process only EBCDIC character data encoded in the CCSID of spufi-ccsid. Ensure that the user's TSO terminal configuration is updated to use a CCSID of spufi-ccsid. Verify the data integrity of all tables modified during the SPUFI session and follow standard recovery procedures. Contact IBM® for guidance if widespread or long term data corruption is evident (for example, if many users report this message when using SPUFI).

Special considerations:
Blank CCSIDs
As noted previously, a blank terminal-ccsid setting occurs when the terminal code page and character set cannot be queried or they are not supported by ISPF. Check for the following situations:
  • If the message occurs when using a terminal emulator, verify that the emulator software is configured with a CCSID setting.
  • Check the VTAM® setup: The VTAM logmode entry used to define the session characteristics for the terminal must have the EDS (extended data stream) bit turned 'on' in the PSERVIC (that is, pservic=xx80xx..). For more information, consult z/OS ISPF Planning and Customizing and the z/OS® SNA Network Implementation Guide.
  • Older terminal hardware such as the IBM 327x series do not support the EDS, so a CCSID cannot be determined. You can instruct users of such devices to specify in the SPUFI defaults panel that the DSNE345I message should be suppressed. Note that suppression applies only when the terminal CCSID is blank. You cannot use this field to suppress DSNE345I when terminal-ccsid is non-blank.

A blank spufi-ccsid indicates that SPUFI probably received an unexpected SQLCODE when it attempted to query the current application encoding scheme. Check the diagnostics for the SQLCODE that is displayed directly after the DSNE345I message, and then respond to the diagnostics accordingly.

User response

Notify the system programmer. Depress the END key to quit or the ENTER key to continue. Important: Continuing can result in corruption of data stored by Db2.