Re: timely

2017-03-13 Thread Mark Zelden
On Mon, 13 Mar 2017 01:13:21 -0500, Elardus Engelbrecht wrote: >Paul Gilmartin wrote: > >>>I see what you did there http://www.gocomics.com/nonsequitur/2017/03/12 > >>What did I do there? Did it work? > >You posted a link to a good joke. Now I know why

Re: timely

2017-03-13 Thread Elardus Engelbrecht
Pommier, Rex wrote: >I think Steve was commenting on your subject line tying nicely into the comic. > It was quite well done. Indeed! Just in time before you timed out! ;-) Groete / Greetings Elardus Engelbrecht -- For

Re: timely

2017-03-13 Thread Pommier, Rex
@LISTSERV.UA.EDU Subject: Re: timely On Sun, 12 Mar 2017 18:16:42 -0500, Steve Horein wrote: >I see what you did there > >On Sunday, March 12, 2017, Paul Gilmartin < >000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >> http://www.gocomics.com/nonsequitur/2017/03/12 >

Re: timely

2017-03-13 Thread Elardus Engelbrecht
Paul Gilmartin wrote: >>I see what you did there >>> http://www.gocomics.com/nonsequitur/2017/03/12 >What did I do there? Did it work? You posted a link to a good joke. Now I know why Stonehenge was abandoned... ;-D Many thanks Paul for sharing it! Groete / Greetings Elardus Engelbrecht

Re: timely

2017-03-12 Thread Paul Gilmartin
On Sun, 12 Mar 2017 18:16:42 -0500, Steve Horein wrote: >I see what you did there > >On Sunday, March 12, 2017, Paul Gilmartin < >000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >> http://www.gocomics.com/nonsequitur/2017/03/12 >> What did I do there? Did it work? -- gil

Re: timely

2017-03-12 Thread Steve Horein
I see what you did there On Sunday, March 12, 2017, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > http://www.gocomics.com/nonsequitur/2017/03/12 > > -- gil > -- For IBM-MAIN subscribe / signoff /

timely

2017-03-12 Thread Paul Gilmartin
http://www.gocomics.com/nonsequitur/2017/03/12 -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Getting timely dump out of LE

2016-05-26 Thread Bill Hitefield
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Anthony Thompson Sent: Wednesday, May 25, 2016 11:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Getting timely dump out of LE I was wondering if you looked in LOGREC to see if that recorded the first S0C4. Ant. -Original Message

Re: Getting timely dump out of LE

2016-05-25 Thread Anthony Thompson
timely dump out of LE I wouldn't think that more than one of the 0C4's in the system trace would match the PSW in the MCH control block. You can display time in the system trace by doing 'ip systrace time(local)'. For the wrapping issue... some version of z/OS allowed the system trace table size

Re: Getting timely dump out of LE

2016-05-25 Thread Don Poitras
I wouldn't think that more than one of the 0C4's in the system trace would match the PSW in the MCH control block. You can display time in the system trace by doing 'ip systrace time(local)'. For the wrapping issue... some version of z/OS allowed the system trace table size to be set much higher.

Re: Getting timely dump out of LE

2016-05-25 Thread Martin Packer
m/tv/category/mpt/ From: Ron MacRae <ronmac...@hotmail.co.uk> To: IBM-MAIN@LISTSERV.UA.EDU Date: 25/05/2016 09:27 Subject:Re: Getting timely dump out of LE Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Lizette, I can get the r

Re: Getting timely dump out of LE

2016-05-25 Thread Ron MacRae
Lizette, I can get the registers and PSW no problem. The problem I have is getting the TIME of the S0C4 so I can see which one is first. So much happens before LE gets round to taking a system dump that the z/OS trace has wrapped and I can't tell which of the 6 S0C4 abends, on

Re: Getting timely dump out of LE

2016-05-11 Thread Lizette Koehler
m: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ron MacRae > Sent: Wednesday, May 11, 2016 6:39 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Getting timely dump out of LE > > Lizette, >I'm familiar with "ip verbx ledata 'all,tcb(tt

Re: Getting timely dump out of LE

2016-05-11 Thread Ron MacRae
Robin, Production support won't run with TRAP(OFF) because of the warnings in the manual about unpredictable results if some conditions are not handled. I think I'll do an IF slip trap when we load the register with zero. This is about a dozen instructions before the S0C4 trying to

Re: Getting timely dump out of LE

2016-05-11 Thread Ron MacRae
Lizette, I'm familiar with "ip verbx ledata 'all,tcb(tt)' " If that's the one you mean. The trace in the SYSMDUMP starts almost a minute after the initial bunch of S0C4s but none of them are in the z/OS trace any more so I can't tell which is first. Ron.

Re: Getting timely dump out of LE

2016-05-06 Thread Robin Atwood
- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: 05 May 2016 23:38 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Getting timely dump out of LE Have you use IPCS with the LE VERBX function? LE normally will have a handle routine

Re: Getting timely dump out of LE

2016-05-05 Thread Lizette Koehler
t; To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Getting timely dump out of LE > > Hi all, > I've got a multi-tasking C & ASM LE application running 100+ TCBs. > Occasionally I get an S0C4 abend, which quickly cascades into multiple S0C4 > abends. By the time LE gets round t

Getting timely dump out of LE

2016-05-05 Thread Ron MacRae
Hi all, I've got a multi-tasking C & ASM LE application running 100+ TCBs. Occasionally I get an S0C4 abend, which quickly cascades into multiple S0C4 abends. By the time LE gets round to taking a SYSMDUMP the MVS trace has wrapped and I can't determine what is the first S0C4. I end