DSXchange

I never use those 'discard' options but I would think a reject link would work for you. Create one to a flat file from your transformer and in the constraint mark it as a Reject Row. Basically, anything that doesn't go out to your target will instead go down that link. Make sure it shows as the last...

So... you just want to add 365 days to the date? Is that what this boils down to?

Use IConv to convert the date to internal format, add 365 and then convert back to your external format with OConv.

No. You'd need to have a clear understanding what precisely 'adding a year' to any given date means and then write your own. You'd also need to know what kind of dates you need to handle - any format? One particular format? What format do you return the result in? Things to think about. If it is as ...

There's practically always a way. Sometimes all it takes is another set of eyes. And no, I don't believe there is any way to disable warnings, hence my advice to eliminate them instead. If that's incorrect, I'm sure someone more DB2 savvy will be along eventually to correct me. Worst case you could ...

Take the query to whatever you have in the way of a 'tuning' resource - your DBAs perhaps? Restructure the query so that it is more... 'optimal', meaning that it would stop throwing that 'Hey, this may be sub-optimal!' warning. DataStage is not your command editor, it actually checks and reports war...

Well... yes, you have to determine which fields need to have null handling. Note that that is a blanket statement regardless of source or situation - one of your jobs as a developer is to determine if nulls will wreak havoc on your process and handle them properly. Always. While we'd all love to hav...

Slide your Columns tab over to the right and investigate the 'Incomplete Column' option. This will allow you to read the file and properly treat the new line as data.

We know all kinds of things that may be different. The hope here is that Rakesh puts some effort into determining what is different betweeen his environments. This is not something we can do for him other than to guide. However, if causes can be determined we can help with the resolution. And if a c...

Was that for my benefit? That aspect of the issue was resolved in the linked post. Read the original post in this thread again: I have written a routine to get the row count of a link, it works fine in some places, in sequencer(trigger column) some places it wont. It's not that it doesn't work at al...

What changes are to be made to what precisely?

You should call your routine using the Routine Activity stage and then check the $ReturnValue of that in your trigger expressions.

And (as noted) in the multiserv.pdf document.

You must be using -jobstatus with your dsjob command, that's what tells it you want an exit code of 1 for OK, 2 for Warnings, etc. You could use -wait instead in the dsjob call for more traditional exit code handling. Simplest answer is to tell Tivoli what is a good exit status and what is a bad one...

You can't. Use a normal OCI stage - first in the Link Order and constrained by @FALSE so it receives no rows but just performs the truncate before the BL stage starts.

Two fields in the hashed file, a 'hard-coded' key value (say "X") and your count as data. Then perform the lookup using "X" and your constraint can check if the data value returned is zero or not.

No, the Pivot stage is columns to rows.