Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
Sessions
Life Cycle of a Session
Contention
Contention arises in half–duplex sessions when either partner has the right to send
data. If the session is operating in the half–duplex flip/flop and brackets are used,
contention arises when one half–session attempts to begin a bracket.
The BIND record assigns one half–session as the contention winner, and the other as
the contention loser. This enables SNAX/HLS to resolve the contention issue. It also
allows SNAX/HLS to determine whether the BID request is needed (it is used when
the contention loser, also known as the bidder, wants to send a chain consisting of
more than one RU).
Your application program, however, might encounter a situation very similar to
contention. If your program begins to send a transaction, a beginning of transaction
might already have arrived from the other partner by the time the request reaches
SNAX/HLS. In this case, SNAX/HLS rejects your SEND–DATA request with a return
code of RC–SEND–CHECK and an SNA sense–code value of %H2003 (Bracket State
Error). The application program can assume that the beginning of the inbound
transaction is ready to be received.
The application program should respond to the RC–SEND–CHECK and temporarily
suspend the attempt to send the data. The inbound data should be retrieved and
processed, and any replies should be sent. When the transaction is finally closed, the
application program can attempt to send the old data once more.
If the application program is controlling responses, another option is available. When
the RC–SEND–CHECK is detected, the application program should temporarily
suspend the efforts to send the data, and should start receiving data until the
MESSAGE–COMPLETE–IND is true. At this point, the application program then uses
the HLS–RESPOND verb to issue a negative response to the chain just received, citing
sense code %H0813 or %H0814. This transmission can be followed immediately by
resending the data that failed. When the transaction initiated by the application
program is complete, you should send a HLS–FLOW–CONTROL(RT) if the
HLS–RESPOND verb issued an %H0814.
Character Mapping
Originally, SNAX/HLS provided character set conversion between Tandem standard
ASCII and EBCDIC. The application programmer also had the choice of having this
conversion performed in SNAX/HLS or by the Tandem SNA access method
(SNAX/XF or SNAX/CDF) below the SNALU interface. In the current version of
SNAX/HLS, this mapping is the default. That is, if you select the TRANSLATE
attribute in the PROFILE used on the session, and do no further character mapping
configuration, data translation is performed on the session and the code sets are
presumed to be Tandem Standard ASCII and EBCDIC.
The current version of SNAX/HLS also supports character set conversion between the
ISO 8859/1 and IBM 3174 CECP character sets. The Tandem product
NLS–MAPS T9279 provides maps to translate between these character sets and
SNAX/HLS has an interface that uses these maps. (For more information on
NLS–MAPS, see the current softdoc for NLS–MAPS.)
104707 Tandem Computers Incorporated
3–9
... Este manual também é adequado para os modelos :
Computadores - HP Integrity NonStop J-Series (534.14 kb)
Computadores - HP NonStop G-Series (534.14 kb)
Computadores - HP NonStop L-Series (534.14 kb)