Clovertech

Alternatives to bouncing the interface to capture output

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Alternatives to bouncing the interface to capture output

  • Creator
    Topic
  • May 20, 2011 at 4:11 pm #52495
    Rehman Masood
    Participant

      We have a process that receives data from a port and we keep on storing all the messages/data into a single file. Up on 5.4.1rev2 we had a task scheduler task that stopped the interface/moved the file that the data was written to/start the interface back up. I did like to get away from this task to be outside of cloverleaf. Is there another alternative to do the same? Something along the lines that cloverleaf at a particular time at the data, starts writing data to a different file or cycles the output file somehow?

      Thanks,

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • May 20, 2011 at 6:56 pm #74465
        Levy Lazarre
        Participant

          Rehman,

          There is a way to accomplish what you want to do, without stopping the thread, using a UPOC thread instead of a fileset protocol.

          This is a technique I learned from Charlie Bursell and I describe it briefly on page 2 of the following post:

          https://usspvlclovertch2.infor.com/viewtopic.php?t=4138

          Take a look and see if you can use this to your advantage. It has worked very well for me.

          I hope this helps.

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