job being monitored eror

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
knowledge
Participant
Posts: 101
Joined: Mon Oct 17, 2005 8:14 am

job being monitored eror

Post by knowledge »

Hi ,

Now recently whenever I am tying to compile a job , I am often getting the message , job is being monitored I am enable to compile the job ,

pl suggest , as we have critical dead line , I am stuck in between

thnks
kcbland
Participant
Posts: 5208
Joined: Wed Jan 15, 2003 8:56 am
Location: Lutz, FL
Contact:

Post by kcbland »

Someone somewhere has a Director Monitor open on that job. Start by exiting all Director sessions on your PC and try again. If that doesn't work, starting asking everyone to get out and try again. If every single person is out, then recycle the DS services as something is obviously wrong internally with the locking mechanisms.
Kenneth Bland

Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Is the message IS being monitored, or MAY BE being monitored? The second of these can occur if any kind of lock on the job exists in the Repository - if the job is open in Monitor, Designer or Monitor, for example.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

Hi all,

I am having this error when i am trying to delete the job from the repository.
Cannot get exclusive access to the executable file for job
Also if i am trying to compile it its giving following error
Job may be being monitored
Thanks in advance
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Even having the job log open in Director can lead to "may be being monitored".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

After closing the job logs still i am having the same problem.Also i checked for any locks but none are there.

Thanks
sam
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

HOW did you "check for locks"?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

From the cleanup resources in the director.

Thanks
sam
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That doesn't show locks held by defunct processes. You need to get to the Administrator client window or to the server and issue a LIST.READU command. If you can get to a UNIX prompt, even better is to issue the command from UNIX, so that you can pipe the output through grep and just search for that job name.

Code: Select all

. $DSHOME/dsenv
$DSHOME/bin/list_readu | grep jobname
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Nageshsunkoji
Participant
Posts: 222
Joined: Tue Aug 30, 2005 2:07 am
Location: pune
Contact:

Post by Nageshsunkoji »

Hi All,

Even i faced the same problem with my jobs sometime back. The main reason behind this is your job is running internally in the server.This is due to you forcefully close your job ( by using alt+ctrl+del in windows) or some other reason. The solution for this is kill your job by using Kill command ( know the PID first) in Unix or you can use Datastage director to Logout from this job by using Cleanup resources option in Tool in DS Director or you can come out of this problem by restarting your server.

Regards
Nagesh.
NageshSunkoji

If you know anything SHARE it.............
If you Don't know anything LEARN it...............
MTA
Participant
Posts: 37
Joined: Thu Feb 02, 2006 2:25 pm

Post by MTA »

You need to run UNLOCK from UVSH utility by logging onto the project from command line. If this does not work you may have to reboot the server
M.T.Anwer
The day the child realizes that all adults are imperfect he becomes an adolescent;
the day he forgives them, he becomes an adult; the day he forgives himself, he becomes wise.
-Aiden Nowlan
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

Hi all,

It is solved!!

Just logged out of each process from the Director>>Cleanup Resources.

Thanks all for sharing your knowledge
sam
Post Reply