10.5  ANALYZE

  New Qualifier:  /SHARED_MEMORY

  In the event of system crashes, it may be necessary to save
  the contents of some or all of shared memory in addition to
  the memory that is local to the system that has crashed.  This
  will be done either by writing shared memory to the sys-
  tem dump file using enhanced system dump code, or as a
  separate step using the DUMP/SHARED_MEMORY com-
  mand (which is the topic of a separate note).  This can be
  done either after the failed system reboots, or at any time
  from another instance of OpenVMS in the same community.

  DUMP/SHARED_MEMORY writes to a separate file, not to
  the system dump file.

  Shared memory included in a system dump file will be
  analyzed with the existing ANALYZE/CRASH_DUMP com-
  mand.  Shared memory dumped separately will be analyzed
  using the new command ANALYZE/SHARED_MEMORY.

  Syntax Description:

  The format is:  ANALYZE/SHARED_MEMORY "file_name"

  where "file_name" is the name of the file created by the
  DUMP/SHARED_MEMORY command.

  The only existing ANALYZE qualifier (from ANALYZE
  /CRASH_DUMP) that may be used with ANALYZE
  /SHARED_MEMORY is /OVERRIDE. This qualifier, which
  is optional, allows limited access to the shared memory dump
  file when trying to establish the cause of a corrupted or
  incomplete dump.

  Qualifier description:

  The /SHARED_MEMORY qualifier indicates that a shared
  memory dump is to be analyzed.  The SDA utility is invoked
  to perform the analysis, although it should be noted that
  only a limited set of SDA commands are relevant to shared
  memory dumps.

  Example:

  $  ANALYZE/SHARED_MEMORY  GLX$SHARED_MEMORY.DMP

    OpenVMS  (TM)  Alpha  system  dump  analyzer
    ...analyzing  a  Galaxy  shared  memory  dump...
  shmSDA>  EXIT
  $

  This command invokes SDA to analyze the shared mem-
  ory dump file GLX$SHARED_MEMORY.DMP. (Note that
  this is the default file name created by DUMP/SHARED_

  MEMORY).