Mark Gathers

Forum Replies Created

Viewing 15 replies – 1 through 15 (of 17 total)
  • Author
    Replies
  • in reply to: Cloverleaf 6.2.0.2 – Windows 7 Enterprise #85572
    Mark Gathers
    Participant

      Yes, we have successfully installed v6.2.1 using Windows 7.

      in reply to: NetConfig problem #71080
      Mark Gathers
      Participant

        All,

        Just wanted to let you know cloverleaf tech support resolved our engine issue, appears we had a brace instead of parenthesis inside the /etc/hosts file that the tcl program didn’t like.

        in reply to: Creating multiple messages from one #59992
        Mark Gathers
        Participant

          Hi Carl,

          You may also be able to use the Suppress & Continue commands.  Suppress allows you to generate multiple outbound messages from a single inbound message.

          in reply to: hostserver CPU usage #58608
          Mark Gathers
          Participant

            Hello all,

            QDX 5.3 rev3, AIX 5.2

            Regarding the java arg,

            Set as follows in the server.ini file

            [general]

            jvm_args=-Xmx256m

            [logging]

            Check all workstations accessing the engine and repeat same procedure  to the client.ini file.  Also, include the netmon parm.

            [general]

            doc_base_dir=C:quovadxqdx5.3integrator

            debug=false

            jvm_args=-Xmx256m

            netmon_auto_load_logs=false

            in reply to: re: Alerts for Recovery DB #59482
            Mark Gathers
            Participant

              Thanks Reggie,

              I wanted something that checks the whole Recovery Database and not by each thread.  I decided to created a UNIX script and check the message count in the Recovery DB using the following command:

              mshcnt=`hcidbdump -r | wc -l | tr -d ” “`  

              If the mshcnt is over a 1000, the script sends a warning alert message via paging and email to us.  Works pretty good.

              I doing this because we neglected to cycle a process after deleting a route.  Since the destination thread was deleted, the messages continued to build up in the Recovery DB without anyone knowing.

              Mark

              Mark Gathers
              Participant

                Something like the following should work, where the time starts in the 7th position of the field for 4 chars.

                set xlateOutVals

                  6 4]]

                  Regards,

                  Mark Gathers

                  West Virginia Univeristy Hospitals

                  Email:  gathersm@wvuh.com

                  in reply to: HA scripts and how long they take #59327
                  Mark Gathers
                  Participant

                    I read this post and we experienced the same problem taking the engine down.   The serial process takes too long.  We don’t have HA installed but I’m wondering if a faster method is available for taking the engine sites/processes down.  Any help would be appreciated.

                    Regards,

                    Mark Gathers

                    Phone: 304.598.4000 x75615

                    Email:  gathersm@wvuh.com

                    Mark Gathers
                    Participant

                      Dan,  

                      Hey this is cool stuff!, any chance I could get a copy of the Visio documentation as well?

                      Regards,

                      Mark Gathers

                      Integration Engineer, Information Technology

                      University Health Associates

                      West Virginia University Hospitals

                      PO Box 8059

                      Morgantown, WV 26506

                      Phone: 304.598.4000 x75615

                      Email:  gathersm@wvuh.com

                      in reply to: Activation of a new route #58822
                      Mark Gathers
                      Participant

                        You’ll need to bounce the process to activate the new route.

                        in reply to: Monitor Daemon Issue 3.8.1P AIX5.2 #58677
                        Mark Gathers
                        Participant

                          The path references I was referring is in the default.alrt file as follows:

                          {VALUE df} {SOURCE /qdx/qdx5.3} {MODE actual} {WITH -1} {COMP {>= 80}} {FOR once} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{notify {}}}}

                          {VALUE df} {SOURCE /qdx/qdx5.3} {MODE actual} {WITH -1} {COMP {>= 80}} {FOR once} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {/usr/local/bin/qdxAlertMail-WVUH  “IEPROD – ENGINE Alert: Disk Space is now 80% full”}}}}

                          {VALUE df} {SOURCE /qdx/qdx5.3} {MODE actual} {WITH -1} {COMP {>= 80}} {FOR once} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {/usr/local/bin/qdxAlertPage-WVUH  “IEPROD – ENGINE Alert: Disk Space is now 80% full”}}}}

                          Also, you may want to check /qdx/qdx5.3/integrator/client/client.ini and make sure netmon_auto_load_logs is set as follows:

                          [general]

                          netmon_auto_load_logs=false

                          in reply to: Monitor Daemon Issue 3.8.1P AIX5.2 #58675
                          Mark Gathers
                          Participant

                            We experienced the same problem and found a qdx path error in the alert file where we referenced the old release.  We updated the alert file and  changed the path reference.  This seems to have fixed the problem.

                            Mark Gathers

                            West Virginia University Hospitals

                            in reply to: re: AIX 5.2 & QDX 5.3 rev3 #58568
                            Mark Gathers
                            Participant

                              I called into tech support and you do NOT need the MNRATIO unless your on AIX 5.1 ML3.  

                              Mark

                              in reply to: re: AIX 5.2 & QDX 5.3 rev3 #58566
                              Mark Gathers
                              Participant

                                Thank you Ryan for sharing your response.  We continued our O/S upgrade Wednesday from AIX 5.2 ml4 to ml8 and everything appears fine so far.  I agree, we’ll need to do more testing before we install into production.

                                in reply to: re: AIX 5.2 & QDX 5.3 rev3 #58564
                                Mark Gathers
                                Participant

                                  Thank you Rich,

                                  Yesterday, we did our AIX upgrade to from v5.1 to 5.2 ml4 and all went well.  Also, identified the same monitor problem that you described in your response.  Today, we’re planning to upgrade from ml4 to ml8 and see what happens.

                                  Mark Gathers

                                  West Virginia University Hospitals

                                  Mark Gathers
                                  Participant

                                    Hello,

                                    We’ve been live with ADT to eScription for over a year with no issues to report.

                                  Viewing 15 replies – 1 through 15 (of 17 total)