INFO-VAX Wed, 07 Mar 2007 Volume 2007 : Issue 131
Contents:
Re: Alpha firmware questions
Re: AlphaServer 8400 MCES register documentation
Re: Can Samba be used to access Windows files on VMS
Re: DECforms
Re: History of VMS and related operating systems
OT: Ownership of Ethernet
Re: OT: Ownership of Ethernet
Re: OT: Ownership of Ethernet
Re: OT: Proposed additions to the PDP11 instruction set
SYSMAN IO SET EXCLUDE question
Time zone/DST change question.
Re: Time zone/DST change question.
Re: Time zone/DST change question.
Re: Time zone/DST change question.
Re: VMS and storage subsystems documentation ?
Re: VMS and storage subsystems documentation ?
Re: VMS Client to Windows Storage Server x64 R2
----------------------------------------------------------------------
Date: Tue, 06 Mar 2007 12:29:25 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: Re: Alpha firmware questions
Message-ID: <8a247$45eda50b$cef8887a$1696@TEKSAVVY.COM>
> Robert Deininger wrote:
>> The FW for most recent Alpha systems is built on VMS.
Stephen Hoffman wrote:
> http://ftp.digital.com/pub/Digital/info/semiconductor/literature/dtools.pdf
Many thanks. Is there a reason why firmware for the 21164 and 21264 systems
was buildable only on <caugh>Windows and Tru64 only ? What changed to
allow more recent ones to be buildable on VMS ?
Interesting the trick of using Huffman compression for the firmware (to fit
more in a ROM) and having the header be a Huffman decompression program to
expand the firmware code into memory. Is this pretty standard on all Alphas
? or was this a concept that was developped but never actually put into
production ?
------------------------------
Date: Tue, 6 Mar 2007 19:01:39 -0500
From: "David Turner, Island Computers US Corp" <dturner@no-spam.islandco.com>
Subject: Re: AlphaServer 8400 MCES register documentation
Message-ID: <CgnHh.3067$m7.2833@bignews5.bellsouth.net>
YOU'RE WELCOME
David T
"Jim Mehlhop" <mjim1025@qwest.net> wrote in message
news:45edca55$0$503$815e3792@news.qwest.net...
> Island Computers, D B Turner wrote:
>> I sent you the service manuals via email in acrobat format
>> Did you get them?
>>
>> DT
>>
>
> Just saw them Thanks much
>
> Jim
>
------------------------------
Date: Wed, 07 Mar 2007 02:34:22 GMT
From: "Michael D. Ober" <obermd.@.alum.mit.edu.nospam>
Subject: Re: Can Samba be used to access Windows files on VMS
Message-ID: <OwpHh.9862$Jl.8986@newsread3.news.pas.earthlink.net>
I'm close to having the VMS NFS Client working with the Windows Services for
Unix subsystem.
Mike Ober.
"dky" <dhruvakm@gmail.com> wrote in message
news:1173097067.308647.107870@h3g2000cwc.googlegroups.com...
> On Mar 1, 6:10 pm, sol gongola <s...@adldata.com> wrote:
>> Gremlin wrote:
>> > Hi All
>>
>> > So, probably a silly question, obviouslySambaon VMS makes the VMS files
>> > available to Windows/*nix, but can it also be used to "interface" with
>> > Windows files on a Windows server, so that they can be used within VMS?
>>
>> > Cheers
>>
>> You can't access files in a seamless fashion as you would going from
>> windows to windows or windows to vms. There is an "smbclient"
>> command that lets you connect to a windows box and lets you send
>> and receive files using commands in an ftp like manner.
>
> The SMBCLIENT tool on VMS is far from complete. Personally, I do not
> suggest you use it for any serious work. On GNU/Linux, you have
> "mount" that supports CIFS. That is the cleanest way of doing it. On
> VMS, there is not equivalent of it and I do not see that happening in
> the near future either.
>
> -dky
>
>
------------------------------
Date: 6 Mar 2007 11:40:45 -0800
From: yyyc186@hughes.net
Subject: Re: DECforms
Message-ID: <1173210042.778354.306210@j27g2000cwj.googlegroups.com>
On Mar 5, 3:49 pm, Michael Kraemer <M.Krae...@gsi.de> wrote:
> yyyc...@hughes.net schrieb:
>
> Hard to believe.
> Germany was one of the countries with the highest
> OS/2 exposure so it would have appeared here to.Warp4 came in 1996, 4.5 was more
> a server release which later included SMP and such.
> A real "Warp5" never existed.
A real Warp 5 did exist, you just didn't have it for whatever reason.
I ran it for over 2 years, but I was getting Devcon CD sets from IBM.
>
> > Lattice was the original C compiler sold under private label by MS
> > with a non-compete agreement, but we see just how well MS honored that
> > non-compete agreement.
>
> So we are talking a different product here.
> The Lattice I know of has nothing to do with M$ whatsoever.
> As said they were bought by SAS Institute (who have nothing
> to do with M$ either) who continued the
> Amiga product until C= went under.
The Lattice you know of is what was left of the Lattice MS rectally
violated. Prior to MS releasing 4.0 of their C compiler under DOS,
they stuck an MS label on the Lattice C compiler and set it out the
door as the MS compiler. All the while having non-competes to not
develop their own C compiler, then doing just that. Gotta love MS,
John Ghatti had more ethics.
------------------------------
Date: Tue, 6 Mar 2007 19:45:43 -0000
From: "John Wallace" <johnwallace4@yahoo.spam.co.uk>
Subject: Re: History of VMS and related operating systems
Message-ID: <45edc4ea$0$8710$ed2619ec@ptn-nntp-reader02.plus.net>
"UnderMine" <pmulvany@gmail.com> wrote in message
news:1173191118.727900.88370@s48g2000cws.googlegroups.com...
<snip>
> What exactly is the genealagy of VAXELN?
> My understanding was that it originally branched from VMS and then
> developed independantly.
That's (at best) an odd way of describing things, more realistically it's
just plain wrong, sorry.
> VMS -> VAXELN (influence/code?)
VMS and VAXELN both ran on VAX. Cutler worked on (architected?) both. Beyond
that, VAXELN has little in common with VMS in terms of architecture or
heritage - VAXELN was not aimed at the VMS market and consequently it has
different goals and different architecture: intentionally it does not do
(for example) demand paging, it does not do ASTs, it does not do VMS-style
logical names, it does not do DCL, it does not do the vast majority of the
techy things which most VMS-aware folks would consider made VMS what it was.
It does understand Files11 as does VMS, it does (to an extent) understand
VMS-style UIC-based protection, it does do DECnet (and later in life it
understood TCP/IP)... VAXELN system images are built using a VAXELN-specific
build process which allows irrelevant stuff to be left out. VAXELN also does
a whole variety of RT-specific and also comms-related stuff which VMS
doesn't do, such as interapplication messaging which looks the same whether
the two apps are on the same box or different boxes - this may not be a
radical concept today but it was innovative back then.
Much (most?) of VAXELN was written in VAXELN Pascal, so although sharing of
some concepts and designs between VMS and VAXELN might have been easy
enough, sharing of actual code between VMS and VAXELN would have been
limited.
On a good day a trivial VMS application (even some non trivial ones) in
various VAXELN-supported languages might work on VAXELN, subject to
recompilation and relinking, but that wasn't really (afaik) a major design
goal (although it was sometimes very convenient). Along these lines, if I
remember rightly, some fundamental VMS system services (e.g. some date/time
stuff) were implemented on VAXELN for the user's convenience; there may have
been common code (between VMS and VAXELN) for stuff like that where it made
sense, but there weren't many examples of that kind of thing.
If you haven't already read the online "Introduction to VAXELN" referenced
earlier in this thread, it really would be worth doing so. The formatting
makes it hard going though, so if you can get hold of a hardcopy or suitable
substitute...
> VMS -> Project Mica (1986-1988) (influence/code?)
> Mica -> NT (influence/code?) -
http://www.businessreviewonline.com/blog/archives/2005/10/ballmer_microso.ht
ml
>
There are folks reading here who know lots more about Mica than I do. There
doesn't yet seem to be much freely available and definitive info about Mica.
You probably had to be there; I wasn't (and nor was Ballmer).
> Does anyone have version release dates for VAXELN?
>
Not me, sorry.
Good luck anyway.
------------------------------
Date: Tue, 06 Mar 2007 15:00:29 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: OT: Ownership of Ethernet
Message-ID: <3f1bb$45edc873$cef8887a$11937@TEKSAVVY.COM>
It is my understanding that Ethernet was developped jointly by Digital,
Intel and Xerox.
Recently, I got a new ADSL modem and in it, it had a mention that Ethernet
was a trademark of Xerox corporation.
If it were truly a "trademarked" product, shouldn't the caption mention
Intel and HP as well as Xerox ?
(This was a Thompson Speedtouch modem).
It was my understanding that Ethernet set out, right from the start, to be
an open standard without any royalties. Was that the case ?
------------------------------
Date: Tue, 06 Mar 2007 21:16:38 GMT
From: VAXman- @SendSpamHere.ORG
Subject: Re: OT: Ownership of Ethernet
Message-ID: <00A64393.480C0DB4@SendSpamHere.ORG>
In article <3f1bb$45edc873$cef8887a$11937@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@vaxination.ca> writes:
>
>
>It is my understanding that Ethernet was developped jointly by Digital,
>Intel and Xerox.
>
>Recently, I got a new ADSL modem and in it, it had a mention that Ethernet
>was a trademark of Xerox corporation.
>
>If it were truly a "trademarked" product, shouldn't the caption mention
>Intel and HP as well as Xerox ?
>
>(This was a Thompson Speedtouch modem).
>
>It was my understanding that Ethernet set out, right from the start, to be
>an open standard without any royalties. Was that the case ?
OK, for the record, I am not a lawyer (and I'm damn happy I'm not) but it
is my unserstanding that a trademark governs the name. XEROX may have the
name "Ethernet" trademarked but I do not believe it has any bearing on the
technology. That would be governed by patent. If there was any patent, I
am pretty sure that any patent privilege has long since expired.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM
"Well my son, life is like a beanstalk, isn't it?"
------------------------------
Date: Tue, 06 Mar 2007 16:36:58 -0800
From: "Tom Linden" <tom@kednos-remove.com>
Subject: Re: OT: Ownership of Ethernet
Message-ID: <op.tosmnwg8tte90l@hyrrokkin>
On Tue, 06 Mar 2007 13:16:38 -0800, VAXman- <@SendSpamHere.ORG> wrote:
> In article <3f1bb$45edc873$cef8887a$11937@TEKSAVVY.COM>, JF Mezei
> <jfmezei.spamnot@vaxination.ca> writes:
>>
>>
>> It is my understanding that Ethernet was developped jointly by Digital,
>> Intel and Xerox.
>>
>> Recently, I got a new ADSL modem and in it, it had a mention that
>> Ethernet
>> was a trademark of Xerox corporation.
>>
>> If it were truly a "trademarked" product, shouldn't the caption mention
>> Intel and HP as well as Xerox ?
>>
>> (This was a Thompson Speedtouch modem).
>>
>> It was my understanding that Ethernet set out, right from the start, to
>> be
>> an open standard without any royalties. Was that the case ?
>
> OK, for the record, I am not a lawyer (and I'm damn happy I'm not) but it
> is my unserstanding that a trademark governs the name. XEROX may have
> the
> name "Ethernet" trademarked but I do not believe it has any bearing on
> the
> technology. That would be governed by patent. If there was any patent,
> I
> am pretty sure that any patent privilege has long since expired.
>
AIR it was developed by Xerox.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
------------------------------
Date: Tue, 6 Mar 2007 22:00:14 +0100
From: Stefaan A Eeckels <hoendech@ecc.lu>
Subject: Re: OT: Proposed additions to the PDP11 instruction set
Message-ID: <20070306220014.e5438757.hoendech@ecc.lu>
On Tue, 6 Mar 2007 18:44:32 +0000 (UTC)
"Dr Ivan D. Reid" <Ivan.Reid@brunel.ac.uk> wrote:
> On Tue, 06 Mar 2007 11:54:32 -0500, Richard B. gilbert
> <rgilbert88@comcast.net> wrote in <45ED9CC8.3030203@comcast.net>:
> > JF Mezei wrote:
> >> Saw this as a "quote of the day" on a web site...
>
> >> Proposed Additions to the PDP-11 Instruction Set:
> >>
> >> BBW Branch Both Ways
> >> BEW Branch Either Way
> >> BBBF Branch on Bit Bucket Full
> >> BH Branch and Hang
> >> BMR Branch Multiple Registers
> >> BOB Branch On Bug
> >> BPO Branch on Power Off
> >> BST Backspace and Stretch Tape
> >> CDS Condense and Destroy System
> >> CLBR Clobber Register
> >> CLBRI Clobber Register Immediately
> >> CM Circulate Memory
> >> CMFRM Come From -- essential for truly structured programming
> >> CPPR Crumple Printer Paper and Rip
> >> CRN Convert to Roman Numerals
>
>
> > EPI Execute Programmer Immediate
> > BADC Branch and Dump Core
> > LACC Load and Clear Core
> > RWP Rewind Printer
>
> HCF Halt and Catch Fire
SCP Stumble and Crush Programmer
FBE Fry Breaker and Explode
BHC Burn Hole in CRT
EPT Eat Paper Tape
LPC Laminate Punch Card
BRL Branch to Random Location
CPZNZ Convert Positive Zero to Negative Zero
(To be honest, these were invented for that paragon of hardware design,
the Control Data Cyber 17, aka "the 6502 without a stack", with an
assembler manual that explained in gory detail the bit layout of the
instructions but forgot to show you how to write them).
--
Stefaan A Eeckels
--
The one thing IT really needs to outsource is the freakin' clueless
managers that don't understand that there are more possibilities than
chaos on the one hand and the reduction of alternatives to zero on the
other. -- Richard Hamilton in comp.sys.sun.hardware
------------------------------
Date: Tue, 06 Mar 2007 22:40:21 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: SYSMAN IO SET EXCLUDE question
Message-ID: <aa768$45ee343c$cef8887a$11169@TEKSAVVY.COM>
I just applied the VMS83A UPDATE 2.0 to one node. Is it possible that the SYSMAN
IO EXCLUDE list is no longer working properly ?
(node CHAIN has $11 allocation class)
(node BIKE has $10 allocation class)
-------------------------------------------------------------------------------
Node CHAIN is 8.3 with: DEC AXPVMS VMS83A_UPDATE V2.0 applied.
$ mc sysman io show exclude
%SYSMAN-I-OUTPUT, command execution on node CHAIN
%SYSMAN-I-IOEXCLUDE, the current permanent exclusion list is:
DQA1,DQB1,DVA0
$ show dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$7$DIA1: (VELO) Mounted 0 MICHELIN 1353744 1 4
$10$DQA0: (BIKE) Mounted 0 FREEWHEEL 27822912 426 4
$11$DQA0: (CHAIN) Mounted 0 SHIMANO 28390576 1 4
$11$DQA1: (CHAIN) Offline 1
$11$DQB0: (CHAIN) Mounted 0 MAVIC 44533512 1 4
$11$DQB1: (CHAIN) Offline 1
Note that DQA1 and DQB1 show up in the show dev, but DVA0 has succesfully been
excluded.
-------------------------------------------------------------------------------
NODE BIKE is 8.3 and has not yet rebooted with the patch.
$ mc sysman io show exclude
%SYSMAN-I-OUTPUT, command execution on node BIKE
%SYSMAN-I-IOEXCLUDE, the current permanent exclusion list is: DQA1,DQB0,DQB1,DVA0
$ show dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$7$DIA1: (WHEEL) Mounted 0 MICHELIN 1353756 1 4
$10$DQA0: (BIKE) Mounted 0 FREEWHEEL 27822912 563 4
$11$DQA0: (CHAIN) Mounted 0 SHIMANO 28390576 1 4
$11$DQB0: (CHAIN) Mounted 0 MAVIC 44533476 21 4
(Both BIKE and CHAIN are DS10L machines, CHAIN has 2 IDE drives, BIKE has 1).
Must the SYSMAN IO SET EXCLUDE have the allocation class in it to work properly?
------------------------------
Date: Tue, 06 Mar 2007 22:06:43 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: Time zone/DST change question.
Message-ID: <80b26$45ee2c59$cef8887a$19152@TEKSAVVY.COM>
The release notes for VMS83A_UPDATE-V0200 which include the TZ update mention
that from now on, those west of GMT will in in a positive time differential
instead of negative as in the past.
However, after intalling the kit (but not yet rebooting), I executed the
UTC$TIME_ZONE_SETUP procedure as the release notes said, but when selecting
eastern canada time zone it still told me that my time zone (eastern canada) is
-5 in winter and -4 in summer.
UTC$TIME_ZONE_SETUP.COM in my sys$manager is:
UTC$TIME_SETUP.COM;1 File ID: (3818,2,0)
Size: 184/192 Owner: [SYSTEM]
Created: 26-JAN-2005 13:39:47.13
Revised: 26-JAN-2005 14:48:07.00 (2)
In the file, the last modification is X35 by the renowned Charlie Hammond,
2005-JAN-26.
What have I done wrong ?
------------------------------
Date: Tue, 6 Mar 2007 22:56:58 -0500
From: "Neil Rieck" <n.rieck@sympatico.ca>
Subject: Re: Time zone/DST change question.
Message-ID: <45ee2b7d$0$16407$88260bb3@free.teranews.com>
"JF Mezei" <jfmezei.spamnot@vaxination.ca> wrote in message
news:80b26$45ee2c59$cef8887a$19152@TEKSAVVY.COM...
> The release notes for VMS83A_UPDATE-V0200 which include the TZ update
> mention that from now on, those west of GMT will in in a positive time
> differential instead of negative as in the past.
>
> However, after intalling the kit (but not yet rebooting), I executed the
> UTC$TIME_ZONE_SETUP procedure as the release notes said, but when
> selecting eastern canada time zone it still told me that my time zone
> (eastern canada) is -5 in winter and -4 in summer.
>
A very weird thing happened to me last week when I was testing some
application software on an Oracle-8 system. For reasons I won't go into
here, we are in possession of some third-party UNIX application software
with baked-in DST rules "and" there is not enough time to install an
upgrade.
So I installed the Solaris-8 patches and was then developing a procedure so
that 2:00 AM on Mar-11 we were going to manually change the timezone from
Canada/Eastern to just plain old GMT-4. (cuz we won't get the new s/w loaded
until mid-summer and I didn't want the baked-in s/w to flip over to EDT on
April-1).
Now here is the weird part, while testing the procedure on a captive system
I learned than GMT-4 actually produced GMT+4. Peering inside file
"/usr/share/lib/zoneinfo/GMT-4" actually revealed "GMT+4" and checking file
"GMT+4" revealed "GMT-4". This is the only UNIX box doing this so I just
assumed that someone screwed up at Sun.
Now it's kind of weird that people have been confusing this stuff all along.
While it is true that EST (local) is the same as GMT minus 5, program data
we send to our ExpressVu satellites is always expressed in GMT which is 5
hours ahead of EST (this is just a matter of perspective I guess).
I guess I had better check the release notes you mentioned.
p.s. this link http://en.wikipedia.org/wiki/GMT-4 assured me that I wanted
my computer's local clock set to GMT minus 4. In the mean time we're going
to begin working on a plan to set all of our computer system clocks to GMT;
we will also being storing GMT in our databases and will only convert back
to local time when expressly requested by a human.
Neil Rieck
Kitchener/Waterloo/Cambridge,
Ontario, Canada.
http://www3.sympatico.ca/n.rieck/
--
Posted via a free Usenet account from http://www.teranews.com
------------------------------
Date: Wed, 07 Mar 2007 03:55:21 GMT
From: rdeininger@mindspringdot.com (Robert Deininger)
Subject: Re: Time zone/DST change question.
Message-ID: <rdeininger-0603072255360001@dialup-4.233.149.173.dial1.manchester1.level3.net>
In article <80b26$45ee2c59$cef8887a$19152@TEKSAVVY.COM>, JF Mezei
<jfmezei.spamnot@vaxination.ca> wrote:
>The release notes for VMS83A_UPDATE-V0200 which include the TZ update mention
>that from now on, those west of GMT will in in a positive time differential
>instead of negative as in the past.
Could you please quote the exact text of the relevant part of the release notes?
Does the part you think is relevant include the sentence "The following
instructions apply to users who have set the time zone to GMT-* or
GMTPLUS* :" ?
>However, after intalling the kit (but not yet rebooting), I executed the
>UTC$TIME_ZONE_SETUP procedure as the release notes said, but when selecting
>eastern canada time zone it still told me that my time zone (eastern
canada) is
>-5 in winter and -4 in summer.
So, you have not set the time zone to GMT-* or GMTPLUS*.
>UTC$TIME_ZONE_SETUP.COM in my sys$manager is:
>UTC$TIME_SETUP.COM;1 File ID: (3818,2,0)
>Size: 184/192 Owner: [SYSTEM]
>Created: 26-JAN-2005 13:39:47.13
>Revised: 26-JAN-2005 14:48:07.00 (2)
>
>In the file, the last modification is X35 by the renowned Charlie Hammond,
>2005-JAN-26.
>
>What have I done wrong ?
I believe you have mis-read the release notes.
------------------------------
Date: Tue, 06 Mar 2007 23:33:01 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: Re: Time zone/DST change question.
Message-ID: <284ee$45ee4094$cef8887a$25922@TEKSAVVY.COM>
Robert Deininger wrote:
> Does the part you think is relevant include the sentence "The following
> instructions apply to users who have set the time zone to GMT-* or
> GMTPLUS* :" ?
OK, fair enough. But the text is quite explicit that for now on,
BUT:
The definition of the timezone names has been changed in
the time-zone public database
(ftp://elsie.nci.nih.gov/pub/). The effect of this change
is that, after installation of the VMS83A_TZ-V0100 kit,
"GMT-" (minus) will now mean "ahead (east) of" Greenwich
Mean Time (GMT) and "GMTPLUS" will now mean "behind (west)
of" GMT. For example, GMT-1 will mean one hour ahead
(east) of GMT and the Time Differential Factor
(SYS$TIMEZONE_DIFFERENTIAL) will be set to "3600".
GMTPLUS1 will mean one hour behind (west) of GMT and the
SYS$TIMEZONE_DIFFERENTIAL will be set to "-3600". This is
the opposite meaning of what you are used to. In order to
correct for this, after installation of this kit, users
must run the SYS$MANAGER:UTC$TIME_SETUP.COM command file
and set the timezone to the opposite of what was originally
set. For example, if you had previously set the timezone
to GMTPLUS*, you must now set the timezone to GMT-* to
account for the timezone definition changes.
So it does mention that SYS$TIMEZONE_DIFFERENTIAL now has negative values for
east, positive values for west.
So it is strange and not too obvious that a time zone specification by *NAME*
(such as eastern canada) would have negative for west, but specifying an actual
GMT *OFFSET* would result in opposite signate for the same logical.
And this is also begs the question since UTC$TIME_SETUP.COM was not modified by
the patch. Is that correct ?
------------------------------
Date: Tue, 06 Mar 2007 20:19:06 -0600
From: David J Dachtera <djesys.no@spam.comcast.net>
Subject: Re: VMS and storage subsystems documentation ?
Message-ID: <45EE211A.CB71C35@spam.comcast.net>
JF Mezei wrote:
>
> Robert Deininger wrote:
> > VMS disks that are connected via SCSI, SAS, and FibreChannel all use the
> > SCSI disk class driver, SYS$DKDRIVER.EXE. The lower-level,
> > adapter-specific port drivers all present a common interface to the class
> > driver.
>
> Does this mean that a utility such as RZDISK could be used against a drive
> on VMS
Why would you want to? What "problem" are you trying to solve?
Again, remember: what's "behind" the LUN is now a virtual concept - it may or
may not represent an actual physical disk drive, more than likely not if using
any kind of storage array in which case it will represent a "storageset" in HSx
terms (RAIDset, mirror-set, stripe-set, etc.).
That said, there ARE FC-interconnect disk drives around, and it IS possible - if
however marginally advisable - to connect them to a fibre-channel switched
fabric SAN. I would expect this to be extremely rare given the cost of FCSW
infrastructure elements compared to LVD SCSI, but very definitely possible.
> and whatever SCSI commands sent by RZDISK would be interpreted by
> the storage array and a response synthesised based on how that logical
> drive had been configured ?
I would doubt that very seriously.
Probably the closest example of virtual storage to you would be connecting a
container file to an LD device. It "looks like" a disk, can be INITIALIZEd,
MOUNTed, shadowed, etc. However, you wouldn't try to "low level format" it,
inquire on its serial number, etc. now would you?
Virtual storage presented by an array can be thought of similarly. It "looks
like" a disk, can be INITIALIZEd, MOUNTed, shadowed, etc. However, you wouldn't
try to "low level format" it, inquire on its serial number, twiddle ARRE or AWRE
bits, etc.
--
David J Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/
Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/
------------------------------
Date: Tue, 06 Mar 2007 21:41:12 -0500
From: JF Mezei <jfmezei.spamnot@vaxination.ca>
Subject: Re: VMS and storage subsystems documentation ?
Message-ID: <dfeff$45ee265e$cef8887a$4458@TEKSAVVY.COM>
David J Dachtera wrote:
>> Does this mean that a utility such as RZDISK could be used against a drive
>> on VMS
>
> Why would you want to? What "problem" are you trying to solve?
Just trying to understand to what extent the storage array fakes a scsi drive to
VMS.
> Again, remember: what's "behind" the LUN is now a virtual concept
But to VMS, it looks like, smells like and behaves like a real drive, doesn't it ?
> Probably the closest example of virtual storage to you would be connecting a
> container file to an LD device.
But the LD driver isn't a SCSI class driver and devices.
My old Dilog SCSI-QBUS card on VAX makes a scsi disk appear as an RA drive on
VMS. It makes it smell, feel, act as an RA82 drive, but reports larger size.
And the card provided an MSCP interface to VMS so VMS didn't need any special
drivers to access SCSI drives. However, because it appeared as a RA82 drive, I
could not use any "SCSI" applications such as RZDISK or the CDaudio player.
------------------------------
Date: Wed, 07 Mar 2007 02:34:23 GMT
From: "Michael D. Ober" <obermd.@.alum.mit.edu.nospam>
Subject: Re: VMS Client to Windows Storage Server x64 R2
Message-ID: <PwpHh.9863$Jl.8171@newsread3.news.pas.earthlink.net>
I'm close to having the VMS NFS Client working with the WSS NFS Server.
Since I know this configuration has been asked about before, when I get it,
I'll post the configuration for both ends of the link.
Mike.
"dky" <dhruvakm@gmail.com> wrote in message
news:1173097276.054597.305960@q40g2000cwq.googlegroups.com...
> On Mar 1, 7:49 pm, "Michael D. Ober" <obermd.@.alum.mit.edu.nospam>
> wrote:
>> I need the ability for our VMS server to mount drives from shares on a
>> Windows Storage Server x64 R2. Basically, VMS will be a client to
>> network
>> shares.
>>
>> SYSTEM>tcpip show ver
>>
>> HP TCP/IP Services for OpenVMS Alpha Version V5.6
>> on an AlphaServer 1200 5/533 4MB running OpenVMS V8.3
>>
>> Does anyone know if Pathworks Advanced Server, JYCSamba2.2.8, HPSamba
>> 3.x, or native VMS NFS client can do this and if so, how?
>
> If it is ALPHA, I would bet my production system on Advanced Server on
> VMS (Pathworks). Samba is still an alpha not architecture) product and
> needs time to mature.
> If it an IA64 box, you will have to wait till a new release comes out
> (many bugs fixed with lot of new features)
>
> -dky
>
>
------------------------------
End of INFO-VAX 2007.131
************************