Unregister a DataBlade module

To unregister a DataBlade module, run the SYSBldPrepare( ) function with the DataBlade module reference and the 'drop' arguments.

For the complete calling syntax and the signature of the SYSBldPrepare( ) function, see its description in the IBM® Informix® Guide to SQL: Syntax.

The following example unregisters version 4.13 of a Map DataBlade module:

EXECUTE FUNCTION sysbldprepare('map.4.13','drop');

When you unregister a DataBlade module with the 'drop' argument, the asterisk notation specifies the version of the specified module that is registered in the database.

The following example unregisters the currently registered version of the Map DataBlade module:

EXECUTE FUNCTION sysbldprepare('map.*','drop');

The 'drop' argument does not implicitly unregister other DataBlade modules that have dependency relationships with the module specified by the first argument. The SYSBldPrepare( ) function issues an error if you attempt to unregister a DataBlade module on which another DataBlade module that is currently registered in the database depends. For example, suppose you create a WorldView DataBlade module that is dependent on the Map DataBlade module. You cannot use this function to unregister the Map DataBlade module while the WorldView DataBlade module is still registered.

EXECUTE FUNCTION sysbldprepare('map.*','drop');

You can unregister the Map DataBlade module without SYSBldPrepare( ) throwing an exception if you first unregister the dependent WorldView DataBlade module:

EXECUTE FUNCTION sysbldprepare('worldview.*','drop');
EXECUTE FUNCTION sysbldprepare('map.*','drop');

Calls to the SYSBldPrepare( ) function can return error messages. For information about these error messages, see Exceptions in calls to SYSBldPrepare( ).