RE: Sub-Procedures -- RPG400-L

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

<snip>
Then what would the source type be?
</snip>

Whatever the type of the module is. RPGLE, SQLRPGLE, CLLE, C, etc.

Here is an example of a program that uses a CLLE, RPGLE, SQLRPGLE and C.
Not real but to show the concept.

EX0001 - Top Level to bind it together into a program.
EX0001_M01 - CLLE module.
EX0001_M02 - RPGLE module.
EX0001_M03 - SQLRPGLE module.
EX0001_M04 - C Module.

So the top level to bind it together is.

CRTPGM PGM(YourLib/EX0001)
MODULE(EX0001_M01 EX0001_M02 EX0001_M03 EX0001_M04)
TEXT('Example create')
ACTGRP(QILE)

A module is simply a way to group like code together. You can have any
number of modules that bind together to form or a program or service
program.

RPGLE, SQLRPGLE, C modules can have any number of procedures. CLLE
module can only have one.

An example I use a lot is I have a standard error handler which has
three modules.

XVERRH_M01 - Throw functions. RPGLE
XVERRH_M02 - Message storage functions. RPGLE
XVERRH_M03 - Condition Handling functions. RPGLE

This all gets bound together to form Service program XVERRH.

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.