Enables a single userid to be used to sign on to more than one terminal at once, with each terminal sharing the same menu and session list.
This common end-user parameter is applicable to these control statements: SYSTEM (see SYSTEM statement), PROFILE (see PROFILE statement), USER (see USER statement), and TERMINAL (see TERMINAL statement).
When a SHAREDISC user signs on and there is no other terminal signed on (or disconnected) with the same userid then this becomes the primary user. Subsequent terminals signing on with the same userid become secondary users. All sessions started by primary or secondary users are primary user sessions. If a secondary user takes over a session from a primary user, the primary user will be disconnected. If a primary user takes over a session from a secondary user, the secondary user will be logged off.
For example, if USERA, with SHAREDISC set to YES, signs on to terminal TERM1 and then signs on to terminal TERM2, both terminals will display the same menu and session list. If a session is started on TERM1 then the session will be displayed as active on both terminals. In this case the owner of the session is TERM1, and TERM1 will remain the owner even if the user on TERM1 escapes and starts another session.
If, however, the user on TERM2 selects a session owned by TERM1, then TERM1 is disconnected. Any data that has been typed but not entered on the original terminal will be lost. Depending on the setting of the LOGDISC parameter (see LOGDISC) for the initial terminal (TERM1), either the IBM Session Manager sign-on screen will be displayed or the terminal will be disconnected.
If a LOGOFF command is entered at any terminal signed on to by a SHAREDISC user then all other terminals signed on with that userid will also be signed off. If, however, a DISCONNECT command is entered at any terminal signed on to by a SHAREDISC user then only that terminal is disconnected.
Only one of SHARE, SHAREDISC and SHARESESS should be set to Yes at any one time.