hcicyclesavemsgs (3.8.1P -> 5.3)

One suggestion would be to use a fully qualified path to hcicyclesavemsgs in the cron command in the same way that you are for the hcisetenv command.

If your cron job is not running as the same user as when you’re running manually, then cron’s environment “PATH” variable may be different

Traci,

Do you need to add “/hci” in front of /quovadx/qdx5.3/… ?

Sam

You could always just call a script from cron – that’s what I decided to do for our cyclesave.

My cron statment just calls:     /hci/scripts/cyclemsgs > /tmp/cyclemsg.log 2>&1

Then my cyclemsgs script sets the root and inititates the cycle of all desired sites.  If you try this route, just make sure permissions on the script are correct.

{cyclemsgs:}

#!/usr/bin/ksh

setroot /hci/qdx5.3/integrator

setsite prodmck

hcicyclesavemsgs -d -o 14

setsite prodsms

hcicyclesavemsgs -d -o 14

setsite prodepr

hcicyclesavemsgs -d -o 14

setsite prodtrans

hcicyclesavemsgs -d -o 14

Traci.

   Another problem you may be running into is the nature of the cron.  When you login to a unix box as a user, it automatically runs a .profile that sets up paths and environment variables.  When cron runs however, it does not run the .profile for the user it is running as.

  So you could have cron run as the same user you login as and the path and environment variables will not necessaraly be the same.

   Just like Mike, I have all my cron jobs run a shell script.  In the shell script I setup and env variables or path’s I need to run the commands in the script.  This also allows me to make modifications to the script without having to mess with the cron.