DSJOB exceeding command line buffer

jseclen · Post by **jseclen** » Fri Dec 13, 2002 6:32 pm

Hi Kiran

You can use a UNIX Shell, define variables that contains the parameters, example,

MyPaht=/home/data/info/files/december
MyUser=dstage
MyFile=Data_20021215_Cancel.txt
MyBD=server2.myconection

when you run the job, use the command

> dsjob -run -mode NORMAL -param PATH=$MyPath -param USER=$MyUser
-param FILE=$MyFile -param BD=$MyBD

all that inside your UNIX script.

I hope this help.

Miguel Seclen
Lima - Peru

ray.wurlod · Post by **ray.wurlod** » Fri Dec 13, 2002 8:05 pm

Another approach is to have parameter values in a text file ("ini" file) that a controlling job can read and use values therefrom to set parameter values in the controlled job(s).

chulett · Post by **chulett** » Mon Dec 16, 2002 6:07 pm

Are all of your parameters *really* necessary, meaning they can change from invocation to invocation of the job? If not and the values you are passing in match the 'default' values for these parameters, then consider removing them from your dsjob command. Any parameters that are not explicitly set by the dsjob command will use their default values. Mine stay pretty short as I only pass in the one or two that change each time.

-craig

chulett · Post by **chulett** » Tue Dec 17, 2002 3:20 pm

Not to beat your (now) dead horse, but we also use different parameters based on environment. We have three projects - one for dev, one for test and one for production. The defaults for the parameters are set based on their environment so I don't have to specify them again unless something changes, just once when the job is promoted. Are you working out of a single project?

ray.wurlod · Post by **ray.wurlod** » Tue Dec 17, 2002 5:07 pm

Don't forget that run-time default values can be set in Director (Job > Set Defaults). You can then also disable prompting for those parameters that are different solely because of the project in which they occur.