1 INFO-VAX	Wed, 28 Jun 2006	Volume 2006 : Issue 356       Contents:  7.3-2 and DW-Motif 1.3.1 upgrade$ Re: 7.3-2 and DW-Motif 1.3.1 upgrade DEGPA-SA available Re: Floating point questions Floating point questions Re: Floating point questions Re: Floating point questions Re: Floating point questions Re: Floating point questions Re: Floating point questions Re: Floating point questions Re: Floating point questions) Re: New OpenVMS Virtualization Whitepaper ) Re: New OpenVMS Virtualization Whitepaper ' Re: OT: Intel quad core X64 benchmarked  VAX Open VMS Production Support # Re: VAX Open VMS Production Support # Re: VAX Open VMS Production Support # Re: VAX Open VMS Production Support # Re: VAX Open VMS Production Support # Re: VAX Open VMS Production Support  Re: [ECP] OpenVMS V8  F ----------------------------------------------------------------------    Date: 27 Jun 2006 19:14:18 -0700 From: tpercy23@hotmail.com) Subject: 7.3-2 and DW-Motif 1.3.1 upgrade B Message-ID: <1151460858.063112.20660@x69g2000cwx.googlegroups.com>  E After installing 7.3-2 os upgrade motif upgrades from 1.2-4 to 1.3.1. D My application is now crashing with a system-access violation, imageD decw$xtlibshrr5.  I have rebuilt and relinked and still getting same= error.  I am under some time contraint an don't have time for A debugging.  My questions are has anyone seen this before and does G anyone think if I reinstalled the old motif that it would work with the   new os?  Thanks for any help!!!!   ------------------------------    Date: 27 Jun 2006 21:49:34 -0700, From: "Cluster-Karl" <karl.rohwedder@gmx.de>- Subject: Re: 7.3-2 and DW-Motif 1.3.1 upgrade C Message-ID: <1151470174.433602.196380@y41g2000cwy.googlegroups.com>    tpercy23@hotmail.com schrieb:   G > After installing 7.3-2 os upgrade motif upgrades from 1.2-4 to 1.3.1. F > My application is now crashing with a system-access violation, imageF > decw$xtlibshrr5.  I have rebuilt and relinked and still getting same? > error.  I am under some time contraint an don't have time for C > debugging.  My questions are has anyone seen this before and does I > anyone think if I reinstalled the old motif that it would work with the " > new os?  Thanks for any help!!!!  B Pls. note that there is a ECO 2 available for Motif 1.3-1. It does7 replace the DECW$XTLIBSHRR5 images, perhaps this helps.    Link: e ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/DEC-AXPVMS-DWMOTIF_ECO02-V0103-1-4.PCSI-DCX_AXPEXE Y ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/DEC-AXPVMS-DWMOTIF_ECO02-V0103-1-4.txt   
 regards Kalle    ------------------------------  % Date: Tue, 27 Jun 2006 10:59:21 -0700 # From: "Tom Linden" <tom@kednos.com>  Subject: DEGPA-SA available ) Message-ID: <op.tbtf87rnzgicya@hyrrokkin>    Have three I don't need.  I http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3D190001935115&ssPage=  Name=3DADME:L:DS:US:8    Tom    ------------------------------  % Date: Tue, 27 Jun 2006 12:34:24 -0700 # From: "Tom Linden" <tom@kednos.com> % Subject: Re: Floating point questions ) Message-ID: <op.tbtknmqrzgicya@hyrrokkin>   / On Tue, 27 Jun 2006 12:16:08 -0700, JF Mezei  =   % <jfmezei.spamnot@teksavvy.com> wrote:   I > I have to talk to a device that does IEEE floating point in both 32 an=  d + > 64 bit forms. (but usually just 32 bits).  > C > On vax, I can use CVT$FTOF to convert to/from native VAX to IEEE.  > " > On vax, the DEC-C doc says that: > 5 > float  =3D 32 bits ( I assume VAX-F floating point)  > double =3D 64 bits? > long double =3D 64 bits and it says it is the same as double.  > I > For the 64 bit floats, I see both VAX-D and VAX-G types available. Whi=  ch2 > ones does DEC-C use for double and long-double ? > D > And if that program is compiled on an alpha, what does "float" and$ > "double" translate to by default ? > E > Since platforms post-alpha do not have support for the vax floating 1 > point type, it is fair to assume that on those:  > 		float =3D IEEE 32 bits > 		double =3D IEEE 64 bits ?  >  > G > Is there a way at compile time to know what type of floating point is ' > being used for "float" and "double" ? G > (since there are CC/FLOAT options, AND there are different platforms, I > how can one know what precise format is being used at the moment durin=  g  > this specicic compile ?) > F > Is it correct to state that if CVT$FTOF is asked to convert a 32 bitF > IEEE float to a 32 bit IEEE float, that it will just move the values6 > without any conversion or changing of the contents ? > G > (aka, the same code would convert from IEEE-32 to VAX-F on a VAX, but C > would convert from IEEE-32 to IEEE-32 on a platform where "float"  > defaults to IEEE-32).  >  >  > Also, if I am told that I > 	 "A value of 1.0e25 in this field indicates that this parameter is no=  t / > supported or is unknown for this trackpoint".  > 6 > Does this mean that I can check for a specific value > 7 > 	aka  if ( variable =3D=3D 1.0e25 ) then do something  > F > or must I assume that 1.0e25 is a "fuzzy" value and that I can neverI > really expect to have it precisely match that, especiually after going=    > though a CVT$FTOF ?    VAX supports F, D, G and H. 1 AXP supports F, S, D, G and T  (S and T are IEEE)   . You can not test for equality, you must write,#   if abs(variable-1.0e25) < epsilon I Based on what you are doing, you should be able to determine the value o=  f  =   the  constant epsilon.    ------------------------------  % Date: Tue, 27 Jun 2006 15:16:08 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ! Subject: Floating point questions , Message-ID: <44A183F0.FC6672E6@teksavvy.com>  G I have to talk to a device that does IEEE floating point in both 32 and ) 64 bit forms. (but usually just 32 bits).   A On vax, I can use CVT$FTOF to convert to/from native VAX to IEEE.     On vax, the DEC-C doc says that:  1 float  = 32 bits ( I assume VAX-F floating point)  double = 64 bits  ; long double = 64 bits and it says it is the same as double.   H For the 64 bit floats, I see both VAX-D and VAX-G types available. Which0 ones does DEC-C use for double and long-double ?  B And if that program is compiled on an alpha, what does "float" and# "double" translate to by default ?    C Since platforms post-alpha do not have support for the vax floating / point type, it is fair to assume that on those:  		float = IEEE 32 bits 		double = IEEE 64 bits ?     E Is there a way at compile time to know what type of floating point is % being used for "float" and "double" ? E (since there are CC/FLOAT options, AND there are different platforms, G how can one know what precise format is being used at the moment during  this specicic compile ?)  D Is it correct to state that if CVT$FTOF is asked to convert a 32 bitD IEEE float to a 32 bit IEEE float, that it will just move the values4 without any conversion or changing of the contents ?  E (aka, the same code would convert from IEEE-32 to VAX-F on a VAX, but A would convert from IEEE-32 to IEEE-32 on a platform where "float"  defaults to IEEE-32).      Also, if I am told that G 	 "A value of 1.0e25 in this field indicates that this parameter is not - supported or is unknown for this trackpoint".   4 Does this mean that I can check for a specific value  1 	aka  if ( variable == 1.0e25 ) then do something   D or must I assume that 1.0e25 is a "fuzzy" value and that I can neverF really expect to have it precisely match that, especiually after going though a CVT$FTOF ?    ------------------------------  % Date: Tue, 27 Jun 2006 12:27:16 -0700 ' From: "Dann Corbit" <dcorbit@connx.com> % Subject: Re: Floating point questions ( Message-ID: <e7s0i9$l71$1@nntp.aioe.org>  ; "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message  & news:44A183F0.FC6672E6@teksavvy.com...H >I have to talk to a device that does IEEE floating point in both 32 and+ > 64 bit forms. (but usually just 32 bits).  > C > On vax, I can use CVT$FTOF to convert to/from native VAX to IEEE.  > " > On vax, the DEC-C doc says that: > 3 > float  = 32 bits ( I assume VAX-F floating point)  > double = 64 bits= > long double = 64 bits and it says it is the same as double.  > J > For the 64 bit floats, I see both VAX-D and VAX-G types available. Which2 > ones does DEC-C use for double and long-double ?  , Depends on whether you used /G_FLOAT or not.  D > And if that program is compiled on an alpha, what does "float" and$ > "double" translate to by default ?   F & D, IIRC.  E > Since platforms post-alpha do not have support for the vax floating 1 > point type, it is fair to assume that on those:  > float = IEEE 32 bits > double = IEEE 64 bits ?   ; http://h71000.www7.hp.com/doc/82final/6673/6673pro_003.html   G > Is there a way at compile time to know what type of floating point is ' > being used for "float" and "double" ? G > (since there are CC/FLOAT options, AND there are different platforms, I > how can one know what precise format is being used at the moment during  > this specicic compile ?) > F > Is it correct to state that if CVT$FTOF is asked to convert a 32 bitF > IEEE float to a 32 bit IEEE float, that it will just move the values6 > without any conversion or changing of the contents ?  M It's just a library call.  It is going to assume you know what you are doing    when you pass something into it.  G > (aka, the same code would convert from IEEE-32 to VAX-F on a VAX, but C > would convert from IEEE-32 to IEEE-32 on a platform where "float"  > defaults to IEEE-32).  >  >  > Also, if I am told that G > "A value of 1.0e25 in this field indicates that this parameter is not / > supported or is unknown for this trackpoint".  > 6 > Does this mean that I can check for a specific value > 2 > aka  if ( variable == 1.0e25 ) then do something  L Checking floating point for equality is almost always a mistake.  This is a  case in point.  F > or must I assume that 1.0e25 is a "fuzzy" value and that I can neverH > really expect to have it precisely match that, especiually after going > though a CVT$FTOF ?   < http://h71000.www7.hp.com/doc/82final/6673/6673pro_003.html    ------------------------------  # Date: Tue, 27 Jun 2006 20:03:36 GMT & From: John Reagan <john.reagan@hp.com>% Subject: Re: Floating point questions 1 Message-ID: <sagog.2292$Nr3.978@news.cpqcorp.net>    Dann Corbit wrote:   > D >>And if that program is compiled on an alpha, what does "float" and$ >>"double" translate to by default ? >  >  > F & D, IIRC. >   : Nope.  The default on Alpha is F for single, G for double.  1 The default on I64 is S for single, T for double.    --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------  # Date: Tue, 27 Jun 2006 20:07:31 GMT & From: John Reagan <john.reagan@hp.com>% Subject: Re: Floating point questions 2 Message-ID: <7egog.2293$2r3.1493@news.cpqcorp.net>   JF Mezei wrote:   G > Is there a way at compile time to know what type of floating point is ' > being used for "float" and "double" ?   G Looking at a .LIS file from the C compiler, I see a __IEEE_FLOAT to be  F either 0 or 1; and a CC$gfloat to be 0 or 1.  Between the two symbols / you should be able to get all the combinations.    --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------  % Date: Tue, 27 Jun 2006 16:17:25 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> % Subject: Re: Floating point questions + Message-ID: <44A19249.2EF63EC@teksavvy.com>    Tom Linden wrote: 0 > You can not test for equality, you must write,% >   if abs(variable-1.0e25) < epsilon K > Based on what you are doing, you should be able to determine the value of  > the constant epsilon.     H This is what I thought. However, in this case, the GPS sets a field to aH specific value (not a calculated value). Wouldn't it then be a trustable value ?    eg:    	A = 1.0+ 	if( A == 1.0 ) then printf("Hello World");     B I fully understand that doing any math operation in floating pointA yields a fuzzy result that cannot be tested for equality. But can ? specifc constant values be represented precisely when those are 5 essentially large integers stored as floating point ?   B In the case where I do have to find the difference and test if theE difference is smaller than "epsilon",  how do I go about deciding the  value of epsilon ?  H Again, this is for a test of a specific constant value that the GPS uses( to indicate that this field is unusable.   ------------------------------  # Date: Tue, 27 Jun 2006 20:09:36 GMT & From: John Reagan <john.reagan@hp.com>% Subject: Re: Floating point questions 2 Message-ID: <4ggog.2294$2r3.1018@news.cpqcorp.net>   Tom Linden wrote:    >  > VAX supports F, D, G and H. 3 > AXP supports F, S, D, G and T  (S and T are IEEE)  >   > Don't forget X (IEEE eXtended) supported on Alpha in software.   and for completion  D OpenVMS I64 supports S and T in hardware; F, D, and G by conversion 3 to/from S and T; and X in software just like Alpha.      --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------  % Date: Tue, 27 Jun 2006 13:30:09 -0700 # From: "Tom Linden" <tom@kednos.com> % Subject: Re: Floating point questions ) Message-ID: <op.tbtm8jvjzgicya@hyrrokkin>   / On Tue, 27 Jun 2006 13:17:25 -0700, JF Mezei  =   % <jfmezei.spamnot@teksavvy.com> wrote:    > Tom Linden wrote: 1 >> You can not test for equality, you must write, & >>   if abs(variable-1.0e25) < epsilonI >> Based on what you are doing, you should be able to determine the valu=  e  =   >> of  >> the constant epsilon. >  > I > This is what I thought. However, in this case, the GPS sets a field to=   aI > specific value (not a calculated value). Wouldn't it then be a trustab=  le	 > value ?   ; Yes, provided it isn't converted from some other data type.  >  > eg:  >  > 	A =3D 1.01 > 	if( A =3D=3D 1.0 ) then printf("Hello World");  >  > D > I fully understand that doing any math operation in floating pointC > yields a fuzzy result that cannot be tested for equality. But can A > specifc constant values be represented precisely when those are 7 > essentially large integers stored as floating point ?  Of course, as in your example. > D > In the case where I do have to find the difference and test if theG > difference is smaller than "epsilon",  how do I go about deciding the  > value of epsilon ?I I don't believe a general answer is possible, it depends on what you are=    =    doing.D If you, for example, are solving an equation f(x) =3D 0 using say  =   Newton-RaphsonI then when x(n+1)-x(n) is less than epsilon then you have a solution.  Th=  e  =   value H of epsilon is determined by the required accuracy, constrained by the  =  	 precision H of the arithmetic employed and the error propogation generated by the  =  
 recursion.   > I > Again, this is for a test of a specific constant value that the GPS us=  es* > to indicate that this field is unusable.   ------------------------------  # Date: Tue, 27 Jun 2006 22:42:32 GMT % From: Rob Brown <mylastname@gmcl.com> % Subject: Re: Floating point questions E Message-ID: <Pine.LNX.4.61.0606271637210.22546@localhost.localdomain>   & On Tue, 27 Jun 2006, Tom Linden wrote:  N > On Tue, 27 Jun 2006 13:17:25 -0700, JF Mezei <jfmezei.spamnot@teksavvy.com>  > wrote: >  >> Tom Linden wrote:2 >>> You can not test for equality, you must write,' >>>   if abs(variable-1.0e25) < epsilon M >>> Based on what you are doing, you should be able to determine the value of  >>> the constant epsilon.  >>   >>  K >> This is what I thought. However, in this case, the GPS sets a field to a K >> specific value (not a calculated value). Wouldn't it then be a trustable 
 >> value ? > = > Yes, provided it isn't converted from some other data type.   F In this case, I will agree.  On the other hand, if the constant has a : fractional part, I think you cannot be sure.  For example:  #    0.4 (decimal) = 0.01100110011...   D If the guy who sets it uses a different number of bits than the guy 4 who checks it, or if they round differently, or ....   - Rob      --    B Rob Brown                        b r o w n a t g m c l d o t c o m6 G. Michaels Consulting Ltd.      (780)438-9343 (voice)4 Edmonton                         (780)437-3367 (FAX)2                                   http://gmcl.com/   ------------------------------  % Date: Tue, 27 Jun 2006 21:20:02 +0200 / From: Paul Sture <paul.sture.nospam@hispeed.ch> 2 Subject: Re: New OpenVMS Virtualization Whitepaper: Message-ID: <7d2e2$44a184e3$50db5015$2515@news.hispeed.ch>   Doug Phillips wrote:   > E > Maybe I just got a lucky card, but I got a Bingo on the first page!  > 1 > < http://isd.usc.edu/~karl/Bingo/bbbingo.html >  >   F "Sorry, your browser does not interpret JavaScriptTM or you have this D function turned off. Please go to  Mozilla for a copy of Mozilla or 	 FireFox."    ???    ------------------------------    Date: 27 Jun 2006 14:41:40 -0700- From: "Doug Phillips" <dphill46@netscape.net> 2 Subject: Re: New OpenVMS Virtualization WhitepaperC Message-ID: <1151444500.698408.242480@p79g2000cwp.googlegroups.com>    Paul Sture wrote:  > Doug Phillips wrote: >  > > G > > Maybe I just got a lucky card, but I got a Bingo on the first page!  > > 3 > > < http://isd.usc.edu/~karl/Bingo/bbbingo.html >  > >  > G > "Sorry, your browser does not interpret JavaScriptTM or you have this E > function turned off. Please go to  Mozilla for a copy of Mozilla or  > FireFox."  >  > ???    What "???" ?G    -- the JavaScript message? The site uses JavaScript, so if you don't @ have JavaScript installed or you have it turned off you get that message.G    -- the Mozilla /Firefox reference? Since you're using Thunderbird on ' your Mac, you likely know about Moz/FF.   E The link is to a "Buzzword Bingo" generator. Here's another if you're  still curious:  * < http://www.lurkertech.com/chris/bingo/ >  D This post was a follow-on to a thread back-a-bit where I stated that@ the word "virtualization" was just a buzzword because it doesn'tF actually describe anything specific. The white paper's first text page (pg.3) contains such as:  ; "...incompatible silos of IT infrastructure deployed around : the classic paradigm of disparate applications, databases,8 servers and networks.Companies need to be agile in their8 response to rapidly changing business/legislative/global8 demands and this is what virtualization and the Adaptive Enterprise address."  0 One square short of a bingo on that bit alone;-)  F But, since the first section is titled: "Executive Summary", buzzwordsD aren't a real bad thing. The rest of the WP goes on the explain (but7 not admit) in increasingly acronymic terms how the word E "virtualization" isn't actually one thing but that many of the things < we've known to be types of virtualization (VM's, Hard & Soft> partitions, etc) are part of HP's "Adaptive Enterprise" world.  E Just for fun, google the word "virtualization" at, say www.ibm.com as   ) Google [virtualization site:www.ibm.com ]   5 and also try some other well know makers of IT stuff.   F Buzzword. Everyone's using it to mean whatever they want it to mean so it doesn't mean anything.    ------------------------------  % Date: Tue, 27 Jun 2006 14:30:05 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 0 Subject: Re: OT: Intel quad core X64 benchmarked, Message-ID: <44A17927.53E2A7AF@teksavvy.com>   Alan Greig wrote:  > E > With the dual core Montecito finally about to appear, it seems that G > quad-core X64 Intel samples are out and about. There's a benchmark at E > http://www.xtremesystems.org/forums/showthread.php?p=1527913 if you  > haven't yet seen it.    F This will certaintly give the 8086 at the very least an image of beingH ahead of that IA64 thing which just now getting to dual core. The delays> in IA64 means that IA64 will never catch up and will always be considered an "also ran".   C And while Intel may not yet announce the end of IA64, I suspect its F reorg/streamlining will not add engineering resources to IA64, and mayA shift more of them to the 8086.  The question should now be asked F whether IA64 will be able to even keep up or whether the gap which hadE narrowed significantly since Merced will again start to grow, leaving   IA64 further and further behind.   ------------------------------    Date: 27 Jun 2006 12:26:28 -07004 From: "JasonatMISI" <jdruckenmiller@misicompany.com>( Subject: VAX Open VMS Production SupportC Message-ID: <1151436388.639331.219130@j72g2000cwa.googlegroups.com>   E Please forgive me if I am publishing this to the wrong group.  I have @ the following spot I am trying to staff and am having difficulty< finding people.  If anyone is interested please let me know.   Location: Jersey City, NJ  Duration: 10 months    Description:G As part of the Large Midrange Open VMS team, this position will provide F Sr. Level systems management, support, and engineering of the Open VMSG (DEC VAX) enterprise. This role is responsible for all Open VMS Servers @ and their peripherals throughout our client. These servers houseE several of our client's critical business applications with financial E activity within these systems, in the trillions of dollars on a daily A basis. Duties include the systems management at all levels of the D existing OVMS structure, research, development and implementation ofF new technology solutions, day to day production support, level two andE three on-call production support for system interruptions, day-to-day @ day operational aspects of providing infrastructure hardware andE software support which includes system management and administration, E database administration, system support tools, performance tuning and ? capacity planning, automation, and business application support    QualificationsD Ideal candidate to have 15 or more years of OVMS systems engineeringE experience, including 5 or more years of Sr. Level Systems Management 2 experience in complex large-scale IT environments.C Expertise in midrange engineering with HP VAX and Alpha VMS systems ( utilizing EVA and XP storage technology.& Technology experience must be current.  Automation tools and techniques.$ Control language and system commands Backup and Recovery * Disaster Recovery Planning and Preparation" Database design and administration8 System performance, capacity planning and implementation/ Currency with OS releases and network protocols F Demonstrable expertise with functional requirements assurance, complex+ project activities, and project management. 7 Experience working within systems life cycle processes. 8 Strong quality assurance and systems testing experience.. Strong interpersonal and communication skills.   Desired:  Banking or financial institution Processing background  Operations background      Jason Druckenmiller  Technical Recruiter  MISI COMPANY an NTT DATA GROUP COMPANY B Your Source for Technical Talent, Solutions and Usability Services www.misicompany.com  phone:   212-355-5585 xt 353 fax:        212-751-5964 AIM:     Jason at MISI  B "There is no limit to what a man can accomplish if he doesn't care5 who gets the credit."  Plaque on Ronald Reagan's Desk    ------------------------------  % Date: Tue, 27 Jun 2006 21:33:57 +0200 3 From: Wilm Boerhout <w5OLD.boerhout@PAINTplanet.nl> , Subject: Re: VAX Open VMS Production Support6 Message-ID: <44a18827$0$26687$ba620dc5@nova.planet.nl>  ' JasonatMISI wrote on 27-6-2006 21:26... G > Please forgive me if I am publishing this to the wrong group.  I have B > the following spot I am trying to staff and am having difficulty> > finding people.  If anyone is interested please let me know.  F It is the right group, don't worry. It is just that I am in the wrong  country for this position.  D > "There is no limit to what a man can accomplish if he doesn't care7 > who gets the credit."  Plaque on Ronald Reagan's Desk   A The credit in this case goes to one of mr. Reagans predecessors,   president Harry S. Truman.   /Wilm    ------------------------------    Date: 27 Jun 2006 12:46:39 -07004 From: "JasonatMISI" <jdruckenmiller@misicompany.com>, Subject: Re: VAX Open VMS Production SupportB Message-ID: <1151437599.274865.33250@i40g2000cwc.googlegroups.com>   Wilm,   @     Thank you for the info!  I wondered where the original quoteE originated. :-)  Shame you are in the wrong country.  This is a tough 
 spot to fill.    Jason      Wilm Boerhout wrote:) > JasonatMISI wrote on 27-6-2006 21:26... I > > Please forgive me if I am publishing this to the wrong group.  I have D > > the following spot I am trying to staff and am having difficulty@ > > finding people.  If anyone is interested please let me know. > G > It is the right group, don't worry. It is just that I am in the wrong  > country for this position. > F > > "There is no limit to what a man can accomplish if he doesn't care9 > > who gets the credit."  Plaque on Ronald Reagan's Desk  > B > The credit in this case goes to one of mr. Reagans predecessors, > president Harry S. Truman. >  > /Wilm    ------------------------------  % Date: Tue, 27 Jun 2006 12:56:31 -0700 # From: "Tom Linden" <tom@kednos.com> , Subject: Re: VAX Open VMS Production Support) Message-ID: <op.tbtloh0bzgicya@hyrrokkin>   1 On Tue, 27 Jun 2006 12:46:39 -0700, JasonatMISI   ' <jdruckenmiller@misicompany.com> wrote:   B >     Thank you for the info!  I wondered where the original quoteD > originated.   Shame you are in the wrong country.  This is a tough > spot to fill.   1 If it is tough to fill, you aren't paying enough.    ------------------------------  % Date: Wed, 28 Jun 2006 00:01:46 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net>, Subject: Re: VAX Open VMS Production Support0 Message-ID: <44A20D3A.9E6C2826@spam.comcast.net>   Tom Linden wrote:  > 1 > On Tue, 27 Jun 2006 12:46:39 -0700, JasonatMISI ) > <jdruckenmiller@misicompany.com> wrote:  > D > >     Thank you for the info!  I wondered where the original quoteF > > originated.   Shame you are in the wrong country.  This is a tough > > spot to fill.  > 3 > If it is tough to fill, you aren't paying enough.   & He's a recruiter - it's not up to him.   --   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, 28 Jun 2006 00:08:55 -0500 6 From: "David J. Dachtera" <djesys.no@spam.comcast.net>, Subject: Re: VAX Open VMS Production Support0 Message-ID: <44A20EE7.B0A3BFC5@spam.comcast.net>   JasonatMISI wrote: >  > Wilm,  > B >     Thank you for the info!  I wondered where the original quoteG > originated. :-)  Shame you are in the wrong country.  This is a tough  > spot to fill.   * Well, there's some valid reasons for that:  G VMS folks with finance banking experience do exist; however, most of us G are senior people who can see retirement at or just beyond the horizon. E Changing jobs now would be hard to motivate unless current conditions  are sufficiently intolerable.   D Again, most VMS folks are senior people who expect - or need - to be3 paid a senior person's salary, not entry-level pay.   E Also, most folks who are looking want W2/full-time, not contract/temp  1099.   G Actually, VMS folks are in great abundance in the job market. Where "it F gets stuck" is at the "experience must be current" statement. Some VMSC folks were laid off over a decade ago, and use the OpenVMS hobbyist H program to stay as current as possible within budgetary limits (not many# home SANs out there, I'm thinking).    --   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, 27 Jun 2006 20:33:12 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: [ECP] OpenVMS V8 0 Message-ID: <cCgog.2295$Ou3.44@news.cpqcorp.net>    Peter 'EPLAN' LANGSTOEGER wrote:  L > Apropos Overlap. As TDC does not have an analyzer part (only an collector)L > I assume that the overlap is not temporary (or is an TDC analyzer coming?)  H    The ECP data collector is the piece that is being replaced by TDC -- @ The Data Collector -- as the ECP data analyzer continues, AFAIK.  C    There are also OpenView-related pieces available that can be of   potential interest here.  F    I've flagged this ECP/TDC matter with the business manager and the + maintainer of the software roll-out report.    ------------------------------   End of INFO-VAX 2006.356 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                  r Ae/(Vf^FCm|=Ln
Ji+ՄQ鯶ޯƺ洛SFfGZk
\-׽?p݋=Y 48	gk""h<YiY[{<\!{rÿ́nB3Oh1!IUTJxBYR$HD$j!qqny*SlCQ	ImIX<'G%)&XHZ"
l-c Fz0B=ሡ{y躧((ff0nzSP0VV?ǹ@-5	!=xCj3晦DƘ[ס=ijքaw>dT#MTJpBU"D駫) 9?a]p*량_W" pF""?{1VX[jQ7Fĉaaa.
##)4'a)e
'#)d}e*T
E4r!C<K
)ϘŖrJ
vX\AdHr	`I6 \,8ZZMlEm0pN
상}P08BӃq#qK$ж>TDx%jPn
p)v=J	(RTPRdu)	LnϬЅ- n_h,{Gu4ij<QĺVR7ݐ+)>&M]fb}nUZGb
'28MX	;.֦gQ2>[Yˍv7{x0.yuWq*t֓)cМiy\L'R+P4ʇ^ /LBj:z%6+8LW_Nor8B?mòA~lN 	GFМ\w^ +O"5s5`1_	YwRmRb
"	BMpX=CU]ia<%_'2]~ҁݻv7ÑPJM3RX6s	u<"暜Γ`sĤ`l0cME,4PJ
R'E;0B$D!gn߬_ǒrjW}nVS1f F~nTQKT]rO<FSE눊;Gm^7{YSmY{<=j#}h4оEɔiԻť^NI2zPZ ޛn2]Iw`F$'SM C&b<+X<A&r*X.gb?#{^AתF
M4E*H]A;_VMR͵^7;et4=̬lܨ Iv:]	eBF?i^v5w˙?z ϩE1!r6h-&OE6RAyMCignLCkǔ!3qN4k5"{/OsoJ{ZE~uH^P1٬Gg_\!fFDHWzmzLAh#?ޘtp7e1~}mHRs3gM$>ܰTfq3gDԱ)ag{-bVV%՘^Uv=k==		\;o=FGf,~]F\|];}c*׽~K>}͢M6ɥ/As+,\p .񀃉{{;p>=ɧn\^?)^kzK~ɧ& Gy8<l߶oZN|<C?(P2g=SlܖkԀYGu*SPhnaRE.pH8%uQ3>LCOo;*SXIP=?:~l⼣w&þ]/:4 k
b0
#_59̀y\Y2"OZ3A/]351q[MMkZ?M.L[z?
k3 VSg6`~DV2cᎃܘ&-D ԬO+9vu|Ei:.I"	X?8sѝΙ
uN&~5n
Wv
]
Umj}gK7NB'Ɣ:"2z'*1M4 "Jךx2taayO_=8PJ{KU:iTQjH;,
~0{<xGk
]bbwyȹ)C}nq<k^gi0B-F@nM<%.1fa0mI@}kȑ7b#`-[bNl1h@DGt_IkqgԵq7|edd&m̤ ib%R:ʲ"օ
4KmkqkWۚ;ZY
oly$cɛ^tpTM1.qS9Q{eߟ:HԊ8[nmD#s3ык۝FAEj+l1c+DGZ/@ sA+O\XkS@G^쥻R^<
(=Hג+S5٭D _ܸFqЀE95PJRceaFԯEa~6S̹\ms# Hu" _EP.8St<^8X=Ie^m/OkًsK}$#Pi'UrY5)~=JLe%?,01SkYfK:wjr{mX9t?^ڞn/JCqlum0<x6tz"˄+kYkmMfS*&hrokԗ:vIlp8tqbjmq,rYd+WR$#0Cѯr%