running a series of scripts (ddl/dml) from job sequencer

kishoreramachandran · Post by **kishoreramachandran** » Thu Nov 30, 2006 3:21 pm

A series of scripts (ddl/dml) need to be run through the job sequencer.
the 1st script will be run with 5 different input values and then the 2nd script with the different set of input values and so on. What will be the best design for this.

chulett · Post by **chulett** » Thu Nov 30, 2006 3:25 pm

What value is the ETL tool adding to this? Why not just script it?

kishoreramachandran · Post by **kishoreramachandran** » Thu Nov 30, 2006 3:27 pm

they want everthing to be controlled through datatage

chulett · Post by **chulett** » Thu Nov 30, 2006 3:33 pm

They need a good... well, nevermind what they need.

Create a standard routine that executes shell scripts. Then a Sequence job with a series of Routine Activity stages can run them. Or code a series of DSExecute calls into the Job Control tab of a Server job and run that.

Or push back and tell 'them' that just because you've got a shiny new DataStage hammer, not every problem is suddenly a nail.

ray.wurlod · Post by **ray.wurlod** » Thu Nov 30, 2006 6:14 pm

If they insist upon DataStage for control, why do they insist upon shell scripts? Why not have DataStage do the whole thing? After all, they've paid the money!

It is sometimes necessary to push back, particularly when what "they" want can not be intelligently justified. Please be advised by a couple of very experienced DataStage practitioners.

As to your original questions, what's wrong with sufficient Execute Command activities in the job sequence? The values can be passed to the shell scripts either as command line arguments (retrieved from $1, $2 and so on) or as environment variable values.

kishoreramachandran · Post by **kishoreramachandran** » Thu Nov 30, 2006 7:32 pm

basically what they plan is to cut and paste the same script with may be some minor changes and execute within datastage

ray.wurlod · Post by **ray.wurlod** » Thu Nov 30, 2006 9:40 pm

They spent such a huge sum on a graphical tool so that they could paste scripts into it?!! Please advise names of persons who make decisions and persons who sign checks. Urgent requirement!!!

narasimha · Post by **narasimha** » Thu Nov 30, 2006 9:50 pm

Make your script clever enough to handle your minor changes and pass them as parameters.
or change the contents of the script everytime you run this script(Not a good practice but an option

)

kishoreramachandran · Post by **kishoreramachandran** » Fri Dec 01, 2006 2:56 pm

none of the replies have helped me so far

ray.wurlod · Post by **ray.wurlod** » Fri Dec 01, 2006 3:09 pm

This

ray.wurlod wrote:As to your original questions, what's wrong with sufficient Execute Command activities in the job sequence? The values can be passed to the shell scripts either as command line arguments (retrieved from $1, $2 and so on) or as environment variable values.

is a solution.

If you have chosen not to implement it, then of course it hasn't helped you!

chulett · Post by **chulett** » Fri Dec 01, 2006 4:10 pm

These

chulett wrote:Create a standard routine that executes shell scripts. Then a Sequence job with a series of Routine Activity stages can run them. Or code a series of DSExecute calls into the Job Control tab of a Server job and run that.

also were solutions offered to you.

narasimha · Post by **narasimha** » Fri Dec 01, 2006 7:32 pm

kishoreramachandran wrote:none of the replies have helped me so far

The solutions given to you, are some of the best available ways you can implement your requirement using datastage.
Have you tried to implement them?

kishoreramachandran · Post by **kishoreramachandran** » Sat Dec 09, 2006 5:42 pm

if i use dsexecute to execute a shell script name 1.sh how do i give the parameters. can you help with the actual command.

chulett · Post by **chulett** » Sat Dec 09, 2006 6:02 pm

You build a complete 'command string', parameters and all, and pass that to DSExecute for it to run. We can't just 'give you the command' as each would be different. Use the concatenation operator - the colon (:) - and put together all the same parts you would put on the command line if you ran the script by hand.

For example, let's say you wanted to run script '/user/fred/scripts/get_gone' and you needed to pass it the current date. From the command line you might type:

Code: Select all

/user/fred/scripts/get_gone 2006-12-09

For DSExecute you would build the same string, but use a variable or job parameter for the current date:

Code: Select all

CmdString = "/user/fred/scripts/get_gone ":DateParameterName

Then you would use the resulting CmdString in your DSExecute call.

kishoreramachandran · Post by **kishoreramachandran** » Sat Dec 09, 2006 6:26 pm

when I am running in unix the will the command be

dsexecute("uv",cmd,output,0) what should i give for output, and if I have to code so many dsexecutes can I do it in 1 server job.

does it mean that the job will not have any stages .