z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Things to consider when logger structure connections exists

z/OS MVS Setting Up a Sysplex
SA23-1399-00

  • Before using a primary LOGR couple data set at HBB705, formatted with ITEM(SMDUPLEX) NUMBER(1), currect Logger connections to the structure from each system had used ALLOWAUTO(NO) on IXLCONN (for initial system connection to the structure).
  • The Logger connection type doesn't change until the system newly reconnects to the structure (not on IXLCONN REBUILD connection requests).
  • After the LOGR couple data set formatted at HBB7705 is brought in as the primary couple data set, any new Logger system connections to the structure will use the ALLOWAUTO(YES) option.
  • If there are still outstanding IXLCONN ALLOWAUTO(NO) connections to the structure from any system in the sysplex, then XES will not enable the system-managed duplexing.
  • If the logstream application or subsystem and Logger on each system is caused to disconnect and then (newly) reconnect to the Logger structure one at a time, all the new structure connections will then be done with IXLCONN ALLOWAUTO(YES).
  • When all the systems connected to a structure use the ALLOWAUTO(YES) option, system-managed duplexing options are now activated.

See Migration steps for migration steps to allow system-managed duplexing rebuild in a sysplex. See LOGR couple data set versioning — new format levels for migration steps to use new format levels of the LOGR couple data set.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014