The scripts that I am aware of for startup and shutdown of Domino are here (in order of increasing usefulness):
These have worked wonderfully over the years, but in RHEL 7 there has arisen a new problem. The sysvinit system has been replaced with systemd.
"No worries!" they claim. "Backwards compatibility" and all that. Right. The problem is, even if you install one of these scripts properly with chkconfig, systemd will NOT shut down Domino gracefully, but kill it and its child processes on shutdown or reboot. This means you're going through recovery and consistency checks after every server shutdown or reboot unless you remember to manually stop domino with "service domino stop" or "systemctl stop domino".
The solution is to set up a proper systemd service unit file and enable it. Since the nashcom scripts are the most useful in my view, I've included them in my example. However, you can use whatever script you want. The true issue here is that your script will NOT be used to shut down Domino unless you set up the directives right in your systemd service unit file. The most important directives are "KillMode=process" and "RemainAfterExit=yes":
Description=IBM Domino Server
NOTE: The LimitNOTFILE=60000 is where the ulimit goes now- it doesn't reside in your startup script as stated in IBM Technote 1221870.
In RHEL 7 or CentOS 7, this file should reside in /etc/systemd/system, for example /etc/systemd/system/domino.service
Enable your new service:
systemctl enable domino.service
Now, Domino will be properly shut down with the OS instead of SIGINT'd and you can start and stop Domino with "systemctl start domino" and "systemctl stop domino" respectively.