Remove form specification from queue

[Jan van den Ende]

The everlasting joys of mixed environments!

Situation:
It has been decided that we will use a (BillyWare based) Secure Print Server.

Each printer will collect any prints to be output, and if the user enters a code into the printer, only then will his document be printed.

Of course that means that the printers will ONLY be accessable via Mickey's PrintServer.
Which is LPD/LPR, with all the joys of that.

The solution for VMS seems to be a TELNETSYM queue printing to a LPD/LPR printing to the PrintServer, which will consider it like any Whinedoze printjob.
(that VMS looses any info about the proceeding is "a minor detail")

Now for our issue:
The second PRINT command (to the LPD queue) ends with %LBR-E-ILLCTL, illegal control index.

We >>> suspect <<< that the qualifier /DEFAULT=FORM=DEFAULT may be the issue.
Trying to SET QUEUE xxx /NODEFAULT or
SET QUEUE xxx /DEFAULT=NOFORM
both are accepted without error, but the default form stays unchanged.

Is our suspicion correct?

Anybody recognise that error?
Anybody know the cause?
ANYBODY KNOW A CURE?

tia,

Proost.

Have one on me.

jpe

[Mike Reznak · Accepted solution]

Hi,

If no form type is explicitly specified, the system assigns the
form "DEFAULT" to the queue.

So it probably cannot be changed. If the form is the issue, then you probably will have to create special form for LPD printing.

But the message points to the library problem.

ILLCTL, illegal control index

Facility: LBR, Librarian Routines

Explanation: Either the library is not open or an illegal library index was
specified.

User Action: Determine that the library is open and that the library index
is correct.


Mike

[Uwe Zessin]

It's my understanding that a queue always needs a default from. How else is a simple "$ PRINT/QUEUE=" statement supposed to work?

Can you put up a "show queue/full"?

I guess there is a problem with device control libraries. E.g. does the DEFAULT from specify a setup module, but the queue is missing a DEVCTL or something like this.

[Jan van den Ende]

Mike, Uwe,

BINGO

It can be so simple, and so simple to miss when operating in a team with too little opportunity to discuss setups, but only the problems.

This way of solving is MUCH quicker than searching yourself!

Proost.

Have one on me.

jpe

[Mike Reznak]

I'll definetly have one on you! ;o)

Mike