DSXchange

Try doing this at the top of the logic to demonstrate how it works: txt = "" txt<-1> = "this is output line 1" txt<-1> = "this is output line 2" txt<-1> = "this is output line 3" txt<-1> = "this is output line 4" txt<-1> = "this is output line 5...

Any chance you're sourcing the same table you are inserting into?

There's two uses for a stored procedure: 1. "do" something 2. stream output Using the ODBC stage to "do" something is not how the stage is intended. It's meant to run a stored procedure to stream output back to the stage. Thus, you are required to have an output link even though no rows are expected...

I need to use the UV stage b/c I'm doing a LEFT JOIN with another Hash file No caching available doing this. Using the hash file stage as a reference lookup gives you the equijoin, which unconstrained is an outer join on the driving primary input stream. You have the option of caching this lookup, ...

You can install just PX without Server installed or licensed. It sure works funny, you have Sequence jobs, but no Server jobs. Under the covers they are the same thing. You can have DS BASIC functions, just no Server jobs. When you do the import into that situation, the Server jobs drop away and you...

You never know, I might have gone back in later and added that paragraph in.

Definetely use the Hash stages - you get to use caching and all kinds of cool tricks. If you created a hash file with a UV stage, it puts a bunch of gunk into the internal structures in a DataStage project because the hash file is now treated like a table. Your metadata issues are because the data t...

You need to construct a truth table. One of your codes is the highest pecking order value. Another code is the second, another the third. For example: A > B > C > D > E > F If you read a row for a group, and its code is E, then lookup the current value in your hash file. If the current value is less...

Forget about any effort to manage permissions within a project. Forget it. Do not mess with umask, do not mess with unix file level permissions. Use the tool as it is intended - users get access to a project or not. If you need to separate jobs by user within a project, your solution is to separate ...

can we agree that I'm not as right as you Okay, , I may be wrong, but I do believe there are reasons to use the CREATE statement for the file to be created, I just can't quite remember right now the reasons there is an explicit statement for doing so. If it's an unnecessary extra step, then I stand...

PhilHibbs wrote:A follow-on conclusion from this is that DataStage does not short-circuit its boolean logic. Is this correct?

That would be true, all elements in the expression are evaluated, even if the first element will cause a result no matter the evaluation of the rest of the elements.

Any chance you tried to put more than 2.2 gigabytes of data into a 32-bit hash file? If so, search the forum for 64BIT hash files as a temporary solution, then go back and look at why you're building such a large file.

Not to be petulant, but with all respect, the function posted by Arnd has some flaws: 1. It does now allow you to add more than 12 months to a given date. If you ever need to add 14 months, you need the extra logic as in the function I posted. 2. It also does not allow for the fact that DS BASIC its...

A code -14 means that your system is overloaded and Ascential has gracefully allowed the particular job control API they wrote to KABOOM blowup rather than generate a return code that allows the job (or in the case of well-written home-grown job control) to gracefully handle this situation. What is ...

Look back at your examples in your post. You refer to "code" as the column that indicates what should be done with the rows. You gave some sketchy rules, such as a code 30 means throw away all rows with a code 20. That tells me that 30 is important. You gave more rules such as a code 4 means throw a...