regarding qsrtmngr

[ray.wurlod]

Possibly that qsrtmngr is not running. This is the component that DataStage uses as a special case of a "real time interface" to invoke QualityStage jobs via the QualityStage plug-in.

[ralleo]

Do a ps -ef|grep qs on command line, to find out if QualityStage is running.
you should see qsrtmngr - which provides the interfaces between DataStage and QualityStage and
qsserv which executes QualityStage Jobs



Quote:
-----------------------------------------------------------------------------------
Throw a lucky man in the sea and he would come out with a fish in his mouth

[boxtoby]

qsrtmngr can be tricky to get right!

In addition to the checks advised earlier can I suggest the following:

Make sure the qsjob has been staged and runs from qs itself

In the qs plug-in stage in the job:

qsrtmngr default port is 6010
Make sure all references to qs are absolutely correct, they are also case sensitive

Are you using a mngr.cfg file? If so, make sure it's entries such as the port are aligned with the job.

You can also use the trace option in the qsrtmngr or mngr.cfg file to give you more info if you haven't already.

Hope this helps.

Bob.

[ralleo]

In addition to the above, are you running QualityStage as a stand alone or from within DataStage.

If from within DataStage, check whether you have registered the plug-in, i.e. Go to DataStage Manager ->Tools -> Register PlugIn.

Also as Bob said, what have you got in your mngr.cfg file. This is normally in the QualityStage directory showing start status, port number and
tracelevel


--------------------------------------------------------------------------------------
Throw a lucky person into the sea and he would come out with a fish in his mouth.

Ritchie