Author: Robert Sample
Posted: Mon Oct 03, 2016 11:49 pm (GMT 5.5)
The table may be using Assembler macros, but it certainly is not Assembler code. And the second screen shot appears to be some sort of high-level variable definition with length, initial value, error message, and range of permitted values (among other things).
Unless you find some documentation (on the system or hardcopy or intranet), it is unlikely that you will ever figure them out. Do you have the job to assemble / compile these code pieces? If not, you need to search to see if they can be found on your system. Without this JCL, you'll need to plan on replicating the functionality (whatever it is) without knowing he details -- which could be a very difficult task.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Mon Oct 03, 2016 11:49 pm (GMT 5.5)
The table may be using Assembler macros, but it certainly is not Assembler code. And the second screen shot appears to be some sort of high-level variable definition with length, initial value, error message, and range of permitted values (among other things).
Unless you find some documentation (on the system or hardcopy or intranet), it is unlikely that you will ever figure them out. Do you have the job to assemble / compile these code pieces? If not, you need to search to see if they can be found on your system. Without this JCL, you'll need to plan on replicating the functionality (whatever it is) without knowing he details -- which could be a very difficult task.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth