1 INFO-VAX	Thu, 13 Jul 2000	Volume 2000 : Issue 388       Contents:+ RE: %DCL-W-USGOTO, target of GOTO not found 0 ANNOUNCING: FreeCiv 1.11.0 port for OpenVMS Axp. Re: Apache for Open VMS  Re: Apache for Open VMS 
 Boot Block Re: Building TK50's % Re: DB connectivity via a web browser . Re: Default protection for logfiles (VMS 7.1)./ Re: RE: Direct OPCOM messages to e-mail account  disable spawn in VMSMail? & Re: DSSI shadow problem on VAX VMS 7.2 duplicate file names Re: duplicate file names Re: duplicate file names Re: duplicate file names Re: duplicate file names Re: Editor Commands  Find Files utility Re: FTP to/from Alpha boxes  Re: Hobbyist TCP IP licenses ?& Re: How to disable DecWindows for OPA0& Re: How to disable DecWindows for OPA0 ibm 18 gig drives  Re: ibm 18 gig drives ' Re: Mac-Decnet via Webster Multiport LT  Re: mime Re: mime Re: mime versions  Re: mime versions $ Re: MIN BOOT problem - openVMS 5.5-2) Re: Minimum Page/Swap File Size in Blocks ) Re: Minimum Page/Swap File Size in Blocks ) Re: Minimum Page/Swap File Size in Blocks ) Re: Minimum Page/Swap File Size in Blocks ) Re: Minimum Page/Swap File Size in Blocks ) Re: MX 4.2 won't rebuild, what's missing? ) Re: MX 4.2 won't rebuild, what's missing?  Re: MX Records( Re: Netscape Fasttrack for OpenVMS 7.2-1G OpenVMS 7.2 backup bug? (was RE: Open-source Database system available) K Re: OpenVMS 7.2 backup bug? (was RE: Open-source Database system available) & OVMS V7.2-1: Passwords Case-Sensitive?* Re: OVMS V7.2-1: Passwords Case-Sensitive?* Re: OVMS V7.2-1: Passwords Case-Sensitive?* Re: OVMS V7.2-1: Passwords Case-Sensitive? Re: ppp dialup on VAX again ' Re: TCPIP remote node in audit security % template device cannot be allocated - ) Re: template device cannot be allocated - ! Re: VAX to DEC Cobol differences.  VMS tuning wsdefaultH What graphics cards are supported by OpenVMS on a AlphaServer 400 4/233? Re: WTB: Microvax2000  Re: WTB: Microvax2000   F ----------------------------------------------------------------------  % Date: Wed, 12 Jul 2000 15:13:30 -0300 1 From: "Boyle, Darren" <boyledj@bankofbermuda.com> 4 Subject: RE: %DCL-W-USGOTO, target of GOTO not foundK Message-ID: <9F664D538536D411BD3200508B6FF01A333678@bdant027.bda.bobda.com>   4 > From: 	Lorin Ricker[SMTP:Lorin.Ricker@t-netix.com] > 
 > My standard H > debugging advice is to comment out whole big swaths of DCL statements,H > focusing on any recent areas of change (and it helps to have a "smart"D > text editor for this), and test-uncomment-test until the offending > statement(s)1 > make themselves known... tedious, but it works.  > L Personally I move the offending label up in chunks, just moving the one lineJ is simpler than commenting out 100 lines then removing the comments again.  I > I've often wished that the -W-USGOTO condition was actually a -E- level E > conditions, which would make trapping it with an ON ERROR condition F > handler possible (I've never had much use for ON WARNING, since thatI > generates too many spurious conditions to worry about).  OTOH, it might G > be nice to extend DCL's ON-handlers to be multi-level, so one *could*  > establish things like: > * >   $ ON WARNING THEN GOTO Warning_Handler& >   $ ON ERROR THEN GOTO Error_Handler& >   $ ON FATAL THEN GOTO Fatal_Handler > L You already can, you just explained it, an error would take the control to aK different place than the fatal error as you have described above.  Although K overlooking on BIG point here, the label would not be found if it is placed $ after the offending (missing) ENDIF.    C > (or am I missing something obvious, equivalent or better, handler  > style-wise?).  > J > Being able to actually handler-*trap* the -USGOTO condition is practicalL > for more than just syntax reasons... consider the case of parameter-driven > "computed-by GOTOs" :  > 
 >    $ ... >    $ GOTO Option_'P1' 
 >    $ ... >  >    $Option_FOO: 
 >    $ ... >  >    $Option_BAR: 
 >    $ ... > 
 >    $ (etc.)  > 0 What about (yes I know it's messy but effective)  , $ IF OPTION .EQS. "FOO" THEN GOTO OPTION_FOO, $ IF OPTION .EQS. "BAR" THEN GOTO OPTION_BAR> $ WRITE SYS$OUTPUT "Option ''P1' not found, procedure exiting"    K > The intent here is for the com-file user to be able to invoke it as, say:  > 7 >    $ @comfile FOO         or           $ @comfile BAR  >  > ...but the invocation  >  >    $ @comfile GLORP  > G > would permit the -USGOTO condition to trap gracefully (presuming that , > the label "$Option_GLORP:" doesn't exist). > H > Just some thoughts on my all-time favorite scripting/command language. > 	 Mine Too.  - Darren  	 > regards  > B > Lorin Ricker                            Lorin.Ricker@T-NETIX.com > Director, JMS 7 > T-NETIX, Inc.                           (303)705-5575  > 67 Inverness Drive East : > Englewood, Colorado 80112      http://www.LockTrack.com/ >  >     F **********************************************************************C This message and any files transmitted with it are confidential and J may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom they L are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copying  of this message is prohibited.   Bank of Bermuda F **********************************************************************   ------------------------------  # Date: Wed, 12 Jul 2000 21:55:01 GMT * From: Roger Tucker <roger.tucker@wcom.com>9 Subject: ANNOUNCING: FreeCiv 1.11.0 port for OpenVMS Axp. ( Message-ID: <396C953C.756DE813@wcom.com>  / Announcing FreeCiv 1.11.0 port for OpenVMS AXP.   ? (Freeciv is a multiplayer strategy game, released under the GNU 9  General Public License.  It is generally comparable with *  Civilization II, published by Microprose.  See http://www.freeciv.org/)   7 My updates to FreeCiv for the port to OpenVMS have been : added to the freeciv CVS latest development release and is% available in the latest CVS snapshot.   : Also the latest stable release 1.11.0 (although it doesn't; include my changes) does compile and run correctly with the  changes in the latest snapshot.   < You will need to get down the latest CVS snapshot to get the: three files needed ([.vms]readme.txt, [.vms]vms_build.com, and [.server]sernet.c)  : Thanks go to the freeciv team for such a good game, and to9 Colin Blake for the port of Mozilla.  If anyone want's to / take up where I left off, they are welcome too.   7 The following information is from the [.vms]readme.txt:    ------------------------- G This document includes instructions on how to build Freeciv for OpenVMS ; Alpha.  I used Compaq C V6.2-003 on OpenVMS Alpha V7.2, but 9 other versions of the C compiler and OpenVMS should work.   8 1.  Make sure TCP/IP is installed correctly and running.  , 2.  Download and install the latest Mozilla.     I used the M16 release from G     http://www.openvms.compaq.com/openvms/products/ips/get_mozilla.html 0     Follow the release notes there to install it,     Run it, and make sure it at least works.  " 3.  Get the latest version of GLIB5     I used 1.9.7 from ftp://ftp.gtk.org/pub/gtk/v1.2/      UnBzip2 it, untar it#     rename the directory to [.glib] 9     Copy in glibconfig.h_vms from the bottom of this file          to [.glib]glibconfig.h7     This directory is only needed for the header files. 0     (I hope to get glibconfig.h_vms added to the      next release of glib)  # 4.  Get the lastest version of GTK+ 5     I used 1.2.8 from ftp://ftp.gtk.org/pub/gtk/v1.2/      UnBzip2 it, untar it"     rename the directory to [.gtk]-     This is only needed for the header files.   # 5.  Get the latest version of IMLIB 7     ftp://ftp.gnome.org/pub/GNOME/stable/sources/imlib/          I used 1.9.8     UnBzip2 it, untar it$     rename the directory to [.imlib]=     copy the imlib_vms_build.com from the bottom of this file           to [.imlib]vms_build.com     set def [.imlib]5     Execute the vms_build and make sure imlib builds. <     (There will be several compiler warnings but I choose to5      leave them so maybe someday they will be fixed.) 8     run [.utils]IMLIB_CONFIG.EXE and make sure it works.=     If you have problems, make sure the logical etc exists or A     hard-code the correct directory in your sys$login:.imrc file. ;     (I hope to get theses changes added to the next version       of IMLIB)  2 6.  Get the latest stable version of Freeciv down.4     UnBzip2 it, untar it to the directory [.freeciv]%         $ bzip2 -d freeciv-1_11_0.bz2 #         $ tar -xvf FREECIV-1_11_0.; >     make sure Freeciv.h is in [.FREECIV-1_11_0.CLIENT.GUI-GTK]4         (You can rebuild this with GNV SED and rc2c)#     $ set def [.FREECIV-1_11_0.vms]      $ @vms_build.com<         You will get a few warnings but theses should be OK.=     Read the vms_build.com file or the unix install.; file if      you have problems    7.  Todo list:  .     Create a standard VMS binary distribution.?     Get changes needed into GLIB and IMLIB source distributions B     Get AUTOCONFIG to work on VMS so that VMS can use the standard         UNIX make-files./     Get RedHat Linux .RPM files to work on VMS. $         (Now I'm really dreaming...)   ----- ? Most of the problems I've found seem to be in all versions, but @ let me know if you run this, have fixes for the OpenVMS port, or/ can contribute to make the installation easier.    Roger    ------------------------------  % Date: Wed, 12 Jul 2000 14:08:10 -0400 3 From: "Gaitan D'Antoni" <gaitan.dantoni@compaq.com>   Subject: Re: Apache for Open VMS* Message-ID: <8kic7r$2lc@usenet.pa.dec.com>  K Printenv. is a perl script, not a cgi script that can be executed directly. 9 To test cgi try http://apache/cgi-bin/test-cgi-vms.com or & http://apache/cgi-bin/test-cgi-vms.exe    % Raji Arulambalam wrote in message ... I >The server does not execute any pages from the cgi-bin area, when I do a L >http://apache/cgi-bin/printenv  test. The server reports an Internal ServerE >error with this message "The server encountered an internal error or ; >misconfiguration and was unable to complete your request."    ------------------------------  % Date: Wed, 12 Jul 2000 13:38:38 -0400 / From: Bradford Hamilton <Brad.Hamilton@fmr.com>   Subject: Re: Apache for Open VMS' Message-ID: <396CAD1E.F6441210@fmr.com>    Hi,   F I'm a little confused here - the "current" beta is listed as 1.3.12 at the  web siteH (http://www.openvms.digital.com/openvms/products/ips/apache/apache.html)  F Will there be a "new" one available tomorrow, with a different version #?   Thanks,  Brad   Rick Barry wrote:  <snip>  ) The latest beta for Apache 1.3.12 removes P > this restriction. It should be available for download tomorrow (7/13/2000). BeP > sure to read the release notes as this beta kit will introduce changes to makeH > the installation and configuration for clusters more friendly, but the/ > startup/config procedures have changed a bit.  >  > Rick Barry > Apache/OpenVMS Project Team  > Compaq Computer Corporation  > Nashua, NH >  > Raji Arulambalam wrote:  >  > > Hi > > * > > Anybody running Apache for Open VMS.?? > > L > > I have the Beta version of Apache Web server 1.3.12 installed an a Alpha$ > > running OVMS 7.2 and TCPIP v5.0.L > > The server does not execute any pages from the cgi-bin area, when I do aO > > http://apache/cgi-bin/printenv  test. The server reports an Internal Server H > > error with this message "The server encountered an internal error or> > > misconfiguration and was unable to complete your request." > > 8 > > I have not changed any thing in the httpd.conf file. > > Otherwise it works fine. > > " > > Any help would be appreciated. > > TIA 1 > > ---------------------------------------------  > >   Raji Arulambalam > >   Systems Administrator $ > >   Bay of Plenty REGIONAL Council > >   P O Box 364 Whakatane. > >   NEW ZEALAND 7 > >   Phone: 0800 ENV BOP (0800 368 267) +64 7 921 3390 8 > >   Fax:    0800 ENV FAX (0800 368 329) +64 7 921 3393 > >   http://envbop.govt.nz 6 > > The Rules Have Changed...Get Paid to Surf the Web!3 > > http://www.alladvantage.com/go.asp?refid=LJG413 0 > > --------------------------------------------: > > Hell is other people.   - Jean-Paul Sartre (1905-1980) > > : > > ******************************************************J > > This e-mail has been checked for viruses and no viruses were detected.   ------------------------------  % Date: Wed, 12 Jul 2000 21:37:34 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: Boot Block 7 Message-ID: <200007122137_MC2-AC17-C37E@compuserve.com>   J         A program with PHY_IO or maybe LOG_IO that is writing to the disk=  E in the mistaken belief that it is some other device could do it.  The B arguments to $QIO that would specify the disk block are unused andJ therefore equal to zero.  Or something like that.  I read about this abou= t 1 15 years ago but have never actually observed it.     % Message text written by "Tomer Cohen" J >Does someone have any idea what could possibly destroy the boot block on=   an Alpha VMS 6.2 system?  <    ------------------------------  ! Date: Wed, 12 Jul 00 15:04:10 GMT  From: heimann@ecs.umass.edu  Subject: Re: Building TK50's, Message-ID: <8kj169$5s5$1@odo.ecs.umass.edu>  ( In Article <8kh1as$qs@usenet.pa.dec.com>2 carlini@true.lkg.dec.com (Antonio Carlini) writes:  	 (Snipped) L >>If you have greater disk capacity on the MVII, you could copy the savesets* >>over to the MVII and install from there. >  >Definitely the way to go. > P >Getting OpenVMS onto an RD54 is not too bad, but there won't be much room left  >over!  F Depends entirely on how much of VMS is loaded.  I have a VS2000 with aE RD54 out on the network here still running.  It has 100,000 blocks in E page and swap files and still has 25,000 blocks free on the disk.  Of F course, all it is doing is acting as a DECnet IV area router, so a lot was trimmed out.   Joe Heimann    heimann@ecs.umass.edu    ------------------------------    Date: 12 Jul 2000 16:49:11 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) . Subject: Re: DB connectivity via a web browser+ Message-ID: <GWZZql3mIIWf@eisner.decus.org>   y In article <NC_a5.53638$NP5.1702434@newsread2.prod.itd.earthlink.net>, "Mike Flaherty" <mflaherty2@earthlink.net> writes:   L > Also, does anyone know when Apache will be available for VMS (not the betaB > version).  I have been hearing "3 months" for the past year now.  * Well, how good is the Field Test version ?5 Can anyone say whether it is "ready for prime time" ?    ------------------------------   Date: 12 Jul 00 11:08:38 PST From: mckinneyj@cpva.saic.com 7 Subject: Re: Default protection for logfiles (VMS 7.1). ( Message-ID: <10hitqn3dgj6@cpva.saic.com>  * In article <396C9449.EA177BD3@bbc.co.uk>, 0  Tim Llewellyn <tim.llewellyn@bbc.co.uk> writes: >  > Hi > H > I am trying to understand how the default protection for batch job log > files  > is controlled. > H > Assume there are no default protection ACL's defined for the directory > where the logfile is created.  > = > The batch logfile is created before sylogin.com and the set  > protection/default# > command it contains are executed.  > C > The logfiles are being created G:RE, we would like G:RWE. Neither A > the device protection or the volume protection are set to G:RE.  > G > I dimly recall something about a disk initialization time setting but  > have$ > been unable to discover it so far. >   > Thanks in advance for any info >    SYSGEN>  HELP PARAM RMS_FILE  
 Parameters     RMS_FILEPROT  E        RMS_FILEPROT determines the default file protection for system G        processes such as those that create the error log, operator log, E        and job controller. It also determines default file protection G        for processes created by the job controller (all interactive and         batch processes). [...]    ------------------------------  % Date: Wed, 12 Jul 2000 16:52:27 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>8 Subject: Re: RE: Direct OPCOM messages to e-mail account7 Message-ID: <200007121652_MC2-AC14-21C5@compuserve.com>E  E         Have you considered the VMS APPEND command?  Try HELP APPEND!r     Message text written by Richarde8 >Is there a way to append files without subscribing to a mailing list?<   ------------------------------  # Date: Wed, 12 Jul 2000 20:16:48 GMTS) From: Lonny Balderston <lbalders@gte.net>m" Subject: disable spawn in VMSMail?# Message-ID: <396CD23A.1A9B@gte.net>V  / (previously posted on vmsnet.alpha 22-JUN-2000)m  4 Is there an easy way to disable the "spawn" command 6 that can be found in in VMSMail? [new: without messing6 with UAF flags. I have no control over the application5 we are running, probably cannot change UAF parameters06 without causing problems. Just want to disable "spawn"- in VMS Mail. Alpha 4100 running VMS 7.1-1H1.]a   Thank you, Lonny Balderstone email: lbalders at gte dot net   ------------------------------  # Date: Wed, 12 Jul 2000 23:54:58 GMTe, From: TMcGrath@cendant.com.au (Tony McGrath)/ Subject: Re: DSSI shadow problem on VAX VMS 7.2i2 Message-ID: <396d0118.5132557@news.ozemail.com.au>  E On Tue, 11 Jul 2000 23:23:26 GMT, "Neil Rieck" <n.rieck@sympatico.ca>r wrote:  L >I'm running OpenVMS 7.2 on three different VAXs (not part of a cluster) andK >when I do a reboot after a clean shut down, I get an error saying that the-K >drives were dismounted incorrectly. This almost always results in a shadow-7 >set merge. The hardware configurations are as follows:s >sL >1. One 6430 using two DSSI buses each connected to an HSD05 containing RZ29- >drives. I'm shadowing across the DSSI buses.r >CJ >2. One 4300 using two DSSI buses each connected to three RF35 drives. I'm! >shadowing across the DSSI buses.b >lK >3. One 3800 using one DSSI bus connected to one HSD05 containing four RZ29d3 >drives. I'm shadowing between drives in the HSD05.d >rM >These machines worked fine under OpenVMS 6.2. Does anyone have any idea what  >is going on here? >- >Neil Rieck- >Kitchener/Waterloo/Cambridge, >Ontario, Canada.-" >http://www3.sympatico.ca/n.rieck/J >An eerie silence fills the room with the gentle whisper of the breeze and" >the frogs singing in the distance  E Fire up DejaNews and have a look for an item posted by Andy GoldsteinaB in Comp.OS.VMS on 29-JUN-1999, titled "Re: Dismounting a disk with additional pagefile installed".e  = Alternatively, go to http://www.deja.com/=dnc/forms/mid.shtmlg and enter this Message Id :e- <3778CBEF.11B267A3@star.zko.dec.youknowwhere>    It may explain what's going on.u  C Andy said "We're working on it". I wonder how they're progressing ?    Cheers from Down Under,l    Tony   C Tony McGrath, Systems Administrator, British Airways Executive ClubtN Cendant Membership Services, 596 North Road, Ormond, Victoria, 3204, Australia- Phone : 61 3 9578 8233   Fax : 61 3 9578 6326    ------------------------------  # Date: Wed, 12 Jul 2000 18:58:23 GMT / From: "John Nixon" <jorlnixon@worldnet.att.net>c Subject: duplicate file namestF Message-ID: <jd3b5.6146$bR6.480547@bgtnsc04-news.ops.worldnet.att.net>  F I have already logged this with Compaq support, but so far there is no
 answer.  Theys have never seen this.   K I am working on a VAX 7860 with VMS 7.1.  There are also a couple of Alphas K in the cluster with Alpha VMS 6.2  (soon to be upgraded to vms 7.2-1).  Thee disk is a software shadow set.  J While moving the data from an MTI disk to a Storageworks disk (by the way, anybody K wanna buy a lot of MTI Storageware disks cheap);  anyway, while moving this  dataF we began getting errors  "file already exists", even though we knew it didn't exist.  H When I looked at the original disk directory, I saw several files of the EXACT name,GH right down to the version number. They had different file-ids, different cre/mod dates,G they were different sizes and had different data.  These were log filesi being kept around.D for statistical purposes.  (Thank god they are not Production data)!  C If I do a $DIR   filename.dat;1    I only see one file, but if I dotG $DIR filename.dat;* it lists both (or all three or four) files with theB
 same name.  @ In order to look at the older one, I have to COPY FILENAME.DAT;*E to   TMP.DAT;0,   which forces it to copy both files to TMP.DAT;1 andi TMP.DAT;2 etc...  I I can't imagine RMS allowing this to happen, but I can't think of any wayt any of= our applications could be creating files while bypassing RMS.O  L Any Ideas?  Has anyone ever saw this before?   If I am not the only one thatA has seen this I think I would have a better chance of getting VMSr engineeringd	 involved.    ------------------------------  # Date: Wed, 12 Jul 2000 19:17:42 GMT  From: byatesiii@my-deja.comT! Subject: Re: duplicate file names,( Message-ID: <8kig84$28$1@nnrp1.deja.com>  F In article <jd3b5.6146$bR6.480547@bgtnsc04-news.ops.worldnet.att.net>,2   "John Nixon" <jorlnixon@worldnet.att.net> wrote:H > I have already logged this with Compaq support, but so far there is no > answer.  Theyw > have never seen this.n > F > I am working on a VAX 7860 with VMS 7.1.  There are also a couple of AlphasE > in the cluster with Alpha VMS 6.2  (soon to be upgraded to vms 7.2-e 1).  The  > disk is a software shadow set. >eG > While moving the data from an MTI disk to a Storageworks disk (by thed way,	 > anybody A > wanna buy a lot of MTI Storageware disks cheap);  anyway, whileu moving thisn > dataH > we began getting errors  "file already exists", even though we knew it > didn't > exist. >*F > When I looked at the original disk directory, I saw several files of the0
 > EXACT name, @ > right down to the version number. They had different file-ids,	 different1 > cre/mod dates,C > they were different sizes and had different data.  These were logC files. > being kept aroundPF > for statistical purposes.  (Thank god they are not Production data)! >nE > If I do a $DIR   filename.dat;1    I only see one file, but if I doIE > $DIR filename.dat;* it lists both (or all three or four) files withs ther > same name. >tB > In order to look at the older one, I have to COPY FILENAME.DAT;*G > to   TMP.DAT;0,   which forces it to copy both files to TMP.DAT;1 and  > TMP.DAT;2 etc... >aG > I can't imagine RMS allowing this to happen, but I can't think of anyt way  > any of? > our applications could be creating files while bypassing RMS.C >sE > Any Ideas?  Has anyone ever saw this before?   If I am not the onlyl one thatC > has seen this I think I would have a better chance of getting VMS 
 > engineeringo > involved.  >  >t8 Tried an analyze/disk/repair? (after backup, of course).C As for MTI drives, it's nice to know we weren't the only suckers....    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  # Date: Wed, 12 Jul 2000 20:06:55 GMTd1 From: "Mark D. Jilson" <jilly@clarityconnect.com>e! Subject: Re: duplicate file namese2 Message-ID: <396CCFA9.9FE8B09A@clarityconnect.com>  B This has nothing to do with RMS, this is the F11BXQP.  I have seenG similar things and they have been due to disk defrag products.  You may/G want ot look at the ECO_SUMMARY article for the VAXF11X06_071 patch kite8 to see if there is anything in there that looks similar.   John Nixon wrote:e > H > I have already logged this with Compaq support, but so far there is no > answer.  Theya > have never seen this.c > M > I am working on a VAX 7860 with VMS 7.1.  There are also a couple of Alphas M > in the cluster with Alpha VMS 6.2  (soon to be upgraded to vms 7.2-1).  Thes  > disk is a software shadow set. > L > While moving the data from an MTI disk to a Storageworks disk (by the way,	 > anybody M > wanna buy a lot of MTI Storageware disks cheap);  anyway, while moving this  > dataH > we began getting errors  "file already exists", even though we knew it > didn't > exist. > J > When I looked at the original disk directory, I saw several files of the
 > EXACT name,8J > right down to the version number. They had different file-ids, different > cre/mod dates,I > they were different sizes and had different data.  These were log filese > being kept aroundxF > for statistical purposes.  (Thank god they are not Production data)! > E > If I do a $DIR   filename.dat;1    I only see one file, but if I doeI > $DIR filename.dat;* it lists both (or all three or four) files with the. > same name. > B > In order to look at the older one, I have to COPY FILENAME.DAT;*G > to   TMP.DAT;0,   which forces it to copy both files to TMP.DAT;1 and  > TMP.DAT;2 etc... > K > I can't imagine RMS allowing this to happen, but I can't think of any wayw > any of? > our applications could be creating files while bypassing RMS.d > N > Any Ideas?  Has anyone ever saw this before?   If I am not the only one thatC > has seen this I think I would have a better chance of getting VMS 
 > engineeringd > involved.    --  D Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------   Date: 12 Jul 2000 20:21:39 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)! Subject: Re: duplicate file namesa6 Message-ID: <8kik0j$4jm$1@mailint03.im.hou.compaq.com>  x In article <jd3b5.6146$bR6.480547@bgtnsc04-news.ops.worldnet.att.net>, "John Nixon" <jorlnixon@worldnet.att.net> writes:( :I am working on a VAX 7860 with VMS 7.1 ..K :I can't imagine RMS allowing this to happen, but I can't think of any way aE :any of our applications could be creating files while bypassing RMS.- : M :Any Ideas?  Has anyone ever saw this before?   If I am not the only one that@B :has seen this I think I would have a better chance of getting VMS :engineering involved.  @   Which set of disks is this problem occuring on?  Is this stuffA   occuring (twice) on the source disks and directories, or on theo   target disks and directories?i     Any I/O caching tools?  !   Any disk defragmentation tools?   B   Check for and apply the VAXF11X (XQP), VAXRMS, VAXSYSA, VAXSYSB,B   VAXMOUN, VAXSHAD (if shadowing is in use), and VAXLOGI (and any !   other "1" ECO kits) as a start.e  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 12 Jul 2000 17:02:25 -0400:- From: JF Mezei <jfmezei.spamnot@videotron.ca>.! Subject: Re: duplicate file names , Message-ID: <396CDCCD.656BF80C@videotron.ca>  . re: idientical file names, different file IDs.  L This may sound silly, but are you sure the files are in the same directory ?O Perhaps your device name is a rooted logical name that contains a search list ?k   ------------------------------  % Date: Wed, 12 Jul 2000 22:36:39 -0500s) From: "John E. Malmberg" <wb8tyw@qsl.net>w Subject: Re: Editor Commands/ Message-ID: <smqdu3a1nd6170@corp.supernews.com>i  2 Hoff Hoffman <hoffman@xdelta.zko.dec.nospam> wrote<  in message news:8ki12b$121$1@mailint03.im.hou.compaq.com... >o- > In article <396d6a06.78564810@news.dal.ca>,k* >  hx_101@hotmail.com (Horse Nuts) writes:H > :Looking for a reference to editor commands!!! Anyone have any links?? <snip>L >   Can't say I've seen teco!!!! or ked!!!! documentation recently, but I do4 >   have a teco manual buried somewhere on my shelf.  : For TECO, documentation and release notes can be found at:  L http://metalab.unc.edu/pub/academic/computer-science/history/pdp-11/teco/doc /i   -Johnv wb8tyw@qsl.network   ------------------------------  % Date: Wed, 12 Jul 2000 21:30:48 -0400e2 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: Find Files utilityq7 Message-ID: <200007122131_MC2-AC17-C34D@compuserve.com>p  A         How about SEARCH and DIRECTORY?  See HELP SEARCH and HELPb= DIRECTORY.  Gnu grep has been ported to VMS; try ftp.wku.edu.-  F         If this does not help, perhaps you should try explainging your= problem in sufficient detail to elicit a meaningful response!     ' Message text written by "Thomas nilsen"0J >Does anyone know of a utillity to search/find files on disks for OpenVMS=   7.13 AXP?  J I've browsed through the free software archive without finding anything.<=   ------------------------------  % Date: Thu, 13 Jul 2000 00:17:20 +0200-. From: "Jesper Naur" <jesper.naur@post.tele.dk>$ Subject: Re: FTP to/from Alpha boxes, Message-ID: <8kiqsm$6ca$1@news.inet.tele.dk>  ) From: Andy Proctor <aproctor@hotmail.com>a Newsgroups: comp.os.vmss8 > Also the customer says that in the file is the message UCX$FTPD_STARTUP.LOG: I > "SYSTEM-F-NOPRIV Insufficient privilege or object protection violation"> (hej9 > did not send me the full file, just extracts as below.)o  - OK, I'm beginning to think, that your problemr/ has NOT to do with the actual TCP/IP connectiont5 (which would otherwise also show problems when tryingo( telnet or ping), but rather with the FTP1 specific actions. In a normal standard VMS TCP/IPa6 installation, the following happens, when some foreign  host tries to connect using FTP:  @ 1) A process is created with username UCX$FTP (this is an actual    UAF account).D 2) This process is given SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD_STARTUP.COM    to execute.' 3) UCX$FTPD_STARTUP.COM basically does:-  :    $ DEFINE SYS$OUTPUT SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD.LOG9    $ DEFINE SYS$ERROR SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD.LOGs     $ RUN SYS$SYSTEM:UCX$FTPD.EXE  3 In order for this to work, the following conditionsc must be fulfilled:  :    User UCX$FTP (which is created during UCX installation)#    must have Read/Execute access tos2    SYS$SYSDEVICE:[UCX$FTP]UCX$FTPD_STARTUP.COM and    SYS$SYSTEM:UCX$FTPD.EXE  ; Since already UCX$FTPD_STARTUP.LOG contains error messages, : this indicates, that the access problems start at a rather early stage.  ! We shall need from your customer:o   Output from:   $ ucx sh service ftp/full," $ dir/full sys$system:ucx$ftpd.exe6 $ dir/full sys$sysdevice:[ucx$ftp]ucx$ftpd_startup.com, $ dir/full sys$sysdevice:[000000]ucx$ftp.dir   Listing of the UCX$FTP account:u   $ set def sys$system $ mc authorize UAF> SH UCX$FTP-  , If possible, instruct the customer to insert  
  $ SET VERIFYi  @ at the beginning of sys$sysdevice:[ucx$ftp]ucx$ftpd_startup.com,? and provide the contents of ucx$ftpd_startup.log resulting fromd! an FTP attempt after this change.3  A Also, see if any ucx$ftpd.log files are created, and include thema as well.  @ (I'm giving this rather long list of instructions, since we seem& to be operating in 'batch mode' here).  
  Best regardsn  Jesper Naur   ------------------------------   Date: 12 Jul 2000 18:55:42 GMT* From: bdwheele@indiana.edu (Brian Wheeler)' Subject: Re: Hobbyist TCP IP licenses ?-3 Message-ID: <8kieve$4ag$1@flotsam.uits.indiana.edu>i  I In article <418E68E524A8D311ACCE00508B78866A7680A7@exchange.t-netix.com>, 0 	Lorin Ricker <Lorin.Ricker@t-netix.com> writes:/ >> Also, always match the case of every letter e$ >> in every place that uses letters.2 >>(As far as I can recall, only upper case letters. >> are used in a PAK - but I may be mistaken). > J > No, you're not mistaken, but VMSLICENSE.COM accepts user input in eitherL > case, then UPCASEs it before using it (esp. on the checksum), so you can'tD > go wrong entering PAKs in upper *or* lower case.  But do proofread > carefully! > 
 > regards, >   Lorin Ricker >   C I might be wrong, but it seems like I was putting a hardware ID andtC used different case (lower instead of upper) and it failed.  When IsB changed it, it worked.  It just seems like that one entry was case sensitive...   Briant   ------------------------------  # Date: Wed, 12 Jul 2000 18:21:04 GMT " From: falk@arc.ab.ca (Alfred Falk)/ Subject: Re: How to disable DecWindows for OPA0t2 Message-ID: <8F6F78D23falkarcabca@205.233.108.180>  1 jfmezei.spamnot@videotron.ca (JF Mezei) wrote in  ! <396B7643.7DD55264@videotron.ca>:t   >Eddy wrote: >> p< >> I know I've done this before, but I can't remember how...< >> I need to disable DecWindows for OPA0: I have an AXP with) >> VGA and I just want a terminal screen.1 >u >BOOT/1: >SYSBOOT> SET WINDOW_SYTEM 0 >SYSBOOT> CONTINUE  G If you still want to leave DECwindows on (i.e. for remote workstations)e6 you could add the following line to SYSTARTUP_VMS.COM:1     	$ DEFINE/SYSTEM DECW$IGNORE_WORKSTATION TRUEd  @ ----------------------------------------------------------------A   A L B E R T A         Alfred Falk               falk@arc.ab.ca  @ R E S E A R C H         Information Systems Dept   (780)450-5185+   C O U N C I L         250 Karl Clark Roadt1                         Edmonton, Alberta, Canada  http://www.arc.ab.ca/   T6N 1E4i  http://www.arc.ab.ca/staff/falk/   ------------------------------  % Date: Wed, 12 Jul 2000 14:41:34 -0700b( From: Eddy <eddy@jumpstart-services.com>/ Subject: Re: How to disable DecWindows for OPA0p6 Message-ID: <396CE60E.E028D717@jumpstart-services.com>   Alfred,i  > The DECW$IGNORE_WORKSTATION logical was exactly what I wanted. Thanks,0 Eddy Fey   Alfred Falk wrote:  2 > jfmezei.spamnot@videotron.ca (JF Mezei) wrote in# > <396B7643.7DD55264@videotron.ca>:  >a > >Eddy wrote: > >>> > >> I know I've done this before, but I can't remember how...> > >> I need to disable DecWindows for OPA0: I have an AXP with+ > >> VGA and I just want a terminal screen.1 > >2	 > >BOOT/16 > >SYSBOOT> SET WINDOW_SYTEM 0 > >SYSBOOT> CONTINUE >mI > If you still want to leave DECwindows on (i.e. for remote workstations)w8 > you could add the following line to SYSTARTUP_VMS.COM:6 >         $ DEFINE/SYSTEM DECW$IGNORE_WORKSTATION TRUE > B > ----------------------------------------------------------------B >   A L B E R T A         Alfred Falk               falk@arc.ab.caB > R E S E A R C H         Information Systems Dept   (780)450-5185- >   C O U N C I L         250 Karl Clark RoadD3 >                         Edmonton, Alberta, Canadas! > http://www.arc.ab.ca/   T6N 1E4l" > http://www.arc.ab.ca/staff/falk/   ------------------------------  % Date: Wed, 12 Jul 2000 22:07:57 -0700d) From: "loribug1" <loribug1@email.msn.com>o Subject: ibm 18 gig drives) Message-ID: <uyQpCjI7$GA.386@cpmsnbbsa08>   2 Does anyone know how to make dnes 18gig drive scsi' drive work on alpha station 200 4/233 .m7 with vms firmware sees drive but drive will not spin up " to init.. system says its online.. is there some firmware trick ..n   help.. Gary C.e   ------------------------------  % Date: Thu, 13 Jul 2000 01:19:15 -0400 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: ibm 18 gig drivesL Message-ID: <rdeininger-1307000119160001@user-2iveb1n.dialup.mindspring.com>  T In article <uyQpCjI7$GA.386@cpmsnbbsa08>, "loribug1" <loribug1@email.msn.com> wrote:  4 > Does anyone know how to make dnes 18gig drive scsi) > drive work on alpha station 200 4/233 . 9 > with vms firmware sees drive but drive will not spin upo$ > to init.. system says its online..! > is there some firmware trick ..h  ? What VMS version?  V7.1 or later will probably have better luckF with off-brand disk drives.-   -- - Robert Deininger rdeininger@mindspring.com:   ------------------------------  # Date: Thu, 13 Jul 2000 01:40:43 GMTp2 From: "Zane H. Healy" <healyzh@shell1.aracnet.com>0 Subject: Re: Mac-Decnet via Webster Multiport LT6 Message-ID: <v69b5.453$sp6.146054@typhoon.aracnet.com>  ! Hans Vlems <hvlems@iae.nl> wrote:eJ > You need DECnet for the MAC. There used to be a product in the Pathworks > familyJ > that supported the MAC. I believe it is no longer available, but perhaps > some kind  > soul can give you the kit.N > There may be third party vendors that still sell a DECnet stack for the MAC.  K There *used* to be DECnet for the Mac available from the company that makes I DAVE (SMB for the Mac).  A portion of that product is available with the tL eXodus X-Windows software for the Mac, but I think all you can do with it is! use it as an X-Windows transport.    			Zane    ------------------------------  % Date: Wed, 12 Jul 2000 13:55:26 -0400y- From: "Peter Weaver" <peter.weaver@stelco.ca>T Subject: Re: mimei. Message-ID: <smpc8isqnd694@corp.supernews.com>  = Paul wrote in message <396C5A54.6211FC5A@evms.zko.dec.com>...l > ...aF >The latest available version of MIME is version V1.32 (and soon there> >will be V1.4 available). The number of problems fixed are too numerousF >to mention. Although I can post them if there is a real interest. You >can use the commands: >l > MIME> SHOW VERSION >...or% > $ ANALYZE/IMAGE SYS$SYSTEM:MIME.EXEg > ...o    D Interesting on how the two version numbers do not match. Where do we get the latest MIME from?i   MIME> show ver MIME Version: V1.6 MIME>  ExitfE NETHER::SYSTEM>pipe ANALYZE/IMAGE SYS$SYSTEM:MIME.EXE | sear sys$pipee
 identifica tion(         Image Identification Information4                 image file identification: "V1.0-04"B                 image file build identification: "PCSI-0050120000"/                 linker identification: "A11-39"d   ------------------------------   Date: 12 Jul 2000 18:17:10 GMT* From: helbig@astro.rug.nl (Phillip Helbig) Subject: Re: mimet. Message-ID: <8kicn6$4h2$3@info.service.rug.nl>   >> MIME> SHOW VERSION   # $ MC MIME SH VERS does not work....    ------------------------------  % Date: Wed, 12 Jul 2000 15:03:26 -0400u' From: Paul <pmosteika@evms.zko.dec.com>h Subject: Re: mime versions0 Message-ID: <396C88BE.512FF055@evms.zko.dec.com>  F The version shown with the MIME command SHOW VERSION should match the  version    $ sho symb MIMER325   MIMER32 == "$ SYS$SYSTEM:MIME.EXE_V132_06-MAR-2000"n    	 $ MIMER32o  
 MIME> sho vera MIME Version: V1.32e MIME>  Exita  + $ anai SYS$SYSTEM:MIME.EXE_V132_06-MAR-2000t. SYS$COMMON:[SYSEXE]MIME.EXE_V132_06-MAR-2000;1 Imager OpenVMS VAX 
 Executable "MIME" "V1.32"C ""  6-MAR-2000 18:32:30.67   H In earlier versions, the version was incremented internally for the SHOWE VERSION display, but this did not match the version in the image filei identification.t  C Later, these were both reset to match the groups of changes made tooH MIME, starting with the 3rd set of changes, or version V1.3, and the two% smaller changes that followed, V1.32.s  E Judging from the one that displays version V1.6, this corresponds to oF version V1.2. Although I would need more file header information to beI certain. There have been two changes since, V1.3 and V1.32 (the latest).    B The other problem, (with $MC SHO VER), is that MIME only accepts aG filename as the P1 parameter for the file to open for read-only access.s This is equivalent to:   $ MIME :== $SYS$SYSTEM:MIME.EXEa   $ MIME   MIME> open filenameo       				Paul Mosteikan   				12-Jul-2000l   ------------------------------  % Date: Wed, 12 Jul 2000 16:01:01 -0400t- From: "Peter Weaver" <peter.weaver@stelco.ca>o Subject: Re: mime versions/ Message-ID: <smpjk0l1nd6136@corp.supernews.com>.  = Paul wrote in message <396C88BE.512FF055@evms.zko.dec.com>... F >The version shown with the MIME command SHOW VERSION should match the >version    ! I agree, too bad that they don't.m   > ...cD >In earlier versions, the version was incremented internally for the SHOWF >VERSION display, but this did not match the version in the image file >identification. >dD >Later, these were both reset to match the groups of changes made toE >MIME, starting with the 3rd set of changes, or version V1.3, and theh twos& >smaller changes that followed, V1.32. >oE >Judging from the one that displays version V1.6, this corresponds to D >version V1.2. Although I would need more file header information to be@ >certain. There have been two changes since, V1.3 and V1.32 (the latest).  A This is the verions that was installed when we used the 7.2-1 CD.2D Whatever version DEC shipped on that CD is what I have. Once again I5 ask, where do we get the latest version of MIME from?,    C >The other problem, (with $MC SHO VER), is that MIME only accepts a @ >filename as the P1 parameter for the file to open for read-only access."    D Sounds like a design problem to me. Whatever happened to the quality> control people at DEC who would have never let this (or CompaqC Analyze, just look at the startup procedures for CA and tell me howdD that made it out the door, people should be fired for that garbage!)F out the door? Before Philip posted his message the first thing I triedB was MCR MIME SHOW VERSION and I received exactly the same thing asE Philip. I think most VMS people would try the same thing without evenfB thinking about it. It is part of this VMS mind-set where we expectF things to work the same way, we expect /OUT= to create an output file,C we expect MCR xxx SHOW VERSION to show us a version number. We alsot# expect programs to say things like;   + %MIME-F-OPENIN, error opening SHOW as inpute -RMS-E-FNF, file not found or@ %DCL-E-MAXPARM, too many parameters - reenter command with fewer
 parameters
  \VERSION\  B we do not expect to see the screen clear and the command prompt toC appear when we make a mistake by assuming that the person who wrote " the program was in a VMS mind-set.  F Now that I have written that, forget my previous questions about where? do I get an updated copy of MIME, I'm taking it off my systems.C     Peter Weaver   ------------------------------  # Date: Thu, 13 Jul 2000 03:17:10 GMT-0 From: gilley@nospam.bravewc.com (Charles Gilley)- Subject: Re: MIN BOOT problem - openVMS 5.5-2o= Message-ID: <byab5.1208$PI1.83940@news-west.usenetserver.com>$   To close off this thread:.  G 1) I did not see a # sign, I saw a $.  Been doing too much Unix lately.t  9 2) The problem was with set/startup=opa0:  Setting it to o* sys$system:startup.com resolved the issue.   Thanks to all who contributed.  > In article <SmR95.3177$451.91241@news-west.usenetserver.com>, 1 gilley@nospam.bravewc.com (Charles Gilley) wrote:yP >On a rather aged VAX today, I ran into a bit of a problem booting the machine. K >Now I'll admit right now that my VMS is rusty. At boot, this machine wouldvM >stop at the # prompt.  Hmmm, I thought, it is set to minimum boot.  Okay, I cN >can fix that.  So, setting the bflg to 1, I popped into sysboot to change theO >value of STARTUP_P1.  But it isn't set to MIN, it's blanks.  Huh?  So, I went  ? >on and ran startup.com, but why is my machine acting this way?S >,2 >Thanks for any pointers, this one has me stumped. >O. >chg (watch the antispam in the email address) >  >-   ------------------------------  # Date: Wed, 12 Jul 2000 18:44:30 GMT-- From: "Richard D. Piccard" <piccard@ohio.edu>n2 Subject: Re: Minimum Page/Swap File Size in Blocks( Message-ID: <396CBC87.2E6DE4E4@ohio.edu>  F One item that I have not seen mentioned in this thread is dump files. H In most situations it would be good to have at least a minimal dump fileF on the system disk, to help diagnose problems early in the boot.  WhenG tight on disk space, I have usually added the lines in MODPARAMS.DAT to H use the primary paging file for dumping, and had no swap or dump files. C This let me have a usefully large primary page file with less space  sitting idle most of the time. t  H As Hoff and many others here well know, setting this up requires care toE avoid having disk blocks stomped on:  rename the swap and dump files,g reboot, THEN delete them!   G Hoff, two follow-up questions:  can the swapper process use a swap file ? more efficiently for swapping than it can use the page file forrE swapping?  Is there any other reason for having a separate swap file?a   				RDP    Hoff Hoffman wrote:u >  > In article <9F664D538536D411BD3200508B6FF01A333663@bdant027.bda.bobda.com>, "Boyle, Darren" <boyledj@bankofbermuda.com> writes:fM > :       What's the absolute minimum file size in blocks of the Primary page/8 > :& swap files for OpenVMS 7.1 (VAX) and 7.1-2 (Alpha). > G >   Zero.  You can quite successfully boot with no primary pagefile andBH >   no primary swapfile present on the system disk, assuming the OpenVMSA >   system has a reasonable amount of physical memory configured.u > G >   You do want to have at least a pagefile connected before you createbG >   processes that will need to be running for a while and/or utilizingrD >   large amounts of virtual memory, lest the processes involved (orE >   potentially the OpenVMS system) comes to a grinding halt when alls2 >   available (free) physical memory is exhausted. > I >   SYPAGSWPFILES.COM (qv: .TEMPLATE) runs early on enough in the OpenVMStE >   bootstrap process that it can (and should be) used to connect the-J >   necessary secondary pagefile(s) and (if desired/required) swapfile(s). > P >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   --  B ==================================================================B Dick Piccard                           Academic Technology ManagerB piccard@ohio.edu                                 Computer ServicesB http://oak.cats.ohiou.edu/~piccard/                Ohio University   ------------------------------   Date: 12 Jul 2000 19:43:21 GMT2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)2 Subject: Re: Minimum Page/Swap File Size in Blocks6 Message-ID: <8kihop$47e$1@mailint03.im.hou.compaq.com>  X In article <396CBC87.2E6DE4E4@ohio.edu>, "Richard D. Piccard" <piccard@ohio.edu> writes:  G :One item that I have not seen mentioned in this thread is dump files. sI :In most situations it would be good to have at least a minimal dump fileFG :on the system disk, to help diagnose problems early in the boot.  When[H :tight on disk space, I have usually added the lines in MODPARAMS.DAT toI :use the primary paging file for dumping, and had no swap or dump files. fD :This let me have a usefully large primary page file with less space  :sitting idle most of the time.   H   On recent OpenVMS Alpha releases, a "stub" dump file (SYS$ERRLOG.DMP) D   exists for use during error logging.  Otherwise (and also over on D   OpenVMS VAX), at least a small system dump file (usually circa 20 C   blocks or so, IIRC) is required if the system is to preserve the tE   contents of the error log buffers over a crash.  SYS$ERRLOG.DMP wassG   set up on OpenVMS Alpha to avoid the problems that are seen with not  G   having a dump file around, or not having a sufficiently large (thoughcH   still quite small) dump file around for the contents of the error log 
   buffers.  D   Dump-of-the-system-disk (DOSD) is also available on various recentH   OpenVMS releases and platforms, and there are good selective-dump and F   compressed-dump features available on various OpenVMS Alpha systems.  I :As Hoff and many others here well know, setting this up requires care to F :avoid having disk blocks stomped on:  rename the swap and dump files, :reboot, THEN delete them! e  C   We fixed that bug a while back -- these files are now held open.  B   (Because the files were opened early during the bootstrap, usingC   rather primitive I/O routines, it was once feasible to delete thevE   files from underneath OpenVMS.  With potentially dire consequences.0D   Now, if you delete the active files, things will continue to work D   just fine.  You will have to ANALYZE/DISK/REPAIR to get the space G   back if you do delete these (active) files, however.  Best to create pH   a newer (smaller) version(s) of the files, reboot, and then purge the    older version(s).,  D   The consequences of the old OpenVMS behaviour around deleted page,H   swap and/or dump files are analogous to the long-standing restriction G   on VAXstation 3100 series systems; the VAXstation 3100 series system eH   disk size limitation.  Crashing a VAXstation 3100 with part or all of H   the system dump file located out past 1.073 GB will cause the console I   ROM drivers to wrap around references starting at 1.073 GB back to the  I   beginning of the disk.  This will scribble the blocks intended for the  H   dump file elsewhere on the disk.  With unpleasant consequences.  (ThisF   is why I don't recommend using a system disk larger than 1.073 GB onG   the VAXstation 3100 series: the corruption can strike days or months rD   after the trigger is set, and an innocent AUTOGEN pass or OpenVMS #   upgrade can "arm" the trigger...)c  H :Hoff, two follow-up questions:  can the swapper process use a swap file@ :more efficiently for swapping than it can use the page file forF :swapping?  Is there any other reason for having a separate swap file?  J   Traditionally, the swapper has tried to use large(r) write clusters for H   out-swapping I/O, meaning that the swapper tries to allocate and writeG   out the process in as few and as large of hunks as is possible.   The-H   pagefile(s) (and also the swapfile(s), of course) can get fragmented, B   so swapping out large and contiguous chunks may not be possible.  J   Because I don't tend to see (nor do I usually tune for) swapping on the I   local systems, I tend to prefer to (over-)configure the available disk fG   storage into the pagefile(s) and thus not to "idle" the disk storage 3H   under the seldom-used swapfile.  In those few (and rare) cases where aI   process gets outswapped, I've storage available for it in the pagefile.e  J   If, on the other hand, you have tuned the system for swapping (and thereL   are valid reasons to do this) or if don't have enough physical memory and K   are accordingly seeing regular swapping activity, you will probably want r7   to create and to size the swapfiles(s) appropriately.t  H   It would not surprise me to learn that somebody's done a study of thisG   stuff...  And most every system has a different set of constraints...S  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Wed, 12 Jul 2000 19:58:17 GMTT1 From: "Mark D. Jilson" <jilly@clarityconnect.com>-2 Subject: Re: Minimum Page/Swap File Size in Blocks2 Message-ID: <396CCDA4.BD3C4077@clarityconnect.com>   "Richard D. Piccard" wrote: J > As Hoff and many others here well know, setting this up requires care toG > avoid having disk blocks stomped on:  rename the swap and dump files,a > reboot, THEN delete them!w  F Not absolutely necessary these days although it is the best practice. E VMS leaves an open channel to these files so if you delete them theiruH space cannot be reused until after you reboot and do an ANA/DISK/REPAIR.   > I > Hoff, two follow-up questions:  can the swapper process use a swap file A > more efficiently for swapping than it can use the page file for G > swapping?  Is there any other reason for having a separate swap file?e  H It really depends on the amount of free space in the pagefile being usedD for both paging and swapping and the dynamics of the actual paging &B swapping activities on the system.  Since the allocation sizes forA paging & swapping are different you can generally say that having84 separate files will be more efficient than just one.   --  D Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  % Date: Wed, 12 Jul 2000 16:37:53 -0400t% From: "Brian Tillman" <tillman_brian> 2 Subject: Re: Minimum Page/Swap File Size in Blocks$ Message-ID: <396cd6ed$1@news.si.com>  D >What's the absolute minimum file size in blocks of the Primary page8 >& swap files for OpenVMS 7.1 (VAX) and 7.1-2 (Alpha).    A Zero.  You don't need ANY page and swap files on the system disk.a   -- s  A Brian Tillman                   Internet: tillman_brian at si.comoA Smiths Industries, Inc.                   tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------    Date: 12 Jul 2000 17:44:41 -0500* From: young_r@eisner.decus.org (Rob Young)2 Subject: Re: Minimum Page/Swap File Size in Blocks+ Message-ID: <7umpioyD1hiQ@eisner.decus.org>    In article <9F664D538536D411BD3200508B6FF01A333663@bdant027.bda.bobda.com>, "Boyle, Darren" <boyledj@bankofbermuda.com> writes:0 > Hi,m > F > 	What's the absolute minimum file size in blocks of the Primary pageH > & swap files for OpenVMS 7.1 (VAX) and 7.1-2 (Alpha).  The systems areN > configures with 448Mb & 4096Mb respectively.  Obviously this should still beI > big enough to accommodate the start-up process  until SYPAGESWPFILES iss( > called to install the secondary files. > TIA, > Darren >   1 	Depending what you find where you are at :-) ...d  : 	At a site , they didn't have any primary page file on the9 	system disk.  They had someone at one time that had thisi< 	theory to have many pagefiles... 9 per system in fact (what= 	a mess and what a *bad* idea in hindsight).  Since a process:C 	can only map to 4 pagefiles, they had a process that couldn't growi< 	any further because it ran out of paging space so I had to # 	grow the pagefiles, all of them.  1  9 	A procedure I created to manage this mess was to installI< 	page files after startup.  One node in the cluster broke onH 	this procedure (forgot to add that node as a target) and a *week later*H 	after reboot, the sucker hung.  Tracked it down via SHOW MEMORY that I ? 	didn't have a page file installed!  (Alpha VMS, version 7.1 , C& 	512 MByte).   Ooops!, time to reboot!  
 	My point... -  @ 	You can install page files later in the startup with the amount 	of memory you have.  D 	At another site with much more saner policies (following guidelines= 	found somewhere) I see a primary pagefile on the system diskNA 	of 10000 blocks, and another one matching memory size elsewhere.    				RobM   ------------------------------   Date: 12 Jul 2000 18:58:16 GMT* From: bleau@umtof.umd.edu (Lawrence Bleau)2 Subject: Re: MX 4.2 won't rebuild, what's missing?) Message-ID: <8kif48$ths$3@hecate.umd.edu>M  p In article <396be73e.524144494f47414741@radiogaga.harz.de>, martin@radiogaga.harz.de (Martin Vorlaender) writes: >:J >: Sure enough, there isn't a STARLET.B32 (or whatever it's supposed to be >: called) in SYS$LIBRARY:.a >n= >$ BLISS /LIBRARY=SYS$COMMON:[SYSLIB] SYS$LIBRARY:STARLET.REQe >a: >(This is done during BLISS installation on a VAX system.)  F If you note my original post, I state that I'm on an Alpha, not a VAX.  K Another poster, who replied on vmsnet.mail.mx, gave me the magic formula toh create the above library:   # >     $ set def sys$common:[syslib]e! >     $ bliss/library starlet.reqa0 >     $ bliss/librar=lib.l32 starlet.req+lib.req  9 This works, just ignore the information messages you get.   J I've had other problems since then, though, in trying to rebuild MX 4.2 onH Alpha.  I noticed the admonition in ther readme file to build FLQ beforeN COMMON, so I started that way.  Doing a MMS in the [MX.FLQ] directory gave me:  D BLISS /OBJ=FLQ_OPEN.OBJ/TERM=STAT/NOLIST/NODEBUG/VAR="" FLQ_OPEN.B32A %DCL-W-IVKEYW, unrecognized keyword - check validity and spellingn  \STAT\pM %MMS-F-ABORT, For target FLQ_OPEN.OBJ, CLI returned abort status: %X00038060..A -CLI-W-IVKEYW, unrecognized keyword - check validity and spellingt  I I assume this is a minor problem and just removed the /TERM=STAT from theeI BFLAGS lines, then invoked MMS again.  This time, though, I got a slew ofd$ errors on the module FLQ_VECTOR.MAR:  0 MACRO /OBJ=FLQ_VECTOR.OBJ/NODEBUG FLQ_VECTOR.MAR           ROUTINE FLQ_OPEN ^h6 %AMAC-W-DIRTRANS, .TRANSFER directive is not supported- -MACRO-I-ATEXPLINE, at macro expansion line 3 9 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1f          .TRANSFER       FLQ_OPEN           ROUTINE FLQ_OPEN ^r1 %AMAC-E-DIRMASK, .MASK directive is not supportedn- -MACRO-I-ATEXPLINE, at macro expansion line 4 9 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1           .MASK           FLQ_OPEN           ROUTINE FLQ_OPEN ^v1 %AMAC-E-BLKEXPNABS, block expression not absolutea- -MACRO-I-ATEXPLINE, at macro expansion line 4 9 at line number 29 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1    [snip]         .END ^ ; %AMAC-E-PREVERROR, previous errors prevent further analysis-9 at line number 42 in file MX_SRC:[MX.FLQ]FLQ_VECTOR.MAR;1t    J I tried the above using the /MIGRATION qualifier and got the same results.  ' I checked the help file and found this:r   MACROd     /MIGRATION  -     Support_of_VAX_MACRO_Assembler_Directivesh  G          The compiler supports most of the standard VAX MACRO assemblersI          directives. However, the following directives that are supportedtH          by the VAX MACRO assembler do not make sense for compiled code.G          Consequently, the compiler flags them and continues execution.eG          You can disable the flagging of these directives by specifyingu          /NOFLAG=DIRECTIVES. [snip]          o  .TRANSFERo            o  .MASKx [snip]  M So it seems the directives really aren't needed for Alphas.  Does this mean IEI can change the FLQ's DESCRIP.MMS file to use /MIGRATION/NOFLAG=DIRECTIVESm= and just rerun MMS?  Or are the above messages really errors?e  
 Meanwhile:E >BLISS /OBJ=FLQ_OPEN.OBJ/TERM=STAT/NOLIST/NODEBUG/VAR="" FLQ_OPEN.B32nB >%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling > \STAT\N >%MMS-F-ABORT, For target FLQ_OPEN.OBJ, CLI returned abort status: %X00038060.B >-CLI-W-IVKEYW, unrecognized keyword - check validity and spelling  N I think I found the reason for this.  There's a macro __ALPHA__ that is testedM in the DESCRIP.MMS file for FLQ (and probably elsewhere as well).  The readme L file doesn't say anything about setting/defining this macro.  When I definedI it, though, using /MACRO=__ALPHA__=1, it didn't give me any errors.  As a N matter of fact, it didn't compile FLQ_VECTOR.MAR at all!  I used the following command$  @ MMS/MACRO=__ALPHA__=1/NOACTION/OUT=X./FROM/DESCRIP=DESCRIP.MMS;1  N to ensure the original makefile was used, to force all compilations to be doneH again (in case some were compiled incorrectly), and to get a list of theH commands that would be done.  The MACRO command doesn't even appear now!  N The problem I now have, though, is that the module FLQ_VECTOR.OBJ is listed inN the options file MX_FLQ_SHR.OPT which is specified on the LINK command.  SinceO I cleaned up the directory (ie, deleted old .OBJ files), and MACRO is no longer 5 invoked, LINK now fails due to a missing file. <sigh>   L I'll try compiling FLQ_VECTOR.MAR with the qualifiers I mentioned in my last/ post.  Meanwhile, what *is* the correct answer?a   Lawrence Bleau University of Maryland" Physics Dept., Space Physics Group 301-405-6223 bleau@umtof.umd.edu3   ------------------------------  % Date: Thu, 13 Jul 2000 05:52:23 +0200m2 From: martin@radiogaga.harz.de (Martin Vorlaender)2 Subject: Re: MX 4.2 won't rebuild, what's missing?; Message-ID: <396d3cf7.524144494f47414741@radiogaga.harz.de>s  + Lawrence Bleau (bleau@umtof.umd.edu) wrote:mF : The problem I now have, though, is that the module FLQ_VECTOR.OBJ isJ : listed in the options file MX_FLQ_SHR.OPT which is specified on the LINKJ : command.  Since I cleaned up the directory (ie, deleted old .OBJ files),G : and MACRO is no longer invoked, LINK now fails due to a missing file.  : <sigh>  A I haven't looked too deeply into the MX 4.2 source, but generallytG speaking: transfer vectors are a VAX construction - no need for them oneG Alphas. Are you sure that MX_FLQ_SHR.OPT isn't meant to be built by thew< description file (i.e. without including FLQ_VECTOR.OBJ whenH /MACRO=__ALPHA__=1)? If there's a "clean" target in the MMS file, please  use it instead of "DEL *.OBJ;*".   cu,a   Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.derN One OS to bring them all      |       http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  % Date: Wed, 12 Jul 2000 20:38:57 +0200l2 From: martin@radiogaga.harz.de (Martin Vorlaender) Subject: Re: MX Recordss; Message-ID: <396cbb41.524144494f47414741@radiogaga.harz.de>   & Horse Nuts (hx_101@hotmail.com) wrote:* : Where (disk and file) are these kept????   Which TCP/IP stack?c    These are part of the DNS files.  B In UCX/DEC^H^H^HCompaq TCP/IP Services: SYS$SPECIFIC:[UCX$BIND] or [TCPIP$BIND], respectively.e   In TCPware: TCPWARE_NAMED_ROOT:    cu,    Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.deyN One OS to bring them all      |       http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  % Date: Wed, 12 Jul 2000 21:36:20 -0400s2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>1 Subject: Re: Netscape Fasttrack for OpenVMS 7.2-1d7 Message-ID: <200007122136_MC2-AC17-C377@compuserve.com>=  E         Consider that the server may turn on a privilege only when it E actually needs to use it.  Enabling only the privileges needed at the 3 moment limits the damage a bug in your code can do!p  5 Message text written by INTERNET:pavichal@my-deja.com-B >My Fasttrack account has OPER,NETMBX,TMPMBX, SYSGBL and PRMGBL asC priviledges(recommended in the docs), however the process that runs F as the server only seems to have NETMBX and TMPMBX. Why doesn't it useB the others? Also, I set up an ACL and it works from an interactiveC login, but doesn't when you use it from Fasttrack(Non-interactive). C Why doesn't Fasttrack inherit the properties of its parent process?  <e   ------------------------------  % Date: Wed, 12 Jul 2000 14:03:35 -0400e- From: "Mitchell, David R." <mitchell@WPI.EDU>aP Subject: OpenVMS 7.2 backup bug? (was RE: Open-source Database system available)B Message-ID: <FE1835D68492D311BF7900508B5BEB0D0DE8AE@petra.WPI.EDU>  I I guess I must have missed this thread a while ago.  To quote from below:   F >  o VMS 7.2 BACKUP's "feature" of a "BACKUP/IMAGE without specifying = >    /NOALIAS" results in incomplete restoration operations. d > = >    IIRC, the last word on this was that Hoff and Andy were u > looking into   >    this apparent bug.r   From "help backup /alias" -s   BACKUP     /ALIAS  &         /ALIAS save-set-spec (default)         /NOALIAS        Command Qualifier  @      Specifies that the previous behavior of multiple processing@      of alias and primary file entries be maintained. The /ALIASA      qualifier maintains the previous BACKUP behavior of treatinguF      alias file entries the same as primary file entries. Therefore, aE      primary file may be processed multiple times by BACKUP if one ordC      more alias file entries reference the same primary file entry.h  B      If you specify /NOALIAS, alias directory and file entries areD      ignored. Therefore, multiple processing of primary files may beD      avoided, which saves time and save-set file space. If a restoreC      operation is performed using the /ALIAS qualifier but the savefB      set was created by using the /NOALIAS qualifier, a message is9      displayed that the /ALIAS qualifier will be ignored.e  J From the helpfile I didn't think I needed /noalias to do a proper restore.. Does anyone know the current status of this???   David      > -----Original Message-----' > From: LESLIE@209-16-45-102.insync.netk* > [mailto:LESLIE@209-16-45-102.insync.net]) > Sent: Wednesday, July 12, 2000 12:23 AM  > To: Info-VAX@Mvb.Saic.Como4 > Subject: Re: Open-source Database system available >  > < > Larry Kilgallen (Kilgallen@eisner.decus.org.nospam) wrote:@ > : In article <396A64A9.5B99AD27@merlin.arc.nasa.gov>, "Arthur  > E. Ragosta" ) > : <ragosta@merlin.arc.nasa.gov> writes:s > : C > : > In fact... what's to keep Compaq from porting it???       :-)r > :  > : 1. Bureaucracy.d# > : 2. Fear of antagonizing Oracle.l& > : 3. Fear of antagonizing Microsoft. > : 4. Priorities. > : F > : As usual, I think DEQ should stick to things that only they can do> > : (VMS, development tools, etc.) unless they have _lots_ of 
 > spare time.p@ > : Looking at features missing from VMS, I don't think that is  > the case.r > 9 > OTOH, look at the features that have met with howls of i > anguish on c.o.s:  > ) >  o The NT VMS System Management packagen > 
 >  o DECEvento >  >  o Compaq Analyze  > F >  o VMS 7.2 BACKUP's "feature" of a "BACKUP/IMAGE without specifying = >    /NOALIAS" results in incomplete restoration operations. c > = >    IIRC, the last word on this was that Hoff and Andy were   > looking into   >    this apparent bug.a > @ > Some of the talent used for the above mentioned efforts could  > have been  > better used elsewhere. >  > 1 > --Jerry Leslie   leslie@209-16-45-97.insync.net = >                  leslie@209-16-45-102.insync.net is invalids4 >                  (my opinions are strictly my own) >    ------------------------------  # Date: Wed, 12 Jul 2000 23:51:21 GMT ) From: "Neil Rieck" <n.rieck@sympatico.ca>fT Subject: Re: OpenVMS 7.2 backup bug? (was RE: Open-source Database system available); Message-ID: <Zv7b5.90133$HK2.1666845@news20.bellglobal.com>d  E I sent a note directly to Hoff with some data from some sample backupaI operations which always seem to trash "alias related" directories (on VAXoF only) no matter which switch is used. I believe that the good folks atJ Compaq are still looking into this. For more info you might wish to searchG for the phrase BACKUP or ALIAS at http://www.deja.com/group/comp.os.vms   H On a related topic, when all things are working properly it is my beliefL that the "NOALIAS" switch will result in only copy of a file being backed upD to tape rather than two (which can happen when an ALIAS directory isL pointing to a real directory). This would result in faster backup operationsK and would require less tape.I'm not sure what this means for "disk to disk"f backups.  
 Neil Rieck Kitchener/Waterloo/Cambridge,- Ontario, Canada.! http://www3.sympatico.ca/n.rieck/   8 "Mitchell, David R." <mitchell@WPI.EDU> wrote in message< news:FE1835D68492D311BF7900508B5BEB0D0DE8AE@petra.WPI.EDU...K > I guess I must have missed this thread a while ago.  To quote from below:r >eG > >  o VMS 7.2 BACKUP's "feature" of a "BACKUP/IMAGE without specifyings> > >    /NOALIAS" results in incomplete restoration operations. > > > > >    IIRC, the last word on this was that Hoff and Andy were > > looking into > >    this apparent bug.t >h > From "help backup /alias" -  >i > BACKUP >n
 >   /ALIAS >t( >         /ALIAS save-set-spec (default) >         /NOALIAS >  >      Command Qualifier > B >      Specifies that the previous behavior of multiple processingB >      of alias and primary file entries be maintained. The /ALIASC >      qualifier maintains the previous BACKUP behavior of treatingoH >      alias file entries the same as primary file entries. Therefore, aG >      primary file may be processed multiple times by BACKUP if one oreE >      more alias file entries reference the same primary file entry.  > D >      If you specify /NOALIAS, alias directory and file entries areF >      ignored. Therefore, multiple processing of primary files may beF >      avoided, which saves time and save-set file space. If a restoreE >      operation is performed using the /ALIAS qualifier but the savemD >      set was created by using the /NOALIAS qualifier, a message is; >      displayed that the /ALIAS qualifier will be ignored.  >uL > From the helpfile I didn't think I needed /noalias to do a proper restore.0 > Does anyone know the current status of this??? >  > David  >  >m > > -----Original Message-----) > > From: LESLIE@209-16-45-102.insync.net , > > [mailto:LESLIE@209-16-45-102.insync.net]+ > > Sent: Wednesday, July 12, 2000 12:23 AM  > > To: Info-VAX@Mvb.Saic.Comr6 > > Subject: Re: Open-source Database system available > >l > >t> > > Larry Kilgallen (Kilgallen@eisner.decus.org.nospam) wrote:A > > : In article <396A64A9.5B99AD27@merlin.arc.nasa.gov>, "Arthur  > > E. Ragosta"T+ > > : <ragosta@merlin.arc.nasa.gov> writes:a > > :-E > > : > In fact... what's to keep Compaq from porting it???       :-)  > > :@ > > : 1. Bureaucracy.o% > > : 2. Fear of antagonizing Oracle.l( > > : 3. Fear of antagonizing Microsoft. > > : 4. Priorities. > > :tH > > : As usual, I think DEQ should stick to things that only they can do? > > : (VMS, development tools, etc.) unless they have _lots_ ofW > > spare time.eA > > : Looking at features missing from VMS, I don't think that isr
 > > the case.A > >d: > > OTOH, look at the features that have met with howls of > > anguish on c.o.s:b > >l+ > >  o The NT VMS System Management packagem > >  > >  o DECEvente > >n > >  o Compaq Analyze  > >lG > >  o VMS 7.2 BACKUP's "feature" of a "BACKUP/IMAGE without specifyinga> > >    /NOALIAS" results in incomplete restoration operations. > > > > >    IIRC, the last word on this was that Hoff and Andy were > > looking into > >    this apparent bug.y > >fA > > Some of the talent used for the above mentioned efforts couldn
 > > have beeni > > better used elsewhere. > >4 > >f3 > > --Jerry Leslie   leslie@209-16-45-97.insync.netr? > >                  leslie@209-16-45-102.insync.net is invalida6 > >                  (my opinions are strictly my own) > >t >    ------------------------------  % Date: Wed, 12 Jul 2000 20:58:48 -0500r7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>g/ Subject: OVMS V7.2-1: Passwords Case-Sensitive? - Message-ID: <396D2258.3EC7B995@earthlink.net>   
 Hi, Folks,  H Ran into an interesting problem on a client site today. My boss upgradedG their Pathworks server from V7.1 of OVMS to V7.2-1 and V6.-something oft" Pathworks to Advanced Server V7.2.  D Now, they have an interesting problem. When attempting to log in viaD PowerTerm, they can't log in unless they have the shift-lock on when typing their password.   Anyone have any ideas?   --   David J. Dachtera  dba DJE Systems- http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Wed, 12 Jul 2000 22:02:19 -0500u) From: "John E. Malmberg" <wb8tyw@qsl.net>43 Subject: Re: OVMS V7.2-1: Passwords Case-Sensitive?n7 Message-ID: <0abd01bfec76$c83bedd0$020a0a0a@xile.realm>T  6 David J. Dachtera <djesys.nospam@earthlink.net> wrote:  J > Ran into an interesting problem on a client site today. My boss upgradedI > their Pathworks server from V7.1 of OVMS to V7.2-1 and V6.-something ofy$ > Pathworks to Advanced Server V7.2. > F > Now, they have an interesting problem. When attempting to log in viaF > PowerTerm, they can't log in unless they have the shift-lock on when > typing their password.  I Are they using External Authentication?  NT passwords are case sensitive.r   ------------------------------  % Date: Wed, 12 Jul 2000 22:11:22 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>r3 Subject: Re: OVMS V7.2-1: Passwords Case-Sensitive? - Message-ID: <396D335A.22F1DBC1@earthlink.net>o   "John E. Malmberg" wrote:  > 8 > David J. Dachtera <djesys.nospam@earthlink.net> wrote: > L > > Ran into an interesting problem on a client site today. My boss upgradedK > > their Pathworks server from V7.1 of OVMS to V7.2-1 and V6.-something ofE& > > Pathworks to Advanced Server V7.2. > >.H > > Now, they have an interesting problem. When attempting to log in viaH > > PowerTerm, they can't log in unless they have the shift-lock on when > > typing their password. > * > Are they using External Authentication?   H No, not to my knowledge. Remember - this change is (presumably) a resultG of the V7.2-1 upgrade. If that were the case, this would be an on-going * problem, before and after the upgrade, no?  " > NT passwords are case sensitive.  * Natch. Gotta emulate Eunuchs, after all...   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/l   ------------------------------  # Date: Thu, 13 Jul 2000 05:14:53 GMT ( From: Terry Kennedy <terry@gate.tmk.com>3 Subject: Re: OVMS V7.2-1: Passwords Case-Sensitive?n' Message-ID: <FxMEKt.C4F@spcuna.spc.edu>c  7 David J. Dachtera <djesys.nospam@earthlink.net> writes:FF > Now, they have an interesting problem. When attempting to log in viaF > PowerTerm, they can't log in unless they have the shift-lock on when > typing their password. >  > Anyone have any ideas?  I   I just checked on 7.2-1 here and alpha passwords aren't case-sensitive. K Of course, "shift lock" (as opposed to "caps lock") will also change thingsl like 2 to @...  - 	Terry Kennedy             http://www.tmk.comd5         terry@tmk.com             Jersey City, NJ USA    ------------------------------  # Date: Wed, 12 Jul 2000 17:52:11 GMTs4 From: LESLIE@209-16-45-102.insync.net (Jerry Leslie)$ Subject: Re: ppp dialup on VAX again) Message-ID: <ff2b5.1271$5L3.11004@insync>n  > Brian Schenkenberger, VAXman- (system@SendSpamHere.ORG) wrote:F : In article <396c993c@amhnt2.amherst.edu>, jlodom@amherst.edu writes: : >sN : >And to add to his question: Is it possible to use PPP on a Vaxstation 3100  : >running Multinet?G : >(And where would I find I good modem to connect to said Vaxstation?)r : >S : F : FWIW, if you're willing to spend a few $$$s (~$250), there are boxesF : with will do this for you.  One such unit is the 3com OfficeConnect E : 56K LAN modem.  This box automatically logs into the ISP and estab-BE : lishes a PPP connection.  The VAX, or Alpha, or any other box which-E : can speak the TCP/IP lingo, connects to the LAN modem via 10bT RJ45hG : connections on the LAN modem.  You can connect up to 4 devices to thedG : 3com LAN modem and it will provide DHCP service, NAT, and *on demand*rE : dialup to the ISP.  There are similar offerings from other mfg's, Ih2 : believe intel has one I've seen in catalogs too. : H : With such boxes you get a modem (V.90), hub, minimal routing features,G : NAT, DHCP server, and a slew of other little features like the on de-/< : mand connection with very little hassle and configuration. : G : BTW, I'm no 3com fan.  I've just had one of these units to play with.e :  : --M : VAXman- OpenVMS APE certification number: AAA-0001 VAXman(at)TMESIS(dot)COM   2 Here's the URL for the 56K LAN Modem's data sheet:  2   http://www.3com.com/products/dsheets/400397.html   56K LAN Modem   > I've got the ISDN equivalent, the OfficeConnect LAN Modem, and am well-pleased with it.    / --Jerry Leslie   leslie@209-16-45-97.insync.netO;                  leslie@209-16-45-102.insync.net is invalid.2                  (my opinions are strictly my own)   ------------------------------   Date: 12 Jul 2000 18:37:37 GMT# From: rifepe@langran.iem.csic.espam 0 Subject: Re: TCPIP remote node in audit security' Message-ID: <8kidth$15s$1@tejo.csic.es>d  ` In article <DvSa5.1249$5L3.10700@insync>, LESLIE@209-16-45-102.insync.net (Jerry Leslie) writes:% >rifepe@langran.iem.csic.espam wrote:: >: Hi, .+ >: We are running VMS 7.1 and and UCX V4.1. > >: We have detect several unsucelfull breaking probes througth@ >: the accounting and security log and we would like to find the> >: remote access node that is trying to enter in our computer.J >: The problem is they are using telnet and the name or addres is too long >: to be shown in the reports.C >: How can I read the full node name or ip address they are ussing?d >:   >: Ricardo Fernandez-Perea >: a >'F >The node name or ip address should appear in SYS$MANAGER:OPERATOR.LOGG >Search OPERATOR.LOG for "TELNET Login Request from Remote Host"; e.g.:  > ; >  %%%%%%%%%%%  OPCOM  11-JUL-2000 15:34:04.42  %%%%%%%%%%%c' >  Message from user INTERnet on SCCVXGVL >  TELNET Login Request from Remote Host: 209-16-45-98.insync.net Port: 1043 > B >You can use this site to track down who to email at the domain of >the offending node: > ' >  http://spamcop.net/hosttracker.shtmlm >  SpamCop - Host Tracker  >  > 0 >--Jerry Leslie   leslie@209-16-45-97.insync.net< >                 leslie@209-16-45-102.insync.net is invalid3 >                 (my opinions are strictly my own).   Thank you very much,  I That cover the problem for the security audit, but How I can do somethingaD equivalent for the accounting reports. I can see very easy from themE that someone has make a port scanning of my computer but I can't knowt from where.t   Thanks Ricardo Fernandez-Pereas   ------------------------------  % Date: Wed, 12 Jul 2000 16:45:29 -0400n2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>. Subject: template device cannot be allocated -7 Message-ID: <200007121645_MC2-AC14-2121@compuserve.com>   J         Why do you believe that "rdc0" is a CDROM drive?  The CDROM devic= es1 I am familiar with are DKxn (SCSI) or DQxn (IDE).   G         Try SHOW DEVICE /FULL RDC0 and, if you still think it's a CDROM  device, post the results.e  ' Message text written by "Thomas nilsen"-J >I'm trying to mount a CD using "mount /over=3Did /nolabel rdc0" but get = thed following error:  8 MOUNT-F-TEMPLATEDEV, template device cannot be allocated  J Anyone got any ideas as to what this can be and how to get the CD to moun= to
 properly?<   ------------------------------  % Date: Wed, 12 Jul 2000 21:30:22 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>t2 Subject: Re: template device cannot be allocated -- Message-ID: <396D29BE.9B32CA23@earthlink.net>    Thomas nilsen wrote: > K > I'm trying to mount a CD using "mount /over=id /nolabel rdc0" but get the  > following error: > : > MOUNT-F-TEMPLATEDEV, template device cannot be allocated > L > Anyone got any ideas as to what this can be and how to get the CD to mount > properly?b >  > Thomas  7 I can't image an OpenVMS DISK device with an RD prefix.   3 Are you sure it isn't DK-something or DQ-something?   . Try e-mailing me the output of these commands:    $ show device d/full/out=shd.lis  $ show device r/full/out=shr.lis  7 Remember to drop the .NOSPAM from the reply-to address.u -- a David J. Dachteraa dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Thu, 13 Jul 2000 05:27:46 GMTt+ From: mike_myers@bellsouth.net (Mike Myers)p* Subject: Re: VAX to DEC Cobol differences.6 Message-ID: <396d4f09.45651764@news.clt.bellsouth.net>  3 On Wed, 12 Jul 2000 09:07:05 -0700, Terry Marositesp  <TMarosites@unitedad.com> wrote: >II >I am migrating to an Alpha (dec Cobol) from a Vax .I just copied my codea 8< snipiL >             The program on the VAX accepted a variable with spaces as zero 8< snip  >rH >             On the VAX the display was performed on the Alpha was not. >e  D We went through this same migration about 5 years ago. I have found B behavior similar to what you describe. It seems that the VAX COBOLD was much more lenient in the handling of non-numeric data in numeric fields.t  ? I would have to say that the Alpha (DEC COBOL) behavior is more 
 *correct*.  ; The very most aggrivating behavior is what we have come to g> refer to as "branch random". The program stack dumps and gives@ a reason of "decimal invalid operand" however the line indicated2 may not have anything to do with the problem data.  F If you follow the flow with debug (what a tedious process) the programF flows fine until it encounters the invalid data. Then instead of stack? dumping right there contol seems to be transfered to some othercA part of the program. A few more lines of code are executed before-? the stack dump. You have to be watching real close to see where14 the branch occurs to identify the field(s) involved.  E We have several million lines running on Alpha now but still run intob one of these from time to time.a  
 Best of luck,l Mike     ------------------------------  % Date: Wed, 12 Jul 2000 16:34:52 -0400c2 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: VMS tuning wsdefault 7 Message-ID: <200007121635_MC2-AC14-2011@compuserve.com>t  J         I wouldn't adjust the working set at all until I had some evidenc= e & that it was the source of the problem!  H         Is your process paging heavily?  Are the page faults for "globalH valid" or "demand zero"?   Both are associated with image activation and. can't be avoided by increasing process quotas.  F         If your process is paging to the disk (page read I/O, and page/ write I/O)  then you need a larger working set.   J         If your paging is against the free or modified lists, you may nee= dCE more working set; this is an inexpensive (relatively) sort of paging.f  E         If your paging is due to image activation, you might considere3 installing the image if it's not already installed.o    ! Message text written by geraldine C > I have a tuning question for OpenVMS 7.1 running on an alpha box.t: We are experiencing what we think is slow performance whenD installing/linking Oracle RDBMS software on the machine.  When we do% this we are the only user on the box.i  G When monitoring the working set usage for the process that is doing the F install, it fluctuates wildly and furthermore goes below the wsdefaultG to almost to values of 200 to 300.  Why is this?  I thought a process'sc8 working set should NEVER go below the wsdefault setting.  ? Quotas have been jacked up really high to see if that makes anye6 difference and doesn't seem to.  Quotas are currently:   WSDEFAULT:  500000 WSQUOTA:    900000 WSEXTENT:   900000  8 Thanks in advance for any words of wisdom on this topic.   <h   ------------------------------  # Date: Wed, 12 Jul 2000 23:57:09 GMTo* From: walnut30@hotmail.com (Edwin Guillot)Q Subject: What graphics cards are supported by OpenVMS on a AlphaServer 400 4/233? - Message-ID: <396d0404.966214468@192.168.63.1>k  F I have just acquired an AlphaServer 400 4/233 (128MB RAM, 2GB disk, 8XB SCSI CD), and was wondering what video cards would be supported byF OpenVMS.  The current card installed is a ATI Mach64 PCI 2MB card, butB I would prefer a 4MB or higher card so I could get 24 bit color at< 1024x768 or higher. The machine currently has Windows NT 4.0F installed, but I plan to install OpenVMS so I can learn more about it.  E I have yet to find an answer to this question, despite looking in thetF FAQ's and Compaq's web site.  I would consider using another system as% an X terminal only as a last resort. h  B Is there a list of the X servers that OpenVMS comes with, so I canE determine if a better video card is an option?  My research indicatesl& that the ATI card would possibly work.   Edwin J. Guillot Jr.   ------------------------------  % Date: Wed, 12 Jul 2000 13:07:40 -0500i% From: Chris Scheers <asi@airmail.net>u Subject: Re: WTB: Microvax2000O Message-ID: <C8608BB974A10FB4.C2F52BA980852BEA.FCA18E8FFE65C802@lp.airnews.net>    Roy Omond wrote: > ( > "Brian Schenkenberger, VAXman-" wrote: > k > > In article <396C7D04.C59CEC3A@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:i > > >tK > > >By the way - I'm not sure just how "limited" VAXstation 4000 VLC might M > > >be. Depends what you want, I guess. VUPs wise, it's about the same as andH > > >8200. Single SCSI bus, SCSI-I only, 24 MB memory max. - better thanF > > >uVAX-2Ks where I believe the max. is 12 MB, but I could be wrong. > > M > > 14MB.  2MB are on the uV2K board.  You could then install optional memoryoL > > of 4MB or 12MB.  I have a 4MB uV2K memory board pinned to my wall with aL > > few other interesting of PCB 'artwork'.  I was debating on 'scanning' itK > > for interested parties to view on the web site but I have better things  > > that I need to do... > B > Mmm... if my memory serves correctly, there was some third-partyD > (maybe Camintonn ?) manufacturer who did 16 Mbyte boards (2 piggy-B > backed 8 Mbyte boards) for the uV2K.  The 2 Mbytes on-board were
 > ignored.  G If I haven't totaly succumbed to dain bramage, the 16MB option was made5 by Clearpoint.  C The problem with this option is that it required a different set ofiH system ROMs to make it work.  If you do find one of these memory boards,D the odds are that you won't find the ROMs, unless you find the whole VS2000.c  G ----------------------------------------------------------------------- $ Chris Scheers, Applied Synergy, Inc.  G 817-237-3360 (Voice)    817-237-3074 (Fax)    Internet: asi@airmail.net    ------------------------------  % Date: Wed, 12 Jul 2000 19:31:04 -0500e) From: "John E. Malmberg" <wb8tyw@qsl.net>. Subject: Re: WTB: Microvax20007 Message-ID: <0a4701bfec61$a6aece40$020a0a0a@xile.realm>n  = Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wroteh > F > Correct...  Not sure about the mfg though.  I didn't want to mentionF > the 3rd party boards.  I'd wager they're pretty had to come by these > days.a  J And some of the third party memory boards will not work with all revisions% of the VAX or VAXstation 2000 series.C  J I ended up soldering in an ECO on a third party memory board to compensate7 for a change in the way that the '2000 detected memory.r   -John  wb8tyw@qsl.network   ------------------------------   End of INFO-VAX 2000.388 ************************