Manually activating using the Support Element

To manually activate an installed upgrade record using the Support Element, follow these steps:

  1. From the Perform Model Conversion window, click Temporary upgrades and Manage. The Temporary Upgrades window opens.
    Temporary Upgrades window

    See Understanding the content of the Installed Records page in the Temporary Upgrades window for details on the fields displayed on the Installed Records page in the Temporary Upgrades window.

  2. If you want to see more details about a record, such as the remaining test/real activations, the expiration dates, and whether the upgrade is controlled by tokens, select the record and click Details.... The Record Details window opens.
    For On/Off CoD records:
    Record Details - On/Off
    The data in the Capacity Pools (Remaining) section is determined by the type of On/Off CoD upgrade record:
    • If the On/Off CoD upgrade is not controlled by tokens, the values in the Processor Tokens table and the value of MSU Tokens is set to N/A.
    • If the On/Off CoD upgrade is controlled by tokens, in the Processor Token table, the value of CPs is set to N/A, and the value of each specialty engine is set to the number of tokens purchased. (A token represents the activation of one engine of that type for one day.)

      MSU Tokens represents the number of tokens of processing capacity available based on the upgrade configurations and the number of days selected when you placed your order. MSU Tokens applies to CP engines. For CP engines, a token represents an amount of processing capacity resulting in one MSU of software cost for one day (an MSU day).

    In the Time Limits section for post-paid On/Off CoD records, Record Expiration Date displays the date the record expires. For prepaid On/Off CoD upgrade records, Record Expiration Date is set to N/A. For all On/Off CoD upgrade records, Real Activation Days Remaining and Test Activation Days Remaining is set to N/A.

    Note: To change the record description, edit or replace the existing description in the Description field, and then click Update Description. On the confirmation panel, click OK.
    For CBU upgrades:
    Record Details - CBU

    If the value of the Status field displays (Default) or (Attention!, Default), this record is set as the default CBU record. The default CBU record is used to support the legacy API interface by enabling the Force activation option on the Change Activation Levels window. (See Step 3 for information on setting the Force activation option.) Enabling and setting the Force activation option allow the APIs to activate or deactivate all the resources in the default CBU record. If there is no default CBU record specified, the oldest CBU record is used. To set a CBU record as the default CBU record, select the Set as Default CBU button located at the bottom of the Record Details window.

    In the Capacity Pools (Remaining) section for a CBU record, Processor Tokens and MSU Tokens are set to N/A. Real Activations and Test Activations display the number of real or test activations remaining for this upgrade record.

    In the Time Limits section for a CBU record, Record Expiration Date displays the date the record expires. Real Activation Days Remaining and Test Activation Days Remaining display the number of days allowed for a real or test activation, if the record is not active. Otherwise, Real Activation Days Remaining and Test Activation Days Remaining display the number of days remaining for the activation.

    Note: To change the record description, edit or replace the existing description in the Description field, and then click Update Description. On the confirmation panel, click OK.
  3. To activate processors in a record, select the record and click Add processors.... (You can perform this task from either the Temporary Upgrades window or the Record Details window.) Depending on the type of record you select, the Change Activation Levels window opens:
    For On/Off CoD records:
    Change Activation Levels On/Off - Activate
    For CBU records:
    Change Activation Levels - CBU

    The table shows all the possible target model capacity identifiers that can be activated with this record. The values in this table are based on the configuration selections you set when you ordered the record on Resource Link®, the current permanent configuration, and the available PUs in the system.

    The Processors section identifies the count for each processor type that you can select.

    The Activation Options section is visible for records that allow test activations. If a record is already activated for test, it must be deactivated prior to real activation.

    Force activation is only available for CBU records and can only be set on the default CBU record. (Refer back to Step 1 for information on setting the default CBU record.) It is supported for legacy CBU activations because legacy activations did not allow the user to specify levels. If the Force activation is checked, the record is activated to its maximum regardless of what resources are available. That is, the CP table refreshes with a single entry with the maximum values for the record and the other processor types are automatically restricted to their maximum LICCC values. The machine will activate as many resources as it can based on what is available and the remaining resources become pending PUs. Pending PUs become active as soon as resource become available. (This information can be seen on the Records Details window.)

  4. Make your changes and click OK. A window opens showing the new activation levels you selected.
    Temporary Upgrades Confirm Activation
  5. If you want to continue with the changes you made, click Yes.

    The changes you made are now active and are reflected in the Temporary Upgrades window.

    Temporary Upgrades On/Off - Activation