Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!fauern!ira.uka.de!smurf!subnet.sub.net!altger!doitcr!hthoene
From: hthoene@doitcr.doit.sub.org (Hermann Thoene)
Newsgroups: comp.databases
Subject: Re: Oracle TWO_TASK
Keywords: Oracle
Message-ID: <1585@doitcr.doit.sub.org>
Date: 29 Jan 91 00:15:40 GMT
References: <1991Jan24.033628.20710@infonode.ingr.com>
Distribution: comp.databases
Organization: DOITCR / FLOENZ1, Public Access Unix Munich/Germany
Lines: 24

In article <1991Jan24.033628.20710@infonode.ingr.com> tensmekl@infonode.ingr.com (Kermit Tensmeyer) writes:
>
>The Unix Environment variable TWO_TASK determines the "default" device
>driver. "F:" indicates the fast (shared memory) driver. While "T:machine:sid"
>indicate a default connect to a remote machine via SQL*Net using TCP/IP.
>
>This all works well with SQL*Plus SQL*Forms imp exp and sqldba. However,
>this kind of default action doesn't seem to effect the default connect 
>under Pro*C. Is there some call or parameters to Pro*C Exec SQL that will
>use either the Environment Variables, the .sqlnet options or the Database Link's
>in the database without my having to recode the standard behavor in my C code.
>

You **must** change your C code to evalute the Environment variable
TWO_TASK with the getenv() call in C. It is left to the application (here
to your PRO*C program) to build the connect string together. So just check
up whether TWO_TASK is set and append the string to the connect string
given to your program.


Servus from Germany

Hermann Thoene,    Muenchen,    Bavaria <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
                                                  hthoene@doitcr.doit.sub.org