The Question is:
with UCX (V4) Telnet-terminals where treated 'local',
with 'TCP/IP-Services (V5) for VMS' Telnet-terminals are treated 'remote'.
How can a (V5-) telnet-terminal be set up to be a local session instead of a
remote session (which our customer disallows)? Is there any system parameter,
telnet-service-flag, TCPIP$*-logical or something else?
The Answer is :
The OpenVMS Wizard will assume this is a reference to the authorization
flags for local and remote access, or similar.
The OpenVMS Wizard is not aware of such a switch, and would tend to have
expected these sessions be considered remote sessions -- telnet sessions,
like DECnet SET HOST sessions, are remote sessions.
Without details of the problem nor details around why remote access
differs from local access nor whether or not changes to the settings
can be made, the OpenVMS Wizard can only suggest use of filtering of
logins via code in SYLOGIN or potentially site-specific access control
via LGI callouts.
The OpenVMS Wizard would encourage an upgrade to TCP/IP Services V5.0A.