All,

I'm just getting started with journaling. I have a history (deficiency?) of not being able to find what I want in the Infocenter. There is a ton of reference material in there on journaling, but not what I would call a programmer's guide or how-to. There is a getting started list, but it doesn't discuss the whys, only the whats. And the redbook is centered on the performance aspect.

1) Is there anyone out there who is journaling and does NOT have "HA Journal Performance" installed? (On V5R4 it's 5722-ss1 option 41.)

2) I'm looking for a detailed discussion of this: If I set a journal as MNGRCV(*SYSTEM) and DLTRCV(*YES), how specifically does the system determine when a journal receiver ("JR") can be deleted? Once the JR is saved somewhere? A successful save of each and every object being journaled?

3) Expansion of #2. What I have in mind is MNGRCV(*SYSTEM) and DLTRCV(*YES), and, a couple of times during the day, save journal receivers to tape. The journal and JR are in the same library and are the only objects in that library. (Should they be in separate libs?) The ideal would be at a predetermined time do a SAVLIB of the JR library which would automajically save any detached receivers and then the system "would just know" that JR can be deleted. Should the *JRN object be saved then too? Shouldn't I be doing a CHGJRN just prior to saving the JR? How does one determine the name of a just detached JR? How does one determine the name of a detached JR if the system did a CHGJRN 45 minutes earlier?

We do a save of the entire system every day at 12:01am. What I guess I'm looking for is best practices of keeping the database changes (and eventually IFS) saved via journaling until the next save. There is no DR or HA site. I do store tapes offsite as well as onsite.

Thanks.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.