Question:
Is there a way to identify the specific EBCDIC type used by IDMS based the country in which it is being used?
Answer:
In your DISTSRC ( AAGJSRC for IDMS 18.0 ) you should have these source members:
CP1140F - All codepages for IBM US EBCDIC - full international
CP1141F - All codepages for IBM DE EBCDIC: full international
CP1141R - All codepages for IBM DE EBCDIC: national-only
CP1142F - All codepages for IBM DK/NO EBCDIC: full international
CP1142R - All codepages for IBM DK/NO EBCDIC: national-only
CP1143F - All codepages for IBM FI/SW EBCDIC: full international
CP1143R - All codepages for IBM FI/SW EBCDIC: national-only
CP1145F - All codepages for IBM SP EBCDIC - full international
CP1145R - All codepages for IBM SP EBCDIC - national-only
CP1147F - All codepages for IBM FR EBCDIC - full international
CP1147R - All codepages for IBM FR EBCDIC: national-only
CP1148F - All codepages for IBM BE/CH EBCDIC: full international
CP1148R - All codepages for IBM BE/CH EBCDIC: national-only
RHDCCODE is created by assembling and linking one of the CPnnnnn source codes depending on the country.
The JCL to create RHDCCODE ://ASMSTEP EXEC PGM=ASMA90,REGION=0M
//SYSLIB DD DSN=Your.HLQ.DISTMAC,DISP=SHR
// DD DSN=Your.HLQ.INDSRC,DISP=SHR
// DD DSN=SYS1.MACLIB,DISP=SHR
//SYSUT1 DD DSN=&&SYSUT1,UNIT=SYSDA,SPACE=(CYL,(15,10))
//SYSUT2 DD DSN=&&SYSUT2,UNIT=SYSDA,SPACE=(CYL,(15,10))
//SYSUT3 DD DSN=&&SYSUT3,UNIT=SYSDA,SPACE=(CYL,(15,10))
//SYSPRINT DD SYSOUT=*
//SYSIN DD DSN=SOURCE.CP1140F,DISP=SHR
//SYSLIN DD DSN=&&OBJECT,DISP=(NEW,PASS),UNIT=SYSDA,
// SPACE=(CYL,(15,10))
//STEP003 EXEC PGM=IEWL,
// PARM='LET,MAP,LIST,NCAL,SIZE=(524288,65536),RENT,REUS,REFR'
//SYSPRINT DD SYSOUT=*
//SYSLMOD DD DSN=Your.HLQ.LOADLIB,DISP=SHR
//RHDCOBJ DD DSN=&&OBJECT,DISP=SHR
//DISTLOAD DD DSN=Your.HLQ.DISTLOAD,DISP=SHR
//SYSLIN DD *
INCLUDE RHDCOBJ
INCLUDE DISTLOAD(RHDCCODT)
ENTRY CODEEP1
NAME RHDCCODE(R)
/*
If your CV is release 18.0 please change the DISTLOAD library in the link step to Your.HLQ.AAGJMOD.
RHDCCODE represents the specific type of EBCDIC that IDMS is using. Being a mainframe product it will only use EBCDIC. Each of the CPnnnnn source is customizable beyond what is required for a specific country. If you are going to communicate between IDMS and the PC, a web application or an application on UNIX the character set can be converted from EBCDIC to unicode or ascii before the data is sent via TCPIP. Knowledge documents such as TEC522052, TEC495321 and TEC502054 are talking about this conversion between character sets to communicate between the mainframe and other platforms.
Additional Information:
Advantage CA-IDMS Release Summary