You can delete the definition of any extended MCS console, thus
freeing the ID and console name that had been
assigned to the extended MCS console. The system then can reuse that
ID for a newly-defined extended MCS console.
There are two ways in which you can delete a console
definition. The first, and preferred way, is to use the
SETCON
DELETE command. For example, to delete an extended MCS console
named EMCSSY1, issue:
SETCON DELETE,CN=EMCSSY1
For
more information about the
SETCON DELETE command,
see
z/OS MVS System Commands.
The second way to remove a console definition is to
assemble and link the sample source code for program IEARELEC in
SYS1.SAMPLIB. Sample invocation of IEARELEC describes the
sample job for invoking the console service. The programming environment,
and the return and reason codes for invoking the console service are
described in the sample program prologue.
The following restrictions for removing an extended MCS console
apply:
- The extended MCS console must be inactive.
- The console ID of a removed extended MCS console can be reused
once it has been deactivated and removed. It is safe to use the console
ID to process a command response, but you should avoid saving the
console ID for later processing. Therefore, you should use the console
name to direct messages to specific consoles. If the console ID is
used, messages may end up going to unintended consoles.
- Do not remove or change the definition of the following
system-used extended MCS consoles:
- The ROUTE command console, named *ROUTExx, where
xx is the value of &SYSCLONE
- The OPERLOG console, named *OPLOGxx, where xx is
the value of &SYSCLONE
- The SYSLOG console, named *SYSLGxx, where xx is the value of &SYSCLONE
- The DIDOCS EMCS console, named *DICNSxx, where xx is the value
of &SYSCLONE
- The System REXX consoles, named *AXTnnxx and *AXRnnxx,
where nn is the worker address space number and xx is the value of &SYSCLONE
- The IOS EMCS console, named SYSIOSRS
- The JES3 DLOG console, named JES3DLOG