bkatom:
Application shell
Command line usage:
bkatom [-conf=bk.ini] program
bkatom [-conf=bk.ini] program
-conf=bk.ini is optional, thanks to this you can set custom ini file with configuration. If you not set this it will take "bk.ini" from directory where bklang compilator is placed
program is program name which will be run. It can be relative path (in SOPATH) or absolute path.
bk.ini configuration file
[bkatom]
SQLLIBDIR=${BASE}/bin/
SOPATH=${BASE}/apps/so/:${BASE}/tests/
PIPEDIR=${GLOBAL_PIPE}
LOGFILE=${GLOBAL_LOGFILE}
LOGSHM=${GLOBAL_LOGSHM}
DEBUG1=0
SNOOP1=1
SNOOP2=1
SNOOP3=1
CONSOLE1=1
CLOSE1=1
[connector:qad]
DRIVER=progress
DATASOURCE=mfgdb
USER=sysprogress
PASS=sysprogress
ODBCINI=${BASE}/tmp/progress/samples/example/odbc.ini
LD_LIBRARY_PATH=${BASE}/tmp/progress/lib
[db:mfgdb]
REALNAME=mfgdb
CONNECTOR=qad
[db:qadcust]
REALNAME=qadcust
CONNECTOR=qad
[bkatom]
SQLLIBDIR=${BASE}/bin/
SOPATH=${BASE}/apps/so/:${BASE}/tests/
PIPEDIR=${GLOBAL_PIPE}
LOGFILE=${GLOBAL_LOGFILE}
LOGSHM=${GLOBAL_LOGSHM}
DEBUG1=0
SNOOP1=1
SNOOP2=1
SNOOP3=1
CONSOLE1=1
CLOSE1=1
[connector:qad]
DRIVER=progress
DATASOURCE=mfgdb
USER=sysprogress
PASS=sysprogress
ODBCINI=${BASE}/tmp/progress/samples/example/odbc.ini
LD_LIBRARY_PATH=${BASE}/tmp/progress/lib
[db:mfgdb]
REALNAME=mfgdb
CONNECTOR=qad
[db:qadcust]
REALNAME=qadcust
CONNECTOR=qad