PENDING PRINT JOBS WHILE QUEUES ARE STARTED

[KENDALL MCCARTHY_1]

I HAVE PRINT QUEUES WHERE THE JOBS ARE PENDING AND THE QUEUES ARE STARTED . tHE ENTRYS HAVE A "CHARACTERISTICS MISMATCH"
?

[Ian Miller.]

can you post the result of SHOW QUEUE/FULL for the queue and
SHOW ENTRY/FULL for one entry.

[Dean McGorrill]

if they are old jobs you can probably delete
them. otherwise you can requeue it elsewhere, or set the queues characteristics. try doing a help submit/char for info. then do a show queue/char. you might be able to release them, else post the que and job full as ian
suggested.

[Jan van den Ende · Accepted solution]

Kendall,

first, WELCOME to the VMS forum!

The SHOW commands Ian shound indicate where the mismatch lies.
It may well be, that the actual mismatch is not really relevant (YOU should be able to to decide, it is YOUR environment).
_IF_, and ONLY if, the differences are not really relevant, THEN you can either
$ SET QUEUE /CHAR=,
OR
$ SET ENTRY=/CHAR=
for every entry that IS compatible.

If the characteristics really are physcally different (like different paper size) then stop the queue, change the relevant property, adjust the characteristic as above, and restart the queue.

Expect the que now to proces these jobs, but to pend any no-longer-matching-char jobs.

HTH

Proost.

Have one on me.

jpe

[atul sardana]

Dear Kendall,

SET QUEUE */CHARACTERISTICS

/CHARACTERISTICS=(characteristics[,...])
/NOCHARACTERISTICS

Specifies one or more characteristics for processing jobs on an execution queue. If a queue does not have all the characteristics that have been specified for a job, the job remains pending. If you specify only one characteristic, you can omit the parentheses. Each time you specify the /CHARACTERISTICS qualifier, all previously set characteristics are canceled. Only the characteristics specified with the qualifier are established for the queue.
Queue characteristics are installation specific. The characteristic parameter can be either a value from 0 to 127 or a characteristic name that has been defined by the
DEFINE/CHARACTERISTIC command.

The /NOCHARACTERISTICS qualifier cancels any characteristics settings previously established for that queue.

Atul sardana.

[KENDALL MCCARTHY_1]

Thanks for your responses. Im a DBA and havn't had to deal with this stuff in a while.

Here is the scenerio. The site I am at did a disaster recovery exercize Yesterday. There were many issues (from an application perspective) with the printing of reports to all the distributed printers accross the state of Florida. There were two issues:

1) The issue with the characteristics that you have answered.

2) One of the queues has 8 jobs in it . The jobs seem to be rotating through the queue but not printing. They seem to be in a continual loop getting new entry numbers each time that rotate through.I have stooped the queue and the jobs are pending. any suggestions?

Thanks Kendall

[Dean McGorrill]

hi Kendall
thats a new one to me. some one/thing maybe requeueing the jobs, check
the submission time. you could try a set queue/close your-quename and restarting it
which will prevent new jobs from being queued.

[Jim_McKinney]

> loop getting new entry numbers each time that rotate through

What print symbiont is in use here? (The symbiont can be determined by using the command "SHOW QUEUE/DEVICE/FULL queuename" and noting the value associated with the "PROCESSOR" attribute.) Also, you might place a "/ALL" qualifier on the above "SHOW" command and note if the listed print jobs contain any "NOTE" value that might provide a clues as to the reason for re-queueing.

[KENDALL MCCARTHY_1]

Server queue ORL_T4100, idle, on LOTTOA::, mounted form DCW_CHECK_TRAY1
(stock=DEFAULT)
/BASE_PRIORITY=4 /CHAR=(69,70) /DEFAULT=(FEED,FORM=DEFAULT)
/LIBRARY=DEVCTL_T4000 Lowercase /OWNER=[SYSTEM] /PROCESSOR=TCPIP$LPD_SMB
/PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR

[Jim_McKinney]

LPD. Are there any messages associated with the requeued entries ("SHOW ENTRY/FULL nnn" for example)? How about in the system OPERATOR.LOG? Is the system that is home to the remote printer accessible?

[Wim Van den Wyngaert]

$ ucx ping lottoa
(connected/reachable ?)

$ telnet lottoa /port=515
(accepting ?, if so abort telnet)

$ dir sys$library:DEVCTL_T4000.tlb
(existing on all nodes ?)

I also have seen printers that can't handle LPD connections coming too fast and thus refuse all connection (which causes a requeue) and after a time (e.g. 10 sec) restarts accepting connections. Just release them 1 by 1 with a 15 second interval and it might work.

Wim

[KENDALL MCCARTHY_1]

Looks like we were missing the .tbl . Im going to give that a shot . Thanks for your help!!

[Jan van den Ende]

Kendall,

for saying thanks forum-style:

http://forums1.itrc.hp.com/service/forums/helptips.do?#33

Proost.

Have one on me.

jpe

[Wim Van den Wyngaert]

If your tlb is the problem, it should be present on 1 of the systems. You can copy it to all the systems (they all have their own system disk ?).

Wim

[Jan van den Ende]

Kendall,

you found the mechanism, now pleas validate EEACH answer. My note was NOT the solution to your problem the various answers however HAVE contributed. Please value those.

(and THIS answer ZERO points, please.)

Proost.

Have one on me.

jpe