Software Licensing Guide To Upgrades And Migrations

Customers commonly want to know if their software licences can be 'transferred' or 'moved' in connection with a reorganisation, reconfiguration or hardware upgrade. Digital's policy on upgrading and migration is perceived to be complex. This guide concentrates on clarifying these topics ancl should provide answers to most relaced questions. A basic awareness of software licensing is presumed.

OCR (הסבר)
SOFTWARE LICENSING GUIDE TO UPGRADES AND MIGRATIONS April 95 | weit hl Laaegntin » ates PREFACE Customers commonly want to know if their software licences can be ‘transferred’ or ‘moved’ in connection with a reorganisation, reconfiguration or hardware upgrade. Digital’s policy on upgrading and migration is perceived to be complex. This guide concentrates on clarifying these topics and should provide answers to most related questions. A basic awareness of software licensing is presumed. This guide covers the following three combinations of Operating System and Hardware Architecture (“platform-pairs”): * Digital UNITX(R)/Alpha OpenVMS/Alpha OpenVMS/VAX * Formerly OSF/1/Alpha In the event of any conflict between this guide and Digital's standard terms and conditions for the supply of computer products, the aforesaid terms and conditions shall prevail. Further information may be obtained through your usual Digital software supply channel. Po ». fa 4 i Le % y — i we } wy hy x i a a i y K f +, 43 é rs tA 2 { of ff A wats - A f + “gy ' > . “he 5 y 4 1. 4 ——s we AN eo wy F a: Hs madeed Allowance Rule Part 1: Operating Systems 1. Base licences 2. SMP Extension licences . Single Interactive User licences 2 3 4. Unlimited Interactive User licences (QL-upiA*-AA) 5. Unlimited Interactive User licences (QL-upiA*-6*) 6 “Classic: OpenVMS licences (QL-001 A*-**) Part 2: Layered Products 1. Traditional licences 2. ClusterWide licences 3. Concurrent Use licences 4 . Personal Use licences 7 Part 3: Current Licensing Programmes 1. Universal Platform Guarantee 2. Upgrade-licence-for-free 3. Trade-Up-To-User Appendices A. New System Classes (replace Traditional Tiers for new licences) B. Original Traditional Tiers and ClusterWide Tiers C. Operating System Interactive Unlimited User and Base licence ppareaumber sub-tier IDs a retaining a Traditional Tiers numb G. Update Lice! INTRODUCTION Digital has greatly simplified its licence trade-in policy. Most trade-ins are now possible and there is a single standard allowance rule. This guide describes which licence-types are ‘moveable’ and/or can be traded in for an applicable replacement. To determine whether the standard allowance rule or current programme allowances should be applied, it is necessary to understand: 1 The meaning of licence Redesignation, : : Page 4 Upgrading, Downgrading and Migration IBS 2 The types of licence 3. The software domain for each of the licence-types + Part 1 4 What licence-types can be REDESIGNATED and Part 2 5 The possible upgrades and migrations for each type of licence 6 The single standard allowance rule Page 5 7 The licensing programmes Part 3 (including their allowance variations) + For any given type of licence, a software domain is a type of hardware (or hardware configuration) on which the use of che software is permitted. Throughout the guide, software licence part-number formats are used (QL-upiA *-**). ‘upi’ stands for unique product identifier. These characters are used as a filler in positions 3, 4and 5 of the part-numbers. Focus is given to characters 7, 8 and 9. ¢ Character 7 indicates the software domain or, in the case of layered product user licences, the underlying operating system. ¢ Character 8 indicates the licence-type. ¢ Character 9 gives further licence information such as Cluster Wide points or the number of users - depending on the licence-type. Licence Redesignation To redesignate a licence means to terminate its cover in one software domain and to designate it to another. With redesignation, an existing licence is ‘moved’ - nothing new is ordered. Redesignation may or may not be allowed, depending on the licence-type and whether or not the proposed alternative system is an appropriate software domain. (Redesignation is performed by the customer and does not require Digital’s involvement.) Licence Upgrading This process is confined to a single platform-pair e.g. OpenVMS/Alpha. CPU Change Where redesignation is not permitted, a new licence (of the same type and for the same product) must be ordered for the upgrade CPU. The price of the licence may be reduced in accordance with the standard allowance rule (see page 5) or any applicable licensing programme (see Part 3). Numbered User to a Higher Number or Unlimited A number of licensed users may be increased by simply ordering more licences of the same kind. Upgrading to Unlimited users is effected by trading-in one or more numbered user licences against the purchase of a new Unlimited User licence. Apply the standard allowance rule (see page 5). Licence Downgrading This process is confined to a single platform-pair and a given licence-type. An existing licence is traded in and a new licence (of the same type and precisely the same product) is ordered sufficient to cover the system in the lower licence price tier. The standard allowance rule applies. (Remember, it costs nothing to simply redesignate an existing licence to the ‘smaller’ CPU but this may be undesirable because any software service contracts must match the original licence level, rather than be reduced to the system level.) _ Licence Migration — Digital's policy on licence trade-ins is to provide an allowance for the replacement licence(s) equal to 75% of the smaller of either: e che price of the licence(s) being traded-in or e the price of the new licence(s). (If the values are equal, the allowance is calculated as 75% of the new licence(s).) Determining the value of the licence being traded-in Depending on the licence-type, the value of the licence(s) being traded-in will be determined by one of (a) the current price (b) the last listed price or (c) the equivalent licence price: Licence-type Base (QL-upiA*-6*) SMP Extension (QL-upiA9-6*) Single Interactive User (QL-upiA9-BB) Unlimited IA User (QL-upiA*-AA) Unlimited IA User (QL-upiA*-6*) Classic OpenVMS (QL-001A*-A*) Classic OpenVMS (QL-001A*-B*) Traditional System Class QL-upiA*-AA) Traditional ‘old’ Tier (QL-upiA*-AA) Cluster Wide (QL-upiA9-J*) Concurrent Use (QL-upiA*-3B) Personal Use (QL-upiA*-2B) Value is 75% of Current Current Current Current Equivalent System Classt Current Current Current Equivalent System Class Last listed Current Current +When trading in either an Unlimited IA User licence (QL-upiA*-6*) or a layered product Traditional licence (‘old’ Tier), use the equivalent System Class licence (‘-AA’). ie. find the System Class in which the CPU is now categorized and use that System Class licence value. Note: In the fucure the percentage for determining the allowance may change but other details of the standard allowance rule will be unaffected. (ereeatmnber: QL-upiA*-6*) OpenVMS/VAX OpenVMS/Alpha Digital UNIX/Alpha UPI: 005 MTl MT4 1. Software Domain One system model marketed by Digital. The system model must be of the type indicated by the seventh and ninth characters of the licence part-number. The seventh character codes are found in Appendix B. Ninth character codes are found in Appendix C. 2. Redesignation Base licences cannot be redesignated or otherwise separated from the original software domain. 3. System and Base licence trade-in for a new system either within the same or within a different hardware architecture If a customer wishes to trade-in a system and its Base licence against the cost of another system, any credit will be bundled with the Base licence which is supplied with the new system provided it is purchased from Digital or from an authorised partner who has purchased the system from Digital. 4. Migrate to a different Operating System licence on a given System (e.g. OpenVMS/Alpha to Digital UNIX/Alpha) See Universal Platform Guarantee Programme in Part 3 of this Guide. SMP Extension Licences) = (Part-number: QL-upiA9-6*) The ninth character for an SMP Extension licence indicates a series of processors. For the VAX 7700 series the ninth character is ‘B’. SMP Extension licence identifiers for Alpha Systems are given in Appendix C. 1. Software Domain An SMP Extension licence must be used in conjunction with a Base licence. One SMP Extension licence is required for each SMP board extension. 2. Redesignation SMP Extension licences must remain with their underlying Base licences. They cannot be redesignated to other systems, even if the SMP boards are moved. 3. System and Base licence trade-in for a new system either within the same or within a different hardware architecture A customer may trade-in a system with its Base licence towards the cost of another system. A Base licence will come with the new system when it is purchased from Digital. If the new system has a lesser number of SMP Extension licences than the number on the system being traded-in, the customer is entitled to an allowance for the additional SMP Extension licences required to equal the original number. Apply the standard allowance rule or, if applicable, the second programme in part 3 of this guide. 4. Migrate to a different Operating System licence on a given Alpha System (e.g. OpenVMS/Alpha to Digital UNIX/1 Alpha) See under Base licences, on page 6. Single Interactive User (“IAU”) and Distributed Interactive User (“DIU”) Licences (Part-number: QL-upiA9-BB) UPIs for OpenVMS/VAX OpenVMS/AIpha Digital UNTX/Alpha IAU XUL MT2 MT7 DIU 09S MT3 MT7 ¢ “XUL is applicable for OpenVMS/VAX 5.5. ¢ ‘09S’ is applicable for OpenVMS/VAX V6.0 or V6.1 and ‘MT3’ is applicable for OpenVMS/Alpha V1.5 or V6.1. ¢ OpenVMS V6.2 will operate on both VAX and Alpha. ¢ With the release of OpenVMS V6.2, the DIU licences will be the ‘Concurrent Use’ type i.e. with part-numbers of the form - QL-upiAA-3B. ¢ OpenVMS Concurrent Use licences, for both VAX and Alpha will have the ‘upi’ ‘MT3’, giving QL-MT3A9-3B. Digital UNIX/Alpha Concurrent Use licences will retain the UPI] ‘M17’, giving QL-MT7AM-3B. 1. Software Domain TAU: one system model marketed by Digital. DIU: one standalone system or one cluster of systems. The system(s) may be any within a hardware architecture indicated by the UPI. Furthermore, the new Concurrent Use licences (QL-MT3AA-3B), mentioned in the note above, are designatable to any VAX or Alpha system running OpenVMS Version 6.2 or a later version. 2. Redesignation IAU/DIU licences are CPU-type independent and therefore are redesignatable between systems within any given hardware architecture e.g. within VAX or within Alpha systems. Note, the new ‘QL-MT3AA-3B' licence is even more flexible, being redesignatable to any other VAX or Alpha running OpenVMS V6.2 or a later version. 3. Upgrading or Migrating from IAU and/or DIU to Unlimited User For a given operating system, total the value of the licences being traded-in. Compare the total value with the price of che new Unlimited User licence (which may be for the same or a different operating system). Apply the standard allowance rule. 4. Migrating from IAU to DIU licences This is permitted on a one-for-one basis either for the same operating system or to a different operating system. Apply the standard allowance rule. 5. Migrate to IAU/DIU licence(s) on a different operating system platform This is permitted on a one-for-one basis. Apply the standard allowance rule. Unlimited Interactive User Licences (Purchased on or after Oct-10-94) Part-number: QL-upiA*-AA) UPIs for OpenVMS/VAX OpenVMS/Alpha Digital UNLX/Alpha XUL MT2 M17 1. Software Domain One system model marketed by Digital. The system model must be within a System Class equal to or below that indicated by the seventh character of the licence part-number. The seventh character codes and System Classes are found in Appendix A. 2. Redesignation These licences may be redesignated to any system within the applicable platform-pair and within the same (or a lower) System Class. (See Appendix A for System Classes.) 3. Upgrade to use on a higher System Class CPU A licence may be traded-in against the purchase of a higher System Class Traditional licence, either with or without a hardware trade-in. Apply the standard allowance rule. 4. Migrate to a different platform-pair A licence may be traded-in against the purchase of an Unlimited User licence for a different platform-pair, either with or without the hardware. Apply the standard allowance rule. 5. Migrate to IAU/DIU licences (for the same or a different platform-pair) A licence may be traded-in against the purchase of one or more [AU or DIU licences. Apply the standard allowance rule. Note: The allowance will be 75% of the smaller of either: e che current price of Unlimited Interactive User licence or e che coral price of the IAU/DIU licences being ordered. (If the values are equal, the allowance is calculated as 75% of the new licences.) If QL-MT7AM-3B and QL-MT3AA-3B are available, then che Trade-Up-To User programme may be applied. (See Part 3.) Unlimited Interactive User Licences (Purchased between July 92 and Oct-10-94) (Part-number: QL-upiA*-6*) UPIs for OpenVMS/VAX OpenVMS/Alpha Digital UNIX/Alpha XUL MT2 MT7 1. Software Domain One system model marketed by Digital. The system model must be within a ‘Tier’ equal to or below that indicated by the seventh character of the licence part-number. The seventh character codes for the ‘old’ tiers are found in Appendix B. 2. Redesignation These licences cannot be redesignated or otherwise separated from the original software domain. 3. Migrate to a System Class Operating System licence (same platform-pair) A licence may be traded-in against the purchase of an Unlimited User System Class licence (QL-upiA*-AA), only if the original hardware is also being traded-in. Apply the standard allowance rule or, if applicable, the Upgrade-licence-for-free programme described in part 3 of this guide. 4. Migrate to a System Class Operating System licence (different platform-pair) A licence may be traded-in against the purchase of an Unlimited User system class licence (QL-upiA*-AA) for a different platform-pair, only if the original hardware is also being traded-in. Apply the standard allowance rule. 5. Migrate to I[AU/DIU licences (for the same or a different platform-pair) A licence may be traded-in against one or more IAU or DIU licences. Apply the standard allowance rule. Note: The allowance will be 75% of the smaller of either: ¢ the current price of Unlimited Interactive User licence or * the coral price of the IAU/DIU licences being ordered. (If the values are equal, the allowance is calculated as 75% of the new licences.) If QL-MT7AM-3B and QL-MT3AA-3B are available then the Trade-Up-To User programme may be applied. (See Part 3.) ‘Classic’ OpenVMS Licences (Part-number: QL-001A*-A*/QL-001A*-B*) 1. Software Domain * QL-001A*-A* licences were the original type of licence for OpenVMS. A licence permits an unlimited number of users access on one system. ¢ QL-001A*-B* licences were introduced for early MicroVAX and VA Xstations. A licence permits either a specified number or, in the case of QL-001A*-BZ, an unlimited number of users access on one system. ¢ For both ‘*-A*’ and ‘*-B*’ licences, the licensed system must be within the tier indicated by the seventh character of the part-number as shown in Appendix B. ¢ For the ninth character (sub-tier identifier) of the “*-A*’ licences, refer to Appendix E. ¢ The ninth character of the **-B*’ licences is reserved for indicating the number of users. (See Appendix F.) 2. Redesignation These licences cannot be redesignated or otherwise separated from the original software domain. 3. ‘In-cabinet’ Upgrades (e.g. 6210 to 6410) and ‘Box Swaps’ A licence may be traded-in against the purchase of another usually higher tier or sub-tier licence in conjunction with an in-cabinet upgrade or if the original hardware is being traded-in to Digital. Apply the standard allowance rule or, if applicable, che Upgrade- licence-for-free programme described in part 3 of this guide. (See Appendix E for systems which have retained classic OpenVMS licences.) 4. Migrate to a System Class Operating System licence A licence may be traded-in against the purchase of a System Class Unlimited User licence (QL-upiA*-AA) or a numbered User licence for a VAX System Upgrade, only if the original hardware is also being traded-in for a VAX System Upgrade. Apply the standard allowance rule or, if applicable, the Upgrade-licence-for-free programme described in part 3 of this guide. 5. Migrate to a different platform-pair A licence may be traded-in against the purchase of a System Class Unlimited User licence (QL-upiA*-AA) or a numbered user licence for a different platform-pair, only if the original hardware is also being traded-in for a new Alpha system. Apply the standard allowance rule. — ah 23 LAY a. . | Traditional Licences (Part-number: QL-upiA*-AA) For Traditional licences ordered since October 10th 1994 (‘System Class Traditional licences”), the seventh position characters of the part-numbers indicate the applicable System Classes. (See Appendix A.) For Traditional licences ordered prior to October 10th 1994 (“Tier Traditional licences”), the seventh position characters of the part-numbers indicate the applicable CPU tiers. (See Appendix B.) 1. Software Domain A Traditional licence grants the licensee the right to use the specified software on a single VAX or single Alpha system, running a specified operating system. The ‘upi’ indicates the applicable platform-pair. ¢ For System Class Traditional licences, the VAX or Alpha system must be in a System Class equal to or lower than that indicated by the licence partc-number. ¢ For Tier Traditional licences, the VAX or Alpha system must be in a tier equal to or lower than that indicated by the licence part-number. 2. Redesignation For Traditional licences, redesignation is limited to a given hardware architecture, running a given Operating System. ¢ A System Class Traditional licence may only be redesignated to another single CPU, in the same or in a lower System Class. (See Appendix A.) ¢ A Tier Traditional licence may only be redesignated to another single CPU, in the same or in a lower tier. (See Appendix B.) 3. Upgrading and Migration A customer may trade-in a ‘Tier’ or a System Class Traditional licence (with or without hardware) and receive an allowance towards the cost of one System Class Traditional licence. Apply the standard allowance rule or, if applicable, the Upgrade-licence-for-free programme, described in Part 3. Note: when trading-in a ‘Tier’ Traditional licence, the standard allowance rule applies to the equivalent System Class Traditional licence (see page 5). 4. Migrate to Concurrent/Personal Use See the Trade-Up-To-User programme, described in part 3. ClusterWide Licences (Part-number: QL-upiA9-J*) Cluster Wide licences are no longer sold but it is still necessary to know what existing licences allow and how these licences may be updated to later versions or migrated to other licence types. The ninth position characters of the ClusterWide licence part-numbers indicate the number of ClusterWide units. (See Appendix B.) 1. Software Domain A CluscerWide licence grants the licensee the right to use the specified software on a single VAX or VAXcluster. The Cluster Wide licence may be designated to the whole or a part of a VA Xcluster. The licence unit requirement (LUR’) of the VAX or VAXcluster (whole or a part) must not exceed the number of units indicated by the licence. For example, a ClusterWide licence for 600 units of Fortran would cover: e asingle VAX with a LUR of 600 or less ¢ awhole VAXcluster with a tocal LUR of 600 or less or ° apart of a VAXcluster if che part has a LUR of 600 or less. 2. Redesignation A ClusterWide licence may be redesignated to any different single CPU or VAXCluster provided a licence is not active in more than one software domain at any given time and provided the licence units are not exceeded. A ClusterWide licence may not be ‘split’ except as described in section 6 under ‘Cluster Wide licences and Hardware Upgrades and Migration.’ 3. Migrating to Concurrent/Personal Use See the Trade-Up-To-User programme, described in part 3. 4. Migrating to Traditional A customer may trade-in one or more ClusterWide licences and receive an allowance towards the cost of one or more System Class Traditional licences. Apply the standard allowance rule. The allowance will be 75% of the smaller of either: e the coral of the ClusterWide licence(s) values being traded-in or e che coral of the Traditional licence(s) being purchased. (If the cotals happen to be equal, take 75% of the latter.) -ClusterWide Licences (continued) 5. Downgrading ClusterWide licences are no longer available to order and downgrading is therefore not possible. Alternatives are given in sections 3 and 4 on this page. 6. ClusterWide Licences and Hardware Upgrades and Migrations A customer may wish to trade-in a system from a VAXCluster. If the system has any Cluster Wide licences, these may be traded-in in accordance with the standard allowance rule or (if the programme criteria are met) the Upgrade-licence-for-free programme. (See part 3 of this guide.) Many systems ‘share’ Cluster Wide licences, i.e. all or some of the systems in a VAXCluster may be covered by one or more ClusterWide licences for different products. Obviously, if a new system has an equal or lower ClusterWide LUR as that of the system it replaces, then the existing ClusterWide licence will cover the new configuration. However, where the new system has a higher LUR, the existing ClusterWide licences may be inadequate. If they are inadequate, Digital will ‘split’ returned ClusterWide licence(s). In each case the trade-in allowance is based on a ClusterWide licence with a points value equal to that of the LUR of the traded-in system. Process steps: ¢ Customer returns (whole) ClusterWide licence(s) with the system being traded-in. ¢ Digital effectively ‘splits’ the licence(s) into the ‘traded-in’ portion and the “‘untraded-in’ portion. ¢ Digital returns, without charge, the equivalent of the ‘untraded-in’ portion in the form of ClusterWide licences in the highest possible denominations. ¢ The last listed price of the ‘traded-in’ portion is used in determining the allowance for the System Class Traditional licence in accordance with the standard allowance rule or, if applicable, the Upgrade-licence-for-free programme. Note: The returned Cluster Wide licences are not actually ordered by the customer whereas the new System Class Traditional licence must be ordered. — —-_++ Concurrent Use Licences = (Part-number: QL-upiA*-3B) The seventh character is an ‘A’ for products running on OpenVMS and an “M’ for products running on Digital UNIX. 1. Software Domain A Concurrent Use licence permits a single unspecified user to use the applicable software on any single CPU or cluster (whole or a part) running the applicable operating system. The licence is not dependent on the capacity of the hardware. 2. Redesignation A Concurrent Use licence may be redesignated to any CPU or cluster running the same operating system. Simply delete the licence from the existing system and load it into another. Ensure the licence is not ‘active’ (being used) on more than one system at any given time. 3. Migrating to Concurrent use on a different Operating system This is permitted on a one-for-one basis for the same or the equivalent product. Apply the standard allowance rule. 4. Migrating to Traditional One or more concurrent use licences may be traded-in for one or more Traditional licences for the same product (running on the same or a different platform-pair). Apply the standard allowance rule. The allowance will be 75% of the smaller of either: e che coral of che Concurrent Use licence values or e che cotal of the Traditional licence values. (If the cotals happen to be equal, take 75% of the latter.) Where the Concurrent Use value is the smaller, 75% of that total must be aportioned against the purchase of the Traditional licence(s). _ cceiibaatiia Personal Use Licences (Part-number: QL-upiA*-2B) The 7th character is an ‘A’ for products running on OpenVMS and an ‘M’ for products running on Digital UNIX. 1. Software Domain A Personal Use licence permits a single nominated user to use the applicable software, on the licensee’s behalf, on any single CPU or cluster (whole or part) running the applicable operating system. The licence is not dependent on the capacity of the hardware. 2. Redesignation A Personal Use licence may be redesignated to any CPU or cluster running the same operating system. Simply delete the licence from the existing system and load it into another. Ensure the licence is not ‘active’ (being used) on more than one system at any given time. 3. Migrating to Personal Use on a different Operating System This is permitted on a one-for-one basis for the same or the equivalent product. Apply the standard allowance rule. 4. Migrating to Concurrent Use (must be the same product) This is permitted on a one-for-one basis. Apply the standard allowance rule. Since a Personal Use licence is always cheaper than the corresponding Concurrent Use licence, the allowance will be 75% of the current list price of the Personal Use licence(s). 5. Migrating to Traditional One or more Personal Use licences may be traded-in for one or more Traditional licences for the same product (running on the same or a different platform-pair). Apply the standard allowance rule. The allowance will be 75% of the smaller of either: e the cotal of the Personal Use licence values or ¢ che total of the Traditional licence values. (If che totals happen to be equal, take 75% of the latter.) Where the Personal Use value is the smaller, 75% of that total must be aportioned against the purchase of the Traditional licence(s). CURRENT LICENSING PROGRAMMES 1. Universal Platform Guarantee Changing Operating system on Alpha Systems A customer may already have an Alpha System with a certain operating system. The customer may wish to change the operating system on the existing CPU. The following text sets out the current programme which caters for this requirement. Universal Platform Guarantee Programme When changing the operating system on an Alpha system, customers receive an allowance, based on the standard allowance rule, for the returned operating system licences towards the purchase of the new operating system licences. However, under this programme the licence migration does not require a one-for-one trade of licences. The allowance is obtained from the sum cotal of the operating system licences being exchanged for the new licence(s). This applies to OpenVMS, Digital UNIX and Windows NT/Alpha operating systems. 2. Upgrade-Licence-for-Free 100% allowance will be given for upgrade software licences when ordered at the same time as ‘In-cabinet’ upgrades or upgrades involving hardware trade-ins if and only if e the new licences are purchased from Digital or a Digital Authorised Reseller who has obtained the upgrade from Digital AND e the new CPU is in the same hardware architecture AND e the new CPU is in the same or a lower System Class AND e che type of Operating System software is unchanged AND ¢ redesignation is not permitted. If one or more of the above is not true, apply the standard allowance rule - see page 5. Note: Digital RDB product set licences and Oracle RDB products are excluded from this programme. However, the standard allowance rule may be applied. ee ee a ~ Summary: This enables a customer to convert layered product licences from Traditional or ‘ClusterWide to Personal Use or Concurrent Use, with approximately 85% discount off the price of a number of new licences. Note: The term ‘Capacity licence(s)’ is used below to cover both Traditional licence(s) and ClusterWide licence(s). The term ‘User-Based licence(s)’ is used below to cover both Personal Use licence(s) and Concurrent Use licence(s). Process steps: ¢ Divide the current price of the User-Based licence into the current price of the Capacity licence(s) being migrated. In cases where more than one licence is being migrated, the sum of the current Capacity licence prices is used. ¢ The result, (if the result is not an integer, it should be rounded up to the nearest integer), gives the quantity of User-based licences that can be ordered at approximately 15% of their normal price. So this would give the formula: CAPACITY LICENCK(s) PRICE -> C = Q (Quantity). USER-BASED LICENCE PRICE -> U There are special ‘trade-up-to-user’ part-numbers: For ordering purposes only, QL-upiA*-2B is converted to QL-upiA*-8B and QL-upiA*-3B is converted to QL-upiA*-9B. (Note: The full User-Based licence must be used in the above formula to find ‘Q’.) So the price is obtained thus: Price = Q * ‘trade-up-to-user’ licence. Note: A customer may choose to order a quantity less than ‘Q’. No further discount may be applied to the price of these licences. The Capacity licences are cancelled. APPENDIX A SYSTEM CLASSES The following hardware systems are grouped into just three System Classes for each of the two hardware architectures. The licence part-number formats in which the seventh character indicates System Class codes, are given below each of the System Classes. SYSTEM CLASS WORKGROUP & ENTRY LEVEL SERVERS Licence Part-number: DEPARTMENTAL SERVERS Licence Part-number: ENTERPRISE SERVERS Licence Part-number: VAX (OpenVMS) VAXSrations, MicroVA Xes VAX 11/7xx, VAX 4050, VAX 410xA VAX 4000-2xx, VAX 82xx, VAX 83xx VAXft 110, VAXftServer1 10-610 VAXServer 4200/4300, 6000-210/310 QL-upiAB-AA VAX 4000-300/400/50xA/60xA VAX 4000-70xA, VAX 6000-210/310 VAXfe 310-810 QL-upiA2-AA VAX 4000-500/600 VAX 6000-220/230/240/320/330 VAX 6000-340/350/360/Axx/Sxx VAX 6000-6xx, VAX 7000 VAX 85xx-89xx, VAX 9000 VAX 10000, VAXServer 6000-220/320/A4xx/5xx VAXServer 9000 QL-upiA5-AA Alpha (OSF/1, OpenVMS) AlphaStation Workstations AlphaServer 400 AlphaServer 1000 DEC 2000-300 DEC 2000-500 DEC 3000-300 DEC 3000-400 DEC 3000-600 DEC 3000-700 QL-upiAE-AA AlphaServer 2000 AlphaServer 2100 DEC 3000-500 DEC 3000-800 DEC 3000-900 QL-upiAG-AA DEC 4000, 7000 DEC 10000 AlphaServer 8000 QL-upiAQ-AA Sa ‘Chart showing ‘old’ Traditional tiers and ClusterWide ratings for VAX Systems Traditional QL-upiA*-AA —aqq G90 Ghee ON Wr oon hey Miao) Mw ClusterW ide Points ratings VAX Systems_ LUR unit-ID QL-upiA9-J* : y VS2000, VAXsrv3000/4000 10 B VS II, VS3xxx, 8000 10 B 4060/4VLC/4090 10 B MicroVax 2000/3 1xx 20 Cc MVax II 50 D VAX 730 100 E VAX 750 100 E VAX 78x 100 E VAX 82xx 100 E MV3300/3400, VAX410x/410xA 100 E VAX 83xx, VA Xsrv6210/310 200 F VAX 4200, 35/36/38/3900 200 F VAX 43/4400, 45/46/4700A, 6210/6310 300 G VAX 8530/86xx, VAXsrv 6410/20 6510/20 6220/30 400 H VAX 8550/8700/8810 600 J VAX 6220/30 6410 600 J VAXsrv 4500, 91/9310, VAX 45/4600 62/6330 6510 900 K VAXsrv 9320/30/40, VAX 6240/6340/6350/6420 1200 L VAX 6610/7610/8800/8820/10610 1200 L VAX 6360/6430/6520/6620/7620/8830/10620 1800 M VAX 6440/6450/6460/6530/6540/6550 2400 N VAX 6560/6630/6640/6650/6660/7630 2400 N VAX 7640/8840/8842/8974/9210/9410/106xx 2400 N 3600 Q VAX 8978/9420/9430/9440 4800 S 6000 We 7200 U 9000 Vv j Alpha Systems 3400, 3400S, 2300S, 3300, 3300S, 3600, 3600S, 2500, 3300LX, 3300X 3500,3500S, 3500X,3800, 3800S, 2100-500 4610, 4710 7610, 4620, 4720 APPENDIX C Chart showing ninth character codes for Operating System Base and SMP Extension licences and, where available, those Unlimited Interactive User licences ordered prior to October 10th 1994. For Alpha Systems the seventh character code is also given; for VAX systems the seventh character code is found in Appendix B. QL-upiA* - 6* vy @7 @9 1) ah BB Jey 7 {Ce EOE Ever Ex &G Boner BJ E K ease aN eh AR nS) ey a G A G B Ge G D Ga Gr G G G H Alpha Systems DEC/3400s DEC/3400 DEC/2300s DEC/3300 DEC/3300L DEC/3600s DEC/3600 DEC/2500 AlphaStation 400 4/233 AlphaStation 400 4/233, AlphaScation 200 4/233 DEC/3700 AlphaServer 1000 4/200 AlphaStation 250 4/266 AlphaStation 200 4/100 DEC/3500S DEC/3500/3500X DEC/3800S DEC/3800 AlphaServer 2100 4/200 DEC/3900 AlphaServer 2000 4/200 AlphaServer 2100 4/275 QL-upiA* - 6* YY @7 @9 yo as yj 13 y€ IL fa N B (Q.) sn OE ©) € ORD 9 A ) 133 DE 9 D 9° E O} IP @} Isl ed) OURS o) 8) DEC/4610 DEC/47 10 DEC/7700 DEC/7610 DEC/10610 AlphaServer 8200 Uni AlphaServer 8400 Dual AlphaServer 8200 Dual AlphaServer 400 Uni DEC/7600 SMP DEC/10600 SMP DEC/4600 SMP DEC/4700 SMP AlphaServer 2000 4/200 SMP, 2100 4/200 SMP DEC/7700 SMP AlphaServer 2100 4/275 SMP AlphaServer 8200/8400 Dual SMP AlphaServer 8200/8400 Uni SMP ALPHA Generic QL-upiA*-6* 8 «= VAXstation 4000/60 N VAXstation 4000 VLC B VAXstation 4000/90 A MicroVAX 3110¢ Zi MicroVAX 3130 N MicroVAX 3140 Vv MicroVAX 318x Ww MicroVAX 319x 2 VAX 82xx A VAX 4000-100 A VAX 4000-100 A VAX 4000-50 FE VAXft 110 Ww 83xx 4 j VAX server 6000-210 3 VAX server 6000-310 2 VAX 4000-400 y. | VAXft 410 Ww ; VAXft 610 x 6000-210 2 6000-310 A VAX 4000-500A G ii VAX 4000-505A EF VAX 4000-600A D VAX 4000-700A E VAX 4000-705A G VAXft 810 Za 86xx A 8500 A 8530 8 N 6 4 5 2 3 3 2 B 2 A 3 2) =a VAX server 6000-220 oer: VAX server 6000-320 : VAX server 6000-410 VAX server 6000-420 VAX server 6000-510 VAX server 6000-520 = ae VAX (continued) 6000-330 . 6000-510 VAX 4000-500 VAX 4000-600 VAX server 9000-110 VAX server 9000-310 6000-610 6000-240 6000-340 6000-350 6000-420 8800 8820 7000-610 10000-610 VAX server 9000-320 VAX server 9000-330 VAX server 9000-340 6000-360 6000-430 8830 6000-520 6000-620 7000-620 10000-620 6000-440 6000-450 6000-460 9000-210 9000-410 6000-530 7000-630 10000-630 6000-540 6000-550 7000-640 . 10000-640 6000-560 6000-630 6000-640 6000-650 6000-660 9000-420 QL-upiA*-6* PCE ROE STeMOMO NE oS AMO OLZS> aN weI AUumUZoarunnweZuanrn Ne scabimy, ~~ + =m. -- APPENDIX D Retained traditional Tiered Priced Licences This is a list of the OpenVMS/VAX, OpenVMS/Alpha and Digital UNIX/Alpha layered products that have retained Traditional licences with tiered pricing instead of the new System Class pricing. 20/20 FOR OPENVMS VAX 20/20 GOLD Al FOR OPENVMS VAX 20/20UP GOLD FOR OPENVMS VAX ACMSXP DEVELOPMENT FOR DEC OSF/1 Alpha CA-VIVID PRESENTATION GRAPHICS FOR OPENVMS VAX VIVID PRESENTATION GRAPHICS Al FOR OPENVMS VAX DBASE IV FOR OPENVMS VAX** DECWRITE FOR OPENVMS VAX** MEP VT FOR DEC SNA 3270 APP SERVICES FOR OPENVMS VAX POLYCENTER FULLSAIL DATABASE FOR DEC OSF/1 Alpha TUXEDO SERVER SOFTWARE FOR DEC OSF/1 Alpha DECEXP SK V/V ACMSXP ACMSXP QL-VEPA*-AA QL-YQJA*-AA QL-MKZA*-AA QL-247A*-AA QL-GMWA*-AA QL-GMXA*-AA QL-YE1LA*-AA QL-VVFA*-AA QL-06CA*-AA QL-268A*-AA QL-07QA*-AA QL-MMMA*-AA QL-248A*-AA QL-249A*-AA **These cwo products changed from ClusterWide with tiered pricing to Traditional with ‘old’ tier pricing. APPENDIX E This is a list of all the OpenVMS VAX Systems that were sold with Operating System User licences (QL-001xx-xx). There are no Unlimited Interactive User licence (QL-XULA*-AA) available for these systems. There are 13 systems (see those with **) that were sold with either an Operating System , User licence (QL-001xx-xx) or an Operating System Base licence (QL-005xx-xx). An Unlimited Interactive User licence (QL-XULA*-AA) is available for those systems with an Operating System Base licence (QL-005xx-xx). (QL-005 and QL-001 must not be mixed.) VAX System MicroVAX II MicroVAX 2000 MicroVAX 3100 ** MicroVAX 3110¢ ** MicroVAX 3110e MicroVAX 3120¢ ** MicroVAX 3130 ** MicroVAX 3130 ** MicroVAX 3140 ** MicroVAX 3140 ** MicroVAX 3180 ** MicroVAX 3180 ** MicroVAX 3190 ** MicroVAX 3190 MicroVAX 3300 MicroVAX 3400 MicroVAX 3500 MicroVAX 3600 MicroVAX 3800 MicroVAX 3900 **VAXfrt 110 **VAXft 110 VAXfr 310 **VAXft 410 **VAXft 410 VAX fe Server 310 VAXft Server 410 VAXfe Server 610 VAXserver 2000 VAXserver 3100 VAXserver 3300 VAXserver 3400 VAXserver 3500 VAXserver 3600 VAXserver 3602 VAXserver 3800 VAXserver 3900 Part-Number QL-001AN-BC QL-001AP-BD QL-001AP-BM QL-001AP-BM QL-005AP-6Z QL-001AP-BM QL-001AP-BM QL-005AP-6N QL-001AP-BM QL-005AP-6V QL-001AP-BM QL-005AP-6W QL-001AP-BC QL-005AP-62 QL-001AS-BM QL-001AS-BM QL-001AB-BJ QL-001 AB-BJ QL-001AB-BJ QL-001AB-BJ QL-001 AS-BZ, QL-005AS-6W QL-001A2-BZ QL-001A2-BZ QL-005A2-6W QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AR-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA QL-001AC-BA Licence Description OpenVMS 1-2 User OpenVMS 1-4 User OpenVMS 1-5 User OpenVMS 1-5 User OpenVMS Base OpenVMS 1-5 User OpenVMS 1-5 User OpenVMS Base OpenVMS 1-5 User OpenVMS Base OpenVMS 1-5 User OpenVMS Base OpenVMS 1-2 User OpenVMS Base OpenVMS 1-5 User OpenVMS 1-5 User OpenVMS 1-20 User OpenVMS 1-20 User OpenVMS 1-20 User OpenVMS 1-20 User OpenVMS Unl OpenVMS Base OpenVMS Unl OpenVMS Unl OpenVMS Base OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMSF&A Server ‘| VAX System VAXserver 4000-200 VAXserver 4000-300 VAXserver 4000-500 VAXserver 4000-600 VAXserver 6000-210 VAXserver 6000-220 VAXserver 6000-310 VAXserver 6000-320 VAXserver 6000-410 VA Xserver 6000-420 VAXserver 6000-510 VAXserver 6000-520 VAXserver 6000-610 VAXserver 6000-620 VAXserver 6000-630 VAXserver 6000-640 VAXserver 9000-110 VAXserver 9000-310 VAXserver 9000-320 VAXserver 9000-330 VAXserver 9000-340 VAXstation II VAXstation 2000 VAXstation 3100 VAXstation 3200 VAXstation 3500 VAXstation 3520 VAXstation 3540 VAXsration 4000-60 VA Xstation 4000-90 VAXstation 4000-VLC VAXstation 8000 VAX 730 VAX 750 VAX 780/785 VAX 4000-200 VAX 4000-300 **V AX 4000-500 **V AX 4000-500 ##*V AX 4000-600 **V AX 4000-600 VAX 6000-210 VAX 6000-220 VAX 6000-230 VAX 6000-240 A [> - Ee NY D q x E (continued) Part-Number QL-001AC-BA QL-001AC-BA QL-001A4-64 QL-001A4-65 QL-001AH-A3 QL-001AG-AN QL-001AH-A2 QL-001AG-A6 QL-00LAG-A4 QL-001AG-A5 QL-001AG-A2 QL-001AG-A3 QL-001AD-6C QL-001AU-6B QL-001AV-GF QL-O001AV-6G QL-001A4-AN QL-001A4-AW QL-OO1LAD-A5 QL-001AD-AG QL-001AD-A7 QL-001AQ-BB QL-001LAR-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AC-BB QL-001AM-AA QL-O01AL-AA QL-001AK-AA QL-001AB-BL QL-001A2-BJ QL-001A4-BK QL-005A4-64 QL-001A4-BK QL-005A4-65 QL-001A2-A2 QL-001A3-A3 QL-001A4-A3 QL-001AD-A4 Licence Description OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS F&A Server OpenVMS | User OpenVMS | User OpenVMS | User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS 1 User OpenVMS Unl OpenVMS Unl OpenVMS Ual OpenVMS 1-10 User OpenVMS 1-20 User OpenVMS 1-40 User OpenVMS Base OpenVMS 1-40 User OpenVMS Base OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl ' : APPENDIX E VAX System VAX 6000-310 VAX 6000-320 VAX 6000-330 VAX 6000-340 VAX 6000-350 VAX 6000-360 VAX 6000-410 VAX 6000-420 VAX 6000-430 VAX 6000-440 VAX 6000-450 VAX 6000-460 **V AX 6000-510 **V AX 6000-510 **V AX 6000-520 **V AX 6000-520 VAX 6000-530 VAX 6000-540 VAX 6000-550 VAX 6000-560 *#V AX 6000-610 **V AX 6000-610 **V AX 6000-620 **V AX 6000-620 VAX 6000-630 VAX 6000-640 VAX 6000-650 VAX 6000-660 VAX 8200 VAX 8250 VAX 8300 VAX 8350 VAX 8530 VAX 8550 VAX 8600 VAX 8650 VAX 8700 VAX 8800 VAX 8810 VAX 8820 VAX 8830 VAX 8840 VAX 8842 VAX 9000-210 VAX 9000-410 VAX 9000-420 VAX 9000-430 VAX 9000-440 Part-Number QL-001A2-AA QL-001A3-A2 QL-001A4-A2 QL-001AD-A2 QL-001AD-A3 QL-001AU-A3 QL-001A3-AA QL-001AD-AA QL-001AU-A2 QL-001AV-AS5 QL-001AV-A6 QL-001AV-A7 QL-001A4-AA QL-005A4-6A QL-001AU-AA QL-005AU-6A QL-OO1AV-AA QL-001AV-A2 QL-001AV-A3 QL-001AV-A4 QL-001AD-6B QL-005AD-6B QL-001AU-6N QL-005AU-6N QL-001AV-6B QL-001AV-6C QL-001AV-6D QL-001AV-GE QL-001AJ-AA QL-001AJ-A2 QL-001AH-A4 QL-001AH-AS QL-001AG-A8 QL-001AE-A2 QL-001AF-AA QL-001AF-A2 QL-001AE-AA QL-001AD-A8 QL-001AE-A3 QL-001AD-AN QL-001 AU-A4 QL-001AV-AY QL-001AV-AZ QL-001AV-AX QL-001AV-A8 QL-001A5-A2 QL-001A5-A3 QL-001A5-A4 (continued) Licence Description OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Base OpenVMS Unl OpenVMS Base OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Base OpenVMS Unl OpenVMS Base OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Unl OpenVMS Un! OpenVMS Un! OpenVMS Unl OpenVMS Unl =) APPENDIX F ‘CLASSIC’ OPENVMS USER LICENCE- chart showing the number of users indicated by the ninth character of the part-number (for the seventh characters see Appendix B). QL-upiA*-B* Description QL-upiA*-B* Description y y A O User 5 3-8 User Upgrade B | User 8 5-8 User Upgrade Cc 2 Users Ww 6-10 User Upgrade Q 3 Users 6 9-16 User Upgrade D { Users U 11-15 User Upgrade M 5 Users 2 11-20 User Upgrade E 8 Users / 16-Unl User Upgrade L 10 Users S 17-32 User Upgrade P 15 Users 7 17 - Unl User Upgrade F 16 Users X 21-30 User Upgrade J 20 Users 3 21-40 User Upgrade N 30 Users NC 31 - Unl User Upgrade G 32 Users ite 33-64 User Upgrade K 40 Userss 4 41 - Unl User Upgrade H 64 Users 9 65 - Unl User Upgrade Z Unlimited Note: When applying the standard allowance rule, use a character from the left-hand column which indicates the total number of users being traded-in. Ignore the fact chat the total may have been obtained through the purchase of several upgrade part-numbers. 27 APPENDIX G Update Licensing If an appropriate Service Update Subscription licence (SUSL) is held, the underlying licence is effectively updated as new versions are released. Please note that the SUSL may be embedded within another service contract. One SUSL is required for each underlying licence. If no appropriate SUSL is held, an applicable Update licence must be purchased, corresponding to each underlying licence. For each later version used, further Update licences are required. The SUSL and Update part-numbers are given alongside the corresponding underlying licence in the diagram below. Licence QL-upiA*-6* QL-upiA9-6* QL-upiA9-BB QL-upiA*-AA QL-upiA9-J* QL-upiA*-3B QL-upiA*-2B Update Licence QL-upiA*-7* QL-upiA9-7* QL-upiA9-YB QL-upiA*-RA QL-upiA9-S* QL-upiA*-5B QL-upiA*-4B Service Update Licence QT-upiA*-L9 (-A9 a la carte) QT-upiA*-L9 (-A9 a la carte) QT-upiA-VB QT-upiA*-L9 QT-upiA9-L* QT-upiA*-DB QT-upiA*-MB To update Traditional licences replaced by System Class pricing, source the equivalent new Update licence: e.g. QL-****S-AA has been replaced by QL-****B-AA, and therefore the Update licence is now QL-****B-RA. ‘QL-upiA9-YB' licences are available only for ‘full’ licence levels. They are not available for User upgrades. If a customer has purchased a CPU with a licence for 5 users and has added a 6-10 User upgrade the customer then has a 10 user licence - not a five user and a separate 6-10 User. If the customer needs to buy an Update licence, the 10 User update licence (QL-upiA*-BL) would apply. (See Also Appendix FE.) Digital believes the information in this publication is accurate as of its publication dare; such information is subject to change without notice. Digital is not responsible for any errors. The following are trademarks of Digital Equipment Corporation: the DIGITAL logo, Alpha AXP, AXP, DEC, DEC Fortran, DECstation, DECsystem, MicroVAX, OpenVMS, VAX, VAX FOR- TRAN, VAXcluster, VAXft VAXserver, VAXstation, VMAcluster. OSF/! is a registered trademark of Open Software Foundation Inc. Windows NT is a trademark of Microsoft Corporation. UNIX is a registered crade- mark in the United States and other countries licensed exclusively through X/Open Company Led. Written by Barry Fitzgerald, for Digital Equipment Co. Limited. Designed and produced by Zone 0173-4 770288