PUBLIC

SySAM 2.4
Document Version: 1.0 – 2018-07-25

SySAM Users Guide

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Before You Generate Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 SySAM License Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Comparing the License Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Using SAP Products When the License Server is Offline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How SySAM Checks Out Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Common License Deployment Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Served License Deployment Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Installing the SySAM License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Platform Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Understanding the SySAM Directory Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 SySAM Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Using SySAM Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 Determining Host IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Finding the Host ID for a Physical Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Finding Host IDs for Machines with Multiple Network Adapters. . . . . . . . . . . . . . . . . . . . . . . . . 20
Using Alternate Host IDs on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

2 Generate License From SPDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.1 Generating Served Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
2.2 Generating Unserved Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3 Regenerating, Renewing, and Rehosting Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Managing License Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Modifying Individual Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3 Generating License Keys from SAP Service Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 License File Content Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.1 Served License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 Unserved License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.3 License Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.4 License Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5 A Three-server Redundancy License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5 Virtual Machine, Partition, or Sub-capacity Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

5.1 Configuring SySAM Sub-capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
5.2 sysamcap Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Example - Licensing a Machine to Allow Any Number of VMware Virtual Machines. . . . . . . . . . . . 34
Example - License an Individual Logical Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SySAM Users Guide

2 PUBLIC Content
 Example - Licensing a Solaris Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.3 SySAM Sub-capacity Glossary of Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6 Administering License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6.1 Starting and Stopping License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Manually Starting and Stopping License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

6.2 Determining License Server Version and Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6.3 Monitoring License Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

6.4 Registering New and Updated License Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

6.5 Managing the License Server Debug Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.6 Controlling License Use with the SySAM Options File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.7 Borrowing Licenses for Offline License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Borrowing Licenses Using lmutil lmborrow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Returning a Borrowed License Before It Expires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

6.8 Configuring SySAM for Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring a Three-Server Redundancy Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Using Multiple License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.9 Access Through a Firewall or VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

6.10 Running a License Server Automatically on UNIX Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7 Installing Product Updates and Support Renewal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

8 Migrating a SySAM 1 License Server to SySAM 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

8.1 Consolidating Multiple License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

9 Troubleshooting SySAM Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9.1 Where to Find License Error Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9.2 Problems and Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

When the Installer or Product Cannot Find a Valid License. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

When the License Server Fails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

When a Product Cannot Find License for Optional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Problems With Unserved License Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Problems With Served License Deployment Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

9.3 Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

9.4 Contacting Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SySAM Users Guide

Content PUBLIC 3
1 Before You Generate Licenses

Have the necessary information available before generating licenses.

Table 1: Information Needed Before License Generation

Required Information or Ac­ Served Li­ Unserved Li­

tion cense Model cense Model Description

License deployment model X X Decide whether to use a served or unserved license deploy­
ment model.

Typically, this is a company-wide decision that is made only

once. Therefore, this is one of the most important things to
determine before license generation.

Product machine host ID X Determine the host ID of the machine, or machine partition
where the product will run.

License server – download and X Download the standalone license server software and install
install the SySAM license server before you generate the product’s
licenses, and before you install the product.

License server host ID X Determine the host ID of the machine where the license
server will run.

License server host name X Determine the host name of the machine where the license
server will run.

License server TCP/IP port X Determine the port numbers on which the license server will
numbers listen for license requests.

 Note

If you do not specify the license server port numbers during license generation, the license server uses the
first available ports in the range 27000 to 27009. If a firewall exists between the server and the client
machines, fix the license server port numbers to allow access to the ports. See Access Through a Firewall
or VPN [page 47].

1.1 SySAM License Deployment Models

Before you generate licenses for SySAM 2 enabled products, determine the license deployment model.

● The served license model – licenses are deployed to one or more SySAM license servers. Using a license
server simplifies and centralizes license administration if you run products on more than several machines,
as doing so provides more control over software assets.

SySAM Users Guide

4 PUBLIC Before You Generate Licenses
● The unserved license model – you generate and download a separate a separate license for each machine
where the product runs.

1.1.1 Comparing the License Deployment Models

Compare the characteristics between the served and unserved license models to determine which setup works
best for your environment.

Unserved Served

Licenses are used only on the machine for which the license Licenses can be distributed from a network license server to
was generated. products running on any machine on a network.

Obtain licenses and save them individually on the machines Obtain licenses and save all of them on the license server
where the products will run. host machine.

License administration is not required. However, when new License administration is required. When new licenses are
licenses are required for product updates, you update and required for product updates, you update all licenses for a
deploy each license for each machine where the product up­ specific license server in a single step.
date will run.

Licenses are installed locally and always available. Requires a functioning license server and network. If either
of these fails, you install an alternate license server or fix the
problem before the product grace period expires.

If a machine where the product is running fails, you regener­ If a machine where the product is running fails, you move the
ate all of its licenses and deploy those licenses to the re­ product to a new machine, where it acquires licenses from
placement machines. the running license server.

If the license server host machine fails, the Manage License

Hosts functionality at SMP or SPDC allows you to move its
licenses to a new network license server host.

License files are distributed across each machine running a License files are centrally located and managed.
product, and therefore are difficult to manage and control.

Unserved Standalone Seat (SS) licenses do not allow prod­ You can use products via Remote Desktop Connection or
uct use via Remote Desktop Connection or other terminal other Terminal Services clients, irrespective of the type of li­
services clients. cense in use.

1.1.2 Using SAP Products When the License Server is Offline

Even when a SySAM-enabled product is disconnected from its license server, SySAM allows you to borrow
licenses for your product to work offline.

To use your SySAM-enabled product offline or while it is disconnected from the license server, you borrow
licenses for a specified period of time. You can use the licensed product offline until the borrowed licenses
expire.

SySAM Users Guide

Before You Generate Licenses PUBLIC 5
When borrowed licenses expire, you reconnect to the network license server and borrow them again for the
product to work offline. If you do not reborrow licenses before your currently borrowed licenses expire, the
product runs only for a runtime grace period, then ceases to function.

 Note

Typically, the maximum duration for which you can borrow a license is 90 days.

Related Information

Borrowing Licenses for Offline License Servers [page 43]

1.1.3 How SySAM Checks Out Licenses

SAP SySAM related products check out licenses on start-up, and perform periodic heartbeat checks to verify
that licenses remain available. If a license is unavailable, the product determines whether it can be awarded a
grace period.

The grace period starts from the time a license was last in use and persists for 90 days. At the end of the grace
period, the product performs an orderly shutdown, if running, or fails to start up. If the license (or a
replacement license) becomes available, the cycle continues with the heartbeat, noting the last use of the
license.

1.1.3.1 Three License Server Redundancy

Tolerance for temporary licensing failure is usually sufficient. However, in certain circumstances, you may
choose to use “three-license-server redundancy.”

This tolerance for temporary licensing failure is usually sufficient. However, in certain circumstances, you may
choose to use “three-license-server redundancy.” For example:

● A grace period is not provided for Floating License (FL) type licenses.
● Standby copy systems rarely qualify for a grace period because they are unlikely to have been used within
the last 30 days.
● Company policy dictates the use of redundancy.

For three-license-server redundancy, use three machines that each:

● Run the same version of the SySAM license server.

● Have good intermachine communication.
● Use a separate copy of the same license files.

A product that uses per-processor licensing checks out a license quantity equal to the number of processors it
can use, or awards runtime grace if there are not enough licenses. A runtime grace period is also awarded if the
number of processors is dynamically increased while the product is running and the product is unable to check

SySAM Users Guide

6 PUBLIC Before You Generate Licenses
out additional licenses. The product shuts down if additional licenses are not made available within the runtime
grace period. Decreasing the number of processors that a product can use while it is running does not reduce
the required license quantity; restart the product on the correct number of processors.

Related Information

Configuring SySAM for Redundancy [page 45]

1.1.3.2 Knowing the Product License Type

Products are sold under different license types, which entitle the customer to different rights of use such as
whether a product is licensed for used in production, standby, or development and test environments.

The license type determines the quantity of licenses required, such as whether a license is required for each
machine; or for each CPU, or CPU chip; or per terabyte of storage.

For example, a product purchased under the CPU License (CP) type requires one license per CPU on the
machine, partition, or resource set where it will run. The same product purchased under the Server License
(SR) type requires a single license for the machine, partition, or resource set.

Make sure you select the correct license type when you generate your SySAM license file, since your account
may have the same product licensed under multiple license types.

When you generate licenses, each license type is presented on the License Information screen, such as:

License Type: CPU License (CP)

1.1.3.2.1 Optional Feature Licenses

Some applications are offered as base products with optional features that require an additional separate
license.

You can mix license types. For example, you can order SAP ASE under the Server License (SR) license type and
order an optional feature (such as, High Availability or Enhanced Full Text Search) under the CPU License (CP)
type.

Optional features are licensed only with the base product of the same product edition. For example, if you order
SAP ASE, you cannot use a Small Business Edition optional feature license with the Enterprise Edition base
product. In addition, the entitled use of the license types must be compatible; for example, both types should
allow use in a production environment.

SySAM Users Guide

Before You Generate Licenses PUBLIC 7
1.1.4 Common License Deployment Scenarios

Learn about some typical license server deployment scenarios and suggestions for a SySAM setup that best
serves each scenario. You can mix and match the suggested configurations with other variations, to best suit
your needs.

1.1.4.1 Small Environment, Unserved Licenses

The easiest setup for this environment is to use unserved licenses, which have a simple initial setup and require
little, if any, ongoing monitoring.

This deployment scenario uses an unserved license deployment model that works best in:

● Very small environments using only a few license files that require little management. If you have more
than 10 hosts, it is probably better to move to a served license deployment model, since a served license
allows you to update all licenses in one step.
● Hosts that are isolated (or need to be isolated) from one network to another; for example, secure networks,
and so on.
● Secure environments, where communication between hosts is limited or restricted; for example, all ports
are blocked, or specific ports are not allowed to be opened on a host.
● Occasionally connected systems, such as laptops or handheld devices.

Figure 1: Small Unserved License Configuration

SySAM Users Guide

8 PUBLIC Before You Generate Licenses
The "Small Unserved License Configuration" figure illustrates a simple unserved license architecture with two
hosts: ASTRO and ELROY. Each license file is installed locally on the same machine that runs the SySAM 2-
enabled products that use that specific license file. The license is used only on the machine on which it is
installed. In each license file representation, the license file HOSTID matches the unique license host
identification for the machine on which the associated licensed product is installed.

To get this information, run lmutil hostid from the $SYBASE/SYSAM-2_0/bin directory, on each machine
for which you want to determine the host ID.

When you log in to the SPDC or SAP Support Portal to generate licenses, enter the correct host ID for the
machine where the product will run.

When using an unserved license, remember that:

● The unserved license is valid only on the machine for which it was generated. The license is node-locked to
the host where your SySAM 2-enabled product is installed, and the license activates products only on that
host. You cannot copy the license file to another machine and use it to run another instance of a product.
● The unserved license deployment model does not use a license server. When you start a product, it looks
for a local license file.
● You must manage unserved licenses, regardless of the architecture in which they are implemented. Most
licenses have a version that usually coincides with the end of your annual support agreement with SAP.
To download and apply product updates and patches, when you renew your product support, update your
SySAM licenses to reflect that fact. Renewing support and updating the corresponding license files on a
few hosts is not difficult, but trying to update 100 or 1,000 hosts would be a formidable task.

Related Information

Borrowing Licenses for Offline License Servers [page 43]

1.1.4.2 Single Site with Multiple Products, Served Licenses

This deployment scenario assumes you have one site, running multiple products, that requires asset
management capabilities.

Typically, a served license with one license server that serves all SAP licenses works most efficiently in such an
environment. The overhead of maintaining the license server is compensated by the asset management
functionality and a reduction in ongoing license maintenance because of the license server.

SySAM Users Guide

Before You Generate Licenses PUBLIC 9
 Figure 2: Single-Site Served License Configuration

The "Single-Site Served License Configuration" figure shows one license server that is set up to grant SySAM
licenses to all SAP products in use. Each instance of a product contacts the license server to acquire a license.

You can set up the license server on a separate host machine, but because the license server uses few
resources, it can typically be hosted on an existing machine.

SySAM Users Guide

10 PUBLIC Before You Generate Licenses
1.1.4.3 Multiple Sites with Security Considerations and
Remote Users
This deployment scenario has multiple sites, each with multiple SAP products, with a license server at each
site. This removes the dependency on network availability and latency, and can provide load balancing.

Figure 3: Multiple Sites and License Servers

The "Multiple Sites and License Servers" figure illustrates an organization with major sites in New York, London,
and Tokyo. Each site uses multiple instances of multiple SAP products. A license server is installed at each site
and individual product instances acquire licenses from the license server at that site.

You can configure the products to find remote license servers if the required license cannot be found on the site
license server, or if the site license server is not running. To share a limited number of floating licenses across
all sites while using the site license server for other licenses, set up those floating licenses on the license server
where floating licenses are likely to be used frequently. At the other sites, you can set up license search paths.
The redundancy provided by this configuration is limited to the number of unused licenses, including any
overdraft licenses that remain on each license server.

You can also consider alternate configurations. For example, if the network communication between two sites
is extremely reliable with minimal latency, you can share a license server between two sites. Smaller remote
sites can share a license server with a larger site that provides the most reliable network connection, even
though the larger site may not be the closest site geographically.

This setup is an extension to the multiple site case explained above. It also addresses additional considerations
including security within your network, remote users, and DMZs. This setup uses a mix of license models and

SySAM Users Guide

Before You Generate Licenses PUBLIC 11
servers to meet your needs. Individual components of this deployment can be applied to any of the other
deployment scenarios.

Figure 4: Complex, Multiple-Site Installations

The "Complex, Multiple-Site Installations" figure depicts a multiple-site deployment with multiple product
setup with additional security requirements. In this example:

● The Headquarters network includes both development and production installations.

● The production installations are set up within a secure subnet within the network.
● The database and application servers that serve the Web are set up in the DMZ.
● Home office and mobile users access the software remotely through VPN.
● There is a disaster recovery center at a remote location.
● There are other secondary sites for the organization.

This example uses a single license server for Headquarters, which serves the development, production, and
remote users’ needs. While the license server is shared for development and production needs, available
licenses can be demarcated based on intended deployment.

● The production subnet security policies are relaxed to allow connections to the license server host and
port.
● The VPN policies allow a connection to license server host and ports.

SySAM Users Guide

12 PUBLIC Before You Generate Licenses
If your security policies do not permit the production subnet to access a license server outside the subnet, set
up a separate license server inside the subnet.

 Note

Use a fixed port for the lmgrd license manager and SAP vendor daemon in such situations. Firewall and
VPN policies must accommodate both lmgrd and SAP port numbers. This means that SERVER lines and
VENDOR lines in all license files must specify the port numbers chosen for the license manager and SAP
daemon processes. For example, a license server running on machine server_1 with the lmgrd license
manager daemon, listening on port 27001 and the SAP vendor daemon listening on port 27100 should use
a license file headed with the following two lines:

SERVER server_1 ANY 27001

VENDOR SAP PORT=27100

Unserved licenses are set up on the DMZ to serve licenses to product instances using the Web. This reduces
the need to set up another license server or open up additional traffic through the firewall.

SAP recommends that you use a separate license server for your disaster recovery site. This ensures
availability of the license server in case of a major catastrophe at the primary site.

If your disaster recovery setup includes cold-standby servers, set up the license servers in a three-server
redundant cluster. This reduces the possibility of a license server being unavailable when a cold-standby server
is attempting to come online. Such redundancy for license servers is typically not needed unless you are using
cold-standby systems.

Each secondary or remote site can have its own license server.

1.1.5 Served License Deployment Model

The license server is a lightweight application that serves licenses to products running on any operating
system.

When you choose the served license deployment model, licenses are deployed to one or more SySAM license
servers.

A license server can run on a low-end machine or a machine with spare cycles. For example, a license server
running on a Solaris UltraSparc-60 serving 100 different licenses to 200 product instances, may use 50 MB of
memory, 5 minutes of CPU time per week, and 100 MB of disk space per year.

After you install the required license servers and generate served licenses, install your products. You can
configure the products to obtain licenses from one or more license servers.

 Note

You cannot start the license server until there is at least one served license saved to the licenses
directory on the license server host machine.

SySAM Users Guide

Before You Generate Licenses PUBLIC 13
1.2 Installing the SySAM License Server

Install a license server on a machine other than that used by the product.

Context

In general, the product installer automatically installs the SySAM utilities; and also a SySAM license server
when you choose the full installation option, or enter a machine-local served license when prompted for the
SySAM license key.

A separate SySAM license server and utilities installer is provided to simplify installing the SySAM license
server and utilities on a machine or operating system other than that used by the product. For example, if you
install SAP ASE on Windows and intend to use a SySAM license server on Linux, you can use the SySAM
installer rather than download the complete SAP ASE for Linux media in order to only install the SySAM license
server.

If you choose to use the:

● Served license model – install the SySAM license server and the utilities.
● Unserved license model – you only need to install the SySAM utilities. The utilities alone are rarely needed
as they are installed by the product, but may be required for virtual environments. For example, to license
SAP ASE Small Business Edition for use in a guest VMware VM running the Windows Operating System,
you need to run the Linux version of the sysamcap utility on the ESXi console.

Procedure

1. To download the installation media, go to:

https://support.sap.com/software.html

2. Go to Software Downloads S Installations and Upgrades - S SYSAM SYSAM 2.4 Installation .

3. Select your operating system, then choose the installation package from the bottom of the page.
4. Extract the zipped installation files into a temporary directory.

○ On UNIX platforms, use the GNU tar (and optionally gunzip) utility.
○ On Windows, use the Zip program or Windows Compressed (zipped) Folders Extraction.
5. (UNIX) If you are installing a SySAM license server on UNIX into a directory that contains an existing
SySAM license server, execute:

SYSAM-2_0/bin/sysam configure none

6. Install:

○ Using the Graphical User Interface (GUI), execute:

○ UNIX: setup.bin
○ Windows: setup.exe

SySAM Users Guide

14 PUBLIC Before You Generate Licenses
 ○ Using console mode, ensure the DISPLAY environment variable is not set, launch the setup program
from a terminal or console, and execute:
○ UNIX: setup.bin -i console
○ Windows:setupConsole.exe -i console
7. If you installed a license server, ensure the machine has sufficient open file descriptors.

Concurrent client connections to the SySAM license server are limited by the operating system limit for the
number of file descriptors that one process can open.

Before starting the SySAM license server on UNIX, you should ensure that the number of file
descriptors configuration is set to a sufficient value. Use the ulimit command to set the file descriptor
limit in the shell where you start the license server. SAP recommends that you do this in the .sysamrc file
in the SYSAM-2_0/bin directory as that file is sourced by the sysam script. For example:
○ ulimit -n 1024
○ ulimit -H -n 1024

Next Steps

Determine the host ID, then obtain license files from SMP or from SPDC using the access information in your
welcome e-mail message.

Related Information

Administering License Servers [page 38]

1.2.1 Platform Support

A separate SySAM license server and utilities installer are available for download and available on these
operating systems.

● HP-UX Itanium 64-bit

○ HP-UX B.11.31 ia64
● IBM AIX 64-bit
○ AIX 6.1 ML 006
○ AIX 7.1 ML 000
● Linux x86-64 64-bit
○ RedHat Enterprise Linux 6, 7
○ SUSE Linux Enterprise 10, 11 and 12
● Solaris SPARC 64-bit
○ Solaris 10 and 11
● Solaris x64 64-bit

SySAM Users Guide

Before You Generate Licenses PUBLIC 15
 ○ Solaris 10 and 11
● Windows x86 32-bit
○ Windows 10
○ Windows Server 2008, including SP1 and SP2
○ Windows 8
○ Windows 8.1
○ Windows 7, including SP1
○ Windows Server 2012 R2
○ Windows Server 2012
● Windows x64 64-bit
○ Windows 10
○ Windows Server 2008, including SP1, SP2, and R2
○ Windows 8
○ Windows 8.1
○ Windows 7, including SP1
○ Windows Server 2012 R2
○ Windows Server 2012

 Note

Windows X64 requires the following patches:

● Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package and KB2565063
● Microsoft Visual Studio 2010 Service Pack 1 and KB2565057

Missing either of the above patches causes the installer to fail, and you see this message:

Missing DLL MSVCR100.dll during Install.

1.3 Understanding the SySAM Directory Structure

SySAM files are installed in the SYSAM-2_0 directory.

The SYSAM-2_0 directory contains these default subdirectories and files:

bin

● sysam – wrapper script to manage the license server

● lmgrd – license server manager daemon
● SYBASE – vendor daemon
● lmutil – licensing Utility program (from Flexera)
● lmtools.exe – (Windows only) GUI License Utility program (from Flexera)
● installs.exe – (Windows only) program used internally to install the SySAM Windows service that
automatically starts the license server
● cpuinfo – utility program that reports the processor counts for the machine, or for the specified
containment level if the SYBASE_SAM_CAPACITY environment variable is set

SySAM Users Guide

16 PUBLIC Before You Generate Licenses
● sysamcap – utility program used to configure sub-capacity licensing

licenses

● *.lic – license files

● SYBASE.opt – license server options file

locales

● unicode – localized message files for the sysamcap and cpuinfo utilities

log

● SYBASE.log – license server debug log

1.4 SySAM Utilities

The licensing utility program, lmutil, includes options for managing licensing activities.

The options available in lmutil are:

● lmborrow – supports license borrowing.

● lmdiag – diagnoses license checkout problems.
● lmdown – shuts down selected license daemons.
● lmhostid – reports the system host identifier for the machine on which the command is run.
● lminstall – (not supported by SAP) converts license files to different formats.
● lmnewlog – moves the existing report log information to a new file name and starts a new report log file
with the existing file name.
● lmpath – allows direct control over license file path settings. You should place all license files in the license
directory rather than scattering them and modifying the license server's search path.
● lmremove – releases the failed license to the pool of free licenses. If an SAP product is still using the
license, the product obtains the license again during its next heartbeat.
● lmreread – directs the license daemon to reread the license file and to start any new vendor daemons.
● lmstat – displays the license server system status.
● lmswitch – tells the license server to start writing to a new debug log file. When you restart the license
server, it uses the debug log file specified in the options file, so you must ensure the old log is renamed to
avoid appending to it.
● lmswitchr – switches the report log to a new file name. You should use lmnewlog to archive the report
log instead.
● lmver – reports the FLEXnet licensing version of a library or binary file.

SySAM Users Guide

Before You Generate Licenses PUBLIC 17
1.4.1 Using SySAM Utilities

Learn how to see a list of optional parameters of SySAM utilities.

Context

SAP does not support the functionality of all optional parameters.

Procedure

1. To see a full list, enter:

lmutil -help

2. To see a list of parameters for lmborrow, enter:

lmutil lmborrow -help

 Note

In addition, the sysam script, also located in the bin directory, provides a wrapper for the most
frequently used FLEXnet utilities. To display the help text, which provides complete instructions, enter:

sysam help

1.5 Determining Host IDs

Identify the host ID of the machine where the licenses will be deployed.

● For served licenses, specify the host ID of the machine where the license server will run.
● For unserved licenses, specify the physical host ID of the machine where the product will run.

If you are running a product with per-CPU or per-CHIP licensing that supports SySAM sub-capacity, and you
want to run the product in a virtualized environment, use the sysamcap utility to enter the host ID for the
virtual machine, partition, or resource-set.

SPDC or SMP remembers the host information so that you can select the same license server when generating
additional licenses.

SySAM Users Guide

18 PUBLIC Before You Generate Licenses
Related Information

Virtual Machine, Partition, or Sub-capacity Licensing [page 32]

1.5.1 Finding the Host ID for a Physical Machine

Use the lmutil utility or the appropriate operating system command to find your host ID.

If you do not intend to run your product in a sub-capacity environment, you must enter your physical machine's
host ID. To find your host ID, you can run the lmutil utility included in the SySAM software download or use
the appropriate operating system command.

To determine the host ID of the machine using lmutil, enter:

lmutil lmhostid

The type of host ID returned depends on the platform. The following table lists the host ID types used for each
platform along with the native OS command that can be used to obtain the host ID value:

Platform Host ID Type Native OS Command

Windows Ethernet Address ipconfig/all(use "Physical Address" value)

Solaris Host ID hostid

Linux Ethernet Address /sbin/ifconfig eth0 (use "HWaddr" value)

MAC OS X Ethernet Address /sbin/ifconfig eth0 (use "ether" value)

Tru-UNIX (Digital) Ethernet Address netstat -i

IBM AIX Host ID uname -m (returns 000276513100), then remove both the
first and the last two digits, and use the remaining eight dig­
its

HP-UX PA-RISC Host ID uname -i (convert to hex, or prepend with #)

HP-UX Itanium Machine ID getconf CS_PARTITION_IDENT (prefix with

"ID_STRING=")

SGI Host ID /etc/sysinfo -s (convert to hex, or prefix #)

 Note

For Windows platforms, if your machine does not have a network adapter an alternate host ID of type Disk
Serial Number is supported. See Using Alternate Host IDs on Windows [page 21].

Each host ID type has valid formats that will be checked when generating a license. Make sure the value
entered matches these valid formats.

SySAM Users Guide

Before You Generate Licenses PUBLIC 19
Ethernet addresses are 12 character hex values consisting of digits 0 through 9 and characters A through F.
They may be entered in any of the following formats:

● 12AB34CD56EF
● 12-AB-34-CD-56-EF
● 3.12:AB:34:CD:56:EF

Host IDs are entered in the exact value returned by hostid. For example: 00068df0

For some platforms, the host ID can also be entered in decimal formats, in this case prefix the host ID with the
"#" sign. For example: #1039716963

The Disk Serial Number is always entered with a "DISK_SERIAL_NUM=" prefix. For example:
DISK_SERIAL_NUM=3e2e17fd

The machine ID string is always entered with an "ID_STRING=" prefix. For example: ID_STRING=9c766319-
db72-d411-af62-0060b05e4c05

1.5.2 Finding Host IDs for Machines with Multiple Network

Adapters

On some platforms, the host ID is derived from the network adapter address.

Context

If the machine where your product is installed or where the license server is hosted has multiple network
adapters, running lmutil lmhostid returns one host ID for each network adapter, and returns output similar
to this:

The FLEXlm host ID of this machine

is ""0013023c8251 0015c507ea90""
Only use ONE from the list of hostids.

It is important that you:

● Choose only one host ID to enter during license generation.

● Use the value associated with the primary wired Ethernet adapter.
● Do not use values associated with internal loopback or virtual adapters.

If you cannot determine the host ID using the lmutil lmhostid output, use the native operating system
commands to get additional details.

SySAM Users Guide

20 PUBLIC Before You Generate Licenses
1.5.3 Using Alternate Host IDs on Windows

If your Windows machine does not have a network adapter, SySAM allows you to use an alternate host ID based
on the hard disk serial number.

Procedure

1. At a Windows command prompt on the machine where you will deploy your license, enter:

lmutil lmhostid -vsn

This returns output similar to:

The FLEXlm host ID of this machine is "DISK_SERIAL_NUM=70ba7a9d"

2. Use the complete output (DISK_SERIAL_NUM=70ba7a9d) for the host ID value requested during license
generation.

SySAM Users Guide

Before You Generate Licenses PUBLIC 21
2 Generate License From SPDC

If you purchased your product from Sybase or an authorized Sybase reseller, go to the secure Sybase Product
Download Center (SPDC) to generate license keys.

Context

Once you log in to SPDC and begin license generation, complete your product’s license generation using the
procedure that applies to the license deployment model you chose, either for generating served licenses or for
generating unserved licenses.

Procedure

1. Go to the SPDC login page at https://sybase.subscribenet.com .

2. Enter the login ID and password, then click Login. If you forget your password, click Password Finder and
your password will be sent to you in an e-mail message.

If you ordered your product from a reseller, enter the authorization string from the Web Key Certificate your
reseller provided, then select Submit Web Key. If you do not know your SPDC account login ID and
password, or Web Key Certificate authorization string, contact the person who ordered your product. At
the Web Key Registration page, enter your account information, then click one of these options:

○ Submit My Registration Information – to register your product using your direct account information.
○ Anonymous Activation – to activate your product anonymously.
3. Select the product family that includes the product for which you want to generate a license; for example,
SAP Adaptive Server Enterprise.
4. Depending on the product family you choose, you may see an additional Product Information page.
a. Product suites – if your product is included in one or more suites, select the suite that includes your
product; for example, ASE Small Business Edition.
b. Product version and platform – select the product version, name, and operating system that matches
your product order.
5. If this is the first time you selected a specific product edition and platform, accept the License Agreement.
6. If your product software installation requires a license key (also referred to as the license file), click License
Keys on the Product Download page.
7. On the License Information page:
a. Select the option button to the left of the product for which to generate a license; for example, “CPU
License (CP), ASE Enterprise Edition 15.7 for Oracle Solaris SPARC 64-bit.”
b. Scroll down and click Select to Generate.
8. In the Generate Licenses wizard, choose a license deployment model:

SySAM Users Guide

22 PUBLIC Generate License From SPDC
 ○ Served license – go to Generating Served Licenses [page 23] to complete the license generation and
download process.
○ Unserved license – go to Generating Unserved Licenses [page 24] to complete the license generation
and download process.

 Note

Some products or license types do not offer a choice of license deployment models and do not display
this page. If this is the case, continue through the Generate Licenses wizard to generate your license.

2.1 Generating Served Licenses

Generate and download a served license for your product.

Prerequisites

You have started the SySAM Generate Licenses wizard and selected served license.

Procedure

1. Enter the number of licenses to generate and click Next.

If you are unsure of the license quantity, select How Many Licenses Should I Generate?.
2. Select an existing license server host, or enter the host ID, and an optional host name and port number, of
a new license server host.

When completing this step, use these recommendations:

○ If you do not know the license server host ID, select What Is My Host ID?.
○ Although the host name is optional, SAP recommends that you provide the host name to ease future
license administration.
○ The port number is optional unless your product configuration is going to use three-server redundancy
(see the next bullet item). Any unused port number between 0 and 64000 is valid. On UNIX, choose a
port number greater than 1024; most port numbers less than 1024 are privileged port numbers. If you
do not specify a TCP/IP port number, a default port between 27000 and 27009 is used.
○ To generate a license for a three-server redundant configuration, enter the required information:
license server host ID, host name, and port number for all three machines. Enter a port number outside
of the 27000 to 27009 range. You must enter the fully qualified domain name (FQDN) as the host
name if any client machine requires an FQDN to contact a license server machine.

 Note

You cannot upgrade SySAM 1.0 licenses and use them in a three-server redundant configuration.

SySAM Users Guide

Generate License From SPDC PUBLIC 23
3. Select Generate.
4. When your license is generated, review the information for accuracy. To correct any information, select
License Overview, then choose the license to correct and select Check In. This resets the license to its
original state so that you can submit the correct information.
5. (Optional) Before you download and save generated licenses, you can select Print Friendly to print a paper
copy of the license, or License Overview to return to the License Information page and generate additional
licenses.
6. Download your license.
○ If you generated only one license, click Download License File.
○ If you generated several licenses, click Download All Licenses for Host.
7. Click Save.
8. Save the license files with a .lic file name extension to the $SYBASE/SYSAM-2_0/licenses (%SYBASE%
\SYSAM-2_0\licenses on Windows) directory on the license server.

 Note

If you do not save the license files with a .lic extension, SySAM does not recognize the licenses.

9. After you save the license files to the license server, register the new license(s) with the license server by
entering the following in a command prompt (Windows) or a shell window (Linux/UNIX) on the machine
where your license server is running:

sysam reread

Related Information

Determining Host IDs [page 18]

2.2 Generating Unserved Licenses

Generate and download an unserved license for your product.

Procedure

1. Enter the number of machines (up to 10) for which to generate unserved licenses, and click Next.
2. Enter:

○ Host ID – enter the host ID of the machine where the product will be run. If you do not know the host
ID, select What Is My Host ID?.
○ Host Name – enter the machine host name.

SySAM Users Guide

24 PUBLIC Generate License From SPDC
 For some license types, you must enter the number of licenses to generate. If you are unsure of the license
quantity, select How Many Licenses Should I Generate?.
3. Select Generate.
4. When your license is generated, review the information for accuracy. To correct any information, select
License Overview, then choose the license to correct and select Check In. This resets the license to its
original state so that you can submit the correct information.
5. (Optional) Before you download and save generated licenses, you can select Print Friendly to print a paper
copy of the license, or License Overview to return to the License Information page and generate additional
licenses.
6. Download your license.
○ If you generated only one license, click Download License File.
○ If you generated several licenses, click Download All Licenses for Host.
7. Click Save.
8. Save the generated licenses with a .lic file name extension. Although <$SYBASE> /SYSAM-2_0/
licenses is typically the directory where unserved licenses are located, your product may have a different
requirement. See your product installation guide and release bulletin for product-specific information.

 Note

If you do not save the license files with a .lic extension, SySAM does not recognize the licenses.

Next Steps

Install your licensed product using the instructions in the product installation guide and release bulletin.

Related Information

Determining Host IDs [page 18]

2.3 Regenerating, Renewing, and Rehosting Licenses

There are certain circumstances under which you might need to regenerate, renew, or rehost SAP licenses.

Context

Licenses are upgraded to the latest versions when:

● Your support contract is renewed. Updated licenses enable you to use the newest versions of the products
that become available during your support period.

SySAM Users Guide

Generate License From SPDC PUBLIC 25
● A new product version is added to your entitlement.

Licenses need to be rehosted when:

● You entered incorrect machine information when generating the license.

● The host ID of the machine has changed due to a hardware upgrade.
● You transfer products to a new machine.

You can either upgrade or rehost all licenses that were previously generated for a specific host (see Managing
License Hosts [page 26]) or you can modify individual licenses (see Modifying Individual Licenses [page
26]).

2.3.1 Managing License Hosts

Manage licenses of license hosts.

Procedure

1. Select Licenses on the left pane of the SMP main page, and then select Manage License Hosts.
2. Select or search for the existing license host.
3. Select one of these buttons to perform the desired operation on all licenses previously generated for the
specified host:
○ Upgrade All – upgrades all licenses on the host to their latest versions.
○ Re-host All – migrates all licenses to a new host. You provide details on the next screen.
○ Return All – returns all licenses to the available licenses pool for future redeployment.

If you select Upgrade All or Re-host All, new licenses are sent via e-mail message to your e-mail address,
and to any additional e-mail addresses you specify.

2.3.2 Modifying Individual Licenses

Modify individual licenses.

Procedure

1. Follow instructions in Generate License From SPDC [page 22] through the step for selecting options that
identify the license you want to change.
2. On the License Information page, select the desired license order.
3. Select one of:
○ Check in – returns the license to the available license pool. To rehost the license, follow instructions in
Generating Unserved Licenses [page 24] or Generating Served Licenses [page 23] .

SySAM Users Guide

26 PUBLIC Generate License From SPDC
 ○ Upgrade – upgrades the license to its latest version. Click Upgrade to generate a new license file.
Download the license file, save it, and deploy it. The Upgrade option appears only if newer versions of
the license are available.

Results

 Note

Each product limits the number of times you can check in and rehost its licenses. If you reach your check-in
limit, and the Check-in option does not appear, contact your company’s designated person in SAP
Technical Support.

SySAM Users Guide

Generate License From SPDC PUBLIC 27
3 Generating License Keys from SAP
Service Marketplace

If you have purchased Sybase products that use SySAM 2-based licenses under a SAP contract, go to the SAP
Support Portal for information about requesting licenses keys.

Procedure

1. Go to the Support Portal License Keys page at https://support.sap.com/keys-systems-installations/

keys.html .
2. Follow the instructions in the "How to Request License Keys - SAP Sybase" presentation available under
the "How-To Documents" quick access link.

SySAM Users Guide

28 PUBLIC Generating License Keys from SAP Service Marketplace
4 License File Content Overview

Learn about the content of the license file.

Each INCREMENT or UPGRADE line in a license file represents a license for a product or a licensable option of a
product. This figure has an INCREMENT line showing fields used by Sybase product licenses:

Served and unserved licenses differ in that an unserved license always has uncounted quantity and always
contains a Host ID field.

4.1 Served License

A served license file begins with SERVER and VENDOR lines, followed by the INCREMENT and UPGRADE lines.

For example:

SERVER license_server_host 0123ABCD

VENDOR SYBASE
INCREMENT prodeg SYBASE 2.0 31-dec-2005 1 \
PLATFORMS="i86_n" ISSUED=01-jan-2005 \
BORROW=720 NOTICE="ACME CORP" SN=1-1010 \
TS_OK SIGN2= "AADD..."

The SERVER line contains the host ID (0123ABCD) of the license server machine (<license_server_host>),
and the digital signature of the INCREMENT line is encoded using that host ID, so this license can be served only
from that machine. The INCREMENT line does not contain a host ID, so the license can be served to any
machine that can access this license server.

The served license example above shows one license to run one copy of version 2.0 or lower of the prodeg
product on the Windows operating system (i86_n) until December 31st, 2005. The product can be used on
any machine and the license can be borrowed from the license server for 720 hours of mobile use at a time.

4.2 Unserved License

An unserved license file contains an INCREMENT line only.

For example:

INCREMENT prodeg SYBASE 2.0 31-dec-2005 uncounted \ HOSTID=0BABE1

PLATFORMS="i86_n" \
ISSUED=01-jan-2005 NOTICE="ACME CORP" \
SN=1-1 SIGN2= "AADD..."

The unserved example above shows a license to run version 2.0 or lower of the prodeg product on the
Windows machine until December 31, 2005. The product can be run only on a machine with a host identifier of

SySAM Users Guide

License File Content Overview PUBLIC 29
0BABE1. The machine containing the correct host identifier cannot be a terminal server, because there is no
TS_OK field.

Two special host ID values which are also used are HOSTID=ANY, and HOSTID=DEMO which signify that the
product can run on any machine and no host identifier checks are performed

4.3 License Packages

SAP groups some licensable options into packages to reflect alternate product bundling or simply for ease of
license deployment.

For example:

PACKAGE PD_STUE SYBASE COMPONENTS="PD_SHELL \

PD_CDM PD_PDM PD_OOM \
PD_ILM PD_BPM PD_RQM PD_FRM PD_XSM PD_RMG" \
ISSUED=01-jan-2004 SIGN2="13BD ……."
INCREMENT PD_STUE SYBASE 12.00000 permanent 2 ……

In the example above, two version 12.0 licenses are provided for all of the PowerDesigner components in the
PD_STUE package.

4.4 License Attributes

SySAM-enabled products may specify license attributes in the VENDOR_STRING and ISSUER fields to identify
certain properties of the license, such as product edition, type of license and any limitations imposed (such as
maximum disk space or memory to be used).

For example:

INCREMENT ASE_EE SYBASE 2000.12310 permanent \

1 HOSTID=0123ABCD \
VENDOR_STRING=PE=EE;LT=CP \
PLATFORMS="hp700_u hp64_u" \
ISSUER="CO=Sybase, Inc.;V=15.0;AS=S;MP=365;CP=2"\
ISSUED=31-dec-2000 BORROW=720 NOTICE="ACME Corp" \
SN=500500065-2021 TS_OK SIGN2="18E7 B0E8 EEBB \
E760 253C 0709 1287 F128 6871 4C28 0204 8F5D \
D6C9 7998 A2DF 1CA1 EDE6 D98C 526E D8D9 F64E \
A836 9781 AC6F F360 2FCE 03B9 3702 A626 BF95

The example above signifies that the license type is a per-CPU license (LT=CP), and that the product is SAP
ASE, with a product edition of Enterprise Edition (PE=EE), and license for standby use (AS=S). The license can
be used to run a machine with a maximum of 2 CPUs (CP=2), and was purchased with a maintenance contract
of one year (MP=365).

One significant difference between the ASE_EE license shown above and the prodeg license example in
Unserved License [page 29] is the value of the license version field. The prodeg license version matched the
version of the product to be licensed. Both had a value of 2.0. The ASE_EE license version is actually a date

SySAM Users Guide

30 PUBLIC License File Content Overview
value, 2000.12310, or December 31st, 2000. This is because SAP ASE uses “date-based versioning” and
requests licenses based on its build date rather than its version number. See Installing Product Updates and
Support Renewal [page 51].

4.5 A Three-server Redundancy License

A three-server redundancy license file begins with three SERVER lines, and a VENDOR line, followed by the
INCREMENT and UPGRADE lines.

For example:

SERVER license_server_host_1 0123ABCD 27010

SERVER license_server_host_2 0456DCBA 27010
SERVER license_server_host_3 07890147 27010
VENDOR SYBASE
INCREMENT prodeg SYBASE 2.0 31-dec-2005 1 \
PLATFORMS="i86_n" ISSUED=01-jan-2005 \
BORROW=720 NOTICE="ACME CORP" SN=1-1010 \
TS_OK SIGN2= "AADD …."

The three-server redundancy license is the same as a normal server license, except the three server lines
indicate that three servers have been set up for redundancy. All three servers require identical license files.

Related Information

Three License Server Redundancy [page 6]

SySAM Users Guide

License File Content Overview PUBLIC 31
5 Virtual Machine, Partition, or Sub-
capacity Licensing

Sub-capacity licensing offer a way to license an SAP product for less than the full processor core capacity of a
server.

Subject to the terms of your software license agreement and product documentation, you may be able to
license a subset of the CPUs available on a physical machine using the SySAM Sub-capacity license
functionality. See your software license agreement and product documentation to determine whether SySAM
Sub-capacity licensing is allowed and if so, what type of partition or resource allocation technologies are
supported.

Related Information

Determining Host IDs [page 18]

5.1 Configuring SySAM Sub-capacity

Configure SySAM to use a license quantity appropriate to the containment level and to share licenses at the
machine, partition, or resource level.

Prerequisites

To configure machine-level licensing on platforms other than AIX logical partitions and HP-UX virtual partitions,
run sysamcap on the physical machine or control domain for the virtualization technology (such as VMware
ESXi/ESX console, the Microsoft Hyper-V host, the Red Hat KVM host, the XEN dom0) as a user with root
permissions.

Procedure

1. Obtain the SYBASE_SAM_CAPACITY environment variable for the containment level you are licensing.
a. To get machine-level information, enter:

sysamcap MACHINE

SySAM Users Guide

32 PUBLIC Virtual Machine, Partition, or Sub-capacity Licensing
 b. To get partition-level information, enter:

sysamcap PARTITION

c. To get resource-set-level information, enter:

sysamcap RESOURCESET

2. Set the SYBASE_SAM_CAPACITY environment variable to the value reported by sysamcap.

3. Do one of the following:

○ Start the installer which includes the sysamcap utility located in SYSAM-2_0/bin.
○ Select the Continue installation without a license key in the Software Asset Management License pane
during installation. After installation, copy your license key to installed_directory/SYSAM-2_0/
licenses directory where installed_directory is the location in which you have installed your
components.

5.2 sysamcap Utility

The sysamcap utility configures sub-capacity licensing for the containment level (machine, partition, or
resource set) and optionally, the name or ID of the resource set.

Syntax

sysamcap <capacity-level> [<resource_set_name>] [-q] [-v]

Parameters

capacity-level
designates the containment level to be licensed:

● MACHINE – the complete physical machine.

● PARTITION – a sub-capacity partition of your machine.
● RESOURCESET – a sub-capacity partition governed by a resource set.
○ <resource_set_name> (optional) – set this parameter to indicate the
resource set that will govern the product. The product is always be licensed
based on the resource set it is actually governed by so this parameter is only to
aid administration or to allow the product to verify that it is running under the
intended resource set.
On Solaris and HP-UX, the <resource_set_name> is the PSET ID obtained
when creating the processor resource set via the psrset command, or
equivalent.

SySAM Users Guide

Virtual Machine, Partition, or Sub-capacity Licensing PUBLIC 33
 On AIX, the <resource_set_name> is the name specified to mkrset, or
equivalent.
● DEFAULT – default configuration settings. SySAM uses the default license check
pre-sub-capacity-support mechanism to check for licenses. Sub-capacity
functionality is not available under the default setting.

-v
verbose output contains diagnostic messages.
-q
quiet mode reports only the environment variable.

Usage

Run sysamcap and set the SYBASE_SAM_CAPACITY environment variable to the value it reports prior to
running your product.

5.2.1 Example - Licensing a Machine to Allow Any Number of

VMware Virtual Machines

Procedure

1. Enable ESXi server tech support mode and log in to the VMware ESXi console with root privileges.

 Note

You must use the Linux version of sysamcap.

2. Run sysamcap, specifying machine-wide licensing:

sysamcap MACHINE

Example output:

Set the following environment variable prior to starting the product. This
only needs to be done once for each instance of the product that will run.
SYBASE_SAM_CAPACITY=MACHINE:FC2F63B3C5C2F2770A2
Using this configuration licensing will be based on 32 logical processor(s),
16 processor core(s) and 2 processor chip(s).
SAP recommends use of a SYSAM License Server, but if you wish to generate un-
served licenses for using the product within this environment then you will
need to specify the following host-id when generating licenses at the Product
Download Center.
MACHINE-ID=782bcb2f04e3

 Note

Starting with version 2.2.0.9, sysamcap MACHINE reports the real MAC address. In earlier versions,
the command reported the VMWare MAC address. Therefore, the host ID for unserved shared-capacity

SySAM Users Guide

34 PUBLIC Virtual Machine, Partition, or Sub-capacity Licensing
 (sysamcap MACHINE) licenses for VMware ESX virtual machines may have changed. Existing licenses
continue to work but you must check in and regenerate the licenses at SPDC for any VMs added after
the SYBASE_SAM_CAPACITY environment variable was last generated. Check the host ID reported by
sysamcap MACHINE against the HOSTID field in the unserved license to determine whether the license
needs to be regenerated.

3. Log in to a VMware VM to set the SYBASE_SAM_CAPACITY environment variable to the value report by
sysamcap and to run the product. Use the mechanism appropriate for the operating system that the VM is
running.

○ On a VM running Windows XP:

1. Right-click My Computer, and then click Properties Advanced Environment variables
System variables New .
2. In the Variable name field, enter the value: SYBASE_SAM_CAPACITY.
3. In the Variable value field enter the value reported by sysamcap, for this example:

MACHINE:FC2F63B3C5C2F2770A2

4. Click OK.
○ On a VM running Linux/UNIX and using a Korn shell:
1. Set the environment variable:

export SYBASE_SAM_CAPACITY=MACHINE:FC2F63B3C5C2F2770A2

4. Start the product.

 Note

Repeat these steps to run the product on a VM that was created after running sysamcap.

5.2.2 Example - License an Individual Logical Partition

License an individual logical partition such as AIX LPAR, HP vPar, HP Integrity Virtual Machine, Microsoft
Hyper-V, Red Hat KVM, Solaris LDOM, VMware VM, and Xen domU.

Procedure

1. Log in to the machine partition, for example, using an xterm running the Korn shell.
2. Run sysamcap, specifying partition-wide licensing:

sysamcap PARTITION

Example output:

Set the following environment variable prior to starting the product. This
only needs to be done once for each instance
of the product that will run.
SYBASE_SAM_CAPACITY=PARTITION

SySAM Users Guide

Virtual Machine, Partition, or Sub-capacity Licensing PUBLIC 35
 Using this configuration, licensing is based on 4 logical processors, 1
processor core and 1 processor chip.
SAP recommends using a SYSAM License Server; however, to generate an unserved
licenses for your SYSAM sub-capacity-enabled product you must specify the
following type of host-id when generating licenses at the SAP Product
Download Center.
PARTITION-ID=83f828fb

3. Set the environment variable:

export SYBASE_SAM_CAPACITY=PARTITION

4. Start the product.

5.2.3 Example - Licensing a Solaris Container

Procedure

1. Log in to the container, for example, using an xterm running the Korn shell.
2. Determine the name of the resource set by which the product will be governed.
3. Run sysamcap, specifying resource set licensing and optionally the <resource_set_name>, for example,
using PSET 1:

sysamcap RESOURCESET 1

Example output:

Set the following environment variable prior to starting the product. This
only needs to be done once for each instance of the product that will run.
SYBASE_SAM_CAPACITY=RESOURCESET,1:8C348011FAC4836A6C
Using this configuration licensing will be based on 2 logical processor(s), 2
processor core(s) and 1 processor chip(s).
SAP recommends use of a SYSAM License Server, but if you wish to generate un-
served licenses for using the product within this environment then you will
need to specify the following host-id when generating licenses at the Sybase
Product Download Center.
RESOURCESET-ID=2179c53d-737f-11dc-b683-8b3cbe475233-PSET-1

4. Set the environment variable:

export SYBASE_SAM_CAPACITY=RESOURCESET,1:8C348011FAC4836A6C

5. Start the product.

 Note

Refer to your product documentation to determine the sub-capacity technologies you can use.

SySAM Users Guide

36 PUBLIC Virtual Machine, Partition, or Sub-capacity Licensing
5.3 SySAM Sub-capacity Glossary of Definitions

Definitions for SySAM 2.x sub-capacity licensing.

● Host-ID – identifier that locks a license to a specific host or virtual environment. SySAM 2 uses the default
FLEXlm host-ID identifiers. With SySAM 2.x, the host-ID used for unserved licenses can be the default
FLEXlm host-ID, the machine-ID, the partition-ID, or the resourceset-ID, depending upon your
configuration.
● Machine-wide licensing – licenses a physical machine.
● Partition-wide licensing – licenses only a partition.
● Resource-wide licensing – licenses only a specific resource.
● Machine-ID – identifier for a specific physical machine. You can split the machine into multiple partitions.
● Machine partition – a logically separate system within a physical machine, typically using its own operating
system rather than a partitioning of a machine’s resources. A machine partition can be a virtual machine
(VM), AIX Logical Partition (LPAR), HP-UX Virtual Partition (vPar), or Solaris Logical Domain (LDOM). The
term "machine partition" refers to a separate logical system (typically using its own operating system)
rather than to partitioning of a machine’s resources.
● Resource partition – a sub-capacity operating environment within a physical machine that limits the
processing capacity for an application, such as a Solaris Container, an AIX WPAR, or an HP Secure
Resource Partition.
● Partition-ID – identifier for a specific machine partition.
● Resource-set-ID – identifier for a specific processor resource-set.
● License quantity – the number of licenses needed for a particular containment level.
● Containment level – a particular division of a machine such as a partition or resource set.

SySAM Users Guide

Virtual Machine, Partition, or Sub-capacity Licensing PUBLIC 37
6 Administering License Servers

Learn about tasks necessary for license server administration and information about license server tools and
functions.

Related Information

Installing the SySAM License Server [page 14]

Served License Deployment Model [page 13]
Installing the SySAM License Server [page 14]

6.1 Starting and Stopping License Servers

Execute the sysam command to start and stop the license server.

Generate and install served licenses before you install products.

● When you install a license server on Windows platforms, it is automatically configured to start as a system
start-up service.
● On UNIX machines, you must configure SySAM to start as a service after you complete the license server
installation.

When you start and stop a license server, execute the commands on the machine where the license server is
installed. You cannot start a license server until at least one served license is installed in the licenses
directory of the license server installation. Only one SySAM license server running on any one machine is
allowed.

6.1.1 Manually Starting and Stopping License Servers

Learn how to manually start and stop a license server.

Prerequisites

On UNIX machines, SAP recommends that you use the “sybase” or "sap" user for license server installation
and administration. If you have root permissions, switch to a specific user account by entering:

su sybase -c "sysam start"

SySAM Users Guide

38 PUBLIC Administering License Servers
Procedure

● To start a license server, issue this command on the machine where the license server is installed:

sysam start

● To stop a license server, issue this command on the machine where the license server is installed:

sysam stop

6.2 Determining License Server Version and Status

You can determine license server version and status by using the sysam status command. You can
determine the versions of lmgrd and vendor daemon by using the -v option.

Procedure

1. To determine the status of the license server, execute this command on the machine where the license
server is installed:

sysam status

The output from this command states whether the license server is running and lists the license files that
the license server is using.
2. To determine the license manager daemon version, enter:

lmgrd -v

3. To determine the vendor daemon version, enter:

SYBASE -v

The version of your license manager daemon must be greater than or equal to the version of your vendor
daemon.

SySAM Users Guide

Administering License Servers PUBLIC 39
6.3 Monitoring License Use

Use the sysam status command to determine the status of a specific license server, establish which licenses
are available, and where licenses are currently being used.

Procedure

Run this command on the license server host machine:

sysam status -a

You can also run this same command on a machine where SySAM-enabled products are running, to determine
the status of all license servers used by the licensed products on that machine, and to verify that the license
servers are referenced correctly in the product license file.

6.4 Registering New and Updated License Files

Register or update your license files the license server.

Prerequisites

To update multiple licenses at once, use Manage License Hosts at SPDC or SAP Support Portal.

Procedure

1. Generate your new licenses from SPDC or the SAP Support Portal and save them to the licenses
directory
2. On the machine on which your license server is running, enter:

sysam reread

Related Information

Generate License From SPDC [page 22]

Generating License Keys from SAP Service Marketplace [page 28]

SySAM Users Guide

40 PUBLIC Administering License Servers
6.5 Managing the License Server Debug Log

Periodically truncate the debug log file as it becomes larger and the value of older messages decreases over
time.

Context

By default, all license server status and error messages are written to the debug log file SYBASE.log in the log
directory. The SYBASE.log is used to diagnose issues with the license server.

Procedure

1. On the license server machine, enter:

lmutil lmswitch -c license_directory_location SYBASE tmp.log

2. Delete or archive SYBASE.log.

3. Return to using SYBASE.log:

lmutil lmswitch -c license_directory_location SYBASE SYBASE.log

4. Delete the temporary file tmp.log.

6.6 Controlling License Use with the SySAM Options File

The options file (SYBASE.opt, in the licenses directory) allows license administrators to control various
licensing operating parameters and to designate users of specific licenses.

Context

License users are identified by their user name, host name, display, IP address, or the user-defined project
defined by the LM_PROJECT environment variable. License administrators can perform the following to the
options file.

The license server reads the options file and obeys its directives at start-up or, if it is already running, when you
issue sysam reread.

SySAM Users Guide

Administering License Servers PUBLIC 41
Procedure

● Control license use – for example, the following options file content restricts the use of the Database
Expert product, controlled by the ASE_SDBE license, to users tom, sam, and alice:

GROUP dbe_group tom sam alice

INCLUDE ASE_SDBE GROUP dbe_group

● Reserve licenses – for example, this line in the options file reserves a SQL Expert license with the licensed
feature ASE_SXP for user joe:

RESERVE 1 ASE_SXP USER joe

 Note

For products with more than one edition, and more than one license type, you can use the
VENDOR_STRING that appears on the INCREMENT or UPGRADE line of the license to identify a specific
license.

For example, to reserve a license for the Enterprise Edition of SAP ASE (license package ASE_EE, and
license attributes SORT=100;PE=EE;LT=SR) to be used on the machines <payrollsvr> and
<accountsvr>, enter:

HOST_GROUP ase_ee_hosts <payrollsvr> <accountsvr>

RESERVE 1 ASE_EE:VENDOR_STRING=SORT=100;PE=EE;LT=SR HOST <payrollsvr>
RESERVE 1 ASE_EE:VENDOR_STRING=SORT=100;PE=EE;LT=SR HOST <accountsvr>

 Note

Reserving a license for multiple hosts requires each host to have a separate RESERVE line in the options
file. If the reservation was made solely for the HOST_GROUP above, then two licenses are reserved, but
any machine in the host group can use all of the reserved licenses.

● Restrict the number of available licenses – for example, to prevent accidental use of overdraft licenses for
SAP ASE, add the following line to the options file:

If overdraft licensing is subsequently needed, you can modify or remove the line from the options file.

 Note

Consider carefully the use of an overdraft license since you need to agree to purchase these licenses
within 30 days.

● Enable report and debug log files – the default SYBASE.opt options file in the license server’s licenses
directory sets the location of the license server debug log and report log files, and specifies that the license
server should append the files (rather than create a new file) each time the license server is started.

The default SYBASE.opt file contains two lines similar to this, where REPORTLOG and DEBUGLOG are the
log type, the + (plus sign character) indicates to append log file entries, and SYBASE.rl and SYBASE.log
specify each log file’s path.

REPORTLOG +/opt/sybase/SYSAM-2_0/log/SYBASE.rl
DEBUGLOG +/opt/sybase/SYSAM-2_0/log/SYBASE.log

SySAM Users Guide

42 PUBLIC Administering License Servers
 Use this syntax for the log file entries in the options file:

[DEBUGLOG | REPORTLOG] [+] log_path

6.7 Borrowing Licenses for Offline License Servers

You can borrow mobile licenses by using GUI functionality provided by some products, or by using the lmutil
licensing utility and lmborrow, one of its parameters.

Check your product's documentation to see whether you can borrow a license by using the product's GUI
functionality.

Related Information

Small Environment, Unserved Licenses [page 8]

Using SAP Products When the License Server is Offline [page 5]

6.7.1 Borrowing Licenses Using lmutil lmborrow

Use lmutil lmborrow to borrow a license.

Prerequisites

Some products automatically borrow licenses whenever they are used, so first check whether licenses are
already borrowed on the machine:

lmutil lmborrow -status

lmutil - Copyright (c) 1989-2006 Macrovision Europe Ltd. and/or Macrovision
Corporation. All Rights Reserved.
Vendor Feature Expiration
------ --------- -----------------
SYBASE PD_SHELL 23-Feb-09 16:59

Procedure

1. Shut down the SySAM-enabled products for which to borrow licenses.

SySAM Users Guide

Administering License Servers PUBLIC 43
2. Execute the following lmutil command for each license you are borrowing:

lmutil lmborrow SYBASE <borrow-end-date> [<borrow-end-time>]

Where:
○ <borrow-end-date> (dd-mon-yyyy) is the date on which you want the borrowed license to expire,
○ <borrow-end-time> (optional) is the 24-hour clock time (hh:mm) at which you want the borrowed
license to expire
For example, to borrow a license that expires at 1 PM (13:00) on August 20th, 2012, enter:

lmutil lmborrow SYBASE 20-aug-2012 13:00

 Note

To continue using a SySAM-enabled served-license product offline, without interruption, you must
renew the borrowed license before the license expires.

3. For the SySAM-enabled products to recognize the borrowed licenses, restart them.
4. (Optional) Before running any product for which you do not want to borrow licenses, enter:

lmutil lmborrow -clear

5. Disconnect from the network.

6. (Optional) Determine the status of a license borrowed for a SySAM-enabled product’s offline use, enter:

lmutil lmborrow -status

6.7.2 Returning a Borrowed License Before It Expires

Use lmutil lmborrow -return to return a borrowed license before it expires.

Procedure

1. From the product machine, that is using a borrowed license, connect to the network.
2. Shut down your SySAM-enabled products.
3. Return each borrowed license by entering:

lmutil lmborrow -return

[-c <location_of_license_file>] <name_of_license>

SySAM Users Guide

44 PUBLIC Administering License Servers
6.8 Configuring SySAM for Redundancy

Configure SySAM for redundancy by setting up a three-server redundant cluster or by specifying multiple
license servers.

A three-server redundant cluster only provides redundancy. Using multiple license servers provides
redundancy and load balancing.

Related Information

Three License Server Redundancy [page 6]

6.8.1 Configuring a Three-Server Redundancy Cluster

Configure SySAM for redundancy by setting up a three-server redundant cluster.

Prerequisites

The three machines hosting a license server should:

● Have excellent communications.

● Maintain identical copies of the license files, the lmgrd binary, and the SYBASE binary locally rather than
on a file server. If you do not do this, you lose the advantages of having redundant servers, since the file
server holding these files becomes a single point of failure.

Context

A three-server redundancy is functional when any two of the three license server systems are running. Three-
server redundancy only provides failover protection; it does not provide load balancing.

Procedure

1. Copy the license file to the licenses directory of each of the three servers. Each line contains the name of
the server, its host ID, and the port number on which it will listen. For example:

SERVER server_1 0123ABCD 27010

SERVER server_2 0456DCBA 27010

SySAM Users Guide

Administering License Servers PUBLIC 45
 SERVER server_3 07890147 27010

The selection order for the master server is determined by the order in which you specify the servers at
SPDC or SMP and can be seen by the order of the servers in the resultant license file. The same license file
must be used by each license server and is headed with a SERVER line for each server.
2. SySAM-enabled products must be informed to obtain licenses from a three-server redundant cluster so
that they can fail over to the new master server if the current master becomes unavailable. Set this up in
one of these ways:

○ SAP recommends that the license file used by the product is headed with three SERVER lines. The
header must be identical to that of the license files on each server, with the exception that the host ID
field can be set to ANY. The following license file enables a product to use the three-server redundant
cluster shown in the example above:

SERVER server_1 ANY 27010

SERVER server_2 ANY 27010
SERVER server_3 ANY 27010
USE_SERVER

○ Alternatively, set the SYBASE_LICENSE_FILE or LM_LICENSE_FILE environment variables to a

comma-separated list of port@hostname values to specify the three-server redundant cluster. For the
example above, set the environment variable to:

27010@server_1,27010@server_2,27010@server_3

 Note

If the machine where the product is running must use a fully qualified domain name (FQDN) to
contact any license server in the cluster, you must specify the FQDN in the environment variable
and also when generating the license at SPDC or SMP.

6.8.2 Using Multiple License Servers

Configure SySAM-enabled products to obtain licenses from multiple license servers for load balancing or
redundancy.

Context

This setup is limited by the number of unused licenses, including overdrafts, remaining on each license server.
This means that you must purchase enough licenses so that each license server has sufficient licenses to
service any product instance that may request one.

SySAM Users Guide

46 PUBLIC Administering License Servers
Procedure

Set this up in one of two ways:

○ Create a license file that includes the two lines below. Create one of these files for each license server,
where <host> is the host name for the license server and <port> is the port number on which the license
server is listening. You need not specify the port number if the license server is listening on a port in the
default port number range (27000 to 27009).

SERVER <host> ANY [<port>]

USE_SERVER

For example, to have the product look for licenses from one of three servers named: <nyc>, <bos>, and
<sfo>, create three files in the default licenses directory of the product as:

# nyc.lic
SERVER nyc ANY 29733
USE_SERVER
# bos.lic
SERVER bos ANY 29722
USE_SERVER
# sfo.lic
SERVER sfo ANY
USE_SERVER

When using such license files, the product loads the files using the directory sort order, so name the files
according the preference of license servers to be used. For example, 1_bos.lic, 2_nyc.lic,
3_sfo.lic .
○ Set the SYBASE_LICENSE_FILE or LM_LICENSE_FILE environment variables to a list of
[port]@hostname values to specify each license server, where the port number is omitted if the license
server is using the default port number range. Separate each license server with a colon on UNIX platforms
and a semicolon on Windows platforms. For the example above, from a UNIX C shell, enter:

setenv SYBASE_LICENSE_FILE 29722@bos:29733@nyc:@sfo

On Windows platforms, enter:

set SYBASE_LICENSE_FILE=29722@bos;29733@nyc;@sfo

6.9 Access Through a Firewall or VPN

SySAM license server listens on two TCP/IP ports for incoming license requests. Therefore, firewall or VPN
policies require a set-up to allow access to both ports.

The SySAM license server consists of two processes: the license manager daemon (lmgrd) and the vendor
daemon (SYBASE).

Set the ports by specifying their port numbers in the license files on the SySAM license server. For example, to
force lmgrd to listen on port 27010 and the SYBASE vendor daemon to listen on port 27011, the license file
header should have:

SERVER keyserver 1D1D1D1D 27010

SySAM Users Guide

Administering License Servers PUBLIC 47
 VENDOR SYBASE PORT=27011

A SySAM enabled product only needs to know the port where lmgrd is listening. The product connects to
lmgrd on that port and will then be told which port to use to connect to the SYBASE vendor daemon. This
means that the product's local license file just needs to contain the following:

SERVER keyserver ANY 27010

USE_SERVER

When generating licenses at SPDC, specify the license server port to fix the port for lmgrd. Edit the license file
to specify the SYBASE vendor daemon port.

When generating licenses at SMP, specify both ports. The port for lmgrd is specified as License Server Port 1,
and the SYBASE vendor daemon port as License Server Port 2. For three-server-redundant configurations, you
can only specify the SYBASE vendor daemon port for the primary license server; same value is used for the
secondary and tertiary license servers.

 Note

You can specify any unused port number between 0 and 64000. On UNIX, choose a port number greater
than 1024, as most port numbers less than 1024 are privileged port numbers. Do not specify a number in
the range 27000 to 27009 for License Server Port 2, as ports in this range are used by the lmgrd process
when no port is specified for License Server Port 1.

6.10 Running a License Server Automatically on UNIX

Systems

Set up license servers on UNIX to run as a service.

Procedure

1. Use an account with root privileges to log in to the machine where the SySAM license server is installed.
2. Create a script for the system to use during start-up and shutdown, using the following example for
reference. The purpose of the script is to avoid running the license server with root privileges, which is not
required.

The example script assumes that the license manager (lmgrd) is run as the user sybase, and is installed in
the /opt/sybase directory. Change these parameters to match your installation.

#!/bin/sh
#
SYBUSER=<sybase>
SYBASE=</opt/sybase>
SYSAM=$SYBASE/SYSAM-2_0
case "$1" in
'start')
su $SYBUSER -c "echo `date` starting lmgrd
>> $SYSAM/log/boot.log"

SySAM Users Guide

48 PUBLIC Administering License Servers
 nohup su $SYBUSER -c "umask 022;
$SYSAM/bin/sysam start >> $SYBASE/log/boot.log"
;; 'stop')
su $SYBUSER -c "echo `date` stopping lmgrd
>> $SYSAM/log/boot.log"
su $SYBUSER -c "$SYSAM/bin/sysam stop -q
>> $SYSAM/log/boot.log"
;;
*)
echo "Usage: $0 { start | stop }"
exit 1
;;
esac
exit 0

3. Save the script with a file name and in a directory that is appropriate for your operating system:

○ (Solaris) /etc/init.d/sysam.boot
○ (Linux and AIX) /etc/rc.d/init.d/sysam.boot
○ (HP -UX) /sbin/init.d/sysam.boot
4. Change the script’s read, write, and execute permissions, as well as owner, and group. For example, if the
script is stored as /etc/init.d/sysam.boot, enter:

chmod 744 /etc/init.d/sysam.boot

chown root /etc/init.d/sysam.boot
chgrp sys /etc/init.d/sysam.boot

5. Create an appropriately named link with which to start the SySAM license manager when the license server
starts; typically, <S> + <run number> + <script name>:

○ (Solaris)

ln -s /etc/init.d/sysam.boot /etc/rc3.d/S70sysam

○ (Linux and AIX)

ln -s /etc/rc.d/init.d/sysam.boot /etc/rc.d/rc3.d/S70sysam

○ (HP-UX)

ln -s /sbin/init.d/sysam.boot /sbin/rc3.d/S070sysam

Choose a run number (70 in the example) that is higher than any required SySAM subsystems (such as
networking services), and lower than the run number of any SySAM-enabled products.
6. Create an appropriately named link that can be used to stop the SySAM license manager when the license
server shuts down; typically, <K> + <run number> + script name. Choose a run number (02 in the
example) that is lower than any required SySAM subsystems (such as networking services), and higher
than the run number of any SySAM-enabled products.

○ (Solaris)

ln -s /etc/init.d/sysam.boot /etc/rc2.d/K02sysam

○ Linux and AIX)–

ln -s /etc/rc.d/init.d/sysam.boot /etc/rc.d/rc2.d/K02sysam

SySAM Users Guide

Administering License Servers PUBLIC 49
 ○ (HP-UX)

ln -s /sbin/init.d/sysam.boot /sbin/rc2.d/K002sysam

SySAM Users Guide

50 PUBLIC Administering License Servers
7 Installing Product Updates and Support
Renewal

When product updates are made available, the licenses are encoded with information about the duration of the
support plan. This information is stored in the license file and is referred to as “date-based versioning.”

Context

When you generate a license for a product that uses date-based versioning, the license version is created with
the date that is the later of:

● The license purchase date

● The date the customer’s support plan ends

For example, two customers are named Acme and Backme. Each customer purchases version 3.0 of ProductX
on January 1st, 2005. However, Backme also purchases support for the product until the end of 2005. The
licenses generated for Acme and Backme have different versions:

For Acme:

INCREMENT ProductX SYBASE 2005.01010 ...\ NOTICE="Acme" …

For Backme:

INCREMENT ProductX SYBASE 2005.12310 ...\ NOTICE="Backme" …MP=365…

Acme can use any version of ProductX built before January 1st, 2005. Backme can similarly use any version of
ProductX built before January 1st, 2005 but can also use any maintenance releases or EBFs for ProductX built
before December 31st, 2005.

ProductX uses its build date as the version when requesting licenses, so an EBF built on March 19th, 2005
requests a license version greater or equal to 2005.0319. This request is satisfied by the license generated by
Backme. Acme does not have a valid license for this request.

If Backme renews their support contract for ProductX until the end of 2006, they must generate and deploy
new licenses with the new end-of-support date. These licenses differ from those seen previously because they
are an upgrade of the license from the old version to the new version. Such licenses look similar to:

UPGRADE ProductX SYBASE 2005.12310 2006.12310 ...

 Note

The UPGRADE line is exactly the same as an INCREMENT line with the exception that the version of the
license to be upgraded precedes the license version field.

SySAM Users Guide

Installing Product Updates and Support Renewal PUBLIC 51
8 Migrating a SySAM 1 License Server to
SySAM 2

A SySAM 2 license server can grant licenses to both SySAM 1 and SySAM 2-enabled products.

Context

There can be only one instance of a SySAM license server running on any given machine.

Procedure

1. Shut down the SySAM 1 license server.

2. Install a SySAM 2 license server on the same host using the same port number that was used for the
SySAM 1 license server.
3. (UNIX platforms only) Configure the new license server to start and stop as part of the system start-up and
shutdown, or replace SYSAM 1 references with SYSAM 2 in any start-up scripts that were used for the
SySAM 2 license server.
4. Copy the SySAM 1 license file (license.dat) to the license server SYSAM-2_0/licenses directory as
license.lic. SySAM 1 licenses are usually contained in one license.dat file, located in the
SYSAM-1_0/licenses directory.

Because the SySAM 2 license server uses the same port as the old SySAM 1 license server port, you need
not edit the license file header to change the port number, which identifies the port where the license
server listens for license requests from SySAM-enabled products.
5. Install any new licenses in the SYSAM-2_0/licenses directory on the license server host.
6. Start the migrated license server, or issue the sysam reread command for the migrated license server to
use any new licenses.

 Note

When the migrated license server starts, it reads every file with a .lic extension; and does not read
any with an extension other than .lic.

Results

After you complete the license server migration, the SySAM 2 license server grants licenses for both SySAM 1
and SySAM 2-enabled products.

SySAM Users Guide

52 PUBLIC Migrating a SySAM 1 License Server to SySAM 2
Related Information

Installing the SySAM License Server [page 14]

8.1 Consolidating Multiple License Servers

You can consolidate multiple SySAM 1 license servers into one SySAM 2 license server.

Procedure

1. Select the host machine on which to consolidate license servers.

2. If the selected host already runs a SySAM 1 license server, migrate to a SySAM 2 license server. Otherwise,
install the SySAM 2 license server using the standalone license server installer.
3. (UNIX platforms only) Configure the SySAM 2 license server to start and stop as part of the system start-
up and shutdown. If the host had a SySAM 1 license server configured to start automatically, replace the
SySAM 1 references with SySAM 2 in system start-up directories and in any start-up scripts that were used
for the SySAM 1 license server.
4. Collect all licenses that were being served from the individual license servers and deploy them to the new
consolidated SySAM 2 license server:
a. Create one new license file with a .lic file name extension. Save it to the license server SySAM-2_0/
licenses directory, then use a text editor to open the file.
b. Use a text editor to open each SySAM 1 license file, remove the license header (the first three lines that
start with SERVER, VENDOR, and USE_SERVER), and copy the remaining contents to the new license file
(with the .lic extension) on the consolidated license server host. Repeat for every SySAM 1 license
file.
5. Continuing in a text editor, add the following header to the new consolidated license file, where <port> is
the port number on which the license server will listen for license requests from SySAM-enabled products:

SERVER this_host ANY <port>

VENDOR SYBASE
USE_SERVER

If you do not specify a port number in the header, the license server uses a default port in the 27000
through 27009 range.
6. Save the consolidated license file (license.lic), which now has all SySAM 1 license file contents and the
updated header, to the license server in the SYSAM-2_0/licenses directory.
7. Start the consolidate license server.
8. Delete the old licenses from the retired SySAM 1 license servers and point the SySAM-enabled products
that used the old license servers to the new consolidated license server:

SySAM Users Guide

Migrating a SySAM 1 License Server to SySAM 2 PUBLIC 53
 ○ On each SySAM 1-enabled product host, use a text editor to open the license.dat file and replace
the contents with the following two lines, where <server_host> is the host name of the consolidated
license server, and <port> is the port number on which the license server will listen:

SERVER <server_host> ANY <port>

USE_SERVER

 Note

Do not specify the <port> if the consolidated license server will be using the default port numbers
and you did not specify the port in the header of the new license server file in step 6.

○ Save each updated license.dat file to its original location.

9. Shut down, uninstall, or remove all other SySAM 1 license servers.

Related Information

Installing the SySAM License Server [page 14]

SySAM Users Guide

54 PUBLIC Migrating a SySAM 1 License Server to SySAM 2
9 Troubleshooting SySAM Errors

Troubleshoot the most common SySAM errors.

If a license problem occurs, solve the problem as quickly as possible. Products that cannot acquire a valid
license during installation may still install or run within a grace period. If you do not solve the problem or
acquire a valid license before the grace period expires, the product stops functioning.

9.1 Where to Find License Error Information

Typically, server products list problems in an error log, and allow you to configure e-mail notifications.

GUI tool products generally show messages in a status window. Some products may also support a command
or menu option, such as Help About to display the current license status.

If you use served licenses, and license servers, all license server status and error messages are written to the
SYBASE.log debug file, which is located, by default, in the log subdirectory.

9.2 Problems and Solutions

There may be some typical scenarios that cause installation issues.

Error Possible Causes Solution

You see "Cannot find a valid You may not have the required li­ See When the Installer or Product Cannot Find a
license." censes installed. If there are installed
Valid License [page 59].
licenses, the licenses may be incorrect
for the product or feature you are try­
ing to install.

You cannot update an exist­ If you are updating an existing installa­ If you are installing an update that is authorized by
ing installation. tion, make sure your license author­ the license, see the solution for Product Cannot
izes you to install the update. See In­ Checkout a License and Starts in Grace Period error
stalling Product Updates and Support below before you proceed with the update.
Renewal [page 51]. If your license does
not allow you to perform the update,
the product may not be usable.

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 55
Error Possible Causes Solution

License server executes When you installed your product, the Use the instructions in your product’s installation
and scripts were not instal­ license server was not installed. Some
guide to install the license server.
led. product installations offer the option
to install a license server; however
when available, this option is not se­
lected, by default, for installation. You
may need to explicitly install a license
server. See your product’s installation
guide and release bulletin to deter­
mine if the product installer offers this
option.

License server does not See When the License Server Fails Go to SPDC or SAP Support Portal, generate a valid
start. [page 60]. served license for your product, and copy it into the
licenses directory on the machine where the li­
cense server is installed.

License server does not ● The license was generated for a ● Verify that the host ID recorded in the license file
recognize the license files.
different machine or generated matches the host ID of the actual machine for
using an incorrect host ID. which the license was issued. If the host IDs do
● The license has been altered. You not match, go to SPDC or SAP Support Portal,
cannot change any information in check in the license, then regenerate the license
a generated license. with the correct host ID.

● If the host ID for your platform is ● If your license is being created by typing from a
based on the network adapter paper copy, verify whether errors occurred
identification, the most common when the license information was entered. You
problem occurs when you have can also download a new copy of the activated li­
used an ID associated with the cense from SPDC or SAP Support Portal.
address of a virtual network ● If the host ID for your platform is based on a net­
adapter. work adapter, verify that the ID you are using is
associated with a valid NIC and that the ID is not
associated with loopback or virtual adapters. If
the ID you are using is associated with a remova­
ble network adapter, verify that the adapter is
actually attached to the computer.

Linux virtual machine does The /usr/sbin/dmidecode in the Log in to Linux virtual machine as root, then execute
not appear to be part of the Linux virtual machine cannot read chmod 4555 /usr/sbin/dmidecode.
Microsoft Hyper-V host. from /dev/mem.

SySAM Users Guide

56 PUBLIC Troubleshooting SySAM Errors
Error Possible Causes Solution

Product does not start, and ● You have not generated and de­ At a command prompt or in a terminal window, exe­
you see a license checkout
ployed the valid licenses for the cute the following, where <feature_name> is the
error.
product requesting licenses. name of the feature for which SySAM failed to check
● The required license does not ex­ out a license:
ist and the product does not
award a license on grace. sysam diag <feature_name>
● The product is configured to use
If the SySAM script is unavailable, enter:
the wrong edition or license type.
● You have the wrong host ID for an lmutil lmdiag -c
unserved license. license_directory_location
feature_name
● When multiple product editions
include optional features, the fea­ Go to SPDC or SAP Support Portal and generate your
tures are offered as separately li­ product’s required licenses. If you are trying to use a
censed items for each edition. Li­ separately licensable optional feature you need a li­
censed optional features work cense for both the base product and the option, and
only with the licensed base prod­ if the product has more than one edition, the edition
uct of the same edition. For exam­ of the base product and option must be the same.
ple, if you order SAP ASE, you
cannot use a Small Business Edi­ If you generated an invalid license, check in the li­
tion optional feature license with cense at SPDC or SAP Support Portal, and regener­

an Enterprise Edition base prod­ ate the license with the correct information.

uct.
● You are using an unserved Stand­
alone Seat (SS) type license on a
terminal server.
● The license is for a different oper­
ating system.
● The license is a Floating License
(FL) but is currently in use else­
where.

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 57
Error Possible Causes Solution

Product cannot check out a To help you determine the possible See Problems With Served License Deployment
license, and starts in grace Models [page 63] or Problems With Unserved Li­
causes when your product cannot
period. cense Deployment Models [page 61].
check out a license, execute the fol­
lowing from the SYSAM-2_0/bin
directory, at a Windows command
prompt or in a UNIX system terminal
window, where <feature_name> is
the name of the feature license that
could not be checked out.

sysam diag
<feature_name>

If the command output says that no li­

censes are available for checkout, this
may be due to one of the reasons be­
low, which are separated into served
and unserved license deployment
model causes and solutions.

Product continues to run in The license status has not yet been Wait up to 6 hours for server products, and up to 1.5
grace period after fixing a li­ updated. When the product periodi­ hours for tool products.
cense problem. cally performs license checks, the li­
cense status is not immediately up­
dated.

Product cannot find li­ You either have not installed the li­ See When a Product Cannot Find License for Op­
censes for optional fea­ cense for the optional feature, or the tional Features [page 61].
tures. license exists, but cannot be checked
out.

SySAM Users Guide

58 PUBLIC Troubleshooting SySAM Errors
Error Possible Causes Solution

Product obtains the wrong These locations are searched, in the ● Configure your product to choose a license for a
license.
order specified, until a suitable license specific edition and license type.
is found. When a license directory is ● If you are using served licenses, use the options
specified, license files in that directory file to ensure that the correct license is used.
are loaded in the directory sort order.
When a product looks for a license, it
looks in:

● The locations that represent the

values set for the SYBASE_LI­
CENSE_FILE and LM_LI­
CENSE_FILE variables. Avoid us­
ing environmental variables; in­
stead, locate all licenses centrally
in the expected licenses direc­
tory.
● All files with a .lic extension in
the licenses directory. This loca­
tion is product-specific, though
typically the directory is
$SYBASE/SYSAM-2_0/
licenses.

The first license that matches the fea­

ture name, version, edition, and li­
cense type filter is used; however, this
license may not be the intended li­
cense your product requested.

License checkout problems See Problems With Unserved License Deployment Models [page 61].
with unserved license

License checkout problems See Problems With Served License Deployment Models [page 63].
with served license

9.2.1 When the Installer or Product Cannot Find a Valid

License

A warning is issued when the installer or product cannot find a valid license.

Procedure

1. If the installation fails, go to SPDC or SAP Support Portal to generate and install the required valid licenses,
then restart the installation.

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 59
2. Verify that you have generated and deployed the correct license. The error message should indicate what
the problem is:

○ An incorrect host ID for unserved licenses

○ An incorrect license server reference file, or the license server is not running on the machine and
listening on the specified port
○ A license generated for a specific product edition and license type, but the product is configured to use
a different product edition and license type.
○ Using Standalone Seat (SS) unserved licenses on a terminal server
○ Check the SYBASE.log file to make sure the license server has started.
3. Ignore the warning. If the product continues to install within a grace period, complete the installation.
Generate and install the required SySAM licenses before the grace period expires.

9.2.2 When the License Server Fails

The most common reason for a license server failing to start is that no served licenses are installed on the
license server.

The license server requires at least one served license in the licenses directory for it to start. When you install
a new license server, there are, by default, no served licenses in the licenses directory. Generate and deploy a
served license to this directory.

Additional reasons for a license server failing to start include:

● Using an unserved license with a license server – the license activated from SPDC or SAP Support Portal is
an unserved license. Examine the license files. Served licenses always start with a SERVER header. If you do
not see a line starting with SERVER , you are using an unserved license that does not work with the license
server.
● The license server port number is already in use – if you are using a specific port number for the license,
that port number may already be in use. Use netstat -a to verify that the port number is free. If not,
reassign the port or use a different port number for the license server.
● Mismatch between the host name in the license file and the actual host name – the host name is recorded
next to the SERVER keyword. If it does not match the actual host name, correct the host name in the
license file or set the value next to the SERVER to this_host which is a keyword that works with any host
name.
● Header mismatch – when you have multiple license files, each one must have the same header, host name,
port, and so on.
● The licenses on one machine were generated for a different machine – examine the host ID recorded next
to the value in the license file host name in the SERVER header. It must match the host ID for the machine
on which the license server will run.
● The LSB packages are missing from the operating system.. You will see an error message similar to the
following:

/lib64/ld-lsb-x86-64.so.3: bad ELF interpreter: No such file or directory

To install the LSB package, run the following command:

RedHat:

sudo yum -y install redhat-lsb

SySAM Users Guide

60 PUBLIC Troubleshooting SySAM Errors
 Suse SLES:

yast -i lsb

9.2.3 When a Product Cannot Find License for Optional

Features

If a license for the optional feature exists, but cannot be checked out by the product, perform these diagnostic
tasks to determine the specific problem.

To ensure that the license for the optional feature exists and can be checked out from the machine where the
product is running, execute:

sysam diag <feature_name>

Compare the feature and the license to:

● Verify that the optional feature is for the same edition of the feature’s base product.
● (Products and features that support active and standby licensing only) Verify that the active or standby
flags match for the base product license and the optional feature license.
● Compare the product and optional feature editions, and active and standby status, then verify that the
available license matches.

See License Attributes [page 30].

If any of the above items do not match, go to SPDC or SAP Support Portal to generate and download the
correct licenses or adjust product configuration.

9.2.4 Problems With Unserved License Deployment Models

Check these typical issues if you are experiencing any problems with an unserved license model.

Possible Causes Solutions

The license for the product or feature you are using is not in The local license directory is product-specific, and the li­
the local licenses directory. cense must be deployed to the correct location for the prod­
uct. Typically, this directory is $SYBASE/SYSAM-2_0/
licenses.

Generate the required unserved licenses from SPDC or SAP

Support Portal and deploy them.

Your product’s license may have been activated with the in­ 1. Check the license back in to SPDC or SAP Support Por­
correct host ID for the machine on which you are running the tal.
product. 2. Regenerate the license at SPDC or SAP Support Portal
with the correct host ID.
3. Install the license to the local machine where you are
running your instance of the SySAM 2-enabled product.

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 61
Possible Causes Solutions

The available licenses are for a different operating system or Obtain a license for the correct platform from SPDC.
architecture than the machine on which you are running
your product feature. 1. Check the license back in to SPDC.
2. Generate a license for the correct platform, or install the
product on the correct platform.
3. Deploy a license to the local machine where you are run­
ning your instance of the product.

 Note
Licenses generated from SAP Support Portal are plat­
form-independent.

You are running your SySAM 2-enabled program in a termi­ Set up served licenses for a terminal server environment:
nal services (TS) environment with an unserved Standalone
Seat (SS) license. 1. Log in to SPDC or SAP Support Portal and check in your
old license.
2. Generate served licenses and deploy them to a license
server.
3. Configure the product to obtain licenses from the li­
cense server.

If the output from running sysam diag For example, the product is configured to look for an SAP
ASE, Enterprise Edition license, but only an SAP ASE, Ex­
<feature_name> states that a license for your product or
press Edition license is available; or, the product is config-
feature is available for checkout, you still may be unable to ured to use a Server License (SR) license type, but only a
check out the license because your product has been config- CPU License (CP) is available.
ured as a specific edition or with a specific license type.
Another incompatibility may occur if your product has sev­
eral editions, and you are trying to run a separately licensed
feature from one edition with the base product of a different
edition.

If the problem is incompatible editions or license types, re­

configure your product, or go to SPDC or SAP Support Por­
tal and check in the incorrect license and regenerate a li­
cense for the correct edition or license type.

SySAM Users Guide

62 PUBLIC Troubleshooting SySAM Errors
9.2.5 Problems With Served License Deployment Models

Check these typical issues if you are experiencing any problems with a served license model.

Possible Cause Solution

The license server may not be running. Verify that the license server is running by entering this com­
mand from the bin directory on the license server host:

sysam status

If the license server is not running, restart it.

The license server is running, but does not contain the de­ Enter the following command to determine if the license
sired license. server is trying to grant a license for the licensed feature you
are trying to use, where <feature_name> is the name of
the separately licensed product feature for which the license
server failed to check out a license:

sysam status -f <feature_name>

If the license is generated for one edition or license type, and

the product configured to use another, go to SPDC or SAP
Support Portal and generate the correct licenses for your
product or feature.

All licenses may be in use; that is no licenses are available for If the output from sysam status -f
checkout.
<feature_name> indicates that there are no available li­
censes:

● Go to SPDC or SAP Support Portal and generate addi­

tional licenses; or,
● If the product is using Floating License (FL) type li­
censes, you can shut down other instances of the prod­
uct or feature you are using, running on other machines,
to free licenses. See Controlling License Use with the
SySAM Options File [page 41].

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 63
Possible Cause Solution

Cannot connect to the license server Ensure that the client can connect to both TCP/IP ports
used by the license server. If there is a firewall, fix the ports
used by both lmgrd and the SYBASE vendor daemon (the
license server's constituent processes), and set up the fire-
wall or VPN policies to allow access to both ports. The li­
cense server's SYBASE.log file shows the port numbers to
be fixed:.

19:04:47 (lmgrd) lmgrd tcp-port 27010

19:04:47 (lmgrd) Starting vendor
daemons ...
19:04:47 (lmgrd) Starting vendor
daemon at port 27011

You can run telnet from the client machine to check that the
ports can be accessed:

telnet keyserver 27010

telnet keyserver 27011

See Access Through a Firewall or VPN [page 47].

9.3 Error Messages

Learn about common error messages you may encounter with SySAM.

# Message

#131231 This error message indicates

that your product cannot obtain
a license and the grace period
has expired.

License for
feature could not
be checked out
within the grace
period and has now
expired.

For example:

License for
ASE_CORE could not
be checked out
within the grace
period and has now
expired.

SySAM Users Guide

64 PUBLIC Troubleshooting SySAM Errors
# Message

#131239 This error message indicates the

cause of a failure, and is followed
by additional details.

Failed to obtain
quantity
license(s) for
feature feature
from License
Server host.

If the license server is not

known, a general message is
given:

Failed to obtain
quantity
license(s) for
feature feature
from license files
or servers.

#131250 This warning message indicates

that you are functioning in a
grace period and that your li­
cense will expire.

License for
feature will
expire
license_expiry_date
.

For example:

License for
ASE_CORE will
expire Wed May 24
17:02:39:2009.

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 65
# Message

#131251 This warning appears when you

exceed the number of available
licenses and have obtained a li­
cense on overdraft.

The total number

of available
licenses for
<feature> has been
exceeded by
<overdraft_amount>
and license usage
is now in
overdraft.

For example:

The total number

of available
licenses for
ASE_CORE has been
exceeded by 1 and
license usage is
now in overdraft.

#131252 Informational message indicat­

ing when a license is obtained.

Checked out
license for
<quantity>
<feature>
(<license_version>
/
<license_expiry> /
<license_identifier
>)

For example:

Checked out
license for 1
ASE_CORE
(2005.1231/
permanent/1343
09DD 6920 420A).

SySAM Users Guide

66 PUBLIC Troubleshooting SySAM Errors
# Message

#131254 This warning appears when a li­

cense cannot be obtained and is
issued on grace.

Installation Grace:

Checked out grace

license for 1
ASE_CORE
(2005.0425) will
expire Thu May 25
16:11:31 2009.

 Note
In the above example, the
highlighted version
2005.0425 is the version re­
quested by the product, not
the license_version, because
no license has been ob­
tained.

Runtime Grace:

Checked out graced

license for 1
ASE_CORE
(2008.0831/
permanent/1A37
58B3 72B4 7546)
will expire Mon
Sep 01 00:00:00
2008.

Support Time Grace (does not

Expire):

Checked out
support-graced
license for 1
ASE_CORE
(2008.0831/
permanent/1A37
58B3 72B4 7546).

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 67
# Message

#131274 The warning notifies you of the

consequences of a grace period
or license expiration when the li­
cense is for the product itself.

WARNING: product
will shut down on
expiry_date,
unless a suitable
feature license is
obtained before
that date.

For example:

WARNING: ASE will

shut down on Wed
May 24
17:02:39:2009,
unless a suitable
ASE_CORE license
is obtained before
that date.

#131275 This warning message notifies

you of the consequences of a
grace period or license expira­
tion when the license is for a
product feature.

WARNING: product
functionality that
requires the
feature license
will be disabled
on expiry_date,
unless a suitable
feature license is
obtained before
that date.

For example:

WARNING: ASE
functionality that
requires the
ASE_ENCRYPTION
license will be
disabled on Wed
May 24
17:02:39:2009,
unless a suitable
feature license is
obtained before
that date.

SySAM Users Guide

68 PUBLIC Troubleshooting SySAM Errors
9.4 Contacting Technical Support

If you cannot resolve a SySAM problem, obtain as much information about your system, and the conditions
leading to the problem, as possible and contact Technical Support.

If you use an unserved license, obtain the following information:

● The product name, version, edition (if any).

● Optional product features that are enabled.
● The product error log or debug log output (if the product produces one), or a screenshot or copy of error
message text if not.
● The SySAM 2-enabled product or feature licenses saved in the $SYBASE/SYSAM-2_0/licenses
directory, which is on your local machine or in the product-specific license location.

If you use a served license, obtain the following information:

● The output from:

sysam diag <feature_name>

● The license server software version.

● The license server debug log file.
● The licenses that are saved in the licenses subdirectory of the SYSAM-2_0 directory on the license
server host machine.

To report a SySAM problem, go to SAP Support Portal Home and report the issue using the component for
the product that is using SySAM:

● BC-SYB-ASE for SAP Adaptive Server Enterprise

● BC-SYB-IQ for SAP IQ
● BC-SYB-REP for SAP Replication Server
● BC-SYB-PD for PowerDesigner

SySAM Users Guide

Troubleshooting SySAM Errors PUBLIC 69
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SySAM Users Guide

70 PUBLIC Important Disclaimers and Legal Information
SySAM Users Guide
Important Disclaimers and Legal Information PUBLIC 71
www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN