> However, this requires that all systems are in the same sysplex. Or... that the automation product can communicate across sysplexes through its own connector. I know of at least one product that has a few different options to communicate with other instances even outside a sysplex. Have managed one such environment.
- KB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, August 11th, 2021 at 10:20 PM, Lennie Dymoke-Bradshaw <[email protected]> wrote: > Steff, > > Looking through the various answers here, I note that someone has mentioned > the need for some kind of security, so that others cannot trigger actions > they are not supposed to. > > I think those security issues conflict with your requirement to run > synchronisation without any authorisation. > > I think the best compromise is to use your existing automation package, as > long as this can perform the necessary security checks. This will already be > running APF authorised, so if security checks can be designed into the rules > you use it will provide the simplest solution. > > If your automation package can determine which id issued a WTO and then > perform the necessary security checks on it, then this can used as the > trigger mechanism to perform the actions. However, this requires that all > systems are in the same sysplex. > > Also, Peter Relson said, > > " FWIW, the program already had to be authorized in order to obtain "global > data" or to use a "name-token that is available to all the address spaces" > > This confused me slightly, as I have used global name-tokens which can be > universally read. I think that the global name-token can be READ by any > address space as long as a fetch-protected key is NOT used, but the address > space used to SET the token would definitely need authorisation. > > Lennie Dymoke-Bradshaw > > https://rsclweb.com > > ‘Dance like no one is watching. Encrypt like everyone is.’ > > -----Original Message----- > > From: IBM Mainframe Discussion List [email protected] On Behalf Of > Steff Gladstone > > Sent: 10 August 2021 13:06 > > To: [email protected] > > Subject: Communication between two computer systems (LPARS or physical) > > 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
