I'm a bit confused. I think I have gotten lost in the postings.
But something did get my attention:
If I have to change my profile's HLQ, and I'm running REXX in
LPAR1 while also logged on on LPARs2-3, Won't that change done
within that REXX affect the PROFILE in the other LPARs with their
next read of the profile data? -- UNLESS those profile data sets
are unique? This kind of thing really makes the profile have to
be unique on each LPAR to avoid issues like this. Unless I'm
missing something.
Steve Thompson
On 11/23/2024 6:19 PM, David Spiegel wrote:
Hi Gil,
You said: "...It is no better than assigning multiple User IDs.
..." What's wrong with one person having more than one userid?
Sometimes it is necessary. For example, one userid is running a
TSO Command and the other is setting/changing system trace
options or looking at dumps. At one of my jobs, the developers
get 5 userids. Regards, David
On 11/22/2024 16:09, Paul Gilmartin wrote:
On Fri, 22 Nov 2024 15:18:36 -0500, David Spiegel wrote:
All? ... No, just the //ISPPROF which can be fixed by
including the LPAR
name as part of the DSNAME. E.g.
<userid>.ISPF.ISPPROF,<lpar-name>
Ouch! Profile changes on any LPAR would not be effective on
other
LPARs. Many (but not all) users would find this unacceptable.
It is no
better than assigning multiple User IDs.
But<https://www.ibm.com/docs/en/zos/3.1.0?topic=logons-duplicate>
says:
ISPF profile sharing or changes to default ISPF data set
names
might be needed to avoid errors in ISPF with multiple
logons.
See z/OS ISPF Planning and Customizing for more details
about
configuring ISPF to support multiple logons.
"profile sharing"
But the referenced document is an abstract containing
a circular reference. I'll submit a Feedback.
--
Regards,
Steve Thompson
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
