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



Hi Rick,
        why not just junk QSYS/QSTRUP in total; retrieve the cl source,
review what you want to keep (copy/paste). I have run with a fully
custom-written mystrup for many years; each new version I check out the new
QSYS/QSTRUP to see what's been added, and maybe copy the new stuff into
mystrup. I always control the start of my writers with AJE's in the QSPL
subsystem.  The start of the QSPL subsystem is in mystrup.

Jeff Bull

-----Original Message-----
From: Rick Klopfer [mailto:rklopfer@daytonprogress.com]
Sent: 25 November 2002 15:18
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.&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;&nb
sp;&nbsp;&nbsp;
<BR>Email:&nbsp;&nbsp;&nbsp;&nbsp; <A
href="mailto:RKlopfer@daytonprogress.com";>RKlopfer@daytonprogress.com</A>&nb
sp;&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.


________________________________________________________________________
This e-mail has been scanned for all viruses by ITM. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe,
email marketing@itm-group.co.uk
ITM - Managing Communication and Information through technology
________________________________________________________________________


DISCLAIMER

Any opinions expressed in this email are those of the
individual and not necessarily the Company. This email
and any files transmitted with it, including replies and
forwarded copies (which may contain alterations)
subsequently transmitted from the Company, are
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the
person responsible for delivering to the intended recipient,
be advised that you have received this email in error and
 that any use is strictly prohibited.

If you have received this email in error please notify the IT
manager by telephone on +44 (0)870 871 2233 or via
email to Administrator@itm-group.co.uk, including a copy
of this message. Please then delete this email and
destroy any copies of it.

________________________________________________________________________
This e-mail has been scanned for all viruses by ITM. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe,
email marketing@itm-group.co.uk
ITM - Managing Communication and Information through technology
________________________________________________________________________


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.