VTLAPSY parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (minor formatting)
 
(3 intermediate revisions by 3 users not shown)
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-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
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&nbsp;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&nbsp;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 45: 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>
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 parameter|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&nbsp;204 Online:
<p class="code">
<p class="code">
                   /\          *                                  *       
                   /\          *                                  *       

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:

  1. The user is temporarily "logged in" with a USERID of YOURVT75 (the subsystem name), ACCOUNT of NO ACCOUNT, and with X'00' privileges.
  2. The $Sir_Login function is enabled.
  3. YOURVT75 is entered automatically as a command.
  4. The YOURTV75 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 $Sir_Login, to log the user in.
  5. 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.
  6. If command level is reached after a successful $Sir_Login, any AUTOSYS subsystem for the thread is processed.
  7. 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 (N settings for Log user into M204 and for Log user out of M204 in 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: