It’s a bit rude of me to ignore Lawrence’s most recent posting, but I had been meaning to reply to Jim’s earlier post.
In general, I agree that it’s a beutiful thing that one can do a Cloverleaf upgrade install without having to even stop running processes in the older release. But I did want to mention one ‘gotcha’ I encountered this week when I installed 5.7 Rev 2 on our production server (we are currently running 5.4). The install makes changes to the /etc/environment file, changing a section from:
# begin HCIenv 5.4
FPATH=/quovadx/qdx5.4/integrator/kshlib
QUOVADX_INSTALL_DIR=/quovadx/qdx5.4
# end HCIenv 5.4
to this:
# begin HCIenv 5.7
FPATH=/quovadx/qdx5.7/integrator/kshlib
CL_INSTALL_DIR=/quovadx/qdx5.7
# end HCIenv 5.7
We have a small number of scripts that are called from crontab using a non-hardcoded method to set the hci environment, basically just executing ‘setroot’ w/ no parameters, then executing the script. As soon as the install changed the FPATH variable in the environment file to point to 5.7, that’s where the script started looking, even before hcisetenv had been copied to the qdx5.7 directory, or before execute permissions had been set.
We have most of our other crontab jobs using a hard-coded method to set the hci environment, like:
15 19 * * * /usr/bin/ksh -c ‘eval `/quovadx/qdx5.4/integrator/sbin/hcisetenv -root ksh /quovadx/qdx5.4/integrator cloprod3`;
And these jobs started failing in the 5.4 environment because:
“QUOVADX_INSTALL_DIR is not set. Exit.”
So once the install was completed I edited the /etc/environment file to be:
# begin HCIenv 5.7
FPATH=/quovadx/qdx5.4/integrator/kshlib
CL_INSTALL_DIR=/quovadx/qdx5.7
QUOVADX_INSTALL_DIR=/quovadx/qdx5.4
# end HCIenv 5.7
This seems to be keeping our crontab jobs running happily in the 5.4 environment for the time being, and later we will have to pick a point in the migration where we point FPATH back to 5.7.
.
