Turn on TRACE CT for SYSTCPIP and SYSTCPDA
V TCIPIP,TCPIP,PKT,ON
TRACE CT for SYSOMVS
Start DUMP COMM=()
Recreate problem
Reply to DUMP R xx,END
If everything you need is in those component traces and if you are sure that
your DUMP parameter will capture those component traces, then sure this i
ite a bit more precise.
//lindy
From: IBM Mainframe Discussion List on behalf of
Peter Relson
Sent: Friday, August 23, 2024 5:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Debugging syscall / SLIP for reason code
EXTERNAL
If entered exactly as shown i
If entered exactly as shown in the original post (the SLIP command and then the
response to the WTOR), that response would have failed and not set a SLIP trap.
As eagle eye Adam spotted, the blank after the address in DATA ends the input
data, requiring the WTOR response to start with the (missin
SLIP set,if,a=SYNCSVCD,RANGE=(10?+8C?+F0?+1F4?),DATA=(13R??+b0,EQ,112B
),DSPNAME=('OMVS'.*)
If the instruction located by OCVTERRA gets control for this situation (that's
what your RANGE keyword gets you) and if your DATA expression is correct, then
the trap will match.
As suggested you m
Without validating the RANGE or DATA parms (although the space after the
address in the DATA parm looks fishy; not sure if that's a problem), I noticed
that you're not specifying a JOBNAME parameter. It would also be good to give
it a descriptive ID parameter.
Also be sure that you're settin
I need some help with debugging a program that runs as a spawned OMVS process.
I have done a SYSOMVS trace where I can see that a syscall to BPX1SOC fails
with reason code 112B and error code is EAFNOSUPPORT.
Looking at the trace I can see that there are 8 parms starting at address
0A6DC23
