Unregister a module

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

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

The following example unregisters version 4.13 of a Map module:
EXECUTE FUNCTION sysbldprepare('map.4.13','drop');

When you unregister a 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 module:
EXECUTE FUNCTION sysbldprepare('map.*','drop');
The 'drop' argument does not implicitly unregister other 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 module on which another module that is currently registered in the database depends. For example, suppose you create a WorldView module that is dependent on the Map module. You cannot use this function to unregister the Map module while the WorldView module is still registered.
EXECUTE FUNCTION sysbldprepare('map.*','drop');
You can unregister the Map module without SYSBldPrepare( ) throwing an exception if you first unregister the dependent WorldView 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( ).