Dear Bryan,
Stitch-in-Time overcomes the limitations of the CMJRNIMG command which can only look at actual journal entries. Stitch-in-Time software captures key data from journal entries and allows analysis on that data whenever you want (e.g. long after journal receivers have been detached and deleted).
CMPJRNIMG is record oriented while Stitch-in-Time is field oriented. Stitch-in-Time lets you search for the changes you are interested in by field(s), with very strong user-defined select/omit criteria. The product only reports those changes that fit the criteria. That seems like a better idea than wading through pages of cryptic data produced by CMJPRNIMG.
a.. To use CMPJRNIMG you must know where a field value is physically located in a record, while Stitch-in-Time allows you review data by field as defined in the database.
b.. CMPJRNIMG can only direct output to a printer file. Stitch-in-Time can direct to screen, printer, database file, PDF document, and can send the PDF to a list of e-mail addresses.
c.. Stitch-in-Time audit report definitions are saved and they can be scheduled for periodic execution.
d.. Stitch-in-Time audit report definitions allow the selection of records using variable values.
Happily, Stitch-on-Time requires no knowledge of journals or programming, can use pre-existing journals (or uses its own), and has robust integrated security which external and internal auditors have applauded at multiple customers.
The link:
http://www.unbeatenpathintl.com/stitch_in_time/source/1.html
Warmest personal regards,
Milt Habeck
Founder/CEO
Unbeaten Path International
North America (888) 874-8008
International +(262) 681-3151
+++++++ +++++++ +++++++ +++++++ +++++++ +++++++ +++++++
From: Burns, Bryan
To: Midrange Systems Technical Discussion
Sent: Wednesday, November 19, 2008 11:32 AM
Subject: RE: Identifying who deleted records - trigger programs
Milt,
What value does your solution add that can't be done
by journaling a file and doing a CMPJRNIMG?
Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois
+++++++ +++++++ +++++++ +++++++ +++++++ +++++++ +++++++
From: midrange-l-bounces@xxxxxxxxxxxx On Behalf Of Milt Habeck
Sent: Tuesday, November 18, 2008 12:27 PM
To: Midrange technical discussion group
Cc: Blake.Moorcroft@xxxxxxxxxx
Subject: Identifying who deleted records - trigger programs
Hi ...
Savvy auditors typically have another problem with triggers ... they can be turned
on and off "without a trace." If a change happens while the trigger is off, the change
is not observed.
We built an audit solution for the pharmaceutical industry; they obviously have an exceedingly
high need to "see" any changes to BOM records for ethical drugs. The product is called
Stitch-in-Time and it has been used to provide fail-safe observation of crucial iSeries
files in a wide range of enterprises ... even an oil company bought a copy.
When Stitch-in-Time is asked to observe a database, the product saves the image of the
record just before a change and what the record looks like after the change. Also saved:
who did it, precisely when that happened, and what tool was used to execute the change.
The audit features of the product are so strong that we've often used it as a debugger
to efficiently find the "smoking gun" causing a data integrity surprise in a production system.
Here's a link:
http://www.unbeatenpathintl.com/stitch_in_time/source/1.html
Warmest personal regards,
Milt Habeck
Founder/CEO
Unbeaten Path International
North America (888) 874-8008
International +(262) 681-3151
+++++++ +++++++ +++++++ +++++++ +++++++ +++++++ +++++++
From: Blake.Moorcroft@xxxxxxxxxx
Sent: Thursday, November 13, 2008 7:44 AM
To: RPG programming on the AS400 / iSeries
Subject: Identifying who deleted records - trigger programs
Hello all...
I'm wondering if anyone has ever run into this situation before. Any help would be appreciated.
A request has been made to track record activity on a file. Specifically, auditors are looking to see who is deleting or updating records and what changes are being made.
The option to use a file trigger has come up and would provide the option to evaluate changes for updated records. The issue that is being encountered is identifying what program or procedure caused the trigger to kick off, and more importantly, what user profile was associated to the program or procedure.
Have a good day.
Blake Moorcroft
Developer - Corporate
Russell A. Farrow Limited
midrange.com
