Console name must be unique within a sysplex when CONSOLE ACTIVATE is issued.
That means no collision on this or any other system. I've found that using the
Rexx name is usually sufficient, but to guard against the same Rexx being run
concurrently on another system, some part of the name can be modified with a
system-unique identifier such as
"CONSOLE ACTIVATE NAME(ABCDEF"MVSVAR("SYMDEF","SYSCLONE")")"
If you still get an occasional conflict, you'll have to get more creative.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of ITschak Mugzach
Sent: Tuesday, December 19, 2017 1:40 AM
To: [email protected]
Subject: (External):Re: Rexx console question
You can generate a dynamic console name (e.g. "CONSOL NAME(CONS"convar")"),
just make sure that the user running the job is authorized to the console names
generated dynamically (job number, time, etc.).
ITschak
On Tue, Dec 19, 2017 at 11:31 AM, Tony Thigpen <[email protected]> wrote:
> I am using CONSOLE ACTIVATE in batch jobs to issue messages to the
> operator.
>
> Most of the time, it works flawlessly, but if two jobs are running at
> the same time, one of the jobs receives an error on the ACTIVATE ane
> the message is never issued.
>
> I am using running the rexx using IKJEFT01. Both jobs are under the
> same userid.
>
> /* JOBZSMSG job processing response REXX */ trace off "CONSOLE
> ACTIVATE"
> pull info
> ii = words(info)
> who = word(info,ii)
> cmd = "$D M,D=OSCAR."who",'"info"'"
> "CONSOLE SYSCMD("Cmd")"
> say cmd
> "CONSOLE DEACTIVATE"
> exit 0
>
> Anybody have any suggestions?
>
> --
> Tony Thigpen
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
