Thank you Salva. We have only one Sysplex here (though we do have 2 JESPLEX's for historical reasons), and I have confirmed that the two LPAR's I have access to run code on have different last byte values (02 and 08) so I am reasonably confident I can use that byte for LPAR uniqueness here.
I would still like to see any available documentation of how z/OS sets that value (if any such documentation exists) so I have backup in case management asks. Peter Relson or Jim Mulder, can either of you say whether there is any available documentation of this TOD field setting? Peter -----Original Message----- From: Salva Carrasco <scarra...@unicaja.es> Sent: Thursday, March 18, 2021 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU; Farley, Peter x23353 <peter.far...@broadridge.com> Subject: Re: Contents of TOD Programmable Field under z/OS? Peter, from my Sysplexex (two CPC, two Sysplexes): Sysplex 1: LPAR1 - CPC 1 - 00D96E2471DF1F558800000008040001 LPAR2 - CPC 1 - 00D96E2543F30EBBA200000008040003 LPAR1 - CPC 2 - 00D96E24D3FB32884200000008040002 LPAR2 - CPC 2 - 00D96E25612D8B384600000008000004 Sysplex2: LPAR3 - CPC 1 - 00D96E25A47E64BAC000000008000001 LPAR4 - CPC 2 - 00D96E25CB7002F3C400000008080002 Last byte match the first byte from SYSTEM NUMBER output of DISPLAY XCF,SYSPLEX,ALL. No idea about bytes 29, 30 & 31. Regards, salva. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
