NET/MASTER RMS Management and Operations Guide

Appendix A RMS Messages
115415 NonStop NET/MASTER RMS Management and Operations Guide A–1
Looking for Additional
Information
This appendix refers to topics that are discussed in other manuals. The following table
provides the cross-referencing information on those topics:
For details on… Refer to…
Distributed Systems Network
Management (DSNM)
User’s Guide to DSNM Commands; Distributed Systems
Management Solutions (DSMS) System Management
Guide
Guardian file-system errors Guardian Procedure Errors and Messages Manual
Network Control Language (NCL) and
message profile variables
NonStop NET/MASTER NCL Reference Manual
NonStop NET/MASTER MS commands NonStop NET/MASTER MS Command Reference
Manual
NonStop NET/MASTER MS message
and NCL error codes
NonStop NET/MASTER Messages Manual
SPI tokens Distributed Systems Management (DSM) Programming
Manual
Before Contacting
Your Tandem Support
Representative
Some of the problems that you encounter may require you to contact your Tandem
support representative. Before you contact your representative, ensure that you have
the relevant information ready.
Software Version Gather the version information on the software that you were using when the problem
occurred as follows:
Gather the version information on the NonStop NET/MASTER RMS that you are
using from one of the following:
Title of the NonStop NET/MASTER RMS primary menu panel
Message RMS0210 in the NonStop NET/MASTER MS activity log
Use the VPROC utility to gather the version information on the NonStop
NET/MASTER MS files you are using. For example:
VPROC $SYSTEM.SYSTEM.NNM
If the problem occurred while you were using another product from your
NonStop NET/MASTER environment, gather the version information on the other
product. For example:
VPROC $SYSTEM.SYSTEM.FUP
If the problem is the result of an OPSYS command, gather the version information
on the command interpreter software of DSNM.
Activity Log Have ready a copy of the activity log file that was active when the problem occurred.
Startup Files Have ready the following files: NCL procedures INIT and READY (if customized).
Process Abends, Hangs, or
Loops
If the problem occurred in a NonStop NET/MASTER process, have the saveabend file
ready, if available. The name of a saveabend file starts with ZZSA.