T.R | Title | User | Personal Name | Date | Lines |
---|
499.1 | | VMSSG::FRIEDRICHS | Ask me about Young Eagles | Mon Apr 21 1997 12:15 | 13 |
| /DENSITY used to be ignored for Files-11 (non-/Foreign) MOUNTS. This
is enforced in the new MOUNT (COMPAT, CLUSIO, V7.1 kits).
The conflicting qualifiers are /NOHDR3 and /FOR. NOHDR3 doesn't
make much sense to a foreign tape.
The commands (and procedures) should be modified to use the correct
syntax. The V7.1 doc set provides full documentation about the new
MOUNT.
Cheers,
jeff
|
499.2 | why did mount forfeit compatibility? | CUJO::SAMPSON | | Mon Apr 21 1997 23:57 | 15 |
| These V7.1 (and V6.2 compatibilty kit ECO) MOUNT changes sure
have caused a lot of trouble for customers. In the past, OpenVMS went
to great lengths to preserve compatible behavior with previous versions.
Couldn't these more stringent checks have produced warning or informational
messages, without having to be fatal to the MOUNT operation? Something
like:
%MOUNT-W-CONFQUAL, /HDR3 ignored; conflicts with /FOREIGN
or:
%MOUNT-W-BUFTOOBIG, !AZ buffer size !UW should be !UW or less
FWIW,
Bob Sampson
|
499.3 | New MOUNT -- Fixes A Nest Of Support Problems... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Apr 22 1997 10:56 | 8 |
| : <<< Note 499.2 by CUJO::SAMPSON >>>
: -< why did mount forfeit compatibility? >-
MOUNT was redesigned and rewritten in V7.1 (and then back-ported to V6.2)
to resolve a large number of MOUNT-related problems. As Andy G. put it,
some "collateral damage" is expected. The MOUNT changes were tested, but
cases where customers use the code in unforseen ways will slip through.
|