| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 547.1 | | QUARK::LIONEL | Free advice is worth every cent | Tue Apr 29 1997 12:55 | 18 |
| The wording in the installation guide is "legalese" - it means that the customer
must have purchased either a version-upgrade license or a support contract
with a right-to-new-versions in order to rightfully do the upgrade. However,
for the majority of customers, this is just words as there's nothing in
OpenVMS that enforces this.
For internal users, the PAKs we get have "release dates" and you will want to
make sure that your OPENVMS-ALPHA PAK has a release date that is in the future,
which may mean going back to VTX PAK and getting a new one (don't forget to
disable or delete your old PAK before regsistering the new one.) Otherwise,
OpenVMS will complain.
It's been a long-standing gripe of mine that we choose to do business in a way
that makes it difficult for customers to honor their license agreements,
leaving money on the table, so to speak, yet we make internal users pay through
the nose for internal PAKs that have to be continuously renewed.
Steve
|
| 547.2 | QAR the doc, for the Raven Release... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Apr 29 1997 13:07 | 4 |
|
Please QAR the documentation -- if it's confusing, it needs to be
clarified. (Even if our licensing policies are a little screwy, we
_should_ be able to describe the policies in text. Yeah, I know...)
|
| 547.3 | future is OK, but the not to distant past is ok too | STAR::ABIS | I come in peace | Thu May 01 1997 11:15 | 9 |
| >For internal users, the PAKs we get have "release dates" and you will want to
>make sure that your OPENVMS-ALPHA PAK has a release date that is in the future,
PAK release dates have nothing to do with the current date/time. On V7.0, your
OPENVMS-ALPHA PAK must have a release date of 1-JUN-1990 or greater. If your
current PAK meets that requirement or has no release date, there is no need to
waste money getting a new PAK from VTX PAK.
Eric
|
| 547.4 | | QUARK::LIONEL | Free advice is worth every cent | Thu May 01 1997 12:11 | 6 |
| I said "in the future" because I despaired of trying to explain how to determine
what "not too distant past" would be, since OpenVMS tends not to document the
release date it uses. If you ensure that the PAK release date is in the future,
you'll rarely have a problem.
Steve
|
| 547.5 | the LMF tip of the day | STAR::ABIS | I come in peace | Thu May 01 1997 14:28 | 6 |
| Just trying to save some cost center a few $$$. :^)
If you have access to the resd (result disk) of a release, you can find out the
minumum PAK release date with this command:
$ search/window=7 xxxx_resd$:[sys.lis]system_data_cells.lis gq_license_date
|
| 547.6 | | TLE::REAGAN | All of this chaos makes perfect sense | Thu May 01 1997 14:59 | 5 |
| Since most do not, perhaps the output of the above search command can
be put in the read-before-installing document or at least in the note
that announces the availability?
-John
|
| 547.7 | | QUARK::LIONEL | Free advice is worth every cent | Thu May 01 1997 16:07 | 5 |
| Or you can go ahead and install it and see if it complains. I'd say that if
your PAK's release date is more than a month earlier than the date the kit
was announced, it's probably best to get a new PAK.
Steve
|