× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Retrieve log entry problems
  • From: Klein Ron <ron.klein@xxxxxxxxxx>
  • Date: Tue, 14 Nov 2000 16:12:20 -0600

Hi All,

During the logging process,  we are adding 3 records to the same file in 1
commitment cycle, which causes the log date and time of those journal
entries to be identical.  In order to produce a Log report,  we need to be
able to retrieve those entries using the (RTVJRNE) command.  The problem is
that we cannot distinguish between those 3 records using the date and time
parameters, we have to use the sequence number parameter to be able to
retrieve all three of those records.  We have tried to use the sequence
number parameters but it returns records that have nothing to do with the
sequence number we specified. 

If we specify a sequence number to start looking for, we get a sequence
anywhere within the journal.  However, the ending sequence that we get is
what we specify.

We are at V4R2.

Can anybody help, please.

Thanks
Ron

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.