DSXchange

I think I would go with 1 sort stage. Partition by A Sort by A,B,C,D,E LastRowInGroup(C) transformer function will give you key breaks on A,B,C LastRowInGroup(A) transformer function will give you key break on A Partition by A since you likely want all of the A rows passing through the same processi...

I haven't used the istool command line in the most recent versions, but is "create package" an option now? Or perhaps the OP meant "build package"? When using the IS Manager GUI, creating a package just puts the package definition into the XMETA repository. You don't get a packag...

I think you are a bit confused on how parameter sets and their values files are stored on the engine server. Your job design may be updating a file called param.txt, but I'll wager it is not the parameter set values file that you are updating. On the server go to your project folder. In it you shoul...

Totally unsupported hack... But the .pkg package file actually contains an XML document for the build manifest. In case you care to pursue using that build manifest... The .pkg file is simply a compressed archive file. You can rename it as a .zip and uncompress it. You'll see something like Manifest...

Sorry. My bad. Didn't notice the forum.

Mike

As UCDI says, you can't prevent someone with the DataStage Developer role from hacking your passwords. In a project where there is no DataStage Developer role allowed (i.e. you can't create and compile jobs) and you also prevent read access to the DSParams file on the server (i.e. you can't copy the...

A job can not modify its own parameters. They are set when the job begins executing. The usual technique is to use a separate job/routine/command to derive the required parameters and then pass them to the job that needs them. There should be lots of discussion about the various techniques. Since yo...

I'm not sure if this is documented or if it is just something I know from experience. The change capture stage requires unique keys on its inputs. This makes perfect sense if you think about the classic two file match logic that probably happens under the covers where a key match results in the next...

A routine activity must return 0 (reply=0) or it will trigger the exception handler.

I suggest calling your routine from a user variable.

A routine that returns anything besides zero requires a trigger to handle that non-zero reply.

Mike

I don't see any need for transformer looping. It looks to me like you can do everything with stage variables and output constraints.

Mike

If by CDC you mean the Change Capture stage, then be aware that it requires unique keys on both input links. You can see the result you describe when there are duplicate keys.

Mike

Bunch of nested if-then-else: If Client = "A" Then Client A logic Else If Client = "B" Then Client B logic Else If Client = "C" Then Client C logic ... Not at all flexible since you will have to change the job every time you add a client or a client needs a derivation c...

The transformer stage doesn't support dynamic derivation expressions. The design-time derivation expression is compiled into the executable code. If you have a reasonable number of clients that won't change often, you could handle the variable logic with a bunch of nested IF-THEN-ELSE. If you want m...

DSODB is way too valuable a resource to be locked away. All developers should have read access. Take it up with your admin folks.

Mike

Why reinvent a redundant wheel? Everything you need is already available in DSODB.

Mike