## Command File

### Definition

When you call the Loader with the Loader CLI, you can transfer the commands and SQL statements that are to be evaluated to the Loader. They are transferred in a special file, the command file.

### Use

If you want to call the Loader in command file mode, you have to specify the name of the command file by means of option –b <command_file>. You can, if necessary, transfer other options (options for establishing a connection, options for input and output, options for determining version information).

### Examples

loadercli -d demodb -u mona,red -n genua -b command.dat

The name of the database instance, database user information and the computer name are transferred via the relevant options. The commands and SQL statements are in the command.dat file.

The commands and SQL statements that you specify in the command file are individually processed by the Loader in the specified order.

For more examples, see the Loader Tutorial, Command File Mode.

### Structure

Note the following syntax rules for command files:

● General Syntax Rules

The same syntax rules apply as for calling the Loader.

● Separator Line Between Commands

Individual commands in a command file are separated by a line, at the beginning of which there is a double forward slash //.

When calling the Loader CLI, you can use the option –cs to define an alternative command separator (options for input and output).

● Comments

You can enter comments after a double forward slash // at the start of the line. The comments are ignored by the Loader when the command file is processed.

### Integration

A command file can also be generated by generating the design data in transport mode.