|
Some followup.
I reviewed the journal entry for the command IMPLOOKUP, and the value
for Entry Type is R. (N = Creation of new object, R = replacement of
existing object) The program logged as "creating" the command is
WVCPLNR. That is a CL program (menu driver), and only one line
references IMPLOOKUP:
0145.00 ? implookup
010219
How does prompting a command cause it to be "created" or "replaced"?
I'm not sure that excluding "replacement" entries from our audit process
would be wise. Checking to see how an Aldon-promoted object looks to the
journal.
--Loyd
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
lgoodbar@xxxxxxxxxxxxxx
Sent: Wednesday, December 10, 2008 8:25 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Audit journal create object entries question
We use the audit journal to capture object creation activity, journal
code T, entry type CO. Almost all new objects in the production
environment should be tied to a help desk or CMS ticket. The usual
exceptions are for dynamic report generators (such as MRC) that create
programs at run-time. We filter out obvious exceptions (system objects,
objects in IBM libraries, various IFS paths, etc.) and try to report
things that should have a documented change request.
Occasionally we will see entries for object creation that do not match
the object description. For example I have journal entry for command
object PROD_MOD/IMPLOOKUP, created by SHERMAN on 2008-11-14, 12:24:45.
When I look at the object description, it shows Creation date/time (MDY)
is 02/16/01 14:49:53. It does, however, have a change date of 11/14/08,
12:24:45. Last restored on 3/27/04. Why would changing an object cause a
create object journal entry?
Has anyone run into this situation before?
Thanks,
Loyd
--
Loyd Goodbar
Business Systems
BorgWarner Shared Services
662-473-5713
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.