uma via cron or at

[Phil Daws_2]

Hi all:

I have a script that executes the following :

echo "stat d" | /opt/omni/lbin/uma -ioctl /dev/rac/c16t0d4

This runs fine from the command line. If I execute it via cron or at it fails and produces gunk eg.

)0 UMA HP OpenView OmniBack II A.04.00V15 [12:1] [2004] 1009536120 UMA dcsux101 [90:13] (unnamed) (unnamed)61]15 [12:1] [2003] 1009536120 UMA dcsux101 [90:28] Details unknown. (unnamed)V15 [12:1] [2004] 1009536120 UMA dcsux101 [90:19] (unnamed) (unnamed)1

I presume it is because uma is expecting to be associated with a tty device. Is there a way around this? I have checked the environment when run inside cron and outside and it is the same.

Ideas on a postcard please?

[garel · Accepted solution]

Hi,

OmniBack II 2.50/2.55 has an enhanced uma for remsh and cron
functionality, which uses the option -tty. For example:

/opt/omni/lbin/uma -tty -ioctl /dev/hsm/jukb1 /ROOT/umalog 2>&1

See the man pages for more details.

regards