COMPILE Command | Teradata Director Program - CONFIG - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

Purpose

The CONFIG command is used to configure controls and default information affecting TDP operation, notably the operation of CPs and NPs. The information that is currently configured may be displayed using the DISPLAY CONFIG command.

Syntax





COMMLOST
Indicates that information controlling the message indicating that all communication has been lost with the database is to be configured.
CP
Indicates that Channel Processor information is to be configured.
NP
Indicates that Network Processor information is to be configured.
XP
Indicates that information affecting both CPs and NPs is to be configured.

COMMLOST MSG Sub-operand:

INTERVAL
Specifies a non-zero decimal number of minutes between messages reminding that all communication has been lost with the database. The maximum is 1440 minutes.
The deprecated DLYTIME default in the distributed HSISPB is 300 seconds. Use of the deprecated INITIAL DLYTIME command, also in seconds, overrides this default. This value, converted to minutes, is the default for INTERVAL.
When the INTERVAL value is less than 15 minutes and no explicit DOUBLE EVERY value has been specified, DOUBLE EVERY is default to six times the INTERVAL value in minutes.
DOUBLE EVERY
Specifies a non-zero integer number of minutes after all communication has been lost with the database, after which the COMMLOST MSG INTERVAL value is doubled. The maximum value is 1440.
If the INTERVAL value or its default is less than 15 minutes, DOUBLE EVERY is defaulted to six times the INTERVAL value in minutes; otherwise, NODOUBLE is the default.
Until communication with the database is restored, doubling will occur each time the DOUBLE EVERY number of minutes passes, resulting in increasingly fewer messages the longer the database is unavailable.
NODOUBLE
Specifies that the effect specified by any INTERVAL DOUBLE EVERY value or its default is immediately rescinded.

CP Sub-operand:

STORAGE
Specifies the maximum number of bytes of virtual storage that may be used for buffers by all CPs. The minimum value is dynamically calculated as the minimum storage required for all currently started CPs. The maximum value is 4294967295.
The STORAGE value is not the amount of storage allocated, simply an upper limit. If a CP is subsequently started that would increase the minimum storage required by all started CPs beyond the STORAGE value, the START will fail. When STORAGE is not specified, the maximum is dynamically calculated based on the number of CPs that are started, and the values for MAXBLKNM and MAXBLKSZ. Once specified, TDP must be restarted to revert to dynamic calculation of the maximum.
On z/OS, when using INITIAL IOMODE settings of EXCPVR or IOSDRIVR, 31-bit storage that is fixed in real storage is used, so higher maximums can increase real storage utilization.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
CHECKSUM
Specifies whether communication protocol checksum processing is forced OFF, forced ON, or automatically adjusts to whether the database presents such checksums (AUTO). The default value is 'ON'.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXBLKNM
Specifies the maximum number of I/O buffers, between 1 and 255, recommended for a channel transmission. The default value is 4. This recommendation may be reduced by the database for a CP when it is started.
This value may not be configured if any CPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXBLKSZ
Specifies the maximum size of an I/O buffer, between 40 and 65535 bytes, to be used for channel transmission. The default value is 65535. This recommendation may be reduced by the database for a CP when it is started.
This value may not be configured if any CPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXCKSUM
Specifies the maximum number of consecutive communication protocol checksum violations, between 0 and 255, before the CP is considered unusable. The default value is 5. A value of zero indicates no threshold exists.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
TIMEUSED
Specifies whether or not CPU time used for CP processing is being recorded. A value of OFF, the default, inhibits such recording; a value of ON requests such recording.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.

NP Sub-operand:

LHID
Specifies a non-zero decimal value between 1 and 65535 for the database Logical-host id to be used if needed for the first NP started. If an LHID has already been established by a currently started CP or NP, this LHID value will not be used unless all CPs and NPs are stopped then an NP is STARTed. A value of zero indicates an LHID is not configured. There is no default value.
Once a CP or NP is started, the LHID being used may be displayed using the DISPLAY SERVER command.
DATABASE
Specifies the name of the database system with which communication is to be established. This name is the leftmost label of the network name defined to either the operating system local host or network Domain Name System (DNS) name established by the network administrator for Vantage. Refer to Teradata® Tools and Utilities for IBM z/OS Installation Guide (B035-3128) for details on configuring network information. A standard IP null address of either '.' or '::' indicates no DATABASE is configured. There is no default value.
This value may not be configured if any NPs are currently started.
DOMAIN
Specifies the name of the domain with which communication is to be established. This name consists of all labels to the right of NTCInn of the Domain Name System (DNS) name established by the network administrator for Vantage. See Teradata® Tools and Utilities for IBM z/OS Installation Guide (B035-3128) for more information on configuring network information.The name may include any zone and prefix using the standard network syntax (a percent sign introducing the zone; a slash introducing the prefix). While a port address may also be specified, since a port specification is not part of a DNS name, the CONFIG NP PORT or SERVICE operands are preferred. But if specified, a port is introduced by a colon (for IPv6, the text before the colon must be enclosed in brackets). A standard IP null address of either '.' or '::' indicates no DOMAIN is configured. There is no default value.
If brackets are used in an IPv6 colon-decimal notation, they must be in the Teradata EBCDIC character set, which requires that the brackets have hexadecimal values of 'AD' for the left bracket and 'BD' for the right bracket. Some editors or ways to issue z/OS commands may convert brackets to other codepoints, preventing their use in TDP commands from those sources.
The DOMAIN value is ignored when resolving the NP name using information defined to the z/OS local host. For more information, see Teradata® Tools and Utilities for IBM z/OS Installation Guide (B035-3128).
This value may not be configured if any NPs are currently started.
RETRYMSG
Specifies how often a TDP3512 message is issued when an NP is attempting to establish communication with the database, and ENABLE NPCOMM DETAIL has been issued. While the number of attempts is included in the response to the 'DISPLAY NP' command, network reliability warrants automatically confirming that TDP continues to attempt re-establishment. After an attempt to establish communication has failed the specified contiguous number of times, a TDP3512 message is issued. Since communication is retried every minute, a TDP3512 is issued approximately every that number of minutes. The value can range from 0 to 65535. A value of zero inhibits TDP3512 messages. The default value is 15.
IPSTACK
Specifies the name of the operating system IP stack to be used. The default is the default stack as configured by the operating system. The configured IP stacks may be displayed using the z/OS 'DISPLAY TCPIP' command.
This value may not be configured if any NPs are currently started.
IPVER
Specifies which versions of IP addressing will be used, as either '4' for IPv4 only, '6' for IPv6 only, or 'DUAL', the default. For z/OS, a value of '6' is rejected since z/OS does not currently support an IPv6-only stack. The default IP addressing is 'DUAL'.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
IPXPORT
Specifies the network IP transport mechanism to be used, as 'TCP'.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
PORT
Specifies a non-zero decimal value between 1 and 65535 for the network port on the database associated with NPs. A value of zero indicates that no port is configured. The default port is 64432.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
TU
Specifies whether or not Transmission Unit (TU) summary information is recorded in an internal diagnostic storage table. A value of NORECORD, the default, inhibits such recording; a value of RECORD requests such recording.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
PROTOCOL CHECKSUM
Specifies whether communication protocol checksum processing is forced OFF, forced ON, or automatically adjusts to whether the database presents such checksums (AUTO). The default value is 'ON'.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
PROTOCOL MAXCKSUM
Specifies the maximum number of consecutive communication protocol checksum violations, between 0 and 255, before the NP is considered unusable. A value of zero, the default, indicates no threshold exists.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
SERVICE
Specifies the name of the service that is associated with the network port on the database to be used. The name is as defined by the database network administrator. If the service name cannot be resolved, the numeric PORT value is used.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
STORAGE
Specifies the maximum number of bytes of virtual storage that may be used for buffers by all NPs. The minimum value is dynamically calculated as the minimum storage required by all currently started NPs. The maximum value is 4294967295.
The STORAGE value is not the amount of storage allocated, simply an upper limit. If an NP is subsequently started that would increase the minimum storage required for all started NPs beyond the STORAGE value, the START will fail. When STORAGE is not specified, the maximum is dynamically calculated based on the number of NPs that are started, and the values for MAXBLKNM and MAXBLKSZ. Once specified, TDP must be restarted to revert to dynamic calculation of the maximum
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXBLKNM
Specifies the maximum number of I/O buffers, between 1 and 255, to be used for a network transmission. The default value is 4. This recommendation may be reduced by the database for an NP when it is started.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXBLKSZ
Specifies the maximum size of an I/O buffer, between 80 and 65535 bytes, to be used for network transmission. The default value is 65535. This recommendation may be reduced by the database for a NP when it is started.
This value may not be configured if any NPs are currently started.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXCKSUM
Specifies the maximum number of consecutive communication protocol checksum violations, between 0 and 255, before the NP is considered unusable. A value of zero, the default, indicates no threshold exists.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
TIMEUSED
Specifies whether or not CPU time used for NP processing is being recorded. A value of OFF, the default, inhibits such recording; a value of ON requests such recording.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.

XP Sub-operands

SELECT
Specifies the algorithm used to select which CP or NP is used to send a request to the database, chosen as one of the following: FIRST if the first available CP or NP is used; NEXT if the one after the one last chosen is used; LOWOMSG if the one with the lowest number of requests sent is used; or LOWDATA, the default, if the one with the lowest total number of bytes sent and received is used.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.
MAXNORSP
Specifies the number of consecutive requests that TDP will consider excessive that have been sent to the database on a particular CP or NP without receiving any responses. If this occurs, TDP considers that CP or NP unresponsive. If other CPs or NPs are available, the unresponsive one will be quiesced until a response is received: no more requests will be sent using it. The default value is 75. A value of zero indicates TDP will never quiesce a CP or NP.
This operand is intended for use in consultation with Teradata customer support personnel: internal knowledge of TDP is required for proper use, without which, unintended results are probable.

Usage Notes

Some operands may not be changed at all times.

Example: CONFIG

CONFIG NP LHID 55

Completion Message

Each operand issues a message when successfully configured. Typical of these messages is the following one, for CONFIG NP LHID 55:

TDP3720 NP LHID IS NOW 55 (WAS 46)