Seeing where a member is deleted in a journal

35 pts.
Tags:
AS/400 journaling
Journaling
Physical File
I have a situation where a member is being created in a physical file and is later being deleted by some process, human or automated. I'm trying to find what is removing the member and set up a journal to find the answer. I am able to readily see where the member is created, where records are added to it, but that seems to be the end of the trail. I've looked for 'DM' and 'MD' entry types (under the 'F' code) and have come up empty. I wrote a program to sift the journal for all occurrences of the member name in the member name field as well as starting in positions 21 and 31. When I'm doing the DSPJRN command, I specify the database file with *All in the member name. I also specify IRCHIDENT(*YES), OUTFILFMT(*TYPE3), ENTDTALEN(*CALC).

Answer Wiki

Thanks. We'll let you know when a new response is added.

When you set up the journal did you exclude deleted records? I know in my journals it will not show up in my query unless you specify “ignore decimal errors. Then it shows up really weird but you can tell what was deleting it.

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Tsettimo
    Thanks for the input, Ron. But I'm not sure what you're referring to. I don't see anything on either the CRTJRN or STRJRNPF commands where I would 'exclude deleted records.' Am I missing something? The only thing being omitted on the STRJRNPF command are *OPNCLO. I don't think that would affect reporting the removal of a member. Also, I'm coding in RPG Free and am not setting the compiler option to correct decimal data errors but I'm also not getting dumps when I run my sifting pgm. Finally, just to be clear, I'm looking for where the member is being deleted, not a record delete. I'm starting to think that maybe this information is only reported when you use some view other than *TYPE3....I'll check that next. I'm still flailing on this, folks, so any input is welcome and much appreciated.
    35 pointsBadges:
    report
  • Cwc
    Are you including just the after record image, or both before and after?
    4,290 pointsBadges:
    report
  • pdraebel
    A workaround could be to AUDIT the use of the RMVM command. See who or what uses it through Audit Journaling. Peter
    2,580 pointsBadges:
    report
  • pdraebel
    Code . . . . . . . . : F - Database file member operation Type . . . . . . . . : MD - Member deleted These should be in the Journal
    2,580 pointsBadges:
    report
  • pdraebel
    There is also a DM entry, that is the actual deletion of the member and the one that should contain the info you are looking for.
    2,580 pointsBadges:
    report
  • Tsettimo
    Cwc - Thanks for your response. I am capturing both before and after images. Pdraebel - Thanks for your response. I wrote originally that I looked for both DM and MD type entries (under the F code) and couldn't find them in the output. This seems highly weird which is what led me to thinking it could be visible under another type of view than *TYPE3. But I tried other views and still couldn't find the DM or MD. Even when I just added a member and then removed it manually. The suggestion about the RMVM is a good one. I set it up a temp version above the QSYS version (in the system liblist) yesterday to send me a message whenever it's used. Thanks again!
    35 pointsBadges:
    report
  • Tsettimo
    An update - I yanked the temp rmvm command realizing that if the execution of the qsys/rmvm command failed within my version of the rmvm command, the monmsg processing in whatever pgm is running the command won't work. Instead, I changed the QSYS version of the command to call a validity checking pgm to perform the processing I want. fyi...
    35 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following