In case this is causing confusion to some readers, the Session Manager that includes the SMCOPY command, which was mentioned earlier, has nothing to do with multiple sessions. There is a chapter about it in the TSO/E User's Guide.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IKJ4C260/4.2.1 Bill On Wed, 6 Nov 2013 11:36:19 -0800, Jon Perryman wrote: >I don't know if IBM still maintains session manager. When they acquired >Candle, they had CL/Supersession which provides different but similar >functionality. They need CL/Supersession for OMEGAMON so if they were to get >rid of one, it would probably be session manager. Session manager is the equivalent of running multiple TN3270 session. Think of it �Nothing more so it doesn't have anything to do with single user signon for TSO.� As far as TSO COPY, it is so heavily used that IBM could not withdraw it. I don't know if it's still priced. Jon Perryman. >________________________________ > From: Paul Gilmartin >To: [email protected] >Sent: Wednesday, November 6, 2013 9:44 AM >Subject: Re: Aging Sysprogs = Aging Farmers > > >On Wed, 6 Nov 2013 08:55:05 -0800, Jon Perryman wrote: > >>Session manager allowed multiple terminal sessions from a single terminal. >> >Past tense? Is it gone? STTL? > >Multiple sessions with the same user ID? On the same LPAR? I know >there are CBTTape type hacks for this, but it hasn't become mainstream. >Is ENQ on the ISPF profiles a further obstacle? > >Do multiple sessions run in the same address space? How do they deal >with DDNAME conflicts? Is every utility invoked with an alternate DDNAME >list? > >And concerning COPY, wasn't it mentioned earlier here that it belonged >to a separately priced feature, perhaps now withdrawn? > >-- gil > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
