Beauty is not what comes to mind with Cobol and I am old and did code in Cobol years ago. I use to code Cobol on VMS as was required at a job. But the applica

Beauty is not what comes to mind with Cobol and I am old and did code in Cobol years ago. I use to code Cobol on VMS as was required at a job. But the application was more of a systems application and had to be redundant. So I would code using VMS system services so it did not look like Cobol. Did have to figure out how to create data structures in Cobol needed with the system services. So a 32 bit word for example, descriptor, reference. I did the redundancy by taking out a cluster lock on the cluster with a wait ($ENQ_W). Then it was part of the startup on all the nodes in the cluster but only one got the lock and the others were stuck in a wait state. So simple. If the Vax crashed or rebooted for maintenance another node would get the lock and run properly. The devices the application interacted with were attached to terminal servers so all the nodes in the Vax cluster could see the terminal server. What was ridiculous is that it should have been written in assembler or C instead of Cobol. Just because it was Cobol no one else was going to be able to maintain just because it was Cobol. What normal Cobol programmer is dealing with system level things? I basically did everything using library and system services. So there was almost no lines of code that look like any normal Cobol. Wonder if that code is still running?