1 INFO-VAX	Sat, 21 Oct 2000	Volume 2000 : Issue 589       Contents: Re: 2nd Hand sales in Europe. 3 Re: Encompass Bylaw Ballot: THE ENVELOPE, PLEASE...  Great service from Camintonn!  Handling oddball disks" Re: hex numbers with CLD + $NUMBER LIB$FIND_IMAGE_SYMBOL Error % Re: New OpenVMS Freeware Submissions?  Re: Odd File Expiration Dates  Re: Odd File Expiration Dates  Re: PDF under OpenVMS  Re: PF keys ' Re: Proliant DL 360 x Alphaserver DS10L @ Re[2]: What connector to use to interconnect X.25 and DECNet V ? Script Under Systartup" Re: Second ethernet for uVAX3180 ? Stockholm Exchange OM and VMS? Re: Sun "uptime" belly laugher Re: Sun "uptime" belly laugher Re: Sun "uptime" belly laugher Re: User Guide for Vax (VMS) Re: Xemacs on OpenVMS ?   F ----------------------------------------------------------------------   Date: 21 Oct 2000 08:23:49 GMT( From: brian-DOT-mcneil@easynet.be (BMcN)& Subject: Re: 2nd Hand sales in Europe.+ Message-ID: <8FD460AA2BMcN@212.100.160.123>   D Thanks to everyone who gave some advice on this, I'm now waiting on B delivery of an AlphaServer 2100 4/275 and am one very happy bunny!  , Paid roughly the equivalent of $1900 for it.   --  + Reply to brian<dot>mcneil<at>easynet<dot>be   - The crux of the biscuit is the Apostrophe (')  - F.Z.   ------------------------------    Date: 21 Oct 2000 08:37:46 -05001 From: kaplow_r@eisner.decus.org.mars (Bob Kaplow) < Subject: Re: Encompass Bylaw Ballot: THE ENVELOPE, PLEASE...+ Message-ID: <d1vI5WTVKw2E@eisner.decus.org>   R In article <G2rJs1.6nI@spcuna.spc.edu>, Terry Kennedy <terry@gate.tmk.com> writes:F > In comp.org.decus Bob Kaplow <kaplow_r@eisner.decus.org.mars> wrote:M >> I object to the way this whole mess was handled. I violently object to the O >> BoD just sending the same damn thing back out again after it didn't pass the K >> first time. I can't think of a more arrogant reaction. Let's just ram it 2 >> down their throats until they swallow the shit. > L >   I'd like to point out that there are 7 amendments for your considerationM > this time, which are the efforts of some folks to address the issues raised 0 > by the "CON" statement in the original ballot.  I And what will we be left with if the bylaws pass, and the ammendments get I the same percentage vote as the bylaws did in the last election? The same + piece-of-crap that we voted down last time.   H I still can't believe the arrogance of the board this time around. No, IK don't want DECUS / Encompass / whatever to be history. But this just sucks. L I'm really tempted to vote NO on the bylaws, and YES on all the ammendments.L Or just join the majority of the "membership" and sit out this election like most did last time.   2 And the BoD wonders why voter turnout is so low...   ------------------------------  % Date: Sat, 21 Oct 2000 16:15:36 +0200 , From: "Bart Zorn" <B.Zorn@TrueBit.nospam.nl>& Subject: Great service from Camintonn!* Message-ID: <8ss8jd$5kt$1@buty.wanadoo.nl>   I thougth I would let you know:   J I have a DECserver 700 at home. It needs a 1- or 4 MB simm module, but the( one that I had fails (most of the time).  J So I needed a 4 MB memory module. These used to be normal a few years ago,H but nowadays the kids who work in the computer stores won't even believe that those things ever existed.   I I was at the trade show of the CETS2000 conference. I decided to find out  what I could find out there.  J I asked the guys at the Digital Networking Products Group, who, after all,L still sell the DECserver. They leafed through their catalog and yes, I couldF order a memory module. Costs a couple of hundred bucks (yuck!). I said: thanks, but no thanks. A bit too much for my home systems.  H With CPUoptions, I got a business card of the person who might know more about DECserver memory.   G Then I went to Camintonn, a company with a long tradition of delivering L memory modules for a lot of different Digital/Compaq systems. I explained myF problem to Anna Wilkinson. She said that there must be some modules atH stock. If I came back the next day, she could sell me one for $ 15. ThatJ sounded good! However, the next day the message was even better. Anna toldD me she didn't have the module, but that she would arrange to have itL Fedex'ed to my hotel the next day, FREE of charge! The next day I received a1 package containing not one, but two 4 MB modules!   % Now my DECserver 700 runs fine again.   H Thank you very much for this really friendly service, Anna Wilkinson and
 Camintonn!   Regards,  	 Bart Zorn    ------------------------------  % Date: Sat, 21 Oct 2000 12:50:17 -0500 , From: "Glenn C. Everhart" <Everhart@GCE.com> Subject: Handling oddball disks ' Message-ID: <39F19109.676BCE9A@GCE.com>   G I have been getting some oddball SCSI disk brands now and then and have 
 found thatC they worked erratically. Concluding that this was likely due to the  drive not doing G tagged queueing right, I tried using scsi_mode to set offset 03 of page  0a to 1 ? to disable it. Woe is me. My 3000-300LX box doesn't seem to run  scsi_mode correctly  (for whatever reaason).   C So I decided it made more sense to arrange that dkdriver should not 
 attempt toH do tagged queueing on "generic" disks (i.e., the pc junk I was trying to use).   6 This might be of wider interest so here goes with how.  E The following macro defines device characteristics found in dkdriver. G The device ID is the identifier returned on INQUIRY, which is generally  what shows up in the  
 >>>SHO DEV  ? display as the device name. This is how a device is recognized.   = The table of specific device types can be located easily in a : copy of sys$dkdriver.exe by looking for ASCII strings like RZ23, RZ57, etc.  8 Note that the structure of entries is as the macro below defines:6 1. a one byte VMS device type (need not be definitive); 2. Flags byte. Most commonly the value 03 is in this, i.e., B         disconnect and sync modes supported. To disable disconnect"         for example, change to 02. 3. A word (2 bytes) padding @ 4. The device ID string (up to 8 ASCII characters, space padded)D 5. Minimum firmware rev level, a longword. Usually just zero.       1 .SBTTL  SCSI_DEV_TYPES  - Build SCSI device table  ;+ ; SCSI_DEV_TYPES ; D ; This macro builds a table of pre-defined SCSI device types. During unitH ; initialization, an inquiry command is sent to the target which returnsG ; 8 bytes of ID string. The table is then scanned for a matching ID. If  one H ; is found, information for that entry is copied into the UCB, including the B ; device type, media ID, disconnect/synchronous flags, and various timeout F ; values. If no matching entry is found, the device is assumed to be aF ; "generic" SCSI disk, and the entry for generic devices is used. Each entry 4 ; in the device type table has the following format: ; !         $DEFINI SCSI_DEVICE_ENTRY A $DEF    DTYP_TYPE       .BLKB   1               ; VMS Device type H $DEF    DTYP_FLAGS      .BLKB   1               ; Flags.  Bit set means:1         $VIELD  DTYP,0,<-                       ; D           <DISC,,M>,-                           ; Bit 0 = disconnect support C           <SYNC,,M>,-                           ; Bit 1 = sync mode  support E           <NO_TCQ ,,M>,-                        ; Bit 2 = disable TCQ  support G           <MODE_10,,M>>                         ; Bit 3 = Mode Sense 10  req'd C $DEF    <>              .BLKW   1               ; Pad for alignment ; $DEF    DTYP_ID_STRING  .BLKL   2               ; ID String E $DEF    DTYP_MINREV     .BLKL   1               ; Min. Revision level : $DEF    DTYP_MEDIA_ID   .BLKL   1               ; Media IdF $DEF    DTYP_PHASE_TMO  .BLKW   1               ; Phase Change TimeoutD $DEF    DTYP_DISC_TMO   .BLKW   1               ; Disconnect TimeoutE $DEF    DTYP_TABLE_ENTRY_SIZE                   ; Size of SCSI Device 
 Table Ent$!         $DEFINI SCSI_DEVICE_ENTRY   @ ; Each table entry is  24 bytes, which allows successive entries ; to be naturally aligned.  +         ASSUME  DTYP_TABLE_ENTRY_SIZE EQ 24   6 ; The table is terminated with a VMS device code of 0. ;-$         .MACRO  SCSI_DEV_TYPES, LIST         .ALIGN  LONG$         .IF IDN <ID_STRING>, GENERIC GENERIC_SCSI_DISK:
         .ENDC   
 ; Device type   !         .BYTE   DT$_'DEVICE_TYPE'   - ; Flags, including disconnect and synchronous            $$$FLAGS = 0C         .IIF IDN DISCONNECT, YES, $$$FLAGS = $$$FLAGS + DTYP$M_DISC D         .IIF IDN SYNCHRONOUS, YES, $$$FLAGS = $$$FLAGS + DTYP$M_SYNCH         .IIF IDN TAGGED_QUEUING, NO, $$$FLAGS = $$$FLAGS + DTYP$M_NO_TCQ:         .IIF IDN MODE_SENSE_10, YES, $$$FLAGS = $$$FLAGS + DTYP$M_MODE_10         .BYTE   $$$FLAGS  ! ; Pad to longword align the entry            .WORD   0   3 ; 8 character product ID string, padded with spaces   %         .NCHR   $$$STRLEN,<ID_STRING> G         .IIF GT $$$STRLEN-8, .ERROR ;Illegal SCSI product ID: ID_STRING          $$$PADCNT = 8-$$$STRLEN          .ASCII  /ID_STRING/          .REPT   $$$PADCNT          .ASCII  / / 
         .ENDR   F ; Minimum revision level. This field is compared to the revision field returnedG ; in the inquiry data. If the device is out of rev, an error is logged.   7         .ASCII  /MINIMUM_REVISION/       .IF B MEDIA_ID !         MEDIA <DK>, <DEVICE_TYPE>          .IFF         MEDIA <DK>, <MEDIA_ID>
         .ENDC          .IFFA         MEDIA   <DK>, <DKX00>, DT$_Generic_DK   ; Media value for  generic DK de$
         .ENDC    ; Phase change timeout  >         $$$PHASE_CHANGE_TIMEOUT = DEFAULT_PHASE_CHANGE_TIMEOUT-         .IF DIF PHASE_CHANGE_TIMEOUT, DEFAULT >                 $$$PHASE_CHANGE_TIMEOUT = PHASE_CHANGE_TIMEOUT
         .ENDC '         .WORD   $$$PHASE_CHANGE_TIMEOUT    ; Disconnect timeout  :         $$$DISCONNECT_TIMEOUT = DEFAULT_DISCONNECT_TIMEOUT+         .IF DIF DISCONNECT_TIMEOUT, DEFAULT :                 $$$DISCONNECT_TIMEOUT = DISCONNECT_TIMEOUT
         .ENDC %         .WORD   $$$DISCONNECT_TIMEOUT              .ENDM   SCSI_DEV_TYPES1            .IRP    ENTRY,<LIST>         SCSI_DEV_TYPES1 ENTRY 
         .ENDR            .ENDM   SCSI_DEV_TYPES  '         .SBTTL  SCSI device types table  ;+ ; SCSI_DEVICE_TABLE+ ; SCSI_DEVICE_TABLE  ; G ; This table is used to translate the product ID field from the inquiry  dataC ; to a VMS device type. Once the device type is determined, various  information G ; about the device such as disconnect and synchronous flags and timeout  vaules ; is saved in the UCB. ; ) ; To clarify the meanings of some fields:  ; E ; TCQ:  A value of NO means that the device should be unconditionally  treated @ ;       as incapable of tagged command queuing.  Any other value indicates thatG ;       the drive should be declared TCQ, provided 3 factors test true: @ ;       - The Inquiry TCQ support bit is set.SCSI_DEVICE_TABLE::   SCSI_DEV_TYPES <-  ; B ; ID string  Dev type    Media ID Min Rev Disc Synch Phas tmo Disc$ tmo            TCQ     Mode Sense 10= ; ---------  --------    -------- ------- ---- ----- -------- ) ---------         --------- -------------  ; =   <<RZ22>,    RZ22,       ,       <0615>, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ23>,    RZ23,       ,       <0615>, YES,  NO,  DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ23L>,   RZ23L,      RZL23,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ24>,    RZ24,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ25>,    RZ25,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ31>,    RZ31,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ55>,    RZ55,       ,       <0700>, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ56>,    RZ56,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ57>,    RZ57,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<ALCITA>,  FD3,        ,       <    >, NO,   YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ57I>,   RZ57I,      RZI57,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ58>,    RZ58,       ,       <    >, YES,  YES, DEFAULT, ' DEFAULT,          DEFAULT,        NO >>    SCSI_DEV_TYPES <- =   <<RRD40>,   RRD40S,     RRD40,  <250D>, YES,   NO, DEFAULT, ( RRD40_DISC_TMO,   DEFAULT,        NO >,-=   <<RRD42>,   RRD42,      ,       <    >, YES,   NO, DEFAULT, ' RRD42_DISC_TMO,   DEFAULT,        NO >>    SCSI_DEV_TYPES <- =   <<RZ72>,    RZ72,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ73>,    RZ73,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ35>,    RZ35,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RWZ01>,   RWZ01,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ24L>,   RZ24L,      RZL24,  <    >, YES,  YES, DEFAULT, / DEFAULT,          DEFAULT,    SCSI_DEV_TYPES <- =   <<RZ55L>,   RZ55L,      RZL55,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ56L>,   RZ56L,      RZL56,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ57L>,   RZ57L,      RZL57,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ26>,    RZ26,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ36>,    RZ36,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ74>,    RZ74,       ,       <    >, YES,  YES, DEFAULT, ' DEFAULT,          DEFAULT,        NO >>            .IF DEFINED RZ74_CACHE-         .print ; Add comment to previous line  SCSI_DEV_TYPES <- = <<RZ74>,    RZ74,         ,       <436A>, YES,  YES, DEFAULT, ' DEFAULT,          DEFAULT,        NO >> 
         .ENDC    SCSI_DEV_TYPES <- =   <<RZ27>,    RZ27,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ37>,    RZ37,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ38>,    RZ38,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ75>,    RZ75,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ59>,    RZ59,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ34L>,   RZ34L,      RZL34,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ35L>,   RZ35L,      RZL35,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ36L>,   RZ36L,      RZL36,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RRD43>,   RRD43,      ,       <    >, YES,   NO, DEFAULT, ( RRD42_DISC_TMO,   DEFAULT,        NO >,-=   <<RRD44>,   RRD44,      ,       <    >, YES,   NO, DEFAULT, ' RRD42_DISC_TMO,   DEFAULT,        NO >>    SCSI_DEV_TYPES <- =   <<RZ13>,    RZ13,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ14>,    RZ14,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ15>,    RZ15,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ16>,    RZ16,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ17>,    RZ17,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ18>,    RZ18,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ51>,    EZ51,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ52>,    EZ52,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ53>,    EZ53,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ54>,    EZ54,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ58>,    EZ58,       ,       <    >, YES,  YES, DEFAULT, 0 DEFAULT,          DEFAULT,     SCSI_DEV_TYPES <-=   <<HSZ10>,   HSZ10,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ28>,    RZ28,       ,       <    >, YES,  YES, DEFAULT,e( DEFAULT,          DEFAULT,        NO >,-=   <<RZ29>,    RZ29,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<Cp350>,   RZ22,       ,       <    >, YES,  YES, DEFAULT,a( DEFAULT,          DEFAULT,        NO >,-=   <<Cp3100-1> RZ23,       ,       <    >, YES,  YES, DEFAULT,o( DEFAULT,          DEFAULT,        NO >,-=   <<1578-15>, RZ55,       ,       <    >,  NO,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<CM 210>,  RRD40S,     RRD40,  <    >, YES,   NO, DEFAULT,u( RRD40_DISC_TMO,   DEFAULT,        NO >,-@   <<RX23>,    RX23S,      RX23,   <    >, YES,   NO, RX_PHS_TMO,% RX_DISC_TMO,   DEFAULT,        NO >,--@   <<RX33>,    RX33S,      RX33,   <    >, YES,   NO, RX_PHS_TMO,% RX_DISC_TMO,   DEFAULT,        NO >,-e@   <<RX26>,    RX26,       ,       <    >, YES,   NO, RX_PHS_TMO,% RX_DISC_TMO,   DEFAULT,        NO >,-t=   <<XT-4380S>, RZ55,      ,       <B2  >, YES,   NO, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<GENERIC>, GENERIC_DK, ,       <    >, NO ,  YES, DEFAULT,m' DEFAULT,          DEFAULT,        NO >>h   SCSI_DEV_TYPES <-t=   <<RZ26B>,   RZ26B,      RZB26,  <    >, YES,  YES, DEFAULT,1( DEFAULT,          DEFAULT,        NO >,-=   <<RZ27B>,   RZ27B,      RZB27,  <    >, YES,  YES, DEFAULT,w( DEFAULT,          DEFAULT,        NO >,-=   <<RZ28B>,   RZ28B,      RZB28,  <    >, YES,  YES, DEFAULT,s( DEFAULT,          DEFAULT,        NO >,-=   <<RZ29B>,   RZ29B,      RZB29,  <    >, YES,  YES, DEFAULT,e( DEFAULT,          DEFAULT,        NO >,-=   <<RZ73B>,   RZ73B,      RZB73,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ74B>,   RZ74B,      RZB74,  <    >, YES,  YES, DEFAULT,t( DEFAULT,          DEFAULT,        NO >,-=   <<RZ75B>,   RZ75B,      RZB75,  <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RZ27L>,   RZ27L,      RZL27,  <    >, YES,  YES, DEFAULT,t( DEFAULT,          DEFAULT,        NO >,-=   <<RWZ21>,   RWZ21,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<HSZ20>,   HSZ20,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<HSZ40>,   HSZ40,      ,       <    >, YES,  YES, DEFAULT,a' DEFAULT,          DEFAULT,        NO >>i   SCSI_DEV_TYPES <- =   <<HSX00>,   HSX00,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<HSX01>,   HSX01,      ,       <    >, YES,  YES, DEFAULT,t( DEFAULT,          DEFAULT,        NO >,-=   <<HSZ15>,   HSZ15,      ,       <    >, YES,  YES, DEFAULT,r( DEFAULT,          DEFAULT,        NO >,-=   <<RZ26M>,   RZ26M,      RZM26,  <    >, YES,  YES, DEFAULT,0( DEFAULT,          DEFAULT,        NO >,-=   <<RW504>,   RW504,      ,       <    >, YES,  YES, DEFAULT,s( DEFAULT,          DEFAULT,        NO >,-=   <<RW510>,   RW510,      ,       <    >, YES,  YES, DEFAULT,s( DEFAULT,          DEFAULT,        NO >,-=   <<RW514>,   RW514,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RW516>,   RW516,      ,       <    >, YES,  YES, DEFAULT,o' DEFAULT,          DEFAULT,        NO >>e   SCSI_DEV_TYPES <-t=   <<RWZ52>,   RWZ52,      ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<RWZ53>,   RWZ53,      ,       <    >, YES,  YES, DEFAULT,l( DEFAULT,          DEFAULT,        NO >,-=   <<RWZ54>,   RWZ54,      ,       <    >, YES,  YES, DEFAULT,C+ DEFAULT,          DEFAULT,SCSI_DEV_TYPES <-d=   <<EZ31>,    EZ31,       ,       <    >, YES,  YES, DEFAULT, ( DEFAULT,          DEFAULT,        NO >,-=   <<EZ32>,    EZ32,       ,       <    >, YES,  YES, DEFAULT,n( DEFAULT,          DEFAULT,        NO >,-=   <<EZ33>,    EZ33,       ,       <    >, YES,  YES, DEFAULT,n( DEFAULT,          DEFAULT,        NO >,-=   <<EZ34>,    EZ34,       ,       <    >, YES,  YES, DEFAULT,u( DEFAULT,          DEFAULT,        NO >,-=   <<EZ35>,    EZ35,       ,       <    >, YES,  YES, DEFAULT,t( DEFAULT,          DEFAULT,        NO >,-=   <<EZ31L>,   EZ31L,      EZL31,  <    >, YES,  YES, DEFAULT,a( DEFAULT,          DEFAULT,        NO >,-=   <<EZ32L>,   EZ32L,      EZL32,  <    >, YES,  YES, DEFAULT,t( DEFAULT,          DEFAULT,        NO >,-=   <<EZ33L>,   EZ33L,      EZL33,  <    >, YES,  YES, DEFAULT,o' DEFAULT,          DEFAULT,        NO >>i         NO >,-=   <<RWZ31>,   RWZ31,      ,       <    >, YES,  YES, DEFAULT,-' DEFAULT,          DEFAULT,        NO >>       NO >>  
     NO >,-=   <<RZ25L>,   RZ25L,      RZL25,  <    >, YES,  YES, DEFAULT,-( DEFAULT,          DEFAULT,        NO >,-=   <<RZ26L>,   RZ26L,      RZL26,  <    >, YES,  YES, DEFAULT,v' DEFAULT,          DEFAULT,        NO >>C  9 ;       - The control mode page TCQ-disable bit is clear. . ;       - The underlying adapter supports TCQ. ;eD ; Mode Sense 10: YES means that all Mode Sense/Select commands shall attemptsB ;      the 10-byte version of the command first, then fall back to 6-byte onlyiG ;      if necessary.  NO means that only the 6-byte version should everg be atte$ ;-        C As can be seen, the table contains lots of ASCII strings for device  types, whichH makes it pretty easy to find this table in a copy of sys$dkdriver.exe on alpha.  H To do this we need a hex editor, so I go grab a copy of VFE. (I will put a copy ontolF the Fall 2000 sigtapes which will be out in a week or so for those who have no old one.)i  ; Just copy vfe_tv.exe to sys$system and vfe.hlb to sys$help.a  $ Now do something like the following:   $ set def sys$loadable_imagesiF $ copy sys$dkdriver.exe sys$dkdriver.exe   ! make a new version so the old one is untouched $ vfe/write sys$dkdriver.exe1 1>lo 'GENE'					! search for "generic" first party Find at block 140, byte 224 0 140> ASCII					! Let's be sure this is the table6 000:  ..(.....|RZ29    |    ..."|..(.0...|Cp350   |    ..."|..(.1...|Cp3100-1? 064:      ..."|..(.3...|1578-15 |    7.."|..(.4...|CM 210  |   p
 ("."|..(.>...mH 128:  RX23    |    ..."|..2.?...|RX33    |    !.."|..2.C...|RX26    |    ..."6 192:  ..2.3...|XT-4380S|B2  7.."|..(.6...|GENERIC |    ..."|..(.....|RZ26Bd? 256:      ..."|..(.....|RZ27B   |    ..."|..(.....|RZ28B   |   a
 ..."|..(.....qH 320:  XP34301 |    ..."|..(.....|RZ29B   |    ..."|..(.....|RZ73B   |    I.."6 384:  ..(.....|RZ74B   |    J.."|..(.....|RZ75B   |    K.."|..(.....|RZ27L ? 448:      ..."|..(.....|RWZ21   |    .}."|..(.....|HSZ20   |   ,
 .=."|..(.....o 140> 140>7   The table looks OK this way. Let's look at it in hex.i 140> HEXD 000:  08002800 89030000 525A3239 20202020 20202020 1DA0E522 08002800 30030000D 032:  43703335 30202020 20202020 16A0E522 08002800 31030000 43703331 30302D31D 064:  20202020 17A0E522 08002800 33020000 31353738 2D313520 20202020 37A0E522D 096:  08002800 34010000 434D2032 31302020 20202020 2822E522 08002800 3E010000D 128:  52583233 20202020 20202020 1780E522 1E003200 3F010000 52583333 20202020D 160:  20202020 2180E522 1E003200 43010000 52583236 20202020 20202020 1A80E522D 192:  1E003200 33010000 58542D34 33383053 42322020 37A0E522 08002800 36070000D 224:  47454E45 52494320 20202020 00BCC822 08002800 8F030000 525A3236 42202020D 256:  20202020 1AA1E522 08002800 90030000 525A3237 42202020 20202020 1BA1E522D 288:  08002800 91070000 525A3238 42202020 20202020 1CA1E522 08002800 92030000D 320:  58503334 33303120 20202020 1CA1E522 08002800 92030000 525A3239 42202020D 352:  20202020 1DA1E522 08002800 93030000 525A3733 42202020 20202020 49A1E522D 384:  08002800 94030000 525A3734 42202020 20202020 4AA1E522 08002800 95030000D 416:  525A3735 42202020 20202020 4BA1E522 08002800 97030000 525A3237 4C202020D 448:  20202020 1BA6E522 08002800 96030000 52575A32 31202020 20202020 157DE522D 480:  08002800 98030000 48535A32 30202020 20202020 143DD122 08002800 99030000  H Notice that byte 224 shows the ASCII. Now the macro definition shows the longE BEFORE the name has the flag we want in the second byte. Here this ishH shown as 92030000 (showing the word pad preceded by 03 which means synch modeG and disconnect are OK if the device claims they work. We set the 04 bit  andDF change this to 92070000 to disable tagged queueing. This is offset 221 140> CH 221,07 140> write			! write it out 	 140> exit=  H This changes the bit and writes it out. (Note you can type "help" to VFE and , get help as long as vfe.hlb is in sys$help.)  G This completes the change, which is visible after reboot. Note too thatD I keptG a copy of the untouched sys$dkdriver.exe so I could reboot from CD if IM goofedH it up, delete the altered one, and get back. No need this time: I got it right.  D Note too that similar changes could be accomplished for a particular kind ofSG disk by changing one of the strings to whatever is seen in INQUIRY (maxd 8 = characters; the INQUIRY device ID is generally what >>>sh devI	 displays.G  G When you have a device that seems to fail on large transfers, incorrecti taggedC queueing can easily be the problem. If you're careful and know what  you're0 about, this information can help you fix things.  G There is nothing special about VFE; any binary file editor can be used.  Note tooH if you don't use /write, VFE will not write anything out so you can look aroundD relatively safely. You can obviously roll your own VFE by building a simple app that H does $qio to some name, assigning the name and building it with debug to control it.E  H You must be careful not to goof up dkdriver though. Also if you do this, remember2 you'll need to do it any time dkdriver is updated.   ------------------------------  # Date: Sat, 21 Oct 2000 11:41:44 GMTi= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)C+ Subject: Re: hex numbers with CLD + $NUMBERM0 Message-ID: <009F1EBA.D273BC1D@SendSpamHere.ORG>  S In article <8sqbu4$qp7$1@nnrp1.deja.com>, moi_is_me <moi_is_me@my-deja.com> writes:  >Greetings,  >   I have a simple .CLD fileP >  >define verb            disc >       synonym         force  >       synonym         remove > D >       qualifier       user    value(required, list, type=$number),
 >nonnegatableLD >       qualifier       gateway value(required, list, type=$number),
 >nonnegatablea > * >       disallow        (user and gateway) >eD >  according to the CLD manuel, $number means decimal, octal or hex. >n! >  YET, if i attempt to parse saya >s >  disc /gate=(1F,2B). >  >  cli$get_value returns ...< >  %CLI-W-ABSENT, entity or value absent from command string >h/ >  BUT, if I instead use the decimal equivalentc >b >  disc /gate=(31,43)e >g, >  I get success, and can extract the values >r >  any ideas ? >r >  As usual ... TIAc >s >-Pierre >  > ' >Sent via Deja.com http://www.deja.com/S >Before you buy.     disc /gate=(%x1F,%x2B)   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  % Date: Sat, 21 Oct 2000 13:00:59 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>$ Subject: LIB$FIND_IMAGE_SYMBOL Error7 Message-ID: <200010211301_MC2-B7F3-8392@compuserve.com>E  J         When you post a question like this, please post the full and exac= tTB text of the error message.  The message should look something like5 SYSTEM-F-INVRFA, Invalid record's file address (RFA).   J         The "INVRFA" portion is the message id, which allows us to look u= pDH the message with HELP /MESSAGE, or to look it up the "Error Messages andJ Recovery Procedures" manual.  If you just can't bring yourself to type th= e>; whole thing, give us the message id instead of the text!!!!U  B         If my guess at "INVRFA" happens to be correct, try ANALYZEH /DISC_STRUCTURE on the disk where the file is stored and ANALYZE /RMS on the file in question.   % Message text written by James GriffinF > =    Good afternoon.   @ I have a complex application currently running on a VAX that I'mB porting to a DS20E.  The DS20 runs OVMS 7.2-1.  The code is almost exclusively fortran.  E The application makes use of shared images for global commons - there>G are a lot of semi-independent processes that make up the application. =L  D I've successfully ported the shared images and most of the processesG from VAX to Alpha, but there's one piece of code that's got me stumped.L  G The code uses LIB$FIND_IMAGE_SYMBOL to make sure that a shared image isUC installed (and, the image *is* installed).  The code goes something 
 like this:  H ISTAT=3D LIB$FIND_IMAGE_SYMBOL (ZRTNAME(1:INUM), ZRTNAME(1:INUM), IADDR)  C The program compiles and links just fine.  However, at run time, itDE bombs out when the above line is executed, returning a stack dump and ? an error line that reads "Invalid record's file address (RFA)".A  E Any suggestions?  This code works fine on OVMS 5.4-2 on a VAX.  ThereDD is a logical for the shared image defined in the System table.  I'veD copied the shared image to SYS$SHARE: and done several other similar things, all to no avail. <<   ------------------------------  % Date: Sat, 21 Oct 2000 12:43:05 -0500 ) From: "John E. Malmberg" <wb8tyw@qsl.net>6. Subject: Re: New OpenVMS Freeware Submissions?. Message-ID: <sv3l90fgtv9a1@corp.supernews.com>  J I would set the follow-ups to comp.os.vms, but I can not find that setting with this newsreader.<  5 "Thomas Dickey" <dickey@saltmine.radix.network> wrote / in message news:8sntdi$9tn$1@news1.Radix.Net...Z >,G > I'm working toward that.  I started a port/update some months ago forEH > tin (which is entangled with socketshr ;-), and have newer versions ofH > lynx, vile and vttest which I intend to package for submitting.  Also,I > I've made changes to byacc to make it ANSI and thus palatable to DEC C.S > . > (unlike bison, byacc isn't dependent on gcc)  D Please see the recently posted articles on comp.os.vms on SOCKETSHR.  J If you rebuild SOCKETSHR and link it against the DEC C RTL, please name itF SOCKETSHRD as the mms file procedures at ftp://ftp.qsl.net/pub/wb8tyw/  K The source there corrects a problem with an uninitialized variable found in  earlier versions.   F Programs built with the existing version of SOCKETSHR binaries must be- linked with the VAX C RTL, not the DEC C RTL.   L Untangling SOCKETSHR should not be hard, but doing so may possibly eliminate% the program running on CMU-IP on VAX.    -John, wb8tyw@qsl.network   ------------------------------  % Date: Sat, 21 Oct 2000 13:12:59 -0400 & From: "Mike Duffy" <mdduffy@erols.com>& Subject: Re: Odd File Expiration Dates+ Message-ID: <8ssinu$2g0$1@bob.news.rcn.net>   B Has this system ever had Raxco's PerfectDisk (defragmenter) on it?  F That product uses retention dates (IIRC about 5 years into the future)J to calculate the file's last "read date".  The product wants to figure outD where to place files and thus needs to know if a file has been read, not just created or updated.   -MikeC      F jbecker@ui.urban.org wrote in message <8sqe4h$smi$1@nnrp1.deja.com>...@ >Can you think of any reason other than the obvious one why fileC >expiration dates would be "too far" into the future? The "obvious"DE >reason is the documented behavior around the current system time and  >volume retention times. >EE >There are a few funny circumstances that make me wonder if somethingZ >else is going on. >>E >But first, the background facts. This is a non-clustered AlphaServerZH >4100 5/533 running OpenVMS V6.2-1H3. For the last few years, disks haveG >had min & max retention settings of 30 days and 90 days, respectively; H >I've never seen an instance in which the settings were other than that.E >The only time anyone messed with the system time AFAIK was last yearLF >during a few hours of Y2K testing; no users were on the system at the( >time (controlled testing and all that). >OC >Today + 90 days is 18-JAN-2001, so I'm calling any expiration date % >beyond that a funny expiration date.- > 8 >The funny expiration dates fall into some odd patterns:H >- Scattered expiration dates occur throughout the period 19-JAN-2001 to" >24-FEB-2003 on about 5,000 files.A >- In 2004, a few hundred files have expiration dates from 16-FEB1 >through 27-FEB.H >- About 10,000 files have expiration dates from 28-FEB-2004 through 27-D >MAR-2004 (including most dates in between instead of just scattered >dates).F >- Apparently without exception, the creation dates for the files with; >funny expiration dates are in the past and look plausible.pE >- All of the above dates occur in many different directories on most C >disks. An interesting exception is the disk that went on line most A >recently, a few months ago, which has no funny expiration dates.< >8D >None of this seems to fit with someone just messing around with theF >system time or volume retention times, so that's why I'm wondering if! >there's something else going on.  >EF >I noticed the funny dates quite a few months ago (possibly last year,H >not sure), but I didn't pursue it at the time. I'm only wondering aboutH >it now because the funny dates are getting closer, which messes up someE >in-house system management tools that assume valid expiration dates.H3 >For example, previously, it was safe to use thingsTC >like /EXPIRED /BEFORE="+90-" to ignore files with funny expiration  >dates.A >, >Any ideas?- >  >--E >Jim Becker_, >The Urban Institute (http://www.urban.org/)8 >Encompass ESILUG (http://eisner.decus.org/lugs/esilug/) >  >Z' >Sent via Deja.com http://www.deja.com/  >Before you buy.   ------------------------------  % Date: Sat, 21 Oct 2000 13:17:33 -0400 & From: "Mike Duffy" <mdduffy@erols.com>& Subject: Re: Odd File Expiration Dates+ Message-ID: <8ssj8i$4v2$1@bob.news.rcn.net>F  5 I should have mentioned this in my previous response:9  5 PerfectDisk does not really care what the Minimum andE: Maximum retention periods are, it just uses the difference to do its calculation.  8 However, most sites do not use them, and the PerfectDisk3 documentation recommends enabling volume rentention,4 dates and gives an example of a little over 5 years.   -Mike> (A former Raxco employee)     F jbecker@ui.urban.org wrote in message <8sqe4h$smi$1@nnrp1.deja.com>...@ >Can you think of any reason other than the obvious one why fileC >expiration dates would be "too far" into the future? The "obvious" E >reason is the documented behavior around the current system time and< >volume retention times. >  [snip]   ------------------------------  # Date: Sat, 21 Oct 2000 11:55:18 GMT>= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)  Subject: Re: PDF under OpenVMS0 Message-ID: <009F1EBC.B806050E@SendSpamHere.ORG>  \ In article <39F0F22F.A5315A61@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: >Paul Sture wrote:J >> Which might explain why the HP 2100M has a PostScript _emulator_ rather >> than the real McCoy.  > N >I beleive that HP has triedto use cheaper emulators instead of the real stuffL >for quite a long time. The low end "postscript" printers rarely support the >real Adobe postcript. > L >I remember at a DECUS convention, I had to print some 1 page DECUS leafletsL >that had the DECUS logo on them.  Printing on the regular printer was fine,H >but when printed on the spanking new Digital-advertised heavy duty highL >production postscript printer, the scaling of the logo was not respected by3 >the printer so that made the printer unusable !!!!F  L I don't know about the "Digital-advertised heavy duty high production" Post-L Script printers but I've found my LNC02 to better handle the PostScript I'veK written better than any new HPs.  Perhaps, this thread has answered to thisUL observed difference -- real Adobe PS interpretation -vs- emulation.  I shop-K ped around looking at the output of various color laser printers and when IdL saw the output of a LNC02 at a DECUS trade show, I got home and ordered one.K HP has the greater marketshare of the laser printer market but I'm not con- 1 vinced it is for the reason of superior printing.O   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.,   ------------------------------  % Date: Sat, 21 Oct 2000 12:51:41 -0400 % From: "Tom DeLuca" <tomdel@erols.com>  Subject: Re: PF keys+ Message-ID: <8sshuc$q0h$1@bob.news.rcn.net>E  1 Xterm is good but how to emulate the VT keyboard?    --
 Tom DeLuca$ Mgr. Computer Operations - Radiology Johns Hopkins Hospital tdeluca@jhmi.edu    9 "Bob Koehler" <koehler@eisner.decus.org> wrote in message % news:MjscmcioKI9t@eisner.decus.org...LJ > In article <39DBA6B1.C3FAFECC@gtech.com>, Arne =?iso-8859-1?Q?Vajh=F8j?=  <arne.vajhoej@gtech.com> writes: > > . > > Unix telnet ? That may be more difficult ! > F > Generally when coming from UNIX I find it best to start xterm.  ThatG > requires X, but it does a useable job of VT100 emulation and it seems  > to always be there.E >LH > ----------------------------------------------------------------------A > Bob Koehler                     | Computer Sciences CorporationC? > Hubble Space Telescope Payload  | Federal Sector, Civil GroupmG >  Flight Software Team           | please remove ".aspm" when replyinge   ------------------------------  % Date: Sat, 21 Oct 2000 09:24:16 +020062 From: martin@radiogaga.harz.de (Martin Vorlaender)0 Subject: Re: Proliant DL 360 x Alphaserver DS10L; Message-ID: <39f144a0.524144494f47414741@radiogaga.harz.de>t  ! John Santos (JOHN@egh.com) wrote:x% : On 19 Oct 2000, Hoff Hoffman wrote:xJ : >   But realize that anything that is available now is already outdated. :iG : Dave Barry once proposed that all computer stores should have a largeiF : trash barrel at the end of each check-out counter so you could slideF : your brand-new (i.e. obsolete) computer directly into the trash with7 : ever having to actually pick it up and bring it home.o  B Somewhere, somewhen I read a proposition to not call it "new" when9 talking about computers, but "obsolete ready" instead :-)4   cu,    Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.de.N One OS to bring them all      |       http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  % Date: Sat, 21 Oct 2000 15:46:47 +0400|4 From: Valentin Likoum <valentin.likoum@ncc.volga.ru>I Subject: Re[2]: What connector to use to interconnect X.25 and DECNet V ? 2 Message-ID: <15205754.20001021154647@ncc.volga.ru>  8 On 20.10.2000 antonio.carlini <arcarlini@iee.org> wrote:   [snip]C >> problems. Can it be used as X.25 gateway for our Alphas as well?(
 >> Thank you.4  E > It almost certainly won't do GAP - I've never come across a non-DEC0 > box that will. [snip](   We don't need GAP any more. Pure LLC2.   > > You can also use XOT now if you prefer (X.25 over TCP) which= > both the cisco and the Alpha support (you'll need X.25 V1.4 B > on the Alpha ... assuming you are running OpenVMS on the Alpha).  $   Thank you very much for your help.   -- 0   Valentin Likoum2   valentin.likoum@ncc.volga.ru   ------------------------------  % Date: Sat, 21 Oct 2000 13:00:58 -040082 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: Script Under Systartup37 Message-ID: <200010211301_MC2-B7F3-8390@compuserve.com>0  J         You should check this, but I believe that SYSTARTUP_VMS is called=  J with P1=3D"STARTUP".  If my recollection is correct you should be able to=  say @SCRIPT-NAME 'P1'1    & Message text written by Jack TrachtmanG >I'm going to be calling a DCL script from within SYSTARTUP_VMS.COM via0F "@script-name".  The script needs to know that it is being run at boot@ time.  What can I include in the script for it to check for this condition?  Thanks.A <5   ------------------------------  % Date: Sat, 21 Oct 2000 09:41:55 +020002 From: martin@radiogaga.harz.de (Martin Vorlaender)+ Subject: Re: Second ethernet for uVAX3180 ?3; Message-ID: <39f148c3.524144494f47414741@radiogaga.harz.de>t   trevor_deja@my-deja.com wrote:B : Anyone know if there is / was an add in card to provide a second) : ethernet interface in a MicroVAX 3180 ?h  G Intraserver (http://www.intraserver.com/) has (had?) UltraSCSI/etherneteE boards for VAXen, but I've no idea whether the MicroVAX is supported.i   cu,D   Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.detN One OS to bring them all      |       http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  # Date: Sat, 21 Oct 2000 10:06:13 GMTe From: richard_maher@my-deja.como' Subject: Stockholm Exchange OM and VMS?h) Message-ID: <8srpqk$sef$1@nnrp1.deja.com>i   Hi,o  D Does anyone know why the Stockholm exchange's trading system crashed8 twice yesterday for a total of 2hours? Was VMS involved?   Regards Richard MaherI    & Sent via Deja.com http://www.deja.com/ Before you buy.l   ------------------------------  % Date: Sat, 21 Oct 2000 09:17:47 -0500 # From: "Mark E. Levy" <mark@fsi.net>d' Subject: Re: Sun "uptime" belly laughery/ Message-ID: <sv39si2erh9s27@corp.supernews.com>    Outstanding!  - "Paul Sture" <paul@sture.ch> wrote in messagea% news:VA.00000112.24c31313@sture.ch... E > In article <sv13kce892oc3c@corp.supernews.com>, Peter Weaver wrote:o
 > > $ input =oJ > > "14E64627567702963702F6E636560216761696E6023786F67796E676028696370265DJ > > 4350256E66797C202865672C6C6020727F6261626C69702861667560247F602465636F > > 6465602478F > > 6963702F6E6028696370286F6D6560284F62626979637470265D4350226F687E2" > > $ i = 0 
 > > $loop:+ > > $ output[i*4,4]=%X'F$EXTRACT(i,1,input)r > > $ i = i + 1-" > > $ if i .lt. 214 then goto loop= > > $ write sys$output "Today's secret message is: " + output  > >n
 > ROFLMAO! > ___X > Paul Sture
 > Switzerlande >w   ------------------------------  % Date: Sat, 21 Oct 2000 09:32:02 -0500a# From: "Mark E. Levy" <mark@fsi.net> ' Subject: Re: Sun "uptime" belly laugher / Message-ID: <sv3anepag04sa5@corp.supernews.com>   = "andrew harrison" <andrew.nospam@uk.sun.com> wrote in message $ news:39F06A69.C6FE3B6F@uk.sun.com...   >Arnef  > >You need to read more of this newsgroup than just the threads$ >where people are trying to FUD Sun.   My dear Andrew,t  L You really do need a hobby. Nobody in comp.os.vms needs to FUD Sun. Sun doesL a more than adequate job of that itself. I really can't beleive that you areH so dense that you actually believe that regulars to this news group care what you have to say..  H In my former life working for a national laboratory, I was a member of aI 4-person group responsible for managing several hundred VMS VAX and Alpha J systems of various sizes, both clustered & standalone. We had so little toI do that we spent most of our time helping the 15-person Unix group, whichSL had far fewer systems to manage. By far the most hated Unix was AIX, but Sun wasn't far behind.  K Give it up, Andrew. OpenVMS still has features that no other O/S can match.t  Sun is just another me-too Unix.  K Sun (the company) should stop patterning itself after heavenly objects. The1' Sun does go down everyday, after all..."   --E ---------------------------------------------------------------------2 Mark E. Levy, President@" System Management Associates, Inc.! 888-291-5055 x202 (Illinois Only)p$ 847-291-1550 x202 (Outside Illinois) 847-291-3866 fax www.sysman-inc.com levy@sysman-inc.comYE ---------------------------------------------------------------------V   ------------------------------  % Date: Sat, 21 Oct 2000 12:40:54 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>a' Subject: Re: Sun "uptime" belly laugherj- Message-ID: <39F1D526.C9DCD182@earthlink.net>    "Mark E. Levy" wrote:e [snip] a > Thee) > Sun does go down everyday, after all...A   OOOOOOHHHHHH !!!!!!,  6 Now wouldn't *THAT* make a tasty OpenVMS advert ???!!!  2 (Audio: ocean sounds, either beach-side or at sea)  H Fade up on a blazing sunset sky (as opposed to a Blazing Saddle! I know,E shutup!). Zoom out until the sky+horizon fills the frame, then titlesa over:   " (Fade in as zoom out continues...)   "The sun goes down every day."  F (While continuing to zoom out - a person on the beach/deck on a chaise% lounge enters the frame. Dissolve to)h  * "OpenVMS runs for years without stopping."  D Then, maybe quote the uptime of a certain railroad's VAX/VMS system.
 (Dissolve to)s  9 "OpenVMS from Compaq. Contact your local reseller today!"I  G For the full-page ad version, just use the full-frame final with titlesh over.    -- s David J. Dachterag dba DJE Systemsi http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/j  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.c   ------------------------------  % Date: Sat, 21 Oct 2000 19:23:22 +0200e% From: "Kirk Acid" <kirk.acid@lion.cc>o% Subject: Re: User Guide for Vax (VMS) 5 Message-ID: <IjkI5.18$gN1.2645@nreader1.kpnqwest.net>c   Hmm..  thats the prob.K How do i find out which version of vms i have installed and which ip-stack,u3 and if i know that how can i change the ip-addr. ??.  = is there a ftp-program in vms ??    can i install netscape ??f   A lot of questions !!!   Thanks, Andreas Safranek: Do you meen  the System Manager's Manual (Essentials) from openvms.digital.com ??* Couse i didnt get any Manual with the VAX    K David J. Dachtera schrieb in Nachricht <39F0DB82.5ABB43D9@earthlink.net>...e >Andreas Safranek wrote: >>  >> [snip]  I would need a manual= >> that discribes, for example, how to change the ip-address,n > I >For which TCP/IP stack? Gotta determine that first. There's three (up to,) >as many as five, really!) possibilities.e >e >> how to add a newc >> user, >s. >See the System Manager's Manual (Essentials). >l  >> where do i find binary-files, >n0 >Why? Well, if you must look for such things as: >/ >*.EXE >*.OLB >*.OBJ >  >...and a host of others.  >b >> and so on...t   ------------------------------   Date: 21 Oct 2000 12:28:24 GMT9 From: Roar =?iso-8859-1?Q?Thron=E6s?= <roart@nvg.ntnu.no>d  Subject: Re: Xemacs on OpenVMS ?3 Message-ID: <972127875.837562@tornado.itea.ntnu.no>t  > Brian Schenkenberger, VAXman- <system@sendspamhere.org> wrote:W : In article <m3bswfsgut.fsf@sebold.lcms.org>, Charles Sebold <sebold@lcms.org> writes:c :>spolato@my-deja.com writes:M :>@ :>> Does anyone know whether Xemacs has been ported on OpenVMS ? :>J :>I have seen no signs of it, although there may have been patches for v19G :>to run under VMS.  I suspect you'll have more luck with GNU Emacs 19, F :>but I haven't found binaries for that, and I can't get it to compileI :>under VMS 6.2 or later.  (If anyone has working binaries, VAX or Alpha,d> :>for Emacs 19, I would dearly love to snag them, by the way.)  H : You'll also not get it to compile with DEC C V5.6 and up due to a pre-G : processor bug.  I've just received a Compaq C6.3 beta that supposedly H : has this fixed.  What other evils may be lurking are still unbeknownst< : at this time but I'm certain I'll encounter more C demons.   : --Q : VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM 
 :            hQ : city, n., 1. a place where trees are cut down and streets are named after them.e   Funny.  # I compiled emacs-19_28-19970601 on:2  & DEC C V5.6-003 on OpenVMS VAX V7.1    + Compaq C V6.2-007 on OpenVMS Alpha V7.2-1  a  . But I had to do som renaming in [.src]sysdep.c& (bcmp to bcmp2 etc, and fork to vfork)  " On VAX, I had to add something in: configure.com*:m +$ LDFLAGS := /nodebug    *  $ if f$type(OPTS) .eqs. "" then OPTS = ""< +$ if f$type(CPP_NOOPSPACE) .eqs. "" then CPP_NOOPSPACE = ""  $ sys_includes = ""  )  $     CFLAGS := 'CFLAGS' /NESTED=INCLUDEi& +$     CPP_NOOPSPACE := /STANDARD=VAXC
  $    else  1  $ if f$type(CC) .nes. "" then __compiler := 'CC'p< -$ '__compiler' '__tmp'/preprocess='tempcname'-i 'tempcname'= +$! '__compiler' '__tmp'/preprocess='tempcname'-i 'tempcname' M +$ '__compiler' '__tmp' 'CPP_NOOPSPACE' /preprocess='tempcname'-i 'tempcname' I  $ search/nohead/output='tempcname'-stripped 'tempcname'-i "configure___"M  C  $ write config_status_file "$ CFLAGS=""''CFLAGS'""" ! ExperimentaltP +$ write config_status_file "$ CPP_NOOPSPACE=""''CPP_NOOPSPACE'""" ! Experimenta le?  $ write config_status_file "$ LN_S=""''LN_S'""" ! Experimentalh  H A lot of such CPP_NOOPSPACE, and maybe some manual removeal of spaces in makefiles/mmsfiles.h  
 descrip.mms*:o0         @ lib_src_dir = f$environment("DEFAULT")5 +       @ etc_dir := $(srcdir_dev)[$(srcdir_dir).etc]          @ set default [-.etc]g, -       @ etc_dir = f$environment("DEFAULT"), +       @ doc_dir = f$environment("DEFAULT")         @ set default 'a' <         @ write foo "$ define/user EMACSDATA ""''etc_dir'"""; -       @ write foo "$ define/user EMACSDOC ""''etc_dir'""" ; +       @ write foo "$ define/user EMACSDOC ""''doc_dir'"""eI         @ write foo "$ define/user TERMCAP ""''termcap_dir'TERMCAP.DAT"""l   [.src]vmsgmalloc.c:i         return NULL; +#if 0G        if (result >= vms_fake_heap_end && result < vms_real_heap_start)i         result = tmpadr[1][0]; +#else +       result = tmpadr[1][0]; +#endifc,        vms_brk_current = result + increment;  $ On Alpha, I had to add something in: [.src]vmsproc.h: +#define UCX$C_DSC_ALL 2  D I am not saying my changes are correct (especially with fork) but it* compiles. So far, only gnus crashes emacs.J (I am not sure all the changes are mine, I may have seen them here before)   -- t
 -Roar Throns    ------------------------------   End of INFO-VAX 2000.589 ************************