Clovertech

rearrange billing flat file in TCL

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › rearrange billing flat file in TCL

  • Creator
    Topic
  • December 16, 2010 at 1:46 pm #52166
    Gary Atkinson
    Participant

      Ok here goes—

      Here is an example of what flat file looks like (each line term with a NL)


      4201034600051 1212104039140 001       [code]
      4201034600051 1212104039140 001

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • December 16, 2010 at 2:06 pm #73267
        Jim Kosloskey
        Participant

          Gary,

          Are you wanting to do this in an Xlate?

          If so, I would think that some of the lifting can be done by using the FRL for more than just specifying the individual fields.

          Then some Tables might be in order (depending on the dynamics involved).

          The IF Action will come into play as well as SUPPRESS, etc.

          And finally maybe some minor Tcl.

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

        • December 16, 2010 at 3:04 pm #73268
          Charlie Bursell
          Participant

            Lay this out in an FRL, naming each field then state the requirements.  It would make more sense that way.

            As Jim says, if you can you need to use FRL, because flat file layouts can change and blow the Tcl out of the water

            Be careful on file names like:  YYYYMMDDHHMMSS.MISCHG

            The engine can process more than one record per second and you *WILL* lose data.  Combine with a counter.

          • December 16, 2010 at 7:48 pm #73269
            Gary Atkinson
            Participant

              I have used FRL in the pass with flat files, but in this specific case.  Doesn’t the translation parse out one line of flat file at a time?  How do account for looking at multiple lines in determining what the billing code should be?

            • December 16, 2010 at 8:02 pm #73270
              Charlie Bursell
              Participant

                I am just saying define as an FRLfor ease of understanding.  Then you can name each field and describe the problem much better.

                An FRL can be passed as a file (eof).  Not sure how easy it would be to translate.

                I was just trying to wrap my arms around what he is trying to accomplish

              • December 16, 2010 at 8:58 pm #73271
                Gary Atkinson
                Participant

                  FRL is attached.

                • December 16, 2010 at 9:13 pm #73272
                  Charlie Bursell
                  Participant

                    That helps but still a bit confused

                    Are these 7 lines considered one record?  Will there always be 7?

                    The part about adding and deleting lines is still very confusing to me.

                    Of course, I am easily confused  😕

                  • December 17, 2010 at 1:50 pm #73273
                    Gary Atkinson
                    Participant

                      Each line is a record.

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