1 INFO-VAX	Tue, 21 Nov 2006	Volume 2006 : Issue 640       Contents:! Re: Educational VMS IA64 licenses ! Re: Educational VMS IA64 licenses ! Re: Educational VMS IA64 licenses ! Re: Educational VMS IA64 licenses 8 First TCP/IP (UCX) Release, Oldest VMS with (limited) IP  Re: Huge Bug in TPU (Capitalize)  Re: Huge Bug in TPU (Capitalize)% Re: LDdriver V9.0 fieldtest available  Re: OpenVMS Support Issues Re: OpenVMS Support IssuesC Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched C Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched * Re: Purpose of uppercasing a RUN command ?. Re: Question: Can anyone write device drivers/ Re: Strategies for time offsets & Using the VMS debugger with C pointers* RE: Using the VMS debugger with C pointers= Re: What layered products are important for a VAX VMS system? = Re: What layered products are important for a VAX VMS system? = Re: What layered products are important for a VAX VMS system?  Re: Who called me? Re: Who called me?  F ----------------------------------------------------------------------  % Date: Mon, 20 Nov 2006 16:18:36 -0800 , From: "Malcolm Dunnett" <dunnett@mala.bc.ca>* Subject: Re: Educational VMS IA64 licenses Message-ID: <4562455c$1@flight>   F "Stephen Hoffman" <Hoff@HoffmanLabs-RemoveThis-.Org> wrote in message " news:ejlblj$b64$1@pyrite.mv.net...  K >   You should have a OPENVMS-I64-FOE, OPENVMS-I64-EOE or OPENVMS-I64-MCOE  I > license -- I don't remember which, but any will authorize base OpenVMS  I > I64 -- in the stash of licenses received.  There was a brief discssion  K > here, and the EDUOE Educational and (though I haven't looked for it) the  J > HOE Hobbyist licenses would be for other vendors or other products that H > want to tie to into that license and into that environment as part of  > their licensing.  B There was an OPENVMS-ALPHA-USER included in the "layered products"F license file, but loading it didn't do anything useful ( which is not 
 surprising as G I understand all IA64 VMS licenses are already "unlimited user" anyway)   ? For comparison purposes I downloaded a VMS hobbyist O/S PAK for @ IA64. It comes up with a product name of  "OPENVMS-FOE64" rather= than the "OPENVMS-I64-EDUOE" that I get with the EDU program.   3 Just to see what would happen I loaded the hobbyist ; PAK onto the rx2600 - it wasn't recognized as valid either.   L With either of these PAKS loaded ( or even with both loaded ) I get the "no  license K is active for this software product" when I log in and only console logins   are allowed.  E Can anyone confirm that they've gotten VMS to work on IA64 using the   hobbyist PAKS?K That won't help me in the long run but at least it would confirm that it's   supposed to work1 and I can try to figure out what I've done wrong.    ------------------------------  % Date: Mon, 20 Nov 2006 19:46:22 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>* Subject: Re: Educational VMS IA64 licenses) Message-ID: <ejti90$2jq5$1@pyrite.mv.net>    Malcolm Dunnett wrote:  G > Can anyone confirm that they've gotten VMS to work on IA64 using the   > hobbyist PAKS?M > That won't help me in the long run but at least it would confirm that it's   > supposed to work3 > and I can try to figure out what I've done wrong.   E    I would not expect any of the PAKs you have mentioned as being in  H your possession here would do what you want; none of the PAKs mentioned C would appear to be those typically necessary to enable OpenVMS I64.   I    AFAIK, the three base PAKs are "it" here.  You need one of the three:  D OPENVMS-I64-FOE, OPENVMS-I 4-EOE or OPENVMS-I64-MCOE.  I don't know = which was cleared here by HP for hobbyists: FOE, EOE or MCOE.   G    [I poked around a couple of days ago looking for an LMF-related ECO  I for OpenVMS I64 releases, and didn't see one.  This would be ond vehicle  2 for adding new licenses into the existing checks.]   ------------------------------  % Date: Mon, 20 Nov 2006 16:58:32 -0800 , From: "Malcolm Dunnett" <dunnett@mala.bc.ca>* Subject: Re: Educational VMS IA64 licenses Message-ID: <45624eb9$1@flight>   F "Stephen Hoffman" <Hoff@HoffmanLabs-RemoveThis-.Org> wrote in message # news:ejti90$2jq5$1@pyrite.mv.net...   K >   I would not expect any of the PAKs you have mentioned as being in your  K > possession here would do what you want; none of the PAKs mentioned would  ? > appear to be those typically necessary to enable OpenVMS I64.  > J   I expect you are right.  That's why I asked if anyone has managed to getL hobbyist working on IA64, I suspect the answer will be no and that somethingF else is required ( eg a "yet to be released" LMF ECO which may address  both the hobbyist and EDU PAKs).  I   Perhaps I'm just too much on the bleeding edge and there's more work to E be done on the programs before they are usable for IA64, or perhaps I ? just totally misunderstand what the programs intend to deliver.    ------------------------------  % Date: Mon, 20 Nov 2006 20:17:05 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>* Subject: Re: Educational VMS IA64 licenses) Message-ID: <ejtk2h$2kb2$1@pyrite.mv.net>    Malcolm Dunnett wrote:  K >   Perhaps I'm just too much on the bleeding edge and there's more work to G > be done on the programs before they are usable for IA64, or perhaps I A > just totally misunderstand what the programs intend to deliver.   I    I suspect the program simply gave you the wrong PAKs, or insufficient  E PAKs.  I'm requesting the PAKs for a look, but this matter is likely  E going to require the involvement of the Deities of the hobbyist site.    ------------------------------  % Date: Mon, 20 Nov 2006 19:12:05 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org>A Subject: First TCP/IP (UCX) Release, Oldest VMS with (limited) IP ) Message-ID: <ejtg8o$2j4m$1@pyrite.mv.net>   E There was a recent thread around here where a question on the oldest  G OpenVMS VAX (VAX/VMS or MicroVMS) release with IP support (optionally)  H available was raised.  Here's the related and oldest (and very limited) > UCX-related information; the oldest VMS version with UCX (IP).  H As for CMU IP or other IP products that might be around, that's another  discussion.   G [Found this announcement on the way to something else equally ancient.]    --   VMS/ULTRIX Connection V1.0  I This is a VMS layered software product that provides VMS services to UNIX @ clients.  This product includes the Internet (TCP/IP) networkingJ protocols running on VMS and the Network File System (NFS) server softwareL running on VMS.  The importance of this product is that it allows any singleJ VMS system or a large VAXcluster system to act as an NFS server to a largeG number of UNIX-based workstations.  For the first time Digital provides L UNIX-based workstations with access to the high availability data management2 features of a VAXcluster system such as shadowing.   Key Features: V1.0 support  % - Transmission Control Protocol (TCP)  - Internet Protocol (IP) - User Datagram Protocol (UDP)# - Address Resolution Protocol (ARP)  - File Transfer Protocol (FTP)  B Future versions will support mail (SMTP) and remote login (Telnet)
 protocols.   Prerequesite Software required:   7 - For the VMS server, VMS 4.7 or V5.0, or MicroVMS V4.7 L - For the UNIX client, any UNIX-based system which supports NFS V2.0 and theI    networking protocols specified by the DDN (Defense Data Network) RFCs, K    including ULTRIX-32 V2.2 or later and ULTRIX Worksystem Software V1.1 or 	    later.   % Deliveries begin in the fall of 1988.    ------------------------------    Date: 20 Nov 2006 16:06:17 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ) Subject: Re: Huge Bug in TPU (Capitalize) 3 Message-ID: <2$YMr5DNp35i@eisner.encompasserve.org>   g In article <9e61f$4561c2ae$cef8887a$1487@TEKSAVVY.COM>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:  > Big John wrote:  > 9 >> The trick is to use the eve-supplied command procedure 0 >> 'eve$add_word_separators'. More specifically,! >> eve$add_word_separators ("-");  >> in your init eve commands.  > 
 > Thanks ! > H > I still think it should be made default though. it shouldn't be up to ) > individual users to rewrite TPU/EVE ...   G    One expansion of EVE is "Extensible VMS Editor".  You're supposed to     customise it.  F    But it should not be changed so that it breaks everything I do justE    to keep you happy.  Upward compatability is a very strong point in     VMS.    ------------------------------    Date: 20 Nov 2006 16:07:42 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) ) Subject: Re: Huge Bug in TPU (Capitalize) 3 Message-ID: <6mVqW6iZYLTo@eisner.encompasserve.org>   | In article <paul.sture.nospam-1E3883.18361820112006@mac.sture.homeip.net>, Paul Sture <paul.sture.nospam@hispeed.ch> writes: > ( > SET ENTITY WORD '  .,?!;:[]()<>*-+=/\' >   B    Yes.  I recall that and several other commands in EDTINI which D    simply reproduce the default behaviour of the out-of-the-box EDT.      Waste of good disk space.   ------------------------------  % Date: Mon, 20 Nov 2006 21:01:25 +0100 4 From: Jur van der Burg <"vdburg at hotmail dot com">. Subject: Re: LDdriver V9.0 fieldtest available4 Message-ID: <45620999$0$333$e4fe514c@news.xs4all.nl>  G If you mean limiting the 'tape' size, yes. That's just dependent on the K containerfile size, so if you create a small file you'll have a small tape.    Jur.     prep@prep.synonet.com wrote:8 > Jur van der Burg <"vdburg at hotmail dot com"> writes: > F >> LDdriver V9.0 is now available for fieldtest. The major new featureF >> is Logical Magtape (LM) support, that is to use a file on disk as a >> magtape.  > ' > Can you set a size limit on LM units?  >    ------------------------------    Date: 20 Nov 2006 16:04:01 -0800- From: "Beach Runner" <Bob4Health@hotmail.com> # Subject: Re: OpenVMS Support Issues B Message-ID: <1164067441.842398.78110@b28g2000cwb.googlegroups.com>  
 Sue wrote: > Dear Newsgroup,  > I > The most important thing for folks to do is for folks to send me detail B > here is what happend when I called.  What does not help is "this > stinks"  What helps is >  > call log number xxxxxxx F > On x date I called and spoke to x regarding and spent so long on the@ > phone and explain what the problem is and the difference is XX > I > It is important to note that this is not a VMS specific thing so we are I > not being singled out.  But if you send me the information I am willing H > to send it to managment and make sure they have it.  What they do with > it I can not say.  > F > We stand together or we fall apart.  Thank you so much for being theH > wonderful people you  the customers are the reasons that I love what I > do. 
 > big hug, > Sue  >  >  >  >  >  >  > William Webb wrote: ? > > On 11/14/06, David J Dachtera <djesys@earthlink.net> wrote:  > > > Hello, Gerry,  > > > N > > > In so much as I'm inclined to agree with you, even though I am an activeR > > > instigator (read: OpenVMS advocate), I think the fact that the issue *IS* soU > > > pervasive here on the 'net speaks more loudly and eloquently than even the most  > > > admired of the ancients. > > > U > > > The issue is immediate, proximate and of vital import to prolonging the life of  > > > the product. > > > U > > > My take is that we need to get HP management on-board with the user community - V > > > that is *THE* most important issue for Encompass, this SIG and any and all other8 > > > groups (users, ISVs, VARs, OEMs, etc.) to address. > > > ) > > > Without HP management's buy-in, ...  > > > D > > > Well, I'm sure there's no need for me to finish that sentence. > > >  > > > David J Dachtera > > >  > > > P.S.: U > > > I think it would be *HIGHLY constructive for *EVERY*one to avoid the use of the V > > > word "whining". It discounts and trivializes an issue that even Sue's job hinges	 > > > on.  > > >   > > > -----Original Message-----V > > > From: Czadowski, Gerard A (Gerry) [mailto:Gerry.Czadowski@NAV-INTERNATIONAL.COM] > > > 0 > > > Sent: Thursday, November 09, 2006 12:37 PM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Fellow VMS advocates,  > > > J > > > This topic started as a plea for advocacy by Encompass regarding theN > > > support issue. I believe that the SIG leadership has responded that theyK > > > will take up the request and address our concerns with HP management. & > > > Let's please give them a chance. > > > L > > > With this thread there are signs that the Encompass VMS-SIG list is onL > > > the verge of degenerating to the C.O.V. level of whining and going offL > > > topic -- the perennial lack of VMS marketing issue has reared its headK > > > here.  Can we please limit this noise pollution?  I'm on the verge of # > > > unsubscribing from this list.  > > > $ > > > Thanks for your consideration. > > >   > > > -----Original Message-----> > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]0 > > > Sent: Thursday, November 09, 2006 12:04 PM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Greetings, > > > K > > > Not sure how many folks reading the "mainstream media" need an MES to M > > > run their wafer fabs, however, the folks that do have a couple of major M > > > players to contend with, PROMIS & Workstream, and they both run on VMS.  > > >  > > > Have Fun,  > > > TW Heim Jr.  > > > twhjr@HeimNet.com  > > > www.HeimNet.com  > > > OpenVMS.HeimNet.com  > > >   > > > -----Original Message-----8 > > > From: David J Dachtera [mailto:djesys@comcast.net]0 > > > Sent: Thursday, November 09, 2006 12:57 PM: > > > To: Heim, Thomas W; VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: RE: OpenVMS Support Issues  > > > N > > > If it's not in the public eye (read: mainstream media) it's "invisible". > > >  > > > D.J.D. > > >   > > > -----Original Message-----> > > > From: Heim, Thomas W [mailto:heimtw@exchptc1.switch.com]/ > > > Sent: Thursday, November 09, 2006 7:29 AM > > > > To: djesys@comcast.net; VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: RE: OpenVMS Support Issues  > > >  > > > Greetings, > > > . > > > "invisible platform, invisible products" > > > , > > > Have you seen the most recent roadmap? > > > D > > > http://h71000.www7.hp.com/openvms/roadmap/openvms_roadmaps.htm > > > N > > > I work most of the time in the area of process control and manufacturingM > > > and mostly in the wafer fab space.  There is a product that is utilized J > > > "World Wide" to help produce most of the ICs (and I mean ALL ICs notH > > > just processors) that everyone use in their day to day lives. ThisN > > > product, PROMIS, was an early adopter of VMS on the Itanium platform and, > > > has been selling it for several years. > > > K > > > Maybe in your vertical market things might be drying up but please do L > > > not try and drag the rest of us, who are flourishing, albeit with some > > > support issues, down.  > > >  > > > Have Fun,  > > > TW Heim Jr.  > > > twhjr@HeimNet.com  > > > www.HeimNet.com  > > > OpenVMS.HeimNet.com  > > >   > > > -----Original Message-----: > > > From: David J Dachtera [mailto:djesys@EARTHLINK.NET]0 > > > Sent: Wednesday, November 08, 2006 9:27 PM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >   > > > No, HP cannot do it alone. > > > K > > > The user base cannot do it alone, even throwing tons of money at ISVs J > > > who face the same VMS-related challenges as the user base: invisible? > > > platform, invisible products, etc. ("stealth marketing").  > > > M > > > In my experience, the user base consistently goes out the ISVs and asks K > > > when we will see their products on I64, only to be told the vendor is 5 > > > not going to I64, they're migrating off of VMS.  > > > L > > > So, the users are doing what they can. It's not as if we can "take ourM > > > ball and go home". If there were VMS-based alternatives from other ISVs H > > > we'd have some leverage. Such is not the case, however. As anotherK > > > respondent cited, even the alternative vendors are, in large measure,  > > > dropping VMS.  > > > I > > > The ball sits squarely in HP's court at this point. Their continued - > > > inaction and/or misaction dooms us all.  > > >  > > > D.J.D. > > >   > > > -----Original Message-----> > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]1 > > > Sent: Wednesday, November 08, 2006 10:42 AM * > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Greetings, > > > M > > > Granted, and I think everyone agrees that HP needs to work very hard on J > > > damage control but is it not also a bigger responsibility of the VMSN > > > user community to push back on the ISVs indicating why the use of VMS is@ > > > a necessity for the efficient operation of their business. > > > L > > > I mean, when you look at it, it is ultimately the users that wield theL > > > mighty sword of the almighty CASH.  In this particular situation HP isJ > > > limited to marketing etc where as the customer holds the real power. > > > L > > > I once worked for a company where they thought it would be a good ideaM > > > to push NT on PowerPCs into their customers control processes and phase K > > > out the dieing VMS (and this was some 10 years ago).  Needless to say M > > > the customers did not favor the idea and to this day I occasionally get I > > > asked questions about the original VMS application that is still in G > > > control and that company is no longer the world leader in control  > > > systems. > > > G > > > HP can not do this alone, we the user community, need to get some L > > > backbone and start standing up to the ISVs.  It would seem that we canL > > > demonstrate to HP that it would behoove them to give us better supportN > > > if we joined together in the effort to increase the visibility of VMS asM > > > an entity and shout from the rooftops that it is alive and viable. This  > > > also is good business. > > >  > > > Have Fun,  > > > TW Heim Jr.  > > > twhjr@HeimNet.com  > > > www.HeimNet.com  > > > OpenVMS.HeimNet.com  > > >   > > > -----Original Message-----6 > > > From: John Zimmerman [mailto:johnz@DIGITASK.COM]0 > > > Sent: Wednesday, November 08, 2006 9:16 AM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > > H > > > It seems to me that the reason "it is incumbent on the folks at HP > > > OpenVMS"K > > > is the same reason as it is the responsibility for the folks as HP-UX J > > > and other Integrity based groups -- it is or should be part of their > > > marketing efforts. > > > M > > > Unless the folks at HP are taking the position that OpenVMS is purely a I > > > legacy operating system and not one which is worth any marketing to G > > > create incentives for current AlphaVMS and new applications to be @ > > > developed for Integrity, then it is at least in part theirE > > > responsibility to promote the O/S.  I believe they do take this K > > > responsibility seriously (even if it might be under-funded) as I just M > > > returned from a DSPP workshop on Itanium development which included all  > > > four supported O/Ses.  > > >  > > >  > > > John Zimmerman  > > > Digitask Consultants, Inc. > > >  > > >  > > >  > > >  > > >  > > > Join my Tribe friends   > > > -----Original Message-----> > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]0 > > > Sent: Wednesday, November 08, 2006 8:45 AM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Greetings, > > > C > > > OK, but... How so is it incumbent on the folks at HP OpenVMS?  > > >  > > > Have Fun,  > > > TW Heim Jr.  > > > twhjr@HeimNet.com  > > > www.HeimNet.com  > > > OpenVMS.HeimNet.com  > > >   > > > -----Original Message-----: > > > From: David J Dachtera [mailto:djesys@EARTHLINK.NET]/ > > > Sent: Tuesday, November 07, 2006 10:41 PM * > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > > L > > > If not "incumbent on the folks at HP OpenVMS", then who? (...incumbent
 > > > upon > > > whom?) > > >  > > > D.J.D. > > >   > > > -----Original Message-----> > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]. > > > Sent: Tuesday, November 07, 2006 3:50 PM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Greetings, > > > N > > > I suppose that the *currently* "might" be implied but it would be better& > > > if it where stated that clearly. > > > 6 > > > "incumbent on the folks at HP OpenVMS"?  How so? > > >  > > > Have Fun,  > > > TW Heim Jr.  > > > twhjr@HeimNet.com  > > > www.HeimNet.com  > > > OpenVMS.HeimNet.com  > > >   > > > -----Original Message-----: > > > From: bradhamilton [mailto:bradhamilton@COMCAST.NET]. > > > Sent: Tuesday, November 07, 2006 4:43 PM* > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG) > > > Subject: Re: OpenVMS Support Issues  > > >  > > > Heim, Thomas W wrote:  > > > > Greetings, > > > >  > > > >  > > > > ) > > > > Slide 4 and 6 seem a bit at odds?  > > > M > > > I don't see a conflict - Cerner on OpenVMS/Integrity is not *currently* N > > > supported, and they will re-evaluate the situation when they test Oracle > > > ! > > > 10gR2 on OpenVMS/Integrity.  > > > M > > > If this is all just a misunderstanding, it is incumbent on the folks at 0 > > > HP OpenVMS to rectify the situation, soon. > > >  > > D > > I think that it would be even more constructive for everyone whoG > > writes HP management a letter to set it aside for 24 hours, go back I > > and look it over with fresh eyes, and then mail it if changes are not  > > deemed to be necessary.  > >  > > For the same reasons.      Face it.  ? Support wil be and continue to be MUCH worse. You can't replace  hundreds of DeccieF VMS support people with 20 or 30 years of tough, real world experienceC with people in India with a few months of training, that can't even  communicate.  G Moving to higher level contracts won't work.  The support will still be F much worse. There will be compression of all issues, as the few peopleG still there that know VMS will be working on calls that would have been + expertly worked on by the departed Deccies.   E And of course, we are no longer dealing with an ethical company.  Dec F was a company based on ethics and quality.  It was a company one could be proud of.  C HP was once a great company too.  Now, the world slimeball comes to F mind. It's sad that so many great people still work there. You can betF the support staff will not get the support they need.  Management that> can replace experts with newbies in India does not value their, employees, their customers or their product.  A Now we see on their sites it says "We value your privacy.".  Does  anyone believe them?D When someone already has demonstrated a complete lack of ethics, can you trust them for anything?  D VMS is still great. And there still are lots of great VMS people and
 applications.   @ We can direct that our money be moved elsewhere. There are otherD organizations that will support VMS. Make sure that HP knows why theC big money is being spent elsewhere.  Just like a bad dog, rub it in E their noses.  And, please not at the engineer and support level.  Get E good examples of the types of support, sales and elevation issues you F run into. Don't blame it on the poor techie in India, it's not his/her fault.  F The best thing would be if HP sells OpenVMS. They know of course, thatD allowed to compete in the real marketplace, it would be a gem again.   ------------------------------  % Date: Mon, 20 Nov 2006 23:47:38 -0500 / From: "William Webb" <william.w.webb@gmail.com> # Subject: Re: OpenVMS Support Issues I Message-ID: <8660a3a10611202047n5ae148d4td084c2ac506ca096@mail.gmail.com>   K On 20 Nov 2006 16:04:01 -0800, Beach Runner <Bob4Health@hotmail.com> wrote:  >  > Sue wrote: > > Dear Newsgroup,  > > K > > The most important thing for folks to do is for folks to send me detail D > > here is what happend when I called.  What does not help is "this > > stinks"  What helps is > >  > > call log number xxxxxxx H > > On x date I called and spoke to x regarding and spent so long on theB > > phone and explain what the problem is and the difference is XX > > K > > It is important to note that this is not a VMS specific thing so we are K > > not being singled out.  But if you send me the information I am willing J > > to send it to managment and make sure they have it.  What they do with > > it I can not say.  > > H > > We stand together or we fall apart.  Thank you so much for being theJ > > wonderful people you  the customers are the reasons that I love what I > > do.  > > big hug, > > Sue  > >  > >  > >  > >  > >  > >  > > William Webb wrote: A > > > On 11/14/06, David J Dachtera <djesys@earthlink.net> wrote:  > > > > Hello, Gerry,  > > > > P > > > > In so much as I'm inclined to agree with you, even though I am an activeT > > > > instigator (read: OpenVMS advocate), I think the fact that the issue *IS* soW > > > > pervasive here on the 'net speaks more loudly and eloquently than even the most   > > > > admired of the ancients. > > > > W > > > > The issue is immediate, proximate and of vital import to prolonging the life of  > > > > the product. > > > > W > > > > My take is that we need to get HP management on-board with the user community - X > > > > that is *THE* most important issue for Encompass, this SIG and any and all other: > > > > groups (users, ISVs, VARs, OEMs, etc.) to address. > > > > + > > > > Without HP management's buy-in, ...  > > > > F > > > > Well, I'm sure there's no need for me to finish that sentence. > > > >  > > > > David J Dachtera > > > > 
 > > > > P.S.: W > > > > I think it would be *HIGHLY constructive for *EVERY*one to avoid the use of the X > > > > word "whining". It discounts and trivializes an issue that even Sue's job hinges > > > > on.  > > > > " > > > > -----Original Message-----X > > > > From: Czadowski, Gerard A (Gerry) [mailto:Gerry.Czadowski@NAV-INTERNATIONAL.COM] > > > > 2 > > > > Sent: Thursday, November 09, 2006 12:37 PM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Fellow VMS advocates,  > > > > L > > > > This topic started as a plea for advocacy by Encompass regarding theP > > > > support issue. I believe that the SIG leadership has responded that theyM > > > > will take up the request and address our concerns with HP management. ( > > > > Let's please give them a chance. > > > > N > > > > With this thread there are signs that the Encompass VMS-SIG list is onN > > > > the verge of degenerating to the C.O.V. level of whining and going offN > > > > topic -- the perennial lack of VMS marketing issue has reared its headM > > > > here.  Can we please limit this noise pollution?  I'm on the verge of % > > > > unsubscribing from this list.  > > > > & > > > > Thanks for your consideration. > > > > " > > > > -----Original Message-----@ > > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]2 > > > > Sent: Thursday, November 09, 2006 12:04 PM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Greetings, > > > > M > > > > Not sure how many folks reading the "mainstream media" need an MES to O > > > > run their wafer fabs, however, the folks that do have a couple of major O > > > > players to contend with, PROMIS & Workstream, and they both run on VMS.  > > > >  > > > > Have Fun,  > > > > TW Heim Jr.  > > > > twhjr@HeimNet.com  > > > > www.HeimNet.com  > > > > OpenVMS.HeimNet.com  > > > > " > > > > -----Original Message-----: > > > > From: David J Dachtera [mailto:djesys@comcast.net]2 > > > > Sent: Thursday, November 09, 2006 12:57 PM< > > > > To: Heim, Thomas W; VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: RE: OpenVMS Support Issues  > > > > P > > > > If it's not in the public eye (read: mainstream media) it's "invisible". > > > >  > > > > D.J.D. > > > > " > > > > -----Original Message-----@ > > > > From: Heim, Thomas W [mailto:heimtw@exchptc1.switch.com]1 > > > > Sent: Thursday, November 09, 2006 7:29 AM @ > > > > To: djesys@comcast.net; VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: RE: OpenVMS Support Issues  > > > >  > > > > Greetings, > > > > 0 > > > > "invisible platform, invisible products" > > > > . > > > > Have you seen the most recent roadmap? > > > > F > > > > http://h71000.www7.hp.com/openvms/roadmap/openvms_roadmaps.htm > > > > P > > > > I work most of the time in the area of process control and manufacturingO > > > > and mostly in the wafer fab space.  There is a product that is utilized L > > > > "World Wide" to help produce most of the ICs (and I mean ALL ICs notJ > > > > just processors) that everyone use in their day to day lives. ThisP > > > > product, PROMIS, was an early adopter of VMS on the Itanium platform and. > > > > has been selling it for several years. > > > > M > > > > Maybe in your vertical market things might be drying up but please do N > > > > not try and drag the rest of us, who are flourishing, albeit with some > > > > support issues, down.  > > > >  > > > > Have Fun,  > > > > TW Heim Jr.  > > > > twhjr@HeimNet.com  > > > > www.HeimNet.com  > > > > OpenVMS.HeimNet.com  > > > > " > > > > -----Original Message-----< > > > > From: David J Dachtera [mailto:djesys@EARTHLINK.NET]2 > > > > Sent: Wednesday, November 08, 2006 9:27 PM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > > " > > > > No, HP cannot do it alone. > > > > M > > > > The user base cannot do it alone, even throwing tons of money at ISVs L > > > > who face the same VMS-related challenges as the user base: invisibleA > > > > platform, invisible products, etc. ("stealth marketing").  > > > > O > > > > In my experience, the user base consistently goes out the ISVs and asks M > > > > when we will see their products on I64, only to be told the vendor is 7 > > > > not going to I64, they're migrating off of VMS.  > > > > N > > > > So, the users are doing what they can. It's not as if we can "take ourO > > > > ball and go home". If there were VMS-based alternatives from other ISVs J > > > > we'd have some leverage. Such is not the case, however. As anotherM > > > > respondent cited, even the alternative vendors are, in large measure,  > > > > dropping VMS.  > > > > K > > > > The ball sits squarely in HP's court at this point. Their continued / > > > > inaction and/or misaction dooms us all.  > > > >  > > > > D.J.D. > > > > " > > > > -----Original Message-----@ > > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]3 > > > > Sent: Wednesday, November 08, 2006 10:42 AM , > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Greetings, > > > > O > > > > Granted, and I think everyone agrees that HP needs to work very hard on L > > > > damage control but is it not also a bigger responsibility of the VMSP > > > > user community to push back on the ISVs indicating why the use of VMS isB > > > > a necessity for the efficient operation of their business. > > > > N > > > > I mean, when you look at it, it is ultimately the users that wield theN > > > > mighty sword of the almighty CASH.  In this particular situation HP isL > > > > limited to marketing etc where as the customer holds the real power. > > > > N > > > > I once worked for a company where they thought it would be a good ideaO > > > > to push NT on PowerPCs into their customers control processes and phase M > > > > out the dieing VMS (and this was some 10 years ago).  Needless to say O > > > > the customers did not favor the idea and to this day I occasionally get K > > > > asked questions about the original VMS application that is still in I > > > > control and that company is no longer the world leader in control  > > > > systems. > > > > I > > > > HP can not do this alone, we the user community, need to get some N > > > > backbone and start standing up to the ISVs.  It would seem that we canN > > > > demonstrate to HP that it would behoove them to give us better supportP > > > > if we joined together in the effort to increase the visibility of VMS asO > > > > an entity and shout from the rooftops that it is alive and viable. This  > > > > also is good business. > > > >  > > > > Have Fun,  > > > > TW Heim Jr.  > > > > twhjr@HeimNet.com  > > > > www.HeimNet.com  > > > > OpenVMS.HeimNet.com  > > > > " > > > > -----Original Message-----8 > > > > From: John Zimmerman [mailto:johnz@DIGITASK.COM]2 > > > > Sent: Wednesday, November 08, 2006 9:16 AM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > > J > > > > It seems to me that the reason "it is incumbent on the folks at HP > > > > OpenVMS"M > > > > is the same reason as it is the responsibility for the folks as HP-UX L > > > > and other Integrity based groups -- it is or should be part of their > > > > marketing efforts. > > > > O > > > > Unless the folks at HP are taking the position that OpenVMS is purely a K > > > > legacy operating system and not one which is worth any marketing to I > > > > create incentives for current AlphaVMS and new applications to be B > > > > developed for Integrity, then it is at least in part theirG > > > > responsibility to promote the O/S.  I believe they do take this M > > > > responsibility seriously (even if it might be under-funded) as I just O > > > > returned from a DSPP workshop on Itanium development which included all  > > > > four supported O/Ses.  > > > >  > > > >  > > > > John Zimmerman" > > > > Digitask Consultants, Inc. > > > >  > > > >  > > > >  > > > >  > > > >  > > > > Join my Tribe friends " > > > > -----Original Message-----@ > > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]2 > > > > Sent: Wednesday, November 08, 2006 8:45 AM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Greetings, > > > > E > > > > OK, but... How so is it incumbent on the folks at HP OpenVMS?  > > > >  > > > > Have Fun,  > > > > TW Heim Jr.  > > > > twhjr@HeimNet.com  > > > > www.HeimNet.com  > > > > OpenVMS.HeimNet.com  > > > > " > > > > -----Original Message-----< > > > > From: David J Dachtera [mailto:djesys@EARTHLINK.NET]1 > > > > Sent: Tuesday, November 07, 2006 10:41 PM , > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > > N > > > > If not "incumbent on the folks at HP OpenVMS", then who? (...incumbent > > > > upon > > > > whom?) > > > >  > > > > D.J.D. > > > > " > > > > -----Original Message-----@ > > > > From: Heim, Thomas W [mailto:heimtw@EXCHPTC1.SWITCH.COM]0 > > > > Sent: Tuesday, November 07, 2006 3:50 PM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Greetings, > > > > P > > > > I suppose that the *currently* "might" be implied but it would be better( > > > > if it where stated that clearly. > > > > 8 > > > > "incumbent on the folks at HP OpenVMS"?  How so? > > > >  > > > > Have Fun,  > > > > TW Heim Jr.  > > > > twhjr@HeimNet.com  > > > > www.HeimNet.com  > > > > OpenVMS.HeimNet.com  > > > > " > > > > -----Original Message-----< > > > > From: bradhamilton [mailto:bradhamilton@COMCAST.NET]0 > > > > Sent: Tuesday, November 07, 2006 4:43 PM, > > > > To: VMS-SIG@LISTSERV.ENCOMPASSUS.ORG+ > > > > Subject: Re: OpenVMS Support Issues  > > > >  > > > > Heim, Thomas W wrote:  > > > > > Greetings,	 > > > > > 	 > > > > > 	 > > > > > + > > > > > Slide 4 and 6 seem a bit at odds?  > > > > O > > > > I don't see a conflict - Cerner on OpenVMS/Integrity is not *currently* P > > > > supported, and they will re-evaluate the situation when they test Oracle > > > > # > > > > 10gR2 on OpenVMS/Integrity.  > > > > O > > > > If this is all just a misunderstanding, it is incumbent on the folks at 2 > > > > HP OpenVMS to rectify the situation, soon. > > > >  > > > F > > > I think that it would be even more constructive for everyone whoI > > > writes HP management a letter to set it aside for 24 hours, go back K > > > and look it over with fresh eyes, and then mail it if changes are not  > > > deemed to be necessary.  > > >  > > > For the same reasons.  >  > 
 > Face it. > A > Support wil be and continue to be MUCH worse. You can't replace  > hundreds of DeccieH > VMS support people with 20 or 30 years of tough, real world experienceE > with people in India with a few months of training, that can't even  > communicate. > I > Moving to higher level contracts won't work.  The support will still be H > much worse. There will be compression of all issues, as the few peopleI > still there that know VMS will be working on calls that would have been - > expertly worked on by the departed Deccies.  > G > And of course, we are no longer dealing with an ethical company.  Dec H > was a company based on ethics and quality.  It was a company one could > be proud of. > E > HP was once a great company too.  Now, the world slimeball comes to H > mind. It's sad that so many great people still work there. You can betH > the support staff will not get the support they need.  Management that@ > can replace experts with newbies in India does not value their. > employees, their customers or their product. > C > Now we see on their sites it says "We value your privacy.".  Does  > anyone believe them?F > When someone already has demonstrated a complete lack of ethics, can > you trust them for anything? > F > VMS is still great. And there still are lots of great VMS people and > applications.  > B > We can direct that our money be moved elsewhere. There are otherF > organizations that will support VMS. Make sure that HP knows why theE > big money is being spent elsewhere.  Just like a bad dog, rub it in G > their noses.  And, please not at the engineer and support level.  Get G > good examples of the types of support, sales and elevation issues you H > run into. Don't blame it on the poor techie in India, it's not his/her > fault. > H > The best thing would be if HP sells OpenVMS. They know of course, thatF > allowed to compete in the real marketplace, it would be a gem again. >  >   ' As Bill Cosby used to say-  LookDammit!   ? Sue asked for something specific and you just spit in her face.   - Thanks a lot.  Your post really helps things.   C Most of the time my issues are hardware-related.  I either send the B onsite guy an email or I walk downstairs to his office and we talk# about it.  Or I just fix it myself.   E I only call support on OS or "software" issues once or twice a month- E it's usually when I find something isn't behaving the way TFM says it 5 should, or something *seriously* obscure is involved.   ( I reiterate what I've posted previously.   Write Sue.  Politely.    Write Mr. Hurd.  Politely.   Write Ann McQuaid.  Politely.   1 Write each and every member of the BOD, politely.   C Especially the outside directors- as the Corporate Rule is that the E inside folks tend to listen when the outside directors are saying, "I 4 got a bunch of letters about this- WTF is going on?"  % Don't just rant, you'll be dismissed.   ) Sue, as usual, is right.  Give specifics.   E I have received follow-up calls which were clearly different that the E typical "on a scale of 1 to 5, with 1 being highly dissatisfied and 5 A being highly satisfied, please rate....---that we've all done for C years-- on about 75 percent of the calls that I've placed that have  been routed offshore.   D Remember, from the DECozoic Era through the Middle Compaq Period andC even unto the present day, there is an extensive history of Surveys D Being Important, and those of you who have been On Medallion Support& for years know what I'm talking about.  P If you bitch about offshoring per se, you will probably be dismissed as a bigot.F And perhaps rightly so, although I don't know you personally (at least I *think* I don't.)   B I have been completely honest in my discussions on these follow-upF calls-  I don't give a rodent's posterior about where the support callB goes- I've dealt with DECfolk all over the world in the past-- theC pertinent issue isn't the location of the support person-- it's the / level of training and resources that they have.   C Also, what I care about is that the service level has deteriorated-   C Where previously as a Gold Support customer, the call was taken and A then forwarded to my TAM, who then decided upon either personally @ owning the call and researching the issue, or referring it to an appropriate backline--  C Now after my call is taken, it is routed to a Tier 1 line where the ; level of knowledge is orders of magnitude less than my own, C communication is sometimes okay and sometimes, well, challenging...   E But to be honest, they're where my VMS level of knowledge was in 1990 F or so- and one of the things that burns me up is that it takes fifteen7 or twenty minutes to even get a case number these days.   E The people who are fielding these calls have neither the training nor B the expertise nor the access to certain in-house resources (STARS,? anyone? or whatever it's called these days) to field calls from E people, who, on average, have from fifteen to fifty times as much VMS  experience as they do.  A It's not fair to us and it's not fair to them, either.  It's like  lambs to the slaughter.   M I know what's going on when I'm told that I'll get a callback in ten minutes.   E This is the support equivalent of reducing the pound bag of coffee to  11 1/2 ounces.  A And once the experience and knowledge is lost, it can't be gotten = back.  That already happened with a StorageWorks design team.   4 And a knowledgebase is no substitute for experience.  # WWWebb, speaking purely for myself.    ------------------------------  + Date: Mon, 20 Nov 2006 13:55:06 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched2 Message-ID: <06112013550616_2020028F@antinode.org>  ' From: Dave Froble <davef@tsoft-inc.com>    > >> Gremlin wrote:  > >>> [...] H > >>> debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config > >>> [...]   J > Well then, is there a config?  I'd guess that without being able to get I > config data, the product will not work.  "Unable to open" seems pretty   > clear.  B    Seems clear, but don't be misled.  On my system, I get the sameB message (give or take an image ident, as I'm at TCPIP V5.4 ECO 6):   alp $ ssh -vP debug: Ssh2/SSH2.C:1906: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0 3 K debug: SshAppCommon/SSHAPPCOMMON.C:322: Allocating global SshRegex context. H debug: SshConfig/SSHCONFIG.C:3332: Metaconfig parsing stopped at line 4.L debug: SshConfig/SSHCONFIG.C:861: Setting variable 'VerboseMode' to 'FALSE'.B debug: SshConfig/SSHCONFIG.C:3240: Unable to open ssh2/ssh2_configF Type alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe -h for help.  = But it all works fine for me, as that's not a necessary file.   H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  % Date: Mon, 20 Nov 2006 14:30:28 -0800 * From: "Tom Linden" <tom@kednos-remove.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched) Message-ID: <op.tjb542d6tte90l@hyrrokkin>   F On Sun, 19 Nov 2006 22:12:12 -0800, Gremlin <not.here@all.mate> wrote:  L > Services started and enabled on an Alpha, can connect using FTP, Telnet,  L > web server running etc, scan shows port 22 open, but......I can't make a  
 > connection.  > L > Haven't played with the configuration files at all, would appreciate any   > suggestions.   works for me on 9 HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 5   > using PuTTY as client on Windows.  Which client are you using?     --  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------    Date: 20 Nov 2006 14:43:01 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedB Message-ID: <1164062581.563374.303500@m7g2000cwm.googlegroups.com>   Hello Steven  F Thanks for your assistance - I don't use my real name as I am a littleG shy - and I get plenty of spam already.....following is a more detailed G dump for you - but the dns names have been sanitised with the exception B of the name of the server - which is beta (I have another which is
 alpha)....
 $ ssh -v beta G debug: Ssh2/SSH2.C:1847: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is  V7.3-2-0 0 B debug: SshAppCommon/SSHAPPCOMMON.C:307: Allocating global SshRegex context.E debug: SshConfig/SSHCONFIG.C:3285: Metaconfig parsing stopped at line  3.C debug: SshConfig/SSHCONFIG.C:842: Setting variable 'VerboseMode' to  'FALSE'.B debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config6 debug: Connecting to beta, port 22... (SOCKS not used)- debug: Ssh2/SSH2.C:2813: Entering event loop. @ debug: Ssh2Client/SSHCLIENT.C:1607: Creating transport protocol.D debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "publickey" to usable methods. 5 debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added  "keyboard-interactive" to  usable methods. C debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "password" to  usable methods. ? debug: Ssh2Client/SSHCLIENT.C:1648: Creating userauth protocol. & debug: client supports 3 auth methods:) 'publickey,keyboard-interactive,password' F debug: SshUnixTcp/SSHUNIXTCP.C:1356: using local hostname beta.xxx.comD debug: Ssh2Common/SSHCOMMON.C:545: local ip = 192.168.100.201, local port = 4915  2 F debug: Ssh2Common/SSHCOMMON.C:547: remote ip = 192.168.100.201, remote	 port = 22 0 debug: SshConnection/SSHCONN.C:2277: Wrapping...? debug: SshReadLine/SSHREADLINE.C:3651: Initializing ReadLine... B debug: Ssh2Common/SSHCOMMON.C:184: DISCONNECT received: Connection closed by remote host.A debug: SshReadLine/SSHREADLINE.C:3717: Uninitializing ReadLine...  warning: Authentication failed. 0 debug: Ssh2/SSH2.C:316: locally_generated = TRUEB Disconnected; connection lost (Connection closed by remote host.).6 debug: Ssh2Client/SSHCLIENT.C:1683: Destroying client.B debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki != NULL,
 user_pki = NU  LL) ? debug: SshConnection/SSHCONN.C:2329: Destroying SshConn object. @ debug: Ssh2Client/SSHCLIENT.C:1751: Destroying client completed.; debug: SshAuthMethodClient/SSHAUTHMETHODC.C:104: Destroying  authentication metho d array.? debug: SshAppCommon/SSHAPPCOMMON.C:320: Freeing global SshRegex  context.A debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki = NULL,  user_pki = NUL L)  B So, as you can see, I am trying to make an ssh connection with theG client on the same node as the server.  I have also tried using various E windows-based ssh clients and get the same result.  I thought that if = it can't work locally, its not going to work remotely either!   C Have rebooted the server, cleaned directories, tried running from a # windows client to the alpha etc....    Cheers   Steven M. Schweda wrote:# > From: Gremlin <not.here@all.mate>  > B >    People with names tend to get more help than those with none. >  > > 2. [SYSMGR] > ssh -v	 > > [...]  > G >    "ssh -v host_name" would tell us more.  The messages from a _bare_ ' > "ssh -v" command are not very useful.  > L > > 3.  Again, don't know - I was hoping that (according to my readin of theL > > manual), it would find that I had no public key and therefore prompt for+ > > a password.  It doesn't,  I just get...  > > # > > warning: Authentication failed. F > > Disconnected; connection lost (Connection closed by remote host.). > > E > > So, I am not authenticating but neither am I being prompted for a L > > password - and this is doing an ssh on the alpha where the ssh server is > > installed. > H >    It might help to know what your local host and remote host are.  InJ > my (limited) experience, this stuff behaves approximately as documented.G > That is, I've gotten the password prompt(s) when other authentication  > methods fail.  >  > I > > The keys are created in the system area, I copied the server's public F > > key to a [.hostkeys] subdir in my sys$login, protection is s:rewd, > > o:rwed, g:re, w:r  > J >    The [.hostkeys] directory should be [.ssh2.hostkeys] under SYS$LOGIN,B > and the SSH software should hanlde that one on its own.  And theJ > typical protection of the files therein is "(RWD,RWD,,)", and there is aJ > non-obvious naming convention for them ("KEY_22_SHELL_VISI_COM.PUB", forE > example, for "shell.visi.com"), so it's probably best not to fiddle  > around in there. > L > > Um, well no - from the prompt I do ssh nodename and I get the connection5 > > refused message.  No password prompt, no nothing.  > E >    And what is at "nodename", and what, exactly, is the message?  A G > "connection refused message" normally means that there's no server at D > the other end.  Other messages normally mean other things.  ActualJ > messages generally mean more than vague descriptions of actual messages. >  >    Things which might help:  > = >       0. Cleaning out any spurious [.hostkeys] directories.  > I >       1. Descriptions of the two systems, local and remote.  (So far, I > > know that one of them is a VMS system, which is not enough.) > ; >       2. A transcript of an "ssh -v remote_host" session.  > J > ------------------------------------------------------------------------ > 5 >    Steven M. Schweda               sms@antinode-org 6 >    382 South Warwick Street        (+1) 651-699-9818 >    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 14:45:30 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164062730.931810.304160@j44g2000cwa.googlegroups.com>    Hi Tom  G SSH secure shell client (free) v3.2.9, then just from the prompt on the F same node as the server.  I know it should work out of the box, but it
 just won't :)    Cheers   Tom Linden wrote: H > On Sun, 19 Nov 2006 22:12:12 -0800, Gremlin <not.here@all.mate> wrote: > L > > Services started and enabled on an Alpha, can connect using FTP, Telnet,L > > web server running etc, scan shows port 22 open, but......I can't make a > > connection.  > > L > > Haven't played with the configuration files at all, would appreciate any > > suggestions. >  > works for me on ; > HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 5  > @ > using PuTTY as client on Windows.  Which client are you using? >  >  > --G > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------  % Date: Mon, 20 Nov 2006 15:32:20 -0800 * From: "Tom Linden" <tom@kednos-remove.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched) Message-ID: <op.tjb8z6lktte90l@hyrrokkin>   I On Mon, 20 Nov 2006 14:45:30 -0800, Milton <milton.baar@gmail.com> wrote:    > Hi Tom > I > SSH secure shell client (free) v3.2.9, then just from the prompt on the H > same node as the server.  I know it should work out of the box, but it > just won't :)   , Not familiar with that, what does it run on?   What do you see to $ tcpip show service   >  > Cheers >  > Tom Linden wrote: I >> On Sun, 19 Nov 2006 22:12:12 -0800, Gremlin <not.here@all.mate> wrote:  >>G >> > Services started and enabled on an Alpha, can connect using FTP,   
 >> Telnet,H >> > web server running etc, scan shows port 22 open, but......I can't  	 >> make a  >> > connection. >> >K >> > Haven't played with the configuration files at all, would appreciate    >> any >> > suggestions.  >> >> works for me on< >> HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 5 >>A >> using PuTTY as client on Windows.  Which client are you using?  >> >> >> -- H >> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >        --  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------  + Date: Mon, 20 Nov 2006 17:06:05 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched2 Message-ID: <06112017060583_2020028F@antinode.org>  & From: "Milton" <milton.baar@gmail.com>   > $ ssh -v beta R > debug: Ssh2/SSH2.C:1847: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0 > 0 M > debug: SshAppCommon/SSHAPPCOMMON.C:307: Allocating global SshRegex context. J > debug: SshConfig/SSHCONFIG.C:3285: Metaconfig parsing stopped at line 3.N > debug: SshConfig/SSHCONFIG.C:842: Setting variable 'VerboseMode' to 'FALSE'.D > debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config8 > debug: Connecting to beta, port 22... (SOCKS not used)/ > debug: Ssh2/SSH2.C:2813: Entering event loop. B > debug: Ssh2Client/SSHCLIENT.C:1607: Creating transport protocol.R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "publickey" to usable meth > ods.Q > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "keyboard-interactive" to  > usable methods. R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "password" to usable metho > ds. A > debug: Ssh2Client/SSHCLIENT.C:1648: Creating userauth protocol. ( > debug: client supports 3 auth methods:+ > 'publickey,keyboard-interactive,password' H > debug: SshUnixTcp/SSHUNIXTCP.C:1356: using local hostname beta.xxx.comR > debug: Ssh2Common/SSHCOMMON.C:545: local ip = 192.168.100.201, local port = 4915 > 2 R > debug: Ssh2Common/SSHCOMMON.C:547: remote ip = 192.168.100.201, remote port = 222 > debug: SshConnection/SSHCONN.C:2277: Wrapping...A > debug: SshReadLine/SSHREADLINE.C:3651: Initializing ReadLine... R > debug: Ssh2Common/SSHCOMMON.C:184: DISCONNECT received: Connection closed by rem > ote host. C > debug: SshReadLine/SSHREADLINE.C:3717: Uninitializing ReadLine... ! > warning: Authentication failed. 2 > debug: Ssh2/SSH2.C:316: locally_generated = TRUED > Disconnected; connection lost (Connection closed by remote host.).8 > debug: Ssh2Client/SSHCLIENT.C:1683: Destroying client.R > debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki != NULL, user_pki = NU > LL) A > debug: SshConnection/SSHCONN.C:2329: Destroying SshConn object. B > debug: Ssh2Client/SSHCLIENT.C:1751: Destroying client completed.R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:104: Destroying authentication metho
 > d array.J > debug: SshAppCommon/SSHAPPCOMMON.C:320: Freeing global SshRegex context.R > debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki = NULL, user_pki = NUL > L)  D > So, as you can see, I am trying to make an ssh connection with the( > client on the same node as the server.      So it appears.   # >   I have also tried using various G > windows-based ssh clients and get the same result.  I thought that if ? > it can't work locally, its not going to work remotely either!       Sounds reasonable to me.   B    When I do the same thing, we look similar for a while, and then diverge:   alp $ tcpip show version  ;   HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6 D   on a COMPAQ Professional Workstation XP1000 running OpenVMS V7.3-2   alp $ ssh "-V"P alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe: SSH Secure Shell OpenVMS (< V5.5) 3.2.0 on COMPAQ Professional Workstation  - VMS V7.3-2   alp $ ssh -v alpP debug: Ssh2/SSH2.C:1906: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0 3 K debug: SshAppCommon/SSHAPPCOMMON.C:322: Allocating global SshRegex context. H debug: SshConfig/SSHCONFIG.C:3332: Metaconfig parsing stopped at line 4.L debug: SshConfig/SSHCONFIG.C:861: Setting variable 'VerboseMode' to 'FALSE'.B debug: SshConfig/SSHCONFIG.C:3240: Unable to open ssh2/ssh2_config5 debug: Connecting to alp, port 22... (SOCKS not used) - debug: Ssh2/SSH2.C:2872: Entering event loop. @ debug: Ssh2Client/SSHCLIENT.C:1608: Creating transport protocol.B    [Here things start to differ, but not in obviously fatal ways.]P debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "hostbased" to usable met hods. P debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "publickey" to usable met hods. P debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "password" to usable meth ods.? debug: Ssh2Client/SSHCLIENT.C:1649: Creating userauth protocol. E debug: client supports 3 auth methods: 'hostbased,publickey,password' J debug: SshUnixTcp/SSHUNIXTCP.C:1378: using local hostname alp.antinode.orgJ debug: Ssh2Common/SSHCOMMON.C:546: local ip = 10.0.0.9, local port = 58480I debug: Ssh2Common/SSHCOMMON.C:548: remote ip = 10.0.0.9, remote port = 22 0 debug: SshConnection/SSHCONN.C:2290: Wrapping...? debug: SshReadLine/SSHREADLINE.C:3670: Initializing ReadLine... @    [Here, I continue happily, where you enter the fatal vortex.]P debug: Remote version: SSH-2.0-3.2.0 SSH Secure Shell OpenVMS V5.5 VMS_sftp_vers ion 2 $ debug: Major: 3 Minor: 2 Revision: 0F debug: Ssh2Transport/TRCOMMON.C:2268: lang s to c: `', lang c to s: `'O debug: Ssh2Transport/TRCOMMON.C:2333: c_to_s: cipher aes128-cbc, mac hmac-sha1,  compression noneO debug: Ssh2Transport/TRCOMMON.C:2336: s_to_c: cipher aes128-cbc, mac hmac-sha1,  compression none+ debug: Remote host key found from database.  [... more successful stuff ...]   F    Knowing little, I'd guess that the server dies in some way to causeF that "DISCONNECT received: Connection closed by remote host." message.  ;    You might look for interesting stuff in the log file(s): 0       SYS$SYSDEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG3 One of my successful run log files looks like this:   
 $ Set NoOn/ $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) A Mon 20 17:24:23 WARNING: Starting image in auxiliary server mode. 4 Mon 20 17:24:23 INFORMATIONAL: OpenVMS$gl_sockfd = 09 Mon 20 17:24:23 INFORMATIONAL: connection from "10.0.0.9" p Mon 20 17:24:23 WARNING: Error trying to access file /home_sms/sms/ssh2/knownhosts/alp_antinode_org_ssh-dss.pub.G    [No surprise, as I allow, but don't use, host-based authentication.] U Mon 20 17:24:24 NOTICE: Public key /home_sms/sms/ssh2/SMS_NPP_ID_DSA_1024_A.PUB used. H Mon 20 17:24:24 NOTICE: Public key authentication for user sms accepted.N Mon 20 17:24:24 NOTICE: User sms, coming from alp.antinode.org, authenticated.    [Normal logout here.]E Mon 20 17:24:30 INFORMATIONAL: Local disconnected: Connection closed. D Mon 20 17:24:30 INFORMATIONAL: connection lost: 'Connection closed.'8   TCPIP$SSH    job terminated at 20-NOV-2006 17:24:30.94     Accounting information: O   Buffered I/O count:                675      Peak working set size:       9280 O   Direct I/O count:                  321      Peak virtual size:         181632 O   Page faults:                       692      Mounted volumes:                0 O   Charged CPU time:        0 00:00:00.38      Elapsed time:       0 00:00:07.89     C    I changed my SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG file so:   H ALP $ diff /merg = 0 SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE .  ************: File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE;1 ******2 File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.;4F   164   AllowedAuthentications          hostbased, publickey, password ************ ************: File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE;1 ******2 File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.;4*   222   IgnoreRhosts                    no ************  & Number of difference sections found: 2% Number of difference records found: 2  [...]   B    The non-default "AllowedAuthentications" accounts for the earlyA differences between our messages.  I made a similar change to the 7 SSH2_CONFIG file, but I don't know if that one matters:   G ALP $ diff /merg = 0 SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.TEMPLATE  .  ************9 File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.TEMPLATE;1  ******1 File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.;2 F   131   AllowedAuthentications          hostbased, publickey, password ************  & Number of difference sections found: 1% Number of difference records found: 1  [...]   H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 16:03:27 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164067407.240696.262600@f16g2000cwb.googlegroups.com>    Ah ha!!    My logs show...   
 $ Set NoOn/ $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) 9 %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR  -CLI-E-IMGNAME, image file5 VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR.  EXE;1 @ -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag  e 8   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40  F So, it looks like the install may have not *really* worked - it should1 install the image as part of the install process.   G So, trash and rebuild VMS??  I have already disabled and re-enabled, it  obviously didn't help....sigh   A On Nov 21, 10:06 am, s...@antinode.org (Steven M. Schweda) wrote: ( > From: "Milton" <milton.b...@gmail.com> >  >  >  > > $ ssh -v beta T > > debug: Ssh2/SSH2.C:1847: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0 > > 0 O > > debug: SshAppCommon/SSHAPPCOMMON.C:307: Allocating global SshRegex context. L > > debug: SshConfig/SSHCONFIG.C:3285: Metaconfig parsing stopped at line 3.P > > debug: SshConfig/SSHCONFIG.C:842: Setting variable 'VerboseMode' to 'FALSE'.F > > debug: SshConfig/SSHCONFIG.C:3193: Unable to open ssh2/ssh2_config: > > debug: Connecting to beta, port 22... (SOCKS not used)1 > > debug: Ssh2/SSH2.C:2813: Entering event loop. D > > debug: Ssh2Client/SSHCLIENT.C:1607: Creating transport protocol.T > > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "publickey" to usable meth > > ods.S > > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "keyboard-interactive" to  > > usable methods. T > > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:99: Added "password" to usable metho > > ds. C > > debug: Ssh2Client/SSHCLIENT.C:1648: Creating userauth protocol. * > > debug: client supports 3 auth methods:- > > 'publickey,keyboard-interactive,password' J > > debug: SshUnixTcp/SSHUNIXTCP.C:1356: using local hostname beta.xxx.comT > > debug: Ssh2Common/SSHCOMMON.C:545: local ip = 192.168.100.201, local port = 4915 > > 2 T > > debug: Ssh2Common/SSHCOMMON.C:547: remote ip = 192.168.100.201, remote port = 224 > > debug: SshConnection/SSHCONN.C:2277: Wrapping...C > > debug: SshReadLine/SSHREADLINE.C:3651: Initializing ReadLine... T > > debug: Ssh2Common/SSHCOMMON.C:184: DISCONNECT received: Connection closed by rem
 > > ote host. E > > debug: SshReadLine/SSHREADLINE.C:3717: Uninitializing ReadLine... # > > warning: Authentication failed. 4 > > debug: Ssh2/SSH2.C:316: locally_generated = TRUEF > > Disconnected; connection lost (Connection closed by remote host.).: > > debug: Ssh2Client/SSHCLIENT.C:1683: Destroying client.T > > debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki != NULL, user_pki = NU > > LL) C > > debug: SshConnection/SSHCONN.C:2329: Destroying SshConn object. D > > debug: Ssh2Client/SSHCLIENT.C:1751: Destroying client completed.T > > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:104: Destroying authentication metho > > d array.L > > debug: SshAppCommon/SSHAPPCOMMON.C:320: Freeing global SshRegex context.T > > debug: SshConfig/SSHCONFIG.C:2745: Freeing pki. (host_pki = NULL, user_pki = NUL > > L)F > > So, as you can see, I am trying to make an ssh connection with the; > > client on the same node as the server.   So it appears.  > % > >   I have also tried using various I > > windows-based ssh clients and get the same result.  I thought that if \ > > it can't work locally, its not going to work remotely either!   Sounds reasonable to me. > D >    When I do the same thing, we look similar for a while, and then
 > diverge: >  > alp $ tcpip show version > = >   HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 6 F >   on a COMPAQ Professional Workstation XP1000 running OpenVMS V7.3-2 >  > alp $ ssh "-V"R > alp$dka0:[sys0.syscommon.][sysexe]tcpip$ssh_ssh2.exe: SSH Secure Shell OpenVMS (> > V5.5) 3.2.0 on COMPAQ Professional Workstation  - VMS V7.3-2 >  > alp $ ssh -v alpR > debug: Ssh2/SSH2.C:1906: CRTL version (SYS$SHARE:DECC$SHR.EXE ident) is V7.3-2-0 > 3 M > debug: SshAppCommon/SSHAPPCOMMON.C:322: Allocating global SshRegex context. J > debug: SshConfig/SSHCONFIG.C:3332: Metaconfig parsing stopped at line 4.N > debug: SshConfig/SSHCONFIG.C:861: Setting variable 'VerboseMode' to 'FALSE'.D > debug: SshConfig/SSHCONFIG.C:3240: Unable to open ssh2/ssh2_config7 > debug: Connecting to alp, port 22... (SOCKS not used) / > debug: Ssh2/SSH2.C:2872: Entering event loop. B > debug: Ssh2Client/SSHCLIENT.C:1608: Creating transport protocol.D >    [Here things start to differ, but not in obviously fatal ways.]R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "hostbased" to usable met > hods. R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "publickey" to usable met > hods. R > debug: SshAuthMethodClient/SSHAUTHMETHODC.C:101: Added "password" to usable meth > ods.A > debug: Ssh2Client/SSHCLIENT.C:1649: Creating userauth protocol. G > debug: client supports 3 auth methods: 'hostbased,publickey,password' L > debug: SshUnixTcp/SSHUNIXTCP.C:1378: using local hostname alp.antinode.orgL > debug: Ssh2Common/SSHCOMMON.C:546: local ip = 10.0.0.9, local port = 58480K > debug: Ssh2Common/SSHCOMMON.C:548: remote ip = 10.0.0.9, remote port = 22 2 > debug: SshConnection/SSHCONN.C:2290: Wrapping...A > debug: SshReadLine/SSHREADLINE.C:3670: Initializing ReadLine... B >    [Here, I continue happily, where you enter the fatal vortex.]R > debug: Remote version: SSH-2.0-3.2.0 SSH Secure Shell OpenVMS V5.5 VMS_sftp_vers > ion 2 & > debug: Major: 3 Minor: 2 Revision: 0H > debug: Ssh2Transport/TRCOMMON.C:2268: lang s to c: `', lang c to s: `'Q > debug: Ssh2Transport/TRCOMMON.C:2333: c_to_s: cipher aes128-cbc, mac hmac-sha1,  > compression noneQ > debug: Ssh2Transport/TRCOMMON.C:2336: s_to_c: cipher aes128-cbc, mac hmac-sha1,  > compression none- > debug: Remote host key found from database. ! > [... more successful stuff ...]  > H >    Knowing little, I'd guess that the server dies in some way to causeH > that "DISCONNECT received: Connection closed by remote host." message. > = >    You might look for interesting stuff in the log file(s): 2 >       SYS$SYSDEVICE:[TCPIP$SSH]TCPIP$SSH_RUN.LOG5 > One of my successful run log files looks like this:  >  > $ Set NoOn1 > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) C > Mon 20 17:24:23 WARNING: Starting image in auxiliary server mode. 6 > Mon 20 17:24:23 INFORMATIONAL: OpenVMS$gl_sockfd = 0; > Mon 20 17:24:23 INFORMATIONAL: connection from "10.0.0.9" r > Mon 20 17:24:23 WARNING: Error trying to access file /home_sms/sms/ssh2/knownhosts/alp_antinode_org_ssh-dss.pub.I >    [No surprise, as I allow, but don't use, host-based authentication.] W > Mon 20 17:24:24 NOTICE: Public key /home_sms/sms/ssh2/SMS_NPP_ID_DSA_1024_A.PUB used. J > Mon 20 17:24:24 NOTICE: Public key authentication for user sms accepted.P > Mon 20 17:24:24 NOTICE: User sms, coming from alp.antinode.org, authenticated. >    [Normal logout here.]G > Mon 20 17:24:30 INFORMATIONAL: Local disconnected: Connection closed. F > Mon 20 17:24:30 INFORMATIONAL: connection lost: 'Connection closed.': >   TCPIP$SSH    job terminated at 20-NOV-2006 17:24:30.94 >  >   Accounting information: Q >   Buffered I/O count:                675      Peak working set size:       9280 Q >   Direct I/O count:                  321      Peak virtual size:         181632 Q >   Page faults:                       692      Mounted volumes:                0 Q >   Charged CPU time:        0 00:00:00.38      Elapsed time:       0 00:00:07.89  > E >    I changed my SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG file so:  > J > ALP $ diff /merg = 0 SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE > .  > ************< > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE;1 > ******4 > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.;4H >   164   AllowedAuthentications          hostbased, publickey, password > ************ > ************< > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.TEMPLATE;1 > ******4 > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSHD2_CONFIG.;4, >   222   IgnoreRhosts                    no > ************ > ( > Number of difference sections found: 2' > Number of difference records found: 2  > [...]  > D >    The non-default "AllowedAuthentications" accounts for the earlyC > differences between our messages.  I made a similar change to the 9 > SSH2_CONFIG file, but I don't know if that one matters:  > I > ALP $ diff /merg = 0 SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.TEMPLATE  > .  > ************; > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.TEMPLATE;1  > ******3 > File SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SSH2_CONFIG.;2 H >   131   AllowedAuthentications          hostbased, publickey, password > ************ > ( > Number of difference sections found: 1' > Number of difference records found: 1  > [...]  > J > ------------------------------------------------------------------------ > 5 >    Steven M. Schweda               sms@antinode-org 6 >    382 South Warwick Street        (+1) 651-699-9818 >    Saint Paul  MN  55105-2547    ------------------------------  + Date: Mon, 20 Nov 2006 18:19:44 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched2 Message-ID: <06112018194483_2020028F@antinode.org>  & From: "Milton" <milton.baar@gmail.com>   > My logs show...  >  > $ Set NoOn1 > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) ; > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR R > -CLI-E-IMGNAME, image file VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR. > EXE;1 R > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag > e : >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40 > H > So, it looks like the install may have not *really* worked - it should3 > install the image as part of the install process.   E    Hmmm.  Around here, DECW$SETSHODISSHR seems to be installed by the ; DECwindows start-up stuff.  Are you not running DECwindows?   0 ALP $ search sys$manager:*.com DECW$SETSHODISSHR   ******************************, SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1  P $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header ''share_address_data'"   ******************************% SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1   P $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header  /protected''share_address_data'"  G    Is it possible that no one has tried SSH without DECwindows (or that E DECwindows is required, but that's not mentioned anywhere)?  (Or that ? it's required, _is_ mentioned, and I don't remember seeing that ( requirement?  I could believe that one.)  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 16:46:40 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164070000.056123.204310@b28g2000cwb.googlegroups.com>   A No DECwindows installed - and I couldn't find a dependency in the F manual - looks like I may have to start that as well!!  Stay tuned....  A On Nov 21, 11:19 am, s...@antinode.org (Steven M. Schweda) wrote: ( > From: "Milton" <milton.b...@gmail.com> >  > > My logs show...  >  > > $ Set NoOn3 > > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) = > > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR T > > -CLI-E-IMGNAME, image file VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR.	 > > EXE;1 T > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag > > e < > >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40 > J > > So, it looks like the install may have not *really* worked - it shouldz > > install the image as part of the install process.   Hmmm.  Around here, DECW$SETSHODISSHR seems to be installed by the= > DECwindows start-up stuff.  Are you not running DECwindows?  > 2 > ALP $ search sys$manager:*.com DECW$SETSHODISSHR >   > ******************************. > SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1 > R > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header > ''share_address_data'" >   > ******************************' > SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1  > R > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header" > /protected''share_address_data'" > I >    Is it possible that no one has tried SSH without DECwindows (or that G > DECwindows is required, but that's not mentioned anywhere)?  (Or that A > it's required, _is_ mentioned, and I don't remember seeing that * > requirement?  I could believe that one.) > J > ------------------------------------------------------------------------ > 5 >    Steven M. Schweda               sms@antinode-org 6 >    382 South Warwick Street        (+1) 651-699-9818 >    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 16:55:55 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164070555.259302.210010@h54g2000cwb.googlegroups.com>   A No DECwindows installed - and I couldn't find a dependency in the F manual - looks like I may have to start that as well!!  Stay tuned....  A On Nov 21, 11:19 am, s...@antinode.org (Steven M. Schweda) wrote: ( > From: "Milton" <milton.b...@gmail.com> >  > > My logs show...  >  > > $ Set NoOn3 > > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) = > > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR T > > -CLI-E-IMGNAME, image file VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR.	 > > EXE;1 T > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag > > e < > >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40 > J > > So, it looks like the install may have not *really* worked - it shouldz > > install the image as part of the install process.   Hmmm.  Around here, DECW$SETSHODISSHR seems to be installed by the= > DECwindows start-up stuff.  Are you not running DECwindows?  > 2 > ALP $ search sys$manager:*.com DECW$SETSHODISSHR >   > ******************************. > SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1 > R > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header > ''share_address_data'" >   > ******************************' > SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1  > R > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header" > /protected''share_address_data'" > I >    Is it possible that no one has tried SSH without DECwindows (or that G > DECwindows is required, but that's not mentioned anywhere)?  (Or that A > it's required, _is_ mentioned, and I don't remember seeing that * > requirement?  I could believe that one.) > J > ------------------------------------------------------------------------ > 5 >    Steven M. Schweda               sms@antinode-org 6 >    382 South Warwick Street        (+1) 651-699-9818 >    Saint Paul  MN  55105-2547    ------------------------------  % Date: Mon, 20 Nov 2006 19:47:14 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched7 Message-ID: <38d99$45624c82$cef8887a$8380@TEKSAVVY.COM>   
 Milton wrote:  > -CLI-E-IMGNAME, image file7 > VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR.  > EXE;1 B > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run > privileged imag     J The "installation" here is not a software installation. It is the INSTALL H utility in VMS which builds a table of known executable files and gives D them known attributes and lock those files to prevent any tampering.  L For instance, the SSH server side software probably needs big privileges in @ order to perform its duties on behalf of your username. This is G accomplished by INSTALling that image with privileges. Once installed,    nobody can tamper with the file.  .  From the SYSTEM account, you may wish to try:   @SYS$MANAGER:TCPIP$SSH_STARTUP  I This should generally get the require images setup, the required logical  H names setup etc. This would normally be automatically executed when you J start the TCPIP stack when you boot your system, but if you only recently B configured it without a reboot, the startup may not have executed.   ------------------------------    Date: 20 Nov 2006 17:08:26 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedA Message-ID: <1164071306.229197.73870@m7g2000cwm.googlegroups.com>   
 SOLVED!!!!  E Thanks everyone for you help and suggestions, especially those lately 5 who rode on the shoulders of the earlier suggestions.   G As JF and Steven noted, DECwindows is somehow tied up in this - I can't D find a link using a quick search through the manuals (so much easier@ than the old days with microfiche....),  but the solution was to= install DECW$SETSHODISSHR.EXE as /open/head/shar/priv=sysprv.   G Voila!!  It springs to life and I get the password prompt, key exchange   and life returns to normal(ish).  > Once again, thanks to all and maybe I should consider actually& installing DECwindows at some time....   Cheers  < On Nov 21, 11:46 am, "Milton" <milton.b...@gmail.com> wrote:C > No DECwindows installed - and I couldn't find a dependency in the H > manual - looks like I may have to start that as well!!  Stay tuned.... > C > On Nov 21, 11:19 am, s...@antinode.org (Steven M. Schweda) wrote:  > * > > From: "Milton" <milton.b...@gmail.com> >  > > > My logs show...  >  > > > $ Set NoOn5 > > > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) ? > > > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR V > > > -CLI-E-IMGNAME, image file VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR. > > > EXE;1 V > > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag > > > e > > > >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40 > L > > > So, it looks like the install may have not *really* worked - it should| > > > install the image as part of the install process.   Hmmm.  Around here, DECW$SETSHODISSHR seems to be installed by the? > > DECwindows start-up stuff.  Are you not running DECwindows?  > 4 > > ALP $ search sys$manager:*.com DECW$SETSHODISSHR > " > > ******************************0 > > SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1 > T > > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header > > ''share_address_data'" > " > > ******************************) > > SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1  > T > > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header$ > > /protected''share_address_data'" > K > >    Is it possible that no one has tried SSH without DECwindows (or that I > > DECwindows is required, but that's not mentioned anywhere)?  (Or that C > > it's required, _is_ mentioned, and I don't remember seeing that , > > requirement?  I could believe that one.) > L > > ------------------------------------------------------------------------ > 7 > >    Steven M. Schweda               sms@antinode-org 8 > >    382 South Warwick Street        (+1) 651-699-9818! > >    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 17:10:00 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedB Message-ID: <1164071400.379645.79620@j44g2000cwa.googlegroups.com>  
 SOLVED!!!!  E Thanks everyone for you help and suggestions, especially those lately 5 who rode on the shoulders of the earlier suggestions.   G As JF and Steven noted, DECwindows is somehow tied up in this - I can't D find a link using a quick search through the manuals (so much easier@ than the old days with microfiche....),  but the solution was to= install DECW$SETSHODISSHR.EXE as /open/head/shar/priv=sysprv.   G Voila!!  It springs to life and I get the password prompt, key exchange   and life returns to normal(ish).  > Once again, thanks to all and maybe I should consider actually& installing DECwindows at some time....   Cheers  < On Nov 21, 11:46 am, "Milton" <milton.b...@gmail.com> wrote:C > No DECwindows installed - and I couldn't find a dependency in the H > manual - looks like I may have to start that as well!!  Stay tuned.... > C > On Nov 21, 11:19 am, s...@antinode.org (Steven M. Schweda) wrote:  > * > > From: "Milton" <milton.b...@gmail.com> >  > > > My logs show...  >  > > > $ Set NoOn5 > > > $ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY")) ? > > > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR V > > > -CLI-E-IMGNAME, image file VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR. > > > EXE;1 V > > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged imag > > > e > > > >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40 > L > > > So, it looks like the install may have not *really* worked - it should| > > > install the image as part of the install process.   Hmmm.  Around here, DECW$SETSHODISSHR seems to be installed by the? > > DECwindows start-up stuff.  Are you not running DECwindows?  > 4 > > ALP $ search sys$manager:*.com DECW$SETSHODISSHR > " > > ******************************0 > > SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1 > T > > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header > > ''share_address_data'" > " > > ******************************) > > SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1  > T > > $ call decw$install_check "sys$share:decw$setshodisshr.exe" "/open/shared/header$ > > /protected''share_address_data'" > K > >    Is it possible that no one has tried SSH without DECwindows (or that I > > DECwindows is required, but that's not mentioned anywhere)?  (Or that C > > it's required, _is_ mentioned, and I don't remember seeing that , > > requirement?  I could believe that one.) > L > > ------------------------------------------------------------------------ > 7 > >    Steven M. Schweda               sms@antinode-org 8 > >    382 South Warwick Street        (+1) 651-699-9818! > >    Saint Paul  MN  55105-2547    ------------------------------    Date: 20 Nov 2006 17:18:43 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164071923.648695.275210@h54g2000cwb.googlegroups.com>    Hi JF   
 SOLVED!!!!  D Thanks to Tom, Steve and JF who also rode on the shoulders of othersG who provided advice and assistance.  The key was DECW$SETSHODISSHR.EXE, D I don't use DECwindows and the image wasn't installed but did exist.G SO, I installed it /open/head/shar/priv=sysprv and, voila!!  It springs  to life and now works fine.   > I did a quick search of the manuals (so much faster than usingG microfiche) but couldn't find any dependency metioned, so that is still 
 a mystery.   Thanks to all.   Cheers  C On Nov 21, 11:47 am, JF Mezei <jfmezei.spam...@teksavvy.com> wrote:  > Milton wrote:  > > -CLI-E-IMGNAME, image file9 > > VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR. 	 > > EXE;1 D > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run\ > > privileged imagThe "installation" here is not a software installation. It is the INSTALLI > utility in VMS which builds a table of known executable files and gives F > them known attributes and lock those files to prevent any tampering. > M > For instance, the SSH server side software probably needs big privileges in A > order to perform its duties on behalf of your username. This is H > accomplished by INSTALling that image with privileges. Once installed," > nobody can tamper with the file. > 0 >  From the SYSTEM account, you may wish to try: >   > @SYS$MANAGER:TCPIP$SSH_STARTUP > J > This should generally get the require images setup, the required logicalI > names setup etc. This would normally be automatically executed when you K > start the TCPIP stack when you boot your system, but if you only recently D > configured it without a reboot, the startup may not have executed.   ------------------------------  + Date: Mon, 20 Nov 2006 19:26:15 -0600 (CST) * From: sms@antinode.org (Steven M. Schweda)L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched2 Message-ID: <06112019261560_2020028D@antinode.org>  & From: "Milton" <milton.baar@gmail.com>   > SOLVED!!!!      What could go wrong?    > [...] but the solution was to ? > install DECW$SETSHODISSHR.EXE as /open/head/shar/priv=sysprv.   C    I'd say that that's _a_ solution, not _the_ solution, and that a , better solution would be to use the existingG SYS$MANAGER:DECW$INSTALL_IMAGES.COM and/or the succulent bits thereof.  > In mine, the options for "sys$share:decw$setshodisshr.exe" areB "/open/shared/header" (more or less), with no reference to SYSPRV.  , > [...] and maybe I should consider actually( > installing DECwindows at some time....  @    Probably.  Especially if everyone else expects it implicitly.  H ------------------------------------------------------------------------  3    Steven M. Schweda               sms@antinode-org 4    382 South Warwick Street        (+1) 651-699-9818    Saint Paul  MN  55105-2547    ------------------------------  % Date: Mon, 20 Nov 2006 17:54:30 -0800 * From: "Tom Linden" <tom@kednos-remove.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patched) Message-ID: <op.tjcfk4zvtte90l@hyrrokkin>   ! Here is what I have in my startup   5 HAFNER> sear SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM ssh ? $! 21-FEB-2006 AKD  Comment out tcpip anal mail, add install  =    DECW$SETSHODISSHR @ $! 23-DEC-2005 TLJL DECW$SETSHODISSHR added for TCPIP ECO 5 SSH2B $! 28-JUN-2004 TLJL Added TCPIP startupfor HAFNER !openssh startup- $ INSTALL ADD SYS$SHARE:DECW$SETSHODISSHR.EXE    That may do it for you.   I On Mon, 20 Nov 2006 16:55:55 -0800, Milton <milton.baar@gmail.com> wrote=  :   C > No DECwindows installed - and I couldn't find a dependency in the I > manual - looks like I may have to start that as well!!  Stay tuned....=    > C > On Nov 21, 11:19 am, s...@antinode.org (Steven M. Schweda) wrote: ) >> From: "Milton" <milton.b...@gmail.com>  >> >> > My logs show... >> >> > $ Set NoOn 6 >> > $ VERIFY =3D F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))> >> > %DCL-W-ACTIMAGE, error activating image DECW$SETSHODISSHR" >> > -CLI-E-IMGNAME, image file  =  8 >> VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR.
 >> > EXE;1H >> > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run  =   >> privileged imag >> > e= >> >   TCPIP$SSH    job terminated at 21-NOV-2006 09:54:57.40  >>I >> > So, it looks like the install may have not *really* worked - it sho=  uld I >> > install the image as part of the install process.   Hmmm.  Around  =   7 >> here, DECW$SETSHODISSHR seems to be installed by the > >> DECwindows start-up stuff.  Are you not running DECwindows? >>3 >> ALP $ search sys$manager:*.com DECW$SETSHODISSHR  >>! >> ****************************** / >> SYS$COMMON:[SYSMGR]DECW$INSTALL_IMAGES.COM;1  >>A >> $ call decw$install_check "sys$share:decw$setshodisshr.exe"  =    >> "/open/shared/header  >> ''share_address_data'"  >>! >> ****************************** ( >> SYS$COMMON:[SYSMGR]DECW$STARTUP.COM;1 >>A >> $ call decw$install_check "sys$share:decw$setshodisshr.exe"  =    >> "/open/shared/header # >> /protected''share_address_data'"  >>I >>    Is it possible that no one has tried SSH without DECwindows (or th=  atI >> DECwindows is required, but that's not mentioned anywhere)?  (Or that=   B >> it's required, _is_ mentioned, and I don't remember seeing that+ >> requirement?  I could believe that one.)  >>I >> ---------------------------------------------------------------------=  ---  >>6 >>    Steven M. Schweda               sms@antinode-org7 >>    382 South Warwick Street        (+1) 651-699-9818   >>    Saint Paul  MN  55105-2547 >        -- =  E Using Opera's revolutionary e-mail client: http://www.opera.com/mail/    ------------------------------    Date: 20 Nov 2006 18:11:05 -0800& From: "Milton" <milton.baar@gmail.com>L Subject: Re: Problem connecting to SSH, OpenVMS7.3-2, HP TCP/IP v5.4 patchedC Message-ID: <1164075065.360192.126110@b28g2000cwb.googlegroups.com>   
 SOLVED!!!!  E Thanks everyone for you help and suggestions, especially those lately 5 who rode on the shoulders of the earlier suggestions.   G As JF and Steven noted, DECwindows is somehow tied up in this - I can't D find a link using a quick search through the manuals (so much easier@ than the old days with microfiche....),  but the solution was to= install DECW$SETSHODISSHR.EXE as /open/head/shar/priv=sysprv.   G Voila!!  It springs to life and I get the password prompt, key exchange   and life returns to normal(ish).  > Once again, thanks to all and maybe I should consider actually& installing DECwindows at some time....   Cheers  C On Nov 21, 11:47 am, JF Mezei <jfmezei.spam...@teksavvy.com> wrote:  > Milton wrote:  > > -CLI-E-IMGNAME, image file9 > > VAX2$DKA0:[SYS0.SYSCOMMON.][SYSLIB]DECW$SETSHODISSHR. 	 > > EXE;1 D > > -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run\ > > privileged imagThe "installation" here is not a software installation. It is the INSTALLI > utility in VMS which builds a table of known executable files and gives F > them known attributes and lock those files to prevent any tampering. > M > For instance, the SSH server side software probably needs big privileges in A > order to perform its duties on behalf of your username. This is H > accomplished by INSTALling that image with privileges. Once installed," > nobody can tamper with the file. > 0 >  From the SYSTEM account, you may wish to try: >   > @SYS$MANAGER:TCPIP$SSH_STARTUP > J > This should generally get the require images setup, the required logicalI > names setup etc. This would normally be automatically executed when you K > start the TCPIP stack when you boot your system, but if you only recently D > configured it without a reboot, the startup may not have executed.   ------------------------------  % Date: Tue, 21 Nov 2006 05:19:44 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> 3 Subject: Re: Purpose of uppercasing a RUN command ? J Message-ID: <paul.sture.nospam-33E6AB.05194421112006@mac.sture.homeip.net>   In article  H <rdeininger-2011062157420001@dialup-4.233.128.17.dial1.manchester1.level 3.net>, 7  rdeininger@mindspringdot.com (Robert Deininger) wrote:   L > In article <paul.sture.nospam-883BE9.18072020112006@mac.sture.homeip.net>,2 > Paul Sture <paul.sture.nospam@hispeed.ch> wrote: >  > B > >This is what VMSINSTAL does (though not all in the same place): > >  > >$delete = "delete"  > >$delete/symbol/global/all > > H > >But that can be a pain in the neck, since you lose symbols set up in  > >your login procedure(s).  > J > IIRC, the main reason VMSINSTAL deletes all global symbols is to make asI > much memory available as possible.  The procedure wants a lot of symbol K > space, and on small-memory systems quotas are low enough that it matters.   I It's a looong time since I saw DCL run out of space for symbols, but now  6 that you've mentioned it, that could be a big problem.  H Nevertheless, after once installing some patches at a client and having I to answer "Y" for every file getting deleted (or was it purged?), it was   a welcome modification :-)   --  
 Paul Sture   ------------------------------  # Date: Mon, 20 Nov 2006 22:41:47 GMT # From: "FredK" <fred@nospam.dec.com> 7 Subject: Re: Question: Can anyone write device drivers/ 2 Message-ID: <Laq8h.2744$4k1.2201@news.cpqcorp.net>  5 "Dave Froble" <davef@tsoft-inc.com> wrote in message  3 news:OtudnWYBO8GkcfzYnZ2dnUVZ_sidnZ2d@libcom.com...  > Bart Z. Lederman wrote: ? >> Editing the SYS$CONFIG.DAT file to make the system recognize A >> one adaptor because it seems similar to another adaptor is not 9 >> a good thing to do (for fairly large values of "NOT").  >>  B Just a note... NEVER edit SYS$CONFIG.DAT - use SYS$USER_CONFIG.DAT  K Also a sub-note - to be more specific about a particular adapter - use the  M FLAGS = EXTENDED_ID and the use the full 64-bit device ID - the 32-bit ID is  C vendor/device, the other 32-bits are subsystem vendor and revision.   + As to the rest of the comments... seconded.    ------------------------------  % Date: Mon, 20 Nov 2006 14:33:06 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ( Subject: Re: Strategies for time offsets7 Message-ID: <b2390$456202e1$cef8887a$6760@TEKSAVVY.COM>    Stephen Hoffman wrote:F >   The OpenVMS quadword time format is not something I would tend to 4 > implement in new code (particularly for storage),   K I've neveer really stored time as the VMS quadword format. However, I find  I the $BINTIM , $NUMTIM and other formating routines to be very convenient  ' since they are well documented in help.   5 In my current case, I found an easy way to handle it.   L My data is in seconds since an arbritary date (DEC 31 1989 (GPS base time). D So after doing the $BINTIM of the various time zone offsets, I used J LIB$CVT_FROM_INTERNAL to produce longword delta seconds. Multiplied by -1  for time zones west of London.  H When processing the data, I just add the approrpiate offset (seconds to ; seconds) and afterwards I then convert it to VMS quadworth  K (LIB$CVT_TO_INTERNAL) and then add it to the GPS base time in VMS quadword.   I So not much of the program needed to be changed and the interface to the   routines remained the same.     F > or other such operation.  The (opaque) UTC format is often a better I > choice here, particularly when dealing with the storage of time values.   I Thanks for your pointer. Interesting reading. Sort of strange to have to  K re-learn VMS because the "real" VMS time routines are no longer recomended.     C >   The OpenVMS quadword time format and the delta time scheme was  H > certainly a good idea way back in 1976-1978, but there are better (or / > different) ways to do this sort of thing now.   E Actually, if the VMS quadword storage had separate bits for sign and  K delta/absolute, then it would have been very neat from a programming point   of view.  J And when VMS started keeping track of time zones, perhaps $CONVERT_TO_UTC F and $CONVERT_FROM UTC would have done an automatic math operation n a J quadword to add or remove the right number of units to the quadword based  on system logicals.     G > correct, however.  These offsets vary by time of year, these offsets  K > vary by year going back in time, and vary by the whim of whatever entity  C > has a perceived need to adjust the offsets going forward in time.   L Yeah. So far, I have been lucky in having a limited number of possible time L zones. Ideally, It would be neat to be able to call some routine, giving it J   lat, long and date and get back a UTC time offset. But that is a lot to E ask since there is no mathematical formula to get a time zone from a  K lat/long location. (think of all the jagged time zone lines, including the  ' intl dat line which is rather crooked).   I > With OpenVMS Alpha and OpenVMS I64 systems and compilers, you can also  J > use the compiler-integrated math operations; the built in quadword math.  L I know I *could*, but would rather not since it still alows me to run it on K VAX. (for instance, I am investigating my my math is giving a 3km distance  G difference, and I was able to run it on one of my vaxes as well as the  L alpha to compare the floating point operations just to see if it was due to F it now running on an alpha, but alas, no difference in calculations...  > >   I'd suggest optimizing these sorts of coding cases later.   J I am more concerned about reusability of code and ability to add features G without having to update all programs (aka: having a good structure to   begin with).  F > go-to example for frequent timezone changes -- have changed the DST I > switch-overs twice in recent years, once for the Olympics and once for  & > the Commonwealth Games.  Maybe more?  L Once in 1995. Victoria changed at a different time than New South Wales. On I the flight there, the FA/pilots weren't sure of the local time in Sydney  I before we landed and had to correct themselves a few times !  And when I  D booked, the reservation systems even had it wrong, listing a flight D duration as 15 minutes instead of 1:15 (because Sydney was ahead of F Melbourne by one hour that week).  And generally airlline reservation 2 systems are one trustable source of time zones....   ------------------------------    Date: 20 Nov 2006 15:04:37 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) / Subject: Using the VMS debugger with C pointers 3 Message-ID: <lNeR7r9+XW$B@eisner.encompasserve.org>   6 Using the VMS debugger for the C programming language, I have had no luck with    	DBG> examine local_ptr->  or 	DBG> examine local_ptr->* or 	DBG> examine local_ptr.*   @ How does one see all the fields in a structure referenced by the pointer ?  For Ada I say   	DBG> examine local_ptr.all    ------------------------------  % Date: Mon, 20 Nov 2006 16:22:41 -0500 1 From: "Farrell, Michael" <MFarrell@Voltdelta.com> 3 Subject: RE: Using the VMS debugger with C pointers L Message-ID: <085BCCCF596B684092B66310B1D3BA7D04703538@NJ103EX1.EAST.VIS.COM>  
 ex *local_ptr    (It's a pointer.) 
 Good luck.     Mike Farrell   -----Original Message-----7 From: Larry Kilgallen [mailto:Kilgallen@SpamCop.net]=20 ' Sent: Monday, November 20, 2006 4:05 PM  To: Info-VAX@Mvb.Saic.Com / Subject: Using the VMS debugger with C pointers   6 Using the VMS debugger for the C programming language, I have had no luck with    	DBG> examine local_ptr->  or 	DBG> examine local_ptr->* or 	DBG> examine local_ptr.*   @ How does one see all the fields in a structure referenced by the pointer ?  For Ada I say   	DBG> examine local_ptr.all    ------------------------------    Date: 20 Nov 2006 15:50:40 -0800- From: "Beach Runner" <Bob4Health@hotmail.com> F Subject: Re: What layered products are important for a VAX VMS system?A Message-ID: <1164066640.646262.78370@e3g2000cwe.googlegroups.com>    Bob Koehler wrote:~ > In article <paul.sture.nospam-B52EF9.18334617112006@mac.sture.homeip.net>, Paul Sture <paul.sture.nospam@hispeed.ch> writes: > > I > > You could bash in the documentation with something more reliable, and , > > sort out the "Word format" bit later on. > F >    Exactly the point of using OpenOffice (more than just word, there/ >    is a standard for which fonts, ... I use).   F As someone that loved VAX 11-780s, many, many, many years ago, I can'tF help really wondering why start it up. The power alone is absurd.  ForF the cost one could get something much smaller and faster, and still be a VAX.  E If it is a public university taking public funds, paying for licenses $ just would be real tough to justify.  D The only possible justification is to run something that can only be8 used on that specific hardware platform, as some ancientF legacy application.  In which, buying some type of compiler just can't make sense.   E Let's face it, this was the first generation VMS system. A classic. I D would LOVE the faceplate.   It wasn't even the "Performance Plus" of the 785.   ------------------------------  % Date: Tue, 21 Nov 2006 01:52:34 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> F Subject: Re: What layered products are important for a VAX VMS system?J Message-ID: <paul.sture.nospam-7DB984.01523421112006@mac.sture.homeip.net>  3 In article <sJnrGWBoW8pz@eisner.encompasserve.org>, =  koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote:   M > In article <paul.sture.nospam-B52EF9.18334617112006@mac.sture.homeip.net>,  3 > Paul Sture <paul.sture.nospam@hispeed.ch> writes:  > > J > > You could bash in the documentation with something more reliable, and , > > sort out the "Word format" bit later on. > F >    Exactly the point of using OpenOffice (more than just word, there/ >    is a standard for which fonts, ... I use).   G What I had in mind when I wrote the above was bashing the text in on a  * VMS system to get around Word crashing :-)  E But yes, OpenOffice should do the trick. I have had problems with it  H printing documents I regularly receive - I had to change fonts to get a I decent result. However, I am just trying out NeoOffice (OpenOffice with   . the OS X interface) and that problem is cured.   --  
 Paul Sture   ------------------------------  % Date: Tue, 21 Nov 2006 05:26:08 +0100 / From: Paul Sture <paul.sture.nospam@hispeed.ch> F Subject: Re: What layered products are important for a VAX VMS system?J Message-ID: <paul.sture.nospam-16BE4E.05260821112006@mac.sture.homeip.net>  0 In article <456275B6.F686DB9F@spam.comcast.net>,5  David J Dachtera <djesys.no@spam.comcast.net> wrote:    > Paul Sture wrote:  > > 7 > > In article <sJnrGWBoW8pz@eisner.encompasserve.org>, A > >  koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote:  > > P > > > In article <paul.sture.nospam-B52EF9.18334617112006@mac.sture.homeip.net>,7 > > > Paul Sture <paul.sture.nospam@hispeed.ch> writes:  > > > > M > > > > You could bash in the documentation with something more reliable, and 0 > > > > sort out the "Word format" bit later on. > > > J > > >    Exactly the point of using OpenOffice (more than just word, there3 > > >    is a standard for which fonts, ... I use).  > > J > > What I had in mind when I wrote the above was bashing the text in on a. > > VMS system to get around Word crashing :-) > ; > At the risk of sounding pro-M$, why not use Notepad then?  > " > ...or do you need a REAL editor?  D The EDT keypad layout wins here when bashing text in, not to forget G editor journalling. But yes, if it just a Word problem, Notepad should   suffice.   --  
 Paul Sture   ------------------------------    Date: 20 Nov 2006 15:38:42 -0800 From: bryan.s.a@gmail.com  Subject: Re: Who called me? C Message-ID: <1164065922.039894.314470@h54g2000cwb.googlegroups.com>    Stephen Hoffman wrote: > bryan.s.a@gmail.com wrote: > J > > My preference would be to see a post of code to obtain the module name3 > > in a variable although any help is appreciated.  > I >    Would you like all the module and call stack information (the entire F > run-time context, whatever symbols are available, etc) stored into aI > file?  From that file, you can then do whatever you want with the text, F > of course.  That file is feasible in exactly one line of code, usingJ > only supported interfaces, and it's portable across all three platforms,G > and most any available OpenVMS version, and it's easily customizable, F > and it works (more or less) as well whether compiled and linked withF > traceback as not (for whatever information is present in the image). > G >    It'll take a few extra lines of code and a very little work to get I > the information loaded into the application without using the file, but G > you can (obviously and easily ) pick a unique filename at run-time to C > reduce the changes of collisions should there be parallel logging J > activities running.  Or you could likely get the information loaded into > a mailbox. > 3 >    Would this line of code be of interest to you?  > H >    [Yes, I'm switching my approach to answering this question here, asH > I'm inferring that my previous approach here wasn't providing you with > what you wanted.]   E I have the following code for a test but haven't yet figured out what  to link it with successfully.    PROCEDURE DIVISION.    main_program SECTION.   
 0000_main.  ;         CALL "LIB$GET_CURR_INVO_CONTEXT" USING BY REFERENCE 
 invo_context. D         CALL "TBK$ALPHA_SYMBOLIZE" USING BY REFERENCE tbk_api_param.   END PROGRAM get_invo_info.  ! $ cobol/debug get_invo_info/noopt   $ link/trace/debug get_invo_info% %LINK-W-NUDFSYMS, 1 undefined symbol: + %LINK-I-UDFSYM,         TBK$ALPHA_SYMBOLIZE A %LINK-W-USEUNDEF, undefined symbol TBK$ALPHA_SYMBOLIZE referenced )         in psect $LINK$ offset %X00000070 $         in module GET_INVO_INFO file( DIGITAL:[ANDREWS_DEV]GET_INVO_INFO.OBJ;6  > Including sys$share:trace.exe/shareable gives a ton of errors:  > $ link/trace/debug get_invo_info,SYS$SHARE:TRACE.EXE/shareableG %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 1 is illegal  (3.)G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 2 is illegal  (1.)G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 3 is illegal  (0.)G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 4 is illegal  (54648.)G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 5 is illegal  (2524.) G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 6 is illegal  (32.) G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 7 is illegal  (5008.) G %LINK-W-RECTYP, file SYS$COMMON:[SYSLIB]TRACE.EXE;1 record 8 is illegal  (46080.)      .      .      ./ I'm wondering if the trace.exe file is corrupt.    $ dir sys$share:trace.exe    Directory SYS$COMMON:[SYSLIB]   = TRACE.EXE;1              883/896      19-OCT-2004 19:58:44.85     Total of 1 file, 883/896 blocks.   Any help is appreciated.  
 Thank You, -Bryan   ------------------------------  % Date: Mon, 20 Nov 2006 19:29:58 -0500 8 From: Stephen Hoffman <Hoff@HoffmanLabs-RemoveThis-.Org> Subject: Re: Who called me? ) Message-ID: <ejtha6$2jf3$1@pyrite.mv.net>    bryan.s.a@gmail.com wrote:  @ > $ link/trace/debug get_invo_info,SYS$SHARE:TRACE.EXE/shareable  F    I'd use a linker options file, and put the TRACE.EXE command there.  <    LINK/TRACE/DEBUG get_invo_info,ddcu:[dir]trace.opt/option  +    And over in trace.opt, there's the line:       ddcu:[dir]trace.exe/share  H    The /SHAREABLE on the command line doesn't do what you want here, as C it creates a shareable image as its output.  The /SHAREABLE in the  G options file references a shareable image for inclusion in the linking  0 operation.  [Confusing and inconsistent, yes...]  1 > I'm wondering if the trace.exe file is corrupt.   D    The file is not likely corrupt, but you could verify that with a H DIFFERENCES command against a known good copy; against the TRACE.EXE on K a distribution kit, or the version from the most recent associated ECO kit.   &    -- another approach, off the top --   #include <lib$routines.h>  #include <ssdef.h> #include <string.h>    main()    {"    char ascic_debug_commands[128];    char *dbgcmd = D "*set log ddcu:[dir]crash.dat;set output verify;show calls;go;exit";  *    strcpy( ascic_debug_commands, dbgcmd );9    ascic_debug_commands[0] = (char) strlen( dbgcmd ) - 1;   0    lib$signal(SS$_DEBUG,1,ascic_debug_commands);      return 1;    }   ------------------------------   End of INFO-VAX 2006.640 ************************