DSXchange

Ascential's lawyers claimed to have copyright over any screen shot of any of their products. I attempted to determine where the boundaries are (e.g. a telnet window showing a ps report showing DataStage processes) but they've been coy (silent) when it comes to details. Yes, as far as I am aware, the...

That, dare I suggest, is an issue for the vendor. How about lodging an enhancement request? They, too, are new to USS, and doubtless are looking for ideas about improving things.

Persistent (on disk) Data Sets are intended to be used for those occasions where one parallel job prepares and stages data for a subsequent parallel job to use.

If no staging is required, persistent Data Sets are not required; the data can be passed to and fro between virtual (in memory) Data Sets.

Well, Monday has been and gone. I note that the OP has not checked back since the previous Saturday; I do hope no offence was caused and that an agreeable solution was found independently of DSXchange. Maybe the code will help someone else needing an indexed range-based vertical pivot.

A Data Set contains data in internal (binary) format. A persistent Data Set (one that is on disk) must have been created with a Data Set stage - there is no other way. There is one or more data files on each processing node; the control file (the one whose name ends in ".ds") describes the location ...

Have you tried this in Grid Style? That is, is it a bug in the OCI GUI, or something that is changed in the underlying mechanisms?

Nowhere did I claim that the Field() function is available in the Modify stage; I simply asserted that the Modify stage is more efficient (because it generates an osh operator directly, without the need to generate a called function as the Transformer stage does). String manipulation (other than dat...

Thousands of attributes maybe, but you should only need to do it once. Why not post an enhancement request?

Why are you reinventing the wheel? And why are you trying to use C constructs unnecessarily in DataStage BASIC? Convert(Char(13), " ", InLink.TheString) does what your routine does, but much more efficiently. If Char(13) were the initial value of a stage variable that remai...

Does it lose focus? Try minimizing all other windows (show desktop). Otherwise, try it on another PC - you may get benefit by reinstalling the client software if it works on the other PC.

You've changed the spelling or casing of a parameter name or removed that parameter, but not adjusted the Job Activity so that the new name is used or reference to the old name is removed. You must edit and fix.

Is the quote character in the Sybase data? Change the Format tab of your Sequential File stage so that " is not the quote character - maybe set the quote character to 000 (no quotes).

The DataStage job design (no coding required) has the form
followed by after-stage subroutine to rename/remove text files.

A constraint expression in the Transformer stage guarantees that only required rows are written into the target file.

Eight hex digits represents a four-byte quantity, such as Integer. Once you go beyond eight hex digits the next larger quantity, such as BigInt, must be inferred. 1234567890 contains ten digits.

Server jobs run uvsh executing the program DSD.RUN. Active stages can run in child processes, also running uvsh . For example, Transformer stages execute the program DSD.StageRun. So, yes, there will be multiple uvsh processes. Process IDs are allocated by the operating system. "User numbers", also ...