| >However, unlike the PWOSF notes conference for the UNIX product. It is
>virtually impossible to find out any details on PATHWORKS for OpenVMS
>V6.0.
Tony,
I'm sorry to hear that you've had a hard time getting info. I work so
hard to avoid that, but obviously I failed. After you read the
following, let me know what else I can do, OK?
First of all, I will put you on my pw_int.dis list. I send out a
newsletter
about every 6 weeks giving all kinds of detail on the PATHWORKS server -
including V6. If anyone else wants to be on this interest list, please send
mail to Gale Taylor at [email protected]. (I'll attach last week's
newsletter at the end of this note.)
>It may be an idea to put some details of the product and also allow
>internal people to use the FT kits as in the past. Also a pointer to
>the Web page may also be an idea. (If one exists).
The web page is: http://www.digital.com/info/pathworks
The notes file for V6 is PW-AS-V6
See the "What's New in the Next Releases of the PATHWORKS for OpenVMS
Server" document I put together for DECUS. You can get it from the web
page.
>Also the public areas on SWOPS and SUTRA do not appear to have been
>updated.
I'll look into that.
Regards
Gale Toale Taylor
DIGITAL PATHWORKS for OpenVMS Product Manager
DIGITAL Equipment Corporation
550 King Street
Littleton, MA 01460
* [email protected]
( DTN: 226-6276
( Tel: +508-486-6276
( Fax: +508-486-5323
Visit our Web Site http://www.digital.com/pathworks
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
o This newsletter is available online at:
http://prodmgt.lkg.dec.com
You have received this newsletter because you are on the PATHWORKS for
OpenVMS interest list. If you would like to change your address or be
dropped from this list, send mail to Gale Taylor at [email protected].
o Infocenter
The external PATHWORKS Infocenter is at
http://www.digital.com/info/pathworks
The web page has recently been updated by Allen Nicholson. Check it out!
Contents
========
o Product releases
o V5.0F
o PATHWORKS V6.0 EFT4
o OpenVMS Delta-Time issue.
o SPDs revised for PATHWORKS for OpenVMS V5.0E
o New Cover and Packaging Graphics
o PATHWORKS Accommodating Corporate Branding Guidelines
o PATHWORKS - Related DECUS Sessions at a glance
o Kanji support in V6
o Year 2000 Ready Update
o Pointer to PATHWORKS presentation materials used in Europe training
o Check out Software Sales Link for PATHWORKS!
o List of PATHWORKS Product Management Contacts
o Locating PATHWORKS Training
o PATHWORKS Marketing/Operational Plan
o PATHWORKS at THOT (Technical Hands-On Training: April, 1997)
o What's New in PATHWORKS Licensing and Business Practices?
o New Product Brief
o V6 Documentation Review
o News on the Pointcast ad
Details
=======
o Product releases
The current kit in SSB and TIMA is V5.0E-ECO1.
Will submit V5.0F kit to SSB on June 30th.
V6 SSB code freeze on July 7, and SSB submit Aug 4, 97 (Alpha only, VAX 3
months later)
o V5.0F
PATHWORKS V5.0F/V1.0F for OpenVMS Server will be distributed to customers
as an ECO (patch kit) through TIMA as well as a standard SSB release.
The submit date for the V5.0F kit to SSB is June 30th. We are able to meet
the Alpha CONDIST for an FCS of August 22. July 23rd is the deadline for
Alpha CONDIST/CONOLD product/submission.
Documentation submission will remain at the previous date of June 16th.
For Alpha Systems, minimum software is OpenVMS Alpha Operating System
V6.1, V6.2, V7.0, V7.1.
For VAX Systems, minimum software is OpenVMS VAX Operating System
V5.5-2, V6.1, V6.2, V7.0, V7.1.
Includes fixes (including DELTA time correction). No new functionality
except backport the capability to treat a "Client Access" license as a
server license as well as a client license.
o PATHWORKS V6.0 EFT4
We do plan to release one more field test update prior to the FCS release
of PATHWORKS V6. Currently the plan is around mid to late June. Since EFT4
will be our final field test release, we are leaving the release date a
little flexible at this point to ensure that we can capture the closest
version to the SSB kit.
Right now the extended team is working extremely hard and working long
hours to bring you V6. If you could lend a hand, let us know!
o OpenVMS Delta-Time issue.
The OPENVMS operating system has a documented delta-time restriction that
may cause a serious error in some applications and the OPENVMS components
beginning on or around 19-May-1997. Digital has provided ECOs that
remove the delta-time limit. Digital strongly recommends that all
customers running the affected versions of OPENVMS install the
appropriate ECO.
The PATHWORKS for OpenVMS group has tested the product in order to assess
the impact of the restriction.
In order to determine if the PATHWORKS for OpenVMS products are affected
by the delta-time restriction, a search of the code base was done. From
this investigation it appears that the PATHWORKS for OPENVMS V5.0E Server
product need not be recompiled or re-linked. However, in support of
future releases, we will install the VMS ECO and re-link our images.
PW V4.2 users should install the OVMS ECO and will not experience any
problem.
Gary Olsen at the CSC indicated that there were 6-7 cases where customers
reported problems as of last week. PATHWORKS users were trying to create
new files and getting incorrect dates (January 18th, 1998). CSC (Gary
Olsen) advised them to apply the ECO. After customers applied the VMS ECO
patch, the problems were fixed.
At this time we do not know exactly how many of these customers are running
and/or V5 servers - but the patched worked for all the customers.
o SPDs revised for PATHWORKS for OpenVMS V5.0E
The LAN Manager SPD and the NetWare SPD have been revised by John Gorczyca
to reflect the new licensing business practices.
LAN Manager SPD number: 30.50.20
NetWare SPD number: 44.47.06
o New Cover and Packaging Graphics
In connection with the Enterprise Integration Packages, and the new
Corporate Branding Guidelines, PATHWORKS will have new Packaging graphics.
We will be dropping the use of the cascading PCs, and using the new
"highways" graphic developed by Sametz and Blackstone.
This graphic will form the basis of (at least) PATHWORKS V6 for OpenVMS and
also PATHWORKS 32 7.1.
o PATHWORKS Accommodating Corporate Branding Guidelines
Several aspects of the documentation are being revised to include the word
DIGITAL (in all uppercase) before product names. For example, PATHWORKS
for OpenVMS is now DIGITAL PATHWORKS for OpenVMS.
o PATHWORKS - Related DECUS Sessions at a glance
These Powerpoint files will be available via our Web page as soon as the
speakers get a chance to send them to us.
Description Date Time Room Who
Enterprise Integration Overview 5/19/97 2:00 PM 203 Rob Emsley
UNIX/NT Integration 5/19/97 5:00 PM 200 Will McGrath
PATHWORKS Licensing 5/21/97 1:00 PM 260 Rob Emsley
PATHWORKS Hints and Kinks 5/21/97 2:00 PM 202 Brad Cooper
PATHWORKS 32 Overview 5/21/97 3:00 PM 202 Ken Robinson
PATHWORKS Panel 5/21/97 4:00 PM 202 Panel
PATHWORKS Strategy 5/22/97 10:00 AM244 Rob Emsley
PATHWORKS V6 Architecture 5/22/97 11:00 AM244 Steve Kennedy
PATHWORKS V6 Troubleshooting 5/22/97 1:00 PM 244 Mike Stewart
PATHWORKS V6 Migration 5/22/97 2:00 PM 244 Steve Kennedy
o PATHWORKS - Related Spring DECUS Seminars at a glance
Description Date Room Who
V6 Advanced Configurations 5/18/1997 S314 Steve Kennedy
Migrating to Windows NT 5/18/1997 S320 Brad Cooper
Integrating the Microsoft
Solutions with PATHWORKS 5/18/1997 S319 Gary Mauler
o Kanji support in V6
At this time, we are not planning to include the KANJI support into the V6
release stream. This is because of the following reasons:
o The fix is not yet tested to ensure no side effects are
introduced to other components of the product (in V5 stream)
o Current V5.0F plan does not include the integration of
these changes
o Risk to the V6 code stream is very high
We plan to include Kanji support targeted to release in the follow-on V6
ECO after the fix is integrated into V5 code stream and released to
customers.
o Year 2000 Ready Update
Our PATHWORKS Year 2000 investigation is still underway we plan to document
our results for customers and then decide how we will deliver Year 2000
solutions (phase 2). We will wrap up the investigation this month.
Investigation includes identifying and documenting any problem areas which
means reviewing all source code for modules that contain time and date
related data fields. There are a total of 2437 modules. This
identification phase will be completed this month. Phase 2 involves
resolving these problems via an ECO or V6.0A by the end of this calendar
year.
Further information as well as general discussion can be found in the
EVMS::Y2K notesfile.
Ronnie Cheng has written a project plan that addresses the how and when
PATHWORKS V6 will meet the OSSG Year 2000 project requirements.
This project is limited to only source code released in the PATHWORKS V6
for OpenVMS (Advanced Server). It does not include any source code
released in the PATHWORKS V1.0G for OpenVMS (NetWare) although it is
shipping as a joint kit with the Advanced Server.
o Pointer to PATHWORKS presentation materials used in Europe training
http://prodmgt.lkg.dec.com/taylor/
Documents used for Gale Taylor's trip to UK DECUS, Germany DECUS and CSC
Training. The following documents are included on this web page:
Info Sheet
o PATHWORKS for OpenVMS Futures
o PATHWORKS Client Futures
Guide
o PATHWORKS Ordering Guide
o PATHWORKS Resource Guide
o PATHWORKS Business Practices Field Advisory
White Paper
o PATHWORKS for OpenVMS Integrating with Windows NT
Sales Update Articles
o DIGITAL PATHWORKS 32 V7.0
o DIGITAL eXcursion Migrates to DIGITAL PATHWORKS 32
o DIGITAL Enterprise Integration Packages
SPD's
o DIGITAL PATHWORKS 32 V7.0 SPD 5633
o PATHWORKS for OpenVMS (LAN Manager) SPD 3050
o PATHWORKS for Digital UNIX (LAN Manager) SPD 35
Presentations (MS Powerpoint)
o PATHWORKS Overview and Futures
o PATHWORKS 32 V7.0
o PATHWORKS Servers
o Digital Enterprise Integration Packages
o PATHWORKS Business Practices
o Check out Software Sales Link for PATHWORKS!
PATHWORKS Prospecting and Selling templates are on SSL. Thanks to Dave
Ellison, the PATHWORKS for OpenVMS `Prospecting' content, as well as the
new `Selling' content are ready. The Selling Support Information is broken
down into four major categories; Prospecting for Customers, Selling the
Product, Service Options, and Marketing, Sales and Delivery Resources.
The URL is:
asewww.zko.dec.com/spo/prod/pwksvms/map.htm
o List of PATHWORKS Product Management Contacts
(Thanks to Allen Nicholson)
Rob Emsley (Acting) [email protected] DTN 226-6443
DIGITAL PATHWORKS 32
DIGITAL PATHWORKS for DOS and Windows
DIGITAL PATHWORKS for Windows NT
DIGITAL PATHWORKS for OS/2
John Gorczyca [email protected] DTN 226-6274
DIGITAL PATHWORKS for OpenVMS (NetWare)
Gale Taylor [email protected] DTN 226-6276
DIGITAL PATHWORKS for OpenVMS (LAN Manager)
Jeff Babington [email protected] DTN 226-6882
DIGITAL PATHWORKS for Macintosh
DIGITAL PATHWORKS for OpenVMS (Macintosh)
Ann Millard [email protected] DTN 381-6403
DIGITAL PATHWORKS for DIGITAL UNIX (Advanced Server)
DIGITAL PATHWORKS for DIGITAL UNIX (NetWare)
o Locating PATHWORKS Training
(Thanks to Allen Nicholson for this info)
Go to http://www.globalknowledgenetwork.com/
Click on the revolving globe in top left frame.
Click on the flag for the country of your choice.
Assuming you have clicked on the U.S. flag, you will see the "Interactive
Catalog" page in the right hand frame.
Click on the FIND button at the bottom left to reach the "Product Keyword
Index" page.
Scroll down and click on PATHWORKS, and will see the following:
PATHWORKS
Integrating Windows NT, Windows 95 and PATHWORKS
Multi-NOS Integration: Windows NT/Windows 95 +/-
NetWare/PATHWORKS
PATHWORKS V1.0 for OpenVMS (NetWare)Inst & LAN Management
PATHWORKS V5: Advanced LAN Management for the OpenVMS Server
PATHWORKS V5: Configuring a Multivendor Client
PATHWORKS V5: Installing & Configuring the OpenVMS (LAN Mgr.)
Server
PATHWORKS V5: Installing & Configuring Digital UNIX Server (LAN
Mgr.)
PATHWORKS V5: Overview and Differences
PATHWORKS V5.1 to V6 Client Update Seminar
PATHWORKS V6: Installing and Configuring a Multivendor Client
o PATHWORKS Marketing/Operational Plan
The address is: http://visavi.zko.dec.com/
Then choose Marketing Operations Plans and then PATHWORKS.
o PATHWORKS at THOT (Technical Hands-On Training: April, 1997)
The "NT Integration with OpenVMS - Installing and Configuring PATHWORKS
Version 6.0 on OpenVMS 7.1 Alpha" lab was originally presented at
Digital s Technical Hands-on Training, or THOT, in April, 1997, in Nashua
New Hampshire.
This lab was Track 3 of the OpenVMS section of THOT and was led by Mike
Aurigemma and Larry Bonnette of the Open Systems Software Group's
Engineering Support group based in Littleton Massachusetts.
The lab was restaged and videotaped. This video program presents an
abbreviated version of this lab, which was 4 hours long during the live
session. It is abbreviated only in that the video format allows the viewer
to pause the taped presentations while software installations take place,
thus compressing the total running time of the tape.
The tape has been created for three primary audiences:
- For attendees at the April THOT session who want a
refresher or more time on the labs but with the added benefit of
having the instructors present the information, versus just using the
lab workbooks that are available on the CD or the Web as the sole
instructional aid.
- For someone who did NOT attend the April THOT session and needs to
understand the information presented in the lab.
Finally, this video is for anyone who attended the training in April
and has been asked to conduct a training session back at their company
for other technical support personnel who did not attend. The tape is
used as an instructional aid for this purpose, to supplement the live
presentation or as a train-the-trainer tool.
The video program comes with a Student Guide that outlines the sequence of
the labs, plus individual workbooks for each lab. The workbooks mirror the
screens shown on the tape and are provided as a hard copy supplement to the
video. Each lab is identified by its number in the upper right hand
corner of the TV screen. This not only ensures that viewers always know
where they are, but it also allows you to advance to sections of the tape
according to your immediate informational needs.
Please note that the labs are presented in real-time. Whenever an
installation takes more than ten to fifteen seconds, you will see and hear
a pause tape or stop tape instruction. This pause allows you to
perform the software installation without the videotape getting ahead of
your place on the tape.
The ways you can use the tape are:
For individual learning at your own pace,
- place the VCR and TV next to your system and follow along on
your system in real-time. or
- you can view the tape and make notes in your workbook and then
do the on-line operations at another time if it is inconvenient
to set up the VCR system next to your computer system.
Or it can be used in a classroom situation,
- if someone is going to facilitate the lab similar to THOT
where there is more than one student, set up the VCR/TV and
computer systems in a lab environment.
The format for the 9 lab modules presented here includes a brief
introduction to each by Larry Bonnette, then Mike Aurigemma conducts
the lab session; finally, Larry summarizes the lab before introducing
the next module.
The labs are:
Lab 1 starts by first installing and configuring PATHWORKS
Version 6.0 on OpenVMS V7.1 and on Alpha systems.
Lab 2 introduces the features of the new License Management
Interface and how to use them.
In Lab 3, you will create a Share using the NT Server Manager.
Lab 4 shows you how to create and use Print Shares on OpenVMS.
In Lab 5, you'll install and configure PATHWORKS 32 on NT
Version 4.0.
Lab 6 takes you through installing and using the new PowerTerm
Emulator.
In Lab 7, you will be creating a Trust with an NT
Version 4.0 Domain.
Lab 8 shows you how to configure and use the new Single Sign-on
Component of PATHWORKS.
And finally, Lab 9 takes you through how to use PATHWORKS new
Password Assist Component.
Files for these are available in:
TNPUBS::DISK$PROJECT3:[2KP0850.PUBLIC.THOT]
o What's New in PATHWORKS Licensing and Business Practices?
The "What's New in PATHWORKS Licensing?" document came up on the PATHWORKS
InfoCenter! Please check it out for complete information. We have also put
together a brief 1 page (2 sides) handout that summarizes the changes. This
is available via the Web Page. Attached is the text version:
What's New in PATHWORKS Licensing and Business Practices?
PATHWORKS is pleased to announce new licensing and business practices
designed to streamline and simplify purchasing PATHWORKS licenses.
The new business practices will be rolled out in 2 steps:
1. Step 1 took place in February, 1997 when we shipped PATHWORKS
32 V7.0 and introduced the new PATHWORKS 32 System License.
2. Step 2 will occur when we ship Version 6 of the PATHWORKS for
OpenVMS Server in August, 1997 when we introduce the new Client
Access License.
PATHWORKS 32 V7.0 System License
Available since February, the PATHWORKS 32 System license is the only
license you need for the PATHWORKS client software. Order a single license
for any of the following products:
PATHWORKS 32 V7.0 (includes PowerTerm and eXcursion)
PATHWORKS V6.0 for DOS/Windows
PATHWORKS V5.1 for OS/2
Order these new licenses in increments of 1, 10, 25, 50, 100, 250, 500, or
1,000 users. Note that the 1-user license price is $250, but the 1,000
user price is only $87 per user. In Step 1 of the licensing simplification
process, new PATHWORKS 32 System licenses were shipped to customers
presently under service contracts for Right to New Versions (RTNV) to CNS
and CCS licenses for the following products:
PATHWORKS for DOS and Windows
PATHWORKS for OS/2
PATHWORKS for Win NT
eXcursion
If you do not have RTNV, you can still upgrade to PATHWORKS 32 V7.0
(includes eXcursion V3.0) from:
PATHWORKS V6 for DOS and Windows
PATHWORKS V4.1B for Win NT
PATHWORKS V5.1 for OS/2
eXcursion 2.1
Upgrade prices remain unchanged at $99/license
Note: PATHWORKS 32 license only replaces the rights pertaining to the
client software component of the CCS license.
PATHWORKS Client Access License
This new license will be available with PATHWORKS V6 for OpenVMS (Advanced
Server) in late August, 1997 and will be the only license required for
access to the PATHWORKS for OpenVMS (LAN Manager) server. This new
license replaces the Designated Access (formerly, FPA) and PC Concurrent
(formerly, FPS) licenses for PATHWORKS for OpenVMS (LAN Manager) servers.
This new Client Access license combines the rights you had with your
Designated Access and PC Concurrent licenses. This new Client Access
license is equivalent to the license Microsoft sells with NT servers. You
decide how you want to implement the licenses and you can change at any
time! There are 2 modes to choose from:
Server-based Concurrent Use License
Designated - allocate to a particular client any number of V5 or V6
servers Use the same way you use Designated Access and PC Concurrent
licenses today. The rights are the same, the mechanics are different. For
example: If you have a PAK for 100 licenses, divide the licenses available
for concurrent vs. designated (per seat) use. The new License Manager
available with Version 6 helps you to manage these licenses.
Migrating to the new licensing scheme. The PATHWORKS V5 for OpenVMS servers
will be able to use the Client Access licenses. We will be providing
customers some simple tools that will allow them to easily upgrade all
their existing clients to these new Client Access licenses, no matter what
licenses they are currently using.
Kit Update Service for PATHWORKS Server Software. A new H-kit will be
shipped to PATHWORKS for OpenVMS (QA-A93AA-Hx) MDDS customers. This will
give customers the licensing software to use the new Client Access license
with the new V6 server. A new Client Access license will be shipped to
customers under RTNV contract for PATHWORKS for OpenVMS (LAN Manager)
licenses: (CCS, FPA and FPS)
Note: Client Access Licenses will be the only license sold for PATHWORKS
for OpenVMS (LAN Manager) Servers. The old licensing will still be
offered for the NetWare and Mac servers
CCS Licenses Retired
The CCS license 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 upgrading the client or server since they are no longer tied to
one another. If You Currently Have CCS Licenses, you have already received
the PATHWORKS 32 license which replace the rights pertaining to the
client software component of the CCS license. It does not provide rights to
access server software. The CCS license you have will continue to be valid
for access to your current servers. In August you will receive a Client
Access license to replace the server access component of your CCS license.
If you want to add clients you have 2 options:
o Buy one PATHWORKS 32 license and buy a license to access your server
o Consider one of the License Packages. These packages contain both client
and server licenses which means it completely replaces the rights provided
by the CCS license.
Three license packages have been introduced that replace the seven CCS
licenses:
1. The DIGITAL Enterprise Integration Client for Microsoft Windows License
Package (QM-5LWAA-Ax), replacing all �LAN Manager� CCS licenses, which
includes
- a DIGITAL PATHWORKS 32 V7.0 license
- a PATHWORKS V5.0 (LAN Manager) Designated Access license
- a Teamlinks Mail for Windows license
- a DIGITAL MAPI Driver for ALL-IN-1 license
2. The DIGITAL PATHWORKS License Package for NetWare, replacing all
�NetWare� CCS licenses, which includes
- a DIGITAL PATHWORKS 32 V7.0 license
- a PATHWORKS V5.0 (NetWare) Designated Access license
3. The DIGITAL PATHWORKS License Package for Macintosh, replacing the
�Macintosh� CCS license, which includes
- a PATHWORKS V1.3 for Macintosh license
- a PATHWORKS V1.3 (Macintosh) Designated Access license
Visit our Web Site:
http://www.digital.com/pathworks
o What is the rationale for the retirement of the "2K6" part number?
The rationale is to make ordering PATHWORKS products much simpler.
Prior to February 3rd, if a customer had an Intel-based PC on their desktop
and wanted/needed to use PATHWORKS client software, they had 8 licensing
options. These options differed by desktop operating system and by
PATHWORKS server type that the client might be using. This was very
confusing to sales channels as well as to new customers and made buying or
selling PATHWORKS products seem overly complicated. We got that message.
In addition, there were many customers who were migrating from one desktop
operating system to another which meant that they needed to face these
decisions and expense yet again. They also were not happy...and we got
that message.
So, in February, we simplified the task of choosing a PATHWORKS license for
Intel-based systems; we now offer only 1 license, the PATHWORKS 32 license,
QM-5LKAA-Ax. All other licenses were retired.
o Did PATHWORKS prices go up? NO!!
Though it was true that a single 2K6 license was less expensive than a
single 5LK license, in February we also introduced volume-based pricing for
all PATHWORKS licenses which means that buying 5LK licenses *can be* less
expensive than buying 2K6 licenses if purchased in moderate volumes. In
the US the break-even price point is 25 licenses.
Finally, the customer should be made aware of the fact that the 2K6 license
was for a software product, "PATHWORKS for Windows NT", that has be
superseded by the "PATHWORKS 32" product that not only provides more
capabilities, but greatly improves the major component of the old product,
DECnet. We will be offering and supporting the old code only until the end
of this calendar year, so it is important that this (and other still
customers using the older code) begin to make plans to migrate to the new
software.
o New Product Brief
A new product brief will be available shortly. A preliminary version was
distributed for review, however it was decided that it was too general, and
will be re-written to address V6. Stay Tuned!
o V6 Documentation Review
The Concepts and Planning Guide has ended final review. Reviewers should
contact Liz Gabel.
The Commands Reference Manual was just distributed for final review.
Reviewers should contact Anne McKinnon.
o News on the Pointcast ad
The ad did go out in April. AT&T had more than 400% increase in hits to
the ASU web site! The key is turning the increase in hits and activity to
increase in sales.
|
| I gave you the external web page and this is only on the internal.
Sorry about that!
Here is the text the .doc file is available at:
http://prodmgt.lkg.dec.com
Gale
-----------------------------------------------------------------------
What s New in the Next Releases
of the PATHWORKS for OpenVMS Server?
The next releases of the PATHWORKS for OpenVMS server include:
* PATHWORKS V5.0F for OpenVMS (LAN Manager)
* PATHWORKS V6.0 for OpenVMS (Advanced Server)
PATHWORKS V5.0F for OpenVMS (LAN Manager)
Expected availability in late June, this release provides Windows NT
Server interoperability and OpenVMS clustering. Based on Microsoft LAN
Manager 2.2, the PATHWORKS server can be a Backup Domain Controller to
Windows NT. V5.0F will support OpenVMS V7.1 (both VAX and Alpha). New
functionality includes support for new Client Access license and new
business practices designed to simplify PATHWORKS licensing.
PATHWORKS V6.0 for OpenVMS (Advanced Server)
Expected availability in late August, 1997, this release provides
seamless Windows NT Server interoperability, enhanced with OpenVMS high
availability and failover clustering technology. Based on Microsoft
Windows NT protocols, V6 provides compatible and seamless
interoperability with a Windows NT server in a domain by supporting
both the primary domain controller and the backup domain controller
roles. In addition, PATHWORKS V6 for OpenVMS provides full support of
the trust feature available in the Windows NT Server. These features
enable OpenVMS to fully participate in a network with a Windows NT
server, and provides better support for Windows NT and Windows 95
workstations. PATHWORKS V6 for OpenVMS allows the PATHWORKS server to
be functionally equivalent in a domain that spans a wide area and
includes Windows NT V4.0 servers.
PATHWORKS V6 for OpenVMS provides file and print services to support an
environment of PCs running Windows NT, Windows 95, Windows for
Workgroups, and PATHWORKS clients. PATHWORKS V6 for OpenVMS will
continue to interoperate with a PATHWORKS V5 server, and LAN Manager
V2.2 Server as "down level" server.
PATHWORKS V6 for OpenVMS provides a comprehensive command line
interface to manage a PATHWORKS V6 Server, both locally and remotely.
Other functionality offered in PATHWORKS V6 for OpenVMS includes:
o Both local area and wide area domain support
o Trusted domain support - supports one centralized user database that
provides authentication between domains so users can access resources
in other domains. This concept is known as a trust.
o Browser support, including the ability to be browsed by a Windows for
Workgroups client, Windows 95, and Windows NT. V6 also provides the
capability to participate as a Master Browser or a Backup Browser on
the NT network.
o Single sign on (also called password synchronization) will provide an
external authentication mechanism allowing users log on validation to
systems other than OpenVMS. There will be only one password between
OpenVMS and Windows, thus there is no synchronization problem.
o Windows NT-like event logging support, including alert and auditing
services.
o PATHWORKS Configuration utility to provide server configuration
support.
o Upgrade utility to assist the migration process from V5 to V6
PATHWORKS V6 will support OpenVMS Alpha V7.1 only. (VAX Support will
follow in V6.0A)
PATHWORKS for OpenVMS V6.0A
Expected availability in December, 1997, this release provides OpenVMS
VAX V7.1 support.
V4.x Support
Support for PATHWORKS for OpenVMS V4.x ended on December 31, 1996.
More Information:
http://www.digital.com/pathworks/ or
http://www.europe.digital.com/info/pathworks/
Last Updated: May 16, 1997
This document contains pre-release information about a future product.
The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
|