|
View previous topic :: View next topic
|
| Author |
Message |
ssk2686
New User
Joined: 10 Sep 2009
Posts: 1
Location: mumbai
|
|
|
|
How to logoff mainframe when it is kept idle for few minutes?
I know it has got session timeout after 3 mins. But i want to reduce this to one and half minute or 2 mins to reduce the cost.
Is there any scheduler job available for this? |
|
| Back to top |
|
 |
rockish
Active User
Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth
|
|
|
|
| Even I have this doubt for long time. I would rather put it the other way. What is the parameter that controls a TSO session timeout ? I have seen different installations taking different time before timing out !! |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| How do you imagine that this will reduce costs |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
whow... the first time I see somebody wanting to reduce the wait timeout
but seriously, why would you want to do that,
reducing the wait/idle timeout from 3 to 2 minutes
is not going lower the costs in a significant way.
(the cost of the infrastructure to do it might be higher )
even with a three minutes timeout
you have barely the time to do anything non terminal related betweek keystrokes ,
read and take notes, look at a manual, for example |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| I can't imagine a scheduler job could do this. You need to contact your site support group and work with them on exactly what you need and how to best provide it -- assuming you're talking about TSO session timeout, the parameter can be set to a different value but there may be system implications to the change that would preclude it from happening. Since this is site specific, you really have to talk to your site support group about this type of request. |
|
| Back to top |
|
|
rockish
Active User
Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth
|
|
|
|
I am not sure about the reason behind ssk2686's question.
But why I wanted to know was for a problem I faced while testing some Rexx codes. When I try to run long running Rexx codes from my TSO session (not in a batch, but online), the job ends abruptly if the session times out. Hence I was wondering if there is a parameter to increase (not decrease as the case with ssk) the session timeout in test/development environments to a little higher value, so that it can aid me in testing those codes easily.
PS - I indeed completed my testing back then by using a batch job to run Rexx. But then, just because somebody else raised a doubt on the same, the old story struck my mind. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Yes, there is a system parameter that controls how long a TSO session will go without activity before being logged off. As a site parameter that affects the entire LPAR, it is not something to be changed without studying the impact. For example, programmers often want it set to not log them off ever. However, when they start an edit session on a file used in batch production (such as a parmlib member) and then go home, they may prevent the batch processing cycle from running (at least until the operator cancels their TSO session). So the time value tends to be a compromise between the various groups that have an interest. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| When I try to run long running Rexx codes from my TSO session (not in a batch, but online), the job ends abruptly if the session times out. |
the parameter that controls the session inactivity is the JWT parameter
a rexx running uses cpu, so Your session will not be in a wait/idle state
and the session should not be canceled...
the abend for jwt exceeded is 522, did You check it |
|
| Back to top |
|
|
rockish
Active User
Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth
|
|
|
|
| Quote: |
a rexx running uses cpu, so Your session will not be in a wait/idle state
and the session should not be canceled...
the abend for jwt exceeded is 522, did You check it |
The case I was saying is, when I run a Rexx using TSO Command EXEC. As we all know, the CPU will be in use at that time and I can even picture a X SYSTEM at the bottom of my screen notifying that my session is in use. But in cases where I dont have any SAY statements and if the program runs beyond 5 minutes (that was the timeout value in that environment) the session automatically disconnects. This happened long back that I donot actually remember if the abend was 522 
Of course, thanks Enrico. JWT is what i wanted to know..
And it is really long time i stopped using rexx for small things. and as the rexx i code does task for long time, i use only batch these days !!!! |
|
| Back to top |
|
|
rockish
Active User
Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth
|
|
|
|
Robert, of course I am very much aware of the serious impact this parameter can cause !!!! And I definitely would not dare to change it that easily in a production environment. I was asking for development environment in particular.. And of course, my site doesnot give access for developers to change TSO parameters  So there is noway I can do this without a big discussion with my sites system programmers. |
|
| Back to top |
|
|
rockish
Active User
Joined: 05 Jun 2009
Posts: 185
Location: Planet Earth
|
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
but beware... the last advice given in the quoted post, even if technically correct ( it works )
is in blatant violations of any work ethics
even if the worse I' ve seen was somebody quoting an attachmate macro issuing an enter every 10 second  |
|
| Back to top |
|
|
|
|
