1. Overview of SYSBldRelease() Function
From a session connected to a GBase 8s database that supports explicit transaction logging, you can register or unregister DataBlade modules by calling the built-in SYSBldPrepare() SQL function. Another built-in function, SYSBldRelease(), returns the version string of the SYSBldPrepare() function in the local database.
An alternative method for registering and unregistering DataBlade modules using SQL functions is the BladeManager utility. The BladeManager utility can perform various DataBlade module tasks, including registration, unregistration, and displaying information about DataBlade modules. This utility supports both command-line and graphical user interfaces.
SYSBldRelease() is defined with a function signature in all databases of a GBase 8s server instance. You can call this function using the SQL EXECUTE FUNCTION statement or the SPL CALL statement to return the version string of the SYSBldPrepare() function.
2. Detailed Explanation and Application of SYSBldRelease() Function
The following details the definition of the SYSBldRelease() function:
CREATE FUNCTION gbasedbt.sysbldrelease()
RETURNS LVARCHAR
EXTERNAL NAME
'$GBASEDBTDIR/extend/%SYSBLDDIR%/ifxmngr.bld(MackRelease)'
LANGUAGE C NOT VARIANT;
GRANT EXECUTE ON FUNCTION SYSBldRelease() TO PUBLIC;
This function does not take any parameters. It returns the version string and the completion date of the SYSBldPrepare() function.
The returned version string has the following format:
major.minor.os_codeCinterim
Here, C is a literal character, and major, minor, os_code, and interim version string elements have the same semantics as in the Module Reference segment of the SYSBldPrepare() function, without the asterisk (*) wildcard notation.
The SYSBldRelease() function is particularly useful when contacting GBase support with issues related to SYSBldPrepare().
For SYSBldRelease() to return the correct version string of SYSBldPrepare(), the SYSBldPrepare() function must be called at least once in the same database. The call to SYSBldPrepare() does not need to occur in the same session as the call to SYSBldRelease().
Top comments (0)