SNAX/CNM Manual

INTRODUCTION
Outstanding Verbs
USAGE NOTES
This subsection first discusses the idea of outstanding verbs.
Next follow notes about when statistical counters get reset and
about what happens when a program closes $SSCP without first
issuing a VERB^DISCONNECT. The subsection ends with suggestions
on how to handle network management functions for a remote node
of an EXPAND network.
Outstanding Verbs
A verb is considered to be outstanding when your WRITEREAD sends
it to $SSCP and $SSCP cannot in itself provide the expected
reply. In such a case, $SSCP passes the SNA request embedded
in your verb to another process or device. Upon receipt of the
SNA response from the process or device, $SSCP builds a CNM reply
that delivers this response to your program on the READ portion
of the WRITEREAD that issued the verb. The verb is outstanding
until $SSCP delivers this reply to your program. At most, three
verbs can be outstanding.
Consider, for example, the case of a VERB^SEND^REQ with an
embedded SNA REQMS request. Upon receipt of this verb, $SSCP
forwards the REQMS request to the designated PU. When the
PU delivers the RSP(REQMS) to $SSCP, $SSCP sends it to your
application on the READ portion of the WRITEREAD that originated
the REQMS request. This sequence also applies when the verb
contains an embedded SNA NMVT requesting network information and
the PU responds with a RSP(-MVT).
Of the ten possible verbs, the following four are regarded as
outstanding:
VERB^SEND^REQ (with an embedded REQMS or NMVT requesting
network information)
VERB^SEND^MS (with an embedded RECFMS or NMVT containing
network information)
VERB^ACCEPT
VERB^STATISTICS (LINE, PU, LU)
The information returned on the READ part of a given WRITEREAD
command is not necessarily related to the verb passed in the
WRITE part. Consider the following examples:
• For a VERB^ACCEPT directed to the CNM component, the reply
buffer might contain a REQMS (from the host) or a RECFMS type
0 (from a device). The same holds true for a RSP(RECFMS).
1-11