I've worked on a system that uses this approach. A bunch of variables are defined in the startup program called by the LOGIN paragraph, and stored in named common. The idea behind it was to centralize in the event that the called program ever needed to be changed.
Larry Hiscock Western Computer Services > Maybe some plan to change SOUREC at some key point w/o having to change it > in multiple places? > > Looks like an idea that wasn't fully thought out, but that is just my 2 > cents worth. Maybe someone has some pearls of wisdom on this. > > > JRI > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson > Sent: Monday, December 03, 2012 7:39 PM > To: u2-users@listserver.u2ug.org > Subject: [U2] Advantage of indirect call in BASIC > > I've not encountered this is my career previously, but now I'm seeing a > system written almost entirely with the use of indirect calls in Universe > BASIC. > > That is > SOURCE = "*SOME.PROGRAM" > ... > CALL @SOURCE(INPUTS) > > Is there some advantage to the use of indirect calls that a system would > be written entirely in this fashion? > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
