DSXchange

LASTERR simply reports the message generated by the database. You will need to direct your requirement to Larry's mob.

Try this design -----> Transformer -----> SeqFile -----> Have the Transformer write a single column the the SeqFile. Derivation is InLink.Col1 : svDelim : InLink.Col2 : svDelim : InLink.Col3 : svEOL : InLink.Col1 : svDelim : InLink.Col2 : svDelim : InLink.Col3 + svDelta : svEOL : InLink.Col1 : svDel...

As far as the database is concerned, DataStage is just another client application.

The same rules apply for all connected clients. If you would need UPDATE privilege to perform some task as an interactive user, then you will need it to perform the same tasks as a DataStage user.

Use stage variables in a Transformer stage. Because stage variables are executed in the order in which they appear in their grid, when one stage variable is being evaluated, later stage variables in the grid still hold their values from the previous row. svTest (InLink.Column <> svPrevValue And ...

A search of the forum would have revealed that a factless fact table records events for which there are no required measures.

Welcome aboard. :D

There's nothing "out of the (DataStage) box" but, if you have an ODBC driver that can access Essbase data, then you can use the ODBC Enterprise stage.

Search the forum in case someone's solved this already.

Direct all failures to the UtilityWarningToLog routine as well as any other processing. This will propagate warnings "up the chain of control".

Your top-level controller can then detect that a warning has occurred.

Ideally create your jobs so that no other warnings occur.

If there's one load per link all you have to do is call the routine multiple times with different link names. String sufficient routine activities together in a job sequence so you still have a single callable component. Implemented one of those as recently as last week.

You have almost certainly created a non-hashed, or directory file, either by creating a Type 19 or Type 1 file (unlikely) or by putting something other than DATA.30, OVER.30 and .Type30 in the hashed file directory.

A hashed file directory must only contain these three files.

Add this to your routine
This call automatically displays the argument values.

It's not in the parameter tab in a job; it's in the parameters grid of the job activity in the job sequence that controls the job where you can use expressions.

If it's Windows XP you must have an active connection even if it's just to a hub. This may or may not be the case with Server 2K or 2K3.

Note that the status of a job obtained from within that job will always be "running". In an after-job subroutine you can get the "interim status" (the status assuming that, apart from the subroutine, the job had finished).

That one could be indexing. DSR_WHEREUSED is checking to see whether the job participates in any dependencies, and is likely to use indexes to assist that search. Try reindexing the project at a quiet time.

Is any of the columns a non-numeric data type, that would require quotes around its value in the SET clause?