Operator Messages Manual

About This Document

This manual describes the operator messages distributed by EMS consumer and printing distributors. Use it to look up messages that are sent to or displayed on:

  • The OSM Event Viewer (for J-series and H-series)

  • The OSM Event Viewer or TSM EMS Event Viewer (for G-series)

  • The Web ViewPoint and ViewPoint event screens (for J-series, H-series, and G-series)

  • Distributed System Management /NonStop™ Operations for Windows (DSM/NOW) Multi Event Viewer

  • NonStop NET/MASTER event viewer

  • Printers, log files, or terminals used by the printing distributor

  • System management applications

This manual describes operator messages generated by J-series subsystems on HP Integrity NonStop BladeSystems, H-series subsystems on HP Integrity NonStop servers, G-series subsystems on HP NonStop S-series servers, and L-series subsystems on NonStop X systems.

Supported Release Version Updates (RVUs)

This manual supports L15.02 and subsequent L-series RVUs, J06.03 and subsequent J-series RVUs, H06.03 and subsequent H-series RVUs, G03.00 and subsequent G-series RVUs, until otherwise indicated by its replacement publication.

Intended Audience

This manual is intended for operators responsible for monitoring the server.

New and Changed Information in This Edition

This edition of the Operator Messages Manual has been updated as follows:

Document Organization

The first chapter in this manual is the Introduction. Except for the Introduction and the appendixes, this manual is organized alphabetically by subsystem name. Within each chapter, the operator messages are listed in numerical order by event number.

The Common Messages chapter contains messages that are generated by many subsystems. Common messages have negative event numbers.

NOTE: If you receive an operator message with a negative event number, see Chapter 15 for an explanation.

To look up an operator message in this manual, you must know the message’s subsystem name and event number. Chapter 1 lists the subsystem name (and subsystem number) for all subsystems documented in this manual and describes how to find a message’s subsystem name or number.

Notation Conventions

General Syntax Notation

This list summarizes the notation conventions for syntax presentation in this manual.

UPPERCASE LETTERS

Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example:

MAXATTACH

Italic Letters

Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required. For example:

file-name

Computer Type

Computer type letters indicate:

  • C and Open System Services (OSS) keywords, commands, and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example:

    Use the cextdecs.h header file.

  • Text displayed by the computer. For example:

    Last Logon: 14 May 2006, 08:02:23

  • A listing of computer code. For example

    if (listen(sock, 1) < 0)
    {
    perror("Listen Error");
    exit(-1);
    }

Bold Text

Bold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE

?123
CODE RECEIVED:      123.00

The user must press the Return key after typing the input.

[ ] Brackets

Brackets enclose optional syntax items. For example:

TERM [\system-name.]$terminal-name

INT[ERRUPTS]

A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example:

FC [ num  ]
   [ -num ]
   [ text ]

K [ X | D ] address
{ } Braces

A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example:

LISTOPENS PROCESS { $appl-mgr-name }
                  { $process-name  }

ALLOWSU { ON | OFF }
| Vertical Line

A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example:

INSPECT { OFF | ON | SAVEABEND }
… Ellipsis

An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example:

M address [ , new-value ]…

 - ] {0|1|2|3|4|5|6|7|8|9}…

An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example:

"s-char…"
Punctuation

Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example:

error := NEXTFILENAME ( file-name ) ;

LISTOPENS SU $process-name.#su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example:

"[" repetition-constant-list "]"
Item Spacing

Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items:

$process-name.#su-name
Line Spacing

If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] LINE

   [ , attribute-spec ]…

Notation for Messages

This list summarizes the notation conventions for the presentation of displayed messages in this manual.

Bold Text

Bold text in an example indicates user input typed at the terminal. For example:

ENTER RUN CODE

?123
CODE RECEIVED:      123.00

The user must press the Return key after typing the input.

Nonitalic Text

Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example:

Backup Up.

Italic Text

Italic text indicates variable items whose values are displayed or returned. For example:

p-register

process-name
[ ] Brackets

Brackets enclose items that are sometimes, but not always, displayed. For example:

Event number = number [ Subject = first-subject-value ]

A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example:

proc-name trapped [ in SQL | in SQL file system ]
{ } Braces

A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example:

obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }

process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown.          }
| Vertical Line

A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example:

Transfer status: { OK | Failed }
% Percent Sign

A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example:

%005400

%B101111

%H2F 

P=%p-register E=%e-register

Related Information

The following manuals provide information related to EMS event messages:

  • Some subsystem manuals document the events generated by the subsystem. If you cannot find a message in this manual, refer to the subsystem manual.

  • The EMS Manual describes the collection of processes, tools, and interfaces that provide event-message collection and distribution in the Distributed Systems Management (DSM) environment.

  • The DSM Template Services Manual describes how event and command-response messages are produced and displayed as text derived from the Subsystem Programmatic Interface (SPI).

  • The Guardian Procedure Errors and Messages Manual describes error codes, error lists, and messages returned by system procedure calls.

  • The TACL Reference Manual describes the interactive terminal messages.

  • The Processor Halt Codes Manual describes processor halt codes.

Publishing History

Part NumberProduct VersionPublication Date
522687-041N.A.February 2014
522687-042N.A.August 2014
522687-043N.A.February 2015
522687-044N.A.May 2015
522687-045N.A.August 2015
862339-001N.A.May 2016

HP Encourages Your Comments

HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to:

pubs.comments@hp.com

Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.