• Subject: RE: Relative Record Number
  • From: Joe Teff <jteff19@xxxxxxx>
  • Date: Fri, 1 Jan 1999 15:57:36 -0600

> You forgot to code the "S" to make the data structures Program status data
> structures.
>     D DB1            SDS
>     D DB1RRN                397    400B 0
>     D DB2            SDS
>     D DB2RRN                397    400B 0

These are File Feedback data structures, not System data structures.
I would have to see the c-spec code before I could identify any problems.
I do not see anything wrong with the data structures though.

> I'm still stuck.  What is wrong with this code?  Why do I get a value of
> 000538976288 as the value in the fields DB1RRNand DB2RRN for every single
> record?  This is in a 7-record file. Both files are logicals.
>     FPHONEFL1  IF   E           K DISK    REMOTE INFDS(DB1)
>     F                                     RENAME(RPHONE:RPHONE1)
>     FPHONEFL2  IF   E           K DISK    REMOTE INFDS(DB2)
>     F                                     RENAME(RPHONE:RPHONE2)
>     D DB1             DS
>     D DB1RRN                397    400B 0
>     D DB2             DS
>     D DB2RRN                397    400B 0

If you e-mail me your entire RPG source, I will try to locate your problem. I
have used RRN processing many times in the past without any problems.
What is the remote keyword? I do not recognize that.

Joe Teff      <jteff19@idt.net>

| 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-2020 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].