DSXchange

These things happen. Thanks for letting us know that it was resolved, and how it was resolved.

If you send it to Clif Oliver (moderator@oliver.com) he can post it in the Files area of datastage-users@oliver.com

This site is still resolving the mechanisms for such a posting area.

Can you expand on this; in particular how can data NOT be byte-aligned? Do you mean word-aligned?
What are the implications for NLS, where the number of bytes used to store any particular character may be one, two three or even four?

Such an API was developed in an earlier release of DataStage, but was withdrawn (about release 4.2 or 5.0). It is no longer possible.

Why do you want to do this? What's wrong with the DataStage Designer? How did you propose to manage the metadata?

You could switch to user-defined SQL, supplying your own TO_DATE function with appropriate date picture.

There's a timing issue. The link row counts are only updated into the status table every so often.
Any reason you can't use a stage variable (as noted by others) or the @OUTROWNUM system variable (for specific (=separate) up-to-date row counts on each output link)?

The DSAPI is documented in the Server Job Developer's Guide . Within this there is a list of error codes (constants all beginning with DSJE_). Most of the functions themselves are int, and return a negative integer in case of error. These values can also be seen in the online help for the DataStage ...

Basically you've identified the issue, that initial load and subsequent incremental loads are slightly different. Ignoring issues of how you want to manage slowly changing dimensions for the moment, the main difference is detecting the changed source records (including those that might be being chan...

That's true as far as it goes, but you can introduce a FFC into the mix. The point about Quality Stage is that it lets you do all this without touching down on disk, and in the PX environment, both of which are cool.

Apparently in version 7 you don't even need the fixed width format; the metadata from the DataStage job can inform Quality Stage about where to find the data. Not sure how you'd manage the redefines in this case, will get to play more with it one day! Vincent, contact Stewart in the Ascential office...

NO, in spite of what the BASIC manual says (p 1-5). Page x in the manual talks about the documentation conventions in the manual itself, not the syntax of the actual language. The only statements that can exend beyond the end-of-line are statements that include comma-delimited lists, such as COMMON,...

Look at your logic. 209779OR matches "...OR..." but does not match "...~COLOR...". Since you've joined these with AND, the test fails. To use the tilde (~) to reverse the sense of a pattern match, it must be the first character in the pattern. Also, I note there's a space in your second pattern, tha...

You didn't make it clear whether you're using osh or dsjob as your command line interface. Which is it? This will affect the answer.

Reset the job and see whether a message "from previous run" is logged; if so tell us what's in that message. I suspect you are seeing a timing issue; you're trying to feed your file into a sort utility before it's actually closed. (Remember that most I/O operations are buffered, so even a report in ...

In Australia it seems to have led to an increased awareness of what INTEGRITY can do (or maybe this is an artifact of the Ascential sales folks having something else to sell!). Whatever, the case, I am about to present the third INTEGRITY class in six weeks here! (This has not yet been updated to 7....