×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
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.
midrange.com
