Connectivitye from Client to Server : error 2035: URGENT !!!

2002-05-29 Thread hegde

Hi All,

I am having connectivity problem from client to
server.

I have created two channels channel1 and channel2.

1. I am able to connect the  local queue
(ORANGE.LOCAL.QUEUE) using channel2 with any user
and from any client O/S becaue in I have given
MCAUSER('mqm')

2. But I am not able to connect the local
queue(ORANGE.LOCAL.QUEUE) using channel1, I tried all
options like MCAUSER (' ') or MCAUSER('prakash')or
MCSUSER('NTACCOUNT'). I created the local unix account
same as nt account, but still it's not working.

3. Can some one help me with Examples.
4. MQSeries V5.2 Server running on Solaris 2.8, and
NT, windows 2000, Solaris 2.8
5. Below is my setup
=
1. I have created the Queue Manager as
crtmqm -q saturn.queue.manager
strmqm saturn.queue.manager
2.  define qlocal (ORANGE.LOCAL.QUEUE)
3.  define channel (CHANNEL1) +
chltype (SVRCONN) +
MCAUSER (' ') +
TRPTYPE (TCP)
4.  I have modified the inetd and services file as per
document.
5.  Started command Server  and started listner and
channel (from runmqsc prompt)
6. On sun solaris I have set the environment as
MQSERVER=CHANNEL1/TCP/'199.221.81.102'
   from solaris system I am able put the message as
   amqsputc ORANGE.LOCAL.QUEUE saturn.manager.queue
   and no problem in receive message using amqsgetc
7. On windows NT system I have set the MQSERVER
environment as
SET MQSERVER=CHANNEL1/TCP/199.221.81.102
amqsputc ORANGE.LOCAL.QUEUE saturn.queue.manager
===

I am getting MCONN ended the connection reason
2035

I don't know what I am missing or doing wrong. I
request some one to correct my mistake with example or
guide me.

I appreciate you help.

Thanks
Prakash



__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Out of Office AutoReply: oye chaal sutta peeneeeeee ...jaldi aaja

2002-05-29 Thread Amit Gandotra

Sorry for the last mail .. It was just by mistake while replying to one of
my fren's mail.

Sorry once again.

Regards,
---
Amit Gandotra
Certified MQSeries Specialist
TechSpan India Ltd.
A-35, Sector#16,
Noida - 201301 (U.P.) India
Tel: - 00-120-4512710/11/12



-Original Message-
From: Conor Sewell [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 10:32 AM
To: Amit Gandotra
Subject: Out of Office AutoReply: oye chaal sutta peenee ...jaldi
aaja


I am currently on holidays and will return to work on Tuesday 4th June.
Any urgent issues should be directed to Kieran Fitzpatrick.
Regards
Conor

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



oye chaal sutta peeneeeeee ...jaldi aaja

2002-05-29 Thread Amit Gandotra

oye chaal sutta peenee ...jaldi aaja


---
Amit Gandotra
Certified MQSeries Specialist
TechSpan India Ltd.
A-35, Sector#16,
Noida - 201301 (U.P.) India
Tel: - 00-120-4512710/11/12



-Original Message-
From: Navin Vali [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 10:21 AM
To: [EMAIL PROTECTED]
Subject: Re: JMS-JDBC-XA transaction coordianation


Hi Ferenc,

Sorry for the delayed reply, I really don't agree with replies you have got
till now.
You can have MQ Series Queue Manager Acting as a Transaction monitor to
control MQ Series resources as well as external resource managers (Some
Database DB2 in your case). I have successfully tried out this with DB2 , so
you need not actually need App server for this.
Any help req pls get in touch on [EMAIL PROTECTED]
 Regards
Navin

-Original Message-
From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 7:30 PM
To: [EMAIL PROTECTED]
Subject: Re: JMS-JDBC-XA transaction coordianation


Ferenc,

If you do not want to use WebSphere, you may use Weblogic instead :-).
Seriously, you will need some XA-capable JTA provider (Java library and
server). They are included in WebLogic and Websphere and some other
expensive application servers. I have not ever heard someone successfully
used the free ones but there is at least one (see http://tyrex.exolab.org/).
You will have to figure out how to configure MQ JMS to use its connection
factories (the documentation only explains how to do that with Websphere).

Again, I never tried that Tyrex myself.

Hope this will help
Pavel

 Message History



From:  Graham French <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on
05/29/2002 01:36 PM CET

Please respond to MQSeries List <[EMAIL PROTECTED]>

DELEGATED - Sent by:MQSeries [EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: JMS-JDBC-XA transaction coordianation



Configuring it is in the MQSeries Systems  Administration Guide, Chapter 14,
Transaction Support.
Coding  is in the MQSeries Application Programming Guide, Chapter 13,
Committing and  Backing out Units of Work

You  may have to use the Java MQ Classes rather than JMS if you're not using
an app  server, but I'll let someone else comment on that who knows more
about what  they're talking about!

Regards

Graham French
MQSolutions
+44 (0)7973 821288
mailto:[EMAIL PROTECTED]

-Original Message-
From: MQSeries List  [mailto:[EMAIL PROTECTED]]On Behalf Of Ferenc
Door
Sent: 29 May 2002 10:48
To:  [EMAIL PROTECTED]
Subject: JMS-JDBC-XA transaction  coordianation


Hi,

A question is : Are there any solution to  build an java application which
use globally coordinated transaction? I not  intend to use WebShere.
Where can I  find a good dokumentation which decribes: how should set up
MQSeries-DB2-Java  environment to gain access this feature?

Best regard, Ferenc  Door



--

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



MQSeries Connection Pooling

2002-05-29 Thread vinay_tiwari
Title: Performance of MQ Get/Put using MQCluter




  
  Hi ,
   
  I am using MQSimpleConnectionManager to create a 
  connection pool. But in some special cases I want all the alive 
  connections in the pool to be destroyed.
  As per the document by specifying MODE_INACTIVE 
  should work but it doesn't seems to be 
  working.
   
  Basically I want some qmgr.disconnect() kind of 
  operation on the connection pool created.
   
  Any help or pointers will be highly 
  appreciated.
   
  Thanks,
  Vinay
    
  MQSimpleConnectionManager myConnMan=new 
  MQSimpleConnectionManager(); 
  myConnMan.setActive(MQSimpleConnectionManager.MODE_AUTO); 
  myConnMan.setTimeout(360); 
  myConnMan.setHighThreshold(50); 
  MQEnvironment.setDefaultConnectionManager(myConnMan
   
   
   


Re: JMS-JDBC-XA transaction coordianation

2002-05-29 Thread Navin Vali

Hi Ferenc,

Sorry for the delayed reply, I really don't agree with replies you have got
till now.
You can have MQ Series Queue Manager Acting as a Transaction monitor to
control MQ Series resources as well as external resource managers (Some
Database DB2 in your case). I have successfully tried out this with DB2 , so
you need not actually need App server for this.
Any help req pls get in touch on [EMAIL PROTECTED]
 Regards
Navin

-Original Message-
From: Pavel Tolkachev [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 7:30 PM
To: [EMAIL PROTECTED]
Subject: Re: JMS-JDBC-XA transaction coordianation


Ferenc,

If you do not want to use WebSphere, you may use Weblogic instead :-).
Seriously, you will need some XA-capable JTA provider (Java library and
server). They are included in WebLogic and Websphere and some other
expensive application servers. I have not ever heard someone successfully
used the free ones but there is at least one (see http://tyrex.exolab.org/).
You will have to figure out how to configure MQ JMS to use its connection
factories (the documentation only explains how to do that with Websphere).

Again, I never tried that Tyrex myself.

Hope this will help
Pavel

 Message History



From:  Graham French <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on
05/29/2002 01:36 PM CET

Please respond to MQSeries List <[EMAIL PROTECTED]>

DELEGATED - Sent by:MQSeries [EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: JMS-JDBC-XA transaction coordianation



Configuring it is in the MQSeries Systems  Administration Guide, Chapter 14,
Transaction Support.
Coding  is in the MQSeries Application Programming Guide, Chapter 13,
Committing and  Backing out Units of Work

You  may have to use the Java MQ Classes rather than JMS if you're not using
an app  server, but I'll let someone else comment on that who knows more
about what  they're talking about!

Regards

Graham French
MQSolutions
+44 (0)7973 821288
mailto:[EMAIL PROTECTED]

-Original Message-
From: MQSeries List  [mailto:[EMAIL PROTECTED]]On Behalf Of Ferenc
Door
Sent: 29 May 2002 10:48
To:  [EMAIL PROTECTED]
Subject: JMS-JDBC-XA transaction  coordianation


Hi,

A question is : Are there any solution to  build an java application which
use globally coordinated transaction? I not  intend to use WebShere.
Where can I  find a good dokumentation which decribes: how should set up
MQSeries-DB2-Java  environment to gain access this feature?

Best regard, Ferenc  Door



--

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Weblogic 6.1 Message Driven Beans and MQSeries 5.2.1

2002-05-29 Thread vinay_tiwari

You will have to use MA88 pac provided by IBM to do the lookup for MQSeries queues.
Thanks,
Vinay

-Original Message-
From: mqm mqm [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 9:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Weblogic 6.1 Message Driven Beans and MQSeries 5.2.1


How are you guys invoking the MDBs to access MQ ? My
understanding is that in Weblogic 6.1 MDBs can only
access the Weblogic JMS queues and not foreign queues
like MQ so they have a bridge to copy MQ to their own
JMS queues.

Ned.

--- "Quigley, Robert" <[EMAIL PROTECTED]> wrote:
> Greetings,
> has anyone had problems managing the MDB hooks into
> a queue when they get
> deployed on an appServer?  I'm specifically looking
> for the way for the MDBs
> to gracefully terminate, similar to quiesce if
> failing logic on queue or
> message options.  Bigger concern is how they act if
> we need to recycle the
> qmanager.  Are people undeploying them altogether
> prior to a qmgr recycle?
> Any hints on administration appreciated.  Note:
> we're not using any
> MQ-specific api.  It's all j2ee spec at this point.
>
> Thanks,
> Rob
>
> Instructions for managing your mailing list
> subscription are provided in
> the Listserv General Users Guide available at
> http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive


__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Trigger Monitor - OS/390

2002-05-29 Thread Rao Krishna
Title: MQ and Cicsplex



Hi there,
I am using CKTIBAT2 trigger monitor in order trigger my 
application program.
CKTIBAT2 is running and it is submitting job when trigger happens to start my 
application program. But my
program is abending with reason code 2085 (wrong q 
name).
I would like to know in what format or using which trigger 
structure trigger monitor CKTIBAT2 passing trigger 
data
to my program.
I can able to display whole trigger data in my program and i can 
see my queue name displaying properly, but 
when i
refer using MQTMC-QNAME to open the queue, i can see first few 
character
missing. For example if my queue name
is ABC.LQ.001, i can see only Q.001 in the MQTMC-QNAME 
field.
 
Thanks in advance
RegardsRao 
 


Re: CUSTOMIZE SUPPORTPAC MA17 OS/390

2002-05-29 Thread Leung, Henry H
Title: CUSTOMIZE SUPPORTPAC MA17 OS/390



Voges,
 
The drawback of MA17 is only
one message is forwarded at one time.  It may be worthwhile
taking the effort to convert CSQ4TVH3 (from MA17)
into a batch program which forwards all messages in the DLQ back
to the original destination queue (MQDLH-DESTQNAME).
 
Regards
Henry

  -Original Message-From: Voges, P. (Pieter)
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, 30 May 2002 1:27
  AMTo: [EMAIL PROTECTED]Subject: CUSTOMIZE
  SUPPORTPAC MA17 OS/390
  Hi everyone. 
  I got some messages on a dead letter queue which I
  need to get back to the original queue quite urgently on MVS MQ 1.2

  The problem is that I first need to strip the DLQ
  header before taking it back. I searched through IBM's website and fount
  Supportpac MA17 which does all this. My Problem is that I am stuck now as the
  readme doc is not very clear. I would appreciate any help I can get from
  someone that installed and used this before.
  I downloaded the supportpac and created the 4
  datasets on MVS 
  MA17.CBS MA17.CLIST MA17.CSR MA17.ISPPENU 
  with all their members in. Step 5 in the readme doc
  says INSTALLATION. According to this the samples should be installed in the
  same way as those already supplied with the product. This is where I am stuck.
  What do I need to do from here. What should be copied where and what should be
  compiled where?
  Any help will be appreciated 
     Thank you 
  
Pieter
Voges MQ
Support     Tel: (011) 881 4410 Sel:  082 5790 790 E-mail: [EMAIL PROTECTED]
  
  http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter


Re: Problem receiving messages from a restarted client applicatio n.

2002-05-29 Thread Miller, Dennis

>Actually I don't see why the larger messages that cause this problem,
>should ever have been locked or need a back-out as the get would be failing
>on a 2080. When the client is not terminated and the surrogate can return
>the 2080, it does not prevent a new get from another client from getting
>the message.

You raise an interesting question. If a get under syncpoint fails, does the
candidate message become available to other processes immediately or is it
reserved until completion of the UOW.  (By "candidate", I mean whatever
message would be returned if the MQGET had been successful). In the case of
a RC=2080, at least, the MD gets filled out and you get part of the message
back, despite the failure. Since, it's common place to obtain a larger
buffer and try the read again, I expect MQ withholds that message from other
processes until it's "freed" by completion of the UOW. Honestly, this is
conjecture on my part, but it does explain part of the behavior you are
seeing.

Also, I am curious, is your client MQGET a browse or destructive?




> -Original Message-
> From: Richard Brunette [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 11:31 AM
> To:   [EMAIL PROTECTED]
> Subject:  Re: Problem receiving messages from a restarted client
> application.
>
> Pavel
>
> I'm not sure that I understand what your saying. From everything I've seen
> the syncpoint processing performs exactly as I would suspect and as
> documented in this usage note from the APR manual. Without syncpointing
> successful gets do lose the message when the 'surrogate' can't return
> them.
> And with syncpointing they are backed out and available for another
> program
> to browse or get.
>
>3. If the application issuing the  MQGET  call is running as an MQ
>   client, it is possible for the message retrieved to be lost if
> during
>   the processing of the  MQGET  call the MQ client terminates
>   abnormally or the client connection is severed. This arises because
>   the surrogate that is running on the queue-manager's platform and
>   which issues the  MQGET  call on the client's behalf cannot detect
>   the loss of the client until the surrogate is about to return the
>   message to the client; this is after the message has been removed
>   from the queue. This can occur for both persistent messages and
>   nonpersistent messages.
>
>
>   The risk of losing messages in this way can be eliminated by always
>   retrieving messages within units of work (that is, by specifying the
>   MQGMO_SYNCPOINT option on the  MQGET  call, and using the  MQCMIT
> or
>   MQBACK  calls to commit or back out the unit of work when processing
>   of the message is complete). If MQGMO_SYNCPOINT is specified, and
> the
>   client terminates abnormally or the connection is severed, the
>   surrogate backs out the unit of work on the queue manager and the
>   message is reinstated on the queue.
>
> I don't know that I've ever read anything to suggest that fully backed-out
> message would under any circumstances not be available to another client
> that was already waiting on a get (let alone an open). In fact if I use a
> smaller message in the test the already waiting client does get the
> message.
>
> Actually I don't see why the larger messages that cause this problem,
> should ever have been locked or need a back-out as the get would be
> failing
> on a 2080. When the client is not terminated and the surrogate can return
> the 2080, it does not prevent a new get from another client from getting
> the message. It appears as though there is nothing to trigger the queue
> manger to check for the any outstanding gets that may be satisfied by this
> message. A new get returns the message immediately. If the first client is
> successful but backs the message out, then the second client's surrogate
> is
> given the message. The same is true if the first client's surrogate does
> the back-out. Why should if be different if the first client's surrogate
> fails to take the message?
>
> Rick
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



cleanmqlogs QMGR recycling

2002-05-29 Thread Robert Broderick

With MQSeries 5.2 do you have to recycle the queue manager after doing a
rcdmqimg to run the cleanmqlogs. Someone indicated there was a quirk in MQ
pre-5.2 that required you to do this to make the END-OF-LOG messages get
generated.

 bobbee

_
Send and receive Hotmail on your mobile device: http://mobile.msn.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



AIX MQ 5.2: Client Mode Does not Work on the same node )

2002-05-29 Thread Jiede J Yang

All:

This is an urgent question.  Please reply ASAP.

On an AIX 4.3.3 node, we have installed MQ 5.2.  We can use C++ to bind to
MQ successfully and put message to it.  When we try to pull message from
Java we failed.

The way we try to communicate with the MQ from Java is through svrconn
channel.   Host name and channel are set properly.  However, the response
from MQ has been that host name unknown.

It sound like a tcp/ip problem, then we  used the same code and property
file from an NT node to communicate the AIX MQ manager, which works.   The
communication to the MQ manager also works another AIX box with same level
of OS and MQ.  Also ping on the same node for itself works.

Why client mode does not work on the same machine?

Thanks for your insight.

Jerry

626-524-2554 (Cell)

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Message ordering

2002-05-29 Thread Miller, Dennis

MQ does deliver messages in sequence, given certain conditions. The problem,
of course, is that the conditions are so restrictive that sequential
delivery is usually impractical. To make matters worse, some of the
restrictions involve network topology. The last thing you want to do is make
your application unnecesarily dependent on how the channels are configured,
the path a message might take, or other things that are subject to change
for operational or performance reasons.

The best practice for satisifying a sequential delivery requirement is to
provide for it in your application(s). You may be able to use logical
message groups or message chaining. Message chaining has has been discussed
before: send every message with a unique msgid and a correlid containing the
msgid preceeding it. You can then guarantee sequential retrieval by
qualifying the correlid on your mqget with the msgid of the prior message.
That may get "interesting" when feeding JMS from a non-JMS application
because of the way JMS manipulates the msgid, but I think it's still
do-able.

regards,
Dennis



> -Original Message-
> From: Jodl, Joe R [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 29, 2002 6:25 AM
> To:   [EMAIL PROTECTED]
> Subject:  Message ordering
>
> We have a application running in MVS that puts messages to a MQ remote
> queue name.  The application guarantees to put the messages in order.
> This remote queue puts the message to a xmit queue on a Sun Solaris box
> running MQ version 5.2
> My question is will the messages be guaranteed to be in order when they
> reach the UNIX box?
>
> Also once the messages are on the UNIX box they are read off by a JAVA
> application using JMS.
> Are there options with JMS to insure order?
>
> Thanks in advance 
> Joe
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: V5.2 or V5.3 (OS390 - MQ)

2002-05-29 Thread Ruud van Zundert

Dave - tricky decision, because you'll probably find people
have different 'agendas' :

- MQ V5.2 is stable - and 'safe'/known quantity amongst the MQ community.
  The end-of-service date is end 2003 so no rush there.
- MQ V5.3 is new (exciting?) and offers new functionality - like SSL on
channels
  amongst others. No software is bug-free but can you live with that?
  What time-scale are you working towards?

I would think that the effort to migrate to V5.2 is probably the same
as moving to V5.3.

Regards ... Ruud


-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Mauro,
Samuel
Sent: 29 May 2002 18:58
To: [EMAIL PROTECTED]
Subject: Re: V5.2 or V5.3 (OS390 - MQ)


FWIW, I went from V1.2 to V5.2 last year. There are toleration PTF's that
make it easy to 'flip-flop' between the prior release and new one if the
need arises. Basically all you have to do is change the MQ subsystem
libraries and batch jobs/tso procs that reference them. Besides applying the
maintenance, I don't remember it being difficult to migrate to the new
version. I'm not sure what V5.3 would do to that scenario. HTH.

Thanks. Sam.

Sam Mauro
Textron Information Services
Voice  (817) 280-3215
Fax(817) 278-3215
Pager  (817) 227-4063


-Original Message-
From: Williams, Dave (Systems Management) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:47 PM
To: [EMAIL PROTECTED]
Subject: V5.2 or V5.3 (OS390 - MQ)


We're one of those users still on MQ OS390 V1.2, but want to upgrade in the
next week or so. My question is, should I put in 5.2 or wait the few extra
weeks for 5.3. I'm not at all sure I want to be in the first cut of the new
release, but want to do
what makes the most sense. Any feedback from anyone?

Thanks,

Dave W.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Data Translation Problem

2002-05-29 Thread Robert Broderick

If this OS390. Have you put the program up in expeditor and verified that
the data going to the queue is what you think it is. Then have you verified
that the data on the queue looks like a '??' or not. I am assuming the data
is going out on a transmission queue to somewhere I was wondering if
translation is set on the channel or 'the receiver makes good'. I guess I'm
trying to figure out at what point the character gets
changed?

  bobbee


>From: Sergio Lima <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Data Translation Problem
>Date: Wed, 29 May 2002 15:01:12 -0300
>
>Hello.
>
>Os/390 2.10
>
>Sergio
>
>
>>From: Robert Broderick <[EMAIL PROTECTED]>
>>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>>Subject: Re: Data Translation Problem
>>Date: Wed, 29 May 2002 08:18:31 -0400
>>
>>Platform?
>>
>>
>>>From: Sergio Lima <[EMAIL PROTECTED]>
>>>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>>>To: [EMAIL PROTECTED]
>>>Subject: Data Translation Problem
>>>Date: Tue, 28 May 2002 19:11:30 -0300
>>>
>>>Hello.
>>>
>>>Here We have some application that get a record from DB2 database, and
>>>write
>>>on MQSeries queue.
>>>We don't understand, why the character g on DB2, was wrote to ?? on
>>>MQSeries
>>>queue .
>>>
>>>Anybody already saw this ?
>>>
>>>Thanks
>>>
>>>Sergio Lima Costa
>>>System Consultant
>>>Sao Paulo - Brasil
>>>
>>>
>>>_
>>>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>>>
>>>Instructions for managing your mailing list subscription are provided in
>>>the Listserv General Users Guide available at http://www.lsoft.com
>>>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>>
>>
>>_
>>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>>
>>Instructions for managing your mailing list subscription are provided in
>>the Listserv General Users Guide available at http://www.lsoft.com
>>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
>
>
>_
>MSN Photos is the easiest way to share and print your photos:
>http://photos.msn.com/support/worldwide.aspx
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive


_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Data Translation Problem

2002-05-29 Thread Robert Broderick

Was the Upper and Lower case feature installed with MQSeries by the System
people on the OS 390?


>From: Sergio Lima <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Data Translation Problem
>Date: Wed, 29 May 2002 15:01:12 -0300
>
>Hello.
>
>Os/390 2.10
>
>Sergio
>
>
>>From: Robert Broderick <[EMAIL PROTECTED]>
>>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>>Subject: Re: Data Translation Problem
>>Date: Wed, 29 May 2002 08:18:31 -0400
>>
>>Platform?
>>
>>
>>>From: Sergio Lima <[EMAIL PROTECTED]>
>>>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>>>To: [EMAIL PROTECTED]
>>>Subject: Data Translation Problem
>>>Date: Tue, 28 May 2002 19:11:30 -0300
>>>
>>>Hello.
>>>
>>>Here We have some application that get a record from DB2 database, and
>>>write
>>>on MQSeries queue.
>>>We don't understand, why the character g on DB2, was wrote to ?? on
>>>MQSeries
>>>queue .
>>>
>>>Anybody already saw this ?
>>>
>>>Thanks
>>>
>>>Sergio Lima Costa
>>>System Consultant
>>>Sao Paulo - Brasil
>>>
>>>
>>>_
>>>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>>>
>>>Instructions for managing your mailing list subscription are provided in
>>>the Listserv General Users Guide available at http://www.lsoft.com
>>>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>>
>>
>>_
>>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>>
>>Instructions for managing your mailing list subscription are provided in
>>the Listserv General Users Guide available at http://www.lsoft.com
>>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
>
>
>_
>MSN Photos is the easiest way to share and print your photos:
>http://photos.msn.com/support/worldwide.aspx
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive


_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Newbie: Urgent : Connectivity problem from NT client to Solar is Server

2002-05-29 Thread hegde

Hey,

It worked thank you man for your help. I used the mqm
user for testing, but I will change after reading
security stuff, Can you guide me what stuff I have to
read to implement the security.

Thanks Again.

Thanks
Prakash
--- "DiLauro, Nick" <[EMAIL PROTECTED]> wrote:
> 2035 is security.  NT differs in that the local
> userid of the client is
> passed to the qmgr on the server.  On the Solaris
> platform no userid is
> passed so the userid of the qmgr is used (because
> the SVRCONN channel has
> not been defined with an MCA userid).  You can
> authorize the NT userid or
> assign an MCA Userid to the SVRCONN channel and then
> give the userid
> authority to access the specific objects it needs.
> You could assign the mqm
> userid if you want the client to have full access,
> but this could be a
> security problem in a production environment.  If
> you're just testing, it
> might work until you come up with a security
> strategy.
>
> Nick
>
> -Original Message-
> From: hegde [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 28, 2002 10:27 PM
> To: [EMAIL PROTECTED]
> Subject: Newbie: Urgent : Connectivity problem from
> NT client to Solaris
> Server
>
>
> Hi All,
>
> I am new to the MQSeries. I have installed the
> MQSeries V5.2 Server on Solaris 8. I have created
> the
> queue as per Manuals Available on CD's. I am able to
> connect the queue from another unix client,  but I
> am
> not able queue from windows NT. I have configured as
> below.
>
> 1. I have created the Queue Manager as
> crtmqm -q saturn.queue.manager
> strmqm saturn.queue.manager
> 2.  define qlocal (ORANGE.LOCAL.QUEUE)
> 3.  define channel (CHANNEL1) +
> chltype (SVRCONN) +
> MCAUSER (' ') +
> TRPTYPE (TCP)
> 4.  I have modified the inetd and services file as
> per
> document.
> 5.  Started command Server  and started listner and
> channel (from runmqsc prompt)
> 6. On sun solaris I have set the environment as
> MQSERVER=CHANNEL1/TCP/'199.221.81.102'
>from solaris system I am able put the message as
>amqsputc ORANGE.LOCAL.QUEUE saturn.manager.queue
>and no problem in receive message using amqsgetc
> 7. On windows NT system I have set the MQSERVER
> environment as
> SET MQSERVER=CHANNEL1/TCP/199.221.81.102
> amqsputc ORANGE.LOCAL.QUEUE saturn.queue.manager
>
> I am getting MCONN ended the connection reason
> 2035
>
> I don't know what I am missing or doing wrong. I
> request some one to correct my mistake or guide me.
>
> I appreciate you help.
>
> Thanks
> Prakash
>
>
>
>
> __
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> Instructions for managing your mailing list
> subscription are provided in
> the Listserv General Users Guide available at
> http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
> Instructions for managing your mailing list
> subscription are provided in
> the Listserv General Users Guide available at
> http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive


__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



RC2111, AMQ6050 and AMQ6174???

2002-05-29 Thread Beinert, William

We went live with out first production app this morning, and the excrement
immediately hit the fan.
The GETting application failed with RC 2111, indicating a problem with the
CCSID conversion. (We are sending from MQ 2.1 in IMS V6 on OS/390 2.8 to MQ
5.2 on HPUX 11.0)  Data converion has worked flawlessly for us for over a
year in testing and training.

As we scrambled to investigate, we started sending messages from our IMS
training system, to see if there was a difference there. The bad messages
were still on the queue, so we couldn't tell if the new ones were OK till I
purged them. I ran a adapation of AMQSGET to drain the queue, and got 2111s
myself, along with
/usr/lib/dld.sl: Can't open shared library: /var/mqm/exits//MQSTR
/usr/lib/dld.sl: No such file or directory

I did manage to empty the queue, but found that messages from the training
system had the same 2111 problem. This configuration worked yesterday until
3 PM, when we stopped work to clean a database in the Unix production app in
prep for going live. And the production config worked perfectly last Wed
when we did a real run with 'ignore this' data.

None of the programs had changed on either the OS/390 or Unix platforms.

I shut down the Unix queue manager, and restarted it, and all was well!!!

I found no FDC files, but my error logs were full of errors like this,
starting YESTERDAY.
05/28/02  06:31:01
AMQ6050: CCSID error.

MQSeries is unable to convert string data in CCSID 500 to data in CCSID
1051.
Check the appropriate National Language Support publications to see if the
CCSIDs are supported by your system.

---
05/28/02  06:31:01
AMQ6174: The library /var/mqm/exits//MQSTR was not found. The queue manager
will continue without this module.

The dynamically loadable file /var/mqm/exits//MQSTR was not found.
Check that the file exists and is either fully qualified or is in the
appropriate directory.

---


Anybody have any clue as to what when wrong? A unix hiccup?

Bill

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Problem receiving messages from a restarted client application.

2002-05-29 Thread Richard Brunette

Pavel

I'm not sure that I understand what your saying. From everything I've seen
the syncpoint processing performs exactly as I would suspect and as
documented in this usage note from the APR manual. Without syncpointing
successful gets do lose the message when the 'surrogate' can't return them.
And with syncpointing they are backed out and available for another program
to browse or get.

   3. If the application issuing the  MQGET  call is running as an MQ
  client, it is possible for the message retrieved to be lost if during
  the processing of the  MQGET  call the MQ client terminates
  abnormally or the client connection is severed. This arises because
  the surrogate that is running on the queue-manager's platform and
  which issues the  MQGET  call on the client's behalf cannot detect
  the loss of the client until the surrogate is about to return the
  message to the client; this is after the message has been removed
  from the queue. This can occur for both persistent messages and
  nonpersistent messages.


  The risk of losing messages in this way can be eliminated by always
  retrieving messages within units of work (that is, by specifying the
  MQGMO_SYNCPOINT option on the  MQGET  call, and using the  MQCMIT  or
  MQBACK  calls to commit or back out the unit of work when processing
  of the message is complete). If MQGMO_SYNCPOINT is specified, and the
  client terminates abnormally or the connection is severed, the
  surrogate backs out the unit of work on the queue manager and the
  message is reinstated on the queue.

I don't know that I've ever read anything to suggest that fully backed-out
message would under any circumstances not be available to another client
that was already waiting on a get (let alone an open). In fact if I use a
smaller message in the test the already waiting client does get the
message.

Actually I don't see why the larger messages that cause this problem,
should ever have been locked or need a back-out as the get would be failing
on a 2080. When the client is not terminated and the surrogate can return
the 2080, it does not prevent a new get from another client from getting
the message. It appears as though there is nothing to trigger the queue
manger to check for the any outstanding gets that may be satisfied by this
message. A new get returns the message immediately. If the first client is
successful but backs the message out, then the second client's surrogate is
given the message. The same is true if the first client's surrogate does
the back-out. Why should if be different if the first client's surrogate
fails to take the message?

Rick
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Weblogic 6.1 Message Driven Beans and MQSeries 5.2.1

2002-05-29 Thread Chris A. Dahl

Hi Ned,

Weblogic 6.1 can access a third party JMS provider, just not within an XA
transaction (which is usually what one wants out of an MDB). To have MQ and
DB XA transactions, the "Messaging Bridge" must be used. Some of this
capability is enhanced for WLS version 7, but I haven't looked at it
extensively yet.

Regards,

Chris




  mqm mqm
 cc:
  Sent by: Subject: Re: Weblogic 6.1 Message 
Driven Beans and MQSeries 5.2.1
  MQSeries List
  


  05/29/02 11:01
  AM
  Please respond
  to MQSeries List





How are you guys invoking the MDBs to access MQ ? My
understanding is that in Weblogic 6.1 MDBs can only
access the Weblogic JMS queues and not foreign queues
like MQ so they have a bridge to copy MQ to their own
JMS queues.

Ned.

--- "Quigley, Robert" <[EMAIL PROTECTED]> wrote:
> Greetings,
> has anyone had problems managing the MDB hooks into
> a queue when they get
> deployed on an appServer?  I'm specifically looking
> for the way for the MDBs
> to gracefully terminate, similar to quiesce if
> failing logic on queue or
> message options.  Bigger concern is how they act if
> we need to recycle the
> qmanager.  Are people undeploying them altogether
> prior to a qmgr recycle?
> Any hints on administration appreciated.  Note:
> we're not using any
> MQ-specific api.  It's all j2ee spec at this point.
>
> Thanks,
> Rob
>
> Instructions for managing your mailing list
> subscription are provided in
> the Listserv General Users Guide available at
> http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive


__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Data Translation Problem

2002-05-29 Thread Sergio Lima

Hello.

Os/390 2.10

Sergio


>From: Robert Broderick <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Data Translation Problem
>Date: Wed, 29 May 2002 08:18:31 -0400
>
>Platform?
>
>
>>From: Sergio Lima <[EMAIL PROTECTED]>
>>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>>Subject: Data Translation Problem
>>Date: Tue, 28 May 2002 19:11:30 -0300
>>
>>Hello.
>>
>>Here We have some application that get a record from DB2 database, and
>>write
>>on MQSeries queue.
>>We don't understand, why the character g on DB2, was wrote to ?? on
>>MQSeries
>>queue .
>>
>>Anybody already saw this ?
>>
>>Thanks
>>
>>Sergio Lima Costa
>>System Consultant
>>Sao Paulo - Brasil
>>
>>
>>_
>>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>>
>>Instructions for managing your mailing list subscription are provided in
>>the Listserv General Users Guide available at http://www.lsoft.com
>>Archive: http://vm.akh-wien.ac.at/MQSeries.archive
>
>
>_
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive




_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: V5.2 or V5.3 (OS390 - MQ)

2002-05-29 Thread Mauro, Samuel

FWIW, I went from V1.2 to V5.2 last year. There are toleration PTF's that
make it easy to 'flip-flop' between the prior release and new one if the
need arises. Basically all you have to do is change the MQ subsystem
libraries and batch jobs/tso procs that reference them. Besides applying the
maintenance, I don't remember it being difficult to migrate to the new
version. I'm not sure what V5.3 would do to that scenario. HTH.

Thanks. Sam.

Sam Mauro
Textron Information Services
Voice  (817) 280-3215
Fax(817) 278-3215
Pager  (817) 227-4063


-Original Message-
From: Williams, Dave (Systems Management) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:47 PM
To: [EMAIL PROTECTED]
Subject: V5.2 or V5.3 (OS390 - MQ)


We're one of those users still on MQ OS390 V1.2, but want to upgrade in the
next week or so. My question is, should I put in 5.2 or wait the few extra
weeks for 5.3. I'm not at all sure I want to be in the first cut of the new
release, but want to do
what makes the most sense. Any feedback from anyone?

Thanks,

Dave W.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



V5.2 or V5.3 (OS390 - MQ)

2002-05-29 Thread Williams, Dave (Systems Management)

We're one of those users still on MQ OS390 V1.2, but want to upgrade in the next week 
or so. My question is, should I put in 5.2 or wait the few extra weeks for 5.3. I'm 
not at all sure I want to be in the first cut of the new release, but want to do
what makes the most sense. Any feedback from anyone?

Thanks,

Dave W.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Message ordering

2002-05-29 Thread Jodl, Joe R

Thanks for the info from everyone..

-Original Message-
From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 11:30 AM
To: [EMAIL PROTECTED]
Subject: Re: Message ordering


In addition to Phil's first sentence I would add that the messages that you
want to stay in order must all be persistent or all be non persistent, for
if you start mixing persistent attributes in your "group", you run the risk
of non persistent messages arriving on the other side before the persistent
ones, even if the non-persistent one got PUt after the persistent one.

Same thing goes for syncpoint / non syncpoint. Don't mix. In this case they
should all ARRIVE on the other side in order, but the syncpointed ones may
not be immediattly available, causing later messages put outside of
syncpoint to be available first on the other side, thus screwing up your
order.



The below is from the App Prog Referance Guide, Under Chapter 35...
Start
Quote###
###

If an application puts a sequence of messages on the same queue without
using message groups, the order of those messages is preserved provided that
the conditions detailed below are satisfied. Some conditions apply to both
local and remote destination queues; other conditions apply only to remote
destination queues.
Conditions for local and remote destination queues

All of the  MQPUT  calls are within the same unit of work, or none of them
is within a unit of work.
Be aware that when messages are put onto a particular queue within a single
unit of work, messages from other applications may be interspersed with the
sequence of messages on the queue.

All of the  MQPUT  calls are made using the same object handle Hobj.
In some environments, message sequence is also preserved when different
object handles are used, provided the calls are made from the same
application. The meaning of "same application" is determined by the
environment:

On Compaq (DIGITAL) OpenVMS, the application is the thread.
On DOS client, the application is the system.
On OS/390, the application is:
For CICS, the CICS task
For IMS, the task
For OS/390 batch, the task
On OS/2, the application is the thread.
On AS/400, the application is the job.
On Tandem NonStop Kernel, the application is the thread.
On UNIX systems, the application is the thread.
On VSE/ESA, the application is the CICS task.
On Windows client and Windows 3.1, the application is the process.
On Windows NT and Windows 95, Windows 98, the application is the thread.
The messages all have the same priority.


Additional conditions for remote destination queues

There is only one path from the sending queue manager to the destination
queue manager.
If there is a possibility that some messages in the sequence may go on a
different path (for example, because of reconfiguration, traffic balancing,
or path selection based on message size), the order of the messages at the
destination queue manager cannot be guaranteed.

Messages are not placed temporarily on dead-letter queues at the sending,
intermediate, or destination queue managers.
If one or more of the messages is put temporarily on a dead-letter queue
(for example, because a transmission queue or the destination queue is
temporarily full), the messages can arrive on the destination queue out of
sequence.

The messages are either all persistent or all nonpersistent.
If a channel on the route between the sending and destination queue managers
has its NonPersistentMsgSpeed attribute set to MQNPMS_FAST, nonpersistent
messages can jump ahead of persistent messages, resulting in the order of
persistent messages relative to nonpersistent messages not being preserved.
However, the order of persistent messages relative to each other, and of
nonpersistent messages relative to each other, is preserved.

End
Quote###
###


Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 11:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Message ordering


If there is only one sender using a FIFO queue, or a Priority queue where
all messages are the same priority, and all queue managers do NOT use Dead
Letter Queues, then yes the messages will be delivered in the same order.

However, if the message is taking multiple hops (the message passes through
multiple queue managers before arriving at its destination), then things
get more complicated.  If you consider contingency sites or you are using
MQClustering, then ordering becomes more complicated.  But in the simple
case where there's only two queue managers with the restrictions stated in
the first sentence above, then message will arrive in the order sent.   In
your case there's three qu

Re: MQ and AIX V5 on P690

2002-05-29 Thread Milton Weinberger

I believe it is.  I will be testing it in a few weeks.
Milt




"mqm mqm" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 05/29/2002 12:05:45 PM

Please respond to "MQSeries List" <[EMAIL PROTECTED]>

Sent by:"MQSeries List" <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:MQ and AIX V5 on P690


Anyone know if MQ is supported on AIX Version 5 on the
new IBM P690 machines.

Ned.

__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: MQSeries and Unicode

2002-05-29 Thread Chris Fryett

try using:
 MQMD md;
 memcpy (md.Format, MQFMT_STRING, MQ_FORMAT_LENGTH);

  This should help in the conversion which is automatic as long as either your
application uses MQGMO_CONVERT and/or the channels are flagged for conversion.

Regards,

Chris






mqm mqm <[EMAIL PROTECTED]> on 05/29/2002 11:35:37 AM

Please respond to MQSeries List <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Chris Fryett/LA/Candle)
Subject:  MQSeries and Unicode

Does MQ support UNICODE ?
We have a problem where we send messages to NT, where
the application puts the messages into a file. We do
MQGET with conversion on NT converting to an NT code
page. We can read the file in DOS but when an NT
application (that uses UNICODE) reads the file some
special characters (e.g. GBP, USD, tilde) are not
correct.
Any ideas on how to get round this ?

Ned.

__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: MQ and AIX V5 on P690

2002-05-29 Thread Chris Fryett

The current version of WMQ 5.2 works fine on the AIX 5.x Regatta 690 systems.  I
have ran several intense tests with little issues, but some of my colleagues
have had a situation with MQM and JVM fighting for the same shared memory
segment.  This was reported to IBM.

Regards,

Chris





mqm mqm <[EMAIL PROTECTED]> on 05/29/2002 11:05:45 AM

Please respond to MQSeries List <[EMAIL PROTECTED]>

To:   [EMAIL PROTECTED]
cc:(bcc: Chris Fryett/LA/Candle)
Subject:  MQ and AIX V5 on P690

Anyone know if MQ is supported on AIX Version 5 on the
new IBM P690 machines.

Ned.

__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



XML to MRM transformation

2002-05-29 Thread Belinda Edwards

Hello Everyone.

Has anyone tried to transform an input XML message into an output MRM
message where you do not know which element(s) will be sent upon input and
will have to create the output from the XML tag attributes?

i.e.  an input XML message contains
something

The OutputRoot.MRM.OutputMsg.??? must be set to InputRoot.XML.INPUT."XML
attr".

Is this possible?

Thanks in advance for the information.

Belinda

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



creating a cluster thru commands

2002-05-29 Thread Philip, Aby

Hi everyone,
Does anyone know how to create a cluster using the command line? I am using
Win 2000 and I am able to create a cluster using the MQExplorer but I would
like to know if there is any command which i can use on the command line. I
presume that the commands I use for creating the cluster in Win 2000 would
be the same for UNIX?

I tried looking at the manual and made two queue managers QM1 and QM2
repositories for the cluster (FIRST.CLUSTER) but once i did that i was not
able to see the cluster in MQExplorer. So I think that was because I did not
create the cluster. There is a step by step procedure in the manual for
cluster creation but it starts from making the queue managers as the
repositories for the cluster and then creating the channels for it but it
does not mention anything about creating a cluster.

Thanks for the help.
Kind Regards
Aby

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



MQSeries and Unicode

2002-05-29 Thread mqm mqm

Does MQ support UNICODE ?
We have a problem where we send messages to NT, where
the application puts the messages into a file. We do
MQGET with conversion on NT converting to an NT code
page. We can read the file in DOS but when an NT
application (that uses UNICODE) reads the file some
special characters (e.g. GBP, USD, tilde) are not
correct.
Any ideas on how to get round this ?

Ned.

__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Message ordering

2002-05-29 Thread Potkay, Peter M (PLC, IT)

In addition to Phil's first sentence I would add that the messages that you
want to stay in order must all be persistent or all be non persistent, for
if you start mixing persistent attributes in your "group", you run the risk
of non persistent messages arriving on the other side before the persistent
ones, even if the non-persistent one got PUt after the persistent one.

Same thing goes for syncpoint / non syncpoint. Don't mix. In this case they
should all ARRIVE on the other side in order, but the syncpointed ones may
not be immediattly available, causing later messages put outside of
syncpoint to be available first on the other side, thus screwing up your
order.



The below is from the App Prog Referance Guide, Under Chapter 35...
Start
Quote###
###

If an application puts a sequence of messages on the same queue without
using message groups, the order of those messages is preserved provided that
the conditions detailed below are satisfied. Some conditions apply to both
local and remote destination queues; other conditions apply only to remote
destination queues.
Conditions for local and remote destination queues

All of the  MQPUT  calls are within the same unit of work, or none of them
is within a unit of work.
Be aware that when messages are put onto a particular queue within a single
unit of work, messages from other applications may be interspersed with the
sequence of messages on the queue.

All of the  MQPUT  calls are made using the same object handle Hobj.
In some environments, message sequence is also preserved when different
object handles are used, provided the calls are made from the same
application. The meaning of "same application" is determined by the
environment:

On Compaq (DIGITAL) OpenVMS, the application is the thread.
On DOS client, the application is the system.
On OS/390, the application is:
For CICS, the CICS task
For IMS, the task
For OS/390 batch, the task
On OS/2, the application is the thread.
On AS/400, the application is the job.
On Tandem NonStop Kernel, the application is the thread.
On UNIX systems, the application is the thread.
On VSE/ESA, the application is the CICS task.
On Windows client and Windows 3.1, the application is the process.
On Windows NT and Windows 95, Windows 98, the application is the thread.
The messages all have the same priority.


Additional conditions for remote destination queues

There is only one path from the sending queue manager to the destination
queue manager.
If there is a possibility that some messages in the sequence may go on a
different path (for example, because of reconfiguration, traffic balancing,
or path selection based on message size), the order of the messages at the
destination queue manager cannot be guaranteed.

Messages are not placed temporarily on dead-letter queues at the sending,
intermediate, or destination queue managers.
If one or more of the messages is put temporarily on a dead-letter queue
(for example, because a transmission queue or the destination queue is
temporarily full), the messages can arrive on the destination queue out of
sequence.

The messages are either all persistent or all nonpersistent.
If a channel on the route between the sending and destination queue managers
has its NonPersistentMsgSpeed attribute set to MQNPMS_FAST, nonpersistent
messages can jump ahead of persistent messages, resulting in the order of
persistent messages relative to nonpersistent messages not being preserved.
However, the order of persistent messages relative to each other, and of
nonpersistent messages relative to each other, is preserved.

End
Quote###
###


Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 11:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Message ordering


If there is only one sender using a FIFO queue, or a Priority queue where
all messages are the same priority, and all queue managers do NOT use Dead
Letter Queues, then yes the messages will be delivered in the same order.

However, if the message is taking multiple hops (the message passes through
multiple queue managers before arriving at its destination), then things
get more complicated.  If you consider contingency sites or you are using
MQClustering, then ordering becomes more complicated.  But in the simple
case where there's only two queue managers with the restrictions stated in
the first sentence above, then message will arrive in the order sent.   In
your case there's three queue manager, again, as long as there are no
failover or contingency machines (where messages can get marooned), and MQ
Clusters are not used, and FIFO is used on all queues, then MQ should
deliver in sequence.  You must 

MQ and AIX V5 on P690

2002-05-29 Thread mqm mqm

Anyone know if MQ is supported on AIX Version 5 on the
new IBM P690 machines.

Ned.

__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Weblogic 6.1 Message Driven Beans and MQSeries 5.2.1

2002-05-29 Thread mqm mqm

How are you guys invoking the MDBs to access MQ ? My
understanding is that in Weblogic 6.1 MDBs can only
access the Weblogic JMS queues and not foreign queues
like MQ so they have a bridge to copy MQ to their own
JMS queues.

Ned.

--- "Quigley, Robert" <[EMAIL PROTECTED]> wrote:
> Greetings,
> has anyone had problems managing the MDB hooks into
> a queue when they get
> deployed on an appServer?  I'm specifically looking
> for the way for the MDBs
> to gracefully terminate, similar to quiesce if
> failing logic on queue or
> message options.  Bigger concern is how they act if
> we need to recycle the
> qmanager.  Are people undeploying them altogether
> prior to a qmgr recycle?
> Any hints on administration appreciated.  Note:
> we're not using any
> MQ-specific api.  It's all j2ee spec at this point.
>
> Thanks,
> Rob
>
> Instructions for managing your mailing list
> subscription are provided in
> the Listserv General Users Guide available at
> http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive


__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Newbie: Urgent : Connectivity problem from NT client to Solar is Server

2002-05-29 Thread DiLauro, Nick

2035 is security.  NT differs in that the local userid of the client is
passed to the qmgr on the server.  On the Solaris platform no userid is
passed so the userid of the qmgr is used (because the SVRCONN channel has
not been defined with an MCA userid).  You can authorize the NT userid or
assign an MCA Userid to the SVRCONN channel and then give the userid
authority to access the specific objects it needs.  You could assign the mqm
userid if you want the client to have full access, but this could be a
security problem in a production environment.  If you're just testing, it
might work until you come up with a security strategy.

Nick

-Original Message-
From: hegde [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 10:27 PM
To: [EMAIL PROTECTED]
Subject: Newbie: Urgent : Connectivity problem from NT client to Solaris
Server


Hi All,

I am new to the MQSeries. I have installed the
MQSeries V5.2 Server on Solaris 8. I have created the
queue as per Manuals Available on CD's. I am able to
connect the queue from another unix client,  but I am
not able queue from windows NT. I have configured as
below.

1. I have created the Queue Manager as
crtmqm -q saturn.queue.manager
strmqm saturn.queue.manager
2.  define qlocal (ORANGE.LOCAL.QUEUE)
3.  define channel (CHANNEL1) +
chltype (SVRCONN) +
MCAUSER (' ') +
TRPTYPE (TCP)
4.  I have modified the inetd and services file as per
document.
5.  Started command Server  and started listner and
channel (from runmqsc prompt)
6. On sun solaris I have set the environment as
MQSERVER=CHANNEL1/TCP/'199.221.81.102'
   from solaris system I am able put the message as
   amqsputc ORANGE.LOCAL.QUEUE saturn.manager.queue
   and no problem in receive message using amqsgetc
7. On windows NT system I have set the MQSERVER
environment as
SET MQSERVER=CHANNEL1/TCP/199.221.81.102
amqsputc ORANGE.LOCAL.QUEUE saturn.queue.manager

I am getting MCONN ended the connection reason
2035

I don't know what I am missing or doing wrong. I
request some one to correct my mistake or guide me.

I appreciate you help.

Thanks
Prakash




__
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



CUSTOMIZE SUPPORTPAC MA17 OS/390

2002-05-29 Thread Voges, P. (Pieter)
Title: CUSTOMIZE SUPPORTPAC MA17  OS/390 





Hi everyone.


I got some messages on a dead letter queue which I need to get back to the original queue quite urgently on MVS MQ 1.2


The problem is that I first need to strip the DLQ header before taking it back. I searched through IBM's website and fount Supportpac MA17 which does all this. My Problem is that I am stuck now as the readme doc is not very clear. I would appreciate any help I can get from someone that installed and used this before.

I downloaded the supportpac and created the 4 datasets on MVS


MA17.CBS
MA17.CLIST
MA17.CSR
MA17.ISPPENU


with all their members in. Step 5 in the readme doc says INSTALLATION. According to this the samples should be installed in the same way as those already supplied with the product. This is where I am stuck. What do I need to do from here. What should be copied where and what should be compiled where?

Any help will be appreciated 


   Thank you 


Pieter Voges
MQ Support
    
Tel: (011) 881 4410
Sel:  082 5790 790
E-mail: [EMAIL PROTECTED] 

http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter







Re: Message ordering

2002-05-29 Thread philip . distefano

If there is only one sender using a FIFO queue, or a Priority queue where
all messages are the same priority, and all queue managers do NOT use Dead
Letter Queues, then yes the messages will be delivered in the same order.

However, if the message is taking multiple hops (the message passes through
multiple queue managers before arriving at its destination), then things
get more complicated.  If you consider contingency sites or you are using
MQClustering, then ordering becomes more complicated.  But in the simple
case where there's only two queue managers with the restrictions stated in
the first sentence above, then message will arrive in the order sent.   In
your case there's three queue manager, again, as long as there are no
failover or contingency machines (where messages can get marooned), and MQ
Clusters are not used, and FIFO is used on all queues, then MQ should
deliver in sequence.  You must also be mindful of multiple channel
definitions where two or more channels can, alternately, send messages from
the same transmit queue.  If one channel goes indoubt, and the second
channel starts sending ordering will not be achieved.






  scottj2512@YAHOO To:  [EMAIL PROTECTED]
  .COM cc:
  Sent by: Subject: Re: Message ordering
  MQSERIES@akh-wie
  n.ac.at


  05/29/2002 10:08
  AM
  Please respond
  to MQSERIES





 --- "Jodl, Joe R" <[EMAIL PROTECTED]> wrote: > We have
a application running in MVS that puts
> messages to a MQ remote queue name.  The application
> guarantees to put the messages in order.   This
> remote queue puts the message to a xmit queue on a
> Sun Solaris box running MQ version 5.2
> My question is will the messages be guaranteed to be
> in order when they reach the UNIX box?

There are several threads on this list server that
talk about message ordering and several solutions.
Have a look at http://www.messageq.com under forums
for the list server archive.

Regards
John.

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Message ordering

2002-05-29 Thread Robert Broderick

NOPE!! Unless you use a MQSeries feature called Grouping. Read up on it
in the Application Prog Ref Manual. This will allow you to put messages in
order.

There are circumstances where MQ sez the order will be preserved. BUT
IBM does not guarentee it. UNLESS.

   bobbee


>From: "Jodl, Joe R" <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Message ordering
>Date: Wed, 29 May 2002 08:25:11 -0500
>
>We have a application running in MVS that puts messages to a MQ remote
>queue name.  The application guarantees to put the messages in order.
>This remote queue puts the message to a xmit queue on a Sun Solaris box
>running MQ version 5.2
>My question is will the messages be guaranteed to be in order when they
>reach the UNIX box?
>
>Also once the messages are on the UNIX box they are read off by a JAVA
>application using JMS.
>Are there options with JMS to insure order?
>
>Thanks in advance 
>Joe
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive


_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: Problem receiving messages from a restarted client application.

2002-05-29 Thread Richard Brunette

Mike

The queue manager is a 5.2 OS/390 queue manager. The application receiving
the messages is on a Windows NT box. I've replicated the problem with the
5.1 and 5.2 clients (Java and native). Since I believe everything
unexplained is happening on the queue manager side, I doubt the client or
programming language would be an issue.

In order to get this to happen I need to put a large enough message to
force a truncation error on that abandoned agent. This is why I mentioned
concern for Java and JMS applications in particular. I often see our Java
developers using the standard get methods that don't specify length and I
seldom see applications that are passing less than 4096, so 2080s are a
common thing in Java and JMS (even if you have to turn on the trace to know
that they are happening). And for JMS I don't even know if there is a
method to receive a message specifying length.

Anyway I have replicated the problem in C as well, if I use a small message
buffer. I believe that good program design will keep most developers out of
this situation. However there are going to be long running application that
are not triggered and with more frequency these are Java  clients that
experience the internal 2080 error. Add with the reality that some of them
might occasionally be ended abnormally (maybe that doesn't happen in other
shops) , and you could have this problem.

Rick

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



COBOL RFH2 Help

2002-05-29 Thread Dave Kazatsky

Hi all,

Hoping can someone has done this in the past.

We are trying to create a message with a RFH2 header on MVS and send to
AIX.  The RFH2 is continually causing the message to fail.  We are using
the delivered copybook and adding NameValueLength and NameValueData to the
copybook and then setting the "mcd" folder.  It seems like the parser is
reading the 1208 NameValueCCSID value as the NameValueLength.

Has anyone successfully done this?

Any help appreciated.

Thanks,

Dave Kazatsky
Senior Middleware Administrator
Metlife

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Monitor MQ channels

2002-05-29 Thread Giuseppe Costagliola



Hi.
 
Currently we run MQseries V5R2 on our 
as/400 connected to Sanpaolo Bank and and Banco di Napoli (both 
with 0s/390). 
 
As/400 every morning starts a batch 
stand-alone monitor that recusively checks the status of critical lines, 
devices, jobs, etc. Among these devices we 
have to monitor the mq manager status, the rcvr and sdr channels and the trigger 
jobs. 
 
With previous version of MQ (4) we checked the 
status of jobs defined into the sync file AMQRSYNA and this was enough to signal 
any failure with channels.  
 
Is there another way now to get the channel status 
(like with WRKMQMCHST) for both sdr and rcvr ? Note that monitor runs unattended 
so there is no operator that can run any WRKMQ* 
command.  
 
Thanks.
 
Giuseppe Costagliola
SanPaoloIMI SGR
Turin - Italy
 
 


Re: Problem receiving messages from a restarted client application.

2002-05-29 Thread Pavel Tolkachev

Richard:

Client's transactional contract is restricted by MQI resources, according the 
"Clients" book. I am not sure if MQSeries globally coordinates two transactions 
(client->channel agent and channel agent->queue manager) at all. If by the time the 
message gets unlocked on qm, the application already has its queue open, it might 
never get it. IMHO of course.

Hope this helps,
Pavel

 Message History 



From:  Michael F Murphy/AZ/US/MQSolutions <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 
05/28/2002 07:44 PM MST

Please respond to MQSeries List <[EMAIL PROTECTED]>

DELEGATED - Sent by:MQSeries [EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: Problem receiving messages from a restarted client  
application.



I have seen similar situations.  The queue manager agent didn't see the client 
application go away so it is still ready to deliver a message to that application. 
 The queue manager agent gets the message from the queue and attempts to deliver it to 
the application which no longer exists.  Then it realizes the application is no longer 
there and since no mqdisc is called, it rolls it back.  If you have yet another 
instance of the application running OK, it should deliver the message to that 
application.  It is a good thing you are getting in syncpoint because otherwise this 
message would go to the bit bucket.  This can occur on other languages besides Java. 
 What is strange is you say the other application is already running  but never gets 
the message.  Since you can browse it, the message is not under syncpoint anymore so I 
can't explain that.  What platform is this anyway? AIX?

Mike Murphy
Sr. Middleware Consultant
MQ Solutions, LLC
http://www.mqsolutions.com



Richard Brunette <[EMAIL PROTECTED]> wrote:
   
   
   
   
   
   
   
   
   
 
   Date Recieved:  
   
   05/28/2002 09:43:31 AM  
   
   
   
   
   
   
 
   
   
   
   
   
   
   
   
   
 
   To: 
   
   [EMAIL PROTECTED] 
   
   
   
   

Re: Message ordering

2002-05-29 Thread John Scott

 --- "Jodl, Joe R" <[EMAIL PROTECTED]> wrote: > We have
a application running in MVS that puts
> messages to a MQ remote queue name.  The application
> guarantees to put the messages in order.   This
> remote queue puts the message to a xmit queue on a
> Sun Solaris box running MQ version 5.2
> My question is will the messages be guaranteed to be
> in order when they reach the UNIX box?

There are several threads on this list server that
talk about message ordering and several solutions.
Have a look at http://www.messageq.com under forums
for the list server archive.

Regards
John.

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: JMS-JDBC-XA transaction coordianation

2002-05-29 Thread Pavel Tolkachev

Ferenc,

If you do not want to use WebSphere, you may use Weblogic instead :-). Seriously, you 
will need some XA-capable JTA provider (Java library and server). They are included in 
WebLogic and Websphere and some other expensive application servers. I have not ever 
heard someone successfully used the free ones but there is at least one (see 
http://tyrex.exolab.org/). You will have to figure out how to configure MQ JMS to use 
its connection factories (the documentation only explains how to do that with 
Websphere).

Again, I never tried that Tyrex myself.

Hope this will help
Pavel

 Message History 



From:  Graham French <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 05/29/2002 
01:36 PM CET

Please respond to MQSeries List <[EMAIL PROTECTED]>

DELEGATED - Sent by:MQSeries [EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: JMS-JDBC-XA transaction coordianation



Configuring it is in the MQSeries Systems  Administration Guide, Chapter 14, 
Transaction Support.
Coding  is in the MQSeries Application Programming Guide, Chapter 13, Committing and  
Backing out Units of Work

You  may have to use the Java MQ Classes rather than JMS if you're not using an app  
server, but I'll let someone else comment on that who knows more about what  they're 
talking about!

Regards

Graham French
MQSolutions
+44 (0)7973 821288
mailto:[EMAIL PROTECTED]

-Original Message-
From: MQSeries List  [mailto:[EMAIL PROTECTED]]On Behalf Of Ferenc  Door
Sent: 29 May 2002 10:48
To:  [EMAIL PROTECTED]
Subject: JMS-JDBC-XA transaction  coordianation


Hi,

A question is : Are there any solution to  build an java application which use 
globally coordinated transaction? I not  intend to use WebShere.
Where can I  find a good dokumentation which decribes: how should set up 
MQSeries-DB2-Java  environment to gain access this feature?

Best regard, Ferenc  Door



--

This e-mail may contain confidential and/or privileged information. If you are not the 
intended recipient (or have received this e-mail in error) please notify the sender 
immediately and destroy this e-mail. Any unauthorized copying, disclosure or 
distribution of the material in this e-mail is strictly forbidden.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Message ordering

2002-05-29 Thread Jodl, Joe R

We have a application running in MVS that puts messages to a MQ remote queue name.  
The application guarantees to put the messages in order.   This remote queue puts the 
message to a xmit queue on a Sun Solaris box running MQ version 5.2 
My question is will the messages be guaranteed to be in order when they reach the UNIX 
box?

Also once the messages are on the UNIX box they are read off by a JAVA application 
using JMS.
Are there options with JMS to insure order?

Thanks in advance 
Joe 

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: JMS-JDBC-XA transaction coordianation

2002-05-29 Thread Graham French



Configuring it is in the MQSeries Systems 
Administration Guide, Chapter 14, Transaction Support.
Coding 
is in the MQSeries Application Programming Guide, Chapter 13, Committing and 
Backing out Units of Work
 
You 
may have to use the Java MQ Classes rather than JMS if you're not using an app 
server, but I'll let someone else comment on that who knows more about what 
they're talking about!
 
Regards
Graham FrenchMQSolutions+44 (0)7973 821288mailto:[EMAIL PROTECTED]  


  -Original Message-From: MQSeries List 
  [mailto:[EMAIL PROTECTED]]On Behalf Of Ferenc 
  DoorSent: 29 May 2002 10:48To: 
  [EMAIL PROTECTED]Subject: JMS-JDBC-XA transaction 
  coordianationHi, 
  A question is : Are there any solution to 
  build an java application which use globally coordinated transaction? I not 
  intend to use WebShere. Where can I 
  find a good dokumentation which decribes: how should set up MQSeries-DB2-Java 
  environment to gain access this feature?   Best regard, Ferenc 
  Door


Re: Data Translation Problem

2002-05-29 Thread Robert Broderick

Platform?


>From: Sergio Lima <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Data Translation Problem
>Date: Tue, 28 May 2002 19:11:30 -0300
>
>Hello.
>
>Here We have some application that get a record from DB2 database, and
>write
>on MQSeries queue.
>We don't understand, why the character g on DB2, was wrote to ?? on
>MQSeries
>queue .
>
>Anybody already saw this ?
>
>Thanks
>
>Sergio Lima Costa
>System Consultant
>Sao Paulo - Brasil
>
>
>_
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>Instructions for managing your mailing list subscription are provided in
>the Listserv General Users Guide available at http://www.lsoft.com
>Archive: http://vm.akh-wien.ac.at/MQSeries.archive


_
Chat with friends online, try MSN Messenger: http://messenger.msn.com

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: commit

2002-05-29 Thread Potkay, Peter M (PLC, IT)

You can do 2 separate commits, or link your batch app with the stub CSQBRSTB
or CSQBRSSI instead of CSQBSTUB. These 2 other stubs allow you take
advantage of RRS (Recoverable Resource Manager Services) on OS/390, which
will allow you to commit both with one call.

Do a search for these stubs in the Application Programming Guide
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/csqzal05/csqzal05
tfrm.htm to see which one suits your needs better. There are JCl and/or
Application code changes required if you switch the stub, so read the manual
first.


Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906


-Original Message-
From: N Vinodh [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:30 AM
To: [EMAIL PROTECTED]
Subject: commit


hi all

 If I have a batch COBOL program that writes to both MQSeries queues and
DB2 tables, then should I give 2 seperate commits (MQseries commit and DB2
commit) for both these resources to get committed? If this is not the
correct strategy what needs to be done?

can any one help me in this?

thanx in advance

rgds
vinodh



This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



AW: Communication about cluster boundaries

2002-05-29 Thread Springer, Henry

Hello Ruud,

We test more scenarios and all work fine.
The procedure, you sent, is similar to the version (a), we tested.
In our environment, the cluster repositories for both cluster are the
gateway server (two in a MSCS Cluster environment).
We changed the cmd-files and set up both systems: 
*   one with separate cluster repositories on dedicated server and a
member-queuemanager as a gateway
*   second with a shared full repository on the gateway server

Both working fine, if we set the definitions of the qalias
DEFBIND(NOTFIXED). And this is the really tricky part. If you define
defbind(open), you get an reason=2082 on the gateway server, otherwise the
queuemanager send the message the correct way out.

Conclusion: Allways use DEFBIND(NOTFIXED) on shared queues in a cluster, if
they are used from a client/server outside the cluster.


Henry Springer
MQSeries Familie
K-DOI-23

Volkswagen AG
Brieffach 1891
38436 Wolfsburg

Telefon +49-53 61-92 97 74
Telefax +49-53 61-92 28 13
eFax +49-5361-95 72 97 74
http://www.volkswagen.de


-Ursprüngliche Nachricht-
Von:Ruud van Zundert [mailto:[EMAIL PROTECTED]]
Gesendet am:Dienstag, 28. Mai 2002 16:21
An: [EMAIL PROTECTED]
Betreff:Re: Communication about cluster boundaries

 << Datei: overlap.txt >> All - just had loads of notifications from various
company's socalled 'anti-virus' programs.
My attached called overlap.cmd was rejected.
I have, therefore, renamed it to overlap.txt.

Regards ... Ruud

-Original Message-
From: Ruud van Zundert [mailto:[EMAIL PROTECTED]]
Sent: 28 May 2002 14:17
To: MQSeries List
Subject: RE: Communication about cluster boundaries


Henry - it's a bit tricky to get this to work, and if you
follow this procedure, you should be ok:

I've attached an example script that you can run on a Win2000 machine.
It is re-runnable. This is what it does (run via 'overlap.cmd') :

1. define 4 qmgrs QMT1, QMT2, QMT2B and QMGW.
   QMT1 holds the full repository for cluster CL001.
   QMT2 holds the full repository for cluster CL002.
   QMT2B holds a partial repository for cluster CL002.
   QMGW is the 'gateway' linking the 2 clusters together.
2. Cluster queue QMT2.CQ is defined on both QMT2 and QMT2B.
3. A 'bridge' queue called BRIDGE is defined on the gateway
   as a QALIAS - it resides in cluster CL001, but points to
   target queue QMT2.CQ in cluster CL002.
4. To test: amqsput BRIDGE QMT1
   Result : messages 'should' ;-) arrive on QMT2.CQ spread
   across qmgrs QMT2 and QMT2B.

Let us know how you get on.

Regards ... Ruud

-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of
Springer, Henry
Sent: 28 May 2002 11:22
To: [EMAIL PROTECTED]
Subject: Communication about cluster boundaries


Hello all,

we want to know, how to communicate about MQSeries Cluster boundaries.
Because of firewall restrictions we had to build two overlapping cluster and
the need to communicate between two nodes in both cluster. We want to use
workload balancing, the queues reside on several cloned machines in both
cluster.

A small and simple scenario:

QM1  belongs to  Cluster1  and share a local Queue  Q.TEST.ORIG  in his
cluster
QM2  belongs to  Cluster2  want to put a message to Q.TEST.ORIG.
QMR  belongs to  Cluster1,Cluster2  and should act as a MQ-Gateway

We do some tests and no one work properly:
a)  Define QALIAS  Q.TEST  on QMR  shared in Cluster1, Cluster2 and
point to Q.TEST.ORIG in the Cluster1
Result:  Reason 2082 on QMR
b)  Define QREMOTE  Q.TEST.1  on QMR  shared in Cluster2, point to
Q.TEST.ORIG (without naming a remote QMGR)
Result:  Reason: 2087 on QMR

Defining a QREMOTE on QMR  shared in Cluster2 and point to Q.TEST.ORIG on
QM1, QM2 can send messages to the Q, but this is a lost of the workload
balancing feature of the cluster.



Henry Springer
MQSeries Familie
K-DOI-23

Volkswagen AG
Brieffach 1891
38436 Wolfsburg

Telefon +49-53 61-92 97 74
Telefax +49-53 61-92 28 13
eFax +49-5361-95 72 97 74
http://www.volkswagen.de

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



JMS-JDBC-XA transaction coordianation

2002-05-29 Thread Ferenc Door

Hi,

A question is : Are there any solution to build an java application which use globally coordinated transaction? I not intend to use WebShere.
Where can I find a good dokumentation which decribes: how should set up MQSeries-DB2-Java environment to gain access this feature?
 
Best regard, Ferenc Door

Open Beta program for IBM WebSphere MQ V5.3 for Distributed Platforms

2002-05-29 Thread Jeff Hooper

The Global Product Introduction Centre (PIC) at Hursley Park, UK and the
WebSphere Development Beta Team based in Austin, Texas, USA jointly
announces an Open Beta program for IBM WebSphere MQ V5.3 for Distributed
Platforms (AIX, Sun Solaris and Microsoft Windows NT or 2000).

WebSphere MQ, V5.3 brings new performance levels, enhanced security, and
added features to enhance cross-platform consistency (harmonization).

   Comprehensive security options with SSL support
   JMS support integrated into the product
   Product flexibility increased by the API crossing exit
   Performance and scalability are enhanced for:
  Message Queuing Interface (MQI)
  JMS with publish/subscribe users
   Support for Windows XP and Linux on zSeries added
   Enhanced functions allow easier system management of MQ clusters
   Other added features harmonize the zSeries and distributed platform
   products

More details are available in Announcement Letter 202-074 (available at
http://www.ibmlink.ibm.com/usalets&parms=H_202-074)

What is included in the Beta program?

The Beta program allows participants to gain early experience with the new
features included in WebSphere MQ V5.3, prior to General Availability, on
the following platforms:

   AIX
   Sun Solaris
   Microsoft Windows NT 4
   Microsoft Windows 2000
Note: Microsoft Windows XP is NOT supported with this release.

Copies of the full set of product manuals (including those for WebSphere MQ
for z/OS V5.3) are available for separate download.

The Beta code is provided without charge but will expire on 31st July 2002.
It is available at http://www.ibm.com/software/mqseries/beta

No formal support is provided and it should not be used in a production
environment.

Jeff Hooper
WebSphere MQ Early Support Programmes
Advanced Technical Support -  Product Introduction Centre
MP135, HursleyPark, Winchester
Jeff Hooper/UK/IBM  |  jhooper at ibmgb  |  [EMAIL PROTECTED]

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Re: MQSeries PUB/SUB

2002-05-29 Thread Andrew Hickson

Stephen,
I'd prefer it if you would correct the problem with the DCE mismatch first.
If the problem persists once this is fixed then please send me the FDC.

Are you dependant upon the MQ DCE threads support ? If you're not using DCE
threads support (e.g. if you simply installed everything (including DCE
support) without considering the consequences) then you'd likely see a
significant performance improvement by removing the MQ DCE support.  Of
course if this is not a new installation then you'll need to consider the
implications of this change. If you are using DCE threads then you'll need
to install the version of the broker which also uses DCE threads.

Andy.

Stephen Cook <[EMAIL PROTECTED]>@AKH-WIEN.AC.AT> on 28/05/2002 22:13:13

Please respond to MQSeries List <[EMAIL PROTECTED]>

Sent by:MQSeries List <[EMAIL PROTECTED]>


To:[EMAIL PROTECTED]
cc:
Subject:Re: MQSeries PUB/SUB



strmqbrk does not match the queue manager in this respect - strmqbrk does
not
link to strmqbrk_d but endmqm does link to endmqm_d.  Each attempt to start
the
broker does produce an FDC.  Should I send the FDC?  Thanks.

Andrew Hickson wrote:

> Are you running draft 4 or draft 11 threads, does your broker match your
> queue manager in this respect ? (e.g does strmqbrk link to strmqbrk_d,
does
> endmqm link to endmqm_d). Note that HP performance is MUCH improved when
> running draft 11 threads.
>
> Were any FDC's produced ? If not then it is likely that a trace will be
> required to understand what's going on. If you'd like to send me a trace
> then I'll have a look, but I probably won't get to it until Thursday at
the
> earliest.
>
> Andy.
>
> Stephen Cook <[EMAIL PROTECTED]>@AKH-WIEN.AC.AT> on 28/05/2002 18:17:26
>
> Please respond to MQSeries List <[EMAIL PROTECTED]>
>
> Sent by:MQSeries List <[EMAIL PROTECTED]>
>
> To:[EMAIL PROTECTED]
> cc:
> Subject:MQSeries PUB/SUB
>
> All,
>
> We are trying to setup an MQSeries PUB/SUB environment
> on HP-UX v.11 running MQ 5.2 with CSD04.  We've
> installed SupportPacs - MA0C (MQSeries -
> Publish/Subscribe) and MA0F (MQSeries Application
> Messaging Interface).  We seem to have a problem after
> we've created and started a QMGR and we attempt to
> start the broker (strmqbrk -m QMgrName).  We receive
> the message - 'MQSeries message broker for queue
> manager PUBSUB not active.'  The QMGR error logs
> contains the following error - "An attempt has been
> made to run the MQSeries message broker (PUBSUB) but
> the broker has ended for reason '5800: (Unexpected
> Error)'."  Thanks for any help that can be provided.
>
> Instructions for managing your mailing list subscription are provided in
> the Listserv General Users Guide available at http://www.lsoft.com
> Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive