<http://data.openlinksw.com/oplweb/faq/UDA/WhatvaluesdoIpassformyOpenLinkenvironmentvariablesAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/uda-faq.ttl> .
<http://data.openlinksw.com/oplweb/faq/UDA/WhatvaluesdoIpassformyOpenLinkenvironmentvariablesAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/uda-faq.ttl> .
<http://data.openlinksw.com/oplweb/faq/UDA/WhatvaluesdoIpassformyOpenLinkenvironmentvariablesAnswer#this>	<http://www.w3.org/1999/02/22-rdf-syntax-ns#type>	<http://schema.org/Answer> .
<http://data.openlinksw.com/oplweb/faq/UDA/WhatvaluesdoIpassformyOpenLinkenvironmentvariablesAnswer#this>	<http://schema.org/answerExplanation>	"OpenLink's ODBC drivers recognize the following ODBC-specific environment variables.\n    Users should not set ODBC variables manually. OpenLink's drivers ship with openlink.sh and openlink.csh files. These files appear in the root of the OpenLink installation. openlink.sh should be sourced if using Bourne or Bash shells. openlink.csh should be sourced in C shell." .