T.R | Title | User | Personal Name | Date | Lines |
---|
510.1 | <Sharp intake of breath> | MARVIN::CARLINI | | Tue Apr 22 1997 17:07 | 22 |
| In general, if you link on Vn you cannot expect to automatically run on
V(n-1) and earlier. If you want to run on an earlier version, the only
supported way of doing it is to build on the earlier version.
Now the customer may very well decide that they can take the relevant
SYS$LIBRARY portions of SYS$SYSTEM and (and anything else they link
against) from an earlier version and shove it into some j-random
directories on their current system, define the appropriate process mode
logicals (SYS$LIBRARY,SYS$SYSTEM etc) and build away. They may even go
so far as to define a LINK logical so they pick up the linker from the
appropriate version of OpenVMS (although if they do this after V7.0 or
V7.1 they may hit some "issues" with CLDs) to guarantee that they get
compatible images.
This would all be unsupported, despite anything you may hear about PSI,
WANDD, DECnet (and even VMS itself) doing just this.
Feel free to translate the above into a "Yes" or a "no" ...
Antonio
|
510.2 | Seems fairly clear to me | GIDDAY::GILLINGS | a crucible of informative mistakes | Tue Apr 22 1997 20:35 | 13 |
| Steve,
To my reading that section is quite clear:
"If your program uses any of these system services and you want to create
a version that runs on systems prior to Version 7.0, you must link your
program on a system running a version of OpenVMS prior to Version 7.0"
> Can you copy the old version of the secureshr to the v7.1 system, and
> link with that
You can try, but if it doesn't work, see 5.22.1.2.
John Gillings, Sydney CSC
|
510.3 | Not A New Restriction... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Wed Apr 23 1997 10:20 | 17 |
| : I've a customer using OpenVMS v7.1 VAX.
: In the release notes section 5.22.1.2, (for v7.1), it says if you're
: using secureshr.exe, you need to link on the version of VMS
: prior to v7.0.
: Can you copy the old version of the secureshr to the v7.1 system, and
: link with that, rather like release notes 5.15.1.1 for mthrtl.exe?
For support, one must link on the oldest version to be supported,
and then test there.
Your customer *may* be able to pull the older shareable images and
such forward and link against those, but this is not a supported
procedure, and this procedure (still) requires testing on the oldest
OpenVMS release targeted.
This is not a new restriction -- this is a day-one OpenVMS requirement.
|
510.4 | But? | KERNEL::PULLEY | Come! while living waters flow | Wed Apr 23 1997 11:42 | 4 |
| Ok, I get the idea.
Would anyone like ot tell me why the restriction seems to be
temporarily lifted for mthtrl in 5.15 of the same release notes?
|