|
Wha'? Time to wake up? Oh, hi, guys! Well, lessee, working backward here - *CHANGE was the default on OS/400 V1, and the /38 was the equivalent, so yes, I'm pretty sure that that's correct, John. I don't think QCRTAUT showed up until sometime in V2, I'm sure it wasn't there when we brought in our first /400 at V1R2. If someone else remembers better, I'm willing to be corrected, though. I suspect that Joe was at a shop, like I was, where security was not an afterthought, and they locked down the files properly when they put them in production - when it's a routine, it's easy to forget. I remember being horrified when they announced the /400 and I found out what Levels 10 and 20 were - maybe they were necessary for marketing reasons, but they certainly weren't improvements in my mind. Dave Shaw Simpsonville, SC --- If you would like to participate in the MAPICS-L mailing list go to http://lists.midrange.com/cgi-bin/listinfo/mapics-l and follow the instructions. ----- Original Message ----- From: "John Earl" <johnearl@powertechgroup.com> > If memory serves me (and it often doesn't), on the S/38 all new > objects were added with *PUBLIC *CHANGE, and later in the S/38 release > or early in the /400 release we got the system value QCRTAUT authority > so that we could set the default for ourselves. > > But I'm not sure enough of this to swear to it.... Dave Shaw is > hanging around here... Dave do you remember? > > jte > > ----- Original Message ----- > From: Joe Giusto II (E-mail) <juicenetdps@crosswinds.net> > To: <security400@midrange.com> > Sent: Thursday, August 23, 2001 6:48 AM > Subject: RE: [Security400] Authority annoyances, continued... > > > > If memory serves me correctly, didn't the SYS38 default objects to > public > > exclude (or maybe it was just use)? I seem to remember always > having > > trouble with object authority when ever we changed employees. As > the new > > operator would run jobs during the first week or so, we would have > to keep > > granting object authority to files as programs blew up. This was of > course > > before we learned about the group profiles which eliminated that > need once > > implemented. We granted proper authority to the group profiles and > then > > just started adding profiles to the group when new person came.
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.