It's less overhead to have a permanent STC on each LPAR and use a MODIFY 
command for change notification.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Massimo Biancucci [[email protected]]
Sent: Tuesday, August 10, 2021 8:47 AM
To: [email protected]
Subject: Re: Communication between two computer systems (LPARS or physical)

Steff,

it's not so simple to understand the scenario and the goal you need to
achieve in terms of "response time and certainness" of the result.

There're different ways, Sysplex Services (other guys already mentioned) or
developing a STC that runs on every LPAR listening to IP stack.
The problem is (and always will), how to be sure all the LPARS got,
understood and refreshed the needed infos.

If you want to simplify sending commands starting STCs on every LPAR, you
could use an operator interface (IBM, Broadcoam, BMC, your own).
You can issue a WTO and let the automated-operator to send the needed
command to all the LPARs (RO *ALL). This should avoid the APF auth at your
programming level.

Regards.
Max

Il giorno mar 10 ago 2021 alle ore 14:06 Steff Gladstone <
[email protected]> ha scritto:

> We have global data pointed to by a name-token that is available to all the
> address spaces in each computer system.  We want to make sure that any
> updates to the data in one system are broadcast to the other computer
> systems in the installation (LPARs or physical computers).  Or at the very
> least notify the other systems that their data is not up-to-date. What
> would be the simplest and cheapest way to send some kind of signal from one
> system to the other without requiring I/O to shared
> DASD?
>
> We thought of issuing a console command starting a started task in each of
> the other computer systems  (the JES2 spool is shared by all the systems.)
> .
> But this is problematic since the required SVC (34) requires that the
> program be authorized.   Any other ideas?
>
> Thanks,
> Steff Gladstone
>
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to