Dealing with Untrapped GT.M Errors

When certain errors occur GT.M does not process $ZTrap. The following section help you gather information from an OpenVMS DUMP to help you identify the problem and select an appropriate method of resolution.

In the following cases the process is deemed to be damaged beyond reasonable expectation of recovery.

  • In the following cases the process is deemed to be damaged beyond reasonable expectation of recovery.

  • Access Violation (ACCVIO)–an attempt to access protected memory.

  • GTMCHECK–failure of an internal consistency check.

  • OPCDEC–the operation code at the indicated address is not known.

  • ROPRAND–an instruction contains an operand in a format that is not acceptable.

  • Stack overflow; however this is preceded by a STACK CRIT (warning) error.

OpenVMS provides a facility to dump the memory of a process for subsequent analysis. This requires significant time and disk space when a process has large amounts of virtual address space. Contact Fidelity Information Services for guidance on whether this technique can be safely employed at your production sites.

In OpenVMS, additional protection has been added to help detect inappropriate modifications to memory.

If it is possible to use process dump, the following DCL command should be added to the LOGIN.COM files for users who are experiencing untrapped failures:

                $ set proc/dump
                

Your terminal may become unavailable for several minutes if your process dumps. A procedure should also be established to ensure that the .dmp files which are generated are copied to tape and deleted promptly so that they do not create a disk space crisis.

Please do not try to use process dumps unless you have a thorough understanding of the possible unpleasant side effects.