CREATE LOGICAL SERVER Statement

Quick Links:

Syntax

CREATE LOGICAL SERVER <logical-server-name> [  
	 { ls-create-clause, ...} ] [ WITH STOP SERVER ]

ls-create-clause - (back to Syntax)
   { MEMBERSHIP ( { ls-member, ...} ) | POLICY <ls-policy-name> }

ls-member - (back to ls-create-clause)
   FOR LOGICAL COORDINATOR | <mpx-server-name>

Parameters

(back to top)

logical-server-name
any user-specified identifier except:
- ALL
- AUTO
- COORDINATOR
- DEFAULT
- NONE
- OPEN
- SERVER

MEMBERSHIP to define a logical membership to the coordinator, include FOR LOGICAL COORDINATOR in the MEMBERSHIP clause.
When no members are specified during the creation of a logical server, the logical server is created empty.

Note Implicit logical server membership definitions, such as those for OPEN and SERVER logical servers, are not stored at all.

The SYS.ISYSLOGICALMEMBER system table stores definitions for the logical server memberships.

Changing the ALLOW_COORDINATOR_AS_MEMBER option of the root logical server policy from ON to OFF does not affect the membership information stored in the catalog. Instead, it affects only the effective configuration of the logical server.

You can define a logical server membership to the current coordinator either by specifying the multiplex server name or by using the FOR LOGICAL COORDINATOR clause, even when ALLOW_COORDINATOR_AS_MEMBER option is set to OFF. Membership definition is stored in the catalog, but is inactive while that multiplex server acts as the coordinator.

The catalog stores the logical server and its membership definitions.

POLICY associates a logical server with a user-defined logical server policy. If no POLICY clause is specified, the logical server is associated with the root policy.
The SYS.ISYSIQLOGICALSERVER system table stores information about the logical server policy for a corresponding logical server.

ls-policy-name any user-specified identifier except ROOT.

WITH STOP SERVER
automatically shuts down all servers in the logical server when the TEMP_DATA_IN_SHARED_TEMP option is changed directly or indirectly.

Applies to

Multiplex only.

Examples

(back to top)

Example 1
creates a user-defined logical server< ls1> with three multiplex nodes as its members:
```
CREATE LOGICAL SERVER ls1 MEMBERSHIP ( n1, n2, n3 )
```
Example 2
creates a user-defined logical server< ls1> with three member nodes, and defines the logical server policy name < lsp1>:
```
CREATE LOGICAL SERVER ls1 MEMBERSHIP ( w1_svr, w2_svr, r2_svr ) POLICY lsp1
```
Example 3
creates servers as in Example 2, except that WITH STOP SERVER automatically shuts down all servers in the logical server when the TEMP_DATA_IN_SHARED_TEMP option is changed directly or indirectly:
```
CREATE LOGICAL SERVER ls1 MEMBERSHIP ( w1_svr, w2_svr, r2_svr ) POLICY lsp1 WITH STOP SERVER
```
Example 4
creates a user-defined logical server <ls1> with logical server policy <lspolicy1> and no member nodes:
```
CREATE LOGICAL SERVER ls1 POLICY lspolicy1
```
Example 5
where <n1> is the current coordinator, creates a logical server <ls2> with the named membership of multiplex nodes< n1> and <n3> and logical membership of the coordinator. Also sets the logical server policy of <ls2> to <lspolicy2>.
```
CREATE LOGICAL SERVER ls2 POLICY 
MEMBERSHIP FOR LOGICAL COORDINATOR 
lspolicy1, n1, n2, n3 POLICY lspolicy2
```

Permissions

(back to top)

Requires the MANAGE MULTIPLEX system privilege.