I've added a console statement to the parmlib member:
CONSOLE
DEVNUM(SUBSYSTEM)
AUTH(ALL)
NAME(ZXPFS0W1)
I'm trying to add support for an EMCS console to my code. I want to
be able to execute a couple of operator commands, then check the
results. I'm running an ADCD 3.1 system. Single zOS image.
The 1st time after an IPL the MCSOPER call to activate the console
will get a return code 4, reason code 0. Manual states:
Meaning: Environmental error. For REQUEST=ACTIVATE, an EMCS console
with this name is already active on this system or on a system within
the same GRS NONE or RING environments.
Does anyone know why the call is getting this return code?
1st time this happened, I executed a 'display console,a' to display
active consoles, and it was not in the list returned.
But, it was in the list when I did a 'display console,n' to display
inactive consoles.
What I have done to get around this to test the console code was to
delete its entry using the 'setcon delete' :
SETCON DELETE,CN=ZXPFS0W1
CNZ4300I SUBSYSTEM CONSOLE ZXPFS0W1 HAS BEEN REMOVED
After deleting the console entry using the operator command, I can
run the code as many times as I want, and the MCSOPER always works,
using ZXPS0W1 a the name.
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.
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.
If there is someone who can enlighten me on the correct way to set
this up, I would appreciate it.
Regards,
-- Dave Day
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
