Re: Change Management

P.S. Use of *PUBLIC *EXCLUDE and adopted authority goes back to the release of MAPICS/38 in 1980 or '81. That was the reason so many sites either gave their users *ALLOBJ or made AMAPICS a group profile, as a shortcut to allow access to MAPICS files without going through MAPICS. It was never a good practice in my opinion, but a lot of people did it.

Dave Shaw
MAPICS-L moderator

----- Original Message ----- From: "Dave Shaw" <daveshaw@xxxxxxxxxxxxx>
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Sent: Thursday, July 24, 2008 10:35 AM
Subject: Re: [MAPICS-L] Change Management

Greg,

It's been a long time since I last did a scratch install - I can't remember
if it was XA release 1 or DB mod 4. In any event, it was *PUBLIC *EXCLUDE
then. Perhaps they changed it after that, although if they did, I
personally think it was a bad decision. Did they also drop the use of
adoptive authority? That's the only way I can think of that would cause it
to break.

Dave Shaw
MAPICS-L moderator

----- Original Message ----- From: "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx>
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Sent: Thursday, July 24, 2008 10:23 AM
Subject: Re: [MAPICS-L] Change Management

Dave - I think you may be wrong about *PUBLIC *EXCLUDE.

At least on an old version...
My MAPICS system is at XA Release 4 and it is all *PUBLIC *CHANGE.
When we started working on SOX we tried changing it to *EXCLUDE.....
MAPICS would not work at all.