# tool to identify source code info from the object code

**URL:** <https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-Utilities\
**Created:** [November 18, 2008, 1:18am UTC](https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514 "2008-11-18T01:18:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg\_Atkinson](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@Greg\_Atkinson](https://techcommunity.softwareag.com/u/Greg_Atkinson)\
**Post date:** [November 18, 2008, 1:18am UTC](https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514/1 "2008-11-18T01:18:28Z")

</div>

I’m looking for a tool (for natural on the mainframe) that can help me identify the source code that was used to create object code - something maybe as simple as the source codes save timestamp used to create the object code. Does something like this exist? Reason - we have an environment where someone can create object code and then overlay the source code with ‘old’ code so that the save date of the source code is older than the object code and visually all it looks like is someone saved the code a few days before catting the code. It’s a maintenance nightmare. Any ideas or help would be appreciated.

---

<div class="post-metadata">

**Author:** ![Steve\_Robinson](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/steve_robinson/32/107_2.png) [@Steve\_Robinson](https://techcommunity.softwareag.com/u/Steve_Robinson)\
**Post date:** [November 18, 2008, 1:25am UTC](https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514/2 "2008-11-18T01:25:52Z")

</div>

If you simply LIST \* \*, you will get a list of all the objects in a library. If you see lines where text is intensified, you know that the source and object are out of synch.

steve

---

<div class="post-metadata">

**Author:** ![Greg\_Atkinson](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@Greg\_Atkinson](https://techcommunity.softwareag.com/u/Greg_Atkinson)\
**Post date:** [November 18, 2008, 3:31am UTC](https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514/3 "2008-11-18T03:31:39Z")

</div>

True for the listing screen but in our environment, most our production code is copied into the production database keeping the save date of the source code but not allowing the object code to be copied, thus you have to cat the code again. In this design, that feature of the listing screen is mostly lost here. If everyone followed this procedure it would not be a problem, but when someone does it is hard to find that one issue right now.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:51pm UTC](https://techcommunity.softwareag.com/t/tool-to-identify-source-code-info-from-the-object-code/79514/4 "2021-04-02T14:51:09Z")

</div>