Security Permissions for Commands | Teradata Data Mover - Access Permissions for Data Mover Commands - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.05
Published
October 2020
Language
English (United States)
Last Update
2020-11-18
dita:mapPath
xxl1591023586203.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

When security is not enabled, a command line user has permission to run all Data Mover commands. When security management is enabled and daemon-level security is selected, the rules described below apply to the command line interface.

If the security level is set at daemon level, only daemon-level permission is checked. If the security level is set to job, both daemon- and job-level permissions are evaluated.

A user needs job-level (if security is set to job level) and daemon-level read permission to run the following commands:
  • list_jobs
  • list_job_definition
  • list_job_steps
  • status
A user needs job-level (if security is set to job level) and daemon-level write permission to run the following commands:
  • delete_job
  • move
  • create
  • edit
  • update_job_steps
  • update_job_priorities
A user need job-level (if security level is job) and daemon-level execute permission to run the following commands:
  • start
  • stop
  • restart
  • cleanup
  • move
A user needs to be either a command-line interface super user (dmcl_admin) or Viewpoint Administrator user to run these Admin-level commands:
  • backup_daemon
  • restore_daemon
  • list_event_table
  • create_event_table
  • delete_event_table
  • modify_event_table
  • list_configuration
  • save_configuration
  • modify_admin_password