It’s an easy fix. Ask the admins to upgrade Python and happy days. Looks like you’re running beta code or worse on Z XPlore. I would be reluctant to address any issues from that system.
> On 17 Jul 2023, at 10:14 pm, Farley, Peter > <[email protected]> wrote: > > Since it was one of the Rocket developers who requested that I try to get a > dump to be analyzed by them, I intend to respect their request and continue > to try to provide one to them if I am able to do so. > > Peter > > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > David Crayford > Sent: Monday, July 17, 2023 1:54 AM > To: [email protected] > Subject: Re: How to set a SLIP to catch S0C4 in OMVS separate AS > > > >>> On 17 Jul 2023, at 12:44 pm, Farley, Peter >>> <[email protected]<mailto:[email protected]>> >>> wrote: >> >> > >> Dave, > >> > >> It may well be that the python V3.9.2 on the Zxplore system is “broken” as >> you suggest, but getting a dump that proves it to the Zxplore admins still >> could help goad them to more rapidly upgrade the python that is available >> there. I don’t see that as a useless exercise or as wasting time chasing at >> shadows. > >> > >> Nailing down the root cause of an issue is not useless. > > > > So you expect the maintainers of ibm_db to identify the underlying cause, > which is broken Python 3.9.2? I find that expectation unreasonable. Perhaps > you should consider opening a case with IBM to address this issue. However, I > can provide you with insight into what their response might be: "Python 3.9.2 > is no longer supported; please upgrade Python to the latest version." Another > concern is that you are utilizing a system where you lack control or > influence over the application of maintenance. > > > > The assumption that Python 3.9.2 is stable may not hold true. Since it is > unsupported and no longer available for download, it raises questions about > how the Rocket developers are able to test it in the first place. > > > >> > >> Peter > >> > >> From: IBM Mainframe Discussion List >> <[email protected]<mailto:[email protected]>> On Behalf Of >> David Crayford > >> Sent: Sunday, July 16, 2023 7:46 PM > >> To: [email protected]<mailto:[email protected]> > >> Subject: Re: How to set a SLIP to catch S0C4 in OMVS separate AS > >> > >> It seems to me that the Zxplore Python is badly broken and has major issues >> with codepage translation. we’ve seen this before when you opened an issue >> for pyzfile. I’m going to update the ticket to that effect so the >> maintainers don’t waste time chasing shadows. > >> > >>>> On 17 Jul 2023, at 3:57 am, Farley, Peter >>>> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>> >>>> wrote: >> >> > >>> Peter, > >> > >>> A CEEDUMP was in fact supplied to the ibmdb team on github in the initial >>> error report that I filed there. I generate a CEEDUMP in my $HOME >>> directory every time I execute the example python script. > >> > >>> I don't think any of the ibmdb team has reviewed the dump that I submitted >>> as of yet, or at least none have yet replied to my error report with any >>> questions concerning the contents of that dump. > >> > >>> Peter > >> > >>> From: IBM Mainframe Discussion List >>> <[email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>>> >>> On Behalf Of Peter Relson > >> > >>> Sent: Sunday, July 16, 2023 9:01 AM > >> > >>> To: >>> [email protected]<mailto:[email protected]<mailto:[email protected]%3cmailto:[email protected]>> > >> > >>> Subject: Re: How to set a SLIP to catch S0C4 in OMVS separate AS > >> > >>> It's not expected that a SLIP dump is required to debug an application >>> error (whether it's a segment fault or anything else). Quite the reverse. > >> > >>> So in what way was the CEEDUMP and/or transaction dump not adequate? That >>> should be brought to the attention of the LE team. > >> > >>> Peter Relson > >> > >>> z/OS Core Technology Design > >> > > -- > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by e-mail > and delete the message and any attachments from your system. > > > ---------------------------------------------------------------------- > 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
