ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Not able to logon by Terminal security violation

book

Article ID: 133085

calendar_today

Updated On:

Products

TPX - Session Management TPX- PACKAGE Vman Session Management for z/OS TPX SESSION MANAGEMENT

Issue/Introduction

How does CA TPX work with MASKING DONE FOR SECURITY: Y ?

Environment

Release : 5.4

Component : CA-TPX for OS/390

Resolution

Any user who has an active session (has MASKING DONE FOR SECURITY: Y) cannot do a transfer of their TPX sessions to another terminal (device) or if the user disconnects from CA TPX, then reconnects to CA TPX on another terminal.

This is a restriction because of "MASKING DONE FOR SECURITY: Y" on application that is active.

Case Example:

User is set up for a timeout when the terminal is idle for a period of time and action is (/F - sign-off keeping session) and one of the active session has " MASKING DONE FOR SECURITY: Y" in the running ACT.

Then the user must reconnect from the same terminal or Replay "Y" to security question which will inactive those sessions with SECURITY MASK.

Another Case Example:

The user does /F (sign-off keeping active sessions), but opens I new TELNET window and access CA TPX. Thus a new terminal that is not the same.

The user is reconnecting and if the user has active session with " MASKING DONE FOR SECURITY: Y" then the user will be queried.

This is most likely configured because there is relationship between physical terminal id and logical terminal id within IMS.