Conference bulean::decnetvax

        If you have "DECnet" on both of them, then  your DECnet is at
        least Phase IV. Of course  you could have DECnet/OSI aka Phase
        V at least on your V6.1 Alpha.
        
        Whether they both have Phase IV DECnet product, Phase V DECnet
        product and mixed case, they can talk to each other.
        
        I am not aware of DECnet Phase III implementation for Alpha
        computers. And in the specific case of Alpha running Digital
        Unix, then there is only Phase V implementation available.
        
        In this case, whether there is at all DECnet phase difference
        between these two systems, it is tied to the operating system
        version anyway. Further, if there is difference, still they
        would be adjacent phases and would talk to each other.
        
        _veli

    
:    Can any one clarify,  one  Alpha  system  with  OVMS  ver.1.51H
:    and another system with  OVMS ver.6.1  on  same  thin  ethernet
:    back bone can talk over Decnet. My doubt is Decnet  phase diff.

   The two systems should be able to communicate via DECnet.

   The OpenVMS V7.1 release is current -- OpenVMS Alpha V1.5-1H1 is a
   very old release, and should be upgraded.  You will have problems
   getting software kits for, and patches for any problems found with,
   that OpenVMS Alpha V1.5-1H1 system.

   Two OpenVMS Alpha or OpenVMS VAX systems can be configured as two
   DECnet Phase IV systems, or as two DECnet-Plus systems, or as one
   DECnet Phase IV system and one DECnet-Plus system using an address
   in the DECnet Phase IV space.  DECnet-Plus generally requires an
   external dedicated network routing box (such as a DECnis) for most
   routing and network communications, though small configurations can
   use host-based DECnet-Plus routing.

   The DECnet Phase III protocols predate the release of OpenVMS VAX
   V3.0, and I am aware of no Digital implementation of DECnet Phase
   III for OpenVMS Alpha.

>   The DECnet Phase III protocols predate the release of OpenVMS VAX
>   V3.0, and I am aware of no Digital implementation of DECnet Phase
>   III for OpenVMS Alpha.
    
    Nit (the above is true) -- DECnet Phase IV was first introduced
    in VAX/VMS V3.4, so Phase III extended a _bit_ beyond V3.0.
    
    
    
    Extreme nit -- there never was an "OpenVMS VAX V3.0"...

    Hi
    Thank you very much. I did it it worked.
    But i have now one more problem, there is a data base sitting on both 
    the systems sharing,(s/w developed by 3rd party called Barco Graphics 
    for printing  bank  notes)  while   invoking s/w it displaying output 
    device error. Earlier it worked nicely. 
    Is it required to upgrade the second system also ?
    One  system  upgraded because of network card DE422 failed and no more
    available. DE425 NIC is alternative which will not work with OVMS1.5
    That is the reason one system upgrades to OVMS 6.1.
    
    thanks
    RAO
    

   "Output device error"?  That may or may not be an error related to DECnet,
   and thus outside the scope of this conference.  Without knowing more, I'd
   guess the problem is not related to DECnet.

   This could be anything from a product that is incompatible with OpenVMS
   V6.1, to a missing logical name or other product misconfiguration...

   Look through the product documentation and if unable to locate any relevent
   troubleshooting information and to locate a software version compatibility
   table (to see if the package is supported on a particular OpenVMS version).
   Failing either, contact the organization that supports the Barco Graphics
   software.

   You specifically indicate "systems sharing" -- is this a VMScluster?  If
   so, OpenVMS Alpha V1.5 is ancient, and should be upgraded.  (OpenVMS V7.1
   is the current release.)  V6.1 and V1.5 *should* interoperate correctly in
   a mixed-version VMScluster, but I'd *definitely* upgrade both systems to
   at least OpenVMS Alpha V6.2...

    Hello
    Let me give you some more details to you, there is no VAX cluster.
    Sharing means s/w (Barco Graphics) will be running on both the systems
    parallel,it is possible when is decnet up and running, otherwise the
    printing the banknotes is not possible.
    While upgrading will it effects any s/w otherthan O/S ?
    
    thanks 
    RAO
    

   Contact the Barco Graphics support organization.  NOW.  You need
   answers, and the folks that can provide you with the answers are
   at Barco, not Digital.  If your customer is not getting the answers
   your customer needs from Barco, there's not much Digital can do...
   Given the previous replies and the questions, you'll need assistance
   of the folks with access to the source code.

:    Let me give you some more details to you, there is no VAX cluster.
:    Sharing means s/w (Barco Graphics) will be running on both the systems
:    parallel,it is possible when is decnet up and running, otherwise the
:    printing the banknotes is not possible.
:    While upgrading will it effects any s/w otherthan O/S ?
    
   There is nowhere near enough information to answer this question.

   DECnet *should* be completely independent, but that you are asking
   this question at all makes it appear that this software is potentially
   unstable, or that is tied tightly into some low-level component of
   OpenVMS or DECnet.  Or that there is some sort of unusual shared
   host or controller on your network or on your local system that is
   accessed via DECnet-derived protocols.

    Hi
    
    I have fixed the problem,I took Barco support.
    Thanks a lot
    
    Rao