Chapter 1 Introduction

What Is an Operator Message?

An operator message is an event message that has been converted to displayable text by an EMS distributor process or by a user application. An event message is a special category of Subsystem Programmatic Interface (SPI) message that conveys information about an event or significant occurrence in the subsystem environment. Occurrences and conditions reported by event messages and displayed as operator messages include:

Operator messages are intended to be seen (and perhaps acted upon) by an operator or, in some systems, by a program that performs operator functions.

Where Do Operator Messages Originate?

EMS is a set of processes that collects event messages from reporting processes and subsystems and then selectively distributes those messages to various destinations. The destinations range from a local operator console to a management application running on a remote server. Figure 1-1 shows how EMS routes messages.

Because operator messages are formatted event messages, they originate from the same places as event messages: HP subsystems (including operating system processes) and user-written subsystems.

Where Are Operator Messages Sent?

Subsystems write event messages to the EMS collector process $0 or to the $ZLOG collector. ($ZLOG is an instance of the EMS alternate collector.) These are the primary collection points for all event messages. The collector process writes the event messages to an event log file. From the event log, event messages are sent to a distributor process. The event log file is read by distributor processes configured onto or started on the server. Each distributor process has a filter associated with it. The distributor selects only the messages it wants by comparing each message to this filter. EMS provides four distributor processes that collect event messages from the EMS log file (or alternate log files). Three of these distributor processes format these messages into operator messages and then distribute these operator messages to various destinations.

The Distributor Processes

EMS provides the following distributor processes for handling event messages:

Consumer Distributor

The consumer distributor is used by applications provided by HP and by users to read the EMS log file (or alternate log files) and all or specific event messages, depending on filter specifications loaded to the consumer distributor process. The application can take appropriate action, if necessary, in response to an important event. ViewPoint (for D-series), the TSM Event Viewer (for G-series), and the OSM Event Viewer (for G‑series or H-series) are applications provided by HP that use the consumer distributor.

Printing Distributor

The printing distributor formats operator messages for logging to disk files, terminals, or printers. The following example shows the format for HP Open Systems Interconnection/Message Handling System (OSI/MHS) operator messages as they are sent to disk files, terminals, or printers:

94-07-23 15:09:51 \NET.$FTI1 TANDEM.MHS.D20 000023 $ZL1 MR.\NET.MRGRP1 $RL11: OSI resource problem with device \NET.$LAPX.#Z0004BW on call APS_ASSOC_CONNECTREQ returned with -1001, 140

Compatibility Distributor ($Z0)

The compatibility distributor ($Z0) was created to allow backward compatibility with the operator process that existed previously. HP no longer supports OPRLOG and related functions. However, the compatibility distributor still sends operator messages to a console device during system load.

Figure 1-1 Operator Messages and the EMS Environment

Forwarding Distributor

The forwarding distributor filters specific events and sends them to the EMS collector process on another server in the network. The EMS collector process on the destination server saves forwarded event messages in its EMS log file.

Operator Message Types

Operator messages are grouped according to type. This manual documents the following types of messages:

Common Messages

Common messages are common to several different subsystems. Common messages have negative event numbers and are divided into the following ranges:

Beginning of Range	End of Range	Event Type
-1	-999	Common communications subsystem events (ZCOM)
-10000	-10999	Common diagnostic events (ZCDG)
-32600	-32767	Common events (ZCMK)

The following example shows a common message:

-4 ldevname LDEV ldev I/O ADDR: (cpu, chan, ctl, unit) Process Fatal Error, Cause: [cause]

EMS Messages

Three types of messages are sent under the EMS subsystem ID:

• EMS messages 1 through 511 have not been fully converted to Distributed Systems Management (DSM) display format.

• EMS messages 512 either have not been fully converted to DSM display format or are user-written messages that are displayed by user-written applications. User-written operator messages are not documented in this manual. Currently, the LINKMON process, the Spooler subsystem, and certain HP NonStop SQL/MX components display EMS 512 messages.

• EMS messages 513 and higher originate from the EMS subsystem itself. Messages numbered 513 through 999 originate from EMS collectors. Messages higher than 1000 originate from EMS distributors.

OSS Messages

Two sets of messages are sent under the OSS subsystem ID:

• OSS messages 1 through 4 and 13 and higher are generated by the OSS subsystem itself.

• OSS messages 5 through 12 are user-written messages that are sent by user-written OSS applications. The message numbers are assigned by severity level. This manual documents the severity level for each message and the message format but does not document actual message text.

Subsystem Messages

Subsystem messages are in DSM display format and are generated by a specific subsystem.

The Message Header

Operator messages are preceded by a header that contains the following information:

Only portions of the subsystem ID and the event number are shown as header information in this manual.

How to Find a Message in This Manual

To look up an operator message in this manual, you must know the message’s subsystem name and event number. The chapters in this manual are organized alphabetically by subsystem names. Messages within each chapter are in order by event number.

Finding the Subsystem Name and Event Number

The subsystem name (or sometimes the subsystem number) is part of the subsystem ID:

• For operator messages displayed on the ViewPoint console application (D-series), use the ViewPoint event-detail screen to find the message’s subsystem ID and event number. If you are using ViewPoint and notice events without a subsystem ID, subsystem name, and event number, refer to Chapter 31 to find out what the message means. The message’s subsystem ID and event number appear in the header in the following format:

  owner-name.subsystem-name.version event-number

  For example:

  TANDEM.TCPIPSA.D20 001001

• While the output format varies slightly, both the TSM event viewer (G‑series) and OSM event viewer (G‑series and H-series) display the following information for each operator message retrieved:

  • Date and time

  • Subsystem ID

  • Event name, number, and subject

    If you see events without a subsystem ID, subsystem name, and event number, refer to Chapter 31 to find out what the message means.

• For event messages sent to printers, log files, and terminals used by the printing distributor, the message’s subsystem ID and event number appear in the following format:

  owner-name.subsystem-name.version event-number

  For example:

  TANDEM.TMF.D20 000041

The message’s subsystem ID and event number variables include the following:

owner-name	HP for all messages described in this manual.
subsystem-name	Subsystem name. In rare cases, the subsystem number appears instead of the name.
version	Release number (for example, D20).
event-number	Event number.

List of Subsystems

Table 1-1 lists the names, numbers, and descriptions of the subsystems that generate the messages described in this manual. The chapters in this manual are organized alphabetically by the subsystem names listed in this table.

Table 1-1 Subsystem Names and Numbers

Subsystem Name	Subsystem Number	Subsystem Acronym	Description
APPCLSTR	252	ZACS	APPCLSTR (Application Cluster Services)
AM3270	22	ZAM3	AM3270 access method
ASAP	226	ZASP	Availability, Statistics and Performance
ATM	172	ZATM	ATM
ATP6100	24	ZATP	6100 Asynch Terminal
BRU	255	ZBRU	Backup and Restore 2.0
BRT	142	ZBRT	BACKUP and Tape Reader
CEV	198	ZCEV	TSM EMS Event Viewer
CIP	259	ZCIP	Cluster I/O Protocols
CL2	85	ZCL2	Common Level 2 (CL2) modules
CLOCK	66	ZCLK	System clock
CMAP	263	ZCMP	Complex Mgr Auxiliary Process
CMN	325	ZCMN	Cluster Connectivity Monitor Process
COM-KRNL	83	ZCMK	Common messages
CP6100	26	ZCP6	CP6100
CPU	15	ZCPU	Processor microcode
DBIOPROC	209	ZDIO	Direct Bulk I/O
DCE	188	ZDCE	Distributed Computing Environment
DCT	297	ZDCT	Remote Destination Control Table Monitor Process
DISK	31	ZDSK	Disk process
DLL	260	ZDLL	Dynamic Link Library
DLSOS	271	ZSOS	Data Loader Heartbeat Monitor
DMP	151	ZDMP	HP Tandem Failure Data System
DNS	5	ZDNS	Distributed Name Service
DSC	34	ZDSC	Dynamic System Configuration
DSMSCM	135	ZPHI	Distributed System Management/Software Configuration Manager
DSNM	82	ZDSN	Distributed Systems Network Management, referred to as Distributed Systems Management Solutions (DSMS)
EM3270	109	ZEM3	EM3270 emulator
EMS	12	ZEMS	Event Management Service
EMSTEXT	N.A.	N.A.	EMSTEXT unable to display an event message
ENVOY	107	ZENV	Envoy
ETHSA	217	ZESA	SNMP Ethernet/Token Ring Subagent
ETN32SRV	221	ZTN3	ETN32SRV Guardian Enhanced TN32SRV Server
EXF	88	ZEXF	EnvoyACP/XF
EXPAND	30	ZEXP	Expand networking tool
FASTPTCP	240	ZFSP	FASTPTCP
FCSM	262	ZFSM	FCS Monitor
FILE	68	ZFIL	File system
GDSX	33	ZGDS	Extended General Device Support
GUARDIO	69	ZGIO	Low-level I/O
GUARDLIB	46	ZGRD	Guardian
HRM	180	ZHRM	Host Resources Subagent
IPB	16	ZIPB	Interprocessor bus interrupt handler
IPC	203	ZIPC	NonStop Kernel Message System
IPXSA	196	ZISA	IPX/SPX Subagent
IPX-SPX	164	ZIPX	Interprocessor Extended/Subsystem Processor Extended
KRN	199	ZKRN	Kernel Subsystem Manager
MEASURE	141	ZMSR	Measure
MEU	326	MEU	Maintenance Entity Unit
MEV	186	ZMEV	Multi Event Viewer (MEV) subsystem
MHS	45	ZMHS	Open Systems Interconnection/Message Handling Services
MONITOR	72	ZMON	System monitor
MSGSYS	73	ZMSG	Message system
NBT	179	ZNBT	NetBIOS over TCP/IP
NBX	178	ZNBX	NetBIOS over IPX/SPX
NCSL	328	ZNCS	NonStop Connection Services Library
NETBATCH	9	ZBAT	NetBatch
NFS	77	ZNFS	Network File System (NFS) for Open System Services (OSS)
NNM	117	ZNNM	NonStop NET/MASTER (NNM) subsystem
NSC	204	ZNSC	NonStop C Multitasking Engine
NSDS	153	ZNDS	NonStop Directory Services
NSK	183	ZNSK	NonStop Kernel
ODBC/MP	234	ZNOS	NonStop Open Database Connectivity Server
ODBC/MX	231	ZMXO	Open Database Connectivity/Mail Exchange
ODP	2	ZODP	Optical disk process
OMF	127	ZOMF	Object Monitoring Facility
ONS	182	ZONS	Open Notification Service (ONS)
OSIAPLMG	97	ZOSA	Open Systems Interconnection/Application Manager
OSIAS	62	ZOSI	Open Systems Interconnection/Application Services
OSIFTAM	136	ZFTM	Open Systems Interconnection/File Transfer, Access, and Maintenance System
OSITS	63	ZOS4	Open Systems Interconnection/Transport Services
OSM	250	ZOSM	Open System Management
OSS	143	ZOSS	Open System Services
OSSTTY	245	ZTTY	Open System Services Pseudo-Terminal Utility
OVNM	253	ZOVN	OpenView Agent for HP NonStop servers
PAM	215	ZPAM	Port Access Method
PATHWAY	8	ZPWY	NonStop TS/MP and NonStop Pathway/TS
QIO	166	ZQIO	Shared I/O for Transmission Control Protocol/Internet Protocol (TCP/IP)
RAL	175	ZRAL	Resource Access Layer
RDF	211	ZRDF	Remote Duplicate Database Facility
RPC	79	ZRPC	Remote Procedure Call
RSC	160	ZRSC	Remote Server Call
SCL	218	ZSCL	HP NonStop ServerNet Cluster
SCP	25	ZSCP	Subsystem Control Point
SCS	122	ZSCS	SQL Communication subsystem
SCSI	190	ZSCZ	Open SCSI
SFG	94	ZSFG	Safeguard security product
SLSA	193	ZLAN	ServerNet LAN Systems Access
SMD	205	ZSMD	Open SCSI Module Driver
SMF	112	ZSMF	Storage Management Foundation
SMN	237	ZSMN	External ServerNet SAN
SMP	155	ZSMP	NonStop SNMP (Simple Network Management Protocol)
SNAX	36	ZSX1	SNAX Advanced Peer Networking (SNAX/APN) and SNAX Extended Facility (SNAX/XF)
SNAX-APC	29	ZAPC	SNAX Advanced Program Communication (SNAX/APC)
SNAX-CDF	37	ZCDF	SNAX Cross-Domain Facility (SNAX/CDF)
SNAX-CRE	133	ZCRE	SNAX Creator-2
SNAX-HLS	110	ZHLS	SNAX High-Level Support (SNAX/HLS)
SNT	201	ZSNT	ServerNet Error Handler
SPL	57	ZSPL	Spooler
SPR	206	ZSPR	Service Processor
SQLAUDIT	162	ZAUD	NonStop SQL/MP Audit Fix-up (a feature of SQL)
SQL/MP	161	ZSQL	HP NonStop SQL/MP
SQL/MX	236	ZMXS	HP NonStop SQL/MX
SRL	184	ZSRL	Shared run‑time libraries
SSI	150	ZSSI	Storage Server Interface
STO	189	ZSTO	Storage Subsystem
SWAN	N.A.	N.A.	SWAN Concentrator (sends events through Trap Multiplexer, TRAPMUX, subsystem)
SXCM	147	ZSCX	SNAX Connection Manager
SYSH	131	ZSYH	Syshealth
TACL	3	ZTAC	HP Tandem Advanced Command Language
TAG	187	ZTAG	Transport Agent
TAPE	4	ZTAP	Tape process
TCPIP	80	ZTCI	Transmission Control Protocol/Internet Protocol (TCP/IP)
TCPIPv6	246	ZTC6	TCP/IPv6
TCPIPSA	202	ZTSA	TCP/IP SNMP Subagent
TCPMAN	220	ZTCP	TCP/IP Manager
TELSERV	91	ZTNT	Telserv subsystem
TLAM	19	ZLAM	HP Tandem LAN Access Method/Multilan connectivity tool
TMDS	20	ZTMD	HP Tandem Maintenance and Diagnostic System
TMF	10	ZTMF	HP Transaction Management Facility (TMF)
TN32SERV	125	ZTN3	TN32SERV access method
TR3271	40	ZTR3	TR3271 access method
TRAPMUX	185	ZTMX	Trap Multiplexer subagent
TSE	191	ZTSE	NonStop TS/MP for HP NonStop Tuxedo users
TSM	194	ZTSM	TSM
TTALK	112	ZTLK	TandemTalk
TUXEDO	208	ZTUX	NonStop Tuxedo
VHS	138	ZVHS	Virtual Hometerm System
VIEWPT	60	ZVPT	ViewPoint console application
WANMGR	176	ZWAN	Wide Area Network subsystem
WEBSERV	210	ZWEB	iTP Secure WebServer
WMSVCS	165	ZWMS	Workload Management Services
X25	41	ZX25	X.25 access method
XIO	200	ZXIO	NonStop Kernel XIO (extended I/O)
YMP	197	ZYMP	YMIOP maintenance I/O process

 

Critical Events

Critical events, such as the loss of a device or the occurrence of certain errors, are events for which the consequences could be serious. Messages for critical events are displayed as follows:

Common Message Variables

Variables are used in most operator messages. Some of these variables are common to many operator messages. EMS message 104 lists some of the variables that are most common in operator messages and illustrates how they are formatted in this manual.

Message Descriptions

Each message description contains the following information:

Additional Information

The appendixes in this manual contain additional information about subsystem-specific parameters and about error numbers issued by certain procedures.

Subsystem-Specific Parameters

Appendix A, contains information about decoding subsystem‑specific parameters returned by some messages.

Error Numbers

Many operator messages refer to error numbers. These error numbers are issued by the file system and by various procedures. The error numbers are listed and briefly described in the following appendixes:

Appendix	Title
B	File-System Errors
C	NEWPROCESS Errors
D	Process Creation Errors
E	ALLOCATESEGMENT Errors
F	SEGMENT_ALLOCATE_ Errors

For cause, effect, and recovery information for messages generated by these errors, refer to the Guardian Procedure Errors and Messages Manual.