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
DatacomDATACOM - ADCISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesDatacom/ADCA ecoMeter Server Component FOCEASYTRIEVE REPORT GENERATOR FOR COMMON SERVICESINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA On Demand PortalCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertware
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?
Release: DATABB00200-14.0-Datacom/AD Component:
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.