The Control GDO Editor, ctl, also called the PDE Control program, lets you display and modify PDE configuration settings. These settings affect how the PDE handles startup, responds to crashes, and the functions during the normal operation of Teradata.
Globally distributed objects (GDOs) are binary files that store Teradata Database configuration settings. They are distributed to and used by every node in the system. The PDE layer of Teradata Database ensures that the GDO is consistent across all virtual processors.
Scenarios Runs From
Ctl runs from the Linux command line.
For general information on starting the utilities from different interfaces, see Appendix B: “Starting the Utilities”
Scenarios Syntax
To start ctl from the command line, use the following command syntax.
|
Setting |
Description |
|
-first command |
First command to execute before other processing. No default. Example: ctl -first “Node Logging Rate = 600;screen rss; write; quit”
Sets the RSS screen Node Logging Rate field to 600, displays the RSS screen to confirm the changes, writes the changes to the Control GDO, and quits the ctl utility. |
|
-last command |
Last command to execute just before exiting. No default. Example: ctl -last screen
Displays the current screen before exiting the ctl interactive mode. |
|
-help |
Provides information on ctl command-line options. |
Note: Some strictly internal and rarely-needed options have been omitted from this discussion. Those options are documented in the ctl command-line help.
Scenarios Usage Notes
The -first and -last options accept one or more commands separated by semicolons. If there are any blank spaces in the command list, enclose the list within double quotation marks.
Note: Teradata recommends using the full field names, rather than the alphanumeric field identifiers in command lists for the -first and -last options.