I would say yes. Note the following:
CSVFETCH exit routine environment
The exit routine receives control in the following environment:
In supervisor state with PSW key 0.
In dispatchable unit mode of task, running under the task and
request block of the fetch or unfetch processing.
In cross memory mode of PASN=HASN=SASN.
In AMODE 31.
In primary ASC mode.
Enabled for I/O and external interrupts.
With the local lock held (the exit routine must not release
the local lock)
With parameter areas in the primary address space. The
parameter list is described below.
In the address space in which the fetch or unfetch was
initiated
Under the task in which the fetch or unfetch was initiated
CSVFETCH exit routine recovery
The exit routine should provide its own recovery, using SETFRR.
If the exit routine ends abnormally, its recovery routine will
get control before the recovery routine established by the system.
I would have it in an APF library with AC(0) if for no other
reason than to know it is in a library of code that can get to
SupState/Key0.
Regards,
Steve Thompson
On 6/26/19 1:28 PM, Thomas David Rivers wrote:
Michael Stein wrote:
On Thu, Jun 13, 2019 at 02:10:32PM -0400, Steve Thompson wrote:
I seem to recall that there is a way to look at a LOAD/FETCH
via an exit.
csvfetch
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa800/csvfetch01.htm
The CSVFETCH exit provides information about the fetching (or
unfetching)
of a module. The exit is primarily intended to be used as
part of
monitoring (whether for reporting or debugging). The exit
will be called
holding the local lock. The exit routine must not release the
local lock.
Does that require an authorized module because the exit receives
control in KEY 0?
- Dave R. -
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
