Referencing Files

Some commands require that you precede artifact or file names with a numeric parameter, from 1 to 4, that tells Essbase where to look for the artifact or file. The parameter directs ESSCMD to look for files in other applications, databases, or systems.

Table 253 lists each value for the numeric parameter (Number), 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.

Table 253. List of Numeric Parameters

Number

File

Essbase prompts user 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 or Essbase Server. The command requires the numeric parameter to tell Essbase 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 interactive and batch processing modes, except when using commands that require a numeric parameter that indicates the location of files: