Restart the Batch Queue on OVMS 7.3-2

[Neal Kirby]

Neal Here

New Guy!

My Admin is on Hols and we need to solve this problem.

OVMS 7.3-2 is running on (a test box) Alpha 4100. Unfortunately the batch queue is not running. The usual commands:

SH QUEUE/BATCH
SH QUEUE/ALL
ETC... hang (forever)

CTRL Y to interupt and exit

I have looked in SYS$STARTUP but cannot see a startup for the batch queue.

Can someone recommend a solution and the suitable command?

Thanks

Neal

[Karl Rohwedder · Accepted solution]

Neal,

welcome to the OpenVMS forum.

If a certain queue is not running, a SHOW QUEUE command should not hang, but show the queue in a state e.g. STOPPED.

Is the queuemanager running (SHOW /QUE/MANA/FULL)? perhaps the disk, on which the queue database is located has a problem.

To start the queuemanager you use START/QUE/MANAGER..., but there a more installation dependant settings available, which you should supply (number of queue managers, location of queue database...).

Perhaps yu may post the output of a SHOW/QUEUE/MANAGER/FULL 1st to get us started.

regards Kalle

[Volker Halle]

Neal,

welcome to the OpenVMS ITRC forum.

Looks like there is some problem with your queue manager or job controller.

Do these processes exist and are they in HIB state ?

$ SHOW SYS/PROC=JOB_CONTROL
$ SHOW SYS/PROC=QUEUE_MANAGER

Any queue manager errors reported in SYS$MANAGER:OPERATOR.LOG ?

Volker.

[Neal Kirby]

Kalle - you get the points for this one - The batch queue was started but it could not be seen or jobs could not be added to it.

As the day progressed other services began to halt.

The console on the server is throwing up disk space errors. Looks like there is not enough disk space on the system disk for these processes to operate.

Thanks

[Jan van den Ende]

Neal,

time for action!

Perhaps it would be best to start with

$ PURGE SYS$SYSDEVICE:[*...]/KEEP=2/LOG

and see how much you gain.

Not the most elegant solution, but probably the quickest, any maybe enough to proceed with some more nuance.

If that is not enough, a good second idea may be
$ DELETE SYS$SYSDEVICE:[*...]*.LOG.*/BEFORE=YESTERDAY/MODIFIED/LOG

Proost.

Have one on me.

jpe

[Neal Kirby]

Thanks for the response JPE

I have just posted a new request...

I think it is a tad too late for the action plan.

NK