Informix Stored Procedure Language ships inside .sql files alongside DDL, GRANT statements, comments, and other SQL. BLT walks each .sql file, locates every CREATE PROCEDURE or CREATE FUNCTION block, and captures the signature, parameter list, return shape, and body span. One procedure per file is the exception, not the rule — production schemas routinely concatenate dozens of procedures into a single deployment .sql, and BLT handles the whole file in one pass.
-- @test EXECUTE FUNCTION sp_validcache(50.0)
-- @test EXECUTE FUNCTION sp_validcache(-5.0)
-- @test EXECUTE FUNCTION sp_validcache(150.0)
CREATE PROCEDURE sp_validcache(p_cache SMALLFLOAT)
RETURNING SMALLFLOAT;
DEFINE l_sqlerr INTEGER;
DEFINE l_isamerr INTEGER;
DEFINE l_str CHAR(256);
ON EXCEPTION SET l_sqlerr, l_isamerr, l_str
INSERT INTO errorlog
VALUES(CURRENT, l_sqlerr, l_isamerr, "sp_validcache:"
|| DBINFO('sessionid') || ":"
|| TRIM(p_cache) || ":" || TRIM(l_str));
RAISE EXCEPTION l_sqlerr;
END EXCEPTION
IF p_cache < 0 THEN
LET p_cache = 0;
END IF
IF p_cache > 100 THEN
LET p_cache = 100;
END IF
RETURN p_cache;
END PROCEDURE;
mode: recovery
inputs:
source_spl:
paths: [examples/sp_validcache.sql]
output:
directory: ./report/
| Surface | What's recovered for sp_validcache |
|---|---|
| Procedure signature | Procedure name (sp_validcache), parameter list (p_cache SMALLFLOAT), and return shape (SMALLFLOAT) — everything a caller needs to know to invoke it. |
| Source location | File and line, so a reviewer can navigate from the spec back into the deployment script. |
| Mixed-content tolerance | A single .sql file routinely carries both DDL and SPL. The same file can be configured under DDL and SPL inputs together — the schema loader skips procedure blocks, the procedure extractor skips DDL and other top-level SQL, and the same fact never lands twice. |
To discuss how Oninit ® can assist please call on +1-913-732-8892 or alternatively just send an email specifying your requirements.
You get all this for free.. think about what you get if you pay us