DSXchange

Aparna, normally I would have said that start/stop times are those of the server, but you have discovered that this is not the case for the DB2 reporting on PX jobs. It seems to take the start time from the DS server and the end time from the DB2 server. This sounds like a bug which you should repor...

Aparna - you must have some really special hardware that the rest of us only know of as "quantum fuzzy hyper spatial computing" or QFHSC . I need one of those Sounds like you have a reprodoceable test case for you support provider. What hardware and OS are you on? Actually, could it be that DS is ge...

Well, there goes that theory. Some part of DS can get the OS time in milliseconds, but on some systems those values aren't always too accurate (I recall HP-UX issues years ago); so if the job finished within 1 second and the millisecond portions of the start and end times don't come from OS correctl...

I've heard here that people have seen it but have not personally seen it. could it be that the job started on one day and finished on the next; since the formula could use "(EndTime-Startime)" as part of the computation that would cause the error on a day rollover unless it is accounted for.

I looked at the post and thought that most likely this will return more than one row unless KEY_1 is the only key; which is why a (single) READ wouldn't be a solution. We'll see what the original poster says and take it from there.

Ray's recommendation is by far the more efficient one, if your hashed file has just one key and it is "KEY_1". Otherwise without a dictionary or VOC pointer you would need to read through the whole file using OPENPATH to get the pointer, SELECT to select all the records in the file and loop around a...

mbsiddu, There are 28 posts that match the search string "() failed, Not enough space" so I would hazard a guess that someone has already had this error before Please use the search facility located in the menu bar of ever page on DSXChange - it saves you a lot of time since you immediately get an a...

You don't need to use a terminator activity, just put one single conditional output on your execute command stage that calls the shell script. I hope you know that there is a stage, called Wait_For_File, which does exactly this and is builtin to DataStage and is much easier to use than calling exter...

You cannot issue a DataStage SELECT or an SQL SELECT on a hashed file that is only referred to by path. In order to do this you need to create a file type record in your VOC. One way to do this is to use the TCL command SETFILE {pathname} {filename} {OVERWRITING} which ...

What, then, is the problem? What does

We need main_program initialization for the job after enviromental settings information in the log.

mean?

What happens when you try to stop the job in the director? What is your job doing (i.e. sometimes a job can seem to "hang" when the database it is writing to hangs)

It so happens that DSINCLUDE is the include file that DataStage uses, it is a subdirectory called "dsinclude" in the project directory. SAMP.H is a file in that directory and you can look at it. n.b. I think that it is bad practice to put user defined include files into DSINCLUDE as they might be ov...

The $ isn't the keyword, "$INCLUDE" is. This is a compile-time switch to include source from another file, in this case "SAMP.H" in "DSINCLUDE". Your code probably will not compile without it. You can read up on $INCLUDE and $INSERT in the DataStage BASIC Programmers Guide

funnily enough those are the 2 functions I find most useful in a typical PX transform stage as well.

They retrofitted those two functions into PX and kept the same order of arguments as well.