3. Enter an applykey  command at the following dscli  command prompt. The  -file parameter specifies the key file. The second parameter specifies the storage image. 

dscli> applykey -file c:\533x_75XXXX0.xml IBM.2107-75XXXX1 

Or you can apply individual keys: 

dscli> applykey -key f190-1234-1234-1234-1234-5678-1234-5678 IBM.2107-75XXXX1 CMUC00199I applykey: License Machine Code successfully applied to storage image IBM.2107-75XXXX1. 

4. Verify that the keys were activated for your storage unit by running the lskey  command, as shown in Figure 9-15. 

dscli> lskey Activation Key Authorization Level (TB) Scope ========================================================================== Base function 130 All Copy services 60 All Encryption Authorization on All Global mirror (GM) 60 All High Performance FICON for System z (zHPF) on CKD IBM HyperPAV on CKD IBM System Storage DS8000 Thin Provisioning on All IBM System Storage Easy Tier on All IBM z/OS Distributed Data Backup on FB Metro/Global mirror (MGM) 60 All Metro mirror (MM) 60 All Operating environment (OEL) 130 All Parallel access volumes (PAV) 90 CKD Point in time copy (PTC) 60 All RMZ Resync 60 CKD Remote mirror for z/OS (RMZ) 60 CKD z-synergy services 90 CKD 

For more information about the DS CLI, see the IBM DS8000 Series Command-Line Interface User’s Guide , SC27-8526. 

The BF license bundle needs to be installed before ranks can be formatted for FB (open systems). The zsS license bundle needs to be installed before ranks can be formatted for CKD (mainframe). 

## 9.3 Licensed scope considerations 

An increase in license capacity is concurrent. A deactivation (or decrease in license capacity) takes place only after one additional machine IML. Similar considerations apply to the license scopes: 

GLYPH<SM590000> The BF license and CS license are available with several license scopes, such as ALL , FB , and CKD . 

GLYPH<SM590000> An increase in license scope, for example, changing FB  or CKD  to ALL , is a concurrent activity. 

