Step 10: Configure one ADNR application per sysplex

ADNR reads configuration data from one file, which can exist as a z/OS® UNIX file, a PDS or PDSE member, or a sequential data set. If you plan to enable ADNR to move within the sysplex in the case of failure, the ADNR configuration file or data set should be on shared DASD, to make it accessible to all systems in the sysplex if necessary. The ADNR configuration file is specified on the CONFIG DD statement in the ADNR start procedure. A sample start procedure is provided in EZBADNRS in SEZAINST.

The ADNR configuration file serves five basic purposes:

Identifies the name servers to update and the zones to be updated in those name servers
Identifies the GWM to connect to and IP address to bind to for communications with the GWM
Identifies the sysplex resources to be managed by ADNR
Uniquely identifies the ADNR instance
Customizes optional statements

A sample ADNR configuration file is provided in EZBADNRC in SEZAINST.

Tip: Consistent with the Advisor and Agent configuration terminology, any statement or keyword containing the word connection refers to a local socket, and any statement containing the word id refers to a remote address and possibly a port.

The ADNR configuration file contains statements or keywords that reference other statements or keywords. All such references are made using labels.