Close Database File Exit Program

The Close Database File exit program is called when a job is trying to lock a file that is currently held by another job due to existence of pseudo closed cursors. If the file is no longer being used, locks are being held over the file to improve the performance of the next SQL open in the job. The locks can be freed to allow the requesting job to use the file.

After a pseudo closed SQL cursor is fully closed, if an exit program is registered to this exit point, database will call the registered exit program in the job that had held the lock. The intent is that the job that had previously held the lock can now free up any additional resources it may have been holding related to the SQL cursor.

For information about adding an exit program to an exit point, see the Registration Facility APIs.

Note: The Close database file exit point ignores any return codes or error messages that are sent from the exit program.

Authorities and Locks

User Profile Authority

*ALLOBJ and *SECADM to add or remove exit programs to the registration facility

Required Parameter

Database close information

Input; CHAR(*)

Information needed by the exit program for the database file to close.

Format of Database Close Exit Information

The following table shows the structure of the close database exit information for format DBCL0100. For a description of the fields in this format, see the Field Descriptions immediately following the table.

Field Descriptions

Database file name. The database file name that another process is attempting to lock. This is always the 10-character system name.

Database file library name. The name of the library containing the database file.

Database file member name. The specific member that another process is attempting to lock. If the member name is *NONE, a file lock is being requested.

Usage Notes

Registration considerations.

Any exit program registered for this exit point must be threadsafe if it will be called in a job that has multiple threads.