Clovertech

IF data fetch produced multiple values.

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › IF data fetch produced multiple values.

  • Creator
    Topic
  • September 10, 2014 at 3:07 pm #54375
    Mike Campbell
    Participant

      Cloverleaf running on AIX

      We are testing the 6.0.2 patch.  Since we’ve applied the patch we are getting a lot of the multiple value errors with our ‘IF’ statements.  Any idea why those would hit with the patch when they aren’t in the 6.0. version?  

      Thanks.

      Mike C.

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • September 11, 2014 at 3:50 am #81220
        Robert Milfajt
        Participant

          Don’t know why you would see more by just loading the patch.  However, when I see them, it usually due to and ^ or & in a data field being used in an IF statement.

          You’ll need to find the actual cause, to determine if the patch changed the format in such a way due to patch to break the IF statement, or if it is coincidence that you are getting data causing the problem at the exact same time you loaded the patch.

          Robert Milfajt
          Northwestern Medicine
          Chicago, IL

        • September 11, 2014 at 12:14 pm #81221
          Mike Campbell
          Participant

            I know the cause, in this case it is ‘&’ in the message.

            What is odd is the same message replayed out of SMAT does NOT cause the IF to throw the error in the 6.0.0 but it does in 6.0.2.

          • September 11, 2014 at 1:15 pm #81222
            Jim Kosloskey
            Participant

              Mike,

              I think the following is what is occurring:

              There is a what I think is a bug in 6.0.0 which under certain circumstances when a field with subcomponent separators is encountered it does not get marshaled into multiple elements of the xlateInVals – thus not seeing an error in your IF.

              Beginning in 6.0.1 that ‘bug’ disappears and the Xlate reverts back to the norm which is in all circumstances if a referenced component has a subcomponent separator in the component (valid or not) then xlateInVals will have multiple elements not just one – thus the error you are seeing.

              So you are being bit by the failure of your sending system to properly handle MSH-1/MSH-2 characters in a text field.

              Email me and I will discuss what I think you can do to work around this.

              email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.