DSXchange

Every background process ("phantom") that DataStage runs redirects its output to a subdirectory called &PH& in the project directory on the server. If &PH& contains thousands of files, job startup can be negatively impacted. The VCS reconfiguration might very well have cause the symp...

All DataStage user belong to one group, which gives them access to the DataStage software. There is a separate group for each project. Only the developers who need to access that project are members of that group. Any particular developer can belong to any combination of groups. Protect the DataStag...

Google will help, and there are probably Autosys analogues of DSXchange (that is, user fora) out there also.

Nah, you just thought it. We said it.

Make sure that $APT_ORCHHOME/lib precedes any Oracle libraries in the shared library search path.

What happens is entirely dependent upon the requirements of the downstream operator. If it's a regular (parallel) operator, with no requirement for partitioned input, Auto should use "Same". If there's no repartitioning icon on the link, you can be comfortable that this is the case. But if you want ...

Try renaming your links to meaningful names. There is always the hazard, when using the default names (DSLink1, DSLink2, and so on) that components copy/pasted or imported will cause name clashes.

Did you import the job design as well as the job executables?

I infer from your note that the error occurs when dragging a link from the Pivot stage to the downstream Oracle Enterprise stage. Is this correct? I was not able to reproduce this problem using version 7.5.1A. My guess is that you already have an output link from the Pivot stage (look carefully for ...

I infer from your note that the error occurs when dragging a link from the Pivot stage to the downstream Oracle Enterprise stage. Is this correct?

Set up the job parameters (in the jobs) that use environment variables to have the special value $PROJDEF as their default values.

SELECT @ID, "KEY", DTC, CREATOR, PREVDTD, PREVDELETOR, EVAL "FIELD(DTM,@VM,COUNT(DTM,@VM)+1,1)" AS DTMOD FMT '19T', EVAL "FIELD(MODIFIER,@VM,COUNT(MODIFIER,@VM)+1,1)" AS MODBY FMT '30T' FROM DS_AUDIT WHERE ("KEY" = '2\' || ...

Worse. Link partitioner uses inter process communication (IPC) which introduces an additional possible point of failure.

You have an ongoing thread on this topic, in which you will find an answer. The current thread is redundant.

So with 8 dual node cpus, there are 16 processes available? Will the server dynamically adjust the number of processes when the second job is submitted or will test1 keep all the processes until it is finished? You're operating on an incorrect assumption. The number of processes available is not go...