Configuring multiple Data Virtualization Manager servers as peers

Edit online

Configure your Data Virtualization Manager servers to use the Integrated DRDA Facility (IDF) for peer-to-peer communication.

About this task

Use the following procedure to configure multiple Data Virtualization Manager servers as peers using IDF.

The procedure uses the following terminology:

Local server. The Data Virtualization Manager server that is the requester in the peer-to-peer relationship.
Remote target peer server. The Data Virtualization Manager server that is the target in the peer-to-peer relationship.

DRDA is used to request and receive data from peer targets. As indicated in the procedure, you will use DEFINE DATABASE configuration commands to describe TYPE(PEER) IDF target servers.

Procedure

Configure the remote target Data Virtualization Manager server to activate the Integrated DRDA Facility (IDF) by setting the following start-up parameters:

MODIFY PARM NAME(IDFPACKAGEPATH)     VALUE(path)
MODIFY PARM NAME(IDF)                VALUE(YES|NO)
MODIFY PARM NAME(IDFALREADYVERIFIED) VALUE(CLIENT|SERVER)
MODIFY PARM NAME(IDFLOCATION)        VALUE(location) 
MODIFY PARM NAME(IDFPORT)            VALUE(port)
MODIFY PARM NAME(OEPORTNUMBER)       VALUE(port)

The following table describes these server parameters:


Parameter	Description	Valid values
IDFPACKAGEPATH	zFS file directory that the server uses to store and retrieve bound SQL statement packages. The server MUST have read, write, and search access to this directory path. The path name must be absolute (begin with “/”). An ending “/”, if omitted, is supplied by the server. If this parameter is not supplied the IDF facility will be disabled during start-up.	A zFS directory absolute path name from 1 to 96 character in length.
IDF	IDF (Integrated DRDA Facility Activated) Determines whether IDF will be activated for the current start-up or remain inactive.	YES Activate IDF. NO IDF is not active. Default: NO
IDFPORT	IDF TCP/IP MAIN PORT TCP/IP port number on which the server listens for in-bound DRDA session requests.	Any available port number appropriate for your site. Default: 50000
IDFSSLPORT	IDF TCP/IP SSL PORT TCP/IP port number on which the server listens for in-bound DRDA SSL session requests.	Port number for SSL listener. When not set, SSL requests cannot be serviced. Default: None
IDFLOCATION	IDF LOCATION NAME DRDA location name. It is recommended that the same standard used to assign DRDA location names to Db2 subsystems be used for IDF.	A valid value is a string 1 - 16 characters. Default: '`lparssid`', where `lpar` is the SMFID of the LPAR and `ssid` is the server subsystem ID.
IDFALREADYVERIFIED	IDF ALREADY-VERIFIED SECURITY REQUIRED Specifies the minimum authentication level that can be used when a client connects to the IDF DRDA Application Server.	SERVER Requires a valid z/OS user ID and password. CLIENT Only a valid user ID must be supplied; a password is not required. Default: SERVER
OEPORT	Port number. This parameter is required for the Data Virtualization Manager studio to obtain metadata directly from the target.

Note: It is recommended that the other IDF-related parameters be allowed to default unless you have specific requirements for their use.

On the local server, define each remote target peer server as a peer-type database server, as follows:

DEFINE DATABASE TYPE(PEER)
       NAME(name) 
       DDFSTATUS(ENABLE)
       DOMAIN(your.domain.name)
       SECMEC(USRIDONL) 
       LOCATION(location)
       PORT(port)
       OEPORT(port)
       OESSLPORT(port)
       CCSID(ccsid)

The following table describes these parameters:


Parameter	Description	Valid values
CCSID	The EBCDIC single-byte application CCSID (Coded Character Set Identifier). This value must match the `SQLENGDFLTCCSID` value specified for the target server. (Required)	Refer to the data source vendor documentation for a list of valid CCSID values.
DDFSTATUS	The DDF activation status. (Required)	ENABLE Make this DDF definition active. DISABLE DDF endpoint is not used.
DOMAIN	The domain name or hostname on which the Data Virtualization Manager server is running. Either DOMAIN or IPADDR is required, but not both.	No default value
IPADDR	The dot-notation IPV4 or IPV6 address of the host on which the Data Virtualization Manager server is running. Either DOMAIN or IPADDR is required, but not both.
LOCATION	DRDA location name. This value must match the `IDFLOCATION` value specified for the target server.	A valid value is a string 1 - 16 characters.
NAME	Target server name.	A valid value consists of 1 - 4 characters.
PORT	This value must match the `IDFPORT` value specified for the target server.	1 - 65535
OEPORT	This value must match the `OEPORT` value specified for the target server.	1 - 65535
OESSLPORT	Sets the port number that is used to LISTEN for and ACCEPT all inbound encrypted OE Sockets TCP/IP sessions. This port number should be reserved for use only by the main product address space. Each copy of the main product address space needs its own port number if SSL over OE Sockets is being used. There is no default value for the SSL port number if the value is not set in the initialization EXEC.	Null
SECMEC	The DRDA security mechanism in force. This value depends on the `IDFALREADYVERIFIED` value specified for the target server.	USRIDPWD User ID and password are sent as is. No encryption is used. Use this setting if `IDFALREADYVERIFIED` is set to `SERVER` for the target server. USRIDONL User ID is sent as is. No encryption is used for the user ID only (client security). Use this setting if `IDFALREADYVERIFIED` is set to `CLIENT` for the target server.
TYPE	Defines the DDF endpoint type. PEER DDF endpoint is an IDF target server.	When using IDF for peer-to-peer communication between servers, PEER is the valid value.

Example

The following example shows the settings in a peer-to-peer server configuration using IDF.

On the remote target peer server, the following start-up parameters are defined:

MODIFY PARM NAME(IDF)                VALUE(YES)
MODIFY PARM NAME(IDFALREADYVERIFIED) VALUE(CLIENT)
MODIFY PARM NAME(IDFLOCATION)        VALUE(ZOS1RDBF) 
MODIFY PARM NAME(IDFPORT)            VALUE(9999)
MODIFY PARM NAME(OEPORT)             VALUE(9991)
MODIFY PARM NAME(OESSLPORTNUMBER)    VALUE(0)
MODIFY PARM NAME(SQLENGDFLTCCSID)    VALUE(1047)

On the local server, the remote target peer server is defined as follows:

DEFINE DATABASE TYPE(PEER)
       NAME(RDBF) 
       DDFSTATUS(ENABLE)
       DOMAIN(zos1.domain.name)
       SECMEC(USRIDONL) 
       LOCATION(ZOS1RDBF) 
       PORT(9999)
       OEPORT(9991)
       OESSLPORT(0)
       CCSID(1047)

The following table summarizes how the values correlate:


Server start-up parameter on remote target peer server	Database definition for remote target peer server on local server
IDFALREADYVERIFIED	SECMEC
IDFLOCATION	LOCATION
IDFPORT	PORT
OEPORT	OEPORT
SQLENGDFLTCCSID	CCSID

IDF for load balancing

The Terminal Owning Regions (TOR) and Data Owning Regions (DOR) uses IDF for load balancing/routing capability. The AVZIDFRR rule facilitates query distribution across different IDF targets by utilizing a comma-delimited list of servers specified in the GLOBAL1.AVZIDFRR variable. To implement a round-robin approach for queries, follow these steps:

Create identical virtual tables on two or more IDF servers with default naming conventions. For example, IDB1_STAFFVS and IDB2_STAFFVS.
Define the global variable GLOBAL1.AVZIDFRR with a comma-separated list of servers. For example, IDB1,IDB2.
Activate the rule and query tables using the IDFRR_tablesuffix pattern. For example:
```
SELECT * FROM IDFRR_STAFFVS
```
In this setup, each query substitutes IDFRR_ with the first server’s name in the GLOBAL1.AVZIDFRR.

What to do next

Use the Data Virtualization Manager studio to create virtual table data maps using information provided by the remote target peer server. See Creating virtual maps for tables on a peer server.