TIMESTOP parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V2.1</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The point at which <var class="product">Model 204</var> automatically terminates the run</p> | <p>The point at which <var class="product">Model 204</var> automatically terminates the run</p> | ||
Revision as of 13:55, 28 September 2017
Time allowed for termination
Summary
- Default value
- 1500
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V2.1 or earlier
Description
The point at which Model 204 automatically terminates the run
The run ends when the number of CPU milliseconds left for the run equals the setting of TIMESTOP. To initiate a command or User Language request, the milliseconds remaining must be twice the value of TIMESTOP.
Files can be logically inconsistent after automatic termination. Use of the ROLL BACK and ROLL FORWARD facilities ensures the logical consistency of files.
If TIMESTOP is set to 0, the Model 204 timing facility's automatic shutdown is bypassed. If, in addition, the JCL EXEC statement parameter TIME is set to 1440 (24 hours), the z/OS automatic shutdown is bypassed, and Model 204 continues to run indefinitely until brought down by other means.