OMBPlus - TCL - reading variables out of text file

Question

Hello,
i want to read out variables from a text file.
For example to connect
OMBCONNECT $login/$pass@$host:1522:$service
and those 4 variables are in a text file.
i'm a newbie, so it could be a stupid question
thanks!

Answer 1

I should point out that, if you are just using this for variable config then there is a far easier way to do this. Put the assignments in a separate .tcl file and then simply use the "source" command to read it. This becomes very handy as you start to build a library of functions that you will want to re-use across multiple scripts. Think of the command "source" to mean "copy that file and paste it into this one right here"
For example, I have a config file and a library file.
The config file might look like:
#file config.tcl
# GLOBAL VARIABLE DECLARATION SECTION
#CORPORATE DESIGN REPOSITORY  CONNECTION INFORMATION
# Login info for the design repository owner
set OWB_DEG_USER    michael
set OWB_DEG_PASS    mypassword
set OWB_DEG_HOST    ourhost.company.net
set OWB_DEG_PORT    1611
set OWB_DEG_SRVC    orcl And a library file of functions called omb_library.tcl
Now, in all my scripts it starts with:
# File Some_Script.tcl
#  Get Current Script name (excluding file extension), Directory and time
set dtstmp     [ clock format [clock seconds] -format {%Y%m%d_%H%M}]
set scrpt      [ file split [file root [info script]]]
set scriptDir  [ file dirname [info script]]
set scriptName [ lindex $scrpt [expr [llength $scrpt]-1]]
#  Library and config file are in same directory as the script
set cnfg_lib "$scriptDir/config.tcl"
set owb_lib  "$scriptDir/omb_library.tcl"
#  Import Library and config file
#get config file
source $cnfg_lib
#get standard library
source $owb_lib
#  Create a subdirectory under the runnign directory, and create a log-file
#   in that directory based on the script name and timestamp
set LOG_PATH "$scriptDir/logs"
file mkdir $LOG_PATH
set    SPOOLFILE  ""
append SPOOLFILE $LOG_PATH "/log_"  $scriptName "_" $dtstmp ".txt"With this block I eliminate the need to hardcode directories. As long as my config and library files are located with the script I can deploy them anywhere and they will get read and used.
Cheers,
Mike
Edited by: zeppo on Mar 10, 2010 7:40 AM