| Author |
Message
|
| mqonnet |
 Posted: Thu Jan 16, 2003 7:52 am Post subject: |
 |
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
While you were installing the PTF you might have installed it on the wrong vol and sub vol. Meaning you supplied wrong details because of whcih the installation passed fine and copied to other volumes that expected. You could verify this by checking the spooler jobs that the insallation program creates.
If the installation succeeds and you specified the appropriate vols and sub vols then there is no way that the vproc would be different. The other possibility could be that your params are set wrong and you are using different exes than you think you are using.
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 |
|
 |
| LuisFer |
| Posted: Fri Jan 17, 2003 6:21 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
In my instalalation always have problems with the install of a PTF, EFIX, etc. Why? In the 99% by the security. We've secure (SAFEGUARD) the restore tandem utility, & only the SUPER group have acces to this one (the UNPAK utility calls RESTORE)
Solution: Install the PTF with a SUPER.user, FUP SECURE $vol.ZMQS*.*, mqm.manger & voila the VPROC is OK.
Don't forget PROGID ZMQSEXE.* |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri Jan 24, 2003 5:45 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
This param tells mq to keep the message catalog open at all times and dont close it. I guess till the QM ends.
Think this goes into performance enhancements as MQ wouldnt open/close this file each time MQ displays a message/error.
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 |
|
|
| rjl_state |
| Posted: Fri Jan 24, 2003 7:41 am Post subject: |
|
|
Apprentice
Joined: 04 Oct 2002
Posts: 48
Location: Des Moines, IA
|
I installed this on my development system last week without any problems, I will be installing in production next week.
We remove the PROGID from the executables and it works without any issues that I can see.
I was wondering if anyone else does this? Our security department  had a problem with anything having the PROGID bit set.
Thanks in advance. |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Jan 24, 2003 10:51 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
There is not any problems if you started the QMGR with the MQM.MANGER (or a user in this group). If you started the QMGR with other user (not MQM group) the MQS-REPSVRxx & othe servers (don't remember all) don't started good (the QMGR). The qmgr works but not all functions work fine.(CLUSTER's, Remote admin, & others).
I recommend to you install the CSD 1 EFIX 3 from IBM. It resolves a problem with TMF. (The MQMCACAL program generates a lot of TX TMF with No Persistence Messages).
If you want the readme file for this EFIX send me a mail.
I have this efix working fine in Production from a week. (70 msg/second NPersistence 2k size x MSG) |
|
| Back to top |
|
|
| rjl_state |
| Posted: Tue Jan 28, 2003 8:55 am Post subject: |
|
|
Apprentice
Joined: 04 Oct 2002
Posts: 48
Location: Des Moines, IA
|
I installed CSD01 & EFIX2 today without any problems.  I didn't find out about EFIX3 until it was too late to test. I should be installing it in the next few months.
Please post if anyone has problems with EFIX3 for NSK.
Thanks! |
|
| Back to top |
|
|
|
|
