On Tue, 20 Feb 2024 22:58:42 +0000, Farley, Peter <[email protected]> wrote:
>the monotonically increasing real-time clock to be the “tie breaker” value. Real-time clocks are not monotonical. Regardless of vendor, there is 1 real-time clock shared by all CPU cores. > I guess COBOL programmers aren’t supposed to be that “sophisticated”. Cobol flawlessly implement security, flawlessly optimize programs that need to be optimized, flawlessly implement NOSQL, flawlessly implement private cloud applications and more. Cobol programmers are more likely to educate themselves more on their line of business. >Or maybe the real issue is the lack of existing support in COBOL for data >structures >like heaps, queues, lists, maps and sets that are so common else where >in the programming language universe. Why implement these concepts when there are robust z/OS alternatives that achieve the same results? > if the “keys” for the heap to be attached were guaranteed by the application > design > and implementation not to have any of the keys in the heap to which it is > being attached, > just keeping the highest counter value would be sufficient. Why bother with unique keys if all you want is LIFO or FIFO access by key. Do you have a problem with using duplicate keys in the heap and access using min or max? I'm guessing you are writing the heap logic. You can read from the left branch and write to the right branch. >In the more general case, how do we get away from needing to use assembler to >write COBOL? >Using CS, CDS, CDSG, PLO, ENQ, etc. to maintain a consistent non-timer counter >value would > all need to be invoked from assembler (or possibly MetalC using > “builtins.h”). Under CICS, Cobol has direct access to ENQ and STORAGE OBTAIN. Single threaded COBOL does not need serialization (e.g. ENQ). Someone familiar with COBOL and the environment you will be using can tell you if storage obtain, multi-threaded and serialization is available / how to use it. >Mind you, I am far from one to shy away from assembler, I am very comfortable >with it. Trivial assembler programs should be acceptable. STORAGE OBTAIN / RELEASE is trivial. CSDG for serialization update of a counter is trivial. Metal C could probably achieve the same functionality. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
