A fix is available
APAR status
Closed as program error.
Error description
DSNHDECP EBCDIC CCSID (SCCSID for a MIXED=NO subsystem or MCCSID for a MIXED=YES subsystem) is not echoed in listing from the DB2 for z/OS Coprocessor.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2 10 and DB2 11 * * for z/OS who use the coprocessor. * **************************************************************** * PROBLEM DESCRIPTION: User has insufficient information about * * CCSID used to process host variables. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the coprocessor is called, message DSNH4790I will be issued to indicate the effective DSNHDECP EBCDIC CCSID. When the DSNHDECP CCSID is different from the source code CCSID, the warning message DSNH4791I will be issued to indicate the source code CCSID used to process SQL and the EBCDIC CCSID from DSNHDECP that is in effect. Additional Keywords: MSGDSNH4790I MSGDSNH4791I
Problem conclusion
Code is enhanced to add the messages described above. ==> Type= DOC Name= PI41312A Version= HDBAA10 PI41312 introduces the following changes to the externals. The exact text of the message descriptions are subject to change. ========================================================= DSNH4790I csectname DSNHDECP HAS CCSID ccsid IN EFFECT Explanation: This message specifies the CCSID specified in the DSNHDECP MODULE. System action: No action required. User response: No action required. Severity: 0 (informational) --------------------------------------------------------- DSNH4791I csectname CCSID ccsid1 IS USED TO PROCESS SQL, BUT DSNHDECP HAS EBCDIC CCSID ccsid2 IN EFFECT Explanation: The DB2 coprocessor is using CCSID ccsid1 to process SQL. ccsid1 is different from the ccsid2 which was load from the DSNHDECP module. System action: Processing continues. User response: Ensure that the CCSIDs specified for compilation is the CCSID intended for processing SQL. Processing SQL with a CCSID different from the CCSID used in database tables can lead to unexpected results. The CCSID used to interpret data in host variables can be from the DSNHDECP module, the ENCODING BIND option, a CCSID specified on the DECLARE VARIABLE statement or specified as a compile option such as CCSID0 for PL/I or SQLCCSID for COBOL. Refer to "Specifying a CCSID for your application" in the DB2 Internationalization Guide (http://www-01.ibm.com/support/knowledgecenter /SSEPEK_11.0.0/com.ibm.db2z11.doc.char/src/tpc /db2z_specifyccsidapp.dita). Severity: 4 (warning) ========================================================= Information about these new messages will be included in the DB2 for z/OS collection in the IBM Knowledge Center (http://www-01.ibm.com/support/knowledgecenter/ SSEPEK/db2z_prodhome.html) at a later date. ==> Type= DOC Name= PI41312A Version= HDBBB10 PI41312 introduces the following changes to the externals. The exact text of the message descriptions are subject to change. ========================================================= DSNH4790I csectname DSNHDECP HAS CCSID ccsid IN EFFECT Explanation: This message specifies the CCSID specified in the DSNHDECP MODULE. System action: No action required. User response: No action required. Severity: 0 (informational) --------------------------------------------------------- DSNH4791I csectname CCSID ccsid1 IS USED TO PROCESS SQL, BUT DSNHDECP HAS EBCDIC CCSID ccsid2 IN EFFECT Explanation: The DB2 coprocessor is using CCSID ccsid1 to process SQL. ccsid1 is different from the ccsid2 which was load from the DSNHDECP module. System action: Processing continues. User response: Ensure that the CCSIDs specified for compilation is the CCSID intended for processing SQL. Processing SQL with a CCSID different from the CCSID used in database tables can lead to unexpected results. The CCSID used to interpret data in host variables can be from the DSNHDECP module, the ENCODING BIND option, a CCSID specified on the DECLARE VARIABLE statement or specified as a compile option such as CCSID0 for PL/I or SQLCCSID for COBOL. Refer to "Specifying a CCSID for your application" in the DB2 Internationalization Guide (http://www-01.ibm.com/support/knowledgecenter /SSEPEK_11.0.0/com.ibm.db2z11.doc.char/src/tpc /db2z_specifyccsidapp.dita). Severity: 4 (warning) ========================================================= Information about these new messages will be included in the DB2 for z/OS collection in the IBM Knowledge Center (http://www-01.ibm.com/support/knowledgecenter/ SSEPEK/db2z_prodhome.html) at a later date.
Temporary fix
Comments
APAR Information
APAR number
PI41312
Reported component name
DB2 ZOS SUBSYS
Reported component ID
5740XYR01
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-05-18
Closed date
2015-07-29
Last modified date
2015-09-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI29821 UI29822
Modules/Macros
DSNHERRM DSNHPSRV
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"10.1"}]
Document Information
Modified date:
03 March 2021