| Author |
Message
|
| jeevan |
 Posted: Sat Oct 10, 2009 4:13 pm Post subject: The AMQCLCHL.TAB file (CCDT) is not created |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
When I created a client channel, the AMQCLCHL.TAB file did not get created. There was some problem in the queue manager so I have deleted the queue manager and was recreated. I am suspecting, whether this deletion of queue manager is causing this problem.
Also, when I created a client channel in another queue manager just check that my script is correct, the AMQCLCHL.TAB file was created but it is of original size 2008 bytes instead of 4008 ( not sure something like that). When I type the file, it only shows SYSTEM.DEF.CLNTCONN channel not the one I created.
There is no FDC file and nothing in error log.
The mq version is : MQ for windows ; 6.0.2.5
Any suggestions would be appreciated
Last edited by jeevan on Sat Oct 10, 2009 4:27 pm; edited 5 times in total |
|
| Back to top |
|
 |
| exerk |
| Posted: Sat Oct 10, 2009 4:47 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Just out of curiosity, what was the cause of the problem? Or was it that the environment variables were still set from a previous incarnation of a queue manager?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sat Oct 10, 2009 4:56 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
| Just out of curiosity, what was the cause of the problem? Or was it that the environment variables were still set from a previous incarnation of a queue manager? |
In fact, I wanted to test a script which create a queue manager, create server conn and client conn channel, copy the channel table to a directory, set the variables, and run the amqsputc. If any one of these steps is not performed, I will fix that script and rerun it.
Therefore, the queue manager is deleted a few times already.
The script is as follows:
===================
SET GESTOR=SSLQM
ENDMQM -i %GESTOR%
DLTMQM %GESTOR%
Rem 1. Setting up a non-SSL WebSphere MQ client
@echo Create queue manager (%GESTOR%).
crtmqm -u SSLQM.DLQ %GESTOR%
@echo Start queue manager
reM amqmdain qmgr start %GESTOR%
STRMQM %GESTOR%
@echo Create listener
@echo DEFINE LISTENER('LISTENER.TCP') TRPTYPE(TCP) PORT(33333) CONTROL(QMGR) | runmqsc %GESTOR%
@echo def ql(SSLQM.DLQ) | runmqsc %GESTOR%
@echo def ql(Q1) | runmqsc %GESTOR%
@echo def chl(SSL.CLIENTS) chltype(SVRCONN) | runmqsc %GESTOR%
@echo START LISTENER('LISTENER.TCP') | runmqsc %GESTOR%
Rem 2. Verify the non-SSL client connectivity
Rem 2.1.- Using WebSphere MQ server
set MQSERVER=SSL.CLIENTS/TCP/localhost(33333)
REM amqsputc Q1 SSLQM
REM amqsgetc Q1 SSLQM
Rem 2.2.- Using channel tables
Rem a. Create a client connection channel on the queue manager machine (this creates the channel
Rem table).
Rem b. Transfer the channel table file to the client machine.
Rem c. Set up the appropriate environment variables on the client machine.
Rem d. Test the WebSphere MQ client with channel tables.
Rem The sequence is :
Rem (a) enter set mqchl to verify we do not have the channel table environment variables set
ECHO def chl(SSL.CLIENTS) chltype(CLNTCONN) conname('LOCALHOST(33333)') replace | runmqsc %GESTOR%
Rem (a) as a result, you see a file called AMQCLCHL.TAB in your queue manager's @ipcc directory
Rem (b) copy FTP binary the AMQCLCHL.TAB file to the client machine, let's say the directory
md MQCLIENT
cd C:\MQCLIENT\
copy c:\mqm\qmgrs\SSLQM@ipcc\AMQCLCHL.TAB
Rem (c) set up the environment variables :
set mqchllib=C:\MQCLIENT
set mqchltab=AMQCLCHL.TAB
set mqserver=
amqsputc Q1 SSLQM
amqsgetc Q1 SSLQM |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Oct 10, 2009 7:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
But you never unset the environment variables. So next time check that the channel table as pointed to by the environment variables has the new entries... or at the end of your script clear the env vars
| Code: |
Rem (c) clear the environment variables :
set mqchllib=
set mqchltab= |
Standard M$ programming with defining env vars... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Oct 11, 2009 3:13 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
When I type the file, it only shows SYSTEM.DEF.CLNTCONN channel not the one I created.
....
copy c:\mqm\qmgrs\SSLQM@ipcc\AMQCLCHL.TAB
....
Rem (c) set up the environment variables :
set mqchllib=C:\MQCLIENT
set mqchltab=AMQCLCHL.TAB
set mqserver= |
'type' is not a reliable method for displaying the contents of CCDT files.
Missing a back slash between SSLQM and @ipcc ?
Always use uppercase for MQ environment variable names.
_________________
Glenn |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Oct 11, 2009 4:43 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| gbaddeley wrote: |
| Quote: |
When I type the file, it only shows SYSTEM.DEF.CLNTCONN channel not the one I created.
....
copy c:\mqm\qmgrs\SSLQM@ipcc\AMQCLCHL.TAB
....
Rem (c) set up the environment variables :
set mqchllib=C:\MQCLIENT
set mqchltab=AMQCLCHL.TAB
set mqserver= |
'type' is not a reliable method for displaying the contents of CCDT files.
Missing a back slash between SSLQM and @ipcc ?
Always use uppercase for MQ environment variable names. |
I fixed that typo already in the script.
I know, type is not a realiable but still in other case, I can see that.
I am thinking probably the installation is not correct for some reason.
I would have done further research but there is no clue. No error and non FDC. So, I am planning to give up and uninstall and install. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Oct 12, 2009 12:06 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| exerk wrote: |
| Just out of curiosity, what was the cause of the problem? Or was it that the environment variables were still set from a previous incarnation of a queue manager? |
The clue was in the question, and fjb_saper actually gave you the fish: "...But you never unset the environment variables...". Unset the variables before trying again
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 12, 2009 2:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It is better practice to set MQCHLTAB/MQCHLLIB to an explicit, known, value, than to unset them to attempt to have them take on a possibly unknown default value. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Oct 12, 2009 2:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqjeff wrote: |
| It is better practice to set MQCHLTAB/MQCHLLIB to an explicit, known, value, than to unset them to attempt to have them take on a possibly unknown default value. |
I've found in the past (WMQ V5.3 - Windows) that with the variables set, problems occurred when the only queue manager on the server was being recreated. Once the variables were completely deleted, everything was back to 'normal'.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon Oct 12, 2009 4:19 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Hmmm, you can use MO72 to maintain CCDT files reliably. Just be sure to tell it what version of MQ to generate the CCDT for.
I have no idea why runmqsc does not allow you to do the same. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 12, 2009 4:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| JosephGramig wrote: |
Hmmm, you can use MO72 to maintain CCDT files reliably. Just be sure to tell it what version of MQ to generate the CCDT for.
I have no idea why runmqsc does not allow you to do the same. |
Perhaps because MO72 essentially running on a client and not server knows it must get the table from the env vars.
I would expect runmqsc to try and go for the default location as this is the server install, expecting that anybody needing a client setup would refererence the files on the default location if they are on the same box?
And of course to allow it to work if you never define any env variables...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Oct 12, 2009 9:09 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
| exerk wrote: |
| Just out of curiosity, what was the cause of the problem? Or was it that the environment variables were still set from a previous incarnation of a queue manager? |
The clue was in the question, and fjb_saper actually gave you the fish: "...But you never unset the environment variables...". Unset the variables before trying again |
I run the script with resetting all the variables. But still no AMQCLCHL.TAB file is created.
I tried creating it in runmqsc SHELL and in explorer. All cased, same result. No FDC file is created. However, there is an error log.
qmgr log
=======
10/10/2009 16:35:12 - Process(4448.2) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4448), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:12 - Process(4448.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'LOGGER-IO' has ended.
EXPLANATION:
The Queue Manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(4756.2) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4756), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ7229: 4 log records accessed on queue manager 'SSLQM' during the log replay
phase.
EXPLANATION:
4 log records have been accessed so far on queue manager SSLQM during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ7230: Log replay for queue manager 'SSLQM' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager SSLQM.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ7231: 0 log records accessed on queue manager 'SSLQM' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager SSLQM during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ7232: Transaction manager state recovered for queue manager 'SSLQM'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager SSLQM.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager 'SSLQM'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager SSLQM ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(4756.3) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'CHECKPOINT' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4756), has started the CHECKPOINT
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ8003: WebSphere MQ queue manager 'SSLQM' started.
EXPLANATION:
WebSphere MQ queue manager 'SSLQM' started.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:13 - Process(4960.2) User(x4n9) Program(amqzmur0.exe)
AMQ5037: The Queue Manager task 'ERROR-LOG' has started.
EXPLANATION:
The Utility Task Manager, processId(1) type(4960), has started the ERROR-LOG
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:19 - Process(2812.1) User(x4n9) Program(crtmqm.exe)
AMQ8048: Default objects statistics : 43 created. 0 replaced. 0 failed.
EXPLANATION:
Information on the number of objects created or replaced successfully as well
as any failures that occurred while creating the default objects.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:19 - Process(4960.1) User(x4n9) Program(amqzmur0.exe)
AMQ5041: The Queue Manager task 'ERROR-LOG' has ended.
EXPLANATION:
The Queue Manager task ERROR-LOG has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:21 - Process(4756.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'CHECKPOINT' has ended.
EXPLANATION:
The Queue Manager task CHECKPOINT has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:21 - Process(4756.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'LOGGER-IO' has ended.
EXPLANATION:
The Queue Manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:21 - Process(3456.1) User(x4n9) Program(amqzxma0.exe)
AMQ8004: WebSphere MQ queue manager 'SSLQM' ended.
EXPLANATION:
WebSphere MQ queue manager 'SSLQM' ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(4784.2) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4784), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ7229: 5 log records accessed on queue manager 'SSLQM' during the log replay
phase.
EXPLANATION:
5 log records have been accessed so far on queue manager SSLQM during the log
replay phase in order to bring the queue manager back to a previously known
state.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ7230: Log replay for queue manager 'SSLQM' complete.
EXPLANATION:
The log replay phase of the queue manager restart process has been completed
for queue manager SSLQM.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ7231: 0 log records accessed on queue manager 'SSLQM' during the recovery
phase.
EXPLANATION:
0 log records have been accessed so far on queue manager SSLQM during the
recovery phase of the transactions manager state.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ7232: Transaction manager state recovered for queue manager 'SSLQM'.
EXPLANATION:
The state of transactions at the time the queue manager ended has been
recovered for queue manager SSLQM.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ7233: 0 out of 0 in-flight transactions resolved for queue manager 'SSLQM'.
EXPLANATION:
0 transactions out of 0 in-flight at the time queue manager SSLQM ended have
been resolved.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(4784.3) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'CHECKPOINT' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4784), has started the CHECKPOINT
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ8003: WebSphere MQ queue manager 'SSLQM' started.
EXPLANATION:
WebSphere MQ queue manager 'SSLQM' started.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:22 - Process(1744.2) User(x4n9) Program(amqzmur0.exe)
AMQ5037: The Queue Manager task 'ERROR-LOG' has started.
EXPLANATION:
The Utility Task Manager, processId(1) type(1744), has started the ERROR-LOG
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(1744.3) User(x4n9) Program(amqzmur0.exe)
AMQ5037: The Queue Manager task 'STATISTICS' has started.
EXPLANATION:
The Utility Task Manager, processId(1) type(1744), has started the STATISTICS
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(5840.1) User(x4n9) Program(amqrrmfa.exe)
AMQ9410: Repository manager started
EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(4784.4) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'ASYNCQ' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4784), has started the ASYNCQ task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(4784.5) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'EXPIRER' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(4784), has started the EXPIRER
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5022: The Channel Initiator has started. ProcessId(5252).
EXPLANATION:
The Channel Initiator process has started.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5024: The Command Server has started. ProcessId(4428).
EXPLANATION:
The Command Server process has started.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:23 - Process(5252.1) User(x4n9) Program(runmqchi.exe)
AMQ8024: WebSphere MQ channel initiator started.
EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
-------------------------------------------------------------------------------
10/10/2009 16:35:25 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5026: The Listener 'LISTENER.TCP' has started. ProcessId(6044).
EXPLANATION:
The Listener process has started.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:48 - Process(5840.1) User(x4n9) Program(amqrrmfa.exe)
AMQ9411: Repository manager ended normally.
EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:49 - Process(5252.1) User(x4n9) Program(runmqchi.exe)
AMQ9542: Queue manager is ending.
EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 941 --------------------------------------------------------
10/12/2009 08:49:49 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5025: The Command Server has ended. ProcessId(4428).
EXPLANATION:
The Command Server process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:49 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5023: The Channel Initiator has ended. ProcessId(5252).
EXPLANATION:
The Channel Initiator process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:49 - Process(4784.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'ASYNCQ' has ended.
EXPLANATION:
The Queue Manager task ASYNCQ has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:49 - Process(4784.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'EXPIRER' has ended.
EXPLANATION:
The Queue Manager task EXPIRER has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:49 - Process(1744.1) User(x4n9) Program(amqzmur0.exe)
AMQ5041: The Queue Manager task 'ERROR-LOG' has ended.
EXPLANATION:
The Queue Manager task ERROR-LOG has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:50 - Process(4636.1) User(x4n9) Program(amqzmgr0.exe)
AMQ5027: The Listener 'LISTENER.TCP' has ended. ProcessId(6044).
EXPLANATION:
The Listener process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:55 - Process(4784.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'LOGGER-IO' has ended.
EXPLANATION:
The Queue Manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
710/12/2009 08:49:55 - Process(5740.1) User(x4n9) Program(amqzxma0.exe)
AMQ8004: WebSphere MQ queue manager 'SSLQM' ended.
EXPLANATION:
WebSphere MQ queue manager 'SSLQM' ended.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:49:57 - Process(3568.2) User(x4n9) Program(amqzmuc0.exe)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.
EXPLANATION:
The Utility Task Manager, processId(0) type(3568), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------
10/12/2009 08:50:02 - Process(3568.1) User(x4n9) Program(amqzmuc0.exe)
AMQ5041: The Queue Manager task 'LOGGER-IO' has ended.
EXPLANATION:
The Queue Manager task LOGGER-IO has ended.
ACTION:
None.
-------------------------------------------------------------------------------
===============MQ SYSTEM LOG=============
it is complaining about the MQSERVER variable setup
================
10/12/2009 09:59:44 - Process(5536.1) User(x4n9) Program(amqsputc.exe)
AMQ9566: Invalid MQSERVER value
EXPLANATION:
The value of the MQSERVER environment variable was ''. The variable should be
in the format 'ChannelName/Protocol/ConnectionName'.
ACTION:
Correct the MQSERVER value and retry the operation.
Last edited by jeevan on Mon Oct 12, 2009 9:27 am; edited 1 time in total |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Oct 12, 2009 9:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Was there a particular reason you posted everything above the actual error? Remove the variables completely then try it, but not in the same session as you use to remove the variables. And as you have seen, WMQ does not like the MQSERVER variable being set to a null value.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Oct 12, 2009 9:29 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
| Was there a particular reason you posted everything above the actual error? Remove the variables completely then try it, but not in the same session as you use to remove the variables. And as you have seen, WMQ does not like the MQSERVER variable being set to a null value. |
No. I wanted to tell everything. That is complete log.
I was not sure why the logger was ended and restarted again. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 12, 2009 12:44 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks like you are trying to do a client put after having cleared the environment variable...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
