This does not give you call relations, where programs are statically
linked.
And static analysis (related on source code) does not give you relations,
where the name of the callee comes from a table or is computed at run time.
That's what a former customer did (besides static analysis, which was
done, too):
every program had a startup macro (no matter, if PL/1, ASSEMBLER, or C).
In ASSEMBLER, the startup macro did all the housekeeping, too, of course.
This startup macro, on first call, wrote a WTO message, like:
"I am module XXXXXXXX EP YYYYYYYY called by ZZZZZZZZ compiled at .... "
only once.
At the end of the day, all production jobs and dialog regions (IMS) etc.
were
scanned for these message types and the call relations were written to
a repository :-)
and this was done day by day.
Kind regards
Bernd
Am 13.11.2019 um 22:07 schrieb Mike Schwab:
http://www.longpelaexpertise.com.au/ezine/SoftwareUsageWithoutTADz.php
For many years IBMs Peter Relson has offered a free ‘as is, no
warranty’ tool to monitor program fetch activity: the Module Fetch
Monitor. Contact Peter directly at rel...@us.ibm.com.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
