|
You should have some lines in your QSTRUP like this:
QSYS/RTVSYSVAL SYSVAL(QSTRPRTWTR) RTNVAR(&STRWTRS)
IF COND(&STRWTRS = '0') THEN(GOTO CMDLBL(NOWTRS))
CALL PGM(QSYS/QWCSWTRS)
MONMSG MSGID(CPF0000)
NOWTRS:
That program, QWCSWTRS should be rockin' through all your printer device
configurations looking for ones that are set for ONLINE *YES and starting
them up. If there's a problem, it should be in the job log of your QSTRUP
job.
Note that TCP/IP starts up asynchronously in the QSTRUP. We've had some
problems with remote writers starting because TCP/IP wasn't fully
operational by the time QSTRUP hit the print writer startup. Not a big
deal, just re-arrange your QSTRUP or even put a WAIT in it.
Dan
rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/17/2005 10:48 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: What starts printer writers?
I figured that out and, yes it is set for online *yes
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"Bryon Cook" <bryonc@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/17/2005 11:39 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: What starts printer writers?
Sorry I left out part of this:
If you do a (WRKCFGSTS *DEV P01A01) on the 570 is it set for online at IPL
*YES?
Then take option 8, then option 5, page down until you see the online at
IPL
value. You can change it by using option 2 instead of option 5.
Sorry for the confusion!
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 17, 2005 11:30 AM
To: midrange-l@xxxxxxxxxxxx
Subject: What starts printer writers?
Trying to figure out what starts printer writers.
Significant situational facts:
Two i5's. Both running V5R3 and comparable ptf levels.
CHGIPLA on both machines both have STRPRTWTR(*YES)
DSPSYSVAL QSTRPRTWTR on both machines is set to 1=Start
DSPSYSVAL QSTRUPPGM on both machines point to QSYS/QSTRUP.
DSPPGM QSYS/QSTRUP on both machines looks like:
Program creation date/time . . . . . . . . . . . : 12/04/03 12:50:07
Type of program . . . . . . . . . . . . . . . . : OPM
Source file . . . . . . . . . . . . . . . . . . : S000039122
Library . . . . . . . . . . . . . . . . . . . : $BLDSS1
Source member . . . . . . . . . . . . . . . . . : S000039122
Source file change date/time . . . . . . . . . . : 11/30/03 20:06:43
There is a writer P01A01 on both machines.
Doing a DSPLOG PERIOD((0915 011505)) JOB(P01A01) where the time and date
is based on the start time/date of subsystem QCTL shows thus on our 520:
Job 494913/QSPLJOB/P01A01 started on 01/15/05 at 09:17:06
Nothing in it's joblog indicates where it was spawned from.
Doing a DSPLOG PERIOD((1900 011505)) JOB(P01A01) where the time and date
is based on the start time/date of subsystem QCTL shows thus on our 570:
(nothing until the writer was manually started this morning)
****************************************************************************
*************************
Why is it started on the 520 and not on the 570? Why did it not even
attempt to start in on the 570?
****************************************************************************
*************************
DSPSBSD SBSD(QSPL)
All options are identical on both machines.
DSPJOBD JOBD(QGPL/QSPLSTRWTR)
All options are identical on both machines.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.