DSXchange

Generate a column containing the column names (as constants) upstream of the Pivot stage.

That understanding is basically correct.

I think that mcs_murali wanted the exact function to use, not the syntax of a Specification property. Further, I am fairly sure it was wanted a month ago.

That throws too much away! Try

HORRIBLY slow, in fact. Even 2GB physical memory is a lower limit - much better results can be had with 3GB or more. (And, yes, that's just for the client.)

There isn't one. You have to write your own. Get the logic from MONTH.LAST Transform from the server job side of the fence.

Explicit functions do not exist for conversions that can be done implicitly. Integer to Decimal is one conversion that can be done implicitly. Therefore DecimalToString() will handle an integer argument quite happily (provided the precision is sufficiently large).

Tip: Using UtilityRunJob() in a parallel job presupposes the use of a BASIC Transformer stage.

You can return anything you want, perhaps by making use of the invoked job's user status area. Research the DSSetUserStatus() and DSGetJobInfo() functions. Or you could write your own version of UtilityRunJob.

I'm not aware of any more direct method, which is why I documented the scriptbeginning from DSPackagePath. Gee, that was so long ago! I'd forgotten it! Must get around to changing the accreditation notice.

Ultimately in a file called msg.text in the DataStage engine directory. However, different databases have different default formats.

Code 99 means "unknown error" or "other error". It follows that neither I nor anyone else can tell you "exactly what created the problem". Have you asked your official support provider? Limits (various) are usually more exactly reported.

Off you go, then.

Incidentally, this site has a separate forum for DataStage TX (now once again renamed to WebSphere Transfomation Extender, with no mention of DataStage at all).

Copy stage does allow re-naming. RCP will ALSO propagate the original name. Probably not what you want.

Depends on your source. If it's a sequential file (in which you must read past every byte to get to the next) then you have to read them all. In this case you can use the column property Drop On Input. Otherwise, select only those columns that you actually need from the source table.