xpserver

Syntax

xpserver -S XP_Server

xpserver
 -SXP_Server
	[-Iinterfaces_file]
	[-ppriority]
	[-sstack_size]
	[-u]
	[-v]
	[-x]

Parameters

-S XP_Server – specifies the name of the XP Server to start. The format of the XP server name is SQLSERVERNAME_XP, where SQLSERVERNAME is the name of the SAP ASE server to which the XP Server is dedicated. For example, the XP Server for an SAP ASE server named SMOKE would be named SMOKE_XP. The XP Server name must be in uppercase.
-I interfaces_file – specifies the name and location of the directory containing the interfaces file (sql.ini) that the SAP ASE server searches when connecting to XP Server. If you do not specify -I, xpserver uses the ini subdirectory of the %SYBASE% release directory.
-p priority – specifies the priority of the Open Server process. Values between 0 (lowest) and 15 (highest) are valid. Overrides the esp execution priority configuration parameter. The default is 8.
-s stack_size – specifies (in bytes) the stack size of the process used to execute an extended stored procedure (ESP). Overrides the esp execution stacksize configuration parameter if it is set. The default is 34816 bytes.
-u – specifies that the functions be automatically unloaded from XP Server memory after the ESP request terminates. Overrides the esp unload dll configuration parameter if it is set. The default is not to unload the function.
-v – prints the version number and copyright message for XP Server and then exits.
-x – specifies that the client security context be used to execute operating system commands using the system ESP, xp_cmdshell. Overrides the xp_cmdshell context configuration parameter if it is set. The default is to use the security context of the operating system account of the SAP ASE session.

Usage

When you run xpserver in root, xpserver automatically enables secure access on the machine as if you set the xp_cmdshell context configuration parameter to 1, thereby preventing users from accessing the SAP ASE server unless they are also valid users on the machine.
XP Server is normally started automatically by the SAP ASE server. Use the manual command to start XP Server only when instructed to do so in an “XP Server Failed to Start” error message.
There can be only one XP Server per SAP ASE server. An SAP ASE server running ESPs communicates with a single XP Server, and the ESPs execute synchronously.
The -p parameter affects the priority used by the Open Server scheduler. If -p is set to a high number, the scheduler can run XP Server before running the other threads in its run queue. If -p is set to a low number, the scheduler can run XP Server only when there are no other Open Server threads in its run queue. This parameter is unrelated to the application queue priorities within SAP ASE, which are set by sp_bindexeclass.

See the discussion of multithread programming in the Open Server Server Library/C Reference Manual.
If automatic unloading of ESP functions is not set by the -u parameter or by the esp unload dll configuration parameter, unload them at runtime using sp_freedll.
Unlike an SAP ASE server and Backup Server, XP Server does not have a runserver file.
When configuring an XP Server, the directory service entry name must end with “_XP” in upper case, such as “abcdef_XP” or “ABCDEF_XP.”

Permissions

No special permissions are required to run xpserver.