|
That sounds like the best solution. 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.
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.