>Here is the response from IBM. TSM commands from CRON are not supported.

What on earth does *that* mean?  Cron is simply running as the designated
username; and if your environment has settings equivalent to an
interactive session, and your Stdin/Stdout/Stderr are likewise, then
I don't see an issue.

For progressive analysis, issue one of those TSM commands in the background of
an interactive session (dsmadmc ... &), with redirected Stdin/Stdout/Stderr and
see what happens.  If a cshell, capture the output of 'set' and 'env' commands,
or the like in other shells, mostly to assure that the proper username is in
effect.  That's pretty close to cron invocation.  Then do much the same in an
'at' or 'cron' job.

  Richard Sims, BU