Already asked everyone to start using this ($VERSION compiler directive).

-dtd




[log in to unmask] on 11/09/2001 10:50:00 AM
To:     [log in to unmask]@Internet
cc:      (bcc: David T Darnell/CO/KAIPERM)
Subject:        Re: [HP3000-L] XL version string under LINKEDIT?

At 7:15 -0600 11/9/01, Dennis Handly wrote:
>David T Darnell ([log in to unmask]) wrote:
>: How do I set the version attribute of an XL, without rebuilding it from
>: scratch ... In the below example the version of the XL is 85082112. I would
>: like to change it, or at least increment it, every time I modify the XL.
>: 140 listxl;module=aslkup
>: 143 VERSION        : 85082112
>
>You can't.  That is the internal (layout) version of the SOM and it can't be
>changed without some kind of roll.


However, you *can* include a user (programmer) configurable version string
in your NMOBJ files at compile time. In Pascal/iX you would include
something like this at the top of your source file:

  $version 'my_module vA.01.05'$

I forget offhand the C and COBOL ways to do this, but it can certainly be
done in those languages, too, as well as any other.

Then, once this module is added to an XL or linked into a program, either
directly or via an RL, MPE's VERSION command will show your version string.

HTH,


Barry Lake                               [log in to unmask]
Allegro Consultants, Inc.                http://www.nospam.allegro.com
(408)252-2330
-------------
Remove ".nospam" to create valid address.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *