DSXchange

Did Craig call Ray a Uber? I don't think I would take that Ray.

Quit using Designer. That is the real problem.

Yeah, what Ray said.

You can set the log to clear itself after every 3 or 4 runs or whatever number you want. Clearing the instance ids is another problem.

Why do you want to do this?

You are missing a semicolon on the second SQL statement.

Post the VB code.

Why not ExecDOS? I think all these commands can be done at the command line.

If you are doing this in a UNIX script or BASIC you need to validate the parameter name before you set the value or dsjob will fail. We did this with

dsjob -lparams

You need to search for that code. I posted code snipets.

http://www.dsxchange.com/viewtopic.php? ... ht=JOBTYPE

Has several ways to get this.

Way to go Ray.

My point is you can do it in a script. We have every parameter for every job in a text file like: ParamName1=ParamValue1 ParamName2=ParamValue2 The script only sets the ones that are valid for the job you are about to run. Works great. There are parameter files like this for all jobs called GlobalPa...

If you are doing this in BASIC then you need to call the API routines to do the same.

You need to validat your parameters using dsjob -lparams $ProjectName $JobName | awk '{printf("%s=\n", $1)}' | sort > $JobParamListFile echo "${ParamName}=" | fgrep -f$JobParamListFile >/dev/null if [ $? -eq 0 ] then You need to add an = to the the par...

I need to post a new version which works well with PX jobs. Maybe soon. I think your first step is to put stats in tables so you can measure how it is now against what you may change it to.

All of this is controlled thru config files. Your mount points should match you config file, one per node.

Craig

Maybe he can call your peeps. What do you think?