This approach is fine so long as you stick to it, but you could end
up with an awful lot of individual journals. There might be some
complications around CRTDUPOBJ and save/restore between libraries (if
you do that) that might also complicate what journal things end up
going to - I have not thought this through yet.
If you are using the journals for a HA product this becomes terribly
difficult to manage as ideally you want to group common
libraries/resources together in the same journal (at least in my
On Fri, Feb 21, 2014 at 8:41 AM,<rob@xxxxxxxxx> wrote:
There are those who will argue that putting the journals and
receivers into the same library as their data also ensures this.
That's all well and good until you start getting cross library
transactions you want to use commitment control on.
I make a sale. I want it to update customer data in ARLIB. I also
want it to update salesperson data in CRMLIB. And I want to use
commitment control. If the operation fails it should roll back the
previously written data. Hard to do when your data resides in two
different journals and journal receivers.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact