How to delete a schedule for another user
Moderators: chulett, rschirm, roy
How to delete a schedule for another user
Hi All,
I need to unscheduled a sequence from Director which is scheduled by another user. I am not able to see the schedule, hence I cannot unscheduled it. Could you please help me?
I need to unscheduled a sequence from Director which is scheduled by another user. I am not able to see the schedule, hence I cannot unscheduled it. Could you please help me?
Rumu
IT Consultant
IT Consultant
Does anyone have elevated privileges on the server itself? Unless the architecture has changed, they're just crontab entries so technically someone with permissions could go in and edit / empty their crontab entries. There may also be an equivalent in Director.
-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:
Ray, are you saying that will work for someone who is not the original scheduling user? Because that's the question at hand.
Last edited by chulett on Mon Jul 09, 2018 7:21 am, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Ray,
The option that your are suggesting is working for the user who scheduled the jobs but if someone else is scheduled then not able to view the schedule for other user.
We asked an user with root prov to edit the crontab entry and that worked.
Wondering why we are not able to view scheduled jobs done by other users.
The option that your are suggesting is working for the user who scheduled the jobs but if someone else is scheduled then not able to view the schedule for other user.
We asked an user with root prov to edit the crontab entry and that worked.
Wondering why we are not able to view scheduled jobs done by other users.
Rumu
IT Consultant
IT Consultant
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi Ray,
No, not everyone is in dstage group. We checked under /etc/var/spool/cron folder and found all the users that have cron entries. We changed permission by using chmod -R 775 and then edited the cron entry of the specific user whose entry was to be deleted.
What is cron.allow and at.allow?
We were asked to check cronjobs or atjobs entries.
No, not everyone is in dstage group. We checked under /etc/var/spool/cron folder and found all the users that have cron entries. We changed permission by using chmod -R 775 and then edited the cron entry of the specific user whose entry was to be deleted.
What is cron.allow and at.allow?
We were asked to check cronjobs or atjobs entries.
Rumu
IT Consultant
IT Consultant
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The cron.allow file specifies which non-root users are permitted to use the cron command, while the at.allow file specifies which non-root users are permitted to use the at command.
That said, I'm not sure that DataStage 11.x still uses cron and at for scheduled jobs. It may be that the Information Server scheduling service is the culprit. Check with IBM about how to configure that.
That said, I'm not sure that DataStage 11.x still uses cron and at for scheduled jobs. It may be that the Information Server scheduling service is the culprit. Check with IBM about how to configure that.
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.
From Director, an admin user, again, can only unschedule their own jobs--only the jobs that they themselves scheduled. In Director, no user can unschedule any other users' jobs.
The only option in that case is at the operating system level through root access or sudo root access, is as you mentioned, to edit the other users' crontab or at entries.
The only option in that case is at the operating system level through root access or sudo root access, is as you mentioned, to edit the other users' crontab or at entries.
Choose a job you love, and you will never have to work a day in your life. - Confucius