1 INFO-VAX	Thu, 01 Nov 2001	Volume 2001 : Issue 607       Contents:" Re: Blockbuster uses Alpha systems" Re: Blockbuster uses Alpha systems Blockbuster's not Alpha  Re: Blockbuster's not Alpha  Re: Broadcasts in LAVC CMS question Re: CMS question Re: DCPS and Native PCL 2 Re: DECwindows Motif Server Mandatory Update Patch! Re: Delta time between two date's ! Re: Delta time between two date's ! Re: Delta time between two date's  Re: FTP over SSL" Re: Garage Sale... Hey, Hobbyists!" Re: Garage Sale... Hey, Hobbyists!" Re: Garage Sale... Hey, Hobbyists!: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB" Mixed language programming and RMS Re: NT/W2K CRSS exploit  Re: NTP on VMS Re: OpenVMS startup log file?  Re: OT - HP's MPE-IX Re: OT - HP's MPE-IX Re: PCL Printer control codes ! Re: savesets,  CDs and attributes @ Re: Stopping processes with open files;  WAS:Re: DEC C and DECUS@ Re: Stopping processes with open files;  WAS:Re: DEC C and DECUS% Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM  Re: Undo disk Initialize Re: Undo disk Initialize Re: Unix-based, VMS-based?! Re: VMS721_Mount96-v0300 Question ! Re: VMS721_Mount96-v0300 Question $ VMSMAIL file, on a write-locked disk( Re: VMSMAIL file, on a write-locked disk( Re: VMSMAIL file, on a write-locked disk$ WARNING: PROTECT YOUR NAME IN CANADA- Re: [VMS V7.3 VAX] my first crash since years   F ----------------------------------------------------------------------  # Date: Wed, 31 Oct 2001 18:54:51 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)+ Subject: Re: Blockbuster uses Alpha systems 3 Message-ID: <%NXD7.1164$RL6.16997@news.cpqcorp.net>   m In article <gsXD7.22909$U7.1484951@bin1.nnrp.aus1.giganews.com>, "John Smith" <someone@somewhere.com> writes: I :Anyone familiar with what make and model Alpha Blockbuster uses in their  :backoffice system?      Yep.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 Oct 2001 16:50:49 -0500 8 From: "Steven Santinelli" <Santinelli@smscompNOSPAM.com>+ Subject: Re: Blockbuster uses Alpha systems + Message-ID: <9rprn10dou@enews1.newsguy.com>   D Yeah, always gives me that warm and fuzzy feeling every time I go to blockbuster, and see the VT's... :^)    Steve     5 "John Smith" <someone@somewhere.com> wrote in message : news:gsXD7.22909$U7.1484951@bin1.nnrp.aus1.giganews.com...J > Anyone familiar with what make and model Alpha Blockbuster uses in their > backoffice system? >  > -- > KCJunkman  >  >    ------------------------------  # Date: Wed, 31 Oct 2001 19:25:22 GMT # From: "Gill Bates" <gbates@aol.com>   Subject: Blockbuster's not Alpha@ Message-ID: <CeYD7.23125$U7.1511719@bin1.nnrp.aus1.giganews.com>  F The system Blockbuster uses isn't a true Alpha system, it's one of the- generic boxes that still have the Alpha logo.    ------------------------------  % Date: Wed, 31 Oct 2001 19:22:10 -0500 0 From: "Island Computers" <dbturner@islandco.com>$ Subject: Re: Blockbuster's not Alpha/ Message-ID: <tu14u739j9li10@news.supernews.com>   . I supplied some spares to them a few years ago  @ Back then they were using Microvax 3100-40's, VT320's and LA75's  B I heard they have gone on to Alphastation 200's but I may be wrong   DT   -- David Turner   We sell Alpha systems & parts  http://www.islandco.com  sales@islandco.com Island Computers US Corp.  2700 Gregory Street  Savannah GA 31404  Tel: 912 447 6622  Fax: 912 201 0096 , Gill Bates <gbates@aol.com> wrote in message: news:CeYD7.23125$U7.1511719@bin1.nnrp.aus1.giganews.com... > H > The system Blockbuster uses isn't a true Alpha system, it's one of the/ > generic boxes that still have the Alpha logo.  >  >  >    ------------------------------  % Date: Thu, 01 Nov 2001 01:56:16 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: Broadcasts in LAVC , Message-ID: <3BE0F20E.2C94C814@videotron.ca>   Hoff Hoffman wrote: J >   The keepalive is a multicast.  Not a broadcast.  The keepalive messageK >   frequency itself is circa once every three seconds.  Very low, in other  >   words.    I But if you have 7 nodes, that would mean 2.3 messages per second, right ?   H From an ethernet network point of view, don't bridges and routers handleF multicasts the same way as a broadcast ? (i.e. send them across to the adjacent segments). ?    ------------------------------  % Date: Wed, 31 Oct 2001 15:09:38 -0800 # From: "Tom Linden" <tom@kednos.com>  Subject: CMS question 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIKEDBDIAA.tom@kednos.com>   B Have a build that runs on both VAX and AXP, with some differences." On the vax a module is retieved as cms fetch foo.pli /gen=V3.7 ""
 and on AXP as H cms fetch foo.pli  ""   These systems are clustered and use the same cms lib.  G In the former it fetches generation 26 of the element and in the latter  generation 27.  H If I reserve the former and try to replace it with the latter element it" says generation 27 already exists.   ThusD $ cms fetch foo.pli ""    (this picks up generation 27, and calls it
 foo.pli;1)J $ cms reserve /gen=V3.7 foo.pli "" (this picks up generation 26, and calls
 it foo.pli;2)  $ dele foo.pli;2" $ cms replace /gen=V3.7 foo.pli ""  " which gives the replacement error.  9 %CMS-E-NOREPLACE, error replacing PLI$COMMON:[CMS]FOO.PLI . -CMS-E-GENEXISTS, generation 27 already exists  I Not sure how I got in this muddle, but I need them both to fetch the same K (generation 27) module.  I had initially  made the change for the AXP build E which created 27, but obviously that didn't make it to the VAX build.    Help is much appreciated.    Tom    ------------------------------  % Date: Wed, 31 Oct 2001 20:55:16 -0500 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: CMS question L Message-ID: <rdeininger-3110012055170001@user-2ivec5o.dialup.mindspring.com>   (posted and mailed)   F In article <CIEJLCMNHNNDLLOOGNJIKEDBDIAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> wrote:   D > Have a build that runs on both VAX and AXP, with some differences.$ > On the vax a module is retieved as  > cms fetch foo.pli /gen=V3.7 "" > and on AXP as J > cms fetch foo.pli  ""   These systems are clustered and use the same cms > lib. > I > In the former it fetches generation 26 of the element and in the latter  > generation 27.  G I assume V3.7 is the name of a class.  A class will refer to a specific J generation of an element.  So /gen=V3.7 gets you (in this case) generationH 26, while a FETCH with no /GEN will get you the latest generation of theJ moment.  No matter what generations you add, /gen=V3.7 will always get you generation 26.  J > If I reserve the former and try to replace it with the latter element it$ > says generation 27 already exists. >  > ThusF > $ cms fetch foo.pli ""    (this picks up generation 27, and calls it > foo.pli;1)L > $ cms reserve /gen=V3.7 foo.pli "" (this picks up generation 26, and calls > it foo.pli;2)  > $ dele foo.pli;2$ > $ cms replace /gen=V3.7 foo.pli "" > $ > which gives the replacement error. > ; > %CMS-E-NOREPLACE, error replacing PLI$COMMON:[CMS]FOO.PLI 0 > -CMS-E-GENEXISTS, generation 27 already exists  J My (old) CMS manual says, "by default, the number of the new generation isJ the number of its predecessor with the rightmost level number increased byE one."  So in your case, you're trying to replace generation 26, which 3 should make generation 27, but that already exists.   F You may need to REPLACE/VARIANT, which would establish another line of descent for this element.   @ If you want to make the stuff in generation 26 become the latest( generation, you could do something like:J FETCH/GEN=V3.7 foo.pli ""       ! fetches generation 26 without reserving.8 RESERVE/NOOUTPUT foo.pli ""     ! reserves generation 27O REPLACE foo.pli ""              ! creates generation 28, with the same contents (                                 ! as 26.  4 I'm not sure I understand what you are trying to do.  K > Not sure how I got in this muddle, but I need them both to fetch the same M > (generation 27) module.  I had initially  made the change for the AXP build G > which created 27, but obviously that didn't make it to the VAX build.   J If you want to fetch or reserve the most recent generation (which is 27 atJ the moment), you need to omit the /GEN=V3.7.  That is forcing CMS to fetch gen 26.   A If the VAX and Alpha elements are really different, and will stay G different, you probaby need variant lines, or different element names.  B With variant lines, you might find it useful to use something likeH "/GEN=V3.7+".   The extra "+" will get you the most recent generation on& the line of descent that matches V3.7.   --   Robert Deininger rdeininger@mindspring.com    ------------------------------  % Date: Wed, 31 Oct 2001 19:22:41 -0500  From: Ray <lists@aik.tec.sc.us>   Subject: Re: DCPS and Native PCL- Message-ID: <3BE095D1.8F838CEC@aik.tec.sc.us>    Tony Scandora wrote:   <snip>K > 1) It only prints on printers it knows about.  New printers come out with E > new device identifications and DCPS can't handle them, even if they H > understand older printers' commands. I would like to have table drivenL > device specific support, with at least a crude user interface, or at least: > the ability to say printer B obeys printer A's commands.  I Actually, I send plain old postscript to several new printers that aren't C supported by my version of DCPS.  Works just fine for normal stuff.    J > 2) It only prints on directly connected printers, which is the best way.K > Without removing the current robust method of handling directly connected H > printers, I would like the options of being able to generate a file ofH > PostScript to be sent later, and being able to send to an lpr queue on > another system.    Agreed!    Ray    ------------------------------  # Date: Wed, 31 Oct 2001 19:04:17 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman); Subject: Re: DECwindows Motif Server Mandatory Update Patch 3 Message-ID: <RWXD7.1165$RL6.17063@news.cpqcorp.net>   \ In article <3BDF5C05.45D92D89@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:  O :Don't some DECW$ files get installed with VMS  without the DECwindows server ?   J   There are two components to DECwindows, the portion that is dependent onJ   the OpenVMS version, and the portion that is not.  The two portions are H   packaged and installed separately -- the former (optionally) installs I   when OpenVMS is installed, and the latter installs when the DECwindows  #   layered product kit is installed.     N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 31 Oct 2001 14:25:58 -0500 - From: "Peter Weaver" <peter.weaver@stelco.ca> * Subject: Re: Delta time between two date's2 Message-ID: <lfYD7.50279$Z2.750062@nnrp1.uunet.ca>  1 "Shane Smith" <ssmith@icius.com> wrote in message * news:01C161F8.F0A678F0@sulfer.icius.com...J > A little experimentation shows the "BOOT" and "LOGIN" date/time keywordsC > aren't global. F$CVTIME understands them, as does ANAL/ERROR, but H > DIAGNOSE (which does get "TODAY") drops an error if you give it eitherI > "BOOT" or "LOGIN". That suggests to me they aren't implemented the same J > way as the others so perhaps DCL_Tips/Date_Time/Absolute isn't the right > place to document them.  >...  / That is because the .CLD for DIAGNOSE includes;    qualifier SINCE  value (type=$rest_of_line)  L instead of specifying "type=$datetime" - so the programmer has to figure outB what the date is. So it is not that BOOT and LOGIN are implementedI differently, some programs (DIAGNOSE and CA specifically) are not written 
 correctly.   ------------------------------  # Date: Thu, 01 Nov 2001 01:02:35 GMT / From: StevenU@POBoxes.com (Steven P. Underwood) * Subject: Re: Delta time between two date's9 Message-ID: <3be09eb4.175588006@news.directvinternet.com>   5 Works back to Alpha/VMS v7.1 but not on VAX/VMS v5.2.    Steve   7 On Tue, 30 Oct 2001 21:19:27 -0600, "David J. Dachtera"  <djesys.nospam@fsi.net> wrote:   >Martin Hunt wrote:  >>  E >> On 24 Oct 2001 20:59 CDT, carl@gerg.tamu.edu (Carl Perkins) wrote:  >>  H >> >Time since last boot (I didn't know this would work until now - it's, >> >pretty spiffy that this actually works): >> > >> >$ @timediff "boottime" >> >0024-04:41:33  >> >E >> New one on me, but I just tried DIR/SINCE=BOOT and guess what - it , >> shows files created since the last boot.  >  >What version are you running? >  >> HELP SPECIFY DATE documentsH >> TODAY and TOMORROW, but BOTTIME is not there. Another thing to add to7 >> the list of undocumented commands/keywords, I think.  > 7 >Wouldn't be the first case of undocumented behavior...  >  >--  >David J. Dachtera >dba DJE Systems >http://www.djesys.com/  > ) >Unofficial Affordable OpenVMS Home Page:   >http://www.djesys.com/vms/soho/   Steven P. Underwood,DNRC Whitinsville,MA  StevenU@POBoxes.com    ------------------------------   Date: 1 Nov 2001 03:00:07 GMT - From: Joe Heimann <heimann@nog.ecs.umass.edu> * Subject: Re: Delta time between two date's, Message-ID: <9rqdrn$fij$1@odo.ecs.umass.edu>  0 David J. Dachtera <djesys.nospam@fsi.net> wrote: > Martin Hunt wrote: >>  E >> On 24 Oct 2001 20:59 CDT, carl@gerg.tamu.edu (Carl Perkins) wrote:  >>  H >> >Time since last boot (I didn't know this would work until now - it's, >> >pretty spiffy that this actually works): >> > >> >$ @timediff "boottime" >> >0024-04:41:33  >> >E >> New one on me, but I just tried DIR/SINCE=BOOT and guess what - it , >> shows files created since the last boot.    > What version are you running?    >> HELP SPECIFY DATE documentsH >> TODAY and TOMORROW, but BOTTIME is not there. Another thing to add to7 >> the list of undocumented commands/keywords, I think.   8 > Wouldn't be the first case of undocumented behavior...  E I had not come across this one before, so tried it.  It is there on a H Vax VMS 7.0 system.  HELP DIR /SINCE does list BOOT as an option as wellH as LOGIN.  If I recall right, 7.0 was released after 6.1 and before 6.2.    Joe   heimann@ecs.umass.edu    ------------------------------  % Date: Wed, 31 Oct 2001 16:44:04 -0500 , From: "Richard Whalen" <WhalenR@process.com> Subject: Re: FTP over SSL + Message-ID: <9rprb7$73a$1@news.process.com>   G The port of SCP2 that will ship with MultiNet 4.4 can use functionality F available in the protocol to preserve VMS file attributes when copyingA between two VMS systems with MultiNet 4.4 SCP2.  It also has some F functionality to translate VMS record mode files to stream-lf files to6 provide some level of compatibility to Unix & Windows.  J I agree that SCP lacks the formal ability to deal with differences in data, representation between systems that FTP has.   Rich Whalen  Process Software  = "Frank da Cruz" <fdc@watsun.cc.columbia.edu> wrote in message / news:9rn40q$1rn$1@newsmaster.cc.columbia.edu... : > In article <00A044BE.CA557701@ssrl04.slac.stanford.edu>,F > Alan Winston - SSRL Admin Cmptg Mgr <winston@SSRL.SLAC.STANFORD.EDU> wrote:, > : In article <3BDEFBC5.80316AE@rdrop.com>,, > :  Dean Woodward <deanw@rdrop.com> writes:K > : >Anyone dealt with transmitting files via FTP over SSL, directly from a K > : >VMS box?  I've got a customer that wants to do this.  (Read: needs to, # > : >wants a non-windoze solution.)  > : F > : I haven't dealt with this, but have heard about it.  There are two, > : protocols, SCP (secure copy) and SFTP... > : F > I don't think these are the same as SSL.  You can have a regular FTPH > connection secured by SSL, but SCP is something else -- in fact it's aH > semi-secure variation of Unix RCP.  SCP does not take into account theE > differences among file systems (e.g. Unix, VMS, Windows) and copiesl everyingF > in binary mode, which is not going to be very useful between VMS andL > anything else, or probably not even between two VMS's, unless the protocolL > is modified to send along file attributes or raw disk and directory blocks > or somesuch. >e   ------------------------------  % Date: Wed, 31 Oct 2001 15:09:40 -0500e) From: "Mike Foley" <mikiefoley@yahoo.com>S+ Subject: Re: Garage Sale... Hey, Hobbyists!a/ Message-ID: <tu0mg7o8d1j6a6@corp.supernews.com>H  J "Brian Schenkenberger, VAXman-" <system@SendSpamHere.ORG> wrote in message* news:00A04582.DF479E7C@SendSpamHere.ORG...  H > being used as scratch posts by Hobbes (that's the cat).  I'm taking it away' > to the remote storage garage for now.   G And here I was thinking you were talking about CW (that's the engineer)    ------------------------------  # Date: Thu, 01 Nov 2001 00:11:53 GMTs= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)l+ Subject: Re: Garage Sale... Hey, Hobbyists!S0 Message-ID: <00A045C8.5D459A46@SendSpamHere.ORG>  p In article <00A04582.DF479E7C@SendSpamHere.ORG>, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes:L >I have some equipment (likely more in the near future) that I am willing toK >part with and that would make a great addition to some of the Hobbyist VMSAL >systems out there.  Much of it is boxed up in my basement and the boxes areL >being used as scratch posts by Hobbes (that's the cat).  I'm taking it away& >to the remote storage garage for now. >oK >I've compiled a list of some of the things I'm taking to storage today andsE >this list is available here:  http://www.tmesis.com/garage_sale.html2 >$L >This is all working equipment -- most used.  I will initialize and test all$ >disk drives before letting them go.  H WOW!  What an overwhelming demand.  Most of what I presently have on theG list has been requested.  I am now at the point were some of this stuff-H will have to be divided up to interested parties.  It's obviously first- come, first-serve.     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMS            aJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesl   ------------------------------    Date: 31 Oct 2001 18:27:43 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)g+ Subject: Re: Garage Sale... Hey, Hobbyists!n3 Message-ID: <4zifZHaRILIg@eisner.encompasserve.org>   p In article <00A045C8.5D459A46@SendSpamHere.ORG>, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes:  J > WOW!  What an overwhelming demand.  Most of what I presently have on theI > list has been requested.  I am now at the point were some of this stuffa3 > will have to be divided up to interested parties.   F Not for those of use whose only request was copies of the disks beforeC they get initialized.  In that case, you can provide duplicates :-)1   ------------------------------  + Date: Wed, 31 Oct 2001 19:19:09 +0000 (UTC), From: david20@alpha2.mdx.ac.ukC Subject: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERB + Message-ID: <9rpird$m77$1@aquila.mdx.ac.uk>   V In article <3bdf755d_6@vienna7.his.com>, "Reece R. Pollack" <bogus@public.com> writes:K >"j.lance wilkinson, (814) 865-1818" <jlw@psulias.psu.edu> wrote in messagef& >news:9qpr2c$uoc@r02n01.cac.psu.edu... >i >> Any chance that somebody'sA >>L >> 1) Implemented MOD_AUTH_KERB for OpenVMS already and is willing to share?H >> 2) Got the full KRB5 include set at least translated for OpenVMS so I >could >> possibly get (1) going here?s > J >I ported the full Kerberos V5 package, clients and servers, to VMS when IM >worked for Wollongong. Anyone running the last Attachmate version of PathWay.J >for OpenVMS has full Kerberos V4 and V5 capabilities, including shareableM >libraries and header files. Alas, Attachmate didn't understand anything thatlE >didn't run under a Microsloth operating system and connect to an IBM0( >mainframe, and they killed the product. >f >--.    ? Just downloaded and setup the Kerberos Security Client for VMS.   / Good news it included a full Kerberos 5 Server.oB Bad news it didn't seem to do anything to modify Telnet , FTP etc.L Contacted Compaq. Seems DEC TCPIP services will not have Kerberized versions9 of Telnet, FTP etc until at least DEC TCPIP Services 5.3.   M Why on earth bother to release this (with the Title Kerberos Security Client) % without Kerberizing Telnet, FTP etc ?   
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------   Date: 31 Oct 2001 20:56:17 GMT0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz)C Subject: Re: Kerberos Client on OpenVMS, CSWS/APACHE, MOD_AUTH_KERBH5 Message-ID: <9rpohh$ndk$1@newsmaster.cc.columbia.edu>a  N In article <9rpird$m77$1@aquila.mdx.ac.uk>,  <david20@alpha2.mdx.ac.uk> wrote: : ...mA : Just downloaded and setup the Kerberos Security Client for VMS.  : 1 : Good news it included a full Kerberos 5 Server..D : Bad news it didn't seem to do anything to modify Telnet , FTP etc.N : Contacted Compaq. Seems DEC TCPIP services will not have Kerberized versions; : of Telnet, FTP etc until at least DEC TCPIP Services 5.3.s : O : Why on earth bother to release this (with the Title Kerberos Security Client) ' : without Kerberizing Telnet, FTP etc ?c : J Maybe somebody would like work on Kerberized Kermit for VMS.  The securityK modules are all there, but so far are only for Unix.  All the work is done,EH except the VMS porting job.  Again, as I said, if it's the same API (MITI Kerberos) then it might not be such a big deal.  Anyone who is interested % in taking this on, please contact me.u   - Franki   ------------------------------  % Date: Wed, 31 Oct 2001 21:14:02 -0700l/ From: "cstranslations" <cstranslations@msn.com>i+ Subject: Mixed language programming and RMS-+ Message-ID: <ONXI1toYBHA.1992@cpimsnntpa03>:  G I am working on an application that will be written in a combination ofRK BASIC and C. I am likely going to have a need to write to a particular filepH (the application logfile) at various times from both the BASIC and the CK parts of the application. I threw together some test code that opens a fileaK (from BASIC) and then does a few "interleaved" writes to the file from bothm
 languages.  K Just wondering if anyone out there has done this and has any gotchas that IlJ should look out for other than, "be sure to use str$get1_dx and associatedL functions when passing string data back and forth between BASIC and C." WhatD I'm wondering about (in particular) is if there will (or can be) anyJ problems on the BASIC side after I alter the rab (in particular) rab$l_rbf! and rab$w_rsz over on the C side.i   JoeG   ------------------------------  # Date: Wed, 31 Oct 2001 20:19:28 GMTe From: LBohan@dbc.spam_less..coml  Subject: Re: NT/W2K CRSS exploit8 Message-ID: <gnm0utssov9noonj82gjo1rk0e1ur8n6e3@4ax.com>  @ On Wed, 31 Oct 2001 11:55:15 GMT, system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) wrote:i  F >Just for "acedemic" purposes, I tried such a file here on the PeeCee.F >It didn't BSoD.  Perhaps, I'm just going about it wrong as I am not a >PeeCee saavy type.  >mG >Could you email your file to me and instructions as to how to take the 
 >PeeCee down.R  0 the key point, for me anyway, seemed to be that * a bare-bones 'default' DOS box was needed.  7 no scrollbars, no quickedit, and maybe no insert mode, t' and possibly  24 lines by 75 (?) cols. r  - such as might be had from a Start/Run..  CMD e  4 those 'defaults', however, iirc, can be mucked with,( by the settings in Control Panel/MSDOS.     2 I hadn't the time to figure out what exactly what / (minimum) combination of DOS box settings will f3 exercise this bug, but I and a few other were able h( to see this on a variety of Billy boxes.  5 the file I used, was one I xfer'ed from a VMS system,7= just (mixed) lines of back-spaces, tabs, and upper-case 'A's.E- Leading backspaces on each line of 595 chars;t   dunno if that's important.   ------------------------------  # Date: Wed, 31 Oct 2001 19:25:38 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: NTP on VMSo3 Message-ID: <SeYD7.1168$RL6.17152@news.cpqcorp.net>e  ^ In article <oRJD7.32226$ya.6550224@news1.busy1.on.home.com>, "Nobody" <guess@home.net> writes:  I   OpenVMS questions are best asked in comp.os.vms.  Follow-ups set there.X  4 :We are running VMS 7.2 and TCPIP 5.0 on our Alphas.  J   I would strongly encourage TCP/IP Services V5.0A with ECO, or V5.1 with -   ECO.  I would definitely upgrade from V5.0.e  N :I would like to set up NTP in order to synch the clocks with our Time Server.  H   Synchronize with the time server via NTP?  Or via some other protocol?  P :Compaq tells me that versions older than 4.0 of TCPIP have this functionality.   E   TCP/IP Services V3.3 and more recent releases have NTP support, and.   V5.1 has the current support.i  F :I have not been able to find it anywhere in the documentation though.  >   Please look in the TCP/IP Services management documentation.  ' :Any thoughts of how to configure NTP ?9  G   Please acquire and read the OpenVMS Frequently Asked Questions (FAQ).yF   There are various time- and NTP-related topics included in the FAQ, F   including the following directly relevent sections: "How can I keep F   the OpenVMS system time synchronized?", "How can I configure TCP/IP I   Services NTP as a time provider?", "How can I drift the OpenVMS system  J   time?", and a few others.  Additionally, please take the time to review F   the TCP/IP Services product documentation, either locally or at the F   http://www.openvms.compaq.com/doc/ site.  The management manual will   be of particular interest.  I   If the Time Server is DECnet-Plus DTSS (DECdtss), I've just received a hJ   pointer to DECnet-Plus DTSS connector for NTP -- very old DTSS kits had H   an example using an ancient NTP protocol, the DECnet-Plus V7.3 kit is F   the first DTSS kit in a long time that contains this example -- the 8   new example also uses a far more current NTP protocol.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 31 Oct 2001 21:44:27 GMT' From: "Jim Strehlow" <jims@data911.com>e& Subject: Re: OpenVMS startup log file?0 Message-ID: <9rprbr$b85@dispatch.concentric.net>  < Since OpenVMS version 7.1 ?? (a while ago) do the following:    L http://www.openvms.compaq.com:8000/72final/6017/6017pro_010.html#sysman_star tup_sece  = $ MCR SYSMAN STARTUP SET OPTIONS /VERIFY=PARTIAL /OUTPUT=FILEi /NOCHECKPOINTING  = $ MCR SYSMAN STARTUP SHOW OPTION          !shows those valuese  ( When you boot OpenVMS with /output=file,@ OpenVMS copies all startup information to SYS$SYSTEM:STARTUP.LOG    3 Jim Strehlow, Data911/SunviewMobile Systems Managerr Alameda, CA, USA  / "Let them do their worst. We will do our best."     D "Lothar Geyer" <Lothar.Geyer@EDV-Berater-Online.de> wrote in message/ news:3BD9CD4C.20DD758C@EDV-Berater-Online.de...  > DigiDemon schrieb: > >5 > > Greetings all! > >tK > > I'm a lil bit of a newbie when it comes to OpenVMS.  I have a DEC Alpha6J > > 4/275.  I'm trying to analye some of the startup messages, but my eyesK > > don't work that fast ;-)  Any chance OPenVMS logs the startup messages?  > > Thanks people :) > >E	 > > Jamess >tH > If you only want to look if there are error messages - use the F1 key.H > So you can stop output to the terminal - and continue with another F1. >a > Lothar Geyer   ------------------------------  # Date: Wed, 31 Oct 2001 23:31:05 GMTi0 From: Monty Brandenberg <mcbinc@ne.mediaone.net> Subject: Re: OT - HP's MPE-IX_/ Message-ID: <3BE08A01.BC15D7A7@ne.mediaone.net>"   Gavin Scott wrote: > " > (and so the battle is joined :-)  = Hey, a perfect opportunity to revive VMS-on-Mach.  Slap on anr; MPE environment, suck over tru64, maybe hire a bunch of oldc: Apollo Domain guys.  They knew how to do universes, right?   -- :M Monty Brandenberg, Software Consultant                              MCB, Inc.aM mcbinc@world.std.com                                          P.O. Box 426188cM mcbinc@ne.mediaone.net                              Cambridge, MA  02142-0021T 617.864.6907   ------------------------------  # Date: Thu, 01 Nov 2001 06:11:56 GMT . From: "Duane Sand" <duane.sand@mindspring.com> Subject: Re: OT - HP's MPE-IXr= Message-ID: <MI5E7.4437$wj5.2079920@news1.rdc1.sfba.home.com>o   <lroduner@americhem.com> wrote:  > ...tI > How difficult would it be to move enough of the MPE-IX system functions> and0I > RTL's to VMS so that the existing MPE-IX applications could be "easily"  > ported to VMS?  ...l  C MPE software is all big-endian.  VMS software is all little-endian. B One side or the other would be faced with incompatible data files,B no execution of old binaries, and nontrivial source changes before recompiling.    Same story with HP-UX and Tru64.   ------------------------------   Date: 31 Oct 2001 20:01 CDTh' From: carl@gerg.tamu.edu (Carl Perkins)s& Subject: Re: PCL Printer control codes- Message-ID: <31OCT200120015957@gerg.tamu.edu>/  1 "John Hayes" <john@worldwide-wines.moc> writes...nH }I have a telnet queue going to a canon printer (photocopier,scanner etcJ }unit). I have created a library with PCL control codes to print landscapeM }and portrait. These are fine but when I print in duplex mode, the first page J }always prints on the back side of the first page. It makes all my reports; }looks like they are skipping a page. Anyone got any ideas.o }  }Desperate Now }  }John 7 }john@worldwide-wines.moc (spam filter, switch the moc)>  	 My guess:   = You send the printer control codes. Somewhere in there is the>@ code to turn on duplex. Since you have already sent stuff to the@ printer, when you switch over it thinks you have already printed< on the front of the page and puts later stuff on the back of) the page. Or something along those lines.B  B Anyhow, you may need to isolate the commands so that it knows they@ don't count for "stuff being printed" purposes. At least some HPA printers like for you to do this, if you don't they print a blank,B page. This is done via an <ESC>P at the start and an <ESC>\ at theF end of any PCL being sent (neither of these escape codes is documentedB in the PCL 5 Technical Reference Manual - it is possible that they5 are specific to HP and Canon may use something else).3   --- Carl   ------------------------------  % Date: Wed, 31 Oct 2001 22:25:05 -0600F1 From: "David J. Dachtera" <djesys.nospam@fsi.net>s* Subject: Re: savesets,  CDs and attributes' Message-ID: <3BE0CEA1.C9C4CC8C@fsi.net>v   Larry Kilgallen wrote: > ] > In article <3BDF6E83.E055C1CA@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:o > > Jan-Erik Sderholm wrote:a > >>< > >> Why not just use $COPY to copy from the CD to the VAX ? > >  > > If the CD is ISO-9660, ... > ! > Are you saying there is a bug ?b > B > Certainly the ISO-9660 format has cells to describe the RMS file > characteristics. > < > If you have a properly written ISO-9660 CD-ROM where thoseD > characteristics are not being honored by VMS, please file a report > with Compaq.  F To my knowledge, there is no known way to store RMS file attributes on> ISO-9660 media of any kind, since VMS typically MOUNTs them asE write-protected. I am unaware of any INITIALIZE qualifiers that would.? let me make either an LDcu: or VDcu: device an ISO-9660 volume,v MOUNTable write-enabled.  C I am unaware of any third-party or non-VMS software for doing this, 4 either. AFAIK, MKISOFS_VMS does not do this, either.  F If this is incorrect, or if this has changed since my initial researchG back circa. 1999 or so (prior to Fall DECUS, '99), please post links toh@ the appropriate software, documentation and/or how-to documents,G especially any info. re: caveats for compatibility with non-VMS systemso, (systems which do not natively support RMS).  D With all the attention on DII-COE, I suppose native ISO-9660 support9 (both read and write) should be a wish list item for VMS.v   -- f David J. Dachtera  dba DJE Systemso http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/e   ------------------------------   Date: 31 Oct 2001 20:20 CDT-' From: carl@gerg.tamu.edu (Carl Perkins)cI Subject: Re: Stopping processes with open files;  WAS:Re: DEC C and DECUS:- Message-ID: <31OCT200120205123@gerg.tamu.edu>D  . Mike Rechtman <rechtman@tzora.co.il> writes...- }Two possibilities come to my fevered mind...G } 6 }1. do a sho dev/file DISK: into a file, parse it and  }stop/id= all non-zero id's 8 }2. in DCL, set up a f$context to select/skip processes : }according to whatever criteria you need, and either just < }stop/id them, or (better, in my opinion) get a 3-line prog > }that'll $FORCEX them - that will give the processes a chance " }to go through their exit handler. }  }Mikee  C Doing this where DISK = the system disk would be a really bad plan.g@ Likewise for any disk where other non-user software is installed: (web server, IP stack, mail transport agent, Samba, etc.).  E In other cases, it could cause data corruption. COnsider something astJ simple as a POP server. It is accessing the mail file and half way throughE modifying a record the process is nuked: sounds like a potential mail  file corruptor to me.e  G You'd need to be very careful about what you did or did not allow to betF killed. Forget one thing from the list of "things not to kill" and youG may create your very own personalized denial of service attack, or even  corrupt some data.   --- Carl   }DigiDemon wrote:g } I }>>:... Second, 2 questions....I've been trying to to snag a lil :proggieiI }>>called findlocks.com from DECUS, but to no avail...is there :somethingv }>>up with the site? }>> F }>>  Um, what are you up to?  AMDS and Availability Manager and recentK }>>  versions of SDA are all quite good at tracking locks.  Though AMDS andiJ }>>  Availability Manager are separately installed kits, they are licensed }>>  with OpenVMS. }>>- }>   }> XF }> Actually, I think "findlocks" isn't what I'm looking for...I have aK }> proggie that will find RMS locks (the real exciting thing here is that IwF }> haven't a clue what those are :-D).  What I AM looking for is for aH }> proggie that will find open files.  When I do a nightly backup of theL }> DEC, I will recieve some messages about certain files not being backed upJ }> due to them being open.  Now some I can understand (log files open willG }> most likely be open by the system account yes?)  But some aren't log H }> files...and I'm guessing it's some user that has something open.  I'dA }> like to find out which user so I can smartly chastise them ;-)t }> tK }> And thanks for the GNU links...I will see if with the help of them I canf: }> install SSH and have everything running like a champ :) }> i }> James }>   }-- F }---------------------------------------------------------------------< }Usual disclaimer: All opinions are mine alone, perhaps not  }even that..@ }Mike Rechtman                            *rechtman@tzora.co.il*   ------------------------------  % Date: Thu, 01 Nov 2001 07:16:08 +0200d* From: Mike Rechtman <rechtman@tzora.co.il>I Subject: Re: Stopping processes with open files;  WAS:Re: DEC C and DECUSs* Message-ID: <3BE0DA98.4070004@tzora.co.il>  = Problem avoidable using f$context, if e.g. you set all users 1 to have UICs; in certain ranges. Also - if you _are_ backing up a system >8 disk online, remember this is unsupported and can cause < serious problems on restore (not often, but when it happens  - oboy!)   Mike   Carl Perkins wrote:e  0 > Mike Rechtman <rechtman@tzora.co.il> writes.../ > }Two possibilities come to my fevered mind...  > } 8 > }1. do a sho dev/file DISK: into a file, parse it and  > }stop/id= all non-zero id'ss: > }2. in DCL, set up a f$context to select/skip processes < > }according to whatever criteria you need, and either just > > }stop/id them, or (better, in my opinion) get a 3-line prog @ > }that'll $FORCEX them - that will give the processes a chance $ > }to go through their exit handler. > }  > }Mike  > E > Doing this where DISK = the system disk would be a really bad plan..B > Likewise for any disk where other non-user software is installed< > (web server, IP stack, mail transport agent, Samba, etc.). > G > In other cases, it could cause data corruption. COnsider something asrL > simple as a POP server. It is accessing the mail file and half way throughG > modifying a record the process is nuked: sounds like a potential mail- > file corruptor to me.0 > I > You'd need to be very careful about what you did or did not allow to beeH > killed. Forget one thing from the list of "things not to kill" and youI > may create your very own personalized denial of service attack, or evenu > corrupt some data. > 
 > --- Carl >  > }DigiDemon wrote:e > } K > }>>:... Second, 2 questions....I've been trying to to snag a lil :proggieuK > }>>called findlocks.com from DECUS, but to no avail...is there :somethingl > }>>up with the site? > }>>pH > }>>  Um, what are you up to?  AMDS and Availability Manager and recentM > }>>  versions of SDA are all quite good at tracking locks.  Though AMDS andoL > }>>  Availability Manager are separately installed kits, they are licensed > }>>  with OpenVMS. > }>>b > }> o > }> dH > }> Actually, I think "findlocks" isn't what I'm looking for...I have aM > }> proggie that will find RMS locks (the real exciting thing here is that IiH > }> haven't a clue what those are :-D).  What I AM looking for is for aJ > }> proggie that will find open files.  When I do a nightly backup of theN > }> DEC, I will recieve some messages about certain files not being backed upL > }> due to them being open.  Now some I can understand (log files open willI > }> most likely be open by the system account yes?)  But some aren't log@J > }> files...and I'm guessing it's some user that has something open.  I'dC > }> like to find out which user so I can smartly chastise them ;-)e > }> aM > }> And thanks for the GNU links...I will see if with the help of them I cana< > }> install SSH and have everything running like a champ :) > }> h
 > }> James > }> f > }-- H > }---------------------------------------------------------------------> > }Usual disclaimer: All opinions are mine alone, perhaps not 
 > }even that.aB > }Mike Rechtman                            *rechtman@tzora.co.il* >      --  E --------------------------------------------------------------------- ; Usual disclaimer: All opinions are mine alone, perhaps not r
 even that.? Mike Rechtman                            *rechtman@tzora.co.il*)/ Kibbutz Tzor'a.                          Voice   (home):(972)-2-99083377    "20% of a job takes 80% of the time, the rest takes r another 80%"E ---------------------------------------------------------------------s* ------ GEEK CODE BLOCK (Version: 3.1)-----( GCM/CS d(-)pu s:+>:- a++ C++ U-- L-- W++' N++ K? w--- V+++$ PS+ PE-- t X- tv-- b+n DI+ D-- G e++ h--- r+++ y+++@i* ---------- END GEEK CODE BLOCK  ----------   ------------------------------   Date: 1 Nov 2001 01:11:13 +0100 * From: eplan@kapsch.net (Peter LANGSTOEGER). Subject: Re: SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM( Message-ID: <3be09321@news.kapsch.co.at>  U In article <3bdfd877@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes: X >In article <ttuqbfmrkjgn1b@news.supernews.com>, "John Vottero" <John@mvpsi.com> writes:H >>For me, the V7.3 DAYLIGHT_SAVINGS.COM didn't work at all.  It wound upN >>executing UTC$CONFIGURE_TDF.COM which just displays a message saying that itK >>is an obsolete command procedure and I should be using UTC$TIME_SETUP.COMn >oH >For me, it didn't work either. Only one system (with DECnet-Plus DECdtsK >still running because I forgot to exclude DECdts from the startup - I haveeF >no longer a DECdts time server, NTP is now the method) did switch the1 >timezones correctly (like all the years before).l > H >All other (V7.3 w/ DTS ECO) systems stayed on DST until I switched themG >by hand (setting the time and redefining all timezone system logicals)c >sA >I was very disappointed (and I'm curious why this did happen)...6  < Bug found. I forgot to add AUTO_DLIGHT_SAV to MODPARAMS.DAT. Shame on me...   -- e< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888W< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------    Date: 31 Oct 2001 11:39:20 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris).! Subject: Re: Undo disk Initializev= Message-ID: <cf15391e.0110311139.1385ef92@posting.google.com>a  A The SALVAGE utility was written (by Al Meier, IIRC) for just this/< purpose (recovering as much as possible after an inadvertentC INITIALIZE operation).  Your support center should have access to a  copy of the program.  ? This topic was also discussed in this newsgroup under the titlenE "unINIT a disk? :-(" in 1999, according to a search using Google.com.eC -------------------------------------------------------------------hC Keith Parris | parris at encompasserve dot org | VMS consulting on: C Clusters, Disaster Tolerance, Internals, Performance, Storage & I/O    ------------------------------  # Date: Wed, 31 Oct 2001 19:51:29 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)! Subject: Re: Undo disk Initialize 3 Message-ID: <5DYD7.1169$RL6.17200@news.cpqcorp.net>r  q In article <cf15391e.0110311139.1385ef92@posting.google.com>, keithparris_NOSPAM@yahoo.com (Keith Parris) writes:sB :The SALVAGE utility was written (by Al Meier, IIRC) for just this= :purpose (recovering as much as possible after an inadvertente :INITIALIZE operation)...e  L   Its an *optical disk* here, folks.  It may or may not be read-write media.K   (An initialize on write-once media has quite different behaviour than an  -   initialize on read-write/rewritable media.)     N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 31 Oct 2001 11:31:00 -08001 From: jason_odonnell@erinet.com (Jason O'Donnell)T# Subject: Re: Unix-based, VMS-based?c< Message-ID: <5c8ffd05.0110311131.e34d7bd@posting.google.com>  N > What is "unix-based" software and "vms-based" software?  That is, aside fromI > the obvious suggestion that one was developed on a particular platform._  A Basically, most programs are written emphasizing the advantageousEC features of the kernel on which they are developed.  In some cases,SC the processing paradigm in one OS is not efficient when the code ish ported to another OS.   ; The UNIX operating system has enjoyed tremendous growth andi; development recently and exists in many different flavors. CC Fortunately for UNIX, the different versions operate very similarlyaC and porting codes between flavors is often trivial and without side3 effect.0  B Unfortunately (to me as I am an OpenVMS fanatic), I think there is@ significantly less development on OpenVMS.  So sometimes new andA "standard" processes show up first on UNIX platforms.  One of the F "nice" things about UNIX is that it is relatively inexpensive to startB new processes.  So, a lot of UNIX development uses the paradigm ofD creating, terminating, and recreating sub-processes.  Unfortunately,@ process creation and deletion is significantly more expensive on OpenVMS.  Soooh  A If you use an application that is an integral part of your system A (such as say an IP stack) that was originally developed on a UNIXnC platform and ported straight to OpenVMS without design changes, you8C will encounter significant performance differences between it and ah' competing product developed on OpenVMS.o   JMOD( Just another stupid view of the world...   ------------------------------  # Date: Wed, 31 Oct 2001 18:50:54 GMT 1 From: "Mark D. Jilson" <jilly@clarityconnect.com>:* Subject: Re: VMS721_Mount96-v0300 Question2 Message-ID: <3BE0484E.7EF02264@clarityconnect.com>  E I would expect that it hasn't been released yet but will be soon.  WenD are working on our patch process to make this type of occurance less  frequent so please bear with us.   Rick Dyson wrote:e > M > In the docs for this ECO, it mentions a remedial kit that is recommended isu >  >         VMS721_CLIUTL-v0200g > " > However, I can only find -v0100. > P > Can anyone address whether this is a typo, -v0200 is missing from the servers,0 > or -v0200 is coming and just not released yet? > 	 > Thanks!  > Rick   -- tD 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: Thu, 01 Nov 2001 03:08:40 GMTo& From: "john nixon" <jnixon@cfl.rr.com>* Subject: Re: VMS721_Mount96-v0300 Question? Message-ID: <Y03E7.585476$8c3.90934900@typhoon.tampabay.rr.com>s  K So; do we use the V0100 kit, or do we wait for the one the Mount96 kit asks. for?  L It was getting a little frustrating.  I saw a fibre-scsi kit which I thoughtL I should install on my new ES40s.  I read the cover letter, and found that IJ should also apply the SYS-V1100 kit and the MOUNT96 kit.  The cover letterI for MOUNT96 said I also  needed the SYS1100, and the CLIUTL-V0200 kit.  IhJ was wondering what the CLIUTL kit was going to require, so I spent quite aI bit of time looking for it, but I couldn't find it.  I thought I was justj8 being dense, so I kept looking and checking my spelling.  H (Now, back to trying to find out why my ES40 crashes every time I try toK start DECPS  (Actually, C.A.'s Adviseit).  It crashes when connecting SWA0:wE Now, I have to figure out how to create a dumpfile on my fibre disk.)   < "Mark D. Jilson" <jilly@clarityconnect.com> wrote in message, news:3BE0484E.7EF02264@clarityconnect.com...G > I would expect that it hasn't been released yet but will be soon.  WebF > are working on our patch process to make this type of occurance less" > frequent so please bear with us. >a > Rick Dyson wrote:a > >CL > > In the docs for this ECO, it mentions a remedial kit that is recommended is > >e > >         VMS721_CLIUTL-v02005 > >n$ > > However, I can only find -v0100. > > I > > Can anyone address whether this is a typo, -v0200 is missing from the  servers,2 > > or -v0200 is coming and just not released yet? > >0 > > Thanks!D > > Rick >e > --F > Jilly - Working from Home in the Chemung River Valley - Lockwood, NY/ > - jilly@clarityconnect.com - Brett Bodine fang- > - Mark.Jilson@Compaq.com - since 1975 or soC- > - http://www.jilly.baka.com               -f >n   ------------------------------  # Date: Wed, 31 Oct 2001 20:41:29 GMT  From: LBohan@dbc.spam_less..comV- Subject: VMSMAIL file, on a write-locked disk 8 Message-ID: <dcn0utsaov9be9ds63obfdrmrho7i3sibj@4ax.com>  @ this suprised me.   probably I ran into this before, and forgot.  - I was about put a couple of years of VMS mailD6 onto a CD-R.    and it looks like idea that won't fly.  . Can anyone here think of a clever work-around?     $  mount/over=id/noass dka500:* %MOUNT-I-WRITELOCK, volume is write locked. %MOUNT-I-MOUNTED, TEST1 mounted on _LF$DKA500:  ) $  DIR/WID=FI=40)/SIZ=ALL/DAT/NOHEA/NOTRAI" DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAIC DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAI;1  30/32  4-MAY-2000 23:29:08.08a   $  MAILn1 MAIL> SET FILE DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAISC %MAIL-E-OPENIN, error opening DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAI asi inpute) -RMS-E-WLK, device currently write lockedc MAIL>  Exit    $  MLS :== $T_EXE:MLSEARCH.EXE 9; $  MLS /file=DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAI INET foobar C %MAIL-E-OPENIN, error opening DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAI asl inputi) -RMS-E-WLK, device currently write locked-F %MLSEARCH-W-OPENIN, Error opening DKA500:[PROD.LOG.MAIL_LDB]MAIL.MAI;1	 for inputn) -RMS-E-WLK, device currently write lockedo# %MLSEARCH-E-NOFILES, No files found # %MLSEARCH-E-NOFILES, No files foundi $  D   ------------------------------  # Date: Wed, 31 Oct 2001 20:56:00 GMTl2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)1 Subject: Re: VMSMAIL file, on a write-locked diskt3 Message-ID: <AzZD7.1173$RL6.17222@news.cpqcorp.net>i  Z In article <dcn0utsaov9be9ds63obfdrmrho7i3sibj@4ax.com>, LBohan@dbc.spam_less..com writes:  ; :I was about put a couple of years of VMS mail onto a CD-R.z' :and it looks like idea that won't fly.c : / :Can anyone here think of a clever work-around?   J   AFAIK, said clever workaround would probably involve patching MAIL.  :-)K   Otherwise, you get to haul the entire contents of the archive out onto a o   read-write area.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Wed, 31 Oct 2001 21:49:02 GMT - From: goathunter@goatley.com (Hunter Goatley)i1 Subject: Re: VMSMAIL file, on a write-locked disk 0 Message-ID: <3be07028.94023849@news.process.com>  N On Wed, 31 Oct 2001 20:56:00 GMT, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote:  [ >In article <dcn0utsaov9be9ds63obfdrmrho7i3sibj@4ax.com>, LBohan@dbc.spam_less..com writes:h >i< >:I was about put a couple of years of VMS mail onto a CD-R.( >:and it looks like idea that won't fly. >:0 >:Can anyone here think of a clever work-around? >gK >  AFAIK, said clever workaround would probably involve patching MAIL.  :-)iL >  Otherwise, you get to haul the entire contents of the archive out onto a  >  read-write area.? >>I Actually, there is a way to do it so that only the main MAIL.MAI file has J to be copied to a read-write area.  The external MAIL$*.MAI files can stayH on the CD.  You do this by faking MAIL out about where the file is.  ForJ example, if your MAIL files on CD are in DKA400:[HUNTER.MAIL] and you haveA a read/write area DKA100:[HUNTER.MAIL.ARCHIVED], you can do this:   D    $ copy dka400:[hunter.mail]mail.mai dka100:[hunter.mail.archived]@    $ define/trans=concealed yyz dka100:[hunter.mail.archived.],-           dka400:[hunter.mail]	    $ MAILc      MAIL> set file yyz:[000000]  P You can then read and access all the mail, as MAIL will use YYZ:[000000] for the; device and directory and find the external files on the CD.y  M Similar games can be played with just the device names if the directories aree the same, etc. Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ 9 goathunter@goatley.com     http://www.goatley.com/hunter/    ------------------------------   Date: Wed, 31 Oct 2001 15:46:49d& From: "Sandy" <sandycanada@canada.com>- Subject: WARNING: PROTECT YOUR NAME IN CANADA-8 Message-ID: <iss.24dc.3be08b06.3cbe.1@mx2.east.saic.com>   Dear name owner,  > I am contacting you on behalf of CanadaSubmit.ca - A Canadian 4 Domain Name Affiliate. (http://www.canadasubmit.ca).  B Are you planning on doing business in Canada now or in the future?  = Do you want to attract Canadian traffic and commerce to your p website?  ; Do you have brand names, corporate names or ideas that you E  would like to protect in Canada?  < If so, you should register your .CA domain names as soon as " possible before someone else does.  @ The .CA domain was recently made more available to the public.  J Many of the best names, including your name, are still likely available.  H Because the .CA domain is a North American - Country Domain it has been G estimated that over 3.5 million names will be registered over the next i
 36-48 months.   > FACT: There will never be a better opportunity to secure your  names in Canada than right now.L  ' Start by searching for availability at:e http://www.canadasubmit.ca  # All prices are in Canadian Dollars.    Regards, Sandyb. ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  ~  Domain Protection Services Dept.2 CanadaSubmit.ca - A Canadian Domain Name Affiliate# Website: http://www.canadasubmit.can  < ............................................................B If you are already an owner of a .CA domain name please disregard , this message as it was not intended for you.  < ............................................................= If you want to be removed from this mailing list please email 7 remove@canadasubmit.ca with your email address in the.  ( first line of the body of the message.  C This email is strictly meant for informative purposes regarding thev: protection of any names you may want to register in Canada" provided the requirements are met.   ------------------------------   Date: 1 Nov 2001 01:39:42 +0100i* From: eplan@kapsch.net (Peter LANGSTOEGER)6 Subject: Re: [VMS V7.3 VAX] my first crash since years* Message-ID: <3be099ce$1@news.kapsch.co.at>  W In article <3bde7c5c$1@news.kapsch.co.at>, eplan@kapsch.net (Peter LANGSTOEGER) writes: G >Unfortunately, CLUE data is not available (I wonder why) and I have tow< >investigate this, too (but surely not this or next week)...   I now have the CLUE info:l  D $ clue /BIN=CLUE$HISTORY.DATA /LOCAL SYS$SYSROOT:[SYSEXE]SYSDUMP.SAVL CLUE Version: V1.9                            Date:   1-NOV-2001 01:33:40.60I                                               ACAS   Uptime:   1 10:58:23o  A CLUE /BIN=CLUE$HISTORY.DATA/LOCAL SYS$SYSROOT:[SYSEXE]SYSDUMP.SAV   , Dump File: SYS$SYSROOT:[SYSEXE]SYSDUMP.SAV;1  + Selective Dump:    Dump Flags    = 020401C0 ' Current Process Name             = NMBDn$ Current IPL                      = 2' Dump file version                = 0530gA # memory pages in dump           = 40963  Physical memory = 24 MBo+ SID                              = 14000006e: Crash time                       = 29-OCT-2001 16:39:49.86) Current Access mode              = KERNELm% Number of processes in dump      = 29h9 Node Name                        = ACAS     Not Clusteredm( Crash CPU/Primary CPU            = 0 / 0- CPU  0 Crash Code 3C4,Crash Type = SSRVEXCEPTt$ Bitmask of CPUs available        = 1$ Bitmask of CPUs active           = 1$ CPU Bitmask completing bugcheck  = 1' Current image:                   = NONE-6 CPU Type                         = VAXstation 4000-VLC' VMS Version                      = V7.3   8                          Symbol     Value       Contents  8                  EXE$GL_MCHKERRS -> 800044F0  = 000000008                   EXE$GL_MEMERRS -> 800044F4  = 000000008                     EXE$GL_STATE -> 80008490  = 00003FFEG                  EXE$GQ_BOOTTIME -> 80004460  = 17-OCT-2001 15:25:31.47.8                     EXE$GL_FLAGS -> 800042F0  = 024168658                   IO$GL_UBA_INT0 -> 800044F8  = 000000008                     MPW$GB_IOLIM -> 800080AA  = 000404048               PMS$GL_NPAGDYNEXPF -> 80004700  = 000000008                  PMS$GL_NPAGDYNF -> 8000491C  = 000000008             PMS$GL_NPAGDYNFPAGES -> 80004920  = 000000008               PMS$GL_NPAGDYNREQF -> 8000492C  = 000000008                   PMS$GL_PAGDYNF -> 80004704  = 000000008              PMS$GL_PAGDYNFPAGES -> 80004924  = 000000008                PMS$GL_PAGDYNREQF -> 80004934  = 000000008                   SCH$GL_FREECNT -> 80004018  = 000037A28                    SCH$GL_PFRATL -> 800080C4  = 00000000     SBR 01752C00  SLR 0001B880  , Processor Information for Crash CPU  0 (Hex)  F    R0 00020009   R1 7FFE775C   R2 816D93C8   R3 00000001   R4 816D93E8F    R5 8163AD18   R6 00000001   R7 00000048   R8 00000001   R9 8163AD00F   R10 4801AE63  R11 8166A28A   AP 7FFE7738   FP 7FFE7720   SP 7FFE7720F    PC 810D7FE3  PSL 00020000  KSP 7FFE7720  ESP 7FFE9800  SSP 7FFECA44F   USP 7FEAECFC  ISP 82126200 P0BR 82A01400 P1BR 82232200 P0LR 000010B78  P1LR 001FF571 PCBB 00C0D620 SCBB 0174A600 SISR 00000000   ASTLVL  = 00000004 ICCS    = 00000040   CPU Dependent Registers:   # Regs = 01 (Hex)e AB5E294F  4 Spinlocks owned by CPU 00 (Hex) (CRASH CPU)     NONE    $  Summary of System at time of Crash:  L  PCB    State CPU Process Name     Username     EPID    Pri PHD        Wkset  K 81156FA0   HIB    SWAPPER                       00000081 16 81156E00      0oK 81692740   HIB    IPCACP           SYSTEM       00000086 10 821A6A00     95eK 81693940   HIB    ERRFMT           SYSTEM       00000087  8 82744200    113pK 81695440   HIB    OPCOM            SYSTEM       00000089  6 82223A00    113 K 815B2B80   HIB    AUDIT_SERVER     AUDIT$SERVER 0000008A 10 82262200    251aK 81690340   HIB    JOB_CONTROL      SYSTEM       0000008B 10 822A0A00    1482K 81690C40   HIB    QUEUE_MANAGER    SYSTEM       0000008C  9 822DF200    503c; ACAS$DKA0:[SYS0.SYSCOMMON.][SYSEXE]QMAN$QUEUE_MANAGER.EXE;19K 81692080   HIB    SECURITY_SERVER  SYSTEM       0000008D 10 8231DA00    517rK 81693DC0   LEF    DNS$ADVER        SYSTEM       0000008E  5 8235C200   2358vK 81693B80   HIB    LES$ACP_V30      SYSTEM       0000008F  8 8239AA00    274 4 ACAS$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LES$ACP_V30.EXE;1K 81694B40   HIB    NET$ACP          DNA$SessCtrl 00000090  6 823D9200    558oK 81690580   HIB    REMACP           SYSTEM       00000091 10 82494A00     58-K 81690A00   HIB    NET$EVD          SYSTEM       00000092  6 82456200    273n= ACAS$DKA0:[SYS0.SYSCOMMON.][SYSEXE]NET$EVENT_DISPATCHER.EXE;1nK 816907C0  HIBO    NET$MOP          SYSTEM       00000093  4 00000000    4791K 81694D80   HIB    LATACP           SYSTEM       00000094 14 82129A00    186RK 816946C0   HIB    TCPIP$INETACP    INTERnet     00000095  9 824D3200    315rK 81693700   LEF    TCPIP$FTP_1      TCPIP$FTP    00000096 10 82511A00     60_K 81695B00   LEF    TCPIP$NTP_1      TCPIP$NTP    00000097  9 82550200    317yK 81694240   HIB    TCPIP$PWIP_ACP   SYSTEM       00000098 10 8258EA00    862rK 81690100   COM    TCPIP$SNMP_1     TCPIP$SNMP   00000099  2 825CD200    267 K 81692E00   LEF    TCPIP$XDM_1      TCPIP$XDM    0000009A 10 8260BA00     68eK 81691C00   COM    TCPIP$OS_MIBS    TCPIP$SNMP   0000009D  2 8264A200    348wK 8168FEC0   LEF    TCPIP$HR_MIB     TCPIP$SNMP   0000009E  2 82688A00    415-K 816910C0   HIB    DECW$SERVER_0    SYSTEM       000000A0  7 82705A00   1313wK 81692980  LEFO    DECW$LOGINOUT    <login>      000000A1  4 00000000    335-K 81695D40   HIB    TISTL            SYSTEM       000000A2  5 826C7200    214 K 816A8180   HIB    VPM_SERVER       SYSTEM       000000AB 15 82976A00    2592K 8169CB00   HIB    SMISERVER        SYSTEM       000000AC  9 829B5200     58cK 816D9340   CUR  0 NMBD             SYSTEM       000000B1 16 829F3A00   1096iK 816A9540   HIB    HTTPd:80         HTTP$SERVER  000000B2  6 82938200     68TK 81671D80   HIB    MX SMTP Server   SYSTEM       0000024F  6 82168200     93i% ACAS$DKA0:[MX.][EXE]SMTP_SERVER.EXE;2gK 816934C0   LEF    DECW$TE_00D2     EPLAN        000000D2  6 821E5200   1284cK 81671B40   LEF    EPLAN            EPLAN        000000D3  7 82417A00    671nK 81694000   HIB    MX FLQ Manager   SYSTEM       000000D9  6 8287CA00    185sK 816B3AC0   HIB    MX Router        SYSTEM       000000DA  6 827C1200    161m! ACAS$DKA0:[MX.][EXE]MX_ROUTER.EXElK 81695680   HIB    MX Local         SYSTEM       000000DB  6 828BB200    146 K 816C6140   HIB    MX SMTP          SYSTEM       000000DC  6 827FFA00    127 K 816D2180   HIB    MX SMTP#2        SYSTEM       000000DD  6 8283E200    163l    Code Modules:  8                      Module Name         Address  Length  :                     TCPIP$PROXY_SERVICES 807CEE00 00009600:                  TCPIP$INTERNET_SERVICES 807D8A00 00111400:                                NET$MOPS0 809E6A00 00000C00:                     NET$LOOP_APPLICATION 808EAE00 00002200:                                NET$OSVCM 808ED200 0000B200:                        NET$TRANSPORT_OSI 808F8C00 0003F000:                               NET$TPCONS 80938200 00012600:                        NET$TRANSPORT_NSP 8094AA00 00013400:                           NET$ROUTING_ES 8095E200 0001DC00:                            LES$NETMANLDR 8097C200 0000B800:                               LES$NETMAN 80987C00 00002400:                               NET$CSMACD 8098A400 00003C00:                        SYS$NAME_SERVICES 8098E200 0001BE00:                      NET$SESSION_CONTROL 809AA800 0003C200:                                NET$ALIAS 809E8000 00007400:                              LES$LES_V30 809EF800 00004E00:                              NET$MESSAGE 80F76E00 00006C00:                                   SYSMSG 80F7DC00 00046A00:                               SYSLDR_DYN 8133F000 00002000:                       DDIF$RMS_EXTENSION 81341400 00001200:                   RECOVERY_UNIT_SERVICES 81342800 00000800:                                      RMS 80FC4800 0002CA00:                                  SYS$NTA 81060600 00000200:                         VAXCLUSTER_CACHE 81041A00 00004C00:                     SYS$NETWORK_SERVICES 81046C00 00017800:                         SYS$UTC_SERVICES 81060C00 00000E00:                 SYS$TRANSACTION_SERVICES 81062000 0000DE00:                         SYS$IPC_SERVICES 81070200 0001E000:                                   CPULOA 8108E400 00005400:                          LMF$GROUP_TABLE 81095C00 00001A00:                               SYSLICENSE 81097A00 00003200:                                  F11BXQP 8109B000 0001F800:                        SNAPSHOT_SERVICES 810BB000 00000C00:                                SYSGETSYI 810BC200 00002000:                                SYSDEVICE 810BE600 00002A00:                         MESSAGE_ROUTINES 810C1600 00006200:                                EXCEPTION 810D7E00 0000A800:                            LOGICAL_NAMES 810E2E00 00023800:                                 SECURITY 81107000 00009A00:                                  LOCKING 81111200 00006E00:                          PAGE_MANAGEMENT 81118A00 0000A000:                   WORKING_SET_MANAGEMENT 8112F800 00005E00:                         IMAGE_MANAGEMENT 81136000 00003600:                     EVENT_FLAGS_AND_ASTS 81139C00 00002200:                              IO_ROUTINES 8113C800 00010600:                       PROCESS_MANAGEMENT 8114E800 0000DA00:                                 ERRORLOG 81330800 00000C00:                             PRIMITIVE_IO 81331A00 00001200:               SYSTEM_SYNCHRONIZATION_UNI 81333000 00004400:                    SYSTEM_PRIMITIVES_MIN 81337A00 00003E00:                    BUGCHECK_CODE_OVERLAY 807CEE00 00003964:                               ECP$DRIVER 81705580 000013C0:                                 RMDRIVER 817B0300 00006240:                                MADDRIVER 817AC800 00003B00:                                DADDRIVER 81710480 00001E40:                               LASTDRIVER 817A7E00 00004A00:                                 WSDRIVER 816CBDC0 00000640:                                GFBDRIVER 817A4D40 000030C0:                                 IKDRIVER 817A26C0 00002680:                                 IMDRIVER 816F3280 00000A40:                                 INDRIVER 8179F580 00003140:                               PWIPDRIVER 8179C180 00003400:                                 TNDRIVER 81730AC0 00009440:                               TCPIP$BGDR 81697D80 000004C0:                                 LTDRIVER 81743BC0 0000EF00:                               LAT$RATING 816C2DC0 000005C0:                                RTTDRIVER 816F4840 00000B80:                                 CTDRIVER 816FA8C0 00002980:                                 OSDRIVER 8173A340 00009880:                               NET$DRIVER 81729E80 00006C40:                               PIPEDRIVER 816C2280 00000580:                                 FTDRIVER 816F1400 00000A00:                                 SODRIVER 81701C00 000012C0:                                 ESDRIVER 81706940 000083C0:                                 YEDRIVER 816F6000 00000DC0:                                 DKDRIVER 818243C0 00005036:                                PKCDRIVER 8181DD80 0000663F:                                 TTDRIVER 81817FC0 00005D85:                                 OPERATOR 8133A000 0000056C:                                 NLDRIVER 810BE683 000001AB:                                 MBDRIVER 810BE600 000019A0:                                  CLIMAGE 7FF59600 0001CDFF:                                   SYSLOA 81815F00 00002090:                                  F11BXQP 00000000 00000000:                           F11BXQP_IMPURE 7FF76400 80089C00:                           CTL$GQ_DBGAREA 7FFF0000 0000FFFF:                             P1SYSVECTORS 7FFEDE00 000009FF:                                   FPEMUL 8180EFC0 00002ABC:                                  VAXEMUL 81811A80 0000367F:                               PAGED_POOL 813FB400 0018D3FF:                            NONPAGED_POOL 81588800 002FAE00:                           ALLOCATABLE_S0 8000AF84 0133D07B   Contents of KERNEL Stack:l  % 7FFE7700 8163AD00 NONPAGED_POOL+B2500n 7FFE7704 4801AE63e% 7FFE7708 8166A28A NONPAGED_POOL+E1A8A-$ 7FFE770C 7FFE7738 CTL$GL_KSTKBAS+538$ 7FFE7710 7FFE7720 CTL$GL_KSTKBAS+520$ 7FFE7714 7FFE7718 CTL$GL_KSTKBAS+5181 7FFE7718 810D7FE3 <= PC EXCEPTION+1E3 EXE$EXCPTNE  7FFE771C 00020000-   7FFE7720 00000000 <= SP <= FP % 7FFE7724 00000000 <= Mask/PSW (CALLG)  7FFE7728 7FEAED38 <= Saved AP 0 7FFE772C 7FFE77E4 <= Saved FP CTL$GL_KSTKBAS+5E4* 7FFE7730 80000014 <= Saved PC EXE$QIOW_3+42 7FFE7734 810DA8E7 EXCEPTION+2AE7 EXE$CONTSIGNAL+7C& 7FFE7738 00000002 <= Condition Handler< 7FFE773C 7FFE775C <= Signal Array address CTL$GL_KSTKBAS+55C? 7FFE7740 7FFE7744 <= Mechanism Array address CTL$GL_KSTKBAS+544 . 7FFE7744 00000004 <= Mech Array Argument Count: 7FFE7748 7FFE77E4 <= FP of estab. Frame CTL$GL_KSTKBAS+5E4" 7FFE774C FFFFFFFD <= Depth of Scan$ 7FFE7750 00000001 <= R0 at exception$ 7FFE7754 00000000 <= R1 at exception# 7FFE7758 000008F8 <= Flags Longwordg0 7FFE775C 00000005 <= Signal Array Argument Count1 7FFE7760 0000000C <= SS$_ACCVIO, Access Violation 2 7FFE7764 00000001 <= Reason Mask: Length Violation- 7FFE7768 4801AE67 <= Faulting Virtual AddresssB 7FFE776C 8110D67F <= Exception PC SECURITY+667F EXE$CHKPRO_INT+2AE" 7FFE7770 00C20008 <= Exception PSL% 7FFE7774 8163AD04 NONPAGED_POOL+B2504. 7FFE7778 00000002k% 7FFE777C 8166A280 NONPAGED_POOL+E1A80F 7FFE7780 00000000r% 7FFE7784 8163AD00 NONPAGED_POOL+B2500.$ 7FFE7788 7FFE77B4 CTL$GL_KSTKBAS+5B4 7FFE778C 00000000.& 7FFE7790 816D9340 NONPAGED_POOL+150B40& 7FFE7794 816AE600 NONPAGED_POOL+125E00 7FFE7798 7FFCFEA0] 7FFE779C 00000031= 7FFE77A0 FFFFFFFF0 7FFE77A4 FEB00000v 7FFE77A8 00000031k 7FFE77AC 00000003 G 7FFE77B0 81339C73 SYSTEM_PRIMITIVES_MIN+2273 EXE$CHECK_DEVICE_ACCESS+36e 7FFE77B4 00000001  7FFE77B8 000004050 7FFE77BC 00000000i 7FFE77C0 00000000d 7FFE77C4 7FFCFEA0f 7FFE77C8 00000000 & 7FFE77CC 816D93C8 NONPAGED_POOL+150BC8% 7FFE77D0 8163AD00 NONPAGED_POOL+B2500  7FFE77D4 7FFCFEA0t 7FFE77D8 00000000G 7FFE77DC 00C00001t2 7FFE77E0 81145BF9 IO_ROUTINES+93F9 EXE$CARRIAGE+65 7FFE77E4 00000000 <= FP.% 7FFE77E8 00000000 <= Mask/PSW (CALLG)- 7FFE77EC 7FEAED38 <= Saved AP1 7FFE77F0 7FEAECFC <= Saved FPy= 7FFE77F4 810D8260 <= Saved PC EXCEPTION+460 EXE$EXCEPTION+228D+ 7FFE77F8 7FFEDE06 P1SYSVECTORS+6 SYS$QIOW+6. 7FFE77FC 03C00000e      Instruction at PC 8110D67F   5 EXE$CHKPRO_INT+2AE       8110D67F BITL    #08,04(R10)m   Instructions around PC 8110D67Fi   Invalid opcode AB @8110D657o< EXE$CHKPRO_INT+287       8110D658 BGTRU   EXE$CHKPRO_INT+29B< EXE$CHKPRO_INT+289       8110D65A BLSSU   EXE$CHKPRO_INT+23C: EXE$CHKPRO_INT+28B       8110D65C CASEB   -(AP),#00,08(R9) Invalid opcode 56 @8110D673n2 EXE$CHKPRO_INT+2A3       8110D674 MOVF    #16,(R1)/ EXE$CHKPRO_INT+2A6       8110D677 MOVL    R0,R6e0 EXE$CHKPRO_INT+2A9       8110D67A TSTL    60(R9)< EXE$CHKPRO_INT+2AC       8110D67D BEQL    EXE$CHKPRO_INT+2EC5 EXE$CHKPRO_INT+2AE    PC>8110D67F BITL    #08,04(R10)a< EXE$CHKPRO_INT+2B2       8110D683 BNEQ    EXE$CHKPRO_INT+2EC? EXE$CHKPRO_INT+2B4       8110D685 BLBS    R6,EXE$CHKPRO_INT+2BF 5 EXE$CHKPRO_INT+2B7       8110D688 BITL    #10,04(R10)p< EXE$CHKPRO_INT+2BB       8110D68C BNEQ    EXE$CHKPRO_INT+2EC< EXE$CHKPRO_INT+2BD       8110D68E BRB     EXE$CHKPRO_INT+2C55 EXE$CHKPRO_INT+2BF       8110D690 BITL    #20,04(R10)d    8 Failing PC is 8110D67F SECURITY+667F  EXE$CHKPRO_INT+2AE    Canasta Parameters:   VMS Version     : 7.3  Crash Type      : SSRVEXCEPT Current Process : NMBD Current Image   : NONE CPU Type        : 4000-VLC SID             : 14000006 Signal Array cnt: 5a Exception par #1: 0000000C Exception par #2: 00000001 Exception par #3: 4801AE67 Exception PC    : 8110D67F Exception PSL   : 00C20008 Failing Inst    : BITL  Code Module     : EXE$CHKPRO_INT Offset          : 2AE     9 Adding entry to binary file CLUE$OUTPUT:CLUE$HISTORY.DATA  Incompatible binary file: 174.  1-NOV-2001 01:34:01.60y     -- r< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888 < <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------   End of INFO-VAX 2001.607 ************************