RE: DFU on a production box ... was Which of the SYSIBM tables/views show the row count for

Hi Mike

I can tell you from personal experience at more than one site that once you
eliminate the "fixing" of data via any kind of back door all the other
"mysterious" data errors also start to vanish.

I have always liked the idea of fixing the data via the application whether
it is by using a one-shot program put through the necessary test process or
by simply deleting and re-keying the data as you suggested.

If anything is going to help them learnt to do it right, then fixing the
error will burn that lesson right in.

All that said, there are cases where you simply have to access the data
directly, but this should be the exception, not a convenience as it all too
often is.

In your fictitious example, does the head of AP raise a project and allocate
the necessary capital and costs for IT to do the project ? Get "datafixes"
in your budget as a line item and you will have a counter argument that "A/P
have used up their allocation of fixes for the year"..


Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
Sent: Tuesday, 11 March 2008 4:48 a.m.
To: 'Midrange Systems Technical Discussion'
Subject: RE: DFU on a production box ... was Which of the SYSIBM
tables/views show the row count for

Tommy, How do you handle data that needs "fixed" in production systems?
Let's say someone in the accounting office started a batch of AP invoices
and used a date of 03/10/2009 instead of 03/10/2008 and then entered 100
invoices under that batch which replicated the batch date into each invoice
record and tagged 100 Pos as being paid. The head of AP comes to you asking
you to fix the date. The alternative being to delete all 100 invoices and
untag the Pos the delete the batch and start all over, which would put them
a day behind schedule and the president of the company wanted someone paid
TODAY!!!!. Do you just say sorry, can't do that, not my problem? (Of course
the head of AP is going to report that IT was unwilling to help them.) With
the proper documentation from the proper people we would use
DFU/WRKDBF/STRSQL to fix this type of problem in just a few minutes knowing
that journaling is there to provide an electronic audit trail and we have
the documentation to back it u
p.