INFO-VAX Wed, 17 Sep 2008 Volume 2008 : Issue 510 Contents: am I the only one hacking VMS on Itanium? Re: am I the only one hacking VMS on Itanium? Re: am I the only one hacking VMS on Itanium? Re: am I the only one hacking VMS on Itanium? Re: am I the only one hacking VMS on Itanium? Annoying feature of SMTP receiver which breaks POP/IMAP Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Is there an updated Ghostscript for VMS? Re: Music for Csaba. [as: HP to axe 24,6000 jobs] Re: Music for Csaba. [as: HP to axe 24,6000 jobs] Re: OpenVMS Architect/Consultant Position Available Re: OT: The end of the world in roughly 3 hours Specials on Radeon 7x cards for VMS integrity and Alpha Re: TCP/IP Printer Queue Problems Re: TCP/IP Printer Queue Problems Re: TCP/IP Printer Queue Problems What is a process' current WSxxxxx quotas ? ---------------------------------------------------------------------- Date: Tue, 16 Sep 2008 18:28:20 GMT From: VAXman- @SendSpamHere.ORG Subject: am I the only one hacking VMS on Itanium? Message-ID: <00A7FB90.EE663929@SendSpamHere.ORG> Just curious. I've been trying to link an execlet and I've encountered not only a Macro compiler issue but now it looks like a linker problem. I can't be the only one with these issues... unless I'm the only hacker still left on planet VMS. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM ... pejorative statements of opinion are entitled to constitutional protection no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside of usenet _must_ include its contents in its entirety including this copyright notice, disclaimer and quotations. ------------------------------ Date: Tue, 16 Sep 2008 11:40:42 -0700 (PDT) From: Bob Gezelter Subject: Re: am I the only one hacking VMS on Itanium? Message-ID: On Sep 16, 1:28 pm, VAXman- @SendSpamHere.ORG wrote: > Just curious. I've been trying to link an execlet and I've encountered > not only a Macro compiler issue but now it looks like a linker problem. > I can't be the only one with these issues... unless I'm the only hacker > still left on planet VMS. > > -- > VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM > > ... pejorative statements of opinion are entitled to constitutional protection > no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) > > Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside > of usenet _must_ include its contents in its entirety including this copyright > notice, disclaimer and quotations. Brian, There are not all that many people who write execlets.For that matter, there are not that many of us who still use MACRO). What kind of issue are you encountering? - Bob Gezelter, http://www.rlgsc.com ------------------------------ Date: Tue, 16 Sep 2008 18:54:00 GMT From: Roger Ivie Subject: Re: am I the only one hacking VMS on Itanium? Message-ID: On 2008-09-16, VAXman- @SendSpamHere.ORG wrote: > Just curious. I've been trying to link an execlet and I've encountered > not only a Macro compiler issue but now it looks like a linker problem. > I can't be the only one with these issues... unless I'm the only hacker > still left on planet VMS. I've done a device driver, but it was in C. And I didn't figure out how to link it; I was busy, so one of my co-workers did. I haven't looked at the linker options file he came up with in detail, but a quick glance looked pretty similar to the Alpha one. I don't have it handy to look at just at the moment. -- roger ivie rivie@ridgenet.net ------------------------------ Date: Tue, 16 Sep 2008 19:55:40 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: am I the only one hacking VMS on Itanium? Message-ID: VAXman- @SendSpamHere.ORG writes: >Just curious. I've been trying to link an execlet and I've encountered >not only a Macro compiler issue but now it looks like a linker problem. >I can't be the only one with these issues... unless I'm the only hacker >still left on planet VMS. I'm doing Macro work on Itanium and we've found odd Macro problems, but the same problems exist on the Alpha macro compiler so I think we're the first to encounter them since the Alpha came out. ------------------------------ Date: Tue, 16 Sep 2008 20:46:59 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: am I the only one hacking VMS on Itanium? Message-ID: <00A7FBA4.4D06B4A6@SendSpamHere.ORG> In article , moroney@world.std.spaamtrap.com (Michael Moroney) writes: >VAXman- @SendSpamHere.ORG writes: > >>Just curious. I've been trying to link an execlet and I've encountered >>not only a Macro compiler issue but now it looks like a linker problem. >>I can't be the only one with these issues... unless I'm the only hacker >>still left on planet VMS. > >I'm doing Macro work on Itanium and we've found odd Macro problems, but >the same problems exist on the Alpha macro compiler so I think we're the >first to encounter them since the Alpha came out. I reported one recently to John Reagan... Here's a simple reproducer: .LIBRARY "SYS$LIBRARY:LIB.MLB" DECLARE_PSECT EXEC$NONPAGED_CODE ABC: .CALL_ENTRY MOVL DATA,R0 RET ;;; DECLARE_PSECT EXEC$NONPAGED_CODE XYZ: .CALL_ENTRY MOVAL DATA,R0 MOVL (R0),R0 RET DECLARE_PSECT EXEC$NONPAGED_DATA DATA: .LONG 1 .END Compile the above with /LIST/MACHINE and look at the PSECT attributes for EXEC$NONPAGED_LINKAGE in the listing. Then, remove the ";;;" com- menting out the second DECLARE_PSECT EXEC$NONPAGED_CODE. Compile with /LIST/MACHINE and look at the EXEC$NONPAGED_LINKAGE PSECT attributes! It's NOT the end of the world as the attributes can be rewritten in a linker option deck. It's just a nuisance. Another is on Itanium. I can't get the linker to resolve a reference to MMG$ALLOC_PFN_MAP_SVA even though it's listed in SYS$BASE_IMAGE.MAP. This is putting a real damper on my progressing forward with a project. This one is NOT a nuisance. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM ... pejorative statements of opinion are entitled to constitutional protection no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside of usenet _must_ include its contents in its entirety including this copyright notice, disclaimer and quotations. ------------------------------ Date: Tue, 16 Sep 2008 22:58:02 -0400 From: JF Mezei Subject: Annoying feature of SMTP receiver which breaks POP/IMAP Message-ID: <48d074d2$0$1568$c3e8da3@news.astraweb.com> The SMTP receiver (or symbiont) has a feature which will insert a line break whenever a line exceeds 255 characters. So, if a header has a line which exceeds 255 characters, The first 255 are printed, then the remainder are printed starting at column 1 on the next line. (and I assume that if that line exceeds 255, it too will be folded into more lines.) The end result is that you have an illformed header. And unfortunatly, both POP and IMAP parse the RFC822 headers and when they encounter an illformed one, they treat it as text and synthetise a vanilla header. For a text message, this isn't the end of the world. But when the message contains attachements, it means that a smart client on some other platform will see the faked vanilla header instead of the real one below and thus will not have a clue that this is a multipart message and no clue what is the boundary between parts is. The only way to fix this is to go into VMS, fire up MAIL or DECW$MAIL, get the actual file name of the message, edit that file to correct the header and then get the client to redoaload the message via IMAP or POP. (via POP, it would be harder since the message is already marked as READ.) Today, I had 5 important messages that I had to manually edit. I realise that because of 1970s limitation of DECnet, messages cannot have lines exceeding 255 characters. I would therefore suggest that the receiver be modified to either: Parse the header with logic that will insert a newline AND a space when it must break lines, and perhaps break them smartly after a white space or a coma instead of blindly breaking them at position 255. This would result in a properly formatted header. Then, once it has encountered a blank line, it can proceed with the normal line folding when it finds long lines. I would suggest that there, it should fold only at the last encountered whitespace before reaching 255. Alternatively, a setting in SMTP.CONF to not fold lines at all which could be used for shops that no longer transfer mail via the 1970s DECnet mail interface. ------------------------------ Date: Tue, 16 Sep 2008 14:26:40 -0700 From: Malcolm Dunnett Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: <48d0248f$1@flight> David J Dachtera wrote: >> How about fixing the failing line in the .mak file? > > Are you volunteering? Well I took a stab at it. There were several issues - The definition for the C compiler didn't seem to be passing through to the included .mak files. - There are lots of instances of "$$" in the openvms.mak file that ought to be a single "$". - the make file doesn't appear to automatically run the program to generate arch.h, but I figured out how to do this by hand. - some compile commands are missing required "/include=" directives (I'll look into proper fixes for these issues later, right now I just want to see if it's feasible to build this version and have it run, so I've just hacked my way through these issues by editing the included files - though a proper solution would concentrate all the customizations in the openvms.mak file of course) I've been stumbling my way through all of this and have gotten a goodly way through the build, but now I'm stuck on compiling one of the modules with the following error: CC/NOWARN/NODEBUG/OPTIMIZE/DECC/PREFIX=ALL/NESTED_INCLUDE=PRIMARY/NAMES=SHORTENED /INCLUDE=([.obj] ,[.src]) /OBJECT=[.obj]gdevx.obj [.src]gdevx.c #include /*Protect against compiling with different switches*/ .^ %CC-F-NOINCLFILEF, Cannot find file specified in #include directive. at line number 62 in file SYS$COMMON:[DECW$INCLUDE]XLIB.H;1 Note the error is in a standard VMS header module, not a file from the ghostscript distro. I think the problem is that I don't understand C include directives properly. What is the significance of the "<" vs quotation marks on the include? What is the significance of the X11 prefix? The file apienvset.h exists in the DECW$INCLUDE search path, but it doesn't get found, I'm assuming this has something to do with the angle brackets or the X11 prefix. (As you can tell, I'm not a C programmer). Any help appreciated. ------------------------------ Date: Tue, 16 Sep 2008 16:43:15 -0500 (CDT) From: sms@antinode.info (Steven M. Schweda) Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: <08091616431568_20202860@antinode.info> From: Malcolm Dunnett > #include /*Protect against compiling with different > switches*/ > .^ > %CC-F-NOINCLFILEF, Cannot find file specified in > #include directive. > at line number 62 in file SYS$COMMON:[DECW$INCLUDE]XLIB.H;1 > > Note the error is in a standard VMS header module, not a file from the > ghostscript distro. define X11 DECW$INCLUDE: > I think the problem is that I don't understand C include directives > properly. What is the significance of the "<" vs quotation marks on the > include? HELP CC /INCLUDE_DIRECTORY Drugs may help. > What is the significance of the X11 prefix? It's a directory in UNIX-land. A logical name workes in VMS. > (As you can tell, I'm not a C programmer). It's getting more obvious. Isn't this all very educational? ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ Date: Tue, 16 Sep 2008 15:12:13 -0700 (PDT) From: johnwallace4@yahoo.co.uk Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: On Sep 16, 10:26 pm, Malcolm Dunnett wrote: > David J Dachtera wrote: > >> How about fixing the failing line in the .mak file? > > > Are you volunteering? > > Well I took a stab at it. There were several issues > > - The definition for the C compiler didn't seem to be passing through > to the included .mak files. > > - There are lots of instances of "$$" in the openvms.mak file that > ought to be a single "$". > > - the make file doesn't appear to automatically run the program to > generate arch.h, but I figured out how to do this by hand. > > - some compile commands are missing required "/include=" directives > > (I'll look into proper fixes for these issues later, right now I just > want to see if it's feasible to build this version and have it run, so > I've just hacked my way through these issues by editing the included > files - though a proper solution would concentrate all the > customizations in the openvms.mak file of course) > > I've been stumbling my way through all of this and have gotten > a goodly way through the build, but now I'm stuck on compiling one of > the modules with the following error: > > CC/NOWARN/NODEBUG/OPTIMIZE/DECC/PREFIX=ALL/NESTED_INCLUDE=PRIMARY/NAMES=SHORTENED > /INCLUDE=([.obj] ,[.src]) /OBJECT=[.obj]gdevx.obj [.src]gdevx.c > > #include /*Protect against compiling with different > switches*/ > .^ > %CC-F-NOINCLFILEF, Cannot find file specified in > #include directive. > at line number 62 in file SYS$COMMON:[DECW$INCLUDE]XLIB.H;1 > > Note the error is in a standard VMS header module, not a file from the > ghostscript distro. > > I think the problem is that I don't understand C include directives > properly. What is the significance of the "<" vs quotation marks on the > include? What is the significance of the X11 prefix? > > The file apienvset.h exists in the DECW$INCLUDE search path, but it > doesn't get found, I'm assuming this has something to do with the angle > brackets or the X11 prefix. > > (As you can tell, I'm not a C programmer). > > Any help appreciated. The traditional interpretations are something like: #include "yourfile.h" /* "file": look for file in the user's own directory rather than the system-wide includes */ #include /* : means look in the system-wide standard places, rather than the user's own directory */ #include /* look in the standard places, in the (sub)directory called sys, for a file called time.h */ So given the source line "#include " and the error message reference to "SYS$COMMON:[DECW$INCLUDE]XLIB.H;1" I conclude that, whilst compiling XLIB.H (which probably comes with VMS), the compiler was told to look for which means it may well have been looking for "SYS$COMMON:[DECW$INCLUDE.X11]APIENVSET.H", but could not find it. Does that seem likely? If the file exists in the right place, is it readable, and other such routine queries, *may* also be relevant ------------------------------ Date: Tue, 16 Sep 2008 20:04:17 -0400 From: "Richard B. Gilbert" Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: <_KWdnTDyk8_71E3VnZ2dnUVZ_h6dnZ2d@comcast.com> Malcolm Dunnett wrote: > David J Dachtera wrote: >>> How about fixing the failing line in the .mak file? >> >> Are you volunteering? > > Well I took a stab at it. There were several issues > > - The definition for the C compiler didn't seem to be passing through > to the included .mak files. > > - There are lots of instances of "$$" in the openvms.mak file that > ought to be a single "$". > > - the make file doesn't appear to automatically run the program to > generate arch.h, but I figured out how to do this by hand. > > - some compile commands are missing required "/include=" directives > > (I'll look into proper fixes for these issues later, right now I just > want to see if it's feasible to build this version and have it run, so > I've just hacked my way through these issues by editing the included > files - though a proper solution would concentrate all the > customizations in the openvms.mak file of course) > > I've been stumbling my way through all of this and have gotten > a goodly way through the build, but now I'm stuck on compiling one of > the modules with the following error: > > CC/NOWARN/NODEBUG/OPTIMIZE/DECC/PREFIX=ALL/NESTED_INCLUDE=PRIMARY/NAMES=SHORTENED > /INCLUDE=([.obj] ,[.src]) /OBJECT=[.obj]gdevx.obj [.src]gdevx.c > > #include /*Protect against compiling with different > switches*/ > .^ > %CC-F-NOINCLFILEF, Cannot find file specified in > #include directive. > at line number 62 in file SYS$COMMON:[DECW$INCLUDE]XLIB.H;1 > > Note the error is in a standard VMS header module, not a file from the > ghostscript distro. > > I think the problem is that I don't understand C include directives > properly. What is the significance of the "<" vs quotation marks on the > include? What is the significance of the X11 prefix? > My memory grows DIMM but I believe that include "mumble" takes mumble from the current directory and looks elsewhere, maybe in what would be /include in Unix. Sorry to be so vague but It has been more than a few years since I last played with this stuff. ------------------------------ Date: Tue, 16 Sep 2008 18:04:35 -0700 From: Malcolm Dunnett Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: <48d057a3$1@flight> Steven M. Schweda wrote: > > define X11 DECW$INCLUDE: > Yup. I missed one of the "double $" bugs in openvms.mak, it was defining X11 as DECW$$INCLUDE:, which didn't work terribly well. >> (As you can tell, I'm not a C programmer). > > It's getting more obvious. Isn't this all very educational? Terribly (more than I wanted to know). Anyway, I've built the executable and "gs -h" works (kind of a "hello world" test). I'll do some more serious testing tomorrow. ------------------------------ Date: Tue, 16 Sep 2008 19:27:26 -0700 From: "Jeffrey H. Coffield" Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: Malcolm Dunnett wrote: > Steven M. Schweda wrote: >> >> define X11 DECW$INCLUDE: >> > > Yup. I missed one of the "double $" bugs in openvms.mak, it was > defining X11 as DECW$$INCLUDE:, which didn't work terribly well. > >>> (As you can tell, I'm not a C programmer). >> >> It's getting more obvious. Isn't this all very educational? > > Terribly (more than I wanted to know). > > Anyway, I've built the executable and "gs -h" works (kind of a "hello > world" test). I'll do some more serious testing tomorrow. I use Ghostscript a lot on OpenVMS and got several earlier versions to compile so I feel your pain. Please post the fixes when you are done. I can provide some serious testing on a new version fairly quickly. Jeff Coffield www.digitalsynergyinc.com ------------------------------ Date: Tue, 16 Sep 2008 21:32:03 -0500 (CDT) From: sms@antinode.info (Steven M. Schweda) Subject: Re: Is there an updated Ghostscript for VMS? Message-ID: <08091621320357_20202860@antinode.info> From: Malcolm Dunnett > - There are lots of instances of "$$" in the openvms.mak file that > ought to be a single "$". Re-reading this, did you notice that there's an "openvms.mak" and an "openvms.mmk"? According to the doc/Make.htm#VMS_build (HTML) doc: [...] As of Ghostscript version 5.0 you can use GNU make -- with the file OPENVMS.MAK [...] [...] Building Ghostscript with MMK or MMS uses the file OPENVMS.MMK [...] Using the right description file might help some. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info 382 South Warwick Street (+1) 651-699-9818 Saint Paul MN 55105-2547 ------------------------------ Date: Tue, 16 Sep 2008 11:54:25 -0700 From: Marty Kuhrt Subject: Re: Music for Csaba. [as: HP to axe 24,6000 jobs] Message-ID: Main, Kerry wrote: >> -----Original Message----- >> From: Phillip Helbig---remove CLOTHES to reply >> [mailto:helbig@astro.multiCLOTHESvax.de] >> Sent: Tuesday, September 16, 2008 8:47 AM >> To: Info-VAX@Mvb.Saic.Com >> Subject: Re: Music for Csaba. [as: HP to axe 24,6000 jobs] >> >> In article <48cfa78c$1@news.comindico.com.au>, Phaeton >> writes: >> >>> Thanks, Brian. I think I've already visited that site, a few >> times. >>> Currently I am downloading old stuff from the net, mainly rare >> European >>> 70s prog ( being an older guy as most VMS people tend to be :-) >> ) >> >> At the store "Saturn" a few days ago (where one can scan in the barcode >> of a CD and here about 20 seconds of each song---this system runs on >> VMS, by the way, so this post is on-topic), I noticed that Nektar have >> a >> new album. How's that for rare 70s prog? :-) Also speaking of 70s >> prog (but not rare), Richard Wright has died. > > Saturn is not only a OpenVMS Integrity Customer, but also a great > testimonial: > > http://tinyurl.com/2ne7cu > (PDF + video testimonial) > > Making great music .. > > :-) > > Regards > > Kerry Main > Senior Consultant > HP Services Canada > Voice: 613-254-8911 > Fax: 613-591-4477 > kerryDOTmainAThpDOTcom > (remove the DOT's and AT) > > OpenVMS - the secure, multi-site OS that just works. Wonder what they use to serve the music snippets? Is it a streaming server, or do the listening stations select and download the various MP3 files? I'd like to use my home cluster as a media server. What stuff do you think I'd need to download/port to make it work? ------------------------------ Date: Tue, 16 Sep 2008 20:33:50 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Music for Csaba. [as: HP to axe 24,6000 jobs] Message-ID: <00A7FBA2.76C5B71F@SendSpamHere.ORG> In article , Marty Kuhrt writes: >{...snip...} >Wonder what they use to serve the music snippets? Is it a streaming >server, or do the listening stations select and download the various MP3 > files? > >I'd like to use my home cluster as a media server. What stuff do you >think I'd need to download/port to make it work? When I get some time, I'm hell bent on getting Shoutcast ported to VMS. IDJC would be the next item. Now, if only there was time. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM ... pejorative statements of opinion are entitled to constitutional protection no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside of usenet _must_ include its contents in its entirety including this copyright notice, disclaimer and quotations. ------------------------------ Date: Tue, 16 Sep 2008 12:33:32 -0700 (PDT) From: johnwallace4@yahoo.co.uk Subject: Re: OpenVMS Architect/Consultant Position Available Message-ID: On Sep 16, 6:54 pm, s...@obanion.us wrote: > I recall that the AS2100 was tricky to write IO drivers for because > the system had several bus addressing modes to map the IO address > space in the longword space of the CPU. So if you wanted to get to a > byte addressed register on a card you would change the mapping so that > byte addresses on the bus were found on longword address from the CPUs > point of view. And I think specify a base address as well, since the > 32 (or was it 64?) bit address of the bus as seen as bytes was larger > that the physical address space of the EV4. > > Once the word and byte operands were added (EV5?), and IO boards > understood longword only register spacing, this problem went away, > leaving the 2100 and it's relatives (seems like the 2000, 1200, and > one other...) with unique IO driver requirements. > > They must have a lot of 2100s to make this worthwhile... > > Sean > > On Sep 16, 5:16 am, VAXman- @SendSpamHere.ORG wrote: > > > In article , hel...@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: > > > >In article > > ><83d2835f-dda1-44cb-b36a-166393c7f...@25g2000hsx.googlegroups.com>, > > >FrankS writes: > > > >> That's interesting. It says this will be a "migration from the legacy > > >> systems" and onto an AlphaServer 2100. > > > >> I never thought I'd see an AS2100 considered non-legacy again. > > > >Is this the EV4 or EV45 AS2100? > > > I've fired off an email to the POC for more information. > > > -- > > VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM > > > ... pejorative statements of opinion are entitled to constitutional protection > > no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC) > > > Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside > > of usenet _must_ include its contents in its entirety including this copyright > > notice, disclaimer and quotations. There were 2100s with EV5/21164 too. They were certainly sold with EV5 (eg see SOC [1]) and (iirc) there might even have been field upgrades from the EV4/21064 to EV5/21164. Didn't Raytheon do a repackaged 2100 (their Model 940), with flight-compatible stuff like conduction-cooled boards and what have you? The software and most of the hardware wouldn't care about whose badge was on the system, but it could well be important to the flight and certification people. Wrt the byte/word thing: It's not really the "IO boards" themselves that are the issue - they're mostly relatively standard PCI stuff in most 2100s and similar-era systems, maybe with EISA too. Maybe you mean the companion IO board in the 2100 which sat between CPU and main IO buses, a board whose name I forget. The real challenge in Alphas of that era is in the CPU->PCI chipset and (as you already mentioned) primarily the lack of true byte/word operands in earlier Alphas, which led to "sparse mode" addressing in PCI space (deep joy). Fixed in a historic major release, fortunately. But by then the damage had been done. Anyway, from the advert: "The US Air Force is developing a Radar software program for a line of aircraft in OpenVMS using Alpha 2100. They will be doing development as well as migration from the legacy systems. They will be doing driver design of radar driver software. This is in a VME/PCI environment." Three things stand out: 0) USAF 1) these systems will be flying (and certified for flying), and therefore there will likely be lots of cost involved if anything significant changes in the hardware (and presumably software). That's probably a manageable risk given the right approach. There's probably lots of cost already, what's a little extra anyway. 2) There are PCI<>VME adaptors in this picture. That's a different set of risks, still manageable, but much care will be needed, not least because of aforementioned byte/word addressing issues, which become particularly interesting on the PCI/VME adaptors, which aren't exactly common, and may even require consideration of matters like bigendian vs littleendian. So it's likely not a "huge" number of 2100s, but could easily be a huge cost to change to anything significantly different either in software or in hardware. Interesting opportunity for someone. Hopefully rewarding too. [1] http://h18000.www1.hp.com/products/quickspecs/SOC/QB002BPF.PDF ------------------------------ Date: Tue, 16 Sep 2008 18:42:30 -0700 (PDT) From: AEF Subject: Re: OT: The end of the world in roughly 3 hours Message-ID: On Sep 12, 7:34=A0am, "Ken Robinson" wrote: > See this site: > > http://hasthelargehadroncolliderdestroyedtheworldyet.com/ > > Ken Actually, we don't need the LHC to end the world; Wall St. is doing a pretty good job of it right now! And if things continue to get worse, many will probably prefer the LHC to end the world to save them the trouble of banging their PC's at the windows so that they can break them so that they can jump out! AEF (And now, something even more off topic!) Two-level nested parenthetical remarks: Superman! And who (disguised as Clark Kent [a reporter for a great metropolitan newspaper]) fights a never-ending battle for truth, justice, and the American Way. Da - da -da-da-daaaaaah (repeat], etc. ------------------------------ Date: Tue, 16 Sep 2008 14:50:55 -0400 From: "David Turner, islandco.com" Subject: Specials on Radeon 7x cards for VMS integrity and Alpha Message-ID: We sell Radeon 7x Graphics cards for Integrity and Alpha VMS systems Only $179 including driver software Regards -- David B Turner ============================================= Island Computers US Corp PO Box 86 Tybee GA 31328 Toll Free: 1-877 636 4332 x201, Mobile x251 Email: dturner@islandco.com International & Local: (001)- 404-806-7749 Fax: 912 786 8505 Web: www.islandco.com ============================================= ------------------------------ Date: Tue, 16 Sep 2008 11:54:38 -0700 (PDT) From: Bob Gezelter Subject: Re: TCP/IP Printer Queue Problems Message-ID: <8f58007f-3443-4430-9975-6921e94a4ea1@k37g2000hsf.googlegroups.com> On Sep 16, 8:56 am, "Carmine Castiglia" wrote: > File this under "Life's Little Annoyances" > > I am running DIGITAL TCP/IP Services for OpenVMS Alpha Version V4.2 on a > AlphaServer 1200 5/533 4MB running OpenVMS V7.1-1H2 with several print > queues configured and working without trouble. > > On the rare occasions when I need to add a print server queue I almost > invaribly run into one odd problem or another. At the moment, I would like > to configure a print server queue to enable printing to a Brother Intellifax > 4750e > (http://welcome.solutions.brother.com/BSC/public/files/dlf/doc002093/N...) > which is already on the network and accessible to Windows PCs using LPR > Protocol and "BINARY_P1" as the queue name. > > I have added an entry to the UCX Hosts database as follows: > > xxx.xxx.xxx.xxx ACCT$FAX, acct$fax > > SYS$STARTUP:UCX$LPD_STARTUP.COM contains the following: > > $ init/queue/start- > /owner=[1,4]- > /retain=error- > /device=server- > /process=ucx$lpd_smb- > /protection=(s:e,g:r,w:w,o:d) ACCT$FAX - > /library=emsdevctl_hplj - > /form=normal/schedule=nosize - > /default=(nofeed,form=normal) > > and UCX$PRINTCAP.DAT contains: > > ACCT$FAX|acct$fax:\ > :lf=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX.LOG:\ > :lp=ACCT$FAX:\ > :rm=acct$fax:\ > :rp=TEXT_P1:\ > :sd=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX:\ > :cr: > > The queue initializes and starts without problem and sending a print command > to the queue gives every indication that it is working normally: > > $ pri/que=acct$fax login.com > Job LOGIN (queue ACCT$FAX, entry 859) started on ACCT$FAX > $ > > Job LOGIN (queue ACCT$FAX, entry 859) completed > $ > > But, the printer shows no signs of life and nothing prints. > > The IP address in the Host entry is correct, UCX$LPD_SPOOL:ACCT$FAX.DIR > exists and has the same Protection as similar folders for working queues > (System:RWE, Owner:RWE, Group:RE, World:RWED). > > What am I missing here?? Carmine, Bob Koehler's comment is well taken. Precisely what type of data are the other systems sending to this printer? When troubleshooting these problems, I have always found a LAN analyzer (e.g. WireShark, http://www.wireshark.org ) to be invaluable. Much of the uncertainty can be resolved by looking at what is actually going bnack and forth on the LAN. For a problem such as this, all one needs is Windows/Linux box (boneyard refugees acceptable), and a LAN hub. Everything will then be visible. One can also use TCPDUMP from the host side to identify what is going back and forth. - Bob Gezelter, http://www.rlgsc.com ------------------------------ Date: Tue, 16 Sep 2008 15:15:03 -0400 From: "Richard B. Gilbert" Subject: Re: TCP/IP Printer Queue Problems Message-ID: Carmine Castiglia wrote: > File this under "Life's Little Annoyances" > > I am running DIGITAL TCP/IP Services for OpenVMS Alpha Version V4.2 on a > AlphaServer 1200 5/533 4MB running OpenVMS V7.1-1H2 with several print > queues configured and working without trouble. > > On the rare occasions when I need to add a print server queue I almost > invaribly run into one odd problem or another. At the moment, I would like > to configure a print server queue to enable printing to a Brother Intellifax > 4750e > (http://welcome.solutions.brother.com/BSC/public/files/dlf/doc002093/NC8100HUK_A.pdf) > which is already on the network and accessible to Windows PCs using LPR > Protocol and "BINARY_P1" as the queue name. > > I have added an entry to the UCX Hosts database as follows: > > xxx.xxx.xxx.xxx ACCT$FAX, acct$fax > > SYS$STARTUP:UCX$LPD_STARTUP.COM contains the following: > > $ init/queue/start- > /owner=[1,4]- > /retain=error- > /device=server- > /process=ucx$lpd_smb- > /protection=(s:e,g:r,w:w,o:d) ACCT$FAX - > /library=emsdevctl_hplj - > /form=normal/schedule=nosize - > /default=(nofeed,form=normal) > > and UCX$PRINTCAP.DAT contains: > > ACCT$FAX|acct$fax:\ > :lf=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX.LOG:\ > :lp=ACCT$FAX:\ > :rm=acct$fax:\ > :rp=TEXT_P1:\ > :sd=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX:\ > :cr: > > The queue initializes and starts without problem and sending a print command > to the queue gives every indication that it is working normally: > > $ pri/que=acct$fax login.com > Job LOGIN (queue ACCT$FAX, entry 859) started on ACCT$FAX > $ > > Job LOGIN (queue ACCT$FAX, entry 859) completed > $ > > But, the printer shows no signs of life and nothing prints. > > The IP address in the Host entry is correct, UCX$LPD_SPOOL:ACCT$FAX.DIR > exists and has the same Protection as similar folders for working queues > (System:RWE, Owner:RWE, Group:RE, World:RWED). > > What am I missing here?? > > One very simple test you can make: Telnet to the printer; telnet 192.168.1.4 and specify whatever port the printer uses. Sorry but it's been many years since I last needed to do this and the details like syntax and port number have slipped away. Once you have the telnet connection, type "Print meNow is the time for all good men. . . . By doing this, you have bypassed a lot of higher layers and gotten right down to where the rubber meets the road. If the printer prints and feeds the form you have established that the computer can talk to the printer and that the printer is capable of printing. Then and only then, you can do battle with the software and be reasonably sure that you are fighting the right battle. If you don't know what port(s) the printer uses, run a "portscan" against it. Be certain that you have the correct IP address for the printer; ISPs take a VERY dim view of people who run portscans over their network!!!! I believe I still have a copy of a program that will do a portscan. I've used it just once to figure out what port to use on a copier/printer combination. ------------------------------ Date: Tue, 16 Sep 2008 22:02:25 -0400 From: JF Mezei Subject: Re: TCP/IP Printer Queue Problems Message-ID: <48d065d7$0$1550$c3e8da3@news.astraweb.com> >> I have added an entry to the UCX Hosts database as follows: >> >> xxx.xxx.xxx.xxx ACCT$FAX, acct$fax >> >> SYS$STARTUP:UCX$LPD_STARTUP.COM contains the following: >> >> $ init/queue/start- >> /owner=[1,4]- >> /retain=error- >> /device=server- >> /process=ucx$lpd_smb- >> /protection=(s:e,g:r,w:w,o:d) ACCT$FAX - >> /library=emsdevctl_hplj - >> /form=normal/schedule=nosize - >> /default=(nofeed,form=normal) >> >> and UCX$PRINTCAP.DAT contains: >> >> ACCT$FAX|acct$fax:\ >> :lf=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX.LOG:\ >> :lp=ACCT$FAX:\ >> :rm=acct$fax:\ >> :rp=TEXT_P1:\ >> :sd=/SYS$SPECIFIC/UCX_LPD/ACCT$FAX:\ >> :cr: I am not sure what works and what doesn't work in this old version of UCX (before 5.0, it was a fairly different and less functional product). If you are totally out of ideas, try to see if having a queue name equal to a host name (or vice versa) might be an issue. DO a SHOW LOGICAL *ACCT$FAX* to see if there might be some conflicts. In the TCPIP> utility (oops, that would be UCX because you are on an old version), does "SHOW HOST" work ? Does it show your ACCT$FAX entry with its correct IP address ? Does "ping ACCT$FAX" work from VMS ? (aka: is there a route setup to reach that host or is that host in the same subnet ?) In TCPIP Sercvices (5.0 and above), the doc says that :cr: is not supported. Not sure if it means that it is ignored, or whether it causes problems. Where did the TEXT_P1 come from ? The doc mentions "TEXT" or "RAW". Do you have the documentation for the UCX circa 4.whatever ? ------------------------------ Date: Wed, 17 Sep 2008 01:38:42 -0400 From: JF Mezei Subject: What is a process' current WSxxxxx quotas ? Message-ID: <48d09a6c$0$12392$c3e8da3@news.astraweb.com> Is it just me in my ever-so-slightly-different universe, or is there no way to obtain a process' current WSquota, WSextent etc values with SHOW PROCESS ? SHOW PROC/CONT will show its current use for the working set, but not its quota. SHOW PROC/QUOTA doesn't show the WSxxxx values at all. I have a BACKUP/IMAGE that appears to work, but only uses up 1330 pages (alpha) of workint set. (disk to disk backup). I would like to know what the authorized WSEXTENT is for that job. Also, if there is only a very tiny page file, does that limit the WSEXTENT that is given to a job ? (even if there is plenty (relatively) of free memory ? I have the WSEXTENT set to 90000 pages for that account. And I seem to recall BACKUP liking to use about 30k pages (on vax), so I am surprise it is using so few pages to do a disk-to-disk/image backup. ------------------------------ End of INFO-VAX 2008.510 ************************