OSI/AS SCF Reference Manual

OSI/AS SCF Commands
OSI/AS SCF Reference Manual—424121-001
2-111
CHECK Command
CHECK Command
The CHECK command provides either configuration or connection information about
the specified object and produces a display that summarizes the relevant information.
Use the CHECK ENTRY command before starting a connection for the first time as a
pre-diagnostic tool to determine whether all the necessary components have been
configured and to determine what servers and protocol related attributes will be used in
the connection. The CHECK ENTRY command emulates the process the OSI manager
uses to determine which servers and profiles will be used and reports errors such as
servers that are not started and missing required configuration components. These types
of errors are indicated in the display along with the message “Configuration not
verified.”
Use the CHECK ENTRY command to simulate a connect request between two
applications or to simulate an attach request for one application that waits for an
incoming connection request. In both cases, the command follows the process the OSI
manager goes through when it receives a request to establish a connection with another
application. (This process is described in the considerations for the ADD command; read
that text first before continuing here.)
Use the CHECK SU command after starting or attempting to start a connection to aid in
the diagnosis of connection problems. The connection can be active or failed; however,
if the connection is failed, the SU must be a static SU.
CHECK is a nonsensitive command.
CHECK Command Syntax
The object-spec is
CHECK [ /OUT file-spec/ ] [ object-spec ]
{ [ , modifier-spec ] | [ , select-spec ] }
object-type object-name
ENTRY
entry-name
SU su-name
Note. Issue the SCF command ALLOW ERRORS before issuing the CHECK command.
When the CHECK command executes, it may need to report multiple errors and will abend
prematurely otherwise.
This command is verbose, may be slow, and can affect system performance. It may make
debugging easier if the SCF LOG command is used to direct the command output to a file.