It means the single previous line was repeated N times.
On 19/09/2019 03:02, Paul Gilmartin wrote:
> On Thu, 19 Sep 2019 01:54:50 +0100, CM Poncelet wrote:
>
>> The before/after addresses (on the LHS in the SYSUDUMP) show which
>> addresses of the excluded lines are "SAME AS ABOVE".
>>
> Yes,
our J Metz
Sent: Thursday, September 19, 2019 9:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Description of the format of a SYSUDUMP
I remember one such product that intercepted ABENDs and dropped diagnostic data
that would otherwise have appeared on the dump.
--
Shmuel (Seymour J.)
x23353
Sent: Thursday, September 19, 2019 11:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Description of the format of a SYSUDUMP
All of which AssUMes that your local sysprog and security teams have deigned to
make IPCS available to the ordinary application developer; not always the case
I&#
t On Behalf Of
Seymour J Metz
Sent: Thursday, September 19, 2019 11:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Description of the format of a SYSUDUMP
Well, chacun à son goût; there's a lot that IPCS can format, and hand decoding
from the hexadecimal storage dump is so 19th Century.
homas David Rivers
Sent: Wednesday, September 18, 2019 1:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Description of the format of a SYSUDUMP
Well - I've been reading SYSUDUMPs for a long time, but I've never
found a pretty precise description of the various pieces of the dump.
The newer z/
n List on behalf of
Thomas David Rivers
Sent: Thursday, September 19, 2019 8:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Description of the format of a SYSUDUMP
Paul Gilmartin wrote:
>On Wed, 18 Sep 2019 15:36:14 -0400, Thomas David Rivers wrote:
>
>
>>I guess I'm askin
try
MVS Diagnosis:
Tools and Service Aids
From: IBM Mainframe Discussion List on behalf of
Thomas David Rivers
Sent: Thursday, September 19, 2019 7:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Description of the format of a SYSUDUMP
Paul Gilmartin
Paul Gilmartin wrote:
On Wed, 18 Sep 2019 15:36:14 -0400, Thomas David Rivers wrote:
I guess I'm asking "what is the chunk of memory described in 'SAME AS
ABOVE'" ?
Seems like a document somewhere might explain that definitively... ?
Was that the entirety of your question or just a r
On Thu, 19 Sep 2019 01:54:50 +0100, CM Poncelet wrote:
>The before/after addresses (on the LHS in the SYSUDUMP) show which
>addresses of the excluded lines are "SAME AS ABOVE".
>
Yes, but the question is, if N lines are identified as excluded, does that
mean the single previous line was repeated
The before/after addresses (on the LHS in the SYSUDUMP) show which
addresses of the excluded lines are "SAME AS ABOVE".
CP
On 18/09/2019 21:48, Tony Harminc wrote:
> On Wed, 18 Sep 2019 at 13:40, Thomas David Rivers wrote:
>
>> My particular question is the
>>
>>LINES -
On Wed, 18 Sep 2019 16:48:18 -0400, Tony Harminc wrote:
>>
>>LINES - SAME AS ABOVE
>>
>> in a memory dump. Does that mean the the single line (of 32-bytes) just
>> before this line is copied as many times to fill in the space between
>> and
>
>Yes - quite def
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Tony Harminc
Sent: Wednesday, September 18, 2019 3:48 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: Description of the format of a SYSUDUMP
On Wed, 18 Sep 2019 at 13:40, Thomas David Rivers wrote:
>
On Wed, 18 Sep 2019 15:36:14 -0400, Thomas David Rivers wrote:
>
>I guess I'm asking "what is the chunk of memory described in 'SAME AS
>ABOVE'" ?
>
>Seems like a document somewhere might explain that definitively... ?
>
Was that the entirety of your question or just a representative example
of se
On Wed, 18 Sep 2019 at 13:40, Thomas David Rivers wrote:
> My particular question is the
>
>LINES - SAME AS ABOVE
>
> in a memory dump. Does that mean the the single line (of 32-bytes) just
> before this line is copied as many times to fill in the space between
> an
On Wed, 18 Sep 2019 15:03:38 -0500, Tom Marchant wrote:
>On Wed, 18 Sep 2019 15:36:14 -0400, Thomas David Rivers wrote:
>
>>I guess I'm asking "what is the chunk of memory described in 'SAME AS
>>ABOVE'" ?
>
>One line. 32 bytes.
>
>It is simply telling you that it has skipped printing lines that w
On Wed, 18 Sep 2019 15:36:14 -0400, Thomas David Rivers wrote:
>I guess I'm asking "what is the chunk of memory described in 'SAME AS
>ABOVE'" ?
One line. 32 bytes.
It is simply telling you that it has skipped printing lines that would contain
the same data content.
It becomes obvious when you
Gereldy wrote:
Seems like I recall, at some point, a pretty precise document on the format
of a SYSUDUMP - but I can't seem to find it now... if anyone remembers what
that might be a pointer to that would be welcome.
I guess I would describe it as the storage that would be shown in li
When in a dump you see:
Line 10 (as in it is all zeroes)
Lines 11-20 SAME AS ABOVE
that means the data in lines 11-20 are all zeroes, too. IBM did this to save
paper (how many zeroes do you need to see?). It does not mean that the data
was copied from Line 10.
-
In times past it always meant the single line above.
Jim Horne
-Original Message-
Well - I've been reading SYSUDUMPs for a long time, but I've never found a
pretty precise description of the various pieces of the dump.
The newer z/OS doc seems to just want to point you to IPCS, but I ra
Well - I've been reading SYSUDUMPs for a long time, but I've never
found a pretty precise description of the various pieces of the dump.
The newer z/OS doc seems to just want to point you to IPCS, but I rather
like just reading the dump.
My particular question is the
LINES -
20 matches
Mail list logo
