T.R | Title | User | Personal Name | Date | Lines |
---|
2075.1 | | CRONIC::LEMONS | And we thank you for your support. | Tue Sep 17 1996 14:43 | 8 |
2075.2 | ECO SLSE01028 available.. | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Thu Oct 10 1996 14:29 | 17 |
2075.3 | < New ECO kit coming soon > | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Tue Nov 05 1996 14:10 | 33 |
2075.4 | SLSE02028 status... | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Thu Nov 21 1996 07:26 | 18 |
2075.5 | SLSE02028 status update.. | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Tue Dec 10 1996 12:22 | 4 |
2075.6 | Updated release schedule... | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Fri Dec 13 1996 13:16 | 55 |
2075.7 | What about upgrade to OVMS v7 + | KERNEL::ANDERSONS | | Wed Jan 08 1997 01:56 | 12 |
2075.8 | Re: updgrade to v7 + | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Wed Jan 08 1997 07:59 | 24 |
2075.9 | | CRONIC::LEMONS | And we thank you for your support. | Wed Jan 15 1997 13:32 | 7 |
2075.10 | FT plans.. | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Fri Jan 17 1997 07:55 | 11 |
2075.11 | | CRONIC::LEMONS | And we thank you for your support. | Fri Jan 17 1997 08:56 | 5 |
2075.12 | V2.8A now available | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Wed Jan 29 1997 14:31 | 7 |
|
SLS V2.8A and MDMS V2.8A kits are now available.
See note 3.25.
|
2075.13 | Revised schedule for V2.9.. | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Fri Feb 28 1997 13:23 | 51 |
|
Revised SLS/MDMS release schedule:
----------------------------------
V2.9-FT1 is now available. See note 3.27 for details.
It appears that we won't be able to release V2.9 in
April as had been planned. We encountered more technical
problems than expected with VMS 7.0/7.1 (these problems were
in SLS; not VMS).
Here is an updated schedule. The estimated dates are for internal
use only.
Release Goals Release Date
------- ------- ------------
V2.8A Mandatory update superceded eco's 22-Jan-1997
SLSEO1028 and SLSE02028 and included:
- SLS/MDMS support for Decnet-Plus (OSI)
- RDF V4.1A which supports Decnet-Plus and
OpenVMS V7.0. V7.1 support is contingent
on field test results.
- MDMS-Only support for OpenVMS V7.0
and 7.1.
- SLS will be installable on neither
V7.0 nor V7.1
V2.9 All V2.8A features plus
- SLS support of OVMS 7.0 and 7.1
- SLS support of DECnet-Plus (OSI)
- Additional bug fixes for SLS and
MDMS.
V2.9 Schedule:
FT1 Start Planned: 02-Feb-97 Actual: 28-Feb-97
FT2 Start 16-Apr-97
FCS Q1FY98
|
2075.14 | Sample Procedure Available? | CHTRBX::HESHELMAN | | Wed Apr 16 1997 16:20 | 6 |
| My customer found a DSN article documenting some workarounds for using SLS V2.8A
on OpenVMS V7.X. The final paragraph mentions that an example backup procedure
is available from Digital Customer Support. Where can I obtain a copy of this
sample procedure?
-jim
|
2075.15 | Command Proceddure in the STARS artiicle "Can SLS Style Backups Be Performed On OpenVMS V7.n Systems?" | CX3PST::WSC217::SWANK | David | Thu Apr 17 1997 12:31 | 118 |
| >My customer found a DSN article documenting some workarounds for using SLS
>V2.8A
>on OpenVMS V7.X. The final paragraph mentions that an example backup procedure
>is available from Digital Customer Support. Where can I obtain a copy of this
>sample procedure?
\
\Jim,
Your customer is referring to the STARS article "[SLS] Can SLS Style Backups Be
Performed On OpenVMS V7.n Systems?". There are three workarounds. See if one
of the first two will allow for SLS backups of V7.x system's disks. They are;
QUESTION:
SLS is not currently supported for use under OpenVMS Versions 7.0 or
7.1. Is there a workaround for using SLS style backups on OpenVMS
V7.n?
ANSWER:
The following workarounds provide different options for performing SLS
style backups for SLS clients running OpenVMS V7.0 or V7.1.
WORKAROUND 1:
SLS clients running OpenVMS V7.n, who are VMScluster members with a
V6.2 member, can have the V6.2 system perform normal SLS system
backups on the V7.n system's MSCP-served drives.
WORKAROUND 2:
Standalone SLS clients can use Archive/Backup for OpenVMS (ABS) V2.1
in place of SLS in conjunction with Media and Device Management
Services (MDMS) V2.8A (or above), DECwindows Motif[R] for OpenVMS
V1.2-3 (or above) and optionally the POLYCENTER Scheduler OpenVMS
version supported under the OpenVMS V7.n.
This workaround requires additional product licenses for all ABS,
DECwindows Motif and/or POLYCENTER Scheduler.
If the aboce two workarounds can not be used then the third one states;
WORKAROUND 3:
For SLS only sites, with standalone clients or with VMScluster member
clients without an OpenVMS V6.2 member, install MDMS client V2.8A on
the OpenVMS V7.n system. Configure the MDMS V2.8A client as a remote
client to a SLS server running SLS V2.5 through V2.8 on OpenVMS
V5.5-2 through V6.2. Write a backup procedure on the OpenVMS V7.n
client that does the following:
o allocates a volume (STORAGE ALLOCATE)
o selects a drive using the volume just allocated (STORAGE SELECT)
o loads and mounts the volume as foreign (STORAGE LOAD /MOUNT)
o uses its own backup command that creates a list file on the
SLS server for each disk (BACKUP/LIST)
o submits a remote job on the SLS server of SYSREADLIST for
each disk (SUBMIT/REMOTE)
o dismounts and unloads the volume (STORAGE UNLOAD)
NOTE: An example backup procedure is available from Digital
Customer Support for a nominal charge. To obtain a
copy of this procedure, please contact Digital Customer
Support and reference this article.
The command procedure does the basic commands listed above.
In the customer non-viewable section it states;
When a customer requests the backup command procedure referred to
in this article, refer to the "COMMAND PROCEDURE" section below for
further instructions.
.
.
.
COMMAND PROCEDURE:
The following command procedure is available as a Value Pak under
consulting or Revenue Opportunity (ROP) terms and conditions.
Please refer to your ROP representative for complete details.
*** ATTENTION SPECIALISTS ***:
The cover letter and Proposal and Statement of Work (see below) must
be faxed to the customer to obtain their written approval and
Purchase Order Number or credit card authorization before the
command procedure may be sent to the customer. The customer must
also fax the signed Proposal and Statement of Work back to us prior
to receiving the command procedure. Verbal authorization cannot be
accepted.
The command procedure, cover letter and Proposal and Statement of Work
are all in the article's customer non-viewable sections.
\
\The cost is a fixed priced US $500.00.
\
\Regards, David
|
2075.16 | Revised schedule for V2.9 | COOKIE::MCCLELLAND | Marty, SLS/MDMS Engineering | Fri May 02 1997 11:26 | 50 |
|
Revised SLS/MDMS release schedule:
----------------------------------
V2.9-FT2 is now available. See note 3.30 for details.
We have scheduled in another Beta release (FT3).
Here is an updated schedule. The estimated dates are for internal
use only.
Release Goals Release Date
------- ------- ------------
V2.8A Mandatory update superceded eco's 22-Jan-1997
SLSEO1028 and SLSE02028 and included:
- SLS/MDMS support for Decnet-Plus (OSI)
- RDF V4.1A which supports Decnet-Plus and
OpenVMS V7.0. V7.1 support is contingent
on field test results.
- MDMS-Only support for OpenVMS V7.0
and 7.1.
- SLS will be installable on neither
V7.0 nor V7.1
V2.9 All V2.8A features plus
- SLS support of OVMS 7.1 (7.0 will not be supported).
- SLS support of DECnet-Plus (OSI)
- Additional bug fixes for SLS and
MDMS.
V2.9 Schedule:
FT1 Start Planned: 02-Feb-97 Actual: 28-Feb-97
FT2 Start 16-Apr-97 02-May-97
FT3 Start 06-Jun-97
FCS Q1FY98
|