On Thu, 1 May 2008 17:58:42 +0200 Lindy Mayfield <[EMAIL PROTECTED]> wrote:
:>There is a small technical detail I have been curious about concerning :>IKJCT441. :>If I use the CALL *(module) method from a Rexx (or CLIST) exec, does it :>make sense to design the module to only work with an exec, or can it be :>more generic and realize how it is being called and function :>appropriately? :>For example, if executed in a batch job or called directly from TSO it :>would read from and write to a file. If called from a Rexx exec it :>would set variables. :>One reason might be to take an existing program and have it also :>interact with an exec and set variables. Or the same with a new :>program. :>If this is valid, what would be a good way for the program to know how :>it is being called? I've been looking at some dumps but haven't found :>anything yet. Like something interesting at R0. This would be poor design. Allow the user to specify a parm as to how he wants this done. Perhaps he wishes to use files under TSO. -- Binyamin Dissen <[EMAIL PROTECTED]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
