On 6/13/2011 5:44 AM, Peter Relson wrote:
We would not want to break some potentially critical application that had
a "correct" program such as
OPEN
If R15 not-equal 0 then abend
When the application had, in effect, wanted the long-standing (somewhat
strange) behavior of ignoring the DCBE because of its key (or any of the
other reasons why a DCBE might be ignored).
My assumption is that (nearly) 100% of ignored DCBEs are a total surprise to the
programmer. Creating a DCBE is extra work. No programmer I know would
intentionally go to that much trouble for a No-Op. If any of our DCBEs are being
ignored (maybe some are!), we would consider that a bug in our code.
Therefore, I favor an abend for 'bad' DCBEs analogous to many similar abends for
'bad' DCBs.
The same tracker technology that was used for the EAV project could be used to
empirically identify cases where a DCBE is being unilaterally ignored by the
system. As I said, I predict that (nearly) 100% of identified cases will come as
a total surprise to the programmer and the problems will be fixed. There might
not be any cases left after that!
For the highly-unlikely (yet possible) case in which a program provides a DCBE
and expects it to be ignored, those programmers could remove the DCBE themselves
prior to OPEN or set a new option in the DCB/DCBE that would tell the system to
use the old behavior.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
