Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Remote print from SLES (SAP) to AIX 7.1 04 sp2 virtual printer queue gets down Post 303027657 by Deneth on Friday 21st of December 2018 07:45:02 AM
Old 12-21-2018
Dear all,
thank you all for Your answers. It stared to work. What did the trick ? The truth is...I don't really know.
It didn't work, but when I restarded spooler and editiet qconfig file (while the queue was ,,ready'') it started to work
so what I did :

1: the queue has staus down
I restared whole spooler with commands :

Code:
stopsrc -g spooler
startsrc -g spooler

2:
I held jobs from the queue

Code:
qhold -PvBIOM

and enabled it again with command

Code:
enable vBIOM

3:
Then I added parameter to the virtual printer definition in qconfig.
it looks like this now (the parameter does not do anything though, when I believed it was supposed to log)

Code:
vBIOM:
        backend = /usr/scripts/backend/BIOM -D /tmp/pst/log



and it worked.

First I released 1 job, then another one , and after that I released all of them and all of them got processed.
The prints are working now.

My guess is that either restarting the spooler did the trick, or editing the qconfig was made at the right time so the qconfig.bin was rebuilt.
I don't really believe that -D parameter helped.

Moderator's Comments:
Mod Comment edit by bakunin: Please use CODE-tags for code, terminal output and data. Thank you.

Last edited by bakunin; 12-21-2018 at 06:38 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

Solaris- print to a remote queue

Is it possible to send a print job to a print queue on a different machine? (3 Replies)
Discussion started by: dangral
3 Replies

2. AIX

Can you set up a networked printer as a local print queue?

Fairly simple question, I think. Still trying to get my head around AIX print queues. Most of our problems seem to stem from print queues going down. This generates help-desk calls when users call up to get their queues started or to get rid of the emails that qdaemon sends them. Looking at... (0 Replies)
Discussion started by: alexop
0 Replies

3. UNIX for Advanced & Expert Users

Solaris 8 setting up a remote printer queue

I have a printer installed over ADSL to a router at a remote location. A Windows printer queue has been setup and working and I can ping the IP address from the Solaris server. I now want to add a printer queue for this printer under Solaris, but I am unsure how to setup a remote printer queue.... (0 Replies)
Discussion started by: miredale
0 Replies

4. UNIX for Dummies Questions & Answers

Solaris 8 setup remote printer queue help

I am trying to setup a remote printer (home users printer) through Solaris 8. The IP address is 172.16.17.10 and I can ping the printer, a local windows printer queue has been setup and works but now I am trying to setup a remote Unix printer queue. With this being a remote printer, do I need to... (2 Replies)
Discussion started by: miredale
2 Replies

5. UNIX for Dummies Questions & Answers

Where are the repositories located in SUSE SLES 10 SP2

Hi, In SUSE SLES 10 SP2 where are the software repositories located? In CENTOS they are in /etc/yum.repositories or something like that. What does SLES use? (1 Reply)
Discussion started by: mojoman
1 Replies

6. SuSE

SLES 10 SP2 possible kernel problem, / slowly filling up

Hello Guys I first though about posting this to emergency but cause I fixed my issue with an reboot its not as important, more is important to me what caused this situation Some facts: OS: SLES 10 x64 SP2 (Virtualized Vmware ESX 3.5) / vmware tools status OK Soft: Oracle10g LVM... (1 Reply)
Discussion started by: kl1ngac1k
1 Replies

7. HP-UX

[Solved] a way to tell printer used by configured print queue?

Hello; As the title says, am trying to find our which driver is used for the alraedy working print queues.. neither hpnpf nor hppi seems to give that info .. Any ideas ?? Thnx (2 Replies)
Discussion started by: delphys
2 Replies

8. AIX

Help with clear printer queue script in AIX 5.3

Good day UNIX forum, could you help me with my clear printer queue script, i have problems with the consistency of this function, sometimes it works sometimes it doesn't. Thanks in advance } preRemovePrintQ(){ clear; echo; echo... (1 Reply)
Discussion started by: beware187
1 Replies

9. SuSE

Failure of Vmware Server 2 installation on SLES 11 SP2

Issue: I am trying to install Vmware Server 2(VMware-server-2.0.2-203138.x86_64) installation on SUSE Linux Enterprise Server 11 (x86_64) SP2 and it fails with error: None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try... (3 Replies)
Discussion started by: rupeshkp728
3 Replies

10. High Performance Computing

Job Schedular for Suse Enterprise SLES 11 SP2

We have a server with 160 hyper-threaded cpu's threads and 2Tb of RAM. I need to implement command line job queue and parallel thread usage for multiple user environment kindly suggest necessary tools to be installed. I have understanding that sun grid engine like applications are available for... (0 Replies)
Discussion started by: vaibhavvsk
0 Replies
FOOMATIC-CONFIGURE(1)					      General Commands Manual					     FOOMATIC-CONFIGURE(1)

NAME
foomatic-configure - the main configuration program of the foomatic printing system. SYNOPSIS
foomatic-configure [OPTION]... foomatic-configure -n queuename [ -N description ] [ -L location ] [ -c con- nect ] [ -d driver ] [ -p printer ] [ --ppd ppdfile ] [ -s spooler ] [ -C [ sourcespooler ] source- queue ] [ -o option1=value1 -o option2 ... ] [ -q ] foomatic-configure -D -n queuename [ -s spooler ] [ -q ] foomatic-configure -R -n queuename [ -s spooler ] [ -q ] foomatic-configure -Q [ -s spooler ] [ -n queuename ] [ -r ] foomatic-configure -P [ -s spooler ] [ -n queuename ] [ -d driver ] [ -p printer ] [ --ppd ppdfile ] [ index ] foomatic-configure -X -p printer | -d driver | -p printer -d driver foomatic-configure -O foomatic-configure -h foomatic-configure --help DESCRIPTION
foomatic-configure is a program to set up and configure print queues for every known spooler (CUPS, LPRng, LPD, GNUlpr, PPR, PDQ. CPS, no spooler) and every valid printer/driver combo in the Foomatic database or every PPD file coming with PostScript printers. As RIP filter (Raster Image Processor, translation from PostScript to the native language of the printer) always foomatic-rip(1) will be used, except for PPD files of PostScript printers under CUPS or PPR, they will be used without RIP filter. It also comprises half of a programatic API for user tools: you can learn and control everything about the static properties of print queues here. With the sister program foomatic-printjob(1), you can do everything related to the print queue's dynamic state: submit jobs, and query, cancel, reorder, and redirect them. Options -n queuename Configure this print queue -N Name/Description Use this proper human-readable name/description -L Location Short phrase describing this printer's location -c connection Printer is connected thusly (ex file:/dev/lp0) -d driver Foomatic database name for desired printer driver -p printer Foomatic id for printer --ppd ppdfile PPD file, for example the one supplied by the manufacturer of a PostScript printer -s spooler Explicit spooler type (cups, lpd, lprng, pdq, ppr, direct) -o option=value Set the default of option to value -o option Turn on option by default -D Set this queue as the default queue (just give -n queuename) -R Remove this whole queue entirely (just give -n queuename) -C [ sourcespooler ] sourcequeue Copy sourcequeue from sourcespooler (or the current one if sourcespooler is not given) into the queue given by -n queuename (of the current spooler). -Q Query existing configuration (gives XML summary) -r List also remotely defined queues (CUPS only) -P [ index ] Get Perl dump of current configuration (as a Perl array named QUEUES, the first index is index, or zero if index is not given) -O Print XML Overview of all known printer/drivers (this shows also the Foomatic IDs of the printers) -X Print XML data for -p printer and/or -d driver object -q Run quietly Commands No commands, just options SEE ALSO
foomatic-printjob(1), foomatic-rip(1) EXIT STATUS
foomatic-configure returns 0 if no errors occurred. AUTHOR
Manfred Wassmann <manolo@NCC-1701.B.Shuttle.de> for the foomatic project using comments from the source. BUGS
foomatic-configure currently cannot handle printcap files in the lprng style. As lprng can use BSD style printcaps this is not much of a problem, as long as the GUI based print manager lprngtool is not used. The difference between those formats is, that BSD style requires continuation lines in printer definitions to be ended with a colon and the newline character to be escaped with a backslash. Lprng has no such restriction. To use a printcap file generated or edited with lprngtool with foomatic-configure it is necessary to add : to the end of all but the last line of every printer definition, just as shown below: #comment # primary printer name lp #alternate names |lp2|lp3 |Example of a printer :sd=/usr/spool/LPD/lp :rw:lp=/dev/lp:mx#100 : must be converted to: #comment # primary printer name lp |lp2|lp3 |Example of a printer :sd=/usr/spool/LPD/lp: :rw:lp=/dev/lp:mx#100: This manpage may be out of date. Foomatic Project 2002-01-06 FOOMATIC-CONFIGURE(1)
All times are GMT -4. The time now is 05:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy