Hello, i'm a SAS beginner and i have a question:
i'm trying to archive a part of my dataset
data _null_;
format archive_date date9.;
archive_date = date() - (30);
put 'Archief_datum = ' archive_date;
call symput('archive_date',left(put(archive_date,12.)));
run;
data...
hello, long time, i got a question
in parameter file
modules = MODULE_A MODULE_B
but every module can have different locations, can i do the follwoing
in the parameter file make a var with the names of the module
MODULE_A = LOCATION_1 LOCATION_2 LOCATION_3
MODULE_B = LOCATION 1 LOCATION 4...
no problem, i'm figuring it out but i got stuck by a simple thing and you are the guy that can help me
it it's quite simple, i've got 2 lists now
a list of all mappings in a module
a list of all variables i entered in parameter file ( modules = MOD_A MOD_B ...
now i'm trying to compare them...
well, in my program Oracle Warehouse Builder you got the following tree:
My_Project
DWH_Module
Mappings
DIM_CUSTOMERS_FRANCE
BI_MODULE
TEST_MODULE
in text parameter file i ask modules,mappings
[MODULE VARIABEL]
modules = DWH_MODULE BI_MODULE TEST_MODULE...
Next question:
Now i say:
DWH_Module, BI_MODULE, Module TEST_MODULE
DIM_CUSTOMERS_FRANCE_MAP, DIM_TIJD_MAP
but DIM_TIJD_MAP only belongs to BI_MODULE, i have to make a check..
OUTPUT:
0 : DWH_MODULE
reconciling: DIM_CUSTOMERS_FRANCE_MAP
reconciling: DIM_TIJD_MAP
1 : BI_MODULE...
ok thanks.. i can read the variables but i have an OMB/logical problem:
OMBCONNECT $user/$pass@$host:$port:$service
puts "Connected"
OMBCC '//$project' (move in the tree to project)
for {set i 0} {$i<[llength $conf(modules)]} {incr i} {
puts "$i : [lindex $conf(modules) $i]"
set...
oh ok,
now i will explain what i tried to explain a few posts before
i let people let in the parameter file but i'm looking for the best method
method A:
module1 = name1
module2 = name2
module3 = name3
...
OR!
method B:
modules = name1,name2,name3,...
i need to know how many modules there...
ok,nice! it works now
now i can start the real work: programming OMBPlus scripts for oracle warehouse builder,familiar with that?
my code to read my parameter file, connect to the repository and to give me a list of tables of a specific module (all thanks to you :D)
set section "GLOBALE...
when i change the name i get the same error
but when i declare in the proc itselves my location of my file it hasn't a problem with that
so it has to have to something with how the parameters are distributed below the procedure, in to the procedure
i also get the same error for section
i can...
ok, thanks,but can you tell me why he gives me an error:
can't read name, no such variable
on line: set fil [open $name r]
loadconf "C:/parameter.txt" {}
puts [array names conf]
while this path really exists!
When i enter the path in the procedure:
set fil [open "C:/parameter.txt" r]
it...
Ok, will formulate that later on.
loadconf "C:/parameter.txt" {}
puts [array names conf]
==> this piece of code should make the procedure loadconf load all variables, right?
proc loadconf {name section} \
{
global conf
# array set conf {}
set needed 0
set fil [open "C:/parameter.txt"...
i think i just read the file once in the same script with same parameters
is the following possible:
Parameter file:
MODULES:
name: ALL
or
name: A,B,C
when importing the variables, when all i call all modules in my project in Oracle WB
when A,B,C i split them into variables with the comma?
or...
the same line by content
proc loadconf {name section} \
{
global conf
array set conf {}
puts "Test"
array unset conf
puts "Test2"...
it only displays Test
I use $conf when i declare my variables
set user $conf(user)
set host $conf(host)
set pass $conf(password)
set service...
proc loadconf {name section} \
{
global conf
array unset conf
set needed 0
set fil [open $name r]
while {![eof $fil]} {
set line [gets $fil]
if {$line=="" || [string range $line 0 0]=="#"} { continue }
if {[string match {\[?*\]*} $line]} {
set needed 0
foreach...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.