1 INFO-VAX	Sat, 17 Jun 2006	Volume 2006 : Issue 334       Contents:? Re: Has any version of VMS ever received an A1 security rating? ? Re: Has any version of VMS ever received an A1 security rating? ? Re: Has any version of VMS ever received an A1 security rating? ? Re: Has any version of VMS ever received an A1 security rating? % Re: How can I read a locked VMS file? % Re: How can I read a locked VMS file? % Re: How can I read a locked VMS file? % Re: How can I read a locked VMS file? 0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 RE: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?# Re: Open VMS OS recovery on Itanium < Q: (Long)  DCL symbols not shown by Show Symbol [SLS V2.9H]?P Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS  V2.9H]  V2.9E Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H] . Re: Question about number of Vax System owners. Re: Question about number of Vax System owners$ Re: Sending HTML mail from VMS MAIL?$ Re: Sending HTML mail from VMS MAIL?$ Re: Sending HTML mail from VMS MAIL?$ Re: Sending HTML mail from VMS MAIL?$ Re: Sending HTML mail from VMS MAIL?; whats the largest usable internal hard drive on vaxstation? ? Re: whats the largest usable internal hard drive on vaxstation? ? Re: whats the largest usable internal hard drive on vaxstation? ? Re: whats the largest usable internal hard drive on vaxstation? ? Re: whats the largest usable internal hard drive on vaxstation? ? Re: whats the largest usable internal hard drive on vaxstation?   F ----------------------------------------------------------------------    Date: 16 Jun 2006 14:50:59 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) H Subject: Re: Has any version of VMS ever received an A1 security rating?3 Message-ID: <ALfuzxoB4irA@eisner.encompasserve.org>   e In article <Z4ykg.2$0_.335@news.uswest.net>, "Michael D. Ober" <obermd.@.alum.mit.edu.nospam> writes:  >   M > The only OS I have ever heard of that received an A1 was at Boeing.  It was F > a custom, from the ground up, development for internal Boeing use onH > military projects.  I don't believe any commercial network OS has ever% > received the Orange Book A1 rating.   2 The Honeywell SCOMP was evaluated at the A1 level.! Purists deried the term "rating".    ------------------------------    Date: 16 Jun 2006 15:05:54 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) H Subject: Re: Has any version of VMS ever received an A1 security rating?3 Message-ID: <uoSxoOlAckqf@eisner.encompasserve.org>   ` In article <8Exkg.1970$sq1.279@news.cpqcorp.net>, Hoff Hoffman <hoff-remove-this@hp.com> writes: > Dan Foster wrote: M >> In article <Fgpkg.1307$uz5.17@fe04.lga>, Z <SpamDumpst3r@yahoo.com> wrote: * >>> Please help me settle a (virtual) bet. >>  E >> I seem to recall having heard of at least one customized [at great D >> expense] VAX/VMS version that achieved the Orange Book A1 rating. >>   > K >    The package that the paper is citing -- variously known as SVS, or as  J > the VVAX Virtual VAX -- did not receive an A1 evaluation, and was never  > released as a product.  C My recollection is that the decision not to release it as a product ' was what caused it not to be evaluated.   D The informal political description I have heard is that the ComputerE Security part of NSA was gung-ho to get vendors to support multilevel B security on a single machine.  But it was not for their own use --D they run "system high" just like other government departments.  TheyG set the rules for what was required to run a multilevel secure machine.   ? But (and this was in the days when MicroVAXen proliferated) the ? government agencies that could not run "system high" on a large E machine saw it as more economical to buy a bunch of binary compatible D little machines and run them at their various categories and levels.  @ So the DEC Marketing folks discovered that although the securityC wonks at NSA had great plans and great standards, they were at odds B with the government folks who actually bought computers.  RIP SVS.  E And SVS was not some variant on VMS.  It was modifications to a large C late-model _VAX_ to allow it to run multiple copies of VMS.  So the E piece that was targeted for A1 evaluation was the moral equivalent of F the microcode that enables Galaxy, but more secure.  More secure meantB being implemented in Pascal with no runtime library written in anyC language less strongly typed than Pascal.  This allowed for the use ; of theorum-proving tools required for an A1 implementation.   ? For an example of how unimportant this has become, note that in ? recent years VMS development has not felt sufficient government A pressure to get an evaluation under the new Common Criteria.  The A only hint I have seen from the feds is the second public draft of ? 800-53A (comment period still open) which places a considerably C heavier burden on those running High Impact applications on systems A that have not received a TCSEC or Common Criteria evaluation.  An F example of a High Impact system is one that contains personal data :-)   ------------------------------  + Date: Fri, 16 Jun 2006 20:37:11 +0000 (UTC) 1 From: legalize+jeeves@mail.xmission.com (Richard) H Subject: Re: Has any version of VMS ever received an A1 security rating?, Message-ID: <e6v4pn$otd$1@news.xmission.com>  / [Please do not mail me a copy of your followup]   = Kilgallen@SpamCop.net (Larry Kilgallen) spake the secret code / <uoSxoOlAckqf@eisner.encompasserve.org> thusly:   E >The informal political description I have heard is that the Computer F >Security part of NSA was gung-ho to get vendors to support multilevelC >security on a single machine.  But it was not for their own use -- E >they run "system high" just like other government departments.  They H >set the rules for what was required to run a multilevel secure machine.   What is running "system high"? --  E "The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ: 3           <http://www.xmission.com/~legalize/book/> ( 	    Pilgrimage: Utah's annual demoparty,                <http://pilgrimage.scene.org>   ------------------------------  % Date: Fri, 16 Jun 2006 17:48:01 -0700 # From: "Tom Linden" <tom@kednos.com> H Subject: Re: Has any version of VMS ever received an A1 security rating?) Message-ID: <op.ta9lubtdzgicya@hyrrokkin>   1 On Fri, 16 Jun 2006 12:02:47 -0700, Dale E. Coy   ' <daleecoy@obfuscation.spinn.net> wrote:   @ > I was never sure about the A1 evaluation, but check out SEVMS. > 0 > http://citeseer.ist.psu.edu/428108.html     or3 > http://h71000.www7.hp.com/openvms/products/sevms/  > / > "Z" <SpamDumpst3r@yahoo.com> wrote in message $ > news:Fgpkg.1307$uz5.17@fe04.lga...) >> Please help me settle a (virtual) bet.  >  > @ As I recall. A1 required a formal proof of correctness.  B levelB Mandatory Access Control and C level Discretionary Access Control.G Multics was at highest B level, but proving correctness of the security 8 model to achieve A level I believe was a difficult task.   ------------------------------  # Date: Fri, 16 Jun 2006 17:54:23 GMT % From: Rob Brown <mylastname@gmcl.com> . Subject: Re: How can I read a locked VMS file?E Message-ID: <Pine.LNX.4.61.0606161150580.13808@localhost.localdomain>   ' On Fri, 16 Jun 2006, Dave Froble wrote:    > Rob Brown wrote:E >> I did some experiments with VMS/Alpha V7.1.  It appears that this  - >> approach does not give the desired result.  >> ... >> :-( >>   >>   > > > An interesting experiment, and not the results I would have  > expected.  > B > Are you running some type of caching product that does not do a  > write through to disk?  	 I am not.   C > When a file extent is added, I would expect the cause would be a  F > need to write (more) data to disk than there is currently allocated  > filespace.  F After my last post, I did a DUMP/ALLOCATED of the open log file.  The D data was definitely in the logfile, but it does *not* get copied by  backup.    :-(   ; > The BACKUP >>should<< pick up all allocated disk storage.    If only that were true.   F > The 'proper' place to handle such is in the application writing the  > log file.   
 Evidently.     --    B Rob Brown                        b r o w n a t g m c l d o t c o m6 G. Michaels Consulting Ltd.      (780)438-9343 (voice)4 Edmonton                         (780)437-3367 (FAX)2                                   http://gmcl.com/   ------------------------------  % Date: Fri, 16 Jun 2006 14:59:38 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: Re: How can I read a locked VMS file?, Message-ID: <4492FF99.4415B72E@teksavvy.com>   Dave Froble wrote:; > The BACKUP >>should<< pick up all allocated disk storage.   E Why should it ? In a sequential file, there is no point in going past  the enf of file marker.   G In a relative file, as I recall from a discussion of highwater marking, F the "end of file" would go to the end of the highest block used in theB file.  (so if you have a 100 block file, and have written only oneG record at block 50, then backup would only pickup the first 50 blocks). ? (and if the first write is at block 50, all previous blocks are  automatically zeroed).  F Similarly, in an indexed file, there is also the concept of an "end of< file" because you can have fewer blocks used than allocated.   ------------------------------  % Date: Fri, 16 Jun 2006 16:44:25 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> . Subject: Re: How can I read a locked VMS file?: Message-ID: <lNadnagl2MWrhQ7ZnZ2dnUVZ_tednZ2d@comcast.com>   Rob Brown wrote:& > On Thu, 15 Jun 2006, JF Mezei wrote: >  >> John Santos wrote:  >>J >>> You will probably still end up with the EOF pointing to the beginning H >>> of the file (directory shows 0/xxx for the size), but BACKUP should 7 >>> copy whatever has actually been written to the disk  >> >> >> Can anyone confirm this ? >  > D > I did some experiments with VMS/Alpha V7.1.  It appears that this , > approach does not give the desired result. >  > This is what I did:  > " > $ open/write/share f openlog.txt9 > $ write f "the quick brown fox jumps over the lazy dog"  > G > I repeated the write statement until a $DIRECTORY command on another  I > terminal showed that an extent had been added to the file.  Then I did  1 > the backup command, with the following results:  > : > $ backup/ignore=interlock openlog.txt;0 copy.txt/log/newK > %BACKUP-W-ACCONFLICT, DISK$8:[BROWN.TEMP]OPENLOG.TXT;2 is open for write   > by another user : > %BACKUP-S-CREATED, created DISK$8:[BROWN.TEMP]COPY.TXT;9& > $ dir/size=all/date openlog.txt,copy >  > Directory DISK$8:[BROWN.TEMP]  > ? > OPENLOG.TXT;2              0/12       16-JUN-2006 09:30:50.51 ? > COPY.TXT;9                 0/12       16-JUN-2006 09:30:50.51  > ... ) > $ dump/allocated/block=count=1 copy.txt  > G > Dump of file DISK$8:[BROWN.TEMP]COPY.TXT;9 on 16-JUN-2006 09:32:35.25 ; > File ID (28737,18,0)   End of file block 0 / Allocated 12  > 5 > Virtual block number 1 (00000001), 512 (0200) bytes  > = >  0000A400 03000100 0000A500 0100054F O............. 000000  > ...  > G > As you can see, it does not say "the quick brown fox" anywhere here.  K > Doing a SET FILE/END COPY.TXT does not change anything.  The data is not   > there. >  > :-(  >  >   C I just tried the experiment on Alpha VMS V7.2-1.  You're right, it  @ doesn't work.  Even after writing 11 blocks worth of "The quick B brown..." nothing was committed to disk until the file was closed.  E I hearby retract foolish remarks I've made in the past about VMS/RMS  E writing things to disk.  It appears that VMS, at least, V7.2-1 is no  F better than Unix about actually committing things to disk and that if I I'd lost power before closing the file the contents would have been lost.    ------------------------------  % Date: Fri, 16 Jun 2006 19:51:36 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> . Subject: Re: How can I read a locked VMS file?, Message-ID: <44934407.9521DE5C@teksavvy.com>   "Richard B. Gilbert" wrote: D > I just tried the experiment on Alpha VMS V7.2-1.  You're right, itA > doesn't work.  Even after writing 11 blocks worth of "The quick D > brown..." nothing was committed to disk until the file was closed.  E Actually, this may not be the case. It may have been written to disk, G but since the EOF pointer was not updated, so normal utilities wouldn't & see the data even thoug it is on disk.   ------------------------------  % Date: Fri, 16 Jun 2006 15:20:37 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? , Message-ID: <44930481.3579378F@teksavvy.com>   Dave Froble wrote:J > I assume I'm one of the 'kooks' since I no longer have anything to offer2 > what the VMS management seems to desire, sales.   G Yes, but you redeemed yourself when you "offered" to test some Titanium D high-tech bat on my head :-) I bet you earned lots of brownie points% with VMS management with that one :-)    Robert Deininger wrote: L > But realize that comp.os.vms is NOT a reliable way to communicate your VMSI > needs to VMS product management.  None of them read this newsgroup, and = > none are likely to return here in the current environment.    G If VMS were a private enterprise, then good management would want to be F here and engage the naysayers to better understand their point of viewD and try to fix things that irritate customers and leverage potential ideas for additional sales.   F In the ISP business in canada, there are various dicussion forums, andG it is those couple of ISPs who have a management/technical presence who G get the best image and wherever someone is unhappy with their ISP, they 1 go to those ISPs who are active on those forums.      H One independant ISP that has some presence in a forum was recently takenH over by a bigger outfit that wasn't as "professional". The bigger outfitF forced a proxy web server onto the customers, as well as combine users= onto that ISP's network, overloading it and causing many many F complaints. The few employees who did participate didn't even know theF full story anymore because those decisions had come from "head office"F far away and were no longer in a position to provide adequate answers.3 As a result, many customers are very very unhappy.    E My current ISP used its presence in forums to build its image. And he A struck hard this week by announcing a new offering with unlimited G bandwidth on a single network (Cogent), while keeping the high quqality B dual-network offering with a 100gig cap.  Questions were asked, heF replied to them. And guess what ? He's raking in the customers becauseC by listening to rants over the years, they get a good feel for what  people like and dislike.  H And if one person complains about his ISP, that is job #1 to respond and@ make damned sure that even if that customer cannot be satisfied,D everyone else will see that the ISP is doing its darndest to fix any problems customers have.  G And because his ISP has a great image, whenever someone is unhappy with 0 their current ISP, guess where they look first ?  B Last year, when a former ISP of mine finally went belly up withoutC official warning, leaving thousands stranded, guess who got a large G proportion of the customers despite that ISP having struck some deal to $ transfger customers to another ISP ?      F If VMS "management"'s role is simply to defend HP decisions, then theyC are simple civil servants who administer some budget. If they cared G about fixing VMS's image, they'd be here not to defend their decisions, E but rather to adapt their decisions to take into account the comments F being made here. comp.os.vms would become a shrine where people prised! VMS management for their efforts.   F If VMS management is unhappy about what is being said here, it is to a large extent their own fault.   * Sorry to be blunt, but it has to be said.   E Imagine the good PR it would make if it were to become known that VMS ? management actively participates in newsgroups and discuss with H customers, former customers and potential customers to ensure VMS is the9 best offering possible. That kind of PR, you cannot buy.    A Now, if none of the VMS management are actually empowered to make F decisions on VMS, then they should come out here and says so and pointD fingers at those who are making the decisions. There are policically correct ways of doing so.    ------------------------------  % Date: Fri, 16 Jun 2006 16:53:32 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? : Message-ID: <neOdndp-npPThw7ZnZ2dnUVZ_rednZ2d@comcast.com>   Dave Froble wrote:  ! > david20@alpha2.mdx.ac.uk wrote:  >  >> In article T >> <rdeininger-1606060719320001@dialup-4.233.173.202.dial1.manchester1.level3.net>, : >> rdeininger@mindspringdot.com (Robert Deininger) writes: >>< >>> In article <dt339292hsnp1dvvfhod68mkq9cfkt5jue@4ax.com>, >>> support@mandala.ca wrote:  >>> 1 >>>> On Thu, 15 Jun 2006 14:24:59 GMT, you wrote:  >>>> >>>>> Mandala support wrote: >>>>> 3 >>>>>> Just Ask The Vendor: Can OpenVMS Scale Down?  >>> I >>> Nothing posted here has any influence, except for rare accidents when K >>> someone notices a legitimate problem and passes it to the right person.  >>> C >>> I won't bother to name the dozen or so posters who have earned   >>> comp.os.vms L >>> its reputation as a nuthouse.  They know who they are, and I assume they; >>> do it intentionally in an attempt to destroy the forum.  >>> H >> Please do name them. I for one am fed up of hearing such disparaging 
 >> remarksC >> about comp.os.vms posters which cannot be verified or gainsayed   >> because the4 >> poster won't identify who they are talking about. >>J >> I for one don't equate disagreeing with where Compaq and HP have taken + >> VMS with wanting to destroy this forum.   >  > 4 > Well, that probably just put you on the list.  :-) > K > I assume I'm one of the 'kooks' since I no longer have anything to offer  H > what the VMS management seems to desire, sales.  I'm in that position H > due to (in part) the (in my judgement) bad decisions by the owners of F > VMS.  I have only one VMS customer left, an ISV who keeps asking me + > silly questions such as "how about java?"  >   ? A few years ago, I installed a Java Development Kit on VMS.  I  C downloaded a bunch of stuff from somewhere on SUN.COM and followed  H directions.  The developers who requested it were apparently happy with I it.  I think it was JDK 1.2 but I won't swear to it.  Don't know if it's  * still available.  Have you looked for one?   ------------------------------  % Date: Fri, 16 Jun 2006 18:14:20 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> 9 Subject: RE: Just Ask The Vendor: Can OpenVMS Scale Down? T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B8684015B472E@tayexc19.americas.cpqcorp.net>   > -----Original Message-----= > From: Richard B. Gilbert [mailto:rgilbert88@comcast.net]=20  > Sent: June 16, 2006 4:54 PM  > To: Info-VAX@Mvb.Saic.Com ; > Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down?  >=20 > Dave Froble wrote: >=20# > > david20@alpha2.mdx.ac.uk wrote:  > >=20 > >> In article=20 > >>=20 @ > <rdeininger-1606060719320001@dialup-4.233.173.202.dial1.manche > ster1.level3.net>,=20 < > >> rdeininger@mindspringdot.com (Robert Deininger) writes: > >>> > >>> In article <dt339292hsnp1dvvfhod68mkq9cfkt5jue@4ax.com>, > >>> support@mandala.ca wrote:  > >>> 3 > >>>> On Thu, 15 Jun 2006 14:24:59 GMT, you wrote:  > >>>> > >>>>> Mandala support wrote: > >>>>> 5 > >>>>>> Just Ask The Vendor: Can OpenVMS Scale Down?  > >>> ? > >>> Nothing posted here has any influence, except for rare=20  > accidents whenB > >>> someone notices a legitimate problem and passes it to the=20 > right person.  > >>> G > >>> I won't bother to name the dozen or so posters who have earned=20  > >>> comp.os.vms ? > >>> its reputation as a nuthouse.  They know who they are,=20  > and I assume they = > >>> do it intentionally in an attempt to destroy the forum.  > >>> @ > >> Please do name them. I for one am fed up of hearing such=20 > disparaging=20 > >> remarksG > >> about comp.os.vms posters which cannot be verified or gainsayed=20  > >> because the6 > >> poster won't identify who they are talking about. > >>@ > >> I for one don't equate disagreeing with where Compaq and=20 > HP have taken=20/ > >> VMS with wanting to destroy this forum.=20  > >=20 > >=206 > > Well, that probably just put you on the list.  :-) > >=20= > > I assume I'm one of the 'kooks' since I no longer have=20  > anything to offer=20> > > what the VMS management seems to desire, sales.  I'm in=20 > that position=20B > > due to (in part) the (in my judgement) bad decisions by the=20 > owners of=20J > > VMS.  I have only one VMS customer left, an ISV who keeps asking me=20- > > silly questions such as "how about java?"  > >=20 >=20C > A few years ago, I installed a Java Development Kit on VMS.  I=20 G > downloaded a bunch of stuff from somewhere on SUN.COM and followed=20 A > directions.  The developers who requested it were apparently=20  > happy with=20 @ > it.  I think it was JDK 1.2 but I won't swear to it.  Don't=20 > know if it's=20 , > still available.  Have you looked for one? >=20    5 Latest V5 Java kit for OpenVMS Alpha can be found at: % http://h18012.www1.hp.com/java/alpha/ ? http://h18012.www1.hp.com/java/documentation/index.html (Doc's) 3 http://h18012.www1.hp.com/java/faq/index.html (FAQ)    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  % Date: Sat, 17 Jun 2006 01:34:44 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 9 Message-ID: <ELKdnVR1zLP8Dg7ZnZ2dnUVZ_qidnZ2d@libcom.com>    Richard B. Gilbert wrote:  > Dave Froble wrote: > " >> david20@alpha2.mdx.ac.uk wrote: >> >>> In article  U >>> <rdeininger-1606060719320001@dialup-4.233.173.202.dial1.manchester1.level3.net>,  ; >>> rdeininger@mindspringdot.com (Robert Deininger) writes:  >>> = >>>> In article <dt339292hsnp1dvvfhod68mkq9cfkt5jue@4ax.com>,  >>>> support@mandala.ca wrote: >>>>2 >>>>> On Thu, 15 Jun 2006 14:24:59 GMT, you wrote: >>>>>  >>>>>> Mandala support wrote:  >>>>>>4 >>>>>>> Just Ask The Vendor: Can OpenVMS Scale Down? >>>>J >>>> Nothing posted here has any influence, except for rare accidents whenL >>>> someone notices a legitimate problem and passes it to the right person. >>>>D >>>> I won't bother to name the dozen or so posters who have earned  >>>> comp.os.vmsI >>>> its reputation as a nuthouse.  They know who they are, and I assume  	 >>>> they < >>>> do it intentionally in an attempt to destroy the forum. >>>>I >>> Please do name them. I for one am fed up of hearing such disparaging   >>> remarks D >>> about comp.os.vms posters which cannot be verified or gainsayed  >>> because the 5 >>> poster won't identify who they are talking about.  >>> E >>> I for one don't equate disagreeing with where Compaq and HP have  2 >>> taken VMS with wanting to destroy this forum.  >> >>5 >> Well, that probably just put you on the list.  :-)  >>F >> I assume I'm one of the 'kooks' since I no longer have anything to F >> offer what the VMS management seems to desire, sales.  I'm in that H >> position due to (in part) the (in my judgement) bad decisions by the G >> owners of VMS.  I have only one VMS customer left, an ISV who keeps  6 >> asking me silly questions such as "how about java?" >> > A > A few years ago, I installed a Java Development Kit on VMS.  I  E > downloaded a bunch of stuff from somewhere on SUN.COM and followed  J > directions.  The developers who requested it were apparently happy with K > it.  I think it was JDK 1.2 but I won't swear to it.  Don't know if it's  , > still available.  Have you looked for one? >   @ The stories that I hear is that if your application is data I/O $ intensive, java doesn't do too well.  H Regardless, the application is written mainly in VAX/DEC Basic, and the B database mainly in Macro-32.  The application works well, and the I development environment is robust enough that over the years the ISV has  F become dominant in his market.  As long as things are going well, why = change?  What's wrong with "if it ain't broke, don't fix it"?   I The ISV has concerns about finding new people to work with the software.  G   My response was, "Don't look for people who know VMS and Basic.  I'm  H sure they are out there.  You'd be better off finding 'good' people and C training them on your system.  You'll have to train regardless, so  E learning VMS and Basic is just a bit more training.  Good people can  ; learn."  I also mentioned the HP web site and job listings.    --  4 David Froble                       Tel: 724-529-0450> Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc.  170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  # Date: Fri, 16 Jun 2006 19:51:01 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> , Subject: Re: Open VMS OS recovery on Itanium2 Message-ID: <FYDkg.2009$dA1.1419@news.cpqcorp.net>   Bob Koehler wrote:f > In article <IaGdnfbrubKg7g3ZnZ2dnUVZ_r6dnZ2d@comcast.com>, "Earl Lakia" <elakia@hotmail.com> writes:= >>* Acpi(HWP0002,700)/Pci(1|1)/Uart(9600 N81)/VenMsg(Vt100+)  1 >>* Acpi(PNP0501,0)/Uart(9600 N81)/VenMsg(PcAnsi)  > E >    Gee, that looks painful.  How well are these strings documented? ' >    (I don't have my first IA-64 yet.)   H They would look scary. But don't worry, you would never have to come up E with or type in such a string. If you're working down at the console  G level, such strings are displayed in a menu and you can select the one  3 you want as the console input/output serial device.   G But most users will never have to deal with that. Upon delivery, a new  B Integrity box with OpenVMS already has the correct console serial 8 input/output devices set up, and it auto-boots into the H factory-installed OpenVMS software, which acts just like the FIS you've G been used to on Alpha, or like the Alpha installation CD. In practical  I terms, you really don't even need to learn much about the console -- you  E can simply run SYS$MANAGER:BOOT_OPTIONS.COM to select or change your  C boot device, running it from the VMS system disk if VMS is already  G installed, or from the VMS binary DVD if VMS were not on disk for some  H reason (this DVD acts just like the Alpha installation CD and gives you D the same familiar list of options, including the one to execute DCL J commands -- you can then just execute BOOT_OPTIONS.COM from the CD there).   ------------------------------  % Date: Fri, 16 Jun 2006 15:18:31 -0700 , From: Ken Fairfield <my.full.name@intel.com>E Subject: Q: (Long)  DCL symbols not shown by Show Symbol [SLS V2.9H]? + Message-ID: <e6vano$7b0$1@news01.intel.com>   , This is a multi-part message in MIME format.& --------------050305040703080602070900; Content-Type: text/plain; charset=ISO-8859-1; format=flowed  Content-Transfer-Encoding: 7bit   A Having worked with VMS for more than 20 years, I really thought I = understood DCL.  But here's a puzzle I just can't understand!   > In the context of SLS's POST_PROCESS_EACH.COM (and similar forF PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),H I was trying to determine what *symbols* are available to that procedureF (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toC Backup and Restore Operations" is known to be incorrect).  Near the 8 beginning of my procedure, I inserted the following DCL:    C $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  $ Show Symbol *  $ Show Symbol /Local  *  $ Show Symbol /Global *  $ Show Symbol /Local  status $ Show Symbol /Global status $ Show Symbol /Local  statusmsg  $ Show Symbol /Global statusmsg  $ Show Symbol first_reel $ Show Symbol last_reel  $ Show Symbol first  $ Show Symbol last $ Show Symbol status $ Show Symbol statusmsg C $Write Sys$Output "''F$Fao("!/ !30*% In POST_PROCESS_EACH !30*%")'"     A There's a lot of redundancy here as I was trying "many" different D approaches.  Note that the documentation claims that all of 'first',E 'last', 'status' and 'statusmsg', are supposed to be available to all G four procedures.  'first_reel' and 'last_reel' are *not* documented but - are, in fact, available in POST_PROCESS_EACH.   F I discovered three things that I cannot explain (see the output at the bottom of this post):   C     1) *Neither* 'first_reel' nor 'last_reel' are present in any of @        the wildcard Show Symbol commands.  They are present on a4        Show Symbol of those names.  How can that be?  A     2) 'status' is not present on any of the wildcard Show Symbol B        commands, nor on "Show Symbol [ /Local | /Global ] status".C        However, the local symbol 'status' is present (see output of A        the next to last Show Symbol command below).  How can that         be??   D     3) 'statusmsg' does not appear in *any* Show Symbol output, even@        the last.  However, it is present. For example, I can do:  9          $ Write Sys$Output "Final status = ''statusmsg'"   C        and have, e.g, "Final status = BACKUP-W-ACCONFLICT," written F        to the log file, and this after testing $ If statusmsg.Nes."" .        How can this be???   A I have tried to reproduce some of these effects interactively, by E defining local and global symbols of the same name but with different G values, and by varying "symbol assign (:=)" versus "string assign (=)", 7 but nothing unexpected, nothing like the above, occurs.   D Can anyone explain what is happening?  Is there a 3rd, or 4th, class? of symbols I've never heard of that are hidden (sometimes) from # Show Symbol??  Have I gone crazy???        Regards, Ken --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com  M ============================================================================= G $Write Sys$Output "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  	 %%%%%%%%%  %%%%%%%%%%%%%%%%%%%%%    " 4 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%% %%   $ Show Symbol *     $RESTART == "FALSE"    $SEVERITY == "1"     $STATUS == "%X00010001"5    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001     BACKUP_TYPE == "VMSBACKUP"     BTYPE = "WEEKLY_DAY5"    BUTYPE == "Weekly" '    CONTINUE == "RA2SW_WW24_2006_WEEKLY" 9    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002     DB_FILE_QUALS == ""6    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002    DENSITY == "COMP"    DEVICE = "WS$SDISK:"     DRIVE_TYPE == "" 4    END_TM == 0   Hex = 00000000  Octal = 00000000000    FILES_1 == "WS$SDISK"    FILES_2 == "WS$S2DISK"     FILES_3 == "WS_LOGS"     FILES_4 == "DOSD_DUMP366"    FILES_5 == "DOSD_DUMP367"    FULL == "0"    HISTORY_SET == "IMAGE" 6    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000    LCS_WW == "200624"     LISTING_GEN == ""    LOG_FILE == "/NOPRINT" A    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM"     MEDIA_TYPE == "TZ89" >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000@    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000I    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 B    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000<    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000    NEXT_JOB == "" 2    NOTES == "RA2SW Weekly Image Backups WW24 2006"6    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001    OFFSITE_DATE == ""     ONSITE_DATE == ""    P1 = "RA2SW_WEEKLY_DAY5_SBK"     P2 = "1"     P3 = "WS$SDISK:" 
    P4 = ""
    P5 = ""
    P6 = ""
    P7 = ""
    P8 = ""$    PARAMS == "RA2SW_WEEKLY_DAY5_SBK";    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" ;    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 6    PREALLOC == 0   Hex = 00000000  Octal = 00000000000    PRE_PROCESS_EACH == "!";    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"     PRINT_Q == "SYS$PRINT"     PRIVS == "BYPASS"6    PROGRESS == 0   Hex = 00000000  Octal = 00000000000$    PROTECTION == "S:RW,O:RW,G:R,W:R"<    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"7    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 A    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 (    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"9    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 $    REPLY_MSG == "REQUEST/TO=(TAPES)">    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""7    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 !    SBK_NAME = "RA2SW_WEEKLY_DAY5" +    SBK_STARTED == "16-JUN-2006 00:35:08.81"     SBK_VOLUMES == "VS0194"    SBUPDT_Q == "SLS$SW_TAPE";    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050     SEVERITY_LEVEL == "F";    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 =    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 <    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154=    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 :    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224    START_TM == "75"     STATUS_MAIL == "":    SUMMARY_FILE == 2   Hex = 00000002  Octal = 000000000028    TAPE_COUNT == 1   Hex = 00000001  Octal = 000000000019    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000     TAPE_POOL == ""@    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001    WORKWEEK == "24"     WORKWEEK_Q == "Q2"  $ Show Symbol /Local  *     BTYPE = "WEEKLY_DAY5"    DEVICE = "WS$SDISK:" A    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM"     P1 = "RA2SW_WEEKLY_DAY5_SBK"     P2 = "1"     P3 = "WS$SDISK:" 
    P4 = ""
    P5 = ""
    P6 = ""
    P7 = ""
    P8 = ""!    SBK_NAME = "RA2SW_WEEKLY_DAY5"  $ Show Symbol /Global *     $RESTART == "FALSE"    $SEVERITY == "1"     $STATUS == "%X00010001"5    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001     BACKUP_TYPE == "VMSBACKUP"     BUTYPE == "Weekly" '    CONTINUE == "RA2SW_WW24_2006_WEEKLY" 9    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002     DB_FILE_QUALS == ""6    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002    DENSITY == "COMP"    DRIVE_TYPE == "" 4    END_TM == 0   Hex = 00000000  Octal = 00000000000    FILES_1 == "WS$SDISK"    FILES_2 == "WS$S2DISK"     FILES_3 == "WS_LOGS"     FILES_4 == "DOSD_DUMP366"    FILES_5 == "DOSD_DUMP367"    FULL == "0"    HISTORY_SET == "IMAGE" 6    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000    LCS_WW == "200624"     LISTING_GEN == ""    LOG_FILE == "/NOPRINT"     MEDIA_TYPE == "TZ89" >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000@    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000I    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 B    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000<    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000    NEXT_JOB == "" 2    NOTES == "RA2SW Weekly Image Backups WW24 2006"6    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001    OFFSITE_DATE == ""     ONSITE_DATE == ""$    PARAMS == "RA2SW_WEEKLY_DAY5_SBK";    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" ;    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 6    PREALLOC == 0   Hex = 00000000  Octal = 00000000000    PRE_PROCESS_EACH == "!";    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"     PRINT_Q == "SYS$PRINT"     PRIVS == "BYPASS"6    PROGRESS == 0   Hex = 00000000  Octal = 00000000000$    PROTECTION == "S:RW,O:RW,G:R,W:R"<    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"7    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 A    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 (    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"9    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 $    REPLY_MSG == "REQUEST/TO=(TAPES)">    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""7    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 +    SBK_STARTED == "16-JUN-2006 00:35:08.81"     SBK_VOLUMES == "VS0194"    SBUPDT_Q == "SLS$SW_TAPE";    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050     SEVERITY_LEVEL == "F";    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 =    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 <    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154=    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 :    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224    START_TM == "75"     STATUS_MAIL == "":    SUMMARY_FILE == 2   Hex = 00000002  Octal = 000000000028    TAPE_COUNT == 1   Hex = 00000001  Octal = 000000000019    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000     TAPE_POOL == ""@    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001    WORKWEEK == "24"     WORKWEEK_Q == "Q2"  $ Show Symbol /Local  status= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Global status= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Local  statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Global statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol first_reel    FIRST_REEL = "VS0194" $ Show Symbol last_reel     LAST_REEL = "VS0194"  $ Show Symbol first = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol last= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol status    STATUS = "%X10A38410" $ Show Symbol statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $Write Sys$Output " 6   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%  %%%"  6   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%  %%% M =============================================================================     & --------------050305040703080602070900 Content-Type: text/plain;   name="SYMBOLS.TXT"  Content-Transfer-Encoding: 7bit  Content-Disposition: inline;  filename="SYMBOLS.TXT"   A Having worked with VMS for more than 20 years, I really thought I = understood DCL.  But here's a puzzle I just can't understand!   > In the context of SLS's POST_PROCESS_EACH.COM (and similar forF PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),H I was trying to determine what *symbols* are available to that procedureF (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toC Backup and Restore Operations" is known to be incorrect).  Near the 8 beginning of my procedure, I inserted the following DCL:    C $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  $ Show Symbol *  $ Show Symbol /Local  *  $ Show Symbol /Global *  $ Show Symbol /Local  status $ Show Symbol /Global status $ Show Symbol /Local  statusmsg  $ Show Symbol /Global statusmsg  $ Show Symbol first_reel $ Show Symbol last_reel  $ Show Symbol first  $ Show Symbol last $ Show Symbol status $ Show Symbol statusmsg C $Write Sys$Output "''F$Fao("!/ !30*% In POST_PROCESS_EACH !30*%")'"     A There's a lot of redundancy here as I was trying "many" different D approaches.  Note that the documentation claims that all of 'first',E 'last', 'status' and 'statusmsg', are supposed to be available to all G four procedures.  'first_reel' and 'last_reel' are *not* documented but - are, in fact, available in POST_PROCESS_EACH.   F I discovered three things that I cannot explain (see the output at the bottom of this post):   B    1) *Neither* 'first_reel' nor 'last_reel' are present in any of?       the wildcard Show Symbol commands.  They are present on a 3       Show Symbol of those names.  How can that be?   @    2) 'status' is not present on any of the wildcard Show SymbolA       commands, nor on "Show Symbol [ /Local | /Global ] status". B       However, the local symbol 'status' is present (see output of@       the next to last Show Symbol command below).  How can that
       be??  C    3) 'statusmsg' does not appear in *any* Show Symbol output, even ?       the last.  However, it is present. For example, I can do:   8         $ Write Sys$Output "Final status = ''statusmsg'"  B       and have, e.g, "Final status = BACKUP-W-ACCONFLICT," writtenE       to the log file, and this after testing $ If statusmsg.Nes."" .        How can this be???  A I have tried to reproduce some of these effects interactively, by E defining local and global symbols of the same name but with different G values, and by varying "symbol assign (:=)" versus "string assign (=)", 7 but nothing unexpected, nothing like the above, occurs.   D Can anyone explain what is happening?  Is there a 3rd, or 4th, class? of symbols I've never heard of that are hidden (sometimes) from # Show Symbol??  Have I gone crazy???       Regards, Ken   ( --------------050305040703080602070900--   ------------------------------  % Date: Sat, 17 Jun 2006 01:49:31 +0200 / From: Paul Sture <paul.sture.nospam@hispeed.ch> Y Subject: Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS  V2.9H]  V2.9 ; Message-ID: <84b50$4493438c$50db5015$30322@news.hispeed.ch>    Ken Fairfield wrote:C > Having worked with VMS for more than 20 years, I really thought I ? > understood DCL.  But here's a puzzle I just can't understand!  > @ > In the context of SLS's POST_PROCESS_EACH.COM (and similar forH > PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),J > I was trying to determine what *symbols* are available to that procedureH > (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toE > Backup and Restore Operations" is known to be incorrect).  Near the : > beginning of my procedure, I inserted the following DCL: >  > E > $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  > $ Show Symbol *  > $ Show Symbol /Local  *  > $ Show Symbol /Global *   ? What results do you get with /ALL instead of the wildcard? i.e.    $ show symbol /local /all  $ show symbol /global /all   ------------------------------  % Date: Fri, 16 Jun 2006 15:32:52 -0700 , From: Ken Fairfield <my.full.name@intel.com>N Subject: Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H]+ Message-ID: <e6vbik$7m6$2@news01.intel.com>   A Having worked with VMS for more than 20 years, I really thought I = understood DCL.  But here's a puzzle I just can't understand!   > In the context of SLS's POST_PROCESS_EACH.COM (and similar forF PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),H I was trying to determine what *symbols* are available to that procedureF (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toC Backup and Restore Operations" is known to be incorrect).  Near the 8 beginning of my procedure, I inserted the following DCL:    C $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  $ Show Symbol *  $ Show Symbol /Local  *  $ Show Symbol /Global *  $ Show Symbol /Local  status $ Show Symbol /Global status $ Show Symbol /Local  statusmsg  $ Show Symbol /Global statusmsg  $ Show Symbol first_reel $ Show Symbol last_reel  $ Show Symbol first  $ Show Symbol last $ Show Symbol status $ Show Symbol statusmsg C $Write Sys$Output "''F$Fao("!/ !30*% In POST_PROCESS_EACH !30*%")'"     A There's a lot of redundancy here as I was trying "many" different D approaches.  Note that the documentation claims that all of 'first',E 'last', 'status' and 'statusmsg', are supposed to be available to all G four procedures.  'first_reel' and 'last_reel' are *not* documented but - are, in fact, available in POST_PROCESS_EACH.   F I discovered three things that I cannot explain (see the output at the bottom of this post):   C     1) *Neither* 'first_reel' nor 'last_reel' are present in any of @        the wildcard Show Symbol commands.  They are present on a4        Show Symbol of those names.  How can that be?  A     2) 'status' is not present on any of the wildcard Show Symbol B        commands, nor on "Show Symbol [ /Local | /Global ] status".C        However, the local symbol 'status' is present (see output of A        the next to last Show Symbol command below).  How can that         be??   D     3) 'statusmsg' does not appear in *any* Show Symbol output, even@        the last.  However, it is present. For example, I can do:  9          $ Write Sys$Output "Final status = ''statusmsg'"   C        and have, e.g, "Final status = BACKUP-W-ACCONFLICT," written F        to the log file, and this after testing $ If statusmsg.Nes."" .        How can this be???   A I have tried to reproduce some of these effects interactively, by E defining local and global symbols of the same name but with different G values, and by varying "symbol assign (:=)" versus "string assign (=)", 7 but nothing unexpected, nothing like the above, occurs.   D Can anyone explain what is happening?  Is there a 3rd, or 4th, class? of symbols I've never heard of that are hidden (sometimes) from # Show Symbol??  Have I gone crazy???        Regards, Ken  N ==============================================================================G $Write Sys$Output "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  	 %%%%%%%%%  %%%%%%%%%%%%%%%%%%%%%    " 4 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%% %%   $ Show Symbol *     $RESTART == "FALSE"    $SEVERITY == "1"     $STATUS == "%X00010001"5    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001     BACKUP_TYPE == "VMSBACKUP"     BTYPE = "WEEKLY_DAY5"    BUTYPE == "Weekly" '    CONTINUE == "RA2SW_WW24_2006_WEEKLY" 9    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002     DB_FILE_QUALS == ""6    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002    DENSITY == "COMP"    DEVICE = "WS$SDISK:"     DRIVE_TYPE == "" 4    END_TM == 0   Hex = 00000000  Octal = 00000000000    FILES_1 == "WS$SDISK"    FILES_2 == "WS$S2DISK"     FILES_3 == "WS_LOGS"     FILES_4 == "DOSD_DUMP366"    FILES_5 == "DOSD_DUMP367"    FULL == "0"    HISTORY_SET == "IMAGE" 6    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000    LCS_WW == "200624"     LISTING_GEN == ""    LOG_FILE == "/NOPRINT" A    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM"     MEDIA_TYPE == "TZ89" >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000@    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000I    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 B    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000<    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000    NEXT_JOB == "" 2    NOTES == "RA2SW Weekly Image Backups WW24 2006"6    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001    OFFSITE_DATE == ""     ONSITE_DATE == ""    P1 = "RA2SW_WEEKLY_DAY5_SBK"     P2 = "1"     P3 = "WS$SDISK:" 
    P4 = ""
    P5 = ""
    P6 = ""
    P7 = ""
    P8 = ""$    PARAMS == "RA2SW_WEEKLY_DAY5_SBK";    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" ;    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 6    PREALLOC == 0   Hex = 00000000  Octal = 00000000000    PRE_PROCESS_EACH == "!";    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"     PRINT_Q == "SYS$PRINT"     PRIVS == "BYPASS"6    PROGRESS == 0   Hex = 00000000  Octal = 00000000000$    PROTECTION == "S:RW,O:RW,G:R,W:R"<    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"7    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 A    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 (    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"9    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 $    REPLY_MSG == "REQUEST/TO=(TAPES)">    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""7    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 !    SBK_NAME = "RA2SW_WEEKLY_DAY5" +    SBK_STARTED == "16-JUN-2006 00:35:08.81"     SBK_VOLUMES == "VS0194"    SBUPDT_Q == "SLS$SW_TAPE";    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050     SEVERITY_LEVEL == "F";    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 =    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 <    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154=    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 :    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224    START_TM == "75"     STATUS_MAIL == "":    SUMMARY_FILE == 2   Hex = 00000002  Octal = 000000000028    TAPE_COUNT == 1   Hex = 00000001  Octal = 000000000019    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000     TAPE_POOL == ""@    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001    WORKWEEK == "24"     WORKWEEK_Q == "Q2"  $ Show Symbol /Local  *     BTYPE = "WEEKLY_DAY5"    DEVICE = "WS$SDISK:" A    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM"     P1 = "RA2SW_WEEKLY_DAY5_SBK"     P2 = "1"     P3 = "WS$SDISK:" 
    P4 = ""
    P5 = ""
    P6 = ""
    P7 = ""
    P8 = ""!    SBK_NAME = "RA2SW_WEEKLY_DAY5"  $ Show Symbol /Global *     $RESTART == "FALSE"    $SEVERITY == "1"     $STATUS == "%X00010001"5    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001     BACKUP_TYPE == "VMSBACKUP"     BUTYPE == "Weekly" '    CONTINUE == "RA2SW_WW24_2006_WEEKLY" 9    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002     DB_FILE_QUALS == ""6    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002    DENSITY == "COMP"    DRIVE_TYPE == "" 4    END_TM == 0   Hex = 00000000  Octal = 00000000000    FILES_1 == "WS$SDISK"    FILES_2 == "WS$S2DISK"     FILES_3 == "WS_LOGS"     FILES_4 == "DOSD_DUMP366"    FILES_5 == "DOSD_DUMP367"    FULL == "0"    HISTORY_SET == "IMAGE" 6    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000    LCS_WW == "200624"     LISTING_GEN == ""    LOG_FILE == "/NOPRINT"     MEDIA_TYPE == "TZ89" >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000@    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000I    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 B    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000<    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000    NEXT_JOB == "" 2    NOTES == "RA2SW Weekly Image Backups WW24 2006"6    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001    OFFSITE_DATE == ""     ONSITE_DATE == ""$    PARAMS == "RA2SW_WEEKLY_DAY5_SBK";    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" ;    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 6    PREALLOC == 0   Hex = 00000000  Octal = 00000000000    PRE_PROCESS_EACH == "!";    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"     PRINT_Q == "SYS$PRINT"     PRIVS == "BYPASS"6    PROGRESS == 0   Hex = 00000000  Octal = 00000000000$    PROTECTION == "S:RW,O:RW,G:R,W:R"<    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"7    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 A    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 (    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"9    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 $    REPLY_MSG == "REQUEST/TO=(TAPES)">    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""7    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 +    SBK_STARTED == "16-JUN-2006 00:35:08.81"     SBK_VOLUMES == "VS0194"    SBUPDT_Q == "SLS$SW_TAPE";    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050     SEVERITY_LEVEL == "F";    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 =    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 <    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154=    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 :    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224    START_TM == "75"     STATUS_MAIL == "":    SUMMARY_FILE == 2   Hex = 00000002  Octal = 000000000028    TAPE_COUNT == 1   Hex = 00000001  Octal = 000000000019    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000     TAPE_POOL == ""@    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001    WORKWEEK == "24"     WORKWEEK_Q == "Q2"  $ Show Symbol /Local  status= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Global status= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Local  statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol /Global statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol first_reel    FIRST_REEL = "VS0194" $ Show Symbol last_reel     LAST_REEL = "VS0194"  $ Show Symbol first = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol last= %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $ Show Symbol status    STATUS = "%X10A38410" $ Show Symbol statusmsg = %DCL-W-UNDSYM, undefined symbol - check validity and spelling  $Write Sys$Output " 6   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%  %%%"  6   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  %%%%%%%%%%%%%%%%%%%%%%%%%%%  %%% N ==============================================================================   --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com   ------------------------------  % Date: Fri, 16 Jun 2006 15:49:38 -0500 C From: pechter@pcp09822625pcs.eatntn01.nj.comcast.net (Bill Pechter) 7 Subject: Re: Question about number of Vax System owners : Message-ID: <ItWdnQzRBOv_hA7ZnZ2dnUVZ_oidnZ2d@comcast.com>  3 In article <f8cbqdXHq8z3@eisner.encompasserve.org>, : Bob Koehler <koehler@eisner.aspm.encompasserve.org> wrote:H >In article <e6su2h03oe@enews4.newsguy.com>, healyzh@aracnet.com writes:, >> Michael Kraemer <M.Kraemer@gsi.de> wrote: >>> DBT schrieb:@ >>> > I am curious how many Vax users there are still out there.M >>> > We are looking at offering Vax systems and Vax based hardware solutions  >>  6 >>> well, prepare to support a future hobbyist market. >>  K >> How much of a VAX Hobbyist market is there?  Of that what percentage are M >> Unix users with some strange fixation on VAX hardware and how many are VMS  >> users?  Just curious. >>   > E >   I don't think there's a lot of attraction to running UNIX on slow F >   hardware.  I know of exactly one fellow who might be interested inC >   having a VAX running Ultirx just so he can say he does.  In the E >   home/hobbyist market most folks are much more likely to pick up a I >   cheap PC and load Linux if they're looking for a UNIX-ish experience.    Make that two.  B I've got the Vaxstation 3100M38 for it.  It's running VAX/VMS 7.2.J I was looking to put Ulrix on it to compare it with VMS and NetBSD on the  same platform.   > H >   People looking for a "real" UNIX home system are much more likely toG >   pick up a cheap used SPARC than a similarly priced VAX.  No need to  >   be patient.  >   A Got 'em  SparcStation2's, IPX's, ELC's, Ultra1E/170's.  Ultra5's.   5 Still want to see BSD and Ultrix on the Vaxstation...   ! I've also got FreeBSD, Linux etc.   9 I'd love to see what SunOS 4 would've been on the ultra1.   > There's still nothing like SunOS 4.1.x on the older Sparcs for5 reasonable performance with minimal memory (48-64mb).   G Linux on Sparc's not as good on the old stuff.  Solaris runs like a dog  with less than 256mb.   8 VAX/VMS w/o DECwindows wasn't too bad on the Vaxstation.F I took 7.3 and loaded it in Simh on the 2.8ghz CentOS desktop here and1 got about 14 MIPS with an old test I used to run.   D The same MIPS test came out at 3.x on the Vaxstation so it's not too bad of a test.   Bill --   --  H   d|i|g|i|t|a|l had it THEN.  Don't you wish you could still buy it now!#   pechter-at-ureachtechnologies.com    ------------------------------  % Date: Sat, 17 Jun 2006 03:26:17 +0200 ( From: Michael Kraemer <M.Kraemer@gsi.de>7 Subject: Re: Question about number of Vax System owners / Message-ID: <e6vln3$590$00$1@news.t-online.com>    Bill Pechter schrieb: D > I've got the Vaxstation 3100M38 for it.  It's running VAX/VMS 7.2.L > I was looking to put Ulrix on it to compare it with VMS and NetBSD on the  > same platform.  B It would run, just a bit slow, compared with the MIPS-based boxes.: I loaded it on a M30, but unfortunately it doesn't support2 the SPX gfx card of the machine (only GPX, AFAIK).6 That's the problem with the VAXes, there's no "native"5 UNIX for them, in particular the most attractive ones G like the VAXstation 4000 series and 3100/M76 do not run Ultrix anymore.    > ; > I'd love to see what SunOS 4 would've been on the ultra1.  > @ > There's still nothing like SunOS 4.1.x on the older Sparcs for7 > reasonable performance with minimal memory (48-64mb).  > I > Linux on Sparc's not as good on the old stuff.  Solaris runs like a dog  > with less than 256mb.   8 That's the problem, "modern" Unices like Linux or NetBSD@ may in principle run on old hardware, but the hardware resources3 are quite a bit limited, so one might be better off " to run the contemporary native OS.   > : > VAX/VMS w/o DECwindows wasn't too bad on the Vaxstation.  F Even w/ DECwindows a VAXstation 4000-90 or even -VLC isn't too bad ... (for hobbyist usage)   ------------------------------  % Date: Fri, 16 Jun 2006 14:52:25 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> - Subject: Re: Sending HTML mail from VMS MAIL? , Message-ID: <4492FDE8.54BDB935@teksavvy.com>   Syltrem wrote: > > $ cr[0,8]=13 > > $ lf[0,8]=109 > > $ subject="[BACKUP] VMS Backup Summary" + cr + lf + - 4 > >                "Mime-Version: 1.0" + cr + lf + -, > >                "Content-Type: text/HTML"6 > > $ mail/sub="''subject'" 'summary_file support_dist     > That works great !    G It may work today, but I am not sure this is garanteed to work forever.    ------------------------------  % Date: Fri, 16 Jun 2006 15:25:26 -0400  From: norm.raphael@metso.com- Subject: Re: Sending HTML mail from VMS MAIL? Q Message-ID: <OF55F5EFB3.31E24B7F-ON8525718F.006A5CD9-8525718F.006AA067@metso.com>   H JF Mezei <jfmezei.spamnot@teksavvy.com> wrote on 06/16/2006 02:52:25 PM:   > Syltrem wrote: > > > $ cr[0,8]=13 > > > $ lf[0,8]=10; > > > $ subject="[BACKUP] VMS Backup Summary" + cr + lf + - 6 > > >                "Mime-Version: 1.0" + cr + lf + -. > > >                "Content-Type: text/HTML"8 > > > $ mail/sub="''subject'" 'summary_file support_dist >  >  > > That works great ! >  > I > It may work today, but I am not sure this is garanteed to work forever.    Okay, I'll bite.   Why does it work? I Why is that stuff in the subject and what/why/how is it processed - since 9 it obviously gets used up somehow, i.e., what's going on?   / Then,  Why would it break? What would break it?    ------------------------------  # Date: Fri, 16 Jun 2006 19:40:15 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)- Subject: Re: Sending HTML mail from VMS MAIL? 6 Message-ID: <00A574CA.7B59ECD2@SSRL.SLAC.STANFORD.EDU>  p In article <OF55F5EFB3.31E24B7F-ON8525718F.006A5CD9-8525718F.006AA067@metso.com>, norm.raphael@metso.com writes: >  > I >JF Mezei <jfmezei.spamnot@teksavvy.com> wrote on 06/16/2006 02:52:25 PM:  >  >> Syltrem wrote:  >> > > $ cr[0,8]=13  >> > > $ lf[0,8]=10 < >> > > $ subject="[BACKUP] VMS Backup Summary" + cr + lf + -7 >> > >                "Mime-Version: 1.0" + cr + lf + - / >> > >                "Content-Type: text/HTML" 9 >> > > $ mail/sub="''subject'" 'summary_file support_dist  >> >> >> > That works great !  >> >>J >> It may work today, but I am not sure this is garanteed to work forever. >  >Okay, I'll bite.  >  >Why does it work?J >Why is that stuff in the subject and what/why/how is it processed - since: >it obviously gets used up somehow, i.e., what's going on?  I This works because the value in the "subject" has line breaks in it.  The M result is that mail clients get to interpret what the mail user agent thought + was only one header, the subject header, as   $ Subject: [BACKUP] VMS Backup Summary Mime-Version: 1.0  Content-Type: text/HTML   C thereby advising it to process the contents of the message as HTML.   H The CR & LF values are carriage-return and linefeed.  There are no blankG lines between the Subject: header and the injected headers, so they are L properly processed; if you put your content-type header in the message body,H there's a blank line (unless you use a speical mail transport to prevent% that) and the header isn't processed.    Hope this helps!   > Why would it break?   G A message transport might at some point decide to escape the CRLF value G in the header and make it a long subject line.  I don't know how likely  that is.   -- Alan    ------------------------------  % Date: Fri, 16 Jun 2006 16:14:44 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> - Subject: Re: Sending HTML mail from VMS MAIL? , Message-ID: <4493112D.AAF63B00@teksavvy.com>   norm.raphael@metso.com wrote:  > Why does it work? K > Why is that stuff in the subject and what/why/how is it processed - since ; > it obviously gets used up somehow, i.e., what's going on?   K Here is a header generated by the MAIL command to a internet email address:   % Date: Fri, 16 Jun 2006 16:06:36 -0400 , Message-Id: <06061616063660@vuxination.cake>3 From: jfmezei@vuxination.cake (Jean-Franois Mezei)  To: JFMEZEI@vuxination.cake  Subject: Chocolate cookie ! X-VMS-To: jfmezei@vuxination.cake  <blank line> contents of message   . With the trick: the above header would become:  % Date: Fri, 16 Jun 2006 16:06:36 -0400 , Message-Id: <06061616063660@vuxination.cake>3 From: jfmezei@vuxination.cake (Jean-Franois Mezei)  To: JFMEZEI@vuxination.cake  Subject: Chocolate cookie  Mime-Version: 1.0  Content-Type: text/HTML ! X-VMS-To: jfmezei@vuxination.cake  <blank line> contents of message     G aka: subject =  "Chocoolate cookie" + CRLF + "Mime-Version: 1.0" + CRLF  + "Content-Type: text/HTML" C  causes the mail foreign protocol to blindly write the CRLFs to the A temporary file. The symbiont and recipient don't see those tricks F because by that time, the single subject has become "Chocolate cookie"C followed by totally separate lines which happen to be bona-fide RFC 
 header lines.    ------------------------------  % Date: Fri, 16 Jun 2006 17:20:35 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> - Subject: Re: Sending HTML mail from VMS MAIL? : Message-ID: <ysKdnSnh6dA4vQ7ZnZ2dnUVZ_qidnZ2d@comcast.com>   norm.raphael@metso.com wrote:    > J > JF Mezei <jfmezei.spamnot@teksavvy.com> wrote on 06/16/2006 02:52:25 PM: >  >  >>Syltrem wrote: >> >>>>$ cr[0,8]=13 >>>>$ lf[0,8]=109 >>>>$ subject="[BACKUP] VMS Backup Summary" + cr + lf + - 4 >>>>               "Mime-Version: 1.0" + cr + lf + -, >>>>               "Content-Type: text/HTML"6 >>>>$ mail/sub="''subject'" 'summary_file support_dist >> >> >>>That works great !  >> >>I >>It may work today, but I am not sure this is garanteed to work forever.  >  >  > Okay, I'll bite. >  > Why does it work? K > Why is that stuff in the subject and what/why/how is it processed - since ; > it obviously gets used up somehow, i.e., what's going on?  > 1 > Then,  Why would it break? What would break it?  >  >   I I'd say that it works because it provides a way to get unsupported stuff   into the message headers.   F It might break because it does unsupported things in unsupported ways.  B You still have to provide your own html text for the message body.   ------------------------------    Date: 16 Jun 2006 11:57:49 -0700 From: transnet@vrx.netD Subject: whats the largest usable internal hard drive on vaxstation?C Message-ID: <1150484268.959523.198650@h76g2000cwa.googlegroups.com>   A I have a few vaxstations, 2100s M76 and so forth (rather typical)   @ what's the largest storage capacity hard disk I can put in these things? B I guess it depends on the bootloader (BIOS) so if there is a newer version it can handle more. ! I use openvms 7.1 on it right now   = I doubt I can use a modern 200 gig IDE or 136GB SCSI drive or 3 something, but I am curious to know what I can use?   3 also like to know for my decserver 3100 (alpha vms)    ------------------------------  % Date: Fri, 16 Jun 2006 15:26:06 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> H Subject: Re: whats the largest usable internal hard drive on vaxstation?, Message-ID: <449305CA.D2A7588A@teksavvy.com>   transnet@vrx.net wrote:  > C > I have a few vaxstations, 2100s M76 and so forth (rather typical)   E I don't recall a Vaxstation 2100.   There are 3100 of various models.   G The Vaxstation 3100 models 40 and lower can only take a max 1 gig disk. % Models after that don't have a limit.   L You'll find that the disks sporting a compatible SCSI stop at about 10 gigs.  5 > also like to know for my decserver 3100 (alpha vms)   8 decserver computers were MIPS based and did not run VMS.   ------------------------------  + Date: Fri, 16 Jun 2006 14:33:58 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda)H Subject: Re: whats the largest usable internal hard drive on vaxstation?2 Message-ID: <06061614335843_2022872F@antinode.org>   From: transnet@vrx.net  C > I have a few vaxstations, 2100s M76 and so forth (rather typical)       3100?  B > what's the largest storage capacity hard disk I can put in these	 > things? D > I guess it depends on the bootloader (BIOS) so if there is a newer > version it can handle more. # > I use openvms 7.1 on it right now  > ? > I doubt I can use a modern 200 gig IDE or 136GB SCSI drive or 5 > something, but I am curious to know what I can use?  > 5 > also like to know for my decserver 3100 (alpha vms)   "    Have you looked at the VMS FAQ?  "       http://hp.com/go/openvms/faq      In particular: G    9.5  What is the largest disk volume size OpenVMS can access?  [...]   H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 16 Jun 2006 12:33:44 -0700 From: transnet@vrx.netH Subject: Re: whats the largest usable internal hard drive on vaxstation?C Message-ID: <1150486424.259375.317950@g10g2000cwb.googlegroups.com>   # Yes, sorry should be 3100 not 2100. $ And model M76, I don't have any 40s.  = I don't believe there is no limit, as you just mentioned, the D compatible scsi interface limits it. so the old scsi style, I'll see what I can dig up.  E as for the decserver, it is an alpha and it is running vms its a 3100 ! model 300 or something like that.   4 anyhow, I think it's the same limitation, I'll checkE there are 18gig scsi drives with 80 pin interfaces so those may be ok    T. JF Mezei wrote:  > transnet@vrx.net wrote:  > > E > > I have a few vaxstations, 2100s M76 and so forth (rather typical)  > G > I don't recall a Vaxstation 2100.   There are 3100 of various models.  > I > The Vaxstation 3100 models 40 and lower can only take a max 1 gig disk. ' > Models after that don't have a limit.  > N > You'll find that the disks sporting a compatible SCSI stop at about 10 gigs. > 7 > > also like to know for my decserver 3100 (alpha vms)  > : > decserver computers were MIPS based and did not run VMS.   ------------------------------  + Date: Fri, 16 Jun 2006 15:32:14 -0500 (CDT) * From: sms@antinode.org (Steven M. Schweda)H Subject: Re: whats the largest usable internal hard drive on vaxstation?2 Message-ID: <06061615321486_2022872F@antinode.org>   From: transnet@vrx.net  ? > I don't believe there is no limit, as you just mentioned, the F > compatible scsi interface limits it. so the old scsi style, I'll see > what I can dig up.  F    How does "the compatible scsi interface" limit it?  What's "the old> scsi style"?  I don't believe that you know whereof you speak.  G > as for the decserver, it is an alpha and it is running vms its a 3100 # > model 300 or something like that.   F    So it probably doesn't say "decserver" on the front.  It might help# to know (exactly) what it does say.   6 > anyhow, I think it's the same limitation, I'll checkG > there are 18gig scsi drives with 80 pin interfaces so those may be ok   B    You mean that the Alpha has the same limitation as the very oldH VAXes?  Or is it supposed to have the same (fictional) limitation as the newer VAXes?  Not likely.   H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  # Date: Fri, 16 Jun 2006 20:42:25 GMT # From: nospam@nouce.bellatlantic.net H Subject: Re: whats the largest usable internal hard drive on vaxstation?8 Message-ID: <jm5692l97iqg8adu2u51m8njg92t76kguj@4ax.com>  6 On 16 Jun 2006 11:57:49 -0700, transnet@vrx.net wrote:  B >I have a few vaxstations, 2100s M76 and so forth (rather typical) > A >what's the largest storage capacity hard disk I can put in these  >things?C >I guess it depends on the bootloader (BIOS) so if there is a newer  >version it can handle more." >I use openvms 7.1 on it right now > > >I doubt I can use a modern 200 gig IDE or 136GB SCSI drive or4 >something, but I am curious to know what I can use? > 4 >also like to know for my decserver 3100 (alpha vms)  ' After reading I see you ment a 3100/m76   ) I have two of these and the dope is this.   @ 1.07 GB for the boot drive (whatever unit it may be) and any aux@ drives are limited to SCSI-II limits and currently I'm running aA 18GB drive there.  With two or more  drives installed insure the  < fans (both of them) are working and clean or heat will be a  problem.  5 FYI: one of mine has a 1.07gb barcuda, 9GB maxtor and 6 a 18gb Seagate all work fine and runs reasonably cool.   Allison    ------------------------------   End of INFO-VAX 2006.334 ************************