VTLAPSY parameter: Difference between revisions
mNo edit summary |
m minor formatting |
||
| (19 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:VTLAPSY parameter subtitle}} | |||
__NOTOC__ | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 6: | Line 8: | ||
<dd>System | <dd>System | ||
<dt>Where set | <dt>Where set | ||
<dd>User 0 CCAIN parameters | <dd>User 0 CCAIN parameters and resettable by system managers | ||
<dt>Related products | <dt>Related products | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd>[[Sirius Mods]] 7.9 | <dd><var class="product">[[Sirius Mods]]</var> 7.9 | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
VTLAPSY 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 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 | |||
When an IODEV=7 terminal connects to Model 204, one of four connection | <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> | ||
states is possible: | |||
===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> | <li>The terminal connection contains no user data (the typical case). </li> | ||
control from a different Model 204 | |||
<li>The terminal connection is the result of a VTAM transfer of | |||
control from a different <var class="product">Model 204</var> Online. VTAM transfer of control is allowed even when RACF is used. </li> | |||
<li> | |||
<li> | <li>The terminal connection request passed user data, and the X'0040' | ||
bit is | 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> | ||
<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 VTLAPSY is | When an <code>IODEV=7</code> terminal connects with no user data and <var>VTLAPSY</var> is | ||
set to a non-blank value, 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 | <li>The <var>[[$Sir_Login]]</var> function is enabled. </li> | ||
<li> | <li><code>YOURVT75</code> is entered automatically as a command. </li> | ||
<li>The | <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> | |||
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 message is issued, and the terminal is disconnected. </li> | |||
<li>If command level is reached without a successful $Sir_Login | |||
call, or if the VTLAPSY subsystem attempts an APSY transfer | <li>If command level is reached after a successful <var>$Sir_Login</var>, | ||
without a successful $Sir_Login call, | any <var>[[AUTOSYS parameter|AUTOSYS]]</var> subsystem for the thread is processed. </li> | ||
message is issued and the terminal is disconnected. | |||
<li>Any environmental error in <var>$Sir_Login</var> results in request cancellation. | |||
<li>If command level is reached after a successful $Sir_Login, | <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> | ||
<li>Any environmental error in $Sir_Login | |||
cancellation. Note | |||
a user in or out. | |||
</ol> | </ol> | ||
==Sample APSY== | |||
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: | |||
<p class="code"> | |||
/\ * * | |||
* //\\ * W E L C O M E T O | |||
// \\ M O D E L 2 0 4 | |||
* /\\__//\ | |||
// - \\ * * | |||
* // ROCKET \\ | |||
* // SOFTWARE \\ VV VV 77777777 5555555 | |||
// - \\ * VV VV 77 55 | |||
// | - | \\ VV VV 77 55 | |||
// / | | \ \\ VV VV 77 5555555 | |||
/_/_/__|__________|__\_\_\ VV VV 77 55 | |||
/__/_/===__===__===__===\_\__\ VV VV 77 55 | |||
/___\/___\/___\/___\ VVV 77 555555 | |||
;;; ;;; ;;; ;;; | |||
Processing login from terminal S26T0019 | |||
User ID: | |||
Password: New Password: | |||
Command: | |||
</p> | |||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 23:52, 6 December 2017
Login APSY for VT75 terminals
Summary
- Default value
- null string
- Parameter type
- System
- Where set
- User 0 CCAIN parameters and resettable by system managers
- Related products
- All
- Introduced
- Sirius Mods 7.9
Description
VTLAPSY 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 IODEV 7 terminals (3270-type). For TN3270 connections, the same functionality is provided by the NEWSESCMD parameter on the JANUS DEFINE command.
Caution: If you set VTLAPSY to a non-existent or non-functional APSY, IODEV=7 threads are prevented from logging in.
Connection states and processing
When an IODEV=7 terminal connects to Model 204, one of four connection states is possible:
- The terminal connection contains no user data (the typical case).
- The terminal connection is the result of a VTAM transfer of control from a different Model 204 Online. VTAM transfer of control is allowed even when RACF is used.
- The terminal connection request passed user data, and the X'0040' bit of TERMOPT is not set. In this case, the user data is processed as a command at connect time.
- The terminal connection contains user data, and
TERMOPT=X'0040'. In this case, the user data will be prefixed with the string "LOGON " and the result is processed as a command.
When an IODEV=7 terminal connects with no user data and VTLAPSY is
set to a non-blank value (for example, YOURVT75), the following processing is performed:
- The user is temporarily "logged in" with a USERID of
YOURVT75(the subsystem name), ACCOUNT ofNO ACCOUNT, and with X'00' privileges. - The $Sir_Login function is enabled.
YOURVT75is entered automatically as a command.- The
YOURTV75subsystem 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 $Sir_Login, to log the user in. - If command level is reached without a successful $Sir_Login call, or if the VTLAPSY subsystem attempts an APSY transfer without a successful $Sir_Login call, an MSIR.0722 non-terminal message is issued, and the terminal is disconnected.
- If command level is reached after a successful $Sir_Login, any AUTOSYS subsystem for the thread is processed.
- Any environmental error in $Sir_Login results in request cancellation.
Note: The VTLAPSY subsystem must be configured to not log a user in or out (
Nsettings forLog user into M204and forLog user out of M204in the "APSY SUBSYSMGMT Operational Parameters" screen).
Sample APSY
A sample subsystem that can be used with the VTLAPSY parameter is provided in the SIRIUS file. Programs are VTLN.LOGIN and VTLN.ERROR, and the comments in VTLN.LOGIN 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:
/\ * * * //\\ * W E L C O M E T O // \\ M O D E L 2 0 4 * /\\__//\ // - \\ * * * // ROCKET \\ * // SOFTWARE \\ VV VV 77777777 5555555 // - \\ * VV VV 77 55 // | - | \\ VV VV 77 55 // / | | \ \\ VV VV 77 5555555 /_/_/__|__________|__\_\_\ VV VV 77 55 /__/_/===__===__===__===\_\__\ VV VV 77 55 /___\/___\/___\/___\ VVV 77 555555 ;;; ;;; ;;; ;;; Processing login from terminal S26T0019 User ID: Password: New Password: Command: