OSI/AS SCF Reference Manual

Table Of Contents
OSI/AS SCF Commands
OSI/AS SCF Reference Manual424121-001
2-141
Examples of the CHECK Command
The CHECK SU command can be used to investigate active connections or
completed (successful or failed) connections, but the use of this command can
depend on the type of SU used in the connection:
°
A static SU (where the DELETETIME attribute for ADD #ENTRY objects is
set to -1) can be examined at any time during the life of the connection or after
the connection has completed.
°
A dynamic SU (where the DELETETIME attribute for ADD #ENTRY objects
is set to 0) can only be examined while the connection is in existence because
dynamic SUs are deleted when the connection completes.
Examples of the CHECK Command
The examples are designed to show correct ways of specifying command syntax.
ENTRY Object
CHECK ENTRY $MGR1.#APPL.LOC1, CONNECT $MGR1.#APPL.REM1
CHECK ENTRY $MGR1.#APPL.LOC1, PROFILES, SERVERS, DETAIL
CHECK ENTRY $MGR1.#APPL.LOC1, PROFILES, SERVERS
CHECK ENTRY $MGR1.#APPL.LOC1, PROFILES
CHECK ENTRY $MGR1.#APPL.*, PROFILES, DETAIL
SU Object
CHECK SU $TAPS.*, ERRORONLY
CHECK SU $TAPS1.#Z000003
CHECK SU $TAPS.*, LOCALAPPL MYAPP
CHECK SU $TAPS.*, OPENER $MAPUA, DISPLAY ONE
CHECK SU $TAPS.*, USER 16,101
Note. If the connection completed (successful or failed) while the CHECK SU
command is executing, only partial response information may be provided. In this
case, the following error message will be displayed for the TSP or NSP fields in the
display:
Error: subsystem-name subquery retcode -17
If this connection needs further analysis, re-establish the connection using a static SU,
and then reissue the CHECK SU command.