TIMEOUT parameter - Revision history

DCameron: /* Description */

2017-09-28T13:52:15Z

Description

← Older revision		Revision as of 13:52, 28 September 2017
Line 37:		Line 37:
	</table>		</table>
	<p>If TIMEOUT is nonzero, <var class="product">Model 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 204</var> MONITOR command, and not available to the user. </p>		<p>If TIMEOUT is nonzero, <var class="product">Model 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 204</var> MONITOR command, and not available to the user. </p>
	<p>The <var class="product">Model 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 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 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 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]]

DCameron: /* Description */

2017-09-28T13:40:11Z

Description

← Older revision		Revision as of 13:40, 28 September 2017
Line 23:		Line 23:
	<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 [[Horizon_TCP/IP\|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>

DCameron: /* Description */

2017-09-28T13:38:45Z

Description

← Older revision		Revision as of 13:38, 28 September 2017
Line 22:		Line 22:
	<tr class="head"><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 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>

DCameron: /* Description */

2017-09-28T13:35:06Z

Description

← Older revision		Revision as of 13:35, 28 September 2017
Line 18:		Line 18:
	<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 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 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 class="head"><th>IODEV</th><th>Access method/device type</th></tr>		<tr class="head"><th>IODEV</th><th>Access method/device type</th></tr>

DCameron: /* Description */

2017-09-28T13:34:00Z

Description

← Older revision		Revision as of 13:34, 28 September 2017
Line 16:		Line 16:
	==Description==		==Description==
	<p>The number of seconds <var class="product">Model 204</var> waits for terminal input before executing a soft restart of the thread</p>		<p>The number of seconds <var class="product">Model 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 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 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 IODEV settings:</p>

DCameron: /* Summary */

2017-09-28T12:58:54Z

Summary

← Older revision		Revision as of 12:58, 28 September 2017
Line 11:		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 204</var> waits for terminal input before executing a soft restart of the thread</p>		<p>The number of seconds <var class="product">Model 204</var> waits for terminal input before executing a soft restart of the thread</p>

ELowell: removed italics from table headers

2017-03-30T22:40:19Z

removed italics from table headers

← Older revision		Revision as of 22:40, 30 March 2017
Line 19:		Line 19:
	<p>Inactive thread timeout is ignored with the following IODEV settings:</p>		<p>Inactive thread timeout is ignored with the following IODEV 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 TCP/IP Horizon SQL thread</td></tr>
Line 31:		Line 31:
	<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>

DmeWiccan: Automatically generated page update

2013-08-27T16:48:12Z

Automatically generated page update

← Older revision		Revision as of 16:48, 27 August 2013
Line 1:		Line 1:
			{{Template:TIMEOUT parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

DmeWiccan: Automatically generated page update

2013-04-23T02:06:16Z

Automatically generated page update

← Older revision		Revision as of 02:06, 23 April 2013
Line 36:		Line 36:
	<p>If TIMEOUT is nonzero, <var class="product">Model 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 204</var> MONITOR command, and not available to the user. </p>		<p>If TIMEOUT is nonzero, <var class="product">Model 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 204</var> MONITOR command, and not available to the user. </p>
	<p>The <var class="product">Model 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 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 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 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]]

Alex: Automatically generated page update

2013-02-28T00:57:09Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Default value
<dd>0
<dt>Parameter type
<dd>User
<dt>Where set
<dd>On user's parameter line
<dt>Related products
<dd>All
<dt>Introduced
<dd><var class="product">Model 204 V6.1</var> or earlier
</dl>
==Description==
<p>The number of seconds <var class="product">Model 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 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>Inactive thread timeout is ignored with the following IODEV settings:</p>
<table>
<tr><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>19</var></th><td>VTAM or 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>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>45</var></th><td>CMS console (line-at-a-time) </td></tr>
<tr><th align="right"><var>47</var></th><td>CMS full screen console </td></tr>
<tr><th align="right"><var>49 </var></th><td>VTAM or TCP/IP Horizon Remote Command Line (RCL) thread</td></tr>
</table>
<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>
<tr><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>29</var></th><td>CRAM line-by-line</td></tr>
</table>
<p>If TIMEOUT is nonzero, <var class="product">Model 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 204</var> MONITOR command, and not available to the user. </p>
<p>The <var class="product">Model 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 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:Parameters]]