DSXchange

Does IBM know about this? Is it admitted officially or something? No idea, but seeing as how it has survived multiple version changes of the product I would consider it is a permanent part of the landscape. When I first ran into it, it was quite painful to figure out because it would mostly work. I...

That would imply a permissions or group issue. Did you follow the FAQ on configuring DataStage for multiple users?

Have you checked to see if that file exists in your project and has the proper permissions? That would be the first step.

XML Input stage?

Honestly, I have no idea never having tried it. Curious if you have and are struggling with 'bad parameter' errors or are we still in the hypothetical?

Just you.

You use the value of a stage variable in a routine by passing it to it as an argument. Or did you mean something else?

Obviously, you can't do this in a Transformer - at least not without some preprocessing or as the second of two passes through the data. First pass would be to determine which records should be 'rejected' and then a second to do the dirty deed. Unless there's some magical way in PX to do this all at...

I doubt there is a bug at work here. This is typically a user error, caused by not understanding all the rules around building user-defined sql lookups.

True. It really boils down to exactly what you mean by a 'year'.

D'oh... misread things. Jury will disregard all statements made by the witness.

Sure, stage variables doing normal 'group change detection' in a Transformer can handle this easily since the data is sorted properly. Keep track of the current and previous combination of User and Role, then only pass a record on the first time you see each particular combination.

If you had this technique working under 7.x and it no longer does under 8.x you need to contact your official Support provider. At the very least, you'll probably need the 'XML fixpack' Ernie has mentioned here more than once as apparently there is much XML bugginess in the first release of 8. At wo...

Compile? Yes. Run? No necessarily, as some parameter types are 'required' to have values before the job can be run. Never mind the fact that the job design may not work all that well without an actual value.

Regardless of your settings, your job must abort to rollback any uncommited records at the time of the abort.