[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

691.0. "ANAL/PROCESS on OpenVMs 6.2 gets OPCDEC error!!" by DV780::THURY (Making it so...) Thu Jun 05 1997 02:15

    I'm working with a customer who's running OpenVMS/Alpha 6.2.  They are
    having problems with a 3rd party product which ACCVIOs randomly and
    frequently.  In order to help the vendor identify/resolve their
    problem, we arranged to create process dump files.  These dump files
    are 13,500 -> 14,500 blocks in size
    
    I now have several of the dump files from different users.  When I try
    ANALYZE/PROCES_DUMP/INTERACTIVE program.DMP, there is a 10-15 second
    delay as the dump is apparently being loaded, then suddenly I get:
    
    Condition signalled to take dump:
    
    Improperly signalled condition, invalid condition handler procedure value.
      Signal arguments:     Number = 00000003
                            Name   = 0000043C
                                     7EE26094
                                     0000001B
    
    Register dump:
    
        R0 --> R29 register dump ....
    
    SP = 00000000009CDCF0  PC = 000000007EE26094  PS = 300000000000001B
    %SYSTEM-F-OPCDEC, opcode reserved to Digital fault at PC=00000000,
    PS=0000043c
    
    and I return to the DCL!
    
    I've seen the article in one of the archived VMSnotes conference about
    problems with ANALY/PROCESS w/ vested images.  Does this problem still
    exist on OpenVMS 6.2?
    
    Any other ideas wha may cause this? Perhaps some improper process
    quota/limit?
    
        Thanks for any help,
             Denny
T.RTitleUserPersonal
Name		DateLines
691.1Suggestions...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu Jun 05 1997 10:3422
   There are previous discussions of ANALYZE/PROCESS_DUMP failures
   around (see 595, 640, and previous conferences), this utility is
   particularly sensitive to the process pagefile quota, and to the
   system virtual memory limits.  And the command is also particularly
   sensitive to stack corruptions in the image dump file -- these same
   stack corruptions can obviously be directly involved with the original
   application failure, as well.

   See CFS_44041 and CTI_SRC951016006676 in the support database for
   some related articles.

   Also consider using DELTA to look at the dump.  See 595.

   Once the above quotas are checked and raised, you might want to
   elevate the ANALYZE/PROCESS_DUMP problem to engineering via an
   IPMT if the tool does not start working.  You will need to provide
   the SYSGEN parameter information for the system, and a copy of the
   (errant) process dump file.

   COMET URL: http://comet.alf.dec.com/ -- this tool allows one to
   search the support databases.