| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ details |
« View previous topic :: View next topic » |
| Author |
Message
|
| kevinf2349 |
 Posted: Tue Mar 03, 2009 5:54 am Post subject: |
 |
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
fyi....even if you find out what the CPF is that is no guarantee that the subsystem is actually startable. You would need to check that the JCL procedure exists and that the boot strap and page datasets are there too.
As a rule the MQ subsystems on z/OS are usually controlled via an automation product and so I echo the recommendation that you talk to the site system programmer. |
|
| Back to top |
|
 |
| ctefehinoz |
| Posted: Tue Mar 03, 2009 10:30 pm Post subject: |
|
|
Apprentice
Joined: 27 Oct 2003
Posts: 29
Location: Australia
|
You can always ring up your Z/OS operations people and get them to issue a D O,PREFIX and get them to read out what command response has been if your sysprog is absent. I would suspect you have a lack of RACF authority to do this all yourself. Armed with the CPF, the sysprog should be able to find the MSTR and CHIN started task procedures for you (if indeed they're running as STC's.). Ditto how they are automated.
HTH
Ctefehinoz |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Mar 04, 2009 7:03 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
/d o,prefix is very helpful.
As mentioned before, you need to make sure you still have all pagesets, active log files and/or archive log files. check MQS1MSTR & MQS1CHIN.
You also need to find out the PARM that your QMGR is using. Check the AUTHLIB in MQS1MSTR, hopefully you have only 2 loadS there in AUTHLIB, which hopefully are the PARMs for your MQS1MSTR & MQS1CHIN respectively.
just to add, to display IPL info, /d iplinfo . |
|
| Back to top |
|
|
| syed_zarina |
| Posted: Wed Mar 04, 2009 10:49 pm Post subject: |
|
|
Newbie
Joined: 01 Mar 2009
Posts: 6
|
My Queue Manager is up. How about the channel ?. Can you please guide.
Thanks |
|
| Back to top |
|
|
| syed_zarina |
| Posted: Wed Mar 04, 2009 11:42 pm Post subject: |
|
|
Newbie
Joined: 01 Mar 2009
Posts: 6
|
| I tried /start xxxxCHIN where xxxx is my queuename . But it fails with S5C6. Can you please guide. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 05, 2009 12:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| syed_zarina wrote: |
| I tried /start xxxxCHIN where xxxx is my queuename . But it fails with S5C6. Can you please guide. |
Try using something other than a queue name with a start command!!! 
Assuming you actually meant queue manager name, take the associated diagnostic data (there should be several pages of dump) to whoever told you the queue manager was up and running & ask if they'd like to revise their opinion. Also ask if they're absolutely certain of the CPF.
If they don't, and the queue manager is indeed running, use the diagnostic information to correct the queue manager configuration, the WMQ installation or both.
You would be well advised to also review what level of WMQ you're using (remembering that z/OS happily supported multiple levels so I do mean the one you're using) and see if you could benefit from a bit of maintenance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Mar 05, 2009 5:58 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
You don't start the CHIN like that....try issuing the START CHINIT command to the qmgr master address space.
/cpf START CHINIT
....and then to answer your next question.....you also may need to start the listener service too....depending on how it has been set up.
This is why it is usually left to an automation product to bring these things up on z/OS  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 05, 2009 7:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
As you've discovered from this post, the mainframe is different. At the system level, experience with Windows or UNIX isn't much help. You need mainframe skills or someone with those skills to help you.
The purpose of the CPF is to direct the command string that follows it to the subsystem interface routine(s) that the cpf represents. For WMQ, its CSQYASCP or something like that (this from memory).
If +MQ01 is the cpf for qmgr MQ01, then the command issued from the real operators console (or equivalent) would be +MQ01 START QMGR PARM(MQ01ZPRM) or something like that. WMQ for z/OS requires that a JCL proc named MQ01MSTR be present in a PROCLIB for this to work.
So, technically, JCL is used to run everything in z/OS. WMQ implementation precludes submitting the JCL directly. It is the WMQ subsystem interface that invokes the MQ01MSTR and MQ01CHIN JCL procs.
If you use SDSF as the operator console, SDSF requires that you enter a slash character before the MVS console command you intend to enter; thus: /+MQ01 START QMGR PARM(MQ01ZPRM).
To start the CHIN, you would issue the op cmmand +MQ01 START CHINIT. To start a listener: +MQ01 START LISTENER PORT(xxxx). To issue an MQSC command: +MQ01 DISPLAY CHS(*) or +MQ01 DEFINE QL(MYQUEUE).
IBM offers 4-day training class for WMQ System Admin for z/OS - WM300 is the course code. For information: http://www-304.ibm.com/jct03001c/services/learning/ites.wss/us/en?pageType=course_search&sortBy=5&searchType=1&sortDirection=9&includeNotScheduled=15&rowStart=0&rowsToReturn=20&maxSearchResults=200&language=en&country=us&searchString=wm300
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zhanghz |
| Posted: Thu Mar 05, 2009 4:39 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
I think you mentioned your MQ is version 5.3. Then when you start your channel initiator, you need to add a PARM module "qmgrXPRM". So the command to start the channel initiator is "+qmgr START CHINIT PARM(qmgrXPRM)".
for WMQ for z/OS V5.3, you can issue "+qmgr DIS DQM" (DIS CHINIT equivalent before V6) to see a general status of your qmgr. The result shows you whether your channel initiator is running, whether your listener is running, how many channels are active, starting, stopped and retrying, etc. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
