OSI/MHS Configuration and Management Manual

Managing Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
7-20
Maintaining the Interfaces to OSI/AS
The INFO CUG command displays the following screen.
The INFO CUG command shows all the CUG objects defined for a subsystem.
The NAMES CUG command shows all the CUG and CUGMEMBER objects defined
for a subsystem, as displayed on the following screen.
Maintaining the Interfaces to OSI/AS
Successful connections between OSI/MHS and external entities depend on the
accuracy of the OSI addresses and the consistency of the address components
defined to OSI/MHS and OSI/AS. To verify the addresses and the connections being
made through them, you can follow three steps:
1. Find the name of the OSI manager serving the OSI/MHS subsystem.
2. Look at the definitions of MR and RS groups and MTA objects to see which
addresses have been defined.
3. Examine the OSI addresses as defined to the OSI manager and, if desired, the
connections through those addresses.
It is a good idea to identify connections and verify the accuracy of OSI addresses
whenever you have made addressing changes.
Finding the OSI Manager Process
To find the name of the OSI manager process, look at the SUBSYS object:
INFO SUBSYS $MHS1.#MHS1,DETAIL
-> info cug $mhs1.*
MHS info CUG
CUG Number-of-members
DEVICEINDUSERSONLY
3
-> names cug $mhs1.*
MHS Names CUG \NEWYORK.*
CUG
SALES
CUGMEMBER
SALES MANUFACTURING SHIPPING