SNAX/XF and SNAX/APN Configuration and Management Manual

SCF Commands for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
13-4
ABORT Command
General Considerations

The object-name sess-name is a 16-digit, hexadecimal, fully qualified procedure
correlation identifier (FQPCID). Users can find FQPCIDs by issuing any of the
following commands:

NAMES LU, SUB ALL

NAMES LU, SUB SESSION

STATUS, SUB ALL for the LINE, PU, and LU objects

Because configured LUs on an IBM system are named by their SNA names, it is
sometimes useful to be able to address these LUs by their SNA names rather than
by their subdevice names on the NonStop node. An example is when one of the
500 terminals connected to the IBM host is hung and must be aborted, but only its
SNA name is known.
Therefore, the ABORT LU command for SNAX/APN accepts either a subdevice
name on the NonStop node or an SNA name to identify an LU object. The SNA
name is the value of the SNANAME attribute described in Section 14, Attributes for
SNAX/XF and SNAX/APN; for remote LU objects, it matches the definition of the
corresponding LU in the IBM configuration.
The SCF interface to the SNAX/APN service manager treats all LU names entered
without the leading pound sign (#) as SNA name input (names entered with the
leading # are treated as HP NonStop subdevice names). The # is, however, one of
the valid characters for an SNA name. Thus, when the SNA name is specified in
the ABORT LU command, the value specified cannot have a # as its leading
character.

When using the SNAX/CM with multiple ports on a switched X.25 line, aborting a
PU does not disconnect the line. To stop a line and all its subordinate PUs and
LUs, use an ABORT LINE command.
Operational Notes for Advanced Program-to-Program
Communication (APPC)

When the local PU (#ZNT21) is aborted, all local LUs used for APPC are also
aborted. This causes all active SNALUXS sessions to terminate.
Considerations for the Extended Logon Facility (XLF)

When the local PU (#ZNT21) is aborted, the subordinate TLOGMGR LU is also
aborted. This causes all sessions between the TLOGMGR LU and the ILOGMGR
LU to terminate. All the sessions between any newly added LUs and the terminals
that requested logon are also terminated.

When the remote PU is aborted, all the sessions between the ILOGMGR LU on
that PU and the TLOGMGR LU terminate. All the sessions to the terminals are also
terminated.