Hello Jon, My question was purely from system programmers perspective.
"As for understanding the storage area and modules, you would need to understand the programs involved. Source code and assembly listings are usually needed for this." Apology for my ignorance. Does it apply same for analysing Z/OS Standalone Dump ? On Wed, Sep 4, 2013 at 1:10 AM, Jon Perryman <jperr...@pacbell.net> wrote: > Your question is too vague. If you could be more specific, we might be > able to answer your questions. I assume you are asking as a sysprog > analyzing a system dump. If you are analyzing your own programs, then it > would be different. > > As a sysprog, you would use this information to do searches in the problem > database. As a default, the CSECT name (and some other information) is > null. It is up to the abend recovery to fill in these fields. Most vendor > products and some programming languages fill in these fields. Assembler > does not fill it unless the programmer implements abend recovery to fill it > in. > > As for understanding the storage area and modules, you would need to > understand the programs involved. Source code and assembly listings are > usually needed for this. > > Jon Perryman. > > >________________________________ > > From: Jake anderson <justmainfra...@gmail.com> > > > >I was trying to understand about an application when It fails I check its > >symptoms using IPCS and I get the Module name and CSECT value. > > > >Is it possible to understand the storage area name where a particular > >Module was failed ? >
