|
View previous topic :: View next topic
|
| Author |
Message |
quest2008
New User
Joined: 12 Jun 2008
Posts: 22
Location: bangalore
|
|
|
|
Hi All,
My Mainframe Timeout period is 12 hours. If i lost the connection due to internet disturbance or some other reason the tso id would be still running until 12 hours and then it is getting cancelled. I read some threads in the forum to override the logon procedure SYSUSER. I dont have rights to update sysproc. Please let me know what are the ways to ovverride the tso logon proc and which file i need to ovverride to reduce the timeout period.
Thanks. |
|
| Back to top |
|
 |
Bill Dennis
Active Member
Joined: 17 Aug 2007
Posts: 562
Location: Iowa, USA
|
|
|
|
The preferred method when you have a connection error is to select the RECONNECT option on the LOGON panel. Unless your site customizes the default, put an "S" in front of RECONNECT to rejoin the session rather than wait for it to timeout.
You can just leave the "S" there all the time as it doesn't effect a normal LOGON. |
|
| Back to top |
|
|
quest2008
New User
Joined: 12 Jun 2008
Posts: 22
Location: bangalore
|
|
|
|
| If I tried that option it throws the message USER ID is already in use . Logon rejected. I think i need to understand how to create my own logon proc where i can set the timeout period. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| If I tried that option it throws the message USER ID is already in use . Logon rejected. I think i need to understand how to create my own logon proc where i can set the timeout period. |
Why are you not working with your site support group to resolve the issue? If your site uses RACF, for example, you may find that the TSO signon procedures are protected by RACF profiles and you will not be able to create your own signon procedure. In all cases, setting up a TSO signon procedure is not a task for an applications person -- only a systems person should be doing this since the signon procedure used has implications about the applications you are allowed access to, sometimes even the tools you are allowed to use.
Most places I've worked, applications programmers who attempted to set up their own TSO signon procedure would be severely reprimanded at best, or terminated, for such an abuse. |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| On our system we enter the user id followed by a space and the word reconnect. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| If I tried that option it throws the message USER ID is already in use . |
This sometimes happens when the "new" connectoin is via a different terminal-id. You should still be able to re-connect.
As was mentioned before, you should talk with your system support people to learn which is the proper way to reconnect from an ungraceful connection termination.
Also, none of my client's systems would allow such a long timeout. . . fwiw. |
|
| Back to top |
|
|
|
|
