This morning I got a request to remove several print queues defined in the following way:
# enq -isWA Queue Dev Status Job Files User PP % Blks Cp Rnk -------------------- -------------- --------- ------ ----- --- --- chca_printx hp@sat20x READY chca_printx-c hp@sat20x READY chca_printx-c-l hp@sat20x READY chca_printx-l hp@sat20x READY chca_printz hp@sat20z READY chca_printz-c hp@sat20z READY chca_printz-c-l hp@sat20z READY chca_printz-l hp@sat20z READY
Without giving it much thought, I logged to the host and executed
smitty rmpq, selected the first queue to be removed and hit the Enter key to see my action fail promptly. This made me think about the task at hand …. Looking at the last output for a while longer, I recognized what I was seeing – these are remote print queues attached to HP print servers (in this case). It took me another moment to remember that I have done something like this years ago, and that then it took me two steps to delete such print device and its queue or queues.
This time around, each HP print server has several associated with it print queues – four to be precise.
AIX has three basic commands to “manually” remove “printing devices”. They are
rmvirprt. The first command
Removes a printer queue, the second one
Removes a printer or plotter queue device, and finally the last one
Removes a virtual printer.
It seemes like the natural order of action is to remove every print
Printer queue attached to the
Printer queue device and finally to delete the device!
# rmque -qchca_printx # rmque -qchca_printx-c # rmque -qchca_printx-c-l # rmque -qchca_printx-l
The print queues removed, it is time to remove the
# rmquedev -dhp@sat20x
The same applied to the second set of queues was gone and the ticket was closed.
It is funny, but this is not the first time that I recognize the limits of memory (mine) which puts me in a philosophical mood – we are “masters” only for a short time, other then that we just pretend ….
Tomorrow, have a Nice Thanksgiving Everybody!!!