17.10 - Extended-Load-Usage - Call-Level Interface Version 2

Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems

Product
Call-Level Interface Version 2
Release Number
17.10
Release Date
October 2021
Content Type
Programming Reference
Publication ID
B035-2418-061K
Language
English (United States)

Usage Notes

If using Multiload, you can specify if the traditional or extended protocol will be used.

Specifying Extended-load-usage as 'N' will use the traditional Multiload protocol. If Extended-load-usage is specified as 'Y', the database will use the traditional protocol unless there is anything in the target table that cannot be done with the traditional protocol, in which case it will use the extended protocol. If this option is specified as 'A', the extended protocol will always be used.

Connect-type=C (DBOCTYPE) needs to be specified to use this option.

A Utility-data query can be done to determine the Multiload support in the database. See Other CLI Routines.

In this language... The variable name for Extended-load is...
COBOL EXTENDEDLOADUSAGE
C extendedLoadUsage
If... Then set Extended-load to..
the application has indicated no availability for the extended MultiLoad protocol 'N'
  • DBC_extLoadNo for C
  • DBC-NO for COBOL
the application has indicated that it is available for the extended MultiLoad protocol. The database will determine and use the traditional MultiLoad protocol for the MultiLoad job if that is deemed appropriate when it processes the CHECK WORKLOAD FOR BEGIN MLOAD statement. If the traditional MultiLoad protocol is used, no warning or error will be returned back to the application. If the database has determined that extended MultiLoad protocol is to be used, it will send warning code 9580 (ERRTEQUSEUTCML) back to the application for the CHECK WORKLOAD END statement. Upon getting the warning code, the application must use the extended MultiLoad protocol for the job 'Y'
  • DBC_extLoadYes for C
  • DBC-YES for COBOL
the application has indicated that it is available for the extended MultiLoad protocol and it does not support the traditional MultiLoad protocol. The database will attempt to use the extended MultiLoad protocol for the job. For consistency, warning code 9580 (ERRTEQUSEUTCML) will be returned for the CHECK WORKLOAD END statement to indicate that the extended MultiLoad protocol is to be used. If the database has determined that it cannot proceed with the extended MultiLoad protocol for some reason (e.g., target table is a column partitioned table), it will return an error back to the application 'A'
  • DBC_extLoadAlways for C
  • ALWAYS for COBOL
the application has indicated that no availability for MLOADX. This is treated the same as 'N' which is currently used by the previous version (TTU 14.10) Client. '0'
the application has indicated that it supports MLOADX Phase 2. The database will determine and use the traditional MultiLoad protocol for the MultiLoad job if that is deemed appropriate when it processes the CHECK WORKLOAD FOR BEGIN MLOAD statement. If the traditional MultiLoad protocol is used, no warning or error will be returned back to the Client. If the database has determined that MLOADX Phase 2 is to be used, it will send warning code 9580 (ERRTEQUSEUTCML) back to the Client for the CHECK WORKLOAD END statement. Upon getting the warning code, the Client must use the MLOADX Phase 2 protocol for the job. Note that '2' is treated similar to 'Y' which is used by the previous version (TTU 14.10) Client but '2' is used for Phase 2 protocol and 'Y' is used for Phase 1 protocol. '2'
the application has indicated that it supports MLOADX Phase 2 and it does not support the traditional MultiLoad protocol. This is used for any Client application that only supports MLOADX. The database will attempt to use MLOADX Phase 2 for the job. For consistency, warning code 9580 (ERRTEQUSEUTCML) will be returned for the CHECK WORKLOAD END statement to indicate that MLOADX Phase 2 is to be used. If the database has determined that it cannot proceed with the MLOADX Phase 2 protocol for some reason (i.e., multiple DMLs reference same target table), it will return an error back to the Client. Note that 'B' is treated similar to 'A' which is used by the previous version (TTU 14.10) Client but 'B' is used for Phase 2 protocol and 'A' is used for Phase 1 protocol. 'B'

The default setting is 'N', the application requests the traditional Multiload protocol be used.

This routine... Takes the action for Extended-load..
DBCHCL reads and writes (CON; RSUP)
Extended-load is used by... To...
applications write