Display MAI sessions on both dual screen monitors
Article ID: 118649
Updated On:
Products
SOLVE:Operations Automation
SOLVE:Access Session Management
SOLVE:FTS
SOLVE
Issue/Introduction
For a user with dual monitors, is it possible to use the PFKeys for jumping or opening secondary sessions (F2 and F9) to open the 2nd session on the 2nd monitor rather than making it a logical image on the same monitor?
Environment
Release:
Component: SACCES
Component: SACCES
Resolution
One TN3270 session can only be displayed once; whether PF9 to open an additional window for the same session, or PF2 to toggle between sessions, the same TN3270 session cannot be displayed in multiple locations.
To take advantage of dual screens, changing the users to allow for multi-signon access would allow for that; a multi-user can sign on to MAI twice, creating two separate TN3270 sessions and thus the ability to display the desired applications sessions on both screens at the same time.
For any Netmaster security that utilizes UAMS, this is done by updating the UAMS definition of the individual user to contain
Multiple Signon Authority .... Y (Y/N)
on Page 2 of the UAMS definition.
If using SEC=NMSAFF for full security, either an existing model (affecting all users in that model) is changed from
multipleSignon N
is available for users containing the correct attributes along with
multipleSignon Y
This would make the change for all users of the same profile.
If using an older, custom Assembler exit, the change would be unique to that exit.
To take advantage of dual screens, changing the users to allow for multi-signon access would allow for that; a multi-user can sign on to MAI twice, creating two separate TN3270 sessions and thus the ability to display the desired applications sessions on both screens at the same time.
For any Netmaster security that utilizes UAMS, this is done by updating the UAMS definition of the individual user to contain
Multiple Signon Authority .... Y (Y/N)
on Page 2 of the UAMS definition.
If using SEC=NMSAFF for full security, either an existing model (affecting all users in that model) is changed from
multipleSignon N
is available for users containing the correct attributes along with
multipleSignon Y
This would make the change for all users of the same profile.
If using an older, custom Assembler exit, the change would be unique to that exit.
Additional Information
See the Security Guide for details about the full security exit and the definition and use of structured fields.
Feedback
Yes
No
Powered by
