View previous topic :: View next topic
|
Author |
Message |
subhra
New User
Joined: 11 Mar 2007 Posts: 3 Location: INDIA
|
|
|
|
How can I execute a REXX/CLIST from my session with the authority of another ID.
Given that the userid and the password is known. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Why do you need the authority of another user?
If the task is something you are authorized to do, you need to be granted the permissions or put into a group that does.
This is something to talk with your security admins or management about. |
|
Back to top |
|
|
subhra
New User
Joined: 11 Mar 2007 Posts: 3 Location: INDIA
|
|
|
|
Very often we lose connectivity to the mainframe which locks out our TPX sessions.
To login again we either have to wait for the session to timeout or we have to request the minframe monotoring team to cancel our session so that we can login again. Both ways it takes quite a long time before we can resume work.
I was looking for a possible REXX/CLIST which we can use from someone else's session to kill our sesssion to enable us to login again.
I have rexx which to kill my own session but it cannot be used to kill someone else's session for lack of authority. Hence I was looking for a way to execute the same rexx with the authority of another user.
I hope I have been able to convey the requirement.
Please do let me know if there is a simpler solution to this than what I am thinking. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
Don't know how your shop has setup TPX, but you should be able to cancel your own session(s) using TPX.
Otherwise, the only option I can think of is to run your code in batch, using the required userid/password on the JOB statement. |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
subhra wrote: |
Very often we lose connectivity to the mainframe which locks out our TPX sessions. |
This seems like a major issue that should be addressed with the Operations Staff/System Administrators. It shouldn't be tolerated for any reason. |
|
Back to top |
|
|
subhra
New User
Joined: 11 Mar 2007 Posts: 3 Location: INDIA
|
|
|
|
Superk,
Thanks for your advice.
I was able to run the rexx in batch mode and kill the session.
- Subhra |
|
Back to top |
|
|
|