DSXchange

No, back before version 6 it was a bad idea to have really long job and stage names. I seem to remember 40 was about the maximum before DS internally started truncating things.

If your before-routine is using "openseq" commands on a common sequential file, they will LOCK each other out. Consider passive reads such as calling DSExecute to "type" the file into screen output return variables. I'd bet a box of donuts your jobs are locking each other out. OPENSEQ will obtain an...

How do you determine if the job is "running"? What is the status of the job in Director? Are there stages that say "Starting" in the Monitor that contain SQL? Are there before-job routines that are executing? What's in the logs of the jobs? Have you check the DS server to see what processes are curr...

Also, would the suggested change apply to the use of hash files? It's very common for me to see jobs in which a hash file is populated in the same job in which it is referenced. Hashed files are not the same as sequential files in these regards. It's perfectly fine to read and write to the same fil...

this process has to be automated. What do they mean by automated? How about the compiler wizard in DS Manager? That would do the trick. How about the free Batch job on my site that compiles jobs and routines? That would show you the logic you need. Those same jobs have their logic posted on this si...

Per the user's requirement, the polarity of the percentage doesn't matter:

You get 2 because the laws of mathematics dictates that is the answer. Two negative numbers multiplied together always produce a positive, and division is the same.

If you don't like your answer, just multiply by -1 whenever you need to change polarity.

I never wrote a looping Sequencer that passes the loop argument to jobs as a variable. I'm sure others have written one. In a Batch job, it's a piece of cake. In pseudo code: For i=1 to 40 ...Call DSAttachJob... ...Call DSSetParam(jobhandle, parameter name, i) ...Call DSRunJob... ...Call DSW...

Batch job control with a loop, or a Sequencer with a loop. Both feed the appropriate parameters to controlled jobs.

Let's all remember that premium content answers are not visible to everyone, and therefore, some non-premium folks may answer something similar to a premium content answer without knowing it.

For some ideas, look here:
http://www.dsxchange.com/viewtopic.php?t=85578

You're on the right track. My company wrote a data cleansing function library to use an external table of data quality rules that is called from DS. It's a lot like you've suggested. The basic idea I would recommend is to not call a function on every column in every row, but rather develop a stand-a...

Chances are the job aborts and you're just getting a message from the CLI driver about it terminating. The root cause I'm guessing is the hash file size exceeded 2.2GB.

This is a duplicate post.

My guess is that you blew thru the 2.2GB hash limit on the 32BIT hash file and the job aborted. Consider creating the file as a 64BIT file.