Re: Printer Qeues

printers are driven by print-symbionts, which operate device execution queues. A generic queue is a higher-level structure, which accepts print-jobs and distributes them to execution queues.

You can stop an execution queue with STOP/QUE/RESET HPLJET_PS

And you can start it again with START/QUE HPLJET_PS

$init /que /start /generic=HPLJET_PS

This command is missing the target queue name parameter, that you want to start. The /GENERIC=HPLJET_PS qualifier specifies, that print-jobs submitted to this 'generic' queue (who's name you did not specify as a parameter) are to be sent to the execution queue HPLJET_PS.

If a print-job does not get printed, use SHOW ENT/FULL or SHOW QUE/ALL/FULL HPLJET_PS to find out the reason why.

Normally we have an "Evaluation application" which sends the job to SYS$FAST and gets assigned to respective exec queues. Once the evaluation is done, the application(I think) automatically starts a print queue.

Now there are two different problems here (could have one solution though).

1st Due to the above (stop and init que changes) I did after the evaluation is done by SYS$FAST que there is no printing que started.

2nd Before I did any changes (the way the things normally are at startup) often after the evaluation is completed the printer queue started stays pending and the no of printer entries just keep building up. So finally we reboot the whole system and things get back to normal.

Please let me know for which problem you are suggesting an explanation. If you need more info please let me knowNipun

Re: Printer Qeues

Sorry, I had not read the ZIPs before (blocked by policy).Now, at home, I have seen them.

I notice HPLJET_PS being generic, and it has an execution que HPLJET.

_THAT_ is the print execution queue, Can you post what _THAT_ looks like?

From what I have seen so far, I would guess that THERE is your trouble somehow.Please post the outpot of $ SHOW QUEU HPLJET /FUL/ALL.(if you make that a simple text file (extension .TXT), then I am sure it will come through).

Re: Printer Qeues

Nipun,

I don't understand why you are using a generic queue. Why aren't you printing directly using TCPIP$TELNETSYM ?Using /AUTOSTART_ON=(node1,node2,node3) you can make sure this queue is always running in the cluster. But anyway, the queue can be stopped because possible you are using the wrong processor. '/PROCESSOR=TCPIP$TELNETSYM' on the execution queue .If there are more systems printing to this printer, the printer will be stalled until the other system gives the printer 'back' or 'releases the printer' for other jobs.A printer can only get information from one system at once. If eg windows is printing to this printer and doesn't free the printer, the printer stays connected to windows and no other system (even VMS) can print until this is done. Even so for VMS. If VMS is printing to the printer and doesn't free the printer after the job no other system can print to this printer. This was in the time from TTA to LTA most of the time the problem. The PROCESSOR could be the same, but never released.

Re: Printer Qeues

Currently all the printing seems to be working fine.But when the problem occurs in future I intend to collect the data as

$show que /full HPLJET /out=PRINT_HPLJET_FULL_SERVER.TXT

$show que /full HPLJET_PS /out=PRINT_HPLJET_FULL_SERVER.TXT

and post it here.

For now I was able to Ping successfully. I also tried both the commands

$Print /que=HPLJET printed the file successfully

$Print /que=HPLJET_PS printed a kind of Info sheet stating the node name user account entry no. and file name 25-MAY-2005 ....%DCPS-W-UNDEF,undefined: Name not known - offending command is $25-May.......%DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored

Re: Printer Qeues

Nipun,

I am now entering territory that I have noe experience myself, so maybe others can supply better details, but as far as I can see now, (please correct if my view is wrong) you are (correctly printing a plain text file. But if you choose the other queue, then it it set to expect PostScript fromatted data, and it does not know what to do with other input.