[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

256.0. "SHRIDMISMAT when running RF_VERS" by COMICS::SHELLEY (Don't get mad, get even.) Thu Feb 27 1997 05:25

    Hi,
    
    A customer is upgrading OpenVMS VAX 6.1 to 6.2 and as per the
    upgrade guide he ran RF_VERS to check the microcode rev level
    of the DSSI disks.
    
    The problem is that he gets the error -
    
    %DCL-W-ACTIMAGE, error activating image CMA$TIS_SHR
    -CLI-E-IMGNAME, image file
    DSA0:[SYS1.SYSCOMMON.][SYSLIB]CMA$TIS_SHR.EXE
    -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image
    
    
    I believe this is caused because RF_VERS is a 6.2 image (he got it
    off the 6.2 CD) is not compatible with 6.1
    
    Is this expected behaviour and if so is there a 6.1 image that can be
    used ?
    
    Thanks
    
    Royston
    UK CSC
    
T.RTitleUserPersonal
Name
DateLines
256.1RF Disk SET HOST/DUP via Console, or via FYDRIVERXDELTA::HOFFMANSteve, OpenVMS EngineeringThu Feb 27 1997 10:3135
    Running newer images on older releases is specifically why the GSMATCH
    value was implemented.

    The RF_VERS tool was first shipped on the OpenVMS VAX V6.2 release.

    You *might* be able to get it to work in V6.1 by pulling over a
    V6.2 CMA$TIS_SHR and (probably) LIBRTL to a user-created directory
    on V6.1, and setting up CMA$TIS_SHR and LIBRTL to reference the
    V6.2 images just before running the RF_VERS tool. 

    But it's probably easier just to connect out into the drive controller,
    and simply ask it for the version...

    $ RUN SYS$SYSTEM:SYSGEN
    SYSGEN> CONNECT FYA0/NOADAPTER
    SYSGEN> ^Z
    $ SET HOST/DUP/SERV=MSCP$DUP/TASK=PARAMS <DSSI-NODE-NAME>
    ...
    PARAMS> STAT CONF
    <The software version is normally near the top of the display.>
    PARAMS> EXIT
    ...

    You can also get to the drive using the console >>> SET HOST
    command present in most 3000- and 4000-class VAX system consoles.
    (Obviously, the system must be halted for these commands...)

    Integrated DSSI:

	>>> SET HOST/DUP/DSSI[/BUS:[0:1]] dssi_node_number PARAMS

    KFQSA:
	>>> SET HOST/DUP/UQSSP port_controller_number PARAMS

256.2COMICS::SHELLEYDon&#039;t get mad, get even.Thu Feb 27 1997 10:597
    > The RF_VERS tool was first shipped on the OpenVMS VAX V6.2 release.
    
    Thats fair enough but why would it suggest this image is run as part
    of a pre upgrade procedure as the customer would _obviously_ be on an
    earlier version of VMS ?
    
    Royston
256.3RF_VERS was not tested, or the test was ignored...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu Feb 27 1997 11:4618
:    > The RF_VERS tool was first shipped on the OpenVMS VAX V6.2 release.
:    
:    Thats fair enough but why would it suggest this image is run as part
:    of a pre upgrade procedure as the customer would _obviously_ be on an
:    earlier version of VMS ?

   It's a bug that obviously got past the testing.

   With V7.1 and (probably) later distribution kits, there's a bootable
   copy of OpenVMS VAX on the CD-ROM.

   Check the COMET and STARS search engines, and the patch area, and see
   if a version of the RF_VERS tool has been released for V6.1.  If you
   are unable to locate the tool for V6.1 or a previous report, QAR the
   bug -- there's not much that can be done for the long-since-shipped
   V6.2 release -- the next time this QAR would be of interest would be
   for any tools needed prior to the `Raven' release of OpenVMS. 

256.4stealth featuresGIDDAY::GILLINGSa crucible of informative mistakesThu Feb 27 1997 19:1412
>   With V7.1 and (probably) later distribution kits, there's a bootable
>   copy of OpenVMS VAX on the CD-ROM.

  It's also present on the OpenVMS/VAX CDs for V6.2 and even V6.1! but
  no one bothered to tell anyone about it. You get to it by booting into
  root 1 of the CD:

>>> B/10000000 cd-drive

  I found it by accident booting a system with default root 1 (hey, who
  changed this VAX into an Alpha?! ;-).
						John Gillings, Sydney CSC