1 INFO-VAX	Sun, 22 Oct 2000	Volume 2000 : Issue 591       Contents:B Re: Anybody else having bugchecks after installing recent patches? Re: Calling C++ from FORTRAN Re: Converting NT Alpha to VMS Re: Converting NT Alpha to VMS3 Re: Encompass Bylaw Ballot: THE ENVELOPE, PLEASE... ! End of life for SuperLAT products  Getting started with SAMBA Re: Getting started with SAMBA Handling oddball disks Re: Handling oddball disks Re: Handling oddball disks OpenVMS + CA Re: OpenVMS + CA Re: PDF under OpenVMS  Re: PF keys ' Re: Proliant DL 360 x Alphaserver DS10L  Re: Sun "uptime" belly laugher TCP/IP questions: Where?" Re: This list participants profile Re: User Guide for Vax (VMS) Re: Xemacs on OpenVMS ?  [DECW] Archive new mirror site  F ----------------------------------------------------------------------  % Date: Sun, 22 Oct 2000 07:44:32 +0100   From: Paul Sture <paul@sture.ch>K Subject: Re: Anybody else having bugchecks after installing recent patches? + Message-ID: <VA.00000119.04e77380@sture.ch>   @ In article <39EB7804.8DA7B3C9@oracle.com>, Norm lastovica wrote:4 > From: norm lastovica <norman.lastovica@oracle.com> > Newsgroups: comp.os.vms M > Subject: Re: Anybody else having bugchecks after installing recent patches? ' > Date: Mon, 16 Oct 2000 17:49:56 -0400  > 9 > I understand that this is a (somewhat minor) bug in the < > SHOW SYSTEM command.  The UIC was moved from one structure9 > to another but not all the code learned about.  Nothing + > to get too concerned about in most cases.  >  > Bruce Vinson wrote:  > > ( > > Didn't notice that before. Not good! > > 	 > > Bruce  > >  > > Peter Weaver wrote:  > > > @ > > > "Bruce Vinson" <r4887c@email.sps.mot.com> wrote in message1 > > > news:39E7201E.80E84AAF@email.sps.mot.com... P > > > > I can't help with the problem, but we are running a cluster of ES40's onL > > > > VMS 7.2-1 with those ECOs installed, and have not seen any problems, > > > > bugchecks or otherwise.  > > > N > > > Try doing a SHOW SYSTEM/FULL and see if every uic shows as [0,0]. If youK > > > remove DEC AXPVMS VMS721_SYS V6.0 then the UIC will be correct again.  > P Oops! The problem with every uic showing as [0,0] is also in V7.2-1H1, and I am * told, also in the V7.3 field test release.  Q So far the impact is limited to one of my monitoring programs, which is claiming  O that SWAPPER doesn't exist (because it doesn't see it with a uic of [SYSTEM]),  O but I would dearly like to know if there are other problems I should watch out   for. ___ 
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 22 Oct 2000 19:50:29 +0010 % From: paddy.o'brien@zzz.tg.nsw.gov.au % Subject: Re: Calling C++ from FORTRAN 5 Message-ID: <01JVNEFXHNAA005NZL@tgmail.tg.nsw.gov.au>    Earl,   1 >Has anyone tried to instantiate a C++ Class from 2 >FORTRAN, I would be interested. Also  calling the- >methods or accessing the properties as well. , >Even if this required calling a C++ stub to- >instantiate the object and call the methods.  > - >I guess one would have to use CXLINK to link  >the program as well.  > , >I examined the FORTRAN manual and it seemed6 >a bit brief referencing the OpenVMS calling standard. > 0 >I have been successful calling FORTRAN routines- >from C++.  (E.g., creating a C++ wrapper and - >then calling old FORTRAN modules to actually  >implement the method).    I agree with David's comments.  M I would also suggest that if you are serious in this endeavour that you post  N this to comp.lang.fortran.  I do not use C++ and am not a devotee of OO so do P not have the URL, but I do remember that Carsten Arnholm has done a lot of work Q on linking Fortran and C++.  You would probably find his page from a web search,  = and I am fairly certain that I have spelt his name correctly.   I There is also a site (Russia?) where they have imitated OO in Fortran 90.   M If you can wait a few years :-), then (sadly, from my viewpoint) all this OO   stuff will be in Fortran.   O ["Sadly" -- yeah, for those who want it, use one of the several languages that  Q profess to have OO.  Don't burden every language with a passing fad and make the  H language and compiler cumbersome for the normal usage of that language.]   Regards, Paddy   Paddy O'Brien, Transmission Development, 
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, Australia    Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people, ; but that little whizz-bang apostrophe gives me little spam.    ------------------------------  % Date: Sun, 22 Oct 2000 19:30:41 +0010 % From: paddy.o'brien@zzz.tg.nsw.gov.au ' Subject: Re: Converting NT Alpha to VMS 5 Message-ID: <01JVNDQEPLXE005MZL@tgmail.tg.nsw.gov.au>    Brian,  P >I have an Alpha 4100 server currently running NT that I plan to convert to VMS.O > I was wondering if anyone could point me to any documentation on this topic.  N >I've been through a number of VMS installs over the years, but didn't know ifP >there were any required steps given this NT to VMS transition.  (I assume there >are.)  K Regretfully I cannot help you -- I've never run NT or windows except under  6 sufferance to read some of the "word" stuff I am sent.  I I certainly hope you get some advice, 'cos it's guys like you we need :-)    Regards, Paddy   Paddy O'Brien, Transmission Development, 
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, Australia    Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people, ; but that little whizz-bang apostrophe gives me little spam.    ------------------------------  % Date: Sun, 22 Oct 2000 13:47:39 -0400 - From: "Island Computers" <sales@islandco.com> ' Subject: Re: Converting NT Alpha to VMS / Message-ID: <sv69l58oqtbi16@corp.supernews.com>    Converting:   I 1) Get rid of any Adaptec based controller in the setupo and replace with K appropriate equivelent Qlogic and/or Symbios (NCR) chipset based controller   H 2) IF an IDE/ATAPI CD-ROM is installed, then replace with Toshiba 12x or higher SCSI CD-ROM  K 3) Video cards - if you have a Matrox, ATI card, then replace with S3Trio64  based card or ELSA/Permedia 2   D 4) Change AlphaBIOS startup to SRM - at ARC/AlphaBIOS go to F2, thenL 6  -scroll down to OS Type and choose between NT VMS And UNIX - make sure to hit F10 before escaping   9 VMS is more touchy with Video and SCSI than anything else A I wouldn't ever suggest using IDE even if your system supports it    David     . "BrianNFO" <briannfo@aol.com> wrote in message4 news:20001020170322.23228.00001193@ng-ch1.aol.com...L | I have an Alpha 4100 server currently running NT that I plan to convert to VMS.H |  I was wondering if anyone could point me to any documentation on this topic.L | I've been through a number of VMS installs over the years, but didn't know ifK | there were any required steps given this NT to VMS transition.  (I assume  there  | are.)  | 	 | Thanks.  |  | Brian    ------------------------------    Date: 22 Oct 2000 09:54:37 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) < Subject: Re: Encompass Bylaw Ballot: THE ENVELOPE, PLEASE...+ Message-ID: <91Dr9AIoWxaJ@eisner.decus.org>   [ In article <8stgfu$p6h$1@slb3.atl.mindspring.net>, "Jeff Killeen" <Jeff@IDM-IO.com> writes:   ? >>So vote "No" !  The Board of Directors has gone out on a limb ? >>and claimed that what they passed is acceptable. If they have @ >>failed in that regard, the only honest response is to vote No. > K > If you choose to vote no please do so on informed basis with knowledge of I > what will happen if this rejected.  The Board voted this through not as M > referendum of whether these are prefect by-laws but instead a needed action K > to continue to deliver the products and services of the User Group at the  > national level.  > I > The burden of proof ought to be on the those opposed to demonstrate why  > these by-laws are flawed.   ? No, my point in the (unattributed) comment above is that anyone A who feels the proposal is unacceptably flawed, for whatever their @ own reason might be, should vote "No" rather than abstain.  They? have no duty to prove anything to anyone other than themselves.    ------------------------------  # Date: Sun, 22 Oct 2000 16:04:05 GMT & From: johnson_meridian_com@my-deja.com* Subject: End of life for SuperLAT products) Message-ID: <8sv35k$5k9$1@nnrp1.deja.com>   > The following announcement has been emailed to recent SuperLATC customers.  I no longer follow this newsgroup, so existing SuperLAT C customers who have questions should use the email addresses in this A notice or other standard channels to contact Meridian Technology.    Ken Johnson  Meridian Technology Corporation   C =================================================================== = We regret to inform you that Meridian sales, distribution and C technical and warranty support of SuperLAT for Windows NT, SuperLAT B for Windows 95, and SuperLAT Gateway will be discontinued as of 31 December 2000.  C We will not be able to provide technical support for these products C after 31 December 2000.  We suggest you visit the technical support  download area of our website= (http://www.meridian.com/DownloadSL.html) and read any of the > material there which may pertain to your usage of the product.  C Effective immediately, Meridian modifies its license grant for your < use of SuperLAT for Windows NT, SuperLAT for Windows 95, andA SuperLAT Gateway as follows: You may use SuperLAT for Windows NT, 9 SuperLAT for Windows 95, or SuperLAT Gateway software and D documentation on multiple CPUs.  You may make copies of the softwareB in machine readable form for use on multiple CPUs. All other terms? and conditions of the Software License agreement remain in full  force and effect.   A Meridian can make source code for SuperLAT available to those who D want to provide their own technical support.  Access to the SuperLATB source code, however, requires a Cabletron LAT Technology license.< Inquiries about SuperLAT source and LAT Technology licensing7 arrangements should be directed to uphoff@meridian.com.   A Please send any other inquries to johnson@meridian.com, including < requests for license key files needed to use the products on5 multiple systems as described in the third paragraph.   C ===================================================================     & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Sun, 22 Oct 2000 07:44:31 +0100   From: Paul Sture <paul@sture.ch># Subject: Getting started with SAMBA + Message-ID: <VA.00000118.04e7718b@sture.ch>   - I've just installed Samba on my VAX (VMS 7.2)   G I've read John Malmberg's FAQ, posted here recently (thanks John), but  6 still can't get a connection from my NT 4.0 (SP6) box.   My questions are:   G 1. The LOG.ntbox file complains that "Username PCFS$ACCOUNT is invalid  ? on this system". Do I need to create this account? If so, what  F privileges / uic etc should I use? I was thinking of delving into the D Pathworks kitinstal to see how _that_ creates it, but firstly, do I  really need it?   E 2. How do I create the smbpasswd file? The above logfile complains:   ( "startsmbfilepwent: unable to open file " /samba_root/private/smbpasswd.dat"  ? 3. How would I add a user to the smbpasswd file? On linux, the  F smbpasswd has -a to add a new user. The VMS version doesn't appear to  have this switch.   C Having added the NT registry entry to enable plain text passwords,  F instead of getting "invalid user", I am now getting "network path not E found" (my messages are in German, so I can't give the exact English  D text). This may be a red herring, since I haven't got the smbpasswd 
 sorted yet...   F PS I am quite willing to write some documentation on all this, once I  get it working...  ___ 
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 22 Oct 2000 09:32:02 -0500 ) From: "John E. Malmberg" <wb8tyw@qsl.net> ' Subject: Re: Getting started with SAMBA / Message-ID: <sv5uesarmu5q01@corp.supernews.com>   - "Paul Sture" <paul@sture.ch> wrote in message % news:VA.00000118.04e7718b@sture.ch... / > I've just installed Samba on my VAX (VMS 7.2)    What version of SAMBA for VMS?  L I am assuming that you are using the pre-built binaries.  If not, welcome to# the world of building SAMBA on VMS.   H > I've read John Malmberg's FAQ, posted here recently (thanks John), but8 > still can't get a connection from my NT 4.0 (SP6) box.  G Microsoft recommends that SP6 not be used.  Use SP6a instead.  Read the E release notes or other documentation on SP6a as to what they changed.   ' It may or may not affect your problems.    > My questions are:  > H > 1. The LOG.ntbox file complains that "Username PCFS$ACCOUNT is invalid@ > on this system". Do I need to create this account? If so, whatG > privileges / uic etc should I use? I was thinking of delving into the E > Pathworks kitinstal to see how _that_ creates it, but firstly, do I  > really need it?   L For some reason SAMBA is interpreting the first part of a connection attemptL from an NT system as logging in as GUEST, and as such needs a Guest account.L For SAMBA-VMS 2.0.3 and earlier I think the code is trying to use UCX$NOBODY5 by default, but this could be overridden in smb.conf.   G This account must exist, and have a default directory that it can write K into.  The password does not matter, so you can set a random string for it.   J For the SAMBA 2.0.6 version that I am packaging up, the guest account will< default to SAMBA__GUEST.  (Note two underscores in the name)  E > 2. How do I create the smbpasswd file? The above logfile complains: ) > "startsmbfilepwent: unable to open file $ > /samba_root/private/smbpasswd.dat"  K As I am not running any of the released binaries, I do not know why you are A getting the message, or if it is something to be concerned about.   J The older SMBD for VMS have the section of the code that actually looks upL the code removed from compilation as there was no file locking available via fcntl().  L Since the SAMBA password database code just uses fcntl() to exclusively lockI the first byte of the file, if you choose to rebuild that version to just I use the default VMS behavior, and have fcntl() return a success it should  work just fine.   @ > 3. How would I add a user to the smbpasswd file? On linux, theG > smbpasswd has -a to add a new user. The VMS version doesn't appear to  > have this switch.   I The SMBD program can not use the smbpasswd file even if you find a way to , populate it.  So for now the answer is moot.  D > Having added the NT registry entry to enable plain text passwords,G > instead of getting "invalid user", I am now getting "network path not F > found" (my messages are in German, so I can't give the exact EnglishE > text). This may be a red herring, since I haven't got the smbpasswd  > sorted yet...   K I would suspect it has more to do with the VMS account that SAMBA is trying & to use as a GUEST account not working.  G > PS I am quite willing to write some documentation on all this, once I  > get it working...    Good.   E I am really trying to move fast on SAMBA 2.0.6, but I do not have the F transfer vectors built for the shared images yet for VAX, or coded the* SAMBA.MMS file I am using to build on VAX.  L This will not help you with your present version, but have you looked at theL FRONTPORT UNIX to VMS porting library?  It will be needed for my SAMBA 2.0.69 release and both VAX and ALPHA binaries are available at:   -  http://eisner.decus.org/~malmberg/frontport/   G The code has mostly been tested on OpenVMS ALPHA 7.2.  The VAX binaries L where built on OpenVMS VAX 7.1, and I have not tested the install on OpenVMS VAX 7.1.   -John  wb8tyw@qsl.network   ------------------------------  % Date: Sun, 22 Oct 2000 09:38:50 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: Handling oddball disks 7 Message-ID: <200010220939_MC2-B7F6-45A1@compuserve.com>   C         Obviously DKDRIVER doesn't support it, but doesn't the SCSI J protocol support "negotiation" so that rather than doing it by "ID string= "X@ and table lookup the driver could ask the device "do you supportC disconnect", "do you support TCQ", "do you support SYNC mode", etc?l  J         If that were done, instead of "I'm not going to talk to this devi= ceJ and why is none of your business", the driver could say "VMS requires "X"=   and this device doesn't do "X".i  H         It would also mean that VMS could work with any disk device thatD complies with the SCSI standard and support all the features of thatJ device; e.g. VMS Engineering would not need to rebuild the driver and its=  $ table for each new supported device.  J         Compaq would obviously not support random brand X devices but tho= se that could work would work.p  + Message text written by "Glenn C. Everhart"- > =-  G I have been getting some oddball SCSI disk brands now and then and have2
 found thatC they worked erratically. Concluding that this was likely due to they drive not doinghG tagged queueing right, I tried using scsi_mode to set offset 03 of page@ 0a to 1 ? to disable it. Woe is me. My 3000-300LX box doesn't seem to runt scsi_mode correctlyo (for whatever reaason).a  C So I decided it made more sense to arrange that dkdriver should notg
 attempt toH do tagged queueing on "generic" disks (i.e., the pc junk I was trying to use).   6 This might be of wider interest so here goes with how.  E The following macro defines device characteristics found in dkdriver.rG The device ID is the identifier returned on INQUIRY, which is generallyo what shows up in the  
 >>>SHO DEV  ? display as the device name. This is how a device is recognized.   = The table of specific device types can be located easily in an: copy of sys$dkdriver.exe by looking for ASCII strings like RZ23, RZ57, etc. <a   <snip>   ------------------------------  % Date: Sun, 22 Oct 2000 10:00:37 -0400e0 From: Glenn and Mary Everhart <Everhart@gce.com># Subject: Re: Handling oddball disksl' Message-ID: <39F2F305.C11B1DF7@gce.com>   9 "Obviously DKdriver DOESN'T support it"????? WRONG!!!!!!!   < DKdriver has negotiated this stuff for years. You just don't> appreciate how flaky are the "SCSI" implementations out there.  > Yes, dkdriver does negotiate. Problem is that some disk drives@ don't support tagged queueing (tcq) properly, so their responses= have to be ignored. Similar issues with disconnect exist. TheS> devices claim these work, and under some circumstances they doI sorta work. However that doesn't mean they work with all SCSI controllershC and when they don't the result is usually flaky performance if they- work at all.  C That is why there are features in dkdriver to allow it to recognize.F lying devices and to work with them anyway. It is not however feasibleE to test 30 zillion disk drives with dkdriver and with every scsi porto driver variant out there.   J Alcita's board works perfectly with Adaptec controllers on PC. On anythingM else it seems there are tweaks needed. The disk drives I patched for tcq weretG generic drives. I don't know what the exact problems were, just observeeG that non-tcq operation is reliable with them, tcq not. There used to beuL a problem, which may still exist, that some tcq implementations only allowedN queue tags in the 0-63 range. There is no such limitation in the scsi standardD and VMS uses tags in the 0-255 range. SCSI only says they have to beI unique. To get around the fact that the drive won't understand 75% of thee, legal tag range you turn off tcq with those.  H The problem is that a large chunk of devices out there are built to workE on PCs with very often one adapter vendor and assuming no DMA access,nD have drivers written to work around any nonstandard issues, and just- never bother to get SCSI all that much right.     I DKdriver does NOT say "I'm not going to work with you" or any such thing.iJ I am appalled at someone bringing these kinds of remarks up after all thisI time, and all the work that I and others did to try to handle some of thebL bizarre stuff that is done. The generic driver handling uses the negotiationL unless you specifically tweak it to disable something or to force variationsJ that get around the odd problems some devices have. Most of the SCSI tableK is there for one purpose: to get the device name right in show device. ThatvH it can be tweaked for oddball devices is a bonus. It has not been shrunkH massively (now that inquiry strings are used directly) due to historicalJ inertia. Just check out that almost all the entries are the same and allow everything.   M Please, all, don't spread the rumor that dkdriver "only" works with a limited-K set of known disks. It works VERY HARD to work with any scsi disk. That you.G can tweak some tables and get it to work differently with the el cheaposK disk you got at a pc show (or that I can) is a plus...but is needed only ifp8 said disk's SCSI IQ puts it in the drooling idiot class.   Glenn C. Everhartd everhart@gce.com     "Richard B. Gilbert" wrote:  > E >         Obviously DKDRIVER doesn't support it, but doesn't the SCSIsL > protocol support "negotiation" so that rather than doing it by "ID string"B > and table lookup the driver could ask the device "do you supportE > disconnect", "do you support TCQ", "do you support SYNC mode", etc?f > M >         If that were done, instead of "I'm not going to talk to this devicesK > and why is none of your business", the driver could say "VMS requires "X"l! > and this device doesn't do "X".  > J >         It would also mean that VMS could work with any disk device thatF > complies with the SCSI standard and support all the features of thatK > device; e.g. VMS Engineering would not need to rebuild the driver and itsz& > table for each new supported device. > M >         Compaq would obviously not support random brand X devices but those  > that could work would work.d > - > Message text written by "Glenn C. Everhart"  > >gI > I have been getting some oddball SCSI disk brands now and then and have  > found thatE > they worked erratically. Concluding that this was likely due to theQ > drive not doingsI > tagged queueing right, I tried using scsi_mode to set offset 03 of page 	 > 0a to 1eA > to disable it. Woe is me. My 3000-300LX box doesn't seem to run  > scsi_mode correctly, > (for whatever reaason).  > E > So I decided it made more sense to arrange that dkdriver should not  > attempt toJ > do tagged queueing on "generic" disks (i.e., the pc junk I was trying to > use).s > 8 > This might be of wider interest so here goes with how. > G > The following macro defines device characteristics found in dkdriver.oI > The device ID is the identifier returned on INQUIRY, which is generallyn > what shows up in the >  > >>>SHO DEV > A > display as the device name. This is how a device is recognized.T > ? > The table of specific device types can be located easily in ap< > copy of sys$dkdriver.exe by looking for ASCII strings like > RZ23, RZ57, etc. > <l >  > <snip>   ------------------------------  % Date: Sun, 22 Oct 2000 10:53:06 -0500V7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>s# Subject: Re: Handling oddball disks-- Message-ID: <39F30D62.EC4A5FB2@earthlink.net>0   Glenn and Mary Everhart wrote: [snip] LO > Please, all, don't spread the rumor that dkdriver "only" works with a limitede > set of known disks.@  D That's really just a "perception at large". DKDRIVER may actually doG better than that. However, "If that light's under a bushel, BRRRR! It's   lost something kind of crucial!"  9 > It works VERY HARD to work with any scsi disk. That youyI > can tweak some tables and get it to work differently with the el cheapo M > disk you got at a pc show (or that I can) is a plus...but is needed only if : > said disk's SCSI IQ puts it in the drooling idiot class.  ? Which I guess begs the question: can DKDRIVER (or some suitableuG substitute) be made to work such that if the target device doesn't meetvG the (a,b,c,...,x,y,z) criteria, it will use some generally operable butr; (much!) less than optimal "lowest common denominator" mode?h  E When we are pitting OpenVMS against the opposition, these SCSI issueso7 are frequently our weakest "Achilles's(sp? usg?) Heel".y   -- , David J. Dachtera  dba DJE Systemst http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/-  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.L   ------------------------------  % Date: Sun, 22 Oct 2000 05:42:52 -0200u) From: fabio_compaq@ep-bc.petrobras.com.brm Subject: OpenVMS + CA L Message-ID: <OF5BFADBC8.431DD549-ON83256980.002A3ED5@ep-bc.petrobras.com.br>  H CA has a good homepage about OpenVMS ! You should check  because it=B4s=  a rarity nowadays ! ! !=    . http://www.cai.com/solutions/platform/openvms/   =r   ------------------------------  % Date: Sun, 22 Oct 2000 11:13:38 -0500p7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>o Subject: Re: OpenVMS + CA2- Message-ID: <39F31232.2A3DDE01@earthlink.net>l  * fabio_compaq@ep-bc.petrobras.com.br wrote: > I > CA has a good homepage about OpenVMS ! You should check  because its ai > rarity nowadays ! ! !c > 0 > http://www.cai.com/solutions/platform/openvms/   Umm, Fabio?r  F Since you're (by your own admission) new to this newsgroup I'll try to  state this as calmly as I can...  , CA is, IMHO, a pile of fetid(sp?), stinking % %CENSOR-E-OBSCENE, obscenity detectedw -CENSOR-I-SUBSTITUTE, "refuse" w9 not to mention a batch of thieving, profit-mongering, ...r  # Well, so much for a calm statement.   G The long and short of it is that CA falls into the category of "personau6 non grata" or (somewhat loosely) "person not wanted".    One example of why:r   <rant>C They were sold certain elements of the Polycenter system managementTB suite by Digital and promptly jacked the prices up to where no oneF except the largest sites could afford them. This didn't bother many ofB us until the OVMS V7.1 upgrade "broke" the great bulk of it and itF stopped working. So, now, at V7.2 and later, we're again searching forG suitable system management automation software at a non-usurious price.  </rant>f  B Many sites keep a V6.2 VAX/Alpha system around on which to run (atF least) PCM (Polycenter Console Manager) so that piece remains stagnantH but usable. Some third party software has recently appeared to fill that@ gap, however, and some sites are moving to it rather than keep a8 back-rev'd system around dedicated to a single function.   -- c David J. Dachterag dba DJE SystemsB http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/l  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.?   ------------------------------  # Date: Sun, 22 Oct 2000 13:23:30 GMTi= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)  Subject: Re: PDF under OpenVMS0 Message-ID: <009F1F92.347BDD10@SendSpamHere.ORG>  _ In article <G2tFwL.3s@world.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes:w >In article <60333E9D00AE31E8.237882F2CA4681FE.216FA30F2142BBFB@lp.airnews.net>, Chris Scheers <chris@applied-synergy.com> writes:I >> As I understand it, Display Postscript on VMS has been unsupported for H >> some time, but if it was already installed, it would be left in place  >> during previous VMS upgrades. >>C >> This changes with VMS 7.3, which will remove Display Postscript.. >iG >Is it possible to "squirrel away" certain files and restore them after * >the upgrade to retain Display Postscript?  < The E7.3 DECW server did seem to activate the DPS extension:  : Activating extension image DECW$SVEXT_Adobe_DPS_Extension,; extension name: Adobe-DPS-Extension, entry address 00323DE0b  C However, a bug in the CDA viewer kept me from testing it.  I didn'ts2 try pulling the older CDA viewer over to E7.3 yet.  A Let's hope the "stubs" remain so we can continue to use the older. DPS extension files.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMy            tO city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------   Date: 22 Oct 2000 15:31:27 GMT/ From: Thomas Dickey <dickey@saltmine.radix.net>  Subject: Re: PF keys* Message-ID: <8sv18f$4vq$1@news1.Radix.Net>  $ Tom DeLuca <tomdel@erols.com> wrote:3 > Xterm is good but how to emulate the VT keyboard?d  K some people use xterm's translation resource to modify the keyboard to make.I it more VT100-like. XFree86 xterm does this by builtin tables (can switchtC from a PC-style to a vt220-style keyboard by a popup-menu setting).g  9 The XFree86 xterm supports ANSI color and VT220 emulation  There's an faq ats+ 	http://dickey.his.com/xterm/xterm.faq.html, 	ftp://dickey.his.com/xterm    > -- > Tom DeLuca& > Mgr. Computer Operations - Radiology > Johns Hopkins Hospital > tdeluca@jhmi.edu    ; > "Bob Koehler" <koehler@eisner.decus.org> wrote in message.' > news:MjscmcioKI9t@eisner.decus.org...tK >> In article <39DBA6B1.C3FAFECC@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?=h" > <arne.vajhoej@gtech.com> writes: >> >/ >> > Unix telnet ? That may be more difficult !  >>G >> Generally when coming from UNIX I find it best to start xterm.  That.H >> requires X, but it does a useable job of VT100 emulation and it seems >> to always be there. >>I >> ----------------------------------------------------------------------iB >> Bob Koehler                     | Computer Sciences Corporation@ >> Hubble Space Telescope Payload  | Federal Sector, Civil GroupH >>  Flight Software Team           | please remove ".aspm" when replying       -- g= Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>t http://dickey.his.comt ftp://dickey.his.com   ------------------------------  % Date: Sun, 22 Oct 2000 06:34:43 +0100t  From: Paul Sture <paul@sture.ch>0 Subject: Re: Proliant DL 360 x Alphaserver DS10L+ Message-ID: <VA.00000115.04a788b7@sture.ch>o  N In article <39f144a0.524144494f47414741@radiogaga.harz.de>, Martin Vorlaender  wrote:4 > From: martin@radiogaga.harz.de (Martin Vorlaender) > Newsgroups: comp.os.vmsd3 > Subject: Re: Proliant DL 360 x Alphaserver DS10L  ' > Date: Sat, 21 Oct 2000 09:24:16 +0200  > # > John Santos (JOHN@egh.com) wrote:c' > : On 19 Oct 2000, Hoff Hoffman wrote: L > : >   But realize that anything that is available now is already outdated. > :NI > : Dave Barry once proposed that all computer stores should have a largeaH > : trash barrel at the end of each check-out counter so you could slideH > : your brand-new (i.e. obsolete) computer directly into the trash with9 > : ever having to actually pick it up and bring it home.  > D > Somewhere, somewhen I read a proposition to not call it "new" when; > talking about computers, but "obsolete ready" instead :-)u > O I don't have the exact text handy, but I recall something which went like this:   3 Legacy:                We've fixed most of the bugs6d Mature:                We know what the bugs are; those we haven't fixed, we                        % have workarounds for, if you're lucky A Proven:                Slow as molasses. We know most of the bugsoI State of the Art:      Yesterday's technology; still lots of bugs to findy5 Latest Technology:     We haven't got it working yet.r8 Tomorrow's Technology: It's not on the drawing board yet   ___ 
 Paul Sture Switzerlande   ------------------------------  % Date: Sun, 22 Oct 2000 12:12:27 +0200V" From: "Hans Vlems" <hvlems@iae.nl>' Subject: Re: Sun "uptime" belly laughert( Message-ID: <8sue0v$t3s$1@news.IAEhv.nl>  E At Fuji the up time record is a little over 1000 days, for a two noder
 8250/HSC50 CIu cluster running VMS 5.3 (!).( OTOH why was everything ported to Linux?  
 Hans Vlems  ) (who *never* installs patches at home...)R  & Jim Jennis heeft geschreven in bericht; <3.0.5.32.20001020151447.00a0dbc0@discovery.fuentez.com>... K >I second Peter's comments. (both on Andrew's posts and VMS reliability). IsK >handled similar responsibilities at a very large manufacturing division of I >3M Corp. We had VMS,Sun,HP-UX,MPE/ix,NT. Our VMS cluster had less than 8=K >hours of unscheduled downtime over a 5 year period from Sept. 1994 throughXF >May 2000. NONE OF THE OTHER PLATFORMS COULD EVEN COME CLOSE. The onlyI >reason why VMS went down in May of 2000 was when we ported everything to " >Linux and I was forced to execute >e >@sys$system:shutdowni >w >on the cluster. >i	 >Regards,e >n >Jim > ) >At 02:26 PM 10/20/2000 -0400, you wrote:  >>? >>"andrew harrison" <andrew.nospam@uk.sun.com> wrote in message=& >>news:39F06A69.C6FE3B6F@uk.sun.com... >>>...> >>> Seems to me that Sun "uptime" belly laughs could easily be@ >>> applied to OpenVMS as well. And that Rob's FUD could equally( >>> be described as OpenVMS botty burps. >>>a@ >>> BTW the tread is called "Anybody else having bugchecks after >>installing >>> recent patches?"9 >>> which is pretty difficult to miss though I assume youL; >>> must have from your confident attempt to FUD Sun's witheA >>> some kind of OpenVMS/Sun relative number of patches argument.r >>>s> >>> P.S This isn't an attempt to compare OpenVMS and Sun patch> >>> quality just a suggestion that you are ill advised to fall; >>> into the normal OpenVMS advocate trap of throwing rocksi >>> in your own glass house. >>E >>I try to avoid Andrew's posts, but as someone who has posted in theh? >>thread "Anybody else having bugchecks after installing recentt% >>patches?" I feel a need to jump in.  >>E >>In a previous life I was a Data Centre (yes Andrew, Canadians spell H >>Centre the same way you do) Manager and had responsibility for Sun, HPD >>UX, VAX/VMS, AXP/VMS and Fujitsu MVS equipment. McNealy's commentsH >>about uptime did give me a good belly laugh. None of the other systemsD >>could compete with our VMS systems for uptime. When we did have toE >>take a VMS system down we had to explain to everyone the reason and!D >>really justify it because everyone expected VMS to be there. EveryH >>time one of the other systems went down, or we had to take one down toC >>apply a patch to keep it from stopping, no one cared because theya/ >>expected those systems to just go away often.  >>F >>Give me a rock and I'll throw it at any SUN, HP or Fujitsu box I canG >>find. We VMS bigots don't live in glass houses, we have a few windowshD >>made of Plexiglas around but we seldom hit them and when we do the >>rocks usually bounce back. >> >> >>Peter Weaver >>$ input = H >>"14E64627567702963702F6E636560216761696E6023786F67796E676028696370265DH >>4350256E66797C202865672C6C6020727F6261626C69702861667560247F602465636F >>6465602478D >>6963702F6E6028696370286F6D6560284F62626979637470265D4350226F687E2"	 >>$ i = 0  >>$loop:) >>$ output[i*4,4]=%X'F$EXTRACT(i,1,input)l
 >>$ i = i + 1n  >>$ if i .lt. 214 then goto loop; >>$ write sys$output "Today's secret message is: " + output  >> >> >>9 >--------------------------------------------------------n8 >FSC - Building Better Information Technology Solutions-8 >      from the Production Floor to the Customer's Door.9 >-------------------------------------------------------- 6 >Jim Jennis, Technical Director for Commercial Systems >Fuentez Systems Concepts, Inc.C >1 Discovery Place, Suite 2  >Martinsburg, WV. 25401  >USA > $ >Phone: +001 (304) 263-0163 ext. 235 >Fax:   +001 (304) 263-0702f% >Email: jjennis@discovery.fuentez.com  >       jhjennis@shentel.net' >WEB: http://www.discovery.fuentez.com/o >n   ------------------------------  % Date: Sun, 22 Oct 2000 09:46:19 +0200o0 From: Didier Morandi <Didier.Morandi@Easynet.fr>! Subject: TCP/IP questions: Where?g* Message-ID: <39F29B4B.66C0FBFB@Easynet.fr>  8 Where can I ask questions on TCP/IP for OpenVMS, please?  @ We just had a training on this product, and we didn't succeed toD "remove" an error message produced by the BIND server when doing the following commando  % $ tcpip sh host/nolocal/server=FOOBARn  $ (VMS 7.2 TCP/IP V5.01 two Alpha 400)  < it does list all nodes, then says something like "invalid orD unrecognized reponse from host" (after a loooong time waiting). If ID look into the .LOG in the TCPIP$DNS directory, I have all the serverH messages with the details read from the CONF files, then the logger saysE (more or less, I don't have the machine at home) "query received fromlM node TOTO, no answer because of error AWRQ (not auth)" (from top of my head).v  F I TPUed the .EXE and found a couple of errors messages in it, one withG the (acl) explanation, one with the (not auth) and another one. So it'sn) not an acl instruction missing somewhere.e  3 I didn't find in the DEC doc this "not auth" error.i  E The problem is that we build the conf by hand, until I discovered thep& TCPIP$BINDSETUP.COM in sys$manager :-)  B When using this (lovely) proc, the server works fine. Doing a diffJ between the two confs didn't help to figure out where the error came from.   Sorry for this long post.tD Thanks for any pointer to the TCP/IP notesfile ooopppss... forum :-)   D. -- lF   --------------------------------------------------------------------F Le Pachacamac COMPAQ/DEC/APPLE 34 ave. G. Pompidou 81500 Lavaur FranceB    http://www.pachacamac.com   ** Une passion pour l'excellence **F Tl. : 05.63.58.58.63    Fax. : 05.63.58.58.33    GSM : 06.88.97.61.48   ------------------------------  % Date: Sun, 22 Oct 2000 19:18:38 +0010n% From: paddy.o'brien@zzz.tg.nsw.gov.auc+ Subject: Re: This list participants profile 5 Message-ID: <01JVNDBG24QA005OYE@tgmail.tg.nsw.gov.au>g  G >Just to inform I accounted the ages and experience of all people here.w >Some didnt inform the age :-) >only the experience . . . >p >Below are  the results: >u >Ages  of the OVMS people: >l- >(Embedded image moved to file: pic00041.pcx)C >v >Total                       53t >  >Experience in years with OVMS:  >  >n- >(Embedded image moved to file: pic18467.pcx)a >. >Total                      56  P The average age was interestingly what I would have expected.  30/40 mark, with J a few of we geriatrics, and a few up-and-coming youngsters.  This is also & probably typical of many career paths.  " Anyway, thanks for the summary ...  J Excepting that I have one objection.  For a handful of lines of text, you I translated these to a .pcx file, whatever that may be.  It is byte heavy!I  O It's obviously one of these things that Bill understands because I was able to oH read by copying it over to a colleagues PC -- I don't have one of these 4 creatures (a PC not a Bill --- I don't want either).  N The current trend in email seems to be to send any combination, and often the J whole combination, of plain text, html and a "word" document.  Plain text M suffices nicely for me, thank-you.  The rest just overload my mail directory.e  Q This .pcx thing used 21 blocks, text would have been 3 (I tested, and that's the -O cluster size on my VAX 6.2 disk where I get my mail).  But it is not as bad as J the "word" stuff..   Regards, Paddy   Paddy O'Brien, Transmission Development,e
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, AustraliaE   Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people,a; but that little whizz-bang apostrophe gives me little spam.f   ------------------------------  % Date: Sun, 22 Oct 2000 07:44:30 +0100"  From: Paul Sture <paul@sture.ch>% Subject: Re: User Guide for Vax (VMS)a+ Message-ID: <VA.00000117.04e76dfc@sture.ch>w  F In article <IjkI5.18$gN1.2645@nreader1.kpnqwest.net>, Kirk Acid wrote:' > From: "Kirk Acid" <kirk.acid@lion.cc>C > Newsgroups: comp.os.vmsn' > Subject: Re: User Guide for Vax (VMS)q' > Date: Sat, 21 Oct 2000 19:23:22 +0200  >  > Hmm..  thats the prob.: > How do i find out which version of vms i have installed    at the command prompt:  )    $ write sys$output f$getsyi("VERSION")t  ' (the initial dollar sign is the prompt)e   on later versions:      $ show system /noprocessi    h > and which ip-stack,r      $ show network"   might give a clueH  5 > and if i know that how can i change the ip-addr. ??p >w+ That depends on which ip system you have...M  " > is there a ftp-program in vms ??  0 Yes, assuming you do have an ip product on there   > can i install netscape ??   N Yes. The one mostly in use is Netscape V3.03. Mozilla has just been released, $ but I can't vouch for it personally. >s  < > Do you meen  the System Manager's Manual (Essentials) from > openvms.digital.com ??   Yes, that's the one. ___e
 Paul Sture Switzerland5   ------------------------------  # Date: Sun, 22 Oct 2000 13:37:16 GMTC= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)p  Subject: Re: Xemacs on OpenVMS ?0 Message-ID: <009F1F94.21088DAA@SendSpamHere.ORG>  o In article <972127875.837562@tornado.itea.ntnu.no>, Roar =?iso-8859-1?Q?Thron=E6s?= <roart@nvg.ntnu.no> writes:-? >Brian Schenkenberger, VAXman- <system@sendspamhere.org> wrote:vX >: In article <m3bswfsgut.fsf@sebold.lcms.org>, Charles Sebold <sebold@lcms.org> writes: >:>spolato@my-deja.com writes: >:>aA >:>> Does anyone know whether Xemacs has been ported on OpenVMS ?a >:>oK >:>I have seen no signs of it, although there may have been patches for v19 H >:>to run under VMS.  I suspect you'll have more luck with GNU Emacs 19,G >:>but I haven't found binaries for that, and I can't get it to compilehJ >:>under VMS 6.2 or later.  (If anyone has working binaries, VAX or Alpha,? >:>for Emacs 19, I would dearly love to snag them, by the way.)s >wI >: You'll also not get it to compile with DEC C V5.6 and up due to a pre-cH >: processor bug.  I've just received a Compaq C6.3 beta that supposedlyI >: has this fixed.  What other evils may be lurking are still unbeknownstn= >: at this time but I'm certain I'll encounter more C demons.n >e >: --fR >: VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM >:            R >: city, n., 1. a place where trees are cut down and streets are named after them. >e >Funny.1 >g$ >I compiled emacs-19_28-19970601 on: > ' >DEC C V5.6-003 on OpenVMS VAX V7.1    e, >Compaq C V6.2-007 on OpenVMS Alpha V7.2-1   >a/ >But I had to do som renaming in [.src]sysdep.ce' >(bcmp to bcmp2 etc, and fork to vfork)X >p# >On VAX, I had to add something in:  >configure.com*: >+$ LDFLAGS := /nodebug  a >i+ > $ if f$type(OPTS) .eqs. "" then OPTS = ""p= >+$ if f$type(CPP_NOOPSPACE) .eqs. "" then CPP_NOOPSPACE = ""  > $ sys_includes = ""n >o* > $     CFLAGS := 'CFLAGS' /NESTED=INCLUDE' >+$     CPP_NOOPSPACE := /STANDARD=VAXC- > $    elseD >t2 > $ if f$type(CC) .nes. "" then __compiler := 'CC'= >-$ '__compiler' '__tmp'/preprocess='tempcname'-i 'tempcname'/> >+$! '__compiler' '__tmp'/preprocess='tempcname'-i 'tempcname'N >+$ '__compiler' '__tmp' 'CPP_NOOPSPACE' /preprocess='tempcname'-i 'tempcname'J > $ search/nohead/output='tempcname'-stripped 'tempcname'-i "configure___" >dD > $ write config_status_file "$ CFLAGS=""''CFLAGS'""" ! ExperimentalQ >+$ write config_status_file "$ CPP_NOOPSPACE=""''CPP_NOOPSPACE'""" ! Experimentan >l@ > $ write config_status_file "$ LN_S=""''LN_S'""" ! Experimental >eI >A lot of such CPP_NOOPSPACE, and maybe some manual removeal of spaces inL >makefiles/mmsfiles. >e >descrip.mms*:1 >        @ lib_src_dir = f$environment("DEFAULT")66 >+       @ etc_dir := $(srcdir_dev)[$(srcdir_dir).etc] >        @ set default [-.etc]- >-       @ etc_dir = f$environment("DEFAULT")d- >+       @ doc_dir = f$environment("DEFAULT")r >        @ set default 'a'= >        @ write foo "$ define/user EMACSDATA ""''etc_dir'"""n< >-       @ write foo "$ define/user EMACSDOC ""''etc_dir'"""< >+       @ write foo "$ define/user EMACSDOC ""''doc_dir'"""J >        @ write foo "$ define/user TERMCAP ""''termcap_dir'TERMCAP.DAT""" >s >[.src]vmsgmalloc.c: >        return NULL;s >+#if 0tH >       if (result >= vms_fake_heap_end && result < vms_real_heap_start) >        result = tmpadr[1][0];b >+#elsee >+       result = tmpadr[1][0];  >+#endif- >       vms_brk_current = result + increment;  >d% >On Alpha, I had to add something in:r >[.src]vmsproc.h:  >+#define UCX$C_DSC_ALL 2m > E >I am not saying my changes are correct (especially with fork) but itn+ >compiles. So far, only gnus crashes emacs. K >(I am not sure all the changes are mine, I may have seen them here before)a >c >--  >-Roar Throns  I I should have said "above V5.6 and up"...  I believe it was V5.7 that was5/ the first version ot improperly handle the "\".r     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMa            sO city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------    Date: 22 Oct 2000 19:12:28 +0100O From: pmoreau@dev.ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.64.40)-' Subject: [DECW] Archive new mirror sitep  Message-ID: <fnNMXm5wmHBF@sable>  ; The DECW Archive (web pages) main mirror is now located at s; http://decwarch.free.fr/ (A nice url for such a site ...). .1 The Multinania mirror is always available at url e( http://www.multimania.com/pmoreau/decw/   M The CENA site may or may not be available in the future (firewalling issues).e  N If the CENA site is closed, I may put some recent kits on the web page mirrors! (about 100 Mb available on each).1   Patrick? --O ===============================================================================fO pmoreau@cena.dgac.fr  (CENA)     ______      ___   _           (Patrick MOREAU)T4 moreau_p@decus.fr (DECUS)       / /   /     / /|  /|J CENA/Athis-Mons FRANCE         / /___/     / / | / |   __   __   __   __  N BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  |N 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__|N http://www.ath.cena.fr/~pmoreau/            http://www.multimania.com/pmoreau/O ===============================================================================n   ------------------------------   End of INFO-VAX 2000.591 ************************