× 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,

Question 1: Yes, the entire record image is saved, both before and after
Question 2: The RMVJRNCHG command does allow you to filter only the changes performed by one job:

Remove Journaled Changes (RMVJRNCHG)

Type choices, press Enter.

Journal . . . . . . . . . . . . Name
Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
Journaled file identification:
Journaled physical file . . . Name, *ALL
Library . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
Member . . . . . . . . . . . . *ALL Name, *ALL, *FIRST
+ for more values
Objects:
Object . . . . . . . . . . . . Name, *ALL
Library . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB
Object type . . . . . . . . . *FILE, *DTAARA
Member, if data base file . . *ALL Name, *ALL, *FIRST
Range of journal receivers:
Starting journal receiver . . *CURRENT Name, *CURRENT, *LASTSAVE
Library . . . . . . . . . . Name, *LIBL, *CURLIB
Ending journal receiver . . . Name
Library . . . . . . . . . . Name, *LIBL, *CURLIB
Starting large sequence number *LAST
Ending large sequence number . . *FIRST
*** Fully qualified job name . . . . Name ***
*** User . . . . . . . . . . . . . Name ***
*** Number . . . . . . . . . . . . 000000-999999 ***
Commitment boundary . . . . . . *YES *YES, *NO
Option . . . . . . . . . . . . . *NONE *NONE, *IGNINQMSG
Object error option . . . . . . *CONTINUE *CONTINUE, *END
Output . . . . . . . . . . . . . *NONE *NONE, *OUTFILE

This may allow you to rollback just the records altered by that job. Then you can correct your program and update again.

Question 3: I have no experience with triggers so I cannot answer this question.

Marvin

==================================================

message: 1
date: Wed, 8 Oct 2014 01:57:42 -0700
from: Kirk Goins <kirkgoins@xxxxxxxxx>
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
Notice: This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. This message may also contain Protected Health Information (PHI) and must be treated confidentially and handled in accordance with HIPAA and other federal and state privacy laws. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately and delete this e-mail (and any accompanying attachments).

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.