sponsored links

Collapse

Announcement

Collapse
No announcement yet.

Journaling. Records added to file not showing in journal

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Journaling. Records added to file not showing in journal

    We have an order file where recently users have added records, but minutes later they disappear from the file. so we figure journaling will help us find the problem.

    I did not make note of the exact parameter to start the journaling, but I did set it to journal as much as possible. We do a sample check and we can see open/close, before/after, record creates/deletes. Journaling is great, we will figure this out! the file name in question is LIBSBL.


    So this morning, the problem occurs. The user enters records, the job copies those records to other files so we know they were really added. But the journal does not show any activity that matches her joblog for the time. She runs the add job at 9:10:03 but the journal only shows an open and close at 9:12:39 and 9:12:56. The job log shows no activity at this time. The journal does not show records added, just the open close. The times do not match.


    We have a scheduled job that runs every two minutes that copies the file LIBLSB to a work file. It ran at 9:10:50.

    The user started her program at 9:10:03, but did not end the add program until 9:25:21. The part where her job copies to a work file ran at 9:25:23 and we confirmed that this statement worked correctly:
    2000 - CPYF FROMFILE(*LIBL/LIBSBL) TOFILE(AS400LIB/BOLCOPY) MBROPT(*REPLACE) CRTFILE(*NO) INCCHAR(*FLD 1 *EQ ' Y85582')

    The scheduled job that ran at 9:10 does this:
    CPYF FROMFILE(QS36F/LIBSBL) TOFILE(SBLP) MBROPT(*REPLACE) CRTFILE(*YES) INCREL((*IF CRTYP *EQ 1)) FMTOPT(*NOCHK)

    So it seems to us this copy is somehow affecting what is written to the journal. We thought you couldn't beat journaling, but somehow we are.


    To make it interesting, the user's update program is S36 rpg ii and called from OCL. the file LIBSBL has records that contain decimal data errrors since the original design had two record types. Journaling records all the activity from this old rpg ii program normally at all other times. It does not care about decimal data errors or invalid data in the file, it shows us all activity. Except between 9:10:03 and 9:25:21 this morning.






  • #2
    The error happened again with the same results. More digging into job logs makes us think an OVRDBF to qtemp is not being deleted. Which would explain why we can't see anything in the journal. The CPYF and everything appears to be working correctly, since they arelikely using the qtemp version.
    How does that saying go? When you have eliminated everything, whatever remains, however improbable, must be the cause of the problem.

    Comment

    Working...
    X