Startup Script

Hi Garret,

We have all our threads on ‘Auto-start connection’, so when starting the process, all the related threads are started automatically. Never had any problems with that. We just made sure that when starting several processes back-to-back, there would be some time (10 or 20 seconds) between these startups. Because starting all processes at once didn’t work well.

I see you will start the Monitor Daemon, but you don’t start the Lockmanager, nor the Hostserver. But it all depends on when you want to use this script and therefore what you want it to do.

We have found there are situations where using auto-start gets in the way.

I don’t need to start any arguments about whose opinion has more merit but we started out with autostart but ended up deciding it was better to not allow any threads in production to be auto-start.

We also found maintaining static shutdown and startup scripts like you are working on requires they be kept up to date and that doesn’t end up happening when someone doesn’t follow procedure or over looks mainting them.

Of course with a smaller number of threads the problem may not exist but we have over 1200 threads so it motivated us to find a better more reliable less effort approach.

We too lived through the process just like you are doing now but felt like we had already learned to not fall back to using auto-start as the path of least resistance.

I would like to thank my co-worker Jim Kosloskey for influencing us to not lapse back into using auto-start because what we have now seems so much better.

So now we wanted granualarity of control and something that was dynamic and required no effot for us to maintain and would work if called by a HACMP fail-over event even if it wasn’t a gracefull shutdown but a hard fail-over.

What I did was to first write a script to take an intellegent snapshot of the current cloverleaf site and dynamically create the stop and start scripts for the current site in $HCISITEDIR/scripts and here is that script called mk_stop_start_scripts_for_current_site.tcl

#!/usr/bin/ksh
# this line to escape the next line from the tcl interpreter
exec hcitcl “$0” “$@”

# Begin Module Header ==========================================================
#
#———
# Purpose:
#———
#
# dynamically create the following scripts
#
# [code]#!/usr/bin/ksh
# this line to escape the next line from the tcl interpreter
exec hcitcl “$0” “$@”

# Begin Module Header ==========================================================
#
#

---

# Purpose:
#

---

#
# dynamically create the following scripts
#
#

I didn’t give specific examples because I didn’t want to get in a circular argument but since you asked I will give a quick one of the top of my head.

Yes turning off alerts is one of the steps I do as seen by the entry

turn_off_alerts.ksh; sleep 3

This is especially important when starting things up that might of been down for a while.

For us our alerts aren’t instaneous and take 5 or more minutes to trigger, so we haven’t had any issues with alerts firing during shutdown.

We have a restart script that we have been using for about 5 years, we schedule it in cron to start every night at midnight.  Basically it creates a list of sites, and goes through each site, shuts down the processes, then restarts the process.  

My problem is our site shutdowns and startups, whether initiated through the script or manually, are really sluggish.  I have had to increase the timeout a couple of times now.

Does anyone have any idea why this would be?  We are on version 5.3, on an AIX platform.  I am hoping for  a new server and cloverleaf upgrade this year, but need some help with this until them.

Any help would be greatly appreciated.

Gina

Here is the script ( list_sites.ksh ) I use to dynamically list and loop thru all the cloverleaf sites

#!/usr/bin/ksh

# Begin Module Header ==============================================================================
#
#——
# Name:
#——
#
# list_sites.ksh
#
#———
# Purpose:
#———
#
# List all the sites for the current $HCIROOT
#
#——–
# Inputs:
#——–
#
# none
#
#——-
# Notes:
#——-
#
# This script assumes the proper environment is set when it is called
# and all sites are symbolic links at the $HCIROOT level
#
#———
# History:
#———
#
# 2001.02.22 Russ Ross
# [code]#!/usr/bin/ksh

# Begin Module Header ==============================================================================
#
#

---

# Name:
#

---

#
# list_sites.ksh
#
#

---

# Purpose:
#

---

#
# List all the sites for the current $HCIROOT
#
#

---

# Inputs:
#

---

#
# none
#
#

---

# Notes:
#

---

#
# This script assumes the proper environment is set when it is called
# and all sites are symbolic links at the $HCIROOT level
#
#

---

# History:
#

---

#
# 2001.02.22 Russ Ross
#

Another way to grab a list of currently defined sites is from the file $HCIROOT/server/server.ini, in the line beginning “environs=”.

I actually use list_sites.ksh to set the environs variable in $HCIROOT/server/server.ini to create a sorted listing of sites in our IDE.

Here is the URL

<a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1424&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1424

posting the code for

set_server_ini_environs.ksh

mk_server_ini_environs.ksh

list_sites.ksh