- Teradata Director Program (TDP)
- Mainframe Cloud-Network Connectivity (Gateway)
The TDP variant of MultiLoad uses the channel-attached CLI to interface with the Analytics Database, which requires a channel connection.
The Gateway variant of MultiLoad uses the network-attached CLIv2 to interface with the Analytics Database, which uses the Database Gateway software.
The following table shows differences between the two variants:
| For | TDP Variant | Gateway Variant |
|---|---|---|
| Access to Analytics Database on a cloud | No with direct channel connection | Yes |
| Channel connection | Yes, required | No |
| CLIv2 | Uses channel-attached CLI | Uses network-attached CLI |
| CLIv2 error codes | Uses channel-attached CLI error codes | Uses network-attached CLIv2 error codes |
| Connection string | Not supported | Supported |
| Interface with Gateway software | No | Yes |
| Longer session connection time | No | Possibly |
| <hlq>.ETC.IPNODES member file | Not required | Yes, required |
| Display of variant in MultiLoad log | CLIv2 : <Version> (TDP) | CLIv2 : <Version> (GTW) |
| Supported SQL Engine versions | All supported versions | 17.10.00.00 or later 17.05.05.03 or later 16.20.53.31 or later |
The Gateway variant of MultiLoad can take a longer time to connect sessions, as there is more overhead between the network-attached CLIv2 and the Database Gateway software for authentication and encryption. This overhead does not exist in the TDP variant of MultiLoad.
The Gateway variant of MultiLoad requires COP entries in the <hlq>.ETC.IPNODES member file. The entries must define the IP address and COP alias name for each database node. <hlq> is the site defined high level qualifier data set name. The TDP variant does not use the <hlq>.ETC.IPNODES member file.