INFO-VAX Mon, 02 Apr 2007 Volume 2007 : Issue 184 Contents: alpha still viable, we were lied to, Microsoft let down users and shareholders! C compiler and include libraries Re: C compiler and include libraries D8: Keyboard controller test failed on Alpha Station 400 Re: How to analyze disk error Re: HP expands OpenVMS marketing and development Re: HP expands OpenVMS marketing and development Re: HP expands OpenVMS marketing and development HSZ question from RCM data collector Re: Keyboard controller test failed on Alpha Station 400 Re: OT: our geniuses on cov do not understand the constitution Re: Purveyor and Auth DLL Re: Purveyor and Auth DLL Re: Purveyor and Auth DLL Re: Purveyor and Auth DLL Re: Purveyor and Auth DLL Re: Purveyor and Auth DLL Re: Switching off MULTITHREAD Re: Switching off MULTITHREAD Re: Switching off MULTITHREAD Re: TCPIP$SMTP_MIME_HACK ---------------------------------------------------------------------- Date: 2 Apr 2007 07:08:38 -0700 From: genius@marblecliff.com Subject: alpha still viable, we were lied to, Microsoft let down users and shareholders! Message-ID: <1175522918.176560.179180@p77g2000hsh.googlegroups.com> http://www.digitimes.com/news/a20060123PR200.html this article shows that Bill Gates let down all windows users as alpha could have made NT spyware proof ... that EV8 and EV9 could still be viable leaders ... even EV7 still leads in some apps ... that is why compaq killed the worksattion base, to get rid of alpha sales ... to sum it up ... MICROSOFT AND COMPAQ LET ITS USERS AND STOCKHOLDERS DOWN BIG TIME ALL FOR PROBABLY MONEY STUCK IN THERE POCKETS TO DO SO ... and HP is continuing the trend ... notice China has been given alot of the technolgy ... bet they are using it right now to take over as the top superpower ... ------------------------------ Date: Mon, 02 Apr 2007 04:04:54 -0400 From: JF Mezei Subject: C compiler and include libraries Message-ID: I have, through various tests, found the following command $ cc/unsigned scan+sys$library:SYS$LIB_C.TLB/library to work, It compiles SCAN.C and makes available the modules in SYS$LIB_C.TLB in ADDITION to the standard libraries. I tryied toying with the various logicals that are discussed briefly in the books but to no avail. If I got it to work to include the abole library, it would then not find any module in the standard libraries. Obviusly, I am doing something wrong. And the manuals aren't so clear on how to achieve what I need to achieve. (I am not adding a directory to the searchlist, I am adding a .TLB). What is the correct incantation of the DEFINE for which DECC logical to have the above library added to the list of libraries searched by DECC dor this compile so that I wouldn't have to type this horrible command line every time ? (This made me realise the last time I did that was with VAXC a century ago.) ------------------------------ Date: Mon, 02 Apr 2007 04:24:45 -0400 From: JF Mezei Subject: Re: C compiler and include libraries Message-ID: <93229$4610bde8$cef8887a$11709@TEKSAVVY.COM> Joseph Huber wrote: > I'm not entirely sure if it is the only or preferred way, but a logical > defined as > (LNM$PROCESS_TABLE) > "DECC$TEXT_LIBRARY" = "SYS$LIBRARY:SYS$LIB_C.TLB" > > does it for me. many thanks. Will have to look up the documentation to see if this is documented and if so, why I didn't see it. It works ! Great stuff ! ------------------------------ Date: 2 Apr 2007 08:23:20 -0700 From: "tadamsmar" Subject: D8: Keyboard controller test failed on Alpha Station 400 Message-ID: <1175527400.740057.18080@n76g2000hsh.googlegroups.com> I am getting this Led indicator on a dead AS400. Is it easy to swap out a keyboard controller on an Alpha Station 400? I have another dead one with a bad motherboard that I could use for parts. ------------------------------ Date: 2 Apr 2007 07:49:42 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: How to analyze disk error Message-ID: In article <1175260217.941914.308690@n76g2000hsh.googlegroups.com>, "tadamsmar" writes: > > I tried ANALYZE/ERROR but it does not seem to be able to do a bit to > text translation. Bit level translation generally requires knowing the internals of the device driver (what data did it actually report), and the hardware manuals. ------------------------------ Date: 2 Apr 2007 08:03:19 -0500 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: HP expands OpenVMS marketing and development Message-ID: In article <973ad$460f7fd0$cef8887a$28214@TEKSAVVY.COM>, JF Mezei writes: >colour It was pretty good up 'till that one. Me thinks American spelling would have come across better. But not bad, all in all. ------------------------------ Date: Mon, 2 Apr 2007 06:59:02 -0600 From: "Michael D. Ober" Subject: Re: HP expands OpenVMS marketing and development Message-ID: <46110c27$0$507$815e3792@news.qwest.net> Well done. Now if HP would only do half of this. Mike Ober. "JF Mezei" wrote in message news:973ad$460f7fd0$cef8887a$28214@TEKSAVVY.COM... > HP Expands OpenVMS marketing and development with strategic initiative > with Martha Steward Living. > Palo Alto, April 1, 2007 > > HP today unveiled a strategic marketing alliance with Martha Stewart > Living which will redevelop the OpenVMS product and expand its > marketing breath and market penetration. > > "VMS is like a home that hasn't been maintained or decorated for 20 > years, and I intend to give it a complete makeover" said Mrs Stewart > during the announcement. > > As first step, Mrs Stewart intends to strip the "Open" from the name. > "It is like idiots who paint a mahogany desk orange. By stripping off > the ugly and confusing "Open", we'll restore VMS to its original high > quality and value." said Mrs Stewart. > > An extensive survey of the operating system and layered products has > revealed an extremely strong core with modern services and market > leading clustering. "Its is something with solid foundations and core > services that is worth building on" was the overwhelming conclusion. > > One of the greatest payback will be the sprucing of the windows. By > giving the window and widget decorations a more modern look, this will > make it much easier to make new customers feel at home and attract new > applications to VMS. Mrs Stewart will evaluate, for HP, whether to hire > a new DECwindows manager, or whether the existing one should be improved. > > Mrs Stewart will also transfer technology that will allow VMS desktops > to have more user friendly environment customisation with Martha Stewart > Living patented colour selection widgets for background and window > decocations, as well as more elaborate patterns. In exchange, VMS > engineers will add colour capability to DCL to make females more at home > with VMS. SET COLOUR/FEMALE will result in DCL making all prompts in > pink, and entered text in taupe. "VMS lacks female customers, it is a > greatly untapped market potential and only Martha Stewart can provide > colour selection swatches that will leverage the market's full potential. > > Massive Co-Marketing Initiative. > > MSL and HP will embark on a massive co-marketing initiative with > co-branding and marketing of each other's products. While Martha Stewart > will feature VMS's makeover on her TV programmes and showcase how its > new modern look will fit better in any home at an affordable price, HP > will include coupons for a reduction on Martha Stewart branded pillows > with every purchase of an HP Ink cartridge. MSL has already committed > to purchasing large VMS systems for their own IT infrastructure. It is > felt that Oprah will also want such systems once she find out her > competitor has them and this will create a huge bandwagon of rich women > moving their IT infrastructure to VMS. > > According to a fourth quarter 2006 report by the market research firm > IDC, HP is the overall worldwide leader in unit shipments in the VMS > server businesses. > > > Additional information is available in an online press kit at > http://www.hpee.com/go/marthadoeshurd > > About HP > > HP focuses on filling proprietary ink cartridges for all of its > customers - from individual consumers to the largest businesses. With a > portfolio that spans black, magenta, cyan, yellow, red, green and blue , > HP is the largest manufacturer of HP ink cartridges, with revenue totaling > $94.1 billion for the four fiscal quarters ended Jan. 31, 2007. More > information about HP (NYSE: HPQ) is available at http://www.hpee.com. > > > > This news release contains diagonal-looking statements that involve > risks, uncertainties and the assumed existance of a paralel universe. If > such risks or uncertainties materialize or such assumptions prove > correct, the results of HP and its consolidated subsidiaries will differ > randomly from those expressed or implied by such upwards-looking > statements and assumptions. All statements including statements of > historical fact are statements that should be deemed to be fictional > statements , including but not limited to statements of the plans of > cosmetic operations for management ; any statements concerning expected > breast sagging, performance relating to the size of the business units; > anticipated overcooking of rice and associated erectional difficulties; > any statements of expectation or religious belief; and any statements of > assumptions underlying any of the foregoing. Risks, uncertainties and > assumptions include the achievement of pregnancy tests and other risks > that are described from time to time in HP's Securities and Exchange > Commission reports, including but not limited to the risks described in > HP's Quarterly Report on Form 10-Q for marital affairs ended Jan. 31, > 2007. HP assumes no obligation nor responsibility for these april fools > statements. ------------------------------ Date: 2 Apr 2007 08:55:49 -0700 From: "bclaremont" Subject: Re: HP expands OpenVMS marketing and development Message-ID: <1175529349.260851.86510@b75g2000hsg.googlegroups.com> Very Good! ------------------------------ Date: 2 Apr 2007 03:08:34 -0700 From: "Big John" Subject: HSZ question from RCM data collector Message-ID: <1175508514.089997.238660@e65g2000hsc.googlegroups.com> Hi. After a full health-check of a customer system, the RCM data collector has thrown up some odd messages about the HSZ. The system is.. AlphaServer ES40 Operating System VMS V7.3-2 Console Version V7.1-1 Palcode Version 1.98-4 Controller: HSZ80 ZG94810319 Software V83Z-1, Hardware E04 SCSI_VERSION = SCSI-2 Here is the extract from the HSZ section of the RCM data collector output. MW2BOTFR> SHOW ASSOCIATIONS FULL Error 9060: Container or unit ASSOCIATIONS does not exist MW2BOTFR> SHOW CONCATSETS FULL Error 9060: Container or unit CONCATSETS does not exist MW2BOTFR> SHOW CONNECTIONS FULL Error 9060: Container or unit CONNECTIONS does not exist MW2BOTFR> SHOW REMOTE_COPY FULL Error 9060: Container or unit REMOTE_COPY does not exist According to the VMS tech journal , - http://h71000.www7.hp.com/openvms/journal/v4/rcm_for_openvms.html - these are correct commands, so I am concerned about why they are throwing up these messages. Any HSZ wizards out there with any ideas? TIA John. ------------------------------ Date: Mon, 02 Apr 2007 16:22:13 GMT From: "FredK" Subject: Re: Keyboard controller test failed on Alpha Station 400 Message-ID: "tadamsmar" wrote in message news:1175527400.740057.18080@n76g2000hsh.googlegroups.com... >I am getting this Led indicator on a dead AS400. > > Is it easy to swap out a keyboard controller on an Alpha Station 400? > I have another dead one with a bad motherboard that I could use for > parts. > The KB controller is part of one of the bridge chips - the replacement is a new motherboard. ------------------------------ Date: 2 Apr 2007 09:47:51 -0700 From: davidc@montagar.com Subject: Re: OT: our geniuses on cov do not understand the constitution Message-ID: <1175532471.269549.187690@e65g2000hsc.googlegroups.com> On Apr 1, 4:50 am, davi...@alpha2.mdx.ac.uk wrote: > Although the Alpha and Integritysourcecodeis supposed to be common that for > VAX isn't the same. However you might regard the VAXsourcecodeas being > common in Spirit to the others. There is a lot of the code that is the same or substantially similar. At release, VAX and Alpha were "bug for bug" compatible for a reason. They are more common than just spirit. ------------------------------ Date: Mon, 2 Apr 2007 08:26:33 -0400 From: "Hal Kuff" Subject: Re: Purveyor and Auth DLL Message-ID: <1E6Qh.45629$s8.6230@newsfe21.lga> Hi, thanks.... we have someone here that has been having a tough go of it... I will verify they are following your hints wrote in message news:1175516265.953692.128330@b75g2000hsg.googlegroups.com... > On Apr 2, 7:46 am, "Hal Kuff" wrote: >> Hi, >> >> Can anyone volunteer about 10 mins on the phone to go over how to >> link >> in the dll so we can use the authenticate model? If so can you send a >> contact number to kuff at tessco dot com , or perhaps sumamrize it here >> would be great as well. I hear Mr. Maniotes used to be the community guru >> but we do not have current info on him. >> >> --HK > > acutally, it is quite easy ... > > 1. compile the file_auth.c program (c 6.0 or higher) using > the file_auth.com dcl routine > > 2. place the .DLL compiled result in your scripts directory > > 3. next run the purveyor RSM management web interface > and goto to the realm that you want to authenticate > and check the box "Use authentication DLL" and fill the > the name box with the directory and name of your scripts > directory you entered in the virtual servers setup screen ... > > 4. sit back and relax because vms authentication takes > over using sysuaf ... > > we actually took the supplied DLL and tweaked it to > work with the HTPASSWORD module from apache, > so you can modify file_auth easily to work with other > file formats ... > ------------------------------ Date: 2 Apr 2007 05:26:44 -0700 From: genius@marblecliff.com Subject: Re: Purveyor and Auth DLL Message-ID: <1175516804.528947.257380@p77g2000hsh.googlegroups.com> On Apr 2, 8:17 am, gen...@marblecliff.com wrote: > On Apr 2, 7:46 am, "Hal Kuff" wrote: > > > Hi, > > > Can anyone volunteer about 10 mins on the phone to go over how to link > > in the dll so we can use the authenticate model? If so can you send a > > contact number to kuff at tessco dot com , or perhaps sumamrize it here > > would be great as well. I hear Mr. Maniotes used to be the community guru > > but we do not have current info on him. > > > --HK > > acutally, it is quite easy ... > > 1. compile the file_auth.c program (c 6.0 or higher) using > the file_auth.com dcl routine > > 2. place the .DLL compiled result in your scripts directory > > 3. next run the purveyor RSM management web interface > and goto to the realm that you want to authenticate > and check the box "Use authentication DLL" and fill the > the name box with the directory and name of your scripts > directory you entered in the virtual servers setup screen ... > > 4. sit back and relax because vms authentication takes > over using sysuaf ... > > we actually took the supplied DLL and tweaked it to > work with the HTPASSWORD module from apache, > so you can modify file_auth easily to work with other > file formats ... forgot to mention ... there are two supplied DLLs for authentication ... SAMPLE_AUTH_AXP and _VAX autheticate againset SYSUAF where FILE_AUTH_AXP and _VAX authenticate againset a generic file layout which you can modify to use any layout you want ... ------------------------------ Date: 2 Apr 2007 05:36:31 -0700 From: genius@marblecliff.com Subject: Re: Purveyor and Auth DLL Message-ID: <1175517391.629618.48020@y66g2000hsf.googlegroups.com> On Apr 2, 7:46 am, "Hal Kuff" wrote: > Hi, > > Can anyone volunteer about 10 mins on the phone to go over how to link > in the dll so we can use the authenticate model? If so can you send a > contact number to kuff at tessco dot com , or perhaps sumamrize it here > would be great as well. I hear Mr. Maniotes used to be the community guru > but we do not have current info on him. > > --HK acutally, it is quite easy ... 1. compile the file_auth.c program (c 6.0 or higher) using the file_auth.com dcl routine 2. place the .DLL compiled result in your scripts directory 3. next run the purveyor RSM management web interface and goto to the realm that you want to authenticate and check the box "Use authentication DLL" and fill the the name box with the directory and name of your scripts directory you entered in the virtual servers setup screen ... 4. sit back and relax because vms authentication takes over using sysuaf ... we actually took the supplied DLL and tweaked it to work with the HTPASSWORD module from apache, so you can modify file_auth easily to work with other file formats ... Reply Reply to author Forward 4. Hal Kuff View profile More options Apr 2, 8:26 am Newsgroups: comp.os.vms From: "Hal Kuff" Date: Mon, 2 Apr 2007 08:26:33 -0400 Local: Mon, Apr 2 2007 8:26 am Subject: Re: Purveyor and Auth DLL Reply | Reply to author | Forward | Print | Individual message | Show original | Report this message | Find messages by this author Hi, thanks.... we have someone here that has been having a tough go of it... I will verify they are following your hints wrote in message news:1175516265.953692.128330@b75g2000hsg.googlegroups.com... - Hide quoted text - - Show quoted text - > On Apr 2, 7:46 am, "Hal Kuff" wrote: >> Hi, >> Can anyone volunteer about 10 mins on the phone to go over how to >> link >> in the dll so we can use the authenticate model? If so can you send a >> contact number to kuff at tessco dot com , or perhaps sumamrize it here >> would be great as well. I hear Mr. Maniotes used to be the community guru >> but we do not have current info on him. >> --HK > acutally, it is quite easy ... > 1. compile the file_auth.c program (c 6.0 or higher) using > the file_auth.com dcl routine > 2. place the .DLL compiled result in your scripts directory > 3. next run the purveyor RSM management web interface > and goto to the realm that you want to authenticate > and check the box "Use authentication DLL" and fill the > the name box with the directory and name of your scripts > directory you entered in the virtual servers setup screen ... > 4. sit back and relax because vms authentication takes > over using sysuaf ... > we actually took the supplied DLL and tweaked it to > work with the HTPASSWORD module from apache, > so you can modify file_auth easily to work with other > file formats ... Reply Reply to author Forward Rate this post: Text for clearing space 5. gen...@marblecliff.com View profile More options Apr 2, 8:26 am Newsgroups: comp.os.vms From: gen...@marblecliff.com Date: 2 Apr 2007 05:26:44 -0700 Local: Mon, Apr 2 2007 8:26 am Subject: Re: Purveyor and Auth DLL Reply | Reply to author | Forward | Print | Individual message | Show original | Remove | Report this message | Find messages by this author On Apr 2, 8:17 am, gen...@marblecliff.com wrote: - Hide quoted text - - Show quoted text - > On Apr 2, 7:46 am, "Hal Kuff" wrote: > > Hi, > > Can anyone volunteer about 10 mins on the phone to go over how to link > > in the dll so we can use the authenticate model? If so can you send a > > contact number to kuff at tessco dot com , or perhaps sumamrize it here > > would be great as well. I hear Mr. Maniotes used to be the community guru > > but we do not have current info on him. > > --HK > acutally, it is quite easy ... > 1. compile the file_auth.c program (c 6.0 or higher) using > the file_auth.com dcl routine > 2. place the .DLL compiled result in your scripts directory > 3. next run the purveyor RSM management web interface > and goto to the realm that you want to authenticate > and check the box "Use authentication DLL" and fill the > the name box with the directory and name of your scripts > directory you entered in the virtual servers setup screen ... > 4. sit back and relax because vms authentication takes > over using sysuaf ... > we actually took the supplied DLL and tweaked it to > work with the HTPASSWORD module from apache, > so you can modify file_auth easily to work with other > file formats ... forgot to mention ... there are two supplied DLLs for authentication ... SAMPLE_AUTH_AXP and _VAX autheticate againset SYSUAF where FILE_AUTH_AXP and _VAX authenticate againset a generic file layout which you can modify to use any layout you want ... Reply Reply to author Forward 6. gen...@marblecliff.com View profile More options Apr 2, 8:29 am Newsgroups: comp.os.vms From: gen...@marblecliff.com Date: 2 Apr 2007 05:29:41 -0700 Local: Mon, Apr 2 2007 8:29 am Subject: Re: Purveyor and Auth DLL Reply | Reply to author | Forward | Print | Individual message | Show original | Remove | Report this message | Find messages by this author On Apr 2, 8:26 am, gen...@marblecliff.com wrote: - Hide quoted text - - Show quoted text - > On Apr 2, 8:17 am, gen...@marblecliff.com wrote: > > On Apr 2, 7:46 am, "Hal Kuff" wrote: > > > Hi, > > > Can anyone volunteer about 10 mins on the phone to go over how to link > > > in the dll so we can use the authenticate model? If so can you send a > > > contact number to kuff at tessco dot com , or perhaps sumamrize it here > > > would be great as well. I hear Mr. Maniotes used to be the community guru > > > but we do not have current info on him. > > > --HK acutally, it is quite easy ... there are two supplied DLLs for authentication ... SAMPLE_AUTH_AXP and _VAX autheticate againset SYSUAF where FILE_AUTH_AXP and _VAX authenticate againset a generic file layout which you can modify to use any layout you want ...- Hide quoted text - also the sample_auth "c" routine is ALREADY compiled where the file_auth IS NOT compiled ... 1. compile the file_auth.c program (c 6.0 or higher) using the file_auth.com dcl routine (sample_auth for sysuaf is already compiled) 2. place the .DLL compiled result in your scripts directory 3. next run the purveyor RSM management web interface and goto to the realm that you want to authenticate and check the box "Use authentication DLL" and fill the the name box with the directory and name of your scripts directory you entered in the virtual servers setup screen ... 4. sit back and relax because vms authentication takes over using sysuaf ... we actually took the supplied DLL and tweaked it to work with the HTPASSWORD module from apache, so you can modify file_auth easily to work with other file formats ... ------------------------------ Date: 2 Apr 2007 05:38:59 -0700 From: genius@marblecliff.com Subject: Re: Purveyor and Auth DLL Message-ID: <1175517539.396525.254450@y80g2000hsf.googlegroups.com> On Apr 2, 7:46 am, "Hal Kuff" wrote: > Hi, > > Can anyone volunteer about 10 mins on the phone to go over how to link > in the dll so we can use the authenticate model? If so can you send a > contact number to kuff at tessco dot com , or perhaps sumamrize it here > would be great as well. I hear Mr. Maniotes used to be the community guru > but we do not have current info on him. > > --HK acutally, it is quite easy ... there are two supplied DLLs for authentication ... SAMPLE_AUTH_AXP and _VAX autheticate againset SYSUAF where FILE_AUTH_AXP and _VAX authenticate againset a generic file layout which you can modify to use any layout you want ... also the sample_auth "c" routine is ALREADY compiled where the file_auth IS NOT compiled ... 1. compile the file_auth.c program (c 6.0 or higher) using the file_auth.com dcl routine (sample_auth for sysuaf is already compiled) 2. place the .DLL compiled result in your scripts directory 3. next run the purveyor RSM management web interface and goto to the realm that you want to authenticate and check the box "Use authentication DLL" and fill the the name box with the directory and name of your scripts directory you entered in the virtual servers setup screen ... 4. sit back and relax because vms authentication takes over using sysuaf ... we actually took the supplied DLL and tweaked it to work with the HTPASSWORD module from apache, so you can modify file_auth easily to work with other file formats ... ------------------------------ Date: 2 Apr 2007 06:06:07 -0700 From: genius@marblecliff.com Subject: Re: Purveyor and Auth DLL Message-ID: <1175519167.433503.310720@n59g2000hsh.googlegroups.com> On Apr 2, 8:38 am, gen...@marblecliff.com wrote: > On Apr 2, 7:46 am, "Hal Kuff" wrote: > > > Hi, > > > Can anyone volunteer about 10 mins on the phone to go over how to link > > in the dll so we can use the authenticate model? If so can you send a > > contact number to kuff at tessco dot com , or perhaps sumamrize it here > > would be great as well. I hear Mr. Maniotes used to be the community guru > > but we do not have current info on him. > > > --HK > > acutally, it is quite easy ... > > there are two supplied DLLs for authentication ... > > SAMPLE_AUTH_AXP and _VAX autheticate againset SYSUAF > where FILE_AUTH_AXP and _VAX authenticate againset a generic > file layout which you can modify to use any layout you want ... > > also the sample_auth "c" routine is ALREADY compiled > where the file_auth IS NOT compiled ... > > 1. compile the file_auth.c program (c 6.0 or higher) using > the file_auth.com dcl routine (sample_auth for sysuaf > is already compiled) > > 2. place the .DLL compiled result in your scripts directory > > 3. next run the purveyor RSM management web interface > and goto to the realm that you want to authenticate > and check the box "Use authentication DLL" and fill the > the name box with the directory and name of your scripts > directory you entered in the virtual servers setup screen ... > > 4. sit back and relax because vms authentication takes > over using sysuaf ... > > we actually took the supplied DLL and tweaked it to > work with the HTPASSWORD module from apache, > so you can modify file_auth easily to work with other > file formats ... see Mark, we are not the only ones using purveyor ... :) ------------------------------ Date: 2 Apr 2007 10:40:23 -0700 From: genius@marblecliff.com Subject: Re: Purveyor and Auth DLL Message-ID: <1175535623.831802.317270@e65g2000hsc.googlegroups.com> On Apr 2, 8:08 am, Dan Foster wrote: > In article , Hal Kuff wrote: > > > Can anyone volunteer about 10 mins on the phone to go over how to > > link in the dll so we can use the authenticate model? If so can > > you send a contact number to kuff at tessco dot com , or perhaps > > sumamrize it here would be great as well. I hear Mr. Maniotes used > > to be the community guru but we do not have current info on him. > > I don't use Purveyor but found this with a minute of Googling: > > http://wwwvms.mppmu.mpg.de/internet_product_suite/HTML_PURVEYOR/PG_HT... > > SAMPLE_AUTH.C comments includes this: > > To compile and link, use: > @PURVEYOR_SAMPLES:SAMPLE_AUTH > > So you'd probably want to look at PURVEYOR_SAMPLES:SAMPLE_AUTH.COM to > see how it's built and linked. > > Or by 'link in the dll', do you mean how to adjust the configuration to > use the authentication DLL? If so, then: > > http://vms.process.com/~help/helptips.html > > (and read the 'Configuring Large Group and User Databases' section.) > > Looks simple and straightforward so you should be all set there, barring > issues. > > -Dan actually, you can find that at vms.process.com it is from the users manual ... ------------------------------ Date: 1 Apr 2007 23:21:27 -0700 From: "Ger_Marsh" Subject: Re: Switching off MULTITHREAD Message-ID: <1175494887.583857.325180@p15g2000hsd.googlegroups.com> > Gerald, > > An interaction between ASTs and threading would not be the early on my > list of possible issues. An image making heavy use of ASTs frequently > appears to permanently be in a HIB state (although the CPU time, IO, > etc. should be gradually increasing). If this does not happen, I often > find that somewhere along the line the application is failing to > schedule the next event. This can be tracked, although it is sometimes > time consuming. > > While I would not expect eliminating threads at the Kernel level to > have a positive effect. It might, by happenstance, change the > frequency that the problem occurs, but that is moving the problem, not > eliminating it. > > A note on my experience underlying the above: > > "Threads and Events", HP Enterprise Technology Symposium, 2002,http://www.rlgsc.com/hpets/2002/1228.html > "Introduction to OpenVMS AST Programming", Compaq Enterprise > Technology Symposium, 2000,http://www.rlgsc.com/cets/2000/435.html > "Threads vs. Events", Fall 1996 US DECUS Symposium,http://www.rlgsc.com/decus/usf96/ad019.pdf > "OpenVMS-ALPHA/VAX Asynchronous System Trap Internals", Fall 1996 US > DECUS Symposium,http://www.rlgsc.com/decus/usf96/ad039.pdf > "Introduction to AST Programming", Fall 1995 US DECUS Symposium,http://www.rlgsc.com/decus/usf95/ad029.pdf > > and several other presentations and seminars on the use of threads and > events. > > Will be happy to continue the discussion, publicly in the forum, or > privately. > > - Bob Gezelter,http://www.rlgsc.com Thank you, Bob. I'll be looking at your presentations in some detail. They just show how little some of us know after decades of VMS systems management! I cannot understand, though, how the inter-process communication has been working OK for 5 years until we upgraded MQ to V5.3 As I mentioned to Kerry, we saw the same scenario when we upgraded the CPU's to faster versions. We had to pull the upgrade pretty quickly! Subsequently this was found to be a "known issue" and we have already applied that patch too. Bye for now and thanks for the info. Gerald. ------------------------------ Date: 1 Apr 2007 23:21:48 -0700 From: "Ger_Marsh" Subject: Re: Switching off MULTITHREAD Message-ID: <1175494908.921953.282950@l77g2000hsb.googlegroups.com> > > Wag, but do you have the following V7.3-2 MQ Series patch applied?ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_MQ-V0400.txt > > It mentions a few process thread issues resolved. > > As a suggestion, this MQ patch is included in the latest Update patch > kit, so you might want to ensure you have all the latest V7.3-2 patches > and use this Update kit vs the individual MQ patch. > > ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_UPDATE-V1100.t > xtftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/ > > Regards > > Kerry Main > Senior Consultant > HP Services Canada > Voice: 613-592-4660 > Fax: 613-591-4477 > kerryDOTmainAThpDOTcom > (remove the DOT's and AT) > > OpenVMS - the secure, multi-site OS that just works. Thank you, Kerry, but we applied those patches some time ago. We have also applied another patch which allegedly cures a problem when CPU's are upgraded - it's a race condition. The process behaved exactly the same then - ie sits in HIB state. We are going to reduce the number of links in the particular chain to see if it helps. Reverting back to MQ V5.1 is "inadvisable and unsupported"! Bye for now, Gerald. ------------------------------ Date: Mon, 02 Apr 2007 10:47:52 -0500 From: Dave Froble Subject: Re: Switching off MULTITHREAD Message-ID: Ger_Marsh wrote: >> Wag, but do you have the following V7.3-2 MQ Series patch applied?ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_MQ-V0400.txt >> >> It mentions a few process thread issues resolved. >> >> As a suggestion, this MQ patch is included in the latest Update patch >> kit, so you might want to ensure you have all the latest V7.3-2 patches >> and use this Update kit vs the individual MQ patch. >> >> ftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/VMS732_UPDATE-V1100.t >> xtftp://ftp.itrc.hp.com/openvms_patches/alpha/V7.3-2/ >> >> Regards >> >> Kerry Main >> Senior Consultant >> HP Services Canada >> Voice: 613-592-4660 >> Fax: 613-591-4477 >> kerryDOTmainAThpDOTcom >> (remove the DOT's and AT) >> >> OpenVMS - the secure, multi-site OS that just works. > > Thank you, Kerry, but we applied those patches some time ago. > > We have also applied another patch which allegedly cures a problem > when CPU's are upgraded - it's a race condition. The process behaved > exactly the same then - ie sits in HIB state. > > We are going to reduce the number of links in the particular chain to > see if it helps. > > Reverting back to MQ V5.1 is "inadvisable and unsupported"! Have to ask, what is your objective? If your objective is for the application to 'work', and MQ V5.1 'worked', then, if it ain't broke, why are you fixing it? Choose one: 1) working and "inadvisable and unsupported" 2) not working and "advisable and supported" -- David Froble Tel: 724-529-0450 Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com DFE Ultralights, Inc. 170 Grimplin Road Vanderbilt, PA 15486 ------------------------------ Date: 2 Apr 2007 07:33:43 -0500 From: briggs@encompasserve.org Subject: Re: TCPIP$SMTP_MIME_HACK Message-ID: In article , helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes: > $! TCPIP$SMTP_MIME_HACK > $! When set, SMTP accepts 8BITMIME requests from SMTP clients, > $! preventing the clients from converting the message into a 7-bit > $! format. > $! > $!DEFINE/SYSTEM TCPIP$SMTP_MIME_HACK 1 > > What exactly does this do? A quick web search turns up RFC 1652 which defines an ESMTP extension using the keyword "8BITMIME". Background... Classically, SMTP (RFC 821) is a 7 bit transport mechanism. It is not supposed to be able to handle 8 bit messages. If you want to pump 8 bit messages down a 7 bit pipe you need to encode them. Clasically, MIME (RFC 2045 et al) provides three mechanisms to handle 8 bit messages. You can encode them Quoted-Printable. You can encode them BASE64. Or you can pump them down an 8-bit safe pipe. But since SMTP isn't 8-bit safe, you're stuck with one of the two encodings. RFC1652 defines an ESMTP (RFC 1869) extension to allow an SMTP client and server to negotiate an 8-bit safe pipe. Details... When an ESMTP client connects to an ESMTP server it will open up the dialogue with: EHLO client.host.name This is, of course, the standard ESMTP greeting. If the server is ancient and only understands SMTP the client would fall back to the older "HELO client.host.name" greeting instead. But we're talking ESMTP here. The server will respond with something that lists the ESMTP options that it is willing to negotiate. For instance: 250-server.host.name Hello [192.168.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ONEX 250-ETRN 250-XUSR 250 HELP Note the "250-8BITMIME" there. This advertises that the server understands and is willing to use the 8 bit MIME extension. In the absence of this advertisement, the server is expected to be able to accept only messages encoded in 7 bit ASCII. The client is expected to encode 8 bit messages accordingly. If the sending user agent has not already done QUOTED-PRINTABLE or BASE64 encoding on the message, the SMTP client is now stuck with that task. [Which is arguably an abuse of protocol layering, but that's neither here nor there]. In the presence of this advertisement, the client can request its use with, for instance: MAIL FROM: BODY=8BITMIME and the server can accept this with 250 Sender and 8BITMIME ok So setting $!DEFINE/SYSTEM TCPIP$SMTP_MIME_HACK 1 causes the VMS SMTP receiver to [at least pretend to] be able to receive 8 bit SMTP traffic. It will advertise its willingness in the greeting response. And it will accept the option on the MAIL FROM: line that it parses. Mind you, I've never used the option and I don't know if there are any restrictions on the ability of the VMS smtp server to properly handle 8 bit message bodies. But this is the apparent meaning of the logical name. ------------------------------ End of INFO-VAX 2007.184 ************************