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 » WebSphere Message Broker (ACE) Support » WMQI Broker on S/390 gives system dump on deployment

Post new topic  Reply to topic
 WMQI Broker on S/390 gives system dump on deployment « View previous topic :: View next topic » 
Author Message
muralihegde
PostPosted: Sun Aug 04, 2002 9:52 pm    Post subject: WMQI Broker on S/390 gives system dump on deployment Reply with quote

Centurion

Joined: 30 Apr 2002
Posts: 108

Hi,
We have WMQI broker created on OS/390. When no configuration is deployed yet, and the broker is started it starts without any problem. But when a initial deployment is done from the configuration manager (Only Topology no message flows yet), there seems to be a problem.
The broker recognizes the Broker UID passed to it from the config manager, and also a default execution group is deployed on it and it starts this execution group. But immediately it starts giving the message in the os/390 system logs that the broker has detected that execution group default has shut down, it tries to start again and the same cycle repeats.
It also gives a system dump at the home directory of the userid (started task of the broker). These dumps are around 60MB to 130MB. The JCL BIPJRSTC to format the dump fails bcz it can not open these dump files. Even copying these dump files from Unix file to a Data Set also fails.

Is this a known problem? Any fix pacs available for this?
Back to top
View user's profile Send private message Yahoo Messenger
bolek
PostPosted: Mon Aug 05, 2002 12:16 am    Post subject: Re: WMQI Broker on S/390 gives system dump on deployment Reply with quote

Apprentice

Joined: 25 Jul 2002
Posts: 35
Location: Germany

The most common problem which causes dumps is some missing prereq.
- Did you installed all necessary PTFs ( check part "5.2 Target System Requirements" of the "Program Directory for WebSphere MQ Integrator for z/OS" ?
- Do you use "New Era of Networking" nodes ? If not ( i.e. Neon part is not customized ), you have to remove /local/wmqi/lil/imbdfneo.lil ( if installed ) to avoid Neon initialization.

BTW: Check "Chapter 12. WebSphere MQ Integrator dumps" of the "WebSphere MQ Integrator Problem Determination Guide" for general information about WMQI dumps. You can format and read the dump using IPCS facility.
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Aug 06, 2002 2:09 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

Checkout the Red Book

Websphere MQ Integrator for z/OS 2.1 implementation guide

SG24-6528-0

www.redbooks.ibm.com
Back to top
View user's profile Send private message
muralihegde
PostPosted: Tue Aug 06, 2002 5:20 am    Post subject: Reply with quote

Centurion

Joined: 30 Apr 2002
Posts: 108

Hi,
Now the prblem is solved.
Actually after applying CSD2 the broker stopped giving dumps. But still the default execution group would keep failing, but this time the system log clearly mentioned "could not load /usr/lpp/wmqi/lil/imbdfneo.lil".. So as Bolek mentioned we renamed this imbdfneo.lil and re-started the broker. This solved the problem. Thanks Bolek.
But I wonder if this is the permanent solution, because even though we are not using any NEON related functionality at present within the broker what if we have to use it in future?
Back to top
View user's profile Send private message Yahoo Messenger
bolek
PostPosted: Wed Aug 07, 2002 1:44 am    Post subject: Reply with quote

Apprentice

Joined: 25 Jul 2002
Posts: 35
Location: Germany

muralihegde wrote:
Hi,
...
But I wonder if this is the permanent solution, because even though we are not using any NEON related functionality at present within the broker what if we have to use it in future?


If I'm not mistaken, WMQI 2.1 on z/OS includes 2 installation packages:
WMQI base and Neon nodes.

If you don't need New Era of Networking nodes, you don't need to install Neon package ( which includes imbdfneo.lil ). If you need Neon, you have to install Neon package AND perform Neon customization ( i.e. specify NNSY PATH/LIBPATH/Databases/etc ). Redbook specified in the Zpat's message describes Neon configuration.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMQI Broker on S/390 gives system dump on deployment
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.