VTLAPSY parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Clarification and correction for the VTLAPSY parameter)
(Add a link to the NEWSESCMD parameter for TN3270 connections)
Line 17: Line 17:
<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 IODEV=7 terminals (3270-type).  
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

Revision as of 23:29, 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). 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:

  1. The user is temporarily "logged in" with a User ID = YOURVT75 (the subsystem name), account = 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 and use $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, a MSIR.0722 non-terminal message is issued and the terminal is disconnected.
  6. If command level is reached after a successful $Sir_Login, then any AUTOSYS subsystem for the thread will be processed.
  7. 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 (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 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.