From an OS/390 or z/OS machine you access data that resides on another machine (OS/390, z/OS and non-OS/390), via either a COBOL or C program running under CICS. On the OS/390 or z/OS machine you do not need to run the daemon, as long as the daemon is running on the other machine.

To set up the CICS ODBC Interface
1. Copy NAVROOT.LOAD(ATTCICSD) to a CICS DFHRPL library.

2. Make sure that the CICS Socket Interface is enabled. You can enable this interface by issuing the following CICS command:

EZAO START CICS1

To use the CICS ODBC Interface

1. Copy the COBOL or C program to a CICS DFHRPL library.

2. Set up CICS resource definitions for the COBOL or C program and transaction.

The following JCL can be used as a template:

//ATTCSD JOB 'ATTUNITY','CSD',MSGLEVEL=1,NOTIFY=&SYSUID
//STEP1 EXEC PGM=DFHCSDUP,REGION=512K,
// PARM='CSD(READWRITE),PAGESIZE(60),NOCOMPAT'
//STEPLIB DD DSN=<HLQ1>.SDFHLOAD,DISP=SHR
//DFHCSD DD UNIT=SYSDA,DISP=SHR,DSN=<HLQ2>.CSD
//OUTDD DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
*/************************************************** ******************/
*/* ATTUNITY ODBC CICS Definitions */
*/* */
*/************************************************** ******************/
*---------------------------------------------------------------------*
* Note: Install GROUP(ATT) - CEDA IN G(ATT) *
* If you are re-running this, you can uncomment the DELETE command. *
*---------------------------------------------------------------------*
*
* Start ATTUNITY ODBC RESOURCES:
*
* DELETE GROUP(ATT)
DEFINE PROGRAM(ATTCICSD ) GROUP(ATT) LANGUAGE(C) DATALOCATION(ANY)
DE(Attunity ODBC DLL)
DEFINE PROGRAM(<PROG> ) GROUP(ATT) LANGUAGE(<LANG>) DATALOCATION(ANY)
DE(Attunity ODBC)
DEFINE TRANSACTION(<ATTTRAN>) GROUP(ATT) PROGRAM(<PROG> )
TASKDATAL(ANY)
DE(Attunity ODBC TRAN ID)
LIST GROUP(ATT)
*
* End ATTUNITY ODBC RESOURCES
*
/*
//

3. Make the following changes before running the JCL:

  • Modify the JCL, as follows:


* Change the JOB card to suit the site.

* Change <HLQ1> to point to the CICS SDFHLOAD library.

* Change <HLQ2> to point to the CICS CSD dataset.

* Change <LANG> to the LE370 for COBOL or C for C.

* Change <PROG> to the COBOL or C program name.

* Change <ATTTRAN> to the CICS transaction name.

  • From CICS, install the ATT group, by issuing the following command:

CEDA IN G(ATT)

4. Compile the COBOL or C program and link it to the NAVROOT.FIXLIB(ATTCICSS) member where NAVROOT is the high-level qualifier where AISis installed.

5. Move the compiled and linked module to a CICS LOAD library.

6. For COBOL programs only: Write, as part of the program, include definitions for the COBOL ODBC interface to match the C definitions found in the attcicsh.h include file (supplied as part of the mainframe kit, in NAVROOT.INCLUDEH.H).


--------------------------------------------------------------------------------
1 Refer to the TCP/IP V3R2 For MVS: CICS Sockets Interface Guide. If you are not sure if the system is configured with the Socket Interface, try running the EZAC transaction. If the transaction produces a screen, you should be able to run the EZAO startup transaction. If not, see if the transaction has been defined in a group that has not been installed, for example: CEDC V TRANS(EZAC) G(*).If it is defined in a group, install that group and try running EZAO again. If not, you have to configure CICS as outlined in the above manual.