| Author |
Message
|
| RatherBeGolfing |
 Posted: Mon Mar 06, 2006 10:28 am Post subject: |
 |
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
Thanks, that certainly makes sense. Wayne, do you personally recommend the "update in place" method or the "delete & reinstall" method?
_________________
Cheers,
Larry
MQ Certifiable |
|
| Back to top |
|
 |
| PieterV |
| Posted: Mon Apr 24, 2006 12:43 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
System: Solaris 8
MQ 5.3 CSD 12
listener on port 1415 and port 1416
Additional question:
when upgrading to V6, do the listeners that have been created in /etc/services and /etc/inetd.conf be removed before upgrading?
Cause the way listeners work have been changed. Now you can add them using a command in runmqsc.
Or can i just keep the existing listeners (in etc/services and inetd.conf)?
Pieter |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Apr 24, 2006 3:20 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You have a choice of keeping things the way they are (runmqlsr) or using the new LISTENER object.
I thought I heard something that they way inetd works in Solaris 9 ( or maybe 10?) has changed, but I might be wrong about that, check with your SA anyways,
_________________
-wayne |
|
| Back to top |
|
|
| PieterV |
| Posted: Mon Apr 24, 2006 3:51 am Post subject: |
|
|
Disciple
Joined: 04 Jan 2006
Posts: 164
Location: Belgium
|
we are still working with Solaris 8,
so it's not necessary to remove the existing listener configuration.
in other words:
i stop MQ
install v6 (i keep /var/mqm)
start MQ v6
and it should work with the existing listeners from v5.3? |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Apr 24, 2006 3:58 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Yes it should.
Even using the runmqlsr listener, you get the advantage of being able to issue DISAPLY LSSTATUS from runmqsc/explorer
_________________
-wayne |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Apr 24, 2006 7:02 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
inetd has changed in Solaris 10. Here is a little write-up on how it now works:
inetd in Solaris 10 has changed, with all inetd services now controlled
under the SMF (Service Management Facility). General service management
is controlled via the svcadm command, but a special command called
inetadm is provided to manage network services, together with inetconv
to assist in adding further inetd-style services.
.
Here is an example of adding an inetd-style service:-
.
First, add an entry in /etc/services for MQSeries:-
.
MQSeries 1414/tcp
.
The /etc/services entry has not changed at Solaris 10.
Next, create a temporary file containing a valid inetd.conf-style entry
for MQSeries, for example /tmp/inet.MQSeries:
.
MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m QMGR
.
Now run inetconv as follows:-
.
# inetconv -i /tmp/inet.MQSeries
.
This produces the following output:
.
MQSeries-> /var/svc/manifest/network/MQSeries-tcp.xml
Importing MQSeries-tcp.xml ...Done
.
Now MQSeries can be enabled (Note the service name):-
.
# inetadm -e svc:/network/MQSeries/tcp:default
.
Finally, refresh the service using this command:
.
# svcadm refresh inetd
.
You can check the service by using inetadm:
.
# inetadm -l /network/MQSeries/tcp
SCOPE NAME=VALUE
name="MQSeries"
endpoint_type="stream"
proto="tcp"
isrpc=FALSE
wait=FALSE
exec="/opt/mqm/bin/amqcrsta -m QMGR"
user="mqm"
default bind_addr=""
default bind_fail_max=-1
default bind_fail_interval=-1
default max_con_rate=-1
default max_copies=-1
default con_rate_offline=-1
default failrate_cnt=40
default failrate_interval=60
default inherit_env=TRUE
default tcp_trace=FALSE
default tcp_wrappers=FALSE
.
The login directory for the mqm user, i.e. the directory specified in
/etc/passwd, must exist.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| dutilleul |
| Posted: Mon Apr 24, 2006 11:59 pm Post subject: Connectivity compatibility between different mq versions |
|
|
Newbie
Joined: 23 Feb 2006
Posts: 7
Location: Bruxelles
|
Hi,
We have plan to migrate to v6 this year.
I would like to plan the migration and I'm looking for a diagram showing the compatibiliy connexion between qmgr and client of differents versions.
We have following configuration :
Qmgr in v5.3.1 on Z/oS (within the same QSG)
Qmgr in v5.3 on Aix and Windows 2000.
Client in v5.3 on AIX and Windows 2000 connecting to upper qmgr.
Is there any particular order to respect for plan migration ?
Can we connect V5.3 Client to a v6 Qmgr on Z/os ?
Can we connect V5.3 Qmgr on Aix/Windows to a v6 Qmgr on Aix/Windows/ZoS ?
Can we connect a V6 Client to a V5.3.1 Qmgr on Z/os ? or to a V5.3 Qmgr on Aix/Windows ?
And the big one : Can we connect a v5.3 client to a QSG having mixed qmgr on V6 and v5.3.1 ?
I supposed that it's true, but I would like to be sure.
Thanks a lot for helping.
Denis |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Apr 25, 2006 5:49 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Backlevel clients work with forward level qmgrs (ie v5.3 client with a v6 qmgr), and the other way too (v6 client with V5.3 qmgr). Of course, if you do use a v6 client with a v5.3 qmgr, you can't use any new API features that the v5.3 client doesn't know about (but there aren't too many anyways).
As always, make sure your service (csd, fp) level is reasonibly up to date.
_________________
-wayne |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Apr 25, 2006 7:03 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| Nigelg wrote: |
| inetd has changed in Solaris 10... |
But does it depend on the MQ version? On Solaris 10 also the /etc/system disappears, to configure the IPC resources, but this is an issue for MQ v5.3 too.
In addition since version 5.3 it is recommended, too use the listener instead of the inetd (due to performance issues, I think). Up to version 5.2 the inetd was recommended.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| csaunders |
| Posted: Thu Apr 27, 2006 10:43 am Post subject: |
|
|
Acolyte
Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va
|
can I connect a 6.0 sender channel to a receiver channel running on 5.3?
and vice versa? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 27, 2006 10:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 27, 2006 8:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And if you have compression enabled on the channel make sure one of the options is 'NONE'. 5.3 will not support the compression. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Thu Jun 08, 2006 2:54 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| Nigelg wrote: |
| inetd has changed in Solaris 10. Here is a little write-up on how it now works:i |
I know this is a little late in the thread life for this comment but... THANK YOU for that post Nigelg! It was VERY helpful. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Thu Jun 08, 2006 5:54 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
Anthony,
I am missing your write-up ...
_________________
Regards
Hubert |
|
| Back to top |
|
|
|
|
