(I don't normally resend posts, but this one never echoed to my inbox.)
Good guess on the abend code. See OA06207 : IEA303W CONTAINS INCORRECT ABEND CODE ERROR DESCRIPTION: When processing a CALLRTM TYPE=ABTERM request, during NIP processing, message IEA303W contain incorrect ABEND code. Interface problem between IEAVNIPX and IEAVNIPM results in identification incorrect ABEND code. In reported problem, program issued DETACH and DETACH processing issued ABEND13E, but abend code in MSGIEA303W did not show ABEND 13E text. Verification steps: IPCS STATUS command will show IEA303W text containing ABEND code that is different from ABEND code shown in *RCVY ABT entry of IPCS SYSTRACE ALL command output. . . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] -----IBM Mainframe Discussion List <[email protected]> wrote: ----- >To: [email protected] >From: Nasuh KARAHALLI >Sent by: IBM Mainframe Discussion List >Date: 05/30/2005 07:59 >Subject: Re: SBD4 at z/OS 1.4 IPL > >Miklos wrote : > >---------------- >IEA303W ABEND BD4 REASON 00000000 DURING INITIALIZATION UNDER RIM >IEAVNPA1 >---------------- <snip> > But when looking at Abend Code BD4, it seems to be >incorrect which may prevent a detailed problem >investigation.Probably >verifying whether Abend Code SBD4 is correct or not should be a path >you go >down at first, I believe. > >Regards. >Nasuh KARAHALLI. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
