DSXchange

Tip

Just in case you can't figure it out, you clear a sort assertion in the Aggregator stage by setting the sort order to 0. (You can't just delete it.)

Yes, you lie to DataStage about which columns are "key" (arguably you ARE using them as secondary keys).
For performance, it is valuable to create an index on each such column.

Metadata rule: is the smiley with sunglasses.
So your got converted by the metadata rule!

If you'd like your own name, like sp_help or describe , all you need to do is load up the actual command (use LIST.DICT rather than LIST DICT ) in the Administrator client's command window, then save it using your preferred name. LIST.DICT has the ability to prompt for the hashed file name if it doe...

I always advocate never allowing jobs to abort. That way the controlling job can remain in control. If there are problems these can be recorded, in the job log or elsewhere, and detected by the controlling job. Because the controlling job is still in control, it can take any required remedial action...

You need to know the key value for the row in the hashed file, and the field number in which the desired value resides. Let me take a shortcut by assigning these directly to variables. In the code example I'm going to read a variable from a hashed file and load that value into a parameter in an atta...

Yes, there seems to be an inordinate penalty for using a quote. Walter?

Yes, you can do this legally. You need to specify that the A.CASE_KEY and FD_RATES.TR_CD as "key" columns (even if this is a lie) so that you can supply reference key expressions to them. In turn, this means that A.CASE_KEY must appear somehow in the outer query. Why not load the inner query into a ...

You're not doing anything "wrong", per se. It's just that what you're looking at with the text editor is the file header, which contains management information, not data. The data starts later in the hashed file (exactly how much later depends on its tuning parameters). @ID is the default name for t...

In this case, explore the Iconv() function in on-line help, and find out how to handle signed numbers with trailing sign. Use this function to convert the data to "conventional" format. Hint: it's part of the "MD" specification; find the MD topic in on-line help (or in the DataStage BASIC manual).

The vital piece is to make sure that you've got everything you need. If you've been diligent about recording dependencies (this is why the Dependencies tab is there), then Version Control can pick up the dependent objects. There may be certain things external to DataStage that you also need to promo...

The real question is what do you think would be a reasonable amount of time, given the complexity of the task that MetaStage is required to perform?

How fast do the competitive products run? Oh, silly me, it's patented technology - there ARE no competitive products!

Line 186 does not refer to the data. It refers to the subroutine called JOB.1623522433.DT.1334767455.TRANS1 (which you can view in the RT_BPnnn directory, where nnn is the job number reported in the error message). This message usually arises from attempting to perform an arithmetic function or oper...

... and you can retro-fit the apostrophe in "can't".

(Sorry, couldn't resist. The Apostrophe Kid)

You wouldn't have a "create table" possibility if doing a SELECT. I suspect it's how the Sybase parser is treating a query with an unqualified table name, either checking to see whether it's in the temporary tables space, or preparing the SQL "in case" it's of the form SELECT ... to temptable; Find ...