Unlock Process Node

The Unlock node removes locks placed by a Lock node. Locks are automatically removed when a script finishes, but the Unlock node can remove a lock prematurely, for example if only a portion of a script needs to be protected. For more information about the Lock node, see Lock Process Node.

The Unlock node has Closedtwo panes where you set attributes.

Unlock Process Node Attributes

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

Attribute Description
Name Specify a descriptive name for the node. Lower case names maximize usage of the available space.
Lock Node Specify a Lock node in the same Production script here. When the Unlock node runs, the lock placed by the specified Lock node is unlocked. This is mutually exclusive with Lock Name.
Lock Name Specify a lock by name. The lock name is persistent across a DiveLine, so this can reference a lock created in a different Production script. This is mutually exclusive with Lock Node.
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.

ClosedUnlock node with comments

For more information, see Using Lock and Unlock Nodes.