1 INFO-VAX	Fri, 14 May 2004	Volume 2004 : Issue 267       Contents:> Re: Big Blue - Caught Red Handed, stealing KGPSA HBA info?????> Re: Big Blue - Caught Red Handed, stealing KGPSA HBA info?????N Re: DCLER (DCL Enhancement Request) for DIRECTORY /SORT=[CREATED,MODIFIED,...]N Re: DCLER (DCL Enhancement Request) for DIRECTORY /SORT=[CREATED,MODIFIED,...] Re: DFO and SET FILE/NOMOVE  Re: DFO and SET FILE/NOMOVE  Re: DFO and SET FILE/NOMOVE  Re: DFO and SET FILE/NOMOVE  Re: DFO and SET FILE/NOMOVE  Re: EVE customizations EWSG on VMS P Re: Future of Availability Manager on IA64 (was Re: Tomcat / Java /  process quo Re: Getting HammeredN How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid error]P Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erroP Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erroP Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erro' Re: Icon (ico file) search for DCL lite  Re: installation boot failure  Re: installation boot failure ' LOGINOUT callouts and network processes + Re: LOGINOUT callouts and network processes + Re: LOGINOUT callouts and network processes  Re: longest uptime Re: longest uptime Re: longest uptime Re: longest uptime Re: longest uptime> Re: Poor VMS file create performance compared to Linux/FreeBSD> RE: Poor VMS file create performance compared to Linux/FreeBSD> Re: Poor VMS file create performance compared to Linux/FreeBSD> Re: Poor VMS file create performance compared to Linux/FreeBSD
 Re: SPAM, etc ! Re: SUN fails to advertise VMS... ! Re: SUN fails to advertise VMS... ! Re: SUN fails to advertise VMS... + TCPIP Services V5.4 on OpenVMS/Alpha V7.2-2 / RE: TCPIP Services V5.4 on OpenVMS/Alpha V7.2-2 < Re: Terry Shannon's "HP: Two Years Post-Merger Presentation"( Re: Timestamp format stored in RMS file?( Re: Timestamp format stored in RMS file?( Re: Timestamp format stored in RMS file? Re: VMS, tftp & ftp questions  Re: VMS, tftp & ftp questions  where to find devicedrivers?  Re: where to find devicedrivers? Re: XDMP and TCPIP 5.4 Re: XDMP and TCPIP 5.4) Re: XFC experiences on OpenVMS Alpha V7.3 ) Re: You'll never guess what HP advertised ) Re: You'll never guess what HP advertised ) Re: You'll never guess what HP advertised ) Re: You'll never guess what HP advertised ) Re: You'll never guess what HP advertised 4 [General]: Understanding 'Mean Time Between Failure'  F ----------------------------------------------------------------------  # Date: Fri, 14 May 2004 10:17:47 GMT % From: "Mike Naime" <mnaime@kc.rr.com> G Subject: Re: Big Blue - Caught Red Handed, stealing KGPSA HBA info????? 4 Message-ID: <f11pc.407$zn.258@twister.rdc-kc.rr.com>  J It's an Emulex rebranded HBA that you purchase from either vendor.  So didL they "steal it " from Emulex the original manufacturer?  :-)   What I reallyE get a kick out of is the 1GB GBICS in our old (Brocade rebranded) SAN J switches are an IBM product that was repackaged and sold by Compaq.  I bet1 that the tech doc for that would be the same too!   6 Rob Young <young_r@encompasserve.org> wrote in message- news:mUSy5GhVjQuD@eisner.encompasserve.org... ; > In article <c81bn5$1o2k$1@news.wplus.net>, "Alex Daniels" / <AlexNOSPAMTHANKSDaniels@themail.co.uk> writes: J > > Take a look at these two pages, one on digital.com and one ibm.com, to me > > they look identical!!  > > I > > Are ibm taking DEC/Compaq/hp documents, and palming them off as their  own??  > >  > > L http://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/archive/utility/identi fy.txt > >  > > L http://www-1.ibm.com/servers/storage/support/disk/64bitpcifibre/fc-hba_paid. html > >  > >  > 7 > No.  IBM was at one time selling compaq storage under @ > a joint venture/agreement.  The MSS became the rebranded 2106.F > What you are pointing to there is technical support docs.  Something= > that shouldn't disappear just because it is no longer being  > sold.  >  > Rob  >    ------------------------------    Date: 14 May 2004 08:33:23 -0700. From: alexdaniels@themail.co.uk (Alex Daniels)G Subject: Re: Big Blue - Caught Red Handed, stealing KGPSA HBA info????? = Message-ID: <9f7f13a8.0405140733.30055fcd@posting.google.com>   a "Mike Naime" <mnaime@kc.rr.com> wrote in message news:<f11pc.407$zn.258@twister.rdc-kc.rr.com>... L > It's an Emulex rebranded HBA that you purchase from either vendor.  So didN > they "steal it " from Emulex the original manufacturer?  :-)   What I reallyG > get a kick out of is the 1GB GBICS in our old (Brocade rebranded) SAN L > switches are an IBM product that was repackaged and sold by Compaq.  I bet3 > that the tech doc for that would be the same too!  > 8 > Rob Young <young_r@encompasserve.org> wrote in message/ > news:mUSy5GhVjQuD@eisner.encompasserve.org... = > > In article <c81bn5$1o2k$1@news.wplus.net>, "Alex Daniels" 2 >  <AlexNOSPAMTHANKSDaniels@themail.co.uk> writes:L > > > Take a look at these two pages, one on digital.com and one ibm.com, to >  me  > > > they look identical!!  > > > K > > > Are ibm taking DEC/Compaq/hp documents, and palming them off as their  >  own?? > > >  > > > N > http://ftp.digital.com/pub/DEC/Alpha/firmware/readmes/archive/utility/identi > fy.txt > > >  > > > N > http://www-1.ibm.com/servers/storage/support/disk/64bitpcifibre/fc-hba_paid. > html > > >  > > >  > > 9 > > No.  IBM was at one time selling compaq storage under B > > a joint venture/agreement.  The MSS became the rebranded 2106.H > > What you are pointing to there is technical support docs.  Something? > > that shouldn't disappear just because it is no longer being 	 > > sold.  > >  > > Rob  > >   C I know that the HBA's are rebranded Emulex, just think its slightly @ odd they have the same tech doc's, although maybe your right and( Emulex just gave them to both companies.  5 Still the 'IBM Tru64' thing is definetly not right...    Alex   ------------------------------    Date: 14 May 2004 04:41:57 -0700% From: Bart.Zorn@xs4all.nl (Bart Zorn) W Subject: Re: DCLER (DCL Enhancement Request) for DIRECTORY /SORT=[CREATED,MODIFIED,...] = Message-ID: <a98cd882.0405140341.71644516@posting.google.com>   E In itself, executing SYS$STARTUP:LIB$DT_STARTUP.COM only adds logical ? names to LNM$DT_FORMAT_TABLE, which will not break anything. By 9 default, only the definitions for LIB$DATE_FORMAT_001 and . LIB$TIME_FORMAT_001 are present in this table.  C If you have the logical name SYS$LANGUAGE defined as something else F besides "ENGLISH", additional logical name tables are defined, one forE each element in your list of languages, in which all kind of language ! dependant definitions are placed.   @ Anyway, there are only definitions added, nothing gets replaced.  D Defining the logical name LIB$DT_FORMAT (certainly in usermode) only affects your current process.   1 In short, I think that there are no side effects.    Regards,  	 Bart Zorn   s spamsink2001@yahoo.com (Alan E. Feldman) wrote in message news:<b096a4ee.0405131941.51022371@posting.google.com>... ^ > Paul Sture <nospam@sture.homeip.net> wrote in message news:<2g5uibF4o8fkU1@uni-berlin.de>... > > Alan E. Feldman wrote:I > > > How about directory listings sorted by date-time? Yes, you'd either J > > > have to list a single directory or suppress the headers and trailersJ > > > for multi-directory listings, and you'd have to wait to see even theA > > > first file listed. But so what -- it would still be useful.  > > B > > Peter Weaver posted this neat trick with dates on 30-Apr-2004: > > B > > Make sure you run it with SET TERM/WIDTH=132 to avoid wrapping > >  > > L > > $ ! Needs @SYS$STARTUP:LIB$DT_STARTUP executing by privileged user first" > > $ ASSIGN LIB$DATE_FORMAT_037,- > >     LIB$TIME_FORMAT_001 -  > >     LIB$DT_FORMAT/USER_MODE ) > > $ directx -  ! Ignore any DIR symbols  > >     /date=modified- % > >     /width=(file:80,display:132)-  > >     /out=out.txt > > $ sort out.txt -! > >      /key=(pos:83,siz:22) tt:  >  >  > Thanks! It worked. > E > But I have a question: What else does running that startup file and B > defining the logical name affect? IOW, are there any "unintended > consequences"? Thanks.   ------------------------------  % Date: Fri, 14 May 2004 11:34:47 -0400 < From: "Peter Weaver" <WeaverConsultingServices@sympatico.ca>W Subject: Re: DCLER (DCL Enhancement Request) for DIRECTORY /SORT=[CREATED,MODIFIED,...] * Message-ID: <2gk78oF3urspU1@uni-berlin.de>   Alan E. Feldman wrote: >...E > besides DIRECTORY/DATE output? I'm asking about the effects of both B > running the LIB$DT_STARTUP file and defining the LIB$DATE_FORMAT > logical name.  >...  F Of course defining LIB$DATE_FORMAT as /USER_MODE won't affect anythingG other than the next image. But if you define it for the process then it G will affect any program that calls LIB$FORMAT_DATE_TIME routine. I have F used it for programs that read MONITOR/RECORD sessions and write filesG that I then use EXCEL to graph because it was an easy way to format the . dates in a way that EXCEL would easily accept.  E Some standard VMS tools use it too, but some do not. "MONITOR SYSTEM" F does not, but "MONITOR DISK" does. "SHOW USERS" and "SHOW SYSTEM" also will use the LIB$DATE_FORMAT.   G I do not know if anything uses LIB$DT_INPUT_FORMAT, but I always define D that as "!DB-!MAAU-!Y4 !H04:!M0:!S0.!C2" just to make sure it is not defined as something else.   --   Peter Weaver Weaver Consulting Services Inc.  Canadian VAR for CHARON-VAX  www.weaverconsulting.ca    ------------------------------  + Date: Fri, 14 May 2004 07:10:37 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)$ Subject: Re: DFO and SET FILE/NOMOVE$ Message-ID: <c81rdd$hpc$1@online.de>  < In article <87isezu99c.fsf@prep.synonet.com>, Paul Repacholi  <prep@prep.synonet.com> writes:   T > helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: > 5 > > In article <3Rtoc.1324$Lf2.397@news.cpqcorp.net>, : > > hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:  > ? > >> The OpenVMS Alpha and OpenVMS I64 installation and upgrade H > >> procedure ensures that the files which require SET FILE/NOMOVE haveF > >> this attribute set.  If they have not been changed, it should not+ > >> be necessary to run SETFILENOMOVE.COM.  > E > > In that case, it might be a good idea for the DFO installation to C > > indicate that perhaps executing SETFILENOMOVE is not necessary.  > F > NOT a good idea! The clasic case is system that is on its own systemE > disk. To the rest of the cluster, it is just a data disk, and files F > opened with the primitive system do not have locks take out, so theyL > are not seen as open by other systems. Not only are they open, they are in: > active use. Well, until some random stuff gets paged in.  G I don't follow you.  My thinking was that once they have the attribute  ; set, via an installation or upgrade, then everything is OK.    ------------------------------    Date: 14 May 2004 04:58:14 -0700% From: Bart.Zorn@xs4all.nl (Bart Zorn) $ Subject: Re: DFO and SET FILE/NOMOVE= Message-ID: <a98cd882.0405140358.1f924f88@posting.google.com>   D Well, the installation procedure could be made intelligent enough toD examine the current system disk (i.e. the system disk of the node onD which the installation runs) and determine if SETFILENOMOVE needs toF be run on that disk or not. It is also not entirely impossible to scanE all disks and find out if any of them are also system disks which may @ or may not need a run of SETFILENOMOVE. Any information provided/ during the installation is IMHO a step forward.   @ However, any system manager who is using any defrag tool without3 knowing what he/she is doing is asking for trouble!   	 Bart Zorn   a Paul Repacholi <prep@prep.synonet.com> wrote in message news:<87isezu99c.fsf@prep.synonet.com>... T > helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: > 5 > > In article <3Rtoc.1324$Lf2.397@news.cpqcorp.net>, : > > hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:  >   ? > >> The OpenVMS Alpha and OpenVMS I64 installation and upgrade H > >> procedure ensures that the files which require SET FILE/NOMOVE haveF > >> this attribute set.  If they have not been changed, it should not+ > >> be necessary to run SETFILENOMOVE.COM.  >   E > > In that case, it might be a good idea for the DFO installation to C > > indicate that perhaps executing SETFILENOMOVE is not necessary.  > F > NOT a good idea! The clasic case is system that is on its own systemE > disk. To the rest of the cluster, it is just a data disk, and files F > opened with the primitive system do not have locks take out, so theyL > are not seen as open by other systems. Not only are they open, they are in: > active use. Well, until some random stuff gets paged in.   ------------------------------  # Date: Fri, 14 May 2004 13:33:08 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond) $ Subject: Re: DFO and SET FILE/NOMOVE1 Message-ID: <oU3pc.1492$n24.992@news.cpqcorp.net>   w In article <c81rdd$hpc$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: = >In article <87isezu99c.fsf@prep.synonet.com>, Paul Repacholi ! ><prep@prep.synonet.com> writes:   > U >> helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: 8 >>                                                      6 >> > In article <3Rtoc.1324$Lf2.397@news.cpqcorp.net>,; >> > hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:   >>  @ >> >> The OpenVMS Alpha and OpenVMS I64 installation and upgradeI >> >> procedure ensures that the files which require SET FILE/NOMOVE have G >> >> this attribute set.  If they have not been changed, it should not , >> >> be necessary to run SETFILENOMOVE.COM. >>  F >> > In that case, it might be a good idea for the DFO installation toD >> > indicate that perhaps executing SETFILENOMOVE is not necessary. >>  G >> NOT a good idea! The clasic case is system that is on its own system F >> disk. To the rest of the cluster, it is just a data disk, and filesG >> opened with the primitive system do not have locks take out, so they M >> are not seen as open by other systems. Not only are they open, they are in ; >> active use. Well, until some random stuff gets paged in.  > H >I don't follow you.  My thinking was that once they have the attribute < >set, via an installation or upgrade, then everything is OK.   Yep.  That is correct.   --  J       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  # Date: Fri, 14 May 2004 13:38:02 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond) $ Subject: Re: DFO and SET FILE/NOMOVE1 Message-ID: <_Y3pc.1493$n24.982@news.cpqcorp.net>   e In article <a98cd882.0405140358.1f924f88@posting.google.com>, Bart.Zorn@xs4all.nl (Bart Zorn) writes: E >Well, the installation procedure could be made intelligent enough to E >examine the current system disk (i.e. the system disk of the node on E >which the installation runs) and determine if SETFILENOMOVE needs to G >be run on that disk or not. It is also not entirely impossible to scan F >all disks and find out if any of them are also system disks which mayA >or may not need a run of SETFILENOMOVE. Any information provided 0 >during the installation is IMHO a step forward.  J The installation or upgrade procedure correctly sets the NOMOVE attribute F as necessary for the system disk being created or upgraded.  Since allF system disk are created/upgraded by this procedure, they will all haveF this attribute correctly set.  It will not matter if a particular diskG is the current system disk for this system, the current system disk for K another system in the OpenVMS cluster, or an un-booted "extra" system disk.   0 This applies to OpenVMS Alpha and OpenVMS I64.  . I have not checked (and do not remember) what % OpenVMS VAX installations/upgades do.    --  J       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  % Date: Fri, 14 May 2004 22:40:53 +0800 , From: Paul Repacholi <prep@prep.synonet.com>$ Subject: Re: DFO and SET FILE/NOMOVE- Message-ID: <87wu3frs0a.fsf@prep.synonet.com>   R helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:  > > In article <87isezu99c.fsf@prep.synonet.com>, Paul Repacholi" > <prep@prep.synonet.com> writes:  > U >> helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:  >>  6 >> > In article <3Rtoc.1324$Lf2.397@news.cpqcorp.net>,; >> > hammond@not@peek.ssr.hp.com (Charlie Hammond) writes:   >>  @ >> >> The OpenVMS Alpha and OpenVMS I64 installation and upgradeI >> >> procedure ensures that the files which require SET FILE/NOMOVE have G >> >> this attribute set.  If they have not been changed, it should not , >> >> be necessary to run SETFILENOMOVE.COM. >>  F >> > In that case, it might be a good idea for the DFO installation toD >> > indicate that perhaps executing SETFILENOMOVE is not necessary. >>  G >> NOT a good idea! The clasic case is system that is on its own system F >> disk. To the rest of the cluster, it is just a data disk, and filesG >> opened with the primitive system do not have locks take out, so they M >> are not seen as open by other systems. Not only are they open, they are in ; >> active use. Well, until some random stuff gets paged in.   I > I don't follow you.  My thinking was that once they have the attribute  = > set, via an installation or upgrade, then everything is OK.   I IFF they are set. Also, if you remove the NOMOVE bits and defrag the disk H while the other system is down, it is handty to have a neat procedure to put them back again.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Fri, 14 May 2004 15:34:40 +0200 ( From: Andreas Davour <ante@update.uu.se> Subject: Re: EVE customizations 0 Message-ID: <cs94qqjp1xr.fsf@Tempo.Update.UU.SE>  = koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:   ] > In article <cs9pt9925bj.fsf@Tempo.Update.UU.SE>, Andreas Davour <ante@update.uu.se> writes: H >> If you mean the "c-mode" happens to you without you know why, then it >> should be a simple problem. > E >    I mean when we're in c-mode, using our indentation standards, it ' >    suddenly changes to gnu standards.   G That behaviour is more odd. I suggest you go ask in a emacs group. They  should be able to help you.    /andreas   ------------------------------  % Date: Fri, 14 May 2004 15:41:41 +0100 E From: Tim ffrench-Lynch <tim-DOT-ffrench-HYPHEN-lynch@baesystems.com>  Subject: EWSG on VMS. Message-ID: <40A4DAA5.5A0CEAEE@baesystems.com>  A Does anyone out there still run EWSG from Data Sciences on VAX or 
 Alpha VMS?  @ EWSG (Electronic Warfare Scenario Generator) is part of EWES (EWF Evaluation System) - not a bad piece of software but probably a little7 dated now. I'm running it on a dozen VAX and one Alpha.    Tim    ------------------------------  # Date: Fri, 14 May 2004 10:31:44 GMT 0 From: "Barry Kierstein" <Barry.Kierstein@HP.Com>Y Subject: Re: Future of Availability Manager on IA64 (was Re: Tomcat / Java /  process quo 1 Message-ID: <ke1pc.1486$5T3.792@news.cpqcorp.net>   L Just a note:  I believe the Performance Data Collector is also known as TDC.K It is the user-mode data collection utility to collect all sorts of things. < The analyzer is intended to either be 3rd party or your own.   Barry   K "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in message 0 news:409ADC3A.E4AC3AA7@NeOaSrPtAhMlNiOnWk.net... > Peter Weaver wrote:  > >  > > Barry Kierstein wrote: > > >...H > > >     Having said this, what are your opinions?  Enough opinions one( > > > way or the other can swing things. > > >... > > K > > Well, since you asked, here is what I saw as the current (revision 2.8) 	 > > plan;  > > 6 > > OpenVMS I64 Foundation Operating Environment (FOE) > >   OpenVMS Operating System& > >   OpenVMS Unlimited User Licensing! > >   TCP/IP Services for OpenVMS ) > >   DECnet-Plus for OpenVMS  End System " > >   DECwindows Motif for OpenVMS > >   DECnet IV   > >   Performance Data Collector > Where's the analyzer?  >  > >   Integration Technologies > >    - BridgeWorks > >    - COM for OpenVMS  > >    - Secure Web Server (SWS)! > >    - Secure Web Browser (SWB) # > >    - SDK for the JavaT Platform  > >    - XML Technology  > >    - NetBeans 5 > >    - Simple Object Access Protocol (SOAP) Toolkit  > >    - Kerberos  > >    - Enterprise Directory 
 > >    - CDSA  > >    - SSL > >    - OpenSource Tools * > Where's SAMBA? Part of OpenSource Tools? > 6 > > OpenVMS I64 Enterprice Operating Environment (EOE) > >   Add to Foundation: > >   RMSjournaling  > >   VolumeShadowing  > >   DECram% > >   OpenVMS System Management Tools   > >    - OVMS Management Station
 > Useless. > * > >    - Enterprise Capacity Planner - ECP9 > Not SPM or DCPA, but better than nothing (not by much).  >  > >    - Availability Manager  > AMDS is better.  >  > >    - OpenVMS Web Agents  > >    - OpenVMS WEBM/CIM  > > = > > OpenVMS I64 Mission Critical Operating Environment (MCOE)  > >  Add to Enterprise:  > >   OpenVMS Clusters > >   OpenVMS RTR Backend  > B > So, it looks like almost everything that has the potential to be- > clustered will have to ship with MCOE, huh?  >  > So much for affordability... >  > --   > David J. Dachtera  > dba DJE Systems  > http://www.djesys.com/ > * > Unofficial Affordable OpenVMS Home Page:! > http://www.djesys.com/vms/soho/    ------------------------------  # Date: Fri, 14 May 2004 15:11:47 GMT 1 From: Michael Austin <maustin@firstdbasource.com>  Subject: Re: Getting Hammered 2 Message-ID: <40A4E21D.614D46C1@firstdbasource.com>  J hmm. I just downloaded the FULL PDF presentation in < 30 seconds.. I am on7 ADSL 256up/1.5down with a router and a WAP in between..    M.   Paul Sture wrote:    > Kenneth Farmer wrote:  > F > >>>Hammered is the word, or should I say Inquirered or maybe Inq'ed. > >>>  > >> >  >  > Paul Sture scribbled: > E > >>Out of interest, what kind of bandwidth do you have? FWIW, my own I > >>business class connection has improved beyond all recognition since I 0 > >>first started with it a couple of years ago. > > L > > 1Mb up / 2Mb down.  I had them double it to 2Mb/2Mb.  Still sluggish but > > better.  > >  > G > 640Kb / 1536KB here, and reliably so. I don't consume much of that at ? > the moment, so please feel free to ask if you want my help in : > distributing annything of interest to the VMS community.   ------------------------------    Date: 13 May 2004 23:05:50 -0700( From: prakash_balaji@yahoo.com (Prakash)W Subject: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid error] = Message-ID: <8e40535b.0405132205.656806aa@posting.google.com>    Hi,   @ 	We are working on FAB/RAB in OpenVMS. We are doing Asynchronous, Operations. We have set the following bit as  *         file->rab->rab$l_rop |= RAB$V_ASY;  5 	When we set this, we are getting the following error   $ 	Earlier, we had used RAB$M_ASY ie.,  *         file->rab->rab$l_rop |= RAB$M_ASY;  > 	But, a crash happens randomly when we used RAB$M_ASY. When we8 replaced RAB$M_ASY with RAB$V_ASY,we saw no crashes,but,  C we get the FAB/RAB invalid error and the operations gets stuck & is  not processed thereafter.   A We use the sys$get call in our code & we get the following error:   D 	RMS$_STR,  user structure (FAB/RAB) became invalid during operation  F         We would like to know how to handle the return value RMS$_STR.    . 1] Can anyone tell us how to handle RMS$_STR? F 2] Is there any other way in which we can achieve both ie., no crash &
 Code working? 9 3] What is the differnce between RAB$M_ASY and RAB$V_ASY?    We are working on OpenVMS & C.  A Any help in this regard is most welcome. Kindly get back to us if ! these details are not sufficient.    Thanks & Regards,  Prakash.   ------------------------------  % Date: Fri, 14 May 2004 09:41:00 -0400 - From: "heuveltjes" <heuveltjes@email.msn.com> Y Subject: Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erro , Message-ID: <40a4cd32$1@usenet01.boi.hp.com>  5 "Prakash" <prakash_balaji@yahoo.com> wrote in message 7 news:8e40535b.0405132205.656806aa@posting.google.com...  > Hi,  > A > We are working on FAB/RAB in OpenVMS. We are doing Asynchronous . > Operations. We have set the following bit as > , >         file->rab->rab$l_rop |= RAB$V_ASY;  L The others have given good and correct advice, but I feel compelled to pointD out that you are working beyond your current level of understanding.G While using RMS asynchroneously is not extremely hard it does require a  certain care and understanding. L In confusing RAB$M_xxx with RAB$V_xxx you indicate you are NOT ready to deal with Async for now. K Please be sure to spend a few hours with the RMS reference manual! You know  about sys$wait right? < Are you maintaining existing code or creating something new?G What are you trying to achieve by going async? (Don't just say 'speed', K please explain how that speed will be accomplish. What useful work will the E program be doing after you initiated the async request and before rms  satisfied finished the request. L If you are dealing with sequential files then it may well be that just usingG Read-Ahead and Write-Behind covers 99% of your needs. When dealing with L shared files, maybe Deferred Write is all you need for the speedbump you are looking for.   Regards, Hein.    ------------------------------    Date: 14 May 2004 07:54:02 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Y Subject: Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erro 3 Message-ID: <dODB7XAdhMdc@eisner.encompasserve.org>   h In article <8e40535b.0405132205.656806aa@posting.google.com>, prakash_balaji@yahoo.com (Prakash) writes: > , >         file->rab->rab$l_rop |= RAB$V_ASY; > 7 > 	When we set this, we are getting the following error  > & > 	Earlier, we had used RAB$M_ASY ie., > , >         file->rab->rab$l_rop |= RAB$M_ASY;  J    V_ indicates a number which is the number of the starting bit of a bit K    field.  M_ indicates a bit mask the size of the bit field. RAB$M_ASY is  &    what you want for bit or (| or |=).  F    OBTW, S_ indicates a number which is the number of bits in the bit 	    field.    > @ > 	But, a crash happens randomly when we used RAB$M_ASY. When we: > replaced RAB$M_ASY with RAB$V_ASY,we saw no crashes,but,  $    Fix that.  It's the real problem.   > 0 > 1] Can anyone tell us how to handle RMS$_STR?   C    Make sure nothing clobbers the RMS structures.  Using |= with V_     could do that.   ; > 3] What is the differnce between RAB$M_ASY and RAB$V_ASY?   
    See above.    ------------------------------  % Date: Fri, 14 May 2004 09:13:49 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam>Y Subject: Re: How to Handle RMS$_STR during Asynchronous Operations [ FAB/RAB invalid erro 4 Message-ID: <c81v3t$222$1$8302bc10@news.demon.co.uk>   Prakash wrote: > Hi,  > B > 	We are working on FAB/RAB in OpenVMS. We are doing Asynchronous. > Operations. We have set the following bit as > , >         file->rab->rab$l_rop |= RAB$V_ASY;  G RAB$V_ASY is a bit number (0) to be used as an index into a bit array,  I so the above is a No-OP, and you're probably still doing synchronous I/O. 5 Correct code would be "file->rab->rab$v_asy = 1;" or  H "file->rab->rab$l_rop |=RAB$M_ASY;" - I can't find a suitable bit array  declaration.  7 > 	When we set this, we are getting the following error  > & > 	Earlier, we had used RAB$M_ASY ie., > , >         file->rab->rab$l_rop |= RAB$M_ASY;   Correct.  @ > 	But, a crash happens randomly when we used RAB$M_ASY. When we: > replaced RAB$M_ASY with RAB$V_ASY,we saw no crashes,but, > E > we get the FAB/RAB invalid error and the operations gets stuck & is  > not processed thereafter.   E It's asynchronous - either you're allocating your rab on the stack &  G then returning out of the allocating procedure, or you're trashing its  ) storage (whether static, heap, or stack). E What the error specifically means is that when RMS looked at the RAB  F (probably on completion of I/O) it didn't appear to be a RAB any more E (rab$b_bid, rab$b_bln or other necessary fields had incorrect values.   G RMS$_STR is a program logic failure, not an I/O error - you need to be  E sure that the RAB you pass the address of to RMS remains valid until   after I/O completion.    Chris   C > We use the sys$get call in our code & we get the following error:  > F > 	RMS$_STR,  user structure (FAB/RAB) became invalid during operation > H >         We would like to know how to handle the return value RMS$_STR. >  > 0 > 1] Can anyone tell us how to handle RMS$_STR? H > 2] Is there any other way in which we can achieve both ie., no crash & > Code working? ; > 3] What is the differnce between RAB$M_ASY and RAB$V_ASY?  >   > We are working on OpenVMS & C. > C > Any help in this regard is most welcome. Kindly get back to us if # > these details are not sufficient.  >  > Thanks & Regards, 
 > Prakash.   ------------------------------  % Date: Fri, 14 May 2004 09:23:06 +0100 * From: Nic Clews <sendspamhere@[127.0.0.1]>0 Subject: Re: Icon (ico file) search for DCL lite' Message-ID: <c81voe$q50$1@lore.csc.com>    "David J. Dachtera" wrote: >  > Nic Clews wrote: > >  ... I > > Anyway, back to subject in hand, anyone got or using a reasonable ICO  > > file for this? > > ' > > You can get the software from here:  > > $ > > http://www.accelr8.com/dcll.html > B > I take it the .EXE itself does not have any icons in it? (Make a6 > shortcut on the desktop and try to change the icon.)  D No it hasn't. I guess I could probably create one, "DCL" in a box orH something. However I thought I'd ask. If nothing turns up I'll have a go, at making one, then I'll post a link here...     --  ? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences  nclews at csc dot com    ------------------------------  # Date: Fri, 14 May 2004 10:49:39 GMT A From: "Colin Butcher" <colin_DOT.butcher_AT@xdelta_DOT.co_DOT.uk> & Subject: Re: installation boot failure= Message-ID: <7v1pc.3515$6c5.32160933@news-text.cableinet.net>   K You might find that you could change the CPU, but keep the bulk of the box. I I did that with a Digital Server 7000 and turned it into a 4100 by simply K swapping the CPU boards for some old 300MHz VMS capable Alphas. The rest of : the box is pretty much the same - seems to work just fine.   --     Hope this helps, Colin. ) colin DOT butcher AT xdelta DOT co DOT uk L Systems Archaeologist - Investigation & troubleshooting of older systems and	 networks.    ------------------------------  % Date: Fri, 14 May 2004 16:43:58 +0200 ) From: Roland Barmettler <itsme@127.0.0.1> & Subject: Re: installation boot failure5 Message-ID: <20040514164358.5f919920.itsme@127.0.0.1>   5 Colin Butcher wrote on Fri, 14 May 2004 10:49:39 GMT:   H > You might find that you could change the CPU, but keep the bulk of theF > box. I did that with a Digital Server 7000 and turned it into a 4100C > by simply swapping the CPU boards for some old 300MHz VMS capable E > Alphas. The rest of the box is pretty much the same - seems to work  > just fine.  E You don't even need to change CPUs, I have a Digital Server 7310 with ' "NT only" CPUs that runs VMS just fine. @ What you need to do is to create a small NVRAM script in the SRMG console that creates and sets an environment variable srm_boot to "ON".    So:   
 >>>edit nvram  >>>10 set srm_boot ON  >>>exit    I also set boot_reset to "ON"    Hope it helps...   Cheers, Roland   -- 3rd Law of Computing:          Anything that can go wr   Segmentation fault (core dumped)   ------------------------------  # Date: Fri, 14 May 2004 13:28:51 GMTX# From: Jonas Lindholm <jlhm@usa.net> 0 Subject: LOGINOUT callouts and network processes7 Message-ID: <nQ3pc.111728$WA4.67902@twister.nyc.rr.com>    HI,d  F I'm trying to use the LGI callouts for LOGINOUT for implementing LDAP.B Everything is working great except that when doing a network loginC the password (LGI$A_ICR_PWD1) points to a string with length 0) if I NET_CALLOUTS is set to 0. G If NET_CALLOUTS is set to 255 the password is filled in and everything   is ok.  C Does anyone know why NET$ACP process removes the password from the o, access control string if NET_CALLOUTS is 0 ?   I'm trying with VMS 7.3    Thanks /Jonas Lindholmn   ------------------------------  # Date: Fri, 14 May 2004 15:07:54 GMT ) From: "Rick Barry" <richard.barry@hp.com>O4 Subject: Re: LOGINOUT callouts and network processes1 Message-ID: <eh5pc.1500$cS3.961@news.cpqcorp.net>a  0 "Jonas Lindholm" <jlhm@usa.net> wrote in message1 news:nQ3pc.111728$WA4.67902@twister.nyc.rr.com...c > HI,  >rH > I'm trying to use the LGI callouts for LOGINOUT for implementing LDAP.D > Everything is working great except that when doing a network loginD > the password (LGI$A_ICR_PWD1) points to a string with length 0) if > NET_CALLOUTS is set to 0.gH > If NET_CALLOUTS is set to 255 the password is filled in and everything > is ok. >lD > Does anyone know why NET$ACP process removes the password from the. > access control string if NET_CALLOUTS is 0 ? >V > I'm trying with VMS 7.3c >a > Thanks > /Jonas Lindholmr  L Setting NET_CALLOUTS to 255 instructs the NET$ACP process to invoke LOGINOUTJ in order to perform authentication. This is what NET_CALLOUTS was designedH to do. If set to zero, NET$ACP performs its own authentication and if itB needs to run LOGINOUT to create the process it sets the request asI "pre-authenticated" (see description of LGI$V_NET_PREAUTH in LIB/LGIDEF).f    
 Rick Barry OpenVMS System Softwaref Hewlett-Packard Companyt
 Nashua, NH   ------------------------------  # Date: Fri, 14 May 2004 14:53:04 GMT # From: Jonas Lindholm <jlhm@usa.net>r4 Subject: Re: LOGINOUT callouts and network processes7 Message-ID: <k35pc.111803$WA4.35728@twister.nyc.rr.com>V   Rick Barry wrote:r  2 > "Jonas Lindholm" <jlhm@usa.net> wrote in message3 > news:nQ3pc.111728$WA4.67902@twister.nyc.rr.com...r >  >>HI,  >>H >>I'm trying to use the LGI callouts for LOGINOUT for implementing LDAP.D >>Everything is working great except that when doing a network loginD >>the password (LGI$A_ICR_PWD1) points to a string with length 0) if >>NET_CALLOUTS is set to 0.MH >>If NET_CALLOUTS is set to 255 the password is filled in and everything >>is ok. >>D >>Does anyone know why NET$ACP process removes the password from the. >>access control string if NET_CALLOUTS is 0 ? >> >>I'm trying with VMS 7.3o >> >>Thanks >>/Jonas Lindholm  >  > N > Setting NET_CALLOUTS to 255 instructs the NET$ACP process to invoke LOGINOUTL > in order to perform authentication. This is what NET_CALLOUTS was designedJ > to do. If set to zero, NET$ACP performs its own authentication and if itD > needs to run LOGINOUT to create the process it sets the request asK > "pre-authenticated" (see description of LGI$V_NET_PREAUTH in LIB/LGIDEF).@ >  >  > Rick Barry > OpenVMS System SoftwareK > Hewlett-Packard Companyt > Nashua, NH >  >    Thanks!o  = but the callout for authentication is always invoked even if  @ NET_CALLOUTS is 0 making it possible for the callout routine to H terminate the login. It would be great if the password always was passedG to the LOGINOUT image. Any reason why NET$ACP remove the password from  = the access control string when invoking the LOGINOUT.EXE and / NET_CALLOUTS is zero ?   /Jonas   ------------------------------  + Date: Fri, 14 May 2004 11:16:56 +0000 (UTC)e From: david20@alpha2.mdx.ac.uk Subject: Re: longest uptimei) Message-ID: <c829r8$k6o$1@news.mdx.ac.uk>S  y In article <40A420FA.B799A859@NeOaSrPtAhMlNiOnWk.net>, "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> writes:- >Syltrem wrote:4 >> 2J >> > Well, I have a cluster that was established well over a year ago, butM >> > the longest uptime for any member is currently just over 30 days, due to9' >> > monthly reboots, patches and such.e >> > >> > --  >> > David J. Dachtera >> > dba DJE Systems >> > http://www.djesys.com/d >> r >> What is a monthly reboot?& >> This is a VMS forum, not windows... >> ;-) > B >Yeah, well, even in the VMS world, pesky app.'s can have resource	 >leaks...  >l >*SIGH*   I Usually when I've come across this monthly reboot phenonemon on VMS it issN because it has been recommnded by the Vendor and the Vendor has recommended itN because at some point they had a memory leak problem with the application on aL Unix platform. The leak on the Unix platform may itself have been fixed agesK ago but the advice to reboot has become set in stone and is applied to all N  systems the application runs on.    
 David Webb VMS and Unix team leader CCSS Middlesex University        >m >--  >David J. Dachtera >dba DJE Systems >http://www.djesys.com/m >/) >Unofficial Affordable OpenVMS Home Page:   >http://www.djesys.com/vms/soho/   ------------------------------  % Date: Fri, 14 May 2004 12:33:19 +0100 * From: Nic Clews <sendspamhere@[127.0.0.1]> Subject: Re: longest uptimes& Message-ID: <c82at5$d3$1@lore.csc.com>   david20@alpha2.mdx.ac.uk wrote:s >  >  > >> What is a monthly reboot?( > >> This is a VMS forum, not windows... > >> ;-) > >bD > >Yeah, well, even in the VMS world, pesky app.'s can have resource > >leaks...i > > 	 > >*SIGH*l > K > Usually when I've come across this monthly reboot phenonemon on VMS it is P > because it has been recommnded by the Vendor and the Vendor has recommended itP > because at some point they had a memory leak problem with the application on aN > Unix platform. The leak on the Unix platform may itself have been fixed agesL > ago but the advice to reboot has become set in stone and is applied to all" > systems the application runs on.  D A system that has a weekly reboot (for standalone image backups) theE operator commands are described as "IPLing" the system (not booting).o  D No prizes for guessing the "partner in crime" system to this one ;-)  . (Uh, oh, OK, Initial Program Load for the IBM)  @ Yes I said weekly. Very stable otherwise. Any advance on weekly? -- F? Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences  nclews at csc dot com    ------------------------------    Date: 14 May 2004 07:39:23 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)i Subject: Re: longest uptimew3 Message-ID: <toaqz3rIKZAv@eisner.encompasserve.org>   b In article <c802s8$4a3$1@pcls4.std.com>, moroney@world.std.spaamtrap.com (Michael Moroney) writes: > / > How do you keep Windows up for a whole month?t      Put a nail through the sash.t   ------------------------------    Date: 14 May 2004 07:42:20 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)e Subject: Re: longest uptime33 Message-ID: <Ot1cvWYwVc3m@eisner.encompasserve.org>e  S In article <c82at5$d3$1@lore.csc.com>, Nic Clews <sendspamhere@[127.0.0.1]> writes:a > B > Yes I said weekly. Very stable otherwise. Any advance on weekly?  G    Our MVS friends always advised a weekly reboot to "clean things up".   D    I reboot VMS almost exclusively for power failures.  Between them    systems stay up for months.   ------------------------------    Date: 14 May 2004 12:07:34 -05007 From: "Gareth V. Williams" <graff@cfa0.cfa.harvard.edu>  Subject: Re: longest uptimet. Message-ID: <40a4eec6@cfanews.cfa.harvard.edu>  & Klaus-D. Bohn <info@it-bcsb.de> wrote:@ : im searching for the longest uptime from a VMS System/Cluster.  
 $ show sysM VAX/VMS V6.1  on node CFAPS0  14-MAY-2004 11:58:19.77   Uptime  1160 17:28:27   E   This machine is on a UPS, but a building-wide extended power outageiC due to maintenance drained the batteries.  If that hadn't occurred, * the uptime would be well over 2000 days...     -- wH ------------------------------------------------------------------------H Gareth V. Williams, MS 18, 60 Garden Street, Cambridge, MA 02138, U.S.A.+ Associate Director, IAU Minor Planet Center-H gwilliams@cfa.harvard.edu        http://cfa-www.harvard.edu/iau/mpc.html7 OpenVMS & RISC OS: refined choices in operating systemsR   ------------------------------    Date: 14 May 2004 09:59:55 +0100K From: pmoreau@ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.68.40):G Subject: Re: Poor VMS file create performance compared to Linux/FreeBSDb! Message-ID: <V1Q82Fg7HlJj@sinead>f  W In article <2gj3a1F3cp4iU1@uni-berlin.de>, Paul Sture <nospam@sture.homeip.net> writes:_ [...]a > K > IIRC, one of the things which came out of David Mathog's research or one iG > of the related discussions was that of default RMS extend size. IIRC _I > (again), Hunter Goatley incorporated a larger value for this in HGFTP, e- > resulting in significant performance gains.o  L RMS default parameters are too conservative. I use some modified parameters:   $ set rms/seq/block=127/buff=8 $ set rms/ind/buf=20 $ set rms/extent=2048O  I and performance is not bad at all (however untar is always rather slow).    I Greater extent size are even useful when creating big backup savesets or _ big zip archives.    Patrickn --O ===============================================================================sN pmoreau@ath.cena.fr  (CENA)      ______      ___   _          (Patrick MOREAU)4 moreau_p@decus.fr (DECUS)       / /   /     / /|  /|J CENA/Athis-Mons FRANCE         / /___/     / / | / |   __   __   __   __  N BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  |N 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__|N http://www.ath.cena.fr/~pmoreau/            http://www.multimania.com/pmoreau/O ===============================================================================H   ------------------------------  % Date: Fri, 14 May 2004 07:55:27 -0400e' From: "Main, Kerry" <kerry.main@hp.com>aG Subject: RE: Poor VMS file create performance compared to Linux/FreeBSDlR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB31470D@tayexc19.americas.cpqcorp.net>   > -----Original Message-----: > From: Patrick MOREAU, CENA Athis, Tel: 01.69.57.68.40=20! > [mailto:pmoreau@ath.cena.fr]=20  > Sent: May 14, 2004 5:00 AM > To: Info-VAX@Mvb.Saic.Comn> > Subject: Re: Poor VMS file create performance compared to=20 > Linux/FreeBSDy >=20: > In article <2gj3a1F3cp4iU1@uni-berlin.de>, Paul Sture=20# > <nospam@sture.homeip.net> writes:t > [...]r > >=20? > > IIRC, one of the things which came out of David Mathog's=20d > research or one=20@ > > of the related discussions was that of default RMS extend=20 > size. IIRC=20 > > > (again), Hunter Goatley incorporated a larger value for=20 > this in HGFTP,=20y/ > > resulting in significant performance gains.i >=20< > RMS default parameters are too conservative. I use some=20 > modified parameters: >=20$ > $ set rms/seq/block=3D127/buff=3D8 > $ set rms/ind/buf=3D20 > $ set rms/extent=3D2048R >=20? > and performance is not bad at all (however untar is always=20o > rather slow).=20 >=20A > Greater extent size are even useful when creating big backup=20x > savesets or=20 > big zip archives.  >=20	 > Patricke > -- > =hL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=$ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D5 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DEB > pmoreau@ath.cena.fr  (CENA)      ______      ___   _         =20 > (Patrick MOREAU)6 > moreau_p@decus.fr (DECUS)       / /   /     / /|  /|@ > CENA/Athis-Mons FRANCE         / /___/     / / | / |   __  =20 > __   __   __ =20? > BP 205                        / /         / /  |/  |  |  |=20e > |__| |__  |__| |  |eA > 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| |=20e > \  |__  |  | |__| 0 > http://www.ath.cena.fr/~pmoreau/           =20$ > http://www.multimania.com/pmoreau/ > =HL =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=L =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=$ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D5 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Ds  C As Patrick mentioned, there are a number of areas where the defaultoG OpenVMS parameters should be adjusted if one wants to compare apples to ( apples performance with other platforms.   A few quick thoughts:   C 1. Ensure all drives have the default "highwater marking" attributeuF removed - especially for write performance. This is a security feature? that will zero any unallocated blocks before it performs the IObE requested by the user. Many Customers choose not to have this defaultl7 attribute on all of their drives. It can be removed by:-  = $ set volume/nohigh $1$dgaxx (do not need to dismount drives)aH $ pipe show dev d/full |search sys$pipe high (to check all drives to see3 if any drives have highwater marking still enabled)p  D 2. With VMS V7.3-1 and later, you can set the application to use RMS? write back in a similar manner as the default on a UNIX system.r
 Reference: =20.F http://h71000.www7.hp.com/openvms/os/v731features.html (scroll down to RMS)' - Increase in default I/O transfer sizel% - Increase in default autoextend sizerG - RMS writebehind performance option (RMS_SEQFILE_WBH is dynamic sysgen 
 parameter)A - New readahead hint passed by RMS to XFC to prefetch disk blocksm  A Reference the following for more details on the RMS new features:ME http://h71000.www7.hp.com/doc/731FINAL/6657/6657pro_007.html (sectionwG 5.11.3 for the write behind feature that allows OpenVMS to perform in av0 nature similar to UNIX default i.e. write-back.)  > 3. I would use VMS V7.3-2 as it has numerous other performance) enhancement features as well over V7.3-1.    Regardst  
 Kerry Main Senior ConsultantO HP Services Canada Voice: 613-592-4660o Fax: 613-591-4477c Email: kerryDOTmainAThpDOTcomn. (remove the DOT's and AT for email address)=20   ------------------------------    Date: 14 May 2004 07:38:46 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) G Subject: Re: Poor VMS file create performance compared to Linux/FreeBSDl3 Message-ID: <dBbtQdSqLoiN@eisner.encompasserve.org>n  U In article <40A44ABC.2000702@MMaz.com>, "Barry Treahy, Jr." <Treahy@MMaz.com> writes:t > H > IMNHO, VMS needs to do a better job of handling the Un*x code because D > Un*x predates VMS, and though many of us thrashed Un*x during the J > VMS/Un*x wars, I suspect that Un*x will outlive VMS and it is something J > we need to learned to live with... Frankly, I'd take a good Un*x system  > over Microcrap anytime...- >   G    Nonsense.  We all know the ENTERP:: will run on VMS, long after UNIXa    literally runs out of time.   ------------------------------    Date: 14 May 2004 06:59:52 -07006 From: andrew.rycroft@intrinsitech.com (Andrew Rycroft)G Subject: Re: Poor VMS file create performance compared to Linux/FreeBSDt= Message-ID: <58ba0101.0405140559.25afc985@posting.google.com>e   As someone once told me -e  . Gee its fast, but boy can it corrupt your data    Z "Barry Treahy, Jr." <Treahy@MMaz.com> wrote in message news:<40A44ABC.2000702@MMaz.com>... > David J. Dachtera wrote: >  > >Simon Clubley wrote:a > >  h > >eL > >>I am seeing very poor VMS I/O performance compared to Linux/FreeBSD whenL > >>trying to perform the same task - unpacking a GCC tar archive - on these3 > >>operating systems. A table of results is below.M > >>
 > >>[snip] > >>M > >>[5] The VMSTAR binaries supplied as part of the GNV kits were slower than 0 > >>the VMSTAR that I linked. I do not know why. > >>     > >> > >cC > >I think there's a primary clue. tar, being a UN*X "baby", is nott > >optimized for VMS.y > > D > >In general, I find the performance of most UN*X-ware to be ratherK > >disappointing on VMS, and I don't consider it for comparison to "native"n > >VMS code. > >  t > >kF > "Native" probably isn't the best word as anything that is compiled, H > linked, and runs on VMS is "native" to the VMS OS.  The real issue is G > that the API libraries that allow Un*x code to run on VMS, basically pH > emulating a Un*x environment, fumbles the proverbial performance ball J > therefore I would say that has less to do with the apps, otherwise they 8 > would also run poorly on Un*x, which isn't the case... >  > H > IMNHO, VMS needs to do a better job of handling the Un*x code because D > Un*x predates VMS, and though many of us thrashed Un*x during the J > VMS/Un*x wars, I suspect that Un*x will outlive VMS and it is something J > we need to learned to live with... Frankly, I'd take a good Un*x system  > over Microcrap anytime...v >  >  > Barryy   ------------------------------  % Date: Fri, 14 May 2004 10:31:47 -0400>) From: Andrew Robert <arobert@townisp.com>m Subject: Re: SPAM, etc0 Message-ID: <10a9m2ktp5fe9c7@corp.supernews.com>  F If you need a nice application to get rid of spam, I highly recommend > the Spambayes open source Outlook plugin found on Sourceforge.  ; The Sourceforge link is http://spambayes.sourceforge.net/ .V  C I've been using it for some time with extremely impressive results.s     Chuck Chopp wrote: > Tom Linden wrote:u > ; >> In my never ending efforts to get rid of spam and virii,h= >> I come across a lot I don't follow.  I am running MX5.3 on : >> 7.3-1 and I use Outlook as a pop client.  What shows up, >> on the subject line appears intelligible, >>> >> Stuart, You can delegate authority, but not responsibility. >>; >> Now, I am not stupid enough to open this type of mail inl8 >> other than VMS mail, and looking at the 822 header it> >> appears as gibbersih.  Is this perhaps a character encoding >> that Outlook understands, >>J >> Here is the header and then there is a .gif attachment, likely a virus.@ >> are =?  ?= delimiters that can be used to effectively filter? >>: >> From:   SMTP%"dugzzfeabrrzwy@attbi.com"  "Clint Jepson"  >> To:     SMTP%"tom@kednos.com" >> CC: >> Subj:K >> =?utf-8?B?U3R1YXJ0LCBZb3UgY2FuIGRlbGVnYXRlIGF1dGhvcml0eSwgYnV0IG5vdCByZX  >> Nwb25zaWJpbGl0eS4=?=  >  > K > It tells you what you need to know, I think, when you see the "utf-8" at rJ > the start of the subject.  I'm not 100% certain about the "=?" and "?=" H > as delimiters, although they appear to function as such.  I'd have to J > review teh SMTP related RFCs to know for certain.  However, the "utf-8" E > reference indicates that the subject line text is encoded in UTF-8 t9 > characters rather than plain old ANSI/ASCII characters.e >  >    ------------------------------  % Date: Fri, 14 May 2004 15:12:52 +0100 O From: Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com>y* Subject: Re: SUN fails to advertise VMS...0 Message-ID: <c82k54$bdt$1@new-usenet.uk.sun.com>   Bob Ceculski wrote:n > Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<c7qp4d$jbd$1@new-usenet.uk.sun.com>...  > 4 >>>"Belkin Plugs in HP Superdome System; Unplugs Sun >>>-J >>>Manufacturer taps HP to replace Sun Solaris and consolidate information; >>>technology infrastructure; Performance soars 250 percent $ >>>PALO ALTO, Calif., Feb. 11, 2004" >>>o >>I >>Last time I looked Belkin were using a Sun E6500 and E4500 so lets just E >>hope that it was a really really tiny SuperDome that delivered 250%WG >>better throughput. Being 250% faster than a system thats over 5 years G >>old and having a TCO thats lower than a system thats over 5 years old-3 >>isn't that impressive its what you should expect.: >>	 >>Regardsm >>Andrew Harrison  >  > ? > what you should expect is that OpenVMS system to replace thatI> > slowaris garbage and its 1100 certs and counting with a cert> > count that is 13 over the last 10 years and an os that can't > get viruses!  9 Naughty naughty Bob, remember you havn't established thate8 you have a right to mention Cert and OpenVMS in the same9 posting and your can't get virus's point has already been 	 debunked.J  ' Why keep repeating proven untruths ????W   Regardse Andrew Harrisons   ------------------------------   Date: 14 May 2004 16:38:11 GMT, From: bill@gw5.cs.uofs.edu (Bill Gunshannon)* Subject: Re: SUN fails to advertise VMS...* Message-ID: <2gkavjF3q593U1@uni-berlin.de>  0 In article <c82k54$bdt$1@new-usenet.uk.sun.com>,R 	Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> writes: > Bob Ceculski wrote:n >> Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<c7qp4d$jbd$1@new-usenet.uk.sun.com>... >>  5 >>>>"Belkin Plugs in HP Superdome System; Unplugs Suno >>>>K >>>>Manufacturer taps HP to replace Sun Solaris and consolidate information < >>>>technology infrastructure; Performance soars 250 percent% >>>>PALO ALTO, Calif., Feb. 11, 2004"  >>>> >>>rJ >>>Last time I looked Belkin were using a Sun E6500 and E4500 so lets justF >>>hope that it was a really really tiny SuperDome that delivered 250%H >>>better throughput. Being 250% faster than a system thats over 5 yearsH >>>old and having a TCO thats lower than a system thats over 5 years old4 >>>isn't that impressive its what you should expect. >>> 
 >>>Regards >>>Andrew Harrison >> v >> e@ >> what you should expect is that OpenVMS system to replace that? >> slowaris garbage and its 1100 certs and counting with a certl? >> count that is 13 over the last 10 years and an os that can'tt >> get viruses!P > ; > Naughty naughty Bob, remember you havn't established thatm: > you have a right to mention Cert and OpenVMS in the same; > posting and your can't get virus's point has already beenI > debunked.  > ) > Why keep repeating proven untruths ????e >   I In his usual manner, Bob comes off looking as silly as ever.  The articleaH I just read on the subject made it quite clear that the move was to HPUX and had nothing to do with VMS,i   bill   -- hJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   a   ------------------------------  % Date: Fri, 14 May 2004 15:30:38 +0100oO From: Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com>b* Subject: Re: SUN fails to advertise VMS...0 Message-ID: <c82l6g$bte$1@new-usenet.uk.sun.com>   David Svensson wrote:o  B > He did not point out that Suns ad campaign was the cause of HP'sD > campaign. He pointed out that Suns ad campaign might have been theH > cause of customer experiences such as those in the press release. SuchA > experiences might have been the case before Sun started it's ad E > campaign. That is why I say a time machine is not needed as a basisc > for what he said.e  8 The example was cited as a sucess for the HP campaign to# get Sun customers to migrate to HP.   , Does that help or are you still struggling ?   regardsB Andrew Harrisonl   ------------------------------  % Date: Fri, 14 May 2004 10:36:20 -0400o2 From: "Jonathan Boswell" <jsb.NOSP@M.cdrh.fda.gov>4 Subject: TCPIP Services V5.4 on OpenVMS/Alpha V7.2-23 Message-ID: <FP4pc.255$Ny6.909@mencken.net.nih.gov>   J Has anybody tried this unsupported configuration?  I am trying to cut down on spam (again).   ------------------------------  % Date: Fri, 14 May 2004 16:13:26 +0100a( From: "Mark Iline" <ivax@meng.ucl.ac.uk>8 Subject: RE: TCPIP Services V5.4 on OpenVMS/Alpha V7.2-22 Message-ID: <000001c439c6$01997ac0$ef362880@WANDA>  : From: Jonathan Boswell [mailto:jsb.NOSP@M.cdrh.fda.gov]=20 =20 I > Has anybody tried this unsupported configuration?  I am trying to cut =  down on spam (again).  % 'Fraid  can't answer your question...a  G However, as I'm running v5.3 on that version of VMS I'm interested in =e thenJ answer. I'm also curious what particular advantages 5.4 gives over 5.3.=20     Mark   Mark Iline, UCL Mech ENg   ------------------------------    Date: 14 May 2004 05:41:18 -0700( From: bob@instantwhip.com (Bob Ceculski)E Subject: Re: Terry Shannon's "HP: Two Years Post-Merger Presentation"h= Message-ID: <d7791aa1.0405140441.3e8826fc@posting.google.com>   \ Paul Sture <nospam@sture.homeip.net> wrote in message news:<2gh8c7F2ppi0U1@uni-berlin.de>...  ; sounds like damage control to me ... and I wouldn't believeB; half that, as EV8 would have been cheap to make compared tos8 itanium ... itanium only holds a lead over alpha because5 alpha has been held back for years now to allow it tok6 catch up ... I think you can find the real reason that7 alpha was canned in their, because intel told compaq toe& get rid of it or no more cheap pcs ...   ------------------------------  % Date: Fri, 14 May 2004 14:02:47 +0300-+ From: Jaan Kronberg <jaan.kronberg@mail.ee>a1 Subject: Re: Timestamp format stored in RMS file?e/ Message-ID: <opr7zkyxygxckwek@diablo.uninet.ee>m  G On Thu, 13 May 2004 16:45:42 +0100, Richard Brodie <R.Brodie@rl.ac.uk> c wrote:   >p; > "Jaan Kronberg" <jaan.kronberg@mail.ee> wrote in message e+ > news:opr7x0i8q6xckwek@diablo.uninet.ee...h >  >> 8 bytes:d >> 0000 36BD 04FB A200 >>E >> Could anybody "translate" it to "readable" date without using any o >> built-inn >> OpenVMS function? >hF > Yes. Time in 100 nanosecond intervals since November 17th 1858, as a > 64-bit word. >n > Some Python: >t! >>>> base = '1-jan-1970 00:00:00'T  >>>> vms.starlet.bintim(base)[1] > 35067168003000000L? >>>> seconds = ( 0xA2FB04BDBDCDA0L - 35067168002100000L ) / 1E7 ' >>>> time.asctime(time.gmtime(seconds))s > 'Thu Apr  1 00:00:00 2004' >e > Close enough:t- >>>> vms.starlet.asctim(0xA2FB04BDBDCDA0L)[1]y > ' 1-APR-2004 00:00:00.89'w >a >p >       % Thank you all, folks, esp. Richard :)   K He answered what I actually needed - platform-independent code (algorythm) f0 for translating vms time from quadword to ascii.    
 thanks again,t jk   ------------------------------  % Date: Fri, 14 May 2004 13:52:27 +0100o* From: "Richard Brodie" <R.Brodie@rl.ac.uk>1 Subject: Re: Timestamp format stored in RMS file?u, Message-ID: <c82fec$12rq@newton.cc.rl.ac.uk>  \ "Richard Brodie" <R.Brodie@rl.ac.uk> wrote in message news:c80578$1a3s@newton.cc.rl.ac.uk...  " > >>> base = '1-jan-1970 00:00:00'! > >>> vms.starlet.bintim(base)[1]u  L I had some noise in the fractional seconds part by forgetting to specify theB hundreths as zero. Hoff's code does too, so I'm in good company ;)   ------------------------------  % Date: Fri, 14 May 2004 18:25:47 +0200 2 From: martin@radiogaga.harz.de (Martin Vorlaender)1 Subject: Re: Timestamp format stored in RMS file? ; Message-ID: <40a4f30b.524144494f47414741@radiogaga.harz.de>e  , Jaan Kronberg (jaan.kronberg@mail.ee) wrote:' > Thank you all, folks, esp. Richard :)r >gM > He answered what I actually needed - platform-independent code (algorythm) A2 > for translating vms time from quadword to ascii.  ? You can find (Visual) C++ class code to deal with VMS quadwordsh (including time) on my website.    cu,    Martin -- y>                     | Martin Vorlaender    |    OpenVMS rules!-   Smiert Spamionem  | work: mv@pdv-systeme.det@                     |   http://www.pdv-systeme.de/users/martinv/4                     | home: martin@radiogaga.harz.de   ------------------------------  + Date: Fri, 14 May 2004 00:50:46 -0500 (CDT)t From: sms@antinode.org& Subject: Re: VMS, tftp & ftp questions) Message-ID: <04051400504620@antinode.org>4  % From: Neil Cherry <njc@wolfgang.uucp>r  H > Thanks, do you know the path to where tftp file will land? I need that" > so I can create the files there.  G    As my only TFTP consumer is a Cisco 678, and I download its firmware:: over a serial line from a Mac, I never use the stuff, but:   alp $ show logical *tftp*t   [...]h   (LNM$SYSTEM_TABLE)  8   "TCPIP$TFTP_ROOT" = "SYS$SYSDEVICE:[TCPIP$TFTP_ROOT.]"   [...]   H    I believe that this stuff gets created when you configure the service! ("SYS$MANAGER:TCPIP$CONFIG.COM").i   ALP $ tcpip show version  ?   Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 2>4   on a AlphaStation 200 4/233 running OpenVMS V7.3-1  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org.    Saint Paul  MN  55105-2547d   ------------------------------  % Date: Fri, 14 May 2004 09:31:49 -0500e% From: Neil Cherry <njc@wolfgang.uucp>F& Subject: Re: VMS, tftp & ftp questions- Message-ID: <slrnca9lt0.pp.njc@wolfgang.uucp>   A On Fri, 14 May 2004 00:50:46 -0500 (CDT), sms@antinode.org wrote:&' > From: Neil Cherry <njc@wolfgang.uucp>p > I >> Thanks, do you know the path to where tftp file will land? I need that # >> so I can create the files there.t > I >    As my only TFTP consumer is a Cisco 678, and I download its firmwaree< > over a serial line from a Mac, I never use the stuff, but: >  > alp $ show logical *tftp*  >  > [...]i >  > (LNM$SYSTEM_TABLE) > : >   "TCPIP$TFTP_ROOT" = "SYS$SYSDEVICE:[TCPIP$TFTP_ROOT.]" >  > [...]o > J >    I believe that this stuff gets created when you configure the service# > ("SYS$MANAGER:TCPIP$CONFIG.COM").e >  > ALP $ tcpip show version > A >   Compaq TCP/IP Services for OpenVMS Alpha Version V5.3 - ECO 2 6 >   on a AlphaStation 200 4/233 running OpenVMS V7.3-1  F Thanks that was a big help (really!). I've discovered that my tftp hasC a problem (-TCPIP-W-NORECORD, information not found). Sounds like I&E haven't setup my tftp properly. Now if I can find in my notes where IBF configured it. Oops, I found it @TCPIP$CONFIG (hey I'm really learning this stuff! ;-).   I think the path is:   SYS$SYSDEVICE:[TCPIP$TFTP]  F I've been able to create a file called foo (just a temp file for now).   Thanks for everyone's help.a   -- 0D Linux Home Automation         Neil Cherry        ncherry@comcast.net; http://home.comcast.net/~ncherry/               (Text only)5= http://linuxha.sourceforge.net/                 (SourceForge)w8 http://hcs.sourceforge.net/                     (HCS II)   ------------------------------    Date: 14 May 2004 02:22:17 -0700' From: g.wiedijk1@chello.nl (G. Wiedijk) % Subject: where to find devicedrivers? < Message-ID: <b4b0cdc.0405140122.76bc5d9e@posting.google.com>  D The file sys$config.dat is mentioning sys$pkq160driver for an QlogicC 12160 SCSI controller, which i intend to buy, but where to find theeB actual file, which is nowhere on the disk (VMS 7.3.2). TIA, Gerrie   ------------------------------  # Date: Fri, 14 May 2004 16:30:17 GMTe# From: hoff@hp.nospam (Hoff Hoffman)r) Subject: Re: where to find devicedrivers?-2 Message-ID: <tu6pc.1509$k64.1207@news.cpqcorp.net>  f In article <b4b0cdc.0405140122.76bc5d9e@posting.google.com>, g.wiedijk1@chello.nl (G. Wiedijk) writes:E :The file sys$config.dat is mentioning sys$pkq160driver for an QlogictD :12160 SCSI controller, which i intend to buy, but where to find theC :actual file, which is nowhere on the disk (VMS 7.3.2). TIA, Gerrie   G   AFAIK, the SYS$PKQ160DRIVER driver is probably presently only seen inaI   the wild in conjunction with OpenVMS I64 V8.0 and later -- I do see theuG   driver latent in the OpenVMS Alpha V8.2 build, as well is in the V8.0 E   and V8.1 OpenVMS I64 releases, as well as in the current baselevel.   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqcN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------    Date: 14 May 2004 02:11:25 -0700. From: martinkirby12@yahoo.co.uk (Martin Kirby) Subject: Re: XDMP and TCPIP 5.4m< Message-ID: <224291b.0405140111.488e8d17@posting.google.com>   Tony,   D I only tried XDMP once, with eXcursion, so I may be misunderstandingE how it works. When you run it I think you are saying that it produceswF its own login box not the standard DECwindows one. So my understandingC of the login process may have been wrong and that would explain whyt the login log was empty.   > H > I can also run the command procedure generated by XDM that starts the ' > dtsession manually and that works OK.i >e  C That is very interesting. Can you post the contents of that commandg file?a  F When you run this command file is the first thing the blue screen withF the welcome message on it ? If so, do you get the welcome message whenF you start it from XDM ? Just trying to isolate where the login process fails.   Regards,   Martin Kirby   ------------------------------  % Date: Fri, 14 May 2004 16:08:02 +0100l) From: Tony Arnold <tony.arnold@man.ac.uk>  Subject: Re: XDMP and TCPIP 5.4l- Message-ID: <c82nci$1fk6$1@godfrey.mcc.ac.uk>    Martin,    Martin Kirby wrote:L  F > I only tried XDMP once, with eXcursion, so I may be misunderstandingG > how it works. When you run it I think you are saying that it producessH > its own login box not the standard DECwindows one. So my understandingE > of the login process may have been wrong and that would explain why- > the login log was empty.  ? Correct, the login box is the XDMP own box. Very plain looking!m  H >>I can also run the command procedure generated by XDM that starts the ' >>dtsession manually and that works OK.s >> >  > E > That is very interesting. Can you post the contents of that command. > file?c  - It's a one line command procedure as follows:s  C $ @SYS$COMMON:[SYSEXE]TCPIP$XDM_XSESSION.COM aca-vnt.mc.man.ac.uk:1e  J It gets created in sys$specific:[tcpip$xdm.work]ACA-VNT_MC_MAN_AC_UK_1.COM  . aca-vnt.mc.man.ac.uk is the dns name of my PC.  H > When you run this command file is the first thing the blue screen withH > the welcome message on it ? If so, do you get the welcome message whenH > you start it from XDM ? Just trying to isolate where the login process > fails.  D Running the above manually giv es teh same as if I logged in at the H console. I.e., it sets the background and then all the windows start to A appear. If I run it via an XDM connection, then all I get is the eF hourglass cursor. Not even the background gets set. The log file sfor ? the server tells me a request from a clinet has been rejected. tF Unfortunately, the current Cygwin X server does not provide any debug  level logging at the moment.  H A thought has just occurred. I could try this to a Linux box and see if ! that works/give more information!0   Regards, Tony.    ------------------------------    Date: 14 May 2004 07:23:09 -0700& From: jordan@ccs4vms.com (Rich Jordan)2 Subject: Re: XFC experiences on OpenVMS Alpha V7.3< Message-ID: <cc5619f2.0405140623.e650da2@posting.google.com>  v koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote in message news:<Sz9cU9RkKhVO@eisner.encompasserve.org>...h > In article <cc5619f2.0405121155.3d5b0b5a@posting.google.com>, jordan@ccs4vms.com (Rich Jordan) writes:G > > Got an Alpha VMS system running V7.3 that I can't currently upgradeMI > > due to production contraints.  I have been given a window in a couple J > > of weeks to update patches to current (last patch installed was UpdateF > > V2); that will include Update V3 and any class 1 or needed class 2J > > patches.  I note that XFC patch is up to version 4.  We've not enabledI > > XFC on this node, despite the presence of the earlier XFC patches due H > > to the early problems that were reported, I believe even with the V1
 > > patch. > F >    You just need a couple more patches.  One is called 7.3-1 and the >    other is called 7.3-2.t > ; >    If you're changing software, you're changing software._    E Third party apps on the system are not certified for use on newer VMSrE releases.  Upgrading them to certified versions is not possible given 1 the small downtime window that is being provided.e   Rich   ------------------------------  % Date: Fri, 14 May 2004 09:22:06 +0200 9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com>s2 Subject: Re: You'll never guess what HP advertised' Message-ID: <40A4739D.36E1D930@aaa.com>r   Bob Koehler wrote: > L > > Last time I checked, MVS still using 80 columns fixed length records for > > many things. > I >    Yep.  But irrelevant.  I can do 80 column fixed length on Linux if Ic! >    just want to write the code.   6 Yes, but in MVS it's much more built in in the kernel.  = Some IBM guy once said that MVS is primarily a large batch OS@D with 80 char input (card reader) and 132 char output (line pirnter).C The rest (network, terminal I/O, you name it) is just emulations...t  D Heck, still today, when you "submit" a batch job on MVS, you actualy sendA it to the "Internal Card Reader", which is just an emulation of a  physicalF 80 char punched card reader :-) The MVS kernel still *thinks* that the. batch stream comes from a punched card reader.  C And the systems to catch batch output on-file, is just add-ons thatn' hooks into the line printing subsystem.   C That might be one of the reasons that constructs like "GOTO" are sotC hard to implement in MVS batch streams. You can not jump back to an C earlier punched card. The only thing you can do, is to conditionalyw= run or not run a specific "step" in the job depending on the l7 "completion code" from an earlier step in the same job.e  	 Jan-Erik.s   ------------------------------    Date: 14 May 2004 07:26:22 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)d2 Subject: Re: You'll never guess what HP advertised3 Message-ID: <GRr6yooOYeM2@eisner.encompasserve.org>U  Z In article <c8058o$1k13$1@news.cybercity.dk>, "Karsten Nyblad" <nospam@nospam.com> writes: > M > Very true.  However, there are always some companies with relatively stablehN > applications that chose not to move on.  They are betting on not runing intoM > problems because they rarely change anything.  That is what we have seen ino > the past.  >   H    And then those who tried to move on, failed miserably, and went back.   ------------------------------    Date: 14 May 2004 07:29:43 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)n2 Subject: Re: You'll never guess what HP advertised3 Message-ID: <2bnvzI7Iz2VH@eisner.encompasserve.org>e  Z In article <c806vr$1m1a$1@news.cybercity.dk>, "Karsten Nyblad" <nospam@nospam.com> writes: > N > So you would like to tell the customers that the security of HP-UX is not as > good as that in VMS.      Sounds good to me.   F    As a salesman working in shoes, lumbers, bolts, nuts, ..., as I wasG    working my way through college I often found it helpfull to tell the B    customer what was different between products.  The cost/benefitH    decision was theirs, not mine.  Being accurate and honest gained many    repeat customers.  H    See "Miracle on 34th Street" for part of my inspiration.  It works in    real life, too.   ------------------------------    Date: 14 May 2004 07:30:41 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)62 Subject: Re: You'll never guess what HP advertised3 Message-ID: <E$8yzRAIdYfR@eisner.encompasserve.org>D  M In article <TKeKOfWyGVx5@wvnvms>, cook@wvnvms.wvnet.edu (George Cook) writes:c  H > Yes, I do recall the extra bits of addressing issue being discussed inH > my 360/370 assembler class in college, but no longer recall much aboutK > it (my assembler book/notes are packed too deeply away for quick access).mL > However both the 360 and 370 System Summary books describe an architecture > with 24 bits of addressing.V  -    That's not the way IBM explained it to us.a   ------------------------------    Date: 14 May 2004 07:33:28 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)n2 Subject: Re: You'll never guess what HP advertised3 Message-ID: <f5roiTKQURix@eisner.encompasserve.org>l  c In article <40A4739D.36E1D930@aaa.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> writes:- > Bob Koehler wrote: >> yM >> > Last time I checked, MVS still using 80 columns fixed length records for  >> > many things.t >> mJ >>    Yep.  But irrelevant.  I can do 80 column fixed length on Linux if I" >>    just want to write the code. > 8 > Yes, but in MVS it's much more built in in the kernel. >   C    Yes, I know.  This was exlained to me by an MVS internals fellow2>    a long time ago.  According to him the whole thing is stillF    a big electronic punch card processor (IBM started with punch cards!    processing them mechanically).l   ------------------------------  % Date: Fri, 14 May 2004 13:17:17 -0400-# From: "John Smith" <a@nonymous.com> = Subject: [General]: Understanding 'Mean Time Between Failure' , Message-ID: <oaudnS7z1f68YjndRVn-vw@igs.net>  < http://itmanagement.earthweb.com/columns/article.php/3354191  ) Understanding 'Mean Time Between Failure'i By George Spafford May 14, 2004  L Mean Time Between Failure (MTBF) is a much-used management metric in IT both3 for discrete components as well as overall systems.:  L For simplicity, let's define MTBF as the average time between failures. It'sH either based on historical data or estimated by vendors and is used as aL benchmark for reliability. Organizations trending MTBF over time can readilyG see devices that are failing above average and take appropriate action.l  I Where MTBF breaks down is when management puts too much faith in unproveneG MTBF estimates and uses them to justify inordinately massive amounts ofnK capital investment on complex systems. This may seem to be a bold statementv( and therefore requires some explanation.  I If we assume that there are 8,760 hours per year (365 days x 24 hours pernI day) then we can divide MTBF claims from vendors and look at how long the L system will run in years. If we buy a system, or component, with a rating ofL 30,000 MTBF, then we might assume that on average, the system would run 3.42I years without a failure. Granted, there are always statistical variations_D around the average, but 3.42 years doesn't seem bad at all, does it?  J There's a problem with this rationale, however, especially when applied toK complex systems. First, as previously mentioned, it is both an estimate and F an average. You run the risk of being one of the seemingly statisticalJ anomalies with a far higher frequency of failure that gets smoothed out byD the averaging! The reason could simply be that the MTBF estimate wasD subjected to different environmental factors such as heat and power.  J Second, fault-tolerance costs accelerate very rapidly as higher and higherL MTBF levels are sought. Third and perhaps the most important, fault-tolerantK systems (hardware, software, documentation and processes) in general becomea? increasingly complex as the level of fault tolerance increases.rI Fault-tolerant systems typically are more complex than non-fault-tolerantfF systems. This increased level of complexity, in and of itself, creates fertile ground for disasters.     ) Coupling, Complexity and Normal Accidents=  F In 1984, Charles Perrow wrote an amazing book titled Normal Accidents:K Living with High Risk Technologies. In it he observed that system accidentscF can be the result of one big failure, but most often are caused by the@ unexpected interactions between failures of multiple components.  G In other words, complex systems whose components are tightly integrated I typically fail through the culmination of multiple components failing andeL interacting in unexpected ways. For example, it's very rare that a plane hasG a wing fall off mid-flight. It's far more likely that several component D failures interact in unpredictable ways that, when combined, cause a> catastrophe. Let's investigate this line of reasoning further.  K First, errors can be readily visible or latent. The former we can deal with J when we detect them. The latter are far more insidious because they can be= in a system and undetected, "waiting to spring," if you will.=  L Second, complex systems made up of hundreds, if not thousands of components,J that interact tightly are considered to be tightly "coupled." The possiblyJ pathways of interaction are not necessarily predictable. Perrow points outK that during an accident, the interaction of failed components can initiallyh be incomprehensible.  H Let's take a highly fault-tolerant database server with its own externalL RAID and then use clustering software to join it with another server located in another data center.   H At this point, we have a pretty complex system comprised of thousands ofK components that are all tightly coupled. The IT operations staff is capableD) and diligent, performing nightly backups.3  L Now, imagine that there is a programming error on the RAID controller causedK by an unexpected combination of data throughput and multi-threaded on-boardDH processor activity that causes a periodic buffer overflow and subsequentL data corruption that is then written to the drives. It doesn't happen often,K but it does happen. As the systems are exact duplicates of one another, the + issue happens on both nodes of the cluster.v  K At an observable level, everything would seem to be OK because the error isiG latent. It isn't readily apparent until one or more database structuresdI become sufficiently corrupt to raise awareness of the issue. Once it doeshJ happen, the network and database people scramble to find out what is wrongL and go tracking through the logs looking for clues and checking for securityB breaches because "it was running fine." The point is that multipleE components can interact in unforeseen ways to bring down a relatively  fault-tolerant system.  J One must also readily conclude that if the chance of errors increases withK the level of complexity, then so to must the probability of errors that can/F cause security breaches. Thus, not only is failure inevitable, but theL likelihood that at least one exploitable security hole exists is inevitable.     Mean Time to Repair (MTTR)  J Let's face it, accidents can and will happen. Fault tolerance can create a? false sense of security. From our 30,000-hour example, we could I unrealistically expect 3.42 years of uninterrupted bliss, but reality and_# Mr. Murphy don't like this concept.i  K Yes, fault tolerance reduces the chance of some errors, but as the system'sdH inherent complexity and level of interaction increases, the chance of anI accident increases. How often is a fault-tolerant system simple? How many I people in your organization fully understand your fault-tolerant systems?aJ There are many questions that can be asked, but here is the most importantJ question: "When the system fails, and it will fail, how easy will it be to	 recover?"6  K Not too surprisingly, there often is a dichotomy with highly fault-tolerantPI systems. On one hand, their likelihood of failure is less than a standardbK system lacking redundancy, but on the other, when they do fail, they can be>, a bear to troubleshoot and get back on line.  D Instead of spending tens, if not hundreds of thousands of dollars onC fault-tolerant hardware, what if IT balanced the costs of the faultrG tolerance with an eye toward unrelentingly driving down the MTTR of the D systems? True systemic fault tolerance is a combination of hardware,L software, processes, training, and effective documentation. Sometimes, teamsE focus on the hardware involved first, the software requirements are a H distant second and then they totally overlook the process, training, and documentation needs.  G Always remember that availability can be addressed by trying to preventeF downtime through fault tolerance as well as by reducing the time spentB recovering when an actual outage does occur. Therefore, activitiesG surrounding the rapid restoration of service and problem resolution are@H essential. The ITIL Service Support book provides great guidance on bothG initially restoring services through Incident Management and ultimatelye@ addressing the root causes of the outage via Problem Management.  H The Berkeley/Stanford Recovery-Oriented Computing (ROC) research team, aG joint project at Berkeley and Stanford, also provides great information   about ROC. You can find it here.     Summarya  I Of course MTBF matters -- it is an important metric to track in regard tokL system reliability. The main point is that even fault-tolerant servers fail.J As the level of complexity and coupling increases, systemic failure due toK the accumulation of component failures interacting in previously unexpectedIL ways is inevitable. IT should look at availability holistically and considerL addressing both initial system design fault tolerance and the speed in which! a failed system can be recovered.e  C In some cases, it may make far more sense to invest less in capitalcH intensive hardware and more on the training, documentation and processes4 necessary to both prevent and recover from failures.   ---------------------------a  G A thought-provoking article on a series of issues that many managements.3 never consider, and most IT departments gloss over.h  L Overall, assuming that one was going to employ properly trained staff in theI first place, I'd consider this article to be making an effective case for I VMS clusters. Some might say that NSK would be a better bet, and for someeG apps that may well be the case. But for the vast majority of companies,-+ OpenVMS style clusters fit the bill better.    ------------------------------   End of INFO-VAX 2004.267 ************************