Step 5: Define one ADNR application per subplex
If resources in a subplex were previously managed by ADNR, to define one ADNR application per subplex, see the following steps (in Steps for configuring automated domain name registration):
- Step 7: Define security server profiles for ADNR
- Step 8: Configure ADNR to automatically restart in case of application or system failure (optional)
- Step 9: Configure and start syslogd (optional, but required to have ADNR write log messages and trace data to syslogd)
- Step 10: Configure one ADNR application per sysplex
- Step 11: Customize the TCP/IP profiles of the TCP/IP stacks on which ADNR and the LBA applications are to run (optional)
Also, for special considerations when migrating ADNR to a subplexing environment, see:
- Step 6: Assign the host_group and server_group statements from the sysplex ADNR configuration to the correct subplex domains
- Step 7: Configure the new ADNR instances to update the name server and zone for its subplex
- Step 8: Configure the new ADNR instances to communicate with the subplex Advisor
Guideline: In a Common INET (CINET)
environment, use stack affinity to ensure that each subplex ADNR instance
is using a TCP/IP stack that is in the subplex. For an example of
the JCL to use to establish affinity, see adnrproc.sample.