DSXchange

DataStage keeps a count of the rows sent to the file, which you can subsequently interrogate using DSGetLinkInfo() or DSGetLogEntry() functions. Or you can use DSExecute to invoke the UNIX command wc -l filename If you prefer to use a job sequence, you can use a Routine Activity for the former and a...

This means that you've specified a small data type (for example TinyInt or SmallInt or perhaps even Integer), or too small a precision for a Decimal or Numeric data type, and that a value too large to be read into such a data type has been encountered in the data being processed. The "solution" is t...

Have "them" dump the table definitions as COBOL file definition (FD) files or, if from DB2, as DCLGen files. In DataStage Manager, use Import > Table Definitions > COBOL File Definitions or Import > Table Definitions > DCL File Definitions For importing COBOL FDs you must correctly specify the colum...

The usual precautions about backing up databases apply. Make sure that they're not in use before starting the backup. You can detect which dynamic hashed files are in use via the command analyze.shm -d (the executable is in the bin directory in the DataStage Engine directory). smat (shared memory an...

The only 64-bit things that get created are the internal pointers within the hashed file. Therefore, it is possible to create them even on a 32-bit operating system. They break when they hit 2GB, not because of anything in DataStage, but because the operating system can't handle files of that size. ...

That behaviour depends on the transaction grouping properties of the ODBC stage, set on the Transaction tab on the Inputs link.

How are you determining that it's an exponential representation? This could simply be an artifact of the data browser. Or does it still occur when you send the data to a text file? Performing some arithmetic on it (adding zero is good) will guarantee that it's a number, but it should be a number int...

Probably not. As a general rule, transformations are performed in the Transformer stage (or in the BASIC Transformer stage).

Please describe exactly what you are trying to accomplish and where, and the exact error message generated and when (during compilation or at run time).

No. The PX engine does not set the kind of lock managed by the DataStage deadlock daemon.
As far as a utility for cleaning up defunct PX processes is concerned I do not know, someone else will need to answer that. I am not aware of one.

You could even constraint on the row number being equal to 1. Do this on the Selection tab.

Try performing simple arithmetic (adding zero is good) in a Transformer stage. DataStage should look after the metadata transition across the Transformer stage.
Beware, however, that any source number with more than eighteen significant digits will fail to load into the target.

Set the Display width in the columns grid to the actual width of the column. (You ought to have done this during the import of Sequential File metadata.)
Make sure, too, that the file format is marked as fixed-width rather than delimited.

My current sig has attracted a flood of private messages. Never thought there'd be so much interest in the Latin. Ah, well, here's the "full Wurlod". IVI is the first person perfect (past tense, completed action) of EO (I go); therefore IVI means "I have gone". ILLUC means "there", so ILLUC IVI mean...

You should periodically purge old entries from the &PH& folder.

The easiest way is a shell script run maybe once per week from cron. Use a command something like