DB2 Server for VSE: System Administration

Using the DBS Utility on Remote Application Servers

For a user to be able to use the DBS utility on a remote DRDA target application server, you must first preprocess the DBS utility package on the target application server and then create the table SQLDBA.DBSOPTIONS on that application server. This is done by the DB2 Server for VSE application requester. You must then obtain the necessary program bind and table creation privileges for your authorization-id on the target application server.

Note:

If the target application server does not support the ERROR option when preprocessing, you must create the DB2 Server for VSE & VM system catalog tables on the target application server for the preprocessing to work. The database managers that do not support the ERROR option (such as the common server database managers) generally supply a command file that creates the necessary table definitions. The command file to create the tables for the DBS Utility is typically called SQLDBSU.CMD or SQLDBSU.BAT.

To create the DBS Utility package, do the following from a DB2 Server for VSE application requester:

1. Ensure that the remote server is identified in the application requester's DBNAME Directory and can be accessed via a TCP/IP network.
2. Preprocess the DBS Utility against the remote application server to create the DBS Utility package. Use the preprocessor options 'PREP=SQLDBA.ARIDSQL,BLK,ISOL(CS),NOPR,NOPU,CTOKEN(NO),ERROR' (omit the ERROR option if the target application server does not support it). Use the member 'ARIDSQLP.A' as the input to the preprocessor. See the DB2 Server for VSE & VM Application Programming manual for more information on preprocessing.
3. If you ran a command file to create the table definitions necessary for preprocessing, the DBSOPTIONS table should have been created for you. If this table does not exists, enter the following DBS Utility commands:

     SET ERRORMODE CONTINUE;
    
     CREATE TABLE SQLDBA.DBSOPTIONS
      (SQLOPTION VARCHAR (18) NOT NULL,
       VALUE     VARCHAR (18) NOT NULL);
    
     CREATE UNIQUE INDEX SQLDBA.DBSINDEX
      ON SQLDBA.DBSOPTIONS (SQLOPTION,VALUE);
    
     INSERT INTO SQLDBA.DBSOPTIONS
      VALUES ('RELEASE','7.1.0');
    
     COMMIT WORK;
   

You must now obtain the necessary program bind and table creation privileges for your authorization-id on the target application server.