CHANGE_NRG_LINK procedure

The CHANGE_NRG_LINK procedure changes a link in one or all of the Db2® Mirror Network Redundancy Groups (NRGs) on the source node.

Authorization: The privileges held by the authorization ID of the statement must include *IOSYSCFG special authority. For the authority needed to use this procedure, see Authorization.

Read syntax diagramSkip visual syntax diagram CHANGE_NRG_LINK ( NRG_NAME =>  nrg-name , SOURCE_ADDRESS =>  source-address ,TARGET_ADDRESS => target-address,LINK_PRIORITY => link-priority,LINE_DESCRIPTION => line-description,VIRTUAL_LAN_ID => virtual-lan-id,RDMA_TYPE => rdma-type )

The schema is QSYS2.

nrg-name
A character or graphic string that contains the name of the NRG where the link is to be changed.
The valid NRG names and their primary uses are:
MIRROR_DATABASE
NRG for immediate replication of database-related objects and operations.
  • Object types: *DTAARA, *ENVVAR, *FILE, *JOBD, *JRN, *LIB, *PGM, *SQLPKG, *SQLUDT, *SQLXSR, *SRVPGM, and *SYSVAL.
  • SQL Data Definition Language operations.
  • Start of changeReplication due to the restore of an object.End of change
MIRROR_ENGINE
NRG used by the Db2 Mirror engine to manage the Db2 Mirror environment.
MIRROR_IFS
NRG used for accessing Integrated File System (IFS) data.
MIRROR_OTHER
NRG for immediate replication of security objects, security attributes, and non-database objects or operations.
  • Object types: *AUTL, *DTAQ, *FCNUSG, *JOBQ, *OUTQ, *SECATR, *SPLF, Start of change*USRIDX,End of change *USRPRF, and Start of change*USRSPCEnd of change.
  • Replication of objects due to Replication Criteria List changes.
  • Comparison of objects between the two nodes.
MIRROR_RESYNC
NRG for resynchronization of objects and data that were changed while replication was suspended.
The following special value is also allowed.
*MIRROR
This link will be changed in all of the Db2 Mirror NRGs.
source-address
A character or graphic string that contains the local IP address for the link to change. Either an IPv4 or an IPv6 address can be specified.
target-address
A character or graphic string that contains a new remote IP address for the link. Either an IPv4 or an IPv6 address can be specified. The remote IP address can only be changed if the NRG has a state of INACTIVE.

This parameter is optional. If it is omitted, the remote IP address for the link will not be changed.

link-priority
An integer value to set as the priority of the link. The range of priorities is from 1 to 16, where 1 is the highest priority.

This parameter is optional. If it is omitted, the link priority will not be changed.

line-description
A character or graphic string that contains the local system line description associated with this link. This parameter only applies when source-address is an IPv6 link-local address and is used to identify a unique local interface. It is ignored for all other addresses.
virtual-lan-id
An integer value for the local virtual LAN identifier associated with this link. This parameter only applies when source-address is an IPv6 link-local address and is used to identify a unique local interface. It is ignored for all other addresses.
Start of changerdma-typeEnd of change
Start of changeA character or graphic string that indicates the type of RDMA protocol associated with this link. The RDMA type can only be changed when the NRG state is INACTIVE. The link will not start if the RDMA type is set to different values on the source and target nodes. End of change
Start of changeThis parameter is optional. If it is omitted, the RDMA type of the link will not be changed.End of change
Start of change
ROCE V1
RoCE version 1 is a non-encrypted and non-routable RDMA protocol. It transfers data using the Ethernet link layer protocol with Ethertype 0x8915 which allows communication between two hosts within the same Ethernet broadcast domain. Communicating host IP addresses must be in the same Ethernet broadcast domain and in the same subnet. This type of link will start only if non-encrypted RDMA is allowed in your environment.
ROCE V2
RoCE version 2 is a non-encrypted and routable RDMA protocol. It is an internet layer protocol which enables packets to be routed. Data is not encrypted and is transferred using the UDP protocol and UDP destination port number 4791. This type of link will start only if non-encrypted RDMA is allowed in your environment.
ENCRYPTED ROCE V2
Encrypted RoCE version 2 is an encrypted and routable RDMA protocol. RoCE version 2 with IPsec encryption is an internet layer protocol which enables packets to be routed securely by using IPsec protocols to provide data authentication, integrity, and confidentiality. A VPN connection must be configured for each RDMA link endpoint with data transforms (encryption protocols) supported by the adapter. A VPN connection must be available for the RDMA link to start. If the VPN connection is ended, the RDMA link is also ended. Data is encrypted using IPsec and transferred using the UDP protocol and UDP destination port number 4791.
End of change

Example

  • Change a link's priority to 5 in all Network Redundancy Groups on the source node. 
    CALL QSYS2.CHANGE_NRG_LINK(NRG_NAME => '*MIRROR',
                           SOURCE_ADDRESS => '9.5.94.95',
                           LINK_PRIORITY => 5);