datablade registration in ANSI database

Hi, everybody, Is there any documented way to register the datablade module in ANSI database? Both Windows-based 'BladeManager' and command-line 'blademgr' do not support ANSI databases.... Any workaround? -Alexey sending to informix-list

What if you change your database to BUFFERED mode, register datablade and change your database back to ANSI (if you really need to). This is just an idea. I have never tried this myself... Gorazd "Alexey Sonkin" <alexeis@grandvirtual.com> wrote in message news:1102549107.c51b39b9d89abb41e6f4d2129134417e@teranews... > > Hi, everybody, > > Is there any documented way to register the datablade module > in ANSI database? > > Both Windows-based 'BladeManager' and command-line 'blademgr' > do not support ANSI databases.... > > Any workaround? > > -Alexey > > > sending to informix-list

Gorazd Hribar Rajteriďż˝ wrote: > What if you change your database to BUFFERED mode, register datablade > and change your database back to ANSI (if you really need to). > > This is just an idea. I have never tried this myself... You can't change the logging mode on a MODE ANSI database, AFAIK. You could create the database as a regular logged database and then add the blades, and finally convert to MODE ANSI -- that should work. > "Alexey Sonkin" <alexeis@grandvirtual.com> wrote: >> Is there any documented way to register the datablade module >> in ANSI database? >> >> Both Windows-based 'BladeManager' and command-line 'blademgr' >> do not support ANSI databases.... >> >> Any workaround? Open a case with Tech Support. Get them to dig out the FR (Feature Request) for this - and add your name to the list of people needing it. Longer lists of cases help give such things priority. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/

Alexey Sonkin wrote: > Hi, everybody, > > Is there any documented way to register the datablade module > in ANSI database? > > Both Windows-based 'BladeManager' and command-line 'blademgr' > do not support ANSI databases.... > > Any workaround? > > -Alexey > > > sending to informix-list Hi, this work for us:( IDS 9.21UC4 on Solaris with ansi databases ) to register a datablade in a database using SQL, the first step is to prepare the datablade modules: EXECUTE FUNCTION SYSBldPrepare('ifxmngr', 'sysblderrorlog');This must be executed every time you connect before executing other routines. sysblderrorlog is a temporary system catalog table which logs the errors. You can check for blade registration errors with the following SQL: SELECT * FROM sysblderrorlog WHERE err_expected != 'expected'; SELECT * FROM 'informix'.sysblderrorlog WHERE err_expected !='expected'; The WHERE clause will avoid certain errors which are expected, such as failure to drop existing versions of the blade because there are none. To determine what datablade modules are available, use the following query: SELECT * FROM sysbldmodules; SELECT * FROM 'informix'.sysbldmodules; -_ Die Tabelle existiert nicht. Aber daf'r funktioniert folgendes: SELECT * FROM 'informix'.sysbldregistered; Next, simply register the datablade: EXECUTE FUNCTION SysBldRegister('BLADE.VERSION','sysblderrorlog');where BLADE.VERSION is the name of the blade and the complete version, and must match the directory in $INFORMIXDIR/extend/ Certain blades require other blades to be registered first. For example, Excalibur Text Search requires the TXT and LLD blades. blademgr will automatically register the blade, but SysBldRegister() will not. You must register each blade separately and in order: execute function sysbldregister('LLD.1.20.UC2','sysblderrorlog'); execute function sysbldregister('TXT.1.10.UC5','sysblderrorlog'); execute function sysbldregister('ETX.1.30.UC5','sysblderrorlog'); To unregister a blade, simply use the following: *** EXECUTE FUNCTION SysBldUnregister('BLADE.VERSION','sysblderrorlog'); execute function sysbldunregister('ETX.1.30.UC5','sysblderrorlog'); execute function sysbldunregister('TXT.1.10.UC5','sysblderrorlog'); execute function sysbldunregister('LLD.1.20.UC2','sysblderrorlog'); hth :-) Jochen