DIAL Process Node

A DIAL node is a Production process node that runs one or more DIAL scripts.

Production DIAL Node

The Dimensional Insight Access Language (DIAL) is a high-level object oriented programming language designed to process, analyze, and distribute information contained in classic models and cBases.

Ensure that the DIAL executable is configured in the Server Settings > Advanced tab.

NOTE: You cannot specify the order in which multiple DIAL scripts run. Use multiple DIAL nodes if any DIAL scripts are dependent on another DIAL script completing.

The DIAL node has Closedfour panes where you set attributes.

Production DIAL Node All Panes

You set attributes for the DIAL node in the Closednode attributes pane.

Production DIAL Node Attributes

Attribute Description
Name Specify a descriptive name for the node. Lower case names maximize usage of the available space.
Fail on warning If set to False (default), the node continues processing when a warning message displays.
If set to True, the node fails when a warning message displays.
Failure type Specify how to handle a DIAL node failure:
  • If set to Any, which is the default and is recommended, the node fails if any of the DIAL scripts fail.
  • If set to Any and a Failure node is specified, the task flow goes to the Failure node if any of the DIAL scripts fail.,
  • If set to All, the task flow stops only if all of the DIAL scripts fail; otherwise, the task flow continues to the next node.
File with list of dial scripts
(Required if no scripts are listed in the Dial Scripts pane)

Specify a text file that contains the names of each DIAL script. List the name of each DIAL script on a separate line. To select the file, use the browse button (...) that appears when you click in the empty File with list of dial scripts box.

This attribute and the Dial Scripts attribute are mutually exclusive.
Simultaneous Define the maximum number of DIAL scripts to process at the same time:
  • 0 or Blank—When set to 0 or blank, the number of simultaneously run scripts depends on the number of available processors.

  • 1 (Default)—When set to 1, all scripts run sequentially, one at a time.

  • 2, 3, 4, or More—If more scripts than processors are specified, the scripts run in the order that they are listed.

Email Object for failure

Select a predefined mailing list to send an email to if the node fails. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. See Mailing Lists Tab for information about setting up Mailing Lists and Email Objects.
Email Object for success

Select a predefined mailing list to send an email to if the node succeeds. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. See Mailing Lists Tab for information about setting up Mailing Lists and Email Objects.
Email Object for warning

Select a predefined mailing list to send an email to if the node generates a warning. The pull-down list is populated with items that can be found in Project Settings > Mailing Lists > Email Templates. See Mailing Lists Tab for information about setting up Mailing Lists and Email Objects.
Failure node Select the next node upon failure. The pull-down list contains all nodes that are on the Task Flow.
Success node Select the next node upon successful completion. The next node automatically populates if a connecting line is set on the Task Flow. The pull-down list contains all nodes that are on the Task Flow.
Working Directory

Specifies the directory in which this node runs. If left blank, the Default Working Directory attribute that is set in the Start Control Node is used. When running a script, Production sets the working directory for the child process to the directory that contains the script, unless the node specifies a different directory.

See Start Control Node.
Default Working Directory

Displays the Default Working Directory that is set the the Start Control Node. If a Default Working Directory is not specified, this attribute is blank. Applies to all nodes.

See Start Control Node.

External File Encoding

Select the format for the node input files. If this attribute is blank, Workbench attempts to detect the type of encoding.

This attribute is also used when saving log files. The encoding might need to be adjusted when using data with high bit Latin-1 characters or Unicode characters.

Each node has an area where you can enter comments.

It is a DI best practice to enter a note for every node in a Production script. These notes can help you or a coworker understand the intent of the node and troubleshoot issues in the future.

ClosedDIAL node with comments

Production DIAL Node with comments

Specify one or more DIAL scripts in the lower-left ClosedDial Scripts pane.

Production DIAL Node Scripts List

The DIAL Scripts attribute is required if no File with list of dial scripts attribute is set.
The DIAL Scripts attribute supports additional control attributes for more detailed control of settings per file than if using the File with list of dial scripts attribute:

  • Disabled—Disables specific DIAL scripts, which is useful for debugging. The default is no.
  • Failure Type—Specifies how to handle an individual DIAL script run failure: Fail, Never, or Warning. The default is Fail.

The DIAL Scripts attribute and the File with list of dial scripts attribute are mutually exclusive.

Specify one or more arguments, in the lower-right ClosedArguments pane, that the Production script passes to the DIAL node.

Production DIAL Node Arguments

Arguments is the term used in the DIAL syntax for parameters.
See Parameters in Production for more information.

See DIAL Overview.