Yeah , now i see thank you Charles Regards, Scott
On Thu, Mar 19, 2015 at 11:54 AM, Charles Mills <[email protected]> wrote: > You can use the LOAD macro (fetch a program but don't branch to it) to > bring a module into storage and then treat it as a big table of some sort. > > You would need to "find things" in the table by basing off the entry > address -- possibly using A() pointers there -- which is returned by the > LOAD macro. I suppose alternatively the entry could point to an executable > routine that returned the desired information. > > This is a fairly common technique. For example, the COBOL compiler's local > customization options reside in a non-executable load module that the > compiler uses in this fashion. > > Charles > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Scott Ford > Sent: Thursday, March 19, 2015 8:27 AM > To: [email protected] > Subject: Load modules > > All, > I have a question about a process. One installation I worked in we loaded > an object module into storage and the residing program used data inside the > load module ...Has anyone else seen this ? if so do you by chance have an > example. I need to base some product activation messages on where certain > criteria, I want to base it on a module residing in a load lib ... > > Regards, > Scott > www.identityforge.com > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
