🚀 go-pugleaf

In article <1992Oct29.211725.13086@webo.dg.com> chuck@maui.webo.dg.com (Chuck Noyes) writes:
>Greetings:
>
>I have 2 questions that I need answered by someone who's SNA proficient.
>
>1.  What should happen in the case where an ACTLU request is received by a 
>    secondary device for an LU that is already active and has an LU_T2
>    session established?  Should a sense code be returned to the primary?  If
>    so, which one? 

If there is already an active SSCP-LU session that matches the LFSID of
the ACTLU request, then the secondary LU is obliged to send a
-RSP(0815) to the primary LU.  -RSP(0815) is the Function Already Active
sense code.

(NB: The code to verify that the LU Type in the BIND matches the LU type
in the local configuration since the SSCP-LU session never gets created.)

Ref: Format and Protocol Reference Manual: Architecture Logic for LU Type 6.2,
procedure PROCESS_ACTLU_RQ on p. 4-79.

>
>2.  In an LU6.2 session, if the *primary* application issues an FMH-5 ALLOCATE
>    with the CONFIRM option set, must it send a CONFIRM *an LUSTAT* to the
>    *secondary* to mark the end of a transaction?

No, the confirm indicator is piggybacked on the RU data by setting the
RH appropriately.  CONFIRM by the Transaction Program results in the
setting of the DR2 bit in the RH.  

If you want to reference the LU 6.2 architecture, setting the CONFIRM
indicator in the SEND_PARM of the SEND_DATA_RECORD for messages from PS
to HS results in setting the response bits to RQD3.  This is described
very vaguely in the LU 6.2 FAPL in Section 6.1 (DFC) and is executed in
SEND_BIU described on p.  6.1-37.

>
>    Thanks in advance.
>
>
>+----------------------------------------------+
>| Chuck Noyes                              DGC |
>| Chuck@maui.webo.dg.com                       |
>+----------------------------------------------+ 

-----------
Wayne Clark
cisco Systems, Inc.
wclark@cisco.com
415/688-4627