Migrating packages from legacy to modular style

# Put all parameters in separate linesS cat ./tmp/nu-pkg.cntl.1 |

tr '; ' '\012' > ./tmp/nu-pkg.cntl.2

# remove extra quotation marks cat ./tmp/nu-pkg.cntl.2 |

sed -e '/FS /s/"//g' \

-e '/^LV /s/"//g' > $nuscript

Summary

Modular packaging gives lot of benefits, which include simplified package configuration, modularized approach to

packages where software partners can easily plug in custom modules for their products, the ability to build a package

from building blocks containing only the functions needed by this package, and so on. This white paper provides

information on the tools to migrate the legacy packages to modular packages.

HP recommends that you create new packages as modular packages to take advantage of the new features, since in

subsequent Serviceguard releases, new package features may be available only in modular packages.

For more information

Looking to migrate from your legacy packages to the new modular package configuration?

Simplify the integration and validation of your user-defined functions and parameters with

Modular packages—the latest interface for configuring Serviceguard packages. They modularize both

package configuration files and the control script.

For more information about modular packages see the latest edition of the Managing Serviceguard manual at:

hp.com/go/hpux-serviceguard-docs

> HP Serviceguard

hp.com/go/linux-serviceguard-docs > HP Serviceguard

Get connected

hp.com/go/getconnected

Current HP driver, support, and security alerts

delivered directly to your desktop

warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein

should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Oracle is a registered trademark of Oracle and/or its affiliates.

4AA4-1786ENW, Created July 2012