1 INFO-VAX	Sat, 05 May 2001	Volume 2001 : Issue 251       Contents:H AlphaServer GS-Series 1GHz Upgrade, ES45, DS25, European VMS Forums, etc3 Re: Compaq OpenVMS and Digital Networks Partnership  Re: Global delete in UAF?  Re: Global delete in UAF?  Re: Glue for a BA356-KC  Re: LDAP on OpenVMS  Re: RADIUS for OpenVMS ?P Re: The DFWCUG's DFWDAYS 2001 Presentations are online (as well as a few  photosP Re: The DFWCUG's DFWDAYS 2001 Presentations are online (as well as a few  photos VAX vs AXP executable  Re: VAX vs AXP executable  Re: VAX vs AXP executable  Re: VAX vs AXP executable  Re: VAX vs AXP executable A [EVENT] Post =?iso-8859-1?Q?Z=FCrich?= seminar event registration   F ----------------------------------------------------------------------  # Date: Sat, 05 May 2001 11:35:36 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>Q Subject: AlphaServer GS-Series 1GHz Upgrade, ES45, DS25, European VMS Forums, etc = Message-ID: <cARI6.14565$V%6.4745210@typhoon.ne.mediaone.net>   K Mike Magee has posted a reprint of an SKC AlphaServer Diamond Forum article  on The Inquirer at:   ' http://www.theinquirer.net/05050103.htm   K The article contains information on the subject platforms and events. Check  it out.    terry s  -- Terry C. Shannon Consultant and Publisher Shannon Knows Compaq  email: terryshannon@mediaone.net$ Web (info on SKC):  www.acersoft.com   ------------------------------  % Date: Sat, 05 May 2001 18:28:04 +0100 + From: "antonio.carlini" <arcarlini@iee.org> < Subject: Re: Compaq OpenVMS and Digital Networks Partnership' Message-ID: <3AF43824.16AA4933@iee.org>    "Barry Treahy, Jr." wrote: >  > Dirk Munk wrote: > Q > > And wouldn't it be nice if Digital Networks would also take over the good old S > > DecNis ? There is no replacement for that product, except for a Unix/VMS system  > > setup as a router/gateway. > U > Why stop there?  Why not include the VAX lines,  Alpha's... Better yet, VMS too and   > they could call the company...) >     ...Digital Equipment Corporation...   6 DNPG certainly have the rights to use the Digital name4 (even for new kit they design and build themselves).  1 I believe (but I'm not 100% sure) that they have  0 that right exclusively for some period of time, / so in some sense they already *are* Digital :-)   1 VAXes, Alphas and OpenVMS are all still supported , by COMPAQ (although there will be no new VAX hardware ...).   Antonio      --     --------------- - Antonio Carlini             arcarlini@iee.org    ------------------------------  % Date: Sat, 05 May 2001 07:56:58 -0400   From: Kuff@Tessco.Com (Hal Kuff)" Subject: Re: Global delete in UAF?O Message-ID: <7EF099BEEFAD9D26.0DF87F3442E45644.DBCAAF52BB0D1FB8@lp.airnews.net>   G From sys$system do a List */Br in Authorize and copy the .lis file into I your directory, then edit out the accounts that you do not want to effect C (system stuff and accounts for installed products like Rdb.. you'll J know).. then modify and run this, it will produce a command file that will do what you want     Bud:Kuff> ty sysuaf.com  $ Start:  $       Open/Read Foo Sysuaf.Lis) $       Open/Write Foo1 Change_Sysuaf.Com ) $       Write Foo1 "$ Set Def Sys$System" $ $       Write Foo1 "$ Mcr Authorize" $       Write Foo1 "$ Deck"  $ Loop:  $       Read/End=Done Foo Stuff & $       Stuff = F$Extract(10,14,Stuff), $       Write Foo1 "Mod/Priv=NoAll " + Stuff/ $       Write Foo1 "Mod/DefPriv=NoAll " + Stuff 6 $       Write Foo1 "Mod/Priv=(Tmpmbx,Netmbx) " + Stuff9 $       Write Foo1 "Mod/DefPriv=(Tmpmbx,Netmbx) " + Stuff  $       Goto Loop  $ Done:  $       Close Foo  $       Close Foo1 $ Exit                  J In article <gurman-E1A50F.18045804052001@skates.gsfc.nasa.gov>, "Joseph B.% Gurman" <gurman@gsfc.nasa.gov> wrote:   H > In article <cWEI6.19$tJ4.1133@client>, "Russ Leathe" <russ@goron.edu>  > wrote: > K > > I recently took over a VAX 4000 with about 500 user accounts.  Over the J > > years different priv were assigned including sysprv to the majority ofK > > users.  I can only assume that the person who created the accounts used  > > "copy" from a priv account.  > >  > > My question is...  > > N > > can I globally modify all these accounts and remove all priv except netmbx > > and tmpmbx?  > ? > If sysprv is the only one you want to get rid of, you can do:  >   > UAF> modify * /priv = nosysprv > E > though of course you'd then have to give it back to system, if you   > wanted system to have it.  > . >     Of course, that isn't what you asked.... >  >                   Joe Gurman >    ------------------------------  $ Date: Sat, 5 May 2001 13:44:26 +01001 From: "Chris Townley" <news@townleyc.demon.co.uk> " Subject: Re: Global delete in UAF?A Message-ID: <989066884.28029.0.nnrp-07.d4e45fa5@news.demon.co.uk>   " I they are grouped by UIC, you can  1 UAF> MODIFY [100,*] /priv=(NOALL,TMPMBX,NETMBX) -  /defpriv=NOALL,TMPMBX,NETMBX)   7 if they are in group 100, and likewise for other groups    --
 Chris Townley  chris@townleyc.demon.co.uk townleyc@spicers.ltd.uk     : "Joseph B. Gurman" <gurman@gsfc.nasa.gov> wrote in message9 news:gurman-E1A50F.18045804052001@skates.gsfc.nasa.gov... G > In article <cWEI6.19$tJ4.1133@client>, "Russ Leathe" <russ@goron.edu>  > wrote: > K > > I recently took over a VAX 4000 with about 500 user accounts.  Over the J > > years different priv were assigned including sysprv to the majority ofK > > users.  I can only assume that the person who created the accounts used  > > "copy" from a priv account.  > >  > > My question is...  > > G > > can I globally modify all these accounts and remove all priv except  netmbx > > and tmpmbx?  > ? > If sysprv is the only one you want to get rid of, you can do:  >   > UAF> modify * /priv = nosysprv > D > though of course you'd then have to give it back to system, if you > wanted system to have it.  > . >     Of course, that isn't what you asked.... >  >                   Joe Gurman >  > --E > | Joseph B. Gurman, NASA Goddard Space Flight Center, Solar Physics @ > | Branch, Greenbelt MD 20771 USA / Federal employees are stillB > | prohibited from holding opinions while at work. Therefore, any3 > | opinions expressed herein are  somebody else's.    ------------------------------  % Date: Sat, 05 May 2001 11:05:55 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)  Subject: Re: Glue for a BA356-KCL Message-ID: <rdeininger-0505011105550001@user-2iveci8.dialup.mindspring.com>  < In article <3AF31BB9.3FE9E0B@pressenter.com>, Lyndon Bartels  <lbartels@pressenter.com> wrote:   H > I have aquired a couple BA356-KC (pedestal) and while the shelf is notC > damaged, the "cap" and "door" have some breaks and/or cracks. Any E > recommendations on a glue that I can rely on to fix said cracks 'n'  > such? F > I tried superglue, and it held for a while... but not when put under > some stress.  H Try some epoxy from the hardware store.  Not the 5-minute stuff, but theE kind that cures in 12-24 hours.  That will hold on almost any sort of  plastic.   --   Robert Deininger rdeininger@mindspring.com    ------------------------------  * Date: Sat, 5 May 2001 10:46:49 +0000 (UTC)' From: david20@alpha2.mdx.ac.uk (D.Webb)  Subject: Re: LDAP on OpenVMS+ Message-ID: <9d0lmp$n71$1@aquila.mdx.ac.uk>   o In article <S4dTxley39dA@eisner.encompasserve.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes: _ >In article <tf5som7qdiq18@news.supernews.com>, wspencer@ap.nospam.org (Warren Spencer) writes: A >> munk@home.nl (Dirk Munk) wrote in <3AF2D1DD.5D6753FA@home.nl>:  >>  K >>>It is a (standard ?) part of VMS 7.3 (or maybe 7.3.1) AFAIK, so you just # >>>have to do a little upgrade :-))  >>>  >>>Toine Dirven wrote: >>>  >>>> Hello,  >>>>4 >>>> I'm running OpenVMS 7.2-1H1 on 7 alpha servers. >>>>+ >>>> Is it possible to use LDAP on OpenVMS.  >>>>. >>>> Are there any examples of LDAP on OpenVMS >>>> >>>> Best regards, >>>> >>>> Toine Dirven  >>  M >> There is a server side and client side to LDAP - which components are you  C >> seeking?  OpenVMS 7.3 is rumored to have an LDAP *client* in it.  >>  M >> My employer recently had a requirement for an LDAP client on OpenVMS, but  L >> since we're at 7.2-1, we had to persue other alternatives.  The somewhat J >> ineligant solution we chose was to talk over the network via HTTP to a N >> cgi/perl scipt on a Solaris box, which in turn issued the LDAP requests to O >> the server.  The advantage here was that a perl-based LDAP client is freely   >> available for Solaris.  > ? >Innosoft had an LDAP client product -- it is now owned by Sun.  >   I Innosoft had an LDAP server (IDDS) which is now sold and supported on VMS + by Process. This would work with VMS 7.2-1.   A However since as mentioned below VMS 7.3 includes an LDAP server  B (which I believe includes an unlimited entry license) I think most3 people will in future choose that rather than IDDS.   H I am pretty sure the Perl-LDAP module will work with Perl on VMS just asK well as it works on Solaris. (And the VMS webservers OSU, WASD etc support   Perl/CGI scripts).         F >An LDAP server has been built into the Compaq X.500 Directory ServiceF >effective with V4.0.  Effective with Alpha VMS V7.3 they are bundlingE >the licensing of that product with VMS, but to prevent it from being 7 >too widely used they have changed the product name :-)     A I believe VMS 7.3 also builds support directly into VMS for LDAP.  Providing various APIs.     
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Sat, 05 May 2001 17:44:28 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> ! Subject: Re: RADIUS for OpenVMS ? ) Message-ID: <3AF41FDC.71642852@gtech.com>     becherini@vortex.ufrgs.br wrote:> >         We know that it exists RADIUS (*) server for several- >         flavors of UNIX and Windows NT too.  > ) >         Do we have RADIUS for OpenVMS ?   B There are pointers at http://www.levitte.org/~ava/vms_inet.htmlx !   Arne   ------------------------------  # Date: Sat, 05 May 2001 10:59:28 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>Y Subject: Re: The DFWCUG's DFWDAYS 2001 Presentations are online (as well as a few  photos = Message-ID: <k2RI6.14520$V%6.4734202@typhoon.ne.mediaone.net>    > ( > "Brian Schenkenberger, VAXman-" wrote: > > H > > How is it that you boys in the DFWCUG can pull together your event's session K > > materials in a matter of days and get them published on the web and the  CETSH > > national event -- now 6 months and counting prior -- can't get their event's 2 > > sessions together and distributed as promised? >   G CETS2001 involves the coordination of resources from Encompass, several I entities within Compaq, and Compaq's event management staff and partners. I The logistics associated with a week-long event for 4-5K people are a bit I more daunting than the logistics associated with an event for 200 people, I especially when the latter event which is locally managed and controlled.   G To get an idea of what has gone into the making of CETS2001 so far, you K might want to take a look at the CETS2001 Core Content Advisory Team Report < at www.cets2001.com/privatedocs/CETS2001PhaseICATReport.doc.   ------------------------------  # Date: Sat, 05 May 2001 14:04:48 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) Y Subject: Re: The DFWCUG's DFWDAYS 2001 Presentations are online (as well as a few  photos 0 Message-ID: <009FB8D3.48534980@SendSpamHere.ORG>  t In article <k2RI6.14520$V%6.4734202@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes: >>) >> "Brian Schenkenberger, VAXman-" wrote:  >> >I >> > How is it that you boys in the DFWCUG can pull together your event's  >sessionL >> > materials in a matter of days and get them published on the web and the >CETS I >> > national event -- now 6 months and counting prior -- can't get their  >event's3 >> > sessions together and distributed as promised?  >> > H >CETS2001 involves the coordination of resources from Encompass, severalJ >entities within Compaq, and Compaq's event management staff and partners.J >The logistics associated with a week-long event for 4-5K people are a bitJ >more daunting than the logistics associated with an event for 200 people,J >especially when the latter event which is locally managed and controlled.  H I received a message from Jeff K. yesterday informing me that the CD wasI sent in Nov. 2000.  Yesterday, I also learned that my last month's Sprint H cell phone bill never arrived and thus it was never paid.  It seems thatI my US mail is about as reliable as a Micro$chlock Exstrange server at re- I liably delivering my mail. :(  I have to constantly wonder what OTHER im- 2 portant mail is trapped in the absolute elsewhere.  F Hopefully, a CD will be mailed to me shortly.  In the interim, anybodyF sending me anything via US mail would be wise to follow-up to see thatB I've actually received it!  I'll spare you all my rant on UPS!  :)   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  # Date: Sat, 05 May 2001 14:19:43 GMT $ From: Ed Wilts <ewilts@mediaone.net> Subject: VAX vs AXP executable< Message-ID: <3_TI6.23660$V6.1080190@typhoon.mn.mediaone.net>  L I'm about to retire the last of my Vaxes (he says with fond memories).   Is L there a relatively fast and easy way for me to identify a VAX executable as L opposed to an AXP exe?  I'm looking to write a script that will archive all  the old VAX exes.    Thanks,          .../Ed --   Ed Wilts, Mounds View, MN, USA mailto:ewilts@mediaone.net   ------------------------------  % Date: Sat, 05 May 2001 12:00:40 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)" Subject: Re: VAX vs AXP executableL Message-ID: <rdeininger-0505011200410001@user-2iveci8.dialup.mindspring.com>  E In article <3_TI6.23660$V6.1080190@typhoon.mn.mediaone.net>, Ed Wilts  <ewilts@mediaone.net> wrote:  N > I'm about to retire the last of my Vaxes (he says with fond memories).   Is N > there a relatively fast and easy way for me to identify a VAX executable as N > opposed to an AXP exe?  I'm looking to write a script that will archive all  > the old VAX exes.   ( $ analyze/image/interactive [.*]free.exe# This is an OpenVMS Alpha image file    IMAGE HEADER            Fixed Header Information  5                 image format major id: 3, minor id: 0 %                 header block count: 2 3                 image type: executable (EIHD$K_EXE)    <snip>  & ANALYZE/IMAGE/INTERACTIVE [.*]FREE.EXE! This is an OpenVMS VAX image file    IMAGE HEADER            Fixed Header Information  7                 image format major id: 02, minor id: 05 %                 header block count: 1 2                 image type: executable (IHD$K_EXE)    J You could capture the output of ANALYZE/IMAGE and look at the first line. > If you don't care about speed, that might be the simplest way.    H Or you could write a little program to open the file check pieces of theF image header.  Unfortunately, Vax and alpha image headers are arranged= differently, and I don't see a simple way to tell them apart.   > $ lib/extract=$eihddef/output=$eihddef.mar sys$library:lib.mlb< $ lib/extract=$ihddef/output=$ihddef.mar sys$library:lib.mlb  H These two .MAR files define the offsets and constanst for the fixed partG of the image header, for alpha and vax respectively.  Maybe if you dump J the first block of each kind of file, and compare to analyze/image, you'llI find a rule of thumb precise enough to tell the two kind of images apart.   F If you have the Internals and Data structures books, they describe the image headers in detail.  ; This looks like brute force, but I don't know a simple way.    --   Robert Deininger rdeininger@mindspring.com    ------------------------------  % Date: Sat, 05 May 2001 17:42:07 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> " Subject: Re: VAX vs AXP executable) Message-ID: <3AF41F4F.E5B771EB@gtech.com>    Ed Wilts wrote: M > I'm about to retire the last of my Vaxes (he says with fond memories).   IseM > there a relatively fast and easy way for me to identify a VAX executable as M > opposed to an AXP exe?  I'm looking to write a script that will archive alls > the old VAX exes.w   The image header is different.  A I have a piece of saved DCL that contains the following fragment:t   $       open/read f 'fnm'e $       read f imghdrL $       close fe9 $       vax = f$cvsi(0,32,f$extract(20,4,imghdr)) .eq. -1  $       if vax $       then   Arne   ------------------------------  # Date: Sat, 05 May 2001 16:32:53 GMTo= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)o" Subject: Re: VAX vs AXP executable0 Message-ID: <009FB8E7.F7B8C2F6@SendSpamHere.ORG>  c In article <3_TI6.23660$V6.1080190@typhoon.mn.mediaone.net>, Ed Wilts <ewilts@mediaone.net> writes: M >I'm about to retire the last of my Vaxes (he says with fond memories).   Is aM >there a relatively fast and easy way for me to identify a VAX executable as IM >opposed to an AXP exe?  I'm looking to write a script that will archive all c >the old VAX exes. >e >Thanks, >        .../Ed  >--  >Ed Wilts, Mounds View, MN, USAl >mailto:ewilts@mediaone.net   H $ PIPE ANALYZE/IMAGE <imagename>.EXE | SEA SYS$PIPE "This is an OpenVMS"   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             aO city, n., 1. a place where trees are cut down and streets are named after them.y   ------------------------------  # Date: Sat, 05 May 2001 16:36:26 GMT0= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)m" Subject: Re: VAX vs AXP executable0 Message-ID: <009FB8E8.76BCADF0@SendSpamHere.ORG>   In article <rdeininger-0505011200410001@user-2iveci8.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:wF >In article <3_TI6.23660$V6.1080190@typhoon.mn.mediaone.net>, Ed Wilts ><ewilts@mediaone.net> wrote:o >~O >> I'm about to retire the last of my Vaxes (he says with fond memories).   Is aO >> there a relatively fast and easy way for me to identify a VAX executable as cO >> opposed to an AXP exe?  I'm looking to write a script that will archive all o >> the old VAX exes. >5) >$ analyze/image/interactive [.*]free.exe $ >This is an OpenVMS Alpha image file >t
 >IMAGE HEADERo >s! >        Fixed Header Information  >l6 >                image format major id: 3, minor id: 0& >                header block count: 24 >                image type: executable (EIHD$K_EXE) >a ><snip>n >r' >ANALYZE/IMAGE/INTERACTIVE [.*]FREE.EXEs" >This is an OpenVMS VAX image file >e
 >IMAGE HEADER0 >i! >        Fixed Header Informatione >r8 >                image format major id: 02, minor id: 05& >                header block count: 13 >                image type: executable (IHD$K_EXE)  >K >oK >You could capture the output of ANALYZE/IMAGE and look at the first line.  ? >If you don't care about speed, that might be the simplest way.a >e >nI >Or you could write a little program to open the file check pieces of the0G >image header.  Unfortunately, Vax and alpha image headers are arrangedv> >differently, and I don't see a simple way to tell them apart. >A? >$ lib/extract=$eihddef/output=$eihddef.mar sys$library:lib.mlba= >$ lib/extract=$ihddef/output=$ihddef.mar sys$library:lib.mlbn >bI >These two .MAR files define the offsets and constanst for the fixed partoH >of the image header, for alpha and vax respectively.  Maybe if you dumpK >the first block of each kind of file, and compare to analyze/image, you'llrJ >find a rule of thumb precise enough to tell the two kind of images apart. >rG >If you have the Internals and Data structures books, they describe thep >image headers in detail.  >s< >This looks like brute force, but I don't know a simple way. >n >--  >Robert Deininger  >rdeininger@mindspring.com  	 ... or...o  J Read in the first longword of the file.  If it's "00000003", it's an Alpha/ image.  That shouldn't be too difficult in DCL.e   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM'            eO city, n., 1. a place where trees are cut down and streets are named after them.5   ------------------------------  % Date: Sat, 05 May 2001 09:18:17 +0200e4 From: Didier Morandi <Didier.Morandi@Pachacamac.com>J Subject: [EVENT] Post =?iso-8859-1?Q?Z=FCrich?= seminar event registration( Message-ID: <3AF3A93A.1BDFC315@wcxn.org>  F As previously stated, Christof Brass and I will organize (if there areH volunteers, of course) a post OpenVMS Technical Update Seminar dinner in Zrich on the 18th of May.  H In order to have an approximate idea on how much we will be, please send5 mail to Didier.Morandi@ubs.com if you are interested.n  G We plan to setup a dinner, then an evening soire. For the dinner, feellZ free to get in touch with me. For the soire, Christof will handle it (brass@infopuls.com)  G We welcome our COMPAQ visitors from over the pond, and the participantsa8 as well, and we look forward to meeting you on the 18th.   Best,- D.   ------------------------------   End of INFO-VAX 2001.251 ************************