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



Got this question about a system value and wasn't getting a response to a 
thread on the security list.  Since it started wavering off to system 
values I thought I'd cross post it here.

I will have my own QSTRUP call the one in QSYS first.  Then it will 
execute it's thing, but with adopted authority.  This way I will get any 
new updates that IBM decides to add in QSYS/QSTRUP, and, if I put on a new 
release I don't have to worry about changing any job descriptions, 
changing the authority on QSYS/QSTRUP, etc.

I have one question about this.  I planned on using the technique that IBM 

uses in their QSTRUP to start writers.
     QSYS/RTVSYSVAL SYSVAL(QSTRPRTWTR) RTNVAR(&STRWTRS)
     IF COND(&STRWTRS = '0') THEN(GOTO CMDLBL(NOWTRS))
     CALL PGM(QSYS/QWCSWTRS)
     MONMSG MSGID(CPF0000)
NOWTRS:

So my code is a copy of the above, preceded by CALL QSYS/QSTRUP.

But if I previously called QSYS/QSTRUP I want to make sure that QSTRPRTWTR 

is not reset by that.  So, at what point does that get reset?  This is not 

a system value you can do CHGSYSVAL on.  Just want to make sure that if I 
am doing some special IPL that I don't start the printer writers 
unnecessarily.

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

Follow-Ups:

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.