TIMEOUT parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:TIMEOUT parameter subtitle}}
==Summary==
==Summary==
<dl>
<dl>
Line 10: Line 11:
<dd>All
<dd>All
<dt>Introduced
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var> or earlier
<dd><var class="product">Model 204 V2.1</var> or earlier
</dl>
</dl>
==Description==
==Description==
<p>The number of seconds <var class="product">Model&nbsp;204</var> waits for terminal input before executing a soft restart of the thread</p>
<p>The number of seconds <var class="product">Model&nbsp;204</var> waits for terminal input before executing a soft restart of the thread</p>
<p>A soft restart logs out the terminal user and closes any open files. In addition, if the SYSOPT setting includes a value of 8, <var class="product">Model&nbsp;204</var> disconnects certain types of terminals. The exceptions are listed below. Inactive thread timeout prevents unused terminals from tying up system resources.</p>
<p>A soft restart logs out the terminal user and closes any open files. In addition, if the <var>[[SYSOPT_parameter|SYSOPT]]</var> setting includes a value of 8, <var class="product">Model&nbsp;204</var> disconnects certain types of terminals. The exceptions are listed below. Inactive thread timeout prevents unused terminals from tying up system resources.</p>
<p>If TIMEOUT is set to 0, there is no time limit for terminal input. TIMEOUT must not exceed 32767.</p>
<p>If TIMEOUT is set to 0, there is no time limit for terminal input. TIMEOUT must not exceed 32767.</p>
<p>Inactive thread timeout is ignored with the following IODEV settings:</p>
<p>Inactive thread timeout is ignored with the following <var>[[IODEV_parameter|IODEV]]</var> settings:</p>
<table>
<table>
<tr><th>IODEV</th><th>Access method/device type</th></tr>
<tr class="head"><th>IODEV</th><th>Access method/device type</th></tr>
<tr><th align="right"><var>  3</var></th><td>BSAM</td></tr>
<tr><th align="right"><var>  3</var></th><td>BSAM</td></tr>
<tr><th align="right"><var>19</var></th><td>VTAM or TCP/IP Horizon SQL thread</td></tr>
<tr><th align="right"><var>19</var></th><td>VTAM or [[Horizon_TCP/IP|TCP/IP Horizon SQL]] thread</td></tr>
<tr><th align="right"><var>23</var></th><td>Host Language IFAM2 thread</td></tr>
<tr><th align="right"><var>23</var></th><td>Host Language [[Using_HLI_and_batch_configurations#IFAM2|IFAM2]] thread</td></tr>
<tr><th align="right"><var>31</var></th><td>Host Language IFAM1 thread</td></tr>
<tr><th align="right"><var>31</var></th><td>Host Language IFAM1 thread</td></tr>
<tr><th align="right"><var>43</var></th><td>IUCV Host Language IFAM2 thread</td></tr>
<tr><th align="right"><var>43</var></th><td>IUCV Host Language IFAM2 thread</td></tr>
Line 30: Line 32:
<p>Even if the SYSOPT setting includes a value of 8, specifying a nonzero value for TIMEOUT can be problematic for CICS applications for the IODEV settings shown below: </p>
<p>Even if the SYSOPT setting includes a value of 8, specifying a nonzero value for TIMEOUT can be problematic for CICS applications for the IODEV settings shown below: </p>
<table>
<table>
<tr><th>IODEV</th><th>Access method/device type</th></tr>
<tr class="head"><th>IODEV</th><th>Access method/device type</th></tr>
<tr><th align="right"><var>11</var></th><td>CRAM 3270 </td></tr>
<tr><th align="right"><var>11</var></th><td>CRAM 3270 </td></tr>
<tr><th align="right"><var>29</var></th><td>CRAM line-by-line</td></tr>
<tr><th align="right"><var>29</var></th><td>CRAM line-by-line</td></tr>
</table>
</table>
<p>If TIMEOUT is nonzero, <var class="product">Model&nbsp;204</var> restarts an IODEV 11 or IODEV 29 thread when the TIMEOUT waiting time is reached. However, for CICS applications, the thread is not freed from CRAM, not reported as used by the <var class="product">Model&nbsp;204</var> MONITOR command, and not available to the user. </p>
<p>If TIMEOUT is nonzero, <var class="product">Model&nbsp;204</var> restarts an IODEV 11 or IODEV 29 thread when the TIMEOUT waiting time is reached. However, for CICS applications, the thread is not freed from CRAM, not reported as used by the <var class="product">Model&nbsp;204</var> MONITOR command, and not available to the user. </p>
<p>The <var class="product">Model&nbsp;204</var> CICS Interface has a timing parameter that you can set to have the interface automatically clear for CICS use any threads that were restarted by <var class="product">Model&nbsp;204</var>. IODEV 11 or IODEV 29 users without this option can keep their threads available by making sure that TIMEOUT=0 for their threads.</p>
<p>The <var class="product">Model&nbsp;204</var> [[CICS_terminal_interface|CICS Interface]] has a timing parameter that you can set to have the interface automatically clear for CICS use any threads that were restarted by <var class="product">Model&nbsp;204</var>. IODEV 11 or IODEV 29 users without this option can keep their threads available by making sure that TIMEOUT=0 for their threads.</p>
[[Category:User Parameters]]
[[Category:User parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Latest revision as of 13:52, 28 September 2017

Inactive thread timeout in seconds

Summary

Default value
0
Parameter type
User
Where set
On user's parameter line
Related products
All
Introduced
Model 204 V2.1 or earlier

Description

The number of seconds Model 204 waits for terminal input before executing a soft restart of the thread

A soft restart logs out the terminal user and closes any open files. In addition, if the SYSOPT setting includes a value of 8, Model 204 disconnects certain types of terminals. The exceptions are listed below. Inactive thread timeout prevents unused terminals from tying up system resources.

If TIMEOUT is set to 0, there is no time limit for terminal input. TIMEOUT must not exceed 32767.

Inactive thread timeout is ignored with the following IODEV settings:

IODEVAccess method/device type
3BSAM
19VTAM or TCP/IP Horizon SQL thread
23Host Language IFAM2 thread
31Host Language IFAM1 thread
43IUCV Host Language IFAM2 thread
45CMS console (line-at-a-time)
47CMS full screen console
49 VTAM or TCP/IP Horizon Remote Command Line (RCL) thread

Even if the SYSOPT setting includes a value of 8, specifying a nonzero value for TIMEOUT can be problematic for CICS applications for the IODEV settings shown below:

IODEVAccess method/device type
11CRAM 3270
29CRAM line-by-line

If TIMEOUT is nonzero, Model 204 restarts an IODEV 11 or IODEV 29 thread when the TIMEOUT waiting time is reached. However, for CICS applications, the thread is not freed from CRAM, not reported as used by the Model 204 MONITOR command, and not available to the user.

The Model 204 CICS Interface has a timing parameter that you can set to have the interface automatically clear for CICS use any threads that were restarted by Model 204. IODEV 11 or IODEV 29 users without this option can keep their threads available by making sure that TIMEOUT=0 for their threads.