1 INFO-VAX	Fri, 06 May 2005	Volume 2005 : Issue 251       Contents: Re: A C programming question Re: A C programming question Re: A C programming question Re: A C programming question Re: Appletalk on Alphas  Re: Appletalk on Alphas  Re: Appletalk on Alphas  Re: Appletalk on Alphas  Clusterwide QUEMGR file  Re: Clusterwide QUEMGR file  Re: Clusterwide QUEMGR file / Re: Google Groups, was: Re: Appletalk on Alphas & Re: how, exactly, is SYS$NODE defined?& Re: how, exactly, is SYS$NODE defined?& Re: how, exactly, is SYS$NODE defined?& Re: how, exactly, is SYS$NODE defined?& Re: how, exactly, is SYS$NODE defined?& Re: how, exactly, is SYS$NODE defined? Re: Message definition files Re: More VAX help needed Re: ordering OpenVMS 8.2 Re: ordering OpenVMS 8.2 Re: ordering OpenVMS 8.2 Re: ordering OpenVMS 8.2K Re: Time to vote on your favorite slogan for the next OpenVMS License plate P Re: Time to vote on your favorite slogan for the next OpenVMS License plate platP Re: Time to vote on your favorite slogan for the next OpenVMS License plate plat  F ----------------------------------------------------------------------  # Date: Thu, 05 May 2005 17:41:50 GMT # From: hoff@hp.nospam (Hoff Hoffman) % Subject: Re: A C programming question 0 Message-ID: <yVsee.4956$mF.978@news.cpqcorp.net>  X In article <4279e3cb@cpns1.saic.com>, Mark Berryman <mark.berryman@mvb.saic.com> writes:@ :A program written for the GNU C environment does the following: :  :typedef short DCTELEM;  :  :and then, inside a structure, : 3 :DCTELEM block[6][64] __attribute__((aligned (8)));  : > :This causes the short array to aligned on an 8-byte boundary. : J :DECC does appear to have any mechanism for specifying alignment within a J :structure.  For the structure itself, and standalone variables, yes, but 2 :not within a structure (that I can find, anyway).  6   Can you post a stand-alone example of the construct?     I'd look at:  -   #pragma nomember_alignment [base_alignment] +   #pragma member_alignment [save | restore]   
   as a start.   G   There is also an _align storage class modifier available, which looks =   close to what you want here.  _align 8 or _align 16, or...    C   Memory that is dynamically allocated is also aligned, though that    may or may not help here.   7   I'm running mostly C V6.5 and C V7.* compilers, FWIW.     N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Thu, 05 May 2005 14:39:21 -0700  From: Z <Z@no.spam> % Subject: Re: A C programming question , Message-ID: <9owee.33196$Ow2.32069@fe06.lga>   Mark Berryman wrote:D > The alignments are necessary.  Does anyone know of a way to align K > variables within a structure, at an alignment greater than their natural  E > alignment, using the VMS C compiler?  If it helps, this particular  K > package usually places the alignment in a macro similar to the following:  > / > #define __align8 __attribute__((aligned (8)))   H Can the DEC C storage class modifer _align be used on an element within  a structure?   ------------------------------  % Date: Thu, 05 May 2005 16:01:20 -0700  From: Z <Z@no.spam> % Subject: Re: A C programming question + Message-ID: <0Bxee.33203$Ow2.2502@fe06.lga>    Z wrote: > Mark Berryman wrote: > E >> The alignments are necessary.  Does anyone know of a way to align  D >> variables within a structure, at an alignment greater than their C >> natural alignment, using the VMS C compiler?  If it helps, this  I >> particular package usually places the alignment in a macro similar to   >> the following:  >>0 >> #define __align8 __attribute__((aligned (8))) >  > J > Can the DEC C storage class modifer _align be used on an element within  > a structure?   Nevermind.  Answer is no.    ------------------------------   Date: 5 May 2005 16:38:45 -0700 0 From: "Bruce Visscher" <bvisscher@bellsouth.net>% Subject: Re: A C programming question C Message-ID: <1115336325.024632.183980@g14g2000cwa.googlegroups.com>   B Of course, the canonical way (IMHO) to align things in C is to use union.   union {    DCTELEM block[6][64];    long long __dummy; } x;  > But if the "original authors of the package" insist on using aD non-standard construct then you might be out of luck.  I don't see aE way of incorporating this (or the other suggestions based on #pragma) " into a simple macro like __align8.   ------------------------------  % Date: Thu, 05 May 2005 17:21:42 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>  Subject: Re: Appletalk on Alphas, Message-ID: <427A5626.19178.F3CA5@localhost>  * On 5 May 2005 at 12:15, Bob Koehler wrote:  E > In article <4278EDE4.20533.2ACBD64D@localhost>, "Stanley F. Quayle" F > <squayle@insight.rr.com> writes: > > I think a PC running CHARON-VAX@ > would make a great print server. > [Shameless Plug (tm) from a > CHARON-VAX reseller] > / >    How does that fix the OP's AppleTalk need?   D Because he can run Appletalk in the VAX environment, without having A to drag an "old VAX" into his data center.  A shiny new Proliant  0 running Windows would be much more acceptable...  
 --Stan Quayle  Quayle Consulting Inc.  
 ----------- Stanley F. Quayle, P.E. N8SQ  +1 614-868-1363 3 8572 North Spring Ct., Pickerington, OH  43147  USA 0 stan-at-stanq-dot-com       http://www.stanq.com   ------------------------------  % Date: Thu, 05 May 2005 20:23:30 -0400 ' From: Dave Froble <davef@tsoft-inc.com>   Subject: Re: Appletalk on Alphas0 Message-ID: <117le828d4tq652@corp.supernews.com>   Stanley F. Quayle wrote:, > On 5 May 2005 at 12:15, Bob Koehler wrote: >  > E >>In article <4278EDE4.20533.2ACBD64D@localhost>, "Stanley F. Quayle" F >><squayle@insight.rr.com> writes: > > I think a PC running CHARON-VAX@ >>would make a great print server. > [Shameless Plug (tm) from a >>CHARON-VAX reseller] >>/ >>   How does that fix the OP's AppleTalk need?  >  > F > Because he can run Appletalk in the VAX environment, without having C > to drag an "old VAX" into his data center.  A shiny new Proliant  2 > running Windows would be much more acceptable...  B He'd still need to run an old version of VMS, because the product G doesn't work on V8.2.  He's stated that that isn't a solution.  All it  E would do is push the problem out to when he can no longer use a V7.3   node in his cluster.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------   Date: 5 May 2005 21:55:40 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)   Subject: Re: Appletalk on Alphas3 Message-ID: <VX3U3AX+MzWw@eisner.encompasserve.org>   Z In article <117le828d4tq652@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes: > Stanley F. Quayle wrote:- >> On 5 May 2005 at 12:15, Bob Koehler wrote:  >>   >>  F >>>In article <4278EDE4.20533.2ACBD64D@localhost>, "Stanley F. Quayle"G >>><squayle@insight.rr.com> writes: > > I think a PC running CHARON-VAX A >>>would make a great print server. > [Shameless Plug (tm) from a  >>>CHARON-VAX reseller]  >>> 0 >>>   How does that fix the OP's AppleTalk need? >>   >>  G >> Because he can run Appletalk in the VAX environment, without having  D >> to drag an "old VAX" into his data center.  A shiny new Proliant 3 >> running Windows would be much more acceptable...  > D > He'd still need to run an old version of VMS, because the product  > doesn't work on V8.2.   ? To the best of my knowledge, CHARON-VAX does not emulate Alpha. 0 Thus the newest version of VMS possible is V7.3.  > I would not expect any future VAX/VMS V8.2 to break Appletalk,= given the emphasis on stability with recent VAX/VMS releases.    ------------------------------  % Date: Fri, 06 May 2005 00:49:31 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>   Subject: Re: Appletalk on Alphas, Message-ID: <427AF73C.8BD6FD00@teksavvy.com>   Dave Froble wrote:C > He'd still need to run an old version of VMS, because the product H > doesn't work on V8.2.  He's stated that that isn't a solution.  All itF > would do is push the problem out to when he can no longer use a V7.3 > node in his cluster.  E With VAX VMS possibly forever stuck at 7.3, while Appletalk may still @ work on that one, there is no commitment (whatever that is worthH anyways) from HP to garantee VAX-VMS 7.3 will continue to be clusterable8 with whatever versionn of VMS is current in a few years.   ------------------------------  % Date: Thu, 05 May 2005 16:25:52 -0600 % From: Dan O'Reilly <dano@process.com>   Subject: Clusterwide QUEMGR fileA Message-ID: <6.1.2.0.2.20050505162409.02336f18@raptor.psccos.com>   H I have a clusterwide queue manager file.  When I reboot the host machineD upon which the qmgr file resides, it loses all information about theG queues defined in it, forcing me to redefine all the queues.  This is a  7.3 system on a PWS600au.    Any ideas, anybody?    ------J +-------------------------------+----------------------------------------+J | Dan O'Reilly                  |  "There are 10 types of people in this |J | Principal Engineer            |   world: those who understand binary   |J | Process Software              |   and those who don't."                |J | http://www.process.com        |                                        |J +-------------------------------+----------------------------------------+   ------------------------------   Date: 5 May 2005 17:23:13 -0700  From: dooleys@snowy.net.au$ Subject: Re: Clusterwide QUEMGR fileB Message-ID: <1115338993.047909.60790@o13g2000cwo.googlegroups.com>   Dan O'Reilly wrote: B > I have a clusterwide queue manager file.  When I reboot the host machine F > upon which the qmgr file resides, it loses all information about theG > queues defined in it, forcing me to redefine all the queues.  This is  a  > 7.3 system on a PWS600au.  >  > Any ideas, anybody? < If you started the queue manager using /ON(node1,node2,...*)1 then when node1 shuts down it will start on node2 B If availability is not an issue you can save the information while" the queue manager is running using. CONVERT/SHARE QMAN$MASTER.DAT QMAN$MASTER.KEEP< CONVERT/SHARE SYS$QUEUE_MANAGER.QMAN$QUEUES QMAN$QUEUES.KEEP= I'm not sure of the sequence to restore the queues, you ought D to check the details in the system manager's manual, it's all there. Phil   ------------------------------  % Date: Thu, 05 May 2005 21:00:52 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>$ Subject: Re: Clusterwide QUEMGR file+ Message-ID: <427ACFD3.DF588F4C@comcast.net>    Dan O'Reilly wrote:  > J > I have a clusterwide queue manager file.  When I reboot the host machineF > upon which the qmgr file resides, it loses all information about theI > queues defined in it, forcing me to redefine all the queues.  This is a  > 7.3 system on a PWS600au.  >  > Any ideas, anybody?   H I can't cite a reference to the VMS on-line doc. just now, but make sure@ you are DEFINE-ing (or ASSIGNing if you prefer) the logical name< QMAN$MASTER prior to attempting to start the queue manager.   F QMAN$MASTER should point to the dev:<dir>QMAN$MASTER.DAT file where inD the required information resides (location of the queue database and such).  E I think it may be in one of the cluster manuals. Can't say which just  now.  G We're preparing to implement multiple system disks at work, so I've had C to look into it, but not since late last season at this point and I > don't recall off the top of my head just now where I found the
 reference.  H At a minimum, see SYS$STARTUP:SYLOGICALS.TEMPLATE for a list of "cluster common" files.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------   Date: 5 May 2005 22:24:28 -0700  From: dooleys@snowy.net.au8 Subject: Re: Google Groups, was: Re: Appletalk on AlphasB Message-ID: <1115357068.508505.84440@g14g2000cwa.googlegroups.com>   Simon Clubley wrote:F > In article <d5deqs$22t$1@online.de>, helbig@astro.multiCLOTHESvax.de2 (Phillip Helbig---remove CLOTHES to reply) writes:F > > In article <1115305516.704342.83710@f14g2000cwb.googlegroups.com>, "Ed & > > Wilts" <ewilts@ewilts.org> writes: > > G > >> Is it just me or does the Google web interface to comp.os.vms just 
 > >> suck? > >  > E > I think that the new Google Groups interface is absolutely horrible $ > (and I only use it for searching). > G > Until now, I have been using the UK interface, as it still pointed to G > the old interface. However, as of a couple of days ago, it now points  > to the new interface. :-(  > 8 The .AU interface was also the "old" one until recently,< however the "new" one now has options for "view titles only"@ (which is similar to the old one, and it remembers this setting)> or "view with message text" and once you open a thread you can= "view as a tree" which again is similar to the old behaviour, & though it doesn't retain this setting.8 I also find the "recently visited" list handy sometimes. Phil   ------------------------------  $ Date: Thu, 5 May 2005 14:05:12 -0400 From: norm.raphael@metso.com/ Subject: Re: how, exactly, is SYS$NODE defined? Q Message-ID: <OF9FF55B33.8711AE2C-ON85256FF8.0063123F-85256FF8.00633201@metso.com>   ? "AEF" <spamsink2001@yahoo.com> wrote on 05/05/2005 12:57:46 PM:    > 1 > Phillip Helbig---remove CLOTHES to reply wrote: G > > SYS$NODE is normally defined by DECnet.  I'm not running any DECnet  > atH > > the moment, but even in the future I probably won't run it on all myH > > systems.  However, SYS$NODE is needed by some other applications, inH > > particular DECwindows (perhaps only to say "Welcome to SYS$NODE" andE > > "Session Manager on SYS$NODE") and (I'm not sure about this) LAT.  > Thus, H > > I have been defining it /SYSTEM/EXEC relatively early in the startupD > > sequence.  Is this the proper way to define it?  I'm pretty sure3 > > /SYSTEM/EXEC is correct, but what about /TRANS?  >  >  > $ SHOW LOG/FUL SYS$NODE G >    "SYS$NODE" [exec,crelog] = "IDS15::" [terminal] (LNM$SYSTEM_TABLE)  > I > Yes, /SYS/EXEC is correct, but to match the real SYS$NODE you also need I > /TRAN=TERMINAL. But you'll still be missing the crelog part and I don't I > think you can do that part with DCL! But if your app is only asking for $ > the node name it shouldn't matter. > H > Whether it is a good idea or not to define SYS$NODE outside of running > DECnet I can't say.  >   / There are at least 3 ways to get the node_name:     $say "<",f$getsyi("scsnode"),">"
 <NODEA   >! $say "<",f$getsyi("nodename"),">"  <NODEA> ! $say "<",f$trnlnm("sys$node"),">" 	 <NODEA::>  $   C If you are not running DECnet, perhaps one of the others will work.    ------------------------------  # Date: Thu, 05 May 2005 18:38:23 GMT # From: hoff@hp.nospam (Hoff Hoffman) / Subject: Re: how, exactly, is SYS$NODE defined? 0 Message-ID: <zKtee.4965$IL.701@news.cpqcorp.net>  p In article <OF9FF55B33.8711AE2C-ON85256FF8.0063123F-85256FF8.00633201@metso.com>, norm.raphael@metso.com writes:0 :There are at least 3 ways to get the node_name: : ! :$say "<",f$getsyi("scsnode"),">"  :<NODEA   > " :$say "<",f$getsyi("nodename"),">" :<NODEA>" :$say "<",f$trnlnm("sys$node"),">"
 :<NODEA::> :$ : D :If you are not running DECnet, perhaps one of the others will work.    H   I'll see if I can't free up some code either for inclusion in a futureG   RTL or for the Freeware, as I've a routine that gathers the name from I   about a dozen different spots.  Two routines, actually -- one looks for G   a series of names from biggest (cluster) to smallest (local node) and G   the other basically reverses that.  The two routines are each a dozen "   or so logical name translations.    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com    ------------------------------  % Date: Thu, 05 May 2005 20:29:37 +0100 - From: John Laird <nospam@laird-towers.org.uk> / Subject: Re: how, exactly, is SYS$NODE defined? 8 Message-ID: <2ssk715ckt510nf1nnbgrshbjsf2225fbh@4ax.com>  H On Thu, 5 May 2005 19:23:56 +0000 (UTC), helbig@astro.multiCLOTHESvax.de1 (Phillip Helbig---remove CLOTHES to reply) wrote:    >What is CRELOG?  K SYS$CRELOG (and DELLOG and TRNLOG) predated their xxxLNM replacements.  For K no doubt sound technical reasons that I couldn't begin to explain, a bit is F reserved in the logical name flags to indicate that CRELOG was used toK create the entry.  TRNLOG was much easier to program than TRNLNM for simple 6 use, and there is still a LIB$SYS_TRNLOG "equivalent".   --  & I'm an analog man in a digital world.    Mail john rather than nospam...    ------------------------------   Date: 5 May 2005 14:30:34 -0700 $ From: "AEF" <spamsink2001@yahoo.com>/ Subject: Re: how, exactly, is SYS$NODE defined? A Message-ID: <1115328634.138372.5090@z14g2000cwz.googlegroups.com>    Hoff Hoffman wrote: F > In article <d5df13$22t$2@online.de>, helbig@astro.multiCLOTHESvax.de2 (Phillip Helbig---remove CLOTHES to reply) writes:F > :SYS$NODE is normally defined by DECnet.  I'm not running any DECnet atG > :the moment, but even in the future I probably won't run it on all my   G > :systems.  However, SYS$NODE is needed by some other applications, in   G > :particular DECwindows (perhaps only to say "Welcome to SYS$NODE" and   D > :"Session Manager on SYS$NODE") and (I'm not sure about this) LAT. Thus, G > :I have been defining it /SYSTEM/EXEC relatively early in the startup   C > :sequence.  Is this the proper way to define it?  I'm pretty sure 2 > :/SYSTEM/EXEC is correct, but what about /TRANS? > D >   You should not need to define it.  If DECwindows thinks it needs it, G >   then that would arguably be a bug in either DECwindows (for needing D >   it) or in OpenVMS (for not defining it if DECnet is not around).    G Is this something new, that SYS$NODE is defined by VMS even when DECnet * is not running? (New since VMS v6.2, i.e.)   [...]    ------------------------------  # Date: Thu, 05 May 2005 22:08:30 GMT * From: "FredK" <fred.nospam@nospam.dec.com>/ Subject: Re: how, exactly, is SYS$NODE defined? 1 Message-ID: <yPwee.4983$TU.3298@news.cpqcorp.net>   A DECwindows doesn't "need" DECwindows to be running, I run without J DECnet installed at all, just using TCPIP.  However, it is pretty apparentB that circa 1993 or so, the code that implements gethostname inside; DECwindows assumes SYS$NODE is defined, otherwise you get a  null string return.   L I'd report this as a bug, but aside from say a quick & dirty fix in DTLOGIN,L a "real" fix to the gethostname code will need careful visual inspection and. testing of a number of things in the X11 code.    L "Phillip Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>/ wrote in message news:d5e3gd$178$1@online.de... I > In article <1115328634.138372.5090@z14g2000cwz.googlegroups.com>, "AEF" " > <spamsink2001@yahoo.com> writes: > H > > >   You should not need to define it.  If DECwindows thinks it needs > > it, K > > >   then that would arguably be a bug in either DECwindows (for needing H > > >   it) or in OpenVMS (for not defining it if DECnet is not around). > > K > > Is this something new, that SYS$NODE is defined by VMS even when DECnet . > > is not running? (New since VMS v6.2, i.e.) > J > I think Hoff was saying that it is a bug that VMS does NOT define it, ifH > it needs it when DECnet is not running, or, alternatively, it is a bug? > in DECwindows for wanting to use it instead of, say, SCSNODE.  >    ------------------------------  % Date: Thu, 05 May 2005 20:51:44 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>/ Subject: Re: how, exactly, is SYS$NODE defined? + Message-ID: <427ACDAF.33D2861E@comcast.net>   / Phillip Helbig---remove CLOTHES to reply wrote:  >  > In articleH > <OF9FF55B33.8711AE2C-ON85256FF8.0063123F-85256FF8.00633201@metso.com>,  > norm.raphael@metso.com writes: > 3 > > There are at least 3 ways to get the node_name:  > > $ > > $say "<",f$getsyi("scsnode"),">" > > <NODEA   >% > > $say "<",f$getsyi("nodename"),">"  > > <NODEA> % > > $say "<",f$trnlnm("sys$node"),">" 
 > > <NODEA::>  > > $  > > G > > If you are not running DECnet, perhaps one of the others will work.  > G > It's not a problem FOR ME to get the node name, but rather DECwindows  > uses only SYS$NODE.   & Then, maybe this would be good enough:  + $ IF F$TRNLNM( "SYS$NODE" ) .EQS. "" THEN - @ $ DEFINE/SYSTEM/EXEC SYS$NODE 'F$GETSYI("NODENAME")'::/TRAN=TERM  ? Do that in SYLOGICALS.COM or SYSTARTUP_VMS.COM, as appropriate.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------   Date: 5 May 2005 14:44:21 -0700 ! From: chessmaster1010@hotmail.com % Subject: Re: Message definition files C Message-ID: <1115329461.831604.210810@o13g2000cwo.googlegroups.com>   G The basic problem is that in this case the global cell for the EXTERNAL E definition will be a constant value defined externally instead of the * address of an externally defined variable.  D There are several solutions you can use.  If message symbols are the1 only EXTERNAL varabiles you can just compile with  /EXTERN_MODEL=GLOBALVALUE   B If there are other EXTERNAL definitions you can define the message# variables using the VAXC extension:    globalvalue int MSG_SYMBOL  D And compile with /STANDARD=VAXC.  To keep the code more standard and) not require any compiler /qualifiers use:    # pragma extern_model save! # pragma extern_model globalvalue  extern int MSG_SYMBOL; # pragma extern_model restore   
 Lawrie wrote:  > Hi,  > E > I am working on an application that uses user defined VMS messages.  >  > The build procedure uses >  > $message filename  > ! > to generate a file filename.obj  > E > This .obj is then linked when building the C++ application. Message 2 > types are declared as external in a header file. > G > I have added a few new message types but when I come to use them they . > appear as the wrong message type or unknown. > G > Apart from building and linking the message definitions .obj file and E > declaring the messages as external is there anything else I have to  do?  >  > Cheers >  > Lawrie   ------------------------------  # Date: Thu, 05 May 2005 17:36:24 GMT E From: "Verell Boaen VMScluster Comm. Architect" <Verell.Boaen@hp.com> ! Subject: Re: More VAX help needed 1 Message-ID: <sQsee.4955$2K.2511@news.cpqcorp.net>    Hello Bill, 5 "Bill Gunshannon" <bill@cs.uofs.edu> wrote in message & news:3dpbekF6rifjsU1@individual.net... >  got the idea that I couldB > connect my storageworks cabinet to a sikngle 6640 without a star
 > coupler., >... the local VMS guru and he said it won't > work without a star coupler.   That's correct, 3 You must have a star coupler for a several reasons:   K - A star coupler provides attenuation (18db min/27db max 10-100Mhz ) of the K transmit signal needed to bring it's amplitude down within the range of the 	 receiver. K - It permits all nodes sending on a path see each others signals on that CI " path. This is necessary to ensure:A .  that a node's receive circuitry is available to receive an ACK A (acknowledgment frame) immediately after a packet is transmitted. L . That a node is not transmitting when another node is sending packets, thusL ensuring that the node's transmitter is available to send an ACK immediately upon receiving the packet.E . Loop-back works ie:  a node can test the path by sending packets to F itself. VMS driver & CI adapter firmware self-test must verify that anK adapter can at least successfully send packets to itself on at least one CI H path  before the adapter is brought online. BTW, The CIPCA requires that. loopback work on both paths to pass self-test.   ROLLING YOUR OWN: L If you can't come up with a star coupler, you can make one out of a resistorK network. A simple T network with each transmit cable attached to the center K of the T thru a resistor, a resistor to ground for the bottom leg of the T, F and a resistor from the center of the T to each input cable. All cableF grounds are tied together at the bottom of the T. The input and output impedence must be 50 ohms.F The resistor values must provide the attenuation previously mentioned.  
 Helpfully, Verell Boaen# VMScluster Communications Architect    ------------------------------  $ Date: Thu, 5 May 2005 13:51:20 -0400 From: norm.raphael@metso.com! Subject: Re: ordering OpenVMS 8.2 Q Message-ID: <OFD5CCCD8E.AE808CDB-ON85256FF8.0062153E-85256FF8.0061ECE3@metso.com>   < kenneth.randell@verizon.net wrote on 05/05/2005 01:09:39 PM:  A > > =CC have called HP, Two authorized resellers and HP financial  > services. F > > None of them can find out the ordering part number for the OpenVMS > 8.2  > > distribution media.  > > * > > Can anyone advise of the part number ? > >  >  > Which platform are you after?  > 5 > Itanium looks like (deciphering an old quote here):  > , > BA322AA listed as HP OpenVMS I64 FOE media >   option AJR says DVD media. > F Perhaps the SPD at http://h18000.www1.hp.com/info/XAV12Z/XAV12ZPF.PDF=   ------------------------------  # Date: Thu, 05 May 2005 17:53:36 GMT # From: hoff@hp.nospam (Hoff Hoffman) ! Subject: Re: ordering OpenVMS 8.2 1 Message-ID: <A4tee.4957$mF.4794@news.cpqcorp.net>   g In article <1115312979.545047.129070@f14g2000cwb.googlegroups.com>, kenneth.randell@verizon.net writes: @ :> =CC have called HP, Two authorized resellers and HP financial :> services.E :> None of them can find out the ordering part number for the OpenVMS  :> distribution media. :>) :> Can anyone advise of the part number ?  :> :  :Which platform are you after? : 4 :Itanium looks like (deciphering an old quote here): : + :BA322AA listed as HP OpenVMS I64 FOE media  :  option AJR says DVD media.   >   Here is the direct path into the QuickSpec for OpenVMS V8.2:  H   http://h18000.www1.hp.com/products/quickspecs/12156_div/12156_div.HTML  E   Attached below are the relevent part numbers for OpenVMS Alpha V8.2 E   and OpenVMS I64 V8.2, including kits, documentation, licenses, etc. C   This documentation was extracted from the QuickSpec, obviously -- E   and the QuickSpec is likely easier to read than what I've pasted...   F   You want a kit and a license, as a start, and probably also want the   product documentation.  F   BA322AA-AJR (FOE), BA323AA-AJR (EOE) or BA324AA-AJR (MCOE, when thatG   becomes available) are the DVD media parts for OpenVMS I64 -- for the E   Foundation, Enterprise and Mission Critical Operating Environments, 5   respectively.  For OpenVMS Alpha V8.2, QA-MT1AA-H8.    	--   N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com      	--    Ordering Information    OpenVMS I64 Ordering Information  A new packaging plan is introduced with OpenVMS I64. With OpenVMS I64 Version 8.2, the operating system software, layered product software, and online documentation CD-ROM are delivered together in one media kit. Media is offered for Foundation (FOE), Enterprise (EOE), and Mission Critical (MCOE) Operating Environments. Purchase of an OE media product requires the purchase of a corresponding OE license on the same order.   Table 1 lists the media product offerings for the three operating environments. Table 2 lists the options available with each media product offering. # Table 1 OpenVMS I64 Media Offerings  Product No. 	Common Description ! BA322AA 	HP OpenVMS I64 FOE Media ! BA323AA 	HP OpenVMS I64 EOE Media # BA324AA1 	HP OpenVMS I64 MCOE Media G 1The MCOE will be introduced later in the OpenVMS I64 Software rollout. " Table 2: OpenVMS I64 Media Options Media Option 	Description   #A18 	HP OpenVMS I64 Version 8.2 #AJR 	OE Media Kit on DVD  #0D1 	Factory_Installationk Each OE media order must include the OE Version option. Please specify option #A18 for OpenVMS Version 8.2.   ; For each media order, one of the following must be ordered:   '     * OE Media Kit on DVD (option #AJR) (     * Factory Installation (option #0D1)H     * Both OE Media Kit and Factory Installation (options #AJR and #0D1)   The purchase of at least one OE media kit on DVD per customer site is strongly advised, since not all products are included in Factory Installation.  For a complete description of the OpenVMS I64 Operating Environments, or additional ordering information, please refer to the HP Operating Environments for OpenVMS Industry Standard 64 Version 8.2 for Integrity Servers Software Product Description (SPD 82.34.xx).  OpenVMS I64 Software Licenses    A license is referred to as a "License-to-Use" or LTU. The term "with system" means an Integrity Server is on the order. The term "without system" means an Integrity Server is not on the order.   ( For OEs, two hardware tiers are defined:  I     * Maximum of 4 Sockets (for systems available at first customer ship) V     * Unlimited Sockets (for larger systems to be supported after first customer ship)  w NOTE: A socket is a receptacle for microprocessor modules. A single microprocessor module can contain one or more CPUs.    The following are licenses offered for each OpenVMS I64 Operating Environment. One license is required for each active processor. D OpenVMS I64 Operating Environment Software Licenses Sold With System0 BA325AC 	HP VMS I64 FOE PPL LTU max4 sockt w/sys1 BA326AC 	HP VMS I64 FOE PPL LTU unltd sockt w/sys 0 BA397AC 	HP VMS I64 EOE PPL LTU max4 sockt w/sys1 BA327AC 	HP VMS I64 EOE PPL LTU unltd sockt w/sys 1 BA399AC 	HP VMS I64 MCOE PPL LTU max4 sockt w/sys 2 BA328AC 	HP VMS I64 MCOE PPL LTU unltd sockt w/sysG OpenVMS I64 Operating Environment Software Licenses Sold Without System 2 BA338AC 	HP VMS I64 FOE PPL LTU max4 sockt w/o sys3 BA329AC 	HP VMS I64 FOE PPL LTU unltd sockt w/o sys 2 BA398AC 	HP VMS I64 EOE PPL LTU max4 sockt w/o sys3 BA330AC 	HP VMS I64 EOE PPL LTU unltd sockt w/o sys 3 BA400AC 	HP VMS I64 MCOE PPL LTU max4 sockt w/o sys 4 BA331AC 	HP VMS I64 MCOE PPL LTU unltd sockt w/o sys" OpenVMS Alpha Ordering Information  5 The following are licenses offered for OpenVMS Alpha:     OpenVMS Alpha Software Licenses 8 QL-MT1A*-6* 	OpenVMS Alpha Operating System Base License? QL-MT1A*-7* 	OpenVMS Alpha Operating System Base Update License b QL-MT1A9-6* 	OpenVMS Alpha Operating System Symmetric Multiprocessing (SMP) Base Extension Licensei QL-MT1A9-7* 	OpenVMS Alpha Operating System Symmetric Multiprocessing (SMP) Base Extension Update License  QL-MT2A9-** 	OpenVMS Alpha Individual User License (No Longer Available...order the Concurrent Use License or Unlimited User License) 1 QL-MT2A*-AA 	OpenVMS Alpha Unlimited User License 9 QL-MT2A*-Y* 	OpenVMS Alpha Individual User Update License x QL-MT3A*-B* 	OpenVMS Alpha Distributed Interactive User License (No Longer Available...order the Concurrent Use License)F QL-MT3A*-Y* 	OpenVMS Alpha Distributed Interactive User Update License+ QL-MT3A*-3* 	OpenVMS Concurrent Use License 2 QL-MT3A*-5* 	OpenVMS Concurrent Use Update License+ Alpha CD-ROM Media and Online Documentation C QA-MT1AA-H8 	OpenVMS Alpha software and online documentation CD-ROM H QA-MT3AA-H8 	OpenVMS Alpha/VAX software and online documentation CD-ROM @                 (includes Alpha V8.2 and VAX V7.3 documentation)  # OpenVMS Hardcopy Documentation Sets  The OpenVMS Hardcopy Documentation sets includes information on all three operating platforms (I64, Alpha, and VAX). Due to different ordering systems for Integrity server and AlphaServer platforms, customers should order a BAxxxMN documentation set with Integrity server orders, or a QA-xxxAA-GZ documentation set with AlphaServer orders. Either order number delivers the same documentation at the same price. If you already have a service contract for the OpenVMS Documentation Set, you will automatically receX ive the V8.2 updated documents and do not need to order a new set for Integrity servers.+ BA555MN 	OpenVMS I64 Base Documentation SetN+ BA554MN 	OpenVMS I64 Full Documentation Sete< BA401MN 	OpenVMS I64 Operating Environment Extension Manuals9 QA-09SAA-GZ 	OpenVMS Alpha and VAX Base Documentation Setr9 QA-001AA-GZ 	OpenVMS Alpha and VAX Full Documentation Seto  ) OpenVMS Alpha and I64 Source Listings KitM1 BA422AA 	OpenVMS I64 Listings DVD Kit and License : QB-MT1AB-E8 	OpenVMS Alpha Listings CD-ROM Kit and License  > OpenVMS Alpha Software Products Library (SPL) CD-ROM Offerings QA-5FX8A-A8 	OpenVMS Alpha Software Layered Products and Operating System Library (Software Layered Product binaries only-no online documentation, complete Operating System kit)m7 QA-4KM8A-G8 	OpenVMS Alpha Online Documentation Libraryr QA-5G98A-H8 	OpenVMS Alpha Software Layered Products and Operating System Library Package (Software Layered Product binaries and online documentation, complete Operating System kit)tp QA-03XAA-H8 	OpenVMS Alpha Software Library Package (Software Layered Product binaries and online documentation)   ------------------------------   Date: 5 May 2005 13:46:18 -0500 - From: Kilgallen@SpamCop.net (Larry Kilgallen)g! Subject: Re: ordering OpenVMS 8.2F3 Message-ID: <NjPLVVJbARyx@eisner.encompasserve.org>s  W In article <A4tee.4957$mF.4794@news.cpqcorp.net>, hoff@hp.nospam (Hoff Hoffman) writes:e  + > OpenVMS Alpha and I64 Source Listings Kit 3 > BA422AA 	OpenVMS I64 Listings DVD Kit and Licensem< > QB-MT1AB-E8 	OpenVMS Alpha Listings CD-ROM Kit and License  K Any hints about the I64 Source Listings Subscription Service order number ?o   ------------------------------  % Date: Thu, 05 May 2005 17:36:04 -0400n- From: JF Mezei <jfmezei.spamnot@teksavvy.com> ! Subject: Re: ordering OpenVMS 8.2 , Message-ID: <427A91BF.527AC9E3@teksavvy.com>  " kenneth.randell@verizon.net wrote: > E > While are at this, this information is in table 2-2 of the recently  > posted VMS FAQs.  E If David Turner can't find a baseic part number to order VMS, imaginee< what a simple customer woudl have to go through to find it ?  G If one of the better known resellers can't find a part number, it means-C that there are some problems in making VMS related prodcust easy top locate and order.A   ------------------------------  # Date: Thu, 05 May 2005 18:00:55 GMT ! From: Nigel Barker <nigel@hp.com>nT Subject: Re: Time to vote on your favorite slogan for the next OpenVMS License plate8 Message-ID: <olnk71123o5ob91teg167ek8t32ic7ft5h@4ax.com>  8 On Thu, 5 May 2005 17:44:09 +0000 (UTC), "Richard Maher"$ <maher_rj@hotspamnotmail.com> wrote:   >VMS - You get what you pay fori  < Or after some advert for L'Oreal I saw with Jennifer Aniston   VMS - Because I'm worth it   -- Nigel Barker Live from the sunny Cote d'Azur?   ------------------------------  % Date: Thu, 05 May 2005 17:18:12 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>mY Subject: Re: Time to vote on your favorite slogan for the next OpenVMS License plate platr, Message-ID: <427A8D93.DD180891@teksavvy.com>  H Hey, 3 more HP employees voted. The stuf about integrity went from Kerry% Main's 24 votes to 27 votes today :-)l  J "When downtime is not an option" is still way ahead with 43% of the votes.   ------------------------------  % Date: Thu, 05 May 2005 22:04:24 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>dY Subject: Re: Time to vote on your favorite slogan for the next OpenVMS License plate plat , Message-ID: <427AD092.2812BA51@teksavvy.com>   Richard Maher wrote:M > to me was "Why are WE doing this?".  Why don't you pay some really creative@N > (in an advertising, outside of the box, sense of the word) people to come up > with an idea?g  / They do that for real HP products. Not for VMS.c    ! > Getting back to amateur day : -o  
 How about:  $ VMS, the operating system for adults VMS, the adult operating systemf   > VMS - Server Viagra    Instead:  L VMS can stay up for more than 4 hours without needing visit by a specialist.   ------------------------------   End of INFO-VAX 2005.251 ************************