Clovertech

Modifications to existing Xlates

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Modifications to existing Xlates

  • Creator
    Topic
  • March 9, 2009 at 5:16 pm #50689
    Keith Oulson
    Participant

      When do changes to existing xlates take effect?

      Assuming an existing xlate is in use by a thread, saved mods to that xlate take effect as soon as the changes are saved, right?  Or does the process have to be bounced for the modified xlate to kick in?

    • Creator
      Topic
    Viewing 7 reply threads
    • Author
      Replies
      • March 9, 2009 at 5:22 pm #67117
        Max Drown (Infor)
        Keymaster

          You have to bounce.

          -- Max Drown (Infor)

        • March 9, 2009 at 5:24 pm #67118
          Keith Oulson
          Participant

            Thanks Max!

            Keith

          • March 9, 2009 at 6:19 pm #67119
            Jim Kosloskey
            Participant

              You can also ‘purge caches’ in the NetMonitor (or from the command line) meaning no interrruption to connections or processes.

              email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

            • March 9, 2009 at 8:11 pm #67120
              Keith Oulson
              Participant

                Very nice.

                Thanks Jim!

                Keith

              • March 10, 2009 at 1:16 pm #67121
                Tom Rioux
                Participant

                  Jim is correct, you can “purge cache” with no interruption.  However, in my experiences, it hasn’t always picked up the changes 100% of the time.  Maybe this isn’t the case anymore in 5.6 and up.  

                  I always bounce the process, where practical, to ensure that the changes will take effect.   If I have to purge cache (we have some systems that won’t reconnect on a bounce so we have to get application support people on the phone in those cases), then I check the outbound SMAT messages to make sure any changes are present in the delivered message.

                  Thanks…

                  Tom Rioux

                • March 10, 2009 at 2:56 pm #67122
                  Jim Kosloskey
                  Participant

                    Well my experience has been just the opposite – the only time I did not get what I wanteds when purging caches is when I did the purge caches against the wrong thread or a t the thread level instead of the process level.

                    As long as I did it at the correct place, I don’t ever recall having an issue.

                    I do recall however, that under certain circumstances (type of messages combined with a particular use of PATHCOPY) at a certain release (Cloverleaf(R) 5.4 I think) there were issues.

                    However, these have been corrected as far as I know and those particular circumstances do not occur here anyway.

                    Stopping and starting the processes (for the purposes of refreshing the caches) has always worked as far as I know.

                    email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

                  • March 10, 2009 at 2:58 pm #67123
                    Max Drown (Infor)
                    Keymaster

                      What’s the command line command for purging caches?

                      Edit: I think the command is: hcicmd -p test06 -c ‘. purgex’

                       (the “.” means the process)

                      -- Max Drown (Infor)

                    • March 10, 2009 at 4:27 pm #67124
                      Tom Rioux
                      Participant

                        Thanks for the heads up Jim.   I guess I’ve always took the “better safe than sorry” approach and bounced the processes.   I’m glad to hear that no one has issues with just purging caches.

                        Max,

                        You are correct!

                        Tom

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