HP-UX Workload Manager User's Guide

Appendix G 465
G Migrating from PRM to WLM
This appendix provides information on converting PRM configuration
files to WLM configuration files.
If your PRM configuration places users in PRM groups, these users can
be grouped similarly in WLM workload groups.
If you are migrating from PRM to WLM, you can quickly convert your
PRM configuration files to WLM configuration files with the wlmprmconf
utility.
This utility, available at /opt/wlm/bin/wlmprmconf, has the following
syntax:
wlmprmconf [-f] PRMconfigfile WLMconfigfile
The wlmprmconf utility takes a PRM configuration (see prmconf(4)) as
the input file PRMconfigfile and translates it to the equivalent WLM
configuration (see wlmconf(4)), storing the result in the file
WLMconfigfile. You can then edit the WLM configuration file to add
SLO goals, change SLO priorities, add time-based conditions and
exceptions, modify WLM tuning parameters, and so forth.
The wlmprmconf utility validates the input PRM configuration using
prmconfig before the translation begins. If prmconfig is not installed or
if the input configuration is invalid, wlmprmconf exits without creating
the WLM configuration file. However, using the -f option, you can force
wlmprmconf to create the WLM configuration file in both of these cases.
After the translation, wlmd checks the validity of the generated WLM
configuration. If the output configuration is invalid, wlmprmconf prints
the wlmd error messages and exits without deleting the generated
configuration file. You can then modify the generated WLM configuration
file without modifying the original PRM configuration file.
The wlmd daemon has stricter rules than prmconfig regarding the
validity of a configuration. In addition, wlmd treats most PRM warnings
as errors. Therefore, it is possible for a valid PRM configuration file to be
translated into a syntactically correct WLM configuration file that fails
the wlmd check. For example, the user names listed in the PRM user
records may not be defined on the system, or the application pathnames
may point to executables that do not exist. In such cases, modify the
generated WLM configuration file to correct the errors reported by wlmd.