[z/OS]

Augmentation rules and limitations for feature packs on z/OS

Profile augmentation depends on the type of profile, whether you changed the configuration information, and so on. You must have the correct combination of feature packs in order to add a node, manage clusters, install applications, and manage server templates. Use these rules and limitations to ensure a properly functioning feature-pack environment.

To use the functionality provided in the Feature Pack for Modern Batch, you must either augment existing profiles or create new profiles enabled with feature-pack functionality. Profile creation and augmentation are done using the customization jobs and the associated instructions created by the Profile Management Tool or by using the zpmt command.

You can have a mix of augmented and unaugmented profiles that share a single WebSphere® Application Server installation. Feature-pack functionality is available only within profiles that have been augmented.

Augmentation rules and limitations

Table 1. Rules for profile augmentation.

The following table provides additional augmentation rules for particular types of profiles with this feature pack.

Profile Supported Not supported
Standalone application server
  • Creation of a new standalone application server that is enabled for the Feature Pack for Modern Batch

    When you create the standalone application server profile for the feature pack, the feature pack automatically augments the profile with feature-pack capabilities.

  • Augmentation of an existing Version 7.0 standalone application server profile

    You might have made configuration changes to the standalone application server profile.

Augmentation of an existing standalone application server if the standalone application server is lower than Version 7.0
Deployment manager
  • Creation of a new management profile with a deployment manager that is enabled for the Feature Pack for Modern Batch

    When you create the management profile with a deployment manager for the feature pack, the feature pack automatically augments the profile with feature-pack capabilities.

  • Augmentation of an existing Version 7.0 management profile with a deployment manager

    You might have made configuration changes to the profile.

Augmentation of an existing management profile with a deployment manager if the profile is lower than Version 7.0
Managed (custom) node
  • Creation of a new managed (custom) node that is enabled for the Feature Pack for Modern Batch

    When you create the managed (custom) node for the feature pack, the feature pack automatically augments the profile with feature-pack capabilities.

  • Augmentation of an existing Version 7.0 managed (custom) node
Augmentation of an existing managed (custom) node if the node is lower than Version 7.0
Network Deployment cell
  • Creation of a new Network Deployment cell that is enabled for the Feature Pack for Modern Batch

    When you create the deployment manager and the federated application server for the cell, the feature pack automatically augments the profile with feature-pack capabilities.

  • Augmentation of an existing Network Deployment cell

    You must enable a deployment manager and application server for the feature pack based on the preceding rules in this table.

Important: To enable feature-pack functionality in a federated application server, you must augment the cell's deployment manager profile as well as the federated application server profile with the feature pack.
Augmentation of an existing network deployment cell if the cell is lower than Version 7.0
Administrative agent
  • Creation of a new Version 7.0 management profile with an administrative agent that is enabled for the Feature Pack for Modern Batch

    You must install the feature pack onto the product first. When you create the management profile for the feature pack, the feature pack automatically augments the profile.

  • Augmentation of an existing Version 7.0 management profile with an administrative agent
Note: Currently, this profile has no requirements for feature-pack capability; however, if you augment an application server with the feature pack that is registered with an administrative agent, you also must augment its administrative agent with the feature pack.
Augmentation of an existing management profile with an administrative agent if the profile is lower than Version 7.0
Job manager   Creation or augmentation of a job manager to enable it for the feature pack

However, you can use a job manager in the feature-pack environment.

Secure proxy server   Creation or augmentation of a secure proxy server to enable it for the feature pack

However, you can use a secure proxy server in the feature-pack environment.

Secure proxy administrative agent   Creation or augmentation of a secure proxy administrative agent to enable it for the feature pack

However, you can use a secure proxy administrative agent in the feature-pack environment.

Augmentation rules and limitations in a mixed-cell environment

Table 2. Augmentation in a mixed-cell environment.

When you perform tasks between nodes or between nodes and the deployment manager, the feature packs must be compatible.

Function Rules
Addition of a node
  • You can add a node to a cell as long as the deployment manager has been augmented with at least the same set of feature packs as the node. The deployment manager might have been augmented with additional feature packs.
  • You can add a node with no feature-pack profile to a cell even though the deployment manager is augmented with some feature packs.
  • You cannot add a node with a particular feature-pack profile to a cell if the deployment manager has not been augmented with that feature pack.
Application installation
  • You can target an application that requires feature-pack functionality to an application server on a node that has been augmented with feature packs that contain that functionality.
  • You cannot target an application that requires feature-pack functionality to an application server on a node that has not been augmented with that feature-pack functionality.
  • You can target an application that does not require feature-pack functionality to an application server on a node with or without feature-pack augmentation.
Server configuration template use
  • You can use the server configuration template to create a server on another node that is augmented with the same feature pack.
  • If you attempt to use a server configuration template to create a server on another node that is augmented with a different feature pack, the operation fails. The scenario is not supported.
Cluster management
  • When you add a new member to a cluster, the new member must be able to run all the applications that have been targeted for the cluster.
  • If an application targeted for the cluster requires a specific feature pack, you must add the new member from a node that is enabled with that feature pack; otherwise, an error occurs.
  • If no application on the cluster requires a specific feature pack, you can add the new member to the cluster from a node with or without a feature pack.
Configuration-archive export and import If a configuration contains feature-pack capabilities, exporting a configuration to a configuration archive and importing a configuration from a configuration archive are not supported. If you run one of the import or export commands of the ConfigArchiveOperations command group against one of these configurations, the command might complete without reporting an error. No message is displayed when importing or exporting; however, no confirmation exists for imported configuration success.

Unaugmentation rule

You cannot unaugment profiles that have been enabled with feature-pack functionality in WebSphere Application Server for z/OS® Version 7.0.

Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 14, 2013 5:55:59 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700compg&product=was-nd-mp&topic=rins_limit_bp_zos
File name: rins_limit_bp_zos.html