On Mon, 9 Feb 2026 16:12:20 +0000, Steely.Mark <[email protected]> wrote:
>If I remember correctly, I think all tasks need an OMVS segment. I think that >requirement started with z/OS v2.5. Peter doesn't say what tasks, but whatever they are they probably required / had an OMVS segment long before z/OS 2.5. But some things were tightened up in 2.5, so I suppose it possible. However, there isn't a single thing mentioned in the migration workflow for z/OS 2.5 nor z/OS 3.1, so I really tend to doubt it. Peter, did you see "BPXP018I" at all? Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html > >-----Original Message----- >From: IBM Mainframe Discussion List <[email protected]> On Behalf Of >Mark Zelden >Sent: Sunday, February 08, 2026 2:23 PM >To: [email protected] >Subject: Re: s422 abend after zos 3.1 > > ! > >CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? >Were you expecting this email? If not, report it using the Report Phishing >Button! > >On Sun, 8 Feb 2026 14:03:24 +0400, Peter <[email protected]> wrote: > >>Hello >> >>Recently I upgraded the zos 2.4 to zos 3.1 and the task started to fail. >> >>These Task have lot of external connections made via IP. >> >>IEF450I XXXXXX XXXXXX - ABEND=S422 U0000 REASON=000001A0 >> >> >> >>From IPCS for the dump captured. >> >>Symptom Description >> >>------- ----------- >> >>PIDS/5752SCPX1 Program id: 5752SCPX1 >> >>RIDS/BPXINPVT#L Load module name: BPXINPVT >> >>RIDS/BPXPTEXT Csect name: BPXPTEXT >> >>AB/S00C4 System abend code: 00C4 >> >>PRCS/00000004 Abend reason code: 00000004 >> >>REGS/C23E0 Register/PSW difference for R0C:-23E0 >> >>RIDS/BPXMIPCE#R Recovery routine csect name: BPXMIPCE >> >> >> >> >> >>Primary Symptom String: >> >> >> >> RIDS/BPXINPVT#L RIDS/BPXPTEXT PIDS/5752SCPX1 AB/S00C4 RIDS/BPXMIPCE#R >> >> VALU/H02240017 REGS/C23E0 PRCS/00000004 VALU/COPENMVS >> >> >> >> Symptom Symptom data Explanation >> >> --------------- ------------- ----------- >> >> RIDS/BPXINPVT#L BPXINPVT#L Routine identifier >> >> RIDS/BPXPTEXT BPXPTEXT Routine identifier >> >> PIDS/5752SCPX1 5752SCPX1 Component identifier >> >> AB/S00C4 00C4 ABEND code - system >> >> RIDS/BPXMIPCE#R BPXMIPCE#R Routine identifier >> >> VALU/H02240017 02240017 Error related hexadecimal value >> >> REGS/C23E0 C23E0 Program register >> >> PRCS/00000004 00000004 Return code >> >> VALU/COPENMVS OPENMVS Error related character value >> >> >> >>Did anyone faced this issue ? It Will helpful for me to research >>further >> >> >>Peter >> > > >I haven't seen that or run into it. Have you looked at the output from "D >OMVS,LIMITS" , Also add >LIMMSG(ALL) to BPXPRMxx and/or set it dynamically. Look at MAXSOCKETS >and MAXFILEPROC. > >Regards, > >Mark >-- >Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 >Foundation Certified mailto:[email protected] Mark's MVS Utilities: >http://www.mzelden.com/mvsutil.html > >---------------------------------------------------------------------- >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
