TSO multi-logon on multi-system, restricting to specific users?

I don't think there is a way to do this using "normal" IBM supplied
facilities. At present, we propagate the SYSIKJUA enqueue across our
entire sysplex via the GRSRNL member. When we convert to z/OS 1.12, I am
going to remove this entry from the RNL. This will allows a single TSO
user to logon to every system in the sysplex concurrently. I am setting
up ISPF properly as well. But, if it is easy, I would like to restrict
who can logon to multiple systems concurrently. Note, I must allow
everyone to logon to all systems for support purposes. But I only want
__concurrent__ logons for a few support people. In particular, I want
the programmers to logon only to one system at a time, while Production
Control and Tech Services can logon to all systems concurrently.

Why? Because I have some programmers who "abuse" the system by doing
"batch like" work under TSO. If they could do both normal ISPF work and
"batch like" work by being logged on to multiple systems, they would.
And we simply cannot afford the CPU overhead. We are "CPU poor" and have
a directive to "reduce CPU utilization to reduce software cost" even if
it reduces productivity. Or, best, let them do "batch like" work in
batch so that it can be scheduled by contending for open initiators.

Yes, I know, in general, how to do this by doing a SAF call and possibly
a SYSTEMS level ENQ in the TSO logon exit. We don't want exits in z/OS.
They must be maintained. I could say more as to why this is undesirable,
but won't.

--
John McKown
Maranatha! <><

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • Re: Sudden and repeated launching of cmd.exe and net.exe
    ... earlier suggestion to check the Task Scheduler for a batch ... and changing it to run only at logon. ... I will put the two kill commands on my ... >The Task manager will also display process users names ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: CPU Spikes completely hangs sessions;No logons: need inputs
    ... LPAR(session HUNG due to high CPU. ... If you cannot logon, use the operator reset command to reset your TSO userid ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: IWAM account
    ... Check the user right "logon as batch", and add the iwam account to have ... This appears to be a negotiate failure due to logon as batch. ... - Network ...
    (microsoft.public.inetserver.iis.security)
  • Re: TSO multi-logon on multi-system, restricting to specific users?
    ... user to logon to every system in the sysplex concurrently. ... "batch like" work by being logged on to multiple systems, ... For IBM-MAIN subscribe / signoff / archive access instructions, ... send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO ...
    (bit.listserv.ibm-main)
  • =?ISO-8859-1?Q?Re:_Sysplex_TSO_logon_behaviour?=
    ... Since you are in a Sysplex, you do not need to IPL to change the GRS RNLs. ... We try to logon to a second image. ...
    (bit.listserv.ibm-main)