| Title: | Optical Products |
| Moderator: | TAPE::SENEKER |
| Created: | Wed May 04 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 841 |
| Total number of notes: | 3218 |
My customer bought an RW552 planning to use it with OSMS and HSM in an OpenVMS
6.1 VAX environment.
The particular analyst working on this project is about to pull his hair out.
He has installed OSMS version 3.3 and in the installation questions he was
baffled. (1) RW552 not a choice (so he used RW532 Jukebox)
(2) Controller is CMD's Hawk (eventually will be upgraded to CMD's
Trident); like the HSJ
He also mentioned to me that the installation guide reflects the naming
convention for the saveset as LSTARV033 yet on the CONDIST it was OSMSVMS33.
The installation finishes but the startup portion LASERSTAR$STARTUP.COM
fails SYSTEM-F-ILLIOFUNC, Illegal IO function code. From a SET VERIFY
he can tell that this error occurs when the JKCONFIG is run.
He found the LSTARV1033 ECO in DSN. Yet there doesn't seem to be any
more information about the RW552 in it.
Now, is the RW552 currently supported and if so how? If not, any plans for
it to be?
What about the CMD controller?
What about the error message that I described above?
The customer is anxious to be using his RW552 for archiving so we appreciate
any insights into this issues. Also this is in a cluster situation and the
customer has heard there is a possibility for cluster crashes with OSMS
although I could not find any reference to this in the OPTICAL notes conference.
Can someone comment on this?
Thanks.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 805.1 | that combination will not work | TAPE::SENEKER | Head banging causes brain mush | Tue Mar 11 1997 13:21 | 26 |
The RW552 is only support under OpenVMS via OSMS V3.4 as of Mar. 97.
Your environment has the following unsupported conditions for use of
RW552:
o OpenVMS/VAX V6.1 --- must be OpenVMS/VAX V6.2
o Controller is CMD's Hawk --- not supported --- HSD30/HSJ40 is
supported.
To answer some of your questions:
Since the configuration you have is unsupported, the error code does
not matter. It most likely means that JKCONFIG issued a I/O request
that lower level drivers could not do so they called it illegal.
There are no plans to qualify the CMD controller. OSMS/LaserStar has
been stable in regards to cluster crashes for some time.
Optical engineering would like to correct anything that we have direct
control of such as documentation, sales updates, etc. We thought we
had a clear picture of what it took to use a RW552.
How did this combination of options get sold to the customer? It
doesn't make Digital look very good when a "solution" is provided that
just doesn't work.
Rob
| |||||
| 805.2 | LEFTY::CWILLIAMS | CD or not CD, that's the question | Tue Mar 11 1997 13:31 | 14 | |
There is no support for the CMD Hawk controllers. None now, none in the
future. Ditto for the Trident. "Like the HSJ" won't cut it. The HSJ's
have a JB SCSI pass thru feature that the CMD controllers don't have,
which OSMS knows about and uses. I believe the CMD controllers have a
similar feature, but OSMS has no idea how to use it.
If the OSMS version you have does not have the RW552 as a choice in the
menus, then you need to upgrade OSMS. I thought it was at V3.4 now...
To suggest a supported configuration, we'll need the CPU type at a
minimum.
Chris
| |||||