|
If your QSTRUP (maybe you should call it something else to reduce confusion) calls QSYS/QSTRUP, then you are covered. The CHGSYSVAL command does not support QSTRPRTWTR, and WRKSYSVAL when you reference QSTRPRTWTR with a '2' returns a CPF1030 message. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s+barsa2=attgloba Midrange Systems Technical l.net@xxxxxxxxxxx Discussion m <midrange-l@xxxxxxxxxxxx> cc 01/19/2005 10:58 Subject AM Re: System value QSTRPRTWTR Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I have no intention of changing QSTRPRTWTR. Is the IPL Options screen the only place where IBM changes it also? If so, then my problem is solved. I just wanted to make sure that the call to QWCSWTRS, or some other such task, doesn't reset the value. In my QSTRUP program the first executable is a CALL QSYS/QSTRUP. Then it does my stuff. That way I am covered if IBM ever adds stuff to it in a new release. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/19/2005 10:38 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: System value QSTRPRTWTR Hi, QSTRPRTWTR is a totally worthless system value. The only place you can change it is on the IPL Options screen, and the only place where IBM uses it is in QSTRUP. Rob, you can change your own QSTRUP program, but you need to be aware that IBM changes this program from release to release, and it's important to examine the changes. IBM does not particularly document these changes. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx midrange-l@xxxxxxxxxxxx cc 01/19/2005 10:11 Subject AM System value QSTRPRTWTR Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.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 -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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-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.
midrange.com
