Resource Details

Don't forget to click Save to save your resource definition.

A default value may be defined, refer to section "Resource Default Settings".

General

• Name

  Resource reference

• Label

  Description of the resource

• Type

  Accepts the resource type.

  The table below summarizes the types of resources available depending on the DUAS version and operating system:

  	Code	DUAS version	Windows	UNIX/Linux	OpenVMS	OS/400
  File	FIL	V5 and V6	yes	yes	yes	yes
  Logical	LOG	V5 and V6	yes	yes	yes	yes
  SAP Event*	SAE	V5 and V6	yes	yes	no	no
  SAP Job*	SAJ	V5 and V6	yes	yes	no	no
  JMS*	JMS	V5 and V6	yes	yes	no	no
  REST*	REST	V6	yes	yes	no	no
  SOAP*	SOAP	V6	yes	yes	no	no
  Script	SCR	V6	yes	yes	no	no
  System	SYS	V6	yes	yes	no	no
  SP Monitor	SPM	V6	yes	yes	no	no

  * These types of resources are usable according to the Dollar Universe Managers installed. These types of resources are described in the corresponding documentations (SAP: Manager for SAP Solutions, JMS: Manager for Java, REST and SOAP : Manager for Web Services).

Location

• Name

  The resource name. It can contain the wildcard *: this means that the directory is being monitored.

  • For Logical type and Script type resources, the name can include variable elements of the Uproc execution context, such as:

    !UG!	!MU!	Management Unit
    !DTRAIT!	!PDATE!	Processing Date
    !SOC!	!COMP!	Company
    !ESP!	!AREA!	Area

    On OpenVMS, if “exit 0” is entered in a script resource, it will be considered as “exit 1”.

  • For File type resources, the name can include any variable elements. The variable values can be derived from Uproc execution context, MU variables, node variables, node settings or system environment variables and are searched for in that order.

    For the Uproc execution context, the following keywords can be used:

    !UG!	!MU!	Management Unit
    !DTRAIT!	!PDATE!	Processing Date
    !SOC!	!COMP!	Company
    !ESP!	!AREA!	Area
    !APP!		Application
    !SESS!		Session
    !UPR!		Uproc

    A variable can be entered in the file name and the file path of the resource definition and in the resource condition of an Uproc for string parsing.

    If a file name contains an exclamation mark “!”,,in order for this character not to be interpreted, one can simply include it in a variable value.

    If the variable cannot be found or if the variable name is empty (case !!), an empty value will be used.

    Example

    • Name: !DATABASE!.log
    • Path: !ROOT!/sub_directory

    In the history trace, only standard variable names are resolved (!UG!, !DTRAIT!, !SOC! ...). The variables are displayed in the resource log.

  • For a System type resource the resource name must be selected from: CPU, RAM or STORAGE.

    For a System resource – STORAGE: enter the System Files that must be monitored. In Windows type the drive letter, for example: C:

• Path

  Corresponds to the path of a resource (max 59 characters). This field is only available for File and Script type resources. Similarly to the resource name, the path may also contain Dollar Universe variable elements (!UG!, !DTRAIT!, !SOC! ...).

• Use a regular expression for the file name: Select this option to enable the use of regular expression to define the file for a file type resource (Tcl/Tk library version 8.1 with option "ERE" meaning that only the syntax of 8.0 is supported; follow the URL https://tcl.tk/doc/howto/regexp81.html#part1_2 for more details). The following characters are supported for regular expressions:

  • A wildcard: any character “.”
  • Repeat: zero or more occurrences of previous character or class “*”
  • Line positions: beginning of line “^”
  • Line position: end of line “$”
  • Character class: any one character in set. Example: [clas]
  • Inverse class: any one character not in set. Example: [^clas]
  • Range: any characters within the specified range. Example: [0-9]
  • Escape: literal use of meta-character “x”. Example: \x
  • Word position: beginning of word. Example: \<xyz
  • Word position: end of word. Example: xyz\>

• Parameters: (For a Script-type resource only) corresponds to the list of parameters to be passed to the script during its execution.

  • Parameters must be separated by spaces.
  • They can contain variable elements of Dollar Universe (!UG!, !DTRAIT!, !SOC! and !ESP!).
  • The maximum length is 60 characters. Once the values are defined, they cannot be more than 1024 characters.

Parameters

Default values may be defined. Refer to section: Resource Default Settings.

• Scan frequency

  Corresponds to the supervisor’s resource scan cycle. For optimum performance, use the longest cycle possible. The default and minimum value is 30 seconds. The value is rounded-up to the next multiple of 30 seconds.

  For a resource-type Script, the monitoring frequency corresponds to the script execution frequency.

• Time validity

  For a Script-type resource, the time validity is the period during which the return code of the script will be considered valid for checking the condition of the resource. The time validity value must be superior to the scan frequency.

• De-allocation mode

  For a resource-type Logical:

  • Automatic: Quotas consumed by the Uproc submission will be released as soon as its execution completes.
  • Manual: Quotas are not automatically released when the Uproc finishes. The resource can be released (partially or completely) with the command uxrls or via the resource events management section. Refer to section: Resource Events.

• Access mode

  For a resource-type Logical:

  • Exclusive: Sets exclusive access to a logical resource, one Uproc at a time. For other types of resources, this parameter should be specified in the Uproc condition to be effective.
  • Non-exclusive: Uprocs having a condition defined on this resource will be able to run at the same time within the quota limits.

• Quota 1, Quota 2

  Contain the maximum number of tokens for quota 1 and 2. These quotas define the maximum number of tokens that can be allocated for a resource. Different Uprocs can share the same resource while they are monitored by Dollar Universe. The consumption of tokens by a Uproc occurs during the Uproc’s launch phase.