DSXchange

I don't think what Craig said is true. Changes to auto-purge settings still only affect subsequently-created jobs. Search DSXchange for examples of routines. Another approach would be to enable tracing then perform the required purge manually. The trace file will show all the routines that get called.

Putting what Craig said another way, upgrading to the new version will update all your jobs. As will importing into a higher version project.

Nor am I aware of any, despite pressure from my customers.

Data Rules stage employs functionality from the former AuditStage, now part of Information Analyzer. I suspect, therefore, that to use the Data Rules stage in DataStage you also need an Information Analyzer licence. Rule definitions created in one tool can be used in the other.

dubuku_01 wrote:... ray's reply is premium content.

Why not get yourself a premium membership? It's not expensive, less than 30c (Rs12) per day, and helps to support the continued existence of DSXchange.

Another approach is to use the Data Rules stage, which includes a genuine matches_regex rule.

Why do you "have to do the operation in transformer stage", particularly since you already have the queries apparently working in Microsoft SQL Server? One way would be to create constraint expressions using Index() or substring functions. To address your specific requirements: Index(InLin...

Short answer: no.

Probably the fastest would be a parallel job that reads the Data Set and uses a Transformer stage to effect the search. You can run this with more nodes than exist in the Data Set.

Sort (by all columns) then Remove Duplicates (first) grouping on all columns.

RT_BPxxx contains any BASIC programs from job number xxx, particularly from server Transformer stages, and BASIC Transformer stages from parallel jobs. RT_BPxxx.O contains the equivalent compiled code from whatever is in RT_BPxxx. RT_QSxxx as you correctly discern is used to contain QualityStage com...

Only if you know how "low values" is defined/implemented. For example it will be different for different data types.

It appears that this problem has been thrown by the Logging Agent. I would strongly counsel you to involve your official support provider. APT_PERFORMANCE_DATA can, like any other environment variable definable for the project, be added to individual jobs as a job parameter. But I don't really belie...

It can be done using routines, but you ruled that out in the original question.

Make absolutely sure that your date picture matches the format of your data. Completely.

Do other Transformer stages compile OK? I've seen that message indicate that a compiler licence has expired.