Executing dsjob command from routine activity

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 5:17 am

Hi,

I am triggering a job from sequence using a routine activity.

inside the routine activity i am use ExecSH.

and passing teh dsjob command as input argument.

the job runs and teh jobs log is also fine, but the log of the sequence says.

JobControl (ExecSH): Error when executing command: dsjob -run -jobstatus -param SRCSYSTEM PROJ JOBNAME.

Output from command was: ***
who: 0551-012 The process is not attached to a terminal.
Do not run who am i as a background process.

what am i doing wrong.

Regards,
Samyam

chulett · Post by **chulett** » Wed Jul 06, 2011 6:29 am

samyamkrishna wrote:what am i doing wrong?

Running a job using ExecSH from a routine activity stage. Any particular reason you can't use the Job Activity stage?

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 6:47 am

The job names ( the invocation id ) and parameters are decided at run time.

chulett · Post by **chulett** » Wed Jul 06, 2011 6:52 am

Invocation IDs (which can be parameterized) and other job parameters "decided at runtime" are easily accomodated in the Job Activity stage. IMHO, you'd be best served by going that route.

If you really want to go the ExecSH route, post the routine code.

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 6:57 am

Hi craig,

Its the built in ExecSH routine.

the argumet is "dsjob -run PROJ JOBNAME"

chulett · Post by **chulett** » Wed Jul 06, 2011 7:11 am

So, there's no routine code involved and all the stage does is call ExecSH? Use the Execute Command stage instead, run dsjob from there if that's all you are doing.

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 7:24 am

alright craig. will discuss with the team and give you an update.

But i am just curious to why that error is coming.

PhilHibbs · Post by **PhilHibbs** » Wed Jul 06, 2011 7:28 am

Do you need to specify -wait in the dsjob command?

chulett · Post by **chulett** » Wed Jul 06, 2011 7:33 am

The first post shows them using "-jobstatus".

As to the why of the error, you'd probably need to go to support for that since we're not privy to the inner workings. But to me it stems from improper use of the Routine Activity stage with ExecSH, I would think it would be fine if you wrote an actual routine and then inside that routine called ExecSH.

chulett · Post by **chulett** » Wed Jul 06, 2011 7:57 am

I'm going to repeat something - if all you are determining dynamically is the Invocation ID then there's no reason to not use a Job Activity stage for this. However, if you are actually deciding on the job name as well at runtime, then this approach is appropriate.

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 8:01 am

PhilHibbs wrote:Do you need to specify -wait in the dsjob command?

Hi,

Yes we are using wait and a lot of other parameters as well. I have just given a sample.

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 12:01 pm

chulett wrote:Outside of a dog a book is man's best friend
Inside of a dog it's too dark to read

super funny

chulett · Post by **chulett** » Wed Jul 06, 2011 1:38 pm

Groucho Marx.

samyamkrishna · Post by **samyamkrishna** » Wed Jul 06, 2011 11:10 pm

Hi,

I am also passing the job name at the run time.
But have not yet discussed about using the execute command activity instead of routine activity.

Hope fully will finalize on that today.

Thanks,
Samyam

samyamkrishna · Post by **samyamkrishna** » Thu Jul 07, 2011 3:58 am

we are going with Execute command activity.

DSXchange

Executing dsjob command from routine activity

Executing dsjob command from routine activity

Re: Executing dsjob command from routine activity

Re: Executing dsjob command from routine activity