| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CICS/VSE goes SOS with a COBOL application using MQI |
« View previous topic :: View next topic » |
| Author |
Message
|
| pyoungkukim |
 Posted: Tue Sep 30, 2003 4:37 pm Post subject: CICS/VSE goes SOS with a COBOL application using MQI |
 |
|
Newbie
Joined: 16 Jul 2002
Posts: 3
|
Hi there,
We are trying to test a COBOL2 program which uses MQI. Every time that we try to send more then 500 messages (Aprox 200 bytes), the CICS partition goes SOS.
We are using VSE/ESA 2.4 LE 1.4 MQSeries 2.1.1 with COBOL2.
The logic of the program is fairly simple. The program is called (by LINK) from another COBOL CICS program, receives the datas through LINKAGE SECTION and put thos data on Remote Queue.
This SOS problem is somehow documented by IBM and we applied the PTF which is UQ57069 (PQ51123), but the problem persists.
We found a document from IBM which states that the program must do CICS SYNCPOINT after each MQPUT and before the MQCLOSE in order to prevent this SOS situation. However, I don't find any sample of it.
Does anyone have a sample code which can be shared with us?
I do not know that this SYNCPOINT will solve the problem as I could see that IBM has the SYNCPOINT line commented in their TTPTST2 sample program.
Anyways, does anyone have had similar situation? I would like to know how this problem can be solved.
The module, which was making getmain without freemain, was MQPSEND as long as I could see.
Thanks and I am looking forward for the help. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Tue Sep 30, 2003 5:12 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Firstly, you need to think about how you want the SYNCPOINT to work. Are you coordinating any of these messages with other resources. Do you need the ability to put multiple messages under a single SYNCPOINT.
If neither of the above are true, then the easiest solution would probably to add an EXEC CICS SYNCPOINT COMMIT (??) immediately after the MQPUT. That will ensure that the message is commited to the queue immediately, and (hopefully) the storage released.
If you do need either the coordination of messages and other resources, or you need multiple messages to be commited together, then you will need to examine your program logic to ensure that the EXEC CICS SYNCPOINT COMMIT is performed at the correct time.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
