Journalling – why the SAVCHGOBJ?

65 pts.
Tags:
AS/400
iSeries
Journal
journalling
Recovery
We need to turn on journalling to allow a backward recovery if a big batch job goes wrong. Do I still need to do the SAVCHGOBJ before starting the journalling in order for the restore to work or is that just for forward recovery? I still don't understand the need for it....

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • philpl1jb
    You're sequence leaves a gap.  Any changes after the save command and before the journalling starts will be lost. Start journalling   then SavChgObj  then run the job  That gives you two routes to recoverybacking out the changes you don't want  or restoring the file and applying the changes that you want.
    49,850 pointsBadges:
    report
  • TomLiotta
    You save an object in order to be able to restore the object. Saves work at an 'object' level. It not only includes (all) records at the time of the save, but also includes the record descriptions, ownership, authorities and full description of the object.   Journaling works on records, essentially saving single records at a time. It can allow both forward and backward recovery from a point in time. An additional important aspect is the ability to audit procedures. A journal record tells which user (ID), job and program made each change and when each change happened.   Saving an object is not required before journaling is started. It is, however, a very good idea. It's irrelevant whether it's with SAVCHGOBJ, SAVLIB, SAVOBJ or any other save method.   Although not required, coordinating a save of the object with the start of journaling can be very useful. Recovery from system failures or staff/human errors can be much easier if both are available. Errors can happen while running commands that change journal behavior.   Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following