Maxl/esscmds on unix : hiccups

Question

im kinda doubtful if the environment variables have to be set in the script if the path is already set in the .profile in essbase.should i set the server ,user and password for eg :server =xyzexport server etc i also feel i have a problem with setting the user as changes are not reflecting in the root.also what is the best way to create a maxl or an esscmd script in unix for scheduling.

Answer 1

This is an excerpt from a script to enable logins after a nightly archive process:############################################################# Backup the old enable log file and start a new log file. #############################################################mv ${LOG_PATH}/${DB_NAME}_enable.log ${LOG_PATH}/${DB_NAME}_enable.log.bak >${LOG_PATH}/${DB_NAME}_enable.logESSCMD << end_esscmdOUTPUT 1 "${LOG_PATH}/${DB_NAME}_enable.log"IFERROR "quit_scr";LOGIN "${SERVER}" "${USER_ID}" "${USER_PWD}";IFERROR "quit_scr";ENABLELOGIN "${APP_NAME}";:quit_screxit;end_esscmd################################################### Log a message if the script fails at any point ###################################################$COMMON_SCRIPT_PATH/chkstat.sh ${LOG_PATH}/${APP_NAME}_enable.logif [ $? != 0 ]then(and so on)##################################################many of the variables are set in the user's profile as part of the connection, others are set in other places of the script. Because it's Unix, the script doesn't have to have any specific extension, as long as it's been marked as an executable. The syntax here shows how the inline code allows the script to be interpreted and fed to the esscmd processor without creating a separate file.As for scheduling, chron works, other things may work better. That's between you and your support department to work out.Good Luck,-Doug