IK (Install Keys)

The IK (Install Keys) command adds, merges, deletes, and installs system keys, system resource license keys, and digital signature algorithm (DSA) keys. The command also activates processor license keys, sets partition processor performance characteristics, sends processor metering and consumption information, displays processor metering and consumption characteristics, and extracts DSA keys. It also adds, merges, deletes, installs, and activates the I/O license, the memory license, and the specialty engine licenses.

System keys enable you to access specific features or products and are maintained in a file called SYSTEM/KEYSFILE on your halt/load unit. System keys can include the following types:

  • Software file keys needed to install files from release media for a new release or for a new product between releases.

  • Software feature keys needed to access special optional products and features.

  • Software user keys needed to use certain software products

By design, system resource license keys are system-wide and license one or more partition processor images. Types of system resource license keys include processor keys, specialty engine keys, memory keys and IO keys. System resource license keys are maintained in system-wide inter-partition permanent storage.

The processor key licenses both a partition processor image and the business model associated with that image. A partition processor image consists of a processor count, the processor performance level, and the constraints on how the processors must be configured (such as non-redundant or redundant power domains). For example, a partition processor image of 4@100N/2 indicates that the partition is licensed for a development workload using four processors at Performance Level of 100, where all processors reside in a single non-redundant power domain. Processor image business model types includes base capacity, timed upgrade capacity, processing power metered usage, and process consumption usage.

On a multi-partition image, a single processor key contains embedded processor performance characteristics for all licensed partitions in the system; each active partition shares in the system-wide pool of partition images. Therefore, only one processor license key is active on the entire system at any time.

A DSA key set contains a Unisys system public DSA key and other relevant DSA information for a particular software level. The set enables you to unwrap Unisys software that has been wrapped and signed with a corresponding Unisys system DSA private key. Creation of public and private key pairs for use in signing wrapped files also requires information from an appropriate DSA key set. All DSA key sets are maintained in a file called SYSTEM/DSAKEYSFILE on your halt/load unit.

Syntax

── IK ───────────────────────────────────────────────────────────────────────────►
─►─┬───────────────────────────────────────────────────────────────────────────┬─┤
   ├─ ADD ── <key> ── : ── <password> ─────────────────────────────────────────┤
   ├─ <DELETE option> ─────────────────────────────────────────────────────────┤
   ├─ MERGE <file name> ───────────────────────────────────────────────────────┤
   ├─ SHOW ─┬────────────┬─┬──────────────────────────┬─┬──────────────────────┤
   │        └─ <string> ─┘ └─ KEYSFILE = <file name> ─┘ ├─ : PRINTER ──────────┤
   │                                                    └─ : FILE <file name> ─┤
   ├─ DSADELETE <DSA key set ID> ──────────────────────────────────────────────┤
   ├─ DSAMERGE <file name> ────────────────────────────────────────────────────┤
   ├─ <DSASHOW option> ────────────────────────────────────────────────────────┤
   ├─ IPACTIVATE ─┬─ <key ID> ─────────────────────────────────────────────────┤
   │              ├─ <partition image> ────────────────────────────────────────┤
   │              └─ <key ID> : ─┬─ <partition image> ─────────────────────────┤
   │                             └─ <image ID> ────────────────────────────────┤
   ├─ IPADD ── <key ID> ── : ── <password> ────────────────────────────────────┤
   ├─ IPDEACTIVATE ────────────────────────────────────────────────────────────┤
   ├─ IPDELETE ── <key ID> ────────────────────────────────────────────────────┤
   ├─ IPLIMIT ─────────────────────────────────────┬─ <RPM limit> ─────────────┤
   │                                               └─ <limit> ── % ────────────┤
   ├─ IPMERGE <keys file> ─────────────────────────────────────────────────────┤
   ├─ IPSEND ─┬─ ACTIVATION ───────────────────────────────────────────────────┤
   │          ├─ DEACTIVATION ─────────────────────────────────────────────────┤
   │          ├─ METER ────────────────────────────────────────────────────────┤
   │          ├─ REPORT ───────────────────────────────────────────────────────┤
   │          ├─ LOCAL ────────────────────────────────────────────────────────┤
   │          ├─ CONFIG ───────────────────────────────────────────────────────┤
   │          ├─ DATE ── <yyyymmdd> ───────────────────────────────────────────┤
   │          ├─ FILE ── <file name> ─┬────────────────────────────────────────┤
   │          │                       └─ ON <family> ──────────────────────────┤
   │          └─ INTERNAL ─┬───────────────────────────────────────────────────┤
   │                       └─ <#> ─┬─────────┬──┬──────────────────────────────┤
   │                               ├─ DAYS ──┤  └─ LOCAL ──────────────────────┤
   │                               └─ HOURS ─┘                                 │
   └─ IPSHOW ─┬────────────────────────────────────────────────────────────────┤
              ├─ ACTIVE ───────────────────────────────────────────────────────┤
              ├─ ALL ──────────────────────────────────────────────────────────┤
              ├─ <key ID> ─────────────────────────────────────────────────────┤
              ├─ METER ────────────────────────────────────────────────────────┤
              └─ REPORT ───────────────────────────────────────────────────────┘

<key>

One or more fields, separated by a hyphen (-). Each field consists of one or more alphanumeric characters, with no embedded blanks.

<password>

10 to 17 characters.

<DELETE option>

 ── DELETE ─┬─ <key> ───────────────────────────────────────────────────┬───┤
            ├─ ALL ── <string> ─┬───────────────────────────────────────┤
            │                   └─ KEYSFILE ── = ── <file title> ───────┤
            └─ ALL EXCEPT ── <string> ── KEYSFILE ── = ── <file title> ─┘
            

<DSASHOW option>

── DSASHOW ─┬──────────┬─┬─────────────────────────────────┬────────────────┤
            └─ STRING ─┘ └─ KEYSFILE ── = ── <file name> ──┘
─►─┬──────────────────────────┬─────────────────────────────────────────────┤
   └─ : KEYSFILE <file name> ─┘

<partition image>

── <number of processors> ── @ ── <processor performance level> ─┬─ N ─┬────┤
                                                                 └─ R ─┘ 

N = nonredundant

R = redundant

<image ID>

── <processors> ── @ ── <processor performance level> ─┬─ N ─┬─────────────┤
                                                       └─ R ─┘ 

<custom processor set #>

On systems that support custom processor sets, a value of 0 designates the standard processor set and a value of 1 through n (where n is the maximum number of custom processor sets as specified in the performance key) designates a custom processor set.

Explanation

IK

Displays the syntax diagram for the IK command.

IK ADD <key> : <password>

Adds the specified key to the system keys file *SYSTEM/KEYSFILE on the halt/load family. This process creates a new version of the file and removes the old version. The total length of the key, the colon (:), and the password must not exceed 150 characters.

IK DELETE <key>

Deletes the specified key from the system keys file *SYSTEM/KEYSFILE on the halt/load family, creates a new version of the file, and removes the old version.

IK DELETE ALL <string>

Deletes any keys that begin with the specified string from the keys file on the Halt/Load unit, creates a new version, and removes the old version.

 Caution

Use of the ALL option can result in a keys file that no longer contains the keys needed to run your system.

Even under normal circumstances there is a risk of inadvertently deleting keys that are still in use. Before using the ALL option, perform both of the following:

  • Copy your active keys file to disk or tape.

  • Ensure that your active keys file is secure.

Because of the potential risk associated with the ALL option, it is recommended that you use the alternate file option and verify the results with the IK SHOW option before replacing your active file.

To minimize chances of deleting needed keys from your active keys file, the following restrictions have been applied to strings:

  • Your string must contain at least three characters.

  • You cannot specify the current SSR release level, the two preceding SSR levels, or a future SSR level. The first two characters in a numeric string are taken as the SSR level.

    For example, if the current SSR level is 53.1, levels 54.1, 53.1, 52.1, and 51.1 are protected.

  • You cannot specify a string that begins with the characters "UL-" or "00-".

When any of these conditions are detected, the system terminates your request with an UNRECOGNIZED REQUEST message.

IK DELETE ALL <string> KEYSFILE = <file title>

Deletes the specified key or keys matching <string> from the specified alternate keys file. In the case of a DELETE ALL request, restrictions described above do not apply.

IK DELETE ALL EXCEPT <string> KEYSFILE = <file title>

Deletes any key from the alternate file that does not match the specified string. Following are restrictions for deleting multiple key alternate files:

  • The string must contain at least one character.

  • You must specify an alternate keys file with a DELETE ALL EXCEPT request.

  • On a DELETE ALL EXCEPT request, the <string> that you enter must match at least one key; otherwise, it is terminated with a KEY NOT FOUND message.

The primary purpose behind the alternate keys file delete capability is to provide an environment in which you can perform keys file maintenance without the risk of impacting site production.

IK MERGE <file name>

Merges the keys from the specified keys file into the system keys file *SYSTEM/KEYSFILE on the halt/load family, creates a new version of the file, and removes the old version.

IK SHOW

IK SHOW <string>

Display keys in the system keys file *SYSTEM/KEYSFILE on the halt/load family. If you omit the string parameter, the system displays all strings. If you specify a string parameter, the system displays only keys that begin with the parameter.

IK SHOW KEYSFILE = <file name>

IK SHOW <string> KEYSFILE = <file name>

Display keys in the specified keys file. If you omit the string parameter, the system displays all keys. If you specify a string parameter, the system displays only keys that begin with the parameter.

IK SHOW <string> KEYSFILE = <file name> :PRINTER

IK SHOW <string> KEYSFILE = <file name> :FILE <file name>

List the specified keys in a file. Use PRINTER to specify a line printer file and FILE to specify a disk file. If a disk file with the specified name already exists, the command generates an error message.

IK DSADELETE <DSA key set ID>

This command deletes the specified DSA key set from the system DSA keys file, creates a new version of the file, and removes the old version.

IK DSAMERGE <file name>

This command merges the DSA key sets from the specified DSA keys file into the system DSA keys file, creates a new version of the file, and removes the old version.

IK DSASHOW

IK DSASHOW <string>

These commands display DSA key set IDs and their corresponding software levels in the system DSA keys file. If you omit the string parameter, the system displays all IDs. If you specify a string parameter, the system displays only DSA key set IDs that begin with the parameter.

IK DSASHOW KEYSFILE = <file name>

IK DSASHOW <string> KEYSFILE = <file name>

These commands display DSA key set IDs and their corresponding software levels in the specified DSA keys file. If you omit the string parameter, the system displays all IDs. If you specify a string parameter, the system displays only key set IDs that begin with the parameter.

IK DSASHOW : KEYSFILE <file name>

IK DSASHOW <string> : KEYSFILE<file name>

IK DSASHOW KEYSFILE = <file name> : KEYSFILE <file name>

IK DSASHOW <string> KEYSFILE = <file name> : KEYSFILE <file name>

These commands extract the specified DSA key sets and store them in another DSA keys file indicated by <file name> of the option : KEYSFILE. If this file does not exist, a new one is created.

IK IPACTIVATE

This command reactivates the MCP partition license on a partition that was previously deactivated. The response includes a confirmation prompt, after which the MCP partition reactivation sequence is started and a new activation code is provided.You can use the commands IK IPSHOW ALL and LOG CON COD UC to retrieve the activation code.

IK IPACTIVATE <key ID>

Activates a specific processor license key for the system. Use the IK IPSHOW system command to list the available valid key IDs. Changing the system processor license key transforms the respective partition processor images for each active partition. If the new key is the alternate processor license key or a change from a temporary key to the previously active permanent key, each partition automatically acquires its previous partition processor image. If the new key was not the alternate processor license key, each partition is automatically assigned the default partition processor image (the lowest-performance processor image licensed by that key). If this is not the desired image, use IK IPACTIVATE <partition image> to select the desired image. Verify the respective partition processor image licenses for all running partitions after the activation of a new processor license key.

IK IPACTIVATE <partition image>

Activates a specific partition processor image license for a specific partition using the current active processor license key. A partition processor image license consists of three items: the number of licensed processors, the associated processor performance level, and the constraints on how the processors must be configured (nonredundant or redundant power domains). Examples include 1@4N, 4@5R, 8@9N, and so forth. The IK IPSHOW ACTIVE system command displays a list of available and stealable images from which to choose. Activation of an available image license does not affect image licenses of any other partition. Activation of a stealable image license resets the respective images for non-local partitions to the default image license. Verify the respective partition processor image licenses for all running partitions after the activation of a stealable image license.

IK IPACTIVATE <key ID>:<partition image>

Activates a specific processor license key for the system and a specific processor image license for a partition. Valid key IDs and images are available using the IK IPSHOW system command. You can activate any of the displayed images. Choosing a new processor license key might reset partition processor image licenses for all active partitions. Verify the respective partition processor image licenses for all running partitions.

IK IPACTIVATE <key ID>:<image ID>

Activates a specific processor license key for the system and a specific processor image license identified by the ordinal image identifier. The ordinal image identifier is available using the IK IPSHOW command.

IK IPADD <key string>:<password>

Adds a single processor performance key into Server Control or the Console. Keys added from any partition are visible to all partitions.

IK IPDEACTIVATE

For ClearPath MCP Software Series systems, initiates the deactivation of an MCP partition license for an MCP partition that is actively licensed and executing a workload. The response includes a deactivation code, which you can use to deactivate the license.

See the MCP Resource Licensing Guide for detailed information.

IK IPDELETE <key ID>

Deletes one or more processor performance keys from a keys file into Server Control or the Console.

IK IPLIMIT <RPM limit>

Sets the maximum performance level of the partition to a value between the contracted baseline and ceiling. This takes effect immediately, and system meters account for the new ceiling value in recorded workload delivery. Note that, although <limit> is a specific RPM value, the system can set the limit only to a restricted set of RPM values, based upon the supported performance level settings of the CPUs. As a result, if the selected <limit> value is not supported by the CPUs, the RPM value that is closest (and less than) the requested <limit> value is selected. System displays show the requested <limit> as TARGET LIMIT, and the selected <limit> as ACTUAL LIMIT.

Each system has a minimum performance level that is supported by Unisys. If you set the processor performance to a level that is below that minimum supported performance level, the system adjusts the requested processing power value only to the minimum supported level. Subsequent system displays show the adjusted limit as TARGET LIMIT.

IK IPLIMIT <percentage> %

Sets the partition level of performance for standard processors to the specified percentage of system-wide licensed performance. This command is valid for nonmetered systems.

IK IPMERGE <keys file>

Merges one or more processor performance keys from a keys file into Server Control or the Console. If the keys file contains system, I/O, and memory keys, those keys are loaded into Server Control along with the processor key or keys. Keys merged from any partition are visible to all partitions.

IK IPSEND ACTIVATION

IK IPSEND CONFIG

IK IPSEND DEACTIVATION

IK IPSEND LOCAL

IK IPSEND METER

IK IPSEND DATE <yyyymmdd>

IK IPSEND FILE <file name>

IK IPSEND FILE <file name> ON <family>

IK IPSEND INTERVAL

IK IPSEND INTERVAL 0

IK IPSEND INTERVAL <#> DAYS

IK IPSEND INTERVAL <#> HOURS

IK IPSEND INTERVAL <#> DAYS LOCAL

IK IPSEND INTERVAL <#> HOURS LOCAL

IK IPSEND REPORT

Generates and sends an e-mail message that contains either a metered usage report or a CPM consumption report to the currently configured e-mail destinations. The configured e-mail destinations are specified in the halt/load family file “METER/EMAIL/DESTINATIONS” ( for metering reports only) or the “EMAIL/DESTINATIONS” file (for both metering and consumption reports).

Archived processor power metering data files are found on the halt/load family using the following naming convention:

  • E-mail report:

    *METERDATA/<yyyymmdd>/<hhmm>/EMAIL

  • Report attachment:

    *METERDATA/<yyyymmdd>/<hhmm>/ATTACH

Archived processor consumption data files are found on the halt/load family using the following naming convention:

  • E-mail report:

    *CONSUMPTION/”<Instance ID> <yyyymmdd> <hhmm>SUMMARY.TXT”

  • Report attachment:

    *CONSUMPTION/”<Instance ID> <yyyymmdd> <hhmm>ATTACHMENT.TXT”

Command

Subject

Description

ACTIVATION

Activation Metering or Processor Consumption Report

Used by Unisys to identify the "begin billing" characteristics of the system.

CONFIG

COD license key and hardware configuration Interim Meter Report

Used for upgrade processing.

DEACTIVATION

Deactivation Metering or Processor Consumption Report

Used by Unisys to identify the "end billing" characteristics of the system.

LOCAL

Interim Metering or Processor Consumption Report

Sends to local addresses only. It can be used for tracking purposes.

METER

Interim Metering Report

Sends to all addresses. It can be used to test the e-mail connection to Unisys or when Unisys requests an interim report.

REPORT

Interim Processor Consumption Report

Sends to all addresses. It can be used to test the e-mail connection to Unisys or when Unisys requests an interim report.

DATE <yyyymmdd>

Monthly Metering or Processor Consumption Report

Manually forces the resending of a previously generated monthly report to the currently configured e-mail destinations.

You can use this form when the report can be found in the standard location.

FILE <file name> on <family>

Monthly Metering or Processor Consumption Report

Manually forces the resending of a previously generated monthly report to the currently configured e-mail destinations.

You can use this form if the report has been saved using a different name or has been moved off the halt/load family.

INTERVAL

Monthly Metering or Processor Consumption Report

Automatically generates an interim report on a schedule more frequently than once a month. The current measured usage is sent to the configured E-mail destinations. Including the LOCAL option removes Unisys from the distribution list.

The valid range for the <#> variable is 0 through 24.

The monthly report mechanism is not affected by this feature.

See “Sending a Missing Monthly Metering E-Mail Report to Unisys” later in this topic for more information.

IK IPSET STD: <custom processor set number> + <IP identifier>

On systems that support custom processor sets, assigns a processor to the custom processor set.

IK IPSET STD: <custom processor set number> − <IP identifier>

On systems that support custom processor sets, removes a processor from the custom processor set. A custom processor set number of 0 designates the standard processor set, and a custom processor set number of 1 through n (where n is the maximum number of custom processor sets as specified in the performance key) designates a custom processor set.

IK IPSHOW

Displays general active processor licensing information and general key information for all keys installed into Server Control or the Console.

IK IPSHOW ACTIVE

Displays detailed active processor licensing information and detailed key information for the currently active key.

IK IPSHOW ALL

Displays detailed active processor licensing information and detailed installed key information for all keys installed into Server Control or the Console.

IK IPSHOW <key ID>

Displays detailed key information for a specific key installed into Server Control or the Console. Key IDs can range from 1 to 999. If the key ID is that of the currently active key, then detailed active licensing information is also displayed.

IK IPSHOW METER

Displays an interim system processing power metering report on the ODT.

IK IPSHOW REPORT

Displays an interim processor consumption report on the ODT.

Examples

Example 1

This example adds the key 591-CANDE-CDE-S with the password AHQWOMNWEFUMDQE:

IK ADD 591-CANDE-CDE-S:AHQWOMNWEFUMDQE
   GOOD KEYSFILE ACTION

Example 2

This example deletes the key 591-CANDE-CDE-S:

IK DELETE 591-CANDE-CDE-S
   GOOD KEYSFILE ACTION

Example 3

This example merges SYSTEM/KEYS/591 ON NI to the *SYSTEM/KEYSFILE on the halt/load family, creates a new version of the keys file, and removes the old version:

IK MERGE SYSTEM/KEYS/591 ON NI
   GOOD KEYSFILE ACTION

Example 4

This example displays the specified key, 591-ALGOL-ALG:

IK SHOW "591-ALGOL-ALG"
   --- KEY -------------------- EXPIRES --- LICENSE ID ---------
   591-ALGOL-ALG

Example 5

This example displays the keys in the specified keys file, SYSTEM/KEYS/591 ON TEST:

IK SHOW KEYSFILE = SYSTEM/KEYS/591 ON TEST
  --- KEY -------------------- EXPIRES --- LICENSE ID ---------
  591-ADDSPROPERTIES-SAP
  591-ADDSPROPERTIES-SAP-S
  591-ALGOL-ALG
  591-ALGOL-ALG-S
  .
  .
  .

Example 6

This example deletes the DSA key set specified by the SSR591DSAKEYID DSA key set ID:

IK DSADELETE SSR591DSAKEYID
   GOOD KEYSFILE ACTION

Example 7

This example merges SYSTEM/DSAKEYSFILE/591 ON NI with the system DSA keys file, creates a new version of the DSA keys file, and removes the old version:

IK DSAMERGE SYSTEM/DSAKEYSFILE/591 ON NI
   GOOD KEYSFILE ACTION

Example 8

This example displays DSA key set IDs and their corresponding software levels in the DSA keys file SYSTEM/DSAKEYSFILE/591:

IK DSASHOW KEYSFILE=SYSTEM/DSAKEYSFILE/591
   ---- Software Release --  ------ DSA Key Set ID ----
                   591                   SSR591DSAKEYID

Example 9

This example extracts DSA key sets whose IDs begin with SSR591 from the file *SYSTEM/KEYSFILE on the halt/load family to the new DSA keys file SYSTEM/KEYSFILE/SSR591 ON MCPMAST:

IK DSASHOW "SSR591" : KEYSFILE SYSTEM/KEYSFILE/SSR591 ON MCPMAST

GOOD KEYSFILE ACTION

Example 10

This example illustrates how keys associated with ClearPath MCP Release 18.0 (release identifier 59.1) can be deleted from an active keys file.

The active keys file is first backed up to tape. The prefix string is verified with an IK SHOW command. Keys associated with release identifier 59.1 are removed. Finally, the delete is verified.

COPY *SYSTEM/KEYSFILE FROM HLUNIT(PACK)TO TAPE(SERIALNO="KYS")
IK SHOW "591"
  ---KEY --------------------EXPIRES ---LICENSE ID -----------
  591-ADDSPROPERTIES-SAP
  591-ADDSPROPERTIES-SAP-S
  591-ALGOL-ALG
  591-ALGOL-ALG-S
  .
  .
  .
IK DELETE ALL "591"
   IK DELETE:GOOD KEYSFILE ACTION
IK SHOW "591"
   NO KEYS FOUND

Example 11

This example illustrates how to send a processing power metering information report by e-mail:

IK IPSEND METER
   IK IPSEND: METERING INFORMATION SENT

Example 12

This example illustrates the display of metering information on a prepaid metering system:

IK IPSHOW METER
Report Type      Interim
    Version      2
   Interval      Nov 18, 2004 15:28:38 to
      (UTC)      Nov 24, 2004 20:11:47
  
Key  41A38DC3[1]  Projected Utilization  Avg Workload   Current Utilization
Image  2@27R/4
    Time                534,508 seconds                       2,415 seconds
    Total Used       46,801,875 RPM sec        88 RPM       211,459 RPM sec
--> Metered                  18 RPM month (standard)
==>                           1 MIPS month (standard) ID=012000ABE41A38DC301
Image  4@57N/2      (Most recent inter-partition update)
    Time                534,508 seconds                       1,747 seconds
    Total Used       43,233,026 RPM sec        81 RPM       141,304 RPM sec
--> Metered                  16 RPM month (standard)
==>                           1 MIPS month (standard) ID=012000ABE41A38DC302

Example 13

This example illustrates the display of metering information on a base-plus-use metering system:

IK IPSHOW METER
Report Type      Interim
    Version      2
   Interval      Nov 18, 2004 15:28:38 to
      (UTC)      Nov 24, 2004 17:00:38

Key  41A3560E[0]  Projected Utilization  Avg Workload   Current Utilization
Image  8@57R/1
    Time                545,410 seconds                       1,848 seconds
    Base         21,816,400,000 RPM sec    40,000 RPM
    Maximum                                48,381 RPM
    Total Used        9,345,971 RPM sec        17 RPM        31,667 RPM sec
    Metered                   0 RPM sec
--> Billable                  0 RPM month 
==>                           0 MIPS month            ID=012000ABE41A3560E01
Image  8@45N     Non-Metering Partition Image
Image  4@57N/2
    Time                545,410 seconds                       1,848 seconds
    Base                      0 RPM sec         0 RPM
    Maximum                                33,680 RPM
    Total Used       42,289,541 RPM sec        78 RPM       143,289 RPM sec
    Metered          42,289,541 RPM sec
--> Billable                 16 RPM month
==>                           1 MIPS month            ID=012000ABE41A3560E03

Example 14

This example shows the display of usage information on a ClearPath MCP Software Series System licensed for consumption-based usage:

IK IPSHOW REPORT

Report                                                                   
   Posted:              2018-06-20 19:28:45 (UTC)                        
                        2018-06-20 15:28:45 (local)                      
   Type:                Interim Consumption Summary                      
   Version:             1                                                
   Interval:            2018-06-01 00:00:15 - 2018-06-20 19:28:45 (UTC)  
                        2018-05-31 20:00:15 - 2018-06-20 15:28:45 (local)
   Active Seconds:      1,711,710                                        
                                                                         
Consumption                                                              
   CSS Processor Secs:  2,120,300                                        
   Calibration Ratio:   0.955                                            
                                                                         
Client Environment                                                       
   Model:               GE1500                                           
   OS:                  MCP                                              
   Instance ID:         123456789-886784829                              
   MCN:                 123456789                                        
   SCN:                 1234567                                          
   Partition Name:      USTRMCP22611    

Example 15

This example shows the display in response to an IK IPSHOW ALL command on a system licensed for metered usage.

IK IPSHOW ALL                                                          

SYSTEM MCN/MACH  917959519/0501   PARTITION 1   ACTIVE KEY 1           
  CURRENT IMAGE  16@100N (RPM ACTUAL 280106)                           
  PARTITION [1]  16@100N/1 (RPM MAX 280106 TARGET 280106)              
                                                                       
 ID  TYPE      STATUS     IMAGES                                       
                                                                       
  1  PERM  HA  ACTIVE     16@100N/1 (RPM MAX 280106)                   
                          Prepaid usage    Report day 1  ID 5952AF20   
               IP1-YMGW8ZC33P5Y61T07R60QSW0YZCY75021AHWJ5G50B1Y04DP54Y2

Example 16

This example shows the display in response to an IK IPSHOW ALL command on a ClearPath MCP Software Series System licensed for consumption-based usage:

IK IPSHOW ALL                                                           

SYSTEM MCN/MACH  123456789/GE1500   PARTITION 1   ACTIVE KEY 1          
  CURRENT IMAGE  4@100%                                                 
  PARTITION [1]  4@100%  General Purpose                                
                                                                        
 ID  TYPE      STATUS     IMAGES                                        
                                                                        
  1  PERM      ACTIVE     4@100%  General Purpose                       
                          CPM Consumption                               
               IP1-JM29TUNAW11RY78R8HWQRES4DKDE56PT27XXAQAR8W8RTU1ANH4B 

Example 17

This is a series of examples of the IK IPSEND INTERVAL command.

IK IPSEND INTERVAL

Responds with the current settings.

IK IPSEND INTERVAL 0

Resets or disables the interval feature.

IK IPSEND INTERVAL 12 HOURS

Sends an interim report every 12 hours.

IK IPSEND INTERVAL 16 DAYS

Sends an interim report bimonthly.

IK IPSEND INTERVAL 7 DAYS LOCAL

Sends an interim report every week to the configured e-mail destinations, except for the Unisys destination.

Considerations for Use

Retaining the *SYSTEM/KEYSFILE on the Halt/Load Family

For some products to be fully functional after their installation, it might be necessary for a particular key to be present. Therefore, it is recommended that you retain the *SYSTEM/KEYSFILE on the halt/load family after the product is installed. Moreover, you should back up this file after you install a software release and after you use the IK MERGE command to install keys for a particular product or feature. Then, if your *SYSTEM/KEYSFILE is ever accidentally deleted or destroyed, you can easily restore the backed up version to your halt/load family.

Timeout Limitations

The system closes the KEYSFILE after 15 seconds of no activity.

Sending a Missing Monthly E-Mail Report to Unisys

Metering reports and processor consumption reports are automatically sent by e-mail monthly from the server to Unisys. Occasionally, a problem might arise (for example, a network connectivity issue) and prevent the report from being received by the Unisys mailbox. When an expected report is not received, Unisys contacts you and provides instructions on how to locate the files that contain the saved e-mail and the related attachment.

To resend a monthly metering or processor consumption e-mail report, choose one of the following commands:

  • IK IPSEND DATE <date>

    The specified <date> is in the format YYYYMMDD and represents the date embedded in the archived e-mail file name.

    The archived e-mail file names are, as follows:

    • Archived metering e-mail:

      *METERDATA/<yyyymmdd>/<hhmm>/EMAIL

    • Archived metering e-mail:

      *CONSUMPTION/“<Instance ID><yyyymmdd><hhmm>SUMMARY.TXT”

  • IK IPSEND FILE <file title>

    The specified <file title> is the title of the saved e-mail file. It is either the standard archived file name or it is a non-standard file name if it has been renamed.

One of the following three responses appears on the ODT after you send the command:

  • REPORT RESENT

    This message indicates that the specified metering report or processor consumption report and the corresponding attachment were located and sent.

  • REPORT NOT RESENT

    This message indicates that there was a problem in either accessing the metering report or processor consumption report, or verifying it as a valid report.

  • wREPORT RESENT WITH NO ATTACHMENT

    This message indicates that the specified metering or processor consumption report was located and sent. However, the corresponding attachment file was either not located, there was a problem reading the file, or the attachment failed validation.

The system log also receives an entry to indicate that a RESEND function was issued.