Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

dsjob command to execute DataStage jobs

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting dsjob command to execute DataStage jobs
# 1  
Old 10-31-2007
dsjob command to execute DataStage jobs
Hi Friends,

I am using a dsjob command in a unix script to invoke DataStage jobs.
DataStage server jobs (version 7.5.2)

The command looks like thisL:
$DSBinPath/dsjob -server :$SERVER_PORTID -run -mode NORMAL -jobstatus -param INPUT_GCDB_DIR=$InputFilePath -param INTERIM_DIR=$SequentialFilePath -param SCRIPT_DIR=$ShellScriptPath -param CountryID=$CountryID -warn 0 $ProjectName $JobName.$CountryID

Then there is another command to check for job status.
JOB_STATUS=`$DSBinPath/dsjob -server :$SERVER_PORTID -jobinfo $ProjectName $JobName.$CountryID | head -1 | cut -d"(" -f2 | cut -d")" -f1`

My query is :
What does each return code value (0,1,2) for JOB_STATUS signify?

Regards,
Suresh
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

How to compile a Datastage Job using Execute Command Stage or Routines in Datastage 11?

I am trying to compile the datastage jobs using the Execute Command stage in datastage 11 or any Routines if possible. My datastage is on Unix machine. So, How can I Compile a datastage job in UNIX from command line or any Routines. Please help me in doing so. Thank you. (1 Reply)
Discussion started by: elena jessi
1 Replies

2. Shell Programming and Scripting

Command to check only Autosys running jobs with autorep like command

Hi, Is there any specific command to use to check only say Running jobs via autorep or similar command for Autosys? (0 Replies)
Discussion started by: sidnow
0 Replies

3. Shell Programming and Scripting

Command to stop all the cron jobs

Hi All, Please provide the command to stop all the cron jobs. Thanks in Advance Regards, Sindu (2 Replies)
Discussion started by: indira_s
2 Replies

4. Shell Programming and Scripting

waiting on jobs in bash, allowing limited parallel jobs at one time, and then for all to finish

Hello, I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies

5. Shell Programming and Scripting

jobs command in a script.

When you run this script in a command prompt it runs fines and echos the background jobs but when written to a script and run, it outputs nothing. for job in `jobs -p` do echo $job done Any ideas what I might be doing wrong. Thanks, SK (3 Replies)
Discussion started by: kanas01
3 Replies

6. Shell Programming and Scripting

DataStage log file output via dsjob command

Hi, I do have 2 files Job_Name Job1 Job2 Job3 Instance_Name USA IND SRI I need to write a script, i.e, output of job1.USA should come in log in unix. i.,e When it runs for the first time it should run as Job1.USA next run Job1.IND Job1.SRI (3 Replies)
Discussion started by: dsnaveen
3 Replies

7. Shell Programming and Scripting

capture last run log using dsjob

Hi All, Could you please let me know how to capture the WARNING or FATAL errors for the last run log using dsjob -logsum in Korn Unix Shell. Thanks in Advance, (0 Replies)
Discussion started by: HemaV
0 Replies

8. UNIX for Dummies Questions & Answers

jobs command

Good morning! When I type in the command "jobs" it takes me back to the command prompt? Any idea why and how I can display all the jobs that are currently running off that host? Ben (6 Replies)
Discussion started by: bigben1220
6 Replies

9. UNIX for Advanced & Expert Users

invoke windows datastage dsjob from unix

hello, i have a windows server with datastage. In another machine, unix machine, i have a shell script that need to invoke the datastage dsjob. Can anyone help me? (0 Replies)
Discussion started by: anaconga
0 Replies

10. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ... (1 Reply)
Discussion started by: GrepMe
1 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

queuedefs

queuedefs(4)							   File Formats 						      queuedefs(4)

NAME

       queuedefs - queue description file for at, batch, and cron

SYNOPSIS

       /etc/cron.d/queuedefs

DESCRIPTION

       The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
       The format of the lines are as follows:

	      q.[njobj][nicen][nwaitw]

       The fields in this line are:

       q	The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs  started  by  batch  (see
		at(1)); c is the default queue for jobs run from a crontab(1) file.

       njob	The  maximum  number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
		njob jobs will be run, and the others will be run as jobs that are currently running terminate.  The default value is  100.

       nice	The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user.  The default value is 2.

       nwait	The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in  that  job's
		queue, or because the system-wide limit of jobs executing has been reached.  The default value is 60.

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       Example 1: A sample file.

       #
       #
       a.4j1n
       b.2j2n90w

       This  file  specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
       of 1.  As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before  trying
       again to run it.

       The  b  queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2.  If a job
       cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All	other  queues  can
       have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
       are running cron will wait 60 seconds before trying again to run it.

FILES

       /etc/cron.d/queuedefs	       queue description file for  at, batch, and  cron.

SEE ALSO

       at(1), crontab(1), nice(1), cron(1M)

SunOS 5.10							    1 Mar 1994							      queuedefs(4)