| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 410.1 | Question | OPG::SIMON | | Thu Sep 22 1994 10:14 | 1 |
| Was this OpenVMS or was it UNIX???
|
| 410.2 | OVMS | FIREBL::LEEDS | From VAXinated to Alphaholic | Thu Sep 22 1994 15:25 | 3 |
| >Was this OpenVMS or was it UNIX???
OpenVMS AXP V6.1 on a DEC 3000-400
|
| 410.3 | | OPG::SIMON | | Thu Sep 22 1994 16:21 | 18 |
| Hmm,
we had a similar question to this a little while ago and checked out whether
our code was correctly reading VCS PAKs on PCM OpenVMS.
We found that V1.5 DID correctly read the PAKS, but that there was a bug in
the LMF code which caused some funny results.
What we found was that loading the PAKS worked OK, but although LMF said they
were available we could not read them. We did a license unload followed by a
license load and the PAKs were then usable!!!
I mentioned this to our CSC colleague in the US and he said he had heard of this
before!!!
Dan (the CSC man) can you confirm what I said is fully correct ( it was a few
months ago and I have a brain like a sieve).
Cheers Simon...
|
| 410.4 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Sep 22 1994 22:03 | 16 |
| >I mentioned this to our CSC colleague in the US and he said he had
>heard of this
>before!!!
>Dan (the CSC man) can you confirm what I said is fully correct ( it was
>a few
>months ago and I have a brain like a sieve).
Totally correct Simon. The nature of these paks is such that they need
to be loaded all at once. We also tested to make sure an Alpha would
use the paks so we configged a bunch of pseudo-nodes and they all
worked fine. You will still get the nastygram from LMF about the
Console-manager pak not being found.
Regs,
Dan
|
| 410.5 | bottom line ?? | FIREBL::LEEDS | From VAXinated to Alphaholic | Fri Sep 23 1994 00:13 | 11 |
| > Totally correct Simon. The nature of these paks is such that they need
> to be loaded all at once. We also tested to make sure an Alpha would
> use the paks so we configged a bunch of pseudo-nodes and they all
> worked fine. You will still get the nastygram from LMF about the
> Console-manager pak not being found.
>
So does that mean my customer does not need a new pak ?? Are his VCS paks on
the AXP okay even with the "nastygram" ?? How would they correctly get the
POLY-CONSOLEMGR pak ?? We can't find a unique part number to order it ...
|
| 410.6 | More than one problem here. | OPG::SIMON | | Fri Sep 23 1994 12:11 | 56 |
| Well,
we do have two problems here. I was trying firstly to deal with
the immediate problem of getting your customer on-line and able to use
the product. Now we need to look at the other bit i.e. why you appeared
to get the wrong PAKs.
Here is an extract from the PCM SPD/SSA.
ORDERING INFORMATION
RISC ULTRIX Systems:
Software Licenses: QL-MU1A*-**
Software Media: QA-MU1A*-**
Software Documentation: QA-V01AA-GZ
Software Product Services: QT-MU1A*-**
OpenVMS VAX Systems:
Software Licenses: QL-V01A*-**
Software Media: QA-V01A*-**
Software Documentation: QA-V01AA-GZ
Software Product Services: QT-V01A*-**
OpenVMS AXP Systems:
Software Licenses: QL-2PCA*-**
Software Media: QA-2PCA*-**
Software Documentation: QA-V01AA-GZ
Software Product Services: QT-2PCA*-**
Software Documentation: QA-V01AA-GZ
Software Product Services: QT-V01A*-**
OpenVMS AXP Systems:
Software Licenses: QL-2PCA*-**
Software Media: QA-2PCA*-**
Software Documentation: QA-V01AA-GZ
Software Product Services: QT-2PCA*-**
Looking at that it appears you actually did not use the order number
for AXP PAKS. the part number should be of the form:
QL-2PCA*-**
What that does not explain is that the QLV01AA part number getting
VCS PAKs generated, as this should have got an OpenVMS Vax PAK.
I shall get this sorted out.
Hope this has helped.
Cheers Simon...
|
| 410.7 | not for CONCURRENT licenses !!! | FIREBL::LEEDS | From VAXinated to Alphaholic | Fri Sep 23 1994 17:12 | 44 |
| > we do have two problems here. I was trying firstly to deal with
> the immediate problem of getting your customer on-line and able to use
> the product.
We solved that when we installed the system by getting them temp paks.
> Now we need to look at the other bit i.e. why you appeared
> to get the wrong PAKs.
You are semi-correct on the ordering.... this was sold thru a VAR. They
were originally going to sell them a VAXstation and VCS. We convinced
them to change to an AXP and PCM. They changed the part numbers for the
hardware, but it appeared from all sources that they did NOT have to
change the part numbers for the software....
The confusion comes in the following:
According to the Sales Update article that went out, the SPD (see below)
and whatever VARs look at for part numbers (Electronic Store ?), the part
number for UNLIMITED use of PCM on an AXP is QL-2PCA*-** as the SPD
states.
However, the part numbers for the CONCURRENT licenses are the same as for
VCS (QL-V01A*-**). So, they order 12 copies of QL-V01AA-3B.
From the PCM V1.1 SPD :
OpenVMS AXP Systems:
Software Licenses: QL-2PCA*-**
Note: The QL-V01AA-3B concurrent license for OpenVMS VAX is usable on
the OpenVMS AXP platform.
There is no separate part number for concurrent licenses for PCM on AXP
VMS.....
So why didn't the QL-V01AA-3B work for PCM on AXP as the SPD states ????
Thanks
Arlan
|
| 410.8 | | OPG::SIMON | | Mon Sep 26 1994 10:10 | 3 |
| This problem is being dealt with by Mail.
Cheers SImon....
|