DSXchange

Depends. From what I recall, an "exact" search will search the entire database with the downside of needing an exact text match. The other two options (any or all terms) are for some reason time limited and only look backwards a handful of months. Not sure why but it's been that way for qu...

What have you tried so far? As Ernie notes, there is some advice in the linked thread that I split you from - curious if you have attempted anything from there yet.

In other words, let's get some specifics around your version of this error - what you are seeing, what you've tried so far, etc etc.

Thanks. Probably never got all that creative with the tool back in those days as we were all stone green newbies then and hadn't learned any bad habits. Yet. :wink: I do seem to recall people posting 'hacks' here, some interesting way to get that (or some version of that) functionality back. Highly ...

For sendmail, in addition to the "To:" and "From:" lines it also supports "Cc:" and "Bcc:" so those should be pretty simple to work in to the process.

It's not about using the actual routine but instead taking the code and adapting it to your specifications under a new name. You're also not stuck with using sendmail but you can use anything your company supports. And then it's just a matter of getting the BCC syntax for the call and folding that i...

Even if that did work (the file would already be open you were writing to) you now have this query information as data flowing through the job rather than accessible as a global job parameter. Quite a difference in scope between the two but could perhaps be an option depending on what exactly "...

You'd have to write your own mail routine so that you have full access / control. It's not all that hard if you have any experience working with DataStage routines. For example, check out the DSSendMailTester routine source code, should give you a good starting point.

Are you sure you need this only for certain warnings? I seem to recall an option in most Oracle stages to 'Treat warnings as Fatal', hence the question.

Apart from using API functions in after job subroutine, can we do something within the datastage job itself? Perhaps. However, I would strongly discourage any such approach. I'm not a big fan of extra bits you'd have to incorporate into every job, parts that would on failure jeopardize the load / p...

dsgguy wrote:Can we have a job parameter as an output parameter?

For completeness - as answered elsewhere, no.

As noted, those are your jobs. If you feel there are 'too many', run fewer jobs at the same time. That or get a bigger boat.

Interesting... I started with the 3.1 version and don't recall that functionality being part of the puzzle but I trust Arnd.

The simplest way to avoid any remote calls is a script that runs on the server... is that not an option for you?

... and this is typically something done as a separate step outside of the job after it completes, not part of the job itself.

And? Your questions are general access ones, you don't have to bring DataStage into them at all so don't worry about that point. I have a small Documentum team here as well, worst case I may be able to ping them and see if they have any words of wisdom if you don't get any traction with your group.