Scheduling Jobs at V8

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Scheduling Jobs at V8

Post by ArndW »

Perhaps I am just having a bad day and a mental "whiteout", but a colleague has just brought up an issue that I cannot quite understand or explain.

We are running Version 8 on AIX. If I try to schedule a job from the director I get an error message stating that I have insufficient privileges to perform that function - but on close inspection, the error is referring to the "at" command, not the UNIX "cron" command that I would have expected.

I was certain, until now, that scheduling a job from the director on a UNIX DataStage server would, in fact, add the request on the Server and not on the client. Can anyone confirm this supposition, or tell me that my remembery is incorrect?
ray.wurlod
Participant
Posts: 54595
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

at is used for "one shot" schedules, cron for repeating schedules. It was thus in earlier versions also.
Note that this is the UNIX command at and not the Windows command AT.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Exactly, you've always needed 'allow' permissions to both cron and at for UNIX. And as Ray notes, cron does all of the repeating schedules while at does schedules that only run once. Granted, the vast majority of times you're doing the 'every X' type scheduling so for some people the issue may never surface.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Ahh, that explains it, when I tested it I must have clicked on a once-only button. Now that I tried it again with "weekly" I get the expected cron error message (since the user really doesn't have the required access)
Post Reply