DSXchange

When you try to execute the jobs, what are the job error messages?

Paste the error messages. We don't know if your jobstreams require prep work in order to run, such as persistent hash files located within the project directory, plugins to be installed, etc...

You're doing something unsupported, using knowledge of the undocumented APIs. You have no control over what happens inside. There's no global solution, once inside that subroutine it can do anything it wants. Would you consider writing your own subroutine to clear the log? You're already doing thing...

Use all error trapping available on all commands. Failure to open a file should not allow processing to continue, letting a write to the file cause a failure. In fact, write failures can be trapped as well. Verify all of the DS BASIC functions/statements against the manual. There's only a handful of...

You can't "move" a project. You can create a new project in a different location and import your jobs there, but you can't physically issue a "mv /fromhere/myproject /tothere/project. It screws up internal pointers inside the database. Don't ever do this again. To fix your problem, consider moving t...

In unix, every command executed is visible in the process table ("ps -ef"), so if your command has exposed passwords on the command line, enterprising individuals can see it.

You get 1 query only.

An exception output link during transformation which sends rows to a file documenting the issues with the data instead of on to the target.

Please search the forum.

Run glance or prstat or top to monitor your server load. You're exceeding the systems ability to quickly switch between tasks, and DataStage job control blew up. Search the forum, this is a common issue, there are some potential tweaks in the uvconfig file that can help out.

1. As long as passwords aren't setup as encrypted, but strings, a mass text replace in the dsx should do the trick. You must recompile everything. 2. Parameter default values are okay to change, but you must recompile everything for those defaults to be effective. Just fix the problem once and for a...

chulett wrote:{Wipes the sweat back on forehead}

Spent enough time on this one, no use trying to figure out what was wrong with the design.

us1aslam1us wrote:But I am just curious to know why suggestion#2 didn't work out?

You were trying to do something the more difficult way, and therefore had to more carefully design the job. I suspect something was not quite right. The solution used now is very easy to understand and not so complicated.

{Wipes the sweat off the forehead}

Glad that one is fixed. :D

This is getting frustrating because we're talking in circles. The purpose of a multi-row lookup is: 1. Produce a product, meaning multiply your primary input stream by the referenced rows. Your initial request has ALWAYS been to produce more output than input. 2. Do a multiple choice selection from ...