Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Unlink packages to remove dependencies

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

You can use the Management of Change (MoC) Package tool (dnapackage) to remove dependencies between two or more existing MoC packages.

Note: The package store (managed by the MOCOrchestrator service) must be available to successfully execute this command.

To unlink MoC packages to remove dependencies

  1. On the desktop, double-click the Windows PowerShell for DNA shortcut.

    Windows PowerShell for DNA opens.

  2. Execute the following commands:

    set-silo RealTime

    dnapackage unlink --title <package title> --dependency <package title> [--dalfolder <DAL configuration folder> --username <remote username> --password <remote password>]

    Where:

    • --title <package title> is the title of the dependent (child) package containing the link.

    • --dependency <package title> is the title of the antecedent (parent) package.

    • --dalfolder <DAL configuration folder> is the DAL configuration folder name on the remote system you are trying to connect to (for example, --dalfolder systemName\control_room).

    • --username <remote username> is the username of the user on the remote system you are trying to connect to.

    • --password <remote password> is the password of the user on the remote system you are trying to connect to.

      Note: The --dalfolder <DAL configuration folder>, --username <remote username>, and --password <remote password> parameters do not need to be included if you are unlinking packages on the same server as the MOCOrchestrator service. These parameters are mandatory if you are unlinking packages on any other server that does not have the MOCOrchestrator service. For example, unlinking packages on the Production MoC zone would require remote DAL configuration to connect to the MOCOrchestrator service.

      For example, to remove the dependency that the package titled "PackageB" has on the package titled "PackageA" (i.e., "PackageA" needs to be deployed before "PackageB"), the command would be as follows:

      dnapackage unlink --title "PackageB" --dependency "PackageA"