| Author |
Message
|
| vmani |
 Posted: Wed Nov 16, 2005 11:17 pm Post subject: wmq 5.3 installation on Redhat 9.0 |
 |
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
Hi all,
I am new to MQseries and i am in the process of installing it (5.3) in redhat 9.0. It seems that wmq can work only in Linux threads and redhat 9.0 works on NPTL. How can i resolve this issue ??
I tried up setting LD_ASSUME_KERNEL=2.4.19; The filesystems are created. And in the process of verification of installation. i could not create a qmanager. when i give crtmqm qmgr, it gives me no reply neither errors and does not reply to the shell! But i see that the filesystems are created in /var/mqm/qmanager/"qmgrname". When i try to start the qmanager, it gives a message "WMQ is not able to display the error maessage 893". What might be the problem ?? Also i want to know what are all the linux versions that it currently supports !!
Thanks in advance,
Mani... |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Nov 17, 2005 1:47 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I tried up setting LD_ASSUME_KERNEL=2.4.19 |
Where did you set this up. Was it in effect from the userid where you tried to create the QM.
| Quote: |
| WMQ is not able to display the error maessage 893 |
That should have cut an FDC in the error directory. Post the top section here.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| vmani |
| Posted: Thu Nov 17, 2005 3:00 am Post subject: Re: wmq5.3 installation on redhat 9.0 |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
The user id i set up the LD_ASSUME_KERNEL was root. and i tried to create the queue manager from mqm user.
And iam not able to show the FDC file currently.
Can u please let me know the cause of my problem ?
Thanks,
Mani. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 17, 2005 3:10 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| The user id i set up the LD_ASSUME_KERNEL was root. and i tried to create the queue manager from mqm user. |
What exactly do you mean? LD_ASSUME_KERNEL must be set in your "mqm" user environment. Is this the case?
_________________
-wayne |
|
| Back to top |
|
|
| vmani |
| Posted: Thu Nov 17, 2005 4:29 am Post subject: set in root user !! |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
Not exactly !! the environment variable is set up in "root" user !!
Is that a problem ?? If that is set up in the "mqm" user will my problem get resolved ??
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 17, 2005 4:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The environment variable MUST be set up in the CURRENT environment of all MQ processes.
Adding it to root's .profile or whatever DOES NOT guarantee this.
Try this. With your current setup log in as root. Then su - mqm.
Then echo $LD_ASSUME_KERNEL.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vmani |
| Posted: Thu Nov 17, 2005 8:50 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
All,
Can i know on what versions of Linux, the websphere 5.3 will be working fine without the problems on threads (NPTL or linux threads) ?
Other than redhat 7.2 what are all the others that can go fine with MQ 5.3 ??
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 17, 2005 9:53 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
WMQ V6 fixes the threading problem, so you don't need LD_ASSUME_KERNEL with v6.
I've used RH 7.3, and RH9 with v5.3 without problems.
I've used FC3 with v6.0.
(but they aren't officially supported platforms).
_________________
-wayne |
|
| Back to top |
|
|
| vmani |
| Posted: Thu Nov 17, 2005 8:15 pm Post subject: Error report on creating qmanager FIRST_QM |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
First Failure System Report:
==================
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday November 18 09:54:50 IST 2005 |
| Host Name :- localhost.localdomain (Linux 2.4.20- |
| PIDS :- 5724B4104 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000502 (mqm) |
| Program Name :- crtmqm |
| Thread-Process :- 00002813 |
| Thread :- 00000006 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2 2 |
| Arith2 :- 2808 af8 |
| Comment1 :- SIGINT |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST
Component Dumps (Thread 00000006)
-------------------------------------
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Friday November 18 09:54:51 IST 2005 |
| Host Name :- localhost.localdomain (Linux 2.4.20- |
| PIDS :- 5724B4104 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000502 (mqm) |
| Program Name :- crtmqm |
| Thread-Process :- 00002813 |
| Thread :- 00000006 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 1 |
| Arith1 :- 2 2 |
| Arith2 :- 2808 af8 |
| Comment1 :- SIGINT |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST
---{ xcsRequestThreadMutexSem
---} xcsRequestThreadMutexSem rc=OK
---{ xcsDisplayMessageForSubpool
----{ xcsQueryValueForSubpool
----} xcsQueryValueForSubpool rc=OK
----{ xcsDisplayMessage
-----{ xcsQueryDateTime2
------{ xcsLocaltime
------} xcsLocaltime rc=OK
-----} xcsQueryDateTime2 rc=OK
----} xcsDisplayMessage rc=OK
---} xcsDisplayMessageForSubpool rc=OK
---{ xcsDisplayMessageForSubpool
----{ xcsQueryValueForSubpool
----} xcsQueryValueForSubpool rc=OK
----{ xcsDisplayMessage
-----{ xcsQueryDateTime2
------{ xcsLocaltime
------} xcsLocaltime rc=OK
-----} xcsQueryDateTime2 rc=OK
----} xcsDisplayMessage rc=OK
---} xcsDisplayMessageForSubpool rc=OK
---{ xcsLocaltime
---} xcsLocaltime rc=OK
---{ xcsQueryValue
---} xcsQueryValue rc=OK
---{ xcsQueryValue
---} xcsQueryValue rc=OK
---{ xcsFmtOpen
---} xcsFmtOpen rc=OK
---{ xcsFmtClose
---} xcsFmtClose rc=OK
---{ xcsReleaseThreadMutexSem
---} xcsReleaseThreadMutexSem rc=OK
---{ xcsReportError
----{ xcsOpenlog
----} xcsOpenlog rc=OK
----{ xcsSyslog
----} xcsSyslog rc=OK
---} xcsReportError rc=OK
--} xcsFFST rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST
.Log file Created:
==========
11/17/2005 09:19:01 AM
AMQ6184: An internal WebSphere MQ error has occurred on queue manager FIRST_QM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2827.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 703 --------------------------------------------------------
11/17/2005 09:19:02 AM
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 0. This message is issued in
association with other messages.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 669 --------------------------------------------------------
11/17/2005 09:19:02 AM
AMQ6184: An internal WebSphere MQ error has occurred on queue manager FIRST_QM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 2827.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
===============================================
Thanks all for the informations, and please let me know the corrective actions i need to do !!
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Nov 17, 2005 11:00 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Unfortunately the FDCs and the messages are from 2 different events:
From the FDCs:
| Quote: |
| Date/Time :- Friday November 18 09:54:50 IST 2005 |
| Thread-Process :- 00002813 | |
And
| Quote: |
| Date/Time :- Friday November 18 09:54:51 IST 2005 |
| Thread-Process :- 00002813 | |
And the logs:
| Quote: |
11/17/2005 09:19:01 AM
The failing process is process 2827. |
And:
| Quote: |
11/17/2005 09:19:02 AM
The failing process is process 2827. |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| vmani |
| Posted: Thu Nov 17, 2005 11:23 pm Post subject: |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
Hi eddie,
Yes, they are from 2 different events but i wonder how the process and thread ids are same if they are from 2 different events!!
Can you find any error there so that my problem can be fixed.. This might be generated when i tried to create a queue manager FIRST_QM !!
I tried to set the environment LD_ASSUME_KERNEL in mqm user. That also did not work out !! Any suggestions please !!
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| vmani |
| Posted: Fri Nov 18, 2005 1:27 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
Thanks, and i will soon send that file for 2827. crtmqm command did not give me any output. After entering that command, it does not return back to the shell prompt !! Thats why i pressed ^c to return back to the shell !!!
Anyway i will send that file and please help me to sort out that issue !!
Can i know where v6.0 (Free version for my personal use) would be available for linux for download and its size ??
Thanks in advance !!
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| vmani |
| Posted: Fri Nov 18, 2005 9:02 pm Post subject: Few lines of AMQ02827.0.FDC!! |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday November 17 09:19:02 IST 2005 |
| Host Name :- localhost.localdomain (Linux 2.4.20- |
| PIDS :- 5724B4104 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- AL008005 |
| Application Name :- MQM |
| Component :- almPerformReDoPass |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000502 (mqm) |
| Program Name :- amqzxma0 |
| Thread-Process :- 00002827 |
| Thread :- 00000001 |
| QueueManager :- FIRST_QM |
| Major Errorcode :- krcE_UNEXPECTED_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
kpiStartup
apiStartup
almPerformReDoPass
xcsFFST
MQM Trace History
------{ adhClose
-------{ adiCloseFile
-------} adiCloseFile rc=OK
-------{ aduReleaseFileCtl
-------} aduReleaseFileCtl rc=OK
------} adhClose rc=OK
-----} aodRead rc=OK
-----{ xcsQueryDateTime
------{ xcsLocaltime
------} xcsLocaltime rc=OK
-----} xcsQueryDateTime rc=OK
-----{ aocObjectDoctor
------{ aodWrite
-------{ adhOpen
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=arcE_OBJECT_MISSING
--------{ aduAllocFileCtl
--------} aduAllocFileCtl rc=OK
--------{ aduBuildOSName
--------} aduBuildOSName rc=OK
--------{ adiOpenFile
--------} adiOpenFile rc=OK
-------} adhOpen rc=OK
-------{ adhWrite
--------{ adiWriteFile
--------} adiWriteFile rc=OK
-------} adhWrite rc=OK
-------{ adhClose
--------{ adiCloseFile
--------} adiCloseFile rc=OK
--------{ aduReleaseFileCtl
--------} aduReleaseFileCtl rc=OK
-------} adhClose rc=OK
------} aodWrite rc=OK
-----} aocObjectDoctor rc=OK
----} aocObjectDoctor rc=OK
----{ xcsReleaseMutexSem
----} xcsReleaseMutexSem rc=OK
---} aocEnquireObject rc=OK
---{ xcsQueryTime
---} xcsQueryTime rc=OK
--} aocLoadCatalogue rc=OK
--{ almPerformReDoPass
---{ hlgQueryLogRestartLsn
----{ hosRequestMutexSem
----} hosRequestMutexSem rc=OK
----{ hosReleaseMutexSem
----} hosReleaseMutexSem rc=OK
---} hlgQueryLogRestartLsn rc=OK
---{ alsReadCheckPoint
---} alsReadCheckPoint rc=arcE_OBJECT_MISSING
---{ xcsGetMem
---} xcsGetMem rc=OK
---{ hlgScanLogBegin
----{ hosRequestMutexSem
----} hosRequestMutexSem rc=OK
----{ hosReleaseMutexSem
----} hosReleaseMutexSem rc=OK
----{ mqlpgrlg
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ mqlpgpst
------{ hosResetWaitPostArea
-------{ xcsResetEventSem
--------{ xlsResetEvent
--------} xlsResetEvent rc=OK
-------} xcsResetEventSem rc=OK
------} hosResetWaitPostArea rc=OK
------{ hosPostWaitPostArea
-------{ xcsPostEventSem
--------{ xlsPostEvent
---------{ xlsLockEvent
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsPostEvent rc=OK
-------} xcsPostEventSem rc=OK
------} hosPostWaitPostArea rc=OK
------{ hosWaitWaitPostArea
-------{ xcsWaitEventSem
--------{ xlsWaitEvent
---------{ xlsLockEvent
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsWaitEvent rc=OK
-------} xcsWaitEventSem rc=OK
------} hosWaitWaitPostArea rc=OK
-----} mqlpgpst rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
----} mqlpgrlg rc=hrcW_LOG_RECD_TRUNCATED
---} hlgScanLogBegin rc=OK
---{ hlgScanLogRecord
----{ mqlpgrlg
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ mqlpgpst
------{ hosResetWaitPostArea
-------{ xcsResetEventSem
--------{ xlsResetEvent
--------} xlsResetEvent rc=OK
-------} xcsResetEventSem rc=OK
------} hosResetWaitPostArea rc=OK
------{ hosPostWaitPostArea
-------{ xcsPostEventSem
--------{ xlsPostEvent
---------{ xlsLockEvent
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsPostEvent rc=OK
-------} xcsPostEventSem rc=OK
------} hosPostWaitPostArea rc=OK
------{ hosWaitWaitPostArea
-------{ xcsWaitEventSem
--------{ xlsWaitEvent
---------{ xlsLockEvent
----------{ xllSpinLockRequest
----------} xllSpinLockRequest rc=OK
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsWaitEvent rc=OK
-------} xcsWaitEventSem rc=OK
------} hosWaitWaitPostArea rc=OK
-----} mqlpgpst rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
----} mqlpgrlg rc=OK
---} hlgScanLogRecord rc=OK
---{ apiReplayLogRecord
----{ aocReplayLogRecord
-----{ aouLocateEntry
------{ aotLocateEntryByName
------} aotLocateEntryByName rc=OK
-----} aouLocateEntry rc=OK
----} aocReplayLogRecord rc=OK
---} apiReplayLogRecord rc=OK
---{ hlgScanLogRecord
----{ mqlpgrlg
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
----} mqlpgrlg rc=OK
---} hlgScanLogRecord rc=OK
---{ apiReplayLogRecord
----{ aocReplayLogRecord
-----{ aotLocateEntryByQid
-----} aotLocateEntryByQid rc=OK
-----{ aocObjectDoctor
------{ aodWrite
-------{ adhOpen
--------{ aduLocateFileCtl
--------} aduLocateFileCtl rc=arcE_OBJECT_MISSING
--------{ aduAllocFileCtl
--------} aduAllocFileCtl rc=OK
--------{ aduBuildOSName
--------} aduBuildOSName rc=OK
--------{ adiOpenFile
--------} adiOpenFile rc=OK
-------} adhOpen rc=OK
-------{ adhWrite
--------{ adiWriteFile
--------} adiWriteFile rc=OK
-------} adhWrite rc=OK
-------{ adhClose
--------{ adiCloseFile
--------} adiCloseFile rc=OK
--------{ aduReleaseFileCtl
--------} aduReleaseFileCtl rc=OK
-------} adhClose rc=OK
------} aodWrite rc=OK
-----} aocObjectDoctor rc=OK
----} aocReplayLogRecord rc=OK
---} apiReplayLogRecord rc=OK
---{ hlgScanLogRecord
----{ mqlpgrlg
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
----} mqlpgrlg rc=OK
---} hlgScanLogRecord rc=OK
---{ apiReplayLogRecord
----{ aocReplayLogRecord
-----{ aotLocateEntryByQid
-----} aotLocateEntryByQid rc=OK
-----{ aocCompleteCreation
-----} aocCompleteCreation rc=OK
----} aocReplayLogRecord rc=OK
---} apiReplayLogRecord rc=OK
---{ hlgScanLogRecord
----{ mqlpgrlg
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
-----{ hosRequestMutexSem
-----} hosRequestMutexSem rc=OK
-----{ mqlpgpst
------{ hosResetWaitPostArea
-------{ xcsResetEventSem
--------{ xlsResetEvent
--------} xlsResetEvent rc=OK
-------} xcsResetEventSem rc=OK
------} hosResetWaitPostArea rc=OK
------{ hosPostWaitPostArea
-------{ xcsPostEventSem
--------{ xlsPostEvent
---------{ xlsLockEvent
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsPostEvent rc=OK
-------} xcsPostEventSem rc=OK
------} hosPostWaitPostArea rc=OK
------{ hosWaitWaitPostArea
-------{ xcsWaitEventSem
--------{ xlsWaitEvent
---------{ xlsLockEvent
---------} xlsLockEvent rc=OK
---------{ xlsUnlockEvent
---------} xlsUnlockEvent rc=OK
--------} xlsWaitEvent rc=OK
-------} xcsWaitEventSem rc=OK
------} hosWaitWaitPostArea rc=OK
-----} mqlpgpst rc=OK
-----{ hosReleaseMutexSem
-----} hosReleaseMutexSem rc=OK
----} mqlpgrlg rc=hrcE_MQLP_LASTLOG
----{ mqlpgcfg
----} mqlpgcfg rc=OK
---} hlgScanLogRecord rc=hrcI_END_OF_LOG
---{ xcsBuildDumpPtr
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xcsBuildDumpPtr rc=OK
---{ xcsBuildDumpPtr
---} xcsBuildDumpPtr rc=OK
---{ xcsFFST
Flag for start chkpt seen
0xbfffbfa0 00000000
Can you please tell me the problem description here !!
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat Nov 19, 2005 2:53 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Have you tried creating a qmgr after you put a csd on (like csd11?)
_________________
-wayne |
|
| Back to top |
|
|
| vmani |
| Posted: Sun Nov 20, 2005 5:56 am Post subject: |
|
|
Newbie
Joined: 16 Nov 2005
Posts: 9
Location: India
|
Hai,
No i have not tried with that !! I think it is a fix package.. what is the exact problem that happened (I am pretty new !! ) and if i install that, will that be resolved ??
Thanks for all replies !!
_________________
Thanks,
Mani. |
|
| Back to top |
|
|
|
|
