Using QMF

Example 1: How connecting to a new location affects your user ID

DB2 for VM application requester and a DB2 for VM application server: When you connect to a new location, your DB2 for VM user ID is not in effect after a connection to a different location. Instead, it is based on the VM logon ID at the previous location.

• Assume that your VM logon ID at MIAMI is DAVID and that you first connect to your local DB2 for VM DBMS (MIAMI):

   CONNECT DANIEL (Password=PWDAN
  

  This command sets your DB2 for VM user ID at MIAMI to DANIEL.

• Now, you connect to another DB2 for VM DBMS (DETROIT):

   CONNECT TO DETROIT
  

• Your DB2 for VM user ID at DETROIT is DAVID, not DANIEL.

DB2 for VM application requester and a DB2 for OS/390 application server: You can set your user ID to DANIEL at a new location by using the SET CURRENT SQLID SQL statement, if your DBMS at that location is DB2 for OS/390, and you are connected to that location.

• Assume that your VM logon ID at MIAMI is DAVID. Also assume that you first connect to your local DB2 for VM DBMS (MIAMI):

   CONNECT DANIEL (Password=PWDAN
  

  This command sets your DB2 for VM user ID to DANIEL. Now, you connect to a DB2 UDB for OS/390 DBMS (DALLAS):

   CONNECT TO DALLAS
  

• Assuming no name translation, your user ID at DALLAS is DAVID, not DANIEL. However, because you connected to a DB2 UDB for OS/390 location, you can use the following SQL statement to change your user ID (your current SQL authorization ID) to DANIEL at this location:

   SET CURRENT SQLID = 'DANIEL'
  

Because SET CURRENT SQLID is an SQL statement, you issue it through an SQL statement. Consequently, the following restrictions apply to the user ID you specify:

• You must enclose it within single quotes.
• It must be your primary ID or one of your secondary authorization IDs.