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 » General Discussion » Tandem WMQ V53 Issues??

Post new topic  Reply to topic
 Tandem WMQ V53 Issues?? « View previous topic :: View next topic » 
Author Message
LuisFer
PostPosted: Wed Jun 21, 2006 10:47 am    Post subject: Tandem WMQ V53 Issues?? Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

Hi all:
There is anything working with the new version.??

Regards

PD: I'm changing from journeyman to Master
Back to top
View user's profile Send private message
LuisFer
PostPosted: Wed Jun 21, 2006 11:17 am    Post subject: Re: Tandem WMQ V53 Issues?? Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

When i'm writting this post , i received an email with the EFIX4 for V53 with this one:
Websphere MQ V5.3 for HP NonStop Server
=======================================

eFix4 for WMQ 5.3 Gold Release (Version 5.3.0.0)
================================================

This README file contains program fix information
and installation instructions for this eFix.

This eFix is a cumulative service package that contains the
eFix1, eFix2 and eFix3 packages plus new service as described below:

contained in V5.3.0.0 eFix1:
Beta PMR 18886 - Command Server abend
Beta PMR 18890 - RC2072 on MQPUT/MQGET

contained in V5.3.0.0 eFix2:
Beta PMR 19284 - Message Grouping failure
Beta PMR 19292 - Error 2009 after large number of MQPuts

contained in V5.3.0.0 eFix3:
Beta PMR 19085 - Queue Server checkpointing problem with messages on
queue and MQPUT/ MQGET returns MQRC_HOBJ_ERROR after
takeover
Beta PMR 19286 - Channel status shows BINDING
APAR IC49232 - instmqm fails trying to check OSS socket availability
APAR IC49229 - Queue server repeatedly abends when stopping primary
Queue Server process while processing messages
APAR IC49243 - Channel status item LSTSEQNUM takes too long to
refresh and wrong LSTSEQNO and CURSEQNO after
restarting channel
APAR IC49233 - Repository Manager process on the same CPU as Execution
Controller is named by system when it is restarted
APAR IC49327 - Repository manager process on cpu 0 is never restarted
after abending repository manager on cpu 1 and 0.
APAR IC49255 - Execution Controller repeatedly restarts MCA and then
abends if using ChannelNameMatch in qmproc.ini after
restarting a channel
APAR IC49269 - Execution Controller, Channel Server and Queue Server
abend when cpu down occurs
APAR IC49269 - Queue Server abends after takeover caused by CPU Down
- Channel Status problem with Local Repository Manager
Cluster Channel end abnormally
- An FDC file is created by the repository manager
- Queue Server fix MQGET for large messages
- runmqlsr using same port number on different TCP/IP
processes fails
- 6 character TCP/IP process name for runmqslr fails
- Start of a second and subsequent SVRCONN channel
stays in BINDING state
- Execution Controller backup has a memory leak
- Channel Server generating FDC on Channel Server
takeover
- nspExport failures in rrxWriteSync are not correctly
being passed back to the client
- Execution Controller log entry for MCA process restart
after CPU down event shows "LQMA" instead of "MCA"

contained in V5.3.0.0 eFix4:
Beta PMR 19253 - FFST from backup Channel Server
Beta PMR 19266 - 8 character passphrase restriction for SSL
Beta PMR 19283 - Long running TMF transaction for idle NPMSPEED(FAST)
sender channels
APAR IC49306 - Sender channel recovery problem after CPU Down
APAR IC49425 - EC Abend after CPU Down
APAR IC49512 - Channel recovery and MCA process management rules
problems after CPU Down
APAR IC49570 - Channel recovery problems after two CPU Down
events
APAR IC49567 - FDC from Channel Server with PCF message
APAR IC49566 - Pathway OWNER attribute not node independent
APAR IC49653 - Backup Queue Server out of sync with Primary and Queue
Server abend on 2nd CPU down
APAR IC49694 - Message stuck in transmission queue when I/O error occurs
while getting a persistent message (CPU Down causes
primary disk process failure)
APAR IC49454 - TNS library unresolved references in certain
methods of binding
APAR IC49492 - TNS library reduce data size to closer to V5.1 level
- serviceability improvements
- add DSPMQFLS Guardian TACL macro
- EC process management rule fixes
- Queue Server support for more than 1000 objects each
process pair - change ported from V5.1 service stream
- handling of TMF error 76
- fix regression in dynamic queues for threaded agents

Regards
Back to top
View user's profile Send private message
hankknowles
PostPosted: Mon Aug 21, 2006 9:03 am    Post subject: Re: Tandem WMQ V53 Issues?? Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

Hi Luisfer:

You don't still have the URL where this fix is hidden @ do you. I just got the 5.3 code and will be installing soon!

Do you have any hints or gotcha's when you installed?

Regards,

Hank Knowles



LuisFer wrote:
When i'm writting this post , i received an email with the EFIX4 for V53 with this one:
Websphere MQ V5.3 for HP NonStop Server
=======================================

eFix4 for WMQ 5.3 Gold Release (Version 5.3.0.0)
================================================

This README file contains program fix information
and installation instructions for this eFix.

This eFix is a cumulative service package that contains the
eFix1, eFix2 and eFix3 packages plus new service as described below:

contained in V5.3.0.0 eFix1:
Beta PMR 18886 - Command Server abend
Beta PMR 18890 - RC2072 on MQPUT/MQGET

contained in V5.3.0.0 eFix2:
Beta PMR 19284 - Message Grouping failure
Beta PMR 19292 - Error 2009 after large number of MQPuts

contained in V5.3.0.0 eFix3:
Beta PMR 19085 - Queue Server checkpointing problem with messages on
queue and MQPUT/ MQGET returns MQRC_HOBJ_ERROR after
takeover
Beta PMR 19286 - Channel status shows BINDING
APAR IC49232 - instmqm fails trying to check OSS socket availability
APAR IC49229 - Queue server repeatedly abends when stopping primary
Queue Server process while processing messages
APAR IC49243 - Channel status item LSTSEQNUM takes too long to
refresh and wrong LSTSEQNO and CURSEQNO after
restarting channel
APAR IC49233 - Repository Manager process on the same CPU as Execution
Controller is named by system when it is restarted
APAR IC49327 - Repository manager process on cpu 0 is never restarted
after abending repository manager on cpu 1 and 0.
APAR IC49255 - Execution Controller repeatedly restarts MCA and then
abends if using ChannelNameMatch in qmproc.ini after
restarting a channel
APAR IC49269 - Execution Controller, Channel Server and Queue Server
abend when cpu down occurs
APAR IC49269 - Queue Server abends after takeover caused by CPU Down
- Channel Status problem with Local Repository Manager
Cluster Channel end abnormally
- An FDC file is created by the repository manager
- Queue Server fix MQGET for large messages
- runmqlsr using same port number on different TCP/IP
processes fails
- 6 character TCP/IP process name for runmqslr fails
- Start of a second and subsequent SVRCONN channel
stays in BINDING state
- Execution Controller backup has a memory leak
- Channel Server generating FDC on Channel Server
takeover
- nspExport failures in rrxWriteSync are not correctly
being passed back to the client
- Execution Controller log entry for MCA process restart
after CPU down event shows "LQMA" instead of "MCA"

contained in V5.3.0.0 eFix4:
Beta PMR 19253 - FFST from backup Channel Server
Beta PMR 19266 - 8 character passphrase restriction for SSL
Beta PMR 19283 - Long running TMF transaction for idle NPMSPEED(FAST)
sender channels
APAR IC49306 - Sender channel recovery problem after CPU Down
APAR IC49425 - EC Abend after CPU Down
APAR IC49512 - Channel recovery and MCA process management rules
problems after CPU Down
APAR IC49570 - Channel recovery problems after two CPU Down
events
APAR IC49567 - FDC from Channel Server with PCF message
APAR IC49566 - Pathway OWNER attribute not node independent
APAR IC49653 - Backup Queue Server out of sync with Primary and Queue
Server abend on 2nd CPU down
APAR IC49694 - Message stuck in transmission queue when I/O error occurs
while getting a persistent message (CPU Down causes
primary disk process failure)
APAR IC49454 - TNS library unresolved references in certain
methods of binding
APAR IC49492 - TNS library reduce data size to closer to V5.1 level
- serviceability improvements
- add DSPMQFLS Guardian TACL macro
- EC process management rule fixes
- Queue Server support for more than 1000 objects each
process pair - change ported from V5.1 service stream
- handling of TMF error 76
- fix regression in dynamic queues for threaded agents

Regards
Back to top
View user's profile Send private message
hankknowles
PostPosted: Fri Aug 25, 2006 6:26 am    Post subject: Re: Tandem WMQ V53 Issues?? Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

Gonna answer my own question........ The NSK efix4 can be found @

ftp.emea.ibm.com
logon as anonymous and enter your email id as password
cd fromibm
cd other
cd HPNSS
bin
prompt
mget *
(after completion)
bye
There will 4 files downloaded!

10,044,954 efix4_update_mqmtns
4,353 readme_wmq53.0.0_efix4_mqmtns_update

66,026,542 wmq53.0.0_efix4_HPNSS.zip
30,882 readme_wmq53.0.0_efix4

The mqmtns is NOT included on efix4 cumm.

Also not that there is a CSD coming in October that is supposed to fix the upgmqm so you can move from V5.1 to V5.3 somewhat painlessly!

Cheers

hankknowles wrote:
Hi Luisfer:

You don't still have the URL where this fix is hidden @ do you. I just got the 5.3 code and will be installing soon!

Do you have any hints or gotcha's when you installed?

Regards,

Hank Knowles



LuisFer wrote:
When i'm writting this post , i received an email with the EFIX4 for V53 with this one:
Websphere MQ V5.3 for HP NonStop Server
=======================================

eFix4 for WMQ 5.3 Gold Release (Version 5.3.0.0)
================================================

This README file contains program fix information
and installation instructions for this eFix.

This eFix is a cumulative service package that contains the
eFix1, eFix2 and eFix3 packages plus new service as described below:

contained in V5.3.0.0 eFix1:
Beta PMR 18886 - Command Server abend
Beta PMR 18890 - RC2072 on MQPUT/MQGET

contained in V5.3.0.0 eFix2:
Beta PMR 19284 - Message Grouping failure
Beta PMR 19292 - Error 2009 after large number of MQPuts

contained in V5.3.0.0 eFix3:
Beta PMR 19085 - Queue Server checkpointing problem with messages on
queue and MQPUT/ MQGET returns MQRC_HOBJ_ERROR after
takeover
Beta PMR 19286 - Channel status shows BINDING
APAR IC49232 - instmqm fails trying to check OSS socket availability
APAR IC49229 - Queue server repeatedly abends when stopping primary
Queue Server process while processing messages
APAR IC49243 - Channel status item LSTSEQNUM takes too long to
refresh and wrong LSTSEQNO and CURSEQNO after
restarting channel
APAR IC49233 - Repository Manager process on the same CPU as Execution
Controller is named by system when it is restarted
APAR IC49327 - Repository manager process on cpu 0 is never restarted
after abending repository manager on cpu 1 and 0.
APAR IC49255 - Execution Controller repeatedly restarts MCA and then
abends if using ChannelNameMatch in qmproc.ini after
restarting a channel
APAR IC49269 - Execution Controller, Channel Server and Queue Server
abend when cpu down occurs
APAR IC49269 - Queue Server abends after takeover caused by CPU Down
- Channel Status problem with Local Repository Manager
Cluster Channel end abnormally
- An FDC file is created by the repository manager
- Queue Server fix MQGET for large messages
- runmqlsr using same port number on different TCP/IP
processes fails
- 6 character TCP/IP process name for runmqslr fails
- Start of a second and subsequent SVRCONN channel
stays in BINDING state
- Execution Controller backup has a memory leak
- Channel Server generating FDC on Channel Server
takeover
- nspExport failures in rrxWriteSync are not correctly
being passed back to the client
- Execution Controller log entry for MCA process restart
after CPU down event shows "LQMA" instead of "MCA"

contained in V5.3.0.0 eFix4:
Beta PMR 19253 - FFST from backup Channel Server
Beta PMR 19266 - 8 character passphrase restriction for SSL
Beta PMR 19283 - Long running TMF transaction for idle NPMSPEED(FAST)
sender channels
APAR IC49306 - Sender channel recovery problem after CPU Down
APAR IC49425 - EC Abend after CPU Down
APAR IC49512 - Channel recovery and MCA process management rules
problems after CPU Down
APAR IC49570 - Channel recovery problems after two CPU Down
events
APAR IC49567 - FDC from Channel Server with PCF message
APAR IC49566 - Pathway OWNER attribute not node independent
APAR IC49653 - Backup Queue Server out of sync with Primary and Queue
Server abend on 2nd CPU down
APAR IC49694 - Message stuck in transmission queue when I/O error occurs
while getting a persistent message (CPU Down causes
primary disk process failure)
APAR IC49454 - TNS library unresolved references in certain
methods of binding
APAR IC49492 - TNS library reduce data size to closer to V5.1 level
- serviceability improvements
- add DSPMQFLS Guardian TACL macro
- EC process management rule fixes
- Queue Server support for more than 1000 objects each
process pair - change ported from V5.1 service stream
- handling of TMF error 76
- fix regression in dynamic queues for threaded agents

Regards
Back to top
View user's profile Send private message
LuisFer
PostPosted: Tue Sep 05, 2006 11:41 am    Post subject: Re: Tandem WMQ V53 Issues?? Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

No errors, only customization of mqm.manager for the OSS subsys. No problem, the performance is in the practice equal to V5.1.
Follow...
Back to top
View user's profile Send private message
hankknowles
PostPosted: Wed Sep 06, 2006 7:45 am    Post subject: MQ 5.3 Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

Hi Luisfer:

Do you have the tcplis00 running, I can do runmqlsr from oss but itwill not gointo background and release my oss command line!

I tried changing the mqs-tcplis00 arglist as shown in the sag but it doesn't work for me! (
Back to top
View user's profile Send private message
LuisFer
PostPosted: Tue Sep 12, 2006 10:17 pm    Post subject: Re: MQ 5.3 Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

I'm starting the Listener as Unix by runmqsc sta lstr.
Other: Efix 4 Patch 2 is available.
Quote:

Note the file will be automatically removed from the IBM server after 2 weeks.

ftp ftp.emea.ibm.com user:anonymous
cd /fromibm/other/HPNSS
binary
get wmq53.0.0_efix4_patch2

APAR IC50459 - MCA and Channel Server memory leak and incorrect handling
of "out-of-memory" situation
APAR IC50072 - MCA reuse not working correctly, leading to an accumulation
of MCA processes and eventually failure to start channels

Back to top
View user's profile Send private message
hankknowles
PostPosted: Wed Sep 13, 2006 3:28 am    Post subject: Re: MQ 5.3 Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

Thanks LuisFer

Yeah I was able to do it that way. But I wanted to idot proof the lsr so I found out the SAG was not entirely correct! in the pathway tcplis00 server in the agrlist commande line you need to have the port -p and -g TCPIP process ( otherwise it defaults to $ZTCP0 ) you'd think IBM would realize that that port is used by the osm consoles! DUH!

Anywho thanks for the heads up on the fix I just pulled it down!


LuisFer wrote:
I'm starting the Listener as Unix by runmqsc sta lstr.
Other: Efix 4 Patch 2 is available.
Quote:

Note the file will be automatically removed from the IBM server after 2 weeks.

ftp ftp.emea.ibm.com user:anonymous
cd /fromibm/other/HPNSS
binary
get wmq53.0.0_efix4_patch2

APAR IC50459 - MCA and Channel Server memory leak and incorrect handling
of "out-of-memory" situation
APAR IC50072 - MCA reuse not working correctly, leading to an accumulation
of MCA processes and eventually failure to start channels

Back to top
View user's profile Send private message
LuisFer
PostPosted: Thu Oct 19, 2006 12:34 am    Post subject: Re: MQ 5.3 Reply with quote

Partisan

Joined: 17 Aug 2002
Posts: 302

New patch eFix4 Patch3
APAR IC50790 - memory leak in MQCLOSE and memory corruption problem
APAR IC50787 - memory leak in MQDISC for FASTPATH applications, affecting channel restart operation

ftp ftp.emea.ibm.com user:anonymous
cd /fromibm/other/HPNSS
binary
get wmq53.0.0_efix4_patch3

Regards
Back to top
View user's profile Send private message
hankknowles
PostPosted: Thu Oct 19, 2006 3:37 am    Post subject: New Patch Reply with quote

Centurion

Joined: 18 Aug 2003
Posts: 114

Thanks Luisfer:

IBM must have pulled it back or hidden it as it's not in the dir.

Just about have the certs creation confusion resolved. Leave it to IBM to take simple process and trun it into a 'never ending story'! HA HA

Thanks again...
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 » General Discussion » Tandem WMQ V53 Issues??
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.