HP OpenVMS Systems

HP Instant Capacity software provides the ability to instantly increase or decrease computing capacity on partionable HP enterprise servers. The Instant Capacity software provides the means to:

• Increase or decrease (load balance) system processing capacity (icapmodify command).

• View status and configuration of the system components (icapstatus command).

• Administer system identification and notification information (icapmodify command).

• If configured, send system asset reports through encrypted email to HP (ICAP_SERVER process on OpenVMS).

• Send configuration change notification, through encrypted email, to the specified system contact.

• Monitor and report system compliance (ICAP_SERVER process on OpenVMS).

For the OpenVMS equivalents of these commands, see DCL ICAP Commands in the Special OpenVMS-Specific Features and Considerations section.

Note: HP Instant Capacity for HP 9000 and HP Integrity Servers, also known as Instant Capacity or iCAP, was known in earlier versions as Instant Capacity on Demand, or iCOD. Although the commands, warning messages and error messages refer to the software as iCAP, some internal files might still refer to iCOD.

With Instant Capacity, you initially purchase an HP enterprise server with a specified amount of active processing capacity, and a specified amount of inactive processing capacity. This amount can vary based on your sales contract with HP.

Processing capacity consists of the system components:

• Processors containing cores
• Cell boards

For each type of component, the number of components that can be active is equal to the number of usage rights applied to the complex for that type of component. Components that are purchased with a part number identifying them as “Instant Capacity” and without the label “Right to Use” come without usage rights. Components that are not labeled “Instant Capacity” implicitly include usage rights that can be applied to any component of that type that is installed on the complex.

Prior to activation of an inactive component, you must obtain additional usage rights. The fundamental method is to purchase usage rights by purchasing the appropriate Instant Capacity products that include the label “Right to Use (RTU)”. HP then supplies an RTU codeword. When the codeword is applied to the HP enterprise server, the inactive component can be activated.

Additional methods for activating components for which usage rights have not been purchased include:

• If a server is a member of a Global Instant Capacity (GiCAP) group, and if extra capacity is available from other members of the group, capacity can be “borrowed” from another member of the group.

• You can purchase additional temporary capacity and apply the Temporary Instant Capacity (TiCAP) codeword in order to activate one or more cores temporarily. If a server is a member of a GiCAP group, temporary capacity can be shared among members of the group.

• You can temporarily activate one or more inactive cores using the Instant Access Capacity (IAC) provided with the initial purchase of the Instant Capacity component. Instant Access Capacity is the same as TiCAP except it is automatically provided with an Instant Capacity component and cannot be purchased separately. It provides an immediate buffer of temporary capacity in case extra capacity is needed before there is time to purchase an RTU or a TiCAP codeword.

Note: It is always a good idea to keep some quantity of temporary capacity in reserve. Purchase of codewords may take one or more days, so having a buffer of temporary capacity allows you to avoid delays in activation of additional cores. Instant Access Capacity provides this buffer initially, but as that capacity is depleted, ongoing purchases of additional temporary capacity are recommended to replenish it. Global Instant Capacity features, including the use of the icapmanage command, are not supported on OpenVMS.

Instant Capacity Software in Virtual Environment

Instant Capacity must be run on a partitionable system. In an Integrity Virtual Machine (VM) environment, Instant Capacity software provides meaningful functionality only on the VM Host system; it does not run on a virtual machine (also known as a “guest”).

Utility Pricing Solutions Portal

The Utility Pricing Solutions (or Instant Capacity) portal is located at the HP web site: http://www.hp.com/go/icap.

After you purchase a component without usage rights, HP sends you a letter containing instructions on how to obtain an RTU codeword from the Utility Pricing Solutions portal.

Instant Capacity Administration System

If asset reporting is configured, the ICAP_SERVER process sends asset reports, in the form of encrypted email messages, to the Instant Capacity Administration System, which saves information in the Instant Capacity database.

Instant Capacity Database
 

The Instant Capacity database is a repository on an HP (internal) corporate server that tracks system resources and provides the information for codeword generation. Note that this database should not be confused with a Global Instant Capacity database, which is created on a customer Group Manager system.

Fig: Instant Capacity System Elements

Core Activation and Deactivation

The ICAP command or the corresponding HP-UX foreign commands must be used on OpenVMS systems when stopping and starting CPUs in complexes containing iCAP components. To start cores on OpenVMS, use the ICAP ACTIVATE/CPU= command. To stop cores on OpenVMS, use the ICAP DEACTIVATE/CPU= command. HP recommends not to use START /CPU and STOP /CPU command or the corresponding system services in order to start or stop processor resources in an iCAP complex. When you enter the START /CPU command on an OpenVMS system in a complex containing iCAP resources, the ICAP_SERVER process validates that the start operation does not take the complex out of compliance. When you enter the STOP /CPU command, the CPU might restart at a later time if the count of intended active cores on the system is greater than the actual active cores. Using the START /CPU command can result in unintended consequences, such as an unexpected usage of temporary capacity or the deactivation of cores on the system or on another system in the complex. Using the STOP /CPU command can result in an unexpected restart of the core or the unexpected start of a core in another system in the complex.

Email Considerations

The iCAP software requires that SMTP mail be configured on the OpenVMS system to send email to the system contact. For more information about setting up SMTP mail, see your IP provider’s documentation.

Time zone Considerations

On OpenVMS systems, the ICAP_SERVER process performs routine Instant Capacity software tasks on a daily basis. A partition’s local time zone setting affects what time zone the ICAP_SERVER process uses for the timing of these tasks. Be sure that the time zone is set properly to ensure synchronization among the partitions.

On OpenVMS systems, the ICAP_SERVER uses the time zone settings defined by the SYS$STARTUP:TDF$UTC_STARTUP.COM file.

To view the time zone settings, enter the command
$ @sys$manager:utc$time_setup “show”

Enter the command
$ @sys$manager:utc$time_setup

and follow the menu instructions to modify the time zone setting for the iCAP partition.

Restrictions

• Instant Capacity software on OpenVMS Version 8.3-1H1 does not support HP virtual partitioning (vPars) since OpenVMS itself doesn’t support vPars.

• Global Instant Capacity features, including the use of the icapmanage command, are not supported on OpenVMS.

• Instant Capacity on OpenVMS does not support internationalization. Only English language support is provided.

• LPMC and HPMC are not available on OpenVMS systems.

Removing Instant Capacity Software

• Maintain the HP Instant Capacity software on each HP-UX or OpenVMS partition in the system. The Instant Capacity software is a nonintrusive, low-overhead software module that resides on the partition.

• Migrate to later Instant Capacity software versions as they become available. For specifics about your individual program requirements, see the Utility Pricing Solutions contract from HP or your authorized channel partner.

Note: HP recommends not to remove the Instant Capacity software. Participants in the Utility Pricing Solutions program who do not meet these requirements may be in breach of contract. This can result in unnecessary expense for both the program participant and HP.

The emulator makes extensive use of OOP, particularly of the features offered by the C++ language.  While C and C++ are reviled by some for their perceived cryptic nature (although there is no rule that says C or C++ code has to be cryptic), they are commonly considered to be the languages of choice for low-level, portable programming found in operating systems, device drivers, and emulators.  C and C++ give programmers a level of control over the bits and bytes of their code few other high-level languages offer, and C and C++ compilers that produce blazingly fast code are available for virtually any platform.

iCAP Product Versions and Supported Platforms

Special Requirements

Dependency Products

• HP TCP/IP Services of OpenVMS (ECO2 is required for TCP/IP Services Versions 5.5 and 5.6)
• HP SSL V1.3
• HP WBEM Services V2.61

Please do maintain the order of installation of the dependency products as mentioned above.

Required Patches

• HP I64VMS VMS831H1I_PCSI V1.0
• HP I64VMS VMS831H1I_UPDATE V2.0

Note: Please do maintain the order of installation of the patches as mentioned above since the later is dependent on the previous one. It is recommended to upgrade your system with the latest SYS and UPDATE patches. Update patches make functional changes to the system and requires reboot in order to have the images in the kit to fully take effect. The patches could be downloaded from the hp ITRC site.
 

Compatibility Matrix

Note: All the WBEM Services versions are not compliant with the iCAP software.        

WBEM Services for OpenVMS is installed automatically with OpenVMS. As with other similar products, an OpenVMS upgrade does not automatically include WBEM Services for OpenVMS if it is not already installed on the target system disk. In this case, you must install the product separately using the PCSI PRODUCT INSTALL command. You must configure WBEM Services for OpenVMS to obtain the services provided by HP SIM (Version 5.2 or later) and products such as Instant Capacity, and gWLM. To provide services over the network, HP recommends using TCP/IP Services for OpenVMS and SSL (for security purposes).

Before configuring WBEM Services for OpenVMS, configure TCP/IP Services for OpenVMS. For information about configuring TCP/IP Services for OpenVMS, see Section 7.7.5 (page 122) of HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual.

Click here to see the steps to configure WBEM Services for OpenVMS on a system on which WBEM Services for OpenVMS has never been installed and configured.

Click here to see the steps if you are configuring the product on a system on which it has been configured previously.

For more information about HP WBEM products, see the following website: http://www.hp.com/go/wbem.

Configuring WBEM Services for OpenVMS (Where Not Configured Previously)

To configure WBEM Services for OpenVMS on a system for the first time, follow these steps:

1. Enter the following command

   $  RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG

This command invokes the utility that configures and initializes the environment for WBEM Services for OpenVMS.

2. After displaying the initial configuration utility banner, the utility informs you where it will store the configuration files and repository and asks if you want to change the location.

 The configuration files and repository will be placed in the following location: SYS$SPECIFIC:[WBEM_Services].

 Do you want to change this location (Yes/No) [No]?:

Note: The repository, a compiled version of the Common Information Model (CIM) class  schema, requires an ODS-5 formatted disk (the repository uses UNIX-style file names, which are not supported on ODS-2 formatted disks). If the default location is on an ODS-2 formatted disk, you must change the location to an ODS-5 disk.

When you accept the default location, the utility informs you that all configuration questions have been answered and asks whether you want to continue, as shown in the following example. If you choose to continue, the utility creates the CIMSERVER repository tree in the location indicated earlier. The CIMSERVER is the WBEM Services for OpenVMS process that runs on the system to support certain applications. It also creates the following command files:

SYS$STARTUP:WBEM_Services$Startup.com
SYS$STARTUP:WBEM_Services$Shutdown.com
SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com

The SYS$STARTUP:WBEM_Services$Startup.com file defines system logicals for the WBEM Services for OpenVMS environment.

All configuration questions have been answered.

Do you want to continue (Yes/No) [YES]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
    SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.

This utility creates:
    SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.

This utility creates:
    SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com.

3. The utility asks whether to start the CIMSERVER:

Do you want to start the CIMServer now (Yes/No) [Yes]?:

CIMSERVER must be running so that your system can use such applications as Instant Capacity, and gWLM. You can start CIMSERVER now, or you can perform other post-installation or post-upgrade tasks first and then start CIMSERVER. If you choose to start CIMSERVER now, the utility displays the progress and operating system information, as in the following example:

%RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
  Host: boston.hp.com
  Name: OpenVMS
  Version: V8.3-1H1
  UserLicense: Unlimited user license
  Number of Users: 1 users
  Number of Processes: 29 processes
  OSCapability: 64 bit
  LastBootTime: Jul 31, 2007  10:52:55 (-0400)
  LocalDateTime: Aug 3, 2007  10:14:58 (-0400)
  SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs

4. To ensure that CIMServer starts automatically at each reboot, add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:

$ @SYS$STARTUP:WBEM_Services$Startup.com

 To have CIMServer shut down automatically with the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM file:

$ @SYS$STARTUP:WBEM_Services$Shutdown.com

All users who use this product should also add the following line to their LOGIN.COM file:

$ @SYS$STARTUP:WBEM_Services$Define_Commands.com

5. In an OpenVMS Cluster, each member that runs WBEM Services for OpenVMS needs its own repository. Therefore, you must perform the WBEM Services for OpenVMS configuration procedure on each of those cluster members.

Configuring WBEM Services for OpenVMS (Where Configured Previously)

To configure WBEM Services for OpenVMS on a system where it has been configured previously, follow these steps:

1. Enter the following command

   $  RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG

This command starts the utility that configures and initializes the environment for WBEM Services for OpenVMS.

If the WBEM Services for OpenVMS product (Version 2.0) available with OpenVMS I64 Version 8.3 is already configured on your system, the following error message and the recommended remedial actions appear:

%WBEMCONFIG-E-SYSCOMMONLOGICAL, WBEM_VAR can no longer be defined to point to a location in SYS$COMMON. The repository files in WBEM_VAR should not be shared with other cluster members.

Follow these manual steps to move the repository out of the SYS$COMMON area and complete the post installation configuration tasks:

• Delete the sys$common:[WBEM_Services.var...] directory tree.

• Deassign the WBEM_VAR system logical.

• Run this procedure again.

Perform the recommended steps, as in the following example:

$  DELETE SYS$COMMON:[WBEM_SERVICES.VAR]*.*;*
$  DELETE SYS$COMMON:[WBEM_SERVICES]VAR.DIR;*
$  DEASSIGN/SYS WBEM_VAR
$  RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG

After you start the configuration procedure, go to Section A  and follow the steps described there, starting with step 2.

2. After displaying the initial configuration utility banner, the utility informs you where it will  store the configuration files and repository and asks if you want to change the location.    
   
The configuration files and repository will be placed in the following location:
SYS$SPECIFIC:[WBEM_Services].

 Do you want to change this location (Yes/No) [No]?:

 The repository is a compiled version of the CIM class schema. This example assumes you accept the current location.

3. As shown in the following example, the utility informs you that all configuration questions  have been answered and asks whether you want to continue.

If the utility determines that the repository schema has not changed, the utility informs you and continues. The utility does not need to upgrade the repository.

If the utility determines that the current repository needs upgrading, or if the utility does not find a repository (perhaps WBEM Services for OpenVMS had been installed but not configured), the utility displays a message informing you that the repository will be upgraded or created and that this will take 10 to 15 minutes depending on your processor and disk I/O speed. In the following example, the utility needs to create the repository tree.

 The utility also creates the SYS$STARTUP:WBEM_Services$Startup.com, SYS$STARTUP:WBEM_Services$Shutdown.com, and
SYS$SYSROOT:[WBEM_SERVICES]WBEM_Services$Define_Commands.com command files. The SYS$STARTUP:WBEM_Services$Startup.com file defines system logicals for the WBEM Services for OpenVMS environment.

All configuration questions have been answered.

Do you want to continue (Yes/No) [Yes]?:
%WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins...
%WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete.
This utility creates:
    SYS$STARTUP:WBEM_Services$Startup.com
which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM.

This utility creates:
    SYS$STARTUP:WBEM_Services$Shutdown.com
which should be added to SYS$STARTUP:SYSHUTDWN.COM.

This utility creates:
    SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com
which users who use this product can add to their login.com.

4. The utility now asks you whether to start the CIMSERVER:

Do you want to start the CIMServer now (Y/N) {Y}?:

CIMSERVER must be running so that your system can use such applications as Instant Capacity, Pay per use, and gWLM. You can start CIMSERVER now, or you can perform other post-installation or post-upgrade tasks first and then start CIMSERVER. If you choose to start CIMSERVER now, the utility displays the progress and operating system information, as in the following example:

 %RUN-S-PROC_ID, identification of created process is 21A00599
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
  Host: boston.hp.com
  Name: OpenVMS
  Version: V8.3-1H1
  UserLicense: Unlimited user license
  Number of Users: 1 users
  Number of Processes: 29 processes
  OSCapability: 64 bit
  LastBootTime: Jul 31, 2007  10:52:55 (-0400)
  LocalDateTime: Aug 3, 2007  10:14:58 (-0400)
  SystemUpTime: 256923 seconds = 2 days, 23 hrs, 22 mins, 3 secs 

5. To ensure that CIMSERVER starts automatically at each reboot, add the following line to the SYS$MANAGER:SYSTARTUP_VMS.COM file:

$ @SYS$STARTUP:WBEM_Services$Startup.com

To have CIMServer shut down automatically with the operating system, add the following line to the SYS$MANAGER:SYSSTARTUP:SYSHUTDWN.COM file:

$ @SYS$STARTUP:WBEM_Services$Shutdown.com

All users who use this product should also add the following line to their LOGIN.COM file:

$ @SYS$STARTUP:WBEM_Services$Define_Commands.com

6. In an OpenVMS Cluster, each member that will run WBEM Services for OpenVMS needs its own repository. Therefore, you must perform the WBEM Services for OpenVMS configuration procedure on each of those cluster members. 

%PCSI-E-HRDREF, product HP I64VMS WBEMCIM V2.61 is referenced by HP I64VMS OPENVMS V8.3-1H1

The two products listed above are tightly bound by a software dependency.    
If you override the recommendation to terminate the operation, the   referenced product will be removed, but the referencing product will have    an unsatisfied software dependency and may no longer function correctly.   Please review the referencing product’s documentation on requirements.   Answer YES to the following question to terminate the PRODUCT command.   However, if you are sure you want to remove the referenced product then    answer NO to continue the operation.

Post installation & configuration of OpenVMS V8.3-1H1, WBEMCIM V2.61-A070728 kits, install the following update patches with /SAVE_RECOVERY_DATA qualifier (so that in case of the patches not functioning properly, we can revert to the previous state) in the order mentioned below and reboot the system. 

• HP I64VMS VMS831H1I_PCSI V1.0

• HP I64VMS VMS831H1I_UPDATE V2.0

The above-mentioned OpenVMS V8.3-1H1 patches need to be installed for the following fixes:

• nPAR Provider fix  for dynamic profile write error;
• C Runtime Library channel leak fix;
• iCAP and nPAR fixes to support Hyperthreading on Montecito.

This kit will make functional changes to your system.
Before installing this kit you should make a backup copy of your system disk.  If you do not make a copy of your system disk you will not be able to restore your system to a pre-kit installation state.

Do you want to continue? [YES]

Installing this patch kit requires a reboot.

Hewlett Packard strongly recommends that you reboot your system immediately after installation ofthis kit. The images in this kit will not fully take effect until the system is rebooted.  However, if you do not re-boot immediately after kit installation, the system may become unstable and may not function as expected.

If you have other nodes in your VMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot (kit installation and reboot on one node at a time) may be performed.

 Before configuring the iCAP software, start the CIMSERVER process by executing the following command procedure:
$ @SYS$STARTUP:WBEM_Services$Startup.com

Define the WBEM Services logical with the following command:
$ @SYS$COMMON:[WBEM_SERVICES]WBEM_Services$Define_Commands.com

Ensure that the CIM Server is running and verify the list of Providers installed by entering the following command:
$ CIMPROVIDER -L -S

An output similar to the following is displayed:

MODULE                            STATUS
OperatingSystemModule             OK
ComputerSystemModule              OK
ProcessModule                     OK
ProcessorProviderModule           OK
IPProviderModule                  OK

 Execute the following command procedure in order to configure the iCAP software:
$ @SYS$MANAGER:ICAP$CONFIG.COM

Note that, this procedure will stop and restart the CIMSERVER process during the configuration. The procedure will enquire if you want to configure GiCAP (Answer NO since GiCAP is not supported on OpenVMS V8.3-1H1), system-contact’s e-mail address, configuration change notification and start the iCAP software.

A sample configuration output is provided below for your reference:

$ @SYS$MANAGER:ICAP$CONFIG.COM

             hp OpenVMS Industry Standard 64

     Instant Capacity on Demand (iCAP) configuration utility

     **************** W A R N I N G ****************

This procedure stops and restarts the CIMSERVER process. ALL WBEM provider modules will be unavailable for a short period of time during the configuration. 

    **************** W A R N I N G ****************

%DCL-I-SUPERSEDE, previous value of SRC_MOF$ has been superseded
%ICAP-I-CHECK, Checking for iCAP configuration requirements
%ICAP-I-CHEDONE, Check Done requirements OK

Are you satisfied with the backup of your WBEMCIM repository (Yes/No)?: y
%ICAP-I-UNREGNPAR, Unregistering  at 30-OCT-2008 08:04:57.32
Disabling provider module...
Provider module disabled successfully.
Deleting provider module...
Provider module deleted successfully.
Disabling provider module...
Provider module disabled successfully.
Deleting provider module...
Provider module deleted successfully.
Disabling provider module...
Provider module disabled successfully.
Deleting provider module...
Provider module deleted successfully.
Disabling provider module...
Provider module disabled successfully.
Deleting provider module...
Provider module deleted successfully.
%ICAP-I-UNREGDON, Unregistering iCAP/nPAR modules done at 30-OCT-2008 08:05:47.90
%ICAP-I-STOPCIM, Stopping the cimserver process.
%WBEMCIM-I-SHUTDOWN, Shutting down WBEM Services for OpenVMS......
%WBEMCIM-I-SHUTDOWNPROV, Shutting down WBEM Providers...
%WBEMPROVIDERS-I-SHUTDOWN, Info:Shutting down WBEMPROVIDERS.
%WBEMCIM-I-SHUTDOWNCS, Shutting down CIMServer.exe...
CIM Server stopped.
%WBEMCIM-I-CSEXITSTS, CIMServer.exe exit status=%X00000001.
%ICAP-I-RESCIM, Restarting the cimserver process.
%RUN-S-PROC_ID, identification of created process is 00000474
%WBEMCIM-I-STARTUPWAIT, Waiting for CIMServer to start... 120 seconds remaining.
%WBEMCIM-S-CSSTARTED, CIMServer successfully started.
OperatingSystem Information
  Host: part0.ind.hp.com
  Name: OpenVMS
  Version: V8.3-1H1
  UserLicense: Unknown
  Number of Users: 1 users
  Number of Processes: 18 processes
  OSCapability: 64 bit
  LastBootTime: Oct 30, 2008  6:33:16 (00000)
  LocalDateTime: Oct 30, 2008  2:36:04 (00000)
  SystemUpTime: 4294953064 seconds = 49710 days, 2 hrs, 31 mins, 4
  secs
%WBEMCIM-I-STARTPROV, Starting WBEM Providers...
%WBEMPROVIDERS-I-STARTING , Info:Starting WBEMPROVIDERS.
%WBEMPROVIDERS-I-WAIT, Info:Waiting for 1 Minute for the Inventory to Initialize
%RUN-S-PROC_ID, identification of created process is 00000475
%iCAP-I-CRENAM, Creating root/cimv2/npar namespace
%ICAP-I-BEGUPDREP, Begin updating WBEMCIM repository at 30-OCT-2008 08:07:20.49

%ICAP-I-ENDUPDREP,   End updating WBEMCIM repository at 30-OCT-2008 08:08:44.58
%ICAP-I-REGNPAR, Registering iCAP Mofs at  30-OCT-2008 08:08:44.58

%ICAP-I-REGDone, Registering iCAP Mofs Done at 30-OCT-2008 08:09:24.46
Registering iCAP Command Language Definition file...
Command Language Definition file successfully registered
Enter (Y)es to configure this system with GiCAP support (N):
Would you like to set the System-Contact's E-mail Address? (Y/N): y
Enter the System-Contact's E-mail Address: xyz@hp.com

The contact e-mail address has been set to xyz@hp.com.
Would you like to turn configuration change notification on? (Y/N): y
Configuration change notification has been turned on.

Would you like to start the iCAP software now? (Y/N): y
%RUN-S-PROC_ID, identification of created process is 00000480

%ICAP-I-EXIT, Exiting ICAP configuration elapsed time 0:05:40.64

Check if all the iCAP related Providers are installed and running by entering the following command:

$ CIMPROVIDER -L -S

 An output similar to the following is displayed:

MODULE                        STATUS
OperatingSystemModule         OK
ComputerSystemModule          OK
ProcessModule                 OK
ProcessorProviderModule       OK
IPProviderModule              OK
HP_NParProviderModule         OK
HP_iCODProviderModule         OK
HP_iCAPProviderModule         OK
HP_GiCAPProviderModule        OK

To verify that the Instant Capacity software is installed and configured, run the following OpenVMS commands:

$ @SYS$MANAGER:ICAP$CLI_UTILS.COM CONFIG_CHECK

$ show log ICAP$CONFIGURED

"ICAP$CONFIGURED" = "TRUE" (LNM$JOB_nnnnnnnn)