On Mon, 16 Jan 2006 16:16:40 +0100, Chris Mason <[EMAIL PROTECTED]>
wrote:

>...
>Once you do find the SysRq key, you can enter "logoff" without the
quotation
>marks* and VTAM, performing its SSCP role, will terminate the session
>between the application and the TELNET logical unit (LU) managed by the
>TELNET 3270 server. Ideally you could have the possibility to determine
the
>degree of "prejudice" you apply to the session termination request by
>specifying  whether the application is to be asked politely, TYPE(COND) -
>COND for conditional, rudely, TYPE(UNCOND) - UNCOND for unconditional, or
>the application is to be given no chance to refuse, TYPE(FORCE).
>...

Chris,

Your posting prompted me to dig into the Tn3270E RFCs (1647 & 2355) a bit.
I don't see any updates to SysReq in 2355.  RFC 1647 states that the
behavior of the server to a SysReq depends on whether the server has
access to the SSCP-LU session.  An outboard emulator that looks like a
3270 controler has access to that session; the zCS Tn3270 server does not;
it is simply a VTAM appl with an open ACB.  (If defined with AUTH=CNMI I
guess it would have access to some SSCP functions, but I don't think
that was included in the design.)  For servers without access to the
SSCP-LU function a very limited SysReq support is implemented.  You can
toggle out of the LU-LU session and back (generating the 082B sense you
mentioned) and you can request LOGOFF which will generate UNBIND
Normal).

The other things you mention are definitely not there, but they are not
supposed to be there according to the RFC.  Servers could add extensions
(like the device support you discovered) but moving too far from the RFC
raises incompatability problems.

Pat O'Keefe

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to