|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Tandem NonStop TriggerMON FDC with ProbeID ZL174035 |
« View previous topic :: View next topic » |
Author |
Message
|
DeadLetter |
Posted: Mon Mar 27, 2017 5:22 am Post subject: Tandem NonStop TriggerMON FDC with ProbeID ZL174035 |
|
|
Novice
Joined: 15 Nov 2016 Posts: 11
|
Hi all,
has anybody an idea, what this probe ID is?
Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday March 27 14:07:07 MET DST 2017 |
| Host Name :- XXXXX (NONSTOP_KERNEL J06.20) |
| PIDS :- 5724A3901 |
| LVLS :- 531.12 FP53112 |
| Product Long Name :- WebSphere MQ for HP NonStop Server |
| Vendor :- IBM |
| Probe Id :- ZL174035 |
| Application Name :- MQM |
| Component :- zlgMainThread |
| Build Date :- May 31 2016 |
| CMVC level :- L20160531-1345 |
| Build Type :- IKAP - (Production) |
| UserID :- 123,255 (MQM.MANAGER) |
| Program Name :- [...] |
| Process :- 0,712 $X0028 OSS(587202574) |
| QueueManager :- XXXXX |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (0) |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
|
|
|
Back to top |
|
 |
mqjeff |
Posted: Mon Mar 27, 2017 5:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I'm sure IBM Support does.
Google seems to have a lot of thoughts on the probe type MSGAMQ6118 _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
DeadLetter |
Posted: Tue Mar 28, 2017 1:30 am Post subject: |
|
|
Novice
Joined: 15 Nov 2016 Posts: 11
|
Hi all,
PMR is ongoing and we were asked for a detailed debug report.
Nevertheless we did some playing around and found this:
http://www-01.ibm.com/support/docview.wss?uid=swg1IT18767
Looks like our issue, but the Probe ID neither the FDC Output is mentioned in the issue.
So it might be the new released FixPack 5.3.1.13 in our case.
I will report, if we got the final solution.
br
Carsten |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Mar 28, 2017 4:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Ask for an ifix for that APAR, see if it helps.
Or ask through the PMR if it'sthe same issue... _________________ chmod -R ugo-wx / |
|
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
|
|
|
|