| Title: | Software Licensing Issues |
| Moderator: | YUPPIE::JENNINGS |
| Created: | Thu Aug 13 1987 |
| Last Modified: | Wed Apr 09 1997 |
| Last Successful Update: | Thu Apr 17 1997 |
| Number of topics: | 441 |
| Total number of notes: | 1794 |
Hello,
I am with the engineering group for the optical storage software
for OpenVMS VAX and Alpha. A gentlemen from Digital Canada called
me with the following problem:
Customer has an Alpha and when they tried to install the following
pak it fails with a "license not valid for this architecture" kind
of message. I have a FAX of the pak and it loads fine on a 3000/500
running V6.2, an 8200 running V6.2-1H3, and a 4100 running V7.1.
The customer loaded the pak on a VAX and it worked. I also tried to
load it under Digital Unix and LMF said "invalid checksum".
Issuer DEC
Auth # ALS-NQ-1996DEC17-1120
Product OSDS-5
Producer PERCEPTICS
# units 10
Act Tab c CONSTANT=10
Checksum (starts with "1-"
The customer thinks the pak needs the work "ALPHA" in the key
options field.
My questions:
o Any ideas on why can I load pak but customer cannot?
o Would pre-VMS 6.2 versions make a difference?
o Is the first digit of the checksum coded to mean anything special
to LMF such as 1=VMS,2=UNIX,4=VMS or UNIX?
Thanks,
Rob
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 440.1 | QUARK::LIONEL | Free advice is worth every cent | Thu Apr 03 1997 16:38 | 8 | |
The first digit of the checksum is called the "seed" - really, it's more an encoding level. The only choices are 1 and 2 - 1 was used initially on VAX, but a defect in the algorithm was discovered and we switched to 2. UNIX doesn't know about 1- checksums. Activity type C is a VAX-only concurrent-user license. Steve | |||||
| 440.2 | should work on any architecture | GIDDAY::GILLINGS | a crucible of informative mistakes | Thu Apr 03 1997 22:30 | 25 |
> Activity type C is a VAX-only concurrent-user license. I think "Act Tab c" is just shorthand for "Activity Table Code" which is "CONSTANT=10". This should be valid for all architectures. > o Any ideas on why can I load pak but customer cannot? The customer must be typing in different information > o Would pre-VMS 6.2 versions make a difference? No. > o Is the first digit of the checksum coded to mean anything special No. If you can register the PAK successfully, execute the following command: $ LICENSE ISSUE/PROCEDURE/OUT=PAK.COM OSDS-5/PRODUCER=PERCEPTICS Now take PAK.COM and send it to your customer by electronic MAIL or on a tape. Have them execute the procedure to register the PAK. John Gillings, Sydney CSC | |||||