OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-44
Checking the Contents of the MIB
Not all errors displayed by the CHECK ENTRY command point to problems in your
configuration. For example, Layer 3 and Layer 4 servers are not required in local APPL
ENTRYs for loopback configurations. However, if you have specified the PROFILES
and SERVERS attributes using a wild card, the CHECK ENTRY command displays
errors for those missing server specifications. See Loopback Connections
on page 4-46.
CHECK ENTRY With PROFILES Attribute
The CHECK ENTRY command with the PROFILES attribute verifies that all of the
ENTRY and PROFILE objects for the address components specified in the APPL
ENTRY are in the MIB. For example, if one of the associated ENTRY objects specifies
a profile name, the CHECK command determines which PROFILE object has
precedence and verifies that the selected PROFILE is in the MIB. If it is not in the MIB,
the command returns an error.
CHECK ENTRY With SERVERS Attribute
If you specify the SERVERS attribute (in addition to the PROFILES attribute), the
CHECK ENTRY command also verifies that the server named in an ENTRY object is in
the MIB and reports on its state (for example, STARTED or STOPPED). For example, if
one of the ENTRY objects (associated with the APPL ENTRY object given in the
command) specifies a server name, the CHECK command determines which PROCESS
object has precedence and verifies that the selected PROCESS object is in the MIB. If it
is not in the MIB, the command returns an error.
CHECK ENTRY With DETAIL Attribute
If you specify the DETAIL option, all requested information is displayed as it is
retrieved, along with additional server information.
The CHECK ENTRY command with the DETAIL option also displays SERVICE
information.
Note. Because the CHECK command may need to report errors in your configuration, you
must issue the SCF command ALLOW ERRORS before using the CHECK ENTRY
command. Failure to do so causes SCF to terminate the CHECK command when it
encounters a configuration error.