In <[EMAIL PROTECTED]>, on 11/27/2006
at 04:44 PM, Charles Mills said:
>I'm sorry - I hate to start up this "reentrant" thing again but would
>anyone (everyone? <g>) like to suggest a term to describe a program
>that is technically reentrant but that cannot be multi-tasked in a
>single jobstep due to some hard-coded externality?
Oxymoron. If it cannot be multitasked in a single jobstep then it is
technically *not* reenterable, regardless of how it is marked.
Assigning the RENT option does not magically make a module
reenterable.
>I'm writing documentation and would like to apply the correct term
>to the IBM FTP client, which has the RENT bit set but which uses the
>hard-coded DD names INPUT and OUTPUT and therefore effectively
>cannot be multi-tasked in a single jobstep or region.
"Serially reusable but incorrectly link edited as reenterable."
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
