Creating a target connection

Edit online

Before using IBM® Z Database Assistant, you need to create a connection to a target Db2® subsystem that contains the workloads to be optimized.

Before you begin

IBM Z Database Assistant uses the ADMIN_COMMAND_DB2 stored procedure to perform various Db2 display commands. If you have not previously done so, complete the instructions in Installation step 21: Configure Db2 for running stored procedures and user-defined functions and Installing Db2-supplied routines during installation to create the ADMIN_COMMAND_DB2 stored procedure.

IBM Z Database Assistant needs profile tables for some of its functions. Before creating target connections, ensure that profile tables are defined. See Profile tables for more information about profile tables.

As part of the task of creating a target connection you are required to create a IBM Z Database Assistant target catalog. See Creating a IBM Z Database Assistant target catalog and granting privileges to the IDs that require access to the IBM Z Database Assistant target catalog.

In order to create a target connection from the user interface, you need the following:
  • Privileges granted by hlq.SAURSAMP(AURGMUSR), the owner of the IBM Z Database Assistant metadata database, or SYSADM or higher on the metadata Db2 system. This gives you the privileges needed to modify the metadata catalog information about the target connection.
  • Privileges granted by hlq.SAURSAMP(AURGTUSR), the owner of the DSNMLDB1 database, or SYSADM or higher on the target Db2 system to which you plan to create a connection. This gives you the privileges needed to configure the ML feature on the target Db2 system.
    Note: If the metadata Db2 and target Db2 are on different systems, the user ID used to create the target connection must exist on the target system.

When the IBM Z Database Assistant SQL tuning background task daemon performs a rebind, it uses the ADMIN_COMMAND_DSN procedure to perform this function.

ADMIN_COMMAND_DSN is a REXX language procedure that generates and reads job output and thus needs access to the RACF JESSPOOL class. In order for this procedure to access the JESSPOOL class, UPDATE privilege to the following RACF profile is needed for the target scheduler ID:
<SYSTEM_NAME>.<WLM_PROC_STARTED_TASK_OWNER>.<WLM_ENVIRONMENT>.**
The following example gives the target scheduler ID IBM Z Database Assistant update access to the required profile:
RDEFINE JESSPOOL STLABDC.DB2PROD.DB0BWLMR.** UACC(NONE)
PERMIT STLABDC.DB2PROD.DB0BWLMR.** CLASS(JESSPOOL) ID(<ZDBA_TSID>) ACCESS(UPDATE)
SETR RACLIST(JESSPOOL) REFRESH
where <ZDBA_TSID> is the target scheduler ID.
Note: Note: this RACF profile may already be covered by an already-created generic profile. Check your RACF profiles in the JESSPOOL class to verify.

About this task

You must complete this process for each target connection you want to create.

Procedure

To create a connection:

  1. From the Manage connections page, click Create connection.
  2. In the Create connection dialog, select Db2, then click Next.
  3. Enter the target connection settings:
    • Connection name
    • Connection description (optional)
    • APPLNAME
      Note: For more information about the APPLNAME, see Enabling Db2 to receive RACF PassTickets.
    • Scheduler ID
      Note: The scheduler ID must be granted the access it needs on the target catalog on the specified connection. Customize and run hlq.SAURSAMP(AURGTSID) to grant the authorizations to that ID.
    • Host
    • Port
    • Location
    • Additional JDBC properties (optional)
      Notes:
      • If ICSF has not been set up on the LPAR in which the target connection will run, you must specify the following in the Additional JDBC properties field:
        securityMechanism=3;
        This setting tells the JDBC driver to pass the user ID and password in the clear, which removes the requirement for ICSF.
      • If you choose to use the non-default collection ID for the JDBC package, you must specify the collection ID here; for example:
        currentPackagePath = jdbc-package-collection-id, DSNAURA;
        Note: DSNARUA must be included in order for the SQL tuning function to work properly.

  4. Click Create connection at the bottom of the page to create the target connection.