Mr "AS400",

If you are using RFC 2355 TELNET 3270 you will have access to the SysReq
function which allows you to invoke an SSCP-mediated LOGOFF - unfortunately
ONLY that. This is another way you may be able to exit from your current
application at whatever depth you are within the panel hierarchy of your
current application.

Now the question is "Which key or combination thereof gives you access to
the equivalent of the 3270 keyboard SysRq* key?" This all depends on the
3270 emulator key mapping of the TELNET 3270 client product you are using.
You'll have to hunt around in the icons on your emulator window to find
maybe a popup with all the 3270 keyboard keys available for selection  (or
maybe a "right click" on the window). I expect you'll even find the PF and
PA keys that way.

* Clearly the SysRq key invokes the SysReq function - actually it "toggles"
it.

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).

* Here's the text from 2.2.1.3.1 "TN3270 Enhanced (TN3270E)" in the CS IP
Configuration Guide:

"SysReq function - The end user can request that a current session be
dropped by entering LOGOFF (in upper, lower, or mixed case) after pressing
the SysReq key. If LUSESSIONPEND is not mapped to the client, the connection
will be dropped. Otherwise, a USSMSG10 screen is sent to the client. If,
instead of entering LOGOFF, the SysReq key is pressed a second time and if
the application supports LUSTAT 082B (presentation screen is lost), the
previous screen is resent to the client emulator. "

This actually isn't the complete SysReq function at all. It's a pale
reflection of the full function. Among other possibilities, it clearly
misses the possibility to specify how "strong" the session termination
should be. Ideally this implementation of the SysReq function should involve
reference to the USS table just as for the logging on process.

Note: Strictly the SysReq function described here is the use of the function
while an LU-LU session exists. The use of the USS table, commands and
messages, while no LU-LU session exists is also, in fact, the SysReq
function.

The other aspects of the SysReq function that are missing are the
possibility not to enter some type of "logoff" command but simply hit enter
in order to invoke USS message 5 - with the wealth of information this could
offer to the help desk when the end user is stuck deep in the panel
hierarchy of the application and wants the help desk to investigate. Also it
may be helpful to invoke the "ibmtest" function in order to see whether or
not the path between VTAM and the emulator can sustain traffic and at what
rate - a sort of SNA ping. In fact I'm not sure that this is even possible
when there is no LU-LU session. If the USS "ibmtest" command is not
supported and the USS "logoff" command is not supported, this leaves only
support for the USS "logon" command. That makes it 1 out of 3*. Thus the
following claim "Telnet USS function supports almost all VTAM session-level
USS message and command definitions." made in section 2.2.1.10.2, "Using the
Telnet USS and INTERPRET support", of the CS IP Configuration Guide must be
deemed false. There is still much work to be done in the area of USS support
if only CS IP development appreciated it.

* I'm excluding the USS "undial" command which is provided only in VM VTAM.

I guess I must seem like a dog with a bone here. There is even something
deficient with the way that CS IP development have implemented their
masquerade of the USS "logoff" function. The sequence they describe is that
required by "non-SNA" 3270 device. For an SNA 3270 device, the SysRq key
must be used first and then the USS command, "logoff" or "ibmtest" or
nothing at all in order to present USS message 5 and be able to tell the
help desk which TELNET LU is causing trouble or whatever else might be
useful from the information the USS message 5 could carry.

Chris Mason

----- Original Message ----- 
From: "John S. Giltner, Jr." <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Saturday, 14 January, 2006 9:46 PM
Subject: Re: TN3270 Question


> as400 wrote:
> > I have a TN3270 running under Windows 2000 with a standard type
> > keyboard without the "P" F function keys...There ONLY the "F" Function
> > keys..
> >
> > Now, when I want to just only back out of a current page on the TN3270,
> > what do I have to enter? Because in order to view a different page, I
> > have to close the TN3270 application entirely and go back and reconnect
> > again in order for me to select a different entry...
> >
> > How can I accomplish this please?
> >
> > Thanks
> >
>
> Every 3270 emulator (TN or otherwise) I have used have mapped PF1-12 to
> F1-12, and Shift+F1-12 to PF13-24.
>
> Now how to back out of the current page, well it depends, you have to
> know what key the application expects and then hit that key.  We have
> different applications that use different keys, some use PF3, some PF4,
> some PF12 and some clear.  Normal is PF3 for END (keep changes and back
> out) or PF12 for cancel (undo changes and back out).

----------------------------------------------------------------------
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