Automating your Essbase Cube - Oracle Essbase 9 Implementation Guide - page 285

• Substitution variables : Use these commands to manage any substitution
variables. Substitution variables are placeholders for information that
changes regularly. Use them in calc scripts, report scripts, and the
spreadsheet add-in to avoid hard coding.
• Aliases : These commands manage and, display the values of alias tables
for database outlines. Alias tables contain a listing of member names and
their alternate names, or aliases.
• Integrity and performance : These commands are used to check database
statistics and validate databases against possible corruption.
• Backing up : Use these commands to place one or more
Application|Databases into Read Only mode in preparation for archiving
or backup.
Well, there you have it! In a nutshell you have all of the Essbase command script
categories. For complete details on how to code each function and what task it
performs please refer to the Essbase Administration Services Information Map
that you access from the EAS Help menu pick. There you will find a complete
command list with specific details on how to code each function.
Coding a basic EssCmd
Even though you should no longer be writing new Essbase command scripts we
would remiss if we did not at least go over the basics. The following instructions
will guide you through writing a basic Essbase command script so you will have
at least a working knowledge level in case you need it.
Always remember EssCmd logging
First and foremost, in any EssCmd script is the inclusion of script logging. A good
output log is invaluable for helping to debug any problems.
The first line in any EssCmd script should be the OUTPUT command. This command
toggles on or off the script logging and also allows you to specify where to put the
log as shown here:
OUTPUT 1 "c:\EssCmd.log"; /* The 1 specifies turning job log output
on and then you code the log's location */