Extended Security with LOGMECH and LOGDATA | Preprocessor2 for Embedded SQL. - Extended Security with LOGMECH and LOGDATA - Teradata Preprocessor2

Network versions of PP2 09.01.00 and later support LOGMECH and LOGDATA statements for use with logon mechanisms. The mainframe-attached version of PP2 does not support these statements.

Syntax

LOGMECH type
LOGDATA:data_address

C Example

EXEC SQL BEGIN DECLARE SECTION;
 	VARCHAR  LOGON_STRING[40];
 	VARCHAR  LOGDATA_STRING[40];
  EXEC SQL END DECLARE SECTION;

  EXEC SQL
 	LOGMECH LDAP;

  strcpy (LOGDATA_STRING.arr, "authcid=guestldap password=password");
  LOGDATA_STRING.len = strlen(LOGDATA_STRING.len);
  EXEC SQL
 	LOGDATA :LOGDATA_STRING;

  strcpy (LOGON_STRING.arr, "tdname");
  LOGON_STRING.len = 6;
  EXEC SQL
  	LOGON :LOGON_STRING;

Cobol Example

01  LOGON-STRING.
            49 FILLER         PIC S9(4) COMP VALUE +5.
            49 FILLER         PIC X(5) VALUE 'TDP1/'.

        01  LOGDATA-STRING.
            49 FILLER         PIC S9(4) COMP VALUE +28.
            49 FILLER PIC X(28)
                      VALUE 'GUEST@KRB5DOM.PROD@@PASSWORD’

	…
	…
	…

            EXEC SQL
                     LOGMECH KRB5
            END-EXEC.

            EXEC SQL
                     LOGDATA :LOGDATA-STRING
            END-EXEC.

            EXEC SQL
                     LOGON :LOGON-STRING
            END-EXEC. 

If LOGMECH and LOGDATA statements are used to pass logon credentials to the database, it may not be necessary to use the default LOGON dialog box in GUI applications. It depends on the type of logon mechanism that is used. To disable the LOGON dialog box, specify GUILOGON=NO as an environmental variable.