|
View previous topic :: View next topic
|
| Author |
Message |
itjagadesh
New User
Joined: 05 Dec 2006
Posts: 89
Location: chennai
|
|
|
|
Hi Team,
I have following issue in my Eazytrive program.
1)I am getting SOC7 abend in Eazytrive program but i am not getting SYSDUMP(To find which statement or address in program caused abend)
in Job SPOOL.
Can anyone please let me know how to get address register of abended statement in eazytrive program or SYSDUMP in JOb Spool.?
2)I have added DEBUG statement in PARM ,still i am not getting abended statement.
Am i missing anything in program?
Please help me on this to resolve SOC7 abend
Thanks
Jagadesh |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Which release of Easytrieve are you using?
| Quote: |
| I have added DEBUG statement in PARM ,still i am not getting abended statement. |
How did you do this? It will probably help if you post the PARM you are using for this run.
Is this a new program or did it sudenly abend after being in use for some time?
How confident are you that the file layout is correct? Can the data be trusted or is this data from some external source and may possibly contain invalid values? |
|
| Back to top |
|
|
itjagadesh
New User
Joined: 05 Dec 2006
Posts: 89
Location: chennai
|
|
|
|
Hi Dick,
Thanks
1) Which release of Easytrieve are you using?
CA-EASYTRIEVE PLUS-6.4
2)How did you do this? It will probably help if you post the PARM you are using for this run.
PARM SSID('ID') DEBUG (STATE FLOW)
3)Is this a new program or did it sudenly abend after being in use for some time?
Its existng program but modified for some requirement
I agree that we included some layout change and invalid data came.
But my query is why i am not getting SYSDUMP in Job Spool or offset value of abended statement? is there any option to get that?
Thanks
Jagadesh |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
From the 6.4 manual:
| Quote: |
| STATE saves the statement number of the statement currently being executed. The statement number is then printed in the associated abnormal termination messages. |
The statement number should be in the output. From the example in the same manual:
| Quote: |
If the STATE or FLOW options were active, the error analysis report contains the
statement number (27) in the message.
27 *******A006 PROGRAM INTERRUPT - CODE 7 (DATA EXCP) |
27 is not your statement, but the one from the example.
| Quote: |
| why i am not getting SYSDUMP in Job Spool or offset value of abended statement? is there any option to get that? |
If your system has abendaid or something similar installed, additional diagnostic info would be created.
If you use the CLIST option of DEBUG, you may get additonal info that will help. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| You've mentioned SYSDUMP a couple of times. Did you really mean SYSUDUMP? |
|
| Back to top |
|
|
itjagadesh
New User
Joined: 05 Dec 2006
Posts: 89
Location: chennai
|
|
|
|
Hi All,
I am sorry i mentioned wrongly SYSDUMP instead of SYSUDUMP.
Thanks Terry.
I am not getting anything in Abended Job.(geting only SYSPRINT) not getting SYSUDUMP.
So its difficult to find abended statement without Offset or address location of abended statement.
But finally using display statement only i have identified that some junk value moved to some variable.But took me lot of time.
Thanks a lot for all of you particpated.
Thanks
Jagadesh |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| So its difficult to find abended statement |
As i mentioned earlier - the abended statememt is presented by Easytrieve. Keep in mind that this is not COBOL and errors are not shown exactly the same way.
You will waste lots and lots of time until you become familiar with what is available in the environment you are working in (rather than some other environment).
There is also a way to find the offset using Easytrieve - it is just done differently than COBOL. It may be helpful as a learning process to use your already solved abend to understand other features available for determining the problem statement/data.
Good to hear it is working - thank you for letting us know  |
|
| Back to top |
|
|
|
|
