Yes, and it’s not that difficult. You can either use ISPF profile sharing or use a separate ISPF profile data set on each LPAR. I have done it both ways.
On Fri, Nov 22, 2024 at 16:09 Paul Gilmartin < 0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> 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. > > -- > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
