DSXchange

I have a blog post DataStage Parallel routines made really easy. You might find it helpful.

You can use Nested XPath Expression in XML stage.

Modular design! When loading job, ie. loading to MQ / Webservice job fails, check for reason (If required look up with known connection error) in the job sequence and play it in a loop. Set or parameterize loop tries.

You are invited to consider this also: Using C/C++ API (DataStage development kit) build a self-contained program to change the Environment variables.

Search for "DSParams" or "Environment vairable" to know more about this. Not sure which input directory you are talking about.

You can change Environmental variable value in many ways: :arrow: DataStage Administrator (Where? : Change the value column) :arrow: Using C/C++ API (the DataStage development kit) you can build a self-contained program that can run anywhere on your system, provided that it can connect to a DataStag...

Depends on your exact requirement. If (Left(InputLink.InputColumn,1) > CHAR(64) and Left(InputLink.InputColumn,1) < CHAR(91)) then 'Y' else 'N' Ex: "1test" will give you 'N' Ex: "test" will give you 'N' Ex: "Test" will give you 'Y' or If (Left(InputLink.InputColumn,1) =...

Fair enough ! For those whose find the above routine is suitable, use it, if someone believe it needs improvement, please create and use.

ray.wurlod wrote: If I believe an SDK routine is suitable for my purposes, I use it; if I believe it needs improvement, I create and use ...

Have you tested the same with "KeyMgtGetNextValue" routine available under Routines/sdk directory? "KeyMgtReset" routine falls into the same category, not for concurrent update as "KeyMgtGetNextValueConcurrent" routine.

Rightly said. As I have noted earlier I just changed one of the SDK key management routines for what OP asked. Have tested it and works fine.

Change one of the SDK key management routines available under Routines and use this in your sequence.

Thanks for letting know that Now if one check the SDK key management routines available under Routines/sdk directory you can see how it proceeds there.

FUNCTION KeyMgtReset(Arg1,Arg2) Input: Arg1 - Name of the sequence Input: Arg2 - Value to be set Description: If this routine is called for the first time in a new environment and if the named sequence (Arg1) does not exist, this routine will create a new one and set the initial value as Arg2. If n...

Change one of the SDK key management routines available under Routines and use this in your sequence.

Modified and tested. Here is a C++ / Parallel routine which removes/replaces all the non printable chars with the given input. Developed and tested on Linux. Function : pxRemoveNPChars * Input : char * InStrToRemove - IN - the input string Input : char * ReplaceChar - IN - the char to replace OR '' ...

If " Hide all executing and executed instances of jobs from director list" is what you want then I think as noted by Ray and Craig filtering by job name will be your only option. Except the Base Jobs,all other instances of these jobs should not list in the Director Log.That's what my quest...