Hi all
Can anybody help me understand how does baan system works? when some user tries to login wot all steps baan takes? and wot does the structure of ipc_info signifies?? ??

bshell s 0 0 p ${BSE}/bin/bshell6.2
bshell.inst s 0 0 p ${BSE}/bin/bshell_inst6.2
audit s 501 510 p ${BSE}/bin/audit_srv6.2
sh_server s 0 0 s ${BSE}/bin/sh_server6.2
fs6.2 s 303 335 m ${BSE}/bin/fs6.2
nserver s 0 0 s ${BSE}/bin/nserver6.2
db2v5 s 310 301 p ${BSE}/bin/db2v5_srv6.2
informix s 305 350 p ${BSE}/bin/inf_srv6.2
oracle7 s 302 320 p ${BSE}/bin/ora7_srv6.2
#oracle8 s 302 320 p ${BSE}/bin/ora8_srv6.2
oracle8 p ${BSE}/bin/ora8_srv6.2

Regards
Gaurav gupta

It lists down the actual executable against command name. U specify these command names in BWC , tabledef6.1 , auditdef6.1 etc. By modifying it on cat run a separate executables depending on the command name and startup options. It can help testing or running a wrpper script for main executable.

Not knowing more details. Somebody can shed more info on this.

An extract from Baan help:

# server name
# | operation (s=single/m=multi)
# | | semaphore key
# | | | message key
# | | | | protocol (s/m/p)
# | | | | | path of executable server
# | | | | | |
#---------------------------------------------------------------
bisam s 304 340 s ${BSE}/bin/bisam_server
bisam6.1 s 307 370 s ${BSE}/bin/bisam_srv6.1
btam s 307 370 m /usr1/bse/bin/btam_srv6.1
bshell s 302 320 s ${BSE}/bin/bshell6.1
fs6.1 s 601 610 p ${BSE}/bin/fs6.1

In addition to previous email:

- operation is always s
- operation, semaphore key and message key are skipped in the latest versions
- protocol is extended with the d with stands for dynamic linked Only used for database drivers in ERP 5 and higher and currently only on Windows. Implemented to prevent contact switches between bshell and driver as the Windows kernel has more problems with a a number of process switches compared to UNIX kernels.

Hope this helps,
Dick