Thanks, John.
On 6/19/2025 4:32 PM, Jon Perryman wrote:
On Thu, 19 Jun 2025 14:08:55 -0500, Dave Day <[email protected]>
wrote:
CONSOLE
DEVNUM(SUBSYSTEM)
MCSOPER is for EMCS consoles are dynamic (not SUBSYSTEM consoles). You are
getting the conflict because they are 2 different types.
The manuals I've read indicated I should put the definition for the
console in the parmlib member, but there's something going on here that
I do not grasp.
I'm surprised it says "should" since no one does it. It would make CONSOLxx a nightmare
to maintain considering automation products, SDSF, TSO CONSOLE command and ... use EMCS consoles.
The idea is "dynamic", not static.
I want to give users the ability to control the console, and the
commands it can issue using RACF profiles. I've got an OPERCMDS profile
set for MVS.MCSOPER.ZXPFS0W1 with read authority for the id the started
task runs with.
Despite EMCS being dynamic, RACF profiles still apply to these consoles.
The doc for setting up the TSO CONSOLE command should point you to the various
RACF profiles. Create the rules you want and be as granular as you want even
with console commands. I think you can even limit it by arguments. As for the
console name, is a reason why?
You mentioned "users" but don't mention any details but it sounds like you will
have an STC that is accessed by multiple users. May I suggest you use TSO CONSOLE in REXX
exec's that each user runs from their TSO session. REXX will greatly simplify message
handling and parsing. Each user will get their own unique console. If you need an STC,
then run batch TSO.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
