A few ideas (and perfectly willing to be slapped down by others more knowledgeable than I):
1) Isn't MQS designed to do just this sort of thing? I gather it works across platforms of many types. 2) If you're in a roll-your-own mood, you could easily enough write a socket client/server in REXX. (I did this once and it was great fun; I can't resist looking for opportunities to do it again.) 3) I once worked on a team for an ACF2 client that had recently acquired a TSS shop; we put together some code that sent every change in either security database to the other. New ID created in TSS: create an equivalent in ACF2 on the other system, and so on. That was just around the turn of the century, but as I recall we used NDM for the transmission, nowadays called Connect:Direct. Figuring out what constitutes the "equivalent" action in two unalike security systems required the combined thought of the whole team; the transmission itself turned out to be pretty simple. --- Bob Bridges, [email protected], cell 336 382-7313 /* Instead of shooting clays on Thanksgiving, you can play great games with your family, like Monopoly: Nothing brings a family together like Monopoly! -from _Top 10 Reasons You Should Just Turn Your Guns Over to the Government TODAY_ (the Babylon Bee) */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steff Gladstone Sent: Tuesday, August 10, 2021 08:06 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? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
