Restored Journal receivers that are deleted by system
Sir Tom: I somehow perceived that it's kinda related to restoring journal receivers so i decided to just attached my concern to Leah Rosin's "Restoring journal receivers". Well, going back to the issue, my question was " i’m able to restore previous journal receivers to the library but after a short time, the restored journal receivers are deleted by the system without my intervention. Why is this so?" And you replied by mentioning about MNGRCV(*SYSTEM) and DLTRCV(*YES). How do i determine whether the journal was created having what you mentioned as '...with MNGRCV (*SYSTEM) DLTRCV(*YES) specified.' I have an OUTFILE of DSPOBJD affecting all objects and libraries but when i made a query on the concerned journal (e.g. TELJRN) it just show the typical info but nothing related to MNGRCV and DLTRCV. I also relayed this concern of mine to one of our senior AS400 programmers and he said that MIMIX might have something to do to the deletion of restored journal receivers since the mentioned journal is one of the key journals in MIMIX w/c is installed in our as/400 box. My dilemma now is that my company has no more maintenance agreement with the vendor who installed mimix so i can't relay this to the mimix guy who i guess, can somehow clarify this issue and last i heard, the guy already resigned and migrated to the U.S. And do you know of any mimix forum where i can somehow raise this issue? MIMIX has an official website but you can't join their forum unless you have this maintenance agreement with them leaving me again facing a "blank wall". Again, thanks for your assistance.
Software/Hardware used:
i-Series model 820 OSV5R3M0
Software/Hardware used:
i-Series model 820 OSV5R3M0
ASKED:
October 7, 2011 11:52 AM
UPDATED:
March 31, 2012 12:29 AM
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
All Answer Wiki Contributors:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
How do i determine whether the journal was created having what you mentioned…
For those specific elements, the simplest method is probably the WRKJRNA (Work with Journal Attributes) command. Enter the command with library/journal name. The resulting display should show “Manage receivers” and “Delete receivers” about half way down the screen.
For the unexpected deletion of any object, the best place to start is the system audit journal, QAUDJRN. Auditing should be enabled through the various QAUD* system values, and system value QAUDLVL (or QAUDLVL2) should contain at least *DELETE as one of the ‘Auditing options’.
In this case, if this site is using MIMIX or any HA replication product, then that product could be configured for synchronization. If an object is deleted on the source system, the replication product may issue a matching deletion on the target system. The target system audit journal should show a ‘DO’ (Delete Object) audit entry that references a program or job from the replication product.
If there is no auditing, then it might be impossible to determine a cause.
Tom
On the Mimix management system, do a WRKJRNDFN. Find QAUDJRN and do an option 2 to change it on the system you’re going to do a restore on. Then change the Receiver delete management . . . *YES to *NO. Now Mimix will not delete the receivers automatically. When you are finished with the receivers you’ve reloaded, change the parameter back to *YES and Mimix will delete any that you’ve reloaded.
OldSysAdmin, i have this screen shot of WRKJRNDFN :
Work with Journal Definitions (WRKJRNDFN) Type choices, press Enter. Journal definition: Name . . . . . . . . . . . . . > QAUDJRN Name, generic*, *ALL... System . . . . . . . . . . . . > BINONDO Name, generic*, *ALL... Journal . . . . . . . . . . . . *ALL Name, generic*, *ALL Library . . . . . . . . . . . . *ALL Name, generic*, *ALL Receiver change management . . . *ALL *ALL, *NONE, *TIME, *SIZE... Receiver delete management . . . *ALL *ALL, *YES, *NO Remote journal link . . . . . . *ALL *ALL, *NONE, *SRC, *TGT... Output . . . . . . . . . . . . . * *, *PRINT, *OUTFILE Detail . . . . . . . . . . . . . *FULL *FULL, *BASIC User data . . . . . . . . . . . *CMD User data, *CMD, *NONE File to receive output . . . . . Name Library . . . . . . . . . . . *LIBL Name, *LIBL, *CURLIB Output member options: Member to receive output . . . *FIRST Name, *FIRST Replace or add records . . . . *REPLACE *REPLACE, *ADD Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keysYou mentioned in your reply about Option 2 “option 2 to change it on the system you’re going to do a restore on” .With the screen shot above, where do i apply the option 2 you were mentioning. I really need to restore these journal receivers because one of our senior programmer is doing an investigation trying to track down a previous bank transaction and the restoration of these journal receivers will greatly assist him in his task. The only obstacle in accomplishing this task is the MIMIX journal definition wherein it only has a 1 day retention period for journal receivers. I think this contributes to the deletion of restored previous journal receivers. If there’s a workaround on dealing with this mimix journal defintion so as to enable the restoration of previous journal receivers without exposing the replication function of mimix to any risk, then so much the better. Thanks for your shared thoughts.
WRKJRNDFN lists all your journals (if you have more than 1). The first column is labeled “Opt”. Enter a “2″ to change, then F10 for additional parameters, then page down to the second page. You should see a line “Receiver delete management . . . *YES *SAME, *YES, *NO”. Change the value from *YES to *NO and restore your journals receivers. No receivers will be deleted for this journal until you change it back to *YES again then all old ones will be deleted.
I also forgot, be sure to be on the management system (the backup) not your production system. You can not make changes on the production system.
OldSysAdmin, if i’m able to do the WRKJRNDFN parameter change in “Receiver Delete Management” from *YES to *NO in management system, can i perform restoration of journal receivers in Production Side because i have a tape backup of the journal receivers concerned and will there be any issue with the mimix replication if i restore this tape backup to the Production Library where it was created since from experience, journal receivers can not be restored to any library except to the library where it was created to. Will there be any “unexpected” negative impact on Mimix? I haven’t done this before so im asking it now so that i can have contingency action whenever there’s something “negative” that might happen. Thanks again for your shared thoughts.
Yes. Once the parameter is changed, simply restore the journal receivers desired on the production side. Mimix will not touch them until you change the parameter back to *YES. It’s really simply and there’s no chance for error or messing anything up. Yes they get restored back into the original library they were in.