What is the purpose of the tversion.o and gversion.o object files created within the module source directory and how are they used?
The gversion.o and tversion.o are object files created at build time from the source file gversion.c and tversion.c both located in $IEFH/src and placed in the Loadmodule source directory. These files are linked into the Loadmodule and RI trigger library respectively to provide file version and build date/time information. The gversion.o is linked into Loadmodules and the tversion is linked into the RI Triggers library.
To check this information with a Loadmodule or RI Trigger Library, enter the "what" command for the Loadmodule or RI Trigger and grep on "Gen".
For example to check the file versions and build dates of the Loadmodule P900, enter: "what P900 | grep Gen" at the UNIX command line. This will return information such as build date/time of the P900 application along with the related AllFusion Gen shared library file versions and build dates/times.
NOTE: The what command does not exist on Linux and users may need to use an alternate method to check the relevant data e.g.
strings <loadmodule or RI Trigger Library> | fgrep '@(#)'
In Gen r8.5 we changed the IT on Unix/Linux to created the gversion within the build script, you will no longer have a gversion within $IEFH/src.
The CA Gen 8.5 documentation explains under the topic "Application Versioning".