Hi All,
When we are compiling a job, it is a giving an error that job may be being monitored. And we are unable to see the lock on this job using DS.TOOLS in administrator.And it is not allowing us to rename.Please pass your inputs if you already handled this error.
Thanks in advance
Koteswara Rao Daliparthi
Compile Error:Job May be being monitored
Moderators: chulett, rschirm, roy
Hi Koti,
There are two approaches you can follow to ovecome this problem:
1.
Unlock all the resources occupied by the user, who has locked that particular job. Hope you are aware of using LIST.READU EVERY, UNLOCK USER USER# INODE INODE# ALL, etc commands.
2.
Make a copy of that job, using "Save As" option. Delete the old job. Rename the new job same as old job. Compile it.
Cheers!
- Nitin
There are two approaches you can follow to ovecome this problem:
1.
Unlock all the resources occupied by the user, who has locked that particular job. Hope you are aware of using LIST.READU EVERY, UNLOCK USER USER# INODE INODE# ALL, etc commands.
2.
Make a copy of that job, using "Save As" option. Delete the old job. Rename the new job same as old job. Compile it.
Cheers!
- Nitin
Koti9,
The fact that you cannot delete the job means that there are still locks open on it; even if you haven't located the appropriate lock. If you stop the DS engine and after the restart still cannot delete the job then you might have some sort of corruption in the project - in which case the DS.TOOLS options to check files & re-index might help.
The fact that you cannot delete the job means that there are still locks open on it; even if you haven't located the appropriate lock. If you stop the DS engine and after the restart still cannot delete the job then you might have some sort of corruption in the project - in which case the DS.TOOLS options to check files & re-index might help.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Koti,
Here are the steps, which you can follow to release locks..
1. Login as dsadm. Test into your UNIX machine where DataStage Server is installed.
2. cd into DataStage home directory. You can enter "cat /.dshome" to find the DataStage home directory.
3. Enter ". ./dsenv" (i.e. .space./dsenv) to source the dsenv file.
4. Enter "bin/uvsh". It will bring you into UV Administration menu. Hit ESC key to get out of the menu and it bring you to ">" TCL prompt.
5. At TCL prompt, you can enter "LOGTO projectname" to log into the project account. The project name is case sensitive.
6. To find out what the job description number, enter "LIST DS_JOBS
jobname".
7. Enter "LIST.READU EVERY" at TCL. Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number.
8. Write down the inode number and user number for the lock that is not a valid lock.
9. Enter "LOGTO UV" to log into UV account. The UNLOCK command lives in UV account.
10. Enter "UNLOCK INODE inode# USER user# ALL". This will unlock the lock hold on this file (inode#) and hold by this user (user#) for file locks, group locks and record locks. If you need to see all the locks again, enter "LIST.READU EVERY".
OR Enter "UNLOCK USER user# ALL"
11. Type Q to logout of Universe
This should probably help you out.
- Nitin
Here are the steps, which you can follow to release locks..
1. Login as dsadm. Test into your UNIX machine where DataStage Server is installed.
2. cd into DataStage home directory. You can enter "cat /.dshome" to find the DataStage home directory.
3. Enter ". ./dsenv" (i.e. .space./dsenv) to source the dsenv file.
4. Enter "bin/uvsh". It will bring you into UV Administration menu. Hit ESC key to get out of the menu and it bring you to ">" TCL prompt.
5. At TCL prompt, you can enter "LOGTO projectname" to log into the project account. The project name is case sensitive.
6. To find out what the job description number, enter "LIST DS_JOBS
jobname".
7. Enter "LIST.READU EVERY" at TCL. Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number.
8. Write down the inode number and user number for the lock that is not a valid lock.
9. Enter "LOGTO UV" to log into UV account. The UNLOCK command lives in UV account.
10. Enter "UNLOCK INODE inode# USER user# ALL". This will unlock the lock hold on this file (inode#) and hold by this user (user#) for file locks, group locks and record locks. If you need to see all the locks again, enter "LIST.READU EVERY".
OR Enter "UNLOCK USER user# ALL"
11. Type Q to logout of Universe
This should probably help you out.
- Nitin