DSXchange

Have you looked up the error code -12154 in the Oracle codes and messages manual? This is a useful resource, as it contains not only the meaning of the code but also (often) possible remedial action. The dsenv file sets environment variables for all DataStage processes, including executable jobs and...

The "bleedingly obvious" question; if the row doesn't exist, why are you trying to update it? Assuming the target table has a primary key, you can pre-load a hashed file with the key values, and use this as a means to determine whether the row exists or not and, thereby, handle updates and inserts o...

... none of which is either relevant nor meaningful for 5.x server jobs! I just tried to answer the question at the OP's release level.

There is no DataStage limit to the number of instances that may be started. However, there is almost certainly a resource limitation. You shouldn't really try to start more than two instances per CPU. DataStage jobs are - intentionally - resource hogs. Do you REALLY need that many instances simultan...

DSParams is a text file in a project directory on a DataStage server machine. The DSParams file serves primarily to store the lists of intrinsic functions and system variables that the syntax checker in the expression editor for server jobs (and the BASIC Transformer in version 7.x parallel jobs) "k...

The other thing to check, of course, is that your method of summing and grouping in the sequential file is correct!
And are your numbers large enough that you might be getting overflow when summing them? Have to ask, to eliminate possibilities.

I used to make it a habit to grab all the plug-in PDFs and install them on the client with the other DataStage manuals (or on a shared drive, depending on the installation).
Version 7.x now does that for me.

I am - among other things - a qualified psychologist, and can appreciate what Ken has just had to say. But there are a couple of things that give me the irrits on these forums (and Oliver's and others). One is posters who provide no information about where they are. Why are they hiding? Another is t...

I'd vote for a separate forum for ProfileStage. It has its own set of techniques and its own set of issues. The only really difficulty, then - and it's a difficulty for Ascential too - is where to post questions about Quality Manager (oops, Audit Stage), which overlaps Profile Stage and Quality Stag...

If you prefer not to do that, it's OK, enrol on the Ascential classes, particularly "DataStage Essentials", where they give actual examples of shared containers and job sequences. This training is available in an instructor-led environment, or via the web. Contact Ascential Software for further info...

Just to add my $0.02 worth, both the BASIC function DSRunJob and the default operation of dsjob are "asynchronous" operations. All they do is submit a request to the server for job execution. Then they're done. You have to make your own arrangements for detection job completion, and any other job ch...

Exactly what do you mean by "in real time"? Are you referring to the "RTI" (real-time integration) capability and, if so, do you have the RTI components installed and licensed? If not, what exactly do you mean? A shared container is simply a way of encapsulating a subset of a job design, in a way th...

Is any message being generated either on the client or the server?
Also, you should not need to be doing Cleanup Resources "many" times - there may be something wrong with the way that the upgrade was installed. Cleanup Resources really ought to be a tool of last resort.

It's OK to do this (once in one job) even though you're using multiple instances of the server job. This is because the separate instances run as separate processes, so that the area of memory declared as COMMON in one does not overlap with the area of memory declared as COMMON in the other.

The least technical fix is re-boot the Solaris machine.
This will guarantee that all ports are cleared.