On 30-Jun-2014 16:26 -0500, Keith McCully wrote:
On 29 June 2014 22:16, Mark S Waterbury wrote:
As the article says, there doesn't seem to be a direct way of doing
this. Their method involves programming and handling one file at a
time. Whereas, I wanted to apply the journal changes for one specific
batch job involving up to 30 files to the same set of files in a
different library. <<SNIP>>
A different system, LPAR, or iASP would allow restoring the original
journaled files with the same Journal Identifier (JID) [rather than
having _otherwise_ seemingly equivalent copies of those files in another
library on the same storage partition], thus allowing the Apply
Journaled Changes (APYJRNCHG) to operate against those files.
_What happens when you restore journaled objects_
_to a different library or directory_
"The system assigns a unique internal journal identifier (JID) to every
object that is journaled.
If you restore a journaled object to a library or directory other than
the original library or directory, and the object still exists on the
system and continues to be journaled to the same journal, the JID of the
restored object is changed. Message CPF70CB — "Journal identifier &2 is
currently in use" is sent to the job log to confirm the changed JID of
the restored object.
All the journal entries associated with the media copy of the object
have the original JID. You cannot apply these journal entries to the
object that was restored to a different library or directory because it
has a different JID. For this reason, you should avoid restoring a
journaled object to a different library or directory.