> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Shmuel Metz (Seymour J.) > Sent: Sunday, October 22, 2006 12:06 PM > To: [email protected] > Subject: Re: Is the teaching of non-reentrant HLASM coding practices ever > defensible? > > In <[EMAIL PROTECTED]>, on 10/21/2006 > at 10:19 AM, "Jeffrey D. Smith" <[EMAIL PROTECTED]> said: > > >Mainframers tend to use the word "reentrant" to mean > >a program that is concurrently executable by multiple > >units of work and it does not modify itself at all (or > >may modify itself in a way that is not detectable by > >the multiple units of work that are concurrently executing the > >program). > > That's refreshable.
No, that's reentrant. Refreshable means the program does not modify itself *ever*. A reentrant program may modify itself in a way that is not detectable by concurrently executing units of work. That's what I wrote. > Reentrant means that you get correct results when > running concurrent copies, which typically requires some sort of > serialization. No, reentrant means what I wrote. Serialization has nothing to do with it, unless the program is self-modifying (which is also what I wrote). > -- > Shmuel (Seymour J.) Metz, SysProg and JOAT /snip/ Jeffrey D. Smith Principal Product Architect Farsight Systems Corporation 700 KEN PRATT BLVD. #204-159 LONGMONT, CO 80501-6452 303-774-9381 direct 303-484-6170 FAX http://www.farsight-systems.com/ comments are invited on my encryption project ---------------------------------------------------------------------- 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
