Re: DBMS_JOB.RUN - requires spare job queue slot?

In article <d8m4o8$82$1_at_news.caravan.ru>, Dmitry E. Loginov says...
>
> "Jeremy" <newspostings_at_hazelweb.co.uk> wrote in message
> news:MPG.1d189a30dc97d0b9989eb8_at_news.individual.net...
> > Version: Oracle 9iR2
> >
> > If you have job_queue_processes set to e.g. 3 and there are 3 jobs
> > running under DBMS_JOB, will a call to DBMS_JOB.RUN for a 4th job be
> > held pending availability of a slot or will it run immediately?
>
> It will be run immediately in your session independently from
> job_queue_processes parameter value and number of jobs running currently.
>

Thanks Dmitry.

> Be noticed: DBMS_JOB.RUN will reset state of packages in your session.

Not clear what you mean by this. You don't mean like variable values set immediately before calling DBMS_JOB.RUN will be reset to their default values in the calling PL/SQL upon completion of the JOB do you? Or are you saying that if DBMS_JOB.RUN is used to execute a procedure in the same package as the calling PL/SQL then its state will be reset?

Or perhaps it is time to go read up some more on this ;)

-- 

jeremy