@Peter, welcome back.
I get the difference between installation exits and other exits. A SYNAD
exit is certainly an exit, but it is not in the same class with an IEFU83
exit.
But I fail to get the distinction relative to CSVFETCH. Installation X wants
to monitor every QSAM close, so they write some code and install it as an
IEFU8x exit. Installation Y wants to monitor every LOAD/FETCH, so they write
some code and install it as a CSVFETCH exit. What is the fundamental
difference?
> renaming the book is part of the answer ("Installation Exits and other
> exits" -- of course not exactly that)
How about "Exits"?
> A chapter "a list of
> non-installation exits" seems somewhat incongruous in a book of
> "Installation Exits"
Agreed, but would work as an Appendix.
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Relson
Sent: Tuesday, June 25, 2019 5:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: LOAD/LINK exit
<snip>
Perhaps we should consider mentioning CSVFETCH in the
MVS Installation Exits book, with a pointer to the book where CSVFETCH
is documented.
</snip>
CSVFETCH is not an installation exit. It is what I call a program exit
(e.g., the EXITTYPE keyword of CSVDYNEX), for use by applications. There
are dozens (hundreds?) of program exits with documentation scattered
everywhere.
I'm not at all opposed to having a list of all of these exits, but perhaps
"in the ...Installation Exits book" is not the right answer. Perhaps
renaming the book is part of the answer ("Installation Exits and other
exits" -- of course not exactly that). A chapter "a list of
non-installation exits" seems somewhat incongruous in a book of
"Installation Exits" but finding a different home for such a list might
not find any better approaches.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
