DB2 Server for VSE: System Administration

Setting the Application Requester Default CHARNAME and CCSIDs

VSE application requesters use the CHARNAME that is specified in the SQLGLOB file, either a specific userid's value or the global default value as follows:

• Batch applications use the SQLGLOB file 'CHARNAME' setting 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 CHARNAME will be used.
• The preprocessor is a batch application requester. The userid given by the 'USERID' preprocessor parameter will be used to determine the CHARNAME from the SQLGLOB file. If the userid is not defined in the SQLGLOB file, the global default CHARNAME value will be used.
• The Database Services Utility is a batch application requester. It uses the SQLGLOB file global CHARNAME setting to determine the input data folding translation table to be used. Otherwise, it will use the SQLGLOB file 'CHARNAME' setting associated with the userid(s) contained on the SQL CONNECT statement(s) used in the application. If any of these are NOT defined in the SQLGLOB file, then the global CHARNAME will be used.
• 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 CHARNAME if the ISQL user had used the DSQU transaction to override the global setting of the CHARNAME parameter. Otherwise, ISQL uses the global setting of the SQLGLOB parameter CHARNAME.

  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 CHARNAME 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 CHARNAME 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 CHARNAME, 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 CHARNAME.
• All online DRDA application requesters have a CICS user ID associated with it. Therefore, they will use the user setting of the SQLGLOB parameter CHARNAME if the CICS user running the online DRDA transaction had used the DSQU transaction to override the global setting of the CHARNAME parameter. Otherwise, they will use the global setting of the SQLGLOB parameter CHARNAME.

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

If you want to check the CHARNAME 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 CHARNAME), you must execute the IBM-supplied job control program ARISGDEF. This program will initialize the global settings for the SQLGLOB parameters with IBM-supplied default values. (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 CHARNAME), you must first execute the IBM-supplied job control program ARISGDEF and then execute the DSQG transaction.

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

DSQG ENGLISH

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.

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

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

DSQU ENGLISH

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

The SQLGLOB File Batch Query/Update Program

This program can be used to query and update the SQLGLOB file in batch mode, using the JCL in library member ARISBGUD.Z. It may be necessary to use this program to add or change SQLGLOB parameters when CICS and the DSQx transactions are not available, or for userids that do not exist under CICS, but are in batch jobs that access remote servers. With this program, any userid's SQLGLOB parameters can be queried, inserted, updated or deleted. The Global Default parameters cannot be deleted. For more information about this batch program, see the DB2 Server for VSE & VM Database Administration.