DSXchange

The '%%' notation must be something new for 8.x, don't recall it being around when I was doing a ton of XML creation, most of it using the trigger column mechanism. I assume it allows you to control the format / placement of the numbering? Needs to go reads me some documentations, it would seem. For...

You've got the concept down - when the trigger values changes, a new file will be created with an incremented number added. Ditch the Copy stage, let the XML Ouput stage handle the file writing.

kirankumarreddydesireddy wrote:Note : we are using Datastage server 7.5v on windows server and we donot have the Stored Procedure plugin as well.

You do. You may have chosen not to install it but you should certainly have it as an option.

So we're back where we started, with ODBC.

Yah, was going to chime in to say that both of your scenarios are equivalent in my mind. Whether it "sorts on a combination" of the two columns or "sorts on the first then the second" the end result should be the same. Now, string sorts can confuse people if that's what you are s...

Thanks, appreciated.

My one contribution to this thread is to change your subject from the rather terse and less than helpful "warning" to something more appropriate.

Try setting the transform type to be Target with a Generator as input, but with no output link.

They did.

Harini wrote:I am basically trying to check the dsjob commands to list the jobs currently running, and the jobs aborted etc.

And as Arnd noted, you need to use dsjob for that and you use it directly, there's no need to include the Director in any command line scenario.

Actually, you don't. The link MT posted shows that you can set an APT variable so that happens automatically.

First suggestion - patience. Pushing doesn't help get answers faster and can actually be counterproductive. Second, a 'transform' procedure means it has a source and a target; you call it, it does work and then passes out an answer. That can't happen if it is the only stage on the canvas. As a matte...

Welcome. The only real difference between running the job 'manually' and via a Job Activity stage in a Sequence job is in the latter you have the opportunity to mess up the handling of the Job Parameters. Not sure how that would cause left-outer-join issues but honest, that's really the only differe...

As noted, it doesn't know what "run" is but a careful examination of the valid options listed shows they all start with a dash so "-run".

I assumed they deleted the entry for the hashed file from the VOC file, not the entire VOC file as stated.

Almost went back and added the gory details on the 'how you should have done it' part to my post but I knew you'd appreciate the opportunity to handle that.

Unfortunately, those links don't work. I believe they may be from the original webinars rather than any archival copy of same. Maybe our dear Editor will see this post and comment on them.