× 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: Simple Subfile question
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Thu, 5 Apr 2001 15:31:37 -0500 (CDT)



On Thu, 5 Apr 2001, Jim Langston wrote:

> Thanks for all the tips, I've changed the indicators to be able to 
> do the SFLDSP separately and it works like a champ.

Hmmm... hope it works better than Mike Tyson!

> Now I'm trying to implement the error message, and so I went into the
> control record and made an output field called DFERRM which I plan on
> loading with an error message and turning on the appropriate indicator
> (57) when I want to display an error.  The only problem is, it won't 
> compile.
> 
> * CPD7812      30        1      Message . . . . :   Subfile control record 
>overlaps subfile record. 
> 

The way I usually get around this is I create a 3rd record format called
the "footer" record format.    I put the OVERLAY keyword on my SFLCTL 
format, then in the RPG code I do:

WRITE FOOTER
EXFMT SFLCTL

I don't know if theres a better technique, but thats the one that I use :)



+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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-Ups:
Replies:

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.