RE: System value QSTRPRTWTR

[rob@xxxxxxxxx]

Regarding third paragraph.  Darn good point there.  And after I saw that 
program QSTRUP does have USEADPAUT I wondered.  Only thing I can say in my 
defense is what if IBM drops that in a future release?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Wilt, Charles" <CWilt@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/19/2005 02:52 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: System value QSTRPRTWTR






I don't know about that.  Take a lesson from history....how many used to 
have the STRTCPSRV and STRHOSTSRV commands in your startup, certainly some 
conflict when IBM added support to auto-start them.

I've got the same mind-set as Evan, QSTRUP is simply another required prep 
doc.

In any event, if you want to do it your way, why do you need go thru the 
printer writer start in you program anyway?  If the QSTRUPPGM system value 
points to your program, and the first thing your program does is call 
QSYS/QSTRUP, and your program is set with GODLIKE as the owner and 
USRPRF(*OWNER).  Then when QSTRUP goes to start the writers, it will have 
all the authority it needs since QSTRUP has USEADPAUT(*YES).


Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
> Sent: Wednesday, January 19, 2005 2:22 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: System value QSTRPRTWTR
> 
> 
> The rest of my steps in my startup are rather simplistic.  I 
> don't see how 
> it would conflict.  Well, maybe if I don't figure out how they reset 
> QSTRPRTWTR back.  :-)
> Playing the odds, I find it more likely that IBM will add 
> something that 
> will cause you some downtime to resolve, or maybe even an IPL, 
> than IBM will add something that will conflict with my QSTRUP.
> 
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
> 
> 
> Evan Harris <spanner@xxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/19/2005 01:59 PM
> 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 Rob
> 
> without reconciling the two programs how will you ever know 
> whether IBM 
> have maybe added something into "their" QSTRUP that will 
> conflict with 
> what 
> you do in "your" QSTRUP and thus create the downtime and 
> frustration you 
> are trying to avoid anyway.
> 
> I do pretty much the same thing as Charles, and my view is 
> that reading 
> the 
> IBM supplied STRUP is akin to reading the other release 
> preparation docs. 
> I 
> have always considered the IBM supplied program to be a 
> sample program 
> rather than something that was truly production ready.
> 
> Regards
> Evan Harris
> 
> 
> >But see, I don't want to have to reconcile any change, 
> regardless of how
> >minor.  Not only that, but the change may cost you some downtime and
> >frustration, and even an extra IPL or two, until you 
> remember to modify
> >your startup to take the new enhancements into your startup. 
>  I already
> >have enough fun everytime I upgrade.  I like my method.
> >
> >Rob Berendt
> >--
> 
> -- 
> 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.