Hi,

I see few of the jobs in forcast report with schedule as "File*".

All of these are for past dates. How can I clean this up.

----

Also sometimes few semaphor file dependent jobs don't execuet

and keep on popping message in the log "Semaphor file found, but can't execute

job as it is already in the que." Whats the best way to handle situaion,

Kill the job fro m the que..!! And how can I avoid the same from happening again.

Regards...

Viji

File-watching job start times are estimated based on the past job performance and start times. To get rid of these jobs from the forecast report, delete their performance data from the Performance Data directory. Basically delete [job id].jpd files whose names match Ids of these that you want to remove from the forecast report.

As for the "job is already in the queue" - this is just a warning that the job is already queue or being executed and yet the file is still there. This could happen if the job takes a while to run and doesn't bother to rename or move the related file in the beginning of the run. As a result, the scheduler finds the same file again and again. It could also happen if the job is sitting in the queue being blocked or used by some other jobs with the same result, the scheduler finding the same file again and again. This is just a status message which could be safely ignored.

: Hi,

: I see few of the jobs in forcast report with schedule as "File*".

: All of these are for past dates. How can I clean this up.

: ----

: Also sometimes few semaphor file dependent jobs don't execuet

: and keep on popping message in the log "Semaphor file found, but can't

: execute

: job as it is already in the que." Whats the best way to handle situaion,

: Kill the job fro m the que..!! And how can I avoid the same from happening

: again.

: Regards...

: Viji

Thanks.

: File-watching job start times are estimated based on the past job performance

: and start times. To get rid of these jobs from the forecast report, delete

: their performance data from the Performance Data directory. Basically

: delete [job id].jpd files whose names match Ids of these that you want to

: remove from the forecast report.

I actually delete the semaphor file prior to running hte dependent job. And jobs are

really small (5 seconds at the max). But this message stays in the loop for hours and job

never runs. But when I check my que it generally has 4-5 jobs qued-up.

Is there a limit on #of jobs can be qued at a time. I am using single user

24X7 on a network PC.

: As for the "job is already in the queue" - this is just a warning

: that the job is already queue or being executed and yet the file is still

: there. This could happen if the job takes a while to run and doesn't

: bother to rename or move the related file in the beginning of the run. As

: a result, the scheduler finds the same file again and again. It could also

: happen if the job is sitting in the queue being blocked or used by some

: other jobs with the same result, the scheduler finding the same file again

: and again. This is just a status message which could be safely ignored.

There is no hard limit on the number of queued jobs.

The warning message appears for hours because the job sits in the queue for hours, waiting for some other job in front of it to release the queue. It looks like you experience some kind of a queue stagnation issue.

I suggest that you configure a separate queue just for this job so that it cannot be blocked by other jobs.

: Thanks.

: I actually delete the semaphor file prior to running hte dependent job. And

: jobs are

: really small (5 seconds at the max). But this message stays in the loop for

: hours and job

: never runs. But when I check my que it generally has 4-5 jobs qued-up.

: Is there a limit on #of jobs can be qued at a time. I am using single user

: 24X7 on a network PC.

: There is no hard limit on the number of queued jobs.

: The warning message appears for hours because the job sits in the queue for

: hours, waiting for some other job in front of it to release the queue. It

: looks like you experience some kind of a queue stagnation issue.

: I suggest that you configure a separate queue just for this job so that it

: cannot be blocked by other jobs.

How can I assign a separate new que to a job. Right now all jobs use same default

que.

1. Click Tools/Job Queues menu then click New to define a new queue

2. Modify job properties. In the step where you are prompted for the queue name, choose new queue.

Hope this helps.

: How can I assign a separate new que to a job. Right now all jobs use same

: default

: que.

: There is no hard limit on the number of queued jobs.

: The warning message appears for hours because the job sits in the queue for

: hours, waiting for some other job in front of it to release the queue. It

: looks like you experience some kind of a queue stagnation issue.

: I suggest that you configure a separate queue just for this job so that it

: cannot be blocked by other jobs.

How can I assign a separate new que to a job. Right now all jobs use same default

que.