CA Global SubSystem Configuration › Customize CA-GSS › Customize CA-GSS for DB2

Customize CA-GSS for DB2

If you are running the IBM DB2 database software, an IMOD can retrieve data by executing dynamic SQL statements.

Make sure that the DSNALI and DSNHLI2 communication modules of DB2 are available. These modules must reside in an APF‑authorized LINKLIB data set.

To configure CA-GSS for DB2

1. Modify your GSSA system PROCLIB member.

   If the DB2 DSNALI and DSNHLI2 load modules are not in a LINKLIST Library, include their library as a STEPLIB in the GSSA system PROCLIB member.

2. Modify CA‑GSS parameters. As needed, modify the CA‑GSS initialization parameters that affect CA‑GSS' DB2 support. Examples of these parameters are contained in the DB2 member of the CAW0OPTN data set.
   • Most parameters in the DB2 member are commented out. To activate one of them, replace its leading asterisk (*) with a blank.
   • You can copy the contents of the DB2 member to your RUNPARM member, or you can simply provide an INCLUDE DB2 statement.
     • The ADDRESS parameter loads the DB2 DSNALI and DSNHLI2 modules during CA‑GSS/ISERVE initialization and makes them available for processing the DB2() REXX function.
     • The DB2PLAN parameter identifies the plan that will be bound to the DB2 where your SQL statements will be processed. The default name is GSSPLAN. If you use a different plan, specify the name through the DB2PLAN parameter.
     • The SSID parameter identifies the DB2 address space that CA‑GSS should communicate with. Each CA‑GSS can communicate with only one DB2 address space.

       The default value is DSN.

       If your DB2 address space uses a different subsystem ID, or you want CA‑GSS to communicate with a different address space, use the SSID parameter to properly identify the address space.

       If you want to process dynamic SQL in multiple DB2 address spaces, you can provide secondary ISERVE address spaces, one for each DB2. GoalNet can then be used to direct processing requests to the appropriate ISERVE address space.

3. Create the SRVDB2P load module.

   Since dynamic SQL programs are highly dependent upon DB2 release level, program name, and date and time of program assembly, CA-GSS distributes the SRVDB2P program in source format. This program, along with sample JCL, can be found in the CAW0JCL member BYSDB2P.

4. Bind the plan.

   Before you execute dynamic SQL using the DB2() function, you must bind the plan (created in step 2 and specified in the DB2PLAN initialization parameter) to the target DB2 address space.