Notes

• Connecting to a database server resets the database authorization ID.
• The default database authorization ID for each server is system defined.
• Changing the database user will change the USER special register. The QMF session will operate with the privileges held by the newly established runtime authorization ID.

  This can be useful in the following situations:

  • To perform privileged database administration tasks by changing the connection to a DBA userid.
  • In batch jobs to set the database user to something different than the batch machine's userid.
• Your DB2 for VM user password can be set or changed by running a QMF SQL Query with a GRANT SQL statement. For example:

  GRANT CONNECT TO &DSQAO_CONNECT_ID  
      IDENTIFIED BY password

• The database authorization ID at a DB2 for OS/390 server can be changed by running a QMF SQL Query with a SET CURRENT SQLID statement. For example:

    SET CURRENT SQLID = 'QMFADM'

  The QMF session is connected to a DB2 for OS/390 server when the global variable DSQAO_DB_MANAGER has the value of 2.

• The database authorization ID cannot be changed when the global variable DSQAO_DB_MANAGER has the value of 3 or 4.
• Differences between the CONNECT command and the DSQSDBNM program parameter:
  • The DSQSDBNM parameter establishes the initial database server used for the QMF session.
  • The CONNECT command changes the database server after a QMF session is established.
• The SQL CONNECT statement cannot be used in a QMF query.