Peter, I must disagree that it is not a programming interface. The problem-state instruction STCKE returns its value and the field is clearly defined in PoOP, so problem-state users deserve to know how the contents are set by the only program authorized to set it, the operating system.
The particular application here involves generating unique application-related values. I can also see its application to entropy-gathering routines determining a unique random seed for statistical purposes. There are probably other uses I haven't imagined. Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Peter Relson Sent: Thursday, March 18, 2021 7:14 PM To: [email protected] Subject: Re: Contents of TOD Programmable Field under z/OS? It should be expected that the principles of operation not have any information about what data is placed there, as it is specifically defined to be set by a program to whatever that program wants it to be. I'll bite: why would we want to document how the operating system sets this? It is not a programming interface. In what way would having this information help diagnosis (that being the only other reason I could think of)? Peter Relson z/OS Core Technology Design -- 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 [email protected] with the message: INFO IBM-MAIN
