I do not have UADS here and do not use the specified exit. The only modification I made was to the PROFILE, where I added the &SYSNAME esoteric.
The major change involves the parmlib member GRSRNL00. Specifically, the following rule must be updated: RNLDEF RNL(EXCL) TYPE(SPECIFIC) QNAME(SYSIKJUA) RNAME(XXXXXXXX) The RNAME specifies an ID because we restrict this action to certain individuals. If you do not wait it restricted remove the RNAME. When you add this dynamically, it generates a WTO to propagate the change across all LPARs. Afterward, you must update this rule on all LPARs. Please note, the GRSRNL00 member must remain consistent across all LPARs; otherwise, the IPL process will fail. Additionally, I believe the TSO ISPCCONF utility includes a PROFILE_SHARING value that may require updating to enable profile sharing. I do not utilize profile sharing, as I maintain separate profiles for each LPAR. Hope this helps. Thank You -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Friday, November 22, 2024 1:32 PM To: [email protected] Subject: Re: Logon to TSO+ISPF on multiple LPAR's at the same time? ! CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? Were you expecting this email? If not, report it using the Report Phishing Button! On Fri, 22 Nov 2024 13:19:02 -0600, Lionel B Dyck wrote: >See >https://www.i/ >bm.com%2Fdocs%2Fen%2Fzos%2F3.1.0%3Ftopic%3Dlogons-duplicate&data=05%7C0 >2%7CSteely.Mark%40ACE.AAA.COM%7C82760b5bb3e648a84e7308dd0b2c6975%7Cd5f6 >18ff295149048f7e999c2dd97ab2%7C0%7C0%7C638679007564629839%7CUnknown%7CT >WFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs >IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oA9ds%2FmdV17x0UHxI >QxZ37Pcxl8BaFg0f7uGPpYOcUc%3D&reserved=0 > Is UADS still a thing? I'm surprise. I thought it was replaced by RACF long ago. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
