 |
» |
|
|
|
Find documentation corrections for:
| To determine what version of WLM you have, enter the following command: |
|
|
|
|
|
|
|
WLM release notesThe release notes did not mention the following system requirement: OpenSSL A.00.09.07-e or laterIf you download software from the Web and create a software depot of your own, the required version of OpenSSL must be installed on the system on which you are installing WLM. You can obtain the required OpenSSL software from your AR media or from the HP Software Depot. If you install WLM from the AR media, the required SSL software is already included. WLM release notes, "WLM configurations cannot be activated with fewer than 100 Mbytes of memory available"In the discussion of this known problem, the following statement appears: When you have WLM controlling memory, it gives each workload group 1% of the memory when a configuration is activated and then adjusts the percentage for workload groups with active SLOs based on settings in the configuration. (Note that if extended_shares is enabled, WLM memory control requires at least 512 MB of memory.) However, WLM requires that the initial 1% of memory represent at least 1Mbyte. On systems with fewer than 100 Mbytes of available memory, that 1% is less than 1 Mbyte. As a result, WLM cannot activate the configuration in this case. The text should read as follows: When controlling memory, WLM allocates at least a minimum amount to each group. If the extended_shares tunable is set to 1, this minimum is 0.2% of the available memory; otherwise, it is 1%. (Available memory is the amount of memory reported by prmavail. It is the amount of real memory not reserved for the kernel and its data structures. Because the size of the kernel varies depending on the number of interface cards, users, and values of the tunable parameters, available memory varies over time.) WLM requires that the minimum amount of memory allocated to each group represent at least one Mbyte. Thus, when memory control is used, the system should have at least 500 Mbytes when the extended_shares tunable is set to 1; if extended_shares is not set to 1, the system should have at least100 Mbytes of available memory.
|
|
|
|
|
|
WLM release notes,
"Compatibility with other software"In the table named "Verified software configurations," Serviceguard A.11.13 is the version referenced as verified for use with WLM A.02.01 on HP-UX 11i V1.0 (B.11.11). The Serviceguard version should be A.11.14. WLM User's Guide, chapter 4, "Pattern matching for filenames"Near the end of the section, the following paragraph appears: Filenames are expanded to their complete names when a PRM configuration is loaded by WLM. Explicit application records take precedence over application records that use wildcards. If an application is matched by several records that use pattern matching, the application is assigned to the workload group specified in the "first" matching record. The "first" matching record is determined by sorting-in ASCII dictionary order- the matching patterns. The text should read as follows: Filenames are expanded to their complete names when a PRM configuration is loaded by WLM. Explicit application records take precedence over application records that use wildcards. If an application without an explicit record is matched by several records that use pattern matching, the record closest to the beginning of the configuration file is used. WLM User's Guide, chapter 4, "How the application manager affects workload group assignments"Near the end of the section, the following text appears: Starting one more program: % call_home The call_home command is matched by the first, second, and fourth records. Because the first record is an exact match, it takes precedence over the other two records, and the call_home process is placed in GroupA. Lastly, a user starts the following program: % calendar The second and fourth records match the calendar command. Because both these records use wildcards, they are processed in ASCII dictionary order. Consequently, the fourth record is the first to match calendar, which is placed in GroupD. The text should read as follows: Starting one more program: % call_home The call_home command is matched by the first and eighth records. (The second and fourth records do not match because PRM expands the regular expressions when the configuration is loaded and finds call_home already has a record.) The eighth record takes precedence because it has an alternate name, and the call_home process is placed in GroupZ. Be careful when constructing regular expressions: As shown with the eighth record above, an expression that is not specific enough can override explicit application records. Lastly, a user starts the following program: % calendar The second and fourth records both seem to match the calendar command. The expressions are expanded in the order they appear in the configuration file. So, the second record is expanded first and is used for the calendar process, placing it in GroupB.
|
|
|
|
|
|
WLM release notes,
"Compatibility and installation requirements"In Step 3.k. of the Installation Procedure, the user is instructed to copy the WLM product bundle to a software depot. During the copying process, SD-UX attempts to resolve all dependencies for the bundle. WLM has a dependency on EMS (Event Monitoring Service). In addition, on HP-UX 11i, EMS has a dependency on SAM (System Administration Manager). This dependency on SAM cannot be resolved because SAM is not on the HP-UX 11i AR CD. The resolution to this issue is to use the following option with the swcopy command:
-x enforce_dependencies=false
| After using the enforce_dependencies option, if you verify the local depot with swverify, you will get an error about the unresolved dependency on SAM. When installing from this local depot, all dependencies will be resolved though because SAM will be on the target system—as it is part of the core HP-UX 11i operating system. |
WLM User's Guide, chapter 2, "WLM in a nutshell"
| WLM User's Guide, chapter 4, "Pattern matching for filenames"Near the end of the section, the following paragraph appears: Filenames are expanded to their complete names when a PRM configuration is loaded by WLM. Explicit application records take precedence over application records that use wildcards. If an application is matched by several records that use pattern matching, the application is assigned to the workload group specified in the "first" matching record. The "first" matching record is determined by sorting-in ASCII dictionary order- the matching patterns. The text should read as follows: Filenames are expanded to their complete names when a PRM configuration is loaded by WLM. Explicit application records take precedence over application records that use wildcards. If an application without an explicit record is matched by several records that use pattern matching, the record closest to the beginning of the configuration file is used. WLM User's Guide, chapter 4, "How the application manager affects workload group assignments"
Near the end of the section, the following text appears:
Starting one more program:
% call_home
The call_home command is matched by the first, second, and fourth records. Because the first record is an exact match, it takes precedence over the other two records, and the call_home process is placed in GroupA.
Lastly, a user starts the following program:
% calendar
The second and fourth records match the calendar command. Because both these records use wildcards, they are processed in ASCII dictionary order. Consequently, the fourth record is the first to match calendar, which is placed in GroupD.
The text should read as follows:
Starting one more program:
% call_home
The call_home command is matched by the first and eighth records. (The second and fourth records do not match because PRM expands the regular expressions when the configuration is loaded and finds call_home already has a record.) The eighth record takes precedence because it has an alternate name, and the call_home process is placed in GroupZ.
Be careful when constructing regular expressions: As shown with the eighth record above, an expression that is not specific enough can override explicit application records.
Lastly, a user starts the following program:
% calendar
The second and fourth records both seem to match the calendar command. The expressions are expanded in the order they appear in the configuration file. So, the second record is expanded first and is used for the calendar process, placing it in GroupB.
|
|
|
|
|
Printable version
