Hi Mary.. Thanks for the response.. We are running zOS 1.12 and we are on
shared file system.. I will take a look on the apars you suggessted. Many
thanks
On Nov 15, 2012 6:13 PM, "Mary Anne Matyaz" <[email protected]> wrote:

> Was the dump an abendec6 with REASON=0E0F0407? If so, have a look at
> OA39768 or OA22587.  Also, it's helpful if you provide z/os level and
> whether or not you are in a shared filesystem sysplex.
> To your question about a missing mount, IMHO I wouldn't think that would
> cause this kind of issue.
>
> MA
>
>
>
> On Thu, 15 Nov 2012 17:16:58 +0530, RCG <[email protected]> wrote:
>
> >Dear Group,
> >
> >One of our system sufferred an outage due to OMVS terminated abruptly with
> >message id BPXI019E OMVS DETECTED A SEVERE INTERNAL ERROR THAT WILL
> REQUIRE
> >A RE-IPL TO CORRECT..
> >
> >There was a dump taken and had to quiesce the workload and re-IPL the
> >system immediately..
> >
> >We have had sent the dump to IBM L2 Support and while we wait to hear from
> >them. Appreciate any expert advice on the reasons that could be a cause
> for
> >this issue as i have had reviewed the log for errors and cant see anything
> >unusual except i see there was a syntax error and one of the file in
> >BPXPRMxx was not physically present in the system.. Can this be potential
> >causer? Or anything else if known.. Any suggesstions / answers are highly
> >appreciated. Many thanks!
> >
> >Regards,
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions,
> >send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to