MQ Issue, no jobs in QMQM sub-system

[gcraill]

Greetings, anyone know about MQ ?

We have a new LPAR and everything "seemed" installed ok (we are on V5R3M0) but we cannot get MQ up and running.

When we try to create a manager it fails, and we have noticed that there are no jobs started in sub-system QMQM.

Does anyone know any config type stuff we may have missed ?

Authorities on IFS, libraries, SBSD etc all seem fine. (same as other systems where MQ works)

I am sure the key is related to no jobs appearing in QMQM sbs.

All I get in the joblog is:

CRTMQM MQMNAME(Fish.Cake.001) DFTQMGR(*NO)
WebSphere MQ queue manager created.     
Error found on CRTMQM command. 

This creates the MQ Manager, but it does NOT start it ... when I try to start it I get ...

An unexpected error was encountered by a command. 
Error found on STRMQM command.                    
Message ID . . . . . . :   AMQ7047
Message . . . . :   An unexpected error was encountered by a command. 

Messages in the /QIBM/UserData/mqm/errors/AMQERR01.LOG log are

----- amqxfddx.c : 722 --------------------------------------------------------
12/14/11  15:18:20                                                             
AMQ6103: WebSphere MQ job submission error.                                    
                                                                               
EXPLANATION:                                                                   
                                                                               
  Cause . . . . . :   WebSphere MQ is unable to submit job CPF115302.          
                                                                                
                                                                                
----- amqxfddx.c : 673 -------------------------------------------------------- 
12/14/11  15:18:20                                                              
AMQ6184: An internal WebSphere MQ error has occurred.                           
                                                                                
EXPLANATION:                                                                    
                                                                                
  Cause . . . . . :   An internal MQ error has occurred on queue manager        
Fish.Cake.001 and the MQ error recording routine has been called. The failing     
process is process 65236.                                                       
  Recovery  . . . :   Use the standard facilities supplied with your system to  
record the problem identifier, and to save the generated output files. Contact  
your IBM support center.  Do not discard these files until the problem has been 
resolved.                                                                       
  Technical Description . . . . . . . . :   None.                               
----- amqxfddx.c : 722 -------------------------------------------------------- 
12/14/11  15:18:20                                                              
AMQ6103: WebSphere MQ job submission error.                                     
AMQ6103: WebSphere MQ job submission error.                                      
                                                                                 
EXPLANATION:                                                                     
                                                                                 
  Cause . . . . . :   WebSphere MQ is unable to submit job QMQM/AMQZXMA0.        
                                                                                 
                                                                                 
----- amqzslo0.c : 256 --------------------------------------------------------  
12/14/11  15:18:20                                                               
AMQ6118: An internal WebSphere MQ error has occurred (X'20006103')               
                                                                                 
EXPLANATION:                                                                     
                                                                                 
  Cause . . . . . :   An error has been detected, and the MQ error recording     
routine has been called.                                                         
  Recovery  . . . :   Use the standard facilities supplied with your system to   
record the problem identifier, and to save the generated output files. Contact   
your IBM support center.  Do not discard these files until the problem has been  
resolved.                                                                        
resolved.                                                                           
  Technical Description . . . . . . . . :   An internal return code was set to      
the value X'20006103'.                                                              
----- amqxfddx.c : 673 --------------------------------------------------------     
12/14/11  15:18:20                                                                  
AMQ6184: An internal WebSphere MQ error has occurred.                               
                                                                                    
EXPLANATION:                                                                        
                                                                                    
  Cause . . . . . :   An internal MQ error has occurred on queue manager            
Fish.Cake.001 and the MQ error recording routine has been called. The failing         
process is process 65236.                                                           
  Recovery  . . . :   Use the standard facilities supplied with your system to      
record the problem identifier, and to save the generated output files. Contact      
your IBM support center.  Do not discard these files until the problem has been     
resolved.                                                                           
  Technical Description . . . . . . . . :   None.                                   
----- amqxfddx.c : 722 -------------------------------------------------------- 

GC

[chrisr]

Re: MQ Issue, no jobs in QMQM sub-system

We have a cl program written to recreate all our MQ setup.. just in case. It's not something I look at very often, so it's not all that clear why some stuff is included but in essence this is what is done..

/*  Create MQSeries Message Queue Manager */
/* (first manager is sent with QDMFTQ = *YES) */
             CRTMQM     MQMNAME(&QMNAME) TEXT(&QMTEXT) DFTQMGR(&QMDFTQ)

/*  Start Queue Manager */
             STRMQM     MQMNAME(&QMNAME)

/*  Change Default Listener */
             CHGMQMLSR  LSRNAME(SYSTEM.DEFAULT.LISTENER.TCP) +
                          MQMNAME(&QMNAME) CONTROL(*QMGR) +
                          PORT(&QMPORT) IPADDR(&LOCTCP)

/*  Start Default Listener */
             STRMQMLSR  MQMNAME(&QMNAME) +
                          LSRNAME(SYSTEM.DEFAULT.LISTENER.TCP)

/*  Create MQSeries Server Connection Channel */
             CHGVAR     VAR(&QMCHLN) VALUE(&QMNAME *TCAT '.CLIENT.CH1')
             CRTMQMCHL  CHLNAME(&QMCHLN) CHLTYPE(*SVRCN) +
                          MQMNAME(&QMNAME) REPLACE(*YES) +
                          TRPTYPE(*TCP) TEXT('Server Connection +
                          Channel') MCAUSRID(QMQM) MAXMSGLEN(9194304)

/*  Create MQSeries Client Connection Channel */
             CRTMQMCHL  CHLNAME(&QMCHLN) CHLTYPE(*CLTCN) +
                          MQMNAME(&QMNAME) REPLACE(*YES) +
                          TRPTYPE(*TCP) TEXT('Client Connection +
                          Channel') TGTMQMNAME(&QMNAME) +
                          CONNAME(&LOCTCP *TCAT '(' *TCAT &QMPORT +
                          *TCAT ')') MAXMSGLEN(9194304)

/*  Change Attributes on Default Local Queue */
             CHGMQMQ    QNAME(SYSTEM.DEFAULT.LOCAL.QUEUE) +
                          MQMNAME(&QMNAME) DFTMSGPST(*YES)

/*  Change Maximum Message Length */
             CHGMQM     MQMNAME(&QMNAME) MAXMSGL(9124124)

/*  Create Dead Letter Message Queue for SYSTEM */
             CRTMQMQ    QNAME(INT.AU.SYSTEM.QL.DEAD.LETTER) +
                          QTYPE(*LCL) MQMNAME(&QMNAME) +
                          REPLACE(*YES) TEXT('Dead Letter Queue') +
                          PUTENBL(*YES) MAXDEPTH(10000) +
                          MAXMSGLEN(4194304) USAGE(*NORMAL)
             CHGMQM     MQMNAME(&QMNAME) +
                          UDLMSGQ(INT.AU.SYSTEM.QL.DEAD.LETTER)

/*  Create Message Queues for SYSTEM */
             CRTMQMQ    QNAME(INT.AU.SYSTEM.QL.SMQ01.SYSTEM) +
                          QTYPE(*LCL) MQMNAME(&QMNAME) +
                          REPLACE(*YES) TEXT('SMQ01') +
                          PUTENBL(*YES) MAXDEPTH(5000) +
                          MAXMSGLEN(4194304) USAGE(*NORMAL)
             CRTMQMQ    ... etc

/*  Grant MQ Object Authority for SYSTEM  */
             GRTMQMAUT  OBJ(&QMNAME) OBJTYPE(*MQM) USER(*PUBLIC) +
                          AUT(*CONNECT) MQMNAME(&QMNAME)
             GRTMQMAUT  OBJ(INT.AU.SYSTEM.QL.DEAD.LETTER) OBJTYPE(*Q) +
                          USER(*PUBLIC) AUT(*ALLMQI) MQMNAME(&QMNAME)
             GRTMQMAUT  OBJ(INT.AU.SYSTEM.QL.SYSTEM.SMQ01) OBJTYPE(*Q) +
                          USER(*PUBLIC) AUT(*ALLMQI) MQMNAME(&QMNAME)
             GRTMQMAUT  ... etc

/*  Restart the MQ Subsystem   */
             ENDSBS     SBS(QMQM) OPTION(*IMMED)
             DLYJOB     DLY(30)
             STRSBS     SBSD(QMQM/QMQM) 

The QMQM subsystem has an autostart job also created which submits jobs to start receiving against each queue when the subsystem is started.
The above is only for local queues, we have slightly different handling for remote. Hopefully it might give you an idea of what you might be missing? I've depersonalised some of the code so if any of it doesn't make sense let me know, could be I'm missing something.

[gcraill]

Re: MQ Issue, no jobs in QMQM sub-system

Thanks chris, but we're falling over on step 1.
The CRTMQM command is failing to complete.

[chrisr]

Re: MQ Issue, no jobs in QMQM sub-system

I've just reviewed the jobs around this and notice we are starting QMQM sbs first then running these steps. Is yours started before you do the create?
here

Because the MQ jobs run in the QMQM subsystem, start the subsystem before doing any configuration.

[chrisr]

Re: MQ Issue, no jobs in QMQM sub-system

also note this snippet "Jobs don't actually appear in the subsystem until you start a queue manager" so you won't see anything till you've solved the create/start queue manager issue

[gcraill]

Re: MQ Issue, no jobs in QMQM sub-system

@Chris - thanks for the follow up.

Yeah SBS was started, stopped/restarted etc. Same process is working fine on other systems.

Will remove and re-install MQ after vacation methinks ...