Relationship Service

Use this page to view and set the configuration properties for the relationship service.

To view this page in the administrative console, click Integration Applications > Relationship Manager > Relationship Services configuration.

To link to relationships that this relationship service manages, click Relationships.

Required security role for this task: When security and role-based authorization are enabled, you must be logged in as a configurator or an administrator to modify the configuration properties. Any WebSphere security role can view this configuration.


Links marked (online) require access to the Internet.

Check for updates to this topic (online)

Name

Specifies the name of the current relationship service. This field is automatically set.

Relationship service version

Specifies the current version of the installed relationship service. This field is automatically set.

Query block size (relationship instance count)

Specify the maximum cache that the relationship service should set aside for relationship queries. This setting determines the size of the query results set. By default, 5000 relationship instances are read at once.

Data source

Specify the default data source for the relationship service by entering the Java Naming and Directory Interface (JNDI) name of a data source defined at the cell level. This is where the tables for relationship service are stored. Each relationship-related schema is created in this data source by default.

Data source is on z/OS

Select the check box in this field if your data source is on a machine running a z/OS operating system. After selecting the check box, the following additional fields display on the page.

Database for table creation

Specify the name of the z/OS datasource.

Storage group

Specify the name of the storage group for the relationship services database. A storage group is a list of Direct Access Storage Device (DASD) volumes on which DB2 can allocate data sets for associated storage structures. DB2 storage group names are unqualified identifiers of up to 128 characters (DB2 version 7 has an 18-character qualifier limit). A DB2 storage group name cannot be the same as any other storage group name in the DB2 catalog.

Tablespace for table creation

Specify the name for the table space. A table space is a storage structure that can hold one or more base tables. The name, qualified with the database-name implicitly or explicitly specified by the in clause, must not identify a table space, index space, or large object (LOB) table space that exists at the current server.

WLM Environment

Identify the Workload Manager (WLM) environment in which the stored procedure will run when the DB2 stored procedure address space is WLM-established. The name of the WLM environment is an SQL identifier. If you do not specify the WLM Environment attribute, the stored procedure runs in the default WLM-established stored procedure address space specified at installation time.

Binding options

Specify the options you want to use to bind your SQL stored procedure package. The maximum length is 1024 characters.

Package collection ID

Identify the package collection to use when executing the stored procedure. This is the package collection for binding the database request module collection (DBRM) that is associated with the stored procedure.

Compiler options

Specify the options for compiling the C language program that DB2 generates for the SQL procedure. The maximum length is 255 characters.

Precompiler options

Specify the options for precompiling the C language program that DB2 generates for the SQL procedure. The maximum length is 255 characters.

Language Environment

Specify the options to pass to the Language Environment for execution of your module. The Language Environment is a strategic execution environment used to run the C language program that DB2 generates for the SQL procedure. The parameter entered in this field will be ignored for other functions. The maximum length is 254 characters.

Builder schema

Specify the schema name for the procedure processor entered in the Builder parameter. Usually this is SYSPROC for version 5, and could be any name in version 6.

Builder

Specify the procedure name attribute when calling the z/OS procedures processor (usually DSNTPSMP). You can create several stored procedure definitions for DSNTPSMP, each of which specifies a different WLM environment. Calling DSNTPSMP using the name in this parameter, DB2 runs DSNTPSMP in the WLM environment that is associated with the procedure name. The maximum length is 18 characters.