Does anyone know how to list the form queues and their attached form
queue device driver?

The ASSIGNFQ command attaches a device driver to a form-queue, and the
SP-ASSIGN... will assign the port to that form-queue. With the port
attached to the form-queue I can then see what device driver is
attached to the form-queue. I could generate a program that would
execute the 1024 sp-assigns required to get the infomation that I want,
but that seems like a silly (long) method to get the information.

I'm looking for a way of just doing a listing of the form-queues to see
what, if any, device driver is attached to any queue, or, better still,
list only the form-queues that have a device driver attached to them
and show the name of the device driver.

Best regards,

Dale

Good question. What do you see with SP-STATUS and LISTPTR?

Regards,
T

"Dale" <dale_benedict (AT) flightcraft (DOT) ca> wrote:

Nothing regarding and device drivers.

Listptr shows:
Page Dev or
Type Number Output Queues Skip Line # Status
serial 11 11 0 255 inactive

and sp-status shows:

Printer # 11 is serial, inactive, and on line.
The printer is running on line 255.
Assigned output queues: 11 .
The number of inter-job pages to eject is 0.

I know there is a device driver attached to form 11.

The other thing with sp-status/listptr is that they only show the
printer status, they don't show the form-queue or any attached driver.

SP-ASSIGN ? will show the attached driver, but that means a small
program to execute sp-assign fnnnn ? 1024 times.

Do note that a device driver can be attached to a form-queue but the
form-queue does not need to be attached to a printer.

Dale

Tony Gravagno wrote:

How about 'listabs' ?

It doesn't report by form queue, it reports by pib; but it does show
assigned form queue number and the associated device.

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

Scott Ballinger wrote:
Been there done that...

I'm trying to get the info about the form-queue itself, without going
thru the gyrations of a program and doing the sp-assgns. If no port is
assigned to a form-queue D3 still won't list what is happening with the
form-queue.

I thought someone out there would happen to know a command to do what I
want but, alas, I guess I'll write a program to do what I need to do,
and report this short-coming to my VAR, and thus up to the D3 people.

Thank-you all for the use of your thinking-caps.

Regards,

Dale

Scott Ballinger wrote:

You might try the WHERES command.

From my system with two printers attached to fq 1 and 2 via ASSIGNFQ

Unknown
0000 000080 F310 000018 RDL_GETCHAR:000 RDL_GETCHAR:000 READLINX:000
LG_ON_PROMPT:000
-------------------------------------------------------------------------------
mark brown mark - epick
wheres z Line# Status Copies Form# Device
1 p 1 2 hp-lzrii
*0001 002C4A FF90 000018 1 WS_WHERE1:000 WS_WHATWHERE:000
-------------------------------------------------------------------------------
Data manager dm - dm
listabs Line# Status Copies Form# Device
2 p 1 2 hp-lzrii
0002 000082 F390 000018 CNTRLNP:000 NPAGE:000 SP_LISTABS:000
-------------------------------------------------------------------------------
At Coldstart Logon
0003 000083 7310 000018 MD0:000
-------------------------------------------------------------------------------
At Coldstart Logon
0004 000084 7310 000018 MD0:000


You will obviously need logic to dig the real data out from the flak, but it should show printer assignmen and device assignment for each port currently logged on. Use the Z option for all users.


Mark Brown


"Dale" <dale_benedict (AT) flightcraft (DOT) ca> wrote

Ross,

Thanks for the pointer. LISTFQ is not in D3's on line help guide.

The program will need a small tweak as it only looks at started
printers.

Based on the program, D3's way of getting the list that I want, is the
same way I described in an earlier post.... Execute the SP-ASSIGN
statement for all 1024 possible form-queues, and capture the
information for a report.

Thanks a big bunch Ross, and all those who applied their thinking caps
to my problem.

Regards,

Dale


Ross Ferris wrote: