The functions described in this section are used to list and define single or multiple resources for a job that are a prerequisite for submitting the job.
Before you can define a resource as a prerequisite for a job, it must be defined as resource master to Entire Operations. You define resources to Entire Operations by using the maintenance functions of the Resource Master metanode described in the Administration documentation.
This document covers the following topics:
Maintenance of a resource master: Resources in the Administration documentation
Basic use and summary of resource features: Resources in the section System Overview
To list all prerequisite resources defined for a job
In the Maintenance Job Master window, open the tabbed page Resources:
The table in the window lists all resources defined as prerequisites for the job. The table columns are described in Columns and Fields: Prerequisite Resource Definitions.
To find out where a predefined resource is used
From the table on the Resources page, select the required resource.
Choose .
A Where used Condition window similar to the example below opens:
If invoked for a master job definition: Shows the usage of this resource as a prerequisite in all master job definitions.
If invoked for an active job definition: Shows the current usage of this resource by active jobs.
The fields and columns contained in the window correspond to the fields and columns of the Defined in Jobs page. They are described in Field and Columns: Resource Defined in Jobs in the section Resources in the Administration documentation.
To display or modify the prerequisite resource definition of a
job
From the table on the tabbed page , select the resource definition you want to view or change and choose .
A Resource Prerequisite window similar to the example below opens:
Make your definitions. The input fields and selection options available in the window are described in Columns and Fields: Prerequisite Resource Definitions.
Choose when you are finished.
To add a prerequisite resource definition for a job
On the tabbed page , choose .
A Resource Prerequisite window similar to the previous example opens.
Make your definitions. The input fields and selection options available in the window are described in Columns and Fields: Prerequisite Resource Definitions.
Choose when you are finished.
To delete a resource definition
From the table on the tabbed page , select the resource definition you want to remove and choose .
The selected resource is deleted for this job master.
The following table explains the columns on the Resources page and the corresponding input fields/options of the Resource Prerequisite window:
| Column/Field/Option | Description | |
|---|---|---|
| Resource (name) | Name of the resource as defined in Entire Operations and listed in the Resource Master List window (see Resources in the Administration documentation). | |
| T | Resource type.
For details, see the description of the Type field in Fields: Resource Definition in the section Resources (Administration documentation). |
|
| (Required) Quantity | Resource quantity required for job
execution.
Input field: Enter the resource quantity required for job execution. Entire Operations does not submit the job until this amount of resource is available. |
|
| D | Deallocation mode of this prerequisite resource: see Resource Deallocation Modes. | |
| Deallocation Mode | ||
| DNO | Applies to
deallocation mode
After job termination
only.
Deallocate if job is |
|
Y
|
The resource will always be deallocated after job termination,
even if the job ended not ok.
|
|
| Deallocate if Job not ok | N
|
The resource will not be deallocated if the job ended not
ok. (However, the job will still be deallocated at network termination.)
|
| Input option: select this check box if you want to deallocate the job. | ||
| Allocated | Applies to active prerequisite
resources only.
Date and time when the resource was allocated for the current job. If the resource has not yet been allocated or if it has already been deallocated, this field is empty. See also Date and Time Formats. |
|
Note:
Resource allocations will be deallocated if the retention period
for an active condition is reached.
| Mode/Selection Option | Explanation |
|---|---|
J
After job termination |
Release resource at job
termination (default).
The resource is released when the allocating job terminates. |
N
After network termination |
Release resource at network
termination.
The resource will be released when the Entire Operations Monitor detects that all jobs of a job network are terminated. The resource will be released also if a currently executing network is being deactivated. Note: |
E
Keep until network termination |
Release resource at network
termination, but release earlier after an erroneous job.
The resource will be kept until network termination. If any job
ends |
K
Keep until explicit release |
Keep resource until manual
release.
The resource will not be released automatically at job or network termination. If the retention period for active conditions is reached, the resource will be released automatically. |
The following additional rules apply:
If an active network or job is deactivated, all the resources allocated by it will be released too. This will be performed regardless of the defined deallocation mode. This means that even resources with deallocation mode Keep until explicit release will be released in such cases.
Master resource amounts can be modified by API calls. Note that this is possible only if the amount is not determined by a resource master determination exit.
Resources can be allocated for a job by an API call. These additionally allocated resources will be handled in the same way as defined prerequisite resources.
Resources can be deallocated by API calls. Preliminary releases of resources are allowed for deallocation modes.
All resource allocations and deallocations will be logged.
For more information, see Handling of Resource Allocations (NOPURE1N) in the section List of Available Entire Operations API Routines.