Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Requirements for starting

DBH

Before you start SESAM-DBAccess, the DBH of SESAM/SQL-Server must be booted.

SESAM/SQL configuration file

To operate the DBAccess Server you need a SESAM configuration file. This file must be created by the administrator. Its default name is SESDA.SESCONF. If the name has been changed, the new name must be entered in the initialization file (see section "Initialization file (start parameters)"). The SESAM/SQL configuration file must contain the following information:

CNF=<c>
NAM=<n>
NOTYPE
PREFETCH-BUFFER=<pb>
CCSN=<ccs_name>

CNF and NAM are used to address the SESAM/SQL DBH. NOTYPE suppresses display on the console. PREFETCH-BUFFER specifies a buffer in 4-KB blocks, which is used for unchangeable results between the DBH and the server.

The CCSN operand defines the coded character set with which the values for columns that are declared in the database to be of the type NATIONAL CHARACTER or NATIONAL CHARACTER VARYING are to be interpreted. If the database referenced has a significant CCSN (i.e. not equal to *NONE), the database’s CCSN must be specified here. Otherwise communication with the database is not possible.

The contents of the SESAM configuration file can be modified during operation. Modifications to the SESAM configuration file apply to new tasks only. They do not apply to tasks that have already been started.

SESAM/SQL database access rights for clients

Users authorized to access the system via clients must be set up by the SESAM/SQL administrator (CREATE USER command) and they must be granted appropriate authorization (GRANT command).

A system entry must be defined for the users:

CREATE SYSTEM_USER ({hostname | *}, [*], {bs2000_userid | *}) FOR user AT CATALOG catalog

The variables hostname and bs2000_userid refer to the names of the host and the user ID under which DBAccess Server was started.

If clients are not using the authorization identifier of the Universal User, you must grant read authorization to DBAccess users in the tables SYS_UNIQUE_CONSTRAINTS, SYS_REFERENTIAL_CONSTRAINTS and SYS_INDEXES in the schema SYS_INFO_SCHEMA, e.g. as follows:

GRANT SELECT ON TABLE SYS_UNIQUE_CONSTRAINTS

TO PUBLIC

GRANT SELECT ON TABLE SYS_REFERENTIAL_CONSTRAINTS

TO PUBLIC

GRANT SELECT ON TABLE SYS_INDEXES

TO PUBLIC

Cancel authorization for clients

Clients can cancel their own SESAM/SQL requests. DBAccess Server must be authorized to execute SESAM administration commands via the SESAM-CALL-DML interface. This authorization must be entered for the host and the BS2000 user ID under which DBAccess Server is running.

You can grant authorization with the SESAM-DBH option

ADMINISTRATOR = *ANY(...)

or

ADMINISTRATOR = *TIME-SHARING-USER(...)

The administration password used must be entered in the SESAM-DBAccess INI file, in the section [Connect], key "SESAMAdmPass”.

BS2000 systems support

TP processes should be permissible for the BS2000 user ID and the job class under which DBAccess Server is running. In addition, the permissible program priority (RUN-PRIO) should be the same program priority entered in the SESAM-DBAccess INI file in the section [MainTask] and key “RunPrio” for batch jobs created with fork().