On Fri, 5 Jul 2019 09:35:49 -0500, Elardus Engelbrecht wrote: >Allan Staller wrote: > >>This typically happens (in my experience) when a single ISPPROF dataset is >>shared across multiple images (last update wins). > >True, last one wins always. This is WAD, not BAD. > ISPF Edit nicely serializes member updates. ISPF seems unable to do likewise with ISPPROF. I call that BAD.
Should there be more metadata for accountability? Would PDSE member versions help? >>A)Code/install ISPF EXIT 16 to change the name of the ISPPROF dataset being >>used to something image specific. > >This is what I did. No problemo anymore with unneeded ISPPROF dsn changes by >LPAR specific applications. > Ouch! So profile changes on a "master" system remain invisible on subordinate systems? Perhaps more control should be given to the user, such as a confirmation prompt at LOGOFF: "Do you want to save or discard profile changes?" -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
