View previous topic :: View next topic
|
Author |
Message |
jgantena
New User
Joined: 13 Aug 2008 Posts: 8 Location: Hyderabad
|
|
|
|
hi,
Can anyone tell me why iam getting this kind of error.
error is like this
"an attempt to change an area that does not belong to this task.
Possible system damage has been prevented. "
Actual functionality that i am following is same map is used to populate upto 30 sequences i.e.,18 in one page and 12 in next page.
when values are added in new screen control is going to receive screen to update the values for 1st 18 sequences whereas for next 12 sequences i am getting the above quoted message.
can any one help me regarding this. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
did You care to search the manual for the message meaning and implications
if the message starts with DFH it is a cics message and should be researched in the CICS manuals
if not ask Your peers about the relevant documentation to look at |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
You receive this message when you are doing what ???
Usually, messages do have a message number (like DFHAC2236 for example).
Are you running Intertest or Xpediter ? |
|
Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006 Posts: 475
|
|
|
|
Quote: |
"an attempt to change an area that does not belong to this task.
Possible system damage has been prevented. "
|
sounds like a storage violation.
contact your CICS systems programmer. |
|
Back to top |
|
|
jgantena
New User
Joined: 13 Aug 2008 Posts: 8 Location: Hyderabad
|
|
|
|
sir i am running intertest |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
sir i am running intertest
|
Which doesn't matter. You're getting a storage violation attempting to write storage your task doesn't own; you need to debug your program and find out why it's hitting storage it doesn't own (table overflow, invalid address, PIC S9904) COMP where PIC S9(08) COMP is required, etc). |
|
Back to top |
|
|
|