| Don't really see what good it would do you, Nicola. It shows *all*
the queue entries because it is coupled to the ADG cluster which
is where the *real* LN03 queue is. You see an empty queue on
RDGE43/CHEST because what you're looking at is a DQS queue. As soon
as you submit a job to a DQS queue, it will be sent to it's target
system (i.e. ADG) where it will join the merry throng patiently
waiting it's turn to print. Meanwhile, all you look at is the DQS
queue on FUTURS which is *almost* guaranteed to be empty 99% of
the time.
To see what the LN03 is *REALLY* doing, you need to SET HOST (or
CONNECT from the LAT) to the ADG cluster and look at the queue from
there. Get it??
steve
|
| > is where the *real* LN03 queue is. You see an empty queue on
> RDGE43/CHEST because what you're looking at is a DQS queue. As soon
> as you submit a job to a DQS queue, it will be sent to it's target
> system (i.e. ADG) where it will join the merry throng patiently
> waiting it's turn to print. Meanwhile, all you look at is the DQS
> queue on FUTURS which is *almost* guaranteed to be empty 99% of
> the time.
>
> To see what the LN03 is *REALLY* doing, you need to SET HOST (or
> CONNECT from the LAT) to the ADG cluster and look at the queue from
> there. Get it??
>
> steve
Not quite, DQS is a little smarter than that, what you need to do from
say RDGE43/CHEST is ;
$ qshow/all ln03$q2
This *will* display absolutely everything for that que.
Danish ;-)
|
| � Not quite, DQS is a little smarter than that, what you need to do from
� say RDGE43/CHEST is ;
�
� $ qshow/all ln03$q2
�
� This *will* display absolutely everything for that que.
Oh!! See what you mean. Sorry, I wasn't aware of "qshow" - I was
thinking in terms of $show queue etc
steve
|