1 INFO-VAX	Wed, 02 Nov 2005	Volume 2005 : Issue 612       Contents: %SYSTEM-F-ILLEGAL_SHADOW error% Re: Advanced Server Performance Issue % Re: Advanced Server Performance Issue  Determining SCSI settings  Re: how to break cluster/ Re: HP : Massive strike and protest march today / Re: HP : Massive strike and protest march today / Re: HP : Massive strike and protest march today / Re: HP : Massive strike and protest march today G Newbie questions (NFS performance, mounting disks, getting ZIP to work) K Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work) K Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work) K Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work) K Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work)  OT: Fiorina still up to things" Re: OT: Fiorina still up to things Re: RF/RZ26 disk question  Re: RF/RZ26 disk question % Re: USB SUPPORT ON DS10 ALPHA oPENvms 9 Re: Why I will vote against the Encompass Bylaws Revision 5 Will Digital's abandonned software ever go "public" ? 9 Re: Will Digital's abandonned software ever go "public" ? 9 Re: Will Digital's abandonned software ever go "public" ? 9 Re: Will Digital's abandonned software ever go "public" ? 9 Re: Will Digital's abandonned software ever go "public" ?  Re: Writing an OpenVMS ACPP Yikes!! -  an INFO-VAX  post with technical content  - beware!  - RE: Writing anD [Fwd: GT.M on Alpha/AXP being released as open source free software]  F ----------------------------------------------------------------------   Date: 2 Nov 2005 10:27:18 -0700 1 From: nothome@spammers.are.scum (Malcolm Dunnett) ' Subject: %SYSTEM-F-ILLEGAL_SHADOW error , Message-ID: <o0+xlKWu6dzy@malvm9.mala.bc.ca>  7 I'm running VMS 7.3-2 on a cluster of two ES40 servers.   4 Since moving to this configuration I've noticed that5 occasionally ( but not reliably reproducibly ) when a ( program exits I get the following error:  5 %SYSTEM-F-ILLEGAL_SHADOW, illegal formed trap shadow, L Imask=0111510C, Fmask=0000001B, summary=0B, PC=000000000000005B, PS=0000001B  2   Improperly handled condition, image exit forced.1     Signal arguments:   Number = 0000000000000003 1                         Name   = 00000000000005B4 1                                  000000000111510C 1                                  000000000000001B        Register dump:J     R0  = 0000000001735488  R1  = 0000000000000002  R2  = 0000000000000000J     R3  = 0000000000000000  R4  = 0000000000000000  R5  = 0000000000000000J     R6  = 0000000000000000  R7  = 0000000000000000  R8  = 0000000000000000J     R9  = 0000000000000000  R10 = 0000000000000000  R11 = 0000000000000000J     R12 = 0000000000000000  R13 = 000000007AE09140  R14 = 00000000017354A8J     R15 = 0000000003842984  R16 = 000000000111510B  R17 = 000000000111510CJ     R18 = 000000000010ACA1  R19 = 0000000000000000  R20 = 0000000000000000J     R21 = 000000000000000F  R22 = 0000000000000000  R23 = 4024000000000000J     R24 = 0000000000000001  R25 = 0000000000000002  R26 = 000000000111510BJ     R27 = 000000000000005B  R28 = 000000000000001B  R29 = 0000000000000000J     SP  = 000000007AE08FD0  PC  = 000000000111510C  PS  = 100000000000001B  $ The HELP/MESSAGE isn't very helpful:  L Explanation:  The instruction sequence does not obey the rules stated in theL                 Alpha Architecture Reference Manual for software completion.I                 It is impossible for system software to complete the IEEE 4                 floating-point arithmetic operation.  D   User Action:  Recompile the program to enable software completion.  C I don't believe it's my code that is causing this and I'm certainly - not doing any IEEE floating-point arithmetic.   C The only reference I could find on Google to this error pertains to G Oracle Rdb, which we don't use - though these programs do use "Classic" H Oracle. We converted the programs to the Oracle 9.2 client when we movedG to these new servers so it's certainly conceivable that it's the Oracle G client code that is causing the problem. There is a reference on Oracle G Metalink to someone getting a similar error using the Oracle DBCA tool.   I This doesn't appear to be a big problem as it never occurs any time other F that at image exit, but of course unexplained errors always bother me.  J Has anyone else seen this and/or have any explanation for why it might be 
 happening?   ------------------------------   Date: 2 Nov 2005 04:36:55 -0800 % From: "Safir" <axica_nopub@yahoo.com> . Subject: Re: Advanced Server Performance IssueC Message-ID: <1130935015.402714.293140@z14g2000cwz.googlegroups.com>    G=F6tz Ulrich wrote:K > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= L =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=L =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  >  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:05.57  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX H > %LICENSE-E-NOAUTH, DEC PWBADLICENSE use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA08.00 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA08.01 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA08.02 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA08.03 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA09.00 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA09.01 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA09.02 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.04  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA09.03 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  > : > %%%%%%%%%%%  OPCOM  30-OCT-2005 21:14:06.05  %%%%%%%%%%%# > Message from user SYSTEM on ULRIX J > %LICENSE-E-NOAUTH, DEC PWLMXXXCA10.00 use is not authorized on this nodeF > -LICENSE-F-NOLICENSE, no license is active for this software product3 > -LICENSE-I-SYSMGR, please see your system manager  >=20  * Where did you get these licences from ?=20 They should not exist.   ------------------------------   Date: 2 Nov 2005 16:54:26 +0100 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER). Subject: Re: Advanced Server Performance Issue* Message-ID: <4368ef42@news.langstoeger.at>  k In article <1130935015.402714.293140@z14g2000cwz.googlegroups.com>, "Safir" <axica_nopub@yahoo.com> writes: ( >Where did you get these licences from ?   Nowhere.   >They should not exist.   C Indeed. But the license checker has them builtin (for years now)...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Wed, 02 Nov 2005 09:21:57 -0700 + From: Mark Berryman <mark@theberrymans.com> " Subject: Determining SCSI settings% Message-ID: <43687726$1@mvb.saic.com>   G How does one tell what type of bus and speed have been negotiated by a  D SCSI controller?  For example, is the SCSI bus running in LVD or SE C mode?  Are the devices running at 160MB or do some negotiate at 40?   I I used to get some indication of this at bootup time but, at least on my  H V8.2 system, I no longer see any SCSI information at startup.  Is there F a data structure anywhere that stores this information, or is there a B way to query the controller to find out what settings it is using?  
 Mark Berryman    ------------------------------   Date: 2 Nov 2005 17:35:23 GMT ) From: Hans Bachner <Hans@Bachner.priv.at> ! Subject: Re: how to break cluster 0 Message-ID: <dkasnl.8s.1@usenet.bachner.priv.at>  / JF Mezei <jfmezei.spamnot@teksavvy.com> wrote:     <snip>   > , > To take a node out of a cluster, you can:  > H > MC SYSGEN SYSGEN> USE CURRENT SYSGEN> SET VAXCLUSTER = 0 SYSGEN> WRITE
 > CURRENT  >  > D > Then reboot, and the machine will be out of the cluster. If you doD > that to all machines in the cluster, the cluster will no longer be? > active. But setting the parameters back on will re-enable it    D But *DON'T* do this without reading the rest of JFs note. Nodes in aH cluster share the system disk in many/nost cases, and just following the@ above advice will trash your system disks within a few seconds.    So read on:    F > There are big caveats to this: If node B relies on access to drives I > served by node A, then node B will fail because it will no longer have   > access to A's drives.  > I > If there are drives that are shared at the hardware level (shared SCSI  F > for instance), then there will not be any lock coordination between B > drives and you will get corruption in files if both nodes try to$ > access the file at the same time.  > H > Also note that a node may rely on another node's system disk to boot. H > (a satellite node), and when you take that node out of the cluster. IfC > so, you need to change the nodes's default boot device to its own E > local disk, as well as ensuring that its onw local disk has its own D > copy of VMS (and this entails copying all configuration files fromH > that node's SYS$SPECIFIC tree from the server's disk to the node's own? > disk so when it boots "alone", it can see all its own files.   >    Hans.    ------------------------------   Date: 2 Nov 2005 07:35:53 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 8 Subject: Re: HP : Massive strike and protest march today3 Message-ID: <eX8JE$vTAdf7@eisner.encompasserve.org>   V In article <3sqmk8Fpfi4nU2@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: > C > While I can't provide any real evidence at this point, I would be > > willing to bet the Hubble was manufactured by union workers.      Guess again.    ------------------------------   Date: 2 Nov 2005 14:13:05 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)8 Subject: Re: HP : Massive strike and protest march today+ Message-ID: <3srvrhFp8vqdU1@individual.net>   C In article <1130900680.086336.221320@g14g2000cwa.googlegroups.com>, ' 	"AEF" <spamsink2001@yahoo.com> writes:  > Bill Gunshannon wrote:. >> In article <43681D92.A4E5205D@comcast.net>,8 >> 	David J Dachtera <djesys.nospam@comcast.net> writes: >> >E >> >> The Hubble did pretty well after the correcting lens was added.  >> >+ >> > It had to be fixed. The defense rests.  >>D >> While I can't provide any real evidence at this point, I would be? >> willing to bet the Hubble was manufactured by union workers.  >  > & > OBJECTION! OBJECTION your honor. :-) > B > Come on, Bill. I generally agree with most of your criticisms of& > unions, but your bet is just a guess  J I will agree that it may be a cheap shot, but based on my years of workingG in government contracting I also know the majority of them employ union J workers more than non-union if for no reason beyond they tend to be largerE corporations (and Perkin-Elmer was no slouch in that department) with : the necessary critical mass of employees to get unions in.   > D > Anyway, the company was Perkin-Elmer and the error was done by the< > optical team. Do any optical engineers belong to a union?   @ Do you actually believe the engineers manufactured the lens?  DoG cpu engineers actually make the wafers at Intel?  An engineer (actually F a team of them) would have designed the lens and probably defined the G process for it's manufacture, but in the end the actual work would have E been done by technicians who were very likely union.  We have optical A companies around here and the unions are well represented.  Their A actions have resulted in at least one closing down completely and  moving overseas.  I >                                                           I did a brief  > Google search for  > 5 >    Hubble "spherical aberration" Perkin-Elmer union  > " > but didn't find anything useful.  < And what?  You expected to find a story where the union took4 responsibility for the problem?  Fat chance of that.   > F > Also, the Hubble is a lot more than the objective mirror and I don'tF > recall reading about any problems with the rest of the Hubble, whoseG > non-objective mirror parts greatly outnumber the mirror part (many to  > one).   F Yeah, and the position of the gas tank on the Pinto was only one small( factor in the overall design of the car.  A >       And the Hubble has performed spectacularly well since the @ > corrective optics were added. The workers who built the HubbleB > certainly deserve a fair portion of the credit, be they union or > otherwise.  D Credit for what?  Doing their job?  They wre paid for that.  If theyE were union, they were very likely paid handsomly. But the mistake is  5 something else, that's not what they were paid to do.   * But the main point is we keep hearing this<      union==competent & non-union=={incompetent|junkie|hick} It just ain't so!!!   C Unions are also legally allowed to do things that if you as private @ individual did would land you in jail for racketeering or worse.D Some people don't see this as a good thing.  And, unless you believe5 "The end justifies the means", it's just plain wrong.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 2 Nov 2005 14:20:04 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)8 Subject: Re: HP : Massive strike and protest march today+ Message-ID: <3ss08kFp8vqdU3@individual.net>   3 In article <eX8JE$vTAdf7@eisner.encompasserve.org>, > 	koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:X > In article <3sqmk8Fpfi4nU2@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >>  D >> While I can't provide any real evidence at this point, I would be? >> willing to bet the Hubble was manufactured by union workers.  >  >    Guess again.   K "Carl Holder, shop steward at PerkinElmer, said unions had a responsibility K  to send out a positive message. "We are there and involved in everything""    Kinda looks union to me!!    bill      --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------   Date: 2 Nov 2005 06:35:34 -0800 $ From: "AEF" <spamsink2001@yahoo.com>8 Subject: Re: HP : Massive strike and protest march todayC Message-ID: <1130942134.166430.322440@g49g2000cwa.googlegroups.com>    Bill Gunshannon wrote:E > In article <1130900680.086336.221320@g14g2000cwa.googlegroups.com>, ) > 	"AEF" <spamsink2001@yahoo.com> writes:  > > Bill Gunshannon wrote:0 > >> In article <43681D92.A4E5205D@comcast.net>,: > >> 	David J Dachtera <djesys.nospam@comcast.net> writes: > >> >G > >> >> The Hubble did pretty well after the correcting lens was added.  > >> >- > >> > It had to be fixed. The defense rests.  > >>F > >> While I can't provide any real evidence at this point, I would beA > >> willing to bet the Hubble was manufactured by union workers.  > >  > > ( > > OBJECTION! OBJECTION your honor. :-) > > D > > Come on, Bill. I generally agree with most of your criticisms of( > > unions, but your bet is just a guess > L > I will agree that it may be a cheap shot, but based on my years of workingI > in government contracting I also know the majority of them employ union L > workers more than non-union if for no reason beyond they tend to be largerG > corporations (and Perkin-Elmer was no slouch in that department) with < > the necessary critical mass of employees to get unions in. > > F > > Anyway, the company was Perkin-Elmer and the error was done by the= > > optical team. Do any optical engineers belong to a union?  > B > Do you actually believe the engineers manufactured the lens?  DoI > cpu engineers actually make the wafers at Intel?  An engineer (actually G > a team of them) would have designed the lens and probably defined the I > process for it's manufacture, but in the end the actual work would have G > been done by technicians who were very likely union.  We have optical C > companies around here and the unions are well represented.  Their C > actions have resulted in at least one closing down completely and  > moving overseas.  ? It wasn't the design that was flawed. It wasn't the workers who E manufactured the lens who were at fault. It was the optical engineers F who three times ignored signes that the mirror was flawed. Testing andF correcting is a normal part of the manufacturing of telescope mirrors.+ Therefore, the fault lies with the testers.    See   -    <http://www.uoguelph.ca/~ebaig/brian.html>    for details.  F Additionally, the mirror had to made very precise specs. We're talking? about making a large glass surface to a specified shape with no G deviations larger than probably a 1/4-wavelength of green light or even E less! This is a difficult job that anyone can easily mess up -- union  or not.    > K > >                                                           I did a brief  > > Google search for  > > 7 > >    Hubble "spherical aberration" Perkin-Elmer union  > > $ > > but didn't find anything useful. > > > And what?  You expected to find a story where the union took6 > responsibility for the problem?  Fat chance of that.  @ I didn't expect anything that specific. I thought if a union wasE involved, something might come up. Other stories putting the union at G fault could easily be posted. Actually, in fact, I did stumble across a D story on slashdot about AA union members working for Alaska AirlinesF complaining that management were instituting too many safety shortcutsG and about how one of their planes crashed as a result and that the NTSB G agreed with the union but the airline is still flying. But this is just F one particular post by one particular person. I don't know how true itF is. But I thought *something* like that or opposite of that might turnA up in such a search. If you find something useful in this debate,  please do tell!   H > > Also, the Hubble is a lot more than the objective mirror and I don'tH > > recall reading about any problems with the rest of the Hubble, whoseI > > non-objective mirror parts greatly outnumber the mirror part (many to 	 > > one).  > H > Yeah, and the position of the gas tank on the Pinto was only one small* > factor in the overall design of the car.   OK.    > C > >       And the Hubble has performed spectacularly well since the B > > corrective optics were added. The workers who built the HubbleD > > certainly deserve a fair portion of the credit, be they union or > > otherwise. > F > Credit for what?  Doing their job?  They wre paid for that.  If theyF > were union, they were very likely paid handsomly. But the mistake is7 > something else, that's not what they were paid to do.   C Credit for doing their job well. We still don't know how much union @ involvement there was. My main point was that this is not a good! example to support David's point.    > , > But the main point is we keep hearing this> >      union==competent & non-union=={incompetent|junkie|hick} > It just ain't so!!!   D I didn't mean to imply otherwise. Again, my personal experience with' union workers has been mostly negative.   E > Unions are also legally allowed to do things that if you as private B > individual did would land you in jail for racketeering or worse.F > Some people don't see this as a good thing.  And, unless you believe7 > "The end justifies the means", it's just plain wrong.  >    ------------------------------   Date: 2 Nov 2005 01:19:00 -0800  From: sampsal@gmail.com P Subject: Newbie questions (NFS performance, mounting disks, getting ZIP to work)C Message-ID: <1130923140.465386.143900@g14g2000cwa.googlegroups.com>    Hi,   C I've managed to get VMS 7.3-1 running on my Alphaserver, and am now F trying to make it into a file server for my home network. But I've run into some problems:   E 1. NFS performance is not great, about 200 KBytes/sec on a  link that ? gets over 1Mbyte/sec over FTP. Is this normal? The machine is a E Alphaserver 4100 with dual 466 CPUs and 2 gigs of RAM. Can I increase ; this performance in any way? Is the TCPWARE NFS any faster?   E 2. How do I run UNZIP? I uploaded the EXE onto the Alpha from my OS X G box without problems. RUN UNZIP gives me the help screen, but RUN UNZIP  FOO.ZIP gives me the following:    ---- OUTPUT -----          $ run unzip.exe foo.zip B         %DCL-W-MAXPARM, too many parameters - reenter command with fewer parameters          \FOO\ ---- OUTPUT -----    What am I missing here? :)  E 3. Mounting drives. For some reason I can only export my system drive G via NFS, I think it's permissions/protection related. Here's the setup. E I've got my main system drive on DRA4: and another on DRA0:. DRA0: is - MOUNT/SYSTEM.  Here's some output from TCPIP:    ---- OUTPUT -----  TCPIP> show proxy   ; VMS User_name     Type      User_ID    Group_ID   Host_name 3 SAMPSA            OND           501         501   * 3 TCPIP$NFS         OND             0           1   * 3 TCPIP$NOBODY      OND            -2          -2   *    TCPIP> show map  Dynamic Filesystem Map; Pathname                                Logical File System - /dra4                                   DRA4: - /dra0                                   DRA0:    TCPIP> show export  1 File System                             Host name 3 /dra0                                   10.0.1.3, * 3 /dra4                                   10.0.1.3, *  ---- OUTPUT -----   G (My UID/GID on the OS X box is 501/501, the /dra4 mount point mounts OK  on OS X, /dra0 doesn't).   Thanks in advance,   Sampsa   ------------------------------   Date: 2 Nov 2005 01:43:35 -0800  From: dooleys@snowy.net.auT Subject: Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work)C Message-ID: <1130924615.665766.305330@g49g2000cwa.googlegroups.com>   : 1 There is a section in the tcp/ip services management doc-    http://h71000.www7.hp.com/doc/tcpip55.html ,    titled "Improving NFS Server Performance" 2 Make it a "foreign" command     put in your login.com1    unzip:==$unzip.exe (if unzip is in sys$system) #    or unzip:==$disk:[path]unzip.exe 	 3 no idea  Phil   ------------------------------   Date: 2 Nov 2005 11:35:50 +0100 . From: huber@NOBODY-mppmu.mpg.de (Joseph Huber)T Subject: Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work)+ Message-ID: <VQVZN3ibtCKF@vms.mppmu.mpg.de>   ] In article <1130923140.465386.143900@g14g2000cwa.googlegroups.com>, sampsal@gmail.com writes:  > G > 3. Mounting drives. For some reason I can only export my system drive I > via NFS, I think it's permissions/protection related. Here's the setup. G > I've got my main system drive on DRA4: and another on DRA0:. DRA0: is / > MOUNT/SYSTEM.  Here's some output from TCPIP:  >  > I > (My UID/GID on the OS X box is 501/501, the /dra4 mount point mounts OK  > on OS X, /dra0 doesn't).  J Switch on operator messages, they show NFS messages, and wether it mounts F successfully. Might be mount is o.k. on the VMS side, but Unix reportsM simply "I/O error": it might be due to the protection of DRA0: root directory D (dra0:[000000]000000.DIR). Is it readable by the proxy user (if it'sA user mounted on Unix), or root (if root mounted) or tcpip$nobody. N In the root mount case, needs a proxy from root to an account which is able to access the root directory.    --  @    Joseph Huber , Muenchen,Germany:  http://www.huber-joseph.de/   ------------------------------   Date: 2 Nov 2005 07:37:43 -0600 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) T Subject: Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work)3 Message-ID: <twt1xlMJspuh@eisner.encompasserve.org>   ] In article <1130923140.465386.143900@g14g2000cwa.googlegroups.com>, sampsal@gmail.com writes:  >  > What am I missing here? :) >   %    You _really_ need to read the FAQ.    ------------------------------   Date: 2 Nov 2005 09:20:24 -0800  From: sampsal@gmail.com T Subject: Re: Newbie questions (NFS performance, mounting disks, getting ZIP to work)C Message-ID: <1130952024.683123.101400@g47g2000cwa.googlegroups.com>   F Yeah, sorry. I posted after going through the docset for about 5 hoursF yesterday. I've ordered a few basic books on VMS admining and use fromB Amazon this afternoon. I did mark the thread Newbie to warn people1 about the rather RTFMesque nature of the queries.    Again, no offence intended.    Sampsa   ------------------------------  % Date: Wed, 02 Nov 2005 12:01:36 +0100  From: S <soterroatyahoodotcom>' Subject: OT: Fiorina still up to things & Message-ID: <43689c8f$1@news1.ethz.ch>  = http://money.cnn.com/2005/09/09/news/newsmakers/case_fiorina/  Funny how ZiffDavis titled it:5 "Amazing Collection of Losers Hoping for Big Web Win" 3 http://www.eweek.com/article2/0,1895,1880058,00.asp   Losers, but with millions of $$.   S    ------------------------------   Date: 2 Nov 2005 12:45:35 +0100 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)+ Subject: Re: OT: Fiorina still up to things * Message-ID: <4368b4ef@news.langstoeger.at>  G In article <43689c8f$1@news1.ethz.ch>, S <soterroatyahoodotcom> writes: > >http://money.cnn.com/2005/09/09/news/newsmakers/case_fiorina/  6 Carly and HealthCare ? Going in touch with VMS again ?? Or should we fear that VMS is losing the health business, too ?    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 2 Nov 2005 09:07:28 -0800 # From: "H Vlems" <hvlems@freenet.de> " Subject: Re: RF/RZ26 disk questionB Message-ID: <1130951248.507256.41280@g47g2000cwa.googlegroups.com>  D Hi Phillip, you are quite right that the RZ26 is more useful in this= world as a SCSI drive. However as a hobbyist user it is quite C reasonable to implement exotic possibilities rather than those that F make sense (technically or business wise). I run DECnet over DSSI just to prove that it can be done. B The question is: can I just connect the RZ26-E to DSSI and will itG autodetect that or do I need one or more jumpers to make that work. The C DSSI bus connector is physically identical to the SCSI connector so D that is not the problem. Neither am I worried in damaging the drive,/ but I'd rather keep my VAX 4000-100A running...    Hans   ------------------------------  % Date: Wed, 02 Nov 2005 18:43:28 +0100 3 From: Michael Unger <spam.to.unger@spamgourmet.com> " Subject: Re: RF/RZ26 disk question+ Message-ID: <3sscc5FpsikmU1@individual.net>   % On 2005-11-02 18:07, "H Vlems" wrote:    > [...] D > The question is: can I just connect the RZ26-E to DSSI and will itI > autodetect that or do I need one or more jumpers to make that work. The E > DSSI bus connector is physically identical to the SCSI connector so F > that is not the problem. Neither am I worried in damaging the drive,1 > but I'd rather keep my VAX 4000-100A running...   G AFAIR the mechanics of the drive are the same for SCSI and DSSI but the F controller board is a totally different one -- there is *no* jumper to' change from SCSI to DSSI or vice versa.   F Also AFAIR DSSI is similar to SCSI-1 but with *active* bus terminationE which explains the maximum length of 25 meters for a DSSI bus. And of ) course, the bus protocol is DEC-specific.    Michael    --  ; Real names enhance the probability of getting real answers. 5 My e-mail account at DECUS Munich is no longer valid.    ------------------------------   Date: 2 Nov 2005 13:37:44 GMT 2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>. Subject: Re: USB SUPPORT ON DS10 ALPHA oPENvms? Message-ID: <DTiotGxQ0bj6-pn2-BYp788pLIFhi@dave2_os2.home.ours>   3 On Tue, 1 Nov 2005 06:17:58 UTC, "Dave Weatherall"  ! <djw-nothere@nospam.nohow> wrote:   3 > On Sun, 30 Oct 2005 23:11:02 UTC, Forrest Kenney    > <Forrest.Kenney@hp.com> wrote: > 
 > > Peter, > > @ > > 	DNDRIVER was not done to support FAT formatted drives.  It G > > was done to support USB DVD's.  There are systems in the pipe line   > > that will need it. > > @ > > 	I keep hoping some person with a need for FAT support will J > > get the MTools from LINUX ported and working.  It has really complete E > > FAT support.  EFI$CP just needs to be good enough for OpenVMS to  J > > populate and update the FAT partition for EFI.  I don't have the time J > > for MTools, my winter weekends will be spent adding more examples for 
 > > UGDRIVER.  > G > A colleague at work has done a version. I'll check on the state when  : > we get back on Wednesday. We're having a long weekend...  F I checked with Dave this morning. His port dates from about 2000 when A we had Y2K problems with PCDISK. He'll post more himself when he   catches up on the newsgroup.   --   Cheers - Dave W.   ------------------------------  # Date: Wed, 02 Nov 2005 13:13:37 GMT / From: Clay M. Denton <denton@orison.dsserv.com> B Subject: Re: Why I will vote against the Encompass Bylaws Revision8 Message-ID: <1pehm1hqpc3sed8g5hug7q5sgcmrreq7e2@4ax.com>  Z I never said anything about the event - I wasn't there - so I can't comment on it.  I saidW that Encompass has become a trade show company.  This year, well over 50% of our income Y came from trade show revenue.  And well over 50% of the traffic on the board's email list Z was concerning the trade show.  So - to the casual observer - we are a trade show company.  T We have had many other initiatives and good ideas that have been dropped for variousJ reasons.  Most of those constituted the "user group" portion of Encompass.  Y I would offer direct proof of all of this - but the non-diclosure agreements prohibit it.    Clay    9 On 1 Nov 2005 13:02:01 -0800, jbecker@ui.urban.org wrote:    >Clay M. Denton wrote:@ >> Related to this is the Encompass Board of Director elections. >>] >> I would personally (in other words - not with my director hat on) recommend voting against \ >> any incumbents - esp. the current president.  We need to regain a user group - as opposed[ >> to what Encompass has become - a trade show company.   We need people who still remember T >> who volunteers are - as opposed to just bringing in their buddies for "volunteer"W >> assignments.  We also need an open board that does not require its members to sign a ] >> non-disclosure agreement so that the board can't hardly talk among itself - much less with  >> the membership. >> >> Clay Denton > ( >I have to disagree with Clay's remarks. > H >As a sitting board member, it would be inappropriate for me to campaignE >for or against particular candidates, but I'll go as far as saying I H >disagree with Clay's recommendations about the incumbents. I'm proud of >the work the board has done.  > H >I attended HPTF, and I was part of the content selection process, so myF >first-hand experience is that there was a lot more to this conferenceG >than the trade show, and there was a lot more to Encompass involvement F >than the trade show. ALL of the Encompass volunteers involved in this? >conference served in the content selection process and various B >community activities -- content and community, which is what userE >groups are about. Encompass was also a full partner on the core team  >that managed the conference.  > G >I don't want to diminish the value of the trade show, however. As many G >attendees have indicated -- verbally as well as through their presence E >-- the trade show is an important and useful part of the conference. E >Encompass managed the trade show, and partnered with another HP user 0 >group, OVFI, in getting vendors to participate. > D >Personally, I'm impressed that HP, Encompass, and OVFI were able toE >work together to relocate and re-implement a technical conference on A >short notice (given that it was originally supposed to be in New F >Orleans in September). There were thousands of attendees, hundreds ofH >sessions and speakers, dozens of volunteers, and dozens of vendors, allD >of whom had to be taken through the change of time and place. I wasG >also gratified to see long lines of interested people at the Encompass  >membership booth. >  >Jim Becker  >Encompass Board of Directors $ >(The Urban Institute is my day job)   ------------------------------  % Date: Wed, 02 Nov 2005 05:10:50 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> > Subject: Will Digital's abandonned software ever go "public" ?+ Message-ID: <4368906E.BF313BF@teksavvy.com>   3 In the 1990s, Digital abandonned a lot of software.   G In some cases, some of the software originated from companies which are F now bankrupt (SoftPC on vax came from Insignia Solutions which doesn't seem to exist anymore).   9 There there is all the source code to the CDA converters.   D Will all this software and/or source ever make it to "public domain"B once the copyrights expire ? If so, how long before this starts toH happen ? Or can the owners continuously renew copyrights of old softwareE even though such software is no longer in development or maintained ?   D eg: how long after the last version of  a software was produced does4 that software no longer really belong to the owner ?   ------------------------------  # Date: Wed, 02 Nov 2005 11:19:38 GMT ! From: Nigel Barker <nigel@hp.com> B Subject: Re: Will Digital's abandonned software ever go "public" ?8 Message-ID: <s55hm1la64ao46fm9jrs7fu4ncmpm62o1n@4ax.com>  K On Wed, 02 Nov 2005 05:10:50 -0500, JF Mezei <jfmezei.spamnot@teksavvy.com>  wrote:  4 >In the 1990s, Digital abandonned a lot of software. > H >In some cases, some of the software originated from companies which areG >now bankrupt (SoftPC on vax came from Insignia Solutions which doesn't  >seem to exist anymore).  P Insignia still exists at www.insignia.com They sold SoftPC to FWB Software years+ ago. Now they do Java solutions for Telcos.   E >Will all this software and/or source ever make it to "public domain" C >once the copyrights expire ? If so, how long before this starts to I >happen ? Or can the owners continuously renew copyrights of old software F >even though such software is no longer in development or maintained ? > E >eg: how long after the last version of  a software was produced does 5 >that software no longer really belong to the owner ?   M It's an interesting question as copyright on a piece of music or written work O now expires 70 years after the death of the author. Assuming that it's the same J with computer software we can't expect expiration of any computer software" copyright for another few decades.   -- Nigel Barker Live from the sunny Cote d'Azur    ------------------------------  % Date: Wed, 02 Nov 2005 05:42:56 -0800 # From: "Tom Linden" <tom@kednos.com> B Subject: Re: Will Digital's abandonned software ever go "public" ?( Message-ID: <opszl8du0rzgicya@hyrrokkin>  D On Wed, 02 Nov 2005 11:19:38 GMT, Nigel Barker <nigel@hp.com> wrote:  G >> eg: how long after the last version of  a software was produced does 7 >> that software no longer really belong to the owner ? L > It's an interesting question as copyright on a piece of music or written   > workJ > now expires 70 years after the death of the author. Assuming that it's  
 > the sameE > with computer software we can't expect expiration of any computer   
 > software$ > copyright for another few decades.  F Software may be protected by more than copyright, e.g., Trade Secrets.   ------------------------------   Date: 2 Nov 2005 14:31:12 GMT ( From: bill@cs.uofs.edu (Bill Gunshannon)B Subject: Re: Will Digital's abandonned software ever go "public" ?+ Message-ID: <3ss0tgFp8vqdU4@individual.net>   + In article <4368906E.BF313BF@teksavvy.com>, 0 	JF Mezei <jfmezei.spamnot@teksavvy.com> writes:5 > In the 1990s, Digital abandonned a lot of software.  > I > In some cases, some of the software originated from companies which are H > now bankrupt (SoftPC on vax came from Insignia Solutions which doesn't > seem to exist anymore).  > ; > There there is all the source code to the CDA converters.  > F > Will all this software and/or source ever make it to "public domain" > once the copyrights expire ?    G Highly unlikely.  I have always been amazed at how much of the software F tied to previous research projects that were public fromt he beginningG have already been lost.  Being as one person holds all this source code F and there is no incentive to ever make it publicly available, it will,: in all liklihood, just disappear and be lost for all time.  E >                               If so, how long before this starts to  > happen ?     Never.  J >          Or can the owners continuously renew copyrights of old softwareG > even though such software is no longer in development or maintained ?   D They don't even have to do that.  They just don't release the source( code.  Or, worse still, they destroy it.   > F > eg: how long after the last version of  a software was produced does6 > that software no longer really belong to the owner ?  D How long does that old TV have to sit in your basement before you noE longer own it?  Copyright or not, there is nothing that ever requires : them to release the source to anything they currently own.   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Wed, 02 Nov 2005 08:53:00 -0800 ' From: David Mathog <mathog@caltech.edu> B Subject: Re: Will Digital's abandonned software ever go "public" ?+ Message-ID: <dkaqta$97g$1@naig.caltech.edu>    JF Mezei wrote: 5 > In the 1990s, Digital abandonned a lot of software.  >    That's an understatement.   F > Will all this software and/or source ever make it to "public domain" > once the copyrights expire ?  9 Who's going to care by then? Copyrights last a LONG TIME.   C Once upon a time I tried to get Pathworks/Mac released and it was a I nightmare.  There were tendrils of ownership going out through all sorts  I of defunct companies.  It became clear that even if Compaq (at the time)  D wanted to "do the right thing" (of which there was little evidence) I there were all sorts of problems doing so because they had lost track of  8 the owners of the various licensed parts of the product.  H This is, in my opinion, one of the primary reasons to avoid proprietary I software and go open source if it is in any way possible.  Open software  A doesn't go "poof" at the whim of the CEO du jour, but commercial  G software does.  Even if an open source project is left for dead it can  G be resurrected years later because the source code tends to sit around  / on sourceforge (or wherever) and not evaporate.    Regards,   David Mathog mathog@caltech.edu   ------------------------------  $ Date: Wed, 2 Nov 2005 18:36:09 +08003 From: "Richard Maher" <maher_rj@hotspamnotmail.com> # Subject: Re: Writing an OpenVMS ACP 1 Message-ID: <dka4td$g33$1@news-02.connect.com.au>    Hi Dan,   - > If I was going to write any significant new " > inner mode code, I'd do it in C.  H Ok, so either you don't care to discuss your reasons for choosing C overL Macro-32, or there just aren't any. In any event you certainly don't have toJ justify yourself to me. Tiger Woods wears Nike and Dan writes in C. ShouldF be enough for anybody, but here are a couple of reasons (excerpts from= sys$examples:uwss.c) why I personally don't like C for UWSSs:   C **      The OpenVMS VAX MACRO-32 example and the OpenVMS Alpha V1.0 D **      BLISS example used "DEFINE_SERVICE" macros in a manner whichE **      allowed declaration of kernel- and executive-mode routines in A **      separate statements, mixing of kernel- and executive-mode C **      routines in successive statements and automatic counting of F **      the numbers of both kinds of routines.  The macro capabilities? **      of C are limited, by comparison, so only the counts are B **      calculated (as opposed to hard-coded) here.  Specifically,E **      this example relies on sizeof() constructs to avoid having to F **      hard-code the numbers of routines, but still requires that allD **      executive-mode routines be declared in a single declaration,A **      and that all kernel-mode routines be declared in a single  **      declaration.  
 and this. . .   8 **      . . .ps_temp should not, and likely will not, beB **      materialized other than in a register (since we don't know= **      where we can safely put it) but there is currently no / **      enforceable compiler guarantee of this,   L then this magnificant display of the macro functionality of the C language . . .    /*E ** The next two defines allow the kernel and executive routine counts C ** to be filled in automatically after lists have been declared for < ** kernel and exec mode.  They must be placed before the PLV> ** declaration and initialization, and for this module will be ** functionally equivalent to: **! ** #define KERNEL_ROUTINE_COUNT 3  ** #define EXEC_ROUTINE_COUNT 1  ** */  ; #define EXEC_ROUTINE_COUNT sizeof(exec_table)/sizeof(int *) ? #define KERNEL_ROUTINE_COUNT sizeof(kernel_table)/sizeof(int *)   / how cunningly deciphered! But there's more. . .   E ** One final note on the service routines.  As a security precaution, D ** protected shareable images aren't allowed to call other shareableE ** images, unless they too are installed protected.  Watch your calls 2 ** (including implicit ones) to external routines!  I so no CRTL then? Would a typical C programmer not find this a hinderence?   J Anyway, for anyone out there that prefers to use the best tool for the jobI and can leave dogma-driven prejudice at the door,  here's a little macro, E and program template, that makes my life easier when writing UWSSs: -   E         .macro define_service,name,narg=0,flags=0,mode=exec,?endmacro   3         'mode'_routine_count='mode'_routine_count+1   1         .call_entry     home_args=false,        - 1                         quad_args=true,         - "                         label=name  #         .save_psect     local_block   #         .psect          'mode'_list            .address        name  $         .psect          'mode'_flags           .long           flags            .restore_psect           .if not_equal narg            cmpb    (ap),#narg           bgeq    endmacro            movzwl  #ss$_insfarg,r0          ret  	 endmacro:   
         .endc 
         .endm   '     .title  MYUWSS - My System Services      .ident  'V1.0' ;+ ; Constants  ;-"     .library "sys$library:lib.mlb"     .library "t3$lib"   7     t3$def                          ; Tier3 Symbol defs <     $plvdef                         ; PLV offsets and values9     $ssdef                          ; System status codes 2     $psldef                         ; Access modes9     $prvdef                         ; Privilege bit masks :     $prtdef                         ; Page protection bits   kernel_routine_count    = 0  exec_routine_count      = 0   C         .psect  exec_list,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long  exec_table:   E         .psect  kernel_list,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long 
 kernel_table:   D         .psect  exec_flags,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long exec_flags:   F         .psect  kernel_flags,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long
 kernel_flags:   C             .psect  my_data,pic,con,rel,lcl,noshr,noexe,rd,wrt,quad B :                      :                                         :A             .psect  my_code,pic,con,rel,lcl,shr,exe,rd,nowrt,long                define_service blah - :                   :                       :               ret  )             define_service fred,3,,kernel - :                   :                       :               ret  
 exec_rundown: I            .jsb_entry                           ; Entry point for rundown 9                                                 ; handler              rsb  ;+ ; Privileged Library Vector  ; K ; Any psect with the VEC attribute will be automatically moved to the start  ; of the image.  ;-2         .psect  my_services,page,vec,pic,nowrt,exe  L         .long    plv$c_typ_cmod          ; Set type of vector to change mode
 dispatcher3         .long    0                       ; Reserved G         .long    kernel_routine_count    ; # of Kernel    mode routines G         .long    exec_routine_count      ; # of Executive mode routines >         .address kernel_table            ; Kernel routine list<         .address exec_table              ; Exec routine listA         .long    0                       ; Kernel rundown handler A         .address exec_rundown            ; Exec   rundown handler 9         .long    0                       ; RMS Dispatcher ?         .address kernel_flags            ; Kernel routine flags ?         .address exec_flags              ; Exec   routine flags            .end     Regards Richard Maher   ' <danco@ns2.pebble.org> wrote in message + news:slrndmf0bc.6tk.danco@ns2.pebble.org... H > In article <dk7kvs$q8i$1@news-02.connect.com.au>, Richard Maher wrote: > J > > So Dan, what would you recommend to the punters for writing inner-mode codeI > > that must be linked /PROTECTed? No doubts about *all* of the bollocks @ > > disclaimers and provisos contained in sys$examples:*uwss*.c? > E > I have some inner mode code here that I wrote some 20 years ago and C > which I still maintain.  It's almost all written in MACRO32, with A > some written in C.  If I was going to write any significant new " > inner mode code, I'd do it in C. >  > - Dan    ------------------------------  $ Date: Wed, 2 Nov 2005 08:00:06 -0500# From: "Dan Allen" <dallen@nist.gov> Y Subject: Yikes!! -  an INFO-VAX  post with technical content  - beware!  - RE: Writing an : Message-ID: <JFEPKAPBPMDFDBOIANGDGEPHGPAA.dallen@nist.gov>   > -----Original Message-----: > From: Richard Maher [mailto:maher_rj@hotspamnotmail.com], > Sent: Wednesday, November 02, 2005 5:36 AM > To: Info-VAX@Mvb.Saic.Com % > Subject: Re: Writing an OpenVMS ACP  >  > 	 > Hi Dan,  > / > > If I was going to write any significant new $ > > inner mode code, I'd do it in C. > J > Ok, so either you don't care to discuss your reasons for choosing C overN > Macro-32, or there just aren't any. In any event you certainly don't have toL > justify yourself to me. Tiger Woods wears Nike and Dan writes in C. ShouldH > be enough for anybody, but here are a couple of reasons (excerpts from? > sys$examples:uwss.c) why I personally don't like C for UWSSs:  > E > **      The OpenVMS VAX MACRO-32 example and the OpenVMS Alpha V1.0 F > **      BLISS example used "DEFINE_SERVICE" macros in a manner whichG > **      allowed declaration of kernel- and executive-mode routines in C > **      separate statements, mixing of kernel- and executive-mode E > **      routines in successive statements and automatic counting of H > **      the numbers of both kinds of routines.  The macro capabilitiesA > **      of C are limited, by comparison, so only the counts are D > **      calculated (as opposed to hard-coded) here.  Specifically,G > **      this example relies on sizeof() constructs to avoid having to H > **      hard-code the numbers of routines, but still requires that allF > **      executive-mode routines be declared in a single declaration,C > **      and that all kernel-mode routines be declared in a single  > **      declaration. >  > and this. . .  > : > **      . . .ps_temp should not, and likely will not, beD > **      materialized other than in a register (since we don't know? > **      where we can safely put it) but there is currently no 1 > **      enforceable compiler guarantee of this,  > N > then this magnificant display of the macro functionality of the C language . > . .  >  > /*G > ** The next two defines allow the kernel and executive routine counts E > ** to be filled in automatically after lists have been declared for > > ** kernel and exec mode.  They must be placed before the PLV@ > ** declaration and initialization, and for this module will be  > ** functionally equivalent to: > **# > ** #define KERNEL_ROUTINE_COUNT 3 ! > ** #define EXEC_ROUTINE_COUNT 1  > ** > */ > = > #define EXEC_ROUTINE_COUNT sizeof(exec_table)/sizeof(int *) A > #define KERNEL_ROUTINE_COUNT sizeof(kernel_table)/sizeof(int *)  > 1 > how cunningly deciphered! But there's more. . .  > G > ** One final note on the service routines.  As a security precaution, F > ** protected shareable images aren't allowed to call other shareableG > ** images, unless they too are installed protected.  Watch your calls 4 > ** (including implicit ones) to external routines! > K > so no CRTL then? Would a typical C programmer not find this a hinderence?  > L > Anyway, for anyone out there that prefers to use the best tool for the jobK > and can leave dogma-driven prejudice at the door,  here's a little macro, G > and program template, that makes my life easier when writing UWSSs: -  > G >         .macro define_service,name,narg=0,flags=0,mode=exec,?endmacro  > 5 >         'mode'_routine_count='mode'_routine_count+1  > 3 >         .call_entry     home_args=false,        - 3 >                         quad_args=true,         - $ >                         label=name > % >         .save_psect     local_block  > % >         .psect          'mode'_list  >  >         .address        name > & >         .psect          'mode'_flags >  >         .long           flags  >  >         .restore_psect >  >         .if not_equal narg >  >          cmpb    (ap),#narg  >          bgeq    endmacro " >          movzwl  #ss$_insfarg,r0 >          ret >  > endmacro:  >  >         .endc  >         .endm  > ) >     .title  MYUWSS - My System Services  >     .ident  'V1.0' > ;+
 > ; Constants  > ;-$ >     .library "sys$library:lib.mlb" >     .library "t3$lib"  > 9 >     t3$def                          ; Tier3 Symbol defs > >     $plvdef                         ; PLV offsets and values; >     $ssdef                          ; System status codes 4 >     $psldef                         ; Access modes; >     $prvdef                         ; Privilege bit masks < >     $prtdef                         ; Page protection bits >  > kernel_routine_count    = 0  > exec_routine_count      = 0  > E >         .psect  exec_list,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long 
 > exec_table:  > G >         .psect  kernel_list,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long  > kernel_table:  > F >         .psect  exec_flags,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long
 > exec_flags:  > H >         .psect  kernel_flags,pic,con,rel,lcl,noshr,noexe,rd,nowrt,long > kernel_flags:  > E >             .psect  my_data,pic,con,rel,lcl,noshr,noexe,rd,wrt,quad D > :                      :                                         :C >             .psect  my_code,pic,con,rel,lcl,shr,exe,rd,nowrt,long  > ! >             define_service blah / > :                   :                       :  >              ret > + >             define_service fred,3,,kernel / > :                   :                       :  >              ret >  > exec_rundown: K >            .jsb_entry                           ; Entry point for rundown ; >                                                 ; handler  >             rsb  > ;+ > ; Privileged Library Vector  > ; M > ; Any psect with the VEC attribute will be automatically moved to the start  > ; of the image.  > ;-4 >         .psect  my_services,page,vec,pic,nowrt,exe > N >         .long    plv$c_typ_cmod          ; Set type of vector to change mode > dispatcher5 >         .long    0                       ; Reserved I >         .long    kernel_routine_count    ; # of Kernel    mode routines I >         .long    exec_routine_count      ; # of Executive mode routines @ >         .address kernel_table            ; Kernel routine list> >         .address exec_table              ; Exec routine listC >         .long    0                       ; Kernel rundown handler C >         .address exec_rundown            ; Exec   rundown handler ; >         .long    0                       ; RMS Dispatcher A >         .address kernel_flags            ; Kernel routine flags A >         .address exec_flags              ; Exec   routine flags  >  >         .end >  >  > Regards Richard Maher  > ) > <danco@ns2.pebble.org> wrote in message - > news:slrndmf0bc.6tk.danco@ns2.pebble.org... J > > In article <dk7kvs$q8i$1@news-02.connect.com.au>, Richard Maher wrote: > > L > > > So Dan, what would you recommend to the punters for writing inner-mode > codeK > > > that must be linked /PROTECTed? No doubts about *all* of the bollocks B > > > disclaimers and provisos contained in sys$examples:*uwss*.c? > > G > > I have some inner mode code here that I wrote some 20 years ago and E > > which I still maintain.  It's almost all written in MACRO32, with C > > some written in C.  If I was going to write any significant new $ > > inner mode code, I'd do it in C. > > 	 > > - Dan  >  >  >    ------------------------------  % Date: Wed, 02 Nov 2005 17:47:49 +0100 " From: Jiri Kulhan <jiri@kulhan.cz>M Subject: [Fwd: GT.M on Alpha/AXP being released as open source free software] + Message-ID: <3ss8tlFpqedjU1@individual.net>    Reposted from comp.lang.mumps:  -----------------------------  B GT.M on HP Alpha/AXP OpenVMS and Tru64 UNIX is joining GT.M on x86C GNU/Linux as open source free software under the GNU General Public G License (GPL - http://www.fsf.org/licensing/licenses/gpl.txt). Binaries # are available now from Source Forge E (http://sourceforge.net/projects/sanchez-gtm) and source code will be ? downloadable once it is repackaged for release at Source Forge.   
 -- Bhaskar2 ks dot bhaskar at fnf dot com <-- send e-mail here   ------------------------------   End of INFO-VAX 2005.612 ************************