On 01-Jul-2014 17:30 -0500, Keith McCully wrote:
<<SNIP>> So the only way to use APYJRNCHG directly on the target
library would be to copy both library and journal/receivers to a
different LPAR and apply there.
The journaled files would have to be /restored/; any other method of
/copy/ would not enable JID equivalence between the original database
file [member] and the /copy/. The restore of the files could be made to
a different *SYSBAS or a different Independent Auxiliary Storage Pool
(iASP) than whence they were saved; whether that is to a physically
different system or logically different partition is inconsequential.
The means of the journal (*JRN) getting there is not restricted to
restore, nor the means of the journal entries [getting deposited] in the
journal receivers. There is at least Remote Journal support, beyond
just save and restore of the journal receivers, for which there is no
requirement to save\restore the receivers.
A consideration would be to choose the correct starting sequence
number for STRJRNPF for the files once the library has been moved to
other LPAR before using APYJRNCHG.
Not sure of the mention of Start Journaling Physical File (STRJRNPF),
but the first Apply Journaled Changes (APYJRNCHG) would typically
specify the Last Save (*LASTSAVE) special value. If restoring the
Journal Receiver (*JRNRCV) objects, then IIRC the APYJRNCHG request
would be coded to specify the [set of the] journal receivers on the
Receiver Range (RCVRNG) parameter, such that the From Entry Large
(FROMENTLRG) specification for the starting Journal Sequence Number
would identified as the special value *FIRST; in that manner, there is
no need to know a specific Sequence Number.