×
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.
Kirk,
Someone is going to have to write a custom program that backs out the changes. Since you have the before images this should not be too difficult.
The program can be an exit program on the RCVJRNE command, one that uses the QjoRetrieveJournalEntries or one that utilizes a DSPJRN output file.
In this program, for the date and time in question, spin through the Before journal receivers excluding the ones that were to be updated. For every other record take the JOESD information and overlay the existing record's information.
Make sense?
Thanks,
Gary
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins
Sent: Wednesday, October 08, 2014 1:58 AM
To: Midrange-L
Subject: Questions on journals
I have some really basic questions on using journals to recover from a bad SQL based update to a file. The SQL was to update a single field and a rather small number of records from what I was told, but updated several hundred thousand before it was stopped. So the file was journaled with Before and After images.
1st question I assume that what is journaled is the Entire Record not just what was changed ( say 1 field ), correct?
2nd Question Since the file was in active use and other jobs could have updated other fields of the modified records after the bad SQL was run I don't think we can just use RMVJRNCHG cmd to backup those SQL changes and then run APYJRNCHG from the SEQ directly following the the bad changes. If we use the APLYJRNCHG to a recorded we rolled back it will just put the bad data back if my assumption in #1 is correct?
Last question for now, What happens if there are triggers on this file if we were to use RMVJRNCHG cmd? How about APYJRNCMD?
Thanks
--
Kirk
--
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.
midrange.com
