Question:
When reviewing the holds for z/OS 2.1 RSU1509, ran across this one for JES2 that I think might possibly be more applicable to ENF:
++ HOLD(UA77919) SYS FMID(HJE7790) REASON(ACTION) DATE(15177)
COMMENT
(***************************************************************
* FUNCTION AFFECTED: JES2 (OA47827) *
****************************************************************
* DESCRIPTION : Installation notes *
****************************************************************
* TIMING : Pre-APPLY *
****************************************************************
ENF listen exits for ENF signals 58, 70, and 78 must
be reentrant. This is not a new requirement, but
ignoring the requirement did not cause a problem in
the past because the signals were presented to the
listen exits serially.
This APAR will change that behavior: As the listen
exits will now be invoked in parallel, these ENF
listen exits DEFINITELY MUST BE CODED TO BE REENTRANT
to function correctly.).
The ENF signals described are JES2 event signals, but they’re used for some other products’ “listeners”. So I’d be wondering about CA7, OPS/MVS or maybe the Common Services tasks that have functionality that wants to check on job statuses?
Answer:
In regards to CA-7 there are currently no anticipated or known concerns. None of its' listeners rely on signals created by IBM’s ENF.
In regards to CA-OPS/MVS there are currently no anticipated or known concerns. CA-OPS/MVS does not use/have any ENF-JES event exit listeners.
In regards to CA Common Services there are no anticipated or known concerns. The CA-ENF SUB=MSTR code uses SIGNAL 40 and all code is reentrant.