Start *LAN printer at IPL
Christian Luebke
a network printer is configured with a remote outq. On IPL the printer
is varied on but not started. What can be done to automate the start
of the printer?
BTW, the printer is powered off during the night and the machine does
an IPL every morning when the printer is still powered off. There
should be any possibility to start the printer automatically when it's
powered on...
Bye, Christian
Rodney Johnson
configuration? There is no such thing as a combination of the two.
There are many customers who like to create a DUMMY printer device
description and make the output queue (of the printer device description)
a remote output queue. If the DUMMY device description is allowed to be
varied on, then there is going to be a race between the auto starting of
remote writers and auto starting of printers writers. Sometimes the
printer writer will get started first and sometimes the remote writer may
get started first. I understand the desire to be able to reference a
printer device for your spooled output (thus the DUMMY device
description), but this is usually a setup for failure, problems, and
usually a call to IBM service (you might have guess by now that this type
of setup is sort of a "sore spot" with me).
Both remote writers and printer writers can be automatically started
after IPL.
For printer writers, this is controlled by the system value QSTRPRTWTR
(usually set on the IPL options screen) and actually implemented via the
startup program QSTRUP in QSYS. The startup program will start any
printer writers whose device descriptions vary on successfully.
Remote writers are started automatically IF the AUTOSTRWTR parameter is
NOT *NONE when the subsystem QSPL is started.
The writers have to have a unique name, so if you have the situation
I mentioned earlier, you are only going to have one of them successfully
start (printer writer writer names default to the device description, and
remote writer writer names default to the output queue name...they would
both be the same in the scenario above).
Christian Luebke wrote:
--
Rodney A Johnson
Technical Team Lead for AS/400 Spool
Dept GJC
IBM Rochester, Minnesota
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, IBM. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
dgust...@dnco.org
remote writer start at IPL? Right now, I have an outq TAXCOLP3 and a
message queue TAXCOLP3 and a writer TAXCOLP3. The printer is set up to
print via IP. I must use the STRRMTWTR command after an IPL to start the
remote writer. The writer TAXCOLP3 never says it is started, always an end
status--but the printing works anyway. I was told that I needed to change
the device description to ONLINE AT IPL: NO so that the remote writer would
start at IPL. This still doesnt work. The OUTQ description says AUTOSTART
WRITERS: 1. Can you give me any suggestions? I would ideally like to keep
the DUMMY device, because of the benefit mentioned.
Thanks,
--Dan
Rodney Johnson <rjoh...@rchland.ibm.com> wrote in message
news:392BE5D6...@rchland.ibm.com...
Achim home
this problem is known if you are on R370 (AUTOSTRWTR won't work)
IBM had fixed this with a PTF.
Do you have R370 on your system ? if not, which release and cume is applied
?
Maybe I can help you further.
Bye
Achim
<dgust...@dnco.org> schrieb in im Newsbeitrag:
LMUW4.28509$T41.6...@newsread1.prod.itd.earthlink.net...
dgust...@dnco.org
top of the line, damn near brand new machine (less than a year old) so I
expect it is mostly up to date.
Thanks,
--Dan
Achim home <amoeh...@cw-net.de> wrote in message
news:8ghhpo$goq$1...@news.wwl.de...
Volker Bruns
don't really know if this is a good idea, but it's working ! What we do
is:
I created a file were i put the names of the printers i want to have
started. I only use TCP - LanDevices! Every 15 Mintues I write WRKWTR to
*print and copy the splf to a DBF. By reading this with query I separate
name and status of the printer with substr funktion. And when the printers
Name matches to the leading file and the status of the printer is end,
I'll have it started. To do this you'll need one or two small CL-Programs
and two queries. And you should have MSG CPA3387 automatically answered
with C (wrkrpyle) to have either status STR or END!
Not shure if this will help you!
Volker
Christian Luebke schrieb:
Rodney Johnson
multiple configurations setup to print to the same printer. Why go through all
the trouble of creating an IP printer device description and not use it? If
your printer supports PCL5e and bi-directional PJL, it makes no sense to use
the remote writer (unless you have a problem with how the AS/400 HP PJL driver
"shares" the printer...).
A number of customers like to create a "dummy" printer device description of
the *VRT type. Make sure that nothing is varying on your printer device
description (should be able to check the status after the IPL to determine
that). As to the remote writer, you are going to have to check the job log for
the job that automatically starts remote writers (QSTRRMTWTR). This may
require that you change the jobd QSPLSTRWTR in QGPL LOG(4 00 *SECLVL). The
joblog should give a reason why your remote writer was not started (mostly
likely due to the output queue was already started to a writer, or a writer by
that name was already running). If the remote writer actually started, then
you need to look for the writer's joblog to find out why it ended.
dgust...@dnco.org wrote:
> So, is it possible for me to have a DUMMY printer device, and still have the
> remote writer start at IPL? Right now, I have an outq TAXCOLP3 and a
> message queue TAXCOLP3 and a writer TAXCOLP3. The printer is set up to
> print via IP. I must use the STRRMTWTR command after an IPL to start the
> remote writer. The writer TAXCOLP3 never says it is started, always an end
> status--but the printing works anyway. I was told that I needed to change
> the device description to ONLINE AT IPL: NO so that the remote writer would
> start at IPL. This still doesnt work. The OUTQ description says AUTOSTART
> WRITERS: 1. Can you give me any suggestions? I would ideally like to keep
> the DUMMY device, because of the benefit mentioned.
>
> Thanks,
> --Dan
>
> > > Hi,
> > >
> > > a network printer is configured with a remote outq. On IPL the printer
> > > is varied on but not started. What can be done to automate the start
> > > of the printer?
> > >
> > > BTW, the printer is powered off during the night and the machine does
> > > an IPL every morning when the printer is still powered off. There
> > > should be any possibility to start the printer automatically when it's
> > > powered on...
> > >
> > > Bye, Christian
> >
dgust...@dnco.org
that I dont need to. What is the best way to set up an HP printer with a
jet direct card so that users can send things to a specific WRITER or an
OUTQ? I have an HPLJ6 in my office that I can use to play with before I go
and change any of the live printers used by others. Any info is greatly
appreciated.
Thanks,
--Dan
Rodney Johnson <rjoh...@rchland.ibm.com> wrote in message
news:392D29BE...@rchland.ibm.com...
Rodney Johnson
http://as400bks.rochester.ibm.com/). Chapter 11 is the one you would be
interested in (if I remember right...they changed the address of the book on me
and have not had time to figure out the new address).
some other configuration information you will find useful:
1. On the printer set the Idle Timeout to 3600 secs (or 0 (if allowed) to
disable) or some other value dependent on step 5 below.
The reason for this is so that the printer will not terminate the connection
with the AS/400.
A timeout from the printer will result in a terminating error and the file
will be set to HLD or RDY (if a file is printing); and the writer will end.
The equivalent timer for the Lexmark print servers is the End of Job Timeout.
It should be set to 0 (disabled).
The equivalent timer for the IBM network printers is the Port Timeout. I
believe it's maximum value is 300, and cannot be disabled.
2. On the printer, the processor timer (called job timeout or wait timeout)
should be disabled or set to maximum (usually 300 secs) since individual pages
may have a delay in transmitting to the printer due to transforming
considerations.
3. The recommended setting for Inactivity Timer should be set at some value
other than *NOMAX so that the
connection will be closed during periods of no activity.
4. The activation timer should be set to a value large enough to prevent
posting of intervention errors due to TCP/IP transmission delays and printer
processing delays. The default setting of 170 secs is usually large enough to
accomplish this unless you send large files to a printer with a slow processor
that has a lot of memory. Increasing the activation time will prevent unwanted
intervention errors but that time will have to pass before you will get an
desired intervention error. Note that intervention errors do not stop the
print process. If the Printer Error Message parameter in the Device
Description for the writer was set to *INQ, then the intervention will require
an operator input to retry or to cancel the writer. If the parameter was set
to *INFO, then the driver will continue to retry until the connection has been
established or the TCP/IP has closed the socket or, in the case of a slow
printer processor, the proper response is obtained which is either the printer
is online or that the printer has received all the data. If the connection was
eventually successful the intervention message will be attempted to be removed
from the message queue, and process will continue.
5. When the Idle Timeout on the printer (step 1 above) is set to some value
(hopefully large), the printer will close the socket if the printer hasn't
processed any communication from the host within the Idle Timeout limit. This
can happen if the printer has a large buffer, and it is filled with data to
print. To prevent this from happening, the TCP/IP Keep-Alive value on the
AS/400 (via the CHGTCPA command) should be set to a value less than the printer
Idle Timeout value. This will cause a poll to be sent to the printer before
the printer times out. We want this value to be as large as possible to
prevent unnecessary network traffic. The recommend value if step 1 is done
(the 3600 secs), is 50 minutes.
dgust...@dnco.org wrote:
> Ok, I am thinking that I should start all over. I am obviously doing things
> that I dont need to. What is the best way to set up an HP printer with a
> jet direct card so that users can send things to a specific WRITER or an
> OUTQ? I have an HPLJ6 in my office that I can use to play with before I go
> and change any of the live printers used by others. Any info is greatly
> appreciated.
>
> Thanks,
> --Dan
>
> Rodney Johnson <rjoh...@rchland.ibm.com> wrote in message
> news:392D29BE...@rchland.ibm.com...
--
Christian Luebke
the printer uses a DEVD with attrib PRTLAN, parameter Online at IPL
set to *YES, and an OUTQ (automatically created during CRTDEVPRT). As
I mentioned in my initial posting, the printer becomes varied on but
not started. Maybe this is due to the printer is powered off when the
machine tries to start it during IPL?
Some DEVD's parameters:
DEVCLS: *LAN
TYPE: 3812
MODEL: 1
LANATTACH: *LEXLINK
ADPTYP: *INTERNAL
PORT: 0
ATTACH: *DIRECT
ONLINE: *YES
ACTTMR: 170
INACTTMR: *SEC15
Btw, sysval QSTRPRTWTR is '1'. Where can I find the AUTOSTRWTR
parameter?
The IBM supplied QSTRUP was not changed.
Rodney Johnson
personel. You should contact your IBM service rep. This problem seems to be
"controlled" somewhat by the number of LEXLINK printer writers you have
starting all at once. Collect the joblogs of these failing writer jobs so
that IBM service has something to look at and verify the problem.
From your description, it sounds like every thing is set up correctly. The
AUTOSTRWTR parameter is in the output queue description (setable via
CRT/CHGOUTQ). It should have been initialized to 1 when you created your
printer device description. Currently AUTOSTRWTR is only honored via the
STRxxxWTR *ALL paths. The startup program was changed back in V3R1 to
nolonger use STRPRTWTR *ALL (because of changes as to when device
descriptions got varied on...was moved to just after the IPL)...
Christian Luebke wrote:
--