DSXchange

pradeepleon wrote:error token for -14 :DSJE_TIMEOUT The job appears not to have started after waiting for a reasonable length of time. (About 30 minutes.)

Actually, it's more like 60 seconds.

Minhajuddin wrote:But I am unable to write a routine which takes the jobname, stage name and link name as parameters and gives the count of rows as the return value.

And why is that? What have you tried? Why don't you post your current effort here wrapped in [code] tags and we'll help you 'fix' it.

Yep, that sounds fine. Let us know how it goes.

A 'better' answer would be to build a Sequence job using the new Start Loop, End Loop and UserVariables stages to get the list of files and run the processing job iteratively, passing it a new filename each time. What version of DataStage do you have, one of the 7.5.x releases with the stages I ment...

If it worked we wouldn't be having this conversation.

What "doesn't work" about it? I'll have to defer the gory details to others more Windoze savvy - I could walk you thru a UNIX server but not when it's Windows, sorry.

From there to a Transformer (where you would do the setting magic) and from there pretty much anywhere. Doesn't really matter in a sense as it won't be used. For example, it could be a flat file writing to /dev/null or it could be a dedicated 'user status' hashed file with the Key field set to the j...

where file1, file2, file3 and fileAll should be fully qualified. Or you can 'cd' and then cat in two steps: cd #P_FILE_DIR# && cat *.csv > cat_file.csv This also shows that you can use your job parameters in the commands as well. You are using parameters for things like this, yes?

The easiest way would be to issue the wildcard 'cat' before-job using ExecSH to a fixed filename. Check under the Job Properties tab if you're not sure where that lives. Or try doing it in the Filter option of the Sequential file stage as others have mentioned. Or you could build a 'batch' job that ...

You don't need a routine unless you want to tackle building a generic job control structure that any job could leverage. And rather than do that, I'd suggest download Ken Bland's Job Control Utilities as he's already done the dirty work. That or pull ETLStats down from Kim Duke. Simplest approach wo...

I'm a little lost on your requirements. This 'list of keys' in your example - are you saying you'd want all three to be fed to your job, one at a time so their results are in three separate output files? Or do you want all of them run at once? For the former, that sounds like a LOOPing Sequence job...

I think the problem was because NULL and "" are not considered same by Datastage That would be because they are not the same - and not just as far as DataStage is concerned. The former is an unknown value and the latter is a known, empty value. Hence the need for two checks when both conditions are...

I tried everything you guys said above. I couldn't get it to run. So for windows, what I did was 1) copy the '.uvconfig' and 'uvconfig' to the bin directory 2) run 'uvregen' 3) copy '.uvconfig' back to the parent directory. Where did anyone advise to move the uvconfig files around? I have no idea w...

What have tried? It is literally just a matter of creating the job parameter and then using it in your SQL with hash/pound signs around it. For ODBC you put anything you need for the 'where' claus in the WHERE clause box on the Selection tab but don't add the 'where' yourself. So: ID > #P_ID# Would ...

It's the DRS or Dynamic Relational Stage. Check the drsstage.pdf file in your Docs folder for the details.

Try again. This is for DataStage TX which ain't the same thing as PX. You need to post over in the Enterprise Edition forum:

http://www.dsxchange.com/viewforum.php?f=8