|
View previous topic :: View next topic
|
| Author |
Message |
packerm
New User
Joined: 15 Jan 2016
Posts: 7
Location: uk
|
|
|
|
Trying to run some debugging on an Easytrieve program. The manual says that using the above parm will...
- SNAP prints a formatted dump of CA-Easytrieve Plus
storage areas along with an error analysis report.
That's fine but where does the formatted report come out, i.e. what DDNAME? Is it supposed to be on the SYSPRINT withthe other debug info? is it site defined maybe?
Is there a way of forcing a SYSUDUMP as well as I'm also missing that. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
look at the manuals Yourself to find out the required ddnames
( or ask Your colleagues - Your support ) |
|
| Back to top |
|
|
packerm
New User
Joined: 15 Jan 2016
Posts: 7
Location: uk
|
|
|
|
In manual for ABEXIT it says:
| Quote: |
ABEXIT
[ABEXIT {SNAP|NOSNAP|NO}] (return to top)
ABEXIT indicates the level of control exercised over program interrupt codes 1 to 11. SNAP prints a formatted dump of CA Easytrieve® storage areas along with an error analysis report. NOSNAP prints only an error analysis report. NO inhibits CA Easytrieve® interception of program interrupts.
It is advisable that the ABEXIT value in the site options table be set to NO, and to use the PARM ABEXIT(SNAP or NOSNAP) during development as a debugging aid. Before moving the CA Easytrieve® program into production, remove the PARM ABEXIT override. This will reduce overhead for production applications. |
So yes says it produces a dump but where to as it ain't coming out in the same place as all the other debug type info.
I've also tried running with SNAP and NOSNAP and the SYSPRINT is the same size so clearly no output there. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1205
Location: Dublin, Ireland
|
|
|
|
Following the sound and practical advice given, a quick search in the documentation would suggest that the output would be directed to the //SYSSNAP DD dataset.
Garry. |
|
| Back to top |
|
|
|
|
