Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Passing control statements by means of an input file

You can pass the SESDCN control statements to SESDCN via an input file in either the batch or interactive mode.

Before starting SESDCN, you must assign the input file. There are several ways to do this. You can assign the input file:

  • as a SESDCN configuration file using the link name SESCONF

  • as a SYSDTA system file

  • as a global configuration file using the CONNECT-SESAM-CONFIGURATION command.

Assigning a SESDCN configuration file

You assign the SESDCN configuration file with the following command:

ADD-FILE-LINK LINK-NAME=SESCONF,FILE-NAME=filename

Assigning a SYSDTA system file as the input file

ASSIGN-SYSDTA TO-FILE=filename

In section “Examples of SESDCN parametrization”, you will find some examples of SESDCN input files.

Assigning a global configuration file

This global configuration file can contain configuration parameters for several components of the SESAM/SQL system (see "Entering the DBH start parameters for the independent DBH").

Notes on entering control statements

When entering SESDCN control statements, you must comply with a number of rules (which apply regardless of whether you are entering them in an input file, a procedure or interactively):

  • Each line must begin with the escape symbol (//).

  • Each control statement must begin on a new line.

  • If a control statement takes up more than one line, you must conclude each line with the continuation character (-); the last line of a control statement must not be concluded with the continuation character (-).

  • The parameters must be entered in a fixed order (see "SESDCN control statements").

  • The last line must contain an END statement; this END statement concludes input of the SESDCN control statements.

If one of the SESDCN control statements is invalid, SESDCN aborts and you receive an error message. A distribution rule is not generated.