Taking advantage of console name message routing

To take advantage of console name message routing, the installation must configure each sysplex sharing the library in one of the following ways:

In a JES3 environment, the console name associated with the library must be attached to the current JES3 global processor, and must be switchable to any local processor capable of becoming the global. The console should be defined in the JES3 initialization deck as an MCS console by specifying TYPE=MCS and using the UNIT keyword on the CONSOLE statement (not the DEVICE statement) to establish the logical association to the actual device number on the individual processors.
In a cross system communication facility (XCF), define a physical console to receive tape library-specific messages. Make sure each system in the sysplex has that console defined with the same name. A separate console can be used per library.
In a JES2 environment without XCF, each system must have a separate physical console, and all consoles must have the same name.

If more than one sysplex shares the library, each sysplex must have a separate physical console. If there is a single TCDB, then all consoles must have the same name. If there is a separate TCDB for each sysplex, then each sysplex may have a unique console name.