ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
CA Datacom/DB use of EBCDIC code pages
Article ID: 102711
Updated On:
Products
Datacom
DATACOM - AD
CIS
COMMON SERVICES FOR Z/OS
90S SERVICES
DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
COMMON PRODUCT SERVICES COMPONENT
Common Services
Datacom/AD
CA ecoMeter Server Component FOC
EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES
INFOCAI MAINTENANCE
IPC
UNICENTER JCLCHECK COMMON COMPONENT
Mainframe VM Product Manager
CHORUS SOFTWARE MANAGER
CA On Demand Portal
CA Service Desk Manager - Unified Self Service
PAM CLIENT FOR LINUX ON MAINFRAME
MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
GRAPHICAL MANAGEMENT INTERFACE
WEB ADMINISTRATOR FOR TOP SECRET
Xpertware
Issue/Introduction
There are multiple code pages used for EBCDIC format, and it is possible to have, for example, 1047 for the operating system, 037 for COBOL compiles, and 500 for MQ-Series tasks.
Does CA Datacom/DB use any special code pages when storing its data?
Environment
Release: DATABB00200-14.0-Datacom/AD
Component:
Component:
Resolution
The MUF and CA Datacom/DB databases do nothing special with the definition of a code page but will default to use the system setting.
Essentially, if you define a field as CHAR(8), you will store 8 characters in the field, and we don't perform any data translation of data in the records, but we store whatever the application passes to us.
There is, of course, a different response when dealing with DBCS data (like Kanji, for example), or data that originates through an application using JDBC type-4 connections, where a codepage can be specified in the CA Datacom Server configuration. Additionally, some application tools like CA Ideal can use an internal translation table to change characters like currency symbols. Again, this has no effect on the actual data storage, but only on the interpretation of the input and output characters in specific applications.
Essentially, if you define a field as CHAR(8), you will store 8 characters in the field, and we don't perform any data translation of data in the records, but we store whatever the application passes to us.
There is, of course, a different response when dealing with DBCS data (like Kanji, for example), or data that originates through an application using JDBC type-4 connections, where a codepage can be specified in the CA Datacom Server configuration. Additionally, some application tools like CA Ideal can use an internal translation table to change characters like currency symbols. Again, this has no effect on the actual data storage, but only on the interpretation of the input and output characters in specific applications.
Additional Information
If you would like more examples of commonly-used codepages, you can refer to these web pages found through an Internet search for EBCDIC Code Pages:
Code Page 037 or 037-2
Code Page 500
Code Page 1047
Here is an interesting page noting the differences between these three codepages.
As always, please contact CA Technologies support for CA Datacom if you have further questions.
Code Page 037 or 037-2
Code Page 500
Code Page 1047
Here is an interesting page noting the differences between these three codepages.
As always, please contact CA Technologies support for CA Datacom if you have further questions.
Feedback
Yes
No
Powered by
