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 » IBM MQ Installation/Configuration Support » How to handle 2017 problem on Tandem machine?

Post new topic  Reply to topic
 How to handle 2017 problem on Tandem machine? « View previous topic :: View next topic » 
Author Message
RAHULTHOTA
PostPosted: Mon Jan 06, 2003 10:00 pm    Post subject: How to handle 2017 problem on Tandem machine? Reply with quote

Novice

Joined: 13 Dec 2002
Posts: 13

I am working on Tandem MQ-Series.Suddenly I faced a problem with reason code 2017.According to it i have to increase the parameter
MaxHandles but i am not able to find this parameter in QMANAGER configuration File of MQ on Tandem.Can anyone suggest me how to change this and what is the default parameter set.
Back to top
View user's profile Send private message
bower5932
PostPosted: Tue Jan 07, 2003 11:20 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I've never used Tandem. On the other platforms, I would use the runmqsc utility to change this:

runmqsc my.qmgr
dis qmgr all
alter qmgr maxhands(new value)

Does Tandem have the runmqsc utility?
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
mqonnet
PostPosted: Tue Jan 07, 2003 11:56 am    Post subject: Reply with quote

Grand Master

Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.

This ones really new. I have never seen this.

How on earth could you get this return code. Unless you changed the defaults for the qm.

By default the MAXHANDS is set to (999999999) on Tandem.
The only way i think you could get this is if you are running an app for ages doing either lots of MQPUT1s or lots of MQOPENs and MQCLOSEs.

But i dont think either is the case here.

Is this a one time occurance, or could you reproduce this. If so, how can you do so. Let me know, i am curious.

Bower, Tandem does have runmqsc, as any other platform that has MQ Server on it. Which is what my assumption is. It is no different.

Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » How to handle 2017 problem on Tandem machine?
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.