Steve This is a copy of the post using Google Groups attached (in e-mail terms) to one of your earlier posts in this thread. For some reason, I didn't see the referenced post as an e-mail.
> BTDTNVE (Been There, Done That - Not Very Exciting) There's something approaching a logical inconsistency here. Since you were not aware of the SSCP LOGOFF capability, I assumed this must be your first exposure to the use of the SYSREQ function ***while an LU-LU session is in place*** - as opposed to after activation or after logging off your previous application when only the SSCP-LU session is in place. If this is the case then you actually haven't "been there", let alone "done that" - and the T-shirt is definitely still on the tailor's dummy in the store. Perhaps you do know all about the "@" variables in USS messages - but you have seen them in use - and been unimpressed - only in, I would expect, the USS 10 message which appears after activation or after logging off your previous application. I am talking about USS message 5 which you can persuade to appear on your display screen in the following scenario: - "****, the **** thing is ****** well stuck again!" - Call to help desk - one hopes using a ruggedised phone. - Repeat of 1 down the phone. - In a calm voice: "Please identify your connection to the application". - "What do you mean?" (Any further possible expletives have been deleted.) - Continuing the calm voice: "Please press your SysRq key (or instructions relating to how to find it on the corporate standard emulator), press Enter and spell out the name following 'Workstation Identification:" (Editor's note: in fact an LU name and if there is a possibility that the VTAM which activated the LU may not be known with certainty by the help desk, the name of the "Owning System:" could be requested as well.) - "Looks like <m-y-l-u-n-a-m-e>." - "Thank you" - short pause - "I see" - short pause - "That should have solved your problem. You can now ..." -- "... press SysRq and continue with what you were doing. ..."[1] -- "... logon again and retry what you were doing. I'm afraid I had to end your connection to the application. ..." - "... I'll be raising an fault report for you. ..." -- In some jurisdictions: "Thank you for using the help desk, Have a nice day." -- In others: "Thank you and goodbye." Note that the alternative to "Please press the SysRq key ..." used to be something on the lines of "Please try to find a 'post-it' or something like that stuck on the surround to your monitor somewhere which identifies your workstation." and the conversation becomes even more fraught - and possibly peppered with even more expletives. Now being told about that USS message 5 used quite to impress my students of 20 years or so ago who, many of them, were the folk responsible for setting up help desk systems. [1] Clever applications can pick up the sense code which they will now receive and refresh the presentation space with the last data known to them. I think the code is 082B. It may be that others, not so clever, put out a line message suggesting that the application "refresh" function is used. Chris Mason Steve Comstock wrote: > Chris Mason wrote: > > > > ... > > > > Since this is your first exposure to the SYSREQ function used when in > > session, perhaps you should simply try pressing Enter after pressing SysRq. > > This will present your USS message 5. If this is simply "Function not > > supported" it indicates you have not invested in cramming masses of useful > > substituted information into the message such as - let me pick one at random > > <g> - @@LUNAME. See sections 5.12.7.1, "BUFFER", and 5.12.7.20, "TEXT" in > > z/OS Communications Server SNA Resource Definition Reference. > > > > BTDTNVE (Been There, Done That - Not Very Exciting) > > ... > > -- > -Steve Comstock > The Trainer's Friend, Inc. ---------------------------------------------------------------------- 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
