| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channels not starting in V2.1 under OpenVMS 6.2 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bennettj |
 Posted: Mon Oct 22, 2007 9:11 pm Post subject: Channels not starting in V2.1 under OpenVMS 6.2 |
 |
|
Newbie
Joined: 25 Jul 2001
Posts: 3
Location: CBH, Perth, Australia
|
I am unable to start both inbound/outbound channels under V2.1 of MQSeries running under OpenVMS 6.2.
I get the following error dump in the *.FDC file:-
LVLS :- 221 |
| Product Long Name :- MQSeries for VAX/Alpha |
| Vendor :- IBM |
| Probe Id :- XC171017 |
| Application Name :- MQM |
| Component :- xllDeleteSemSet |
| Build Date :- Apr 18 1997 |
| Userid :- |
| Program Name :- RUNMQCHL.EXE |
| Process :- 00001516 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal MQSeries error has occurred. |
| Comment1 :- 'error 0' from semctl. |
| VMS Errorcode :- -RMS-E-FNF, file not found (00018292) |
| VMS error :- |
| semctl: Semaphore block not allocated
Can anybody through any light on this problem.
Many thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Oct 22, 2007 10:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
On the understanding that what I know about this platform would fit comfortably on a very small piece of paper, my investigation into the problem would have started with the "file not found" error.
Is it a new install, or an old install that's just started throwing this error? Was any work doing on the system prior to the error? Etc? Etc?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bennettj |
| Posted: Mon Oct 22, 2007 10:39 pm Post subject: More details about the problem. |
|
|
Newbie
Joined: 25 Jul 2001
Posts: 3
Location: CBH, Perth, Australia
|
The Version of MQSeries is V2.1 which was installed back in 1997 and has been running smoothly ever since...except for the past couple of months.
Up until last week, I was able to stop and restart MQ and the channels would come up cleanly.
This is no longer the case.
I have tried deleting and recreating the queue manager and all processes, queues and channels - but to no avail.
Unfortunately, the Company no longer has the original install media (performed by 3rd party Company who no longer exist).
The platform is an old Alpha.
We are unable to upgrade the platform due to the application running on it, hence we are stuck with V2.1 of MQ until the application is replaced (scheduled for mid-2008).
We have been experiencing power spikes recently - this may have compounded the problem...? |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Mon Oct 22, 2007 11:04 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
It will be good to go for MQ V6, instead of still using mq 2.1
Please stick in to what vitor has suggested, check whether that particular file / exe is existing or not in the correct location/path
Thanks and Regards
gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 22, 2007 11:18 pm Post subject: Re: More details about the problem. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Bennettj wrote: |
| Up until last week, I was able to stop and restart MQ and the channels would come up cleanly. |
I'd almost be inclined to try restoring from last week's system backup. Certainly looking at the inventory of the backup would be worth it - see if this "file not found" can be found on it, look for other changes, that sort of thing.
| Bennettj wrote: |
| Unfortunately, the Company no longer has the original install media (performed by 3rd party Company who no longer exist). |
Oops.
| Bennettj wrote: |
| We are unable to upgrade the platform due to the application running on it, hence we are stuck with V2.1 of MQ until the application is replaced (scheduled for mid-2008). |
Again oops. Hope it's not running anything business critical, but then something which such an old hardware/software stack wouldn't be would it? Or at least you'd have the media in case of emergencies? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Tue Oct 23, 2007 2:15 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
It's been many many many years since I worked with MQ on VMS....
But I did get some hits by googling various fields in your FDC file:
RMS-E-FNF, file not found (00018292)
RMS-E-FNF VMS
RMS-E-FNF
'error 0' from semctl.
....and so forth.
I found some hits on IBM with this same type of error but different probe IDs. Since the probe IDs are not a match, you can't depend on the specifics of the IBM articles. But there did seem to be several mentions of system resource allocation which would be consistent with the semaphore block and the semctl reference in the FDC file. Also, I saw references to file security as possible problems.
Perhaps your VMS system administrator could help? I wonder if there have been changes in the OS or in other applications on the server that might have impacted system resources available to MQ.
I am just thinking out loud. I don't really have any concrete information for you, but I sure am sympathetic.
Shirley |
|
| 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
|
|
|
|
