> Is there some actual technical reason why TSO cannot be made to allow one > user ID to log in multiple times to TSO within a single LPAR? Who says TSO does not allow one userid with several logins within a single apar?
JOBNAME StepName ProcStep JobID Owner C Pos DP Real Paging SIO CPU% ASID ASIDX BARBARA CEAPROCF TSU07563 BARBARA OUT FF 2105 0.00 0.00 0.00 96 0060 BARBARA CEAPROCF TSU07566 BARBARA OUT FF 2110 0.00 0.00 0.00 68 0044 BARBARA CEAPROCF TSU07567 BARBARA OUT FF 2110 0.00 0.00 0.00 30 001E BARBARA CEAPROCF TSU07562 BARBARA OUT FF 2109 0.00 0.00 0.00 75 004B BARBARA CEAPROCF TSU07570 BARBARA OUT FF 2115 0.00 0.00 0.00 92 005C BARBARA CEAPROCF TSU07565 BARBARA OUT FF 2109 0.00 0.00 0.00 93 005D BARBARA CEAPROCF TSU07564 BARBARA OUT FF 2108 0.00 0.00 0.00 91 005B BARBARA CEAPROCF TSU07568 BARBARA OUT FF 2109 0.00 0.00 0.00 78 004E BARBARA ISPFPROC SC0TCP31 TSU07560 BARBARA IN EE 2349 0.00 0.96 6.74 89 0059 BARBARA CEAPROCF TSU07561 BARBARA OUT FF 2062 0.00 0.00 0.00 90 005A BARBARA CEAPROCF TSU07569 BARBARA OUT FF 2115 0.00 0.00 0.00 94 005E We only have one lpar (one system), and I am now logged in 11 times with the same TSO userid. We have made sure that each of those TSO sessions has their own ISPF profile data set. And each session can have up to 8 split screens. And be aware that TSO send won't really work. I don't remember if the message is sent everywhere or only to the address space with the lowest asid number. Each of those asids can be terminated externally by using the asid qualifier if it doesn't terminate all by itself. Just canceling u=barbara will get you "who? which one?" If you go into SDSF and name all of those SDSF consoles the default (the TSO userid), then command responses won't necessarily come back to the console that issued the command. Barbara Nitz ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
