Automatic-redrive - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Automatic-redrive is a one byte EBCDIC field that indicates whether a request be automatically redriven after, instead of aborted by, a database restart.

Automatic-redrive is currently ignored for a mainframe-connected system.
In this language... The variable name for Automatic-redrive is...
COBOL AUTOMATIC-REDRIVE
PL/I AUTOMATIC_REDRIVE
C, C++ automaticRedrive
IBM Assembler DBCNIAR
This routine... Does this for Automatic-redrive...
DBCHINI writes
DBCHCL reads (RCON)
Automatic-redrive is used by... To...
applications write.

One of the following values may be set before connecting a session:

If... Then set Automatic-redrive to...
indicates that a request be aborted by a database restart. 'N'
  • DBC-NO for COBOL
  • DBC_AUTO_REDRIVE_NO for PL/I
  • DBC_AutoRedriveNo for C and C++
  • DBCNIARN for Assembler
indicates that a request be automatically redriven after a database restart, subject to Database controls that may ignore the specification. 'Y'
  • DBC-YES for COBOL
  • DBC_AUTO_REDRIVE_YES for PL/I
  • DBC_AutoRedriveYes for C and C++
  • DBCNIARY for Assembler
indicates that the Database decide whether a request be automatically redriven after, instead of aborted by, a database restart 'D'
  • DBC-DEFAULT for COBOL
  • DBC_AUTO_REDRIVE_DFLT for PL/I
  • DBC_AutoRedriveDflt for C and C++
  • DBCNIARD for Assembler

If not specified, the default from the HSHSPB is used, which as distributed is 'D'. If no HSHSPB default is provided, then 'D' is assumed.