My own particular solution about the $ENV{ODBCHOME} is to have the script set it. It's the only %ENV setting I mess with on runtime. My reason for doing this is my scripts can use multiple DBMS and so I actually set $ENV{$DBTYPE} in order to provide the DBD driver the environment that it will need when I need it. Plus, setting the necessary environment variables may come in handy when you don't know whether a given user will have it set when they wish to run your code.

Especially in this case, you don't really need $ENV{ODBCHOME} hanging around when you're not running the script since any system tools such as odbctest (a tool that comes with the Openlink driver) already have it built in.

ALL HAIL BRAK!!!

In reply to Re: Re: $ENV question by PsychoSpunk
in thread $ENV question by radagast

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.