[Kevin Scantlan]

I found this documentation in the Global Monitor v 6.1.1 release notes.

Roles

The Administrator creates and assigns roles to users. A role is a collection of permissions that includes command permissions and page resources. Permission changes made to the role are inherited by the users with this defined role.

Users

After creating roles, the Administrator creates users. When users are added to a view, the view keeps a user list, where all users on the list can access the view. Users can have different roles in different views.

Views

Administrator-created views

Administrators have access to all views. When roles and users are created, the Administrator creates views, adding users to views and assigning roles to users in different views.

The user/role list associated with a view determines who has access to the view. If the Administrator does not add any user to a view, that view is a private view for the Administrator, and other users cannot see it.

So, it appears that multiple users can share the same view.

[Kevin Scantlan]

Where did you find the documentation about hcialertnotify?  I’ve been trying to find how cause a pop-up notification window on Global Monitor when using the notify action with an alert.

[Kevin Scantlan]

Where is the documentation for this command?

I looked at the perl script for hcialertnotify and saw that it’s really only executing  hcicmd -t d -c “triggernotify $message $msgfile $source”.

I looked up triggernotify under hcicmd and it says:

triggernotify {ALERTNAME {alertname}} {ALERTMSG {message}} {ALERTSRC {source list}} .

Is the alertname an existing alert in your alert file?

Does the alert message override the action message?

Does the source list override the sources for that alert?

We use hciguimsg to write a message to the desktop with a particular IP address.  Our most useful usage is to create a pop up window (TK) on the screen where we run the netmonitor for operations.  How does hcialertnotify replace hciguimsg for this?  With hciguimsg we have to run Reflections on the desktop of who is supposed to receive the message.

Also, it is our intention to migrate completely to Global Monitor when get to version 6.1.2 for all of our sites.  How can we use hcialertnotify to send a message to our operators?

I searched for hcialertnotify in the Cloverleaf Integration Suite Help Contents and did not find anything.

[Kevin Scantlan]

Thanks, Rob!   I used your information and was able to recreate the error!  I did a kill -11 on a process and it PANIC’ed that process.  I brought the process back up and resent a single message into an inbound thread that is in the process.  The message got “stuck” in state 2.  I also got the following in the process log:

[tcl :out :INFO/0:     ccs_ci_4:08/30/2016 09:17:46] 160830 091746.1472566666   ccs_ci_4        CCSED   DFT^P03 20160829110320  2016082911

0320_001                        67-99-39-6()            28368899()                              LEIVA^ELIZABETH^    

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[cmd :cmd :INFO/0:test1_ps04_cmd:08/30/2016 09:17:46] Receiving a command

[cmd :cmd :INFO/0:test1_ps04_cmd:08/30/2016 09:17:46] Command client went away.  Closing connection.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

[pd  :pdtd:ERR /0:     ccs_ci_4:08/30/2016 09:17:46] [0.0.108735679] Delivery to xlate thread test1_ps04_xlate failed. Requeuing msg.

I have been told that there is a “fix” (6.1.2.1).  So once I install that fix, I can recreate the same scenario and see if it is indeed fixed.

Thanks for your help.  It appears we are on our way.

[Kevin Scantlan]

Does anyone know of a way to force an abort in a process?  Our issue occurs after a process aborts,  but we’ve not had an abort for over a week (which is good).  It seems like the only way we tell what is doing on, is to “catch it the act”.  I’m not of the belief that it’s not what’s causing the abort that is the issue, but how the engine handles the abort.  We don’t want to turn logging up and just wait for it to happen.  We want to be able to force the issue on the test site that resides on the same server and turn on the logging there.

Thanks.

[Kevin Scantlan]

We have built a number of apps where we use TK.  One example is where we have a number of domains (non-prod) in Cerner where we send/receive messages to our test interface engine (BUILD, CERT, DEV, TRAIN, etc).  We don’t have separate interfaces for each of them and we point the test engine to one of them at a time.  So, this apps allows us to configure the 30 plus interfaces for each domain, and the apps also allows us to switch between domains thread by thread, or a whole domain at a time.  We also have a utility app where we can view the current status like the netmonitor does, but has more features such as rate (messages/sec).  We can also view stats broken down by thread, hour , and message type within hour.  The are all graphic apps.

[Kevin Scantlan]

Rob,

I did not try to go a hcicmd command, but I presume that when we brought the process back up and the threads came back up that it was doing a hcicmd -p -c ‘ pstart” in the background.

We had not made any changes from version 5.8.5 to 6.1.2  in the NetConfig, the xlates, or the tclprocs.

We’ve been told that this has been submitted to R&D, but I’ve not heard anything from them.  Would it be possible to follow up on this.  It’s not happened again, but it’s a time bomb and we don’t know when it will happen again.

[Kevin Scantlan]

We have a case open.  It’s my guess that for some reason, version 6.1.2 is not handling a abort and it’s corrupting the ICL thread.  When we bring the process back up is when we start getting the “Delivery” messages.  When we clean up the ICL, it goes away.

[Kevin Scantlan]

Thanks!  That worked.

[Kevin Scantlan]

How can I have the IDE automatically launch the Network Monitor when it’s brought up?  Also, I would like to have it automatically point to a particular site instead of just brining up the last one closed.

[Kevin Scantlan]

1.  I usually do it from the process, but it’s my understanding you can’t purge cache for just a thread.  It’s always for the whole process.

2.  I think we have the NetMonitor GUI messages turned off.  Never check them.  

3.  Don’t know if the purgex worked or not.  That’s what I was trying to confirm.

4.  Not been busier.

I don’t see if show up in the process log when I do a hcicmd from the command line.  I do get a message XLT-related caches purged.  Which is different than the message in the process log.

[Kevin Scantlan]

Version 6.1.2, but same happens with 5.8.5  .  It’s not every process, just some.

[Kevin Scantlan]

I have some processes where the purgex does not show up in the process log.  I try it from the IDE and it does not show and I run it from hcicmd and it does not show.  So, I’m not sure if executed or not.

[Kevin Scantlan]

I notice your procedure, you remove the mid.ctr file.  What is this file for?  In the clean-up instructions for customers, I do not see this step.

Thanks.

[Kevin Scantlan]

No, you do not need advanced security.

[Author]

Replies