1 INFO-VAX	Sun, 29 Aug 2004	Volume 2004 : Issue 479       Contents:; Re: CSWS_JAVA v2.1 - won't unpack "war" files automatically  Re: HPworld - I Survived! Re: problems setting up a cluster " Re: Two IPs on same NIC OVMS 7.2-1  F ----------------------------------------------------------------------  % Date: Sun, 29 Aug 2004 12:29:05 -0500 6 From: "Craig A. Berry" <craigberry@mac.com.spamfooler>D Subject: Re: CSWS_JAVA v2.1 - won't unpack "war" files automaticallyD Message-ID: <craigberry-718104.12290529082004@news.isp.giganews.com>  9 In article <Q1oYc.42966$cx.41581@bignews4.bellsouth.net>, ,  Chuck Chopp <ChuckChopp@rtfmcsi.com> wrote:  F > 3)  Copy the WAR file to the APACHE$COMMON:[JAKARTA.TOMCAT.webapps] M > directory on my Alpha system.  I use FTP for this and transfer the file in   > binary mode.  E Which probably gives you a file with fixed length 512-byte records.   5 You probably need to change the file format to STMLF.    ------------------------------   Date: 29 Aug 2004 13:14:06 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)! Subject: Re: HPworld - I Survived * Message-ID: <2pe34tFjorpeU1@uni-berlin.de>  3 In article <89KXc.28056$Jn5.7554@fe1.texas.rr.com>, . 	LESLIE@JRLVAX.HOUSTON.RR.COM (leslie) writes:$ > John Smith (a@nonymous.com) wrote: >:  I >: Or maybe when all the middle-class jobs have been outsourced to India, ( >: China, Pakistan, Phillipines, etc...  >:  6 >    http://inhome.rediff.com/money/2004/aug/26bpo.htm1 >    'All US tech jobs will move out in a decade'  > ? >    http://economictimes.indiatimes.com/articleshow/786093.cms A >    Now comes Knowledge Process Outsourcing - The Economic Times  >   @ Yeah, I was reading about this the other day.  After hearing how> it's all Bush's fault imagine my surprise to see an AustralianB article lamenting the loss of computer jobs to Indian outsourcing.7 I never realized Bush was the president down there too.   @ Of course, the funniest article by far was the one about all theC manufacturing jobs leaving Mexico for place like China and VietNam. * Why, you ask?  Why for cheaper labor.  :-)   >:< >: and nobody here can afford their car payments any longer. >: > > > Maybe people will be able to afford cars from Wal-mart-land: > + >    http://makeashorterlink.com/?G266514A8 ? >    General Motors Officially Launches Cadillac Brand in China   B If that means they are going to be selling them there too, I guess# that's one way to get back at them.    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Sun, 29 Aug 2004 14:57:38 +0100 < From: "Alex Daniels" <AlexNOSPAMTHANKSDaniels@themail.co.uk>* Subject: Re: problems setting up a cluster6 Message-ID: <4131e0cb$0$22749$db0fefd9@news.zen.co.uk>  @ "Rodrigo Ventura" <yoda-NOSPAM@isr.ist.utl.pt> wrote in message 5 news:newscache$4qj63i$shh$1@newsfront4.netvisao.pt...  > Hello everyone,  > ? > I've been trying to set up a OpenVMS cluster using a bunch of H > discontinued alpha workstations. I have two DEC 3000/500 and three DECF > 3000/400. I installed OpenVMS (hobbyist CD, ver 7.3-1) on one of theF > 500's, then I setup the other 500 as a sattelite. All works well now9 > (I even have setiathome running in each one of them ;).  > @ > When I tryed to repeat the procedure in the 400 machines I gotD > problems. I all seemed to went well, during the cluster_config_lanH > script, before the final reboot. When it boots the problems start whenG > the machine is unable to open the paging file (note that a disk local = > to the machine was initialized for that purpose, during the F > cluster_config_lan setup). Then it issues a couple of errors relatedH > with lack of memory, which seem consequence of lack of page file. Then8 > it crashes with a bugcheck=0000036C and a memory dump: >  > $ anal/crash sysdump.dmp > ) > OpenVMS (TM) Alpha system dump analyzer ) > ...analyzing a selective memory dump...  > : > %SDA-W-NOTSAVED, global pages not saved in the dump file' > Dump taken on 27-AUG-2004 10:03:06.66 ! > PROCGONE, Process not in system  >  > System crash information > ------------------------/ > Time of system crash: 27-AUG-2004 10:03:06.66  > H > Version of system: OpenVMS (TM) Alpha Operating System, Version V7.3-1 > ' > System Version Major ID/Minor ID: 3/0  > / > VMScluster node: xxxxxx, a DEC 3000 Model 400  > % > Crash CPU ID/Primary CPU ID:  00/00  > 6 > Bitmask of CPUs active/available:  00000001/00000001 >  > CPU bugcheck codes: 3 >         CPU 00 -- PROCGONE, Process not in system  > $ > CPU 00 Processor crash information$ > ---------------------------------- > = > CPU 00 reason for Bugcheck: PROCGONE, Process not in system  > 2 > Process currently executing on this CPU: SYSINIT > ! > Current image file: SYSINIT.EXE  >  > Current IPL: 0  (decimal)  > ! > CPU database address:  81430000  > $ > CPU 00 Processor crash information$ > ---------------------------------- > * > CPUs Capabilities:    PRIMARY,QUORUM,RUN >  > General registers: > = > R0   = 00000000.00000124  R1   = FFFFFFFF.811214D8  R2   =   > 00000000.00000003 = > R3   = FFFFFFFF.810C1300  R4   = FFFFFFFF.8158D340  R5   =   > 00000000.000000C0 = > R6   = FFFFFFFF.8028A8C4  R7   = 00000000.7FFA1FC0  R8   =   > 00000000.00000000 = > R9   = FFFFFFFF.810D4BF8  R10  = 00000000.7FFCF800  R11  =   > 00000000.7FF741B2 = > R12  = 00000000.00000000  R13  = FFFFFFFF.811214D8  R14  =   > 00000000.00000000 = > R15  = 00000000.000204D8  R16  = 00000000.0000036C  R17  =   > 00000000.000037EF = > R18  = 00000000.00000000  R19  = 00000000.00000000  R20  =   > 00000000.00000000 = > R21  = 00000000.00000110  R22  = 00000000.00000001  R23  =   > 00000000.00000800 = > R24  = 00000000.12016074  AI   = 00000000.00000000  RA   =   > FFFFFFFF.810086A0 = > PV   = FFFFFFFF.811216E8  R28  = 00000000.7FFF01B4  FP   =   > 00000000.7FFA1F20 4 > PC   = FFFFFFFF.8028AD60  PS   = 18000000.00000003 > $ > CPU 00 Processor crash information$ > ---------------------------------- >  > Processor Internal Registers:  > = > ASN  = 00000000.0000003E                     ASTSR/ASTEN =  
 > 0000000F= > IPL  =          00000000  PCBB = 00000000.01D36080  PRBR =   > FFFFFFFF.81430000 = > PTBR = 00000000.00000E9C  SCBB = 00000000.00000959  SISR =   > 00000000.00000000 = > VPTB = FFFFFEFC.00000000  FPCR = 00000000.00000000  MCES =   > 00000000.00000000  > $ >         KSP    = 00000000.7FFA1F18$ >         ESP    = 00000000.7FFA6000$ >         SSP    = 00000000.7FFAE000$ >         USP    = 00000000.7B04DA40 > $ > CPU 00 Processor crash information$ > ---------------------------------- > 8 >                 No spinlocks currently owned by CPU 00 >  >   > Any clues on what is going on? > H > I suspect it has something I did between the install of the second 500G > and the first 400. I noticed that the MONITOR program was unable show  > all nodes status:  >  > MONITOR> mon clus C > %MONITOR-I-ESTABCON, establishing connection to remote node(s)... ; > %VPM-W-NOCONNECT, Unable to connect to remote node xxxxxx 9 > -MONITOR-W-NODEINIERR, error during node initialization ! > %MONITOR-I-CONT, continuing....  > > > So I thought it had something to do with DECnet. Then I used? > NET$CONFIGURE.COM to configure DECnet -- maybe this procedure E > destroyed some previously auto-configured stuff... Then I regretted 4 > and disabled it by (re-)commenting out the "SUBMITB > SYS$MANAGER:STARTNET.COM" command in SYSTARTUP_VMS.COM. Even so, > DECnet still works:  > 
 > $ sh net > G > Product:  DECNET        Node:  xxxxxx               Address(es):  x.x D > Product:  TCP/IP        Node:  xxxxxx.xxx.xxx.xxx.xx Address(es):  > xxx.xxx.xxx.xx > A > This is all very strange to me... (linux wizard & vms newbie ;)  > 	 > Cheers,  >  > Rodrigo Ventura    Can you boot it like this....    P00>>> b -fl x,20000  J Were 'x' is the system root you are booting from. Then post the output of  the point where it crashes.   K If you are using volume shadowing ensure SHADOW_SYS_UNIT is the same as on  8 the other nodes (as you are using a shared system disk).   Alex   ------------------------------  + Date: Sun, 29 Aug 2004 06:10:07 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)+ Subject: Re: Two IPs on same NIC OVMS 7.2-1 $ Message-ID: <cgrrvv$3ih$1@online.de>  E In article <aus-73B346.19565028082004@news.cis.dfn.de>, "Hans M. Aus" # <aus@vim.uni-wuerzburg.de> writes:    $ > 2) What is the difference between  >  > Set interface (didn't work)  > and  > Set configuration interface?  < The former changes the values in memory, the latter on disk.   ------------------------------   End of INFO-VAX 2004.479 ************************