I need to find out the last execution date of all the natural objects in my library (programs, maps, subprograms, subroutines, etc). Is this information recorded somewhere in FUSER? My problem is that I do not know when a natural object is being last executed.
Please advise how I can obtain the information I need. Any Natural utilities?
We’ve implemented a bufferpool-history on our Solaris-Box. Every 5 minutes we save a complete listing of the buffer pool. Every evening, we delete all modules from the buffer pool. So we know when an object was called the last time.
If you implement a NATRDC user exit, it can write out the library & object name of every object loaded into the buffer pool, which can be flushed out to flat file for programmatic loading into a database so that you can retain this information. However, you will need to implement and let this run for a long time in order to know if the objects are run at all or just not very often for those that are missing.
The ultimate goal is to find out what modules are still being used at runtime. If I were to retrieve the information from bufferpool for this purpose then I would need this process to run for the period of a few months just to cover as wide a basis as possible. Even if I can identify a certain percentage (high I hope) of the modules and manually address the rest that would be fine.
Building something around NATRDC is the most reliable way on the mainframe,
but it isn’t available on OpenSystems, so using the bufferpool information probably
is the best bet here, however, there’s a risk of missing entries when they are purged
No, it’s all Solaris-stuff. I’m afraid it won’t help you on Mainframe.
It’s a simple cronjob - called every 5 Minutes:
natbpmon bp=mybp dir k=g > /tmp/nat.monitor.log
natbpmon bp=mybp dir k=s >> /tmp/nat.monitor.log
# this perl-script feeds a kind of Bufferpool-database with the content of nat.monitor.log
No. We just want to know when a program was used the last time. For example: If you want to change a field length it’s very useful to know which modules are used every day and which one is used only one time a year (e.g. for stock-taking) …