|
|
| Author |
Message |
sunny_io
New User
Joined: 11 Jul 2007
Posts: 22
Location: noida
|
|
|
|
Hello All
can you pls share what does the following dump signify
and how to read it Also.. thanks
F0F04040 404040F0 F0F04040 404040F0
404040F0 F0F04040 404040F0 F0F0F0F0 |
|
| Back to top |
|
 |
References
|
 Posted: Tue Mar 18, 2008 10:49 pm Post subject: Re: what is 40 and 0F in mainframe spool dump |
|
|
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 985
Location: Virginia, USA
|
|
|
|
| x'F0' is a 0 and x'40' is a space |
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 271
Location: Jacksonville, FL
|
|
|
|
F0F04040 404040F0 F0F04040 404040F0
404040F0 F0F04040 404040F0 F0F0F0F0
converts to:
A 40 is a blank and a F0 is a zero.
There is not enough information to debug a dump. |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7997
Location: 221 B Baker St
|
|
|
|
Hello,
What are you trying to resolve? Do you have an abend or did something run incorrectly?
What you have posted provides no info to work with. It reads as zeros and spaces and as posted does not have any significance.
If you provide proper info, someone here should be able to help. |
|
| Back to top |
|
|
sunny_io
New User
Joined: 11 Jul 2007
Posts: 22
Location: noida
|
|
|
|
Hello All
thanks for the replies. I was just trying to understand how to read a dump.
this was the most common thing in there.. "F0" and "40" so i thought of starting with this..
thanks again
Sunny |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7997
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
| this was the most common thing in there.. "F0" and "40" so i thought of starting with this |
A space is the most common alpha value in a process and a zero is the most common number in a process.
Keep in mind that individual bytes in a core dump are nearly meaningless. They only mean something when considered by their address in the dump and the surrounding data (i.e. within a data record or working-storage item), the surrounding executable code, or "control" information used by the run unit (i.e. tgt, pgt, i/o buffers, etc).
If you want to look into a dump, i'd suggest for a first step you might create a small cobol program, put an "eye catcher" at the start of working-storage, define some pic n(x), some pic n(9), and some pic n(9) comp-3 fields with initial "value"s specified, and then force the program to abend so you will have a dump to look at.
In the dump look for the eye catcher and then the fields you defined and you can see how your fields appear in a dump. |
|
| Back to top |
|
|
|
|
