On 7/5/2019 10:35 AM, 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.
Actually, the behavior is controlled by settings in the ISPF
Configuration Dialog or SHRPROF command. Last one wins is a default,
and a good one. But feel free to chose others.
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.
Bad idea from an ISPF Edit Recovery standpoint. In a unique profile
environment, if USERA on SYSA edits a dataset and goes into recovery,
then USERA on SYSB later edits the same dataset, then goes back to A,
gets the recovery, and then saves it, all changes from the SYSB session
are lost. If you share datasets across LPARs, you should share the ISPF
profile across those same LPARs.
As an aside, if you're using exit 16 to build your profile name, you
should move that logic into your TSO logon exec.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
