DataStage server job locked after Designer crashes

[rdy]

A couple of times, DataStage designer has frozen ("not responding") when viewing large sequential files. (Local client is Windows NT 4.0).

When Designer is restarted, we have been unable to edit the job that was being edited when the error occurred. The only way we have found to release the job is to stop and start the datastage engine.

Is there another way to release a job without restarting the engine?

[chulett]

This is a common problem and there are quite a number of posts on this particular subject here. If you search for something like "releasing locks" you should turn them up.

[ogmios]

Execute on UNIX:

Code: Select all

list_readu

And look for the entry where your jobname appears in the last column.
Then login to Director with dsadm and use Job->Cleanup Resources. "Show All". Then find the corresponding job entry (out of my head using the last number right before your jobname in list_readu), first unlock the locks in the bottom half of the screen and then log them off.

Ogmios

[kduke]

If you login to the Admin and TCL do UNLOCK ALL. This is the easiest way.

You need to be dsadm.