RE: Restoring Journaled Objects

My experience has been:

Note: Taken from the BU Recovery Guide V5

Journaled Object Considerations

For an object that is restored and associated with an inactive local
journal, the
restore of the object completes normally. However, an informational message
is
sent to the joblog. This message indicates that journaling could not be
started for
the object. Existing restore logic will send a final escape message for the
restore
operation.

For an object that is being restored-over and it is currently journaled to
an inactive
local journal, the restore for the object is prevented. A diagnostic message
is left in
the joblog. The diagnostic message is followed by the appropriate message
that is
currently sent by restore. The current message indicates that the restore
for the
particular object failed.

The system will send a diagnostic message for any object in which the
'object
restored' journal entry could not be sent due to a problem with the journal
or
attached journal receiver. The system always attempts to start journaling
for an
object that was journaled at save time to the same named journal, in the
same
named library, during a restore operation. This is still true, and there are
no
processing changes to note if a local journal is found by the restore
processing.

However, if a remote journal is found by the restore processing, the restore
completes successfully, but journaling is not started for the restored
object. A
diagnostic message is sent that indicates that a remote journal was found by
the
restore processing. This message is followed by the message that is already
sent
that indicates journaling was not started.

Kenneth

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Ken Slaugh
Sent: Monday, August 15, 2005 3:41 PM
To: Midrange Systems Technical Discussion
Subject: Restoring Journaled Objects



Restoring journaled objects:

        A customer restored objects to a new library to create a set of
'test' files. The problem is that the files in the saved library were
attached to a journal. This resulted in the 'test' files being attached
to the journal as well. This does seem to be a great feature of OS/400
but, in my opinion, should be a conditional feature.

        Does anyone have a solution to this issue? Of course, running
the ENDJRNPF for each object is certainly an option but it would be
better to avoid the attachment of the test files in the first place.

        TIA,

Ken Slaugh (707) 795-1512 x118 
Chouinard & Myhre, Inc. 
http://www.cm-inc.com/ 

DISCLAIMER: The information contained in this e-mail may be confidential
and is intended solely for the use of the addressee.  Access, copying or
re-use of the e-mail or any information contained therein by any other
person is not authorized.  If you are not the intended recipient, please
notify us immediately by returning the e-mail to the originator and
destroying all unauthorized copies.