0 INFO-VAX	Sat, 01 Feb 2003	Volume 2003 : Issue 63      Contents:$ Alpha parallel port, LRDRIVER: Read?" Re: ALphaServer 2100A Disk Options( Re: Alphaserver 4100 and Powerstorm 4D202 ANN: unixODBC 2.2.4 ODBC client software available2 Re: Announcing the first OpenVMS Technical Journal Re: Batch job log spec Re: Batch job log spec Re: Batch job log spec Re: Batch job log spec Re: Batch job log spec Re: Batch job log spec= DECW$STARTAPPS.COM and OPA0: /NOBROADCAST with serial console - Re: DMA on IA-64, was: Re: EV7, ES47 question - Re: DMA on IA-64, was: Re: EV7, ES47 question 7 Re: Graphics support on VMS, was RE: EV7, ES47 question " Re: Information on VMS web servers= Re: Inspecting VMS SMTP email contents before it gets to user 1 Linux has just as many dangerous bugs as Windows! 5 Re: Linux has just as many dangerous bugs as Windows! 5 Re: Linux has just as many dangerous bugs as Windows!   Multi-host SCSI adapter question$ Re: Multi-host SCSI adapter question. Re: Network Time Protocol (NTP) for OpenVMS ??# Re: OpenRDA ODBC Driver for OpenVMS # Re: OpenRDA ODBC Driver for OpenVMS - Re: OpenVMS Boots on Itanium on Friday Jan 31 - Re: OpenVMS Boots on Itanium on Friday Jan 31 - RE: OpenVMS Boots on Itanium on Friday Jan 31 - Re: OpenVMS Boots on Itanium on Friday Jan 31 - Re: OpenVMS Boots on Itanium on Friday Jan 31 - Re: OpenVMS Boots on Itanium on Friday Jan 31 - Re: OpenVMS Boots on Itanium on Friday Jan 31  Oracle 9i on VMS use LMF? & Selling: New 9.1GB 10KRPM Disks USD109 Re: Submit at end of month?  Re: Submit at end of month?  Re: VMS source listings ?   F ----------------------------------------------------------------------  + Date: Fri, 31 Jan 2003 23:11:36 -0600 (CST)  From: sms@antinode.org- Subject: Alpha parallel port, LRDRIVER: Read? ) Message-ID: <03013123113608@antinode.org>   F    I finally got around to trying to push some arbitrary bytes out theC parallel port of my AlphaStation 200 4/233.  After I discovered the F value of "SET PRINTER /[NO]PASSALL", I can report success in twiddling eight LEDs using a DCL WRITE.   .    Initially, I was puzzled by this complaint:   ALP $ cop lra0: nla0: ( %COPY-E-READERR, error reading LRA0:[].;- -RMS-F-SYS, QIO system service request failed . -SYSTEM-F-ILLIOFUNC, illegal I/O function code1 %COPY-W-NOTCMPLT, LRA0:[].; not completely copied   E This seems to be consistent with the code in SYS$EXAMPLES:LRDRIVER.C, , which appears never to mention IO$_READ%BLK.  F    Is anyone out there willing to admit already having added some read@ functionality to this driver, or will I need to get educated and
 ambitious?  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode.org     Saint Paul  MN  55105-2547    ------------------------------  $ Date: Sat, 1 Feb 2003 16:30:29 +1100B From: "Antony Wardle" <antony.wardle@noooo_spammm_optusnet.com.au>+ Subject: Re: ALphaServer 2100A Disk Options < Message-ID: <3e3b5b7b$0$27993$afc38c87@news.optusnet.com.au>  # are you talking about the 9GB disks  that go in a BA shelf?   If so then yes, they should.   I have a 2100 with an 18GB SBB, , although I think it is the VA (narrow model)  ( If you have a free slot, just plug it in/ and type MC SYSMAN IO A and see see if it turns  up.      kiwi            5 "rob kas" <r0b@paychoice.nospam.com> wrote in message 4 news:gYgW9.1313$1n4.389367880@news.netcarrier.net... >     Hi > 0 > I'm trying to keep our last VMS machine alive.D > Does anyone know if the 9 Gig Disks will work in  AlphaServer 2100 InternalJ > RAID racks?   Failing that does anyone have a suggestion for adding Disk > Space to this old girl.  >  > . >                                       Thanks- >                                         Rob  >  >  >  >  >    ------------------------------    Date: 31 Jan 2003 16:49:48 -0800/ From: stuie_norris@yahoo.com.au (Stuart Norris) 1 Subject: Re: Alphaserver 4100 and Powerstorm 4D20 = Message-ID: <51262235.0301311649.13c78c80@posting.google.com>   M > Loaded RH 7.2  X wouldn't work until I loaded 4.2 from source and compiled. A > Heard 4.1 and up supported but once I got it working was happy.  >   D So you got the Powerstorm 4d20 to work with RH linux alpha.  Want toC post what you did so I can do the same.  I am sick of going back to , the gloria card to run linux on my PWS600au.   Stuart   ------------------------------    Date: 31 Jan 2003 15:39:19 -0800: From: craig.berry@SignalTreeSolutions.com (Craig A. Berry); Subject: ANN: unixODBC 2.2.4 ODBC client software available = Message-ID: <7f15589f.0301311539.32a3cfa1@posting.google.com>   E unixODBC is an open source collection of software supporting the Open 7 Database Connectivity standard.  Despite the name, it's A cross-platform, and the recent 2.2.4 release includes updated VMS ! support.  Build requirements are:   ( OpenVMS Alpha (tested with 7.2-1, 7.3-1) Compaq C 6.4 or later & gunzip and vmstar to unpack the source  + More information and kits are available at:    http://www.unixodbc.org/  F The PostgreSQL driver is currently the only one set up to build out ofA the box on VMS, but the driver manager is known to work fine with  other drivers as well.  D N.B.  Some warning-generating nits slipped into the code late in theB release cycle.  For now just locate CFLAGS in vmsbuild.com and add+ "/nowarn" to the list of compiler switches.    ------------------------------  % Date: Fri, 31 Jan 2003 15:31:01 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>; Subject: Re: Announcing the first OpenVMS Technical Journal / Message-ID: <3E3ACEEF.35E4D546@vl.videotron.ca>    Sue Skonetski wrote:5 > To view the OpenVMS Technical Journal please visit: 0 > http://www.openvms.compaq.com/openvms/journal/  D Glad to see you provided HTML versions that work without javascript.  
 Good work.   ------------------------------  % Date: Fri, 31 Jan 2003 13:53:39 -0500 % From: "John Vottero" <John@mvpsi.com>  Subject: Re: Batch job log spec / Message-ID: <v3lhhjn9cvhm4e@news.supernews.com>   7 "James Gessling" <jgessling@yahoo.com> wrote in message / news:b1edmc$126daj$1@ID-46415.news.dfncis.de... : > I want to know the file spec of my batch job's log file.1 > (so I can mail it to operations to be checked).  > & > I can see that f$getqui can do this: > = > x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")  > B > But I need to "establish context" for DISPLAY_JOB.  The examples@ > that "establish context" that I've found are all about looping/ > through a bunch of jobs, and I just want one.  > . > Can someone give me an example DCL,  Thanks, >   J Use DISPLAY_ENTRY instead of DISPLAY_JOB.  However, you won't get what you want.   I You can't get the actual log filespec from DCL and even if you could, you H can't e-mail the log file from the batch job because the file is in use.  J You could get kind of close by building the log specification from scratchJ and then copying that file to another file which you then mail.  Even thatJ will break if more than one instance of the job is running or if a logicalK name that's involved in the log specification has a process/job level value - that different than when the job was started.   H To really do this right, translate the value of SYS$OUTPUT,.  The secondI word of the result is the RMS IFI of the log file.  Set the FAB$M_PPF_IND 1 bit in this word and then pass it to sys$display.    ------------------------------    Date: 31 Jan 2003 13:04:41 -0600 From: briggs@encompasserve.org Subject: Re: Batch job log spec 3 Message-ID: <VXgvizKltEip@eisner.encompasserve.org>   W In article <v3lhhjn9cvhm4e@news.supernews.com>, "John Vottero" <John@mvpsi.com> writes: 9 > "James Gessling" <jgessling@yahoo.com> wrote in message 1 > news:b1edmc$126daj$1@ID-46415.news.dfncis.de... ; >> I want to know the file spec of my batch job's log file. 2 >> (so I can mail it to operations to be checked). >>' >> I can see that f$getqui can do this:  >>> >> x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB") >>C >> But I need to "establish context" for DISPLAY_JOB.  The examples A >> that "establish context" that I've found are all about looping 0 >> through a bunch of jobs, and I just want one. >>/ >> Can someone give me an example DCL,  Thanks,  >> > L > Use DISPLAY_ENTRY instead of DISPLAY_JOB.  However, you won't get what you > want.   B DISPLAY_JOB works fine.  I tried it before I posted and again justE now.  _In this case_, it appears to be synonymous with DISPLAY_ENTRY.   F But if you don't specify /LOG on the SUBMIT command, LOG_SPECIFICATIONC will be null.  In order to make much use of it, you need to default A in something like SYS$LOGIN:<jobname>.LOG;  And that still leaves C you with a problem with simultaneously running jobs (as you pointed  out).   A As you also suggested, a more fruitful approach may be to dig the 9 file name out from the SYS$OUTPUT process permanent file.   0 See code to do just that in my previous posting.   	John Briggs   ------------------------------   Date: 31 Jan 03 11:29:14 PST From: mckinneyj@cpva.saic.com  Subject: Re: Batch job log spec ( Message-ID: <Vgq$vnANllVu@cpva.saic.com>  5 In article <b1edmc$126daj$1@ID-46415.news.dfncis.de>, /  "James Gessling" <jgessling@yahoo.com> writes: : > I want to know the file spec of my batch job's log file.1 > (so I can mail it to operations to be checked).  > & > I can see that f$getqui can do this: > = > x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")  > B > But I need to "establish context" for DISPLAY_JOB.  The examples@ > that "establish context" that I've found are all about looping/ > through a bunch of jobs, and I just want one.  > . > Can someone give me an example DCL,  Thanks, >  > Jim  >   E Try explictily specifying a log file on the submit command line. When F you let the logfile spec default to jobname.LOG then the value of your x symbol is nul.   --   - Jim    ------------------------------   Date: 31 Jan 03 11:48:10 PST From: mckinneyj@cpva.saic.com  Subject: Re: Batch job log spec ( Message-ID: <oZCxnH1pAioO@cpva.saic.com>  3 In article <VXgvizKltEip@eisner.encompasserve.org>, !  briggs@encompasserve.org writes: Y > In article <v3lhhjn9cvhm4e@news.supernews.com>, "John Vottero" <John@mvpsi.com> writes: : >> "James Gessling" <jgessling@yahoo.com> wrote in message2 >> news:b1edmc$126daj$1@ID-46415.news.dfncis.de...< >>> I want to know the file spec of my batch job's log file.3 >>> (so I can mail it to operations to be checked).  >>> ( >>> I can see that f$getqui can do this: >>> ? >>> x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")  >>> D >>> But I need to "establish context" for DISPLAY_JOB.  The examplesB >>> that "establish context" that I've found are all about looping1 >>> through a bunch of jobs, and I just want one.  >>> 0 >>> Can someone give me an example DCL,  Thanks, >>>  >>  M >> Use DISPLAY_ENTRY instead of DISPLAY_JOB.  However, you won't get what you  >> want. > D > DISPLAY_JOB works fine.  I tried it before I posted and again justG > now.  _In this case_, it appears to be synonymous with DISPLAY_ENTRY.  > H > But if you don't specify /LOG on the SUBMIT command, LOG_SPECIFICATIONE > will be null.  In order to make much use of it, you need to default C > in something like SYS$LOGIN:<jobname>.LOG;  And that still leaves E > you with a problem with simultaneously running jobs (as you pointed  > out).  > C > As you also suggested, a more fruitful approach may be to dig the ; > file name out from the SYS$OUTPUT process permanent file.  > 2 > See code to do just that in my previous posting. >  > 	John Briggs  9 A simpler (DCL only) method might be to get the output of > SHOW DEVICE/FILES SYS$LOGIN and SEARCH the output for your own< PID and the string "jobname.LOG". You'd only want to do this9 after you'd used the F$GETQUI calls to determine that the - logfile wasn't specified on the command line.    --   - Jim    ------------------------------  % Date: Fri, 31 Jan 2003 14:42:07 -0800 , From: "James Gessling" <jgessling@yahoo.com> Subject: Re: Batch job log spec 5 Message-ID: <b1eu40$12jo9f$1@ID-46415.news.dfncis.de>   * <mckinneyj@cpva.saic.com> wrote in message" news:Vgq$vnANllVu@cpva.saic.com...7 > In article <b1edmc$126daj$1@ID-46415.news.dfncis.de>, 1 >  "James Gessling" <jgessling@yahoo.com> writes: < > > I want to know the file spec of my batch job's log file.3 > > (so I can mail it to operations to be checked).  > > ( > > I can see that f$getqui can do this: > > ? > > x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")  > > D > > But I need to "establish context" for DISPLAY_JOB.  The examplesB > > that "establish context" that I've found are all about looping1 > > through a bunch of jobs, and I just want one.  > > 0 > > Can someone give me an example DCL,  Thanks, > >  > > Jim  > >  > G > Try explictily specifying a log file on the submit command line. When H > you let the logfile spec default to jobname.LOG then the value of your > x symbol is nul. >  > -- > - Jim   - Thanks a bunch.  I find that this works fine:   9 f$getqui("DISPLAY_ENTRY","LOG_SPECIFICATION",,"THIS_JOB")   J but only (as you point out) if /log was specified on the submit.  That was my problem.   Regards,  (another) Jim    ------------------------------    Date: 31 Jan 2003 12:51:15 -0600 From: briggs@encompasserve.org Subject: Re: Batch job log spec 3 Message-ID: <KY18jZ1V4fjK@eisner.encompasserve.org>   d In article <b1edmc$126daj$1@ID-46415.news.dfncis.de>, "James Gessling" <jgessling@yahoo.com> writes:: > I want to know the file spec of my batch job's log file.1 > (so I can mail it to operations to be checked).  > & > I can see that f$getqui can do this: > = > x = f$getqui("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")  > B > But I need to "establish context" for DISPLAY_JOB.  The examples@ > that "establish context" that I've found are all about looping/ > through a bunch of jobs, and I just want one.  > . > Can someone give me an example DCL,  Thanks,  G The above DCL is correct.  But there is a catch.  The log file actually B used is formed by taking the log specification (possibly null) andC defaulting in the user's home directory, the job name (with special F characters eliminated if neccessary) and an extension of .LOG togetherC with file version 1 or 1 greater than the pre-existing file of that 
 name, if any.   C If you want the name of the log file of the currently running batch ? job, you may want to consider a different approach.  Figure out 1 what file name SYS$OUTPUT refers to and use that.   ? The following Macro code works on Alpha and VAX.  Most of it is B Jon Pinkley's work.  [And pretty spiffy work at that].  I couldn'tA find an online copy, but I did have one hanging around in my home  directory here on eisner.   > The opening commentary alone makes the following worth a read.   	John Briggs  @ ; PPF translate specified PPF logical name to file specification< ; This is based on code posted on comp.os.vms by John Briggs? ; on 19 Nov 1996, message-id <1996Nov19.110550@alpha.vitro.com> < ; Modified by Jon Pinkley to accept a logical name so we can3 ; get the actual file name of a file opened by DCL. : ; This also sets three local symbols, instead of only one. ; : ; First delete local symbols PHY_FILE_NAME, ORG_FILE_NAME,: ; and FID_FILE_NAME.   These will be recreated when we can ; successfully determine them. ;  ; PHY_FILE_NAME 9 ;   This is the unconcealed name of the file at the time  5 ;   it was opened.  If it has been renamed, this will  ;   not be correct.  ; $ ;   PHY_FILE_NAME is set as follows:: ;   If it's a PPF, then do a $DISPLAY with nop=<noconceal>' ;     and save the resulting file name. 9 ;     If it is a record oriented device, (you can't trust 8 ;     fab$l_dev for this, you must ask $getdvi), instead5 ;     of using the rsa returned by $display, use the   ;     nam$t_dvi value.3 ;     (this is the name it had when it was opened.) 5 ;     if the device is a terminal, then save only the 6 ;     device name.  Set FILE_NAME to the saved string.; ;   If it's not a PPF, exit with warning status CLI$_UNDFIL 2 ;   This is after all, meant to be used with PPF's ;  ; ORG_FILE_NAME 7 ;   This is the concealed name of the file at the time  5 ;   it was opened.  If it has been renamed, this will  ;   not be correct.  ; $ ;   ORG_FILE_NAME is set as follows:% ;   If it's a record oriented device  $ ;     set ORG_FILE_NAME to nam$l_dev ;   otherwise 0 ;     do another $DISPLAY, this time displaying ! ;     the concealed name, and set / ;     ORG_FILE_NAME to the concealed file name.  ; " ; FID_FILE_NAME is set as follows: ;   If nam$l_fid is non zero? ;     determine the current file name by using lib$fid_to_name. < ;     Set FID_FILE_NAME to this value.  Note that this file C ;     name will be correct if the file was renamed using the RENAME 9 ;     command (but not necessarily if the FID is entered   ;     multiple times). ;   ; Usage: $ ppf :== $some_dir:ppf ;        $ ppf [logical_name]  ; ? ;        if no logical is specified, then sys$output is assumed 1 ;        i.e. the following three are equivalent:  ;        $ ppf sys$output  ;        $ ppf@ ;        $ run some_dir:ppf ! foreign command not necessary here ; > ;        The reason the this is the default is that it is very? ;        useful to allow a batch process to determine the exact . ;        filename and version of its log file. ; > ;        PPF can also be used to determine the version of file) ;        opened by DCL.  Example follows: , ;        $ open/read foo sys$login:login.com ;        $ ppf foo( ;        $ show symbol/local *_file_name@ ;          FID_FILE_NAME = "DISK$USER1:[USERS.JON]LOGIN.COM;181": ;          ORG_FILE_NAME = "ROOT$USERS:[JON]LOGIN.COM;181"A ;          PHY_FILE_NAME = "$4$DKA200:[USERS.][JON]LOGIN.COM;181"  ;        $ close/nolog foo ; 3 ;  example where file gets renamed while it is open  ; " ;        $ open/write foo test.dat ;        $ ppf foo# ;        $ sho sym /loc *_file_name > ;          FID_FILE_NAME = "DISK$JSCRATCH:[JON.PPF]TEST.DAT;1"> ;          ORG_FILE_NAME = "DISK$JSCRATCH:[JON.PPF]TEST.DAT;1": ;          PHY_FILE_NAME = "$4$DKC204:[JON.PPF]TEST.DAT;1"& ;        $ ren test.dat; jons.data;100 ;        $ ppf foo# ;        $ sho sym /loc *_file_name A ;          FID_FILE_NAME = "DISK$JSCRATCH:[JON.PPF]JONS.DATA;100" > ;          ORG_FILE_NAME = "DISK$JSCRATCH:[JON.PPF]TEST.DAT;1": ;          PHY_FILE_NAME = "$4$DKC204:[JON.PPF]TEST.DAT;1" ;        $ close/nolog foo           .psect  data,quad,noexe          $LNMDEF          $FABDEF          $NAMDEF          $DEVDEF          $DVIDEF          $CLIMSGDEF  9         .macro  errchk, ?skip           ; check for error >         blbs    r0, skip                ; on success skip this?         pushl   r0                      ; push offending status =         calls   #1, g^lib$stop          ; and kill this thing < skip:   .endm   errchk                  ; and that's errchk!   fab:    $FAB    nam=nam  nam:    $NAM    rsa=buffer,-!                 rss=buffer_size,-                  nop=<noconceal>   	 itemlist:          .word   buffer_size          .word   lnm$_string          .address        buffer&         .address        file_name_desc         .long   0            .align quad  buffer: .blkb   255  buffer_size=.-buffer         .align quad  buffer1:        .blkb   255  buffer1_size=.-buffer1         .align quad  buffer2:        .blkb   16 buffer2_size=.-buffer2         .align quad  recdev: .blkl   1  dvirec: .long   DVI$_REC return_length:         .blkw   1    sysout: .ascid  /SYS$OUTPUT/ tabnam: .ascid  /LNM$FILE_DEV/N phynam: .ascid  /PHY_FILE_NAME/         ; name file was originally opened withF orgnam: .ascid  /ORG_FILE_NAME/         ; same as file_name, concealedL fidnam: .ascid  /FID_FILE_NAME/         ; name determined by lib$fid_to_name: input:  .long   lnm$c_namlength         ; make a descr for9         .address 2$                     ; lib$get_foreign ; 2$:     .blkb   lnm$c_namlength         ; the buffer itself    file_name_desc:          .blkw   1          .word   0          .address buffer    fid_name_desc:         .blkw   1          .word   0          .address buffer1   dvi_name_desc:         .blkw   1          .word   0          .address buffer2           .psect  code,exe         .entry  MAIN,^m<> &         ; Get logical file name of PPFO         pushal  input                   ; set the length to the length returned 2         pushl   #0                      ; nopromptC         pushal  input                   ; write the rec'd data here 7         calls   #3, g^lib$get_foreign   ; get a command 9         errchk                          ; check for error   E         cmpw    input, #0               ; no input logical specified?          bneq    5$@         movc3   sysout,@sysout+4,@input+4 ; input = "SYS$OUTPUT"         movw  5$: @         ; Delete the symbols we are going to set (ignore errors)9         pushaq  fidnam                  ; "FID_FILE_NAME" &         calls   #1,g^lib$delete_symbol9         pushaq  orgnam                  ; "ORG_FILE_NAME" &         calls   #1,g^lib$delete_symbol9         pushaq  phynam                  ; "PHY_FILE_NAME" &         calls   #1,g^lib$delete_symbol  :         ; Translate specified logical name in LNM$FILE_DEV         pushal  itemlist         pushl   #0         pushaq  input          pushaq  tabnam         pushl   #0         calls   #5,g^sys$trnlnm          blbs    r0,10$5         brw     99$                     ; error? bail   #         ; Is it a PPF logical name? 6 10$:    cmpw    buffer,#^X001b          ; Escape, null         beql    11$ >         brw     101$                    ; it's not a PPF, quit 11$:+         ; Use $DISPLAY to get PPF file name &         movw    buffer+2,fab+fab$w_ifi,         bisw2   #fab$m_ppf_ind,fab+fab$w_ifiG         $display        fab=fab         ; first with non-concealed name 9         errchk                          ; check for error   9         ; Determine if device is a record oriented device M         ; Note that network devices like node"user pass"::sys$login:login.com G         ; will have nam$t_dvi set to a null string.  In this case, just E         ; treat it like a non-record oriented device.  We will handle ,         ; the lack of a FID at a later time.  :         ; copy the nam$t_dvi name into the dvi_name string  +         movzbw  nam+nam$t_dvi,dvi_name_desc          bneq    12$ F         brw     20$                     ; must be a decnet device name 12$:>         movc3   dvi_name_desc,nam+nam$t_dvi+1,@dvi_name_desc+4  L         pushal  recdev                  ; boolean for record oriented device5         pushaq  dvi_name_desc           ; device name ?         pushl   #0                      ; channel not specified E         pushal  dvirec                  ; address containing DVI$_REC          calls   #4,g^lib$getdvi          errchk  C         tstl    recdev                  ; if record oriented device A         beql    20$                     ; then skip the following   ?         ; here we have a record oriented device.  Directory and 6         ; file names really don't make a lot of sense.,         ; set PHY_FILE_NAME to nam$t_dvi and(         ;     ORG_FILE_NAME to nam$l_dev'         ; leave FID_FILE_NAME undefined            pushaq  dvi_name_desc          pushaq  phynam#         calls   #2,g^lib$set_symbol          errchk  ;         ; copy the nam$l_dev name into the file_name string ,         movzbw  nam+nam$b_dev,file_name_desc?         movc3   file_name_desc,@nam+nam$l_dev,@file_name_desc+4            pushaq  file_name_desc         pushaq  orgnam#         calls   #2,g^lib$set_symbol          errchk           brw     99$   0         ; Stuff file name length into descriptor, 20$:    movzbw  nam+nam$b_rsl,file_name_desc  7         ; The file name is all set up in file_name_desc 6         ; Stuff it into the DCL symbol 'PHY_FILE_NAME' 30$:    pushaq  file_name_desc         pushaq  phynam#         calls   #2,g^lib$set_symbol          errchk  5         ; Use $DISPLAY to get PPF file name concealed 1         bicb2   #<nam$m_noconceal>, nam+nam$b_nop          $display        fab=fab          blbs    r0,40$;         ret                             ; If it fails, exit   0         ; Stuff file name length into descriptor, 40$:    movzbw  nam+nam$b_rsl,file_name_desc  7         ; The file name is all set up in file_name_desc 6         ; Stuff it into the DCL symbol 'ORG_FILE_NAME'         pushaq  file_name_desc         pushaq  orgnam#         calls   #2,g^lib$set_symbol          errchk  9         ; Now grab the FID from the NAM block and convert 6         ; it to a filename using LIB$FID_TO_NAME, then6         ; stuff it into the DCL symbol 'FID_FILE_NAME'  8         ; we're going to use buffer1, set the length in '         ; the descriptor to buffer_size F         movab   buffer1,fid_name_desc+4         ; make sure we have it,         movzbw  #buffer1_size, fid_name_desc6         ; we are going to reuse the descriptor for the"         ; nam$t_dvi counted string-         movzbw  nam+nam$t_dvi, file_name_desc B         beql    99$                             ; no FID, bail out1         movab   nam+nam$t_dvi+1, file_name_desc+4            pushaw  return_length          pushaq  fid_name_desc          pushaw  nam+nam$w_fid          pushaq  file_name_desc$         calls   #4,g^lib$fid_to_name         errchk  0         ; Stuff file name length into descriptor+ 60$:    movzbw  return_length,fid_name_desc   7         ; The file name is all set up in file_name_desc 6         ; Stuff it into the DCL symbol 'FID_FILE_NAME' 70$:    pushaq  fid_name_desc          pushaq  fidnam#         calls   #2,g^lib$set_symbol  99$:    ret  101$:   movl    #CLI$_UNDFIL,r0          brb     99$            .end    main   ------------------------------    Date: 31 Jan 2003 14:08:21 -0800* From: ken.randell@fortel.com (Ken Randell)F Subject: DECW$STARTAPPS.COM and OPA0: /NOBROADCAST with serial console= Message-ID: <8debc3ff.0301311408.779f4af7@posting.google.com>   D VMS 7.3-1, Decwindows 1.2-6 on a DS10, Oxygen card (if that matters)  D I have a DS10 set up with the console on the serial line via the SRMD environment variable.  The console (OPA0:) in this case is being setF /NOBROADCAST by the SYS$MANAGER:DECW$STARTAPPS.COM.  I'm puzzled as to2 why this is occurring (or rather, needs to occur).  " The DCL in question is as follows:   $ GOSUB get_ws_flags2 $ if .not. ws_present then goto skip_console_checkF $ IF ws_alt_console .and. decw$console_selection .eqs. "WINDOW" THEN -2                 decw$console_selection == "ENABLE"* $ if decw$console_selection .eqs. "ENABLE" $   then. $       set terminal opa0:/permanent/broadcast $   else0 $       set terminal opa0:/permanent/nobroadcast $ endif   E The get_ws_flags routine is finding the flags as appropriate for INA0 9 DEVDEPEND2 (BEEF0005) and ws_alt_console is set to true.  D DECW$CONSOLE_SELECTION is initialized to DISABLE at the beginning ofE the procedure.  I have failed to see how/where decw$console_selection C is set to WINDOW anywhere in any of the DECW* procedures, so the if E statement always takes the 'else' path.  After the system has booted, ? the DECW$CONSOLE_SELECTION logical name has a value of DISABLE.   > This 'code' does not appear to have changed since at least VMS 6.2/Decwindows 1.2-4.   F If I boot a minimal system, then OPA0: is set to /BROADCAST as I wouldB expect, so I'm fairly certain the above 'code' is what is changing this.    Ken Randell    ------------------------------  % Date: Fri, 31 Jan 2003 15:45:20 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>6 Subject: Re: DMA on IA-64, was: Re: EV7, ES47 question/ Message-ID: <3E3AD24A.881DA3B9@vl.videotron.ca>    Fred Kleinsorge wrote:N > Itanium2 systems are all "legacy free"... which means no ISA bridge (no junk7 > IO, no PS2 KB/Mouse, no square wave generator, etc).    + Does Legacy-free also mean no serial port ?    ------------------------------  % Date: Fri, 31 Jan 2003 15:58:20 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>6 Subject: Re: DMA on IA-64, was: Re: EV7, ES47 question/ Message-ID: <3E3AD555.8775D63E@vl.videotron.ca>    Fred Kleinsorge wrote:N > On some *future* Itanium2 box (perhaps a generic Intel box) there may not beK > map registers, and any VMS driver written to "assume" the availability of  > map registers - will fail.  + This is meant as a question, not a comment:   M Is it therefore official that until further notice, VMS will only run on IA64 F systems built by HP due to its use of HP proprietary add-ons of IA64 ?    N (Now, the comments: it makes no difference as far as I am concerned, and it isJ no surprise, and in a way, if you want a robust system, you prefer one for- which VMS was built, not some random config.)    ------------------------------  % Date: Fri, 31 Jan 2003 14:14:04 -0500 A From: "Fred Kleinsorge" <kleinsorge@star-dot-zko-dot-dec-dot-com> @ Subject: Re: Graphics support on VMS, was RE: EV7, ES47 question. Message-ID: <3e3acafd$1_3@hpb10302.boi.hp.com>  F Cool.  I'm sure someone will buy one and try it once we relase the SW.J AFAIK, we haven't even gotten production cards yet, since the initial ones& had a problem with hot-swap PCI slots.    4 "Carl Perkins" <carl@gerg.tamu.edu> wrote in message' news:31JAN200311590098@gerg.tamu.edu... @ > In article <3e3ab042_3@hpb10302.boi.hp.com>, "Fred Kleinsorge"3 <kleinsorge@star-dot-zko-dot-dec-dot-com> writes...  > } ; > }"Sean O'Banion" <seanobanion@attbi.com> wrote in message : > }news:f883d5a4.0301310831.1df1133b@posting.google.com...J > }> > Yes.  ATI is more-or-less making a PCI version of the 7500 just for usK > }> > (I think because we're the only ones who asked).  The plan is for it  toK > }> > be supported anywhere a VX1 can be plugged in - which is pretty much J > }> > all the EV6 platforms.  We are using the PCI version for debug, and are B > }> > using XP1000's, DS10's, DS20's, ES45's, and Marvel systems. > }> >F > }> > Note:  We may or may not "support" the XP1000 - or at least notH > }> > support multi-head on it - it needs new firmware that hasn't been done.  > }>J > }> Does this mean that there is a "special" version of the 7500 for VMS?. > }> Or can I use the $76 one that Amazon has? > }> > } J > }As far as I know, the 7500 is only available in an AGP version.  I have to > F > If you go to the ATI web site (www.atitech.ca) you'll find that theyG > have a PCI version (you can even buy one from their online store - at G > least, I assume you can: I couldn't get to their online store page as F > it didn't like Netscape 303's SSL options due to insufficient bits). > L > See, for example, the second line in the system specifications section of: > 9 > http://mirror.ati.com/products/pc/radeon7500/specs.html  > G > (which doesn't mention the Itanium, BTW). It is also mentioned in the ' > monitor support section on that page.  > 
 > --- Carl   ------------------------------  % Date: Sat, 01 Feb 2003 08:30:35 +0200 * From: Mike Rechtman <rechtman@tzora.co.il>+ Subject: Re: Information on VMS web servers ( Message-ID: <3E3B698B.30407@tzora.co.il>   Arindam wrote: > Hi !N > I am new to this group and would like to say Hi! to all you floks out there.J > Here in my organisation we are having VAX 3400 and 3800 systems running  > on VMS 5.5-2. J > I would like to know if there is any internet browsers available on VMS J > for our platform. Is it also possible to have ASP like programs running K > on such browsers if there are any. Also where can I get the software for   > this.  >    > Bye  >  >    >  > Arindam Paul > J Manager 0 > Computer And Information Technology Department > Durgapur Steel Plant$ >   Steel Authority Of India Limited2 > There's a little bit of SAIL in everybody's life > www.sail.co.in >   ! 1. Please *D*O* *N*O*T* post mime  2. Try  J http://www.openvms.compaq.com/openvms/products/ips/register_nav3j_vax.htmlH (Unfortunately I do not recall whether this will run on V5.5-2, it does ' run on VAX V6.2.) In any case - no asp.    Mike   --    & New to c.o.vms? allow me to recommend:6 http://eisner.encompasserve.org/~rechtman/post_hlp.htm@ Other useful links at http://eisner.encompasserve.org/~rechtman/E --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that. ? Mike Rechtman                            *rechtman@tzora.co.il* E Kibbutz Tzor'a.                          Voice (home):(972)-2-9908337sC    "20% of a job takes 80% of the time, the rest takes another 80%"cE ---------------------------------------------------------------------u   ------------------------------  % Date: Fri, 31 Jan 2003 15:39:02 -0400c0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>F Subject: Re: Inspecting VMS SMTP email contents before it gets to user/ Message-ID: <3E3AD0D0.70B60AE1@vl.videotron.ca>S   Sol Gongola wrote: > < > I need to programmatically intercept email received by VMS> > and inspect it before it gets POPped to its final recipient.  . > Current platform is VMS 7.2-1 with TCPIP 5.1  , No documented features allow you do do this.  K However, one way of doing this would be to use the DELIVER foreign protocoleL which allows you to process incoming messages. You'd have to set forward allM mailboxes to redrect incoming mail to deliver (which would process individual 5 messages and then deliver it to the mailbox per say).e  L PMDF is far more flexible in how you handle messages between the outside and the VMS mailbox.   ------------------------------    Date: 31 Jan 2003 11:01:48 -0800( From: bob@instantwhip.com (Bob Ceculski): Subject: Linux has just as many dangerous bugs as Windows!= Message-ID: <d7791aa1.0301311101.7a6475c4@posting.google.com>M  1 not my opinion but a leading security experts ...S( OpenVMS is your only "secure" option ... if you can read click here ...  5 http://www.informationweek.com/story/IWK20030124S0013i   ------------------------------  % Date: Fri, 31 Jan 2003 12:59:00 -0700-+ From: "Barry Treahy, Jr." <Treahy@MMaz.com> > Subject: Re: Linux has just as many dangerous bugs as Windows!' Message-ID: <3E3AD584.2010105@MMaz.com>0   Bob Ceculski wrote:I  2 >not my opinion but a leading security experts ...) >OpenVMS is your only "secure" option ...i >if you can read click here ...  > 6 >http://www.informationweek.com/story/IWK20030124S0013 >  n >iK No question, VMS is the way to go but his article doesn't even mention VMS!   I These type of 'Anti-Linux/Pro-MS' articles have been appearing in all of ;H the rags since last fall and what they fail to address is the number of 7 systems compromised based on these 'CERT' advisories!  o  I When compared to the ongoing exploits that plague the Microcrap suite of :I products, any other operating system is a saint!  Also, considering that oG it isn't the Linux kernel that is being exploited but the libraries or oI applications, many of which have been used on VMS or in VMS apps as well -B as many other OS's, the real question is how well does a properly F administered system with a quality kernel hold up?  You have to admit C that a flawed application installed on VMS that requires privs can -L create just as large of a whole as a BIND flaw that allows the Lion exploit!  H He also spends a lot of time on the speed of the fix but how many sites H will not use XP or W2K SP3 because Microcrap linked the bug fixes to an  unacceptable EULA and malware?  G On a tit-for-tat, sure the open-source components that make up a Linux lF distribution may have just as many if not more 'bugs' as Windoze, but I does that make it less secure?  Did anyone care to 'count' the number of NC VMS patches posted year?  I justed checked my e-mail folder of the  I notifications and since June, I count over 120!  Does that mean that VMS @. is 'less' secure than Windows?  I think not!    I So why does the press continue to paint Linux in a bad light and Windoze  F as a innocently accused and abused contributor to society unless they I are Microcrap shills?  Linux, Un*x, BSD, Mac OS X, OS/2, these ain't the  G enemy folks, the lack of common sense and the inability to deduce fact   from fiction is!   Regards,   Barry      --    @ Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028e   ------------------------------  % Date: Fri, 31 Jan 2003 20:21:05 +0000oE From: Jamie Stallwood <this.no.work.try.something.else@project76.net>.> Subject: Re: Linux has just as many dangerous bugs as Windows!8 Message-ID: <rjml3vg6l8evnb1f25j5m84v6milr7tohv@4ax.com>  A On 31 Jan 2003 11:03:52 -0800, bob@instantwhip.com (Bob Ceculski)  wrote:  # >says a leading security expert ...t) >OpenVMS is your only "secure" option ...0' >if you can read click here to read his- >reasoning ... >J6 >http://www.informationweek.com/story/IWK20030124S0013   That's Great Bob  8 Now sod off back to cov and stop bothering linux people.   ------------------------------  # Date: Fri, 31 Jan 2003 18:42:49 GMT " From: Alfred Falk <falk@arc.ab.ca>) Subject: Multi-host SCSI adapter questiona9 Message-ID: <Xns931477288F10Dfalkarcabca@205.233.108.180>l  E I want to configure a VMScluster with some disks connected do a dual-l hosted SCSI bus.   Here's what I have:s4    DS20 with KZPCM (Dual SCSI with Ethernet) adapter=       channel A of KZPCM is connected to BA364 4-bay SW shelfr#    AS800 with built-in adapter onlyb  I I would like to connect the AS800 to the BA364.  What model SCSI adapter  G to I need to buy for the AS800?  Will the KZPCM work this way, or do I t' need another adapter for the DS20 also?g  B (Performance is not crucial.  I would assume that this will be an G improvement on the current configuration involving DSSI/HSD05/RZ-28's.)f   -- e@ ----------------------------------------------------------------A   A L B E R T A         Alfred Falk               falk@arc.ab.ca n@ R E S E A R C H         Information Systems Dept   (780)450-5185+   C O U N C I L         250 Karl Clark Road.1                         Edmonton, Alberta, Canada  http://www.arc.ab.ca/   T6N 1E4   http://www.arc.ab.ca/staff/falk/   ------------------------------  % Date: Fri, 31 Jan 2003 22:13:21 -0500j2 From: rdeininger@mindspring.com (Robert Deininger)- Subject: Re: Multi-host SCSI adapter question L Message-ID: <rdeininger-3101032213210001@user-2ive3j5.dialup.mindspring.com>  E In article <Xns931477288F10Dfalkarcabca@205.233.108.180>, Alfred Falkl <falk@arc.ab.ca> wrote:e  F >I want to configure a VMScluster with some disks connected do a dual- >hosted SCSI bus.y >t >Here's what I have:5 >   DS20 with KZPCM (Dual SCSI with Ethernet) adapter > >      channel A of KZPCM is connected to BA364 4-bay SW shelf$ >   AS800 with built-in adapter only > J >I would like to connect the AS800 to the BA364.  What model SCSI adapter H >to I need to buy for the AS800?  Will the KZPCM work this way, or do I ( >need another adapter for the DS20 also? >aC >(Performance is not crucial.  I would assume that this will be an nH >improvement on the current configuration involving DSSI/HSD05/RZ-28's.)  ; I don't know which adapter you need off the top of my head.o  F The Guidelines for Cluster Configuration manual lists all the adaptersJ that support multi-host SCSI in VMS.  From that list, pick an adapter thatJ is listed (in the QuickSpecs, SOC, etc) as supported for your system type.  B Then add the appropriate cables, terminators, bus converters, etc.   ------------------------------    Date: 31 Jan 2003 15:49:16 -0600+ From: young_r@encompasserve.org (Rob Young)t7 Subject: Re: Network Time Protocol (NTP) for OpenVMS ??e3 Message-ID: <Bd0A3gCTtMcL@eisner.encompasserve.org>e  p In article <h0C_9.236027$pDv.121438@news04.bloor.is.net.cable.rogers.com>, "John Smith" <a@nonymous.com> writes: > : > "Rob Young" <young_r@encompasserve.org> wrote in message   	[snip a bunch]c  : >> A number of good GPS links hanging off that, including: >> >> http://www.gpsy.com/gpsinfo/g >> >> From there: >>. >> http://www.edu-observatory.org/gps/gps.html >># >> How accurate are the GPS clocks?" >>F >> http://www.globalsecurity.org/space/library/news/1997/970505-2f.htm >>F >> "The GPS IIF spacecraft will have four frequency standards composed	 > of bothIA >> cesium and rubidium technologies. These extremely accurate GPS$ > atomic clockss0 >> can keep time to within 8 nanoseconds a day." >>A >> Bottom Line:  The days of a "time server" (national, military)L: >> are past/unnecessary.  Nameless, faceless, GPS is best. >> > H > Sorry for jumping in late ...aren't the GPS-based clock susceptible toH > larger 'deviation' if the military decides to kick things back the wayH > things were before Clinton decided it was allow the signals to be usedD > to fix position to approx 2m accuracy? I'm thinking about the IraqF > situation in the next couple of months, or anytime in the future the, > GPS signals are tinkered with in this way. >   > 	Any -good- conspiracy has "some" supporting evidence.  If you: 	are going to kick-start a good-ol' c.o.v. conspiracy, how/ 	about some twisted references to get us going?p   				Rob    ------------------------------    Date: 31 Jan 2003 12:05:56 -0800: From: craig.berry@SignalTreeSolutions.com (Craig A. Berry), Subject: Re: OpenRDA ODBC Driver for OpenVMS= Message-ID: <7f15589f.0301311205.5c5fda39@posting.google.com>J  i Earl Lakia <Lakia_n_o__s_p_a_m_@ipact.com> wrote in message news:<Z5ydnfx6WZAnCaSjXTWcqw@netnitco.net>... @ > I was looking a product to allow me to connect my OpenVMS hostB > to a Microsoft SQL Server database.  Anyway, found the following6 > product and wondering if anyone has tried it before.  E If it's the one I'm thinking of I did try it once and wasn't terribly F impressed.  The user guide showed a weak understanding of what logical@ names are.  Linking a test program showed that the code in theirB libraries had compiled with warnings (though the user guide said I? could ignore them).  That was a couple years ago, so you shouldtF definitely get a trial version and see how well it works for you.  You? should also do the same with EasySoft, Attunity, and CONNX, andl6 compare prices, features, and tech support.  My $0.02.   ------------------------------  % Date: Fri, 31 Jan 2003 23:30:31 +0300o2 From: "Ruslan R. Laishev" <Laishev@StarLet.SPB.RU>, Subject: Re: OpenRDA ODBC Driver for OpenVMS- Message-ID: <3E3ADCE7.4040500@StarLet.SPB.RU>R   Take a look to :4 http://starlet.deltatel.ru/~laishev/work/freetds/*.*     Craig A. Berry wrote:nk > Earl Lakia <Lakia_n_o__s_p_a_m_@ipact.com> wrote in message news:<Z5ydnfx6WZAnCaSjXTWcqw@netnitco.net>...h > @ >>I was looking a product to allow me to connect my OpenVMS hostB >>to a Microsoft SQL Server database.  Anyway, found the following6 >>product and wondering if anyone has tried it before. >  > G > If it's the one I'm thinking of I did try it once and wasn't terribly H > impressed.  The user guide showed a weak understanding of what logicalB > names are.  Linking a test program showed that the code in theirD > libraries had compiled with warnings (though the user guide said IA > could ignore them).  That was a couple years ago, so you shouldbH > definitely get a trial version and see how well it works for you.  YouA > should also do the same with EasySoft, Attunity, and CONNX, ando8 > compare prices, features, and tech support.  My $0.02. >      --   Cheers, Ruslan.eD +---------------------pure personal opinion------------------------+2               Mobile: +7 (812) 116-3222/NMT/IMT-MCB     TKD (WTF) in Russia, St.-Petersburg - www.TaeKwonDo-WTF.SPb.RU0                  http://starlet.spb.ru/~laishev/   ------------------------------  # Date: Fri, 31 Jan 2003 22:58:36 GMTaL From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 316 Message-ID: <00A1ACC1.B219A284@SSRL.SLAC.STANFORD.EDU>  b In article <b1et1g$1nc$1@web1.cup.hp.com>, "Sue Skonetski" <susan.skonetski@hp.nospam.com> writes: >-----Original Message-----) >t >From: Grant, Clairh >u' >Sent: Friday, January 31, 2003 3:40 PM  >R# >To: OpenVMS Systems Software Grouph >t >Subject: VMS boots on Itanium > I >We are please to announce that OpenVMS has booted on an HP i2000 ItaniumfL >system. By successfully executing a DIRECTORY command the official date and; >time for the Boot Contest is January 31, 2003 3:31 PM EST.m >JG >Many, many people have contributed to this effort, including managers,eM >supervisors, project leaders, consultants, development infrastructure group,mJ >calling standard committee, engineers working on post-boot projects, etc.L >All will receive their well-deserved credit as we proceed. The following is; >a very specific set of people; these are the engineers whosF >designed/wrote/debugged the code that comprises the running operating >system. > 5 >list of wonderful engineers removed by Sue SkonetskiP     Many congratulations!"  C Whatever anybody thinks about the Itanium strategy, this is a major_- accomplishment and an impressive achievement."   -- Alanf    O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056cM  Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA   94025vO ===============================================================================h   ------------------------------  % Date: Fri, 31 Jan 2003 20:00:07 -0400_0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 31/ Message-ID: <3E3B0E00.7744A20C@vl.videotron.ca>-   Sue Skonetski wrote:H > Many, many people have contributed to this effort, including managers,  6 > list of wonderful engineers removed by Sue Skonetski    K Seems to me that the engineers and their caretaker (Sue)  would be far moreg; important and should have been listed well before managers.   L Now that they have completed the port, can they can back to improving VMS on VAX ????? ;-) :-) :-)t   ------------------------------  % Date: Fri, 31 Jan 2003 17:17:09 -0800I$ From: Shane Smith <ssmith@icius.com>6 Subject: RE: OpenVMS Boots on Itanium on Friday Jan 310 Message-ID: <01C2C94C.AD4198D0@sulfer.icius.com>  H IMHO the fact that managers in OpenVMS engineering contribute to gettingD the job done is unique and impressive. Most management types seem to have the opposite effect...a  . (Damn, I wish a smiley were appropriate here.)   Shaneb   -----Original Message-----7 From: JF Mezei [mailto:jfmezei.spamnot@vl.videotron.ca]r& Sent: Friday, January 31, 2003 4:00 PM To: Info-VAX@Mvb.Saic.Com 6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 31     Sue Skonetski wrote:H > Many, many people have contributed to this effort, including managers,  6 > list of wonderful engineers removed by Sue Skonetski    F Seems to me that the engineers and their caretaker (Sue)  would be far more; important and should have been listed well before managers.   E Now that they have completed the port, can they can back to improving, VMS on VAX ????? ;-) :-) :-)u   ------------------------------  # Date: Sat, 01 Feb 2003 01:59:42 GMTe1 From: Michael Austin <maustin@firstdbasource.com> 6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 312 Message-ID: <3E3B2914.670FF50B@firstdbasource.com>   Sue Skonetski wrote: >  > -----Original Message----- >  > From: Grant, Clair > ( > Sent: Friday, January 31, 2003 3:40 PM > $ > To: OpenVMS Systems Software Group >  > Subject: VMS boots on Itaniums > J > We are please to announce that OpenVMS has booted on an HP i2000 ItaniumM > system. By successfully executing a DIRECTORY command the official date ande< > time for the Boot Contest is January 31, 2003 3:31 PM EST. > H > Many, many people have contributed to this effort, including managers,N > supervisors, project leaders, consultants, development infrastructure group,K > calling standard committee, engineers working on post-boot projects, etc.pM > All will receive their well-deserved credit as we proceed. The following is < > a very specific set of people; these are the engineers whoG > designed/wrote/debugged the code that comprises the running operatinga	 > system.  > 6 > list of wonderful engineers removed by Sue Skonetski     Congratulations!!!   -- e Regards,  6 Michael Austin            OpenVMS User since June 19847 First DBA Source, Inc.    Registered Linux User #261163i7 Sr. Consultant            http://www.firstdbasource.com,   ------------------------------  % Date: Sat, 01 Feb 2003 14:28:12 +1030e/ From: Mark Daniel <Mark.Daniel@wasd.vsm.com.au>e6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 31, Message-ID: <3e3b45cb_2@news.chariot.net.au>   Sue Skonetski wrote: > -----Original Message----- >  > From: Grant, Clair > ( > Sent: Friday, January 31, 2003 3:40 PM > $ > To: OpenVMS Systems Software Group >  > Subject: VMS boots on Itaniumt > J > We are please to announce that OpenVMS has booted on an HP i2000 Itanium	 > system.e
 8< snip 8<  C Many congratulations to VMS Engineering (who in spite of not a few _F obstacles and many naysayers have shown, once again, that they can do ; whatever they set their minds - and are permitted - to do!)b  F +--------------------------------------------------------------------+E   Mark Daniel                         http://wasd.vsm.com.au/adelaide F   mailto:Mark.Daniel@wasd.vsm.com.au (Mark.Daniel@dsto.defence.gov.au)F +--------------------------------------------------------------------+   ------------------------------    Date: 31 Jan 2003 22:18:31 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)h6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 313 Message-ID: <Lt5iVBJCpGCa@eisner.encompasserve.org>n  ^ In article <3e3b45cb_2@news.chariot.net.au>, Mark Daniel <Mark.Daniel@wasd.vsm.com.au> writes:  E > Many congratulations to VMS Engineering (who in spite of not a few sH > obstacles and many naysayers have shown, once again, that they can do = > whatever they set their minds - and are permitted - to do!).  > Presumably N-5 or so of the crew avoided naysayers by avoiding
 comp.os.vms .P   ------------------------------  % Date: Fri, 31 Jan 2003 21:03:06 -0400l0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>6 Subject: Re: OpenVMS Boots on Itanium on Friday Jan 31/ Message-ID: <3E3B1CBE.7C97E447@vl.videotron.ca>e   Shane Smith wrote: > J > IMHO the fact that managers in OpenVMS engineering contribute to gettingF > the job done is unique and impressive. Most management types seem to > have the opposite effect...$  N Which is why the engineers deserve an ever bigger round of applause since theyL managed to boot VMS on an intel chip DESPITE their managers getting involved :-) :-) ;-)L   ------------------------------    Date: 31 Jan 2003 12:34:32 -0800, From: mcbill20@hotmail.com (Bill McLaughlin)" Subject: Oracle 9i on VMS use LMF?= Message-ID: <e9cbc4f2.0301311234.6533d6a3@posting.google.com>N  E Can anyone tell me if Oracle 9i on VMS uses LMF? If not, do they have C their own "enforcement" or is it the same as in the past, where you03 are just supposed to use what you are licensed for?   D I use it at home just to keep up-to-date (the company I work for wasF using Oracle 7 until two months ago). A couple years back, I purchasedA a minimal license for around $300 but now I find that the minimum E license for VMS is for 5 users and does not even include any support.   D Last week almost all of us software people in the Denver office wereB laid off, so I figure now it's even more important to stay current with technology.   Thanks.e Bill McLaughlin    ------------------------------  % Date: Fri, 31 Jan 2003 14:28:34 -0500 , From: "Island" <dbturner@nospamislandco.com>/ Subject: Selling: New 9.1GB 10KRPM Disks USD109 / Message-ID: <v3ljjbrd6d7aa6@news.supernews.com>2  ; Brand NEW Compaq Branded (DEC) Ultra2 (Backward Compatible)$/ 9.1GB U2SCSI Wide Disk Drive 68 Pin Low Profilet' (Formatted to 8678MB for VMS and Tru64)L   $109 each while stocks lastP  ? Fully Compatible with DS10, DS10L, XP1000, Alpha PWS, AS500 etcm  
 Call or emailL   Toll Free 877-636 4332   Island Computers US Corporationd 2700 Gregory St., Suite 180a Savannah GA 31404b Tel: 912 447 6622: Fax: 912 201 0402l Email: dbturner@islandco.com www.hpaq.net   ------------------------------    Date: 31 Jan 2003 15:26:04 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)$ Subject: Re: Submit at end of month?= Message-ID: <b096a4ee.0301311526.129ec7a1@posting.google.com>   \ carl@gerg.tamu.edu (Carl Perkins) wrote in message news:<31JAN200311410859@gerg.tamu.edu>...4 > spamsink2001@yahoo.com (Alan E. Feldman) writes... [...]p > [...]eG > }OK, that's not the algorithm's fault, you say. And you're right! But I > }it could also fail at least in an "idealized" world. Suppose it is runrH > }just before midnight New Year's Eve. That is, 31-DEC-XXXX 23:59:59.98I > }or so and the month portion is evaluated before the change of year and^H > }the year portion is evaluated after the change of year. In that case, > }it will fail. > } H > }Of course, practically, this is either extremely, extremely unlikely,H > }or perhaps even impossible. I don't know enough internals to tell forD > }sure, but I suspect it may well happen at least on slow machines. > } @ > }Yeah, this is nitpicking, but "[in] no case" is a very strong
 > }statement.  >  > Oops.  > G > You are right that the code can actually produce an incorrect result,AF > but not during the January to December transition - it could give anK > incorrect result during the November to December transition. (See below.)   = Oops! You're right! But you did get the jist of what I meant.   D Anyway, I tried the following command several times with and withoutF higher priority processes running and only once got a positive result:  > $ A = "''F$CVTIME()' + ''F$PARSE("GEN:TO.COM")' ''F$CVTIME()'"
 $ SH SYM A   A = "2003-01-31 21:25:50.69 +e? DISK$DATA1:[FELDMAN.UTI.GENERAL]TO.COM; 2003-01-31 21:25:50.70"   ? (Don't ask about the spurious plus sign -- it was just a typo.)a  F I was concerned that such a short line of DCL might be "atomic" or runF so fast that the clock wouldn't be updated in the interim. But this isC proof that it can happen, barring anything else that might still bed overlooked, of course.  A I used F$PARSE because it actually takes a short while to run, atdE least compared to many other DCL commands. But it also means that the A failure mode has a "vanishingly small" probability, since I could$A obtain different times only once with a relatively slow operationt placed in the way.   [...]e >  > Here's a fix:  > 5 > $ base_date = F$CvTime("1--+31-","ABSOLUTE","DATE") 7 > $ next_month = F$CvTime(base_date,"ABSOLUTE","MONTH") < > $ next_months_year = F$CvTime(base_date,"ABSOLUTE","YEAR") > $ last_day_of_this_month = -M >     F$CvTime("01-''next_month'-''next_months_year'-1-", "ABSOLUTE", "DATE")+ > F > Since both month and year are based on the same time returned by theF > single earlier call, you can't get it split due to the date changing > between calls. > G > You can also eliminate the "next_months_year" symbol and simplify theh > final date string some:  > 5 > $ base_date = F$CvTime("1--+31-","ABSOLUTE","DATE")t > $ next_month = "1-" + - 4 >   F$CvTime(base_date,"ABSOLUTE","MONTH") + "-" + -) >   F$CvTime(base_date,"ABSOLUTE","YEAR") K > $ last_day_of_this_month = F$CvTime("''next_month'-1-","ABSOLUTE","DATE")d > G > That's still pretty short and pretty clear. It also provides you withsH > a symbol holding the first day of next month ("next_month", of course)( > as well as the last day of this month.  
 Good fix.    [...]    Disclaimer: JMHO Alan E. Feldmanu  F "Thank you for your time, this time, until next time" -- Roger Grimsby6 (Eyewitness News, Channel 7, New York, many years ago)   ------------------------------    Date: 31 Jan 2003 19:30:31 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)$ Subject: Re: Submit at end of month?= Message-ID: <b096a4ee.0301311930.73239cf1@posting.google.com>r  v "John Smith" <a@nonymous.com> wrote in message news:<6jy_9.522108$F2h1.287066@news01.bloor.is.net.cable.rogers.com>...= > "Alan E. Feldman" <spamsink2001@yahoo.com> wrote in message 9 > news:b096a4ee.0301310715.6ea97302@posting.google.com...06 > > carl@gerg.tamu.edu (Carl Perkins) wrote in message, >  news:<30JAN200311091091@gerg.tamu.edu>...- > > > "John Smith" <a@nonymous.com> writes...n) > > > }<geff@excite.com> wrote in messageo> > > > }news:2119a17f.0301292159.201411cc@posting.google.com...8 > > > }> I'm sorry - I mean 31-JAN, 28-FEB, 31-MAR, etc. > > > }> > > > } A > > > }Do you want to be able to handle Feb. 29th in a leap year?w > >+G > > Yes, he wants it to handle leap years. Really, now. Did you (that's_E > > "you" as in John Smith, not Carl Perkins [I'm covering my behind!  > :-]hD > > ) really want the poster to type "Well, make that 29-FEB in leapC > > years"? I do suppose that "the last day of the following month"  >  would > > have been better, though.e > C > I've seen some pretty weird stuff over the years in terms of what'' > companies consider to be 'month-end'.o > E > I've seen companies that have fiscal year-end as Feb. 28 that count F > Feb 29th as part of the next fiscal year, and others that count Feb.F > 29th as the 'prior' fiscal year. Same thing for month-end reporting.  B That's wacky. The assumption should be "normal". If the poster hasE something wacky like that, it is his responsibility to make it clear. D This poster was being vague and if he gets a "bad" answer because of it, that's his problem.   B I was tempted to answer his first post with "Could you be a little more vague?"  G > I've also seen companies that take every 4th Thursday or Friday as anaG > accounting period end - they get 13 month-ends per year that way (one0G > large brokerage firm that has a large ugly animal as its 'symbol' didaD > it that way for many years - they handed out a photocopied 10-yearG > table showing which date each accounting period closed so staff could D > refer to going backwards/forwards without having to rely on simple@ > concepts like 'the last day of each month is when we close theE > accounting period'). As a result, sometimes fiscal year-end fell ineD > December and sometimes in January using that method, and sometimesC > people wound up working on Christmas Day manually posting journal8- > entries trying to close books for year end.c  / Wacky. Maybe they're trying to confuse the IRS.r  : > And as we also know, most business system development isE > straightforward if you don't have to deal with legal and regulatorysF > matters. What you and I may consider to be logical isn't always thatE > way in the minds of accountants, lawyers, and politicians - look atCE > the tax system for an example. Hence my question about dealing withs > Feb. 29th.  D OK. But it is the poster's responsibility to elucidate any weirdness in his question.   Disclaimer: JMHO Alan E. Feldmani   ------------------------------    Date: 31 Jan 2003 13:24:52 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) " Subject: Re: VMS source listings ?3 Message-ID: <ldHnzp+utLRI@eisner.encompasserve.org>r  R In article <r8fl3vs1349jkmev9fpeclolagr0uuj1ee@4ax.com>, Dan <dan@vrx.net> writes:H > On 30 Jan 2003 16:08:50 -0600, Kilgallen@SpamCop.net (Larry Kilgallen) > wrote:  L >>The location rules are the terms whereby the source listings are licensed.J >>Whether there are terms other than full-time employment that would allow: >>them to show you the source has not been discussed here. >  > Location: Sol System  F Fine by me.  Send HP your check and see if they will sign the contractE worded that way.  Report back here if they do, I am sure we would allI be interested.   ------------------------------   End of INFO-VAX 2003.063 ************************