DSXchange

Edit your breakpoint. Make it an expression such as (colname = "" Or IsNull(colname)). Hit Go; the job continues to execute until such a row occurs. THEN strap on the Sherlock Holmes gear! A zero length string has a known value, and is therefore not NULL, and therefore it will not be detected by the...

The question was about datasets in the PX environment. All you should need to do, provided that the machines are in the same cluster, is to define the hostname along with other definitions of each resource, in the PX configuration file associated with the job. Information on editing configuration fi...

There was once a known issue with dsjob only reporting the least significant byte of its true exit status. I don't know, however, when (or even if) this was fixed.

There's no documented limit to the length of a string constructed using an expression. However, the result must be able to fit in available memory.
There is a limit to the length of a string literal (constant), namely 255 bytes, not including the surrounding quote characters.

Welcome aboard! :D

Is this really a parallel job, or a server job? (There's an indicator on your Designer canvas of the job type.) The answer hinges on this question.

Since you have time to investigate ( ), you might like to discover how DataStage does it. Enable server side tracing (from Administrator client or from DS.TOOLS). Open a Director client. Perform a partial purge. Close the Director client. Disable server side tracing. Inspect the trace file (it's in ...

You want the constraint to pass rows if either of SV1 or SV2 is true. The simplest expression to accomplish this (because SV1 and SV2 only generate a true/false value) is SV1 Or SV2 You could, redundantly, expand this to (SV1 = @TRUE) Or (SV2 = @TRUE) which may provide a better sense...

... including the control records!

A better command to execute (though a little slower) is:

1. UNIX. (PX is scheduled for Windows, perhaps in 7.1?) 2. More. The secret of PX is its ability to share the load over multiple "resources" (= CPU + memory + work disk + scratch disk). These can be in an SMP (symmetric multi-processor) environment or in an MPP (massively parallel processing) enviro...

Have you read the on-line help and/or the manual entry for the Exception Handler? Essentially it's a "listener" that sits on your design canvas and can initiate an action, or series of actions, if an "exception" occurs. A child job aborting is an example of an exception. You might, for example, caus...

Have you searched the Forum? There are examples posted in a number of replies to other questions. Use the keywords "sequence" and "trigger" in your search criteria.

Welcome aboard! :D The ORABULK stage is quite old, and quite limited in the functionality and performance it offers. 10,00,000 rows is what DataStage practitioners would regard as a medium sized ETL task. Search this forum to find techniques to gain orders of magnitude more speed using a Sequential ...

Project-wide purge parameters are stored in the DSParams file. There is a section that looks like this: [AUTO-PURGE] PurgeEnabled=0 DaysOld=0 PrevRuns=0 A routine to update all jobs with these defaults should read these settings, then update the control record //PURGE.SETTINGS in the RT_LOGnnn file ...

Manuals for all plug-in stage types is on the CD, in a folder called Packages. In version 7 they are automatically installed in the client folder (Docs folder) if you choose to install the corresponding stage type. The only exception is the chargeable stage types, in which case the manual is deliver...

Step 1. Read the excellent book The Data Warehouse Lifecycle Toolkit by Ralph Kimball and others, so that you have a firm grasp of what is meant by Type 2 SCD. Step 2. Search this forum for ideas. The topic has been extensively discussed. Step 3. Enrol in DataStage Best Practices class (DS306), wher...