> On Jun 29, 2017, at 12:07 PM, Paul Gilmartin > <[email protected]> wrote: > > On Thu, 29 Jun 2017 11:44:18 -0500, Elardus Engelbrecht wrote: >> >> Or what are you using to determine that an id is 'inactive'? >> > Are entries in SYS1.BRODCAST timestamped so they could be aged out? > > What was the original design rationale for using a common SYS!.BRODCAST > rather than individual &PREFIX.BRODCASTs? Allocation/OPEN/CLOSE > overhead? ENQ contention? Space/VTOC constraint? Other? I can’t give a definitive answer but I can make a good guess on the common Broadcast. The original developers I am guessing did not want potentially 1000’s of tiny datasets laying around. They opted for 1 dataset. Broadcast was in (still in) mstrjcl so there was no need to do multiple opens/closes. As for contention it wasn’t all that bad as *I THINK* it was only enqued at update time. It was/is a BDAM dataset.
Ed > > UNIX facilities could be your friend here, even as UNIX batch jobs simply > append their logs to the user's mbox. > > -- gil > > ---------------------------------------------------------------------- > 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
