The UUID for a z/OS instance is what I’m looking for so this is the right track. I saw this in the z/OSMF doc but it appeared to be tied to the z/OSMF z/OS instance for service, not a UUID for each instance in a Syplex. Perhaps Marne will see this chain and respond.
Matt Hogstrom > On Jun 4, 2024, at 13:53, Lionel B. Dyck > <0000057b0ee5a853-dmarc-requ...@listserv.ua.edu> wrote: > > Take a look at https://www.newera.com/INFO/032223_Marna_I_Didnt_Know.pdf - > page 31 > > Planned for z/OS 3.1, is the capability to correlate a UUID with a running > z/OS system, which can then programmatically retrieve the SMP/E CSI which > represents the running system when used as directed. > ❖ This function is limited to the z/OS operating system Software Instance > only. Separately deployed program > products and middleware are not applicable, > > hope this helps (found the answer by asking on the System Z Enthusiasts > discord > > > Lionel B. Dyck <>< > Github: https://github.com/lbdyck > System Z Enthusiasts Discord: https://discord.gg/sze > > “Worry more about your character than your reputation. Character is what you > are, reputation merely what others think you are.” - - - John Wooden > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Matt Hogstrom > Sent: Tuesday, June 4, 2024 12:43 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: UUID for z/OS Instances > > I wasn’t clear, I’m looking for a means to uniquely identify the instance. > I can gen a UUID but I’m looking to see if there is a generally accepted > approach to uniquely identify a z/OS instance. > > Matt Hogstrom > >> On Jun 4, 2024, at 12:39, lbd...@gmail.com wrote: >> >> I can confirm that it is available with the z/OS Open Tools collection. >> >> /u/xxxx>uuidgen -h >> >> Usage: >> uuidgen [options] >> >> Create a new UUID value. >> >> Options: >> -r, --random generate random-based uuid >> -t, --time generate time-based uuid >> -n, --namespace ns generate hash-based uuid in this namespace >> available namespaces: @dns @url @oid @x500 >> -N, --name name generate hash-based uuid from this name >> -m, --md5 generate md5 hash >> -s, --sha1 generate sha1 hash >> -x, --hex interpret name as hex string >> >> -h, --help display this help >> -V, --version display version >> >> /u/xxxx>uuidgen -V >> uuidgen from util-linux 2.39.3-dirty >> >> Lionel B. Dyck <>< >> Github: https://github.com/lbdyck >> System Z Enthusiasts Discord: https://discord.gg/sze >> >> “Worry more about your character than your reputation. Character is what you >> are, reputation merely what others think you are.” - - - John Wooden >> >> From: Rick Troth <tro...@gmail.com> >> Sent: Tuesday, June 4, 2024 11:35 AM >> To: Matt Hogstrom <m...@hogstrom.org> >> Cc: Ed Jaffe <edja...@phoenixsoftware.com>; Lionel B Dyck >> <lbd...@gmail.com>; Phil Smith III <phs...@gmail.com> >> Subject: Re: UUID for z/OS Instances >> >> [off-list, but including a few luminaries] See if you have the >> 'uuidgen' command in USS/OMVS. >> I don't know how/where you would apply a unique ID of that size/length/kind, >> but unique IDs are commonly produced by tools such as 'uuidgen'. >> I suspect the command I'm thinking of is *not* stock USS but might be >> available from the "Open Tools" collection. >> >> -- R; <>< >> >> >> On 6/4/24 12:15 PM, Matt Hogstrom wrote: >> I’m looking for a way to uniquely identify a z/OS instance across multiple >> clients/customers. I see that z/OSMF has a get UUID but it appears to be >> for the z/OSMF instance and not for each z/OS. >> >> Is anyone aware of a generally accepted way to uniquely identify an instance? >> >> I’m asking because when emitting OTel telemetry data its common to >> have a UUID for an instance but that concept has really been foreign >> to z/OS >> >> >> >> Matt Hogstrom >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, send >> email to mailto: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 > > ---------------------------------------------------------------------- > 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
