Henry Tabingo

Forum Replies Created

Viewing 11 replies – 1 through 11 (of 11 total)
  • Author
    Replies
  • in reply to: Iterate Issue #78413
    Henry Tabingo
    Participant

      {

       [{OBX}]

       [{NTE}]

       [{ZDS}]

      }

      I don’t know how you changed your variant to make your translate work, but your original variant above shows your group with all segments [{OBX}], [{NTE}], and [{ZDS}] optional and repeating. All I’m saying is that you can have several ZDS segments within the group. And that’s what I’m suggesting that you iterate through if you need to process all the fields in each repeating ZDS segment in a group. If your message has only one ZDS segment in each group, your code works fine. I could be making wrong assumptions on your variant and message after you have made changes.

      in reply to: Iterate Issue #78411
      Henry Tabingo
      Participant

        Jon,

        You don’t need to iterate on all ZDS segments if you only need to process the first ZDS segment, as you are doing now.

        Thanks.

        in reply to: Iterate Issue #78409
        Henry Tabingo
        Participant

          Jon,

          I don’t know if you have already resolved your xlate iterate issue. If not, it appears your variant has a repeating ZDS segment and I don’t see a ZDS segment iterate. You may have to do that first before iterating the ZDS field.

          My 2 cents.:)

          in reply to: FRL to XML Translate Warning #75629
          Henry Tabingo
          Participant

            Robert,

            In CL 5.7 I tried changing the minimum values to 0 and recompiled, but was still getting the warning.

            We just upgraded to CL 5.8 and the same translate no longer generated warning messages in the log file. Interesting!

            Thanks for you help!

            in reply to: Route Message from Tcl proc #75364
            Henry Tabingo
            Participant

              Chris,

              Sorry I missed your last statement indicating you have only one message going to 15 different locations.

              in reply to: Route Message from Tcl proc #75363
              Henry Tabingo
              Participant

                Chris,

                If you can identify uniquely the one message out of 15 you want to send based on the segment, field, and subfield, at Adventist Health we use a tcl script that might help you.  The disposition argument “‘continue” will send the one message and kill the rest and the disposition “kill” will kill the message and send the rest. I’m attaching the tcl proc. I hope it helps.

                in reply to: Concating an Iterate #74969
                Henry Tabingo
                Participant

                  Hi Kevin,

                  If you haven’t already resolved your xlate, you may also need to place the repeating variable in your destination path in that last concat. The OBR field will then have a repeating tilde “~” that separates each value:

                  CONCAT   {~2(0).1(0).OBX.00573(0).[1]}=::->2(0).0(0).OBR.00263(%g1)

                  Henry

                  in reply to: Concating an Iterate #74968
                  Henry Tabingo
                  Participant

                    Is your last concat statement within the iterate?

                    in reply to: ftp from Redhat to Windows #74630
                    Henry Tabingo
                    Participant

                      Jason,

                      I’m using the same fileset-ftp protocol to write to a folder on a windows box. Were on AIX with CL 5.7. The receiving system didn’t have to do more than just create the user login and password. It works fine for us. Try if you are able to manually go to the windows folder from your internet browser using the credentials? If not, then there might be a problem with how the ftp user account was set up.

                      Henry

                      Adventist Health

                      in reply to: xml translate #74636
                      Henry Tabingo
                      Participant

                        Jim,

                        I tried the first of your 3 options and it worked perfectly. The volume of the messages for this interface is not so many that the xml it creates is not extremely large. I hope that the xml size will not be an issue. Otherwise, we can always resort to one xml per message.

                        Again, thank you very much for your help.

                        Henry

                        in reply to: xml translate #74635
                        Henry Tabingo
                        Participant

                          Jim,

                          Thanks for the solutions you recommended. I’ll surely give one of these a try. I’ll let you know how it goes.

                          Henry

                        Viewing 11 replies – 1 through 11 (of 11 total)