Turner Cheryl L wrote:
Greetings.
Our former sysprog, who paid attention to the more finer system details, has
left the building for greener pastures. So now we seem to have to step up our
game. However, I'm not sure what to do or how.
We are running several EREP reports to see what software or symptom records are
being cut per LPAR (mostly just HISTORY reports for now). We are finding that
a lot of records are being cut at the time an IBM supplied SLIP trap is taken
(for example X13E, X47B, X91A). Some of these records can exceed hundreds on a
given day.
What should we/I be doing? Reporting them to IBM? I just don't understand why
IBM would set the SLIP yet cut a symptom or software record too. We can't be
the only shop seeing these. Yet I've tried to research a few on IBMLINK but
can't find any hits for known problems. Or maybe there is a way to turn of the
creation of the software/symptom record? Though I can't wrap my head around
that either, thinking why are they then being cut at all if it's not anything
to look into?
Any schooling you can give, would be most appreciated! But please, be gentle.
I'm out of my element. Many thanks to you all.
If you care to research these, look up the abends and see whether you
really care. Using 13E as an example:
Explanation: The task that created a subtask issued a DETACH macro for
that subtask, specifying STAE=NO, before
the subtask ended.
This may or may not be an error, depending on the intent of the user.
Consequently, the system does not abnormally
end the task issuing the DETACH macro.
With no proof to back my assumptions, I nonetheless suspect that, if you
look at these, you will find that most or all of those are from
application programs that summarily shot their subtasks rather than
signaling them to complete or waiting for them to complete.
You can discuss such things with the application owner, but you might
find most of them reluctant to "fix" the problem when what they are
doing is working from their perspective and the net ill effect is
"noise" in EREP reports.
I will observe, though, that the system programmer action for ABEND13E
could use some updates...
--
John Eells
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
