| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| iSeries STRMQMCSVR error X'837'. Help anyone? |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bernard |
 Posted: Thu Nov 10, 2005 7:27 am Post subject: iSeries STRMQMCSVR error X'837'. Help anyone? |
 |
|
Newbie
Joined: 10 Nov 2005
Posts: 5
Location: London
|
Hi can anyone help me solve the following problem:-
We migrated to a new iSeries 810 and ever since then we cannot start our MQ command server. We are running O/S V5R2.
The error we get when running the STRMQMCSVR command is:-
X'00000837'
which equates to this description:-
2103 MQRC_ANOTHER_Q_MGR_CONNECTED
I have noticed that in the root directory: \QIBM\UserData\mqm\qmgrs\
there are now 2 folders for our queue manager (QP22), the original folder QP22 and what looks like a new system generated folder QP22.000, this new folder is the one our QP22 queue manager refers to. Could it be that the system thinks the command server is still connected to the old folder?
In the past we have had MQ problems that have required clearing out of various files from the iSeries IFS root directory, are we looking at a similar fix for this problem?
Any help would be appreciated.
Thanks & regards
Bernard |
|
| Back to top |
|
 |
| Toronto_MQ |
| Posted: Thu Nov 10, 2005 9:10 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
The QP22.000 folder implies you had a queue manager named QP22 previously, and deleted it but it was never completely removed. Assuming this is a test system, I would advise deleting your new QP22 queue manager to get rid of the QP22.000 IFS directory and then manually cleaning up the old queue manager... to do this delete the IFS directory QP22, remove any QP22 entries from /QIBM/Userdata/mqm/mqs.ini, and delete the library (you may also have multiple QP22 libraries).
May as well start with a clean system... see if this gets rid of your 2103.
Steve |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Thu Nov 10, 2005 9:17 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
I also found this item which seems to be a pretty good hit. Recommends the same fix as above, however also provides an alternative if deleting and recreating is not an option. I would advise you try to clean it out if at all possible so you start fresh.
Just my 2 cents
Steve
Item RTA000180713
Source..........: PDDBN PDDBN
Last updated....: 20050701
Abstract........: Unable to start the command server (STRMQMCSVR) fails with
USERS: ALL USERS with CICS
PROBLEM SUMMARY:
When attempting to start the command server job using the STRMQMCSVR
command, message AMQ8101 RC2103 (MQRC_ANOTHER_Q_MGR_CONNECTED)
is generated.
SOLUTION:
Requested enduser to create and start another queue manager, then
issue the
STRMQMCSVR command for that qmgr. Same error message was generated.
No FDCs were generated, however, found several queue manager
directories for the BAMTAS16 and TEST queue manager listed under the
path '/qibm/userdata/mqm/qmgrs' . I suspect that under one of these
directory paths the qmstatus.ini indicates the command server is
RUNNING. Since the TEST queue manager failed, another queue manager
was
created that has never existed on the system. Enduser was able to
create and start the
queue manager . Next they started the command server for the queue
manager successfully.
Recommend the MQ Administrator should delete the queue manager , along
with removing the duplicate queue manager libraries and directories
under the qmgrs sub-directory, if
possible.
If the queue manager cannot be deleted and recreated, then they must
review all the
qmstatus.ini streamfile and modify the CmdSvrStatus setting to have a
status of Ended.
NOTE: The status is case sensitive.
To check the status of the command server:
Type, edtf '/qibm/userdata/mqm/qmgrs//qmstatus.ini'
QueueManagerStatus:
. CurrentStatus=Running
. CmdSvrStatus=Ended <---------------
NOTE: For this enduser's environment you will need to review the
qmstatus.ini file each queue manager listed under the qmgrs
sub-directory |
|
| Back to top |
|
|
| Bernard |
| Posted: Fri Nov 11, 2005 5:47 am Post subject: More problems! |
|
|
Newbie
Joined: 10 Nov 2005
Posts: 5
Location: London
|
Hi,
Thanks for your help. Unfortunately I am dealing with a production system for a bank so cannot risk stopping the transaction flow. I have previously tried the changing of the qmstatus.ini file with no results. However I have created a new qmgr and successfully started and stopped the command server so it does work on other qmgrs. I have stopped and restarted the production qmgr and interestingly I now get a different error msg X'40406109' when running STRMQMCSVR, here is the FDC, maybe someone knows what this means, I cant find anything for the above err msg, I have the full trace details if required, thanks for any help:-
+-----------------------------------------------------------------------------
|
| MQSeries First Failure Symptom Report
| =====================================
|
| Date/Time :- Friday November 11 12:10:05 2005
| Host Name :- LONPROD.LON02
| PIDS :- 5733A38
| LVLS :- 520
| Product Long Name :- MQSeries for AS400
| Vendor :- IBM
| Probe Id :- XC037003
| Application Name :- MQM
| Component :- xcsExecProgram
| Build Date :- Dec 10 2002
| UserID :- 00000117 (QSECOFR1)
| Program Name :- STRMQCSV QSECOF
| Job Name :- 767588/QSECOFR1/STRMQCSV
| Activation Group :- 117 (QMQM) (QMQM/STRMQCSV)
| Process (MQPIDs) :- 00124385 (0, 12, 0, 0)
| Thread :- 00000001
| QueueManager :- QP22
| Major Errorcode :- OK
| Minor Errorcode :- OK
| Probe Type :- INCORROUT
| Probe Severity :- 4
| Probe Description :- AMQ6125: An internal MQSeries error has occurred.
|
+-----------------------------------------------------------------------------
MQM Function Stack
pcmSPIStrCmdSvr
xcsExecProgram
xcsFFST |
|
| Back to top |
|
|
| paulgroo |
| Posted: Tue Nov 15, 2005 4:57 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hi,
I user MQ on iSeries also and I've come across a few of these wierdo little problems. Is this still happening? If so, try removing the directory QP22.000 . There may also be some files in the shmem directory within:
\QIBM\UserData\mqm\QP22\...
Restart that badboy, and check the error logs for any more errors. It sounds like you might have restored the queue manager from the backup of another system and a few settings arent correct.
Let me know how you get on. I have a few more ideas... |
|
| 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
|
|
|
|
