DSXchange

No, there are no built-in variables in a Sequence job. You can certainly add such a check, but you'll need to bring the value in to check as a parameter or encapsulate the check in a routine. In either case, based on the result you can then branch to the actually run steps or bypass the run entirely.

You shouldn't be losing anything, that constraint should only be on the delete link and there shouldn't be any constraint on the normal loading link. Records don't have to go down one link or the other, they can go down any number of links.

dsscholar wrote:cat text_file > directory\parameter_file. But how to do this in windows.

The exact same way as you have the MKS Toolkit installed, but if you want the "Windows way" then just replace cat with type.

Yes, that is precisely what the CFF stage is for.

I thought Connectors were PX only... or at least initially. When did they come over to the Server side? However, I did see in the 8.5 documentation that basically every stage other than the Connectors are listed as 'deprecated'.

Two links to the ODBC stage, ordered properly, with the delete link being sent first. Constrain the delete link to only send the first row to the target, for example using @OUTROWNUM=1.

Source has date column through which incremental extraction happens. First time start_dt = 1-1-1900 and end_dt = sysdate -1. Next time end_dt + 1 will become start_date and sysdate - 1 will be end_dt. This s just to ensure that no record of today should be missed during anytime of run. We introduce...

Moved.

Where the metadata was imported from makes no difference - as long as it is correct, of course. What it actually connects to depends on the connection being used, the odbc entry your stage specifies.

Sorry, missed this one. Moved.

That's not an error, just an informational message. Can you send email from the command line on the DataStage server using sendmail?

I don't believe the Server ODBC stage supports that... the ODBC Connector and Enterprise stages do, however. What do you need to do before/after sql?

Vincent's blog doesn't mention a new "key change option" property but rather new functions to help simplify key change detection. And it's basically all laid out in the "Transformer Remembering" section.

I don't have the docs in front of me right now. You sort by your grouping keys and then number them appropriately in the Aggregator to show their sort order. Nothing else should be changed. You can tell it's working when rows "flow through" the stage as the job runs. If it continues to hol...

You need to revisit the parameter string that DSSendMail() needs, there's more to it than that. Take a look at the source for the DSSendMailTester routine, that should make what it needs it more clear.

So... is that good?

Your best solution to this would be to properly pre-sort the data before it comes to the Aggregator and then assert that sorted order there. It will then use minimal resources for the aggregation and greatly improve the overall performance.