config_systems | Teradata DSA Commands - config_systems - BAR - Data Stream Architecture

Teradata® DSA User Guide

Data Stream Architecture
Release Number
November 2022
English (United States)
Last Update
Product Category
Teradata Tools and Utilities


The config_systems command configures the DSC settings for the Teradata system used for backup and restore jobs. It also sets the selector in the targeted system for ActiveMQ and establishes a JDBC connection to the target system. Nodes are configured automatically after restarting DSMain on the system.


config_systems -f|-file File -s|skip_system_config SkipSystemConfiguration


dsc config_systems -f configSystem.xml -s system


f|file filename
The full path and name of the file containing the necessary configuration parameters.
Example: configSystem.xml
s|skip_system_config SkipSystemConfiguration
[Optional] Flag indicating whether the systems and node configuration or selector setting is skipped when you run the command. If this option is not specified, then both parts of the configuration (system and selector) are run. Enter one of the following:
  • system: Avoid configuring Teradata systems and nodes
  • selector: Avoid setting the selector in the targeted system for ActiveMQ
    If you choose the selector option, restart the DSMAIN on the database.
u|user_authentication User
Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.

Permissions required: Administrator role

Usage Notes

System nodes are configured by auto discovery.

Item Description
Component names

The component name can only use the following characters: 'A-Z', 'a-z', '0-9' and '_'.

The first character of the component name cannot be '_'.
Allowing Backing Jobs Based on Full or Cumulative Backup Jobs Completed with Errors

By setting the skip_force_full option in the XML file, you can run a CBB backup job that is based on a prior full or cumulative backup job that completed with errors.

Default. If the full or cumulative backup job fails, aborts, or completes with errors, the next time the job is run, the job is forced to be a full backup.
If the full or cumulative backup job fails or aborts, the next time the job is run, the job is forced to be a full backup.

Jobs that complete with errors are handled the same as jobs that complete successfully or with a warning.

The skip_force_full option is set system-wide. You cannot use this option on a single-job basis.
System Configuration Attributes The following XML file example shows system configuration attributes. System configuration is subject to the following restrictions and requirements.
Setting reset_node_limit to true overwrites node limits with the system's hard and soft limits.
Soft and hard limits for insertion of new nodes:
  • If node limits are specified, they are used.
  • If node limits are not specified, the system limits are used.
  • The soft limits cannot be greater than the hard limits.
Soft and hard limits when updating existing nodes:
  • If the node limit is specified, the node limit is used.
  • If a node limit is not specified and the system limit = system limit in database, the node limit is used.
  • If a node limit is not specified and system limit is not the same as system limit in database, system limit is used.

XML File Example

Here is a representative XML file containing system configuration information.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

          <!--****This command must be on one line.****-->
<dscConfigSystems xmlns=""
xmlns:xsi="" xsi:schemaLocation="DSC.xsd">

<!-- 'system_name' - Required, max 32 characters -->

<!-- 'tdpid' - Required (unless skipped by option)-->

<!-- 'database_query_method' - Required, accepted values: BASE_VIEW/EXTENDED_VIEW -->

<!-- 'streams_softlimit' - Required, number of streams per node per job -->

<!-- 'streams_hardlimit' - Required, max number of streams per node-->

<!-- 'reset_node_limit' - Optional, accepted values: true/false -->

<!-- 'skip_force_full' - Optional, accepted values: true/false -->