Using special resources
In the application description, you can specify the resources that are used by each operation in your application. You also specify whether the operation requires the resource exclusively or whether it can share the resources with other operations. For information about resources, see Creating special resources.
The resource name you choose can be any character string up to 44 characters. For documentation purposes, the string should be a meaningful name. If the resource represents a data set, it is good practice to make the resource name the data set name.
When you create an operation that uses a special resource, select option 3 (SPECIAL RESOURCES) in the OPERATION DETAILS menu. You see the SPECIAL RESOURCES panel, shown in EQQAMSRL - Special resources .
- Special Resource
- The name of the resource, up to 44 characters. You can use the global search characters % and * if you are unsure of the name: HCL Workload Automation for Z will display a list of matching names. For example, if you specify PAY*, HCL Workload Automation for Z displays all special resources beginning with PAY, and you can select PAYROLL.DATABASE.
- Qty
- The number of resources that the operation allocates. If you leave this field blank, the operation is allocated the whole quantity currently available (the adjust quantity), unless this value is not greater than 0, in which case the operation cannot start until the adjust quantity becomes greater than 0. This adjust value is the difference between the current and global values. Once started, the operation allocates the whole quantity available, even if this value later increases.
- Shr Ex
- Whether the operation needs shared or
exclusive access to the
resource:
S
(shared)X
(exclusive)
A resource unit allocated to an operation as shared can be used by other sharing operations at the same time, but is unavailable to operations that need exclusive allocation. Resource units allocated as exclusive can be used only by that operation. HCL Workload Automation for Z does not start another operation that requires the allocated units until the first operation ends.
This is like data set disposition. However, if a resource unit is allocated as shared by an operation and an operation requiring exclusive use becomes ready, further shared requests are not delayed behind the waiting exclusive operation. Waiting operations, in other words, have no allocated resources (unless they are failed operations that have the keep-on-error attribute for some resources).
- Keep on error
- Whether the operation keeps
the resource when it fails:
- Y
- The resource is kept
- N
- The resource is freed
- Blank
- The default value set for the resource is taken
- Avail on complete
- Whether
the global availability
of the resource is to be changed when the operation completes.
- Y
- The global availability is changed to Yes.
- N
- The global availability is changed to No.
- R
- The global availability is changed to blank.
- Blank
- Uses
the system default, according to the following order:
- The On Complete value set at operation definition level, if not blank.
- The On Complete value set at special resource definition level, if not blank.
- The ONCOMPLETE or DYNONCOMPLETE keyword value, respectively set for the not dynamically added resources or the dynamically added resources, in all the other cases.
Use the SPECIAL RESOURCE panel to create and modify special resources (option 1.6 from the main menu).