ONE of entry points can serve as the constructor. OTHERS as methods. But that's up to programmer. As procedures can be nested that provides sub classing. If all variables were static that constructor was not really necessary. Of course nothing was STILL formalized, but that was happening in early 60th not in late 80th .

But there was a beauty in it: this was a very simple and very effective technique of creating your own namespace for the set of procedures; technique that any programmer can easily learn and successfully apply. So successfully that usually he/she did not write in other way since this point.

ALLOCATION of variable in the stack was also optional as SERVERS at this time were really minuscule even in comparison with modern smartphones; the latter are far suprassing the largest of system 360 servers in capabilities including CPU speed, memory size and the size of the harddrives. 

One of entry points can serve as the constructor. Others as methods. But that's up to programmer. As procedures can be nested that provides sub classing. If all variables were static that constructor was not really necessary. Of course nothing was still formalized, but that was happening in early 60th not in late 80th .

But there was a beauty in it: this was a very simple and very effective technique of creating your own namespace for the set of procedures; technique that any programmer can easily learn and successfully apply. So successfully that usually he/she did not write in other way since this point.

Allocation of variable in the stack was also optional as servers at this time were really minuscule even in comparison with modern smartphones; the latter are far suprassing the largest of system 360 servers in capabilities including CPU speed, memory size and the size of the harddrives.