DSXchange

Be more intuitive about your search criteria. An exact match search for "LONG data" returned 33 matches.

You can run it from wherever you like, provided that its parent directory is in your command search list (PATH environment variable) or that you specify the full pathname of the dsjob command itself. This is fundamental operating system stuff!

Totally wrong. The data viewer can display data from almost all sources (one exception is Lookup File Set).

"plz" is not an English word. Please strive for a professional standard of written English on DSXchange, which is used by a large number of people whose first language is not English.

Select "Functions" from the operand menu of the expression editor.

No, but you can for parallel jobs. The same job control language is used to execute/interrogate server, parallel and sequence jobs. But it must be created in a server job or a job sequence or a Batch, not in a parallel job.

The $CommandOutput activity variable will include the output of the command (that is, by default, stdout) with all line terminator characters converted to field mark characters.

A field mark character can be represented in a DataStage expression using the @FM system variable.

Why bother? You can check the row count in an after job subroutine and set the ErrorCode argument to a non-zero value to abort the job. You may like to have the after job subroutine delete the empty file first.

Use a UniVerse stage and perform a regular join in the WHERE clause of the SQL (on the Selection tab).

You may need to create VOC pointers to the hashed files for this to work.

We have a requirement that if this text file contains more than a million records then this file has to be split to multiple files with each not exceeding a count of 1 million. Resist stupid requirements. The same result can be had by specifying multiple readers per node in the Sequential File stag...

Welcome aboard.

You need to set the format property that indicates that the record format is fixed width. For each column you need to specify the display width (which is the number of characters in the record that represent that particular field).

The $CommandOutput activity variable will include the output of the command (that is, by default, stdout) with all line terminator characters converted to field mark characters.

A field mark character can be represented in a DataStage expression using the @FM system variable.

How did you (or someone else) create the Data Set? What stage type and pathname was used there? Try using "/" rather than "\" in the pathname. Does the pathname contain any space characters? If so try enclosing the pathname in double quote characters or using the "short DOS ...

This alert message is telling you that it has substituted 0x80 to a code point in the user-defined area (of Unicode). The reason it has done that is that, internally, DataStage uses 0x80 to represent NULL. Always has. Later, "they" (mainly Microsoft) elected to use 0x80 to represent the Eu...