× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What you should be doing is retrieving the source of QSTRUP, and modifying
the retrieved source.  Then change the system value to call that program.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                      "Rick Klopfer"
                      <rklopfer@daytonpr        To:       
<midrange-l@midrange.com>
                      ogress.com>               cc:
                      Sent by:                  Subject:  QSTRUP
                      midrange-l-admin@m
                      idrange.com


                      11/25/2002 10:17
                      AM
                      Please respond to
                      midrange-l






--
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.&nbsp; Over the
years
we have modified it at each release/upgrade.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Here's what we want to do:</DIV>
<DIV>&nbsp;</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>&nbsp;</DIV>
<DIV>Now...herein lies the problem.&nbsp; One of the first things
QSYS/QSTRUP
does is call CALL QSYS/QWCSWTRS and starts all the writers.&nbsp; We have
several outq's that we <U>never</U> want&nbsp;a writer&nbsp;start.&nbsp; We
looked at those outq's configurations with CHGOUTQ and they do have
"Writers to
Autostart = 1".&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Simple question:&nbsp; If we change "Writers to Autostart" to&nbsp;
*NONE on
those particular outq's, can we safely expect that the writers will never
be
started by QSYS/QWCSWTRS??</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks!</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>***********************************************<BR>Rick Klopfer, CCP
CSP<BR>AS/400 Certified Specialist</DIV>
<DIV>&nbsp;</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>&nbsp;</DIV>
<DIV>Telno:&nbsp;&nbsp;&nbsp; 937.859.5111&nbsp;
ext.293&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;
<BR>Email:&nbsp;&nbsp;&nbsp;&nbsp; <A
href="mailto:RKlopfer@daytonprogress.com";>RKlopfer@daytonprogress.com</A>
&nbsp;&nbsp;
. <BR><A href="http://www.daytonprogress.com
">www.daytonprogress.com</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.