Because of the current implementation the adsm client running in
schedule mode cannot be started as a "real" deamon.
Digital Unix and also HP/UX 10 have a new style of system
startup-sequence in /etc/inittab            ( / is slash )

Digital Unix:
s2:23:wait:/sbin/rc2 < /dev/console > /dev/console 2>&1
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1

HP/UX 10
sqnc::wait:/sbin/rc </dev/console >/dev/console 2>&1 # system init

That means the shell-scripts to be started at boottime are located in
directory /sbin/rc2.d
A shell-script set up this way to start dsmc sched does not work !
To start dsmc sched at boot-time it needs an entry in
/etc/inittab directly.

Digital Unix:
s2:23:wait:/sbin/rc2 < /dev/console > /dev/console 2>&1
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
adsm::respawn:/usr/bin/dsmc sched -quiet >/dev/null 2>&1

HP/UX 10
sqnc::wait:/sbin/rc </dev/console >/dev/console 2>&1
adsm::respawn:/usr/bin/dsmc sched -quiet >/dev/null 2>&1

This limitation will be fixed in Version 3 of ADSM.



Best best regards,

Markus Fehling                    Internet: fehling AT vnet.ibm DOT com

ADSM Client Development
55131 Mainz
Germany