| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries V5.2 upgrade on Solaris 7 w/SNA Support |
« View previous topic :: View next topic » |
| Author |
Message
|
| dhuddles |
 Posted: Sun Nov 04, 2001 9:37 am Post subject: |
 |
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
I have just upgraded MQ from V5.1 to V5.2 on a Sun Solaris 7 server. I have applied CSD #1 also. We have most channel connectivity via TCP/IP, but use SunLink SNA 9.1 software for a PU type connection to a mainframe.
The TCP/IP channels are working fine, but I cannot even "PING" the SNA channel. I get "kicked out" of the "runmqsc" utility when I do the "ping channel(xxx)" command. An FFST file is created in /var/mqm/errors, however I cannot completely understand the contents. Here is a fragment that might assist someone:
MQM Function Stack
mqscMAIN
uscRunScript
uscRunCommand
uscRunIT
pcmPingChannel
rrxPingChannel
rriInitSess
ccxNetWorkInit
cciLoadLibrary
xcsLoadFunction
xcsDisplayMessageForSubpool
xcsQueryValueForSubpool
xcsFFST
MQM Trace History
-----------{ xusGetLineType
-----------} xusGetLineType rc=Unknown(1)
-----------{ xusAddStanzaLineList
------------{ xcsGetMem
------------} xcsGetMem rc=OK
-----------} xusAddStanzaLineList rc=OK
-----------{ xusGetLineType
-----------} xusGetLineType rc=Unknown(1)
-----------{ xusAddStanzaLineList
------------{ xcsGetMem
------------} xcsGetMem rc=OK
-----------} xusAddStanzaLineList rc=OK
-----------{ xusGetLineType
-----------} xusGetLineType rc=Unknown(1)
-----------{ xusAddStanzaLineList
------------{ xcsGetMem
The other bit of info that may help is as follows:
Probe Id :- XC130003
Major Errorcode :- STOP
Minor Errorcode :- OK
Probe Type :- HALT6109
Probe Severity :- 1
Probe Description :- AMQ6109: An internal MQSeries error has occurred.
Arith1 :- 11 b
Looks to me like it (MQ) cannot get the proper line type (SNA)... but again, I am not the expert!
Anyone already encounter this? Any help appreciated.
David Huddleson
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada |
|
| Back to top |
|
 |
| isreal |
| Posted: Mon Nov 05, 2001 8:11 am Post subject: |
|
|
Novice
Joined: 18 Sep 2001
Posts: 22
|
Have you run TRUSS on this? That would be really helpful at this point. Do you have any exits in these channels? I had a problem like this, it was due to a misconfigured /etc/system. My problem was a resource one but I'm not sure what this one is.
[ This Message was edited by: isreal on 2001-11-05 08:13 ] |
|
| Back to top |
|
|
| dhuddles |
| Posted: Mon Nov 05, 2001 8:56 am Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
I have not run TRUSS against this. Actually, what would I be running truss against? The "runmqsc" command?
There are no EXITS running on the channels, plain old LU62 with no magic. We have been through MQ5.0 and 5.1 without any problems, although I distinctly remember having to create some soft-links back in V5.0 to make things work in SNA channels....
I have opened a PMR with IBM today, so maybe the answer will come from them sooner...
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada |
|
| Back to top |
|
|
| isreal |
| Posted: Mon Nov 05, 2001 12:43 pm Post subject: |
|
|
Novice
Joined: 18 Sep 2001
Posts: 22
|
| I would run Truss on the pid that belongs to runmqsc. Then once you have that running, try to ping the channel. when it dumps you'll see why. FYI, I use truss -f -l -a -vall -rall -wall -o -p as root. |
|
| Back to top |
|
|
| dhuddles |
| Posted: Tue Nov 06, 2001 5:24 am Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
As you suggested, I ran a TRUSS against the "runmqsc" and PING command. I have output, and I can see where the FFST gets generated, but I am trying to interpret what exactly is in error... here is a chunk where I think the important info is:
(WARNING! THIS MAY NOT "PASTE" NICELY...)
24322/1: llseek(4, 0, SEEK_CUR) = 1406
24322/1: llseek(4, 0, SEEK_CUR) = 1406
24322/1: read(4, 0x0003BD6C, 8192) = 0
24322/1: llseek(4, 0, SEEK_CUR) = 1406
24322/1: close(4) = 0
24322/1: open("/opt/mqm/lib/amqcc62a", O_RDONLY) = 4
24322/1: fstat(4, 0xFFBED31C) = 0
24322/1: d=0x00800078 i=255880 m=0106554 l=1 u=1008 g=1001 sz=7096
8
24322/1: at = Nov 6 07:50:09 EST 2001 [ 1005051009 ]
24322/1: mt = May 22 12:51:38 EDT 2001 [ 990550298 ]
24322/1: ct = Nov 4 10:34:57 EST 2001 [ 1004888097 ]
24322/1: bsz=8192 blks=140 fs=ufs
24322/1: mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 4, 0) =
0xFEC80000
24322/1: mmap(0x00000000, 114688, PROT_READ|PROT_EXEC, MAP_PRIVATE, 4, 0)
= 0xFEC60000
24322/1: mmap(0xFEC7A000, 5725, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVA
TE|MAP_FIXED, 4, 40960) = 0xFEC7A000
24322/1: munmap(0xFEC6C000, 57344) = 0
24322/1: memcntl(0xFEC60000, 7516, MC_ADVISE, 0x0003, 0, 0) = 0
24322/1: close(4) = 0
24322/1: open("/opt/mqm/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/usr/ccs/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/usr/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/opt/lotus/notes/latest/sunspa53/libcpic.so", O_RDONLY) Er
r#2 ENOENT
24322/1: open("/opt/sna/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/opt/SUNWappc/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/opt/cics/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/opt/encina/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: open("/usr/lib/libcpic.so", O_RDONLY) Err#2 ENOENT
24322/1: munmap(0xFEC7A000, 5725) = 0
24322/1: munmap(0xFEC60000, 42583) = 0
24322/1: munmap(0xFEC80000, 8192) = 0
24322/1: access("/opt/mqm/lib/amqcc62a", 0) = 0
24322/1: open("/usr/lib/locale/C/LC_MESSAGES/amq.cat", O_RDONLY) = 4
24322/1: fstat64(4, 0xFFBECF60) = 0
24322/1: d=0x00800078 i=6460 m=0100444 l=1 u=2 g=2 sz=32013
6
24322/1: at = Nov 6 07:51:01 EST 2001 [ 1005051061 ]
24322/1: mt = Nov 6 21:53:56 EST 2000 [ 973565636 ]
24322/1: ct = Nov 4 10:24:02 EST 2001 [ 1004887442 ]
24322/1: bsz=8192 blks=656 fs=ufs24322/1: mmap(0x00000000, 320136, PROT_READ, MAP_SHARED, 4, 0) = 0xFEC300
00
24322/1: close(4) = 0
24322/1: munmap(0xFEC30000, 320136) = 0
24322/1: time() = 1005051113
That section is followed by the generation of the FFST record and FDC file.
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada
[ This Message was edited by: dhuddles on 2001-11-06 05:26 ] |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Nov 06, 2001 6:18 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Hmmmm. That looks like it can't find the libcpic.so library.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| isreal |
| Posted: Tue Nov 06, 2001 7:56 am Post subject: |
|
|
Novice
Joined: 18 Sep 2001
Posts: 22
|
Did you leave the LU62 stanza entry in the qm.ini blank or spell it wrong? What is the error code from the QM log file?
|
|
| Back to top |
|
|
| dhuddles |
| Posted: Tue Nov 06, 2001 12:10 pm Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
Regarding the "libcpic.so" library, I have searched my whole server and that file does not exist! Another server currently runs MQ5.1 (the PROD server), and it does NOT have that file either, however MQ and SNA work fine. Does anyone know if this is a component of MQ, or SNA, or something else??
Regarding the QM.INI file, I do not have, and have not had, a stanza for LU62. What platform/OS are you on, and what purpose do you need LU62 stanza for? And, when performing a channel "ping", no entry is written in the QMGR errorlog file. However, if you "START" the channel, the following is written, and the channel enters "RETRYING" state...
11/05/01 13:40:37
AMQ9220: The APPC communications program could not be loaded.
EXPLANATION:
The attempt to load the APPC library or procedure 'amqcc62a' failed with
error
code 536895861.
ACTION:
Either the library must be installed on the system or the environment
changed
to allow the program to locate it.
And yes, the amqcc62a is there, and does have a link to /usr/lib/ so where do I go next?
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada
[ This Message was edited by: dhuddles on 2001-11-06 12:14 ] |
|
| Back to top |
|
|
| isreal |
| Posted: Tue Nov 06, 2001 12:29 pm Post subject: |
|
|
Novice
Joined: 18 Sep 2001
Posts: 22
|
I would suggest reading the following under the Chapter 3 heading: http://www-4.ibm.com/software/ts/mqseries/support/readme/sun520_read.html
I think it will help you out alot!
Also, I have encountered problems when installing MQSeries in single user mode. It didn't link some file properly, but when done in multiuser it installed fine. Did it install sucessfully or partially? Any work from IBM on this yet? Hope this helps! |
|
| Back to top |
|
|
| dhuddles |
| Posted: Tue Nov 06, 2001 12:34 pm Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
I think you might have hit it DEAD ON! I don't remember seeing that information, but am reading it now!
I will follow up when done...
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada |
|
| Back to top |
|
|
| dhuddles |
| Posted: Wed Nov 07, 2001 5:52 am Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
There is now a requirement in Solaris for the MQSeries qm.ini file to specify which SNA software package is being used, either SunLink SNA 9.1 or SNAP-IX. The default is SNAP-IX, and therefore you MUST add the LU62 stanza into the qm.ini if you wish to use SunLink. Here is what you need:
LU62:
MQCommLibrary=amqcc62a | amqcc62s
where amqcc62a means use SNAP-IX
and amqcc62s means use SunLink SNA
Things work perfectly now that I have defined this value. I hope this may help someone else in the future!
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada |
|
| Back to top |
|
|
| isreal |
| Posted: Wed Nov 07, 2001 7:51 am Post subject: |
|
|
Novice
Joined: 18 Sep 2001
Posts: 22
|
| So IBM had nothing to tell you?? |
|
| Back to top |
|
|
| dhuddles |
| Posted: Wed Nov 07, 2001 7:58 am Post subject: |
|
|
Newbie
Joined: 03 Nov 2001
Posts: 7
|
IBM was leading me off in different directions (with ancient "hits" on their database), and had missed this V5.2 Release Information completely! I had to pass the URL to the rep, and he admitted he was not aware of this.
Sometimes resources like this Forum have more experience than the so-called experts! But I did my best to make sure they are now "aware"!
_________________
David Huddleson
CCRA, Ottawa, Ontario, Canada
[ This Message was edited by: dhuddles on 2001-11-07 07:58 ] |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 07, 2001 11:27 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
For what it is worth, I just checked the MQSeries V5.2 Release Guide and there is a partial page that describes the parameter that you mentioned. It states that if this attribute (MQCommLibrary) is not specified, then SNAP-IX is the default.
[ This Message was edited by: bower5932 on 2001-11-07 11:28 ] |
|
| 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
|
|
|
|
