Author: mainakdalal
Posted: Tue Oct 04, 2016 5:49 pm (GMT 5.5)
Hi All,
I was able to figure it out. The table is actually made up of Assembler macros. They were not in the standard maclib but in a different PDS. When I expanded the macros used as keyword in the table, I found that the code is actually loading the table in a register, which points to the address of register 1 for linkage to calling module. This is how the table values are passed to called COBOL code.
On the other piece of code, which seems like a screen layout, is actually working as a card input to some code. unfortunately we do not have the driver source code, but only the load to it :-(
Thanks for all your help in pointing me towards a solution.
_________________
knowledge sharing in mainframe is my intension
Posted: Tue Oct 04, 2016 5:49 pm (GMT 5.5)
Hi All,
I was able to figure it out. The table is actually made up of Assembler macros. They were not in the standard maclib but in a different PDS. When I expanded the macros used as keyword in the table, I found that the code is actually loading the table in a register, which points to the address of register 1 for linkage to calling module. This is how the table values are passed to called COBOL code.
On the other piece of code, which seems like a screen layout, is actually working as a card input to some code. unfortunately we do not have the driver source code, but only the load to it :-(
Thanks for all your help in pointing me towards a solution.
_________________
knowledge sharing in mainframe is my intension