The following syntax rules explain the criteria for acceptable parameters and how to properly assign values to parameters:
- Separate multiple parameter assignments by blanks or commas. Repeated blanks, tab characters, and other white space characters are ignored. Unless otherwise stated, each parameter assignment has this form:
PARAMETERNAME = value
- Parameter names are case-insensitive. For example, config, CONFIG, and cONFIG are all acceptable. The equal sign (=) between the parameter name and the value can be replaced by one or more blanks. Blanks and a single comma can separate multiple parameter assignments on the IOPARM string.
- The assigned value can be one of the following, depending upon the parameter semantics:
| Value | Description | |
|---|---|---|
| Directory Path Value | Similar to a name token with the possible inclusion of forward slashes, backslashes, or periods within the overall name. In addition, directory paths can have a colon character (:) as the second character to separate the drive letter from the rest of the directory path. For example, C:\TIVBAR is a valid directory path. Directory paths can be up to 255 characters. Express embedded special characters not mentioned above (such as, blanks) as a quote string value. |
|
| Integer Value | Consists of numeric digits (0 through 9) from one to six digits long with an optional sign (+ or -). Avoid numbers expressed with a decimal point or in scientific notation.
|
|
| Name Value | Must be 30 or fewer alphanumeric characters that begin with a non-numeric character. To maintain consistency with Teradata SQL names, a dollar sign ($), underscore (_), or sharp symbol (#) are considered alphabetic characters. As with parameter names, name values are case-insensitive. | |
| Quote String Value | Can be up to 255 characters and must be enclosed with either single-quote (‘) or double-quote (“) characters. Any valid ASCII character can be between the outermost quote characters, but a second occurrence of an opening quote will terminate the string.
For example, ‘a “ b’ and “a ‘ b” are valid quote strings, but ‘a” b’ would be interpreted as two different quote strings, because the two single-quote characters in the middle would be interpreted as ending the first and starting a second string. |
|
- Parameters can be defined multiple times in a IOPARM string, but only the last assignment for the relevant parameter in the IOPARM string takes effect. Use this convention to override an entire set of parameter assignments.
- The following command line uses a second default file to override or merge with the normal settings established by the BARAM_DEFAULT environment variable:
Tivarc <arcsamp.txt ioparm=’default=c:\tdbar\mydefaults.txt’