DSXchange

I need the same email (Job control routine) to handle both success and failure. Write it as a transform function and invoke it through a Routine activity. Should I get the Execute Activity name if it calls my job control routine to send out the email? No. Use separate Notification activities, or pr...

The back quotes around the date command is a technique only available in UNIX shell scripts. If you have a UNIX-on-Windows, such as Cygwin or MKS Toolkit, then you could use your proposed approach. Otherwise an after-job subroutine, as Ken suggests, is probably easiest. Though I would have generated...

Try using a Filter on table name or owner. Overflow can occur when there are too many tables in the database.

It can also occur (theoretically) when there are too many columns in a table, but I have never seen this actually happen.

What does your support provider have to say?

Best practice is to avoid aborting jobs from being locked by not having their log or monitor open while they are running. You should be able to log out processes using the Cleanup Resources tool in Director. Be extremely careful to ensure that you have identified the correct process, and log out any...

Client permissions do play a role when compiling job sequences, because some of the pre-compilation is to craft a temporary XML document on the client.

I suspect Zabeerulla is on UNIX and is paying the price for hijacking a thread about a problem on Windows.

If on UNIX then you do need to edit the three files indicated.

This is exactly the task (horizontal pivot) that the Pivot stage performs.

Try either of the following.

(1) Put the key value on the Selection tab inside single quotes.

(2) Replace the explicit key value with an appropriate clause (a WITH clause (without the WITH) for a Hashed File stage, a WHERE clause (without the WHERE) for a UV stage).

Write the data into a text file then use a hex editor (UltraEdit is good, and free for 45 days) to see exactly what you're trying to write. Post results here.

The NLS map associated with a DataStage hashed file should always be NONE, because the hashed file is "inside" DataStage; characters have already been mapped at the boundaries between external data and DataStage.

Or make your page wider.

Precisely HOW are you "moving from UNIX to Windows"? Did you re-compile jobs and routines after the migration? It may be that the executables contain references to the UNIX shared libraries (the files with a ".so" or ".sl" suffix to their names).

This is NOT a DataStage problem. It is purely a problem between the keyboard and the chair, where you do not understand that each executable has to be findable, either because you enter its full pathname or because you have its directory in your command search path (recorded in the PATH environment ...

There's always the "official" web site.

DataStage jobs execute the generated osh. You can find the shell scripts that organize all of this in the RT_SCnnn directory, where nnn is the job number from DS_JOBS. I also find it useful sometimes to inspect the generated osh (perhaps in conjunction with the job log) to diagnose those little irks...