The question is too vague to answer. It's also terribly uninteresting in general. What is the point of trying to make this determination? If it actually matters, then you'll have to define exactly what is meant by dynamic vs. static. For example, you could be statically called from a dynamically loaded module. Or dynamically called from a statically linked program. Plus a slew of combinations, variations, and more arcane possibilities.
sas On Tue, Nov 14, 2017 at 2:39 PM, glen herrmannsfeldt <g...@ugcs.caltech.edu> wrote: >> Yes. My question was "In a called module, how do we determine >> if it was called dynamically or statically” > > The whole design, since OS/360, is that you don’t. > > If you want to know, pass an argument to the load module that has a different > value for the dynamic case. > > Using LINK, your module is called by the system in pretty much the > same way as any other module is called. The only difference is in the > arguments, which for statically called (or the first of dynamic) is > the PARM string. > > If another load module calls you, with one argument that is a string > after a two byte length, you should work exactly the same way as if > you were not called from another load module. -- sas
