JNLCLOSED, Journaling closed for database file dddd at transaction number xxx
GT.M run-time warning: This message indicates GT.M had to turn journaling OFF on the specified database. Other preceding messages identify the cause (e.g. lack of disk space while writing to journal file, permissions issue while auto-switching to new journal files etc.). The message also displays the database transaction number.
Fix the issue that caused journaling to get turned OFF in the first place (disk space, permissions etc.).
Turn journaling back ON by issuing a MUPIP SET JOURNAL=ON or MUPIP BACKUP NEWJNL command. This command can work while processes are concurrently updating the database and causes GTM to journal subsequent updates in the journal file.