There is no inode information for "creation" date; but if you istat the
binary it will tell you the last time it was modified which should imply
the day it was compiled unless you make changes directly to it ( which I
doubt ).

Installs:
instfix -lk [fix #] Checks if fix is installed
instfix -i | grep ML Checks to see if all filesets were
installed for ML's
Installp -c Cleans up after a cancelled or
interrupted install.
And whichlpp command

> Thanks. I should have been more specific with my question.
> If I compile a 'C' program, is there a command to tell me the
> date and time I compiled the program?
>
> Mike

> There is no inode information for "creation" date; but if you
> istat the binary it will tell you the last time it was
> modified which should imply the day it was compiled unless
> you make changes directly to it ( which I doubt ).
>
> istat <filename>
>
> Lamar
>

Mike: at the risk of being overly picky the istat command doesn't
necessarily give you the information you think it does. It tells you the
date that a file was created regardless of how it was created there. If
you build an executable into one directory then after a lapse of time
copy it to a second directory, istat on the second location will show
the time of the copy not the time of the build in the original
directory.

Overly picky is accepted at any time. You get more information to help
better answer my question, and I get an answer which is more accurate
for future reference. One thing that really frustrates me is getting an
answer to a question only to find out in the future the information was
totally incorrect.

Lamar: I've got a feeling there is no definitive solution to what you
want. I'm comparing AIX to the mainframe of my salad days (25+ years
ago). The equivalent there to the linker was a program called the
linkage editor and it had a function whereby it added special data
called IDR records into an executable that could contain any arbitrary
information you wanted. Out of the box it stamped executables (load
modules for any other old geezers out there) with time and date as well
as its own version and those of the compilers. Sometimes I wonder if
we're making any progress at all in this business:-)

Jim,
Not me that wanted a solution... I was just providing what I thought
was the best answer since we do not track creation time. I am thinking
that the same information should still be available in the binary.

Hey, you sent me down a trail that seems fruitful... I can't remember
who asked about the creation date of binary, but it seems you can derive
it:

It was me. I tried "dump -ohv <binary> | grep Timestamp and the
following was returned:

Timestamp = "Mar 05 17:10:03 2007"

Perfecto!

Thanks for continuing the discussion.

Mike

>
> Jim,
> Not me that wanted a solution... I was just providing
> what I thought was the best answer since we do not track
> creation time. I am thinking that the same information
> should still be available in the binary.
>
> Hey, you sent me down a trail that seems fruitful... I can't
> remember who asked about the creation date of binary, but it
> seems you can derive
> it:
>
> dump -ohv <binary>
>
> Look for the Timestamp entry.
>
> Back to the MVS days Jim... <grin>
>
> Lamar
>

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.