VTLAPSY parameter: Difference between revisions
Jump to navigation
Jump to search
m (Clarify actions performed by YOURVT75 subsystem.) |
m (misc cleanup) |
||
| 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 | <li>The <var>[[$Sir_Login]]</var> function is enabled. </li> | ||
<li> | <li><code>YOURVT75</code> is entered automatically as a command. </li> | ||
<li><code> | <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> | ||
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. < | <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 | 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 | |||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 18:21, 11 May 2015
Login APSY for VT75 terminals
Summary
- Default value
- null string
- Parameter type
- System
- Where set
- User 0 CCAIN parameters
- 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 via the NEWSESCMD parameter on the JANUS DEFINE command.
When an IODEV=7 terminal connects to Model 204, one of four connection states is possible:
- Terminal connection contains no user data (the typical case).
- Terminal connection is the result of a VTAM transfer of control from a different Model 204 online. A zap for SirMods Version 7.7 allows VTAM transfer of control even when RACF is used.
- Terminal connection request passed user data, and the X'0040' bit of TERMOPT is not set. In this case the user data will be processed as a command at connect time.
- 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 will be 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 userid and password, then it uses $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, a MSIR.0722 non-terminal message is issued, and the terminal is disconnected.
- If command level is reached after a successful $Sir_Login, then any AUTOSYS subsystem for the thread will be processed.
- Any environmental error in $Sir_Login will result in request cancellation.
Note: A 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 apsy that can be used with the VTLAPSY parameter is provided 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.