|
Rick, If the writers in question have device descriptions, just set the *DEVD parameter for Online at IPL to *NO in each device description. They will not start at IPL time. For remote IP OUTQ's just make sure the Writers to autostart is set to 0. The writer startup via QSTRUP will not start a writer job if it is set to 0. I have several of these in place and it works fine. Regards, Mike Shaw -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com] On Behalf Of Rick Klopfer Sent: Monday, November 25, 2002 7:18 AM To: midrange-l@midrange.com Subject: QSTRUP -- We want to go back to using the default QSYS/QSTRUP. Over the years we have modified it at each release/upgrade. Here's what we want to do: Create OURSTRUP (Yep...we know to change the sysval QSTRUPPGM) First line would be CALL QSYS/QSTRUP Followed by our stuff... Now...herein lies the problem. One of the first things QSYS/QSTRUP does is call CALL QSYS/QWCSWTRS and starts all the writers. We have several outq's that we never want a writer start. We looked at those outq's configurations with CHGOUTQ and they do have "Writers to Autostart = 1". Simple question: If we change "Writers to Autostart" to *NONE on those particular outq's, can we safely expect that the writers will never be started by QSYS/QWCSWTRS?? Thanks! *********************************************** Rick Klopfer, CCP CSP AS/400 Certified Specialist Software Development and Support Information Technology Group Dayton Progress Corporation --A Federal Signal Company-- 500 Progress Drive Dayton, OH 45449 Telno: 937.859.5111 ext.293 Email: RKlopfer@daytonprogress.com . www.daytonprogress.com -- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD> <BODY style="MARGIN-TOP: 2px; FONT: 10pt Comic Sans MS; MARGIN-LEFT: 2px"> <DIV>We want to go back to using the default QSYS/QSTRUP. Over the years we have modified it at each release/upgrade.</DIV> <DIV> </DIV> <DIV>Here's what we want to do:</DIV> <DIV> </DIV> <DIV>Create OURSTRUP (Yep...we know to change the sysval QSTRUPPGM)</DIV> <DIV>First line would be CALL QSYS/QSTRUP</DIV> <DIV>Followed by our stuff...</DIV> <DIV> </DIV> <DIV>Now...herein lies the problem. One of the first things QSYS/QSTRUP does is call CALL QSYS/QWCSWTRS and starts all the writers. We have several outq's that we <U>never</U> want a writer start. We looked at those outq's configurations with CHGOUTQ and they do have "Writers to Autostart = 1". </DIV> <DIV> </DIV> <DIV>Simple question: If we change "Writers to Autostart" to *NONE on those particular outq's, can we safely expect that the writers will never be started by QSYS/QWCSWTRS??</DIV> <DIV> </DIV> <DIV>Thanks!</DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <DIV>***********************************************<BR>Rick Klopfer, CCP CSP<BR>AS/400 Certified Specialist</DIV> <DIV> </DIV> <DIV>Software Development and Support<BR>Information Technology Group<BR>Dayton Progress Corporation<BR>--A Federal Signal Company--<BR>500 Progress Drive<BR>Dayton, OH 45449</DIV> <DIV> </DIV> <DIV>Telno: 937.859.5111 ext.293   ; <BR>Email: <A href="mailto:RKlopfer@daytonprogress.com";>RKlopfer@daytonprogress.com</A > . <BR><A href="http://www.daytonprogress.com";>www.daytonprogress.com</A></DIV> <DIV> </DIV> <DIV> </DIV></BODY></HTML> _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.
midrange.com
