| Author |
Message
|
| dencio |
 Posted: Fri Dec 19, 2003 10:14 am Post subject: dspmq shows % in Queue Manager name |
 |
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
Hi,
I need help in determining this minor problem I'm seeing on our Queue Manager. I have created a queue manager and when I do a dspmq command, it shows this:
QMNAME(%TEST_QueueManager)% STATUS(Running)
There are % signs that appears on the Queue Manager name. I tried to delete the Queue Manager and re-create it but it's still the same. I created the same queue manager on another machine but when the dspmq command is ran, it does not show the % signs.
Appreciate any help.
Thanks! |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Dec 19, 2003 3:21 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
it would help if you let us know the platform and the version of mq / csd level.
Michael |
|
| Back to top |
|
|
| dencio |
| Posted: Mon Dec 22, 2003 5:55 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
[quote="MichaelDag"]it would help if you let us know the platform and the version of mq / csd level.
Michael[/quote]
Sorry, MQSeries is running on a Sun machine with Solaris 8. MQ version is 5.3 with CSD 3. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Dec 22, 2003 2:43 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| What are your entries in /var/mqm/mqs.ini file. |
|
| Back to top |
|
|
| dencio |
| Posted: Tue Dec 23, 2003 6:18 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
| vennela wrote: |
| What are your entries in /var/mqm/mqs.ini file. |
I've checked the file too and it has the correct Queue Manager name. I just wonder where does the % comes from. But anyway, here's the contents of the mqs.ini.
AllQueueManagers:
DefaultPrefix=/var/mqm
ClientExitPath:
ExitsDefaultPath=/var/mqm/exits
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
QueueManager:
Name=TEST_QueueManager
Prefix=/var/mqm
Directory=TEST_QueueManager |
|
| Back to top |
|
|
| dencio |
| Posted: Tue Dec 23, 2003 6:22 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
Even the log file shows the % signs.
-------------------------------------------------------------------------------
12/18/03 17:08:37
AMQ8003: WebSphere MQ queue manager '%FACM_QueueManager' started.
EXPLANATION:
WebSphere MQ queue manager '%FACM_QueueManager' started.
ACTION:
None.
-------------------------------------------------------------------------------
12/18/03 17:08:37
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
12/18/03 17:08:38
AMQ7467: The oldest log file required to start queue manager %FACM_QueueManager
is %S0000000.LOG.
EXPLANATION:
The log file %S0000000.LOG contains the oldest log record required to restart
the queue manager. Log records older than this may be required for media
recovery.
ACTION:
You can move log files older than %S0000000.LOG to an archive medium to release
space in the log directory. If you move any of the log files required to
recreate objects from their media images, you will have to restore them to
recreate the objects.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| Leafar |
| Posted: Tue Dec 23, 2003 7:17 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
Try creating a new DUMMY qmgr, to see if the problem persist.
Is the only qmgr in this machine? |
|
| Back to top |
|
|
| dencio |
| Posted: Tue Dec 23, 2003 7:23 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
| Leafar wrote: |
Try creating a new DUMMY qmgr, to see if the problem persist.
Is the only qmgr in this machine? |
Yes, it is. I've tried creating a DUMMY qmgr but it's still the same (see below).
% dspmq
QMNAME(%TEST_QueueManager)% STATUS(Running)
% crtmqm DUMMY
WebSphere MQ queue manager created.
Creating or replacing default objects for %DUMMY.
Default objects statistics : %31 created. %0 replaced. %0 failed.
Completing setup.
Setup completed.
% dspmq
QMNAME(%TEST_QueueManager)% STATUS(Running)
QMNAME(%DUMMY)% STATUS(Ended immediately)
% dltmqm DUMMY
WebSphere MQ queue manager '%DUMMY' deleted. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Dec 23, 2003 7:56 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Looks like an OS problem. Some character is being substituted by "%" I guess. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 23, 2003 8:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Do you get the same problem when creating queues? (Probably not, since you are in a runmqsc session).
What happens if you run the following command: touch testfile.txt
Does it create %testfile.txt?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| dencio |
| Posted: Tue Dec 23, 2003 8:12 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2003
Posts: 7
|
| PeterPotkay wrote: |
Do you get the same problem when creating queues? (Probably not, since you are in a runmqsc session).
What happens if you run the following command: touch testfile.txt
Does it create %testfile.txt? |
I tried creating the file testfile.txt but it did not put a % in the file name.
% touch testfile.txt
% ls -l testfile.txt
-rw-r--r-- 1 mqm mqm 0 Dec 23 11:09 testfile.txt
%
I'm thinking that the WMQ itself is causing it. I did not install WMQ the first time and I'll find out if I could re-install it. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Dec 23, 2003 8:20 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Hmmmmm.
Ya know, I once had a problem where i was trying to upgrade MQ to 5.3 on a Solaris machine.
I could not run the license script. The OS kept prefixing (or suffixing) the path to the license script with some funky character, plus the number 2. We could not get around it. I tried putting in another 5.3 CD in, and now the OS was adding the funky char plus the number 3!  
Then I happened to mention to the team that the CD for MQ 5.2 was still in the CD tray when I went to put in the 5.3 CD. That Solaris machine was rebooted many times with that 5.2 CD in the tray.
We suspected that the OS somehow had it burned into its little brain that the 5.2 CD was still in that CD tray.
So we rebooted the machine making sure the CD tray was empty.
We then tried the 5.3 install again and it worked!
Maybe this has nothing to do with your problem, but you might want to try the Bill Gates solution and reboot this machine. Maybe the problem will go away.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
