ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » problem with starting the Queue manager

Post new topic  Reply to topic
 problem with starting the Queue manager « View previous topic :: View next topic » 
Author Message
surendra
PostPosted: Fri Jul 16, 2004 10:49 pm    Post subject: problem with starting the Queue manager Reply with quote

Newbie

Joined: 16 Jul 2004
Posts: 7

WHEN I USED THE FOLLOWING COMMANDS IT SAYS THE QMGR ALREADY EXISTS AND WHEN I SEE IN THE MQ EXPLORER THE QMGR IS CREATED BUT ITS NOT STARTED. WHEN I TRIED TO START FROM THE MQ EXPLORER, IT SHOWS THE FOLLOWING ERROR MESSAGE.

ERROR CODE 71 STARTING MIPT/QUEUE MANAGER WEBSPHERE MQ SERVICE. THE SERVICE UNABLE TO START THE QUEUE MANAGER.WEBSPHERE WAS UNABLE TO DISPLAY THE ERROR MESSAGE 893.

COMMANDS START FROM HERE:

crtmqm MIPT
amqmdain start MIPT
runmqsc MIPT < LOADMIPT.TXT
amqmdain crttrm MIPT INIT.QUEUE
amqmdain start MIPT



THIS IS THE LOADMIPT.TXT FILE
*
* This file generated by SAVEQMGR V5.2.1 on 2003-05-09 at 16.10.45 hours.
*
* QMNAME (MIPT) +
* CRDATE (2003-05-09) +
* CRTIME (15.58.41) +
* ALTDATE (2003-05-09) +
* ALTTIME (16.03.16) +
* QMID (MIPT_2003-05-09_15.58.41) +
*
ALTER QMGR +
AUTHOREV(DISABLED) +
DEADQ(' ') +
DEFXMITQ(' ') +
DESCR('Trigger Example, by M-Invent') +
INHIBTEV(DISABLED) +
LOCALEV(DISABLED) +
MAXHANDS(256) +
MAXUMSGS(10000) +
PERFMEV(DISABLED) +
REMOTEEV(DISABLED) +
STRSTPEV(ENABLED) +
TRIGINT(60000) +
MAXMSGL(4194304) +
CHAD(DISABLED) +
CHADEV(DISABLED) +
CHADEXIT(' ') +
CLWLEXIT(' ') +
CLWLDATA(' ') +
REPOS(' ') +
REPOSNL(' ') +
CLWLLEN(100) +
FORCE

DEFINE QLOCAL ('INIT.QUEUE') +
* CRDATE (2003-05-09) +
* CRTIME (15.58.55) +
* ALTDATE (2003-05-09) +
* ALTTIME (16.03.16) +
DESCR('WebSphere MQ Default Local Queue') +
PUT(ENABLED) +
DEFPRTY(0) +
DEFPSIST(NO) +
SCOPE(QMGR) +
GET(ENABLED) +
MAXDEPTH(5000) +
MAXMSGL(4194304) +
SHARE +
DEFSOPT(SHARED) +
MSGDLVSQ(PRIORITY) +
HARDENBO +
USAGE(NORMAL) +
NOTRIGGER +
TRIGTYPE(FIRST) +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGDATA(' ') +
PROCESS(' ') +
INITQ(' ') +
RETINTVL(999999999) +
BOTHRESH(0) +
BOQNAME(' ') +
QDEPTHHI(80) +
QDEPTHLO(20) +
QDPMAXEV(ENABLED) +
QDPHIEV(DISABLED) +
QDPLOEV(DISABLED) +
QSVCINT(999999999) +
QSVCIEV(NONE) +
DISTL(NO) +
CLUSTER(' ') +
CLUSNL(' ') +
DEFBIND(OPEN) +
REPLACE

DEFINE QLOCAL ('INPUT.QUEUE') +
* CRDATE (2003-05-09) +
* CRTIME (15.58.55) +
* ALTDATE (2003-05-09) +
* ALTTIME (16.03.16) +
DESCR('WebSphere MQ Default Local Queue') +
PUT(ENABLED) +
DEFPRTY(0) +
DEFPSIST(NO) +
SCOPE(QMGR) +
GET(ENABLED) +
MAXDEPTH(5000) +
MAXMSGL(4194304) +
SHARE +
DEFSOPT(SHARED) +
MSGDLVSQ(PRIORITY) +
HARDENBO +
USAGE(NORMAL) +
TRIGGER +
TRIGTYPE(FIRST) +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGDATA(' ') +
PROCESS('SEND.NOTE') +
INITQ('INIT.QUEUE') +
RETINTVL(999999999) +
BOTHRESH(0) +
BOQNAME(' ') +
QDEPTHHI(80) +
QDEPTHLO(20) +
QDPMAXEV(ENABLED) +
QDPHIEV(DISABLED) +
QDPLOEV(DISABLED) +
QSVCINT(999999999) +
QSVCIEV(NONE) +
DISTL(NO) +
CLUSTER(' ') +
CLUSNL(' ') +
DEFBIND(OPEN) +
REPLACE

DEFINE PROCESS ('SEND.NOTE') REPLACE +
* ALTDATE (2003-05-09) +
* ALTTIME (16.03.24) +
DESCR(' ') +
APPLTYPE(WINDOWSNT) +
APPLICID('C:\SENDNOTE.BAT') +
USERDATA(' ') +
ENVRDATA(' ')

IMMEDIATE HELP WOULD BE APPRECIATED. THANKS.
Back to top
View user's profile Send private message
kirani
PostPosted: Fri Jul 16, 2004 11:15 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Are there any messages logged in system error log?
Please don't type complete post in UPPERCASE.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
jefflowrey
PostPosted: Sat Jul 17, 2004 5:30 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You should not mix useages of amqmdain and ctrmqm/strmqm etc.

Use either the GUI (MQExplorer, MQServices) and amqmdain [b]or[/b[ use crtmqm, strmqm, etc.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
surendra
PostPosted: Sat Jul 17, 2004 8:19 am    Post subject: Reply with quote

Newbie

Joined: 16 Jul 2004
Posts: 7

i found the following error in the error logs.
7/17/2004 01:02:27
AMQ7472: Object MIPT, type catalogue damaged.

EXPLANATION:
Object MIPT, type catalogue has been marked as damaged. This indicates that the
queue manager was either unable to access the object in the file system, or
that some kind of inconsistency with the data in the object was detected.
ACTION:
If a damaged object is detected, the action performed depends on whether the
queue manager supports media recovery and when the damage was detected. If the
queue manager does not support media recovery, you must delete the object as no
recovery is possible. If the queue manager does support media recovery and the
damage is detected during the processing performed when the queue manager is
being started, the queue manager will automatically initiate media recovery of
the object. If the queue manager supports media recovery and the damage is
detected once the queue manager has started, it may be recovered from a media
image using the rcrmqmobj command or it may be deleted.
Back to top
View user's profile Send private message
Rockon
PostPosted: Sun Jul 18, 2004 2:08 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2004
Posts: 43

surendra wrote:

ACTION:
If a damaged object is detected, the action performed depends on whether the
queue manager supports media recovery and when the damage was detected.
If the queue manager supports media recovery and the damage is
detected once the queue manager has started, it may be recovered from a media
image using the rcrmqmobj command or it may be deleted


Q1.What does it mean by media recovery?
Q2.What if you donot have QMGR that has media recovery support?
Q3.Is it possible to load this support from someplace?


Last edited by Rockon on Wed Jan 05, 2005 4:43 pm; edited 1 time in total
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Jul 18, 2004 5:33 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Media recovery support is given with LINEAR Logging.

Anyway why do you start the QMGR twice ?
You did not start a listener ?
Quote:
crtmqm MIPT
amqmdain start MIPT
runmqsc MIPT < LOADMIPT.TXT
amqmdain crttrm MIPT INIT.QUEUE
amqmdain start MIPT

Your queue manager is already started and running otherwise you would not have been able to run the loadmipt.txt script !

My guess is that the second start was intended to start a listener...
Now I do not know what type of msgs amqmdain will give if you try to start an already running qmgr...

Why not just create the qmgr using MQExplorer. You can then still load the objects running the script from the command line. All other commands (like trigger monitor) etc should then be run from MQExplorer.
If that works fine read up on amqmdain and make sure you get it right.


Just my 2 cts
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » problem with starting the Queue manager
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.