Re: Audit Journal Entry -- MIDRANGE-L

It is refreshing to see an IBM'er take responsibility;
It's a much better response than JDE or Oracle would give.

Here are a few that I have gotten from the JDE/Peoplesoft/Oracle customersupport hot line over the years...(I have NEVER gotten a straight answerfrom them, by the way).


1)  It is "Working As Designed"

2)  You don't understand how the function is supposed to work

3) Did you modify the program? If so, then YOU obviously introduced theerror...

4) Oh, yeah...we know about the problem, but it won't be fixed until thenext release is issued. In the meantime, we have a "Paper Fix" that we cansend you so you can modify the offending program yourself to fix theproblem, but we can't guarantee that it will fix your problem nor will wetake responsibility for any problems that it might cause...


Regards,
Steve

----- Original Message -----From: <ChadB@xxxxxxxxxxxxxxxxxxxx>

To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, September 27, 2006 7:21 AM
Subject: RE: Audit Journal Entry

Now that's an authoritative response!

Thanks Pat.

            Patrick Botz
            <botz@xxxxxxxxxx>
            Sent by:                                                   To
            midrange-l-bounce         Midrange Systems Technical
            s@xxxxxxxxxxxx            Discussion
                                      <midrange-l@xxxxxxxxxxxx>
                                                                       cc
            09/26/2006 11:16
            PM                                                    Subject
                                      RE: Audit Journal Entry

            Please respond to
            Midrange Systems
                Technical
               Discussion
            <midrange-l@midra
                nge.com>

The "GR" audit journal entries were added to the system as a way to solve a
development process problem.

Often the need for a new audit journal entry in the OS was not discovered
until too late in the development process to create them in time for that
release.  In the -- now, long ago -- past, we would have to wait for the
next release to add the new audit journal entry.  This time delay was not
always acceptable.

So, to be able to add new crucial audit journal entry codes that were not
originally planned for, we created the concept of a "generic audit journal"
entry or the GR.  The GR entry is used for many different types of
unrelated entries.  The TYPE of the GR entry ("T" in this case) is supposed
to tell you exactly what a specific entry means.  The type also defines
what kind information is stored in the other entries of this particular
record.

Unfortunately, a quick check of the Audit Entry Layout appendix in the
Security Reference manual, seems to show that the information for the "T"
entry type for GR records is missing.  It was either inadvertently removed
or somehow never got updated.

Based on the information in a previous post of this topic, it seems that
this indicates something today with an FTP connection request.  I can't be
sure though.

As an aside, this "brilliant" idea happened to be mine and I was somehow
able to convince the necessary people that this was indeed a good idea.
After one or two releases, however, it became apparent that the idea may
not have been quite as brilliant as I thought it was. Mea culpa...

Patrick Botz
Senior Technical Staff Member
IBM Lab Services, Rochester
Security Architecture & Consulting, i5/OS Security Architect
(507) 253-0917, T/L 553-0917
CTC Fax # 507-253-2070
email: botz@xxxxxxxxxx

For more information on CTC, visit our website at
http://www.ibm.com/eserver/services
http://www.ibm.com/servers/eserver/services

--
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.

_____________________________________________________________________________

Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________

ForwardSourceID:NT00053756

--------------------------------------------------------------------------------

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglist

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.