Clovertech

cyclesave IB SMAT

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › cyclesave IB SMAT

  • Creator
    Topic
  • February 3, 2006 at 3:18 pm #48293
    Rentian Huang
    Participant

      Greetings Cloverleafers!!!

      V5.2 on AIX

      I am trying to cyclesave my IB SMAT, my thread was up and running when I tried it via the GUI (Full->cycle save->in), nothing happened. Then i did it from the command line and I got this:

      Code:

      hcicmd -p cis_rad -c “cis_rad_ord_in save_cycle in”
      Response:
      saving of inbound messages is not active

      I tried the same ways with others running thread and they worked fine, why?

      Sam  ðŸ™‚

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • February 3, 2006 at 6:42 pm #58264
        James Cobane
        Participant

          Rentian (Sam),

          The message indicates that the inbound save for that thread is not turned on, which is why there is nothing to cycle.  So, it is likely not ‘checked’ in NetConfig, or someone had stopped the save via the NetMonitor (or command line), and the thread has not been bounced since the save was stopped.

          Hope this helps.

          Jim Cobane

          Henry Ford Health

        • February 3, 2006 at 9:28 pm #58265
          Rentian Huang
          Participant

            Jim,

            I checked the Property of the thread and the “Save inbound messages” was checked. And I have been bouncing the process recently for a few times…

            One thing I haven’t point out was, there were a lot of msgs (thousands) keep coming to this IB thread since I couldn’t build an acceptable ACK to the sending system. Could that be the reason?

            Thanks for your help Jim!

            Sam

          • February 6, 2006 at 12:55 pm #58266
            James Cobane
            Participant

              Rentian (Sam),

              The fact that you are getting lots of messages shouldn’t be an issue; the saved message file gets invoked as soon as the message is read on the connection, so you should have “lots” of saved messages 🙂.

              The only other things I would recommend checking is the log, to see if there is an error messaging indicating that the engine is unable to write to the saved message file; sometimes this can happen if the thread was re-started with SMAT still open on that saved message file.  Also, look to see if there is an existing .msg and .idx for that thread and see what the date and time stamp is for it.  If the files exist, I would stop the thread, and rename/remove the current .idx and .msg files, then re-start the thread.  This should allow the engine to re-create the saved message file.  There is also quirk in SMAT on Platform V, that if you open a current saved message file (with the thread stopped), exit SMAT cleanly, and then start the thread, it still can get an error attempting to open the saved message file.  So, you ultimately have to rename/remove the existing saved message file to allow the engine to re-create it.

              Hope this helps.

              Jim Cobane

              Henry Ford Health

            • February 6, 2006 at 4:26 pm #58267
              Rentian Huang
              Participant

                James,

                Thanks a lot for the information, it helps me to pinpoint the problem!

                Once this situation happens again, I will follow this solution. I think did not close the SMAT properly…

                Good day,

                Sam  8)

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