JNLQIOLOCKED, Error obtaining io_in_prog lock on journal file xxxx

Run Time Error: When the last process with write access to a journaled database exits, it does a cleanup of the journal file by attempting to get an exclusive write lock on the journal file. If that fails after waiting for nearly one minute, it issues this error.

Action: Attempt MUPIP RUNDOWN on the region making sure to run down all processes actively attached to this database. If the error persists even after no one is attached, contact your GT.M support channel before proceeding.

inserted by FC2 system