DSXchange

Use the Sample stage. Provide a job parameter for the skip and period properties. Set the number of records (per node) to 125000 (or, if you prefer, use a downstream Head stage). Generate the job parameter values in a controlling sequence using Rnd() functions.

Stay on the case with your official support provider.

Meanwhile, do you have the DataStage deadlock daemon running? It has a secondary task of cleaning up orphaned processes. (Note that processes waiting on database responses are not orphaned.)

Use a constraint something like Not(Num(Inlink.TheString))

Probably not. U (one of our posters) has not been involved in this thread.

Only by changing the data type from CHAR to VARCHAR. Every value in a CHAR(10) field - including the null field value - must have precisely ten characters.

The only way to guarantee unbroken sequence is to run the stage that generates them - I'd use a Column Generator stage - in sequential mode.

at -l command suggests that the Director was open in schedule view, and the user probably got impatient waiting for the result of this command. dsapi_slave is the agent process of the Director client connection, and therefore the parent process of the at command.

Of course this alert will be generated. You have an int (that is, int32) in source1 and you're specifying that it should be transferred to a smallint (that is, int16) in the target. It's got nothing at all to do with length. int32 is a four-byte (binary) integer, int16 only has two bytes. There are ...

Care to share the list of environment variables you use?

I believe that you'll need to add the -h server_name option to your command line.

Not at all. One flight to LA, one flight to PA.

Slowly Changing Dimension stage.

If it's always the same six fields the first thing I'd be doing is getting the provider of the file to be consistent. If you can't do that, you need to determine which column is which. If there are column headings this ought to be easy. In a Transformer stage you could use RCP to direct the correct ...

Ask yourself whether uniqueness is sufficient. If it is, gaps in the numbers are completely irrelevant.

Please explain what "didn't work" entails? Your first expression should have removed the terminator, but replaced it with a comma. What command are you executing?