DSXchange

Yeah. That's why it's called yousucks.h, Ray.

parsimonious

Trust Ray to teach you a new word a day!

Heh. Where the heck did you come up with that word, Ray?

Trim() can do it. Convert() can do it. Each works in a different way -- just depend on what you want to do. You will need to pass a hex value of the newline character in order for that to work with newline character.

("0xblah")

You will need to create a buildop or custom stage to do this type of task.

Just pre-sort the data, and throw it in a buildop which will open a file, watch the data flows through, and when the data changes, close the file, and open a new one.

Buildop definitely will serve you well on this one.

Ray is correct. In fact, you probably are better off with a Lookup stage. Heavy volume? Hah. Maybe for output, but not for a lookup. 300k of reference file that does not have to be sorted? Do a lookup. Join stage sorts within the framework (unless you already sort the data beforehand.) That adds time.

I just discovered that there was a nasty bug within JobMonApp. If your job crash hard (i.e. "Error on line 10234 of file yousucks.h"), your JobMonApp may go down with it.

Fortunately, this bug was fixed for 7.5.

Modify Operator (Stage) used to be the primary method for conversion of nullability type. Now you can do it within Transformer Stage. Do an "If IsNull(Field) Then Value Else Value" Modify Operator use OSH functions, not DataStage functions. So IsNull() will not work. is_null() will work.

I would like to create a PX routine that returns a (modified) substring of an input string, much like this one posted by another user of this forum Modified substring? That can easily be done in Transformer stage. Give us your rules, and I can whip something up without you having to build a BuildOP...

As a rule of thumb if I have under 50,000 reference rows I try to use the Lookup stage. It has the best interface of the three and has good reject and conditional lookup capabilities. Only 50k? Geez, a bit stingy with your Lookup use. I have seen excellent (read: better than Join) performance upwar...

Read the Install and Upgrade Guide. I'm sure they have included a minimal set of requirements for you.

But again, as Ray says: More is BETTER. What is the most you can afford? That's the one you're going to get.

Unfortunately, I am not able to test my solution on 7.5. I did test it on 7.1r2, and it worked. I did not do anything special (AsInteger() or anything like that) -- just plain straight varchar to integer conversion, doing the conversion with the values you provided. It produced the expected results....

Ranged Lookup is not yet supported in EE. It is a feature coming very soon now (or probably already in 7.5.1, need to double check that.)

You will need to use a buildop if you're using a EE solution. Routines are also a good alternative if you're using Server.

Here's a true PX solution: * * * Presuming that input field is entitled "DSLink3.currentDate". Have 3 stage variables in a Transform stage: A - JulianDayFromDate(DSLink3.currentDate) B - WeekdayFromDate(DSLink3.currentDate) C - If (b >= 5) Then (a - (b - 5)) Else (a - ((b + 7) - 5)) In the...

That is a question only Ascential can properly give you. They have specific rates for specific regions that your sales group will need to negotiate on.

Contact your Ascential provider for further details.

You may try it, but you will NOT be supported by Ascential.

Good luck.