DB2 Server for VSE: System Administration

Setting the Default Application Requester DBCS Option

The VSE application requester DBCS option is set by the DBCS option contained in the SQLGLOB file, as follows:

• Batch applications use the SQLGLOB file 'DBCS' option associated with the userid(s) contained on the SQL CONNECT statement(s) used in the application. If any of these userids are NOT defined in the SQLGLOB file, then the global DBCS will be used.
• The preprocessor is a batch application requester. The userid given by the 'USERID' preprocessor parameter will be used to determine the DBCS option from the SQLGLOB file. If the userid is not defined in the SQLGLOB file, the global default DBCS value will be used.
• The Database Services Utility is a batch application requester. It uses the SQLGLOB file global DBCS value.
• ISQL is an online application requester. It has a CICS user ID associated with it. Therefore, ISQL uses the user setting of the SQLGLOB parameter DBCS if the ISQL user had used the DSQU transaction to override the global setting of the DBCS parameter. Otherwise, ISQL uses the global setting of the SQLGLOB parameter DBCS.

  Note:

  If ISQL is running against a remote DRDA application server, the ISQL user must ensure that the global and the user setting of the SQLGLOB parameter DBCS are the same. ISQL has a two transaction structure: ISQL and CISQ. ISQL starts CISQ. The former controls the terminal and the latter is for access to the application server. Because CISQ is a transaction started by ISQL, it does not have a CICS user ID associated with it. Therefore, the online DRDA resource adapter uses the global setting of the SQLGLOB parameter DBCS to process the SQL requests from CISQ. On the other hand, ISQL, being the front-end transaction, has a CICS user ID associated with it. Therefore, ISQL uses the user setting of the SQLGLOB parameter DBCS, if available, to process the same SQL statement it received from the terminal.

• All "started" CICS transactions that pass SQL requests to a remote DRDA application server do not have a CICS user ID associated with it. Therefore, these transactions will use the global setting of the SQLGLOB parameter DBCS.
• All online DRDA application requesters have a CICS user ID associated with it. Therefore, they will use the user setting of the SQLGLOB parameter DBCS if the CICS user running the online DRDA transaction had used the DSQU transaction to override the global setting of the DBCS parameter. Otherwise, they will use the global setting of the SQLGLOB parameter DBCS.

If you want to check the global setting for the SQLGLOB parameter DBCS, use the DSQQ transaction without specifying any parameter. The DBCS displayed is the global setting of the SQLGLOB parameter DBCS.

If you want to check the DBCS setting for a CICS user, use the DSQQ transaction and specify the user ID of the CICS user. If the user setting exists, it will be displayed. If the user setting does not exist, a message will be displayed.

For more information about the DSQQ transaction, see the DB2 Server for VSE & VM Database Administration.

If you want to use the IBM-supplied default global settings for the SQLGLOB parameters (including the default for DBCS), you must execute the IBM-supplied job control program ARISGDEF. This program will initialize the global settings for the SQLGLOB parameters. (For more information on the default values for the SQLGLOB parameters, see the DB2 Server for VSE & VM Database Administration manual.)

If you want to use your own default global settings for the SQLGLOB parameters (including the default for DBCS), you must first execute the IBM-supplied job control program ARISGDEF and then execute the DSQG transaction.

To specify YES as the new global setting for the SQLGLOB parameter DBCS, run the DSQG transaction and specify the YES DBCS value as follows:

  DSQG ,,YES

The global settings for the SQLGLOB parameters do not apply to online application requesters that have already run the DSQU transaction (and thereby have their own user SQLGLOB parameter values).

For more information about the DSQG transaction, see the DB2 Server for VSE & VM Database Administration manual.

To specify a user setting for the SQLGLOB parameter DBCS which is different from the default setting, run the DSQU transaction and specify the DBCS value. This value overrides the global setting for the user who ran the DSQU transaction.

For example, to specify YES as the new user setting for the SQLGLOB parameter DBCS for the CICS user CICSUSER, CICSUSER must sign on to a CICS session, run the DSQU transaction and specify the YES DBCS value as follows:

  DSQU ,,YES

For more information about the DSQU transaction, see the DB2 Server for VSE & VM Database Administration manual.

The SQLGLOB File Batch Query/Update Program can also be used to display or modify user or global default parameters. For more information, see The SQLGLOB File Batch Query/Update Program, or the DB2 Server for VSE & VM Database Administration.