Integration Services Shell commands are not case-sensitive, but named data sources, user IDs, and passwords might be case-sensitive, depending on the operating system and the data source you are using. Enter the syntax exactly as shown in this chapter for each command. Keyword parameters can appear in any order.
The commands require semicolons and parameters such as data source name (DSN), code page (CODEPAGE), user ID (UID), and password (PWD) to separate the command into statements that indicate what kind of information you are providing; for example:
SETSOURCE "DSN=database;CODEPAGE=English_UnitedStates.Latin1@Binary; UID=Smith;PWD=password;"
You must separate the statements with a semicolon. The final semicolon is optional. Do not use semicolons as part of data source names, because Integration Services Shell recognizes semicolons as field separators. It is recommended that you use double quotation marks around the parameters, as shown in the preceding example.
In this guide, all optional syntax parameters are indicated by their enclosure in brackets [ ]; however, do not type the brackets when you enter the commands.
Press Enter to execute the commands.
If you are unsure of a specific syntax, use Integration Services Console to schedule member or data loads, or to create load scripts. An Integration Services Shell batch file and a corresponding .cbs file are created automatically in the eis\server\Batch directory. You can reference, modify, and reuse the .cbs file for future member and data loads. In the Schedule Essbase Load dialog box, be sure to check the Save Script Only option instead of the Schedule option. See Recording Member and Data Load Scripts. |