OSI/TS SCF Reference Manual

OSI/TS SCF Commands
OSI/TS SCF Reference Manual—424832-001
2-83
Examples of the CHECK Command
SU command is used with a TAPS process from the C21 product version and a TSP
process from this release (C30), then the TAPS displays will contain C21 product
values and will ignore C30 product values. In this case, the ASU information will
be unavailable and "ASU: unavailable" will be displayed.
•
TLAM (for D-series, or PAM subsystems for G06 and above releases) returns very
different, and far fewer, errors than X25AM returns. Because these two subsystems
are different, it may appear, incorrectly, that TLAM (PAM, for G06 and above
releases) errors are not captured. If TLAM (PAM, for G06 and above releases)
errors are suspected, check the TLAM (PAM, for G06 and above releases) EMS
event messages for the TLAM (PAM, for G06 and above releases) NSP or issue a
STATS SERVICE command to the TLAM (PAM, for G06 and above releases)
subsystem.
•
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 #SU 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 #SU objects is set to 0)
can only be examined while the connection is in existence because dynamic SUs are
deleted when the connection completes.
Note that 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 ASU, TAP, 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.
Examples of the CHECK Command
The examples are designed to show correct ways of specifying command syntax.
SU Object
CHECK SU $TS.*, user 15,72
CHECK SU $TS.*, opener \NY.$TAPS
CHECK SU $TS.*, opener $TAP
CHECK SU $TS.*, localtsel "AA30"
CHECK SU $TS.*, localnsap "AA3030"
CHECK SU $TSP.*, ERRORONLY
CHECK SU $TSP1.#z000003
CHECK SU $TSP2.*, OPENER $mine, DISPLAY ONE