License scope

Licensed functions are activated and enforced within a defined license scope.

License scope refers to the following types of storage and types of servers with which the function can be used:

Fixed block (FB): The function can be used only with data from Fibre Channel attached servers. The Base Function, and Copy Services licensed functions are available within this scope.

Count key data (CKD): The function can be used only with data from FICON® attached servers. The Copy Services, Transparent Cloud Tiering, and z-synergy Services licensed functions are available within this scope.

Both FB and CKD (ALL): The function can be used with data from all attached servers. The Base Function, and Copy Services licensed functions are available within this scope.

Some licensed functions have multiple license scope options, while other functions have only a single license scope.

You do not specify the license scope when you order function authorization feature numbers. Feature numbers establish only the extent of the authorization (in terms of usable capacity), regardless of the storage type. However, if a licensed function has multiple license scope options, you must select a license scope when you initially retrieve the feature activation codes for your storage system. This activity is performed by using the IBM® Entitled Systems Support (ESS) website.

Note: Retrieving feature activation codes is part of managing and activating your licenses. Before you can logically configure your storage system, you must first manage and activate your licenses.

When you use the ESS website to change the license scope after a licensed function is activated, a new feature activation code is generated. When you install the new feature activation code into the storage system, the function is activated and enforced by using the newly selected license scope. The increase in the license scope (changing FB or CKD to ALL) is a nondisruptive activity. A reduction of the license scope (changing ALL to FB or CKD) is a disruptive activity, which takes effect at the next restart.