× 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.



I'm just getting my feet wet with RPGLE and I have a design question.   I
have 3 workstation programs, pgma, pgmb, pgmc.  Each one processes one
screen of a display file.  Pgma is a subfile program where the user can
drill down and it calls pgmb.  Pgmb is a subfile program also where the
user can drill down and call pgmc.  Pgmc is not a subfile program.

Right now I have pgma as a regular rpg400 program doing a regular non-bound
call the pgmb.  Pgmb and pgmc are bound
together and pgmb does a function call to a procedure in pgmc.  All the
programs are in activation group QILE.

Also, I am calling pgma from a cl program which does a rclactgrp QILE after
the call to pgma so that all the files are closed.  Can't I do this from
the rpg program pgma?

Is there a better way to group the modules?

clpgm
     |
     |__pgma
     |           |
     |           |_pgmb
     |                  |
     |             pgmc
     |                   procedure(DspSalesData)
     |
     |__rclactgrp


tks!


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

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.