|
View previous topic :: View next topic
|
| Author |
Message |
genesis786
Active User
Joined: 28 Sep 2005
Posts: 210
Location: St Katherine's Dock London
|
|
|
|
Hi All - we are facing a tricky situation here. Our host application is failing at times with
| Code: |
Command ===> Scroll ===> CSR
Abbrev Short Full - TRANID: ZESR CICS ABEND: ASRA LQ05 2
10695 QR AP 1942 APLI *EXC* Program-Check START_PROGRAM,XZQVDPLR,C
10695 QR AP 0790 SRP *EXC* PROGRAM_CHECK
|
and at times with a storage violation abend [4094 - reason 0018]
| Code: |
Called-from-address 00062CC2 : Module CEECCICS + X'2D32'
41605 QR SM 0D01 SMMF ENTRY FREEMAIN 2E850DA8,EXEC,USER
41605 QR SM 0D02 SMMF EXIT FREEMAIN/OK USER storage at 2E850DA8
41605 QR AP 00E1 EIP EXIT FREEMAIN OK
41605 QR AP 00E1 EIP ENTRY ABEND
Called-from-address 000627F6 : Module CEECCICS + X'2866'
41605 QR AP 0741 ABAB ENTRY CREATE_ABEND_RECORD 0018C58C , 00000040,PZMV
41605 QR SM 0301 SMGF ENTRY GETMAIN 264,NO,00,TACB,CICS
|
I have the fault analyzer dump and IPCS dump with me to look at, but i am doing literally only that. Haven't been able to locate any helpful thing which can help in deciphering how to read through the dump information.
Can someone please point me to the right direction where i can find how to make use of FAZ dump and IPCS dump information? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
storage violations are pretty tricky to debug, the task abending could be the innocent victim of somebody else bug
to see if the task abended is the culprit
review the <active> program chain for array overflow ( unchecked indexes )
otherwise
in the dump look at the <violated> storage area and see if You can find evidence of data related to some other transaction and start reading the other transaction program
a pretty high percentage of errors can usually be found by just rereading the involved programs ( walk thru ) |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
The trace indicates a good FREEMAIN. Afterwards, is the program attempting to address any of the previously freed area? Is the FREEMAIN being issued by the program? If not, then CICS is issuing it at task or enclave termination.
A SOC4 is a Protection exception, where the program is attempting to address storage that is no longer or never has been "legally" addressable. It's similar to a Storage Violation but not as severe and should only affect the resulting program and not trample on storage associated with another program/programs in the mix.
It would make sense that this happens from time-to-time as it's a timing issue, where sometimes the storage can be addressed without error and sometimes not. |
|
| Back to top |
|
|
|
|
