Re: TSO/E Reconnect
On Thu, 23 Jan 2014 00:18:09 -0600, Paul Gilmartin paulgboul...@aim.com wrote: Now after some reading and testing, I've found a way to get TSO/E to keep my natively connected session active when I need to shutdown my laptop which involves issuing 2 VTAM commands as follows (which can easily be done in a REXX exec). D NET,TSOUSER,ID=iii V NET,TERM,LU1=l,TYPE=UNCOND Not sure this is exactly what it does, but I have installed the late Gilbert St Flour's excellent IKJEFLN2 exit that works some magic whenever I loose my TCP connection and try to reconnect. Since then, I never had to bother any more with trying to get some commands into the system I just lost my connection to... Have a look at http://gsf-soft.com/Products/IKJEFLN2.html And thanks again, Gilbert S. Jantje. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
On Thu, Jan 23, 2014 at 5:49 AM, Jantje. jan.moeyers...@gfi.be wrote: On Thu, 23 Jan 2014 00:18:09 -0600, Paul Gilmartin paulgboul...@aim.com wrote: Now after some reading and testing, I've found a way to get TSO/E to keep my natively connected session active when I need to shutdown my laptop which involves issuing 2 VTAM commands as follows (which can easily be done in a REXX exec). D NET,TSOUSER,ID=iii V NET,TERM,LU1=l,TYPE=UNCOND Not sure this is exactly what it does, but I have installed the late Gilbert St Flour's excellent IKJEFLN2 exit that works some magic whenever I loose my TCP connection and try to reconnect. Since then, I never had to bother any more with trying to get some commands into the system I just lost my connection to... Have a look at http://gsf-soft.com/Products/IKJEFLN2.html And thanks again, Gilbert S. Gilbert is sorely missed and the above is excellent. But in z/OS 1.12 and above it is no longer needed. In the active IKJTSOxx member of PARMLIB, you can put in the new section like: LOGON + LOGONHERE(ON) ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E2B0/61.5 quote *LOGON* Specifies the system settings for the TSO/E LOGON command: *LOGONHERE(*ON*|OFF)*Specifies whether the RECONNECT option on the TSO/E LOGON panel will be honored even when the system does not detect a disconnected state and the user appears to be logged on. This allows users to reconnect their session from a new terminal without canceling their previous session first, similar to how the LOGONHERE option works under z/VM. *Default:* ON *PASSPHRASE(ON|*OFF*)*Specifies whether the TSO/E logon panel allows users to enter up to 100 characters in the password field. If eight characters or less are entered, the input is treated as a password. If more than eight characters are entered, the input is treated as a passphrase. For more information about activating passphrase support, see z/OShttp://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? TSO/E Customizationhttp://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS?. *Default:* OFF *VERIFYAPPL(ON|*OFF*)*Specifies whether TSO/E determines an APPLID for the system the user is logging onto and passes that APPLID to RACF for verification during TSO/E logon. This option can be used to limit access to different systems that share the same RACF database. For information about setting up APPLIDs in RACF and implementing APPLID verification, see z/OS TSO/Ehttp://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? Customizationhttp://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS?. *Default:* OFF /quote -- Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
In 6648464504487393.wa.paulgboulderaim@listserv.ua.edu, on 01/22/2014 at 08:09 PM, Paul Gilmartin paulgboul...@aim.com said: I can reconnect to the running session with tn3270, absent VTAM. I doubt it. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
For logon reconnect, you also have to make sure that TSOKEY00 contains a nonzero value for RECONLIM= , This is the number of minutes that the system will 'preserve' a disconnected session. For reasons lost to time, we had '0' for this parameter for a long time. Zero says not to preserve such a session at all. If you had a nonzero value already, since the default for LOGONHERE is ON, then reconnect has worked since R12. Note that you have to specify RECON in your logon request. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: John McKown john.archie.mck...@gmail.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 01/23/2014 05:27 AM Subject:Re: TSO/E Reconnect Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Thu, Jan 23, 2014 at 5:49 AM, Jantje. jan.moeyers...@gfi.be wrote: On Thu, 23 Jan 2014 00:18:09 -0600, Paul Gilmartin paulgboul...@aim.com wrote: Now after some reading and testing, I've found a way to get TSO/E to keep my natively connected session active when I need to shutdown my laptop which involves issuing 2 VTAM commands as follows (which can easily be done in a REXX exec). D NET,TSOUSER,ID=iii V NET,TERM,LU1=l,TYPE=UNCOND Not sure this is exactly what it does, but I have installed the late Gilbert St Flour's excellent IKJEFLN2 exit that works some magic whenever I loose my TCP connection and try to reconnect. Since then, I never had to bother any more with trying to get some commands into the system I just lost my connection to... Have a look at http://gsf-soft.com/Products/IKJEFLN2.html And thanks again, Gilbert S. Gilbert is sorely missed and the above is excellent. But in z/OS 1.12 and above it is no longer needed. In the active IKJTSOxx member of PARMLIB, you can put in the new section like: LOGON + LOGONHERE(ON) ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2E2B0/61.5 quote *LOGON* Specifies the system settings for the TSO/E LOGON command: *LOGONHERE(*ON*|OFF)*Specifies whether the RECONNECT option on the TSO/E LOGON panel will be honored even when the system does not detect a disconnected state and the user appears to be logged on. This allows users to reconnect their session from a new terminal without canceling their previous session first, similar to how the LOGONHERE option works under z/VM. *Default:* ON *PASSPHRASE(ON|*OFF*)*Specifies whether the TSO/E logon panel allows users to enter up to 100 characters in the password field. If eight characters or less are entered, the input is treated as a password. If more than eight characters are entered, the input is treated as a passphrase. For more information about activating passphrase support, see z/OS http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? TSO/E Customization http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? . *Default:* OFF *VERIFYAPPL(ON|*OFF*)*Specifies whether TSO/E determines an APPLID for the system the user is logging onto and passes that APPLID to RACF for verification during TSO/E logon. This option can be used to limit access to different systems that share the same RACF database. For information about setting up APPLIDs in RACF and implementing APPLID verification, see z/OS TSO/E http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? Customization http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/DOCNUM/SA22-7783/CCONTENTS? . *Default:* OFF /quote -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
TSO/E Reconnect
A coworker has observed that if he connects to TSO/E via VTAM then disconnects (pulls the plug; not logs out), he can reconnect. If he connects via tn3270 and attempts to reconnect, he gets a new session. I can reproduce this. Furthermore, if I logon initially with VTAM, then pull the plug, I can reconnect to the running session with tn3270, absent VTAM. What makes the difference? We'd like to spare the overhead of running VTAM on a separate (VM, in this case) host. Our configuration involves no solicitor; connection goes immediately to a TSO IKJ56700A ENTER USERID - prompt. Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
Have you checked the TN3270 software to see if it has a timeout or session termination time or function? Have you looked in SYSLOG? I suspect when you terminate the TN3270 session you will be getting a S622 abend. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Wednesday, January 22, 2014 7:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: TSO/E Reconnect A coworker has observed that if he connects to TSO/E via VTAM then disconnects (pulls the plug; not logs out), he can reconnect. If he connects via tn3270 and attempts to reconnect, he gets a new session. I can reproduce this. Furthermore, if I logon initially with VTAM, then pull the plug, I can reconnect to the running session with tn3270, absent VTAM. What makes the difference? We'd like to spare the overhead of running VTAM on a separate (VM, in this case) host. Our configuration involves no solicitor; connection goes immediately to a TSO IKJ56700A ENTER USERID - prompt. Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
On 22 January 2014 21:09, Paul Gilmartin paulgboul...@aim.com wrote: A coworker has observed that if he connects to TSO/E via VTAM then disconnects (pulls the plug; not logs out), he can reconnect. If he connects via tn3270 and attempts to reconnect, he gets a new session. What do you mean by via VTAM? Is your colleague using a real 3270 device? If not, what, and how is it connected? I can reproduce this. Furthermore, if I logon initially with VTAM, then pull the plug, I can reconnect to the running session with tn3270, absent VTAM. What makes the difference? We'd like to spare the overhead of running VTAM on a separate (VM, in this case) host. Ah - I suspect you mean that you are using virtual local 3270s provided by VM. Regardless, you can't connect to TSO without VTAM (or conceivably TCAM!); there is no direct TCP/IP to TSO connection. You need VTAM and TCAS in the loop, unless IBM has slipped a big change past me recently. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TSO/E Reconnect
On Wed, 22 Jan 2014 22:50:58 -0500, Tony Harminc wrote: What makes the difference? We'd like to spare the overhead of running VTAM on a separate (VM, in this case) host. Ah - I suspect you mean that you are using virtual local 3270s provided by VM. Regardless, you can't connect to TSO without VTAM (or conceivably TCAM!); there is no direct TCP/IP to TSO connection. You need VTAM and TCAS in the loop, unless IBM has slipped a big change past me recently. OK, then, TCP/IP to z/OS vs. TCP/IP to VM, then VTAM to z/OS. I'm pretty sure that in the former case TCP/IP goes directly to z/OS. Well, perhaps there's an OSA in there somewhere (I can't bear to think). But the victim did some research and discovered his own solution: Now after some reading and testing, I've found a way to get TSO/E to keep my natively connected session active when I need to shutdown my laptop which involves issuing 2 VTAM commands as follows (which can easily be done in a REXX exec). D NET,TSOUSER,ID=iii V NET,TERM,LU1=l,TYPE=UNCOND where iii is my userid and, l is the ACB name that is output by the first command. [ ... screen shots redacted ... ] After issuing these commands, I was then able to reconnect back to my T790575 session. I understand none of this, least of all why that setup isn't the default, which is why I referred the question to IBM-MAIN. natively connected? Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
