Screen Scrape the Job Log /SYSLOG via SDSF API.
On 2022-03-08 10:03, Steff Gladstone wrote:
In one of our REXX procedures we execute IEBCOPY to copy a member from one
PDS to another. Sometimes IEBCOPY fails (e.g., for lack of space either in
the directory or the library). It intercepts the abend through its ESTAE
routine and returns a CC=8 with a text message to SYSPRINT.
We would like to be able to receive more specific information as to the
abend code and reason code of the IEBCOPY fail so we wrote a front-end
which creates our own ESTAE before calling IEBCOPY so we can capture the
information from the SDWA at abend time. But it appears that IEBCOPY
overlays our ESTAE with its own so we don't get control. So we decided
that when IEBCOPY returns to our front-end we would locate the RTM2WA and
glean the information from it. But the pointer to the RTM2WA (TCBRTWA) is
zero at that point (we suppose that IEBCOPY cancels its ESTAE before
returning to us and the RTM2WA is released).
Does anybody have any ideas how we might capture the abend and reason codes
in spite of all this?
Thanks,
Steff Gladstone
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
