Re: meaningful queue commands


"Phillip Helbig---remove CLOTHES to reply" <helbig@xxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:efee68$608$2@xxxxxxxxxxxx
In article <1159343152.496974.315440@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Cluster-Karl" <karl.rohwedder@xxxxxx> writes:

Perhaps the following suits your needs:

SAP01_Rohwedder. init/que/batch/star/auto=(sap01::,sap23::) kalle
SAP01_Rohwedder. shb kalle
Batch queue KALLE, idle, on SAP01::
SAP01_Rohwedder. stop/que/nex kalle
SAP01_Rohwedder. shb kalle
Batch queue KALLE, stopped, autostart inactive, on SAP01::
SAP01_Rohwedder. init/que/batch/star/auto=(sap23::,sap01::) kalle
SAP01_Rohwedder. shb kalle
Batch queue KALLE, idle, on SAP23::

OK, it works, but why?

STOP

/QUEUE

/NEXT

Stops the specified queue after all executing jobs have completed
processing. No new jobs are initiated. For autostart queues, also
marks the queue as inactive for autostart.

Since the job is an endless loop, I would expect the command to never do
anything, since the job will never complete.

Perhaps I should have said that I don't want to just change the nodes in
the queue, but do so while a job is running and have that job failover
to another node.



If you want to requeue the job to another queue:
$ STOP/QUEUE/REQUEUE=other_queue executing_queue/ENTRY=nnnn

Syltrem


.

Relevant Pages