MSIR.0301 Using disk buffer monitor: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
(Automatically generated page update)
Line 1: Line 1:
This warning message indicates that [http://m204wiki.rocketsoftware.com/images/9/95/FrelrNew.pdf Fast/Reload] has determined that it cannot use full track I/O to write the table B pages for the database file and instead must go through the <var class="product">Model 204</var> disk buffer monitor. This may be a result of the user specifying the DKONLY option, loading into a pre-release 8 file, loading into an already populated hash or sort key file or some other problem. When operating in this mode, <var class="product">Fast/Reload</var> will tend to work more slowly than when using full track I/O. If performance is a critical concern, you should determine why <var class="product">Fast/Reload</var> is not using full track I/O and correct the problem.
This warning message indicates that [http://m204wiki.rocketsoftware.com/images/9/95/FrelrNew.pdf Fast/Reload] has determined that it cannot use full track I/O to write the table B pages for the database file and instead must go through the <var class="product">Model 204</var> disk buffer monitor. This may be a result of the user specifying the DKONLY option, loading into a pre-release 8 file, loading into an already populated hash or sort key file or some other problem. When operating in this mode, <var class="product">Fast/Reload</var> will tend to work more slowly than when using full track I/O. If performance is a critical concern, you should determine why <var class="product">Fast/Reload</var> is not using full track I/O and correct the problem.


[[Category:Sirius Mods messages]]
[[Category:Sirius Mods messages]] [[Category:MSIR.0200 - MSIR.0399]]

Revision as of 15:52, 13 August 2015

This warning message indicates that Fast/Reload has determined that it cannot use full track I/O to write the table B pages for the database file and instead must go through the Model 204 disk buffer monitor. This may be a result of the user specifying the DKONLY option, loading into a pre-release 8 file, loading into an already populated hash or sort key file or some other problem. When operating in this mode, Fast/Reload will tend to work more slowly than when using full track I/O. If performance is a critical concern, you should determine why Fast/Reload is not using full track I/O and correct the problem.