The primary benefit derived from MSO Load Balancing is the ability to evenly distribute MSO Logon requests across multiple MSO regions. This makes monitoring of MSO regions less costly to administrative personnel. It also ensures that MSO users will get more even-handed performance characteristics when they Logon to MSO.
There is more flexibility for the MSO Administrator in controlling how many resources to give to MSO Users. The connection to all but the primary or initially contacted MSO region need not be known by the connecting environments, including the primary MSO region. Additional MSO regions may be started via the console or by submitting a job. These new regions must have their own unique connection data sets allocated (MSGET/MSPUT) and VTAM applids if they are to be accessible from VTAM. However, they become automatically available to the APPLGROUP when they have completely initialized.
The connecting environments, TSO, CICS, and VTAM only have to be set up to connect to the primary or initially contacted MSO region.
The TSO CLIST/EXEC only has to allocate the MSGET/MSPUT communication data sets of one of the MSO regions in the MSO Load Balancing group.
The VTAM Logon command/session manager screen only has to specify the MSO applid (lu2_name in the MSO Configuration File) of one of the MSO regions in the Load Balancing group.
The CICS regions that connect MSO Users to the MSO Load Balancing group only have to have one pair of communication data sets allocated. In addition, only one MSO transaction id has to be defined.
| Information Builders |