Updating the BSDS for data sharing or DDF by using the DSNJU003 utility

You can use the DSNJU003 (change log inventory) utility to update the BSDS information related to Db2 data sharing and distributed database facility (DDF) communication. The information is stored in the bootstrap data sets (BSDSs) of Db2 data sharing group members.

You can use the following DSNJU003 statements update information for DDF or data sharing in the BSDS. For the syntax of each statement, see DSNJU003 (change log inventory).

Distributed Data Facility (DDF)

The DDF statement updates the LOCATION and other DDF related information in the BSDS.

If you use this statement to insert new values into the BSDS, the DDF statement must include TCP/IP information, SNA information, or both, and any elements you want to remove from the BSDS. To update an existing set of values, you only need to include values that you want to change. The DDF record cannot be deleted from the BSDS after it has been added, it can only be modified.

DRDA port (PORT=port)

The DRDA port is the TCP/IP port number that is used by the DDF to accept incoming connection requests. The recommended DRDA port is 446.

If you change this value for one member of the group, you must change it for all members. Db2 requires that all members of a data sharing group use the same, well-known port number to receive incoming connection requests.

Generic LU name (GENERIC=gluname)

The generic LU name represents all the members of a data sharing group, in either an SNA network or a TCP/IP network.

If you change this value for one member of the group, you must change it for all members. All members of a data sharing group must specify the same name.

GRPIPV4

The GRIPV4 keyword option identifies a constant IPV4 address to be associated with the data sharing group for which this DDF is a member.

It is used for the purposes of accepting incoming connection requests that can be serviced by any member of the data sharing group. This address must be entered in dotted decimal form. An associated IPV4 subsystem/member address (see IPV4) must also be specified in order to identify the IP address associated to this specific member of the group. If an IP address is not specified, Db2 will automatically determine the IP address from TCP/IP. It is strongly recommended that you refer to a Sysplex distributor owned distributing dynamic virtual IP address (DVIPA).

GRPIPV6

The GRIPV6 option identifies a constant IPV6 address to be associated with the data sharing group for which this DDF is a member.

It is used for the purposes of accepting incoming connection requests that can be serviced by any member of the data sharing group. This address must be entered in colon hexadecimal form. An associated IPV6 subsystem/member address (see IPV6) must also be specified in order to identify the IP address associated to this specific member of the group. If an IP address is not specified, Db2 will automatically determine the IP address from TCP/IP. It is strongly recommended that you refer to a Sysplex distributor owned distributing dynamic virtual IP address (DVIPA).

IPV4=ipv4-address

The IPFV4 keyword option identifies a constant IPV4 address to be associated to DDF for the purposes of accepting incoming connection requests to this specific subsystem only.

This address must be entered in dotted decimal form. If an IP address is not specified, Db2 will automatically determine the IP address from TCP/IP. When Db2 is a member of a data sharing group, it is strongly recommended that you refer to a dynamic virtual IP address (DVIPA). A group IP address should also be specified.

IPV6=ipv6-address

The IPFV6 keyword option identifies a constant IPV6 address to be associated to DDF for the purposes of accepting incoming connection requests to this specific subsystem only.

This address must be entered in colon hexadecimal form. If an IP address is not specified, Db2 will automatically determine the IP address from TCP/IP. When Db2 is a member of a data sharing group, it is strongly recommended that you refer to a dynamic virtual IP address (DVIPA). A group IP address should also be specified.

Location aliases (ALIAS=alias-name:alias-port:alias-secport)

Location aliases can represent one, several, or all members of a data sharing group for member specific access, to enable clients to continue to connect to a member's old location name, and for defining subsets of data sharing groups.

Location aliases can be defined without an alias-port or alias-secport value. Clients that use a location alias without an alias-port or alias-secport value receive information only about the member that processes the connection request in the list of servers. To distribute work requests across the members or a subset of a group, clients must be configured to use the Db2 group location name or location alias that is defined for a subset of members. For location aliases that are defined by the DNJU003 utility, alias-port and alias-secport values are ignored in non-data sharing environments.

Tip: You can define and manage only 8 static location aliases by using the DSNJU003 utility. However, you can also define additional dynamic location aliases by using the MODIFY DDF command. When a static alias is defined with the same name as an existing dynamic alias, Db2 uses only the dynamic alias. Dynamic location aliases, unlike those defined by the DSNJU003 utility, can be added, modified, and deleted without stopping and restarting Db2 or DDF. For more information, see Member-specific location aliases.

Resynchronization port (RESPORT=resport)

The resynchronization port is the TCP/IP port number that is used by the DDF to accept incoming DRDA two-phase commit resynchronization requests.

Db2 requires that each member of a data sharing group in a TCP/IP network have a resynchronization port number that is unique within the Parallel Sysplex®. In the event of a failure, this unique port number allows a requester to reconnect to the correct member so that units of work that require two-phase commit can be resolved.

Secure port (SECPORT=secport)

The secure port identifies the TCP/IP port number that is used by DDF to accept inbound secure DRDA connection requests.

This value must be a decimal number in the range 0–65535; zero indicates that the DDF secure connection support for TCP/IP is deactivated. If the secure port has not been specified, remote connections can still use the DRDA PORT, and use SSL on it, but DDF does not validate whether that the connection is using SSL protocol.

Important: Before updating any of the information related to Db2 data sharing, have all members check for the existence of indoubt threads. If any indoubt threads exist, resolve them before making any updates. To check for indoubt threads, use the DISPLAY THREAD command.