1 INFO-VAX	Wed, 19 Jul 2006	Volume 2006 : Issue 398       Contents:= Re: "OpenVMS - A System of Structure" published on OSNEWS.COM = Re: "OpenVMS - A System of Structure" published on OSNEWS.COM  2 CPU's in timeout on my ES40 ! Re: 2 CPU's in timeout on my ES40  Re: Alpha remembrance day  Another USB midnight project DECnet session timeout Re: DECnet session timeout Re: DECnet session timeout Re: DECnet session timeout DYNDNS client for OpenVMS? Re: DYNDNS client for OpenVMS? Re: DYNDNS client for OpenVMS?P Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in execP Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in execP Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in exec# Re: HP to cut down on telecommuting # RE: HP to cut down on telecommuting  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  RE: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Re: http://h71000.www7.hp.com/?  Monitor print queues Re: Monitor print queues Re: Netbeans BASIC plugin  Re: Netbeans BASIC plugin  Re: Netbeans BASIC plugin # USB temperature and humidity logger ' Re: USB temperature and humidity logger ' Re: USB temperature and humidity logger   F ----------------------------------------------------------------------    Date: 18 Jul 2006 13:27:14 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) F Subject: Re: "OpenVMS - A System of Structure" published on OSNEWS.COM3 Message-ID: <2dRWPCS5jE2A@eisner.encompasserve.org>   n In article <1153234320.846189.73730@m79g2000cwm.googlegroups.com>, "Bob Gezelter" <gezelter@rlgsc.com> writes:@ > OSNews.com has just published an article I wrote on OpenVMS at/ > http://www.osnews.com/story.php?news_id=15222    Yes, a very good job, Bob.  @ The content is not a surprise to participants in this newsgroup.@ The good job is in getting the material in front of people other than the existing fan base.    ------------------------------    Date: 18 Jul 2006 12:58:47 -0700$ From: "AEF" <spamsink2001@yahoo.com>F Subject: Re: "OpenVMS - A System of Structure" published on OSNEWS.COMC Message-ID: <1153252727.137527.206270@m73g2000cwd.googlegroups.com>    Bob Gezelter wrote: @ > OSNews.com has just published an article I wrote on OpenVMS at/ > http://www.osnews.com/story.php?news_id=15222  > & > - Bob Gezelter, http://www.rlgsc.com   -    Awesome! Thank you so much.    AEF    ------------------------------  % Date: Tue, 18 Jul 2006 13:45:34 -0400 * From: "Syltrem" <syltremzulu@videotron.ca>& Subject: 2 CPU's in timeout on my ES400 Message-ID: <12bq7easlsf9p4e@corp.supernews.com>  B Has anyone experienced CPU's ceasing to be in service on an ES40 ?  K I've never seen this before, there are no errors on the system or reported   by DIAG * 2 CPUs out of 4 are not working right now.   $ sh cpu    System: HELIOS, AlphaServer ES40   CPU ownership sets:     Active               0,2     Configure            0-3    CPU state sets:     Potential            0-3     Autostart            0-3     Powered Down         None    Not Present          None    Failover             None $ sh err, Device                           Error Count* $1$DQB0: (HELIOS)                        1* $1$DQB1: (HELIOS)                        1   I tried: $ set cpu/start 1 D %SYSTEM-W-WRONGSTATE, CPU 1 is in the wrong state for the requested 	 operation  $   K But I'm not familiar with these commands, such a problem never happened to   me (and we never had Galaxy)  G If you have an idea why this would be, and have a solution, pls write ! E Is this a situation where VMS needs to be rebooted just like Windows?   M The 2 CPUs may not have restarted since the system was powered back on after  H having failed because of the high temperature in the computer room. The J reading with f$getsyi("temperature_vector") showed 100 F at the time. The H system was rebooted when the temperature in the room started to go down.   Thanks   --   Syltrem L http://pages.infinit.net/syltrem (OpenVMS information and help, en franais)   ------------------------------  # Date: Tue, 18 Jul 2006 22:26:21 GMT   From: John Santos <john@egh.com>* Subject: Re: 2 CPU's in timeout on my ES40* Message-ID: <hedvg.13299$A8.1535@trnddc02>   Syltrem wrote:D > Has anyone experienced CPU's ceasing to be in service on an ES40 ? > M > I've never seen this before, there are no errors on the system or reported  	 > by DIAG , > 2 CPUs out of 4 are not working right now. > 
 > $ sh cpu >     $ show cpu/full might tell more.  " > System: HELIOS, AlphaServer ES40 >  > CPU ownership sets:  >    Active               0,2  >    Configure            0-3  >  > CPU state sets:  >    Potential            0-3  >    Autostart            0-3  >    Powered Down         None >    Not Present          None >    Failover             None
 > $ sh err. > Device                           Error Count, > $1$DQB0: (HELIOS)                        1, > $1$DQB1: (HELIOS)                        1 > 
 > I tried: > $ set cpu/start 1 F > %SYSTEM-W-WRONGSTATE, CPU 1 is in the wrong state for the requested  > operation   C Maybe you need $ start/cpu?  The difference between "set cpu/start" A and "start/cpu", at lest in the online help, is clear as mud, but  they might do different things.    > $  > M > But I'm not familiar with these commands, such a problem never happened to   > me (and we never had Galaxy) > I > If you have an idea why this would be, and have a solution, pls write ! G > Is this a situation where VMS needs to be rebooted just like Windows?  > O > The 2 CPUs may not have restarted since the system was powered back on after  J > having failed because of the high temperature in the computer room. The L > reading with f$getsyi("temperature_vector") showed 100 F at the time. The J > system was rebooted when the temperature in the room started to go down. >  > Thanks >      --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Wed, 19 Jul 2006 00:45:39 -0400 ( From: Bill Todd <billtodd@metrocast.net>" Subject: Re: Alpha remembrance dayG Message-ID: <vK-dnXUVNo1pJSDZnZ2dnUVZ_tmdnZ2d@metrocastcablevision.com>   
 Andrew wrote:  > Bill Todd wrote: >> etmsreec@yahoo.co.uk wrote: >>> Well, that's one view. > 	 >>    Can K >>> you say "lack of applications"?  Can you say "lack of operating systems  >>> to run on it"?K >> Can you say "incompetent blowhard?"  I think David addressed that latter A >> chimera adequately, and given that one of said OSs was Windows H >> (including support of x86 application binaries) I'd say that puts theD >> former to rest as well (not to say that VMS and Tru64 didn't have? >> adequate application support in their own right, of course).  >> > ? > I read this post with some amusement for a number of reasons.   G Unfortunately, overlooking probably the best one - for which you would  * have had to have been looking in a mirror.   > I > 1.     One of the key reasons for the decline in the Alpha business was C > as the previous poster quite rightly stated the lack of software.   I Ah, well - taking a week off from debating with uninformed morons can be  F very relaxing, but they're usually right where you left them when you 
 come back.  I For the edification of the educable (a group which history suggests does  L not number you as a member), the main reasons for the decline of Alpha were:  C 1. The Great Palmer Contraction - the transformation of DEC from a  ? forward-looking aggressive (though not always ideally-focused)  G competitor to a multiple-amputee just trying to remain afloat.  No one  E on the inside mistook this for anything but what it was, so it seems  3 unlikely to have been missed by a lot of customers.   G 2.  The infamous mid-'90s 'affinity' program (a Wes Melling Production  G IIRC), which encouraged the VMS community to switch to NT on Alpha - a  B great way to turn much of a loyal and robust customer base into a D combination of skittish stalwarts and disenchanted ex-users, and to I stall the growth of a leading OS without much compensating return (NT on  @ Alpha never having come close to taking up the resulting slack).  H 3.  The drastic loss of VMS development momentum at the end of the '90s F (more handwriting on the wall for Alpha's primary OS for those paying H attention).  When 'supporting new hardware' becomes the main attraction G of new releases rather than vigorous evolution of OS features in their  G own right to keep pace with the evolving OS competition, the new trend   line is clear.  H 4.  The Slough of Despond which Alpha entered immediately after Curly's A ascension to the throne, when both performance increases and new  I releases slowed to a crawl and allowed other platforms to challenge what  H had until then been the unquestioned industry performance leader.  What I better way to get people wondering about the real level of commitment of  < a corporation to an architecture?  Well, one could have been  I 5.  The butchering of Win64 (and Windows in general) on Alpha in August,  E 1999 - another Curly brain-fart which managed to call Alpha's future  I into such question that the infamous "Commitment to Alpha" letter had to  1 be written in an attempt to quell customer fears.   E 6.  The Unix vacillations which first embraced MIPS as the corporate  I Unix platform and then haltingly switched to Alpha after that damage had  E been done.  It took Digital Unix sales years to recover, but recover  I they eventually did:  while Tru64 had only about 1/3 the market share of  H AIX, or HP-UX, or Solaris as of Y2K, it was growing far faster than any 6 of them and threatening to overtake VMS revenues until  D 7.  The Alphacide, of course - a fine way to kill such a resurgence.  F The fact that DECpaq's Alpha system business remained one of its most H profitable hardware franchises despite those first six major handicaps, D and that its Tru64 business eventually attained robust growth, is a F testament to Alpha's (and its OSs') continuing perceived strength and C potential in the eyes of customers and their willingness to try to  F leverage them.  Perhaps a 'lack of applications' was some part (along H with the other problems noted above) of what kept Tru64 from growing at F *more* than the 30% annual rate it was achieving shortly prior to the ? Alphacide, but it sure as hell wasn't contributing to anything  @ resembling a 'decline' in either absolute or market-share terms.   - bill   ------------------------------  % Date: Tue, 18 Jul 2006 11:21:21 -0400 , From: Forrest Kenney <Forrest.Kenney@hp.com>% Subject: Another USB midnight project & Message-ID: <44BCFC71.27C1B671@hp.com>  @ 	The OpenVMS USB midnight software team, the folks that brought A you the USB postal scale, USB Joystick, and other unofficial USB  A goodies has a new item.  The USB temperature and humidity logger. F Built around the Lascar Electronics El-USB-2 temperature and humidity  logger.   < 	What is available is code that uses the USB generic driver D to configure and read data out of the logger.  This midnight projectA was completed to late to make it into the V8.3 USB demo software  @ directory in SYS$EXAMPLES.  It should make it into the examples  directory in the future.  : 	I can think of a number of useful things one could build D using the logger and this demo code.  The hard part is done sorting C out the protocol and data formats.  Now to come up with real world  - useful code to take advantage of this device.   9 	Past USB midnight products that are now part of OpenVMS   include:   	USB mass storage driver 	Joystick driver# 	USB to RS232 controllers based on   		Prolific PL2303 
 		FTDI 232   Forrest Kenney' OpenVMS head midnight USB device person    ------------------------------  # Date: Wed, 19 Jul 2006 01:01:08 GMT " From: reed@forge.{fe}.net (Brian ) Subject: DECnet session timeout , Message-ID: <2ea0p3-9k4.ln1@server.iron.net>  1 I have 2 VAXstation 4000/60 machines, VMS 5.5 era   ; I have node A that occasionally we have to halt the CPU on. : I use node B as a remote terminal, and set host to node A.B If node A is halted too long, then the sessions go away on node B.  E I see in NCP there is an outgoing timer setting, however that implies E it is for making a new connection, as I read it.  I didn't run across C any other settings that sound applicable, like a keepalive setting.   C So, what can I set, so that the remote sessions don't timeout when  A node A is halted, and not responding?  I would assume I would set E this on node B, unless when node A is continued that it might timeout  also upon checking the timers.   ------------------------------  % Date: Tue, 18 Jul 2006 20:53:08 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net># Subject: Re: DECnet session timeout 0 Message-ID: <44BD9084.6F78D026@spam.comcast.net>   Brian wrote: > 3 > I have 2 VAXstation 4000/60 machines, VMS 5.5 era  > = > I have node A that occasionally we have to halt the CPU on. < > I use node B as a remote terminal, and set host to node A.D > If node A is halted too long, then the sessions go away on node B. > G > I see in NCP there is an outgoing timer setting, however that implies G > it is for making a new connection, as I read it.  I didn't run across E > any other settings that sound applicable, like a keepalive setting.  > D > So, what can I set, so that the remote sessions don't timeout whenC > node A is halted, and not responding?  I would assume I would set G > this on node B, unless when node A is continued that it might timeout   > also upon checking the timers.  / In NCP, see HELP SET EXECUTOR INACTIVITY TIMER.    Why must you halt the CPU?   --   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: Wed, 19 Jul 2006 03:28:25 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com># Subject: Re: DECnet session timeout 0 Message-ID: <tFhvg.740$nk4.243@news.cpqcorp.net>   Brian wrote:3 > I have 2 VAXstation 4000/60 machines, VMS 5.5 era   <    Are these systems locked in on OpenVMS VAX V5.5, or is an< upgrade to something somewhat more recent feasible?  (If the: upgrade is feasible, tools such as AMDS can potentially be  brought to bear on the problem.)  = > I have node A that occasionally we have to halt the CPU on.   >    The obvious question being the background around why Node A: is halted.  And is this a halt followed by a console-level) continue, or a halt followed by a reboot?   < > I use node B as a remote terminal, and set host to node A.  &    SET HOST, or SET HOST [/qualifier]?  D > If node A is halted too long, then the sessions go away on node B.  C    If you have sessions from B to A, and A halts, then DECnet will  B detect this and will drop the connections back to B.  This is the   expected and intended behaviour.  H As I recall, there are connection timers that can be increased, but I'd C first tend to look at the specific need around halting the node --  H setting the DECnet timers longer also hampers the detection of problems G not caused by a processor halt; it delays the response to a crash, for  H instance.  (Longer timers tended to be of interest back in this vintage . when DECnet was in use over a satellite link.)  G    The other option is to use a serial connection via terminal server,  E for instance, into the console line on the VAXstation 4000 model 60.  H This won't drop when the system halts, and you can also remotely manage C the box this way.  (Do be careful around the security here, as the  E console line is fully privileged.  The console is also the only line  B that gets certain critical diagnostic messages, should the system , encounter certain severe resource problems.)   ------------------------------  # Date: Wed, 19 Jul 2006 04:01:13 GMT " From: reed@forge.{fe}.net (Brian )# Subject: Re: DECnet session timeout , Message-ID: <h6m0p3-gm6.ln1@server.iron.net>  i In article <44BD9084.6F78D026@spam.comcast.net>, "David J. Dachtera" <djesys.no@spam.comcast.net> writes: 7 >From: "David J. Dachtera" <djesys.no@spam.comcast.net> $ >Subject: Re: DECnet session timeout > 
 >Brian wrote:  >>  4 >> I have 2 VAXstation 4000/60 machines, VMS 5.5 era >>  > >> I have node A that occasionally we have to halt the CPU on.= >> I use node B as a remote terminal, and set host to node A. E >> If node A is halted too long, then the sessions go away on node B.  >>  H >> I see in NCP there is an outgoing timer setting, however that impliesH >> it is for making a new connection, as I read it.  I didn't run acrossF >> any other settings that sound applicable, like a keepalive setting. >>  E >> So, what can I set, so that the remote sessions don't timeout when D >> node A is halted, and not responding?  I would assume I would setH >> this on node B, unless when node A is continued that it might timeout! >> also upon checking the timers.  > 0 >In NCP, see HELP SET EXECUTOR INACTIVITY TIMER. >  >Why must you halt the CPU?   F We have some equipment that runs on unibus, and plugs into an adapter.D If you don't halt it before powering off the external equipment, the' power glitch will reset the VAXstation.   I In the old days, with the PDP, it ran on unibus, so the equipment plugged J straight into the bus on the PDP, so I could see why that caused an issue.D I would have thought the adapter on the VAXstation would isolate theE VAXstation bus from the unibus, but I don't know just how it is made.    ------------------------------    Date: 18 Jul 2006 14:26:43 -0700. From: "Julian Wolfe" <fireflyst@earthlink.net># Subject: DYNDNS client for OpenVMS? C Message-ID: <1153258003.391076.261200@s13g2000cwa.googlegroups.com>   	 HI there,   E I'm looking at putting my Alpha on the front end of my network for my F own general usage and web serving some small sites.  Is there a client$ around for using the DYNDNS service?   Any help would be appreciated.   Thanks!    Julian   ------------------------------  % Date: Tue, 18 Jul 2006 20:44:24 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net>' Subject: Re: DYNDNS client for OpenVMS? . Message-ID: <44BD8E78.F9EB00@spam.comcast.net>   Julian Wolfe wrote:  >  > HI there,  > G > I'm looking at putting my Alpha on the front end of my network for my H > own general usage and web serving some small sites.  Is there a client& > around for using the DYNDNS service? >   > Any help would be appreciated. > 	 > Thanks!  >  > Julian  C I'm using some code posted by Aaron Sakovich called DYNDNS_VMS.COM.   H Try Googling this group for it. I don't recall exactly how/where I found it.    --   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: Wed, 19 Jul 2006 03:31:11 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>' Subject: Re: DYNDNS client for OpenVMS? 0 Message-ID: <3Ihvg.741$nk4.344@news.cpqcorp.net>   Julian Wolfe wrote:   G > I'm looking at putting my Alpha on the front end of my network for my H > own general usage and web serving some small sites.  Is there a client& > around for using the DYNDNS service?  I    I've worked with a D-LINK firewall that appears able to provide that,  7 and the OpenVMS box can sit in the DMZ.  DFL-700, IIRC.   H    I don't know of a client for this for OpenVMS, however.  (But that's - also not something I've particularly sought.)    ------------------------------    Date: 18 Jul 2006 11:04:40 -0700 From: fkburrie@yahoo.co.ukY Subject: Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in exec A Message-ID: <1153245880.045529.56840@35g2000cwc.googlegroups.com>   L >    The obvious question being here, what might this exit handler be doing? The answer: E For our SCADA system we use this tailormade program. This program was F originally developed for VAX in the early half of the 90's, some yearsF ago it had a midlife update to Alpha. Currently running version 7.3.1.E The program consists of a "realtime" distributed database that partly D runs in executive mode and sometimes, when it becomes critical, runs? with asts disabled. For logging purposes condition handlers are G established for the several access modes. From these condition handlers D either a file is created in which the traceback will be dumped (userE mode) or in which the sig/mec arrays are being dumped. Until recently F this implementation was fine - because in all these years we never hadF an error while in executive mode with asts disabled! Now we have foundG the ommission at this stage we want to correct it; mainly because it is > definitely unwanted that the program will hang during logging.  F I will experiment with the suggested solutions. I can mix C in Pascal,E so maybe I can use the C version of tr_print in pascal. But, if the C - RTL can be used than also fopen can be used??    Thx,   Frank Burrie   ------------------------------    Date: 18 Jul 2006 11:04:36 -0700 From: fkburrie@yahoo.co.ukY Subject: Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in exec C Message-ID: <1153245876.306980.218070@h48g2000cwc.googlegroups.com>   L >    The obvious question being here, what might this exit handler be doing? The answer: E For our SCADA system we use this tailormade program. This program was F originally developed for VAX in the early half of the 90's, some yearsF ago it had a midlife update to Alpha. Currently running version 7.3.1.E The program consists of a "realtime" distributed database that partly D runs in executive mode and sometimes, when it becomes critical, runs? with asts disabled. For logging purposes condition handlers are G established for the several access modes. From these condition handlers D either a file is created in which the traceback will be dumped (userE mode) or in which the sig/mec arrays are being dumped. Until recently F this implementation was fine - because in all these years we never hadF an error while in executive mode with asts disabled! Now we have foundG the ommission at this stage we want to correct it; mainly because it is > definitely unwanted that the program will hang during logging.  F I will experiment with the suggested solutions. I can mix C in Pascal,E so maybe I can use the C version of tr_print in pascal. But, if the C - RTL can be used than also fopen can be used??    Thx,   Frank Burrie   ------------------------------    Date: 18 Jul 2006 11:04:42 -0700 From: fkburrie@yahoo.co.ukY Subject: Re: File I/O in Pascal, Exec-Mode, ASTs disabled (was: Re: File io while in exec C Message-ID: <1153245881.952647.218710@h48g2000cwc.googlegroups.com>   L >    The obvious question being here, what might this exit handler be doing? The answer: E For our SCADA system we use this tailormade program. This program was F originally developed for VAX in the early half of the 90's, some yearsF ago it had a midlife update to Alpha. Currently running version 7.3.1.E The program consists of a "realtime" distributed database that partly D runs in executive mode and sometimes, when it becomes critical, runs? with asts disabled. For logging purposes condition handlers are G established for the several access modes. From these condition handlers D either a file is created in which the traceback will be dumped (userE mode) or in which the sig/mec arrays are being dumped. Until recently F this implementation was fine - because in all these years we never hadF an error while in executive mode with asts disabled! Now we have foundG the ommission at this stage we want to correct it; mainly because it is > definitely unwanted that the program will hang during logging.  F I will experiment with the suggested solutions. I can mix C in Pascal,E so maybe I can use the C version of tr_print in pascal. But, if the C - RTL can be used than also fopen can be used??    Thx,   Frank Burrie   ------------------------------  % Date: Tue, 18 Jul 2006 23:06:41 -0400 / From: "William Webb" <william.w.webb@gmail.com> , Subject: Re: HP to cut down on telecommutingI Message-ID: <8660a3a10607182006r27db4075l5785fa45fec21264@mail.gmail.com>   2 On 7/16/06, Main, Kerry <Kerry.Main@hp.com> wrote: >  > > -----Original Message-----6 > > From: Steve Matzura [mailto:number6@speakeasy.net]  > > Sent: July 15, 2006 10:09 PM > > To: Info-VAX@Mvb.Saic.Com 0 > > Subject: Re: HP to cut down on telecommuting > > G > > This is a trend I'm finding is taking hold across the VMS board.  I E > > was just recently let go from a job where I'd been asking for the J > > ability to telecommute since '99. Unfortunately, it was 9/11 that gaveF > > me that ability when the building in which my ofice was housed wasI > > closed for three months thereafter while they cleaned it up. After it I > > reopened in January, 2002, I worked at home at first two days a week, G > > then three, then I got a new supervisor who permitted me to work at I > > home full time.  It was the best possible situation for both sides--I I > > was available for more hours per day, which was good for the company, H > > and I got to lose a commute with which I really couldn't deal due toJ > > physical limitations, which was good for me.  Since my separation fromH > > this company earlier this year, I've been looking for VMS work whereH > > telecommuting is embraced, but there's a trend going on out there toH > > bring everybody back into the ofice that very well may spell the endJ > > of this 25-year VMS professional's work life. And here I thought I had* > > at least another decade or more to go. > > 0 > > On Mon, 05 Jun 2006 16:44:09 -0400, JF Mezei) > > <jfmezei.spamnot@teksavvy.com> wrote:  > > A > > >http://www.mercurynews.com/mld/mercurynews/news/14732974.htm  > > > > > > >About 1000 employess in the IT division will no longer be > > able to workF > > >from home. Those who don't accept to work in one of 25 designated. > > >offices will be let go without severance. > > > 7 > > >Not known if this is to spread to other divisions.  > > > E > > >HP had been a world leader in flexible work rules startting with G > > >introduction of flextime back in 1967. Last July, they hired an ex J > > >Walmast IT director and it seems he doesn't believe in telecommuting. > >  > >  > F > There is always going to be some debate which is better, but this isE > only one division in HP doing this that I know of. Others have very G > openly embraced the virtual work from home strategy. Indeed, facility H > closures are usually based on this virtual work closure concept as theH > cost of facilities is just way to big of a cost. It assumes a relativeI > ratio of 3-5 (or higher) workers per virtual work "pod" and if everyone H > had to go back into the office, then new facilities would be required. > C > For DR scenario's, you need to have an established work from home D > infrastructure as workers may not be able to physically get to theJ > backup site. In addition, if everyone is in the office at the same time,J > it further raises the risk of a significant event impacting the majority > of your workers. > G > Think of a single person walking into your office facility and Health I > authorities find out he/she was exposed to SARS. They may not even have F > it - simply being exposed is enough to close the entire building andG > send *everyone* in that entire building home for 10 days minimum. For I > those who have not lived through SARS type events, that is the accepted 
 > process. > D > This SARS / pandemic worry is not theory - it actually happened inG > Toronto. The entire facility was closed and everyone sent home for 10 I > days. It just so happened that a data center was also in that building. H > The DC had to be vacated immediately (no backups, no gathering tapes -I > just leave now!) and closed to all physical access for 10 days as well. J > Fortunately, the DC was part of a dual site design and the workers couldH > continue working from home along with staff at the other facility, butA > how many companies have this multi-site + remote work from home  > capability today?  > J > It is also why new DC's being built today should be dedicated structuresE > away from major centers and that do not have any shared access with   > other tenants or office space.  ! Aaah, the circle of life.  Or DP.   N Sounds like the trend is to return to the days of glass walls and white coats.   :-)    WWWebb   > 	 > Regards  >  > Kerry Main > Senior Consultant  > HP Services Canada > Voice: 613-592-4660  > Fax: 613-591-4477  > kerryDOTmainAThpDOTcom > (remove the DOT's and AT)  > 6 > OpenVMS - the secure, multi-site OS that just works. >      --  C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Wed, 19 Jul 2006 00:01:15 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> , Subject: RE: HP to cut down on telecommutingT Message-ID: <FA60F2C4B72A584DBFC6091F6A2B86840177AC0E@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: William Webb [mailto:william.w.webb@gmail.com]=20  > Sent: July 18, 2006 11:07 PM > To: Info-VAX@Mvb.Saic.Com . > Subject: Re: HP to cut down on telecommuting >=204 > On 7/16/06, Main, Kerry <Kerry.Main@hp.com> wrote: > >   	 [snip...]    > : > > It is also why new DC's being built today should be=20 > dedicated structuresG > > away from major centers and that do not have any shared access with " > > other tenants or office space. >=20# > Aaah, the circle of life.  Or DP.  >=20B > Sounds like the trend is to return to the days of glass walls=20 > and white coats. >=20 > :-)  >=20 > WWWebb >=20  H Yep, I am getting a bit cranky with DC strategies and some Cust's reallyG hate what I tell them .. Like zero tours of their DC facility - if some C exec wants to show off whats inside the room, then install cameras.   H Bottom line is that every time you have a non-essential person enter theG DC facility, you increase the risk of closing that facility due to some G exotic pandemic issue that the person *may* have been exposed to in the 3 last number of days. Why take unnecessary risks?=20   F Same goes for developers that like to "reach out and touch the system"D occasionally. Take their access away and let Operations staff do anyG hands on work. That usually strikes up a few conversations with the dev  staff ..   :-)    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  % Date: Tue, 18 Jul 2006 15:15:35 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ( Subject: Re: http://h71000.www7.hp.com/?, Message-ID: <44BD3351.AECC0B5A@teksavvy.com>   w_tom wrote:G >   EMP is so trivial that even an NE-2 neon glow lamp (a bulb rated in B > milliamps) will make such transients irrelevant.  If a transientH > overwhelmed protection already inside appliances, this it was not EMP. > It was a direct strike.   C This is not as simple. In the 1980s, much of quebec was thrown into H darkness because of aurora borealis a few thousand km north of montreal.> Those induced currents into the power lines from james bay andC protective circuits automatically shut then down and Hydro Qubec's H software was ill conceived to automatically start load shedding and as aE result crashed everything. (our software was fixed since then, but in A ontario and north east USA they obviously had not fixed that load @ shedding software a couple years ago during a hot summer's day).  H The aurora borealis did not induce destructive currents, but the systems8 detected an anomaly in currents and shut the line down.   F Now, imagine the line between the home and the barn. Imagine that withF time, the ground at the barn becomes corroded and contact is no longerD really good and your switch there is no longer properly grounded and( some fuse blows to protect the circuits.      E > directly into electronics.  With only one AC electric wire grounded 1 > means AC electric is not sufficiently earthed.    G Well, if you ground all three of the 2 phase wires that come into north E american homes, the electric utility will either love you because you E your huge electric consumption/bills, or will hate you because you're  shorting their grid :-)    ------------------------------  % Date: Tue, 18 Jul 2006 15:18:28 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ( Subject: Re: http://h71000.www7.hp.com/?, Message-ID: <44BD33FE.F6C58C19@teksavvy.com>   "Main, Kerry" wrote:E > That is the job of those being paid to manage stuff like this. Some H > monitoring processes in place did not work as expected and from what I4 > have heard, steps are being taken to address this. > H > If HP or any other business had to rely on a Cust notifying them of an? > IT failure, then that would be a very poor IT infrastructure.   D RELY ? No. But there should be an easy way to notify a business of aF problem being seen by customers and not necessarily detected in-house.A In the end, having the lwoer downtime is more important than some = artificial pride of being able to detect problem on your own.   G I have seen many examples where those "alarm systems" did not detect or  alert the people of a failure.    B > Mmm .. Kind of why we stress DT solutions - not just DT systems.  G And very bad publicity for this type of service when your own DT people F coudn't detect the failure of a crucial node (switch) that fed a whole	 web site.    ------------------------------  % Date: Tue, 18 Jul 2006 16:32:49 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ( Subject: Re: http://h71000.www7.hp.com/?9 Message-ID: <3bqdnWX9NfFj3iDZnZ2dnUVZ_rqdnZ2d@libcom.com>    JF Mezei wrote:  > w_tom wrote:H >>   EMP is so trivial that even an NE-2 neon glow lamp (a bulb rated inC >> milliamps) will make such transients irrelevant.  If a transient I >> overwhelmed protection already inside appliances, this it was not EMP.  >> It was a direct strike. > E > This is not as simple. In the 1980s, much of quebec was thrown into J > darkness because of aurora borealis a few thousand km north of montreal.@ > Those induced currents into the power lines from james bay andE > protective circuits automatically shut then down and Hydro Qubec's J > software was ill conceived to automatically start load shedding and as aG > result crashed everything. (our software was fixed since then, but in C > ontario and north east USA they obviously had not fixed that load B > shedding software a couple years ago during a hot summer's day). > J > The aurora borealis did not induce destructive currents, but the systems: > detected an anomaly in currents and shut the line down.  > H > Now, imagine the line between the home and the barn. Imagine that withH > time, the ground at the barn becomes corroded and contact is no longerF > really good and your switch there is no longer properly grounded and* > some fuse blows to protect the circuits. >  >  > F >> directly into electronics.  With only one AC electric wire grounded2 >> means AC electric is not sufficiently earthed.  > I > Well, if you ground all three of the 2 phase wires that come into north G > american homes, the electric utility will either love you because you G > your huge electric consumption/bills, or will hate you because you're  > shorting their grid :-)   B It's my understanding, (note, I'm not an expert), that lightening 6 doesn't travel inside a wire, it rides on the outside.  G If I'm correct, then a simple grounded collar on the wire should strip  L the lightening off the wire, if the collar provides a better path to ground.  & You don't physically ground all wires.  # Dave, just a victim, not an expert.    --  4 David Froble                       Tel: 724-529-0450> Dave Froble Enterprises, Inc.      E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc.  170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Tue, 18 Jul 2006 16:10:38 -0500 $ From: Bud-- <remove.BudNews@isp.com>( Subject: Re: http://h71000.www7.hp.com/?9 Message-ID: <9a72f$44bd4a3c$4213eab7$21018@DIALUPUSA.NET>    w_tom wrote: > I >   Electronics already contain internal protection.  Protection that can F > be overwhelmed if a destructive surge is not earthed before enteringI > the building.  My apathy for adjacent protectors is because anything at G > the electronics that will protect those electronics is already inside A > electronics.  Experience has demonstrated how adjacent (and not I > earthed) protectors even contributed to damage of adjacent (and powered  > off) electronics.  >   ' I expect that is antipathy, not apathy.   I The IEEE and the NIST both say plug-in point-of-use surge protectors are  
 effective.  4 The best paper I have seen on surge protection is atQ http://www.mikeholt.com/files/PDF/LightningGuide_FINALpublishedversion_May051.pdf 2 - this a paper w_tom originally provided a link to@ - the title is "How to protect your house and its contents from H lightning: IEEE guide for surge protection of equipment connected to AC ! power and communication circuits" & - it was published by the IEEE in 2005   A second reference is ? http://www.nist.gov/public_affairs/practiceguides/surgesfnl.pdf G - this is the "NIST recommended practice guide: Surges Happen!: how to  $ protect the appliances in your home"I - it is published by the National Institute of Standards and Technology,  I the US government agency formerly called the National Bureau of Standards  - it was published in 2001  I Both guides were intended for wide distribution to the general public to  C explain surges and how to protect against them. The IEEE guide was  G targeted at people who have some (not much) technical background. Read  2 one (or both) to understand surges and protection.  1 Both say plug-in surge suppressors are effective.   C Note that if a device, like a computer, has connections other than  E power, like LAN, it has to be connected through the surge suppressor  D also. This type of suppressor is called a surge reference equalizer E (SRE) by the IEEE (also described by the NIST). The idea is that all  I wires connected to the device (power, phone, CATV, LAN, ...) are clamped  B to the common ground at the SRE. The voltage on all wires passing F through the SRE to the protected device are held to a voltage safe to  the device.    >  > Dave Froble wrote: > A >>I seem to remember your apathy for the battery backup and surge  >>protection units.  :-) >>I >>Still, one does what one can.  I have the units supplying power to most D >>electronics.  I use the RJ45 ports in the units for network lines. >>I >>The problem is that I'm connecting 4 buildings via underground conduit. J >>  Not very far underground.  I think one is about 6 inches deep, another >>maybe 12 inches. >>G >>Electrical entrances are all properly grounded.  The phone lines have D >>the protection you mentioned.  Unless there is a direct contact, IJ >>should be protected.  I'm thinking that the several hundred feet in eachF >>conduit just might be picking up an EMP.  I never would have thoughtI >>this would happen, but I can not find anywhere in the system that isn't  >>protected. >>  B In addition to direct pickup in the network wires, the grounds at G different buildings can be at significantly different potentials. This  E can be caused by earth current resulting from a lightning strike, or  I other cause. That ground potential difference would appear at a computer  G between the power and LAN connection. Incoming LAN wires should have a  D protector block with short ground conductor run to electric service I grounding electrode conductor, like phone wires. And/or SRE at computer.  4 Using fiber optic would be another fix, or wireless.   bud--    ------------------------------  % Date: Tue, 18 Jul 2006 17:20:25 -0400 ' From: "Main, Kerry" <Kerry.Main@hp.com> ( Subject: RE: http://h71000.www7.hp.com/?T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B86840177AB3C@tayexc19.americas.cpqcorp.net>   > -----Original Message-----9 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20  > Sent: July 18, 2006 3:18 PM  > To: Info-VAX@Mvb.Saic.Com * > Subject: Re: http://h71000.www7.hp.com/? >=20 > "Main, Kerry" wrote:G > > That is the job of those being paid to manage stuff like this. Some A > > monitoring processes in place did not work as expected and=20 
 > from what I 6 > > have heard, steps are being taken to address this. > >=20B > > If HP or any other business had to rely on a Cust notifying=20 > them of anA > > IT failure, then that would be a very poor IT infrastructure.  >=20F > RELY ? No. But there should be an easy way to notify a business of aH > problem being seen by customers and not necessarily detected in-house.C > In the end, having the lwoer downtime is more important than some ? > artificial pride of being able to detect problem on your own.  >=20B > I have seen many examples where those "alarm systems" did not=20 > detect or   > alert the people of a failure. >=20  F Well, there is also the contact Webmaster link on the main HP web site under contacts.    >=20D > > Mmm .. Kind of why we stress DT solutions - not just DT systems. >=20B > And very bad publicity for this type of service when your own=20 > DT people H > coudn't detect the failure of a crucial node (switch) that fed a whole > web site.  >=20  C No excuses, but as I mentioned, there were management processes and H tools in place that failed to work as expected. As I understand it, this is being addressed.    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  # Date: Tue, 18 Jul 2006 22:04:02 GMT   From: John Santos <john@egh.com>( Subject: Re: http://h71000.www7.hp.com/?* Message-ID: <mVcvg.13055$A8.9661@trnddc02>   Dave Froble wrote: > JF Mezei wrote:  >  >> w_tom wrote:  >>I >>>   EMP is so trivial that even an NE-2 neon glow lamp (a bulb rated in D >>> milliamps) will make such transients irrelevant.  If a transientJ >>> overwhelmed protection already inside appliances, this it was not EMP. >>> It was a direct strike.  >> >>F >> This is not as simple. In the 1980s, much of quebec was thrown intoK >> darkness because of aurora borealis a few thousand km north of montreal. A >> Those induced currents into the power lines from james bay and F >> protective circuits automatically shut then down and Hydro Qubec'sK >> software was ill conceived to automatically start load shedding and as a H >> result crashed everything. (our software was fixed since then, but inD >> ontario and north east USA they obviously had not fixed that loadC >> shedding software a couple years ago during a hot summer's day).  >>K >> The aurora borealis did not induce destructive currents, but the systems : >> detected an anomaly in currents and shut the line down.I >> Now, imagine the line between the home and the barn. Imagine that with I >> time, the ground at the barn becomes corroded and contact is no longer G >> really good and your switch there is no longer properly grounded and + >> some fuse blows to protect the circuits.  >> >> >>G >>> directly into electronics.  With only one AC electric wire grounded 3 >>> means AC electric is not sufficiently earthed.   >> >>J >> Well, if you ground all three of the 2 phase wires that come into northH >> american homes, the electric utility will either love you because youH >> your huge electric consumption/bills, or will hate you because you're >> shorting their grid :-) >  > D > It's my understanding, (note, I'm not an expert), that lightening 8 > doesn't travel inside a wire, it rides on the outside.  @ Skin effect?  That's still on the conductor, just at the surface  of the wire and not in its core.   > I > If I'm correct, then a simple grounded collar on the wire should strip  G > the lightening off the wire, if the collar provides a better path to  	 > ground.  >   ? Doesn't the (presumably) grounded service panel locate right at B the entrance to the house do this?  (I'm 99.99% sure code requiresD the service panel be grounded.)  All the wires run through knockouts@ in the metal wall of the panel, which creates a grounded collar.  ( > You don't physically ground all wires. >   < Or does each individual leg require a separate collar?  Even< so, if it is that easy, you would think it would be required> anywhere there's been a lightning storm in the last 100 years.9 (I.E. the entire planet except maybe parts of Anarctica!)       < If you actually need to ground each conductor, the way to do: it would be through a low-pass filter with the cutoff well< below 60Hz connect to the ground, or a high-pass filter with< the cutoff just below 60Hz in series with the AC circuit, or5 both.  Lightning is basically DC, so I think it would 9 induce a large DC pulse.  Electric power is AC, and would 9 see the low-pass filter as high-resistance.  (High enough ; impedance at 60 Hz and no appreciable power would be lost.) 7 AC would pass right through the high-pass filter but DC   would see it as an open circuit.  ; Whole house surge protectors seem to cost enough ($150-$200 < at Home Depot) that they probably consist of filters and not just a grounded collar.     : It's been 31 years since I studied electronics, so IANAEE!  % > Dave, just a victim, not an expert.  >      --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Wed, 19 Jul 2006 00:41:54 GMT # From: Beach Runner <bob@nospam.com> ( Subject: Re: http://h71000.www7.hp.com/?9 Message-ID: <mdfvg.11252$47.2252@tornado.tampabay.rr.com>    Mark Daniel wrote:  A > For an environment touting it's availability it's always a bit  K > disconcerting/disappointing/discouraging when the primary portal doesn't  J > respond.  Second time in almost as many weeks I've gone to check What's  > New and received no response.  > ! > KLAATU$ ping h71000.www7.hp.com 8 > PING openvms.compaq.com (161.114.65.60): 56 data bytes, > ----openvms.compaq.com PING Statistics----= > 4 packets transmitted, 0 packets received, 100% packet loss # > %SYSTEM-F-TIMEOUT, device timeout  >   1 Couldn't ping it, but I could open it no problem.   J > Not just my particular system or part of the Net either.  I've tried it * > from four hosts across three continents.   ------------------------------    Date: 18 Jul 2006 18:37:27 -0700 From: "w_tom" <w_tom1@usa.net>( Subject: Re: http://h71000.www7.hp.com/?C Message-ID: <1153273047.140728.323990@m73g2000cwd.googlegroups.com>    JF Mezei wrote: E > This is not as simple. In the 1980s, much of quebec was thrown into J > darkness because of aurora borealis a few thousand km north of montreal.@ > Those induced currents into the power lines from james bay andG > protective circuits automatically shut then down and Hydro Qu=E9bec's J > software was ill conceived to automatically start load shedding and as aG > result crashed everything. (our software was fixed since then, but in C > ontario and north east USA they obviously had not fixed that load F > shedding software a couple years ago during a hot summer's day). ...  F You are literally mixing apples and oranges.  Two completely different@ effects are discusses as if they were same.  They have differentE frequency domains.  One is on feet of wire; other on hundred miles of D wire.  Using your reasoning, I can also suggest that static electricF discharge can also upset the grid - the classic butterfly in ArgentianE creating a tornado in Oklahoma.  What happened in Quebec on a grid is * irrelevant to lightning inside a building.  B     Protection already inside electronics makes that nearby strikeD irrelevant.   Thousands of volts induced on an isolated wire becomesD only trivial volts when those few milliamps are conducted by an NE-2B glow lamp.   We install properly earthed protection to make directC strike irrelevant.  That means the induced transient is even moreso  irrelevant.   G   Meanwhile worry more about a different type of induced transient.  If G the wire earthing a direct lightning strike is bundled with other wires B (inches apart), then those other wires have a transient induced onD them.   Did you confuse that induced transient with fields that also  might create an aurora borealis?  G   Worry first about how or if each wire entering a building is properly D earthed either by hardwire or via a 'whole house' protector.  Ignore? other irrelevant rumors.  Concentrate on what really does shunt $ transients to earth without damage..   ------------------------------    Date: 18 Jul 2006 19:09:34 -0700 From: "w_tom" <w_tom1@usa.net>( Subject: Re: http://h71000.www7.hp.com/?C Message-ID: <1153274972.303143.140100@i42g2000cwa.googlegroups.com>    Dave Froble wrote:C > It's my understanding, (note, I'm not an expert), that lightening 8 > doesn't travel inside a wire, it rides on the outside. > H > If I'm correct, then a simple grounded collar on the wire should stripN > the lightening off the wire, if the collar provides a better path to ground. > ( > You don't physically ground all wires.  8   To enhance a protection system, industry professionalsF (www.polyphaser.com) sell bulkheads for wires to pass through; furtherD increase wire impedance; further encourage a transient to find earthF before entering a building. But still, that transient must be providedA a better path to earth.  Otherwise that bulkhead would accomplish  little.   G   Yes, you physically ground every wire either with a direct connection G (hardwire), or via a protector.  Appreciate what an effective protector  does: ,    http://www.telebyteusa.com/primer/ch6.htm< > Conceptually, lightning protection devices are switches to; > ground. Once a threatening surge is detected, a lightning : > protection device grounds the incoming signal connection; > point of the equipment being protected. Thus, redirecting 5 > the threatening surge on a path-of-least resistance - > (impedance) to ground where it is absorbed. 9 > Any lightning protection device must be composed of two : > "subsystems," a switch which is essentially some type of; > switching circuitry and a good ground connection-to allow " > dissipation of the surge energy.  E   Coax cable is literally connected direct to earth ground - needs no = protector.  Telephone line cannot make a hardwire connection. D Therefore the telco installs a 'whole house' protector (for free) toE ground each wire of their cable to your earthing electrode.  Earthing @ as defined by telebyteusa.com.  Earthing as in the most critical> component in every protection system as defined by an industry, benchmark, repeatedly, in application notes:-   http://www.polyphaser.com/ppc_ptd_home.aspx   ?   Those representing ineffective protectors (made obvious by no F dedicated earthing connection) hope you never learn what a responsibleG protector manufacturers connects to - single point earth ground.  Every E wire entering the building must either dump that transient into earth ? before the wire enters a building - or that transient will find + destructive paths via interior electronics.   C   Electricity travels outside the wire and in the skin of the wire. > Irrelevant to what you need know.  Protection means earthing aG transient long before that transient can overwhelm internal electronics > protection.  A non-destructive transient is made so by a wiredE connection to earth.  Literally, transient electricity is dumped into E earth at the service entrance or finds earth via your electronics.  A . principle demonstrated byBen Franklin in 1752.   ------------------------------  # Date: Tue, 18 Jul 2006 23:52:07 GMT % From: "The KGB" <kgb@tampabay.rr.com>  Subject: Monitor print queues 9 Message-ID: <Huevg.5756$Eh7.2082@tornado.tampabay.rr.com>   
 Hello all,L I need to monitor the number of pages a LPD printer in VMS/Cache prints per M job/day/month etc.  Anyone have a DCL program already in-place they would be   willing to share?    Many thanks  Kent     ------------------------------  % Date: Tue, 18 Jul 2006 20:46:57 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net>! Subject: Re: Monitor print queues 0 Message-ID: <44BD8F11.92541EC6@spam.comcast.net>   The KGB wrote: >  > Hello all,M > I need to monitor the number of pages a LPD printer in VMS/Cache prints per N > job/day/month etc.  Anyone have a DCL program already in-place they would be > willing to share?  > 
 > Many thanks  > Kent  # See HELP ACCOUNTING /REPORT Keyword    --   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: Tue, 18 Jul 2006 19:35:15 GMT ( From: "Meg Watson" <meg.watson@hpxx.com>" Subject: Re: Netbeans BASIC plugin0 Message-ID: <TJavg.695$aa4.271@news.cpqcorp.net>   Hi Rich,  H We are about to release Distributed NetBeans T5.0, which includes Basic L support as well as C/C++, Fortran, Cobol, and Pascal support.  We expect to M have a field test kit available in a few weeks.  I'll put your email address  ( on our notification list for field test.  1 Thanks for your interest in Distributed NetBeans!   
 Best Regards,   
 Meg Watson  Distributed NetBeans Engineering! HP OpenVMS Systems Software Group   4 "Rich Jordan" <jordan@ccs4vms.com> wrote in message < news:1153242963.599378.136330@35g2000cwc.googlegroups.com... >  > Rich Jordan wrote:D >> Back in 2001 the Netbeans announcement stated that BASIC would beF >> supported.  Last year (around May) there was a post that Pascal and> >> BASIC plugins were being worked on.  Any idea yet when they/ >> (specifically BASIC) will be made available?  >>
 >> Thanks! >> >> Rich Jordan >> CCS > D > Followup; I see that the 2006 release of Distributed Netbeans doesI > include the Pascal plugin.  So our remaining (critical for our own use) ; > holdout is BASIC.  Any info would be greatly appreciated.  >  > Rich >    ------------------------------    Date: 18 Jul 2006 12:48:08 -0700( From: "Rich Jordan" <jordan@ccs4vms.com>" Subject: Re: Netbeans BASIC pluginC Message-ID: <1153252087.970277.268700@i42g2000cwa.googlegroups.com>    Meg Watson wrote: 
 > Hi Rich, > I > We are about to release Distributed NetBeans T5.0, which includes Basic M > support as well as C/C++, Fortran, Cobol, and Pascal support.  We expect to N > have a field test kit available in a few weeks.  I'll put your email address* > on our notification list for field test. > 3 > Thanks for your interest in Distributed NetBeans!  >  > Best Regards,  >  > Meg Watson" > Distributed NetBeans Engineering# > HP OpenVMS Systems Software Group  >    Meg,C      thank you _very_ much.  We've been looking forward to at least E trying to work with this package for a long time, but 99% of our code @ is VAX BASIC (now on Alpha and moving to I64).  I await eagerly.   Rich   ------------------------------  # Date: Wed, 19 Jul 2006 01:54:28 GMT ; From: "Jeffrey H. Coffield" <jeffrey@digitalsynergyinc.com> " Subject: Re: Netbeans BASIC plugin> Message-ID: <ohgvg.70120$fb2.25272@newssvr27.news.prodigy.net>   Meg Watson wrote: 
 > Hi Rich, > J > We are about to release Distributed NetBeans T5.0, which includes Basic N > support as well as C/C++, Fortran, Cobol, and Pascal support.  We expect to O > have a field test kit available in a few weeks.  I'll put your email address  * > on our notification list for field test. >   E Please add jeffrey@digitalsynergyinc.com also. This is very exciting!    ------------------------------  # Date: Tue, 18 Jul 2006 20:25:11 GMT & From: John Reagan <john.reagan@hp.com>, Subject: USB temperature and humidity logger0 Message-ID: <Hsbvg.702$a74.279@news.cpqcorp.net>  I I'm posting this for Forrest who tried to post this but some news server  8 dropped it.  DO NOT send me USB or driver questions. :-)      G          The OpenVMS USB midnight software team, the folks that brought H you the USB postal scale, USB Joystick, and other unofficial USB goodies9 has a new item.  The USB temperature and humidity logger. E Built around the Lascar Electronics El-USB-2 temperature and humidity  logger.   F          What is available is code that uses the USB generic driver toE configure and read data out of the logger.  This midnight project was F completed to late to make it into the V8.3 USB demo software directoryF in SYS$EXAMPLES.  It should make it into the examples directory in the future.   G          I can think of a number of useful things one could build using E the logger and this demo code.  The hard part is done sorting out the F protocol and data formats.  Now to come up with real world useful code! to take advantage of this device.   @          Past USB midnight products that are now part of OpenVMS include:             USB mass storage driver          Joystick driver*          USB to RS232 controllers based on                   Prolific PL2303                  FTDI 232      Forrest Kenney' OpenVMS head midnight USB device person    ------------------------------  % Date: Wed, 19 Jul 2006 07:25:55 +0800 ) From: Tim Sneddon <tesneddon@bigpond.com> 0 Subject: Re: USB temperature and humidity logger9 Message-ID: <44bd6098$0$19666$88260bb3@free.teranews.com>    John Reagan wrote: >         [...snip...]    > Forrest Kenney) > OpenVMS head midnight USB device person   A Has anyone had a crack a getting the USB Missile Launcher running  on VMS? :-)   ( Linux software for controlling the unit:  ;      http://scott.weston.id.au/software/pymissile-20060126/   
 Regards, Tim.    --  = Posted via a free Usenet account from http://www.teranews.com    ------------------------------  % Date: Tue, 18 Jul 2006 20:41:31 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net>0 Subject: Re: USB temperature and humidity logger0 Message-ID: <44BD8DCB.8C60252F@spam.comcast.net>   John Reagan wrote: > J > I'm posting this for Forrest who tried to post this but some news server: > dropped it.  DO NOT send me USB or driver questions. :-) > I >          The OpenVMS USB midnight software team, the folks that brought J > you the USB postal scale, USB Joystick, and other unofficial USB goodies; > has a new item.  The USB temperature and humidity logger. G > Built around the Lascar Electronics El-USB-2 temperature and humidity 	 > logger.  > H >          What is available is code that uses the USB generic driver toG > configure and read data out of the logger.  This midnight project was H > completed to late to make it into the V8.3 USB demo software directoryH > in SYS$EXAMPLES.  It should make it into the examples directory in the	 > future.   : How 'bout posting it somewhere under the Freeware CD site?   ...on ftp.itrc.hp.com?   --   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/   ------------------------------   End of INFO-VAX 2006.398 ************************