Operator Role problem
Moderators: chulett, rschirm, roy
Operator Role problem
Hi to all,
I have created a user group in windows and assign DataStage Operator Role to this group from DataStage Administrator.
I was expecting that when i login to Director by any user of this group, i could run jobs ............... but the problem is I could not EVEN VIEW my jobs and commands/menu to run jobs are all DISABLED.
Tell me what i am missing.
Thanks
I have created a user group in windows and assign DataStage Operator Role to this group from DataStage Administrator.
I was expecting that when i login to Director by any user of this group, i could run jobs ............... but the problem is I could not EVEN VIEW my jobs and commands/menu to run jobs are all DISABLED.
Tell me what i am missing.
Thanks
-
- Participant
- Posts: 437
- Joined: Fri Oct 15, 2004 6:13 am
- Location: Pune, India
userasif - Either If you dont find any jobs or if they are not compiled, you may not see the options to run the jobs. So check if you were able to find the jobs using other User id.
If not even in other user id, you may need to Reindex your project.
If not even in other user id, you may need to Reindex your project.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
No, no, no... read the documentation on what exactly the Operator role allows. An Operator can only see Released jobs - something basically no-one does anymore. In other words, the advent of Version Control completely nerfed the Operator role.
Give them access to the project as a Developer but make sure the project either contains all 'read only' jobs (via Version Control) or make it a Protected project. They'll be able to see but not change any job designs. You can look into getting around that by removing the Designer from their workstations if that ability really bothers you.
Give them access to the project as a Developer but make sure the project either contains all 'read only' jobs (via Version Control) or make it a Protected project. They'll be able to see but not change any job designs. You can look into getting around that by removing the Designer from their workstations if that ability really bothers you.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
In 8.0 there is a new role called Super Operator, who can view but not change job designs. And can run all jobs that are in a runnable state, not just released jobs.
Incidentally, Director for PDA is no longer available.
Incidentally, Director for PDA is no longer available.
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.
Thanx to all but my problem is still there........
I have tried a lot of time.....when i change role from OPERATOR to DEVELOPER....useroperator can view and run jobs but when i again change this role to OPERATOR and login again......now useroperator can not view any job.
Please help me i am stick with it.
I have tried a lot of time.....when i change role from OPERATOR to DEVELOPER....useroperator can view and run jobs but when i again change this role to OPERATOR and login again......now useroperator can not view any job.
Please help me i am stick with it.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The Operator role can only run RELEASED jobs. It's a major restriction, which is why hardly anyone makes use of that role, and why IBM has put in the SuperOperator role in version 8.0.
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.
Hmm... I think there is a Dilbert cartoon about trying something over and over, expecting it to eventually work the way to want it to.userasif wrote:I have tried a lot of time.....
Have you thought about the other suggestions made in this thread? Making the jobs read only or making the project a Protected project, for example?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Ray, smay... I told you that over a month ago. And how did we know this, you ask? Because it is in the documentation. Granted, it's kind of buried in the Setting Up Users and Group section of the 'Pre-Install Checks and Set Up' chapter of the Installation and Upgrade Guide, but it *is* there.
And... releasing jobs? Yurk. Great, now your Operators can see the jobs listed in the Director but you've got no design time information for those jobs which will severely limit your ability to support them in that Project. Good luck with that.
Oh, and keep in mind the lovely fact that the various releases (if you keep multiple versions there) are string sorted... and the last one in the list is the version that is actually run when you request a run of the base job name. So there can technically be times where the last one is not the latest one. Then there's the whole issue of Sequence jobs... I vaguely recall problems with them. Been way too long since I stopped releasing jobs.
You sure you made the right choice here?
And... releasing jobs? Yurk. Great, now your Operators can see the jobs listed in the Director but you've got no design time information for those jobs which will severely limit your ability to support them in that Project. Good luck with that.
Oh, and keep in mind the lovely fact that the various releases (if you keep multiple versions there) are string sorted... and the last one in the list is the version that is actually run when you request a run of the base job name. So there can technically be times where the last one is not the latest one. Then there's the whole issue of Sequence jobs... I vaguely recall problems with them. Been way too long since I stopped releasing jobs.
You sure you made the right choice here?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This one?chulett wrote:Hmm... I think there is a Dilbert cartoon about trying something over and over, expecting it to eventually work the way to want it to.
The definition of insanity is doing the same thing over and over and expecting different results.
-- Benjamin Franklin
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.