|
View previous topic :: View next topic
|
| Author |
Message |
wangjiyi
New User
Joined: 14 Aug 2006
Posts: 12
Location: Shanghai, China
|
|
|
|
When I logon the TSO and after no operation for a while, The system will automatically force me logoff.
what parameter should I adjust to prolong this time or even forever. |
|
| Back to top |
|
 |
UmeySan
Active Member
Joined: 22 Aug 2006
Posts: 771
Location: Germany
|
|
|
|
Hi !
This parameter is set by your systemprogrammers.
Regards, UmeySan |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
| Some users go into SDSF and use the & command (auto update). If you type &30 on the command line in SDSF, the screen with autoupdate every 30 seconds. This gives the system the appearance you are pressing enter every 30 seconds. Pressing the ATTN (attention) key twice will interupt you out of the auto update command. |
|
| Back to top |
|
|
wangjiyi
New User
Joined: 14 Aug 2006
Posts: 12
Location: Shanghai, China
|
|
|
|
| Thanks, yeah,when I submit a job which persists a long time,I use &2 to auto-update the recently state of the job. Of course its a solution to solve my problem. But I want to know exactly which parameter can be modified to implement such effect, maybe in my logon procedure, in sys1.parmlib and so on... |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
You cannot adjust your own TSO timeout parameter. It is a system default.
You are correct about where the parameter resides. It is in SYS1.PARMLIB(SMFPRM00)
| Code: |
ACTIVE /* ACTIVE SMF RECORDING */
DSNAME(SYS1.MAN1,
SYS1.MAN2,
SYS1.MAN3)
NOPROMPT /* DO NOT PROMPT OPERATOR */
REC(PERM) /* TYPE 17 PERM RECORDS ONLY */
MAXDORM(3000) /* WRITE IDLE BUFFER AFTER 30 MIN */
STATUS(SMF,SYNC) /* WRITE TYPE-23 TO SMF SYNC */
JWT(0100) /* 522 AFTER 60 MINUTES */
DDCONS(NO) /* TURN OFF CONSOL TYPE30 */
INTVAL(60) /* CFJ SMF GLOBAL DEFAULT 60 MIN */
SYNCVAL(59) /* CFJ SET SYNC VALUE 01 MIN */
SID(SYSX)
LISTDSN /* LIST DATA SET STATUS AT IPL */
|
THe JWT(0100) parameter indicates to abend TSO with a S522 after a 1 hour wait. |
|
| Back to top |
|
|
wangjiyi
New User
Joined: 14 Aug 2006
Posts: 12
Location: Shanghai, China
|
|
|
|
Thank you very much. I have found that.
JWT (hhmm) Specifies the maximum amount of time that a job or TSO/E user address space is allowed to wait continuously, where hh is the amount of real time in hours and mm is in minutes.
If the specified time limit expires, the system passes control to the SMF time limit exit, IEFUTL (if active). IEFUTL either causes the job or TSO/E user address space to end abnormally, or it extends the wait time.
accordingly I should found a new member SMFPRMXX which the JWT parameter is modified. Then use SET SMF command to activate it. |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
I believe your change will work, however, the new Job Wait setting will apply to every TSO user on your mainframe.
I'm not sure what your job title or responsibilities are, but you should make sure your change does not go against the policies of your company.
You will probably need to ensure you have authority to issue the SET SMF command. |
|
| Back to top |
|
|
wangjiyi
New User
Joined: 14 Aug 2006
Posts: 12
Location: Shanghai, China
|
|
|
|
Your constructive suggestion is appreciated. I will take charge of the OS,XRC maintenance routine of ABC, one of the largest bank of China.
I perform such changes on the test LPAR provided by our bank for me.
So it will not exert any influence on our business. |
|
| Back to top |
|
|
DarrylHoward
New User
Joined: 23 Feb 2007
Posts: 1
Location: US
|
|
|
|
While adjusting the JWT value will work, it may not be the best solution. The JWT value affects all jobs in the system, not just TSO sessions. Increasing the JWT setting would prolong jobs that you may really want to terminate due to inactivity.
A better solution would be to add a "TIME=1440" parameter to the EXEC statement of the TSO logon procedure (such as IKJACCNT) for any users that have a legitimate need for a TSO session that does not timeout. You may have to create a new logon procedure with the TIME parameter, then use the TSO ACCOUNT command, or a security facility such as RACF, to assign it to the desired users. Then, when the user logs on, a started task, identified by their TSO userid, will be initiated. This task will have the TIME=1440 parameter and will never timeout. |
|
| Back to top |
|
|
banu_parveen
New User
Joined: 30 Jan 2007
Posts: 6
Location: india
|
|
|
|
Preventing Mainframe session from getting logged off automatically can be done through OMVS Utility.
Give option ?=6? in the command line to reach the ISPF Command Shell
Give the command ?omvs?
Your login session goes to a ?stand-by? mode
When you want to activate your session again, type ?exit? (all small letters) in the command line and press Enter.
Press Enter again to go back to the Command shell
You can resume your work right from where you left it, without losing any valuable effort, or having to re-do anything!
OMVS command invokes the OMVS shell, and allows you to switch among the shell, a TSO/E session, and subcommand mode. You can find out more about this by pressing the HELP (F1) key. |
|
| Back to top |
|
|
|
|
