|
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.
As an Amazon Associate we earn from qualifying purchases.
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.