ISPF also nicely serializes ISPPROF updates. >>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. ---------------------->ISPF also nicely serializes ISPPROF updates.
Ouch! So profile changes on a "master" system remain invisible on subordinate systems? ------------------------> Nope. As was previously indicated, given a single dataset, the latest update wins. 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?" ------------------------> This is why ISPF Exit 16 was provided. To segregate the ISPPROF datasets. No need for the prompt. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Friday, July 5, 2019 10:35 AM To: [email protected] Subject: Re: Who is changing a user's ISPF profile 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 [email protected] with the message: INFO IBM-MAIN ::DISCLAIMER:: -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
