| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 120.1 | A change...but still an upgrade! | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Fri Feb 07 1997 13:11 | 37 |
| re: .0
A CCS license is really 2 licenses in 1: a CNS license for your client/desktop
software and an FPA license for your server software.
Though CCS licenses are our best selling licenses, they are also the most
confusing. So, we've decided to take the first step to simplifying our
PATHWORKS licensing practices...starting with the CCS license.
With the (pending) release of PATHWORKS 32 we have eliminated the CCS license.
We will now offer CNS licenses (now referred to by the normal Digital PC
software license name, "System") and FPA licenses (now referred to as
"Designated Access" licenses to clarify it's purpose/use). We will also offer
packages that include *both* a "System" and "Designated Access" license so that
customers can continue to order 1 part number and get the same rights as they
did with the old CCS license.
Given this change, we are updating customers who have *either* CNS or CCS
licenses (except for Macintosh-based licenses), with PATHWORKS 32 V7.0 System
licenses (assuming that they have rights-to-new-versions contracts). This
license give them the *new* right to use PATHWORKS 32 code. However, it does
*not* provide or take-away any of the rights that customers with CCS licenses
already have.
What customers with current CCS licenses will do is:
1) *Continue* to use their current CCS licenses to access their servers
2) Use, or simply save as proof-of-license, their PATHWORKS 32 V7.0
System licenses.
This information is included with letters that will be sent to our MCS/SPS
customers and will be discussed in the cover letter sent with PATHWORKS 32
software.
Bottom line is that this is both and upgrad and a change.
John
|
| 120.2 | | JAMIN::WASSER | John A. Wasser | Fri Feb 07 1997 17:47 | 18 |
| > What customers with current CCS licenses will do is:
> 1) *Continue* to use their current CCS licenses to access their servers
> 2) Use, or simply save as proof-of-license, their PATHWORKS 32 V7.0
> System licenses.
It might have been nicer to upgrade the CCS license to the:
* DIGITAL Enterprise Integration Client for Microsoft Windows
License Package -- Includes a PATHWORKS 32 V7.0 System license,
a PATHWORKS V5.0 (LAN Manager) Designated Access license, a
TeamLinks Mail license, and a MAPI driver for ALL-IN-1 license.
This package replaces the CCS licenses for LAN Manager servers
(QM-0TLAA-Ax, QM-2K5AA-Ax, and QM-YFWAA-Ax).
That would have allowed them to install the PATHWORKS 32 client
software without having to re-configure each client to ask
for the PWLMDOSCC06.00 instead of the default PWLMXXXFP05.00
(PATHWORKS V5.0 (LAN Manager) Designated Access license).
|
| 120.3 | Hole? | VMSNET::P_NUNEZ | | Mon Feb 10 1997 14:51 | 23 |
| I think this has been covered, but I can't find it...
I've got DOS CCS licenses now. So I have a license to access any
PATHWORKS server. However, this license is valid only for
DOS/Win3.1/WfWg/Win95.
I also have new license version support so I should get PATHWORKS 32
v7.0 System license update. So now I've got the right to use PATHWORKS
32 on any Windows client, including NT. However, I don't get any
replacement FPA licenses.
Hmmm, but what happens when I upgrade that Win3.1 client to Windows NT?
I don't have an FPA license (and I never had a PWLMWNTCC04.01 license
because, at the time, I didn't need it) that will let that NT client
access PATHWORKS servers. My existing DOS CCS (PWLMDOSCC0n.0m) license
won't help, right? So do I have to buy an FPA license (because I want
client-based designated access license so I can access many PATHWORKS
servers - I don't have/want server-based/concurrent access licenses)?
Understandably this isn't likely to happen alot, but...
where do we send customers with such questions?
Paul
|
| 120.4 | | JAMIN::WASSER | John A. Wasser | Mon Feb 10 1997 16:56 | 11 |
| > My existing DOS CCS (PWLMDOSCC0n.0m) license won't help, right?
Wrong. The LM/DOS CCS (PWLMDOSCC05.00 et. seq.) license
includes all the rights of the PWLMXXXFP05.00 license. When
you install PATHWORKS 32, just configure the DEC LAN Manager
Licensing Agent to get a DEC-PWLMDOSCC05.00 instead of the
default DEC-PWLMXXXFP05.00.
Ask for 05.00 even if you don't think you have any... The
license server will give you a newer version if it has none
of the requested version.
|
| 120.5 | The move to NT is expected... | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Mon Feb 10 1997 19:19 | 20 |
| re: .3
Hmmm, but what happens when I upgrade that Win3.1 client to Windows NT?
.
.
.
Understandably this isn't likely to happen alot, but...
where do we send customers with such questions?
Actually, we expect that to happen quite a bit. Granted, in the next year or
so, most customers will still be moving up only to Win95, *but*, Mr. Bill needs
to collect more $'s from us each year so soon many of us will be led to believe
that we really *want* (need?) to upgrade to Windows NT.
Right now, however, this is *only* affecting 10's of thousands of our installed
base.
As John points out in .4, however, we have them covered.
John
|
| 120.6 | NVSL customers | DECPRG::PRSS2::csfr::markus | | Tue Feb 11 1997 06:07 | 16 |
| re .1 .2
Hi,
We have a lot of customers with NVSL contract for CCS licenses.
I would like to ask which license(s) will obtain customers with NVSL
contract for PW 6.0?
Will they get just
- a system license or
- system license and designated access license?
I wish that second point is correct.
Thanks
Jiri
|
| 120.7 | | VMSNET::P_NUNEZ | | Tue Feb 11 1997 08:33 | 8 |
| Jiri,
They'll get just the System license. Which is actually ok because if
you replaced your existing CCS licenses (in pwrk$license_manager) with
new FPA licenses, I think you'd have to visit each/every client
currently configured to obtain a CCS license...
Paul
|
| 120.8 | | JAMIN::WASSER | John A. Wasser | Tue Feb 11 1997 10:12 | 35 |
| > NVSL contract for CCS licenses.
> Which license(s) will customers with NVSL contract for PW 6.0 CCS
> licenses get?
>
> Will they get:
> - just a system license or
> - system license and designated access license?
>
> I hope it's the second one.
My understanding is that as a first upgrade they will get
only a V7.0 "System" (formerly CNS) licnese to allow them
to run PATHWORKS 32 and they will use their V6.0 CCS
license to continue to access their PATHWORKS servers.
I would expect that later they would be able to upgrade
their CCS licenses to V?.? "Designated Access" (formerly
FPA) licenses when they need new licenses to access
new PATHWORKS file servers. I don't think they will
need the new DA license until PATHWORKS V6.x for OpenVMS
ships.
Think of the CCS license as two separate licenses glued
together and it almost makes sense to upgrade the two
pieces separetely. It would make a little more sense
to me if the first upgrade was to:
V6.0 CCS -> V7.0 "System" + V5.0 FPA
Then the second upgrade would be:
V5.0 FPA -> V?.? "Designated Access"
As someone pointed out, that would require re-configuring
all of the client using CCS licenses (about 90% of sales).
|
| 120.9 | Please alert customers whenever possible... | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Tue Feb 11 1997 10:22 | 27 |
| re: .6 & .7
This conversation touches on an important point.
Customers who are used to using CCS licenses may, or more probably, will assume
that the new PATHWORKS 32 V7.0 system license is a full replacement for their
current license. As *we* all know, this is not the case.
The result may/will be that customer will be unloadling their old CCS licenses,
loading and registering their new System licenses, and expecting only good
things to happen. As *we* know, if they do this, good things will not happen!
We are including information with the new license *packages* and with the
licenses being sent to customers on MCS/SPS update services that document this
issue in much detail, but based on previous experience, customers will probably
not read this material or really understand it, and do the wrong thing.
Sooo, any chance you get to alert customers via any means you have that they
should *not* be discarding their current CCS licenses (yet), and should *not*
be expecting to use a PW32 Sys license like a CCS license, will certainly help
and be appreciated by all.
We did/do expect a few bumps along the way to PATHWORKS license simplification.
We don't like bumps, but we do like the end-point...and think that customers
will too.
John
|
| 120.10 | still not clear | DECPRG::PRSS2::praha::markus | | Tue Feb 11 1997 12:13 | 49 |
| re .7, .8
Paul and John,
> They'll get just the System license. Which is actually ok because if
> you replaced your existing CCS licenses (in pwrk$license_manager) with
> new FPA licenses, I think you'd have to visit each/every client
> currently configured to obtain a CCS license...
Maybe I do not quite understand technical point of view,
but I thought that default licenses which are asked by PW32 license
requester are PWxxWINAT07.00 (system - technically not neccessary) and
PWLMXXXFP05.00. If I will install new WIN95 client I will need those two
licenses. If I will be upgrading WIN9510A client to the PW 7.0 client I
would have to change default PWLMXXXFP05.00 to PWLMDOSCC06.00 to have
access to PW server. So it means that I have to change all client's
licenses as well. I think that the most of the big customers have theirs
CCS 6.0 licenses divided into smaller parts. They can than install new
licenses and uninstall the old ones just step by step. Correct me please if
I am wrong.
I fully agree with John W. that
> It would make a little more sense
> to me if the first upgrade was to:
> V6.0 CCS -> V7.0 "System" + V5.0 FPA
I think that there are also some questions concerning a "legal" part of the
whole operation.
1. Did the customers, who bought version 6.0 licences AND NVSL, bought also
right for the new designated access licenses?
If the answer is YES, they lost part of money they spent because PW 7.0
client will consume one CCS license just for the FPA part of it.
2. The NVSL contract could be still valid for PW 7.0 license. What the
continuing NVSL contract for the new license really means? Is it a right to
obtain
a. just a newer system license or
b. a newer system license and the right for a newer FPA license?
Thanks for answers
Jiri
|
| 120.11 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Feb 11 1997 14:10 | 18 |
| >requester are PWxxWINAT07.00 (system - technically not neccessary) and
>PWLMXXXFP05.00. If I will install new WIN95 client I will need those two
>licenses.
No, you'd need two licenses but not necessarily those two. You need a
license to use the new client software -- the PWxxwinat07.00, and a
license to access your PATHWORKS v5 servers, which can be a
PWLMXXXFP05.00 or the PWLMDOSCC06.00 you already were using before.
>1. Did the customers, who bought version 6.0 licences AND NVSL, bought also
>right for the new designated access licenses?
My understanding is "no", because the "Designated Access" license is
not really new, it's a renamed FPA
but then again, who am I to say? :-)
|
| 120.12 | is this really simpler? | TROOA::MSCHNEIDER | [email protected] | Sun Feb 16 1997 08:25 | 14 |
| I thought we were simplifying things? My assumption would have been
that CCS customers would get 2 new licenses.... PW32 and updated
designated access. Seems to me that is what they have now. CNS
customers on the other hand would only get only PW32. Howevever it
would appear that CCS and CNS customers get the same thing. Remember
that perception is reality.
Yes I understand they can use the 6.0 bits... but realize that most
people in the field (as witnessed at the recent Software Connectivity
Symposium) never figured out the old licensing scheme after many years
of use. Twists such as the CCS licensing updates will only continue to
confuse us. If the people in this notesfile can't get their head
around it then how do we expect our customers and sales people to get
it? Customer satisfaction issues are lurking around the corner.
|
| 120.13 | Change... | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Mon Feb 17 1997 09:46 | 27 |
| re: .12
"Simple" will always be a subjective term.
I think that we will all agree that any change will be a bit confusing at first.
We don't like this, but we expect this.
The first step in our "simplification" is to use one license for client software
and different licenses for server software. This means that when your client
software revs *and* you have subscribed to a service that gives you the license
to use the new software, you should expect to receive a new license for your
*client* software...not a license for your client software and **another**
license for your server software.
This also means that when your server software revs *and* you have subscribed to
a service that gives you the license to use this new software, you should expect
to receive a new license for your *server* software...not a license for your
server software and **another** license for your client software.
Admittedly it may be a bit confusing today because most folks (especially
Digital folks) never took the time in 3 years to understand what they licenses
for PATHWORKS provided. I can't undo or fix that. The best we can do is to
try to make future licensing terms as intuitive as possible.
In the meantime, the will be some bumps in the road.
John
|
| 120.14 | server 6.0 license | DECPRG::PRSS2::csfr::markus | | Tue Feb 18 1997 01:56 | 13 |
| re .13,
John,
my question is very simple but very important for our customers. Will
customer with CCS 6.0 license and NVSL get a new dessignated access license
to OpenVMS 6.0 server as a part of his NVSL contract when it will be
released?
Thanks for answer
Jiri
|
| 120.15 | Even better.. | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Tue Feb 18 1997 11:52 | 16 |
| re .14
Jiri,
My answer is also simple: Customers with NVLS on CCS (LAN Manager) licenses
will get a new(er) Client Access license for OpenVMS V6.0 ... when it is
released.
For more information on the Client Access license (available with V6.0) and
other PATHWORKS licensing matters, please refer to the recently released
PATHWORKS Business Practices Field Advisory Package
avaiable on VTX IR or WEB IR, published date 05-FEB-1997, DOC ID LI01PY.
John
|
| 120.16 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Tue Feb 18 1997 13:40 | 14 |
| > Customers with NVLS on CCS (LAN Manager) licenses
>will get a new(er) Client Access license for OpenVMS V6.0 ... when it
>is released.
Small nit, John, but CCS licneses were not tied to an OpenVMS server...
at what point will the DIGITAL UNIX server also require/accept the new
licenses? And if before the OpenVMS LM 6.0 server ships, would
customers get new licenses then?
Also note that customers who get the new CA licenses will need the new
license manager (in the OVMS v6 server, for example, and to be put into
a yet-to-be-named but probably 5.0F OVMS as well) to use them...
customers with old servers (including UNIX?) would be left in a lurch.
|
| 120.17 | | JAMIN::WASSER | John A. Wasser | Tue Feb 18 1997 15:18 | 11 |
| > For more information on the Client Access license (available with V6.0)
> and other PATHWORKS licensing matters, please refer to the recently
> released
>
> PATHWORKS Business Practices Field Advisory Package
>
> avaiable on VTX IR or WEB IR, published date 05-FEB-1997, DOC ID LI01PY.
At least VTX IR and WEB IR show only a Microsoft Word format.
How do I use OpenVMS to convert this file into something I can
read?
|
| 120.18 | | JAMIN::WASSER | John A. Wasser | Tue Feb 18 1997 16:23 | 788 |
| For those of us, like me, who don't have Microsoft Word, here is the document
in ASCII form. Note that some of the lines are VERY long and there were
two flowcharts that do not appear in the text version (I paraphrased them
in english).
-------------------------------------------------------------------------------
PATHWORKS BUSINESS PRACTICES
FIELD ADVISORY Version 1.0 January 31,1997
A) Introduction:
With the introduction of the PATHWORKS 32 client software in late February 1997,
significant PATHWORKS Business Practice changes will occur. A simpler licensing
scheme offering more flexibility will be initiated at that time, as will a more
competitive pricing program.
This Field Advisory has been created in an attempt to help the Field prepare for
the impact of these changes. It is a gathering of the information needed to
enable the Field to effectively support their customers and partners successful
migration to the new PATHWORKS Business Practices.
B) Background:
PATHWORKS has experienced ten years of success integrating disparate industry NOS
technology across DIGITAL customer enterprises. With our customers now desiring
to consolidate technologies
and integrate Windows 95 and Windows NT into their computing environments,
PATHWORKS provides a vital component to help them leverage their investment in
DIGITAL platforms. However, to
accommodate this paradigm shift, there are some licensing, packaging and pricing
changes which need to be implemented to help keep PATHWORKS a vital contributor
to customer enterprise integration solutions.
Therefore, with the February release of PATHWORKS 32 V7.0 client software, and
the upcoming release of PATHWORKS V6.0 for OpenVMS (Advanced Server) server
software, the necessary business practices changes will start to be implemented.
The changes are designed to satisfy Customer, Field and Business Partner
requirements, support DIGITAL's AllConnect Program and better support the future
direction of the PATHWORKS business by:
1) Reducing complexity of PATHWORKS licenses.
- One client license will cover all technologies except
MAC
- Significantly reduces the number (60%) of licenses
2) Offering more license flexibility
- Ability to move between desktop technologies
- Ability to change licensing style throughout the life
of the license
3) Implementing a Volume Discount Plan
- Based on specific increments of license
4) Introducing License Packages
- Upgrading is less cumbersome
5) Changing the license names to better reflect their functional
purpose, i.e. FPS becomes PC
Concurrent.
C) New License Names:
In February, PATHWORKS license type names will be changed to something more
closely resembling their function. The official corporate definitions and
explanations for PATHWORKS users are as follows:
1) CNS License changes to System (SYS) - "You may use the Software on the
specified
quantity (QTY) of computers." This means the customer is granted rights to
use one copy of
PATHWORKS client software on a single PC.
2) FPA License changes to Designated Access (DA) - " You May install the
Software on
multiple servers for access by the quantity of designated clients." This
means PATHWORKS
server software may be loaded on any number of servers for access by the
designated client.
3) FPS License changes to PC Concurrent (CU) - "You may install the Software
on one server
for concurrent access by the quantity of clients." Any number of
clients may have access to a
single PATHWORKS server not to exceed the quantity identified on the
PAK at any one
time.
4) New Client Access becomes available with the upcoming release of the server
software in Q4 - "You may install the Software on one server for
concurrent access by any
client, and/or on multiple servers for access by designated clients, for up
to the quantity of the
combination of all clients." Means this license allows the flexibility to
choose either PC
Concurrent or Designated Access use for each PATHWORKS license granted by
the PAK.
5) Upgrade (UPG) - "Extends the rights and restrictions of the
underlying license to a
subsequent version." " The Upgrade license(s) requires an
equal quantity of the underlying
license(s)."
D) Implementation:
PATHWORKS will implement license name and business practice changes in two
phases. Phase I will be
focused around the February release of PATHWORKS Client software and Phase II
tied to the upcoming release of PATHWORKS V6.0 for OpenVMS (Advanced Server)
server software. The changes mostly affect LAN Manager servers and Microsoft
clients.
Phase I - February 1997
New Client Software and License Introduction
The new PATHWORKS 32 client software will be released in February. It is a new
software kit consisting of Windows 95 and Windows NT host-connectivity code.
This software will be a follow on release for:
- PATHWORKS V1.0A for Windows 95
- PATHWORKS V4.1B for Windows NT
A new license, named PATHWORKS 32 V7.0 System license, will also be introduced at
this time. It will provide the rights to use PATHWORKS 32 V7.0 software as well
as any of the following products.
- PATHWORKS for DOS and Windows
- PATHWORKS for Windows NT
- PATHWORKS for OS/2.
CCS License Replaced by License Packages
In order to streamline our licensing practices and to clarify the rights each
license conveys, the popular yet complicated, CCS licenses have been retired. In
their place we have introduced license packages that simplify licensing PATHWORKS
products by providing one license that grants rights only to client software and
another license that grants rights only to server software. This change allows
customers to maintain their rights to those products of current interest to them
and to update their licenses only when the software that they are actually using
is updated.
This change, combined with the availability of the new PATHWORKS 32 V7.0 System
license, has the added benefit of actually shrinking the total number of
licenses and part numbers for PATHWORKS products. A table showing the migration
path for all PATHWORKS licenses is provided towards the end of this documents.
However, some examples of popular products and the packages that now replace them
include:
QM-0TLAA-A*, the PATHWORKS for DOS and Windows (LAN Manager) CCS license, is
replaced by QP-5LWAA-Ax , the Enterprise Integration Client for Microsoft
Windows license package
QM-2K5AA-A*, the PATHWORKS for Windows NT (LAN Manager) CCS license, is replaced
by QP-5LWAA-Ax, the Enterprise Integration Client for Microsoft Windows license
package
QM-YFWAA-A*, the PATHWORKS for OS/2 (LAN Manager) CCS license, is replaced by
QP-5LWAA-Ax, the Enterprise Integration Client for Microsoft Windows
license package
QM-0EKAA-A*, the PATHWORKS for DOS and Windows (NetWare) CCS license, is
replaced by QP-03WAA-Ax, the PATHWORKS License Package for NetWare
QM-YPHAA-A*, the PATHWORKS for Macintosh CCS license, is replaced by
QP-03YAA-Ax, the PATHWORKS License Package for Macintosh
These packages will include (minimally!):
a) A PATHWORKS 32 System license (or a Macintosh System license), and
b) A Designated Access (DA) license for the associated NOS (LAN Manager or
NetWare or
Macintosh).
***************************************************************************
* Big ugly flow chart which translates roughly to: *
* *
* If you need CCS (=FPA/DA+CNS/SYSTEM) capability, buy the package; *
* otherwise buy the individual licenses you need (some combination *
* of FPA/DA, FPS/CU and CNS/SYSTEM). *
* *
***************************************************************************
Phase II - Q4
With the release of PATHWORKS V6.0 for OpenVMS (Advanced Server) software in Q4,
additional license changes will occur:
a) A new PATHWORKS V6.0 (Advanced Server) Client Access license, that will replace
all licenses for our LAN Manager servers will be introduced. All other
licenses for that software
[ CU a.k.a. FPS & DA a.k.a. FPA (CCS eliminated in February)] will no
longer be offered at that
point.
Note: PC Concurrent licenses for PATHWORKS for NetWare server and Designated
Access licenses
for both PATHWORKS for NetWare and PATHWORKS for Macintosh servers
will still be
offered.
b) The Enterprise Integration Package will be updated to replace the Designated
Access license with
the new Client Access license. This package will minimally include:
- a PATHWORKS 32 System license, and
- a New Client Access license
***************************************************************************
* Another, smaller, ugly flow chart the translates roughly to: *
* *
* FPA/DA and FPS/CU are merged into "Client Access". *
* If you need both both the rights to run the PATHWORKS client *
* software and the rights to connect to PATHWORKS file servers, *
* buy the package; otherwise buy the individual licenses you need *
* (CA or SYSTEM). *
* *
***************************************************************************
E) End State of PATHWORKS Licensing Changes:
With the implementation of Phases I and II of the Business Practice changes, the
PATHWORKS product set licenses will be available in the following ways:
LAN Manager Environment
System License: Separate license providing the rights to use all
current PATHWORKS code for
DOS, Windows, Windows for Workgroups, Windows 95, Windows NT and OS/2.
Client Access License: Simultaneously conveys the same rights as the
Designated Access and PC
Concurrent licenses.
Enterprise Integration Client License Package: Contains PATHWORKS 32
V7.0 System
License, PATHWORKS Client Access license, TeamLinks Mail for Windows
license, and Mapi
Driver for ALL-IN-1 license. This package is the migration path for the
PATHWORKS LAN
Manager CCS license.
Novell Environment
System License: Separate license providing the rights to use all
current PATHWORKS code for
DOS, Windows, Windows for Workgroups, Windows 95, Windows NT and OS/2.
Designated Access License: Separate license providing guaranteed access
to multiple
PATHWORKS servers providing NetWare services.
PC Concurrent License: Provides access to a single server for the
quantity of clients indicated on a
concurrent basis.
PATHWORKS License Package for NetWare: This package consists of
PATHWORKS
(NetWare)Designated Access license and a PATHWORKS 32 V7.0 System
license. It is the
replacement for PATHWORKS (NetWare) CCS licenses.
Apple Environment:
System License: Separate license providing the rights to use PATHWORKS
code for Macintosh.
Designated Access License: Separate license providing guaranteed access
to multiple
PATHWORKS servers providing Appleshare services.
PATHWORKS License Package for Macintosh: This package consists of
PATHWORKS for
Macintosh Designated Access license and a PATHWORKS for Macintosh
System license. It is the
migration path for PATHWORKS for MAC CCS license.
F) Volume Discount:
With the release of PATHWORKS 32 in February, a volume discount will be
introduced. It is designed to make PATHWORKS prices more competitive for end
users. The introduction of this volume discounting has rendered Exact Quantity
PAKs (EQPs) impractical for initial license sales. In their place are license
increments designed to match PATHWORKS historical buying behavior. They range
from 1 unit to 1,000 units with volume discounts for some products ranging as
high as 70% over unit=1 prices.
The increment PAKS are non splitable and can be loaded on only one server and
should be ordered accordingly. The volume discount plan is very aggressive and
should contribute to the ease of selling PATHWORKS.
G) Upgrades:
Upgrade licenses will remain flat-priced and since they are already highly
discounted, the prices will remain unchanged. They will be purchasable in EQPs or
in increments.
H) Update Services:
Rights to new version services
With the release of PATHWORKS 32 V7.0 in February of 1997, a new System license
will be shipped to those PATHWORKS customers presently under service contracts
for rights to new versions to DOS and Windows NT or OS/2 versions of CNS, CCS
licenses.
When the PATHWORKS V6.0 for OpenVMS (Advanced Server) software ships in Q4, new
Client Access licenses will be shipped to all customers under rights to new
version contract for LAN Manager server licenses (CCS,FPA/Designated Access or
FPS/PC Concurrent).
Note: For customers wishing to purchase rights to new version update service for,
Enterprise Integration Client License Package,
PATHWORKS License Package for NetWare,
PATHWORKS License Package for Macintosh,
contracts will only be offered on the components of the packages.
Kit Update Service
With the release of PATHWORKS 32 V7.0 in February of 1997, a new Hkit
(QA-5LKAA-H8) will be shipped to all customers presently under Kit Update Service
for PATHWORKS for DOS/Windows and Windows NT (QT-0TLAAE* or QT-2K5AA-E*).
When the PATHWORKS V6.0 for OpenVMS (Advanced Server) software ships in Q4,
customers under Kit Update Service for PATHWORKS for Open VMS LAN Manager servers
will be sent new Hkits. This will give customers the licensing software to use
the new Client Access license with the new PATHWORKS V6.0 for Open VMS (Advanced
Server). The new Client Access license allows the customer to utilize his server
licenses in either concurrent or designated mode. Version 5.0 of PATHWORKS for
Open VMS LAN Manager servers will be updated to use the new Client Access
license which will be the only license sold for LAN Manager servers.
I) Resources:
Internal
PATHWORKS 32 notes file jamin::pathworks32
PATHWORKS 32 web site
http://sack.lkg.dec.com/http/humnbird/index.htm
PATHWORKS 32 file service \\lanmgr\specs\projects\humnbird
PATWORKS Business Practices Sales Update http://prodmgt.lkg.dec.com
PATHWORKS 32 Sales Update http://prodmgt.lkg.dec.com
External
PATHWORKS InforCenter
http://www.digital.com/info/pathworks
PTHWORKS 32 V7.0 SPD 56.53
Trademarks:
Novell and NetWare are registered trademarks of Novell, Inc. Microsoft is a
registered trademark. Windows, Windows NT, MS DOS, Windows 3.1, Windows 3.11
(Windows for Workgroups), and Windows 95 are trademarks of Microsoft Corporation.
IBM and OS/2 are registered trademarks of International Business Machines, Inc.
PowerTerm is a registered trademark of ERICOM Software Ltd.
Q&A
PATHWORKS BUSINESS PRACTICES
1) Q: Why is Digital changing the PATHWORKS Licensing scheme?
A: The licensing of PATHWORKS products has been streamlined and simplified
to reflect
customer feedback and suggestions. The changes make it even easier for
customers to use
PATHWORKS software in a continually evolving environment.
2) Q: It seems the price of PATHWORKS licensing has changed. Why is that?
A: Yes indeed , PATHWORKS licensing has changed. With the introduction
of the
PATHWORKS volume discount, customers can now purchase
PATHWORKS licenses for
up to 70% off of previous license prices.
3) Q: Given the PATHWORKS licenses are now sold in increments,
can I buy 75 licenses at the
same price as 50?
A: No. It will be necessary for a customer to buy a 50 license PAK and
a 25 license PAK at
there respective discounted prices.
4) Q: Can I still buy Exact Quantity PAKs (EQPs) ?
A: For initial sales, volume discounted part numbers have replaced
EQPs. However, EQPs
continue to be used for customers wanting to Upgrade
existing EQP PAKs.
5) Q: I have been satisfied buying CCS licenses, why are you retiring them?
A: The CCS licenses have traditionally granted rights to use client
software and rights to server
access. These rights have been split into two separate
licenses with the introduction of
PATHWORKS 32. This change allows more flexibility for our
customers whereby
upgrading the client or server are not tied to one another.
If, however, you wish to purchase
the dual rights, we have created license packages containing
both client and server licenses
which is completely replace the rights provided by the CCS
license.
6) Q: Now that I have PATHWORKS 32 licenses, do these replace my
existing CCS license?
A: No, the PATHWORKS 32 license replaces the rights pertaining to the client
software
component of the CCS license. It does not provide rights to
access server software.
7) Q: Now that you have retired CCS licenses, do I have to buy Designated
licenses to access
PATHWORKS servers?
A: No, the CCS license you now hold will continue to be valid for
access to your current
servers. However, if you add clients, you will need to buy a
license to access your server.
8) Q: Do I need a new license when the PATHORKS V6.0 for OpenVMS (Advanced
Server)
ships?
A: Yes, when the PATHWORKS V6.0 for OpenVMS (Advanced Server) software
ships in
Q4 of this year, a new PATHWORKS license will be required.
It is at this time that the
new Client Access license will be introduced offering
customer selectable Concurrent or
Designated access use.
9) Q: When I install PATHWORKS 32, will I have to use License Management
for my clients?
A: No, as with previous PATHWORKS client software, PATHWORKS 32
software license
is not license managed.
10) Q: Since you have done away with the CCS licenses, what do I now buy
if I want
to use PATHWORKS client software and access to PATHWORKS
servers?
A: You would purchase the Enterprise Integration Client License
Package for LAN
Manager environments, the PATHWORKS License Package for
NetWare for Novell
environments, or PATHWORKS License Package for Macintosh for
Apple environments.
11) Q: I understand the Enterprise Integration Client is a replacement
for the CCS LAN Manager
license but is there any way I can purchase equivalent
rights without
including the rights to TeamLinks and the MAPPI driver?
A: Yes, the purchase of PATHWORKS 32 V7.0 System license and
a PATHWWORKS 5.0
(LAN Manager) Designated Access license will provide
the equivalent rights to the
obsoleted CCS license. However, it is less costly to
purchase these licenses via the license
package.
12) Q: Will I be able to buy kit update services and/or rights to new
version services for the new
Enterprise Integration License Package?
A: No, continuing with our theme of flexibility, rather than
purchasing these services for the
package itself, you may purchase these services for each of
the individual products within
the package.
13) Q: Can a reseller now buy PATHWORKS licenses in units of 1K
and sell them in smaller
numbers of license units?
A: No, PATHWORKS volume discounting has been put in place to create
greater incentive
for end users to purchase PATHWORKS
14) Q: Why are you not discounting the PATHWORKS Upgrade part numbers?
A: PATHWORKS Upgrades have always carried a substantial discount and
we will continue
to offer the same discount.
15) Q: I have PATHWORKS for DOS/Windows CCS today, can I migrate to
PATHORKS 32 ?
How and at what cost?
A: You can easily migrate to PATHWORKS 32 by purchasing the necessary
media,
documentation and PATHWORKS 32 Upgrade license(s). Since
PATHWORKS 32 is an
Upgrade only for your client, your present CCS license
continues to be valid for server
access and should be maintained until the next PATHWORKS
server release. The cost of the
PATHWORKS 32 Upgrade license is $99 per license.
16) Q: I have rights to new version and kit update services for
PATHWORKS for DOS and
Windows. Are these services changed to PATHWORKS 32
automatically by Digital? Is
there any action required on my part?
A: You are not required to change your service contract. Digital
will ship PATHWORKS 32 software and license(s) to you automatically.
17) Q: I just want to use eXcursion. Do I need to install the PATHWORKS
32 license requestors on
the desktop or any PAKs on the server?
A: No, eXcursion is a component of PATHWORKS 32 and as with all
PATHWORKS client
software, it is not license managed. Therefore, there is no
need to install licensing software.
18) A: When eXcursion was sold separately, it required licenses for each
supported language. What
is the PATHWORKS 32 policy?
B: All language variants of all components of PATHWORKS 32 are covered
by the
PATHWORKS 32 license.
19) Q: What effect will the elimination of the CCS license have on my
computing operations?
A: The elimination of the CCS license will not impact your current
clients and servers.
However, if you add additional clients using PATHWORKS
client software, you may need to
configure your clients differently to use the new server
licenses. See the cover letter included
with the new license packages for details.
20) Q: Once I have purchased a PATHWORKS license PAK containing a
certain number of
licenses, can I change or adjust that PAK to multiple PAKs?
A: No, with the implementation of the volume discount, PATHWORKS
licenses will be
sold in non adjustable increments.
Availability and Ordering
The new pricing is available February, 1997.
Order No. Description U.S. List
PATHWORKS 5.0 (LAN Manager) Designated Access
QM-2CLAA-AB 1 LIC $129
QM-2CLAA-AC 10 LIC $990
QM-2CLAA-AD 25 LIC $2200
QM-2CLAA-AE 50 LIC $3750
QM-2CLAA-AF 100 LIC $5625
QM-2CLAA-AG 250 LIC $12500
QM-2CLAA-AH 500 LIC $18750
QM-2CLAA-AJ 1000 LIC $30000
Order No. Description U.S. List
PATHWORKS 5.0 (NetWare) Designated Access
QM-2CMAA-AB 1 LIC $149
QM-2CMAA-AC 10 LIC $1050
QM-2CMAA-AD 25 LIC $2450
QM-2CMAA-AE 50 LIC $4500
QM-2CMAA-AF 100 LIC $8250
QM-2CMAA-AG 250 LIC $18750
QM-2CMAA-AH 500 LIC $33750
QM-2CMAA-AJ 1000 LIC $60000
Order No. Description U.S. List
PATHWORKS 1.3 (Macintosh) Designated Access
QM-0EAAA-AB 1 LIC $149
QM-0EAAA-AC 10 LIC $1050
QM-0EAAA-AD 25 LIC $2450
QM-0EAAA-AE 50 LIC $4500
QM-0EAAA-AF 100 LIC $8250
QM-0EAAA-AG 250 LIC $18750
QM-0EAAA-AH 500 LIC $33750
QM-0EAAA-AJ 1000 LIC $60000
Order No. Description U.S. List
PATHWORKS 5.0 for DIGITAL UNIX LM PC Concurrent
QM-2CPAA-AB 10 LIC $990
QM-2CPAA-AC 25 LIC $2200
QM-2CPAA-AD 50 LIC $3750
QM-2CPAA-AE 100 LIC $5625
QM-2CPAA-AF 250 LIC $12500
Order No. Description U.S. List
PATHWORKS 5.0 for OpenVMS LM PC Concurrent
QM-A93AA-AB 10 LIC $990
QM-A93AA-AC 25 LIC $2200
QM-A93AA-AD 50 LIC $3750
QM-A93AA-AE 100 LIC $5625
QM-A93AA-AF 250 LIC $12500
Order No. Description U.S. List
PATHWORKS 32 7.0 System
QM-5LKAA-AB 1 LIC $249
QM-5LKAA-AC 10 LIC $1750
QM-5LKAA-AD 25 LIC $3750
QM-5LKAA-AE 50 LIC $6850
QM-5LKAA-AF 100 LIC $12450
QM-5LKAA-AG 250 LIC $28000
QM-5LKAA-AH 500 LIC $49800
QM-5LKAA-AJ 1000 LIC $87150
Order No Description U.S. List
PATHWORKS 32 V7.0 Upgrade
QM-5LKAA-CA 1 User
License * 99
QM-5LKAA-CB 1 User
License ** 99
QM-5LKAA-CC 10 User
Licenses 990
QM-5LKAA-CD 25 User
Licenses 2475
QM-5LKAA-CE 50 User
Licenses 4950
QM-5LKAA-CF 100 User
Licenses 9900
QM-5LKAA-CG 250 User
Licenses 24750
QM-5LKAA-CH 500 User
Licenses 49500
* QM-5LKAA-CA allows multiple licenses per PAK (specifies exact quantity in
the PAK) .
** QM-5LKAA-CB allows one license per PAK.
Order No. Description U.S. List
PATHWORKS 1.3 for Macintosh System
QM-0EEAA-AB 1 LIC $ 249
QM-0EEAA-AC 10 LIC $1750
QM-0EEAA-AD 25 LIC $3750
QM-0EEAA-AE 50 LIC $6850
QM-0EEAA-AF 100 LIC $12450
QM-0EEAA-AG 250 LIC $28000
QM-0EEAA-AH 500 LIC $49800
QM-0EEAA-AJ 1000 LIC $87150
Order No. Description U.S. List
Digital Enterprise Integration Client License Package
QP-5LWAA-AB 1 User License Package $315
QP-5LWAA-AC 10 User License Package $2500
QP-5LWAA-AD 25 User License Package $5550
QP-5LWAA-AE 50 User License Package $9650
QP-5LWAA-AF 100 User License Package $16450
QP-5LWAA-AG 250 User License Package $37700
QP-5LWAA-AH 500 User License Package $66100
QP-5LWAA-AJ 1000 User License Package $119800
Order No. Description U.S. List
PATHWORKS License Package for NetWare
QP-03WAA-AB 1 User License Package $315
QP-03WAA-AC 10 User License Package $2225
QP-03WAA-AD 25 User License Package $4950
QP-03WAA-AE 50 User License Package $9075
QP-03WAA-AF 100 User License Package $16550
QP-03WAA-AG 250 User License Package $37400
QP-03WAA-AH 500 User License Package $66850
QP-03WAA-AJ 1000 User License Package $117725
Order No. Description U.S. List
PATHWORKS License Package for Macintosh
QP-03YAA-AB 1 User License Package $315
QP-03YAA-AC 10 User License Package $2225
QP-03YAA-AD 25 User License Package $4950
QP-03YAA-AE 50 User License Package $9075
QP-03YAA-AF 100 User License Package $16550
QP-03YAA-AG 250 User License Package $37400
QP-03YAA-AH 500 User License Package $66850
QP-03YAA-AJ 1000 User License Package $117725
PATHWORKS License Migration
Today's License
License in 2/97
Licenses in Q4/97
DOS/Win, OS/2, WinNT CNS licenses: QM-2CNAA-A* or QM-2K6AA-A* or QM-36EAA-A*
PATHWORKS 32 System license QM-5LKAA-A*
PATHWORKS 32 System license QM-5LKAA-A*
DOS/Win, OS/2, WinNT CCS/LM lics: QM-0TLAA-A* QM-2K5AA-A* QM-YFWAA-A*
Enterprise Integration Client Lic. Pkg. QP-5LWAA-A* QM-5LKAA-A*, QM-2CLAA-A*
QM-0N18A-A* and QM-5KEAA-A* Enterprise Integration Client Lic. Pkg.
QP-5LWAA-A* QM-5LKAA-A*, New Client Access license, QM-0N18A-A*, and QM-5KEAA-A*
DOS/Win, OS/2, WinNT CCS/NW lics: QM-0EKAA-A* QM-506AA-A*
PATHWORKS NetWare Client Lic. Pkg. QP-03WAA-A* QM-5LKAA-A* and QM-2CMAA-A*
PATHWORKS NetWare Client Lic. Pkg. QP-03WAA-A*
QM-5LKAA-A* and QM-2CMAA-A*
V5.0 FPA (LAN Manager) license QM-2CLAA-A*
V5.0 DA (LAN Manager) license QM-2CLAA-A*
New Client Access license QM-?2?AA-A*
V5.0 FPA (NetWare) license QM-2CMAA-A*
V5.0 DA (NetWare) license QM-2CMAA-A*
V5.0 DA (NetWare) license QM-2CMAA-A*
OVMS & UNIX V5.0 FPS/LM licenses: QM-A93AA-A* or QM-2CPAA-A*
OVMS & UNIX 5.0 CU/LM licenses: QM-A93AA-A* or QM-2CPAA-A*
New Client Access license QM-?2?AA-A*
OpenVMS & UNIX FPS/NW licenses: QM-0ENAA-A* or QM-3Q1AA-A*
OpenVMS & UNIX CU/NW licenses: QM-0ENAA-A* or QM-3Q1AA-A*
OpenVMS & UNIX CU/NW licenses: QM-0ENAA-A* or
QM-3Q1AA-A*
PATHWORKS Macintosh CCS licenses: QM-YPHAA-A*
PATHWORKS Macintosh Client Lic. Pkg. QP-03YAA-A* QM-0EEAA-A* and QM-0EAAA-A*
PATHWORKS Macintosh Client Lic. Pkg. QP-03YAA-A*
QM-0EEAA-A* and OM-0EAAA-A*
PATHWORKS Macintosh FPA licenses: QM-0EAAA-A*
PATHWORKS Macintosh DA licenses: QM-0EAAA-A*
PATHWORKS Macintosh DA licenses: QM-0EAAA-A*
PATHWORKS License Migration
Today's NVLS Action Needed in 2/97 Action Needed in Q4/97
DOS/Win, WinNT CNS services: QT-2CNAA-T* or QT-2K6AA-T* or QT-36EAA-T*
Will send PATHWORKS 32 System license to all QM-5LKAA-A* None
DOS/Win, OS/2, WinNt CCS/LM lics: QT-0TLAA-T* or QT-2K5AA-T* or QT-YFWAA-T*
Will send PATHWORKS 32 System license to all QM-5LKAA-A* Will send New
Client Access licenses to all QM-?2?AA-A*
DOS/Win, OS/2, WinNT CCS/NW lics: QT-0EKAA-T* or QT-506AA-T*
Will send PATHWORKS 32 System license to all QM-5LKAA-A* None
V5.0 FPA (LAN Manager) license QT-2CLAA-A*
None Will send New
Client Access license to all QM-?2?AA-A*
V5.0 FPA (NetWare) license QT-2CMAA-T*
None None
OVMS & UNIX V5.0 FPS/LM licenses: QT-A93AA-T* or QT-2CPAA-T*
None Will send New
Client Access license to all QM-?2?AA-A*
OpenVMS & UNIX FPS/NW licenses: QT-0ENAA-T* or QT-3Q1AA-T*
None None
PATHWORKS Macintosh CCS licenses: QT-YPHAA-T*
None None
PATHWORKS Macintosh FPA licenses: QT-0EAAA-T*
None None
Shaded area indicates an action required
PATHWORKS Kit Migration
Today's MDDS Action Needed in
2/97 Action Needed in Q4/97
DOS/Win, WinNT MDDS services: QT-0TLAA-E* or QT-2K5AA-E* Will send
PATHWORKS 32 Hkit to all QA-5LKAA-H8 None
FPA-kit MDDS QT-2CLAA-E* Will send new
QA-2CLAA-HC kit Will send new QA-2CLAA-HC kit
OpenVMS MDDS: QT-A93AA-E* None
Will send new QA-A93AA-H* kit
UNIX MDDS: QT-2CPAA-E* None
Will send new QA-2CPAA-H* kit
Shaded area indicates an action required
|
| 120.19 | Lots of prep needed before CA's debut... | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Tue Feb 18 1997 20:30 | 33 |
| re: .16
Ahhhh UNIX....
If all goes according to the script, the good folks in the UNIX group would
mirror the activities in the OpenVMS group. We'd ask them to lead, but they
seem to have an aversion to leading in this particular area.
Once the dust settles with these new changes, and I get a bit of rest, we'll
try to get a definitive statement from the UNIX folks on their plans for the
future. Until then, the default plan is to assume that they will be ready
when OpenVMS is to adopt the new CA licenses.
---
Note that customers with new CA licenses will need more than just a new License
Server to take full advantage of these licenses. In particular, customers will
need new License Registrars in any server that will use these licenses for
concurrent-use access, and most customers will need new License Registrars to
even use these new CA licenses for client-based access.
It is no small nit. We will need to start educating customers about the
requirements, as well as the rewards, of these new licenses soon, and will
also need to begin the roll-out of software to support these new licenses
well before they finally replace today's Designated Access (old FPA) and
PC Concurrent (old FPS) licenses.
But first, we need to insure that folks understand the change the just
happened on February 3rd and need to insure that customers have all the info
they require to keep their systems running until the next change occurs.
John
|
| 120.20 | Between a rock and a hard-place! | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Tue Feb 18 1997 20:33 | 10 |
| re: .17
John! We really need to bring you into the 20th Century...before it ends!!!
(...no WORD???)
I'll covert this file to a .PS file if there is enough interest. Of course,
I'm not sure that those without access to MS Word have access to a PostScript
printer!
John
|
| 120.21 | but .... | WOTVAX::16.194.208.3::warder.reo.dec.com::sharkeya | Who am I now ? | Wed Feb 19 1997 04:30 | 8 |
| Umm - I have a new PW customer who has unix servers. Can he still buy the
old (CCS) style licenses ?
If not, how can I sell him things ? (the PW stuff is a vital part of a
larger bid)
Alan
|
| 120.22 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Wed Feb 19 1997 07:52 | 11 |
| .21
Alan,
You sell them a PW32 SYSTEM license for each of their clients that want
to run PATHWORKS client software (be it DOS,Win,WfW,95,NT, or OS/2) and
either a DESIGNATED ACCESS (nee FPA) for each of their clients that want
access to PATHWORKS SERVERS or a PC CONCURRENT (nee FPS) license for
each of the servers to which clients want access. Simple, no?
|
| 120.23 | ccs = #123 pw lice package = #306 ? | KERNEL::BURNST | | Wed Feb 19 1997 12:54 | 16 |
| Alan I dont think so...
But I'll let john answer for define as I only came here because I have
a simmilar but differnet query.
Cust has pw vms systems and wfw clients running PW v6.
Cust has slowly being adding more users ie QM-0TLAA-AA (ccs license to
us techies.) These were uk list #123 pounds.
Cust now has added some more wfw clients and want another ccs license.
Unfortunatly these are EOL so cust no must buy a Inetgrated client
license package (OK so far I think) ie QP-5LWAA-AB UK LIST PRICE
#306.00 pounds. Almost a 300% increase in price to add 1 more wfw
client.
If he doesnt use ANY PW s/w then yes a designated access license will
be cheaper.
Is this right and how does $315 us = #306 UK pounds ?.
Are we trying to price PW out ot the market !!!!.
Trev UK CSC.
|
| 120.24 | Is this any way to do business ? | WOTVAX::16.194.208.3::warder.reo.dec.com::sharkeya | Who am I now ? | Wed Feb 19 1997 15:15 | 7 |
| All the customer wants is 30 CCS licenses. I thought this was supposed to
be simple ?
If the server cannot recognise the new ones anyway, what is the point ?
Alan
|
| 120.25 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Wed Feb 19 1997 15:43 | 9 |
| the server can recognise the currently available license; my earlier
comments to John were about the future - ignore them for now.
as for cost, there are (in $US anyway) quantity discounts that did not
exist before which bring the cost for an Integrated Kit down under the
old CCS if you purchase 50 or more -and- you now get capabilities you
didn't have before; the right to run PATHWORKS 32 which includes
eXcursion and PowerTerm, and the right to use Teamlinks and the right
to use the All-in-One MAPI Driver
|
| 120.26 | Replies to .21, .23, .24 | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Wed Feb 19 1997 16:29 | 94 |
| Simple is a relative and subjective term...
re: .21
Umm - I have a new PW customer who has unix servers. Can he still buy
the old (CCS) style licenses ?
If not, how can I sell him things ? (the PW stuff is a vital part of a
larger bid)
Alan
Since when was the nature of the OS of the server platform (OpenVMS or UNIX or
ULTRIX or SCO) a consideration when buying a client-based access license?
As per the Sales Updates, the most direct replacement for CCS licenses are now
license *packages*:
QP-5LWAA-xx provides a replacement alternative for QM-0TLAA-xx, or
QM-2K5AA-xx, or
QM-YFWAA-xx
QP-03WAA-xx provides a replacement alternative for QM-0EKAA-xx, or
QM-506AA-xx
QP-03YAA-xx provides a replacement alternative for QM-YPHAA-xx
Alternatively, they could consider Steve's suggestions in .22, but those choices
will be, in general, more expensive.
----
re: .23
Alan I dont think so...
But I'll let john answer for define as I only came here because I have
a simmilar but differnet query.
Cust has pw vms systems and wfw clients running PW v6.
Cust has slowly being adding more users ie QM-0TLAA-AA (ccs license to
us techies.) These were uk list #123 pounds.
Cust now has added some more wfw clients and want another ccs license.
Unfortunatly these are EOL so cust no must buy a Inetgrated client
license package (OK so far I think) ie QP-5LWAA-AB UK LIST PRICE
#306.00 pounds. Almost a 300% increase in price to add 1 more wfw
client.
If he doesnt use ANY PW s/w then yes a designated access license will
be cheaper.
Is this right and how does $315 us = #306 UK pounds ?.
Are we trying to price PW out ot the market !!!!.
Trev UK CSC.
Trev,
I can not explain how a $315 US$ price gets translated into a #306 UK pounds
price. Please try questioning up your chain and I'll try my contacts (note that
I can not see the price files for any country but the US and have little say in
what is ultimately charged...)
The price changes made *should* result in *savings* for customers over the
old price scheme *if* customers adjust their buying habits to purchase their
licenses in modest numbers at any one time. Think about it, customers have
always done this for our FPS licenses which have incorporated volume discount
pricing from the start.
Customers asked us to implement this model for our other licenses, and we have
responded.
However, I'd agree, a 300% increase...even for unit=1, is not reasonable.
John
----
re: .24
All the customer wants is 30 CCS licenses. I thought this was supposed to
be simple ?
See reply to .21. Please let me know if this is "simple" as you define it.
If it is not, please try to identify the complexity...as *you* see it. I need
your vantage point to make things simpler.
If the server cannot recognise the new ones anyway, what is the point ?
As Steve clarified in .25, this is not an issue. The licenses that we sell
today work with the related servers we sell today. All is well with the world!
Thanks for your considered feedback,
John
|
| 120.27 | Today's price for QP-5LW is a BUG | EVTAI1::ROUX_P | Software Mktg France | Thu Feb 20 1997 04:52 | 12 |
| re to .23
Trev,
I noticed this problem in the french price file too. I escalated it to
the european Pricing Manager. The issue is that the QP-5LW has been
set a wrong family code (D1J) instead of C1H (which the default family
code for ALL PWKS products).
As you noticed, D1J is *MUCH* higher than C1H.
This problem WILL be corrected in the upcoming PACS addendum (March 3)
In the meantime, you should ask you local Mktg person (John WHITELEY ?)
to point-price the 8 QP-5LW references, as I did in France.
|
| 120.28 | can we make sure the FPA issue is solved | EVTAI1::ROUX_P | Software Mktg France | Thu Feb 20 1997 05:01 | 17 |
| This one if for John 8-)
"Customers with NVLS on CCS (LAN Manager) licenses
will get a new(er) Client Access license for OpenVMS V6.0 ... when it
is released"
If I understand right, you can't replace the integrated FPA (now DA)
included in the "old" CCS by a Concurrent PC on the server.
The UNIX issue has already been raised in the previous replies.
What if a customer has 80 servers (I know one french customer like
this), will we have to "offer" 80 times a PC-concurrent licences on
behalf of his NVLS contract ?
It should be wiser to "offer" the Designated Access to alleviate this
issue (how many servers does a PC access, how can Digital prove that
what the customer will claim for too many Client Access, and so on)
Best regards from pAris,
Philippe
|
| 120.29 | | JAMIN::WASSER | John A. Wasser | Thu Feb 20 1997 10:26 | 30 |
| > This one is for John 8-)
Which John?
> If I understand right, you can't replace the integrated FPA (now DA)
> included in the "old" CCS by a Concurrent PC on the server.
As far as I know there has NEVER been a way of swapping
an FPA license for an FPS license. I don't think that will
change just because FPA is now called "Designated Access" and
FPS is now called "PC Concurent".
In the past I don't think there was even a way of converting
a CCS license to separate CNS and FPA licenses. Now there
is.
When the license simplification is over, converting between
FPA/DA licenses and FPS/PCC licenses will be a moot point
because the "Client Access" license replaces both.
> What if a customer has 80 servers, will we have to "offer" 80 times a
> PC-concurrent licences on behalf of his NVLS contract?
I think they will only get "PC Concurrent" (nee FPS) licenses
if they have NVLS for FPS licenses. If they have NVLS for FPA
or CCS licenses they will get "Designated Access" (nee FPA)
licenses.
See the charts at the bottom of reply 18 to see what the NVLS
path is for each current license type.
|
| 120.30 | reply from JohnG | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Thu Feb 20 1997 13:48 | 65 |
| re: .28
I'll add my 2 bits (or bytes) as "the other John", or JohnG...
"Customers with NVLS on CCS (LAN Manager) licenses
will get a new(er) Client Access license for OpenVMS V6.0 ... when it
is released"
If I understand right, you can't replace the integrated FPA (now DA)
included in the "old" CCS by a Concurrent PC on the server.
The UNIX issue has already been raised in the previous replies.
What if a customer has 80 servers (I know one french customer like
this), will we have to "offer" 80 times a PC-concurrent licences on
behalf of his NVLS contract ?
It should be wiser to "offer" the Designated Access to alleviate this
issue (how many servers does a PC access, how can Digital prove that
what the customer will claim for too many Client Access, and so on)
Best regards from pAris,
Philippe
Though I'll admit that I'm not sure that I understand your question, I'll
answer it as follows:
When a customer with NVLS for CCS/LAN Manager licenses get updated
with new "Client Access" licenses, that customer will receive a
number of "Client Access" licenses that is equal to the number of
CCS licenses under contract. If the customer has 200, the customer
will receive 200 "Client Access" licenses. No more, no less.
The customer *will* be able to use these 200 licenses as Designated
Access licenses and/or as PC Concurrent.
If they are all used as Designated Access licenses, then the usage
model remains as it was with CCS licenses; each of 200 clients gets
its own key an each is enabled to use any PATHWORKS V6.0 (or earlier)
(LAN Manager [...or Advanced Server]) server.
If some/all of these 200 licenses are used as PC Concurrent licenses,
then their usage model will completely change and they will need to
determine exactly how many of these 200 licenses they will assign to
each server they want to use. Once they determine that, they'll need
a PAK for *each* server.
So, if they have 10 servers that they want to use, they'll need 10 PAKs
with, for example, 20 licenses each. If they have 80 servers, then
they'd need 80 PAKs with about 1-3 licenses each!
Bottom line is that when FPA and FPS licenses are upgraded to "Client
Access" licenses, customers do *not* get *more* licenses. However,
they will have the choice to use those licenses using either usage
model.
This model follows the Microsoft "client access license" model except
for a couple of key difference:
a) In our model, both the "concurrent use" model and "per seat" model
can be used on a single system without penalty. In the Microsoft
model, your server can use only 1 model.
b) In our model, you can switch from "concurrent use" to "per seat"
and back again, as often as you'd like; the customer chooses. In the
Microsoft model, once your switch from "concurrent use" to "per seat"
you can not switch back again.
John
|
| 120.31 | can anyone fill the gaps or add extras | KERNEL::BURNST | | Fri Feb 21 1997 10:18 | 40 |
|
Can somebody help fill in the following table to try and help me now
understand how to get these licenses working with CURRENT SHIPPING
PW versions. (Lets just stick with Lm for starters)
License Replaces
(right to use PW software on a client.)
System License CNS
PWXXWINAT07.00 ???????????
QM-5LKAA-Ax QM-2CNAA-A1
(Right to access files / print to a PW server)
Designated Access FPA
?????????????? PWLMXXXFP05.00
QM-2CLAA-AB QM-2CLAA-A1
(Right to access servers and use PW software)
Integrated Client Access CCS
?????????????? PWLMDOSCC06.00
QP-5LWAA-Ax QM-0TLAA-A1
(Server Based Licenses)
PC Conncurrent FPS
?????????????? PWVMSCU05.00
QM-A93AA-Ax QM-A93AA-Ax
As Iam typing this out it slowly dawning that there a lot of new names
but I think the LMF codes will be the same....
I also have noticed on the sheet that there are no new Pathworks VMS /
UNIX NETWARE concurrent part Nos or names. Is this because we should just
continue to use the old ones of both. (names and Part nos).
So the only major change is the new Integrated license which I will
wait to see the LMF code if anybody can fill out the ????? gaps please.
Trev UK CSC (Where the first call on a new PWXXWINAT07.00 replacing a
CCS licnese on his NT Client failed to connect to his server
AAAHHHHHH!)
|
| 120.32 | | JAMIN::WASSER | John A. Wasser | Fri Feb 21 1997 11:40 | 27 |
| The only one I know the PAK for is the old
PWXXWINAT07.00=QM-5LKAA-Ax (PATHWORKS 32 System License) replaces:
PWXXDOSAT05.00 PATHWORKS V5.0 for DOS and Windows CNS
PWXXDOSAT05.01 PATHWORKS V5.1 for DOS and Windows CNS
PWXXDOSAT06.00 PATHWORKS V6.0 for DOS and Windows CNS
PWXXWNTAT04.01 PATHWORKS V4.1 for Windows NT CNS
and also replaces the CNS half of:
PWLMDOSCC05.00 PATHWORKS V5.0 for DOS and Windows LM/CCS
PWLMDOSCC05.01 PATHWORKS V5.1 for DOS and Windows LM/CCS
PWLMDOSCC06.00 PATHWORKS V6.0 for DOS and Windows LM/CCS
PWLMWNTCC04.01 PATHWORKS for Windows NT LM/CCS
PWNWDOSCC05.00 PATHWORKS V5.0 for DOS and Windows NW/CCS
PWNWDOSCC05.01 PATHWORKS V5.1 for DOS and Windows NW/CCS
PWNWDOSCC06.00 PATHWORKS V6.0 for DOS and Windows NW/CCS
PWNWWNTCC04.01 PATHWORKS V4.1 for Windows NT NW/CCS
I have not seen a PAK for the QM-2CLAA-AB Designated Access license.
It would replace PWLMXXXFP05.00=QM-2CLAA-A1 (PATHWORKS V5.0 LAN
Manager Server FPA) as you suppose and also replace the FPA half of:
PWLMDOSCC05.00 PATHWORKS V5.0 for DOS and Windows LM/CCS
PWLMDOSCC05.01 PATHWORKS V5.1 for DOS and Windows LM/CCS
PWLMDOSCC06.00 PATHWORKS V6.0 for DOS and Windows LM/CCS
PWLMWNTCC04.01 PATHWORKS for Windows NT LM/CCS
The "package" that replaces the CCS license includes several licenses,
including both a System license and a Designated Access license.
|
| 120.33 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Fri Feb 21 1997 13:27 | 34 |
|
License Replaces
(right to use PW software on a client.)
System License CNS
PWXXWINAT07.00 PWXX***AT**.** (* Depends on O/S and version)
QM-5LKAA-Ax QM-2CNAA-A1 (this part# is PWXXDOSATvv.vv)
(Right to access files / print services on PW v5 or earlier servers)
Designated Access FPA
PWLMXXXFP05.00 PWLMXXXFP05.00
QM-2CLAA-AB QM-2CLAA-A1
(Right to access servers and use PW software)
Integrated Client Access CCS
2 PAKs - both above PWLMDOSCC06.00
QP-5LWAA-Ax QM-0TLAA-A1
(Server Based Licenses)
PC Conncurrent FPS
PWVMSCU05.00 PWVMSCU05.00
QM-A93AA-Ax QM-A93AA-Ax
>Trev UK CSC (Where the first call on a new PWXXWINAT07.00 replacing a
>CCS licnese on his NT Client failed to connect to his server
right, because PWXXWINAT07.00 does not grant the right to connect to a
PATHWORKS server.
|
| 120.34 | re: .31 | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Fri Feb 21 1997 14:44 | 35 |
| re: .31
Steve's answers are pretty good in .33. Just note that in your left column
you ended most part numbers with "-Ax" and in the left with "-A1". The mapping
from -A1 is to -AB in the new scheme.
Also, to elaborate on the last point that Steve tries to make in .33, the
reason why your new PW32 license doesn't let you access your servers is that
it is a "System" license (a.k.a., CNS) not a new CCS license (those are gone).
Think of it like this:
1. When we first shipped PW4D&W V5.0 and PW4V(LM), we sold you a
PW4D&W(LM) V5.0 CCS license.
2. When we were ready to ship PW4D&W V5.1, we *could* let you update
your PW4D&W(LM) V5.0 CCS license with a PW4D&W V5.1 CNS-Update
license, since the only new code that you got rights to was the
V5.1 client code.
If we had done this, you would have known that you needed to keep using your
CCS license to access your servers...CNS license, as you know, have nothing to
do with licensing servers. The new "System" licenses *are* CNS licenses.
Finally, to answer your question...
I also have noticed on the sheet that there are no new Pathworks VMS /
UNIX NETWARE concurrent part Nos or names. Is this because we should just
continue to use the old ones of both. (names and Part nos).
...the answer is that, for these part numbers, the *only* thing that changed
was the *names*; they, too, are now called "PC Concurrent" licenses instead of
FPS. However, their part numbers and prices did not change.
John
|
| 120.35 | License trades? | NQOS01::tunsrv2-tunnel.imc.das.dec.com::Workbench | | Fri Feb 28 1997 15:38 | 13 |
| Yet another scenario:
Customer has just upgraded Pathworks Server Cluster to PWV5.0 (reluctantly)
Customer has 50 OS/2 FPA client licenses. They replaced those machines with
Windows NT Machines. They want to know if those 50 OS/2 licenses are worth
anything now, and can they "trade them in" for Designated Access licenses.
They DON'T want PW32, just file and print.
They currently have a temporary PWLMXXXFP05.00 license to allow this.
What are their choices?
Betsy
|
| 120.36 | DA = FPA | DELNI::tunsrv2-tunnel.imc.das.dec.com::DECNA.LKG.DEC.COM::emsley | | Fri Feb 28 1997 18:01 | 10 |
| Betsy,
50 FPA license = 50 DA License
License NAMES have changed not Rights
Unless you use PATHWORKS 32 you need no additioanl licenses, unless the
customer wants more machines connecting to PATHWORKS servers.
Rob
|
| 120.37 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 03 1997 08:24 | 8 |
| also, there's no such thing as an OS/2 FPA license -- FPA has always
been operating-system nuteral. PWLMXXXFP05.00 -- the XXX means 'any
o/s'
As a more marketing-savvy company might say...
Just Use 'Em
|
| 120.38 | Cover Letter for PWXXWINAT07.00 ("System") Upgrade | JAMIN::WASSER | John A. Wasser | Fri Mar 07 1997 13:12 | 117 |
| Here is the text of the cover letter that customers got with the new
"System" upgrade licenses.
HANDI::USER$280:[PWRK_PM.PUBLIC]PW32RTNV.DOC
--------------------------------------------------------------------------------
DIGITAL PATHWORKS 32 System License
Upgrade Service
Included in this mailing are your PATHWORKS 32 V7.0 System Upgrade licenses
(QM-5LKAA-C*). These upgrade licenses are being delivered to those with one
or more of the following licenses and subscribing to one or more of the
following rights to new versions services:
License Product Name License PN Service PN
PATHWORKS for DOS and Windows (LAN Manager) CCS QM-0TLAA-A* QT-0TLAA-T*
PATHWORKS for DOS and Windows (NetWare) CCS QM-0EKAA-A* QT-0EKAA-T*
PATHWORKS for DOS and Windows CNS QM-2CNAA-A* QT-2CNAA-T*
PATHWORKS for Windows NT (LAN Manager) CCS QM-2K5AA-A* QT-2K5AA-T*
PATHWORKS for Windows NT CNS QM-2K6AA-A* QT-2K6AA-T*
PATHWORKS for OS/2 (LAN Manager) CCS QM-YFWAA-A* QT-YFWAA-T*
PATHWORKS for OS/2 (NetWare) CCS QM-506AA-A* QT-506AA-T*
PATHWORKS for OS/2 CNS QM-36EAA-A* QT-36EAA-T*
eXcursion for Windows and Windows 95 QM-MG7AA-A* QT-MG7AA-T*
eXcursion for Windows NT QM-0ECAA-A* QT-0ECAA-T*
New Licensing for PATHWORKS and eXcursion
Why are you receiving a PATHWORKS 32 V7.0 System Upgrade license?
The licensing of PATHWORKS products has been streamlined and simplified to
make it even easier for customers to use PATHWORKS software in a continually
evolving environment. The PATHWORKS 32 V7.0 System license is now the only
license that is offered for customers who want to use any of the desktop
software related to the products listed above.including eXcursion software.
Since we are both Upgrading the software and related licenses for some of
the desktop software referenced above and expanding the rights associated
with our current licenses, a PATHWORKS 32 V7.0 System Upgrade license is
being provided to all customers with contract covering the licenses above,
even if the particular software product you may be using is not changing,.
For more information on all the changes to PATHWORKS and eXcursion licenses
and business practices, please visit our Internet site at:
http://www.digital.com/info/pathworks/
- See Important Information on Reverse Side -
SPECIAL NOTES
Customers with CCS licenses
Although the PATHWORKS 32 V7.0 System-Upgrade license represents a total
upgrade for customers with a CNS or eXcursion System license, it does not
completely upgrade customers with CCS licenses. The PATHWORKS 32 V7.0
System-Upgrade license upgrades your rights with respect to your client
software but does not upgrade, or provide, any rights pertaining to your
PATHWORKS server software. This means that your PATHWORKS 32 V7.0 System
license can not be used to access your PATHWORKS servers.
Therefore, if you are using CCS licenses today, you should continue to use
these licenses with existing or the new PATHWORKS 32 software to gain access
to your PATHWORKS server.
NOTE:
Client licensing software provided with PATHWORKS 32 V7.0 software, by default,
will look for 2 licenses: a PATHWORKS 32 V7.0 System license (PWXXWINAT07.00)
and a Designated Access license (for LAN Manager, PWLMXXXFP05.00; for NetWare,
PWNWXXXFP05.00).
If you are going to continue to use your existing CCS license with PATHWORKS
32 V7.0 software, you should consult Chapter 4 of the Installation and
Configuration Guide for simple directions to change the licenses the software
requests and uses.
Customers using PATHWORKS for OS/2
As noted above, the new PATHWORKS 32 V7.0 System-Upgrade license represents
an upgrade to your rights regarding PATHWORKS client software. This new
Upgrade license, combined with your existing license for PATHWORKS V5.1 for
OS/2, now grants you the right to use any PATHWORKS client software including
software for Windows 95 and Windows NT. You now are free to choose a wide
variety of desktop operating systems that runs on Intel or Alpha, with Windows
NT, platforms and continue to enjoy the added capabilities provided by
PATHWORKS client software.
NOTE:
This license update is not related to any new PATHWORKS
software for the OS/2 clients. It simply represents an
update to PATHWORKS client licenses, in general, due to
a change in licensing practice for all PATHWORKS client
software.
Customers using eXcursion
As noted above, the new PATHWORKS 32 V7.0 System-Upgrade license represents
an upgrade to your rights regarding eXcursion software. This new Upgrade
license, combined with your existing license for eXcursion V2.1, now grants
you the right to use any PATHWORKS client software and any version of
eXcursion software.
The reason for this change is that, with the release of DIGITAL PATHWORKS
32 V7.0, enhanced versions of eXcursion software will now only be shipped
as part of the PATHWORKS 32 V7.0 software package. In fact, the most recent
update to eXcursion software to support Microsoft Windows NT 4.0 and to
provide 32-bit support for Microsoft Windows 95, will only be available as
part of the PATHWORKS 32 V7.0 software.
If you also subscribe to Media and Documentation Distribution services from
DIGITAL for eXcursion, you will also be shipped the new PATHWORKS 32 V7.0
software kit and documentation that includes the new release of eXcursion.
Once again, thank you for choosing DIGITAL as your information systems
provider!
|
| 120.39 | Practical License Question | UTRTSC::BAKKER | Running arround in circles | Wed Mar 12 1997 05:41 | 26 |
| Hi,
I know by now how the new license sceme works . I would like
to know how to setup a PW32 client in a way that i don't have
to change it in the future.
Suppose I have only OLD CCS licenses from my old version which I
still should use for my server access.
Can I add a THIRD license key to my client in stead of changing
the Designated Access key (DEC-PWLMxxxFP05.00).
This way I don't have to change my client in the future and when
the new Client Access license is out I can register it in the
license server and remove the old CCS.
Is this Valid?
In fact If this was the DEFAULT during shipping all worked
ok and nobody had somany question as we have now.
I think we should NOT replace the Designated access key because
this would force us to modify each client again when the new
license is out.
Any comment?
Paul Bakker
PCI support Holland
|
| 120.40 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Wed Mar 12 1997 07:51 | 10 |
| the DA really isn't a new license, it's exactly the same as the "OLD"
FPA license -- if someone's working with PW32 using a System License
and an old CCS, why would you ever change to a DA?
The next time you will need to change, it'll be when the server
upgrades, to the yet-unreleased (I believe) Client Access license -
perhaps putting that in wouldn't be a bad idea if you want to follow
along with the rationale in .39... but I don't know what other
ramifications this might have when that license is actually loaded.
|
| 120.41 | Good luck... | JAMIN::WASSER | John A. Wasser | Wed Mar 12 1997 10:57 | 27 |
| > I know by now how the new license sceme works . I would like
> to know how to setup a PW32 client in a way that i don't have
> to change it in the future.
That method is to set it up correctly for your current
circumstances. If you have FPA or DA licenses (DEC-PWLMXXXFP05.00)
then the defaults are fine. If you have CCS licenses
(DEC-PWLMDOSCC0x.xx) then use them instead of the FPA/DA
default.
When the new "Client Access" (CA) licenses arrive the V6.0
servers will create a Virtual CCS or Virtual FPA/DA license
depending on what you ask for. The client will not need
to be configured again.
> Can I add a THIRD license key to my client instead of changing
> the Designated Access key (DEC-PWLMxxxFP05.00).
You can request up to 10 licenses. The user will get a
pop-up error message for any configured license that is
not currently available.
> In fact If this was the DEFAULT during shipping all worked
> ok and nobody had somany question as we have now.
I suspect that users would notice the pop-up error message.
|
| 120.42 | Virtual CCS! that solves it! | UTRTSC::BAKKER | Running arround in circles | Thu Mar 13 1997 02:30 | 6 |
| Thanks! I knew about the virtual FPA license in V6.
Ok. Now savely CHANGE from PWLMXXXFP05.00 to
PWLMDOSCC06.00!
Thanks again.
Paul
|
| 120.43 | License fake CC07.00? | UTRTSC::BAKKER | Running arround in circles | Thu Mar 13 1997 03:22 | 14 |
| Hi,
I have one more question about the license FAKE of the new
advanced server. Is the Fake from PWLMXXXCA06.00 to
PWLMDOSCC07.00 AND will the License registrar check for
one of the licenses with these minimum values:
PWLMXXXFP06.00
PWLMDOSCC07.00
PWLMXXXCA06.00
I would like to know this for future troubleshooting.
thanks!
Paul
|
| 120.44 | | JAMIN::WASSER | John A. Wasser | Thu Mar 13 1997 08:44 | 22 |
| > I have one more question about the license FAKE of the new advanced server.
> Is the Fake from PWLMXXXCA06.00 to PWLMDOSCC07.00
That is my understanding. You may want to ask in the
CPEEDY::PW-AS-V6 conference to be sure.
> AND will the License registrar check for one of the licenses with
> these minimum values: PWLMXXXFP06.00, PWLMDOSCC07.00, PWLMXXXCA06.00
I think it may check for a minimum of PWLMXXXFP07.00 instead
of PWLMXXXFP06.00 since I don't think the 06.00 version will
ever exist.
I think PWLMDOSCC07.00 is the correct minimum.
I don't know what the initial CA license version will be.
They may make it 07.00 rather than 06.00 to be consistent
with the virtual FPA/DA and CCS licenses.
The folks over in the OpenVMS V6 server conference (CPEEDY::PW-AS-V6)
may have more information.
|
| 120.45 | What about NT V3.51 and new license agent? | NQOS01::16.72.96.54::Workbench | | Fri Mar 21 1997 11:45 | 26 |
| re: .35-.37
This situation is still biting me. The customer with the 50 OS/2 CCS licenses
wants File and Print Access to their Pathworks V5.0 servers from a mix
of Windows NT V3.51 and V4.0 systems--without the Pathworks client software
loaded on them--just using the native networking capabilities of NT.
Apparently, our new license agent doesn't support CCS licenses for V3.51 of
NT--V4.0 works fine. The customer is planning on upgrading to V4.0 on all
the machines, but that won't be completed for another 6 months or so. So, in
the meantime, they're trying to figure out what to do.
In order to fix this, the customer's looking for a way to "trade-in" his CCS
licenses (QM-YFWAA-A1, qty 50) for lower functionality, but operational FPA
licenses (QM-2CLAA-A1, qty 50), hopefully at no cost.
Two questions:
- Is there a process to do this, and where do we go?
- Is there a near-term plan to support NT V3.51 for CCS licenses w/ the new
license agent?
The cusotmer's temporary license packs expire next week!
Thanks,
Betsy
|
| 120.46 | Answers... | DELNI::GORCZYCA | PATHWORKS Prod/Bus Mgmt | Sat Mar 22 1997 11:25 | 32 |
| In order to fix this, the customer's looking for a way to "trade-in" his CCS
licenses (QM-YFWAA-A1, qty 50) for lower functionality, but operational FPA
licenses (QM-2CLAA-A1, qty 50), hopefully at no cost.
Two questions:
- Is there a process to do this, and where do we go?
"Trading in" PATHWORKS licenses is not covered by any existing corporate policy.
However, some situations can be handled via special handling that varies by
geography. This case is one that can usually be handled. (Have I left myself
enough "escape routes" with this statement?)
Please send me mail, including the customer name, location, and SPS service
status *if* the next statement doesn't solve your problem, and I'll see what
I can do.
- Is there a near-term plan to support NT V3.51 for CCS licenses w/ the new
license agent?
Yes. We do plan on releasing a new "FPA Kit", soon, that will provide the new,
supported licensing software for Windows NT 4.0 clients and software for
Windows NT 3.5x clients that will allow the use of CCS/LAN Manager licenses
(from any platform: DOS, OS/2, Windows NT) as well as FPA/Designated Access
licenses.
The exact date has not be determined yet, but mid/late-April is probably a
reasonable expectation. (Yeah, Steve, I know that it *should* have been much
sooner, but...)
John
|
| 120.47 | Thanks! | NQOS01::tunnsrv_remote.alf.dec.com::Workbench | | Sun Mar 23 1997 18:02 | 6 |
| Thanks John,
I'll run the date by the customer and if it doesn't suffice, I'll send you
their info.!
Betsy
|
| 120.48 | TIMA/STARS/DSNlink Article on the topic | VMSNET::DEFIANT::s_vore | Smile, Mickey's watching! [email protected] | Wed Apr 16 1997 09:11 | 330 |
| For what it's worth, here's an article that was written for
the CSC's database. Check TIMA/STARS or DSNlink for the most
up-to-date version; it may be updated without this note being
changed.
[PW] Licensing: Update Information March 1997 (FAQ)
Any party granted access to the following copyrighted information
(protected under Federal Copyright Laws), pursuant to a duly executed
Digital Service Agreement may, under the terms of such agreement copy
all or selected portions of this information for internal use and
distribution only. No other copying or distribution for any other
purpose is authorized.
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
SOURCE: Digital Equipment Corporation
PATHWORKS LICENSE UPDATE INFORMATION (SPRING 1997)
PRODUCTS: PATHWORKS[TM] for OpenVMS[TM], Versions 5.0 through 5.0E
PATHWORKS 32, Version 7.0
PATHWORKS for DOS and Windows[R], Version 6.0
PATHWORKS for Windows 95, Version 1.0A
PATHWORKS for Windows NT, Version 4.1B
OP/SYS: OpenVMS, Versions 5.5-4 through 7.0
Microsoft[R] Windows, Version 3.1
Microsoft Windows for Workgroups, Version 3.11
Microsoft Windows 95
Microsoft Windows NT, Version 3.51, 4.0
COMPONENT: PATHWORKS Licensing
SOURCE: Digital Equipment Corporation
QUESTION:
I've heard that there have been some changes to Digital's PATHWORKS
licensing. I was familiar with the license types I was using before -
CCS, FPA, etc - what's changed?
ANSWER:
Some definitions, just to get us all started in the same place:
FPA = File & Print Access (now called DESIGNATED ACCESS) - a
client-based license which is served to ONE client from a PATHWORKS
License Server (requires license requestor/responder software on the
client PC). This grants the right for that one client to access as many
PATHWORKS servers as it's user would like. The license is assigned to
that ONE PC and cannot be used by another client.
FPS = File & Print Service (now called PC CONCURRENT) - a server-based
license which is only loaded on the server (no client software required
at all). This CONCURRENT-USE license grants access from one client AT A
TIME to ONE PATHWORKS server. When that client disconnects, the license
is released and then may be used by another client. No management of
this sort of licenses is possible.
CCS = Combined Client/Server (Now called a SYSTEM LICENSE) - a
client-based license which is served to ONE client from a PATHWORKS
License Server (requires license requestor/responder software on the
client PC). This grants the right for that one client to access as many
PATHWORKS servers as it's user would like AND also the right to use
PATHWORKS client software for a particular operating system. (i.e.
PWLMDOSCC06.00 may use PATHWORKS for DOS & Windows v6.0 or earlier,
PWLMWNTCC04.01 may use PATHWORKS for Windows NT 4.1). The license is
assigned to that ONE PC and cannot be used by another client.
CNS = Client Network Services (No longer available) - a client-based
license which is assigned to ONE client from a PATHWORKS License Server
(requires license requestor/responder software on the client PC). ).
This grants the right for that one client to use PATHWORKS client
software for a particular operating system. (i.e. PWXXDOSAT06.00 may
use PATHWORKS for DOS & Windows v6.0 or earlier, PWLXXNTAT04.01 may use
PATHWORKS for Windows NT 4.1). The license is assigned to that ONE PC
and cannot be used by another client.
Actually, not that much has changed. The licensing is very similar to
the way you knew it over the last couple of years. If anything, it will
be easier to understand.
We've always required a license to run the client software and a license
to access the server. Many people did not understand this, especially
since the two licenses were almost always purchased in one package, most
recently called a CCS (Combined Client & Server) license. This made
transitions between client operating systems (95 to NT, for example)
difficult because an NT CCS license was different from the CCS license
required for DOS-based operating systems. Now the licenses are the same
- a System License to run the client software (be it
DOS/Win/WfW/95/NT/OS2) and a license to access the server.
With the current server products, that "access the server" license can
be either an FPA, FPS, or if you've still got some around a CCS.
When the v6 server ships, new licenses (CLIENT ACCESS) will ship. At
this point, there will only be two licenses - the SYSTEM LICENSE to run
PATHWORKS client software (if you are), and a CLIENT ACCESS license to
access the servers. A nice feature will be that these licenses will be
able to switch between client-based (obtained by a client, granting
access to any server, like an FPA) and server-based (no software at all
on the client, concurrent-use, but only for one server, like an FPS) at
the will of a system administrator. This will require new license server
and registrar code, which will be in both v6 and a future version of v5.
A client will be happily using just a CLIENT ACCESS license then,
when/if they decide they need to add PATHWORKS client software, obtain a
SYSTEM license. In the past, they would have had to turn in the license
they were using - no longer.
In my mind, this is MUCH easier... no more asking what client operating
system you're using, just these simple rules:
To access a PATHWORKS server, you need an CLIENT ACCESS license.
To use PATHWORKS client software, you need a SYSTEM license.
But that's in the future. What is the current state of licensing?
First of all, your existing clients need make no changes at this point.
If you're not upgrading your client software to PATHWORKS 32 or
installing new clients, you're already set; keep things as they are.
Clients being upgraded to PATHWORKS 32 or new clients will require two
separate licenses.
One license (PATHWORKS 32 SYSTEM LICENSE) grants the right to use the
PATHWORKS Client software of a particular version or earlier on any
client - DOS, NT, WfW, 95, or OS/2. This is basically the same as the
old CNS license. For existing clients which are being upgraded (and for
which you've got a License Update Service contract), this is the license
that was just updated since the software was just updated.
The other license will grant the right to access your PATHWORKS servers
of a particular version or earlier. This is where things get tricky. If
you are ordering new licenses, you would order a DESIGNATED ACCESS
license - the thing that used to be called an FPA license. If you're
upgrading an existing client or if you have some extra CCS licenses
around, you can use it's existing CCS license to access the server -
you're using one of the two rights that license granted you. This does
not mean that you can legally use just the CCS license - if you're
running PATHWORKS 32 then you still need that System License.
For technical information on requesting these licenses for your clients,
please see the PATHWORKS Guide to Managing Licenses (part number
AA-Q1BZD-TH) which you should have received with a prior version of
your software and the cover letter that came with your updated licenses.
This cover letter can also be found in the DSNlink PATHWORKS database, "
[PW-VMS]V5 PATHWORKS Licensing 1997 - Enterprise Integration Client"
For those purchasing new licenses, the "replacement" for the CCS is a
license package - part # QP-5LWAA-A* is the ENTERPRISE INTEGRATION
CLIENT LICENSE PACKAGE, which includes a SYSTEM license and a DESIGNATED
ACCESS license.
By the way, before anyone complains... yes, these kits are slightly more
expensive in quantity 1 than the old CCS licenses were. There are now
quantity discounts, which did not exist for CCS licenses, that bring the
price down under that of a CCS license once you get over quantity 50
(and even at 25 they're pretty close). They also include the right to
more than a CCS license did, including PATHWORKS 32 (which now includes
eXcursion) and TeamLinks.
I know it sounds complex, but think of this... in the Microsoft/LAN
Manager world, we previously had (at a quick count) 7 different
licenses. In the future, there will be 2.
Specific Questions
QUESTION:
I have received 'PATHWORKS 32 v7.0/SYS-UPG:QTY:1' license pak for the
right number of licensed PATHWORKS PCs (475). The license PAK that we
are currently using is 'DECPWLMDOSCC06.00' for the same quantity. Is
the 'PWXXWINAT07.00' license the license information that I enter on
each client's licensing agent in win95's network icon or do I still use
the my current one, 'DECPWLMDOSCC06.00'?
ANSWER:
Since you're using PWLMDOSCC06.00 licenses to grant you two rights: the
right to use PATHWORKS for DOS and Windows v6.0 or earlier the right to
access any number of PATHWORKS LAN Manager v5.0 or earlier servers.
Then you will continue to use the second of these to access your
servers. You will use the new PATHWORKS 32 System License to grant the
right to use the new PATHWORKS 32 software. Therefore, a PATHWORKS 32
client will request and obtain two licenses, both of the above.
QUESTIONS:
My current server based license is 'PWLMVMSCU05.00' what do I need to
replace this or do I? My remote win95 users use this and also our NT
users do; we do not have any PATHWORKS client software installed on
those PCs.
ANSWER:
Since the server is not changing, nor is your access to the server(s)
from these clients, this license does not change at this point.
QUESTION:
If I buy a NEW PATHWORKS 32 license I should get a PW32 license and an
FPA (Designated Access) license?
ANSWER:
If you've orderd the right thing, yes. We're getting reports of folks
who say "I want to run PATHWORKS 32 on my client, what do I need?" The
answer to that, of course, is 'just a PW32 SYSTEM license' but that's
missing the mark. The question really is "I want to run PATHWORKS 32 on
my client and access PATHWORKS servers, what do I need?" The correct
answer to that is what leads you to your answer - a PW32 SYSTEM license
and [an FPA license, a DESIGNATED ACCESS license (the new name for FPA),
or an existing CCS license].
QUESTION:
If I get an update to my existing CCS license I get a PW32 license and
use my existing CCS licenses. If this IS the case then can I use my
DOS/Windows CCS licenses to connect an NT machine or am I still stuck
when I want to change operating systems ?
ANSWER:
If you're using PW32 on NTv4, then the answer is yes - you can use (the
connect-to-the-server half of) your CCS license, be it WNT, DOS, or OS2,
to connect to the server. The eventual goal, of course, when all is
said & done, is that you'll be using CLIENT ACCESS licenses which don't
care which of the operating systems you're running.
QUESTION:
So, if I got this right, I should have a number of PATHWORKS System 7
licenses for my new PATHWORKS 32 software, and they should be called
DEC-PWXXWINAT07.00. These I'm missing, and I'm about to call my
software service rep to find out where they are.
ANSWER:
Right. Any clients running PATHWORKS 32 need the new license.
QUESTION:
And I continue to use my CCS licenses, PWLMDOSCC06.00 for example, to
grant
my clients access to my PATHWORKS servers, and I need to leave these
around/served even if I do finally get my System licences for the clients.
ANSWER:
Right.
QUESTION:
Now if I understand the numbering scheme, these should still work when I
install Pathworks for VMS V6 software. Is that true?
ANSWER:
No. The 06.00 part of these licenses (this is part of what made
things confusing and will be easier in the future) has more to do with
the version of client than that of the server. When the v6 server comes
out, the "access any number of v5 or earlier" portion of your CCS
license will not grant the right to access a v6 server. At this point,
you'll complete the second part of this whole operation by upgrading
that (2nd half of the) CCS license to a Client Access license.
See Also:
[PW-VMS]V5 PATHWORKS Licensing 1997 - Enterprise Integration Client
[PW-VMS]V5 FastM: LICENSE ISSUES MASTER FM0046
[PW] Licensing: How Does it Work? What are the Common Problems? (FAQ)
[PW-DOS]V5 FastD: Obtaining a License From a Cluster Over a WAN
|