starting threads from a view

This topic has 6 replies, 4 voices, and was last updated 16 years, 1 month ago by Bob Richardson.

Creator

Topic
March 16, 2010 at 6:51 pm #51634
Kevin Crist
Participant
we are trying to speed up our process of coming back up after a downtime, is there a way to start threads by the view from the command line to put into a script, i know you can manually do this but cant find a command to do it.

Thanks for any help.
Creator

Topic

Viewing 5 reply threads

Author

Replies
- March 17, 2010 at 9:03 am #71052
  Robert Kersemakers
  Participant
  Hi Kevin,
  
  You can start a thread from the command line with:
  Code: hcicmd -p -c ” pstart”
  
  But I think you want to start a bunch of threads from command line that are in a view, right? You will need to have a look at the file dflt.mvw then: it has all the views and all the threadnames belonging to a view.
  
  So you will need a script to process the dflt.mvw and then start all the threads of a certain view.
  
  Hmmm: that could be fun! 😉
  
  Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
- March 17, 2010 at 3:24 pm #71053
  Tom Rioux
  Participant
  Kevin,
  
  Open up the NetMonitor and start/stop the threads in a view from the view pane. If you have “Command and Engine Output” checked, then you can see the command that is given when you attempt to start or stop via a view. You won’t like what you see. Basically, it is the hcicmd command with all of the threads in the view separated by commas.
  
  hcicmd -p -c “,, , pstart”
  
  Tom Rioux
- March 17, 2010 at 3:34 pm #71054
  Kevin Crist
  Participant
  in the script i am playing with i currently have:
  
  hcienginerun -p adts050 -s fr_affi_adt,fr_affi_adts
  
  What is the difference between that and the hcicmd way?? Or is there?
  
  Thanks.
- March 17, 2010 at 3:59 pm #71055
  Robert Kersemakers
  Participant
  I never heard of the -s option with hcienginerun. Did I miss this one while upgrading to a newer version or has this always been a valid option?
  
  With hcienginerun you can only start a process that is down, and at that time make sure certain threads are started as well, ignoring the auto-start settings of these threads.
  
  With hcicmd you can stop/start threads at any time, as long as the process is running.
  
  Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands
- March 17, 2010 at 4:25 pm #71056
  Kevin Crist
  Participant
  we are on 5.4.1. If we used this it would be after our monthly downtime bounce so all processes and threads would be down. We dont have anything that is set to AutoStart. And we start different ones first depending on the view we have them grouped in.
  
  below is from our documentation:
  
  hcienginerun
  
  Starts engine processes.
  
  Input: hcienginerun -p or hcienginerun -p [-h ][-s [, …] ] —
  
  Where:
  
  -p starts the indicated process.
  
  -h is the name of the remote host to run the engine on.
  
  -s is a comma-separated list of threads to start. This flag overrides the auto-start setting for the named threads and starts them upon process startup.
- March 17, 2010 at 7:08 pm #71057
  Bob Richardson
  Participant
  Greetings,
  
  We are an AIX 5.3 TL8 SP3 shop (soon to go to TL11) running CIS5.6R2
  
  and our operators have a procedure to shutdown a group of threads and then start them back up after our HIS (Epic systems) downtime ends.
  
  We have created a “NetView” in the NetMonitor gui for all of our sites that have an Epic systems’ interface. By selecting the view group, they can shutdown the entire group with one click; then start it back up again.
  
  Easy to configure and maintain.
  
  Has worked for years.
  
  See attachment for a sample.
  
  You need to right click in the left pane and select “create a new view”.
  
  The rest is intuitive.
  
  Hope this helps you.
Author

Replies

Viewing 5 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.