From the documentation it seems that users will have to modify, compile, and link all their ADABAS/CICS programs in order to take advantage of new ADABAS/CICS interface plus change CICS region JCL. Has anybody test it?
You will only have to modify your programs (using native Adabas calls) if you want to use the new ACBX interface.
It will require having either two libraries, one for ACI 813 and one for 743, or merge modules, mix them in one library… either way will make our multi-environment platform too complex.
What if we relink the new (813) Adabas CICS interface with an ALIAS that points to our current Adabas CICS interface name?
The ALIAS trick works
//SYSLMOD DD DISP=SHR,DSN=SAG.CICS.RPL.LOAD
//ACILOD DD DISP=SHR,DSN=SAG.ACI813.LOAD
//SYSLIN DD *
MODE AMODE(31),RMODE(ANY)
INCLUDE ACILOD(ADACICS)
ENTRY ADACICS
ALIAS ADABAS <== previous Adabas CICS interface name
NAME ADACICS(R)
We have tried the trick with the ALIAS but during the cics startup, the following error occurs:
+NTAD - ADABAS , ABEND U670 IN ADABAS LINKAGE ROUTINE
Can this be related or be something else? The jcl as follows:
//LKED EXEC PGM=HEWL,PARM=‘RENT,LIST,XREF,REUS,NCAL,LET’
//SYSPRINT DD SYSOUT=*
//SYSLMOD DD DSN=DBMS0E.ADABAS.ACI814.USER.LOAD,DISP=SHR
//ADALIB DD DSN=DBMS0E.ADABAS.ACI814.USER.LOAD,DISP=SHR
//CICSLIB DD DSN=CICSTS.V220.CICS.SDFHLOAD,DISP=SHR
//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSALLDA
//SYSLIN DD *
MODE AMODE(31),RMODE(24)
INCLUDE CICSLIB(DFHEAI)
REPLACE DFHEAI0
INCLUDE ADALIB(ADACICS)
INCLUDE ADALIB(LNKGBLS)
INCLUDE CICSLIB(DFHEAI0)
ENTRY ADACICS
ALIAS ADABAS
NAME ADACICS(R)
Thanks in advance.