We're working on a new feature, and we would like to know your thoughts. Our initial questions:
- Would you be able to continue with your existing applications or would you need to make any changes to the existing applications to make them work?
- Would you be interested in partnering as we develop this feature? This may include short calls, demos, and/or beta testing.
- Any other feedback?
See details below.
Your inputs or suggestions in this regard would be highly valuable. Thank you for your time.
==============================
We observed some SQL errors while doing a HE & IT install on z/OS, when the underlying DB2 subsystem is in Unicode Encoding Scheme. The same applies the generation and execution of the Gen applications.
It is our intent to provide our customers with a way to use EBCDIC for Gen within their chosen environment so In order to avoid these SQL Errors which are typically caused by a mismatch of Encoding Scheme of Db2 objects and packages with the Db2 Subsystem default Encoding scheme, we planning to add CCSID EBCDIC statement to the DDL generation, and bind the Gen applications with Encoding EBCDIC.
CREATE DATABASE GENDBXX
STOGROUP SYSDEFLT
BUFFERPOOL BP0;
CREATE DATABASE GENDBXX
STOGROUP SYSDEFLT
CCSID EBCDIC
BUFFERPOOL BP0;
By adding this all the objects that are created would be using the Encoding scheme of EBCDIC, irrespective of the default Encoding scheme of the Db2 subsystem.
We think that the addition of CCSID statement to the DDL, wouldn't cause any change in the behavior for the existing applications on z/OS.
We would not require customers to recreate their existing Databases as these already work with their applications.
We are also planning to Include the option of ENCODING(EBCDIC) in the Bind parms in the following members of CEHBCLS0
BINDPKRT
BINDPLAN
BINDPACK
BIND PACKAGE(&COLLID) +
MEMBER(ADDASSC) +
ISOLATION(&ISOLATION) +
CURRENTDATA(&CURRENTDATA) +
&LIBRARY +
ACTION(&ACTION) +
VALIDATE(B) +
FLAG(I) +
ENCODING(EBCDIC) +
&OWNER +
&QUALIFIER
By specifying the Encoding scheme as EBCDIC in the bind parms, we expect this value to take precedence over the default value specified in the DECP defaults of APPENSCH/ ENSCHEME of a subsystem.
==============================
To summarize, the following changes are planned to Include Encoding parm
For Installation of HE & IT
a) BIND package/Plans (BINDPACK, BINDPKRT, BINDPLAN)
b) Database objects required for HE and IT (CCSID EBCDIC statement)
For Gen Generated Applications
a) Bind of Package/Plan (in TICBNPK)
b) Generated Database (CCSID EBCDIC statement)
------------------------------
Kim Peelman
Product Owner, CA Gen
Broadcom
Plano,TX
------------------------------