JAL: add link

2018-02-26T18:37:30Z

add link

← Older revision		Revision as of 18:37, 26 February 2018
Line 1:		Line 1:
	{{Template:M204.0440 skeleton}}		{{Template:M204.0440 skeleton}}
	<P>		<P>
	This message indicates that Model 204 attempted to write all of the modified pages for the indicated file to disk in order to mark the file PHYSICALLY CONSISTENT. This process is performed at different times, depending on whether the DKUPDTWT parameter is zero: </P>		This message indicates that Model 204 attempted to write all of the modified pages for the indicated file to disk in order to mark the file PHYSICALLY CONSISTENT. This process is performed at different times, depending on whether the <var>[[DKUPDTWT parameter\|DKUPDTWT]]</var> parameter is zero: </P>
	<ul>		<ul>
	<li>If it is zero then the process is performed by a user thread at the end of an update or a set of related updates (such as a ~~User Language~~ request), if no other users are currently updating the file. </li>		<li>If it is zero then the process is performed by a user thread at the end of an update or a set of related updates (such as a SOUL request), if no other users are currently updating the file. </li>

	<li>If DKUPDTWT is non-zero, the process can be performed on a user thread after certain file-related commands or on the CHKPPST PST at periodic intervals or as part of CHECKPOINT processing. When this process is executed from the PST and a user thread attempts to begin an update unit for the file, the DISK UPDATE process may be ABORTed in order to allow the user to begin updating the file. The disk update process will be attempted at a later time when no update units are active. </li>		<li>If <var>DKUPDTWT</var> is non-zero, the process can be performed on a user thread after certain file-related commands or on the CHKPPST PST at periodic intervals or as part of CHECKPOINT processing. When this process is executed from the PST and a user thread attempts to begin an update unit for the file, the DISK UPDATE process may be ABORTed in order to allow the user to begin updating the file. The disk update process will be attempted at a later time when no update units are active. </li>
	</ul>		</ul>
	<P>		<P>
	The "completed" version of the message indicates that all updated file pages, including the File Parameter List, have been successfully written to disk and that FISTAT is set to zero. </P>		The "completed" version of the message indicates that all updated file pages, including the File Parameter List, have been successfully written to disk and that <var>FISTAT</var> is set to zero. </P>
	<P>		<P>
	The "aborted" version of the message indicates that the process of writing pages to disk has been aborted in order to allow a new update unit to proceed (or to allow a user thread to do the disk update). The file remains in an "updated" state, and FISTAT is not set to zero. This version of the message <b>does note</b> indicate that there is an integrity problem with the file, just that it's updates have not yet been fully written to disk. </P>		The "aborted" version of the message indicates that the process of writing pages to disk has been aborted in order to allow a new update unit to proceed (or to allow a user thread to do the disk update). The file remains in an "updated" state, and <var>FISTAT</var> is not set to zero. This version of the message <b>does note</b> indicate that there is an integrity problem with the file, just that it's updates have not yet been fully written to disk.
			</P>
	{{Template:M204.0440 footer}}		{{Template:M204.0440 footer}}
	<!-- skeleton as it was in pdf/filename DISK UPDATE (COMPLETED\|ABORTED) /-->		<!-- skeleton as it was in pdf/filename DISK UPDATE (COMPLETED\|ABORTED) /-->

DmeWiccan: Automatically generated page update

2018-02-23T03:23:06Z

Automatically generated page update

New page

{{Template:M204.0440 skeleton}}

This message indicates that Model 204 attempted to write all of the modified pages for the indicated file to disk in order to mark the file PHYSICALLY CONSISTENT. This process is performed at different times, depending on whether the DKUPDTWT parameter is zero: 
<ul>
<li>If it is zero then the process is performed by a user thread at the end of an update or a set of related updates (such as a User Language request), if no other users are currently updating the file. </li>

<li>If DKUPDTWT is non-zero, the process can be performed on a user thread after certain file-related commands or on the CHKPPST PST at periodic intervals or as part of CHECKPOINT processing. When this process is executed from the PST and a user thread attempts to begin an update unit for the file, the DISK UPDATE process may be ABORTed in order to allow the user to begin updating the file. The disk update process will be attempted at a later time when no update units are active. </li>
</ul>

The "completed" version of the message indicates that all updated file pages, including the File Parameter List, have been successfully written to disk and that FISTAT is set to zero. 

The "aborted" version of the message indicates that the process of writing pages to disk has been aborted in order to allow a new update unit to proceed (or to allow a user thread to do the disk update). The file remains in an "updated" state, and FISTAT is not set to zero. This version of the message does note indicate that there is an integrity problem with the file, just that it's updates have not yet been fully written to disk. 
{{Template:M204.0440 footer}}

M204.0440 - Revision history

JAL: add link

DmeWiccan: Automatically generated page update