Author |
Message
|
neeeelus |
Posted: Sun Oct 04, 2009 5:04 am Post subject: Issue while making an MQSI Commands Script in Windows |
|
|
 Novice
Joined: 28 Jul 2008 Posts: 12
|
Hi All,
Sorry if I am asking a simple question, as I am new in writing the script. My question is I am Trying to create a script in windows to create all the Broker components. In which initial I tried of Creating a script with simple command to see the components in windows I.e. mqsilist
The script i wrote is
echo Try To Create a Script
cd C:\Program Files\IBM\MQSI\6.1\bin\
mqsilist
pause
The message I am getting is
The user environment was not adequately prepared to continue execution. Locate a
nd run the profile supplied with the product. This file is called mqsiprofile.cm
d, and is located in the bin subdirectory for the product.
Can any one help me by providing a sample script and configurations should be done before executing a script in windows. _________________ Thanks & Regards,
Neeeelu. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Oct 04, 2009 7:00 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
You need to initialise the WBI environment before the mqsi* commands are valid.
You don't need to cd to the runtime install directory either.
You have two options.
1) run your script from a WBI Command Console window
OR
2) invoke the mqsiprofile script from within you script so that you can run it from a normal command window. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
neeeelus |
Posted: Sun Oct 04, 2009 7:30 am Post subject: |
|
|
 Novice
Joined: 28 Jul 2008 Posts: 12
|
Hi smdavies99,
Thanks for you reply
smdavies99 wrote: |
You need to initialise the WBI environment before the mqsi* commands are valid. |
How to initialise the WBI env before the mqsi* commands..
smdavies99 wrote: |
1) run your script from a WBI Command Console window |
But I am trying to create a .bat file which should be done automation of creation of components in windows at development machines.
smdavies99 wrote: |
2) invoke the mqsiprofile script from within you script so that you can run it from a normal command window. |
When i invoke the mqsiprofile the window is closing automatically with out showing any other commands execution.
Please give me a sample script, how to create a .bat file for automation _________________ Thanks & Regards,
Neeeelu. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Oct 04, 2009 7:55 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
A command console window is a
Command Windows with the mqsiprofile script already applied.
All my scripts for broker creation etc run from this type of window.
What have you tried to invoke the mqsiprofile script from a normal command window?
Have you read the details on this in the WBI info centre?
Have you googled for "mqsiprofile windows" _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Sun Oct 04, 2009 8:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can use the CALL command in windows dos to invoke any .bat or .cmd file (a text file! with a special extension!) in the current environment rather than starting a new environment. |
|
Back to top |
|
 |
neeeelus |
Posted: Sun Oct 04, 2009 9:10 am Post subject: |
|
|
 Novice
Joined: 28 Jul 2008 Posts: 12
|
smdavies99 wrote: |
What have you tried to invoke the mqsiprofile script from a normal command window? |
CALL mqsiprofile (Sorry i don't know whether it is correct or not.)
Now I am getting an alert saying MQM.dll is missing in machine. _________________ Thanks & Regards,
Neeeelu. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Oct 04, 2009 9:28 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Do you have WMQ Server installed on the system?
What output does the following commands give?
_________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
neeeelus |
Posted: Sun Oct 04, 2009 9:50 pm Post subject: |
|
|
 Novice
Joined: 28 Jul 2008 Posts: 12
|
Hi smdavies99,
smdavies99 wrote: |
Do you have WMQ Server installed on the system?
What output does the following commands give?
|
The out puts for the above commands are
smdavies99 wrote: |
dspmqver |
Name: WebSphere MQ
Version: 6.0.0.0
CMVC level: p000-L050519
BuildType: IKAP - (Production)
QMNAME(QMANAGER) STATUS(Running) _________________ Thanks & Regards,
Neeeelu. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Oct 04, 2009 10:37 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Ok, you have WMQ BUT BUT BUT BUT BUT BUT BUT it is totally unpatched.
Please apply service packs. 6.0.2.5 is a good one.
Then try your script (less the call to mqsiprofile) from a WBI Command Console Window. Do you get the same mqm.dll error?
If not then there is a difference in the %PATH% etc between the two environments.
[/b] _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|