DKUPDTWT parameter: Difference between revisions
| Line 19: | Line 19: | ||
<p>If DKUPDTWT is nonzero, <var class="product">Model 204</var> delays the start of the disk update process for at least DKUPDTWT seconds, after which it can be the checkpoint pseudo subtask (CHKPST) that performs the disk update. The user who completed the last in-flight update does not have to wait for the disk update process to complete. </p> | <p>If DKUPDTWT is nonzero, <var class="product">Model 204</var> delays the start of the disk update process for at least DKUPDTWT seconds, after which it can be the checkpoint pseudo subtask (CHKPST) that performs the disk update. The user who completed the last in-flight update does not have to wait for the disk update process to complete. </p> | ||
<p>If DKUPDTWT is nonzero, the CHKPST and CHKPTIMR pseudo subtasks are started automatically at <var class="product">Model 204</var> initialization. An error message informs you if the <var>[[NSUBTKS_parameter|NSUBTKS]]</var> parameter is set too low to start these pseudo subtasks.</p> | <p>If DKUPDTWT is nonzero, the CHKPST and CHKPTIMR pseudo subtasks are started automatically at <var class="product">Model 204</var> initialization. An error message informs you if the <var>[[NSUBTKS_parameter|NSUBTKS]]</var> parameter is set too low to start these pseudo subtasks.</p> | ||
<p>DKUPDTWT has a maximum of 60, and it also depends on the CPTIME parameter setting. If CPTIME is nonzero, DKUPDTWT must be less than or equal to CPTIME*30. </p> | <p>DKUPDTWT has a maximum of 60, and it also depends on the <var>[[CPTIME_parameter|CPTIME]]</var> parameter setting. If CPTIME is nonzero, DKUPDTWT must be less than or equal to CPTIME*30. </p> | ||
<p>The system manager can reset DKUPDTWT to zero while the online is running, and to a nonzero value as long as the CHKPST and CHKPTIMR pseudo subtasks were started during <var class="product">Model 204</var> initialization.</p> | <p>The system manager can reset DKUPDTWT to zero while the online is running, and to a nonzero value as long as the CHKPST and CHKPTIMR pseudo subtasks were started during <var class="product">Model 204</var> initialization.</p> | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 13:15, 16 October 2014
# seconds after file's last update before file is updated on disk
Summary
- Default value
- 0
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V3.2
Description
How long a disk buffer containing a file's modified pages must have aged (in seconds) before it can be flushed (that is, written to disk)
If DKUPDTWT is zero, Model 204 writes all of a file's modified pages to disk at the end of the last in-flight update of the file. The user who completed the last in-flight update waits for this disk update process to complete and for the message stating that the disk update is complete.
If DKUPDTWT is nonzero, Model 204 delays the start of the disk update process for at least DKUPDTWT seconds, after which it can be the checkpoint pseudo subtask (CHKPST) that performs the disk update. The user who completed the last in-flight update does not have to wait for the disk update process to complete.
If DKUPDTWT is nonzero, the CHKPST and CHKPTIMR pseudo subtasks are started automatically at Model 204 initialization. An error message informs you if the NSUBTKS parameter is set too low to start these pseudo subtasks.
DKUPDTWT has a maximum of 60, and it also depends on the CPTIME parameter setting. If CPTIME is nonzero, DKUPDTWT must be less than or equal to CPTIME*30.
The system manager can reset DKUPDTWT to zero while the online is running, and to a nonzero value as long as the CHKPST and CHKPTIMR pseudo subtasks were started during Model 204 initialization.