DSXchange

I have a nice routine that does the same, for anyone who is interested. I usually use it in job sequences, but it has been used as a derivation.

You will find it on the DataStage Tools page of www.anotheritco.com .

Take a look at my Jobs and routines to integrate a parameter table into a sequence. You will find it on the DataStage Tools page of www.anotheritco.com .

Verify in your master sequence that the activity stage calling the sub sequence has a failed trigger and does NOT have an unconditional trigger. The default trigger colors of DataStage Designer do not give enough visual clues. I suggest changing the wraning trigger to yellow, and the otherwise trigg...

I find this type of task easier to do in a routine, then call that routine in a routine activity stage from a job sequence or a derivation in a stage variable in a server transform stage.

In the routine, build your command, then use the basic EXECUTE statement to run it.

Happy holidays... I have posted three new tools on the DataStage Tools page of www.anotheritco.com . One is a routine that one passes a job name, active stage name, and link name. The link's row count is returned. Another is a set of jobs and routines, with a sample sequence, that I use to get, set,...

Could this be a data type issue, such as moving a CHAR column to a VARCHAR column?

This is not too difficult. In a transform stage set up four stage variables: ThisRowKey, NewKey, PrevRowKey, and MoreData. The derivation for ThisRowKey should be the columns that uniquely identify the rows you want to group. The derivation for NewKey is If ThisRowKey <> PrevRowKey Then @TRUE Else @...

Review this page:

In general, you may want to have four triggers from each job activity stage: a failed, two warnings, and an otherwise. Also, each job activity stage should be paired with an "ANY" sequencer stage. All of the failed triggers from each job activity stage should be connect to an "ANY&quo...

If your SQL statements really have nothing to do with the row you are passing to the DRS stage, then do not pass any rows. Set the output constraint to @FALSE, and put you SQL statements on the after SQL tab.

You may be able to use the before and after SQL tabs in a Dynamic Relational stage. Create a simple job that is a transform stage liked to a DRS stage. In the transform stage, add a stage variable and set the constraint on the output link to @FALSE. In the DRS stage, you will need some table informa...

If you trust your load portion of ETL, you can compare yesterday's full load file with today's full load file to identify inserts, updates, and deletes.

Look at the unix "comm" command to compare your load files.

I have recently seen this happen if the user id the job is scheduled to run as does not have appropriate permissions to the project directory.

Do you think the order of the output links in the first transform stage is important? If so, I suggest you order your output links to ensure that the write to the hashed file occurs before the passing of the row from the first transform to the second.

After the job finishes, use a job sequence RoutineActivity stage with ExecDOS or ExecSH (or Execute Command stage) to run an operating system rename command. Using a UserVariableActivity stage, you can easily build the destination file name with dates and time available as DataStage macros. For exam...