VTLAPSY parameter - Revision history

JAL: minor formatting

2017-12-06T23:52:03Z

minor formatting

← Older revision		Revision as of 23:52, 6 December 2017
Line 17:		Line 17:
	==Description==		==Description==
	<var>VTLAPSY</var> is a ten-character resettable User 0 parameter that, if set to a non-blank value, indicates the name of an [[APSY]] subsystem that can be used to		<var>VTLAPSY</var> is a ten-character resettable User 0 parameter that, if set to a non-blank value, indicates the name of an [[APSY]] subsystem that can be used to
	provide full-screen login support for <var>[[IODEV parameter\|IODEV]]</var> 7 terminals (3270-type). For TN3270 connections, the same functionality is provided by the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.		provide full-screen login support for <var>[[IODEV parameter\|IODEV]]</var> 7 terminals (3270-type). For TN3270 connections, the same functionality is provided by the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.

	<p class="warn"><b>Caution:</b> If you set <var>VTLAPSY</var> to a non-existent or non-functional APSY, <code>IODEV=7</code> threads are prevented from logging in. </p>		<p class="warn"><b>Caution:</b> If you set <var>VTLAPSY</var> to a non-existent or non-functional APSY, <code>IODEV=7</code> threads are prevented from logging in. </p>
Line 44:		Line 44:
	<li><code>YOURVT75</code> is entered automatically as a command. </li>		<li><code>YOURVT75</code> is entered automatically as a command. </li>

	<li>The <code>YOURTV75</code> subsystem is expected to format a full screen that prompts the user for a valid ~~userid~~ and password. The subsystem then uses the response to those prompts, along with <var>$Sir_Login</var>, to log the user in. </li>		<li>The <code>YOURTV75</code> subsystem is expected to format a full screen that prompts the user for a valid user ID and password. The subsystem then uses the response to those prompts, along with <var>$Sir_Login</var>, to log the user in. </li>

	<li>If command level is reached without a successful <var>$Sir_Login</var>		<li>If command level is reached without a successful <var>$Sir_Login</var>
Line 51:		Line 51:

	<li>If command level is reached after a successful <var>$Sir_Login</var>,		<li>If command level is reached after a successful <var>$Sir_Login</var>,
	any <var>[[~~AUTOSYS_parameter~~\|AUTOSYS]]</var> subsystem for the thread is processed. </li>		any <var>[[AUTOSYS parameter\|AUTOSYS]]</var> subsystem for the thread is processed. </li>

	<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation.		<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation.
Line 60:		Line 60:
	A sample subsystem that can be used with the <var>VTLAPSY</var> parameter is provided in the [[SIRIUS file]]. Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.		A sample subsystem that can be used with the <var>VTLAPSY</var> parameter is provided in the [[SIRIUS file]]. Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.

	This is an example of how a screen could be designed, using basic SOUL screen definition statements, to provide an alternative to the ">" prompt for logging a full-screen user into a Model 204 ~~online~~:		This is an example of how a screen could be designed, using basic SOUL screen definition statements, to provide an alternative to the ">" prompt for logging a full-screen user into a Model 204 Online:
	<p class="code">		<p class="code">
	/\ * *		/\ * *

DCameron: /* Connection states and processing */

2017-12-06T14:13:09Z

Connection states and processing

← Older revision		Revision as of 14:13, 6 December 2017
Line 51:		Line 51:

	<li>If command level is reached after a successful <var>$Sir_Login</var>,		<li>If command level is reached after a successful <var>$Sir_Login</var>,
	any <var>AUTOSYS</var> subsystem for the thread is processed. </li>		any <var>[[AUTOSYS_parameter\|AUTOSYS]]</var> subsystem for the thread is processed. </li>

	<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation.		<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation.

JAL: move cautionary note

2017-11-22T17:43:08Z

move cautionary note

← Older revision		Revision as of 17:43, 22 November 2017
Line 1:		Line 1:
	{{Template:VTLAPSY parameter subtitle}}		{{Template:VTLAPSY parameter subtitle}}
			__NOTOC__
	==Summary==		==Summary==
	<dl>		<dl>
Line 8:		Line 9:
	<dt>Where set		<dt>Where set
	<dd>User 0 CCAIN parameters and resettable by system managers		<dd>User 0 CCAIN parameters and resettable by system managers
	~~<p><b>Caution:</b>: If you set VTLAPSY to a non-existent or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>~~
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All
Line 16:		Line 16:

	==Description==		==Description==
	<var>VTLAPSY</var> is a ten-character resettable User 0 parameter that, if set		<var>VTLAPSY</var> is a ten-character resettable User 0 parameter that, if set to a non-blank value, indicates the name of an [[APSY]] subsystem that can be used to
	to a non-blank value, indicates the name of an APSY subsystem that can be used to		provide full-screen login support for <var>[[IODEV parameter\|IODEV]]</var> 7 terminals (3270-type). For TN3270 connections, the same functionality is provided by the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.
	provide full-screen login support for IODEV=7 terminals (3270-type). For TN3270 connections, the same functionality is provided ~~via~~ the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.

	When an IODEV=7 terminal connects to <var class="product">Model 204</var>, one of four connection states is possible:		<p class="warn"><b>Caution:</b> If you set <var>VTLAPSY</var> to a non-existent or non-functional APSY, <code>IODEV=7</code> threads are prevented from logging in. </p>

			===Connection states and processing===
			When an <code>IODEV=7</code> terminal connects to <var class="product">Model 204</var>, one of four connection states is possible:
	<ul>		<ul>
	<li>~~Terminal~~ connection contains no user data (the typical case). </li>		<li>The terminal connection contains no user data (the typical case). </li>

	<li>~~Terminal~~ connection is the result of a VTAM transfer of		<li>The terminal connection is the result of a VTAM transfer of
	control from a different <var class="product">Model 204</var> ~~online~~. ~~A zap for <var class="product">SirMods</var> Version 7.7 allows~~ VTAM transfer of control even when RACF is used. </li>		control from a different <var class="product">Model 204</var> Online. VTAM transfer of control is allowed even when RACF is used. </li>

	<li>~~Terminal~~ connection request passed user data, and the X'0040'		<li>The terminal connection request passed user data, and the X'0040'
	bit of <var>[[TERMOPT parameter\|TERMOPT]]</var> is not set. In this case the user data ~~will be~~		bit of <var>[[TERMOPT parameter\|TERMOPT]]</var> is not set. In this case, the user data is processed as a command at connect time. </li>
	processed as a command at connect time~~. </li>~~

	~~<li>Terminal connection contains user data, and <code>TERMOPT=X'0040'</code>.~~
	~~In this case the user data will be prefixed with the string "LOGON " and the result will be processed as a command~~. </li>

			<li>The terminal connection contains user data, and <code>TERMOPT=X'0040'</code>. In this case, the user data will be prefixed with the string "LOGON " and the result is processed as a command. </li>
	</ul>		</ul>

	When an IODEV=7 terminal connects with no user data and <var>VTLAPSY</var> is		When an <code>IODEV=7</code> terminal connects with no user data and <var>VTLAPSY</var> is
	set to a non-blank value (for example, <code>YOURVT75</code>), the following processing is performed:		set to a non-blank value (for example, <code>YOURVT75</code>), the following processing is performed:
	<ol>		<ol>
Line 49:		Line 48:
	<li>If command level is reached without a successful <var>$Sir_Login</var>		<li>If command level is reached without a successful <var>$Sir_Login</var>
	call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer		call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer
	without a successful <var>[[$Sir_Login]]</var> call, an [[MSIR.0722]] non-terminal		without a successful <var>[[$Sir_Login]]</var> call, an [[MSIR.0722]] non-terminal message is issued, and the terminal is disconnected. </li>
	message is issued, and the terminal is disconnected. </li>

	<li>If command level is reached after a successful <var>$Sir_Login</var>,		<li>If command level is reached after a successful <var>$Sir_Login</var>,
	~~then~~ any <var>AUTOSYS</var> subsystem for the thread ~~will be~~ processed. </li>		any <var>AUTOSYS</var> subsystem for the thread is processed. </li>

	<li>Any environmental error in <var>$Sir_Login</var> ~~will result~~ in request cancellation.		<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation.
	<p class="note">'''Note:''' The <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log		<p class="note">'''Note:''' The <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the "APSY SUBSYSMGMT Operational Parameters" screen).</p></li>
	a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the "APSY SUBSYSMGMT Operational Parameters" screen).</p></li>
	</ol>		</ol>

	==Sample APSY==		==Sample APSY==
	A sample ~~apsy~~ that can be used with the <var>VTLAPSY</var> parameter is provided in the ~~<code>~~SIRIUS~~</code>~~ file~~, beginning with [[ULSPF~~]] ~~Version 7.7~~. Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.		A sample subsystem that can be used with the <var>VTLAPSY</var> parameter is provided in the [[SIRIUS file]]. Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.

	This is an example of how a screen could be designed, using basic SOUL screen definition statements, to provide an alternative to the ">" prompt for logging a full-screen user into a Model 204 online:		This is an example of how a screen could be designed, using basic SOUL screen definition statements, to provide an alternative to the ">" prompt for logging a full-screen user into a Model 204 online:
	<p class="code">		<p class="code">

JDamon: /* Summary */

2017-11-22T16:37:39Z

Summary

← Older revision		Revision as of 16:37, 22 November 2017
Line 8:		Line 8:
	<dt>Where set		<dt>Where set
	<dd>User 0 CCAIN parameters and resettable by system managers		<dd>User 0 CCAIN parameters and resettable by system managers
	<p><b>Caution:</b>: If you set VTLAPSY to a non-~~existant~~ or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>		<p><b>Caution:</b>: If you set VTLAPSY to a non-existent or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All

JDamon: /* Summary */

2017-11-22T16:35:49Z

Summary

← Older revision		Revision as of 16:35, 22 November 2017
Line 7:		Line 7:
	<dd>System		<dd>System
	<dt>Where set		<dt>Where set
	<dd>User 0 CCAIN parameters and ~~can be reset~~ by system managers		<dd>User 0 CCAIN parameters and resettable by system managers
	<p><b>Caution:</b>: If you set VTLAPSY to a non-existant or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>		<p><b>Caution:</b>: If you set VTLAPSY to a non-existant or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>
	<dt>Related products		<dt>Related products

JDamon: Added a caution on reset.

2017-11-22T16:32:52Z

Added a caution on reset.

← Older revision		Revision as of 16:32, 22 November 2017
Line 7:		Line 7:
	<dd>System		<dd>System
	<dt>Where set		<dt>Where set
	<dd>User 0 CCAIN parameters		<dd>User 0 CCAIN parameters and can be reset by system managers
			<p><b>Caution:</b>: If you set VTLAPSY to a non-existant or non-functional APSY, then no users will be able to logon via IODEV=7 threads.</p>
	<dt>Related products		<dt>Related products
	<dd>All		<dd>All

JDamon: Added a sample screen showing how VTLAPSY might be used

2015-06-15T17:56:38Z

Added a sample screen showing how VTLAPSY might be used

@@ Line 61: / Line 61: @@
 ==Sample APSY==
 A sample apsy that can be used with the <var>VTLAPSY</var> parameter is provided in the <code>SIRIUS</code> file, beginning with [[ULSPF]] Version 7.7.  Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.
 [[Category:System parameters]]
 [[Category:Parameters]]

JDamon: minor grammatical changes

2015-05-11T22:45:32Z

minor grammatical changes

← Older revision		Revision as of 22:45, 11 May 2015
Line 44:		Line 44:
	<li><code>YOURVT75</code> is entered automatically as a command. </li>		<li><code>YOURVT75</code> is entered automatically as a command. </li>

	<li>The <code>YOURTV75</code> subsystem is expected to format a full screen that prompts the user for a valid userid and password, then it uses <var>$Sir_Login</var> to log the user in. </li>		<li>The <code>YOURTV75</code> subsystem is expected to format a full screen that prompts the user for a valid userid and password. The subsystem then uses the response to those prompts, along with <var>$Sir_Login</var>, to log the user in. </li>

	<li>If command level is reached without a successful <var>$Sir_Login</var>		<li>If command level is reached without a successful <var>$Sir_Login</var>
	call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer		call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer
	without a successful <var>[[$Sir_Login]]</var> call, a [[MSIR.0722]] non-terminal		without a successful <var>[[$Sir_Login]]</var> call, an [[MSIR.0722]] non-terminal
	message is issued, and the terminal is disconnected. </li>		message is issued, and the terminal is disconnected. </li>

Line 55:		Line 55:

	<li>Any environmental error in <var>$Sir_Login</var> will result in request cancellation.		<li>Any environmental error in <var>$Sir_Login</var> will result in request cancellation.
	<p class="note">'''Note:''' A <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log		<p class="note">'''Note:''' The <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log
	a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the "APSY SUBSYSMGMT Operational Parameters" screen).</p></li>		a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the "APSY SUBSYSMGMT Operational Parameters" screen).</p></li>
	</ol>		</ol>

JAL: misc cleanup

2015-05-11T18:21:12Z

misc cleanup

← Older revision		Revision as of 18:21, 11 May 2015
Line 19:		Line 19:
	provide full-screen login support for IODEV=7 terminals (3270-type). For TN3270 connections, the same functionality is provided via the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.		provide full-screen login support for IODEV=7 terminals (3270-type). For TN3270 connections, the same functionality is provided via the <var>[[NEWSESCMD]]</var> parameter on the <var>[[JANUS DEFINE]]</var> command.

	When an IODEV=7 terminal connects to <var class="product">Model 204</var>, one of four connection		When an IODEV=7 terminal connects to <var class="product">Model 204</var>, one of four connection states is possible:
	states is possible:
	<ul>		<ul>
	<li>Terminal connection contains no user data (the typical case).		<li>Terminal connection contains no user data (the typical case). </li>

	<li>Terminal connection is the result of a VTAM transfer of		<li>Terminal connection is the result of a VTAM transfer of
	control from a different <var class="product">Model 204</var> online. A zap for <var class="product">SirMods</var> Version 7.7		control from a different <var class="product">Model 204</var> online. A zap for <var class="product">SirMods</var> Version 7.7 allows VTAM transfer of control even when RACF is used. </li>
	allows VTAM transfer of control even when RACF is used.

	<li>Terminal connection request passed user data, and the X'0040'		<li>Terminal connection request passed user data, and the X'0040'
	bit of <var>TERMOPT</var> is not set. In this case the user data will be		bit of <var>[[TERMOPT parameter\|TERMOPT]]</var> is not set. In this case the user data will be
	processed as a command at connect time.		processed as a command at connect time. </li>


	<li>Terminal connection contains user data, and <code>TERMOPT=X'0040'</code>.		<li>Terminal connection contains user data, and <code>TERMOPT=X'0040'</code>.
	In this case the user data will be prefixed with the		In this case the user data will be prefixed with the string "LOGON " and the result will be processed as a command. </li>
	string "LOGON " and the result will be processed as a command.

	</ul>		</ul>
Line 42:		Line 38:
	set to a non-blank value (for example, <code>YOURVT75</code>), the following processing is performed:		set to a non-blank value (for example, <code>YOURVT75</code>), the following processing is performed:
	<ol>		<ol>
			<li>The user is temporarily "logged in" with a <var>USERID</var> of <code>YOURVT75</code> (the subsystem name), <var>ACCOUNT</var> of <code>NO ACCOUNT</code>, and with X'00' privileges. </li>

	<li>The ~~user is temporarily "logged in" with a USERID =~~ <~~code~~>~~YOURVT75~~</~~code~~> ~~(the subsystem name), ACCOUNT = NO ACCOUNT and with X'00' privileges~~.		<li>The <var>[[$Sir_Login]]</var> function is enabled. </li>

	<li>~~The~~ <~~var~~>~~[[$Sir_Login]]~~</~~var~~> ~~function~~ is ~~enabled~~.		<li><code>YOURVT75</code> is entered automatically as a command. </li>

	<li><code>~~YOURVT75~~</code~~> is entered automatically as a command.~~		<li>The <code>YOURTV75</code> subsystem is expected to format a full screen that prompts the user for a valid userid and password, then it uses <var>$Sir_Login</var> to log the user in. </li>

	~~<li>The <var>YOURTV75</var~~> subsystem is expected to format a full screen ~~which~~ prompts the user for a valid userid and password ~~and~~ then
	uses <var>$Sir_Login</var> to log the user in.

	<li>If command level is reached without a successful <var>$Sir_Login</var>		<li>If command level is reached without a successful <var>$Sir_Login</var>
	call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer		call, or if the <var>VTLAPSY</var> subsystem attempts an APSY transfer
	without a successful <var>[[$Sir_Login]]</var> call, a [[MSIR.0722]] non-terminal		without a successful <var>[[$Sir_Login]]</var> call, a [[MSIR.0722]] non-terminal
	message is issued and the terminal is disconnected.		message is issued, and the terminal is disconnected. </li>

	<li>If command level is reached after a successful <var>$Sir_Login</var>,		<li>If command level is reached after a successful <var>$Sir_Login</var>,
	then any <var>AUTOSYS</var> subsystem for the thread will be processed.		then any <var>AUTOSYS</var> subsystem for the thread will be processed. </li>

	<li>Any environmental error in <var>$Sir_Login</var> will result in request		<li>Any environmental error in <var>$Sir_Login</var> will result in request cancellation.
	cancellation. <br>'''Note:''' A <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log		<p class="note">'''Note:''' A <var>VTLAPSY</var> subsystem must be configured to <i>not</i> log
	a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the ~~<var>~~APSY SUBSYSMGMT Operational Parameters</~~var~~> ~~screen).~~		a user in or out (<code>N</code> settings for <code>Log user into M204</code> and for <code>Log user out of M204</code> in the "APSY SUBSYSMGMT Operational Parameters" screen).</p></li>
	</ol>		</ol>

	==Sample APSY==		==Sample APSY==
			A sample apsy that can be used with the <var>VTLAPSY</var> parameter is provided in the <code>SIRIUS</code> file, beginning with [[ULSPF]] Version 7.7. Programs are <code>VTLN.LOGIN</code> and <code>VTLN.ERROR</code>, and the comments in <code>VTLN.LOGIN</code> explain how to customize the programs for the local environment.
	A sample apsy that can be used with the VTLAPSY parameter is provided ~~by Sirius Software. The code is~~ in the SIRIUS file, beginning with [[ULSPF]] Version 7.7. Programs are VTLN.LOGIN and VTLN.ERROR, and the comments in VTLN.LOGIN explain how to customize the programs for the local environment.

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

JDamon: Clarify actions performed by YOURVT75 subsystem.

2015-05-08T23:39:49Z

Clarify actions performed by YOURVT75 subsystem.

← Older revision		Revision as of 23:39, 8 May 2015
Line 43:		Line 43:
	<ol>		<ol>

	<li>The user is temporarily "logged in" with a ~~User ID~~ = <code>YOURVT75</code> (the subsystem name), ~~account~~ = NO ACCOUNT and with X'00' privileges.		<li>The user is temporarily "logged in" with a USERID = <code>YOURVT75</code> (the subsystem name), ACCOUNT = NO ACCOUNT and with X'00' privileges.

	<li>The <var>[[$Sir_Login]]</var> function is enabled.		<li>The <var>[[$Sir_Login]]</var> function is enabled.
Line 49:		Line 49:
	<li><code>YOURVT75</code> is entered automatically as a command.		<li><code>YOURVT75</code> is entered automatically as a command.

	<li>The <var>YOURTV75</var> subsystem is expected to format a full screen and		<li>The <var>YOURTV75</var> subsystem is expected to format a full screen which prompts the user for a valid userid and password and then
	~~use~~ <var>$Sir_Login</var> to log the user in.		uses <var>$Sir_Login</var> to log the user in.

	<li>If command level is reached without a successful <var>$Sir_Login</var>		<li>If command level is reached without a successful <var>$Sir_Login</var>