| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 2C1 abend during starting WMB on z/OS |
« View previous topic :: View next topic » |
| Author |
Message
|
| hooman24 |
 Posted: Sat Aug 09, 2014 9:38 pm Post subject: 2C1 abend during starting WMB on z/OS |
 |
|
Apprentice
Joined: 09 Aug 2014
Posts: 25
|
Hi,
We had WMB on System z running without any problem, until recently that we have changed our Coupling Facility Processor. After IPLing the system, broker address space was started but when we had defined execution group and recycled it, broker abended with 2C1.
We had delete/defined WMB, but same problem occured. Verification step passed successfully.
Here is the error in the STDERR:
CEE3250C The system or user abend S2C1 R=000000C4 was issued.
From entry point ImbDumpAndTerminate(int,const void*) at compile unit offset +000000001AB943E4 at entry offset -0000000000847BB4 at address 000000001AB943E4.
Here is sysdump title:
TITLE
LIST 00. LITERAL LENGTH(X'2B') CHARACTER
00000000 | WMQBRK ,ABN=S2C1-000000C4,C=M7500.700.BRKR |
Broker address space and OMVS are the only Address spaces included in the dump. Dump is taken from /usr/lpp/mqsi/v7r0m0/bin/bipbroker.
Our system specifications:
z/OS 1.11
WMQ V7.0.1
WMB V7.0.0
DB2 v9.1
I will be pleased if anyone can help us solving this problem, or have any idea.
Thanks in advance
Hooman |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Mon Aug 11, 2014 6:20 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Well, first z/OS 1.11 hit EOS two years ago...
When you look in SDFS at the output of the broker job, what fix pack do you see?
I would open a PMR if I were you... Note they will want you to apply maintenance and the fact you are on a unsupported level of the OS means they want you to upgrade. |
|
| Back to top |
|
|
| hooman24 |
| Posted: Tue Aug 12, 2014 5:07 am Post subject: Solution! |
|
|
Apprentice
Joined: 09 Aug 2014
Posts: 25
|
Surprisingly, the problem has solved by adding TSO segment to BROKER user with zero REGION SIZE.
We didn't have TSO segment for this user before and everything was fine. I don't understand what should have been changed and considerring no OutOfMemoryError in dumps, what are the main factors for memory allocation in Websphere Message Broker on z/OS?! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
