Limiting access to only view the job log.
Moderators: chulett, rschirm, roy
Limiting access to only view the job log.
Is there any way to limiting access in director to only be able to view the job log? We want our developer to be able to view the production job log, but not be able to run the jobs. So granting operator access is not an option. Does anybody know if this is possible? I can't think of any way to do it, but maybe someone has a good idea.
My approach is to create a web interface to dsjob.exe utilizing the -logsum and -logdetail commands. However, I wish it would be possible just to do it in datastage without any external scripts.
My approach is to create a web interface to dsjob.exe utilizing the -logsum and -logdetail commands. However, I wish it would be possible just to do it in datastage without any external scripts.
Mike
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Add this user to a group to which the DataStage Operator role only is assigned, and to no group to which the DataStage Developer role is assigned for this project. Check the "operator can view full log" when configuring DataStage roles for this project.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
You'll need to find some other mechanism to deliver log information to them, something other than Director as you've already noted. I don't believe there is any such mechanism built into the Client tools that would allow log looking but not job running.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
is there a limited number of jobs you don't want that operator to be able to run, or is it all the jobs? if it is the first case you can do some workaround.
Thanks,
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
it will be a naive way but you can make the job aborted when he tries to run with his username. for other users the jobs can run without abort.chulett wrote:Such as?
Thanks,
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
Chad
__________________________________________________________________
"There are three kinds of people in this world; Ones who know how to count and the others who don't know how to count !"
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The Operator role can only run released jobs. I'm prepared to bet you have none of these.
The Super Operator role has been introduced at version 8.0 to allow running of all runnable jobs.
The Super Operator role has been introduced at version 8.0 to allow running of all runnable jobs.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.