Re: AMI

[Govender Magendran]

Title: RE: AMI





Hi Heinz


Thanks for the info, this helps alot.


Magendran Govender



-Original Message-
From: Heinz Klein [mailto:[EMAIL PROTECTED]]
Sent: 02 August 2004 06:45
To: [EMAIL PROTECTED]
Subject: Re: AMI



Hello.


The text below can be found in the AMI support pack (MA0F) page. Based on that
and on another reply I had from Hursley we are recommending our customers to
move away from the AMI.


Heinz Klein


OLTP Tecnologia & Solucoes Ltda.
Sao Paulo/SP - Brasil


-


After June 2003, IBM has no plans to enhance the AMI with any new functions or
platforms. IBM will however continue to support the AMI as described in the
Technical Support sectioin below.


We would recommend that customers do not use the AMI for any new projects and do
not extend usage in existing projects. This recommendation does not apply to
functions shipped by other IBM products, such as DB2, that have made use of the
AMI. IBM is working to ensure that these products are able to provide the same
functionality as today without the AMI.


Govender Magendran wrote:
> Hi all
>
> Can anybody tell me if AMI is still supported by IBM ? Last I heard that
> IBM have stopped development on it (therefore no new releases or CSDs)
> or have I heard wrong.
>
> And would it be a good decision to go the AMI route due to all the
> benefits it provides ?
> Are there any pitfalls if AMI was used ?
>
> Your input would invaluable.
>
> Thanks, in advance.
>
> Magendran Govender
>
> Please click on the following link to read the Old Mutual legal notice:
> <http://www.oldmutual.co.za/e-mail_legal_notice>
> Alternatively, send a "blank" e-mail to
> <mailto:[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



Please click on the following link to read the Old 
Mutual legal notice: <http://www.oldmutual.co.za/e-mail_legal_notice> 
Alternatively, send a "blank" e-mail to <mailto:[EMAIL PROTECTED]> 

 

Re: AMI

[Govender Magendran]

Title: RE: AMI





Hi all


Can anybody tell me if AMI is still supported by IBM ? Last I heard that IBM have stopped development on it (therefore no new releases or CSDs) or have I heard wrong.

And would it be a good decision to go the AMI route due to all the benefits it provides ?
Are there any pitfalls if AMI was used ?


Your input would invaluable.


Thanks, in advance.


Magendran Govender



Please click on the following link to read the Old 
Mutual legal notice:  
Alternatively, send a "blank" e-mail to  

 

Re: XML encoding="ibm-437"

[Govender Magendran]

Title: XML encoding="ibm-437"



Hi
 
I am
not sure how you would do it in the MRM Domain.
 
But
before you output to the queue, you can reset to XML Domain and
use
SET
OutputRoot.XML.(XML.XmlDecl).(XML.Encoding) = 'UTF-8';
 
Hope
this helps.
 
Regards
Magendran Govender 

  -Original Message-From: van Zyl, Andre
  [mailto:[EMAIL PROTECTED]Sent: 25 May 2004
  03:21To: [EMAIL PROTECTED]Subject: XML
  encoding="ibm-437"Importance: High
  Hi, 
  I have an XML DTD which I imported into WMQ
  (version 2.1) and created a message type for it in MRM and I am using this to
  generate an XML output message.
  It works well, except for the fact that it somehow
  defaults to encoding="ibm-437". How do I change this to encoding="UTF-8"??
  
  I checked in the "working with messages" manual,
  but could not find any details on this. 
  Thanks 
  Andre van Zyl 
  =
  
  Disclaimer 
  This message may contain information which is
  private, privileged or confidential and is intended solely for the use of the
  individual or entity named in the message. If you are not the intended
  recipient of this message, please notify the sender thereof and destroy /
  delete the message. Neither the sender nor Sappi Limited (including its
  subsidiaries and associated companies) shall incur any liability resulting
  directly or indirectly from accessing any of the attached files which may
  contain a virus or the like.
  Director Names 
   A list of Sappi companies and the names of
  their directors can be retrieved from http://www.sappi.com/home.asp?pid=644
  =
  
Please click on the following link to read the Old
Mutual legal notice: 
Alternatively, send a "blank" e-mail to 

 

Re: MQSI - How to add attributes to input XML

[Govender Magendran]

Hi Sebastian
 
I tried the ESQL as is and it produced the
following results :
 fred
I cannot explain how your flow has produced
the following results :




  fred

 
This XML is not well formed. Are you using
MRM or XML Domain as a parser ?
 
Regards
Magendran Govender 

  -Original Message-From: Daniel Graper
  [mailto:[EMAIL PROTECTED]Sent: 19 April 2004 02:59To:
  [EMAIL PROTECTED]Subject: Re: MQSI - How to add attributes to
  input XML
  Magendran:
  I appreciate your response bit I think there is something missing
  still.  This EQSL produced the following:
   
  
  
  
    fred
  
   
  >>> [EMAIL PROTECTED] 4/19/2004 7:53:47 AM
  >>>
  
  SET OutputRoot = InputRoot;
  SET
  OutputRoot.XML.people.person.(XML.Attribute)location = 'London';
   
  Regards
  Magendran Govender 
  
-Original Message-From: Daniel Graper
[mailto:[EMAIL PROTECTED]Sent: 19 April 2004 01:26To:
[EMAIL PROTECTED]Subject: MQSI - How to add attributes to
input XML
I am having some difficulty trying to add xml attributes to opening
tags that are input to one of our message flows.  Basically, I need to
find out how to take an input document like this:
 


  fred

 
and change it to something like this:
 



  fred

 
Does anyone have an example of this in a v2.1 compute node?
 
thanks,
Sebastian
 
  Please click on the following link to read the Old Mutual
  legal notice:  Alternatively, send a "blank" e-mail to  
   
Please click on the following link to read the Old
Mutual legal notice: 
Alternatively, send a "blank" e-mail to 

 

Re: MQSI - How to add attributes to input XML

[Govender Magendran]

SET OutputRoot = InputRoot;
SET
OutputRoot.XML.people.person.(XML.Attribute)location = 'London';
 
Regards
Magendran Govender 

  -Original Message-From: Daniel Graper
  [mailto:[EMAIL PROTECTED]Sent: 19 April 2004 01:26To:
  [EMAIL PROTECTED]Subject: MQSI - How to add attributes to
  input XML
  I am having some difficulty trying to add xml attributes to opening tags
  that are input to one of our message flows.  Basically, I need to find
  out how to take an input document like this:
   
  
  
    fred
  
   
  and change it to something like this:
   
  
  
  
    fred
  
   
  Does anyone have an example of this in a v2.1 compute node?
   
  thanks,
  Sebastian
   
Please click on the following link to read the Old
Mutual legal notice:  Alternatively, send a "blank" e-mail to
 
 

Re: How to fix invalid XML with broker

[Govender Magendran]

Title: RE: How to fix invalid XML with broker





Hi Francois


You take message in blob domain.


Then cast as char ie ESQL : CAST(InputRoot.BLOB.BLOB AS CHAR CCSID 819 ENCODING 546); 
Encoding will depend on platform, this works for W2K.


Then you can search for it in the string using POSITION function.


Alternatively you can search for the pattern in the blob.


Hope this helps.


Regards
Magendran


-Original Message-
From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED]]
Sent: 05 December 2003 12:53
To: [EMAIL PROTECTED]
Subject: Re: How to fix invalid XML with broker



John
I think that is what I am looking for, the code on how to do it in ESQL,
I'm not an expert ESQL programmer.
Thanks


Francois van der Merwe
Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert &
Developer
IBM, Cape Town, South Africa
+27 (0)82 556 9467 / +27 (0)21 402 5597
[EMAIL PROTECTED]





  John Scott
  <[EMAIL PROTECTED]    To:   [EMAIL PROTECTED]
  .CO.UK>  cc:
  Sent by: MQSeries    Subject:  Re: How to fix invalid XML with broker
  List
  <[EMAIL PROTECTED]
  N.AC.AT>



  05/12/2003 10:40
  Please respond to
  MQSeries List





What you're looking to do is remove the second  instruction and
enclose the whole lot in a  element.


Can you cast the message to a non-XML plain string and then use string
manipulation to find the end of the first  and insert a
,
then find and remove the next  and then append 


Regards
John Scott
IBM Certified Specialist - MQSeries
Argos Ltd



-Original Message-
From: Francois Van der Merwe1 [mailto:[EMAIL PROTECTED]]
Sent: 05 December 2003 08:24
To: [EMAIL PROTECTED]
Subject: How to fix invalid XML with broker



Using WBIMB V5 fixpack 2


I've got the following invalid xml flowing into the broker:




   Something 
   Something  else 



  
 Groot Kokkedoor 
  1000
  
  
 Nelson 
  100
  



So, from above, the XML is invalid.   I need to change it with the broker
to:



   Something 
   Something  else 


  
 Groot Kokkedoor 
  1000
  
  
 Nelson 
  100
  




Any ease way to do this?


Thanks


Francois van der Merwe
Senior IT Specialist: IBM MQSeries Certified Specialist, Solutions Expert &
Developer IBM, Cape Town, South Africa
+27 (0)82 556 9467 / +27 (0)21 402 5597
[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



***



Click here to visit the Argos home page http://www.argos.co.uk


The information contained in this message or any of its attachments may be
privileged and confidential, and is intended exclusively for the addressee.
The views expressed may not be official policy, but the personal views of
the originator.
If you are not the addressee, any disclosure, reproduction, dissemination
or use of this communication is not authorised.
If you have received this message in error, please advise the sender by
using the reply facility in your e-mail software.
All messages sent and received by Argos Ltd are monitored for virus, high
risk file extensions, and inappropriate content.  As a result users should
be aware that mail maybe accessed.


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 : Non-Unique Message Ids

[Govender Magendran]

Title: Re : Non-Unique Message Ids





Hi all


I have a question for the OS390 guys with regards to the DPL Bridge.


We have an application sending request messages that have a message id that is non-unique so that we can aggregate/relate all the replies. The DPL Bridge requires that the Correl Id be set to NEW SESSION CORRELID and so we therefore set the Message Id so it can be passed back in the Correl Id.

The problem is that this causes the DPL Bridge to process these messages in a single thread ( it does not spawn additional threads ) which is a bottle neck in the system. We have stress tested the DPL Bridge using unique message id's ( which is generated by the Queue Manager ) and the DPL Bridge spawns multiple threads and processes the messages in sub milli-seconds. But this is not the case if the message id is not unique.

A possible solution would be that the requesting app keep track of the all the message ids (that are unique because it will be generated by the Queue Manger ) and this could possibly keeping track of 50 message ids.

Is there an alternative solution ?


Can the DPL Bridge be configured to process the messages using multiple threads ?


Thanks, in advance


Magendran Govender

Re: Programmatically stopping and starting of the broker.

[Govender Magendran]

Title: RE: Programmatically stopping and starting of the broker.





Hi All, 


Is it advisable to programmatically stop and start the broker ?  If it is, what are the guidelines and best practises surrounding this type of function and what will the impact be on the integrity and security of the broker ?

Your help will be much appreciated 


Regards
Sedick Fakir

Re: CICS DPL Bridge and MsgId's, CorrelId's

[Govender Magendran]

Title: RE: CICS DPL Bridge and MsgId's, CorrelId's





Hi Dennis


Why would we want to set the Message Type as Report.


The problem we were experiencing is as follows :
I have a application putting messages on a remote queue to the CICS DPL Bridge Queue.


The message format is MQCICS,
The message type is MQMT_REQUEST


A new message id is generated for every request.
The correl id is set to MQCI_NEW_SESSION


The CICS DPL Bridge picks up the message and processes and sends the reply.


But it does not copy the message id of the request into the correl id of the reply message.
In all instances a new message id is set and the correl id is the same as the message id.


I want the request message id to be populated in the correl id of the reply message.



We do not require a report, we just needed the request message id to be relayed in the correlid of the reply.


Regards
Magendran


-Original Message-
From: Miller, Dennis [mailto:[EMAIL PROTECTED]]
Sent: 18 July 2003 06:43
To: [EMAIL PROTECTED]
Subject: Re: CICS DPL Bridge and MsgId's, CorrelId's



HmmmYou may have sunk the nail, but I don't think you hit it on the head.  What really controls that behaviour is MD.REPORT.  

regards,
Dennis


> -Original Message-
> From: Govender Magendran [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, July 17, 2003 11:41 PM
> To:   [EMAIL PROTECTED]
> Subject:   Re: CICS DPL Bridge and MsgId's, CorrelId's
> 
> Hi all 
> 
> Problem solved. 
> 
> I set the MsgType as Datagram. 
> 
> Regards 
> Magendran 
> 


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: CICS DPL Bridge and MsgId's, CorrelId's

[Govender Magendran]

Title: RE: Re: CICS DPL Bridge and MsgId's, CorrelId's





Hi all


Problem solved.


I set the MsgType as Datagram.


Regards
Magendran

Re: CICS DPL Bridge and MsgId's, CorrelId's

[Govender Magendran]

Title: Re: CICS DPL Bridge and MsgId's, CorrelId's





Hi all


I have a application putting messages on a remote queue to the CICS DPL Bridge Queue.


The message format is MQCICS,
The message type is MQMT_REQUEST


A new message id is generated for every request.
The correl id is set to MQCI_NEW_SESSION


The CICS DPL Bridge picks up the message and processes and sends the reply.


But it does not copy the message id of the request into the correl id of the reply message.
In all instances a new message id is set and the correl id is the same as the message id.


What am not setting in the MQMD or MQCIH for message id to be relayed in the correl id of the reply message.


I want the request message id to be populated in the correl id of the reply message.


Any ideas/solutions.


Thanks, in advance
Magendran

Re: WMQI : Set MQMD.Format to MQFMT_CICS

[Govender Magendran]

Title: Re: WMQI : Set MQMD.Format to MQFMT_CICS



Hi
 
I am
already setting values :
SET
OutputRoot.MQMD.Format = MQFMT_CICS; (MQFMT_CICS resolves to 'MQCICS  ' as
shown in the trace)
SET
OutputRoot.MQCIH.Format = MQFMT_STRING;
 
I have included settings : " SET OutputRoot.MQCIH.CodedCharSetId=1208;SET
OutputRoot.MQCIH.Encoding = 546;"
 
And it still gives the same
result.
 
The question is
: 
The CodeCharSetId and Encoding field are for convert the message
from one CharSet to another.
 
The message originates from NT and then goes to the
CICS Bridge Queue, and won't the channel convert the message when going
from one platform to another. 
The channels  convert option is set to yes between
these 2 queue managers.
 
Thank you for the
information.
 
Regards,
Magendran


  -Original Message-From: Nagendra
  [mailto:[EMAIL PROTECTED]Sent: 10 July 2003
  10:53To: [EMAIL PROTECTED]Subject: Re: WMQI : Set
  MQMD.Format to MQFMT_CICS
  Hi,
   
   
  In your message you should have
  
  MQMD
  MQCIH
  
   
  By changing the format of your
  MQMD you are telling MQSI that the MQCICS header follows your MQMD and it
  should use MQCIH parser, which is not true in your case.
  The order in your case is
  
  MQMD
  
  MQCIH
   
  Try out the following and see if
  it works.. theoretically it should
   
  SET OutputRoot.MQMD.Format =
  'MQCICS  ';SET OutputRoot.MQCIH.CodedCharSetId=1208;SET
  OutputRoot.MQCIH.Encoding = 546;SET OutputRoot.MQCIH.Format  =
  'MQSTR   ';
  ..
  ..
  Follow above statements by your
  XML to MRM assignments.
   
   
  Hope this helps.
   
   
  Note:- For MQCICS header, the
  parser is MQCIH and class name is "MQCICS"
   
  Regards,
  Nagendra
   
   
  
    - Original Message - 
From:
Govender Magendran 
To: [EMAIL PROTECTED] 
Sent: Wednesday, July 09, 2003 11:43
PM
Subject: Re: WMQI : Set MQMD.Format to
MQFMT_CICS

Hi all 
I have a messageflow that transforms an input XML
message to a Custom Wire Format(Cobol Copybook). 
The output message has a CICS Header followed by
the copybook record. 
We have a CICS Bridge that picks up the cobol
message and processes it. 
We have to set the MQMD.Format to MQFMT_CICS
because a CICS Header exists. 
When trying to set MQMD.Format field in WMQI,
WMQI does not set it. When the message written to the output queue the
message format seems to be MQFMT_NONE.
The ESQL used in WMQI is as follows :
SET "OutputRoot"."MQMD"."Format" =
MQFMT_CICS; I have tried setting the
MQMD.Format to MQFMT_STRING and this work i.e. WMQI sets the value.
I have run traces and when tracing ${Root} the
MQMD.Format field is not in the trace when setting the field to MQFMT_CICS
but it is in the trace when setting the MQMD.Format field to MQFMT_STRING
.i.e. the trace shows the field set to MQSTR.
Any ideas on what might be wrong will really be
appreciated. 
Thanks, in advance 
Magendran Govender
  

Re: WMQI : Set MQMD.Format to MQFMT_CICS

[Govender Magendran]

Title: Re: WMQI : Set MQMD.Format to MQFMT_CICS





Hi all


I have a messageflow that transforms an input XML message to a Custom Wire Format(Cobol Copybook).


The output message has a CICS Header followed by the copybook record.


We have a CICS Bridge that picks up the cobol message and processes it.


We have to set the MQMD.Format to MQFMT_CICS because a CICS Header exists.


When trying to set MQMD.Format field in WMQI, WMQI does not set it. When the message written to the output queue the message format seems to be MQFMT_NONE.

The ESQL used in WMQI is as follows :
SET "OutputRoot"."MQMD"."Format" = MQFMT_CICS;
I have tried setting the MQMD.Format to MQFMT_STRING and this work i.e. WMQI sets the value.
I have run traces and when tracing ${Root} the MQMD.Format field is not in the trace when setting the field to MQFMT_CICS but it is in the trace when setting the MQMD.Format field to MQFMT_STRING .i.e. the trace shows the field set to MQSTR.

Any ideas on what might be wrong will really be appreciated.


Thanks, in advance


Magendran Govender

Re: CSD Version(s)

[Govender Magendran]

Title: CSD Version(s)



Check
the Service Level document for WMQSI. ( memo.ptf )

  -Original Message-From: Fakir Sedick
  [mailto:[EMAIL PROTECTED]Sent: 11 March 2003
  12:38To: [EMAIL PROTECTED]Subject: CSD
  Version(s)
  How do find out what csd version(s) you have
  intsalled on your Control Centre, Broker and  Configuration Manager
  ?   Thanks, Sedick

Re: MQSeries and Delphi

[Govender Magendran]

Title: Re: MQSeries and Delphi





Hi all


I am writing a Delphi Client app, using the Delphi Files(cmqpas.zip) by Dinko Miljak. The app just puts/gets a message on/from  a queue. It works fine when running on the server but when it runs on the client it does not connect to the queue manager on the server.

I have set the necessary parameters in the MQCNO and MQCD structures when using the CONNX call and have created the SERVER CONN channel on the server. I used the AMQSCNXC app to verify the connection and it successfully gets the queue manager name from the server. 

I also tried linking the app to the mqic32.dll instead of the mqm.dll and it does not work.


Am I am missing anything ?


Regards
Magendran