|
View previous topic :: View next topic
|
| Author |
Message |
jsathishbabu84
New User
Joined: 07 Jun 2007
Posts: 22
Location: India
|
|
|
|
Hi,
Is there anyway to trigger a rexx routine or JCL during mainframe logoff
Thanks,
SJ |
|
| Back to top |
|
 |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| You could have automation fire a rule for the $HASP395 message when that TSO session ends. |
|
| Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008
Posts: 400
Location: Mumbai
|
|
|
|
| If you are running a logon clist or rexx that automatically logs you off after you exit ISPF then that clist/rexx can be changed to do anything you want between the time you exit ISPF and actually logoff. If not, write your own logon clist or rexx and run it from the logon screen. |
|
| Back to top |
|
|
jsathishbabu84
New User
Joined: 07 Jun 2007
Posts: 22
Location: India
|
|
|
|
Hi,
I have a logon Clist but can that be used for logoff too. If so, is there any command to recognize the logoff...
Thanks,
SJ |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| There may be a TSO exit that can be invoked at logoff time -- I haven't looked into it so I don't know for sure. If so, and if you can convince your site support group to enable that exit, you could use it to trigger your logoff routine. However, it would be effective for everybody using TSO at your site. So you'd probably have to have an extremely good reason to have this implemented. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| However, it would be effective for everybody using TSO at your site. |
It has been many years, but I think you can put some exits in a steplib dataset. That is, it might only affect the people using the same logon proc... easier to request from the system support.
You might also try putting your exit in a TSOLIB allocated dataset. If you try, let us know the result. |
|
| Back to top |
|
|
MBabu
Active User
Joined: 03 Aug 2008
Posts: 400
Location: Mumbai
|
|
|
|
The point about the logon clist is that if you start ISPF from the logon clist, then when you exit ISPF, the logon clist will still be running, so just put the commands in there. To be sure it will still be active after abends, start the clist with a CONTROL MAIN command. For example, a login clist like this would do it. I haven't used a login clist like this in years but the basic idea works
| Code: |
PROC 0
CONTROL MAIN NOFLUSH
ALLOC .... /* whatever you need to do before starting ISPF
ISPF
EX 'SOME.CLIST(LOGOFF1)' /* do whatever you want before logoff
LOGOFF /*force user off |
|
|
| Back to top |
|
|
|
|
