Unlocking mistakenly blocked jobs in DataStage

When working with the IBM WebSphere DataStage client, client application crashes are quite common, causing the job lock to be blocked (we will call Job that way, avoiding the more Russian, but at the same time, more general term etl-procedure or data overflow procedure ). If the job is locked, it cannot be recompiled, since the DataStage client will report the impossibility of exclusive seizure of the job resources.

In this section, I will explain how you can, without restarting the DataStage server, unlock the Jobs.





To perform all the above operations, you need to start the DataStage Administrator, select the desired project in it and switch to command mode.





Then, you need to display a list of all blocked resources. To do this, enter the following command in the Command field:

')

LIST.READU







In the Command Output window that appears, we are interested in two columns: Inode and Userno. It is by these identifiers that you can unlock a job using command



UNLOCK INODE _INODE ALL



or



UNLOCK USER _USERNO ALL



Perhaps the execution of these commands you fail. In this case, you need to unlock commands that are locked for the current project by default (only once for each project is enough).

Like this:

SET.FILE UV VOC UV.VOC

COPY FROM UV.VOC TO VOC UNLOCK