Peter,
If you can run GTF on the Zxplore system and capture the output, you might
want to try to use the DEBUG option of the SLIP SET command:
DEBUG
For a SLIP SET trap, allows you to determine why a trap that you set is
not working as you expected by indicating which of the conditions you
established is not being met. DEBUG provides trap information each time
the trap is tested rather than just when it matches.
The generalized trace facility (GTF) and its trace option for SLIP
records must be active. Each DEBUG trace record contains SLIP
information plus two bytes: the first byte contains a value indicating
the failing parameter and the second byte contains zero.
For a description of the DEBUG values, see the SLIP debug trace record
for GTF in z/OS MVS Diagnosis: Tools and Service Aids.
Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.
On Sun, Jul 16, 2023 at 3:48 PM Farley, Peter <
0000031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:
> This is the latest SLIP setup from today which did not catch the abend
> when the python script is executed from an ssh login to z/OS on the Zxplore
> system:
>
>
> SLIP
> SET,ID=PJF1,JOBNAME=Z02446*,COMP=0C4,ACTION=SVCD,AL=(H,P,S),SDATA=(ALLNUC,PSA,RGN,LPA,CSA,SQA,TRT,GRSQ,SUM),END
>
>
> Peter
>
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf
> Of Peter Relson
> Sent: Saturday, July 15, 2023 8:26 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: How to set a SLIP to catch S0C4 in OMVS separate AS
>
>
>
> What SLIP trap did you try setting? SLIP SET,C=0C4,A=SVCD,END will catch
> every 0C4 that occurs anywhere. That wouldn't be what I'd want for a SLIP
> trap (it's too broad so will hit on things you don't want). But it would
> work. But only once (default match limit for A=SVCD is one). Either there
> was no 0C4 or your SLIP trap asked to filter out the 0C4 that happened or
> your SLIP trap is not active (perhaps because of a previous match reaching
> the match limit). I can think of a lot of ways to create a SLIP trap that
> would not match.
>
>
>
> Gil wrote
>
> <snip>
>
> No assistance, but an observation that SLIP has appeared to have been
>
> specified before fork() came to MVS.
>
>
>
> It would be a good Idea to enhance SLIP to recognize all the progeny
>
> of a job step.
>
> </snip>
>
>
>
> I wouldn't bet that SLIP needs any enhancement in that arena. But perhaps
> once we hear from the OP what he tried that did not work we will form a new
> opinion.
>
>
>
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
