Comments on: AS/400 file reorganization/journaling http://itknowledgeexchange.techtarget.com/itanswers/as400-file-reorganizationjournaling/ Tue, 21 May 2013 00:48:46 +0000 hourly 1 By: adrianf http://itknowledgeexchange.techtarget.com/itanswers/as400-file-reorganizationjournaling/#comment-96488 adrianf Tue, 13 Sep 2011 03:52:47 +0000 #comment-96488 If all answers could be this easy ..
It depends on which kind of options you use for the reorg. If you are reorganizing while other programs can still access the file then the story is a little bit different.
When doing an exclusive reorg you will basically create a copy without the holes left by the deleted records and the copy will then replace the original file.
In all other cases the system will shift all records after the first hole to get a continuous file. This method implies lots of inserts and deletes and ………. journal entries. Stopping journalling is an option, but another option to look at is journal caching. Journal caching is changing the way the receivers are physically being written to disk. Normally receivers are written record by record (FORCEWRITE is ON), but with journal caching it will be blockwise and thus less physical writes to disk. BE CAREFUL about this option as the receivers now stay in cache longer and in case of a system failure transactions WILL go missing.

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/as400-file-reorganizationjournaling/#comment-96308 tomliotta Thu, 08 Sep 2011 21:37:03 +0000 #comment-96308 Actually, for some large-file reorganizations, journaling needs to be active. Specifying RGZPFM ALWCANCEL(*YES) requires journaling to be active. See message ID CPF3181 for a reference.)

Tom

]]>