[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference unxa::cde

Title:	CDE on Digital UNIXonment - CDE
Notice:	CDE on Digital UNIX - for CDE on VMS, please see Note 1.3
Moderator:	UNXA::SYSTEM

Created:	Tue Nov 23 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	660
Total number of notes:	2674

617.0. "dtprintinfo & remote queues." by SWETSC::HAGLUND () Tue Mar 11 1997 05:55

			Hello!

	 When using "Print Manager" (dtprintinfo) on DUNIX v4.0B
	and looking at a remote queue going to a VMS machine running 
	ucx/lpd/telnet printing you cannot see the Printer Jobs. 
	No problem to see the printer job when printing to a remote 
	queue from v4.0B to a Ultrix/DUNIX node. We tested to stop
	the telnet queue to be sure the jobs didn't "disappear" from
	the queue. Lpq showed all the jobs to be there:

birger> lpq -Plp3
birger.soo.dec.com: Tue Mar 11 11:35:47 1997:
telnetko is paused
Rank   Owner      Job  Files                                  Total Size
active UCX_LPD    896  .login                                 2048 bytes
1st    UCX_LPD    898  .login                                 2048 bytes
2nd    UCX_LPD    899  .login                                 2048 bytes
birger>

dtprintinfo however says the queue is empty.

Is this a CDE or UCX problem?

Any hints?

Regards,

Tomas Haglund

T.R Title User Personal
Name Date Lines

617.1 UNXA::BEUTE No good deed ever goes unpunished... Tue Mar 11 1997 09:44 9

T.R	Title	User	Personal Name	Date	Lines
617.1		UNXA::BEUTE	No good deed ever goes unpunished...	`Tue Mar 11 1997 09:44`	9
	dtprintinfo uses the "lpstat -oPRINTER" command to check the status of print queues, and tries to parse the output based upon some known rules. It may not be recognizing what is returned from a VMS print queue- I don't have the local resources to try it here. If you can reproduce this, please show the output of an 'lpstat -o' command to the VMS print queue. And file an IPMT or QAR if you'd like to see it addressed.

	dtprintinfo uses the "lpstat -oPRINTER" command to check the
	status of print queues, and tries to parse the output based
	upon some known rules. It may not be recognizing what is returned
	from a VMS print queue- I don't have the local resources to try 
	it here. If you can reproduce this, please show the output of
	an 'lpstat -o' command to the VMS print queue. And file an IPMT
	or QAR if you'd like to see it addressed.