| Title: | Dollar File System Information |
| Notice: | Use TRIFID::DOLLAR_INTERNAL QAR db for reporting problems |
| Moderator: | MOVIES::HARRIS |
| Created: | Mon Jan 31 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 241 |
| Total number of notes: | 897 |
+---------------------------+
| | | | | | | | TM
| d | i | g | i | t | a | l |
| | | | | | | |
+---------------------------+
/\
/ \ INTEROFFICE MEMORANDUM
IIII
IIII TO: OPENVMS_SEG_DIRECT DATE: 20 January 1997
/....\ OFST_PROG_TEAM FROM: Janis Horn/Mark Howell
|:\_:| OVMS Ambassadors DEPT: OFST Bus/Eng Mgmt
/ :..: \ DTN: 381.0704/824.3393
| | NODE: STAR::HORN
IIIIIIIIII MOVIES::HOWELL_MA
LOC: ZKO/EDO
SUBJECT: Updated Plan of Record for Spiralog V1.2
This change to the Spiralog POR involves a decrease in schedule
(it's shipping a month earlier!) and a reduction in project functionality.
The main goal of Spiralog V1.2 remains unchanged - ship a version of
Spiralog that runs on OpenVMS Alpha V7.1 (Gryphon) coincident with the
Gryphon FRS of 1/97.
Why the change?
---------------
Before this change to POR the Spiralog V1.2 maintenance release had three
additional sub-goals:
1) correct the volume full problem
- disks become write locked when they are full and even
deletes are not possible, thereby rendering the volume
"read-only"
2) bug fixes/maintenance
3) add performance enhancements
The volume full changes accounted for approximately 9K new lines
of code and the performance work for another 6K. Together the 15K of code
resulted in instability and a severely increasing QAR rate. Pursuing this
route would not allow Spiralog V1.2 to release "coincident with Gryphon".
What you get
------------
o Timely maintenance release of Spiralog for Gryphon customers
o Existing Spiralog V1.1 kit from Theta, rebuilt to run on Gryphon,
renamed Spiralog V1.2 with only those CLDs and Showstopper below
o Stable code base comprising 300 lines of new code, fully inspected
- 2 CLD fixes
o VMS lock consumption problem
o Backup/replace corrupts data
- Gryphon related changes
- Gryphon Showstopper SYSTEMCHECK bugcheck fixed
- Checkpoint volume data corrupter fixed
o Full QTV validation and qualification
o Minor documentation changes (Release Notes, Install Guide, SPD)
What you lose
-------------
You do not get pro-active maintenance for Spiralog. The 15K
lines of code correcting the documented volume full problem and providing
performance enhancements will remain unavailable to customers.
As OpenVMS V7.1 usage increases, an increased number of customers
will select to install Spiralog V1.2. Their first impression of Spiralog
will be colored by the volume full problem. The rectification of the
volume full problem will appear in the major Spiralog V2.0 release.
Schedule
--------
Spiralog V1.2 will submit to SSB FEB 24th. FRS is MAR 3, 97.
Spiralog V1.2 will not undergo a formal field test period, although all
CLDs will be tested against the original customer statements. Spiralog
V1.2 kits will be shipped directly to the CLD customers for confirmation
of fix.
Future Spiralog V1.n Maintenance and Resources
----------------------------------------------
Spiralog will not be maintained pro-actively. Spiralog maintenance
releases will be scheduled to coincide with new releases of the operating
system as needed. For instance, there is no plan for Spiralog V1.3; a
Spiralog V1.3 release will be built when/if needed for Raven (OpenVMS
V7.2).
The current 2 Spiralog maintainers will merge with the existing
XQP maintenance team to form a combined OFST maintenance group where XQP
and Spiralog CLDs will continued to be addressed on a prioritized basis.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 234.1 | How will v1.2 be distributed? | CSC32::BARELA | Thu Feb 06 1997 00:22 | 18 | |
Greetings,
How will Spiralog v1.2 be distributed?
The question comes up because of the following situation:
Customer upgraded to OpenVMS Alpha v7.1 and saw the reference
to Spiralog. They search the v7.1 CD and consolidated
distribution CDs and don't find v1.2 - so they call the CSC.
I explain it is not currently available but will be in March.
Customer then asks "Does that mean I will automatically get
the distribution??"
Thanks in advance,
Rod Barela
US CSC
| |||||
| 234.2 | MOVIES::MJOHNSON | Mike Johnson - VMS Europe | Mon Feb 10 1997 10:11 | 5 | |
I've forwarded your question to our Product Manager Janis (STAR::) Horn and I expect that she will be putting an answer here shortly. Mike | |||||
| 234.3 | Well.... | TOPTEN::KELLER | Tue Feb 18 1997 17:14 | 7 | |
We are still waiting on an answer here. My impression is that if
you have been running V1.1 and had a problem that has a CLD open, you
will get the new distribution; otherwise you will have to wait till it
comes out on the next release of VMS. Is this correct? If so; what can
we do to get V1.2 when it is released early March.
Larry
| |||||
| 234.4 | Automatic distribution of Spiralog V1.2 | STAR::HORN | Tue Feb 18 1997 19:29 | 33 | |
Spiralog V1.0 and V1.1 were available in two ways: 1) as an IPO (independent product offering) CD-ROM media 2) or on CONDIST Spiralog was never part of the OpenVMS Alpha operating system media and therefore you cannot "wait till it comes out on the next release of VMS" as suggested in the previous reply. Spiralog V1.2 will be available in only one way: 1) as an IPO ($49 CD-ROM media charge in the US, sorry, I don't know what that translates to in other countries) Customers who purchased the Spiralog V1.0 or V1.1 media kit will AUTOMATICALLY receive the Spiralog V1.2 media kit as a courtesy. There are no media and update services for Spiralog. The license rights and telephone support services for Spiralog _are_ bundled with those of the OpenVMS operating system, but not the media update services. The difficult part is that those customers who did not originally purchase the Spiralog media kit, but rather who pulled Spiralog off of CONDIST, will not automatically receive the Spiralog V1.2 kit. Nor is Spiralog shipping on CONDIST any longer, so those customers will have to purchase an independent Spiralog V1.2 kit if they want to upgrade. For internal use, Spiralog V1.2 will be posted in AVOLUB for general network distribution. Submission is next Monday (24 FEB 97) and FCS is 3 MAR 97. thanks for your patience, Janis | |||||