× 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: Re: determining the # of recs in a file from a CL
  • From: DAsmussen <DAsmussen@xxxxxxx>
  • Date: Thu, 22 Jan 1998 18:17:02 EST
  • Organization: AOL (http://www.aol.com)

Dave,

In a message dated 98-01-21 21:53:12 EST, you write:

> How can I determine the # of records in a file, from within a CL?
>  
>  I'll use this # to determine if I should run a Client Access data transfer
>  via RUNRMTCMD.

You can use the RTVMBRD command to retrieve the number of current records
(keyword NBRCURRCD).  You didn't mention the application's function.  Unless
you are clearing the file after your process runs (which would be bad should
your process fail), I'd recommend checking change date (keyword CHGDATE) for
daily processes that involve transfers from other systems -- on the off chance
that today's file has the same number of records as yesterday's...

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@aol.com

"Be true to your teeth, or your teeth will be false to you." -- Dental Proverb
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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.