OSI/AS SCF Reference Manual

OSI/AS SCF Commands
OSI/AS SCF Reference Manual—424121-001
2-140
Considerations for the CHECK Command
SU Object
•
The CHECK SU command can only be used for TAPS processes. See the OSI/TS
SCF Reference Manual for information on using the CHECK SU command for TSP
processes.
•
Wildcards are supported for the CHECK SU command.
•
There are a number of options to this command that can help find the particular SU
in question:
°
If the SU name is not known, wildcards can be used: specify the su-name (in
the
object-spec) with a wildcard character. For example:
CHECK SU $TAP1.*
Or to find an SU in error being used by the application $MYAPP and the name
of the TAPS server is known, then the following command will display a list of
SUs:
CHECK SU $TAP1.* , OPENER $MYAPP, ERRORONLY
Or if the name of the local #APPL name is used to create the connection is
known, this command can be used:
CHECK SU $TAP1.* , LOCALAPPL MYAPP
•
If the CHECK 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 releases) and PAM (for G06 and later releases) return very
different, and far fewer, errors than does X25AM. Because the subsystems are
different, it may appear, incorrectly, that TLAM or PAM errors are not captured. If
TLAM or PAM errors are suspected, check the TLAM or PAM EMS event
messages for the TLAM or PAM NSP, or issue a STATS SERVICE command to the
TLAM subsystem (for PAM, issue a STATS LINE or STATS SESSION command,
as STATS SERVICE is not supported in PAM).