Build cBase Process Node

A Build cBase node is a Production process node that runs the Spectre Build application to create one or more cBases as prescribed by the attributes.

The Build cBase node has four panes where you set attributes.

Production Build cBase with all panes

Node Attributes

You set attributes for the Build cBase node in the node attributes pane.

Production Build cBase Attributes

Attribute	Description
Name	Specify a descriptive name for the node. Lower case names maximize usage of the available space.
Failure type	Specify how to handle a Build cBase node failure: If set to Any, which is the default and is recommended, the node fails if any of the Build scripts fail. If set to Any and a Failure node is specified, the task flow goes to the Failure node if any of the Build scripts fail. If set to All, the task flow stops only if all of the Build scripts fail; otherwise, the task flow continues to the next node.
File with list of Build scripts (Required if no Build Scripts attribute is set)	Specify a text file that contains the names of each Spectre Build script file. List the name of each Spectre Build script 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 build Scripts box. This attribute and the Build Scripts attribute are mutually exclusive.
LimitRows	Direct the Build cBase node to use a specific number of rows from each input file. If multiple input files are used, the first <number> of rows are read from each file, ensuring a complete sampling of data values.
NumCores	Define the number of cores to use for parallel processing, usually between 2 and 6. Using this attribute might speed up the build, but it depends on the capacity of the I/O system. Use this option when dealing with multiple inputs, or adding columns and lookups.
Simultaneous	Define the maximum number of Spectre Build files to process at the same time: 0 or Blank—When set to 0 or blank, the number of simultaneously run files depends on the number of available processors. 1 (Default)—When set to 1, all files run sequentially, one at a time. 2, 3, 4, or More—If more files than processors are specified, the files run in the order that they are listed.
Custom Success State Rules	Opens the Edit Custom Output Filters dialog box where you can define a custom warning state (Failed, Succeeded, or Warning) based on text found in the node's output. See Custom Output Filters.
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.