<snip> A few IBM products run with NODSI intentionally. Looking the I&T, looks like PSF, VLF, DLF, FFST, RMF, JES2, JES3, *MASTER*, SMF, CAS </snip> To be clear and picky, most of these are components of the z/OS base, not products. There's a big difference between a product needing NODSI and the operating system itself need it.
<snip> If one job connects to several members with DESERV, is it guaranteed a consistent snapshot of those members (to which changes might need to be synchronized) while another job is updating those members? </snip> I think the answer is "yes". That's exactly the intent of a "connection". The "connected copy" remains available, even if the member is subsequently updated. Once a connection is formed, a subsequent fetch using that connection will get the copy associated with the connection. It feels similar to the PDS compression case: as we know, until "compress" is done on a PDS, the old data still exists, it's just that the directory no longer points to the old data once a member is updated. For a PDSE, the directory is updated when a member is updated but the connection lets the fetcher locate the "old data". Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
