Re: RSTLIB restarts Journaling. Why?

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi Sam

Doing a DSPFD will show the name of the journal that the file was lat
journalled to and whether journalling is active or not, so it would
seem that the journal information is part of the object. It makes
sense to me that if the object was journalled and you restore it then
you would probably want to continue journalling it; thus the default
behaviour that makes sens to me:
when restoring an object, if the journal the object is journaled to
exists, then journalling is restarted as part of the restore process.

You can specify for a different behaviour to take place by setting the
*RSTOVRJRN action in the QDFTJRN data area in the library being
restored. I've used this in the past to change the journal that files
being restored were journalled to.

It occurs to me that you might be able to specify a non-existent
journal in this data area which combined with the *RSTOVRJRN parameter
might cause your objects not to be journalled. You would need to omit
the QDFTJRN data area in the save and ensure that the data area exists
in the library you are restoring to.

More details about the QDFTJRN data area and  how to manipulate it can
be found here:
http://www.redbooks.ibm.com/abstracts/tips0604.html

Hope this helps you out.

On Fri, Nov 4, 2011 at 1:37 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:
> Clearly the original journal is know.  But if I restore to a *different*
> library, it does not seem to make sense to automatically start
> journaling especially to the *same* journal.  This seems like an
> unwarranted assumption *if* there is no way to override it.
>
> So I remain confused...
>
> Sam