Values on the Modify Shared Resource Pool window
Instance Details
- Software services instance name prefix
- Character string to use as the beginning of the names of instances when
they are created from templates.
The requirements and the fields that are displayed for the prefix vary with
the software type and vendor. For a shared resource pool, all three fields are required because the
shared resource pool might be used when you provision any software type, for example, CICS, Db2, or
WebSphere Application Server Liberty. For help on specifying the prefix, you can also hover the mouse pointer on for the field.
- Use SNA APPLID
- Indicates that the character string should be derived from the SNA application ID. This option requires a network pool to be created, and is automatically selected if a network administrator was specified for the domain. This prefix is used for CICS templates when the SNA APPLID is available.
- Specify general name prefix
- Specify a character string that is up to six alphanumeric characters. The first character must be alphabetic. You can specify a wildcard character (*) as the last character.
- Specify subsystem name prefix
- Specify a character string that is up to 2 characters.
- Maximum number of software services instances
- Maximum number of software services instances that are allowed: Up to 1296 for a standard template, or up to the lowest maximum that was set for the associated child templates, for a composite template.
- Maximum number of software services instances for a user
- Maximum number of software services instances that are allowed for a single user. If you do not specify a value, the only limit for a standard template is the one that is specified for Maximum number of software services instances. For a composite template, if a child template set a maximum other than 1, the valid maximum is shown in parentheses.
- Maximum days to keep provisioned software services instances
- Maximum number of days until a provisioned
instance expires. When a provisioned instance exceeds this time limit, it is marked as expired,
and the instance is placed in provisioned-expired state. This limit applies to both
standard and composite templates.
When an instance for which a time limit is set nears its time limit, z/OSMF notifies the consumer, who can then deprovision the instance. By default, no time limit is set; a provisioning instance is retained until it is deleted explicitly by the domain administrator.
The domain administrator can modify this time limit. Doing so changes the time limit for provisioned instances that are created after the modification. Existing instances are not affected.
If you do not specify a value, the provisioned instance does not expire automatically unless a time limit is set for the template that creates the instance.
- Allow members of the tenant to access and run actions for software services instances
- Allow members of the tenant to view and perform actions against software services instances that are provisioned from the template. If you do not select this option, users must be owners of the template or domain administrators to have that authority.
Allow Modify Account
- Allow account information to be modified when the template is provisioned
- Specifies whether the account information can be modified when a template is provisioned, with a Test Run or Run action. For a composite template, this option is selected if it is selected for any of the child templates.
Job Statement JCL
- Specify customized JOB statement JCL (standard templates only)
- Select this to supply JOB statement JCL that will be used in all provisioning jobs. Job names:
- Can be up to 8 characters, consisting of A-Z, a-z, 0-9, and these special characters: # $ @
- Must start with an alphabetic character or one of these special characters: # $ @
- Can use workflow variables, which you specify as follows:
- ${_workflow-softwareServiceInstanceName}
- Software service instance name
- ${_workflow-workflowOwnerUpper}
- Workflow owner
- ${_step-stepOwnerUpper}
- Workflow step owner
Resource Management
- Create network resource pool
- Select this option to cause a resource pool for the template to be created with network
resources. A network resource pool defines shared network resources within the domain.
This option is enabled only if a network administrator is defined for the domain and the template is a standard template or a composite cluster template.
The network administrator must complete the network resource pool definition by using the Network Configuration Assistant task, in the Configuration category.
See the documentation from the software provider for information about whether the template requires a network pool. This documentation can include:- A readme file
- Administrator documentation, which you can access by viewing the template with the Software Services task.
- Create workload management pool (standard templates only)
- Select this option to cause a workload management resource pool to be created. The resource pool
is created with the name domain.tenant.template-type.
This option is enabled only if a workload management administrator is defined for the domain.
The workload management administrator must complete the workload management pool definition by using the Workload Management task, in the Performance category.
See the documentation from the software provider for information about whether the template requires a workload management pool. This documentation can include:- A readme file
- Administrator documentation, which you can access by viewing the template with the Software Services task.
Service Level Agreement (standard templates only) Select a value to specify the level of performance that the software services instance requires. The WLM administrator must associate the service level agreement that is specified in the WLM resource pool for the tenant with a service class that provides the appropriate level of performance. This option is available only if a workload administrator was specified for the domain. - Create LPAR resource pool
- Select this option to cause a logical partition (LPAR) resource pool for the template to be
created. An LPAR pool defines LPAR resources within the domain. This option creates a table that
allows you to add, modify, or remove volumes and other resources for the LPAR pool.
The LPAR pool can only be used by z/OS provisioning templates.
Systems
- System selection for provisioning
- Select an option for selecting the system on which the software service is provisioned.
- Use a specific system
- Select a system on which the template is to be provisioned, in the System field.
- Assign system automatically
- Select a system from a list of available systems.
- Systems for domain: domain-name
- The available systems are shown in the form
sysplex-name.system-name. LOCAL indicates the system that you
are logged on to.
The Systems for domain table shows the set of systems for the domain, for a standard template, and the systems that are common to all of the child templates, for a composite template.
Use Add or Remove to build the set of systems from which one will be automatically assigned for provisioning.
For a clustered composite template, all of the selected systems must exist in the same sysplex.
- Systems for automatic assignment
- The Systems for automatic assignment table shows the set of systems from which a system is assigned.
- Prompt user for system
- Use tables of available and selected systems to control the systems to be displayed in a prompt
in response to the Run or Test Run action for a template.
- Systems for domain: domain-name
- The Systems for domain table shows the full set of systems for the domain, in the form
sysplex-name.system-name. LOCAL indicates the system that you
are logged on to.
Use Add or Remove to build the list of systems that will be included in the user prompt. The user can select from that list.
- Systems for user prompt
- The Systems for user prompt table shows the systems that are included in the user prompt.