Re: DSPJRN date/time reliability

["Monnier, Gary" <Gary.Monnier@xxxxxxxxx>]

Joel,

Did the journal receiver names roll over?  Did the receiver names start back at 0 or 1?

Sent from my iPhone

On Aug 1, 2013, at 3:02 PM, "Stone, Joel" <Joel.Stone@xxxxxxxxxx> wrote:

> So I have changed my theory concerning how we missed journal entries.
>
> (BTW JRNCACHE is set to *NO.)
>
> We DSPJRN all journal entries for 20 files of interest to an outfile for a specific time window, about 24 hours.  (except Monday even, which has a time window that begins Friday eve).
>
> On Monday eve, we ran DSPJRN to select journal entries from Fri eve until Monday eve.
>
> We only write out records to a work file it fields of interest CHANGE in a record.  For example, if a customer CITY changes from the UB to UP record, I write a record.  
>
> It appears that the Friday evening UB records were NOT seen by the DSPJRN command.  This caused no field changes to be detected since the BEFORE images were missed for some RRN's.  There was an IPL early Saturday morning around 5 am.
>
> Could an IPL disrupt the DSPJRN from retrieving journal entries?
>
> Here is the command:
>
> DSPJRN     JRN(&libJRN/JRNLCMIS) +               
>         FILE((&libCMIS/filenames     *first)  +    
> RCVRNG(*CURCHAIN) +                          
> FROMTIME(&FRM_DT &FRM_TM) +                  
> TOTIME(  &TO_DT  &TO_TM)                  +  
> OUTPUT(*OUTFILE) +                           
> ENTTYP(*RCD)     +                           
> OUTFILE(QTEMP/JRNFLALL) ENTDTALEN(1000)      
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
> Sent: Thursday, August 01, 2013 2:43 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: DSPJRN date/time reliability
>
> We have a production CL pgm run each evening after the EOD jobs which DSPJRN to an outfile for analysis.
>
> We use DSPJRN FROMTIME(20130712 194218) TOTIME(20130715 194700) with other parms to an outfile.
>
>
>
> DSPJRN apparently failed to select a handful of journal entries which were written (JODATE & JOTIME) at exactly 20130715 193856.
>
> This is suspiciously close to the end of the time window 19:47:00 - it is 8 minutes from the end of the time window.
>
> Another clue:  we MIMIX these journal entries to a backup box.  I ran the DSPJRN with the same time window against the backup box, and the journal entries DO exist properly.  The ONLY source for these backup box journal entries is the production box journal.
>
>
>
> Any idea what is occurring here?  Can a journal entry be prepared in a buffer with the curr time and written to the actual journal several minutes later?  Then the journal record would fall outside BOTH of my time windows?
>
> Should I be selecting journal records using the starting and ending large sequence number (FROMENTLRG & TOENTLRG) for just this reason?
>
> What would cause journal records to be time-stamped but delay their writing to the journal file?  Commitment control?  Something else?
>
> Could it be some other issue that I am missing journal records?
>
> PS I cant see the production journal entries as they are too old now and are gone from the prod box (although they are still available on the backup box).
>
> Thanks
>
>
>
> ______________________________________________________________________
> This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> ________________________________________________________________________
> This inbound email has been scanned for all viruses by the MessageLabs SkyScan
> service. 
> ________________________________________________________________________
>
> ______________________________________________________________________
> This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.