I guess you all missed the original Frank's email [probably on IBM-MAIN] where he said this load module is just a [configuration?] DATA to be accessed via either MVS or CICS LOAD and then mapped by a copybook...
-Victor- ============================= On 2015-12-09, at 09:59, David Cole wrote: > > That may work if your load module consists of only a single csect. If you > start building multi-csect load modules, then it won't work at all, since > your method can provide only the length of that single csect. > > If you want to find the length of a multi-csect load module, you can do so > using DXD statements placed at the end of every csect, and then a q-con to > reference the cumulative length of all csects added together. (I'll leave it > to you to research the missing details.) > And even that may not suffice if you have library modules autocalled from a Binder SYSLIB not under your control. Binder needs a variant of ORDER to place a dummy CSECT at the end of the module. "DISORDER"? -- gil
