DB2 Server for VM: System Administration


Changing the Server Name and Resource Identifier

Situations exist where you may want to change the application server name or the resource identifier. For example, you may want to change an application server name from 8 to 18 characters or have it conform to your naming conventions, or you may want to change a resource identifier name to a registered DRDA TPN.

The first character of the application server name must be an uppercase letter (A-Z), followed by alphanumeric characters. The name must be from 1 to 18 characters.

The following example shows how to rename an application server with a character resource identifier. In this example, the DB2 Server for VM production minidisk is assumed to be the Q-disk, and an application server with a DBNAME of dbname1 and a RESID of resid1 will be renamed to dbname2 resid2.

Notes:

  1. In a DRDA2 environment, the database manager uses the RESID to create its own log name. Therefore, before changing the server name, ensure that any DRDA2 in-doubt agents have been resolved. Once the server name has changed, use the RESET CRR LOGNAMES command to clear old log names. When the database manager is next started with the initialization parameters PROTOCOL=AUTO and SYNCPNT=Y and Resynchronization Initialization occurs, the DB2 Server for VM log status will be COLD.

  2. If the RESID NAMES Q file is not on the production minidisk, use XEDIT to create the file. Create it with one entry that has the following three tags:
      :nick
      :dbname
      :resid
    

  1. Access the Q-disk with write capability.
  2. Enter the CMS command:
       FILELIST resid1 * Q
    

    A list of files from the Q-disk is displayed. Three files are on the Q-disk for each application server:

    1. resid1 SQLDBGEN
    2. resid1 SQLDBN
    3. resid1 SQLFDEF
  3. Rename the file name of each file:
       RENAME / resid2 SQLDBGEN Q
       RENAME / resid2 SQLDBN Q
       RENAME / resid2 SQLFDEF Q
    
  4. Edit resid2 SQLDBN Q:
       XEDIT resid2 SQLDBN Q
    

    This file contains a statement similar to the following:

       DBMACHID=Dbmachid,DCSSID=Dcssid,DBNAME=dbname1
    

    Replace the DBNAME value (DBNAME=dbname1) with your new server name:

       DBMACHID=Dbmachid,DCSSID=Dcssid,DBNAME=dbname2
    
  5. Edit RESID NAMES Q:

       XEDIT RESID NAMES Q
    

    In this file, you see the :DBNAME and :RESID tags. Replace the resource identifier resid1 with resid2, and dbname1 with dbname2.

    Before:
        :nick.      :dbname.dbname1  :resid.resid1
     
    After:
        :nick.      :dbname.dbname2  :resid.resid2
     
    
  6. If the old server name or resid (for example, TPN) is referenced by any CMS communication directory entries, you must update those directory entries.

After changing your application server name and resource identifier, ensure that users enter:

   SQLINIT DB(dbname2)

to identify the application server to be accessed.

When you want to start the renamed application server, specify the new server name when you enter SQLSTART:

   SQLSTART DB(dbname2)

The following example shows how to rename an application server, and how to change a resource identifier to a registered DRDA TPN. In this example, the DB2 Server for VM production minidisk is assumed to be the Q-disk, and an application server with a DBNAME of dbname1 and a RESID of resid1 will be renamed to dbname2 07F6C4C2. The RESID 07F6C4C2 represents the default DRDA TPN X'07F6C4C2'.
Note:If the RESID NAMES Q file is not on the production minidisk, use XEDIT to create the file. Create it with one entry that has the following three tags:
  :nick
  :dbname
  :resid

  1. Access the Q disk with write capability.
  2. Enter the CMS command:
       FILELIST resid1 * Q
    

    A list of files from the Q-disk is displayed. Three files are on the Q-disk for each application server:

    1. resid1 SQLDBGEN
    2. resid1 SQLDBN
    3. resid1 SQLFDEF
  3. Rename the file name of each file:
       RENAME / 07F6C4C2 SQLDBGEN Q
       RENAME / 07F6C4C2 SQLDBN Q
       RENAME / 07F6C4C2 SQLFDEF Q
    
  4. Edit 07F6C4C2 SQLDBN Q:
       XEDIT 07F6C4C2 SQLDBN Q
    

    This file contains a statement similar to the following:

       DBMACHID=Dbmachid,DCSSID=Dcssid,DBNAME=dbname1
    

    Replace the DBNAME value (DBNAME=dbname1) with your new server name:

       DBMACHID=Dbmachid,DCSSID=Dcssid,DBNAME=dbname2
    
  5. Edit RESID NAMES Q:
       XEDIT RESID NAMES Q
    

    In this file, you will see :DBNAME and :RESID tags. Replace the resource identifier resid1 with the hexadecimal value X'07F6C4C2' and dbname1 with dbname2.

    Before:
        :nick.      :dbname.dbname1  :resid.resid1
     
    After:
        :nick.      :dbname.dbname2  :resid.X'07F6C4C2'
     
    
  6. Enter a hexadecimal TPN value in the CMS communication directory by using the SET VERIFY ON HEX 1 72 command, and entering the hexadecimal digits.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]