email@james-w-kilgore.com (James W Kilgore) on 10/24/99 10:17:27 AM

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Arlene M Soderlund/NFCNA.COM)
Subject:  Re: status of last chain to file



Max,

We also use the same indicator for all chains, so we created a field for
each file to store the CHAIN results.

So after your CHAIN do a move of *in90 to a single character field and
you can test that anywhere else in your program.


>
>              Hi,
>
>              I have a program that has 10 files in it. All chain's use
> indicator 90
>              in the no record indicator. So how can i find out if a file i
> am going
>              to update had the record found on the last chain operation?
>              Thanks for any information on this.
>
>              Max
>



Use the INFDS for the file !


FCT100M  IF  E           K        DISK         KINFDS SYSCON


I*
ISYSCON      DS
I*
I*  CT100M STATUS DATA STRUCTURE
I*
I                                     *STATUS  CONSTS


 C                     Z-ADD0         FOUND   50
 C                     Z-ADD12        NOTFND  50

 C*
 C*  RETRIEVE COMPANY NAME
 C*
 C           'COMNAM'  CHAINCT100M               4140
 C
 C           CONSTS    IFEQ FOUND


    .....  Of course other statuses like record lock must be added to defined
fields.    With only 99 indicators this is the way to go.





+---
| 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
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].