View previous topic :: View next topic
|
Author |
Message |
Benchwarmer
New User
Joined: 16 Jul 2016 Posts: 22 Location: desk
|
|
|
|
Receiving following error in a existing CICS transaction
Quote: |
An SFE, SA or MF order was received with an unrecognized attribute type. The error occurred at location 0x424 in the write. |
Once the user received error on different location
Quote: |
An SFE, SA or MF order was received with an unrecognized attribute type. The error occurred at location 0x41e in the write. |
Sending the map via below command
Code: |
EXEC CICS
SEND MAP('MAPNAME')
MAPSET('MAPSET')
FROM(COPYOUT) ERASE
CURSOR
END-EXEC. |
I would like to know how to map this location in physical or symbolic map to determine the field causing the issue.
Did not find anything that talks about what am looking for. Any pointers will be helpful. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Are you sure the map storage is initialized to nulls before sending the map? There should be a MOVE LOW-VALUES TO MAPNAMEO somewhere before the SEND MAP. |
|
Back to top |
|
|
Benchwarmer
New User
Joined: 16 Jul 2016 Posts: 22 Location: desk
|
|
|
|
Yes, the map storage is initialized. I don't see an issue with that. This issue does not happen often. There is no distinguishable scenario causing the issue. It happens randomly. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
There is no distinguishable scenario causing the issue. It happens randomly. |
Which is a strong indication that the issue is caused by a storage overlay in the program. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
Back to top |
|
|
Benchwarmer
New User
Joined: 16 Jul 2016 Posts: 22 Location: desk
|
|
|
|
In the program, a working storage variable is initialized with values from DB2 table for first time the transaction is initiated. In the consecutive interactions of the transaction, the same working storage variable is moved into the map.
This is a protected field in MAP.
I suspect this could be the cause for data stream error. Any pointers? |
|
Back to top |
|
|
Benchwarmer
New User
Joined: 16 Jul 2016 Posts: 22 Location: desk
|
|
|
|
NOTE: The transaction is re-entrant and value of the working storage variable in question is not stored in communication area. |
|
Back to top |
|
|
|