×
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.
Replying to my own message to perhaps clarify the discussion. Here's
what I found.
I created a QDFTJRN data area in the target test library. The important
value is "*RSTOVRJRN" which will "Override the saved object's journal
and start journaling to the journal name in this QDFTJRN data area when
the object is restored into the library"
I opted to start journaling to a journal that I created just for the
test library. If I used a journal that didn't exist, then the objects
were not journaled, so this is also an option. (Using lower case for
the journal name has the same effect.)
A snippet of the code:
/*=== Force journaling to the test journal */
CRTDTAARA DTAARA(&TOLIB/QDFTJRN) TYPE(*CHAR) LEN(80)
CHGDTAARA DTAARA(&TOLIB/QDFTJRN (1 10)) VALUE(&TOLIB)
CHGDTAARA DTAARA(&TOLIB/QDFTJRN (11 10)) VALUE(TSTJRN)
CHGDTAARA DTAARA(&TOLIB/QDFTJRN (21 10)) VALUE(*ALL)
CHGDTAARA DTAARA(&TOLIB/QDFTJRN (31 10)) +
VALUE(*RSTOVRJRN)
/*=== Restore the objects to the test library */
RSTLIB SAVLIB(&FRMLIB) DEV(*SAVF) +
SAVF(QTEMP/&FRMLIB) RSTLIB(&TOLIB) +
OMITOBJ((&FRMLIB/QDFTJRN))
Sam
On 11/2/2011 8:55 PM, Sam_L wrote:
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.
midrange.com
