Sponsored Content
Full Discussion: Printing queue in rs6000
Operating Systems AIX Printing queue in rs6000 Post 302261950 by bakunin on Wednesday 26th of November 2008 04:52:56 AM
Old 11-26-2008
You might want to explore the "qadm" command (man qadm). The spooled printer files reside in "/var/spool/lpd/*" (have a look there, its pretty intuitive) and /var/spool/qdaemon respectively.

You will find your queue definitions (as well as the queue device definitions) in the file "/etc/qconfig".

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. Programming

Good IDE for C++ on RS6000/AIX

I am looking for the above Can anyone point me to a reliable product, with available support in the forseeable future ? Seeker (0 Replies)
Discussion started by: Seeker
0 Replies

2. AIX

RS6000 SSA Raid question

Hi Can I add disks on the fly to extend the capacity of an existing RAID 5 volume? It's created on a 4P Advanced SSA Raid Adapter. I need to extend a volume group, so I figured it would be easiest to extend the "physical disk" which is a RAID5 volume. Thanks. (1 Reply)
Discussion started by: osee
1 Replies

3. AIX

Printing multiple copies via remote queue

Hi all, I have an interesting problem. Using remote queues to print using jetdirect printers I am unable to get a printer to print multiple copies of a print job. command being used: lpr -P -#3 ./test (one copy prints) Also tried: enq -P -C3 ./test (same results) Any ideas? ... (6 Replies)
Discussion started by: Luck
6 Replies

4. AIX

Re-Installation of AIX 5.2 in RS6000 7026

Hi There!! I need to reinstall the operating system AIX 5.2 in a RS6000 7026/6H1 that has AIX 4.3 but I need a firmware upgrade that I dón´t know where can I obtain. - Platform firmware version 3 or later. Someone can help me please, I will be very grateful !! Thank´s. (1 Reply)
Discussion started by: terron79
1 Replies

5. AIX

New to AIX and got my hands on a RS6000 v.need help getting it on the network

So im fairly new to AIX and my knowledge is very, very limited but i got my hands on an RS6000 43P model and im trying to get it on the network so i can access it from work. I have pretty much tried everything i can/know how to do by reading up as much as i can but im still lost. I have the 43P... (2 Replies)
Discussion started by: IIIII
2 Replies

6. AIX

VNC or X Emulator on RS6000 AIX 5.2

Hello everyone, I have just joined your forum even though I have been using it on and off for couple of months now. Up until now I have been able to find any information I needed by just browsing this site or performing a Google search, but now I'm stuck!. I was hoping you could help me with... (16 Replies)
Discussion started by: juniorG
16 Replies

7. AIX

Reinstalling AIX 4.3 on IBM RS6000

Hey guys, I'm a newbie in Unix world.. Currently in my office lies an old IBM RS6000 which hasn't been maintained for a very long time. The former admin has resigned and we don't have any documentation or whatsoever regarding the old machine. All I know that it is an RS6000 is because of what's... (4 Replies)
Discussion started by: arch4ng3l
4 Replies

8. AIX

Remote printing to Linux CUPS queue

Hello all. I am setting up a queue under AIX 4.2.1 to print to a remote Linux CUPS queue. At present I can print to the queue remotely from Windows but not AIX. What I am seeing is lpstat reads the state of the remote queue but at job submission time I am getting backend exit fatal errors. The... (4 Replies)
Discussion started by: tgx
4 Replies

9. UNIX for Dummies Questions & Answers

Sco Unix printing : jobs hangs in queue - printing via lp versus hpnpf

Hi, We have a Unix 3.2v5.0.5. I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts). This is the configuration file : Code: root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies

10. AIX

AIX 5.1 and RS6000

I've an old server 1996 RS6000 (Processor 604e) running AIX 5.1. It started up fine, booted up and connected on 10Mbit with my router. I used to be able to connect to it with telnet but not anymore. I know the IP is right but working with the smit tcpip options, looks like I've changed... (1 Reply)
Discussion started by: Devyn
1 Replies
LPRM(1) 						      General Commands Manual							   LPRM(1)

NAME
lprm - remove jobs from the line printer spooling queue SYNOPSIS
lprm [ -a ] [ -A ] [ -Ddebugopt ] [ -Pprinter ] [ -V ] [ -Uuser ] [ jobid... ] [ all ] DESCRIPTION
Lprm will send a request to the LPD server to remove jobs from a spool queue. (See clean(1) for an lp(1) compatible interface.) Lprm is normally the only method by which a user may remove a job. The jobs to be removed are specified by the job number or user name; with no specifiers the first removable in a queue will be selected for removal. Usually users may only remove jobs submitted by themselves from the host which originated the original lpr request. The spool queue is searched first for jobs that the user has permissions to remove, then for jobs that match any of the specified set of tags. If no tags are specified, only the first job in the queue that the user has permissions to remove will be removed. If the -a flag or the all spool queue is specified, lprm will search all available spool queues. The all wildcard jobid is used to match all jobs in a spool queue; however unless the user has control permissions for the spool queue only the user's jobs will be removed. See the lpd(1) man page for details about control permissions. A jobid can be a job number, a user name, a job identifier, or a pattern for a glob based wild card match. This match is applied to the job identifier information. Lprm will announce the names of any files it removes and is silent if there are no jobs in the queue which match the request list. If the job being removed is active, the LPD server will stop printing the job and then restart printing operations. EXAMPLES
Remove the last job I submitted if it is in the queue: lprm Remove job 25 in spool queue p1: lprm -Pp1 25 Remove job 25 and 30 in spool queue p1: lprm -Pp1 25 30 Remove all of user john's jobs in spool queue p1: lprm -Pp1 john Remove all jobs in spool queue p1: lprm -Pp1 all Remove all jobs in all spool queues: lprm -a all Remove the jobs with identifier nobody@system in spool queue p1. Note that the quotes around the pattern are needed to suppress shell glob expansion. lprm -Pp1 'nobody@system*' OPTIONS
-A Use authentication specified by the value of the AUTH environment variable. -a Remove files from all spool queues available to the user. -Pprinter Specifies printer queue. By default, the destination printer is taken from the command line dest value, then the environment vari- ables PRINTER, LPDEST, NPRINTER, NGPRINTER, then first entry in the printcap information, and and finally the default_printer entry from the configuration file, and then the compile time default. -Uuser Explicitly provide a userid for doing the removal to the LPD server. This can be done only by ROOT or userids listed in the allow_user_setting configuration or printcap option. This facility is provided to allow printing front end systems such as SAMBA to submit job removal requests on behalf of users. -Ddebugopts Debugging is controlled using the -D option. This accepts a comma-separated list of debugging settings. These settings take one of two forms: facility=value , or value to set an overall default value. -V The -V option prints the version information for the program and verbose information about activities. WARNINGS
Users with CONTROL (i.e.- administrative) permissions on spool queues can remove any or all jobs. The all wildcard defaults to all user jobs, not just those submitted by the user. This allows administrators to purge a spool queue easily. ENVIRONMENT
By default, the destination printer is taken from the command line dest value, then the environment variables PRINTER, LPDEST, NPRINTER, NGPRINTER, then first entry in the printcap information, and and finally the default_printer entry from the configuration file, and then the compile time default. EXIT STATUS
The following exit values are returned: zero (0) Successful completion. non-zero (!=0) An error occurred. FILES
The files used by LPRng are set by values in the printer configuration file. The following are a commonly used set of default values. /etc/lpd.conf LPRng configuration file ${HOME}/.printcap user printer description file /etc/printcap printer description file /etc/lpd.perms permissions /var/run/lpd lock file for queue control /var/spool/lpd spool directories /var/spool/lpd/QUEUE/control queue control /var/spool/lpd/QUEUE/log trace or debug log file /var/spool/lpd/QUEUE/acct accounting file /var/spool/lpd/QUEUE/status status file SEE ALSO
lpd.conf(5), lpc(8), lpd(8), checkpc(8), lpr(1), lpq(1), lprm(1), printcap(5), lpd.conf(5), pr(1), lprng_certs(1), lprng_index_certs(1). DIAGNOSTICS
Most of the diagnostics are self explanatory. If you are puzzled over the exact cause of failure, set the debugging level on (-D5) and run again. The debugging information will help you to pinpoint the exact cause of failure. HISTORY
LPRng is a enhanced printer spooler system with functionality similar to the Berkeley LPR software. The LPRng mailing list is lprng@lprng.com; subscribe by sending mail to lprng-request@lprng.com with the word subscribe in the body. The software is available from ftp://ftp.lprng.com/pub/LPRng. AUTHOR
Patrick Powell <papowell@lprng.com>. LPRng LPRng-3.9.0 LPRM(1)
All times are GMT -4. The time now is 01:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy