DSXchange

UtilityWarningToLog is a function that you can call to write a Warning message to the log. DataStage does not call this function, someone has coded this into the job or (based on the message) a 'sub-routine' that one of the jobs or the Sequencer itself is calling. The USER INFO part of the message ...

I specifically said 'steps' so that it would apply to either of the scenarios you mentioned - two jobs or turning your job into two 'sections'.

As Keith mentioned, draining the table to a flat file first (even in the same job) would avoid your locking problem on the target.

Assuming a job structure as you've noted, regardless of the Source database and target, the target process starts before the sourcing stage completes. A row from the source is pulled from the result set and processed through to the target before the next row is pulled from the result set and process...

There is no 'decrypting algorithm' in DataStage. You could, however, write one as part of a custom routine... as long as you know how the field was encrypted.

If you really want to handle things like this, you could write a custom routine that included a call to DSSendMail... that or a straight DSExecute of sendmail or a script that wrappers sendmail. I'd probably stick with the Stage Variable idea, simply to control how often this routine would get calle...

You are starting to walk down the path to the Dark Side. This gets into the 'hacking' of the structures used to store this information and writing magic utilities to dig information like this out. Others have posted or have available routines to do things like this. We've had some success simply exp...

You would need to make it a Job Parameter and then reference that parameter, bounded by pound signs (#), in the DB stage.

Do something like you are doing in an outer job control 'wrapper' or script to set the parameter value accordingly.

Yes, there is a link between metadata and the jobs that use it, but it can be a little... fragile. What you can try is navigate to the metadata via the Manager and then click on the beaker, which is the Usage Analysis tool. If the links are still intact, it will show you every object that references...

Not sure how many people here have experience with sourcing from Notes or with that particular ODBC driver. I don't. We had Notes push data directly to Oracle staging tables rather than trying to go get it ourselves when I had to do this in a past life. You may have better luck contacting Ascential ...

Welcome. :D Out of curiousity, what happens when you run the job? Do you get the same error? I've seen times where you could run but not view, due to some of the 'quirks' in the View Data code, hence the question... Also, might help people to know what version of Notes you are accessing, from what I...

If you are going to take that approach, you would be much better off using a Sequence object instead. Simple to implement and it avoids any concurrency issues.

If you check the online help for Oconv and then click on the link to the 'D' (Date) conversion codes, you'll find there is a 'J' formatting option which returns the Julian Day of the year - 1 thru 366.

It also shows examples of its use.

If you've created them using the 'pathed' option, then yes, backing up (in some form) the entire contents of their folder is sufficient.

ShaneMuir wrote:3. Unix OS

Actually, I meant which specific O/S... HP/UX? It seems to get more than its fair share of mutex errors.

I set the timeout higher but still get the multiple mutex errors

What value do you currently have it set to?

What kinds of things are you doing in your job, what stages are you using? IPC? Do you have Row Buffering enabled? What operating system? When you release this job, do you migrate it to another (production) server or is it running on the same server as the unreleased job? Should I set the timeout pe...