John Viksne[SMTP:viksnej AT VNET.IBM DOT COM] wrote:
>Hi,
>
>This may be caused by set effective group id bit being on for 'dsmc'.
 Check
>the access permissions on the executable 'dsmc' and if it is on just
>do a chmod g-s dsmc.
>
>We took an APAR on this (IC12532).  The install proccess turned this
>bit on (it is needed for the HSM executables, but not the backup).
>It is still not clear why this prevents the change to the csh.    John
Viksne

I found a workaround.  Starting the script with #!/bin/csh -b allowed it to
work.  The shell is figuring that the script is not running with the same
real and effective user ids.  I was starting dsmc schedule by su-ing to
root, so that may have something to do with it.