|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Tandem Tech's have you ever run accrss this ? |
« View previous topic :: View next topic » |
Author |
Message
|
hankknowles |
Posted: Fri May 21, 2004 8:46 am Post subject: Tandem Tech's have you ever run accrss this ? |
|
|
 Centurion
Joined: 18 Aug 2003 Posts: 114
|
2072 X’0818’ MQRC_SYNCPOINT_NOT_AVAILABLE
Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT
was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to
honor the request. If the queue manager does not support units of work, the SyncPoint
queue-manager attribute will have the value MQSP_NOT_AVAILABLE.
This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an
external unit-of-work coordinator is being used. If that coordinator requires an explicit call to
start the unit of work, but the application has not issued that call prior to the MQGET,
MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned.
v On OS/400, this reason codes means that OS/400 Commitment Control is not started, or is
unavailable for use by the queue manager.
v On z/OS, this reason code does not occur.
Corrective action: Remove the specification of MQGMO_SYNCPOINT or
MQPMO_SYNCPOINT, as appropriate.
On OS/400, ensure that Commitment Control has been started. If this reason code occurs after
Commitment Control has been started, contact your systems programmer. |
|
Back to top |
|
 |
mqonnet |
Posted: Fri May 21, 2004 9:49 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Look at the ems log to see if you had any events around the time you got this reason code. There could be variety of reasons you end up into this situation.
But usually it would be, your transaction was aborted by either user or tmf.
Your transaction went over the autoabort time set in tmf and caused the transaction to be obsolete.
Bottom line is, MQ is complaining saying that you dont have a valid transaction when Mq was expecting one.
BTW how did you get this. I mean what api call and under what circumstances.
Cheers
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
hankknowles |
Posted: Fri May 21, 2004 10:01 am Post subject: Thanks |
|
|
 Centurion
Joined: 18 Aug 2003 Posts: 114
|
Well this here message comes from an encryptdecrpt routine that was created and used in lot's of application areasin the bank. This is a development system.
The security folks built this thing and I have to sit between the developers and god knows who else and look and peek around to try and help find an answer. I am not JAVA literate merely a Tandem S/A that has all this hung around my neck.... We have to do this till IBM release V 5.3 or whatever they decide to call it!
Not complaing mind you been in the business 28 years and have been on IBM, AS/400, Netware, RT PC ( baby AIX) and now the Nonstop servers.
The other issue I asked about was resolved when I went back through the last steps of the MA88 and re ran the nld -change stuff. |
|
Back to top |
|
 |
mqonnet |
Posted: Fri May 21, 2004 10:11 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Hank,
"Well this here message comes from an encryptdecrpt routine that was created and used in lot's of application areasin the bank. This is a development system.
The security folks built this thing and I have to sit between the developers and god knows who else and look and peek around to try and help find an answer"
---As i mentioned earlier, look in the ems logs and you are sure to find events around the time you got this reason code. Possibility of FFST is also there. Look for it and you may find Tandem FSE error code in the ffst. That would help too.
"I am not JAVA literate merely a Tandem S/A that has all this hung around my neck.... We have to do this till IBM release V 5.3 or whatever they decide to call it!
"
Hope i could be more help than this. :(
Good luck!!!
Cheers
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
Back to top |
|
 |
hankknowles |
Posted: Fri May 21, 2004 10:13 am Post subject: Thanks |
|
|
 Centurion
Joined: 18 Aug 2003 Posts: 114
|
Well you were right on target - transaction got too old, and the proc blew up after 10 threads created... The developers are now involved... Thanks for the 30-30 shells
Cheers!
Have a good weekend!  |
|
Back to top |
|
 |
hankknowles |
Posted: Thu Jun 24, 2004 6:04 am Post subject: The solution |
|
|
 Centurion
Joined: 18 Aug 2003 Posts: 114
|
God I hate being the middle man....... After much hemming and complaining and trying this and that it turns out the when he opened up his app he was doing a beginTX and he kept looping waiting for work to do .... After two hours TMF aborted the transaction he started. Thus the 2255 and 2072 errors logged.
So we engaged IBM finally after they shot their wad and IBM came back and told him to commit and close the transaction. That took care of the issue and the application is now happy as a clam.
IMHO
One would think that this product and java are not platform dependant... NOT with NSK it seems the defaults are screwed backwards in most cases when you accept the defaults params for a NT say.... IN NSK lots of the defaults mean the oppsite..... GEEZ off my soap box!!!
Y'all have a fine week ! |
|
Back to top |
|
 |
mqonnet |
Posted: Thu Jun 24, 2004 7:21 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Hank,
Any product, if uses the features of the O/s, is limited in usage. It has nothing to do with the product in particular. Even if you remove MQ from this whole picture and write a pure java app on NSK with begin/end transactions(may be using c wrappers), you would end up with the same limitation at the end of the day.
So, this is purely O/s specific issue rather than Mq/java issue. IMHO.
Good luck.
Cheers
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
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
|
|
|
|