INFO-VAX Tue, 06 Feb 2007 Volume 2007 : Issue 74 Contents: AMD Quad-core Opteron Models Unveiled Re: Change sys$specific:[tcpip$smtp] directory to another disk Re: Disk space problem Re: F$GETSYI("TEMPERATURE_VECTOR") questions Re: F$GETSYI("TEMPERATURE_VECTOR") questions Re: F$GETSYI("TEMPERATURE_VECTOR") questions FYI: Blu-Ray disc as an bootdevice for a Itanium & Alpha (XP1000) Re: FYI: Blu-Ray disc as an bootdevice for a Itanium & Alpha (XP1000) Re: Help building pcre from (HP) Apache sources Re: Help building pcre from (HP) Apache sources Re: How to extract file from pcsi file from Windows ? Re: How to extract file from pcsi file from Windows ? Re: How to extract file from pcsi file from Windows ? Re: How to temporarily disable AUTO_DLIGHT_SAV? Re: How to temporarily disable AUTO_DLIGHT_SAV? Re: How to temporarily disable AUTO_DLIGHT_SAV? Re: Mark Daniel and/or Hein van den Huevel or anyone really Re: Mark Daniel and/or Hein van den Huevel or anyone really Re: Mark Daniel and/or Hein van den Huevel or anyone really Re: Mark Daniel and/or Hein van den Huevel or anyone really Re: Mark Daniel and/or Hein van den Huevel or anyone really Re: Searching FMS documentation in pdf Re: Searching FMS documentation in pdf Re: SWS 2.1 question Re: VMS83A_ACMELDAP-V0100 Re: Wanted: Alisashare / Alisatalk for VMS / VAX Re: Wanted: Alisashare / Alisatalk for VMS / VAX Re: Wanted: Alisashare / Alisatalk for VMS / VAX Re: Wanted: Alisashare / Alisatalk for VMS / VAX ---------------------------------------------------------------------- Date: Tue, 6 Feb 2007 07:23:14 -0500 From: "Neil Rieck" Subject: AMD Quad-core Opteron Models Unveiled Message-ID: <45c87154$0$7457$9a6e19ea@news.newshosting.com> AMD Quad-core Opteron Models Unveiled (for June-2007) http://dailytech.com/AMD+Quadcore+Opteron+Models+Unveiled/article5992.htm The race for the chip multi-processing (CMP) market goes up a notch. Neil Rieck Kitchener/Waterloo/Cambridge, Ontario, Canada. http://www3.sympatico.ca/n.rieck/ ------------------------------ Date: Tue, 6 Feb 2007 07:50:55 +0000 (UTC) From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Change sys$specific:[tcpip$smtp] directory to another disk Message-ID: In article <1170663841.471201.98090@l53g2000cwa.googlegroups.com>, "Bart.Zorn@gmail.com" writes: > A (long) while ago, I did some experiments with TCPIP$SMTP_COMMON. > > First I defined it in LNM$SYSCLUSTER_TABLE (of course), but that did > not seem to have any effect. Then I defined it in LNM$SYSTEM_TABLE and > that stopped SMTP completely. > > I talked about this with Guy Peleg some years ago, and he told me then > that he would be working on TCPIP soon and he would look into the > general quality of things like this. Unfortunately, that day did not > come... As I mentioned in another post, I have it defined like this: $ sh log tcpip$smtp_common "TCPIP$SMTP_COMMON" = "SYS$SPECIFIC:[TCPIP$SMTP]" (LNM$SYSTEM_TABLE) = "CLUSTER_TCPIP_SMTP" 1 "CLUSTER_TCPIP_SMTP" = "CLUSTER_DISK:[SYSTEM.TCPIP_SMTP]" (LNM$SYSTEM_TABLE) I don't think I tried the cluster table, though that would be the logical place for it. In CLUSTER_DISK:[SYSTEM.TCPIP_SMTP] I have stuff like SMTP.CONFIG, TCPIP$SMTP_LOCAL_ALIASES.TXT and so on, i.e. stuff common to all nodes. I am reasonably happy with 5.4, though especially in the area of logical names etc it would be nice to have some more flexibility and have it properly documented. I've looked at some of the TCPIP DCL procedures. It is strange, to say the least. I have the impression that the person who wrote the code doesn't understand the possibilities of VMS. I would thus expect that the expectation that logical names will be honoured would not be fulfilled. There are probably some hard-coded file specs in the code, perhaps some translations of logical names at startup (might be necessary for performance reasons in specialised cases, but in general means a restart is necessary after changing anything in the logical names) etc. ------------------------------ Date: 6 Feb 2007 09:45:23 -0800 From: "Rich Jordan" Subject: Re: Disk space problem Message-ID: <1170783923.592623.284980@q2g2000cwa.googlegroups.com> Just an FYI although its moot at this point. We ran a PC AXP150 for years as our primary Alpha node. We had three (nonshadowed) disks internally; two of them were RZ29s (one B and one L if I remember correctly); we also used front mounted cooling fans in front of those drives. since those drives were bigger and hotter than the system was supposed to be able to support. Ran for years, no real problems. ------------------------------ Date: 6 Feb 2007 08:17:35 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: F$GETSYI("TEMPERATURE_VECTOR") questions Message-ID: In article <480ed$45c80f1d$cef8887a$27875@TEKSAVVY.COM>, JF Mezei writes: > Robert Deininger wrote: >> This particular new feature request needs to be directed at the >> Alphaserver hardware support folks, as has been pointed out before. > > Since there are no publically announced plans to keep on > producing/upgrading Alpha models, such a request would serve no purpose. > > The request should be aimed at VMS so that the temperature vector returns a > string for any/all alpha and even vax models, one where none of the bytes > contain valid temperature (aka: all FFs). This way, command procedures > could be rolled out that will not generate errors no matter what platform > they run on. Or command procedures use in a production system could catch and handle excetions just like any real world software. ------------------------------ Date: Tue, 06 Feb 2007 09:59:35 -0500 From: JF Mezei Subject: Re: F$GETSYI("TEMPERATURE_VECTOR") questions Message-ID: Bob Koehler wrote: > Or command procedures use in a production system could catch and > handle excetions just like any real world software. Spaghetti programming , your program becomes $ON ERROR THEN GOTO labelx $ $set message/nofacility/notext/noseverity/noidentification $temp = f$getsyi("TEMPERATURE_VECTOR") $goto labelY $! $labelx: $temp = "FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF" $! $labely: $set message/nofacility/notext/noseverity/noidentification (process the string) All this instead of 1 line of DCL $temp = f$getsyi("TEMPERATURE_VECTOR") Now, scale this to all DCL where you need to check for every statement and it gets really ugly. ------------------------------ Date: 6 Feb 2007 12:27:00 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: F$GETSYI("TEMPERATURE_VECTOR") questions Message-ID: In article , JF Mezei writes: > Bob Koehler wrote: >> Or command procedures use in a production system could catch and >> handle excetions just like any real world software. > > Spaghetti programming , your program becomes > .Y Impersonate a master, youngling must not. ------------------------------ Date: Tue, 6 Feb 2007 17:14:35 +0100 From: "Eberhard Heuser" Subject: FYI: Blu-Ray disc as an bootdevice for a Itanium & Alpha (XP1000) Message-ID: <000701c74a09$e500bb60$05072286@vg2> Hi, I have bought a PLEXTOR BD-R PX-B900A yesterday. Here is a log that shows that this really nice drive allows you to boot Blu-Rays (and DVDs and CDs, too). I took original OpenVMS discs or burned a Blu-Ray with DVDwrite. Eberhard PS: This drive is a so called second generation drive that burns BDR-R(E) DL with a capacity of ~50 GB... ========================================================= %SYSBOOT-I-BOOT_DRIVERS, detected 00000004 boot drivers. %SYSBOOT-W-EXEC_DATA_SMALL, raising GH_EXEC_DATA to 00000464 pages. HP OpenVMS Industry Standard 64 Operating System, Version V8.2-1 © Copyright 1976-2005 Hewlett-Packard Development Company, L.P. Installing required known files... Configuring devices... %EIA0, Link up: 100 mbit, full duplex, flow control (receive only) %PKA0, Copyright (c) 2001 LSI Logic, PKM V1.1.01 %PKA0, SCSI Chip is LSI53C1030, Operating mode is LVD Ultra320 SCSI %PKA0, LSI53C1030 firmware version is 1.3.35.69 %PKB0, Copyright (c) 2001 LSI Logic, PKM V1.1.01 %PKB0, SCSI Chip is LSI53C1030, Operating mode is LVD Ultra320 SCSI %PKB0, LSI53C1030 firmware version is 1.3.35.69 **************************************************************** You can install or upgrade the OpenVMS I64 operating system or you can install or upgrade layered products that are included on the OpenVMS I64 operating system CD/DVD. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS I64 Version V8.2-1 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7 WARNING -- The normal OpenVMS startup procedure has not executed. Some commands and utilities will not work as documented. HP does not support PRODUCT INSTALL and other PRODUCT operations in this environment. Enter DCL commands -- Enter "LOGOUT" when done. When you enter "LOGOUT" a message will be displayed saying "Process SA_STARTUP_DCL logged out at