Dive Process Node

A Dive node is a Production process node that runs a Spectre Dive script, which describes a query to a cBase.

Production Dive Node

The results of the Dive node can be used as an input for an Integrator process node. For more information about dives, see What is a Spectre Dive? The dive node allows you to run one or multiple dives to populate the cache before users look at their data. The dive node also allows you to run one or more dives to capture the output in text files for further processing.

The Dive node has Closedfour panes where you set attributes.

Production Dive Node All Panes

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

Production Dive Node Attributes

Attribute Description
Name Specify a descriptive name for the node. Lower case names maximize usage of the available space.
File with list of Dive scripts
(Required if no Dive Scripts attribute is set)

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

This attribute and the Dive Scripts attribute are mutually exclusive.
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.

ClosedDive node with comments

Production Dive Node with comments

Specify one or more Dive files in the lower-left ClosedDive Scripts pane.

Production Dive Node Scripts List

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

  • Disabled—Disables specific Dive scripts, which is useful for debugging. The default is no.
  • Dive scripts—Specifies the location of the Dive file.
  • Output Files—Specifies the location of a text file for the dive results. If blank, all output is directed to the node log.
  • Failure Type—Specifies how to handle an individual Dive file failure: Fail, Never, or Warning. The default is Fail.

The Dive scripts attribute and the File with list of Dive scripts attribute are mutually exclusive.

Define parameters for this node in the lower-right ClosedParameters pane.

Production Build cBase Parameters

NOTE: Node-level parameters are available only for the current node.
See Parameters in Production for more information.