All batch jobs submitted are turning 'PENDING..' how to overcome

[kumaraguruparan]

On VMS alpha800 server here, the batch jobs for cleaning up of logs and other applications have been found executing perfectly for the submitted time till two days back when by mistake the queue was deleted and then manually initialized and started.
But currently after that the jobs submitted are observed to be normally 'Holding' till submitted time and turns to 'PENDING' status when execution time arrives.
It is sure that restarting will resolve, But restart is impossible as there would be huge data loss during the server boot time.
Please help me by giving the command to resolve above issue without restarting.

Thanks'
Guru

[labadie_1]

can you post the output of the following commands

$ sh que /batch/full
$ sh que /manager/full

Is this Alpha 800 a member of a Cluster ?

[Joseph Huber_1]

[It is sure that restarting will resolve]

Are You sure ?
What is the state of the queue ?

SHOW QUEUE/FULL queuename

Is it really started after recreation ?

Is it started on the right node ?

Are there many pending jobs because the joblimit parameter is too small after recreate ?
Is joblimit exhausted because running jobs not ending ?

[kumaraguruparan]

Thanks for the responses,
the output of command 'show queue/full' is in the SHOW_QUEUE_FULL.TXT attached.
I am available here to provide you more required information.
Thanks,
Guru

[Duncan Morris · Accepted solution]

Guru,

welcome the the OpenVMS itrc forum!

Your BATCH queue, SYS$BATCH has not be recreated correctly - it has been created as a PRINTER queue!

Printer queue SYS$BATCH, stopped, on NA0DS1::

You need to delete the queue, and then recreate it as a batch queue.

Duncan

[kumaraguruparan]

Duncan Morris,
Yes now I have initialized and started the queue sys$batch as 'BATCH' after deleting the old PRINTER queue.
I have submitted a job and it is holding to execute.Hope the problem is resolved, will update you once the job starts executing.

Thanks,
Guru

[kumaraguruparan]

Thanks Duncan Morris,
The issue is resolved after I deleted the printer queue and initialized the queue as batch with 10 joblimits.
Thanks again for the solution.
-Guru