Re: Communication between two computer systems (LPARS or physical)
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, robhbrid...@gmail.com, 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 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Was wondering when the B-word would be dropped... for me to then ask... is this a case for something like Raft consesus protocol? I'm talking only theory-wise. As far as solving the OP's problem, it may be a bit of a tangential thought. - KB ‐‐‐ Original Message ‐‐‐ On Thursday, August 12th, 2021 at 2:48 PM, Timothy Sipples wrote: > Lennie Dymoke-Bradshaw wrote: > > > 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 don't think that's a given. As long as the participants in this > > synchronization network can establish and maintain trust with one another, > > that should be fine even if none of them are particularly trusted by > > anything else outside their circle. Metaphorically it's like a secret > > society. DLTs (Blockchain networks) generally operate this way, for > > example. (I'm not necessarily suggesting a DLT-based approach in this > > case.) > > Have we learned yet whether or not it's acceptable if this synchronization > > network provides different answers if you ask different nodes the same > > question at exactly the same time? For example, if you have a 3 node > > network then hypothetically you could ask a question and if a majority of > > the nodes (2 out of 3) agree on a common answer, that's a valid answer. As > > another example, if the "truth" is 5 minutes out of date, that's OK, and a > > node will take some action if it isn't able to check in with its peers and > > maintain truth-consensus within 5 minute intervals. > > There are a LOT of possible options. > > Timothy Sipples > > I.T. Architect Executive > > Digital Asset & Other Industry Solutions > > IBM Z & LinuxONE > > E-Mail: sipp...@sg.ibm.com > > --- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Thank you all for your informative answers! Steff On Thu, 12 Aug 2021 at 12:19, Timothy Sipples wrote: > Lennie Dymoke-Bradshaw wrote: > >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 don't think that's a given. As long as the participants in this > synchronization network can establish and maintain trust with one another, > that should be fine even if none of them are particularly trusted by > anything else outside their circle. Metaphorically it's like a secret > society. DLTs (Blockchain networks) generally operate this way, for > example. (I'm not necessarily suggesting a DLT-based approach in this > case.) > > Have we learned yet whether or not it's acceptable if this synchronization > network provides different answers if you ask different nodes the same > question at exactly the same time? For example, if you have a 3 node > network then hypothetically you could ask a question and if a majority of > the nodes (2 out of 3) agree on a common answer, that's a valid answer. As > another example, if the "truth" is 5 minutes out of date, that's OK, and a > node will take some action if it isn't able to check in with its peers and > maintain truth-consensus within 5 minute intervals. > > There are a LOT of possible options. > > - - - - - - - - - - > Timothy Sipples > I.T. Architect Executive > Digital Asset & Other Industry Solutions > IBM Z & LinuxONE > - - - - - - - - - - > E-Mail: sipp...@sg.ibm.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Lennie Dymoke-Bradshaw wrote: >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 don't think that's a given. As long as the participants in this synchronization network can establish and maintain trust with one another, that should be fine even if none of them are particularly trusted by anything else outside their circle. Metaphorically it's like a secret society. DLTs (Blockchain networks) generally operate this way, for example. (I'm not necessarily suggesting a DLT-based approach in this case.) Have we learned yet whether or not it's acceptable if this synchronization network provides different answers if you ask different nodes the same question at exactly the same time? For example, if you have a 3 node network then hypothetically you could ask a question and if a majority of the nodes (2 out of 3) agree on a common answer, that's a valid answer. As another example, if the "truth" is 5 minutes out of date, that's OK, and a node will take some action if it isn't able to check in with its peers and maintain truth-consensus within 5 minute intervals. There are a LOT of possible options. - - - - - - - - - - Timothy Sipples I.T. Architect Executive Digital Asset & Other Industry Solutions IBM Z & LinuxONE - - - - - - - - - - E-Mail: sipp...@sg.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
CA-ENF has supports inter-LPAR (and other platforms) communication over a variety of mechanisms. > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Brian Westerman > Sent: Wednesday, August 11, 2021 9:34 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Communication between two computer systems (LPARS or > physical) > > That's right, I think CA's ENF product (now Broadcom) does that. I think it > uses TCP/ip but maybe it's VTAM or something else. > > Brian > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
That's right, I think CA's ENF product (now Broadcom) does that. I think it uses TCP/ip but maybe it's VTAM or something else. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
> 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 <032fff1be9b4-dmarc-requ...@listserv.ua.edu> 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 IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Steff Gladstone > > Sent: 10 August 2021 13:06 > > To: IBM-MAIN@LISTSERV.UA.EDU > > 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 > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > --- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
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 On Behalf Of Steff Gladstone Sent: 10 August 2021 13:06 To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: 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. But this is problematic since the required SVC (34) requires that the program be authorized. 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" (i.e., system level). And I surely hope that the "global data" is not in user key (another thing requiring authorization). broadcast to the other computer systems in the installation (LPARs or physical computers). XCF will not send beyond the bounds of the sysplex. Nor would a routed command. So covering "other computer systems in the installation" can be very difficult if they are not part of a single sysplex. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
If this was my code, I would be using one of : (o) IXCNOTE (o) IXCSETUS with XCF groups (o) IXCSEND/RECV All the above are really easy to code and built for exactly this sort of thing. If you absolutely must use problem state code, then a couple of ideas : (o) SYSTEMS scope ISGENQ with USERDATA with servers in periodic wakeup to issue ISGQUERY to check the contents of the USERDATA to see if changed. (o) TCP/IP sockets (so many error codes to consider and recover from...) Rob Scott -Original Message- From: IBM Mainframe Discussion List On Behalf Of Allan Staller Sent: 10 August 2021 20:22 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Communication between two computer systems (LPARS or physical) EXTERNAL EMAIL Classification: Confidential XCF (either via CF or CTC)). RYO method for communication -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steff Gladstone Sent: Tuesday, August 10, 2021 7:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Communication between two computer systems (LPARS or physical) [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
I hate to make this more complicated, but if (all of) the LPARs are not connected via a plex or CTC's, then you can't use some of these suggestions. The reason DASD was used originally with a lot of old time software (think Checkpoint datasets) was because it was available to ALL of the LPARs that could see it. Then I believe things moved on to a VTAM based application that could send data to other VTAM applications, which you could do with TCP/IP now. The point I am trying to make is that you need some "thing" that is available to all of the LPARs to be able to keep them all updated. The mechanism you use to keep that "thing" available and update it without tying up the other LPARs unnecessarily. There are likely things on the CBT tape that would come in useful in this effort. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Perhaps SMC-D or SMC-R. Probably don't need to run authorized for this. However, you'll need daemon tasks on each system, I suppose to send/receive. - KB ‐‐‐ Original Message ‐‐‐ On Wednesday, August 11th, 2021 at 12:52 AM, Allan Staller <0387911dea17-dmarc-requ...@listserv.ua.edu> wrote: > Classification: Confidential > > XCF (either via CF or CTC)). > > RYO method for communication > > -Original Message- > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of > Steff Gladstone > > Sent: Tuesday, August 10, 2021 7:06 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Communication between two computer systems (LPARS or physical) > > [CAUTION: This Email is from outside the Organization. Unless you trust the > sender, Don’t click links or open attachments as it may be a Phishing email, > which can steal your Information and compromise your Computer.] > > 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 > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ::DISCLAIMER:: > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses > in transmission. The e mail and its contents (with or without referred > errors) shall therefore not attach any liability on the originator or HCL or > its affiliates. Views or opinions, if any, presented in this email are solely > those of the author and may not necessarily reflect the views or opinions of > HCL or its affiliates. Any form of reproduction, dissemination, copying, > disclosure, modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL is > strictly prohibited. If you have received this email in error please delete > it and notify the sender immediately. Before opening any email and/or > attachments, please check them for viruses and other defects. > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Classification: Confidential XCF (either via CF or CTC)). RYO method for communication -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steff Gladstone Sent: Tuesday, August 10, 2021 7:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Communication between two computer systems (LPARS or physical) [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
On Tue, 10 Aug 2021, at 14:30, David Spiegel wrote: > Hi Steff, > Have the application which updates the data put out a WTO which triggers > your Automation to schedule Tasks on all other LPARs (e.g. RO *ALL, S > UPDATE). I'd just add: make sure the automation process validates who issued the WTO and also doesn't just take some literal text from the WTO and have that executed as the actual command... since a mechanism like that is likely to get misused. -- Jeremy Nicoll - my opinions are my own. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Hi Steff, Have the application which updates the data put out a WTO which triggers your Automation to schedule Tasks on all other LPARs (e.g. RO *ALL, S UPDATE). Regards, David On 2021-08-10 08:06, Steff Gladstone wrote: 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN . -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
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 [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Massimo Biancucci [mad4...@gmail.com] Sent: Tuesday, August 10, 2021 8:47 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 < steff.gladst...@gmail.com> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 < steff.gladst...@gmail.com> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
Doesn't that require authorization, which the OP wishes to avoid? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of esst...@juno.com [esst...@juno.com] Sent: Tuesday, August 10, 2021 8:38 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Communication between two computer systems (LPARS or physical) You may want to consider using some of the SYSPLEX Services (log streams/structures) -- Original Message -- From: Steff Gladstone To: IBM-MAIN@LISTSERV.UA.EDU Subject: Communication between two computer systems (LPARS or physical) Date: Tue, 10 Aug 2021 15:06:22 +0300 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
You could have a VTAM application on each system; I can't think of a simpler way that doesn't require authorization. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Steff Gladstone [steff.gladst...@gmail.com] Sent: Tuesday, August 10, 2021 8:06 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Communication between two computer systems (LPARS or physical)
You may want to consider using some of the SYSPLEX Services (log streams/structures) -- Original Message -- From: Steff Gladstone To: IBM-MAIN@LISTSERV.UA.EDU Subject: Communication between two computer systems (LPARS or physical) Date: Tue, 10 Aug 2021 15:06:22 +0300 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
