DSXchange

You can run it from any directory if you use its full pathname ${DSHOME}/bin/dsjob or if you have ${DSHOME}/bin in your command directory search list (the PATH environment variable).

Potentially there is only one ${DSHOME}/bin/dsrpcd

You may optionally have the deadlock daemon ${DSHOME}/bin/dsdlockd and the job monitor application (a Java application that runs as JobMonApp and can be started using ${APT_ORCHHOME}/java/jobmoninit

Not enough information. Please describe (with examples) the expressions you are using to accomplish this result.

Is dummy a totally empty job?

How about you put in an after-job subroutine that calls ExecTCL to COUNT VOC (just for something to do)?

If you have a Date column is does NOT have a format: your Sequential File stage specifies the date format in the file and the import operator looks after it. If it's a Char or VarChar data type then the format is important. There are date conversion functions both for the Modify stage and for the Tr...

Source is VarChar while target is Date. Date does NOT have a format.

Therefore should suffice.

Can you see the dummy job post-import? If not, try the query It may be that there's a job called dummy in some other category, which should throw an error if you try to import the same job name into another category.

Very easily. And if you search the forum you will find that that question has been answered lots of times - sometimes with examples - already.

Chances are that your Lookup Failed rule is "Fail", which is the default. This causes your job to abort as soon as one lookup fails. Change the setting to one of the three other possible values.

What if you're in Status view and you try Clear Log ?

Can someone please try this in version 7.x? It might be something new in version 8.x.

I expect, from reading the rules, that the fact that the routine uses COMMON variable would preclude it. Why not try it and let us know?

RowProcCompareWithPreviousValue in a parallel Transformer? Doubt it. RowProcCompareWithPreviousValue is written in DataStage BASIC and relies on COMMON, which immediately invalidates it from use in a parallel job. See Chapter 2 of Parallel Job Developer's Guide for more information on the rules.

Define "not performing". The only permanently-running process is the dsrpcd (DataStage RPC daemon). It is a listener, so tends not to use much in the way of resources. Optionally you may have the job monitor (a Java application JobMonApp) running for parallel jobs, and the DataStage deadlock daemon ...

Can you connect if the Omit button is checked?

Are you using a legally licensed copy of DataStage server? This symptom can occur if the licence has expired.

"Phantom" is DataStage terminology for "background process".
All DataStage jobs run as phantom (background) processes.
The only way to avoid them is to take a vacation.
Or simply stop using DataStage and any other tool that uses background processes.