Be aware that it's quite common for customers to repeat the same sysplex name for monoplexes. I'm also aware of at least one customer who repeats SMF IDs too. LPAR name can help, but if the goal is to keep the identification even if the system is IPL'ed on another CEC, then that might be counter-productive because some customers change the LPAR name when they move between CECs either for DR or site swap or even just because they upgraded to a new machine.
If it's possible to do something, somebody probably will. Scott Chapman On Wed, 5 Jun 2024 07:25:29 -0400, Matt Hogstrom <[email protected]> wrote: >Thanks Marc, that is promising; I’ll explore that option. > >Matt Hogstrom >> On Jun 5, 2024, at 07:12, Mark A. Brooks <[email protected]> wrote: >> >> It may not help, but be aware that the XCF SysplexID and SystemID have a >> good chance of being unique if you need to identify an instance of a z/OS >> IPL across the universe of sysplexes. These IDs are available via IXCQUERY >> macro using REQINFO=COUPLE. >> >> Mark Brooks >> z/OS Sysplex Development >> >> ---------------------------------------------------------------------- >> 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
