ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Change in Message set resulted in weird things

Post new topic  Reply to topic
 Change in Message set resulted in weird things « View previous topic :: View next topic » 
Author Message
edasnarik
PostPosted: Fri Feb 12, 2010 4:30 am    Post subject: Change in Message set resulted in weird things Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

I have enhanced one message set and I find that my segments are not interpreted properly like before. Not able to understand and comprehend the change.
Previously
Code:

Form 
   Number = PP0167

Now
Code:

Form =
   Number = PP0167


Any suggestions ? Has anyone faced this kind of a problem before?
Back to top
View user's profile Send private message
Gaya3
PostPosted: Fri Feb 12, 2010 4:44 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

what changes you have done to the message set , please explain to us properly.

how it is getting impacted, and how does the data mapping happens in the broker for that particular field.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
edasnarik
PostPosted: Fri Feb 12, 2010 4:49 am    Post subject: Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

I have added another global type and added that as element reference to Form segment.
And the elements, It is not particular only to that field. It is for all segments present in the schema.

Previously
Code:
MRM
   [b]Status[/b]
      StatusCd = 0
      StatusDesc = Success
   [b]InsuranceSvcRs[/b]
      RqUID = f81d4fae-7dec-11d0-a765-00a0c91e6bf6
      PolicyInqRs


Now
Code:
MRM
   [b]Status = [/b]
      StatusCd = 0
      StatusDesc = Success
   [b]InsuranceSvcRs = [/b]
      RqUID = f81d4fae-7dec-11d0-a765-00a0c91e6bf6
      PolicyInqRs =


And when I enter into Compute , the Status and InsuranceSvcRs segments names remain with no values in them.

This is the message I see in debug perspective.


Last edited by edasnarik on Fri Feb 12, 2010 5:34 am; edited 1 time in total
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Feb 12, 2010 5:16 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

What, exactly, is producing this output that you keep posting?
Back to top
View user's profile Send private message
edasnarik
PostPosted: Fri Feb 12, 2010 5:18 am    Post subject: Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

Code:
(0x0100001B):MRM        = (
    (0x01000013):Status         = (
      (0x0300000B):StatusCd   = '0'
      (0x0300000B):StatusDesc = 'Success'
    )
    (0x01000013):InsuranceSvcRs = (
      (0x0300000B):RqUID       = 'f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
      (0x01000013):PolicyInqRs = (
        (0x0300000B):RqUID                 = 'f81d4fae-7dec-11d0-a765-01a0c61f6bd5'
        (0x03000013):TransactionResponseDt = '2008-03-28T9:30:00.000-5:00'
        (0x03000013):CurCd                 = 'USD'
        (0x01000013):MsgStatus             = (
          (0x03000013):MsgStatusCd   = 'Success'
          (0x03000013):MsgStatusDesc = 'none'
        )
        (0x03000013):AsOfDt                = TIMESTAMP '2007-08-15 00:00:00'
        (0x01000013):Requestor             = (
          (0x03000013):ContractNumber = '04101000'
        )
        (0x01000013):TransactionInqInfo    = (
          (0x01000013):TransactionInfo = (
            (0x03000013):TransactionEffectiveDt = TIMESTAMP '2008-03-28 00:00:00'
            (0x01000013):PartialPolicy          = (
              (0x03000013):PolicyNumber = '123456789'
              (0x03000013):LOBCd        = 'contact admin'
            )
            (0x03000013):PolicyStatusCd         = 'Issued'
          )
        )
        (0x01000013):PolInfo               = (
          (0x01000013):contact admin = (
            (0x01000013):Producer             = (
              (0x01000013):GeneralPartyInfo = (
         



Sample Messages
Code:
<?xml version="1.0" encoding="UTF-8"?>
 <ACORD xmlns="http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Status>
   <StatusCd>0</StatusCd>
   <StatusDesc>Success</StatusDesc>
  </Status>
  <InsuranceSvcRs>




Code:

  (0x0100001D):MRM        = (
    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Status         = NULL
    (
      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:StatusCd   = '0'
      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:StatusDesc = 'Success'
    )
    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:InsuranceSvcRs = NULL
    (
      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:RqUID       = 'f81d4fae-7dec-11d0-a765-00a0c91e6bf6'
      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PolicyInqRs = NULL
      (
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:RqUID                 = 'f81d4fae-7dec-11d0-a765-01a0c61f6bd5'
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:TransactionResponseDt = '2008-03-28T9:30:00.000-5:00'
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:CurCd                 = 'USD'
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:MsgStatus             = NULL
        (
          (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:MsgStatusCd   = 'Success'
          (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:MsgStatusDesc = 'none'
        )
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:AsOfDt                = '2007-08-15'
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Requestor             = NULL
        (
          (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:ContractNumber = '04101000'
        )
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:TransactionInqInfo    = NULL
        (
          (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:TransactionInfo = NULL
          (
            (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:TransactionEffectiveDt = '2008-03-28'
            (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PartialPolicy          = NULL
            (
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PolicyNumber = '123456789'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:LOBCd        = 'contact admin'
            )
            (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PolicyStatusCd         = 'Issued'
          )
        )
        (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PolInfo               = NULL
        (
          (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:contact admin = NULL
          (
            (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PersPolicy = NULL
            (
              (0x0300000D):@id                                                                        = 'yyy'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:PolicyNumber           = '123456789'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:CompanyProductCd       = 'Prestige Home Premier'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:LOBCd                  = 'contact admin'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:ControllingStateProvCd = 'AZ'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:OriginalInceptionDt    = '1997-01-01'
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Form                   = NULL
              (
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormNumber          = 'PP0167'
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormName            = 'Amendment of Policy Provisions - Arizona'
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:EditionDt           = '2005-11'
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:com.ffic_FillInData = NULL
                (
                  (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:com.ffic_FillInDataCoverage = NULL
                  (
                    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:CoverageDesc = 'Bodily Injury'
                    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Limit        = NULL
                    (
                      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormatText       = '500'
                      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:LimitAppliesToCd = 'PerPers'
                    )
                  )
                  (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:com.ffic_FillInDataCoverage = NULL
                  (
                    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:CoverageDesc = 'Hurricane Coverage'
                    (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Limit        = NULL
                    (
                      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormatText       = '50000'
                      (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:LimitAppliesToCd = 'PerOcc'
                    )
                  )
                )
              )
              (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:Form                   = NULL
              (
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormNumber = 'PP0309'
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:FormName   = 'Single Liability Limit'
                (0x0300000D)http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/:EditionDt  = '2005-11'



Code:
<ACORD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="acord-pcs-v1_11_0-nodoc-codes.xsd">
   <Status>
      <StatusCd>0</StatusCd>
      <StatusDesc>Success</StatusDesc>
   </Status>
   <InsuranceSvcRs>



The second one has
Code:
<Form>
                  <FormNumber>PP0167</FormNumber>
                  <FormName>Amendment of Policy Provisions - Arizona</FormName>
                  <EditionDt>2005-11</EditionDt>
                  <com.ffic_FillInData>
                     <com.ffic_FillInDataCoverage>
                        <CoverageDesc>Bodily Injury</CoverageDesc>
                        <Limit>
                           <FormatText>500</FormatText>
                           <LimitAppliesToCd>PerPers</LimitAppliesToCd>
                        </Limit>
                     </com.ffic_FillInDataCoverage>
                     <com.ffic_FillInDataCoverage>
                        <CoverageDesc>Hurricane Coverage</CoverageDesc>
                        <Limit>
                           <FormatText>50000</FormatText>
                           <LimitAppliesToCd>PerOcc</LimitAppliesToCd>
                        </Limit>
                     </com.ffic_FillInDataCoverage>
                  </com.ffic_FillInData>
               </Form>


elements extra.[/code]


Last edited by edasnarik on Fri Feb 12, 2010 5:52 am; edited 1 time in total
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Feb 12, 2010 5:21 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Example messages would be a big help.
And please note that we do not know what a 'Form segment' is.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Fri Feb 12, 2010 5:50 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

edasnarik wrote:
I am posting the message from debug jeff.
I will posting the user trace soon. one min..


Did you upgrade your toolkit?
Back to top
View user's profile Send private message
edasnarik
PostPosted: Fri Feb 12, 2010 5:54 am    Post subject: Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

mqjeff wrote:
edasnarik wrote:
Did you upgrade your toolkit?

No Jeff.

kimbert wrote:
Example messages would be a big help.

Edited my previous Posts and placed them. Pls check.
Back to top
View user's profile Send private message
edasnarik
PostPosted: Fri Feb 12, 2010 6:08 am    Post subject: Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

Hey Guys Thanks Everyone

Seems like the
Code:
<ACORD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="acord-pcs-v1_11_0-nodoc-codes.xsd">
is the trick .

If I place this at the top of messages ,only then it is working.

I don't know reasons. Can somebody interpret them for me ?
Back to top
View user's profile Send private message
edasnarik
PostPosted: Wed Mar 17, 2010 9:59 pm    Post subject: Reply with quote

Acolyte

Joined: 10 Mar 2009
Posts: 61

Am I missing something when I modify this in the XML message ?
Please help.
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Mar 18, 2010 2:20 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

In the first case, the input XML does not have a default namespace, and the tags are matched successfully against the elements in the message set.

In the second case, you have added
Code:
xmlns="http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/"
. All of the tags are now in namespace "http://www.ACORD.org/standards/PC_Surety/ACORD1/xml/", and they are *not* matched against the elements in the message set. The data is still parsed, but it is parsed as 'self-defining' data.

It looks very much as if the message definition is expecting the namespace to be "". Are you 100% sure that you have not been changing the target namespace in your message definition file(s)?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Change in Message set resulted in weird things
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.