1 INFO-VAX	Tue, 09 May 2000	Volume 2000 : Issue 259       Contents:, anonymous users cannot ftp to cluster member0 Re: anonymous users cannot ftp to cluster member% Re: Auto login for telnet connections % Re: Auto login for telnet connections  AW: cdrom writer drive problem AW: cdrom writer drive problem" Re: AW: cdrom writer drive problem cdrom writer drive problem Re: cdrom writer drive problemL Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thL Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thL Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thL Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thL Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4th RE: Console Manager Replacement 7 FAQ - How do I subscribe to the SAMBA-VMS mailing list? 
 Internal date  Re: Internal date  Re: Internal date  Re: Internal date  Re: Internal date  Re: Internal date 3 LN15 printer setup: job remains in "starting" state 7 Re: LN15 printer setup: job remains in "starting" state  Re: Marketing opportunity  Re: Marketing opportunity  Re: Marketing opportunity  Re: Marketing opportunity / Re: MOP Deamon for DECSERVER under MS-DOS/WINxx / Re: MOP Deamon for DECSERVER under MS-DOS/WINxx  RE: Mozilla M15's out..." ODBC Drivers for OpenVMS RMS files& Re: ODBC Drivers for OpenVMS RMS files& Re: ODBC Drivers for OpenVMS RMS files& Re: ODBC Drivers for OpenVMS RMS files! Re: Pitch of the Margin bell Beep ! Re: Pitch of the Margin bell Beep 7 Re: Remote unix queues to VMS- HELP with RMS breaking..  S80 competitor of E10000?! Re: S80 competitor of E10000?! Re: S80 competitor of E10000?! Re: S80 competitor of E10000?! Re: S80 competitor of E10000?! Re: SCSI device names  Seagate ST19171N Set host/mop Re: Set host/mop RE: Set host/mop Re: Set host/mopP Re: Split line (Off-Topic)(was: Charlie Matco on DFWDAYS,A	Compaq Update Weekend tape label in EBCDIC Re: the latest billybox virus  Re: Unsolicited OpenVMS/NT book  Re: Unsolicited OpenVMS/NT book ) Re: Upgrading system disk ... many thanks ( Vaxstation 4000 90 on ebay - going today, Re: Vaxstation 4000 90 on ebay - going today Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy?  Re: Which VAX to buy? ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 ' Re: Why  RZ28M can't be used on VAX3100 & Re: Why RZ28M can't be used on VAX3100# Re: wich list: DIRECTORY limitation   F ----------------------------------------------------------------------  $ Date: Tue, 9 May 2000 00:57:03 -06000 From: Phillip Williams <phdevax@sleepy.lobo.net>5 Subject: anonymous users cannot ftp to cluster member E Message-ID: <Pine.LNX.4.21.0005090042330.7885-100000@sleepy.lobo.net>    Hello ; I set up an anonymous user account on my cluster (VMS 5-5.2 8 UCX 4.1) and followed the recommend procedure in the UCX8 Managemnet Guide, setting up an identifier and assigning. the RIGHTSLIST.DAT an ACL but I still get this  P PISCES>                                                                         P %%%%%%%%%%%  OPCOM   8-MAY-2000 02:20:11.51  %%%%%%%%%%%    (from node ANDERA atP   8-MAY-2000 02:20:09.65)                                                       P Message from user AUDIT$SERVER on ANDERA                                        P Security alarm (SECURITY) and security audit (SECURITY) on ANDERA, system id: 10P 49                                                                              P Auditable event:        Network login failure                                   P Event time:              8-MAY-2000 02:20:09.56                                 P PID:                    20400174                                                P Username:               ANONYMOUS                                               P Remote nodename:                        Remote node id:         3325785072      P Remote username:        FTP_C63B73F0                                            P Status:                 %LOGIN-F-RDBACCERR, error accessing rights data base    P                                                                                 P PISCES>                                                                           I PISCES is the boot node and ANDERA is one member of the cluster. Is there * something that I am over looking or what?? phillip    ------------------------------   Date: 9 May 2000 12:48:22 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)9 Subject: Re: anonymous users cannot ftp to cluster member 5 Message-ID: <8f91em$m3$2@mailint03.im.hou.compaq.com>   x In article <Pine.LNX.4.21.0005090042330.7885-100000@sleepy.lobo.net>, Phillip Williams <phdevax@sleepy.lobo.net> writes:< :I set up an anonymous user account on my cluster (VMS 5-5.29 :UCX 4.1) and followed the recommend procedure in the UCX 9 :Managemnet Guide, setting up an identifier and assigning / :the RIGHTSLIST.DAT an ACL but I still get this  ..Q :Status:                 %LOGIN-F-RDBACCERR, error accessing rights data base      ..A :PISCES is the boot node and ANDERA is one member of the cluster.      How many system disks?  K   If you have more than one system disk, make sure that all of the logical  H   names necessary for the OpenVMS Cluster are defined cluster-wide, and I   that these logical names are defined /SYSTEM/EXECUTIVE.  Here's a list  F   of the core definitions, from the V7.2 SYLOGICALS.TEMPLATE.  TCP/IP H   Services has at least a few files that can (should?) end up as common    files, as well.   L $! DEFINE/SYSTEM/EXECUTIVE SYSUAF                      SYS$SYSTEM:SYSUAF.DATO $! DEFINE/SYSTEM/EXECUTIVE SYSUAFALT                   SYS$SYSTEM:SYSUAFALT.DAT L $! DEFINE/SYSTEM/EXECUTIVE SYSALF                      SYS$SYSTEM:SYSALF.DATP $! DEFINE/SYSTEM/EXECUTIVE RIGHTSLIST                  SYS$SYSTEM:RIGHTSLIST.DATN $! DEFINE/SYSTEM/EXECUTIVE NETPROXY                    SYS$SYSTEM:NETPROXY.DATO $! DEFINE/SYSTEM/EXECUTIVE NET$PROXY                   SYS$SYSTEM:NET$PROXY.DAT O $! DEFINE/SYSTEM/EXECUTIVE NETOBJECT                   SYS$SYSTEM:NETOBJECT.DAT T $! DEFINE/SYSTEM/EXECUTIVE NETNODE_REMOTE              SYS$SYSTEM:NETNODE_REMOTE.DATQ $! DEFINE/SYSTEM/EXECUTIVE LMF$LICENSE                 SYS$SYSTEM:LMF$LICENSE.LDB V $! DEFINE/SYSTEM/EXECUTIVE VMSMAIL_PROFILE             SYS$SYSTEM:VMSMAIL_PROFILE.DATAQ $! DEFINE/SYSTEM/EXECUTIVE VMS$OBJECTS                 SYS$SYSTEM:VMS$OBJECTS.DAT W $! DEFINE/SYSTEM/EXECUTIVE VMS$AUDIT_SERVER            SYS$MANAGER:VMS$AUDIT_SERVER.DAT [ $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_HISTORY        SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA _ $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_DICTIONARY     SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA U $! DEFINE/SYSTEM/EXECUTIVE NETNODE_UPDATE              SYS$MANAGER:NETNODE_UPDATE.COM Z $! DEFINE/SYSTEM/EXECUTIVE VMS$PASSWORD_POLICY         SYS$LIBRARY:VMS$PASSWORD_POLICY.EXEW $! DEFINE/SYSTEM/EXECUTIVE LAN$NODE_DATABASE           SYS$SYSTEM:LAN$NODE_DATABASE.DAT  $!I $! DEFINE/SYSTEM/EXECUTIVE QMAN$MASTER                 device:<directory>     N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 09 May 2000 10:09:34 GMT # From: Mark Sterk <strong@chello.nl> . Subject: Re: Auto login for telnet connections) Message-ID: <3917E4CA.AC69231D@chello.nl>   M I have been testing this terminal emulator for some time now and I think it's  exelent and it's cheap too. N It has a very user friendly auto-login function and a fantastic keyboard remap	 function. # We are realy thinking of buying it.    Just try it.  . http://www.vandyke.com/products/crt/index.html         Mark               Mike Price wrote:   > > Most of our users used to be connected from VT terminals and  > terminal servers and used LAT.= > Increasingly people are using these new fangled PC thingies > > (they'll never catch on though) and are connected from a KEA > emulator window and TCP/IP. A > The old VT terminals where mostly automatically logged in using A > the SYSMAN ALF facility but we cannot yet find any way of doing A > this for the tlnet PC connections (except by using a KEA script A > which is a bit messy to maintain). The problem is that the port ! > number is different every time. > > Has anyone else seen this nad does anyone have a way to auto > login these connections. >  > Thanks in advance  >  > Mike Price >  > all views are my own etc etc.  > N > * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *I > The fastest and easiest way to search and participate in Usenet - Free!    ------------------------------  % Date: Tue, 09 May 2000 03:28:50 -0700 ? From: Mike Price <mike.priceNOmiSPAM@littlewoods.co.uk.invalid> . Subject: Re: Auto login for telnet connections9 Message-ID: <1d8766c4.03579289@usw-ex0104-033.remarq.com>    Thanks> Unfortunatly we really need to control the auto-login from the: VMS system. The emulator looks good but we need full VT420 emulation as a minimum. ? SO I still need a way of getting sysman LAF to recognise telnet  sessions from an NT pc   Any other ideas out there??    Mike  L * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *G The fastest and easiest way to search and participate in Usenet - Free!    ------------------------------  % Date: Tue, 09 May 2000 14:25:11 +0200 9 From: "Manser, Nazim (EXT)" <nmanser@union-investment.de> ' Subject: AW: cdrom writer drive problem @ Message-ID: <99371BC88DB7D311B79300508B95647E03EAD5@uf22.uid.de>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01BFB9B1.9F3DF632  Content-Type: text/plain;  	charset="iso-8859-1"   , thanks for your answer, i will upgrade soon.K But at console prompt i tried to boot the 7.2 cdrom and i got the following  error   
 >>> B dka500     DKA500    
 ?06 HLT INST   PC = 00000B15   PSL=041F004    what does it mean ??   Nazim Manser  , nmanser@union-investment.de (work temporary) manser@decus.de (permanent)   ' ------_=_NextPart_001_01BFB9B1.9F3DF632  Content-Type: text/html; 	charset="iso-8859-1"   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>H <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">H <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">- <TITLE>AW: cdrom writer drive problem</TITLE>  </HEAD>  <BODY>  C <P><FONT SIZE=2>thanks for your answer, i will upgrade soon.</FONT> i <BR><FONT SIZE=2>But at console prompt i tried to boot the 7.2 cdrom and i got the following error</FONT>  </P>  - <P><FONT SIZE=2>&gt;&gt;&gt; B dka500 </FONT>  </P>   <P><FONT SIZE=2>DKA500 </FONT> </P>  $ <P><FONT SIZE=2>?06 HLT INST </FONT>> <BR><FONT SIZE=2>PC = 00000B15&nbsp;&nbsp; PSL=041F004 </FONT> </P>  + <P><FONT SIZE=2>what does it mean ??</FONT>  </P>  # <P><FONT SIZE=2>Nazim Manser</FONT>  </P>  C <P><FONT SIZE=2>nmanser@union-investment.de (work temporary)</FONT> 3 <BR><FONT SIZE=2>manser@decus.de (permanent)</FONT>  </P>   </BODY>  </HTML> ) ------_=_NextPart_001_01BFB9B1.9F3DF632--    ------------------------------  % Date: Tue, 09 May 2000 15:47:51 +0200 9 From: "Manser, Nazim (EXT)" <nmanser@union-investment.de> ' Subject: AW: cdrom writer drive problem @ Message-ID: <99371BC88DB7D311B79300508B95647E03EAD9@uf22.uid.de>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01BFB9BD.2BB0344E  Content-Type: text/plain;  	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   D And how does the CDWRITER software at uni konstanz handle with VMS ?? i read that there is a cdburner software for VMS at your site . @ which devices are used as the cdburner ? which interface ? which7 architecture (vax or alpha ) which VMS version ? etc...       # -----Urspr=FCngliche Nachricht-----  Von: Eberhard Heuser-Hofmann, [mailto:vaxinf@CHCLU.CHEMIE.UNI-KONSTANZ.DE]( Gesendet am: Dienstag, 9. Mai 2000 14:58 An: nmanser@union-investment.de ' Cc: vaxinf@CHCLU.CHEMIE.UNI-KONSTANZ.DE ' Betreff: RE: cdrom writer drive problem    Nazim,  4 Under VMS you cannot access a cdrecorder as a cdrom,- because most drive only accept 2048 k Blocks.    eberhardI =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=  =3D=3D=3D=3D	 =3D=3D=3D    Dr. Eberhard Heuser-Hofmann  Univ. Konstanz Fakultaet fuer Chemie  Universitaets-Strasse 10 D-78464 Konstanz Germany . Phone: +49-7531-88-2026, FAX: +49-7531-88-3139* email: vaxinf@chclu.chemie.uni-konstanz.de  I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=  =3D=3D=3D=3D	 =3D=3D=3D   ' ------_=_NextPart_001_01BFB9BD.2BB0344E  Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =  charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2650.12"> - <TITLE>AW: cdrom writer drive problem</TITLE>  </HEAD>  <BODY>  F <P><FONT SIZE=3D2>And how does the CDWRITER software at uni konstanz = handle with VMS ?</FONT>H <BR><FONT SIZE=3D2>i read that there is a cdburner software for VMS at = your site .</FONT>C <BR><FONT SIZE=3D2>which devices are used as the cdburner ? which = D interface ? which architecture (vax or alpha ) which VMS version ? = etc...</FONT></P>  <BR> <BR>  < <P><FONT SIZE=3D2>-----Urspr=FCngliche Nachricht-----</FONT>6 <BR><FONT SIZE=3D2>Von: Eberhard Heuser-Hofmann</FONT> <BR><FONT SIZE=3D2>[<A =I HREF=3D"mailto:vaxinf@CHCLU.CHEMIE.UNI-KONSTANZ.DE">mailto:vaxinf@CHCLU.= " CHEMIE.UNI-KONSTANZ.DE</A>]</FONT>B <BR><FONT SIZE=3D2>Gesendet am: Dienstag, 9. Mai 2000 14:58</FONT>9 <BR><FONT SIZE=3D2>An: nmanser@union-investment.de</FONT> A <BR><FONT SIZE=3D2>Cc: vaxinf@CHCLU.CHEMIE.UNI-KONSTANZ.DE</FONT> A <BR><FONT SIZE=3D2>Betreff: RE: cdrom writer drive problem</FONT>  </P>   <P><FONT SIZE=3D2>Nazim,</FONT>  </P>  A <P><FONT SIZE=3D2>Under VMS you cannot access a cdrecorder as a = 
 cdrom,</FONT> G <BR><FONT SIZE=3D2>because most drive only accept 2048 k Blocks.</FONT>  </P>  ! <P><FONT SIZE=3D2>eberhard</FONT>  <BR><FONT = I SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>  </P>  4 <P><FONT SIZE=3D2>Dr. Eberhard Heuser-Hofmann</FONT>( <BR><FONT SIZE=3D2>Univ. Konstanz</FONT>/ <BR><FONT SIZE=3D2>Fakultaet fuer Chemie</FONT> 2 <BR><FONT SIZE=3D2>Universitaets-Strasse 10</FONT>* <BR><FONT SIZE=3D2>D-78464 Konstanz</FONT>! <BR><FONT SIZE=3D2>Germany</FONT> 2 <BR><FONT SIZE=3D2>Phone: +49-7531-88-2026, FAX: = +49-7531-88-3139</FONT> D <BR><FONT SIZE=3D2>email: vaxinf@chclu.chemie.uni-konstanz.de</FONT> </P>  
 <P><FONT =I SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= % =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>  </P>   </BODY>  </HTML> ) ------_=_NextPart_001_01BFB9BD.2BB0344E--    ------------------------------  # Date: Tue, 09 May 2000 14:45:45 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) + Subject: Re: AW: cdrom writer drive problemV0 Message-ID: <009E9D2C.3146E848@SendSpamHere.ORG>  | In article <99371BC88DB7D311B79300508B95647E03EAD9@uf22.uid.de>, "Manser, Nazim (EXT)" <nmanser@union-investment.de> writes:K >This message is in MIME format. Since your mail reader does not understandd= >this format, some or all of this message may not be legible.t  " PLEASE TURN OFF MIME when posting.   >m( >------_=_NextPart_001_01BFB9BD.2BB0344E >Content-Type: text/plain; >	charset="iso-8859-1", >Content-Transfer-Encoding: quoted-printable > E >And how does the CDWRITER software at uni konstanz handle with VMS ?A@ >i read that there is a cdburner software for VMS at your site .A >which devices are used as the cdburner ? which interface ? which 8 >architecture (vax or alpha ) which VMS version ? etc...  D I have CDrecord EXEcutables for both VAX and Alpha on my web site asD well as a pointer to the source.  There are a few "tweaks" needed toD get it compiled *properly* on VAX so, until those changes are mergedC into the current source, I'd suggest you download the VAX .EXE from  my site.  D I'm using a Yamaha CRW4416S on Alpha.  The Yamaha CRW4416S is a SCSID burner for CDR@4x/CDRW@4x and can read at 16x.  You will want to en-D sure that the firmware is at least V1.0f on the Yamaha.  Recently, IC had been given a chance to use a Plextor.  No problems there unless D you are planning to connect your SCSI to a uVAX 3100 series box.  If$ you do, you *MUST* use the GKDRIVER.  E The .EXEs on my web site will work with VAX V6.0 and above and, IIRC,e V7.1 Alpha and above.t   --N VAXman- OpenVMS APE certification number: AAA-0001           VAXman@TMESIS.COM  L GNU Freeware -- What does the GNU *really* stand for?  Garbage!  Not Usable!   ------------------------------  % Date: Tue, 09 May 2000 13:56:52 +0200C9 From: "Manser, Nazim (EXT)" <nmanser@union-investment.de>o# Subject: cdrom writer drive problemt@ Message-ID: <99371BC88DB7D311B79300508B95647E03EAD4@uf22.uid.de>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01BFB9AD.AA17ED1Ek Content-Type: text/plain;b 	charset="iso-8859-1"a  
 Hi Fiolks,  L I installed on my vax station 4000 model 60 a SCSI CDROM Writer DRive (Model XR-W2022 from JVC) i am running openvms v6.2   , The jumpers of the drive are set as follows:  ! Jumper 6 = OFF (Termination OFF)  5 Jumper 5 = OFF (device type cdrom read , ON  = write)  Jumper 4 = ON   (Parity on)t Jumper 3 = ON   (SCSI Id 5)  Jumper 2 = OFF Jumper 1 = ON     the speed is 6X read , 2x Write.  J there is no jumper about the 512 Byte Block size, nor is it documented (in* the manual ) how the block is interpreted.  6 at console level the drive was recognised as JVC R2626  0 when i boot from dka500  (vms7.1 or V7.2 cdroms)   >>> B dka500   DKA500   ?06 HLT INST PC = 00000B15	PSL=041F004M   >>>   
 at vms level r   $mount/over=id $1$dka500:@" %MOUNT-F-MEDOFL, Medium is offline   Here is the error logt  F  V A X / V M S        SYSTEM ERROR REPORT         COMPILED  8-MAY-2000 15:54:58J                                                                       PAGE 13.a  /  ******************************* ENTRY     493.a *******************************iF  ERROR SEQUENCE 1666.                            LOGGED ON:        SID 12000003F  DATE/TIME  8-MAY-2000 15:53:59.68                            SYS_TYPE 04140002  SYSTEM UPTIME: 0 DAYS 00:05:48%K  SCS NODE: EARTH                                               VAX/VMS V6.2   8  DEVICE ERROR  KA46  CPU FW REV# 3.  CONSOLE FW REV# 1.4  +  GENERIC DK SUB-SYSTEM, UNIT _EARTH$DKA500:           HW REVISION     30312E31I9                                        HW REVISION = 1.10         ERROR TYPE            05 C                                        EXTENDED SENSE DATA RECEIVED         SCSI ID               05 3                                        SCSI ID = 5.M        SCSI LUN              00 4                                        SCSI LUN = 0.        SCSI SUBLUN           00 7                                        SCSI SUBLUN = 0.         PORT STATUS     00000001 J                                        %SYSTEM-S-NORMAL, NORMAL SUCCESSFUL2                                         COMPLETION        SCSI CMD        007F001A                             00FFG1                                        MODE SENSE         SCSI STATUS           02 6                                        CHECK CONDITION    EXTENDED SENSE DATA          EXTENDED SENSE  00050070                         0A000000o                        00000000o                        00000020n                            0000?6                                        ILLEGAL REQUESTE                                        INVALID COMMAND OPERATION CODEa        UCB$B_ERTCNT          00c;                                        0. RETRIES REMAININGt        UCB$B_ERTMAX          00c;                                        0. RETRIES ALLOWABLE         ORB$L_OWNER     00010004l:                                        OWNER UIC [001,004]        UCB$L_CHAR      1EC54008 ;                                        DIRECTORY STRUCTUREDd4                                        FILE ORIENTED/                                        SHARABLEu0                                        AVAILABLE4                                        ERROR LOGGING0                                        ALLOCATED<                                        SOFTWARE "WRITE LOCK"7                                        CAPABLE OF INPUTr8                                        CAPABLE OF OUTPUT4                                        RANDOM ACCESS        UCB$W_STS           0000r      F  V A X / V M S        SYSTEM ERROR REPORT         COMPILED  8-MAY-2000 15:54:58J                                                                       PAGE 14.T          UCB$L_OPCNT     00000007 9                                        7. QIO'S THIS UNITA        UCB$W_ERRCNT        0007::                                        7. ERRORS THIS UNIT        IRP$W_BCNT          0000 ?                                        TRANSFER SIZE 0. BYTE(S):        IRP$W_BOFF          0000E<                                        TRANSFER PAGE ALIGNED        IRP$L_PID       00030039O6                                        REQUESTOR "PID"        IRP$Q_IOSB      00000000 C                        00000000        IOSB, 0. BYTE(S) TRANSFERREDT  * ANALYZE/ERROR/FULL/SINCE/OUT=JVC_CDROM.TXT     My question is:Y  > 1) have anyone have any experiences with WRITE CDROM DRives ? . 2) What is going wrong by the mount command ?    thanks for help.  H PS: sorry if some receives this post as MIMED Format, but i only have MS. OUTLOOK (set as text only) for sending emails     ' ------_=_NextPart_001_01BFB9AD.AA17ED1EM Content-Type: text/html; 	charset="iso-8859-1"E+ Content-Transfer-Encoding: quoted-printable:  1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">E <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =D charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2650.12">U) <TITLE>cdrom writer drive problem</TITLE>Y </HEAD>W <BODY>  2 <P><FONT SIZE=3D2 FACE=3D"Arial">Hi Fiolks,</FONT> </P>  E <P><FONT SIZE=3D2 FACE=3D"Arial">I installed on my vax station 4000 =$C model 60 a SCSI CDROM Writer DRive (Model XR-W2022 from JVC)</FONT>-B <BR><FONT SIZE=3D2 FACE=3D"Arial">i am running openvms v6.2</FONT> </P>  F <P><FONT SIZE=3D2 FACE=3D"Arial">The jumpers of the drive are set as = follows:</FONT>- </P>  E <P><FONT SIZE=3D2 FACE=3D"Arial">Jumper 6 =3D OFF (Termination OFF) =  </FONT>:G <BR><FONT SIZE=3D2 FACE=3D"Arial">Jumper 5 =3D OFF (device type cdrom =e! read , ON&nbsp; =3D write)</FONT>sG <BR><FONT SIZE=3D2 FACE=3D"Arial">Jumper 4 =3D ON&nbsp;&nbsp; (Parity =c
 on)</FONT>H <BR><FONT SIZE=3D2 FACE=3D"Arial">Jumper 3 =3D ON&nbsp;&nbsp; (SCSI Id =	 5)</FONT>i9 <BR><FONT SIZE=3D2 FACE=3D"Arial">Jumper 2 =3D OFF</FONT> 9 <BR><FONT SIZE=3D2 FACE=3D"Arial">Jumper 1 =3D ON </FONT>a </P>  < <P><FONT SIZE=3D2 FACE=3D"Arial">the speed is 6X read , 2x =
 Write.</FONT>  </P>  H <P><FONT SIZE=3D2 FACE=3D"Arial">there is no jumper about the 512 Byte =D Block size, nor is it documented (in the manual ) how the block is = interpreted.</FONT>a </P>  A <P><FONT SIZE=3D2 FACE=3D"Arial">at console level the drive was =u recognised as JVC R2626</FONT> </P>  H <P><FONT SIZE=3D2 FACE=3D"Arial">when i boot from dka500&nbsp; (vms7.1 = or V7.2 cdroms)</FONT> </P>  = <P><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; B dka500</FONT>o </P>  . <P><FONT SIZE=3D2 FACE=3D"Arial">DKA500</FONT> </P>  4 <P><FONT SIZE=3D2 FACE=3D"Arial">?06 HLT INST</FONT>? <BR><FONT SIZE=3D2 FACE=3D"Arial">PC =3D 00000B15&nbsp;&nbsp; =  PSL=3D041F004</FONT> </P>  4 <P><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt;</FONT> </P>  5 <P><FONT SIZE=3D2 FACE=3D"Arial">at vms level </FONT>  </P>  C <P><FONT SIZE=3D2 FACE=3D"Arial">$mount/over=3Did $1$dka500:</FONT>-> <BR><FONT SIZE=3D2 FACE=3D"Arial">%MOUNT-F-MEDOFL, Medium is = offline</FONT> </P>  = <P><FONT SIZE=3D2 FACE=3D"Arial">Here is the error log</FONT>o </P>  : <P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;V A X / V M =: S&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYSTEM ERROR =G REPORT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; COMPILED&nbsp; =e 8-MAY-2000 15:54:58</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=II nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=aI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=,I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=vH nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PAGE&nbsp; =
 13.</FONT> </P>  # <P><FONT SIZE=3D2 FACE=3D"Courier =s, New">&nbsp;******************************* =$ ENTRY&nbsp;&nbsp;&nbsp;&nbsp; 493. =& *******************************</FONT>> <BR><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;ERROR SEQUENCE =I 1666.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=aI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=   nbsp;&nbsp;&nbsp;&nbsp; LOGGED =A ON:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SID 12000003</FONT>h? <BR><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;DATE/TIME&nbsp; =  8-MAY-2000 =I 15:53:59.68&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= 6 nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYS_TYPE 04140002</FONT>E <BR><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;SYSTEM UPTIME: 0 DAYS =A 00:05:48</FONT>N9 <BR><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;SCS NODE: =cI EARTH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=nI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=oI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=OC nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  VAX/VMS V6.2</FONT>0 </P>  A <P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;DEVICE ERROR&nbsp; = : KA46&nbsp; CPU FW REV# 3.&nbsp; CONSOLE FW REV# 1.4</FONT> </P>  E <P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;GENERIC DK SUB-SYSTEM, =T UNIT _EARTH$DKA500:</FONT> </P>  # <P><FONT SIZE=3D2 FACE=3D"Courier =/. New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HW =0 REVISION&nbsp;&nbsp;&nbsp;&nbsp; 30312E31</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=rI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=mI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=@- nbsp;&nbsp;&nbsp; HW REVISION =3D 1.10</FONT> $ <BR><FONT SIZE=3D2 FACE=3D"Courier =1 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ERROR =nH TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =	 05</FONT> $ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=nI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=VI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=e5 nbsp;&nbsp;&nbsp; EXTENDED SENSE DATA RECEIVED</FONT>n$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SCSI =I ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=0 p;&nbsp;&nbsp; 05</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=lI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=3' nbsp;&nbsp;&nbsp; SCSI ID =3D 5.</FONT>=$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SCSI =I LUN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=3 sp;&nbsp; 00</FONT>a$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=uI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&==( nbsp;&nbsp;&nbsp; SCSI LUN =3D 0.</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SCSI =D SUBLUN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =	 00</FONT>P$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=rI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=AI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=s+ nbsp;&nbsp;&nbsp; SCSI SUBLUN =3D 0.</FONT>3$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PORT =. STATUS&nbsp;&nbsp;&nbsp;&nbsp; 00000001</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=eI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=2I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=t< nbsp;&nbsp;&nbsp; %SYSTEM-S-NORMAL, NORMAL SUCCESSFUL</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=HI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=.I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=<) nbsp;&nbsp;&nbsp;&nbsp; COMPLETION</FONT>n$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SCSI == CMD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 007F001A</FONT>/$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=TI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=  nbsp;&nbsp;&nbsp; 00FF</FONT>I$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=NI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&==I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&==# nbsp;&nbsp;&nbsp; MODE SENSE</FONT>3$ <BR><FONT SIZE=3D2 FACE=3D"Courier =0 New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SCSI =D STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =	 02</FONT>.I <BR><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=NI bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=tI bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=4< bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CHECK = CONDITION</FONT> </P>  G <P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;EXTENDED SENSE DATA</FONT>= </P>  # <P><FONT SIZE=3D2 FACE=3D"Courier =3@ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EXTENDED SENSE&nbsp; = 00050070</FONT> $ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= C nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =- 0A000000</FONT>-$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=VC nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0 00000000</FONT>S$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=eC nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =e 00000020</FONT> $ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=x nbsp;&nbsp;&nbsp; 0000</FONT>"$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=tI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=e( nbsp;&nbsp;&nbsp; ILLEGAL REQUEST</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=nI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=l7 nbsp;&nbsp;&nbsp; INVALID COMMAND OPERATION CODE</FONT>W$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =eD UCB$B_ERTCNT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =	 00</FONT> $ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=oI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=GI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= - nbsp;&nbsp;&nbsp; 0. RETRIES REMAINING</FONT>p$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =eD UCB$B_ERTMAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =	 00</FONT>-$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=.I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=9I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=o- nbsp;&nbsp;&nbsp; 0. RETRIES ALLOWABLE</FONT>,$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =A3 ORB$L_OWNER&nbsp;&nbsp;&nbsp;&nbsp; 00010004</FONT>8$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=oI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=oI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=d, nbsp;&nbsp;&nbsp; OWNER UIC [001,004]</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 8 UCB$L_CHAR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1EC54008</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=iI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=cI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=M- nbsp;&nbsp;&nbsp; DIRECTORY STRUCTURED</FONT>$$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=RI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=*& nbsp;&nbsp;&nbsp; FILE ORIENTED</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=-I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= ! nbsp;&nbsp;&nbsp; SHARABLE</FONT>C$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=EI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=1I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= " nbsp;&nbsp;&nbsp; AVAILABLE</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=LI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= & nbsp;&nbsp;&nbsp; ERROR LOGGING</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=PI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= " nbsp;&nbsp;&nbsp; ALLOCATED</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=0I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=nI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=I8 nbsp;&nbsp;&nbsp; SOFTWARE &quot;WRITE LOCK&quot;</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= ) nbsp;&nbsp;&nbsp; CAPABLE OF INPUT</FONT>,$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= * nbsp;&nbsp;&nbsp; CAPABLE OF OUTPUT</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= & nbsp;&nbsp;&nbsp; RANDOM ACCESS</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0G UCB$W_STS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  0000</FONT>E </P> <BR> <BR>  : <P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;V A X / V M =: S&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SYSTEM ERROR =G REPORT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; COMPILED&nbsp; =N 8-MAY-2000 15:54:58</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=0I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=EI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=)H nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PAGE&nbsp; =
 14.</FONT> </P>  # <P><FONT SIZE=3D2 FACE=3D"Courier = + New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 3 UCB$L_OPCNT&nbsp;&nbsp;&nbsp;&nbsp; 00000007</FONT>)$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=1I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=-I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=e+ nbsp;&nbsp;&nbsp; 7. QIO'S THIS UNIT</FONT>9$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ="B UCB$W_ERRCNT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0007</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=xI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=VI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=N, nbsp;&nbsp;&nbsp; 7. ERRORS THIS UNIT</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =AB IRP$W_BCNT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0000</FONT>F$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&==I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=EI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=>1 nbsp;&nbsp;&nbsp; TRANSFER SIZE 0. BYTE(S)</FONT>T$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =ZB IRP$W_BOFF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0000</FONT>T$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=3I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= . nbsp;&nbsp;&nbsp; TRANSFER PAGE ALIGNED</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = = IRP$L_PID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00030039</FONT>S$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=EI nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=/I nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=T2 nbsp;&nbsp;&nbsp; REQUESTOR &quot;PID&quot;</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =+ New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 8 IRP$Q_IOSB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00000000</FONT>$ <BR><FONT SIZE=3D2 FACE=3D"Courier =I New">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=EC nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =&E 00000000&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IOSB, 0. BYTE(S) =n TRANSFERRED</FONT> </P>  # <P><FONT SIZE=3D2 FACE=3D"Courier =N8 New">ANALYZE/ERROR/FULL/SINCE/OUT=3DJVC_CDROM.TXT</FONT> </P> <BR>  7 <P><FONT SIZE=3D2 FACE=3D"Arial">My question is:</FONT>& </P>  F <P><FONT SIZE=3D2 FACE=3D"Arial">1) have anyone have any experiences =! with WRITE CDROM DRives ? </FONT>pG <BR><FONT SIZE=3D2 FACE=3D"Arial">2) What is going wrong by the mount =b command ? </FONT>& </P>  8 <P><FONT SIZE=3D2 FACE=3D"Arial">thanks for help.</FONT> </P>  G <P><FONT SIZE=3D2 FACE=3D"Arial">PS: sorry if some receives this post =<D as MIMED Format, but i only have MS OUTLOOK (set as text only) for = sending emails </FONT> </P>   </BODY>& </HTML>p) ------_=_NextPart_001_01BFB9AD.AA17ED1E--*   ------------------------------  # Date: Tue, 09 May 2000 12:47:44 GMT== From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)b' Subject: Re: cdrom writer drive problemp0 Message-ID: <009E9D1B.B4B2F21D@SendSpamHere.ORG>  | In article <99371BC88DB7D311B79300508B95647E03EAD4@uf22.uid.de>, "Manser, Nazim (EXT)" <nmanser@union-investment.de> writes:K >This message is in MIME format. Since your mail reader does not understandb= >this format, some or all of this message may not be legible.b   TURN OFF MIME!!!!&     >b( >------_=_NextPart_001_01BFB9AD.AA17ED1E >Content-Type: text/plain; >	charset="iso-8859-1" >  >Hi Fiolks,= >CM >I installed on my vax station 4000 model 60 a SCSI CDROM Writer DRive (Model2 >XR-W2022 from JVC)> >i am running openvms v6.2 >&- >The jumpers of the drive are set as follows:& >p" >Jumper 6 = OFF (Termination OFF) 6 >Jumper 5 = OFF (device type cdrom read , ON  = write) >Jumper 4 = ON   (Parity on) >Jumper 3 = ON   (SCSI Id 5) >Jumper 2 = OFF& >Jumper 1 = ON & >p! >the speed is 6X read , 2x Write.p > K >there is no jumper about the 512 Byte Block size, nor is it documented (inD+ >the manual ) how the block is interpreted.3 >b7 >at console level the drive was recognised as JVC R2626  >E1 >when i boot from dka500  (vms7.1 or V7.2 cdroms)N >_
 >>>> B dka500F >> >DKA500  ><
 >?06 HLT INSTA >PC = 00000B15	PSL=041F004 >b >>>> >& >at vms level  >W >$mount/over=id $1$dka500:# >%MOUNT-F-MEDOFL, Medium is offlineI >3 >Here is the error log  L I've tried MANY CD-R and CD-RW devices on VMS -- both VAX and Alpha.  While K you can use them to burn CDs, you'll be hard pressed to get VMS to use themb for CDrom reading devices.    I If you can't set the CD drive to 512 byte sectoring, I doubt that the VMS/I DKDRIVER will take too kindly to it even if the device attributes did not& confuse it.R   --N VAXman- OpenVMS APE certification number: AAA-0001           VAXman@TMESIS.COM  L GNU Freeware -- What does the GNU *really* stand for?  Garbage!  Not Usable!   ------------------------------   Date: 9 May 2000 12:41:25 GMTb2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)U Subject: Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thb5 Message-ID: <8f911l$m3$1@mailint03.im.hou.compaq.com>E  d In article <391773E1.285AFA79@worldnet.att.net>, Pat Jankowiak <vaxhackery@worldnet.att.net> writes:M :DFWDAYS, A Compaq Update Weekend...  The agenda includes sessions on Linux, NH :OpenVMS 7.3 Futures, Web-enabling OpenVMS Applications, Tru64 UNIX and 5 TruCluster V5 Updates, Fib- rechannel Technology, ...&  G   Um, I'm not sure I want to know about "fib rechannel" technology. :-)&  4   The (in)famous ZKO (Nashua NH) analog to this was:                 Digital Softwa               Reengineering=  H   This comment was spelled out in ASCII in the colors used for two rows I   of otherwise decorative vertical bars at the main entrance of the site.0  K   The DFWdays event two years ago was a blast, though one rather memorable bE   demonstration at that event certainly gave new meaning to the word pI   "stink". :-)  For details and background on that demonstration, please p@   see http://www.research.compaq.com/wrl/techreports/html/TN-13/  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  " Date: Tue, 9 May 2000 13:26:15 GMT0 From: "Terry C. Shannon" <shannon@world.std.com>U Subject: Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thb& Message-ID: <FuAnFI.KC4@world.std.com>  ? "Hoff Hoffman" <hoffman@xdelta.zko.dec.nospam> wrote in message / news:8f911l$m3$1@mailint03.im.hou.compaq.com...C >D@ > In article <391773E1.285AFA79@worldnet.att.net>, Pat Jankowiak% <vaxhackery@worldnet.att.net> writes:NG > :DFWDAYS, A Compaq Update Weekend...  The agenda includes sessions onb Linux,I > :OpenVMS 7.3 Futures, Web-enabling OpenVMS Applications, Tru64 UNIX andp7 > TruCluster V5 Updates, Fib- rechannel Technology, ...p >bI >   Um, I'm not sure I want to know about "fib rechannel" technology. :-)-  I Hmm. Fib rechannel... that must be a cable TV station that specializes in"' reruns of President Clinton's speeches.p >b6 >   The (in)famous ZKO (Nashua NH) analog to this was: >p >               Digital Softwa >               Reengineeringp >bI >   This comment was spelled out in ASCII in the colors used for two rowsOK >   of otherwise decorative vertical bars at the main entrance of the site.p  E Always wondered what cryptic message was contained in the "bar code."    >0L >   The DFWdays event two years ago was a blast, though one rather memorableF >   demonstration at that event certainly gave new meaning to the wordJ >   "stink". :-)  For details and background on that demonstration, pleaseB >   see http://www.research.compaq.com/wrl/techreports/html/TN-13/ >b  ? Rumour has it that this year's technology demo will eclipse the& Electro-Vlasic.&   ------------------------------  # Date: Tue, 09 May 2000 15:03:15 GMTp From: kparris@my-deja.combU Subject: Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4th=) Message-ID: <8f99b5$853$1@nnrp1.deja.com>   3   "Terry C. Shannon" <shannon@world.std.com> wrote:;G > Always wondered what cryptic message was contained in the "bar code.">  E In embarrassment at the word-wrap which resulted in the appearance ofsE the word "REENGINEERING", the message was changed so that at least as;- of the early '90s, when I was there, it read:n       CustomersWin       WhenWeDelivernG ----------------------------------------------------------------------- G Keith Parris|Integrity Computing,Inc.|parris@decuserve.decus.org-nospam"F VMS Consulting: Clusters, Perf., Alpha porting, Storage&I/O, Internals    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  " Date: Tue, 9 May 2000 15:49:34 GMT0 From: "Terry C. Shannon" <shannon@world.std.com>U Subject: Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thb& Message-ID: <FuAu2E.1uC@world.std.com>  J <kparris@my-deja.com> wrote in message news:8f99b5$853$1@nnrp1.deja.com...5 >   "Terry C. Shannon" <shannon@world.std.com> wrote:2I > > Always wondered what cryptic message was contained in the "bar code."b >&G > In embarrassment at the word-wrap which resulted in the appearance ofpG > the word "REENGINEERING", the message was changed so that at least as&/ > of the early '90s, when I was there, it read:b >       CustomersWin >       WhenWeDeliverb  5 T'is obvious that the incumbents do not read ASCII...b   ------------------------------  % Date: Tue, 09 May 2000 12:00:27 -0400b2 From: Michael Brodeur <Michael.Brodeur@compaq.com>U Subject: Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd, and 4thb& Message-ID: <3918361B.58F0@compaq.com>   kparris@my-deja.com wrote: > 5 >   "Terry C. Shannon" <shannon@world.std.com> wrote:EI > > Always wondered what cryptic message was contained in the "bar code."p > G > In embarrassment at the word-wrap which resulted in the appearance of&G > the word "REENGINEERING", the message was changed so that at least asp/ > of the early '90s, when I was there, it read:  >       CustomersWin >       WhenWeDeliverE  F It still says that.  Of course you have to be able to read 7-bit ASCII to confirm it. :);   -- Michael Brodeur; Compaq Computer CorporationT
 Nashua, NH   ------------------------------  % Date: Tue, 09 May 2000 07:04:06 -0400p+ From: "Main, Kerry" <Kerry.Main@compaq.com>p( Subject: RE: Console Manager ReplacementJ Message-ID: <910612C07BCAD1119AF40000F86AF0D80528428A@kaoexc4.kao.dec.com>   Jay,  I Most console manager products work on the basis of supporting any consoleFH that outputs ascii text - hence, the previous note about console manager working with Solaris.s  I The real issue is what do these console mgmt products support in terms ofuH message awareness ie. if a "-F-" type error happens, can the console pkgF escalate this via email, pager ect? These filter pkgs are OS specific.  E Here are a few alternative products as well (in no particular order):&  1 http://www.robomon.com/product_detail_robocen.htmE- http://www.tditx.com/tdicard/www/cwframe.html   http://www.ki.com/products/clim/, http://www.globalmt.com/products/polycenter/K http://www.cai.com/products/commandit.htm (Console Manager replacement fromb CA)b   Regards,  
 Kerry Main Senior Consultant,
 Compaq Canada& Professional Services& Voice : 613-592-4660 FAX   : 819-772-7036 Email : kerry.main@compaq.com&       -----Original Message-----1 From: Jay T.McCanta [mailto:jmccanta@immunex.com] " Sent: Monday, May 08, 2000 6:27 PM To: Info-VAX@Mvb.Saic.Comb$ Subject: Console Manager Replacement    D I am in charge of finding a replacement for Console Manager.  We hadD the Polycenter brand then the CA brand.  It works extremely well andD has no drawbacks, except that it runs on OpenVMS.   Ok, that's not aC drawback, but since there are only two of us here who can spell VMS&F and there are many more eunichs - oops- UNIX folks, I'm chartered with8 finding a replacement that runs on the Solaris flavor.     What are folks out there using?pE -===================================================================-&9 Jay McCanta              |  My opinions are barely my ownb; System Administrator     |  My employer doesn't necessarilyO' Immunex Corp.            |  share them.DE -===================================================================-&   ------------------------------  % Date: Tue, 09 May 2000 07:49:35 -0500&) From: "John E. Malmberg" <wb8tyw@qsl.net>p@ Subject: FAQ - How do I subscribe to the SAMBA-VMS mailing list?7 Message-ID: <146201bfb9b5$09abb3d0$020a0a0a@xile.realm>e  I To subscribe to the SAMBA-VMS mailing list e-mail listproc@samba.org withp  %  "subscribe samba-vms Your Full Name"p  9 in the message body.  Do not include the quotation marks.b  7 For additional information see http://lists.samba.org/.p   -JohnL wb8tyw@qsl.network  I A MIME is a terrible thing to waste.  Plain text only and no VCF cards tob mailing lists please.    ------------------------------  # Date: Tue, 09 May 2000 13:31:00 GMT& From: torlet@my-deja.com Subject: Internal date) Message-ID: <8f93uk$1il$1@nnrp1.deja.com>b   Hello,; I have a problem with fortran and the internal date in VMS.bG The internal date is coded in a quadword in VMS.  The quadword contains&0 the nuimber of 100nanoseconds since 17-nov-1858.E Knowing the days since that date, i would like to produce an internalpC date.  The problem in my version of fortran is that it doesn't know E integers coded on 64 bits, so i use two integers coded on 32 bits.  IbE thus have to stock my nanoseconds use a real coded on 64 bits and trypG to put that real number (that is an integer) in 2 integers.  I tried tobA use arithmetic functions (divide by 2**32 and use the integer anduC fractionnal parts) but one of the integer should be an unsigned one" then.&F I am looking for a bit of code to be able to transfer the value i have, in 100nanoseconds in my two 4 bytes integer.9 Any other help in that field would be greatly appreciatedb  E PS : i know that LIB$CVT_TO_INTERNAL_TIME exists i also know that the/E time should be less than 10000 days.  And we are 67000 days away fromb 17-nov-1858.    & Sent via Deja.com http://www.deja.com/ Before you buy.b   ------------------------------  % Date: Tue, 09 May 2000 09:01:05 -0500b" From: Earl Lakia <lakia@ipact.com> Subject: Re: Internal date( Message-ID: <39181A21.F615E5A@ipact.com>  6 If you are using FORTRAN on an ALPHA, then no problem, use the Integer*8 data type.  / On the VAX there are some extended instructionsb- (EMUL & EDIV)  instructions that can help youp6 (available through library routines).  You can also do9 some quad word bit shitfting to keep the precision.  Also 1 you can convert the word to floating point and do&? arithmatic (I wrote a Macro routine that did this).  Obviously,p you lose accuracy.  - If you use the EMUL and EDIV,  not all of theO arguments can be quad word.e   -earlV --
 Earl D. Lakiap0 Senior Staff Engineer         Web: www.ipact.com4 Snail Mail:                   Email: lakia@ipact.com
 IPACT Inc.1 260 S. Campbell St.           Phone: 219-464-7212I Valparaiso, IN 46383     torlet@my-deja.com wrote:p   > Hello,= > I have a problem with fortran and the internal date in VMS.pI > The internal date is coded in a quadword in VMS.  The quadword containsp2 > the nuimber of 100nanoseconds since 17-nov-1858.G > Knowing the days since that date, i would like to produce an internalbE > date.  The problem in my version of fortran is that it doesn't know)G > integers coded on 64 bits, so i use two integers coded on 32 bits.  I=G > thus have to stock my nanoseconds use a real coded on 64 bits and trybI > to put that real number (that is an integer) in 2 integers.  I tried to7C > use arithmetic functions (divide by 2**32 and use the integer andpE > fractionnal parts) but one of the integer should be an unsigned one& > then.pH > I am looking for a bit of code to be able to transfer the value i have. > in 100nanoseconds in my two 4 bytes integer.; > Any other help in that field would be greatly appreciatedE >2G > PS : i know that LIB$CVT_TO_INTERNAL_TIME exists i also know that theRG > time should be less than 10000 days.  And we are 67000 days away fromE > 17-nov-1858. >r( > Sent via Deja.com http://www.deja.com/ > Before you buy.p   ------------------------------   Date: 9 May 2000 14:27:51 GMTb2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Internal date6 Message-ID: <8f9797$3ab$1@mailint03.im.hou.compaq.com>  D In article <8f93uk$1il$1@nnrp1.deja.com>, torlet@my-deja.com writes:< :I have a problem with fortran and the internal date in VMS.  1   OpenVMS version and platform?  Fortran version?   H :The internal date is coded in a quadword in VMS.  The quadword contains1 :the nuimber of 100nanoseconds since 17-nov-1858.&  D   17-Nov-1858 being the OpenVMS system base date and the native timeD   storage format being centiseconds since the base date stored in a    quadword, of course.  F :Knowing the days since that date, i would like to produce an internal :date.    >   You have the results of lib$day, in other words, and want to<   convert this back to the native quadword format.  Correct?  = :The problem in my version of fortran is that it doesn't know&E :integers coded on 64 bits, so i use two integers coded on 32 bits.  b  3   Your own extended-precision math, in other words.&  E   There are a variety of RTL routines useful in the area of time and L?   time conversion, including lib$subx and lib$addx and friends.b  H :I thus have to stock my nanoseconds use a real coded on 64 bits and try> :to put that real number (that is an integer) in 2 integers.    J   I would tend to discourage the use of mixing floating point and integer J   data types for this -- stay with integer, if you can.   (Floating point H   is less than ideal for storage of both money and time -- unless you're*   a congress critter or an astronomer. :-)   :I tried toEB :use arithmetic functions (divide by 2**32 and use the integer andD :fractionnal parts) but one of the integer should be an unsigned one :then.G :I am looking for a bit of code to be able to transfer the value i have&- :in 100nanoseconds in my two 4 bytes integer.b  A   The use of pointers make this sort of access rather easier, but;@   things get rather more interesting as you are mixing floating    point and integer data types."  : :Any other help in that field would be greatly appreciated  E   lib$emul goes directly from the two longwords you have (the number OG   of days since the base date and the number of centiseconds in a day) pD   into a quadword integer product.  Which would seem to be the most    direct approach.  F :PS : i know that LIB$CVT_TO_INTERNAL_TIME exists i also know that theF :time should be less than 10000 days.  And we are 67000 days away from
 :17-nov-1858.:  H   And there was an error in the way that some folks that had managed theG   the day field in the time format conversions a couple of years back,  H   with various ensuing overflow problems.  Be careful not to exceed any +   documented time format conversion limits.4  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 09 May 2000 16:41:15 +0200s= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>e Subject: Re: Internal date) Message-ID: <3918238B.62E62B2A@gtech.com>t   Earl Lakia wrote:lK > > The internal date is coded in a quadword in VMS.  The quadword contains_4 > > the nuimber of 100nanoseconds since 17-nov-1858.I > > Knowing the days since that date, i would like to produce an internalxG > > date.  The problem in my version of fortran is that it doesn't knowJI > > integers coded on 64 bits, so i use two integers coded on 32 bits.  IfI > > thus have to stock my nanoseconds use a real coded on 64 bits and tryyK > > to put that real number (that is an integer) in 2 integers.  I tried to(E > > use arithmetic functions (divide by 2**32 and use the integer andaG > > fractionnal parts) but one of the integer should be an unsigned oner	 > > then.mJ > > I am looking for a bit of code to be able to transfer the value i have0 > > in 100nanoseconds in my two 4 bytes integer.= > > Any other help in that field would be greatly appreciateda  8 > If you are using FORTRAN on an ALPHA, then no problem, > use the Integer*8 data type. > 1 > On the VAX there are some extended instructions / > (EMUL & EDIV)  instructions that can help you 8 > (available through library routines).  You can also do; > some quad word bit shitfting to keep the precision.  Alsoa3 > you can convert the word to floating point and do A > arithmatic (I wrote a Macro routine that did this).  Obviously,I > you lose accuracy. > / > If you use the EMUL and EDIV,  not all of thee > arguments can be quad word.t  2 LIB$EMUL and LIB$EDIV works on both VAX and Alpha.  > Combined with LIB$ADDX and LIB$SUBX everything should be there in Fortran.*  ' But ofcourse learning Macro-32 is fun !-   Arne   ------------------------------  # Date: Tue, 09 May 2000 15:14:41 GMTz From: torlet@my-deja.com Subject: Re: Internal date) Message-ID: <8f9a0e$945$1@nnrp1.deja.com>   @ OK, let's go and try lib$emul that seams to be the best solution I have to supply :  C a longword integer multiplier : 24 *3600 * 100 00000 (to convert mye days in centiseconds)WD a longword integer multiplicand : the number of days since base date# addend : the number of centisecondsi* the result : the adress of my two longword   did i understand you correctly?     6 In article <8f9797$3ab$1@mailint03.im.hou.compaq.com>,&   hoffman@xdelta.zko.dec.nospam wrote: >iF > In article <8f93uk$1il$1@nnrp1.deja.com>, torlet@my-deja.com writes:> > :I have a problem with fortran and the internal date in VMS. >t3 >   OpenVMS version and platform?  Fortran version?r >eA > :The internal date is coded in a quadword in VMS.  The quadwordh contains3 > :the nuimber of 100nanoseconds since 17-nov-1858.m >bF >   17-Nov-1858 being the OpenVMS system base date and the native timeE >   storage format being centiseconds since the base date stored in a  >   quadword, of course. >sH > :Knowing the days since that date, i would like to produce an internal > :date. >n@ >   You have the results of lib$day, in other words, and want to> >   convert this back to the native quadword format.  Correct? >-? > :The problem in my version of fortran is that it doesn't knowrE > :integers coded on 64 bits, so i use two integers coded on 32 bits.F >Y5 >   Your own extended-precision math, in other words.s >-F >   There are a variety of RTL routines useful in the area of time andA >   time conversion, including lib$subx and lib$addx and friends.q >mF > :I thus have to stock my nanoseconds use a real coded on 64 bits and tryv> > :to put that real number (that is an integer) in 2 integers. >eC >   I would tend to discourage the use of mixing floating point andt integer-E >   data types for this -- stay with integer, if you can.   (Floating, pointeC >   is less than ideal for storage of both money and time -- unlessu you're, >   a congress critter or an astronomer. :-) >.
 > :I tried toaD > :use arithmetic functions (divide by 2**32 and use the integer andF > :fractionnal parts) but one of the integer should be an unsigned one > :then.D > :I am looking for a bit of code to be able to transfer the value i have/ > :in 100nanoseconds in my two 4 bytes integer.r >oC >   The use of pointers make this sort of access rather easier, buteA >   things get rather more interesting as you are mixing floatingd! >   point and integer data types.  >d< > :Any other help in that field would be greatly appreciated > F >   lib$emul goes directly from the two longwords you have (the numberC >   of days since the base date and the number of centiseconds in al day)E >   into a quadword integer product.  Which would seem to be the most  >   direct approach. > H > :PS : i know that LIB$CVT_TO_INTERNAL_TIME exists i also know that theH > :time should be less than 10000 days.  And we are 67000 days away from > :17-nov-1858.j >:F >   And there was an error in the way that some folks that had managed the=B >   the day field in the time format conversions a couple of years back,oE >   with various ensuing overflow problems.  Be careful not to exceedn anyd- >   documented time format conversion limits.  >dH >  --------------------------- pure personal opinion ------------------- --------1 >    Hoff (Stephen) Hoffman   OpenVMS Engineeringw hoffman#xdelta.zko.dec.com >  >u    & Sent via Deja.com http://www.deja.com/ Before you buy.-   ------------------------------  " Date: Tue, 9 May 2000 18:25:53 GMT From: briggs@eisner.decus.orgc Subject: Re: Internal date+ Message-ID: <KjMr8FUOlPTn@eisner.decus.org>/  D In article <8f9a0e$945$1@nnrp1.deja.com>, torlet@my-deja.com writes:B > OK, let's go and try lib$emul that seams to be the best solution > I have to supply : > E > a longword integer multiplier : 24 *3600 * 100 00000 (to convert myA > days in centiseconds)n  / 24 * 3600 * 10000000 is not a longword integer..  2 You need something that is less than four billion.  ? An easy trick is to multiply days by 24*36 using 32 bit integeroI arithmetic and then multiply that by 1,000,000,000 using 64 bit LIB$EMUL.d  C That should do a good job of keeping the two sides of your LIB$EMULu down to 32 bit quantities.  & 	John Briggs			briggs@eisner.decus.org   ------------------------------  % Date: Tue, 09 May 2000 11:17:39 +0111e6 From: Horst Drechsel <ai05@sternwarte.uni-erlangen.de>< Subject: LN15 printer setup: job remains in "starting" state= Message-ID: <009E9D30.A681BAFD.11@sternwarte.uni-erlangen.de>0  
    Hi all,  K    we recently purchased an LN15N-A (the one with a 10-Base-2 BNC ethernet ,K interface) and are trying to connect it to our local network consisting of cD an OpenVMS cluster with various AXP Alphastations under VMS 7.1-1H1;L DCPS version is 1.7. However, so far we haven't been able to get it running.  L    The printer was configured under TCP/IP, reacts on ping, and we are able I to telnet to the RP600 environment and use RP600 commands. We use telnet n@ port 3001 as recommended in the DCPS release notes for the LN15.  M    The DCPS V1.7 release notes say that for LN15 one should set the parameter   F               PERSONALITY  PS       in the printer console CONFIG menuH               NPAP MODE    OFF      in the printer console PARALLEL menuC               PORT 1       ENABLED  in the Ethernet card managementM               BITRONICSo  H    The first two are set accordingly, but we cannot locate the last one.> In the console mode PARALLEL menu, bidirectional mode is "ON".  I    The print queue is initialized within our DCPS$STARTUP.COM as follows:h  K ===========================================================================  $!% $ @sys$startup:dcps$execution_queue - C       cps15 -                           ! P1 - Execution queue nameeP       a400::"ip_rawtcp/192.44.90.51:3001" - ! P2 - Serial Device name or PrintS$L       dcps_lib -                        ! P3 - Logical name for library(ies)G       ""-                               ! P4 - Default queue parametersd@       "/SEPARATE=(NOFLAG,NOBURST,NOTRAILER)/SCHED=SIZE/FORM=PS -S                    /DEFAULT=(FORM=PS,NOFEED)" -     ! P5 - Default queue qualifiersp       ""-                               ! P6 - Communication speed(serial device      "/SPOOLED=(CPS15,SYS$SYSDEVICE)" - ! P7 - Device characteristics<       ""                                ! P8 - Verify on/off $! $! $ on error then continue) $ @sys$startup:dcps$generic_queue -     !aA         LPS_142F8C_ps -                 ! P1 - Generic queue name F         cps15 -                         ! P2 - Execution queue name(s)G         "data=post"-                    ! P3 - Default queue parametershG           "/prot=(S:M,O:D,G:R,W:SDMR)"- ! p4 - Default queue qualifierso<           ""                            ! P5 - Verify on/off $! $ on error then continue) $ @sys$startup:dcps$generic_queue -     !nI         LPS_142F8C_TEXT -                       ! P1 - Generic queue namenF         cps15 -                         ! P2 - Execution queue name(s)G         "data=ansi"-                    ! P3 - Default queue parameters=G           "/prot=(S:M,O:D,G:R,W:SDMR)"- ! p4 - Default queue qualifiers <           ""                            ! P5 - Verify on/off $!K ============================================================================  K    The queue names LPS_142f8c_ps and ..._TEXT contain the last 6 digits of 0L the ethernet hardware address of our LN15, as suggested in the installation  manual.H  C    Now, if we send some job to /queue=cps15 , we get the following:b  K ===========================================================================t- A400# print/notify/queue=cps15 vms$phases.dat   8 Job VMS$PHASES (queue CPS15, entry 346) started on CPS15  ' %DCPS-W-NOT_READY, Printer is not readynD -DCPS-I-JOB_ID, for job VMS$PHASES (queue CPS15, entry 346) on CPS15K ===========================================================================s   and show/queue cps15 gives:   K ===========================================================================o A400# show queue cps15 /fullB Printer queue CPS15, busy, on A400::"ip_rawtcp/192.44.90.51:3001", mounted form PStI   /BASE_PRIORITY=4 /DEFAULT=(FORM=PS) /NOENABLE_GENERIC /LIBRARY=DCPS_LIBuM   Lowercase /OWNER=[SYSTEM] /PROCESSOR=DCPS$SMB /PROTECTION=(S:M,O:D,G:R,W:S)n  4   Entry  Jobname         Username     Blocks  Status4   -----  -------         --------     ------  ------6     346  VMS$PHASES      SYSTEM            1  StartingC          Submitted  8-MAY-2000 18:50:08.87 /NOFLAG /FORM=PS /NOTIFYo          /PRIORITY=100N          File: _A400$DKA0:[VMS$COMMON.SYS$STARTUP]VMS$PHASES.DAT;1 (printing))              /NOFLAGK ===========================================================================r  G    but nothing comes out of the printer. The job remains in "Starting"   state.  F    We have also tried to set up the printer on a LAT port, as another K DEClaser 5100 is working here properly this way, but with the same negativeaK results. By the way, we have another network printer, an HP1600CM, which isnP set up exactly like we tried for the LN15, using ip_rawtcp with port 9100 under  DCPS, which is working fine.  J    Has anybody an idea where to look? What is the preferred way to set up F the printer: under LAT or TCPIP? Any suggestions or comments would be  highly appreciated.R      Thanks a lot in advance,3,                               Horst Drechsel   --M  ****************************************************************************e)   Horst Drechsel                          L   Dr. Remeis Observatory                 drechsel@sternwarte.uni-erlangen.deL   Astronomical Institute                             Phone: +49-951-95222-15L   University Erlangen-Nuernberg                        Fax: +49-951-95222-22*   Sternwartstr.7, D-96049 Bamberg, GermanyM  ****************************************************************************    ------------------------------  # Date: Tue, 09 May 2000 15:33:57 GMT + From: Paul Anderson <panderson@genicom.com> @ Subject: Re: LN15 printer setup: job remains in "starting" state@ Message-ID: <panderson-79E325.11335909052000@news.earthlink.net>  D In article <009E9D30.A681BAFD.11@sternwarte.uni-erlangen.de>, Horst 1 Drechsel <ai05@sternwarte.uni-erlangen.de> wrote:   F >    The DCPS V1.7 release notes say that for LN15 one should set the  >    parameter > H >               PERSONALITY  PS       in the printer console CONFIG menuJ >               NPAP MODE    OFF      in the printer console PARALLEL menuE >               PORT 1       ENABLED  in the Ethernet card management  >               BITRONICSo > J >    The first two are set accordingly, but we cannot locate the last one.  ? Log in to the printer's network card (via Telnet or LAT).  Get sH privileges with the SU command and then issue a DEFINE PORT 1 BITRONICS / ENABLED command.  Then power-cycle the printer.p  $ > Has anybody an idea where to look?  @ As the DCPS documentation says, the RapidPrint 600 Print Server @ Installation Guide has the details.  (The RapidPrint 600 is the ! printer's internal network card.)L  F > What is the preferred way to set up the printer: under LAT or TCPIP?  @ That's mostly personal preference.  Use what works best for you.   Paul   -- a"    Paul Anderson, DCPS Engineering"    GENICOM Corporation, Gardner MA   ------------------------------  % Date: Tue, 09 May 2000 10:46:14 +0200c= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> " Subject: Re: Marketing opportunity) Message-ID: <3917D056.3AB82890@gtech.com>j   "Joe H. Gallagher" wrote:i > Arne Vajhj wrote:& > > Digital know/knew about security !$ >   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > B > And how did this come about?  We'll the store I heard was that a? > VMS system manager on the VMS development team bet a language-E > devoloper (Jim Starkey, the author of DATATRIEVE) that he (Starkey)n( > couldn't break into to his VMS system. > H > Because the system manager used a VT125 terminal (with ReGIS graphics)G > Starkey mailed him a (ReGIS) macro which simulated a logout, login to E > capture the manager's password, and mailed it back to Starkey.  The  > systemJ > was conpromised in only a few hours.  The system manager was not amused;H > the MAIL routine was changed to display <ESC> as $ in the next release	 > of VMS.e   :-)    Good story.o   And it sounds plausible.  B Note that VT125 indicates it is a very old story. Not even Digital< got it rigth from day zero, but they certainly have improved continously.  ; MS is not only not improving, but actually making it worse.a   Arne   ------------------------------  % Date: Tue, 09 May 2000 10:44:13 +0200g= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>n" Subject: Re: Marketing opportunity) Message-ID: <3917CFDD.E3C6D121@gtech.com>   ( Andrew Harrison SUNUK Consultancy wrote: > Arne Vajhj wrote:K > > This virus/worm uses two features of Windows and Microsoft Mail that noiF > > other OS and email program on another OS to my best knowledge has: > >f; > > - all users has write access to all files on the systemd > >  > D > This may be true but it isn't really relevant, the worm could haveA > done its damage (clogging up email servers etc) without needing  > write access.t   I think it is relevant.a  D First, the damage was bigger on the clients because it had access to8 delete all the (graphics/video) files on the hard-drive.  D Second, it was more difficult to get rid of, because it infected the> registry, which in many ways is the heart of a Windows system.? That every user and program can modify the system configurationq
 is not smart.   K > > - the email-program run code when you click on an attachment containingt > > code > >I > M > Many email clients let people execute attachments by clicking them, VMSmaildM > may not but most MIME compliant email tools with a graphical user interface L > allow you to click on an attachment and launch it and some of these do run > on OpenVMS and UNIX.   ????  H There is a *HUGE* difference between viewing an attachment and executing code in it.t  D I have no problem if Outlook had oopened the VBS code in Notepad and+ showed it to the user. But it executed it !   H I have never seen a VMS mail program that would execute code in emails ! Can you name one ?  H Unix maybe !? I do not know all Unix flavours and all Unix mail programs !-   Arne   ------------------------------  % Date: Tue, 09 May 2000 14:16:32 +01003B From: Andrew Harrison SUNUK Consultancy <andrew.nospam@uk.sun.com>" Subject: Re: Marketing opportunity* Message-ID: <39180FB0.97F3B761@uk.sun.com>   Arne Vajhj wrote:  * > Andrew Harrison SUNUK Consultancy wrote: > > Arne Vajhj wrote:M > > > This virus/worm uses two features of Windows and Microsoft Mail that nodH > > > other OS and email program on another OS to my best knowledge has: > > >t= > > > - all users has write access to all files on the systemo > > >t > > F > > This may be true but it isn't really relevant, the worm could haveC > > done its damage (clogging up email servers etc) without needing  > > write access.r >i > I think it is relevant.  >eF > First, the damage was bigger on the clients because it had access to: > delete all the (graphics/video) files on the hard-drive. >e  ; Sure the worm deleted JPG's on local drives and you do neede write access to do this.  7 That however wasn't where the real damage was done. Ther< biggest impact that the Worm had was to clog up mail servers; stopping all mail services in some major corporations partsn6 of the US and UK governments for example. This did not6 require write access and in many ways was similar to a denial of service attack.a       >aF > Second, it was more difficult to get rid of, because it infected the@ > registry, which in many ways is the heart of a Windows system.A > That every user and program can modify the system configuration  > is not smart.  >$  > Sure but again thats not the point, it did infect the registry; but it could have been almost as effective without changing 
 the registry.l  ; The author of the Worm chose to delete JPG's and infect the-= registry which required write access to user files and systemeB files in the case of the registry but his/her Worm would have done< almost the same amount of damage without resorting to eitherA tactic.  Reading the users email directory does not require writee? access to the system but that all the writer actually needed to 3 cause the bulk of the damage inflicted by the worm.s   >bM > > > - the email-program run code when you click on an attachment containingw
 > > > code > > >  > >sO > > Many email clients let people execute attachments by clicking them, VMSmail O > > may not but most MIME compliant email tools with a graphical user interface.N > > allow you to click on an attachment and launch it and some of these do run > > on OpenVMS and UNIX. >n > ???? > J > There is a *HUGE* difference between viewing an attachment and executing
 > code in it.T >qF > I have no problem if Outlook had oopened the VBS code in Notepad and- > showed it to the user. But it executed it !b > J > I have never seen a VMS mail program that would execute code in emails ! > Can you name one ? >   ' Netscape mail client running on OpenVMSy   Regardst Andrew Harrisonk Enterprise IT Architect    ------------------------------   Date: 9 MAY 2000 13:57:32 GMTa4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)" Subject: Re: Marketing opportunity5 Message-ID: <9MAY00.13573292@thuria.waisman.wisc.edu>   G In a previous article, Nigel Arnot <sysmgr@maxwell.ph.kcl.ac.uk> wrote:   / ->... Our NT systems are very much multi-user. s  
 A minor nit:    G While we know what you mean by "multi-user", I believe the correct termeB should be "roving profiles".  We don't want to advance the popularD misconception that NT is a "multi-user" system. Multi-tasking - yes. Multi-user - no.   ------------------------------  $ Date: Tue, 9 May 2000 18:27:42 +10001 From: "Geoffrey Sinclair" <grsinclair@one.net.au>-8 Subject: Re: MOP Deamon for DECSERVER under MS-DOS/WINxx& Message-ID: <3917ca6a@pink.one.net.au>  " Terry Kennedy wrote in message ...+ >Hans Hamakers <hamakers@pobox.com> writes:rD >> Does anyone now if there is a possibility to load DECSERVERs from  >> MS-DOS/WINxx in stead of VMS? >rB >  You could look at: ftp://ftp.stacken.kth.se/pub/OS/NetBSD/mopd/1 >where there are C sources for a Unix MOP loader.d >o. > Terry Kennedy             http://www.tmk.com6 >        terry@tmk.com             Jersey City, NJ USA  4 When we bought our DECserver 90's in early 1999 they5 came with a CD with a MOP loader for win 95 and maybei> NT as well.  It seems to be a free utility, check with Compaq.   Geoffrey Sinclairl   ------------------------------  % Date: Tue, 09 May 2000 11:17:16 -0400 1 From: "Mark D. Jilson" <jilly@clarityconnect.com>h8 Subject: Re: MOP Deamon for DECSERVER under MS-DOS/WINxx2 Message-ID: <39182BFC.6A4CE065@clarityconnect.com>  C What kind of DECSERVERs?  A number of them support being loaded via_F BOOTP so getting them booted w/o VMS can be done.  My sources say thatD Pathworks used to have a PC floppy boot support for some DECSERVERs.   Hans Hamakers wrote: >  > Hi,a > C > Does anyone now if there is a possibility to load DECSERVERs fromo > MS-DOS/WINxx in stead of VMS?s >  > hamakers@pobox.com   -- gD Jilly	- Working from Home in the Chemung River Valley - Lockwood, NY0 	- jilly@clarityconnect.com			- Brett Bodine fan. 	- Mark.Jilson@Compaq.com			- since 1975 or so, 	- http://www.jilly.baka.com               -   ------------------------------  " Date: Tue, 9 May 2000 14:02:44 GMT1 From: schreiber@eisner.decus.org (Jeff Schreiber)-! Subject: RE: Mozilla M15's out... + Message-ID: <xGyw5AAf2Ech@eisner.decus.org>r  C On Sat, 22 Apr 2000, Hunter Goatley (goathunter@process.com) wrote:UO >On Fri, 21 Apr 2000 15:44:18 -0500, Mike Drabicky <drabicky#dallas.net> wrote:eL >>On Wed, 19 Apr 2000 10:47:11 -0600, Dan O'Reilly <dano@process.com> wrote: >>> N >>>Be advised - I haven't gotten it to run worth a damn on Multinet (although,Q >>>i'm not sure that's got anything to do with it).  I can send/receive mail thrudR >>>it, but it won't load any web pages.  It's also pretty slow, but it is at least >>>much more stable. >>H >>Ditto that. Multinet V4.2a on OpenVMS V7.2-1. M14 at least worked; M15B >>doesn't load any content to any pages. Sure makes browsing fast! >>$ >We're looking into this problem.... >y  :     This problem is now corrected with UCXDRIVER-120_A042.       The ReadMe is available:J http://www.multinet.process.com/scripts/eco/eco_tlb.com?UCXDRIVER-120_A042       The ECO itself:yI ftp://ftp.multinet.process.com/patches/multinet042/ucxdriver-120_a042.zip-  )                                     -Jeff1   --1 Jeff Schreiber,            Process Software Corp.o1 schreiber@mx.process.com   http://www.process.com +      TCPware & MultiNet: Stronger than Ever    ------------------------------  # Date: Tue, 09 May 2000 12:35:28 GMTv From: awrycroft0001@my-deja.comn+ Subject: ODBC Drivers for OpenVMS RMS filesS) Message-ID: <8f90me$u2g$1@nnrp1.deja.com>    Hi,g  1 The Visual Basic documentation makes reference to - the ODBC drivers to access OpenVMS RMS files.r) Does anybody know where I can find them ?o   Thanks Andrew Rycroft    & Sent via Deja.com http://www.deja.com/ Before you buy.c   ------------------------------  % Date: Tue, 09 May 2000 15:11:46 +0200l* From: Jimmi Aakjr <aakjaer@post7.tele.dk>/ Subject: Re: ODBC Drivers for OpenVMS RMS filese8 Message-ID: <3a3ghs4nhnla28kt4vf19ig79sf53dtfat@4ax.com>  B On Tue, 09 May 2000 12:35:28 GMT, awrycroft0001@my-deja.com wrote:   Tryt  2 http://www.solutionsiq.com/products/CONNX-rms.html  1 http://www.easysoft.co.uk/products/rms/main.phtml   A http://www.isgsoft.com/products/Navigator/components/datasources/      Jimmil   >Hi, >t2 >The Visual Basic documentation makes reference to. >the ODBC drivers to access OpenVMS RMS files.* >Does anybody know where I can find them ? >  >Thankso >Andrew Rycroftn >a >h' >Sent via Deja.com http://www.deja.com/S >Before you buy.   ------------------------------  % Date: Tue, 09 May 2000 08:51:23 -0500g" From: Earl Lakia <lakia@ipact.com>/ Subject: Re: ODBC Drivers for OpenVMS RMS filesd) Message-ID: <391817DB.D71659FC@ipact.com>   5 One of my customers purchased Easysoft for a project.c7 We  found that the  Easysoft product works rather well. 5 We created a bunch of reports using Microsoft Access.a  3 My customer also purchased a product "DrDeeBe" thate7 is a skelton that servers ODBC to clients.  The DrDeeBe 4 product was designed for UNIX, but we migrated it to VMS without too much effort.6 We serve process variables from RMS files that contain9 process data (e.g., process variables, such as flow ratesr9 that are archived every second) to Microsoft applicationsf, such as Excel and Access.  Actually any ODBC5 compliant client.  The DrDeeBe server actually servede/ keyed RMS files as well (the data dictionary ife. you will of how the data was stored within the process data files).  1 We also used Access to join data from the DrDeeBeo server and the Easysoft.  7 Biggest problem I have with Easysoft is their licensingi2 method.  Their license expires every year.  In the, process control environment, where you don't6 necessarly upgrade each year, the license expires, you. have to call the company.   A real pain in the butt.d  - Handling of record unions and datetime stamps   are things you need to consider.   --
 Earl D. Lakiah0 Senior Staff Engineer         Web: www.ipact.com4 Snail Mail:                   Email: lakia@ipact.com
 IPACT Inc.1 260 S. Campbell St.           Phone: 219-464-7212e Valparaiso, IN 46383      awrycroft0001@my-deja.com wrote:   > Hi,a >e3 > The Visual Basic documentation makes reference tom/ > the ODBC drivers to access OpenVMS RMS files.t+ > Does anybody know where I can find them ?r >f > Thanks > Andrew Rycroft >y( > Sent via Deja.com http://www.deja.com/ > Before you buy.n   ------------------------------  % Date: Tue, 09 May 2000 15:58:45 +0100i- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>e/ Subject: Re: ODBC Drivers for OpenVMS RMS fileso) Message-ID: <391827A5.E9BFDC56@bbc.co.uk>    Earl Lakia wrote:r  : >  Biggest problem I have with Easysoft is their licensing4 > method.  Their license expires every year.  In the. > process control environment, where you don't8 > necessarly upgrade each year, the license expires, you0 > have to call the company.   A real pain in the > butt.h >r  @ So, remember to install the updated licences before the old ones< expire. Tim, who's got used to doing that every october now.   --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those ofo MedAS or the BBC.    ------------------------------  $ Date: Tue, 9 May 2000 09:44:55 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>t* Subject: Re: Pitch of the Margin bell Beep+ Message-ID: <8f94nl$eej$1@lead.zk3.dec.com>e  I At some point in time, the fixes to allow pitch/duration to work with the I "normal" controls made it out... this may be what you are seeing.  In any  case...   J Go into the STYLE manager, and select BEEP.  If the volume control changesJ the pitch... then you have the old stuff (in which case the "click" volumeG under keyboard will change the duration -- there is no key click for PC L keyboards).  Otherwise, the volume will only turn it on/off (the system bell9 has no volume control), and pitch and duration will work.t   _Fredm  % Robert Deininger wrote in message ... K >On Thu, May 4, 2000 11:20 AM, Menno van Eck <m.van.eck@philips.com> wrote:tA >>Installing VMS 7.1-2 on an AS800/500 I noticed the pitch of therL >>margin/warning bell for Motif X-applications on the local system was lowerD >>than I used to. I know the pitch is influenced by which version of >>SYS$IKBDRIVER.EXE is used. >>I >>Does anyone have a clue how to change (higher) the pitch or maybe lowern >theJ >>volume of this bell. I get remarks of the users of the systems about it? >1L >Same thing happened to me last night when I installed 7.1-2.  I didn't find* >(or really even look for) a solution yet. >w >  >--------------------------- >Robert Deininger> >rdeininger@mindspring.com >  >  >Y   ------------------------------   Date: 9 May 2000 11:50:50 -0400e4 From: "Robert Deininger" <rdeininger@mindspring.com>* Subject: Re: Pitch of the Margin bell Beep+ Message-ID: <B53DAC1C-205B8A@165.247.26.71>y  J On Tue, May 9, 2000 9:44 AM, Fred Kleinsorge <kleinsorge@star.zko.dec.com> wrote:J >At some point in time, the fixes to allow pitch/duration to work with theJ >"normal" controls made it out... this may be what you are seeing.  In any >case... >uK >Go into the STYLE manager, and select BEEP.  If the volume control changescK >the pitch... then you have the old stuff (in which case the "click" volume3H >under keyboard will change the duration -- there is no key click for PCH >keyboards).  Otherwise, the volume will only turn it on/off (the system bell: >has no volume control), and pitch and duration will work.  @ Thanks.  Found it.  And I'll stop trying to adjust the volume...     ---------------------------e Robert Deininger rdeininger@mindspring.com    ------------------------------  " Date: Tue, 9 May 2000 14:25:45 GMT9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)d@ Subject: Re: Remote unix queues to VMS- HELP with RMS breaking..+ Message-ID: <kT8iiDphqtyt@eisner.decus.org>:  ^ In article <2000May8.190003@axp1.cpg.mcw.edu>, brodie@axp1.cpg.mcw.edu (Kent C Brodie) writes:D > Help?   This has been bugging me for years--  I have a remote unixD > system that needs to print to VMS queues.   Unfortunately, the VMS> > system has a bad habit of letting RMS limits get in the way, > specifically:  > 6 >   Entry  Jobname         Username     Blocks  Status6 >   -----  -------         --------     ------  ------A >    1154  standard input  TPOQUETT       3619  Retained on errore* >        %PSM-E-READERR, error reading !AS@ >        -RMS-W-RTB, !UL byte record too large for user's buffer1 >        -SYSTEM-I-NOMSG, Message number 00008E13 ? >          Completed  8-MAY-2000 18:42:59.74 on queue SYS$COPS6> > < > ==========================================================A > The unix system can, of course, go DIRECTLY to the printer, butl6 > that is not a full solution for operational reasons. > B > Does anyone know how I can tweak this so that files don't "bust" > the VMS rms environment?  > You did not outline how you are transferring the files to VMS,< but it seems likely you are doing so with "records" that are= too long.  Presuming this is normal ASCII output (rather than6? Postscript), you should make sure that each "line" you transfere; is a separate "record" in RMS.  If you are using unix-stylen: utilities to transfer the file, those utilities might have such a control on them.n  = The limit you are seeing, by the way, is not the absolute RMS;< limit, but the print symbiont limit on the longest "line" it? might reasonably receive, based on what the printer can handle.e   ------------------------------  / Date: Tue, 09 May 2000 08:48:48 +0200 (MET DST)a& From: Rudolf Wingert <win@fom.fgan.de># Subject: S80 competitor of E10000?!t/ Message-ID: <200005090548.HAA32169@fom.fgan.de>a   Hello,  I today I red that, as the Information Week and GigaGroup say, the S80 willpI be the competitor of the E10000. IBM is happy, that they did sold the S80tF three times (720) of Sun's E10000 (255). I am hoping that the WildfireE soon and will be a competitor of both and well sold better then both.e   Regards Rudolf Wingert   ------------------------------  " Date: Tue, 9 May 2000 14:37:26 GMT9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)h' Subject: Re: S80 competitor of E10000?!=+ Message-ID: <MaPQyQVf5Dlk@eisner.decus.org>=  X In article <200005090548.HAA32169@fom.fgan.de>, Rudolf Wingert <win@fom.fgan.de> writes: > Hello, > K > today I red that, as the Information Week and GigaGroup say, the S80 will1K > be the competitor of the E10000. IBM is happy, that they did sold the S80 H > three times (720) of Sun's E10000 (255). I am hoping that the WildfireG > soon and will be a competitor of both and well sold better then both.T  8 Well Apple has sold more iMacs than Sun has sold E10000.. At a 1:1000 price to price ratio, they should.  E For some situations the Compaq ES40 might be the proper competitor tosF the IBM S80, rather than Wildfire.  On the other hand, based on what IF saw at the San Diego DECUS Symposium, it will be possible to configureB a Wildfire so that it is _less_ powerful than a fully loaded ES40.  C I don't necessarily trust Information Week and GigaGroup about whatcB will be the competitor to anything else.  Andrew Harrison keeps upB a litany regarding the importance of CPU hot-swap.  If Compaq wereA to release a DS10H with CPU hot-swap, that would not be likely to4) compete with E10000 or Compaq's own DS40.    ------------------------------  " Date: Tue, 9 May 2000 13:29:40 GMT0 From: "Terry C. Shannon" <shannon@world.std.com>' Subject: Re: S80 competitor of E10000?! & Message-ID: <FuAnL8.M6B@world.std.com>  F "Larry Kilgallen" <Kilgallen@eisner.decus.org.nospam> wrote in message% news:MaPQyQVf5Dlk@eisner.decus.org...D@ > In article <200005090548.HAA32169@fom.fgan.de>, Rudolf Wingert <win@fom.fgan.de> writes:i
 > > Hello, > >"H > > today I red that, as the Information Week and GigaGroup say, the S80 willI > > be the competitor of the E10000. IBM is happy, that they did sold theS S808J > > three times (720) of Sun's E10000 (255). I am hoping that the WildfireI > > soon and will be a competitor of both and well sold better then both.w >e: > Well Apple has sold more iMacs than Sun has sold E10000.0 > At a 1:1000 price to price ratio, they should. >=G > For some situations the Compaq ES40 might be the proper competitor to H > the IBM S80, rather than Wildfire.  On the other hand, based on what IH > saw at the San Diego DECUS Symposium, it will be possible to configureD > a Wildfire so that it is _less_ powerful than a fully loaded ES40.  I Yup. Anything from a GS80 to a GS320 can be configured with just one CPU.=9 Not really practical but it keeps the "entry price" down.o   ------------------------------  " Date: Tue, 9 May 2000 15:14:10 GMT- From: young_r@eisner.decus.org (Robert Young) ' Subject: Re: S80 competitor of E10000?!A+ Message-ID: <yto06cKvBzam@eisner.decus.org>O  g In article <MaPQyQVf5Dlk@eisner.decus.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:lZ > In article <200005090548.HAA32169@fom.fgan.de>, Rudolf Wingert <win@fom.fgan.de> writes:	 >> Hello,  >>  L >> today I red that, as the Information Week and GigaGroup say, the S80 willL >> be the competitor of the E10000. IBM is happy, that they did sold the S80I >> three times (720) of Sun's E10000 (255). I am hoping that the Wildfire=H >> soon and will be a competitor of both and well sold better then both. > : > Well Apple has sold more iMacs than Sun has sold E10000.0 > At a 1:1000 price to price ratio, they should. > G > For some situations the Compaq ES40 might be the proper competitor totH > the IBM S80, rather than Wildfire.  On the other hand, based on what IH > saw at the San Diego DECUS Symposium, it will be possible to configureD > a Wildfire so that it is _less_ powerful than a fully loaded ES40. > E > I don't necessarily trust Information Week and GigaGroup about what D > will be the competitor to anything else.  Andrew Harrison keeps upD > a litany regarding the importance of CPU hot-swap.  If Compaq wereC > to release a DS10H with CPU hot-swap, that would not be likely to*+ > compete with E10000 or Compaq's own DS40.e  % 	As a countervaling point to offer...  	 H 	Much can be said about marchitecture.  Intel has frozen CPU developmentA 	teams in their tracks by touting futures, Microsoft has likewise-? 	frozen software development with futures...  a lot can be said C 	about being the "fastest" (regardless how you measure it and sadly B 	regardless how you spin it).  That is why it is important to haveA 	very good tpmC's to offer up when making the Big Dog sales calls0? 	(i.e. multi-million dollar RFP).   At the very least, being atu= 	the top helps to get your name on the short list and that is D 	VERY IMPORTANT.  Otherwise, you aren't even invited to participate.? 	(Danger: assumption is you are interested in a high performing ? 	solution to meet your needs and aren't locked in to a vendor.)D  B 	Since it is apparent Sarenspaghetti isn't out until 2001, perhapsA 	Wildfire stays on top through year-end.  Surely copper SOI 21264nA 	shows up year-end or early next year and gives a nice speed bumpt$ 	to Wildfire to further their cause.   				Rob    ------------------------------  % Date: Tue, 09 May 2000 15:48:50 +0100   From: steven.reece@quintiles.com' Subject: Re: S80 competitor of E10000?!n> Message-ID: <802568DA.0051A2B3.00@qedilc01.qedi.quintiles.com>  N Larry Kilgallen (kilgallen at eisner dot decus dot org dot no dot spam) wrote:  < >>>If Compaq were to release a DS10H with CPU hot-swap, thatC would not be likely to compete with E10000 or Compaq's own DS40.<<<P  O Interesting concept though!  A uniprocessor machine with a hot swap cpu.  Shove N everything out of cache and quiesce the cpu.  Take out one processor and shove: in a new one with no loss of context.  Coolllllll!!!!!!!!!  < It *might* even quiesce a Sunny one for a minute or two.....   Steve.   ------------------------------  % Date: Tue, 09 May 2000 10:47:09 +0200-= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>  Subject: Re: SCSI device names) Message-ID: <3917D08C.A7F19F05@gtech.com>e   FAZEKAS Mihaly wrote:-$ > I have a new SCSI controller card.H > (i'm buy a Cadmus 9600 Terminal server, and this terminal server has a
 > SCSI card.) ! > This SCSI card put into my VAX.^ > 4 > What is the SCSI device name(s)? (dka*, dsa*, or?)  & DKA is the first SCSI disk controller.   Arne   ------------------------------   Date: 09 May 2000 16:50:54 GMT% From: barrys2552@aol.com (Barrys2552)o Subject: Seagate ST19171NS: Message-ID: <20000509125054.22329.00004156@ng-md1.aol.com>  L I.m having trouble getting a seagate disk drive to work on a 3100/95 runningN VMS 7.1. The drive is seen by the console, and vms sees it after it boots. ButO when I try to init it I get Medium is offline. I double checked for patches andwK didn't find anything. Do I need to upgrade to 7.2? Is there a configuration!  issue with jumpers on the drive?  = The drive is a 9.1GB Narrow SCSI drive Seagate model ST19171N1  
 Barry Streetsh Echo Management Group  Barrys@echoman.com   ------------------------------   Date: 8 May 2000 19:46:37 GMTC, From: Mike Lynch <lynch@puma.middlebury.edu> Subject: Set host/mopv3 Message-ID: <8f75it$k3a$1@pampascat.middlebury.edu>   8 Configuration: AlphaServer 400 4/233, OpenVMS AXP V7.1-2  $ In the past I have used the command:   set host/mop <servername>a  E to connect to a terminal server.  Once connected, one can modify portaH speeds, disconnect users, give ports a dedicated service, etc.  I swear F I found this command in the help at some point, but it does not appear there now.    F After using this command several times last Friday morning, the system# began to issue the following error:o  ) %CCR-F-NORESOURCE, insufficient resourcesh   Help /message tells me:e  > %MSGHLP-F-NOTFOUND, message not found in Help Message database  I The documentation does not indicate what the CCR facility is.  Once I get E this message, I cannot connect to any other terminal server either.  M  G Did I dream up this command?  What resources are insufficient? Is thereeI another way to connect to a terminal server?  The server is a Xyplex, andpE I need to logout/disconnect a couple of ports, and configure a coupleo others.c   Thanks,.  
 Mike Lynch Systems Librarianp Middlebury College   ------------------------------   Date: 9 May 2000 13:09:51 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Set host/mop 6 Message-ID: <8f92mv$1cg$1@mailint03.im.hou.compaq.com>  b In article <8f75it$k3a$1@pampascat.middlebury.edu>, Mike Lynch <lynch@puma.middlebury.edu> writes:9 :Configuration: AlphaServer 400 4/233, OpenVMS AXP V7.1-2g  G   I will assume you are using DECnet MOP, and not LANCP MOP.  As such,  G   which DECnet Phase?   (I'll assume DECnet-Plus, based on the details m   of the question.)t   :set host/mop <servername> ..* :%CCR-F-NORESOURCE, insufficient resources  >   There are sometimes other messages included with this error.  > :The documentation does not indicate what the CCR facility is.      CCR: Console Carrier Requestor  ? :Did I dream up this command?  What resources are insufficient?o  D   The insufficient resources error can arise because the address is G   in use (eg: somebody else is connected), because DECnet-Plus NET$MOP iB   process has run out of virtual address space (check the log fileF   SYS$MANAGER:NET$MOP_OUTPUT.LOG), and if no LAN was specified in the    DECnet-Plus database.s  E   You might restart MOP, either by bouncing the circuit or via a morenF   brute-force approach (eg: STOP/ID of NET$MOP) followed by a restart.A   (Use "@sys$system:startup network mop" to restart NET$MOP.)  Ora   bounce DECnet-Plus.n  D   Do you have any DECnet-related ECO kits installed?  (If not, checkA   for any DECnet-Plus ECO kits available.  If found, apply them.)e  D   If the problem persists, please directly contact the folks at the !   Compaq Customer Support Center.a   	--s  ;   (ps: We dropped "AXP" a while back, in favor of "Alpha".)   N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 09 May 2000 09:35:05 -0300a1 From: "Boyle, Darren" <boyledj@bankofbermuda.com>n Subject: RE: Set host/moptK Message-ID: <F150836441C5D311A11700508B6FF01A98341A@bdant024.bda.bobda.com>f  C No you didn't dream it up you were just looking in the wrong place.o  ( PLAXP2_Darren1> mc ncl help connect node   CONNECT-     node_(OpenVMS)    G        The Phase IV NCP CONNECT NODE command has no Phase V equivalent.cG        Instead, use the following command to access the console carrier6"        function of MOP on Phase V:          $SET HOST/MOP  B        For further information about the Console Carrier, refer to;        the DECnet-Plus Network Management book, Appendix I.u     Topic?  Exit  K Unfortunately I can't assist with the resource in which you are lacking.  I L would imagine the CCR is as mentioned above "Console Carrier".  You got yourK error message file from SYS$MESSAGE:NETWRKMSG.EXE.  It may be worth looking 9 through the SYS$HELP:NET$MGMT_HELP.HLB help library file.P - Darren   > ----------3 > From: 	Mike Lynch[SMTP:lynch@puma.middlebury.edu]b% > Sent: 	Monday, May 08, 2000 4:46 PMo > To: 	Info-VAX@Mvb.Saic.Com > Subject: 	Set host/mop > : > Configuration: AlphaServer 400 4/233, OpenVMS AXP V7.1-2 > & > In the past I have used the command: >  > set host/mop <servername>e > G > to connect to a terminal server.  Once connected, one can modify portgJ > speeds, disconnect users, give ports a dedicated service, etc.  I swear H > I found this command in the help at some point, but it does not appear > there now.   > H > After using this command several times last Friday morning, the system% > began to issue the following error:h > + > %CCR-F-NORESOURCE, insufficient resourcesc >  > Help /message tells me:e > @ > %MSGHLP-F-NOTFOUND, message not found in Help Message database > K > The documentation does not indicate what the CCR facility is.  Once I getvG > this message, I cannot connect to any other terminal server either.  i > I > Did I dream up this command?  What resources are insufficient? Is thereaK > another way to connect to a terminal server?  The server is a Xyplex, andtG > I need to logout/disconnect a couple of ports, and configure a coupleo	 > others.w > 	 > Thanks,n >  > Mike Lynch > Systems Librarianc > Middlebury College >     F **********************************************************************C This message and any files transmitted with it are confidential andmJ may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom theysL are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copyingn of this message is prohibited.   Bank of Bermuda F **********************************************************************   ------------------------------  % Date: Tue, 09 May 2000 15:43:40 +0100p  From: steven.reece@quintiles.com Subject: Re: Set host/mopt> Message-ID: <802568DA.005129F1.00@qedilc01.qedi.quintiles.com>   Hoff commented:sH >>>  You might restart MOP, either by bouncing the circuit or via a moreF   brute-force approach (eg: STOP/ID of NET$MOP) followed by a restart.A   (Use "@sys$system:startup network mop" to restart NET$MOP.)  Orr   bounce DECnet-Plus.<<<  J Can you bounce DECnet-Plus?  I didn't think it was as, erm, "adaptable" asL DECnet Classic.  As in "you want to restart DECnet?  You have to restart theD machine".  MC NCP SET EXEC/STATE=OFF not spoken here kinda thing....   Steve.   ------------------------------  % Date: Tue, 09 May 2000 11:41:55 -0400-  From: norm.raphael@jamesbury.comY Subject: Re: Split line (Off-Topic)(was: Charlie Matco on DFWDAYS,A	Compaq Update Weekendt4 Message-ID: <C22568DA.005661B9.00@jklh21.valmet.com>  7 hoffman@xdelta.zko.dec.nospam on 05/09/2000 08:41:25 AMa  / Please respond to hoffman@xdelta.zko.dec.nospamu   To:   Info-VAX@mvb.saic.comp cc:hN Subject:  Re: Charlie Matco on DFWDAYS, A Compaq Update Weekend June 2nd, 3rd,
       and 4thu        ? /In article <391773E1.285AFA79@worldnet.att.net>, Pat Jankowiaki% <vaxhackery@worldnet.att.net> writes: M /:DFWDAYS, A Compaq Update Weekend...  The agenda includes sessions on Linux, H /:OpenVMS 7.3 Futures, Web-enabling OpenVMS Applications, Tru64 UNIX and6 /TruCluster V5 Updates, Fib- rechannel Technology, ... /rH /  Um, I'm not sure I want to know about "fib rechannel" technology. :-) /r5 /  The (in)famous ZKO (Nashua NH) analog to this was:  /  /              Digital Softwa2 /              Reengineering / H /  This comment was spelled out in ASCII in the colors used for two rowsJ /  of otherwise decorative vertical bars at the main entrance of the site. /t  H Off topic, but my experience with this phenominon was a magazine label I. encountered in a medical waiting room, to wit:   JOHN DOE THE RAPIST    K /  The DFWdays event two years ago was a blast, though one rather memorable E /  demonstration at that event certainly gave new meaning to the worduI /  "stink". :-)  For details and background on that demonstration, pleasetA /  see http://www.research.compaq.com/wrl/techreports/html/TN-13/l / O / --------------------------- pure personal opinion ---------------------------mM /   Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.comt /e   ------------------------------  % Date: Tue, 09 May 2000 14:07:56 +0200a  From: marc.hinderickx@banksys.be Subject: tape label in EBCDIC-; Message-ID: <FBD86325E818D311ADC10008C75B7A6301695238@AZHA>m   Hi,f; 	I have to write a tape in EBCDIC format. This tape must be?! initialised (not a foreign tape) 19 Do you have an example (in COBOL if possible) to help me?r   Kind regards   Marc HINDERICKXS Systems Manager - Operations Banksys0   ------------------------------  % Date: Tue, 09 May 2000 10:19:25 -04000" From: Dan Sugalski <dan@sidhe.org>& Subject: Re: the latest billybox virus8 Message-ID: <4.3.1.0.20000509101637.0240dac0@24.8.96.48>  0 At 12:44 AM 5/8/00 +0000, Larry Kilgallen wrote:4 >But I think concern may be less and less necessary,3 >as the fascination with all things Microsoft seemse2 >to be in retreat at DEQ.  The new latest thing is2 >supposed to be Apache, which is approximately the6 >antithesis of Microsoft.  Of course eternal vigilance8 >is the price of liberty, as there might be shortcomings >in the Apache code, as well.   D While the Apache code's not perfect, the Apache folks seem to place F correctness over speed, which is a pleasant change from a lot of Unix L things. It's one of the reasons that Apache doesn't do quite as well in the L benchmarks as some other servers. OTOH, it does *not* fall down and go boom ! when placed under lots of stress.    					Dan  I --------------------------------------"it's like this"-------------------e2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenn;                                       teddy bears get drunk    ------------------------------  " Date: Tue, 9 May 2000 14:30:04 GMT9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)r( Subject: Re: Unsolicited OpenVMS/NT book+ Message-ID: <e1$MFi54aojx@eisner.decus.org>e  \ In article <882568DA.0003B16A.00@WHDOM99.HEALTHNET.COM>, Shane.F.Smith@healthnet.com writes:  I > I just received my latest unexpected package from Rich Marcello: a free3D > copy of the "OpenVMS and Windows NT Integration For Dummies" book. > ' > Am I to assume he thinks I'm a dummy?   > If you don't feel you are qualified as a target for that book,= someday you may meet someone who is.  Give them the book. :-)c   ------------------------------  % Date: Tue, 09 May 2000 10:32:12 -0700t5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>a( Subject: Re: Unsolicited OpenVMS/NT book9 Message-ID: <026faffc.993eef37@usw-ex0110-076.remarq.com>E   Hi,I  9 I believe another chapter will/should be added in the 2nd7	 edition:-s  : Sorry to be brief but the sun is finally shining in London9 and I'll gladly continue this conversation (blatent self- 0 promotion) at the Roe-Buck pub on Richmond hill.   Cheers Richard Maher.0   TIER3o   Functional Overviewl  5 Tier3 is the client/server system that enables remotee5 client access to your server system resources. As thef1 middleware residing between the client and servert3 components of your application, Tier3 regulates andc2 schedules client requests, allocates the resources5 necessary to satisfy those requests, and channels the / resulting output back to the requesting client.   9 Similar to a Remote Procedure Call, Tier3 allows a remote 6 client (eg: a Powerbuilder program on a Windows PC) to; access your 3GL routine running on a VMS server. But unlike 5 other RPC implementations, Tier3 offers the followingy benefits: -i  0 *	Transparent Multi-Threading. Tier3 provides an8 independent multi-threaded communication server for each9 application. This relieves your server code from the needn* to perform its own threading and mutexing. * 3 *	Application Based Tuning & Configuration. Becauset9 every Tier3 application has its own communication server,t: inter-application resource contention is reduced, and each3 application on a given node can be tuned/configuredn independently. *=3 *	Persistent Network Connection. Once accepted, theo: network connection between client and communication server: is maintained until either your client or your server code8 asks specifically for it to be dropped. This removes the1 overhead of having to obtain a channel, request ar6 connection, and pass authorization, each time a client( needs to access your server application. *w3 *	Secure Client/Server Applications. In addition to 5 ensuring that only authorized clients can access youro8 application, Tier3 also identifies the username that the5 client is entitled to assume on the server node. Thisr4 allows your server application to perform additional3 security checks, perform charge-back accounting, orD3 maintain an audit trail of who has been modifying a 	 database.i *E. *	Re-usable Execution Servers. Tier3 execution9 servers are re-usable on a transactional basis, with youre7 development team controlling how long a transaction, or 8 server affinity, will be maintained. This is achieved by; effectively supplying your 3GL RECEIVE routine with a full-a6 duplex, or conversational, pipe as its only parameter. * 5 *	Dynamic Execution Server Creation. As client demands5 dictates, each applications communication server willm4 grow/shrink the execution server processing pool, in7 accordance with the parameters specified by your systems( manager in the Tier3 Configuration File. *i3 *	Preservation of Existing Investment. Tier3 servert6 development is as simple as creating a shareable image; containing the six subroutines or User Action Routines thatd5 Tier3 will activate on your behalf during the life ofn9 an execution server. Your UARs can be written in any 3GL,t8 and have the complete VMS execution environment at their6 disposal. You are free to spawn a sub-process, perform; inter-process communication, or your server application can ; become a client of another Tier3 application on a different8 node.0 * 1 *	This ability to re-use/incorporate existing 3GLc7 code into your new Tier3 applications, coupled with the@6 fact that your development staff will find very little; difference between developing Tier3 server applications andI5 developing any other VMS application, means that yourt$ existing IT investment is preserved. *04 *	No Tier3 Specific Client Software Required. By not5 layering another API on top of the standard Socket orv2 System Service interface, Tier3 allows your client8 developers unrestricted access to the underlying network9 protocol. Performance features such as asynchronous SENDs 9 and Interrupt/Out-of-Band functionality are all available- to you.-  ; In summary, once your organization has decided it needs thee9 security, performance, scalability and functionality of ac2 three-tiered client/server architecture, then your organization will need TIER3.a   Example server code:-w  < ************************************************************ ************************ *s                        *7 *         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALLc RIGHTS RESERVED.           * *K                        *: *    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED ONLY    * 9 *    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH1 LICENSE AND  WITH THE    *8 *    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE  OR ANY OTHER    *v7 *    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISEn MADE AVAILABLE  TO  ANY    *9 *    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THEi SOFTWARE  IS  HEREBY    *  *  TRANSFERRED.                   *  *I                        *5 *    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TOv CHANGE WITHOUT NOTICE AND    *5 *    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3  SOFTWARE LTD.                * *m                        *< ************************************************************ ************************ *+ * Routine Name: USER_INIT  *s: * This routine is called by Tier3 as part of the execution server's initialization2
 * procedures.  *1: * In this routine you would normally open files or connect to any database(s): * required by your application. In the DEMO application no files or databases are7 * accessed directly, but an exit handler is declared to  listen for an abnormal * termination. *i< * As a CLI has been loaded you are also free to spawn a sub- process via LIB$SPAWNs6 * if that is a requirement of your application, and it should be noted that there7 * is no restriction on this execution server becoming a  client of different Tier3g" * application(s) on other node(s). *- identification division. program-id.    user_init.l data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.c8 01  sys_status                      pic s9(9)       comp# value   external        ss$_normal.y 01  exit_desblk.9     03                              pic s9(9)       comp.u8     03                              pic s9(9)       comp% value   external        exit_handler.-8     03                              pic s9(9)       comp
 value   1.;     03                                              pointer $ value   reference       exit_status.9 01  exit_status                     pic s9(9)       comp.l *r 01  demo_context.<-     03  system_name                 pic x(8).i9     03  buffer_size                 pic 9(9)        comp.a.     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp.-9     03  session_count               pic 9(9)        comp.h9     03  message_count               pic 9(9)        comp.r9     03  lostlnk_count               pic 9(9)        comp.i9     03  persona_context             pic 9(9)        comp.  *+3 * DEBUG area. TIER3 sets the "language" to COBOL by  default, so the followinga2 * debugger commands are included just to show how. *-8 \d01  ss$_debug                     pic s9(9)       comp" value   external        ss$_debug. \d01  debug_commands.s, \d    03  cmd_len                   pic x(1) value   x"25".- \d    03                            pic x(37)L0 value   "set language cobol; show process/full". *u linkage section.- 01  t3_system_name                  pic x(8).i9 01  t3_buffer_size                  pic 9(9)        comp.f7 procedure division using t3_system_name, t3_buffer_sizer giving sys_status. 00.r *+8 * In this example, for the VMS debugger to be invoked at
 run-time thenE6 * the /conditionals=d qualifier needs to be applied at
 compile-time.l *e7 * To assist a run-time decision as to whether or not top invoke debug5 * TIER3 has defined a local DCL symbol T3$DEBUG. Thise
 symbol is set ; * to the value specified by the system manager in the Tier3 
 Configuration- * file ie: "Y" or "N". *- \d      call "lib$signal"-4 \d              using   by value        ss$_debug, 17 \d                      by reference    debug_commands.- *+; * Record some startup information in the execution server'se	 log file.b *-7     display "Initializing application " t3_system_name.g;     display "Buffer size is           " t3_buffer_size withb conversion.o *+5 * These example routines are designed specifically top handle requests fore8 * the DEMO application only and require a buffer size of 510 bytes, but a9 * single shareable image, or set of user action routines,t could be designed 8 * to service the requests of multiple applications. Such routines could use: * the t3_system_name argument to determine the appropriate code path to8 * execute at run-time. Similarly, by designing your user action routines to8 * be able to cope with a variable buffer size you afford the system manager1 * greater flexibility in tuning your application.n *h9 * We'll remember the Tier3 application parameters as theyr may come in handy. *-'     move t3_system_name to system_name.o'     move t3_buffer_size to buffer_size.M *+; * By passing the address of the data structure DEMO_CONTEXT  as the context5 * argument to the routine T3$SETCTX, the data is made2 available to all9 * subsequent user routines by becoming the first argumento
 in each call.p *-:     call "t3$setctx" using demo_context giving sys_status..     if sys_status not = ss$_normal go to fini. *+9 * DEMO does not need any application specific cleanup butn we'll check the exit * status anyway. *-:     call "sys$dclexh" using exit_desblk giving sys_status. *h fini.a     exit program.o *p end program user_init. *+ * Routine Name: USER_LOGON *s; * This routine is called by Tier3 when a client request hasm been allocated tot9 * the execution server for processing. From this point on  an association is said7 * to exist between the client and execution server. The  association is terminateda/ * by specifying either the t3$m_close or the t3t# $m_disconnect modifier in a call to 8 * the T3$SEND routine. The communication server may also cancel an association at2 * any time if the link to the client task is lost. *?; * Note: The output channel to the client will not be openedh until the USER_LOGON8 *       routine has returned control to Tier3. Therefore any attempt to call ; *       T3$SEND from this routine would result in the errorr T3$_CHANCLOSE beingl *       returned.* *- identification division. program-id.    user_logon. data division. working-storage section.8 01  t3$k_decnet                     pic s9(9)       comp$ value   external        t3$k_decnet.8 01  t3$k_tcp_ip                     pic s9(9)       comp$ value   external        t3$k_tcp_ip.8 01  lib$_strtru                     pic s9(9)       comp$ value   external        lib$_strtru.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal. 8 01  sys_status                      pic s9(9)       comp# value   external        ss$_normal.* **8 01  persona_create_flags            pic s9(9)       comp- value   external        persona_create_flags.a8 01  persona_assume_flags            pic s9(9)       comp- value   external        persona_assume_flags.D *0. 01  remote_node_name                pic x(31).. 01  remote_user_name                pic x(12).- 01  remote_user_socket              redefineso remote_user_name.T     03  remote_host_addr.b*         05  rha_1                   pic x.*         05  rha_2                   pic x.*         05  rha_3                   pic x.*         05  rha_4                   pic x.9     03  remote_port_num             pic 9(9)        comp.t *Y9 01  tcpip_rem_user_len              pic 9(4)        comp.F. 01  tcpip_rem_user                  pic x(21). *- linkage section. 01  demo_context.,-     03  system_name                 pic x(8).l9     03  buffer_size                 pic 9(9)        comp.a.     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp.f9     03  session_count               pic 9(9)        comp.a9     03  message_count               pic 9(9)        comp.V9     03  lostlnk_count               pic 9(9)        comp.A9     03  persona_context             pic 9(9)        comp.  * 9 01  transport_type                  pic 9(4)        comp.a *w- 01  remote_node_desc                pic x(8).: *D- 01  remote_user_desc                pic x(8).l *s 01  local_user_desc.     03  lud_class_len.9         05  lud_len                 pic 9(4)        comp.e9         05  lud_class               pic 9(4)        comp.m9     03  lud_addr                    pic 9(9)        comp.: * & procedure division using demo_context,(                          transport_type,*                          remote_node_desc,*                          remote_user_desc,1                          local_user_desc   givinge sys_status.i 00.a *+: * Initialize the timers and counts for session statistics. *-4     call "lib$init_timer" using timer_context giving sys_status.m.     if sys_status not = ss$_normal go to fini.       add 1 to session_count.t *+; * COBOL cannot receive arguments by descriptor transparentyt so8 * the Run-Time Library routine LIB$SCOPY_DXDX is used to copy: * the remote_node, remote_user and local_user arguments to fixedt* * length strings in local working-storage. *-     call "lib$scopy_dxdx" 4             using   by reference    remote_node_desc4                     by descriptor   remote_node_name             giving sys_status.8     if sys_status not = ss$_normal and lib$_strtru go to fini.        call "lib$scopy_dxdx"04             using   by reference    remote_user_desc4                     by descriptor   remote_user_name             giving sys_status.8     if sys_status not = ss$_normal and lib$_strtru go to fini.t *+7 * The return status lib$_strtru is treated as a seriousB	 error forb; * the local username. ie 12 bytes is the maximum length for  a VMS  * username.  *-     call "lib$scopy_dxdx"-3             using   by reference    local_user_desc 0                     by descriptor   session_user             giving sys_status..     if sys_status not = ss$_normal go to fini. *+9 * Report the client association in the execution server'st	 log file.n *-;     display "Association with ", session_user(1:lud_len), "i
 established".e:     display "Transport = " transport_type with conversion.,     display "Rem node  = " remote_node_name.(     display "Rem user  = " no advancing.       evaluate    transport_type8         when    t3$k_decnet     display remote_user_name.         when    t3$k_tcp_ip     call "sys$fao"2                                         using   by& descriptor   "!@UB.!@UB.!@UB.!@UB:!ZL"2                                                 by reference    tcpip_rem_user_lene2                                                 by descriptor   tcpip_rem_usero2                                                 by' reference    rha_1, rha_2, rha_3, rha_4-2                                                 by value        remote_port_num:                                         giving  sys_status3                                 if sys_status not =  ss$_normal go to fini end-if6                                 display tcpip_rem_user (1:tcpip_rem_user_len)     end-evaluate.n *+6 * By assuming the persona of the VMS username that the remote client has : * been authorized to use on local node we have removed the need to performH9 * additional security checking such as $check_access. IE:u This server will9 * be running with only those privileges and access rightso that the clientd5 * is entitled to assume. (Let VMS do all the work :-)t *s0 * NB: Again, this is only a suggestion and not a requirement of Tier3. If: *     you choose to use this extremely usefull VMS feature then the username-8 *     that the demo application will run under will need DETACH privilege1 *     and read access to SYSUAF (Usually SYSPRV).v *-     call "sys$persona_create"e/         using   by reference    persona_contexte7                 by descriptor   session_user(1:lud_len)e4                 by value        persona_create_flags         giving  sys_status.f.     if sys_status not = ss$_normal go to fini.       call "sys$persona_assume"f/         using   by reference    persona_contextl4                 by value        persona_assume_flags         giving  sys_status.n *e fini.s     exit program.m *e end program user_logon.e *+ * Routine: USER_RECV *f3 * The USER_RECV routine is called by Tier3 for each  message, or 7 * fragment of a message, that is received from a clientr
 with which% * the execution server is associated.s *t6 * In the DEMO example we are receiving one message per associationt * with no fragmentation. *R; * If the status value T3$_CHANCLOSE is returned from the T3o $SENDd7 * routine it is assumed that the link to the client hasu	 been lostV: * so we simply return control to Tier3 after resetting our exist - * status to SS$_NORMAL to avoid server crash.- *e; * NB:   If you application incorporates User Written Systema Services: *       do NOT use any executive mode dispatching codes in	 the range < *       -3000 to -2900 as these codes are reserved to Tier3. *- identification division. program-id.    user_recv.c data division. working-storage section.8 01  t3$_chanclose                   pic s9(9)       comp& value   external        t3$_chanclose.8 01  jbc$_nosuchent                  pic s9(9)       comp' value   external        jbc$_nosuchent.o8 01  jbc$_nomoreent                  pic s9(9)       comp' value   external        jbc$_nomoreent.r8 01  jbc$_normal                     pic s9(9)       comp$ value   external        jbc$_normal.8 01  ss$_abort                       pic s9(9)       comp" value   external        ss$_abort.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.t9 01  sys_status                      pic s9(9)       comp.T *38 01  t3$m_close                      pic 9(9)        comp# value   external        t3$m_close. 8 01  t3$m_now                        pic 9(9)        comp! value   external        t3$m_now.c8 01  t3$m_more                       pic 9(9)        comp" value   external        t3$m_more.8 01  t3$m_oob                        pic 9(9)        comp! value   external        t3$m_oob.u8 01  qui$_display_entry              pic s9(9)       comp+ value   external        qui$_display_entry. 8 01  qui$_cancel_operation           pic s9(9)       comp. value   external        qui$_cancel_operation.8 01  qui$m_search_wildcard           pic s9(9)       comp. value   external        qui$m_search_wildcard. *a9 01  sts_index                       pic s9(9)       comp. 9 01  on_or_off                       pic s9(9)       comp.s9 01  entry_count                     pic 9(9)        comp.n
 01  qui_iosb.r9     03  qui_cond                    pic s9(9)       comp.n9     03                              pic s9(9)       comp.e 01  que_status_table.r8     03                              pic s9(9)       comp. value   external        qui$m_queue_available.-     03                              pic x(10)c value   "AVAILABLE".8     03                              pic s9(9)       comp) value   external        qui$m_queue_busy.t-     03                              pic x(10)c value   "BUSY".T8     03                              pic s9(9)       comp- value   external        qui$m_queue_disabled.t-     03                              pic x(10)@ value   "DISABLED".l8     03                              pic s9(9)       comp) value   external        qui$m_queue_idle.e-     03                              pic x(10)u value   "IDLE".n8     03                              pic s9(9)       comp+ value   external        qui$m_queue_paused.o-     03                              pic x(10)e value   "PAUSED".l8     03                              pic s9(9)       comp, value   external        qui$m_queue_pausing.-     03                              pic x(10)u value   "PAUSING".8     03                              pic s9(9)       comp- value   external        qui$m_queue_resuming.y-     03                              pic x(10)  value   "RESUMING".n8     03                              pic s9(9)       comp, value   external        qui$m_queue_stalled.-     03                              pic x(10)* value   "STALLED".8     03                              pic s9(9)       comp- value   external        qui$m_queue_starting.R-     03                              pic x(10)  value   "STARTING".E8     03                              pic s9(9)       comp, value   external        qui$m_queue_stopped.-     03                              pic x(10)  value   "STOPPED".8     03                              pic s9(9)       comp- value   external        qui$m_queue_stopping.E-     03                              pic x(10)N value   "STOPPING".E- 01  que_status_array                redefinesO que_status_table. .     03  que_status_item             occurs 11.9         05  que_value               pic s9(9)       comp.O.         05  que_text                pic x(10). 01  que_flags_table.8     03                              pic s9(9)       comp, value   external        qui$m_queue_printer.-     03                              pic x(10)* value   "PRINTER".8     03                              pic s9(9)       comp* value   external        qui$m_queue_batch.-     03                              pic x(10)d value   "BATCH".8     03                              pic s9(9)       comp, value   external        qui$m_queue_generic.-     03                              pic x(10)s value   "GENERIC".8     03                              pic s9(9)       comp- value   external        qui$m_queue_terminal.e-     03                              pic x(10)c value   "TERMINAL". - 01  que_flags_array                 redefinesn que_flags_table.-     03  que_flags_item              occurs 4.c9         05  flags_value             pic s9(9)       comp.l.         05  flags_text              pic x(10). 01  job_status_table. 8     03                              pic s9(9)       comp+ value   external        qui$m_job_aborting. -     03                              pic x(15)c value   "ABORTING". 8     03                              pic s9(9)       comp, value   external        qui$m_job_executing.-     03                              pic x(15)u value   "EXECUTING".8     03                              pic s9(9)       comp* value   external        qui$m_job_holding.-     03                              pic x(15)  value   "HOLDING".8     03                              pic s9(9)       comp/ value   external        qui$m_job_inaccessible. -     03                              pic x(15)e value   "INACCESSIBLE". 8     03                              pic s9(9)       comp* value   external        qui$m_job_pending.-     03                              pic x(15)_ value   "PENDING".8     03                              pic s9(9)       comp* value   external        qui$m_job_refused.-     03                              pic x(15)  value   "REFUSED".8     03                              pic s9(9)       comp+ value   external        qui$m_job_retained.E-     03                              pic x(15)  value   "RETAINED".l8     03                              pic s9(9)       comp* value   external        qui$m_job_stalled.-     03                              pic x(15)_ value   "STALLED".8     03                              pic s9(9)       comp+ value   external        qui$m_job_starting. -     03                              pic x(15)s value   "STARTING".u8     03                              pic s9(9)       comp, value   external        qui$m_job_suspended.-     03                              pic x(15)g value   "SUSPENDED".8     03                              pic s9(9)       comp0 value   external        qui$m_job_timed_release.-     03                              pic x(15)o value   "TIMED RELEASE".- 01  job_status_array                redefines  job_status_table. .     03  job_status_item             occurs 11.9         05  job_value               pic s9(9)       comp.i.         05  job_text                pic x(15). *o< 01  item_list_addr                                  pointer. *  01  entry_item_list.     03  item_search_entry.#         05  pic s9(4) comp value 4. )         05  pic s9(4) comp value external  qui$_search_number.e2         05  pointer value reference search_number.         05  pic s9(9) comp.e     03  item_queue_flags.e#         05  pic s9(4) comp value 4.w;         05  pic s9(4) comp value external qui$_queue_flags. .         05  pointer value reference que_flags.         05  pic s9(9) comp.r     03  item_que_status.#         05  pic s9(4) comp value 4. <         05  pic s9(4) comp value external qui$_queue_status./         05  pointer value reference que_status.          05  pic s9(9) comp.s     03  item_job_status.#         05  pic s9(4) comp value 4. :         05  pic s9(4) comp value external qui$_job_status./         05  pointer value reference job_status.l         05  pic s9(9) comp.      03  item_que_name.$         05  pic s9(4) comp value 31.:         05  pic s9(4) comp value external qui$_queue_name.-         05  pointer value reference que_name.y1         05  pointer value reference que_name_len.      03  item_job_name.$         05  pic s9(4) comp value 39.8         05  pic s9(4) comp value external qui$_job_name.-         05  pointer value reference job_name.o1         05  pointer value reference job_name_len.r     03  pic s9(9) comp.l *  01  wild_item_list.t     03  item_search_flags.#         05  pic s9(4) comp value 4. <         05  pic s9(4) comp value external qui$_search_flags.:         05  pointer value reference qui$m_search_wildcard.         05  pic s9(9) comp.h     03  item_queue_flags.s#         05  pic s9(4) comp value 4.r;         05  pic s9(4) comp value external qui$_queue_flags.G.         05  pointer value reference que_flags.         05  pic s9(9) comp.l     03  item_job_entry.o#         05  pic s9(4) comp value 4.i<         05  pic s9(4) comp value external qui$_entry_number..         05  pointer value reference job_entry.         05  pic s9(9) comp.r     03  item_que_status.#         05  pic s9(4) comp value 4. <         05  pic s9(4) comp value external qui$_queue_status./         05  pointer value reference que_status.          05  pic s9(9) comp.      03  item_job_status.#         05  pic s9(4) comp value 4.n:         05  pic s9(4) comp value external qui$_job_status./         05  pointer value reference job_status.3         05  pic s9(9) comp.      03  item_que_name.$         05  pic s9(4) comp value 31.:         05  pic s9(4) comp value external qui$_queue_name.-         05  pointer value reference que_name.31         05  pointer value reference que_name_len.      03  item_job_name.$         05  pic s9(4) comp value 39.8         05  pic s9(4) comp value external qui$_job_name.-         05  pointer value reference job_name. 1         05  pointer value reference job_name_len.$     03  pic s9(9) comp.  * 9 01  search_number                   pic s9(9)       comp. . 01  que_name                        pic x(31).9 01  que_name_len                    pic 9(4)        comp.l9 01  que_status                      pic s9(9)       comp. 9 01  que_flags                       pic s9(9)       comp.e. 01  job_name                        pic x(39).9 01  job_name_len                    pic 9(4)        comp. 9 01  job_status                      pic s9(9)       comp._9 01  job_entry                       pic s9(9)       comp.  * 9 01  local_flags                     pic 9(9)        comp.r 01  show_entry_reply. *     03                              pic xx
 value   "11". -     03  se_entry_number             pic 9(4). .     03  se_job_name                 pic x(39)..     03  se_job_status               pic x(15)..     03  se_que_name                 pic x(31)..     03  se_que_type                 pic x(10)..     03  se_que_status               pic x(10).8 01  show_entry_len                  pic 9(9)        comp value   111. 01  error_msg.*     03                              pic xx
 value   "00".s,     03  error_len                   pic 999./     03  error_text                  pic x(505).3 *e linkage section. 01  demo_context. -     03  system_name                 pic x(8). 9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp._9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp.u9     03  persona_context             pic 9(9)        comp.  * 
 01  msg_buff. +     03  msg_type                    pic xx.          88  show_entry
 value   "10". /     03                              pic x(508).n 01  show_entry_msg redefines       msg_buff.t+     03                              pic xx.t-     03  show_entry_number           pic 9(4).s-     03  show_entry_max              pic 9(4).e * 9 01  msg_size                        pic s9(9)       comp.n *o9 01  msg_flags                       pic s9(9)       comp.  *n procedure division         using   demo_context,a                 msg_buff,f                 msg_size,n                 msg_flagst"                 giving sys_status. kick_off section.h 00.-     add 1 to message_count.Y *+; * If the client has sent a message that is greater than theu buffer size 6 * for this application, then Tier3 will set the bit T3 $V_MORE in the4 * msg_flags argument. The remaining fragments of the message are not lost, : * and will be delivered to user_recv routine in subsequent invocations.9 * This example does not contain all of the code necessaryo to properly : * handle fragmented messages. The following "IF" statement is included_9 * merely to illustrate how your routine would be notified  of fragmentation.s *-6     call "mth$jiand" using msg_flags, t3$m_more giving local_flags.:     if local_flags not = zeros display "Fragmented message - More to come". *+8 * NOTE: All Tier3 parameters passed to your routines are
 maintained ina: * user mode read-only storage. Any attempt to modify their
 contents willo9 * result in an access violation. Take a copy of any input_ parameter that0 * needs to be modified to local working-storage. *-"     move low-values to error_text.       evaluate        true:             when    show_entry      if show_entry_number = zeross3                                             perform  get_entry_wild3                                     else    perform  get_entry_info*                                     end-if5             when    other           move ss$_abort to 
 sys_status     end-evaluate.u       exit program.n *  get_entry_wild section.$ 00. 3     set item_list_addr to reference wild_item_list.e       perform get_que_info.U  "     if sys_status = jbc$_nosuchent             perform send_error'     else    if sys_status = jbc$_normal -                     move zeros to entry_countt2                     perform until sys_status not =+ jbc$_normal or entry_count = show_entry_maxa0                             add 1 to entry_count.                             perform send_entry6                             if sys_status = ss$_normal8                                     perform get_que_info"                             end-if                     end-performi2                     if sys_status = jbc$_normal or jbc$_nomoreent*                             call "t3$send"8                                     using   by reference "99EOF"a4                                             by value
 5, t3$m_close 7                                     giving  sys_status.t *+5 * The maximum number of entries may have been reachedd before all $GETQUI information4 * had been retrieved for the wildcard search, or the association with the client maym7 * have been terminated prematurely by the communicationu server, therefore we muste4 * be sure to tell the job controller that we wish to terminate the wildcard search. *-/     if sys_status = ss$_normal or t3$_chanclose              call "sys$getquiw"'                     using   by value 0,n qui$_cancel_operation, 0, 0y1                             by reference qui_iosb )                             by value 0, 0 &                     giving  sys_status9             if sys_status = ss$_normal and qui_cond not =_ jbc$_normal 0                     move qui_cond to sys_status. *  get_entry_info section.e 00._7     move show_entry_number to search_number, job_entry. 4     set item_list_addr to reference entry_item_list.       perform get_que_info.   "     if sys_status = jbc$_nosuchent             perform send_error'     else    if sys_status = jbc$_normalc&                     perform send_entry.                     if sys_status = ss$_normal*                             call "t3$send"8                                     using   by reference "99EOF" 4                                             by value
 5, t3$m_closen7                                     giving  sys_status.o *o fini.e4     if sys_status = t3$_chanclose move ss$_normal to sys_status.v *c send_error section.f 00.a     move 13 to error_len.r5     move "No such entry" to error_text (1:error_len).u     call "t3$send"-             using   by reference    error_msga;                     by value        buffer_size, t3$m_closes             giving  sys_status.  *a send_entry section.t 00. &     move job_entry to se_entry_number.1     move job_name(1:job_name_len) to se_job_name. 1     move que_name(1:que_name_len) to se_que_name.   '     move zeros to sts_index, on_or_off. 9     perform until sts_index = 11 or on_or_off not = zeros              add 1 to sts_index.             call "mth$jiand" using job_status,8                                    job_value (sts_index),                             giving on_or_off     end-perform.     if on_or_off = zeros+             move "UNKNOWN" to se_job_status 6     else    move job_text (sts_index) to se_job_status$             move zeros to on_or_off.       move zeros to sts_index.9     perform until sts_index = 11 or on_or_off not = zeros              add 1 to sts_index/             call "mth$jiand" using  que_status, 9                                     que_value (sts_index)1-                             giving  on_or_off      end-perform.     if on_or_off = zeros+             move "UNKNOWN" to se_que_status 6     else    move que_text (sts_index) to se_que_status$             move zeros to on_or_off.       move zeros to sts_index.8     perform until sts_index = 4 or on_or_off not = zeros             add 1 to sts_index.             call "mth$jiand" using  que_flags,;                                     flags_value (sts_index)x-                             giving  on_or_offt     end-perform.     if on_or_off = zeros)             move "UNKNOWN" to se_que_type 7     else    move flags_text (sts_index) to se_que_type.        call "t3$send"4             using   by reference    show_entry_reply<                     by value        show_entry_len, t3$m_now             giving  sys_status._ *t get_que_info section.  00. (     call "sys$getquiw" using by value 0,$ qui$_display_entry, 0 item_list_addr2                              by reference qui_iosb*                              by value 0, 0(                     giving   sys_status.;     if sys_status = ss$_normal move qui_cond to sys_status.  *  end program user_recv. *+ * Routine: USER_LOGOFF * 6 * This routine is called when the association with the client has been_4 * terminated, either by the USER_RECV routine or the communication server,S: * and the USER_RECV routine has returned control to Tier3. *o; * For the DEMO example we are logging resource usage by the  client.  *- identification division. program-id.    user_logoff.  data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.u9 01  sys_status                      pic s9(9)       comp.9 * 8 01  persona_assume_flags            pic s9(9)       comp- value   external        persona_assume_flags.a8 01  restore_persona                 pic 9(9)        comp
 value   1. *p linkage section. 01  demo_context._-     03  system_name                 pic x(8). 9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp. 9     03  persona_context             pic 9(9)        comp.  * 8 procedure division using demo_context giving sys_status. 00._9     display "Session completed with user ", session_user.a      move spaces to session_user.       call "sys$persona_assume" /         using   by reference    restore_personai4                 by value        persona_assume_flags         giving  sys_status._.     if sys_status not = ss$_normal go to fini.  :     call "sys$persona_delete" using persona_context giving sys_status._.     if sys_status not = ss$_normal go to fini. *+( * Display the user's session statistics. *u: * The Run-Time Library performance reporting routines have	 been usedp6 * as a very simple example of obtaining information on server resource 5 * usage by a client. If this is a requirement of your  application then9 * you should consider obtaining more detailed informationu via the VMS 6 * system services $GETTIM and $GETJPI and accumulating totals for each ; * user in a disk file. This disk file could be processed atl a lateru4 * date as part of charge-back accounting procedures. *-4     call "lib$show_timer" using timer_context giving sys_status.i *9 fini.      exit program.e *l end program user_logoff. *+ * Routine: USER_FINI * : * This routine is called by Tier3 when the server has been culled from 6 * the execution server pool due to inactivity timeout. *m7 * In the DEMO aplication there are no files to close or  databases to4 * disconnect from so the only image rundown activity performed here& * is the logging of server statistics. *- identification division. program-id.    user_fini.  data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.  *  linkage section. 01  demo_context._-     03  system_name                 pic x(8). 9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp. 9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp. 9     03  persona_context             pic 9(9)        comp.  * 8 procedure division using demo_context giving ss$_normal. 00.$-     display "Execution server shutting down". ;     display "Number of associations formed: " session_count  with conversion.;     display "Number of messages received  : " message_count  with conversion.;     display "Number of client links broken: " lostlnk_count  with conversion.     exit program.o *  end program user_fini. *+ * Routine: USER_INT  * 8 * The user interrupt routine differs from the five other user action : * routines invoked by Tier3, in that it is called from AST level. * ; * In this example we merely increment a count of the number( associations5 * that were terminated abnormally. This count will be9 reported at image  * exit.l *- identification division. program-id.    user_int. data division. working-storage section.8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.u, 01  link_lost                       pic x(1) value   x"01". *  linkage section. 01  demo_context. -     03  system_name                 pic x(8).n9     03  buffer_size                 pic 9(9)        comp. .     03  session_user                pic x(12).9     03  timer_context               pic 9(9)        comp.s9     03  session_count               pic 9(9)        comp. 9     03  message_count               pic 9(9)        comp. 9     03  lostlnk_count               pic 9(9)        comp.l9     03  persona_context             pic 9(9)        comp.  *r. 01  interrupt_msg                   pic x(16). *59 01  interrupt_type                  pic 9(9)        comp.e     88  system_msg$ value   external        t3$k_system.     88  user_msg" value   external        t3$k_user. * ) procedure division using    demo_context, *                             interrupt_msg,*                             interrupt_type'                   giving    ss$_normal.. 00.  *+6 * The client program in the DEMO example does not send interrupts, 9 * therefore the only interrupt that this routine needs tou	 cater fora8 * is that of link disconnection notification sent by the
 communication9	 * server.  * 3 * The Interrupt_Type field with contain T3$K_SYSTEMe indicating that 6 * the message is from the communication server and the
 first byte ofu; * the interrupt message will contain the value 1 indicating3
 that it is9 * a link disconnection message. Currently bytes 2 thru 16 
 are unused; * for Tier3 interrupts, and link disconnection notificatione is the onlye" * interrupt that is sent by Tier3. * 5 * Note: The maximum message size for TCP/IP interrupt  messages is 1 byte. 9 *       This is a network transport restriction and not a  TIER3 restriction. *-6     if (system_msg and interrupt_msg(1:1) = link_lost)"             add 1 to lostlnk_count3             display "Link to client has been lost"._       exit program.i *9 end program user_int.  *+ * Routine: exit_handler. *r: * This routine is application specific and not required by Tier3. *h3 * For the DEMO example there are no special cleanupm
 procedures9 * required but we'll interogate the exit status for error9 loggingv * purposes.  *$9 * VMS won't let a new persona to survive after image exitg so no $ * special cleanup check is required. *- identification division. program-id.    exit_handler. data division. working-storage section.8 01  t3$_nocomsrv                    pic s9(9)       comp% value   external        t3$_nocomsrv. 8 01  ss$_normal                      pic s9(9)       comp# value   external        ss$_normal.a linkage section.9 01  exit_status                     pic s9(9)       comp. % procedure division using exit_status.b 00.u.     display "In exit handler - " no advancing.     evaluate        exit_statusa3             when    ss$_normal      display "Normalc rundown. Everything is OK"7             when    t3$_nocomsrv    display "Can't find  Tier3 communication server" 5             when    other           if exit_status is  failureo9                                             display "This ) will bring down the communication server"n3                                     else    display50 "Problem, but another server will take my place"*                                     end-if     end-evaluate.e       exit program._ *e end program exit_handler.o     Example Build routine:-    ! < ************************************************************ ************************ !a *l                        *8 !*         COPYRIGHT (c) 1994 BY TIER3 SOFTWARE LTD. ALL RIGHTS RESERVED.           * !g *                         *; !*    THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE9 USED AND COPIED ONLY    * : !*    IN ACCORDANCE  WITH THE TERMS AND CONDITIONS OF SUCH LICENSE AND  WITH THE    *9 !*    THE INCLUSION  OF THE ABOVE COPYRIGHT NOTICE.  THIS  SOFTWARE  OR ANY OTHER    * 8 !*    COPIES  THEREOF MAY NOT  BE PROVIDED  OR OTHERWISE MADE AVAILABLE  TO  ANY    *: !*    OTHER  PERSON.  NO  TITLE TO  AND OWNERSHIP  OF  THE SOFTWARE  IS  HEREBY    *  !* TRANSFERRED.                   *( !. *                         *6 !*    THE INFORMATION  IN THIS SOFTWARE  IS SUBJECT TO CHANGE WITHOUT NOTICE AND    *6 !*    SHOULD NOT BE CONSTRUED AS A COMMITMENT BY TIER3 SOFTWARE LTD.                * !l *                         * ! < ************************************************************ ************************ $! $! Procedure: BUILD_DEMO $!; $! This command procedure builds and installs the DEMO_UARS  shareable imagek7 $! for the Tier3 DEMO example. After this procedure has  been run successfully 6 $! the DEMO application can be registered in the Tier3 configuration file.s $! $   SAY := WRITE SYS$OUTPUT   $   REQD_PRIVS = "CMKRNL,SYSNAM"% $   PREV_PRIVS = F$SETPRV(REQD_PRIVS)o $   ON ERROR THEN GOTO FINI  $   ON CONTROL_Y THEN GOTO FINI 1 $   IF F$PRIVILEGE(REQD_PRIVS) THEN GOTO BUILD_ITn7 $   SAY "You need (CMKRNL,SYSNAM) privilege to run thiss
 command file" 
 $   GOTO FINI) $!
 $BUILD_IT: $!8 $! Compile the source files. P1 is checked to see wheter debug is required.% $   IF P1 .EQS. "Y" .OR. P1 .EQS. "y"  $   THEN5 $       COBOL/LIST/DEBUG/CONDITIONALS=D DEMO_UARS.COB  $       LINK_QUAL = "/DEBUG" $   ELSE  $       COBOL/LIST DEMO_UARS.COB $       LINK_QUAL = ""	 $   ENDIF  $! $   CREATE QUIDEF.MAR  ;+: ; Some of the external references in DEMO_UARS.COB will be
 unresolved8 ; at link-time because the linker won't find them in the default system7 ; libraries. This macro file is needed to resolve those  references.s ;u5 ; Note: This is not a Tier3 requirement. This file isl needed only because 9 ;       the DEMO User Access Routines need to talk to them job controller, ;       and use the persona system services. ;-;                 .TITLE          GETQUI External symbols ande condition codesi  &                 $QUIDEF         GLOBAL&                 $JBCMSGDEF      GLOBAL&                 $IMPDEF         GLOBAL    / PERSONA_CREATE_FLAGS==<IMP$M_ASSUME_DEFPRIV!  -    IMP$M_ASSUME_DEFCLASS>  / PERSONA_ASSUME_FLAGS==<IMP$M_ASSUME_SECURITY! -d   IMP$M_ASSUME_JOB_WIDE! -<                                        IMP$M_ASSUME_ACCOUNT>                   .END ;n $   MACRO QUIDEF.MAR $!; $! We'll define the logical name LNK$LIBRARY to point to T3g
 $USER so that 4 $! the Tier3 system service library will be searched automatically. $!# $   DEFINE/USER LNK$LIBRARY T3$USERp $! $   LINK/SHARE'LINK_QUAL'n) DEMO_UARS.OBJ,QUIDEF.OBJ,SYS$INPUT/OPTIONA !a: ! Transfer Vectors were not used in the DEMO example so we
 need to forcek8 ! the linker to define the procedure entry masks for our User Action 7 ! Routines as universal symbols. If not, Tier3 won't be  able to find them. !r9 ! There are no EXTERNAL file connectors, database handlesr or working- 6 ! storage variables defined in the DEMO example, so no PSECT attribute 9 ! modification is required to build this shareable image.n !          UNIVERSAL=USER_INIT          UNIVERSAL=USER_LOGON         UNIVERSAL=USER_RECVa         UNIVERSAL=USER_LOGOFFv         UNIVERSAL=USER_FINIn         UNIVERSAL=USER_INT $!9 $! Unless the resulting shareable image will be placed in 
 the SYS$SHAREe; $! directory, a trusted logical name needs to be defined so 
 that Tier37 $! can locate the shareable image at run-time. NB: this  requirement is# $! *not* enforced for DEBUG images.  $!; $! SYSNAM privilege is required to define a trusted logicalt name and8 $! CMKRNL privilege is required to install the shareable image. $!- $   UAR_SPEC = F$PARSE("DEMO_UARS.EXE") - ";" 0 $   DEFINE/SYSTEM/EXEC/NOLOG DEMO_UARS 'UAR_SPEC $! $   INSTALL := $INSTALL/COMMANDr $!3 $! In the following command the /SHARE qualifier is  required. The /OPENf' $! and /HEADER qualifiers are optional.  $!1 $   IF F$FILE_ATTRIBUTES("DEMO_UARS.EXE","KNOWN") ; $   THEN        INSTALL REPLACE DEMO_UARS/OPEN/HEADER/SHARE ; $   ELSE        INSTALL ADD     DEMO_UARS/OPEN/HEADER/SHARE 	 $   ENDIFv $! $FINI:% $   PREV_PRIVS = F$SETPRV(PREV_PRIVS)  $   EXIT $!         * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifulo   ------------------------------  $ Date: Tue, 9 May 2000 08:56:11 +0100: From: "Dean Richard Benson" <dean.benson@remove_metrw.com>2 Subject: Re: Upgrading system disk ... many thanks, Message-ID: <8f8g7d$5bn$1@murrow.sp.trw.com>   Hi all._  * Thanks for your support and help recently.  ; A few people have suggested disk to disk transfers, however0< one of the reasons that we are doing this move is because we? have ran out of space in the storage cabinet, and are combiningg> two sets of current disks onto one new set, so we have no room3 to put the new disks in until the old ones are out.c  B I have confirmed that the tape drive supports compression by using3 the following DCL (taken from the VMS FAQ found at:t7 http://www.openvms.digital.com/wizard/openvms_faq.html)   6     $ Devdepend2 = F$GETDVI("$4$MKA200:","DEVDEPEND2")     $ Comp_sup = %X00200000      $ Comp_ena = %X00400000$5     $ IF (Devdepend2.AND.Comp_sup).EQ.Comp_sup THEN - 0         WRITE SYS$OUTPUT "Compression supported"5     $ IF (Devdepend2.AND.Comp_ena).EQ.Comp_sup THEN - .         WRITE SYS$OUTPUT "Compression enabled"  = This means that for the first disk, I will use this command :s  "  backup                          _"      /block_size=32256           _"      /list=dka100:[drb]disk2.lis _"      /ignore=(label)             _"      /log                        _"      /verify                     _"      /noalias                    _"      /image                      _"      dka200:                     _"      mka500:disk2.bck            _"      /media_format=compaction    _      /rewind  D and for the second disk, I will use the same command but without the- /rewind paramter, and the disks etc adjusted.s  K Since the data that I will be moving is rather business critical, I want tor6 be 100% sure that there can be no floors in this plan!   Regards.   Dean  E "Dean Richard Benson" <dean.benson@remove_metrw.com> wrote in message"& news:8f62h6$scq$1@murrow.sp.trw.com...	 > Hi all.  >j8 > Hardware : AlphaServer 1000A 4/266 running VMS 6.2-1H3 >r@ > I am going to rearrange the disk setup in the storage cabinet.$ > (need to upgrade the system disk). > A > My plans are to reboot the system from the CD drive, get to thetA > prompt and backup the system disk.  Then power everything down,_K > phyically change the setup, power back up, configure the disk controller, J > boot from CD again and restore to the new disk from the previous backup. >uG > My question is, have I missed anything obvious in the above scenario?  >-E > Secondly, what would be the safest method to use to both backup andeK > restore the system disk.  Could any kind sole help me with the parameters 3 > that I should use on the backup command for this?e > " > Thanks all for any help offered. >r
 > Regards. >s > Dean >  >d   ------------------------------  $ Date: Tue, 9 May 2000 10:58:27 -0400" From: "DA" <da@digitalsurplus.com>1 Subject: Vaxstation 4000 90 on ebay - going todayg. Message-ID: <pSVR4.32$XM4.2395@news.shore.net>  > Vaxstation 4000 90 32mb rz25   on ebay  - auction ends today !@ http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=323355312   ------------------------------  % Date: Tue, 09 May 2000 08:47:49 -0700 5 From: Richard  <maher_rjNOmaSPAM@hotmail.com.invalid>i5 Subject: Re: Vaxstation 4000 90 on ebay - going today 9 Message-ID: <053a541c.99ff9663@usw-ex0109-070.remarq.com>   8 Please update with the closing price. What screen did it have?b     * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautifulr   ------------------------------  % Date: Tue, 09 May 2000 12:02:08 +0200w3 From: Jonas Nielsen <Jonas-Nielsen@bornholm-gym.dk>m Subject: Which VAX to buy?/ Message-ID: <3917E220.FCB75242@bornholm-gym.dk>    Hi there  A Im a young UNIX-freak, who has become a bit interested in the VMSwH operating system :-). So, i want a VAX and i have been offered some used VAXen:  ! Digital VAXstation 3100/M76 - SPXo Digital VAXstation 4000 - 602 Digital VAXserver 3100 (Scsi disk Ext. SCSI udtag)  5 and a Digital Storage Expansion (99 MB Disk + CD-ROM)s  C Basically, i just want to learn OpenVMS, DECwindows a little bit ofaG system administration, and perhaps some programming. I thought it wouldeB be a good idea to buy the Storage Expansion as well, so that i can= install programs and newer releases of OpenVMS on the system.y  H So i ask you guys, (since i know nothing about VAX), which configuration, would you suggest? The VS4000 or VS3100-M76?= And finally and very important :-), what should i pay for it?   & Any help would be greatly appreciated!  
 Kind Regards, 
 Jonas Nielsenp Denmark3   ------------------------------   Date: 9 May 2000 13:19:00 GMTn2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Which VAX to buy?6 Message-ID: <8f9384$1cg$2@mailint03.im.hou.compaq.com>  e In article <3917E220.FCB75242@bornholm-gym.dk>, Jonas Nielsen <Jonas-Nielsen@bornholm-gym.dk> writes:aB :Im a young UNIX-freak, who has become a bit interested in the VMSI :operating system :-). So, i want a VAX and i have been offered some usedn :VAXen:f :s" :Digital VAXstation 3100/M76 - SPX :Digital VAXstation 4000 - 60g3 :Digital VAXserver 3100 (Scsi disk Ext. SCSI udtag)s  E   Of those three systems, the VAXstation 4000 model 60 is likely the oJ   best choice.  Faster, capable of more memory, and capable of supporting H   a SCSI system disk above 1.073 GB.    It can optionally have some I/O E   expansion via an (optional) TURBOchannel bus, as well -- the other nF   systems have very limited expansion.  Next choice would probably be F   the VAXstation 3100 model 76, though there are a few VAXserver 3100 D   series systems that can be fairly fast boxes -- we need the model H   number of the system to be sure.  The SPX was the fastest graphics in I   that VAXstation series, though it's an antique with antique performancen   by current standards.y  A   All VAXstation 3100 series systems are limited to a system diskfA   capacity of 1.073 GB or less.  See the OpenVMS FAQ for details.   D   Make sure you have as much memory as you can get -- the VAXstation@   3100 model 76 tops out at 32 MB.  The VAXstation 4000 model 60   supports rather more.a  6 :and a Digital Storage Expansion (99 MB Disk + CD-ROM)  A   The disk is way too small, but the CD-ROM drive will be useful.i$   You'll probably want to scrounge a  D :Basically, i just want to learn OpenVMS, DECwindows a little bit ofH :system administration, and perhaps some programming. I thought it wouldC :be a good idea to buy the Storage Expansion as well, so that i can > :install programs and newer releases of OpenVMS on the system.  E   See the details of the OpenVMS hobbyist program in the OpenVMS FAQ.   I :So i ask you guys, (since i know nothing about VAX), which configuration - :would you suggest? The VS4000 or VS3100-M76?g> :And finally and very important :-), what should i pay for it?  F   As few Kroner as the seller will take, but you knew that.  (You can G   get some nice used Alpha systems rather inexpensively, and this tendsi+   to limit the value of older VAX systems.)s  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 09 May 2000 13:38:28 GMTt+ From: Chris Doran <chris_doran@my-deja.com>m Subject: Re: Which VAX to buy?) Message-ID: <8f94ch$267$1@nnrp1.deja.com>t  / In article <3917E220.FCB75242@bornholm-gym.dk>,t6   Jonas Nielsen <Jonas-Nielsen@bornholm-gym.dk> wrote:0 > i want a VAX and i have been offered some used > VAXen: ...n? > And finally and very important :-), what should i pay for it?.  C FWIW, a UK surplus dealer has just _offered_ me 200 UK pounds for adG 4000/60 plus some other bits. They will expect to _sell_ it for 5 to 10o times that price.   G I haven't accepted the 200, as for that little I'd rather _give_ it tolG a hobbyist. So if you fancy a trip to London... (as I'm not prepared tok	 post it)..   Chriso      & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Tue, 09 May 2000 15:36:31 +0200r3 From: Jonas Nielsen <Jonas-Nielsen@bornholm-gym.dk>  Subject: Re: Which VAX to buy?/ Message-ID: <3918145F.FD625A67@bornholm-gym.dk>   + Hello Hoff - thanks a lot for your reply :)   G >   As few Kroner as the seller will take, but you knew that.  (You can I >   get some nice used Alpha systems rather inexpensively, and this tends - >   to limit the value of older VAX systems.)   g Yes... but the seller wants me to make an offer.. ;-) and frankly, i have no idea... is $140-200 way tok= much? (for the whole bunch, VAXstation 4000-60 + Storage EXP)   
 Kind regards,i Jonasi   ------------------------------   Date: 9 May 2000 13:59:45 GMT * From: helbig@astro.rug.nl (Phillip Helbig) Subject: Re: Which VAX to buy?. Message-ID: <8f95kh$5vm$1@info.service.rug.nl>  = In article <3917E220.FCB75242@bornholm-gym.dk>, Jonas Nielsenr( <Jonas-Nielsen@bornholm-gym.dk> writes:   	 >Hi there  >lB >Im a young UNIX-freak, who has become a bit interested in the VMSI >operating system :-). So, i want a VAX and i have been offered some useda >VAXen:  >s" >Digital VAXstation 3100/M76 - SPX >Digital VAXstation 4000 - 60 3 >Digital VAXserver 3100 (Scsi disk Ext. SCSI udtag)3 >h6 >and a Digital Storage Expansion (99 MB Disk + CD-ROM) > D >Basically, i just want to learn OpenVMS, DECwindows a little bit of6 >system administration, and perhaps some programming.    Great!  Welcome to the club!   > I thought it wouldC >be a good idea to buy the Storage Expansion as well, so that i can > >install programs and newer releases of OpenVMS on the system.  C For a VAX, unless you want to worry about tailoring, what (not) to uG install and so on, you need a 500 MB system disk; 1 GB is better.  The rI system disk can be in an external box.  (This can be an advantage, as it r( is easier to stick it on another system.  I >So i ask you guys, (since i know nothing about VAX), which configurationr- >would you suggest? The VS4000 or VS3100-M76?x  H All are nice; personally, I wouldn't recommend anything slower than the F 3100 M76.  The 4000/60 is the better machine---faster and can take an H arbitrarily large system disk (not that you need it); 3100s are limited I to 1.07 GB (just system disk, not other disks).  Otherwise, the 3100 M76  ) is nice.  Don't know about the VAXserver.3  > >And finally and very important :-), what should i pay for it?  G Nothing.  That is, if you're lucky you can get these sorts of machines uG for free (I even got a 4000/90 and a 4000/100A for free) or these days i even an older ALPHA for free.I  B By the way, I was on holiday on Bornholm last summer---nice place!   ------------------------------  % Date: Tue, 09 May 2000 16:35:43 +0200O= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>i Subject: Re: Which VAX to buy?) Message-ID: <3918223F.4D274325@gtech.com>t   Jonas Nielsen wrote:i > Yes... but the seller wants me to make an offer.. ;-) and frankly, i have no idea... is $140-200 way to ? > much? (for the whole bunch, VAXstation 4000-60 + Storage EXP)   D $200 is much for an antique system, but if it includes a monitor andB there are lot of RAM in the system and it is possible to connect a3 extra SCSI disk, then it may still be a fair price.*   Arne   ------------------------------  % Date: Tue, 09 May 2000 15:59:56 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>( Subject: Re: Which VAX to buy?) Message-ID: <391827EC.93531267@bbc.co.uk>    Chris   K I'm still trying to schedule something, maybe I can get a mate to pick someD stuffP up. Where are you in London?   Chris Doran wrote:  1 > In article <3917E220.FCB75242@bornholm-gym.dk>,*8 >   Jonas Nielsen <Jonas-Nielsen@bornholm-gym.dk> wrote:2 > > i want a VAX and i have been offered some used
 > > VAXen: > ...DA > > And finally and very important :-), what should i pay for it?  > E > FWIW, a UK surplus dealer has just _offered_ me 200 UK pounds for aFI > 4000/60 plus some other bits. They will expect to _sell_ it for 5 to 10N > times that price.F >RI > I haven't accepted the 200, as for that little I'd rather _give_ it toRI > a hobbyist. So if you fancy a trip to London... (as I'm not prepared to  > post it).  >* > Chris* >*( > Sent via Deja.com http://www.deja.com/ > Before you buy.*   --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukd  A I speak for myself only and my views in no way represent those ofs MedAS or the BBC.    ------------------------------  + Date: Tue, 09 May 2000 16:07:35 +0000 (   )S3 From: Christopher Smith <chriss@Mufasa.pubserv.com>N Subject: Re: Which VAX to buy?J Message-ID: <Pine.LNX.4.05.10005091559010.14831-100000@Mufasa.pubserv.com>  ( On Tue, 9 May 2000, Jonas Nielsen wrote:  C > Im a young UNIX-freak, who has become a bit interested in the VMSCJ > operating system :-). So, i want a VAX and i have been offered some used > VAXen:  F That might have been me a few years ago, actually.  I'm less of a unixJ freak now, and more well-balanced as far as operating systems. (Read that:* I kind of like anything except windows...)  # > Digital VAXstation 3100/M76 - SPX+ > Digital VAXstation 4000 - 604 > Digital VAXserver 3100 (Scsi disk Ext. SCSI udtag)  7 > and a Digital Storage Expansion (99 MB Disk + CD-ROM)m  E > Basically, i just want to learn OpenVMS, DECwindows a little bit of I > system administration, and perhaps some programming. I thought it wouldaD > be a good idea to buy the Storage Expansion as well, so that i can? > install programs and newer releases of OpenVMS on the system.     J This is an easy choice for me.  I'd go after the 4000, since (I'm not sureG about this part) it's likely to be faster, and (I'm sure about this...)BH it's certainly not going to take up as much space.  They're a very light VAX.  F If you can get the extra box too, then I'd also consider that.  NormalH (such as they are) SCSI drives should work well on any of the VAXen thatJ you've listed, though, so it's not a requirement.  You could very well useH drives from some other source. (Unfortunately, my VAXStation 3100 has no3 original drives in it.  They've all been replaced.)r  J > So i ask you guys, (since i know nothing about VAX), which configuration. > would you suggest? The VS4000 or VS3100-M76?  8 So, as I was saying... I'd go after the VAXStation 4000.  ? > And finally and very important :-), what should i pay for it?i  E It depends on ram, and disk space, and how much you really want it ;)a  & I've heard prices from $50 to $200 US.   Regards,   Chrish  O ===============================================================================i@ "My two cents"			(http://rootworks.com/twocentsworth.cgi?128562)= Christopher Smith(chriss@pubserv.com)			Prgramer^W Programmer  Prime Synergy of Champaign, IL.N% -------------------------------------SI "Where a calculator on the ENIAC is equipped with 18,000 vacuum tubes and H weighs 30 tons, computers in the future may have only 1,000 vacuum tubes; and weigh only 1.5 tons." -- Popular Mechanics, March 1949  O -------------------------------------------------------------------------------n   ------------------------------   Date: 9 May 2000 17:37:26 GMTs2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Which VAX to buy?6 Message-ID: <8f9icm$8n8$1@mailint03.im.hou.compaq.com>   In article <Pine.LNX.4.05.10005091559010.14831-100000@Mufasa.pubserv.com>, Christopher Smith <chriss@Mufasa.pubserv.com> writes:K :This is an easy choice for me.  I'd go after the 4000, since (I'm not surerH :about this part) it's likely to be faster, and (I'm sure about this...)I :it's certainly not going to take up as much space.  They're a very lightO :VAX.P  H   Um, I suspect there might be a little confusion here.  The VAXstation I   4000 VLC series -- the "pizza box" VAXstation -- is definitely smaller T.   and lighter than the VAXstation 3100 series.  H   The VAXstation 4000 model 60 (and the rather physically similar model J   90 series) are roughly between the size and weight of the larger (three H   horizontal rows of vents along the side) and the smaller (two rows of F   vents) enclosures used on the members of the VAXstation 3100 series.  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Tue, 9 May 2000 21:01:34 +0800! From: "ƥ" <wanglimin@2911.net>s0 Subject: Re: Why  RZ28M can't be used on VAX3100* Message-ID: <8f924j$ju7$1@info.bta.net.cn>   Thank you .e  : you mean this disk can't be used as boot device on a 3100?   but how can i make use of it?p   ------------------------------   Date: 9 May 2000 13:44:01 GMTt2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)0 Subject: Re: Why  RZ28M can't be used on VAX31006 Message-ID: <8f94n1$1tb$1@mailint03.im.hou.compaq.com>  N In article <8f924j$ju7$1@info.bta.net.cn>, "ƥ" <wanglimin@2911.net> writes:  8   There is no such system as a "VAX 3100" I am aware of.  ; :you mean this disk can't be used as boot device on a 3100?P  F   3100?  The VAXstation 3100?  The VAXserver 3100?  The MicroVAX 3100?F   The DECstation 3100?  The DECstation 3100?  Some other 3100?   Each G   can have different requirements and restrictions, and the use of the eC   SPECIFIC system name is a CRITICAL factor in receiving an answer  E   correct for your particular system.  And as should be apparent from D   the above list, the "number" portion alone does not unambiguously H   identify the particular system.  (No offense intended -- this is just !   one of my standard "rants". :-)    :but how can i make use of it?  C   I will *assume* this is the older MicroVAX 3100 or the VAXstation H   3100 (any member) series.  If so, you can use disks larger than 1.073 D   GB as data disks, but these systems cannot reliably bootstrap fromE   (and more importantly, crash to) system disks larger than 1.073 GB.hH   Some details on this topic are in the OpenVMS FAQ, among other places.=   In particular, please see the OpenVMS FAQ section entitled:   J "VAX5.   What system disk size limit on the MicroVAX and VAXstation 3100?"  H   And please remember to acquire a copy of the FAQ (and then remember toH   skim through it) when you have a question -- many common questions are8   answered in the FAQ.  (Again, no offense is intended.)  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 09 May 2000 10:12:09 -0400 " From: Dan Sugalski <dan@sidhe.org>0 Subject: Re: Why  RZ28M can't be used on VAX31008 Message-ID: <4.3.1.0.20000509100840.00e39c40@24.8.96.48>  - At 09:01 PM 5/9/00 +0800, =C6=A5=C6=D5 wrote: ; >you mean this disk can't be used as boot device on a 3100?9   Correct.   >but how can i make use of it?  J Use it as a non-boot device. You can hang the thing off the system just=20K fine, as VMS can handle it. It's the low-level boot routines that can't.=20yK You're not in VMS quite yet then, and there are some restrictions in place=t =203# that are lifted once you've booted.-   					Dan  I --------------------------------------"it's like this"-------------------m2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evena;                                       teddy bears get drunk    ------------------------------  % Date: Tue, 09 May 2000 10:52:32 -0400u" From: Dan Sugalski <dan@sidhe.org>0 Subject: Re: Why  RZ28M can't be used on VAX31008 Message-ID: <4.3.1.0.20000509105048.02412750@24.8.96.48>  - At 08:35 AM 5/9/00 -0600, Dan O'Reilly wrote:e  ) >At 08:12 AM 5/9/00 , Dan Sugalski wrote:W/ >>At 09:01 PM 5/9/00 +0800, =C6=A5=C6=D5 wrote:b= >>>you mean this disk can't be used as boot device on a 3100?b >>
 >>Correct. >>  >>>but how can i make use of it? >>L >>Use it as a non-boot device. You can hang the thing off the system just=20K >>fine, as VMS can handle it. It's the low-level boot routines that can't.=i =20 I >>You're not in VMS quite yet then, and there are some restrictions in=20 + >>place that are lifted once you've booted.C >dK >Actually, you should be able to boot off of it, provided everything is in=t  the >first 1gb of disk space.t  K Yeah, but that's mildly tricky and just begging for problems at some point=r =20eK later when the system gets upgraded. Not the sort of thing to recommend to=t =20,I someone new to VMS. (Though didn't someone burn new boot ROMs for this=20aK thing that lifted that limit? I seem to remember that, though I can't find=r =20  the references anywhere)   					Dan  I --------------------------------------"it's like this"-------------------92 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and even$;                                       teddy bears get drunk4   ------------------------------  % Date: Tue, 09 May 2000 08:58:08 -0600 % From: Dan O'Reilly <dano@process.com>a0 Subject: Re: Why  RZ28M can't be used on VAX3100B Message-ID: <4.2.0.58.20000509085739.00a9b340@pop.clsp.uswest.net>  ( At 08:52 AM 5/9/00 , Dan Sugalski wrote:. >At 08:35 AM 5/9/00 -0600, Dan O'Reilly wrote: >s* >>At 08:12 AM 5/9/00 , Dan Sugalski wrote:0 >>>At 09:01 PM 5/9/00 +0800, =C6=A5=C6=D5 wrote:> >>>>you mean this disk can't be used as boot device on a 3100? >>>s >>>Correct.  >>>I! >>>>but how can i make use of it?c >>>tK >>>Use it as a non-boot device. You can hang the thing off the system just=l =20tL >>>fine, as VMS can handle it. It's the low-level boot routines that can't.= =20 J >>>You're not in VMS quite yet then, and there are some restrictions in=20, >>>place that are lifted once you've booted. >>L >>Actually, you should be able to boot off of it, provided everything is in=  the >>first 1gb of disk space. > L >Yeah, but that's mildly tricky and just begging for problems at some point= =20 L >later when the system gets upgraded. Not the sort of thing to recommend to= =20BJ >someone new to VMS. (Though didn't someone burn new boot ROMs for this=20L >thing that lifted that limit? I seem to remember that, though I can't find= =20A >the references anywhere)u  I I don't remember if somebody did it for the 3100, I know that it was done) for the 4000VLC.     ------I +-------------------------------+---------------------------------------+eI | Dan O'Reilly                  |                                       | I | Principal Engineer            |  "Time flies like an arrow.  Fruit    |bI | Process Software Corporation  |   flies like a banana."               |lI | http://www.process.com        |                    -- Groucho Marx    | I +-------------------------------+---------------------------------------+    ------------------------------  % Date: Tue, 09 May 2000 08:35:56 -0600 % From: Dan O'Reilly <dano@process.com>y0 Subject: Re: Why  RZ28M can't be used on VAX3100B Message-ID: <4.2.0.58.20000509083526.00ac1c10@pop.clsp.uswest.net>  ( At 08:12 AM 5/9/00 , Dan Sugalski wrote:. >At 09:01 PM 5/9/00 +0800, =C6=A5=C6=D5 wrote:< >>you mean this disk can't be used as boot device on a 3100? >-	 >Correct.n >o >>but how can i make use of it?- > K >Use it as a non-boot device. You can hang the thing off the system just=20 L >fine, as VMS can handle it. It's the low-level boot routines that can't.=20L >You're not in VMS quite yet then, and there are some restrictions in place= =20 $ >that are lifted once you've booted.  J Actually, you should be able to boot off of it, provided everything is in=  the first 1gb of disk space.     ------I +-------------------------------+---------------------------------------+aI | Dan O'Reilly                  |                                       |fI | Principal Engineer            |  "Time flies like an arrow.  Fruit    |eI | Process Software Corporation  |   flies like a banana."               |I | http://www.process.com        |                    -- Groucho Marx    |cI +-------------------------------+---------------------------------------+    ------------------------------   Date: 9 May 2000 17:48:56 GMT-2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)0 Subject: Re: Why  RZ28M can't be used on VAX31006 Message-ID: <8f9j28$8up$1@mailint03.im.hou.compaq.com>  j In article <4.2.0.58.20000509083526.00ac1c10@pop.clsp.uswest.net>, Dan O'Reilly <dano@process.com> writes:H :Actually, you should be able to boot off of it, provided everything is   :in the first 1gb of disk space.  I   Booting isn't the really interesting part, since it either boots or it eK   doesn't.  Crashing, on the other hand, is rather more interesting, as it e)   either corrupts the disk or it doesn't.o  M   If you know what you are doing, then you can likely keep from getting into -I   trouble with the larger disks (above 1.073 GB), but if you're not very oJ   careful, an OpenVMS upgrade or an ECO kit can push the dump file or the G   page file above the threshold, and then things can get "interesting".m  >N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  + Date: Tue, 09 May 2000 08:21:35 -0700 (PDT)g! From: Tom Linden <tom@kednos.com>g/ Subject: Re: Why RZ28M can't be used on VAX31000G Message-ID: <Pine.ULT.3.91.1000509081951.23690Y-100000@gunn.kednos.com>M  ' On Tue, 9 May 2000, Dan Sugalski wrote:n  ' > Date: Tue, 09 May 2000 10:52:32 -0400 $ > From: Dan Sugalski <dan@sidhe.org> > To: Info-VAX@Mvb.Saic.Com!1 > Subject: Re: Why RZ28M can't be used on VAX3100  >=20/ > At 08:35 AM 5/9/00 -0600, Dan O'Reilly wrote:a >=20+ > >At 08:12 AM 5/9/00 , Dan Sugalski wrote:p1 > >>At 09:01 PM 5/9/00 +0800, =C6=A5=C6=D5 wrote:t? > >>>you mean this disk can't be used as boot device on a 3100?n > >> > >>Correct. > >>" > >>>but how can i make use of it? > >>L > >>Use it as a non-boot device. You can hang the thing off the system just= =20aL > >>fine, as VMS can handle it. It's the low-level boot routines that can't= .=20K > >>You're not in VMS quite yet then, and there are some restrictions in=20s- > >>place that are lifted once you've booted.a > > L > >Actually, you should be able to boot off of it, provided everything is i= n the  > >first 1gb of disk space.o >=20L > Yeah, but that's mildly tricky and just begging for problems at some poin= t=20L > later when the system gets upgraded. Not the sort of thing to recommend t= o=20K > someone new to VMS. (Though didn't someone burn new boot ROMs for this=20cL > thing that lifted that limit? I seem to remember that, though I can't fin= d=20 > the references anywhere) >=20  J <moeller@gwdvms.dnet.gwdg.de>  actually modified the PROMs though I never= =20rK tried it out, but you can get the code from him and burn the PROMs yourself:  ! Curious to know how it works out.?   > =09=09=09=09=09Dan >=20K > --------------------------------------"it's like this"-------------------h4 > Dan Sugalski                          even samuraiA > dan@sidhe.org                         have teddy bears and even = >                                       teddy bears get drunk- >=20 >=20 >=20  A                __________________________________________________aA               /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/t@              /_/                                             /_/?             /_/     Tom Linden              PL/I Support    /_/5>            /_/    Kednos Corporation       OpenVMS and     /_/=           /_/   tel 831 373 7003          Tru64 Unix      /_/.<          /_/_____________________________________________/_/;         /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/n   ------------------------------  $ Date: Tue, 9 May 2000 13:28:46 -0400% From: "Brian Tillman" <tillman_brian>e, Subject: Re: wich list: DIRECTORY limitation$ Message-ID: <39184b02$1@news.si.com>   >> DIRECTORY >>
 >>   /EXCLUDEn >>$ >>         /EXCLUDE=(filespec[,...]) >>H >>      Excludes the specified files from the DIRECTORY command. You canG >>      include a directory but not a device in the file specification. F >>      The asterisk (*)  and the percent sign (%) wildcard charactersF >>      are allowed in the file specification. However, you cannot useF >>      relative version numbers to exclude a specific version. If you< >>      specify only one file, you can omit the parentheses. >>F >> Is there hope that the two restrictions above will be lifted in the >> future?  Ditto for BACKUP:, >.- >Does anyone have a good workaround for this.l  . Here's what I do (for the device part, anyway)  - $ define/user sys$disk: whateverdiskyou want:r8 $ purge/excl=(file,file,file) whateverdiskyouwant:[*...]  8 To determine how much space a purge would regain, I use: $ @gain mydisk:[mydir...] /log2 MYDISK:[MYDIR]ALIASES.SMA;1 is a previous version.%    Deleting it will save 1459 blocks..< MYDISK:[MYDIR]DECSET$ENVMGR_ERR.LOG;1 is a previous version.!    Deleting it will save 1 block.m< MYDISK:[MYDIR]DECSET$ENVMGR_OUT.LOG;1 is a previous version.!    Deleting it will save 1 block.s4 MYDISK:[MYDIR]EXCEED.LOG;1206 is a previous version.!    Deleting it will save 1 block.n4 MYDISK:[MYDIR]EXCEED.LOG;1205 is a previous version.!    Deleting it will save 1 block. 4 MYDISK:[MYDIR]EXCEED.LOG;1204 is a previous version.!    Deleting it will save 1 block.a  6 A total of 6 files can be deleted, saving 1464 blocks.    @ $! GAIN.COM - Report how much space one would gain from a purge. $       verify = 'f$verify( 0 )e $       set noon $! $ getp1:& $       if p1 .nes. "" then goto gotp13 $       read/prompt = "_Directory: " sys$command p1g $       goto getp1 $! $ gotp1:B $       if f$locate( "/", p1 ) .eq. f$length( p1 ) then goto getp2 $       p2 = p1y $       p1 = ""i $       goto getp1 $! $ getp2:+ $       if p2 .eqs. "" then goto docommandssG $       if f$locate( "/", p2 ) .ne. f$length( p2 ) then goto docommandsa $       temp = p1a $       p1 = p2c $       p2 = templ $!
 $ docommands:u $       p2 := 'p2b $       log = 0a8 $       if f$extract( 0, 2, p2 ) .eqs. "/L" then log = 1 $       totalsize = 0y $       totalfiles = 0 $       previousfile = ""n $! $ nextfile: . $       fullfile = f$search( "''p1'*.*;*", 1 ). $       if fullfile .eqs. "" then goto summary3 $       currentfile = f$element( 0, ";", fullfile ).3 $       if currentfile .eqs. ";" then goto nextfilet: $       if currentfile .eqs. previousfile then goto gather" $       previousfile = currentfile $       goto nextfileA $!	 $ gather: # $       totalfiles = totalfiles + 1)7 $       size = f$file_attributes( fullfile, "alq" ) + 1s$ $       totalsize = totalsize + size' $       if .not. log then goto nextfile2/ $       say fullfile, " is a previous version."=C $       say f$fao( "   Deleting it will save !ZL block!%S.", size )w $       goto nextfilew $!
 $ summary: $       say ""C $       phrase = "A total of !ZL file!%S can be deleted, saving !ZLr
 block!%S."2 $       say f$fao( phrase, totalfiles, totalsize )+ $       exit 1 + ( 0 * f$verify( verify ) )q     --  B  Brian Tillman                   Internet: tillman_brian at si.comB  Smiths Industries, Inc.                   tillman at swdev.si.com>  3290 Patterson Ave. SE, MS      Addresses modified to prevent=  Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"-9         This opinion doesn't represent that of my companyf   ------------------------------   End of INFO-VAX 2000.259 ************************