LPAR-LPAR synchronization requires some sort of external mechanism, e.g., CF; 
there's no shared memory. But I probably should add some text on SysPlex.

Is there an online copy of the old CF article? It was in either the IBM Systems 
Journal or the IBM Journal of Research and Development, back when the CF was 
first announced.

-- 
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר




________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Stefan Skoglund <[email protected]>
Sent: Friday, August 14, 2026 8:43 AM
To: [email protected] <[email protected]>
Subject: Re: Wikipedia reliable sources for serialization?


External Message: Use Caution


tor 2026-08-13 klockan 18:01 +0000 skrev Seymour J Metz:
> What are good sources to cite on wikipedia for latches and locks? I'm
> currently citing MVT Supervisor PLM for older serialization and z/OS
> Authorized Services for for locks.
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> עַם יִשְׂרָאֵל חַי
Solaris: if i'm not wrong, the kernel uses spin-locks (bus snooping
instructions) to allocate turnstiles.

Can instructions like that be used in a SYSPLEX ?

I think you should take up the memory usage problem ie how to limit
synch objects and why.

----------------------------------------------------------------------
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