1 INFO-VAX	Sat, 02 Jun 2001	Volume 2001 : Issue 304       Contents:, Re: "Talk Baq" to Compaq - or perhaps to Sun Re: CD-RW on a VMS system.  CHARON-VAX: Cannot open disk E::$ CHARON-VAX: change keyboard mapping?# CHARON-VAX: Help/mess does not work 2 Re: Function to measure time for command execution Re: hszterm software6 Re: Size of VMS patch kits and new compression options Re: The future of VMS  Re: University in USA ' Wanted:H.323 protocol stack for OpenVMS ) Re: [OT] Current Microsoft v DOJ status ? ) Re: [OT] Current Microsoft v DOJ status ? ) Re: [OT] Current Microsoft v DOJ status ?   F ----------------------------------------------------------------------  $ Date: Sat, 2 Jun 2001 01:39:55 -0500* From: "T. S. Murphy" <murphyts@swbell.net>5 Subject: Re: "Talk Baq" to Compaq - or perhaps to Sun . Message-ID: <0T%R6.497$yt.10594@nnrp1.sbc.net>  6 "Christof Brass" <brass@infopuls.com> wrote in message& news:3B182808.FD1B013C@infopuls.com...  = > And one remark about your a little strange idea of the IA32 A > coming close to real enterprise computing power. Would you like @ > to tell me how many IA32 CPUs are able to work together in oneB > server? I thought that the limit is 8 or 12. The ability to linkA > is a major design aspect. Do you know if the IA64 is any better  > in that respect?  F Intel's ASCI Red supercomputer has 9,632 Pentium Pro CPU's, and is the( second fastest supercomputer ever built.  I IBM's xSeries 430 server can contain up to 64 Pentium III Xeon CPU's in a  single node.  G There is nothing architecturally or microarchitecturally limiting IA-32 L CPU's to a small number of CPU's. The reason shared bus Intel systems are soL prevalent is because they are by far cheaper than other MP solutions offeredJ by other vendors, but are certainly not the only MP soultion available. MP) is a platform problem, not a CPU problem.   E Of course IA64 scales well. Intel claims it is scalable to 512 CPU's. + There's a reason it's being positioned Sun.    ------------------------------  # Date: Sat, 02 Jun 2001 13:50:38 GMT + From: Jeff Campbell <jcampbell@ins-msi.com> # Subject: Re: CD-RW on a VMS system. + Message-ID: <3B18E8B8.AB552792@ins-msi.com>    Comment interspersed.    "Leigh G. Bowden" wrote: > M > This is an update of something I posted a couple of months ago. I shouldn't I > really complain about freeware I suppose but trying to find information A > about writing to a CD-RW from VMS has basically been confusing, : > contradictary and a litany of busted websites and links. > > > System: VAXstation 4000/60 with OpenVMS 6.2 and Y2K patches.' > CDRECORD: 1.8a9 (only doco is 1.8.1). J > CD-RW: Plextor Plexwriter 12/4/32 SCSI-2 (HD50) in a tabletop enclosure.D > This Plextor is the closest I could find that matched the CDRECORDN > information. It works as I have attached it to an NT system and it was fine. > D > The Plextor has some selector switches on the back for parity (on)J > termination (on -  last in chain), test (off) and block. The manual saysM > that turning this on makes it ready for Unix environments. There is nothing L > more in the manual about this than that. Everything below has been done in" > the Unix and "Windows" settings. > M > * At the console prompt the VAXstation recognises the device and that it is  > a Plextor device.  > L > * VMS recognises the device and recognises that it is a Plextor. See below1 > but you'll need courier font to see it aligned.  > B > Disk PHJ$DKA200:, device type PLEXTOR CD-R PX-W124TS, is online, > file-oriented 2 >     device, shareable, error logging is enabled.> >     Error count                    1    Operations completed > 4 3 >     Owner process                 ""    Owner UIC 
 > [SYSTEM]2 >     Owner process ID        00000000    Dev Prot > S:RWPL,O:RWPL,G:R,W = >     Reference count                0    Default buffer size  > 512  > N > * I have not been able to mount anything with this drive though with variousJ > combinations of MOUNT/MEDIA=CDROM/UNDEFINED_FAT=STREAM:2048 etc etc etc.M > Some of these commands are from the VMS FAQ. Any form of mount generates an E > error on the device count. An analysis of the error is shown below.  > F > ---------------------- Forwarded by Leigh G Bowden/IT/North East/RAC
 > Motoring: > Services on 29/05/2001 15:04 --------------------------- > 5 > "PHJ::BOWDENL"@re1.rac.co.uk on 29/05/2001 14:59:14 : > To:   Leigh G Bowden/IT/North East/RAC Motoring Services
 > Subject: > G > V A X / V M S        SYSTEM ERROR REPORT         COMPILED 29-MAY-2001 
 > 13:57:47L >                                                                       PAGE > 1.0 > ******************************* ENTRY     944.! > ******************************* G > ERROR SEQUENCE 26.                              LOGGED ON:        SID 
 > 12000003G > DATE/TIME 29-MAY-2001 13:56:26.74                            SYS_TYPE 
 > 04140002  > SYSTEM UPTIME: 0 DAYS 03:50:39L > SCS NODE: PHJ                                                 VAX/VMS V6.29 > DEVICE ERROR  KA46  CPU FW REV# 3.  CONSOLE FW REV# 1.4 * > GENERIC DK SUB-SYSTEM, UNIT _PHJ$DKA200:! >        HW REVISION     34302E31 ; >                                        HW REVISION = 1.04 ! >        ERROR TYPE            06 I >                                        INVALID MODE SENSE DATA RETURNED ! >        SCSI ID               02 5 >                                        SCSI ID = 2. ! >        SCSI LUN              00 6 >                                        SCSI LUN = 0.! >        SCSI SUBLUN           00 9 >                                        SCSI SUBLUN = 0. ! >        PORT STATUS     00000001 L >                                        %SYSTEM-S-NORMAL, NORMAL SUCCESSFUL4 >                                         COMPLETION! >        SCSI CMD        003F001A ! >                            00FF 3 >                                        MODE SENSE ! >        SCSI STATUS           00 - >                                        GOOD  > MODE SENSE DATA ! >        MEDIUM TYPE           00 < >                                        DEFAULT MEDIUM TYPE! >        FLAGS                 00 6 >                                        WRITE ENABLED! >        BLOCK DESC 1.   00000000 ! >                        00080000 C >                                        _DEFAULT DENSITY OF MEDIUM ? >                                        _NUMBER OF BLOCKS = 0.     ( >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  > >                                        _BLOCK LENGTH = 2048.    E The "BLOCK" switch is set for Unix or Windows operation. Disk devices < must present a 512 byte block interface to VMS disk drivers.  . Try the "BLOCK" switch in it's other position.  ) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>   ! >        PAGE DESC 1.    0A000601 ! >                        00000000 : >                                        PAGE CODE = 01(X)B >                                        ERROR RECOVERY PARAMETERS9 >                                        _RETRY CNT = 10. > >                                        _CORRECTION SPAN = 0.> >                                        _HEAD OFFSET CNT = 0.E >                                        _DATA STROBE OFFSET CNT = 0. G >                                        _RECOVERY TIME LIMIT = 0. MSEC ! >        PAGE DESC 2.    F0040E02 ! >                        00000000 ! >                        00000000 ! >                        00000000 : >                                        PAGE CODE = 02(X)G > V A X / V M S        SYSTEM ERROR REPORT         COMPILED 29-MAY-2001 
 > 13:57:47L >                                                                       PAGE > 2.L >                                        DISCONNECT/RECONNECT CONTROL PARAMS@ >                                        _BUFFER FULL RATIO = 4.C >                                        _BUFFER EMPTY RATIO = 240. H >                                        _BUS INACTIVITY LIMIT = 0. USECI >                                        _DISCONNECT TIME LIMIT = 0. USEC F >                                        _CONNECT TIME LIMIT = 0. USEC! >        PAGE DESC 3.    C4013205 ! >                        00000008 ! >                        00000000 ! >                        96000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 ! >                        00000000 : >                                        PAGE CODE = 05(X)C >                                        FLEXIBLE DISK DRIVE PARAMS F >                                        _452. K BIT/SEC TRANSFER RATE> >                                        _NUMBER OF HEADS = 8.: >                                        _0. SECTORS/TRACKC >                                        _0. DATA BYTES/PHYS SECTOR B >                                        _NUMBER OF CYLINDERS = 0.F >                                        _START CYL WRITE PRECOMP = 0.J >                                        _START CYL REDUCE WRITE CURR = 0.@ >                                        _DRIVE STEP RATE = 150.E >                                        _DRIVE STEP PULSE WIDTH = 0. @ >                                        _HEAD SETTLE DELAY = 0.= >                                        _MOTOR ON DELAY = 0. > >                                        _MOTOR OFF DELAY = 0.> >                                        _HEAD LOAD DELAY = 0.F >                                        _STARTING SECTOR, SIDE 0 = 0.F >                                        _STARTING SECTOR, SIDE 1 = 0.! >        PAGE DESC 4.    0A000607 ! >                        00000000 : >                                        PAGE CODE = 07(X)1 >                                        RESERVED ! >        PAGE DESC 5.    00000A08 ! >                        00000000 ! >                        00000000 : >                                        PAGE CODE = 08(X)1 >                                        RESERVED ! >        PAGE DESC 6.    0B00060D ! >                        4B003C00 : >                                        PAGE CODE = 0D(X)1 >                                        RESERVED ! >        PAGE DESC 7.    00040E0E ! >                        00000000 G > V A X / V M S        SYSTEM ERROR REPORT         COMPILED 29-MAY-2001 
 > 13:57:47L >                                                                       PAGE > 3.! >                        FF02FF01 ! >                        00000000 : >                                        PAGE CODE = 0E(X)1 >                                        RESERVED ! >        PAGE DESC 8.    0707142A ! >                        23296F73 ! >                        00010D16 ! >                        0D160010 ! >                        45080000 ! >                            4508 : >                                        PAGE CODE = 2A(X)C >                                        VENDOR UNIQUE PAGE FORMATS ! >        UCB$B_ERTCNT          04 = >                                        4. RETRIES REMAINING ! >        UCB$B_ERTMAX          00 = >                                        0. RETRIES ALLOWABLE ! >        ORB$L_OWNER     00010004 < >                                        OWNER UIC [001,004]! >        UCB$L_CHAR      1EC54008 = >                                        DIRECTORY STRUCTURED 6 >                                        FILE ORIENTED1 >                                        SHARABLE 2 >                                        AVAILABLE6 >                                        ERROR LOGGING2 >                                        ALLOCATED> >                                        SOFTWARE "WRITE LOCK"9 >                                        CAPABLE OF INPUT : >                                        CAPABLE OF OUTPUT6 >                                        RANDOM ACCESS! >        UCB$W_STS           0000 ! >        UCB$L_OPCNT     00000000 ; >                                        0. QIO'S THIS UNIT ! >        UCB$W_ERRCNT        0001 < >                                        1. ERRORS THIS UNIT! >        IRP$W_BCNT          0000 A >                                        TRANSFER SIZE 0. BYTE(S) ! >        IRP$W_BOFF          0000 > >                                        TRANSFER PAGE ALIGNED! >        IRP$L_PID       00010012 8 >                                        REQUESTOR "PID"! >        IRP$Q_IOSB      00000001 E >                        000F0000        IOSB, 0. BYTE(S) TRANSFERRED A > ANAL/ERROR/SINCE=29-MAY-2001 13:45:00.00/INCLUDE=DKA200/OUT=T.T  > L > * I haven't really been able to try CDRECORD. I did do a CDRECORD -SCANBUSF > DEV=0,2,0 out of interest and it reported that unable to find device  > DKA002!! Which was a surprise. > M > * I've tried this on a Alphastation 255 and the results are pretty much the = > same except an error is reported as "invalid media format".     
 Jeff Campbell  n8wxs@arrl.net   ------------------------------  % Date: Sat, 02 Jun 2001 10:37:10 +0200 , From: Didier Morandi <Didier.Morandi@gmx.ch>) Subject: CHARON-VAX: Cannot open disk E:: & Message-ID: <3B18A5B6.3D6EE5DF@gmx.ch>  H I have installed a CHARON-VAX demo for Windows (Me). It works fine until: I try to enable CD access (system is a COMPAQ Armada 100S)  A When I remove the # in front of line SET DUA file[2]="\\.\E:" the  console complains with message:   9   DSK:3040: cannot open disk \\.\E:: operation terminated   A The CD is E: and works fine under Windows. Same behaviour with or  without CD in the device.   & Any help would be greatly appreciated. Thanks,    D.   ------------------------------  % Date: Sat, 02 Jun 2001 10:40:32 +0200 , From: Didier Morandi <Didier.Morandi@gmx.ch>- Subject: CHARON-VAX: change keyboard mapping? & Message-ID: <3B18A680.1973E9A8@gmx.ch>  A I did not find how to change the keyboard mapping of the terminal   emulator, if possible of course.  ! Did someone here succeed in this? 5 (are there actually CHARON-VAX users around here?...)    D.   ------------------------------  % Date: Sat, 02 Jun 2001 17:20:05 +0200 , From: Didier Morandi <Didier.Morandi@gmx.ch>, Subject: CHARON-VAX: Help/mess does not work& Message-ID: <3B190424.1F754C67@gmx.ch>  
 When doing a     $ help/mess pkgreqd    I get this:    Message number 05FD8013  (and many others similar)   4 Actually a simple $ help/mess gives the same result. The HELP facility is ok.  G I did not find any 05FD8013 error message. Except the 05FD prefix which G seems to be a VGATHL code "reserved to Digital" (from 4515pro_038.html) C Set watch sez that sys$help:msghlp$library.msghlp$data is accessed.   7 (I recall that Charon-Vax is shipped with OpenVMS 6.2).    Any idea anyone? Thanks,     D.   ------------------------------   Date: 2 Jun 2001 00:42 CDT' From: carl@gerg.tamu.edu (Carl Perkins) ; Subject: Re: Function to measure time for command execution , Message-ID: <2JUN200100422660@gerg.tamu.edu>  : andrew.rycroft@intrinsitech.com (Andrew Rycroft) writes...A }In the UNIX world there is a command "time" which can be used to E }measure the time elapsed, CPU and real, of a command, e.g. # time ls  } + }Is there anyway of doing this within VMS ?  }  }Thanks  }Andrew   G There are, of course, ways of doing this. But there is no equally short K single command that comes as part of the shell. Perhaps the best equivalent K is to create a command proceedure that takes the command to execute as it's H parameter, the proceedure then gets the time, runs the command, and thenH gets the time and calculates the difference. If you define a symbol thatJ runs the command proceedure, it will look pretty much the same. I.E. this:   $ time :== @time_the_command
 $ time dir  I No matter how you slice it, this pretty much requires a command procedure G (or a really, really, long PIPE command that assumes very short times - H it's likely to have a problem if you cross a day boundary since you justG can't squeeze that much into a PIPE before you hit the DCL buffer limit C and if-then-else-endif type flow controls are out of the question).   J Coming up with DCL that deals with time differences correctly in all casesF can be a bit tricky. You might be interested in the command proceedureG below to help with this. It should even function correctly for any time I difference expressable in valid VMS times, which means it is limited onlyNI by the range from the VMS base date to the last date and time expressableX+ within the 4 digit limit on the year field:e  A $ @tools:timediff "17-nov-1858 0:0:0.0" "31-dec-9999 23:59:59.99"M 2973483-23:59:59  B With this command proceedure, assuming it is in a location you canG access via the "tools" logical name, you can also do it with this shortD
 pipe command:e  ? $ pipe (starttime = f$time() ; dir ; @tools:timediff starttime)t  F which will report the time after the command (the "dir" in the middle,D in this case). You can, of course, do the same without the PIPE, butD then you get the time it takes you to type the commands in added in.  J Or, to get the results into a place where you can access them later, this:  & $ pipe (starttime = f$time() ; dir ; -1  @tools:timediff starttime f$time() totaltime ; - !  define/job totaltime &totaltime)n  G which puts the time data into a logical name, "totaltime" in this case,u in your job logical name table.n  I Due to the nature of this command proceedure, you can time even very longm duration things correctly.   --- Carl  H (Watch for bad line-breaks due to news transmission - every line in this, command proceedure should start with a "$".)   $! TimeDiff.comUK $! Calculate the amount of time between two date-time values in the typical - $! VMS text format (dd-mmm-yyyy hh:mm:ss.hh).U $!L $! V1.0 - Carl Perkins, March 2001; based on earlier stuff that had a bit ofK $!        error correction from Bob Kaplow (kaplow_r@eisner.decus.org.mars)eK $! V1.1 - Carl Perkins, June 2001; added error detection and correction forsF $!        the case where P1 and P2 are the names of symbols instead of) $!        raw text holding the date-time., $!M $! Subroutine MJD calculates the modified julian day (days since 17-Nov-1858,5> $! which is - not exactly coincidentally - the VMS base date). $MJD: Subroutine
 $ jddate = p1e* $ jdy = F$CVTime(jddate,"ABSOLUTE","YEAR")- $ jdm = F$CVTime(jddate,"COMPARISON","MONTH"):) $ jdd = F$CVTime(jddate,"ABSOLUTE","DAY")E $ jdy = jdy + 8000 $ If jdm .LT. 3  $ Then $   jdy = jdy-1G $   jdm = jdm+12 $ EndIFsO $ mjday == (jdy*365)+(jdy/4)-(jdy/100)+(jdy/400)-3600821+(jdm*153+3)/5-92+jdd-1y $ Exit' $ EndSubtoutine ! end of MJD subtoutinef $!!! $ If P1 .EQS. "" $ ThenF $   Write Sys$Output "Usage: @timediff start-time [end-time [symbol]]"J $   Write Sys$Output " - start-time is required, end-time defaults to now"O $   Write Sys$Output " - if symbol not specified, output is written to display"RE $   Write Sys$Output " - the times need to be text data, not symbols"  $   EXIT $ EndIf  $! $! Parse parameters  $! $ If P2 .EQS. """ $ Then !none given, default to now, $   now = F$CVTime("","ABSOLUTE","DATETIME") $ ElseF $! 1st, set up error trap for case when value passed to P2 is a symbol@ $   On Warning Then $ now = F$CVTime('P2',"ABSOLUTE","DATETIME") $   define/user sys$error nl:i $   define/user sys$output nl:+ $! now try and get the time specified in P2t1 $   now = F$CVTime("''P2'","ABSOLUTE","DATETIME")  $   deassign/user sys$errorg $   deassign/user sys$output $   Set NoOn $ EndIfg $ If P3 .EQS. ""/ $ Then !none given, default to Write Sys$Output ! $   do_thing = "Write Sys$Output"s $ Else: $   do_thing = F$Edit("''P3'","COLLAPSE,UNCOMMENT")+" == " $ EndIfiF $! 1st, set up error trap for case when value passed to P1 is a symbolC $ On Warning Then $ start_dt = F$CVTime('P1',"ABSOLUTE","DATETIME")n $ define/user sys$error nl:  $ define/user sys$output nl:+ $! now try and get the time specified in P1 4 $ start_dt = F$CVTime("''P1'","ABSOLUTE","DATETIME") $ deassign/user sys$errore $ deassign/user sys$output
 $ Set NoOn $! $! Do calculations $! $ Call MJD "''start_dt'" $ start_mjd = mjdaya $ Call MJD "''now'"o $ end_mjd = mjdayh $ If end_mjd .LT. start_mjd  $ Then !wrong orderNE $   Write Sys$Output "%TIMEDIFF-F-Oops, Start-time is after end-time"o $   Exit $ EndIf 3 $ start_time = F$CVTime(start_dt,"ABSOLUTE","TIME")t $ If end_mjd .EQS. start_mjd $ Then ! use shortcutl $   up_days = "0"-D $   time_diff = F$CVTIME("''now'-0-''start_time'","ABSOLUTE","TIME")# $ Else ! calculate the whole schmoo- $   days = end_mjd - start_mjd@ $   start_hour = F$Integer(F$CVTime(start_dt,"ABSOLUTE","HOUR"))9 $   end_hour = F$Integer(F$CVTime(now,"ABSOLUTE","HOUR")) ! $   hours = end_hour - start_hourRA $   start_min = F$Integer(F$CVTime(start_dt,"ABSOLUTE","MINUTE")) : $   end_min = F$Integer(F$CVTime(now,"ABSOLUTE","MINUTE"))! $   minutes = end_min - start_min*A $   start_sec = F$Integer(F$CVTime(start_dt,"ABSOLUTE","second")) : $   end_sec = F$Integer(F$CVTime(now,"ABSOLUTE","second"))! $   seconds = end_sec - start_secY $   If (seconds .lt. 0)  $   Then $     minutes = minutes - 1  $     seconds = seconds + 60	 $   EndIf  $   If (minutes .lt. 0)  $   Then $     hours = hours - 1/ $     minutes = minutes + 60	 $   EndIfV $   If (hours .lt. 0). $   Then $     days = days - 1  $     hours = hours + 24	 $   EndIf  $   If (days .LE. 9999)  $   ThenI $     time_diff = F$FAO("!4ZL-!2ZL:!2ZL:!2ZL",days,hours,minutes,seconds)  $   ElseH $     time_diff = F$FAO("!ZL-!2ZL:!2ZL:!2ZL",days,hours,minutes,seconds)	 $   EndIF  $ EndIF0 $ 'do_thing' time_diff $ Exit   ------------------------------  % Date: Sat, 02 Jun 2001 12:03:45 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>  Subject: Re: hszterm software ' Message-ID: <3B191C71.2EC35A6A@fsi.net>    Scott Vieth wrote: >  > No, that's not correct.  > O > There is a scripting tool for VMS that will let you talk directly to the HSGs + > without any Solaris or NT boxes involved.   H If you're talking about HSDSA-SCRIPT, I've already made entensive use ofG that. In one case, I even combined that with DFU to resolve the problem F of propagating backup dates onto disks where the mirror-sets are splitE at the HSx so BACKUPs can proceed in parallel with normal operations.   H Too bad HSDSA-SCRIPT (or similar) is not supported. Would solve a ton of	 problems.   H The question remains: how does one "talk to" HSG's from an OpenVMS batch2 job? Is the HSDSA-SCRIPT approach still effective?   --   David J. Dachtera  dba DJE Systems  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.>   ------------------------------    Date: 02 Jun 2001 18:54:30 +0800, From: Paul Repacholi <prep@prep.synonet.com>? Subject: Re: Size of VMS patch kits and new compression options - Message-ID: <87snhjup7d.fsf@prep.synonet.com>E  D Simon Clubley <simon_clubley@remove_me.excite.com-Earth.UFP> writes:  O > On Thu, 31 May 2001 15:06:01 -0400, in article <3B169619.1138CCC@oracle.com>,  > norm lastovica wrote:E  F > >there is no need to ship a zip/unzip tool.  there is self-etracting@ > >ZIP on VMS already that could easily replace the existing DCXE > >stuff.  In fact, the file types could even remain the same so that = > >there would be little "down-stream" impact to the existing  > >procedures.  = > >But, it would be cool for PCSI to be able to automatically(; > >produce a compressed kit source.  The technology used toE > >do so is unimportant.  : > I probably have not explained myself clearly enough. :-)  D > The reason that I suggested the self extraction option was becauseD > of strict security VMS sites. I have a problem believing that they> > would be happy to be given a .ZIP patch kit and then told to4 > download a public domain unzipper to unzip it. :-)  D Think about this. If you care about security, what would you prefer;  D 1) Get a standard utillity, audit it, and use that to decompress the kits.   B 2) Down load a file that *claims* to be a VMS supported format and execute it blind.   B The bigest plus to ZIP today, is that even the stupidest slugeware@ around has at least a small chance of knowing the .zip = binary!   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov     ------------------------------    Date: 02 Jun 2001 19:11:29 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: The future of VMS- Message-ID: <87ofs7uof2.fsf@prep.synonet.com>   ' Dan O'Reilly <dano@process.com> writes:   0 > At 10:29 AM 6/1/2001, Christopher Smith wrote:  6 > > > From: Christof Brass [mailto:brass@infopuls.com]  F > > > I would refrain from trying to support C/C++ as common language.> > > > Both languages lack the very basics from the point of SWA > > > engineering and therefore provide a worst case scenario for  > > > porting apps.   A > >It's interesting to note that I can't think of much commercial C > >software that's not written in C/C++ these days.  Perhaps rather E > >than porting a modern application, one should consider looking for D > >an older one with a solid foundation and doing a port/enhancement > >at the same time.  E > >It's unfortunate that web browsers are probably too new to do this D > >with.  A web browser in ADA would be interesting.  As a matter ofF > >preference, I don't like ADA too well, but it seems well supported,@ > >and is relatively solid.  Most of the problems I see with webA > >browsers are in memory allocation, I assume, from sloppy C. :)   1 > Caveat emptor: not trying to slam anybody here!   C > You know, it's interesting the way software engineering vis-a-vis A > languages has transmogrified over the years.  It used to be the E > responsibility of the engineer to write good code.  Now it seems to ? > be the responsibility of the language constructs to FORCE the B > engineer to write good code.  Hence, state- ments like languages= > lacking "the very basics from the point of SW engineering".7  @ > Maybe that's good for the kids just coming out of college, butD > (showing my age - I wrote my first BASIC program 27 years ago!) as; > for me, I mourn the passing of the "real art" of software  > engineering...  E C has a pile of really nasty traps, and has not bothered to learn the C lessions of experience. Ma Bell found out the hard way that in-band F signalling is a really bad idea, much to the joy of phone phreakers. CB has not yet learned that lession, and still clings to the 'inbuilt( magic' method for basic data structures.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.E@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov     ------------------------------   Date: 2 Jun 2001 01:13 CDT' From: carl@gerg.tamu.edu (Carl Perkins)  Subject: Re: University in USA, Message-ID: <2JUN200101130337@gerg.tamu.edu>  - fabio_compaq@ep-bc.petrobras.com.br writes...C$ }It is nothing regarding to OpenVMS. } 9 }I am searching the Yahoo but I dont remember the name of 6 }that Technology Insitute with unities spreaded in all }the USA }  }ITT?  IEE ? IET ? EET ? }  }FC   C There is a thing called the ITT Technical Institute. It has a bunchC3 of campuses (70 or so, I think) all over the place.R  D It isn't quite a univeristy in the usual sense (as used in the US) -G it is more comparable to a group of community colleges with a technical F focus, I'd say. They offer mostly associate degrees (which should be 2D years of study if you go year-round), but also some bachelors degreeA programs - one of them does evidently offer a masters degree in a0! single area (project management).    See www.itt-tech.edu.   D It is fairly well known (not surprising as they advertise nationallyC via television commercials, and probably in other ways) and, as far0D as I know, has a pretty good reputation - on the other hand, I don't( think I know anybody who has gone there.   --- Carl   ------------------------------  $ Date: Sat, 2 Jun 2001 20:13:11 +0400C From: "Ruslan R. Laishev" <to-junk--laishev@mail.dls.net---to-junk> 0 Subject: Wanted:H.323 protocol stack for OpenVMS> Message-ID: <%48S6.7284$Qd.184716@e420r-atl1.usenetserver.com>  
 Hello All!  K         I looking a H.323 protocols series implementaion under OpenVMS, I'd  like toe	 implement0% my own VoIP gatekeeper under OpenVMS.e  2         Any ponters, links is greatly appreciated.       -- Regards.6 Mobile:+7 (901) 9713222, AIM nickname:"VMS hardworker"> http://www.DLS.net  - Non-stop VMS-powered ISP in ChicagoLand!< http://www.RadiusVMS.com - RADIUS server for OpenVMS project   ------------------------------    Date: 02 Jun 2001 18:49:05 +0800, From: Paul Repacholi <prep@prep.synonet.com>2 Subject: Re: [OT] Current Microsoft v DOJ status ?- Message-ID: <87wv6vupge.fsf@prep.synonet.com>D  - Christopher Smith <csmith@amdocs.com> writes:I   > > From: Simon Clubleyi  C > > To move this back to VMS, my concern was that if Microsoft win, D > > then they would feel free to go all out into the high-end serverC > > area, regardless of the relative merits of the MS versus non-MSi > > operating systems.  C > A valid concern, and until I see microshaft dead, I won't believe-E > that it isn't going to happen.  Personal opinion, of course.  NevernF > underestimate the ruthlessness of microshaft or the stupidity of the > general populace.A  C > The question we should be asking here, though, is "what is Compaqn > going to do about it?"  F > > People here should also remember that people generally do not missF > > something that they have never experienced; in other words, if youD > > have never been exposed to something like VMS, then you will not4 > > miss it when you are given a Microsoft solution.  D > Not all people -- only most of them.  I know one person who had noD > idea about VMS, nor had she seen much other than microsoft garbageF > before I met her.  She still hated the microsoft "solution," and now8 > she has her own hobbyist VAX.  I plan to marry her. ;)  E > Mind you, you don't find many people like that.  I'm sure there areo1 > a few.  For the rest, though -- affordable VMS?r  A I have found that it is in fact NOT unusual. The VMS bit, not thei other bit ;)  E Show a group VMS, and about half will sit up and take notice. Half ofy. them will, if given a chance, follow up on it.  E Thee problem is, they seldom get that chance in a usefull way, and ifrC they do, then they are still wedded to others by apps they need, or  think they need.  B I know of near NO VMS in teaching, comp sci, or system programming# courses. I was there, but has gone.d   -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.I@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.H Spam-To: uce@ftc.gov,enforcement@sec.gov,sness@fcc.gov,hfurchtg@fcc.gov,#   mpowell@fcc.gov,gtristan@fcc.gov t   ------------------------------  % Date: Sat, 02 Jun 2001 12:25:18 -0500a1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e2 Subject: Re: [OT] Current Microsoft v DOJ status ?' Message-ID: <3B19217E.5B23F040@fsi.net>    JF Mezei wrote:o > [snip]I > Note that electric cars may be neat, but you still need to generate thed > electricity somewhere.  F One problem I've noticed is that when you say "electric car", the mindF of the listener/reader automatically equates "electric car" = "battery
 operated".  H There was an article in the local papers (Elgin (IL) Daily Courier News,G Chicago Sun Times) circa. 1983 or so documenting one inventor's effortsdB to provide for a self-contained generating system using a reactionB between Deutrium (common isotope of Hydrogen, extractible from seaH water) and Gallium (early transistors were based Germanium and Gallium).H Don't know whatever happened to it, but it seemed to hold great promise.H The stories stated that the inventor had a power plant + fork lift motor? installed in (what was then) a full-size car (Olds?) and he wasXE producing performance equivalent to a 490ci (7 cubic litres or so) V8-D from an ounce of each element for the equivalent of 100,000 miles of4 highway driving ("city" numbers were not mentioned).  C The closest we come to that today is Honda's hybrid (gas/electric).t  8 > Bicycles however are great for transportation and they > keep you in shape.  E Not much good for 40 mile commutes, or in rainy/snowy/icy weather ...nA sort of like public transit. In Chgo., as long as your commute istE between the suburbs and the City or between points on the rail lines, H public transit is a good option; however, this includes less than 15% ofB area commuters, according to Metra's numbers (Metra is the ChicagoC Metropolitan Commuter Railroad Corp.) which, according to figures ItD recall seeing, list their ridership at circa. 400,000 per day systemB wide. I've seen other statistics indicate the total number of areaA commuters as circa. 3.5 million, less than 30% of which (non-railnC commuters) travel to/from Chicago by way of the area express(?)wayse (parking lots, in rush hour).   B I seem to recall reading numbers showing that the average suburbanD commute (suburb to suburb) in this area is circa. 10 miles each way.  A I'm a pedaller from WAY back, but that's a stretch - even for me!    -- P David J. Dachtera  dba DJE Systemss http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/r  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: Sat, 02 Jun 2001 13:58:18 -0400u- From: JF Mezei <jfmezei.spamnot@videotron.ca>A2 Subject: Re: [OT] Current Microsoft v DOJ status ?, Message-ID: <3B19293A.CDB7FC99@videotron.ca>  E > > The question we should be asking here, though, is "what is CompaqG > > going to do about it?"  N Compaq was the only box maker to openly support Microsoft during the trial. SoR it seems fairly obvious to me that Compaq will side with Microsoft no matter what.  J It was silly for Compaq to side with Microsoft because they gained nothingK from it and would have been much beter off staying neutral silent. ConsidertJ that Compaq could have helped bring down Microsoft with all the anti-trustN stuff that MS forced on Digital (such as dropping email/messaging products andD adopting exchange in exchange for the right to sell MS consulting ).  J So I fully expect Compaq to remain a loyal Microsoft supporter, even if itL hurts Compaq's alpha sales, at least until Microsoft has declared bankrupcy.  M If Microsoft splits up in multiple companies, I fully expect Compaq to remainrJ loyal to those companies as if they were one unit. Lets not kid ourselves,A Bill Gates may split the companies up in such a way to please the T authoritioes, but those companies will remain one single logical entity in practice.   ------------------------------   End of INFO-VAX 2001.304 ************************