Suggestions:
1)make the assembler routine re-entrant. Successive LOADS will up the use
count, but not actually bring in a new module.
2)pass the called routine a parm that says this is a successive call, not
the 1st.
3)if you can't do #2 above, take a look at NAME/TOKEN services.
4)if you can't do #3 above, create another load module that is not
re-entrant. Just a csect that is all 0's. Have the 1st routine search the
CDE chain for the non re-entrant one. Set indicators in the non re-entrant
dummy 0's load module that tells the other one what the status of things
are.
----------------------------------------------------------------------
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
