DSXchange

Sorry Kim, wasn't taking to 'you you' but the more generic 'you' of the OP. I'll make a small... correction... to my post.

If you unprotect your project, the state of the jobs should also automatically chagne to Non-Readonly. Umm... no. Protected and Read Only are two separate things. One shouldn't have to unprotect the project and then flip all the RO bits to NRO just to recompile things. Goodness knows what some nast...

You do... and no space between the plus sign and the date mask or you end up doing some kind of odd math. I don't see any reason something simple like this would not work from DataStage except for all the standard reasons we've talked about ad nauseam. However, since you've taken this out of the con...

If this was usenet, I'd say we have a troll.

Gateleys, you didn't blink on Kim's reference to 'dual' so, on the off chance you are on Oracle: SELECT constraint_name, constraint_type, r_constraint_name, status, delete_rule, r_constraint_name, r_owner, search_condition, deferrable, deferred, validated, bad, rely FROM SYS.dba_constraints WHERE ta...

You must not have read the fine print. "This routine should not be used more than one place in a job"... and you've called it twice in one derivation. Setup a stage variable, make the call once and then do your comparisons to the stage variable. Or check out the RowProcCompareWithPreviousValue routi...

It would help if we knew what database you were using.

These projects are protected and first need to be unprotected in order to use either method. That's not true. A protected project can be 'multi job compiled' using the dsadm userid. Granted, it is slow as molasses because of all the silly gui updating going on, but you don't have to unprotect the p...

[sigh]

You are close. Yes, you use two stage variables, but it looks like you've got them in the wrong order. And you need to compare the values up in the Stage Variables area, not down in the derivation of the incoming data. So, in the order shown below... Stage Variable Derivation svIsNew NEW_KEY_VAL <> ...

Actually, based on your example you need to do the opposite - columns into rows. Which means you can use the Pivot stage to do that for you.

The -jobstatus option would be the one. Then your return codes would be the internal codes:

1 = Ran OK
2 = Ran with Warnings
3 = Aborted

etc.

(dang, too late!)

<duplicate post cleared>

Dang site is acting up for me today. Push the button once, wait forever and then get two posts for the price of one. Sheesh.

Not possible, the stage does not support wildcards.

Sorry if my post was a little confusing. The CDC stage *is* a PX only stage, I was talking about emulating what it does under the covers in a Server job - not saying there was a Server stage equivalent.