Re: RSTLIB restarts Journaling. Why?

[jim t <jim_t_59@xxxxxxxxx>]

The saved objects contain the knowledge that they are journalled and the journal name. The restore will always attempt to start journaling to the original journal again.

You aren't missing a parm for "don't journal". You have no choice.




--- On Thu, 11/3/11, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

> From: Sam_L <lennon_s_j@xxxxxxxxxxx>
> Subject: RSTLIB restarts Journaling.  Why?
> To: midrange-l@xxxxxxxxxxxx
> Received: Thursday, November 3, 2011, 7:25 AM
> Each night we run job TSTCRT to
> create a copy of production data for 
> testing, thus:
>
>    SAVLIB PRODLIB to QTEMP/SAVF
>    CLRLIB TESTLIB
>    RSTLIB from QTEMP/SAVF to TESTLIB,
> OMITOBJ(PRODLIB/QDFTJRN)
>
> Every morning I find that the objects in TESTLIB are
> journaled to the 
> production journal.  I don’t want that.
>
> DSPLIBD of both PRODLIB and TESTLIB show that neither
> library is 
> journaled.  We're on V6R1.
>
> QDFTJRN exists in PRODLIB and all objects are journaled.
> QDFTJRN does not exist in TESTLIB.  (Thought it once
> did.)
>
> We’re running Mimix and it uses remote journaling, but we
> don’t 
> replicate the TESTLIB library.
>
> The journal records for TESTLIB show that it is job TSTCRT
> that is 
> starting the journaling.
>
> Any thoughts on why journaling is starting?
>
> Thanks, Sam
>
> Maybe I should have the OMITOB(QDFTJRN) on the SAVLIB? Or
> there is some 
> obvious parm I’m missing that says “don’t
> journal”.
>
> -- 
> 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.