MU Details

Refer to section "Management Unit Default Settings" for default value settings.

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

General

• MU Name

  The Management Unit code. Enter a new name to create or duplicate a Management Unit.

• Label

  The Management Unit’s description

• MU type

  Management Unit Type (first character of the Management Unit code). If this type does not exist, it will automatically be created during creation of the Management Unit. If the type already exists, its description will automatically be displayed in the MU Label type field.

  (DUAS V5) It may be useful to reserve a type ("N" for example), to denote Management Units that are unique to each Node. This will facilitate the distribution of tables and other objects required in a single occurrence on a given Node, regardless of the number of Management Units and Areas present (Uprocs or Sessions). The Management Unit target for distribution can be defined as “N” (meaning all Management Units of type = "N" i.e. all Nodes).

• MU type label

  The Management Unit type description

• Node of residence

  Defines the Node, (present in the Dollar Universe Node table), on which the Management Unit resides. Complete the Node name (case sensitive) or click the arrow to select the Node from a list.

• Access to Area

  DUAS V5 only, these two flags define whether the Management Unit is active in the Development Universe and/or in the Production Universe.

  • Development: Check the box to activate this Management Unit in the Application and Integration Areas.
  • Production: Check the box to activate this Management Unit in the Simulation and Production Areas.

• Default submission account

  DUAS V6 only, enter the default submission account name that will be used during the creation of Tasks or launches on this Management Unit or click on the arrow to select it in the list.

Timezone

This section allows to change the default time of job runs. The choice between the three options is exclusive.

• None

  No offset will be applied to the job run time. By default the job run time is the same as the server time.

• Custom

  Offset of the Management Unit time relative to the system clock

  • In the first drop-down list, select the sign of the offset: "+" or "-".
  • In the Hours field, enter the number of hours of the offset: from 0 to 23 hours.
  • In the Minutes field, enter the number of minutes of the offset: from 0 to 59 minutes.

  The offset defined will always be used by the engine to translate the time entered by the user (his local time) to the system time when he schedules a Task. For example, if a user in Boston wants a job to run at 8 pm local time and the system is set to Central European Time (six hours before Boston), the MU offset should be set to "– 06 h 00". The launch would automatically be calculated at 2 am system Time.

• Timezone name

  The timezones list displayed is from IANA (http://www.iana.org/time-zones ). Timezone names use the «Continent/Town» format. For example: America/Montreal, Europe/Paris, Asia/Hong_Kong… Selecting a time zone for an MU allows a time difference that varies with the summer / winter time without user intervention. In addition, there is no dependence on the time zone of the machine.

In order for the MU offset time to be displayed in the job runs, the user must go into the Administration Mode > User Preferences > General Setting > Date Format > Reference Time and set the Reference Time to MU Time.

Directories

Dollar Universe can manage the paths to an application's data by Node/ Management Unit/ Area/ application. Use of this table is optional.

• Application Name

  Lists the applications for which MU directories have been defined; such directories will be displayed in the Area fields.

• Application Area

  Value of the FIC variable (available in the Uproc script) for a Uproc belonging to this application and running for the Management Unit in the Application Area.

• Integration Area

  Value of the FIC variable (available in the Uproc script) for a Uproc belonging to this application and running for the Management Unit in the Integration Area.

• Simulation Area

  Value of the FIC variable (available in the Uproc script) for a Uproc belonging to this application and running for the Management Unit in the Simulation Area.

• Production Area

  Value of the FIC variable (available in the Uproc script) for a Uproc belonging to this application and running for the Management Unit in the Production Area.

  • To create a new MU – application – Area directory, click Add, to update it click Update. In the displayed window:

    Enter the Application name or click the arrow to select the name from the list.

    Enter the repertory path for each Area or click to select it on the local system.

    Click OK to confirm your entries, or Cancel.

  • To delete a MU – application – Area directory, select a line and click Delete. The directory will be removed from the list with a user confirmation.

Dependencies

Dependent MU: Lists the Management Units defined as dependent on the current Management Unit.

• To create a new dependency, click Add. In the displayed window, select one or several Management Units. Then click OK to confirm your entries, or Cancel.

• To delete a dependency, select the dependency from a list and click Delete. The dependency will be removed with a user confirmation.

Variables

The variables defined for the Management Unit, on the basis of their names and their default values, can be used in the script of each Uproc executed on this Management Unit.

• Add/Update: Click on Add to create a variable:

Enter the name of the variable. On UNIX/Linux, a variable name cannot start with a number (operating system restriction).

Type TAB to enter its default value. Only the characters a-z, A-Z, 0-9, _, – are authorized.

Type ENTER to validate

Select a variable in the list and click on Update to update its name or its value.

• Delete: Delete the selected object.

In OS400, the UPROCLIB variable defined on the node, MU or Uproc can be used to load a library before launching the batch. The variable must be set with the name of the library to be loaded.