VTLAPSY parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
(Clarification and correction for the VTLAPSY parameter) |
||
| Line 15: | Line 15: | ||
==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 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 IODEV=7 terminals (3270-type). | provide full-screen login support for IODEV=7 terminals (3270-type). | ||
| Line 22: | Line 22: | ||
states is possible: | states is possible: | ||
<ul> | <ul> | ||
<li>Terminal connection contains no user data (the typical case). | |||
<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 | ||
| Line 35: | Line 37: | ||
string "LOGON " and the result will be processed as a command. | string "LOGON " and the result will be processed as a command. | ||
</ul> | </ul> | ||
When an IODEV=7 terminal connects with no user data and <var>VTLAPSY</var> is | When an IODEV=7 terminal connects with no user data and <var>VTLAPSY</var> is | ||
set to a non-blank value (for example, <code> | set to a non-blank value (for example, <code>YOURVT75</code>), the following processing is performed: | ||
<ol> | <ol> | ||
<li>The user is "logged in" with a User ID | <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. | ||
<code> | |||
<li>The <var>[[$Sir_Login]]</var> function is enabled. | <li>The <var>[[$Sir_Login]]</var> function is enabled. | ||
<li><code> | <li><code>YOURVT75</code> is entered automatically as a command. | ||
<li>The <var> | <li>The <var>YOURTV75</var> subsystem is expected to format a full screen and | ||
use <var>$Sir_Login</var> to log the user in. | use <var>$Sir_Login</var> to log the user in. | ||
Revision as of 23:03, 8 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).
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 User ID =
YOURVT75(the subsystem name), account = NO ACCOUNT and with X'00' privileges. - The $Sir_Login function is enabled.
YOURVT75is entered automatically as a command.- The YOURTV75 subsystem is expected to format a full screen and use $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 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.