Conference lassie::ucx

5470.0. "/PASSALL on Inbound LPD queue, can't avoid it" by 29087::MATTHEWS_G (Gary/Matt DTN 343-1139) Fri Apr 25 1997 15:05

C970319-5928   UCX LPD printing

Quick summary:

Customer running UCX 4.0 no ECO's has an LPD inbound queue where all jobs
from an NT system cause the job in the queue to show up as /PASSALL.

They have found that this causes the jobs to format poorly and if they
manually remove the /PASSALL on the entry and then requeue it to the VMS
queue the LPD points to; it prints much better, as they wish it to.

Customer has found no action under UCX and LPD queues that can prevent this
/PASSALL from occurring.

The UCX$LPD_STREAM_PASSALL is inapplicable because the queue is an INBOUND
one.

Setting the   'pa'   symbol in the UCX$LPRSETUP should make a difference IF
a difference can be made and it does not.

A log file generated by the logical LPR_RCV being set, has no text in it
for either PASSALL  or   lcard to quickly prove the job is submitted to the
UCX$LPS_QUEUE has /PASSALL set.

I believe the answer is that if another system generates a PRINT that comes
to an LPD inbound queue and if a    /PASSALL   is put on that entry through
the NT job submittal.... then there is nothing to be done directly under
setting the LPD inbound queue through any setup that can cause those
/PASSALL entries to nolonger have /PASSALL on them.

A workaround would be for the LPD INBOUND to point to an always STOPPED VMS
queue where a COM file examines all entries in the queue and REQUEUES them
to a valid print queue having removed the  /PASSALL on the entry.

I faxed customer a COM file for do some job in queue checking and to then
requeue the job.

I am asking in the UCX notes file to see if there is any opinion on this.
This may also be IPMT'd just to get an official response if there is no
response through the UCX Notes file.

Gary