How to install and configure a qmgr on Win 2008 in a VCS Cluster

Hi,
I need to install and configure a qmgr  (mq V7.0.1) on WIN 2008 VCS cluster.
Has any one done this . can they share how did it?

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

How to install and configure a qmgr on Win 2008 in a VCS Cluster

Hi,
I need to install and configure a qmgr  (mq V7.0.1) on WIN 2008 VCS cluster.
Has any one done this . can they share how did it?

thanks In advance

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Co-locating WMQ6 and WMQ7 client installations

Re: Co-locating WMQ6 and WMQ7 client installations

Inquire head scratcher

All,

I've created an API Exit to do some testing.  I'm running it on WMQ 
v6.0.2.7 on WinXP.

I'm scratching my head over data being passed on the API Exit's 
Inquire interface.  Note: I've registered both the MQXR_BEFORE and 
MQXR_AFTER for the MQXF_INQ (Inquire Interface).

Every 20 seconds, the command server issues an MQ Inquire 
command.  The data the API Exit Inquire interface is receiving is:
SelectorCount=1
Selectors=13
IntAttrCount=1
IntAttrs=9000
CharAttrLength=0
CharAttrs=

I thought the "Selectors" values come from MQIA_* and MQCA_* 
values.  13 is MQIA_MAX_MSG_LENGTH.  Also, IntAttrs has a value of 
9000 but there is no such value from MQIA_* or MQCA_* or anything 
else that I could find.

When I run a program to issue a PCF call to list the queues, the 
"Selectors" and "IntAttrs" have values from MQIA_* and MQCA_* but the 
command server's Inquire call does not make sense and what is 9000?

Anybody got any guesses?  (Anybody from IBM want to chime in?)

Maybe I'm still high from the Olympics but it doesn't make any sense to me.

Regards,
Roger Lacroix

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Re: Inquire head scratcher

Hi Roger,

isn't 9000 the response value? Or on the BEFORE call it would be unitialized storage.

On the AFTER call, it should be the value of MAXMSGL of the object which was inquired on. You would need to
trace back to the MQOD on the MQOPEN call which creates the handle to work out which object that is.

Regards,

Neil Casey.

> Roger Lacroix <roger.lacroix@...> wrote:
> 
> All,
> 
> I've created an API Exit to do some testing.  I'm running it on WMQ 
> v6.0.2.7 on WinXP.
> 
> I'm scratching my head over data being passed on the API Exit's 
> Inquire interface.  Note: I've registered both the MQXR_BEFORE and 
> MQXR_AFTER for the MQXF_INQ (Inquire Interface).
> 
> Every 20 seconds, the command server issues an MQ Inquire 
> command.  The data the API Exit Inquire interface is receiving is:
> SelectorCount=1
> Selectors=13
> IntAttrCount=1
> IntAttrs=9000
> CharAttrLength=0
> CharAttrs=
> 
> I thought the "Selectors" values come from MQIA_* and MQCA_* 
> values.  13 is MQIA_MAX_MSG_LENGTH.  Also, IntAttrs has a value of 
> 9000 but there is no such value from MQIA_* or MQCA_* or anything 
> else that I could find.
> 
> When I run a program to issue a PCF call to list the queues, the 
> "Selectors" and "IntAttrs" have values from MQIA_* and MQCA_* but the 
> command server's Inquire call does not make sense and what is 9000?
> 
> Anybody got any guesses?  (Anybody from IBM want to chime in?)
> 
> Maybe I'm still high from the Olympics but it doesn't make any sense to 
> me.
> 
> 
> Regards,
> Roger Lacroix
> 
> To unsubscribe, write to
LISTSERV@... and,
> in the message body (not the subject), write: SIGNOFF MQSERIES
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Re: Co-locating WMQ6 and WMQ7 client installations

Fwd: Re: Inquire head scratcher

Oops.  I replied directly to Neil rather than the list.  Below is my 
response to Neil.

Regards,
Roger Lacroix

>Date: Wed, 03 Mar 2010 01:07:33 -0500
>To: Neil_Casey@...
>From: Roger Lacroix <roger.lacroix@...>
>Subject: Re: Inquire head scratcher
>
>Hi Neil,
>
>Actually, the API Exit receives the same info for both 'before and 
>'after' calls to the Inquire interace.  The only MQOPEN performed by 
>the command server was to SYSTEM.ADMIN.COMMAND.QUEUE.
>
>
>Regards,
>Roger Lacroix
>
>At 12:34 AM 3/3/2010, you wrote:
>>Hi Roger,
>>
>>isn't 9000 the response value? Or on the BEFORE call it would be 
>>unitialized storage.
>>
>>On the AFTER call, it should be the value of MAXMSGL of the object 
>>which was inquired on. You would need to trace back to the MQOD on 
>>the MQOPEN call which creates the handle to work out which object that is.
>>
>>Regards,
>>
>>Neil Casey.
>>
>>
>>
>> > Roger Lacroix <roger.lacroix@...> wrote:
>> >
>> > All,
>> >
>> > I've created an API Exit to do some testing.  I'm running it on WMQ
>> > v6.0.2.7 on WinXP.
>> >
>> > I'm scratching my head over data being passed on the API Exit's
>> > Inquire interface.  Note: I've registered both the MQXR_BEFORE and
>> > MQXR_AFTER for the MQXF_INQ (Inquire Interface).
>> >
>> > Every 20 seconds, the command server issues an MQ Inquire
>> > command.  The data the API Exit Inquire interface is receiving is:
>> > SelectorCount=1
>> > Selectors=13
>> > IntAttrCount=1
>> > IntAttrs=9000
>> > CharAttrLength=0
>> > CharAttrs=
>> >
>> > I thought the "Selectors" values come from MQIA_* and MQCA_*
>> > values.  13 is MQIA_MAX_MSG_LENGTH.  Also, IntAttrs has a value of
>> > 9000 but there is no such value from MQIA_* or MQCA_* or anything
>> > else that I could find.
>> >
>> > When I run a program to issue a PCF call to list the queues, the
>> > "Selectors" and "IntAttrs" have values from MQIA_* and MQCA_* but the
>> > command server's Inquire call does not make sense and what is 9000?
>> >
>> > Anybody got any guesses?  (Anybody from IBM want to chime in?)
>> >
>> > Maybe I'm still high from the Olympics but it doesn't make any sense to
>> > me.
>> >
>> >
>> > Regards,
>> > Roger Lacroix
>> >
>> > To unsubscribe, write to
LISTSERV@... and,
>> > in the message body (not the subject), write: SIGNOFF MQSERIES
>> > Instructions for managing your mailing list subscription are provided in
>> > the Listserv General Users Guide available at http://www.lsoft.com
>> > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
>>
>>To unsubscribe, write to
LISTSERV@... and,
>>in the message body (not the subject), write: SIGNOFF MQSERIES
>>Instructions for managing your mailing list subscription are provided in
>>the Listserv General Users Guide available at http://www.lsoft.com
>>Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Re: Inquire head scratcher

WMQ v7.0.1.1 and Java client-side security exits

All,

Anybody using Java client-side security exits with WMQ Client 
v7.0.1.1 may find that it no longer works after upgrading to v7.0.1.1.

In WMQ v7.0.1.1, IBM introduced a fix for APAR IC63753.
APAR IC63753 says:
The size of the AgentBuffer supplied by the MQ Java client to a 
security exit is zero, when the MQ C client supplies a minimum buffer size.

IBM fixed it by making ALL Java security message exit buffers 3968 bytes.

Hence, I had IBM create a fix for the fix.  If you are using Java 
client-side security exits with WMQ Client v7.0.1.1 then you need to 
apply APAR IZ69820.

Regards,
Roger Lacroix
Capitalware Inc.

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES