RE: CL program calling a CL program with no parameters: can the called program easily return some result to the calling program?

Since you imply that you cannot use a parameter, I'd go with some sort of
message. *NOTIFY seems best to me.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Man invented language to satisfy his need to complain."
-- Lily Tomlin

Scenario:
A CL standardized program that rebuilds an application's "environment
library" calls an installation-specific CL program, to build
installation-specific elements of that library.

If it doesn't find the installation-specific CL program, it just goes
through a standard version of what the installation-specific program
would do.

If it does find the installation-specific CL program, then depending on
the individual circumstances, the standard code might be executed
anyway, or it might be skipped.

What would be the best way for the called program to tell the calling
program what to do? End with an escape message? Something else?

If I weren't overlaying this on something already in place, I'd just
use
a parameter.