Schedule datastage job using command line

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
PSADMIN
Participant
Posts: 3
Joined: Fri Dec 15, 2006 8:36 am

Schedule datastage job using command line

Post by PSADMIN »

Hi,

We are using Ascential Datastage 7.5.1A

Does anybody know, what is command line syntax for scheduling datastage job?

I look forward to your response.

Regards,
Suhas
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There really isn't a commond line option for scheduling a DataStage job. However, there *is* a command line option for running a DataStage job which can be be leveraged by your scheduler. What is your scheduler of choice, by the way?

That option is dsjob and it is fully documented in the Command Line Interface chapter of the Server Job Developer's Guide pdf. Or if your paths are setup correctly, you can just type 'dsjob' and get a usage statement.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

From a private email:
PSADMIN wrote:Thanks for your reply !!

I am using Ascential Datastage scheduler, but I need to trigger scheduling of particuler job based output from an execution of other job.
:!: First off, private email is for exactly that - private conversations. This is the place to continue a conversation started here. So, to that end...

The 'DataStage Scheduler' on UNIX is just a front-end to cron which is what does the actual scheduling. However, it seems to me when you say 'schedule' you may actually mean 'run'.

If that's the case, then Sequence jobs are just what you need. It's pretty straight-forward to create one that would run a job, check whatever it may have output and then conditionally run another job based on the result of those checks. No command line required. However, it also can be done from the command line, if you prefer, using the dsjob command noted previously and some intelligent scripting.

If you really mean 'schedule', then please explain your requirements in more detail. Right now we don't really have enough information to give you any kind of a coherent answer or alternative approach.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Great... how is this a 'workaround'? :?

How about coming back here and explaining whatever issue or issues you still have with this and let's get them straightened out.
-craig

"You can never have too many knives" -- Logan Nine Fingers
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Hehe.... :P
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
bhaskarjha
Participant
Posts: 67
Joined: Thu Apr 06, 2006 7:13 am

Post by bhaskarjha »

You can create a sequence as required then you can run this sequence, by using dsjob utility. Once you enter the command with dsjob in a script. you can make a crontab entry to schedule this script. Alternate way is just create a simple job (flat file) to (flat file), then call this script in this job ( by specifying location of script in job properties).
Thanks,
Bhaskar Jha
Post Reply