Hi *SM-ers!
I have installed the new Linux 3.7 client on a Linux Suse 6.2 machine which
was running the ADSM 3.1 client before.
Normally I would start the scheduler by issuing the command:

nohup /usr/adsm/dsmc sched 2> /dev/null &

This worked fine with the ADSM client, but when I use this command with the
TSM client it doesn't return the prompt afterwards. When I press enter
again, the prompt returns along with the following message:

[1]+  Exit 127                nohup dsmc sched 2>/dev/null

The scheduler is stopped and the backup is missed.
Does anybody know why the TSM scheduler can't be started in the background
no more?
Thank you very much for your reply in advance!
Kindest regards,
Eric van Loon