Opening a Session: Loader CLI Options 
You can call Loader using the Loader CLI Client (LOADERCLI). By specifying the corresponding options, you can make various settings, including the settings in operating mode and transfer connection information.
Procedure
You can specify options when you call Loader CLI:
loadercli [<options>]
Call up the help function to get an overview of all options:
loadercli -h
Operating Modes
Imports to Loader can be made in three different operating modes: interactive transport mode, command file mode and session mode.
In transport mode, interactive entries are prompted by the user in order to export application data from one database and import it into another database. The input parameters and the loader configuration file are used to generate and execute the syntax of the loader commands. The generated Loader commands are optionally displayed on the console. The user can then use them as templates for custom commands. No knowledge of the loader syntax is required in transport mode.
In command file mode, a command file written by the user is processed sequentially. Unlike in transport mode, the command file can contain any sequence of Loader commands and SQL statements. In most application cases, the Loader commands generated in transport mode only need to be slightly modified to create a command file.
In session mode the user can transfer the Loader commands and SQL statements to Loader directly via the console.
As of SAP MaxDB version 7.7, the Database Studio database tool provides a GUI for Loader (Database Studio, Importing, Exporting, Transporting Data or the Database Catalog).
Setting up the Operating Mode: Loader CLI Options
The option required for determining the desired operating mode always has to be specified.
-p [<package_name>] |
Loader CLI transferred into transport mode if you specify option –p. More information: Transport Mode |
-b <command_file> [<connect_options>] [<in_output_options>] [<version_options>] |
Loader CLI is transferred into command file mode if you specify option –b. More information: Command File Mode |
[<connect_options>] [<in_output_options>] [<version_options>] |
Loader CLI is transferred into session mode if you specify neither option –p nor option –b. More information: Session Mode |
Further Loader CLI Options
-d <database_name> |
Name of database |
-u <database_user>[,<password>] |
Name and password of database user |
-n <database_computer>[:<port>] |
Name of database computer |
-s <schema_name> |
Name of schema |
-e <encryption> |
Encryption method |
More information: Opening a Database Session: Loader CLI Options
-o[w|a] <file_name> |
Name of output file |
-cs <separator> |
Command separator |
-ps<number> <string> |
Substitution parameter |
-E <number> |
Maximum number of errors allowed |
More information: Input and Output: Loader CLI Options
-V |
Version of Loader server |
-v |
Version of Loader CLI |
-R <dependent_path> |
Directory containing the programs that are dependent on the version of the database software |
More information: Determing Version Information: Loader CLI Options
Result
Before connecting to the database, Loader CLI evaluates the relevant options. Loader then executes the Loader commands and SQL statements in the command file (or those entered interactively). In all three operation modes, Loader writes a log file and, if appropriate, additional information (Loader Log File, Loader Log Functions).
If errors occur when Loader commands or SQL statements are processed, the way in which Loader responds depends on the operation mode in which it was used.
Transport mode: Loader stops processing the Loader commands and SQL statements when an error occurs. Detailed information is written to log files. For the export and import, the errors are written to the log file. With transports, there is a separate log file for the export and the import.
Command file mode: After a defined number of errors, Loader stops processing Loader commands and SQL statements and closes. You can use the option –E to define the number of errors that Loader ignores before it stops processing commands. If you do not use the option –E, Loader stops running after the first command with an error. You cannot react to the errors when you are using Loader CLI.
Session mode: Loader reports the error that has occurred and then awaits further input for processing.
If you want to respond to errors, the Loader functions are available as a library for the Perl and Python script languages: Perl Manual, SAP::DBTech::loader Module, Python Manual, sdb.loader Module.
Example
Loader Tutorial, Transport Mode, Command File Mode, Session Mode