sysamcap Utility

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.

      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.

Examples

• Licensing a machine to allow any number of VMware virtual machines –
  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).
     
     Sybase 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.
     
     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 (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.
• Licensing 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 –
  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
     
     Using this configuration, licensing is based on 4 logical processors, 1 processor core and 1 processor chip.
     
     Sybase 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 Sybase Product Download Center.
     
     PARTITION-ID=83f828fb
     

  3. Set the environment variable:

     export SYBASE_SAM_CAPACITY=PARTITION

  4. Start the product.
• Licensing a Solaris container –
  1. Log in to the container, for example, using an xterm running the Korn shell.
  2. If desired, determine the name of the resource set by which the product will be governed.
  3. Run sysamcap, specifying resource set licensing and optionally the desired 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).
     
     Sybase 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.