Verify the CLI.INI file

About this task

Note: The CLI.INI file contains the configuration information for ODBC that ARSSOCKD uses to connect to the correct Db2® subsystem. This file is pointed to by the value of DSNAOINI. This value could be already set within your installation by a DSANOINI DD statement in JCL or as a HFS file as in the example. See Db2 for z/OS® ODBC Guide and Reference for more information about configuring the CLI.INI file.
The following shows an example of the CLI.INI file with the minimum keywords required; however, other keywords might be present.
[COMMON]
MVSDEFAULTSSID=DSNA
[DSNA]
PLANNAME=DSNACLI
Where:
MVSDEFAULTSSID=DSNA
Identifies to ODBC the Db2 subsystem name or group attachment name in a data sharing group.
PLANNAME=DSNACLI
If the plan for ODBC is not the default plan DSNACLI, you must specify the plan with PLANNAME=plan
Verify that the ARSSOCKD owner has execute privilege on the ODBC plan (for example, DSNACLI). If the ID does not have access, the customer needs to grant the access. One way to do that is
GRANT EXECUTE ON PLAN planname TO arssockd owner
Note: Content Manager OnDemand does not support the RRSAF value of the MVSATTACHTYPE keyword in the CLI.INI file. If the MVSATTACHTYPE keyword is specified, the value must be CAF (that is, MVSATTACHTYPE=CAF).

Content Manager OnDemand uses ODBC to issue SQL statements to the database. These ODBC connections are Db2 Call Attachment Facility (CAF/batch) connections. If you are using RACF to control access to Db2, the RACF DSNR profile would be db2sub.BATCH. The ARSSOCKD server needs to be permitted to that resource.

The total number of all Db2 batch connections is limited by the DB2 MAX BATCH CONNECT on panel DSNTIPB, or ZPARM IDBACK. ARSSOCKD will add to the number of batch connection used, and the IDBACK value might not be sufficient to accommodate the additional connections. For each ARSSOCKD that is started, ARS_NUM_DBSRVR + ARS_NUM_OAMSRVR + 3 can be used as a starting point for the number of connections used to determine if the IDBACK limit needs to be increased. Depending on exits and other settings, additional Db2 batch connections may be used by the server.