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

James,

How about a data area to return a value? The calling program sets up the data area and the called program updates the data area. If you're using called programs already in place that won't be modified then the data area never changes and the calling program does some default behavior. You could create a data area specifically for this purpose or could use the LDA.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Tuesday, April 12, 2011 5:11 PM
To: Midrange Systems Technical Discussion
Subject: CL program calling a CL program with no parameters: can the calledprogram easily return some result to the calling program?

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.

--
JHHL