David Bolin

Forum Replies Created

Viewing 5 replies – 1 through 5 (of 5 total)
  • Author
    Replies
  • in reply to: message throttling #71083
    David Bolin
    Participant

      Here is a very simple idea for throttling the messages coming in from any particular inbound thread. Copy the “create_ack” proc as “create_ack_delay” and then add a 1 second sleep delay to the new proc. Replace this  “create_ack_delay” proc to do the function of “create_ack” proc for each thread in need of throttling. Be advised that this will then hold the messages on the client as they stack up. For the Cloverleaf admin this is great but may be a problem for the client machine’s admin. We implemented this to prevent sporadic critical messages from getting stuck in the out bound queue behind a stack of low importance batch messages.

      in reply to: Cloverleaf 5.7 on AIX 5.3 TL9 #68184
      David Bolin
      Participant

        Donna Snider wrote:
        We are running on AIX 5.3.

        in reply to: Issues running CIS5.6Rev2 on AIX5.3 TL10 #68860
        David Bolin
        Participant

          I’m asking the same questions as Robert but for 2 other versions:

          Healthvision does not certify OS patch levels.  CIS5.7 Rev1 is certified on TL8 only. Also, I can’t find what versions CIS5.4.1 is certified for either.

          Has anyone run these versions of the Integrator on TL10?  Any problems?

          I am currently running CIS5.4.1 Rev2 on AIX5.3 TL5-SP6 and wish to upgrade to CIS5.7 Rev1.  

          Can anyone suggest the common AIX version to go to and final version of AIX to settle on?  I would prefer AIX5.3 TL10…

          in reply to: Time out on Established Connections #64336
          David Bolin
          Participant

            Gary Atkinson wrote:
            I just went through a similar issue, but cloverleaf was the sender.

            in reply to: FTP to an iSeries #62143
            David Bolin
            Participant

              You should attempt a manual ftp (external to cloverleaf) from the engine server to the iseries.  This will help determine the source of the problem. SQL creates physical files too. The main difference is the name of the member within its physical file. Maybe you left that off and need to use it. Its in the form library.file.mbr. If you leave the member off then it defaults to same name as the file name.

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