Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Automatically starting a remote writer at IPL
466 views
Skip to first unread message
dgust...@dnco.org
May 16, 2000, 3:00:00 AM5/16/00
to
I searched through the past posts about automatically starting a remote
writer at IPL and found some suggestions that I didnt in fact need to put
the commands in the STARTUP. I read that all i needed to do was change the
AUTOSTRWTR parameter in the OUTQ description to 1. Well, I looked at my
OUTQ description and sure enough, the AUTOSTRWTR param was set to 1 already.
Any idea why this is not auto starting my writer at IPL?
writer at IPL and found some suggestions that I didnt in fact need to put
the commands in the STARTUP. I read that all i needed to do was change the
AUTOSTRWTR parameter in the OUTQ description to 1. Well, I looked at my
OUTQ description and sure enough, the AUTOSTRWTR param was set to 1 already.
Any idea why this is not auto starting my writer at IPL?
Thanks,
--Dan
Rodney Johnson
May 17, 2000, 3:00:00 AM5/17/00
to
Dan, Remote writers are automatically started when the subsystem QSPL is
started (there is an auto start job entry defined to the subsystem). Only
those output queues with AUTOSTRWTR(1 or >) will be automatically started.
Take a look at the job QSTRRMTWTR. You may find out that the remote writer
name that would be used for your output queue matches the name of a printer
writer that is already started. By default, the remote writer name will be the
same name as the output queue. Another possibility, is that your output queue
is already in use by another writer (for example a printer writer). One
COMMON mistake, is to create a dummy printer device description (which varies
on at IPL...therefore make sure it is vary on at IPL NO) and make the printer
device's output queue a remote output queue. Now you may have a race
condition. Sometimes the remote writer may start first, and sometimes the
printer writer will (depends on your system performance/setup).
started (there is an auto start job entry defined to the subsystem). Only
those output queues with AUTOSTRWTR(1 or >) will be automatically started.
Take a look at the job QSTRRMTWTR. You may find out that the remote writer
name that would be used for your output queue matches the name of a printer
writer that is already started. By default, the remote writer name will be the
same name as the output queue. Another possibility, is that your output queue
is already in use by another writer (for example a printer writer). One
COMMON mistake, is to create a dummy printer device description (which varies
on at IPL...therefore make sure it is vary on at IPL NO) and make the printer
device's output queue a remote output queue. Now you may have a race
condition. Sometimes the remote writer may start first, and sometimes the
printer writer will (depends on your system performance/setup).
dgust...@dnco.org 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.
Mark Ford
May 17, 2000, 3:00:00 AM5/17/00
to
If these are remote output queues using IP, you will probably find the
remote writers are not starting because TCP/IP is not active when QSPL
starts. If this is the case you can change your system startup program
so that subsystem QSPL (and anything else TCP/IP dependant) starts
after TCP/IP (and after a delay of some sort preferably to allow
TCP/IP to initialise).
remote writers are not starting because TCP/IP is not active when QSPL
starts. If this is the case you can change your system startup program
so that subsystem QSPL (and anything else TCP/IP dependant) starts
after TCP/IP (and after a delay of some sort preferably to allow
TCP/IP to initialise).
Mark.
0 new messages