Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Brian Westerman
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 th

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread kekronbekron
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>

Re: DLL linkage vs static linkage

2021-08-10 Thread Eric D Rossman
Just to be clear, there is no case to ever include SYS1.SCSFMOD0. That dataset should never be in any since HCR77D0 (z/OS V2R4) because it is not a programming interface. Everything that was in there that was intended as a programming interface is now in SYS1.SCSFSTUB. ASM programs should be us

Re: Software drag racing

2021-08-10 Thread Andrew Rowley
I wrote up the results of trying Dave Plummer's software drag racing on z/OS. The focus is mainly Java vs C++ because I do SMF processing in Java, and people like to tell me Java is too slow. Results are here: https://www.blackhillsoftware.com/news/2021/08/10/java-vs-c-drag-racing-on-z-os/ T

Re: DLL linkage vs static linkage

2021-08-10 Thread Frank Swarbrick
Hi Barry, Interesting. But I can't quite get it to work. What's bizarre is that the DLL linkage seems to get resolved: IMPORT/EXPORT TYPESYMBOL DLL DDNAME SEQ MEMBER - -- --- --

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Allan Staller
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 syst

Re: DLL linkage vs static linkage

2021-08-10 Thread Barry Lichtenstein
This complaint has come up every so often. There is something already in the binder that works. However it requires a control statements one-for-one with each IMPORT statement. The control statement is a restricted no-call LIBRARY statement, it looks simply like this (with the parentheses):

Re: COBOL V5+

2021-08-10 Thread Larry Slaten
Thank you for your quick response Mr. Ross. The answer to your question is that we no longer have DEBUG TOOL, and the replacement vendor doesn't support the DWARF protocol/format.  I chose NOTEST(DWARF) because the documentation indicated that LE CEEDUMP was able to access/process the addition

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Jeremy Nicoll
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 WT

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread David Spiegel
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

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Seymour J Metz
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 Biancu

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Massimo Biancucci
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

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Seymour J Metz
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, Augu

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Seymour J Metz
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 Ste

Re: Communication between two computer systems (LPARS or physical)

2021-08-10 Thread esst...@juno.com
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 gl

Communication between two computer systems (LPARS or physical)

2021-08-10 Thread Steff Gladstone
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 n