Eduard,

I like your technique and I will use it.  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:

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





"Eduard van den Braken" <Eduard.van.den.Braken@xxxxxxxxxxxxxx> 
Sent by: security400-bounces@xxxxxxxxxxxx
01/18/2005 03:38 AM
Please respond to
Security Administration on the AS400 / iSeries  <security400@xxxxxxxxxxxx>


To
"Security Administration on the AS400 / iSeries" 
<security400@xxxxxxxxxxxx>
cc

Subject
RE: [Security400] Anyone see a security issue with 
CHGJOBDJOBD(QSYS/QSTRUPJD) USER(GODLIKE)?






Think about this

Create a new STARTUP CL-program in QGPL or a Tools library.
Call the original QSTRUP in QSYS (thus al the release changes are
allways honored)
Put your extra actions in the STARTUP program.

This way after a release update all the new stuff does start, maybe you
will try to start something which is already started, but that should be
no problem


===================================================
Met vriendelijke groet,
Inter Access BV

Eduard van den Braken
Technisch Consultant iSeries

E-mail:  eduard.van.den.braken@xxxxxxxxxxxxxx


-----Oorspronkelijk bericht-----
Van: security400-bounces@xxxxxxxxxxxx
[mailto:security400-bounces@xxxxxxxxxxxx] Namens Mayer, Michael (CMA
Consulting)
Verzonden: maandag 17 januari 2005 19:37
Aan: 'Security Administration on the AS400 / iSeries'
Onderwerp: RE: [Security400] Anyone see a security issue with
CHGJOBDJOBD(QSYS/QSTRUPJD) USER(GODLIKE)?

Exactly why our startup program is also in QGPL!

-----Original Message-----
From: Sean Porterfield [mailto:sporter@xxxxxxxxxxxx] 
Sent: Monday, January 17, 2005 1:47 PM
To: Security Administration on the AS400 / iSeries
Subject: Re: [Security400] Anyone see a security issue with
CHGJOBDJOBD(QSYS/QSTRUPJD) USER(GODLIKE)?

Edwin Davidson wrote:

> We did this because last time we upgraded the OS, QSTRUP got replaced 
> with a new clean version.  We had
> to restore QSTRUP from backup.


That's why we put our QSTRUP in QGPL.  IBM gets to replace the QSYS 
version every upgrade, we check for changes that we need to make, our 
copy stays the same.
_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)
mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.
_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400)
mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.


_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400) 
mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.



This thread ...

Replies:

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

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