1 INFO-VAX	Thu, 18 Aug 2005	Volume 2005 : Issue 460       Contents: Re: Australian DECUSE Cerner hopefully is using Zotob to show why hospitals should run VMS! / Re: Changing Uppercase filenames into Lowercase 8 Re: Companies not on VMS get a taste of coming disaster!4 Companies not on VMS get a taste of coming disaster! Re: DFG (Defrag) - OpenVMS Erro using OBNDRA from Fortran. % Re: Help Needed: Tape Backup Save Set : Re: How many files can you have in a VMS directory without: Re: How many files can you have in a VMS directory without: Re: How many files can you have in a VMS directory without: Re: How many files can you have in a VMS directory without: Re: How many files can you have in a VMS directory withoutF Re: How many files can you have in a VMS directory without performanceF Re: How many files can you have in a VMS directory without performanceP Re: How many files can you have in a VMS directory without performance   problem Re: HP 3rd quarter financials   Re: Investigating ACCVIO problem RAM ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' RE: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) ' Re: SAMBA for VMS (The saga continues!) + Simh terminal lines and networking with VMS / Re: Simh terminal lines and networking with VMS  Re: Squid for VMS  Re: Squid for VMS  Re: SYSMAN vs SYSGEN VMS as a SMTP client+ Zotob worm shows VMS notebooks needed ASAP! / Re: Zotob worm shows VMS notebooks needed ASAP! / Re: Zotob worm shows VMS notebooks needed ASAP!   F ----------------------------------------------------------------------  # Date: Thu, 18 Aug 2005 10:11:30 GMT % From: John Proctor <lost@nowhere.org>  Subject: Re: Australian DECUS 1 Message-ID: <2005081820112916807%lost@nowhereorg>   8 On 2005-08-18 08:41:44 +1000, dooleys@snowy.net.au said:  ( > I think they recently changed address,@ >  did you get it from http://www.encompass.asn.au/contact.shtml > Phil  G Thanks for that Phill, I e-mailed them to follow up on the application  ' that I sent in. We'll see what happens.    --   Regards, John D Proctor   ------------------------------    Date: 18 Aug 2005 08:45:11 -0700 From: bob@instantwhip.com N Subject: Cerner hopefully is using Zotob to show why hospitals should run VMS!C Message-ID: <1124379911.664722.272650@g14g2000cwa.googlegroups.com>   8 This is again a huge opportunity for VMS ... will HP and: Cerner and other VMS vendors take advantage of it?  Forget/ HP but hopefully compnaies like Cerner will ...    ------------------------------  % Date: Thu, 18 Aug 2005 06:43:04 -0500 . From: Alphaman <alphaman-nix-spam@alphant.com>8 Subject: Re: Changing Uppercase filenames into Lowercase7 Message-ID: <d0a1e$43047448$186088ed$19042@KNOLOGY.NET>    Fred Bach wrote: > Aaron, > 8 >  Not a bad idea when it's ready.  I don't like to post: >  poor code, unreadable or uncommented code, or code with; >  known bugs.  Before today, MAKELOWER.COM worked, but had  >  all four above problems.  :  :[snip]  : " >  ...  I'll wait a while, and putB >  it in use here at the lab before posting it to dcl.openvms.org.A >  I've seen some badly written code posted there, and complained ? >  about it, so I don't want to be guilty of my own complaints. @ >  (Frankly I think I could tidy up much of that code.  Not that+ >  the code below is any great example....)  > 2 >  Below is the current test copy of MAKELOWER.COM >   >  .. fred bach  music@triumf.ca    F You make some excellent points, and I have absolutely no problem with E people correcting code that they've seen and re-posting it as a "v2"  F version.  I encourage it, in fact, especially if the original code is F left intact as much as possible, and comments are judiciously used to  describe any changes.   I While this isn't as formal a process as a SourceForge or CVS, I think we  7 can easily manage this process informally at this time.    Thanks for your input, Aaron    ------------------------------    Date: 18 Aug 2005 08:37:33 -0700/ From: "Dr Tim" <tim.llewellyn@blueyonder.co.uk> A Subject: Re: Companies not on VMS get a taste of coming disaster! B Message-ID: <1124379453.538278.79400@g43g2000cwa.googlegroups.com>  C ... don't just fire them, put em in jail for gross violation of the # Data Protection Act (in UK anyway).   G Sadly, about as likely to happen as the proverbial deep freeze in hell.    regards    ------------------------------    Date: 18 Aug 2005 08:31:17 -0700 From: bob@instantwhip.com = Subject: Companies not on VMS get a taste of coming disaster! C Message-ID: <1124379077.685670.148850@g44g2000cwa.googlegroups.com>   < The zotob worm has proven that every ceo/cio not running vms should be fired immediately!    ) http://www.theinquirer.net/?article=25509    ------------------------------  % Date: Thu, 18 Aug 2005 08:44:57 +0200 ' From: JOUKJ <joukj@hrem.stm.tudelft.nl> # Subject: Re: DFG (Defrag) - OpenVMS < Message-ID: <ccbe1$43042e6b$82a1f19e$17214@news2.tudelft.nl>   david20@alpha2.mdx.ac.uk wrote: e > In article <ddvmu2$4r8$1@mailhub227.itcs.purdue.edu>, Chuck Aaron <caaron@ceris.purdue.edu> writes:  > K >>Can someone tell me what account and what parameter/value needs to be set I >>to prevent this from occurring when DFG runs to defrag one of my disks?  >>	 >>Thanks,  >>Chuck  >> >>N >>Begin file evaluation phase:                         17-AUG-2005 00:00:00.72 >>I >>   Candidates for defragmentation (based on the defragmentation level):  >>< >>%DFG-F-SYSSRVERR, call to system service SYS$EXPREG failed+ >>-SYSTEM-F-EXQUOTA, process quota exceeded  >>CHUCK> >  > sys$startup:dfg$startup.com & > Look in sys$startup:dfg$startup.com.# > You should find a section like :-  >  > " H > $!      The following logicals override the default quotas used by allM > $!      defragmentation processes on this system.  The values shown are the P > $!      minimim recommended.  In general, the quotas used are conservative andH > $!      may be increased without restriction (other than normal systemK > $!      restrictions).  DIGITAL does not recommend reducing these values. O > $!      Doing so may cause the defragmentation process to fail.  See the user F > $!      guide for the POLYCENTER File Optimizer for OpenVMS for moreP > $!      information about using these logicals. See Open VMS documentation forO > $!      more information about the effects of individual quotas on a process.  > $!M > $!      To use these logicals, increase the associated value, uncomment the . > $!      desired line, and execute this file. > $!1 > $!  CALL DEFINE_LOGICAL DFG$ASTLM           100 0 > $!  CALL DEFINE_LOGICAL DFG$BIOLM           183 > $!  CALL DEFINE_LOGICAL DFG$BYTLM           61440 0 > $!  CALL DEFINE_LOGICAL DFG$DIOLM           181 > $!  CALL DEFINE_LOGICAL DFG$ENQLM           500 0 > $!  CALL DEFINE_LOGICAL DFG$FILLM           50C > $!  CALL DEFINE_LOGICAL DFG$JTQUOTA         {uses system default}  > .  > .  > .  > "  > # > You probably need to increase the  >  > DFG$PGFLQUOTA  >  > and possibly >  > DFG$WSDEFAULT          > DFG$WSEXTENT           > DFG$WSQUOTA            >  >  >   At my side it was DFG$PGFLQUOTA.I I finally set it to 1500000 on advise of HP-support. Note that this also  G depends on the amount of page/swap space available and on the quota of  - the "user" running the actual DEFRAG process.     G Note that all changes to sys$startup:dfg$startup.com are lost when you   update DFG.                   Jouk    ------------------------------    Date: 18 Aug 2005 08:03:20 -07000 From: "Marcelo" <marcelo.favaro@chemtech.com.br>( Subject: Erro using OBNDRA from Fortran.B Message-ID: <1124377400.477682.46100@g49g2000cwa.googlegroups.com>  - Using OBNDRA in Fortran for output parameters   = How can I bind an output parameters from Pl/SQL using OBNDRA.  THis is may code.  CALL OBNDRA(CURS,':OUT1',5,   + %LOC(out_var), 20,1,-1,0,0, 0, + 0, 0, 0, -1, -1)  C OBNDRA does not return an erro, but when call OEXEC an exception is  create.    Any suggestion?    ------------------------------  % Date: Thu, 18 Aug 2005 08:35:54 -0500 ( From: Wayne Sewell <wayne@tachysoft.com>. Subject: Re: Help Needed: Tape Backup Save Set/ Message-ID: <00A48758.4F9175D9.1@tachysoft.com>   - >Message-ID: <4303801E.E6F42C07@teksavvy.com> & >Date: Wed, 17 Aug 2005 14:21:27 -0400. >From: JF Mezei <jfmezei.spamnot@teksavvy.com> >X-Newsgroups: comp.os.vms/ >Subject: Re: Help Needed: Tape Backup Save Set      >Wayne Sewell wrote:L >> "If you want to start processing at BOT, and the magnetic tape is alreadyR >> positioned beyond BOT, specify /REWIND. Otherwise, the magnetic tape begins (orB >> resumes) processing from the logical end-of-tape (EOT) marker." > G >On TK50s, (I used this because any difference in processing results in I >large difference in total time), it seemed that doing successive backups D > would result in the tape being rewound by the second invocation ofH >backup (I assume in the process of privately mounting the tape to checkG >its label etc) and then the TK50 would spend much time reading through H >to seek the EOT position because I had specified /NOREWIND. I know muchE >time was spent doing this because BACKUP was essentially iddle for a H >long time while the tape light was blinking away. and it was a very lon4 >time before backup started to do actual processing. > 2 >Is this a correct interpretation of what I saw ?   L I don't know.  Could be.  I never saw this behavior myself, but then I neverK tried to put multiple savesets on the same tK50.  Since the capacity of the H TK50 was so low, it was more like multiple tapes per saveset rather thanL multiple savesets per tape.  I usually did image backups, which would pretty much fill up the tapes.   5 But somebody else in the thread was talking about it.   K I don't think current drives do this rewind every time thing, because there O would be a cumulative slowdown.  Modern drives are much faster, but still...you K should be able to notice a difference if the tape is rewinding and scanning O forward every time.  My main image backup contains 25 disks and the ones at the N end start as quickly as those at the beginning.  I can easily keep up with theC progress of the savesets because of the tapesys broadcast messages.   I So this is just one more reason why the TK50s are obsolete.  Of course, I N especially hated the scsi version because of the horrendous whine it made when the tape was in motion.  :-)     > C >If one is to mount or allocate the tape before first invovation of I >BACKUP, do subsequent invocations still result in a implicity rewind and I >seek end-of-tape operation, or would BACKUP be able to see that the tape D >that is already mounted has the right label and is already at EOT ?    L backup can see the label, because it is in the volume control block.  That'sH where show device gets it from.  But I don't think backup can detect theG position on the tape.  BOT, sure, that shows up in the status.  But not  anyplace else.  H EOT is tricker.  There are two, the logical end-of-tape and the physicalO end-of-tape.  The former is the place where you stopped writing last and can be K anywhere on the tape.  It's just a code written on the tape.  The latter is 0 just what it says, the physical end of the tape.  M Or rather three EOT positions, because I seem to recall that the physical end O of tape actually has two hardware detectable markers.  The first one means that N you're almost to the end and you better start wrapping things up.  This allowsM backup to finish off the volume before hitting the absolute marker, which the $ drive won't allow you to write past.  J There is only one EOT bit in the device status, and it appears to mean theM first physical EOT.  Certainly after doing a backup, the EOT is not set, even N though the tape drive is sitting at logical EOT.  Therefore, I am not sure howJ backup would be able to determine the logical EOT on a new backup/norewind; command without performing i/o to the drive to hunt for it.   M I think what happens is that backup scans forward for the eot marker in every L case when /norewind is used.  Even if the BOT bit is set.  That tells it theJ current position of the tape on the drive, but it still doesn't know whereN logical EOT is.  It could be right after BOT (initialized tape), almost at theH end, or anywhere in between.  Needless to say, if the tape is already atL logical eot, which is the scenario you are asking about, the scan won't take long.    Wayne O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== P Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------    Date: 18 Aug 2005 07:42:34 -0500 From: briggs@encompasserve.orgC Subject: Re: How many files can you have in a VMS directory without 3 Message-ID: <1E$hHAQBfcUT@eisner.encompasserve.org>   [ In article <BF292AFB.12ACA%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes: K > On 8/17/05 5:34 PM, in article 4303D75D.E69402A3@teksavvy.com, "JF Mezei" ' > <jfmezei.spamnot@teksavvy.com> wrote:  >  >> FredK wrote: K >>> A modern file system design to replace ODS would use a b-tree structure  >>> instead of a linear list.  >>  G >> is INDEXF.SYS also a culprit in the "slow" files system for VMS ? or > >> just the simple sequential file nature of directory files ? > N > The problem is not with INDEXF.SYS, which is quite efficient. It is with theK > fact that the entries in the .DIR file are always sorted. If there was no I > care for sorting and reclamation of deleted space in the .DIR file then  > these issues would not arise.   C Instead you'd get a different set of issues.  File lookups would be & slow and directories would grow large. > 	 TANSTAAFL    	John Briggs   ------------------------------    Date: 18 Aug 2005 07:53:15 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: How many files can you have in a VMS directory without 3 Message-ID: <dYlqIrUVHVBe@eisner.encompasserve.org>   [ In article <BF292AFB.12ACA%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes:  > N > The problem is not with INDEXF.SYS, which is quite efficient. It is with theK > fact that the entries in the .DIR file are always sorted. If there was no I > care for sorting and reclamation of deleted space in the .DIR file then  > these issues would not arise.   C    RSX didn't sort them (or was that ODS-1).  Older versions of PIP H    would only /LI (PIP/LI is the equivalent of DIR) in the stored order.6    You could get freeware to produce a sorted listing.  G    I agree a b-tree would be better.  Maybe a simple keyed-indexed file C    (building on existing RMS capabilities) would be good enough.  I E    don't want to have to guess what file * will pick up when DCL$PATH C    is set (which is why I have a $.com in my first DCL$PATH entry).    ------------------------------    Date: 18 Aug 2005 08:09:36 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) C Subject: Re: How many files can you have in a VMS directory without 3 Message-ID: <H$JV4LzGsw5t@eisner.encompasserve.org>   [ In article <BF292368.12ABC%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes:  > H > Sure! There are many more image activations but when it comes to largeM > directories the rev_del is substantially faster, plus which would you rater 7 > have, lots of mapped page reads for image activation    J    Those are not likely to be hard page faults after the first invocation.F    DIRECTORY.EXE and it's shared images only take up about 2K pageletsC    on my Alpha, hardly likely to get bumped from the free page list F    between executions (especially since those shared images are almost+    certainly mapped by some other process).   B    As a matter of fact there are several instances of DIRECTORY inL    sys$startup:*.com, so it's probably paged in during boot and almost neverC    removed from memory on an interative system with even close to a     reasonable amonut of RAM.   ------------------------------    Date: 18 Aug 2005 09:42:06 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) C Subject: Re: How many files can you have in a VMS directory without 3 Message-ID: <1il+7q1SialS@eisner.encompasserve.org>   [ In article <BF29C963.12B1C%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes: J > On 8/17/05 6:20 PM, in article 4303E231.7D05A2C@teksavvy.com, "JF Mezei"' > <jfmezei.spamnot@teksavvy.com> wrote:  > I >> What was/were the reasons for not going for a more efficient directory  >> file structure ?  > N > The term "efficient directory file structure" is rather subjective. Yes thisJ > thread is describing one of the problems with this approach to directoryJ > structure, but there are other advantages. Likewise with other directoryN > structures there are advantages and disadvantages. There are trade offs with > every design.   C In partcular, the VMS on disk structure is designed to be resiliant C in the case of a system crash while disk metadata is being written.    ------------------------------    Date: 18 Aug 2005 09:48:56 -0700$ From: "AEF" <spamsink2001@yahoo.com>C Subject: Re: How many files can you have in a VMS directory without C Message-ID: <1124383736.566897.238890@g49g2000cwa.googlegroups.com>    Bob Koehler wrote:] > In article <BF292368.12ABC%roktsci@comcast.net>, Jeff Cameron <roktsci@comcast.net> writes:  > > J > > Sure! There are many more image activations but when it comes to largeO > > directories the rev_del is substantially faster, plus which would you rater 8 > > have, lots of mapped page reads for image activation > L >    Those are not likely to be hard page faults after the first invocation.H >    DIRECTORY.EXE and it's shared images only take up about 2K pageletsE >    on my Alpha, hardly likely to get bumped from the free page list H >    between executions (especially since those shared images are almost- >    certainly mapped by some other process).  > D >    As a matter of fact there are several instances of DIRECTORY inN >    sys$startup:*.com, so it's probably paged in during boot and almost neverE >    removed from memory on an interative system with even close to a  >    reasonable amonut of RAM.    @ Even better, it's an installed image. So it should already be in memory, no?    ------------------------------    Date: 18 Aug 2005 07:47:38 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) O Subject: Re: How many files can you have in a VMS directory without performance 3 Message-ID: <s6$qux18REVS@eisner.encompasserve.org>   Z In article <11g7cc2145st9ae@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes: > K > Actually, the practical answer is 20-22 files.  Any more and they scrool  J > off the screen when issuing the DIR command with one file per line.  :-)  I    I've always tried to keep it to one screen, but never required that to     be one per line.   >    Bu I don't thinkk the OP was worried about looking at them.   ------------------------------    Date: 18 Aug 2005 08:00:29 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) O Subject: Re: How many files can you have in a VMS directory without performance 3 Message-ID: <OWEvGmdCgJeb@eisner.encompasserve.org>   \ In article <4303E38E.BC700038@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > J > But what logic is used by f$parse to determine that [ and/or ] should beG > considered part of the filename and "escaped" or whether it points to B > the directory portion of the specicication entered by the user ?  D    [ ] are parsed as directory delimiters unless ^ is to escape them    when they are entered.   C    Other characters can be entered without the ^ and will be parsed B    according to appropriate rules, such as . within names, but are    displayed with ^:      $ create ^[.a    Exit     $ create [.a P    %DCL-W-DIRECT, invalid directory syntax - check brackets and other delimiters    \[.a\    $ create a.a.a     Exit 
    $dir .a     Directory USER1:[KOEHLER]       a^.a.a;1            ^[.a;1       Total of 2 files.   ------------------------------  % Date: Thu, 18 Aug 2005 05:13:07 -0700 ( From: Jeff Cameron <roktsci@comcast.net>Y Subject: Re: How many files can you have in a VMS directory without performance   problem 0 Message-ID: <BF29C963.12B1C%roktsci@comcast.net>  H On 8/17/05 6:20 PM, in article 4303E231.7D05A2C@teksavvy.com, "JF Mezei"% <jfmezei.spamnot@teksavvy.com> wrote:   H > What was/were the reasons for not going for a more efficient directory > file structure ?  L The term "efficient directory file structure" is rather subjective. Yes thisH thread is describing one of the problems with this approach to directoryH structure, but there are other advantages. Likewise with other directoryL structures there are advantages and disadvantages. There are trade offs withJ every design. Actually I think the MAC HFS and EHFS has the best directory structure of a catalog b-tree.   ------------------------------  % Date: Thu, 18 Aug 2005 09:08:46 -0600  From: Dan Notov <d9nn0@hp.com>& Subject: Re: HP 3rd quarter financials, Message-ID: <4304a481$1@usenet01.boi.hp.com>   JF Mezei wrote:  > Dan Notov wrote: > G >>Significant growth in ISS platforms. All units are profitable, except  >>software.  >  > $ > That was the other question I had: > F > Does any VMS software/application/compilers belong to the "Software"D > division, or is all the stuff a VMS customer would require from HP > sold/responsability of BCS ? > I > Also, if one looks at a product such as ALL-IN-1/Office Server which in H > "maintenance mode" in India, is that a responsability of Ann McQuaid ?L > Or is Ann McQuaid responsible only for the VMS operating system and SIPs ?C No, software includes mostly OpenView products. Part of the reason  G software has not be profitable is HP has acquired a number of software  G firms that were still in startup mode. Lot's of R&D, no sales to speak  ; of, etc. There are other reasons that need to be addressed.   G OpenVMS & it's layered products & applications sits firmly within BCS,   as does HP-UX, Tru64 UNIX, etc.    ------------------------------    Date: 17 Aug 2005 23:14:14 -0700 From: sinobato@gmail.com) Subject: Re: Investigating ACCVIO problem C Message-ID: <1124345654.180797.255740@g49g2000cwa.googlegroups.com>   	 Hi folks,   C thanks for replying to this query. I was able to get hold of a test ? server and tried to simulate the problem. As it turned out, the F parameter MAXPROCESSCNT was the culprit! The original value was aroundB 800 and after I did the autogen and had it rebooted, it went up toF 1204. This is when the problem started. I'm currently negotiating withF the users for this node for another outage so that we can decrease theD value of this parameter. I'm not just sure why in the first place it+ started to error out due to this parameter.   3 Anyway, thanks again for your help and suggestions!    Sino   ------------------------------  % Date: Thu, 18 Aug 2005 19:36:30 +0200 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk> Subject: RAM< Message-ID: <4304c71a$0$22986$edfadb0f@dread16.news.tele.dk>   I am an hardware ignorant.  2 Can memory be moved between any of theese systems:  	 PWS 433au  AS 800 (500 MHz) AS 1000A (400 MHz)   ?    Arne   ------------------------------  # Date: Thu, 18 Aug 2005 09:51:53 GMT ( From: Alan Greig <greigaln@netscape.net>0 Subject: Re: SAMBA for VMS (The saga continues!); Message-ID: <ZSYMe.2628$a87.1675@fe3.news.blueyonder.co.uk>    John Santos wrote:   >  > G > It has.  According to the web site, he no longer has access to a VAX, ' > so is no longer providing VAX .OLB's.   I There's always the option of simh, ts10 and Charon-VAX. Simh seems to be  E running reliably for me and will run under VMS (Alpha not sure about  + Itanium build yet), Unix/Linux and Windows.   F > I have a VAX but no CDROM on it.  I also have an Alpha with a CDROM C > drive that I planned to cluster with the VAX, but the CDrom drive  > recently broke. :-(    Again how about simh?    --  
 Alan Greig   ------------------------------   Date: 18 Aug 2005 12:12:18 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mjc92F1769jgU1@individual.net>  R In article <FD827B33AB0D9C4E92EACEEFEE2BA2FB6B1F4D@tayexc19.americas.cpqcorp.net>,* 	"Main, Kerry" <Kerry.Main@hp.com> writes: >  >> -----Original Message----- % >> From: bill@triangle.cs.uofs.edu=20  >>  A >> HP has no real interest in academia.  I've been down the road.  > I > Reminds me of all those in 1988 who stated that there was absolutely no I > way that anything but WordPerfect would ever be the std word processing J > pkg - especially in the Govt. If you were to suggest that something elseG > might come along, those "experienced techies and analysts" would have : > smiled knowingly and thought "he just doesn't get it .." >  > Things change.  ( So, finally someone willing to admit it.   > J > Heck, 5 years ago, Linux was hardly anything but a lab experiment in theF > back labs. 7 Years ago it was not even on analysts radar as an OS to
 > look at. >  > Things change.  @ How true.  VMS, once the darling of academia, now irrelevant.  I? can remember when you couldn't find a CS department that didn't C have VMS running on a VAX.  When, as a contractor, bidding anything C against a VAX running VMS was a sure lose on an RFP. (Need I remind C everyone of the incident I reported here in the past where I sat in D a bidders conference and heard the head of the procurement committeeE at a college state catagorically, "I don't care which system wins the 2 procurement as long as it says VAX on the front.")  A But as you say, "Things change".  Not necessarily for the better.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Thu, 18 Aug 2005 08:34:44 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> 0 Subject: RE: SAMBA for VMS (The saga continues!)R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB6B1F5C@tayexc19.americas.cpqcorp.net>   > -----Original Message-----$ > From: bill@triangle.cs.uofs.edu=20A > [mailto:bill@triangle.cs.uofs.edu] On Behalf Of Bill Gunshannon  > Sent: August 18, 2005 8:12 AM  > To: Info-VAX@Mvb.Saic.Com 2 > Subject: Re: SAMBA for VMS (The saga continues!) >=20 > In article=20 @ > <FD827B33AB0D9C4E92EACEEFEE2BA2FB6B1F4D@tayexc19.americas.cpqc > orp.net>, , > 	"Main, Kerry" <Kerry.Main@hp.com> writes: > >=20 > >> -----Original Message----- ) > >> From: bill@triangle.cs.uofs.edu=3D20  > >>=20 C > >> HP has no real interest in academia.  I've been down the road.  > >=20@ > > Reminds me of all those in 1988 who stated that there was=20 > absolutely no > > > way that anything but WordPerfect would ever be the std=20 > word processing @ > > pkg - especially in the Govt. If you were to suggest that=20 > something elseA > > might come along, those "experienced techies and analysts"=20  > would have< > > smiled knowingly and thought "he just doesn't get it .." > >=20 > > Things change. >=20* > So, finally someone willing to admit it. >=20   [snip..]  G My main point in this response was to point out that as much as Windows G "good enough" functionality and features has become popular today, that > in no way means it will have the same level of interest and/or deployment in 5-7 years.   As just a few examples:   D - the security / virus /trojan issues are becoming much more visibleF these days as companies are finding that they can not keep up with theE testing and certifying of the recommended monthly patches before they 6 are rolled into production. [same goes for Linux btw].  F - app stacking is becoming a very popular approach in consolidation asF it not only reduces HW costs, but also OS + Mgmt costs. Unfortunately,B App stacking is not something you see much of in the Windows/LinuxH world. Rather you see OS stacking (VMware etc), which does not reduce OS8 costs that are directly related to FTE (staffing) costs.  G My personal view is that OS platforms popularity have a way of changing C over the years. IBM was the biggie with mainframe stuff in 60/70's. F OpenVMS was the biggie in the 80's/early 90's. Solaris/Windows was the? biggie in late 90's/early 2000's. Linux is the buzz word today.    It keeps changing.  H With more Customers moving big time back to much more centralized models> of computing, app stacking, workload management, HA (includingF multi-site with SOX compliance etc), who knows - perhaps a new (or old" becomes new) platform will emerge?   :-)    Interesting times ..  
 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.   =20    ------------------------------   Date: 18 Aug 2005 12:43:07 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mje2rF165n5eU1@individual.net>  @ I hate to be so critical, but this is really getting ridiculous.   First the unpack didn't work.  Then the build didn't work.  Now the install doesn't work.   D And none of these problems has anythng to do with my being on a VAX.D I can't see how any of this stuff worked on an Aplha or IA64 either.  E Considering how hard it is to get anything to work that is supposedly D targeted at VMS I can easily see why no one is bothering with trying! to port Open Source stuff to VMS.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 18 Aug 2005 12:58:06 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mjeuuF165n5eU2@individual.net>  , In article <3mje2rF165n5eU1@individual.net>,+ 	bill@cs.uofs.edu (Bill Gunshannon) writes:  >  > Now the install doesn't work.  >   C I don't have a clue how to fix this.  I also don't see how it could  work on anything.    From the install: K    Enter DEVICE:[DIRECTORY] for SAMBA_ROOT [SYS$COMMON:[UTILITIES.SAMBA]]]:   H You can see from this that my SAMBA_ROOT is SYS$COMMON:[UTILITIES.SAMBA]I The install procedure accepted it and it does meet the DEVICE:[DIRECTORY]  requirement.  > But all further references in the INSTALL.COM are of the form:  ) $       create/directory SAMBA_ROOT:[BIN] ) $       create/directory SAMBA_ROOT:[LIB] 3 $       create/directory SAMBA_ROOT:[LIB.CODEPAGES] - $       create/directory SAMBA_ROOT:[private] ) $       create/directory SAMBA_ROOT:[tmp] ) $       create/directory SAMBA_ROOT:[VAR] / $       create/directory SAMBA_ROOT:[VAR.LOCKS]    How is this possible?   E That would make them something like SYS$COMMON:[UTILITIES.SAMBA][BIN]   J which, as expected, returns:   -RMS-F-SYN, file specification syntax error  F It seesm to me that there is no way this INSTALL.COM could work on any system.    Any suggestions?   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 18 Aug 2005 13:14:56 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mjfugF17mkj8U1@individual.net>  , In article <3mjeuuF165n5eU2@individual.net>,+ 	bill@cs.uofs.edu (Bill Gunshannon) writes: . > In article <3mje2rF165n5eU1@individual.net>,- > 	bill@cs.uofs.edu (Bill Gunshannon) writes:  >>    >> Now the install doesn't work. >>   > E > I don't have a clue how to fix this.  I also don't see how it could  > work on anything.  >  > From the install: M >    Enter DEVICE:[DIRECTORY] for SAMBA_ROOT [SYS$COMMON:[UTILITIES.SAMBA]]]:  > J > You can see from this that my SAMBA_ROOT is SYS$COMMON:[UTILITIES.SAMBA]K > The install procedure accepted it and it does meet the DEVICE:[DIRECTORY]  > requirement. > @ > But all further references in the INSTALL.COM are of the form: > + > $       create/directory SAMBA_ROOT:[BIN] + > $       create/directory SAMBA_ROOT:[LIB] 5 > $       create/directory SAMBA_ROOT:[LIB.CODEPAGES] / > $       create/directory SAMBA_ROOT:[private] + > $       create/directory SAMBA_ROOT:[tmp] + > $       create/directory SAMBA_ROOT:[VAR] 1 > $       create/directory SAMBA_ROOT:[VAR.LOCKS]  >  > How is this possible?  > G > That would make them something like SYS$COMMON:[UTILITIES.SAMBA][BIN]  > L > which, as expected, returns:   -RMS-F-SYN, file specification syntax error   Ooops.  Actually it makes it: 1                SYS$COMMON:[UTILITIES.SAMBA]:[BIN]    Which returns:    Q %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters \:\    But the result is the same.    > H > It seesm to me that there is no way this INSTALL.COM could work on any	 > system.  >  > Any suggestions? >    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Thu, 18 Aug 2005 09:15:52 -0400  From: norm.raphael@metso.com0 Subject: Re: SAMBA for VMS (The saga continues!)Q Message-ID: <OFA46270F7.1BC2F278-ON85257061.0048A066-85257061.0048DD17@metso.com>    SAMBA aside...  : bill@triangle.cs.uofs.edu wrote on 08/18/2005 08:58:06 AM:  . > In article <3mje2rF165n5eU1@individual.net>,/ >    bill@cs.uofs.edu (Bill Gunshannon) writes:  > > ! > > Now the install doesn't work.  > >  > E > I don't have a clue how to fix this.  I also don't see how it could  > work on anything.  >  > From the install: , >    Enter DEVICE:[DIRECTORY] for SAMBA_ROOT  [SYS$COMMON:[UTILITIES.SAMBA]]]:  I I'd conjecture this is a rooted logical-name assignment and so should be/ 	 have been    SYS$COMMON:[UTILITIES.SAMBA.]    > J > You can see from this that my SAMBA_ROOT is SYS$COMMON:[UTILITIES.SAMBA]K > The install procedure accepted it and it does meet the DEVICE:[DIRECTORY]  > requirement. > @ > But all further references in the INSTALL.COM are of the form: > + > $       create/directory SAMBA_ROOT:[BIN] + > $       create/directory SAMBA_ROOT:[LIB] 5 > $       create/directory SAMBA_ROOT:[LIB.CODEPAGES] / > $       create/directory SAMBA_ROOT:[private] + > $       create/directory SAMBA_ROOT:[tmp] + > $       create/directory SAMBA_ROOT:[VAR] 1 > $       create/directory SAMBA_ROOT:[VAR.LOCKS]  >  > How is this possible?  > G > That would make them something like SYS$COMMON:[UTILITIES.SAMBA][BIN]   H Actually should become something like SYS$COMMON:[UTILITIES.SAMBA.][BIN]  ( which oddly enough IIRC is valid syntax.   > F > which, as expected, returns:   -RMS-F-SYN, file specification syntax error  > H > It seesm to me that there is no way this INSTALL.COM could work on any	 > system.  >  > Any suggestions? >  > bill >  > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three  wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------   Date: 18 Aug 2005 13:39:41 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mjhctF17cjn9U1@individual.net>  Q In article <OFA46270F7.1BC2F278-ON85257061.0048A066-85257061.0048DD17@metso.com>,  	norm.raphael@metso.com writes:  > SAMBA aside... > < > bill@triangle.cs.uofs.edu wrote on 08/18/2005 08:58:06 AM: > / >> In article <3mje2rF165n5eU1@individual.net>, 0 >>    bill@cs.uofs.edu (Bill Gunshannon) writes: >> >" >> > Now the install doesn't work. >> > >>F >> I don't have a clue how to fix this.  I also don't see how it could >> work on anything. >> >> From the install:- >>    Enter DEVICE:[DIRECTORY] for SAMBA_ROOT " > [SYS$COMMON:[UTILITIES.SAMBA]]]: > K > I'd conjecture this is a rooted logical-name assignment and so should be/  > have been  >  > SYS$COMMON:[UTILITIES.SAMBA.]  >  >>K >> You can see from this that my SAMBA_ROOT is SYS$COMMON:[UTILITIES.SAMBA] L >> The install procedure accepted it and it does meet the DEVICE:[DIRECTORY] >> requirement.  >>A >> But all further references in the INSTALL.COM are of the form:  >>, >> $       create/directory SAMBA_ROOT:[BIN], >> $       create/directory SAMBA_ROOT:[LIB]6 >> $       create/directory SAMBA_ROOT:[LIB.CODEPAGES]0 >> $       create/directory SAMBA_ROOT:[private], >> $       create/directory SAMBA_ROOT:[tmp], >> $       create/directory SAMBA_ROOT:[VAR]2 >> $       create/directory SAMBA_ROOT:[VAR.LOCKS] >> >> How is this possible? >>H >> That would make them something like SYS$COMMON:[UTILITIES.SAMBA][BIN] > J > Actually should become something like SYS$COMMON:[UTILITIES.SAMBA.][BIN] > * > which oddly enough IIRC is valid syntax.  - Nope.  I tried both possible interpretations.   0 $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin]M %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters   \:\ $ 0 $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin] P %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory file not creat edK -RMS-F-DEV, error in device name or inappropriate device type for operation  $    :-(    bill     --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Thu, 18 Aug 2005 13:50:28 +0000 - From: David B Sneddon <dbsneddon@bigpond.com> 0 Subject: Re: SAMBA for VMS (The saga continues!)* Message-ID: <43049224.9060500@bigpond.com>  % Bill Gunshannon was overheard to say:  >  > / > Nope.  I tried both possible interpretations.  > 2 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin]O > %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters  >  \:\ > $ 2 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin] R > %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory file not creat > edM > -RMS-F-DEV, error in device name or inappropriate device type for operation  > $  >  > :-(  >  > bill   >   @ That's because SYS$COMMON itself is a rooted logical and you can only have ONE of those...    Regards, Dave.  --  D David B Sneddon (dbs)  VMS Systems Programmer  dbsneddon@bigpond.comD Sneddo's quick guide ...     http://www.users.bigpond.com/dbsneddon/D DBS freeware     http://www.users.bigpond.com/dbsneddon/software.htm   ------------------------------  % Date: Thu, 18 Aug 2005 09:59:46 -0400  From: norm.raphael@metso.com0 Subject: Re: SAMBA for VMS (The saga continues!)Q Message-ID: <OFBB301967.46A28388-ON85257061.004CA9A0-85257061.004CE253@metso.com>   : bill@triangle.cs.uofs.edu wrote on 08/18/2005 09:39:41 AM:  ? > In article <OFA46270F7.1BC2F278-ON85257061.0048A066-85257061.  > 0048DD17@metso.com>,# >    norm.raphael@metso.com writes:  > > SAMBA aside... > > > > > bill@triangle.cs.uofs.edu wrote on 08/18/2005 08:58:06 AM: > > 1 > >> In article <3mje2rF165n5eU1@individual.net>, 2 > >>    bill@cs.uofs.edu (Bill Gunshannon) writes: > >> >$ > >> > Now the install doesn't work. > >> > > >>H > >> I don't have a clue how to fix this.  I also don't see how it could > >> work on anything. > >> > >> From the install:/ > >>    Enter DEVICE:[DIRECTORY] for SAMBA_ROOT $ > > [SYS$COMMON:[UTILITIES.SAMBA]]]: > > I > > I'd conjecture this is a rooted logical-name assignment and so should  be/ 
 > > have been  > > ! > > SYS$COMMON:[UTILITIES.SAMBA.]  > >  > >>0 > >> You can see from this that my SAMBA_ROOT is SYS$COMMON:[UTILITIES.SAMBA]; > >> The install procedure accepted it and it does meet the  DEVICE:[DIRECTORY] > >> requirement.  > >>C > >> But all further references in the INSTALL.COM are of the form:  > >>. > >> $       create/directory SAMBA_ROOT:[BIN]. > >> $       create/directory SAMBA_ROOT:[LIB]8 > >> $       create/directory SAMBA_ROOT:[LIB.CODEPAGES]2 > >> $       create/directory SAMBA_ROOT:[private]. > >> $       create/directory SAMBA_ROOT:[tmp]. > >> $       create/directory SAMBA_ROOT:[VAR]4 > >> $       create/directory SAMBA_ROOT:[VAR.LOCKS] > >> > >> How is this possible? > >>J > >> That would make them something like SYS$COMMON:[UTILITIES.SAMBA][BIN] > > ) > > Actually should become something like " SYS$COMMON:[UTILITIES.SAMBA.][BIN] > > , > > which oddly enough IIRC is valid syntax. > / > Nope.  I tried both possible interpretations.  > 2 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin]D > %DCL-W-PARMDEL, invalid parameter delimiter - check use of special
 characters >  \:\ > $ 1 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin] C > %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory  > file not creat > edC > -RMS-F-DEV, error in device name or inappropriate device type for 	 operation  > $  >  > :-(    Did you try   1 $DEFINE SAMBA_ROOT: SYS$COMMON:[UTILITIES.SAMBA.]   ) $       create/directory SAMBA_ROOT:[BIN]  $   6 which is more like what you described to be happening?  
 <wry grin>   >  > bill >  > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three  wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  # Date: Thu, 18 Aug 2005 13:54:52 GMT + From: Ken Robinson <sendspamhere@rbnsn.com> 0 Subject: Re: SAMBA for VMS (The saga continues!)B Message-ID: <1124373292.345624d4c6813de07f16b04e081ca85c@teranews>  + bill@cs.uofs.edu (Bill Gunshannon) wrote in / news:3mjhctF17cjn9U1@individual.net (in part):     >>  ( >> Actually should become something like& >> SYS$COMMON:[UTILITIES.SAMBA.][BIN]  >>  + >> which oddly enough IIRC is valid syntax.  > / > Nope.  I tried both possible interpretations.  > 2 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin]D > %DCL-W-PARMDEL, invalid parameter delimiter - check use of special
 > characters   >  \:\  ) That was never suggested as a possibility    > $ 2 > $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin] H > %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory file > not creat edC > -RMS-F-DEV, error in device name or inappropriate device type for  > operation $  >   K Unfortunately, sys$common is already a rooted logical and can't be used in  L another rooted logical. If you do a show logical on sys$common and see what K it translates to, you can then use those for your definition of samba_root.   A For example, on the decuserve system, sys$common translates into     $ sho log sys$commonD    "SYS$COMMON" = "EISNER$DRA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)  , So using this as an example, you would enter  / Your$diskhere:[sys0.syscommon.utilities.samba.]   E to the question about samba_root. After that, things should progress  	 smoothly.    Ken Robinson kenrbnsn (at) rbnsn (dot) com ! Out of work VMS system manager...    ------------------------------   Date: 18 Aug 2005 14:35:48 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: SAMBA for VMS (The saga continues!), Message-ID: <3mjkm4F17hghoU1@individual.net>  B In article <1124373292.345624d4c6813de07f16b04e081ca85c@teranews>,. 	Ken Robinson <sendspamhere@rbnsn.com> writes:- > bill@cs.uofs.edu (Bill Gunshannon) wrote in 1 > news:3mjhctF17cjn9U1@individual.net (in part):   >  >>> ) >>> Actually should become something like ' >>> SYS$COMMON:[UTILITIES.SAMBA.][BIN]   >>> , >>> which oddly enough IIRC is valid syntax. >>  0 >> Nope.  I tried both possible interpretations. >>  3 >> $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin] E >> %DCL-W-PARMDEL, invalid parameter delimiter - check use of special  >> characters  >>  \:\  > + > That was never suggested as a possibility  >  >> $  3 >> $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin]  I >> %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory file  >> not creat ed D >> -RMS-F-DEV, error in device name or inappropriate device type for >> operation $   >>   > M > Unfortunately, sys$common is already a rooted logical and can't be used in  N > another rooted logical. If you do a show logical on sys$common and see what M > it translates to, you can then use those for your definition of samba_root.  > C > For example, on the decuserve system, sys$common translates into   >  > $ sho log sys$commonF >    "SYS$COMMON" = "EISNER$DRA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) > . > So using this as an example, you would enter > 1 > Your$diskhere:[sys0.syscommon.utilities.samba.]  > G > to the question about samba_root. After that, things should progress   > smoothly.  >    Thank you.  I'll try that.   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------    Date: 18 Aug 2005 09:40:23 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) 0 Subject: Re: SAMBA for VMS (The saga continues!)3 Message-ID: <rxrmp1otYlu+@eisner.encompasserve.org>   W In article <3mje2rF165n5eU1@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: B > I hate to be so critical, but this is really getting ridiculous. >  > First the unpack didn't work.  > Then the build didn't work.  > Now the install doesn't work.  > F > And none of these problems has anythng to do with my being on a VAX.F > I can't see how any of this stuff worked on an Aplha or IA64 either. > G > Considering how hard it is to get anything to work that is supposedly F > targeted at VMS I can easily see why no one is bothering with trying# > to port Open Source stuff to VMS.   C Rather, I would say that those who _are_ trying to port Open Source @ stuff to VMS are not very successful at it.  You should not haveD to build Samba in order to use Samba.  Imagine if that were the case. with automobiles.  Well it was, back in 1890 !   ------------------------------  % Date: Thu, 18 Aug 2005 11:28:10 -0400  From: norm.raphael@metso.com0 Subject: Re: SAMBA for VMS (The saga continues!)Q Message-ID: <OF2406C69F.65DAFA53-ON85257061.005478EA-85257061.0054FA33@metso.com>   : bill@triangle.cs.uofs.edu wrote on 08/18/2005 10:35:48 AM:  D > In article <1124373292.345624d4c6813de07f16b04e081ca85c@teranews>,2 >    Ken Robinson <sendspamhere@rbnsn.com> writes:/ > > bill@cs.uofs.edu (Bill Gunshannon) wrote in 2 > > news:3mjhctF17cjn9U1@individual.net (in part): > >  > >>> + > >>> Actually should become something like ( > >>> SYS$COMMON:[UTILITIES.SAMBA.][BIN] > >>> . > >>> which oddly enough IIRC is valid syntax. > >>2 > >> Nope.  I tried both possible interpretations. > >>5 > >> $ create/dir SYS$COMMON:[UTILITIES.SAMBA.]:[bin] G > >> %DCL-W-PARMDEL, invalid parameter delimiter - check use of special  > >> characters 	 > >>  \:\  > > - > > That was never suggested as a possibility  > >  > >> $4 > >> $ create/dir SYS$COMMON:[UTILITIES.SAMBA.][bin]K > >> %CREATE-E-DIRNOTCRE, SYS$COMMON:[UTILITIES.SAMBA.][BIN] directory file  > >> not creat ed F > >> -RMS-F-DEV, error in device name or inappropriate device type for > >> operation $ > >> > > K > > Unfortunately, sys$common is already a rooted logical and can't be used  inI > > another rooted logical. If you do a show logical on sys$common andsee  whatC > > it translates to, you can then use those for your definition of  samba_root.  > > D > > For example, on the decuserve system, sys$common translates into > >  > > $ sho log sys$commonH > >    "SYS$COMMON" = "EISNER$DRA0:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE) > > 0 > > So using this as an example, you would enter > > 3 > > Your$diskhere:[sys0.syscommon.utilities.samba.]  > > H > > to the question about samba_root. After that, things should progress
 > > smoothly.  > >  >  > Thank you.  I'll try that. >    Sorry, Ken is correct.  
 On my system:   * $ dir sys$sysdevice:[000000]vms$common/fil    Directory SYS$SYSDEVICE:[000000]  A VMS$COMMON.DIR;1     (15,1,0)                      4  30-MAR-1999  14:43:04.48    Total of 1 file, 4 blocks.  D Notice that the file_id for these two is identical, meaning they are the same directory.   K So actually sys$sysdevice:[vms$common.] will work on a cluster_common disk, % but I don't necessarily recommend it.     + $ dir sys$sysroot:[000000]syscommon.dir/fil    Directory SYS$SYSROOT:[000000]  A SYSCOMMON.DIR;1      (15,1,0)                      4  30-MAR-1999  14:43:04.48    Total of 1 file, 4 blocks. $ sho log sys$sysroot 6    "SYS$SYSROOT" = "DSA150:[SYS1.]" (LNM$SYSTEM_TABLE)         = "SYS$COMMON:" ? 1  "SYS$COMMON" = "DSA150:[SYS1.SYSCOMMON.]" (LNM$SYSTEM_TABLE)    > bill >  > --E > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three  wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  # Date: Thu, 18 Aug 2005 09:30:34 GMT ( From: Alan Greig <greigaln@netscape.net>4 Subject: Simh terminal lines and networking with VMS< Message-ID: <_yYMe.20100$0u2.7892@fe2.news.blueyonder.co.uk>  H Is annyone using simh with physical terminal devices mapped to incoming I telnet on the host OS? If so do you have reliable emulated modem control  G to ensure drop of sessions on network problems? Simh emulates both the  G dzv11 (tt) and dhq11 (tx) both with optional emulated modem control so  H that VMS can both signal a hangup (drop incoming telnet) and respond to  a telnet disconnect.  G Now I want to be able to telnet into the emulated VAX from the outside  I world so that's why I need reliable hangup. It might only be an emulated  E system but I'd rather not have some random user telnet in and grab a  / setprv session which had dropped on me earlier.   G Now I think I have this working with the dzv11 emulation but the dhq11  G emulation doesn't seem to signal a carrier drop and the next telnet in  F grabs the previous session. As there seem to be a few quirks with the H dzv11 emulation I'd rather use the dhq11 emultion so has anyone figured I out how to make this work reliably? Note I am setting /perm/modem/hangup  J and using the -am flags with dz and the modem and hangup commands with vh.  H Also is anyone running simh with ethernet support? Seems I really would D need a second ethernet card to do this but if it works reliably its E probably worth the effort and would give me much more flexibility in   handling incoming telnet.  --  
 Alan Greig   ------------------------------    Date: 18 Aug 2005 08:35:38 -0700/ From: "Dr Tim" <tim.llewellyn@blueyonder.co.uk> 8 Subject: Re: Simh terminal lines and networking with VMSC Message-ID: <1124379338.448463.132960@f14g2000cwb.googlegroups.com>   B I've had a cluster running under simh, so the network support does work.   F It's been a while though, and I'm not in front of the system right now to look up details.    regards    ------------------------------  # Date: Thu, 18 Aug 2005 09:43:03 GMT ( From: Alan Greig <greigaln@netscape.net> Subject: Re: Squid for VMS= Message-ID: <HKYMe.14322$Wq4.11699@fe1.news.blueyonder.co.uk>    David J Dachtera wrote:    > Volker Englisch wrote: >  >>Hi,  >>L >>I'm wondering if there is something like squid for OpenVMS? There seems toL >>be no port of squid to this OS. Is there maybe another http-proxy software >>for OpenVMS? >  > % > Standard question: What is "squid"?  > F > UN*X-land programs are not guaranteed to be familiar or known to theI > OpenVMS crowd. Please describe what the program does so that a parallel B > facility, if any, on VMS can be cited as a possible replacement.  B That's a description more specific than "http-proxy software"? :-)     --  
 Alan Greig   ------------------------------    Date: 18 Aug 2005 08:13:44 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: Squid for VMS3 Message-ID: <O2VlP0BidqFr@eisner.encompasserve.org>   ` In article <4303DED5.194ED82F@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes: > % > Standard question: What is "squid"?  >   %    Friend of "sponge" and "starfish".    ------------------------------    Date: 18 Aug 2005 08:12:12 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: SYSMAN vs SYSGEN 3 Message-ID: <Ccv31fcTArp3@eisner.encompasserve.org>   \ In article <4303D6E7.3725D9BD@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > H > Thanks. So if I understand correctly, everytime you export an Alpha orF > IA64 thing running VMS to another country, you send ICBMs with it...  @    It also comes with the CIA.  Now you know how VMS has so much    built in security.    ------------------------------    Date: 18 Aug 2005 05:28:22 -0700 From: anguel@web.de  Subject: VMS as a SMTP client C Message-ID: <1124368102.101727.128010@g47g2000cwa.googlegroups.com>   ? Is there a tutorial on how to get VMS to exchanging mail with a D provider using a modem? Say dialing out, sending outbound mail usingF SMTP-Auth, retrieving inbound mail using POP3, hanging up. I'm sure itD somehow can work. My machine is a Alpha running OpenVMS 7.3 and UCX. Thanks for every hint.   ------------------------------    Date: 18 Aug 2005 08:50:29 -0700 From: bob@instantwhip.com 4 Subject: Zotob worm shows VMS notebooks needed ASAP!C Message-ID: <1124380229.557714.263270@g43g2000cwa.googlegroups.com>   $ can you still buy tadpoles anywhere?   ------------------------------    Date: 18 Aug 2005 08:53:28 -0700 From: bob@instantwhip.com 8 Subject: Re: Zotob worm shows VMS notebooks needed ASAP!C Message-ID: <1124380408.057613.255000@g43g2000cwa.googlegroups.com>   - why isn't Intel making a 1P itanium notebook? ' anyone at HP care to answer why you are ) missing out on a potentially huge market?    ------------------------------    Date: 18 Aug 2005 10:04:34 -0700 From: icerq4a@spray.se8 Subject: Re: Zotob worm shows VMS notebooks needed ASAP!C Message-ID: <1124384674.470233.232040@z14g2000cwz.googlegroups.com>   C Intel haven't done any notebook IA64 CPU so that is pretty obvious. F Although if they wanted they could fairly easy make a 90nm Itanium CPU? for notebook. A Montecito core at 1.6GHz consume about 30 Watt.    ------------------------------   End of INFO-VAX 2005.460 ************************