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.

Thanks,
Lindy

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

Reply via email to