While working on the Asynchronous Consumption of Messages in CICS, I found out this issue while putting messages to a queue (from which MQ passes the data to callback consumer routine in the form of channels and container over the default channel - MQ_ASYNC_CONSUME.
I noticed in my callback consumer module - that as soon as its GETs the container 'Buffer' - it is supposed to get the refreshed copy. But, if the 'now' data area is changed to something not-spaces/blanks, then it gets a refreshed copy.
But, when that data area is changed to blanks/spaces, then it doesn't refreshes that particular area. However, in the same LUW -it does gets the refreshed copy of other fields if I change them to non-blanks characters.
Eg: first PUT to MQ:
status-type - Processed
status-reason-desc - 0080
Buffer container has the same value for these two fields.
But, now in second try, I supply these values while putting to the queue:
status-type - Rejected
status-reason-desc - <blanks>.
In this case, it does takes the new value of status-type supplied to the queue, but it doesn't takes the new <blank> value of status-reason-desc field. That is, the value of status-reason-desc is still '0080' which ideally should have been <blanks>.
Does anybody has any idea on such a behaviour. Does it have to do anything with GMO fields?
Buffer container issue in Async Message Consumption in CICS
-
- Similar Topics
- Replies
- Views
- Last post
-
- 13
- 8462
-
by valeca
View the latest post
Fri Sep 30, 2022 11:22 pm
-
-
SYNCSORT DATASORT message SYT076E
by f1_lemaner » Thu Dec 23, 2021 11:12 pm » in DFSORT/ICETOOL/ICEGENER - 5
- 1885
-
by f1_lemaner
View the latest post
Fri Dec 24, 2021 2:23 pm
-
-
-
How can I copy message queue files (LGMSG,SHMSG) in V9R1
by futohomok » Thu Jul 27, 2023 5:54 pm » in IMS DB/DC - 6
- 2142
-
by futohomok
View the latest post
Thu Aug 03, 2023 1:21 pm
-
-
- 1
- 2078
-
by prino
View the latest post
Mon Sep 05, 2022 2:12 am
-
- 3
- 5116
-
by jrcox
View the latest post
Wed Jul 29, 2020 7:52 pm