Hot Diggety! Prather, Wanda was rumored to have written:
> This always works for me:
>
> nohup dsmc sched 2>&1 >/dev/null  </dev/null &

Alternatively, drop this one liner in /etc/inittab on an AIX system:

dsmc::respawn:/usr/bin/dsmc sched -password=quiet >/dev/null 2>&1

(It is usually preferrable to put this at or near the very end of the file)

Then do:

# kill -HUP 1

(to make inittab aware)

Subsequently, if you want to force the scheduler to update, it's just a
matter of kill -9'ing the 'dsmc sched' process ID and inittab would
automatically respawn a fresh copy of the dsmc scheduler.

For instance:

# kill -9 `ps -ef|grep '/usr/bin/dsmc sched'|grep -v grep|awk '{print $2}'`

This general approach works if you've got the client password stored as an
encrypted hash in a file locally... if you have a setup that requires
someone to manually enter the password every time, then this may not be a
suitable approach (use of inittab to respawn).

-Dan