With a normal LOAD EPLOC=... macro; no ADDR parameter. I calculated the 
absolute offset of the target instruction and substituted RANGE for PVTMOD and, 
of course, everything worked perfectly. 😊 There is definitely something SLIP 
doesn't like about our modules. 

One good outcome of this exercise is I have read the SLIP doco thoroughly and 
discovered the ACTION=RECOVERY parameter. This causes an abend 06F-080 to be 
issued when the trap is triggered; that
causes our recovery routines to run which schedule an SVC dump. Then you can 
use your normal
abend analysis and recover the registers at the time of the trap. Neat!

Robin

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Seymour J Metz
Sent: 08 June 2022 17:28
To: [email protected]
Subject: Re: SLIP IF not working

How did you load it?


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Robin Atwood [[email protected]]
Sent: Wednesday, June 8, 2022 3:03 AM
To: [email protected]
Subject: Re: SLIP IF not working

Thanks to everyone who responded. I will answer all the questions here:

1. The module was definitely loaded. We dynamically load all our modules so I 
checked with XDC that it was there.
2. It is not an LPA module, it's loaded into private memory.
3. I did issue D SLIP=SLP1 and the SLIP was enabled/active.
4. It is not a CICS module. The task is a file server so I kicked off a 
transfer from the PC.
5. A=SVCD is the default for most types of trap. I even tried A=SYNCSVCD, which 
overrides DAE.

I strongly suspect the problem is caused by the PVTMOD parameter. Normally I 
just specify a RANGE but this SLIP must be sent to a customer, so that will not 
work.

Robin

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
allan winston
Sent: 07 June 2022 23:35
To: [email protected]
Subject: Re: SLIP IF not working

Robin,

   Since you said " I made a transaction that drove MOD1", this brings up the 
question of whether or not this is a CICS region.

   I ran into this problem around 20 years ago.  Because CICS uses a customized 
loader in order to maintain multithreading, PVTMOD did not work.
I forced the module into a fixed location in memory using the "CORE=LOAD"
function of INTERTEST, located the starting address, added the desired offset, 
and then used the RANGE parameter instead of the PVTMOD parameter.

     Allan

On Tue, Jun 7, 2022 at 9:19 AM Robin Atwood <[email protected]> wrote:

> I wanted to get a dump of my server when the instruction at 001234 in 
> module
> MOD1 gets executed, so I entered:
>
>
>
> SLIP SET,IF,J=SRV1,PVTMOD=(MOD1,001234),ID=SLP1,END
>
>
>
> I made a transaction that drove MOD1 but no dump was taken. So, OK, 
> the offset maybe incorrect (there are lots of csects in MOD1) and I 
> adjusted the offset, but to no avail. So just to see if the trap 
> worked at all, I
> entered:
>
>
>
> SLIP SET,IF,J=SRV1,PVTMOD=(MOD1),ID=SLP1,END
>
>
>
> but still no dump. So I must be missing something basic; I was 
> recently doing a lot of SLIP SA traps and didn't have this
>
> trouble. MOD1 is definitely in memory at the time the SLIP command is 
> issued. Any advice much appreciated.
>
>
>
> Thanks
>
> Robin
>
>
>
>
>
>
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
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

Reply via email to