How about SLIP SET,COMP=0c4,ACTION=SVCD and do not specify any address space etc Colin
On Sat, 15 Jul 2023 at 01:17, Farley, Peter < [email protected]> wrote: > Hi All, > > I am trying to help the python ibmdb team help me solve an S0C4 abend > issue with (we think maybe) their code on the IBM Zxplore LPAR by > generating an SVCDUMP that the ibmdb team could analyze. The admins at > Zxplore have tried a couple of times to set a SLIP to catch the S0C4 abend > that I am getting when using one of the ibmdb functions, but it keeps > missing catching the abend. > > Here is the "usual" setup to duplicate the abend: > > 1. USS logon from ssh on a Windows box at my home into the Zxplore > system. Zxplore runs the bash shell as your default shell. > 2. Execute "python3 db_fetch_both_err-2.py" > 3. This reliably generates a S0C4 abend deep inside the python > runtime code in something named TOROLABA the first time the python script > tries to use the ibmdb function "fetch_both(...)". > > I can supply both a copy of the python script and the exact text of the > abend messages if it helps you to help me, but the real question we have is > how should a SLIP trap be set up to catch a S0C4 abend in a forked USS > address space? The only dump that seems to be generated is a CEEDUMP in my > $HOME directory on Zxplore. > > I have also tried a JCL executing BPXBATCH to run the exact same python > script, and that also does not trigger the SLIP they recently set to match > the JOB name of that JCL. SHAREAS=MUST does not work with the bash shell, > so the python process is (I believe) being forked to a new AS by BPXBATCH. > > Any and all assistance to help us catch this abend and generate the > SVCDUMP that the ibmdb team have requested to help solve the root cause > would be much appreciated. > > Peter > > 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
