Troubleshooting
Problem
When running dsjob from UNIX, the status of success or failure is returned correctly for some jobs, but long-running jobs return "Error 81002 waiting for job" even though the job has run successfully. Specifically, if the job runs longer than the timeout set in DataStage Administrator -> General tab -> Inactivity timeout, the 81002 error is returned; if the job completes before the timeout, the correct status is returned.
Resolving The Problem
There are two ways to resolve the problem.
You may increase the timeout in DataStage Administrator to accommodate the longest-running job. However, this will also increase the time that inactive client connections will remain on the system before being cleaned up.
Alternatively, to run the job you may create a script which invokes dsjob, and then uses a loop to query dsjob periodically to avoid the timeout. Refer to the help for the -jobinfo command for more information.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21422701