|
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
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.