Session Configuration Procedures

These built-in SPL procedures enable the Database Administrator to execute SQL and SPL statements automatically when a user connects to or disconnects from the database.

These routines are called "built-in" procedures in this document because the database server recognizes their names and treats them differently from how it treats other routines, but the database server does not create these routines automatically. To use their features, the DBA must issue the CREATE PROCEDURE statement or the CREATE PROCEDURE FROM statement to define the actions of these routines and to register them in the database. Only the DBA or user informix can create, alter, or drop these routines.

If the DBA specifies the login ID of a user as the owner of one of these procedures, the database server executes it when the specified user connects to or disconnects from the database. If the DBA specifies PUBLIC as the owner, that routine is automatically executed when a user who is not the owner of any of these built-in session configuration procedures connects to or disconnects from the database. Different databases of the same database server instance can specify either the same or different session configuration procedures for individual users or for PUBLIC. These built-in procedures are useful in setting the session environment or activating a role for users of applications whose code cannot easily be modified.

These are the built-in session configuration procedures:
  • sysdbclose
  • sysdbopen
Instances of the SYSDbOpen and SYSDbClose routines can be defined for individual users, for roles, and for the PUBLIC group in every HCL OneDB™ database.