The Take Action command scripts are updated to include environment variables that access and reference new encryption libraries and paths. Also, UNSET statements pass default values from the runtime agent to the Take Action command scripts.
### set RAS1 tracing
export CTIRA_LOG_PATH=|CANDLEHOME|/logs
export KBB_VARPREFIX='%'
export KBB_RAS1_LOG='%(CTIRA_LOG_PATH)/aquarius_sa_
%(SAPSYSTEMNAME)_%(syspgm)_%(sysutcstart)-.log
INVENTORY=%(CTIRA_LOG_PATH)/aquarius_sa_%
(SAPSYSTEMNAME)_%(syspgm).inv COUNT=03
LIMIT=5 PRESERVE=1 MAXFILES=9'
export KBB_RAS1='ERROR'
export LD_LIBRARY_PATH=|CANDLEHOME|/|BINARCH|/sa/lib:|CANDLEHOME|
/|ARCHITECTURE|/lib:|ICCRTE_DIR|/lib
export LIBPATH=|CANDLEHOME|/|BINARCH|/sa/lib:|CANDLEHOME|
/|ARCHITECTURE|/lib:|ICCRTE_DIR|/lib
export SHLIB_PATH=|CANDLEHOME|/|BINARCH|/sa/lib:|CANDLEHOME|
/|ARCHITECTURE|/lib:|ICCRTE_DIR|/lib:/lib:/usr/lib
export ICCRTE_DIR=|ICCRTE_DIR|
export KEYFILE_DIR=|CANDLEHOME|/keyfiles
During the upgrade process, the default wrapper scripts, ksar3 and ksanfy, are updated for all of the environment variable and UNSET statement changes. If you are using the default wrapper scripts, the only changes you must make are for updated password values if you included these values in the wrapper scripts.
If you made copies of the default wrapper scripts, your copies are not updated during the upgrade process. You must make all the updates manually. Compare the updated 6.2 wrapper scripts with your scripts to determine the changes that you need to make.
If you included encrypted passwords in the wrapper script files, you must update these encrypted passwords also to avoid locking your SAP system user ID. Use the ksapwd utility after upgrade to encrypt your password. If your wrapper script includes the encrypted password, then copy the new encrypted password into the wrapper script. If your wrapper script is using a password file, regenerate the password file with the ksapwd utility.