1 INFO-VAX	Sun, 19 Mar 2006	Volume 2006 : Issue 156       Contents:8 Re: Advance Server wish list .OR. VMS PC Behaviour Traps@ Attunity Press Release - Products Available on OpenVMS Integrity Re: boot problem - device full Re: HP's ITRC forum for VMS  Re: HP's ITRC forum for VMS  Re: HP's ITRC forum for VMS ? Re: Mysterious revision date changes caused by Advanced Server?  Problems upgrading tcp services # Re: Problems upgrading tcp services % The reply they didn't want you to see   F ----------------------------------------------------------------------    Date: 19 Mar 2006 19:08:27 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)A Subject: Re: Advance Server wish list .OR. VMS PC Behaviour Traps , Message-ID: <441dac2b$1@news.langstoeger.at>  h In article <4m5r12l2d9huat2mtferi8c1cdr4vrhlj2@4ax.com>, D Gillbilly <gillbilly@ns.sympatico.ca> writes:1 >Advance Server wish list .OR. VMS PC Virus Traps  > B >To the good people in AS engineering (and anyone else who cares), > C >In some future release of AS, could the following functionality be  >added to the product?  K The VMS roadmaps (so far) don't speak of next AS versions (only about minor L changes for current/coming VMS versions like ECO5 now and V7.3B in Apr-2006)M The speak however of a replacement by CIFS (SAMBA V3 and up) starting 2006H2.   D 	http://www.openvms.digital.com/openvms/roadmap/openvms_roadmaps.htm   --   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: Sun, 19 Mar 2006 10:00:02 -0500 ' From: "Main, Kerry" <Kerry.Main@hp.com> I Subject: Attunity Press Release - Products Available on OpenVMS Integrity R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB826011@tayexc19.americas.cpqcorp.net>   All,  H Attached may be of interest to this list (apologies in advance if it was previously posted)  F - Attunity product press release announcing their product availability for OpenVMS Integrity:  F http://www.attunity.com/content/PressRelease.Asp?PRName=3D20060227a=20: (note date error should state 2006, not 2005 as seen from:! http://www.attunity.com/News/pr/)   F Burlington, MA, February 27, 2005 - Attunity, Ltd. (NASDAQ: ATTU), the= strategic Enterprise Integration Platform of choice for large > organizations, has announced today the release of its AttunityF Integration Suite (AIS) version 4.8.2, with support for the HP OpenVMS1 operating system running on HP Integrity servers.   C Due to increased market demand, Attunity has ported its Integration G Suite (AIS) of products (CONNECT, FEDERATE and STREAM) to OpenVMS on HP A Integrity servers with support for version 8.2-1 of the operating  system.   D "Attunity's support for OpenVMS on HP Integrity servers provides yetH another option for OpenVMS customers," said Itamar Ankorion, director ofC product management, Attunity. "These customers can now extend their F OpenVMS investment and capitalize on the performance and cost benefitsF of HP Integrity servers. With the Attunity Integration Suite, they nowH have the tools that simplify data access and information integration for9 such initiatives as migration and business intelligence."   C The availability of the Attunity Integration Suite on the 64-bit HP ? Integrity platform, running OpenVMS and powered by the Intel(r) A Itanium(r) 2 microprocessor, provides access to RMS data sources, H enables the use of new J2EE and .NET applications, provides Web ServicesF and supports a variety of reporting tools. Many customers with missionE critical applications running on VAX and/or AlphaServer platforms now 3 have the choice to migrate to HP Integrity servers.   H "HP has long supported Attunity's effort to provide connectivity for ourC OpenVMS platform," said Ann McQuaid, general manager of the OpenVMS B group at HP. "The support for OpenVMS on HP Integrity servers willB provide a comprehensive, strategic integration platform choice for& customers who are looking to migrate."   ------------------------------  % Date: Sun, 19 Mar 2006 16:52:11 +0100 ! From: Emil <emilg2SP@AMgazeta.pl> ' Subject: Re: boot problem - device full + Message-ID: <dvjuno$8qj$1@achot.icm.edu.pl>    Thank you all guys! A lot!!   I it boots up now and I've learnt I have to watch out for the free space :)    best regards Wojtek   ------------------------------  % Date: Sun, 19 Mar 2006 09:27:37 +0100 + From: Marc Schlensog <fishtank.spam@web.de> $ Subject: Re: HP's ITRC forum for VMS: Message-ID: <20060319092737.4787df46.fishtank.spam@web.de>  " On Sun, 19 Mar 2006 12:46:04 +08004 "Richard Maher" <maher_rj@hotspamnotmail.com> wrote:  
 > Hi Mark, > [...] C > There's only a small neat pile of ashes where my posts used to be  > [...]   G Dunno what was going on on ITRC, but if you were acting a fool like you F are doing here, I can thoroughly understand why your posts got erased.   Marc   ------------------------------  # Date: Sun, 19 Mar 2006 12:55:48 GMT " From:   VAXman-  @SendSpamHere.ORG$ Subject: Re: HP's ITRC forum for VMS0 Message-ID: <00A52EB2.FF791444@SendSpamHere.ORG>  g In article <dviku9$c3q$1@news-02.connect.com.au>, "Richard Maher" <maher_rj@hotspamnotmail.com> writes:  >  >  >Hi Ian (stirrer :-) Miller, > 0 >> the high signal to noise ratio makes it worth( >> putting up with the occational glich. >   >One may find the, equally high,I >sanctimonious-self-serving-narcissistic-wanker to common-IT-wanker ratio  >conversely off-putting.  H Are you refering to the hog warts thing that somebody explained to me on9 one visit there?  I think, all in all, it's pretty silly.       K >Regardless of whatever hats they profess to wear, I can assure you that in L >ITRC when the HP good ol' boy (ex)employees come a-knockin' on your door inJ >the middle of the night, they're all wearing pointy white ones with holesM >cut out for the eyes. Anyway, it was my fault for gettin' a bit uppity and I 8 >still got the one good eye and I had 'nuff kids anyhow.  F There appears to be a wealth of info and well intentioned folks in theF VMS ITRC forum but I still haven't gotten an answer to my issue.  ITRCG is, and I reiterate, *NO* replacement for what was DSN/WIS.  I miss the E real assistance and problem resolution I used to get with DSN/WIS.          M >>"We don't care about your damn facts boy! Don't you dare eyeball one of the I >I.T.R.C. lessen ya know what's good for ya. We got all the facts we need 
 >right here".  > . >Regards Richard (Toby, NO! Kunta Kinte) Maher > H >PS. If the humour doesn't travel well to the States then tough shit! ITJ >SHOULDN'T!!! This is exactly how I've been treated as a VMS customer (andJ >long time advocate) and DSPP member. Can you please send an adult over toI >that Lord of the Flies remake island of ITRC and smash that conch over a  >couple of kid's heads?   $ Got it "Toby"!!! :)  Loud and clear.   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  % Date: Sun, 19 Mar 2006 12:24:18 -0600 2 From: David J Dachtera <djesys.nospam@comcast.net>$ Subject: Re: HP's ITRC forum for VMS+ Message-ID: <441DA1D2.93CB077C@comcast.net>    JF Mezei wrote:  >  > Richard Maher wrote:M > > There's only a small neat pile of ashes where my posts used to be and I'm N > > sure it's for the best. There is no way that an outsider could come in andI > > try to understand the inner workings of the delicate and finely-tuned G > > machine that is HP's Abu Ghraib for VMS customers and DSPP members.  > G > While HP goes through great lengths to avoid PR and marketing of VMS, J > the rest of the corporation is extremely PR and marketing savvy. ITRC isD > part of  a customer facing public web site infrastructure and as aH > result, it is also part of HP's PR and contributes towards HP's image. > F > As a result, HP will do whatever it takes to ensure that it does notH > contain anything which would not fit within the image HP wants its web > site infrastructure to have.  H FWIW, openvms.org - for the time being at least - has a link on the main- OpenVMS page. Perhaps that is a better forum.   G > ITRC are not public forums. They are private property. If you enter a G > store and start saying stuff that the shopowner doesn't like , he has   > the right to ask you to leave. > G > Where HP is perhaps lacking is in advising a poster of the removal of * > one of his posts and why it was removed. > H > That is why there are newsgroups and user groups which operate outsideG > the boundaries of the corporation, and thus without PR restrictons of & > forums operated on private property.  G Also, FWIW, the owner of openvms.com might be persuaded to join with us D in our efforts (no guarantees, of course). As the regulars here willD attest, persuasion is not my strong suit (not even sure I have one).C Perhaps others may have better luck. Be advised, however, that I am H personally acquainted with this person having worked for him twice in my@ career. Believe me when I say that you'd better make one hell of business case to him!   C That said, should web searches for VMS and OpenVMS start turning up F links that have powerful marketing material, HP will, in any event, be? more or less "along for the ride" and could become an unwilling H beneficiary of our efforts to market OpenVMS on our own. If they have toH be dragged by the feet, kicking, scratching and screaming all the way toC bank to deposit their unwanted profits, then so be it. They may not G thank us - and may, in fact, curse us and seek to destroy our work, but E their stockholders will thank us for protecting stockholder interests 3 and enhancing the value of stockholder investments.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  # Date: Sun, 19 Mar 2006 12:57:25 GMT - From: D Gillbilly <gillbilly@ns.sympatico.ca> H Subject: Re: Mysterious revision date changes caused by Advanced Server?8 Message-ID: <srmq12pk28rr85u2k80veuuoicfnq5794u@4ax.com>  B On Fri, 17 Mar 2006 22:09:02 GMT, "PEN" <paul.nunez.nosp@m.hp.com> wrote:   >Hi, > ) >I just thought of  one more iffy bit :o)  > K >I know that the DOS file size is not stored in the DOS ACE for sequential  M >files with a stream, stream_lf, or undefined record format.  The "DOS" size  L >of these files can be computed from information in the file header.  Thus, M >I'm not sure whether AS will modify the DOS ACE on such files whenever they  - >are read (I suspect the ACE is not updated).  > L >Your case is a bit unique in that you have OpenVMS .EXE files in the share K >directory making them both subject to the "Windows Known File Types" code  I >paths on the client and the "non-stream files" code paths on the server.  > 	 >Regards,  >  >  >Paul  >    You beat me...  @ I was going to see why I still thought I had 2 distinct types ofF directory access. Only one of them it seemed to cause a header update.  @ My next set of tests were going to be on the files themselves. IC thought if I could figure out what had changed in the file, I could 7 use that information to deduce what else was happening.   ' My guess now is it will be "see above".   F Windoze is stupid after all. It's just a "works pretty good for nearly@ everybody" type of OS anyway. I can now see ways to use it's ownB behaviors against itself. (Visions of a cheap 1 CPU VMS appliance,C acting as the uncorruptable network law enforcer dancing through my 	 head :-).   	 <wake up>  HP!!!     YOU HAVE THAT NOW!
 </wake up>  E If Windoesnot works well enough for most people, imagine the benefits B VMS can bring to your network. It's hard to bully VMS and get awayF with it. We keep an alternate (usually disconnected) connection to our= remote  VMS sites just so that I have an alternate way into a E misbehaving network. I can usually identify the bully pretty quickly.     It is a fantastic forensic tool.  A Am I the only one that uses the reliability of  VMS in hostile PC 
 environments?   #    After all, it is safe. It's VMS.        Duane     6 Once again Paul (and others), thank you for your help.  B And the irony of saving a support call to hp and having an hp tech help, is not lost on me. :-)   ------------------------------    Date: 19 Mar 2006 07:54:20 -0800 From: tomarsin2015@comcast.net( Subject: Problems upgrading tcp servicesC Message-ID: <1142783660.480167.142390@e56g2000cwe.googlegroups.com>   A I have a VAX 4000-VLC that has 6.2 and UCX 4.2.  I  would like to B upgrade the system from UCX 4.2 to 5.1 or 3. I should say that theF reason I am at 6.2 I have a application that will not work on VMS 7.X., Anyway I get this when trying to upgrade TCP  ! Directory DAD6:[TCPIP_VAX051.KIT]   " DEC-VAXVMS-TCPIP-V0501-15-1.PCSI;1   Total of 1 file. ALTAIR> product install *  %PCSI-E-OPENIN, error opening 2 PCSI$SOURCE:[TCPIP_VAX051.KIT]*-*-*-%%%%%-*-*.PCSI *; as input A -RMS-F-DEV, error in device name or inappropriate device type for 	 operation " %PCSI-E-S_OPFAIL, operation failed? %PCSIUI-E-ABORT, fatal error encountered - operation terminated  ALTAIR>   % So if I define pcsi$source I get this     ALTAIR> define pcsi$source dad6: ALTAIR> product install * 0 %PCSI-E-PDFFIL, the following errors are in file _DAD6:[TCPIP_VAX051.KIT]DEC-VAX  VMS-TCPIP-V0501-15-1.PCSI;1 1     5           error TCPIP_NOT_SUPPORTED abort ; ! %PCSI-E-PDFMST, missing semicolon 3     8           error UCX_ALREADY_INSTALLED abort ; ! %PCSI-E-PDFMST, missing semicolon # %PCSI-E-PDFUDV, undeclared variable " %PCSI-E-S_OPFAIL, operation failed? %PCSIUI-E-ABORT, fatal error encountered - operation terminated  ALTAIR>   
 Any thoughts?  phil   ------------------------------    Date: 19 Mar 2006 18:57:48 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER), Subject: Re: Problems upgrading tcp services* Message-ID: <441da9ac@news.langstoeger.at>  d In article <1142783660.480167.142390@e56g2000cwe.googlegroups.com>, tomarsin2015@comcast.net writes:B >I have a VAX 4000-VLC that has 6.2 and UCX 4.2.  I  would like toC >upgrade the system from UCX 4.2 to 5.1 or 3. I should say that the G >reason I am at 6.2 I have a application that will not work on VMS 7.X.   G Are you sure about that? There haven't been much of a change between V6  and V7 on OpenVMS VAX...  - >Anyway I get this when trying to upgrade TCP  > " >Directory DAD6:[TCPIP_VAX051.KIT] > # >DEC-VAXVMS-TCPIP-V0501-15-1.PCSI;1  >  >Total of 1 file.  >ALTAIR> product install * >%PCSI-E-OPENIN, error opening3 >PCSI$SOURCE:[TCPIP_VAX051.KIT]*-*-*-%%%%%-*-*.PCSI  >*; as inputB >-RMS-F-DEV, error in device name or inappropriate device type for
 >operation# >%PCSI-E-S_OPFAIL, operation failed @ >%PCSIUI-E-ABORT, fatal error encountered - operation terminated >ALTAIR>  F You haven't defined a PCSI$SOURCE logical and haven't used /SOURCE=xxx  & >So if I define pcsi$source I get this > ! >ALTAIR> define pcsi$source dad6:   8 You should define PCSI$SOURCE as dev:[dir] so better try  - 	$ DEFINE PCSI$SOURCE DAD6:[TCPIP_VAX051.KIT]    >ALTAIR> product install *1 >%PCSI-E-PDFFIL, the following errors are in file   >_DAD6:[TCPIP_VAX051.KIT]DEC-VAX >VMS-TCPIP-V0501-15-1.PCSI;12 >    5           error TCPIP_NOT_SUPPORTED abort ;" >%PCSI-E-PDFMST, missing semicolon4 >    8           error UCX_ALREADY_INSTALLED abort ;" >%PCSI-E-PDFMST, missing semicolon$ >%PCSI-E-PDFUDV, undeclared variable# >%PCSI-E-S_OPFAIL, operation failed @ >%PCSIUI-E-ABORT, fatal error encountered - operation terminated >ALTAIR> >  >Any thoughts?  < 1) Check if TCPIP V5.1 does support/work-on OpenVMS VAX V6.2@ 	a) check also if you need a PCSI ECO for the TCPIP installationF 	b) I personally don't think that V5.1 supports V6.2, but I don't know' 2) Remove UCX before you install TCPIP. G 3) Install all VMS ECOs and the last TCPIP ECO after TCPIP installation   	 Good luck    --   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: Sun, 19 Mar 2006 20:47:34 +0800 3 From: "Richard Maher" <maher_rj@hotspamnotmail.com> . Subject: The reply they didn't want you to see1 Message-ID: <dvjjse$ntl$1@news-02.connect.com.au>    Hi,   K The following was entered into HP's ITRC forum for VMS on Mar 12th 13:45 as  part of the following thread.   L http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1007568  I It was subsequently, the only reply removed yesterday from that thread by G the self-appointed decorum police, apparently because I upset someone's K buddy. I don't recall them appearing when I was being spat on, so I find it K a tad incongrous that they turn up now to give me a parking ticket. Anyway, K I wrote it, I think it's compelling reading, I can't find anything in there F to reproach myself about, and I want to put it out of the reach of theL self-serving revisionists that sadly seem to be running the show these days.I If I want to reminiss in the future then I want somewhere I can look this  up.   L So if you are of a delicate disposition and find such stuff distasteful thenI look away now. This is for me. Read-it / Don't read it. That's up to you.   I It's almost verbatim, but the crappy way you have to enter things in ITRC C means I had to break it into two and may have changed the odd word.    Regards Richard Maher   3 On Mar 7, 2006 21:03:06 GMT  John Gillings wrote: -  >>> L ITRC is entirely voluntary. It's pretty much at the bottom of my priorities. <<<   G Not for me - I just can't get enough of it! I've placed it way up there L between breathing and eating, on my life's to-do list. Why, only yesterday IL asked my secretary to block book at least three days from every week just toD respond to the unsubstantiated rumours and commercially damaging FUD2 emanating from the poisonous pens of HP employees.   >>>  I don't come here to "spar"  <<<   J Which would make your standing-up-walking-over-and-punching-me-in-the-nose all the more bizarre!   D But if, by having the absolute gall to defend themselves, one was toG precipitate an appearance boycott by some Dame Nellie Melba then hey, I / guess we'll just all have to try to soldier-on.   , On Mar 8, 2006 20:53:26 John Gillings wrote: >>> 	 Consider:    CLRL R0  CALLG (R0),your-routine  <<<   K OK let's consider it. No! Let's go really crazy and actually test it before I we start shooting our mouths off and denigrating other people's software. E (Doesn't look like anybody else could be bothered. Maybe it's just my H fascination with FACTS.) Here's the output from a simple command file: -  
 $ set noon $ create lasik.mar0 .title none_so_blind - as those who will not see .entry blind_freddy,^m<>       CLRL R0 (     CALLG (R0),g^t3$$waitfr_file_promote       $exit_s code=#1  .end blind_freddy  $ macro/lis lasik  $ link lasik,sys$input/opt sys$share:dir_watch_exec/share $!% $ write sys$output f$getjpi("","PID")  00000D37 $ run lasik ; %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual : address=0000000000000000, PC=0000000000030030, PS=0000001B/ %TRACE-F-TRACEBACK, symbolic stack dump follows J   image    module    routine             line      rel PC           abs PC>  LASIK                                      0 0000000000020030 0000000000030030>                                             0 FFFFFFFF89043494 FFFFFFFF89043494% $ write sys$output f$getjpi("","PID")  00000D37  J Funny thing is, my process (let alone my machine) is still up and running. What a surprise! NOT.   0 Want to see one that traps the access violation?   $create prk.cob  identification division. program-id.    Santa_Lucia.  data division. working-storage section. 01  sys_status pic s9(9) comp. procedure division.  00. *     call "blind_freddy" giving sys_status.3     display "Status = " sys_status with conversion. 
     stop run.  *  end program Santa_Lucia. $cob/lis prk $! $create lasik.mar  .call_entry label=blind_freddy       MOVAB g^exe$sigtoret,(FP)      CLRL R0 (     CALLG (r0),g^t3$$waitfr_file_promote     ret    .end $mac/lis lasik$ $link/sysexe prk,lasik,sys$input/opt sys$share:dir_watch_exec/share $run prk Status =         12   1 =================================================   I John, on those occasions when it has become apparent to me that I've been J talking through my bottom on a given issue (usually some time after it hadK crystallised for almost everyone else), I've found it best just to stick my J hands up in the air, apologise for having wasted everyone else's time, andH then move on to the next issue. Maybe there's something in that for you?   >>>  Try it on a VAX  <<<    OK, lets: -    SYSTEM> @dir_watch This code only works on alpha  %SYSTEM-F-ABORT, abort   Doh!  J I think the clue is in the error message. My code is, and always has been,I Alpha-specific as you well know. How exactly were you expecting me to run I this on a VAX? Why not a PDP? (And I have this slight suspicion that it's H just not gonna compile-and-run on an IA64 either. These calling standard# changes must really throw you hey?)   K Oh I get it! You've plucked a handful of my Alpha Macro-32 instructions out D of context, placed them in your imaginary system on a VAX and am nowJ lecturing me publicly about the security and box-crashing pitfalls in your design?   ; Gather round children. Uncle John is gonna tell us a story. 
 .  .  .  .F And then the big bad wolf ate the third little pig 'cos he hadn't usedC string to bind his bricks! Now due to planetary alignment and sheer G providence sometimes concrete may keep a weak wolf out but depending on = these coincidences is completely the wrong attitude. I have a L dead-sea-scrolls copy of "Everything you need to build a Stick House" and itH clearly states that if you don't use string to bind the sticks the house will fall over. So there!   9 Q: What do these "strings" look like on Alpha Uncle John?   I Q: Yeah and why don't the sys$examples:uwss.c and $getuai and $qio houses 	 use them?   8 A: Shut up and go back to sleep you impudent young pups!   >>> C look it up in the architecture manual (section 8.4 in my 1977 first 5 edition). That's how the CALL instruction is defined.  <<<   H Cheers for that fascinating little meander down memory lane, but I don'tJ have to look anything up as my code on VAX, like many others' I'd imagine,K is based on sys$examples:ussdisp.mar which does the job quite nicely thanks K very much. Or was that you jumping up and down yelling "He's doing the same & thing on VAX everyone! He is! He is!"?  G Now, to attempt that inference would take a particularly nasty piece o' L work! Which obviously you're not John. But a casual observer may be forgivenJ for thinking that you're trying to transfer your smear of my Alpha code to< the VAX by proxy. We wouldn't want that to happen, would we?  F [Are you actually looking for help and advice, or are you just here to insult people?]   I For some time now I have been, and sadly still am, seeking "help" here in 1 the form of answers to the following questions: -   G Q1: Without the use of enhanced privileges and with the Main Executable J Image not having being INSTALLed: - Can a call from an inner-mode UWSS outE to any other shareable image (/PROTECTED or otherwise) be spoofed and L redirected to another shareable image? My testing to-date indicates that theH image activator insists on all shareable images being INSTALLed. Is this$ supported and architected behaviour?  L Q2: When a LIB$ routine is called from an EXEC Mode UWSS, why does the imageB activator consider Non-Trusted, Supervisor-Mode Logical Names whenK activating LIBRTL? Furthermore, why does the image activator then appear to K ignore non-trusted logical names when activating other shareable images? Is & there something peculiar about LIBRTL?  J Now either you don't know the answer to these questions (which is fine) orE you choose not to share the answers in this forum (which is also your K prerogative). I cannot compel anyone to reply, nor should I be able to. But J imagine my surprise and displeasure when, instead of answers, I am greeted8 with unsubstantiated and disparaging FUD such as this: -  C [For a start, I'd want to see some far more extensive validation of ; arguments before deploying your code on one of my systems.]   I Do you consider that statement to be "Helpful" John? Why did you use your L status as a HP employee, VMS Support person, and your pointy little crown toJ carry out an emotive and subjective attack on the commercial quality of my code? How 'bout one of mine: -  F "For a start, I'd want to see a higher calibre of HP employee involved5 before I'd fork out one cent for a support contract."   E Personally, I'd describe both of those statements as churlish, highly & inflammatory and anything but helpful.  E In this case, my code to which you refer was being offered only as an G example of a UWSS calling out to LIBRTL and while I don't recall asking H someone, as purportedly busy as yourself, to perform a critique on it, IJ always welcome additional testers and bug-spotters. Stick your code's headJ above the parapet and someone's bound to take a shot at it. I'm big enoughK and ugly enough to look after myself. Having said that, if "help" was truly J being offered (as opposed to an attempt at public ridicule) then one mightL have expected a short e-mail. But I'm certainly not shy when it comes to theG public "outing" of bugs that need fixing so I would have been genuinely L grateful if you had have said something like "Why aren't you probing the argG list?" or "I think there's a typo and your IFNORD should be a IFNOWRT". B Sadly, I think we all know  "help" was not what I got John was it?   >>> G upon entry to your routine, AP will be zero. Therefore the instruction:    CMPB (AP),#anything    will ACCVIO. <<<   K More heresay, conjecture and just plain wrong! All the evidence I've posted J here says the System Service Dispatcher prevents this from happening. HaveK you ever even written a UWSS on Alpha? I can't believe you've really wasted K this much of my, and everyone else's time, with your frivolous speculation! J (But you're too busy for that. So this must be malicious mud slinging! But. why John? Have I done something wrong to you?)  L Maybe you really did believe there was a fire in the theatre John, maybe youK did smell smoke, but that doesn't help the dead lying trampled on the floor ! because of your beak now does it?   A I tell you what, why don't you resort to that last bastion of the J floundering support person: - HP's internal VMSNOTES notes conference, andK see if you can't dig up someone who knows what they're talking about. Maybe F they can find some other part of the code that can be manipulated intoI crashing the system. Then you can come back and tell us that that was the G vulnerability you were talking about all along. (To my knowledge, these J particular routines have never been tested in the field so, who knows, you may get "lucky").    >>> L Now, as it *happens*, in some cases the Alpha MACRO-32 compiler may generateK code for the CALL in such a way as to result in an ACCVIO *before* actually E calling the target routine. That may protect you from this particular J exploit, but depending on coincidences is entirely the wrong attitude when coding in inner modes. <<<   K Just what is that smut you're peddling? You should write for a tabloid like H The Sun. ("Sources close to the couple" have informed us that undetectedL access violations have been going on for years. Big-G's paparazzi understandL it's just the tip of the iceberg!) Was it LA Confidential where they used to say "Just the facts ma'am!".  K If you'd've permitted your eyes to even countenance the possibility of your J being wrong, then they would have been able to simply peruse the wealth ofK evidence that I placed before them. I even gave you the line numbers in the K VMS source code to look at! And all you did was put your hands to your ears ( and sing "I can't heeear you! La La La".  I Anyway, I've wasted enough time as a VMS customer and DSPP partner on the J ITRC experience and I'm clearly not going to get anything out of you otherI than conjecture so, for the benefit of the wider audience, I submit it as C fact that "It is the architected function of the VMS System Service H Dispatcher to probe the argument list (not the arguments themselves) forH accessibility before calling a UWSS". I can't say it's indisputable factK but, given the weight of evidence in previous replies, I wouldn't expect to # see too much proof to the contrary.   A John, I don't know what your agenda has been here but a window of K opportunity has presented itself to you. I scincerely hope that you embrace  it.    Regards Richard Maher    ------------------------------   End of INFO-VAX 2006.156 ************************                                                                                                                                                                                      k_^>2vA*Dva)Pb'`k|x.5go
2.$}}"'>q,kgU:`y|6Si2@\ۙ:B`@^/3mSOY{zJyK_4-s,tǃFVCSh^hc.G3!Z- /D^[Soӡ~gvˢAgԻSe1p;f ɭvicjcf5=KwN^o:jdçh~h~."MyCcd13&Rؑ8yBIHlvHNْHşRRdm0Ff/XM5ϼ?}O;~tyyS̼y3lYNtg9q1vJ(/G8>Rt4İ9i+ܴ-1
BI+h";K6]De]\vް=0
xWsvpVߍ2퇛wh
򺙥`\~5S
*W
N4!ՂlV&ȵ%BªpfyHT8
w/r`}JwY+n:c_
]]`2 bUb5հAM>EC	KF1lL.3s៤X^gAY|`#|M-S4jR?جEwy]8,\FQӰ[XEDW42"` zLny#L+!Ff8	t~Quk	gCv	&>Z4עƃ^G[c!|f8,zeQ?}-5{=L$%Ia#KIs[1{_fH@<q.
JEh "MALVwVQ^+6ᬅN*u.3(f gWkWVz9n
m!ʦ^K#k	uod*c]%0_aXu7R4%S򉐟j$AC?>o0\tۓ7GR;!1 BIԪno8'ђc/uǗr:*H`/Vv	 08	CNy[cPdX6N3%Lc;D="
=vC!Ӑzc7d$g;IAabĨުf^4EFq<n
,;ۡ2zՎ= ~#cKۯrK{Ñ9%1ݤIKƪ7#i Ltaj+t}E5fJ4:CNYeQ~q첞V[{}j:qWk=66c3_aQ|sU9ܻyOgNkcXlV4IG:tj_D}#2mZ^皒4]
	tY
eaF;S,L]㷡T{@]%i/>-5Ӻe_/Ħv	ݙ'T
Қ7/w|nVȪbdݝ;u_ݝr`g#UEi<%ӷn鼐Y[!=m2Vi	?U?QVՁn==y+ϣv6ze댔VZFj2+t͡N=G1,!xXX[D_<~"t&.~mU 9DY" OMwN4́=1	mؼ
qtZ
3n?9v>W{4zO.qmps]B,~8O"BܾYZӡ0p{n8uMRDWʭ.fâ^ZH̠hs2-U]ՉOg*ۨ*w4r[{5^2.4{2c]ؒ0g)|bȼP=)mDNɎY" te
t_400E@Rc?""9~Hljn%
ԆtvOe
%,"im[UG8zE3&miǝnVz1kE-QԲ7{z~]2vq4nzԐjT'ZCt^4:'4g4(}^RwW
C
^=krA(~ztu
#ݮn[D:r=|U<8fMZHAОvc(p%οVכ!KN»bMy/H<VC1RD5UiTL@J#60F`iE7SqYdz!>.8
Vkv4FQ5̴N)MѨ<N@QidGX%7mȵr3d(_J160
>E$wƚRS<ն;ʶT@C&CΔZý=VV.ivZfN6^ma2I@
<++ n1bO40}΢rG_&?>}{SruIl7w+fh3{3M-plgSxdl9D0 1q@+`kG,(.A۴P{jӍG$xq%e`˘6,K.govsf|Oqgq3g)90+p!dLI8Q2"R۵0ahS4ݺR\^KICcn2cf"	zZlQ(X,68ԥ)10fuɀay&A!X5M%fvV7t?~(b0`7Y\,^++^~]ꘅrTj 5_˟5͍"o*#/1oGUaGtdI^zPZʌ(QѺdCSky斗{1 6T{zD=2P