Some commands require that you precede object or file names with a numeric parameter, from 1 to 4, that tells ESSCMD where to look for the object or file. The parameter directs ESSCMD to look for files in other applications, databases, or systems.
The following table lists each value for the numeric parameter (numeric), the file location to which it applies, and the information that ESSCMD requests when you use each parameter setting. appName is the application name and dbName is the database name.
| Numeric | File | ESSCMD prompts for: |
|---|---|---|
| 1 | Local or client-based file | Windows: Files in the \ARBORPATH\CLIENT\appName\dbName directory. UNIX: Files in the $ARBORPATH/client/appName/dbName directory. |
| 2 | Remote or server-based file | Windows: Files in the \ARBORPATH\APP\appName\dbName directory. UNIX: Files in the $ARBORPATH/app/appName/dbName directory. |
| 3 | File | Fully-qualified path to the file, unless file is in the current ESSCMD directory. |
| 4 | SQL table | Full network and database information for the SQL table. |
For example, the LOADDATA command can load a data file that resides on the client computer or the Essbase Server computer. The command requires the numeric parameter to tell ESSCMD where to look for the data file. This example causes ESSCMD to prompt for the fully-qualified path name of the file to load:
LOADDATA 3
File extensions are usually optional in both interactive and batch processing modes, except when using commands that require a numeric parameter that indicates the location of files:
If you use file option 3 (File), you must enter the file extension in both interactive and batch processing modes.
If the object is in the directory from which you started ESSCMD, you do not need to enter a path.