    Upgrade to newer VAX systems?   The Question is:    0 What are the physical dimensions of the VAX 4000 106A and is it still available?    - I am looking to replace current clusters of :  VAX 4000-200, MicroVAX 3100-40,  VAXStation 4000-60    with clusters of e.g.    " VAX 4000-106A, VAXStation 4000-96.   + Need to stay with Q-bus technology for risk  reduction in s/w development.    
 Any thoughts?   The Answer is :   >   Please contact your HP  sales representative or HP reseller.   E   What VAX information is available is accessable via the AlphaServer *   website, which is itself accessable via:        http://www.hp.com/go/server    E   All VAX systems are going -- or have already gone -- "End Of Life".    G   The VAX 4000 model 100 series (save for the VAX 4000 model 108 series B   enclosure) generally has the following physical characteristics:   
   Standalone: ?     14.99cm (5.9in) H x 46.38cm (18.26in) W x 40cm (15.75in) D. 0     18.4 Kg, approximate, including three disks.   3   Rackmount (including shelf assembly and sliders): ;     22.22cm (8.75in) H x 28.26cm (19in) W x 63.5cm (25in) D 7     27.22Kg (60lb), approximate, including three disks.    F   Of all of the systems listed in your current configuration, only the*   VAX 4000 model 200 permits Q-bus access.   G   The VAX 4000 model 200 uses a processor module that installs directly H   in a standard Q-bus enclosure.  The VAX 4000 model 100 series includesD   an entirely seperate system enclosure including the processor, andH   supports an external expansion into a seperate Q-bus enclosure for use"   with specific Q-bus peripherals.   =   The OpenVMS Wizard would also recommend using SCSI storage.    C   The OpenVMS Wizard would generally recommend a mixed-architecture E   OpenVMS Cluster, and the migration of specialized Q-bus hardware to G   PCI or other buses, or migration to standard (existing) PCI hardware.    E   OpenVMS VAX and OpenVMS Alpha are generally quite compatible at the G   source level, and even Macro32 generally migrates easily.  (There are G   certainly cases where code has been written to specific VAX features, F   or privileged-mode code that might not be particularly easy to port.G   That said, the vast majority of OpenVMS VAX applications are directly G   source-portable to OpenVMS Alpha.)  Mixed-architecture configurations F   permit sharing source code, data files, passwords, and configurationE   information, and greatly redice what would be otherwise be the more G   tedious and error-prone portions of any code migration -- copying the    files around.    G   As a first step to migration, ensure that the OpenVMS VAX systems are K   running current OpenVMS VAX version and current layered product versions. B   This will ease migration, allowing you to determine if a problemC   (potentially) encountered during migration is specific to the new 7   software environment or the new hardware environment.    /  Answer written or last revised on  9-JUN-2004  