Messages and Codes v2

IBM Z NetView
Version 6 Release 3
Messages and Codes

Volume 2 (DUI-IHS)
IBM
GC27-2857-08
Note
Before using this information and the product it supports, read the information in “Notices” on page
929.
This edition applies to version 6, release 3 of IBM Z NetView (product number 5697-NV6 ) and to all subsequent
versions, releases, and modifications until otherwise indicated in new editions.
This edition replaces GC27-2857-06.
© Copyright International Business Machines Corporation 1997, 2019.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents
About this publication............................................................................................v

Intended audience....................................................................................................................................... v
Publications.................................................................................................................................................. v
IBM Z NetView library............................................................................................................................. v
Related publications ............................................................................................................................ vii
Terminology in this Library................................................................................................................... vii
Using IBM Z NetView online help......................................................................................................... vii
Accessing publications online............................................................................................................. viii
Ordering publications ..........................................................................................................................viii
Accessibility .............................................................................................................................................. viii
Tivoli user groups.......................................................................................................................................viii
Support information.................................................................................................................................. viii
Conventions used in this publication.......................................................................................................... ix
Typeface conventions ........................................................................................................................... ix
Operating system-dependent variables and paths.............................................................................. ix
Syntax diagrams.....................................................................................................................................ix
Chapter 1. DUI Prefix Messages............................................................................. 1
Chapter 2. DWO Prefix Messages....................................................................... 143
Chapter 3. EJN Prefix Messages......................................................................... 289
Chapter 4. EKG Prefix Messages.........................................................................291
Chapter 5. EKGK Prefix Messages...................................................................... 365
Chapter 6. EKGV Prefix Messages...................................................................... 369
Chapter 7. EZL Prefix Messages......................................................................... 381
Chapter 8. FKV Prefix Messages......................................................................... 459
Chapter 9. FKX Prefix Messages.........................................................................489
Chapter 10. FLB Prefix Messages....................................................................... 521
Chapter 11. FLC Prefix Messages....................................................................... 587
Chapter 12. FLCI Prefix Messages...................................................................... 637
Chapter 13. IHS Prefix Messages Issued from the Host....................................... 643
Chapter 14. IHS Prefix Messages Issued from the NetView Management Console
Workstation...................................................................................................699
Chapter 15. GMFHS Method Error Messages....................................................... 855
iii
Appendix A. Codes.............................................................................................911
NetView Abend Codes............................................................................................................................. 911
Alias Sense Codes....................................................................................................................................924
Global Sense Codes........................................................................................................................... 924
Specific-Request Sense Codes.......................................................................................................... 924
LUC Conversation Request Service Return Codes and Sense Codes.....................................................925
Generic Alert Code Points....................................................................................................................... 926
Code Point Format..............................................................................................................................926
Resource Types (X'05')...................................................................................................................... 926
Recommended Actions (X'81').......................................................................................................... 927
Detail Data (X'82').............................................................................................................................. 927
Detail Data (X'85').............................................................................................................................. 927
Actual Actions (X'86').........................................................................................................................927
Generic Alert Data/Resolution Data (X'92')...................................................................................... 927
Probable Causes (X'93').....................................................................................................................928
User Causes (X'94')............................................................................................................................928
Install Causes (X'95')......................................................................................................................... 928
Failure Causes (X'96')........................................................................................................................ 928
Notices..............................................................................................................929
Programming Interfaces..........................................................................................................................930
Trademarks..............................................................................................................................................930
Privacy policy considerations.................................................................................................................. 930
iv
About this publication
The IBM Z® NetView® product provides advanced capabilities that you can use to maintain the highest
degree of availability of your complex, multi-platform, multi-vendor networks and systems from a single
point of control. This publication, IBM Z NetView Messages and Codes Volume 2 (DUI-IHS), lists the
messages produced by the NetView program. Many of the messages described in this publication can be
used in NetView automation. See the IBM Z NetView Automation Guide for more information about
NetView automation. Messages that are new or changed for this release are listed in the IBM Z NetView
Installation: Migration Guide. You can display the descriptions for SNA or VTAM® sense codes that you
encounter in a NetView message by using the SENSE command list. For more information, see the
Systems Network Architecture Formats manual or the appropriate VTAM manual.
Intended audience
This publication is for system programmers and operators who need explanations of and responses to the
messages produced by the NetView program.
Publications
This section lists publications in the IBM Z NetView library and related documents. It also describes how
to access NetView publications online and how to order NetView publications.
IBM Z NetView library

The following documents are available in the IBM Z NetView library:
• Administration Reference, SC27-2869, describes the NetView program definition statements required
for system administration.
• Application Programmer's Guide, SC27-2870, describes the NetView program-to-program interface
(PPI) and how to use the NetView application programming interfaces (APIs).
• Automation Guide, SC27-2846, describes how to use automated operations to improve system and
network efficiency and operator productivity.
• Command Reference Volume 1 (A-N), SC27-2847, and Command Reference Volume 2 (O-Z), SC27-2848,
describe the NetView commands, which can be used for network and system operation and in
command lists and command procedures.
• Installation: Configuring Additional Components, GC27-2851, describes how to configure NetView
functions beyond the base functions.
• Installation: Configuring the NetView Enterprise Management Agent, GC27-2853, describes how to
install and configure the IBM Z NetView Enterprise Management Agent.
• Installation: Getting Started, GI11-9443, describes how to install and configure the base NetView
program.
• Installation: Migration Guide, GC27-2854, describes the new functions that are provided by the current
release of the NetView product and the migration of the base functions from a previous release.
• IP Management, SC27-2855, describes how to use the NetView product to manage IP networks.
• Messages and Codes Volume 1 (AAU-DSI), GC27-2856, and Messages and Codes Volume 2 (DUI-IHS),
GC27-2857, describe the messages for the NetView product, the NetView abend codes, the sense
codes that are included in NetView messages, and generic alert code points.
• Programming: Pipes, SC27-2859, describes how to use the NetView pipelines to customize a NetView
installation.
© Copyright IBM Corp. 1997, 2019 v

• Programming: REXX and the NetView Command List Language, SC27-2861, describes how to write
command lists for the NetView product using the Restructured Extended Executor language (REXX) or
the NetView command list language.
• Security Reference, SC27-2863, describes how to implement authorization checking for the NetView
environment.
• Troubleshooting Guide, GC27-2865, provides information about documenting, diagnosing, and solving
problems that occur in the NetView product.
• Tuning Guide, SC27-2874, provides tuning information to help achieve certain performance goals for
the NetView product and the network environment.
• User's Guide: Automated Operations Network, SC27-2866, describes how to use the NetView
Automated Operations Network (AON) component, which provides event-driven network automation, to
improve system and network efficiency. It also describes how to tailor and extend the automated
operations capabilities of the AON component.
• User's Guide: NetView, SC27-2867, describes how to use the NetView product to manage complex,
multivendor networks and systems from a single point.
• User's Guide: NetView Enterprise Management Agent, SC27-2876, describes how to use the NetView
Enterprise Management Agent.
• Using Tivoli System Automation for GDPS/PPRC HyperSwap Manager with NetView, GI11-4704, provides
information about the Tivoli® System Automation for GDPS®/PPRC HyperSwap® Manager with NetView
feature, which supports the GDPS and Peer-to-Peer Remote Copy (PPRC) HyperSwap Manager services
offering.
• Licensed Program Specifications, GC31-8848, provides the license information for the NetView product.
• Program Directory for IBM Z NetView US English, GI11-9444, contains information about the material
and procedures that are associated with installing the NetView product.
• Program Directory for IBM Z NetView Japanese, GI11-9445, contains information about the material and
procedures that are associated with installing the NetView product.
• Program Directory for IBM Z NetView Enterprise Management Agent, GI11-9446, contains information
about the material and procedures that are associated with installing the IBM Z NetView Enterprise
Management Agent.
The following books are archived:
• Customization Guide, SC27-2849, describes how to customize the NetView product and points to
sources of related information.
• Data Model Reference, SC27-2850, provides information about the Graphic Monitor Facility host
subsystem (GMFHS), SNA topology manager, and MultiSystem Manager data models.
• Installation: Configuring Graphical Components, GC27-2852, describes how to install and configure the
NetView graphics components.
• Programming: Assembler, SC27-2858, describes how to write exit routines, command processors, and
subtasks for the NetView product using assembler language.
• Programming: PL/I and C, SC27-2860, describes how to write command processors and installation exit
routines for the NetView product using PL/I or C.
• Resource Object Data Manager and GMFHS Programmer's Guide, SC27-2862, describes the NetView
Resource Object Data Manager (RODM), including how to define your non-SNA network to RODM and
use RODM for network automation and for application programming.
• SNA Topology Manager Implementation Guide, SC27-2864, describes planning for and implementing
the NetView SNA topology manager, which can be used to manage subarea, Advanced Peer-to-Peer
Networking, and TN3270 resources.
• User's Guide: NetView Management Console, SC27-2868, provides information about the NetView
management console interface of the NetView product.
vi IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Related publications
You can find additional product information on the IBM Z NetView web site at https://www.ibm.com/us-
en/marketplace/ibm-tivoli-netview-for-zos.
For information about the NetView Bridge function, see Tivoli NetView for OS/390 Bridge Implementation,
SC31-8238-03 (available only in the V1R4 library).
Terminology in this Library

The following terms are used in this library:
CNMCMD
For the CNMCMD member and the members that are included in it using the %INCLUDE statement
CNMSTYLE
For the CNMSTYLE member and the members that are included in it using the %INCLUDE statement
DSIOPF
For the DSIOPF member and the members that are included in it using the %INCLUDE statement
IBM® Tivoli Netcool®/OMNIbus
For either of these products:
• IBM Tivoli Netcool/OMNIbus
• IBM Tivoli OMNIbus and Network Manager
MVS™
For z/OS® operating systems
MVS element
For the base control program (BCP) element of the z/OS operating system
NetView
For the following products:
• IBM Z NetView version 6 release 3
• IBM Tivoli NetView for z/OS version 6 release 2 modification 1
• NetView releases that are no longer supported
PARMLIB
For SYS1.PARMLIB and other data sets in the concatenation sequence
VTAM
For Communications Server - SNA Services
Unless otherwise indicated, topics to programs indicate the latest version and release of the programs. If
only a version is indicated, the topic is to all releases within that version.
When a topic is made about using a personal computer or workstation, any programmable workstation
can be used.
Using IBM Z NetView online help

The following types of IBM Z NetView mainframe online help are available, depending on your installation
and configuration:
• General help and component information
• Command help
• Message help
• Sense code information
• Recommended actions
About this publication vii

Accessing publications online
IBM posts publications for this and all other products, as they become available and whenever they are
updated, to the IBM Knowledge Center at https://www.ibm.com/support/knowledgecenter. You can find
IBM Z NetView documentation on IBM Z NetView Knowledge Center.
Note: If you print PDF documents on other than letter-sized paper, set the option in the Print window that
enables Adobe Reader to print letter-sized pages on your local paper.
Ordering publications
You can order many Tivoli publications online at http://www.ibm.com/e-business/linkweb/publications/
servlet/pbi.wss
You can also order by telephone by calling one of these numbers:
• In the United States: 800-426-4968
• In Canada: 800-879-2755
In other countries, contact your software account representative to order Tivoli publications. To locate
the telephone number of your local representative, perform the following steps:
1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.
2. Select your country from the list and click the grey arrow button beside the list.
3. Click About this site to see an information page that includes the telephone number of your local
representative.
Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to
use software products successfully. Standard shortcut and accelerator keys are used by the product and
are documented by the operating system. Refer to the documentation provided by your operating system
for more information.
For additional information, see the Accessibility appendix in the User's Guide: NetView.
Tivoli user groups

Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with
information to assist them in the implementation of Tivoli Software solutions. Through these groups,
members can share information and learn from the knowledge and experience of other Tivoli users.
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following
ways for you to obtain the support you need:
Online
Please follow the instructions located in the support guide entry: https://www.ibm.com/support/
home/pages/support-guide/?product=4429363.
Troubleshooting information
For more information about resolving problems with the IBM Z NetView product, see the IBM Z
NetView Troubleshooting Guide. You can also discuss technical issues about the IBM Z NetView
product through the NetView user group located at https://groups.io/g/NetView. This user group is for
IBM Z NetView customers only, and registration is required. This forum is also monitored by
interested parties within IBM who answer questions and provide guidance about the NetView
viii IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

product. When a problem with the code is found, you are asked to open an official case to obtain
resolution.
Conventions used in this publication

This section describes the conventions that are used in this publication.
Typeface conventions
This publication uses the following typeface conventions:
Bold
• Lowercase commands and mixed case commands that are otherwise difficult to distinguish from
surrounding text
• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list
boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,
property sheets), labels (such as Tip:, and Operating system considerations:)
• Keywords and parameters in text
Italic
• Citations (examples: titles of publications, diskettes, and CDs
• Words defined in text (example: a nonswitched line is called a point-to-point line)
• Emphasis of words and letters (words as words example: "Use the word that to introduce a
restrictive clause."; letters as letters example: "The LUN address must start with the letter L.")
• New terms in text (except in a definition list): a view is a frame in a workspace that contains data.
• Variables and values you must provide: ... where myname represents...
Monospace
• Examples and code examples
• File names, programming keywords, and other elements that are difficult to distinguish from
surrounding text
• Message text and prompts addressed to the user
• Text that the user must type
• Values for arguments or command options
Operating system-dependent variables and paths

For workstation components, this publication uses the UNIX convention for specifying environment
variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for environment variables
and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment
variables are not always the same in the Windows and UNIX environments. For example, %TEMP% in
Windows environments is equivalent to $TMPDIR in UNIX environments.
Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions.
Syntax diagrams
The following syntax elements are shown in syntax diagrams. Read syntax diagrams from left-to-right,
top-to-bottom, following the horizontal line (the main path).
• “Symbols” on page x
• “Parameters” on page x
• “Punctuation and parentheses” on page x
About this publication ix

• “Abbreviations” on page xi
For examples of syntax, see “Syntax examples” on page xi.
Symbols
The following symbols are used in syntax diagrams:
Marks the beginning of the command syntax.
Marks the end of the command syntax.
Indicates that the command syntax is continued on the next line.
Indicates that a statement is continued from the previous line.

|
Marks the beginning and end of a fragment or part of the command syntax.
Parameters
The following types of parameters are used in syntax diagrams:
Required
Required parameters are shown on the main path.
Optional
Optional parameters are shown below the main path.
Default
Default parameters are shown above the main path. In parameter descriptions, default parameters
are underlined.
Syntax diagrams do not rely on highlighting, brackets, or braces. In syntax diagrams, the position of the
elements relative to the main syntax line indicates whether an element is required, optional, or the
default value.
When you issue a command, spaces are required between the parameters unless a different separator,
such as a comma, is specified in the syntax.
Parameters are classified as keywords or variables. Keywords are shown in uppercase letters. Variables,
which represent names or values that you supply, are shown in lowercase letters and are either italicized
or, in NetView help, displayed in a differentiating color.
In the following example, the USER command is a keyword, the user_id parameter is a required variable,
and the password parameter is an optional variable.
USER user_id
password
Punctuation and parentheses

You must include all punctuation that is shown in the syntax diagram, such as colons, semicolons,
commas, minus signs, and both single and double quotation marks.
When an operand can have more than one value, the values are typically enclosed in parentheses and
separated by commas. For a single value, the parentheses typically can be omitted. For more information,
see “Multiple operands or values” on page xii.
If a command requires positional commas to separate keywords and variables, the commas are shown
before the keywords or variables.
x IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

When examples of commands are shown, commas are also used to indicate the absence of a positional
operand. For example, the second comma indicates that an optional operand is not being used:
COMMAND_NAME opt_variable_1,,opt_variable_3
You do not need to specify the trailing positional commas. Trailing positional and non-positional commas
either are ignored or cause a command to be rejected. Restrictions for each command state whether
trailing commas cause the command to be rejected.
Abbreviations
Command and keyword abbreviations are listed in synonym tables after each command description.
Syntax examples
The following examples show the different uses of syntax elements:
• “Required syntax elements” on page xi
• “Optional syntax elements” on page xi
• “Default keywords and values” on page xi
• “Multiple operands or values” on page xii
• “Syntax that is longer than one line” on page xii
• “Syntax fragments” on page xii
Required syntax elements

Required keywords and variables are shown on the main syntax line. You must code required keywords
and variables.
REQUIRED_KEYWORD required_variable
A required choice (two or more items) is shown in a vertical stack on the main path. The items are shown
in alphanumeric order.
REQUIRED_OPERAND_OR_VALUE_1
REQUIRED_OPERAND_OR_VALUE_2
Optional syntax elements

Optional keywords and variables are shown below the main syntax line. You can choose not to code
optional keywords and variables.
OPTIONAL_OPERAND
A required choice (two or more items) is shown in a vertical stack below the main path. The items are
shown in alphanumeric order.
OPTIONAL_OPERAND_OR_VALUE_1
OPTIONAL_OPERAND_OR_VALUE_2
Default keywords and values

Default keywords and values are shown above the main syntax line in one of the following ways:
• A default keyword is shown only above the main syntax line. You can specify this keyword or allow it to
default. The following syntax example shows the default keyword KEYWORD1 above the main syntax
line and the rest of the optional keywords below the main syntax line.
About this publication xi

• If an operand has a default value, the operand is shown both above and below the main syntax line. A
value below the main syntax line indicates that if you specify the operand, you must also specify either
the default value or another value shown. If you do not specify the operand, the default value above the
main syntax line is used. The following syntax example shows the default values for operand OPTION=*
above and below the main syntax line.
KEYWORD1 OPTION=*
COMMAND_NAME
KEYWORD1 OPTION= *
KEYWORD2 VALUE1
KEYWORD3 VALUE2
Multiple operands or values

An arrow returning to the left above a group of operands or values indicates that more than one can be
selected or that a single one can be repeated.
KEYWORD= (
,
REPEATABLE_OPERAND_OR_VALUE_1
value_n )
Syntax that is longer than one line

If a diagram is longer than one line, each line that is to be continued ends with a single arrowhead and the
following line begins with a single arrowhead.
OPERAND1 OPERAND2 OPERAND3 OPERAND4 OPERAND5 OPERAND6
OPERAND7 OPERAND8
Syntax fragments
Some syntax diagrams contain syntax fragments, which are used for lengthy, complex, or repeated
sections of syntax. Syntax fragments follow the main diagram. Each syntax fragment name is mixed case
and is shown in the main diagram and in the heading of the fragment. The following syntax example
shows a syntax diagram with two fragments that are identified as Fragment1 and Fragment2.
COMMAND_NAME Fragment1
Fragment2
Fragment1
KEYWORD_A= valueA KEYWORD_B KEYWORD_C
Fragment2
KEYWORD_D KEYWORD_E= valueE KEYWORD_F
xii IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Chapter 1. DUI Prefix Messages
This section describes the DUI messages from the NetView program.
DUI000E MESSAGE NUMBER messagenum System programmer response
IS NOT IN MESSAGE CSECT Locate the accompanying DSI769 message in the
csectname. NOTIFY THE SYSTEM network log. This message contains the return code
PROGRAMMER. that explains the reason for the failure.
Explanation DUI101I NETCONV COMMAND PROCESSED

SUCCESSFULLY.
The requested message was not found in the specified COMMUNICATION TO LU luname
CSECT. STARTED.
Message Variables
Explanation
messagenum
The message number requested. The NETCONV START request processed successfully.
csectname Message Variables
The message CSECT specified for this request.
luname
The name of the logical unit (LU) specified on the
System action NETCONV command.
Processing continues.
System action
Operator response Processing continues.
Notify the system programmer.
DUI102I LU luname HAS ALREADY BEEN
STARTED BY operatorid.
System programmer response CONDITION CODE = condcode
Contact IBM Software Support.
Explanation
DUI100W LU 6.2 COMMUNICATIONS SETUP
FOR LU luname HAS FAILED. THE The NETCONV START request is ignored because LU
NETCONV START COMMAND IS 6.2 communication to the specified LU has already
REJECTED. been established by another operator, or a NETCONV
START command is currently being processed.
Explanation Message Variables
The LU 6.2 communication setup has failed. luname
Message Variables The name of the LU specified on the NETCONV
command.
luname
operatorid
The LU name specified on the NETCONV
The ID of the operator who had previously issued
command.
the NETCONV START request.
condcode
System action
The condition code, which is one of the following:
The NETCONV command is ignored.
1
Communication has already been established
Operator response by the other operator.
Notify the system programmer. 2
A NETCONV START command issued by the
listed operator is currently outstanding.
© Copyright IBM Corp. 1997, 2019 1

System action System programmer response
The request is ignored. See IBM Z NetView Programming: Assembler for the
meaning of the return code.
Operator response DUI105I THE NETCONV COMMAND MAY BE
Upon receiving this message, the operator must ISSUED FROM STATUS FOCAL
recycle the CNMTAMEL task before attempting to POINT HOSTS ONLY. host IS NOT
issue the NETCONV command again. A STATUS FOCAL POINT.
DUI103E NETCONV START COMMAND

Explanation
CANNOT BE PROCESSED. task
TASK IS NOT ACTIVE. The NETCONV command was issued from a host that
is not a status focal point.
The NetView message queuing service request host
(DSIMQS) for the NETCONV START request failed The name of the host.
because the target task task is not active.
Message Variables System action
task The NETCONV command is ignored.
The name of the task that was not active.
DUI106E COMMUNICATION TO LU luname
TERMINATED ABNORMALLY:
System action VTAM TPEND.
The NETCONV START request is ignored.
Explanation
Operator response VTAM ended and therefore the LU 6.2 conversations
Start the indicated task and reissue the NETCONV for luname also ended abnormally.
command. Message Variables
DUI104E NETCONV START FOR LU luname luname
REJECTED. DSIMQS FAILED WITH The name of the LU whose LU 6.2 conversations
RC=retcode. have ended.
Explanation System action

The NetView message queueing service request The LU 6.2 conversations end.
(DSIMQS) for the NETCONV START request failed.
Message Variables Operator response
luname Notify the system programmer.
The name of the LU specified on the NETCONV
command. System programmer response
retcode Determine the reason VTAM ended, restart VTAM,
The return code from the NetView Message establish connectivity between the host and the
Queueing Service (hexadecimal). workstation, and reissue the NETCONV command.
System action DUI107I A DUPLICATE NETCONV START

REQUEST WAS ISSUED FOR LU
The NETCONV START request is ignored. luname. THE REQUEST IS
IGNORED.
Operator response
Notify the system programmer. Explanation
The NETCONV START request has already been
issued.
Message Variables
2 IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

luname System action
The LU 6.2 conversations end.
command.
Operator response
System action
Reissue the NETCONV command from another
The request is ignored.
operator station task (OST).
Operator response
System programmer response
Upon receiving this message, the operator must
Determine the reason for the abend and correct the
recycle the CNMTAMEL task before attempting to
error.
issue the NETCONV command again.
DUI108I A NETCONV STOP REQUEST FOR
LU luname THAT WAS ISSUED BY
OPERATOR LOGOFF.
operatorid COULD NOT BE
PROCESSED.
Explanation
Explanation The operator that issued the NETCONV command for
LU luname logged off and therefore the LU 6.2
The system cannot process the NETCONV STOP
conversations ended abnormally.
request. This message can be generated by any of the
following situations: Message Variables
• Communication has already stopped because of the luname
ending of the CNMTAMEL task The name of the LU whose LU 6.2 conversations
• Communication is in the process of becoming active ended.
• The operator who issued the stop command did not

System action
issue the NETCONV START request.
Message Variables
luname Operator response
command. Reissue the NETCONV command from another
operator.
operatorid
The ID of the operator who issued the NETCONV DUI111E COMMUNICATION TO LU luname
STOP request. TERMINATED ABNORMALLY:
CNMTAMEL TASK IS
System action TERMINATING.
Explanation
The CNMTAMEL task on the host is ending and
TERMINATED ABNORMALLY: OST
therefore the LU 6.2 conversations to the workstation
ABEND.
with the LU name luname ended abnormally.
The operator station task (OST) that issued the luname

NETCONV command for LU luname abended and The name of the LU whose LU 6.2 conversations
therefore the LU 6.2 conversations ended abnormally. have been ended.
Message Variables
System action
luname
The name of the LU whose LU 6.2 conversations
ended.
Operator response
Chapter 1. DUI Prefix Messages 3

System programmer response System programmer response
Determine why the CNMTAMEL task is ending and Interpret the return codes in message DSI769I,
correct the error, if any. Restart the CNMTAMEL task correct the error, and re-establish communication
and reestablish communication using the NETCONV using the NETCONV command.
command.
DUI112E COMMUNICATION TO LU luname TERMINATED ABNORMALLY:
TERMINATED ABNORMALLY: FATAL ERROR
FATAL ERROR DURING RECEIVE.
Explanation
Explanation
The host encountered a fatal error while attempting to
The host encountered a fatal error while attempting to communicate with the workstation with the LU
receive data from the workstation with the LU name luname. The LU 6.2 conversations have been ended
luname. The LU 6.2 conversations have been ended abnormally.
abnormally.
Message Variables
Message Variables
luname
luname The name of the LU whose LU 6.2 conversations
The name of the LU whose LU 6.2 conversations have been ended.
have been ended.
System action
System action
Operator response
Operator response
Interpret the return codes in message DSI769I,
correct the error, and re-establish communication DUI115E COMMUNICATION TO LU luname
using the NETCONV command. TERMINATED ABNORMALLY:
RECEIVED DATA THAT WAS NOT
DUI113E COMMUNICATION TO LU luname VALID.
FATAL ERROR DURING SEND. Explanation
The host received data from the workstation with LU
Explanation
name luname. The data was not as expected and the
The host encountered a fatal error while attempting to LU 6.2 conversations have been ended abnormally.
send status data to the workstation with LU name
Message Variables
luname. The LU 6.2 conversations have been ended
abnormally. luname
Message Variables
have been ended.
luname
The name of the LU whose LU 6.2 conversations System action
have been ended.
System action
Operator response
Operator response

DUI116E COMMUNICATION TO LU luname large value specified for the MAXRESOURCES
TERMINATED ABNORMALLY: keyword.
WORKSTATION FATAL ERROR. Message Variables
Explanation network
The name of the network whose status cannot be
The workstation with the LU name luname monitored.
encountered an error. The workstation initiated LU 6.2
conversation termination. System action
Message Variables The task continues, but the status information for
luname network is not recorded.
have been ended. Operator response
System action
The LU 6.2 conversations end. System programmer response
Check the value specified for the MAXRESOURCES
Operator response keyword. If the value is larger than necessary for this
Notify the system programmer. network, reduce it and restart the task.
DUI119I COMMUNICATION TO LU luname
System programmer response TERMINATED NORMALLY DUE TO
Determine the error detected by the workstation, THE CLOSING OF THE
correct it, and re-establish communications using the COMMUNICATION SERVER.
NETCONV command.
Explanation
DUI117I NETCONV COMMAND PROCESSED
SUCCESSFULLY. The communication server at the specified logical unit
COMMUNICATION TO LU luname (LU) ended and brought down the LU 6.2 connection to
STOPPED. the status focal point.
Message Variables
Explanation
luname
A NETCONV STOP request was processed The LU name of the workstation where the
successfully. communication server ended.
Message Variables
System action
luname
The name of the logical unit (LU) specified on the Processing continues.
NETCONV command.
Operator response
System action If you desire communication to the workstation,
Processing continues on other requests. restart the communication server and reissue the
NETCONV command to that LU.
DUI118I STATUS OF NETWORK network
CANNOT BE MONITORED DUE TO DUI120I DATA WAS LOST DUE TO
STORAGE SHORTAGE. DATA FROM TERMINATION OF CNMTAMEL.
THIS NETWORK HAS BEEN
DISCARDED. Explanation
The status collector was sending data to the status
Explanation focal point when the CNMTAMEL task ended.
There is insufficient storage available to build the
tables required to monitor the status of resources in System action
network. This might be because of an unnecessarily
The CNMTAMEL task ends. Data is lost.

Operator response 3. If the workstation is not communicating with
another status focal point, notify the system
programmer.
System programmer response 4. Issue NETCONV ACTION=LIST OPID=ALL to

determine which workstations currently have an
Determine why the CNMTAMEL task ended and restart LU6.2 or TCP/IP session with this host.
the task. The status collector attempts to resend the
lost data. System programmer response
DUI121E THE NETCONV START COMMAND Check the version and release levels of the
HAS FAILED BECAUSE LU luname workstation and the NetView status focal point. Ensure
IS COMMUNICATING WITH that they are both running the same version and
ANOTHER STATUS FOCAL POINT, release of the NetView program.
IS RUNNING AN UNSUPPORTED
LEVEL OF NMC, OR IS ALREADY DUI122E CNMTAMEL FAILED TO RECEIVE
COMMUNICATING WITH THIS DATA FROM LU 'luname' DUE TO A
STATUS FOCAL POINT. STORAGE SHORTAGE.
REQUESTED AMOUNT = amount
BYTES.
Explanation
A NETCONV START command was issued to LU Explanation
luname, which has failed for one of the following
reasons: CNMTAMEL attempted to receive data from a server
workstation, but cannot get enough storage to satisfy
• LU luname is communicating with another status the request.
focal point, and an LU can communicate with only
one status focal point at a time. Message Variables
• The workstation is running a release of the NetView luname
program that is not compatible with the release used The LU for which CNMTAMEL tried to receive data.
by the status focal point. amount
• The workstation is already communicating with the The amount of storage that CNMTAMEL tried to
focal point through an LU6.2 or TCP/IP session. get.
Message Variables
System action
luname
The name of the independent LU defined in the The LU 6.2 session between the LU and the status
workstation. focal point host ends.
System action Operator response
The NETCONV START command is rejected and no Notify the system programmer of the storage
communication occurs between the status focal point problems. Reissue the NETCONV command to restart
and the LU. the LU that had ended.
Operator response System programmer response
Determine if the workstation is communicating with If the problem persists, contact IBM Software Support.
another status focal point. DUI123E COMMUNICATION TO LU luname
1. If it is possible, determine the host with which the TERMINATED ABNORMALLY:
workstation is to be communicating and reroute the WORKSTATION NOT
session. RESPONDING.
2. If the workstation is communicating with another
status focal point in error, issue the NETCONV Explanation
STOP command from that host, and reissue the The CNMTAMEL task detected a data server
NETCONV START command from the correct status workstation that is not responding, and has
focal point host. abnormally ended the LU 6.2 connections to the
workstation.

Message Variables operatorid
The ID of the NetView operator for which session
luname
data is requested.
The name of the LU whose LU 6.2 connections
ended. DUI126I NO OPERATOR IS
COMMUNICATING WITH ANY
System action WORKSTATION
All LU 6.2 connections to the data server workstation

Explanation
that is not responding are ended.
This message is returned when you issue the
Operator response NETCONV command specifying ACTION=LIST
OPID=ALL, and currently no operators have a session
Notify the system programmer. with any workstation.
System programmer response DUI150E ERROR IN 'initmem' AT RECORD

recnum. UNRECOGNIZED
Locate the data server workstation that is not INITIALIZATION STATEMENT.
responding. Attempt to determine the problem with THE STATEMENT IS IGNORED.
the workstation and correct it. The status focal point
has detected that the workstation is not responding Explanation
and cannot communicate with it. If the workstation
appears to be responding properly, the problem might An unrecognized initialization statement was
be the result of memory constraints at the data server encountered while reading the task initialization file.
workstation. Verify that you have enough memory on The format is not correct, or a keyword is misspelled.
the workstation by using the IBM Z NetView Tuning Message Variables
Guide. Restart the LU 6.2 connections to the
workstation by using the NETCONV command. initmem
The initialization member or file for the CNMTAMEL
DUI124I OPERATOR operatorid IS task.
COMMUNICATING WITH
WORKSTATION AT LU luname recnum
The number of the record where the name was
found.
Explanation
The specified operator has established a session with System action
the specified workstation LU through an LU 6.2
connection. This message is a response to issuing the The initialization statement is ignored.
NETCONV command with the ACTION=LIST
parameter. Operator response
Message Variables Notify the system programmer.
operatorid
The ID of the NetView operator that logged on. System programmer response
luname Examine the member or file named in the message.

The LU specified on the NETCONV command. Locate the line which is in error and correct it.
DUI125I OPERATOR operatorid IS NOT DUI152I VTAM APPCCMD MACRO appccmd

COMMUNICATING WITH ANY FAILED. REG15 = X'r15', REG0 =
WORKSTATIONS. X'r0', RCPRI = X'code1', RCSEC =
X'code2'.
Explanation
Explanation
The operator ID specified in the NETCONV
ACTION=LIST OPID=operatorid does not have a The VTAM APPCCMD macro appccmd failed.
session with any workstation. Message Variables
Message Variables appccmd
The VTAM APPCCMD macro that failed.

r15 System action
The value in Register 15 (used for problem
The module is not loaded.
analysis).
r0
Operator response
The value in Register 0 (used for problem
analysis). Notify the system programmer.
code1
The code used for problem analysis. System programmer response
code2 The DSILOD return code might be from the system
The code used for problem analysis. LOAD macro. If you cannot determine the problem,
contact IBM Software Support.
System action DUI156E ERROR READING 'initmem' AT
The LU 6.2 conversations end. RECORD recnum. NAME 'sfpmem'
IS TOO LONG. IT IS IGNORED.
Operator response
Explanation
The member or file name specified in the message was
too long. Names must be 1- to 8-characters.
Message Variables
initmem
DUI153E CNMTAMEL DETECTED A GMFHS
The member or file containing the erroneous
INSTALLATION ERROR: MODULE
record.
DUIFERSM NOT FOUND.
recnum
The number of the record where the name was
Explanation
found.
GMFHS has been installed but the module DUIFERSM sfpmem
was not successfully loaded. The member or file name that is not valid.
System action System action

The module DUIFERSM is not loaded. The statement is ignored. If valid member or file
names are found elsewhere, the CNMTAMEL task
Operator response continues to initialize. Otherwise the task ends.
Operator response
System programmer response Notify the system programmer.
DUI155E DSILOD FAILED FOR MODULE
module WITH RC= retcode. Edit the member or file named in the message to
check for incorrect or missing name specification in
the record shown in the message.
Explanation
Module module cannot be loaded. DUI157E DSIPUSH OF TERMINATION
ROUTINE FAILED WITH RC =
Message Variables retcode. NOTIFY THE SYSTEM
module PROGRAMMER.
The name of the module for which the load request
failed. Explanation
retcode The CNMTAMEL initialization module is unable to
The return code from DSILOD (hexadecimal). establish a termination routine.
Message Variables

retcode Operator response
The return code from the DSIPUSH macro
(hexadecimal).

System action
Examine the member or file named in the message.
The CNMTAMEL task ends.
Locate the specified keyword and either correct the
keyword or remove the line.
Operator response
DUI160I APPCCMD COMPLETED BUT
Notify the system programmer. CONVERSATIONS NO LONGER
EXIST.
Contact IBM Software Support. See IBM Z NetView Explanation
Programming: Assembler for more information on An APPCCMD completed, but the conversations have
return codes. already been ended.
DUI158W DUPLICATE FPPARMS KEYWORD
ENCOUNTERED IN 'initmem'. System action
MEMBER NAME 'sfpname' WILL BE
USED. ALL OTHERS ARE IGNORED.
DUI161I LU luname NOT AVAILABLE FOR
Explanation WORK; REQUEST TO THIS LU WAS
ABORTED.
More than one FPPARMS statement was encountered
in initmem.
Explanation
Message Variables
A request was made to a workstation with an LU name
initmem luname that cannot be honored because this LU is
The initialization member or file for the CNMTAMEL either initializing or ending.
task.
Message Variables
sfpname
The status focal point parameters member or file. luname
The LU that is not available for work.
System action
System action
All subsequent FPPARMS statements are ignored.
The LU finishes ending or initializing. Upon completing
DUI159W UNRECOGNIZED INITIALIZATION initialization it receives complete status information.
STATEMENT IN 'initmem'. THE
KEYWORD 'keyword' IS IGNORED. DUI163E STATUS FOCAL POINT RECEIVED
A REQUEST TO CHANGE THE
STATUS FOCAL POINT -
Explanation
SYNCHRONIZATION SERIES NOT
An unrecognized initialization statement was INITIATED.
encountered in the initialization member or file.
Message Variables Explanation
initmem A CHANGEFP STATUS command was issued for this

The initialization member or file for the CNMTAMEL host, but the host is a status focal point. This is not
task. correct. The target in the CHANGEFP STATUS
command must be a status collector host. That is, the
keyword
CNMTAMEL task in the target host must be defined as
The keyword that is not correct.
a status collector. Because status collector focal point
hosts do not communicate (synchronize) with other
System action status focal point hosts, an attempt was not made to
The initialization statement is ignored. initiate this communication. That is, the
synchronization series was not initiated.

System action Explanation
The status focal point is changed for this host. This host is a status collector that received a request
from the status focal point host host1. However, this
Operator response host has not defined a status focal point. That is, the
DEFFOCPT STATUS statement in DSICRTTD has been
Notify the system programmer. omitted for this host. Therefore this status collector
cannot honor the request.
Message Variables
Determine whether the target ID in the CHANGEFP
host1
STATUS command that was entered is correct. If so,
The domain ID of the status focal point host that
recycle the CNMTAMEL task in this host and define it
sent the request.
as a status collector. If not, ignore the message
because this command was not entered correctly and
will not affect status forwarding at this point. System action
DUI164E REQUEST FROM STATUS FOCAL The request is ignored.

POINT host1 IGNORED. host2 IS A
STATUS FOCAL POINT AND Operator response
CANNOT HONOR REQUESTS FROM Verify that the DSICRTR task is active. If it is and
OTHER STATUS FOCAL POINTS. problems persist, notify the system programmer.
Explanation System programmer response

This status focal point, host2, received a request from Define a status focal point for this status collector with
another status focal point, host1. This is not valid. the DEFFOCPT statement in DSICRTTD and recycle the
Status focal points must send requests only to status DSICRTR task, or use the CHANGEFP STATUS
collectors. command.
Message Variables
DUI166E REQUEST FROM host1 IGNORED -
host1 host1 IS NOT DEFINED AS THE
The domain ID of the host that sent the request. STATUS FOCAL POINT FOR THIS
host2 STATUS COLLECTOR.
The domain ID of the host that received the
request. Explanation
This status collector received a request from a foreign
System action status focal point host1. The request has been
The request is ignored. discarded.
Message Variables
Operator response host1
Notify the system programmer. The domain ID of the status focal point host that
sent the request.
System action
The request that was sent in error is a synchronization
request. The sending focal point's initialization The request is discarded.
member is incorrect. The list of status collectors
includes a focal point host. Correct the error. Operator response
DUI165E REQUEST FROM STATUS FOCAL Notify the system programmer.
POINT host1 IGNORED - THIS
STATUS COLLECTOR HAS NOT System programmer response
DEFINED A STATUS FOCAL POINT.
Check the definition member of the sending status
focal point and remove the status collector
specification for this status collector (if one is present).

This status collector is owned by another status focal FROM OTHER STATUS
point and cannot be owned by two. COLLECTORS.
DUI167I THE STATUS FOCAL POINT FOR
THIS STATUS COLLECTOR HAS Explanation
CHANGED FROM HOST host1 TO This status collector, host2, received a request from
HOST host2 another status collector, host1. This is not valid. Status
collectors must only send requests to status focal
Explanation points.
The CHANGEFP STATUS command was entered at Message Variables
host host2 to take over this status collector. The host1
statuses of the resources at this host are sent to the The domain ID of the host that sent the request.
host host2. Problems encountered at the host host1
can warrant the change. host2
The domain ID of the host that received the
Message Variables request.
host1
The domain ID of the previous status focal point System action
host.
The request is discarded.
host2
The domain ID of the new status focal point host. Operator response
System action Notify the system programmer.
This status collector sends status information to the System programmer response
new status focal point.
The request that was sent in error is a request for
Operator response synchronization. host1 sent the request, therefore
host2 is defined as the status focal point of host1. This
The problems might have warranted the change of is not correct. Either the DEFFOCPT statement in
focal points for this status collector. Therefore, DSICRTTD at host1 is not correct or a CHANGEFP
problems with any resources at this host might have to STATUS command was entered for host2 from host1
be detected here during the change. when host1 was defined as a status focal point.
(CHANGEFP STATUS command can only be entered
DUI168I THE STATUS FOCAL POINT FOR
from a status focal point host.) To correct the problem
THIS STATUS COLLECTOR HAS
either change the DEFFOCPT statement in DSICRTTD
BEEN DEFINED AS host1 BY THE
and recycle the DSICRTR task at host1, or use the
CHANGEFP COMMAND.
CHANGEFP STATUS command to change the status
focal point of host1.
Explanation
DUI170E LUC DEALLOCATE SERVICE
The CHANGEFP STATUS command was entered at
REQUEST FROM luctask1 TO
host host1 to take over this status collector, but this
luctask2 HAS FAILED. RETURN
status collector had not previously defined a status
CODE X'retcode'. SENSE CODE
focal point.
X'sense'.
Message Variables
host1 Explanation
The domain ID of the status focal point host. The luctask1 attempted to deallocate the LUC
conversation between itself and luctask2. The request
System action failed.
This status collector sends status information to the Message Variables
status focal point host1.
luctask1
DUI169E REQUEST FROM STATUS The name of the LUC task that requested the
COLLECTOR host1 IGNORED. deallocate service.
host2 IS A STATUS COLLECTOR
AND CANNOT HONOR REQUESTS

luctask2 Message Variables
The name of the target LUC task for which the
retcode
deallocate was intended.
The LUC conversation request service return code.
retcode
The LUC conversation request service return code. System action
sense
The sense code.
Operator response
System action

Operator response
Attempt to interpret the return code and correct the
problem. For more information, see “LUC Conversation
Request Service Return Codes and Sense Codes” on
System programmer response page 925. If you cannot correct the problem, contact
Attempt to interpret the documented return code and IBM Software Support.
sense code and correct the problem. See “LUC DUI173E LUC ALLOCATE SERVICE REQUEST
Conversation Request Service Return Codes and Sense FROM luctask1 TO luctask2 HAS
Codes” on page 925 or use the NetView SENSE
FAILED. RETURN CODE X'retcode'.
command. If you cannot correct the problem, contact
SENSE CODE X'sense'. VTAM
IBM Software Support.
RTNCD X'vtamrcd'. VTAM FDBK2
DUI171E LUC DEALLOCATE MACRO HAS X'vtamfb'. VTAM SENSE
FAILED WITH A RETURN CODE OF X'vtamsens'.
X'retcode'.
Explanation
Explanation luctask1 attempted to allocate an LUC conversation
The LUC deallocate macro was not accepted by VTAM. between itself and luctask2. The request failed. The
requesting LUC task has data to send to the target LUC
Message Variables task but this data is not sent because the conversation
retcode cannot be allocated.
The LUC conversation request service return code. Message Variables
luctask1
System action
The name of the LUC task that requested the
Processing continues. allocate service.
luctask2
Operator response The name of the target LUC task to which the
Notify the system programmer. allocate was intended.
retcode
System programmer response The LUC conversation request service return code.
sense
Attempt to interpret the return code and correct the
The NetView sense code.
problem. For more information, see “LUC Conversation
Request Service Return Codes and Sense Codes” on vtamrcd
page 925. If you cannot correct the problem, contact The VTAM internal return code.
IBM Software Support. vtamfb
DUI172E LUC ALLOCATE MACRO HAS The VTAM internal feedback code.
FAILED WITH A RETURN CODE OF vtamsens
X'retcode'. The VTAM sense code.

The LUC allocate macro was not accepted by VTAM. Processing continues.

Operator response retcode
The LUC conversation request service return code.
sense
System programmer response The sense code.
Attempt to interpret the documented return code and System action

sense code and correct the problem. For more
information, use the RCFB and SENSE commands to Processing continues.
determine the meaning of the return/feedback and
sense codes, or see “LUC Conversation Request Operator response
Service Return Codes and Sense Codes” on page 925
to determine the meaning of the return code. If you
cannot correct the problem, contact IBM Software
Support. System programmer response
DUI174E LUC SEND MACRO HAS FAILED Attempt to interpret the documented return code and
WITH A RETURN CODE OF sense code and correct the problem. For more
X'retcode'. information, use the SENSE command to determine
the meaning of the sense code, or see “LUC
Conversation Request Service Return Codes and Sense
Explanation
Codes” on page 925 to determine the meaning of the
The LUC send macro was not accepted by VTAM. return code. If you cannot correct the problem,
Message Variables
retcode DUI176E LUC RECEIVE SERVICE REQUEST
The LUC conversation request service return code. FROM luctask1 TO luctask2 HAS
FAILED. RETURN CODE X'retcode'.
System action
Explanation
luctask1 attempted to receive data from the target
LUC task luctask2. The request failed.
Operator response
Message Variables
luctask1
System programmer response The name of the LUC task that requested the
receive service.
See “LUC Conversation Request Service Return Codes
luctask2
and Sense Codes” on page 925 to determine the The name of the target LUC task to which the
meaning of the return code. If you cannot correct the receive request was intended.
problem, contact IBM Software Support.
retcode
DUI175E LUC SEND SERVICE REQUEST The LUC conversation request service return code.
FROM luctask1 TO luctask2 HAS
FAILED. RETURN CODE X'retcode'. System action
SENSE CODE X'sense'.
Explanation
Operator response
luctask1 attempted to send data to the target LUC task
luctask2 and the request failed. Notify the system programmer.
Message Variables
luctask1
The name of the LUC task that requested the send See “LUC Conversation Request Service Return Codes
service. and Sense Codes” on page 925 to determine the
meaning of the return code. If you cannot correct the
luctask2 problem, contact IBM Software Support.
The name of the target LUC task to which the data
was to be sent.

DUI200E CNMTAMEL RECEIVED DUI202E CNMTAMEL FAILED TO RECEIVE
CORRUPTED DATA FROM LU DATA THROUGH THE PROGRAM
luname. TO PROGRAM INTERFACE.
REASON CODE IS reason.
Explanation
Explanation
The CNMTAMEL task does not recognize the data
received from NMC. CNMTAMEL attempted to receive data from the
program-to-program interface and failed. The reason
Message Variables
code in the message is returned by the program-to-
luname program interface.
The name of the LU that sent the data.
Message Variables
System action reason

The reason why the receive failed.
Processing continues, but the corrupted data is not
processed.
System action
Operator response CNMTAMEL continues to run, but the data is not

received from the program-to-program interface.
Record the message and notify the system CNMTAMEL keeps trying to receive this buffer.
programmer.
Operator response
DUI201E CNMTAMEL FAILED TO RECEIVE System programmer response
DATA THROUGH THE PROGRAM Check the explanation of the reason code in the IBM Z
TO PROGRAM INTERFACE DUE TO NetView Application Programmer's Guide for help in
STORAGE SHORTAGE. STORAGE determining the problem. Contact IBM Software
REQUESTED = amount BYTES. Support if necessary.
Explanation DUI203E CNMTAMEL HAS BEEN SENT DATA

OF LENGTH length THROUGH THE
CNMTAMEL attempted to receive data from the PROGRAM TO PROGRAM
program-to-program interface, but cannot get enough INTERFACE. THIS EXCEEDS THE
storage. MAXIMUM LENGTH ALLOWED OF
Message Variables maxlength. THE DATA WILL BE
IGNORED. SENDER ID = senderid.
amount
The amount of storage that CNMTAMEL tried to
Explanation
get.
Data was sent to CNMTAMEL through the program-to-
System action program interface that was too large for CNMTAMEL to
process.
CNMTAMEL continues to run, but data is not received
from the program-to-program interface. CNMTAMEL Message Variables
keeps trying to obtain storage to receive this buffer. length
The size of the data received by CNMTAMEL in
Operator response bytes.
Determine whether you received message BNH16I, maxlength
which means the task has reached its storage limit. If The maximum amount of data, in bytes, that
so, notify your system programmer. CNMTAMEL can process.
senderid
System programmer response The program-to-program interface sender ID of
the program that sent the data.
See the IBM Z NetView Troubleshooting Guide for
possible causes of the storage shortage.

CNMTAMEL discards the data received and continues Part of a multiline message. Each NMCSTATUS policy
processing. definition in member_name is error checked. Any
errors found will be part of the multiline message.
Operator response Message DUI251I begins the multiline message.
Message DUI252I ends the multiline message.
Notify the system programmer. Message DUI250I precedes and succeeds both
DUI251I and DUI252I as a visual aid.
Message Variables
member_name
DUI205I CNMTAMEL HAS ISSUED A Name of the DSIPARM member containing the
PROGRAM TO PROGRAM NMCSTATUS policy definitions.
INTERFACE REQUEST THAT HAS
DUI252I END ERROR CHECKING FOR
FAILED. REQUEST TYPE = reqtype.
MEMBER member_name
REASON CODE = retcode.
Explanation
Explanation
Part of a multiline message. Each NMCSTATUS policy
CNMTAMEL attempted to issue a program-to-program
definition in member_name is error checked. Any
interface request and failed. The reason code in the
errors found will be part of the multiline message.
message is returned by the program-to-program
Message DUI251I begins the multiline message.
interface.
Message DUI252I ends the multiline message.
Message Variables Message DUI250I precedes and succeeds both
DUI251I and DUI252I as a visual aid.
reqtype
The program-to-program interface request that Message Variables
was issued by CNMTAMEL.
member_name
retcode Name of the DSIPARM member containing the
The reason why the request failed. NMCSTATUS policy definitions.
DUI253E policy_def: UNABLE TO CREATE
System action
BEGINNING TIMER FOR THIS
CNMTAMEL continues without processing the POLICY DEFINITION IN MEMBER
program-to-program interface requests. member_name
Operator response Explanation

Notify the system programmer. The DSIPARM member member_name contains a
NMCSTATUS policy definition for policy_def. An
System programmer response attempt was made to create a CHRON timer indicating
the beginning of the policy. Subsequent message
See the IBM Z NetView Application Programmer's DUI284E indicates which command failed and why.
Guide for an explanation of the reason code. If the
problem persists, contact IBM Software Support. Message Variables
DUI250I ---------------------------------------- policy_def

----------- Name of policy definition.
member_name
Explanation Name of the DSIPARM member containing the
NMCSTATUS policy definitions.
Part of a multiline message. Message DUI251I begins
the multiline message. Message DUI252I ends the
System action
multiline message. Message DUI250I precedes and
succeeds both DUI251I and DUI252I as a visual aid. A timer is not set indicating the beginning of the policy.
DUI251I BEGIN ERROR CHECKING FOR
MEMBER member_name System programmer response
Review subsequent message DUI284E.

DUI254E policy_def: ONE OF THE System action
FOLLOWING KEYWORDS IS The DSIPARM member containing the NMCSTATUS
REQUIRED FOR THIS POLICY definitions is in error. Until all errors are resolved,
DEFINITION IN MEMBER
actions based on these policies, such as, disabling
member_name: CLASS,
resource status changes or suspending resources from
BLDVIEWSSPEC OR aggregation, will not occur at the NMC console.
COLLECTIONSPEC

Explanation
All NMCSTATUS policy definitions must specify one of
The DSIPARM member member_name contains a the following keywords: SUSPENDAGG=YES or
NMCSTATUS policy definition for policy_def. A required STOPUPDATE=YES. Correct and reload
keyword is missing from the definition. member_name. For additional information, see the
Message Variables definition of NMCSTATUS in the IBM Z NetView
Administration Reference.
policy_def
Name of policy definition DUI256E policy_def: ONLY ONE OF THE
member_name FOLLOWING KEYWORDS IS
Name of the DSIPARM member containing the ALLOWED FOR THIS POLICY
NMCSTATUS policy definitions. DEFINITION IN MEMBER
member_name: CLASS,
BLDVIEWSSPEC OR
System action
COLLECTIONSPEC
The DSIPARM member containing the NMCSTATUS
definitions is in error. Until all errors are resolved, Explanation
resource status changes or suspending resources from The DSIPARM member member_name contains a
aggregation, will not occur at the NMC console. NMCSTATUS policy definition for policy_def. An
unallowable combination of keywords is used for this
definition.
Message Variables
All NMCSTATUS policy definitions must specify one of
the following keywords: CLASS, BLDVIEWSSPEC or policy_def
COLLECTIONSPEC. Correct and reload member_name. Name of policy definition
For additional information, see the definition of member_name
NMCSTATUS in the IBM Z NetView Administration Name of the DSIPARM member containing the
Reference. NMCSTATUS policy definitions.
DUI255E policy_def: ONE OF THE
FOLLOWING KEYWORDS IS System action
REQUIRED FOR THIS POLICY The DSIPARM member containing the NMCSTATUS
DEFINITION IN MEMBER definitions is in error. Until all errors are resolved,
member_name: actions based on these policies, such as, disabling
SUSPENDAGG=YES OR resource status changes or suspending resources from
STOPUPDATE=YES aggregation, will not occur at the NMC console.

The DSIPARM member member_name contains a NMCSTATUS policy definitions must specify one and
NMCSTATUS policy definition for policy_def. A required only one of the following keywords: CLASS,
keyword is missing from the definition. BLDVIEWSSPEC or COLLECTIONSPEC. Correct and
Message Variables reload member_name. For additional information, see
the definition of NMCSTATUS in the IBM Z NetView
policy_def Administration Reference.
Name of policy definition
member_name DUI257E policy_def: keyword IS A
Name of the DSIPARM member containing the REQUIRED KEYWORD MISSING
NMCSTATUS policy definitions. FOR THIS POLICY DEFINITION IN
MEMBER member_name

Explanation resource status changes or suspending resources from
aggregation, will not occur at the NMC console.
The DSIPARM member member_name contains a
NMCSTATUS policy definition for policy_def. A required
keyword keyword is missing from this definition. System programmer response
Message Variables The keyword was specified more than once for this
NMCSTATUS policy definition. Correct and reload
policy_def member_name. For additional information, see the
Name of policy definition definition of NMCSTATUS in the IBM Z NetView
keyword Administration Reference.
Keyword for NMCSTATUS policy definition
DUI259E policy_def: keyword1 IS A
member_name REQUIRED KEYWORD WHEN
Name of the DSIPARM member containing the KEYWORD keyword2 EXISTS FOR
NMCSTATUS policy definitions. THIS POLICY DEFINITION IN
MEMBER member_name
System action
The DSIPARM member containing the NMCSTATUS Explanation
definitions is in error. Until all errors are resolved, The DSIPARM member member_name contains a
actions based on these policies, such as, disabling NMCSTATUS policy definition for policy_def. Since
resource status changes or suspending resources from keyword keyword2 was specified for this definition,
aggregation, will not occur at the NMC console. keyword1 is a required keyword.
Message Variables
policy_def
The missing keyword is required for this NMCSTATUS Name of policy definition
policy definition. Correct and reload member_name.
For additional information, see the definition of keyword1
NMCSTATUS in the IBM Z NetView Administration Required keyword missing from this definition.
Reference. keyword2
Optional keyword specified for this definition.
DUI258E policy_def: ONLY ONE keyword
KEYWORD IS ALLOWED FOR THIS member_name
POLICY DEFINITION IN MEMBER Name of the DSIPARM member containing the
member_name NMCSTATUS policy definitions.
The DSIPARM member member_name contains a The DSIPARM member containing the NMCSTATUS
NMCSTATUS policy definition for policy_def. A definitions is in error. Until all errors are resolved,
duplicate keyword keyword was specified for this actions based on these policies, such as, disabling
definition. resource status changes or suspending resources from
aggregation, will not occur at the NMC console.
Message Variables
policy_def System programmer response
Since keyword2 was specified for this definition,
keyword keyword1 is a required definition. Correct keyword1
Keyword for NMCSTATUS policy definition. and reload member_name. For additional information,
member_name see the definition of NMCSTATUS in the IBM Z NetView
Name of the DSIPARM member containing the Administration Reference.
DUI260E policy_def: keyword IS NOT A
VALID KEYWORD FOR THIS
System action POLICY DEFINITION IN MEMBER
The DSIPARM member containing the NMCSTATUS member_name
definitions is in error. Until all errors are resolved,

Explanation Explanation
The DSIPARM member member_name contains a The DSIPARM member member_name contains a
NMCSTATUS policy definition for policy_def. An NMCSTATUS policy definition for policy_def. An
incorrect keyword keyword was specified for this unallowable combination of keywords is used for this
definition. definition.
Message Variables Message Variables
policy_def policy_def
Name of policy definition Name of policy definition
keyword member_name
Incorrect keyword. Name of the DSIPARM member containing the
member_name NMCSTATUS policy definitions.
Name of the DSIPARM member containing the
NMCSTATUS policy definitions. System action
The DSIPARM member containing the NMCSTATUS
System action definitions is in error. Until all errors are resolved,
The DSIPARM member containing the NMCSTATUS actions based on these policies, such as, disabling
definitions is in error. Until all errors are resolved, resource status changes or suspending resources from
actions based on these policies, such as, disabling aggregation, will not occur at the NMC console.
resource status changes or suspending resources from
aggregation, will not occur at the NMC console. System programmer response
NMCSTATUS policy definitions might specify one and
System programmer response only one of the following keywords: RESOURCE or
keyword is not a valid keyword for this definition. MYNAME. Correct and reload member_name. For
Correct keyword and reload member_name. For additional information, see the definition of
additional information, see the definition of NMCSTATUS in the IBM Z NetView Administration
NMCSTATUS in the IBM Z NetView Administration Reference.
Reference. DUI263I TIMER HANDLE timer_handle
DUI261I NO ERRORS WERE FOUND IN POPPED TO INDICATE THE
MEMBER member_name SCHEDULED WINDOW FOR
POLICY DEFINITION policy_def
HAS BEGUN
Explanation
No errors were found in DSIPARM member Explanation
member_name.
A CHRON timer with the timer handle timer_handle
Message Variables has popped indicating the beginning of a scheduled
member_name NMCSTATUS policy. If RODM is started, an attempt
Name of the DSIPARM member containing the will be made to create a RODM object to represent the
NMCSTATUS policy definitions. NMCSTATUS policy definition.
Message Variables
System action timer_handle
Processing of the NMCSTATUS definitions continues. Timer handle of the CHRON timer
DUI262E policy_def: ONLY ONE OF THE policy_def

FOLLOWING KEYWORDS IS Name of policy definition
ALLOWED FOR THIS POLICY
DEFINITION IN MEMBER System action
member_name: RESOURCE OR When the CHRON timer pops, an action, in this case,
MYNAME an internal REXX command list, is executed to attempt
to create a RODM object representing the NMCSTATUS
policy definition.

DUI264I TIMER HANDLE timer_handle same myname exists in RODM. The object will be
POPPED TO INDICATE THE deleted, resulting in message DUI266I and created
SCHEDULED WINDOW FOR again, resulting in message DUI267I.
POLICY DEFINITION policy_def
DUI266I DELETED RODM OBJECT myname
HAS ENDED
FOR POLICY DEFINITION
policy_def IN THE
Explanation AGGREGATE_COLLECTION_CLASS
A CHRON timer with the timer handle timer_handle
has popped indicating the end of a scheduled Explanation
NMCSTATUS policy. If RODM is started, an attempt
An object with a MyName value of myname
will be made to delete the RODM object representing
representing policy definition policy_def was deleted
the NMCSTATUS policy definition.
from the Aggregate_Collection_Class.
Message Variables
Message Variables
timer_handle
myname
Timer handle of the CHRON timer
MyName value of the RODM object. Value is a
policy_def concatenation of the timer handle that scheduled
Name of policy definition the beginning of the window and the name of the
policy definition. For example, if timer handle
System action NMC1 pops to indicate the beginning of policy
definition POLICY1, the MyName of the RODM
When the CHRON timer pops, an action, in this case, object representing the policy is NMC1POLICY1.
an internal REXX command list, is executed to attempt
to delete the RODM object representing the policy_def
NMCSTATUS policy definition. Name of policy definition
DUI265I ATTEMPTED TO CREATE RODM System action

OBJECT myname TO REPRESENT
POLICY DEFINITION policy_def The object is deleted from RODM.
BUT AN OBJECT WITH THE SAME
DUI267I CREATED RODM OBJECT myname
MYNAME EXISTS IN RODM
FOR POLICY DEFINITION
policy_def IN THE
Explanation AGGREGATE_COLLECTION_CLASS
An attempt was made to create a RODM object with a
MyName value of myname to represent the Explanation
NMCSTATUS policy definition but an object in class
An object with a MyName value of myname
Aggregate_Collection_Class already exists for that
representing policy definition policy_def was created in
myname. The RODM object is deleted and recreated.
the Aggregate_Collection_Class.
Message Variables
Message Variables
myname
myname
concatenation of the timer handle that scheduled
the beginning of the window and the name of the
NMC1 pops to indicate the beginning of policy
object representing the policy is NMC1POLICY1.
object representing the policy is NMC1POLICY1.
policy_def
policy_def
System action
System action
An attempt was made to create a RODM object with a
The object is created in RODM.
MyName value of myname in the
Aggregate_Collection_Class but an object with the

DUI268E RODM PROCESSING ERROR. Operator response
PROCESSING FOR RODM OBJECT Notify the system programmer.
myname FOR POLICY DEFINITION
policy_def ENDED IN MODULE
module_name WITH RETURN System programmer response
CODE return_code. See message number DUI268E or DUI287E.
DUI270E ATTEMPTED TO CREATE RODM
Explanation
OBJECT myname TO REPRESENT
Module module_name encountered a RODM POLICY DEFINITION policy_def
processing error while attempting to access a RODM BUT VALUE value FOR KEYWORD
object in class Aggregate_Collection_Class. keyword IS INCORRECTLY
SPECIFIED IN MEMBER
Message Variables
member_name
myname
MyName value of the RODM object. Value is a Explanation
the beginning of the window and the name of the An error occurred while NetView attempted to
policy definition. For example, if timer handle generate a RODM Collection Manager specification
NMC1 pops to indicate the beginning of policy from the keyword value in the policy definition.
definition POLICY1, the MyName of the RODM Message Variables
object representing the policy in NMC1POLICY1.
myname
policy_def MyName value of the RODM object. Value is a
Name of policy definition concatenation of the timer handle that scheduled
module_name the beginning of the window and the name of the
Name of the module that was running at the time policy definition. For example, if timer handle
the error was discovered. NMC1 pops to indicate the beginning of policy
return code definition POLICY1, the MyName of the RODM
The return code from the module. object representing the policy is NMC1POLICY1.
policy_def
System action Name of policy definition
A RODM object representing an NMCSTATUS policy value

definition cannot be processed. Keyword value
keyword
System programmer response Keyword for NMCSTATUS policy definition
member_name
• Make sure the data model is loaded and that RODM
is correctly processing function requests from
NMCSTATUS policy definitions
applications.
• Check the NetView log for message DUI269E.
System action
• Contact IBM Software Support if you cannot resolve
the problem. A RODM object will not be created to represent policy
definition policy_def.
DUI269E RODM OBJECT INFORMATION
Operator response
Explanation
A RODM processing error was encountered.
System action
• Verify value is correct.
The system logs the RODM object being processed at
– If QSAMDSN was indicated in the value, make
the time of the error to the NetView log along with
sure the data set name specified in the keyword
other pertinent information.
value for policy_def exists.

– If QSAMDD was indicated in the value, make sure stage
the data definition specified in the keyword value PIPE stage in error
for policy_def exists.
• Correct the keyword and reload member_name. For System action
additional information, see the definition of If module_name=DUIFSNTX, the error was found
NMCSTATUS in the IBM Z NetView Administration before any timers were set for the policy. Until the
Reference. error is resolved, actions based on any policies defined
DUI271E policy_def: UNABLE TO READ in the DSIPARM member will not occur at the NMC
DATA SPECIFIED IN VALUE value console.
FOR KEYWORD keyword FOR THIS If module_name=DUIFACTV, the error occurred when
POLICY DEFINITION IN MEMBER the beginning timer for policy popped. This indicates
member_name. MODULE that the data set or data definition file was allocated
module_name RC return_code PIPE when the policies were read but has been deallocated
STAGE stage since the timers were set. A RODM object will not be
created to represent policy definition policy_def.
Explanation
An error occurred when NetView attempted to access Operator response
data in the specified data set name or data definition Notify the system programmer.
file.
Message Variables System programmer response
policy_def • Verify value is correct.
– If QSAMDSN was indicated in the value, make
value sure the data set name specified on keyword for
Keyword value policy_def exists.
keyword – If QSAMDD was indicated in the value, make sure
Keyword for NMCSTATUS policy definition the data definition file specified on keyword for
member_name policy_def exists.
Name of the DSIPARM member containing the • Correct the keyword and reload member_name. For
NMCSTATUS policy definitions additional information, see the definition of
module_name NMCSTATUS in the IBM Z NetView Administration
Name of the module that was running at the time Reference.
the error was discovered
DUI272E policy_def: VALUE value
return_code SPECIFIED FOR KEYWORD
The return code from the module. Even return keyword FOR THIS POLICY
codes, such as 12,28,32,36 and 100, are issued DEFINITION IN MEMBER
from the PIPE QSAM command. Issue a HELP PIPE member_name IS NOT VALID.
QSAM for more information. Odd return codes are MODULE module_name
issued from the NMCSTATUS policy autotask: GENERATED RETURN CODE
3 return_code
A data set name was not specified for
BLDVIEWSSPEC=(QSAMDSN,dataset) Explanation
5 An incorrect value was specified for the keyword.
A data definition file was not specified for
BLDVIEWSSPEC=(QSAMDD, Message Variables
data_definition_file) policy_def
7 Name of policy definition
A data set name was not specified for value
COLLECTIONSPEC=(QSAMDSN,dataset) Keyword value in error
9 keyword
A data definition file was not specified for Keyword of NMCSTATUS policy definition in error
COLLECTIONSPEC=(QSAMDD,
data_definition_file)

member_name resource status changes or suspending resources from
Name of the DSIPARM member containing the aggregation, will not occur at the NMC console.
module_name System programmer response
Name of the module that issued the message. The value of the keyword is incorrect. See the return
return_code codes for help in determining the error. Correct the
Return code set in the module. policy definition and reload member_name.
19 For additional information, see the definition of
No value was specified NMCSTATUS in the IBM Z NetView Administration
20 Reference.
Value must be enclosed with parenthesis, for DUI273E policy_def: UNABLE TO CREATE
example (value) ENDING TIMER FOR THIS POLICY
21 DEFINITION IN MEMBER
No value was specified inside the parenthesis, member_name
for example ()
22 Explanation
A comma can not be the first or last character
The DSIPARM member member_name contains a
of the value, for example (,value) and (value,)
NMCSTATUS policy definition for policy_def. An
are incorrect
attempt was made to create a CHRON timer indicating
23 the end of the policy. Subsequent message DUI284E
Valid characters for the value are 0 to 9 and '.' indicates which command failed and why it failed.
24 Message Variables
Format of the value must be
(hh.mm.ss.hh.mm.ss) policy_def
25
Valid values for hh are 0 to 23, for mm are 0 to member_name
59, for ss are 0 to 59 Name of the DSIPARM member containing the
26
Valid length for values hh, mm, and ss is 2, for
example (05.00.00.06.00) is correct and System action
(5.00.00.6.00.00) is not A timer is not set indicating the end of the policy.
27
Expected 2 parsed values, such as System programmer response
(value1,value2)
Review subsequent message DUI284E.
28
Valid value is (QSAMDSN,definition) or DUI274E DUI274E MODULE module_name
(QSAMDD,definition) WAS CALLED WITH INCORRECT
29 PARAMETERS
Valid value is YES or NO
Explanation
30
Multiple consecutive commas within value are During processing of NMCSTATUS policy definitions,
not allowed, for example (50.00.00,,06.00.00) CHRON timers are set to indicate the beginning and
is incorrect end of each scheduled NMCSTATUS policy.
31 Either an internal error has occurred or an operator
Embedded blanks within value are not allowed, has changed the timer command of a CHRON timer
for example (05.00. , 06.00.00) is incorrect that was created for a NMCSTATUS policy. It is critical
that the timer command of these timers is not
System action modified.
The DSIPARM member containing the NMCSTATUS Message Variables
definitions is in error. Until all errors are resolved,
module_name
Name of the module

System action member_name
If the module_name is DUIFACTV, processing has
failed to create a RODM object to represent the
NMCSTATUS policy definition. return_code
If the module_name is DUIFNACT, processing has 0
failed to delete a RODM object that represents a Successful
NMCSTATUS policy definition. 1
POLICY command failed because NMCSTATUS
System programmer response policy was not found
Make sure that an operator did not modify the timer 2

command of a CHRON timer that was created for a Internal error
NMCSTATUS policy. An example of a timer command 3
is: POLICY command failed because of missing
parameters
DUIFACTV POLICYA NMC1 NMC1POLICYA
4
where DUIFACTV is the name of the clist to run when POLICY command failed because of incorrect
the timer pops, POLICYA is the name of the policy, parameters
NMC1 is the timer ID and NMC1POLICYA is the 5
MyName value of the RODM object to be created. Internal error
Modifications to the timer command might result in
7
errors in NMCSTATUS policy processing. To re-
POLICY command failed (SIGNAL NOVALUE)
initialize processing, issue the NMCPINIT command.
8
For additional information, see the definition of POLICY command failed (SIGNAL SYNTAX)
NMCSTATUS in the IBM Z NetView Administration
Reference. 9
POLICY command failed because of security
DUI275I BEGIN PROCESSING NMCSTATUS authorization failure
POLICY DEFINITIONS DEFINED IN 10
MEMBER member_name POLICY command failed because request
cannot be processed. Make sure NMCSTATUS
Explanation is uppercase and begins in column 1 in the
Command NMCPINIT or NMCPTEST has been issued. policy file.
NMCPINIT is coded in the automation table (DSIPARM 11
member DSITBL01). Syntax error found in NMCSTATUS policy file
Message Variables 13
No policies to syntax check
member_name
Name of the DSIPARM member containing the 14
NMCSTATUS policy definitions. Global EZLPOLICY.GRAPHICS was not set,
indicating autotask AUTOAON did not load any
policies for TOWER GRAPHICS
System action
15
Processing of NMCSTATUS policy definitions begins. Incorrect keyword on command NMCPINIT or
DUI276I END PROCESSING NMCSTATUS NMCPTEST
POLICY DEFINITIONS DEFINED IN 16
MEMBER member_name, RETURN Incorrect value for keyword on command
CODE return_code NMCPINIT or NMCPTEST
-1
Explanation POLICY command failed (SIGNAL FAILURE)
Command NMCPINIT or NMCPTEST has been issued. -5
NMCPINIT is coded in the automation table (DSIPARM POLICY command failed (SIGNAL HALT)
member DSITBL01).
Message Variables

If the return_code is non-zero, actions based on these The command is unable to run on the DUIFPOLI
policies, such as, disabling resource status changes or autotask.
suspending resources from aggregation, will not occur
at the NMC console. Operator response
Browse the NetView log and see what messages were
Operator response
issued before DUI278E.
Browse the NetView log for errors regarding policy.
Make sure the policy file containing your NMCSTATUS System programmer response
policy definitions was loaded and did not contain any
errors. Make sure function.autotask.NMCpolicy = DUIFPOLI is
coded in the CNMSTYLE member.
System programmer response DUI279I NMCSTATUS POLICY
DEFINITIONS WERE NOT FOUND
For additional information, see the definition of IN MEMBER member_name
Reference. Explanation
DUI277I COMMAND command_name HAS POLICY.GRAPHICS in the CNMSTYLE member
BEEN SENT TO AUTOTASK indicates that member_name containing NMCSTATUS
autotask_name FOR PROCESSING policy definitions were to be loaded into storage.
NetView attempted to read NMCSTATUS policy
Explanation definitions in member_name but none were found.
Commands NMCPINIT and NMCPTEST must run on Message Variables
autotask DUIFPOLI. If the command is issued from an
member_name
operator other than autotask DUIFPOLI, the command
is sent to autotask DUIFPOLI to run.
NMCSTATUS policy definitions
Message Variables
command_name System action
Name of the command sent to the autotask Processing of NMCSTATUS policy definitions ends.
autotask_name
Name of the autotask the command was sent to System programmer response
Make sure that your NMCSTATUS policy definitions are
System action defined in member_name. Reload member_name. For
The command runs on the DUIFPOLI autotask. additional information, see the definition of
DUI278E ATTEMPT TO SEND COMMAND Reference. If you have not defined NMCSTATUS policy
command_name TO AUTOTASK definitions, comment out POLICY.GRAPHICS in the
autotask_name FAILED CNMSTYLE member.
Explanation DUI280I ----------------------------------------

-------------
Commands NMCPINIT and NMCPTEST must run on
autotask DUIFPOLI. If the command is issued from an Explanation
operator other than autotask DUIFPOLI, the command
is sent to autotask DUIFPOLI to run. If necessary, the Part of a multiline message
DUIFPOLI autotask is started. • Message DUI281I begins the multiline message.
Message Variables • Message DUI282I ends the multiline message.
command_name • Message DUI280I precedes and succeeds both
Name of the command sent to the autotask DUI281I and DUI282I as a visual aid.
autotask_name DUI281I BEGIN SETTING TIMERS FOR
Name of the autotask the command was sent to NMCSTATUS POLICIES DEFINED
IN MEMBER member_name

Part of a multiline message. Each NMCSTATUS policy Processing of NMCSTATUS policy definitions
definition in member_name generates two CHRON continues.
timers. One timer indicates the beginning of the policy
DUI284E COMMAND command_name
and the other timer indicates the end of the policy. Any
FAILED WITH RETURN CODE
errors found while setting the timers will be part of the
return_code IN MODULE
multiline message.
module_name. THE NEXT
• Message DUI281I begins the multiline message. num_msgs MESSAGE(S) MAY HELP
• Message DUI282I ends the multiline message. DETERMINE THE ERROR
• Message DUI280I precedes and succeeds both
DUI281I and DUI282I as a visual aid. Explanation
Message Variables An attempt was made to create a timer for the policy
definition referenced in message DUI253E or DUI273E
member_name but failed with the return_code. If any error messages
Name of the DSIPARM member containing the were returned with the failed command_name, they
NMCSTATUS policy definitions will appear in the NetView log after message DUI284E.
DUI282I END SETTING TIMERS FOR Message Variables
NMCSTATUS POLICIES DEFINED
command_name
IN MEMBER member_name
Name of the command
Explanation return_code
Return code from the command
Part of a multiline message. Each NMCSTATUS policy
module_name
definition in member_name generates two CHRON
Name of the module that issued the command
timers. One timer indicates the beginning of the policy
and the other timer indicates the end of the policy. Any num_msgs
errors found while setting the timers will be part of the Number of error messages from the command
multiline message. related to the error
• Message DUI281I begins the multiline message.

System action
• Message DUI282I ends the multiline message.
A timer is not set indicating the beginning or ending of
• Message DUI280I precedes and succeeds both the policy definition referenced in preceding message
DUI281I and DUI282I as a visual aid. DUI253I or DUI273E.
Message Variables
member_name System programmer response
Name of the DSIPARM member containing the The num_msgs messages following DUI284E were
NMCSTATUS policy definitions issued by command_name. If command_name is
EZLETAPI, review these messages carefully to
DUI283I ALL TIMERS WERE SET
determine if one of the keywords specified for the
SUCCESSFULLY
policy definition referenced in preceding message
DUI253E or DUI273E is incorrect. Pay special
Explanation attention to the following keywords: TIME,
No errors were found while setting CHRON timers for DAYOFWEEK, EDAYOFWEEK, DAYOFMONTH,
NMCSTATUS policies defined in DSIPARM member EDAYOFMONTH, CALENDARDAY, and
member_name. ECALENDARDAY. Correct and reload the DSIPARM
member referenced in preceding message DUI253E or
Message Variables DUI273E.
member_name If command_name is PIPE CORRCMD (MOE)
Name of the DSIPARM member containing the EZLETAPI, an internal error has occurred. Contact the
NMCSTATUS policy definitions IBM Software Support with the following information:
• The complete policy definition that is in error
• Messages DUI253E or DUI273E, message DUI284E
and the subsequent errors from the command.

For additional information, see the definition of Explanation
Module module_name encountered a RODM
Reference.
processing error while attempting to locate all RODM
DUI285I DELETED TIMER HANDLE objects with field_name.
timer_handle DURING Message Variables
PROCESSING OF THE command
COMMAND field_name
Name of the RODM field
Explanation module_name
Name of the module that was running at the time
The command command processes NMCSTATUS
the error was discovered.
policy definitions currently loaded in the Policy
Repository. Any CHRON timers set by previous return_code
NMCSTATUS policy definitions are deleted. If the The return code from the module
current NMCSTATUS policy definitions are error free,
new CHRON timers are created. System action
Message Variables A RODM LOCATE cannot be processed
timer_handle
Timer handle of the CHRON timer System programmer response
command • Make sure the data model is loaded and that RODM
Name of the command that deleted the CHRON is correctly processing function requests from
timer applications.
• Check the NetView log for message DUI269E.
System action • Contact IBM Software Support if you cannot resolve
The timer is deleted the problem.
DUI286I DELETED RODM OBJECTID DUI288E policy_def: VALUE SPECIFIED FOR

object_id DURING PROCESSING THIS POLICY DEFINITION IN
OF THE command COMMAND MEMBER member_name IS NOT
VALID. MODULE module_name
Explanation GENERATED RETURN CODE
return_code
The command command processes NMCSTATUS
policy definitions currently loaded in the Policy Explanation
Repository. Any CHRON objects representing active
policies defined by previous NMCSTATUS policy An incorrect value was specified for policy_def.
definitions are deleted. If the current NMCSTATUS Message Variables
policy definitions are error free, new CHRON timers are
created. When these timers pop, new RODM objects policy_def
are created to represent active policies. Name of the policy definition
Message Variables member_name
object_id NMCSTATUS policy definitions.
RODM object id that is deleted
module_name
command Module that issued the message
Name of the command that deleted the CHRON
return_code
timer
The return code set in the module:
System action 40
Policy definition contains a quotation mark
The RODM object id is deleted
DUI287E RODM PROCESSING ERROR. System action
LOCATE ON FIELD field_name The DSIPARM member containing the NMCSTATUS
ENDED IN MODULE module_name definitions is in error. Until all errors are resolved,
WITH RETURN CODE return_code actions based on these policies, such as, disabling

resource status changes or suspending resources from module_name
aggregation, will not occur at the NMC console. The name of the module being traced.
data
System programmer response The trace information related to the option
The value of the policy definition is incorrect. See the specified on the TRACE= keyword.
return code for help in determining the error. Correct DUI291I TRACE=level IS SET FOR
the policy definition and reload member-name. NMCSTATUS PROCESSING
For additional information, see the definition of
NMCSTATUS in the IBM Z NetView Administration Explanation
Reference. This message is generated whenever the keyword
DUI289I COMMAND command_name TRACE=level is entered for the NMCPINIT or
COMPLETED WITH RETURN CODE NMCPTEST command.
return_code Message Variables
level
Explanation
The level of tracing that is activated
The command has completed.
ALL
Message Variables All of the trace statements are generated
command_name NONE
The name of the command None of the trace statements are generated
return_code DUI292E UNABLE TO CREATE RODM
The return code that is returned from the OBJECT myname FOR POLICY
command_name DEFINITION policy_def IN THE
AGGREGATE_COLLECTION_CLASS
System action . TIMER HANDLE timer_handle
MODULE module_name RETURN
Actions based on these policies do not occur at the CODE return_code
NMC console if the return_code is non-zero. Some
examples of such policies include disabling resource
status changes or suspending resources form Explanation
aggregation. A CHRON timer has popped and command list
DUIFACTV is executed to indicate the beginning of a
Operator response scheduled NMCSTATUS policy. The command list
parameters consist of the name of the policy
Browse the NetView log for errors regarding policy. definition, the timer handle of the CHRON timer that
Make certain the policy file containing your popped, and the MyName of the object to be created
NMCSTATUS policy definitions is loaded and does not in RODM. An attempt is made to create a RODM object
contain any errors. See the message help for message to represent the NMCSTATUS policy definition.
DUI276I for information about return code values. However, the policy definition in the DUIFACTV
parameter list did not match any NMCSTATUS policy
System programmer response definitions in the Policy Repository. The RODM object
For additional information, see the definition of is not created.
NMCSTATUS in IBM Z NetView Administration Message Variables
Reference.
myname
DUI290I TRACE MODULE module_name. MyName value of the RODM object. Value is a
data. concatenation of the timer handle that scheduled
Explanation policy definition. For example, if timer handle
This message is generated whenever ALL is entered definition POLICYabc, the MyName of the RODM
for the NMCPINIT TRACE= keyword or the NMCPTEST object representing the policy is NMC1POLICYabc.
TRACE= keyword.
policy_def
Message Variables Name of the policy definition

timer_handle SCHEDULED WINDOW FOR POLICY DEFINITION
POLICYabc HAS BEGUN
Timer handle of the CHRON timer DUI267I CREATED RODM OBJECT NMC1POLICYabc FOR
POLICY DEFINITION POLICYabc IN THE
module_name AGGREGATE_COLLECTION_CLASS
Name of the module that was running at the time
the error was discovered DUI353E UNABLE TO ALLOCATE MEMORY
return_code FOR PROGRAM TO PROGRAM
INTERFACE RECEIVER BUFFER
10
FOR DUIFSSCO.
Policy definition on CHRON timer was not
found in storage
Explanation
13
Global variable CNMSTYLE.POLICY.GRAPHICS A call to the DSIGET macro failed in DUIFSSCO, the
is NULL load module for the scope checker optional task
50 (OPT). The system is unable to allocate memory for
CollectionSpec1 field cannot be generated the program-to-program interface receiver buffer.
51
System action
RequestFlags field has an incorrect value of 0
The scope checker OPT ends.
System action
Operator response
A RODM object representing the NMCSTATUS policy
definition is not created. Actions based on the policy, Notify the system programmer.
such as, disabling resource status changes or
suspending resources from aggregation, will not occur System programmer response
at the NMC console.
Ensure that the NetView region size is large enough. If
it is not, resolve the storage problem and restart
DUIFSSCO.
You might receive this error if your policy definition
contains mixed case characters and a NetView DUI354E UNABLE TO DELIVER NETWORK
operator enters the DUIFACTV command without COMMAND TEXT TO taskid TASK
NETVASIS preceding the command list. For example, a BECAUSE THE TASK IS NOT
CHRON timer with a timer handle of NMC1 is ACTIVE.
generated for policy definition POLICYabc. Instead of
waiting for CHRON to execute the command, a Explanation
NetView operator enters the DUIFACTV command list The DUIFSSCO scope checker optional task cannot
from an OST. If NETVASIS did not precede the deliver the network command to the specified task
command, POLICYabc is changed to POLICYABC as because it is inactive.
shown in the NetView log.
Message Variables
DUIFACTV POLICYABC NMC1 NMC1POLICYABC
DSI268I EXCMD COMPLETE taskid
DUI277I COMMAND 'DUIFACTV POLICYABC NMC1 The ID of the task that is inactive.
NMC1POLICYABC' HAS BEEN SENT TO AUTOTASK
DUIFPOLI FOR PROCESSING
DUI263I TIMER HANDLE NMC1 POPPED TO INDICATE THE
SCHEDULED WINDOW FOR POLICY DEFINITION System action
POLICYABC HAS BEGUN
DUI292E UNABLE TO CREATE RODM OBJECT This message is sent to the NetView authorized
NMC1POLICYABC receiver and processing continues.
FOR POLICY DEFINITION POLICYABC IN THE
AGGREGATE_COLLECTION_CLASS.
TIMER HANDLE NMC1 MODULE DUIFACTV RETURN Operator response
CODE 50
Notify the system programmer. Reenter the network
To correct, enter NETVASIS in front of the command, command after the specified task has been activated.
as shown in the NetView log:
NETVASIS DUIFACTV POLICYabc NMC1 NMC1POLICYabc System programmer response

DUI277I COMMAND 'DUIFACTV POLICYabc NMC1
NMC1POLICYabc' HAS BEEN SENT TO AUTOTASK Activate the specified task.
DUIFPOLI FOR PROCESSING
DUI263I TIMER HANDLE NMC1 POPPED TO INDICATE THE

DUI355I DUPLICATE REQUEST TO TYPE = type, RETURN CODE =
REGISTER DUIFSSCO. retcode
The scope checker optional task (OPT) cannot The scope checker optional task (OPT) received a
establish communication with CNMTAMEL because permanent-failure return code from the program-to-
CNMTAMEL detected a duplicate request. program interface.
Message Variables
System action
type
This message is sent to the NetView authorized The program-to-program interface request type.
receiver and processing continues.
retcode
The program-to-program interface return code
Operator response that indicates the failure.
System action
System programmer response This message is sent to the authorized receiver and
Recycle both the CNMTAMEL and the scope checker the scope checker OPT ends.
tasks. If the problem persists, contact IBM Software
Support. Operator response
DUI357E AN UNRECOGNIZED SENDER Notify the system programmer.
senderid EXISTS IN THE
DUIFSSCO PROGRAM TO System programmer response
PROGRAM INTERFACE BUFFER.
See the IBM Z NetView Application Programmer's
Guide for an explanation of the return code. Determine
Explanation the cause of the error and correct the problem.
DUIFSSCO, the load module for the scope checker
DUI359E GMFHS SCOPE CHECKER OPT
optional task (OPT), received a program-to-program
DUIFSSCO RECEIVED
interface buffer from an unauthorized sender.
TEMPORARY FAILURE RETURN
Message Variables CODE FROM PROGRAM TO
PROGRAM INTERFACE, REQUEST
senderid
TYPE= type, RETURN CODE =
The task identifier of the message received by
retcode
DUIFSSCO.
Explanation
System action
The scope checker optional task, DUIFSSCO, received
This message is sent to the authorized receiver. The
a temporary failure return code from the program-to-
scope checker OPT ignores this sender ID and
program interface.
processing continues.
Message Variables
Operator response type
Notify the system programmer. The program-to-program interface request type.
retcode
System programmer response The program-to-program interface return code
that indicates the failure.
Determine the owner of the sender ID, and notify the
owner not to send the data buffer using a program-to-
System action
program interface receiver name of DUIFSSCO.
DUIFSSCO cannot communicate with the program-to-
DUI358E DUIFSSCO RECEIVED
program interface, but periodically attempts to re-
PERMANENT FAILURE RETURN
establish communication until it succeeds.
CODE FROM PROGRAM TO
PROGRAM INTERFACE, REQUEST

Operator response DUI364E DUIFSSCO INTERNAL ERROR
OCCURRED, MODULE = module,
NETVIEW MACRO = macro,
RETURN CODE = retcode
See the IBM Z NetView Application Programmer's Explanation
Guide for an explanation of return codes. Determine
An internal error occurred while the scope checker
the cause of the error and correct the problem.
optional task (OPT) processed a network control
DUI360E var GLOBAL VARIABLE IS command.
MISSING
Message Variables
Explanation module
The name of the module where the error condition
The global variable representing the procedure name occurred.
is missing.
macro
Message Variables The name of the NetView services macro.
var retcode
The name of the variable that is not set The return code from the NetView services macro.

The command ends. The scope checker OPT sends this message to the
authorized receiver and ends.
Operator response
Operator response
Set the global command list variable
COMMON.DUIFHPRC to the procedure name. See IBM Z NetView Programming: Assembler for an
explanation of return codes. Determine the cause of
DUI363E UNABLE TO ALLOCATE STORAGE the error and correct the problem. Restart DUIFSSCO.
FOR VECTOR TABLE IN SCOPE If you cannot resolve the problem, contact IBM
CHECKER OPT. Software Support.
Explanation DUI373E NETVIEW SUBSYSTEM NOT

AVAILABLE FOR PROGRAM TO
The scope checker optional task (OPT) received a PROGRAM INTERFACE REQUEST
failure return code from DUIFLAMC, which was called FROM task.
upon to allocate storage for the Graphic Monitor
Facility host subsystem vector table. Explanation
System action An attempt by the named task to request the status of

the NetView subsystem failed.
This message is sent to the authorized receiver and
the scope checker OPT ends. Message Variables
task
Operator response The name of the task that cannot communicate
with the PPI.
System action
This message is sent to the authorized receiver, and
Ensure that the NetView region size is large enough. If the named task retries its status query.
it is not, resolve the storage problem and restart
DUIFSSCO.

Operator response command
The name of the command that was invoked
incorrectly.

System action
Determine whether the NetView subsystem is active.
The command is not executed.
Correct the problem and restart the task. If you cannot
resolve the problem, contact IBM Software Support. DUI376E GMFHS SCOPE CHECKER OPT
PROGRAM TO PROGRAM
DUI374E task ATTEMPTED TO ESTABLISH
INTERFACE SEND FAILURE,
COMMUNICATIONS WITH
SENDER ID = sender, RECEIVER ID
CNMTAMEL, BUT FAILED BECAUSE
= recvrid, RETURN CODE = retcode
CNMTAMEL IS NOT ACTIVE OR IS
NOT FUNCTIONING AS A STATUS
FOCAL POINT Explanation
An attempt to send a data buffer to a program-to-
Explanation program interface failed.
The Graphic Monitor Facility host subsystem (GMFHS) Message Variables
tasks cannot connect to the CNMTAMEL task because
sender
CNMTAMEL is not functioning as a status focal point,
The ID used by the sender to identify itself in the
or is not active. The GMFHS tasks cannot serve the
program-to-program interface Send a Data Buffer
Graphic Monitor Facility workstations.
to a Receiver request.
Message Variables recvrid
task The ID used by the sender to identify the receiver
The name of the GMFHS task that attempted to in the program-to-program interface Send a Data
communicate with the CNMTAMEL task. Buffer to a Receiver request.
retcode
System action The program-to-program interface return code
that describes the failure.
The Graphic Monitor Facility host subsystem tasks
periodically attempt to communicate with the
CNMTAMEL task. System action
The data buffer is not sent to the receiver.
Operator response
Start the CNMTAMEL task as a status focal point. If Operator response
you cannot start it as a status focal point, notify the Notify the system programmer.
system programmer.
Ensure that the Graphic Monitor Facility host Guide for an explanation of the return code. Determine
subsystem is installed at a NetView host using the the cause of the error and correct the problem. If you
central system installation option. cannot correct the problem, contact IBM Software
Support.
DUI375I COMMAND command NOT
AVAILABLE. DUI377E GMFHS SCOPE CHECKER OPT
PROGRAM TO PROGRAM
Explanation INTERFACE RECEIVE FAILURE,
SENDER ID = sender, RECEIVER ID
The specified command was invoked in an incorrect
= recvrid, RETURN CODE = retcode
environment. If command is DUIFECMV, this
command processor can only be invoked under the
DUIFEAUT autotask. Otherwise, commandis a Explanation
command processor that cannot be invoked from an An attempt to receive a data buffer from the receiver's
operator console. program-to-program interface receiver buffer queue
Message Variables failed.

Message Variables DUI380I DUIFSSCO SCOPE CHECKER OPT
SUCCESSFULLY INITIALIZED.
sender
The ID used by the sender to identify itself in the
program-to-program interface Receive a Data Explanation
Buffer to a Receiver request. The scope checker optional task, DUIFSSCO, has
recvrid initialized successfully.
The ID used by the sender to identify the receiver
in the program-to-program interface Receive a System action
Data Buffer to a Receiver request.
retcode processing continues.
The program-to-program interface return code
that describes the failure. DUI381I DUIFSSCO SCOPE CHECKER OPT
HAS TERMINATED.
System action
Explanation
The data buffer is not received by the receiver.
The scope checker optional task (OPT), DUIFSSCO,
Operator response has ended successfully.

System action
System programmer response This message is sent to the authorized receiver and
the scope checker OPT ends.
Guide for an explanation of the return code. Determine DUI382E ALERT AUTOMATION BUFFER
the cause of the error and correct the problem. If you DOES NOT CONTAIN AIFR
cannot correct the problem, contact IBM Software
Support. Explanation
DUI378I ALERT LOST, SUBSYSTEM You automated an alert or resolution, but the buffer
MEMORY NOT AVAILABLE received by the alert automation command processor
does not contain an automated internal function
Explanation request (AIFR).
An attempt to send an alert or resolution to the This message is related to DUI384E and DUI385E.
Graphic Monitor Facility host subsystem host failed
either because memory was not available in the System action
NetView subsystem or because the program-to-
The alert automation command processor does not
program interface queue is full.
send the alert or resolution to the Graphic Monitor
Facility host subsystem. Any status information
System action contained in the alert or resolution is lost.
The status information contained in the alert or
resolution is not received by the Graphic Monitor Operator response
Facility host subsystem host. If the resource identified
in the alert or resolution is defined as an object in
RODM, the status information is not applied to that
object. If the object is also represented in a view, the System programmer response
status information is not reported in the view. Contact IBM Software Support.
DUI383I DUIFSSCO SCOPE CHECKER OPT
Operator response
TERMINATION IN PROGRESS.
Explanation
The scope checker optional task (OPT), DUIFSSCO,
Determine the cause of the memory shortage in the has received a termination notice from the NetView
NetView subsystem and correct the problem. program.

System action DUI390I COS GATEWAY COMMAND
PROCESSOR SUCCESSFULLY
INITIALIZED.
the scope checker OPT waits for the outstanding timer
to be posted by the primary program operator
interface task (PPT). DUIFSSCO ends after the Explanation
outstanding timer is posted. The maximum timer value The common operations services (COS) gateway
is 30 seconds. command processor has initialized its environment
DUI384E ALERT AUTOMATION BUFFER after being invoked by autotask DUIFCSGW.
DOES NOT CONTAIN THE MSU. DUI391E COS GATEWAY COMMAND
PROCESSOR FAILED WITH
Explanation RETURN CODE retcode
You automated an alert or resolution, but the buffer
received by the alert automation command processor Explanation
contains an AIFR that is missing the MSU. The common operations services (COS) gateway
This message is related to DUI382E and DUI385E. command processor was invoked under autotask
DUIFCSGW, but was unable to initialize its
environment.
System action
Message Variables
The alert automation command processor does not
send the alert or resolution to the Graphic Monitor retcode
Facility host subsystem. Any status information The return code. The values are:
contained in the alert or resolution is lost.
Code
Meaning
Operator response
100
Notify the system programmer. Unable to obtain storage for the DUIFCSGB
control block.
System programmer response 104
Contact IBM Software Support. Unable to issue DSIPUSH for the DUIFCSGB
control block.
DUI385E ALERT AUTOMATION BUFFER 108
DOES NOT CONTAIN THE Unable to determine the RUNCMD verb.
XTMALERT.
System action
Explanation
The COS gateway is unable to service Graphic Monitor
You automated an alert or resolution, but the buffer Facility host subsystem requests.
received by the alert automation command processor
contains an AIFR that is missing the hardware monitor
resource hierarchy. Operator response
This message is related to DUI382E and DUI384E. Notify the system programmer.
The alert automation command processor does not If you received return code 108, ensure that a
send the alert or resolution to the Graphic Monitor CMDDEF for load module DSIYORNP exists in
Facility host subsystem. Any status information CNMCMD. If you received return code 100 or 104,
contained in the alert or resolution is lost. contact IBM Software Support.
DUI392E COS GATEWAY STORAGE
Operator response REQUEST FAILED IN MODULE
module, LOCATION X'locid'


The common operations services (COS) gateway See IBM Z NetView Programming: Assembler for an
command processor was unable to obtain storage in explanation of the return code accompanying the MS
the specified module. transport request, or contact IBM Software Support.
Message Variables DUI394E COS GATEWAY COMMAND
REQUEST FOR SERVICE POINT
module
servpt FROM source WITH INPUT
The name of the module where storage was
CORRELATOR X'inpcorr' LOCAL
requested.
CORRELATOR X'lclcorr' FAILED
locid WITH RETURN CODE X'retcode'
The identifier of the storage requested.
Explanation
System action
A common operations services (COS) gateway request
The COS gateway request ends. from either the Graphic Monitor Facility host
subsystem (GMFHS) or the management services (MS)
Operator response transport failed.
Determine whether you received message BNH16I, Message Variables
which means the task has reached its storage limit. If
servpt
so, notify your system programmer.
The service point name, or N/A (not available).
source
Either the GMFHS or the MS transport.
See the IBM Z NetView Troubleshooting Guide for inpcorr
possible causes of the storage shortage. If necessary, The input correlator associated with the request
contact IBM Software Support. from source. If the source is the MS transport, this
DUI393E COS GATEWAY MS TRANSPORT is the correlator on the input agent unit of work.
REQUEST: request FAILED WITH lclcorr
RETURN CODE retcode IN MODULE The local correlator generated by the COS gateway
module for this request. If the local correlator value is 0, a
local correlator was not generated.
Explanation retcode
The common operations services (COS) gateway A hexadecimal value indicating the nature of the
command processor failed while attempting to use the error. The values are:
management services (MS) transport. Code
Message Variables Meaning
2020
request
Input was not recognized or there was a length
The MS transport request type, such as REGISTER
field mismatch.
or DSI6SNDS.
2021
retcode
An error was received from the RUNCMD
The return code from the MS transport request.
command processor.
module
2022
The module that issued the request.
The COS gateway was unable to obtain
storage.
System action
2023
The COS gateway request ends. The DSIGDS task was unable to deliver the
command. This might be a temporary error if
Operator response the service point is busy.

The COS gateway was unable to initialize its
environment.

2025 System action
A response that is not valid was received from
The COS gateway request ends.
the service point.
2026
Operator response
A response was received from the service point
but it did not contain data. Notify the system programmer.
2027
Input from the GMFHS is missing a required System programmer response
parameter. Examine the network log for error messages related to
2028 program-to-program interface processing.
The service point reply contained an error
DUI396E COS GATEWAY RECEIVED A
subvector.
REPLY FROM source value,
2029 INTERNAL CORRELATOR X'corr'
The service point did not reply within the THAT DID NOT MATCH ANY
timeout value. This might be a temporary error OUTSTANDING COMMAND
if the service point is busy. REQUESTS
202A
The command request was canceled because Explanation
the COS gateway task ended.
The common operations services (COS) gateway
202B received a reply from the service point or the
The command request was canceled because management services (MS) transport, but was unable
of an MS transport error. to correlate it with any outstanding request.
202C
Message Variables
The target service is busy. This might be a
temporary error. source
Either the service point or the MS transport.
System action value
Either the service point name or, for the MS
The COS gateway request ends.
transport, the origin NetView program name.
Operator response corr

The internal correlator value associated with this
Notify the system programmer. reply. This is the value that did not match any
outstanding requests.
If you receive return code X'202A', determine why the System action
COS gateway task, DUIFCSGW, ended. Examine the The reply is discarded.
network log for an error message received by task
DUIFCSGW. If you are unable to resolve the problem, Operator response
DUI395E COS GATEWAY PROGRAM TO
PROGRAM INTERFACE SEND
FAILED WITH RETURN CODE =
X'retcode' Examine the network log for error messages related to
COS gateway processing. Look for a DUI394E message
Explanation that contains the same internal correlator value.
The common operations services (COS) gateway failed DUI397E COS GATEWAY RECEIVED SENSE
to communicate with the Graphic Monitor Facility host X'sense' FOR MS-TRANSPORT TO
subsystem across the program-to-program interface. NETWORK: network NODE: node
APPLICATION: applid
Message Variables
retcode
The value received from utility routine DUIFEXPP.

The common operations services (COS) gateway Check the NetView log for accompanying messages
application in the issuing NetView program was unable DUI403 and DUI430. If you are unable to resolve the
to communicate with the COS gateway application in problem, contact IBM Software Support and provide
the specified NetView program. the accompanying messages.
Message Variables Check the NetView log for accompanying messages
BNH821I or BNH822I. If either of these messages is
sense
displayed, this might signal incompatibility with the
The Systems Network Architecture (SNA) sense
setting for the TAMEL.TTLS statement in the
code received in the SNA condition report.
CNMSTYLE member and the configuration of the
network TCP/IP stack or with the policies defined to the z/OS
The network name received in the SNA condition Communications Server Policy Agent.
report.
node SUCCESSFULLY.
The name of the node received in the SNA COMMUNICATION TO IP 'ipid:port'
condition report. STARTED.
applid
The application name received in the SNA Explanation
condition report. It should be DUIFCSGW.
The NETCONV START request processed successfully.
System action Message Variables
The COS gateway request ends. ipid:port
The IP name or address and, if specified, the port
Operator response associated with the value of the IP keyword on the
NETCONV command. It is in the form
Notify the system programmer. ipv4address:port for an IPv4 address or
[ipv6address]:port for an IPv6 address.
Determine whether the COS gateway autotask, System action
DUIFCSGW, is started in the specified NetView Processing continues.
program.
DUI402I IP 'ipid:port' HAS ALREADY BEEN
DUI400W IP COMMUNICATIONS SETUP FOR STARTED BY operatorid.
IP 'ipid:port' HAS FAILED. THE CONDITION CODE = condcode
NETCONV START COMMAND IS
REJECTED.
Explanation
Explanation The NETCONV START request is ignored because

communication to the specified IP has already been
The IP communication setup has failed. established, or a NETCONV START command is
Message Variables currently being processed.
ipid:port Message Variables

The IP name or address and, if specified, the port ipid:port
associated with the value of the IP keyword on the The IP name or address and, if specified, the port
NETCONV command. It is in the form associated with the value of the IP keyword on the
ipv4address:port for an IPv4 address or NETCONV command. It is in the form
[ipv6address]:port for an IPv6 address. ipv4address:port for an IPv4 address or
System action operatorid
The NETCONV command is ignored. The ID of the operator who had previously issued
the NETCONV START request.
Operator response condcode
The condition code, which is one of the following:

1 ipid:port
Communication has already been established The IP name or address and, if specified, the port
by the other operator. associated with the value of the IP keyword on the
2 NETCONV command. It is in the form
A NETCONV START command issued by the ipv4address:port for an IPv4 address or
listed operator is currently outstanding. [ipv6address]:port for an IPv6 address.
retcode
System action The return code from the NetView Message
Queueing Service (hexadecimal).
System action
Operator response
The NETCONV START request is ignored.
Operator response
DUI403I CONNECTION socketnum
EXCEEDED THE MAXIMUM
maxsocket System programmer response
See IBM Z NetView Programming: Assembler for the
Explanation meaning of the return code.
The maximum number of NETCONV connections were DUI405E COMMUNICATION TO IP 'ipid:port'
exceeded for this socketnum. TERMINATED ABNORMALLY:
TCP/IP HAS TERMINATED.
Message Variables
socketnum Explanation
The number of NETCONV connections that was
attempted. TCP/IP has ended. Therefore, the IP conversations for
ipid:port have ended abnormally.
maxsocket
The maximum number of NETCONV connections Message Variables
allowed. The number will be one less than the ipid:port
number specified on the SOCKETS keyword in The IP name or address and, if specified, the port
DSIPARM member DUIFPMEM. associated with the value of the IP keyword on the
System action ipv4address:port for an IPv4 address or
Processing continues but the NETCONV START [ipv6address]:port for an IPv6 address.
command is rejected.
System action
System programmer response The conversations end.
Increase the value for the SOCKETS keyword in
DSIPARM member DUIFPMEM. Verify that TCP/IP is Operator response
active and configured correctly. Verify that the Notify the system programmer.
workstation server has been started and is currently
operating. Contact IBM Software Support if the
problem persists. System programmer response
Determine the reason TCP/IP ended and restart
DUI404E NETCONV START FOR IP 'ipid:port'
TCP/IP. When connectivity has been established,
REJECTED. DSIMQS FAILED WITH
reissue the NETCONV command.
RC=retcode.
Note: When NETCONV is ended because TCP/IP
Explanation ended, it can take from 1–60 seconds before
CNMTAMEL is updated with this information.
The NetView message queueing service request
(DSIMQS) for the NETCONV START request failed.
Message Variables

DUI406E COMMUNICATION TO IP 'ipid:port' DUI408I A NETCONV STOP REQUEST FOR
TERMINATED ABNORMALLY: IP 'ipid:port' THAT WAS ISSUED
VTAM TPEND. BY operatorid COULD NOT BE
PROCESSED.
Explanation
Explanation
VTAM ended and therefore the IP conversations for
ipid:port also ended abnormally. The system cannot process the NETCONV STOP
request. This message can be generated by any of the
Message Variables
following situations:
ipid:port
• Communication has already stopped because of the
ending of the CNMTAMEL task.
associated with the value of the IP keyword on the
NETCONV command. It is in the form • Communication has not been started for this IP
ipv4address:port for an IPv4 address or address/name and port.
[ipv6address]:port for an IPv6 address. • Communication is in the process of becoming active.
• The operator who issued the stop command did not
System action issue the NETCONV START request.
The conversations end. Message Variables
ipid:port
Operator response
Notify the system programmer. associated with the value of the IP keyword on the
System programmer response ipv4address:port for an IPv4 address or
Determine the reason VTAM ended, restart VTAM,
operatorid
establish connectivity, and reissue the NETCONV
The ID of the operator who issued the NETCONV
command.
STOP request.
DUI407I A DUPLICATE NETCONV START
REQUEST WAS ISSUED FOR IP System action
'ipid:port'. THE REQUEST IS
IGNORED. The request is ignored.
DUI409E COMMUNICATION TO IP 'ipid:port'
Explanation TERMINATED ABNORMALLY: OST
The NETCONV START request has already been ABEND.
issued.
Explanation
Message Variables
The operator station task (OST) that issued the
ipid:port NETCONV command for IP ipid:port abended and
The IP name or address and, if specified, the port therefore the conversations ended abnormally.
NETCONV command. It is in the form Message Variables
ipv4address:port for an IPv4 address or ipid:port
[ipv6address]:port for an IPv6 address. The IP name or address and, if specified, the port
System action NETCONV command. It is in the form
ipv4address:port for an IPv4 address or
Operator response
System action
The conversations end.

Operator response Operator response
Reissue the NETCONV command from another Notify the system programmer.
Determine why the CNMTAMEL task is ending and
Determine the reason for the abend and correct the correct the error, if any. Restart the CNMTAMEL task
error. and reestablish communication using the NETCONV
command.
TERMINATED ABNORMALLY: DUI412E COMMUNICATION TO IP 'ipid:port'
OPERATOR LOGOFF. TERMINATED ABNORMALLY:
FATAL ERROR DURING RECEIVE.
Explanation
Explanation
The operator that issued the NETCONV command for
IP ipid:port logged off; therefore, the conversations The host encountered a fatal error while attempting to
ended abnormally. receive data from the workstation with the ipid:port.
The conversations ended abnormally.
Message Variables
Message Variables
ipid:port
The IP name or address and, if specified, the port ipid:port
associated with the value of the IP keyword on the The IP name or address and, if specified, the port
NETCONV command. It is in the form associated with the value of the IP keyword on the
ipv4address:port for an IPv4 address or NETCONV command. It is in the form
[ipv6address]:port for an IPv6 address. ipv4address:port for an IPv4 address or
System action Note: If, for this connection, the CNMTAMEL task
The conversations end. is the server, then the IP address that is displayed
is the client IP address, and no port number is in
the message variable.
Operator response
Reissue the NETCONV command from another System action
TERMINATED ABNORMALLY: Operator response
CNMTAMEL TASK IS
TERMINATING. Notify the system programmer.

The CNMTAMEL task on the host is ending and Interpret the return codes in message DUI430I,
therefore the conversations with the workstation with correct the error, and re-establish communication
IP ipid:port ended abnormally. using the NETCONV command.
Message Variables DUI413E COMMUNICATION TO IP 'ipid:port'
ipid:port
FATAL ERROR DURING SEND.
NETCONV command. It is in the form Explanation
ipv4address:port for an IPv4 address or The host encountered a fatal error while attempting to
[ipv6address]:port for an IPv6 address. send status data to the workstation with IP ipid:port.
The conversations ended abnormally.
System action
Message Variables

ipid:port Explanation
The host received data from the workstation with IP
ipid:port. The data was not as expected and the
conversations ended abnormally.
[ipv6address]:port for an IPv6 address. Message Variables
ipid:port
System action The IP name or address and, if specified, the port
The conversations end. associated with the value of the IP keyword on the
Operator response
System action
Interpret the return codes in message DSI769I,
correct the error, and re-establish communication Operator response
using the NETCONV command.
TERMINATED ABNORMALLY: System programmer response
FATAL ERROR
Explanation DUI416E COMMUNICATION TO IP 'ipid:port'
The host encountered a fatal error while attempting to TERMINATED ABNORMALLY:
communicate with the workstation with the IP WORKSTATION FATAL ERROR.
ipid:port. The conversations ended abnormally.
Explanation
Message Variables
The workstation with IP ipid:port encountered an
ipid:port
error. The workstation initiated conversation
termination.
NETCONV command. It is in the form Message Variables
ipid:port
System action NETCONV command. It is in the form
The conversations end. ipv4address:port for an IPv4 address or
Operator response
System action
Operator response
TERMINATED ABNORMALLY: System programmer response
RECEIVED DATA THAT WAS NOT
VALID. Determine the error detected by the workstation,
correct it, and re-establish communications using the
NETCONV command.
SUCCESSFULLY.

COMMUNICATION TO IP 'ipid:port' Explanation
STOPPED.
A NETCONV START command was issued to IP
ipid:port, which has failed for one of the following
Explanation reasons:
A NETCONV STOP request was processed • IP ipid:port is communicating with another status
successfully. focal point, and can communicate with only one
Message Variables status focal point at a time.
• The workstation is running a release of the NetView
ipid:port
program that is not compatible with the release used
by the status focal point.
NETCONV command. It is in the form • The workstation is already communicating with the
ipv4address:port for an IPv4 address or focal point through an LU6.2 or TCP/IP session.
[ipv6address]:port for an IPv6 address. Message Variables
System action ipid:port

Processing continues on other requests. associated with the value of the IP keyword on the
DUI419I COMMUNICATION TO IP 'ipid:port'
TERMINATED NORMALLY. THE
COMMUNICATION SERVER
CLOSED THE SOCKET.
System action
Explanation The NETCONV START command is rejected and no
communication occurs between the status focal point
The communication server at the specified IP ipid:port
and the IP host name, address, and port.
brought down the IP connection to the status focal
point. The communication server either ended or
rejected the connection from the status focal point. Operator response
Message Variables Determine if the workstation is communicating with

another status focal point.
ipid:port
The IP name or address and, if specified, the port 1. If it is possible, determine the host with which the
associated with the value of the IP keyword on the workstation is to be communicating and reroute the
NETCONV command. It is in the form session.
ipv4address:port for an IPv4 address or 2. If the workstation is communicating with another
[ipv6address]:port for an IPv6 address. status focal point in error, issue the NETCONV
STOP command from that host, and reissue the
System action NETCONV START command from the correct status
focal point host.
3. If the workstation is not communicating with
another status focal point, notify the system
Operator response
programmer.
If you desire to communicate with the workstation, 4. Issue NETCONV ACTION=LIST OPID=ALL to
verify that the communication server is active, verify determine which workstations currently have an
that there is not an LU 6.2 connection to the LU6.2 or TCP/IP session with this host.
communication server and reissue the NETCONV
START command.
DUI421E THE NETCONV START COMMAND
Check the version and release levels of the
HAS FAILED BECAUSE IP
workstation and the NetView status focal point. Ensure
'ipid:port' IS COMMUNICATING
that they are both running the same version and
WITH ANOTHER STATUS FOCAL
release of the NetView program.
POINT, IS RUNNING AN
UNSUPPORTED LEVEL OF NMC, OR DUI422E CNMTAMEL FAILED TO RECEIVE
IS ALREADY COMMUNICATING DATA FROM IP 'ipid:port' DUE TO
WITH THIS STATUS FOCAL POINT. A STORAGE SHORTAGE.

REQUESTED AMOUNT = amount Operator response
BYTES.
Explanation
CNMTAMEL attempted to receive data from a server
Locate the data server workstation that is not
workstation, but cannot get enough storage to satisfy
responding. Attempt to determine the problem with
the request.
the workstation and correct it. The status focal point
Message Variables has detected that the workstation is not responding
and cannot communicate with it. If the workstation
ipid:port
appears to be responding properly, the problem might
be the result of memory constraints at the data server
workstation.
ipv4address:port for an IPv4 address or Verify that you have enough memory on the
[ipv6address]:port for an IPv6 address. workstation. See the IBM Z NetView Tuning Guide.
amount Restart the IP connections to the workstation by using
The amount of storage that CNMTAMEL attempted the NETCONV command.
to get. DUI424I OPERATOR operatorid IS
COMMUNICATING WITH
System action WORKSTATION AT IP 'ipid:port'.
The IP connection between the status focal point host
and the IP host name and address ends. Explanation
The specified operator has established a session with
Operator response the specified workstation IP identifier through an IP
connection. This message is a response to issuing the
Notify the system programmer of the storage
NETCONV command with the ACTION=LIST
problems. Reissue the NETCONV command.
parameter.
System programmer response Message Variables
If the problem persists, contact IBM Software Support. operatorid

The ID of the NetView operator that logged on.
ipid:port
WORKSTATION NOT
RESPONDING.
Explanation [ipv6address]:port for an IPv6 address.
The CNMTAMEL task detected a data server DUI427E ERROR. CNMTAMEL ATTEMPTED
workstation that is not responding, and has TO TERMINATE COMMUNICATION
abnormally ended the IP connections to the TO AN UNRECOGNIZED
workstation. WORKSTATION.
Message Variables
ipid:port Explanation
The IP name or address and, if specified, the port An internal function either made an attempt to end a
associated with the value of the IP keyword on the connection from the host to a workstation that does
NETCONV command. It is in the form not exist or through a connection path that does not
ipv4address:port for an IPv4 address or exist.
System action
System action
All IP connections to the data server workstation that
is not responding are ended.

Operator response System action
Notify the system programmer. Processing continues.
System programmer response Operator response

Recycle the CNMTAMEL task. Notify the system programmer.
DUI430I UNSUCCESSFULL CALL TO
function, ERRNO= errorcode. System programmer response
If TCP/IP is used, verify that TCP/IP is active and
Explanation configured correctly. Verify that the workstation server
has been started and is currently operating. If TCP/IP
The CNMTAMEL, DSIRTTR, or DUIDGHB task received is not used, ensure that the TASK.DUIDGHB.INIT
an error on a library function call. statement in the CNMSTYLE member is set to NO.
This message can be issued by the CNMTAMEL, Otherwise, the NetView program continues to attempt
DSIRTTR, or DUIDGHB task. The operator ID field in to attain the host name from the TCP/IP address.
the NetView log contains the name of the task that For more information about the return codes, refer to
logs the message. This task name can be the task that the TCP/IP library. Note the library function and return
issues the message or the name of the NetView code and contact IBM Software Support.
authorized receiver. If column 24 of this message in
the NetView Log contains a percent sign (%), then the DUI431E COMMUNICATION CANNOT BE
message is logged by the authorized receiver and not ESTABLISHED VIA A TCP/IP
by the task that issues the message. To determine CONNECTION. THE NETCONV
which of the above tasks issued this message, issue COMMAND IS IGNORED.
the DEFAULTS MSGMODID=YES command. When the
MSGMODID operand is specified, the DSI799I Explanation
message is logged whenever a message is issued and
the operator ID field in the DSI799I message contains The host NetView cannot connect to an IP
the name of the task that issues the message. workstation. The initialization parameter that enables
TCP/IP sessions was not set.
Message Variables
function System action
The name of the library function:
The NETCONV command is ignored. Processing
• Accept continues. The host NetView is still able to establish
• Bind LU 6.2 sessions.
• Close
Operator response
• Connect
• GetAddrInfo
• GetClientID System programmer response
• GetHostName
Set the CNMTAMEL initialization parameter USETCPIP
• GetNameInfo to YES in the CNMTAMEL initialization member
• InitAPI DUIFPMEM.
• IOCTL DUI432I AN UNSUCCESSFUL CALL TO
• Listen INITAPI HAS BEEN MADE BY
TASK=task DUE TO AN INVALID
• Recv
TCPANAME VALUE = value IN THE
• Select INPUT FILE file.
• Send
• ShutDown Explanation
• Socket An error occurred calling the TCP/IP function INITAPI
because of a TCPANAME value that is not valid being
errorcode specified in the initialization member of the given task.
The return code from the function call.
Message Variables

task DUI461I IP ipid:port NOT AVAILABLE FOR
The task that attempted to use the TCPANAME WORK; REQUEST TO THIS IP WAS
that was not valid. ABORTED.
value
The TCPANAME value that was not valid. Explanation
file A request was made to a workstation with IP ipid:port
The input file that is being read. that cannot be honored because this IP ipid:port is
either initializing or ending.
The TCP/IP function for this task is not enabled. For ipid:port
the DSIRTTR task, the task ends after this message is The IP name or address and, if specified, the port
received. associated with the value of the IP keyword on the
Operator response ipv4address:port for an IPv4 address or
Notify the system programmer. [ipv6address]:port for an IPv6 address.
System programmer response System action
Check the input file and correct the TCPANAME value The IP host name, address, and host finish ending or
that is not valid. initializing. Upon completing initialization it receives
complete status information.
DUI433I PASSIVE SOCKET
INITIALIZATION FAILED DUE TO DUI500E CNMTAMEL RECEIVED
UNSUCCESSFUL function CORRUPTED DATA FROM IP
FUNCTION CALL ipid:port.
CNMTAMEL received an error on a library function call The CNMTAMEL task does not recognize the data
which was attempting to set up a passive (listen) received from NMC.
socket for which workstation servers can listen. Message Variables
Message Variables ipid:port
function The IP name or address and, if specified, the port
The name of the library function. (Socket, Bind, or associated with the value of the IP keyword on the
Listen) NETCONV command. It is in the form
System action
CNMTAMEL ends. System action
Processing continues, but the corrupted data is not
Operator response processed.
Operator response
System programmer response Record the message and notify the system
Verify that TCP/IP is active and configured correctly. programmer.
Verify that port number specified in DUIFPMEM is not
currently being used. Check the NetView log for System programmer response
message DUI430I for more details about the specific
function call error return code. For more information Contact IBM Software Support.
about the return codes, refer to the TCP/IP library. DUI502E RECORD recnum IN 'member'
Note the library function and return code and contact CANNOT BE PARSED. RETURN
IBM Software Support. CODE FROM DSIPRS WAS retcode.

Explanation DUI505A ERROR CONNECTING TO MEMBER.
RETURN CODE FROM DSIDKS
The record indicated by recnum in the member or file
WAS retcode.
named member cannot be parsed because it contains
an error such as unbalanced quotation marks.
Explanation
Message Variables
An error occurred while attempting to connect to the
recnum member or file noted in message DUI513I.
The number of the record where the error was
found. Message Variables
member retcode
The member or file being read. The hexadecimal return code from DSIDKS.
retcode
The return code given by DSIPRS for the type of System action
error found (hexadecimal). The CNMTAMEL task ends.

Processing continues with the next record. Notify the system programmer.

Check the input file for typographical errors. If none Check for errors initializing the NetView program. Most
are found, contact the system programmer. likely this is a storage allocation error. Check return
code from DSIDKS (retcode).
DUI506E ERROR FINDING FILE 'file' OR
Check the input file for errors. An explanation of the READING FIRST RECORD.
return codes for DSIPRS can be found in IBM Z RETURN CODE FROM DSIDKS
NetView Programming: Assembler. WAS retcode.
DUI504I NO VALID SC SPECIFICATIONS IN
USER-SUPPLIED INPUT FILE 'file'. Explanation
An error occurred while attempting to find the file in
Explanation the data set.
No valid status collectors (SCs) were specified in the Message Variables
input file.
file
Message Variables The name of the file causing this error.
file retcode
The user-supplied input file. The hexadecimal return code from DSIDKS.

Processing continues. The command or processing ends.
If the message is issued during CNMTAMEL task
Operator response initialization, then CNMTAMEL task initialization ends.
Check the input file for the SC specifications. There are
either none in the file, or none of the specifications are Operator response
valid. Incorrect SC specifications were to have been
Check the file name in the error message, and ensure
flagged when processing was attempted. Replace or
that it is correct and exists in the data set being read.
remove any SC specification that is not valid from the
The file can be empty.
file.

Check the input file for incorrect or nonexistent SC
specifications.

Locate the source of the problem by checking the The CNMTAMEL task is initializing as a status focal
DSIDKS return code. See IBM Z NetView Programming: point.
Assembler.
DUI526E ERROR. THE KEYWORD 'keyword'
DUI507E ERROR READING FILE 'file'. IN THE INPUT FILE 'file'
RETURN CODE FROM DSIDKS CONTAINS AN INVALID VALUE
WAS retcode. 'value'.
An error occurred while attempting to read from a A value was entered for keyword that is not valid.
member in the data set.
Message Variables
Message Variables
keyword
file The keyword whose value is in error.
The file being read when the error occurred. file
retcode The input file that is being read.
The hexadecimal return code from DSIDKS. value
The value that is in error.
System action
The command or processing ends. System action
If the message is issued during CNMTAMEL task CNMTAMEL task initialization ends.
initialization, then CNMTAMEL task initialization ends.
Operator response
Operator response Notify the system programmer.
Ensure that the file (member) was set up correctly for
reading. If it was, notify the system programmer. System programmer response
Check the input file and correct the statement that
System programmer response contains the keyword with the value that is not valid.
Locate the source of the problem by checking the
DUI527E RESOURCE STATUS 'status' IS
DSIDKS return code. See IBM Z NetView Programming:
SPECIFIED MORE THAN ONCE IN
Assembler. Further action must be based on the
'member'.
problem source.
DUI513I STATUS FOCAL POINT READING Explanation
INITIALIZATION PARAMETERS
Each status known to the resource status manager
FROM 'sfpname' AS SPECIFIED IN
must be specified only once on a STATUSTABLE
'initmem'.
statement. The status status was specified more than
once on the STATUSTABLE statement in the member
Explanation member.
The initialization parameters for the status focal point Message Variables
are being read.
status
Message Variables The status name that is specified more than once
sfpname member
The status focal point parameters member or file. The name of the member or file being read
initmem
The initialization member or file for the CNMTAMEL System action
task.
CNMTAMEL task initialization fails.
Operator response

Correct the status decision table in the member Notify the system programmer.
specified or specify a member with a correct
STATUSTABLE statement on the FPPARMS parameter System programmer response
of the AMELINIT statement.
Verify the syntax of the DUIFECMV command for the
DUI528E RESOURCE STATUS 'status' proper number and combination of parameters. For
ENCOUNTERED IN 'member' IS more information on the DUIFECMV command, see the
NOT VALID. IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide.
Explanation
DUI531E THE KEYWORD GMFHSDOM IN
A value that is not valid, status, was encountered while THE DUIFECMV COMMAND
reading the STATUSTABLE values from the DSIPARM CONTAINS THE VALUE domain
member member. WHICH IS AN INVALID DOMAIN
ID.
Message Variables
status Explanation
The incorrect status name.
The domain name given is incorrect for one of the
member following reasons:
The member or file being read.
• The DOMAIN keyword is specified without a domain
System action name.
• The specified domain name is longer than 5
CNMTAMEL task initialization fails.
characters.
• The domain name contains one or more non-
Operator response
alphanumeric characters.
Message Variables
System programmer response domain

The incorrect user-specified domain ID for the
Correct the status decision table in the member GMFHSDOM parameter on the DUIFECMV
specified or specify a member on the FPPARMS command.
parameter of the AMELINIT statement with a correct
STATUSTABLE. See the IBM Z NetView Administration
System action
Reference for more information.
The status information contained in the alert or
DUI530I THE REQUIRED NUMBER OF
resolution is not received by the NMC.
PARAMETERS WAS NOT
SPECIFIED FOR THE DUIFECMV
COMMAND. Operator response
Explanation
The DUIFECMV command can be issued with: System programmer response
• No parameters Correct the domain name specified by the DUIFECMV

command in the automation table.
• One optional GMFHSDOM parameter
• Five parameters that are DOMAIN, CLASS, STATUS, DUI532E UNRECOGNIZED BUFFER 'buffer'
OBJNAME, and INDICAT FROM SNA TOPOLOGY MANAGER
RECEIVED BY STATUS
• Six parameters that are DOMAIN, CLASS, STATUS, COLLECTOR. THE BUFFER IS
OBJNAME, INDICAT, and the optional GMFHSDOM IGNORED.

The DUIFECMV command ends. The status collector received an unrecognized buffer
from the SNA topology manager.

Message Variables same. See the IBM Z NetView Administration Reference
buffer
Up to 32 bytes of the received buffer. DUI534E ERROR. THE KEYWORD 'keyword'
WAS NOT SPECIFIED IN THE
System action INPUT FILE 'file'.
The buffer is discarded.

Explanation
Operator response The required keyword keyword is not specified in the

input file.
Message Variables
System programmer response keyword
The keyword that is missing.
Trace the RU through which the message travels and
determine if the error originates from the SNA file
topology manager or is caused by the underlying The input file that is being read.
communication component. A status collector must
never receive buffers from the SNA topology manager. System action
This error can occur as a result of terminating the
CNMTAMEL task which was running as the status focal CNMTAMEL task initialization ends.
point and recycling it as a status collector. Recycle the
CNMTAMEL task as a status focal point. Operator response
DUI533E ERROR. INCOMPLETE STATUS Notify the system programmer.

DECISION TABLE IN THE INPUT
FILE 'file'. count ENTRIES FOUND, System programmer response
total REQUIRED.
Update the input file so that it contains the required
keyword. See the IBM Z NetView Administration
Explanation Reference for more information.
The status decision table being read from the input file DUI535E ERROR. DUPLICATE KEYWORD
contains only count status names. There must be total
'keyword' SPECIFIED IN THE
entries.
INPUT FILE 'file'.
Message Variables
file Explanation
The input file that is being read. You can specify the keyword keyword only once, and it
count is specified more than once in the input file.
The number of entries specified in the status Message Variables
decision table.
keyword
total
The keyword that is specified more than once.
The number of entries that must be supplied for
the status decision table. file
The input file that is being read.
System action
System action
CNMTAMEL task initialization ends.
Operator response
Operator response
Compare your copy of the status decision table with
the one you received from IBM. The order can be Check the input file and remove the duplicate keyword
changed, but the number of entries must remain the keyword.

DUI536E ERROR. DUPLICATE VALUE 'value' System programmer response
SPECIFIED FOR THE KEYWORD Check the input file and correct the statement
'keyword' IN THE INPUT FILE 'file'. containing the keyword with the value in error.
Explanation DUI538E ERROR. THE RECORD 'record' IN

THE INPUT FILE 'file' IS NOT
The value value is specified more than once in the VALID.
input file.
value An error was found on the record record of file file. It is
The value that is specified more than once. possible that the end of file was encountered while
keyword reading a continued record in the input file file. Check
The keyword that is assigned the value more than for a comma at the end of the last line or a keyword
once. that has not been assigned a value.
file Message Variables

The input file that is being read. record
The record where the error occurred.
System action file
CNMTAMEL task initialization ends. The input file that is being read.

Notify the system programmer. CNMTAMEL task initialization ends.

Check the input file and remove the duplicate value Notify the system programmer.
from the keyword.
IN THE INPUT FILE 'file' Check the record in the input file. If the error was on
CONTAINS A NON-NUMERIC the last record, determine whether a continuation is
VALUE 'value'. desired.
DUI539E ERROR. THE KEYWORD 'keyword1'
Explanation
MUST BE SPECIFIED BEFORE THE
The keyword keyword expects a numeric value but KEYWORD 'keyword2' IN THE
was assigned a non-numeric value. INPUT FILE 'file'.
Message Variables
Explanation
keyword
The keyword whose value is in error. You must specify the keyword keyword1 before any
occurrence of the keyword keyword2.
file
The input file that is being read. Message Variables
value keyword1
The value that is in error. The keyword that must be specified before the
keyword keyword2.
System action keyword2
The keyword that cannot be specified before the
keyword keyword1.
Operator response file

The input file that is being read.

System action keyword
The keyword that is in error.
file
Operator response The input file that is being read.
Notify the system programmer. System action

Move the location of keyword1 so that it precedes any Operator response
occurrence of keyword2.
IN THE INPUT FILE 'file'
CONTAINS THE VALUE 'value'
THAT IS LONGER THAN THE Modify DUIFPMEM so that it contains a valid keyword.
MAXIMUM ALLOWABLE LENGTH The valid keywords are:
OF 'length' CHARACTER(S).
• CODEPAGE
• DIAGNOSE
Explanation
• ENABLE31GDS
The keyword value is too long. This value cannot
exceed length characters. • MAXRESOURCES
• MAXSCCOUNT
Message Variables
• MAXNETWORKDS
keyword
The keyword whose length exceeds the maximum • NULLGDSOPIDS
allowable length. • PORT
file • SC
The input file that is being read. • SOCKETS
value • STATUSTABLE
The value that exceeds that maximum allowable
length. • TCPANAME
length • USETCPIP
The maximum allowable length for the value of the DUI542E ERROR. UNEXPECTED END OF
keyword. FILE IN THE INPUT FILE 'file'.

CNMTAMEL task initialization ends. The end of the file was encountered while reading a
continued record in the input file file. In most cases,
Operator response this is caused by a comma at the end of the last line, or
Notify the system programmer. by a keyword that was not assigned a value.
Message Variables
System programmer response file
Change the value of the keyword in the input file so The name of the input file being read.
that it contains no more than length characters.
System action
IN THE INPUT FILE 'file' IS NOT CNMTAMEL task initialization ends.
VALID.
Operator response
Explanation
The input file contains an incorrect keyword.
Message Variables

Check the last record in the input file and determine The buffer is discarded.
whether a continuation is desired.
DUI546I THE KEYWORD keyword IN THE Operator response
INPUT FILE file CONTAINS THE Verify that you specified the correct name on the TASK
VALUE value WHICH IS INVALID. statement for MOD=CNMTARCA in the CNMSTASK
THE DEFAULT VALUE OF defvalue member. The name must be your DOMAINID
WILL BE USED. concatenated with 'VMT', such as, CNM01VMT, where
in this example DOMAINID=CNM01. If you started
Explanation STATMON dynamically, ensure that you typed the
START TASK= command correctly. For example:
A non-valid value was specified for keyword. The
default value will be used. START TASK=CNM01VMT,MOD=CNMTARCA,PRI=5
Message Variables
It is recommended that you start STATMON using the
keyword TASK definitions in the CNMSTASK member to avoid
The keyword whose value is in error. these errors.
file You might also receive this message for internal
The input file that is being read. errors. If the TASK statements are valid, notify your
value system programmer.
The value that is in error.
defvalue System programmer response
The default value that will be used. Look at the discarded buffer. Bytes 9–17 will contain
the domain with which the focal point is attempting to
System action communicate. The data must be converted from
EBCDIC. This will be the domain of the Resource
Status Collector attempting to send data to this focal
point. For example:
Operator response
DUI551I UNRECOGNIZED BUFFER
Notify the system programmer. '0018010100000000C3D5D4F0F1404040057000010500000
'
RECEIVED BY STATUS FOCAL POINT. THE BUFFER IS
System programmer response IGNORED.
Check the input file and correct the statement where C3D5D4F0F1404040 represents CNM01.
containing the keyword with the value in error. If the
keyword is TTLS, you might have specified a value that Trace the RU through which this message travels and
is not valid for the level of z/OS that is currently determine if the error originates from its sender or is
running. The AT-TLS (Application Transparent caused by the underlying communication components.
Transport Layer Security) function is only available for DUI552I SYNCHRONIZATION FAILED WITH
z/OS V1.7 and later. The TTLS keyword can be STATUS COLLECTOR scname DUE
specified in the CNMSTYLE member by the user and TO STORAGE SHORTAGE
then inserted into the file identified in this message PROBLEMS.
using Data REXX.
DUI551I UNRECOGNIZED BUFFER 'buffer' Explanation
RECEIVED BY STATUS FOCAL
The status focal point cannot complete
POINT. THE BUFFER IS IGNORED.
synchronization with a status collector because of
storage problems.
Explanation
Message Variables
The status focal point received an unrecognized buffer.
scname
Message Variables The status collector that cannot be synchronized.
buffer
Up to 25 bytes of the received buffer.

System action • The status collector is running at a distributed host
and it does not have a status focal point defined.
The focal point does not synchronize with the status
collector, but continues processing other requests. • The status collector host scname is not running as a
status collector.
Operator response • All required tasks have not been started at either the
status focal point host, the status collector host, or
Determine whether you received message BNH16I, both.
so, notify your system programmer. • The status collector is running at a distributed host
and there are underlying communication problems
between the status collector host and the status
focal point host.
See the IBM Z NetView Troubleshooting Guide for • The timer values can be set inappropriately for your
possible causes of the storage shortage. configuration.
DUI563I STATUS FOCAL POINT FAILED TO Message Variables
COMMUNICATE WITH STATUS
COLLECTOR scname. scname
The domain ID of the status collector.
Explanation
System action
An attempt to send the SYNCH command to the status
collector failed. The status of all resources monitored by this status
collector are set to UNKNOWN.
Message Variables
scname Operator response
System action
The status of all resources monitored by this status
Determine the appropriate action from the following
collector are set to UNKNOWN. After your specified
list:
retry interval has passed, the SYNCH command is sent
again. • Define a status focal point for the status collector
and issue the CHANGEFP command.
Operator response • Verify that the status monitor preprocessor has been
run with a valid GRAPHOPT statement. See the IBM
Z NetView Administration Reference for information
on coding the GRAPHOPT statement.
• Ensure that the appropriate tasks are active. These
Check the underlying communication components and tasks include CNMTAMEL and status monitor in all
possible non-released storage. cases, and also LUC and DSICRTR in cross-domain
situations.
DUI564E STATUS FOCAL POINT CANNOT
COMMUNICATE WITH STATUS • Determine the cause of the problem from the
COLLECTOR scname. SYNCH communication error messages.
RETRY THRESHOLD WAS • Determine if the timers are set inappropriately. If so,
EXCEEDED. reset the timeout values in DSICTMOD to higher
values and restart the CNMTAMEL task.
Explanation
DUI565E STATUS FOCAL POINT fpname
There are several situations that can generate this HAS RECEIVED DATA FROM AN
message. It is also possible to receive DUI564E more UNSUPPORTED LEVEL STATUS
than once for a single status collector. This message COLLECTOR scname. THE DATA IS
occurs whenever something happens to cause the DISCARDED.
status focal point to begin attempting synchronization
again. The following are reasons for receiving this
message:

A status collector scname was initialized with a level of The resource status manager has lost its session with
code that is unsupported by its status focal point, the topology services manager.
fpname. The status focal point recognizes that it
cannot communicate with this status collector, so it Operator response
rejects all data received from it and puts out this
message. Notify the system programmer.
Message Variables
fpname
Verify that the FLBTOPO autotask is active. If not,
The name of the status focal point that received
restart the FLBTOPO autotask. If it is active or if
data from an unsupported level status collector.
problems persist, contact IBM Software Support.
scname
The name of the status collector that sent data to a DUI569E STATUS COLLECTOR domainid
status focal point that cannot support it. DOES NOT HAVE REQUIRED PTF
FOR FORWARDING STATUS TO
THE SNA TOPOLOGY MANAGER
System action
This message is displayed and the data is discarded. Explanation
Everything else progresses normally. The status focal
point is not able to synchronize with the status The resource status collector for a NetView Version 2
collector or to collect status from it. program is trying to establish a session with a resource
status manager. The resource status collector does
not have the required PTF applied. For information on
Operator response
required PTFs, see the IBM Z NetView program
Notify the system programmer. directory.
Message Variables
domainid
Determine the level of code installed on the fpname The domain ID of the resource status collector.
host and the level of code installed on the scname
host. Reinstall the correct level of code on either the
System action
fpname host or the scname host so that the status
collector and the focal point are compatible. The status focal point has detected that the status
collector does not have the required PTF for
DUI567I RESOURCE STATUS MANAGER forwarding status to the SNA topology manager. Status
CANNOT ESTABLISH A SESSION will not be forwarded to the SNA topology manager.
WITH SNA TOPOLOGY MANAGER
Operator response
Explanation
The resource status manager cannot establish a
session with the topology services manager.
Operator response Apply the required PTF to the resource status
collector.
DUI579I STATUS FOCAL POINT fpname
System programmer response AND STATUS COLLECTOR scname
ARE SYNCHRONIZED.
Verify that the FLBTOPO autotask is active. If not, start
the FLBTOPO autotask. If it is active or if problems
Explanation
persist, contact IBM Software Support.
The status focal point received a complete REPLY
DUI568I RESOURCE STATUS MANAGER SYNCH from a status collector.
HAS LOST ITS SESSION WITH SNA
TOPOLOGY MANAGER Message Variables
fpname
The domain ID of the status focal point.

scname System programmer response
Trace the messages from the status collector.
System action DUI610E CNMTAMEL FAILED TO SEND TO

SERVER PWS AT LU luname
DUI593I STATUS FOCAL POINT UNABLE TO Explanation
COMMUNICATE WITH STATUS
The resource status manager attempted to send data
COLLECTOR scname - OUT OF
to a data server, and the send failed. There is a
STORAGE CONDITION
problem with the LU 6.2 connection to the server
workstation.
Explanation
Message Variables
The status collector does not have enough storage to
send status to its status focal point. luname
The name of the LU where the send failed.
Message Variables
scname System action
The resource status manager continues processing,
but halts sending to the failed server workstation until
System action the LU 6.2 sessions are re-established and the data
The status focal point sets the status of any resources server re-initializes.
reported by this status collector to UNKNOWN, and
does not attempt to resynch with the status collector. Operator response
Operator response
Notify the system programmer. System programmer response
Check the LU 6.2 sessions between the status focal
System programmer response point host and the server workstation LU indicated in
Check the status collector for an out-of-storage the message. When the connection is reestablished,
condition. When the storage shortage is relieved, reissue the NETCONV command to the LU indicated in
reinitialize the status collector. the message.
DUI601E STATUS UPDATE WAS LOST FROM DUI611I THE OPERATOR ID AND
STATUS COLLECTOR scname. PASSWORD FOR GRAPHIC
MONITOR OPERATOR operatorid
HAS BEEN VERIFIED. ipid:port IS
Explanation
THE SERVER PWS SERVING THIS
The status collector sent an update with an GRAPHIC MONITOR.
unexpected sequence number to its status focal point.
scname The graphic monitor operator identified in the

The domain ID of the status collector. message now has the authority to send commands to
the status focal point through the graphic monitor
commands function.
System action
Message Variables
If the SYNCH retry threshold is not exceeded, the
status focal point tries to resynch with the status operatorid
collector. The ID of the operator that logged on
ipid:port
Operator response The IP name or address and, if specified, the port
of the server workstation that is serving the
graphic monitor. It is in the form ipv4address:port
for an IPv4 address or [ipv6address]:port for an
IPv6 address.

The NetView operator ID and password or password A GETMAIN command issued by the CNMTAMEL task
phrase entered at the graphic monitor are valid and failed. The CNMTAMEL task tried to obtain the number
authorized to enter NetView commands from the of bytes indicated in the message. This storage was to
graphic monitor. be used to respond to a request from a server
workstation. Examples of these requests are:
Operator response • Verify an operator ID and password or password
Information message only. phrase for logging on to the graphic monitor.
• Execute a command request.
This message is logged and provides an audit trail of bytes
the operators who have attempted to use the graphic The number of bytes is the amount of storage that
monitor commands function. the CNMTAMEL task tried to obtain
DUI612E A GRAPHIC MONITOR OPERATOR luname
HAS ATTEMPTED TO LOG ON TO The name of the LU
GRAPHIC MONITOR WITH
operatorid BUT THE OPERATOR ID System action
IS NOT LOGGED ONTO NETVIEW
PROGRAM. The server workstation times out on its outstanding
request to the CNMTAMEL task. Normal operations
resume at the workstation after the time-out
Explanation
processing is complete. Depending on the conditions
The graphic monitor operator must be logged on to the of NetView storage, normal operations might be
NetView system before commands can be accepted. resumed at the host focal point.
Message Variables
operatorid
The ID of the NetView operator attempting to log See the IBM Z NetView Troubleshooting Guide for
on. possible causes of the storage shortage.
DUI614I CNMTAMEL HAS RECEIVED A
System action REQUEST FROM A DATA SERVER
The logon attempt fails and commands cannot be AT LU luname THAT IS RUNNING
accepted from the graphic monitor. AT AN UNSUPPORTED LEVEL. THE
REQUEST IS IGNORED.
Operator response
Explanation
If you are authorized to issue commands from the
graphic monitor, ensure you are logged on to the The data server at the LU luname is not running a
NetView system before attempting to log on to the compatible level of code with the status focal point to
graphic monitor. If you have not been issued a which it is attached. The data server's code must be
NetView operator ID and password or password upgraded.
phrase, notify the system programmer. Message Variables
luname
System programmer response The name of the LU where the unsupported data
If certain graphic monitor operators can enter host server is running.
commands from the graphic monitor, they must be
provided with valid NetView operator IDs and System action
passwords or password phrases.
The data server request is ignored.
DUI613E CNMTAMEL IS UNABLE TO
ALLOCATE bytes BYTES OF Operator response
STORAGE FOR SENDING A
REQUIRED RESPONSE TO SERVER Notify the system programmer.
PWS AT LU luname

Upgrade the down-level data server. Notify the system programmer to correct storage
problems. To force the data server and the CNMTAMEL
DUI615E CNMTAMEL COULD NOT SEND A
task to resynchronize, you can recycle the LU 6.2
DATA PACKET TO THE DATA
session connecting the host and workstation by using
SERVER AT LU luname BECAUSE the NETCONV command.
OF A STORAGE SHORTAGE.

Explanation
If the problem persists, contact IBM Software Support.
The CNMTAMEL task attempted to send data to a
particular data server, but ran out of storage. DUI617E CNMTAMEL FAILED TO SEND
DATA TO THE DATA SERVER AT LU
Message Variables
luname DUE TO AN MQS FAILURE.
luname
The name of the LU where the data server is Explanation
running.
The CNMTAMEL task attempted to send data to the
specified data server, but encountered a message
System action
queuing service (MQS) failure.
The CNMTAMEL task continues processing, but the
Message Variables
data server has missed some data. Message DUI2028
might appear at the specified data server, but the host luname
and workstation will resynchronize automatically, so The name of the LU where the data server is
the loss of data is only a temporary problem. running.

Notify the system programmer to correct storage The CNMTAMEL task continues processing, but the
problems. To force the data server and the CNMTAMEL data server has missed some data. Message DUI2028
task to resynchronize, you can recycle the LU 6.2 might be displayed at the data server, but the host and
session connecting the host and workstation by using workstation will resynchronize automatically.
the NETCONV command.
Operator response
The MQS failure is probably because of storage
If the problem persists, contact IBM Software Support. problems. If the problem persists, notify the system
programmer to investigate storage shortages, and
DUI616E CNMTAMEL COULD NOT issue the NETCONV ACTION=STOP command for the
BROADCAST A DATA PACKET specified LU. When the problems have been cleared,
BECAUSE OF A STORAGE reissue the NETCONV ACTION=START command to
SHORTAGE. reconnect the workstation with the host.

The CNMTAMEL task attempted to send data to all If the problem persists, contact IBM Software Support.
connected data servers, but ran out of storage.
DUI618I THE OPERATOR ID AND
System action PASSWORD FOR COMMAND
PROFILE EDITOR OPERATOR
The CNMTAMEL task continues processing, but the operatorid HAS BEEN VERIFIED.
data servers has missed some data. Message DUI2028 name IS THE SERVER PWS
might appear at any connected data server, but the SERVING THIS COMMAND
host and workstations will resynchronize PROFILE EDITOR.
automatically, so the loss of data is only a temporary
problem.
Explanation
The command profile editor operator identified in the
message now has the authority to send commands to

the status focal point through the command profile System programmer response
editor commands function.
If certain command profile editor operators can enter
Message Variables host commands from the graphic monitor, they must
be provided with valid NetView operator IDs and
operatorid
passwords or password phrases.
The ID of the operator that logged on
name DUI620E CNMTAMEL FAILED TO SEND TO
The LU or IP name or ID of the server workstation SERVER PWS AT IP ipid
that is serving the command profile editor
Explanation
System action The resource status manager attempted to send data
The NetView operator ID and password or password to a data server, and the send failed. There is a
phrase entered at the command profile editor are valid problem with the IP connection to the server
and authorized to enter NetView commands from the workstation.
command profile editor. Message Variables
ipid
Operator response
The IP name and address associated with the
Information message only. value of the IP keyword on the NETCONV
command. It is in the form IPname (IPaddress).
System action
This message is logged and provides an audit trail of
the operators who have attempted to use the The resource status manager continues processing,
command profile editor commands function. but halts sending to the failed server workstation until
the IP sessions are reestablished and the data server
DUI619E A COMMAND PROFILE EDITOR has been reinitialized.
OPERATOR HAS ATTEMPTED TO
LOG ONTO COMMAND PROFILE
EDITOR WITH operatorid BUT THE Operator response
OPERATOR ID IS NOT LOGGED Notify the system programmer.
ONTO NETVIEW PROGRAM.
Explanation
Check the IP sessions between the status focal point
The command profile editor operator must be logged host and the server workstation indicated in the
on to the NetView system before commands can be message. When the connection is reestablished,
accepted. reissue the NETCONV command to the IP host name
Message Variables and address indicated in the message.
operatorid DUI623E CNMTAMEL IS UNABLE TO

The ID of the NetView operator attempting to log ALLOCATE bytes BYTES OF
on STORAGE FOR SENDING A
REQUIRED RESPONSE TO SERVER
PWS AT IP ipid:port
System action
The logon attempt fails and command profiles cannot Explanation
be edited from the command profile editor.
A GETMAIN command issued by the CNMTAMEL task
failed. The CNMTAMEL task tried to obtain the number
Operator response
of bytes indicated in the message. This storage was to
If you are authorized to edit command profiles from be used to respond to a request from a server
the command profile editor, ensure you are logged on workstation. Examples of these requests are:
to the NetView system before attempting to log on to
• Verify an operator ID and password or password
the command profile editor. If you have not been
phrase for logging on to the graphic monitor.
issued a NetView operator ID and password or
password phrase, notify the system programmer. • Execute a command request.
Message Variables

bytes System programmer response
The number of bytes is the amount of storage that
the CNMTAMEL task tried to obtain.
ipid:port DUI627E CNMTAMEL FAILED TO SEND
The IP name or address and, if specified, the port DATA TO THE DATA SERVER AT IP
associated with the value of the IP keyword on the ipid:port DUE TO AN MQS
NETCONV command. It is in the form FAILURE.
[ipv6address]:port for an IPv6 address. Explanation
The CNMTAMEL task attempted to send data to the
System action specified data server, but encountered a message
The server workstation times out on its outstanding queuing service (MQS) failure.
request to the CNMTAMEL task. Normal operations Message Variables
resume at the workstation after the timeout
processing is complete. Depending on the conditions ipid:port
of NetView storage, normal operations might be The IP name or address and, if specified, the port
resumed at the host focal point. associated with the value of the IP keyword on the
possible causes of the storage shortage. System action
DUI625E CNMTAMEL COULD NOT SEND A The CNMTAMEL task continues processing, but the
DATA PACKET TO THE DATA data server has missed some data. Message DUI2028
SERVER AT IP ipid:port BECAUSE might appear at the data server, but the host and
OF A STORAGE SHORTAGE. workstation will resynchronize automatically.
Explanation Operator response

The CNMTAMEL task attempted to send data to a The MQS failure is probably because of storage
particular data server, but ran out of storage. problems. If the problem persists, notify the system
Message Variables programmer to investigate storage shortages, and
issue the NETCONV ACTION=STOP command for the
ipid:port specified IP host name and address. When the
The IP name or address and, if specified, the port problems have been cleared, reissue the NETCONV
associated with the value of the IP keyword on the ACTION=START command to reconnect the
NETCONV command. It is in the form workstation with the host.
[ipv6address]:port for an IPv6 address. System programmer response
System action If the problem persists, contact IBM Software Support.
The CNMTAMEL task continues processing, but the DUI3900E DISPLAYSTATUS OF ONE OR
data server has missed some data. Message DUI2028 MORE AGGREGATES IS
might appear at the specified data server, but the host INCORRECT, RECALCULATE
and workstation will resynchronize automatically, so DISPLAYSTATUS FOR ALL
the loss of data is only a temporary problem. AGGREGATES
Notify the system programmer to correct storage A processing error has prevented the DisplayStatus
problems. To force the data server and the CNMTAMEL field value of one or more aggregate objects in the
task to resynchronize, you can recycle the IP Resource Object Data Manager (RODM) data cache
connection between the host and workstation by using from being recalculated as required.
the NETCONV command.

Graphic Monitor Facility host subsystem (GMFHS) The requested flush of the Graphic Monitor Facility
processing continues. One or more RODM log entries host subsystem (GMFHS) trace table is complete.
are written to describe the cause of the error and to
indicate on which aggregate object processing failed. System action
The contents of the in-storage trace table are written
Operator response
to the data set specified in the CNMT ddname, and the
Notify the system programmer. in-storage trace table is reinitialized.
DUI3904I GMFHS DOMAIN MISSING FROM
System programmer response INITIALIZATION PARAMETERS
Print the RODM log entries (types 1, 2, 3, and 4) to
determine what caused the calculation of the Explanation
DisplayStatus value to fail. Correct the condition
The DOMAIN statement is missing from the GMFHS
causing the error and use the RODM load utility to start
initialization member, the GMFHS start procedure, or
the DUIFFRAS method. This method recalculates the
the GMFHS start command.
DisplayStatus of all aggregate objects.
DUI3901I FLUSHING GMFHS IN STORAGE System action
TRACE TABLE
GMFHS ends.
Explanation
Operator response
You requested that the contents of the Graphic
Monitor Facility host subsystem (GMFHS) in-storage Notify the system programmer.
trace table be written to the data set specified by the
CNMT ddname in the GMFHS job control language System programmer response
(JCL).
Specify the GMFHS DOMAIN parameter and restart
GMFHS. See the IBM Z NetView Administration
System action Reference for more information.
The contents of the in-storage trace table are written DUI3905I GMFHS NETWORK
to the specified data set, and the in-storage trace table CONFIGURATION insert1 FOR
is reinitialized. DOMAIN = insert2
DUI3902I TRACE – DISPLAY OR CHANGE
TRACE PARAMETERS Explanation
GMFHS network configuration initialization has
Explanation completed and has ended in one of the following
This is one of the messages generated in response to states:
your HELP command. This message describes the • COMPLETED SUCCESSFULLY
Graphic Monitor Facility host subsystem (GMFHS)
• COMPLETED WITH ERRORS
TRACE command
• FAILED
System action
Operator response
The system displays a summary of the possible
Graphic Monitor Facility host subsystem (GMFHS) Notify the system programmer.
commands that you can enter.
Operator response If the GMFHS network configuration initialization has
Enter the appropriate command. If you need help, see completed with errors, see the output log entries
the NetView online help for more information about between and including the configuration initialization
the listed commands. start and end times in the message; the default output
log is the internal trace log (CNMT DD). In RODM,
DUI3903I FLUSH OF GMFHS IN STORAGE correct the objects that contain errors. See the IBM Z
TRACE TABLE COMPLETE NetView Data Model Reference for more information.

You might need to issue a GMFHS CONFIG command time
to make the changes effective. The time that the first or only message was logged
within the 30-second interval. This is in the format
If the initialization has failed, see the output log
hhmmss, where hh is the hour (00–23), mm is the
entries between and including the configuration
minutes (00–59), and ss is the seconds (00–59).
initialization start and end times in the message and
contact IBM Software Support; the default output log domainid
is the internal trace log (CNMT DD). The domain ID to which this GMFHS is connected
or attempting to connect.
DUI3912E AN ERROR WAS ENCOUNTERED
INITIALIZING GMFHS METHODS
System action
Explanation Processing continues.
The initial RODM method invoked by GMFHS did not

Operator response
complete successfully.
System action
GMFHS ends because of a critical error. One or more
RODM log entries are issued to report the failure and Use the GMFHS Dbserver audit log print program to list
to provide diagnostic information. If the RODM reason the error synopsis entries from the log at the
code is 45092, another GMFHS was already connected approximate time of the error. Use the time provided
to RODM. If the reason code is 45093, the level of the in the message to limit the period for which the entries
GMFHS methods is incompatible with the version of are printed. Investigate and correct the error
the GMFHS application that attempted the connection described in the printout.
to RODM.
DUI3932I GMFHS IN STORAGE TRACE
TABLE NOT ALLOCATED
Operator response
A request to flush the in-storage trace table was
System programmer response issued, but no table has been allocated.
Print the RODM log entries associated with the failure.
The return and reason codes in the messages along System action
with the information in the log entries can help to
determine the action to be taken to correct the Processing continues.
problem. See the IBM Z NetView Resource Object Data
Manager and GMFHS Programmer's Guide for more System programmer response
information. The in-storage trace table must always be available;
DUI3913E GMFHS TASK task HAS LOGGED this is an internal error. Dump the GMFHS address
AN IMPORTANT MESSAGE AT time space and contact IBM Software Support for more
FOR DOMAIN = domainid information. You can use either GTF or GMFHS job
output files for more job output as a problem
workaround.
Explanation
DUI3933I THE CONFIG VIEW COMMAND IS
A message describing an application error has been
written to the Graphic Monitor Facility host subsystem NO LONGER REQUIRED. THE
(GMFHS) audit log. This message can represent RODM LOADER WILL BE RUN IF
multiple log entries because it is issued a maximum of LOAD=YES IS SPECIFIED
every 30 seconds.
Explanation
Message Variables
The CONFIG VIEW command is no longer required
task when changes are made to Resource Object Data
The name of the GMFHS task that logged the Manager (RODM). The RODM loader or user-written
message. methods or applications can be used to add, delete, or
change views directly. If LOAD=YES is specified, the
RODM loader is started as specified.

The RODM loader is started if LOAD=YES is specified. Modify DUIGINIT to remove the RODMPASS
parameter for future invocations of GMFHS.
Operator response DUI3936E GMFHS IS NOT AUTHORIZED TO
Run the RODM loader directly instead of using the CONNECT TO RODM.
CONFIG command. If the CONFIG command was
invoked by a command list, contact the system Explanation
programmer.
The security system did not allow GMFHS to obtain a
connection with RODM.
If the CONFIG VIEW command is in a command list, System action
remove it or replace it with a command to invoke the
GMFHS ends because of a critical error.
RODM loader directly.
DUI3934I THE MSG OPTION OF THE CONFIG System programmer response
COMMAND IS NO LONGER
SUPPORTED AND IS IGNORED Verify that the RODMID parameter in the DUIGINIT file
has the correct value. Also verify that the security
system is set up to authorize the RODM ID value to
Explanation
connect to RODM.
The MSG option is no longer supported on the CONFIG
DOMAIN or the CONFIG VIEW command. This option DUI3937E GMFHS HAS DETECTED THAT ITS
has been ignored. RODM USERID HAS BEEN
DISCONNECTED FROM RODM BY
ANOTHER RODM USER
System action
The MSG option is ignored. Explanation
Another user of the Resource Object Data Manager
Operator response (RODM) gained access to RODM using the same RODM
Do not specify the MSG option on the CONFIG user ID and password or password phrase as the
command. Users monitoring views will be notified, Graphic Monitor Facility host subsystem (GMFHS) and
automatically, if any of the views they are monitoring has now disconnected from RODM. As a result, GMFHS
change. If the CONFIG command was invoked by a has lost its connection to RODM.
command list, contact the system programmer.
System action
System programmer response GMFHS ends because of a critical error.
If the CONFIG DOMAIN or the CONFIG VIEW
command was in a command list, remove the usage of Operator response
the MSG option.
DUI3935E THE RODMPASS PARAMETER IS
NO LONGER SUPPORTED. THE System programmer response
PARAMETER IS IGNORED
Determine what other user of RODM is using the same
user ID and password or password phrase as GMFHS.
Explanation
Either change the GMFHS user ID and password or
The RODMPASS parameter specified in DUIGINIT file password phrase or change the other RODM user's
is no longer needed. user ID and password or password phrase. Then,
restart GMFHS. Ensure that all RODM users have
System action different RODM user IDs and passwords or password
phrases.
DUI3965I GMFHS COMPLETED LINK OF
DOMAIN: domainid TO NMG:
nmgid

GMFHS processing of a dynamic link between a The user specified the GTF value for PRINT on the
network management gateway (NMG) and domain has TRACE command or for PRINTPDU38 in DUIGINIT, but
completed. GTF is not active.
Message Variables
System action
domainid
Specifies the domain to which the NMG is linked. Output will not be stored in a GTF trace data set.
Output data will continue to be stored in the in-storage
nmgid trace facility or in GMFHS job data sets, if requested.
Specifies the NMG to which the domain is linked.
Operator response
System action
Start GTF or set GTF tracing off.
GMFHS begins normal processing of the domain and
NMG. DUI3986I RECORDING TO GTF FAILED WITH
RETURN CODE retcode
DUI3981I GMFHS RESOURCE STATUS WARM
START IS IN EFFECT
Explanation
Explanation The user was writing output to GTF, but GTF has
stopped.
You started GMFHS with keyword RESWS=YES. This
will force GMFHS to bypass setting initial status for Message Variables
domains in RODM if the information in RODM for that retcode
domain indicates the status in RODM is accurate. Specifies the return code from the MVS GTRACE
Without this keyword GMFHS will solicit the status of MACRO.
every resource again.
System action
System action
Trace data after the stop is not recorded to GTF.
GMFHS processing continues. Output data will continue to be stored in the in-storage
DUI3982I GMFHS IS STARTING trace facility or in GMFHS job data sets, if requested.
SOLICITATION FOR NMG nmgid
DOMAIN domainid Operator response
Restart GTF or set GTF tracing off.
Explanation
The Graphic Monitor Facility host subsystem (GMFHS) System programmer response
starts status solicitation for resources in domain
If the return code is not 4 (GTF not active) or 24 (GTF
domainid for the network management gateway
buffers are full), consult the MVS library for the
(NMG) nmgid.
GTRACE assembler macro return code responses. If
Message Variables the problem persists, contact IBM Software Support.
nmgid DUI3987I RECORDING TO GTF HAS
Specifies the name of the NMG associated with RESUMED
this domain.
domainid Explanation
Specifies the name of the domain. It is the
MyName field value of a System Network The user received message DUI3986I and has
Architecture (SNA) domain object, or the restarted GTF.
EMDomain value of a non-SNA domain object.
System action
System action Job output from GMFHS to the GTF trace data
GMFHS processing continues. setresumes.
DUI3990E LOAD FAILED FOR MODULE
DUI3985I GTF IS SPECIFIED FOR OUTPUT,
modname
BUT GTF IS NOT ACTIVE

Explanation rescode
Specifies the IXCARM macro reason code.
GMFHS was unable to load the identified module.
modname GMFHS processing continues.
The name of the module GMFHS was trying to
load.
System action Contact IBM Software Support.
Dependent upon which module GMFHS was trying to DUI3993E ARM DEREGISTRATION FAILED
load. WITH RETURN CODE retcode,
REASON CODE rescode
Operator response
Explanation
Dependent upon the action GMFHS takes following the
load failure. Notify the system programmer. During termination processing, GMFHS attempted to
deregister from automatic restart manager (ARM) and
was unsuccessful.
Message Variables
Ensure that required modules are available to GMFHS.
retcode
DUI3991I ARM REGISTRATION FAILED
Specifies the IXCARM macro return code.
WITH RETURN CODE retcode,
REASON CODE rescode rescode
Specifies the IXCARM macro reason code.
Explanation
System action
GMFHS attempted to register with automatic restart
manager (ARM) and was unsuccessful. GMFHS termination continues.
Message Variables
retcode
rescode DUI3994E UNRECOGNIZED JCL EXEC
Specifies the IXCARM macro reason code. STATEMENT PARAMETER
GMFHS processing continues. GMFHS cannot recognize a parameter found in the JCL
EXEC parameter string.
System action
If no ARM policy was active and restart capability is
desired, activate an ARM policy and restart GMFHS. GMFHS ends.
Otherwise, contact IBM Software Support.
DUI3992E ARM READY FAILED WITH
RETURN CODE retcode, REASON Correct the JCL EXEC parameter string and restart
CODE rescode GMFHS.
DUI3995E JCL EXEC STATEMENT
Explanation PARAMETER parmname IS NOT
GMFHS was unsuccessful in notifying automatic VALID OR IS DUPLICATED
restart manager (ARM) that it was ready.
Explanation
Message Variables
The value of a GMFHS JCL EXEC statement parameter
retcode
was not valid or the JCL EXEC statement keyword was
duplicated.

parmname domainid
Specifies the incorrect parameter. Specifies the domain ID to which this GMFHS is
attempting to connect.
System action
System action
GMFHS ends.
The most recently started Graphic Monitor Facility host
System programmer response subsystem ends.
Correct the error and restart GMFHS. DUI4000E NETVIEW SUBSYSTEM NOT
AVAILABLE FOR PPI REQUEST
DUI3996I GMFHS COMMUNICATION
STARTED WITH WORKSTATION
Explanation
workstation FOR DOMAIN =
domainid An attempt to use the program-to-program interface
(PPI) of the NetView subsystem failed because the
Explanation NetView subsystem is inactive.
A session between GMFHS and the designated

System action
workstation has been established.
The Graphic Monitor Facility host subsystem
Message Variables
periodically attempts to use the program-to-program
workstation interface.
Either the LU name or IP address of the
workstation. If this is an LU name, the name begins Operator response
with LU. If this is in an IP address, it is in the form
IPname:port (IPaddress:port). Notify the system programmer.
domainid
Specifies the domain ID to which this GMFHS is System programmer response
connected or attempting to connect. Determine why the NetView subsystem is inactive.
DUI3997I GMFHS COMMUNICATION Correct the error and activate the NetView subsystem.
STOPPED WITH WORKSTATION DUI4001E ALERT TRANSLATION TABLE table
workstation FOR DOMAIN = NOT FOUND
domainid
Explanation
Explanation
The Graphic Monitor Facility host subsystem (GMFHS)
A session between GMFHS and the designated expected to find two alert translation tables in the
workstation has ended. STEPLIB data set. These tables are load modules
Message Variables named DUIFEIBM and DUIFEUSR. The table was not
found.
workstation
Either the LU name or IP address of the Message Variables
workstation. If this is an LU name, the name will table
begin with LU. If this is in an IP address, it will be Specifies the name of the load module that was
in the form IPname:port (IPaddress:port). not found.
domainid
Specifies the domain ID to which this GMFHS is System action
connected or attempting to connect.
If this message appears twice (once for each table),
DUI3999I GMFHS IS ALREADY ACTIVE FOR GMFHS is unable to interpret the status contained in
DOMAIN = domainid alerts and resolutions and is unable to monitor the
status of non-SNA resources contained in NetView
Explanation Graphic Monitor Facility views. If the message appears
only once, GMFHS uses the status-translation
You attempted to start the Graphic Monitor Facility information contained in the table that it found to
host subsystem while it was already active.

provide status monitoring for non-SNA resources the IBM Z NetView Resource Object Data Manager and
contained in NetView Graphic Monitor Facility views. GMFHS Programmer's Guide for more information.
DUI4003I GMFHS NETWORK
Operator response CONFIGURATION INITIALIZED
Notify the system programmer. SUCCESSFULLY
System programmer response Explanation
Verify that both DUIFEIBM and DUIFEUSR are in the The network configuration definition used by the
STEPLIB data set concatenation. Graphic Monitor Facility host subsystem (GMFHS) has
initialized successfully. No errors occurred during this
DUI4002E ALERT PROCESSOR processor NOT initialization.
FOUND, ALERTS GENERATED:
number
System action
Explanation GMFHS begins to establish communication sessions

with server workstations or client workstations and to
An alert processor load module used by the Graphic query the current display status of non-SNA real
Monitor Facility host subsystem (GMFHS) was not resources.
found. GMFHS uses this module to determine the
name of a Resource Object Data Manager (RODM) DUI4004E GMFHS CONFIGURATION
object to which to apply the status information INITIALIZATION COMPLETED BUT
contained in an alert. ERRORS WERE LOGGED -
CONFIGURATION START:
Message Variables starttime END: endtime
processor
Specifies the name of the alert processor load Explanation
module that is to supply the name of a RODM
object to GMFHS. The configuration definition used by the Graphic
Monitor Facility host subsystem (GMFHS) has been
number initialized successfully, but errors were found in
Specifies the number of alerts that have not been objects in the Resource Object Data Manager (RODM).
processed between the last and current
appearances of this message. The minimum Message Variables
interval for this message is 30 seconds. starttime
The time that the configuration initialization
System action started, in the format hhmmss, where hh is the
hour (00–23), mm is the minutes (00–59), and ss
GMFHS cannot identify any objects in RODM that
is the seconds (00–59).
represent non-SNA resources. This occurs because an
element manager, whose non-SNA domain object in endtime
RODM is defined by the processor as its AlertProc The time that the configuration initialization ended,
attribute, reports on those resources. As a result, in the format hhmmss, where hh is the hour (00–
GMFHS cannot report status information for any of 23), mm is the minutes (00–59), and ss is the
these resources. seconds (00–59).


Review the RODM object definitions supplied by your Notify the system programmer.
installation for objects in the non-SNA domain class.
Review the STEPLIB data set concatenation in the System programmer response
GMFHS job control language (JCL). Ensure that all
user-supplied alert processor load modules that are See the output log entries between and including the
named in the non-SNA domain definitions are also configuration initialization start and end times in the
present in the STEPLIB data set concatenation. See message; the default output log is the internal trace
log (CNMT DD). In RODM, correct the objects that

contain errors. See message DUI3905I and the IBM Z System programmer response
NetView Data Model Reference for more information.
See message DUI3905I. See the output log entries
You might need to issue a GMFHS CONFIG command
between and including the configuration initialization
to make the changes effective.
start and end times in the message and contact IBM
DUI4005A GMFHS CONFIGURATION Software Support; the default output log is the internal
INITIALIZATION FAILED, RETURN trace log (CNMT DD).
CODE = retcode - CONFIGURATION
DUI4006E THE COMMAND command1
START: starttime END: endtime
REQUEST IN PROGRESS, NEW
command2 REQUEST IGNORED
Explanation
The initialization of the configuration definition used by Explanation
the Graphic Monitor Facility host subsystem (GMFHS)
A command request was in process when you entered
has failed for the reason identified in the message.
another command. This message is displayed in
Message Variables response to a Graphic Monitor Facility host subsystem
(GMFHS) CONFIG NETWORK command for one of the
retcode
following reasons:
Specifies the return code indicating the reason that
the initialization of the configuration failed. The • A previously issued CONFIG NETWORK command is
return code is one of the following: still being processed.
1. There was a Resource Object Data Manager • The RODM session is not available.
(RODM) internal error. Message Variables
2. GMFHS lost its connection with RODM.
command1
3. There was a class or field definition error with Specifies the name of the command in process.
RODM.
command2
4. There was a GMFHS internal error. Specifies the name of the command you entered
starttime that was ignored.
Specifies the time that the configuration
initialization started, provided in the format System action
hhmmss, where hh is the hour (00–23), mm is the The command you entered is ignored.
endtime Operator response
initialization failed, provided in the format You can reenter command2 after the first command is
hhmmss, where hh is the hour (00–23), mm is the completed. The system issues a message to indicate
minutes (00–59), and ss is the seconds (00–59). when processing of the first command ends. To
determine whether the RODM session is available,
enter a CONFIG VIEW or a CONFIG DOMAIN
System action
command. Message DUI4092 is issued in response to
If the reason the initialization of the configuration these commands if the RODM session is not available.
failed is because of a RODM internal error (return code
1), a class or field definition error (return code 3), or a DUI4007A GMFHS TERMINATING DUE TO
GMFHS internal error (return code 4), the GMFHS job CRITICAL ERROR FOR DOMAIN =
ends. If the reason is that GMFHS lost its connection domainid
with RODM (return code 2), it is possible that the
RODM to which GMFHS was connected ended. GMFHS Explanation
waits for its RODM connection to be reestablished and
restarts the configuration initialization.
is ending because a critical error has been
encountered. The error that caused GMFHS to end is
Operator response displayed in a preceding message.
If RODM ended, try to restart the initialization. If it Message Variables
does not restart, notify the system programmer.
domainid
Specifies the domain ID to which this GMFHS is
connected or attempting to connect.

GMFHS ends. Correct and reenter the CONFIG command. For more
information about the CONFIG command, see the
Operator response NetView online help.
Notify the system programmer. DUI4010E objecttype objectid NOT FOUND,

command COMMAND REJECTED
Explanation
Restart GMFHS after correcting the error indicated in
the preceding message. You entered a command containing a domain or
network management gateway (NMG) identifier that is
DUI4008E INITIALIZATION PARAMETER not defined to the Graphic Monitor Facility host
parameter IS NOT VALID, OR IS subsystem (GMFHS).
DUPLICATED
Message Variables
Explanation objecttype
Specifies the type of the object that was not found,
The Graphic Monitor Facility host subsystem
either NMG or DOMAIN.
encountered a parameter in the initialization file that it
did not recognize or found to be duplicated. objectid
Specifies the identifier of the undefined object.
Message Variables
command
parameter Specifies the name of the command that was
Specifies the parameter encountered in the rejected.
initialization file that was not recognized or was
duplicated. System action
System action The command is rejected.
The parameter is ignored. Operator response
Operator response Determine whether the identifier has been defined or

was entered incorrectly. If the name was entered
Notify the system programmer. incorrectly, reenter the command with the valid
names. If you entered the domain name or NMG
System programmer response identifier correctly, notify the system programmer.
Correct or remove the displayed parameter in the
DUIGINIT member. See the IBM Z NetView System programmer response
Administration Reference for more information. Ensure that each domain or NMG is defined in the
Resource Object Data Manager and that its EMDomain
DUI4009E A TYPE OF NETWORK, DOMAIN
(for non-SNA domains) or MyName (for SNA domains
OR VIEW MUST BE SPECIFIED
and NMGs) attribute value is the name entered in the
WITH THE CONFIG COMMAND
command. If the attribute has been defined in the
database since the GMFHS host job was started, enter
Explanation a CONFIG NETWORK command to make the domain or
An incorrect parameter for the CONFIG command was NMG known to GMFHS.
issued or no parameter was specified. You must DUI4011E GMFHS ATTEMPTED TO SEND A
specify a CONFIG type of either NETWORK, DOMAIN,
MESSAGE TO SCOPE CHECKER
or VIEW.
OPTIONAL TASK BUT FAILED

The CONFIG command is rejected. The Graphic Monitor Facility host subsystem (GMFHS)
attempted to send a message to the scope checker
optional task (DUIFSSCO) using the NetView program-
to-program interface, but cannot because DUIFSSCO

was not an active program-to-program interface DUI4013I TASK = task STATUS = WAIT
receiver. QUEUE DEPTH = qcount

GMFHS is unable to complete the process that This message is part of a multiline response generated
required the services of DUIFSSCO. Other GMFHS by the TASK command you issued using the MVS
functions requiring DUIFSSCO cannot complete MODIFY command or the GMFHS command list. This
normally as long as DUIFSSCO is not an active message is for each Graphic Monitor Facility host
program-to-program interface receiver. For example, subsystem (GMFHS) subtask with a status of WAIT,
the alert logging and alert retrieval functions require meaning that the subtask will wait until you enter a
DUIFSSCO, so GMFHS cannot log or retrieve alerts command or the timer expires.
when it cannot communicate with DUIFSSCO.
Message Variables
Operator response task

Identifies a GMFHS subtask. One report line is
Notify the system programmer. issued for each task. The subtask can be one of the
following:
DBSERVER
Verify that DUIFSSCO is inactive, and then start it. If Dbserver subtask.
DUIFSSCO is active and the problem persists, review EVENTMGR
the network log to determine the cause of the Event manager subtask.
problem.
IPC
DUI4012E NO objecttypeS ARE DEFINED Interprocess communications subtask.
NETCMD
Explanation Network commands subtask.
You issued a SHOW NMG command, but no network NETCON
management gateways (NMGs) are defined in the Network configuration subtask.
Resource Object Data Manager (RODM). Or you issued OPERIF
a SHOW DOMAIN command and no Systems Network Operator interface subtask.
Architecture (SNA) or non-SNA domains are defined in
RODM. RTMGR
Resource traits manager subtask.
Message Variables
IRMGR
objecttype IPC-RODM manager subtask.
Either NMG or DOMAIN, depending on what was VIEWMGR
specified in the associated GMFHS SHOW View manager subtask.
command.
VSTATMGR
View status manager subtask.
System action
qcount
Processing of the SHOW command ends. Specifies the number of messages waiting in the
queue to be delivered to the subtask.
Operator response
DUI4014I CONFIG COMMAND ERROR: THE
Ensure that the network definition has been loaded in INDD PARAMETER WAS CODED
RODM. If not, it must be loaded before any NMGs or WITH LOAD=NO
domains are recognized by GMFHS. If the network
definition has been loaded in RODM, notify the system Explanation
programmer.
You entered a CONFIG command using LOAD=NO,
System programmer response which is not valid with the INDD parameter.
Verify that the NMG, SNA domain, and non-SNA System action
domain definitions are included in the network
definition loaded in RODM. The CONFIG command is rejected.

If LOAD=NO is correct, delete the INDD parameter and See the output log entries between and including the
retry the command. If LOAD=YES was intended, code start and end times in the message ; the default output
this with the INDD parameter and retry the command. log is the internal trace log (CNMT DD). IF LOAD=YES
See the NetView online help for more information was specified in the CONFIG command, check the
about the correct parameter values for the CONFIG messages issued to the EKGPRINT data set by the
command. RODM loader.
DUI4016I CONFIG COMMAND PROCESSING DUI4018A command COMMAND
INITIATED PROCESSING FAILED -REASON =
reason - START: starttime END:
Explanation endtime
The CONFIG command has been successfully initiated.

Explanation
Any informational or error messages that occur while
the CONFIG command is completing are issued to the A command has failed for the reason identified in the
system console. message.
Message Variables
System action
command
Processing continues. Specifies the name of the failing command.
DUI4017E command COMMAND reason
PROCESSING COMPLETED WITH Specifies the reason that the CONFIG command
ERRORS - START: starttime END: processing failed is one of the following:
endtime PROGLOAD
An error occurred while attempting to load the
Explanation Resource Object Data Manager (RODM) load utility
from the program library (STEPLIB) used by the
A CONFIG NETWORK, CONFIG DOMAIN, or CONFIG
Graphic Monitor Facility host subsystem (GMFHS).
VIEW command has completed. Errors were found
when applying changes to the Resource Object Data INTERNAL
Manager (RODM) database (if the INDD parameter was An internal processing error occurred during
included in the command) or in the resulting CONFIG command processing.
configuration definition in the RODM database. LOAD-RC
Message Variables Specifies the RODM load utility return code was
greater than 4.
command
RODMERR
Specifies the name of the command for which
Unrecoverable errors were encountered in
processing has completed.
requesting service from RODM.
starttime
starttime
Specifies the time that the configuration command
processing started, in the format hhmmss, where
initialization started, in the format hhmmss, where
hh is the hour (00-23), mm is the minutes (00-59),
and ss is the seconds (00-59).
endtime
endtime
Specifies the time that the configuration command
processing ended, in the format hhmmss, where
initialization ended, in the format hhmmss, where
hh is the (00-23), mm is the minutes (00-59), and
ss is the seconds (00-59).
System action
System action
Diagnostic information is written to the GMFHS output
log, and processing of the CONFIG command ends.
Operator response

Operator response endtime
Specifies the time of the failure in the format
hhmmss, where hh is the hour (00–23), mm is the
retcode
If the reason in the message is PROGLOAD, the RODM Specifies the return code from the transaction
load utility program, EKGLOTLM, cannot be loaded. information block for the method.
Verify that this load module is in a library that is reason
available to the GMFHS job and that there is sufficient Specifies the reason code from the transaction
virtual storage for GMFHS. If the reason in the information block for the method.
message is LOAD-RC, check the output in the
EKGPRINT data set for messages issued by the RODM transactionid
load utility describing the problem. If the reason is Specifies the transaction identifier for the
INTERNAL or RODMERR, see the system error particular invocation of the failed method.
synopsis entries from the GMFHS output log; the
default output log is the internal trace log (CNMT DD). System action
See the output log when you contact IBM Software
One or more RODM log entries are issued to report the
Support.
failure and to provide diagnostic information. If the
DUI4019I NETWORK CONFIGURATION reason code is 45081, the method completed
DEFINITION WILL BE processing, but the log entries written identify an
REINITIALIZED object and field that contains an incorrect value for
which a default value was used. For all other reason
Explanation codes, the method ends when the error is detected.
A Resource Object Data Manager (RODM) Operator response

disconnection or the CONFIG NETWORK command
has made it necessary for the system to reinitialize the Notify the system programmer.
network configuration definition used by the Graphic
Monitor Facility host subsystem (GMFHS). System programmer response
Print the RODM log entries associated with the failure.
System action The return and reason codes in the message along
All sessions between GMFHS and graphic data servers with the information in the log entries can help you
are ended. GMFHS services are unavailable to determine the action to be taken to correct the
workstation users. The displayed status of all non-SNA problem. See the IBM Z NetView Resource Object Data
resources in open views become Unknown. GMFHS Manager and GMFHS Programmer's Guide for an
stops and restarts all of its subtasks. When the RODM explanation of the return and reason codes in the
connection is reestablished, the network configuration message and log entries.
definition is reinitialized. Then sessions with graphic
DUI4021I value IS REPEATED IN THE
data servers are reestablished and GMFHS services
parameter PARAMETER OF THE
become available.
command COMMAND
DUI4020A METHOD method FAILED AT
endtime, RETURN CODE = retcode Explanation
REASON CODE = reason
TRANSACTION = transactionid A name (for example, the name of a domain) is
duplicated in the value list provided for the parameter.
A Resource Object Data Manager (RODM) method has value
failed. Depending upon the reason for the failure, the Specifies the name that is repeated in the
DisplayStatus or other field of one or more objects in parameter value list.
the RODM data cache might now have an incorrect or parameter
inconsistent value. Specifies the name of the keyword parameter for
Message Variables which the list was specified.
method
Specifies the name of the method that has failed.

command System programmer response
Specifies the name of the command containing the
Correct the keyword parameter on the CHECKPOINT
error.
statement in member DUIGINIT. See the IBM Z
NetView Administration Reference for more
Operator response information.
Enter the command again without the repeated value. DUI4023E STATUS SOLICITATION FOR
DUI4022A GMFHS INITIALIZATION DOMAIN domainid FAILED.
CHECKPOINT PARAMETER SOLICITATION START: starttime
keyword IS INVALID OR END: endtime
CONFLICTS
Explanation
Explanation An attempt to obtain the current display status of the
You supplied a keyword parameter on the real resources for the indicated domain was not
CHECKPOINT statement of the Graphic Monitor successful.
Facility host subsystem (GMFHS) initialization member Message Variables
DUIGINIT. The keyword supplied is either not valid or
in conflict with other keywords supplied for this domainid
statement. Specifies the identifier of the non-SNA domain for
which the status was being queried.
Message Variables
starttime
keyword Specifies the start time of the status solicitation in
Specifies the keyword parameter you supplied on the format hhmmss, where hh is the hour (00–23),
the CHECKPOINT statement in DUIGINIT. Valid mm is the minutes (00–59), and ss is the seconds
keywords for CHECKPOINT are: (00–59).
STARTUP endtime
A checkpoint is taken at GMFHS startup time. Specifies the end time of the status solicitation in
TERM the format hhmmss, where hh is the hour (00–23),
A checkpoint is taken when GMFHS ends. mm is the minutes (00–59), and ss is the seconds
(00–59).
CONFIG
A checkpoint is taken after GMFHS processes a
CONFIG command. System action
NONE Status solicitation for the domain ends. The status of

No checkpoints are taken. This keyword is the domain is set to SOL-FAIL.
mutually exclusive with any others.
ALL Operator response
All checkpoints are taken at the following If this message is accompanied by other messages
occurrences: indicating that a network management
• At GMFHS startup time communications gateway has failed (program-to-
program interface or COS transport errors) and can be
• When GMFHS ends restored, restore the gateway. Otherwise, notify the
• After GMFHS processes a CONFIG command. system programmer.
This keyword is mutually exclusive with any
others. System programmer response
Check the system operator's console log for messages
System action that indicate why the status solicitation failed. The
GMFHS is initialized with a checkpoint default of
output log also contains one or more error synopsis
NONE.
entries that explain the reason for the failure.
Operator response DUI4024A GMFHS TASK taskid LOGGED AN

INTERNAL ERROR AT errortime
FOR DOMAIN = domainid

A logic error occurred in the Graphic Monitor Facility Graphic Monitor Facility host subsystem (GMFHS)
host subsystem (GMFHS). An error synopsis that processing continues.
provides more information is written to the GMFHS
output log. Operator response
taskid
Specifies the identifier of the GMFHS task that System programmer response
detected and logged the error.
Use the return and reason codes in the message to
errortime find the error and correct the problem. See the IBM Z
Specifies the time when the error occurred, in the NetView Administration Reference for more
format hhmmss, where hh is the hour (00–23), information.
mm is the minutes (00–59), and ss is the seconds
(00–59). DUI4026A RODM CONNECTION LOST AT
losstime
domainid
connected. Explanation
System action network configuration manager subtask is notified that
the connection between GMFHS and Resource Object
The specific process involved ends, and processing Data Manager (RODM) has ended.
continues.
Message Variables
Operator response losstime
Notify the system programmer. Specifies the time when network configuration
manager receives the notification that the RODM
connection has ended. This is provided in the
System programmer response format hhmmss, where hh is the hour (00–23),
Use the time provided in the message to determine mm is the minutes (00–59), and ss is the seconds
which entries in the GMFHS output log might see the (00–59).
error. If you contact IBM Software Support for
assistance, see the error synopsis messages available. System action
DUI4025A RODM CHECKPOINT FAILED AT The network configuration manager asks the GMFHS
failtime RETURN CODE = retcode main task to reinitialize GMFHS to prepare for when
REASON CODE = reason the connection to RODM is established again. While
the host is reinitializing, all graphic data server
Explanation sessions end. All non-SNA resources in open views at
the GMFHS workstations are displayed as Unknown.
The Resource Object Data Manager (RODM) rejected a GMFHS finishes initializing and starts all of its subtasks
request to checkpoint the RODM database. again. When the RODM connection is reestablished,
Message Variables GMFHS initializes the network configuration definition.
When this is done, the graphic data server sessions are
failtime established again and the GMFHS services are
Specifies the time when the error occurred, in the available.
format hhmmss, where hh is the hour (00–23),
mm is the minutes (00–59), and ss is the seconds
Operator response
(00–59).
retcode If RODM ends in error, start RODM again.
Specifies the return code from the RODM DUI4027I GMFHS MAIN TASK
checkpoint request. INITIALIZATION IS COMPLETE
reason FOR DOMAIN = domainid
Specifies the reason code from the RODM
checkpoint request.

The initialization process for the Graphic Monitor Correct the format of the GMTOFFSET parameter in
Facility host subsystem (GMFHS) main task is DUIGINIT and restart GMFHS. See the IBM Z NetView
complete. Administration Reference for more information.
Message Variables DUI4030E parameter MISSING FROM GMFHS
INITIALIZATION PARAMETERS
domainid
attempting to connect. Explanation
The Resource Object Data Manager (RODM)
System action application name statement (RODMNAME) is missing
from the DSIPARM member containing GMFHS
GMFHS processing continues.
initialization values.
DUI4028E INITIALIZATION MEMBER
Message Variables
DUIGINIT WAS NOT FOUND IN
THE CNMPARM DATASET parameter
Specifies the missing parameter.
Explanation
System action
DUIGINIT, which is part of the Graphic Monitor Facility
host subsystem (GMFHS) main task initialization, GMFHS ends.
cannot be found in the CNMPARM data set.
Operator response
GMFHS ends.
Operator response Change the RODMNAME parameter in DUIGINIT and
Notify the system programmer. restart GMFHS. See the IBM Z NetView Administration
System programmer response DUI4031I GMFHS IS TERMINATING OR IS IN
Change the CNMPARM DD statement to address the THE PROCESS OF TERMINATING
data set that contains DUIGINIT, or recreate DUE TO OPERATOR REQUEST FOR
DUIGINIT and restart GMFHS. See the IBM Z NetView DOMAIN = domainid
Administration Reference for more information.
Explanation
DUI4029E GMTOFFSET PARAMETER IS NOT
FORMATTED CORRECTLY The Graphic Monitor Facility host subsystem (GMFHS)
is terminating because of an operator request.
The GMTOFFSET statement in DUIGINIT s is not domainid
formatted correctly. It must be in the form of shhmm, Specifies the domain ID to which this GMFHS is
where s is a positive (+) or negative (N) sign, hh is the connected or attempting to connect. If this
hour (00–23), and mm is the minutes (00–59). message is issued as a result of a missing domain
(message DUI3904E), this value is set to MISSING.
System action
The Graphic Monitor Facility host subsystem (GMFHS) System action
ends. GMFHS ends.
DUI4033I RODM CONFIGURATION STATUS =
Operator response
PENDING

Explanation domtype
Specifies the type of domain, either SNA or non-
This message is displayed as part of the multiline
SNA.
response to your GMFHS STATUS command. PENDING
is the status in the Resource Object Data Manager domstate
(RODM) database during configuration initialization. Specifies the state of the domain. The domain
state indicates the last known state of the domain,
DUI4034E THE COMMAND command IS NOT as recognized by NETCON, through the completion
VALID. USE THE "HELP" of status solicitation.
COMMAND FOR A LIST OF THE
VALID COMMANDS If the network management gateway (NMG) for the
domain goes down, these states will not be reset
until the NMG comes back up.
Explanation
The domain states are:
You entered a command that is not valid.
Value
Message Variables
Meaning
command INITIAL
Specifies the command that you entered. Specifies the initial state prior to configuration
initialization.
Operator response PENDING
Use the HELP GMFHS command to obtain a list of valid Reconfiguration was requested but has not
Graphic Monitor Facility host subsystem commands started.
and enter the correct command. RECONFIGURING
DUI4035I NETWORK MANAGEMENT Waiting for a response to a RECONFIGURE
DOMAIN DISPLAY generic network control command.
RELEASING
Explanation Waiting for the release of the gateway
communication session.
This is the first line of the display generated in
LOADING
response to the SHOW DOMAIN command.
Waiting for the RODM load utility to run.
DUI4036I NAME = domainid TYPE = domtype SETTING
STATE = domstate CFGTM = Setting (as part of the reconfiguration) the
timestamp SESS = sessionstat DisplayStatus of the resources within the
NMG = nmgid domain to the InitialResourceStatus value for
the domain.
Explanation CHECKPOINTING
This is part of a multiline response generated by the Waiting for a checkpoint to be taken on the
SHOW DOMAIN command. There is one DUI4036I RODM data cache.
message for each domain delivered. WAITING
Message Variables Waiting for a gateway communication session
to be established.
domainid
SOLICITING
Specifies the name of the domain. It is the
Waiting for a response to a Display Status or
MyName field value of a Systems Network
Display Abnormal Status network control
Architecture (SNA) domain object, or the
command.
EMDomain value of a non-SNA domain object, or
an alias for EMDomain value that equal 'NODISP.'. RETRYING
Domain ID aliases are composed of seven numeric Waiting to retry the sending of a Display Status
characters followed by a period (.). To correlate or Display Abnormal Status network control
this alias to a unique object in the command.
Non_SNA_Domain_Class in RODM, the MyName FAILED
field of the object appears in succeeding message Solicitation of the current DisplayStatus of the
DUI3966I. non-SNA domain resources has failed.

ACTIVE Explanation
Solicitation of the current DisplayStatus of the
This is part of a multiline response generated by the
non-SNA domain resources has been
SHOW NMG command. There is one DUI4039I
completed.
message for each Graphic Monitor Facility host
COMPLETE subsystem (GMFHS) network management gateway
DisplayStatus solicitation does not apply to (NMG) object defined in the Resource Object Data
this domain, but initialization or reconfiguration Manager (RODM) data cache.
has been completed.
Message Variables
INVALID
Specifies the domain's state is not valid. There nmgname
is an internal processing error. Specifies the name of the NMG.
timestamp nmgstatus
Specifies the day and time of the initialization or Specifies the AgentStatus value of the NMG. This
last reconfiguration of this domain. The format of value is one of the following:
the time stamp is mm/dd/yy hhmm where mm is SATISFACTORY
the month (01-12), dd is the day (01-31), yy is the Satisfactory statu.
year (01-99), hh is the hour (00-23), and mm is the
UNSATISFACTORY
minutes (00-59).
Unsatisfactory status
sessionstat
UNKNOWN
Specifies the value YES, NO, or N/A, which
Unknown status
indicates whether a gateway communication
session is established for this domain. transport
Specifies the TransportProtocolName
nmgid
Specifies the name of the NMG associated with value
this domain. This field is not applicable for SNA This value is one of the following:
domains. COS
DUI4037I END Common operations services.
OST
Explanation Operator station task.
This is the last line of a multiline response generated PPI
by one of the following Graphic Monitor Facility host Program-to-program interface.
subsystem (GMFHS) commands: NONE
Protocol was not used.
• SHOW DOMAIN
• SHOW NMG winsize
Specifies the number of commands that the NMG
• STATUS can handle at once. It is the maximum number of
• TASK commands to which the system has not yet
• TRACE (without parameters) responded that can be present in the NMG at once.
cmdsout
DUI4038I NETWORK MANAGEMENT Specifies the number of network command
GATEWAY DISPLAY controls sent to and recognized by the NMG. A
response is expected but has not yet been
Explanation received for these commands.
This is part of a multiline response generated by the cmdssent
SHOW NMG command. Specifies the number of commands sent through
this NMG.
DUI4039I NMG = nmgname STATUS =
nmgstatus TRAN = transport DUI4040I STATUS DISPLAY
WINDOW = winsize OUT = cmdsout
SENT = cmdssent Explanation
response to the STATUS command you issued using

the MVS MODIFY command or the GMFHS command INVALID
list. The session status is not valid because of an
internal error.
DUI4041I RODM CONFIGURATION STATUS =
COMPLETE session
Identifies a session that GMFHS has with another
entity. This is a NetView task name for the
Explanation
sessions with the NetView CNMTAMEL data
This message is displayed as part of the multiline services task (DST) and the GMFHS scope checker
response to your GMFHS STATUS command. OPT within the NetView address space. If there is
COMPLETE is the status in the Resource Object Data a program-to-program interface network
Manager (RODM) database after network configuration management gateway receiver, the value is the
initialization. name of the gateway receiver.
DUI4042I TYPE = sesstype STATUS = ppistatus
sessionstat SESSION = session Specifies the program-to-program interface
PPIST = ppistatus transport status for applicable sessions. The
values are as follows:
Explanation INITIAL
Not activated (initial state)
This is part of a multiline response generated by the
STATUS command you issued using the MVS MODIFY QUERYING
command or the GMFHS command list. This message Query receiver
is displayed for each active session of type SCOPT, SENDING
CNMTAMEL, and PPI. Send data buffer
Message Variables OK
Message sent successfully
sesstype
Specifies the type of the session. The types are as TEMPORARY
follows: Temporary error
SCOPT PERMANENT
A session with the Graphic Monitor Facility host Permanent error
subsystem (GMFHS) scope checker optional INVALID
task (OPT). The value is not valid; an internal error
CNMTAMEL occurred.
A CNMTAMEL task session.
Operator response
PPI
A session with a program-to-program interface If the system has detected an internal error, notify the
(PPI) network management gateway. system programmer.
?????
Specifies the session type is not valid because System programmer response
of an internal error.
sessionstat
Specifies the session status. The values are as DUI4043I TYPE = sesstype STATUS =
follows: sessionstat SESSION = session
REGISTER
Specifies the CNMTAMEL session state—Register Explanation
request has been sent. This is part of a multiline response generated by the
ACTIVE STATUS command you issued using the MVS MODIFY
The session is active. command or the GMFHS command list. This message
is displayed for each active session of type RODM and
FAILED
GDS.
The session has failed.
N/A Message Variables
The session has not been established. sesstype
Indicates the type of the session. The types are as
follows:

RODM System programmer response
Specifies the connection to the Resource
Object Data Manager (RODM).
GDS DUI4044I GMFHS TASK DISPLAY
A session with a graphic data server.
????? Explanation
Specifies the session type is not valid because This is part of a multiline response generated by the
of an internal error. TASK command you issued using the MVS MODIFY
sessionstat command or the GMFHS command list.
Indicates the session status. The values are as DUI4045I TASK = task STATUS = ACTIVE
follows QUEUE DEPTH = qcount
CONNECTED
Specifies the connection to RODM or to the Explanation
graphic data server has been established.
This message is part of a multiline response generated
ADDED by the TASK command you issued using the MVS
RODM session state—Notification queue added MODIFY command or the GMFHS command list. This
COMPLETE message is for each Graphic Monitor Facility host
RODM session state—Notification queue subsystem (GMFHS) subtask with a status of ACTIVE,
establishment is complete meaning the subtask is processing a user command or
INSTALLED the timer is running.
RODM session state—Methods installed Message Variables
FOUND task
RODM session state—Methods found Identifies a GMFHS subtask. The subtask can be
ACTIVE one of the following:
Session is active DBSERVER
FAILED Dbserver subtask
Session has failed EVENTMGR
DOWN Event manager subtask
Session has not been established IPC
INVALID Interprocess communications subtask
Session status is not valid because of an NETCMD
internal error Network commands subtask
session NETCON
Identifies a session that Graphic Monitor Facility Network configuration subtask
host subsystem (GMFHS) has with another entity.
OPERIF
If the session has a session type of RODM, then Operator interface subtask
session is the name of the RODM for the
RTMGR
connection that GMFHS has or is attempting to
Resource traits manager subtask
make.
IRMGR
If the session has a session type of GDS, then IPC-RODM manager subtask
session is either the name of the LU associated
with the graphic data server, or the IP address and VIEWMGR
the port number in the format View manager subtask
ipaddress:portnumber (xxx.xx.xxx.xxx:xxxx). VSTATMGR
This IP identifier applies only to sessions with a View status manager subtask
type of GDS. One report line is issued for each task
qcount
Operator response
Specifies the number of messages waiting in the
If the system has detected an internal error, notify the queue to be delivered to the subtask.
system programmer.
DUI4046I AGGREGATION PROFILE
UPDATED AT: time

This message is issued to indicate that an operator has Processing continues.
updated either the aggregation parameters associated
DUI4051E TASK task NOT FOUND
with a resource type, or the aggregation parameters
associated with a real or aggregate object.
Explanation
Message Variables
You entered a TRACE command, and the requested
time task cannot be found.
Specifies the time of update.
Message Variables
System action task
Specifies the task that you tried to initialize.
DUI4048I OPERATOR HELP MENU Operator response
Verify the name of the task that you are trying to
Explanation
initialize and reenter the command. To display a list of
This is part of a multiline response generated by your all tasks, enter the TASK command.
HELP command.
DUI4052I RODM CONFIGURATION STATUS
IS NOT INITIALIZED
System action
The system displays a summary of the possible Explanation
response to your GMFHS STATUS command. NOT
Operator response INITIALIZED is the status in the Resource Object Data
See the NetView online help for more information Manager (RODM) database before network
about the listed commands. configuration initialization begins.
DUI4049I GMFHS DOMAIN CONFIGURATION

INITIALIZED SUCCESSFULLY
If you are running multiple copies of NetView or
Explanation GMFHS, ensure that the domain ID to which your
GMFHS is attempting to connect is active and is not
The domain configuration definition used by the already connected to another GMFHS.
Graphic Monitor Facility host subsystem (GMFHS) has
initialized successfully. No errors occurred during this DUI4053I CONFIG COMMAND ERROR: THE
initialization. DD NAME ddname WAS NOT
FOUND
System action
Explanation
GMFHS begins to establish communication sessions
with server workstations or client workstations and You entered a command using a parameter value that
query the current display status of non-SNA real is not valid for the specified parameter.
resources. Message Variables
DUI4050I GMFHS VIEW CONFIGURATION ddname
INITIALIZED SUCCESSFULLY Specifies the data definition name from the
CONFIG command INDD parameter.
Explanation
The view configuration definition used by the Graphic System action
Monitor Facility host subsystem (GMFHS) has The CONFIG command is rejected.
initialized successfully. No errors occurred during this
initialization.
Operator response
If the INDD parameter value you entered was
incorrect, correct the value and try the command

again. If the INDD parameter was correct, notify the Message Variables
system programmer.
keyword1
Specifies the first keyword option
keyword2
Determine why the data set called by the parameter Specifies the second keyword option
does not exist. See the NetView online help for more
keyword3
information about the correct parameter values for the Specifies the third keyword option
command. Correct and reenter the command.
DUI4054I INITIALIZATION PARAMETER Operator response
DISPLAY
Enter the TRACE command again using the correct
keywords. See the NetView online help for information
Explanation about the keywords of the TRACE command.
This is part of a multiline response generated by a DUI4060I CURRENT TRACE SETTINGS
LISTINIT command, which displays a list of the
Graphic Monitor Facility host subsystem initialization
parameters currently being used by GMFHS. Explanation
This is part of a multiline response generated by a
DUI4056I TRACE IS ALREADY ACTIVE
TRACE command you issued without parameters. This
message is followed by DUI4090I and DUI4091I.
Explanation
DUI4061I command COMMAND IS NOT
You entered a command to activate Graphic Monitor
FORMATTED CORRECTLY
Facility host subsystem tracing, but it was already
active.
Explanation
System action You entered a Graphic Monitor Facility host subsystem
command using an incorrect format. You might have
Processing continues. unmatched parentheses or an open quoted string.
DUI4057I TRACE HAS BEEN ACTIVATED Message Variables
command
Explanation
Specifies the command you entered.
Graphic Monitor Facility host subsystem tracing has
been activated by your command. Operator response
See the NetView online help for information about the
System action
correct format of the command. Correct and reenter
Processing continues. the command.
DUI4058I TRACE HAS BEEN DEACTIVATED DUI4062I parameter IS NOT VALID IN A
command COMMAND
Explanation
Explanation
Graphic Monitor Facility host subsystem tracing has
been inactivated by your command. You entered a command using an incorrect keyword
parameter.
Processing continues. parameter
DUI4059I TRACE COMMAND MUST INCLUDE Specifies the parameter keyword you entered.
keyword1, keyword2, or keyword3 command
KEYWORD Specifies the command you entered.
Explanation
You entered a TRACE command but did not include
one of the specified keywords.

Operator response value
Specifies the value you entered.
See or enter the HELP command for information about
the correct keyword parameters of the command. parameter
Correct and reenter the command. Specifies the parameter you entered.
command
DUI4063I value IS NOT VALID IN THE
parameter PARAMETER OF THE
command COMMAND
Operator response
Explanation See the NetView online help for information about the
correct parameter values for the command. Correct
You entered a command using a parameter value that
and reenter the command.
is not valid for the specified parameter.
Message Variables DUI4066I THE parameter PARAMETER IS
DUPLICATED IN THE command
value COMMAND
Specifies the incorrect value.
parameter Explanation
Specifies the parameter you entered.
You entered a command using a parameter that
command occurred more than once, but the parameter is valid
Specifies the command you entered. only once.
Message Variables
Operator response
parameter
Specifies the parameter you entered.
correct parameter values for the command. Correct
and reenter the command. command
DUI4064I A VALUE MUST BE SUPPLIED
WITH THE parameter PARAMETER
Operator response
OF THE command COMMAND
Explanation correct use of parameters in the command. Correct
and reenter the command.
You entered a command using a parameter that
required a value, but a value was not supplied. DUI4067I A DOMAIN OR NMG PARAMETER
IS REQUIRED IN THE SHOW
Message Variables COMMAND
parameter
Specifies the parameter you entered. Explanation
command You entered the SHOW command without the DOMAIN
Specifies the command you entered. or NMG keyword. One of these keywords is required.

See the NetView online help for information about the See the NetView online help for information about the
correct parameter values for the command. Correct correct use of the parameter in the command. Correct
and reenter the command. and reenter the command.
DUI4065I value IS UNEXPECTED IN THE DUI4068I command COMMAND PROCESSED
parameter PARAMETER OF THE FOR task
command COMMAND
Explanation
Explanation
You entered a Graphic Monitor Facility host subsystem
You entered a command using a parameter that did (GMFHS) command that has been processed for the
not require a value, but a value was supplied. specified GMFHS task. If command is GMFHS TRACE,
Message Variables this message was issued in response to a GMFHS

TRACE command that included a TASK parameter, and status focal point or is not active. Therefore, GMFHS
is issued for each task included in the parameter tasks cannot provide service to workstations.
value.
Message Variables
Message Variables
domainid
command Specifies the domain ID to which this GMFHS is
Specifies the name of the command that was attempting to connect
processed.
task System action
Specifies the ID for the GMFHS task for which the GMFHS is not able to send view or status data to the
command was processed. workstations.

The parameters are changed for the indicated task. Notify the system programmer.
DUI4069A RODM CLASS class NOT FOUND
Explanation Verify that the CNMTAMEL task is running and is
The Graphic Monitor Facility host subsystem (GMFHS) configured as a status focal point. See IBM Z NetView
specified that the Resource Object Data Manager Installation: Configuring Additional Components for
(RODM) is to provide notification of changes to objects information about this configuration. Also, if you are
in the specified class; however, this class is not valid. running multiple NetViews and GMFHSs, ensure that
the domain ID to which your GMFHS is attempting to
Message Variables connect is:
class • An active NetView domain
Specifies the name of the RODM class.
• Not already connected to another GMFHS
System action • Not a downlevel NetView domain
GMFHS continues to function but does not receive Check the log or issue the DISPPI command to see
notifications of changes to objects. Functions information about PPI senders and receivers.
dependent on notifications provided by the missing DUI4071E RODM METHOD method NOT
class will not work properly. FOUND

Notify the system programmer. The Graphic Monitor Facility host subsystem (GMFHS)
attempted to subscribe to notification of changes to
System programmer response Resource Object Data Manager (RODM) objects by a
Verify that the data model is loaded correctly. See notification method not known to RODM.
"Loading the GMFHS Data Model" in the IBM Z NetView Message Variables
Resource Object Data Manager and GMFHS
Programmer's Guide for more information. If the data method
model is loaded correctly, but the problem persists, Specifies the name of the RODM method by which
contact IBM Software Support. GMFHS expected to be notified of changes to
RODM objects.
DUI4070E GMFHS ATTEMPTED TO
ESTABLISH COMMUNICATIONS System action
WITH CNMTAMEL BUT FAILED
FOR DOMAIN = domainid GMFHS continues to function but does not receive
notifications of changes to objects. Functions
dependent on notifications provided by the missing
Explanation
method do not work properly. This message can be
The Graphic Monitor Facility host subsystem (GMFHS) issued more than once for the same RODM notification
tasks cannot communicate with the CNMTAMEL task method. This occurs if the same notification method is
because the CNMTAMEL task is not functioning as a used to report changes on more than one object and
this method is not found.

Operator response recvrid
Specifies the ID used by the sender to identify
itself in the program-to-program interface Receive
a Data Buffer request.
retcode
Verify that the data model is loaded correctly. See the Specifies the program-to-program interface return
IBM Z NetView Resource Object Data Manager and code that describes the failure.
GMFHS Programmer's Guide for more information. If
the data model is loaded correctly, but the problem System action
persists, contact IBM Software Support.
The data buffer is not received by the receiver.
DUI4072E PPI SEND FAILURE, SENDER ID =
sender, RECEIVER ID = recvrid,
Operator response
RETURN CODE = retcode
Explanation
Your attempt to send a data buffer to a program-to-
program interface (PPI) receiver failed. See the IBM Z NetView Application Programmer's
Guide for an explanation of the return code.
Message Variables
DUI4074E GMFHS INITIALIZATION
sender
Specifies the ID used by the sender to identify PARAMETER parameter_name
itself in the program-to-program interface Send a VALUE IS NOT VALID OR IS
Data Buffer to a Receiver request. OUTSIDE ALLOWED LIMITS
recvrid
Explanation
Specifies the ID used by the sender to identify the
receiver in the program-to-program interface Send You supplied an initialization parameter in the Graphic
a Data Buffer to a Receiver request. Monitor Facility host subsystem (GMFHS) DUIGINIT
retcode initialization member that was not valid.
Specifies the program-to-program interface return Message Variables
code that describes the failure.
parameter_name
The parameter name supplied in the DUIGINIT
System action
member of the CNMPARM data set.
The data buffer is not sent to the receiver.
System action
Operator response
GMFHS continues to function using the default value
Notify the system programmer. for the parameter.

See the IBM Z NetView Application Programmer's Notify the system programmer.
Guide for an explanation of the return code.
DUI4073E PPI RECEIVE FAILURE, RECEIVER
ID = recvrid, RETURN CODE = Supply the correct parameter value in the DUIGINIT
retcode member. See the IBM Z NetView Administration
Explanation DUI4075E parameter_name LIMITS ARE:
Your attempt to receive a data buffer from the LOWER LIMIT = lowlimit, UPPER
receiver's program-to-program interface (PPI) receiver LIMIT = highlimit
buffer queue failed.
A parameter value in the GMFHS DUIGINIT
initialization member is not valid. The value is outside

of the valid limits. This message is associated with TYPE
message DUI4074E. The list of interface or message types to trace for
APIs
Message Variables
STORAGE
parameter_name Sets storage trace on or off.
The parameter name supplied in the DUIGINIT
member of the CNMPARM data set. PRINTPDU38
Causes the system error synopsis records to be
lowlimit printed.
The valid lower limit for the parameter value.
highlimit System action
The valid upper limit for the parameter value.
The message is written to the console and processing
continues.
System action
GMFHS continues to function using the default value Operator response
for the parameter.
Operator response
Correct the TRACE parameter in the DUIGINIT
initialization member and recycle GMFHS. See the IBM
Z NetView Administration Reference for more
Correct the specification of the appropriate value in information.
the GMFHS initialization parameters. Restart GMFHS.
DUI4077A RODM CLASS class FIELD field
DUI4076E ERROR ENCOUNTERED IN THE NOT FOUND
INITIALIZATION ROUTINE FOR
TRACE PARAMETER traceparm Explanation
The specified field is not defined to the class in the
Explanation
Resource Object Data Manager (RODM). This field is
The Graphic Monitor Facility host subsystem critical to the operation of the VIEWMGR task, and its
initialization routines encountered an error in absence causes the Graphic Monitor Facility host
processing the TRACE parameters in the GMFHS subsystem (GMFHS) to end.
initialization member.
Message Variables
Message Variables
class
traceparm Name of the class under which the field must be
The trace parameter in error: defined.
TRACE field
Sets trace on or off. Name of the field that is missing.
TRACEPAGES
Number of pages allocated for the in-storage trace System action
table. GMFHS ends.
TRACEBYTES
Number of bytes per trace record written to the in- Operator response
storage trace table.
TASK
The list of tasks to trace.
LEVEL
The trace level. Ensure that RODM is properly loaded and that the field
exists. Then restart the GMFHS task.
API
The list of APIs to trace. DUI4078I SHOW NMG - DISPLAYS ALL
NMGS DEFINED IN RODM

This is one of the messages generated in response to This message is part of a multiline response generated
your HELP GMFHS command. This message describes by the TASK command you issued using the MVS
the Graphic Monitor Facility host subsystem (GMFHS) MODIFY command of the GMFHS command list. This
SHOW NMG command. message is for each Graphic Monitor Facility host
subsystem (GMFHS) subtask with a status of
System action STOPPED, meaning the subtask is inactive because an
abnormal end occurred.
GMFHS commands that you can enter. Message Variables
task
Operator response Identifies a GMFHS subtask. The subtask can be
one of the following:
See the NetView online help for more information
about the listed commands. DBSERVER
Dbserver subtask
DUI4079I SHOW DOMAIN - DISPLAYS ALL
DOMAINS DEFINED IN RODM EVENTMGR
Event manager subtask
Explanation IPC
Interprocess communications subtask
This is one of the messages generated in response to
NETCMD
your HELP GMFHS command. This message the
Network commands subtask
SHOW DOMAIN command. NETCON
Network configuration subtask
System action OPERIF
Operator interface subtask
GMFHS commands that you can enter. RTMGR
Resource traits manager subtask
Operator response IRMGR
IPC-RODM manager subtask
about the listed commands. VIEWMGR
View manager subtask
DUI4080I STATUS - DISPLAYS STATUS OF
VSTATMGR
GMFHS
View status manager subtask
Explanation One report line is issued for each task.

qcount
The number of messages waiting in the queue to
be delivered to the subtask.
STATUS command. DUI4082I TASK - DISPLAYS CURRENT TASK
INFORMATION
System action
Explanation
GMFHS commands that you can enter. This is one of the messages generated in response to
Operator response Graphic Monitor Facility host subsystem (GMFHS)
TASK command.
about the listed commands.
System action
DUI4081I TASK = task STATUS = STOPPED The system displays a summary of the possible
QUEUE DEPTH = qcount GMFHS commands that you can enter.

Operator response VIEWMGR
about the listed commands. VSTATMGR
View status manager subtask
DUI4083I HELP - DISPLAYS THE HELP MENU
One report line is issued for each task.
Explanation qcount
The number of messages waiting in the queue to
This is one of the messages generated in response to be delivered to the subtask.
Graphic Monitor Facility host subsystem (GMFHS) DUI4085I TERM – TERMINATES GMFHS
HELP command.
Explanation
System action This is one of the messages generated in response to
The system displays a summary of the possible your HELP GMFHS command. This message describes
GMFHS commands that you can enter. the Graphic Monitor Facility host subsystem (GMFHS)
TERM command.
Operator response
System action
about the listed commands. The system displays a summary of the possible
GMFHS commands that you can enter.
DUI4084I TASK = task STATUS = ENQUEUED
QUEUE DEPTH = qcount Operator response
Explanation See the NetView online help for more information

about the listed commands.
This message is part of a multiline response generated
by the TASK command you issued using the MVS DUI4086I LISTINIT – DISPLAYS THE
MODIFY command of the GMFHS command list. This INITIALIZATION PARMS
message is for each Graphic Monitor Facility host
subsystem (GMFHS) subtask with a status of Explanation
ENQUEUED, meaning the subtask is waiting for a
resource.
your HELP GMFHS command. This message describes
Message Variables the Graphic Monitor Facility host subsystem (GMFHS)
LISTINIT command.
task
Identifies a GMFHS subtask. The subtask can be
one of the following: System action
DBSERVER The system displays a summary of the possible

Dbserver subtask GMFHS commands that you can enter.
EVENTMGR
Event manager subtask Operator response
IPC See the NetView online help for more information
Interprocess communications subtask about the listed commands.
NETCMD DUI4087I CONFIG – SYNCHRONIZE GMFHS
Network commands subtask WITH RODM UPDATES
NETCON
Network configuration subtask Explanation
OPERIF This is one of the messages generated in response to
Operator interface subtask your HELP GMFHS command. This message describes
RTMGR the Graphic Monitor Facility host subsystem (GMFHS)
Resource traits manager subtask CONFIG command
IRMGR
IPC-RODM manager subtask

System action SNATM-TIMEOUT=lcon-value15
LCON-ALERT-CMD-
TIMEOUT=lcon-value16LCON-
GMFHS commands that you can enter.
MAX-QUEUE-IPC = lcon-value17
LCON-MAX-QUEUE-OPERIF = lcon-
Operator response value18 LCON-MAX-QUEUE-
See the NetView online help for more information DBSERVER = lcon-value19 LCON-
about the listed commands. MAX-QUEUE-NETCON = lcon-
value20 LCON-MAX-QUEUE-
DUI4088I ***** END OF MENU DISPLAY EVENTMGR = lcon-value21 LCON-
***** MAX-QUEUE-VIEWMGR = lcon-
value22 LCON-MAX-QUEUE-
Explanation VSTATMGR = lcon-value23 LCON-
MAX-QUEUE-NETCMD=lcon-
This is the last message generated in response to the value24 LCON-MAX-QUEUE-
HELP GMFHS command you issued. RTMGR=lcon-value25 LCON-MAX-
QUEUE-IRMGR = lcon-value26
System action LCON-MAX-QUEUE-RCMGR=lcon-
The system displays a summary of the possible value27 LCON-MAX-QUEUE-
Graphic Monitor Facility host subsystem (GMFHS) MAINTASK = lcon-value28
Explanation
Operator response This is one of the lines generated in response to a
See the NetView online help for more information LISTINIT command, which displays a list of the
about the listed commands. Graphic Monitor Facility host subsystem (GMFHS)
initialization parameters currently in use.
DUI4089I JAPANESE=off GMTOFFSET =
Message Variables
shhmm RODMNAME = rodmname
RODMID = rodmid DOMAIN = JAPANESE
domainid TRACE = traceind TASK = Specifies whether or not GMFHS uses Japanese
(taskidx, taskidx,...taskidx) LEVEL text for displayable text on the NMC console.
= tracelvl API = api TYPE = typeind
on
STORAGE = storageind
Specifies that GMFHS uses Japanese text for
PRINTPDU38 = yyy TRACEPAGES
displayable text on the NMC console.
= pages TRACEBYTES = bytes
CHECKPOINT = check-point LCON- off
NMG-POLL-INTERVAL = lcon- Specifies that GMFHS does not use Japanese
value1 LCON-NCC-RETRY-LIMIT = text for displayable text on the NMC console.
lcon-value2 LCON-NCC-RSC-LIMIT The default is off.
= lcon-value3 LCON-EVCHANGE- shhmm
BUFFER-INTERVAL=lcon-value4 The Coordinated Universal Time offset, which is
LCON-AIP-RESET- the number of hours and minutes the time differs
INTERVAL=lcon-value5 LCON- from Coordinated Universal Time, where s is a
AGG-BUNDLE-INTERVAL=lcon- positive (+) or negative (N) sign, hh is the hour
value6 LCON-STATUS-DELAY- (00-23), and mm is the minutes (00-59).
TIME = lcon-value7 LCON-STATUS-
rodmname
DELAY-MAX = lcon-value8 LCON-
REPORT-UNKNOWN-STATUS = The Resource Object Data Manager (RODM)
lcon-value9 LCON-HEX- jobname.
SUBVECTOR-DISPLAY = lcon- rodmid
value10 LCON-OPERATOR-CMD- The RODM user ID.
AUDIT = lcon-value11 LCON- domainid
ASSOCIATE-NULL-NODE-WITH- The 1 to 5 alphanumeric character domain to
LINK=lcon-value12 LCON- which this GMFHS is to be connected.
AGGRST-REQUIRED=lcon-value13
LCON-MAX-LOCATE-RESOURCE- traceind
VIEWS=lcon-value14 LCON- The TRACE ON or OFF indicator.

pages Explanation
The number of pages allocated for the in-storage
This is the second line displayed in response to a
trace table.
TRACE command you issued without parameters.
bytes
The number of bytes per trace record written to Message Variables
the in-storage trace table. globtracestat
taskidx Specifies either ON or OFF to indicate whether
The GMFHS tasks to be traced. tracing has been activated. This must be ON for
parameters to be effective.
tracelvl
The program tracing level. DUI4091I subtask tasktracestat LEVEL
api tracelevel PRINT printstatus API =
The API to trace: RODM, IPC, or NONE. (api1, api2, ..., apin ) STORAGE
storagetrace IPCAPI = (ipcapi1,
typeind ipcapi2, ..., ipcapin)
The type of trace entries included.
storageind Explanation
Indicates whether trace storage is requested:
possible values are YES or NO. This is part of a multiline response generated by a
TRACE command you issued without parameters. This
yyy message shows the status of tracing for each Graphic
Indicates which output log is being used by Monitor Facility host subsystem (GMFHS) task,
GMFHS to log PDU38 data. including the main task.
NO or INTERNAL
Message Variables
The PDUs are written to the internal trace log.
YES or FILE subtask
The PDUs are written to output data sets defined The subtask can be one of the following:
by DD statements for each GMFHS component. MAIN
GTF GMFHS main task
The PDUs are written to the GTF. RTMGR
checkpoint Resource traits manager subtask
The times when GMFHS requests a RODM IPC
checkpoint. Interprocess communications subtask
storeset OPERIF
Controls how event reports are logged to the event Operator interface subtask
report database in the CNMDB VSAM file. This
VIEWMGR
setting enables a trade off between DASD use and
CPU time. NONALERT causes Dbserver to store all
event reports that are not forwarded to the VSTATMGR
hardware monitor in the event report database. View status manager subtask
This is the default setting. ALL causes Dbserver to DBSERVER
store all event reports in the event report Database server subtask
database, even if they are forwarded to the
EVENTMGR
hardware monitor. NONE causes Dbserver not to
Event manager subtask
store event reports in the event report database.
However, some event reports are still forwarded to IRMGR
the hardware monitor and recorded in the IPC-RODM manager subtask
hardware monitor database. NETCMD
lcon-value Network commands subtask
See the IBM Z NetView Administration Reference NETCON
for information about lcon-value1 – lcon-value28. Network configuration subtask
DUI4090I TRACING IS globtracestat RCMGR
Resource Collection Manager subtask
One report line is issued for each task.

tasktracestat PPI
Specifies either one (1) to indicate tracing is Turns on tracing for the IPC subtask messages
enabled, or zero (0) to indicate that it is not. sent across the program-to-program
tracelevel interfaces.
A level from 0–99 at which trace has been GDS
activated for the task. Level 00 is the lowest level Turns on tracing for requests and responses
of detail and 99 is the highest. from the NMC and the NMC server.
printstatus CNMTAMEL
A letter that indicates whether trace entries are Turns on tracing for requests and responses
being written to the internal trace log (I), an output from the CNMTAMEL data services task (DST).
data set (F), or GTF (G). NOTIFY
storagetrace Turns on tracing for RODM notification blocks.
Specifies either 1 or zero (0) to indicate that all PDU
requests the task makes to allocate or free Turns on tracing for protocol data units
memory are to be traced. A zero indicates that exchanged between GMFHS subtasks.
they are not traced.
ALL
api1, api2, ..., apin Turns on tracing for all IPC messages.
Specifies the types of APIs to be traced. The
possible types are: DUI4092E GMFHS UNABLE TO
COMMUNICATE WITH RODM rodm
NONE
Turns off tracing for all APIs.
Explanation
RODM
Turns on tracing for user API requests to The Graphic Monitor Facility host subsystem (GMFHS)
RODM. attempted to connect with Resource Object Data
Manager (RODM) and failed. At least one RODM is
IPC
active, but RODM rodm was not found by GMFHS.
Turns on tracing for interprocess
communication messages. The types of Message Variables
messages are further classified with the
rodm
IPCAPI parameter.
Specifies the name of RODM that cannot be
PPI connected with GMFHS. This is the value of the
Turns on tracing for data sent to or received RODMNAME parameter supplied in DSIPARM
from the program-to-program interface. member DUIGINIT.
RCM
Turns on tracing for event flows within the System action
Resource Collections Manager subtask.
GMFHS must be able to connect to RODM before it is
ALL able to perform any of its applications. GMFHS
Turns on tracing for all APIs. periodically attempts to connect to RODM until it
storagetrace succeeds.
Specifies either one (1) or zero (0) to indicate that
all requests the task makes to allocate or free Operator response
memory are to be traced.
ipcapi1, ipcapi2, ..., ipcapin
Specifies the types of IPC messages to be traced if
the IPC API is enabled. The types are:
NONE Verify that the RODMNAME parameter in DUIGINIT is
Turns off tracing for all IPC messages. the same as the started task name of the RODM rodm.
This is the same RODM that contains the GMFHS
SCO structure load and the object definitions for the
Turns on tracing for messages exchanged with network that is to be monitored by GMFHS.
the Scope Checker optional task (OPT).
If the RODMNAME parameter is not the same as RODM
started task name, do the following:

1. End the GMFHS job with the TERM console System programmer response
command.
If you are not using security software, verify that the
2. Change the value of the RODMNAME parameter in RODM user ID for GMFHS is correct as specified by the
member DUIGINIT so that it is the same as the RODMID parameter in DSIPARM member DUIGINIT. If
started task name of RODM rodm. See the IBM Z the RODMID parameter is not correct:
NetView Administration Reference for more
information. 1. Correct the value of the RODMID parameter in
DUIGINIT. See the IBM Z NetView Administration
3. Start the GMFHS job. Reference for more information.
If the RODMNAME parameter is the same as the RODM 2. Start the GMFHS host job. If you are using security
started task name, then: software, take the steps necessary to correct the
• If RODM with this started task name is not active, problem.
start the task. If you are using security software, take the necessary
• If RODM is active, contact IBM Software Support. steps to correct the problem.
DUI4093E THERE ARE NO ACTIVE RODM DUI4095E RODM PASSWORD NOT

SESSIONS FOR GMFHS TO AUTHORIZED
CONNECT TO
Explanation
Explanation The Graphic Monitor Facility host subsystem (GMFHS)
The Graphic Monitor Facility host subsystem (GMFHS) attempted to connect with the Resource Object Data
attempted to connect with the Resource Object Data Manager (RODM) but failed. This message is followed
Manager (RODM) but failed because no RODM systems by message DUI4007A.
are active.
System action
System action GMFHS ends.
GMFHS must be able to connect to RODM before it is
able to perform any of its applications. GMFHS Operator response
periodically attempts to connect to RODM until it
succeeds.

Operator response
Make sure that the USERID specified by the RODMID
parameter in DUIGINIT has an authorized password or
password phrase in your security product.
DUI4096E AN ERROR REQUIRING
Start a RODM that has a task name that is identical to
RESYNCHRONIZATION HAS BEEN
the RODMNAME parameter in DSIPARM member
FOUND IN THE AGGREGATION
DUIGINIT.
HIERARCHY
DUI4094E RODM USERID NOT DEFINED
Explanation
Explanation A Resource Object Data Manager (RODM) method has
The Graphic Monitor Facility host subsystem (GMFHS) encountered an error in the value of a field of a real or
attempted to connect with the Resource Object Data aggregate object. This error causes status aggregation
Manager (RODM) but failed. This message is followed to fail for the object and its aggregation ancestors.
by message DUI4007A.
System action
System action Graphic Monitor Facility host subsystem (GMFHS)
GMFHS ends. processing continues. information about the object,
field, and value in error is issued to the RODM log.
Operator response

Notify the system programmer. GMFHS periodically attempts to connect to the RODM
until it succeeds.
Operator response
Print the RODM log entries (types 1, 2, 3, and 4) to
determine what caused the error to be introduced into Notify the system programmer.
the aggregation hierarchy. Correct the condition
causing the error and resynchronize the aggregation System programmer response
hierarchy. You can do this by starting the DUIFFAWS
method using the RODM load utility or by reinitializing See theIBM Z NetView Resource Object Data Manager
GMFHS. and GMFHS Programmer's Guide for more information.
DUI4097E RODM CONNECT FAILURE
DUI4099E GENERAL PPI FAILURE, RETURN
CODE = retcode
Explanation
The Graphic Monitor Facility host subsystem (GMFHS) Explanation
attempted to connect with the Resource Object Data
Manager (RODM) and failed. The failure might have An attempt to use the program-to-program interface
occurred because security software is active, but the (PPI) failed. As a result, the Graphic Monitor Facility
class specified in the customization file is not defined host subsystem (GMFHS) cannot communicate with
or active in the security software. the graphic data server.
Message Variables
System action
retcode
GMFHS periodically attempts to connect to RODM until The program-to-program interface return code
it succeeds. that describes the failure.

Notify the system programmer. The action depends on the value of retcode:
• If retcode is 24 or 32, GMFHS periodically attempts
System programmer response to connect with the program-to-program interface.
Verify that the customization file is active and defined • If retcode is any other value, GMFHS cannot attempt
in the security software. If both of these conditions are to connect with the program-to-program interface.
met and this message continues to be issued, contact
IBM Software Support. Operator response
DUI4098E GENERAL RODM FAILURE, Notify the system programmer.
RETURN CODE = retcode, REASON
CODE = reason
Explanation The action taken depends on the value of retcode:
Either the Graphic Monitor Facility host subsystem 24

(GMFHS) attempted to connect with the Resource The NetView subsystem is not active. Start the
Object Data Manager (RODM) but failed, or GMFHS NetView subsystem.
successfully connected to RODM but later had a 28
nonrecoverable RODM failure. NetView is not supporting user requests. Verify
that the NetView program is installed so it can
Message Variables
support user requests.
retcode 32
The value of the return code reported by RODM to The NetView program has experienced a storage
GMFHS. shortage. If this problem does not clear within a
reason short time period, contact IBM Software Support.
The value of the reason code reported by RODM to
GMFHS.

If the return code is any other value, contact IBM Explanation
Software Support.
The program-to-program interface (PPI) return code
DUI4200E RODM CONNECT/DISCONNECT indicates that an error has occurred from which
LOOP GMFHS can recover.
Message Variables
Explanation
retcode
GMFHS has discovered that its user object still exists PPI return code.
in RODM (from a previous invocation). GMFHS then
postcode
deletes the object, attempts to reconnect with RODM,
ECB post code
and once again discovers that its user object is
present. This condition resulted from an problem
within RODM which has since be fixed. System action
System action
GMFHS ends. Operator response
Operator response
Use the PPI return code and ECB post code for
System programmer response assistance in determining the cause of the error.
Ensure that the NetView Subsystem Interface is
active, and the PPI is active within the subsystem.
DUI4201E INVALID PPI DATA RECEIVED
DUI4203E RODM OVERFLOW DATA
FROM PPI SENDER sender
DISCARDED
Explanation
Explanation
GMFHS was unable to correctly interpret the data in
The value of EKG_RBOverflowAction has changed,
the PPI buffer that was received from sender.
causing RODM to discard response block overflow
Message Variables data.
sender
Identifies the PPI sender. System action
System action
PPI message is discarded and processing continues. Operator response
Operator response
Change the value of EKG_RBOverflowAction so that
System programmer response response block overflow data is saved for GMFHS. If
the value of EKG_RBOverflowAction is correct and the
More information is sent to the GMFHS output logs
message still occurs, contact IBM Software Support.
describing the error. The error is likely a result of data
being sent to the GMFHS PPI receiver from an DUI4204E GMFHS USER OBJECT CANNOT BE
unauthorized source. If you cannot determine the DELETED FROM RODM
unauthorized source, contact IBM Software Support
for assistance in interpreting the additional Explanation
information.
An attempt was made to delete an existing GMFHS
DUI4202E TEMPORARY PPI FAILURE, user object from RODM, but there were existing
RETURN CODE = retcode, ECB notification queues or subscriptions on the object and
POST CODE = postcode the EKG_StopMode field on the object was set to

indicate that these queues and subscriptions must not 11
be purged. A RODM Query Multiple Subfield function for
the fields on an object during the evaluation of
System action a collection specification failed. Additional
information on this failure is logged following
GMFHS ends. this message in the RCMGR output file. This
information includes a dump of the function
Operator response block and response block (if available).
A RODM Execute Function List function used to
issue Query Multiple Subfield functions for
multiple objects during the evaluation of a
Change the value of EKG_StopMode so that queues collection specification failed. Additional
and subscriptions will be purged when the object is information on this failure is logged following
deleted. this message in the RCMGR output file. This
DUI4205E ELEMENT MANAGER COMMAND
block and response block (if available).
FAILED, COS TASK NOT ACTIVE
26
A RODM Query Field function failed for the
Explanation
MyObjectChildren field of a class during the
A command cannot be delivered to an element evaluation of a collection specification.
management system through the common operations Additional information on this failure is logged
services (COS) gateway task. The task is inactive. following this message in the RCMGR output
file. This information includes a dump of the
System action function block and response block (if
available).
The command fails, processing continues.
38
A RODM Query Entity Structure function failed
Operator response attempting to query the CDO class structure on
Notify the system programmer. the Network_View_Collection_Class. Additional
information about this failure, is logged
System programmer response following this message in the RCMGR output
If the COS task is not operational, start the COS task. function block and response block (if available)
39
DUI4206E AN RCMGR INITIALIZATION A CollectionSpecn field in the
ERROR HAS OCCURRED, ERROR Collection_Definition_Class is badly formed.
CODE errorcode The value of n is either not an integer, or it is
less than or equal to zero. There is no
Explanation additional information logged with this error.
Review the CollectionSpecn fields on the
An error occurred during the initialization of the Collection_Definition_Class and correct the
RCMGR task of GMFHS. The error is the result of a error.
configurable setting; in most cases, it is a result of the
40
RCMGR interacting with RODM.
A RODM Add Notification Subscription function
Message Variables failed for the Trigger field of the
Network_View_Collection_Class. Additional
errorcode
A numeric code that indicates the type of error.
this message in the RCMGR output file. This
Additional information related to the specific error
is written to the RCMGR output file (to the CNMN
DD from the GMFHS startup procedure, the GTF
output file, the internal trace file, or any 41
combination of these three files depending on the A RODM Add Notification Subscription function
PRINT options that have been requested on the failed for the Trigger field of the
GMFHS TRACE command). The error codes are: Aggregate_Collection_Class. Additional

this message in the RCMGR output file. This following this message in the RCMGR output
information includes a dump of the function file. This information includes a dump of the
block and response block (if available) function block and response block (if
49 available).
A RODM Query Field function on the 63
Network_View_Collection_Class A RODM Trigger Named Method function failed
MyObjectChildren field failed. Additional for the UpdateUserStatus field of an object
information on this failure is logged following linked to a CCO. Additional information on this
this message in the RCMGR output file. This failure is logged following this message in the
information includes a dump of the function RCMGR output file. This information includes a
block and response block (if available). dump of the function block and response block
50 (if available).
A RODM Query Field function on the
Aggregate_Collection_Class MyObjectChildren System action
field failed. Additional information on this The RCMGR task ends, forcing GMFHS to end.
failure is logged following this message in the
RCMGR output file. This information includes a
dump of the function block and response block Operator response
(if available). Notify the system programmer.
58
A RODM Locate function failed while System programmer response
attempting to locate all resources scheduled
Locate the additional information in the RCMGR output
for status updates. Additional information on
file. In most cases, the error is accompanied by a
this failure is logged following this message in
RODM return and reason code for a failure on a RODM
the RCMGR output file. This information
object or class. These errors can occur as a result of
includes a dump of the function block and
errors with the GMFHS data model or incorrectly
response block (if available).
defined Network_View_Collection_Class or
59 Aggregate_Collection_Class objects. Use the logged
A RODM Locate function failed while information as an aid in resolving the problem with
attempting to locate all resources scheduled RODM.
for suspend aggregation. Additional
information on this failure is logged following DUI4207E AN RCMGR FIELD SUBSCRIPTION
this message in the RCMGR output file. This ERROR HAS OCCURRED, ERROR
information includes a dump of the function CODE errorcode
60 Explanation
A RODM Change Field function failed for the An error occurred when the RCMGR task of GMFHS
PolicyCtrSU field of an object linked to a CCO. attempted to add a notification subscription to a field
Additional information on this failure is logged in RODM.
following this message in the RCMGR output
file. This information includes a dump of the Message Variables
function block and response block (if errorcode
available). A numeric code that indicates the type of error.
61 Additional information related to the specific error
A RODM Change Field function failed for the is written to the RCMGR output file (to the CNMN
DisplayStatus field of an object linked to a DD from the GMFHS startup procedure, the GTF
CCO. Additional information on this failure is output file, the internal trace file, or any
logged following this message in the RCMGR combination of these three files depending on the
output file. This information includes a dump of PRINT options that have been requested on the
the function block and response block (if GMFHS TRACE command). The error codes are:
available). 24
62 The add notification subscription for a class/
A RODM ChangeField function failed for the field pair failed. This might cause one or more
PolicyCtrSA field of an object linked to a CCO. collections to be incorrect. Determine the
Additional information on this failure is logged cause of the error from the additional

information that is logged following this Explanation
message in the RCMGR output file. This
The list of candidate resource names returned by the
alert processor is garbled. The alert associated with
block and response block (if available). The
this error is dropped.
recycle GMFHS to Cold Start all collections.
Message Variables
System action alertp
The RCMGR task ignores the subscription and Specifies the name of the alert processor.
continues processing.
System action
Operator response The alert is ignored, processing continues.
Operator response
Locate the additional information in the RCMGR output
file. In most cases, the error is accompanied by a System programmer response
RODM return and reason code for a failure on a RODM
If you are using the default alert processor
(DUIFEDEF), this is an internal error. Contact IBM
errors with the GMFHS data model or incorrectly
Software Support.
defined Network_View_Collection_Class or
Aggregate_Collection_Class objects. Use the logged If you have supplied an alert processor, correct the
information as an aid in resolving the problem with alert processor. The work area is written to the GMFHS
RODM. output logs.
DUI4208E ALERT PROCESSOR alertp DUI4210E ALERT PROCESSOR alertp
OVERLAID WORKAREA 1 LENGTH EXCEEDED MAXIMUM ALLOWED
WORKAREA
Explanation
Explanation
The alert processor changed the length of the first
work area supplied to it. Changing the length is not The alert processor requested a larger work area after
allowed. The alert associated with this error is the maximum work area has been provided. The
dropped. current maximum is one MB of storage. The alert
associated with this error is dropped.
Message Variables
Message Variables
alertp
Specifies the name of the alert processor. alertp
Specifies the name of the alert processor.
System action
System action
The alert is ignored, processing continues.
Operator response
Operator response
If you are using the default alert processor
(DUIFEDEF), this is an internal error. Contact IBM If you are using the default alert processor
Software Support. (DUIFEDEF), this is an internal error. Contact IBM
Software Support.
If you have supplied an alert processor, correct the
alert processor. The work area is written to the GMFHS If you have supplied an alert processor, correct the
output logs. alert processor. The work area is written to the GMFHS
output logs.
DUI4209E ALERT PROCESSOR alertp
RETURNED GARBLED RESPONSE

DUI4211E ALERT PROCESSOR alertp DUI4213E AN RCMGR ERROR HAS
WORKAREA LENGTH REQUEST OCCURRED PROCESSING A
ERROR NETWORK_VIEW_
COLLECTION_CLASS CDO, ERROR
Explanation CODE errorcode
The alert processor requested a smaller work area.

Explanation
The alert associated with this request is dropped.
An error occurred while processing a
Message Variables
Network_View_Collection_Class object. The error is
alertp the result of a configurable setting; in most cases, it is
Specifies the name of the alert processor. a result of the RCMGR interacting with RODM
Message Variables
System action
errorcode
The alert is ignored and processing continues. A numeric code that indicates the type of error.
Additional information related to the specific error
Operator response is written to the RCMGR output file (to the CNMN
DD from the GMFHS startup procedure, the GTF
output file, the internal trace file, or any
combination of these three files depending on the
System programmer response PRINT options that have been requested on the
If you are using the default alert processor GMFHS TRACE command). If known, the name of
(DUIFEDEF), this is an internal error. Contact IBM the MyName of the CDO object is logged first,
Software Support. followed by information specific to the error. The
error codes are:
If you have supplied an alert processor, correct the
alert processor. 1
A RODM Query Subfield function failed while
DUI4212E ALERT PROCESSOR alertp attempting to query the MyId value subfield of
REPORTED PARAMETER ERROR the classname class in the collection
specification; this failure can be because of an
Explanation incorrectly specified class. Additional
The alert processor reported that it was called with this message in the RCMGR output file. This
incorrect parameters. The alert associated with this information includes a dump of the function
request is dropped. block and response block (if available). If the
Message Variables RODM reason code indicates that the class
cannot be found, correct the classname in the
alertp collection specification.
Specifies the name of the alert processor.
2
A RODM Query Field Structure function failed
System action while attempting to query the fieldname field in
The alert is ignored and processing continues. the collection specification; this failure can be
because of an incorrectly specified field.
Operator response Additional information on this failure is logged
Notify the system programmer. file. This information includes a dump of the
function block and response block (if
System programmer response available). If the RODM reason code indicates
that the field cannot be found, correct the
If you are using the default alert processor fieldname in the collection specification.
(DUIFEDEF), this is an internal error. Contact IBM
Software Support. 3
The collection specification value at position
If you have supplied an alert processor, correct the xxx of the full collection specification failed to
alert processor. compile for the regular expression regexp. xxx
is the character position of the value in error.
regexp is the regular expression that was

compiled. If the collection specification value information includes a dump of the function
was already a regular expression, the value block and response block (if available).
and regexp must be identical. The CDO is 13
ignored. Check the CollectionSpecn fields, The data type for the field at position xxx of the
delete the CDO object, and reload the full collection specification is not allowed; data
corrected object. type is datatype. xxx is the character position
4 of the field with the incorrect datatype;
The CollectionSpec is a null string. The CDO is datatype is the name of the RODM data type in
ignored. Check the CollectionSpecn fields, error. The CDO is ignored. Check the
delete the CDO object, and reload the CollectionSpecn fields, delete the CDO object,
corrected object. and reload the corrected object.
5 14
There are no tokens in the collection A RODM Add Delete Notification Subscription
specification. The CDO is ignored. Check the function for the CDO failed. Additional
CollectionSpecn fields, delete the CDO object, information on this failure is logged following
and reload the corrected object. this message in the RCMGR output file. This
6 information includes a dump of the function
The collection specification is syntactically block and response block (if available).
incorrect at the conjunction at position xxx of 15
the full collection specification. When the A RODM Query Field function failed for the
conjunction was found, processing was not at MyName field of the CCO object. If the CCO
the end of a leaf specification. xxx is the object did not exist, if will not generate this
character position of the conjunction in error. error. Additional information on this failure is
The CDO is ignored. Check the CollectionSpecn logged following this message in the RCMGR
fields, delete the CDO object, and reload the output file. This information includes a dump of
corrected object. the function block and response block (if
7 available).
The collection specification is syntactically 16
incorrect at the conjunction at position xxx of A RODM Query Entity Structure function failed
the full collection specification. One side of the during an attempt to delete an object from
logic tree was missing.xxx is the character RODM. Additional information on this failure is
position of the conjunction in error. The CDO is logged following this message in the RCMGR
ignored. Check the CollectionSpecn fields, output file. This information includes a dump of
delete the CDO object, and reload the the function block and response block (if
corrected object. available).
8 17
The end of the full collection specification was A RODM Query Field function failed during an
reached, and there was not exactly one node attempt to delete an object from RODM.
on the logic tree stack. This is usually the Additional information on this failure is logged
result of a missing conjunction. The CDO is following this message in the RCMGR output
ignored. Check the CollectionSpecn fields, file. This information includes a dump of the
delete the CDO object, and reload the function block and response block (if
corrected object. available).
9 18
The end of the full collection specification was A RODM Trigger Unlink function failed during
reached, and there was an incomplete leaf an attempt to delete an object from RODM.
specification. The CDO is ignored. Check the Additional information on this failure is logged
CollectionSpecn fields, delete the CDO object, following this message in the RCMGR output
and reload the corrected object. file. This information includes a dump of the
10 function block and response block (if
A RODM Query Multiple Subfields function for available).
the fields on the CDO failed. Additional 20
information on this failure is logged following A RODM Create Object function failed for the
this message in the RCMGR output file. This creation of the CCO object. Additional

this message in the RCMGR output file. This AGGREGATE_COLLECTION_CLASS
information includes a dump of the function CDO, ERROR CODE errorcode
21 Explanation
A RODM Change Multiple Fields function failed An error occurred while processing an
for multiple fields on the CCO object. Aggregate_Collection_Class object. The error is the
Additional information on this failure is logged result of a configurable setting; in most cases, it is a
following this message in the RCMGR output result of the RCMGR interacting with RODM.
function block and response block (if Message Variables
available). errorcode
29 A numeric code that indicates the type of error.
A RODM Execute Function List function failed Additional information related to the specific error
for linking collection objects into the CCO is written to the RCMGR output file (to the CNMN
object. Additional information on this failure is DD from the GMFHS startup procedure, the GTF
logged following this message in the RCMGR output file, the internal trace file, or any
output file. This information includes a dump of combination of these three files depending on the
the function block and response block (if PRINT options that have been requested on the
available). GMFHS TRACE command). If known, the name of
64 the MyName of the CDO object is logged first,
The field value value is not allowed for the data followed by information specific to the error. The
type datatype of a field within the collection error codes are the same as those for message
specification; datatype is the name of the DUI4213E; see that message for a description of
RODM datatype in error. This problem occurs the codes. There are a few codes that are unique
when a wild card is used with a value that does for this message. These codes are:
not allow a wild card. The CDO is ignored. 22
Check the CollectionSpecn fields, delete the A RODM Query Field function failed for the
CDO object and reload the corrected object. MyId field of the Aggregate CCO Display
65 Resource Type object. Check the
A RODM Query Field function failed for the DisplayResourceType field of the CDO and
MyID field of an object from an NMC wizard insure that it is the name of an object in the
CREATE request. Additional information on this Display_Resource_Type class. Additional
failure is logged following this message in the information on this failure is logged following
RCMGR output file. This information includes a this message in the RCMGR output file. This
dump of the function block and response block information includes a dump of the function
(if available). block and response block (if available).
23
System action A RODM TriggerOIMethod for method
DUIFCLRT failed attempting to link the
The RCMGR task ignores this collection object and Aggregate CCO object to a DRT object. Check
continues processing. the LayoutType field of the CDO and insure that
it is valid. Additional information on this failure
Operator response is logged following this message in the RCMGR
Notify the system programmer. output file. This information includes a dump of
the function block and response block (if
available).
32
Locate the additional information in the RCMGR output A RODM TriggerOIMethod for method
file. In most cases, the error is accompanied by a DUIFCUAP failed attempting to unlink the
RODM return and reason code for a failure on a RODM Aggregate CCO object from its child object.
object or class. Use the logged information as an aid in Additional information on this failure is logged
resolving the problem with RODM. following this message in the RCMGR output
DUI4214E AN RCMGR ERROR HAS file. This information includes a dump of the
OCCURRED PROCESSING AN function block and response block (if
available).

51 the function block and response block (if
A RODM Query Field function failed for the available).
MyId field of the
Layout_Parameter_For_View_Class object. System action
Additional information on this failure is logged
following this message in the RCMGR output The RCMGR task ignores this collection object and
file. This information includes a dump of the continues processing.
available). Operator response
52 Notify the system programmer.
A RODM Trigger Link function failed attempting
to link the Layout_Parameters_For_View_Class System programmer response
object to the CCO object. Additional
information on this failure is logged following Locate the additional information in the RCMGR output
this message in the RCMGR output file. This file. In most cases, the error is accompanied by a
information includes a dump of the function RODM return and reason code for a failure on a RODM
block and response block (if available). object or class. Use the logged information as an aid in
resolving the problem with RODM.
53
A RODM ChangeField function failed for the DUI4215E DUPLICATE SUBTASK
DisplayStatus field of an object linked to a REGISTERED WITH HTM, NAME =
CCO. Additional information on the change subtask
failure is logged following this message in the
Explanation
dump of the function block and response block
(if available). The Host Task Manager program (CNMTAMEL)
54 reported that it is already registered with the specified
A RODM Trigger Named Method function failed name.
for the UpdateUserStatus field of an object Message Variables
linked to a CCO. Additional information on the
trigger failure is logged following this message subtask
in the RCMGR output file. This information Specifies the name of the subtask
response block (if available). System action
55 GMFHS abends.
A RODM ChangeField function failed for the
DisplayStatus field of an object linked to a Operator response
CCO. Additional information on the change
failure is logged following this message in the Notify the system programmer.
dump of the function block and response block System programmer response
(if available).
Attempt to determine what other process may be
56 registered with the host task manager using the given
A RODM Trigger Named Method function failed name. For more information, contact IBM Software
for the UpdateUserStatus field of an object Support.
linked to a CCO. Additional information on the
trigger failure is logged following this message DUI4216E MYNAME FIELD NOT DEFINED ON
in the RCMGR output file. This information GMFHS_SHADOW_OBJECTS_CLAS
includes a dump of the function block and S OBJECT objectname
response block (if available).
57 Explanation
A RODM Query field function on the The MyName field for the RODM object cannot be
Aggregation Child field of an object failed found during an object query.
during an attempt to delete a collection.
Additional information on the query failure is Message Variables
logged following this message in the RCMGR
output file. This information includes a dump of

objectname objectid
Specifies the name of the RODM object. Specifies the RODM ObjectID.

Processing continues. The status change is discarded; processing continues.

Notify the system programmer. Notify the system programmer.

This is an internal RODM error; the MyName field This can happen if alerts are received from the
should be found on any RODM object. Contact IBM network that have earlier time stamps than an alert
Software Support. that previously changed the status of a resource. If
you feel you have received this message in error,
DUI4217E RECEIVED UNEXPECTED EVENT contact IBM Software Support for assistance.
MAJOR VECTOR vector
DUI4219E MYNAME ATTRIBUTE DOES NOT
Explanation START WITH A DOMAIN
IDENTIFIER
A major vector was received by the event manager
subtask that was neither an alert, resolution, or
Explanation
transparent coded data stream.
The MyName attribute of a RODM object is expected to
Message Variables
contain a domain identifier as a prefix, but does not.
vector
Specifies the major vector in error. System action
This error occurs during the parsing of a major vector
System action
to determine a resource status change. The major
The major vector is discarded; processing continues. vector is dicsarded, processing continues.


The major vector in error is written to the GMFHS Ensure that the non-SNA domain definitions in RODM
output logs. This is probably an internal error within are correct. See the output logs for more information
the NetView address space. Contact IBM Software about the object in error.
Support.
If you are using your own alert processor, the alert
DUI4218E STATUS CHANGE REJECTED, processor might be returning incorrect candidate
OBJECT ID = objectid names for the resource. Contact IBM Software Support
for assistance.
Explanation DUI4220E UNKNOWN ALERT TYPE
The time stamp of a change non-SNA status command REPORTED FOR ELEMENT
request is earlier than the last time the status was DOMAIN emdomain
changed for the resource, denoted by its object
identifier. This is reported by the DUIFECDS method, Explanation
which is run to make the change. This message is
The status of an alert major vector cannot be
similar to DUI4225E; for this message, the RODM
translated into a valid DisplayStatus value.
object ID of the object whose DisplayStatus field
cannot be changed is given because a query of the Message Variables
MyName field failed.
Message Variables

emdomain System action
Specifies the Element Management Domain
The request is ignored; processing continues.
identifier.
Operator response
System action
The status change is discarded; processing continues.

Operator response
More information concerning the unexpected request
is written to the GMFHS output logs. This is probably
because of an error in the data server. Contact IBM
System programmer response Software Support for assistance.
An alert was received with an alert code that cannot be DUI4224E AN RCMGR GENERAL ERROR HAS
translated by either the IBM or USR status translation OCCURRED, ERROR CODE
tables. See the output logs for more information about errorcode
the alert. If the alert status is not translated by the
IBM translation table and you expect the alert status
Explanation
to be translated by the USR translation table, correct
the USR table. If you expect the status of this alert to A general error has occurred during normal operation
be translated by the IBM translation table, contact of the RCMGR task of GMFHS. The error is not related
IBM Software Support. to a specific Aggregate_Collection_Class or
NetView_View_Collection_Class object in RODM.
DUI4221E A MAJOR VECTOR SUBVECTOR IS
NOT VALID Message Variables
errorcode
Explanation A numeric code that indicates the type of error.
An alert or resolution major vector subvector had Additional information related to the specific error
either an incorrect length, or the subfields within the is written to the RCMGR output file (to the CNMN
vector were incorrect. This occurred during the parsing DD from the GMFHS startup procedure, the GTF
of the major vector. output file, the internal trace file, or any
combination of these three files depending on the
PRINT options that have been requested on the
System action
GMFHS TRACE command). The error codes are:
The alert or resolution major vector is discarded; 16
processing continues. A RODM Query Entity Structure function failed
during an attempt to delete an object from
Operator response RODM. Additional information on this failure is
Notify the system programmer. logged following this message in the RCMGR
output file. This information includes a dump of
the function block and response block (if
System programmer response available).
An erroneous alert was received. More information 17
concerning the subvector is written to the output logs. A RODM Query Field function failed during an
Ignore or correct the alert if possible. attempt to delete an object from RODM.
DUI4223E DBSERVER RECEIVED AN Additional information on this failure is logged
UNEXPECTED REQUEST FROM A following this message in the RCMGR output
DATA SERVER file. This information includes a dump of the
available).
Explanation
18
The DataBase Server subtask of GMFHS received a A RODM Trigger Unlink function failed during
function request from a Graphic Data Server that it did an attempt to delete an object from RODM.
not understand. Additional information on this failure is logged

function block and response block (if Explanation
available).
The time stamp of a change non-SNA status command
19 request is earlier than the last time the status was
A RODM DeleteObject function failed during an changed for the resource, denoted by its resource
attempt to delete an object from RODM. name. This is reported by the DUIFECDS method,
Additional information on this failure is logged which is run to make the change. This message is
following this message in the RCMGR output similar to DUI4218E.
function block and response block (if Message Variables
available). resource
66 Specifies the resource on which the status change
A RODM Query Field function failed for the failed.
MyObjectChildren field of a class from an NMC
wizard QUERY request. Additional information System action
on this failure is logged following this message
The status change is ignored; processing continues.
in the RCMGR output file. This information
response block (if available). Operator response
67 Notify the system programmer.
A RODM Query Entity Structure function failed
for the class from an NMC wizard QUERY System programmer response
request. Additional information on this failure
is logged following this message in the RCMGR This can happen if alerts are received from the
output file. This information includes a dump of network that have earlier time stamps than an alert
the function block and response block (if that previously changed the status of a resource. If
available). you feel you have received this message in error,
contact IBM Software Support for assistance.
68
A RODM Query Multiple Subfields function DUI4226E ELEMENT MANAGER COMMAND
failed for the class/object/field from an NMC FAILED. DOMAIN NOT FOUND FOR
wizard QUERY request. Additional information TARGET RESOURCE
on this failure is logged following this message
in the RCMGR output file. This information Explanation
response block (if available). The RODM resource which is the target of an element
management system command is missing a RODM
domain object link. This link is needed to determine
System action
where the element management system that executes
The RCMGR task ends, forcing GMFHS to end. the command exists.

Notify the system programmer. The command is ignored; processing continues.

Locate the additional information in the RCMGR output Notify the system programmer.
file. In most cases, the error is accompanied by a
RODM return and reason code for a failure on a RODM System programmer response
errors with the GMFHS data model or incorrectly Check the command target object in RODM to
defined Network_View_Collection_Class or determine why it is not linked with a domain object. If
Aggregate_Collection_Class objects. Use the logged you feel you have received this message in error,
information as an aid in resolving the problem with contact IBM Software Support for assistance.
RODM. DUI4227E RODM QUERY FAILURE IN
DUI4225E STATUS CHANGE REJECTED, NETCMD
RESOURCE = resource

The NETCMD subtask reported an error while querying Verify that the resource definition file loads without
an object in RODM error. The field in error is the DisplayResourceName
field or one of the generic command text fields, and
System action the error detected indicates that the field type of the
field in error is incorrect. Contact IBM Software
The command is ignored; processing continues. Support for assistance.
DUI4230E UNKNOWNTHRESHOLD FIELD
Operator response
MISSING FROM GLOBAL
Notify the system programmer. AGGREGATE CLASS

Look in the GMFHS output log for additional The UnknownThreshold field is not defined on the
information about the type of query failure. Contact Global_Aggregation_Parameters_Class.
IBM Software Support for assistance.
DUI4228E ELEMENT MANAGER COMMAND System action
TARGET IS A DOMAIN The data server request for this unknown threshold
fails; processing continues.
Explanation
The target of an element management system Operator response
command is the management system domain; this is Notify the system programmer.
not allowed.
System action
Check the RODM and GMFHS output logs. Verify that
The command is ignored; processing continues. the resource definition file loads without error. Contact
Operator response
DUI4231E FIND OF RODM OBJECT FOR
Notify the system programmer. myname FAILED

See the GMFHS output log for additional information No RODM object can be found with a MyName field
about the domain in error. Contact IBM Software value that matches a CP resource name in a DOMP010
Support for assistance. protocol command response. The status provided in
the response for that component is discarded.
DUI4229E NETCMD ERROR QUERYING
TARGET RESOURCE Message Variables
myname
Explanation RODM object for which the search failed.
Either the display resource name or generic command
RODM data type is incorrect for the target resource. System action
Generic commands can be retrieved from either the
target resource, or from the target resources domain
object.
Operator response
The command is ignored, processing continues.
Operator response Verify that the resource definition file loads without
error. Contact IBM Software Support for assistance.

DUI4235E NOTIFICATION METHOD ON THE and one of the RODM methods used to complete the
field FIELD OF object FAILED request failed.
AFTER FIELD VALUE CHANGED TO
value System action
Explanation
The task changed the value of the indicated field of the Operator response
named object but the reason code from the RODM
change request is in the range used by the EKGNOTF Notify the system programmer.
method to report a failure. The field value has been
changed, but notifications of this change were not sent System programmer response
to subscribers. More information regarding the failure is written in the
Message Variables GMFHS and RODM output logs. Contact IBM Software
Support for more information.
field
Specifies which field was changed. DUI4239E RODM REQUEST FAILED:
object SLOW/NO RESPONSE
Specifies the object that the field is part of.
Explanation
value
Specifies the value to which field was changed. The NETCON subtask has made a RODM request, and
RODM response came back after a timeout or did not
System action come back at all.
System action
Operator response Processing continues.

Operator response
System programmer response Contact the system programmer.
More information about the query failure is written in

the output logs. Contact IBM Software Support for
assistance. See the IBM Z NetView Troubleshooting Guide for more
information. More information regarding the failure is
DUI4237E LIST OF SUSPENDED RESOURCES
written in the GMFHS and RODM output logs. Contact
TOO LARGE TO SEND TO
WORKSTATION. ONLY PARTIAL
LIST WAS SENT DUI4240E ERROR TRIGGERING RESOURCE
TYPE PROFILE UPDATE METHOD
Explanation
Explanation
The List Suspended Resources request resulted in a
response that contained too much data. The list of The NETCMD subtask received an error while
resources has been truncated. attempting to trigger an aggregation class profile
update method.
System action
System action
DUI4238E WARNINGS LOGGED BY THE
METHOD: CHECK RODM LOG FOR
MORE INFORMATION Operator response
Contact the system programmer.
Explanation
The NETCMD subtask was performing a List
Suspended Resources or Aggregation Update request,

System programmer response suspended. One of the notifications was not returned
in the time allowed. If any notifications are received,
More information regarding the failure is written in the
the partial list of suspended resources is displayed at
GMFHS and RODM output logs. Contact IBM Software
the workstation.
Support for more information.
DUI4246E RODM REQUEST FAILED: RODM System action
SETUP INCORRECT
Explanation
Operator response
The NETCON subtask has made a RODM request, and
RODM response indicated a failure because of a RODM Retry the list suspended resources command.
installation or customization error. DUI4251E ALERT PROCESSOR alertp
OVERLAID WORKAREA 2 LENGTH
System action
Processing continues. Explanation
The alert processor changed the length of the second
Operator response work area supplied to it. This is not allowed. The alert
associated with this error is dropped.
Message Variables
System programmer response alertp
See the IBM Z NetView Resource Object Data Manager Specifies the alert processor.
and GMFHS Programmer's Guide for more information.
More information regarding the failure is written in the System action
Support for assistance.
DUI4248E THE GET AGGREGATION PROFILE Operator response
REPLY HAS TIMED OUT
Explanation
The NETCMD subtask was waiting for a RODM
notification containing the information for the If you are using the default alert processor
requested aggregation profile, which timed out. RODM (DUIFEDEF), this is an internal error. Contact IBM
did not return the reply for Get Aggregation Profile in Software Support.
the time allowed. If you have supplied an alert processor, correct the
alert processor. The work area is written to the GMFHS
System action output logs.
Processing continues. DUI4252E COULD NOT QUERY THE
timestamp TIMESTAMP SUBFIELD
Operator response OF object
Retry the aggregation profile command.

Explanation
DUI4249E THE LIST SUSPENDED The EVENTMGR subtask updated the DisplayStatus
RESOURCES REPLY HAS TIMED field of the indicated object but cannot successfully
OUT query the time stamp subfield to provide a system
time for the event report that is logged.
Explanation
Message Variables
The NETCMD subtask was waiting for a RODM
notification containing the information for the List timestamp
Suspended Resources request, which timed out. The Name of the timestamp subfield.
list of suspended resources might require more than object
one notification when a large number of resources are Object for which query attempted.

The DisplayStatus update is ignored, processing More information regarding the failure is written in the
continues. GMFHS and RODM output logs. Contact IBM Software
Operator response DUI4255E GLOBAL_NLS_PARAMETERS_CLAS
Contact the system programmer. S ATTRIBUTE VALUE ERROR
ATTRIBUTE: attribute VALUE:
value
Contact IBM Software Support for assistance. Explanation
DUI4253E TASK sender DISCARDING The value on one of the Global_NLS_Parameters_Class
MESSAGE; MAXIMUM REACHED attributes is not valid.
FOR TASK receiver
Message Variables
Explanation attribute
Specifies the RODM field (attribute).
The number of messages queued to a given task has
reached the maximum. The sending task discards the value
message. Specifies the RODM field value in error.
Message Variables
System action
sender
Identifies the GMFHS sending subtask.
receiver
Operator response
Identifies the GMFHS receiving subtask.
System action
Correct the RODM field and restart GMFHS.
Operator response DUI4256E CONFIGURATION
Contact the system programmer. INITIALIZATION FAILED DUE TO
ERROR IN RODM
Explanation
Contact IBM Software Support for assistance.
The RODM data type of a field in the
DUI4254E AGGREGATION WARMSTART Global_NLS_Parameters_Class is not of the expected
METHOD FAILED type for the field.

The Aggregation Warmstart method, triggered by the Network Configuration will fail, GMFHS processing
NETCON subtask, did not run successfully. continues.

Processing continues. Contact the system programmer.

Contact the system programmer. More information regarding the failure is written in the
DUI4257E UNEXPECTED DATA TYPE, FIELD =
field

Issued in association with other messages that Network Configuration will fail, GMFHS processing
indicate the termination of configuration initialization. continues.
This message indicates that the data type of the field
is not the data type expected. Operator response
Message Variables Contact the system programmer.
field
Data type of field which received bad data. System programmer response
A following message has more information about the
System action type of error. More information regarding the failure is
Processing continues. written in the GMFHS and RODM output logs. Contact
Operator response DUI4260E DOMAIN OBJECT INFORMATION
MISSING
Explanation
While parsing the data for SNA or non-SNA domain
GMFHS and RODM output logs. Contact IBM Software Class objects, the network configuration subtask
determined that an object or fields on an object are
missing. This can be the MyObjectChildren field on the
DUI4258E MISSING FIELD = field class object, or required fields within the child domain
object.
Explanation
System action
Issued in association with other messages that
indicate the termination of configuration initialization. Processing continues.
This message indicates that the field specified by field
is missing from the class definition. Operator response
field
Field missing from class definition. System programmer response
A following message has more information about the
System action type of error. More information regarding the failure is
Processing continues. written in the GMFHS and RODM output logs. Contact
Operator response DUI4261E DOMAIN OBJECT DEFINITION
Contact the system programmer. ERROR
More information regarding the failure is written in the While parsing the data for SNA or non-SNA domain
GMFHS and RODM output logs. Contact IBM Software Class objects, the network configuration subtask
Support for assistance. determined that a field on the object has an incorrect
data type.
DUI4259E NMG CLASS DEFINITION ERROR
System action
Explanation
While parsing the data from an NMG Class object, the
network configuration subtask determined that the Operator response
object contains erroneous data.

A following message has more information about the A following message has more information about the
type of error. More information regarding the failure is type of error. More information regarding the failure is
written in the GMFHS and RODM output logs. Contact written in the GMFHS and RODM output logs. Ensure
IBM Software Support for assistance. that the element manager on the remote system is
operational.
DUI4264E NMG OBJECT INFORMATION
MISSING DUI4266E NMG ATTRIBUTE VALUE ERROR
While parsing the data for NMG Class objects, the A field on an NMG class object has an unsupported
network configuration subtask determined that an value.
object or fields on an object are missing.
System action
System action
Operator response
Operator response
A following message has more information about the GMFHS and RODM output logs. Ensure that the
type of error. More information regarding the failure is element manager on the remote system is operational.
written in the GMFHS and RODM output logs. Contact
IBM Software Support for assistance. DUI4267E ATTRIBUTE VALUE ENCOUNTERED
IN SNA_DOMAIN
DUI4265E STATUS SOLICITATION FAILED
FOR RESOURCE Explanation
domain.component
A field on a SNA Domain Class object has an incorrect
value.
Explanation
The network configuration subtask is reporting that a System action
status solicitation command to the element
management system at domain failed for the specified Processing continues.
component.
Operator response
Message Variables
domain
Specifies the domain to which the command was
issued. System programmer response
component More information regarding the failure is written in the
Specifies the component, or resource, to which the GMFHS and RODM output logs. Correct the problem
command was issued. and reload the information in RODM.
DUI4268E AGGREGATION WARMSTART
System action METHOD COMPLETED WITH
Processing continues. WARNINGS
Contact the system programmer. The aggregation warmstart method issued a warning
return code when invoked by the network
configuration subtask.

System action DUI4271E MANAGER STATUS MONITOR
SETUP FAILED (returncode/
reasoncode). NO MANAGER
STATUS WILL BE REPORTED
Operator response
Contact the system programmer. Explanation
The NETCON manager status monitor function was not
System programmer response able to install notification methods. Manager status
More information regarding the failure is written in the cannot be reported.
GMFHS and RODM output logs. If the source of the Message Variables
error cannot be determined from the output logs,
contact IBM Software Support for assistance. returncode
Specifies the RODM return code.
DUI4269E UNSUPPORTED PROTOCOL
reasoncode
COMBINATION -- OST AND
Specifies the RODM reason code.
DOMP010
System action
Explanation
The specified protocol combination of operator station
task (OST) and DOMP010 are not supported on an
NMG and domain pairing. Operator response
System action
Processing continues. System programmer response
Operator response GMFHS and RODM output logs. Correct the problem
and reload the information in RODM. Contact IBM
Software Support for assistance.
System programmer response DUI4272E MANAGER STATUS MONITOR

FIELD CHANGE FAILED
Correct the protocol mismatch and reload the
(returncode/reasoncode). FIELD:
information in RODM.
field, CLASS: class
DUI4270E ATTRIBUTE VALUE ERROR
ENCOUNTERED IN Explanation
NON_SNA_DOMAIN
An attempt was made to change a field related to the
manager status monitor function, but the change
Explanation failed.
A field on a non-SNA domain class object has an Message Variables
incorrect value.
returncode
System action
reasoncode
Processing continues. Specifies the RODM reason code.
field
Operator response
Specifies the field for which RODM change was
Contact the system programmer. requested.
class
System programmer response Specifies the class for which RODM change was
requested.
GMFHS and RODM output logs. Correct the problem
and reload the information in RODM. System action

Operator response DUI4275E SET INITIAL OR SET UNKNOWN
STATUS METHOD COMPLETED
WITH WARNINGS

Explanation
Either DUIFFIRS or DUIFFSUS completed with a
GMFHS and RODM output logs. Correct the problem
warning return code.
and reload the information in RODM. Contact IBM
System action
DUI4273E EMDOMAIN emdomain WAS
DUPLICATED IN THE FOLLOWING Processing continues.
NON-SNA DOMAIN OBJECTS:
Operator response
Explanation Contact the system programmer.
A duplicate EMDomain value was detected in another
non-SNA object EMDomain field, or in a SNA Domain System programmer response
object's MyName field.
Message Variables GMFHS and RODM output logs. If the source of the
emdomain
EMDomain name.
DUI4276E SET INITIAL STATUS METHOD
System action COMPLETED WITH ERRORS
Message DUI4274 is issued after this message once
for every duplicate object. Processing continues. Explanation
DUIFFIRS completed with an error return code.
Operator response
Contact the system programmer. System action
DUI4274E --DUPLICATED
NON_SNA_DOMAIN OBJECT:
object Operator response
Explanation
A list of the duplicate domain objects MyName field. System programmer response
Message Variables More information regarding the failure is written in the

GMFHS and RODM output logs. If the source of the
object error cannot be determined from the output logs,
SNA or non-SNA domain object name. contact IBM Software Support for assistance.
DUI4277E COMMAND BUFFER FOR ELEMENT
System action
MANAGER COMMANDS IS FULL
Explanation
Operator response
The NETCMD subtask cannot add the command to its
Contact the system programmer. internal command buffer because the buffer is full.
The command is discarded.
Correct the duplicate EMDomain field problem and System action
reload the information in RODM. The EMDomain field Processing continues.
MUST be unique among the individual domains.
DUI4278E ALL TRANSPORT CORRELATORS
FOR AN ELEMENT MANAGER

COMMAND ARE CURRENTLY IN successful, but a warning condition is reported from
USE RODM.
Message Variables
Explanation
domain
The maximum number of command blocks have been Specifies the domain ID.
allocated.
displaystatus
Specifies the new DisplayStatus value.
System action
Processing continues. System action
Operator response
Contact the system programmer. Operator response
Contact IBM Software Support for additional System programmer response
information.
DUI4279E OBJECT ATTRIBUTE WRONG TYPE GMFHS and RODM output logs. If the source of the
- EXPECTED type1 - FOUND type2 error cannot be determined from the output logs,
Explanation DUI4281E UNABLE TO ACQUIRE THE
The NETCMD subtask received an unexpected data DISPLAY NAME FROM RODM
type when attempting to query an object field.
Explanation
Message Variables
NECMD was not able to get the value of a
type1
DisplayResourceName field; the field was not found on
Expected field type.
the object.
type2
Found field type.
System action
System action Processing continues.
Operator response
Operator response Contact the system programmer.

System programmer response More information regarding the failure is written in the
GMFHS and RODM output logs. If the source of the
More information regarding the failure is written in the error cannot be determined from the output logs,
GMFHS and RODM output logs. If the source of the contact IBM Software Support for assistance.
contact IBM Software Support for assistance. DUI4282E NATIVE COMMAND TEXT FOR AN
ELEMENT MANAGER COMMAND
DUI4280E DOMAIN domain ENCOUNTERED NOT FOUND IN RODM
AN ERROR CHANGING THE
DISPLAYSTATUS TO displaystatus.
Explanation
Explanation The command text for an element management

system native command cannot be found on the
The NETCMD subtask attempted to change the domain or class object in RODM.
DisplayStatus field value of a Non_SNA_Domain_Class
object to reflect the status of its gateway
communications session. The attempt failed, or it was

Processing continues. Contact the system programmer.

Contact the system programmer. Correct the gateway name in RODM and reload the
RODM information. ContactIBM Software Support for
System programmer response assistance.
More information regarding the failure is written in the DUI4285E EMDOMAIN NAME NOT FOUND OR
GMFHS and RODM output logs. If the source of the INCORRECT
contact IBM Software Support for assistance. Explanation
DUI4283E THE REQUESTED ELEMENT The NETCMD subtask found that an element
MANAGER COMMAND SERVICE management system EMDomain name was not found
TYPE IS NOT SUPPORTED, TYPE or was unusable for this domain.
type
System action
Explanation
The NETCMD subtask received a command request
from a data server that has an unsupported command Operator response
request type.
Message Variables
type System programmer response
Command type.
Correct the EMDomain name in RODM and reload the
RODM information. Contact IBM Software Support for
System action assistance.
Processing continues. DUI4286E TARGET RESOURCE OBJECT FOR
AN ELEMENT MANAGER
Operator response COMMAND NOT DEFINED IN
Contact the system programmer. RODM
More information regarding the failure is written in the The target resource object cannot be found in RODM.
GMFHS and RODM output logs. This is an internal
error. Contact IBM Software Support for assistance. System action
DUI4284E GATEWAY NAME NOT FOUND OR Processing continues.

INCORRECT FOR DOMAIN domain.
Operator response
The NETCMD subtask found that an element
management system gateway name was not found or System programmer response
was unusable for this domain.
Correct the target resource name or add the target
Message Variables resource object to RODM and reload RODM. Contact
domain
Domain name. DUI4287E TARGET RESOURCE OBJECT FOR
AN ELEMENT MANAGER
System action COMMAND IS NOT DEFINED
CORRECTLY IN RODM

The target resource object is not defined correctly in Contact the system programmer.
RODM.
System action
Attempt to determine from other messages what
Processing continues. caused the session to be lost with the element
manager gateway. Reestablish the session.
Operator response DUI4290E THE SESSION WITH THE ELEMENT
Contact the system programmer. MANAGER GATEWAY WAS LOST
BEFORE COMMAND RESPONSE
RECEIVED
Correct the target resource object entry in RODM and Explanation
reload RODM. Contact IBM Software Support for
assistance. An element management system command was
discarded because of the session being lost with the
DUI4288E COMMAND TEXT SUBSTITUTION element manager gateway.
PARAMETER IS NOT SUPPORTED
System action
Explanation
The text of a command that is about to be sent to an
element management system by the NETCMD task
Operator response
contains an unsupported substitution variable.
System action
Attempt to determine from other messages what
Operator response caused the session to be lost with the element
manager gateway. Reestablish the session.
DUI4291E ELEMENT MANAGER COMMAND
System programmer response NOT ALLOWED ON THIS
RESOURCE
GMFHS output logs. Use this information to determine Explanation
what object in RODM contains the failing command
text. Correct the substitution parameter and reload the The NETCMD subtask has attempted to send a
information in RODM. command to the element management system for a
particular resource, but the command is not valid for
DUI4289E THE SESSION WITH THE ELEMENT this resource.
MANAGER GATEWAY IS NOT
ACTIVE
System action
The NETCMD subtask is attempting to route a

Operator response
command to an element management system and
there is no active session with the element manager Contact the system programmer.
gateway.
System action
Use the GMFHS output logs and other GMFHS
Processing continues. messages to determine why the command is not valid
for this resource. Contact IBM Software Support for
assistance.

DUI4292E ELEMENT MANAGER COMMAND Message Variables
RESPONSE TYPE MISMATCH. receivedsq
EXPECTED expectedtype, GOT Received sequence number.
receivedtype
expectedsq
Expected sequence number.
Explanation
The element management system response for a System action
command that was issued by the NETCMD subtask did
not contain the expected command type. The command is discarded and processing continues.
Message Variables
Operator response
expectedtype
The expected command type.
receivedtype System programmer response
The received command type.
System action DUI4295E SEQUENCE NUMBER NOT
The command is discarded and processing continues. PRESENT IN ELEMENT MANAGER
COMMAND RESPONSE
Operator response
Explanation
The element management system response for a
not contain any sequence number value.
DUI4293E ELEMENT MANAGER COMMAND System action
RESPONSE DID NOT CONTAIN The command is discarded and processing continues.
RESPONSE KEYWORD
Operator response
Explanation
command that was issued by the NETCMD subtask did System programmer response
not contain the expected response keyword.
System action DUI4296E DISPLAYSTATUS COMMAND
The command is discarded and processing continues. DOESN't CONTAIN ST = KEYWORD
Contact the system programmer. The element management system response for a
not contain a status value.
Contact IBM Software Support for assistance. System action
DUI4294E COMMAND RESPONSE SEQUENCE The command is discarded and processing continues.
NUMBER INCORRECT. GOT
receivedsq, EXPECTED expectedsq Operator response
The element management system response for a System programmer response

not contain the expected sequence number value. Contact IBM Software Support for assistance.

DUI4297E STATUS (status) FROM ELEMENT not contain a valid time stamp, or the time stamp was
MANAGER COMMAND RESPONSE not present.
CANNOT BE CONVERTED
System action
Explanation The command is discarded and processing continues.
command that was issued by the NETCMD subtask did Operator response
not contain a status value that can be converted to
NetCenter status. Contact the system programmer.

status Contact IBM Software Support for assistance.
Received status.
DUI4300E REASONCODE FROM ELEMENT
System action MANAGER COMMAND RESPONSE
IS NOT PRESENT OR NOT VALID
The command is discarded and processing continues.
Explanation
Operator response
Contact the system programmer. command that was issued by the NETCMD subtask did
not contain a valid reasoncode, or the reasoncode was
System programmer response not present.
System action
DUI4298E STATUS (status) FROM ELEMENT
MANAGER COMMAND RESPONSE The command is discarded and processing continues.
IS NOT VALID
Operator response
command that was issued by the NETCMD subtask did System programmer response
not contain a valid status value. Contact IBM Software Support for assistance.
Message Variables
DUI4301E PROTOCOLCODE FROM ELEMENT
status MANAGER COMMAND RESPONSE
Received status. IS NOT VALID

The command is discarded and processing continues. The element management system response for a
Operator response not contain a valid protocolcode.

System action
System programmer response The command is discarded and processing continues.

Operator response
DUI4299E TIMESTAMP FROM ELEMENT Contact the system programmer.
MANAGER COMMAND RESPONSE
IS NOT PRESENT OR NOT VALID
Explanation Contact IBM Software Support for assistance.
The element management system response for a DUI4302E COMMAND STATUS FROM
command that was issued by the NETCMD subtask did ELEMENT MANAGER COMMAND

RESPONSE IS NOT PRESENT OR month
NOT VALID Specifies the month the response was received.

The element management system response for a The command is discarded and processing continues.
not contain a valid command status, or the command Operator response
status was not present.
System action
Operator response DUI4305E DAY PORTION OF TIMESTAMP
FROM ELEMENT MANAGER
COMMAND RESPONSE IS NOT
VALID, DAY day
DUI4303E YEAR PORTION OF TIMESTAMP The element management system response for a
FROM ELEMENT MANAGER command that was issued by the NETCMD subtask did
COMMAND RESPONSE IS NOT not contain a time stamp with a valid day.
VALID, YEAR year
Message Variables
Explanation day
Specifies the day the response was received.
System action
not contain a time stamp with a valid year.
Message Variables
year Operator response
Specifies the year the response was received.
System action
Operator response DUI4306E HOUR PORTION OF TIMESTAMP
Contact the system programmer. FROM ELEMENT MANAGER
COMMAND RESPONSE IS NOT
VALID, HOUR hour
DUI4304E MONTH PORTION OF TIMESTAMP The element management system response for a
FROM ELEMENT MANAGER command that was issued by the NETCMD subtask did
COMMAND RESPONSE IS NOT not contain a time stamp with a valid hour.
VALID, MONTH month
Message Variables
Explanation hour
Specifies the hour the response was received.
System action
not contain a time stamp with a valid month.
Message Variables

Operator response DUI4309E UNABLE TO COMPLETE A
SEGMENTED COMMAND TO
domain

Explanation
DUI4307E MINUTES PORTION OF command segment indicates that the command
TIMESTAMP FROM ELEMENT cannot be completed. The entire command is
MANAGER COMMAND RESPONSE discarded.
IS NOT VALID, MINUTES minutes
Message Variables
Explanation domain
Specifies the destination element management
The element management system response for a system domain.
not contain a time stamp with a valid minute.
System action
Message Variables
minutes
Specifies the minute the response was received. Operator response
System action
The command is discarded and processing continues. System programmer response
Operator response
Contact the system programmer. DUI4310E AGGREGATION PROFILE
NOTIFICATION NOT CORRELATED
-- CHECK FOR COMMAND
System programmer response TIMEOUT
Explanation
DUI4308E SECONDS PORTION OF
TIMESTAMP FROM ELEMENT The NETCMD subtask received a response for an
MANAGER COMMAND RESPONSE aggregation profile request that cannot be correlated
IS NOT VALID, SECONDS seconds to any outstanding commands in its command list.
This may be because of a timeout, which caused the
Explanation command to be removed from the internal command
list.
System action
not contain a time stamp with a valid seconds.
Message Variables
seconds Operator response
Specifies the second the response was received.
System action
If this happens persistently, contact IBM Software
Support for assistance. Otherwise, retry the command.
Operator response
DUI4311E NETCMD ERROR TRIGGERING
UPDATE USER STATUS METHOD

Explanation command is being routed to, or from which the
response has come.
The NETCMD subtask received an error when
attempting to trigger the DUIFCUUS (Update User
Status) method. System action
System action
The update is ignored, processing continues. Operator response
Operator response
Contact the system programmer. System programmer response
This is an internal error. Contact IBM Software Support
System programmer response for assistance.
More information regarding the failure is written in the DUI4314E COMMAND TYPE type WITH
GMFHS and RODM output logs. Contact IBM Software PASSTHRU PRESENTATION
Support for assistance. PROTOCOL IS NOT ALLOWED
DUI4312E NO RESPONSE TO SESSION
PROTOCOL SET TIME COMMAND Explanation
FOR DOMAIN domain The NETCMD subtask cannot find the gateway domain
name for the element management system that this
Explanation command is being routed to, or from which the
response has come.
The NETCMD subtask did not receive a response to a
set time command from the element management Message Variables
system. The command has timed out.
type
Message Variables Specifies the command type. 1 indicates the
Generic command type
domain
Specifies the destination element management
system domain. System action
System action
Processing continues. Operator response
Operator response
Generic commands are not valid to be sent using the
System programmer response PASSTHRU presentation protocol. Change the
presentation protocol for the element management
Ensure that the element management system for the
system, or send a resource specific or native command
gateway uses the DOMS010 session protocol. Make
instead.
sure that the element management system is active. If
the problem persists for this domain, contact IBM DUI4315E COMMAND BLOCK ERROR,
Software Support for assistance. UNKNOWN DOMAIN OR NMG
OBJECT
DUI4313E GATEWAY DOMAIN NAME
CANNOT BE LOCATED FOR
ELEMENT MANAGER COMMAND Explanation
PROCESSING The NETCMD subtask cannot find either the domain
name or the NMG agent name for the transport of the
Explanation command.
The NETCMD subtask cannot find the gateway domain
name for the element management system that this System action

Contact the system programmer. The NETCMD subtask cannot create a resource name
for the %resource% substitution variable.
This is an internal error. Contact IBM Software Support string
for assistance. Specifies the resource string.
DUI4316E COMMAND BLOCK ERROR,
DOMAIN NAME NOT VALID System action
Explanation
The NETCMD subtask found a domain name that is not Operator response
valid while building a command. Contact the system programmer.

The command is discarded and processing continues. This is an internal error. Contact IBM Software Support
for assistance.
Operator response
DUI4319E %TYPE% SUBSTITUTION FAILED.
Contact the system programmer. COULD NOT GET TYPE FROM
COMMAND BLOCK
This is an internal error. Contact IBM Software Support Explanation
for assistance. The NETCMD subtask cannot find the %type%
DUI4317E PRESENTATION PROTOCOL TYPE substitution variable in the command block.
IS NOT VALID, TYPE=type
System action
Explanation The command is discarded and processing continues.
The NETCMD subtask found that the presentation
protocol is not of a supported type. Operator response
type
Specifies the presentation protocol type. System programmer response
System action for assistance.
The command is discarded and processing continues. DUI4320E %APPL% SUBSTITUTION FAILED.
COULD NOT GET TRANSACTION
Operator response PROGRAM FROM COMMAND
BLOCK
Explanation
The NETCMD subtask cannot find the %appl%
This is an internal error. Contact IBM Software Support substitution variable in the command block.
for assistance.
DUI4318E %RESOURCE% SUBSTITUTION System action
FAILED. COULD NOT PARSE The command is discarded and processing continues.
RESOURCE FROM RESOURCE
STRING string
Operator response

This is an internal error. Contact IBM Software Support The command is discarded and processing continues.
for assistance.
DUI4321E %SPNAME% SUBSTITUTION Operator response
FAILED. COULD NOT GET NMG Contact the system programmer.
NAME FROM COMMAND BLOCK
Explanation
The NETCMD subtask cannot find the %spname% GMFHS output logs. Contact IBM Software Support for
substitution variable in the command block. assistance.
DUI4324E REASON IN COMMAND RESPONSE
System action
NOT FORMATTED CORRECTLY
Explanation
Operator response
The reason provided by the RN keyword of a response
Contact the system programmer. is not formatted correctly.

This is an internal error. Contact IBM Software Support The command is discarded and processing continues.
for assistance.
DUI4322E CP NAME IN COMMAND Operator response
RESPONSE DOES NOT MATCH Contact the system programmer.
NAME IN REQUEST
Explanation
There is a name in the list of names provided by the CP GMFHS output logs. Contact IBM Software Support for
keyword of a response that does not match any of the assistance.
names that were given on the command request.
DUI4325E PROTOCOL IN COMMAND
RESPONSE NOT FORMATTED
System action
CORRECTLY
Explanation
Operator response
The protocol provided by the PT keyword of a
Contact the system programmer. response is not formatted correctly.

More information regarding the failure is written in the The command is discarded and processing continues.
GMFHS output logs. Contact IBM Software Support for
assistance. Operator response
DUI4323E TIMESTAMP IN COMMAND Contact the system programmer.
RESPONSE NOT FORMATTED
CORRECTLY System programmer response
Explanation More information regarding the failure is written in the

The time stamp provided by the TM keyword of a assistance.
response is not formatted correctly.
DUI4326E SEQUENCE NUMBER (seqnumber)
IN COMMAND RESPONSE NOT
FORMATTED CORRECTLY

The sequence number provided by the SQ keyword of More information regarding the failure is written in the
a response is not formatted correctly or has an out of GMFHS output logs. Contact IBM Software Support for
sequence number. assistance.
DUI4329E STATUS IN COMMAND RESPONSE
System action NOT FORMATTED CORRECTLY
Explanation
Operator response The status provided by the ST keyword of a response
Contact the system programmer. is not formatted correctly.
More information regarding the failure is written in the The command is discarded and processing continues.
DUI4327E RESPONSE INDICATOR NOT Contact the system programmer.
PRESENT IN COMMAND
RESPONSE System programmer response
Explanation
The response indicator RP was not sent in the assistance.
command response.
DUI4330E STATUS IN COMMAND RESPONSE
DID NOT HAVE A KNOWN VALUE
System action
The command is discarded and processing continues. Explanation
The status provided by the ST keyword of a response
Operator response does not contain a recognized value.
System action
System programmer response The command is discarded and processing continues.
GMFHS output logs. Contact IBM Software Support for Operator response
assistance.
DUI4328E RESPONSE TEXT DID NOT
CONTAIN A LEFT PARENTHESIS System programmer response
Explanation
The response text TX did not start with a left assistance.
parenthesis.
DUI4331E DOMAIN IN COMMAND RESPONSE
NOT FORMATTED CORRECTLY
System action
The command is discarded and processing continues. Explanation
The domain provided by the DM keyword of a response
Operator response is not formatted correctly.
System action

Contact the system programmer. This message appears in association with DUI4333E.
It indicates that critical class information cannot be
System programmer response retrieved.

System action
assistance. GMFHS ends.
DUI4332E EXTRANEOUS DATA FOUND IN
THE COMMAND RESPONSE Operator response
Explanation
A command response had additional data that was System programmer response
unnecessary. More information regarding the failure is written in the
System action assistance.
The command is discarded and processing continues. DUI4335E NON-CRITICAL CLASS
INFORMATION CANNOT BE
Operator response RETRIEVED — GMFHS
TERMINATING
Explanation
This message appears in association with DUI4333E.
More information regarding the failure is written in the It indicates that non-critical class information cannot
GMFHS output logs. Contact IBM Software Support for be retrieved.
assistance.
DUI4333E ERROR RETRIEVING INITIAL System action
CLASS AND FIELD IDENTIFIER Processing continues.
INFORMATION FROM RODM
Operator response
Explanation
A class or field identifier that is used by GMFHS cannot
be retrieved from RODM at GMFHS initialization.
System action More information regarding the failure is written in the
If the class or field is a critical class or field, GMFHS assistance.
ends. Otherwise, processing continues.
DUI4336E CRITICAL FIELD INFORMATION
Operator response CANNOT BE RETRIEVED

Explanation
System programmer response This message appears in association with DUI4333E.

It indicates that critical filed information cannot be
More information regarding the failure is written in the retrieved.
assistance.
System action
DUI4334E CRITICAL CLASS INFORMATION GMFHS ends.
CANNOT BE RETRIEVED — GMFHS
TERIMATING
Operator response

More information regarding the failure is written in the A method failed during an exception view request.
assistance. System action
DUI4337E NON-CRITICAL FIELD Processing continues.
INFORMATION CANNOT BE
RETRIEVED Operator response
This message appears in association with DUI4333E. System programmer response

It indicates that non-critical field information cannot
be retrieved. More information regarding the failure is written in the
System action Support for assistance.
Processing continues. DUI4340E NETWORK VIEW REQUEST COULD

NOT BE PROCESSED
Operator response
Explanation
A method failed during a Network view request.
System action
GMFHS output logs. Contact IBM Software Support for Processing continues.
assistance.
Operator response
DUI4338E ELEMENT MANAGER SESSION
ESTABLISHMENT REQUEST TIMED Contact the system programmer.
OUT FOR DOMAIN domain
The NETCMD subtask did not receive a response to a GMFHS and RODM output logs. Contact IBM Software
session protocol request within a specified period of Support for assistance.
time.
DUI4341E UNABLE TO INVOKE METHOD
Message Variables method
domain
Specifies the domain to which the command was Explanation
sent. This message appears with DUI4339E , DUI4340E,
DUI4342E, DUI4343E, DUI4344E. This message
System action indicates that the indicated method cannot be
invoked.
Message Variables
Operator response method
Contact the system programmer. Specifies the method that failed
More information regarding the failure is written in the Processing continues.

DUI4339E EXCEPTION VIEW REQUEST Contact the system programmer.
COULD NOT BE PROCESSED

More information regarding the failure is written in the Contact the system programmer.
Support for assistance. System programmer response
DUI4342E FAST PATH VIEW REQUEST COULD More information regarding the failure is written in the
NOT BE PROCESSED GMFHS and RODM output logs. Contact IBM Software
Explanation
DUI4345E SESSION PROTOCOL RESPONSE
A method failed during a Fast Path view request. NOT SUPPORTED

Processing continues. The session protocol response is not supported for
this type of domain session.
Operator response
System action
Operator response
GMFHS and RODM output logs. Contact IBM Software Contact the system programmer.
DUI4343E MORE DETAIL RESOURCE VIEW System programmer response
REQUEST COULD NOT BE More information regarding the failure is written in the
PROCESSED GMFHS and RODM output logs. Contact IBM Software
Explanation
DUI4346E START UPDATES REQUEST COULD
A method failed during a More Detail Resource view NOT BE PROCESSED
request.
Explanation
System action
A method failed during a Start Updates view request.
System action
Operator response
Operator response
GMFHS and RODM output logs. Contact IBM Software System programmer response
DUI4344E GLOBAL FIND VIEW REQUEST GMFHS and RODM output logs. Contact IBM Software
COULD NOT BE PROCESSED Support for assistance.
DUI4347E STOP UPDATES REQUEST COULD
Explanation
NOT BE PROCESSED
A method failed during a Global Find view request.
Explanation
System action
A method failed during a Stop Updates view request.

Processing continues. A method failed during a Get Name Map request.

Contact the system programmer. Processing continues.

More information regarding the failure is written in the Contact the system programmer.
DUI4348E NETWORK/MDR VIEW LIST More information regarding the failure is written in the
REQUEST COULD NOT BE GMFHS and RODM output logs. Contact IBM Software
PROCESSED Support for assistance.
DUI4351E UNABLE TO RETRIEVE THE ID OF
Explanation
THE method METHOD
A method failed during a Network/MDR view list
An attempt to retrieve the id of the specified method
System action
failed.
Message Variables
Operator response method

Specifies the method whose ID cannot be
Contact the system programmer. retrieved.

Operator response
DUI4349E GET VIEW (BY RESOURCE LIST) Contact the system programmer.
REQUEST COULD NOT BE
PROCESSED
A method failed during a Get View (by resource list) Support for assistance.
view request.
DUI4352E EXCEPTION VIEW REQUEST
System action COULD NOT BE PROCESSED
Explanation
Operator response A method failed during an Exception view request.

System action
System programmer response Processing continues.

Operator response
Support for assistance. Contact the system programmer.
DUI4350E GET NAME MAP REQUEST COULD
NOT BE PROCESSED

Support for assistance. Operator response
DUI4353E NAME TO ID REQUEST COULD NOT Contact the system programmer.
BE PROCESSED
Explanation
None; GMFHS will cleanup from the missing session
A method failed during a Name to ID request. release normally.
DUI4356E CLOSE VIEW REQUEST COULD
System action
NOT BE PROCESSED
Explanation
Operator response
A method failed during a Close View request.
System action
GMFHS and RODM output logs. Contact IBM Software Operator response
DUI4354E GET DRT REQUEST COULD NOT BE
PROCESSED System programmer response

A method failed during a Get Display Resource Type Support for assistance.
request.
DUI4357E FAILURE RETRIEVING VIEW
NOTIFICATION NEGATIVE ACK
System action
FROM DATA SERVER
Explanation
Operator response
A negative acknowledgment view notification from a
Contact the system programmer. data server cannot be retrieved from the View
Manager task internal data queue.
System action
GMFHS and RODM output logs. Contact IBM Software Processing continues.
DUI4355E SESSION RELEASE MISSING FOR Operator response
GRAPHIC DATA SERVER LU server Contact the system programmer.

A method failed during a Get Display Resource Type This is an internal error. Contact IBM Software Support
request. for assistance.
Message Variables DUI4358E DATA SERVER LU NAME luname IS
server NOT KNOWN TO VIEW MANAGER
Specifies the server for which the session release SUBTASK
was not received.

The data server specified by the luname is not The NETCMD subtask has an incorrect transport
currently in session with GMFHS. protocol type in the saved command block.
Message Variables
System action
luname
Specifies the luname which cannot be found in the The command is discarded and processing continues.
View Manager subtask list.
Operator response
System action Contact the system programmer.
Operator response This is an internal error. Contact IBM Software Support
Contact the system programmer. for assistance.
DUI4361E NEGATIVE PROTOCOL
System programmer response ACKNOWLEDGMENT FROM THE
COS GATEWAY
This is probably because of a timing window in which
the session was ended at the same time that a view
notification request was issued. This message can be Explanation
ignored. A command sent to the COS gateway resulted in a
DUI4359E METHOD method ERROR negative protocol acknowledgment from the gateway.
(returncode/reasoncode),INVOKED
FROM RESOURCE TRAITS System action
MANAGER SUBTASK
Explanation
Operator response
The data server specified by the luname is not
currently in session with GMFHS.
method More information regarding the failure is written in the
Specifies the method returning the error. GMFHS and RODM output logs. If the problem cannot
returncode be determined from this information, contact IBM
Specifies the RODM return code. Software Support for assistance.
reasoncode DUI4362E PPI TRANSPORT COMMAND
Specifies the RODM reason code. RESPONSE FAILURE -- MAJOR
VECTOR vector PARSING ERROR
System action
Processing continues. Explanation
A command response from the PPI transport did not
Operator response contain a valid major vector.
Contact the system programmer. Message Variables
vector
System programmer response Specifies the vector in error.
GMFHS and RODM output logs. Contact IBM Software System action
UNKNOWN TRANSPORT TYPE

Operator response domain
Specifies the domain on which the command was
to execute.
System programmer response subtask

Specifies the subtask from which the command
More information regarding the failure is written in the response was sent.
GMFHS and RODM output logs. If the problem cannot
be determined from this information, contact IBM System action
DUI4363E command COMMAND FOR resource
FROM subtask HAS TIMED OUT
Operator response
A command response for the specific resource has

timed out. The command response originated from the
specific subtask. More information regarding the failure is written in the
GMFHS output logs. If the problem cannot be
Message Variables
determined from this information, contact IBM
command Software Support for assistance.
Specifies the command that timed out.
DUI4365E command COMMAND FOR resource
resource HAS TIMED OUT
Specifies the resource on which the command was
to execute.
Explanation
subtask
Specifies the subtask from which the command A command response for the specific resource has
response was sent. timed out. No information about the originating task is
provided.
The command is discarded and processing continues. command
Operator response resource
Specifies the resource on which the command was
to execute.

System action
GMFHS output logs. If the problem cannot be
Software Support for assistance. Operator response
DUI4364E command COMMAND FOR DOMAIN Contact the system programmer.

domain FROM subtask HAS TIMED
OUT System programmer response
Explanation GMFHS output logs. If the problem cannot be
A command response for the specific domain has determined from this information, contact IBM
timed out. The command response originated from the Software Support for assistance.
specific subtask. DUI4366E DOMAIN UNKNOWN -- EXECUTE
Message Variables CONFIG NETWORK COMMAND
command
Explanation
The domain object for a command cannot be found.
The Config Network command must be done whether

new domains have been added to RODM since the last DUI4369E PPI TRANSPORT COMMAND
time GMFHS has been started. RESPONSE FAILURE -- MAJOR
VECTOR vector UNKNOWN
System action
Explanation
Operator response contain a known major vector.
Contact the system programmer. Message Variables

vector
System programmer response Specifies the vector in error.
Execute the CONFIG NETWORK command. If the
problem for this domain persists, contact IBM System action
Software Support. The command is discarded and processing continues.
UNKNOWN TRANSPORT TYPE Operator response
Explanation
The NETCMD subtask has an incorrect transport System programmer response
protocol type in the saved command block.
System action be determined from this information, contact IBM
The command is discarded and processing continues. Software Support for assistance.
DUI4370E IPC WAS UNABLE TO DELIVER
Operator response COMMAND TO PPI GATEWAY
Explanation
System programmer response A command sent to the PPI transport cannot be sent
This is an internal error. Contact IBM Software Support across the PPI.
for assistance.
System action
DUI4368E RESOURCE TYPE PROFILE
UPDATE METHOD FAILED The command is discarded and processing continues.
The NETCMD subtask received an error from the Contact the system programmer.
aggregation profile update method.
System action More information regarding the failure is written in the
Processing continues. GMFHS and RODM output logs. If the problem cannot
be determined from this information, contact IBM
Operator response
DUI4371E RODM CHECKPOINT REQUEST
FAILED
Explanation
GMFHS and RODM output logs. Contact IBM Software The network configuration subtask attempted to
Support for more information. checkpoint RODM. The checkpoint request failed.

System action DUI4374E subtask REPORTS THAT THE
NETWORK CONFIGURATION
The checkpoint is ignored, processing continues.
COMMAND WAS REJECTED
Operator response
Explanation
A command that originated with the network
configuration subtask has been rejected by the
System programmer response indicated subtask for an unknown reason.
More information regarding the failure is written in the Message Variables
be determined from this information, contact IBM subtask
Software Support for assistance. Specifies the subtask reporting the error.
DUI4372E COMMUNICATIONS SESSION

System action
WITH ELEMENT MANAGER LOST
Explanation
Operator response
The session with the element management system of
a particular domain is no longer active. Contact the system programmer.

Processing continues. More information regarding the failure may be written
in the GMFHS and RODM output logs. If the problem
Operator response cannot be determined from this information, contact
DUI4375E FIELD TYPE ERROR IN NON-SNA
System programmer response DOMAIN OBJECT
The session will be reestablished after a timeout. If Explanation

the session cannot be reestablished, contact IBM
Software Support. The ContainsResource field on a non-SNA domain
object is not of type ObjectLinkList.
DUI4373E NETWORK CONFIGURATION
COMMAND RETRY LIMIT
System action
EXCEEDED
Explanation
Operator response
A command that originated with the network
configuration subtask has been retried the maximum Contact the system programmer.
number of times.
System action
Change the definition in the RODM data model and
Processing continues. reload the data model. Contact IBM Software Support
for assistance.
Operator response DUI4376E EXPECTED NON-SNA DOMAIN
Contact the system programmer. OBJECT IS MISSING

More information regarding the failure may be written A non-SNA domain object no longer exists in RODM.
cannot be determined from this information, contact System action

Contact the system programmer. A non-SNA domain object is missing it's DisplayStatus
field.
System action
More information regarding the failure may be written
in the GMFHS and RODM output logs. If the problem Processing continues.
cannot be determined from this information, contact
IBM Software Support for assistance. Operator response
DUI4377E FIELD TYPE ERROR IN NON-SNA Contact the system programmer.
DOMAIN OBJECT
Explanation
The DisplayStatus field on a non-SNA domain object is reload the data model. Contact IBM Software Support
not of type Integer. for assistance.
DUI4380E NON-SNA DOMAIN OBJECT CLASS
System action
DEFINITION ERROR
Explanation
Operator response
The non-SNA domain object class is not defined
Contact the system programmer. correctly.

Change the definition in the RODM data model and Processing continues.
reload the data model. Contact IBM Software Support
for assistance. Operator response
DUI4378E EXPECTED NON-SNA DOMAIN Contact the system programmer.
OBJECT IS MISSING
Explanation
A non-SNA domain object no longer exists in RODM. reload the data model. Contact IBM Software Support
for assistance.
System action
DUI4381E MANAGER STATUS UPDATE
Processing continues. FAILED

Contact the system programmer. The network configuration subtask attempted to build
the Manager Status message and failed.
System action
in the GMFHS and RODM output logs. If the problem Processing continues.
IBM Software Support for assistance. Operator response
DUI4379E NON-SNA DOMAIN OBJECT DOES Contact the system programmer.
NOT HAVE A DISPLAYSTATUS
FIELD System programmer response
for assistance.

DUI4382E UNRECOGNIZED CONSOLE Operator response
COMMAND RECEIVED Contact the system programmer.
Explanation
The network configuration subtask received a Change the definition in the RODM data model and
command which it did not understand.
reload the data model. Contact IBM Software Support
for assistance.
System action
DUI4386E GMFHS WILL NOT MONITOR
Processing continues. STATUS FOR THE TOPOLOGY
MANAGER
Operator response
This message appears in combination with the
System programmer response following messages and indicates that the a particular
manager will not be monitored.
for assistance.
System action
DUI4383E OBJECT NOT INCLUDED IN
STATUS SOLICITATION FOR Processing continues.
DOMAIN: domain
Operator response
The network configuration subtask cannot generate a
status solicitation for the specified domain because of System programmer response
an error in the domain object. More information regarding the failure may be written
Message Variables in the GMFHS and RODM output logs. If the problem
domain IBM Software Support for assistance.
Specifies the domain in error.
DUI4387E SOME OF THE GDA
System action CHARACTERISTICS WERE
MASKED OUT
Explanation
Operator response
This message appears in combination with DUI4388E
Contact the system programmer. and indicates that some of the domain characteristics
from the DomainCharacterstics field have been
System programmer response masked because of a protocol mismatch.
reload the data model. Contact IBM Software Support System action
for assistance. Processing continues.
DUI4384E MANAGER STATUS UPDATE
FAILED -- NMG CLASS ERROR Operator response
Explanation
DUI4388E TRANSPORT PROTOCOL WAS NOT
The network configuration subtask attempted to build PPI, OST, COS, OR IP
the Manager Status message and failed because of an
error in the NMG Class definition.
Explanation
System action This message appears in combination with DUI4387E

and indicates that some of the domain characteristics

from the DomainCharacterstics field have been Operator response
masked because of a protocol mismatch.
System action
Turn on the requested tracing.
Operator response DUI4391E subtask REPORTS THAT A

PROCESS FAILED
DUI4389E destsubtask REJECTED A Explanation
REQUEST FROM origsubtask
The reporting subtask cannot complete a request
because of a process failure.
Explanation
Message Variables
This message appears in combination with DUI4387E
and indicates that some of the domain characteristics subtask
from the DomainCharacteristics field have been Specifies the reporting subtask.
masked because of a protocol mismatch.
System action
Message Variables
destsubtask
Specifies the destination subtask for the request.
Operator response
origsubtask
Specifies the originating subtask for the request. Contact the system programmer.

Processing continues. Contact IBM Software Support for assistance.
DUI4392E subtask REPORTS THAT THERE
Operator response WAS NO OBJECT
Explanation
System programmer response The reporting subtask cannot complete a request
Contact IBM Software Support for assistance. because of not being able to find the target object in
RODM.
DUI4390E TURN TRACING ON FOR
origsubtask AND destsubtask FOR Message Variables
MORE INFORMATION subtask
Specifies the reporting subtask.
Explanation
This message appears in combination with DUI4374E System action
and DUI4395E. Processing continues.
Message Variables
Operator response
destsubtask
Specifies the destination subtask for the request. Contact the system programmer.
origsubtask
Specifies the originating subtask for the request. System programmer response
System action
DUI4393E subtask REPORTS THAT THE
Processing continues. COMMAND WAS NOT
AUTHORIZED

The reporting subtask cannot complete a request Contact IBM Software Support for assistance.
because of the command not being authorized.
DUI4396E WAITING FOR SESSION WITH
Message Variables SCOPE CHECKER
subtask
Specifies the reporting subtask. Explanation
The Network Configuration task must have a session
System action with the Scope Checker optional task to begin status
solicitation for non-SNA domains
System action
Operator response
Operator response
DUI4397E NON-SNA SESSION
DUI4394E subtask REPORTS THAT THE
ESTABLISHMENT HAS NOT
COMMAND IS NOT SUPPORTED
COMPLETED
Explanation
Explanation
The reporting subtask cannot complete a request
This message accompanies message DUI4396E
because of the command not being supported.
subtask Processing continues.
Specifies the reporting subtask.
Operator response
System action
DUI4398E THIS WILL RESUME WHEN THE
Operator response SCOPE CHECKER SESSION IS UP
System programmer response This message accompanies message DUI4396E
Contact IBM Software Support for assistance. System action

DUI4395E COMMAND CANNOT BE RETRIED Processing continues.

This is an informational message that comes out with Contact the system programmer.
other messages indicating that a status solicitation
command from the network configuration subtask DUI4399E THE DOMAIN domain WAS NOT
failed to execute successfully. FOUND IN RODM - CONFIG
DOMAIN CANNOT COMPLETE
System action
Explanation
A CONFIG DOMAIN=domain command was issued,
Operator response and the specified domain cannot be found in RODM.
The domain in question was deleted from RODM prior
Contact the system programmer. to the CONFIG DOMAIN=domaincommand.

domain Reissue the command with another domain name, or
Specifies the domain that was not found. add the domain to RODM and issue a CONFIG
NETWORK command.
System action DUI4402E RODM QUERY FAILED (returncode/
Processing continues. resasoncode). FIELD: field, CLASS:
class
Operator response
Explanation
This message accompanies message DUI3386E, and
indicates the RODM query failure that caused the
status monitoring failure.
Reissue the command with another domain name, or
Message Variables
add the domain to RODM and issue a CONFIG
NETWORK command. returncode
DUI4400E ALL TRANSACTIONS INVOLVING
THIS DOMAIN ARE SUSPECT. THE reasoncode
DOMAIN WAS IN RODM BUT NOW Specifies the RODM reason code.
IS NOT field
Specifies the field for which RODM change was
Explanation requested.
This message accompanies message DUI3399E. class
Specifies the class for which RODM change was
requested.
System action
Operator response
Contact the system programmer. Operator response
Reissue the command with another domain name, or System programmer response
add the domain to RODM and issue a CONFIG
NETWORK command. More information regarding the failure may be written
DUI4401E IT IS RECOMMENDED THAT A cannot be determined from this information, contact
GMFHS CONFIG NETWORK BE IBM Software Support for assistance.
DONE
DUI4403E RODM DATA TYPE NOT VALID.
FIELD: field, CLASS: class
Explanation
This message accompanies message DUI3399E. Explanation
This message accompanies message DUI3386E, and
System action
indicates the RODM data type error that caused the
Processing continues. status monitoring failure.
Message Variables
Operator response
field
Contact the system programmer. Specifies the field for which RODM change was
requested.
class
Specifies the class for which RODM change was
requested.

Processing continues. More information regarding the failure may be written
in the GMFHS and RODM output logs.
Operator response DUI4406E COMMAND RESPONSE FROM PPI
Contact the system programmer. GATEWAY MISSING TEXT DATA
PARAMETER MAJOR VECTOR
Explanation
in the GMFHS and RODM output logs. If the problem A command response from the PPI transport did not
cannot be determined from this information, contact contain a Text Data Parameter major vector.
System action
DUI4404E ERROR ENCOUNTERED IN
PROCESSING A REQUEST TO Command is discarded and processing continues.
UPDATE THE GLOBAL
UNKNOWN_THRESHOLD TO value. Operator response
Explanation
A RODM error was received in the attempt to change System programmer response
the UnknownThreshold field in RODM.
This is a problem with the PPI gateway application.
Message Variables The gateway application must provide this major
value vector on all command responses.
Requested unknown threshold value. DUI4407E objectname IN CLASS classname
IS NOT LINKED TO A linkclass
System action OBJECT
Explanation
Operator response The Domain object link of the object specified by
Contact the system programmer. classname and objectname is not linked to an
appropriate class object.
More information regarding the failure may be written objectname
in the GMFHS and RODM output logs. If the problem Specifies the object name in the link error.
cannot be determined from this information, contact classname
IBM Software Support for assistance. Specifies the class name in the link error.
DUI4405E MAXIMUM RESPONSE TEXT SIZE linkclass
REACHED Specifies the class which the object is to be linked
with.
Explanation
System action
A response to a DOMP010 presentation protocol
command contained too much data in the response Command is discarded and processing continues.
text area.
Operator response
System action Contact the system programmer.
Command is discarded and processing continues.
Operator response Change the specified object to have a Domain link to
Contact the system programmer. an object in the correct class. Contact IBM Software

DUI4408E OBJECT NAME objname TOO LONG IS INCONSISTENT WITH THE
FOR COMMAND FOR DOMAIN emdname NAME OF THE classtype
domain OBJECT IT IS LINKED TO
The specified object name, when added to a The specified object from the specified class has an
command, makes the command too long to be issued. EMDomain field that is not consistent with the Domain
object to which it is linked. The EMDomain field must
Message Variables be the prefix of the MyName field of the Domain
objname object.
Specifies the object name of the resource that Message Variables
makes the command too long.
objectname
domain
Specifies the objectname of the target resource.
Specifies the domain to which the command is to
be issued. classname
Specifies the class name of the target resource.
System action emdname
Specifies the EMDomain field name from the target
resource.
classtype
Operator response
Specifies the type of class of the Domain object.
System action
This command cannot be issued with this object name.
Shorten the object name if possible. Contact IBM Operator response
DUI4409E COMMAND TEXT FOR DOMAIN
domain IS TOO LONG
Explanation Correct either the Domain object MyName, or the

EMDomain field of the linking object. Contact IBM
The command text for a domain makes the command Software Support for assistance.
too long to be issued.
DUI4411E DATA CORRELATION SUBVECTOR
Message Variables NOT FOUND IN REPLY TO
domain EXECUTE VECTOR
Specifies the domain to which the command is to
be issued. Explanation
System action contain a correlation subvector.
System action
Operator response Command is discarded and processing continues.
Operator response
System programmer response Contact the system programmer.
This command cannot be issued with this command
text. Shorten the command text if possible. Contact System programmer response
This is a problem with the PPI gateway application.
DUI4410E THE MYNAME VALUE OF The gateway application must provide this subvector
objectname IN CLASS objectclass on all command responses.

DUI4412E PCID SUBFIELD IS MISSING OR Operator response
INVALID REPLY TO EXECUTE Contact the system programmer.
VECTOR

Explanation
This error may be because of a problem with the
element management system. Contact IBM Software
contain a correlation subvector with a valid PCID Support for assistance.
subfield.
DUI4416E COMMAND NOT KNOWN TO THE
System action DOMAIN'S ELEMENT MANAGER

Explanation
Operator response A network configuration solicitation command failed

because of the command not being recognized by the
Contact the system programmer. element management system.

This is a problem with the PPI gateway application. Command is discarded and processing continues.
The gateway application must provide this subfield on
all command responses.
Operator response
DUI4414E SOLICITATION COMMAND RETRY Contact the system programmer.
LIMIT EXCEEDED
Explanation
A network configuration solicitation command failed element management system. Contact IBM Software
because of the retry limit for the command being Support for assistance.
exceeded.
DUI4417E COMMAND REJECTED BY
System action ELEMENT MANAGER : BAD
PARAMETERS
Explanation
Operator response
A network configuration solicitation command failed
Contact the system programmer. because of the command having bad command
parameters.
This error may be because of a problem with the System action
element management system. Contact IBM Software Command is discarded and processing continues.
DUI4415E NO SESSION WITH THE DOMAIN'S Operator response
ELEMENT MANAGER Contact the system programmer.

A network configuration solicitation command failed This error may be because of a problem with the
because of the session with the domains element element management system. Contact IBM Software
manager having been lost Support for assistance.
System action DUI4418E COMMAND NOT ALLOWED BY THE

DOMAIN'S ELEMENT MANAGER

because of the command not being valid by the element management system. Contact IBM Software
element management system. Support for assistance.
DUI4421E COMMAND CANCELLED BY THE
System action DOMAIN'S ELEMENT MANAGER
Explanation
Contact the system programmer. because of the command being cancelled by the
element management system.
System action
Operator response
DUI4419E COMMAND NOT CURRENTLY
ALLOWED BY THE DOMAIN'S Contact the system programmer.
ELEMENT MANAGER
Explanation
because of the command being temporarily disallowed Support for assistance.
by the element management system.
DUI4422E COMMAND PREEMPTED BY THE
System action
Command is discarded and processing continues. Explanation
Operator response because of the command being preempted by the
Contact the system programmer. element management system.
This error may be because of a problem with the Command is discarded and processing continues.
Support for assistance. Operator response
DUI4420E COMMAND ABORTED BY THE Contact the system programmer.
Explanation
because of the command being cancelled by the Support for assistance.
element management system.
DUI4423E COMMAND FAILED BY THE
System action
Command is discarded and processing continues. Explanation
Operator response because of the command being failed by the element
Contact the system programmer. management system.

System action DUI4426E COMMAND CONTAINS TOO MANY
RESOURCE NAMES
Explanation
Operator response
because of the command containing too many
resource names.
DUI4424E THE ELEMENT MANAGER HAD Operator response
INSUFFICIENT RESOURCES TO
PROCESS THE COMMAND Contact the system programmer.
because of the element management system not element management system. Contact IBM Software
having enough system resources to process the Support for assistance.
command. DUI4427E COMMAND NOT SUPPORTED BY
THE DOMAIN'S ELEMENT
System action MANAGER
Explanation
Contact the system programmer. because of the command not being supported by the
domain's element management system.
System action
Operator response
DUI4425E COMMAND TIMED OUT BY THE
DOMAIN'S ELEMENT MANAGER Contact the system programmer.
because of the element management system timing element management system. Contact IBM Software
out the command. Support for assistance.
DUI4428E INCORRECT LOGIN REPORTED BY
System action THE DOMAIN'S ELEMENT
Command is discarded and processing continues. MANAGER
Contact the system programmer. A network configuration solicitation command failed

because of an incorrect login at the domain's element
management system.
Support for assistance. Command is discarded and processing continues.

Contact the system programmer. A network configuration solicitation command failed
because of the command response being incorrect for
System programmer response the gateway.

System action
element management system. ContactIBM Software
Support for assistance. Command is discarded and processing continues.
DUI4429E INSUFFICIENT PRIVILEGE FOR
THE GATEWAY TO RUN THIS Operator response
COMMAND Contact the system programmer.

because of insufficient privilege for the gateway to run element management system. Contact IBM Software
the command at the domain's element management Support for assistance.
system.
DUI4432E A VALUE OF ZERO (0) FOR THE
TRACEPAGES PARAMETER IS NO
System action
LONGER SUPPORTED. THE
Command is discarded and processing continues. DEFAULT VALUE OF 100 WILL BE
USED INSTEAD.
Operator response
Explanation
Zero is no longer a valid value for the TRACEPAGES
System programmer response command. You cannot use the TRACEPAGES
command to enable or disable internal tracing. If zero
This error may be because of a problem with the (0) is specified, the value 100 is used instead.
System action
DUI4430E COMMAND'S TARGET RESOURCE TRACEPAGES is set to 100 and processing continues.
IS UNKNOWN BY RODM OR THE
GATEWAY
Operator response
because of the command's target resource being System programmer response
unknown to the element management system. Remove or comment out the TRACEPAGES statement
in initialization member DUIGINIT, or change its value
System action from zero (0) to 100.
Command is discarded and processing continues. DUI4433E POSSIBLE CONSOLE FLOOD FROM
SUBTASK subtask. CONSOLE
Operator response MESSAGES FROM THIS SUBTASK
ARE SUSPENDED FOR 30
Contact the system programmer. SECONDS.

This error may be because of a problem with the This message occurs when GMFHS detects a possible
element management system. Contact IBM Software flood of console messages from a subtask. GMFHS
Support for assistance. disables console messages from a subtask if more
DUI4431E COMMAND RESPONSE DATA IS than 30 console messages from the subtask are
NOT VALID generated within a 1 second interval. All messages
continue to be sent to any active output logs,

regardless of whether they are suspended from System programmer response
appearing on the console.
If the condition persists, contact IBM Software
Message Variables Support.
subtask
The subtask generating the console messages.

Chapter 2. DWO Prefix Messages
DWO prefix messages are sent to the NetView terminal operator or the authorized message receiver. If an
authorized message receiver is not defined in the system or is not logged on, the messages destined for
the authorized message receiver are sent to the system console operator.
DWO000I COMMAND FACILITY MESSAGE System programmer response
msgid ISSUED BUT DOES NOT Interpret the sense codes and make the appropriate
EXIST IN MESSAGE TABLE changes. Refer to the z/OS Communications Server
DSIMDMV - CALL IGNORED library for more information.
Explanation DWO002I VTAM FAILURE FUNCTION =

function RTNCD = X'vtamrcd'
The specified message number does not exist in the FDBK2 = X'vtamfb' SENSE =
message table. X'vtamsens' MODNAME = module
Message Variables
Explanation
msgid
The message number. A request has been rejected by VTAM, and a
corresponding request ID is not available. Use the
System action RCFB command list for a description of the return code
and feedback code. Use the SENSE command list for a
The NetView program ignores the message call and description of the sense code.
continues processing.
Message Variables
Operator response function
Specifies which VTAM service failed.
vtamrcd
The VTAM internal return code.
vtamfb
Contact IBM Software Support. The VTAM internal feedback code.
DWO001I REQID reqid : NEGATIVE vtamsens
RESPONSE RECEIVED WITH The VTAM internal sense code.
SENSE CODE = X'code'
module
The module name that issued this message.
Explanation
The specified request has been rejected by VTAM. System action
Message Variables The request is not processed.
reqid
The ID of the request to which this message is Operator response
responding. Determine if the request was sent to the correct PU. If
code the request was correct, notify the system
The sense code from VTAM. programmer.

The request is not processed. Use the RCFB and SENSE command lists to determine
the meaning of the return/feedback and sense codes.
Operator response See the device specific documentation for the meaning
of the user sense data.
DWO003I VPDTASK OPTIONS ARE AS
FOLLOWS : ACBNAME = acbname

SNAPRQ = snapopt VPDWAIT = Explanation
vpdwait VPDREQ = vpdreq
A VTAM error occurred during the processing of a
VPDSTOR = vpdstor
VPDCMD command or during the initialization of
VPDTASK.
Explanation
Message Variables
This message is the response to the VPDCMD
OPTIONS or the VPDCMD SNAP ON | OFF command. It function
lists the current values of the VPDTASK options. Specifies which VTAM service failed.
code
Message Variables
The problem analysis codes.
acbname module
The ACBNAME specified on the VPDINIT definition The module that issued the message.
statement.
snapopt System action
Indicates whether the trace for the SNAP record is
ON or OFF. If the error was detected during initialization,
VPDTASK is not started. If the error was detected
vpdwait
while processing a VPDCMD command, the request is
The maximum waiting period for a VPDTASK
not processed.
before a time-out.
vpdreq Operator response
The maximum number of simultaneous requests
specified for VPDTASK. Contact the system programmer.
vpdstor
The storage estimate that is specified on the System programmer response
VPDINIT definition statement. Determine whether the values for registers 0 and 15
DWO004I ACBNAME NOT FOUND - VPDTASK are acceptable. If not, correct the values and start
INITIALIZATION TERMINATED VPDTASK again. Refer to the z/OS Communications
Server library for more information.
Explanation DWO006I task IS READY FOR WORK
The VPDTASK initialization routines cannot find the (ACBNAME = acbname SNAPRQ =
ACBNAME specified on the VPDINIT definition snapopt VPDWAIT = vpdwait
statement. VPDREQ = vpdreq VPDSTOR =
vpdstor )
System action
Explanation
VPDTASK does not start.
VPDTASK has successfully initialized.
Operator response Message Variables
Contact the system programmer. task

The task name of the VPDTASK.
System programmer response acbname
The ACBNAME specified on the VPDINIT definition
Verify that the ACBNAME is specified in VTAM APPLS statement.
definition member. Then ensure that the ACBNAME on
the VPDINIT statement in the DSIVPARM member of snapopt
DSIPARM is the same as the ACBNAME specified in Indicates whether the trace for the SNAP record is
VTAM APPLS definition member. to be turned on.
vpdwait
DWO005I VTAM SERVICES FAILURE.
The maximum waiting period for a VPDTASK
FUNCTION = function REG15 =
before a time-out.
X'code' REG0 = X'code' MODNAME
= module vpdreq
The maximum number of simultaneous requests
specified for VPDTASK.

vpdstor vtamrcd
The storage estimate that is specified on the The VTAM internal return code.
VPDINIT definition statement. vtamfb
The VTAM internal feedback code.
System action vtamsens
Processing continues. The VTAM internal sense code.
DWO007I REQID reqid TERMINATED BY module

TIMEOUT The module that issued this message.
A VPD request was ignored because it was waiting The request is not processed.
longer than the value specified for the VPDWAIT on
the VPDINIT definition statement, or a link failure Operator response
occurred after the request was accepted. Determine if the request was sent to the correct PU. If
Message Variables the request was correct, notify the system
programmer.
reqid
The ID of the request to which this message is
responding. System programmer response
Use the RCFB and SENSE command lists to interpret
System action return, feedback, and sense codes and make the
appropriate changes.
The request is not processed.
DWO009I REQUEST 'keyword' ACCEPTED
Operator response FOR puname , REQID = reqid
If a link failure occurred, retry the VPD request when

Explanation
the link comes up. If a link failure did not occur,
contact the system programmer. VTAM accepted your request for vital product data
from the specified PU.
Ensure that the specified time-out value (VPDWAIT) keyword
allows the network sufficient time to transport the The keyword (OWN or ALL) you used on the
replies. VPDCMD command.
DWO008I REQID reqid VTAM FAILURE puname
FUNCTION = function RTNCD = The PUNAME specified in your command.
X'vtamrcd' FDBK2 = X'vtamfb' reqid
SENSE = X'vtamsens' MODNAME = The ID of the request to which this message is
module responding.
Explanation DWO010I INVALID REQUEST QUEUED TO

task
A request has been rejected by VTAM. Use the RCFB
command list for a description of the return code and Explanation
feedback code. Use the SENSE command list for a
description of the sense code. An incorrect request was queued to VPDTASK or
DSIATOPT.
Message Variables
Message Variables
reqid
The ID of the request to which this message is task
responding. The task name of VPDTASK or DSIATOPT
function
The failed VTAM service. System action
Chapter 2. DWO Prefix Messages 145

Contact the system programmer. The RU is saved if the SNAP option, which was
specified in VPDINIT definition statement, and the
System programmer response NetView internal trace are on. If not, the RU needs to
be created again with those options on. Analyze the
Verify that user-written requests are not being queued SNAP record received using Systems Network
to VPDTASK or DSIATOPT. Architecture Formats and the vendor device
DWO011I UNKNOWN RU RECEIVED - documentation. For an IBM device, keep the SNAP and
IGNORED contact IBM Software Support.
DWO013I CDE CONTROL BLOCK CHAIN
Explanation MODIFIED WHILE DISPMOD WAS
RUNNING, RETRY.
An unexpected RU was delivered by VTAM to
VPDTASK.
Explanation
System action You entered a DISPMOD command, but while the
command was running the CDE control block chain
The received RU is ignored.
was modified. The DISPMOD command cannot
continue.
Operator response
Contact the system programmer. System action
The command stops running.
The RU is saved if the SNAP option, which was Operator response
specified in the VPDINIT definition statement, and the
Enter the command again.
NetView internal trace are on. If not, the RU needs to
be created again with those options on. Print the SNAP DWO014I REQID reqid COMPLETED
record and ensure you did not start VPDTASK with an
ACBNAME that VTAM knows as manager for Explanation
unsolicited RUs. Keep the SNAP and contact IBM
Software Support. The VPD request is complete.
DWO012I REQID reqid : UNKNOWN MAJOR Message Variables

VECTOR X'vector' RECEIVED - reqid
IGNORED The ID of the request to which this message is
responding.
Explanation
An unexpected major vector was returned for a VPD System action
request. Processing continues.
Message Variables DWO015I REQUEST 'keyword' ACCEPTED
reqid FOR ncp pu, LSL = lsl - REQID =
The ID of the request to which this message is reqid
responding.
vector Explanation
The major vector that was received. A request to solicit data from the DCEs was accepted.
Message Variables
System action
keyword
The keyword, DCE, of the VPDCMD command.
Operator response ncp

The name of the NCP specified on the VPDCMD
Contact the system programmer. command.

pu System action
The name of the PU specified on the VPDCMD
command.
lsl
Operator response
The starting link segment level specified on the
VPDCMD command request. Wait until another VPDCMD request completes (look
for a DWO014I message), then submit your request
reqid
again, or contact the system programmer.
responding.
System action Increase the value of VPDREQ on your VPDINIT
definition statement.
DWO018I NETVIEW TRACE IS INACTIVE
DWO016I REQID reqid : REQUESTED LSL
FOR task
'rlsl' IS GREATER THAN THE
NUMBER IN YOUR
CONFIGURATION 'alsl' Explanation
VPD SNAP ON was specified before the NetView
Explanation program internal trace (TRACE) is turned on.
A request soliciting data the from the DCEs specified a Message Variables
level of rlsl while the configuration shows only alsl link
task
segment levels.
The task name of VPDTASK.
Message Variables
reqid System action
The ID of the request to which this message is The request is not processed.
responding.
rlsl Operator response
The link segment level specified in the request.
Activate the TRACE command, then issue the VPDCMD
alsl command.
The actual link segment level in the existing
configuration. DWO019I REQID reqid : VPDSTOR
PARAMETER 'vpdstor' IS
System action INSUFFICIENT. MODNAME =
module
Explanation
Operator response
There is not sufficient storage to receive the vital
Enter the command again with a correct link segment product data. This message is issued to the operator
level. that initiated the request.
DWO017I MAXIMUM NUMBER OF VPD Message Variables
REQUESTS HAS BEEN EXCEEDED -
RETRY LATER. VPDREQ = vpdreq reqid
responding.
Explanation
vpdstor
The VPDTASK is servicing the maximum number of The value specified in VPDSTOR parameter in
simultaneous VPD requests. VPDINIT definition statement.
Message Variables module
The module that issued this message.
vpdreq
The maximum number of simultaneous VPDCMD
command requests allowed. System action

Operator response The VPDTASK initialization routines issue this message
either when the member is not specified in DSIPARM,
or when the member is specified in DSIPARM but does
not contain a statement necessary to start the
System programmer response VPDTASK.
Increase the value of VPDSTOR on your VPDINIT Message Variables
statement and restart the VPDTASK.
mbrid
DWO020I REQID reqid : INVALID RU The name of a DSIPARM data set member, for
RECEIVED - MODNAME = module example, the member name specified for
VPDTASK in the CNMSTASK member.
Explanation
The received RU from the VPD request does not System action
adhere to NMVT architecture. The request or command is not processed.
Message Variables
Operator response
reqid
The ID of the request to which this message is Contact the system programmer.
responding.
module System programmer response
The module that issued this message. Verify that the correct member name is being used.
Verify that the member exists in DSIPARM, and that
System action the member contains lines that specify the required
information.
The received RU is ignored.
For VPDTASK initialization, verify that the correct
Operator response member name is specified in the CNMSTASK member
and that the member contains initialization
Contact the system programmer. parameters.
System programmer response DWO022I TASKNAME TYPE DPR CPU-TIME

N-CPU% S-CPU% MESSAGEQ
To determine the device sending the RU that is not STORAGE-K CMD
valid, print the snap record (the RU is saved in a snap
record if the SNAP option and the NetView trace for
Explanation
VPDTASK are on). The information contained in the
snap record, along with the PU that received the This message is a multiline response to your
request, allows you to identify the device sending the TASKUTIL command. The data includes CPU and
RU that is not valid. Contact the service representative storage usage information. See the NetView online
of the device sending the RU that is not valid. help for more information on the TASKUTIL command.
DWO021I MEMBER mbrid IN DSIPARM IS

System action
EMPTY OR MISSING
Explanation DWO023I INVALID INPUT (input) 'statement'
This message can be issued for one of the following
reasons: Explanation
• The DSIPARM member mbrid either contains no The VPDTASK initialization routine encountered an
lines (is empty) or does not exist. error in the VPDINIT definition statement.
• For some commands, no non-comment lines were Message Variables
found.
input
• A particular type of statement was requested from
One of the following:
the specified member and no statement of the type
requested can be found. STATEMENT
If the DSIVPARM member contains a
statement other than VPDINIT.

KEYWORD System programmer response
If the VPDINIT statement contains an incorrect
keyword.
VALUE DWO026I VPDSTOR PARAMETER 'vpdstor' IS
If the VPDINIT statement contains an incorrect INSUFFICIENT - INCREASE THE
parameter value. VALUE
statement
Explanation
The entire statement coded in DSIVPARM.
There is not sufficient storage to receive vital product
System action data. This message is issued to the starter of
VPDTASK.
VPDTASK does not start.
Message Variables
Operator response vpdstor
The value specified on the VPDSTOR parameter in
the initialization deck.

System action
See the VPDINIT definition statement in the IBM Z
NetView Administration Reference for the correct
syntax of the statement. Correct the initialization
parameters in the VPDINIT definition statement. Operator response
DWO024I YOUR REQUEST CANNOT BE Notify the system programmer.

SATISFIED DUE TO VPDTASK
TERMINATION System programmer response
Increase the value of VPDSTOR on your VPDINIT
Explanation statement and restart the VPDTASK.
You receive this message if VPDTASK ends while one DWO027I num1 VPDPU COMMANDS AND
of your requests is queued. num2 VPDDCE COMMANDS
CREATED
System action
VPDTASK ends. Explanation
DWO025I INTERNAL ERROR IN MODULE A VPDALL command generated VPDPU and VPDDCE
module, FUNCTION = function commands for the PUs and link segments in your
VTAMLST member of DSIVTAM.
The NetView program encountered an internal logic num1
error or a system macro gave an unexpected return The number of VPDPU commands generated.
code. num2
Message Variables The number of VPDDCE commands generated.
module
System action
The module that issued the error.
function Processing continues.
The type of service that failed. DWO028I num1 VPDPU COMMANDS AND
num2 VPDDCE COMMANDS
System action EXECUTED
The request ends.
Explanation
Operator response A VPDALL command was issued with the EXECUTE
Notify the system programmer. option and executed the numbers of VPDPU and

VPDDCE commands specified in the message to be AUTOTEST, or the QRYGLOBL command attempted to
executed. create the specified member, but the command list or
the member is currently being used.
Message Variables
Message Variables
num1
The number of VPDPU commands executed. member
num2 The name of the command list or member that the
The number of VPDDCE commands executed. AUTOCNT, AUTOTBL, AUTOTEST, QRYGLOBL, or
VPDALL command attempted to create
System action ddname
For AUTOTEST, the DD name in which member
Processing continues. cannot be created
DWO029I THE MEMBER 'member' ALREADY
EXISTS, YOU MUST REPLACE IT System action
The command is ignored.
Explanation
A VPDALL command attempted to create a command Operator response
list that already exists in DSICLD; or, an AUTOCNT, Wait until the command list, or member, is no longer
AUTOTBL, AUTOTEST, or QRYGLOBL command being used and execute the AUTOCNT, AUTOTBL,
attempted to create a member that already exists. AUTOTEST, QRYGLOBL, or VPDALL command again.
Message Variables
DWO031A MESSAGE FAILED TO AUTOMATE,
member MESSAGE CONTENTION
The name of the command list that the VPDALL PROBLEM.
command attempted to create; or, the member
that the AUTOCNT, AUTOTBL, AUTOTEST, or Explanation
QRYGLOBL command attempted to create
An internal NetView error has caused NetView
automation to fail. The message that failed to
System action
automate is concatenated to this message.
System action
Operator response
The failed message is not automated.
Check the existing command list or member, to
determine whether you want to replace it. If you do Operator response
not, enter the VPDALL command with the name of a
command list; you can also enter the AUTOCNT, Notify the system programmer.
AUTOTBL, AUTOTEST, or QRYGLOBL command with
the name of a member that does not already exist. System programmer response
If you want to replace the existing command list or Contact IBM Software Support.
member, enter the VPDALL command with the same
command list name; or, enter the AUTOCNT, DWO032E AUTOMATION ACTION action
AUTOTBL, AUTOTEST, or QRYGLOBL command with COULD NOT BE ROUTED TO
the same member name and the REPLACE option. TASK(S) task.
DWO030I UNABLE TO CREATE THE MEMBER Explanation

'member|member ddname'. IT IS
IN USE, TRY LATER. — or — The NetView automation process attempted to route
UNABLE TO CREATE THE FILE 'file an automation action to the task or tasks listed in the
type mode'. IT IS IN USE, TRY message. The task or tasks are not active, not defined,
LATER. or not defined as a valid OST, NNT or PPT.
If the task is the name of a DST (for example,
Explanation BNJDSERV or CNMCSSIR), the action cannot be routed
to the OST that started the DST. If a list of tasks is
A VPDALL command attempted to create the specified
specified, the action was not routed to at least one of
command list; or, the AUTOCNT, AUTOTBL,

the tasks in the list. If UNKNOWN appears in the task DWO034I command COMMAND, OPID =
field, the task cannot be determined. operatorid WAITING FOR DATA
SERVICE RESPONSE
A message can be truncated for an action or task, or
both, because of the limitations in the network log.
Explanation
This message is written to the network log only and
does not drive installation exit DSIEX02A, and by The RESUME routine received control because of a
default is not displayed. It is, however, eligible for console interruption, but did not receive a response
NetView automation table processing, and subject to from data services.
automation table actions (for example, it can be Message Variables
routed, and displayed) and processing by installation
exit DSIEX16. command
The GLOBALV command
Message Variables
operatorid
action The operator ID
The automation table action.
task Operator response
The task or a list of tasks.
Wait for the data services response. If the message
continues, notify the system programmer.
System action
DWO035A MSU FAILED TO AUTOMATE, MSU
The actions associated with the automation table
CONTENTION PROBLEM.
entry are not processed.
Explanation
Operator response
An internal NetView error has caused NetView
Notify the system programmer of the errors.
automation to fail.

System action
If the task is not defined as an appropriate OST, NNT,
The MSU that failed to automate is not concatenated
or PPT then correct the definition or route the action to
to this message.
an appropriate task. If the task is defined properly,
then determine why the task was not active. All
actions are routed to an active task using the ROUTE Operator response
keyword of the EXEC action of the automation table Notify the system programmer.
(an autotask is recommended). See IBM Z NetView
Automation Guide for more information on automation
table routing.
DWO033I command COMMAND, OPID =
operatorid, RESUMED DWO038I function IS NOT ALLOWED IN THE
PROCESSING product ENVIRONMENT
The RESUME routine received a response from data A command or function was attempted that is not
services and passed the data to the command allowed in the specified product environment.
processor. Message Variables
Message Variables function
command The disallowed function
The GLOBALV command. product
operatorid The product environment in which the function is
The operator ID. not allowed
Important: Some disallowed function names are in
System action the following form:

CNMCSSIR-ssn operatorid
The ID of the operator who requested the load of
In these cases, ssn is the subsystem name that is the current active table.
associated with the given instance of the CNMCSSIR
DWO044I AUTOMATION TABLE LISTING
task. The message also specifies the allowed
listingname SUCCESSFULLY
subsystem name, which is the first NetView
GENERATED
subsystem name that is defined to z/OS (if one exists).
Explanation
System action
This message indicates that the automation table
The specified function does not run.
listing listingname you specified on a previous
AUTOTBL command invocation was successfully
Operator response generated.
Review the product documentation. Message Variables
DWO039I INVALID X'31' SUBVECTOR listingname
RECEIVED. The member or file name of the listing member
specified on the AUTOTBL command.
Explanation
DWO045E LOGICAL ERROR ON VSAM RPL.
A X'31' subvector that is not valid was received for a RC= X'retcode'. MSGAREA=
message text buffer. X'msgarea'. RPL FEEDBACK=
X'fdbkcode'.
System action
Explanation
VSAM encountered a logical error while attempting to
Operator response execute a GET or PUT for a RPL.
Notify the system programmer. This message is written only to the NetView log.
Message Variables
retcode
The subvector can be found as part of a X'3100' major The return code error in VSAM register 15.
vector. The buffer can be analyzed using a VTAM msgarea
buffer trace and Systems Network Architecture The 5 bytes of data returned by VSAM in the
Formats. MSGAREA of the RPL control block.
DWO040I AUTOMATION TABLE table fdbkcode
ACTIVATED mm/dd/yy hh:mm:ss The feedback field returned by VSAM.
BY operatorid
System action
Explanation
Processing continues, but the hardware monitor VSAM
You receive this message in response to an AUTOTBL database was not properly initialized.
STATUS request, if there is an active automation table.
This message describes the current active NetView Operator response
automation table.
Message Variables
table System programmer response
The name of the active automation table.
See the appropriate VSAM documentation for your
mm/dd/yy hh:mm:ss system.
The date and time the active automation table was
loaded. The date and time formats depend on the DWO046E PHYSICAL ERROR ON VSAM RPL.
TRANSMSG member, when in effect, and on the RC= X'retcode'. MSGAREA=
date and time operands of the DEFAULTS and msgarea. RPL FEEDBACK=
OVERRIDE commands. X'fdbkcode'. I/O BUFFER ADDR=
X'bufferaddr'

VSAM encountered a physical error while attempting The data is not sent.
to execute a GET or PUT for a RPL. This message is
written only to the network log. Operator response
Message Variables If the reason code is 08, determine why the task is not
retcode active. If possible, restart the task. For 04 or 12, notify
The return code error in VSAM register 15. the system programmer.
msgarea
The 116 bytes of data returned by VSAM in the System programmer response
MSGAREA of the RPL control block If the reason code is 12, determine why there is a
fdbkcode shortage of storage. If the reason code is 04, contact
The feedback field returned by VSAM IBM Software Support.
bufferaddr DWO048E AUTOMATION TABLE LISTING
The address of the I/O buffer associated with the HALTED DUE TO SEVERE ERROR.
data where the error occurred
Explanation
System action
The process was halted because of a severe I/O error.
Processing continues, but the hardware monitor VSAM This error can be a result of:
database was not properly initialized.
• Attempting to write records to a member or file for
which there is no write access
Operator response
• Filling the data set or the disk to which the records
Notify the system programmer. are being written
• Attempting to replace an existing member or file of
System programmer response the wrong type, or that is missing a required key field
Refer to the z/OS Communications Server library for
more information. System action
DWO047I UNABLE TO ROUTE DATA TO TASK The process ends.
task, REASON CODE = reason
Operator response
Explanation Notify the system programmer.
An attempt to MQS a buffer to the specified task failed
for the reason specified. System programmer response
Message Variables Determine the cause of the error and correct the
task problem. Check the system log for additional
The name of the task to which the data was sent. messages that might better describe the problem.
reason Ensure that your test of the automation table member

The reason for the failure. The value is one of the was successful. If it was, the member is loaded, but
following: the automation table listing is not generated. You can
generate a listing using the active, in-storage table
04 after you have cleaned up the DSILIST data set.
Buffer length not valid.
08 DWO049W A STORAGE OVERLAY CONDITION
The task is not active. WAS DETECTED, AND A STORAGE
DUMP IS BEING ATTEMPTED
12
Unable to obtain buffer storage.
Explanation
For reason codes not listed here, see the DSIMQS
macro in IBM Z NetView Programming: Assembler. The DSIFRE or DSIGET storage macro service
detected that storage was overlaid or that internal
storage table damage occurred. Possible reasons are:

• A program moved data beyond the end of the retcode3 — retcode9
storage it owned. These inserts are conditionally present and contain
• A DSIFRE specified the wrong length for the storage additional data, such as, module return codes to
being freed. assist IBM Software Support in problem
determination.
• A DSIFRE was used to free storage that was not
owned using DSIGET. The storage area specified
System action
overlaps storage that the NetView program is
managing. Processing continues.
• NetView storage management tables have been
overlaid. System programmer response
If the error is detected by the DSIFRE service, If the problem is the result of an error in NetView
message DWO115W is also issued. DWO115W code, contact IBM Software Support.
describes the storage being freed and the task where
DWO051I FOCALPT function COMMAND FOR
the DSIFRE was invoked.
CATEGORY category COMPLETED
If the problem was detected by the DSIGET service, SUCCESSFULLY
message DWO115W is not issued. The NetView
program detected a problem in the tables needed to Explanation
obtain storage for the request.
A FOCALPT DROP or FOCALPT ACQUIRE command
executed successfully. Messages that follow will fully
System action
describe any acquisition of a focal point that might
A storage dump is taken and NetView processing have taken place. The internal representation of the
continues. focal point names is updated. You can use this
message for automation, as it is the first message
Operator response within a multiple-line message block.
Notify the system programmer. Message Variables

function
System programmer response The function of the FOCALPT command issued
from an entry point (DROP or ACQUIRE).
When the storage dump is complete, investigate the
reason for the storage overlay dump. See the IBM Z category
NetView Troubleshooting Guide for more information The category of data for which the FOCALPT
on debugging the problem. You might want to recycle command was issued.
the NetView program as soon as possible to avoid
other problems resulting from the storage overlay System action
conditions.
DWO050E FOR PROBLEM DEBUG:
COMPONENT component MODULE: DWO052I FOCALPT function COMMAND FOR
module RC: retcode3 retcode4 CATEGORY category FAILED
retcode5 retcode6 retcode7
retcode8 retcode9 Explanation
Explanation failed to execute. Messages that follow fully describe
This message is written only to the network log and is the reason for the failure.
intended for IBM Software Support to use in You can use this message for automation, as it is the
debugging internal NetView errors. This message first message within a multiple-line message block.
accompanies other messages that are sent to the
authorized receiver. Message Variables

The function of the FOCALPT command issued
component from an entry point (DROP or ACQUIRE).
The component involved in the error.
module
The module involved in the error.

category Operator response
The category of data for which the FOCALPT
Enter the command again with a category known to
command was issued.
the focal point function and that has focal points
defined. You can use the FOCALPT QUERY command
System action to determine the current status of categories known to
Processing ends. the focal point function.
DWO055I NO BACKUP FOCAL POINT
Operator response DEFINED: CATEGORY category
Take appropriate action as indicated by the messages
that follow this message. Explanation
DWO053I CATEGORY IS UNKNOWN A FOCALPT DROP command specifying the BACKUP

keyword was issued to a registered category that does
not currently have a backup focal point.
Explanation
Message Variables
failed to execute. The category specified is category
syntactically correct, but it is not known to the focal The category of data for which the FOCALPT
point function at this node. This message follows a command was issued.
DWO052I message. You cannot use this message for
automation, as it is a message within a multiple-line System action
message block.
Processing ends.
System action
Operator response
Processing ends.
Enter the command again with a category known to
the focal point function and that has backup focal
Operator response
points defined. You can use the FOCALPT QUERY
Enter the command again with a category known to command to determine the current status of
the focal point function. You can use the FOCALPT categories known to the focal point function.
QUERY command to determine the current status of
categories known to the focal point function. DWO056I REASON CODE OF X'reason'
ENCOUNTERED
Explanation
Determine if an MS application was not registered.
This indicates that the focal point function was never A FOCALPT DROP command failed to execute. The
informed of its category of interest. command failed for the reason indicated by the reason
code. This message follows a DWO052I message.
DWO054I NO REMOTE FOCAL POINTS
You cannot use this message for automation, as it is a
DEFINED: CATEGORY category
message within a multiline message block.
The FOCALPT DROP command was issued to a reason

registered category that does not currently have a The reason code that identifies the reason for the
primary or backup focal point. failure. The possible values are:
Message Variables 100

nn
category
An application notification failure with the
The category of data for which the FOCALPT
following specific nn codes:
command was issued.
04
System action Storage shortage.
08
Processing ends.
Fatal error.

12 DWO051I message. You cannot use this message for
Non-fatal error. automation, as it is a message within a multiple-line
message block.
300nn
A failure concerning the locating of internal Message Variables
control blocks with the following specific nn
name
codes:
The name of the previous current focal point
04 (netid.luname).
Storage shortage.
08 System action
Control block access failed.
System action DWO059I THE CURRENT FOCAL POINT name

REMAINS UNCHANGED
Processing ends.
Explanation
Operator response
A FOCALPT DROP command executed successfully.
Notify the system programmer. The existing current focal point you specified was not
affected by the results of the FOCALPT DROP
System programmer response command and is still the current focal point for this
Identify the problem from the above reason codes and category for this entry point. This message follows a
take the necessary corrective action. If you need DWO051I message. You cannot use this message for
further assistance, contact IBM Software Support. automation, as it is a message within a multiple-line
message block.
DWO057I THE type FOCAL POINT name HAS
Message Variables
BEEN DROPPED
name
Explanation The name of the current focal point (netid.luname).
A FOCALPT DROP command executed successfully

System action
and the primary or backup focal point specified was
dropped. The internal representation of the focal point Processing continues.
is null. This message follows a DWO051I message.
You cannot use this message for automation, as it is a DWO060I CATEGORY ALERT SUPPORTS
message within a multiline message block. BOTH SNA-MDS AND NETVIEW-
UNIQUE FOCAL POINTS
Message Variables
type Explanation
Either PRIMARY or BACKUP. This message is issued in response to a FOCALPT
name QUERY command with a category of ALERT. ALERT is
The qualified name of the focal point that was unique in the NetView program because the NetView
dropped (netid.luname). program supports both architected local SNA-MDS
focal points and NetView-unique focal points for this
System action category. As SNA-MDS focal points, non-NetView entry
point applications can forward ALERT data to NetView
Processing continues. over the NetView MS transport. As NetView-unique
DWO058I THE OLD CURRENT FOCAL POINT focal points, NetView entry points can forward ALERT
name HAS BEEN SENT A data to the NetView focal point over LUC sessions.
REVOCATION Because of this unique situation for category ALERT,
the FOCALPT QUERY command provides two sets of
information. One set is for the NetView program as an
Explanation
SNA-MDS local focal point, and another set is for the
A FOCALPT DROP command executed successfully. NetView program as a NetView-unique focal point.
The previous current focal point was sent a revocation
to inform it that it is no longer the focal point for this
message within a multiple-line message block.
entry point for this category. This message follows a

System action NetView-unique focal pointing method does not
support the concept of a local focal point application.
DWO061I THE SNA-MDS FOCAL POINT
INFORMATION FOR CATEGORY
ALERT FOLLOWS:
System action
This message is issued in response to a FOCALPT DWO064I THERE ARE CURRENTLY NO
QUERY command with a category of ALERT. The NETVIEW-UNIQUE FOCAL POINTS
messages that follow this message provide the current FOR CATEGORY category
focal point state for category ALERT in regard to the
architected SNA-MDS focal pointing method. You Explanation
cannot use this message for automation, as it is a
message within a multiple-line message block. This message is issued in response to a FOCALPT
QUERY command with a category of ALERT or STATUS.
It indicates that no NetView-unique focal points
System action
currently exist for the specified category.
DWO062I THE NETVIEW-UNIQUE FOCAL message within a multiple-line message block.
POINT INFORMATION FOR Message Variables
CATEGORY category FOLLOWS:
category
Explanation Either ALERT or STATUS.
This message is issued in response to a FOCALPT System action

QUERY command with a category of ALERT or STATUS.
The messages that follow this message provide the Processing continues.
current focal point state for the specified category in
DWO065I THERE ARE CURRENTLY NO SNA-
regard to the NetView-unique focal pointing method.
MDS FOCAL POINTS FOR
STATUS supports only the NetView-unique focal
CATEGORY ALERT
pointing method. ALERT supports both NetView-
unique and architected SNA-MDS focal pointing
methods. NetView-unique focal pointing uses LUC Explanation
sessions to forward ALERT or STATUS data from a This message is issued in response to a FOCALPT
NetView entry point to a NetView focal point. QUERY command with a category of ALERT. It
You cannot use this message for automation, as it is a indicates that no SNA-MDS local focal point currently
message within a multiple-line message block. exists for the ALERT category. The NetView program
does not support SNA-MDS remote focal points for the
Message Variables ALERT category. This message appears after message
category DWO061.
Either ALERT or STATUS. You cannot use this message for automation, as it is a
System action
DWO063I NOT APPLICABLE, NETVIEW- Processing continues.

UNIQUE FOCAL POINTS ARE DWO066I CATEGORY STATUS SUPPORTS
ALWAYS REMOTE ONLY NETVIEW-UNIQUE FOCAL
POINTS
Explanation
This message is issued in response to a FOCALPT Explanation
QUERY with a category of ALERT or STATUS. This This message is issued in response to a FOCALPT
message appears after message DWO173 for LOCAL QUERY command with a category of STATUS. STATUS
focal points. Unlike the SNA-MDS method, the supports only the NetView-unique focal pointing

method, so no SNA-MDS related messages are This message can be accompanied by additional
present. This message is issued instead of message messages such as DWO138E or DWO335E that are
DWO061. sent to the authorized receiver.
You cannot use this message for automation, as it is a Message Variables
command
The name of the command that failed.
System action
DWO067I fptype NAME: name Processing of the command ends.

This message is issued in response to a FOCALPT Reenter the command. If the message persists, notify
QUERY command and displays focal point information the system programmer.
for the specified category.
You cannot use this message for automation, as it is a System programmer response
message within a multiple-line message block. Contact IBM Software Support.
Message Variables DWO070I THE FOCAL POINT DETAILS ARE
fptype AS FOLLOWS:
Either PRIMARY or BACKUP.
name Explanation
The current name of the remote focal point. A FOCALPT ACQUIRE command executed
successfully. The messages that follow this message
System action give detailed information on the current state of the
focal points for this category.
DWO068I BACKUP NAME: N/A, NOT header message within a multiple-line message block.
ALLOWED FOR CATEGORY
STATUS
System action
This message is issued in response to a FOCALPT DWO071I NEW fptype: netid1.fpname1 OLD
QUERY command with a category of STATUS. STATUS fptype: netid2.fpname2
does not currently support backup focal points. This
message is issued instead of message DWO067 for a Explanation
backup focal point.
A FOCALPT ACQUIRE command completed
You cannot use this message for automation, as it is a successfully. This message displays the current and
message within a multiple-line message block. previous focal point details. The fptype can be either
PRIMARY, BACKUP, or CURRENT. The primary and
System action backup focal points are as exists in the internal focal
point representation. When it exists, the CURRENT (or
Processing continues. active) focal point is the primary or backup focal point.
DWO069E command COMMAND FAILED DUE You cannot use this message for automation, as it is a
TO INTERNAL NETVIEW ERROR. message within a multiple-line message block.
REENTER THE COMMAND.
Message Variables
Explanation fptype
Either PRIMARY, BACKUP, or CURRENT.
The NetView program encountered an internal error
while processing your command, and the command netid1.fpname1
cannot continue. The qualified name of the NEW focal point for the
fptype specified, or NONE.

netid2.fpname2 You cannot use this message for automation, as it is a
The qualified name of the OLD focal point for the message within a multiple-line message block.
fptype specified, or NONE.
Message Variables
System action function

ACQUIRE
operatorid
DWO072I FOCALPT function ISSUED FROM The NetView operator who issued the outstanding
NODE nodeid command.

This message is issued when a FOCALPT CHANGE Processing ends on the FOCALPT DROP or FOCALPT
command is received at an entry point on which a ACQUIRE command.
FOCALPT ACQUIRE is in progress. The FOCALPT
ACQUIRE command is overridden. Operator response
You cannot use this message for automation, as it is a Issue the FOCALPT command again with the
message within a multiple-line message block. OVERRIDE keyword.
Message Variables DWO075I function WITH OVERRIDE ISSUED
function BY OPERATOR operatorid
CHANGE.
nodeid Explanation
The qualified name of the focal point node from The specified operator operatorid has overridden your
which the command was issued (netid.luname). outstanding FOCALPT ACQUIRE command.
System action
Processing of the FOCALPT ACQUIRE command ends.
Message Variables
DWO073I LOCAL FOCAL POINT REGISTERED function
Either ACQUIRE or DROP.
Explanation
operatorid
This node already contains an active local focal point The NetView operator who issued the overriding
application for the specified category. The FOCALPT command.
DROP and FOCALPT ACQUIRE commands can be
issued only on an entry point node. Therefore, they are System action
disallowed because this node is a focal point node for
the specified category. Processing on the FOCALPT ACQUIRE ends.
You cannot use this message for automation, as it is a DWO076I NO PRIMARY FOCAL POINT
message within a multiple-line message block. DEFINED

Processing of the command ends. A FOCALPT ACQUIRE command explicitly or implicitly
specified PRIMARY=KEEP with an explicit BACKUP
DWO074I function COMMAND ISSUED BY value when no primary focal point is defined.
OPERATOR operatorid STILL IN
PROGRESS You cannot use this message for automation, as it is a
Explanation
System action
An operator issued a FOCALPT ACQUIRE command.
Before it completes, another (or the same) operator Processing ends.
issues a FOCALPT DROP or FOCALPT ACQUIRE DWO077I INVALID DATA STRUCTURE
command for the same category. The second request RECEIVED FROM FOCAL POINT
is rejected. name

Explanation DWO079I NOTE -- THE BACKUP FOCAL
POINT IS THE CURRENT REMOTE
A FOCALPT ACQUIRE command failed because the
FOCAL POINT
focal point function in this node received data that is
not valid from the focal point function in the focal point
node. Explanation
You cannot use this message for automation, as it is a The FOCALPT ACQUIRE command successfully
message within a multiple-line message block. updated the internal representation of focal points and
obtained the backup focal point as the new active focal
Message Variables point. An unsuccessful attempt was made to acquire
name the primary focal point prior to acquiring the backup.
The qualified name of the focal point When the timer expires, another attempt is
(netid.luname). automatically made to try to acquire the primary focal
point.
System action You cannot use this message for automation, as it is a
Processing ends.
System action
Operator response
Enter the command again. If the message persists,
contact the system programmer. DWO080I TASK NAME 'taskname' IS
INVALID. IT IS A NETVIEW
System programmer response RESERVED NAME
Validate the software running on the focal point.
Contact IBM Software Support and provide the Explanation
NetView internal trace and log. The taskname cannot be used as an optional task
name. The name is reserved for NetView use only.
DWO078I NOTE -- THERE IS NO CURRENT
These are the NetView reserved names: ALL, DPR,
REMOTE FOCAL POINT
DST, HCL, HCT, LOG, MNT, NNT, OPT, OST, PPT,
SYSOP, TCT, and any names that begin with DSI#.
Explanation
Message Variables
A FOCALPT ACQUIRE command successfully updated
the internal representation of focal points, but did not taskname
obtain a new active focal point. The NetView program The task name defined in the CNMSTYLE member
attempts to acquire the primary focal point first, and or the value for the TASK parameter in the START
then the backup focal point (if one exists). When the command.
timer expires, another attempt is automatically made
to acquire the primary focal point. System action
You cannot use this message for automation, as it is a NetView ignores the TASK statement or the START
message within a multiple-line message block. TASK command.

Processing continues. If the message is issued as a result of a START TASK
command, enter the command again using a different
Operator response TASK value. If the message is issued at NetView
initialization, notify the system programmer.
If a focal point is required, issue the FOCALPT
ACQUIRE command again for a node on which an
active local focal point application exists. You can
issue the DEFAULTS REACQPRI command to modify Correct the TASK definition in the CNMSTYLE member.
the timer interval for subsequent acquisition attempts See IBM Z NetView Installation: Getting Started for
of the primary focal point. information on how to modify the CNMSTYLE member.
DWO081I token is verb implemented in
module. Type = type

DWO082I (no text) DWO085E The value 'MEM-' was specified for
the MODFILT keyword without a
Explanation member name following 'MEM-'.
This message is the control line for a multiline

Explanation
message listing the applications active on a NetView
task. The following line is a label line naming the The MEM-member value was specified for the
columns of data that follow. MODFILT keyword of the TRACE command with a
missing member. For example, MODFILT=(MEM-) was
Each application is identified by the command verb
specified. This is incorrect; a non-null DSIPARM
that was used to start the application, except that
member name must be specified. For example,
NCCF identifies the standard command facility screen.
MODFILT=(MEM-FILT1) specifies a DSIPARM member
Each application is also identified by a serial number in
named FILT1.
the range 1-4294967295 and is unique across each
instance of the NetView program.
System action
DWO083I text
The NetView program stops processing the command.
Explanation
Operator response
This message is used to display the NetView trace
entries at the monitoring operator task when the Correct the command and enter it again.
TRACE command is issued with the MONOPER DWO086I ddname member member contains
keyword. no MODFILT filter entries.
Message Variables
Explanation
text
The text of the message varies depending on the MODFILT=(MEM-member) was specified on the TRACE
type of NetView trace entries that are being command; however, the specified data set member
displayed. For example, OPTION=MOD trace contains no MODFILT filter entries. For example, the
entries are displayed with a different format than member might contain only comment lines or blank
OPTION=PSS trace entries. See the IBM Z NetView lines. This is not an error, but it is unusual, because
Troubleshooting Guide for examples. normally the specified member is expected to contain
one or more MODFILT filter entries.
DWO084E The value value specified for
keyword keyword on the command Message Variables
command is incorrect. It is too
ddname
long.
The data set name, for example, DSIPARM.
member
Explanation
The name of a data set member.
The value specified for the keyword is too long.
value The NetView program continues processing the

The specified value. command.
keyword DWO087E ddname member member contains
The keyword. the following incorrect MODFILT
command filter entry: 'MEM-badmem'.
The command. Nesting members is not permitted.
The NetView program stops processing the command. MODFILT=(MEM-member) was specified on the TRACE
command. A MODFILT filter entry in the data set
member incorrectly attempts to include another data
Operator response
set member. Nesting members is not permitted. A
Correct the command and enter it again. MODFILT filter entry within a data set member cannot
attempt to include another data set member.

Message Variables DWO089I is issued, followed by one or more
DWO083I messages which display the undecoded
ddname
trace record in hexadecimal.
The data set name, for example, DSIPARM.
member Message Variables
The name of a data set member. type
MEM-badmem The trace record type. See the IBM Z NetView
The MODFILT filter entry present in the data set Troubleshooting Guide for a list of the trace record
member that incorrectly attempts to include types.
another data set member. DWO090A action error for component.
Maintenance required.
System action
The NetView program stops processing the command. Explanation
A serious error occurred when attempting to perform
Operator response the specified action by the component named.
Remove the MEM-badmem entry from the data This message will be accompanied by other system or
member; then enter the command again. NetView messages providing details of the failure.
DWO088E An error was encountered while Message Variables
processing ddname member
action
member.
Either ALLOCATE or WRITE. An action necessary to
the proper function of the component.
Explanation
component
The NetView program encountered an error while A function of the NetView program.
reading and processing lines in the data set member.
Other error messages will always accompany this Operator response
message, and they will precisely identify the problem.
These accompanying messages can either precede or Notify the system programmer.
follow the DWO088E message.
ddname Examine the log for messages that provide details

The data set name, for example, DSIPARM. about the failure.
member If the component is the Canzlog log, the failure

The name of a data set member. prevents data from being saved in the Canzlog archive.
Take manual or automated steps to correct the error.
One of the following actions occurs at the time of the
System action
failure:
See the accompanying messages.
• The NetView program retries the action
approximately every 5 minutes until it succeeds.
Operator response
• Archiving stops.
See the accompanying messages.
• The NetView program ends.
DWO089I type not currently decoded. The If the CNMSTYLE definitions indicate that archiving is
trace record follows. enabled and the RESTYLE ARCHIVE command is run,
the NetView program retries the action. To avoid the
Explanation loss of data, correct the problem as soon as possible
The NCCF TRACE command was previously issued and before a system IPL.
with the MONOPER keyword. The current trace record DWO091I action received. No operator
that is being displayed at the MONOPER monitoring dataset defined for DDN.
task has a trace record type that is not recognized.
Presently, not all types of trace records are recognized
and decoded by MONOPER processing. When these
unrecognized trace records are encountered, message

The action specified was partially processed, but could Notify the system programmer.
not be completed because of a lack of access to the
DDN named. System programmer response
Message Variables Review the log to determine whether the member
action specified contained an error or if the required
Previously specified command, subcommand, or automation activation command was in error.
keyword. Determine whether the required automation was
included in a member of a different name. If this
DDN message occurred during NetView initialization, then it
A data definition name. may be necessary to restart the NetView program after
correcting the problem.
Operator response
DWO094W NetView at ASID asidno is using
None required unless completion of the action is SSI ssiname - procname
necessary.
Explanation
The subsystem router task cannot connect with or
Determine why the DDN was unavailable. User the receive messages or commands from the subsystem
OVERRIDE command to specify a correct value for the interface because another instance of the NetView
DDN. program is so connected.
DWO092I action ignored. Insufficient input Message Variables
provided.
asidno
The Address Space ID number of the other
Explanation program.
You entered a command or subcommand, possibly ssiname
from a panel, but did not provide enough input The four-character name of the SSI that is in
parameters, panel selections, or both input contention.
parameters and panel selections. The action is
procname
ignored.
The Job name of the instance of the NetView
Message Variables program that is contending for connection to the
named subsystem interface.
action
Previously specified command, subcommand, or
keyword. System action
The NetView program ends.
Operator response
Provide additional parameters or enter another Operator response
command. Notify the system programmer.
DWO093W Required automation at risk.
Member tblName not activated. System programmer response
This contention is caused by two instances of the
Explanation NetView program in the same LPAR having the same
The automation in the table or include member named first four characters in the job name. The job name is
is considered necessary for proper operation of the usually the same as the procedure name. Change the
NetView product. It is not an active part of the current job name of one NetView instance and then restart
automation table list. that instance.
Message Variables DWO095A NetView at ASID asidno forced

OFF SSI ssiname - procname
tblName
The name of an automation table member or an
include member in an automation table.

The subsystem router task removed a connection to Notify the system programmer.
the subsystem interface from another instance of the
NetView program. System programmer response
Message Variables Install the part with the correct attribute. If the part is
asidno DSIRXPRM, delete the current copy of DSIRXPRM from
The Address Space ID number of the other your load library. Make sure that the job that is used to
program. link edit DSIRXPRM (such as the CNMSJM11 sample
job) uses only the REUS attribute, and then run the job.
ssiname After the job completes successfully, restart the
The four-character name of the SSI that is in NetView program.
contention.
procname DWO097E Configuration not supported
The Job name of the instance of the NetView reason text
program that is contending for connection to the
named subsystem interface. Explanation
The configuration is not supported.
System action
Message Variables
The subsystem router task connected to the
subsystem and removed the connection from the reason_text
procedure named in the message. If the procedure Text describing the configuration that is not
named by procName is active, it might not tolerate the supported.
disconnection. DWO098W UNAUTHORIZED CLIENT username
SENT DATA TO service, ID =
Operator response 'symbol'
Explanation
System programmer response Data has been received from a program or client
identified by username. This user is not authorized to
If the procedure named by procName is active, stop
use the service. If the data contains an identifier, that
the subsystem router task for that instance of the
is given as "ID".
NetView program. Otherwise, review the log to
determine why the contending instance of the NetView Message Variables
program was unable to shut down cleanly.
username
DWO096E part incorrectly installed with An identifier for a job or client, usually an SAF ID.
attr_name attribute service
A service or a command that requires
Explanation authorization.
The part part is incorrectly installed with the symbol
attr_name attribute. If the request data contains a sequence number or
other identifying text, that information is given as
Message Variables symbol.
attr_name
The erroneous attribute. System action
part The service request is ignored.
The name of the failing part.
Operator response
System action
The system action is determined by how critical the
part is to the overall NetView operation. If the part is
DSIRXPRM, the NetView program ends.
Determine whether the client should have access to
the specified service. If so, configure the client's

access to the service using the appropriate X'10' and X'11' and is built while the system is
configuration steps documented in the NetView running.
library.
Message Variables
If the service is APSERV, see the APSERV.PREFIX
reqid
statements in the IBM Z NetView Administration
Reference and the sections that discuss APSERV in the
responding.
IBM Z NetView Security Reference.
prodid
DWO100I REQID reqid : ORIG nodetype Identifies the type of product.
nodename CNFG nodetype
vpdfield=xxx [...]
nodename [...]
Various fields and values that describe the type of
product. For details on these fields and values, see
Explanation the IBM Z NetView Application Programmer's
This message reflects the configuration of the node Guide.
that answered the VPD request. The data returned in DWO103I REQID reqid : ORIG nodetype
this message is built while the system is running. nodename CNFG nodetype
Message Variables nodename [...]
reqid
The ID of the request to which this message is Explanation
responding. This message is issued instead of DWO100 if the
nodetype and nodename configuration reported by VTAM includes more names
The nodetype and nodename following ORIG than the routine can manage. This happens when the
describe the node where the VPD request amount of storage allocated during initialization (on
originated. The pair or pairs of nodetypes and the VPDSTOR operand of the VPDINIT statement) is
nodenames following CNFG describe the not sufficient. The data returned in this message is
configuration of the originating node. For more built while the system is running.
information on the data returned in nodetype and Message Variables
nodename, see the IBM Z NetView Application
Programmer's Guide. reqid
DWO101I REQID reqid : vpdfield=xxx [...] responding.
nodetype and nodename.
Explanation The nodetype and nodename following ORIG
This message contains attached device configuration describe the node where the VPD request
data. The data is returned in subvector X'82' and is originated. The pair or pairs of nodetypes and
built while the system is running. nodenames following CNFG describe the
configuration of the originating node. For more
Message Variables information on the data returned in nodetype and
reqid nodename, see the IBM Z NetView Application
The ID of the request to which this message is Programmer's Guide.
responding.
vpdfield=xxx [...] Operator response
Various fields and values that describe the Contact the system programmer.
attached device. For details on these fields and
values, see the IBM Z NetView Application
Programmer's Guide.
Increase the size specified in the VPDSTOR parameter
DWO102I REQID reqid : prodid vpdfield=xxx in the VPDINIT definition statement.
[...]
DWO105I REQID reqid : vpdfield=xxx [...]
Explanation
This message contains data about the type of product
of a particular node. The data is returned in subvectors

This message contains product set attribute data. The reqid
data is returned in subvector X'84' and is built while The ID of the request to which this message is
the system is running. responding.
Message Variables sensecode
The 8-character hexadecimal sense code of the
reqid node that cannot satisfy the VPD request.
responding. DWO115W A STORAGE OVERLAY WAS
DETECTED WHEN STORAGE AT
vpdfield=xxx [...]
ADDRESS X'address' WAS FREED
Various fields and values that describe the product
BY TASK task
set attributes. For details on these fields and
values, see the IBM Z NetView Application
Programmer's Guide. Explanation
DWO106I REQID reqid : vpdfield=xxx [...] An overlay of storage was detected by the DSIFRE
macro service. This message follows either message
DWO049W or DWO316W and identifies the address of
Explanation
the storage being freed and the task where the DSIFRE
This message contains additional product set attribute macro was invoked.
data. The data is returned in subvector X'86' and is
Message Variables
built while the system is running.
address
Message Variables
Address of storage being freed by the DSIFRE
reqid macro.
The ID of the request to which this message is task
responding. Name of the task where the DSIFRE macro was
vpdfield=xxx [...] invoked.
Various fields and values that describe the
additional product set attributes. For details on System action
these fields and values, see the IBM Z NetView
Application Programmer's Guide. NetView processing continues.
DWO110I REQID reqid : vpdfield=xxx [...] Operator response
This message contains link configuration data. The System programmer response
data is returned in subvector X'52' and is built while
the system is running. Using the address of the storage being freed and the
task name where the NetView service macro DSIFRE
Message Variables was invoked, investigate the reason for the storage
reqid overlay condition. Consider recycling the NetView task
The ID of the request to which this message is identified in the message as soon as possible to avoid
responding. other problems resulting from the storage overlay
conditions.
vpdfield=xxx [...]
Various fields and values that describe the link DWO119A FOCAL POINT DEFINITION IS NOT
connection. For details on these fields and values, VALID, DSICRTR IS NOT ACTIVE
see the IBM Z NetView Application Programmer's
Guide.
Explanation
DWO111I REQID reqid : SNS sensecode A LIST FOCPT command was entered, but the
DSICRTR task was not active.
Explanation
This message contains SNA sense data supplied by a Operator response
node that cannot satisfy a VPD request. The data is Start the DSICRTR task.
returned in subvector X'7D'.

DWO120I STATUS NOT FORWARDED, THIS DWO131I FOCALPT COMMAND FAILED, NO
HOST IS A STATUS FOCAL POINT MS APPLICATION IS CURRENTLY
REGISTERED AS A LOCAL FOCAL
Explanation POINT APPLICATION FOR TYPE
type
A LIST FOCPT command was entered, but this
NetView host is a status focal point and therefore is
Explanation
not forwarding status.
The FOCALPT command failed because there are no
DWO130I command COMMAND FAILED. local management services (MS) applications currently
REASON CODE OF X'reason' registered as a local focal point for the type specified.
ENCOUNTERED That is, the command failed because you are
requesting that the target node in the FOCALPT
Explanation command change its focal point to be your node for
The command entered failed because of the reason the specified type. However, your node is not allowed
indicated. to be a focal point for this type because no local MS
application in your node currently qualifies as a focal
Message Variables point for this type.
command Message Variables
The name of the command that failed
type
reason The type of data for which no local focal point
The reason code that identifies the problem exists in your node
If reason=X'000010nn', it is only valid for the
FOCALPT command. The destination of the FOCALPT System action
command sent back an MS capabilities reply rejecting
the MS capabilities request for this node to be its focal The command is not processed.
point. nn represents the rejection reason. These codes
can be: Operator response
00 The FOCALPT command failure can result from either
No specific reason stated. the hardware monitor's BNJDSERV task not being
01 active, or the multiple-domain support (MDS)
The function is not supported. transport's DSI6DST task not being active. Ensure that
both tasks are active and retry the command. If the
02 command fails with both tasks active, notify the
There is an existing focal point defined for this system programmer.
category that has a higher rank.
06 System programmer response
The receiving node does not support having an
explicit focal point. First determine if a local MS application must be
registered as a focal point for the type specified in the
Otherwise, the reason code is the same as the SNA node. If not, simply inform the operator that this node
sense code. Refer to the Systems Network is not defined to be a focal point for the specified type.
Architecture library for more information about SNA If the node is defined, determine why there is no local
sense codes. focal point registered for the specified type.
See IBM Z NetView Installation: Configuring Additional
System action
Components to determine why there is no local focal
The command is not processed. point registered for the specified type.
DWO132I FOCALPT function COMMAND
Operator response
FAILED - TARGET DOMAIN target
Notify the system programmer. CANNOT BE ITS OWN PRIMARY
REMOTE FOCAL POINT
Explanation
Identify the problem by finding the SNA sense code in
the Systems Network Architecture library and take The command failed because the target node name
corrective action. you specified (also known as the LU name or the

domain name) matches the local domain name. For If the error occurs on the DEFFOCPT statement, notify
the FOCALPT CHANGE command, the target domain the system programmer.
cannot be a remote focal point for itself. A single
domain can be its own local focal point for various System programmer response
types (such as ALERT or OPS_MGMT), but it is never
allowed to be its own remote focal point (either If the error occurred on a DEFFOCPT statement, either
primary or backup) for a type. remove the backup specification, or change it so that it
differs from the primary focal point name.
Message Variables
DWO134I IDENTICAL VALUES DETECTED
function FOR THE REMOTE PRIMARY AND
The function of the FOCALPT command issued BACKUP FOCAL POINT NAMES
(ACQUIRE or CHANGE). FOR TYPE type. THE BACKUP
target FOCAL POINT NAME HAS BEEN
The target domain specified in the command. REMOVED.

The command is not processed. A request was received to change the value of the
remote primary (and possibly the remote backup as
Operator response well) focal point for the indicated focal point. The
request most likely originated from a FOCALPT
Enter the command again with a valid remote focal CHANGE command in another node. The value or
point domain name. values were changed, and after the change it was
DWO133I WARNING: PRIMARY AND found that both the remote primary and backup focal
BACKUP FOCAL POINTS FOR points had the same value for the specified type. This
CATEGORY fpcat HAVE THE SAME is not allowed, so the backup focal point is set to null
VALUE=value. BACKUP VALUE IS and no backup focal point now exists for this type. You
IGNORED. can use the FOCALPT QUERY command to verify the
set focal points.
Explanation Note: This message is sent to the authorized receiver
and must be held until explicit action is taken.
In either a DEFFOCPT statement in the DSI6INIT
member of DSI6DST task initialization data set, or in a Message Variables
FOCALPT command, both the remote primary (or type
target) focal point and the backup focal point names The type of data for which focal point information
have the same value. This is not allowed and the is being given.
backup value is ignored. The primary (or target) focal
point name is accepted and processed.
System action
Message Variables
fpcat
PRIMARY for the DEFFOCPT statement or TARGET Operator response
for the FOCALPT command.
If you want to acquire a backup focal point, issue the
value
FOCALPT ACQUIRE command. If you want to restore
The value of the primary and backup focal points.
the focal points defined in the SYSDEF instead of the
currently active focal points, stop the DSI6DST task
System action and restart it. Otherwise, no action is needed.
Processing continues. DWO136I function function2 command
REQUEST FAILED DURING process
Operator response PROCESS REASON= reason
If the error occurs on a FOCALPT command, enter the
command again without the backup specified, or Explanation
specify the backup as being something other than the
The command request failed during the process
primary. For example, specify something other than
process because of reason indicated.
the node name from which you are entering the

function DWO137I FOCAL POINT AUTHORIZATION
The first function name, such as FOCALPT or FOR CATEGORY category HAS
FPINFO. BEEN REVOKED BY DISTRIBUTED
function2 NODE node
The second function name, such as SAVE/
RESTORE or MSCAPS. Explanation
command A FOCALPT DROP or FOCALPT ACQUIRE command
The command requested, such as SAVE, RESTORE, was successfully issued at the specified distributed
DELETE, or REPLACE. node. Data for the specified category is no longer sent
process to this focal point.
The process where the command failed. It has one Message Variables
of the following values:
category
01 A focal point category name (for example,
Initialization. OPS_MGMT).
61 node
Explicitly acquiring a focal point through a The qualified LU name of the distributed node that
FOCALPT CHANGE command. was an entry point of the specified category for this
64 focal point.
Implicitly acquiring a focal point through a
DEFFOCPT statement. System action
reason The entry point data for this category is no longer sent
The reason why the command failed. It has one of to this focal point.
the following values:
04 DWO138E FOCAL POINT FUNCTION
Storage shortage. ENCOUNTERED INTERNAL ERROR.
UNEXPECTED RESULTS MAY
08 OCCUR AS PROCESSING
Save/Restore task (DSISVRT) abend. CONTINUES.
12
Buffer length is not valid. Explanation
16 The focal point function encountered an internal error
Combination of buffers is not valid. during processing from which it is unable to recover.
20 As a result, the focal point function might be unable to
Number of buffers is not valid. function properly and unexpected results can occur.
These results can be:
System action • Local management services (MS) applications might
Processing continues, but the focal point does not not be notified of a focal point change. For example,
perform any SAVE and RESTORE functions until the the focal point changed but one or more local MS
error is corrected. No more focal point information is applications were not made aware of it.
saved, restored, or deleted to and from the VSAM file. • The focal point function was unable to build and
send a request or reply to another node, so normal
Operator response focal point communication between nodes was
unable to complete successfully. For example, a
Notify the system programmer. focal point cannot be obtained or revoked.
• The focal point function was unable to properly
maintain internal tables, and they might be
Determine the reason for the failure. If the reason corrupted. This results in incorrect focal point being
code is 08 (ABEND), see the related messages to find sent to a local MS application, or incorrect focal
out why DSISVRT abends. If the reason code is 04, 12, point status information being displayed from a
16, or 20, contact IBM Software Support. FOCALPT QUERY command.
After you have corrected the error, recycle subtask • The focal point function might stop trying to
DSI6DST. Recycle the NetView program if the focal reacquire its remote primary focal point.
point information needs to be saved in VSAM.

• The focal point function might improperly process Operator response
the registration of a local MS application that has
Enter the command again with a valid remote focal
registered as either a focal point itself, or as
point domain name.
interested in a category. (Interested in a category
means that the application wants to be sent notice DWO142I resource REMOVED FROM
whenever the focal point status changes for the REGISTRATION FILE BECAUSE OF
interested category). X'sensecode' SENSE CODE
This message is accompanied by message DWO050E
in the network log. DWO050E is present to help IBM Explanation
Software Support debug the internal NetView errors. A resource was removed from the registration file
because of a sense code that is not valid.
System action
Message Variables
Processing continues, but unexpected results can
resource
occur in the focal point function.
The name of the resource for which the sense code
was issued.
Operator response
sensecode
Notify the system programmer. The hexadecimal sense code.

Stop and restart the DSI6DST task to reinitialize the The request is ignored.
focal point function. You can delay this recycling until
your system is at an acceptable point for recycling. Operator response
However, the unexpected results discussed previously
might occur. Notify the system programmer.
If this message persists, contact IBM Software
Support. System programmer response
Determine the source of the error from the sense code
DWO139I FOCALPT CHANGE COMMAND
and correct the problem.
FAILED - TARGET DOMAIN target
CANNOT BE ITS OWN BACKUP DWO143I DSIROVS [NOT | NO LONGER]
REMOTE FOCAL POINT AVAILABLE TO PROCESS
REGISTRATIONS
Explanation
The command failed because the target node name Explanation
you specified (also known as the LU name or the A PU type 2 gateway attempted to register a
domain name) matches the local domain name. For configuration change with the NetView program, but
the FOCALPT CHANGE command, the target domain the DSIROVS registration task was not available.
cannot be a remote focal point for itself. A single
domain can be its own local focal point for various Message Variables
types (such as ALERT or OPS_MGMT), but it is never NOT
allowed to be its own remote focal point (either DSIROVS was never started. This message is
primary or backup) for the same type. issued for each attempt by a PU gateway to
Message Variables register.
NO LONGER
target
DSIROVS was previously started but is no longer
The target domain specified in the command.
active. This message is only issued once.
System action
System action
The command is not processed.
If a registration table exists, it is disabled and the
registration request is discarded.

The name of the task that failed.
Issue a START command for task DSIROVS.
System action
The function fails.
It is recommended that DSIROVS be started during
NetView initialization.
Operator response
DWO144I FRONT END GATEWAY puname
HAS REGISTERED Notify the system programmer.
A front end gateway registered one attached device. Take any necessary corrective action. If you need
Subsequent device registrations to this gateway are further assistance, contact IBM Software Support.
not reported. DWO151I NETVIEW BRIDGE FAILURE IN
Message Variables TASK task. SNA SENSE CODE OF
X'sensecode' ENCOUNTERED
puname
The name of the front end gateway that registered
Explanation
the device.
The function listed in the message failed because of
System action the reason indicated by the SNA sense code.
DWO546I is issued along with DWO151I.
Message Variables
DWO145I FRONT END GATEWAY puname NO
LONGER REGISTERED task
The name of the task that encountered the error
Explanation sensecode
The SNA sense code that identifies the problem.
A front end gateway, that previously had devices Refer to the Systems Network Architecture library
registered to it, reset all registered devices. for more information about the SNA sense codes.
Message Variables
System action
puname
The name of the front end gateway that reset all The function fails.
the registered devices.
Operator response
System action
DWO150I NETVIEW BRIDGE FAILURE IN System programmer response
TASK task. INVALID BUFFER Identify the problem by finding the SNA sense code in
RECEIVED the Systems Network Architecture library. Take the
necessary corrective action. If you need further
Explanation assistance, contact IBM Software Support.
This message is usually issued alone, and rarely DWO152I NETVIEW BRIDGE FAILURE IN
occurs. It can be created if a token sent from the TASK task. macro RETURN CODE =
server is neither a READY nor a QUIESCE token, or if a retcode
buffer is received from the server that is all blanks.
Both of these failures occur in the NetView Bridge Explanation
task. This message can also be created if a buffer
greater than 32767 bytes is received in the cross- A macro failed with a return code in register 15. This
domain receive component of NetView Bridge. This message is usually issued alone and often indicates a
failure is in the Remote Bridge task. severe error that causes the task to abend.

task retcode15
The name of the task that failed. The return code from the IEFSSREQ macro. The
macro value will be one of the following:
The name of the macro that failed. X'04'
retcode The primary job entry subsystem does not
The return code in register 15 of the macro that support this function.
failed. X'08'
The primary job entry subsystem exists, but is
System action not up.
The macro or function fails. X'0C'

The primary job entry subsystem does not
exist.
Operator response
X'10'
Notify the system programmer. The function is not completed—disastrous
error.
System programmer response X'14'
If the program-to-program interface function fails, A logical error. For example, bad subsystem
identify the problem by finding the return code in the options block (SSOB), incorrect length.
IBM Z NetView Application Programmer's Guide. retcode
If the MDS_MU_DECODE function fails, the return The return code from SSOBRETN. The value will be
codes are: one of the following:
0 X'04'
Successful. The request or return jobid was unsuccessful.
4 X'08'
Type for decoding request is not valid. The request is without a matching return.
10 X'0C'
Data truncated. The return is without a matching request.
12 X'24'
Cursor is not valid. A program error.
16
No parameter exists in the encoded data. System action
18 The request or release jobid function is not processed.

Fatal.
Otherwise, identify the problem by finding the return
code in IBM Z NetView Programming: Assembler. Take Verify that the primary job entry subsystem is defined
any necessary corrective action. If you need further correctly and is active. This problem prevents
assistance, contact IBM Software Support. submission of batch jobs using the SUBMIT command
and allocating system output files using the ALLOCATE
DWO153I task : IEFSSREQ MACRO ERROR:
command.
(REQUEST | RETURN) JOBID, R15=
retcode15 RC= retcode DWO154I 'task' : NETVIEW HAS (RECEIVED |
RELEASED) JES JOBID 'jobid'
Explanation
Explanation
The specified task was unable to request or release a
jobid to the primary job entry subsystem. If the NetView program is started under the master
subsystem (SUB=MSTR), it is not assigned a JES jobid.
Message Variables
A JES jobid is required for the SUBMIT command to
task submit batch jobs, and for the ALLOCATE command to
The name of the task that issued the IEFSSREQ allocate system output data sets. When started under
macro. the master subsystem, the NetView program requests
a jobid from JES. The NetView program releases the
jobid when JES or the NetView program ends.

However, after NetView receives a jobid from JES, if Explanation
JES abends or ends without notifying NetView to
A macro failed with a return code in register 15.
release the jobid, NetView might not be able to end
DWO546I and DSI384I might be issued along with this
before JES becomes active again.
message.
Message Variables
Message Variables
task
task
The name of the task that requested or released
The name of the task that failed.
the JES jobid.
macro
jobid
The name of the macro that failed.
The JES jobid.
retcode
DWO155I NETVIEW DOES NOT HAVE A JES The return code in register 15 of the macro that
JOBID failed.

This message is a response to a SUBMIT or ALLOCATE The macro or function fails.
command. The NetView program does not have a JES
jobid and the services requested by these commands
Operator response
require a JES jobid.
System action
If the program-to-program interface function fails,
Operator response identify the problem by finding the return code in the
IBM Z NetView Application Programmer's Guide.
Verify that the primary job entry subsystem is defined
correctly and is active. Verify that NetView task If the MDS_MU_DECODE function fails, the return
DSIRQJOB is active by issuing a LIST codes are:
TASK=DSIRQJOB command. If it is not active, issue 0
START TASK=DSIRQJOB. If this message occurs Successful.
frequently, notify the system programmer.
4
Type for decoding request is not valid.
10
To start this task every time the NetView program is Data truncated.
started, change your CNMSTUSR or CxxSTGEN 12
member as follows: Cursor is not valid.
• Override the TASK.DSIRQJOB.MOD=*NONE* entry 16
in the CNMSTYLE member by adding the following No parameter exists in the encoded data.
entry:
18
TASK.DSIRQJOB.MOD=DSIRQJOB Fatal.
• Override the TASK.DSIRQJOB.INIT=N entry in the Otherwise, identify the problem by finding the return
CNMSTYLE member by adding the following entry: code in IBM Z NetView Programming: Assembler. If you
need further assistance, contact IBM Software
TASK.DSIRQJOB.INIT=Y Support.
DWO157I NETVIEW BRIDGE TRANSACTION
DWO156I NETVIEW BRIDGE TRANSACTION
REPLY TERMINATED IN TASK
REQUEST TERMINATED IN TASK
task. macro RETURN CODE =
task. macro RETURN CODE =
retcode
retcode

Explanation A STORAGE DUMP IS BEING
ATTEMPTED
A macro failed with a return code in register 15. This
message is usually issued alone, but DWO546I might
be issued with this message. Explanation
Message Variables A control block overwrite of a DSISWB/DSICWB

control block was detected. The most common cause
task of this problem is a program that attempts to free the
The name of the task that failed. same control block twice at two different places using
macro the DSILCS macro.
The name of the macro that failed.
retcode System action
The return code in register 15 of the macro that A storage dump is taken and NetView processing
failed. continues.

The macro or function fails. Notify the system programmer.

Notify the system programmer. When the storage dump is complete, investigate the
reason for the control block overwrite. See the IBM Z
System programmer response NetView Troubleshooting Guide for more information
on debugging the problem. Consider recycling the
If the MDS_MU_SEARCH function failed, the return
NetView program as soon as possible to avoid other
codes are:
problems resulting from the control block overwrite.
0
Search successful. DWO159W A CONTROL BLOCK OVERWRITE
CONDITION WAS DETECTED, BUT
4
A STORAGE DUMP WAS NOT
Search failure.
REQUESTED
08
Field length is zero. Explanation
If the MDS_MU_DECODE function failed, the return
A control block overwrite of a DSISWB/DSICWB
codes are:
control block was detected. The most common cause
0 of this problem is a program that attempts to free the
Search successful. same control block twice at two different places using
4 the DSILCS macro.
Type for decoding request is not valid.
10 System action
Data truncated. A dump did not occur because the limit for the number
12 of storage dumps to occur for control block overwrite
Cursor is not valid. conditions (specified on the DEFAULTS STORDUMP
command) has been exceeded. Processing continues.
16
No parameter exists in the encoded data.
Operator response
18
Fatal. Notify the system programmer.
Otherwise, identify the problem by finding the return
code in IBM Z NetView Programming: Assembler. Take System programmer response
any necessary corrective action. If you need further If you have not been able to find the problem from
assistance, contact IBM Software Support. previous dumps, consider resetting the STORDUMP
counter with the DEFAULTS command to get a storage
DWO158W A CONTROL BLOCK OVERWRITE
dump if this problem reoccurs. Recycle the NetView
CONDITION WAS DETECTED, AND
program as soon as possible to avoid other problems.

DWO161I OPERATION SAVE FAILED FOR occurs and the type is FPINFO, this NetView program
type WITH QUALIFIER id might not acquire the correct focal point. If the
NetView program is brought down and restarted, the
Explanation program might not acquire the correct information
when it is restarted.
The SAVE request failed for the element described by
type and id.
Operator response
type
The type of data for which the request failed. This System programmer response
can be TIMER or FPINFO.
Message DWO165I, DWO166I, DWO167I, or
id DWO168I is issued with this message. See the system
The timer element identification, or MSCAPS if the programmer response of the associated message for
type is FPINFO. details of the failure.
System action DWO163I OPERATION DELETE FAILED FOR

type WITH QUALIFIER id
If the type is TIMER, the timer event remains in the
internal timer list but is not saved. If the type is Explanation
FPINFO, the focal point information is not saved to
VSAM. When a failure occurs and the type is FPINFO, The DELETE request failed for the element described
this NetView program might not acquire the correct by type and id.
focal point. Message Variables
Operator response type

The type of data for which the request failed. This
Notify the system programmer. can be TIMER or FPINFO.
id
System programmer response The timer element identification, or MSCAPS if the
Message DWO165I, DWO166I, DWO167I, or type is FPINFO.
DWO168I is issued with this message. See the system
programmer response of the associated message for System action
details of the failure.
If the type is FPINFO, the focal point information is not
DWO162I OPERATION RESTORE FAILED FOR saved to VSAM. The NetView program does not
type WITH QUALIFIER id attempt to perform a SAVE after the DELETE has
failed. When a failure occurs and the type is FPINFO,
Explanation this NetView program might not acquire the correct
focal point.
The RESTORE request failed for the element described
by type and id. Operator response
type
The type of data for which the request failed. This System programmer response
id DWO168I is issued with this message. See the system
The timer element identification, or MSCAPS if the programmer response of the associated message for
type is FPINFO. details of the failure.
System action DWO164I OPERATION REPLACE FAILED FOR

type WITH QUALIFIER id
If the type is FPINFO, the function was unable to re-
acquire any information that it might have had before
Explanation
the task was started. For FPINFO, the NetView
program is unable to send an MS capabilities The REPLACE request failed for the element described
revocation to any previous focal point. When a failure by type and id. REPLACE is a combination of RESTORE,

DELETE, and SAVE when type is FPINFO and id is DWO166I REASON FOR FAILURE: TASK NOT
MSCAPS. ACTIVE
Message Variables
Explanation
type
The type of data for which the request failed. This The request has failed because DSISVRT is inactive.
id System action
The timer element identification, or MSCAPS if the Message DWO161I, DWO162I, DWO163I, DWO164I,
type is FPINFO. DWO190I, DWO191I, DWO192I, or DWO193I is
issued before this message to indicate whether the
System action request type is SAVE, RESTORE, DELETE, or REPLACE.
If the type is FPINFO, one of the following occurs to
any focal point information in the VSAM database: Operator response
• The information is left intact if the failure occurred Notify the system programmer.
during RESTORE or DELETE.
• The information is erased if the failure occurred System programmer response
during SAVE. Activate the DSISVRT task.
When a failure occurs and the type is FPINFO, this DWO167I REASON FOR FAILURE:
NetView program might not acquire the correct focal DUPLICATE ID
point. If the NetView program is brought down and
restarted, the program might not acquire the correct
Explanation
information when it is restarted.
The request has failed because a duplicate TIMER
Operator response element has been found.

System action
System programmer response Message DWO161I, DWO162I, DWO163I, DWO164I,

DWO190I, DWO191I, DWO192I, or DWO193I is
Message DWO165I, DWO166I, DWO167I, or issued before this message to indicate whether the
DWO168I is issued with this message. See the system request type is SAVE, RESTORE, DELETE, or REPLACE.
programmer response of the associated message for
details of the failure.
Operator response
DWO165I REASON FOR FAILURE: STORAGE Notify the system programmer.
FAILURE
Explanation
If the request type is SAVE, a RESTORE has not been
The request has failed because of insufficient storage. issued for timer events since the NetView program
was started. An accurate saving of timer elements
System action requires that the saved timer elements be a subset of
Message DWO161I, DWO162I, DWO163I, DWO164I, the internal timer element list. If you require that the
DWO190I, DWO191I, DWO192I, or DWO193I is timer element be saved, purge the event from the
issued before this message, to indicate whether the internal timer list and issue the timer command again
request type is SAVE, RESTORE, DELETE, or REPLACE. with a unique ID.
DWO168I REASON FOR FAILURE: VSAM
Operator response ERRORS
Explanation
System programmer response The request has failed because of VSAM I/O errors.
Allocate more storage for the NetView program before
it is restarted.

Message DWO161I, DWO162I, DWO163I, DWO164I, hexcat
DWO190I, DWO191I, DWO192I, or DWO193I is The architecturally-defined hexadecimal value for
issued before this message to indicate whether the the category.
request type is SAVE, RESTORE, DELETE, or REPLACE. category
The EBCDIC value of the category.
Operator response
DWO173I type FOCAL POINT
Explanation
The FOCALPT QUERY command is returning
Correct the VSAM I/O errors before attempting any information about its focal point for the category
other action. listed. This message separates local focal point
information from remote focal point information. This
DWO169I REASON FOR FAILURE: INVALID
is part of a multiline message.
BUFFER LENGTH
Message Variables
Explanation type
The request has failed because of a buffer length that The type of focal point (either LOCAL or REMOTE).
is not valid. DWO174I APPL NAME: name ACTIVE: aind
System action
Explanation
Message DWO191I or DWO192I is issued before this
This message returns the local focal point application
message to indicate whether the request type is
name, and an indication of whether or not it is
RESTORE or DELETE.
currently active. The presence of an application name
indicates the presence of a local focal point
Operator response application. This is part of the information returned as
Notify the system programmer. a result of a FOCALPT QUERY command. This is part of
a multiline message.
Correct the buffer length before attempting any other name
action. The application name of the local focal point for
this category.
DWO170I DISPLAY OF CURRENT FOCAL
POINT INFORMATION aind
The active indicator:
Explanation Y
Active
This is the starting delimiter for information returned
as a result of issuing the FOCALPT QUERY command. N
This is the first line of a multiline message. Inactive
Processing continues. If the local focal point is supposed to be active, and it

is inactive, try to activate it.
DWO172I CATEGORY (ARCH): X'hexcat'
CATEGORY (EBCDIC): category DWO175I type NAME: name ACTIVE: aind
PENDING: pind
Explanation
Explanation
The FOCALPT QUERY command is returning
information about its focal point for the category This message returns the remote focal point
listed. The category information is returned in both application name, and an indication of whether or not
architected hexadecimal value and EBCDIC value. This it is currently active, or if acquisition of this focal point
is part of a multiline message. authorization is currently pending a response. This is

part of the information returned as a result of a Explanation
FOCALPT QUERY command. This is part of a multiline
There is currently no focal point (local or remote) for
message.
the category for this node. This is part of a multiline
Message Variables message.
type
The type of remote focal point (either PRIMARY or System action
BACKUP). Processing continues.
name
DWO179I FOCAL POINT CATEGORY category
The application name of the remote focal point for
IS NOT REGISTERED
this category. A NetView name in this field
indicates that the focal point is an LUC focal point.
A netid.nau name in this field indicates that the Explanation
focal point is an LU 6.2 focal point. There is currently no focal point category registered
aind for the category requested in the FOCALPT QUERY
The active indicator: command. This is part of a multiline message.
Y Message Variables
Active
category
N The focal point category requested.
Inactive
pind System action
The pending indicator. Y=currently pending.
DWO176I RETRY TIMER SET: sind
DWO180I NO MATCHING CATEGORIES ARE
REGISTERED
Explanation
If the remote focal point type is BACKUP, this indicator Explanation
lets you know whether the timer to retry the primary
There are currently no focal point categories
focal point has been set. This is part of a multiline
registered. This is part of a multiline message.
message.
sind Processing continues.
The primary focal point retry timer set. Y means
the NetView program tries to reacquire the primary DWO181I ALERT AND STATUS
focal point. N means the NetView program does INFORMATION MAY BE
not try to reacquire the primary focal point. INCOMPLETE : DSICRTR
INACTIVE
DWO177I THERE ARE CURRENTLY NO
FOCAL POINTS FOR CATEGORY
Explanation
category
A FOCALPT QUERY command was issued for category
Explanation ALERT or STATUS and the DSICRTR task was not
active. DSICRTR supports both SNA_MDS and NetView
There is currently no focal point (local or remote) for unique applications for the ALERT and STATUS
the category requested in the FOCALPT QUERY keywords. This message indicates that data cannot be
command. This is part of a multiline message. provided for NetView unique applications.
Message Variables
Operator response
category
The focal point category requested. Start the DSICRTR task and issue the command again.
DWO178I THERE ARE CURRENTLY NO DWO182I FOCALPT CHANGE STATUS
FOCAL POINTS FOR THIS NODE COMPLETED SUCCESSFULLY BUT

INITIATED -- THIS NODE IS A host must be defined as a status focal point. Recycle it
STATUS FOCAL POINT. as a status collector, and issue the FOCALPT CHANGE
STATUS command again if status forwarding is
Explanation desired. If the target ID was not correct, change it and
issue the FOCALPT CHANGE STATUS command again.
The status focal point was changed for this host but
this host is a status focal point. This is not correct. The DWO184E FOCALPT CHANGE COMMAND TO
target host in the FOCALPT CHANGE command must NODE node FOR STATUS FAILED:
be a status collector. Because status focal point hosts CNMTAMEL TASK MUST BE
do not communicate (synchronize) with other status ACTIVE AND DEFINED AS A
focal point hosts, no attempt was made to initiate this STATUS FOCAL POINT.
communication. That is, the synchronization series
was not initiated. Explanation
The FOCALPT CHANGE command for status failed
System action because either the CNMTAMEL task was not active, or
The status focal point for this host changes. it was active but not running as a status focal point.
Message Variables
Operator response
node
If you want to forward status data, start the The name of the distributed node.
CNMTAMEL task, defining this host as a status
collector. The host then begins sending status to its System action
status focal point. If you do not want to forward status
data, ignore the message. The status focal point is not changed.
DWO183E FOCALPT CHANGE STATUS

Operator response
ACCEPTED BY DISTRIBUTED
NODE node BUT Start the CNMTAMEL task if it is not active. If it is
SYNCHRONIZATION SERIES NOT active, stop the CNMTAMEL task and restart it as a
INITIATED -- DISTRIBUTED NODE status focal point.
IS A STATUS FOCAL POINT
COMPLETED SUCCESSFULLY BUT
Explanation SYNCHRONIZATION SERIES NOT
The distributed node received the FOCALPT CHANGE INITIATED -- REASON CODE
STATUS command and processed it successfully, but reason.
cannot communicate with this node because both
nodes are defined as status focal points. Therefore, no Explanation
attempt was made to initiate the synchronization
The status focal point for this host was changed, but
series between the two nodes.
this host cannot communicate (synchronize) with the
Message Variables new status focal point because of the reason code
reason. Therefore, no attempt was made to initiate the
node
synchronization series between the two hosts.
The name of the distributed node.
Message Variables
System action reason
The status focal point for the distributed node is The reason that the synchronization series cannot
defined as this node. be initiated.
Note: These errors occurred at this host.
Operator response
The reason code is one of the following values:
01
Cannot load the module DUIABUFF to build the
System programmer response buffer to initiate the synchronization series;
Verify that the target ID in the FOCALPT CHANGE installation error.
command was entered correctly. If it was, determine
whether or not the CNMTAMEL task on the distributed

02 (synchronize). Therefore, no attempt was made to
Cannot get storage to build the buffer to initiate the synchronization series between the two
initiate the synchronization series. nodes.
Cannot send the buffer to the CNMTAMEL task
to initiate the synchronization series. node
The name of the distributed node.
System action
System action
The status focal point for this host is changed.
The status focal point for the distributed node is
defined as this node.
Operator response
If you want to forward status data, notify the system Operator response
programmer. If not, ignore this message.
If you want to forward status data, contact IBM
Software Support. If not, ignore this message. Verify that the target ID in the FOCALPT CHANGE
command was entered correctly. If it was, contact an
DWO186I FOCALPT CHANGE STATUS operator at the distributed host to determine why the
COMPLETED SUCCESSFULLY BUT CNMTAMEL task is not active and therefore not
SYNCHRONIZATION SERIES NOT forwarding status information to this host. If the target
INITIATED -- CNMTAMEL TASK ID was not correct, change it and issue the FOCALPT
NOT ACTIVE. CHANGE STATUS command again.
Explanation
ACCEPTED BY DISTRIBUTED
The status focal point for this host has changed, but NODE node BUT
this host cannot communicate (synchronize) with the SYNCHRONIZATION SERIES NOT
new focal point because the CNMTAMEL task is not INITIATED -- REASON CODE
active. Therefore, the synchronization series to the reason.
new status focal point cannot be initiated.
Explanation
System action The distributed node received the FOCALPT CHANGE
The status focal point for this host has changed. STATUS command and processed it successfully, but
cannot communicate (synchronize) with the new
Operator response status focal point because of the reason code reason.
Therefore, no attempt was made to initiate the
If you want to forward status data, start the synchronization series between the two hosts.
collector. The host then begins sending status to its Message Variables
status focal point. If you do not want to forward status node
data, ignore the message. The name of the distributed node.
DWO187E FOCALPT CHANGE STATUS reason
ACCEPTED BY DISTRIBUTED The reason code indicating why the
NODE node BUT synchronization series cannot be initiated.
SYNCHRONIZATION SERIES NOT Note: These errors occurred at the distributed
INITIATED -- CNMTAMEL TASK node.
NOT ACTIVE.
Explanation 01
The distributed node received the FOCALPT CHANGE
buffer to initiate the synchronization series;
STATUS command and processed it successfully, but
installation error.
because the CNMTAMEL task is not active at the
distributed node, the two hosts cannot communicate

Cannot get storage to build the buffer to
initiate the synchronization series.
DWO168I is issued with this message. See the system
03 programmer response of the associated message for
Cannot send the buffer to the CNMTAMEL task details of the failure.
to initiate the synchronization series.
DWO191I OPERATION RESTORE FAILED FOR
type
System action
The status focal point for the distributed node has Explanation
been defined as this host.
The RESTORE request failed for the element described
by type.
Operator response
Message Variables
type
System programmer response The type of data for which the request failed. This
can be TIMER, FPINFO, or GLOBALV.
DWO189I END OF CURRENT FOCAL POINT System action
INFORMATION If the type is FPINFO or GLOBALV, the function was
unable to reacquire any information that it might have
Explanation had before the task was started. For FPINFO, the
This is the ending delimiter for information returned as NetView program is unable to send an MS capabilities
a result of issuing the FOCALPT QUERY command. This revocation to any previous focal point. When a failure
is the last line of a multiline message. occurs and the type is FPINFO or GLOBALV, this
NetView program might not acquire the correct focal
point. If the NetView program is brought down and
System action restarted, the program might not acquire the correct
Processing continues. information when it is restarted.
DWO190I OPERATION SAVE FAILED FOR

Operator response
type
Explanation
The SAVE request failed for the element described by
type. Message DWO165I, DWO166I, DWO168I, DWO169I,
or DWO398I is issued with this message. See the
Message Variables
system programmer response of the associated
type message for details of the failure.
can be TIMER, FPINFO, or GLOBALV. DWO192I OPERATION DELETE FAILED FOR
type
System action
Explanation
If the type is TIMER, the timer event remains in the
internal timer list but is not saved. If the type is The DELETE request failed for the element described
FPINFO or GLOBALV, the focal point or global variable by type.
information is not saved to VSAM. When a failure Message Variables
occurs and the type is FPINFO or GLOBALV, this
NetView program might not acquire the correct focal type
point. The type of data for which the request failed. This
can be TIMER, FPINFO, or GLOBALV.
Operator response

System action DWO195I VTAM MACRO macid FAILURE FOR
TASK taskid: RTNCD = X'vtamrc',
If the type is FPINFO, the focal point or global variable
FDBK2 = X' vtamfb'.
information is not saved to VSAM. The NetView
program does not attempt to perform a SAVE after the
DELETE has failed. When a failure occurs and the type Explanation
is FPINFO or GLOBALV, this NetView program might A VTAM macro failure occurred for the task, which
not acquire the correct focal point. might have caused the task to end. The return and
feedback codes associated with the failure are shown.
Operator response
Message Variables
macid
The name of the VTAM macro returning the error.
taskid
Message DWO165I, DWO166I, DWO168I, DWO169I, The name of the task where the failure occurred.
vtamrc
The VTAM RPL return code.
message for details of the failure.
vtamfb
DWO193I OPERATION REPLACE FAILED FOR The VTAM RPL feedback code.
type
System action
Explanation
If the session ended, the NetView program does not
The REPLACE request failed for the element described restart the session.
by type.
type Notify the system programmer.
can be TIMER, FPINFO, or GLOBALV. System programmer response
Use the RCFB command list to determine the meaning
System action
of the return/feedback code.
If the type is FPINFO or GLOBALV, one of the following
DWO196I THE FOLLOWING MSU RECORD IS
occurs to any focal point information in the VSAM
database: INVALID
• The information is left intact if the failure occurred Explanation

during RESTORE or DELETE.
The command facility has a table of valid MSU types.
• The information is erased if the failure occurred
The MSU being examined is not contained in this table
during SAVE.
or the MSU has a format error. See Systems Network
When a failure occurs and the type is FPINFO or Architecture Formats and the Systems Network
GLOBALV, this NetView program might not acquire the Architecture Management Service Reference for
correct focal point. If the NetView program is brought information on MSUs.
down and restarted, the program might not acquire the
Messages DWO197I and DWO198I follow this
correct information when it is restarted.
message.
Operator response
System action
No further processing is done on this MSU.

Operator response
Message DWO165I, DWO166I, DWO168I, DWO169I,
message for details of the failure.

Determine the device generating the MSU, obtain a Notify the system programmer.
copy of the associated DWO197I message from the
network log, and contact IBM Software Support. System programmer response
DWO197I data If VTAM is not active, bring up VTAM. If VTAM is active,
analyze the ACB error. Refer to the appropriate VTAM
Explanation manual for more information. The most probable
cause of the error is an incorrect definition of NetView
This message follows a command facility message. application IDs applids or passwords to VTAM.
The preceding message indicates why the command
facility rejected the data. DWO197I contains the DWO200I INTERNAL ERROR IN MODULE
vectorized data that was rejected (for example, an module , FUNCT = function -
MDB or MSU). Multiple DWO197I messages can be ABENDING
used to display all of the data. The message can be
longer than the width of the operator's console, so use Explanation
the network log to view all of the data. The last
DWO197I message is followed by DWO198I. The NetView program encountered an internal logic
error.
See the message that preceded this message. module
The module that issued this message.
The type of service that failed.
System action
The request is not processed and VPDTASK ends with
See the message that preceded this message.
abend code 27 (X'1B').
DWO198I END
Operator response
Explanation
This message indicates the end of a multiline
message. System programmer response
DWO199I UNABLE TO PROCESS VTAM Contact IBM Software Support.
COMMAND 'command'. TASK ACB
IS NOT OPENED. DWO201I EXTENDED CONSOLE 'console'
REACHED THE CONSOLE
STORAGE LIMIT. SYSTEM
Explanation
MESSAGE QUEUING TO THIS
The NetView program has not been able to forward the CONSOLE IS TEMPORARILY
VTAM command that the operator entered to the HALTED.
VTAM address space. The task ACB has not yet been
opened. Explanation
Message Variables The MVS system messages queued to the specified
command console have completely filled the storage allocated
The VTAM command that was entered by the for the specified console.
operator. Message Variables
console
System action
The name of the console affected.

System action QLIMIT keywords, see the GETCONID command in the
NetView online help.
Message queuing to the specified console ends. The
NetView program retrieves system messages until all Note: System messages can be lost while message
the messages in the extended console's queue are queuing to the specified extended console is halted.
processed. When all of the queued system messages
DWO203I AN INTERNAL ERROR OCCURRED
have been processed, system message queuing to the
IN THE MESSAGE QUEUE FOR
specified console is automatically resumed.
EXTENDED CONSOLE 'console'.
THIS CONSOLE WILL BE
Operator response RELEASED BY TASK 'task'.
Explanation
System programmer response An MVS error occurred from which the NetView
Determine whether the STORAGE and QLIMIT settings program cannot recover.
need adjustment. If you received this message without Message Variables
first receiving DWO202I or DWO204I, the storage
allocated for the specified console is not large enough console
to contain the number of messages specified in The name of the console affected.
QLIMIT. For information on the STORAGE and QLIMIT task
keywords, see the GETCONID command in the The name of the task.
NetView online help.
Note: Messages can be lost while message queuing is System action
halted. All messages that can be retrieved are processed, and
DWO202I EXTENDED CONSOLE 'console' the console is inactivated.
REACHED THE QUEUE LIMIT.
MESSAGE QUEUING TO THIS Operator response
EXTENDED CONSOLE IS
TEMPORARILY HALTED.

Explanation
An error has occurred in the MVS message queue. Try
The maximum number of messages as specified by
to restart the console. If the problem persists, contact
QLIMIT has arrived for processing by the specified
extended console.
Message Variables DWO204I EXTENDED CONSOLE 'console'
REACHED THE MESSAGE
console QUEUING THRESHOLD
Explanation
System action
The extended console has reached the defined
Message queuing to the specified console ends. The ALERTPCT limit.
NetView program retrieves and processes messages.
Message queuing resumes automatically when the Message Variables
queue reaches the set QRESUME percentage. console
Operator response
Message queuing and processing continue.
Determine whether the settings for QLIMIT, Operator response
QRESUME, and STORAGE need adjustment. If you Notify the system programmer.
raise the QLIMIT, you might also have to adjust the
STORAGE value. For information on the STORAGE and

System programmer response REXX, or HLL command procedure which invoked the
PIPE command.
Determine whether the ALERTPCT definition for the
specified console needs to be changed. If this Message Variables
message is received frequently and the QLIMIT is
stemvar
never reached (message DWO202I), you might want to
The STEM variable containing the expected record
raise the ALERTPCT or QLIMIT value. Adjust the
count.
ALERTPCT value so that this message is issued only
when the queue limit exceeds your expectations for maxstem
the specified console. Redirect message traffic to The maximum allowed STEM variable record
another extended console, if possible. For information count.
on the ALERTPCT keyword, see the GETCONID value
command in the NetView online help. The value of stemvar, which was not a valid record
count.
DWO205I A SYSTEM REQUEST TO RELEASE
EXTENDED CONSOLE 'console'
HAS BEEN RECEIVED BY TASK System action
'task'. The STEM is rejected and the PIPE command fails.

A system request to inactivate the extended console Notify the system programmer.
has been received.
console Set the stemvar variable to a valid number before
The name of the console affected. using the STEM stage as a first stage. Also, a stage
task STEM with the APPEND option requires the stemvar
The name of the task that received the request. variable to be a valid number.
DWO207I TRACING TO GTF FAILED WITH
System action RETURN CODE retcode
Queued messages are retrieved and processed, and
the console is released. Explanation
The NetView program can no longer write trace
Operator response records to the generalized trace facility (GTF).
System action
System programmer response Tracing to GTF stops.
This message appears when an MVS console SWITCH
command for the specified console has been entered. Operator response
If the SWITCH command was entered in error, issue See the return codes from the GTRACE macro to
the GETCONID command with the appropriate determine the problem. Correct the problem with GTF.
parameters to reactivate the console.
DWO208I NETVIEW TRACING TO GTF HAS
DWO206I VARIABLE 'stemvar' RECORD RESUMED
COUNT MUST BE ZERO OR
POSITIVE AND NOT LARGER THAN
Explanation
maxstem: 'value'
The problem that caused tracing to the generalized
Explanation trace facility (GTF) to cease has been fixed.
The STEM variable stemvar did not have a valid record

System action
count. The record count must be zero or a positive
number and not larger than maxstem. NetView resumes writing trace records to GTF.
If 'value' = 'stemvar', the variables being accessed by DWO209I Match not found for direction
the STEM stage have not been initialized in the clist, search_parms

A search has failed to find any records matching the Notify the system programmer.
search parameters.
direction If loc is LOC 01, contact IBM Software Support. If loc is

LOC 02, use the DISPPI and SETBQL commands to
A plus sign (+) indicates a search from older to display and change the Program to Program Interface
newer records. receiver queue for DUIATMGR.
A minus sign (-) indicates a search from newer
to older records. DWO211I task NO LONGER ENCOUNTERING
CONGESTION SENDING DATA TO
search_parms CNMTAMEL. loc
The parameters for the search in question.
Explanation
Operator response
The task task is able to send data to CNMTAMEL again.
Issue a new search request, possibly in the opposite loc indicates the type of congestion no longer
direction. occurring.
Message Variables
task
If a message is not found in Canzlog but is expected or
The name of the task encountering congestion.
has been previously seen in a browse session, the
reason might be archive management. If your Canzlog loc
archive data has been trimmed for space (or you have 'LOC 01' indicates the number of unacknowledged
chosen not to archive the Canzlog data), then the requests sent to CNMTAMEL below the threshold.
missing message might be in the data that was 'LOC 02' indicates the Program to Program
removed (or not written). Issue the TOP subcommand interface buffer is no longer full.
from your Canzlog browse session. Note the date and
time of the topmost message. If the date and time of System action
the missing message is earlier than this, then the
When task is the DSIAL2WS task, alerts will be sent to
problem can be addressed by restoring Canzlog data
the workstation.
for the appropriate time range.
DWO212I task1 IS ABLE TO COMMUNICATE
DWO210I task ENCOUNTERING
WITH task2
CONGESTION SENDING DATA TO
CNMTAMEL. loc
Explanation
Explanation The task task1 is able to use task or function task2.
The task task is unable to send data to CNMTAMEL Message Variables
because of congestion. loc indicates the type of
task1
congestion.
The name of the task attempting to use functions
Message Variables provided by task2.
task task2
The name of the task encountering congestion. The name of the task or function being used by
task1.
loc
'LOC 01' indicates the maximum number of DWO213I 'task1' IS UNABLE TO
unacknowledged requests have been sent. 'LOC COMMUNICATE WITH 'task2'.
02' indicates the CNMTAMEL Program to Program WILL RETRY IN sec SECONDS.
interface buffer is full.
Explanation
System action
The task task1 is unable to use services provided by
When task is the DSIAL2WS task, alerts will no longer task2. task1 will retry in sec seconds.
be sent to the workstation until the congestion stops.
Message Variables

task1 luname
The name of the task attempting to use functions The name of the LU to which the DSIAL2WS task
provided by task2. cannot send alerts.
task2 loc
The name of the task or function unavailable to The loc will indicate why DSIAL2WS stopped
task1. If task2 is Program to Program interface, sending alerts. A '01' indicates that the LU sent a
verify the Program to Program interface is active. If stop request, a '02' indicates that the session went
task2 is CNMTAMEL, verify that the CNMTAMEL down, a '03' indicates that the send failed and a
task is active and functioning as a status focal '04' indicates that the receiver at the LU was
point. If task2 is a NetView domain, verify the unable to forward the alert.
following: rc
• The Hardware Monitor is active on the host The return code.
designated by task2
• SNA connectivity between this host and the host System action
designated by task2 The DSIAL2WS task will no longer send alerts to
If task2 is an IP address or an IP host name, verify luname.
the following:
Operator response
• The Hardware Monitor and DSIRTTR are active
on the host designated by task2 Use the loc code to determine why the message is
• IP connectivity between this host and the host being issued and take corrective action, if necessary.
designated by task2 DWO294I NO CLIENTS IN CONFIGURATION.
sec service IS DISABLED.
The number of seconds until retry.
Explanation
System action The service or command named cannot function
task1 will retry to use the services of task2 in sec without configuration.
seconds. Message Variables
DWO214I ALERTS WILL BE SENT TO LU= service
luname. A service or a command that requires
configuration.
Explanation
The DSIAL2WS task has successfully processed a System action
request from luname and will now forward alerts to it. The service named is disabled.
This message is written to the NetView log only.
luname Notify the system programmer.
The name of the LU to which the DSIAL2WS task
will send alerts. System programmer response
Determine and follow the proper configuration for the
System action specified service.
The DSIAL2WS task will now send alerts to luname If the service is APSERV, see the APSERV.PREFIX
DWO215I NO LONGER SENDING ALERTS TO statements in the IBM Z NetView Administration
LU= luname. LOC= loc RC= rc, Reference and the APSERV command in the IBM Z
NetView Command Reference Volume 1 (A - N).
Explanation DWO295I Command changed by
The DSIAL2WS task has determined that it is unable to procedure_name
send alerts to luname and will no longer forward alerts
to it. This message is written to the NetView log only.
Message Variables

Explanation header are from an incomplete message received over
sessid. The message is displayed when a transmission
This message is issued as a result of a REISSUE
is received, but not complete, and a time-out period
command, following a NETVONLY action by the
expires.
Command Revision Table. The DWO295I message is
issued only when the ISSUE.IEE295I=YES option was This message is often displayed after a session is
used when loading the Command Revision Table. established with VM/SNA console services (VSCS),
since this application deliberately sends an incomplete
This is the first line of a multiline message. The second
message as part of its startup procedure. The text of
and third lines show the command before and after the
this incomplete message instructs you to PRESS ATTN
changes made by the REXX procedure named in the
KEY. To perform this function over a TAF OPCTL
DWO295I message.
session, enter:
Message Variables
SENDSESS sessid,*
procedure_name
The name of the NETVONLY REXX procedure that Message Variables
caused a change to the MVS command being
revised. sessid
The session ID for the session displaying an
DWO296I Time expired for message search. incomplete message.
Press keySpec to continue.
Operator response
Explanation
The text of the message can indicate what action is
A request has taken longer than the time allowed for it. required. If it does not, notify the system programmer.
If you are browsing Canzlog data, the time allowed is
determined by the setting of DEFAULTS CZBRWAIT. System programmer response
Message Variables Determine the reason for the message not being
keySpec complete. If an attention signal (SENDSESS
The name of a keyboard action (programmed sessid,*) is not appropriate, the session must be
function key or Enter key) that will continue the stopped and restarted. This must not occur.
request that timed out. If no key is defined for the DWO311E MEMBER member IS NOT VALID
operation, a command is named instead. FOR TASK task. TASK ABORTED.

The request is suspended. The initialization member specified is not a valid
initialization member for the task specified.
Operator response
Message Variables
Use the key or command named to continue or enter a
different command. On the Canzlog display, take note member
of the time range in the upper right corner. If an The initialization member or file for the specified
operation repeatedly times out, the times reported in task.
the display will indicate how far your search has task
proceeded. The name of the task to be started.

If time expires frequently, consider increasing the The specified task fails.
value of DEFAULTS CZBRWAIT.
DWO310I FOR SESSION sessid, THE Operator response
FOLLOWING MESSAGE(S) ARE Use the default initialization member or specify a valid
WAITING: initialization member for the task specified.
DWO312I REQUEST TO NODE node FAILED.
Explanation
SNA SENSE CODE OF X'sensecode'
This message is the header line for a multiline write- RETURNED.
to-operator (MLWTO) message. The lines following this

A focal point request to a node failed because the You issued a FOCALPT command with the BACNET=*
node does not support the requested function. operand, but the attempt to resolve the backup netid
was not successful.
Message Variables
Message Variables
node
The node to which the command was directed command
sensecode The command that issued the request.
The sense code returned from the node
System action
System action No backup focal point node is assigned.
Processing of the command ends.
Operator response
Operator response Check that the backup LU name is valid. If it is valid,
Notify the system programmer. issue the FOCALPT CHANGE command again with the
LU name's netid. If this does not correct the problem,
notify the system programmer.
Check the sense code in the Systems Network System programmer response
Architecture library and take corrective action.
Identify a valid backup node and issue the FOCALPT
DWO313I NODE node RESPONDED WITH A CHANGE command again with the valid backup node's
SENSE CODE OF X'sensecode'. netid.
DWO315I MAXIMUM RETRY COUNT HAS
Explanation
BEEN EXCEEDED FOR id1 id2. THE
The node you attempted to acquire does not support SESSION WITH id1 HAS BEEN
the function requested. TERMINATED.
Message Variables
Explanation
node
The node to which the command was directed The specified subtask ended abnormally because the
maximum allowed number of times (MAXABEND) has
sensecode been exceeded. If the subtask was running under an
The sense code returned from the node OST, id1 specifies the terminal that was logged off and
is no longer in the NetView session. A RESET IMMED
System action or STOP UNCOND command might have also caused
this message to be displayed.
Note: The MAXABEND count for a task will be reset to
Operator response zero if the task has run for at least one hour since the
last abend.
Message Variables
System programmer response id1
The name of the logical unit for an OST or a task
Check the sense code in the Systems Network
identifier.
Architecture library and take corrective action.
id2
DWO314I COMMAND command WAS The operator identifier for an OST or further task
UNABLE TO RESOLVE THE identification.
BACKUP NETID. BACKUP IS
DEFAULTED TO BLANKS.
System action

Operator response dump if this problem reoccurs. Recycle the NetView
program as soon as possible to avoid other problems.
DWO320I task IS ACTIVATING WITH
System programmer response SECURITY LEVEL: seclevel
For an OST, the specified operator ID is available to

Explanation
the NetView program. The operator can log back on to
the NetView program. Depending upon the cause of The DSIUDST task is activating and the RMTSECUR
the MAXABEND, the NetView program might have statement coded in the initialization member for this
dumped the specified operator ID. You can restart the task determines what security is used for incoming
failing task using the START command. RMTCMD and ENDTASK requests. This message
informs the task starter what the security setting is. If
DWO316W A STORAGE OVERLAY CONDITION
there is no RMTSECUR statement in the initialization
WAS DETECTED, BUT A STORAGE
member, then NONE is assumed and no security is
DUMP WAS NOT REQUESTED
used with DSIUDST.
The DSIFRE or DSIGET storage macro service task

detected that storage was overlaid or that internal The task that is activating (DSIUDST).
storage table damage occurred. Possible reasons are: seclevel
The security level coded on the RMTSECUR
• A program moved data beyond the end of the
statement in the initialization member for
storage it owned.
DSIUDST.
• A DSIFRE specified the wrong length for the storage
being freed. DWO321I command REJECTED: operatorid
ON networkid.domainid IS NOT
• A DSIFRE was used to free storage that was not
AUTHORIZED FOR autotask ON
owned using DSIGET. The storage area specified
rejnetworkid.rejdomainid
overlaps storage that NetView is managing.
• NetView storage management tables have been
Explanation
overlaid.
This message is routed to an operator who issues a
If the error is detected by the DSIFRE service,
RMTCMD or ENDTASK command that is rejected by
message DWO115W is also issued. DWO115W
the target NetView program's DSIUDST security. An
describes the storage being freed and the task where
unauthorized RMTCMD or ENDTASK request indicates
the DSIFRE was invoked.
that the security software defined at the target of the
If the problem was detected by the DSIGET service, RMTCMD or ENDTASK command was unable to
message DWO115W is not issued. NetView detected a validate the request. This generally indicates that
problem in the tables needed to obtain storage for the security definitions do not permit the request, but
request. might also result from various errors with the security
software. See the system programmer response for
System action more information.
A dump did not occur because the limit for the number Message Variables
of storage dumps to occur for storage overlay command
conditions (specified on the DEFAULTS STORDUMP The requested command (RMTCMD or ENDTASK).
command) has been exceeded. Processing continues.
operatorid
The operator ID of the RMTCMD or ENDTASK
Operator response issuer, or the operator ID of the originator of the
Notify the system programmer. request that eventually resulted in the RMTCMD or
ENDTASK that is rejected, depending on a setting
in the rejecting NetView program.
networkid
If you have not been able to find the problem from The network ID of the RMTCMD or ENDTASK
previous dumps, consider resetting the STORDUMP issuer, or the network ID of the originator of the
counter with the DEFAULTS command to get a storage request that eventually resulted in the RMTCMD or

ENDTASK that is rejected, depending on a setting Explanation
This message is routed to the authorized receiver
domainid whenever the security being used by the DSIUDST task
The domain ID of the RMTCMD or ENDTASK issuer, rejects an incoming RMTCMD or ENDTASK request. An
or the domain ID of the originator of the request unauthorized RMTCMD or ENDTASK request indicates
that eventually resulted in the RMTCMD or that the security software defined at the target of the
ENDTASK that is rejected, depending on a setting RMTCMD or ENDTASK command was unable to
in the rejecting NetView program. validate the request. This generally indicates that
autotask security definitions do not permit the request, but
The autotask that was the target of the RMTCMD or might also result from various errors with the security
ENDTASK request. software. See the system programmer response for
more information.
rejnetworkid
The network ID of the NetView program that Message Variables
rejected the request.
operatorid
rejdomainid The operator ID of the RMTCMD or ENDTASK
The domain ID of the NetView program that issuer, or the operator ID of the originator of the
rejected the request. request that eventually resulted in the RMTCMD or
System action in the rejecting NetView program.
The request is ignored and message DWO322 is networkid
routed to the authorized receiver on the target The network ID of the RMTCMD or ENDTASK
NetView system to inform the receiver of the issuer, or the network ID of the originator of the
unauthorized request. request that eventually resulted in the RMTCMD or
Operator response
domainid
Notify the system programmer. The domain ID of the RMTCMD or ENDTASK issuer,
or the domain ID of the originator of the request
System programmer response that eventually resulted in the RMTCMD or
Determine whether the request must be authorized
and if so, update the security being used in the target
NetView program's DSIUDST task. The LIST DSIUDST command
command issued on the target NetView system shows The requested command (RMTCMD or ENDTASK).
the current security setting of the task. localautotask
Note: This message might also result from various The local autotask that was the target of the
errors or availability with the security software at the RMTCMD or ENDTASK request.
target of the RMTCMD or ENDTASK command. For tarnetworkid
example, when using SAF security if the SAF product is The target network ID of the RMTCMD or ENDTASK
no longer available or active or the RMTOPS class is request.
not active then RMTCMD and ENDTASK requests will tardomainid
be rejected. To determine the error in these situations, The target domain ID of the RMTCMD or ENDTASK
it might be helpful to recycle the DSIUDST task at the request.
target and review the system and network logs for any
messages issued during DSIUDST initialization. Such
messages can help determine any problems with the System action
security software. The RMTCMD or ENDTASK command is ignored. The
operator who issued this request is notified by
DWO322I operatorid ON networkid.domainid
message DWO321 that the request was rejected
ISSUED AN UNAUTHORIZED
command REQUEST FOR
localautotask ON System programmer response
tarnetworkid.tardomainid Determine whether the request must be authorized. If
the request is allowed, use the LIST DSIUDST
command to determine the security level of DSIUDST
and update the appropriate security environment.

Note: This message might also result from various System programmer response
errors or availability with the security software at the
Determine the problem associated with the SAF return
target of the RMTCMD or ENDTASK command. For
code. Correct the problem and restart or recycle the
example, when using SAF security if the SAF product is
DSIUDST task to allow SAF security to be used.
no longer available or active or the RMTOPS class is
not active then RMTCMD and ENDTASK requests will If retcode is 255, there was a severe error when the
be rejected. To determine the error in these situations, task tried to use the interface to the NetView save
it might be helpful to recycle the DSIUDST task at the segment. This is probably because of an installation
target and review the system and network logs for any error associated with the save segment.
messages issued during DSIUDST initialization. Such
DWO324I NO VALID secclass SECURITY
messages can help determine any problems with the
STATEMENTS FOUND IN member
security software.
DWO323I SAF SECURITY ENVIRONMENT Explanation
FAILED TO CREATE WITH SAF
RETURN CODE retcode Either no statements of the security class were found
in the specified member, or none of the statements for
a particular security class were valid.
Explanation
Message Variables
The RMTCMD data services task (DSIUDST) was
unable to successfully create an SAF environment secclass
using the RACROUTE Security class (RMTSEC).
REQUEST=VERIFY,ENVIR=CREATE macro. member
When the DSIUDST task activates, the NetView The DSIPARM member containing the security
program attempts to create an SAF environment. This statements.
environment is used for RMTCMD security checking,
unless SAFREFSH=NO is specified on the RMTSECUR System action
card in the DSIUINIT initialization member or unless
A RMTCMD security table is not built for the specified
RMTINIT.SAFrefresh=No is specified in the CNMSTYLE
security class.
member.
This SAF security environment is created even when System programmer response
SAF security is not explicitly requested to allow the
REFRESH command to dynamically switch to SAF Correct the missing or incorrect statements in the
security checking. To prevent the creation of the SAF specified member.
environment, specify RMTINIT.SAFrefresh=No in the
DWO325W REFRESH COMMAND FAILED.
CNMSTYLE member.
DSIUDST IS INACTIVE.
Message Variables
retcode Explanation
The SAF return code returned by the RACROUTE Required task DSIUDST was not active. No changes to
REQUEST=VERIFY,ENVIR=CREATE macro. the RMTCMD security were made.

SAF security is disabled for DSIUDST. If the DSIUDST The command is ignored.
task is initializing and SAF is coded on the RMTSECUR
card of the initialization member, DSIUDST is not
Operator response
allowed to initialize. For security settings of TABLE or
NONE, if an ACEE is not successfully created, DSIUDST Start task DSIUDST.
activates and the refresh command does not allow a
DWO326I SAF INITIALIZATION FAILED. SAF
switch to SAF.
PRODUCT IS NOT AVAILABLE.
Operator response
Explanation
The user specified SAF on the REFRESH command, but
there was no SAF product installed, or DSIUDST was

unable to create the necessary environment for the System programmer response
SAF product.
Correct the statement in the RMTCMD security table.
System action DWO329W SYNTAX ERRORS ENCOUNTERED

WHILE BUILDING secclass
The command is ignored. SECURITY TABLE

Start the SAF product. Recycle DSIUDST to initialize Syntax errors were found in the RMTCMD security
the SAF environment. table for statements pertaining to a particular security
DWO327I secclass SECURITY REFRESHED class.
FROM oldvalue TO newvalue BY Message Variables
operatorid
secclass
Security class (RMTSEC).
Explanation
This message is sent to the operator who started the System action
DSIUDST task.
If one or more valid statements are found, the security
Message Variables table is built.
secclass
Security class (RMTSEC). System programmer response
oldvalue Correct the statements in the RMTCMD security table.
Old security class (NONE|TABLE|SAF).
DWO330I secclass SECURITY TABLE HAS
newvalue
BEEN INITIALIZED
New security class (TABLE|SAF).
operatorid Explanation
The operator who entered the REFRESH
command. The RMTCMD security table has been created by
starting the DSIUDST task or by issuing the REFRESH
DWO328W BACK SLASH NOTATION command.
SPECIFIED IN THE secclass
SECURITY TABLE IS IN ERROR Message Variables
secclass
Explanation Security class (RMTSEC).
The BACKSLASH (\) notation used in the TARGOP and DWO331E secclass SECURITY TABLE HAS
RMTOP keywords on the RMTSEC statement in the FAILED TO INITIALIZE
RMTCMD security table is not valid. The backslash
must appear as the first character in both keywords. If Explanation
neither keyword is specified on the RMTSEC
statement, the default is the backslash notation. The RMTCMD security table for a particular security
class was not created because of severe errors.
Note: Use the backslash notation when the intention is
for both the TARGOP and the RMTOP to have the same Message Variables
operator ID. secclass
Message Variables Security class (RMTSEC).
secclass
System action
Security class (RMTSEC).
The RMTCMD security table is not created. Any
System action authorization calls to the table result in an
unauthorized response.
The statement is ignored. Processing of the RMTCMD
security table continues.

System programmer response THIS TERMINATING TASK - TASK
TERMINATION CONTINUES.
Determine the reason for the failure from the previous
error message. Correct the problem and use the
REFRESH command to rebuild the table. Explanation
DWO332I DISTRIBUTED AUTOTASK Task termination was unable to complete processing

autooper ON rmtnet.rmtdomain of task's message queues. An attempt to free the
FAILED TO BEGIN PROCESSING storage causes unpredictable results.
THE FOLLOWING COMMAND: Message Variables
'cmdtext'
task
Is the LU name of the task, if the task is a data
Explanation services task (DST). If the task is an operator
A RMTCMD command was entered and the command station task (OST), this is the operator ID of the
text of the RMTCMD command was passed to the operator.
destination distributed autotask. However, the
distributed autotask ended before processing the System action
command. This message is generated for each
RMTCMD command that failed to process. Task termination continues, but task's queued
messages are not freed.
Message Variables
autooper Operator response
The operator ID of the distributed autotask that Notify the system programmer.
did not process the command.
rmtnet.rmtdomain System programmer response
The network identifier for the NetView program in
which the distributed autotask did not process the This message is preceded by message DSI528I or
command. DSI529I and, possibly, a task abend. Determine the
cause of the error and restart the NetView program to
cmdtext
reclaim the lost resources.
The command text that the distributed autotask
was unable to process. The command text is DWO334I THE secclass SECURITY TABLE
truncated at 100 characters. HAS BEEN REFRESHED.

The command that was passed to the distributed This message is sent to the operator who started the
autotask is not processed. DSIUDST task. It informs the operator that the
RMTCMD security table statements have been
Operator response refreshed.
Issue the RMTCMD command again. This establishes Message Variables
the session again if the distributed autotask is not secclass
already in use. The command text is then passed to Security class (RMTSEC).
the distributed autotask again for processing. If
reissuing the RMTCMD command fails, notify the DWO335E HARDWARE MONITOR
system programmer. ENCOUNTERED AN INTERNAL
ERROR. UNEXPECTED RESULTS
System programmer response MAY OCCUR AS PROCESSING
CONTINUES.
If the distributed autotask ended as a result of an
ENDTASK FORCE command, determine whether this
Explanation
request must be authorized and update your RMTCMD
security table to limit the use of the ENDTASK The hardware monitor encountered an internal error
command. during processing from which it cannot fully recover.
The error might also have occurred while processing a
DWO333W task: WARNING, UNABLE TO hardware monitor command.
DEALLOCATE RESOURCES FOR

This message is accompanied by message DWO050E System action
in the network log to assist IBM Software Support in
The active distributed autotasks established by the
debugging internal NetView errors. In the case of a
operator receiving this message, and the remote
failing hardware monitor command, message
NetView program being reported on remain active.
DWO069E is also issued.
Operator response
System action
Hardware monitor processing continues, but
unexpected results might occur.
Operator response If this message is issued because the DSIUDST or
DSIHPDST tasks are not active, restart them. Issue the
ENDTASK STOP or ENDTASK FORCE command to end
the sessions after the communications path has been
System programmer response established again.
Stop and restart the BNJDSERV task to reinitialize the DWO337I TASK 'task' OBTAINED EXTENDED
hardware monitor. If your system is in a state where it CONSOLE 'console'.
cannot recycle the BNJDSERV task, delay recycling.
However, unexpected results might occur as hardware
Explanation
monitor processing continues. If the message persists,
contact IBM Software Support. The specified extended console was obtained by the
specified task.
DWO336I DISTRIBUTED AUTOTASK
autooper ON autonet.autodomain Message Variables
NOT TERMINATED
task
The name of the task that issued the GETCONID
The RMTCMD command was issued to establish a console
session with a distributed autotask on a remote node. The name of the console specified by the
The RMTCMD issuer who established this session GETCONID command.
logged off, causing a request to be sent to the remote
node to end all active autotasks started by the issuer. System action
This message indicates that the communication path
between the RMTCMD issuer who logged off and the Processing continues.
issuer's autotasks is not available. Therefore, the DWO338I CONSOLE NOT OBTAINED FOR
distributed autotasks were not ended. This message is
TASK 'task'. CONSOLE 'console' IS
usually issued because the DSIUDST or DSIHPDST
ALREADY IN USE.
tasks were inactive at the time the RMTCMD issuer
logged off.
Explanation
Note: For TCP/IP remote operations, the DSIHPDST
task is not involved, but if host names are used task You attempted to obtain an MVS extended console by
DUIDGHB is used. issuing a GETCONID command or an MVS command.
The console name requested is already being used in
Message Variables the system or sysplex.
autooper Message Variables
The operator ID of the distributed autotask that
was not ended. If the value is ALL, all distributed task
autotasks on the remote node started by the The name of the task that attempted to obtain the
RMTCMD issuer were not ended. console.
autonet console
The network ID of the distributed autotasks that The name of the console that was requested.
were not ended.
System action
autodomain
The domain id of the distributed autotasks that No console is obtained. If the command was MVS, the
were not ended. system command that was entered is not executed.

Operator response DWO340E 'command' 'definition' WAS NOT
FOUND
Use the GETCONID or SETCONID command to specify
a different console name to be used by the task. If you
continue to have problems obtaining a console, notify Explanation
the system programmer. The command cannot read the specified definitions.
Definitions with that name were not found.
Message Variables
Ensure that all NetView operators who need to issue
command
MVS system commands are able to access the
The name of the command
necessary consoles. Each console name must be
unique within each system or sysplex. Console names definition
for multiple console support or subsystem consoles The name of the definitions
defined in the CONSOLxx data sets for your system or
sysplex cannot be used as extended console names. System action
If you are running the NetView program in the The command is not processed. The previous
extended console mode, use the ConsMask statement definitions remain in effect.
in the CNMSTUSR member to generate unique console
names (see the CNMSTYLE member for more Operator response
information), or use the GETCONID or SETCONID
command in each operator's initial command list to Check for spelling errors. If the definition name is
obtain a unique name. Otherwise, the first MVS spelled correctly, notify the system programmer to
command issued by an operator will attempt to obtain verify that the data exists.
a console name equal to the NetView task's operator
ID. Any duplication of NetView operator IDs in your System programmer response
system or sysplex can create a console name conflict.
Also consider that extended consoles might be in use Ensure the definitions have the right name and are
by other applications. filed in the correct data set or file.
DWO339I command COMMAND FAILED. DWO341E 'command' I/O ERROR READING

TASK task HAS ALREADY 'file' LINE 'number'
OBTAINED CONSOLE console.
Explanation
Explanation The command cannot read the specified definitions.
The specified task has already obtained an extended The specified line in the definition cannot be read.
console. Message Variables
Message Variables command
command The name of the command.
The name of the command that failed. file
task The name of the definitions.
The task that issued the request for a console. number
console The number of the 80-byte statement of file that
The name of the console being used by the task. cannot be read.
The console is not obtained. Processing continues. The command is not processed. The previous
definitions remain in effect.
Operator response
Operator response
If you need to obtain a different console for issuing
MVS system commands or receiving system Notify the system programmer.
messages, release your current MVS extended console
by issuing the RELCONID command. Retry the System programmer response
command that failed. Check the file for data damage.

DWO342I 'command' 'file' DROPPED DWO344E 'command' 'file' LINE 'number'
NUMBER OF PREFIX COLUMNS
Explanation EXCEEDS MAXIMUM
The definitions named by the command are taken out

Explanation
of use.
The sum of the columns reserved for previous prefixes
Message Variables
plus the calculated size needed by the prefix on this
command line number exceeds the maximum allowed value.
The name of the command.
Message Variables
file
The name of the definitions. command
Note: If the value is *UNKNOWN*, the NetView
file
program cannot find any active definitions for the
The name of the definitions.
DEFAULTS or OVERRIDE command. The * symbols
allow you to distinguish the values from real and number
valid definition names. The line number of the statement in the file where
the error was found.
System action
System action
The existing default values for the definitions become
active according to the precedence rules for those The command is not processed. The previous
definitions that are currently in effect. definitions remain in effect.
DWO343E 'command' 'file' LINE 'number'

Operator response
'data' IS INVALID
Notify the system programmer to correct the
Explanation definitions.
The definition statement cannot be understood. The

command did not recognize the words used.
Reduce the number of PREFIX statements, make the
Message Variables
COLTAG values smaller, or use a sub-string of the
command prefix fields to make the prefix smaller. When you use
The name of the command. TIME or DATE in the PREFIX statement, set the time
file and date format prior to the first PREFIX statement if
The name of the definitions. you are not using the default time and date format.
This ensures that the correct length of the prefix fields
number is calculated.
The 80-byte statement in file that is not
understood. See the IBM Z NetView Customization Guide and
sample CNMSCNFT for additional usage information.
data
The word in the definition that is not recognized. DWO345E 'command' 'file' LINE 'number'
HAS EXTRA 'data'
System action
The command is not processed. The previous Explanation
definitions remain in effect. The definition had duplicate or unnecessary data.
Message Variables
Operator response
command
Notify the system programmer to correct the The name of the command.
definitions.
file
number
Check the spelling of the statement in error. The 80-byte statement in file that is not
understood.

data Operator response
The word in the definition that is duplicated or
unnecessary.
definition.
System action
Check the definitions and add the missing information,
or remove the definition.
Operator response
DWO347E 'command' 'file' LINE 'number'
Notify the system programmer to correct the HAS AN UNMATCHED 'deltype'
definition. DELIMITER

Check the definitions and remove duplicate or The definition did not have both beginning and ending
unnecessary data. delimiters.
DWO346E 'command' 'file' LINE 'number' IS Message Variables
MISSING THE 'keyword' VALUE
command
Explanation
file
You did not specify a value for the specified The name of the definitions.
information.
number
Message Variables The 80-byte statement in file that is not
command understood.
The name of the command. deltype
file The kind of delimiter that is missing.
The name of the definitions. Values are:
number COMMENT
The 80-byte statement in file that is not A comment delimiter is missing.
understood.
LITERAL
keyword A literal data delimiter is missing.
The information you tried to define, but for which
you did not provide a value. Note: If deltype is OE/OF, there is a problem with
the number of shift-ins and shift-outs in your
Typical keywords are: double-byte character set (DBCS) string.
DATE
The calendar date format in a SCRNFMT System action
definition.
The data is not processed.
TIME
The time-of-day format in a SCRNFMT
Operator response
statement.
COLTAG Notify the system programmer to correct the
A column-tag value in the SCRNFMT definition.
definitions.
BACKGROUND
The background color when the ON keyword Check the definitions and add the missing delimiter, or
was used in a SCRNFMT definition. remove the definition.
DWO348E 'command' 'file' LINE 'number' TOO
System action
MANY PREFIXES ARE DEFINED

You defined more than 16 prefixes, or had more than You entered a RESET command during the display of a
four prefixes combined into one field. multiline message, or pressed the attention key (the
attention key is available on SNA LU type 2 3270
Message Variables
sessions).
command
The name of the command. System action
file Message lines written to the screen prior to the RESET
The name of the definitions. command are displayed. Subsequent lines of the
number message are not. The NetView program then ends the
The 80-byte statement in file that is not RESET condition. If the message is a held or action
understood. message, it is saved and displayed in the held output
area. Command procedures running at the same time
System action messages are displayed are subject to the RESET
command, even though the message being displayed
The data is not processed. is not from that command procedure.

Notify the system programmer to correct the Continue normal operations.
definition.
Note: When you are running with AUTOWRAP 0, use
the HOLD command to stop the screen before using
the RESET command. The last message displayed can
Check the definitions and remove the extra prefix be reset if it is a multiline message, and if the last line
statements. has not been displayed. You can also reset a command
procedure when there is not a partial display of a
DWO349E 'command' 'file' HAS NO
multiline message by using the HOLD command to
DEFINITION STATEMENTS
stop the screen. You can then enter a RESET
command. Remember that the messages displayed on
Explanation your screen usually are displayed after the
You attempted to use a SCRNFMT definition or a corresponding command procedure. This is important
command definition that was empty or had only when deciding that you want to reset a command
comment statements. procedure.
Message Variables DWO353I INVALID TIMER ELEMENT

DETECTED. ID= 'reqname' FOR
command TASK 'opid:' LOC= 'location'
file Explanation
Either while queuing a new EVERY timer element
(LOC=1) or requeuing an EVERY command that has
System action
just been processed (LOC=2), an element with an
The data is not processed. interval of less than a second (which is not valid) was
detected. This message is sent as a held message to
Operator response the authorized receiver and the issuer of the EVERY
command.
definition. Message Variables
reqname
System programmer response The ID of the EVERY request.
Check the definitions and add statements or fix the opid
comment delimiters. The TVBOPID value of the task that issued the
EVERY command.
DWO350I A MULTIPLE LINE MESSAGE
DISPLAY WAS TRUNCATED

location DWO360E IMPROPER OPTION option
Indicator at which point in module DSITIMGR SPECIFIED. cmdname REJECTED.
detection occurred.
Explanation
System action
You specified an option that is not known to the stage
A dump of NetView is attempted. Message DWO050I command.
is logged with further information from the incorrect
Message Variables
element. The element is not requeued and the storage
is freed. option
The unknown option.
System programmer response cmdname
If the specifics of the EVERY timer can be determined The command that rejected the unknown option.
from the information in the DWO353I and the
associated DWO050I, the NetView EVERY command System action
can be used to reschedule the timer request. An Processing ends.
EVERY timer with an interval of less than a second
cannot be built by the EVERY command. If this
message is issued, either some code (other than the Operator response
NetView EVERY command processor) is not valid for Specify a correct option. If necessary, enter HELP
building or modifying the timer elements or a storage cmdname for information.
overlay has occurred. Thus, making a once valid EVERY
timer element incorrect. A dump titled 'NETVIEW DWO361E DUPLICATE OPTION option
INVALID TIMER DUMP SEE MSGDWO353I' was SPECIFIED. cmdname REJECTED.
attempted. In the dump, register 5 points to the
incorrect timer element. Contact IBM Software Explanation
Support as needed for assistance.
You specified an option twice.
Note: DWO353I is issued with attributes to force the
Message Variables
message to be displayed and held regardless of the
AUTOTBL or DEFAULT settings which usually affect it. option
The option that was repeated.
DWO354I NETVIEW PASSWORD CHECKING
FOR OPERATOR 'operatorid' cmdname
BYPASSED DUE TO NOCHECK The command that found the duplicate option.
OPTION SPECIFIED IN DSIOPF
System action
Explanation Processing ends.
The NOCHECK keyword was specified on the
OPERATOR statement in DSIOPF. Because of this, the Operator response
NetView program did not verify the password
Specify a correct option. If necessary, enter HELP
associated with the operatorid.
cmdname for information.
Message Variables
DWO362E PIPELINE TERMINATED. ERROR
operatorid IN STAGE stagenum IN PIPELINE
The ID of the operator who logged on. 'pipename':

The password was not verified. This is the first line of a multiline message. The
message text, which follows the text of the stage in
System programmer response error, can help you find the error. The specified stage
command reported an error. This message is usually
Correct DSIOPF if necessary. When the NOCHECK preceded by another message giving details of the
keyword is specified, you can install a logon user exit error.
to verify the password. For more information, see IBM
Z NetView Programming: Assembler or IBM Z NetView Note: Stage commands inserted with the INTERPRT
Programming: PL/I and C. stage command always have a stage number greater

than 10,000. If stagenum is greater than 10,000 the DWO365E KEYWORD 'keyword' IS
stagenume was inserted by INTERPRT. Enter HELP POSITIONAL AND NOT IN ITS
PIPE INTERPRT for more information from the online EXPECTED POSITION.
help facility.
stagenum The syntax of the command you entered requires the

The number of the stage command that reported specified keyword to be in a certain position in relation
the error to the command's other keywords. The keyword is out
of position, and must be specified either preceding or
pipename
following the command's other keywords.
The pipeline name
Message Variables
Processing ends. The keyword that is out of position.
Correct the stage command specification. Review Processing ends.

previous messages for details of the error.
Operator response
DWO363E PIPELINE TERMINATED. NULL
SPECIFICATION Move the keyword to its correct position and reenter
the command.
Explanation DWO366E NUMERIC VALUE number IS NOT
You specified a pipeline without stage commands. VALID. IT IS NOT WITHIN THE
RANGE REQUIRED BY THE
COMMAND OR KEYWORD ON
System action
WHICH IT IS SPECIFIED.
Processing ends.
Explanation
Operator response
The numeric value specified is not within the numeric
Specify the stage commands you need for your range required by the command or keyword on which
pipeline. it is specified.
DWO364E PIPELINE TERMINATED. NO Message Variables
STAGE stagename EXISTS. number
The numeric value that was specified.
Explanation
The stage command cannot be found. System action
Message Variables Processing ends.
stagename
The stage command from the pipeline Operator response
specification that cannot be found. Correct the numeric specification.
DWO367E UNSUPPORTED DELIMITER
System action
FOUND.
Processing ends.
Explanation
Operator response
A delimited string is required or allowed. The string
Enter HELP PIPE to determine the correct stage found does not have an acceptable delimiter
command specification. Then enter the command character, or an option has an improper value for the
again. delimiter.

Processing ends. Enter HELP PIPE stagename for the stage command
reporting the error to determine the meaning of the
Operator response return code.
Correct the delimited string or option value and enter DWO370E command REQUEST REJECTED.
the command again. Consult the help panels for the THE function FUNCTION ON
command entered, if necessary. Some characters are orignet.origlu IS NOT COMPATIBLE
not permitted as delimiters. WITH destnet.destlu.
DWO368E IMPROPER DELIMITER 'delimiter'

Explanation
FOLLOWS KEYWORD 'keyword'. A
BLANK DELIMITER IS REQUIRED. The specified command request was rejected because
the specified function in the originating NetView
Explanation program is not compatible with the target NetView
program.
The specified keyword is valid for the command you
entered; however, it is followed by a non-blank Message Variables
delimiter. The command syntax requires a blank command
delimiter. The name of the rejected command.
The function that was being performed when the
delimiter
command request was rejected.
The non-blank delimiter.
orignet.origlu
keyword
The fully qualified network name for the origin of
The valid keyword.
the command request.
System action destnet.destlu

The fully qualified network name for the target of
Processing ends. the command request.

Replace the non-blank delimiter with a blank and The command request is rejected and processing of
reenter the command. the request ends.
DWO369I stagename STAGE (stagenum) HAD DWO371E command REQUEST REJECTED.
RETURN CODE retcode. THE INPUT PARAMETERS TO THE
function FUNCTION ARE NOT
Explanation SUPPORTED.
You specified the message on error (MOE) option in a
stage command specification. The stage command Explanation
encountered an error. The command request cannot be satisfied because its
Message Variables input parameters are not supported or are not valid. If
the command is RMTCMD, RMTCMD was driven with
stagename an automation internal function request (AIFR) that
The name of the stage command that reported the was too large to include in the outbound LU 6.2
error. request. (LU 6.2 does not support outbound buffers
stagenum larger than 31000 bytes.) This might be the case when
The number of the stage command that reported a large AIFR is trapped in the automation table and the
the error. RMTCMD command is scheduled using that same
AIFR.
retcode
The return code for the error encountered. Message Variables
command
System action The name of the rejected command.

function The command list ends immediately and message
The function that was being performed when the DSI678I is inserted into the pipeline.
command request was rejected. • REXX error
System action – If SIGNAL ON FAILURE is in effect for the REXX

procedure, the FAILURE label takes control.
Your command request is rejected and processing of
– If SIGNAL ON FAILURE is not in effect for the
the request ends. REXX procedure, the procedure ends immediately
and a REXX symptom string is absorbed into the
Operator response pipeline.
Notify the system programmer. • HLL error
A PL/I or C procedure ends immediately and
System programmer response message CNM996I is inserted into the pipeline.
Reduce the size of the outbound request AIFR.
Operator response
DWO372E ENDING DELIMITER NOT FOUND
FOR DELIMITED STRING: 'string'. Notify the system programmer.

The specified delimited string keyword has a valid Do one of the following:
beginning delimiter; however it has no matching • Recode the procedure using the PIPE command
ending delimiter. A delimited string requires matching instead of message trapping.
beginning and ending delimiters.
• Consider adding an EXPOSE stage to your pipeline.
Message Variables See IBM Z NetView Programming: Pipes for additional
string information about the EXPOSE stage.
The delimited string that is missing an ending DWO374E stagename STAGE COMMAND
delimiter. CONTAINS TOO MANY DELIMITED
STRINGS, THE MAXIMUM OF
System action number IS EXCEEDED.
Processing ends.
Explanation
Operator response You specified too many delimited strings.
Add the ending delimiter to the delimited string, and Message Variables
reenter the command.
stagename
DWO373E ERROR: IMPROPER TRAPPING OF The name of the stage command where the error
MESSAGES WITHIN A PIPELINE. was detected.
command FAILED. number
The maximum number of delimited strings that are
Explanation supported.
A command procedure cannot use &WAIT or message
trapping if executing in a pipeline. System action
Message Variables Processing ends.
command
Operator response
The command procedure that included the
improper message trapping. Remove delimited strings until the allowable
maximum is reached, then reenter the command. If
System action necessary, consult the stage command's help panels
by entering the HELP PIPE stagename command.
The command procedure ends according to one of the
following conditions: DWO375E IMPROPER DELIMITER 'delimiter'
PRECEDES STRING 'string'.
• NetView command list language error

The syntax of the command you entered does not Processing ends.
permit the specified delimiter to precede the specified
string. Operator response
Message Variables Correct the PIPE command so that stagename is used
delimiter only as the first stage command in the pipeline. If
The delimiter that cannot precede the specified necessary, consult the stage command's help panels
string. by entering the HELP PIPE stagename command.
string DWO378E stringtype STRING IS TOO LONG,
The string that had an improper delimiter GREATER THAN maxlength
preceding it. The string can be one of the CHARACTERS IN LENGTH: 'string'.
keywords.
Explanation
System action
The specified string is too long for its type.
Processing ends.
Message Variables
Operator response stringtype

One of the following types of strings:
Correct the command specification and reenter the
command. • INTEGER
• POSITION.LENGTH
DWO376E ERROR: STAGE stagename
CANNOT BE FIRST IN A PIPELINE. • DELIMITED
• DDNAME.MEMBER
Explanation • TOKEN
The indicated stage command is not allowed as the • MORE-TOKENS
first stage command in a pipeline. You can specify it • LABEL
only as a subsequent stage command.
• HEX
Message Variables
maxlength
stagename The maximum length allowed for the specified
The name of the stage command. type of string.
string
System action The string that is longer than 255 characters; only
Processing ends. the first 255 characters are displayed.
Correct the PIPE command so that stagename is not The command that has this syntax error ends.
the first stage command. If necessary, consult the
stage command's help panels by entering the HELP Operator response
PIPE stagename command.
Correct the length of the string and enter the
DWO377E ERROR: STAGE stagename CAN command again. The types of strings and their
ONLY BE FIRST IN A PIPELINE. maximum lengths are:
INTEGER
Explanation 10 characters
The indicated stage command can only be specified as POSITION.LENGTH
the first stage command in a pipeline; it cannot be 21 characters
specified as a subsequent stage command. DELIMITED
Message Variables 255 characters (257 including delimiters)
stagename DDNAME.MEMBER
The name of the stage command. 17 characters

TOKEN delimiter
255 characters The delimiter that cannot follow the specified
MORE-TOKENS string.
255 characters string
LABEL The string that had an improper delimiter following
8 characters it. The string can be one of the keywords.
HEX
System action
254 characters
Processing ends.
Consult the command help panels if necessary.
DWO379E command FAILED. task IS NOT Operator response
AUTHORIZED FOR KEYWORD
'keyword'. Correct the command specification and enter the
command again. Consult the command's help panels,
if necessary.
Explanation
DWO381E POSITION.LENGTH STRING
The command request cannot be satisfied because
CONTAINS ZERO AS EITHER THE
task is not authorized to specify keyword with the
POSITION OR THE LENGTH:
specified command.
'string'.
Message Variables
command Explanation
The name of the command that failed. The position.length string contains zero as either the
task position or the length specification. Both the position
The task that tried to invoke the unauthorized and length specifications must be greater than zero.
command.
Message Variables
keyword
The keyword that the task is not authorized to string
specify on the command. The position.length string.
The command request is rejected and processing of Processing ends.

the request ends.
Operator response
Operator response Correct the position.length string and reenter the
Notify the system programmer. command.
DWO382E IMPROPER USE OF ESCAPE
System programmer response CHARACTER. command
REJECTED.
Determine if task task can issue command command
with keyword keyword. If so, update the operator's
security access appropriately. Explanation
DWO380E IMPROPER DELIMITER 'delimiter' You are not allowed to use the escape character as the
FOLLOWS STRING 'string' last character in a pipeline specification.
Message Variables
Explanation command
The syntax of the command you entered does not The command that was rejected.
permit the specified delimiter to follow the specified
string. System action
Message Variables The command request is rejected and processing of
the request ends.

The name of the command that did not complete
Consult the help panels for the correct syntax of the
its function.
PIPE command, correct your command, and resubmit
the command. target
The name of the resource or domain from which
DWO383E AN INTERPRT STAGE (stagenum1) the response was expected.
IS NESTED WITHIN AN INTERPRT
STAGE (stagenum2). NESTING OF
System action
INTERPRT STAGES IS NOT
ALLOWED. Processing ends.

The INTERPRT stage command is used to dynamically Try the command again. If it still fails, consult the help
insert stage commands into a NetView pipeline. When information for command.
the INTERPRT stage command identified by stage
number stagenum2 executed and began inserting System programmer response
stage commands into the pipeline, it found that one of
the stage commands being inserted was itself an Determine why the expected response was not
INTERPRT stage command, identified by stage received by checking the following:
number stagenum1. Nesting of INTERPRT stage • Whether target is active
commands is not allowed.
• Whether target is at the proper level
Note: Stage commands inserted with the INTERPRT • Whether there is an active session with target
stage command always have a stage number greater
than 10,000, so stagenum1 is greater than 10,000. For • Whether target was too busy with other requests to
more information, consult the INTERPRT stage respond in a reasonable amount of time
command's help panels by entering HELP PIPE DWO385E THE MAXIMUM NUMBER OF
INTERPRT. STAGES THAT MAY BE INSERTED
Message Variables BY INTERPRT STAGE (stagenum)
HAS BEEN EXCEEDED. THE
stagenum1 MAXIMUM IS maxnum.
The number of the nested INTERPRT stage
command.
Explanation
stagenum2
The number of the outer INTERPRT stage The INTERPRT stage command is used to dynamically
command. insert stage commands into a NetView pipeline. At
most maxnum stage commands can be inserted by a
single INTERPRT stage command. When the
System action
INTERPRT stage command identified by stage number
Processing ends. stagenum executed, it attempted to insert more than
maxnum stage commands into the pipeline. Consult
Operator response the INTERPRT stage command's help panels for more
information.
Correct the pipeline specification so that the
INTERPRT stage command's input data does not Message Variables
contain an INTERPRT stage command. Then reenter stagenum
the command. The stage number of the INTERPRT stage
DWO384I TIME-OUT OCCURRED. 'command' command.
FOR 'target' IS TERMINATED. maxnum
The maximum number of stage commands that
Explanation can be inserted by a single INTERPRT stage
command.
The command cannot complete because the expected
response was not received within the allotted time.
System action
Message Variables
Processing ends.

Correct the pipeline specification so that the The command procedure ends.
INTERPRT stage command's input data does not
contain more than maxnum stage commands. Then Operator response
reenter the command.
DWO386I THE FOLLOWING MESSAGES
WERE RECEIVED WHILE System programmer response
PROCESSING THE PRECEDING
COMMAND: Use the command and messages displayed to help you
determine why the command timed out. If you are
Explanation unable to determine why the command timed out, or if
you determine that the cause of the time-out is
This message is preceded by a message line displaying something that you cannot correct, contact IBM
a command that was executed from within a command Software Support.
procedure. When this command executed, it failed and
returned a nonzero return code, causing the command DWO388I NO MESSAGES WERE RECEIVED
procedure to end. This nonzero return code is present PRIOR TO THE PRECEDING
in message DWO369I, which immediately follows the COMMAND TIMING OUT.
command and immediately precedes this DWO386I
message. Normally whenever a command fails, one or Explanation
more error messages accompany the nonzero return
This message might be preceded by a message line
code. If such error messages are present, they are
displaying a command that was run from within a
displayed after this DWO386I message.
command procedure or a command that was relayed
to the NetView application. The command might or
System action might not be running as expected, but the allowed
The command procedure ends. response time has expired.
Notify the system programmer. The command results are not shown.
Use the command, return code, and messages If you received this message from WINDOW, a labeled
displayed to help you determine why the command command, the web browser, or a command entered
failed. If you cannot determine why the command remotely to NetView, and it is safe to reissue the
failed, or if you determine that the cause of the failure command, and then enter the command again
is something that you cannot correct, contact IBM preceded by a timeout value (in seconds). For z/OS
Software Support. commands, consult the system log for possible
responses. Otherwise, notify the system programmer.
DWO387I THE FOLLOWING MESSAGES
WERE RECEIVED PRIOR TO THE System programmer response
PRECEDING COMMAND TIMING
OUT: Determine which command is without response. Use
that information and the fact that it received no
Explanation messages to help you determine why the timeout
occurred. A larger timeout value might be needed in
This message is preceded by a message line displaying DSICCDEF or in a command procedure issuing the
a command that was executed from within a command command. If you are unable to determine why the
procedure. When this command executed, certain command timed out, or if the cause of the timeout
messages that normally result from issuing this cannot be corrected, then contact IBM Software
command were expected to be received. These Support.
expected messages were not received within a
specified period of time. A time-out occurred and the DWO390I UNABLE TO SEND DATA TO TASK
command procedure ended. Other unexpected task, STORAGE FAILURE
messages were received, and they are displayed after
this DWO387I message.

An attempt to MQS a buffer from a foreign domain to The command is not processed.
the specified task failed because of a shortage of
storage. Operator response
task
The name of the task to which the data was being System programmer response
sent.
Update the NetView startup procedure by adding a DD
statement containing the information related to the
System action VSAM database you want to clear. Restart the NetView
The buffer storage is freed. system.
DWO393I RESETDB COMMAND FAILED,
Operator response 'ddname' DLBL STATEMENT
MISSING
Explanation
The RESETDB command failed to clear the specified
Determine why there is a shortage of storage.
VSAM database because the DLBL statement is
DWO391I UNABLE TO SEND DATA TO TASK missing.
task, INVALID BUFFER LENGTH
Message Variables
Explanation ddname
The data definition name of the VSAM file.
An attempt to MQS a buffer from a foreign domain to
the specified task failed because of an incorrect buffer
System action
length.
Message Variables
The name of the task to which the data was being
sent. Notify the system programmer.
The buffer storage is freed. Update the NetView startup procedure by adding a
DLBL statement containing the information related to
the VSAM database you want to clear. Restart the
Operator response
NetView system.
'ddname' DATA BASE IS OPEN
Contact IBM Software Support. Explanation
DWO392I RESETDB COMMAND FAILED, The RESETDB command failed to clear the specified
'ddname' DD STATEMENT VSAM database because the VSAM database is open.
MISSING
Message Variables
Explanation ddname
The RESETDB command failed to clear the specified
VSAM database because the DD statement is missing.
System action
Message Variables
ddname

Notify the system programmer. A command list that issued the WTOR command is still
waiting for a reply from the operator.
To clear the VSAM database, you need to stop the task operatorid
using the database before issuing the RESETDB The operator ID of the task that issued the WTOR
command. Restart the task after the command is command in a command list.
completed.
DWO395I RESETDB COMMAND FAILED, System action
'ddname' IS NOT A VSAM DATA The command list stops until the corresponding reply
BASE is received. The operator's terminal is still free to
perform other functions.
Explanation
The RESETDB command failed to clear the specified Operator response
VSAM database because the file referred to by the Use the RESET command to cancel the command list
ddname is not a VSAM database. that issued the WTOR command if the WTOR does not
Message Variables expect or need a reply.
ddname Note: More than one command list might be waiting
The data definition name of the VSAM file. for replies to their respective WTOR commands. The
RESET command cancels these command lists in last
System action in, first out (LIFO) order.
The command is not processed. DWO398I REASON FOR FAILURE:

OPERATION TIMED OUT
'ddname' WAS NOT DEFINED Explanation
WITH REUSE
The request has failed because the operation timed
Explanation out.
The RESETDB command failed to clear the specified System action

VSAM database because the file referred to by
ddname was defined without the REUSE option. Message DWO191I or DWO192I is issued before this
message to indicate whether the request type is
Message Variables RESTORE or DELETE.
ddname
The data definition name of the VSAM file. Operator response
System action
The command is not processed. System programmer response
Correct the cause of the time-out before attempting
Operator response any other action.
DWO402I VPDLOG REQUEST HAS BEEN
ACCEPTED FOR PROCESSING
Redefine the VSAM database with the REUSE option Explanation
specified.
A VPDLOG request is syntactically correct and queued
DWO397I REPLY OUTSTANDING FOR WTOR for processing by DSIELTSK.
COMMAND ISSUED BY operatorid
System action
The request is queued to DSIELTSK for processing.

DWO403I TASK task IS INACTIVE. REQUEST Explanation
FAILED. The parameter following SNAP on a VPDCMD
command is not valid. ON or OFF are the valid
Explanation parameters following SNAP.
A correct VPD request was issued, but VPDTASK is Message Variables
inactive.
parameter
Message Variables The parameter following SNAP.
task
The task name of VPDTASK. System action
System action
The request is not processed. Operator response
Correct the request and issue it again.
Operator response
DWO407I SYNTAX ERROR - TOO MANY
Start VPDTASK and issue the request again. PARAMETERS FOR VPDCMD [OWN
DWO404I SYNTAX ERROR - INSUFFICIENT | ALL | DCE | SNAP | OPTIONS]
PARAMETERS FOR VPDCMD [OWN REQUEST
| ALL | DCE | SNAP] REQUEST
Explanation
Explanation The indicated type of VPD request has too many
The indicated type of VPD request does not contain all parameters specified.
the required parameters.
System action
System action The request is not processed.
Operator response
Operator response Correct the request and issue it again.
Correct the request and issue it again. DWO408I SYNTAX ERROR - PARAMETER
DWO405I SYNTAX ERROR - INSUFFICIENT parmnum CANNOT BE ZERO
PARAMETERS
Explanation
Explanation A VPD request contains a zero (0) as a link segment
A VPD request is missing a required parameter. For level on a VPDCMD command, or as a starting position
example, if you entered VPDCMD or VPDLOG 222 you or the record type number on a VPDLOG command.
receive this message. For example, in the command:
VPDLOG 0 1 aaa 4 cccc

System action
The request is not processed. the record type number is 0. The message shows
parmnum as 1.
Correct the request and issue it again. parmnum
DWO406I SYNTAX ERROR - 'parameter' IS The number of the parameter that has a value of 0.
AN UNSUPPORTED OPTION FOR
VPDCMD SNAP System action

Operator response • A PIPE label
Correct the request and issue it again. Message Variables
DWO409I MAXIMUM LSL EXCEEDED ( MAX = value
maxlsl ) The value of the parameter in error

The VPDCMD DCE request specifies a link segment The request is not processed.
level greater than the maximum level supported.
maxlsl Correct the request and issue it again. Valid characters

The maximum acceptable link segment level. are any alphanumerics, $, #, and @.
DWO412I SYNTAX ERROR - IN PARAMETER
System action parmnum 'value' IS NOT NUMERIC
Explanation
Operator response Either the link segment level you specified in your
VPDCMD command is not numeric, or a position you
specified in your VPDLOG command is not numeric.
DWO410I SYNTAX ERROR - IN PARAMETER Message Variables
parmnum 'value' IS TOO LONG
parmnum
Explanation The number of the parameter in error.
value
The specified parameter on a VPD request is too long.
The value of the parameter in error.
For example, in the command:
System action
VPDLOG 222 99999999 ABC
the 99999999 parameter is too long. The message
shows parmnum as 2 and value as 99999999.
Operator response
Message Variables
parmnum
DWO413I SYNTAX ERROR - VPDCMD
The number of the parameter in error.
'keyword' IS AN UNSUPPORTED
value REQUEST
The value of the parameter in error.
Explanation
System action
A VPDCMD command contains an incorrect keyword.
The request is not processed. See the NetView online help for the valid keywords.
Message Variables
Operator response
keyword
The keyword that is not valid.
DWO411I SYNTAX ERROR - value CONTAINS
INVALID CHARACTERS System action
Explanation
A request contains characters that are not valid. The Operator response
request was one of the following:
• A vital product data (VPD) request
• An ATTACH command

DWO414I SYNTAX ERROR - PARAMETERS default value used for the record formats that are
ARE NOT PAIRED provided by IBM.
Message Variables
Explanation
record
A VPDLOG request contains parameters that are not The specified record number that is not valid.
paired correctly. VPDLOG requests must contain a
record identifier followed by pairs of parameters. The System action
first parameter of a pair indicates the offset position in
the record where the second parameter of the pair is The request is not processed.
to be written.
Operator response
System action Contact the system programmer to get a valid record
The request is not processed. number to use. Valid record numbers are in the range
of 128-255.
Operator response DWO417I SYNTAX ERROR - THE STRING AT
Correct the request and issue it again. RECORD OFFSET 'offset' IN
PARAMETER parmnum WOULD
DWO415I CURRENT RECORD SIZE 'size' OVERLAY PREVIOUS STRING
EXCEEDS THE MAXIMUM ( max )
ALLOWED Explanation
Explanation The vital product data record cannot be written

correctly. The specified parameter overwrites the
The length of a record or data structure created by previously written field.
your request exceeds its maximum allowed length.
For example, in the command:
Message Variables
VPDLOG 222 1 aaaa 3 cccc 10 fff
size
The total length of the record or data structure the fourth parameter specifies a starting position of
created by your request. three, but the previously written field ends in position
max four. The message shows parmnum as 4 and offset as
The maximum allowable length. 3.
Message Variables
System action
offset
The request is not processed. The starting position indicated by the parameter in
error.
Operator response parmnum
Correct the request and issue it again. If the problem The number of the parameter in error.
persists, contact the system programmer.
System action
System programmer response The request is not processed.
If a VPDLOG request is causing this condition, change
your command list so that it splits the record that is Operator response
too long into multiple records. Otherwise, you must
reduce the input data.
DWO418I SYNTAX ERROR - THE STRING AT
DWO416I CURRENT RECORD ID 'record' IS
RECORD OFFSET 'offset' IN
INVALID
PARAMETER parmnum WOULD
BEGIN BEYOND THE LAST STRING
Explanation
The specified record ID, in the VPDLOG request, is
neither in the user-defined range of 128-255 nor a

You did not enter the parameter pairs of a VPDLOG Your VPDINIT definition statement is coded with too
request in the proper sequence. The parameter many parameters.
indicates a starting position greater than the starting
position for the last pair of parameters. System action
For example, in the command: VPDTASK is not initialized.
VPDLOG 222 1 aaaa 10 cccc 7 fff
Operator response
the fourth parameter specifies a starting position of
ten, but the last pair of parameters uses a starting
position of seven and an ending position of nine. The
message shows parmnum as 4 and offset as 10. System programmer response
Message Variables Correct your VPDINIT definition statement in

DSIVPARM of DSIPARM, then start VPDTASK. See the
offset IBM Z NetView Administration Reference for the correct
The starting position indicated by the parameter in syntax of the VPDINIT statement.
error.
DWO424I SYNTAX ERROR - A STRING IS
parmnum
LONGER THAN 255 CHARACTERS
The number of the parameter in error.
Explanation
System action
A VPDLOG command contains a string longer than 255
characters, which is the maximum length of a string.
Operator response
System action
DWO421I LOG REQUEST CANNOT BE
SATISFIED Operator response
Explanation
DWO430I FOCALPT CHANGE FAILED - TIME-
A VPDLOG was unable to queue a record to the
OUT CONDITION OCCURRED
external logging task.
Explanation
System action
A FOCALPT CHANGE request sent to the distributed
node failed because a response was not received
within the allotted amount of time. A time-out
Operator response condition occurred.
Use the LIST DSIELTSK command to determine if the
external logging task is active. If not, start the task. If System action
the task is active, contact the system programmer.

Operator response
Check the error return code for DSIWLS macro with
Verify that the distributed node where the request was
EXTLOG option in IBM Z NetView Programming:
sent has a NetView program release of Version 2
Assembler.
Release 2 or later. If it does not, use the CHANGEFP
DWO422I VPDINIT STATEMENT CONTAINS command for ALERT and STATUS type because the
TOO MANY PARAMETERS FOCALPT CHANGE command is not supported in
earlier releases. If this is not the problem, notify the
system programmer.

System programmer response retcode
The return code in hexadecimal. The return code
Increase the time-out value for FOCALPT CHANGE
has one of the following values:
(default set to 120 seconds) in DSICTMOD.
0C
DWO431I FOCALPT CHANGE FAILED - THE The LUC task is not active.
task IS INACTIVE
Others
A NetView internal program error occurred.
Explanation
The FOCALPT CHANGE request failed because the task System action
at the issuing node was not active.
Message Variables
The task that is not active. Notify the system programmer.

The request is ignored. If the return code is 0C, verify that the LUC task is
active. For other return codes, contact IBM Software
Operator response Support.
Notify the system project. DWO434I FOCALPT CHANGE FAILED -
REASON CODE = X'retcode', SNA
System programmer response SENSE CODE = X'sensecode'
Start the task and issue the command again.
Explanation
DWO432I FOCALPT CHANGE FAILED - OUT
OF STORAGE A FOCALPT CHANGE request sent to the distributed
node failed.
A FOCALPT CHANGE request sent to the distributed retcode
node failed because of a storage shortage. The return code in hexadecimal. The return code
has one of the following values:
System action 04
A session is not available.
06
Operator response Resources or storage is not available.
34
An allocation error occurred.
36
DSICRTR at the distributed node is not
If the message persists, check the NetView storage available and a retry is allowed.
and adjust if necessary. See the IBM Z NetView Tuning F0
Guide. A system error occurred indicating a problem
DWO433I FOCALPT CHANGE FAILED - outside the issuing NetView program.
REASON CODE = X'retcode' others
A NetView internal program error occurred.
Explanation sensecode
A FOCALPT CHANGE request sent to the distributed The SNA sense code.
node failed.
System action
Message Variables

Operator response CANNOT BE ITS OWN FOCAL
POINT
If sensecode is '084B6031, 084C0000', or
'10086021', try to activate the DSICRTR task at the
distributed node with which you are attempting to Explanation
communicate. The DEFFOCPT statement in DSICRTTD or DSI6INIT
If sensecode is '087D0001', ensure that the cross- contains a primary or backup focal point name that is
domain session to the distributed node is set up and not valid. Forwarding messages, alerts, status data,
the LUC task at the distributed node is active. OPS_MGMT data, and user data from the local domain
to the local domain is not allowed.
If you receive other sense codes, notify the system
programmer. When the host is defined to be a status focal point
itself, status data will be not be forwarded, regardless
of whether there is a valid status focal point definition.
Message Variables
If retcode is 04, retry at a later time or consider
changing the MAXSESS operand on the CNMAUTH type
definition statement to allow more sessions. The type of DEFFOCPT statement.
If retcode is 06, increase the available resources or
storage. System action
If retcode is 34 or 36, ensure the DSICRTR task is The DEFFOCPT statement is ignored.
active at the distributed node. If the problem persists,
see the Systems Network Architecture library for Operator response
information on the sense code.
If retcode is F0, ensure VTAM and LUC are active at
both domains. Also, confirm that communication can System programmer response
be established between the two domains.
Correct the statement that is not valid.
For other return codes, see Systems Network
Architecture Reference Summary. If necessary, contact DWO450I NO REGISTERED APPLICATIONS
IBM Software Support. FOUND
DWO435I FOCAL POINT AUTHORIZATION IS

Explanation
REVOKED BY 'ephost' FOR type
DATA. NEW FOCAL POINT IS No applications were found for the REGISTER QUERY
'newfp' request. If you use QUERY (with no options) or
QUERY=ALL, this message indicates that there were
Explanation no applications found for any of the application types.
This host is no longer a focal point for the data you

System action
specified.
Message Variables
DWO452I TASK 'task' IS TERMINATING.
ephost
The distributed entry point node. 'nnnnnn' SYNCHRONOUS
REQUESTS CANCELLED.
type
The type of data for which the focal point is being
Explanation
changed (such as alert, status, or ops_mgmt).
newfp A task is ending that has a number of outstanding
The new focal point host. synchronous send requests that have not yet received
replies.
System action This message is written only in the network log.
The specified type of data is not forwarded to this Message Variables
host.
task
DWO444I ERROR IN type DEFFOCPT The name of the task that is ending.
STATEMENT - LOCAL DOMAIN

nnnnnn were sent by the served application and have not yet
The total number of outstanding synchronous been answered. These outgoing outstanding requests
requests that originated from the ending task and are canceled.
are being canceled.
This message is written only in the network log.
Synchronous requests issued from the ending task are appl

canceled. MDS error messages are sent to the The name of the operations management served
applications to whom the original requests were sent application that deregistered. It is either an 8-byte
informing them that the requests are canceled and EBCDIC (0-9 or capital A-Z only) name or a 4-byte
replies are no longer expected. architecturally defined or reserved hexadecimal
value preceded by the character X to indicate that
DWO453I OPERATIONS MANAGEMENT this is a 4-byte hexadecimal name.
SERVED APPLICATION 'appl'
nnnnnn
DEREGISTERED. 'nnnnnn'
The total number of outstanding outgoing requests
INCOMING REQUESTS
that are canceled.
CANCELLED.
System action
Explanation
The outstanding outgoing requests are canceled
An operations management served application has
because of deregistration of the operations
deregistered. A number of requests expecting a reply
management served application. MDS error messages
were received by the served application to which it has
are sent to the applications to whom the original
not yet replied. These incoming outstanding requests
requests were sent, informing them that the requests
are canceled since they are not satisfied.
are canceled and replies are no longer expected.
DWO455I OPERATIONS MANAGEMENT
Message Variables RECEIVED ERROR MESSAGE FOR
appl UNKNOWN TRANSACTION.
The name of the operations management served ORIGIN NODE = 'netid.luname',
application that deregistered. It is either an 8-byte ORIGIN APPLICATION =
EBCDIC (0-9 or capital A-Z only) name, or a 4-byte 'oapplname', DESTINATION
architecturally defined or reserved hexadecimal APPLICATION = 'dapplname',
value preceded by the character X to indicate that SENSE CODE = X'code'.
this is a 4-byte hexadecimal name.
Explanation
nnnnnn
The total number of outstanding incoming Operations management received an MDS error
requests that are canceled. message or a Routing Report for a unit of work with a
unit of work correlator that does not match any of
System action those in the operations management transaction lists.
The MDS error message or Routing Report is
The outstanding incoming requests for the application discarded.
are canceled because of deregistration of the
operations management served application. MDS error Message DWO461 might be sent after this message.
messages are sent to the applications that sent the This message is written only in the network log.
requests, informing them that they will not receive the
requested replies. Message Variables
DWO454I OPERATIONS MANAGEMENT netid.luname

SERVED APPLICATION 'appl' The network ID and LU name of the originator of
DEREGISTERED. 'nnnnnn' the MDS error message or the Routing Report.
OUTGOING REQUESTS oapplname
CANCELLED. The application name of the origin of the MDS error
message or the Routing Report. It is either an 8-
Explanation byte EBCDIC (0-9 or capital A-Z only) name, or a 4-
byte architecturally defined or reserved
An operations management served application has
deregistered. A number of requests expecting a reply

hexadecimal value preceded by the character X to Operator response
indicate that this is a 4-byte hexadecimal name.
Verify that the application name is spelled correctly.
dapplname
The application name of the destination of the MDS DWO458I 'luappl' IS ALREADY A
error message or the Routing Report. It is either an REGISTERED APPLICATION
8-byte EBCDIC (0-9 or capital A-Z only) name, or a
4-byte architecturally defined or reserved Explanation
hexadecimal value preceded by the character X to
The REGISTER command was issued, with the
indicate that this is a 4-byte hexadecimal name.
REPLACE=NO option, to register an application that is
code already registered.
A 4-byte architecturally defined sense code that
describes the error. See the Systems Network Message Variables
Architecture library for a description of the sense luappl
codes. The LU 6.2 application that is already a registered
application.
System action
The MDS-MU is discarded because it does not match System action
any existing unit of work. Processing continues.
DWO456I THE VALUE FOR KEYWORD
'keyword' CONFLICTS WITH Operator response
OTHER OPTIONS Do not use the REPLACE=NO option if this registration
is to replace the registration already made for this
Explanation application.
The keyword is not consistent with the value of the DWO459I INVALID MDS_MU, NODE =
other keywords specified. 'netidluname', SENSE =
Message Variables X'sensecode', PARTIAL DATA =
X'data'
keyword
The keyword with the conflicting value. Explanation
System action An MDS-MU with format errors was received by the

NetView program. The sender, sense code, and up to
Processing continues. 100 bytes of data are included in the message. An
alert was created and sent to the operator. The
Operator response purpose of this message is to assist in further problem
determination.
Verify the keyword values that are in conflict and enter
the command again with the correct keyword values. This message is written only in the network log.
See the NetView online help for more information on Message Variables
keyword values.
netidluname
DWO457I 'luappl' IS NOT A REGISTERED The netid and the LU name of the node where the
APPLICATION MDS-MU that is not valid originated.
sensecode
Explanation The sense code.
The REGISTER command was issued to deregister an data
application, but luappl is not registered. Up to 100 bytes of the MDS-MU in error.
Message Variables
System action
luappl
The LU 6.2 application that was to be deregistered. The MDS-MU in error is not processed. Processing
continues.
System action

Operator response application name are available in the MDS error
message or the Routing Report.
Determine the source of the MDS-MU in error using the netid.luname
supplied information in the message and the NetView- The reported-on network ID and LU name in the
generated alert. If the origin is an application that is SNA Condition Report (SNACR) of the MDS error
supplied by IBM, contact IBM Software Support. message or the Routing Report. If netid.luname is
DWO460I REGISTRATION FOR 'applname' an *, NetView cannot determine the network ID of
FAILED. RETURN CODE FROM the LU.
REGISTRATION = 'retcode'. applid
The reported-on application name in the SNACR of
Explanation the MDS error message or the Routing Report. It is
either an 8-byte EBCDIC (0-9 or capital A-Z only)
A NetView application failed to register itself as an MS name, or a 4-byte architecturally defined or
application. This error can occur if a particular reserved hexadecimal value preceded by the
command definition statement is in error or is missing, character X to indicate that this is a 4-byte
or if the NVAUTO application is already registered. hexadecimal name.
Message Variables DWO462I 'keyword' VALUE OF 'value1'
applname CANNOT EXCEED MAXREPLY
The application that failed to register. VALUE OF 'value2'. CURRENT
VALUES ARE: MAXREPLY =
retcode
'maxreply', RCVREPLY = 'rcvreply',
The return code from registration.
NOREPLY = 'noreply'.
System action
Explanation
Depending on the NetView application, the task might
The value of rcvreply or noreply exceeded the value of
not continue to initialize. If the task continues to
maxreply.
initialize, the application indicated is not registered as
an MS application. Message Variables
keyword
System programmer response The keyword RCVREPLY or NOREPLY.
Determine the reason for the registration failure and value1
take appropriate action. The entered value for RCVREPLY or NOREPLY.
One of the following must be defined in CNMCMD: value2
The value for MAXREPLY.
• DSIOURCP for OPSMGMT applications
maxreply
• BNJNETOP for ALERTNET applications
The current value of MAXREPLY.
• DSIFPRCV for MS CAPS applications
rcvreply
• DSINVGRP for NVAUTO applications, or you can The current value of RCVREPLY.
verify that a user-defined NVAUTO is registered.
noreply
The return codes from registration are documented in The current value of NOREPLY.
IBM Z NetView Programming: PL/I and C.
System action
DWO461I REPORTED-ON NODE =
'netid.luname', REPORTED-ON The new CNMSENDMU time-out values (MAXREPLY,
APPLICATION = 'applid'. RCVREPLY, and NOREPLY), as entered in the
DEFAULTS command, are not saved.
Explanation
Operator response
This message follows message DWO455. It is sent
when the reported-on node name and reported-on Enter the command again with the correct values.

DWO463I 'keyword' VALUE OF 'value1' System action
CANNOT EXCEED ALLOWABLE The statement statement is ignored and the default
LIMIT OF 'value2'. CURRENT value for EPONLY is used.
VALUES ARE: MAXREPLY =
'maxreply', RCVREPLY = 'rcvreply',
NOREPLY = 'noreply'. Operator response
Explanation
The value entered for MAXREPLY exceeded the System programmer response
allowable range. If the defaulted value is acceptable, you do not need
Message Variables to do anything. If it is not acceptable, correct the value
and restart the DST.
keyword
The keyword MAXREPLY as it is entered with the DWO465I 'task' INITIALIZATION ERROR.
DEFAULTS command. REASON CODE = 'reason'.
value1
The entered value for MAXREPLY. Explanation
value2 The task you specified in task encountered an

The maximum valid MAXREPLY value; which is initialization error. The error is identified by the reason
31622400. code field reason.
maxreply Message Variables
task
rcvreply The name of the task being initialized.
The current value of RCVREPLY.
reason
noreply The hexadecimal reason code. The valid reason
The current value of NOREPLY. codes are:
0001
System action An attempt to define an LU 6.2 transaction
The new default value for MAXREPLY is not saved. If program to the command facility failed.
RCVREPLY, NOREPLY, or both have values entered, Contact IBM Software Support.
those values are not saved either. 0002
The PUSH of the logoff routine failed. This can
Operator response be caused by a missing CMDDEF statement.
Review required command definition
Enter the command again with the correct values. statements. If all statements are defined,
DWO464I INVALID VALUE 'value' SPECIFIED contact IBM Software Support.
FOR 'keyword' - 'statement' 0003
STATEMENT IGNORED. An attempt to issue a timer services request
during initialization failed. Contact IBM
Explanation Software Support.
The value of EPONLY is not valid. Valid values for 0004
EPONLY are YES or NO. Operations management initialization failed.
Message Variables
0005
value Focal point initialization failed. Contact IBM
The value for EPONLY that is not valid. Software Support.
keyword 0006
The incorrect keyword, EPONLY. Bad syntax on the PARTNER statement.
statement Correct the error.
The statement (DEFENTPT) in which the incorrect 0007
value is specified. VTAM is not active. Start VTAM before starting
the task.

Determine the type of error identified by the reason Processing continues.
code and take corrective action. See the reason code
DWO469I appltype applname cmdproc task
descriptions for more information. If necessary,
fpcat focalpt logmode notify priority
DWO466I ALERT LENGTH length RECEIVED Explanation
BY TASK task EXCEEDS THE
ALLOWABLE MAXIMUM This message displays the actual data for the QUERY
maxlength. IT IS NOT PROCESSED. request when you issue a REGISTER command with
the QUERY option.
An alert was received that was longer than the appltype
allowable maximum. The alert is not processed. This The type of application that is registered. It can be
message is followed by message DWO467, which one of the following:
gives the first 100 bytes of the alert. MS
Message Variables A management services application.
length OM
The length of the alert received (in decimal). An operations management (OPS_MGMT)
application.
task
The task that received the alert. HP
A high performance application.
maxlength
The maximum length for an alert. applname
The name of the application.
System action cmdproc
The name of the command processor run for
The alert is not processed (the hardware monitor does unsolicited data.
not receive the alert).
task
The name of the task under which the application
is registered.
Find the origin of the alert and change the alert fpcat
content, if possible. The focal point category of interest. You must
DWO467I THE FIRST 100 BYTES OF THE specify this during registration.
ALERT IS X'alert'. focalpt
Indicates if the application is a focal point.
Explanation logmode
This message shows the first 100 bytes of an alert. The log mode used by the application. This field is
This message usually follows message DWO466. only relevant for high performance (HIPERF)
applications.
Message Variables
notify
alert The type of session outage notification requested.
The first 100 bytes of the alert in hexadecimal It can be one of the following:
value. NONE
DWO468I TYPE APPL COMMAND TASK The application does not require session
FPCAT FOCALPT LOGMODE outage notification.
NOTIFY PRI ERROR
The application requests only error session
Explanation outage notification.
This is the title line that is used to arrange the output ALL
into columns when you issue the REGISTER command The application requests all session outage
with the QUERY option. notification.

priority command
The MQS priority for incoming unsolicited requests The name of the NetView command that
and error messages. It can be one of the following: established the given session with a remote
HIGH device.
The incoming unsolicited request or error number
message is sent to the destination application The number of records purged.
with a MQS of high priority.
NORMAL System action
The incoming unsolicited request or error This message is written only to the network log.
message is sent to the destination application
with a MQS of normal priority. DWO517I command PURGE REQUEST IN
PROGRESS
LOW
The incoming unsolicited request or error
message is sent to the destination application Explanation
with a MQS of low priority. The requested purge of panel templates from the
TEST database is being processed by the system.
The incoming unsolicited request or error
Message Variables
message is sent to the destination application
with a MQS of the current NetView command command
priority. The name of the NetView command that
established the given session with a remote
System action device.
Operator response
DWO515I command PURGE ALREADY Wait until the purge processing completes. Or, enter
RUNNING NetView commands or other command subcommands
while waiting.
Explanation
DWO518I command SESSION ALREADY IN
A requested purge of panel templates from the PROGRESS
command database is already in progress.
command You already have a CSCF session in progress, or
The name of the NetView command that another NetView operator has a CSCF session with the
established the given session with a remote requested PU.
device.
Message Variables
System action command

The name of the NetView command that
The request is ignored and processing continues. established the given session with a remote
device.
Operator response
Wait for the first PURGE to complete, and then issue Operator response
the request again. Wait until the first session is complete before reissuing
DWO516I NUMBER OF command RECORDS the command request to this PU.
PURGED : number DWO519I command SESSION TERMINATED
DUE TO NO ACTIVITY FOR timeout
Explanation MINUTES
This message indicates the number of panel templates
that were purged from the command database in Explanation
response to the operator's request. The NetView program ended the specified session.
Message Variables There were no requests over this session for the
number of minutes indicated by timeout. Other

operators now have the opportunity to establish the NetView online help for more information on messages
same type of session with the remote device. issued by the SWITCH command.
Message Variables
Operator response
command
The name of the NetView command that If retcode or errcode are not zero (0), notify the system
established the given session with a remote programmer.
device.
timeout System programmer response
The number of minutes that the NetView program If the retcode and errcode are zero (0), the CLOSE
allows you to remain idle before ending the completed successfully. Otherwise, refer to the
session. appropriate VSAM manual for CLOSE return codes and
ACB error fields.
Operator response
DWO521I TASK task IS NOT AUTHORIZED
Enter the command again if you wish to resume your BY THE SECURITY SOFTWARE TO
command session. OBTAIN EXTENDED CONSOLE
console
Explanation
If you want to change the time-out value, make the
change in DSICTMOD (the NetView constants module), The specified task attempted to obtain an EMCS
where this time value is identified as the CSCF console using the GETCONID command or the MVS
APPLICATION IDLE TIMEOUT. DSICTMOD is shipped command, but was prevented from doing so by the
as sample CNMS0055. installed security software.
DWO520I task: VSAM DATASET 'CLOSE' Message Variables
COMPLETED, DDNAME='ddname', task
RETURN CODE= X'retcode', ACB The name of the task.
ERROR FIELD= X'errcode'
console
The name of the EMCS console.
Explanation
A CLOSE completed for the VSAM data set indicated by System action
ddname. This message is issued when a SWITCH,
SWLD, or SWPD command is issued which causes an The console is not obtained. If the MVS command was
open data set to be closed. entered, the system command is not issued.
Message Variables
Operator response
task
See your security administrator to obtain authorization
The name of the task.
for the desired EMCS console resource. Notify the
ddname system programmer.
The name of the VSAM data set.
retcode System programmer response
The return code used for problem analysis.
Determine which command was issued when the
errcode operator tried to obtain an EMCS console. If the MVS
The error code used for problem analysis. command was used, the task attempted to obtain the
EMCS console with the console name equal to the
System action operator's ID. If the GETCONID command was used,
the console name might have been explicitly specified,
This message is routed to the task that issued the
or it might have defaulted to the operator's ID.
SWITCH command causing an open data set to be
closed. CLOSE processing has completed and Ensure that the method the operator used to obtain an
additional processing (such as IDCAMS) can now be EMCS console is consistent with the security
issued for this data set. When the SWITCH command administrator's definitions for the EMCS consoles.
is issued within a NetView pipeline, message
DWO522E TASK 'task' DETECTED FORMAT
DWO520I will correlate to the pipeline. See the
ERRORS IN DSIAIFRO

VECTORIZED DATA DURING DWO524I DISTRIBUTED AUTOTASK
AUTOMATION PROCESSING autooper ON autonet.autodomain
WAS TERMINATED BY termoper
Explanation ON termnet.termdomain
The message being processed by automation has one

Explanation
or more format errors in the DSIAIFRO extensions of
the message. An operator issued an ENDTASK FORCE command to
end a distributed autotask that the operator did not
Message Variables
start. This message informs the operator who started
task the distributed autotask that the DSIUDST task has
The name of the task reporting the error. ended the autotask. If the DSIUDST task ends, it
forces off all the active distributed autotasks defined
System action to the same NetView program. This message is
presented to each operator who started a distributed
The message in error is not automated. The message autotask that has been forced off by autotask
is discarded. The message in error and the associated DSIUDST.
vectorized data from the DSIAIFRO extensions are
written to the network log. Message Variables
autooper
Operator response The operator ID of the distributed autotask that
was ended.
autonet
System programmer response The network ID of the distributed autotask that
was ended.
Search for the error in the diagnostic dump that was
autodomain
written to the network log. See messages DWO523E
The domain id of the distributed autotask that was
and DWO604E in the dump for more information. If
ended.
there are installation exits in use that modified or
returned buffers for this message, ensure that the termoper
exits have properly formed the DSIAIFRO vectorized The operator ID of the task that issued the
data extensions. Verify that the length fields are ENDTASK FORCE request. The value is DSIUDST if
correct. the ending of DSIUDST caused active distributed
autotasks to end.
DWO523E DIAGNOSTIC DUMP OF DSIAIFRO
termnet
VECTORIZED DATA FOR TASK
The network ID of the operator that issued the
'task'
ENDTASK FORCE request.
Explanation termdomain
The domain id of the operator that issued the
This message is a title line within a diagnostic dump. ENDTASK FORCE request.
Message Variables
System action
task
The name of the task reporting the error. The ENDTASK FORCE request or the ending of the
DSIUDST task causes the distributed autotask to end.
System action If an operator issues the ENDTASK FORCE command
to a distributed autotask that the operator did not
The vectorized data from the DSIAIFRO extensions is start, the operator receives message DWO571I and
written to the network log. the operator who started the distributed autotask
receives message DWO524I.
Operator response If the DSIUDST task ends and logs off the active
Notify the system programmer. distributed autotasks, no RMTCMD security table
authorization checking is done. The RMTCMD security
System programmer response table checking applies only to explicit invocations of
the ENDTASK command.
See the description for message DWO522E.

Notify the system programmer. Issue another task
RMTCMD command to the autotask that was ended. The name of the task.
This establishes the session again if that operator is
DWO533I NETVIEW BRIDGE DATABASE
not already in use.
SERVER serverid QUIESCED

Explanation
If this message is issued because the DSIUDST task
The NetView Bridge dispatcher has completed cleanup
ended, restart the DSIUDST task when appropriate. If
for the specified server.
this message is issued because of an ENDTASK FORCE
command, determine whether this request must be Message Variables
authorized and update your security tables to limit the
serverid
use of the ENDTASK command.
The database server name.
DWO525I TEST OF NETVIEW AUTOMATION
DWO534I command COMMAND FAILED, task
FILE "member" WAS
ALREADY ACTIVE FOR THIS
UNSUCCESSFUL
FUNCTION
Explanation
Explanation
A test of a NetView automation member has detected
The request for command failed. A command can only
errors in the automation statements. You will receive
be invoked once from each task in the NetView
additional error messages indicating the incorrect
program, and while the task that issued that command
NetView automation statements.
is active, it performs the function that this command
Message Variables sets up. task is active and has already issued the
command.
member
The name of the member specified by AUTOTBL. Message Variables
DWO530I INVALID MESSAGE ID FOR command
NETVIEW BRIDGE TRANSACTION The name of the command that failed.
REPLY task
The name of a task that is already active and
Explanation providing this function.
The TRANRCV command was invoked with something
other than message DWO548I. System action
The command is ignored and processing continues.
System action
Transaction reply processing is ended. Operator response
Operator response
Verify that only one task is active at a time using this
System programmer response command. Remove the cause for the second task
trying to issue the command while the first task is still
Modify the command list that issues the TRANRCV
active.
command.
DWO535I PPI RECEIVER queue HAS BEEN
DWO531I NETVIEW BRIDGE
REACTIVATED BY task
INITIALIZATION COMPLETE FOR
TASK = task
Explanation
Explanation The receiver queue in this message has already been
defined to the program-to-program interface (PPI).
The initialization process for NetView Bridge has
This is a warning message to prevent another task
successfully completed.

from reactivating predefined queues that were defined Operator response
but not active.
Message Variables
queue System programmer response
The program-to-program interface queue being Modify the incorrect parameter.
reactivated.
DWO539I command COMMAND FAILED,
task
queue IS ALREADY DEFINED
The name of the task that the command is running
under.
Explanation
System action You did not enter the command text correctly. All
program-to-program interface queue names must be
The specified queue is reactivated.
unique. The queue specified is already active in the
program-to-program interface.
Operator response
Message Variables
command
queue
Verify that the task reactivating this queue is the The name of the queue in error.
desired task. If not, provide a unique queue name and
recycle the task.
System action
DWO536I NETVIEW BRIDGE PROCESSING
The NetView program ignores the entire command
RESUMED FOR TASK = task
entry.
Explanation
Operator response
A full-screen component panel interrupted the
NetView Bridge autotask processing. NetView Bridge
processing has resumed.
Message Variables
Provide a unique queue name and issue the command
task again.
The name of the task that has been resumed.
DWO540I UNEXPECTED ERROR FROM
DWO537I NETVIEW BRIDGE TRANSACTION CONVCON-RETURN CODE =
PARAMETER VALUE FOR variable retcode
IS TOO LONG. RETURN CODE =
retcode
Explanation
Explanation The MVS CONVCON service encountered an error

condition.
A parameter in the transaction request or reply has a
value that is too long. Message Variables
Message Variables retcode

The value of register 15 at the time of the error.
variable
The variable that is too long.
System action
retcode
The return code. Processing continues and the command request is not
executed.
System action
Operator response
Transaction processing is ended (return code = 4), or
the parameter value is truncated (return code = 2). Notify the system programmer of the return code
value and the console ID or console name that you
entered.

System programmer response greater than MAXREPLY, so COSTIME has been set to
X'FFFFFFFF', which causes COSTIME to use the
Verify that the console ID or console name entered is
MAXREPLY value.
valid.
DWO541I CONVCON SERVICE IS NOT System action
AVAILABLE
The time-out value used is now equal to the
MAXREPLY value. The value of COSTIME is reset to
Explanation MAXREPLY.
The MVS CONVCON service is not operational at this
time. Operator response
System action
Processing continues and the command request is not System programmer response
executed.
If a time-out value greater than MAXREPLY is required,
change the value of MAXREPLY using the DEFAULTS
Operator response command. If a time-out value less than MAXREPLY is
Notify the system programmer. required, change the value of COSTIME using the
DEFAULTS command.
DWO542E DIAGNOSTIC DUMP OF DATA FOR
TASK task CANCELED DUE TO DWO546I TRANSACTION PARAMETERS ARE
NON-ADDRESSABLE STORAGE AS FOLLOWS: DESTTASK =
desttask, DESTDOM = destdom,
Explanation DESTNET = destnet, ORIGTASK =
origtask, ORIGDOM = origdom,
The NetView program encountered non-addressable ORIGNET = orignet, TRANSID =
storage while trying to create a diagnostic dump of transid, CORRID = corrid,
vectorized data for the network log. RESPCODE = respcode, TRTYPE =
Message Variables trtype, ORIGDOME = origdome,
ORIGNETE = orignete
task
The name of the task for which a diagnostic dump Explanation
was being made.
This message accompanies DWO151I, DWO152I,
System action DWO156I, or DWO157I when transaction data is
available. This is an information message. If one of the
The diagnostic dump is canceled. following fields is unknown, UNKNOWN is placed in
the field. Some of the fields might be lost on errors if
Operator response the information is cleaned up before the reply is
received. The time-out for this cleanup might be
Notify the system programmer. adjusted using DEFAULTS NOREPLY=x, where x is the
time in seconds. The initial default is 120 seconds (2
System programmer response minutes).
There was an error in the vectorized data that was Message Variables
passed to the NetView program. Ensure that there are
no errors in any command procedures that invoke the desttask
CNMPMDB or DSIMMDB services. The destination task operand.
destdom
DWO543I PREVIOUS VALUE OF COSTIME IS The destination domain operand.
INVALID WITH THE NEW VALUE
OF MAXREPLY. COSTIME VALUE destnet
HAS BEEN SET TO MAXREPLY The destination network operand.
origtask
Explanation The originating task operand.
MAXREPLY has been reset to a value that is less than origdom

the current value of COSTIME. COSTIME cannot be The originating domain operand.

orignet DWO550I PROGRAM TO PROGRAM QUEUE
The originating network operand. queue IS FULL.
transid
The transaction ID operand. Explanation
corrid The program-to-program interface receiver queue has
The correlator ID operand. exceeded its specified limit.
respcode Message Variables
The response code operand.
queue
trtype
The name of the program-to-program interface
The transaction type operand.
queue that has exceeded its limit.
origdome
The originating domain of the error (displayed only System action
with DWO151I).
The program-to-program interface buffer has not been
orignete
added to the queue.
The originating network of the error (displayed
only with DWO151I).
Operator response
DWO548I TRANSID = transid, CORRID =
corrid, VOCAB = vocab, DESTTASK Notify the system programmer.
= desttask, DESTDOM = destdom,
DESTNET = destnet, ORIGTASK = System programmer response
origtask, ORIGDOM = origdom,
• For the HOLD queue, issue the RTRINIT command
ORIGNET = orignet, RESPCODE =
again with a larger HOLD queue limit.
respcode, TRTYPE = trtype
• For the READY or OUTPUT queue, contact IBM
Software Support for programming assistance.
Explanation
• For the TIIN queue associated with the database
This message contains the parameters of a transaction server, see the documentation for your database
reply. Blank fields indicate the data was not provided. server.
Message Variables Note: You might want to consider adding additional
transid database servers to reduce traffic congestion.
The transaction ID parameter.
DWO551I STATUS FOCAL POINT: PRIMARY
corrid fpname
The correlator ID parameter.
vocab Explanation
The vocabulary parameter.
This message is the response to a LIST
desttask FOCPT=STATUS command or the response when the
The destination task parameter. NetView program processes a DEFFOCPT
destdom TYPE=STATUS definition statement.
The destination domain parameter. Message Variables
destnet
fpname
The destination network parameter.
The name of the NetView program in the remote
origtask node that is the primary status focal point for the
The originating task parameter. specified NetView program.
origdom
The originating domain parameter. System action
orignet Processing continues.
The originating network parameter.
DWO552I CHANGEFP STATUS COMPLETED
respcode
The response code parameter. SUCCESSFULLY BUT
trtype INITIATED -- CNMTAMEL TASK
The transaction type parameter. NOT ACTIVE.

Explanation the CNMTAMEL task is not active at the distributed
host, the two hosts cannot communicate
The status focal point for this host has changed, but
(synchronize). Therefore, no attempt was made to
initiate the synchronization series between the two
new focal point because the CNMTAMEL task is not
hosts.
active. Therefore, the synchronization series to the
new status focal point cannot be initiated. Message Variables
host1
System action The domain ID of the distributed host.
System action
Operator response The status focal point for the distributed host host1 is
If you want to forward status data, start the defined as this host.
collector. The host then begins sending status to its Operator response
status focal point. If you do not want to forward status
data, ignore the message.
DWO553I CHANGEFP STATUS COMPLETED System programmer response
SUCCESSFULLY BUT
SYNCHRONIZATION SERIES NOT Verify that the target ID in the CHANGEFP command
INITIATED -- THIS HOST IS A was entered correctly. If it was, contact an operator at
STATUS FOCAL POINT. the distributed host to determine why the CNMTAMEL
task is not active and therefore not forwarding status
information to this host. If the target ID was not
Explanation correct, change it and issue the CHANGEFP STATUS
The status focal point was changed for this host but command again.
this host is a status focal point. This is not correct. The
DWO555E DISTRIBUTED HOST host1
target host in the CHANGEFP STATUS command must
ACCEPTED CHANGEFP STATUS
be a status collector. Because status focal point hosts
COMMAND BUT
do not communicate (synchronize) with other status
focal point hosts, no attempt was made to initiate this
INITIATED -- host1 IS A STATUS
communication. That is, the synchronization series
FOCAL POINT.
was not initiated.
Explanation
System action
The distributed host received the CHANGEFP STATUS
command and processed it successfully, but cannot
communicate with this host because both hosts are
Operator response defined as status focal points. Therefore, no attempt
If you want to forward status data, stop the was made to initiate the synchronization series
CNMTAMEL task and restart it, defining this host as a between the two hosts.
status collector. The host then begins sending status Message Variables
to its status focal point. If you do not want to forward
status data, ignore the message. host1
The domain ID of the distributed host.
DWO554E DISTRIBUTED HOST host1
ACCEPTED CHANGEFP STATUS System action
COMMAND BUT
SYNCHRONIZATION SERIES NOT The status focal point for the distributed host host1 is
INITIATED -- CNMTAMEL TASK defined at this host.
NOT ACTIVE AT host1.
Operator response
command and processed it successfully, but because

Verify that the target ID in the CHANGEFP command Contact IBM Software Support.
was entered correctly. If it was, contact an operator at
DWO557E CHANGEFP STATUS COMPLETED
the distributed host to determine why it is running as a
SUCCESSFULLY BUT
status focal point and is therefore not forwarding
status information to this host. If it was not entered
INITIATED -- REASON CODE
correctly, correct the ID and issue the CHANGEFP
reason.
command again.
Note: This change at the distributed host that is Explanation
running as a status focal point does not affect status
forwarding at this host. The status focal point for this host was changed, but
DWO556E DISTRIBUTED HOST host1 new status focal point because of the reason code
ACCEPTED THE CHANGEFP code. Therefore an attempt was not made to initiate
STATUS COMMAND BUT the synchronization series between the two hosts.
INITIATED -- REASON CODE code. Message Variables
reason
Explanation The reason that the synchronization series cannot
be initiated.
command and processed it successfully, but cannot Note: These errors occurred at this host.
communicate (synchronize) with the new status focal
point because of the reason code code. Therefore, no
attempt was made to initiate the synchronization 01
series between the two hosts. Cannot load the module DUIABUFF to build the
buffer to initiate the synchronization series;
Message Variables installation error.
host1 02
The domain name of the distributed host. Cannot get storage to build the buffer to
code initiate the synchronization series.
The reason code indicating why the 03
synchronization series cannot be initiated. Cannot send the buffer to the CNMTAMEL task
Note: These errors occurred at the distributed to initiate the synchronization series.
host.
System action
01
buffer to initiate the synchronization series; Operator response
installation error. If you want to forward status data, notify the system
02 programmer. If not, ignore this message.
Cannot get storage to build the buffer to
initiate the synchronization series. System programmer response
03 If you want to forward status data, contact IBM
Cannot send the buffer to the CNMTAMEL task Software Support. If not, ignore this message.
to initiate the synchronization series.
DWO558E CHANGEFP COMMAND FOR
System action STATUS FAILED: CNMTAMEL TASK
MUST BE ACTIVE AND DEFINED
The status focal point for the distributed host host1 is AS A STATUS FOCAL POINT.
defined as this host.
Operator response

Explanation DWO561E ATTACH FAILED FOR SUBTASK
“SYSNVSAM”
The CHANGEFP command for status failed because
either the CNMTAMEL task was not active, or it was
active but not running as a status focal point. Explanation
The program-to-program interface VSE subtask
System action SYSNVSAM was not attached by the VSE operating
system.
The status focal point is not changed.
System action
Operator response
Processing ends.
Start the CNMTAMEL task if it is not active. If it is
active, stop the CNMTAMEL task and restart it as a
status focal point. Operator response
DWO559E CHANGEFP COMMAND FOR Notify the system programmer.

STATUS FAILED: NOT ABLE TO
DETERMINE STATE OF CNMTAMEL System programmer response
TASK -- DSILCS RETURN CODE
Correct the previous errors and restart the program-
retcode.
to-program interface job.
Explanation DWO562E THE NETVIEW PROGRAM TO

PROGRAM INTERFACE IS
The CHANGEFP command for status failed because ALREADY ACTIVE
the system was not able to determine the state of the
CNMTAMEL task.
Explanation
Message Variables
The program-to-program interface job is already
retcode started. Only one program-to-program interface is
The return code from the DSILCS macro. allowed per system.

The status focal point is not changed. Processing ends.
DWO563E VSE SUBSID FAILED FOR TASK
Operator response
task, RETURN CODE = X'retcode'
Explanation
System programmer response The program-to-program interface's attempt to
Contact IBM Software Support. identify itself as a VSE subsystem failed.
DWO560E THE NETVIEW PROGRAM TO Message Variables

PROGRAM INTERFACE IS task
TERMINATING. The name of the task (either SYSNVRAM or
SYSNVSAM).
Explanation retcode
The program-to-program interface is ending because The return code in register 15 from the SUBSID
of a previous error. macro.

The program-to-program interface job ends. Processing ends.

Correct the previous errors and restart the program- Notify the system programmer.
to-program interface job.

Check to see if the program-to-program interface is Processing continues without the needed storage. The
already active in the system. request that caused the need for storage might not be
honored.
DWO564E UNEXPECTED dtlayer ERROR FOR
FUNCT = function. RETURN CODE =
retcode REASON CODE = reason Operator response
Explanation
An unexpected error occurred while using the XPCC or System programmer response
IUCV data transport layer of the operating system. If this problem persists, increase the amount of
Message Variables storage available to the program-to-program interface.
dtlayer DWO566E THE dtlayer CONNECTION FOR PPI

The XPCC or IUCV data transport layer TASK task FAILED
function
Is IDENT, CONNECT, SEND, RECEIVE, DISCONN, Explanation
PURGE, or SEVER The initial communication connection was not
retcode established. Data cannot be sent through the program-
The return code in register 15 from the XPCC or to-program interface (PPI) until the connection is
IUCV macro made.
reason Message Variables
The reason code in IJBXRETC or IPRCODE
dtlayer
The XPCC or IUCV data transport layer.
System action
task
Processing continues even though the specific action The task name (SYSNVRAM).
fails. The action is not retried and the data is lost.
System action
Operator response
Processing ends.
Operator response
Verify that XPCC and IUCV are installed and
functioning properly. System programmer response
DWO565I command FOR STORAGE FAILED Verify that XPCC and IUCV are installed and
FOR TASK task FOR NUMBER OF functioning.
bytes BYTES
DWO567I NETVIEW PROGRAM TO
Explanation PROGRAM INTERFACE
INITIALIZATION IS COMPLETE
An attempt to obtain or free storage for processing
failed. Explanation
Message Variables The program-to-program interface is active.
command DWO568I TOTAL SIZE OF NETVIEW BRIDGE
The GET or FREE command.
TRANSACTION REQUEST IS
task GREATER THAN 31K BYTES
The name of the task (either SYSNVRAM or
SYSNVSAM). Explanation
bytes
The transaction being sent exceeds the allowed
The amount of storage, in bytes, that was
maximum of 31K bytes.
requested.

System action X'08A80001'
Origin or destination NAU name unknown. For
Transaction request processing ends.
the NetView program, either the origin or the
destination network ID in the MDS header is
Operator response not valid.
Notify the system programmer. X'08A80003'
The target NetView system does not know the
System programmer response MS application name specified. This usually
indicates that the target application is not
Modify the transaction request to reduce its size. registered with the LU 6.2 transport. Verify that
DWO569I NETVIEW BRIDGE TRANSACTION the DSIUDST and DSIHPDST tasks at the target
PARAMETER NAME variable IS NetView are active.
TOO LONG. RETURN CODE = X'08A8000A'
retcode Three attempts were made to converse with
the specified netid.luname without success.
Explanation This usually indicates that a netid.luname that
is not valid was specified in the command or a
A parameter name in the transaction request or reply communication link failure has occurred.
is too long.
X'08A8000B'
Message Variables Data cannot be sent because of a failure in the
variable target NetView transport support.
The name of the variable in error. X'08A8000C'
retcode Data cannot be sent because of a problem
The return code. communicating with the target application.
Verify that the DSIUDST and DSIHPDST tasks
at the target NetView are active.
System action
X'08A8000D'
The transaction processing ends (return code = 4), or Communication has been lost because of a
the parameter value is truncated (return code = 2). failure in the originating NetView transport
support.
Operator response X'08A90005'
Notify the system programmer. Data cannot be sent because of a failure in the
originating NetView transport support, for
example, a storage shortage.
Modify the parameter to conform to the appropriate System action
size restriction.
The session is not established.
DWO570I UNABLE TO ESTABLISH REMOTE
SESSION ON netid.luname WITH
Operator response
SENSE: X'sensecode'
Resolve the problem indicated by the SNA sense code
Explanation and issue the command again.
Your system was not able to establish a remote DWO571I DISTRIBUTED AUTOTASK taskid
session with the target NetView system because of the ON netid.domainid TERMINATED
reason indicated by the SNA sense code received.
Explanation
Message Variables
An ENDTASK command was entered and, as a result,
netid.luname
the distributed autotask taskid ends.
The network identifier for the reported-on node.
sensecode Message Variables
The SNA sense code received. This code is one of taskid
the following: The distributed autotask that ended.

netid.domainid System action
The network and domain identifiers of the NetView
The request is ignored and processing continues.
program that generated this message.
Operator response
System action
Issue the command again using a valid operator ID for
The association with the distributed autotask is lost.
the target NetView system.
DWO572I DISTRIBUTED OPERID operatorid System programmer response
ALREADY IN USE ON
netid.domainid If the destination operatorid was excluded from
DSIOPF on the target NetView system by mistake,
update DSIOPF to include the desired operator ID.
Explanation
DWO574E DISTRIBUTED AUTOTASK FAILED
The specified operatorid might already be logged on
ON netid.domainid
locally to the target NetView system, or the distributed
autotask for the specified operatorid might have
already been started by another operator. Explanation
Message Variables The request cannot be serviced because of an internal

fault or failure on the target NetView system.
operatorid
The operator ID specified for the target NetView Message Variables
system. netid.domainid
netid.domainid The network and domain identifiers for the node
The network and domain identifiers for the on which the report was being built.
reported-on node.
System action
System action The request is ignored and processing continues.
Operator response
Operator response Issue the command again and, if unsuccessful, retain
Issue a LIST STATUS=OPS or LIST operatorid the console logs and contact the system programmer.
command through another distributed autotask to
determine the status of the specified operator ID on System programmer response
the target NetView system. If you are authorized, you
can issue a ENDTASK FORCE command to end the Perform NetView traces at the originating and target
existing distributed autotask. NetView systems to isolate the problem. After
completing the traces, contact IBM Software Support.
DWO573E OPERID operatorid INVALID ON
netid.domainid DWO575I session_type TERMINATED ON
netid.luname WITH SENSE:
X'sensecode'
Explanation
A destination operatorid was entered that is unknown Explanation
to the target NetView system.
A session between the local NetView system and the
Message Variables indicated NetView system was ended with the SNA
operatorid sensecode.
The operator ID specified for the target NetView Message Variables
system.
session_type
netid.domainid The session type that ended, such as RMTCMD.
The network and domain identifiers for the
reported-on node. netid.luname
The network identifier and the LU name identifying
the NetView system which had a session with the
local NetView system.

sensecode System action
The SNA sense code that was received. This code
can be one of the following:
X'08A80003' Operator response
The target NetView system does not know the
MS application name specified. This usually Issue the RMTCMD command again with the
indicates that the target application is not appropriate command text.
registered with the LU 6.2 transport. Verify that DWO577E STOP OR FORCE COMMAND
the DSIUDST and DSIHPDST tasks at the target INVALID FOR operatorid ON
NetView are active. netid.domainid
X'08A8000A'
Three attempts were made to converse with Explanation
the specified netid.luname without success.
This usually indicates that a netid.luname that An ENDTASK STOP or ENDTASK FORCE was entered
is not valid was specified in the command, or and the specified destination operatorid was not active
that a communication link failure has occurred. as a distributed autotask. In the case of a STOP, the
originating operatorid did not match the originating
X'08A8000B'
operatorid that started the distributed autotask.
Data cannot be sent because of a failure in the
target LU 6.2 transport support. Message Variables
X'08A8000C' operatorid
Data cannot be sent because of a problem The operator ID specified for the target NetView
communicating with the target application. system.
Verify that the DSIUDST and DSIHPDST tasks
netid.domainid
at the target NetView are active.
The network and domain identifiesr for the node
X'08A8000D' on which the reported was being built.
Communication has been lost because of a
failure in the originating LU 6.2 transport System action
support.
X'08A80012'
Unrecoverable failure of user-mode session.
MDS has detected an error on a user-mode Operator response
session (a user-mode session in this context is Issue a LIST STATUS=OPS or LIST operatorid
one with a mode name other than SNASVCMG). command through another distributed autotask to
Retries have been exhausted. Application determine the status of the specified operatorid on the
program data might have been lost. target NetView system. Check to see if you entered the
X'08A90005' operator ID correctly. If you did not, issue the
Data cannot be sent because of a failure in the command again with the correct operatorid. If you
originating LU 6.2 transport support, for entered the operatorid correctly, then you are not the
example, a storage shortage. operator who started this autotask and you are not
allowed to stop it. If you are authorized, you can issue
System action a ENDTASK FORCE command to end the existing
distributed autotask.
DWO578E INVALID DATA STRUCTURE
Operator response RECEIVED
Resolve the problem indicated by the SNA sense code Explanation

and issue the command again.
A data structure that was not valid was received by the
DWO576E COMMAND TEXT NOT PRESENT IN DSIUDST task on a target NetView system. The
'RMTCMD' COMMAND DSIUDST task is used by the RMTCMD and ENDTASK
commands.
Explanation
A RMTCMD was entered that did not contain any System action
command text. The request is ignored and processing continues.

Retain the console logs and contact the system Notify the system programmer.
programmer.
Diagnostic information about the MDB in error is
Perform NetView traces at the originating and target written to the network log if the length of the MDB is
NetView systems to isolate the problem. After not zero. Attempt to identify the source of the
completing the traces, contact IBM Software Support. improperly formatted MDB. If you have customized or
written applications that use the CNMPMDB or
DWO600E TASK 'task' RECEIVED DSIMMDB NetView services, verify that you are
INCOMPLETE MDB DATA creating a properly formatted MDB, giving special
attention to length and type fields.
Explanation
If the source of the improperly formatted MDB is not
Required vector data was not included in the MDB. The installation-written code, contact the support center
MDB was not processed. for the product that created the MDB.
Message Variables DWO602E TEXT LINES OF MDB IN ERROR
task FOR TASK 'task'
The task ID reporting the error.
Explanation
System action An error occurred while processing an MDB. The
The data is not processed. following lines of the multiline write-to-operator
(MLWTO) message have already been built from this
MDB or previously received related MDBs.
Operator response
Message Variables
task
System programmer response The name of the task reporting the error.
Diagnostic information about the MDB in error is

System action
written to the network log if the length of the MDB is
not zero. Attempt to identify the source of the The data follows in the lines of a multiline write-to-
incomplete MDB. If you have customized or written operator (MLWTO) message.
applications that use the CNMPMDB or DSIMMDB
NetView services, verify that you are creating a Operator response
complete MDB with all of the required vectors. Ensure
that there are no length field errors in the MDB. Notify the system programmer.
If the source of the MDB is not installation-written

code, contact the support center for the product that
created the MDB. Use the information that follows this message to help
determine the source of the error in the MDB. See the
DWO601E TASK 'task' RECEIVED MDB DATA error descriptions for messages DWO600E and
WITH FORMAT ERRORS DWO601E for more information.
Explanation DWO603E DIAGNOSTIC MDB DUMP FOR

TASK 'task'
A formatting or length error was detected in an MDB
vector. The MDB was not processed.
Explanation
Message Variables
An EBCDIC representation of the hex data is presented
task on the following lines.
The name of the task reporting the error.
Message Variables
System action task

The data is not processed.

The data follows in the lines of a multiline write-to- Notify the system programmer.
operator (MLWTO) message.
Operator response
Review the exit code to verify that the buffer is being
Notify the system programmer. built with all fields set correctly.
DWO607E DIAGNOSTIC SOURCE OBJECT
System programmer response DUMP FOR TASK 'task'
Use the data provided in the diagnostic dump to
determine the error in the vectorized data. See the Explanation
error descriptions for messages DWO600E and
This message is a title line within a diagnostic dump.
DWO601E for more information.
Vectorized data for the source object follows this
DWO604E DATA BUFFERS OF AIFR IN message.
ERROR FOR TASK 'task'
Message Variables
Explanation task
The name of the task reporting the errors.
This message is a title line within a diagnostic dump.
The data buffers of the AIFR in error follow this
System action
message.
The vectorized data from the source object is written
Message Variables
to the network log.
task
The name of the task reporting the error. Operator response
System action
This message and the data buffers of the AIFR in error System programmer response
are written to the network log.
Search for the error in the diagnostic dump that was
written to the network log. See messages DWO522E,
Operator response
DWO523E, and DWO604E in the dump for more
Notify the system programmer. information. If installation exits are in use that
modified or returned buffers for this message, ensure
System programmer response that the exits have properly formed the DSIAIFRO
vectorized data extensions. Verify that the length fields
See the description for message DWO522E. are correct.
DWO605E 'exitnum' RETURNED A BUFFER DWO608I MESSAGE QUEUING RESUMED
WITH ERRORS. THE BUFFER IS FOR EXTENDED CONSOLE
DISCARDED. 'console'
An installation exit returned an incorrect buffer. The Messages are again being queued to the specified
buffer contained errors that were detected by the console. Message queuing to this extended console
NetView program. had been halted because of QLIMIT or console storage
Message Variables error conditions.
exitnum Message Variables

The installation exit number. console
System action
The returned buffer is discarded. The original buffer System action
presented to the exit is also discarded. Messages begin queuing to the extended console and
are retrieved and processed.

DWO609E TASK 'task' RECEIVED AN MDB codes
WHICH WAS NOT PROPERLY The system sense and modifier sense codes
CORRELATED. returned by the node in the error reply subvector.

A correlation parameter that is not valid was passed to Processing of the command ends.
DSIMMDB or CNMPMDB.
task Notify the system programmer.

System action Determine the reason that the receiving node cannot
The MDB is not processed. perform the function.
DWO611I command REQUEST NOT
Operator response PERFORMED BY ID node FOR
(APPL | STATION | LINE | PORT) =
'(name | number)', SENSE CODES =
X'codes' FUNCTION NOT ENABLED
Diagnostic information about the MDB is written to the Explanation
network log if the length of the MDB is not zero.
The receiving node cannot perform the requested
Attempt to identify the source of the improperly
function because the request is inconsistent or in
correlated MDB.
conflict with other operations within the node.
If you have customized or written applications that use
Message Variables
the CNMPMDB or DSIMMDB NetView services, verify
that you are passing the correct correlation parameter command
as described in IBM Z NetView Programming: The command request issued.
Assembler and IBM Z NetView Programming: PL/I and node
C. If the source of the improperly correlated MDB is The name of the receiving network node.
not installation-written code, contact the support
center for the product that created the MDB. name | number
The target station, line, or port of the request.
DWO610I command REQUEST NOT codes
PERFORMED BY ID node FOR The system sense and modifier sense codes
(APPL | STATION | LINE | PORT) = returned by the node in the error reply subvector.
'(name | number)', SENSE CODES =
X'codes' FUNCTION NOT
SUPPORTED System action
Explanation
The receiving node cannot perform the requested Operator response
function because the request is inconsistent or in Notify the system programmer.
command Determine the reason that the receiving node cannot
The command request issued. perform the function.
node DWO612I command REQUEST NOT
The name of the receiving network node. PERFORMED BY ID node FOR
name | number (APPL | STATION | LINE | PORT) =
The target station, line, or port of the request. '(name | number)', SENSE CODES =
X'codes' FUNCTION IN USE

The receiving node cannot perform the requested Notify the system programmer.
conflict with other operations within the node. System programmer response
Message Variables Determine the reason that the receiving node cannot
command perform the function.
The command request issued. DWO615I command REQUEST NOT
node PERFORMED BY ID node FOR
The name of the receiving network node. (APPL | STATION | LINE | PORT) =
name | number '(name | number)', SENSE CODES =
The target station, line, or port of the request. X'codes' FUNCTION NOT
SUPPORTED FOR SWITCHED LINE
codes
The system sense and modifier sense codes
Explanation
returned by the node in the error reply subvector.
System action function because the request is inconsistent or in
Message Variables
The command request issued.
node
System programmer response The name of the receiving network node.
name | number
Determine the reason that the receiving node cannot
perform the function.
codes
DWO614E command REQUEST NOT The system sense and modifier sense codes
PERFORMED BY ID node FOR returned by the node in the error reply subvector.
(APPL | STATION | LINE | PORT) =
'(name | number)', SENSE CODE =
System action
X'codes' FUNCTION INACTIVE
Explanation
Operator response
function because the request is inconsistent or in Notify the system programmer.
command Determine the reason that the receiving node cannot

The command request issued. perform the function.
node DWO616I command REQUEST NOT
The name of the receiving network node. PERFORMED BY ID node FOR
name | number (APPL | STATION | LINE | PORT) =
The target station, line, or port of the request. '(name | number)', SENSE CODES =
X'codes' FUNCTION NOT
codes SUPPORTED FOR FAILED LINE
returned by the node in the error reply subvector.
Explanation
System action The receiving node cannot perform the requested
Processing of the command ends. conflict with other operations within the node.
Message Variables

command System programmer response
The command request issued.
Follow the normal procedures for an out-of-storage
node condition.
The name of the receiving network node.
DWO619I SCREEN COPY FUNCTION:
name | number SCREEN PRINTED NOT LOGGED
codes Explanation
returned by the node in the error reply subvector. The central site control facility attempted to copy the
current panel to the network log and to the hard copy
log. The panel was printed to the hard copy log but not
System action
to the network log.
System action
Operator response
Operator response
Activate the network log.
Determine the reason that the receiving node cannot
perform the function. DWO620I SCREEN COPY FUNCTION:
SCREEN LOGGED NOT PRINTED
DWO617I SCREEN COPY FUNCTION:
SUCCESSFUL Explanation
The central site control facility attempted to copy the
Explanation
current panel to the network log and to the hard copy
The central site control facility attempted to copy the log. The panel was logged to the network log but not to
current panel to the network log and to the hard copy the hard copy log.
log. The operation succeeded.
System action
System action
Operator response
Operator response
Activate the hard copy log.
Check the network or hard copy log for the desired
output. DWO621I SCREEN COPY FUNCTION:
UNSUCCESSFUL
DWO618I SCREEN COPY FUNCTION: FAILED
Explanation
Explanation
The central site control facility attempted to copy the
The central site control facility attempted to copy the current panel to the network log and to the hard copy
current panel to the network log and to the hard copy log. The hard copy and network logs were not active;
log. There was not enough storage available for therefore, the panel was not printed in the hard copy
logging. or network log.

Processing continues. Processing continues.

Notify the system programmer. Activate the hard copy and network logs.

DWO622I AUTOMATION TABLE LISTING Explanation
listingname UNSUCCESSFULLY The NetView program’s management services
GENERATED transport layer has encountered an error that has
caused data to be discarded. However, it is not severe
Explanation enough to recycle the function.
This message indicates that the automation table Message Variables
listing listingname you specified on a previous
AUTOTBL command invocation was not successfully reason code
generated. A previous message is issued describing The type of error detected can be one of the
the failure. following:
Reason Code
A failure can be caused by any of the following:
Reason
• Specifying a listing destination member on the 1
AUTOTBL command that already exists. You can Unexpected data has been received from
reuse the name if you specify the REPLACE VTAM.
AUTOTBL command.
2
• Specifying a listing destination member that is Data has been received from VTAM prior to
already in use. synchronization completion.
• An I/O error. 3
• A system macro failure. A DSIMQS macro failure or storage request
failure caused data to be lost in the transport.
Message Variables
4
listingname Data has been received from a sender ID other
The member or file name of the listing member than VTAM.
specified on the AUTOTBL command.
System action
System action
An unsuccessful listing prevents an automation table
replacement from occurring.
Operator response
Locate the previous message that indicates the listing
failure and correct the source of the failure. If you are System programmer response
unable to correct the problem, notify the system Following are the responses for reason.
programmer.
Reason Code
Response
1
Locate the previous message that indicates the listing Contact IBM Software Support.
failure and correct the source of the failure.
2
DWO624I MANAGEMENT SERVICES Contact IBM Software Support.
TRANSPORT INITIALIZED. 3
Ignore isolated instances of this message. If the
Explanation problem persists, attempt to stop and restart the
DSI6DST task. If this does not solve the problem,
The management services transport layer for the
NetView program has initialized.
4
DWO625E MANAGEMENT SERVICES Contact IBM Software Support.
TRANSPORT ERROR. REASON
CODE IS reason code. DWO626E COSTIME VALUE OF value1
PROCESSING CONTINUES. CANNOT EXCEED MAXREPLY
VALUE OF value2. CURRENT
VALUES ARE: COSTIME value3,
MAXREPLY value4.

Explanation 3
A synchronization request was received from
The time-out value specified for common operations
VTAM.
services (COS) commands (COSTIME) exceeds the
time-out value for the LU 6.2 transport (MAXREPLY). 4
A storage shortage has caused important
Message Variables processing in the transport layer to fail.
value1 5
The value of the COSTIME requested on the Unexpected data was received from VTAM.
DEFAULTS command.
6
value2 The NetView program’s program-to-program
The maximum time-out value of the LU 6.2 interface receiver cannot be successfully
transport. defined, because a receiver is already defined.
value3 number
The current value of COSTIME. The number outstanding transactions awaiting a
value4 reply that have been cancelled.
System action
System action The NetView program will disconnect its program-to-
The COSTIME value is not updated. program interface receiver, if defined, and generate
MDS_MU error messages for local MS applications for
Operator response all outstanding transactions. The NetView program will
initialize MS transport again after all transactions have
Issue the DEFAULTS command again with a valid been cleared. NetView might wait for up to 5 minutes
COSTIME value. before retrying initialization. The user might recycle
DSI6DST to force an immediate initialization retry.
DWO627E MANAGEMENT SERVICES
TRANSPORT RE-INITIALIZING.
REASON CODE IS reason code. Operator response
NUMBER OF TRANSACTIONS Following are the operator responses for each reason
CANCELLED ARE number. code.
Reason Code
Explanation
Response
The NetView program’s management services (MS) 1
transport layer has encountered an error that has Verify that the program-to-program interface is
caused it to cancel outstanding transactions and active. If not, restart it. Operators can use the
reinitialize its interface with VTAM. The NetView DISPPI or DISBQL command to determine if the
program’s management services transport is now program-to-program interface is active.
using the program-to-program interface. The cause of
this error can be the program-to-program interface. 2
Verify that the program-to-program interface is
Message Variables active. If not, restart it. Use the DISPPI or DISBQL
reason code command to verify that VTAM’s program-to-
The MS transport is reinitializing because of one of program interface receiver (ISTMTRCV) is active. If
the following: not, wait until VTAM activates it.
3
Reason Code
None.
Reason
4
1
None.
The NetView program’s program-to-program
interface receiver cannot be successfully 5
defined. Notify the system programmer.
2 6
A program-to-program interface failure was Notify the system programmer.
detected on a request by the NetView program. If this message is received several times after the
program-to-program interface has been activated, it

indicates a failure to initialize the transport. Stop task of this error. When indicated, verify that the device is
DSI6DST and notify the system programmer. defined and initialized correctly.
DWO650I operid NOT LOGGED ON
Following are the responses for the reason code. Explanation
Reason Code This message is in response to a LIST command
Response issued for an operator ID that is either not logged on or
1-5 not valid.
If the problem cannot be fixed by activating the Message Variables
program-to-program interface and recycling the
DSI6DST task, contact IBM Software Support. operid
The NetView operator ID given in the LIST
6
command.
If multiple NetView programs are running under
the same VTAM, only one can have a program-to-
program interface with VTAM. Verify that Operator response
VTAMCP.USE=NO has been included (or defaulted) Ensure you entered a valid operator ID.
for all NetView programs except the one that must
have the interface. DWO653I DISPLAY DEFAULTS OVERRIDES
If the problem still exists, recycle the program-to-

program interface. If recycling the interface fails, Explanation
contact IBM Software Support. This message provides header information for the LIST
7 OVERRIDE command.
Verify that the SSI level is V2R4 or greater.
System action
DWO628I A MACRO FAILURE OCCURRED
DURING LOGON. LOGON Processing continues.
ABORTED. LUNAME = 'luname'. DWO654I DISPLAY DEFAULTS
This message is issued during logon processing when This message provides header information for the LIST
a presentation services error occurs while DEFAULTS command.
presentation services is trying to send the NetView
logon screen. This message is also issued if the
System action
number of operator terminals that can logon to
NetView and remain in session at the same time Processing continues.
exceeds 4096.
DWO656E THE VALUE, value, IS NOT IN THE
Message Variables DEFAULTS SENDMSG LIST.
luname
The name of the device attempting logon. Explanation
The DEFAULTS command was issued to delete a
System action nonexistent value from the SENDMSG list.
The logon fails. Message Variables
value
Operator response
The value that did not exist in the SENDMSG list.
Retry the logon. If the problem persists, notify the
system programmer. System action
The value was not deleted from the SENDMSG list
because it did not exist.
The netlog might contain a DWO050E or DWO195I
message with additional information about the cause

Ensure that the DEFAULTS command was coded Verify the syntax of the NetView automation table
correctly. entry. Correct the entry if necessary and refresh the
NetView automation table.
DWO657E THE VALUE, value, ALREADY
EXISTS IN THE DEFAULTS DWO659I THE FIELD, field, DATA TYPE IS
SENDMSG LIST. NOT SUPPORTED BY command
COMMAND.
Explanation
Explanation
The DEFAULTS command was issued to add a value to
the SENDMSG list, but the value already exists. An ORCONV command was issued to update a field in
the Resource Object Data Manager (RODM) but the
Message Variables
field was not of the type INTEGER, SMALL INTEGER,
value FLOATING POINT, or CHARACTER.
The value that already exists in the SENDMSG list.
Message Variables
System action field

The name of the field that was to be updated.
The value was not added to the SENDMSG list because
command
it was already in the list.
The name of the command that was issued.
Operator response
System action
Ensure that the DEFAULTS command was coded
correctly.
DWO658E THE command COMMAND keyword Operator response
MUST BE USED WITH keyword2.
If the command was executed because of automation,
notify the system programmer that there is an error in
Explanation
the automation table. Otherwise, check the command
The specified keyword can only be used in conjunction and try again. Make certain that the field that is being
with another keyword. updated is of a valid type.
Message Variables
command
The name of the command that was issued. Ensure that the RODM field is of a valid type. Verify the
syntax of the NetView automation table entry. Correct
keyword the entry if necessary and refresh the NetView
The name of the keyword that is dependent on automation table.
another keyword.
keyword2 DWO670I AN ASSIST HAS BEEN REQUESTED
The name of the keyword that needs to be FOR THE FOLLOWING COMMAND,
specified. SENDER = sender, SENDER TOKEN
= token.
System action
Explanation
This multiline message is queued by DSIQTSK after
receiving a command request over the program-to-
Operator response
program interface that requests the ASSIST facility
If the command was executed because of automation, instead of a command buffer. The second line contains
notify the system programmer that there is an error in the command text, and subsequent lines contain
the automation table. Otherwise, check the correct sender-defined descriptor text entries.
keyword usage and try again.
Message Variables
sender
The name of the command sender.

token
DWO672I Message * was issued at
The name of the token specified by the sender. If 10/18/19 13:11:23.807 by +CONSOLE
no sender token is sent, the value displayed is N/A.
10/18/19 13:21:16.160 by AUTO1
System action
date time millisec
Processing continues. This message is intended for The date and time shown in the user's preferred
automation. date/time format, with a period-delimited number
DWO671E THE COMMAND command indicating milliseconds after the stated time.
REQUEST TO FREE NETVIEW source
STORAGE FAILED. The message source:
• job name
Explanation
• SAF user name for MVS messages
A FREEMAIN command request failed to free NetView
• operator ID for NetView messages
storage. The Resource Object Data Manager (RODM)
sends this message to the NetView system operator DWO673E AN MVS ENQUEUE OF THE
when a free-storage request within a NetView region NETVIEW chain HAS FAILED,
fails. command COMMAND IS
Message Variables TERMINATED.
command Explanation
The NetView program cannot successfully obtain a
System action system enqueue on the named chain.
The NetView program stops processing the command. Message Variables

chain
Operator response The name of the access control block (ACB) or task
vector block (TVB) chain.
command
The name of a NetView command.
Determine why the FREEMAIN command has failed, System action
and correct the problem.
The NetView program stops processing the command.
DWO672I Message msgid was issued at
date_time_and_source Operator response
The indicated message was issued at the indicated System programmer response
time. This message is seen in the context of browsing
a message log after a WHENCE command has been Determine why the enqueue failed from the DSI072E
invoked for a particular displayed message. message.
Message Variables DWO674E AN MVS DEQUEUE OF THE
NETVIEW chain HAS FAILED,
msgid
command COMMAND IS
The first blank-delimited token of the indicated
TERMINATED.
message. An asterisk (*) is displayed when cursor
position and highlighting is used to denote the
message being referred. The message can Explanation
conclude with additional information, such as the The NetView program cannot successfully dequeue
job name, the SAF user name, or the source, as in the named chain.
these examples. Note also that the msgid is not
reported in these examples. Message Variables

10/18/19 13:11:01.043 by T610EENV

chain keyword
The name of the access control block (ACB) or task The keyword in error
vector block (TVB) chain.
command System action
The name of a NetView command. The NetView program rejects the command.

The NetView program stops processing the command. If the command was issued because of automation,
Operator response the NetView automation table entry.
Notify the system programmer. If command is DSIMCAP, the command text returned
by the CNMEMCXY command list is too long. Correct
System programmer response CNMEMCXY and retry.
Determine why the dequeue failed from the DSI072E Otherwise, check the command and retry.
message.
DWO675E THE command COMMAND
TRUNCATED CHARACTER DATA. Verify the syntax of the NetView automation table
entry. Correct the entry if necessary and refresh the
Explanation NetView automation table.
The command attempted to store character data into a If command is DSIMCAP, check CNMEMCXY to make
field of insufficient length. The update ends. sure that the command text is 122 characters or less
and that the command length is set correctly.
Message Variables
DWO678E THE command COMMAND FAILED.
command
DATA KEYWORD OR PARAMETER
The name of the command that was issued to
KEYWORD DOES NOT CONTAIN
store data.
VALID NUMERIC DATA.

The NetView program stops processing the command. The ORCONV command processor attempted to
translate character data from the message into binary
Operator response or floating point data and failed.
If the command was issued because of automation, Message Variables
the NetView automation table entry. Otherwise check command
the command and retry. The name of the command.
Verify that the correct entity is being updated. Ensure The NetView program rejects the command.
that the data type of the field and data match.
Operator response
DWO677E THE DATA LENGTH OF THE
command KEYWORD, keyword, IS If the command occurred because of automation,
TOO LONG. notify the system programmer that there is an error in
the NetView automation table entry. Otherwise check
the command and retry.
Explanation
The keyword value for keyword was too large. System programmer response
Message Variables Verify in the NetView automation table that the correct
command entity is being updated. Ensure that the data type of
The name of the command the field and the data match.

DWO679E THE OBJECT IS NOT FOUND OR DWO681E THE FIELD IS NOT FOUND OR
SPECIFIED. THE COMMAND, SPECIFIED. COMMAND, command,
command, IS TERMINATED. IS TERMINATED.
The object referenced by the command was not found The field referenced by the command was not found in
in the Resource Object Data Manager (RODM) or was the Resource Object Data Manager (RODM) or not
not specified in the API call. specified in the API call.
command command
The name of the command that was issued. The name of the command.

The NetView program rejects the command. The NetView program rejects the command.

Ensure that RODM is loaded. If the command was Ensure that RODM is loaded. If the command was
ORCONV, notify the system programmer that there is ORCONV, notify the system programmer that the
an automation table entry that is not valid. automation table entry is not valid.

If the command was ORCONV, verify the syntax of the If the command was ORCONV, verify the syntax of the
NetView automation table entry. Correct the entry if NetView automation table entry. Correct the entry if
necessary and refresh the NetView automation table. necessary and refresh the NetView automation table.
For other commands, check the command referencing
DWO680E THE CLASS IS NOT FOUND OR the field that is not valid.
SPECIFIED. COMMAND, command,
IS TERMINATED. DWO682E RODM CANNOT PROCESS THE
command COMMAND. COMMAND
Explanation IS TERMINATED.
The class referenced by the command was not found

Explanation
in the Resource Object Data Manager (RODM) or was
not specified in the API call. The Resource Object Data Manager (RODM) was not
available to process the command specified.
Message Variables
Message Variables
command
The name of the command. command
System action
System action
The NetView program rejects the command.
Operator response
Operator response
Verify that RODM has been loaded. If the command
was ORCONV, notify the system programmer that an Activate RODM.
automation table entry is not valid.
DWO683E THE command UPDATE TO RODM
FAILED; UNEXPECTED DATA
System programmer response TYPE=type.
If the command was ORCONV, verify the syntax of the
NetView automation table entry. Correct the entry if Explanation
necessary and refresh the NetView automation table.
The data type referenced by the command is not valid.

Message Variables DWO685E command RODM ERROR, RETURN
CODE=retcode REASON
command
CODE=reason.
type
Explanation
The unexpected data type value.
An error occurred while the command was attempting
System action to update a Resource Object Data Manager (RODM)
entity or invoke a method in RODM.
Message Variables
If the command was ORCONV, notify the system
programmer that there is an automation table entry retcode
that is not valid. The RODM return code.
reason
System programmer response The RODM reason code.
Verify the syntax of the NetView automation table
entry if the command was ORCONV. Ensure that the System action
data type of the field matches that of the data. Correct The NetView program stops processing the command.
the entry if necessary and refresh the NetView
automation table. For other commands, check the Operator response
command referencing the data type that is not valid.
Verify that RODM is loaded. If the command was
DWO684E THE METHOD WAS NOT FOUND OR ORCONV, notify the system programmer that there is a
SPECIFIED. THE command NetView automation table entry that is not valid.
COMMAND IS TERMINATED.
Explanation
Verify the syntax of the NetView automation table
The method referenced by the command was not entry if the command was ORCONV. Correct the entry
found within the Resource Object Data Manager if necessary and refresh the NetView automation
(RODM) API call. table. For other commands, check the command
Message Variables referencing the entity that is not valid.
command DWO686E DSIQTSK WAS UNABLE TO OPEN

The name of the command. THE STARTUP DSIPARM MEMBER.

The NetView program rejects the command. The DSIQTSK subtask attempted to connect to the
DSIPARM member and failed.
Operator response
System action
Ensure that RODM is loaded. If the command was
ORCONV, notify the system programmer that an The DSIQTSK subtask ends.
automation table entry is not valid.
Operator response
System programmer response Try to start the subtask again. If it fails again, notify
Verify the syntax of the NetView automation table the system programmer.
entry if the command was ORCONV. Correct the entry
if necessary and refresh the NetView automation System programmer response
table. For other commands, check the command
referencing the method that is not valid. Verify that the DSIPARM member is correct, then
restart the subtask.

DWO687E DSIQTSK HAS NO DSIPARM System action
MEMBER SPECIFIED IN THE The duplicate task is ignored. Processing continues.
STARTUP DEFINITION.

Explanation
Remove the duplicate task name.
There is no member name defined to the DSIQTSK
subtask. DWO690I DUPLICATE RODM SPECIFIED,
rodm, AND IGNORED.
System action
Explanation
The DSIQTSK subtask ends.
A Resource Object Data Manager (RODM) was defined
Operator response more than once within the initialization file.

rodm
System programmer response The name of RODM.
The definition of the DSIQTSK subtask to the NetView
program must have a DSIPARM member name. Ensure System action
that a member name is specified and restart the The duplicate RODM is ignored. Processing continues.
NetView program.
DWO688E DSIQTSK WAS UNABLE TO FIND System programmer response
DSIPARM MEMBER, member. Remove the duplicate RODM defined in the
initialization file.
Explanation
DWO691E TOO MANY TASKS WERE DEFINED
The DSIPARM member defined to the DSIQTSK AT INITIALIZATION.
subtask was not found.
member The initialization file contained more than 64
The name of initialization member. definitions for NetView tasks.

The DSIQTSK subtask ends. The subtask ends.


Ensure that the DSIPARM member name specified in Reduce the number of tasks defined within the
the DSIQTSK task definition is valid. If incorrect, initialization file to a maximum of 64. Restart the
correct the name and restart the NetView program. DSIQTSK subtask.
DWO689I DUPLICATE TASK SPECIFIED, DWO692E TOO MANY RODMS WERE
task, AND IGNORED. DEFINED AT INITIALIZATION.
A task is defined more than once within the The initialization file contained more than 64 Resource
initialization file. Object Data Manager (RODM) definitions.
Message Variables
System action
task
The name of the task. The subtask ends.

Operator response DWO695E MORE THAN ONE RODM WAS
SPECIFIED FOR AUTOMATION IN
MEMBER, member.

Explanation
Reduce the number of RODMs defined within the
Multiple Resource Object Data Managers (RODMs)
initialization file to a maximum of 64. Restart the
were defined for automation.
DSIQTSK subtask.
Message Variables
DWO693E A PARAMETER SYNTAX ERROR
WAS FOUND IN MEMBER, member. member
The name of the initialization member.
Explanation
System action
The initialization file has a parameter syntax error.
Message Variables
member Operator response
The name of the initialization member.
System action
Correct the initialization member error and restart
DSIQTSK.
Operator response
Notify the system programmer. DWO696W THE TASK DEFINITION IN THE
INITIALIZATION FILE IS NOT
VALID.
Check the DSIPARM member and correct the ERROR. Explanation
Restart the subtask.
A command receiver was defined in the initialization
DWO694E A DUPLICATE PARAMETER WAS file without any TASK statements, or tasks were
SPECIFIED IN THE RODM defined in the initialization file without a CMDRCVR
DEFINITION IN MEMBER member. statement.

A Resource Object Data Manager (RODM) definition The DSIQTSK task does not support receiving
statement contained a duplicate parameter. commands.
Message Variables
Operator response
member
The name of the DSIPARM member where the Notify the system programmer.
error was detected.
System action Correct the initialization file and restart the DSIQTSK
The DSIQTSK subtask ends. subtask.
DWO697I starttype START OF THE RODM
Operator response CONTROL TASK IS IN PROGRESS.
Explanation
System programmer response This message shows how the subtask was started.
Check the DSIPARM member and correct the error. Message Variables
Restart the subtask.
starttype
Type of startup (COLD or WARM).

COLD DWO700I DSIQTSK IS CONNECTED TO THE
The first time DSIQTSK has been started. RODM rodm.
WARM
The DSIQTSK subtask was previously active. Explanation
The DSIQTSK subtask has connected to a specified
System action Resource Object Data Manager (RODM) successfully.
In either start type, all Resource Object Data Managers Message Variables
(RODMs) defined within the initialization file are
utilized. If the start was warm, then all parameters in rodm
the initialization deck are processed. If RODM existed The name of RODM.
on the previous initialization deck but it does not exist
in the new one, RODM is disconnected and is no longer System action
defined to the NetView program. All connections or
The subtask attempts to sign on to RODM notification
connect retries that existed the last time the NetView
queue.
program was running are maintained unless RODM is
no longer defined in the initialization deck. DWO701E COMMUNICATION IS LOST TO
RODM, rodm.
DWO698I THE INITIALIZATION OF THE
RODM CONTROL TASK HAS
COMPLETED. Explanation
The specified Resource Object Data Manager (RODM)
Explanation has ended. The NetView program has detected this
and tries to establish a new connection if a disconnect
The DSIQTSK subtask has completed initialization and
request is not outstanding. If the connect request fails,
is ready for work.
message DWO742E is issued and the NetView
program attempts to connect to RODM every minute.
System action
Message Variables
rodm
The name of RODM.
Operator response
You can now issue ORCNTL commands. System action
DWO699E THE CONNECTION TO RODM rodm Unless the operator has requested the DSIQTSK to
FAILED. ATTEMPTING RETRY. disconnect from the RODM, the DSIQTSK tries to
reconnect to RODM.
Explanation
The DSIQTSK subtask attempted to connect to the Operator response
specified Resource Object Data Manager (RODM) but If you have not requested the RODM disconnection,
failed. check the status of the specified RODM. If a failure
Message Variables occurred, attempt to reconnect to RODM.
rodm DWO702I A CHECKPOINT HAS BEEN ISSUED

The name of RODM. TO THE RODM rodm.
Message DWO742E is generated. The DSIQTSK retries The DSIQTSK subtask issued a successful checkpoint
in 60 seconds or when the operator requests a request to a specified Resource Object Data Manager
connection. This message is not generated again if the (RODM).
retry fails. Message Variables
rodm
Operator response
The name of RODM.
Check the status of the specified RODM to ensure that
it is operative. If the specified RODM has not been
started, start RODM.

Processing continues. The keyword specified is no longer a supported
keyword.
DWO703E THE CHECKPOINT REQUEST TO
RODM rodm HAS FAILED. In the case of the CNMSTYLE member, the specified
CHECKPOINTING IS DISABLED. keyword or value is ignored. NetView initialization will
continue. The statement or value should be removed.
Explanation In the case of DSIQTSK, the PASS keyword is no longer
The DSIQTSK subtask failed in an attempt to issue a supported on the REP statement and the APF keyword
checkpoint request to the specified Resource Object is no longer supported on the CMDRCVR statement in
Data Manager (RODM). the DSIQTSK initialization member (DSIQTSKI).
rodm keyword
The name of RODM. The name of the keyword that is no longer
supported and therefore it is ignored. If this
message is encountered during CNMSTYLE
System action member processing and a period (.) is the last
The DSIQTSK subtask does not retry a checkpoint character of the keyword in the message, then all
request. keywords that begin with this stem are no longer
supported.
Operator response
System action
To retry a checkpoint request, issue an ORCNTL CONN
request to the specified RODM. This reconnects RODM The keyword is ignored.
and drives the initialization of the notify queue and
subscriptions. Operator response
Remove the keyword from the initialization member of
System programmer response the task or from the CNMSTYLE member.
Message DWO742E is generated with function code In the case of DSIQTSK, the PASS keyword and the
1201. Compare the error codes with those provided by APF keyword must be removed from the DSIQTSKI
the RODM to verify the error. initialization member.
DWO704I DSIQTSK IS NOW DISCONNECTED DWO706E THE SIGNON TO RODM rodm
FROM RODM, rodm. CHECKPOINT NOTIFY FAILED.
CHECKPOINT IS DISABLED.
Explanation
The DSIQTSK subtask has disconnected from the Explanation
specified Resource Object Data Manager (RODM) The DSIQTSK task has failed to sign on to the
Message Variables Resource Object Data Manager (RODM) checkpoint
notification queue. The checkpoint procedure failed
rodm and was disabled.
The name of RODM.
Message Variables
System action rodm
Processing continues. The name of RODM.
If you want RODM to be reconnected, issue the The subtask continues with the checkpoint function of
ORCNTL CONN command. DSIQTSK disabled. Message DWO742E is also issued.
DWO705I THE KEYWORD keyword IS NO

LONGER SUPPORTED AND WILL
BE IGNORED.

Issue the ORCNTL CONN command to reconnect to The DSIQTSK subtask attempted to connect to the
RODM and retry the signon. The reconnection drives specified Resource Object Data Manager (RODM) that
the initialization of the notify queue and subscriptions. had already failed because of a password or password
phrase that was not valid.
Message DWO742E is generated with the function rodm
codes 1401, 1409, 1412, and 1504. Compare the The name of RODM.
error codes with those provided by RODM to find the
error.
System action
DWO707E THE RODM rodm IS NOT DEFINED. The request is rejected.

The Resource Object Data Manager (RODM) specified Notify the system programmer.
within the ORCNTL command was not found.
rodm Change the sign-on password or password phrase in
The name of RODM. the initialization file of the DSIQTSK subtask for this
RODM. This new password or password phrase is used
System action at the next start of the DSIQTSK subtask.
The processing of the request ends. DWO710I THE RODM rodm WILL
DISCONNECT WITHOUT A
Operator response CHECKPOINT.
Correct the RODM name specified in the ORCNTL

Explanation
request. If the RODM name is not known, issue the
ORCNTL LIST,REP command to have the valid RODMs An ORCNTL command was issued with the DISC
displayed. option. The Resource Object Data Manager (RODM) is
takes a checkpoint prior to disconnection.
DWO708E THE REQUEST TO DISCONNECT
RODM rodm HAS FAILED. Message Variables
rodm
Explanation The name of RODM.
An ORCNTL command was issued to disconnect the
Resource Object Data Manager (RODM) specified. The System action
specified RODM is not currently connected to the The DSIQTSK task disconnects the specified RODM
DSIQTSK task. without taking a checkpoint.
Message Variables
DWO711I THE RODM rodm WILL
rodm DISCONNECT WITH A
The name of RODM. CHECKPOINT.

Check the ORCNTL command and verify that the An ORCNTL command was issued with the DISC
specified RODM is correct. If the specified RODM was option. The Resource Object Data Manager (RODM)
incorrect, correct the name and issue the ORCNTL takes a checkpoint prior to disconnection.
command again. If the proper RODM was specified,
Message Variables
then verify the status of the requested RODM and
issue the command again, if required. rodm
The name of RODM.
DWO709E THE REQUEST TO CONNECT RODM
rodm IS REJECTED. PASSWORD IS
NOT VALID.

System action specified Resource Object Data Manager (RODM) that
is not connected.
The DSIQTSK task disconnects the specified RODM
while taking a checkpoint. Message Variables
DWO712E THE REQUEST TO CONNECT THE rodm
RODM rodm HAS FAILED. The name of RODM.
PASSWORD IS NOT VALID.
System action
Explanation The request is rejected.
A request was made to connect the specified Resource
Object Data Manager (RODM) to the subtask DSIQTSK. Operator response
The request is rejected because of a password or
password phrase that is not valid. Verify the RODM name, correct it if necessary, and
issue the command again, if required. Verify the
Message Variables current status of the requested RODM by issuing the
rodm ORCNTL LIST,REP command.
The name of RODM. DWO715E THE REQUEST TO CHECKPOINT
THE RODM rodm FAILED. RODM IS
System action CURRENTLY DISCONNECTING.
The DSIQTSK rejects the connect request.
Explanation
Operator response The ORCNTL command has been issued with the
CHKPT option. The request has been rejected because
Change the RODM password or password phrase using
the Resource Object Data Manager (RODM) specified is
the ORCNTL command. Then issue the connect
currently being disconnected.
request again.
Message Variables
System programmer response rodm
Change the signon password or password phrase in The name of RODM.
the initialization file of the DSIQTSK subtask for this
RODM. This new password or password phrase is used System action
at the next start of the DSIQTSK subtask.
The request is rejected.
DWO713I THE REQUEST TO CONNECT THE
RODM rodm HAS BEEN ISSUED. Operator response
Verify the RODM name, correct it if necessary, and
Explanation issue the command again, if required. Verify the
An ORCNTL CONN command has been issued for the current status of the requested RODM by issuing the
specified Resource Object Data Manager (RODM). ORCNTL LIST,REP command.
Message Variables DWO716E THE REQUEST TO CHECKPOINT
THE RODM rodm FAILED.
rodm
REQUEST WAS ALREADY
The name of RODM.
REQUESTED.
System action
Explanation
The DSIQTSK connection continues.
The ORCNTL command has been issued with the
DWO714E THE REQUEST TO CHECKPOINT CHKPT option. The request has been rejected because
THE RODM rodm FAILED. a previous checkpoint request was issued for
Resource Object Data Manager (RODM).
The ORCNTL command has been issued with the rodm
CHKPT option, but the checkpoint request is for a The name of the Resource Object Data Manager
(RODM).

The request is rejected. The request is rejected.

Verify the RODM name. Correct and issue the Check the command and try again.
command again, if necessary.
DWO720E THE REQUEST WAS REJECTED
DWO717E THE REQUEST TO CHECKPOINT DUE TO AN UNKNOWN SEND
THE RODM rodm FAILED. RODM IS ERROR TO DSIQTSK. PLEASE
CURRENTLY CHECKPOINTING. RETRY.
The Resource Object Data Manager (RODM) specified The ORCNTL command attempted to send a request to
in the ORCNTL checkpoint request is already taking a the subtask DSIQTSK and the command was
checkpoint. Therefore, the new checkpoint request is corrupted.
rejected.
rodm The request is rejected.

The name of RODM.
Operator response
System action Check the command and try again.
The request is rejected. DWO721E THE REQUEST FAILED; DSIQTSK
NOT ACTIVE.
Operator response
Verify the RODM name. Correct and issue the Explanation
command again, if required. The DSIQTSK subtask is not active and the command
DWO718I THE REQUEST TO CHECKPOINT request was rejected.
THE RODM rodm HAS BEEN
RECEIVED. System action
The command is rejected.
Explanation
The ORCNTL checkpoint request has been issued and Operator response
scheduled for the Resource Object Data Manager
Start the DSIQTSK subtask.
(RODM) specified.
DWO722E THE REQUEST TO CHECKPOINT
Message Variables
THE RODM rodm FAILED. THE
rodm CHECKPOINT HAS BEEN
The name of RODM. DISABLED.
DWO719E THE command REQUEST FAILED. A
PARAMETER ERROR WAS Explanation
DETECTED. The ORCNTL command that was issued with the
CHKPT option failed. The request has been rejected
Explanation because the checkpoint function for the specified
Resource Object Data Manager (RODM) has been
The DSIQTSK subtask has detected an error in a
disabled.
request block received from the issued command.
Message Variables
Message Variables
rodm
command
The name of RODM.

System action DWO725I THE AUTOMATION RODM IS NOW
rodm.
The checkpoint function is disabled because the
DSIQTSK subtask has failed to issue a checkpoint
request to rodm. Explanation
Operator response CHNG request. The automation Resource Object Data
Manager (RODM) has been changed to the specified
Issue the ORCNTL CONN command.
RODM.
DWO723E THE REQUEST TO CHECKPOINT
Message Variables
THE RODM rodm FAILED. DSIQTSK
IS NOT SIGNED ON TO RECEIVE rodm
THE CHECKPOINT NOTIFICATION. The name of RODM.

The ORCNTL command has been issued with the Processing continues.
CHKPT option but the request has been rejected
because the DSIQTSK has previously failed to sign on Operator response
to the Resource Object Data Manager (RODM)
checkpoint notification. Ensure that the new automation RODM is connected.
Verify this by issuing the ORCNTL LIST,REP command.
Message Variables
DWO726E THE AUTOMATION RODM IS
rodm ALREADY rodm. THE REQUEST IS
The name of RODM. REJECTED.

The NetView program stops processing the command. The ORCNTL command has been issued with the
CHNG request. The automation Resource Object Data
Operator response Manager (RODM) is already set to RODM specified in
Issue the ORCNTL CONN command. the request.
Message Variables
DWO724I THE PASSWORD FOR THE RODM
rodm HAS BEEN CHANGED. rodm
The name of RODM.
Explanation
System action
The ORCNTL command was issued with a PASS
request. The password or password phrase for the The request is rejected.
specified Resource Object Data Manager (RODM) was
changed. Operator response
Message Variables Ensure that the proper RODM was specified and issue
rodm the command again.
The name of RODM. DWO727I NO RODM IS NOW DEFINED AS
THE AUTOMATION RODM.
System action
The command was rejected. Explanation
System programmer response NOAOREP request. No Resource Object Data Manager
Update the DSIQTSK initialization file to reflect this (RODM) is available as the automation RODM.
new password or password phrase. Passwords or
password phrases changed using the ORCNTL System action
command are used only until the next restart of the Processing continues.
DSIQTSK subtask.

DWO728W THE CURRENT AUTOMATION System action
RODM rodm IS NOT CONNECTED. The request is retried on another task defined in
DSIQTSK.
Explanation
DWO731I A CHECKPOINT HAS BEEN
The Resource Object Data Manager (RODM) that is COMPLETED ON THE RODM rodm.
currently the automation RODM is not connected.
rodm The specified Resource Object Data Manager (RODM)
The name of RODM. took a checkpoint.
Message Variables
Operator response
rodm
If you want RODM connected, issue the ORCNTL The name of RODM.
command with the CONN option. This connects RODM
to the DSIQTSK subtask.
System action
DWO729E THERE IS AN ERROR READING The checkpoint is complete. Any RODM calls waiting
THE RODM rodm NOTIFICATION checkpoint notification are posted.
QUEUE. CHECKPOINTING HAS
BEEN DISABLED. DWO732I EXCESSIVE ERRORS WERE FOUND
IN THE TASK task. THE TASK IS
Explanation NO LONGER IN USE.
The DSIQTSK subtask attempted to query the

Explanation
Resource Object Data Manager (RODM) notification
queue and failed. Message DWO742E is generated to The dispatcher has encountered an error more than
provide error codes. once issuing a DSIMQS request to the specified task.
rodm task
The name of RODM. The name of the task.

The DSIQTSK subtask detected an error reading the The task is no longer used by DSIQTSK.
RODM notification queue. The checkpoint function for
this RODM is disabled. Operator response
Restart DSIQTSK.
Check the DWO742E message generated for return System programmer response
and reason codes for problem determination. After
correcting the problem, enable the checkpoint Check for task error messages in the DSILOG to
function by reconnecting to RODM. determine the problem.
DWO730E THERE IS AN ERROR ISSUING DWO733A NO NETVIEW TASKS ARE

WORK TO THE TASK task. AVAILABLE FOR WORK. ENTER
ATTEMPTING RETRY. “1” TO RETRY OR “2” TO
TERMINATE THE REQUEST.
Explanation
Explanation
The DSIQTSK received an error trying to issue work to
a task. The NetView program has no available tasks for work.
Message Variables
task

System action rodm
The name of the current RODM, or NOTFOUND if a
The command request to the NetView program is
current automation RODM has not been defined to
suspended. No work is issued to any NetView task
the NetView system.
until the request is acknowledged.
DWO736I RODM( rodm ) STATE( status )
Operator response CHKPT( checkpoint )
Issue the ORCNTL LIST,TASK command. This displays

Explanation
all of the tasks defined to the DSIQTSK subtask.
Activate at least one of the tasks defined as having the This is a response to an ORCNTL LIST,REP request.
current state of NOTFOUND. Enter 1 to have the The name, status, and checkpoint state of the
request issued. If there is no task available to activate, Resource Object Data Manager (RODM) are displayed.
enter 2 to end the request. The DSIQTSK subtask
Message Variables
ends. Update the initialization file with the name of an
available task and restart the DSIQTSK subtask. rodm
The name of RODM.
Note: If you enter 2 and commands were transmitted
from the Resource Object Data Manager (RODM) status
through the program-to-program interface, they are The status of RODM in relation to the DSIQTSK
processed when the DSIQTSK is returned. task:
DWO734E YOU MUST ENTER “1” or “2”. CONNECT

Connected to RODM.
Explanation CONNREQ
Connection has been requested.
The response you entered for DWO733A was not a 1
or 2. DISC
Disconnected from RODM.
System action DISCREQ
Disconnection has been requested.
The DSIQTSK subtask issues message DWO733A
again. checkpoint
The status of the checkpoint:
Operator response REQUEST
Checkpoint has been requested.
The message DWO733A is displayed. Enter a 1 to retry
or a 2 to end the request. INACTIVE
No checkpoint in progress.
DWO735I RCVR = status, AUTO REP= rodm ACTIVE
Checkpoint in progress.
Explanation
DISABLE
This is a response to an ORCNTL LIST request. The Checkpoint function from DSIQTSK has been
status of the Resource Object Data Manager (RODM) disabled because of checkpoint notification
receiver component and the name of the default request error from RODM. Issue an ORCNTL
automation RODM are displayed. CONN request to RODM in error. This
reconnects the RODM, which drives the
Message Variables
initialization of the notify queue and
status subscriptions.
The status of the dispatcher. The statuses are:
DWO737I TASK( task ) STATE( status )
Active
The dispatcher is currently ready for work.
Explanation
Inactive
The dispatcher is currently inactive. This is a response to ORCNTL LIST,TASK request. The
name and status of the task are displayed.
WTOR
The dispatcher is waiting for a response to Message Variables
message DWO733A. See message DWO733A task
for details. The name of the task.

status Operator response
The status of the task:
Message DWO740I follows. See this message to
INUSE determine which command was not issued and take
The task defined within the initialization file appropriate action.
has been found in the NetView system. It
currently is being used and work is being sent System programmer response
to it.
Use message DWO740I for diagnosis.
NOTFOUND
This is defined to DSIQTSK but not found in the DWO740I CODE = retcode, TEXT = text.
NetView system.
DISABLED Explanation
The dispatcher encountered errors trying to
A command sent to DSIQTSK cannot be issued (or
issue DSIMQS requests to this task and has
assisted). DWO740I follows another message,
failed.
providing additional detail.
The task is no longer used by the dispatcher. retcode

Reason code for command failure:
Operator response 1
Request message has no text.
Recycle the NetView program to restart the task.
2
DWO738I THE END OF DISPLAY REQUEST. Parse of message failed.
3
Explanation Insufficient parameters in message.
This indicates when the response to the ORCNTL LIST 4
request is complete. Delimiter in message is not valid.
DWO739E UNABLE TO ISSUE COMMAND 5
FROM SENDER sender TO TASK Parameter is not valid.
task, SENDER TOKEN = token. 6
Assisted command, no assist operator.
Explanation 7
A program requested that a command (or assist Operator or autotask specified is not valid.
message) be issued to a specific task only. The 8
request failed because the task specified was not valid Attempt to issue command failed.
or not active.
text
Message Variables The text of the command that was not issued.
sender
The sender name provided to the program-to- System action
program interface by the sending program. The Resource Object Data Manager (RODM) stops
task processing the request.
The name of the task where the command was to
be executed. System programmer response
token Determine the problem and correct it. The problem
The token sent by the sender in the command might have originated in the program that sent the
buffer. If no sender token is sent, the value command.
displayed is N/A.
DWO741E UNABLE TO ISSUE COMMAND TO
System action TASK task. DSIMQS RC = retcode.
The request is not processed because the task

requested was not found or not active.

Explanation DWO744I DSIQTSK DOES NOT HAVE ANY
RODMs DEFINED TO IT.
A program requested that a command be assisted or
issued to a specific task only. The request failed on the
DSIMQS call because of the reasons indicated by the Explanation
MQS return code. An ORCNTL LIST,REP command was issued and no
Message Variables Resource Object Data Managers (RODMs) have been
defined in the DSIQTSKI initialization member in
task DSIPARM.
The name of the task where the command was to
be queued. DWO745I DSIQTSK DOES NOT HAVE ANY
AUTOTASKS DEFINED TO IT.
retcode
The DSIMQS return code.
Explanation
System action An ORCNTL LIST,TASK command was issued and no
tasks have been defined in the ORAC initialization
The request is canceled because the DSIMQS call
deck.
failed.
DWO746I THE process FAILED. PROGRAM-
System programmer response TO-PROGRAM INTERFACE
REQUEST TYPE IS request_type,
Look up the DSIMQS return code and determine the RETURN CODE IS retcode.
cause of the failure. Message DWO740I is also issued
in response to this message. See message DWO740I
for further details. Explanation
One of the following processes failed:
DWO742E RODM rodm ERROR, FUNCTION =
func, RETURN CODE = retcode, • The DSIQTSK task attempted to initialize the
REASON CODE = reason. program-to-program interface (PPI) receiver and
failed after a specified number of retries.
Explanation • The Z NetView Enterprise Management Agent
The Resource Object Data Manager (RODM) is encountered a failure with its PPI communication
returning error information in response to a DSIQTSK layer.
request. Message Variables
Message Variables process
rodm The name of the process that failed. Possible
The name of RODM. values for process are:
func • PPI initialization

The RODM function ID. • PPI receive
retcode • QRYPPI Query program-to-program interface
The return code from RODM.
• QRYRCVR Query PPI receiver
reason
• INITRCVR Initialize PPI receiver
The reason code from RODM.
• DELRCVR Delete a PPI receiver
System action • RECVBUFR Receive buffer
The error message is generated for all RODM API call request_type
failures in which the error codes are unknown. The PPI request that failed.
retcode
System programmer response The return code returned from the request type.
Use this message for problem analysis to determine
why a DSIQTSK call is failing. After correcting the System action
problem, reconnect RODM to force the DSIQTSK to The request is ended.
sign on to the notification queue and to query it again.

Operator response OPERAND OF THE cmd COMMAND,
IS NOT VALID
Start the NetView subsystem interface with the PPI
option enabled or notify the system programmer that
there is a problem with the PPI subsystem. Explanation
The error command does not exist as a command list
System programmer response or a command processor.
Determine why the specified process failed. Check the Message Variables
request type and the return code. See the IBM Z
errcmd
NetView Application Programmer's Guide for more
The command or command list which the operator
information.
is not authorized to use.
DWO747I AN INCORRECTLY FORMATTED cmd
BUFFER WAS RECEIVED FROM The command that was issued specifying errcmd
THE PROGRAM-TO-PROGRAM as the ERROR operand.
INTERFACE, AND WAS REJECTED.
System action
Explanation
The cmd command ends.
A buffer was sent through the program-to-program
interface subsystem but the data was not in the DWO750I DSIQTSK IS UNABLE TO ISSUE
correct format. WORK FROM THE senderid. THERE
ARE NO AUTOTASKS AVAILABLE.
DWO748E THE COMMAND OR COMMAND
LIST, errcmd, SPECIFIED ON THE
Explanation
ERROR OPERAND OF THE cmd
COMMAND, IS NOT WITHIN THE Work was received from the specified sending
OPERATOR AUTHORITY. application, but none of the autotasks listed in the
initialization file are available to receive the work. This
Explanation message might be accompanied by message
DWO733A if the sending application is RODM.
The operator is not authorized to issue the command.
Message Variables
Message Variables
senderid
errcmd The name of the sending application.
The command or command list which the operator
is not authorized to use.
System action
cmd
The command that was issued specifying errcmd Any work that needs to be executed on the autotask by
as the ERROR operand. DSIQTSK is ignored.
The cmd command is ended. Issue the ORCNTL LIST,TASK command. This displays
all of the tasks defined to the DSIQTSK subtask.
Activate at least one of the tasks defined as having the
Operator response current state of NOTFOUND. Enter 1 to have the
If you need to enter the command, notify the system request issued. If there is no task available to activate,
programmer. enter 2 to end the request. The DSIQTSK subtask
ends. Update the initialization file with the name of an
System programmer response available task and restart the DSIQTSK subtask.
Evaluate the operator's requirements and add System programmer response

appropriate security access if required.
Ensure that one of the autotasks listed in the
DWO749E THE NETVIEW COMMAND OR initialization file is executing properly.
COMMAND LIST, errcmd,
SPECIFIED ON THE ERROR DWO751I DSIQTSK IS UNABLE TO CONNECT
TO THE RODM rodm; THERE ARE
NO AUTOTASKS AVAILABLE TO

PROCESS THE INITIAL Operator response
COMMAND.
Explanation
A connection was made to the specified Resource
Ensure that the API modules exist in the correct load
Object Data Manager (RODM) that had an initial
library.
command associated with it. DSIQTSK attempted to
connect to RODM every specified number of seconds. DWO753I task: WARNING, UNABLE TO
The specified number is a NetView constant. DEALLOCATE RESOURCES FOR
THIS TERMINATING TASK - TASK
Message Variables
TERMINATION CONTINUES.
rodm
The name of RODM. Explanation
Task termination has determined that DSIZMQEP was
System action
unable to complete processing of the task's message
The request is ended. queues. An attempt to free the messages can cause
unpredictable results.
Start one of the autotasks listed in the initialization task
deck and enter R to retry. If the task is a data services task, this is the LU
DWO752E A LOAD FOR apimodule FAILED. name of the task. If the task is an operator station
task, this is the operator ID.
Explanation
System action
A load of one of the following services has failed:
Task termination continues, but the task's message
• One of the Application Programming Interface (API) queues are not freed.
modules, such as EKGUAPI.
• The Z NetView Enterprise Management Agent Operator response
command service module.
Message Variables
apimodule System programmer response
The name of the API module or a description of the This message is preceded by message DSI528I,
API module. A description of RODM API DSI529I or a task abend. Determine the cause of the
INTERFACE refers to the EKGUAPI module. message or abend. Restart the NetView program to
reclaim the lost resources.
System action
DWO754I THE CHECKPOINT REQUEST FOR
The operation associated with the API will fail. If this RODM rodm WAS CANCELLED DUE
message is issued during NetView initialization, TO OPERATOR INTERVENTION
NetView initialization will continue. These are possible
consequences of this failure:
Explanation
• If the EKGUAPI module was not loaded, then calls
An operator has canceled the checkpoint before it
related to the Resource Object Data Manager
completed.
(RODM) will fail with a return code of 8 and the
message DWO721E is issued. Message Variables
• If the EZBCTAPI, EZBNMCTF, or EZBPTFM4 module rodm
was not loaded, the FMTPACKT pipe stage will fail. The name of RODM.
• If the CNMPPISR module was not loaded, make sure DWO755W The keyword kywd is deprecated.
that the NetView CNMLINK library is accessible to
LLA or a library that is searched at program
initialization of the Z NetView Enterprise
Management Agent.

Explanation category will cause the new DEFFOCPT definition to be
used when DSI6DST is restarted.
The keyword is still supported for migration purposes,
but might have reduced function. DWO761W BACKUP FOCAL POINT fpname
PREVIOUSLY DEFINED FOR
Message Variables
CATEGORY fpcat. FIRST
kywd OCCURRENCE USED.
The name of the keyword. If this message is
encountered during the CNMSTYLE member Explanation
processing and a period (.) is the last character of
the keyword in the message, then all keywords A backup focal point name has been defined more
that begin with this stem are deprecated. than once for a specified category. The subsequent
definitions are ignored.
Processing continues. fpname
The name of the remote node that is a backup
System programmer response focal point for the specified category
See the IBM Z NetView Administration Reference for fpcat

details about the level of support remaining for this The category for which the information is being
keyword. Try to remove any dependency on the given
keyword.
System action
DWO760W NO PRIMARY FOCAL POINT
DEFINED FOR CATEGORY fpcat. Processing continues. The NetView program uses the
DEFFOCPT STATEMENTS FOR first definition of the backup focal point. Subsequent
THIS CATEGORY ARE IGNORED. definitions are ignored.
A primary focal point has not been defined with a If the error occurred on a FOCALPT ACQUIRE
DEFFOCPT statement for this category, but DEFFOCPT command, verify that you entered the backup focal
statements defining backup focal points for this point name correctly. If incorrect, enter the FOCALPT
category have been detected. The definition of a ACQUIRE command again with the correct backup
primary focal point for each category is mandatory. All focal point name and the OVERRIDE keyword. If this
DEFFOCPT statements pertaining to this category are message is not the result of issuing a FOCALPT
ignored. ACQUIRE command, notify the system programmer.
Message Variables
fpcat
Remove the duplicate definition of the backup focal
The category for which the focal point information
point for this category. Any change in the DEFFOCPT
is being given.
definition for a category will cause the new DEFFOCPT
definition to be used when DSI6DST is restarted.
System action
DWO762W MULTIPLE PRIMARY FOCAL
Processing continues. DEFFOCPT statements for this
POINTS DEFINED FOR CATEGORY
category will not be used.
fpcat. FOCAL POINT fpname
ACCEPTED.
Operator response
In DEFFOCPT statements in the DSI6INIT initialization
System programmer response member, two different primary focal point names have
Either remove the DEFFOCPT statements for this been defined for the same category. The NetView
category if no longer required or add a DEFFOCPT program uses the last definition it reads.
statement defining the primary focal point for this Message Variables
category. Any change in the DEFFOCPT definition for a

fpcat FOCALPT ACQUIRE command again with a maximum
The category of data for which the focal point of 8 backup focal points specified.
information is being given.
If this message is not the result of issuing a FOCALPT
fpname ACQUIRE command, notify the system programmer.
The name of the remote node that is a primary
focal point for the specified type. System programmer response
System action Remove the extra DEFFOCPT BACKUP statements.

Any change in the DEFFOCPT definition for a category
Processing continues. The NetView program uses the will cause the new DEFFOCPT definitions to be used
last definition of a primary focal point. Previous when DSI6DST is restarted.
definitions are ignored.
DWO764W RESTORE OF ALL CURRENT FOCAL
POINTS UNSUCCESSFUL.
DEFFOCPT STATEMENTS USED
Remove the duplicate DEFFOCPT statements. You can WHEN DETAILS NOT RESTORED.
only define one primary focal point per category. Any
change in the DEFFOCPT definition for a category will Explanation
cause the new DEFFOCPT definition to be used when
DSI6DST is restarted. A failure was detected when restoring the saved focal
points from the save/restore database. Some focal
DWO763W MAXIMUM NUMBER OF BACKUP point information might have been returned and will
FOCAL POINTS DEFINED FOR be used. If no information is returned from the
CATEGORY fpcat. BACKUP FOCAL database, the DEFFOCPT statements are used.
POINT fpname IGNORED.
System action
Explanation
More than 8 backup focal points have been defined for
this category. The NetView program ignores the Operator response
extraneous backup focal points.
Issue the FOCALPT QUERY command to determine
Message Variables what information from the save/restore database was
fpcat returned.
The category of data for which the focal point
information is being given. System programmer response
fpname Use the save/restore error messages that appear at
The name of the remote backup node that has the authorized receiver console to determine the
been ignored. cause of the error.
System action DWO765W QUALIFIED BACKUP FOCAL POINT

fpname1 DEFINED FOR CATEGORY
Processing continues. The first 8 backup focal points fpcat. UNQUALIFIED BACKUP
defined are used. FOCAL POINT fpname2 IGNORED.

If the error occurred on a FOCALPT ACQUIRE Both a qualified and an unqualified network name
ADDBKUP command, enter the FOCALPT ACQUIRE have been supplied for a category with the same
command again: network addressable unit (NAU). If a qualified network
• Without the ADDBKUP keyword name is supplied for a category, MS_CAPS does not
support the inclusion of an unqualified network name
• With the BACKLIST operand specifying the complete for the same NAU because it cannot predict how the
backup list netid will be resolved by VTAM and duplicates are not
The FOCALPT ACQUIRE command will replace the valid.
existing list with the backup list supplied. Message Variables
If the error occurred on a FOCALPT ACQUIRE
command without the ADDBKUP keyword, enter the

fpname1 point is removed from the backup focal point list for
The qualified network name. the category. Although the backup focal point might
fpcat have been fully qualified, the primary focal point is
The category for which the focal points are being considered to be of higher priority than the backup
specified. focal point; thus the primary focal point is kept.
fpname2 Message Variables
The unqualified network name. fpname1
The primary focal point name.
System action fpcat
Processing continues. The qualified network name is The category for which the focal points are being
kept in the backup focal point list for the category specified.
selected. fpname2
The backup focal point name removed.
Operator response
Check that the qualified network name entered is System action
correct. If not, issue a FOCALPT DROP command for Processing continues. The primary focal point is kept
the qualified network name to remove the added name and the backup focal point ignored.
from the category's backup list. Issue the FOCALPT
ACQUIRE command again, adding the unqualified
Operator response
network name removed by the first FOCALPT
ACQUIRE command and the corrected new backup Check that the primary focal point name entered is
focal point name. correct. Issue the FOCALPT ACQUIRE command again,
adding the backup focal point removed by the first
System programmer response FOCALPT ACQUIRE command and the corrected new
primary focal point name.
Check that the focal point names defined in the
DEFFOCPT statements are correct.
DWO766I NO DEFFOCPT FOCAL POINTS Check that the focal point names defined in the
DEFINED FOR THIS CATEGORY. DEFFOCPT statements are correct.
Explanation DWO768I THE FOLLOWING BACKUP FOCAL

POINT(S) HAS BEEN DROPPED:
A FOCALPT ACQUIRE command with the DEFFOCPT
parameter specified that the focal points defined in the
Explanation
DSI6DST DSI6INIT initialization member be restored
for a specific category. However, no focal points were This message precedes the display of the dropped
defined in this member for the category requested. backup focal points.
This message follows a DWO051I message that is
System action displayed upon successful completion of a FOCALPT
The command is not processed. DROP command. You cannot use this message for
automation because it is a message within a multiple-
line message block.
Operator response
DWO769I fpname1 fpname2 fpname3
Enter the command again with focal point names or
corrected category name. fpname4
DWO767W PRIMARY FOCAL POINT fpname1 Explanation

DEFINED FOR CATEGORY fpcat.
BACKUP FOCAL POINT fpname2 This message displays the names of backup focal
IGNORED. points that have been dropped.
Explanation displayed upon successful execution of a FOCALPT
DROP command. You cannot use this message for
A primary and backup focal point have the same
network addressable unit (NAU). The backup focal
line message block.

fpname1 MS_CAPS has detected that the focal points for this
The backup focal point name. category are in a loop. The active remote focal point
fpname2 for this category is a backup and its name has been
The backup focal point name. removed from the category's backup list to ensure that
it is not able to create the loop again. This message
fpname3 appears only in the NetView log.
The backup focal point name.
Message Variables
fpname4
The backup focal point name. fpname
The name of the remote backup focal point that
DWO770W A LOOP HAS BEEN DETECTED FOR has been dropped.
CATEGORY fpcat. node1 HAS
ISSUED A REVOKE TO node2 TO fpcat
BREAK THE LOOP. The category that the loop has been detected for.
MS_CAPS has detected that the focal points for this The focal point name is removed from the backup
category are in a loop and has issued a revocation to focal point list for the category.
an active remote focal point to break the loop. This
message is sent to the authorized receiver and System programmer response
appears in the NetView log.
Ensure that the action taken by MS_CAPS is correct.
Message Variables Check that the backup focal point is not required for
the category. If it is required, issue a FOCALPT
fpcat
ACQUIRE or FOCALPT CHANGE command to include
The category that the loop has been detected.
the backup focal point in the category's backup focal
node1 point list. Ensure that the addition of the backup focal
The node that detected the existence of a loop. point will not create the loop again.
node2
DWO772I A LOOP HAS BEEN DETECTED FOR
The node that has been issued a revocation, to
CATEGORY fpcat. THE NODES
break the loop.
INVOLVED IN THE LOOP ARE:
System action
Explanation
The entry point drops the focal point, thus ending the
This message precedes the display of the nodes
loop.
involved in the loop. This message appears only in the
NetView log.
Operator response
Message Variables
Notify the system programmer of the detection of the
loop. fpcat
The category that the loop has been detected for.
System programmer response DWO773I node1 node2 node3 node4 node5
node6 node7 node8 node9
Messages DWO772I and DWO773I in the NetView log
display all nodes that were detected in the loop. Check
that MS_CAPS dropped the right focal point. If not, Explanation
issue a FOCALPT CHANGE, ACQUIRE or DROP This message lists all the nodes involved in a loop. It
command to end the loop and to reacquire the focal might be repeated multiple times to list all nodes
point that MS_CAPS dropped. involved in the loop. This diagnostic message can be
DWO771W BACKUP FOCAL POINT fpname used to determine how a loop was created for the
HAS BEEN DROPPED FROM THE category. This message appears only in the NetView
BACKUP LIST FOR CATEGORY log.
fpcat DUE TO THE DETECTION OF Message Variables
A LOOP.

node1 applname
The name of a node within the loop. Node1 was The name of the application that has previously
forwarding data to node2. registered, or is now registering.
node2
The name of a node within the loop. Node2 was Operator response
forwarding data to node3. If this message appears at DSI6DST startup time,
node3 report the message to the system programmer. Do not
The name of a node within the loop. Node3 was try to register applications as focal points while you
forwarding data to node4. are operating on an end node.
node4
The name of a node within the loop. Node4 was System programmer response
forwarding data to node5.
Modify any startup procedures on this end node that
node5 try to register applications as focal points. Any change
The name of a node within the loop. Node5 was in the DEFFOCPT definition for a category will cause
forwarding data to node6. the new DEFFOCPT definition to be used when
node6 DSI6DST is restarted.
The name of a node within the loop. Node6 was DWO775I SAVE/RESTORE TASK DSISVRT IS
forwarding data to node7. INACTIVE. DSI6DST SAVE/
node7 RESTORE PROCESSING WILL
The name of a node within the loop. Node7 was CONTINUE.
node8 Explanation
The name of a node within the loop. Node8 was
The NetView program will use data from its internal
table to restore the focal points that existed prior to
node9 stopping DSI6DST. The NetView program cannot
The name of a node within the loop. Node9 was access the data in the save/restore database because
forwarding data to node1 of the next message. the save/restore task is not active.

Use this information to determine how your focal point Modify the startup procedures on this node to have the
nodes created the loop. save/restore task start prior to starting DSI6DST.
DWO774I END NODE DOES NOT SUPPORT DWO776I SAVE/RESTORE TASK DSISVRT IS
applname AS A FOCAL POINT. INACTIVE. USING DEFFOCPT
DEFINITIONS.
Explanation
An application was registered or is being registered as Explanation
a focal point on an end node. Applications on end The NetView program will use the DEFFOCPT
nodes do not receive focal point services. If the statements in the DSI6INIT initialization member to
application registered as being interested in a establish focal points. Previous focal point states are
category, it will still be served as an interested unknown:
application, but no applications will be notified by the
NetView program that this application is available as a • The NetView internal table of focal points does not
focal point. exist.
• The NetView program's attempt to access data in the
save/restore database failed because the save/
can appear at the start of DSI6DST to inform the
restore task was not active.
authorized receiver that applications registered prior
to the start of DSI6DST will not be treated as focal
points. It will also be issued after DSI6DST is started System programmer response
whenever an application tries to register as a focal Modify the startup procedures on this node to have the
point on an end node. save/restore task start prior to starting DSI6DST.
Message Variables

DWO777W TARGNET PARAMETER IGNORED. fpname
FULLY QUALIFIED NETWORK The current focal point name.
NAME PROVIDED. type
The type of focal point, PRIMARY, DOMAIN, or
Explanation BACKUP(n), where (n) indicates which node in the
backup list is the current focal point.
A FOCALPT DISPSOC or FOCALPT DELETE command
was issued with both the TARGNET parameter and a
fully qualified network name specified by the TARGET System action
parameter. Processing continues.
DWO781I NO BACKUPS MATCH SUPPLIED
System action
LIST
The TARGNET parameter is ignored and the command
is processed using the fully qualified network name Explanation
specified by the TARGET parameter.
There are currently no backup focal points which
DWO779W NO APPLICATIONS INTERESTED match the backup list supplied on the FOCALPT DROP
IN THAT CATEGORY. command.

A FOCALPT ACQUIRE command has been issued Processing continues.
specifying a category in which no application has
registered an interest. This message follows message
Operator response
DWO052I.
Enter FOCALPT DROP command again with valid
System action backup focal point names.
The command is not processed. DWO782I FOCAL POINT AUTHORIZATION

FOR CATEGORY fpcat HAS BEEN
Operator response REVOKED BY DISTRIBUTED NODE
epname DUE TO LOOP
Ensure that the category specified on the FOCALPT DETECTION.
ACQUIRE command was correct. Do one of the
following: Explanation
• If the incorrect category was specified, enter the This node has been revoked as a focal point because a
command again with the correct category specified. loop has been detected. This message appears only in
• If the correct category was specified, use the the NetView log.
REGISTER command to define an application with an
Message Variables
interest in the category before entering the FOCALPT
ACQUIRE command again. fpcat
The category that the loop has been detected for.
DWO780I THE CURRENT REMOTE FOCAL
POINT IS fpname. TYPE : type epname
The node that detected the existence of a loop.
Explanation
System action
This message displays details of the current remote
focal point. MS-CAPS drops the focal point, thus ending the loop.

displayed upon successful execution of a FOCALPT
DROP command when the focal points dropped do not Messages DWO772I and DWO773I in the NetView log
include the current focal point. You cannot use this of the Distributed Node (Entry Point) display all nodes
message for automation because it is a message that were detected in the loop. Check that MS-CAPS
within a multiple-line message block. dropped the right focal point to end the loop. If not,
issue a FOCALPT CHANGE, ACQUIRE or DROP
Message Variables

command to end the loop and to reacquire the focal automation because it is a message within a multiple-
point that was dropped. line message block.
DWO783W command subcommand NOT Message Variables
ALLOWED FROM AN END NODE
fpname
The name of the pending remote focal point.
Explanation
type
The command command subcommand is not The type of focal point, PRIMARY, DOMAIN, or
processed when entered from an end node. BACKUP(n), where (n) indicates which node in the
backup list is the pending focal point.
Message Variables
DWO792I PRIMARY: fpname
command
Explanation
subcommand
The name of the subcommand. This message displays the primary remote focal point.
This message follows a DWO051I or DWO170I
System action message that is displayed upon successful execution
The command command subcommand is not of a FOCALPT QUERY or FOCALPT ACQUIRE
processed. command. You cannot use this message for
line message block.
Operator response
Message Variables
Do not enter the command command from an end
node. fpname
The name of the primary remote focal point.
DWO790I CURRENT: fpname TYPE: type
DWO793I BACKUP LIST: indicator
Explanation
Explanation
This message displays the current remote focal point
and its type. This message precedes the display of the backup focal
point list.
This message follows a DWO051I or DWO170I
message that is displayed upon successful execution This message follows a DWO051I or DWO170I
of a FOCALPT QUERY or FOCALPT ACQUIRE message that is displayed upon successful execution
command. You cannot use this message for of a FOCALPT QUERY or FOCALPT ACQUIRE
automation because it is a message within a multiple- command. You cannot use this message for
line message block. automation because it is a message within a multiple-
line message block.
Message Variables
Message Variables
fpname
The name of the current remote focal point. indicator
type --NONE-- or blank.
The type of focal point, PRIMARY, DOMAIN, or DWO794I number1) fpname1 number2)
BACKUP(n), where (n) indicates which node in the fpname2 number3) fpname3
backup list is the current focal point.
DWO791I PENDING: fpname TYPE: type Explanation
This message displays up to three focal point names
Explanation from the category's backup focal point list.
This message displays the pending remote focal point This message follows a DWO051I or DWO170I
and its type. message that is displayed upon successful execution
This message follows a DWO051I or DWO170I of a FOCALPT QUERY and FOCALPT ACQUIRE
message that is displayed upon successful execution command. You cannot use this message for
of a FOCALPT QUERY or FOCALPT ACQUIRE automation because it is a message within a multiple-
command. You cannot use this message for line message block.

Message Variables This message follows a DWO051I message that is
displayed upon successful execution of a FOCALPT
number1
ACQUIRE command. You cannot use this message for
The sequence number of the focal point within the
backup list.
line message block.
fpname1
The backup focal point name. DWO800I AUTOMATION TABLE type DETAIL
REPORT BY taskname
number2
backup list. Explanation
fpname2 A detailed usage report of automation table

The backup focal point name. statements is displayed. The report contains statistical
information given in tabular form. This report is used
number3
to assist in the tuning of automation table statements
for better automation performance.
backup list.
fpname3 Message Variables
The backup focal point name. type
MSG or MSU.
DWO795I DOMAIN: fpname
taskname
Explanation The NetView task that issued the command.
A domain focal point is defined for the category. The System action
FOCALPT QUERY request was issued from an APPN-
served end node. The message lists the domain focal Processing continues.
point's name if one exists.
This message follows a DWO170I message that is System programmer response
displayed upon successful execution of a FOCALPT Review the information you have requested.
QUERY or FOCALPT ACQUIRE command. You cannot
use this message for automation because it is a DWO801I AUTOMATION TABLE type
message within a multiple-line message block. SUMMARY REPORT BY taskname
Message Variables
Explanation
fpname
A summary usage report of automation table
The domain focal point name.
statements is displayed. The report contains statistical
DWO796I NEW REMOTE FOCAL POINT information given in tabular form. This report is used
DETAILS ARE AS FOLLOWS: to assist in the tuning of automation table statements
for better automation performance.
This message precedes the display of the new backup type
focal point list. MSG or MSU.
This message follows a DWO051I message that is taskname
displayed upon successful execution of a FOCALPT The NetView task that issued the command.
ACQUIRE command. You cannot use this message for
automation because it is a message within a multiple- System action
line message block.
DWO797I OLD REMOTE FOCAL POINT
DETAILS ARE AS FOLLOWS: System programmer response
Explanation Review the information you have requested.
This message precedes the display of the old backup DWO802I AUTOMATION TABLE COUNTERS
focal point list. RESET BY taskname AT mm/dd/yy
hh:mm:ss

The RESET option has reset the automation table This message indicates a file containing automation
usage counters to zero in the active automation table. table usage statistics for the current automation table
Resetting the usage counters to zero provides a known was successfully generated.
starting point to evaluate automation statement
Message Variables
usage.
filename
Message Variables
The member or file name of the generated file.
taskname
The NetView task that issued the command. System action
mm/dd/yy hh:mm:ss Processing continues.
The current date and time. The date and time
formats depend on the TRANSMSG member, when DWO829I AUTOMATION TABLE REPORT
in effect, and on the date and time operands of the 'filename' UNSUCCESSFULLY
DEFAULTS and OVERRIDE commands. GENERATED

Processing continues. This message indicates a file containing automation
table usage statistics for the current automation table
DWO826E AUTOMATION TABLE USAGE was not successfully generated. A prior message is
REPORT HALTED DUE TO SEVERE issued describing the failure. A failure can be caused
ERROR. by any of the following:
Explanation • Specifying a report destination member of the

AUTOCNT command that already exists. You can
The process was halted because of a severe I/O error. reuse the name if you specify the REPLACE option on
This error can be a result of: the AUTOCNT command.
• Attempting to write records to a member or file for • Specifying a report destination member that is
which there is no write access already in use.
• Filling the data set or the disk to which the records • An I/O error.
are being written • A system macro failure.
• Attempting to replace an existing member or file of
Message Variables
the wrong type, or that is missing a required key field
filename
System action The member or file name of the file that was not
successfully generated.
The process ends.
System action
Operator response
Processing ends.
Operator response
Locate the prior message that indicates the failure,
Check the system log for additional messages that correct the problem, and issue the AUTOCNT
might better describe the problem. Determine the command again. If you are unable to correct the
cause of the error, correct the problem in your DSILIST problem, notify the system programmer.
data set, and issue the AUTOCNT command again.
DWO828I AUTOMATION TABLE REPORT System programmer response
'filename' SUCCESSFULLY Locate the prior message that indicates the failure and
GENERATED correct the problem.
DWO830I OPERATOR operid IS DELETED
FROM THE GROUP OF VALID
NETVIEW OPERATORS

You see this message: The RMTCMD security table has been deleted by
stopping the DSIUDST task or by issuing the REFRESH
• After a REFRESH OPERS command is processed and
command.
the specified operator ID is removed from DSIOPF.
• If you have your operators defined through an SAF Message Variables
product and you used the REFRESH command to secclass
change your operators to be defined in NetView Security class (RMTSEC).
through DSIOPF and the specified ID is not in
DSIOPF. DWO833I CURRENTLY DEFINED OPERATOR
operid IS NOT FOUND IN DSIOPF
Message Variables
operid Explanation
The NetView operator ID.
You see this message after an operator has issued a
REFRESH OPERS,TEST command. The specified
System action operator ID was not found in DSIOPF, but remains
operid is no longer a valid NetView operator ID and available until a REFRESH OPERS command is issued.
cannot log on to the NetView system. Message Variables
operid
If the definition for operid was accidentally deleted,
update DSIOPF to include a definition for operid and System action
issue the REFRESH OPERS command.
The operator ID is still defined to the NetView
DWO831I OPERATOR operid IS ADDED TO program. This message alerts you that, if you issue a
THE GROUP OF VALID NETVIEW REFRESH OPERS command, the specified operator ID
OPERATORS will no longer be a valid NetView operator ID.

You see this message after a REFRESH OPERS If the definition for operid was accidentally deleted,
command is processed and DSIOPF has had an update DSIOPF to contain the definition for operid and
operator added. issue the REFRESH OPERS,TEST command again.
Message Variables DWO834I NEW OPERATOR DEFINITION FOR
operid operid IS FOUND IN DSIOPF
Explanation
System action You see this message after an operator has issued a
operid is a valid ID and can log on to the NetView REFRESH OPERS,TEST command. The specified
program. operator ID was found in DSIOPF, but remains
unavailable until a REFRESH OPERS command is
issued.
Operator response
Message Variables
An operator can use operid to log on to the NetView
program. operid
System action
If the definition for operid was accidentally added,
update DSIOPF to remove the definition for operid and The operator ID is not defined to NetView program.
issue the REFRESH OPERS command again. This message alerts you that, if you issue a REFRESH
OPERS command, the specified operator ID will be
DWO832I secclass SECURITY TABLE HAS defined as a valid NetView operator ID.
BEEN DELETED

If the definition for operid was accidentally added, operid
update DSIOPF to remove the definition for operid and The NetView operator ID queried.
issue the REFRESH OPERS,TEST command again.
DWO838I operid IS DEFINED TO NETVIEW
DWO835I TEST OF REFRESH OPERS BUT IS NOT LOGGED ON
COMMAND SUCCESSFULLY
COMPLETED Explanation
You see this message after an operator issues a QOS
Explanation
command. The operator specified is a valid NetView
You see this message after a REFRESH OPERS,TEST operator, but is not currently logged on.
command is processed and has finished successfully.
Message Variables
DWO836E TASK NAME task IS ALREADY operid
DEFINED TO THE NETVIEW The NetView operator ID queried.
PROGRAM AS AN tasktype
DWO839I operid IS NOT DEFINED TO
Explanation NETVIEW BUT IS LOGGED ON
One of the following errors has occurred:

Explanation
• A START TASK command was issued to dynamically
This message is displayed after an operator issues a
start a task that had the same name as an existing
QOS command. The operator is not a valid NetView
task of a different type.
operator, but is currently logged on. This message is
• A REFRESH OPERS command was issued with an displayed
operator definition in DSIOPF having the same name
as an OPT/DST. • When an operator who is in session with the NetView
program is deleted from DSIOPF and a REFRESH
Message Variables OPERS command is issued,
task • If the current value for OPERSEC is SAFDEF and the
The task name. operator is either not defined or not defined to the
tasktype APPL class for this domain.
The type of task that is already defined: OST, PPT, • The operator is a virtual OST (VOST) created by an
MNT, or OPT (including DSTs). ATTACH command.
After logoff, the deleted operator will not be allowed
System action access to the NetView Program.
Processing continues without the taskname specified. Message Variables
For a START TASK, the task is not started. For a
REFRESH OPERS, the operator is not defined to the operid
NetView program. The NetView operator ID queried
Notify the system programmer. NetView allows the operator session to continue in a
limited capacity. If span of control is used to limit
operator access to resources, the operator ID will no
longer have access to any span and, therefore, to any
Correct the definition or keyword in error and issue the resources using the DISPLAY, MODIFY, and VARY
command again. commands. If the current value of OPERSEC is
SAFDEF, the operator can continue to use only those
DWO837I operid IS DEFINED AND LOGGED spans that are currently active.
ON TO NETVIEW
If the operator is a VOST, the VOST will continue to run
Explanation normally.
You see this message after an operator has issued a

QOS command. The operator specified is a valid
NetView operator and is currently logged on.

System programmer response name
The resource for which the access level was
The operator has been deleted from DSIOPF, or if the
queried.
current value of OPERSEC is SAFDEF, the operator is
not defined to the SAF product or to the APPL class for DWO843I command COMMAND FAILED
this domain. Consider ending the operator session by
issuing the STOP command with the FORCE keyword. Explanation
If the operator is a VOST, no action is required. The command that you entered failed
DWO840I operid IS NOT DEFINED TO Message Variables
NETVIEW
command
Explanation
The operator specified is not currently defined to the Operator response
NetView program.
See the associated messages for error information.
Message Variables Correct the problem and issue the command again.
operid DWO850I SAF REFRESH INVALID.
The ID of the specified operator. SAFREFSH SET TO NO IN DSIUDST
INITIALIZATION MEMBER
If the operator ID is DSIWEB, define DSIWEB as a Explanation
NetView operator before starting DSIWBTSK again. The operator has attempted to change RMTCMD
DWO841I operid IS ALLOWED ACCESS TO security to an SAF level with the REFRESH command.
name The system programmer has prohibited this change by
coding RMTINIT.SAFrefresh=No in the CNMSTYLE
member or by coding SAFREFSH=NO on the
Explanation
RMTSECUR statement in the DSIUDST initialization
This message is displayed after an operator issues a member.
QRS command. The specified operator can access the
specified resource. When running span of control for System action
VTAM resources, this means that the specified
resource is defined in one of the active spans for the The REFRESH command fails. There is no change in
specified operator. the RMTCMD security level.
Message Variables
operid
If appropriate, either change the SAFREFSH parameter
on the RMTSECUR statement and recycle DSIUDST, or
name change the RMTINIT.SAFrefresh value in the
The resource queried. CNMSTYLE member and recycle the NetView program
before attempting the command again. See IBM Z
DWO842I operid IS NOT ALLOWED ACCESS
NetView Installation: Getting Started for information on
TO name
how to modify the CNMSTYLE member.
Explanation DWO851I TEST OF REFRESH OPERS

COMMAND COMPLETED WITH
This message is displayed if the operator does not
ERRORS
have access to the specified resource. For VTAM
resources, the operator does not have access unless
the resource is defined in one of the active spans at Explanation
the necessary access level. A REFRESH OPERS,TEST command detected errors
Message Variables while processing DSIOPF.
operid Operator response


System programmer response NetView program issues this message during its own
initialization if VTAM is up before the NetView
Correct the statements in DSIOPF.
program.
DWO852I REFRESH COMMAND COMPLETED • If object is Canzlog, NetView startup or restart is
WITH ERRORS proceeding normally. Connection to the active
Canzlog data space is required for message
Explanation processing functions.
A REFRESH OPERS or REFRESH OPERSEC command • If object is ?NAPOLTSKx, where x is a number, a Z
detected errors while processing DSIOPF. The NetView Enterprise Management Agent data
associated messages describe the errors. Operator collection autotask is active and automation is
definitions which contain no errors are updated. driven.
• If object is ?MVSCMDREVISION, the autotask that
Operator response manages the NETVONLY action for the Command
Revision function is now active.
• If object is ?COLTSKx, where x is a number, a
NetView data collection autotask is active and
automation is driven to begin the collection of data.
Review the associated messages. Correct any errors in
Message Variables
DSIOPF and issue the REFRESH command again.
object
DWO853I REQUEST NOT COMPLETED; NO The name of the object that is now active.
ACTIVE DATABASE FOR TASK
taskname
Explanation Automate this message if action is needed to set up
parameters or issue commands to VTAM.
A command to update a database for the named task
cannot be completed because there is currently no DWO900E CANNOT SPECIFY A VALUE WITH
active database for the task. A KEYWORD
Message Variables
Explanation
taskname
The name of the task running the command. The system console operator specified a DISPPI or
TRACEPPI command with a keyword followed by an
equal sign.
System action
The command ends. System action
Operator response
Switch to the primary or secondary database for the Operator response
task and issue the command again.
Issue the command again with the correct syntax.
System programmer response DWO901E INCORRECT KEYWORD
If switching to the primary or secondary database is SPECIFIED
unsuccessful, delete or redefine the VSAM cluster and
issue the SWITCH command again. Explanation
DWO854I object is active. The system console operator specified a DISPPI or

TRACEPPI command with a unknown keyword.
Explanation
System action
The NetView program has recognized that object is
now active. The command is ignored.
• If object is VTAM, the NetView program has opened

Operator response
its ACBs and taken all other necessary actions to
prepare for your use of VTAM interfaces. The Issue the command again with the correct syntax.

DWO902E TOO MANY KEYWORDS Operator response
SPECIFIED Issue the command again with ON, OFF, MODIFY or
END.
Explanation
DWO906E SIZE PARAMETER IS NOT
A command was issued with too many keywords. ALLOWED WITH TRACEPPI
MODIFY
System action
The command is ignored. Explanation
The system console operator specified TRACEPPI
Operator response MODIFY with the SIZE parameter.
System action
DWO903E DUPLICATE KEYWORDS
SPECIFIED The command is ignored.
The system console operator specified a DISPPI or Issue the command again without the SIZE parameter.
TRACEPPI command with duplicate keywords. DWO907E SIZE PARAMETER IS NOT
ALLOWED WITH TRACEPPI OFF
System action
The system console operator specified TRACEPPI OFF
Operator response with the SIZE parameter.
System action
DWO904E INCORRECT VALUE SPECIFIED
Explanation
Operator response
The system console operator specified a DISPPI or
TRACEPPI command with a value that was too long or Issue the command again without the SIZE parameter.
was a numerical value with non-numeric characters. DWO908E GTF PARAMETER IS NOT
System action
Operator response with the GTF parameter.
Issue the command again with correct values.
System action
DWO905E MUST SPECIFY ON, OFF, MODIFY,
OR END The command is ignored.
The system console operator specified a TRACEPPI Issue the command again without the GTF parameter.
command without specifying either ON, OFF, MODIFY, DWO909E GTF PARAMETER IS NOT
or END. ALLOWED WITH TRACEPPI END

The command is ignored. The system console operator specified TRACEPPI END
with the GTF parameter.

The command is ignored. The system console operator specified TRACEPPI END
with the BUFSIZE parameter.
Operator response
System action
Issue the command again without the GTF parameter.
DWO910E GTF PARAMETER IS NOT
ALLOWED WITH TRACEPPI
MODIFY Operator response
Issue the command again without the BUFSIZE
Explanation parameter.
The system console operator specified TRACEPPI DWO914E TRACEPPI FAILED
MODIFY with the GTF parameter.
Explanation
System action
The TRACEPPI command failed.
System action
Operator response
Issue the command again without the GTF parameter.
DWO911E SIZE PARAMETER IS NOT Operator response
ALLOWED WITH TRACEPPI END Read the preceding message for explanation of the
failure.
Explanation
DWO915I TRACEPPI COMPLETED
The system console operator specified TRACEPPI END SUCCESSFULLY FOR RECEIVER
with the SIZE parameter. receiver_id

The command is ignored. The TRACEPPI command completed successfully.
Message Variables
Operator response
receiver_id
Issue the command again without the SIZE parameter. The receiver ID that is specified in the TRACEPPI
DWO912E BUFSIZE PARAMETER IS NOT command or all.
System action
Explanation The specified TRACEPPI function is performed.
The system console operator specified TRACEPPI OFF DWO916E INCORRECT COMBINATION OF
with the BUFSIZE parameter. PARAMETERS

The command is ignored. The system console operator specified DISPPI or
TRACEPPI with conflicting keywords.
Operator response
Issue the command again without the BUFSIZE System action
parameter. The command is ignored.
DWO913E BUFSIZE PARAMETER IS NOT
ALLOWED WITH TRACEPPI END Operator response
Issue the command again with correct syntax.

DWO917E TRACEPPI ON SPECIFIED FOR A Explanation
RECEIVER THAT IS NOT DEFINED The system console operator specified TRACEPPI END
for a receiver that is not defined in the program-to-
Explanation program interface.
The system console operator specified TRACEPPI ON
for a receiver that is not defined in the program-to- System action
program interface. The command is ignored.

The command is ignored. Verify that the correct receiver ID was specified on the
TRACEPPI command, and issue the command again.
Operator response
DWO921E TRACEPPI ON SPECIFIED FOR A
Verify that the correct receiver ID was specified on the RECEIVER THAT IS ACTIVE
DWO918E TRACEPPI OFF SPECIFIED FOR A Explanation
RECEIVER THAT IS NOT DEFINED The system console operator specified TRACEPPI ON
for a receiver that already has an active program-to-
Explanation program interface trace.
for a receiver that is not defined in the program-to- System action
program interface. The command is ignored.

Operator response
DWO922E TRACEPPI MODIFY SPECIFIED
Verify that the correct receiver ID was specified on the FOR A RECEIVER THAT DOES NOT
TRACEPPI command and issue the command again. HAVE A TRACE DEFINED
DWO919E TRACEPPI MODIFY SPECIFIED
FOR A RECEIVER THAT IS NOT Explanation
DEFINED The system console operator specified TRACEPPI
MODIFY for a receiver that does not have a program-
Explanation to-program interface trace defined.
The system console operator specified TRACEPPI
MODIFY for a receiver that is not defined in the System action
program-to-program interface. The command is ignored.

Operator response To define a new trace, issue the TRACEPPI ON
Verify that the correct receiver ID was specified on the command.
TRACEPPI command, and issue the command again. DWO923E TRACEPPI OFF SPECIFIED FOR A
DWO920E TRACEPPI END SPECIFIED FOR A RECEIVER THAT IS INACTIVE
RECEIVER THAT IS NOT DEFINED
Explanation
for a receiver that does not have an active program-to-
program interface trace.

System action DWO927I TRACEPPI END SPECIFIED FOR
ALL RECEIVERS BUT THERE ARE
NO DEFINED TRACES
Operator response
Explanation
Verify that the correct receiver ID was specified on the
The system console operator specified a TRACEPPI
END with the ALL option, but there is no receiver with a
DWO924E TRACEPPI END SPECIFIED FOR A defined program-to-program interface trace.
RECEIVER THAT DOES NOT HAVE
A TRACE DEFINED System action
The default values are changed
Explanation
DWO928I TRACEPPI ON SPECIFIED FOR ALL
The system console operator specified TRACEPPI END
RECEIVERS BUT AT LEAST ONE
for a receiver that does not have a program-to-
RECEIVER IS ALREADY ACTIVE
program interface trace defined.
Explanation
System action
ON with the ALL option, and at least one receiver in the
program-to-program interface had a trace status of
Operator response active.
Verify that the correct receiver ID was specified on the
TRACEPPI command, and issue the command again. System action
DWO925I TRACEPPI OFF SPECIFIED FOR This TRACEPPI command has no effect on the trace
ALL RECEIVERS BUT THERE ARE characteristics of all active receivers. The TRACEPPI
NO ACTIVE TRACES command continues processing for the inactive
receivers.
Explanation
Operator response
OFF with the ALL option, but there is no receiver with Issue the TRACEPPI MODIFY command with the
an active program-to-program interface trace. RCVRID keyword.
DWO929I TRACEPPI OFF SPECIFIED FOR
System action ALL RECEIVERS BUT AT LEAST
The default values are changed ONE RECEIVER IS ALREADY
INACTIVE
DWO926I TRACEPPI MODIFY SPECIFIED
FOR ALL RECEIVERS BUT THERE
Explanation
ARE NO DEFINED TRACES
Explanation OFF with the ALL option, and at least one receiver in
the program-to-program interface had a trace status
The system console operator specified a TRACEPPI of inactive.
MODIFY with the ALL option, but there is no receiver
with a defined program-to-program interface trace.
System action
System action This TRACEPPI command has no effect on the trace

characteristics of all inactive receivers. The TRACEPPI
The default values are changed command continues processing for the active
receivers.
Operator response
DWO930I TRACEPPI MODIFY SPECIFIED
Issue a TRACEPPI ON command to define a new FOR ALL RECEIVERS BUT AT
program-to-program interface trace. LEAST ONE RECEIVER DOES NOT
HAVE A TRACE DEFINED

Explanation DWO933E GTF IS NOT ENABLED TO ACCEPT
PROGRAM TO PROGRAM
INTERFACE TRACE RECORDS
MODIFY with the ALL option, and at least one receiver
in the program-to-program interface had a trace status
of not defined. Explanation
GTF is inactive or was started without enabling
System action program-to-program interface trace records.
This TRACEPPI command has no effect on the trace
characteristics of any receivers that do not have a System action
trace defined. The TRACEPPI command continues The trace is placed into a GTF DISABLED state. When
processing for the all receivers that have a defined GTF becomes enabled and the program-to-program
trace. interface sends it a trace record, the program-to-
program interface issues a message and the trace is
Operator response placed in the GTF state.
To define a trace for a program-to-program interface
receiver, issue the TRACEPPI ON command. Operator response
DWO931E GTF TRACE NOT ALLOWED. Start the GTF address space with program-to-program
INTERNAL TRACE IS CURRENTLY interface trace records enabled. Use X'5EF' as the ID
DEFINED for the program-to-program interface trace.
The system console operator specified a TRACEPPI If using a user-written procedure to start the GTF
command with the GTF option, but an internal trace is address space, ensure that it enables GTF to accept
already defined for that receiver. program-to-program interface trace records.
DWO934E PROGRAM TO PROGRAM
System action INTERFACE TRACE SIZE OPERAND
The command is ignored. CANNOT BE 0
Explanation
Operator response
The system console operator specified 0 for the SIZE
Issue a TRACEPPI END command to end the current
parameter on a TRACEPPI command.
trace. Then, issue TRACEPPI ON command with the
GTF option.
System action
DWO932E INTERNAL TRACE NOT ALLOWED.
GTF TRACE IS CURRENTLY The command is ignored.
DEFINED
Operator response
Explanation Issue the TRACEPPI command again with a non-zero
The system console operator specified a TRACEPPI value for SIZE.
command with the SIZE option, but a GTF trace is DWO935E BUFSIZE OPERAND CANNOT BE
already defined for that receiver. GREATER THAN 208 BYTES WHEN
A GTF TRACE IS DEFINED
System action
On the TRACEPPI command, the system console
Operator response operator specified a BUFSIZE value larger than 208
Issue a TRACEPPI END command to end the current bytes when the GTF option was used.
trace. Then, issue TRACEPPI ON command with the
SIZE option. System action

Operator response DWO938I PROGRAM TO PROGRAM
INTERFACE READY FOR
Issue the TRACEPPI command again with a BUFSIZE
COMMUNICATIONS
value less than or equal to 208 bytes.
DWO936E UNABLE TO ALLOCATE THE Explanation
PROGRAM TO PROGRAM
INTERFACE TRACE TABLE A system operator issued MSG Fn initiating the
program-to-program interface command facility.
Explanation
System action
The program-to-program interface trace facility is
unable to allocate storage in the program-to-program The program-to-program interface command facility
interface for the trace table. waits for operator input.
The command is ignored. Issue a program-to-program interface command.

DWO939E INVALID PROGRAM TO PROGRAM
Operator response INTERFACE COMMAND.
COMMAND IGNORED
Issue the TRACEPPI command again with a smaller
value for the SIZE parameter.
Explanation
System programmer response A system operator issued a program-to-program
Allocate more virtual storage for the program-to- interface command that was not valid.
program interface.
System action
DWO937E GTRACE FAILURE, RETURN CODE
= yy. PROGRAM TO PROGRAM The command is ignored.
INTERFACE TRACE IS SUSPENDED
Operator response
Explanation Issue a valid program-to-program interface command.
A failure occurred when the program-to-program DWO940I PROGRAM TO PROGRAM
interface issued the GTRACE macro to send a record to INTERFACE DUMP COMPLETE
GTF.
yy The program-to-program interface dump completed.
Return code from the GTRACE macro.
System action
System action
A formatted program-to-program interface dump is
The program-to-program interface is put into a GTF spooled.
DISABLED state. All traces are lost until GTF is
enabled again. DWO941I TRACEPPI OFF SPECIFIED FOR
ALL RECEIVERS BUT THERE ARE
NO DEFINED TRACES
Operator response
Issue the TRACEPPI ON command again when the Explanation
error is corrected to reactivate the trace.
for all receivers, but there is no receiver that has a
defined trace.
Consult the MVS library for an explanation of the
GTRACE return code, and take appropriate action. System action
Default values are changed, but no receiver values are
changed.

DWO942E NO PROGRAM TO PROGRAM Explanation
INTERFACE TRACE DEFINED The program-to-program interface was unable to set
up an interrupt handler.
Explanation
Message Variables
The system console operator specified TRACEPPI with
OFF, MODIFY, or END, but no program-to-program yy
interface traces have been defined. Return code from the IMMCMD macro.
The command is ignored. The program-to-program trace facility is not available.
Issue a TRACEPPI ON command to define a program- Contact IBM Software Support.

to-program interface trace. DWO946E UNABLE TO OBTAIN STORAGE
DWO943I GTF IS ENABLED TO ACCEPT FOR NETVIEW DATA TRANSPORT
PROGRAM TO PROGRAM ANCHOR BLOCK (DSIDTA)
INTERFACE TRACE RECORDS,
TRACE IS RESUMING Explanation
During initialization, the SSI was unable to allocate
Explanation storage for the data transport anchor block. This
The program-to-program interface was in a GTF control block is an internal NetView structure. In the
DISABLED state and successfully sent a trace record event that IBM Software Support needs to be
to GTF. contacted, provide this message ID.
The program-to-program interface trace is set to the The SSI initialization ends.
GTF state, and the program-to-program interface trace
record is sent to GTF. Operator response
DWO944I GTF IS NOT ENABLED TO ACCEPT Contact the system programmer.

PROGRAM TO PROGRAM TRACE
RECORDS, TRACE IS SUSPENDED System programmer response
Verify the amount of storage allocated for the SSI
Explanation address space. Increase, if necessary, and restart the
The program-to-program interface tried to send GTF a SSI. If you are still unable to bring up the SSI, contact
trace record, but GTF was not enabled to accept the IBM Software Support.
record. DWO947E Unable to obtain storage for
NetView ppi trace table anchor
System action block
The program-to-program interface trace is set to GTF
DISABLED, and the trace record is lost. All further Explanation
trace records are lost until GTF is enabled to accept
During initialization, the SSI was unable to allocate
program-to-program interface records.
storage for the program-to-program interface trace
table anchor block. This control block is an internal
System programmer response NetView structure.
Restart GTF with program-to-program interface trace
records (ID X'5EF') enabled. System action
DWO945E UNABLE TO SET UP INTERRUPT SSI initialization ends.
HANDLER, RETURN CODE = yy
SUSPENDED

Operator response BUFFER LIMIT
The receiver's buffer queue limit.
QUEUED BUFFERS
System programmer response The number of buffers in the receiver's queue.
TOTAL BUFFERS
Verify the amount of storage allocated for the SSI The total number of buffers sent to a receiver.
address space. Increase, if necessary, and restart the
SSI. If you are still unable to bring up the SSI, contact STORAGE ALLOCATED
IBM Software Support. The total number of bytes allocated for the buffers
in the receiver's queue.
DWO948I RECEIVER RECEIVER BUFFER
RCVR ASID
QUEUED TOTAL STORAGE RCVR
The address space ID of the program-to-program
interface receiver.
Explanation
This message is the first line of the header for the System action
output from the DISPPI command with the BUFQ
Message DWO950I follows this message.
operand. This message is part of a multiline message.
The columns contain: DWO950I -------- -------- ---------- ----------
RECEIVER IDENTITY ---------- ---------- ----
The program-to-program interface receiver ID.
RECEIVER STATUS Explanation
Indicates whether the receiver is active or inactive. This message is the third line of the header for the
BUFFER LIMIT output from the DISPPI command with the BUFQ
The receiver's buffer queue limit. operand. This message is part of a multiline message.
QUEUED BUFFERS
The number of buffers in the receiver's queue. System action
TOTAL BUFFERS DISPPI data follows this message.
The total number of buffers sent to a receiver.
DWO951I &1 ACTIVE &2 &3 &4 &5 &6
STORAGE ALLOCATED
The total number of bytes allocated for the buffers Explanation
in the receiver's queue.
This message is one of the data items in response to
RCVR ASID
the DISPPI BUFQ or DISPPI TRACE commands. This
The address space ID of the program-to-program
message is part of a multiline message.
interface receiver.
System action
System action
DISPPI data is included in this message.
Message DWO949I follows this message.
DWO952I &1 INACTIVE &2 &3 &4 &5
DWO949I IDENTITY STATUS LIMIT
BUFFERS BUFFERS ALLOCATED
ASID Explanation
Explanation the DISPPI BUFQ or DISPPI TRACE commands. This
message is part of a multiline message.
This message is the second line of the header for the
output from the DISPPI command with the BUFQ
operand. This message is part of a multiline message. System action
The columns contain: DISPPI data is included in this message.
RECEIVER IDENTITY DWO953I &1 NOT DEFINED
The program-to-program interface receiver ID.
RECEIVER STATUS
Indicates whether the receiver is active or inactive.

This message is one of the data items in response to This message is the second line of the header for the
the DISPPI BUFQ or DISPPI TRACE commands. This output from the DISPPI command with the TRACE
message is part of multiline message. operand. This message is part of a multiline message.
The column headings are:
System action RECEIVER IDENTITY
DISPPI data is included in this message. Program-to-program interface receiver ID.
TRACE STATUS
DWO954E THIS LEVEL OF NETVIEW Indication of whether the receiver has a trace
PROGRAM TO PROGRAM defined and the trace is turned on (active), has a
INTERFACE DOES NOT SUPPORT trace defined but the trace has been turned off
THE DISPPI FUNCTION (inactive), or has no trace defined (not defined).
TRACE BUFFER SIZE
Explanation
The number of bytes being copied into a trace
The level of program-to-program interface that is record from each buffer being sent or received by
currently running is V2R3 or less. the receiver.

The command is ignored. DISPPI data follows this message.
DWO957I TRACE DEFINED: YES
Operator response
Issue a DISBQL command. Explanation
This is one of the messages displayed when the
System programmer response DISPPI command is issued with the TABLE operand.
Start the program-to-program interface with NetView This message is part of a multiline message.
V2R4 or higher. TRACE DEFINED
DWO955I RECEIVER TRACE TRACE Indication whether a program-to-program
interface trace is currently defined.
Explanation
System action
This message is the first line of the header for the
output from the DISPPI command with the TRACE DISPPI data is displayed with this message.
operand. This message is part of a multiline message. DWO958I TRACE DEFINED: NO
The column headings are:
RECEIVER IDENTITY Explanation
Program-to-program interface receiver ID.
TRACE STATUS DISPPI command is issued with the TABLE operand.
Indication of whether the receiver has a trace This message is part of a multiline message.
defined and the trace is turned on (active), has a
trace defined but the trace has been turned off TRACE DEFINED
(inactive), or has no trace defined (not defined). Indication whether a program-to-program
interface trace is currently defined.
TRACE BUFFER SIZE
The number of bytes being copied into a trace
System action
record from each buffer being sent or received by
the receiver. DISPPI data is displayed with this message.
DWO959I TRACE TYPE: INTERNAL
System action
Message DWO956I follows this message. Explanation
DWO956I IDENTITY STATUS BUFFER SIZE This is one of the messages displayed when the
DISPPI command is issued with the TABLE operand.
This message is part of a multiline message.

TRACE TYPE Explanation
The program-to-program interface trace can be in
one of three states: INTERNAL, GTF, GTF
DISABLED.
System action TABLE ADDRESS

The address of the program-to-program interface
DISPPI data is displayed with this message. trace table.
DWO960I TRACE TYPE: GTF Message Variables
zzzzzzzz
Explanation The address of the table in hex.
DISPPI command is issued with the TABLE operand. System action
DISPPI data is displayed with this message.
TRACE TYPE
The program-to-program interface trace can be in DWO964I TRACE ALL: YES
DISABLED. Explanation
System action DISPPI command is issued with the TABLE operand.
DISPPI data is displayed with this message. This message is part of a multiline message.
TRACE ALL
DWO961I TRACE TYPE: GTF DISABLED
Indication whether all receivers are being traced.
Explanation
System action
DISPPI data is displayed with this message.
This message is part of a multiline message. DWO965I TRACE ALL: NO
TRACE TYPE
The program-to-program interface trace can be in Explanation
DISABLED.
System action
TRACE ALL
DISPPI data is displayed with this message. Indication whether all receivers are being traced.
DWO962I TABLE SIZE: xxxxxxxx
System action
Explanation DISPPI data is displayed with this message.
This is one of the messages displayed when the DWO966I DEFAULT BUFFER SIZE: yyyyyyyy
Explanation
TABLE SIZE
The number of pages allocated for the program-to-
program interface trace table.
System action DEFAULT BUFFER SIZE

The value a receiver's BUFSIZE will be set up to
DISPPI data is displayed with this message. when the receiver initializes with the program-to-
DWO963I program interface.
TABLE ADDRESS: zzzzzzzz
Message Variables

yyyyyyyy might be that a bad stack name was supplied, possibly
The default buffer size. by a TCPCONN.ROWSA definition in the CNMSTYLE
member.
DISPPI data is displayed with this message. reporter
DWO967E BUFSIZE VALUE CANNOT BE The component that reported the message
LARGER THAN THE SIZE OF THE failcomp
TRACE TABLE The component that failed
retcode
Explanation The return code
The BUFSIZE value entered causes the trace record to
be too large to fit into the program-to-program Operator response
interface trace table. Determine the cause of the failure and try to correct
the problem. Otherwise, contact your system
System action programmer.
Operator response If the problem is not apparent contact IBM Software
Support.
Specify a smaller BUFSIZE value
Note: If the failing component is QSAM-WRITE, the
DWO968I END OF DISPLAY
retcode value will be one of the return codes that are
documented for the PIPE QSAM stage.
Explanation
DWO971I reporter : listelt ADDED TO listtyp
The DISPPI command has completed. LIST

DISPPI has completed. An element was added to a list.
DWO969I DOMAIN FOR cpname IS domname Message Variables
reporter
Explanation
The component that reported the message
The indicated domain name matches the specified CP listelt
name. The element that was added to the list
Message Variables listtyp
cpname The type of list to which the element was added
The CP name that was specified. DWO972I reporter : listelt REMOVED FROM
domname listtyp LIST
The NetView domain name at the specified CP.
DWO970I Explanation
reporter : failcomp FAILED WITH
RETURN CODE retcode An element was removed from a list.
Message Variables
Explanation
reporter
A component failed and a return code was received. The component that reported the message
If this message indicates that DSITAQUA had a return listelt
code of 24, a DWO050I message in the netlog can The element that was removed from the list
indicate more information about the failure of the
listtyp
underlying Communications Server interface.
The type of list from which the element was
Furthermore, if that DWO050I message indicates that
removed
the EZBNMIFR interface had a return code of 121, it

DWO973I reporter : NO TASKS EXCEED THE Explanation
LIMIT OF nummin MINUTE(S) This describes an operator that exceeds the idle time
specified by the IDLEOFF command.
Explanation
Message Variables
No attended tasks were found whose idle times, as
shown in the NCCF LIST command, exceed the reporter
maximum idle time specified in the IDLEOFF The component that reported the message
command. opid
The operator name, in the form OPID=xxxxxxxx
Message Variables
luname
reporter The LU name associated with the operator, in the
The component that reported the message form LU=xxxxxxxx
nummin time
The number of minutes defined by IDLEOFF The number of minutes that the operator has been
DWO974I reporter : ACTIVE TASKS EXEMPT idle as shown in the NCCF LIST command
FROM IDLE TIME LIMITS: DWO978E URL WAS NOT DEFINED IN
CNMSTYLE
Explanation
The label line for the list of active attended tasks that Explanation
are exempt from being logged off by the IDLEOFF A URL was requested for the web application server
command. servlet, but the URL is not defined to the global
Message Variables variable in the CNMSTYLE member.
reporter
System action
The component that reported the message
The command list exits.
DWO975I reporter : NO ACTIVE TASKS ARE
EXEMPT FROM IDLE TIME LIMITS
Operator response
No active attended tasks are exempt from being
logged off by the IDLEOFF command. System programmer response
Message Variables From IBM Z NetView and UNIX System Services,

update the URL of the servlet or servlets that are used
reporter to invoke various functions in global variables defined
The component that reported the message in the CNMSTYLE member.
DWO976I reporter : etype edesc DWO979I LIMIT REACHED - OUTPUT
TRUNCATED
Explanation
The description of an exception. Explanation
Message Variables A request produced an excessive amount of data,
which was truncated.
reporter
The component that reported the message.
System action
etype
The type of exception being described. The truncated data is output.
edesc
A description or name of the exception. This can Operator response
be a list of names that begin on the following line. In the case of a SESS command or other session list
DWO977I reporter : opid luname time (NLDM.SESS) request, consider listing the other
session endpoint or issuing a SESS command
specifying both session endpoints. Consider specifying
a larger maximum value on the SESS command.

DWO990I type global variable variable_name Explanation
set by command via A GLOBALV TRACE (C or T) ON request was issued
invoked_LRC--->calling_LRC to specifically or generically for the named global
value --->new_value<--- variable to trace changes to the named global variable
value.
Explanation
Message Variables
A GLOBALV TRACE (C or T) ON request was issued
specifically or generically for the named global type
variable to trace changes to the named global variable The type of global variable being changed. Possible
value. values are:
Common
Message Variables
for a common global variable
type Task
The type of global variable being changed. Possible for a task global variable
values are:
variable_name
Common The name of the global variable being changed.
for a common global variable
command
Task The name of the CLIST or HLL command changing
for a task global variable the global variable value.
variable_name invoked_LRC
The name of the global variable being changed. The name of the long-running command (LRC),
command which can be a CLIST, a PIPE or a REXX program
The name of the command changing the global entered by the operator or invoked by automation,
variable value. or by the timer, or by some other method.
invoked_LRC new_value
The name of the long-running command (LRC), The new value being assigned to global variable
which can be a CLIST, a PIPE, or a REXX program variable_name. Only the first 255 characters are
entered by the operator or invoked by automation, shown, if the value is longer.
or by the timer, or by some other method.
calling_LRC System action
The name of the long-running command (LRC) This message is logged in the NetView log.
CLIST, a PIPE, or a REXX program calling the
command command.
Operator response
Note: The invoking_LRC and the calling_LRC might
be the same. None
new_value System programmer response

The new value being assigned to global variable
variable_name. Only the first 255 characters are None
shown, if the value is longer.
DWO992I type global variable variable_name
set by command to value ---
System action >new_value<---
This message is logged in the NetView log.
Explanation
Operator response A GLOBALV TRACE (C or T) ON request was issued
None specifically or generically for the named global
variable to trace changes to the named global variable
value.
Message Variables
None
type
DWO991I type global variable variable_name The type of global variable being changed. Possible
set by command via invoked_LRC values are:
to value --->new_value<---

Common *ALL
for a common global variable For all global variables of listType function
Task groupID
for a task global variable for the specific group of global variables being
variable_name listed
The name of the global variable being changed.
System action
command
The name of the command changing the global This is a multiline message sent to the operator.
variable value.
new_value Operator response
The new value being assigned to global variable None
variable_name. Only the first 255 characters are
shown, if the value is longer.
System action None
This message is logged in the NetView log. DWO994I type global variable variable_name
set to value --->new_value
Operator response
Explanation
None
A GLOBALV AUTO (C or T) ON request was issued
System programmer response specifically or generically for the named global
variable to automate changes to the named global
None variable value.
DWO993I List of listType GVtype global Message Variables
variables for group GVgroup
type
The type of global variable being changed. Possible
Explanation values are:
A GLOBALV AUTO (C or T) or TRACE (C or T) LIST Common
request was issued specifically or generically for the for a common global variable
named group or groups. The variables being
automated or traced and the group to which they Task
belong are listed. for a task global variable
variable_name
Message Variables
The name of the global variable being changed.
listType new_value
The global variable function being listed. Possible The new value being assigned to global variable
values are: variable_name. Only the first 255 characters are
automated shown, if the value is longer.
list of variables being automated
traced System action
list of variables being traced This message is automated. By default, this message
GVtype is not displayed and is not logged. Use the DISPLAY(Y)
The type of global variable being listed. Possible and NETLOG(Y) automation table actions to override
values are: these defaults.
COMMON
for list of common global variables Operator response
TASK None
for list of task global variables
GVgroup System programmer response
The group of global variables being listed. Possible None
values are:

Chapter 3. EJN Prefix Messages
This chapter lists the EJN prefix messages.

EJN001I AUTOMATION TABLE STATEMENT The server will have an output file for all messages
SAVED SUCCESSFULLY logged by the server. Spring Boot comes with a very
robust logging system. It provides filtering to control
Explanation what types of messages show up in the log. The
following levels are used to filter: TRACE, DEBUG,
The NetView REST Server saved and stored a single INFO, and ERROR. The server is designed to use INFO
automation table statement or set of automation table and DEBUG for troubleshooting purposes. This can be
statements in a dataset specified by the user. specified from the application.yml file. The
sample contains a logging section at the bottom of the
EJN002I AUTOMATION TABLE STATEMENT
file.
SAVE FAILED
Example logging configuration:
Explanation
logging:
An error occurred while the NetView REST Server was level:
root: DEBUG
attempting to save a user's automation table file: ${NVRESTCONFIG}/logs/debug.log
statement. The user should verify that the Dataset
where the save is to occur contains a valid HLQ and
MLQ.

Chapter 4. EKG Prefix Messages
EKG prefix messages describe errors that occur with the Resource Object Data Manager (RODM).
EKG0001E jobname: REQUIRED STORAGE ddname
CANNOT BE OBTAINED. The name of the RODM log file specified in the
RODM START job control language (JCL).
Explanation
System action
The Resource Object Data Manager (RODM) tried to
obtain the virtual storage required for internal tables, RODM continues logging with the specified file.
but no storage was available.
jobname Notify the system programmer if necessary.

The RODM job name specified in the MVS START
Determine whether there was a failure in writing to the
System action previous RODM log file or whether the previous RODM
RODM ends. log file reached capacity. If there was a write failure,
analyze the appropriate RODM log file to determine
the source of the error. See the IBM Z NetView
Operator response Troubleshooting Guide for information about RODM log
Notify the system programmer. record formats. See the MVS system console for IEC
messages.
System programmer response EKG0003I jobname: PRIMARY LOG FILE
Analyze the appropriate RODM log file to determine CANNOT BE OPENED.
Troubleshooting Guide for information about RODM log Explanation
record formats. Increase the region size for RODM and
The Resource Object Data Manager (RODM) cannot
restart it.
open the primary log file for one of the following
EKG0002I jobname: THE CURRENT ACTIVE reasons:
LOG FILE IS NOW ddname. • The primary file does not exist.
• The primary file is not properly defined.
Explanation
• The primary log file is already in use.
A new Resource Object Data Manager (RODM) log file
has been opened for one of the following reasons: Message Variables
• The previous RODM log file is full. jobname

• The write request to the previous RODM log file
command
failed.
• RODM has just initialized. This is an informational System action
message only.
If the error occurs during initialization, RODM
• A LOGQ command has been issued. This is an
continues processing without the primary log file.
informational message only.
RODM does not attempt to open the secondary log file.
Message Variables The switch log function (LOGP) is now disabled.
jobname
The RODM job name specified in the MVS START Operator response
command. After issuing the MVS MODIFY jobname, LOGP
command, review the messages displayed. Notify the
system programmer.

Verify that the primary log file is defined correctly. See RODM ends.
IBM Z NetView Installation: Getting Started for
information about the START job control language Operator response
(JCL) and the associated file names. See the NetView
online help for information about the MVS MODIFY Notify the system programmer.
command.
EKG0004I jobname: SECONDARY LOG FILE
CANNOT BE OPENED. Check if the CCSID keyword is missing in the control
record. The control record is the second record.
Explanation Ensure the CCSID contains 00037 for English.
The Resource Object Data Manager (RODM) cannot EKG0901E jobname: THE MESSAGE TEXT
open the secondary log file for one of the following FILE CANNOT BE READ.
reasons:
Explanation
• The secondary log file does not exist.
• The secondary log file is not properly defined. The Resource Object Data Manager (RODM) cannot
read the message text file member EKGMSENU for one
• The secondary log file is already in use. of the following reasons:
Message Variables • RODM cannot find the message text file.
jobname • The message text file is empty.
• The record length is not 125.
command
• The record format is not fixed block (FB).
System action • A partitioned data set was not specified for the
EKGLANG DD statement.
RODM continues processing without the secondary log
file. The switch log function (LOGS) is now disabled. Message Variables
jobname
Operator response The RODM job name specified in the MVS START
After issuing the MVS MODIFY jobname, LOGS command
command, return to the console and review the
messages displayed. Notify the system programmer. System action
The message text file is not loaded and RODM ends.
Verify that the secondary log file is defined properly. Operator response
See the IBM Z NetView Installation: Getting Started for Notify the system programmer.
information about the START job control language
(JCL) and associated file names. See the NetView
online help for information about the MVS MODIFY System programmer response
command. Ensure that member EKGMSENU exists in the file
specified by the EKGLANG DD statement of the RODM
EKG0900E jobname: THE CONTROL
START job control language (JCL), and that member
INFORMATION IN THE MESSAGE
EKGMSENU contains the required message text. Also
TEXT FILE IS NOT CORRECT.
ensure that the record length is 125 and the format is
fixed block (FB). See IBM Z NetView Installation:
Explanation Getting Started for information about the START job
The CCSID specified in the message text file, control language (JCL) and associated file names.
EKGMSENU, is incorrect. Restart RODM.
Message Variables EKG0902E jobname: THE FORMAT OF THE

MESSAGE TEXT FILE IS NOT
jobname
CORRECT AT LINE linenumber.
The Resource Object Data Manager (RODM) job
name specified in the MVS START command

The Resource Object Data Manager (RODM) cannot RODM ends.
process the message text file member EKGMSENU
because of one of the following format errors: Operator response
• The first record of the message text file contains Notify the system programmer.
something other than the MVS message services
(MMS) version record.
• One or more message numbers in the message text
file are not in ascending order. Analyze the appropriate RODM log file to determine
• One or more message numbers are not in the format Troubleshooting Guide for information about RODM log
EKGnnnnc, where nnnn is a decimal number and c is record formats.
either E, I, or D.
• Verify that the checkpoint data sets (DD names
Message Variables EKGMAST, EKGTRAN, and EKGDnnn) are properly
jobname defined.
The RODM job name specified in the MVS START • Ensure that the space allocated for the master-
command window checkpoint data set is sufficient for a 2MB
linenumber window.
The number of the line where the error exists • Otherwise, increase the region size for RODM.
• Restart RODM.
System action
See IBM Z NetView Installation: Getting Started for
RODM ends. information about the START job control language
(JCL) and associated file names.
Operator response
EKG1101E jobname: THE FIRST SEGMENT OF
Notify the system programmer. THE TRANSLATION WINDOW
CANNOT BE ALLOCATED.
Determine which format errors exist and correct them. Explanation
See IBM Z NetView Installation: Getting Started for The Resource Object Data Manager (RODM) cannot
information about the START job control language allocate the first segment of the translation window for
(JCL) and associated file names. Restart RODM. one of the following reasons:
EKG1100E jobname: THE MASTER WINDOW • The space allocation for the translation-window
CANNOT BE ALLOCATED. checkpoint data set is insufficient.
• The translation-window checkpoint data set is not
Explanation properly defined.
The Resource Object Data Manager (RODM) cannot • The virtual storage for the translation window is
allocate the master window for one of the following unavailable.
reasons: Message Variables
• The space allocation for the master-window jobname
checkpoint data set is insufficient. The RODM job name specified in the MVS START
• The master-window checkpoint file is not properly command
defined.
• The virtual storage for the master window is not System action
available.
RODM ends.
Message Variables
jobname Operator response
The RODM job name specified in the MVS START Notify the system programmer.
command
Chapter 4. EKG Prefix Messages 293

System programmer response • Verify that the data-window checkpoint data set is
properly defined.
Analyze the appropriate RODM log file to determine
the source of the error. See the IBM Z NetView • Ensure that the size of the data-window checkpoint
Troubleshooting Guide for information about RODM log data set is sufficient. See the EKGSI101 sample for
record formats. information about calculating checkpoint data set
sizes.
• Verify that the translation-window checkpoint data
set is properly defined. • Otherwise, increase the region size for RODM.
• Ensure that the size of the translation-window • Restart RODM.

checkpoint data set is sufficient. See the EKGSI101 EKG1104E jobname: THE MASTER WINDOW
sample for information about calculating checkpoint CANNOT BE CHECKPOINTED. THE
data set sizes. CHECKPOINT FUNCTION IS NOW
• Otherwise, increase the region size for RODM. DISABLED.
• Restart RODM.
Explanation
information about the START job control language The Resource Object Data Manager (RODM) cannot
(JCL) and associated file names. take a checkpoint to the master window checkpoint
file. The checkpoint file might be damaged.
EKG1102E jobname: THE FIRST DATA
WINDOW CANNOT BE ALLOCATED Message Variables
FOR DDNAME ddname. jobname
allocate the first data window for one of the following System action
reasons: The translation and data windows do not take a
• The space allocation for the specified data-window checkpoint. RODM continues processing. The
checkpoint data set is insufficient. checkpoint function is now disabled until RODM is
ended. All transactions that have occurred since the
• The specified checkpoint data set is not properly last successful checkpoint are lost.
defined.
• A data space cannot be created. Operator response
• Virtual storage for RODM has been exhausted.
Message Variables
jobname System programmer response
The RODM job name specified in the MVS START End RODM without taking a checkpoint (MODIFY
command. jobname,TERM). Analyze the appropriate RODM log
ddname file to determine the source of the error. See the IBM Z
The name of the data-window checkpoint data set. NetView Troubleshooting Guide for information about
RODM log record formats. See the NetView online help
System action for information about the MVS MODIFY command.
Warm start RODM using the checkpoint files from the
RODM ends. last successful checkpoint. If no checkpoint files are
available, cold start RODM.
Operator response
EKG1105E jobname: THE TRANSLATION
Notify the system programmer. WINDOW CANNOT BE
CHECKPOINTED. THE
System programmer response CHECKPOINT FUNCTION IS NOW
DISABLED.
Troubleshooting Guide for information about RODM log
record formats.

Explanation data windows prior to the specified data window have
been successfully checkpointed. RODM continues
processing. The checkpoint function is now disabled
take a checkpoint to the translation window
until RODM is ended.
checkpoint file. The file might be damaged.
jobname Notify the system programmer.
command.
System action End RODM without taking a checkpoint (MODIFY

jobname,TERM). When RODM is ended without taking
RODM has already successfully taken a checkpoint to a checkpoint, all transactions occurring after the last
the master window. RODM does not checkpoint the successful checkpoint are lost. Analyze the
translation and data windows and RODM continues appropriate RODM log file to determine the source of
processing. The checkpoint function is now disabled the error. See the IBM Z NetView Troubleshooting
until RODM is ended. All transactions that have Guide for information about RODM log record formats.
occurred since the last successful checkpoint are lost. Warm start RODM using the checkpoint files from the
last successful checkpoint.
Operator response
EKG1107E jobname: THE MASTER WINDOW
Notify the system programmer. CANNOT BE LOADED.

End RODM without taking a checkpoint (MODIFY The Resource Object Data Manager (RODM) cannot
jobname, TERM). Analyze the appropriate RODM log load the master window from the master-window
file to determine the source of the error. See the IBM Z checkpoint data set during a warm start. The master-
NetView Troubleshooting Guide for information about window checkpoint data set might be empty or
RODM log record formats. Warm start RODM using the damaged. The master-window checkpoint data set is
checkpoint files from the last successful checkpoint. the one identified by the EKGMAST DD statement in
the RODM startup JCL.
EKG1106E jobname: A DATA WINDOW
CANNOT BE CHECKPOINTED FOR Message Variables
DDNAME ddname.
jobname
take a checkpoint to the data-window checkpoint file System action
identified by the specified ddname for one of the
RODM ends.
following reasons:
• The data window checkpoint file might be damaged. Operator response
• There is insufficient storage for the DIV macro Notify the system programmer.
request.
jobname Verify that your RODM startup JCL points to a valid,
The RODM job name specified in the MVS START non-empty checkpoint data set, and retry the warm
command. start. Otherwise, cold start RODM.
ddname EKG1108E jobname: THE TRANSLATION
The name corresponding to the data window
WINDOW CANNOT BE LOADED.
checkpoint file.
Explanation
System action
RODM has already successfully taken a checkpoint to
load the translation window from the translation-
the master window and the translation window. All

window checkpoint data set during a warm start. The EKG1110I jobname: TRANSLATION WINDOW
translation-window checkpoint data set might be SEGMENT NUMBER nnn1 CANNOT
empty or damaged. The translation-window BE ALLOCATED. nnn2 SEGMENTS
checkpoint data set is the one identified by the ARE AVAILABLE.
EKGTRAN DD statement in the RODM startup JCL.
jobname The Resource Object Data Manager (RODM) cannot

The RODM job name specified in the MVS START allocate a new segment of the translation window for
command. one of the following reasons:
• The MAX_SEGMENT_NUM keyword from the
System action customization file has been exceeded. (The sample
customization file is EKGCUST.)
RODM ends.
• The virtual storage for RODM is unavailable.
Operator response • If CHECKPOINT_FUNCTION(REQUIRE) was coded in
the RODM customization member, the space
allocated for the translation-window checkpoint data
set is insufficient. (See the EKGTRAN DD statement
System programmer response in the RODM startup JCL.) The most likely reason for
Verify that your RODM startup JCL points to a valid, this error is that your checkpoint data sets are too
non-empty checkpoint data set, and retry the warm small. RODM will not attempt to allocate storage for
start. Otherwise, cold start RODM. data if the total amount of data in RODM exceeds the
amount that can be written to your checkpoint data
EKG1109E jobname: A DATA WINDOW sets.
CANNOT BE LOADED FOR
DDNAME ddname. Message Variables
jobname
Explanation The RODM job name specified in the MVS START
command.
load a data window from the checkpoint data set into nnn1
which it had been previously checkpointed. The The segment number that cannot be allocated.
specified checkpoint data set might be empty or nnn2
damaged. The number of unused segments.
Message Variables
System action
jobname
The RODM job name specified in the MVS START RODM continues processing. Requests from user
command. applications requiring additional storage (for example,
creating an object) might not be processed.
ddname
The name corresponding to the checkpoint data
set for the data window. Operator response
System action
RODM ends. System programmer response
Verify that the MAX_SEGMENT_NUM setting in your
Operator response customization file is sufficient. IBM recommends
setting this keyword to its maximum value because
translation window segments are only allocated when
they are actually used.
Check and correct your EKGTRAN checkpoint data set
Verify that your RODM startup JCL points to a valid, size.
non-empty checkpoint data set, and retry the warm
start. Otherwise, cold start RODM. If this error was generated because of the checkpoint
data set size, you can avoid the error in the future by

disabling the checkpoint function, or by ensuring that System action
your checkpoint data sets are large enough.
RODM continues processing. Requests from user
To disable the checkpoint function, code applications requiring additional storage (for example,
CHECKPOINT_FUNCTION(NONE) in the customization creating an object) might not be processed.
file. Note that disabling the checkpoint function also
disables the warm start option. Operator response
If the checkpoint function is enabled, ensure that your Notify the system programmer.
checkpoint data sets are large enough. See the
EKGSI101 sample for information about calculating
the proper size for your checkpoint data sets.
Verify that the MAX_WINDOW_NUM setting in your
If you determine that this error is not related to your
customization file is sufficient. IBM recommends
checkpoint data set size, or the MAX_SEGMENT_NUM
setting this keyword to its maximum value because
keyword, increase the region size for RODM.
data windows are only allocated when they are
After performing any of the previous steps, you must actually used.
restart RODM.
Check and correct your EKGDnnn checkpoint data set
EKG1111I jobname: DATA WINDOW NUMBER sizes.
nnn1 CANNOT BE ALLOCATED. If this error was generated because of the checkpoint
nnn2 UNUSED DATA WINDOWS data set size, you can avoid the error in the future by
ARE STILL AVAILABLE. disabling the checkpoint function, or by ensuring that
Explanation
To disable the checkpoint function, code
The Resource Object Data Manager (RODM) cannot CHECKPOINT_FUNCTION(NONE) in the customization
allocate a data window for one of the following file. Note that disabling the checkpoint function also
reasons: disables the warm start option.
• The MAX_WINDOW_NUM keyword from the If the checkpoint function is enabled, ensure that your
customization file has been exceeded. (The sample checkpoint data sets are large enough. See the
customization file is EKGCUST.) EKGSI101 sample for information about calculating
• A data space cannot be created. the proper size for your checkpoint data sets.
• Virtual storage for RODM has been exhausted. If you determine that this error is not related to your
• If CHECKPOINT_FUNCTION(REQUIRE) is coded in checkpoint data set size, or the MAX_WINDOW_NUM
the RODM customization member, the space keyword, increase the region size for RODM.
allocated for the translation-window checkpoint data After performing any of the previous steps, you must
set is insufficient. (See the EKGTRAN DD statement restart RODM.
in the RODM startup JCL.) The most likely reason for
this error is that your checkpoint data sets are too EKG1112E jobname: THE CHECKPOINT
small. RODM will not attempt to allocate storage for FUNCTION IS DISABLED.
data if the total amount of data in RODM exceeds the
amount that can be written to your checkpoint data Explanation
sets.
Message Variables perform the requested checkpoint function because
the checkpoint function is disabled for one of the
jobname
following reasons:
command. • CHECKPOINT_FUNCTION(NONE) was coded in the
nnn1 customization file. The sample customization file is
The number of data windows that cannot be EKGCUST.
allocated. • CHECKPOINT_FUNCTION(REQUEST) was coded in
nnn2 the customization file and RODM either cannot
The number of unused data windows. access the checkpoint data sets, was using a
translation or data window that cannot be
checkpointed, or one or more of the checkpoint data

sets were too small to set up the master window, the Operator response
first translation window, or the first data window.
• RODM detected an error during a previous
checkpoint request.
Message Variables Update the cell size and pool size parameters in the
jobname customization file. See the IBM Z NetView
The RODM job name specified in the MVS START Administration Reference for information on defining
command. the cell pools in the customization file.
EKG1115I jobname: THE TRANSLATION
System action WINDOW CHECKPOINT IS
RODM rejects this checkpoint request and continues COMPLETE.
processing.
Explanation
Operator response The Resource Object Data Manager (RODM) has
Notify the system programmer. completed a checkpoint of the translation windows.
The operator or a user application requested the
checkpoint.
Message Variables
Browse the system console log for messages
EKG5011I, EKG1100E, EKG1101E, EKG1102E, jobname
EKG1104E, EKG1105E, and EKG1106E. See these The RODM job name specified in the MVS START
messages for more information. command.
EKG1114I jobname: POOL_SIZE poolsize,
CELL_SIZE cellsize, System action
INCOMPATIBLE. NEW SIZES ARE RODM continues processing. Users can now resume
newpool AND newcell. user API requests.
EKG1116I jobname: NO MORE TRANSLATION
Explanation
WINDOW SEGMENTS ARE
The pool size value specified in the customization file AVAILABLE. nnn SEGMENTS HAVE
is not valid for one of the following reasons: BEEN ALLOCATED.
• The cellsize is too large for the poolsize.
Explanation
• The poolsize is too large.
Message Variables allocate a new segment of the translation window for
jobname one of the following reasons:
The Resource Object Data Manager (RODM) job • The space allocated for the translation-window
name specified in the MVS START command. checkpoint data set is insufficient. (See the
poolsize EKGTRAN DD statement in the RODM startup JCL.)
The pool size specified (in bytes). • The MAX_SEGMENT_NUM keyword from the
cellsize customization file has been exceeded. (The sample
The cell size specified (in bytes). customization file is EKGCUST.)
newpool • The virtual storage for RODM is unavailable.
The new pool size.
The most likely reason for this error is that your
newcell checkpoint data sets are too small. RODM will not
The new cell size. attempt to allocate storage for data if the total amount
of data in RODM exceeds the amount that can be
System action written to your checkpoint data sets.
The poolsize defaults to the new pool size, and cellsize Message Variables
defaults to the new cell size. RODM continues with the
defaulted values.

jobname • The space allocated for the data-window checkpoint
The RODM job name specified in the MVS START data sets is insufficient. (See the EKGD00x DD
command. statement in the RODM startup JCL.)
nnn • The MAX_WINDOW_NUM keyword from the
The total number of segments that have been customization file has been exceeded. (The sample
allocated. customization file is EKGCUST.)
• A data space cannot be created.
System action • Virtual storage for RODM has been exhausted.
RODM continues processing. Requests from user The most likely reason for this error is that your
applications requiring additional storage (for example, checkpoint data sets are too small. RODM will not
creating an object) might not be processed. attempt to allocate storage for data if the total
amount of data in RODM exceeds the amount that
Operator response can be written to your checkpoint data sets.
jobname
System programmer response The RODM job name specified in the MVS START
Verify that the MAX_SEGMENT_NUM setting in your command.
customization file is sufficient. Set this keyword to its nnn
maximum value because translation window segments The total number of data windows that have been
are allocated only when they are used. allocated.
Check and correct your EKGTRAN checkpoint data set
size. System action
If this error was generated because of your checkpoint RODM continues processing. Requests from user
data set size, disable the checkpoint function or applications requiring additional storage (for example,
ensure that your checkpoint data sets are large creating an object) might not be processed.
enough. To disable the checkpoint function, code
CHECKPOINT_FUNCTION(NONE) in the RODM Operator response
customization member. Optionally, you can also
comment out the checkpoint data sets in the RODM Notify the system programmer.
startup JCL (DD statements EKGMAST, EKGTRAN, and
EKGD00x). Note that disabling the checkpoint function System programmer response
also disables the warm start option.
Verify that the MAX_WINDOW_NUM setting in your
If the checkpoint function is enabled, ensure that your customization file is sufficient. IBM recommends
checkpoint data sets are large enough. See the setting this keyword to its maximum value because
EKGSI101 sample for information about calculating data windows are only allocated when they are
the proper size of the checkpoint data sets. actually used.
If you determine that this error is not related to your Check and correct your EKGD00x checkpoint data set
checkpoint data set size, or the MAX_SEGMENT_NUM sizes.
keyword, increase the region size for RODM.
If this error was generated because of your checkpoint
After performing any of the previous steps, you must data set size, you can avoid the error in the future by
restart RODM. disabling the checkpoint function, or by ensuring that
EKG1117I jobname: NO MORE DATA
WINDOWS ARE AVAILABLE. nnn To disable the checkpoint function, code
DATA WINDOWS HAVE BEEN CHECKPOINT_FUNCTION(NONE) in the RODM
ALLOCATED. customization member. Optionally, you can also
comment out the checkpoint data sets in the RODM
Explanation startup JCL (DD statements EKGMAST, EKGTRAN, and
EKGD00x). Note that disabling the checkpoint function
The Resource Object Data Manager (RODM) cannot also disables the warm start option.
allocate a data window for one of the following
reasons: If the checkpoint function is enabled, ensure that your
checkpoint data sets are large enough. See the

EKGSI101 sample for information about calculating Explanation
the proper size for your checkpoint data sets.
This is an informational message that is used in
If you determine that this error is not related to your conjunction with EKG1326D. This message is issued
checkpoint data set size, or the MAX_WINDOW_NUM when a termination is requested, but is not running
keyword, increase the region size for RODM. because of other active transactions.
After performing any of the previous steps, you must Message Variables
restart RODM.
jobname
EKG1118I jobname: THERE ARE uapi_number The RODM job name specified in the MVS START
UAPI REQUESTS AND command
asyn_number ASYNCHRONOUS uapi_number
REQUESTS AHEAD OF THE The number of synchronous requests to be
CHECKPOINT REQUEST. completed before the RODM termination request
can run.
Explanation asyn_number
This is an informational message that is used in The number of asynchronous requests to be
conjunction with EKG1326D. This message is issued completed before the RODM termination request
when a checkpoint is requested, but is not running can run.
because of other active transactions.
Messages EKG1330I, EKG1324I or EKG1325I and
jobname
EKG1326D accompany this message.
command
Operator response
uapi_number
The number of synchronous requests to be This message can be reissued if you decide to
completed before the RODM checkpoint request continue waiting with the reply to EKG1326D. When
can run. the message is reissued, if the number of requests
asyn_number ahead of the termination request does not decrease,
The number of asynchronous requests to be there can be a loop in a method. In this case, cancel
completed before the RODM checkpoint request the current transaction by replying to the EKG1326D
can run. message.
EKG1120I jobname: RODM WILL BE UNABLE
System action TO CHECKPOINT THE MASTER
WINDOW
Messages EKG1330I, EKG1324I or EKG1325I and
EKG1326D accompany this message.
Explanation
Operator response With the CHECKPOINT_FUNCTION(REQUEST) option
in use and during cold start initialization, RODM was
This message can be reissued if you decide to
unable to set up the master window for future
continue waiting with the reply to EKG1326D. When
checkpointing. Typical reasons are that the master
the message is reissued, if the number of requests
checkpoint data set was not defined or was too small.
ahead of the checkpoint request does not decrease,
there can be a loop in a method. In this case, cancel Message Variables
the current transaction by replying to the EKG1326D
jobname
message.
EKG1119I jobname: THERE ARE uapi_number command
UAPI REQUESTS AND
asyn_number ASYNCHRONOUS System action
REQUESTS AHEAD OF THE
TERMINATION REQUEST. RODM continues without the checkpoint function.

If the checkpoint function is required at all times jobname
during RODM operation, then code The RODM job name specified in the MVS START
CHECKPOINT_FUNCTION(REQUIRE) in the RODM command
customization member and restart RODM. You might nn
also want to increase the size of the master The number of the first data window for which the
checkpoint data set. See the EKGMAST DD statement problem occurred
in the RODM startup JCL.
EKG1121I jobname: RODM WILL BE UNABLE System action
TO CHECKPOINT TRANSLATION
If the window number is one, RODM continues without
WINDOW SEGMENT NUMBER nn
the checkpoint function. If the window number is
larger than one, RODM continues with the checkpoint
Explanation function until the identified data window is used, at
With the CHECKPOINT_FUNCTION(REQUEST) option which time message EKG1123I will be issued.
in use, RODM allocated a translation window segment
that, when ultimately used, cannot be checkpointed. System programmer response
Typical reasons are that the translation checkpoint
If the checkpoint function is required at all times
data set was not defined or was too small.
during RODM operation, then code
Message Variables CHECKPOINT_FUNCTION(REQUIRE) in the RODM
customization member and restart RODM. You might
jobname
also want to increase the size of the data window
checkpoint data sets. See the EKGDnnn DD
command
statements in the RODM startup JCL.
nn
The number of the first translation window EKG1123I jobname: THE CHECKPOINT
segment for which the problem occurred FUNCTION IS NOW DISABLED
If the window number is one, RODM continues without During cold start initialization with the
the checkpoint function. If the window number is CHECKPOINT_FUNCTION(REQUEST) or
larger than one, RODM continues with the checkpoint CHECKPOINT_FUNCTION(NONE) RODM
function until the identified translation window is used, customization option in use, RODM found that it will
at which time message EKG1123I will be issued. not be able to checkpoint the master window, first
translation window, or the first data window.
Alternatively, during operation with the
CHECKPOINT_FUNCTION(REQUEST) RODM
If the checkpoint function is required at all times customization option in use, RODM began to use a
during RODM operation, then code translation window or a data window that cannot be
CHECKPOINT_FUNCTION(REQUIRE) in the RODM checkpointed.
customization member and restart RODM. You might
Message Variables
also want to increase the size of the translation
checkpoint data set. See the EKGTRAN DD statement jobname
in the RODM startup JCL. The RODM job name specified in the MVS START
command
EKG1122I jobname: RODM WILL BE UNABLE
TO CHECKPOINT DATA WINDOW
NUMBER nn System action
RODM continues without the checkpoint function.
Explanation
With the CHECKPOINT_FUNCTION(REQUEST) option System programmer response
in use, RODM allocated a data window that, when If the checkpoint function is required at all times
ultimately used, cannot be checkpointed. Typical during RODM operation, then code
reasons are that the data window checkpoint data sets CHECKPOINT_FUNCTION(REQUIRE) in the RODM
were not defined or were too small. customization member and restart RODM. Additional

responses can include defining or increasing the size jobname
of one or more of the checkpoint data sets and The RODM job name specified in the MVS START
restarting RODM. See the EKGMAST, EKGTRAN, and command.
EKGDnnn DD statements in the RODM startup JCL. rodm
EKG1301E jobname: THERE ARE uapi_number The internal RODM name.
UAPI REQUESTS AND
asyn_number ASYNCHRONOUS System action
REQUESTS AHEAD OF THE
RODM checkpoints the master window, the translation
CHECKPOINT REQUEST.
window, and the data windows. RODM rejects all user
requests until it checkpoints both the master window
Explanation and translation window. After the translation window
This is an informational message to be used in has taken a checkpoint, the user API requests are
conjunction with EKG1326D. This message will get allowed while the data windows are taking a
issued when a checkpoint or termination is requested, checkpoint.
but is not running yet because of other transactions EKG1303I jobname: RODM rodm HAS
still being active. COMPLETED CHECKPOINTING.
Message Variables
Explanation
jobname
The RODM job name specified in the MVS START The Resource Object Data Manager (RODM) has
command. completed a checkpoint of the master, translation, and
uapi_number data windows.
The number of synchronous requests that need to Message Variables
be completed before RODM checkpoint or
termination request can run. jobname
asyn_number command.
The number of asynchronous requests that need to
be completed before RODM checkpoint or rodm
termination request can run. The internal RODM name.
Message EKG1330I, EKG1324I or EKG1325I and RODM continues normal processing.

EKG1326D accompany this message. EKG1304I jobname: THE CURRENT LOG FILE
HAS BEEN OVERWRITTEN.
Operator response
This message will get reissued if you decide to Explanation
continue waiting with the reply to EKG1326D. When The current log file has been overwritten by a
the message is reissued, if the number of requests Resource Object Data Manager (RODM) logging
ahead of the checkpoint request does not decrease, function because the current log file is at capacity and
there can be a loop in a method. In this case, cancel only one log file is provided.
the current transaction by replying to the EKG1326D
message. Message Variables
EKG1302I jobname: RODM rodm IS NOW jobname

CHECKPOINTING. The RODM job name specified in the MVS START
command.
Explanation
System action
The Resource Object Data Manager (RODM) is taking a
checkpoint as a result of a checkpoint request from RODM continues processing.
the operator or a user application. EKG1305I jobname: NO LOG RECORD IS
Message Variables LOGGED DUE TO A LOG FILE
FAILURE.

Explanation field
The RODM field name. Possible values are
An error condition was encountered when a log record
LastCheckPointID and LastAsyncError.
write request was attempted. Possible causes for the
error are: object
The name of the object.
• No log files are specified in the Resource Object Data
Manager (RODM) START job control language (JCL). reason
The reason code indicating the cause of the
• Only one log file is specified in the RODM START JCL problem.
and there was a failure when attempting to write to
that file.
System action
• Neither log file has been written.
RODM continues processing. The field does not
Message Variables contain current information because the field was not
jobname updated.
Analyze the appropriate RODM log data set to
System action determine the source of the error. See the IBM Z
RODM continues without error logging. NetView Troubleshooting Guide for information about
RODM log record formats.
Operator response EKG1307I jobname: RODM rodm CANNOT BE
Notify the system programmer. CHECKPOINTED AND WAS NOT
STOPPED.
Explanation
information about RODM log record formats and log You issued a MODIFY command with the Resource
file definition. Object Data Manager (RODM) or you issued an
application programming interface (API) request to
EKG1306I jobname: THE SYSTEM FIELD field end RODM with a checkpoint, but you did not provide
IN OBJECT object CANNOT BE checkpoint data sets in RODM. The checkpoint data
UPDATED, ERROR REASON CODE sets in the START job control language (JCL) or that
IS reason. you provided are being used by another user. RODM
cannot perform the checkpoint function.
The specified Resource Object Data Manager (RODM) jobname
system field cannot be updated. The required action The RODM job name specified in the MVS START
for the application programming interface (API) was command.
not completed successfully and a return code of 8 or
rodm
greater has been recorded for the transaction. A return
The internal RODM name.
code of 8 or greater causes RODM to attempt to
update the LastAsyncError field in the EKGUSER
object. This message is issued whenever the System action
LastAsyncError field cannot be updated in a multiple RODM continues processing.
use environment, or storage cannot be obtained. If
RODM runs out of storage, you receive this message
Operator response
for every asynchronous transaction task running in
RODM. Notify the system programmer.
Message Variables
jobname
The RODM job name specified in the MVS START Verify that the RODM START JCL contains the
command. checkpoint data sets. If the data sets are provided,
check the RODM procedure library or the MVS system

to see if another user is using the checkpoint data System action
sets.
The system continues without flushing.
EKG1310I jobname: THE LOG FLUSHING IS
COMPLETED. Operator response
Explanation
All buffered log records that had not yet been written System programmer response
to the Resource Object Data Manager (RODM) log file
have now been written (flushed) successfully to the Verify that the log file exists and is defined correctly.
log file. The flushing of log records has completed in See the MVS system console for messages.
response to a MODIFY LOGF command. EKG1313I jobname: THE PRIMARY LOG FILE
Message Variables IS NOW CLOSED.
jobname
Explanation
command. The Resource Object Data Manager (RODM) has closed
the current (primary) log file in response to a log
System action terminate or log switch MODIFY command. The
primary log file has been closed for one of the
The system continues processing. following reasons:
EKG1311I jobname: NO LOG FILE IS • The primary log file was open while there was an
CURRENTLY OPEN. attempt to end logging using the MODIFY command.
• The primary log file was current and a switch to the
Explanation secondary log file was requested using the MODIFY
The user has entered a LOGQ command or a MODIFY command. The secondary log file was opened
command to either flush the log buffer, switch the log successfully.
file, or end logging. The log switch is triggered by a Message Variables
LOGP or a LOGS command. The log file was closed
when these commands were issued, however, the jobname
LOGP and LOGS commands continue processing and The RODM job name specified in the MVS START
open their respective log files. command.
Message Variables
System action
jobname
RODM continues processing.
name specified in the MVS START command. EKG1314I jobname: THE SECONDARY LOG
FILE IS NOW CLOSED.
System action
Explanation
The Resource Object Data Manager (RODM) closed the
EKG1312I jobname: THE LOG FLUSHING HAS
current (secondary) log file while ending or switching
FAILED.
the log file. The secondary log file has been closed for
one of the following reasons:
Explanation
• The secondary log file was open while there was a
The flushing of log records has failed in response to a request to end logging using the MODIFY command.
MODIFY LOGF command because an error occurred
• The secondary log file was current and a switch to
while attempting to write to the log file.
the primary log file was requested using the MODIFY
Message Variables command. The primary log file was opened
successfully.
jobname
The Resource Object Data Manager (RODM) job Message Variables
name specified in the MVS START command.

jobname retcode
The RODM job name specified in the MVS START The return code returned from the MVS system
command. macro.
macro
System action The name of the MVS system macro.
System action
EKG1315I jobname: THE PRIMARY LOG FILE
IS NOW CURRENT. RODM ends.
The primary log file is now the current log file because Notify the system programmer.
of either a MODIFY command or an end-of-file EKG1318E jobname: THE QUIESCENCE TASK
condition occurring on the previous (secondary) file. CANNOT BE CREATED. RETURN
Message Variables CODE retcode IS RETURNED FROM
SYSTEM MACRO macro.
jobname
Explanation
System action create the quiescence task.
RODM continues processing. Message Variables
EKG1316I jobname: THE SECONDARY LOG jobname

FILE IS NOW CURRENT. The RODM job name specified in the MVS START
command.
Explanation retcode
The return code returned from the MVS system
The secondary log file is now the current log file macro.
because of either a MODIFY command or an end-of-
file condition occurring on the previous (primary) file. macro
The name of the MVS system macro.
Message Variables
jobname System action
The RODM job name specified in the MVS START RODM ends.
command.
Operator response
System action
EKG1317E jobname: THE I/O TASK CANNOT System programmer response
BE CREATED. RETURN CODE
If the cause of the failure cannot be determined from
retcode IS RETURNED FROM
the return code given in the message, contact IBM
SYSTEM MACRO macro.
Software Support.
Explanation EKG1319E jobname: THE METHOD TASK

CANNOT BE CREATED. RETURN
CODE retcode IS RETURNED FROM
create the I/O task.
SYSTEM MACRO macro.
Message Variables
jobname Explanation
The RODM job name specified in the MVS START The Resource Object Data Manager (RODM) cannot
command. create the method task.
Message Variables

jobname retcode
command. macro.
retcode macro
The return code returned from the MVS system The name of the MVS system macro.
macro.
macro System action
The name of the MVS system macro. RODM ends.

RODM ends. Notify the system programmer.
Operator response EKG1322E jobname: THE CONSOLE TASK

Notify the system programmer. CODE retcode IS RETURNED FROM
EKG1320E jobname: TRANSACTION TASK SYSTEM MACRO macro.
CODE IS retcode FROM SYSTEM Explanation
MACRO macro. The Resource Object Data Manager (RODM) cannot
create the console task.
Explanation
Message Variables
create the transaction task. jobname
Message Variables command.
jobname retcode
command. macro.
retcode macro
The return code returned from the MVS system The name of the MVS system macro.
macro.
macro System action
The name of the MVS system macro. RODM ends.

Operator response EKG1323E jobname: THE ALLOCATION TASK

Notify the system programmer. CODE retcode IS RETURNED FROM
EKG1321E jobname: THE TIMER TASK SYSTEM MACRO macro.
CODE retcode IS RETURNED FROM Explanation
SYSTEM MACRO macro. The Resource Object Data Manager (RODM) cannot
create the allocation task.
Explanation
Message Variables
create the timer task. jobname
Message Variables command.
jobname retcode
command. macro.

macro Message Variables
jobname
System action command.
RODM ends.
System action
Operator response Message EKG1326D accompanies this message.
Notify the system programmer. Depending on the reply to EKG1326D, RODM does one
of the following:
EKG1324I jobname: THE WAIT PERIOD HAS
EXPIRED FOR THE CHECKPOINT • Repeats the termination wait
REQUEST, BUT THERE ARE STILL • Ends all transactions and proceeds with an
ACTIVE TRANSACTIONS. unconditional end
• Cancels the terminate request
Explanation
The wait period for allowing transactions to complete Operator response
before the checkpoint commences has expired. Some Notify the system programmer.
transaction activity is continuing after expiration of this
timer interval.
Message Variables
Investigate all active transactions and reply to
jobname message EKG1326D.
name specified in the MVS START command. EKG1326D jobname: ENTER '1' TO PERFORM
WAIT AGAIN, '2' TO END
CURRENT TRANSACTION, '3' TO
System action
CANCEL REQUEST.
Message EKG1326D accompanies this message.
Depending on the reply to EKG1326D, RODM does one Explanation
of the following:
The message is generated as a result of message
• Repeats the checkpoint wait EKG1324I for a checkpoint request or message
• Ends all transactions and proceeds with an EKG1325I for a termination request. The wait period
unconditional checkpoint for checkpoint or termination has expired. The system
programmer is prompted for one of three actions.
• Cancels the checkpoint request
Message Variables
Operator response jobname
Notify the system programmer. The Resource Object Data Manager (RODM) job
System action
Investigate all active transactions and reply to
message EKG1326D. RODM asks the system programmer to take one of the
following actions:
EKG1325I jobname: THE WAIT PERIOD HAS
EXPIRED FOR THE TERMINATE • Enter 1 to repeat the checkpoint or termination wait
REQUEST, BUT THERE ARE STILL • Enter 2 to end the current transaction. If there are
ACTIVE TRANSACTIONS. no other active transactions, the checkpoint or
termination will proceed. If there are other active
Explanation transactions, the wait for the termination or
checkpoint is repeated for the remaining active
The wait period for allowing transactions to complete transactions.
before the Resource Object Data Manager (RODM)
• Enter 3 to cancel the checkpoint or termination
ends has expired. Some transaction activity is
request.
continuing after expiration of this timer interval.

Notify the system programmer. jobname
System programmer response command.
retcode
Investigate all active transactions and reply
appropriately.
macro.
EKG1327I jobname: THE CHECKPOINT macro
REQUEST IS ABORTED, AND THE The name of the MVS system macro.
CHECKPOINT FILES REMAIN
UNMODIFIED.
System action
Explanation RODM ends.
A system programmer entered 3 in response to

Operator response
message EKG1326D. The Resource Object Data
Manager (RODM) cancels the checkpoint request. Notify the system programmer.
Message Variables
jobname
The RODM job name specified in the MVS START If the cause of the failure cannot be determined from
command. the return code given in the message, contact IBM
Software Support.
System action EKG1900I jobname: RODM rodm
RODM cancels the checkpoint request. The checkpoint INITIALIZATION IS COMPLETE
files are not modified. WITH env.
EKG1328I jobname: THE TERMINATE Explanation

REQUEST IS ABORTED, AND
RODM IS CONTINUING NORMAL The Resource Object Data Manager (RODM) has
PROCESSING. successfully initialized.
Message Variables
Explanation
jobname
A system programmer entered 3 in response to The RODM job name specified in the MVS START
message EKG1326D. The Resource Object Data command.
Manager (RODM) cancels the termination request. rodm
Message Variables The internal RODM name.
jobname env
The RODM job name specified in the MVS START Indicates the specific runtime support with which
command. RODM was installed. This value is either “PL/I” or
“LE/370”.
System action
System action
RODM cancels the termination request and continues
normal processing. RODM has successfully completed initialization and is
ready to process user transactions or operator
EKG1329E jobname: THE QUIESCENCE WAIT MODIFY commands.
TASK CANNOT BE CREATED.
RETURN CODE retcode IS EKG1901I jobname: NO INIT METHOD IS
RETURNED FROM SYSTEM MACRO SPECIFIED.
macro.
Explanation
Explanation No INIT method is specified in the MVS START
The Resource Object Data Manager (RODM) cannot command or in the Resource Object Data Manager
create the quiescence wait task. (RODM) START job control language (JCL). This

message is only informational, because INIT methods • The load module cannot be found in the load module
are not required. library.
Message Variables • The load module is not executable.
jobname Message Variables

The RODM job name specified in the MVS START jobname
command. The RODM job name specified in the MVS START
command.
System action module
RODM continues initialization without executing an The name of the load module that cannot be
INIT method. loaded.
EKG1902E jobname: THE INIT METHOD

System action
CANNOT BE FOUND.
RODM ends.
Explanation
Operator response
The INIT method specified in the MVS START
command or in the Resource Object Data Manager Notify the system programmer.
(RODM) START job control language (JCL) cannot be
found in the method library. Therefore, RODM cannot System programmer response
execute the INIT method.
Ensure that the module exists in the RODM load
Message Variables module libraries and can be executed. Restart RODM.
jobname
EKG1905I jobname: A WARM START IS IN
PROGRESS.
command.
Explanation
System action
The Resource Object Data Manager (RODM) is
RODM ends.
currently being warm started. If the TYPE parameter
was not specified in the MVS START command or in
Operator response the RODM START job control language (JCL), the
Notify the system programmer. default start type (warm start) is assumed. Otherwise,
the TYPE parameter had explicitly specified a warm
start.
Message Variables
If an INIT method is desired, do the following:
jobname
1. Ensure that the INIT method name exists in the
desired method library.
command.
2. Ensure that the desired method library is specified
in the RODM START JCL. System action
3. Restart RODM.
RODM proceeds to warm start.
more information on the START JCL and specifying EKG1906I jobname: THE RODM NAME IS
INIT methods. systemname.
EKG1903E jobname: LOAD MODULE module Explanation

CANNOT BE LOADED INTO THE
COMMON STORAGE AREA. You did not specify the NAME parameter in the MVS
START command or in the Resource Object Data
Manager (RODM) START job control language (JCL).
Explanation
RODM uses the system name.
Message Variables
load the specified load module into the common
storage area for one of the following reasons:

command.
systemname • For the START command:
The RODM START JCL procedure name or the If a customization parameter is not specified and
identifier name. default member EKGCUST cannot be read (or not
found), RODM uses the default values for all the
System action customization parameters and an EKG1922D
message appears following this message.
RODM continues initializing.
If a customization parameter is specified and the
Operator response member name specified in this parameter cannot be
read, RODM uses the default values for all the
See the NetView online help for information about customization parameters and an EKG1922D
specifying RODM names. message appears following this message.
EKG1907I jobname: THE CUSTOMIZATION • For the MODIFY command:
FILE filename CANNOT BE READ. If RELOAD or 'RELOAD,MEMBER=' is specified
without a member name, RODM reads default
Explanation member EKGCUST. If RODM cannot read EKGCUST,
The Resource Object Data Manager (RODM) cannot RODM does not use the default values for all
read (or open) the customization file member specified customization parameters and an EKG1911I
in the RODM START job control language (JCL) or message appears following this message.
START command, or use the default member If 'RELOAD,MEMBER=' is specified with a member
EKGCUST, for one of the following reasons: name, RODM reads this member. If RODM cannot
• The RODM customization file data definition (DD) read this member, RODM does not use the default
name EKGCUST is not specified in the RODM START values for all customization parameters and an
JCL. EKG1911I message appears following this message.
• The RODM customization file is a sequential file, but

Operator response
it must be a partitioned data set.
• RODM cannot open the customization file specified Notify the system programmer.
in the ddname EKGCUST in the RODM START JCL.
• RODM cannot read the customization file. For the System programmer response
START command, the member name is specified by Ensure that the member specified in the START job
the CUST parameter. For the MODIFY command, the control language (JCL), START command, MODIFY
member name is specified in the RELOAD command, or default member EKGCUST exists in the
parameter. If the member name is not specified in file specified by the EKGCUST DD statement in the
either of these commands, the default member START job control language (JCL).
name EKGCUST is used.
EKG1908E jobname: THE START TYPE IS NOT
Note: The EKGCUST ddname must be specified in VALID.
the RODM START JCL and the EKGCUST member
must be in the partitioned data set. Otherwise,
Explanation
RODM uses its internal values.
• The customization file is empty. The value of the TYPE parameter specified in the MVS
START command or in the Resource Object Data
• The record length is not 80. Manager (RODM) START job control language (JCL) is
• The record format is not fixed block (FB). not valid. The start type must be either WARM, W,
COLD, C, or null (for the default of WARM).
Message Variables
Message Variables
jobname
The RODM job name specified in the MVS START jobname
filename command.
The member name of the customization file.

System action STATCELL
Output the statistics information of windows and
RODM ends.
segments usage.
Enter the MVS START command with a valid start type jobname
or notify the system programmer. The RODM job name specified in the MVS START
command.
System programmer response commandparm
The name of the MODIFY command parameter.
Verify that the start type in the RODM START JCL is
valid. See the NetView online help for information on
System action
the START command. See IBM Z NetView Installation:
Getting Started for more information on the START RODM continues processing.
JCL. Restart RODM.
EKG1911I jobname: THE MVS MODIFY
EKG1909I jobname: THE MVS MODIFY COMMAND commandparm HAS
COMMAND commandparm IS FAILED.
SUCCESSFUL.
Explanation
Explanation
The Resource Object Data Manager (RODM) has failed
The Resource Object Data Manager (RODM) has to process the function of the MODIFY command. The
successfully processed the MVS MODIFY command. possible MODIFY command parameters are:
The possible MODIFY command parameters are:
STATAPI
RELOAD Output the application programming interface
Reload the customization values during RODM (API) statistics to the RODM log as a type 8 record.
processing. STATCELL
STATAPI Output the statistics information of windows and
Write the application programming interface (API) segments usage.
statistics to the RODM log as a type 8 record. RELOAD
Message Variables Reload the customization values during RODM
processing.
jobname
The RODM job name specified in the MVS START Message Variables
command. jobname
commandparm The RODM job name specified in the MVS START
The name of the MODIFY command parameter. command.
commandparm
System action The name of the MODIFY command parameter.
System action
COMMAND commandparm IS RODM continues without processing the MODIFY
ACCEPTED. command.
The Resource Object Data Manager (RODM) has Notify the system programmer.
successfully processed the function of the MODIFY
command. The possible MODIFY command System programmer response
parameters are:
STATAPI the source of the error. See the IBM Z NetView
Output the application programming interface Troubleshooting Guide for information about RODM log
(API) statistics. record formats. See the NetView online help for
information about the MODIFY command.

EKG1912E jobname: THE RODM rodm IS Operator response
ALREADY ACTIVE. Notify the system programmer.
Explanation
The Resource Object Data Manager (RODM) with the Check the INIT method for the cause associated with
specified name is already active. Two RODMs with the
the specified return and reason code.
same name cannot run at the same time.
• If the INIT method is supplied by IBM, see the IBM Z
Message Variables NetView Resource Object Data Manager and GMFHS
jobname Programmer's Guide for information about the
The RODM job name specified in the MVS START meaning of INIT method return code and reason
command. code values.
rodm • If the INIT method is a load function INIT method
The internal RODM name. check the output listing for details about the error.
The SYSPRINT DD statement in the RODM start-up
System action JCL defines the name of the output listing data set.
• If the INIT method is not supplied by IBM, check the
RODM ends.
INIT method for the cause associated with the
specified return code and reason code.
Operator response
Start RODM using a different RODM name, or notify the the source of the error. See the IBM Z NetView
system programmer. Troubleshooting Guide for information about RODM log
record formats.
EKG1914E jobname: THE RODM SUBSYSTEM
Ensure that an acceptable internal RODM name is CANNOT BE LOCATED IN THE MVS
selected. All internal RODM names must be unique SYSTEM.
within the MVS system. See the NetView online help
for information on the START command. See IBM Z Explanation
NetView Installation: Getting Started for more
information about the START job control language The required subsystem name EKGX cannot be found
(JCL). in the MVS subsystem name table.
EKG1913E jobname: ERROR RETURN CODE = Message Variables

retcode AND REASON CODE = jobname
reason FROM THE INIT METHOD. The Resource Object Data Manager (RODM) job
Explanation
The INIT method encountered an error and set the System action
return code and the reason code to the specified RODM ends.
values.
jobname Notify the system programmer.
name specified in the MVS START command. System programmer response
retcode Add the subsystem name entry, EKGX, to the
The INIT method return code. IEFSSNxx member of SYS1.PARMLIB. Re-IPL MVS and
reason restart RODM. See IBM Z NetView Installation: Getting
The INIT method reason code. Started for information about installing a RODM in
MVS.
System action EKG1915E jobname: THE MVS CROSS
RODM ends. MEMORY ENVIRONMENT CANNOT
BE ESTABLISHED.

Explanation jobname
command.
establish the required MVS cross-memory
environment. The possible causes are: rodm
• No system-wide linkage index is available.
EKG1918D jobname: RODM rodm WILL COLD
• An error occurred when setting up the MVS cross-
START. ENTER '1' TO CONTINUE
memory environment.
OR '2' TO TERMINATE.
Message Variables
jobname Explanation
The RODM job name specified in the MVS START You requested that the specified Resource Object Data
command. Manager (RODM) be cold started. You must confirm
your request.
System action
Message Variables
RODM ends.
jobname
Operator response command.
Notify the system programmer. rodm
If there are no system-wide linkage indexes available, System action
you must extend the number of system linkage RODM requests the operator's confirmation for a cold
indexes and re-IPL the MVS system. Restart RODM. start.
EKG1916I jobname: RODM rodm
TERMINATION IS IN PROGRESS. Operator response
Enter 1 to continue or 2 to end RODM. RODM does not
Explanation continue until a valid response is entered.
The Resource Object Data Manager (RODM) is ending Note: When performing a warm start on RODM, ensure
because of a termination request from the operator or that the checkpoint data sets and the associated
user application. Master and Translation data sets are kept together. If
the data sets are not together, RODM does not
Message Variables
initialize.
jobname
The RODM job name specified in the MVS START EKG1919I jobname: RODM rodm IS ALREADY
command. PROCESSING A PREVIOUS
REQUEST.
rodm
Explanation
System action The Resource Object Data Manager (RODM) is not

available to accept a MODIFY command. RODM is
RODM ends. processing a prior operator request (MODIFY
EKG1917I jobname: RODM rodm command) or API request.
TERMINATION IS COMPLETE. Message Variables
jobname
Explanation
The Resource Object Data Manager (RODM) has command.
ended. rodm
Message Variables The internal RODM name.

RODM ignores the MODIFY command and continues If the reply is 2, correct the customization parameters
processing the previous request. in error. See the IBM Z NetView Administration
Reference for information about the customization file
Operator response parameters.
Retry the MODIFY command after RODM replies to the EKG1924I jobname: THE CUSTOMIZATION
previous request. FILE CANNOT BE OPENED.
EKG1920I jobname: THE COUNTERS FOR API

Explanation
STATISTICS HAVE BEEN
CLEARED. The Resource Object Data Manager (RODM) cannot
open the customization file because the customization
Explanation file data definition (DD) name is not specified in the
RODM START job control language (JCL).
The counters for temporary application programming
interface statistics have been cleared after being Message Variables
written to the type 8 log record. jobname
Message Variables The RODM job name specified in the MVS START
command.
jobname
System action
RODM continues the initialization process without the
System programmer response customization file and uses default values for each
parameter.
Flush the RODM log and print it using the RODM log
formatter.
Operator response
EKG1922D jobname: DEFAULTS ARE USED Notify the system programmer.
FOR SOME CUSTOMIZATION
VALUES. ENTER '1' TO CONTINUE
OR '2' TO TERMINATE. System programmer response
If a customization file is desired, ensure that the
Explanation desired customization file is specified for EKGCUST in
the RODM START JCL. See the IBM Z NetView
The Resource Object Data Manager (RODM) has Administration Reference for information on defining
detected an error in the customization file. Message the customization file.
EKG1953I has been placed on the console for each
customization parameter in error. You must choose to EKG1925E jobname: JCL EXEC STATEMENT
either continue initialization or to end. PARAMETER FOR THE AUTOMATIC
RESTART OPTION IS NOT VALID
Message Variables
jobname Explanation
command. The value supplied for the positional RODM parameter
for automatic restart manager (ARM) registration was
not valid.
System action
Message Variables
RODM requests operator confirmation to either
continue or end. jobname
The name assigned to RODM when it was started.
Operator response
System action
Enter 1 to continue or 2 to end RODM. RODM does not
continue until a valid response is entered. RODM ends, instead of completing initialization.

Correct the parameter and restart RODM.

EKG1926E jobname: JCL EXEC STATEMENT System action
PARAMETER FOR THE SYMBOL RODM does not start.
SUBSTITUTION OPTION IS NOT
VALID
Operator response
The value supplied for the positional RODM parameter
for symbol substitution was not valid. System programmer response
Message Variables Change the RODM name. See the NetView online help
for the format of RODM name.
jobname
The name assigned to RODM when it was started. EKG1929E jobname: THE RODM NAME IS TOO
LONG
System action
Explanation
RODM ends, instead of completing initialization.
The Resource Object Data Manager (RODM) name
specified is greater than eight characters.
Message Variables
Correct the parameter and restart RODM.
jobname
EKG1927E jobname: JCL EXEC STATEMENT The RODM job name specified in the MVS START
PARAMETER FOR THE ROUTE command.
CODE OPTION IS NOT VALID
System action
Explanation
RODM does not start.
The value supplied for the positional RODM parameter
for route code was not valid.
Operator response
Message Variables
jobname
The name assigned to RODM when it was started. System programmer response
System action Change the RODM name. See the NetView online help
for the format of RODM name.
RODM ends, instead of completing initialization.
EKG1930E jobname: OPERATOR COMMAND
ENVIRONMENT CANNOT BE
SETUP. RETURN CODE IS retcode
Correct the parameter and restart RODM. FROM SYSTEM MACRO macro.
EKG1928E jobname: THE RODM NAME
rodmname IS NOT VALID Explanation
Explanation establish the operator command environment for the
operator MVS MODIFY command.
The Resource Object Data Manager (RODM) name
specified is not valid. Message Variables
Message Variables jobname
jobname command.
name specified in the MVS START command. retcode
rodmname macro.
The input RODM name.
macro

System action programmer. See the NetView online help for
information on the MVS START command.
RODM ends.

Operator response
Verify that the RODM INIT method name is correct in
the RODM START job control language (JCL). See the
EKG1931E jobname: MAIN TASK RECOVERY IBM Z NetView Installation: Getting Started for
ROUTINE CANNOT BE CREATED. information about the RODM job.
RETURN CODE IS retcode FROM
EKG1933I jobname: RODM rodm CANNOT
SYSTEM MACRO macro.
ACCEPT THE MVS STOP
COMMAND.
Explanation
The Resource Object Data Manager (RODM) cannot Explanation
create the error recovery routine for the main task.
You entered an MVS STOP command for the Resource
Message Variables Object Data Manager (RODM), but the RODM does not
allow the MVS STOP command.
jobname
The RODM job name specified in the MVS START Message Variables
command.
jobname
retcode The RODM job name specified in the MVS START
The return code returned from the MVS system command.
macro.
rodm
macro The internal RODM name.
System action
System action
RODM rejects the MVS STOP command and continues
RODM ends. processing.
Operator response
COMMAND commandparm IS NOT
Notify the system programmer. RECOGNIZED.
EKG1932E jobname: THE INIT METHOD NAME
IS TOO LONG. Explanation
You entered an incorrect parameter in the MODIFY
The length of the RODM INIT method name specified Message Variables
in the Resource Object Data Manager (RODM) START jobname
command or in the RODM START job control language The Resource Object Data Manager (RODM) job
(JCL) is greater than eight characters. name specified in the MVS START command.
Message Variables commandparm
jobname The incorrect parameter specified in the MODIFY
The RODM job name specified in the MVS START command.
command.
System action
System action RODM rejects the MODIFY command and continues
RODM ends. processing.
Enter the MVS START command with the correct Enter the RODM MVS MODIFY command again with
RODM INIT method name or notify the system correct parameters. Acceptable RODM MODIFY
command parameters are:

• CHKPT jobname
• LOGF The RODM job name specified in the MVS START
command.
• LOGP
class
• LOGS The name of the security class.
• LOGT
• RELOAD System action
• STATAPI RODM ends.
• STATCELL
• TERM Operator response
See the NetView online help for more information on Notify the system programmer.
the MVS MODIFY command parameters.
EKG1935E jobname: THE SECURITY CLASS
class IS NOT ACTIVE. Verify that the correct security class name is specified
in the SEC_CLASS parameter of the customization file.
Verify that the correct security class name is defined
Explanation
and activated in the security system. See the IBM Z
During Resource Object Data Manager (RODM) NetView Administration Reference for information
initialization, RODM detects that the specified security about the customization file and the security system
class is not active. setup for RODM.
Message Variables EKG1937I jobname: THE SECURITY SYSTEM
jobname IS NOT ACTIVE.
command. Explanation
class During Resource Object Data Manager (RODM)
The name of the security class. initialization, RODM detects that there is no active
security system available.
RODM ends. jobname
System action
System programmer response RODM continues to initialize. Because the security
Verify that the correct security class name is specified system is not active, RODM does not perform authority
in the SEC_CLASS parameter of the customization file. checking. Users obtain the highest authority level
Verify that the correct security class name is defined during API connection time.
and activated in the security system. See the IBM Z
NetView Administration Reference for information Operator response
about the customization file and the security system Determine if the security system is required for RODM
setup for RODM. operation. If so, notify the system programmer.
EKG1936E jobname: THE SECURITY CLASS
class IS NOT DEFINED. System programmer response
End RODM. Verify that the security system is installed
Explanation and activated. Restart RODM.
During Resource Object Data Manager (RODM) EKG1938I jobname: THE SECURITY
initialization, RODM detects that the specified security RESOURCE resource IS NOT
class is not defined. DEFINED IN THE SECURITY CLASS
Message Variables class.

Explanation class
The security resource name specified in the
customization file.
customization file is not defined in the security class
for the security system.
System action
Message Variables
RODM ends.
jobname
Operator response
resource Notify the system programmer.
customization file. System programmer response
class Define the required security resources under the
The security class name specified in the security class specified and restart RODM. See
customization file. message EKG1938I for more information. See the IBM
Z NetView Administration Reference for information
System action about customization file security resource name
selection and the security system setup for RODM.
RODM continues checking other security resources. If
none of the security resources specified in the EKG1940I jobname: WARNING RETURN
customization file or the default security resource CODE = retcode AND REASON
name derived by the RODM name are defined under CODE = reason FROM THE INIT
the specific security class, users cannot connect to METHOD.
RODM after the RODM initialization completes.
Otherwise, only users defined in security resources Explanation
can perform the associated services.
The INIT method returned the specified warning
return code and reason code.
Operator response
Message Variables
jobname
System programmer response The Resource Object Data Manager (RODM) job
Check the security system for the specific security
retcode
class and the security resources under this specific
The value of the return code.
security class. See the IBM Z NetView Administration
Reference for information about customization file reason
security resource name selection and the security The value of the reason code.
system setup for a RODM.
System action
EKG1939E jobname: NONE OF THE SIX RODM
SECURITY RESOURCES ARE RODM continues processing.
DEFINED UNDER THE SECURITY
CLASS class. Operator response
Explanation
The Resource Object Data Manager (RODM) security System programmer response
resources are not defined in the security class. A
minimum of one and a maximum of six RODM security If the INIT method is supplied by IBM, see the IBM Z
resources can be defined for a security class in the NetView Resource Object Data Manager and GMFHS
security system. Programmer's Guide for the specified return code and
reason code. If the INIT method is not supplied by
Message Variables IBM, check the INIT method for the cause associated
jobname with the specified return code and reason code.
The RODM job name specified in the MVS START EKG1941E jobname: THE RODM START JCL
command. STEP LIBRARY CONTAINS AN

UNAUTHORIZED data set. RODM customization file because the value specified is not
IS TERMINATING. valid.
Message Variables
Explanation
jobname
Abend S047 occurred because a data set in the START The RODM job name specified in the MVS START
JCL is not authorized program facility (APF) command.
authorized.
custparm
Message Variables The parameter in the customization file containing
a value that is not valid.
jobname
The Resource Object Data Manager (RODM) job defvalue
name specified in the MVS START command. The default value that RODM uses.

Ensure that all data sets in the STEPLIB are APF RODM uses the specified default value and continues
authorized. to initialize. Message EKG1922D is displayed when
RODM has completed analyzing the customization file.
EKG1952I jobname: THE CUSTOMIZATION
FILE PARAMETER custparm IS
Operator response
NOT VALID.
Explanation
The Resource Object Data Manager (RODM) does not
recognize the specified parameter in the customization Determine whether to end RODM and reply to
file. EKG1922D. See the IBM Z NetView Administration
Reference for the valid customization parameter
Message Variables
values. Restart RODM.
jobname
The RODM job name specified in the MVS START EKG1954I jobname: CUSTOMIZATION
command. PARAMETER custparm HAS AN
INCORRECT VALUE AND IS
custparm IGNORED.
The unrecognized parameter in the customization
file.
Explanation
System action During reload processing, the Resource Object Data

Manager (RODM) detected that the value specified in
RODM continues processing. the customization parameter is not valid. The original
value for this parameter remains unchanged.
Operator response
Message Variables
jobname
System programmer response command.
Correct the specified parameter in the customization custparm
file. See the IBM Z NetView Administration Reference The customization parameter in error.
for information about customization parameters.
EKG1953I jobname: CUSTOMIZATION System action
PARAMETER custparm IS NOT RODM ignores this parameter and continues
VALID. THE DEFAULT VALUE processing the remaining parameters.
defvalue IS USED.
Operator response
Explanation
The Resource Object Data Manager (RODM) uses the
default value for the specified parameter in the

Check the customization file member specified in the The operator has the option of using the parameters as
MODIFY command RELOAD,MEMBER= or EKGCUST if they are, or terminating RODM by replying to message
no member was specified in the MODIFY command. EKG1922D.
See the IBM Z NetView Administration Reference for
the syntax of the customization parameters. Change System programmer response
the syntax of the customization parameter and use the
MODIFY RELOAD command to reload the If necessary, correct the error in the customization
customization parameters if necessary. member.
EKG1955I jobname: '/*' APPEARS IN A EKG1960E jobname: THE RODM MODULE

COMMENT. A COMMENT module CANNOT BE LOADED.
DELIMITER MAY BE MISSING
Explanation
Explanation The Resource Object Data Manager (RODM) cannot
The customization member processing found a load the specified module into memory for one of
comment start delimiter within a comment. these reasons:
Message Variables • The load module cannot be found in the RODM load
module library.
jobname
The name assigned to RODM when it was started. • The load module is not executable.
• Virtual storage is unavailable.
Customization member processing continues. jobname
The operator has the option of using the parameters as module
they are, or terminating RODM by replying to message The load module that cannot be loaded.
EKG1922D.
System action
System programmer response RODM ends.
If necessary, correct the error in the customization
member. Operator response
EKG1956I jobname: CUSTOMIZATION Notify the system programmer.
PARAMETER PROCESSING ENDED
WHILE IN A COMMENT. A System programmer response
COMMENT DELIMITER MAY BE
MISSING Ensure that the module exists in the RODM load
module libraries and can be executed. Ensure that the
region size is adequate. Restart RODM.
Explanation
EKG1961E jobname: LOAD FAILED FOR
A comment start delimiter (/*) was found without a
MODULE modname
corresponding end delimiter (*/) at the time the
customization member processing completed.
Explanation
Message Variables
RODM was unable to load the identified module.
jobname
The name assigned to RODM when it was started. Message Variables
jobname
System action The name assigned to RODM when it was started.
Customization member processing continues. modname
The name of the module RODM was trying to load.

Dependent upon which module RODM was trying to RODM processing continues.
load.
Operator response
Dependent upon the action RODM takes following the
EKG1964E jobname: ARM DEREGISTRATION
load failure. Notify the system programmer.
FAILED WITH RETURN CODE
retcode, REASON CODE rescode
Ensure that required modules are available to RODM. Explanation
EKG1962E jobname: ARM REGISTRATION During termination processing, RODM attempted to
FAILED WITH RETURN CODE deregister from automatic restart manager (ARM) and
retcode, REASON CODE rescode was unsuccessful.
Message Variables
Explanation
jobname
RODM attempted to register with automatic restart The name assigned to RODM when it was started.
manager (ARM) and was unsuccessful.
retcode
Message Variables The IXCARM macro return code.
jobname rescode
The name assigned to RODM when it was started. The IXCARM macro reason code.
retcode
The IXCARM macro return code. System action
rescode RODM termination continues.
The IXCARM macro reason code.
System action
RODM processing continues.
EKG1973E jobname: AN ERROR OCCURRED
WHILE CREATING RODM SYSTEM
System programmer response CLASS class.
If no ARM policy was active and restart capability is
desired, activate an ARM policy and restart RODM. Explanation
An error occurred while creating the specified
EKG1963E jobname: ARM READY FAILED Resource Object Data Manager (RODM) system class.
WITH RETURN CODE retcode,
Message Variables
REASON CODE rescode
jobname
Explanation The RODM job name specified in the MVS START
command.
RODM was unsuccessful in notifying automatic restart
class
manager (ARM) that it was ready.
The class name that cannot be created.
Message Variables
The name assigned to RODM when it was started. RODM ends.
retcode
The IXCARM macro return code. Operator response
rescode Notify the system programmer.
The IXCARM macro reason code.

System programmer response class
The class name containing the field that cannot be
created.
Troubleshooting Guide for more information about
RODM log record formats. System action
EKG1974E jobname: AN ERROR OCCURRED RODM ends.

OBJECT object IN CLASS class. Operator response
Explanation
An error occurred while creating the specified System programmer response
Resource Object Data Manager (RODM) system object Analyze the appropriate RODM log file to determine
in the specified class. the source of the error. See the IBM Z NetView
Message Variables Troubleshooting Guide for more information about
RODM log record formats.
jobname
The RODM job name specified in the MVS START EKG1976E jobname: AN ERROR OCCURRED
command. WHILE INITIALIZING RODM
object SYSTEM FIELD fieldname IN
The object name that cannot be created. CLASS classname.
class
The class name containing the object that cannot Explanation
be created. An error occurred while initializing the specified
system class field.
RODM ends. jobname
Operator response name specified in the MVS START command.
Notify the system programmer. fieldname
The field name of the RODM class.
System programmer response classname
The class name containing the field that cannot be
created.
Troubleshooting Guide for more information about
RODM log record formats. System action
EKG1975E jobname: AN ERROR OCCURRED RODM ends.

FIELD field IN CLASS class. Operator response
Explanation
An error occurred while creating the specified System programmer response
Resource Object Data Manager (RODM) system field in Analyze the appropriate RODM log file to determine
the specified class. the source of the error. See the IBM Z NetView
Message Variables Troubleshooting Guide for information about RODM log
record formats.
jobname
The RODM job name specified in the MVS START EKG1981E jobname: THE QUIESCENCE TASK
command. HAS TERMINATED.
field
The field name that cannot be created.

The Resource Object Data Manager (RODM) main task The Resource Object Data Manager (RODM) main task
detects that the quiescence subtask has abnormally detects that the method subtask has abnormally
ended because of an error. ended because of an error.
jobname jobname
The RODM job name specified in the MVS START The RODM job name specified in the MVS START
command. command.

RODM ends. RODM ends.


Analyze the appropriate RODM log file to determine Analyze the appropriate RODM log file to determine
the source of the error. See the IBM Z NetView the source of the error. See the IBM Z NetView
Troubleshooting Guide for information about RODM log Troubleshooting Guide for information about RODM log
record formats. record formats.
EKG1982E jobname: THE I/O TASK HAS EKG1984I jobname: THE TRANSACTION
TERMINATED. TASK HAS TERMINATED.
detects that the input/output subtask has abnormally detected that a transaction subtask has abnormally
ended because of an error. ended because of an error.
jobname jobname
command. command.

RODM ends. RODM continues processing. If all of the transaction
tasks abend, RODM ends. The number of transaction
Operator response tasks is specified in the customization file.

Operator response

Troubleshooting Guide for information about RODM log Analyze the appropriate RODM log file to determine
record formats. the source of the error. See the IBM Z NetView
EKG1983E jobname: THE METHOD TASK HAS record formats.
TERMINATED.
EKG1986I jobname: THE MESSAGE TASK
HAS TERMINATED.

detects the message subtask has abnormally ended detects that the console subtask has abnormally
because of an error. ended because of an error.
jobname jobname
command. command.

All PL/I error messages are not written to the console RODM ends.
or to the RODM log file. All RODM log records
generated by UAPI return code 12 and reason code Operator response
212 are not written to the log file. RODM continues
processing without this subtask. Notify the system programmer.
Notify the system programmer. Analyze the appropriate RODM log file to determine
record formats.
the source of the error. See the IBM Z NetView EKG1989E jobname: THE ALLOCATION TASK
Troubleshooting Guide for information about RODM log HAS TERMINATED.
record formats.
Explanation
EKG1987E jobname: THE TIMER TASK HAS
TERMINATED. The Resource Object Data Manager (RODM) main task
detects that the allocation subtask has abnormally
ended because of an error.
Explanation
Message Variables
The Resource Object Data Manager (RODM) main task
detects that the timer subtask has abnormally ended jobname
because of an error. The RODM job name specified in the MVS START
command.
Message Variables
command. RODM ends.
Notify the system programmer. Analyze the appropriate RODM log file to determine
record formats.
EKG1990E jobname: THE PL/I COMMON
Troubleshooting Guide for information about RODM log LIBRARY DOES NOT EXIST.
record formats.
EKG1988E jobname: THE CONSOLE TASK HAS
TERMINATED.

Explanation information about runtime library requirements for
RODM.
The Resource Object Data Manager (RODM) requires
the runtime library corresponding to the level of PL/I EKG1995E jobname: MODULE NAME module
or LE/370 which was used to install RODM. This library ABENDS WITH ABEND CODE
cannot be located. abcode - reason AT OFFSET offset.
Message Variables
Explanation
jobname
The RODM job name specified in the MVS START The Resource Object Data Manager (RODM) abended
command. during its initialization.
Message Variables
System action
jobname
RODM ends. The RODM job name specified in the MVS START
command.
Operator response module
Notify the system programmer. The module name where the abnormal ending
occurred.
System programmer response abcode
The abend code that was returned.
Ensure that the runtime library is installed and
reason
correctly specified in the RODM START job control
The reason code that was returned.
language (JCL) or in the MVS link-list. See IBM Z
NetView Installation: Getting Started for information offset
about runtime library requirements for RODM. The offset from the entry point to the abend
position.
EKG1991E jobname: EXECUTION
ENVIRONMENT SUPPORT NOT
System action
INSTALLED
RODM ends.
Explanation
Operator response
The Resource Object Data Manager (RODM) was not
installed with either the V2R3 PL/I or LE/370 feature. Notify the system programmer.
One of these features must be installed to support
RODM. If V2R3 PL/I is chosen, you must also install System programmer response
the V2R1 C/370 feature if you have any methods
written in C or plan to use GMFHS. Analyze the appropriate module to determine the
source of the error. See the IBM Z NetView
Message Variables Troubleshooting Guide for information about the abend
jobname that occurred during initialization.
The RODM job name specified in the MVS START EKG1996E jobname: A SEVERE ERROR HAS
command.
CAUSED RODM TO ABNORMALLY
TERMINATE.
System action
RODM ends. Explanation
A severe error occurred during Resource Object Data
Operator response Manager (RODM) initialization.
jobname
Install the RODM language environment support command.
feature which corresponds to the level of PL/I or
LE/370 on your system. See IBM Z NetView System action
Installation: Configuring Additional Components for
RODM ends.

Notify the system programmer. See the IBM Z NetView Administration Reference for
information about the security system setup for
System programmer response RODM.
Analyze the appropriate RODM log file to determine EKG2000I jobname: CONNECT REQUEST
the source of the error. See the IBM Z NetView FROM APPLICATION applname IS
Troubleshooting Guide for information about abnormal REJECTED WITH RC = retcode AND
RODM endings. RS = rescode.
EKG1998I THE AUTHORITY CHECKING FOR

Explanation
THE RODM IS BYPASSED.
RODM cannot process the CONNECT request from the
Explanation applname.
The user specified *TSTRODM as the security resource This message is also issued when the RODM loader
class name in the RODM customization file to bypass runs and RODM security is not active, because the
any authority checking for the Resource Object Data loader will first attempt to connect with a blank user
Manager (RODM). ID. The connect request is rejected with RC=8 and
RS=127. The loader will then automatically attempt to
connect with a non-blank user ID. In this case, this
System action
message can be ignored.
RODM continues initialization. RODM does not perform
Message Variables
any authority checking because of the security
resource class name specified in the RODM jobname
customization file. Users gain the highest authority The RODM job name specified in the MVS START
level at connection. command.
applname
System programmer response The name of the application that connects to
RODM.
If authority checking is desired, specify another
security resource class name. See the IBM Z NetView retcode
Administration Reference for more details on how to The RODM return code.
define the RODM security class. rescode
EKG1999I jobname: THE SECURITY SYSTEM The RODM reason code.
IS NOT INSTALLED.
System action
Explanation The request fails and RODM continues.
The security system is not installed. All users who
connect to the Resource Object Data Manager (RODM) Operator response
obtain the highest authority level. Notify the system programmer.
Message Variables
The RODM job name specified in the MVS START Review the return and reason codes provided by
command. RODM. If the failure is caused by SAF definition,
correct the definition. If the failure is caused by a
System action RODM internal error, contact IBM Software Support.
RODM continues initialization. Because the security EKG2300E jobname: THE PL/I ENVIRONMENT
system is not installed, RODM does not perform any CANNOT BE INITIALIZED.
authority checking. Users gain the highest authority
level at connection time. Explanation
initialize the PL/I environment for the
CONCURRENT_USERS and ASYNC_TASK parameters
as specified in the customization file.

jobname identifier
The RODM job name specified in the MVS START A number representing the particular environment.
command.
System action
System action
The number of concurrent users is lowered by one.
RODM ends.
Operator response
Operator response
Reinitialization of an environment for the RODM user
Determine whether there is a virtual storage shortage, API is usually attempted after an abend. Normally, the
or if the REGION parameter in the START job control reinitialization is successful. This message indicates
language (JCL) is too small to hold the environment. that the attempt failed.
If the identifier in the message is equal to twice the
information on PLI_ISA, CONCURRENT_USERS, and
number of allowable concurrent users, a storage
ASYNC_TASKS in the customization file.
overlay might have occurred in the area allocated for
EKG2302E jobname: THE MESSAGE TASK the environment. RODM continues to run, but no
CANNOT BE CREATED. RETURN longer attempts to use this environment. This can
CODE retcode IS RETURNED FROM indicate some other problem, so you might want to
SYSTEM MACRO macro. take a dump and restart RODM when convenient.
If the identifier in the message is less than twice the
Explanation number of allowable concurrent users, you can
The Resource Object Data Manager (RODM) cannot continue to allow RODM to run with a reduced number
create the message task. of concurrent users, unless there are not enough
concurrent users left to support your system. Look in
Message Variables the RODM log to see if there are any other instances of
jobname this message. This will help you determine if more
The RODM job name specified in the MVS START than one environment for the RODM user API has
command. become unavailable.
retcode EKG2304I jobname: THE command_name

The return code returned from the MVS system COMMAND IS COMPLETE.
macro.
macro Explanation
The name of the MVS system macro. A RODM command completed.
Message Variables
System action
jobname
RODM ends.
command.
Operator response
command_name
Notify the system programmer. The name of the command that was issued.
EKG2303E ONE ENVIRONMENT FOR THE
RODM USER API COULD NOT BE System action
REINITIALIZED. THE IDENTIFIER RODM continues.
IS identifier
EKG2305I jobname: A RODM DUMP WAS
Explanation PREVENTED BECAUSE THE RODM
DUMP LIMIT IS EXCEEDED FOR
An attempt was made to reinitialize an environment APPROXIMATELY THE NEXT
for the RODM user API, but it was not successful. num_of_minutes MINUTES.

The DUMP_LIMIT specified in the customization RODM ends.
member has been exceeded. No more dumps for
RODM will be taken until num_of_minutes passes, or a Operator response
DMPRESET command is issued.
Message Variables
Increase the region size in the RODM START JCL and
command.
restart RODM.
num_of_minutes
The number of minutes remaining until the next EKG5002E jobname: DATA WINDOW TABLE
dump is allowed to be scheduled. CANNOT BE INITIALIZED.
RETURN CODE IS retcode FROM
SYSTEM MACRO macro.
System action
RODM continues. Explanation
Operator response
initialize or create the data window table. Possible
To enable more dumps, issue the DMPRESET causes are:
command using the MVS modify command. (F
• The region size specified in the START job control
jobname,DMPRESET)
language (JCL) is too small.
• Virtual storage is not sufficient.
Message Variables
Investigate the prior dumps to determine possible
error sources. Modify the DUMP_LIMIT keyword in the jobname
customization member if you wish to allow more The RODM job name specified in the MVS START
dumps per time interval while debugging a problem. command.
EKG5001E jobname: TRANSLATION WINDOW retcode
TABLE CANNOT BE INITIALIZED. The return code returned from the MVS system
RETURN CODE IS retcode FROM macro.
SYSTEM MACRO macro. macro
Explanation
The Resource Object Data Manager (RODM) cannot System action
initialize or create the translation window table. RODM ends.
Possible causes are:
• The region size specified in the START job control Operator response
language (JCL) is too small. Notify the system programmer.
• Virtual storage is not sufficient.
jobname Increase the region size in the RODM START JCL and
The RODM job name specified in the MVS START restart RODM.
command. EKG5003E jobname: DATA SPACE TABLE
retcode CANNOT BE INITIALIZED.
The return code returned from the MVS system RETURN CODE IS retcode FROM
macro. SYSTEM MACRO macro.
macro

Explanation macro
initialize or create the data space table. Possible
causes are: System action
• The region size specified in the START job control RODM ends.
language (JCL) is too small.
• Virtual storage is not sufficient. Operator response

command. Increase the region size in the RODM START JCL and
restart RODM.
retcode
The return code returned from the MVS system EKG5005E jobname: RETURN CODE IS retcode
macro. FROM SYSTEM MACRO macro. TCB
macro TOKEN UNAVAILABLE FOR FIRST
The name of the MVS system macro. DATA SPACE.

RODM ends. The Resource Object Data Manager (RODM) cannot
obtain the TCB token when creating the first data
space.
Operator response
Message Variables
jobname
System programmer response The RODM job name specified in the MVS START
command.
Increase the region size in the RODM START JCL and
restart RODM. retcode
EKG5004E jobname: FIRST DATA SPACE macro.
CANNOT BE CREATED. RETURN macro
CODE IS retcode FROM SYSTEM The name of the MVS system macro.
MACRO macro.
System action
Explanation
RODM ends.
create the first data space. Possible causes are:
Operator response
• The region size specified in the START job control
language (JCL) is too small. Notify the system programmer.
• Virtual storage is not sufficient. EKG5007E jobname: RODM CANNOT BE

• You have the IEFUSI macro installed on your STARTED AS A BATCH JOB.
system. The IEFUSI macro is not supported for use
with RODM. Explanation
Message Variables The Resource Object Data Manager (RODM) cannot be
started as a batch job. Therefore, RODM does not
jobname initialize.
retcode jobname
The return code returned from the MVS system The RODM job name specified in the MVS START
macro. command.

RODM ends. The Resource Object Data Manager (RODM) detects
that an operator MVS FORCE command has been
Operator response entered.
Restart RODM as a started task. See the NetView Message Variables

online help for more information on the START jobname
EKG5008I jobname: THE FILE SPECIFIED BY command.
DDNAME ddname IS TOO SMALL
FOR A DATA WINDOW. System action
RODM ends.
Explanation
EKG5010E jobname: RODM IS TERMINATING
The data set specified by ddname is too small. Each DUE TO CATASTROPHIC ERROR.
checkpoint data set must be large enough to contain at
least one 16 MB data window.
Explanation
Message Variables
An abnormal error occurred within the Resource
jobname Object Data Manager (RODM) after it had been
The Resource Object Data Manager (RODM) job successfully initialized.
Message Variables
ddname
The name of the file. jobname
command.
System action
RODM skips this file and continues searching for the System action
next one.
RODM ends.
Operator response
Check and correct your EKGD00x checkpoint data set
sizes. Notify the system programmer.
If this error was generated because of your checkpoint System programmer response
data set size, you can avoid the error in the future by
disabling the checkpoint function, or by ensuring that Analyze the appropriate RODM log file to determine
your checkpoint data sets are large enough. the source of the error:
To disable the checkpoint function, code 1. Verify the RODM start job control language (JCL).
CHECKPOINT_FUNCTION(NONE) in the customization 2. Verify the attributes of the checkpoint data sets.
file. The checkpoint function cannot be disabled if you
3. Increase the region size for RODM if it is too small.
attempt to warm start RODM. If you attempt to warm
start RODM with CHECKPOINT_FUNCTION(NONE) 4. Verify the cell-pool size.
coded in the customization file, RODM issues message 5. Verify that all the RODM modules are located in the
EKG1953I and attempts to set the checkpoint function STEPLIB data set.
to the default value
6. Verify that the checkpoint data sets are used for the
CHECKPOINT_FUNCTION(REQUEST).
RODM warm start.
If the checkpoint function is enabled, ensure that your
checkpoint data sets are large enough. See the EKG5011I jobname: THE NUMBER OF
EKGSI101 sample for information about calculating CHECKPOINT FILES USED BY
the proper size for your checkpoint data sets. RODM IS numberparm.
Restart RODM.
Explanation
EKG5009E jobname: RODM IS FORCED BY This number specifies the number of EKGDnnn
THE OPERATOR. checkpoint files coded in the RODM start procedure.

If the checkpoint function is enabled, this number is WITH CHECKPOINT OF RODM
one less than the number shown in the EKGDnnn file rodm.
name in message IEC161I. If the checkpoint function
is not enabled (CHECKPOINT_FUNCTION(NONE) is Explanation
coded in the customization file), the number is zero
(0). The number is also 0 if the checkpoint function is The specified user requests that the Resource Object
enabled, but RODM was unable to access one or more Data Manager (RODM) take a checkpoint and end.
of the checkpoint files (DD names EKGMAST, Message Variables
EKGTRAN, or EKGDnnn).
jobname
Message Variables The RODM job name specified in the MVS START
jobname command.
The Resource Object Data Manager (RODM) job userid
name specified in the MVS START command. The user requesting the termination with
numberparm checkpoint.
The number of EKGDnnn checkpoint files coded in rodm
the RODM start procedure. The internal RODM name.

RODM continues. RODM checkpoints the master window, the translation
window, and the data windows. RODM ends.
EKG7003I jobname: THE USER userid HAS
REQUESTED A CHECKPOINT OF EKG7005I jobname: THE USER userid HAS
RODM rodm. REQUESTED A TERMINATION
WITHOUT CHECKPOINT OF RODM
Explanation rodm.
The specified user requests a checkpoint of the
Explanation
Resource Object Data Manager (RODM) data cache.
The specified user requests that the Resource Object
Message Variables
Data Manager (RODM) end immediately without taking
jobname a checkpoint.
Message Variables
command.
userid jobname
The user application ID requesting checkpoint. The RODM job name specified in the MVS START
command.
rodm
The internal RODM name. userid
The user application ID requesting the termination
without checkpoint.
System action
rodm
RODM checkpoints the master window, the translation The internal RODM name.
window, and the data windows. RODM rejects all user
API requests until both the master-window and
System action
translation-window checkpoints. After the translation
window has taken a checkpoint, message EKG1115I is RODM ends.
issued and user API requests are allowed while the
data windows are taking a checkpoint. EKG8001E A CLOSE FAILURE OCCURRED ON
THE FILE FOR DDNAME ddname.
Explanation
information about the RODM checkpoint function. The MVS CLOSE macro failed to close the specified
file.
EKG7004I jobname: THE USER userid HAS
Message Variables
REQUESTED A TERMINATION

ddname ddname
The name on the data definition statement. The name on the data definition statement.

If this message is received on the console, a return If this message is received on the console, a return
code of 12 is returned and processing stops. code of 12 is returned and processing stops.
Otherwise, a return code of 8 is returned and Otherwise, a return code of 8 is returned and
processing stops. The system attempts to close all processing stops.
other files to ensure a clean termination. The loader
ends. Operator response
Operator response
Determine from the accompanying system messages
where the failure occurred and correct the problem.
EKG8004E THE RECORD LENGTH OF length IS
NOT VALID FOR DDNAME ddname.
EKG8002E THE LENGTH length OF THE LIST
OF ALTERNATE DDNAMES IS NOT Explanation
VALID.
The specified data control block logical record length
(LRECL) is not valid for the specified data set.
Explanation
Message Variables
The list of alternate DD statement names has a length
of zero, or the length is not a multiple of 16. length
The logical record length of the data control block.
Message Variables
ddname
length The name of the data set being opened.
The length of the DD statement name list.
System action
System action
If this message is received on the console, a return
If this message is received on the console, a return code of 12 is returned and processing stops.
code of 12 is returned and processing stops. Otherwise, a return code of 8 is returned and
Otherwise, a return code of 8 is returned and processing stops.
processing stops.
Operator response
Operator response
Determine the correct LRECL for the data set and
Ensure that the length of the alternate DD statement reallocate the data set. See IBM Z NetView Installation:
name list is not 0 and is a multiple of 16. See IBM Z Configuring Graphical Components for information on
NetView Resource Object Data Manager and GMFHS reallocating data sets using CNMSJ004.
Programmer's Guide for more information.
EKG8005E THE RECORD FORMAT IS NOT
EKG8003E AN OPEN FAILURE OCCURRED ON VALID FOR THE DDNAME ddname.
Explanation
Explanation
The data control block record format (RECFM) is not
The MVS OPEN macro cannot open the specified file. valid for this data set.

ddname System action
The name of the data set being opened.
code of 12 is returned and processing stops.
System action Otherwise, a return code of 8 is returned and
If this message is received on the console, a return processing stops.
Otherwise, a return code of 8 is returned and Operator response
processing stops.
Operator response
EKG8008E THE MEMBER membername WAS
Determine the correct RECFM for the data set and NOT FOUND IN THE PDS FOR
reallocate the data set. See IBM Z NetView Installation: DDNAME ddname.
Configuring Graphical Components for information on
reallocating data sets using CNMSJ004.
Explanation
EKG8006E A READ FAILURE OCCURRED ON
The member cannot be located in the specified file.
Message Variables
Explanation membername
There is a failure in an attempt to read a record from The name of the member that cannot be found.
the specified data set. ddname
The name of the partitioned data set that was
Message Variables
searched.
ddname
The name of the data set that was being read. System action
System action
If this message is received on the console, a return Otherwise, a return code of 8 is returned and
code of 12 is returned and processing stops. processing stops.
Otherwise, a return code of 8 is returned and
processing stops. Operator response
Operator response
Determine if the member exists in the specified
partitioned data set (PDS). If it does not, create a PDS
Determine from the accompanying system messages or refer to a PDS that contains the member.
EKG8009E THE OBJECT INDEPENDENT
EKG8007E A WRITE FAILURE OCCURRED ON METHOD methodname FAILED TO
THE FILE FOR DDNAME ddname. START. REFER TO RODM RETURN/
REASON CODE return/reasoncode.
Explanation
Explanation
There is a failure in an attempt to write a record to the
specified data set. The Resource Object Data Manager (RODM) failed to
invoke the specified object-independent method.
Message Variables
Message Variables
ddname
The name of the data set that was being written.

methodname ddname
The object-independent method that cannot be The name on the data definition statement.
invoked.
return/reasoncode System action
The return or reason code from RODM. A return code of 8 is returned and the RODM load
function stops processing data.
System action
The message is issued to the operator's console with a System programmer response
return code of 12 and processing stops. Determine from the accompanying system messages
why the DEB is not valid and correct the problem.
Operator response
EKG8012E A PERMANENT I/O ERROR
Notify the system programmer. OCCURRED DURING THE
DIRECTORY SEARCH OF THE FILE
System programmer response FOR DDNAME ddname.
Determine from the RODM return or reason code in the
message where the failure occurred and correct the Explanation
problem. See IBM Z NetView Resource Object Data During a directory search of the file, a permanent I/O
Manager and GMFHS Programmer's Guide for the error occurred.
RODM return and reason codes.
Message Variables
EKG8010E INSUFFICIENT VIRTUAL
STORAGE IS AVAILABLE WHEN ddname
SEARCHING THE DIRECTORY OF The name on the data definition statement.
System action
Explanation A return code of 8 is returned and processing stops.
Insufficient virtual storage was available when a
search was performed on the directory of the specified System programmer response
file. Determine from the accompanying system messages
Message Variables where the I/O error occurred and correct the problem.
ddname EKG8050W EXPECTED PARAMETER COLD OR
The name on the data definition statement. WARM NOT SPECIFIED AS START
PARAMETER ON JOB
System action INVOCATION. COLD IS ASSUMED
AND PROCESSING CONTINUES.
A return code of 8 is returned and processing stops.
Explanation
When the Resource Object Data Manager (RODM) load
Determine from the accompanying system messages utility is invoked as an RODM initialization method, a
why there is not enough storage and correct the parameter is passed indicating whether a cold or warm
problem. start is invoked.
EKG8011E THE DATA EXTENT BLOCK WAS
NOT VALID WHEN SEARCHING System action
THE DIRECTORY OF THE FILE FOR If this parameter is not supplied or the value is not
DDNAME ddname. valid, and the RODM load utility is invoked, cold is
assumed and processing continues.
Explanation
A search of the directory of the file and the data extent System programmer response
block (DEB) was not valid. Verify whether the correct parameter is specified. If
Message Variables the problem persists, contact IBM Software Support.

EKG8101E THE PARAMETER TABLE NAME IS System action
REQUIRED IN THE CONTROL Processing continues. When the RODM load utility
TABLE, BUT IT IS NOT FOUND. disconnects from the RODM, all prior applications that
were connected to the RODM with your user
Explanation application ID are disconnected.
The parameter mapping table name is not found when
the control table is searched. System programmer response
This message is a warning that more than one user
System action application is requesting RODM transactions from the
If the table is not supplied and the Resource Object same user application ID. While RODM allows multiple
Data Manager (RODM) load function is invoked, a connections for a given user application ID, it is your
return code of 8 is issued and the RODM load function responsibility to ensure the integrity of the user
stops processing. application ID environment. See IBM Z NetView
Programmer's Guide for more information about RODM
System programmer response connections and user application IDs.
Determine if the table name was specified in the
EKG8171E AN EXPECTED KEYWORD WAS
control table. If not, specify the table name. The
NOT SUPPLIED.
control file exists as partitioned data set (PDS)
member EKGCTABL in data definition (DD) EKGLUTB.
Explanation
EKG8102E THE NAME OF THE INSTALL
METHOD TABLE IS REQUIRED IN A keyword is missing from the input parameter list.
THE CONTROL TABLE, BUT IT IS
NOT FOUND. System action
Explanation
The specified installation method table name is not System programmer response
found when the control table is searched. Correct the input parameter list.
System action EKG8172E A KEYWORD VALUE IS NOT

SUPPLIED FOR THE KEYWORD
If the table name is not supplied and the Resource keyword.
Object Data Manager (RODM) load function is invoked,
a return code of 8 is issued and processing ends.
Explanation
System programmer response A keyword value is missing on the input parameter list
for the specified keyword.
Determine if the table name was specified in the
control table. If not, specify the table name. The Message Variables
control file exists as partitioned data set (PDS) keyword
member EKGCTABL in data definition (DD) EKGLUTB. The input keyword for which the value is missing.
EKG8103I LOADER HAS RECONNECTED TO
RODM. System action
Explanation
A previous Resource Object Data Manager (RODM) System programmer response
load utility request or a previous user application had Determine which keyword is missing a value and
already successfully connected to RODM using your correct the input parameter list.
current user application ID and remains connected to
RODM. The RODM load utility has now successfully EKG8173E THE MAXIMUM LENGTH length IS
connected to RODM using the same user application EXCEEDED FOR KEYWORD
ID. keyword.

The length of the input keyword is greater than the Determine from the Resource Object Data Manager
maximum valid length of a keyword. (RODM) message why the parameter list is incomplete.
Correct the input parameter list.
Message Variables
EKG8176E THE KEYWORD OR KEYWORD
length
VALUE IS MISSING FOR
The maximum length of a keyword.
parameter.
keyword
The input keyword with the incorrect length.
Explanation
System action A keyword or keyword value is missing from the

parameter list.
Message Variables
System programmer response parameter
The parameter that is missing a keyword or a
Determine which keyword length is not valid and
keyword value.
correct the input parameter list.
EKG8174E THE MAXIMUM LENGTH length IS System action
EXCEEDED FOR KEYWORD VALUE
keyword. A return code of 8 is returned and processing stops.
The length of the input keyword is greater than the Determine from the accompanying system messages
maximum valid length of a keyword. which keyword or keyword value is missing and
correct the problem.
Message Variables
EKG8177W THE PARAMETER MAPPING TABLE
length table IS OUT OF SEQUENCE. THE
The maximum length of a keyword. DEFAULT default IS IGNORED.
keyword
The input keyword value that was too long. Explanation
The order of records in the parameter table is not
System action valid.
A return code of 8 is returned and processing stops. Message Variables
System programmer response table

The name of the parameter mapping table.
Determine from the Resource Object Data Manager
default
(RODM) message which keyword value length is not
The keyword default value that was found out of
valid. Correct the input parameter list.
sequence in the parameter mapping table.
EKG8175E THE PARAMETER LIST IS NOT
COMPLETE. System action
A return code of 4 is returned and processing
Explanation continues.
Additional keywords and their associated values are
expected, but the end of the input is reached. System programmer response
Determine from the accompanying system message
System action which default value is out of sequence. Validate the
A return code of 8 is returned and processing stops. parameter mapping table sequence by checking the
sequence. The sequence is: KEYWORD, KEYWORD
ABBREVIATION, KEYWORD VALUE, KEYWORD VALUE
ABBREVIATION, KEYWORD DEFAULT.

EKG8178W THE PARAMETER MAPPING TABLE EKG8180E THE KEYWORD VALUE keyword IS
table IS OUT OF SEQUENCE. THE NOT VALID.
KEYWORD VALUE keyword IS
IGNORED. Explanation
The specified keyword value is not valid. The default
Explanation
value from the parameter mapping table is used.
The order of records in the parameter mapping table is
Message Variables
not valid.
keyword
Message Variables
The input keyword value or a passed parameter by
table a module invocation.
keyword System action
The keyword value record that was found out of A return code of 8 is returned and processing stops.
sequence in the parameter mapping table.

System action
Correct the input keyword value.
continues. EKG8181E AN ERROR OCCURRED IN THE
PARAMETER MAPPING TABLE
System programmer response table. THE MISSING INTERNAL
PROCESSING KEYWORD IS
Determine from the accompanying system messages keyword.
which keyword value record is out of sequence and
validate the parameter mapping table. The sequence
Explanation
is: KEYWORD, KEYWORD ABBREVIATION, KEYWORD
VALUE, KEYWORD VALUE ABBREVIATION, KEYWORD The required internal processing keyword has not
DEFAULT, KEYWORD. been set. An error occurs in the parameter mapping
table.
EKG8179W THE PARAMETER MAPPING TABLE
table HAS A DEFAULT VALUE FOR Message Variables
A REQUIRED KEYWORD keyword. table
THE DEFAULT VALUE IS IGNORED. The name of the parameter mapping table.
keyword
Explanation
The name of the internal processing keyword.
The keyword is required and does not require a default
value. System action
Message Variables A return code of 8 is returned and processing stops.
table
The name of the parameter mapping table. System programmer response
keyword Determine from the Resource Object Data Manager
The keyword that was present in the parameter (RODM) message which internal processing keyword is
mapping table. missing and add it to the parameter mapping table.
EKG8182E THE REQUIRED KEYWORD
System action
keyword IS NOT SPECIFIED.
continues. Explanation
The specified keyword is required and is not available.
Message Variables
Delete the default value record from the parameter
mapping table. keyword
The name of the missing keyword.

A return code of 8 is returned and processing stops. Determine from the Resource Object Data Manager
(RODM) message which keyword value is not valid.
System programmer response Correct the input parameter list.
Determine from the Resource Object Data Manager EKG8185E AN ERROR OCCURRED IN THE
(RODM) message which required keyword is missing. PARAMETER MAPPING TABLE
Correct the input parameter list. table. THE INTERNAL KEYWORD
VALUE keyword IS NOT VALID.
EKG8183E AN ERROR OCCURRED IN THE
PARAMETER MAPPING TABLE
Explanation
table THE REQUIRED DEFAULT
VALUE FOR keyword IS MISSING. The specified internal keyword value in the parameter
mapping table is not valid.
A required default value was not available in the table
parameter mapping table. The name of the parameter mapping table.
Message Variables keyword
The name of the keyword value that is not valid in
table
the parameter mapping table.
keyword
System action
The name of the keyword that is missing a default
value. A return code of 8 is returned and processing stops.

A return code of 8 is returned and processing stops. Notify the system programmer.

Determine from the Resource Object Data Manager Determine from the Resource Object Data Manager
(RODM) message which default value is missing. Add (RODM) message which keyword value is not valid and
the missing value to the parameter mapping table or correct the parameter mapping table.
specify a valid keyword value on the input parameter
list. EKG8186E PARAMETER LIST KEYWORD
keyword IS NOT VALID.
EKG8184E THE INPUT KEYWORD VALUE
keyword IS NOT VALID. Explanation
The parameter list keyword specified is not valid.
Explanation
Message Variables
The specified keyword value is not valid. The input
keyword value does not have an equivalent entry in the keyword
parameter mapping table. The keyword in error.
Message Variables
System action
keyword
The name of the input keyword value that is not A return code of 8 is returned and processing stops.
valid.
System action Correct the input keyword.
A return code of 8 is returned and processing stops. EKG8187E THE KEYWORD keyword IS
DUPLICATED IN THE INPUT
PARAMETER LIST.

The input parameter list contains more than one When reading the syntax within a file, a shift-in
occurrence of the keyword. character was encountered, but shift-out to double-
byte character set (DBCS) was not.
Message Variables
keyword System action
The input keyword that appears more than once on
the input parameter list. A return code of 4 is returned and processing
continues.
System action
Correct the input syntax.
System programmer response EKG8204E PROCESSING SYNTAX IN FILE file
TERMINATED DUE TO ERROR.
Correct the input parameter list.
EKG8201W THE NUMBER OF TOKENS IN THE Explanation
STATEMENT EXCEEDS THE
MAXIMUM. The processing syntax contains an error and was
ended.
The number of tokens given in the input syntax is file
greater than the allowed maximum. The maximum The name of the file that contains the syntax in
number of tokens allowed is 10. error.

A return code of 4 is returned and processing A return code of 8 or greater is returned.
continues.
Correct the syntax. See IBM Z NetView Resource Object
Correct the input syntax. Data Manager and GMFHS Programmer's Guide for
more information about syntax.
EKG8202W AN UNEXPECTED END OF THE
INPUT SYNTAX FILE file EKG8205W INCOMPLETE DATA FOR keyword
OCCURRED. OCCURRED.
The syntax within the named file is not complete when For the syntax keyword, more data is required but
the end of the file is reached. none was supplied.
file keyword
The name of the file containing the input syntax. The keyword for the data that is incomplete.

A return code of 4 is returned and processing A return code of 4 is returned and processing
continues. continues.

Correct the input syntax. Correct the syntax. If you need help correcting the
syntax, see the NetView online help.
EKG8203W THE START OF THE DBCS STRING
IS NOT INDICATED.

EKG8206W THE SYNTAX PRECEDING THE System programmer response
keyword KEYWORD IS NOT VALID. Correct the syntax.
Explanation EKG8210W THE KEYWORD keyword IS

ALREADY SPECIFIED.
The syntax preceding the specified keyword is not
valid.
Explanation
Message Variables
The named keyword has already been specified in the
keyword input data.
The keyword for the syntax that is not valid.
Message Variables

The keyword that is specified.
continues.
System action
Operator response A return code of 4 is returned and processing

continues.
Correct the syntax.
Correct the syntax. If you need help correcting the
syntax, see the NetView online help. EKG8211W THE PUBLIC AND PRIVATE
KEYWORDS ARE NOT
EKG8207W A VALID MODIFIER VALUE IS COMPATIBLE.
REQUIRED FOR THE ATTRIBUTE
VALUE.
Explanation
Explanation A field can only be public or private, not both.
The type of modification to the attribute value must be

System action
stated correctly.
System action continues.

continues.
Remove one of the keywords so the field is defined as
System programmer response either PUBLIC or PRIVATE.
Set the modifier to the desired value. EKG8212W THE ATTRIBUTE DEFINITION LIST
IS STILL ACTIVE.
EKG8208W A SEMI-COLON IS EXPECTED
FOLLOWING keyword.
Explanation
Explanation The attribute definition list is still being processed, and

must not be called again before processing is
A semicolon is expected as an indicator of the end of a complete.
token, but is not found.
keyword A return code of 4 is returned and processing
The keyword that is missing a semicolon. continues.

A return code of 4 is returned and processing Correct the input data so that the attribute definition
continues. list is not called again before processing is complete.

EKG8213W A VALID STATEMENT IS NOT System programmer response
ACTIVE FOR THE KEYWORD Correct the attribute name structure.
keyword.
EKG8216W A PARENTHESIS MISMATCH HAS
Explanation OCCURRED.
For the specified keyword, the appropriate processing

Explanation
has not begun.
The parentheses have not been set correctly. An
Message Variables
opening or closing parenthesis is missing.
keyword
The keyword for the statement that is not active. System action
System action
continues.
continues. System programmer response
Find the mismatch and correct the problem.
EKG8217W THE VALUE FOR KEYWORD
Correct the input data so that the appropriate
keyword IS NOT VALID OR IS
processing is called for the specified keyword.
MISSING.
EKG8214W THE QUALIFIED NAME SHOULD
NOT APPEAR IN THE ATTRIBUTE Explanation
DEFINITION LIST.
The given keyword must have a value associated with
it. This value is either not valid or missing.
Explanation
Message Variables
The attribute name is the same as the qualified name.
The qualified name cannot be specified as an attribute keyword
name. The keyword whose value is missing or not valid.

A return code of 4 is returned and processing A return code of 4 is returned and processing
continues. continues.

Correct the attribute name. See IBM Z NetView Find the specified assignment and set the correct
Resource Object Data Manager and GMFHS number of occurrences.
Programmer's Guide for more information about
EKG8218W THIS ASSIGNMENT SYMBOL
attribute names.
symbol APPEARS MORE THAN
EKG8215W THE INITIAL ATTRIBUTE VALUE ONCE.
FOR THE INIT KEYWORD IS
MISSING. Explanation
The assignment symbol must only appear one time.
Explanation
Message Variables
The INIT keyword must precede an attribute initial
value, but cannot be found. symbol
The symbol is either '=' or '::='.
System action
System action
continues. A return code of 4 is returned and processing
continues.

System programmer response keyword
The keyword that is missing.
Find the specified assignment symbols and set the
symbol only once.
System action
EKG8219W THIS ASSIGNMENT SYMBOL
symbol IS MISSING. A return code of 4 is returned and processing
continues.
Explanation
The specified assignment symbol is expected in the
syntax but is missing. Determine which statement is missing and correct the
syntax.
Message Variables
EKG8222W AN UNMATCHED END STATEMENT
symbol WAS ENCOUNTERED.
The symbol is either '=' or '::='.
Explanation
System action
The end statement was encountered before any
A return code of 4 is returned and processing syntax was processed.
continues.
System action
Find the place where the assignment symbol is to continues.
occur and correct the syntax.
EKG8220W THE insert OF THE ATTRIBUTE IS Operator response
MISSING. Notify the system programmer.

The specified attribute's value is missing. Determine the location of the error and correct the end
Message Variables syntax.
insert EKG8223W THE RODM DATA TYPE IS
The descriptor of the piece of syntax that is MISSING OR IS NOT VALID.
missing. The descriptor is TYPE, NAME, or VALUE.
Explanation
System action
A valid data type is not supplied for the particular
A return code of 4 is returned and processing attribute.
continues.
System action
Operator response
Notify the system programmer. continues.

Determine the attribute syntax that is missing and Notify the system programmer.
correct the syntax.
EKG8221W THE keyword KEYWORD System programmer response
STATEMENT IS MISSING. Insert a valid data type for this attribute.
EKG8224W EXTRANEOUS DATA APPEARS IN
Explanation
THE ATTRIBUTE DEFINITION.
The statement for the specified keyword is missing.
Message Variables

The data specified in the attribute definition is of Correct the input syntax so that all quotation marks
unknown type or form. are matched.
EKG8227W THE END OF DOUBLE BYTE
System action CHARACTER SET (DBCS) STRING
A return code of 4 is returned and processing NOT INDICATED.
continues.
Explanation
Operator response A shift-in character does not follow a shift-out
Notify the system programmer. character on the same line.
Find the data that is not valid and correct the problem. A return code of 4 is returned and processing
continues.
EKG8225W AN ATTRIBUTE VALUE CANNOT BE
SUPPLIED FOR THIS ATTRIBUTE
TYPE attribute.
Correct the input to contain a valid DBCS string within
Explanation the bounds of a single input line.
An attribute value is not valid for the specified EKG8228W THE DOUBLE BYTE CHARACTER
attribute type. SET (DBCS) STRING IS COMPOSED
OF AN UNEVEN NUMBER OF
Message Variables SINGLE BYTE CHARACTERS.
attribute
The attribute type. Explanation
The number of single bytes between shift-out (X'0E')
System action and shift-in (X'0F') characters is not a multiple of two.
continues. System action
Operator response continues.
System programmer response Correct the input to contain a valid DBCS character
Correct the input syntax so that no value is supplied string.
for the specified attribute type.
EKG8251E RODM LOADER PRIMITIVE
EKG8226W A QUOTE IS MISSING FROM THE STATEMENT primitive HAS FAILED.
BEGINNING OR END OF THE REFER TO RODM RETURN/
STRING. REASONCODE retcode/reason.
A single quotation mark exists without a The Resource Object Data Manager (RODM) API call to
corresponding quotation mark to make a pair. perform the RODM function on the primitive statement
failed, and a return or reason code was returned.
A return code of 4 is returned and processing primitive
continues. The name of the RODM primitive statement that
has failed.
retcode/reason
The return or reason code issued by RODM.

System action and processing continues. In both cases, the current
primitive statement is parsed.

Determine from the accompanying messages where
the error occurred, and correct the problem. See
where the error occurred and correct the problem. See
associated messages EKG8254E and EKG8256E for
IBM Z NetView Resource Object Data Manager and
information.
GMFHS Programmer's Guide for more information on
return codes and reason codes. EKG8254E THE string IS NOT VALID FOR
token.
EKG8252E RODM LOADER PRIMITIVE
STATEMENT primitive HAS BEEN
SPECIFIED WITH AN INCORRECT Explanation
NUMBER OF TOKENS. The character string is not valid for the token name
being specified. If token name is DataType or
Explanation SubFieldType, the character string must be a Resource
Object Data Manager (RODM) Data or SubFieldType. If
The number of tokens specified in the primitive
the token name is ClassName, ObjectName,
statement is not valid.
FieldName, or SubFieldName, the character string
Message Variables must:
primitive • Begin with an alphanumeric character
The name of the RODM primitive statement that • Be of a valid length for the name being specified
was specified.
• Contain alphanumeric characters or special
characters for the name being specified
System action
Strings embedded in quotation marks must:
If the severity parameter is ERROR, a return code of 8
is returned and processing stops. If the severity – Begin and end with a single quotation mark
parameter is WARNING, a return code of 4 is returned – Represent each embedded single quotation mark
and processing continues. In both cases the current by a pair of single quotation marks
primitive statement is parsed.
See IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide for more information
about token names and character strings.
Correct the primitive statement to reflect a valid
Message Variables
number of tokens.
string
EKG8253E RODM LOADER PRIMITIVE The input string that is not valid.
STATEMENT primitive CONTAINS
SYNTAX ERRORS. token
The descriptor of the character string that is in
error: ClassName, ObjectName, FieldName,
Explanation
SubFieldName, DataType, or SubFieldType.
Syntax errors were found during primitive statement
handler processing. System action
Message Variables If the severity parameter is ERROR, a return code of 8
primitive is returned and processing stops. If the severity
The name of the RODM primitive statement parameter is WARNING, a return code of 4 is returned
containing the syntax errors. and processing continues.
If the severity parameter is ERROR, a return code of 8 Correct the syntax in error and retry the request.
is returned and processing stops. If the severity EKG8255E THE PRIMITIVE STATEMENT
parameter is WARNING, a return code of 4 is returned CANNOT BE RESOLVED.

The primitive statement cannot be processed. If the severity parameter is ERROR, a return code of 8
is returned and processing stops. If the severity
System action parameter is WARNING, a return code of 4 is returned
and processing continues. In both cases the current
If the severity parameter is ERROR, a return code of 8 primitive statement is parsed.
is returned and processing is halted. If the severity
parameter is WARNING, a return code of 4 is returned
and processing continues. In both cases, the current
primitive statement is parsed. Determine where the end occurred from the
accompanying system messages and correct the
System programmer response problem.
Determine which primitive statement is unresolved EKG8258I THE primitive PRIMITIVE

and correct the problem. Other messages that clarify STATEMENT COMPLETED
errors in the statement might accompany this one. SUCCESSFULLY.
EKG8256E THE VALUE value IS NOT VALID

Explanation
FOR THE RODM DATA TYPE
datatype. The Resource Object Data Manager (RODM) load
function primitive statement, represented by primitive,
Explanation processed successfully.
The specified value is not valid for the Resource Object Message Variables
Data Manager (RODM) data type. primitive
Message Variables The name of the primitive statement.
value
System action
The input value that is not valid.
datatype A return code of 0 is returned and processing
The RODM data type for the value expression that continues.
is not valid. EKG8259E THE primitive PRIMITIVE
STATEMENT WAS NOT
System action SUCCESSFUL.
is returned and processing stops. If the severity Explanation
parameter is WARNING, a return code of 4 is returned The Resource Object Data Manager (RODM) load utility
and processing continues. primitive statement, represented by primitive, was not
processed successfully.
Message Variables
Correct the value expression that is not valid.
primitive
EKG8257E AN UNEXPECTED END The name of the primitive statement.
STATEMENT WAS FOUND WHILE
PARSING token TOKEN. System action
Explanation is returned and processing stops. If the severity
The end of the token was prematurely encountered. parameter is WARNING, a return code of 4 is returned
and processing will continue. In both cases, the
Message Variables current primitive statement continues to be parsed.
token
The token type for which the unexpected end was System programmer response
found.
See the associated messages to determine the
reasons for failure. Make modifications in the

definition syntax files if syntax or other definition Message Variables
problems exist.
class
EKG8260E THIS datatype DATA TYPE IS NOT The RODM class name that is not valid.
VALID FOR THIS primitive
PRIMITIVE STATEMENT. System action
The given data type is not valid in the context of this parameter is WARNING, a return code of 4 is returned
primitive statement. and processing continues.
Message Variables
datatype
The name of the data type that is not valid in this Use a valid RODM class name in the syntax.
context. EKG8502E THE PARENT CLASS NAME
primitive parentclass DOES NOT EXIST.
The name of the primitive statement.
Explanation
System action The parent class name specified in the primitive
If the severity parameter is ERROR, a return code of 8 statement is not found in the parent class name list.
is returned and processing stops. If the severity Message Variables
and processing will continue. In both cases, the parentclass
current primitive statement continues to be parsed. The parent class that does not exist.

Use a valid data type in conjunction with the desired If the severity parameter is ERROR, a return code of 8
primitive statement. is returned and processing stops. If the severity
EKG8261I RODM LOADER VERIFICATION and processing continues.
LOGIC IS NOT PERFORMED FOR
THE primitive PRIMITIVE
STATEMENT.
Use a valid class name for the parent class in the
Explanation syntax.
Verification cannot be performed for the specified EKG8503E THE CLASS NAME class DOES NOT
primitive statement. EXIST.
Message Variables
Explanation
primitive
The name of the primitive statement. The Resource Object Data Manager (RODM) class
name specified in the primitive statement is not found
in the class name list.
System action
Message Variables
continues. class
The RODM class that does not exist.
EKG8501E THE CLASS NAME class IS NOT
VALID.
System action
Explanation If the severity parameter is ERROR, a return code of 8

The class name specified in the primitive statement is parameter is WARNING, a return code of 4 is returned
not valid. This message is issued as a result of and processing continues.
Resource Object Data Manager (RODM) returning a
reason code of 86.

Correct the input syntax to include a valid RODM class The Resource Object Data Manager (RODM) field name
name. specified in the primitive statement is not valid.
EKG8504E THE PARENT NAME FOR THE Message Variables
CLASS NAME class IS INCORRECT. field
The RODM field name that is not valid.
Explanation
The Resource Object Data Manager (RODM) class System action
name specified in the primitive statement points to the If the severity parameter is ERROR, a return code of 8
wrong parent class. is returned and processing stops. If the severity
Message Variables parameter is WARNING, a return code of 4 is returned
and processing continues. A reason code of 91 is
class returned with this message.
The RODM class for which the parent name is
incorrect.
System action Correct the input syntax to process a valid RODM field
name.
is returned and processing stops. If the severity EKG8507E THE FIELD field DOES NOT EXIST
parameter is WARNING, a return code of 4 is returned OR IS NOT LOCALLY DEFINED.
and processing continues.
Explanation
The Resource Object Data Manager (RODM) has
Correct the input syntax to include a valid parent/child indicated that the specified field is not created under
relationship. the specified class.
EKG8505E THE CLASS NAME class ALREADY Message Variables
EXISTS. field
The field name specified on the primitive
Explanation statement that does not exist or is not locally
The Resource Object Data Manager (RODM) class defined.
name specified in the primitive statement already
exists in the class name list. System action
Message Variables If the severity parameter is ERROR, a return code of 8
class parameter is WARNING, a return code of 4 is returned
The RODM class that already exists. and processing continues.

If the severity parameter is ERROR, a return code of 8 Correct the primitive syntax.
parameter is WARNING, a return code of 4 is returned EKG8508E THE FIELD NAME field DOES NOT
and processing continues. This message is EXIST.
accompanied by message EKG8535, which details the
return and reason codes from RODM. Explanation
The Resource Object Data Manager (RODM) field name
specified in the primitive statement does not exist in
Correct the input syntax to process a valid RODM class the field name list.
name.
Message Variables
EKG8506E THE FIELD NAME field IS NOT field
VALID. The name of the field that does not exist.

System action EKG8511E THE FIELD NAME field IS NOT
PRIVATE.
parameter is WARNING, a return code of 4 is returned Explanation
and processing continues. Reason codes 56 and 92 The Resource Object Data Manager (RODM) field name
are returned with this message. specified in the primitive statement is not private. This
name is specified as public in the field name list.
Message Variables
Correct the input syntax to contain a valid RODM field
field
name.
The name of the field that is not private.
EKG8509E THE DATA TYPE DOES NOT MATCH
THAT OF THE FIELD. System action
Explanation
The Resource Object Data Manager (RODM) data type parameter is WARNING, a return code of 4 is returned
specified in the primitive statement does not match and processing continues. This message is
the data type of the field. accompanied by message EKG8535, which details the
return and reason codes from RODM.
System action
is returned and processing stops. If the severity Correct the input syntax to specify the correct private
parameter is WARNING, a return code of 4 is returned or public attribute for this field.
and processing continues. Reason codes 66, 92 and
83 are returned with this message. EKG8512E THE SUBFIELD subfield IS NOT
VALID.
Explanation
Correct the input syntax to contain a valid RODM data
type for the supplied value in the primitive statement. The Resource Object Data Manager (RODM) subfield
name specified in the primitive statement is not valid.
EKG8510E THE FIELD NAME field ALREADY
Message Variables
EXISTS.
subfield
Explanation The name of the subfield that is not valid.
The Resource Object Data Manager (RODM) field name

System action
specified in the primitive statement already exists in
the field name list. If the severity parameter is ERROR, a return code of 8
Message Variables
field and processing continues. This message is
The name of the field that already exists. accompanied by message EKG8535, which details the
System action
is returned and processing stops. If the severity Correct the input syntax to specify a valid RODM
parameter is WARNING, a return code of 4 is returned subfield name. The subfield can contain one of the
and processing continues. Reason codes 7 and 92 are following: VALUE, PREV_VALUE, TIMESTAMP,
returned with this message. CHANGE, QUERY, or NOTIFY.
EKG8513E THE SUBFIELD subfield DOES NOT
System programmer response EXIST.
Correct the input syntax so that it contains a valid
RODM field name.

The Resource Object Data Manager (RODM) subfield The Resource Object Data Manager (RODM) object
name specified in the primitive statement is not found specified in the primitive statement is not valid.
in the subfield list.
Message Variables
Message Variables
object
subfield The RODM object that is not valid.
The name of the subfield that does not exist.
System action
System action
If the severity parameter is ERROR, a return code of 8 is returned and processing stops. If the severity
is returned and processing stops. If the severity parameter is WARNING, a return code of 4 is returned
parameter is WARNING, a return code of 4 is returned and processing continues. This message is
and processing continues. This message is accompanied by message EKG8535, which details the
accompanied by message EKG8535, which details the return and reason codes from RODM.
Correct the input syntax to specify a valid RODM
Correct the input syntax to specify a valid RODM object.
subfield name. The subfield can have the value of
VALUE, PREV_VALUE, TIMESTAMP, CHANGE, QUERY, EKG8516E THE OBJECT object DOES NOT
or NOTIFY. EXIST.
EKG8514E THE SUBFIELD subfield ALREADY Explanation

EXISTS.
The Resource Object Data Manager (RODM) object
specified in the primitive statement is not found in the
Explanation
object list.
The Resource Object Data Manager (RODM) subfield
Message Variables
name specified in the primitive statement already
exists in the subfield list. object
The RODM object that does not exist.
Message Variables
subfield System action
The name of the subfield that already exists.
System action
If the severity parameter is ERROR, a return code of 8 and processing continues. This message is
is returned and processing stops. If the severity accompanied by message EKG8535, which details the
parameter is WARNING, a return code of 4 is returned return and reason codes from RODM.
and processing continues. This message is
accompanied by message EKG8535, which details the System programmer response
object.
EKG8517E THE OBJECT object ALREADY
subfield name. The subfield can contain one of the EXISTS.
following: VALUE, PREV_VALUE, TIMESTAMP,
CHANGE, QUERY, or NOTIFY. Explanation
EKG8515E THE OBJECT object IS NOT VALID. The Resource Object Data Manager (RODM) object
specified in the primitive statement already exists in
the object list.
Message Variables

object System programmer response
The RODM object that already exists.
Correct the input syntax to specify a valid RODM value
that matches the supplied field.
System action
EKG8520E THE FIELDS ARE NOT LINKED.
Explanation
and processing continues. This message is The Resource Object Data Manager (RODM) link fields
accompanied by message EKG8535, which details the specified in the primitive statement are not linked.
System action
Determine the valid object name for the field and is returned and processing stops. If the severity
correct the input syntax. parameter is WARNING, a return code of 4 is returned
EKG8518E THE SPECIFIED TYPED VALUE IS
NOT VALID.
Explanation If the fields are required to be linked, rerun the load
function as an OPERATION=LOAD.
The Resource Object Data Manager (RODM) TYPED
value is not valid. EKG8521E THE OBJECTS ARE ALREADY
LINKED.
System action
If the severity parameter is ERROR, a return code of 8 Explanation
is returned and processing stops. If the severity A link already exists between the Resource Object
parameter is WARNING, a return code of 4 is returned Data Manager (RODM) objects specified. The
and processing continues. This message is requested link function cannot be performed.
return and reason codes from RODM. System action
System programmer response If the severity parameter is ERROR, a return code of 8

Determine the valid data type for the field being parameter is WARNING, a return code of 4 is returned
changed and correct the input syntax. and processing continues. This message is
EKG8519E THE SPECIFIED TYPED VALUE
DOES NOT MATCH THAT OF THE
FIELD.
Explanation Correct the input syntax to link only RODM objects that
are not already linked.
The Resource Object Data Manager (RODM) TYPED
value does not match the TYPED value of the field EKG8523E THE CLASS class HAS BOTH
specified. CLASS AND OBJECT CHILDREN
AND CANNOT BE DELETED.
System action
is returned and processing stops. If the severity The Resource Object Data Manager (RODM) class
parameter is WARNING, a return code of 4 is returned specified for deletion has both class and object
and processing continues. This message is children and will not be deleted.
return and reason codes from RODM. Message Variables
class
The RODM class that will not be deleted.

System action class
The RODM class that cannot be deleted.
NOT_A_CLASS RODM load function returned a reason
code of 90 which causes the job to have an overall
return code of either: System action
Return Code If the severity parameter is ERROR, a return code of 8
Meaning is returned and processing stops. If the severity
4
The severity parameter is WARNING and
8
The severity parameter is ERROR and processing System programmer response
stops.
Correct the input syntax to delete only classes that
System programmer response have no children.
Correct the input syntax to delete only classes that EKG8526E THE OBJECT object HAS LINKS TO
have no children. OTHER OBJECTS AND CANNOT BE
DELETED.
EKG8524E THE CLASS class HAS CLASS
CHILDREN AND CANNOT BE Explanation
DELETED.
The links to other Resource Object Data Manager
Explanation (RODM) objects must be disconnected for the
specified deletion to occur.
The Resource Object Data Manager (RODM) class
specified for deletion has children and cannot be Message Variables
deleted. object
Message Variables The name of the RODM object with links.
class System action

The RODM class specified for deletion.
System action is returned and processing stops. If the severity
If the severity parameter is ERROR, a return code of 8 and processing continues. This message is
is returned and processing stops. If the severity accompanied by message EKG8535, which details the
parameter is WARNING, a return code of 4 is returned return and reason codes from RODM.
accompanied by message EKG8535, which details the System programmer response
Correct the input syntax to delete only RODM objects
System programmer response that have no links to other RODM objects.
Correct the input syntax to delete only classes that EKG8527E THE FIELD field CANNOT BE
have no children. DELETED BECAUSE THE CLASS OR
A DESCENDENT CLASS HAS
EKG8525E THE CLASS class HAS OBJECT OBJECTS.
CHILDREN AND CANNOT BE
DELETED. Explanation
Explanation The specified field cannot be deleted because an

object exists on the class of the field or on another
The Resource Object Data Manager (RODM) class class that is a descendent of the field.
specified for deletion has objects and cannot be
deleted. Message Variables
Message Variables field

The name of the Resource Object Data Manager
(RODM) field that cannot be deleted.

If the severity parameter is ERROR, a return code of 8 Notify the system programmer.
parameter is WARNING, a return code of 4 is returned System programmer response
accompanied by message EKG8535, which details the Correct the primitive so that the value of the field is the
return and reason codes from RODM. same as its inherited value.
EKG8531E THE VALUE FOR THE SUBFIELD
System programmer response subfield IS NOT INHERITED.
Correct the input syntax to delete only RODM field
names belonging to a class with no objects. Explanation
EKG8528E THE FIELD field IS ALREADY SET The value of the specified subfield has not been
TO ITS INHERITED VALUE. inherited from its primary parent. Either the subfield
was created on the class specified on the primitive, or
the value has been changed.
Explanation
Message Variables
The Resource Object Data Manager (RODM) field value
is already set to the inherited value. subfield
The subfield whose value was not inherited.
Message Variables
field System action
The field name set to the inherited value.
System action
If the severity parameter is ERROR, a return code of 8 and processing continues.
parameter is WARNING, a return code of 4 is returned System programmer response
accompanied by message EKG8535, which details the Correct the input syntax to specify a valid value for the
return and reason codes from RODM. RODM subfield.
EKG8532E NO LINKS EXIST BETWEEN THE
System programmer response SPECIFIED OBJECTS.
Correct the input syntax to no longer set this field to its
inherited value. Explanation
EKG8530E THE VALUE OF THE FIELD field IS The links between the two specified objects either do
NOT INHERITED. not exist or have been deleted.
The value of the specified field has not been inherited If the severity parameter is ERROR, a return code of 8
from its primary parent. Either the field was created on is returned and processing stops. If the severity
the class specified on the primitive, or the value has parameter is WARNING, a return code of 4 is returned
been changed. and processing continues. This message is
Message Variables return and reason codes from RODM.
field
The field name specified on the primitive. System programmer response
Correct the input syntax to reference two objects with
System action a link already established.
If the severity parameter is ERROR, a return code of 8 EKG8533E THE SPECIFIED DATA TYPE DOES
is returned and processing stops. If the severity NOT MATCH THAT OF THE
parameter is WARNING, a return code of 4 is returned SUBFIELD.

The data type specified on the primitive statement is Check the meaning of the reason code supplied. See
not the data type of the Resource Object Data Manager IBM Z NetView Resource Object Data Manager and
(RODM) subfield. GMFHS Programmer's Guide for more information on
return and reason codes.
System action EKG8536E THE FIELD NAME field IS NOT
If the severity parameter is ERROR, a return code of 8 LOCALLY DEFINED.
The Resource Object Data Manager (RODM) field (or
subfield of the field) was not created on the specified
System programmer response class, but was inherited from its primary parent.
Correct the input syntax of the primitive statement to Message Variables
match the data type of the RODM subfield.
field
EKG8534E THE SPECIFIED TYPED VALUE The field that is not locally defined.
DOES NOT MATCH THAT OF THE
SUBFIELD.
System action

The TYPED value specified on the primitive statement parameter is WARNING, a return code of 4 is returned
is not the TYPED value of the Resource Object Data and processing continues.
Manager (RODM) subfield.
System action
Correct the input syntax to reference a valid RODM
If the severity parameter is ERROR, a return code of 8 field name.
parameter is WARNING, a return code of 4 is returned EKG8537E THE OBJECT NAMES ARE
and processing continues. ALREADY LINKED.
Correct the input syntax of the primitive statement to Links exist between the specified Resource Object
match the TYPED value with that of the RODM Data Manager (RODM) objects.
subfield.
System action
EKG8535E THE API CALL TO RODM FAILED,
WITH RETURN/REASON CODE If the severity parameter is ERROR, a return code of 8
retcode/reason. is returned and processing stops. If the severity
Explanation and processing continues.
The API call to the Resource Object Data Manager EKG8538E THE SUBFIELD subfield CANNOT
(RODM) failed. A return or reason code is issued. BE DELETED BECAUSE THE CLASS
HAS OBJECTS.
Message Variables
retcode/reason Explanation
The return or reason code issued by RODM.
Objects of a class must be deleted before a subfield of
that class can be deleted.
System action
Message Variables
subfield
(RODM) subfield.

If the severity parameter is ERROR, a return code of 8 Correct the input syntax by not using the revert
is returned and processing stops. If the severity function for OBJECTLINK or OBJECTLINKLIST fields or
parameter is WARNING, a return code of 4 is returned subfields.
EKG8543E THE REVERT FUNCTION IS NOT
VALID FOR THE REQUIRED FIELD
field.

Explanation
Correct the input syntax to delete the subfields.
The revert function cannot be specified for required
EKG8541E THE FIELD NAME field IS LOCALLY fields.
DEFINED.
Message Variables
Explanation field
The required field that is not valid in the revert
The specified field is not inherited, because it is locally function.
defined.
field If the severity parameter is ERROR, a return code of 8
The field that is locally defined. is returned and processing stops. If the severity
System action and processing continues. This message is
If the severity parameter is ERROR, a return code of 8 return and reason codes from RODM.
accompanied by message EKG8535, which details the Correct the input syntax to remove required fields.
EKG8544E THE REVERT FUNCTION IS NOT
VALID FOR THE SUBFIELD
System programmer response subfield.
Correct the input syntax to reference a valid Resource
Object Data Manager (RODM) field name. Explanation
EKG8542E THE DATA TYPE FOR THE REVERT The revert function cannot be used with certain
FUNCTION IS NOT VALID. subfields, such as NOTIFY, TIMESTAMP, and
PRE_VALUE.
The revert function cannot be used for fields (or subfield
subfields of the field) of data type OBJECTLINK or The subfield that is not valid in the revert function.
OBJECTLINKLIST.
System action
System action
If the severity parameter is ERROR, a return code of 8 is returned and processing stops. If the severity
is returned and processing stops. If the severity parameter is WARNING, a return code of 4 is returned
parameter is WARNING, a return code of 4 is returned and processing continues. This message is
and processing continues. This message is accompanied by message EKG8535, which details the
accompanied by message EKG8535, which details the return and reason codes from RODM.
Correct the input syntax to specify a valid subfield that
can be inherited.

EKG8546E THE SUBFIELD subfield CANNOT System action
BE CREATED FOR RODM If the severity parameter is ERROR, a return code of 8
REQUIRED FIELDS. is returned and processing stops. If the severity
Explanation and processing continues. This message is
The specified subfield cannot be created for any accompanied by message EKG8535, which details the
required or system fields. return and reason codes from RODM.

subfield Correct the input syntax to specify valid data types.
The subfield that cannot be created.
EKG8549E THE PARENT CLASS class HAS
System action OBJECT CHILDREN.

Explanation
parameter is WARNING, a return code of 4 is returned The Resource Object Data Manager (RODM) parent
and processing continues. This message is class has objects.
Message Variables
class
System programmer response The class with object children.
Correct the input syntax to reference valid subfields

System action
for the required fields.
EKG8547E AN OBJECT NAME CANNOT BE is returned and processing stops. If the severity
LINKED TO OR UNLINKED FROM parameter is WARNING, a return code of 4 is returned
ITSELF. and processing continues. This message is
Explanation return and reason codes from RODM.
Identical object names cannot be linked or unlinked.
System action Correct the input syntax to reference a parent class
If the severity parameter is ERROR, a return code of 8 that has no objects.
is returned and processing stops. If the severity EKG8550E THE METHOD method IS A NULL
parameter is WARNING, a return code of 4 is returned METHOD.
Explanation
The specified method is a null module because it has
System programmer response previously been deleted by an unsuccessful module
refresh.
Correct the input syntax to link or unlink object names.
Message Variables
EKG8548E THE DATA TYPE FOR THE LINK OR
UNLINK IS NOT VALID. method
The name of the method that is null.
Explanation
System action
The specified data type is not valid for a link or unlink
function. The valid data types are OBJECTLINK and If the severity parameter is ERROR, a return code of 8
OBJECTLINKLIST. is returned and processing stops. If the severity

Refresh the method and retry the request. If the The method you called is not installed.
request fails after you refresh the method, delete the
Message Variables
method and then install it again.
method
EKG8552E THE DATA TYPE OF THE FIELD The method that is not installed.
field IS NOT VALID FOR INVOKING
A METHOD.
System action
To invoke a method, a field must be specified and the parameter is WARNING, a return code of 4 is returned
data type must be MethodSpec. and processing continues. This message is
Message Variables accompanied by message EKG8535, which details the
field
The name of the field specified.
System action Either add the method to the install method table or
correct the input syntax to call an installed method.
is returned and processing stops. If the severity EKG8555E THE METHOD method HAS BEEN
parameter is WARNING, a return code of 4 is returned DELETED.
accompanied by message EKG8535, which details the Explanation
The method has been deleted.
Correct the input syntax to specify a data type of method
MethodSpec. The method that has been deleted.
EKG8553E THE METHOD method CANNOT BE
INVOKED MORE THAN ONCE. System action
The method can only be called once. and processing continues. This message is
Message Variables accompanied by message EKG8535, which details the
method
The method that is being called more than once.
System action Either add the method to the install method table or
correct the input syntax to call an installed method.
is returned and processing stops. If the severity EKG8556E THE CLASS NAME class HAS NOT
parameter is WARNING, a return code of 4 is returned BEEN DELETED.
and processing continues. A reason code of 64 is
returned with this message. Explanation
The Resource Object Data Manager (RODM) class in
the primitive statement still exists in the class name
Correct the input syntax to call a method only once. list.
EKG8554E THE METHOD method IS NOT Message Variables
INSTALLED. class
The name of the class that still exists.

If the severity parameter is ERROR, a return code of 8 Either correct the input syntax to reference the correct
is returned and processing stops. If the severity field name or perform an OPERATION=LOAD to delete
parameter is WARNING, a return code of 4 is returned the specified field.
EKG8559E THE SUBFIELD subfield HAS NOT
BEEN DELETED.
Explanation
The Resource Object Data Manager (RODM) subfield in
Either correct the input syntax to reference the correct
the primitive statement still exists in the subfield list.
class name or perform an OPERATION=LOAD to delete
the specified class. Message Variables
EKG8557E THE OBJECT NAME object HAS subfield
NOT BEEN DELETED. The name of the subfield.

The Resource Object Data Manager (RODM) object in If the severity parameter is ERROR, a return code of 8
the primitive statement still exists in the object name is returned and processing stops. If the severity
list. parameter is WARNING, a return code of 4 is returned
Message Variables
object return and reason codes from RODM.
The name of the object that still exists.
System action
Either correct the input syntax to reference the correct
If the severity parameter is ERROR, a return code of 8 subfield or perform an OPERATION=LOAD to delete
is returned and processing stops. If the severity the specified subfield. The subfield can be either
parameter is WARNING, a return code of 4 is returned PREV_VALUE, TIMESTAMP, CHANGE, QUERY, or
and processing continues. This message is NOTIFY.
return and reason codes from RODM. EKG8560E SUBFIELDS CANNOT BE DELETED
FROM REQUIRED OR SYSTEM
FIELDS.
Either correct the input syntax to reference the correct Explanation
object or perform an OPERATION=LOAD to delete the
specified object. Subfields created by the Resource Object Data
Manager (RODM) cannot be deleted by user
EKG8558E THE FIELD NAME field HAS NOT applications.
BEEN DELETED.
System action
Explanation
The Resource Object Data Manager (RODM) field in the is returned and processing stops. If the severity
primitive statement still exists in the field name list. parameter is WARNING, a return code of 4 is returned
Message Variables
field return and reason codes from RODM.
The name of the field that still exists.
If the severity parameter is ERROR, a return code of 8 System programmer response
is returned and processing stops. If the severity Correct the input syntax so that there is not an attempt
parameter is WARNING, a return code of 4 is returned to delete system-created subfields.
accompanied by message EKG8535, which details the EKG8561E THE SUBFIELD VALUE CANNOT BE
return and reason codes from RODM. DELETED.

The subfield VALUE cannot be deleted. Correct the input syntax so that there is not an attempt
to delete required RODM or system fields.
System action EKG8564E THE DATA TYPE datatype IS NOT
If the severity parameter is ERROR, a return code of 8 VALID FOR THE CHANGE
is returned and processing stops. If the severity SUBFIELD FUNCTION.
and processing continues. This message is Explanation
Subfields cannot be changed for fields of data type
OBJECTLINK or OBJECTLINKLIST.
Correct the input syntax so that the subfield VALUE is datatype

not deleted. The data type that is not valid.
EKG8562E THE CLASS class HAS NO OBJECT

System action
CHILDREN.
The primary parent class specified has no object and processing continues. This message is
children. The operation is not possible. accompanied by message EKG8535, which details the
Message Variables return and reason codes from RODM.
class
The name of the class with no object children.
Correct the input syntax by not changing subfields for
System action data types OBJECTLINK or OBJECTLINKLIST.
If the severity parameter is ERROR, a return code of 8 EKG8565E THE SUBFIELDS OF REQUIRED
is returned and processing stops. If the severity FIELDS CANNOT BE CHANGED.
and processing continues. This message is Explanation
return and reason codes from RODM. Required subfields cannot be changed by user
applications.
System action
Correct the input syntax to reference a parent class
that has objects. If the severity parameter is ERROR, a return code of 8
EKG8563E REQUIRED OR RODM PREDEFINED parameter is WARNING, a return code of 4 is returned
FIELDS CANNOT BE DELETED. and processing continues. This message is
Explanation return and reason codes from RODM.
Required or Resource Object Data Manager (RODM)

predefined fields cannot be deleted by user
applications. Remove the input syntax that involves changing
required subfields.
System action EKG8566E THE FUNCTION IS NOT VALID FOR
If the severity parameter is ERROR, a return code of 8 SUBFIELD subfield.
The function being performed by this primitive
statement is not permitted for the specified subfield.

subfield The specified method cannot be installed because it
The name of the subfield. already exists.
Message Variables
System action
method
If the severity parameter is ERROR, a return code of 8 The name of the method that already exists.
System action
accompanied by message EKG8535, which details the A return code of 4 is returned and processing
return and reason codes from RODM. continues.

Correct the input syntax that is performing the Ensure that the method already exists.
function on the specified subfield. See IBM Z NetView
EKG8569E THE SUBSTITUTION CANNOT
TAKE PLACE. THE VALUE WAS
Programmer's Guide for the correct subfield types.
NOT PREVIOUSLY USED IN THE
EKG8567E THE METHOD method HAS NOT SYNTAX.
BEEN INSTALLED. REFER TO THE
RODM RETURN/REASON CODE Explanation
retcode/reason.
The input syntax contains an asterisk (*) to indicate
that the previous value is to be substituted; however
Explanation
no previous value exists.
The specified method is not installed. A Resource
Object Data Manager (RODM) return or reason code is System action
returned.
Message Variables is returned and processing stops. If the severity
method parameter is WARNING, a return code of 4 is returned
The name of the method that cannot be created. and processing continues.
retcode/reason
The return or reason code returned by RODM. System programmer response
Correct the input syntax by removing asterisks (*) in
System action cases where no previous values exist for substitution
and replacing them with valid names.
is returned and processing stops. If the severity EKG8570E THE FIELD NAME field IS NOT
parameter is WARNING, a return code of 4 is returned PUBLIC.
Explanation
The requested operation cannot be performed on the
Determine from the accompanying RODM return or specified field because it is a private field.
reason code where the failure occurred and correct
Message Variables
the problem. See IBM Z NetView Resource Object Data
Manager and GMFHS Programmer's Guide for the field
return and reason codes. The name of the field that is not public.
EKG8568W THE METHOD method HAS NOT
BEEN INSTALLED BECAUSE IT System action
ALREADY EXISTS. If the severity parameter is ERROR, a return code of 8

accompanied by message EKG8535, which details the 4
return and reason codes from RODM. The severity parameter is WARNING and
Correct the input syntax by removing references to the The severity parameter is ERROR and processing
stops.
specified private field.
EKG8571E PARENT CLASS NAME class HAS System programmer response
CLASS CHILDREN.
Retry the request after ensuring that applications are
not currently modifying the class structure being
Explanation
deleted.
An attempt was made to create an object under the
EKG8573E THE TARGET CLASS CANNOT BE
specified parent class, but the parent class already has
DELETED. SOME OBJECT
class children. A parent class can have either class
CHILDREN STILL EXIST.
children or object children, but not both.
class The forced deletion of the target class is unsuccessful
The parent class that already has class children. for the FORCE_HAS_NO_CLASS primitive statement
because some object children cannot be force-
System action deleted. Forced deletion of all object children is
necessary before the target class can be deleted. Note
that some object children might have been
successfully force-deleted.
accompanied by message EKG8535, which details the System action
return and reason codes from RODM. If the severity parameter is ERROR, a return code of 8
System programmer response parameter is WARNING, a return code of 4 is returned
Either remove the Create Object request, or ensure
that the specified parent class has no class children
before attempting to create an object under that class. Operator response
EKG8572E THE TARGET CLASS CANNOT BE Notify the system programmer.

DELETED. SOME CLASS AND/OR
OBJECT CHILDREN STILL EXIST. System programmer response
Retry the request after ensuring that other
Explanation applications are not currently modifying the class
The forced deletion of the target class is unsuccessful structure being deleted.
for the FORCE_NOT_A_CLASS RODM load function EKG8574E THE TARGET OBJECT CANNOT BE
primitive statement because some class or object DELETED. SOME LINKS TO OTHER
children cannot be force deleted. Forced deletion of all OBJECTS STILL EXIST.
class and object children is necessary before the
target class can be deleted. Note that some class or
object children might have been successfully deleted. Explanation
The forced deletion of the target object is unsuccessful
System action for the FORCE_HAS_NO_INSTANCE primitive
statement because some links to other objects cannot
FORCE_NOT_A_CLASS RODM load function returned a be force-unlinked. Forced unlinking of all linked
reason code of 90 which causes the job to have an objects is necessary before the target object can be
overall return code of either: deleted.
Return Code
Note: Some object links might have been successfully
Meaning
force-unlinked.

System action • CLASSIDLIST
If the severity parameter is ERROR, a return code of 8 • CLASSLINKLIST
is returned and processing stops. If the severity • ECBADDRESS
• METHODNAME
• METHODPARAMETERLIST
Operator response • OBJECTIDLIST
Notify the system programmer. • OBJECTNAME
• RECIPIENTSPEC
System programmer response • SHORTNAME
Retry the request after ensuring that other • SUBSCRIBEID
applications are not currently modifying the class • SUBSCRIPTSPEC
structure being deleted.
• SUBSCRIPTSPECLIST
EKG8580E THE datatype DATA TYPE CANNOT • TRANSID
EXIST WITHIN A SELFDEFINING
VALUE.
System action
A SELFDEFINING value cannot contain the given data parameter is WARNING, a return code of 4 is returned
type. Data types that are not valid within a and processing continues.
SELFDEFINING value are: OBJECTLINK,
OBJECTLINKLIST, and ANONYMOUS.
Message Variables
Correct the input to contain a valid data type.
datatype
The name of the data type that cannot exist with a EKG8583E SOME NOTIFICATION METHODS
SELFDEFINING value. ARE NOT TRIGGERED FOR
primitive PRIMITIVE.
System action
Explanation
is returned and processing stops. If the severity There is an error with at least one of the notification
parameter is WARNING, a return code of 4 is returned methods for the field in the named primitive. Possible
and processing continues. causes are that the notification method is recursive or
there are errors in executing the method.
Correct the input to contain a valid data type. primitive
The name of the RODM primitive statement.
EKG8582E THE datatype DATATYPE CAN Primitive names which might incur this error are:
ONLY EXIST WITHIN A
SELFDEFINING VALUE. • HAS_PARENT
• HAS_INSTANCE
Explanation • HAS_VALUE
The given data type is only valid within a • IS_LINKED_TO
SELFDEFINING value.
• NOT_A_CLASS
Message Variables • FORCE_NOT_A_CLASS
datatype • NOT_AN_INSTANCE
The data type that is valid only within the context
• FORCE_NOT_AN_INSTANCE
of a SELFDEFINING statement. Data types that are
valid only within a SELFDEFINING statement are: • IS_NOT_LINKED_TO
• APPLICATIONID
• CHARVARADDR

System action object
(RODM) object.
and processing continues. System action
Operator response is returned and processing stops. If the severity

Operator response
Determine whether all methods in the notification list
are valid.
EKG8584E THE CLASS class CANNOT BE System programmer response
CREATED UNDER THE RODM
SYSTEM CLASS sysclass. Delete the notification queue object and retry the
request.
Explanation EKG8586E THE OBJECT NAME object CANNOT
BE CREATED OR DELETED UNDER
The Resource Object Data Manager (RODM) does not
THE RODM SYSTEM CLASS NAME
allow classes to be created under RODM system
class.
classes.
class The user application cannot create or delete an object
The name of the class you are attempting to under some Resource Object Data Manager (RODM)
create. system classes.
sysclass
Message Variables
The name of the RODM system class.
object
System action The name of the object.
class
The name of the RODM system class.
and processing continues. System action
Operator response is returned and processing stops. If the severity

Operator response
Ensure that the parent class is not a RODM system
class. See IBM Z NetView Resource Object Data
Manager and GMFHS Programmer's Guide for more
information about RODM system classes. System programmer response
EKG8585E THE LINK WITH THE OBJECT Ensure that the class is not one of the RODM system
NAME object CANNOT BE classes which does not allow objects to be created.
CREATED. See IBM Z NetView Resource Object Data Manager and
GMFHS Programmer's Guide for more information
about RODM system classes.
Explanation
EKG8587E ONE OR BOTH OF THE FIELDS ARE
The notification queue object was created successfully
READ ONLY.
but the link to the user object failed.
Message Variables

One or both of the specified fields are Resource Object The specified field (with data type OBJECTLINK) is
Data Manager (RODM) read-only fields. already linked to another field, and can only be linked
to one field.
If the severity parameter is ERROR, a return code of 8 field
is returned and processing stops. If the severity The name of the Resource Object Data Manager
parameter is WARNING, a return code of 4 is returned (RODM) field.
System action
Operator response
Notify the system programmer. is returned and processing stops. If the severity
System programmer response and processing continues.
Ensure that neither of the fields is read-only and retry
the request. Operator response
EKG8588E THE primitive PRIMITIVE IS Notify the system programmer.

UNSUCCESSFUL DUE TO
SUBFIELD TIMESTAMP ERROR. System programmer response
Either delete the original link and retry the request, or
Explanation ignore this message and allow the original link to
The system cannot update the value of the remain.
TIMESTAMP subfield. There might not be enough EKG8590E THE RODM SYSTEM CLASS class
storage. CANNOT BE DELETED.
Message Variables
Explanation
primitive
The name of the Resource Object Data Manager An attempt was made to delete a universal class or a
(RODM) primitive statement. Primitive names system created class. These classes cannot be
which might incur this error are: deleted.
• IS_LINKED_TO Message Variables
• IS_NOT_LINKED_TO class
System action (RODM) class.
is returned and processing stops. If the severity System action
parameter is WARNING, a return code of 4 is returned If the severity parameter is ERROR, a return code of 8
and processing continues. is returned and processing stops. If the severity
Operator response and processing continues.
Operator response
Allocate additional storage to RODM, then retry the
request. System programmer response
Ensure that the class name is not a RODM system
EKG8589E THE FIELD NAME field IS ALREADY
class.
LINKED TO ANOTHER FIELD
NAME. EKG8591E THE RODM METHOD method
CANNOT BE DELETED.

The request to delete the specified method was Notify the system programmer.
rejected because the method is currently referenced
by other entities. System programmer response
Message Variables Retry the request.
method EKG8593E THE FIELD NAME field SPECIFIES
The name of the Resource Object Data Manager THE NULLMETH OBJECT AS THE
(RODM) method. NAMED-METHOD TO BE
TRIGGERED.
System action
is returned and processing stops. If the severity The field name on the primitive has specified the
parameter is WARNING, a return code of 4 is returned NullMeth object as the named-method to be triggered
and processing continues. with the INVOKED_WITH primitive. For this primitive,
the object specified by the field cannot be the
Operator response NullMeth object, but must be a valid named-method
object.
Message Variables
System programmer response field
Ensure that the method is not referenced by other The name of the field specified on the primitive
entities and retry the request. indicating the named-method to be triggered.
EKG8592E THE primitive PRIMITIVE IS

System action
UNSUCCESSFUL DUE TO A LOCK
FAILURE. If the severity parameter is ERROR, a return code of 8
Explanation parameter is WARNING, a return code of 4 is returned
The request was rejected because the required
resources are currently locked by another application.
Operator response
Message Variables
primitive
The name of the rejected primitive. System programmer response
Ensure that the indicated field contains a value for a
System action
valid method object. Retry the primitive.

Chapter 5. EKGK Prefix Messages
EKGK prefix messages are issued by the RODM unload function (EKGKUNLD).
EKGK0001E An error occurred initializing the EKGK0005I Disconnected from RODM
EKGKUNLD messages
Explanation
Explanation
The RODM unload function (EKGKUNLD) successfully
The RODM unload function (EKGKUNLD) messages are disconnected from RODM.
not initialized because an error occurred.
EKGK0006E Cannot disconnect from RODM
Operator response
Operator response
See message EKGK0002E for the return code and
EKGK0002E Return/reason codes from RODM: reason code associated with the failure.
return_code/reason_code
EKGK0009E Cannot find SYSIN DD file
specified in the JCL
Explanation
The RODM unload function (EKGKUNLD) issued a Explanation
function call to RODM. For each function call made to
The RODM unload function (EKGKUNLD) attempted to
RODM, the RODM program returns a return code and
open the file specified but cannot find the file.
reason code. The reason code gives you more specific
information.
Operator response
Message Variables
Verify that the JCL is correct and that the SYSIN DD file
return_code specified is valid.
RODM return code.
reason_code EKGK0010E No parameters found in SYSIN DD
RODM reason code. file
See the NetView online help for a description of the The SYSIN DD file was found but no parameters were
RODM return and reason codes. found in the file.
EKGK0003I RODM version identifier is Operator response

identifier
Verify that the JCL is correct and that the SYSIN DD file
specified is valid.
Explanation
EKGK0011E The RODM parameter is longer
The identifier is obtained from RODM and identifies the
version and release of the RODM to which you are than 8 characters
connected.
Operator response
Message Variables
Correct the specification for the RODM parameter.
identifier
RODM version and release level. EKGK0012E The RODM parameter must be
specified
EKGK0004E Cannot connect to RODM
Explanation
Operator response
The value for the RODM parameter is missing.
reason code for the connection failure.

Specify a valid value for the RODM parameter. Contact your system programmer.
EKGK0013E The CLASS parameter is longer
than 64 characters System programmer response
Free system resources and retry.
Operator response
EKGK0020E The class name specified by the
Correct the specification for the CLASS parameter. CLASS keyword is not found:
class_name
EKGK0014E The DEPTH parameter is not valid.
Valid values are ONE and ALL.
Explanation
Operator response The RODM unload function (EKGKUNLD) queries
RODM for the class name specified by the CLASS
Correct the specification for the DEPTH parameter. keyword. The class name was not found in RODM.
EKGK0015E The WRITEMODE parameter is not Message Variables
valid. Valid values are APPEND
and OVERWRITE. class_name
RODM class name.
Operator response
Operator response
Correct the specification for the WRITEMODE
parameter. Correct the class name and retry.
EKGK0016E The WHITESPACE parameter is EKGK0021E An error occurred during a RODM

not valid. Valid values are LOW query
and HIGH.
Operator response
Operator response See message EKGK0002E for the return code and
Correct the specification for the WHITESPACE reason code for the failure.
parameter. EKGK0033E An error occurred querying the
EKGK0017E The REPORTONLY parameter is contents of a subfield
not valid. Valid values are NO and
YES. Operator response
Operator response reason code for the failure.
Correct the specification for the REPORTONLY EKGK0034E Cannot access file for DD filename
parameter.
EKGK0018E The keyword specified in the Explanation
SYSIN DD file is not valid: keyword
The 6 output data sets are specified in the start JCL
with the following DD statements:
Explanation
CLASSES
Valid keywords are RODM, CLASS, OBJECT, DEPTH, Class structure creation high level syntax.
WRITEMODE, WHITESPACE, and REPORTONLY.
CLASSVAL
Message Variables Class subfield creation and value setting
primitives.
keyword
The keyword in error in the SYSIN DD file. OBJECTS
Object creation primitives.
Operator response OBJVAL
Object subfield value setting primitives.
Correct the specification for the keyword.
LINKS
EKGK0019E EKGKUNLD memory allocation Link primitives.
failed

REPORT EKGK0038I Attempted to unload a ClassID
Summary report of RODM data. that does not exist
Message Variables
Explanation
filename
The DDNAME of the file in error. The RODM unload function (EKGKUNLD) queried
RODM for a ClassID and the ClassID was not found.
Operator response EKGK0039I Attempted to unload an ObjectID
Verify that the JCL correctly specifies the DD file. that does not exist
EKGK0035I RODM unload function processing Explanation

is complete
The RODM unload function (EKGKUNLD) queried
RODM for an ObjectID and the ObjectID was not
Explanation
found.
Processing is complete with return code 0.
EKGK0040I Attempted to unload a list of
EKGK0036E An error occurred and processing ClassIDs that do not exist
is halted
Explanation
Explanation
The RODM unload function (EKGKUNLD) queried
A non-zero return code has occurred and processing is RODM for a list of ClassIDs and none of these were
halted. found.
EKGK0041I Attempted to unload a list of
Operator response
ObjectIDs that do not exist
Review previously logged errors to determine the
cause of the error. Explanation
EKGK0037E The field data type cannot be The RODM unload function (EKGKUNLD) queried
printed RODM for a list of ObjectIDs and none of these were
found.
Explanation EKGK0042I The OBJECT parameter is longer
The data type is either one that cannot be printed such than 254 characters
as ANONYMOUS or is not a valid RODM data type.
Operator response
Operator response Correct the specification for the OBJECT parameter.
If the data type is valid, no action is necessary. If the
data type is not valid, contact IBM Software Support.
Chapter 5. EKGK Prefix Messages 367

Chapter 6. EKGV Prefix Messages
EKGV prefix messages are issued by the RODMView program.

Messages EKGV68000-EKGV68002 are issued to the console. These messages come directly from
RODMView command processors. All other EKGV messages are displayed to the operator while running
the RODMView program.
When messages EKGV0000-EKGV8000 are displayed, they include return and reason codes from the
RODM program. For additional information on the RODM program reason and return codes, see the IBM Z
NetView Resource Object Data Manager and GMFHS Programmer's Guide.
EKGV0000I Request is successful (return/ Operator response
reason) Restart RODM or connect to a different RODM and
then retry the request.
Explanation
EKGV0007E Request failed. Required
The request completed successfully. resources are locked (return/
Message Variables reason)
return
Operator response
RODM return code.
reason Retry the request later.
RODM reason code. EKGV0009E Request failed. User ID not
EKGV0001E Request failed. RODM is authorized (return/reason)
checkpointing (return/reason)
Operator response
Operator response Contact your system administrator.
Retry the request. EKGV0013E Request failed. Specified RODM is
EKGV0002E Request failed. RODM is starting not found (return/reason)
(return/reason)
Operator response
Operator response Start the specified RODM and then retry the request.
Retry the request. EKGV0014E Request failed. User ID not signed
EKGV0003E Request failed. RODM is stopping on (return/reason)
(return/reason)
Operator response
Operator response Connect to RODM and get a valid sign-on token. Retry
Restart RODM or connect to a different RODM and the request.
then retry the request. EKGV0015E Request failed. Too many active
EKGV0005E Request failed. RODM has stopped API calls (return/reason)
(return/reason)
Operator response
Operator response Retry the request later.
Restart RODM or connect to a different RODM and EKGV0020E Request not complete. Abend has
then retry the request. occurred (return/reason)
EKGV0006E Request failed. RODM has stopped
(return/reason) Operator response
Contact your system administrator.

See the IBM Z NetView Troubleshooting Guide. return
RODM return code.
EKGV0024E Request failed. Methods are not
triggered (return/reason) reason
RODM reason code.
Operator response EKGV0052E Request failed. Class does not
exist (return/reason)
Ensure all methods in the notification list are valid.
EKGV0025E Request failed. Data is being Operator response
checkpointed (return/reason)
Correct the class or parent class. Retry the request.
Operator response EKGV0053E Request failed. Class has class
children (return/reason)
Retry the request later.
EKGV0026I The new data is the same as the Operator response
old data (return/reason)
Correct the primary parent class. Retry the request.
Explanation EKGV0054E Request failed. Object does not
exist (return/reason)
The new data value is the same as the old data value.
No change took place.
Operator response
Message Variables
Correct the object data. Retry the request.
return
RODM return code. EKGV0056E Request failed. Field does not
reason exist (return/reason)
RODM reason code.
Operator response
EKGV0028E RODM log files are not available
(return/reason) Correct the field data. Retry the request.
EKGV0057E Request failed. Parent has no
Operator response object children (return/reason)
Contact the system administrator.
Operator response
EKGV0040E Primary inheritance already exists
(return/reason) Correct the primary parent class data. If the primary
parent class data is correct, verify the class ID portion
of the object ID. Retry the request.
Explanation
EKGV0060E Request failed. Objects exist.
The system does not change the field value because
the field already contains the primary inheritance (return/reason)
value.
Operator response
Message Variables
Delete descendent objects. Retry the request.
return
RODM return code. EKGV0063E Request failed. System cannot
reason load method (return/reason)
RODM reason code.
Operator response
EKGV0041E Request failed. Field is locally
defined (return/reason) Verify that the method exists in the method library.
EKGV0066E The new data and field types are
Explanation different (return/reason)
The system rejects the request because the field is
locally defined.

Correct the data type or field. Retry the request. This user ID is already connected to RODM, either
through RODMView or another program accessing
EKGV0067E Function does not apply to a RODM.
system field (return/reason)
Message Variables
Operator response return
Correct the function ID or the field. Retry the request. RODM return code.
reason
EKGV0072E The two target objects are already RODM reason code.
linked (return/reason)
Operator response
Operator response
Try proceeding normally. If RODMView requests fail
Correct the entity and field information. Retry the and issue message EKGV0014E, try signing on with
request. another user ID.
EKGV0073E The two target objects are EKGV0086E Class name is reserved or not valid
identical (return/reason) (return/reason)

Objects cannot be linked to themselves with the same Correct the class name. Retry the request.
field.
EKGV0087E Class name is used by another
Message Variables
class (return/reason)
return
RODM return code. Operator response
reason
Correct the class name. Retry the request.
RODM reason code.
EKGV0089E The class cannot be deleted
Operator response (return/reason)
Correct the entity information. Retry the request.

Explanation
EKGV0074E The operation is not valid on the The universal or a system-created class cannot be
field (return/reason) deleted.
Correct the field information. Retry the request. return

RODM return code.
EKGV0075E Request failed. The two objects reason
are not linked (return/reason) RODM reason code.

Correct the field information. Retry the request. Correct the class information. Retry the request.
EKGV0081E Request failed. Method is not EKGV0090E Delete failed. Entities exist under
installed (return/reason) this class (return/reason)

Install the specified method. Retry the request. Delete all entities under the specified class. Retry the
EKGV0084E This user ID is already connected request.
to RODM (return/reason) EKGV0091E Field name is not valid or is
reserved (return/reason)
Chapter 6. EKGV Prefix Messages 371

Correct the field name. Retry the request. Unlink all other objects from the specified object.
Retry the request.
EKGV0092E The field exists under this class
(return/reason) EKGV0127E User ID is not authorized to use
this RODM (return/reason)
Operator response
Operator response
Correct the field data. Retry the request.
Verify the user ID or contact the system administrator.
EKGV0098E System field cannot be deleted
(return/reason) EKGV0128E Password is not authorized or has
expired (return/reason)
Operator response
Operator response
Correct the field information. Retry the request.
Verify the password or password phrase. Retry the
EKGV0103E Field does not exist under request
specified class (return/reason)
EKGV0139E Field information is not valid
Correct the class or field information. Retry the

Operator response
request.
Specify a valid field ID or a valid field name. Retry the
EKGV0104E Specified subfield already exists request.
(return/reason)
EKGV0140E Class name and ID are not valid
EKGV0108E The method is in use (return/
(return/reason)
reason)
Operator response
Explanation
Specify a valid class ID or a valid class name. Retry the
Subscriptions using this method must be deleted
request.
before the method can be deleted.
EKGV0142I Local copy is created (return/
Message Variables
reason)
return
RODM return code. Explanation
reason
The system performs the request successfully and a
RODM reason code.
local copy is created.
Retry the request later. return

RODM return code.
EKGV0109E Object name is not valid or is
reason
reserved (return/reason)
RODM reason code.
Operator response EKGV0143I Returned field value is inherited

(return/reason)
Correct the object name. Retry the request.
EKGV0110E Object name already exists under Explanation
this class (return/reason)
The field value is inherited and does not contain a local
copy.
Operator response
Message Variables
Correct the object name. Retry the request.
return
EKGV0111E The object is linked to other RODM return code.
objects (return/reason)

reason Message Variables
RODM reason code.
return
EKGV0144E System fields cannot be deleted RODM return code.
(return/reason) reason
RODM reason code.
Operator response
EKGV0179E Cannot create the object (return/
Correct the field or subfield information. Retry the reason)
request.
EKGV0145E The specified field is read-only Operator response
(return/reason) Retry the request later.
EKGV0186E Cannot create classes under the
Operator response
system classes (return/reason)
Correct the field or subfield information. Retry the
request. Operator response
EKGV0146E The subfield does not exist Correct the parent class information. Retry the
(return/reason) request.
EKGV0194E The method has an execution error
Operator response
(return/reason)
Correct the subfield information. Retry the request.
EKGV0148I Subfields cannot be created on Operator response
system fields (return/reason) The method has abended. Check the RODM log record
for further information.
Operator response
EKGV0195E Cannot change system fields at
Correct the field information. Retry the request. the class level (return/reason)
EKGV0150E Object ID or name information is
not valid (return/reason) Operator response
Correct the data. Retry the request.
Operator response
EKGV0200E Request failed. RODM is quiescing
Specify a valid object ID or a valid object name. Retry (return/reason)
the request.
EKGV0170E You cannot create or delete Operator response
system objects (return/reason) Retry the request later.
EKGV0224E Field data type cannot be created
Operator response
as indexed (return/reason)
Correct the parent class information. Retry the
EKGV0176E The new data is not valid (return/ Only CHARVAR and INDEXLIST field data types can be
reason) created as indexed fields.
Message Variables
Operator response
return
Correct the new data. Retry the request.
RODM return code.
EKGV0178E This user ID is already connected reason
to RODM (return/reason) RODM reason code.

The user is already connected to RODM. Correct the field data type and retry.

EKGV0225E Locate datatype does not match Operator response
field or field non-indexed (return/ Specify a Class name, Class ID, or Object ID.
reason)
EKGV8009E The value is not valid. The Object
Explanation ID is 16 hex digits.
The field being used to locate objects first be created

Operator response
with the CHARVAR or INDEXLIST data type, and must
also be an indexed field. The datatype specified on the Specify a valid object ID.
locate command must also match the datatype of the
EKGV8012E The NetView command processor
field.
did not respond
Message Variables
return Explanation
RODM return code. NetView program timed out waiting for a reply from a
reason RODMView command processor.
RODM reason code.
Operator response
Operator response
Retry the request. If the error persists, contact your
Correct the field data type and retry. system programmer.
EKGV8001E Specify an option by number
Operator response Browse the system log to determine the reason for the
error. A common cause of this error is that the
Specify a valid option number as listed on the panel or command processor is not correctly defined to
place the cursor on an option and press the enter key. NetView program. Correct the error and then retry the
EKGV8002E The RODM name field is blank request.
EKGV8013I The query output is copied to the
Operator response netlog
Specify the RODM name.
Explanation
EKGV8003E The user ID field is blank
This message confirms that the query output has been
copied to the netlog as you requested.
Operator response
Specify a RODM user ID. EKGV8014E The Class name and the Class ID
are blank
EKGV8005E The RODM function field is blank
Operator response
Operator response
Specify a Class name or Class ID.
Specify the RODM function. Valid functions are
COnnect, Disconnect, CHeckpoint, or Stop. Only the EKGV8015E The Object name and the Object ID
capitalized letters of the function needs to be entered. are blank
EKGV8007E The RODM function is not valid Operator response

Specify the Object name or the Object ID.
Operator response
Specify a valid RODM function. Valid functions are EKGV8018E The Field name and the Field ID
COnnect, Disconnect, CHeckpoint, or Stop. Only the are blank
capitalized letters of the function needs to be entered.
Operator response
EKGV8008E The Class name, Class ID, and
Object ID field are blank Specify the field name or the field ID.
EKGV8021E Cannot create a child class and
field name at the same time

Create the child class first and then create the field. This is a prompt to enter the find request. If you are
not familiar with the find command, enter F to display
EKGV8022E Cannot create a child class and find usage help.
object name at the same time
EKGV8037E RODM Return code/reason code is
Create the child class first and then create the object.
Explanation
EKGV8023E Data type outside of a SelfDefining The return and reason codes are returned from RODM.
string is not valid This particular combination does not have a message
associated with it, so see the NetView online help for
Explanation more information on the return code and reason code
This data type is only valid inside a SelfDefining string, pair.
or is a RODM reserved data type. See the NetView Message Variables
online help for a more complete explanation of RODM
abstract data types that are allowed outside self- return
defining strings. RODM return code.
reason
Operator response RODM reason code.
Specify a different field data type.

Operator response
EKGV8026E Cannot delete an object's field See the NetView online help for a more complete
explanation of the return and reason code pair.
Operator response
EKGV8039E Cannot create a field on an object
Specify the object name field as blank and then retry
the request.
Operator response
EKGV8030I The command is complete Make the Object Name field blank and then retry the
request. You can only create a field on a class.
Explanation
EKGV8040E The parent class name and parent
The command is complete. class ID fields are blank
EKGV8033I Find usage is F searchstring
<PREVious> Operator response
Specify a parent class name or parent class ID.
Explanation
EKGV8041E The child class, object name and
Searchstring is the text string to find. Your search field name fields are all blank
string cannot contain blanks. To search backwards,
specify PREVious.
Operator response
Operator response Specify a child class, object name, or field name.
Specify the FIND command. EKGV8042E The Method type field is blank
EKGV8034I Characters are found

Operator response
Explanation Specify a valid method type. Valid types are NAMED or

OI.
The FIND request has successfully located the
specified search string. The found text is as close to EKGV8046I No query output currently exists
the top of the panel as is possible.
Explanation
EKGV8035I Specify the find request or specify
F for help information on the find You requested that a previous query's output be
command. displayed, but no query output exists.

EKGV8047E Display request return code is rc EKGV8052E The Field data value is not a valid
hex value.
Explanation
Operator response
The RODMView screen cannot be displayed.
Specify a valid hexadecimal value. Valid values are
Message Variables
strings that include the numbers 0—9 and the
rc characters A—F.
VIEW command return code.
EKGV8053E A blank User password is not valid
with the User ID specified
Operator response
Contact your system programmer. Explanation
The specified user ID requires a non-blank password
System programmer response or password phrase unless the specified user ID is the
See the NetView online help for a more complete same as the NetView operator ID.
explanation of the return code displayed in the
message. Operator response
EKGV8049E Length of all input concatenated Specify a valid password.
together is greater than allowed
EKGV8054E The Class Name specified cannot
be found
Explanation
RODMView concatenates fields that are specified to Operator response
build a command. The maximum length of the
Specify a valid or blank class name.
command is 240 characters. You might encounter this
more frequently if you use full textual names for EKGV8055E The Field Name field specified
classes and objects. cannot be found

Use enough object and class IDs to reduce the overall Specify a valid or blank field name.
length of the command or use the compound query
function to issue the query. Be sure to clear out any EKGV8059E Field information cannot be
previous input from the second and third compound specified with GMFHS method
query panels with the PF4 key. invocation
EKGV8050E The function key is not defined. Operator response
Operator response Erase the field name or field ID information or both for
object 1 and object 2 specifications and retry the
Use one of the functions keys listed at the bottom of request.
your screen.
EKGV8060E Place cursor on an object ID to
EKGV8051E The Maximum lines returned field copy, press PF10 for destinations
is not valid.
Explanation
Explanation
PF10 was pressed while the cursor was not on a valid
The Query request displays the maximum number of object ID on the query output panel.
lines as specified in the Maximum lines returned field.
If you specify 0, the RODMView program defaults to Operator response
5000.
Retry the request by placing the cursor on any one of
Operator response the 16 hex digits of an object ID and press PF10.
Specify a valid value for the Maximum lines returned EKGV8062I Object ID copied from query
field. output

The object ID was copied from query output to the See the command syntax, correct the error, and retry
input panel you chose. the request.
EKGV8063E The required field is blank or is not EKGV9002E A required parameter is not found
valid
Operator response
Explanation
See the command syntax, correct the error, and retry
A required field did not contain any information or the request.
contained information that was not valid. Valid entries
EKGV9003E A parameter is too long
are usually listed on the panel next to the field.
Operator response
Operator response
See the command syntax, correct the error, and then
Correct the field information and retry the request.
retry the command.
EKGV8064E Action canceled
EKGV9004E A keyword is not valid
Explanation
Operator response
You canceled the request.
EKGV8065I name_1 = name_2 (type) retry the command.
EKGV9005E Too many parameters exist
Explanation
This message contains the translation of the name to Operator response
its 'dotted decimal' number or vice versa.
Message Variables retry the command.
name_1 EKGV9006E An error occurred parsing the
The name that was found when you pressed PF11. parameters.
name_2
The name corresponding to name_1. Operator response
type Retry the command. If the error persists, contact IBM
Either class or field, describing if the name is a Software Support.
class or field name.
EKGV9007E A hex parameter contains a value
EKGV8066E Place cursor on a class/field, that is not valid
pressed PF11 for translation
Operator response
Explanation
If a parameter is to be entered in hexadecimal, it must
You pressed PF11 on query output data that had no contain an even number of hexadecimal digits. It
translation. cannot contain X' delimiters, and any leading zeroes
must be entered. Object ID and time stamp values
Operator response must contain exactly 16 hexadecimal digits. Correct
the hexadecimal parameter and retry the request.
Ensure you have the cursor on a class or field name or
'dotted decimal' number and retry the request. Note EKGV9010E Error with CNMVARS. Sign on to
that the name or dotted decimal number must be on a RODM again.
line by itself and cannot span more than one line in the
query output. Operator response
EKGV9001E Parameters cannot contain spaces Sign on to RODM again. If your signon is successful but
this error persists, contact IBM Software Support.
EKGV9011E The memory cannot be allocated.

Operator response the command processor was compiled. This message
can indicate either corrupt RODM data or a RODM
Retry the command. If the error persists, contact your
datatype that came into existence after your version of
system programmer.
RODMView was compiled. Attempt to issue the same
query from the command line (or using a REXX exec)
System programmer response and contact IBM Software Support with the output.
Browse the system log to locate error messages that EKGV9314E No match is found
indicate potential reasons why the memory cannot be
allocated. Correct the reason the memory cannot be
Explanation
allocated and then retry the command.
No entities are found that match the query criteria.
EKGV9013E The Sign_on_token is not valid.
Sign on to RODM again EKGV9320E Parent of object ID is not found
RODM sets the Sign_on_token field in your access The parent of the object ID is not found.
block after a successful connect. RODM detects that
this field has a value in your access block that is not EKGV9399E An error has occurred in module
valid when a RODM API function request is made. EKGVQUEM
Reconnect to RODM. Contact your system programmer.
EKGV9014E The keyword is not authorized System programmer response

Explanation
The keyword specified is not in your scope class EKGV9400E Resulting IndexList string is longer
definition. You are not authorized to use this keyword. than allowed
Contact your system programmer if you need to enter Adding the specified IndexList data to the data already
the keyword. contained in the field exceeds the allowed length of
32768 bytes.
EKGV9015E A blank user password is not valid
with user ID specified EKGV9699E An error has occurred in module
EKGVCREM
Explanation
Operator response
The specified user ID requires a non-blank password
unless the specified user ID is the same as the Contact your system programmer.
NetView operator ID.
Operator response Contact IBM Software Support.
Specify a valid password. EKGV9799E An error has occurred in module
EKGV9311E The data type passed to module EKGVDELM
EKGVRFLM is not valid
Operator response
Operator response Contact your system programmer.
Contact your system programmer.
System programmer response Contact IBM Software Support.
This message appears when RODM returns a response EKGV9899E An error has occurred in module
block containing a datatype that is not valid at the time EKGVMETM

Operator response reason
Corresponding message
67001
System programmer response EKGV9001E
67002
Contact IBM Software Support. EKGV9002E
EKGV9999E An error has occurred in module 67003
EKGVSUBM EKGV9003E
67004
Operator response EKGV9004E
Contact your system programmer. 67005
EKGV9005E
Contact IBM Software Support. EKGV9006E
67007
EKGV68001I return reason are the module EKGV9007E
return/reason codes.
67010
EKGV9010E
Explanation
67011
The return code and reason code are returned from EKGV9011E
the RODMView command processor.
67013
Message Variables EKGV9013E
return 67014
RODM or RODMView return code. EKGV9014E
reason 67015
RODM or RODMView reason code. EKGV9015E
module 67310
Failing command processor. EKGV9310E
67311
Operator response EKGV9311E
If module is RODM, then the return and reason return 67312
and reason codes are from RODM. See the IBM Z EKGV9312E
NetView Resource Object Data Manager and GMFHS 67313
Programmer's Guide for a more complete explanation EKGV9313E
of the return code and reason code pair. If module is
67314
one of:
EKGV9314E
• EKGVACTL 67315
• EKGVACTM EKGV9315E
• EKGVQUEM 67316
• EKGVLOCM EKGV9316E
• EKGVLNKM 67317
EKGV9317E
• EKGVCHGM
67318
• EKGVCREM EKGV9318E
• EKGVDELM 67319
• EKGVMETM EKGV9319E
• EKGVSUBM 67320
EKGV9320E
then the reason reason code came from a command
processor, and its explanation is a message: 67321
EKGV9321E

EKGV9322E
module
67323 Command processor name:
EKGV9323E
• EKGVACTL
67324
EKGV9324E • EKGVACTM
67325 • EKGVQUEM
EKGV9325E • EKGVLOCM
67398 • EKGVLNKM
EKGV9398E • EKGVCHGM
67399 • EKGVCREM
EKGV9399E
• EKGVDELM
67400
EKGV9400E • EKGVMETM
67699 • EKGVSUBM
EKGV9699E mod_level
67700 Command processor modification level.
EKGV9700E EKGV68003I function output follows: ... End of
67799 function
EKGV9799E
67899 Explanation
EKGV9899E
This is the text which precedes and the MLWTO
67999 message containing a successful query or locate
EKGV9999E output. This message is repeated at the end of the
display.
EKGV68002I module level mod_level syntax:
Message Variables
Explanation function
This message explains the command syntax for Either the Locate or Query function.
command_name.

Chapter 7. EZL Prefix Messages
EZL message prefixes apply to Automated Operations Network (AON) messages:

• The range EZL001-EZL899 is reserved for base AON error and information messages.
• The range EZL900-EZL999 is reserved for base AON panel messages.
• The range EZL1101-EZL2036 is reserved for base AON workstation interface messages.
The following message classes apply to the AON messages:
0
Errors
1
Down
2
Up
3
Degraded/Performance
4
Manual intervention required
7
Critical threshold exceeded
8
Frequent threshold exceeded
9
Infrequent threshold exceeded
10
Systems Network Architecture (SNA)
11
Virtual Telecommunications Access Method (VTAM) detects storage problem
12
X.25
15
Switched network backup (SNBU)
20
VTAM subarea automation
21
Network Control Program (NCP), LINKSTA
22
Line
23
Physical unit (PU)
24
Cross-domain resource manager
25
Cross-domain resources
26
Application (APPL)

27
Session
30
Local area network (LAN)
31
LAN manager (LANMGR)
32
LAN segment (LANSEGMENT)
33
LAN bridge (LANBRIDGE)
34
LAN controlled access unit (LANCAU)
35
LAN adapter (LANADAPTER)
50
Advanced peer-to-peer networking (APPN)
60
Transmission Control Protocol/Internet Protocol
61
IP router
62
Name server
65
NetView/6000 (NV6000)
66
NetView/6000 service point (NV6000 SP)
67
IP host
68
Interface
69
IP link
90
AON
EZL000E MESSAGE number ISSUED, BUT System programmer response
THIS MESSAGE DOES NOT EXIST If the message is correct, notify IBM Software Support
IN MESSAGE TABLE DSIMDEZL - about the missing message.
CALL IGNORED
EZL001I REQUEST request WAS
Explanation SUCCESSFUL FOR function
AON cannot find the specified user message.

Explanation
Message Variables
The specified request for the specified record
number completed successfully.
The missing message number
Message Variables

The name of the function
Notify your system programmer.
request
The name of the request

EZL002I END Explanation
The control file is currently using the specified
Explanation member. You receive this message after issuing the
This message identifies the end of a multiline message EZLCFG STATUS or POLICY REQ=STATUS command.
group. Message Variables
EZL003E RECOVERY PROCESSING CAN member
NOT BE PERFORMED. AON The name of the control file that is currently active
INITIALIZATION HAS NOT when only one file is loaded, or the name of the
COMPLETED. RELATED DATA: data logical file that is loaded when more than one
policy file has been defined in the CNMSTYLE
Explanation member.
AON was invoked to perform recovery processing for a EZL006I member FILE num = name
resource, but AON was still initializing.
data This message is part of a multiline message group

Data passed to AON which indicates the type of issued as a result of a POLICY REQ=STATUS or POLICY
recovery processing to perform REQ=LOAD command when more than one policy file
has been defined.
Recovery processing cannot be performed because member
AON was still initializing. The name of the logical file that is loaded when
more than one policy file has been defined in the
Operator response CNMSTYLE member.
num
The relative file number.
name
The real name of the policy file.
This message usually occurs infrequently and only
during AON initialization. It can be ignored. However, if EZL007I AUTOMATION TABLE table WAS
it occurs frequently, notify IBM Software Support and NOT LOADED SUCCESSFULLY
provide the data received. RECEIVED MESSAGE message
EZL004I REQUEST request WAS Explanation

UNSUCCESSFUL FOR function
The AUTOTBL command failed to load the specified
automation table. As a result, AON automation might
Explanation
stop processing.
The specified request for the specified function failed
Message Variables
to process.
table
Message Variables
The name of the automation table
request message
The name of the request The message ID and the text that explains the
function error that occurred when you tried to load the
The name of the function table
EZL005I MEMBER member CURRENTLY
BEING USED FOR THE CONTROL Operator response
FILE Notify your system programmer.

Check for a syntax error, an unknown command, or an
error generating the listing file for the Automation
Chapter 7. EZL Prefix Messages 383

table. To test the table, issue the AUTOTBL Explanation
MEMBER=table, TEST command. View the NETLOG for
A policy query expected to find the specified delimiter
errors. If there are no errors, check the NETLOG to
for the specified parameter, but it cannot.
determine why the listing file was not created.
Message Variables
EZL008I THE AUTOMATION TASK (task)
CANNOT BE STARTED - delimiter
AUTOMATION CANNOT PROCEED The character expected as the delimiter, for
example, ' (single quotation mark), " (double
Explanation quotation marks), or = (equal sign)
parameter
AON cannot resume processing because it cannot
The parameter missing the delimiter
start the specified task.
task Correct the command or the policy definition and
The name of the task attempt to query the policy again.
EZL013I MESSAGE TRUNCATED - 'text'
System action
AON initialization stops. Explanation
AON issued a multiline message that was truncated
Operator response
because the text of the message was too long to
Notify your system programmer. display. This message displays the first part of the
multiline message.
Check for missing TASK definitions, correct the text
problem, and initialize AON again. The first part of the multiline message
EZL009W TOO MANY PARAMETERS EZL015E INVALID DELIMITER OF delimiter
SPECIFIED ENCOUNTERED
You entered more parameters than are allowed for one You entered the specified delimiter, but the delimiter
of the operands used for the EZLCFG command. is not correct for the EZLCFG command.
Message Variables
Operator response
delimiter
Check the syntax for this command and issue the
The incorrect delimiter
command again, using the correct number of
operands.
Operator response
EZL010W TOO FEW PARAMETERS
SPECIFIED Issue the command again using the correct syntax.
EZL016I NAME = name
Explanation
You did not enter the minimum number of parameters Explanation
required for the operand used for the EZLCFG This message is the first part of a 2-part message. This
command. part displays the name of the common global variable
(CGLOBAL) that you requested.
Operator response
Message Variables
Issue the command again using the correct number of
name
parameters.
The name of the CGLOBAL
EZL011W EXPECTING A delimiter FOR
EZL017I VALUE=value
parameter

This message is the second part of a 2-part message. The test of the specified control file member was
This part displays the value of the common global successful.
value (CGLOBAL) that you requested.
Message Variables
Message Variables
member
value The policy definition member that was tested. This
The CGLOBAL value might be the actual member name in DSIPARM or
it might be a logical member name as defined in
EZL018I INVALID SEARCH RANGE the CNMSTYLE member. The name used depends
SPECIFIED on the command used and the CNMSTYLE
definitions.
Explanation
EZL025E SYNTAX ERROR IN MEMBER
You specified a search range that is greater than the member
ending search range.
Explanation
Operator response
A syntax error was encountered while attempting to
Issue the command again using the correct syntax. read the specified member.
EZL020E MACRO/TYPE REQUEST WAS Message Variables
UNSUCCESSFUL RC=rc | A=xx |
I=yy | ECB=zzz FOR function member
The policy definition member containing the error.
This might be the actual member name in
Explanation DSIPARM or it might be a logical member name as
AON cannot run the specified function. defined in the CNMSTYLE member. The name used
depends on the command used and the
Message Variables CNMSTYLE definitions.
rc
The return code from the function Operator response
xx Correct the member, and issue the command
The major return code from a VSAM or NetView again.The statement in error will be displayed in
request message EZL029E which acompanies this message.
yy
EZL026I TEST OF CONTROL FILE MEMBER
The minor return code from a VSAM or NetView
request member WAS UNSUCCESSFUL
zzz
Explanation
The event control block error code
function The test of a specified control file member failed.
The name of the function Message Variables
member
Operator response The policy definition member that was tested. This
Notify your system programmer. might be the actual member name in DSIPARM or
it might be a logical member name as defined in
System programmer response the CNMSTYLE member. The name used depends
on the command used and the CNMSTYLE
Find the VSAM return code and use problem definitions.
determination procedures. For more information about
VSAM messages, refer to the VSAM library. System programmer response
EZL023I TEST OF CONTROL FILE MEMBER Correct the control file entries and repeat the test.
member WAS SUCCESSFUL
EZL027I THE FOLLOWING ERRORS
ENCOUNTERED IN PROCESSING
MEMBER member

This message is the header of a multiline message. It task
precedes the list of errors that AON encountered while The name of the task or the operator ID
processing the specified member.
member AON issues the command to start the task.

The policy definition member containing the error.
This might be the actual member name in Operator response
DSIPARM or it might be a logical member name as
If AON cannot start the task, issue the START TASK
defined in the CNMSTYLE member. The name used
command to an operator that is not active, or issue
START TASK=task to start the task. The task can be
CNMSTYLE definitions.
one of the following:
EZL028I END OF member ERROR DISPLAY • EZLTLOG for the log file
• EZLTCFG for the control file
Explanation
• EZLTSTS for the status file
This message is the last line of a multiline message for
the specified member. • EZLTDDF for the Dynamic Display Facility (DDF)
Message Variables If you cannot start the task, notify your system
programmer.
member
The policy definition member containing the error. EZL031E SCREEN READ ERROR text
This might be the actual member name in
DSIPARM or it might be a logical member name as Explanation
defined in the CNMSTYLE member. The name used
AON encountered an error while reading the screen.
CNMSTYLE definitions. Message Variables
EZL029E text text
Additional information about the system action
Explanation
System action
The control file contains incorrect data.
AON runs the function again, unless the specified text
Message Variables includes the text -LIMIT EXCEEDED in the message. If
text the message includes the text -LIMIT EXCEEDED, AON
The statement that is in error. does not run the function again.
EZL032I task : log AUTOMATION LOG FULL
System action
AON processing continues. Explanation
The specified task found that the specified automation
Operator response log file is full.
Notify your system programmer. Message Variables
task
The task that detected the full log file.
Correct the data in the control file. For more log
information about the POLICY command, see the The name of the full log file. This file can be the
NetView online help. primary or secondary log file.
EZL030I task IS INACTIVE
System action
Explanation AON switches to the alternate log file.
The specified AON task is inactive.

EZL033E FIRST LEVEL OF THE TREE MUST message is issued during SDF initialization or while
BE A 1 AON is processing an SDFPANEL ADD command.

You defined the structure of a tree with a number Ensure that the root or status component specified in
other than 1. Specify the first level of the tree as a 1. the SDF STATUSFIELD statement for the panel being
loaded exists in the current SDF tree structure.
System action EZL039W TREE LEVELS OUT OF SEQUENCE
The EZLTDDF task is not active.
Explanation
System programmer response The tree levels that define the dependent subsystems
Ensure that your system tree definitions in the are out of sequence.
EZLTREE member start with a level number of 1. Issue
the START TASK=EZLTDDF command again. System action
EZL034E INVALID LEVEL - LESS THAN 1 The EZLTDDF task becomes active, but AON does not
determine the status of the subsystems.
Explanation
You defined the structure of a tree with a number that
is less than 1. Ensure that your system tree definitions in the
EZLTREE member start with a level number of at least
System action 1 and that all subsystems follow in hierarchical and
numerical order. Restart DDF.
The EZLTDDF task is not active.
EZL040I NO CONTROL FILE LOADED
Explanation
Ensure that your system tree definitions in the
EZLTREE member start with a level number of at least This message appears because you made a request to
1. Issue the START TASK=EZLTDDF command again. the control file when the control file member was not
loaded or you issued the EZLCFG STATUS command.
EZL036I BUFFER SIZE SPECIFIED IS TOO
SMALL FOR SCREEN Operator response
Explanation Load the control file member. Enter EZLCFG

MEMBER=member, where member is the control file
The size of the screen buffer specified in the EZLINIT member, for example, EZLCFG MEMBER=EZLCFG01.
member is too small for the screen.
EZL041I UNABLE TO FIND type name
Operator response
Explanation
An AON command, such as EZLCFG or DDF, cannot
find the specified information.
Message Variables
Increase the value of the SCREENSZ keyword in the
EZLINIT member in your NetView DSIPARM data set. type
Restart the DDF. The type of information that was passed to the
status file or the control file command processor
EZL037I STATUS ELEMENT IN TREE NOT
FOUND name
The name that was passed to the status file or to
the control file command processor
Explanation
AON cannot find the name of the root or status Operator response
component that is specified in an SDF STATUSFIELD
statement in the active SDF tree structure. This Notify your system programmer.

Review any recent changes to your control file or AON request
customized panel to ensure that they are syntactically A request sent by AON
correct, including any comments. If you are unable to module
resolve the error, record the information and contact The name of the module
rc
EZL042I MEMBER member NOT FOUND The return code

AON cannot find the specified member. Notify your system programmer.
Message Variables
member
The name of the member Record the information and contact IBM Software
Support.
Operator response EZL048E PANEL DEFINITION FOR panel
Verify that you use the correct name of the member NOT FOUND
when you issue the request.
Explanation
EZL043I task IS ACTIVE
AON requested the definition for the specified panel
but cannot find it.
Explanation
Message Variables
AON activated the specified task.
panel
Message Variables
The name of the panel
task
The name of the task Operator response
EZL044I task TERMINATING Notify your system programmer.

AON is ending the specified task. Note the name of the panel and contact IBM Software
Message Variables Support.
task EZL050I ACCESS DENIED - MAXIMUM

The name of the task USERS EXCEEDED FOR DDF
EZL045I task TERMINATED

Explanation
Explanation You have exceeded the maximum limit for logging on

to the Dynamic Display Facility (DDF).
The specified task stopped processing.
task AON denies access to DDF.
The name of the task
EZL046E INTERNAL PROGRAMMING Operator response
ERROR - REQUEST request Notify your system programmer.
MODULE module RETURN CODE rc
Explanation
Increase the value of the MAXOPS keyword entry in
AON sent a request to the specified program, but the the EZLINIT member in your NetView DSIPARM data
request failed. set. Restart DDF.

EZL054I REQUEST DENIED BECAUSE Explanation
NETVIEW IS TERMINATING The password data set is not allocated in the NetView
Job Control Language (JCL).
Explanation
The Dynamic Display Facility (DDF) is not responding. Operator response
The NetView program is stopping.

AON denies access to DDF. Add an EZLPSWD DD statement to the procedure to
EZL055I COMMAND DDF IS NOT allocate the VSAM data set.
SUPPORTED UNDER A NON-OST EZL063E ERROR OPENING PASSWORD
TASK DATASET
A program or an automated task ID tried to issue a AON cannot open the AON password data set.
DDF command, but only an operator can issue this
command.
Operator response
System action Notify your system programmer.
The DDF command is not issued.
EZL056E TERMINAL TYPE IS NOT
Ensure that the AON password data set is allocated
SUPPORTED BY DDF
correctly and is defined to NetView program.
Explanation EZL064I RECORD FOR data1 data2 NOT

FOUND
Extended terminal support requires the Dynamic
Display Facility (DDF) to display the panel successfully.
Explanation
EZL061I PASSWORD IS TOO length
The information for the specified data cannot be
found.
Explanation
Message Variables
You specified a new password with an incorrect length
on the GETPW command. Passwords must be a data1
minimum of 4 characters and a maximum of 8 A unique data identifier.
characters. data2
Message Variables A second unique data identifier.
length Operator response

Contains the value LONG or SHORT and explains
that there are too many or too few characters. If the data specified is an operator ID and a domain ID,
notify your system programmer. If the data specified
System action relates to another function, modify any filter settings
that are in effect. If the problem persists, notify your
The GETPW command fails. system programmer.

Reissue the command witha new password of the If the data specified is an operator ID and a domain ID,
correct length. use the INIT option to specify a password record for
the operator on the domain. For any other data,
EZL062I NETVIEW PASSWORD DATASET
browse the netlog for informational messages, and
NOT ALLOCATED
ensure that the relevant function has initialized
successfully.

EZL065I CURRENT PASSWORD IS current Operator response
Explanation
AON retrieved the specified current password from the System programmer response
password data set. AON suppresses this message, but the routines that
Message Variables perform cross-domain logons can still use it.
current EZL069E NEW PASSWORD UPDATE FAILED
The current password - NO NEW PASSWORD

Notify your system programmer. VSAM cannot update the current password held in the
VSAM data set to the new password because no
System programmer response password has been assigned.
Ensure that the message is suppressed so that it does

Operator response
not appear in the log or on an operator terminal.
EZL066I CURRENT/NEW PASSWORD IS
current/new
Explanation Wait until the password expires before issuing the
UPDATE parameter, or use the REGEN parameter to
The GETPW command randomly generated the generate a new password.
specified new password because the current
password was last updated more than 30 days ago. EZL072E request ERROR PROCESSING
VSAM DATASET
Message Variables
current Explanation
The current password
AON issued a VSAM macro and received an error while
new processing a request.
The new password
request
Operator response The name of the VSAM macro request that was
processing when the error occurred.
System action
The GETPW command fails and does not perform its
AON suppresses this message, but the routines that function.
perform cross-domain logons can still use it. Change
the RACF® password for the affected user. Operator response
EZL067E CURRENT PASSWORD IS Notify your system programmer.
password - ERROR CREATING
NEW PASSWORD
Explanation Browse the NETLOG for the specific VSAM error

message that signaled the error. Refer to the VSAM
This message displays the current password. The reference manuals to correct the error. If the error
password record was last updated more than 30 days persists, contact IBM Software Support.
ago, but the GETPW command cannot generate a new
one. EZL076I PASSWORD MASK IS TOO LONG
Message Variables
Explanation
password
The current password The mask for the password is too long.

System programmer response EZL113I DATA IS data
Correct the PWMASK keyword in the control file.
Explanation
EZL077I PASSWORD MASK IS TOO SHORT
This message is part of a multiline message group that
starts with message EZL111I and follows message
Explanation
EZL112I.
The mask for the password is too short.
Message Variables
System programmer response data

The data associated with the active type displayed
Correct the PWMASK keyword. in message EZL112I.
EZL090I IPLDATE = MM/DD/YY , IPLTIME = EZL115I Entry Type Keyword Value
HH:MM
Explanation
Explanation
This message is part of a multiline message group
AON issues this message at startup to establish the issued as a result of a POLICY REQ=GET command.
system startup time.
Message Variables
EZL110I controlfile BEING USED FOR THE
CONFIGURATION TABLE Entry
The policy name
Explanation Type
The policy definition
You loaded the specified control file. This message is
Keyword
the beginning of a multiline message. You will also see
The policy keyword
one or more EZL006I messages that list the Policy
Files used to load the Policy Repository. Value
The value of the policy keyword
Message Variables
EZL150I STATISTICS DISPLAY REQUEST
controlfile
FOR highest THROUGH lowest
The name of the control file (if it is the only file), or,
the name of the logical file loaded when more than
one policy file has been defined in the CNMSTYLE Explanation
member. This message is the header for a multiline message
EZL111I AUTOMATION CONFIGURATION that displays statistics from a higher-node resource
DISPLAY - ENTRY= entry and a lower-node resource.
Message Variables
Explanation highest
This is the first message of a multiline message group The name of the highest resource
that displays the entry for the current automation lowest
configuration. The name of the lowest resource
Message Variables EZL151I ID= resource, TYPE= type,
entry STATUS= status
The entry for the current automation configuration.
Explanation
EZL112I ACTIVE TYPE= type
Explanation starts with message EZL150I and displays the ID, the
type, and the status of the specified resource.
starts with message EZL111I. This message is also used as a single line message by
NETSTAT to update DDF if the "Send to DDF" option is
Message Variables chosen.
type Message Variables
The type of entry AON found in the control file.

resource Explanation
The name of the resource
type starts with message EZL150I. This message states
The type of resource whether an operator has been notified of the current
status error.
The status of the resource Message Variables
EZL152I LAST UPDATED BY OPERATOR notify
operatorid The message that notifies the operator. The
possible answers are Y (Yes) and N (No).
Explanation
EZL156I LAST STATUS CHANGE DATE =
This message is part of a multiline message group that date, TIME = time, OPID= id
starts with message EZL150I. This message specifies
the last operator to update the resource. Explanation
operatorid This message displays the ID of the operator that last
The ID of the operator who last updated the updated this record, as well as the time and date when
resource the operator updated it.
EZL153I LAST THRESHOLD EXCEEDED - Message Variables
threshold
date
The date of the last status change
Explanation
time
This message is part of a multiline message group that The time of the last status change
starts with the message EZL150I. The last threshold
setting was exceeded. id
The ID of the operator who updated the record
Message Variables
EZL157I LAST MONITORED DATE = date
threshold TIME = time
The last threshold setting for the resource
EZL154I REPLYID = reply, JOB TYPE = type, Explanation
NUMBER = number, NAME = name
This message displays the time and date that AON last
monitored this resource.
Explanation
Message Variables
starts with message EZL150I. This message displays date
the maximum number of errors allowed. NetView The date AON last monitored the resource
Access Services uses this information to set the time
information needed to reply to the next request for The time AON last monitored the resource
NetView Access Services.
EZL159I NO ERROR DATA AVAILABLE
Message Variables
reply Explanation
The reply ID
This message is part of a multiline message group
type starting with message EZL150I. There is no error data
The type of job available for the resource.
number EZL160I ERROR COUNT DATE TIME
The maximum number of errors allowed
name Explanation
The name of the NetView Access Services as
defined for the NetView on which the user is This message is part of a multiline message group
running starting with message EZL150I. This message is the
header line for message EZL161I.
EZL155I OPERATOR NOTIFIED: notify,
TIMERSET: EZL161I count date time

This message is part of a multiline message group This message is part of a multiline message that
starting with message EZL150I. This message shows begins with message EZL150I.
the current error count, date, and time of the last
Message Variables
error.
user1
Message Variables
User data
count user2
The sequence number of the error User data
date
EZL171I USER3= user3, USER4= user4
The date the error occurred
time
Explanation
The time the error occurred
This message is part of a multiline message that
EZL162I HIER 1= hierarchy1,2= begins with message EZL150I.
hierarchy2,3= hierarchy3
Message Variables
Explanation user3
This message displays the hierarchy for a resource. User data
user4
Message Variables
User data
hierarchy1
The name of the Network Control Program (NCP) in EZL172I USER5= user5, USER6= user6
the NetView Hardware Monitor Alert Hierarchy
Explanation
hierarchy2
The name of the line (LINE) in the NetView This message is part of a multiline message that
Hardware Monitor Alert Hierarchy begins with message EZL150I.
hierarchy3 Message Variables
The name of the physical unit (PU) in the NetView
Hardware Monitor Alert hierarchy user5
User data
EZL163I ALTPORT= altport,POOL= pool, user6
SPEED= speed, LEVEL= level User data
Explanation EZL173I USER7= user7, USER8= user8
This message is part of a multiline message that

Explanation
begins with message EZL162I. This part of the
message displays the switched network back-up This message is part of a multiline message that
(SNBU) setup information for the resource. begins with message EZL150I.
altport user7
The port to use when not using the primary port User data
pool user8
The modem pool for SNBU User data
speed EZL174I USER9= user9, USER10= user10
The speed of the modem
level Explanation
The modem link segment in a tailed circuit,
specified as 1 (local) or 2 (remote). This message is part of a multiline message that
begins with message EZL150I.
EZL170I USER1= user1, USER2= user2
Message Variables

user9 AON uses the default color defined for the priority
User data of the status descriptor. The colors are:
user10 B
User data Blue
EZL180I domain restype STATUS G
INFORMATION Green
P
Explanation Pink
This message is the header line of a multiline message R
that results from a query request the operator sent to Red
the Dynamic Display Facility (DDF). T
Turquoise
Message Variables
W
domain White
The domain for the resource
Y
restype Yellow
The type of resource
highlight
EZL181I rootname.compname,PR=priority, The highlighting associated with the status
RV=refvalue, CO=color, descriptor. The highlighting options are:
HL=highlight, DP=dupcount
B
Blink
Explanation
N
AON found a status descriptor that matches the search Normal
arguments in a request to use status descriptor
R
information. This message identifies the status
Reverse
descriptor and shows some of the information it
contains. This message is the first message line in the U
multiline response to the DDFQUERY command. Underscore
Messages EZL182I, EZL183I, and EZL185I show dupcount
additional information contained in the status The number of duplicate status descriptors that
descriptor. exist. Duplicate status descriptors have identical
Message Variables reference value, priority, information, color,
highlight, and data values.
rootname
The root (system) name of the requested status
System action
component.
compname Processing continues.
The status component name. If the alternate EZL182I DATE=date,TIME=time,REPORTER
status component name was used to locate the = reporter,PU=pu,PD=pd,
status descriptor, it appears in parentheses PLVU=plu,PLVD=pld
following the primary status component name.
priority Explanation
The priority associated with the status descriptor.
This priority is normally specified in a request to AON found a status descriptor that matches the search
add the status descriptor to the chain of arguments in a request to use status descriptor
descriptors for a status component. information. This message shows some of the
information contained in the status descriptor and is
refvalue
the second message line of the multiline response to
The reference value for the status descriptor.
the DDFQUERY command. Messages EZL181I,
color EZL183I, and EZL185I contain additional information
The variable color shows the color associated with contained in the status descriptor.
the status descriptor. If you do not specify this
color in the request to add a status descriptor, Message Variables

date Message Variables
The date when the status descriptor was created.
information
The date is shown in the mm/dd/yy format.
The value used to replace the default STATUSTEXT
time information when the status descriptor is used as
The time when the status descriptor was created. the basis for the STATUSFIELD and a status
The time is shown in the hh:mm:ss format. descriptor number other than 0 is specified in the
reporter STATUSFIELD definition.
The NetView operator ID that made the request to
create the status descriptor. The node of the System action
reporter, if available, appears in parentheses
immediately following the operator ID.
pu EZL185I DA=data
Shows whether the status condition is propagated
upward through the SDF tree structure. The Explanation
possible values are:
A status descriptor has been found that matches the
Y search arguments in a request to use status descriptor
Upward propagation was requested. information. This message shows some of the
N information contained in the status descriptor. This
Upward propagation was not requested. message is the fourth message line of the multiline
response to the DDFQUERY command. Messages
pd EZL181I, EZL182I, and EZL183I show additional
Indicates whether the status condition is information contained in the status descriptor.
propagated downward through the SDF tree
structure. The possible values are: Message Variables
Y data
Downward propagation was requested. The data displayed when the status descriptor is
N selected as the basis for a detail display
Downward propagation was not requested.
System action
plu
The tree node past which upward propagation is Processing continues.
not performed. An asterisk (*) indicates that
upward propagation ends at the root (system) EZL199I THE CHARACTER 'char' IS NOT
node. VALID IN value
pld
Explanation
The tree node past which downward propagation is
not performed. An asterisk (*) indicates that The characters specified can not be used in the
downward propagation is performed to all specified value.
subordinate nodes of the status component.
Message Variables
System action char

The character that is not allowed
value
EZL183I IN=information The value that contained the character in error
EZL198I PARAMETER INVALID FOR
Explanation COMMAND command
AON found a status descriptor that matches the search
arguments in a request to use status descriptor Explanation
information. This message shows some of the
A parameter that was passed to the specified
information contained in the status descriptor. This
command is incorrect.
message is the third message line of the multiline
response to the DDFQUERY command. Messages Message Variables
EZL181I, EZL182I, and EZL185I show additional
command
information contained in the status descriptor.

The command fails and does not perform its function. command
Operator response parameter
The incorrect parameter
Correct the parameter and re-enter the command. If
necessary, view the help for the command to assist in
entering a valid command. System action
EZL200I AUTOMATION OPERATOR id HAS The command fails and does not perform its function.
BEEN INITIALIZED
Operator response
Explanation Correct the parameter and re-enter the command. If
AON initialized an automation operator and started necessary, view the help for the command to assist in
processing. entering a valid command.
Message Variables EZL203I EXPECTED PARAMETERS

MISSING FOR REQUEST command
id —request
The ID of the automation operator
Explanation
System action
The specified parameter that must be passed to the
AON is ready for processing. specified command is missing.
EZL201I "global" GLOBAL NOT Message Variables
COMPLETELY UPDATED - TIMED
OUT request
The name of the request.
Explanation command
The incorrect command
AON cannot update a global variable or value during
initialization.
System action
Message Variables
The command fails and does not perform its function.
global
The type of global variable. The type is COMMON Operator response
or TASK.
If the message appears on an operator panel, correct
the input and press Enter. If the message appears in
System action
the NETLOG, notify your system programmer.
AON operations can be affected.
Operator response
Perform the problem determination function on the
Notify your system programmer. command. Find the error in the NETLOG and contact
System programmer response EZL204I EXPECTED PARAMETERS INVALID
Review the NETLOG for the AON AUTOTASK ID to FOR REQUEST command -
determine which ID is timing out and contact IBM parameter = value
Software Support.
EZL202I Explanation
PARAMETER "parameter" INVALID
FOR REQUEST command The parameter that must be passed to the specified
command is incorrect.
The specified parameter that must be passed to the command
specified command is incorrect. The name of the command

parameter EZL206I "intcmd " COMMAND FAILED FOR
The parameter that is incorrect command: RECEIVED "rc"
value message
The value of the parameter that is incorrect
Explanation
System action The specified command was not processed. The
The command fails and does not perform its function. command list received a return code or a message that
indicates the problem.
Notify your system programmer. intcmd
The name of the internal command that failed
System programmer response command
The command that issued the failing internal
command
command. Find the error in the NETLOG and contact
IBM Software Support. rc
The return code for the issued command
EZL205I "aoncmd"COMMAND FAILED FOR
command: interval - WAIT TIME message
EXPIRED message The message text
Processing of the specified command took too much The command stops processing.
time and failed.
Operator response
Message Variables
aoncmd
The internal command that failed
command
The AON command Check the NetView log for more information. Use
problem determination procedures to solve the
interval
problem.
The exceeded timer interval
message EZL207W NO DEFAULTS SET FOR parameter
The extra message text (option) FOR restype resname- COMMAND
HALTED
Operator response
Explanation
Check the NetView log that was active when the
message was received to see whether other command AON stopped processing a command because the
timers have expired. If no other timers have expired, automation defaults for the specified resource are not
review the syntax for the command and issue the set.
command again. If other command timers have been Message Variables
exceeded or if processing of the command fails again,
notify your system programmer. parameter
The automation defaults that must be set
System programmer response restype
Review the user input to determine the
appropriateness of the request and instruct the resname
operator on the proper procedure. If the user input is The name of the resource
correct, review the NetView log that was active when
the message was received to look for the cause for System action
delays in command list processing. Note the value of The command stops processing.
the timer interval to see whether the timer default
must be changed.

Notify your system programmer. interval
The default interval specified in the control file.
System action
Correct control file entry for the specified resource.
The system uses the specified default interval.
EZL208I THE INPUT LENGTH MUST BE
length CHARACTERS. input IS
INVALID. System programmer response
In the control file, correct the interval for automation
Explanation check.
The input parameter specified has an incorrect length. EZL211W NO AUTOOPS ENTRIES HAVE
BEEN DEFINED - AUTOMATION
Message Variables
CANNOT CONTINUE
length
The length required for the input value Explanation
input No entries for automation operators are defined in the
The value that is in error control file.

The command fails and does not perform its function. AON initializing stops.

If the message appears on an operator panel, correct Notify your system programmer.
the input and press Enter. If the message appears in
the NETLOG, notify your system programmer.
System programmer response Add the appropriate AUTOOPS keyword to the control
file and reload the control file.
command. Find the error in the NETLOG and contact EZL212I NO PRIMARY OPERATOR ID WAS
IBM Software Support. SPECIFIED FOR autoop
EZL209I DEFAULT OPERATOR ID AT
domain WILL BE opid Explanation
No primary operator is defined in the control file for
Explanation the AUTOOP entry.
The specified default operator ID is located at the Message Variables
specified domain. autoop
Message Variables The AUTOOP control file entry that is in error
domain
The name of the domain System action
opid AON uses the operator ID assigned to the BASEOPER

The default operator ID keyword.
EZL210I INTERVAL NOT VALID DEFAULT OF

Operator response
interval BEING USED
Explanation
The current interval set for the automation check is
incorrect, so the specified default interval is being Correct the specified AUTOOP keyword in the control
used. file and reload the control file.

EZL213E program - REQUIRED TABLE Explanation
ENTRY NOT DEFINED keyword You issued the specified AON function from the
component group operator interface but do not have sufficient authority
to issue the command.
Explanation
Message Variables
The loader table lookup command cannot locate a
required table entry. This problem occurs only if the opt
loader tables are incorrect. The number of the option that you selected from
an AON component or panel
Message Variables
program System action
The name of the program The command is not issued.
keyword
The high-level keyword Operator response
component
Request authority to issue the command from your
The name of the component
system programmer. Provide the system programmer
group with the component and the name of the panel
The identifying group selection you need to access.

The system resumes command processing. See the appropriate AON or component installation
guide for documentation of all the available
Operator response commands and their associated program names. For
command authorization information, see the IBM Z
Notify your system programmer with the error from NetView Security Reference.
the NETLOG.
EZL216I COMMAND command NOT
System programmer response PROCESSED - THE AUTOMATION
ENVIRONMENT IS NOT
Perform the problem determination function on the INITIALIZED
loader tables. Look at the error in the NETLOG, correct
the entry in the specified table, and load the table
Explanation
again.
You tried to issue a command but the command failed
EZL214E RESOURCE resname IS NOT VALID because the automation environment is not
FOR THIS NETWORK completely initialized.
You issued a command on a resource that is not command

known to your network. This occurs when the Network The name of the command that failed
ID for the resource is different from the Network ID of
the current NetView domain. System action
Message Variables The command exits without completing its function.
resname
The name of the resource Operator response
Issue the command again after completing AON
System action initialization.
AON does not issue the command. EZL217E command - UNMATCHED
DELIMITERS ENCOUNTERED
EZL215I OPTION opt NOT PROCESSED - MEMBER= table ENTRY= entry
ACCESS NOT AUTHORIZED option

Explanation RC=7
Missing key parameters
The specified command found unmatched delimiters
in a loader table. The delimiters are ' or ". RC=8
Uneven keywords
Message Variables
RC=9
command Missing semicolon
The name of the command that located the
RC=10
unmatched delimiters.
Missing comma
table
RC=11
The loader table that contains the unmatched
Keyword value greater than 255
delimiters
entry System action
The table entry
Loading of the table in error stops.
option
The table option
Operator response
Loading of the table stops for the table in error.
Operator response Correct the option definition table in error by looking at
the specified entry and keyword. Use the return code
for help in determining the error.
System programmer response EZL219I COMMAND command NOT FOUND

Correct the option definition table error and load the
table again. Explanation
The specified command was set to run but the
EZL218E command - FORMAT ERROR
command does not exist.
ENCOUNTERED IN MEMBER= table
ENTRY= entry keyword RC= rc Message Variables
command
Explanation The name of the command
The specified command found an error in the syntax of
an entry in the specified option definition table. System action
Message Variables The command that calls the program stops processing.
command
The name of the command that located the error Operator response
table Notify your system programmer.
The name of the table in which the error was found
entry System programmer response
The table entry in error Perform the problem determination function on the
keyword missing command. Note the missing command and
The keyword in error search the concatenated libraries for it.
rc EZL220E table NOT INITIALIZED , flag FLAG
The return code (RC) that identifies the particular SET TO setting
error
RC=5 Explanation
Missing keyword
During initialization, AON tried to load a component,
RC=6 but the option flag for installation (INSTALLOPT) is not
Missing key values set correctly in the control file.
Message Variables

table Operator response
The name of the option definition table that cannot
Review any settings and retry. After retrying, if there is
be initialized
still no data to display, review the netlog for related
flag messages and contact the System Programmer.
The configuration flag on the (INSTALLOPT) entry
setting System programmer response
The flag setting
Review any system-wide settings (such as community
name for SNMP-related functions). Review the netlog
System action for related messages. If you are still unable to
The system logs a message. determine the cause for this message, contact IBM
Software Support.
Operator response EZL223E exit_command EXIT IN cfentry IS
Notify your system programmer. INVALID, RC = rc
In the control file, correct the install option entry for An exit command in a calling program failed.
the component to be loaded. Message Variables
EZL221E DUPLICATE MENU SELECTION exit_command
DEFINED (position) FOR The exit command
component cfentry
The control file entry for that exit command
Explanation
rc
During initialization, AON tried to load the Main Menu The return code (RC) that AON issued.
positions and found duplicate entries for different RC=4
components. The exit command exceeded 78 characters.
Message Variables RC=8
(position) The exit command was not found.
The menu position of the specified component
component System action
The name of the component The program fails.

The duplicate entry is not loaded. Notify your system programmer.

Correct option definition table entries for the specified Perform problem determination on the error.
component in the option definition table for that
component. The entry is MAINPANELPOS. EZL224I command ERROR - STATUS FILE
IS EMPTY
EZL222I THERE IS NO DATA TO DISPLAY
Explanation
Explanation
AON received a request to delete records from a
You attempted to view data that is not available. status file, but the status file was empty.
Possible reasons that might prevent data from being
displayed are filter settings, network issues, command Message Variables
timeouts, and system setting. command
The name of the status command that was issued

System action restype
Database maintenance stops.
resname
EZL225E command - RECORD id CONTAINS The name of the resource
AN INVALID DATE FORMAT
Operator response
Explanation
Correct the resource name and try the command
A record in the status file has an incorrect date format. again. Check the NetView log for messages BNH232I
Message Variables and BNH233I for additional information.
command EZL228E task NOT AUTHORIZED TO ISSUE

The name of the status command that was issued COMMAND command
id
The ID of the record Explanation
You issued a command using a task that is not
System action authorized to issue the command, one of its keywords,
or one of its keyword values. Check the Netlog for
Processing resumes.
additional error information.
Record the record number and notify your system task

programmer. The ID used to issue the command
command
System programmer response The command issued
Perform problem determination on the status file date

System action
error. Try to change the date of the record in error.
The command fails.
EZL226I PARAMETER parameter OF THE
entry STATEMENT IGNORED -
PARAMETER NO LONGER Operator response
SUPPORTED To issue the command, request authorization from
your system programmer.
Explanation
The parameter of the entry statement no longer exists. System programmer response
Message Variables Verify that the task has the authorization to issue the
command. For more information, see the IBM Z
parameter NetView Security Reference.
The parameter name (keyword)
EZL229I NO ENTRY FOR parameter type
entry
HAS BEEN DEFINED - DEFAULT OF
The control file entry
value USED

Explanation
Remove the unsupported entry from the control file.
The entry type is not defined in the control file
EZL227I RESOURCE restype resname member, so AON uses the default value.
COULD NOT BE IDENTIFIED BY Message Variables
ANY INSTALLED COMPONENTS
parameter
Explanation The parameter that is defined in the control file
statement and that is specified by the specified
AON tried to identify a resource that is not defined to type
any AON component.
type
Message Variables The field in the control file statement that is not
defined

value type
The default value assigned to the entry The second field of the affected control file entry

The system assigns the default value. Notify your system programmer.

Notify your system programmer. Correct the timeout value in the control file.
EZL232I HIERARCHY NOT BUILT - restype
System programmer response resname HAS NO LOWER NODES
Correct the control file member if you do not want to
use the default. Explanation
EZL230E REQUIRED PARAMETER parm The hierarchy for the specified resource is not built
MISSING FROM entry STATEMENT because the resource has no lower nodes. When the
IN name FILE hierarchy for resources monitored by the RECOVERY
parameter is built, and if AUTO=Y, each resource is
Explanation checked for any lower nodes to set.
The parameter identified in the message as parm is Message Variables

required but was not specified in the entry statement restype
in the file named name. The type of resource
Message Variables resname
parm
The parameter that was not specified, although it
is required. System action
entry Setup of the hierarchy cancels.
The statement that contains the required parm.
name Operator response
The name of the file containing the entry Note the error and notify your system programmer.
statement.

Operator response
Correct the control file entry for the resource type and
Notify your system programmer. resource name. The entry is RECOVERY= and the type
is AUTO=. When you have made these changes, load
System programmer response the control file again.
Correct the error and reload the file if necessary. EZL233E HIERARCHY NOT BUILT - restype
EZL231I INVALID TIMEOUT VALUE OF resname IS NOT VALID IN THIS
interval HAS BEEN DEFINED FOR NETWORK
entry type COMMANDS
Explanation
Explanation The hierarchy is not built for the specified resource,
The specified timeout value defined in the control file because the resource is not correctly defined in the
member is incorrect. local network.
interval restype
The timeout interval in error The type of resource
entry resname
The first field of the affected control file entry The name of the resource

AON stops setting up the hierarchy for the resource.
resname
Operator response The name of the resource
location
Record the error for the resource and notify your The domain or service point
system programmer.
EZL236I RECOVERY MONITORING
System programmer response ALREADY IN EFFECT FOR restype
resname ON location, ACTIVE
Correct the control file. MONITORING REQUEST IGNORED
EZL234I NO ACTMON ROUTINE DEFINED
FOR COMPONENT component OR Explanation
restype resname, ACTIVE AON tried to start active monitoring (ACTMON) on a
MONITORING NOT SCHEDULED resource, but the command failed because the
resource is in recovery mode.
Explanation
Message Variables
AON tried to start active monitoring (ACTMON) on a
resource for which no ACTMON routine is defined in restype
the option definition table for the resource type. The type of resource
resname
Message Variables
component location
The name of the component The domain or service point
restype
The type of resource System action
resname The request fails.
EZL237I resname restype STATUS=
System action "resstat" IS GOOD. DESIRED
STATUS="desirestat". ACTIVE
The ACTMON routine does not start on the resource MONITORING CONTINUES
type or the resource name.
Explanation
Operator response
You have scheduled active monitoring for a resource,
Note the error and notify your system programmer. but the resource is currently in an acceptable status.
Message Variables
resname
Note the component and look at its option definition
The name of the resource being actively monitored
table, define the EZLRT ACTMON entry for the
resource type and load the table again, using the restype
LOADTBL command. The type of resource
resstat
EZL235I ACTIVE MONITORING ALREADY
The current status of the resource
IN EFFECT FOR restype resname
ON location, ACTIVE MONITORING desirestat
REQUEST IGNORED The requested status for active monitoring

AON tried to start active monitoring (ACTMON) on the Active monitoring continues.
specified resource, but failed, because ACTMON is
EZL238I AUTOMATION OPERATOR operator
already active.
IS NOT ACTIVE
Message Variables

You issued a command on an ID that is not correctly If you need to turn on the AON trace function, contact
defined or active. your System Programmer to gain access to the trace
administration function.
Message Variables
operator System programmer response
The operator ID on which the command was
issued Allow several NetView operators access to the AON
Trace Administration function. See the IBM Z NetView
Administration Reference for more information.
System action
EZL242I PROGRAM program-RUNCMD
AONTEST stops.
RETRY COUNT LIMIT OF number
EXCEEDED FOR resname
Operator response
Check the ID of the automation operator and notify Explanation
A REXX program issued a run command to the
EZL239I CORRECT THE PROBLEM AND specified resource for the specified number of times
RERUN AONTEST (the limit for the specified resource) but received a
busy sense code from a service point.
AON encountered a problem running a test during AON program
initialization. The name of the REXX program that issued the
command
System action number
AON initialization stops. The number of times the REXX program issued the
command
Operator response resname
Record all error messages and notify your system
programmer.
System action
System programmer response The REXX program stops running.
Perform problem determination on all error messages,
correct the problem, and reinitialize AON. Operator response
Start problem determination procedures for the
EZL241W TRACE = req REQUEST IGNORED,
resource. The problem might involve performance or
SETTING = NONE
looping.
Explanation EZL243I variable COMMON GLOBAL

UPDATED TO value
You issued an AON trace function, but your NetView
domain is not enabled for tracing. Tracing is typically
disabled for improved performance. Explanation
Message Variables AON updated the common global variable and value.
req Message Variables

The trace function you requested. variable
The common global variable
System action value
The command is not issued. The common global value
EZL244E DSICTMOD RUNCMD TIMEOUT
HAS BEEN EXCEEDED, RUNCMD
TO service point FAILED FOR
program.

Explanation DSRBS available for the RUNCMD to run. To determine
whether DSRBS is adequate, issue the DSRBS DSIGDS
The run command (RUNCMD) timed out because the
command.
timeout value in the DSICTMOD NetView constants
module is exceeded. EZL246E RUNCMD FAILED TO SP spname -
RECEIVED MESSAGE msgnum
Message Variables
SENSE CODE sensecode
service point
The name of the service point Explanation
program
A RUNCMD that you sent to the specified service point
The name of the program that issued the RUNCMD
abnormally ended with the specified message number
and sense code.
System action
Message Variables
The program issuing the RUNCMD ends and passes a
return code of 5 back to the calling program. spname
The name of the service point
Operator response msgnum
The number of the message received back from
Check to see if the service point is hung. Start problem the RUNCMD
determination procedures on the resource. Also check
to see if there is a problem with the NetView RUNCMD sensecode
components. Make sure the DSIGDS task is not hung The sense code information received with the
and that there is enough DSRBS available for the message
RUNCMD to run. To check this, issue the DSRBS
DSIGDS command. System action
EZL245E RCMD CORRWAIT TIMEOUT OF The RUNCMD stops.

seconds SECONDS HAS BEEN
EXCEEDED, RUNC MD TO service Operator response
point FAILED FOR program.
View the sense code information using the NetView
SENSE command and correct the problem. If the
Explanation problem persists, contact your system programmer.
The run command (RUNCMD) timed out because the
RCMD value (number of seconds) in the ENVIRON System programmer response
TIMEOUT entry is exceeded. The RCMD value is used
Activate the service point, and start the agent software
in a PIPE command to issue the RUNCMD.
that accepts the RUNCMDs.
Message Variables
EZL247E command - TGLOBAL tglobal NOT
seconds INITIALIZED
The number of seconds
service point Explanation
The specified command attempted to locate the
program specified task global variable (TGLOBAL) set but
The name of the program that issued the RUNCMD cannot find it.
Message Variables
System action
command
The program issuing the RUNCMD ends and passes a
return code of 5 back to the calling program.
tglobal
The name of the TGLOBAL that is defined
Operator response
Determine whether the service point is hung. Start Operator response
problem determination procedures on the resource.
Also, determine whether there is a problem with the Notify your system programmer.
NetView RUNCMD components. Ensure that the
DSIGDS task is not hung and that there is enough

System programmer response timer
The timer that AON cannot set.
Perform the problem determination function to
determine why the TGLOBAL parameter is not set. Set parameter
the task globals on the NetView session being used. The parameter used to set the timer.
EZL248E TASK GLOBAL VARIABLES NOT

System action
SET; MUST ISSUE command TO
SET The timer is not set.

You must issue the specified command to set the Notify your system programmer.
required task global variables.
command Correct the parameter in the control file and load the
The command used to set the task global control file again.
variables. EZL251E TIMER ID = timer NOT
SCHEDULED, CURRENT TIME PAST
Operator response THE EXECUTION
Run the specified command to set the task global
variables. Explanation
EZL249E command - CGLOBAL cglobal NOT AON cannot schedule the specified timer, because the
INITIALIZED current time exceeds the time set for the timer.
Message Variables
Explanation
timer
The specified command cannot locate the specified The timer
common global variable (CGLOBAL) set.
command The timer is not set.

The command used to set the common global
variables Operator response
cglobal If the timer is necessary, use the AON timer function
The name of the CGLOBAL that is defined to set the timer.
EZL252E TIMER ID = timer NOT
Operator response
SCHEDULED, reason RC = rc
Explanation
The specified timer cannot be scheduled because of
Perform the problem determination function to the specified reason.
determine why the CGLOBAL parameter is not set. Set
Message Variables
the common global variables.
timer
EZL250E TIMER ID = timer NOT The timer
SCHEDULED, INVALID parameter
PARAMETER reason
The explanation of the failure
Explanation rc
The NetView return code values
At initialization, AON cannot set the time for the
specified timer.
System action
Message Variables
The timer is not scheduled.

Determine why the timer was not scheduled and issue AON tried to set the specified timer, but the timer is
the timer request again. For more information about already set.
the AFTER, AT, CHRON, and EVERY commands, see
Message Variables
the online help.
timer
EZL253E REQUESTED TIMER timer NOT The name of the timer
FOUND
System action
Explanation
Processing resumes.
AON cannot find the specified timer when it tried to
purge the timer.
Operator response
Message Variables
Select another timer to set.
timer
The name of the timer EZL256E TIMER ID = timer NOT SCHEDULED
Processing resumes. AON cannot set the specified timer.

Message Variables
Operator response
timer
Verify that the timer does not exist by refreshing the The timer AON cannot define.
timer display. Possibly, the timer exceeded its time
limit before it was deleted. System action
EZL254E TIMER ID = timer NOT The timer is not set.
SCHEDULED, task NOT ACTIVE
Operator response
Explanation
AON tried to set the specified timer, but the task that
issues the command on the timer when the timer System programmer response
reaches its time limit is not active.
Determine why the timer cannot be set by trying to set
Message Variables it manually.
timer
The name of the timer
SCHEDULED, failure FAILED WITH
task REASON reason
The name of the timer task
Explanation
System action
AON cannot set the specified timer because of the
Processing resumes without the timer being set. specified reasons.
Message Variables
timer
Perform the problem determination function on why The timer
the task is not active. If the task must be active, start
it. failure
The failure key
reason
SCHEDULED, DUPLICATE ID
The reason for failure
TIMER ALREADY EXISTS

The timer is not scheduled. Possibly, the timer is not Correct the message ID specified as the second
set because it is inactive. parameter of the EZLMSG command.
EZL263I MESSAGE ID NUMERIC "ID" IS
Operator response NOT NUMERIC
Determine why the timer was not scheduled, correct
the problem, and issue the time request again. Explanation
EZL260I date time opid program ENTRY/ The specified message ID is not correct because it
EXIT parmlist does not end with three numeric digits.
Message Variables
Explanation
ID
This message appears when the AONTRACE The message ID that is not correct. This ID is the
(RXTRACE) program starts. The message displays the second parameter of the EZLMSG command.
entry and exit parameters for the specified REXX
program, command lists, and command processors.
Operator response
Message Variables
date
The date System programmer response
time Correct the message ID that is specified as the second
The time parameter of the EZLMSG command.
opid
The ID of the operator or task running the program EZL264I TOO FEW PARMS ON EZLMSG
COMMAND - 2 IS MINIMUM
program
The name of the REXX program, the name of the
command list, or command processors Explanation
parmlist You issued the EZLMSG command without specifying

A list of the parameters passed to the program one or more of the required parameters. At least two
parameters must be specified.
EZL262E MESSAGE ID "ID" INVALID, MUST
BE "NNN" "ABCNNN" OR Operator response
"ABCDNNN"
Explanation
The specified message ID is not correct but must be
like the other ones that are specified. Ensure that the coding of the EZLMSG command
specifies a message ID value as the second parameter.
Message Variables If you do not want to specify a value for the first
ID parameter, enter a comma in its position as a place
The message ID that is incorrect. holder, for example, EZLMSG, 001.
NNN EZL271E PROGRAM program FAILED - LINE
Three decimal digits. line CONTAINS A VARIABLE WITH
abcnnn NO VALUE - variable
A 3-character prefix followed by three decimal
digits. The prefix can contain numeric values. Explanation
abcdnnnn AON found an error in the specified REXX program.
A 4-character prefix followed by three decimal
digits. The prefix can contain numeric values. Message Variables
program
Operator response The failed program
Notify your system programmer. line
The line in the program where the error occurred

variable application name is hex data, it means that AON
The variable in the program that is missing a value cannot determine its real name.

AON stops processing the REXX program. Record the application name for your system
programmer. Examine the contents of the sense code
Operator response in message EZL284E to determine the cause of the
failure.
Note: Only the first failure of NPDA will be shown.
System programmer response EZL281E DESTINATION NETID = netid
Contact IBM Software Support and provide the
appropriate problem determination information. Explanation
EZL275E program FAILED - LINE line This message identifies the destination network ID for
SYNTAX ERROR number the LU 6.2 MS Transport send.
Message Variables
Explanation
netid
The specified program failed because of a syntax error The network ID as specified in the send command
in the REXX code.
program Note the network ID for the system programmer.

The failed program Determine the cause of the failure based on the
contents of the sense code in message EZL284E.
line
The line number EZL282E DESTINATION LU = destlu
number
The REXX error number Explanation
This message identifies the destination LU name for
System action the LU 6.2 MS Transport send. This name might be the
AON stops processing the program. destination NetView domain ID of a Communications
Manager LU0 name.
Notify your system programmer. destlu
The destination NetView domain or the
System programmer response Communications Manager LU0 name.
Contact IBM Software Support and give the

Operator response
appropriate problem determination information.
Record the name of the destination LU for the system
EZL280E START OF ERROR MDS_MU programmer. Determine the cause of the failure based
DISPLAY RECEIVED FROM appl on the contents of the sense code in message
EZL284E.
Explanation
EZL283E DESTINATION APPLICATION =
This message is the first line of a multiline message. destappl
When an error associated with an LU 6.2 MS Transport
send request occurs, this line is written to the NetView Explanation
log.
This message identifies the destination MS application
Message Variables for the LU 6.2 MS Transport send.
appl Message Variables
The name of the application that detected the
error. MDS_ROUTER is the most probable name, destappl
but other application names are possible. If the The name of the destination MS application

Operator response status
The status of the specified resource. The status is
Record the name of the destination application for the
ON or OFF.
system programmer. Determine the cause of the
failure based on the contents of the sense code in resname
message EZL284E. The name of the resource.
EZL284E SENSE CODE RECEIVED = X EZL306I PRIMARY LOG log IS NOW ACTIVE
'sensecode'
Explanation
Explanation The log task switched logs and activated the primary
This message identifies the SNA sense code that log.
explains why the error occurred. Message Variables
Message Variables log
sensecode The name of the primary automation log
The SNA sense code
System action
Operator response AON records the log information in the primary log.
Issue the NetView SENSE command to view an online EZL307I SECONDARY LOG log IS NOW
explanation of the failure. If the sense code is ACTIVE
unavailable, see SNA Formats.
Explanation
The log task switched logs and activated the
See VTAM Messages and Codes or SNA Formats.
secondary log.
EZL285E CORRELATOR = X'correlator' Message Variables
log
Explanation
The name of the secondary automation log
This message identifies the LU 6.2 MS Transport send
that caused the error. System action
Message Variables AON records the log information in the secondary log.
correlator EZL308I resname : TASK status - ALL
A unique hex string that MS Transport builds when
table(s) ARE FULL
a send is requested.
Explanation
Operator response
AON cannot switch log files because all of the log files
Record the correlator information for the system are full.
programmer. Determine the cause of the failure from
the sense code in message EZL284E. Message Variables
EZL289E END OF ERROR MDS_MU DISPLAY resname

Explanation status
The status of the task
This message identifies the end of the display group of
messages for the MDS_MU error. table
The control file literal tables that are used for task
EZL302I AUTOMATION STATE SET status logging
FOR resname
System action
Explanation
AON stops the log task.
The specified resource is set to ON or OFF.
Message Variables

Notify your system programmer. Allocate a subsystem-allocatable console for NetView
to use, or start the EZLSUS01 member in the
System programmer response EZL5J007 job to perform the switch.
Examine the primary and secondary control file entries EZL314I CATCHUP TIMER ID timer NOT
for EZLTLOG to determine why the controls did not EXECUTED. TASK operator NOT
switch. Use the AUTOFLIP keyword. LOGGED ON
EZL309E MUST OFFLOAD PRIMARY log

Explanation
MANUALLY - NO CONSOLES
AVAILABLE The specified timer became a catch-timer because its
interval passed. However, the timer cannot be issued
Explanation because the operator it used to issue the command on
the timer was not logged on. Therefore, the timer was
The log autoflip function cannot issue the MVS START deleted.
command to reset the primary logs.
Message Variables
Message Variables
timer
log The name of the timer
The name of the log
operator
The ID of the operator who issued the command
System action on the timer
AON does not switch logs.
Operator response
Operator response Issue the command again manually under the
Notify your system programmer. appropriate operator ID.
EZL315I TIMER timer PURGED
Allocate a subsystem-allocatable console for NetView Explanation
to use, or start the EZLSUP01 member in the
You deleted a timer from the NetView timer list.
EZL5J007 job to perform the switch.
Message Variables
EZL310I MUST OFFLOAD SECONDARY log
MANUALLY - NO CONSOLES timer
AVAILABLE The deleted timer
EZL319I OPERATOR operator1 SCHEDULED
Explanation TIMER timer UNDER OPERATOR
The log autoflip function cannot issue the MVS START operator2 - COMMAND: text
command to reset the secondary logs.
Explanation
Message Variables
You created and defined a new timer.
log
The name of the secondary automation log Message Variables
operator1
System action The ID of the operator who created the timer
AON does not switch the log. timer
The name of the timer that was scheduled.
Operator response operator2
Notify your system programmer. The ID of the operator who scheduled the timer
text
The command to issue when the timer exceeds its
interval

AON sets the timer. The system recycled the resource.
EZL320I TIMER timer WAS EXECUTED ON EZL333I restype resname ON location HAS
TASK operator BY CATCHUP BEEN RECYCLED
PROCESSING
Explanation
Explanation
AON recycled the specified resource.
Catch-up processing successfully issued a command
Message Variables
on the timer again. The timer had exceeded its running
time and cannot be restored by the timer-restore restype
component of NetView program. The type of resource
timer
The name of the timer for which the timer location
command was issued again The domain or service point
operator EZL334I UNABLE TO VARY restype resname

The ID of the operator who issued the timer ON location ACTIVE
command
Explanation
EZL331I VTAM NOT ACTIVE: COMMAND
command CAN NOT BE INVOKED You tried to issue a VARY ACT command, but the
command failed to activate the resource.
AON issued a VTAM command while VTAM was not restype
active. The type of resource
command The name of the resource
The failed command location
The domain or service point
System action
System action
AON does not process the command.
The resource remains not active.
Operator response
Operator response
Use the log to determine why the resource is not
System programmer response normal and notify your system programmer.
Start VTAM and issue the command again.

EZL332I RECYCLING NETWORK NODE Determine why the resource is not normal. Correct the
resname problem and issue the command again.
Explanation EZL335I NO RESPONSE FOR seconds

SECONDS - RECYCLE COMMAND
AON is issuing a RECYCLE command for the specified ENDING
resource.
resname The RECYCLE command waited the specified number
The name of the resource being recycled of seconds for a response from the VARY ACT
command.
Message Variables

seconds EZL338I IF UNABLE TO ACTIVATE AFTER
The number of seconds the RECYCLE command number SECONDS - RECYCLE
waited. COMMAND WILL TERMINATE

AON stops processing the RECYCLE command. The RECYCLE command waits the specified number of
seconds for a response from VTAM regarding the
Operator response activation of a resource. If VTAM does not respond in
time, the RECYCLE command stops processing.
Increase the timeout value and manually issue the
VARY ACT command on the resource. Message Variables
number
System programmer response The number of seconds in which AON tries to
activate the RECYCLE command
Determine why the resource is not normal. Correct the
problem and issue the command again.
System action
EZL336E 'resname' IS NOT A VALID
RESOURCE NAME The RECYCLE command stops.
EZL341I NO LARGE SCALE THRESHOLDING
Explanation CONTROL FILE ENTRY FOUND FOR
You issued a VARY ACT or VARY INACT command for type
the specified resource, but VTAM does not recognize
the resource. Explanation
Message Variables AON received an event on which thresholding is being
tracked, but the threshold type has no entry in the
resname control file.
Message Variables
System action type
AON does not process the VARY ACT command or the The type used for large-scale thresholding
INACT command on the resource.
System action
Operator response Large-scale thresholding does not start.
Verify the spelling of the resource name and issue the
VTAM command again. If the problem persists, notify Operator response
your system programmer. Notify your system programmer.

Determine why the resource is not recognized by Correct the control file entry for the type and load the
VTAM. Correct the problem and issue the command control file again.
again.
EZL342I keyword FOR type INVALID OR
EZL337I COMMAND command CANCELLED keyword NOT FOUND IN CONTROL
BY OPERATOR FILE FOR LARGE SCALE
THRESHOLDING
Explanation
You canceled the specified command. Explanation
Message Variables There is an incorrect parameter in the control file or

the keyword is missing from the control file.
command
The name of the canceled command Message Variables
keyword
The large-scale threshold keyword

type endpt1
The type used for large-scale thresholding One of the session partners
endpt2
System action The second session partner
Large-scale thresholding does not start.
System action
Operator response Active monitoring continues.
Notify your system programmer. EZL400W functionname FUNCTION FAILED
WITH RETURN CODE retcode -
System programmer response FUNCTION IS DISABLED
Correct the control file entry for the type and load the
control file again. Explanation
This message is issued when the AONAIP or AONOIV
EZL343I LARGE SCALE type THRESHOLD OF
function is unable to continue processing requests.
number EVENTS WITHIN
timeframe HAS BEEN REACHED Message Variables
functionname
Explanation Either the Automation in Progress (AIP) or
The threshold on the specified monitored type was Operator Intervention View (OIV) function
reached. retcode
Message Variables The return code indicating the cause of the failure
as follows:
type
100
The type used for large-scale thresholding. The
The RODMNAME is not specified in
type value can consist simply of a valid threshold
Environment Setup.
type or it can consist of a valid threshold type with
the name of a resource appended to it. 104
The MSMACC command is not available.
number
The number of events 108
The VTAM SNA Node Name was not found
timeframe
during initialization.
The interval for the type that is defined in the
control file 109
The current operator is not authorized to use
Operator response MSMACC.
110
View the congestion area to determine whether any
The AIP function is already disabled.
action is required and reference the documentation on
large-scale thresholding for the appropriate 112
component. The OIV function is already disabled.
126
EZL350I resname restype IS BETWEEN
The required AIPOPER AUTOOPS entry in the
endpt1 endpt2
AON control file is missing or is not valid.
Explanation
System action
This is an informational message that identifies the
The specified function is already disabled or has been
endpoints of a session being actively monitored by
disabled as a result of the failure.
AON. This message accompanies other messages
regarding the session.
Operator response
Message Variables
If you need to enable the AIP or OIV function, contact
resname your system programmer.
The name of the resource being actively monitored
restype

System programmer response functionname
Either the Automation in Progress (AIP) or
Examine the return code and determine the reason for
Operator Intervention View (OIV) function
the failure. This message indicates that the AONAIP or
AONOIV function is now disabled. If several EZL400W retcode
messages exist in the log, the return code in the first MSM Access return code
message will indicate the reason for the failure.
Correct the problem as needed and reinitialize AON. System action
EZL401W functionname FUNCTION FAILED. The specified function is disabled because of the
RODM rodmname FAILED WITH unexpected MSM Access error.
RODM RETURN CODE retcode
REASON CODE rescode - CORRECT Operator response
THE PROBLEM
If you need to enable the AIP or OIV function, contact
Explanation
This message is issued when the AONAIP function System programmer response
detects unexpected RODM Return and Reason codes.
Examine the MSM Access return code to determine the
Message Variables cause of the failure. Correct the problem and
functionname reinitialize AON.
Either the Automation in Progress (AIP) or EZL403I AUTOMATION IN PROGRESS
Operator Intervention View (OIV) function FUNCTION WILL USE GATEWAY
rodmname PREFIX prefix - AN ATTEMPT TO
The RODM name that is defined to AON ACCESS THE FLBSYSD GATEWAY
retcode NCP SETTING FAILED
The RODM return code
rescode Explanation
The RODM reason code This message is issued when the AONAIP function is
unable to access the FLBSYSD member to obtain the
System action gateway prefix during initialization. Or, if the member
was accessed the GATEWAY_NCP entry was not
The specified function is disabled because of the found.
RODM error.
Message Variables
Operator response prefix
The calls specified in functionname will continue to fail The prefix that will be used to refer to gateway
until the problem is corrected. If necessary, contact objects in RODM.
System action
System programmer response The Automation in Progress function, if enabled, uses
Examine the RODM return and reason codes to the prefix when attempting to set the AIP bit for NCP
determine the cause of the failure. Correct the gateway objects.
problem as needed.
Operator response
EZL402W functionname FUNCTION FAILED.
MSM ACCESS FAILED WITH Contact your system programmer.
RETURN CODE retcode -
FUNCTION IS DISABLED System programmer response
Verify that the gateway prefix is correct. If it is not,
Explanation determine the reason for the error. During
This message is issued when the specified function initialization, AON attempts to read the FLBSYSD
detects an unexpected MSM Access return code. member in search of the first GATEWAY_NCP entry.
AON needs access to the FLBSYSD member and
Message Variables

expects a GATEWAY_NCP entry. Correct the problem System programmer response
as needed and reinitialize AON.
Verify the correct domain was selected in the
EZL404E DOMAIN domainid IS RODMDOM AON control file entry. If the domain is
FORWARDING AUTOMATION IN correct, verify the AON gateway session with the target
PROGRESS UPDATES TO THIS domain is defined and active. Enable the gateway
DOMAIN WHICH IS NOT DEFINED interface or otherwise correct the AON AIP settings as
AS EXPECTED needed, reinitialize AON if appropriate.
EZL406E commandname COMMANDS MUST
Explanation BE FORWARDED TO THE RODM
This message is issued when the AONAIP updates are FOCAL POINT DOMAIN domainid -
forwarded to the current domain, and the current commandname UPDATE IS
domain is not defined as an AON AIP focal point. IGNORED
Message Variables
Explanation
domainid
The specified command must be issued from the AON
The domain that sends the AONAIP updates to the
AIP focal point domain.
current domain
Message Variables
System action commandname
The AONAIP function update is ignored. Contains the current command AONAIP or
AONOIV
Operator response domainid
The domain that is defined as the AONAIP focal
Contact your system programmer. point

If this domain is not a focal point for AONAIP updates, The specified function update has failed.
correct the RODMDOM setting in the AON control file
of the sending domain. If this domain is the focal point
Operator response
for AONAIP updates, verify the AONAIP function is
enabled correctly. Correct the problem as needed and Issue the command on, or forward the command to,
reinitialize the appropriate AON. the AONAIP focal point domain. Contact your system
programmer if necessary.
EZL405E AN ATTEMPT TO FORWARD
AUTOMATION IN PROGRESS
UPDATES TO DOMAIN domainid System programmer response
HAS FAILED Both AONAIP and AONOIV commands must be issued
to an AIP focal point domain. Verify the focal point is
Explanation defined correctly and that the operator can issue the
commands to that domain.
This message is issued when AONAIP updates cannot
be forwarded to the selected domain. EZL407E functionname FUNCTION FAILED.
Message Variables RODM rodmname FAILED WITH
RODM RETURN CODE retcode
domainid REASON CODE rescode -
The domain selected to receive the AONAIP FUNCTION IS SUSPENDED
updates, otherwise known as the AONAIP focal
point Explanation
System action The AONAIP command cannot be executed until

RODM is initialized or other initialization problems are
The AONAIP function update has failed. resolved.
Message Variables
Operator response

functionname EZL409E AUTOMATION IN PROGRESS
Either the Automation in Progress (AIP) or UPDATES IGNORED FOR
Operator Intervention View (OIV) function RESOURCE TYPE resctype -
rodmname DISABLED BY ENVIRON AIP
The RODM name that is defined to AON ENTRY
retcode
The RODM return code Explanation
rescode This message is issued when the AONAIP function is

The RODM reason code unable to change the AIP bit for a supported resource
type, which is disabled by the ENVIRON AIP entry.
Operator Intervention View actions are also blocked
System action
by ENVIRON AIP settings for the specified resource
The current AONAIP function fails. type.
Message Variables
Operator response
resctype
No action is necessary, however AONAIP function The resource type passed to AONAIP
commands cannot complete until RODM is initialized.
If this error persists, contact your system programmer.
Operator response
System programmer response If the AIP bit needs to be updated for this resource
type, contact your system programmer.
Ensure RODM is active with the appropriate data
models loaded. This error is not considered fatal as it
does not disable the AON AIP function. However no
RODMAIP commands will complete successfully until Determine whether AIP support is to be used for the
the problem indicated in the return codes is corrected. resource type, update ENVIRON AIP entry if
necessary, and reinitialize AON.
EZL408E functionname FUNCTION FAILED.
WAITING ON RODM EZL440E INFORM POLICY MEMBER
INITIALIZATION member_name statement
STATEMENT STARTING AT LINE
Explanation number CONTAINS THE
FOLLOWING UNKNOWN
The specified function cannot be executed until RODM PARAMETERS: invalid_parms
is initialized.
functionname An error was detected in the specified inform policy
Either the Automation in Progress (AIP) or member. Unknown, duplicate, or incorrectly entered
Operator Intervention View (OIV) function parameters were detected for the identified
statement.
The current function fails. member_name
The inform policy member which contains the
Operator response error.
No action is necessary; however, the specified function statement
cannot complete until RODM is initialized. If this error The type of statement which contains the error.
persists, contact your system programmer. number
The line number in the policy member where the
System programmer response statement in error begins.
Ensure RODM is active or in the process of becoming invalid_parms
active. AON detects when RODM has initialized. This A list of incorrect parameters supplied on the
message can only occur after AON initialization. current statement.

System action 26
Tap access number supplied for interface other
The inform policy member will not be loaded until the
than alpha-page
error is corrected, or the test of inform policy member
fails. keyword
The specific keyword which has the problem
Operator response
System action
Use the list of incorrect parameters to resolve the
problem or contact your system programmer. The inform policy member will not be loaded until the
System programmer response fails.
Examine the incorrect parameters and correct the Operator response

reason for the failure. Attempt to reload the inform
policy member after correcting the problems. Use the errorcode to resolve the problem or contact
EZL441E INFORM POLICY policy_name
statement ENTRY STARTING AT
LINE number CONTAINS SYNTAX
ERROR errorcode IN keyword Examine the errorcode and determine the reason for
the failure. Correct the problem as needed and
Explanation attempt to reload the inform policy member.
An error was detected in the specified inform policy EZL442I INFORM LOG MEMBER NOT
member. The errorcode can be used to determine the DEFINED
exact type of the error.
policy_name The inform policy logging function was unable to read

The inform policy or group name which contains from the log member because no member is defined.
the error.
System action
statement
The type of statement which contains the error The command issued to access the inform policy log
(GROUP, INFORM, CONTACT, or SETUP) ends.
number
This is the line number in the policy member where Operator response
the statement in error begins.
If this message persists and the log contains entries,
errorcode contact your system programmer.
The error code indicating the cause of the failure,
as follows: System programmer response
8
Check the inform policy SETUP statement to see if
Value not found, or unexpected data found
logging is enabled (LOG=YES) and the log file name
10 (MEMBER=).
Numeric data expected, or data format error
detected EZL443E ROUTE route CONFLICTS WITH
CONNECTION TYPE contype IN
12
THE CONTACT STATEMENT
Invalid times specified
STARTING AT LINE number IN
14 POLICY policy_name
Stop time is not later than the start time
16 Explanation
Connection type is not supported
The routing inormation specified conflicts with the
18 connection type.
Required service point name was omitted on
both the current inform and contact entries Message Variables

route System programmer response
Routing information specified in the failing
Correct the inform policy as needed and attempt to
statement.
reload the inform policy member.
contype
The type of connection specified in the failing EZL445E INTERFACE ROUTINE routine IN
statement. THE CONTACT ENTRY STARTING
AT LINE number IN POLICY
number policy_name WAS NOT FOUND
This is the line number in the policy member where
Explanation
policy_name
The inform policy name which contains the error. The routine specified in the inform policy contact entry
cannot be found, or the operator is not authorized to
execute it.
System action
Message Variables
error is corrected, or the test of inform policy member routine
fails. The routine name specified by interface keyword
of the contact statement or EZLENETF by default.
Operator response number
Use the inserts in the message to identify and resolve This is the line number in the policy member where
the problem or contact your system programmer. the statement in error begins.
policy_name
System programmer response The inform policy name which contains the error.
Correct the route or connection type and attempt to

System action
EZL444E A NUMERIC MESSAGE IS error is corrected, or the test of inform policy member
REQUIRED IN INFORM POLICY fails.
policy_name CONTACT ENTRY
STARTING AT LINE number WHEN
CONNECTION=NUMPAGE IS Operator response
SPECIFIED Insure the interface routine is available and the
operator has the necessary authorization to use it, or
Explanation contact your system programmer.
A numeric message is required when the connection
selected is a numeric pager. System programmer response
Message Variables Correct the inform policy as needed and attempt to

reload the inform policy member. Contact the person
policy_name responsible for security in your organization if an
The inform policy name which contains the error. access error exists.
number EZL446I THE CONTACT ENTRY KEYWORD
keyword STARTING AT LINE
number WAS TRUNCATED IN
POLICY policy_name
System action
The inform policy member will not be loaded until the Explanation
Either the contact entry name or message keyword
fails.
specified was truncated. The truncation may occur
when the inform policy member is loaded, when the
Operator response message is built with synonym substitution, or by
Correct the message or the connection type selected operator input on the INFORM command.
to resolve the problem or contact your system Message Variables
programmer.

keyword EZL448I NO INFORM POLICY MEMBER IS
Identifies which keyword's value has been LOADED
truncated.
number Explanation
There is no inform policy member loaded at this time.
the affected statement begins.
policy_name Operator response
The inform policy name which contains the
affected keyword. The inform policy member cannot be disabled if no
policy number is loaded.
System action EZL449E INVALID INFORM POLICY NAME
The inform policy member is loaded, the test of inform policy_name FOUND AT LINE
policy member completes, or the INFORM command number
continues.
Explanation
Operator response The inform policy name shown is not valid.
Ensure the contact entry name or message is Message Variables
adequate following the truncation. Update the inform
policy or reissue the INFORM command. policy_name
The inform policy name which contains the error.
System programmer response number
Correct the inform policy member as needed to the statement in error begins.
eliminate these messages.
EZL447E A statement STATEMENT WAS System action
EXPECTED AT LINE number
Explanation fails.
An unexpected statement or statement out of
sequence was encountered in the policy member. This Operator response
message can occur for any failing %INCLUDE
Correct the inform policy name, or contact your
statements.
system programmer.
Message Variables
statement System programmer response
The statement that was expected. Correct the inform policy as needed and attempt to
number reload the inform policy member.
The line number in the policy member where the
EZL450I INFORM POLICY INACTIVE
statement in error begins.
Explanation
System action
No inform policy member is currently loaded.
The inform policy member is not loaded, or the test of
inform policy member fails.
System action
Operator response None, or discontinue the current log related function.
Remove any incorrect statements, or correct the
sequence error in the statements in the inform policy Operator response
member. An inform policy member may need to be loaded to
complete your request.
EZL451I TEST OF INFORM POLICY MEMBER
Correct the inform policy as needed and attempt to member_name WAS result

Explanation date
The date the inform policy table was activated.
The message indicates the result of a syntax check on
the inform policy member. oper
The operator task that activated the inform policy
Message Variables table.
member_name
The DSIPARM member tested. System action
result The inform policy table status is displayed.
The result of the inform policy member test.
SUCCESSFUL indicates that the inform policy EZL454E DUPLICATE POLICY OR GROUP
member loads if the TEST keyword is omitted. NAME name DETECTED AT LINE
UNSUCCESSFUL is accompanied by the errors number
encountered which must be corrected before
attempting to activate this member as your active Explanation
inform policy.
GROUP statement policy names and INFORM
statement policy names cannot be duplicated in an
System action inform policy member.
The inform policy member is not loaded when the test Message Variables
keyword is specified.
name
The INFORM statement policy name or the GROUP
Operator response
statement group name which is a duplicate.
Note the results of the test and make corrections if number
necessary before loading the inform policy member. This is the line number in the policy member where
EZL452I DSIPARM MEMBER member_name the statement in error begins.
IS BEING USED FOR INFORM
POLICY System action
Explanation error is corrected, or the test of inform policy member
The DSIPARM member shown was loaded using the fails.
INFORMTB command and is the active inform policy
table. Operator response
Message Variables Correct either the GROUP or the INFORM statement
containing the duplicate policy name. All GROUP
member_name
names and INFORM policy names must be unique.
The DSIPARM member currently being used for
inform policy. EZL455I PROCESSING FAILED FOR
'INFORMTB member_name'
System action COMMAND
DSIPARM member member_name has been or is now
the active inform policy. Explanation
EZL453I The inform policy table was not loaded because of

INFORM POLICY ACTIVATED AT
errors. See previously issued error messages for
time ON date BY oper
details.
This message indicates when a DSIPARM member was member_name

activated using the INFORMTB command, and became The member name that was not activated.
the active inform policy table.
System action
Message Variables
time
error is corrected. If an inform policy member is
The time the inform policy table was activated.
currently active, it is not affected by this failure.

Correct the member as indicated by the preceding If the default value is not acceptable, make the
messages and attempt to reload it. necessary changes to the inform policy member and
reload it.
EZL456E statement STATEMENT STARTING
AT LINE number WAS NOT EZL458I INFORM POLICY policyname
PROPERLY TERMINATED ENTRY STARTING AT LINE number
CONTAINS AN INCORRECT VALUE
Explanation FOR KEYWORD keyword
An inform policy statement was not ended with a

Explanation
semicolon.
A keyword on the specified INFORM statement
Message Variables
contains a missing or incorrect value.
statement
Message Variables
The type of statement which was not properly
ended. policyname
number The name of the inform policy member containing
This is the line number in the policy member where the error.
the statement in error begins. number
The line number in the CONTACT statement.
The keyword which was defaulted.
error is corrected.
System action
Operator response The inform policy member will be loaded until the
error is corrected, or the test of the inform policy
Each inform policy statement must end with a
member fails.
semicolon (;), with the exception of the %INCLUDE
statement. Add the missing semicolon to inform policy
member and attempt to reload it. Operator response
EZL457I THE keyword KEYWORD IN THE Correct the inform policy member as indicated and try
CONTACT ENTRY STATEMENT to reload it.
STARTING AT LINE number WAS EZL459I INFORM POLICY NAME
DEFAULTED TO value policy_name WAS NOT FOUND IN
THE ACTIVE INFORM POLICY
Explanation MEMBER member_name
A contact entry keyword was assigned a default value.
Explanation
Message Variables
The current inform table does not contain any GROUP
keyword or INFORM statement for the policy name specified in
The keyword which was defaulted. the command.
number
Message Variables
The line number in the CONTACT statement.
value policy_name
The default value used. The INFORM or GROUP statement policy name.
member_name
System action The DSIPARM member which was loaded to form
the active inform policy.
If no other errors exist, the inform policy member will
be loaded using the specified values.
System action
The inform action ends. Check the inform policy or
group name specified and verify it corresponds to a

GROUP or INFORM statement in the active inform member_name
policy member. The DSIPARM member which contains the error.
number
Operator response This is the line number in the policy member where
Only defined GROUP and INFORM policies can be the SETUP statement in error begins.
referenced by the INFORM command and be specified errorcode
in the Notification Policy. The error code indicating the cause of the failure,
as follows:
EZL460I connection_type ACTION WAS
result ISSUED FOR POLICY 8
policy_name BY OPERATOR operid Value not found, or unexpected data found.
10
Explanation Inform log operator task is not currently
defined.
This message indicates the result of an attempt to
inform an operator using a specific type of connection. 12
Inform log operator task cannot be started.
Message Variables
14
connection_type Inform exit routine was not found
The type of inform connection attempted (for keyword
example, EMAIL, NUMPAGE). The SETUP statement keyword in error.
result
SUCCESSFULLY indicates the interface routine did System action
not report a failure. UNSUCCESSFULLY indicates
the interface routine detected a failure. The inform policy member will not be loaded until the
policy_name
fails.
The INFORM or GROUP policy name specified in
the request.
Operator response
operid
The operator who attempted the inform action. Correct the SETUP keyword in error and attempt to
reload the inform policy table.
System action EZL462E NO CONTACT ENTRIES WERE
This message is in response to an inform request. The FOUND IN INFORM POLICY
action taken by the system is specified by the result MEMBER member_name
insert.
Explanation
Operator response The subject inform policy member contains no contact
Only defined GROUP and INFORM policies can be entries.
referenced by the INFORM command or be specified in Message Variables
the Notification Policy. If the expected action did not
occur, update the inform policy, notification policy, or member_name
INFORM command invocation accordingly. The DSIPARM member which contains the error.
EZL461E INFORM POLICY MEMBER System action

member_name SETUP ENTRY
STARTING AT LINE number The inform policy member will not be loaded until the
CONTAINS SYNTAX ERROR error is corrected, or the test of inform policy member
errorcode IN keyword fails.

The subject inform policy member contains a syntax At least one contact statement is required in the
error in a SETUP statement keyword. inform policy member. Add a contact statement to
inform policy member and attempt a reload.
Message Variables

EZL463E THE INFORM POLICY LOGGING Operator response
FUNCTION WAS UNABLE TO If this message persists and the log contains entries,
WRITE TO OR CLOSE THE dsname contact your system programmer.
OUTPUT MEMBER

Explanation
Check the inform policy member using the NetView
The subject inform policy logging function detected a browse command or some other means to see if it
failure when attempting to write to or close the log contains entries. Check the NetView log to see if log
member. updates are failing. Correct the problem with the log
Message Variables data set and retry the command.
dsname EZL466I NO NEW INFORM ACTIONS WERE
The fully qualified data set name which cannot be SUCCESSFULLY ISSUED AS A
written to or closed. RESULT OF INTERFACE
PROBLEMS OR THE CURRENT
System action POLICY SETTINGS
The inform policy log entry may have been lost or the
Explanation
inform log may no longer be accessible.
An attempt was made to perform a reinform. At the
Operator response time of this attempt, either the interface was unable to
communicate with the service point, or the current
If this message persists, correct the problem with the policy specifies that no actions are warranted for the
data set to resume inform policy logging. original policy at this time.
EZL464I THE INFORM LOG FUNCTION IS
NOT ENABLED System action
The reinform is not issued.
Explanation
The inform policy logging function is not enabled and Operator response
cannot be accessed at this time. Verify the service point is available by using the ILOG
REINFORM/NEW option to display the policy name
System action associated with the entry. Determine if a contact must
The command to access the inform log ends. be defined for the current time and date. If corrections
are required, make the corrections, reload the inform
policy member, and attempt another reinform.
Operator response
EZL467E OUTPUT MEMBER member_name
The logging function must be enabled in the SETUP
IN DATASET dataset CANNOT BE
statement of the active inform policy member to
REPLACED WITH AN INFORM
enable ILOG® commands. Inactive inform logs can be
POLICY LOG MEMBER
viewed using the NetView browse command.
EZL465E UNABLE TO READ THE INFORM Explanation
LOG MEMBER OR THE MEMBER
CONTAINS NO ENTRIES Only an existing inform policy log can be overwritten
by an inform policy log. This protects all other types of
files from being overwritten.
Explanation
Message Variables
The inform policy logging function was unable to read
from the log member or the log member currently member_name
contains no entries. The member name which was not previously an
inform log.
System action dataset
The DSILIST data set name where member_name
The command issued to access the inform policy log
was found.
ends.

This attempt to update the inform policy log and all If the inform policy action was cancelled in error, or if
subsequent attempts will fail. The inform policy log all actions are being cancelled, contact your system
function cannot overwrite other types of members. programmer.

Disable the inform logging function or update the Verify the specified exit is functioning as expected.
SETUP statement MEMBER keyword with a valid log
EZL470E GROUP group_name STATEMENT
member name. Reload the inform policy member and
STARTING AT LINE number
verify actions can now be logged.
CONTAINS A REFERENCE TO
EZL468E INFORM PREPROCESSING EXIT ITSELF
11 DID NOT RETURN AN
EXPECTED GROUP OR POLICY Explanation
NAME
A group statement contains a reference to itself in the
list of other group or policy names specified.
Explanation
Message Variables
When AON Exit 11 returns a return code of 4 it must
set the task global variable EZLPOLEX with a valid group_name
policy name, group name, or list of these names. The GROUP statement which contains the error.
number
System action The line number in the policy member where the
GROUP statement in error begins.
No inform policy action is taken.
System action
Operator response
error is corrected, or the test of the inform policy
member fails.
Verify AON Exit 11 returns policy or group names Operator response
defined in the current inform policy table by placing
Correct the GROUP statement so it does not contain a
these names in the task global variable EZLPOLEX.
direct reference to itself or an indirect reference
EZL469I INFORM PROCESSING FOR through another group. Attempt to reload the inform
GROUP OR POLICY name WAS table following the correction.
CANCELLED BY exit
EZL471I LOG ENTRY SEARCH START TIME
DOES NOT PRECEDE THE STOP
Explanation TIME
An inform action was cancelled by an AON exit.
name The search start date and time does not precede the
The group or policy name whose action was stop date and time.
cancelled.
System action
exit
The AON exit which cancelled the current inform No search is performed.
status.
Operator response
System action
Correct the time parameters and retry the inform log
The current processing for an inform action was search.
cancelled by an AON inform policy exit.
EZL472I DATE OR TIME WAS NOT ENTERED
ON THE PANEL IN THE SAME
FORMAT AS SHOWN

A format error was detected in the date or time field The default search criteria was not updated.
entered on the inform log search panel.
System action
System action
No action is performed.
No search is performed. The search criteria specified
on the panel is reset. Operator response
Update the search criteria prior to attempting the
Operator response
search or cancel the search panel.
The date and time must be entered in the format
EZL476I connection_type ACTION WAS
shown on the inform log search panel. The format of
result FORWARDED FOR INFORM
these fields is validated; however, the contents are
POLICY policy_name BY
otherwise not validated. Correct the settings and retry
OPERATOR operid TO DOMAIN
the inform log search.
domainid
EZL473I NO RECORDS MEET THE
SPECIFIED SEARCH CRITERIA Explanation
If the service point is in another domain, this message
Explanation
documents the attempt to forward the inform policy
No inform log entries met the search criteria specified. action.
Message Variables
System action
connection_type
No action is performed. The search criteria specified The type of inform connection attempted (for
on the panel is reset. example, EMAIL, NUMPAGE).
result
Operator response SUCCESSFULLY indicates the action was
Alter the start and stop date and times, if specified, to forwarded. UNSUCCESSFULLY indicates the action
widen the search range. If appropriate, update either cannot be forwarded.
the name or message field search criteria. Retry or policy_name
cancel the search. The INFORM or GROUP policy name that
generated the request.
EZL474I SEARCH CRITERIA CANNOT BE
SPECIFIED FOR BOTH THE NAME operid
AND MESSAGE FIELDS The operator ID forwarding the request.
domainid
Explanation The domain the request is being forwarded to.
Search criteria cannot be specified in both the name
and message fields. System action
The inform policy action is either forwarded to the
System action service point domain or the attempt to forward it fails.
No action is performed. The search criteria specified
on the panel is reset. Operator response
Verify the service point was correctly specified in the
Operator response inform policy member. Verify the RGWAY link to the
other domain has been correctly defined.
Reenter the criteria with only the name or message
field specified and retry the search. EZL477I NO ACTIONS SPECIFIED FOR
POLICY policy_name AT THIS
EZL475I SEARCH CRITERIA WAS NOT
TIME
UPDATED, SPECIFY NEW
CRITERIA OR CANCEL

The INFORM policy is active but no actions are member_name
specified for the current day and time. The inform log file name.
Message Variables
System action
policy_name
The INFORM policy name that resulted in no The command issued to access the inform policy log
action. ends.
No INFORM policy actions are issued for the current None. This message is an indication that no inform
policy. actions have been taken, so the inform log is empty.
EZL480E THE AUTOMATION TABLE setting
Operator response NAME value IS NOT UNIQUE
This may be an acceptable result indicating that the
contact specified in the policy is not currently Explanation
available. If coverage for this policy is desired for the The automation table marker or listing name you
current day and time, the INFORM policy member specified was not unique. A unique name is required
must be updated and reloaded. for markers and listing files.
EZL478E INFORM LOG MEMBER Message Variables
member_name CONTAINS
INVALID DATA setting
Identifies which item is not unique. Set to
LISTNAME or MARKER.
Explanation
value
The inform policy logging function was unable to read Indicates the marker or listing name that is not
from the log member because it does not contain valid unique.
data.
member_name At least one of your requests failed.
The inform log file name.
Operator response
System action
Enter a unique marker or listing file name and retry the
The command issued to access the inform policy log task.
ends.
EZL481I ONE OR MORE REQUESTS FAILED,
VIEW THE RESPONSE WINDOW
Operator response
OR DSILOG FOR DETAILS
If this message persists and the log contains entries,
contact your system programmer. Explanation
The command option selected from a panel did not
successfully complete for all resources or statements.
If this problem persists then check the inform log file
and notify IBM Software Support. System action
EZL479I INFORM LOG MEMBER At least one of the requests failed. When this message
member_name CONTAINS NO is received while using the IPTRACE function, the
ENTRIES failing request reflects an SNMP query and the error
condition is logged.
Explanation
The inform policy logging function was unable to read
from the log member because no entries have been
logged.

Check the current panel for a function key for viewing You attempted to display a block or group of
responses. If no function key is labeled for this task, automation table statements. However, your cursor is
view the NetView log for more information. not located on a statement that is an endpoint to a
block or a member of a group. For an enable or disable
If the failing request is an SNMP query, resolve the
action, place the cursor on a group statement or at the
SNMP issue that caused the error and retry the
beginning of a block.
command.
EZL482I THERE IS NOTHING TO DISPLAY System action
FOR THE CURRENT REQUEST
The display or disable request fails.
Explanation
Operator response
You selected an option to display more detailed or
error information. No information is currently available Place your cursor on a different statement or select a
for your request. different action for the current statement.
EZL483E THE FOCUS AUTOMATION TABLE EZL485E THE AUTOMAN keyword

curtable IS LOADED AS curmarker KEYWORD WAS REJECTED WITH
RC= retcode
Explanation
Explanation
The automation table INSERT request cannot be
completed because of the currently loaded table The automation table INSERT request cannot be
specified in the message. completed. The automation table name or listing file
name is not valid.
Message Variables
Message Variables
curtable
The currently loaded automation table name is keyword
blocking the requested action. Contains the TBLNAME or the LISTNAME.
curmarker retcode
The marker for curtable is set to either FIRST or Identifies the following:
LAST. 100
The listing file name was omitted or is not
System action unique.
The INSERT request fails. 102
The automation table name you specified is
already loaded.
Operator response
This message is issued for one of the following System action
conditions. Update your INSERT request and retry the
task. The INSERT request fails.
• A new table cannot be inserted using the AT option

Operator response
when the focus table is marked as FIRST.
• A new table cannot be inserted using the BEFORE See the return code descriptions for more information.
option when the focus table is marked as FIRST. EZL490E THE ATTEMPT TO INSTORE THE
• A new table cannot be inserted using the AFTER CONTROL FILE FAILED
option when the focus table is marked as LAST.
• You requested a new table be loaded as FIRST or Explanation
LAST; however, another table is already loaded in During initialization, or reinitialization, the attempt to
one of those positions. load the control file using the PIPE INSTORE stage
EZL484E THE SELECTED STATEMENT IS failed
NOT A BLOCK ENDPOINT OR
GROUP MEMBER

Processing continues without resolving system The specified resource experienced the specified
symbolics. number of errors during the interval defined in the
control file for the frequent error threshold.
AON may continue to function normally if no system restype
symbolics are coded in the control file. If system The type of resource
symbolics are coded, the results may be
resname
unpredictable.
System programmer response location

See the NetView log for additional messages that
number
indicate why PIPE INSTORE failed. Correct the
The number of errors that have occurred
problem and restart AON if system symbolics are
defined. time
The time when the first error occurred
EZL501I RECOVERY FOR restype resname
date
ON location HALTED - number
The date when the first error occurred
ERRORS SINCE time ON date -
CRITICAL ERROR THRESHOLD
EXCEEDED System action
• If the specified resource is a network resource, AON
Explanation resumes the recovery process.
The specified resource experienced the specified • If the specified resource is a system resource, AON
number of errors during the time interval defined in issues the appropriate commands.
the control file for the critical error threshold.
Message Variables ON location CONTINUING - number
restype
INFREQUENT ERROR THRESHOLD
EXCEEDED
resname
The name of the resource Explanation
location
The specified resource experienced the specified
number of errors since the specified time. The
number infrequent error threshold has been exceeded, but the
The number of errors that have occurred recovery process for this resource resumes.
time Message Variables
restype
date
resname
System action The name of the resource
location
• If the specified resource is a network resource, AON
stops the recovery process.
number
• If the specified resource is a system resource, the
The number of errors that have occurred
recovery process stops or issues the appropriate
commands. time
date
ON location CONTINUING - number
FREQUENT ERROR THRESHOLD
EXCEEDED

System action MONITORING HAS BEEN
INITIATED
AON resumes processing.
Explanation
Operator response
AON automation is trying to recover the specified
If necessary, report the problem to your system
resource.
programmer.
Message Variables
System programmer response restype
Investigate the resource to determine what is causing The type of resource
the errors and correct the problem. resname
EZL504I restype resname IS AVAILABLE
(REPORTED BY reporter) location
Explanation
System action
AON determined that the specified resource is active.
AON continues processing.
Message Variables
restype Operator response
To stop recovery, issue the Timer command with the
resname resource name and delete the timer.
EZL507I REMINDER: restype resname ON
reporter
location HAS BEEN
A service point or a domain ID
UNRECOVERABLE FOR interval
System action
Explanation
AON returns the resource to an active status and
AON automation is trying to recover the specified
resumes processing.
resource, which has been unrecoverable for the
EZL505I RECOVERY TERMINATED FOR specified interval.
restype resname DUE TO ACTION Message Variables
BY OPERATOR operator
restype
Explanation The type of resource
resname
The specified operator stopped recovery for the
specified resource.
location
Message Variables The domain or service point
restype interval
The type of resource The amount of time since recovery was started
resname
The name of the resource Operator response
operator Review the status of the resource to determine
The ID of the operator whether intervention is required.
EZL508I RECOVERY MONITORING FOR
System action
restype resname ON location
AON stops recovery for the resource and resumes HALTED - RECOVERY
processing. MONITORING INTERVALS
EXCEEDED
EZL506I restype resname ON location
INACTIVE - RECOVERY

AON cannot resume the recovery for the resource The specified resource was initially reported to AON as
because the MONIT intervals set by the user were unavailable, however AON has determined that the
exceeded. resource is now available (active). For example, an
SNA switched PU resource might fail and then be
Message Variables
immediately recovered before AON is alerted to the
restype failure.
Message Variables
resname
The name of the resource restype
location
The domain or service point resname
System action reporter
The service point or the domain ID
AON stops the recovery process.
System action
Operator response
Intervene manually.
EZL511I member CONFIGURATION
EZL509I restype resname IS UNAVAILABLE MEMBER COMMON VALUES HAVE
(REPORTED BY reporter) BEEN INITIALIZED
AON determined that the specified resource is not AON used the control file data to create the common
available. variables that are used throughout the automation
Message Variables process.
restype Message Variables

The type of resource member
resname The name of the control file
reporter System action
The service point or the domain ID AON resumes processing.
System action EZL514I RECOVERY MONITORING FOR

restype resname ON reporter
AON resumes processing. TERMINATED - HIGHER NODE
highnode IS UNAVAILABLE
Operator response
If the resource is part of a component with a help Explanation
desk, consult the help desk. If problem persists, notify AON stopped monitoring the recovery of the specified
your system programmer. resource because the higher node for the resource is
inactive.
Message Variables
Determine which AON component the resource is part
restype
of and start problem determination procedures.
EZL510I restype resname WAS REPORTED resname
AS UNAVAILABLE, BUT IS NOW The name of the resource
AVAILABLE (REPORTED BY
reporter
reporter)
The service point or domain ID

highnode operator
The higher node The operator who activated the resource
EZL520I NO ENTRIES HAVE BEEN DEFINED
Operator response
If the resource is part of a component with a help Explanation
desk, run the help desk on the resource. If problems
There are no policy definitions in the control file.
persist, notify your system programmer.
Operator response
Determine which AON component the resource is part
of and start problem determination procedures.
EZL515I RECOVERY MONITORING FOR
restype resname ON reporter Update the control file with the policy definition
TERMINATED - AUTOMATION entries. For more information about updating the
FLAG SET OFF control file, see the IBM Z NetView Administration
Reference.
Explanation EZL524I NO infotype AVAILABLE FOR
RESOURCE: resname
AON tried to recover a resource when the AUTO
keyword was set to OFF.
Explanation
Message Variables
You attempted to use the AON workstation interface to
restype display the history of the specified resource at your
The type of resource workstation, but no information for the resource
resname exists.
Message Variables
reporter
The service point or the domain ID infotype
The information you requested (HISTORY)
System action resname
Recovery for the resource ends and processing
continues.
System action
Operator response AON continues processing.
If recovery is necessary, change the control file entry

Operator response
by going to AON Base Functions and selecting
Automation Settings. In Automation Settings, select Use another resource, or notify your system
Automation. programmer if you think there must be information
about this resource available through AON.
EZL517I restype resname HAS BECOME
ACTIVE FROM INTERVENTION BY EZL531I restype resname IS INACTIVE DUE
OPERATOR operator TO OPERATOR operator
INTERVENTION
Explanation
Explanation
The specified resource is available because the
specified operator intervened. The specified operator successfully deactivated the
specified resource.
Message Variables
Message Variables
restype
The type of resource restype
resname The type of resource
The name of the resource resname
The name resource

operator Operator response
The ID of the operator who deactivated the
The application program cannot be successfully
resource
opened again before it is successfully closed. Notify
your system programmer and provide the output from
System action your problem determination action.
EZL532I AUTOMATION ENVIRONMENT HAS
BEEN INITIALIZED Browse the NetView log for VTAM messages and see
the VTAM Messages and Codes manual.
Explanation EZL553I NO NOTIFY OPERATORS LOGGED
You initialized the automation environment. ON TO RECEIVE THE FOLLOWING
MESSAGES
System action
Explanation
This message precedes the message that is sent to the
EZL533I CURRENT STATUS OF resname IS automation log when no notification operators are
status logged on to receive messages.

The specified resource currently has the specified AON resumes processing.
status.
EZL554I MESSAGE = "text"
Message Variables
resname Explanation
This message displays the text of the message sent to
status the log when no notification operator was logged on to
The status of the resource receive it.
Message Variables
System action
text
AON resumes processing. The text of the message
EZL550I APPLICATION application WAS EZL561I STATUS OF domain1 OUTBOUND
NOT CLOSED CORRECTLY BY job GATEWAY TO DOMAIN domain2 IS
ACTIVE
Explanation
The system is closing a VTAM application program that Explanation
was opened by the specified job. The closing was not The outbound gateway from the initiating domain to
successful because the application was not closed the target domain is active.
within five minutes of closing initiation.
Message Variables
Message Variables
domain1
application The domain initiating the connection to the target
The name of the application domain
job domain2
The job that initiated the application program The domain to which the gateway is connected
System action EZL562I STATUS OF domain1 OUTBOUND

GATEWAY TO DOMAIN domain2 IS
The application is not closed and its resources are not INACTIVE
freed in VTAM.

Explanation 32
The domain is unknown.
The outbound gateway from the initiating domain to
the target domain is inactive. 36
An incorrect logon was specified.
Message Variables
40
domain1 The session was ended.
The domain initiating the connection to the
44
gateway
The logon is incorrect.
domain2
48
The domain to which the gateway is connected
An error occurred.
52
A timeout error occurred.
Ensure that the password for the gateway automation 56
operator on the target system is stored in the AON A GETPW error occurred.
password data set. To do this, use the GETPW
command with the INIT parameter. Where a RACF- 60
shared database is being used, ensure that the correct An error occurred when the RACF password
domain name is specified in the GETPW command. For was updated.
more information about the GETPW command, see the 64
IBM Z NetView Administration Reference. The table that was allocated for NNT sessions
reached its limit. Increase the numeric value
EZL563E ERROR ACCESSING domain1
on the RRD.*=nn statement that is defined in
OUTBOUND GATEWAY TO
the CNMSTYLE member or its included
DOMAIN domain2 - RC= rc
members.
Explanation
System action
You tried to log on to the domain of the adjacent
The operator is not logged on.
NetView but failed because of the specified return
code (RC).
Operator response
Message Variables
Note the error and correct the problem. If problems
domain1 persist, notify your system programmer.
The domain ID of the local NetView
domain2 System programmer response
The domain ID of the physically adjacent NetView
defined in the GATEWAY control file entry Note the return code and correct the problem.
rc EZL564E ERROR ACCESSING domain1

The return code: OUTBOUND GATEWAY TO
DOMAIN domain2 - id REVOKED
4
ON domain
The RACF data set was not allocated.
8
Explanation
The Password was not found.
12 You attempted to log on to the domain of the adjacent
An incorrect operator ID was defined. NetView, but the attempt failed.
An incorrect password was specified. domain1
20 The domain ID of the local NetView
The domain is not controlled with RACF. domain2
24 The domain ID of a physically adjacent NetView
The password has expired. that is defined in the GATEWAY control file entry
28 id
RACF failed. The ID of the operator

domain Explanation
The domain name of a physically adjacent NetView
The inbound gateway from the target domain to the
that is defined in a GATEWAY control file entry
local domain is inactive.
Revokes the operator ID. domain1

The domain ID of current NetView
Operator response domain2
The domain ID of an adjacent NetView that is
Notify your system programmer. defined in a GATEWAY control file entry
System programmer response EZL571I resname SUBSYSTEM STATUS FOR

JOB job IS status - REQUESTED BY
Reinstate the operator ID. OPERATOR operator
EZL567I FOCAL POINT DOMAIN (focalpt)
FOR domain LOST, BACKUP Explanation
FORWARDING TO backup The specified operator changed the status of the
STARTING specified resource to the specified status.
Message Variables
Explanation
resname
AON lost communications to the focal-point domain.
The backup focal-point domain receives forwarded
messages. job
The job name
Message Variables
status
focalpt The status at the time of the message
The focal-point domain
operator
domain The operator who requested the change in status
The domain from which messages are being
forwarded EZL572I OPERATOR CGLOBALS NOT
INITIALIZED - UNABLE TO ROUTE
backup
COMMAND command
The backup focal-point domain
EZL568I STATUS OF domain1 INBOUND Explanation
ACTIVE AON cannot route the specified command to another
operator for processing because AON did not initialize
the CGLOBAL values.
Explanation
Message Variables
The inbound gateway from the target domain to the
local domain is active. command
The command that AON tried to route
Message Variables
domain1 System action
The domain ID of the current NetView
AON does not route the command.
domain2
The domain ID of an adjacent NetView that is
Operator response
defined in a GATEWAY control file entry
Notify your systems programmer.
EZL569I STATUS OF domain1 INBOUND
INACTIVE System programmer response
Investigate why AON did not initialize the CGLOBAL
values and initialize AON again.

EZL573I AUTOMATED task restype HAS AON INITIALIZATION HAS BEEN
BEEN RESTARTED STOPPED.
AON restarted the specified automation operator. AON issued a START command for the Automation
Configuration Task, EZLTCFG. However, no messages
Message Variables indicating startup or failure were processed within the
task allotted timeout period, or the GO command was used
The task ID to interrupt the wait for the startup or failure message.
restype
The type of resource System action
EZL600W program RESUMING - AON initialization is stopped.

PARAMETER(S) IGNORED
Operator response
Explanation Notify your system programmer.
You entered the NLOG command using parameters
that the NLOG command processor ignored. System programmer response
Message Variables Logon to NetView to start the task from the Command
Facility through the command: START TASK=EZLTCFG.
program
Take action based on messages received. If EZLTCFG
The program that resumes processing
starts normally, resume initialization through the
command: EXCMD AUTO1,EZLEANTL. If you do not
System action use AUTO1, substitute the task to which EZLEANTL is
The NLOG command processor resumes processing usually run.
the specified program. EZL609E POLICY FILE(S) COULD NOT BE
EZL607E LOAD OF CONTROL FILE member LOADED
FAILED
Explanation
Explanation You attempted to load policy definitions into the Policy
The specified file cannot be successfully loaded into Repository, but there were no valid policy files defined
the policy repository. in the CNMSTYLE member. Or, you did not specify a
valid POLICY.&DOMAIN definition in the CNMSTYLE
Message Variables member.
member
The name of the control file being loaded System action
The load of policy definitions is ended.
System action
The load of the policy definitions is ended. Operator response
Operator response
Notify your system programmer. System programmer response
Review the policy file definitions in the CNMSTYLE
System programmer response member and make any necessary updates. If you need
Issue a POLICY REQ=TEST command and note the to make changes, see IBM Z NetView Installation:
errors. See the IBM Z NetView User's Guide: Automated Getting Started for information on how to modify the
Operations Network for more information. CNMSTYLE member.
EZL608E AON AUTOMATION EZL610E FAILED TO OPEN LOG FILE

CONFIGURATION TASK EZLTCFG
INITIALIZATION HAS FAILED. Explanation
You tried to open a log file, but your attempt failed.

The NLOG command processing stops. Enter the NLOG parameters again to view the active
log, which contains data. To browse the inactive log,
Operator response verify that it contains data.
There is a problem with the VSAM file of the EZL632I AON AUTOMATION LOG BROWSE
automation log. Delete and redefine the active log TERMINATED
according to the procedure in the SAMPLIB and start
NetView again. Explanation
EZL615E FAILED TO CLOSE LOG FILE The NETLOG is no longer displayed.
EZL633I AUTOMATION LOG TASK (task)
Explanation NOT STARTED. - "task" ENTRY
You tried to close a log file, but your attempt failed. NOT SPECIFIED IN THE CONTROL
FILE.
System action
Explanation
NLOG command processing stops.
AON initialization tried to start the LOG task but the
LOG task is not defined in the control file.
Message Variables
Notify IBM Software Support.
task
EZL623E SECONDARY LOG FILE NOT
The name of the AON LOG task (EZLTLOG)
DEFINED
System action
Explanation
You issued the NLOG command to view the secondary
log, but a secondary log does not exist.
Operator response
Operator response Define the EZLTLOG task in the AON control file and
load the control file again.
Ensure that a secondary log has been allocated. If a
secondary log has not been allocated, run job to EZL634I AUTOMATION LOG TASK (task)
allocate it. Ensure that the secondary log is included in NOT STARTED. - "task" COULD
the NetView JCL procedure. For more information NOT BE RETRIEVED FROM THE
about allocating secondary logs, see the IBM Z CONTROL FILE.
NetView Administration Reference.
EZL627E LOG FILE IS EMPTY OR Explanation
INACCESSIBLE AON initialization tried to start the LOG task but the
EZLCFG program cannot retrieve the EZLTLOG entry
Explanation from the control file.
You attempted to browse a log that is empty or Message Variables
inaccessible.
task
The name of the AON LOG task (EZLTLOG).
System action
The NLOG command processing stops. System action

Notify your system programmer. AON continues processing.

Manually issue the 'EZLCFG Notify your system programmer.
REQ=DISP,ENTRY=EZLTLOG,TYPE=*' command and
note the error back from EZLCFG. Make corrections System programmer response
based on the error message. If the problem persists,
contact IBM Software Support. Start the LOG task manually.
EZL635I AUTOMATION LOG TASK (task) EZL637E NO ACTIVE LOG CURRENTLY

NOT STARTED. - task NONE AVAILABLE
SPECIFIED IN THE CONTROL FILE.
Explanation
Explanation You attempted to access an active automation log, but
AON initialization tried to start the LOG task but, no active automation log was available.
because the control file entry is EZLTLOG NONE, the
log file does not start. System action
Message Variables NLOG command processing stops.
task
The name of the AON LOG task (EZLTLOG) Operator response
Ensure that the EZLTLOG task is active. If the current
System action active log has recently filled, AON captures the
message LOG FILLED and tries to switch logs.
Switching logs may result in no active log being
available at this time. Watch for the message LOG
Operator response NOW ACTIVE and issue the NLOG command again.
Notify your system programmer. EZL638E NO INACTIVE LOG CURRENTLY
AVAILABLE
To start the LOG, change the LOG entry in the control Explanation
file. See the IBM Z NetView Administration Reference You attempted to browse an inactive automation log,
for more information. Load the control file again. but no inactive log was available.
EZL636I AUTOMATION LOG TASK (task)
NOT STARTED. - "command" HAS System action
FAILED OR operator IS HUNG.
AUTOMATION MAY FAIL.
Operator response
Explanation
Ensure that the EZLTLOG task is active. If the current
AON initialization tried to start the LOG task but the
active log recently filled, AON captures the message
START TASK command failed, or the operator ID that
LOG FILLED and tries to switch logs. Switching logs
started the task is hung.
may result in no inactive log being available at this
Message Variables time. Watch for the message LOG NOW ACTIVE and
issue the NLOG command again.
task
The name of the AON LOG task (EZLTLOG) EZL639E LOG CLEAR SUCCESSFUL
command
The START TASK command Explanation
operator You cleared a log by issuing a NLOG CLEARxxxx
The operator ID that tried to issue the START TASK command.
command

If you issued the NLOG CLEAR command when the domain
inactive log was not being viewed, the inactive log The name of the destination domain
cleared. If you issued the NLOG CLEARSCND
command when the secondary log was not being System action
viewed, the secondary log cleared. If you issued the
NLOG CLEARPRIM command when the primary log AON recognizes that GATEWAY connections are
was not being viewed, the primary log cleared. available to the destination domain.
EZL640I NLOG ENDED - LOG SWITCH IN EZL652I gatoper STARTING GATEWAY

PROGRESS SESSIONS WITH TARGET
DOMAINS
Explanation
Explanation
You attempted to view an automation log while
automation logs were being switched. The specified gateway operator is trying to log on to a
remote domain.
The NLOG command processing stops. gatoper
The automated gateway operator who is trying to
Operator response log on to the remote domain
To view the automation log, wait for the message LOG EZL655I number RECORDS action FOR
NOW ACTIVE and issue the NLOG command again. COMPONENT component
EZL645I ALL NLOG BROWSE TASKS

Explanation
POSTED FOR INACTIVE LOG
This message goes to the log and details the results of
Explanation issuing the DBMAINT command.
You attempted to clear the inactive log by issuing the Message Variables
NLOG command. The tasks that are currently viewing number
the inactive log are scheduled to end. The number of records affected.
action
System action The action performed on the record. The record is
The NLOG command processing stops. DELETED, READ, KEPT, or ERROR.
component
EZL646I NO OPERATORS BROWSING THE
The name of the component on which the action
INACTIVE LOG
was performed.
Explanation EZL660I CURRENT FOCAL POINT IS

newfocal, WAS oldfocal, FOR
An automation operator attempted to clear the
domain FOR SYSTEM ddf
inactive log by issuing the NLOG CLEAR command
while no other operator was viewing the log.
Explanation
System action AON switched gateway focal-point NetView domains
because of an outage of the primary focal-point
NetView or because a primary focal-point NetView
EZL650I DESTINATION DOMAIN domain domain was restarted. If the switch occurred because
RESPONDED of an outage of the primary focal-point, AON switches
to the backup focal point. If the switch occurred
because a primary focal-point NetView domain was
Explanation
restarted, the flow switches back to the primary focal
While monitoring gateway sessions, AON routed a point.
command to the specified destination domain. The
Message Variables
destination domain currently has NNT sessions with
your domain.

newfocal domain1
The new focal-point NetView domain The NetView domain issuing the request.
oldfocal domain2
The old focal-point NetView domain or RESET or The NetView domain to which the request was
NONE sent.
domain product
The NetView from which domain messages are The name of the product being run on domain2,
sent including the system name, product name, version
ddf number, and release number. OLD refers to an
The Dynamic Display Facility (DDF) in the NetView previous product that does not support the
domain from which the messages are sent EZLE1REQ function.
Gateway connections with the destination domains are AON stops gateway connections with the destination.
lost or established. EZL663I DOMAIN domain STATUS IS
EZL661I DOMAIN domain1 IS status, REPORTED by repdomain
COMMUNICATING WITH domain2,
VIA domain3, product Explanation
The specified reporting domain reported the status of
Explanation the other specified domain but does not recognize that
The first specified NetView domain established status. Known statuses are ACTIVE, INACTIVE,
communications with the second specified NetView INVALID, and RESET.
domain through the third specified domain. Message Variables
Message Variables domain
domain1 The NetView domain whose status is being
The NetView domain that issued the request. reported
domain2 status
The NetView domain that received the request. The unrecognized status
domain3 repdomain
The NetView domain through which the request The domain ID of the reporting domain
was routed.
Operator response
product
The name of the product being run on domain2, Notify your system programmer.
including the system name, product name, version
number, and release number. OLD refers to an old System programmer response
product that does not support the EZLE1REQ
function. The reporting domain does not recognize the status of
another domain. The reporting domain originated the
status. The problem is that the product on the
System action
reporting domain is in error or that it supports statuses
AON establishes gateway connections with the domain not recognized by the product running on the domain
that received the request. whose status is being reported.
EZL662I DOMAIN domain1 HAS STOPPED EZL664I NO FOCAL POINT IS AVAILABLE
COMMUNICATING WITH domain2
product Explanation
No focal-point NetView domain is available at this
Explanation
time. Both the primary and backup focal-point
The first specified domain sent a request to the second NetView domains are unavailable.
specified domain but cannot communicate with it.
EZL665I OUT domain EZLE1REQ: command
Message Variables

Gateway trace is running on the specified domain. The The specified domain rejected the specified command.
specified command currently being used is EZLE1REQ.
Message Variables
Message Variables
domain
domain The domain that received the request
The NetView domain to which the request was command
sent The rejected command
command
The command that was sent to the domain Operator response
Use this message to analyze gateway activity. System programmer response
EZL666I IN domain EZLE1REQ: command The NetView domain the request was sent to does not
support the request or the request is not correct. If the
Explanation request is not correct, correct it and try again.
While a Gateway trace was running on the specified EZL669I REQUEST LOOPED BACK TO
domain, an operator issued the specified command by domain1, SENT ON domain2,
using the EZLE1REQ command. RECEIVED FROM domain3,
REQUEST: command
Message Variables
domain Explanation
The domain that sent the command
You sent a gateway command from the first specified
command
domain to the second specified domain, but the
The command that sent from the domain
command erroneously returned to the first domain by
way of the third specified domain. This error indicates
System programmer response a loop in the gateway routing.
Use this message to analyze gateway activity. Message Variables
EZL667I REQUEST TO DOMAIN domain domain1
WAS REJECTED AT adjdomain , NO The NetView domain that issued and received the
ROUTE DEFINED command
domain2
Explanation The NetView domain to which the command was
You attempted to route a request to the specified originally routed
domain through an adjacent domain and the request domain3
failed, or an adjacent domain requested the status of a The domain that routed the command to the
destination domain but no gateways between the issuing NetView domain
domains are defined. command
Message Variables The issued command
domain
The domain to which the request was sent
adjdomain Review the gateway definitions to determine the cause
The adjacent domain through which the request is of the loop.
being routed EZL670I COMMAND (command) WAS
EXECUTED IN DOMAIN domain BY
System programmer response OPERATOR operator
Define routes from the adjacent NetView domain to
the destination NetView domain. Explanation
EZL668I DOMAIN domain REJECTED The specified operator issued the specified command
REQUEST: command from the specified domain.

Message Variables domain
The NetView domain to which the gateway request
command
was sent
The issued command
ezle1req
domain
The gateway request that was sent
The NetView domain that received and ran the
command EZL674I DOMAIN domain IS NOT ACTIVE.
operator GATEWAY REQUEST REJECTED
The operator ID that sent the command ezle1req
EZL671I COMMAND (command) FAILED Explanation

EXECUTION IN DOMAIN domain,
RC= rc You attempted to send a gateway request to the
specified domain but failed because the gateway to
Explanation the domain is not active.
The specified command cannot run in the specified Message Variables

domain. domain
Message Variables The destination NetView domain
ezle1req
command
The failed gateway request.
The issued command
domain EZL675I GATEWAY PREFIX UNKNOWN
The NetView domain that cannot run the command FOR domain
rc
The return code from the command that cannot Explanation
run You made a gateway connection to the specified
NetView domain, but because a previous product is
Operator response being run on that domain, gateway processing cannot
recognize the product.
The return code is specific to the command. Record
the information for follow-up action. Message Variables
EZL672I GATEWAY CONVERSION FAILED domain

FOR command The NetView domain running an earlier release of
the product
Explanation
System action
The specified command, issued through a gateway,
cannot be processed in the domain to which the The EZLE1REQ command does not forward commands
command was sent. or responses to the specified NetView domain.
Message Variables
Operator response
command
Recycle NetView or end the NNT session to the
The issued command
specified NetView domain in order to retry to establish
EZL673I DOMAIN domain IS NOT DEFINED. a session with this domain.
GATEWAY REQUEST REJECTED.
ezle1req System programmer response
The EZLE1REQ command is not supported in the
Explanation
remote domain. An EZLCFG was issued to determine
The gateway request that was sent to the specified whether the old product in the remote domain uses
domain cannot be processed because gateways to the the EZL or EHK prefix, but no response was received.
domain are not defined. Determine why the attempt to establish a connection
failed to get a response to EZLCFG within the 2-minute
Message Variables
timeout allowed.

EZL676I ROUTING COMMAND command TO Operator response
DOMAIN ID domain Notify your system programmer.
Explanation
AON is transferring the specified command to another Review the TCP390 policy definition that is referred to
domain.
in this message and determine whether you need any
Message Variables of the keywords that are defined.
command EZL872I COMMAND command NOT
The command that was routed DELIVERED TO OPERATOR
domain operator, REASON errormsg
The domain to which the command was routed
Explanation
EZL700E EZLMSG msgnum RC= rc
AON cannot route the specified command to another
automation operator. AON did not receive the DSI001I
Explanation
or DSI268I messages, which indicate that the
EZLMSG detected an error while formatting a command has run successfully on the task.
message.
Message Variables
Message Variables
command
msgnum The name of the command to be sent to the
The message number that was being formatted. specified operator
rc operator
The return code received from EZLMSG. The ID of the operator who is supposed to issue
the specified command
Operator response errormsg
Notify your system programmer. The message received when the attempt was
made to run the specified command on the
specified operator ID
Severity:
Verify that the AON message modules and EZLMSG
have been installed correctly. If there is no apparent 0
cause for the failure, contact IBM Software Support.
Operator response
EZL710I EZL710I One or more policy_type
policy_name keywords found. Notify your system programmer.

During resource discovery for stacks, one or more Verify that the task in question is active and able to run
policy keywords was found for the stack. Those commands and that it is not severely backlogged with
keywords will be used in place of any information that programs to be run. If the task is working properly,
has been discovered about the stack. notify IBM Software Support.
Message Variables EZL880I type SESSION TO target IS
policy_type ALREADY ACTIVE
A valid policy definition, such as TCP390.
policy_name Explanation
The name of the TCP390 policy statement You already have a known active session with the
containing the keywords. target NetView domain.
Message Variables
System action
type
The stack discovery processing continues, using the The type of session, which are NNT and RMTCMD
TCP390 keywords.

target System action
The target NetView domain
The request is delayed until an operator provides the
correct information or cancels the request.
System action
AON ignores the start request. Operator response
EZL881I type SESSION TO target IS NOT Enter the correct session information or cancel the
ACTIVE request.
EZL884I CONFLICTING INFORMATION -
Explanation CDLOG ENTRY SHOWN
You selected a session with the specified target
domain, but that domain is not active. Explanation
Message Variables AON found conflicting information when trying to run
an action for the CDLOG command. AON displays the
type
information defined in the control file.
The type of session, which are NNT and RMTCMD
target System action
The target NetView domain
AON delays the request until an operator provides
System action correct information or cancels the request.
AON ignores the request. Operator response
Operator response Provide correct information, such as an operator ID or

password, or cancel the request. Notify your system
Start a session before attempting to send a command. programmer of any changes you make to the CDLOG
control file entry.
EZL882I OPERATOR operator ALREADY
LOGGED ON target
Explanation Modify the CDLOG control file entry for the operator.
The specified NetView operator is already logged on in EZL887I DOMAIN target DID NOT RESPOND
the specified target NetView domain.
operator The CDLOG attempted to communicate with the target
The ID of the target operator domain but cannot because the target domain is not
responding to any requests.
target
The target NetView domain name Message Variables
target
System action The target NetView domain
AON delays the start request until you enter another
operator ID or cancel the request. Operator response
Operator response
Provide another NetView operator ID or it cancels the System programmer response
request.
Verify that there are no problems in the target domain.
EZL883I INVALID SESSION INFORMATION
EZL888I UNABLE TO START SESSION TO
- PLEASE REENTER
target. PRESS F4 TO VIEW ERROR
MESSAGE
Explanation
You provided incorrect information for starting the
cross-domain NetView session.

Explanation upper
The upper selection boundary
You logged on and CDLOG attempted to start a
session, but the attempt failed.
Operator response
Message Variables
Correct the selection and enter it again.
target
The target NetView domain EZL902I CURSOR IS NOT LOCATED ON
VALID RESOURCE OR SELECTION
System action
Explanation
The target request stops.
You selected an entry on a cursor-sensitive panel, but
did not place the cursor in correct position. For
Operator response
automation table management (AUTOMAN), you
Press F4 to view the error message received when you placed your cursor on a statement that cannot be
attempted to start the session. subject to the action selected.

Determine why the session cannot be started. Move the cursor to an appropriate position and try
again.
EZL889I NO MESSAGE ERRORS FOUND
EZL903I THE INPUT FOR variable IS NOT
Explanation SEQUENTIAL
You attempted to view error messages for starting up
Explanation
a cross-domain NetView session, but there are no
error messages to display. An ordered set of numbers or letters was expected as
input, but there were one or more skipped in the
EZL900I ONLY SELECTION selection IS
sequence.
VALID
Message Variables
Explanation variable
You attempted to change a selection that is already The input in error.
set.
Operator response
Message Variables
Correct the input and enter it again.
selection
The selection the operator attempted to change EZL904I NO ADDITIONAL HELP AVAILABLE

Correct the entry and enter it again. AON cannot locate help for a command.
EZL901I SELECTION selection IS INVALID. EZL905I key KEY NOT ACTIVE
TYPE A NUMBER BETWEEN lower
AND upper Explanation
You pressed the specified inactive key, but the key is
Explanation
inactive.
The specified selection entered by the operator is
Message Variables
incorrect.
key
Message Variables
The key that is inactive
selection
The selection entered Operator response
lower
Select the correct function key and try again.
The lower selection boundary
EZL906I FIRST LINE OF DATA DISPLAYED

You attempted to scroll backwards on a list panel, but You changed the operator ID in AONTRACE. The
the top of the list is already displayed. settings are those of the specified operator.
EZL907I LAST LINE OF DATA DISPLAYED Message Variables
operator
Explanation The new operator ID
You attempted to scroll forward on a list panel, but the
display is already at the bottom. Operator response
EZL908I SETTINGS REPLACED Enter the new settings or change the displayed
settings.
Explanation EZL915I OPERATION CANCELED. NO
You changed the setting for the message headers that SELECTION MADE
are used to handle messages.
Explanation
EZL909I REQUESTED STATE ALREADY SET
You quit or canceled from a selection menu.
Explanation EZL916I NO LOADER TABLES FOUND
You attempted to change a setting, but that setting is
already set. Explanation
AON cannot find any option definition tables to
Operator response display.
Select another setting or command and try again.
Operator response
EZL910I ENTER A SELECTION
Explanation
You pressed the Enter key on a selection menu
without specifying an option. Select an option before Check the control file for the appropriate INSTALLOPT
you press Enter. keywords for the component. Specifically, check for a
defined DEFTAB entry on the INSTALLOPT keyword.
Operator response EZL917E ERROR OCCURRED. BROWSE LOG
Select an option and press Enter. FOR MORE INFORMATION
EZL911I OPTION option NOT ACTIVE Explanation

One of the following errors occurred:
Explanation
• You entered multiple actions from a list panel,
You attempted to select the specified option from a
resulting in at least one error.
panel, but the option is not active.
• An unexpected error occurred while data was being
Message Variables processed from a request.
option
The option that is inactive Operator response
Browse the NETLOG for additional information and
Operator response take the appropriate action. Retry the request. If the
Select another option and try again. If the option is error persists, contact IBM Software Support.
disabled and you want to use it, go to AON support
EZL918E ERROR IN program PROCESSING
functions to enable it and select it again. Otherwise,
PANEL panel. VIEW RC= rc
choose another option.
EZL912I TRACE SETTINGS FOR OPERATOR
operator DISPLAYED

Explanation performs the needed action on the subcomponent and
on the higher component.
The specified program attempted to view the specified
panel but received the specified return code from the EZL921E ERROR VIEWING TABLE table.
VIEW command processor. VIEW RC= rc
Message Variables
Explanation
program
The name of the program You attempted to view the specified table in the list
with the VIEW command processor, but your attempt
panel
failed.
The name of the panel
rc Message Variables
The return code table
The name of the table.
Operator response rc
Notify your system programmer. The return code from the NetView BROWSE
command.
Operator response
Notify IBM Software Support.
EZL919I ALL ACTIONS SUCCESSFULLY
COMPLETED System programmer response
Explanation See the error code in the IBM Z NetView Customization

Guide. Check for error messages in the log to
You successfully entered multiple selections from a determine the cause of the error.
list panel and all selections ended successfully.
EZL922I command COMMAND SCHEDULED
EZL920I COMPONENT subcomponent FOR EXECUTION
CANNOT BE action BECAUSE
component IS NOT action Explanation
Explanation You scheduled the specified command to run.
You attempted to enable or initialize a subcomponent Message Variables

in AONENABL, but the higher component was not command
enabled or initialized. The name of the command
Message Variables EZL923I ONLY NUMERIC DATA IS VALID.
subcomponent data IS INVALID
The name of the lower AON component.
component Explanation
The name of the higher AON component. You entered the specified nonnumeric data in a
action numeric field, or you entered an invalid scroll value.
The action attempted against the subcomponent. Message Variables
The action can be ENABLE or INITIALIZE.
data
The non-numeric data or invalid scroll value that
System action
was entered
The subcomponent is not enabled or initialized.
Operator response
Operator response
Type the correct numeric data or, for the scroll value,
To enable or initialize the subcomponent, press the type a positive number, and try again.
Tab key to move the cursor to the higher component
and enable, or initialize, the higher component. This EZL924I PRESS key TO action OR F12 TO
CANCEL

You added a configuration entry and must press the You attempted to initialize a component that does not
specified key to process the specified action. have an initialization routine. This is not an error
message. This message is for information only.
Message Variables
Message Variables
key
The function key that is used to process the action component
action The name of the AON component
The action to be processed
System action
Operator response The component initialization flag is set to Y.
To process the action, press the correct function key. EZL929I COMPONENT component CANNOT
To cancel the action press F12. BE action BECAUSE IT IS NOT
EZL925I CANNOT CHANGE VALUE value INITIALIZED
You attempted to change the specified value but your You attempted to enable a component that has not
attempt failed. been initialized.
value component
The value you attempted to change. The name of the AON component.
action
System action The action you attempted. The action can be
ENABLED or RESET.
AON does not process the command.
EZL926I TASK TYPE OF type NOT ALLOWED System action
TO BE STARTED, STOPPED OR The component is not enabled or reset to its default.
FORCED
Operator response
Explanation
If you want to enable or reset the component, you
You cannot process a task with the specified type must select the action to initialize the component and
because the type cannot be stopped or forced inactive. press Enter. After doing this, select the action,
Message Variables 1=ENABLE or 3=DEFAULT, for the component and
press Enter.
type
The type of task EZL930I SESSION(S) ENDED
EZL927I TASK TYPE OF type NOT ALLOWED
TO BE RECYCLED Explanation
The requested CDLOG sessions stopped.
Explanation
EZL931I SESSION TYPE = type, NOT
In the Automation Task List display, you attempted to DEFINED FOR DOMAIN = domain
recycle a task that was not an appropriate resource to
recycle. Explanation
Message Variables You attempted to start a CDLOG session that is not
type defined for the target NetView domain.
The type of task Message Variables
EZL928I COMPONENT component DOES type
NOT HAVE AN INITIALIZATION The session type. The types are NNT and RMTCMD.
ROUTINE

domain System action
The target NetView domain.
The session cannot be started.
System action
Operator response
The system ignores the start request.
Restart the session by using a correct NetView
operator ID or notify your system programmer.
Operator response
To start a session, notify your system programmer. System programmer response
Define a correct NetView operator ID in the target
System programmer response domain.
Add the appropriate definitions to the control file to EZL937E INVALID PASSWORD ENTERED
allow the session to start.
EZL932I SESSION(S) STARTED Explanation
The NetView operator ID password used to start the
Explanation session is not correct for the target domain.
AON started the cross-domain NetView sessions that
you requested. System action
EZL934I PLEASE ENTER USER ID The session cannot be started.

You must enter a correct NetView operator ID to start Restart the session using a correct password or notify
a cross-domain session. your system programmer.

AON delays the start request until you enter a correct Define a correct password for the NetView operator in
NetView operator ID. the target domain.
EZL938I ISSUING COMMAND = command.
Operator response PRESS F6 TO ROLL BACK TO
Enter a correct NetView operator ID for the target CDLOG
domain.
Explanation
EZL935I PLEASE ENTER PASSWORD
AON is running the command you requested in the
Explanation target NetView domain. After the command stops
processing, you must roll back to CDLOG.
You must enter a password to start a cross-domain
NetView session. Message Variables
command
System action The requested command
The start request is delayed until you enter a correct
NetView operator password. System action
The command is routed to the target NetView domain.
Operator response
Enter a correct password for the NetView operator. Operator response
Wait until the response has completed and rollback to
EZL936E INVALID OPERATOR ID ENTERED
the previous panel.
Explanation EZL939I PRESS ENTER TO START SESSION

USING CDLOG DEFINITIONS
The NetView operator ID used to start the session is
not correct for the target domain.

Explanation EZL942E UNABLE TO START type SESSION
TO DOMAIN target.
You must confirm the start of a CDLOG session using
the appropriate definitions in the control file.
Explanation
Operator response You attempted to start a cross-domain NetView
session, but your attempt failed.
Press Enter to start the session using the CDLOG
definitions displayed or press F12 to cancel the Message Variables
session.
type
EZL940E NO SYSTEM NAME SPECIFIED IN The type of session. The types are NNT and
THIS DOMAIN RMTCMD.
target
Explanation The target NetView domain.
You did not supply the system name for a Dynamic
Display Facility (DDF) command, and AON cannot System action
determine which system to use. AON cannot start the session.

The DDF command stops. Notify your system programmer.

Specify the system name and try the command again. Determine why the error occurred. This message is
EZL941E UNABLE TO START type SESSION displayed when AON does not cause the error.
TO DOMAIN target - INVALID EZL951I DUPLICATE SELECTIONS FOUND
SESSION DEFINITION.
Explanation
Explanation
You attempted to enter a program trace into the list
The request to start a cross-domain NetView session more than once. You attempted to enter a selection
failed because session definitions in the control file into the Session Status Filters panel more than once.
were not correct.
type AONTRACE is not set and the session status filters are
The type of session. The types are NNT and not changed.
RMTCMD.
target Operator response
The target NetView domain.
Remove the duplicate entry and press Enter again.
System action EZL952E INVALID CURSOR LOCATION

AON does not start the session.
Explanation
Operator response You attempted to issue a command from a row that
cannot issue commands. The cursor must be
Notify your system programmer. positioned on a row that can issue commands before
you press Enter.
Determine why the error occurred and update the Operator response
control file CDLOG definitions. For more information Move the cursor to a valid row and press Enter.
about CDLOG definitions, see the IBM Z NetView
Administration Reference. EZL953E COMMAND LENGTH TOO LONG.
MUST BE LESS THAN OR EQUAL
TO length

You attempted to issue a command that is too long. To return to the operator interface, enter GO on the
command line.
Message Variables
length System action
The length of the command on the RUNCMD.
When a command is issued, you are rolled to the
command facility to see the response. To return to the
System action
operator interface, enter GO on the command line.
The command does not process.
EZL965I CURRENT DATE PAST REQUESTED
DATE date
Operator response
Change the command and press Enter. Explanation
EZL960I DEFAULTS ENTRY CANNOT BE You attempted to set a timer for the specified date, but
DELETED the date had already passed.
Message Variables
Explanation
date
You attempted to delete a DEFAULTS entry from the The date entered by the operator
control file, but your attempt failed because you are
not authorized to delete the DEFAULTS entries. You
System action
are authorized only to change them.
The timer fails to set.
Operator response
Operator response
If necessary, change the DEFAULTS entries or make
another selection. Correct the date and try again.
EZL961W num NOAUTO INTERVALS EXIST. EZL966E BOTH INTERVAL AND DAYS
NO CHANGES CAN BE MADE FROM CANNOT BE 0 WHEN TIMER TYPE
THIS PANEL. = AFTER.
The Recovery Setting command list detected more You attempted to change the timer type AFTER, but
than five NOAUTO intervals defined for this resource in the attempt failed. The value of interval or days must
the control file. No changes to recovery settings are be non-zero.
allowed from this panel.
num AON cannot update the timer.

The number of NOAUTO intervals
Operator response
Operator response Correct the input and try again.
Notify your system programmer. EZL967E END TIME CANNOT BE LESS THAN
OR EQUAL TO START WHEN DAY
System programmer response IS NOT = '*'
Edit the control file to make any changes to the
recovery settings. Explanation
EZL962I **** NOTICE: ENTER 'GO' WHEN When you specify a day to turn off recovery, the end
READY TO RETURN TO PANEL time must be greater than the start time.
Operator response
Specify an end time that is later than the start time
and press Enter.

EZL970I NO TIMERS ARE SCHEDULED FOR Explanation
THE FILTER CRITERIA 'filter' ON You changed the specified timer.
'target'
Message Variables
Explanation timer
You attempted to view timers that are not scheduled. The ID of the timer
target
Message Variables
The domain or system ID where the timer
filter command was processed.
The filter criteria specified at the timer invocation
or on the Timer main panel. A blank insert means System action
that filter criteria was not specified.
AON changes the timer.
target
The domain or system ID where the timer EZL975I REQUEST FAILED TIMER timer
command was processed. ALREADY EXISTS ON 'target'

Ensure that the filter criteria is specified correctly. If You attempted to add the specified timer ID, but the
not, press PF3 to return to the main timer panel and timer was already set.
reenter the filter criteria. If a new timer is desired,
Message Variables
enter the appropriate information.
timer
EZL971I REQUESTED TIMERS WERE The ID of the timer
DELETED ON 'target'
target
Explanation
command was processed.
You deleted the requested timers.
target AON does not set the timer.

command was processed. Operator response
Specify another timer ID and try again.
System action
EZL976I CHANGES TO THE variable ENTRY
AON deletes the timers. ARE NOT PERMITTED WITH
EZL973I REQUESTED TIMER timer ADDED '(MORE:+)'
ON ' target'
Explanation
Explanation You attempted to modify an entry on a timer panel
You added the specified timer. input line that contained the string '(MORE:+).'
timer variable
The ID of the timer The entry field that was modified.
target
The domain or system ID where the timer Operator response
command was processed. To change the entry, remove the string '(MORE:+)' and
enter all of the entry data. If a change is not required,
System action change the data to the original text and case.
AON adds the timer. EZL977I PRESS ENTER TO SWITCH TO A
DIFFERENT TIMER TYPE
EZL974I REQUESTED TIMER timer
CHANGED ON 'target'

You attempted to set a timer from a panel interface, You must choose another option or clear other
but the TIMER TYPE entry did not match the current selections.
panel.
EZL981I OPTION option REQUIRES
ADDITIONAL PANEL SELECTIONS
Operator response
If a different timer type is required, press enter to Explanation
process that request. To set the timer using the
The option specified requires you to make additional
current panel, change the TIMER TYPE entry to match
selections on this panel.
the current entry.
Message Variables
EZL978I ITEMS sel1 AND sel2 ARE
MUTUALLY EXCLUSIVE option
The panel option that requires additional panel
Explanation selections.
sel1 and sel2 cannot be selected together.

Operator response
Message Variables
You must choose another option or make additional
sel1 selections on the panel.
The first selection that is mutually exclusive
EZL982I A DAY OF THE WEEK WAS NOT
sel2 SPECIFIED
The second selection that is mutually exclusive
Explanation
Operator response
A panel selection was made without a corresponding
Change your input to specify only one of the day selection.
selections.
EZL979I CURRENT TIME PAST REQUESTED Operator response
TIME You must select the day highlighted or clear the
additional selection for that day.
Explanation
EZL984E KEYWORD CONFLICT BETWEEN
AON attempted to set a timer type of AT for today with keywd1 AND keywd2
a time that had already passed.
Explanation
System action
This message is issued when you have attempted to
AON does not set the timer. specify two mutually exclusive keywords on a
command.
Operator response
Message Variables
Enter the correct time and try again.
keywd1
EZL980I OPTION option DOES NOT The first keyword specified.
SUPPORT ADDITIONAL PANEL keywd2
SELECTIONS The second keyword specified.

You selected an option that does not support Choose the correct keyword and reissue the
additional panel selections. command.
Message Variables EZL985I VALID VALUES ARE values
option
The panel option that does not support additional
panel selections.

Explanation EZL992I MULTIPLE SELECTIONS ARE NOT
SUPPORTED
This message displays the specified range of correct
values.
Explanation
Message Variables
You attempted to select more than one item from the
values selection list, but the list does not support multiple
The range of correct values selections. Or you attempted to obtain a selection list
using a ? for an option that does not support them.
Operator response
Correct the entry and press the appropriate key to System action
process the values. AON does not process a selection.
EZL986I req_val MUST ACCOMPANY value1
value2 Operator response
Select only one item and try again, or replace the ?
Explanation with an appropriate entry.
You selected a value on an input panel but did not EZL999I OP opid ISSUED type CMD: "cmd"
provide the other values that go with the selected
value.
Explanation
Message Variables
This message is logged for tracking purposes. It
req_val provides detailed information about the operator and
The missing and required value that goes with what command they issued.
value1 and value2
Message Variables
value1
The first value specified opid
The ID of the operator
value2
The second, optional value specified type
The type of command issued (for example, VTAM)
System action cmd
EZL1101I Remote request in progress.
Operator response
Explanation
Type the required value in the missing field and press
Enter to continue. This message is displayed when the AON
Communications Server application is processing a
EZL991I INVALID SELECTION selection request to the NetView host. The message is displayed
until a response is received or the wait time has
Explanation expired.
You requested a selection that is either incorrect or
not allowed for this type of resource. User response
Message Variables The request can be stopped by selecting the CANCEL

pushbutton on the message box.
selection
The incorrect selection. EZL1102E Confirm delete of monitor setting?

The action fails. You have selected to delete a monitor setting. This
message asks you for confirmation before the setting
Operator response is deleted.
Try again with a valid selection.

User response User response
Select YES to continue the deletion or NO to cancel it. Select YES to continue the deletion or NO to cancel it.
EZL1103E Storage error; Threshold data EZL1112E Storage error: Monit data cannot
cannot be loaded. RC = n be loaded. RC = n
The Automation Thresholds page of the Automation The Automation Monitor Settings page in the
Settings notebook encountered a storage error. You Automation Notebook encountered a storage error.
might have too many application windows open. You might have too many application windows open.
User response User response

Close the Automations Settings notebook and any Close the Automation Settings notebook and non-
other non-essential windows and restart the essential windows. Restart the Automation Settings
Automation Settings notebook. notebook.
EZL1106E Unable to create notebook control. EZL1114E Monitor interval insert failed. RC =
n
Explanation
Explanation
Presentation Manager failed to obtain the required
resources to initialize the Automation Settings A program error stopped the insertion of a Monit
notebook. You might have too many application interval in the intervals list.
windows open.
User response
User response
Retry the operation.
Close non-essential application windows and open the
Automation Settings notebook. EZL1115E Storage error; Monit change dialog
terminated. RC = n
EZL1107E Help error.
Explanation
Explanation
A program error closed the Monitor Value panel.
The Help Manager cannot be started. No online help
information is available. User response
EZL1109I Confirm delete of Critical Retry the operation.
Threshold setting?
EZL1116E Storage error; On/Off data cannot
be loaded. RC = n
Explanation
You have selected to delete a threshold setting. This Explanation
is deleted. The Automation Settings On/off page encountered a
storage error. You might have too many application
windows open.
User response
Select YES to continue the deletion or NO to cancel it. User response
EZL1111I Confirm delete of NOAUTO Close the Automation Settings notebook and non-
setting? essential application windows. Restart the Automation
Settings notebook.
Explanation
EZL1119E Window positioning failed!
You have selected to delete a NOAUTO setting. This
is deleted.

Presentation Manager resources were unavailable to The Help Manager encountered an error while trying to
open the window. start the online help facility. The requested help
cannot be displayed.
User response EZL1130E Stop Time not greater then Start
Close non-essential application windows and retry the time.
operation.
Explanation
EZL1120E An error occurred while creating a
window. RC = n The NOAUTO stop time must be greater than the start
time.
Explanation
User response
Presentation Manager resources were unavailable to
open the window. Change the setting so that the stop time is greater
than the start time.
User response EZL1131I Remote request time out
Close non-essential application windows and retry the occurred!!
operation.
Explanation
EZL1121E Error starting History
program...RC = n The Automation Settings application timed out while
waiting for a response from the AON host.
Explanation
User response
The Automation History application failed to start.
Verify the following:
User response • The AON Communications Server application is
Note the return code and report the failure to your running.
support personnel. • The AUTWKSTA automation operator is active on the
AON host.
EZL1122E Memory allocation error: RC = n
• The workstation interface application (EZLMSAPL) is
registered on the AON host.
Explanation
Retry the operation.
An application request for memory was not satisfied.
The application stopped. EZL2005E Queue create failed. RC = n
User response Explanation

Close any non-essential application windows and The DosCreateQueue function call failed.
restart the application.
EZL1127E NOAUTO insert/change request User response
failed. RC = n Restart the program. If the failure occurs again,
contact your support personnel.
Explanation
EZL2008E Queue read error
A program error closed the Set NOAUTO value panel.
Explanation
User response
An error was detected while reading data from the
Note the return code and notify your support response queue. The data was ignored.
personnel.
EZL1129E Error displaying Help. User response
Retry the operation. If the failure occurs again, contact
your support personnel.

EZL2011E Thread creation failed User response
Close any non-essential application and restart the
Explanation AON Communications Server application.
The DosCreateThread function call failed. EZL2036E Register_ms_application failed,
primary RC = n,sec RC = n
User response
Start the AON Communications Server application. If Explanation
the failure occurs again, contact your support The AON Communications Server application failed to
personnel. register with the communications manager.
EZL2014E Failed to load Help Manager
User response
Explanation Verify that the communications manager is running.
Help Manager cannot be started. No help is available. Restart the AON Communications Server application.
EZL2035E DosAllocSharedMem failed. RC = n
Explanation
The AON Communications Server application failed to
acquire enough memory. The application stopped.

Chapter 8. FKV Prefix Messages
FKV messages provide error descriptions and information about AON/SNA automation.
FKV215E command IS USED BY DATA FROM command COMMAND :
AUTOMATION, OPERATORS OR CRITICAL DUMP REPLY FROM
OTHER PROGRAMS ARE NOT RECOVERY HOST
ALLOWED TO EXECUTE IT
Explanation
Explanation The specified program cannot find the expected
An unauthorized user attempted to run the specified configuration data from the specified command
automation program but failed. because you did not specify the critical response to
the Network Control Program (NCP) DUMP/RELOAD
Message Variables command in the control file.
program
Operator response The name of the program
command
The command issued

Operator response
Verify the operator profile for unauthorized users and
perform problem determination.
FKV226E program COULD NOT FIND System programmer response
EXPECTED CONFIGURATION
DATA FROM "command" Correct or add the appropriate control file entry.
COMMAND : NON-CRITICAL DUMP FKV228E program COULD NOT FIND
REPLY FROM RECOVERY HOST EXPECTED CONFIGURATION
DATA FROM "command"
Explanation COMMAND
The specified program cannot locate the expected
configuration data from the specified command Explanation
because you did not specify the noncritical response The specified program cannot find the expected
to the Network Control Program (NCP) DUMP/RELOAD configuration data from the specified command
command in the control file. because you did not specify the critical or non-critical
Message Variables response to the Network Control Program (NCP)
DUMP/RELOAD command in the control file.
program
The name of the program Message Variables
command program
The command issued The name of the program
command
Operator response The command issued
Operator response
System programmer response Notify your system programmer.
Correct or add the appropriate control file entry.
FKV227E program COULD NOT FIND
EXPECTED CONFIGURATION Correct or add the appropriate control file entry.

FKV331I TAB TO SELECTION BOX OR FKV334I NETVIEW ACCESS SERVICES IS
PRESS F10 TO VIEW SENSE CODE NOT ACTIVE ON domain
DATA
Explanation
Explanation
You attempted to enter the option for NetView Access
You tried to view sense code data but your cursor was Services (NVAS) on the SNA Help Desk panel, but
in the wrong field. NetView Access Services is not active.
Message Variables
Operator response
domain
Press the F10 or Tab key to move the cursor to the The name of the domain where NetView Access
Sense Code Data field located in the lower right Services is not active
section of the panel.
FKV332I UNABLE TO RUN LUDRPOOL. Operator response
resname DOES NOT HAVE AN NCP Notify your system programmer to start NetView
DEFINED Access Services.

You tried to issue the LUDRPOOL command against a Start NetView Access Services.
resource that has no NCP defined.
FKV335I nvasid IS NOT LOGGED ONTO
Message Variables
NETVIEW ACCESS SERVICES,
resname nvas
Explanation
Operator response
You entered an NetView Access Services (NVAS) user
Issue the command again to a correct resource. ID and selected NetView Access Services on the SNA
Help Desk panel, but the NetView Access Services
FKV333I resname1 IS status DUE TO user ID is not logged on.
restype2 resname2. PRESS F11
FOR ERROR DETAILS Message Variables
nvasid
Explanation The NetView Access Services user ID
The first specified resource has the specified status nvas
because the second specified resource, which is a The NetView Access Services name defined at
higher node, is not active. installation
Message Variables
Operator response
resname1
The name of the resource that is being supported Notify the user that called in that the ID is not logged
by the higher resource on to NetView Access Services.
status FKV336I NO DATA RETURNED FOR
The status of the resource that is being supported NETVIEW ACCESS ID nvasid
restype2
The resource type of the higher resource Explanation
resname2 AON/SNA cannot find data for the specified NetView
The name of the higher resource Access Services (NVAS) user ID, even though the ID is
logged onto the system.
Press the F11 key to view the error information. Follow nvasid
the menu to solve the resource problem. The NetView Access Services user ID

Operator response sensecode
The sense code returned from the ACTIVATE
command

Operator response
Check the NetView Access Services user ID for any
View help for the sense code for more information.
problems and correct them. Verify that the NetView
Note the sense code and view the sense code
Access Services application is working properly.
information by selecting the View Sense Code option.
FKV337I resname IS status. PRESS F11 FOR Notify your system programmer with the sense code
ERROR DETAILS information.

You selected Problem Determination on the specified Perform problem determination using the sense code
resource, and the resource is not active. and NetView and VTAM references.
Message Variables FKV501I DUMP OF NCP resname FAILED -
error
resname
Explanation
status
The status of the resource The NCP failed to DUMP because of the specified
error.
Press the F11 key to view the error information. Take resname
the appropriate action on the resource. The name of the resource
FKV338I RESOURCE resname IS status. error
THERE ARE NO ERROR DETAILS The reason for the failure
TO DISPLAY
System action
Explanation The NCP DUMP is not completed.
You selected Problem Determination for the specified
resource and pressed F11, but the resource is normal. Operator response
The F11 key is not available when the resource is
normal. Notify your system programmer.

resname Note the reason for the DUMP failure and correct the
The name of the resource problem.
status
The status of the resource. FKV502I LOAD OF NCP resname FAILED -
reason
FKV339I UNABLE TO ACTIVATE THE
HIERARCHY FOR resname. Explanation
SENSECODE= sensecode
The NCP failed to LOAD because of the specified error.
You tried to activate the hierarchy for the specified resname
resource, but the ACTIVATE command that you issued The name of the resource
failed because of the specified sense code. reason
Message Variables The reason for the failure
resname
The name of the resource System action
The NCP LOAD is not completed.
Chapter 8. FKV Prefix Messages 461

Notify your system programmer. VTAM recovers the CDRM automatically.

Note the reason for the LOAD failure and correct the Notify the system programmer.
problem.
FKV510A LOAD OF NCP ncp STOPPED System programmer response
BECAUSE LOAD MODULE DOES Try to recover the SSCP.
NOT MATCH NEW NCP:
AUTOMATION IS OFF, REPLY 'NO' FKV512I LOAD OF NCP ncp CANCELED -
TO CANCEL OR 'YES' TO RELOAD LOAD MODULE DOES NOT MATCH
FOR REPLYID replyid NEW NCP
AON/SNA stopped loading the specified Network The load module in the Network Control Program
Control Program (NCP) because the load module does (NCP) does not match the new NCP. The NCP cannot
not match the new NCP. be loaded.
ncp ncp
The name of the NCP that stopped loading The name of the NCP
replyid
The reply number that the operator used to control System action
the NCP load AON/SNA recovery stops. The NCP is not loaded.

AON/SNA stops processing until an operator Resolve the mismatch between the load module and
intervenes. the NCP by using the ACTIVATE command. If you
cannot solve the problem, notify your system
Operator response programmer.
Solve the problem with the NCP load module. Respond
to the outstanding reply. System programmer response
Resolve the mismatch between the load module and
System programmer response the NCP by using the ACTIVATE command. Reference
the appropriate NetView and VTAM documentation.
Determine why the load module did not match the new
NCP and solve the problem. FKV513I STORAGE UNAVAILABLE FOR
ADJSSCP TABLE FOR definition
FKV511I COMMUNICATION WITH CDRM
cdrm LOST DUE TO SSCP FAILURE
- (RC = returncode): AUTOMATIC Explanation
RECOVERY IN PROGRESS AON/SNA cannot build the ADJSSCP table while
processing the specified definition because of a lack of
Explanation storage.
A System Service Control Point (SSCP) failed, so the Message Variables
specified Cross Domain Resource Manager (CDRM) definition
was lost. AON/SNA started the recovery process. The definition in the VTAM list
Message Variables
cdrm System action
The CDRM that was lost AON/SNA issues a DISPLAY BFRUSE command.
returncode
The return code X'0E' from the CDRM failure

Notify your system programmer. A VTAM request for storage from the specified subpool
cannot be satisfied.
Browse the NetView log for the results of the DISPLAY subpool
BFRUSE command. Resolve the lack of storage. The storage subpool requested
FKV514I STORAGE UNAVAILABLE FOR type
BUFFER POOL System action
AON/SNA issues a DISPLAY BFRUSE command.
Explanation
VTAM requested more storage for the specified buffer Operator response
pool, but the request cannot be satisfied. Notify your system programmer.
Message Variables
type System programmer response
The type of buffer pool requested Browse the NetView log for the results of the DISPLAY
BFRUSE command. Increase storage.
System action
AON/SNA issues a DISPLAY BFRUSE command. cdrm LOST DUE TO CLEANUP - THE
SSCP IS RESETTING (RC =
Operator response returncode)

Explanation
System programmer response AON/SNA lost communication with the specified Cross
Domain Resource Manager (CDRM) during a System
Browse the NetView log for the results of the DISPLAY Service Control Point (SSCP) reset. AON/SNA is not
BFRUSE command. Resolve the lack of storage. started.
FKV515I STORAGE UNAVAILABLE - type Message Variables
HAS BEEN REACHED
cdrm
The name of the CDRM
Explanation
returncode
A VTAM request for storage from the specified type The return code X'0F' from the CDRM failure
cannot be satisfied.
type Communication with the CDRM is lost. Automated
The type of storage unit requested recovery does not start.

AON/SNA issues a DISPLAY BFRUSE command. Wait for the SSCP to reestablish communications.
Ensure that the CDRM recovers. If the CDRM does not
Operator response recover, reactivate it. If problems persist, notify your
system programmer.
Wait for SSCP to reestablish communications. Ensure
Browse the NetView log for the results of the DISPLAY that the CDRM recovers. If the CDRM does not recover,
BFRUSE command. Resolve the lack of storage. reactivate it.
FKV516I STORAGE UNAVAILABLE FOR
SUBPOOL subpool

FKV518I restype resname DISCONNECTION Operator response
FAILED DUE TO LACK OF STORAGE Resolve the SSCP contention and reestablish
- CURRENT STATUS IS status communication with the CDRM. If problems persist,
notify your system programmer.
Explanation
AON/SNA tried to disconnect the specified resource System programmer response
but failed because of a lack of storage for VTAM. Resolve the SSCP contention and reestablish
Message Variables communication with the CDRM.
restype FKV520I COMMUNICATION WITH CDRM
The type of the resource. cdrm LOST DUE TO FORCED
resname INACTIVATE OF THE VR (RC =
The name of the resource. returncode): AUTOMATIC
RECOVERY IN PROGRESS
status
The current status of the resource.
Explanation
System action AON/SNA lost communications with the specified

Cross Domain Resource Manager (CDRM) because the
AON/SNA issues a DISPLAY BFRUSE command. The virtual route (VR) is inactive.
resource is inactive.
Message Variables
Operator response cdrm
The name of the CDRM.
Notify your system programmer if the problem
persists. returncode
The return code X'0B', which was received from
System programmer response VTAM when communication was lost.
Browse the NetView log for the results of the DISPLAY System action
BFRUSE command. Resolve the lack of storage.
AON/SNA initiates recovery of the CDRM.
cdrm LOST DUE SSCP
Operator response
CONTENTION (RC = returncode)
If the VR is not routed, resolve the VR failure.
Explanation Reactivate the CDRM. If problems persist, notify your
system programmer.
AON/SNA lost communication with the specified Cross
Domain Resource Manager (CDRM) because of
contention with a System Service Control Point (SSCP).
AON/SNA cannot recover the connection. If the VR is not routed, resolve the VR failure.
Reactivate the CDRM.
Message Variables
cdrm FKV521I COMMUNICATION WITH CDRM
The name of the CDRM with which communication cdrm LOST DUE TO VR INOP (RC =
was lost returncode); AUTOMATIC
RECOVERY IN PROGRESS
returncode
The return code X'10' that was received from
VTAM when communication was lost. Explanation
AON/SNA issued an INACTIVATE command that
System action disrupted the session with the specified Cross Domain
Resource Manager (CDRM).
Communication with the CDRM is lost. Automated
recovery does not start. Message Variables
cdrm

returncode switch occurs when a backup line is deactivated and
The return code X'07' then reactivated.
Message Variables
System action
restype
AON/SNA stops the session with the CDRM without The type of resource
disrupting other active LU-U sessions. AON/SNA starts
resname
recovery on the CDRM.
Operator response line

The backup line
Notify your system programmer. Issue a VARY ACT
command for the CDRM to reestablish the session. System action
System programmer response AON/SNA resumes processing.
Solve the problem with VR INOP. FKV524I SESSION LOST BETWEEN resname
AND application IN SA sa DUE TO
FKV522I COMMUNICATION WITH CDRM VR INOP RECEIVED
cdrm LOST DUE TO SSCP -
FAILURE (RC = returncode): Explanation
AUTOMATIC RECOVERY IN
PROGRESS The session between the specified resource and the
specified subarea of the specified application was lost
Explanation because the virtual route (VR) between the resource
and application was inoperative.
A System Service Control Point (SSCP) failure
disrupted the session with the specified Cross Domain Message Variables
Resource Manager (CDRM). resname
Message Variables The name of the resource
application
cdrm
The name of the application
sa
returncode
The subarea number
The return code X'0C'
Operator response
System action
If you have been instructed to provide backup for the
AON/SNA stops the session with the CDRM without
application, perform the necessary operations. If
disrupting other active LU-U sessions. AON/SNA
problems persist, notify your system programmer.
initiates recovery of the CDRM.

Operator response
Resolve the routing problem. Recover the connection
Notify your system programmer. Issue a VARY ACT
between the resource and the application.
command to reestablish a session with the CDRM.
System programmer response cdrm LOST DUE TO SESSION
OVERRIDE - ACTIVATE ALREADY
Resolve the SSCP failure. IN PROGRESS (RC = returncode)
FKV523I TG SWITCH HAS TAKEN PLACE
FOR restype resname (line WAS Explanation
RECYCLED)
The session setup for the specified Cross Domain
Resource Manager (CDRM) failed. AON/SNA lost
Explanation communications with the CDRM.
AON/SNA switched transmission groups (TGs) to Message Variables
ensure that the lines in the TG are in order when the
primary line or PHYSICAL_UNIT is activated. A TG

cdrm Explanation
AON/SNA cannot deactivate the specified resource
returncode because the VARY command has failed with the sense
The return code X'0D' code displayed. The node is not available to VTAM.
Message Variables
System action
resname
Communication to the CDRM is lost. The name of the resource
sensecode
Operator response
The sense code
System action
AON/SNA waits to inactivate the resource with the
Resolve the problem with the session setup for the VARY command.
CDRM.
FKV526I restype resname IS IN AN INVALID Operator response
STATE: CURRENT STATUS IS Issue a VARY INACT,F command to deactivate the
status node. If the problem persists, notify your system
programmer. Provide the problem determination
Explanation information.
An unrecoverable or forced error occurred on the
node. AON/SNA cannot act on the specified resource. System programmer response
Message Variables Using the sense code provided, resolve the

deactivation problem for the resource, and inactivate
restype the resource.
FKV528I DISCONNECT OF resname FAILED
resname
DUE TO I/O ERROR OR
INSUFFICIENT STORAGE
status
The current status of the resource Explanation
AON/SNA tried to end a session on the specified
System action
resource but the request failed because of an I/O error
AON/SNA issues a VARY INACT command for the node or insufficient storage.
automatically. No other automation is started.
Message Variables

None, if you want the resource to remain inactive. If
the message appears to be the result of a hardware
System action
error, follow the problem determination procedure and
notify your system programmer. AON/SNA resumes processing.

Put the resource in an active or inactive state. Resolve Issue a VARY INACT,I command for the resource so
why the resource stayed in an unrecoverable state. that the system can release the resources allocated to
it. Notify your system programmer. Provide the system
FKV527I DEACTIVATION OF resname
programmer with output from the problem
CANNOT BE COMPLETED
determination action that you received after issuing
BECAUSE VARY HAS FAILED WITH
the DISPLAY BFRUSE command.
SENSE: sensecode

Resolve the I/O error or storage shortage. Inactivate The NCP load continues.
the resource.
FKV529I ACTIVATION OF minornode Operator response
FAILED DUE TO INACTIVE HIGHER Notify your system programmer.
NODE - highernode, ACTIVATION
OF highernode ATTEMPTED System programmer response
Explanation Browse the syslog for appropriate I/O error messages

and verify the job control statements of the load utility
AON/SNA cannot activate the specified minor node program.
because its higher-level node is inactive. To activate
the minor node, the higher node must be active. FKV531I COMMUNICATION WITH CDRM
cdrm LOST DUE TO GATEWAY
Message Variables NODE CLEANUP ( RC = returncode)
minornode
The lower node of the resource Explanation
highernode You lost communications with the specified Cross
The higher node of the resource Domain Resource Manager (CDRM) because of a
Gateway node cleanup.
VTAM rejects the VARY command and AON/SNA tries cdrm
to activate the higher node. The minor node is The name of the CDRM
recovered as part of the higher node recovery.
returncode
The return code X'11'
Operator response
Watch for associated messages to verify that the System action
attempt to activate succeeds.
AON/SNA stops communication with the CDRM and
does not attempt to recover it.
If recovery of the higher node fails, resolve the failure Operator response
and activate the higher node with SCOPE=U.
Wait for the Gateway to activate and reactivate the
FKV530I BYPASS THE INITIAL TEST CDRM and notify your system programmer.
ROUTINE FOR resname, REPLY OF
-U- BYPASS WAS ISSUED System programmer response
Explanation Resolve the Gateway node failure and reactivate the

CDRM.
While processing a VARY ACT command or an error
recovery, VTAM attempted to load the communication FKV532I REPLY OF -reply- WAS ISSUED BY
controller. However, the initial test routine of the load AUTOMATION FOR resname FROM
utility program cannot be used because of a origin: NON-CRITICAL DUMP
permanent I/O error or because of erroneous or REPLY FROM RECOVERY HOST
missing job control statements. AON/SNA issued a
reply of U to the initial test routine, causing the system Explanation
to bypass the routine and to initiate the Network
The communication controller associated with the
Control Program (NCP) without testing the hardware.
specified Network Control Program (NCP) failed.
Message Variables AON/SNA issued the specified reply to the Option to
dump NCP prompt. The NCP critical threshold for
resname
failures are not exceeded.
Message Variables

reply FKV534I REPLY OF -reply- WAS ISSUED BY
The reply issued to the Option to dump NCP AUTOMATION FOR ncp FROM
prompt. This reply is read from the NCPRECOV origin: STANDARD DUMP REPLY
statement for the NCP in the control file. FROM NON-RECOVERY HOST
resname
The name of the resource Explanation
origin The communication controller associated with the
The origin of the message specified Network Control Program (NCP) failed.
AON/SNA issued the specified reply to the Option to
System action dump NCP prompt. Channel-attached, non-recovery
hosts always issue a reply of NO, so that only one AON
The NCP dumps into an allocated dump data set. host performs a recovery.
Notify your system programmer. reply

The reply issued to the Option to dump NCP
prompt. This reply is read from the NCPRECOV
System programmer response statement for the NCP in the control file.
Investigate why the NCP failed to prevent a future ncp
failure. The name of the NCP.
FKV533I REPLY OF -reply- WAS ISSUED BY origin
AUTOMATION FOR ncp FROM The origin of the message.
origin: CRITICAL DUMP REPLY
FROM RECOVERY HOST System action
The NCP performs a dump into an allocated dump data
Explanation
set.
specified Network Control Program (NCP) failed. Operator response
dump NCP prompt. The number of NCP failures has Notify your system programmer.
reached the critical threshold.
Message Variables
Investigate the NCP failure to prevent a future
reply
occurrence.
The reply issued to the Option to dump NCP
prompt. This reply is read from the NCPRECOV FKV535I REPLY OF -reply- WAS ISSUED BY
statement for the NCP in the control file. AUTOMATION FOR ncp FROM
ncp origin: NON-CRITICAL RELOAD
The name of the NCP. REPLY FROM RECOVERY HOST
origin
The origin of the message. Explanation
System action specified Network Control Program (NCP) failed.
AON/SNA issued the specified reply after receiving the
The NCP performs a dump into an allocated dump data
Option to load NCP prompt. The threshold for a critical
set.
failure threshold has not been reached.
Notify your system programmer. reply

The reply issued to the prompt Option to load NCP.
This reply is retrieved for the NCPRECOV control
file statement.
Investigate the cause of the NCP failure to prevent a ncp
future failure. The name of the NCP

origin System action
The origin of the message
AON/SNA starts loading the NCP.
System action FKV538I REPLY OF -reply- WAS ISSUED BY

AUTOMATION FOR ncp FROM
AON/SNA starts loading the NCP. origin: CRITICAL RELOAD REPLY
FKV536I REPLY OF -reply- WAS ISSUED BY FROM NON-RECOVERY HOST
origin: CRITICAL RELOAD REPLY Explanation
FROM RECOVERY HOST
specified Network Control Program (NCP) failed.
Explanation AON/SNA issued the specified reply to the Option to
The communication controller associated with the dump NCP prompt. The critical threshold for NCP
specified Network Control Program (NCP) failed. failures has been reached.
AON/SNA issued the specified reply to the Option to Message Variables
dump NCP prompt. The critical threshold for NCP
failures has been reached. reply
The reply issued to the Option to load NCP prompt.
Message Variables This reply is retrieved for the NCPRECOV control
reply file statement.
The reply issued to the Option to load NCP prompt. ncp
This reply is retrieved for the NCPRECOV control The name of the NCP.
file statement. origin
ncp The origin of the message.
The name of the NCP.
origin System action
The origin of the message.
AON/SNA starts loading the NCP.
System action FKV539I SESSION LOST BETWEEN resname

AND sscp IN SA sa DUE TO A
AON/SNA starts loading the NCP. FORCED DEACTIVATION OF THE
FKV537I REPLY OF -reply- WAS ISSUED BY SSCP-PU SESSION
origin: NON-CRITICAL RELOAD Explanation
REPLY FROM NON-RECOVERY
AON/SNA lost the session between the specified
HOST
resource and the specified System Service Control
Point (SSCP) in the specified subarea of the
Explanation application. AON/SNA does not initiate recovery of the
The communication controller associated with the session.
specified Network Control Program (NCP) failed. Message Variables
dump NCP prompt. The critical limit for NCP failures resname
has not been exceeded. The name of the resource
sscp
Message Variables
The application with which the resource was in
reply session
The reply issued to the Option to load NCP prompt. sa
This reply is retrieved for the NCPRECOV control The subarea of the SSCP
file statement.
ncp System action
AON/SNA does not start recovery.
origin
The origin of the message.

Notify your system programmer. If the status is QUEUED, AON/SNA queues the
activation of the CDRM, pending the availability of a
System programmer response suitable gateway NCP. If the status is FAILED, the
activation of the CDRM failed, because of an
Determine why the session between the SSCP and the unexpected error (such as a storage shortage),
physical unit ended and solve the problem. because all paths have been tried and failed, or
FKV540I OUTSTANDING REPLY: replyid - because VTAM has not defined a suitable Gateway
replyid msgnum OPTION TO action NCP that can become fully active in the future.
ncp AVAILABLE - REPLY 'YES' OR
'NO' OR Operator response
'YES,station=LINKSTANAME' Notify your system programmer. To stop the CDRM
from activating, issue a VARY INACT command.
Explanation
AON/SNA automation does not respond to the System programmer response
specified reply. Resolve the path problem and reactivate the CDRM.
Message Variables
FKV542I NCP resname REQUIRES A
replyid MANUAL ACTIVATION
The outstanding reply.
msgnum Explanation
The message number to which to reply.
You must activate the specified Network Control
action Program (NCP) manually because AON/SNA is off or
The action taken. The actions are DUMP or because there is no entry for the NCP in the control
RELOAD. file. The nodes associated with this communication
ncp controller are inaccessible.
The name of the NCP. Message Variables
station
resname
The station type to use for DUMP or RELOAD. The
The name of the NCP
type is DUMPSTA or LOADSTA.
System action
Operator response
AON/SNA resumes processing.
Reply to the outstanding reply.
FKV541I ACTIVATION status FOR CDRM Operator response
cdrm, GATEWAY PATH NOT
Complete the following steps:
AVAILABLE
1. Issue a VARY ACT command for the NCP.
Explanation 2. Verify the automation status of the NCP.
AON/SNA cannot select a gateway Network Control 3. Verify that there is an entry for the NCP in the
Program (NCP) to support a session between two control file.
System Services Control Programs (SSCPs) with the
specified Cross Domain Resource Manager (CDRM). System programmer response
Message Variables To recover the NCP automatically, enter the
status supporting controls into the control file.
The activation status. The status is FAILED or FKV543I SESSION LOST BETWEEN resname
QUEUED. AND application IN SA sa DUE TO
cdrm A DEACTIVATION OF THE
The name of the CDRM. VIRTUAL ROUTE

AON/SNA lost the session between the specified ncp
Network Control Program (NCP) and the specified The name of the NCP
System Service Control Point (SSCP) in the specified sscp
subarea. The session was lost because the virtual The name of the SSCP
route (VR) was deactivated. AON/SNA is enabled for
both the controller and the SSCP. sa
The subarea number of the SSCP
Message Variables
resname Operator response
The name of the NCP If you have been instructed to provide backup for the
application SSCP, perform the necessary operations for backing up
The name of the SSCP the SSCP. If problems persist, notify your system
sa programmer.
The subarea number of the application
System action Resolve the SSCP failure.
AON/SNA stops the traffic between the resource and FKV546I TIME USED TO RELOAD restype
the SSCP. resname HAS EXCEEDED number
MINUTES
Operator response
Notify your system programmer. Explanation
AON/SNA started loading the specified Network
System programmer response Control Program (NCP) but did not finish within the
Resolve the VR problem. specified number of minutes. The number of minutes
is defined in the LOADTIME parameter of the
FKV544I RELOAD WAS SUCCESSFUL FOR NCPRECOV statement in the control file for the NCP.
resname AND IS AVAILABLE
Message Variables
Explanation restype
The type of resource (NCP)
AON/SNA successfully loaded the communication
resname
controller with the Network Control Program (NCP) in
The name of the resource (NCP)
response to a VARY ACT command or to an NCP reload
after an error recovery procedure. The communication number
controller is ready for use. The number of minutes AON/SNA has to load the
NCP
Message Variables
resname System action
The name of the NCP
AON/SNA resumes loading the NCP.
System action
Operator response
Determine why the loading time exceeds the allotted
FKV545I SESSION LOST BETWEEN ncp AND time or why loading failed. Notify your system
sscp IN SA sa DUE TO AN SSCP programmer.
FAILURE
Explanation
Check routes, links, and link capacity for any
AON/SNA lost the session between the specified resolvable bottlenecks for the flow of a large load
Network Control Program (NCP) and the specified module and clear them.
System Service Control Point (SSCP) in the specified
subarea because the SSCP failed. AON/SNA is enabled
for both the controller and the SSCP.

FKV547I TIME USED TO DUMP restype TERMINATED, ncp IS UNKNOWN
resname HAS EXCEEDED number TO VTAM
MINUTES
Explanation
Explanation AON/SNA exceeded the DUMP threshold for the
AON/SNA started to dump the specified Network specified Network Control Program (NCP), but the NCP
Control Program (NCP), but the dump did not complete is inactive and unknown to VTAM. An operator might
within the specified number of minutes. The number of have intervened during the dumping process.
minutes is defined in the DUMPTIME parameter of the Message Variables
NCPRECOV statement in the control file for the NCP.
ncptype
Message Variables The type of NCP
restype ncp
The resource type of NCP The name of the NCP
resname
The name of the NCP System action
number AON/SNA stops trying to recover the NCP and resumes
The number of minutes allotted for AON/SNA to processing.
dump the NCP
Operator response
System action
Recover the NCP manually.
AON/SNA resumes the dumping process.
Operator response
Check routes, links, and link capacity for resolvable
Determine why the dumping time exceeds the allotted bottlenecks to the flow of a large dump and resolve
time or why dumping failed and solve the problem. If them.
problems persist, notify your system programmer.
FKV550I DUMP OF NCP ncp FAILED -
System programmer response PERMANENT I/O ERROR ON NCP
OR DUMP DATASET
Check routes, links, and link capacity for resolvable
bottlenecks for the flow of a large dump and resolve
Explanation
them.
AON/SNA cannot dump the specified Network Control
FKV548I linkstation HAS CONTACTED NCP Program (NCP) because of its inability to access the
ncp - ncp IS AVAILABLE dump data set.
Message Variables
Explanation
ncp
The specified link station contacted the Network
Control Program (NCP). The NCP is accessible from the
host.
System action
Message Variables
AON/SNA stops automatic recovery.
linkstation
The name of the NCP link station.
Operator response
ncp
The name of the NCP Notify your system programmer.
AON/SNA resumes processing. Resolve dump failure by recovering the NCP manually.
FKV549I DUMP TIMER FOR ncptype ncp FKV551I REPLY FOR BYPASS INITIAL TEST
EXPIRED, DUMP AUTOMATION FOR NCP ncp NOT ISSUED;
AUTOMATION FOR ncp IS OFF:

REPLY 'U' TO BYPASS OR CANCEL Operator response
FOR REPLY ID replyid
Start the application if the application must be
running. If problems persist, notify your system
Explanation programmer.
No NCPRECOV statement exists for the Network
Control Program (NCP), so AON/SNA cannot respond System programmer response
automatically. The initial test failed.
Start the application if the application must be
Message Variables running. If you cannot start the application, determine
why, correct the problem, and start the application
ncp
again by issuing the START command.
replyid FKV554I DUMP OF NCP ncp FAILED - DUMP
The reply ID. DATASET dataset CANNOT BE
OPENED
Operator response
Explanation
Type u to continue loading or cancel to stop loading.
The dump for the specified Network Control Program
FKV552I APPLICATION application HAS (NCP) failed because AON/SNA cannot open the
BEEN TERMINATED BY VTAM specified data set.
Message Variables
Explanation
ncp
VTAM ended the specified application. The name of the NCP
Message Variables dataset
application The name of the data set that cannot be opened
System action
System action AON/SNA stops automatic recovery.
Operator response
Operator response Notify your system programmer.
Issue the DISPLAY NET command on the application
to view its status. Issue the VARY ACT command to System programmer response
change its status.
Resolve the dump data set problem by manually
FKV553I APPLICATION application HAS dumping and recovering the NCP.
BEEN status FOR interval
FKV555I LINK STATION linkstation HAS
LOST CONTACT WITH restype
Explanation resname - resname MAY NOT BE
The specified application has the specified status and AVAILABLE
has had this status for the specified interval.
Explanation
Message Variables
The link station lost contact with a Network Control
application
Program (NCP) that has options for NCPRECOV
recovery defined in the control file. If the link station is
status the only path to the NCP, the NCP might not be
The status of the application available from the host.
interval Message Variables
The time allotted to the application in the specified
status linkstation
The link station address of the NCP
restype

The name of the NCP
None, if the resource is not valid for this network.
Otherwise, resolve the resource failure manually. If
System action problems persist, notify your system programmer.
AON/SNA tries to recover the NCP if VTAM issues a
WTORS message for a dump and reload. System programmer response
None, if the resource is not valid for this network.
Operator response Otherwise, resolve the resource failure manually.
Check the availability of the NCP. Watch for more FKV558I DUMP OF ncp status
messages on the status of the NCP. Notify your system
programmer.
Explanation
System programmer response AON/SNA dumped or started dumping the specified

Network Control Program (NCP).
Resolve the link station failure.
Message Variables
FKV556I LOAD OF ncp BY OPERATOR
STARTED ncp
Explanation status
The status of the dump. The status is COMPLETE
You started loading the specified Network Control or PARTIALLY COMPLETE.
Program (NCP) by using the VARY command.
ncp If the status is COMPLETE, you can format and print
The name of the NCP the entire dump formatted by using the utility
program.
System action
FKV559I DUMP OF restype resname FAILED
AON/SNA resumes loading the NCP. - DUMP DATASET ON AN
UNSUPPORTED DEVICE TYPE
FKV557I RECOVERY TERMINATED FOR
restype resname, VTAM
Explanation
DEFINITION NOT FOUND
The dump of the Network Control Program (NCP)
Explanation cannot be stored into the dump data set because it is
located on an unsupported device.
AON/SNA tried to recover the specified resource on
the MONIT intervals defined in the control file. Since Message Variables
the last recovery attempt, the resource has become restype
unknown to VTAM. Potentially, the major node The type of NCP
containing the resource definition is inactive.
resname
Message Variables The name of the NCP
restype
The type of resource. System action
resname AON/SNA stops recovery of the NCP.
Operator response
System action
AON/SNA stops trying to recover the resource.
Resolve the data set problem. Manually dump and
reload the NCP.

FKV560I LOAD OF NCP ncp FAILED - System action
RECEIVED text The X25MONIT command fails.
Explanation
AON/SNA stopped loading the specified Network If X25MONIT is valid for this region, initialize the
Control Program (NCP) because of an error explained
environment by running X25INIT.
in the specified message text.
FKV564I DEFINITIONS FOR resname
Message Variables
ALREADY EXISTS
ncp
The name of the NCP Explanation
text The specified resource name is already in use for an
The text of the message explaining the NCP load existing link under monitoring. The resource name
failure must be unique.
AON/SNA stops for the NCP. resname

The name of the installation-unique resource that
defines the link.
Operator response
Notify your system programmer. Operator response
Correct the resource name in the resource name field.
Load and activate the NCP manually. System programmer response
FKV561I resname X25MCH DEFINITION If the name being entered is unique, contact the
HAS BEEN BYPASSED support center.
FKV566I ERRORS HAVE OCCURRED,
Explanation
PLEASE CORRECT HIGHLIGHTED
While AON/SNA was processing configuration files in FIELD(S)
X25INIT startup for X25MONIT, it encountered errors
in the parameters of the specified resource. This Explanation
message follows message EZL203I, which identifies
the incorrect parameter. During ADD or CHANGE processing, you entered one or
more fields with values that are not valid.
Message Variables
The name of the installation-specific resource that Correct the values in the highlighted fields and press
defines the link in the configuration file. Enter.

AON/SNA resumes processing with the next link If the values are correct, and if the problem persists,
definition. contact the support center.
System programmer response FKV567I RESTARTCAUSE BYTE = vcbrec1,

DIAG BYTE = vcbrec2 RECEIVED
Correct the parameter in error and run X25INIT again. FOR FOLLOWING RESOURCE
FKV563I X25MONIT ENVIRONMENT HAS hierarchy
NOT BEEN INITIALIZED
Explanation
Explanation A BNJ146I message was received supplying the
The user issued the X25MONIT command on a region restart and diagnostic bytes for the hierarchy in the
where X25INIT is not running. message.

vcbrec1 A BNJ146I message was received supplying the
The X.25 VCBREC1 byte for RESTART, CLEAR, and restart and diagnostic bytes for the hierarchy in the
RESET causes message.
vcbrec2 Message Variables
The X.25 VCBREC2 byte for DIAGNOSTIC codes
vcbrec1
hierarchy The X.25 VCBREC1 byte for RESTART, CLEAR, and
The hierarchy for which the BNJ146I message was RESET causes
issued
vcbrec2
The X.25 VCBREC2 byte for DIAGNOSTIC codes
System action
hierarchy
Processing continues. The hierarchy for which the BNJ146I message was
issued
Operator response
Use the codes in the message and see the NPSI System action
Diagnosis, Customization, and Tuning Guide for more Processing continues.
information.
FKV568I RESETCAUSE BYTE = vcbrec1, Operator response
DIAG BYTE = vcbrec2 RECEIVED Use the codes in the message and see the NPSI
FOR FOLLOWING RESOURCE Diagnosis, Customization, and Tuning Guide for more
hierarchy information.
Explanation FKV571I restype resname IS status AT THE

reslevel LEVEL
A BNJ146I message was received supplying the
restart and diagnostic bytes for the hierarchy in the
Explanation
message.
AON/SNA reported the specified status for the line,
Message Variables
PHYSICAL_UNIT, or LOGICAL_UNIT for the link.
vcbrec1
Message Variables
The X.25 VCBREC1 byte for RESTART, CLEAR, and
RESET causes restype
vcbrec2 The resource type.
The X.25 VCBREC2 byte for DIAGNOSTIC codes resname
hierarchy The name of the resource.
The hierarchy for which the BNJ146I message was status
issued The status of the resource received from VTAM.
reslevel
System action The highest level that an inactive status was found.
The possibilities are line, PU, and LU.
System action
Operator response
AON/SNA notifies the Dynamic Display Facility (DDF).
Use the codes in the message and see the NPSI
Diagnosis, Customization, and Tuning Guide for more
information. Operator response
FKV569I CLEARCAUSE BYTE = vcbrec1, Solve the problem that is causing VTAM to report the
DIAG BYTE = vcbrec2 RECEIVED inactive status.
FOR FOLLOWING RESOURCE FKV572I SVC THRESHOLD EXCEEDED FOR
hierarchy restype resname, FREE SVCS IS
number, THRESHOLD IS threshval

AON/SNA tripped the threshold value defined for the If the definition from the control file is incorrect,
specified resource. The specified number of free correct the control file entry.
switched virtual circuit (SVC) is less than the specified
FKV574I count FREE SVCS FOR restype
threshold value defined for the resource.
resname IS WITHIN THRESHOLD
Message Variables LIMIT OF threshval
restype
The type of resource Explanation
resname AON/SNA notified the Dynamic Display Facility (DDF)
The name of the resource that any exceeded condition for the specified resource
number is resolved.
The number of available switched virtual circuits Message Variables
(SVCs)
restype
threshval The type of resource
The threshold value for the number of free
switched virtual circuits (SVCs) resname
System action count
The number of switched virtual circuit (SVC)
AON/SNA notifies the Dynamic Display Facility (DDF). available
theshval
Operator response The threshold value for the number of free switch
Notify your system programmer. virtual circuits (SVCs)
FKV651I LUDRPOOL FOR NCP ncp = count
Adjust the threshold value or define additional circuits Explanation
as appropriate.
The specified count is the number of available
FKV573I restype resname HAS BEEN dynamic reconfiguration logical units (LUs) for the
DEFINED TO X25MONIT BUT IS specified Network Control Program (NCP).
UNKNOWN TO VTAM Message Variables
ncp
Explanation
The name of the NCP
The specified resource is defined in the control file as count
a X25MONIT entry or through the dynamic add facility, The number of available dynamic reconfiguration
but a VTAM Display command cannot find it. LUs
Message Variables
FKV653I LUDRPOOL FOR NCP ncp = count :
restype THRESHOLD = threshval
resname Explanation
The specified number of available dynamic
reconfiguration logical units (LUs) for the specified
System action Network Control Program (NCP) is less than the
AON/SNA marks the resource as unknown. specified threshold value set for the LUDRSTAT
parameter.
If the definitions for the link are correct, activate the ncp
link in VTAM. If the definitions for the link are The name of the NCP
incorrect, correct the link definition.

count cpname
The number of available dynamic reconfiguration The Control Point (CP) name
LUs for the specified NCP
threshval Operator response
The threshold value defined for the LUDRSTAT None
parameter
FKV659I THIS NCP RELEASE IS NOT
System action SUPPORTED
AON/SNA notifies the Dynamic Display Facility (DDF)

Explanation
about the condition.
The LUDRPOOL command cannot support downlevel
Operator response Network Control Program (NCP) software.

Operator response
System programmer response If you want a higher level of NCP software, notify your
system programmer.
Adjust the threshold or define additional LUs as
appropriate.
FKV654I RESOURCE ncp IS UNKNOWN BY Upgrade the NCP software to the current level.
VTAM: CHECK NCP NAME
FKV801I command COMMAND IS NOT
Explanation VALID FOR REMOTE RESOURCES
VTAM does not recognize the specified Network

Explanation
Control Program (NCP).
You attempted to issue the specified command to a
Message Variables
remote resource, but the resource does not support
ncp the command.
The name of the NCP
Message Variables

The command issued
Verify the spelling of the name of the NCP and enter
the name again. FKV802I restype resname ON domain WAS
RESOLVED BY SNA HELP DESK
FKV655I NO DIRECTORY INFORMATION
RELATED TO RESOURCE cpname
Explanation
IS AVAILABLE
The SNA Help Desk resolved the problem with the
Explanation specified resource.
The SNA Automation: APPN Directory AON panel Message Variables

FKVKA300 cannot be displayed. The directory resname
database contains no information for resources served The name of the resource
or owned by the cpname resource.
restype
APPN and subarea resources are dynamically added to The type of resource
and deleted from the directory database by VTAM. You domain
might notice that sometimes the SNA Automation: The name of the domain
APPN Directory panel can be displayed (when
resources related to the cpname have been added to FKV803I restype resname ON domain WAS
the database) and sometime it can't be displayed UNABLE TO BE RESOLVED BY SNA
(when resources related to the cpname have been HELP DESK
removed from the database). This is normal, and is
because of VTAM dynamically updating the directory
database.
Message Variables

Explanation FKV806I restype resname ON domain IS
ACTIVE BUT IN CONNECTABLE
The SNA Help Desk cannot resolve the problem with
STATUS
the specified resource.
resname The specified resource is active and ready for
The name of the resource connection.
restype
Message Variables
domain resname
The name of the domain The name of the resource
restype
Operator response The type of resource
domain
Notify your system programmer about the status of
The name of the domain
the resource and explain how you attempted to
resolve the problem.
Operator response
System programmer response If you cannot activate the resource, notify your system
Note the status of the resource and try to resolve the programmer.
problem by using the appropriate VTAM reference
guides. System programmer response
FKV804I restype resname ON domain WAS If the resource is an application, issue the OPEN
VARY INACT FORCED; THEN command for it. If the resource is channel-attached,
ACTIVATED BY SNA HELP DESK power on the resource.
FKV807I restype resname ON domain IS A
Explanation VALID LU AND SNA HELP DESK
You used the VARY INACT command to deactivate the HAS STARTED PROCESSING
specified resource. The SNA Help Desk reactivated the
resource. Explanation
Message Variables The SNA Help Desk has started processing the
specified resource.
resname
The name of the resource Message Variables
restype resname
The type of resource The name of the resource
domain restype
The name of the domain The type of resource
FKV805I restype resname ON domain IS domain
ALREADY ACTIVE The name of the domain
FKV808I UNSUPPORTED VTAM FUNCTION.
Explanation
You attempted to activate the specified resource, but Explanation
the resource was already active. You attempted to issue an AON/SNA function that
Message Variables requires a level of VTAM that you are not running on
your system.
resname
The name of the resource FKV811I PORT port ADDED TO POOL pool
restype
The type of resource Explanation
domain You added the specified port to the specified pool in
The name of the domain the control file.

Message Variables FKV815I PU pu DELETED FROM CONTROL
FILE
port
The SNBU port
Explanation
pool
The SNBU pool You deleted the specified PHYSICAL_UNIT from the
control file.
AON/SNA resumes processing. pu
FKV812I PORT port DELETED FROM POOL The name of the PU (control unit)
pool
System action
Explanation AON/SNA resumes processing.
You deleted the specified port from the specified pool FKV816I DELETE STATUS REQUEST FOR PU
in the control file. pu CANCELED BY OPERATOR
Message Variables
Explanation
port
The SNBU port You attempted to delete a status request for the
pool specified PHYSICAL_UNIT but canceled the delete
The SNBU pool request.
Message Variables
System action pu
AON/SNA resumes processing. The name of the PU (control unit).
FKV813I PU pu ADDED TO CONTROL FILE

System action
You added the specified PHYSICAL_UNIT to the FKV817I DELETE STATUS REQUEST FOR PU
control file. pu COMPLETED
Message Variables
Explanation
pu
The name of the PU (control unit) You deleted a status request for the specified
PHYSICAL_UNIT.
AON/SNA resumes processing. pu
The name of the PU (control unit)
FKV814I PU pu REPLACED IN CONTROL
FILE
System action
You replaced the specified PHYSICAL_UNIT in the FKV818I DETERMINING LINE NAME FOR PU
control file. pu
Message Variables
Explanation
pu
The name of the PU (control unit) The program that is currently active is trying to
determine the appropriate line for the Switched
Network Backup Automation PHYSICAL_UNIT.
System action
Message Variables

pu FKV821I pu HAS BEEN MOVED TO
The name of the PU (control unit) SWITCHED NETWORK BACKUP

AON/SNA resumes processing. AON/SNA established Switched Network Backup
Automation for the specified PHYSICAL_UNIT. The PU
FKV819I ERROR DETERMINING LINE NAME
is back in service over one or more dialed lines.
FOR PU pu
Message Variables
Explanation pu
AON/SNA encountered an error while trying to find the The name of the PU (control unit)
line to which the PHYSICAL_UNIT is attached. You
issued a VTAM D NET command, but VTAM does not System action
know where the PU is located.
Message Variables
pu Operator response
The name of the PU (control unit) Determine why the switch occurred and correct the
problem. Use the CHGSNBU command to restore the
System action PU to leased line operation. If the modem is an IBM
786x model 4y modem, it switches back automatically
AON/SNA processing stops.
when the leased line is available.
FKV820I pu CANNOT BE MOVED TO SNBU -
FKV831I pu HAS BEEN RESTORED FROM
NUMBER TO DIAL MISSING.
SNBU TO LEASED LINE
CHECK CONTROL FILE ENTRY.
Explanation
Explanation
You moved the specified PHYSICAL_UNIT from
You attempted to switch the specified
Switched Network Backup Automation to normal
PHYSICAL_UNIT from leased line operation to
leased line operation. You switched the operation
Switched Network Backup Automation, but the
when you issued the CHGSNBU command or AON/SNA
attempt failed because no dial numbers are specified
switched the operation because it received a BNJ017I
in the control file for the PHYSICAL_UNIT.
message.
Message Variables
Message Variables
pu
pu
The name of the PU (control unit)
The remote PU (control unit)
System action
System action
AON/SNA resumes processing but the PU remains in
leased line operation. It probably remains in
inoperative or pending status. FKV834I SNBU ENTRIES NOT DEFINED OR
NOT ACCESSIBLE
Operator response
Determine the number to dial for the remote modem Explanation
attached to the PU, and add it to the control file You cannot access the Switched Network Backup
dynamically by using the SETSNBU command. Use the Automation control file entries. Either the control file is
CHGSNBU command to initiate SNBU manually. Later, not loaded, no SNBU entries were found, or the routine
add the numbers permanently by using the system wait timed out.
editor. Notify your system programmer for help.
System action
SNBU processing stops.
Update the control file with the necessary telephone
numbers.

Operator response FKV839I MOVE OF PU pu FROM line1 TO
line2 COMPLETE
Ensure that the control file is loaded. If the control file
is loaded, check that the SNBU entries in it are
defined. If the entries are defined, issue the command Explanation
again. If the problem persists, contact your system You issued a VTAM MOVE command for the specified
programmer. PHYSICAL_UNIT.
FKV835I ERROR MOVING PU pu , LINE = Message Variables
line
pu
The remote PU (control unit)
Explanation
line1
You attempted to move the specified PHYSICAL_UNIT The source line.
to the specified line, but the attempt failed.
line2
Message Variables The target line.
pu If an error occurs during the move, you see message
The remote PU (control unit) FKV382I.
line FKV843I ACTIVATE FOR PORT port
The target line STARTING

AON/SNA stops processing the move. You issued a VTAM VARY NET ACT command for the
specified port.
Operator response
Message Variables
Check the NetView log for additional VTAM messages
and correct the condition before trying another move. port
The SNBU port
FKV836I STATUS FILE DOES NOT CONTAIN
ANY SNBU RESOURCES Operator response
If the VTAM VARY NET ACT command failed, browse
Explanation
the NetView log for related messages.
You attempted to query the status file for Switched
FKV844I ACTIVATE FOR PORT port
Network Backup Automation resources but failed
because there are no SNBU resources in the status COMPLETE
file.
Explanation
FKV838I MOVE OF PU pu FROM line1 TO
line2 STARTING You issued a VTAM VARY NET ACT command for the
specified port.
You issued a VTAM MOVE command for the specified port
PHYSICAL_UNIT. The SNBU port
Message Variables
Operator response
pu
The remote PU (control unit) If the VTAM VARY NET ACT command failed, browse
line1
The source line FKV845I ACTIVATE FOR PORT port FAILED
line2
The target line Explanation
If an error occurs during the move, message FKV382I You issued a VTAM VARY NET ACT command for the
is displayed. specified port.
Message Variables

port that AON/SNA is starting to move the PU, or FKV819I,
The SNBU port which states that an error occurred.
FKV849I SNBU OPTION NOT ENABLED
Operator response
If the VTAM VARY NET ACT command failed, browse Explanation
You cannot access the SNBU Automation option for
FKV846I INACTIVATE FOR PORT port AON.
STARTING
System action
Explanation
AON/SNA stops the command.
You issued a VTAM VARY NET INACT command for the
specified port. Operator response
Message Variables Notify your system programmer if SNBU Automation
port must be enabled permanently. You can also enable
The SNBU port SNBU Automation by going to the AON Base Functions
panel and selecting Support Functions. This takes you
to the AON Support Functions panel. From this panel,
Operator response
select Enable/Disable Automation to enable SNBU.
If the VTAM VARY NET INACT command fails, you
receive message FVK832I. System programmer response
FKV847I DISCONNECT OF PU pu STARTING Update the FKVTABLE table for SNBU to ENABLE=Y.
FKV850I pu CANNOT BE MOVED TO SNBU.
Explanation
NO PORTS AVAILABLE IN POOL
AON/SNA started the process for disconnecting the pool
specified PHYSICAL_UNIT. This message is the first
one you receive during the process. Explanation
Message Variables You attempted to place a Switched Network Backup
pu Automation PHYSICAL_UNIT into dial backup mode.
The name of the physical unit that is starting Your attempt failed because placing the PU in dial
backup mode requires a pooled modem and none is
available.
Operator response
Message Variables
If the VTAM VARY NET ACT command fails, you
receive message FVK832I. The next message you pu
receive after FVK833I is either FKV838I, which states The name of the PU
that AON/SNA is starting to move the PU, or FKV819I, pool
which states that an error occurred. The name of the modem
FKV848I DISCONNECT OF PU pu COMPLETE FKV851I pu CANNOT BE MOVED TO SNBU.
NO MODEM POOLS DEFINED.
Explanation
AON/SNA started the process for disconnecting the Explanation
specified PHYSICAL_UNIT. This is the last message You attempted to place a Switched Network Backup
you receive during the process. Automation PHYSICAL_UNIT into dial backup mode.
Message Variables Your attempt failed because the PU requires a pooled
modem and no modem pools are defined.
pu
The SNBU port Message Variables
If the VTAM VARY NET ACT command fails, you pu
receive message FVK832I. The next message you The name of the PU
receive after FVK833I is either FKV838I, which states

System programmer response FKV933E INVALID X.25 ERROR CODE. MUST
BEGIN WITH 'L', 'P', 'Q', OR 'R'
If necessary, define a modem pool.
FKV858I pu HAS BEEN RESTORED FROM Explanation
SNBU TO LEASED LINE, BUT IS
NOT ACTIVE You entered an incorrect X.25 error code.
You moved the specified physical unit (PU) from Correct the entry.
switched network backup automation (SNBU) to FKV934I UNABLE TO FIND ANY TYPE=
normal leased line operation. The operation was restype FOR SCOPE= scope,
switched because either you issued the CHGSNBU CHKAUTO= ckauto
command, or AON/SNA received a BNJ017I message.
AON/SNA attempted to activate the PU, but failed.
Explanation
Message Variables
You issued the NETSTAT command, but NETSTAT
pu cannot find any resources to display based on your
The name of the remote PU (control unit) entry.
Message Variables
System action
restype
AON/SNA resumes processing. The PU is in leased line The type of resource
operation, probably in a pending status.
scope
The search parameter
Operator response
ckauto
Determine why the failure occurred and correct the The check automation flag
problem.
FKV935I SNBU IS NOT SELECTABLE
FKV914I NO MORE SUBORDINATE NODES BECAUSE SNBU IS DISABLED
TO DISPLAY
Explanation
Explanation
You attempted to select a Switched Network Backup
You attempted to view a lower resource, but the Automation command from the SNA Help Desk panel,
lowest resource is already displayed. but SNBU is not enabled.
FKV930I UNKNOWN ERROR CODE:
errorcode Operator response
If you want SNBU, select Support Functions from the
Explanation AON Base Functions panel. From this panel, select
You entered an incorrect error code. Enable/Disable Automation to enable SNBU.
Message Variables FKV937I SNBU IS NOT SELECTABLE

BECAUSE resname HAS NO PU
errorcode
The error code entered
Explanation
Operator response You attempted to select a Switched Network Backup

Automation command from a SNA Help Desk panel,
Contact the person who reported the problem to verify but the specified resource has no physical unit for a
that the error code is correct. If the error code is higher resource. SNBU works only on physical units.
correct, enter it again. If the error code is correct but
still not recognizable, notify your system programmer. Message Variables
resname
System programmer response The name of the resource
Note the error code and notify IBM Software Support. FKV940I INVALID COMMAND SELECTED

You attempted to issue a command that is not correct Select a local or remote modem or both.
for the type of resource.
FKV948I INVALID REQUEST - NO
FKV942I INVALID SELECTION - MUST BE A OPERATION SELECTED
REMOTE PU
Explanation
Explanation
You attempted to act upon a Switched Network
You attempted to act on a PHYSICAL_UNIT, but the PU Backup Automation PHYSICAL_UNIT but did not
is not known to VTAM. select an action.
FKV943I INVALID MODEM SELECTION
Operator response
Explanation Select an action.
You attempted to switch a modem speed but did not FKV949I INVALID REQUEST - PLEASE
select a correct modem type. RETRY
FKV944I INVALID REQUEST - SNBU
SELECTION CONFLICT Explanation
You selected an action that is not supported, or you
Explanation requested to act on an improper panel field.
You attempted to both connect and disconnect a
Switched Network Backup Automation Operator response
PHYSICAL_UNIT at the same time. Check your request and enter it again.
FKV950I RESOURCE NAME REQUIRED
Operator response
Select connect or disconnect but not both. Explanation
FKV945I INVALID REQUEST - CANNOT You attempted a Switched Network Backup
MODIFY STATUS ENTRIES Automation action but did not select a resource for the
action.
Explanation
You attempted to modify Switched Network Backup Operator response
Automation status file entries, but you are not allowed Select a PHYSICAL_UNIT and enter the action again.
to modify SNBU status file entries.
FKV951I RESOURCE NAME CHANGED -
FKV946I INVALID REQUEST - SPEED PRESS ENTER TO USE
SELECTION CONFLICT
Explanation
Explanation
While using SETSNBU, you changed the name of the
You attempted to change a modem speed but PHYSICAL_UNIT to a name that is not defined.
requested both SWITCH and RESTORE. These two
actions cannot be selected together. Operator response
Operator response Press Enter to define the current PU using the values
of the prior PU.
Select SWITCH or RESTORE but not both.
FKV952I RESOURCE NAME CHANGED -
FKV947I INVALID REQUEST - MODEM NOT CURRENT VALUES ARE
SPECIFIED DISPLAYED
You attempted to act upon a Switched Network While using SETSNBU, you changed the name of the
Backup Automation modem but did not specify a PHYSICAL_UNIT to a name that is defined.
modem.

To change the settings, press Enter. You attempted to define a line for a Switched Network
Backup Automation modem pool, but the pool does
FKV953I ONE OR MORE DEFAULTS ARE not exist.
DISPLAYED
Operator response
Explanation
Define the modem pool and try again.
You entered a SETSNBU command for a Switched
Network Backup AutomationPHYSICAL_UNIT. One or FKV962I POOL MUST BE DEFINED IF APO
more of the default automation settings are being IS SPECIFIED
used.
FKV954I CURRENT DEFAULTS ARE Explanation
DISPLAYED You specified APO=YES for a Switched Network
Backup Automation PHYSICAL_UNIT definition. This
Explanation also requires the use of a modem pool.
You entered a SETSNBU command without specifying
the name of a PHYSICAL_UNIT. The switched network Operator response
backup automation default values are displayed. You Select a valid modem pool and enter the command
pressed PF9 on the TCP/IP for OS/390® Session Status again.
Filters panel.
FKV963I NO MODEM POOLS DEFINED
FKV955I THIS IS A NEW SNBU RESOURCE
DEFINITION. PRESS ENTER TO Explanation
ADD
You attempted to define a line for a Switched Network
Explanation Backup Automation modem pool, but no SNBU pools
are defined.
You entered a SETSNBU command for an undefined
physical unit (PU). The default switched network Operator response
backup automation settings are displayed.
If necessary, notify your system programmer.
Change the default settings for this resource and press
ENTER to add the definition. Press F3 to cancel the
add function. System programmer response
Add SNBUPOOL entries to the control file.
FKV959I CANNOT SPEED SWITCH LEVEL 2
MODEM FKV964I line NOT DEFINED TO A MODEM
POOL
Explanation
You attempted to speedswitch a Link Segment Level 2 Explanation
modem. This action is not supported. The specified line is not defined to a modem pool.
FKV960I POOL NAME MUST BE 4 Message Variables
CHARACTERS OR LESS
line
The name of the line that is not defined
Explanation
FKV965I MODEM POOL NAME IS REQUIRED
You referenced a Switched Network Backup
Automation modem pool, but the name of the pool
must be four or fewer characters in length. Explanation
You issued the SETPOOL command for a Switched
Operator response Network Backup Automation resource, but no pool is
defined for the resource.
Try again using a correct modem pool name.
FKV961I DEFINE POOL BEFORE USING Operator response
Select a modem pool for the resource.

FKV966I LINE NAME IS REQUIRED Explanation
You attempted to enter one or more phone numbers
Explanation that are too long.
You issued a SETPOOL command, but did not specify a
line name. Operator response
Correct the phone numbers.
Operator response
FKV980I ENTER TYPE OF CHANGE: 1-ADD
Enter a valid line name. 2-DELETE
FKV970I PHONE NUMBER IS REQUIRED
WITH AUTOBK Explanation
You did not specify an action for the SETPOOL
You requested the AUTOBK command, but did not
provide phone numbers for the dial command. Operator response
Select 1 for Add or 2 for Delete.
Operator response
FKV989I VERIFY SELECTION AND PRESS
Provide dial phone numbers. ENTER TO CONTINUE.
FKV971I ERROR IN PHONE NUMBER(S)
Explanation
Explanation You requested that the SNA Help Desk start a
The phone numbers specified for a Switched Network Switched Network Backup Automation action.
Backup Automation dial are in error.
Operator response
Operator response Verify the action and press Enter to start it.
Correct the phone numbers. FKV993I CANNOT CHANGE POOL
FKV972I PHONE NUMBER INVALID - LOCAL DEFINITION
MODEM
Explanation
Explanation You attempted to change a pool definition of type
The phone number you specified for the local modem POOL. This definition can be issued only against a
includes incorrect characters. Only the characters 0–8, physical unit (PU).
F, P, -, (, and ) are valid.
Operator response
Operator response Press the Tab key to move the cursor to a PU name
Correct the phone number. and press F4. Then, select the Change option and
press Enter.
FKV973I PHONE NUMBER INVALID -
REMOTE MODEM FKV996I INVALID SELECTION FOR SNBU -
VALID RESOURCES ARE PU AND
LINE
Explanation
The phone number you specified for the remote Explanation
modem includes incorrect characters. Only the
characters 0–8, F, P, -, (, and ) are valid. You attempted to issue a SNBU command against a
resource that is not a physical unit (PU) or a LINE.
Operator response
Operator response
Correct the phone number.
Press the Tab key to move the cursor to a PU or LINE
FKV974I PHONE NUMBER TOO BIG and issue the SNBU command again.

FKV997I UNABLE TO RUN SNBU ON LINE Explanation
resname. NO PU FOUND FOR THIS You attempted to cancel a logical unit (LU) that is in an
RESOURCE unknown or disconnected state or has no sessions.
You attempted to issue a SNBU command on a line but resname

there is no defined physical unit (PU) to which the The name of the resource
LINE can send the command.
Operator response
Message Variables
Press the Tab key to move the cursor to a resource
resname that is known and is not one of the above and enter a
The name of the resource character to cancel the session.
FKV998I INVALID SELECTION TO CANCEL.
LU = resname

Chapter 9. FKX Prefix Messages
FKX messages provide error descriptions and information about AON/TCP.

FKX101I IDLE TIME THRESHOLD Explanation
EXCEEDED FOR CONNECTION AON/TCP monitoring detected that a connection for
conn_id BETWEEN stack_ipaddr : the specified port has exceeded the IDLETIME
port AND client_ipaddr : port. specification and has broken the connection.
ACTION=NOTIFY SP=sp_name
POLICY=policy_name. Message Variables
conn_id
Explanation The connection which exceeded the IDLETIME
AON/TCP monitoring detected that a connection for threshold, in the format of decimal connection ID/
the specified port has exceeded the IDLETIME hexadecimal connection ID
specification. stack_ipaddr
The IP address of the stack
Message Variables
client_ipaddr
conn_id The IP address of the client
The connection which exceeded the IDLETIME
threshold, in the format of decimal connection ID/ port
hexadecimal connection ID The port number of the stack or client
stack_ipaddr sp_name
The IP address of the stack The TCP/IP stack name
client_ipaddr policy_name
The IP address of the client The IPCONN policy governing this action
port
System action
The port number of the stack or client
sp_name Based on policy definitions, the AON notification policy
The TCP/IP stack name is invoked and the connection is dropped.
policy_name
The IPCONN policy governing this action Operator response
System action
Based on policy definitions, the AON notification policy System programmer response
is invoked. Determine why the connection exceeded the idle time
criteria and establish the connection again, if
Operator response necessary. The IPCONN policy specification for the
application might need to be revised.
FKX104I MINIMUM BYTES THRESHOLD
System programmer response EXCEEDED FOR CONNECTION
conn_id BETWEEN stack_ipaddr :
Determine why the connection exceeded the idle time port AND client_ipaddr : port.
criteria and take the appropriate action, if necessary. ACTION=NOTIFY SP=sp_name
The IPCONN policy specification for the application POLICY=policy_name.
might need to be revised.
FKX102I IDLE TIME THRESHOLD Explanation
EXCEEDED FOR CONNECTION AON/TCP monitoring detected that a connection for
conn_id BETWEEN stack_ipaddr : the specified port has exceeded the MINBYTES
port AND client_ipaddr : port. specification.
ACTION=DROP SP=sp_name
POLICY=policy_name. Message Variables

conn_id sp_name
The connection which exceeded the MINBYTES The TCP/IP stack name
threshold, in the format of decimal connection ID/ policy_name
hexadecimal connection ID The IPCONN policy governing this action
stack_ipaddr
The IP address of the stack System action
client_ipaddr Based on policy definitions, the AON notification policy
The IP address of the client is invoked and the connection is dropped.
port
The port number of the stack or client Operator response
sp_name
The TCP/IP stack name
policy_name System programmer response
The IPCONN policy governing this action
Determine why the connection exceeded the minimum
System action bytes criteria and establish the connection again, if
necessary. The IPCONN policy specification for the
Based on policy definitions, the AON notification policy application might need to be revised.
is invoked.
FKX107I MAXIMUM BYTES THRESHOLD
EXCEEDED FOR CONNECTION
Operator response
conn_id BETWEEN
Notify your system programmer. stack_ipaddr:port AND
client_ipaddr:port.
System programmer response ACTION=NOTIFY SP=sp_name
POLICY=policy_name.
Determine why the connection exceeded the minimum
bytes criteria and take the appropriate action, if
Explanation
necessary. The IPCONN policy specification for the
application might need to be revised. AON/TCP monitoring detected that a connection for
the specified port has exceeded the MAXBYTES
FKX105I MINIMUM BYTES THRESHOLD specification.
EXCEEDED FOR CONNECTION
conn_id BETWEEN stack_ipaddr : Message Variables
port AND client_ipaddr : port. conn_id
ACTION=DROP SP=sp_name The connection which exceeded the MAXBYTES
POLICY=policy_name. threshold, in the format of decimal connection ID/
hexadecimal connection ID
Explanation
stack_ipaddr
AON/TCP monitoring detected that a connection for The IP address of the stack
the specified port has exceeded the MINBYTES client_ipaddr
specification and has broken the connection. The IP address of the client
Message Variables port
conn_id The port number of the stack or client
The connection which exceeded the MINBYTES sp_name
threshold, in the format of decimal connection ID/ The TCP/IP stack name
hexadecimal connection ID policy_name
stack_ipaddr The IPCONN policy governing this action
client_ipaddr System action
The IP address of the client Based on policy definitions, the AON notification policy
port is invoked.
The port number of the stack or client

Operator response FKX204I INVALID IP ADDRESS FOR sp-
ADDRESS ip address
Explanation
One or more octects of the supplied IP address is non-
Determine why the connection exceeded the
numeric.
maximum bytes criteria and take the appropriate
action, if necessary. The IPCONN policy specification Message Variables
for the application might need to be revised.
sp
FKX108I MAXIMUM BYTES THRESHOLD The name of the TN3270 server request
EXCEEDED FOR CONNECTION ip address
conn_id BETWEEN The supplied IP address from the configuration file
stack_ipaddr:port AND
client_ipaddr:port. ACTION=DROP
System action
SP=sp_name
POLICY=policy_name. The command ends.

AON/TCP monitoring detected that a connection for If problems persist, notify your system programmer.
the specified port has exceeded the MAXBYTES
specification and has broken the connection. System programmer response
Message Variables Define a valid IP address for this TN3270 server.
conn_id
FKX300I IDS EVENT RECEIVED :
The connection which exceeded the MAXBYTES
DIPADDR=dest_ip_addr,
threshold, in the format of decimal connection ID/
SIPADDR=src_ip_addr,
hexadecimal connection ID
CORRELATOR=nnnn.
stack_ipaddr MEMBER=member_name
client_ipaddr Explanation
The IP address of the client
This message indicates that an Intrusion Detection
port Automation Service (IDS) event has been processed by
The port number of the stack or client IDS automation services. One or more actions can
sp_name have occurred. The responses to those actions are
The TCP/IP stack name listed in DSIPARM member member_name. If
member_name is NONE, there is no data to view.
policy_name
The IPCONN policy governing this action Message Variables
dest_ip_addr
System action The destination IP address for the IDS event as
Based on policy definitions, the AON notification policy determined from the message that started IDS
is invoked and the connection is dropped. automation services. If the dest_ip_addr is
UNKNOWN, the destination IP address cannot be
determined.
Operator response
src_ip_addr
Notify your system programmer. The source IP address
nnnn
The IDS correlator associated with the event
Determine why the connection exceeded the member_name
maximum bytes criteria and establish the connection The name of the DSIPARM member containing the
again, if necessary. The IPCONN policy specification command responses. This name is listed in the
for the application might need to be revised. following CNMSTYLE definition:
IDS.Event_Log_File = DSIPARM.member_name
Chapter 9. FKX Prefix Messages 491

If NONE is specified, event logging is not enabled. FKX303I IDS EVENT DETECTED CONTAINS
UNKNOWN probeid
If **ERROR** is specified, no data can be written
to the file. For more information, browse DSILOG
for message CNM236. Explanation
An IDS event was sent to IDS automation services.
System action However, IDS automation services did not recognize
the probeid contained in the event. The event
containing the unknown probeid is logged immediately
following this message.
Operator response
Message Variables
For additional information on the IDS event, browse
DSIPARM member member_name. probeid
The probe ID from the IDS event.
System action
If necessary, grant the operator access to browse
DSIPARM member member_name. The event is discarded.
FKX301I IDS EVENT THRESHOLD OF nnn

EVENTS DURING INTERVAL
interval REACHED FOR STACK Browse CNMSTIDS and ensure that the probeid is
stackname defined in the IDS.PROBEID.* list.
FKX305I IDS EVENT DETECTED FOR
Explanation DESTINATION IP ADDRESS
A number of IDS events (for which the threshold was dest_ip_addr BUT COULD NOT
matched or exceeded) were detected within the CORRELATE TO A KNOWN TCP/IP
system. The threshold is set in the CNMSTIDS STACK.
member. This message is sent to the IDS NTFYOPs.
Explanation
Message Variables
An IDS event was sent to IDS automation services.
nnn
However, IDS automation services was unable to
The threshold for the number of IDS events as
determine the TCP/IP stack associated with the
defined in the following CNMSTIDS statement:
destination IP address.
IDS.Auto_Thresh = nnn
Message Variables
interval dest_ip_addr
The time interval used to determine the threshold The destination IP address for the IDS event as
as defined in the following CNMSTIDS statement: determined from the message that started IDS
automation services. If the dest_ip_addr is
IDS.Auto_Intvl = hh:mm:ss
UNKNOWN, the destination IP address cannot be
determined.
stackname
The name of the stack as defined on a TCP390
policy definition. System action
Processing continues. Some data (such as Summary
System action Probe Statistics) might not include this event.
IDS events are ignored until enough time has passed
to no longer trigger this threshold. System programmer response
For more information related to the event, browse
System programmer response DSILOG for EZZ* messages.
Check your CNMSTYLE definitions and update as FKX400I tracetype SCHEDULED FOR SP sp
needed. See IBM Z NetView Installation: Getting BY OPERATOR operid
Started for information on how to modify the
CNMSTYLE member.

NetView has successfully started the trace requested The command fails.
by operator operid for the service point sp.
tracetype Issue the command again.

The type of trace requested. Valid types are
CTRACE or PKT. System programmer response
sp If the problem persists, contact IBM Software Support.
The NetView service point for which the trace was
requested. FKX403I tracetype STOPPED FOR SP sp BY
OPERATOR operid
operid
The ID of the operator who made the trace start
The request to stop the trace completed successfully.
FKX401I tracetype - DELAY TRACE
SCHEDULED FOR SP sp BY operid Message Variables
tracetype
Explanation The type of trace requested. Valid types are
NetView has successfully scheduled a timer to start CTRACE or PKT.
the trace requested by operator operid for the service sp
point sp at a future date and time. The name of the NetView service point that was
Message Variables traced
operid
tracetype
The ID of the operator who requested the trace
CTRACE or PKT. FKX405I TARGET DOMAIN/PROC FOR SP sp
sp IS NOT VALID
The name of the NetView service point to be
traced Explanation
operid The target NetView domain and TCP/IP procedure
The ID of the operator who requested the trace name for the service point sp is not recognized.
FKX402I tracetype action START FOR SP sp Message Variables
FAILED - MESSAGE msgid
sp
RECEIVED.
The name of the NetView service point for which
the trace was requested
Explanation
The attempt to start or stop the trace has failed. The System action
msgid is the message received from the MVS TRACE
The command fails.
command.
tracetype Correct the names of the target NetView domain and
The type of trace requested. Valid types are TCP/IP procedure and issue the command again. If
CTRACE or PKT. you are using the 3270 interface, contact the system
action programmer.
Either START or STOP
sp System programmer response
The name of the NetView service point for which Contact IBM Software Support.
msgid FKX406I tracetype - DELAYED TRACE
The error message received from the MVS TRACE FAILED FOR SP sp BY operid
command

NetView cannot schedule the timer for a trace to start Verify the operator has sufficient NetView security
at a later date and time. access to set the timer. If the problem persists,
Message Variables
FKX408I TRACE INSTANCE STARTED FOR
tracetype
STACK stack BY OPERATOR operid
ON TASK task AT SP sp
CTRACE or PKT.
sp
Explanation
The operid operator started a new packet trace
instance for the indicated TCP/IP stack, and the trace
operid is running on the indicated NetView autotask. Each
The ID of the operator who requested the trace trace instance is assigned to a unique NetView task.
Message Variables
System action
operid
The command fails. The ID of the operator who requested the trace.
sp
Operator response
Verify that the date and time were entered correctly. If the trace was requested.
they are in the correct format, contact the system stack
programmer. The name of the TCP/IP stack for which the trace
was started.
System programmer response task
Determine why NetView is unable to schedule the The name of the NetView autotask to which the
timer. If the problem persists, contact IBM Software trace instance is assigned.
Support.
FKX409I TRACE INSTANCE ENDED FOR
FKX407I DELAYED tracetype BLOCKED BY STACK stack BY OPERATOR operid
SECURITY FOR SP sp BY operid ON TASK task AT SP sp
The operid operator issued a command to end the
Operator operid was attempting to schedule a timer packet trace instance for the indicated TCP/IP stack
and NetView received a security failure. that was running on the indicated NetView autotask.
Message Variables Each trace instance is assigned to a unique NetView
task. When a trace instance is ended, all packets and
tracetype storage that are associated with the trace instance in
The type of trace requested. Valid types are the NetView program are released.
CTRACE or PKT.
Message Variables
sp
The name of the NetView service point for which operid
the trace was requested The ID of the operator who requested the trace.
operid sp
The ID of the operator who requested the trace The name of the NetView service point for which
the trace was requested.
System action stack
The command fails. The name of the TCP/IP stack for which the trace
was started.
The name of the NetView autotask to which the
Contact the system programmer. trace instance is assigned.
FKX410I UNABLE TO START tracetype ON
SP sp - TRACE ALREADY ACTIVE

Explanation tracetype
NetView has determined that a trace type of tracetype
CTRACE or PKT.
already exists for this service point.
sp
Message Variables The name of the NetView service point for which
tracetype the trace was requested
CTRACE or PKT. System action
sp The command fails.
Operator response
System action If necessary, cancel the delayed trace and issue the
command again.
The command fails.
Operator response
If necessary, stop the active trace and issue the
command again. FKX413I THE PROCNAME proc IS NOT
DEFINED ON SP sp
Explanation
The procname proc requested for this trace does not
FKX411I UNABLE TO STOP tracetype ON SP exist on this service point.
sp - TRACE NOT ACTIVE
Message Variables
Explanation proc
The name of the TCP/IP procedure
NetView has determined that no trace type of
tracetype currently exists for this service point. sp
Message Variables the trace was requested
tracetype
The type of trace requested. Valid types are System action
CTRACE or PKT.
The command fails.
sp
Operator response
System action
The command fails.
Verify that the FT.sp.TARGET common global variable
System programmer response for this service point is correctly set. If this is a
CNMPOLCY-defined service point, ensure that the
If the problem persists, contact IBM Software Support. TCPNAME parameter of the TCP390 statement is set
FKX412I START tracetype ON SP sp FAILED to the correct name. If the problem persists, contact
- TRACE ALREADY SCHEDULED IBM Software Support.
FKX414I UNABLE TO START WRITER ON SP
Explanation sp, PACKET TRACE ALREADY
ACTIVE
NetView has determined that a delayed trace type of
tracetype already exists for this service point.
Explanation
Message Variables
You tried to start a packet trace with a writer, but the
packet trace component SYSTCPDA is already active.

Because NetView cannot determine why SYSTCPDA Explanation
was previously started, the START command is The trace that was previously suspended was resumed
stopped. with a PKTTRACE START OPID command for this trace
instance. For details about the suspension of the trace,
Message Variables
see the FKX415I message.
sp
Message Variables
the trace was requested. operid
The ID of the operator who requested the trace.
System action sp
The command fails.
Operator response stack

The name of the TCP/IP stack for which the trace
Verify the state of the SYSTCPDA component for this was started.
service point. If appropriate, stop the SYSTCPDA
task
component and reissue the command. If the problem
persists, contact the system programmer.
trace instance is assigned.
System programmer response FKX417I TRACE INSTANCE action FAILED

FOR STACK stack ON SP sp
FKX415I TRACE INSTANCE SUSPENDED Explanation
FOR STACK stack BY OPERATOR A trace start or stop was requested, but the requested
operid ON TASK task AT SP sp action failed.
Message Variables
Explanation
The trace that is active on this task suspended packet action
data collection because of a PKTTRACE STOP action. The requested action (START, STOP, or STOPALL)
The trace is still associated with the NetView task on that failed.
which it was started. You can restart the trace by sp
issuing a PKTTRACE START OPID=operid command for The name of the NetView service point for which
this trace instance. Because filters that were set the trace was requested.
previously are not retained, restarting a trace requires stack
you to set any filters that you want (such as IPADDR or The name of the TCP/IP stack for which the trace
PORTNUM). was started.
Message Variables
operid System action
The ID of the operator who requested the trace. The command fails.
sp
The name of the NetView service point for which Operator response
Review the NetView log for additional messages.
stack
The name of the TCP/IP stack for which the trace
was started.
task Additional messages that describe the failure are
The name of the NetView autotask to which the logged in the NetView log. If the problem persists,
trace instance is assigned. contact IBM Software Support.
FKX416I TRACE INSTANCE RESUMED FOR FKX418I TRACE INSTANCE STOPPED ON

STACK stack BY OPERATOR operid TASK task FOR STACK stack
ON TASK task AT SP sp
Explanation
The trace that is active on the specified task
suspended packet data collection because of a PKTS

STOPCOLL action. The trace is still associated with the System action
NetView task on which it was started, and the trace
The command fails.
records can be queried by using the PKTS QUERY
action. You can resume the trace by issuing a PKTS
START OPID=task command for this trace instance. Operator response
Because filters that were set previously are not Verify the options being requested are correct. If you
retained, resuming a trace requires you to set any are using the 3270 interface, contact the system
filters that you want (such as IPADDR or PORTNUM). programmer.
Message Variables
stack
The name of the TCP/IP stack for which the trace Contact IBM Software Support.
was started.
FKX431I DUPLICATE CTRACE OPTION opt
task SPECIFIED - sp
Explanation
System action A duplicate option was specified in the trace start

request.
Packet data collection for the active trace on the
specified task is suspended. Message Variables
FKX419I TRACE INSTANCE ENDED ON sp

TASK task FOR STACK stack The name of the AON service point for which the
trace was requested
Explanation opt
The trace that is active or suspended on this task The name of the duplicate option.
ended packet data collection as a result of a PKTS
STOP action. The trace is no longer associated with the System action
NetView task on which it was started, and cannot be
The command fails.
resumed or queried.
stack Verify the options being requested are correct. If you
The name of the TCP/IP stack for which the trace are using the 3270 interface, contact the system
was started. programmer.
task
The name of the NetView autotask to which the System programmer response
System action FKX432I INVALID CTRACE OPTION opt
SPECIFIED - sp
Packet data collection for the active or suspended
trace on the specified task is ended.
Explanation
FKX430I NO VALID CTRACE OPTIONS
SPECIFIED - sp An incorrect option was specified in the trace start
request.
Either no CTRACE options were specified or none of sp
the options were valid for this trace request. The name of the AON service point for which the
trace was requested
Message Variables
opt
sp The name of the incorrect option
The name of the AON service point for which the
trace was requested

The command fails. Verify the IP address is specified correctly.

Verify the options being requested are correct. If you If the problem persists, contact IBM Software Support.
are using the 3270 interface, contact the system
FKX435I INVALID IP PORT ipport
programmer.
SPECIFIED FOR CTRACE - sp

Explanation
An incorrect port number was found in the requested
FKX433I NO VALID CTRACE OPTIONS trace start.
SPECIFIED - sp
Message Variables
Explanation sp
None of the options specified in the trace start request trace was requested
are valid.
ipport
Message Variables The IP port number
sp
The name of the AON service point for which the System action
trace was requested The command fails.

The command fails. Verify the IP ports being requested are valid.

Verify the options being requested are correct. If you If the problem persists, contact IBM Software Support.
programmer. FKX436I NO PKT TRACE OPTIONS MATCH
ANY VALID LINK NAMES FOR sp
Explanation
NetView checks the service point for its link names
FKX434I INVALID IP ADDRESS ipaddr and matches them to the link names in the request. No
SPECIFIED FOR CTRACE - sp matches were found.
Message Variables
Explanation
sp
An IP address specified for the trace start request is
not in the correct format.
trace was requested
Message Variables
sp System action
The name of the AON service point for which the The command fails.
trace was requested
ipaddr Operator response
The IP address
Verify the options being requested are correct. If you
System action
programmer.
The command fails.

Contact IBM Software Support. The trace and automatic stop requests were
successful.
FKX437I INVALID option (opt) SPECIFIED
FOR PKT TRACE START - sp Message Variables
tracetype
Explanation The type of trace requested. Valid types are
One of the PKT trace options specified has an incorrect CTRACE or PKT.
value. sp
Message Variables
trace was requested
sp operid
The name of the AON service point for which the The ID of the operator who requested the trace
trace was requested
FKX461I tracetype STARTED BY operid FOR
option
SP sp BUT AUTOSTOP FAILED
The type of PKT trace option found in error
opt
Explanation
The value in error
The trace request was successful, but the requested
System action automatic stop was not.
The command fails. Message Variables

tracetype
Operator response The type of trace requested. Valid types are
CTRACE or PKT.
Verify the options being requested are valid.
sp
trace was requested
If the problem persists, contact IBM Software Support. operid
FKX438I SIZE OF THE TOTAL OPTIONS The ID of the operator who requested the trace
REQUESTED IS TOO LARGE - sp
System action
Explanation Trace is started, but requires a manual stop.
CTRACE has a limit of 1024 characters in the options
field. The requested options, including values, IP Operator response
address, and port, has exceeded this maximum.
Stop the trace and determine why NetView was unable
Message Variables to schedule the timer.
sp
The name of the AON service point for which the System programmer response
trace was requested If the problem persists, contact IBM Software Support.
System action FKX462I tracetype STARTED BY operid FOR

SP sp BUT AUTOSTOP BLOCKED
The command fails. BY SECURITY

Reduce the options being requested. The trace request was successful, but the requested
FKX460I automatic stop was not allowed by NetView security.
tracetype STARTED AND
AUTOSTOP SCHEDULED FOR SP sp Message Variables
BY operid
tracetype
CTRACE or PKT.

sp No additional action is needed.
FKX465I NO OPIDS DEFINED FOR TRACE
trace was requested
INSTANCES
operid
The ID of the operator who requested the trace Explanation:
The operator entered a PKTTRACE START command
without specifying an OPID parameter. Because the
System action PKTTRACE command can assign an autotask from a
Trace is started, but requires a manual stop. pool of autotasks to the trace instance, this is a valid
request. However, in this case, the PKTTRACE
Operator response command cannot find a pool of autotasks to use.
Contact the system programmer. System action:

The command stops.
System programmer response Operator response:
Contact the systems programmer.
Verify the operator has sufficient NetView security
access to set the timer. If the problem persists, System programmer response:
contact IBM Software Support. The pool of autotasks is defined on the
COMMON.PKTS.INSTANCE.POOL parameter in the
FKX463I OPID REQUIRED FOR STOP OR CNMSTYLE member. Verify that the common global
STOPALL OF TRACE INSTANCE variable for this is set. If it is and the problem persists,
Explanation: contact IBM Software Support.
The operator entered a PKTTRACE command with a FKX466I NO AVAILABLE OPIDS FOR TRACE
STOP or STOPALL action but did not specify the OPID INSTANCES
parameter. The OPID parameter is needed for these
actions so that the PKTTRACE request can be issued to Explanation:
the correct NetView autotask. The operator entered a PKTTRACE START command
without specifying an OPID parameter. Because the
System action: PKTTRACE command can assign an autotask from a
The command stops. pool of autotasks to a trace instance, this is a valid
Operator response: request. However, in this case, all the autotasks in the
Re-enter the PKTTRACE command with the OPID pool already have active traces assigned to them.
parameter to indicate the NetView autotask for the System action:
trace that you want. The command stops.
System programmer response: Operator response:
No additional action is needed. To free autotasks, end any trace instances that are no
FKX464I OPID task DOES NOT HAVE AN longer needed. If more autotasks are needed, contact
ACTIVE TRACE INSTANCE the systems programmer.

The operator entered a PKTTRACE command with a The pool of autotasks is defined on the
STOP or STOPALL action, but no trace is active for the COMMON.PKTS.INSTANCE.POOL parameter in the
specified OPID (NetView autotask). CNMSTYLE member. Verify that the common global
variable for this is properly set. Change the number of
Message Variables tasks as needed for your environment.
task Important:
The name of a valid NetView autotask to which an
active trace instance is assigned. Too many concurrent trace tasks can affect
performance.
System action:
The command stops. FKX467I OPID task ALREADY HAS AN
ACTIVE TRACE INSTANCE
Operator response:
Re-enter the PKTTRACE command with the correct
NetView autotask for the trace that you want. Explanation
The operator entered a PKTTRACE START command
System programmer response: with an OPID parameter for an autotask that already

has an active trace collecting packet data. To restart System programmer response
the trace with different filters, the operator must first
None
issue a PKTTRACE STOP command. The PKTTRACE
STOP command sets the trace to the DORMANT FKX476I PACKET TRACE DELETED
status, and a new PKTTRACE START command can be
issued. Explanation
Message Variables The request to delete the packet trace completed
task successfully.
The name of the requested NetView autotask to
which an active trace instance is assigned. System action
System action: The command ends.
The command stops.
Operator response: Operator response
Verify the name of the task that you are trying to start. None
Re-enter the command with the correct task name.
FKX470I NO SERVICE POINTS FOUND System programmer response
MATCHED SP sp
None
Explanation FKX477I NO HEADERS FOUND IN FILE
FKXPKTS
The name of the service point or stack entered by the
operator does not match the SPs defined (TCP390
definition) in the DSIPARM member CNMPOLCY Explanation
configuration file. The stack may be defined in The LISTTRRC command did not find any packet trace
CNMPOLCY but is missing required information such headers in the FKXPKTS database.
as a domain name or a TCP name.
sp The command ends.
trace was requested Operator response
Operator response
Enter the correct service point name as defined in the System programmer response
CNMPOLCY configuration member and issue the
command again. If you are using the IPMAN function, Verify that the FKXPKTS database is active and
ensure that the policy loaded successfully and that whether there are active traces in the database. If
there is a LOCAL stack (DOMAIN=LOCAL) defined. there are active traces in the database, contact IBM
Software Support.
FKX475I PACKET TRACE SAVED
FKX478I AN UNEXPECTED ERROR HAS
OCCURRED USING DSIVSMX
Explanation
action
The request to save the packet trace has completed
successfully. Explanation
DSIVSMX is the NetView facility that is used to write,
System action read, and delete packet traces from the database. In
The command ends. this case, the function has returned an unexpected
response.
None action
This can be any of the following values:
CLOSE

DELETE Operator response
OPEN The system might be busy. Try to reissue the
READ command at a later time.
WRITE
System action
If necessary, increase the WAITTIME.
The command ends.
FKX490I NO ESTABLISHED
COMMUNICATION WITH REMOTE
Operator response
DOMAIN dom
Explanation
Communication with the remote domain cannot be
Check the log for any VSAM error messages. If the established. There is no active session with the remote
problem persists, contact IBM Software Support. domain.
FKX479I UNABLE TO action PACKET TRACE, Message Variables
AUTOTASK taskname IS NOT dom
ACTIVE The name of the remote domain as defined in the
DSIPARM member FKXCFG01 configuration file
Explanation (using TCP390 definitions).
The autotask is not active.
Operator response
Message Variables
Activate communication with the remote system.
action
The action, Write or Delete, that you were FKX500I restype resname ON servicept
attempting to complete. FAILURE DETECTED BY PASSIVE
MONITORING - RECOVERY
taskname
INITIATED
The name of the NetView autotask defined for
FKXPKTS in CNMSTYLE.
Explanation
System action AON/TCP detected a failure on the specified NetView
for AIX® resource.
The command ends.
Message Variables
Operator response restype
Activate the autotask. If the problem persists, contact The type of resource
the system programmer. resname
System programmer response servicept
Check the autotask; if it is active and available, contact The name of the NetView for AIX service point
System action
FKX480I TIMEOUT IN COLLECTING TRACE
INFO AT DOMAIN dom AON/TCP starts recovery monitoring on the MONIT
intervals defined in the control file and updates the
Explanation Dynamic Display Facility (DDF). Automated recovery
does not occur.
A command to collect trace information at the NetView
domain dom was issued, but the global variable Operator response
WAITTIME initialized at AON startup has expired.
If problems persist, notify your system programmer.
Message Variables
dom
The name of the NetView domain

Resolve the failure by going to the service point If the CPU load is unacceptable, notify your system
workstation and correcting the problem. programmer.
FKX501I restype resname ON servicept HAS
RECOVERED - RECOVERY System programmer response
TERMINATED If the CPU is overloaded, resolve the problem.
FKX503I DISK UTILIZATION THRESHOLD
Explanation
OF threshold EXCEEDED FOR
AON/TCP recovered the specified resource. restype resname ON servicept -
DISK UTILIZATION IS diskutil
Message Variables
restype Explanation
AON/TCP received a disk utilization from the NetView
resname for AIX service point. Disk utilization exceeded the
The name of the resource percentage for disk utilization defined in the
servicept THRESHOLDS DISK parameter in the control file.
The name of the NetView for AIX service point
Message Variables
Recovery monitoring stops. Active monitoring starts, if
the supporting definitions exist in the control file. resname
AON/TCP removes the resource from the display in the The name of the resource
Dynamic Display Facility (DDF). servicept
FKX502I CPU LOAD THRESHOLD OF
threshold EXCEEDED FOR restype diskutil
resname ON servicept - CPU LOAD The current disk utilization
IS currentcpu threshold
The threshold for disk utilization
Explanation
System action
AON/TCP received a CPU load alert from the NetView
for AIX service point. The CPU load exceeded the AON/TCP updates the Dynamic Display Facility (DDF).
percentage for the load defined in the parameter for
THRESHOLDS CPU in the control file. Operator response
Message Variables If disk utilization is unacceptable, notify your system
restype programmer.
resname System programmer response
The name of the resource If disk utilization is unacceptable, resolve why the disk
servicept on the host is full and provide more disk space.
FKX504I NETVIEW FOR AIX SERVICE
currentcpu POINT servicept RESPONSE FOR
The current CPU load COMMAND
threshold
The threshold of the CPU load Explanation
You issued a run command to the NetView for AIX
System action service point.
AON/TCP updates the Dynamic Display Facility (DDF). Message Variables
servicept

System action LINKDOWN status. DDF and logs are updated.
Operators receive FKX505I.
AON/TCP continues processing.
FKX505I LINK linkid IN ROUTER Operator response
router_name ON servicept IS NOT
ACCESSIBLE Resolve link failure on router.
A link on a router cannot be pinged. The failure was Resolve link failure on router.
detected by active or passive monitoring. FKX507I AUTHORIZATION FAILURE
Message Variables DETECTED ON restype resname BY
servicept
linkid
The name of the failed link
Explanation
router_name
The name of the router AON/TCP detected an authorization failure on the
specified resource. You see this message when a value
servicept of ALL is defined in the THESHOLDS AUTH parameter.
Message Variables
Failure processing, if appropriate, was initiated. DDF
and operators are notified. resname
Operator response servicept
Resolve link failure on router.
System action
AON/TCP does not start recovery.
Resolve link failure on router.
FKX506I ROUTER router_name ON servicept Operator response
HAS INACCESSIBLE LINKS
(failed_link_list) Notify your system programmer.
A router has 1 or more interfaces that cannot be Follow procedures for following up on an authorization
pinged through the NetView for AIX service point. The failure.
router IP address can be pinged so the router is still FKX508I AUTHORIZATION FAILURE
accessible through the TCP/IP network. A router can THRESHOLD EXCEEDED FOR
be a hub, router, or gateway. restype resname ON servicept -
Message Variables failures FAILURES WITHIN interval
router_name
Explanation
The name of the router
servicept The specified resource exceeded its threshold for
The name of the NetView for AIX service point authorization failures. The specified number of failures
occurred within the specified interval. The number of
failed_link_list allowed authorization failures for the resource is
All the links that have failed on the router defined in the THRESHOLDS AUTH parameter.
Failure processing for Link is initiated. No action is restype

taken for the router, except that the router is in The type of resource

resname FKX510I IPPORT MONITORING CANNOT BE
The name of the resource STOPPED
servicept
The name of the NetView for AIX service point Explanation
failures You attempted to stop monitoring a port, but port
The number of authorization failures monitoring cannot be stopped individually.
interval
The time period System action
The command fails.
System action
AON/TCP does not start recovery. Operator response
Operator response
All ports under a defined stack can be stopped at the
System programmer response same time by purging their active and recovery timers.
Follow procedures for following up on an authorization FKX512I restype resname ON servicept
failure. ACCESSIBLE BY IP ADDRESS
FKX509I restype resname ON servicept ipaddr BUT NOT BY HOST NAME
FAILURE DETECTED BY ACTIVE hostname, THE NAME SERVER
MONITORING - RECOVERY MAY BE DOWN
INITIATED
Explanation
Explanation Active monitoring detected a failure with the specified
AON/TCP active monitoring detected a failure on the resource. The resource is accessible at the specified
specified resource. IP address but not by the specified host name. This
condition often occurs when the name server in the
Message Variables domain fails. This message appears to operators only
restype if NTFY=ALL is defined in the LSTHRESH NAMESERVER
The type of resource statement in the control file.
resname Message Variables
restype
servicept The type of resource
resname
System action
servicept
Recovery monitoring starts on the MONIT control file The name of the NetView for AIX service point
intervals. AON/TCP does not start automated ipaddr
recovery, but updates the Dynamic Display Facility The IP address of the resource
(DDF).
hostname
The host name of the resource
Operator response
Notify your system programmer. System action
AON/TCP does not process the failure because the
resource is still accessible on the network by its IP
If necessary, intervene manually to solve the problem. address.
Follow local procedures for recovering a NetView for
AIX service point or TCP/IP host.

Check the status of the name servers and notify your
system programmer. servicept
System programmer response definedrtt
The defined round trip time for a ping
Check the status of the name servers and resolve the
problem with the name servers. currentrtt
The current round trip time for a ping
FKX513I NAME SERVER ACCESS
THRESHOLD EXCEEDED (errors System action
ERRORS IN interval), A NAME
SERVER MAY BE DOWN AON/TCP continues active monitoring and does not
process failures. AON/TCP updates the Dynamic
Explanation Display Facility (DDF).
You exceeded the threshold for failed attempts at Operator response

accessing a name server. The specified number of
failures occurred over the specified interval. You If you cannot resolve the problem with slow traffic,
cannot access the resource by its IP address or host notify your system programmer.
name. The threshold counter for name server failures
is defined in the LSTHRESH NAMESERVER statement System programmer response
in the control file.
Follow local procedures for resolving problems with
Message Variables slow traffic.
errors FKX516I restype resname ON servicept
The threshold of allowable access errors for the currentlost% LOST PACKETS
name server EXCEEDS PERFORMANCE
interval THRESHOLD OF definedlost%
The time period during which the errors registered
Explanation
Operator response
During an active monitoring cycle, AON/TCP uses ping
Check the status of the name servers and notify your statistics to monitor the availability of a resource. The
system programmer. percentage of packets lost during a ping from the
specified resource exceeded the percentage of lost
System programmer response packets for the resource defined in the PKTLOSS
parameter in the ACTMON statement in the control
Check the status of the name servers and resolve the file.
problem with the name servers.
Message Variables
FKX515I restype resname ON servicept
restype
PING ROUND TRIP TIME OF
currentrtt MS EXCEEDS
PERFORMANCE THRESHOLD OF resname
definedrtt MS The name of the resource
servicept
Explanation The name of the NetView for AIX service point
During an active monitoring cycle, AON/TCP uses ping definedlost
statistics to monitor the availability of a resource. The The percentage of allowable lost packets for a
time it took for a ping to complete a round trip from ping, which is defined in the control file
the specified resource exceeded the time defined for currentlost
the resource in the PINGRTT parameter of the The current percentage of lost packets for a ping
ACTMON statement in the control file.
Message Variables
restype

AON/TCP continues active monitoring and does not If you are not using the AONTCP component for
start failure processing. AON/TCP updates the automation, remove the AONTCP tower from the
Dynamic Display Facility (DDF). CNMSTYLE member in the DSIPARM data set.
FKX530I NO COMMANDS FOUND FOR THIS
Operator response RESOURCE TYPE
Follow local procedures for resolving problems with
slow traffic. If you cannot resolve the problems with Explanation
slow traffic, notify your system programmer.
There are no commands defined for the selected
resource or resource type.
Follow local procedures for resolving problems with System action
slow traffic.
The FKXK2740 panel is not displayed.
FKX518I Cannot start IPMGT because the
FKX611I SESSION info HAS BEEN DROPPED
POLICY is not loaded
Explanation
Explanation
The DROP command was issued for this resource and
IPMGT initialization cannot continue because the
a positive response was returned.
CNMPOLCY file is not loaded.
Message Variables
System action info
IPMGT initialization ends. For TCP/IP connections, info contains the session
number that was dropped.
Operator response For DVIPA connections, info contains an address
containing four segments, separated by periods,
defined as follows:
System programmer response DVIPAAddress.DVIPAPORT.

ClientAddress.ClientPort
Determine why the policy file is not loaded. If the
problem persists, contact IBM Software Support. FKX612I SESSION info COULD NOT BE
FKX519I AONTCP TOWER ACTIVE. IPMGT DROPPED — COULD NOT BE
INITIALIZATION TERMINATED FOUND
While attempting to initialize the IPMGT function, the The DROP command was issued for this resource, and
AONTCP tower was found to be active in the the session id was not found by NETSTAT.
CNMSTYLE member. If you are already using the AON Message Variables
component, you do not need to activate the IPMGT
tower. info
For TCP/IP connections, info contains the session
number that was dropped.
System action
For DVIPA connections, info contains an address
IPMGT initialization ends. containing four segments, separated by periods,
defined as follows:
Operator response
DVIPAAddress.DVIPAPORT.
Notify your system programmer. ClientAddress.ClientPort

Operator response DVIPAAddress.DVIPAPORT.
ClientAddress.ClientPort
Verify that the session no longer exists. If the session
is shown as active, but does not drop, notify your
system programmer. Operator response
Verify that AON is properly communicating with the System programmer response
TCP/IP stack. If the problem persists, contact IBM
Software Support. Check that the NetView system user is defined in the
Obey file for the TCP/IP stack which the DROP
FKX613I SESSION info COULD NOT BE command is issued, or your SAF product file. See the
DROPPED — ERROR UNKNOWN IBM Z NetView Command Reference Volume 1 (A-N) or
the NetView online help for details on identifying
Explanation NetView to TCP/IP. If the problem persists, contact
The DROP command was issued for this resource and
an undetermined problem occurred. FKX615I CONNECTION DOES NOT EXIST
Message Variables
Explanation
info
For TCP/IP connections, info contains the session You issued a command, but the connection does not
number that was dropped. exist, was recently dropped, or ended.
For DVIPA connections, info contains an address System action

containing four segments, separated by periods,
defined as follows: The command fails.
DVIPAAddress.DVIPAPORT. FKX621I NO SERVER DEFINED FOR

ClientAddress.ClientPort SERVICE POINT spnode sp
Notify your system programmer. You issued a command to a service point, but no
server was found in the AON configuration file.
Verify that AON is properly communicating with the spnode
TCP/IP stack. Check for any TCP/IP error messages The NetView domain of the service point.
that might have been issued. If the problem persists, sp
contact IBM Software Support. The service point name for which the command is
FKX614I SESSION info COULD NOT BE being attempted.
DROPPED — NOT AUTHORIZED The command ends.

The DROP command was issued for this resource and Notify your system programmer.
the TSO server user ID is not defined in the Obey file
for the TCP/IP stack or your SAF product file. System programmer response
Message Variables Check the AON configuration file TCP390 entry for the
info service point. Add the SERVER or UNIXSERV
For TCP/IP connections, info contains the session parameter if it is not specified. If either parameter is
number that was dropped. specified, contact IBM Software Support.
For DVIPA connections, info contains an address FKX622I NO ACTIVE TSO SERVERS FOR
containing four segments, separated by periods, SERVICE POINT sp
defined as follows:

Explanation sp
The service point name for which the command is
You tried to issue a TSO command to a service
being attempted.
point :mv.sp:emv. and no TSO Server jobs were found
active.
System action
Message Variables
The command ends.
sp
The service point name for which the command is
Operator response
being attempted. This is an optional value.
System action
The command ends.
Check the AON Configuration file TCP390 entry for the
Operator response service point. Add the appropriate DROP parameter if
it is not coded. If it is, contact IBM Software Support.
FKX625I DROP PROCEDURE module_name
COULD NOT BE FOUND FOR sp
Reinitialize the TSO Server jobs. If the problem Explanation
A DROP procedure was defined on the IPTH3270
FKX623I NO DATACOL PROCEDURE definition in the configuration file for this service point,
DEFINED FOR SERVICE POINT sp but it was not found in DSICLD.
Message Variables
Explanation
module_name
No DATACOL parameter was found on the TCP390
The name of the procedure that was defined in the
statement for this service point.
configuration file.
Message Variables sp
sp The service point name for which the command is
The service point name for which the command is being attempted.
being attempted.
System action
System action The command ends.
The command ends.
Operator response
System programmer response Check the AON Configuration file TCP390 entry for the
Check the AON Configuration file TCP390 entry for the service point. Correct the DROP parameter to use the
service point. Add the appropriate DATACOL appropriate procedure name. If it is, contact IBM
parameter if it is not coded. If it is, contact IBM Software Support.
Software Support. FKX651I THE DATA REQUEST request IS
FKX624I NO DROP PROCEDURE DEFINED NOT SUPPORTED
FOR SERVICE POINT sp
Explanation
Explanation A data collection request was issued and the value of
No DROP parameter was found on the TCP390 the Request field is not supported by the SNMPView
statement for this service point. data collector routine.

request System action
The value of the data collection request submitted.
The command ends.
Operator response
If sessions exist, and reissuing the command gives the
same results, contact IBM Software Support.
FKX681I NO IP ADDRESS IS FOUND FOR
Correct the name of the data collection request — INTERFACE ifno ON RESOURCE
ensure that the name is in all upper case. If the resname
problem persists, contact IBM Software Support.
FKX670I SET REQUEST SUCCESSFUL Explanation
A request was issued to display the list of connections
Explanation for the specified interface on a resource, but there is
An SNMPView SNMP SET request was issued and a no IP address associated with the selected interface.
positive result was returned. SNMP needs an IP address to collect connection data.
Message Variables
System action
ifno
The command ends. The interface number requested
FKX671I SET REQUEST FAILED resname
The name of the TCP/IP resource requested
Explanation
System action
An SNMPView SNMP SET request was issued and
detected an authorization failure. The command ends.
FKX682I FUNCTION NOT SUPPORTED FOR
System action z/OS release
The command ends.
Explanation
Operator response A request was issued that is not supported by your
release of z/OS.
Message Variables
System programmer response release
Check the operator's authorization to issue an SNMP The release of z/OS you are currently using.
SET for this resource. If the problem persists, contact
IBM Software Support. System action
FKX680I NO TCP CONNECTIONS FOUND The command ends.
FOR INTERFACE ifno ON
FKX701I THE CURRENT STATUS OF restype
RESOURCE resname
resname IS resstat
Explanation
Explanation
A request was issued to display the list of connections
Active Monitoring has found the status of the named
for the specified interface on a resource, and
resource to be either DEGRADED, THRESH, or
SNMPView has previously determined that there are
NOSNMP.
no sessions for this interface.
Message Variables
Message Variables
restype
ifno
The resource type of the resource.
The interface number requested
resname
resname
The ALIAS name of the resource.
The name of the TCP/IP resource requested

resstat Explanation
The status of the resource, which is either
While a ping or service command was running on the
DEGRADED, THRESH, or NOSNMP:
specified service point, the specified operator
DEGRADED canceled the run command (RUNCMD) sent to the
One or more interfaces on this resource is service point.
inactive.
Message Variables
THRESH
One or more of the MIBs requested to be restype
tested in the control file has exceeded the The type of the resource
defined threshold. resname
NOSNMP The name of the resource on the NetView for AIX
The resource was defined to use SNMP to service point
collect status but SNMP did not respond to the operator
request. However, active monitoring was able The name of the operator who canceled the
to successfully PING the resource. command
command
System action The name of the command canceled by the
Monitoring continues. operator
Use TCP/390 Resource Manager to determine if there The command on the RUNCMD stops.
are inactive interfaces. FKX753I NO COMPONENT SERVICE POINTS
DEFINED - AON TCPIP
System programmer response COMPONENT CANNOT FUNCTION
For NOSNMP, determine if SNMP is supported for the
resource and is active. If SNMP is not supported, Explanation
change the active monitoring definitions to an You tried to process an alert or initialize AON/TCP, but
appropriate method. If the status reported is incorrect, the specified TCP/IP component is not defined in the
contact IBM Software Support. control file.
FKX702I THE CURRENT STATUS OF restype Message Variables
resname IS NORMAL
component
The name of the TCP/IP component
Explanation
Active Monitoring has found that the status of the Operator response
named resource has changed from either DEGRADED,
THRESH, or NOSNMP to NORMAL. Notify your system programmer.

restype Define the NetView for AIX service points in the
The resource type of the resource control file.
resname
The ALIAS name of the resource FKX755I restype resname NOT ACTIVE -
RECEIVED MESSAGE number
SENSE CODE sensecode
System action
Monitoring continues. Explanation
FKX752I RUNCMD TO restype resname You sent a run command (RUNCMD) to the specified
CANCELED BY OPERATOR resource on the specified service point, but the
operator-COMMAND command resource is not active.
FAILED
Message Variables

restype • Source IP Address
The type of the resource • Source Port
resname •
The name of the resource on the NetView for AIX
service point •
number The Source IP Address (LADDR) and Destination IP
The message ID from the RUNCMD sent to the Address (RADDR) must be a single IP address and
service point cannot be an asterisk (*). The Source Port (LPORT) and
Destination Port (RPORT) must contain a single port
sensecode
number and cannot be an asterisk (*). The TCP/IP
The sense code information from the RUNCMD
Stack name (TCPNAME) must be specified and cannot
be an asterisk (*).
System action
Message Variables
AON/TCP stops processing the function.
parmname
The name of the parameter which was not valid
Operator response
Note the message ID and sense code information, and System action
run first level problem determination on the service
point. If problems persist, notify your system The command ends.
programmer.
Operator response
System programmer response Retry the command with the correct values.
Note the error information, then go to the workstation
and determine why the service point is failing to System programmer response
process RUNCMDs.
If the values specified are correct and the error
FKX901I INCORRECT VALUE DETECTED. persists, contact IBM Software Support.
PRESS PF1 FOR HELP
FKX903I UNABLE TO SUMMARIZE THE
SESSION REPORT
Explanation
One or more values specified for an SNMPView is not Explanation
correct.
The FKXETRS3 command did not find valid data in the
IP Trace Session Report.
System action
The command ends.
Operator response
Use the help information to determine the valid values System programmer response
for setting the failing requests.
System programmer response FKX904I PROTOCOL protocol IS NOT

SUPPORTED FOR ANALYSIS
If the value to be set is within the accepted range,
Explanation
FKX902I REQUIRED PARAMETER
The protocol passed to packet trace analysis is not
parmname IS INVALID
supported by this function.
Explanation: One of these required parameters does protocol

not contain valid data: The protocol type that is requested. Valid
protocols options are: (ALL), TCP, UDP, and ICMP.
• Destination IP Address
• Destination Port

System action FKX907I UNABLE TO DETERMINE THE
CONNECTION ID FOR THIS
The command ends.
SESSION
Operator response
Explanation
Retry the command with the correct values.
A problem occurred while trying to get the connection
ID for the selected session.
If a value was specified and the error persists, contact System action
The command ends.
FKX905I MULTIPLE PROTOCOL SELECTION
ONLY SUPPORTED FOR ANALYSIS Operator response
Explanation
You selected multiple protocols from the list and System programmer response
requested View Packets or Extended Options. These
functions do not support a multiple selection for Use the TCPCONN or IPSTAT command to check the
protocol. Selecting multiple protocols (any status of the requested connection.
combination of TCP, UDP, and ICMP) is only supported FKX910I SERVICE POINT NAME SET.
by the Analysis function. PRESS ENTER TO CONTINUE

The command ends. The name of the service point is set to issue pings.

Retry the command with the correct values. Make other changes and press Enter to continue.
System programmer response FKX911I UNABLE TO FIND SERVICE POINT

FOR NODE resname
FKX906I CONNECTION NOT ACTIVE Explanation
You entered the name of the specified resource on the
Explanation Ping a Service Point panel without specifying the name
of a service point. AON/TCP searched each service
You selected a connection to drop, but no connection
point for the resource, but the search failed. The
ID was found for that connection. The connection
resource might not be accessible.
information, IP addresses, and ports are in error, or
the connection has already terminated. Message Variables
resname
System action The name of the NetView for AIX resource
The command ends.
Operator response
Operator response Verify that the spelling of the resource name in the
If the connection information is incorrect, retry the control file is correct. If the resource name is spelled
command with the correct parameters. incorrectly, select another service point by typing ? in
the entry field for service point and pressing Enter.
If the connection parameters are correct and you are
sure that the connection is still active, contact IBM Verify the resource entry in the AON/TCP control file. If
Software Support. the resource entry is not in the control file, add it.
Otherwise, initialize AON/TCP again by typing AON
1.8.3.

FKX912I ERROR ISSUING RUNCMD TO Operator response
SERVICE POINT servicept Notify your system programmer.
RECEIVED rc

Explanation
Check the connection between NetView and the
You sent a run command (RUNCMD) to the specified
TCP/IP Service point. To check the error codes, issue
service point but the command failed. the HELP PIPE TSO or HELP PIPE UNIX command. The
Message Variables command issued depends upon whether you are using
a TSO or UNIX service point. If the problem persists,
servicept contact IBM Software Support.
rc FKX915I INCORRECT MIB VARIABLE
The return code from the RUNCMD FORMAT. ONE VARIABLE PER
LINE
Operator response
Explanation
Note the return code from the RUNCMD. If RC=1, the
service point is not active and the PING command More than one entry was coded on a MIB variable line
received no response. If RC=5, the service point is in the panel. Only a single entry per-line is valid.
active but is not responding. Notify your system
programmer to correct the problem with the service System action
point. The incorrect value is displayed in red.

Go to the service point and correct the problem. Correct the entry and issue the command again.
FKX913I ENTER A REMOTE COMMAND FKX916I NO VALUE SPECIFIED.
You must enter a command to send to the NetView for Using the SET command option, a MIB variable name
AIX service point. was entered, but no corresponding value was entered.

Type a command and press Enter. The incorrect line is displayed in red.
FKX914I ERROR ISSUING COMMAND TO
SERVICE POINT sp:operid Operator response
RECEIVED error
Correct the entry and issue the command again.
Explanation FKX917I NO VARIABLE NAME SPECIFIED

A TCP/IP command was issued to a service point and a
non-zero return code was received from the Explanation
command. This usually indicates a loss of Using the SET command option, a value was entered,
communications to the MVS TCP/IP service point. but no corresponding MIB variable name was entered.
Message Variables
System action
sp:operid
The service point to which the command was The incorrect line is displayed in red.
issued and the automation operator that issued
the command Operator response
error Correct the entry and issue the command again.
The error return code received from the command
FKX918I NO PACKETS MEET THE
REQUESTED CRITERIA

Explanation FKX931I NO INDEX MIB DEFINED FOR
TABLE GROUP group
The requested filters for the PKTS QUERY command
did not return packet data. The trace data might have
been purged or overwritten by newer packets in the Explanation
NetView PKTS dataspace. A TABLE type group was requested, but no index
variable is defined for this group in FKXSNMP.
Operator response
Message Variables
Validate that you requested the correct interface and
group
that the filters that you specified are correct. Refresh
The group name defined in the FKXSNMP file
the data and retry the operation.
FKX919I UNABLE TO ACCESS PACKETS System action
FROM REMOTE DOMAIN -
domain_name EZLERGWY RC = The command ends.
return_code
Operator response
Explanation Correct the entry in the FKXSNMP file and issue the
The FKXETRS2 command was unable to get the command again.
requested packet data from a remote host.
Message Variables
domain_name
The NetView domain to which the FKXETRS2 FKX932I THE REQUESTED GROUP group
command was sent. DOES NOT EXIST IN THE
return_code FKXSNMP FILE
The return code from the EZLERGWY call to the
remote host. The following return codes can be Explanation
returned:
A group name was requested, but there is no entry for
-1 this group in the FKXSNMP file.
SIGNAL ON FAILURE
Message Variables
-5
SIGNAL ON HALT group
The group name defined in the FKXSNMP file
00
EZLERGWY completed successfully
System action
04
Parameter missing or not valid The command ends.
05
Wait time expired Operator response
07 Add an entry in the FKXSNMP file for this group and
NOVALUE variable found issue the command again.
08
REXX syntax failure System programmer response
12 If the problem persists, contact IBM Software Support.
Command or Pipe command failure
FKX933I INVALID GROUP DEFINITION
group IN FKXSNMP FILE
Operator response
Correct the cause for the EZLERGWY return code and Explanation
submit the request again.
Group is incorrectly defined in FKXSNMP. Possible
errors include a group name containing more than 15
System programmer response characters, a group name containing more than one
If the problem persists, contact IBM Software Support. word, or a lower case keyword GROUP.

Message Variables field
group THRESH
The group name defined in FKXSNMP file The threshold value specified.
OPERATOR
Operator response The operation symbol.
Correct the entry in the FKXSNMP file and issue the MIBNAME
command again. The name of the MIB variable.
resname
System programmer response The name of the TCP/IP resource.
If the problem persists, contact IBM Software Support. mibnum
The MIBVAR number as listed in the AON
FKX934I DUPLICATED GROUP NAME group Configuration file of the incorrect entry.
IN FKXSNMP FILE
System action
Explanation
The variable is ignored.
Group name cannot be duplicated.
group Correct the definition in the AON Configuration file. If
The group name defined in the FKXSNMP file the problem persists, contact IBM Software Support.
FKX942I NO VALID SNMPMIBS FOUND FOR
Operator response RESOURCE resname
Correct the entry in the FKXSNMP file and issue the
command again. Explanation
None of the MIBVAR entries for this resource are valid.
Message Variables
resname
FKX940I INCOMPATIBLE OPTION opt The name of the TCP/IP resource.
SPECIFIED FOR THIS RESOURCE.
System action
Explanation
Threshold Polling for this resource is not performed.
You issued a TCP/IP command that is not supported
by the target service point.
Operator response
Message Variables
Contact your System Programmer.
opt
The AON automation option or component that System programmer response
communicates with the target service point.
Correct the definition in the AON Configuration file. If
the problem persists, contact IBM Software Support.
Operator response
FKX950E INSUFFICIENT INFORMATION TO
Specify a different resource or service point and enter
the command again. ACTIVELY MONITOR THIS
RESOURCE
FKX941I INCORRECT field SPECIFIED FOR
RESOURCE resname SNMPMIB Explanation
mibnum.
There is insufficient information defined in the current
control file entry to start monitoring for this resource.
Explanation
An error was found in the "field" in the MIBVAR System action
numbered "mibnum" for TCP/IP resource "resname".
The request to start active monitoring for this resource
Message Variables fails.

Operator response FKX954E RESNAME resname ALREADY IN
USE
For IPPORT resources each of the following fields are
required: PROTOCOL, TCPNAME, and PORT.
Explanation
FKX951E KEYWORDS FROM OTHER
CONTROL FILE ENTRIES CANNOT The resname you specified or are attempting to add is
BE DELETED already in use.
Message Variables
Explanation
resname
The control file keyword value pair cannot be deleted The resname specified that is already in use
because it is not defined to the selected control file
entry. System action
The request fails.
System action
The delete request fails. Operator response
Specify a unique resname or delete the duplicate
Operator response
resname and retry the current operation.
The current keyword value pair can be changed but
FKX960I NO SERVICE POINTS FOUND FOR
not deleted.
SESSION MONITORING
FKX952I THE NEWLY ADDED FIELD IS
SHOWN BUT MUST BE SUBMITTED Explanation
TO TAKE EFFECT
FKXE2200 (Session Monitoring) was unable to find
TCP390 IPTN3270.
Explanation
The keyword value pair was added and is now System action
displayed with the others for this control file entry.
However, you must submit the changes for all the The command ends.
fields for this field to be added in storage. FKX961I UNABLE TO RESOLVE AN IP
ADDRESS FOR HOST FVT06T
Operator response
Press F4 to submit the control file changes including Explanation
the addition of any newly added keyword value pairs. A host name was entered as a search parmeter.
FKX953E ONE OF THE FOLLOWING IS NetView was unable to determine an IP address
REQUIRED: keywords associated with this host. Session Monitoring requires
an IP address when searching a TN3270 server for
sessions.
Explanation
The action requested requires at least one of the listed System action
keywords or parameters be properly specified.
The command ends.
Message Variables
keywords Operator response
One or more keywords or parameters. At least one
Check that the host name is valid. If the problem
must be supplied.
persists contact your system programmer.
System action
The request fails.
If the host name is defined correctly in your network,
Operator response
FKX962I WILDCARDS ARE NOT
Supply one of the keywords or parameters listed with SUPPORTED FOR TN3270 SERVER
a value. sp

Explanation FKX979E UNIXSERV=YES IS REQUIRED ON
TCP390 stackname STATEMENT
You entered a wild card character (*) in the search
IN POLICY DEFINITION
field. Session Monitoring does not support wild card
addresses for TN3270 servers.
Explanation
Message Variables
During AON/TCP initialization, AON determined that
sp there was a TCP390 statement for the local domain
The name of the TN3270 server requested. that did not contain a UNIXSERV=YES parameter. This
parameter is required.
System action
AON/TCP initialization stops.
Operator response
Retry the command with a valid IP address or host Operator response
name. Notify the system programmer.

If the problem persists, contact IBM Software Support. Add UNIXSERV=YES to the TCP390 statement for the
FKX963I NO SERVICE POINT DEFINED FOR local domain and reinitialize AON.
TN3270 SERVER sp FKX980I UNIX SERVICES FUNCTION
module_ name WAS NOT FOUND
Explanation
No service point is found in the IPTN3270 Explanation
Configuration file entry for this TN3270 server. A call was made to use a UNIX System Services
Message Variables function that is supplied with the NetView program,
but the module was not found in any UNIX System
sp Services searched directory.
The name of the TN3270 server requested.
Message Variables
System action module_name
The name of the called UNIX System Services
The command ends.
function that is supplied with the NetView
program.
Operator response
Contact your system programmer. System action
The command ends.
Add an SP parameter on the IPTN3270 statement for Operator response
this TN3270 server. If the problem persists, contact
Tivoli IBM Software Support.
FKX970I NO SESSIONS MATCH DEFINED System programmer response
FILTER CRITERIA
Install the module in a UNIX System Services
searched directory. If the problem persists, contact
Explanation
Configured filter criteria has resulted in all active
FKX981I UNABLE TO RUN UNIX SERVICES
sessions being filtered from your display.
FUNCTION module_ name
Operator response
Explanation
Verify that your filters and the AND or OR operands are
A call was made to use a UNIX System Services
properly defined.
function that is provided with the NetView program,

but the permission bits for the module refused Operator response
execution.
Try the command again. If the problem persists,
Message Variables contact your system programmer.
module_ name
The name of the called UNIX System Services System programmer response
function that is supplied with the NetView Adjust the amount of time the NetView Pipe waits for a
program. response by changing the ENVIRON TIMEOUT SNMP
value.
System action
FKX984I TIMEOUT RECEIVED FROM SNMP
The command ends. REQUEST

Contact your system programmer. An SNMP request was issued and no data was
received except this SNMP Timeout response. This
System programmer response timeout indicates that the IP resource from which the
data was requested does not have SNMP support
You need to resolve the permission bits for this active.
module.
FKX982I UNIX SERVICES ERROR System action
RECEIVED: message_ text
The command ends.
Explanation
Operator response
A call was made to use a UNIX System Services
Retry the command, and verify that the resource has
function that is supplied with the NetView program,
SNMP support active.
and an error was returned from UNIX System Services.
message_ text If the problem persists, contact IBM Software Support.
The text of the error message returned from UNIX
System Service. FKX985I TCP/IP IS UNABLE TO RESOLVE
HOSTNAME resname
System action
Explanation
The command ends.
NetView was not able to resolve the host name.
Contact your system programmer. resname
The host name of the IP resource
System action
Resolve the problem that is detailed in the message.
The command ends.
FKX983I NETVIEW TIMEOUT BEFORE
RESPONSE RECEIVED FROM
TCP/IP Operator response
Verify that the host name is valid, and retry the
A SNMP request was sent to UNIX System Services,
but the NetView timed out before any data was System programmer response
returned from UNIX System Services TCP/IP. Check your TCP/IP domain name server definitions. If
the problem persists, contact IBM Software Support.
System action
FKX986I UNIX SERVER IS NOT AVAILABLE,
The command ends. PPI ERROR 26 RECEIVED

Explanation FKX988I ERRORS RECEIVED FROM SNMP
REQUEST. HIT F10 FOR
NetView was unable to send the TCP/IP command to
MESSAGES
UNIX System Services.
Explanation
System action
An SNMP request was issued, and in addition to or
The command ends.
instead of TCP/IP data, TCP/IP messages were
returned. Select F10 from the screen, to see the
Operator response messages.
Check that the NetView PPI is initialized, and that the
UNIX server is active. System action
The command is continued.
If the problem persists, contact IBM Software Support. Operator response
FKX987I UNIX AUTHORIZATION FAILED, Review the message to see if further action is required.
UNIX ERROR -11 RECEIVED
FKX989I NO CONNECTIONS FOUND FOR
THIS INTERFACE
Explanation
A TCP/IP command request was issued and a UNIX Explanation
System Services return code -11 error was returned.
This response indicates that the operator is not A request was issued to display the list of connections
properly defined to use UNIX System Services. for the specified interface on a resource, and
SNMPView cannot find any connections for that
interface.
System action
The command ends.
Operator response
Contact System Programming. System programmer response
If sessions exist, and re-issuing the command gives
System programmer response the same results, contact IBM Software Support.
Define NetView to UNIX System Services.

Chapter 10. FLB Prefix Messages
FLB prefix messages provide error descriptions and information about SNA Topology Manager.
FLB000I MESSAGE msgnum WAS ISSUED System action
BUT THIS MESSAGE DOES NOT The SNA topology manager is ended.
EXIST IN MESSAGE TABLE
DSIMDMFB
Operator response
The message processing routines were asked to issue
a message which is not found in message table System programmer response
DSIMDMFB. This message is issued because of a failure to load the
Message Variables specified module. This is usually because NetView or
VTAM has not been installed properly, or VTAM is not
msgnum at the correct level. If the module name begins with
The number of the message that cannot be found FLB, verify that NetView has been installed properly. If
the module name begins with ACY, verify that VTAM
System action 4.3 or later has been installed properly and includes
CMIP Services support.
The request to issue the message is cancelled.
FLB300W SNA TOPOLOGY MANAGER IS
Operator response REINITIALIZING

Explanation
System programmer response The SNA topology manager detected an error that
forced re-initialization.
Verify that message table DSIMDMFB exists and is
properly installed. If it is, record the message number
System action
and contact IBM Software Support.
The SNA topology manager stops all command
FLB010E FLBTOPO RECEIVED RETURN processing and reinitializes.
CODE retcode, ABEND CODE
abncode, REASON CODE rsncode,
ATTEMPTING TO LOAD MODULE Operator response
'module' This message is issued in combination with FLB481E
or FLB684E. Either RODM or CMIP Services ended.
Explanation Restart RODM or CMIP Services, depending upon
which other message was received.
The SNA topology manager (FLBTOPO) received an
error from the DSILOD macro while attempting to load
the specified module. System programmer response
Message Variables Determine why VTAM CMIP Services or RODM ended.
retcode FLB301E RODM ERROR ENCOUNTERED ON

The return code from the DSILOD macro RODM FUNCTION type OBJECTID
X'objectid' RETURN CODE rc
abncode
REASON CODE xx
The abend code returned from the DSILOD macro
rsncode Explanation
The reason code returned from the DSILOD macro
The SNA topology manager received an error on a
module
RODM request.
The module which was being loaded
Message Variables

type Operator response
The function ID of the failing RODM request
Report the failure to the system programmer.
objectid
The object ID of the resource in hexadecimal
rc
If this message is not preceded by message FLB301E,
The RODM return code in decimal
the problem is the result of an SNA topology manager
xx internal processing failure. Contact IBM Software
The RODM reason code in decimal Support.
If this message is preceded by message FLB301E, the
System action
problem was caused by a RODM function. Contacting
The SNA topology manager command that IBM Software Support might be required; see message
encountered the error fails. If the ERRLIMIT value is FLB301E.
greater than zero, the command is retried the number
FLB303W MONITORING OF SNA type FROM
of times specified by the ERRLIMIT value.
RESOURCE resource IS BEING
RETRIED
Operator response
Report this problem to the system programmer. Explanation
A command that previously failed, because of an error
System programmer response from SNA topology manager or RODM, is being retried.
Using the information in the message and the IBM Z Message Variables
NetView Troubleshooting Guide, determine why the
failure occurred. This might indicate a problem type
requiring you to contact IBM Software Support, or a The type of the failed monitor command; possible
problem introduced by user-written methods values are:
executing in the RODM address space. • NETWORK TOPOLOGY
FLB302E MONITORING OF SNA type FROM • LOCAL TOPOLOGY
RESOURCE resource FAILED DUE • LU COLLECTION
TO SNA TOPOLOGY MANAGER OR
RODM PROCESSING ERROR resource
The name of the resource from which the type of
Explanation monitoring is to be performed
The SNA topology manager encountered a non- System action

network related problem forcing the specified
operation to fail. The command is being retried. The total number of
retries is determined by the error retry limit value set
Message Variables by the TOPOSNA SETDEFS,ERRLIMIT=xxx command.
type
FLB304E MONITORING OF SNA type FROM
The type of monitor command that failed; possible
RESOURCE resource FAILED AND
values are:
HAS EXCEEDED THE ERROR
• NETWORK TOPOLOGY RETRY LIMIT
• LOCAL TOPOLOGY
• LU COLLECTION Explanation
resource A command that previously failed, because of an error

The name of the resource from which the type of from SNA topology manager or RODM, has failed again
monitoring was being performed. and the error retry limit has been exceeded. The error
retry limit value is set by the TOPOSNA
SETDEFS,ERRLIMIT=xxx command.
System action
Message Variables
The command is retried if the error limit value (set by
the TOPOSNA SETDEFS,ERRLIMIT=xxx command) is type
greater than zero. If the error limit value was specified The failing monitor command type; possible values
as NORETRY or zero, the command is not retried. are:

• NETWORK TOPOLOGY System programmer response
• LOCAL TOPOLOGY See the IBM Z NetView Troubleshooting Guide for
• LU COLLECTION possible causes of the storage shortage.
resource If necessary, see the IBM Z NetView SNA Topology

The name of the resource from which the type of Manager Implementation Guide.
monitoring was being performed See the IBM Z NetView Tuning Guide for more
information about how to increase NetView storage.
System action
FLB400E TOPOSNA STOP COMMAND IS
The command is no longer retried. IGNORED BECAUSE SNA
NETWORK TOPOLOGY OF NODE
Operator response nodename IS NOT BEING
MONITORED
Report the failure to the system programmer.
Explanation
The TOPOSNA STOP command was ignored by the
If this message is not preceded by message FLB301E, SNA topology manager because the SNA topology
the problem is the result of an SNA topology manager manager is not monitoring the network topology of the
internal processing failure. Contact IBM Software node. The probable cause of the problem is one of the
Support. following:
If this message is preceded by message FLB301E, the • No one started monitoring the SNA topology
problem was caused by a RODM function. Contacting manager of the node.
IBM Software Support might be required; see message
FLB301E. • Another operator already stopped monitoring the
SNA network topology of the node.
FLB305E MONITORING OF SNA type FROM
• The operator specified an incorrect node name on
RESOURCE resource FAILED DUE
the TOPOSNA STOP command.
TO STORAGE SHORTAGE
Message Variables
Explanation nodename
A storage request cannot be satisfied. Message The control point name of the agent node
FLB419E will precede this message.
Operator response
Message Variables
Verify the name of the node specified on the TOPOSNA
type
STOP command is correct and issue the command
The failing monitor command type; possible values
again.
are:
FLB401E TOPOSNA STOP COMMAND IS
• NETWORK TOPOLOGY
IGNORED BECAUSE SNA LOCAL
• LOCAL TOPOLOGY TOPOLOGY OF NODE nodename IS
• LU COLLECTION NOT BEING MONITORED
resource
The name of the resource from which the type of Explanation
monitoring was being performed The TOPOSNA STOP command was ignored by the
SNA topology manager because the SNA topology
System action manager is not monitoring the local topology of the
node. The probable cause of the problem is one of the
The command fails and is not retried.
following:
Operator response • No one started monitoring the SNA local topology of

the node.
Determine whether you received message BNH16I,
• Another operator already stopped monitoring the
SNA local topology of the node.
so, notify your system programmer.
Chapter 10. FLB Prefix Messages 523

• The operator specified an incorrect node name on the TOPOSNA MONITOR operator command expires. If
the TOPOSNA STOP command. the topology manager is stopped and warm-started, it
restarts the monitoring automatically.
Message Variables
Message Variables
nodename
The control point name of the agent node nodename
The control point name of the agent node
Operator response
System action
Check the name of the node specified on the
TOPOSNA STOP command. If the name is incorrect, Monitoring is started.
issue the command again with the correct name.
FLB402I SNA TOPOLOGY MANAGER HAS Operator response
BEGUN WARM-START Look for message FLB406I to indicate that the initial
PROCESSING transfer of topology data has completed.
FLB404I COMPLETED MONITORING OF
Explanation
SNA NETWORK TOPOLOGY FROM
The SNA topology manager has connected to RODM NODE nodename
and CMIP services and is beginning to process the
information contained in the RODM data cache. The Explanation
topology manager restarts all continuous monitor
operations during warm start. The topology manager The SNA topology manager completed monitoring SNA
uses information in the RODM data cache to determine network topology from the agent node. The initial
which nodes must be monitored. Warm-start transfer of topology data from the agent was
processing occurs when the PURGDAYS keyword in completed, and the monitor time for updates expired.
the FLBSYSD initialization file is specified with a value The monitor time is specified on the MONTIME
greater than zero. The amount of time required to parameter on the TOPOSNA MONITOR command.
warm-start depends on the number of objects that are Message Variables
in RODM.
nodename
Note: If RODM is loaded with checkpoint data, the The control point name of the agent node
topology manager restarts continuous monitoring of
the nodes that were being monitored when the RODM
System action
checkpoint was taken.
Monitoring stop.
System action FLB405W OPERATOR 'operid' STOPPED
The RODM data cache is read and verified. All eligible MONITORING SNA NETWORK
objects in the data cache are purged, according to the TOPOLOGY FROM NODE nodename
PURGDAYS parameter in the initialization file
FLBSYSD. All continuous monitor operations that were Explanation
active when the topology manager was stopped or
when the RODM checkpoint was taken (see note The operator stopped monitoring SNA network
above) are restarted. topology from the agent node by issuing a TOPOSNA
STOP command. Monitoring stops even if the initial
FLB403I REQUESTED MONITORING OF SNA transfer of topology data from the agent node is not
NETWORK TOPOLOGY FROM complete.
NODE nodename
Message Variables
Explanation operid
The name of the operator who issued the
The SNA topology manager sent the agent node a TOPOSNA STOP command
request to monitor its network topology. In response,
nodename
the agent node sends the initial transfer of its topology
data. Following the initial transfer, the agent node
sends updates as they occur. The monitoring
continues until the TOPOSNA STOP operator System action
command is issued or the monitor time specified on Monitoring stop

If you want to resume monitoring network topology, See the error messages in the NetView log and to IBM
issue another TOPOSNA MONITOR command; Z NetView Troubleshooting Guide to diagnose and
otherwise, no response is required. correct the error. Refer also to the system error log at
the agent node to determine whether an agent system
FLB406I INITIAL TRANSFER OF SNA error occurred; if it did, take action to fix the problem
NETWORK TOPOLOGY FROM at the agent node. Restart monitoring the network
NODE nodename IS COMPLETE topology. If necessary, contact IBM Software Support.
Explanation FLB408W MONITORING OF SNA NETWORK

TOPOLOGY FROM NODE nodename
The SNA topology manager started monitoring SNA IS BEING RETRIED
network topology from the agent node, and the agent
node completed the initial transfer of its topology
Explanation
data, and stored topology data in the RODM cache.
The agent node continues to send updates to the The SNA topology manager started monitoring SNA
manager as they occur. network topology from the agent node, but either the
topology manager cannot complete the initial transfer
Message Variables
of the topology data, or it lost communications with
nodename the agent node after the initial transfer was complete.
The control point name of the agent node The error is considered recoverable and retry occurs
immediately. The topology manager will retry until it
System action successfully completes the initial transfer, exceeds
the retry limits for network topology, or encounters an
Monitoring continues until a TOPOSNA STOP unrecoverable error. The retry limits are specified on
command is issued, the time specified on the the TOPOSNA SETDEFS operator command.
MONTIME parameter of the TOPOSNA MONITOR
command expires, or an error occurs that stops the The probable cause of the error is one of the following:
monitoring. • The session from the NetView host to the agent node
FLB407E MONITORING OF SNA NETWORK failed.
TOPOLOGY FROM NODE nodename • The topology agent program has been stopped.
FAILED • The time interval specified on the MAXREPLY
parameter of the NETVIEW DEFAULTS command
Explanation expired before the initial transfer of the topology
data was complete.
The SNA topology manager cannot start the
monitoring of SNA network topology from the agent Message Variables
node, cannot complete the initial transfer of the
nodename
topology data, or has lost communications with the
agent node after the initial transfer was complete. The
error is considered unrecoverable and no retry occurs.
The probable cause of the error is a system error at the System action
agent node. The topology manager begins retrying the task.
Message Variables
Operator response
nodename
The control point name of the agent node See the messages in the NetView log to diagnose the
error. If the error is because the time interval specified
System action on the MAXREPLY parameter of the NETVIEW
DEFAULTS command expired, increase the time
Monitoring is not started and no retry occurs. interval in order to reduce the frequency of this
condition. Otherwise, no action is necessary in
Operator response response to this message. If the topology manager
cannot restart the monitoring, it will issue message
See the messages in the NetView log to diagnose the
FLB407E or FLB462E.
error. If you are unable to fix the problem, notify your
system programmer.

FLB409W MONITORING OF SNA NETWORK Explanation
TOPOLOGY FROM NODE nodename The command processor for the SNA topology
WILL BE RETRIED manager task cannot allocate enough storage to
process the TOPOSNA operator command. The
Explanation probable cause of the error is that the address space
The SNA topology manager cannot start the allocated to NetView is too small.
monitoring of SNA network topology from the agent Message Variables
node. The error is considered recoverable and retry
will begin at the end of the first retry interval for requestparm
network topology. The topology manager will retry The name of the TOPOSNA request parameter
until it successfully completes the initial transfer,
exceeds the retry limits for network topology, or System action
encounters an unrecoverable error. The retry intervals The command is ignored.
and limits are specified on the TOPOSNA SETDEFS
operator command.
Operator response
The probable cause of the error is one of the following:
• A session from the NetView host to the agent node which means the task has reached its storage limit. If
cannot be established, or the session failed and so, notify your system programmer.
cannot be established again.
• The agent node does not have a topology agent System programmer response
installed and running.
• The agent node control point name is incorrect; for possible causes of the storage shortage. If necessary,
example, the name was not typed correctly on the see the IBM Z NetView SNA Topology Manager
TOPOSNA MONITOR operator command. Implementation Guide. For storage estimates, see the
• The agent node is not turned on, or it does not exist IBM Z NetView Tuning Guide.
in the network.
FLB411I TOPOSNA requestparm COMMAND
• The agent node is an end node; end nodes do not COMPLETED SUCCESSFULLY
support requests for network topology.
nodename The SNA topology manager successfully completed
The control point name of the agent node the processing of the TOPOSNA operator command.
Message Variables
System action
requestparm
The topology manager will begin retrying after the The name of the TOPOSNA request parameter
retry interval specified for network topology.
System action
Operator response
The command is completed.
Ensure that the agent node is a network node. If it is,
no action is necessary in response to this message. FLB412E TOPOSNA requestparm COMMAND
However, if the topology manager cannot start the CANNOT BE COMPLETED
monitoring, it will issue message FLB407E or BECAUSE OF AN ERROR
FLB462E. You can attempt to start monitoring network
topology at any time with the TOPOSNA MONITOR Explanation
operator command. Otherwise, the topology manager
The SNA topology manager cannot complete the
will attempt to restart the monitoring at the intervals
processing of the TOPOSNA operator command. This
specified on the NETRETRY parameter of the
message might follow other messages that indicate
TOPOSNA SETDEFS operator command.
the type of error. No further processing of the
FLB410E INSUFFICIENT STORAGE TO command can be done.
PROCESS TOPOSNA requestparm The probable cause of the error is one of the following:
COMMAND

• A RODM error occurred during the processing of a System programmer response
TOPOSNA PURGE or TOPOSNA SETDEFS command.
See the error messages in the NetView log and to the
• A GTF error occurred during the processing of a IBM Z NetView Troubleshooting Guide to diagnose and
TOPOSNA TRACE command. correct the error. If the FLBSYSD member does not
• A system error occurred during the processing of any exist, install it on your system. If the member is
TOPOSNA command. incorrectly formatted or contains incorrect
information, update the member using the correct
Message Variables format or information. IBM Z NetView Installation:
requestparm Getting Started contains installation instructions and
The name of the TOPOSNA request parameter the description of the member format and content. If
necessary, contact IBM Software Support.
System action FLB414E TOPOSNA requestparm COMMAND
The command is ignored. CANNOT BE PROCESSED
BECAUSE OF AN ERROR
Operator response
Explanation
See messages in the NetView log to diagnose the
error. Correct the problem and issue the operator The TOPOSNA operator command cannot be
command again. If you cannot correct the problem, processed because of an internal error condition. A
notify your system programmer. probable cause is that the command processor cannot
send the command to the FLBTOPO autotask.
See the error messages in the NetView log and to IBM requestparm
Z NetView Troubleshooting Guide to diagnose and The name of the TOPOSNA request parameter
correct the error. If necessary, contact IBM Software
Support. System action
FLB413E SNA TOPOLOGY MANAGER The command is ignored.
CANNOT PROCESS OR READ
INITIALIZATION MEMBER Operator response
'FLBSYSD'
This condition might be temporary, so try to issue the
command later. If this condition persists, notify your
Explanation
system programmer.
The SNA topology manager cannot read the FLBSYSD
initialization member in the data set named on the System programmer response
DSIPARM DD statement in the system-start JCL. The
initialization member contains information that is This condition occurs when the command processor is
needed for the topology manager to complete its attempting to send the operator command to the
initialization, such as the RODM name for connecting topology manager. See the error messages in the
to RODM. NetView log and to the IBM Z NetView Troubleshooting
Guide to diagnose and correct the error. If necessary,
The probable cause of the error is one of the following: contact IBM Software Support.
• The topology manager encountered a disk I/O error FLB415W SNA TOPOLOGY MANAGER
when it attempted to read the member.
INITIALIZATION FILE CONTAINS
• The FLBSYSD member does not exist. KEYWORDS 'keyword1' AND
• The FLBSYSD member contains a syntax error or 'keyword2' WITH STRING VALUES
incorrect information. THAT ARE EQUAL
The topology manager stops executing. The SNA topology manager initialization file, FLBSYSD,
includes keywords and associated values expressed
as:
Operator response
Notify your system programmer. KEYWORD="value"

Some of the keywords provide character string values Message Variables
used for identifying capabilities or related elements of
keyword
certain APPN topology objects. The character strings
The keyword, from the FLBSYSD initialization file,
are stored in RODM in the DisplayResourceOtherData
that has no value assigned
field of the corresponding objects.
The topology manager detected that the keywords System action
indicated in the message have character string values
that are the same. The topology manager does not initialize.
Message Variables
Operator response
keyword1
One keyword, from the FLBSYSD initialization file
keyword2 System programmer response
The other keyword, from the FLBSYSD initialization
file Change the initialization file so that the keyword
contains a value.
System action FLB417E SNA TOPOLOGY MANAGER
The topology manager continues, using the keywords INITIALIZATION FILE CONTAINS
and their character string values from the initialization KEYWORDS 'keyword1' AND
file. 'keyword2' WITH PREFIX VALUES
THAT ARE EQUAL
Operator response
Explanation
The SNA topology manager initialization file, FLBSYSD,
as:
Consider changing the initialization file so that the
character strings assigned to the indicated keywords KEYWORD="value"
are not the same.
Some of the keywords provide prefix values used for
FLB416E SNA TOPOLOGY MANAGER distinguishing the displayed names of objects of
INITIALIZATION FILE CONTAINS different classes that have the same name structure.
A KEYWORD 'keyword' WITH A The prefixes are joined to the names of the objects and
NULL VALUE stored in RODM in the DisplayResourceName field.
The topology manager detected that the keywords
Explanation indicated in the message have prefix values that are
The SNA topology manager initialization file, FLBSYSD, the same.
includes keywords and associated values expressed Message Variables
as:
keyword1
KEYWORD="value" One keyword, from the FLBSYSD initialization file
keyword2
Some of the keywords provide character string values The other keyword, from the FLBSYSD initialization
used for identifying capabilities or related elements of file
certain APPN topology objects. The character strings
are stored in RODM in the DisplayResourceOtherData
field of the corresponding objects. Some keywords System action
provide prefix values used for distinguishing the The topology manager does not initialize.
displayed names of objects of different classes that
have the same name structure. The prefixes are joined Operator response
to the names of the objects and stored in RODM in the
DisplayResourceName field. Other keywords are used Contact the system programmer.
to set numeric values used during initialization.
The topology manager detected that the keyword
indicated in the message has no value assigned to it.

System programmer response If necessary, see the IBM Z NetView SNA Topology
Manager Implementation Guide. For storage estimates,
Change the initialization file so that the prefixes
see the IBM Z NetView Tuning Guide.
assigned to the indicated keywords are not the same.
FLB420I REQUESTED MONITORING OF SNA
FLB418I SNA TOPOLOGY MANAGER HAS
LOCAL TOPOLOGY FROM NODE
BEGUN COLD-START
nodename
PROCESSING
Explanation
Explanation
The SNA topology manager sent the agent node a
The SNA topology manager has connected to RODM
request to monitor its local topology. In response, the
and CMIP services. None of the existing APPN
agent node sends the initial transfer of its topology
topology information in RODM is used by the topology
data. When the initial transfer is complete, the
manager. Cold-start processing occurs when the
topology manager issues message FLB423I. Following
PURGDAYS keyword in the FLBSYSD initialization file
the initial transfer, the agent node sends updates as
specifies a value equal to zero. The amount of time
they occur. The monitoring continues until the
required to warm-start depends on the number of
TOPOSNA STOP operator command is issued or the
objects that are in RODM.
monitor time specified on the TOPOSNA MONITOR
operator command expires. If the topology manager is
System action stopped and warm-started, it restarts the monitoring
The RODM data cache is read and verified. All APPN automatically.
topology objects in the data cache are purged. No Message Variables
monitor operations are restarted.
nodename
FLB419E SNA TOPOLOGY MANAGER COULD The control point name of the agent node
NOT ALLOCATE ENOUGH
STORAGE. AMOUNT OF STORAGE System action
ATTEMPTED WAS 'amount'
Monitoring is started.
Explanation
Operator response
The SNA topology manager cannot allocate enough
storage to complete its processing. Look for message FLB423I which indicates that the
initial transfer of data is complete.
Message Variables
FLB421I COMPLETED MONITORING OF
amount
SNA LOCAL TOPOLOGY FROM
The amount of storage (in bytes) that the SNA
NODE nodename
topology manager attempted to allocate. If the
amount of storage is unknown to the SNA topology
manager, 'UNKNOWN' is displayed. Explanation
The SNA topology manager completed monitoring SNA
System action local topology from the agent node. The initial transfer
of topology data from the agent node was completed.
If the storage request occurs during initialization, the
The monitor time for updates has expired. The monitor
SNA topology manager ends. Otherwise, only the
time is specified on the MONTIME parameter on the
command that generated the storage request ends
TOPOSNA MONITOR command.
(the command will not be retried).
Message Variables
Operator response nodename
Determine whether you received message BNH16I, The control point name of the agent node.
so, notify your system programmer. System action
Monitoring is stopped.
FLB422W OPERATOR 'operid' STOPPED
See the IBM Z NetView Troubleshooting Guide for MONITORING SNA LOCAL
possible causes of the storage shortage. TOPOLOGY FROM NODE nodename

Explanation the initial transfer was complete. The error is
considered unrecoverable and no retry occurs. The
The operator stopped monitoring SNA local topology
probable cause of the error is a system error at the
from the agent node by issuing a TOPOSNA STOP
agent node.
command. Monitoring stops even if the initial transfer
of topology data from the agent node is not complete. Message Variables
Message Variables nodename
operid
The name of the operator who issued the
TOPOSNA STOP command System action
nodename Monitoring is not started and no retry occurs.
Operator response
System action See the messages in the NetView log to diagnose the
Monitoring is stopped error. If you are unable to correct the problem, notify
Operator response
If you wish to resume monitoring local topology, issue
another TOPOSNA MONITOR command; otherwise, no See the error messages in the NetView log and to IBM
response is required. Z NetView Troubleshooting Guide to diagnose and
correct the error. Refer also to the system error log at
FLB423I INITIAL TRANSFER OF SNA LOCAL the agent node to determine whether an agent system
TOPOLOGY FROM NODE nodename error occurred; if it did, take action to correct the error
IS COMPLETE at the agent node. Restart monitoring the local
topology. If necessary, contact IBM Software Support.
Explanation
FLB425W MONITORING OF SNA LOCAL
The SNA topology manager started monitoring SNA TOPOLOGY FROM NODE nodename
local topology from the agent node, and the agent IS BEING RETRIED
node completed the initial transfer of its topology
data, and the SNA topology manager has processed Explanation
and stored topology data in the RODM data cache. The
agent node continues to send updates to the manager The SNA topology manager started monitoring SNA
as updates occur. local topology from the agent node, but either it
cannot complete the initial transfer of the topology
Message Variables data, or it lost communications with the agent node
nodename after the initial transfer was complete. The error is
The control point name of the agent node considered recoverable and retry occurs immediately.
The topology manager will retry until it successfully
System action completes the initial transfer, exceeds the retry limits
for local topology, or encounters an unrecoverable
Monitoring continues until a TOPOSNA STOP error. The retry limits are specified on the TOPOSNA
command is issued, the time specified on the SETDEFS operator command.
MONTIME parameter of the TOPOSNA SETDEFS or
TOPOSNA MONITOR command expires, or an error The probable cause of the error is one of the following:
occurs that stops the monitoring. • The session from the NetView host to the agent node
failed.
FLB424E MONITORING OF SNA LOCAL
TOPOLOGY FROM NODE nodename • The topology agent program has been stopped.
FAILED • The time interval specified on the MAXREPLY
parameter of the NETVIEW DEFAULTS command
Explanation expired before the initial transfer of the topology
data was complete.
monitoring of SNA local topology from the agent node, Message Variables
cannot complete the initial transfer of the topology
data, or lost communications with the agent node after

nodename Operator response
No action is necessary in response to this message.
However, if the topology manager cannot restart the
System action monitoring, it will issue message FLB424E or
The topology manager immediately begins retrying. FLB463E. You can attempt to start monitoring local
topology at any time with the TOPOSNA MONITOR
operator command. Otherwise, the topology manager
Operator response
will try to restart the monitoring at the interval
See the messages in the NetView log to diagnose the specified on the LCLRETRY parameter of the TOPOSNA
error. If the error is because the time interval specified SETDEFS operator command.
on the MAXREPLY parameter of the NETVIEW
FLB427E SNA TOPOLOGY MANAGER
interval in order to reduce the frequency of this
A KEYWORD 'keyword' WITH AN
condition. Otherwise, no action is necessary in
INCORRECT VALUE
response to this message. If the topology manager
cannot restart the monitoring, it will issue message
FLB424E or FLB463E. Explanation
FLB426W MONITORING OF SNA LOCAL The SNA topology manager initialization file, FLBSYSD,
TOPOLOGY FROM NODE nodename includes keywords and associated values expressed
WILL BE RETRIED as:
KEYWORD="value"
Explanation
The values are used for initializing certain start-up and
run-time parameters. The value assigned to the
monitoring of SNA local topology from the agent node.
keyword indicated in the message has an incorrect
The error is considered recoverable and retry will
value.
begin at the end of the first retry interval for local
topology. The topology manager will retry until it Message Variables
successfully completes the initial transfer, exceeds
keyword
the retry limits for local topology, or encounters an
The keyword, from the FLBSYSD initialization file,
unrecoverable error. The retry intervals and limits are
that has an incorrect value
specified on the TOPOSNA SETDEFS operator
command.
System action
The topology manager does not initialize.
• A session from the NetView host to the agent node
cannot be established, or the session failed and
Operator response
• The agent node does not have a topology agent Contact the system programmer.
• The agent node control point name is incorrect; for System programmer response
example, the name was not typed correctly on the Change the initialization file so that the value assigned
TOPOSNA MONITOR operator command. to the indicated keyword is correct.
• The agent node is not powered on or it does not exist FLB429E SNA TOPOLOGY MANAGER HAS
in the network. EXHAUSTED THE NUMBER OF
Message Variables RETRIES TO ESTABLISH A
SESSION WITH TASK CNMTAMEL
nodename
Explanation
System action The SNA topology manager has made several attempts
to establish a session with CNNTAMEL. All of these
The topology manager will begin retrying after the attempts have failed. The SNA topology manager will
retry interval specified for local topology. stop retrying.
The probable cause of the error is:

• The CNMTAMEL task has not been activated. 1.3.18.0.0.1843
• There is a storage constraint; the SNA topology 2.1 node
manager cannot allocate a buffer to send to the 1.3.18.0.0.1826
CNMTAMEL task. Interchange node
1.3.18.0.0.1833
System action Migration Data Host
Communication between SNA topology manager and 1.3.18.0.0.1845
the CNMTAMEL task cannot occur. This will prevent T5 Node
the following requests from successfully executing: Message Variables
• Status history of objects owned by SNA topology nodename
manager The control point name of the node that changed
• List the SSCP owners for an object owned by SNA class
topology manager class1
• Locate a logical unit (LU) that is not already created The RODM class name of the existing class
in RODM class2
The RODM class name of the new class
Operator response
rodmobjectid
Activate the CNMTAMEL task in the NetView program. The RODM object ID of the object with the new
class.
FLB430I NODE nodename OF CLASS class1
IS UPGRADED TO CLASS class2
WITH NEW RODM OBJECT ID System action
rodmobjectid The topology manager replaces the existing node
object in RODM with the updated object, preserving
Explanation the links to other objects in RODM.
The node has changed its object class. This change
occurs when the topology manager receives more up- System programmer response
to-date information about an existing node, where the The topology manager does not copy customer-
new information indicates a different object class. For defined fields from the old object to the updated
example: object in RODM. Set these customer-defined fields for
• An agent node first reports an adjacent node as a the new RODM object. See the IBM Z NetView Resource
type 2.1, and later reports it as an end node after Object Data Manager and GMFHS Programmer's Guide.
activating a logical link to the adjacent node. FLB431I NODE nodename OF CLASS class1
• An agent network node reports an APPN border IS REPLACED WITH SAME NODE
node in an adjacent APPN subnetwork as an end OF CLASS class2 WITH NEW
node; and later an agent network node in the RODM OBJECT ID rodmobjectid
adjacent subnetwork reports the border node as a
network node (its real node class). Explanation
The RODM class names and corresponding node types The node has been deleted and is replaced with a new
are: node of the same name. This change occurs when the
RODM Class Name topology manager receives information about an
Node Type existing node, where the new information indicates an
explicit change in object class. For example, the APPN
1.3.18.0.0.1821 node type is reconfigured from end node to network
APPN end node node. The RODM class names and corresponding node
1.3.18.0.0.1822 types are:
APPN network node
RODM Class Name
1.3.18.0.0.1827 Node Type
EN node
"1.3.18.0.0.1821"
1.3.18.0.0.1839 APPN end node
snaNode
"1.3.18.0.0.1822"
APPN network node

"1.3.18.0.0.1827" • An agent network or end node reports the node
LEN node identified in this message as one of its adjacent
"1.3.18.0.0.1839" nodes when it sent its local topology data to the
snaNode manager.
"1.3.18.0.0.1843" The RODM class names and corresponding node types
2.1 node are:
"1.3.18.0.0.1826" RODM Class Name
Interchange node Node Type
"1.3.18.0.0.1833" 1.3.18.0.0.1821
Migration Data Host APPN end node
"1.3.18.0.0.1845" 1.3.18.0.0.1822
T5 Node APPN network node
Message Variables 1.3.18.0.0.1826
Interchange node
nodename
1.3.18.0.0.1827
The control point name of the node that changed
LEN node
class
1.3.18.0.0.1833
class1
Migration Data Host
The RODM class name of the existing class
1.3.18.0.0.1839
class2
snaNode
The RODM class name of the new class
1.3.18.0.0.1843
rodmobjectid
2.1 node
The RODM object ID of the object with the new
class. 1.3.18.0.0.1844
T4 Node
System action 1.3.18.0.0.1845
T5 Node
The topology manager replaces the existing node
object in RODM with the new node object, preserving Message Variables
the links to other objects in RODM.
nodename
The control point name of the node that was
System programmer response created
The topology manager does not copy customer- class
defined fields from the old object to the new object in The RODM class name of the class
RODM. Set these customer-defined fields for the new rodmobjectid
RODM object. See the IBM Z NetView Resource Object The RODM object ID of the object
Data Manager and GMFHS Programmer's Guide.
FLB432I NODE nodename OF CLASS class System action
IS CREATED WITH RODM OBJECT
The topology manager creates the node object in
ID rodmobjectid
RODM.
Explanation
The node having the indicated object class was just
The topology manager does not set any customer-
created. This node was not previously known to the
defined fields in the newly created object in RODM.
topology manager. This message is issued when the
You might set these customer-defined fields for the
manager creates a real node, such as an APPN
new RODM object. See the IBM Z NetView Resource
network node or end node, but not a virtual routing
Object Data Manager and GMFHS Programmer's Guide.
node. For example, the manager issues this message
when: FLB433E SNA TOPOLOGY MANAGER COULD
• The agent network node reports the network node NOT ALLOCATE ENOUGH
identified in this message as part of its network STORAGE
topology data it sent the manager.

Explanation REQUEST FROM THE CNMTAMEL
TASK
The SNA topology manager cannot allocate enough
storage in command processor FLBTRCH. This
command processor is used to receive data from task Explanation
CNMTAMEL, and format the data from CNMTAMEL in a The SNA topology manager is not in the proper state to
format that task FLBTOPO expects. process the request from the CNMTAMEL task.
Probable causes of the error are:
System action
• The SNA topology manager initialization is not yet
The command processor stops processing this specific
complete.
request.
• The SNA topology manager has not been started or it
has been stopped.
Operator response
Determine whether you received message BNH16I, System action
so, notify your system programmer. The command is ignored.
See the IBM Z NetView Troubleshooting Guide for After the SNA topology manager initialization is
possible causes of the storage shortage. If necessary, complete, issue the operator command again, if
see the IBM Z NetView SNA Topology Manager appropriate.
Implementation Guide. For storage estimates, see the
IBM Z NetView Tuning Guide.
INITIALIZATION FAILED
FLB434E A REQUEST SENT TO THE SNA
TOPOLOGY MANAGER CANNOT BE Explanation
PROCESSED BECAUSE OF AN
The SNA topology manager encountered an error
ERROR
during its initialization and has stopped. This message
is usually preceded by other messages identifying the
Explanation cause of the problem.
The DSIMQS from this command processor to
FLBTOPO autotask received a non-zero return. A System action
buffer was received from the CNMTAMEL task in
The SNA topology manager stopped.
command processor FLBTCRH. This command
processor will change the buffer into one that the SNA
topology manager will accept. Operator response
System action
The command is ignored. System programmer response
See the error messages in the NetView log and to IBM
Operator response Z NetView Troubleshooting Guide to diagnose and
correct the error. Restart the SNA topology manager. If
This condition might be temporary. If this condition
necessary, contact IBM Software Support.
persists, notify your system programmer.
System programmer response CANNOT SEND A BUFFER TO TASK
CNMTAMEL BECAUSE OF AN
This condition occurs when the command processor is
ERROR
attempting to send a request from the CNMTAMEL
task to the SNA topology manager. See the error
messages in the NetView log and to IBM Z NetView Explanation
Troubleshooting Guide to diagnose and correct the The SNA topology manager attempted to send a buffer
error. If necessary, contact IBM Software Support. to the CNMTAMEL task. However, the DSIMQS macro
FLB435E invocation received a non-zero return code. A likely
SNA TOPOLOGY MANAGER IS NOT
READY TO PROCESS THE

reason for this failure is that the CNMTAMEL task is not System action
operational.
The SNA topology manager will not be able to accept
operator requests such as a request for status history
System action for objects owned by the SNA topology manager.
The buffer is not sent to the CNMTAMEL task.
Operator response
This condition might be temporary. If this condition
persists, notify your system programmer. System programmer response
System programmer response IBM Z NetView Troubleshooting Guide to diagnose and
Ensure that the CNMTAMEL task is operational. See correct the error. If necessary, contact IBM Software
the error messages in the NetView log and to the IBM Support.
Z NetView Troubleshooting Guide to diagnose and FLB440I SNA TOPOLOGY MANAGER
correct the error. If necessary, contact IBM Software INITIALIZATION IS COMPLETE
Support.
FLB438E SNA TOPOLOGY MANAGER COULD Explanation
NOT ALLOCATE ENOUGH
The SNA topology manager has successfully
STORAGE
completed its initialization, including its cold-start or
warm-start processing, and is now ready to accept all
Explanation TOPOSNA operator commands. The cold-start
The SNA topology manager cannot allocate enough processing includes purging all APPN topology objects
storage in module FLBTRSH. This command processor in the RODM data cache. The warm-start processing
is used to send data to task CNMTAMEL. includes purging all eligible APPN topology objects,
based on the PURGDAYS parameter in the topology
manager initialization file, and restarting continuous
System action
monitoring operations.
The SNA topology manager stops processing the
specific request. System action
Topology manager is prepared to accept TOPOSNA
Operator response
operator commands.
FLB441I SNA TOPOLOGY MANAGER IS
so, notify your system programmer. SHUTTING DOWN NORMALLY
Explanation
The SNA topology manager is beginning a normal
shutdown in response to the TOPOSNA STOPMGR
possible causes of the storage shortage. If necessary,
operator command.
see the IBM Z NetView SNA Topology Manager
Implementation Guide and the IBM Z NetView Tuning
Guide for more information. System action
FLB439E SNA TOPOLOGY MANAGER COULD Topology manager performs an orderly shutdown.
NOT ESTABLISH A SESSION WITH FLB442E SNA TOPOLOGY MANAGER IS
TASK CNMTAMEL SHUTTING DOWN BECAUSE OF AN
ERROR
Explanation
The SNA topology manager attempted to establish a Explanation
session with task CNMTAMEL. However, the The SNA topology manager is beginning to shut down
CNMTAMEL task responded with a failure. because it has encountered an error. This message is
usually preceded by other messages identifying the
cause of the problem.

Topology manager attempts an orderly shutdown. The SNA topology manager ignored the TOPOSNA
operator command because it is shutting down. Either
Operator response the TOPOSNA STOPMGR operator command was
issued earlier or the topology manager encountered an
Notify your system programmer. error that caused it to shut down.
Message Variables
requestparm
The name of the TOPOSNA request parameter
IBM Z NetView Troubleshooting Guide to diagnose and
correct the error. Restart the topology manager. If
necessary, contact IBM Software Support. System action
FLB443I SNA TOPOLOGY MANAGER The command is ignored.

SHUTDOWN IS COMPLETE
Operator response
Explanation After the topology manager is restarted, issue the
The SNA topology manager has completed its orderly command again, if appropriate.
shutdown process. Logoff processing follows the FLB446E SNA TOPOLOGY MANAGER
shutdown, to ensure that the connections between the CANNOT BE EXECUTED UNDER
topology manager and other components are properly TASK taskname
disconnected.
Explanation
System action
A task other than FLBTOPO tried to start the SNA
Logoff processing begins. topology manager. The topology manager must be
FLB444E SNA TOPOLOGY MANAGER started under task FLBTOPO.
ENCOUNTERED A PROCESSING Message Variables
ERROR
taskname
The name of the incorrect task
Explanation
In the course of its processing, the SNA topology System action
manager has encountered a processing error.
Topology manager stops.
System action
Operator response
Topology manager either resumes processing or
begins shutting down, depending on the error. Start the topology manager under task FLBTOPO.
FLB447I SNA TOPOLOGY MANAGER IS
Operator response INITIALIZING
Explanation
System programmer response The SNA topology manager is beginning its
initialization processing.
Z NetView Troubleshooting Guide to diagnose and
correct the error. Restart the topology manager if it System action
has stopped. If necessary, contact IBM Software The topology manager initializes.
Support.
FLB445E TOPOSNA requestparm COMMAND Operator response
IGNORED BECAUSE SNA Look for message FLB440I to verify that initialization
TOPOLOGY MANAGER IS has completed successfully.
SHUTTING DOWN

FLB448E SNA TOPOLOGY MANAGER COULD nodename
NOT CREATE AN EFD FOR The control point name of the agent node
DEFINITIONGROUPS AT NODE
nodename System action
The SNA topology manager will continue to function.
Explanation However, the SNA topology manager will not receive
The SNA topology manager cannot create an Event Object Deletion Event Reports for definitionGroups.
Forwarding Discriminator at the agent node to receive
Object Deletion Event Reports for definitionGroups. Operator response
The error is considered unrecoverable and no retry
occurs. The probable cause of the error is a system Notify your system programmer.
error at the agent node.
Message Variables
nodename IBM Z NetView Troubleshooting Guide to diagnose and
The control point name of the agent node correct the error. Then start monitoring the topology
again. If necessary, contact IBM Software Support.
System action
FLB450E SNA TOPOLOGY MANAGER IS NOT
The SNA topology manager will continue to function, READY TO PROCESS THE
but the SNA topology manager will not receive Object TOPOSNA requestparm COMMAND
Deletion Event Reports for definitionGroups.
Explanation
Operator response
The SNA topology manager is not in the proper state to
Notify your system programmer. process the TOPOSNA operator command.
• The topology manager initialization is not yet
complete.
correct the error. Refer also to the system error log at • The topology manager has not been started or it has
the agent node to determine whether an agent system been stopped.
error occurred; if it did, take action to fix the problem Message Variables
at the agent node. Restart monitoring the topology. If
necessary, contact IBM Software Support. requestparm
FLB449E SNA TOPOLOGY MANAGER FAILED
ALL RETRIES TO CREATE AN
System action
EVENT FORWARDING
DISCRIMINATOR FOR The command is ignored.
DEFINITIONGROUPS AT NODE
nodename Operator response
After the topology manager initialization is complete,
Explanation
issue the operator command again, if appropriate.
The SNA topology manager cannot create an Event
FLB451E TOPOSNA requestparm COMMAND
Object Deletion Event Reports for definitionGroups. HAS AN UNKNOWN PARAMETER
The error is considered recoverable, but the SNA 'parameter'
topology manager has exceeded the retry limits of 10.
Explanation
Probable causes of the error are that a session from
the NetView host to the agent node cannot be The TOPOSNA operator command contains an
established, or that the session failed and cannot be unknown parameter for this command.
established again. Message Variables
Message Variables requestparm

parameter System action
The name of the unknown parameter
System action
Operator response
Issue the operator command again using the correct
syntax. If you are not sure of the correct syntax, enter
Operator response HELP TOPOSNA requestparm.
Issue the operator command again using the correct FLB454E TOPOSNA requestparm COMMAND
parameter. If you are not sure of the correct command IS MISSING PARAMETER
parameters, enter HELP TOPOSNA requestparm. 'parameter'
HAS INCORRECT VALUE 'value' Explanation
FOR PARAMETER 'parameter'
The TOPOSNA operator command is missing a
parameter that is required for this command.
Explanation
Message Variables
The TOPOSNA operator command contains an
incorrect parameter value. requestparm
Message Variables
parameter
requestparm The name of the required parameter
value System action
The value that is incorrect
parameter
The name of the parameter Operator response
System action Issue the operator command again with the required
parameter. If you are not sure of the required
The command is ignored. parameters for the command, enter HELP TOPOSNA
requestparm.
Operator response
Issue the operator command again using the correct IS MISSING A VALUE FOR
parameter value. If you are not sure of the correct PARAMETER 'parameter'
value, enter HELP TOPOSNA requestparm.
FLB453E TOPOSNA requestparm COMMAND Explanation
HAS INCORRECT SYNTAX The TOPOSNA operator command is missing a value
that is required for the parameter for this command.
The TOPOSNA operator command contains a general requestparm
syntax error. The name of the TOPOSNA request parameter
The probable cause of the error is one of the following: parameter
• Missing or misplaced comma The name of the parameter that is missing a value
• Missing parenthesis
System action
• Missing equal sign (=)
• Unbalanced parentheses
• Incorrect parameter length Operator response
Message Variables Issue the operator command again with a value for the
requestparm parameter. If you are not sure of the values allowed
The name of the TOPOSNA request parameter for the parameter, enter HELP TOPOSNA requestparm.

FLB456E TOPOSNA requestparm COMMAND FLB458E TOPOSNA requestparm COMMAND
HAS CONFLICTING PARAMETERS IS MISSING ONE OF THE
'parameter1' AND 'parameter2' FOLLOWING PARAMETERS
'parameters'
Explanation
Explanation
The TOPOSNA operator command contains conflicting
parameters. Check for the following: The TOPOSNA operator command is missing one or
more parameters that are required for this command.
• Two parameters must not be specified together on
the same command Message Variables
• The same parameter is specified twice when only requestparm
one occurrence is allowed The name of the TOPOSNA request parameter
• The values specified for the two parameters are in parameters
conflict. The names of the missing parameters separated
Message Variables by commas
requestparm System action

parameter1
The name of the first parameter
Operator response
parameter2
The name of the second parameter. Issue the TOPOSNA command again with the required
parameters. If you are not sure of the required
System action parameters for the command, enter HELP TOPOSNA
requestparm.
Operator response HAS A VALUE SPECIFIED FOR THE
PARAMETER 'parameter' WHERE
Issue the operator command again using the correct NONE IS ALLOWED
parameters or with corrected values for the
parameters. If you are not sure of the correct Explanation
parameters, enter HELP TOPOSNA requestparm.
The TOPOSNA command has been entered with a
FLB457E TOPOSNA 'requestparm' value where no value is allowed.
COMMAND IS UNKNOWN
Message Variables
Explanation requestparm
The TOPOSNA operator command is unknown to the
SNA topology manager. The probable cause is that the parameter
TOPOSNA request parameter is misspelled. The name of the parameter that must not have a
value associated with it
Message Variables
requestparm System action
The name of the unknown TOPOSNA request
parameter
Operator response
System action
Remove the unnecessary value and issue the
command again. If you are not sure of the correct
syntax, enter HELP TOPOSNA requestparm.
Operator response
FLB460W THE CREATION OF AN EVENT
Issue the correct TOPOSNA operator command. If you
FORWARDING DISCRIMINATOR
are not sure of the correct commands for the SNA
FOR DEFINITIONGROUPS AT
topology manager, enter HELP TOPOSNA.

NODE nodename IS BEING CDRMname
RETRIED The name of the crossDomainResourceManager
objectid
Explanation The RODM object ID of the
The SNA topology manager cannot create an Event crossDomainResourceManager
Object Deletion Event Reports for definitionGroups. System action
The error was considered recoverable. The SNA Monitoring is not started.
topology manager is retrying the creation of this Event
Forwarding Discriminator at the agent node. The FLB462E MONITORING OF SNA NETWORK
probable reason for the error is that the session from TOPOLOGY FROM NODE nodename
the NetView host to the agent node failed. FAILED ALL RETRIES
Message Variables
Explanation
nodename
The control point name of the agent node The SNA topology manager cannot start the
monitoring of SNA network topology from the agent
node. The error is considered recoverable but the
System action topology manager has exceeded the retry limits for
The SNA topology manager retries to create the event network topology. The retry limits are specified on the
forwarding discriminator. TOPOSNA SETDEFS operator command.
FLB461E SNA TOPOLOGY MANAGER IS The probable cause of the error is one of the following:
UNABLE TO DETERMINE THE • A session from the NetView host to the agent node
AGENT CP NAME FOR CROSS cannot be established, or the session failed and
DOMAIN RESOURCE MANAGER cannot be established again.
'CDRMname' WITH OBJECT ID
'objectid' • The agent node does not have a topology agent
Explanation • The agent node control point name is incorrect; for
example, the name was not typed correctly on the
The SNA topology manager cannot convert the RODM TOPOSNA MONITOR operator command.
object ID of a crossDomainResourceManager to the
• The agent node is not powered on or it does not exist
SSCP name of the agent that it represents. This can
in the network.
happen for the following reasons:
• The agent node is an end node; end nodes do not
• The realSSCPname field value of the support requests for network topology.
crossDomainResourceManager object, and the third
RDN (Relative Distinguished Name) of the MyName Message Variables
field are not network qualified. nodename
• The realSSCPname field value of the The control point name of the agent node
crossDomainResourceManager object is null. The
third RDN (Relative Distinguished Name) of the System action
MyName field is not network qualified.
Monitoring is not started.
The situations above can occur when the following
conditions exist concurrently:
Operator response
• The topology agent has reported a
Ensure that the agent node is a network node. If it is,
crossDomainResourceManager to the SNA topology
see the messages in the NetView log to diagnose the
manager, and
error. You might be able to later start monitoring
• This crossDomainResourceManager does not network topology from the agent node. Issue the
contain a NETWORK statement in the CDRM major TOPOSNA QUERYDEF operator command to
node, and determine if the retry limits must be increased. If you
• This crossDomainResourceManager is not currently are unable to correct the problem, notify your system
in session with the adjacent SSCP. programmer.
Message Variables

System programmer response FLB464I SNA TOPOLOGY MANAGER
A KEYWORD 'keyword' WITH A
NULL VALUE AS FIRST ENTRY
correct the error. Then start monitoring the network
topology again. If necessary, contact IBM Software
Support. Explanation
FLB463E MONITORING OF SNA LOCAL The SNA topology manager initialization file FLBSYSD
TOPOLOGY FROM NODE nodename includes a keyword with a null value as the first entry.
FAILED ALL RETRIES The keyword indicated in the message has no value
assigned to it. All the subsequent entries are ignored
and not processed by the SNA Topology Manager.
Explanation
Message Variables
monitoring of SNA local topology from the agent node. keyword
The error is considered recoverable but the topology The keyword in the file that has no value assigned
manager has exceeded the retry limits for local to it
topology that are specified on the TOPOSNA SETDEFS
operator command. System action
The probable cause of the error is one of the following: The SNA topology manager stores this keyword value
• A session from the NetView host to the agent node as null value and ignores the rest of the entries for this
cannot be established, or the session failed and keyword.
• The agent node does not have a topology agent Operator response
installed and running. Notify your system programmer.
• The agent node control point name is incorrect; for
example, the name was not typed correctly on the System programmer response
TOPOSNA MONITOR operator command.
Read the information provided in the initialization file
• The agent node is not powered on or it does not exist FLBSYSD in the comment block before this keyword
in the network. and take an appropriate action.
Message Variables FLB465I SNA TOPOLOGY MANAGER
nodename INITIALIZATION FILE CONTAINS
The control point name of the agent node A KEYWORD 'keyword' WITH A
DUPLICATE VALUE 'value'
System action
Explanation
Monitoring is not started.
The SNA topology manager encountered duplicate
Operator response entries for the keyword specified in the initialization
file FLBSYSD.
See the messages in the NetView log to diagnose the
error. You might be able to later start monitoring local Message Variables
topology from the agent node. Issue the TOPOSNA keyword
QUERYDEF operator command to determine if the The keyword that was duplicated in the file
retry limits must be increased. If you are unable to
value
correct the problem, notify your system programmer.
The value that was duplicated in the file

System action
Processing continues and the duplicate entry is
ignored.
correct the error. Then start monitoring the local
topology again. If necessary, contact IBM Software

Remove the duplicate entry from the FLBSYSD Issue the command again with a single value for the
initialization file. specified keyword.
FLB466I SNA TOPOLOGY MANAGER FLB468E THE FORMAT OF THE LU NAME IS
INITIALIZATION FILE CONTAINS INCORRECT. IT MUST BE
A KEYWORD 'keyword' WITH AN NETID.CPNAME.NETID.LUNAME
INVALID VALUE 'value'
Explanation
Explanation
The format of the LU name that you entered in the
The SNA topology manager encountered a entry that is TOPOSNA CRITICAL command is incorrect. It must be
not valid for the keyword specified in the initialization netid.cpname.netid.luname.
file FLBSYSD.
keyword The command is rejected.

The keyword in the file that had a value that was
not valid Operator response
value Issue the command again with the correct format for
The value of the keyword the LU name.
FLB472I SNA TOPOLOGY MANAGER RODM
System action
ACTIVITY COUNTS FOLLOW:
Processing continues and the entry that is not valid is
ignored. Explanation
This is the first message in response to the TOPOSNA
Operator response
LISTRODM operator command, which lists RODM
Notify your system programmer. activity and object counts. The messages containing
the information about the RODM activity and object
System programmer response counts follow this message. The topology manager
issues message FLB477I when it has finished listing
Correct the entry in FLBSYSD and restart SNA topology the information about its storage usages.
manager. Check the comments in FLBSYSD for
information concerning valid values for this specific FLB473I OBJ. LINK/ FLBTRST RODM
keyword.
Explanation
FLB467E TOPOSNA command COMMAND
REQUIRES A SINGLE VALUE FOR This message is the first line of the header for the
KEYWORD 'keyword' output from the TOPOSNA LISTRODM command that
lists RODM activity and object counts. This message is
Explanation part of a multi-line message.
This message indicates that a TOPOSNA command

System action
was entered with multiple keyword values and the
specified keyword only supports a single value. Message FLB474I follows this message.
Message Variables FLB474I TYPE CREATE DELETE UPDATE
command QUERY UNLINK (STATUS) COUNT
The name of the TOPOSNA command
Explanation
keyword
The name of the incorrectly specified keyword This message is the second line of the header for the
output from the TOPOSNA LISTRODM command that
System action lists RODM activity and object counts. This message is
part of a multi-line message.
The command has no effect.

System action T5
t5Node
Message FLB475I follows this message.
VRN
FLB475I ---- ------- ------- ------ ----- ------ virtualRoutingNode
------- -------
Link
logicalLink
Explanation
CDR
This message is the third line of the header for the crossDomainResource
output from the TOPOSNA LISTRODM command that
LU
lists RODM activity and object counts. This message is
logicalUnit
part of a mult-line message.
LUGr
luGroup
System action
Port
LISTRODM data follows this message. port
FLB476I objtype create delete update query TG
lnkunlnk flbtrst rodmcnt appnTransmissionGroup
ACir
Explanation appnTransmissionGroupCircuit
This message is one of the data items in response to SCir
the TOPOSNA LISTRODM command that list RODM subareaTransmissionGroupCircuit
activity and object counts. This message is part of a AggG
multiple-line message. aggregateGraph2
Message Variables AggC
objtype circuit2
The RODM object class SnaL
snaLocalTopology
Following is a list of the RODM object classes:
TOTL
CDRM
Totals (not an object class)
crossDomainResourceManager
DefG
definitionGroup
EN create
appnEN The number of EKG_CreateObject calls issued
against OBJ TYPE.
ICN
interchangeNode delete
The number of EKG_DeleteObject calls issued
LEN against OBJ TYPE.
lenNode
update
MDH The number of EKG_ChangeMultipleFields calls
migrationDataHost issued against OBJ TYPE.
NN query
appnNN The number of EKG_QueryField and
BrNN EKG_QueryMultipleSubfields calls issued against
Branch Network Node object OBJ TYPE.
Sna lnkunlnk
snaNode The number EKG_LinkTrigger and
T2.1 EKG_UnlinkTrigger calls issued against OBJ TYPE.
t2-1Node flbtrst
T4 The number of times the FLBTRST method was
t4Node invoked for OBJ TYPE (indicates a status change
occurred). The column contains a blank entry for
aggregate objects (SCir, AggG, AggC, and SnaL).

rodmcnt FLB481E SNA TOPOLOGY MANAGER
Indicates the current number of object instances DISCOVERED THAT RODM
of OBJ TYPE currently or previously known to the 'rodmname' IS TERMINATING/
SNA Topology Manager since the SNA Topology QUIESCING
Manager was last initialized (in other words, the
SNA Topology Manager must have received a Explanation
status report on this object by an ongoing or
previous topology monitor in order for the object to The SNA topology manager received a reason code on
be reflected in this count). Column will contain a a call to the RODM user API that indicates RODM is
blank entry for aggregate objects (SCir, AggG, terminating or quiescing, or the RODM termination
AggC, and SnaL). ECB has been posted.
Message Variables
System action
rodmname
LISTRODM data for RODM activity and object counts is RODM name from the FLBSYSD initialization
included in this message. member
FLB477I END OF RODM ACTIVITY
COUNTS------------------------------ System action
---- The SNA topology manager reinitializes and attempts
to connect to RODM on a timed basis.
Explanation
The display of RODM activity and object counts from Operator response
the LISTRODM command is complete. If RODM has stopped, restart RODM. If RODM is
FLB480E SNA TOPOLOGY MANAGER FAILED quiescing, wait until RODM has finished quiescing,
TO CONNECT TO RODM then restart RODM.
'rodmname' BECAUSE OF A LACK FLB482E SNA TOPOLOGY MANAGER
OF STORAGE ENCOUNTERED AN
UNRECOVERABLE ERROR ON A
Explanation CALL TO RODM 'rodmname'
The SNA topology manager cannot obtain enough
storage to connect to RODM during the topology Explanation
manager's initialization. The SNA topology manager received an unsatisfactory
Message Variables return code or reason code on a call to the RODM user
API. The topology manager cannot recover from the
rodmname error.
RODM name from the FLBSYSD initialization
member Message Variables
rodmname
System action RODM name from the FLBSYSD initialization
member
The topology manager stops.
System action
Operator response
The topology manager stops.
so, notify your system programmer. Operator response
See the IBM Z NetView Troubleshooting Guide for System programmer response
possible causes of the storage shortage. If necessary, See the error messages in the NetView log and to IBM
see the IBM Z NetView SNA Topology Manager Z NetView Troubleshooting Guide to diagnose and
Implementation Guide and the IBM Z NetView Tuning correct the error. Also, check the RODM log for an
Guide for more information. error conditions generated by the APPNTM application
(APPNTM is the user application ID used by SNA

topology manager to connect to RODM). Then restart This retrying continues until the RODM call is
the topology manager. If necessary, contact IBM successful or the topology manager exceeds the retry
Software Support. limits. If the retry limits are exceeded, the RODM call
is treated as a failing call and further RODM processing
FLB483W SNA TOPOLOGY MANAGER FAILED
is determined by RDMRETRY value settings (see
TO CONNECT TO RODM TOPOSNA SETDEFS for additional information on
'rodmname' AND WILL RETRY the
RDMRETRY values).
RODM named in the message.
Explanation • RODM is stopping or has stopped.
The SNA topology manager failed to connect. The SNA • The topology data model is not loaded into RODM.
topology manager attempts to establish the RODM
Message Variables
connection based on the RODM retry value settings.
rodmname
• RODM is not started. member
• RODM has not completed its initialization.
System action
• The RODM name in FLBSYSD is different than the
active RODM name. The topology manager begins retrying after the first 5-
• The SNA topology manager is not authorized to use second interval, or 30-second interval, as appropriate.
RODM.
Operator response
Message Variables
If the topology manager retry attempts succeed, no
rodmname
further action is necessary. If all retry attempts fail,
the topology manager will retry the current command
member
based on RDMRETRY settings.
System action FLB485E SNA TOPOLOGY MANAGER FAILED

ALL RETRIES WHEN CONNECTING
The SNA topology manager attempts to establish the TO OR CALLING RODM 'rodmname'
connection to RODM, based on the RODM retry value
settings or until the TOPOSNA STOPMGR command is
issued. Explanation
The SNA topology manager either attempted to
Operator response connect to RODM, or attempted to call RODM, and
received an error indication on all attempts. The error
If RODM has not completed its initialization, the SNA is considered recoverable but the topology manager
topology manager establishs the connection to RODM has exceeded its retry limit of 10 times.
when the initialization is complete. In this case, no
action is necessary in response to this message. Message Variables
FLB484W SNA TOPOLOGY MANAGER rodmname

RECEIVED AN ERROR ON A CALL RODM name from the FLBSYSD initialization
TO RODM 'rodmname' AND WILL member
RETRY
System action
Explanation The topology manager writes a related error message
The SNA topology manager received an unsatisfactory to the NetView log and continues RODM processing
return code or reason code from a call to the RODM based on the RDMRETRY values (set by the TOPOSNA
user API. The error is considered recoverable and the SETDEFS,RDMRETRY command).
topology manager will try the RODM call again. If the
topology data model is loaded into RODM, the retry Operator response
begins in 5 seconds and is repeated 10 times at 5-
second intervals. If the topology data model is not
loaded into RODM, the retry begins in 30 seconds and
is repeated 10 times at 30-second intervals.

System programmer response NMC display field is limited to 254 characters. For the
specified RODM object, the data to be written to this
field or to be appended to the existing data in this
field, causes the total data length to exceed this limit.
correct the error. The error messages in the NetView
Therefore, the truncation character is inserted at
log include the RODM return code and reason code. If
position 254 and only the first 254 characters
RODM has not been started, start it. If the RODM name
(including the truncation character) are displayed by
indicated in this message does not match the name
NMC. However, the topology manager stores the
under which RODM was started, enter the correct
complete value of the DisplayResourceOtherData field
RODM name in the topology manager FLBSYSD
in RODM.
initialization member. If the topology manager is not
authorized to use RODM, give it the proper Message Variables
authorization; the topology manager uses the
rodmobjectid
application ID 'APPNTM' when connecting to RODM.
The RODM object identifier of the object containing
Refer also to the IBM Z NetView Resource Object Data
partial data in the DisplayResourceOtherData field
Manager and GMFHS Programmer's Guide for
information about establishing a connection to RODM
and RODM error conditions. Then, restart the topology System action
manager. If necessary, contact IBM Software Support. The complete value of the DisplayResourceOtherData
FLB486I SNA TOPOLOGY MANAGER field is stored in RODM, but with the truncation
CALLED RODM 'rodmname' character inserted at position 254.
DURING A RODM CHECKPOINT
AND WILL RETRY Operator response
If required, use RODMVIEW or another RODM tool to
Explanation view the complete DisplayResourceOtherData in
The SNA topology manager received a RODM RODM.
checkpoint indication on a call to the RODM user API. FLB490I SNA TOPOLOGY MANAGER
The retry begins in 5 seconds and is repeated at 5- STORED DEFAULT VALUES IN
second intervals until the call is successful or the RODM
topology manager receives an error return code.
rodmname This message is in response to the TOPOSNA SETDEFS
RODM name from the FLBSYSD initialization operator command to change topology manager
member defaults. The topology manager writes the default
values to RODM and then issues this message.
System action
System action
The topology manager begins retrying to call RODM
after the first 5-second interval. The new default values are in effect.
Operator response TO STORE DEFAULT VALUES IN
If the topology manager retry attempts succeed, no RODM
action is necessary in response to this message. If
retry attempts fail because of an error, the topology Explanation
manager issues message FLB485E.
The SNA topology manager is unable to write the
FLB487W THE 'DISPLAY RESOURCE OTHER topology manager default values to RODM. This
DATA' FIELD WAS TRUNCATED message is in response to the TOPOSNA SETDEFS
FOR RODM OBJECT ID operator command to change the default values. The
'rodmobjectid' operator command is ignored and the topology
manager stops execution.
Explanation
System action
The DisplayResourceOtherData field in RODM is used
to provide additional information to the user The topology manager stops.
concerning various RODM objects. The corresponding

Operator response QUERYDEF operator command. Messages containing
the topology manager default values follow this
message.

System action
correct the error. Then start the topology manager FLB495I MONITOR SNA LOCAL TOPOLOGY
again. If necessary, contact IBM Software Support. FOR NEW NETWORK NODES :
defaultset
FLB492I 'CLASS' KEYWORD ONLY APPLIES
TO THE 'SIGNALS', 'UPDATE', AND
'RODM' TRACE CATEGORIES, Explanation
'CLASS' KEYWORD IS IGNORED This message shows the default setting for whether
the topology manager must automatically monitor the
Explanation SNA local topology for newly discovered network
nodes. The default setting indicated in the message is
The TOPOSNA TRACE command was issued with the
YES or NO.
'CLASS' keyword, but no applicable trace category was
specified with the 'ON' or 'OFF' keyword. Message Variables
The default setting for monitoring SNA local
System action topology from network nodes
The 'CLASS' keyword is ignored, the rest of the
TOPOSNA TRACE command is processed. System action
Operator response
FLB496I MONITOR SNA LOCAL TOPOLOGY
Issue the command again, specifying a correct trace FOR NEW END NODES : defaultset
category along with the 'CLASS' keyword.
FLB493I ERROR RETRY LIMIT: limit Explanation
This message shows the default setting for whether
Explanation the topology manager must automatically monitor the
As part of the TOPOSNA QUERYDEF output, this SNA local topology for newly discovered end nodes.
message lists the command error-retry limit. If a The default setting indicated in the message is YES or
command fails because of an SNA topology manager NO.
or RODM error, it is retried the specified number of Message Variables
times. If the command fails the specified number of
times, the retries are stopped. defaultset
The default setting for monitoring SNA local
Message Variables topology from end nodes
limit FLB497I SNA NETWORK TOPOLOGY
The retry limit (valid range is 0–65535) IMMEDIATE RETRY INTERVAL:
defaultset
Operator response
To change the retry limit value, issue the TOPOSNA Explanation
SETDEFS,ERRLIMIT=xxx command. Reducing the This message shows the default setting for the
value fails any current commands that are in error immediate retry time interval in seconds for
retry status and have exceeded the new retry limit. monitoring SNA network topology. When the topology
FLB494I SNA TOPOLOGY MANAGER manager fails to complete the initial transfer of
DEFAULT SETTINGS FOLLOW: network topology for a given agent node, the topology
manager retries at the indicated interval of time. The
default setting indicated in the message is the time
Explanation
interval in seconds.
This is the first message that lists the topology
Message Variables
manager defaults in response to the TOPOSNA

defaultset defaultset
The default setting for the immediate retry time The default setting for the long-term retry limit for
interval for monitoring SNA network topology monitoring SNA network topology
FLB498I SNA NETWORK TOPOLOGY FLB501I SNA LOCAL TOPOLOGY
IMMEDIATE RETRY LIMIT : IMMEDIATE RETRY INTERVAL :
This message shows the default setting for the This message shows the default setting for the
immediate retry limit for monitoring SNA network immediate retry time interval in seconds for
topology. When the topology manager fails to monitoring SNA local topology. When the topology
complete the initial transfer of network topology for a manager fails to complete the initial transfer of local
given agent node, it retries up to the indicated limit of topology for a given agent node, it retries at the
retries. The default setting indicated in the message is indicated interval of time. The default setting indicated
upper limit of the number of retries. in the message is the time interval in seconds.
The default setting for the immediate retry limit for The default setting for the immediate retry time
monitoring SNA network topology interval for monitoring SNA local topology
FLB499I SNA NETWORK TOPOLOGY LONG- FLB502I SNA LOCAL TOPOLOGY
TERM RETRY INTERVAL : IMMEDIATE RETRY LIMIT :
This message shows the default setting for the long- This message shows the default setting for the
term retry time interval in seconds for monitoring SNA immediate retry limit for monitoring SNA local
network topology. When the topology manager fails to topology. When the topology manager fails to
complete the initial transfer of network topology for a complete the initial transfer of local topology for a
given agent node and exceeds the number of given agent node, it retries up to the indicated number
immediate retries allowed, the topology manager of retries. The default setting indicated in the message
retries at the indicated long-term interval of time. The is the upper limit of the number of retries.
default setting indicated in the message is the time
Message Variables
interval in seconds.
defaultset
Message Variables
The default setting for the immediate retry limit for
defaultset monitoring SNA local topology
The default setting for the long term retry time
FLB503I SNA LOCAL TOPOLOGY LONG-
interval for monitoring SNA network topology
TERM RETRY INTERVAL: defaultset
FLB500I SNA NETWORK TOPOLOGY LONG-
TERM RETRY LIMIT : defaultset Explanation
This message shows the default setting for the long-
Explanation
term retry time interval in seconds for monitoring SNA
This message shows the default setting for the long- local topology. When the topology manager fails to
term retry limit for monitoring SNA network topology. complete the initial transfer of local topology for a
When the topology manager fails to complete the given agent node and exceeds the allowed number of
initial transfer of network topology for a given agent immediate retries, the topology manager retries at the
node and exceeds the number of immediate retries indicated long-term interval of time. The default
allowed, the topology manager retries up to the setting indicated in the message is the time interval in
indicated long-term limit. The default setting indicated seconds.
in the message is the upper limit of the number of
Message Variables
retries.
Message Variables

defaultset Operator response
The default setting for the long-term retry time
If the size of the internal trace buffer is not set to the
interval for monitoring SNA local topology
correct value, issue the TOPOSNA TRACE,SIZE=xxx
FLB504I SNA LOCAL TOPOLOGY LONG- command to change it. Changing the value while the
TERM RETRY LIMIT : defaultset SNA topology manager internal trace is active is
allowed, but if the new size is smaller than the
Explanation previous size, only the most recent trace entries are
retained.
This message shows the default setting for the long-
term retry limit for monitoring SNA local topology. FLB507E method_name METHOD CANNOT
When the topology manager fails to complete the OBTAIN NECESSARY STORAGE
initial transfer of local topology for a given agent node,
and exceeds the number of immediate retries allowed, Explanation
the topology manager retries up to the indicated long-
The SNA topology manager method cannot get enough
term limit. The default setting indicated in the
local storage for execution.
message is the upper limit of the number of retries.
Message Variables
Message Variables
method_name
defaultset
The name of the SNA topology manager method
The default setting for the long-term retry limit for
that cannot get enough local storage
monitoring SNA local topology
FLB505I SNA TOPOLOGY MANAGER TRACE System action
MODE IS tracemode
The SNA topology manager method stops executing.
This can cause the current SNA topology manager
Explanation operation (such as a TOPOSNA MONITOR) to end.
As part of the TOPOSNA TRACE,QUERY output, this
message lists the trace mode. Operator response
Message Variables Notify your system programmer.
tracemode
Possible values are: System programmer response
INTERNAL Correct the shortage of storage in RODM. Restart any
Trace mode is set to internal. SNA topology manager operations that failed.
EXTERNAL FLB508I SNA TOPOLOGY MANAGER TRACE
Trace mode is set to external (GTF). CLASS class IS status

If the trace mode setting is incorrect, issue the As part of the TOPOSNA TRACE,QUERY output, this
TOPOSNA TRACE MODE=INT|EXT command to change message indicates whether the trace class is enabled
the value. (ON) or disabled (OFF).
FLB506I SNA TOPOLOGY MANAGER Message Variables
INTERNAL TRACE BUFFER SIZE IS
size PAGES class
The trace class
Explanation status
Indicates whether the trace category is enabled
As part of the TOPOSNA TRACE,QUERY output, this (ON) or disabled (OFF)
message lists the size of the internal TOPOSNA trace
buffer in pages where each page is equal to 4096
Operator response
bytes.
If the trace class is not set properly, use the TOPOSNA
Message Variables
TRACE command to set the class correctly.
size
Size in pages (4096 bytes per page)

FLB509I SNA TOPOLOGY MANAGER TRACE attempts by the SNA topology manager to connect to
CATEGORY tracecat IS status RODM when the RODM connection is lost.
Message Variables
Explanation
interval
The SNA topology manager trace categories are used Interval of time in seconds between retries
to control what information is being traced by the
topology manger. If a trace category is turned ON, all Operator response
events related to that category are traced and stored
using the Generalized Trace Facility (GTF). See the IBM If the RODM retry interval is not set properly, use the
Z NetView Troubleshooting Guide for more information. TOPOSNA SETDEFS RDMRETRY command to set the
interval correctly.
Message Variables
FLB521I RODM RETRY LIMIT: limit
tracecat
A topology manager trace category
Explanation
status
Indicates whether the trace category is enabled As part of the TOPOSNA QUERYDEF output, this
(ON) or disabled (OFF) message indicates the maximum number of times the
SNA topology manager will attempt to connect to
Operator response RODM when the RODM connection is lost.
If the trace category is not set properly, use the Message Variables
TOPOSNA TRACE command to turn the category ON or limit
OFF. For more information about the TOPOSNA TRACE The maximum number of retries
command, see the NetView online help.
FLB516I ---------------------------------------- Operator response
------------- If the RODM retry limit is not set properly, use the
TOPOSNA SETDEFS RDMRETRY command to set the
Explanation limit correctly.
This is a separator to partition the trace categories in FLB524I keyword KEYWORD RANGE MUST
the TOPOSNA TRACE,QUERY command output. BE value1 THROUGH value2,
FLB517W keyword KEYWORD IGNORED
'CLASS' KEYWORD SPECIFIED
WITHOUT 'ON' OR 'OFF'
KEYWORD. NO ACTION Explanation
PERFORMED. The value for the specified keyword is not within the
allowed range.
Explanation
Message Variables
This message indicates that a TOPOSNA TRACE
keyword
command was entered with an incorrect keyword
The keyword in error
combination. The 'ON' or 'OFF' keyword must be
issued whenever the 'CLASS' keyword is specified. value1
The minimum range value
System action value2
The maximum range value
The TRACE command has no effect.
System action
Operator response
The keyword in error is ignored. The remainder of the
command is executed.
FLB520I RODM RETRY INTERVAL: interval
Operator response
Explanation Issue the command again with a valid range value.
As part of the TOPOSNA QUERYDEF output, this
message indicates the time (in seconds) between the

FLB525I SNA TOPOLOGY MANAGER TRACE Operator response
MODE IS EXTERNAL, 'SIZE' If the CMIP Services retry limit is not set properly, use
KEYWORD IGNORED the TOPOSNA SETDEFS CMPRETRY command to set
the limit correctly.
Explanation
FLB532I SNA TOPOLOGY MANAGER
The 'SIZE' keyword was specified with 'MODE=EXT' or INTERNAL TRACE TABLE SIZE
the current tracing mode was external and CHANGED TO number PAGES
'MODE=INT' was not specified.
Explanation
System action
The requested internal-trace table size for the SNA
The TOPOSNA TRACE command is executed, but the topology manager was processed.
'SIZE' keyword is ignored.
Message Variables
Operator response number
The number of pages of memory (rounded to the
If internal tracing mode is desired, enter the
nearest page size), where one page equals 4096
'MODE=INT' and 'SIZE' keywords with the TOPOSNA
bytes
TRACE command (TOPOSNA
TRACE,MODE=INT,SIZE=number). Where, the variable
number is the number of pages (4096 bytes) of System action
memory you want for the internal trace buffer. If the trace table size is larger than the previous
FLB528I CMIP SERVICES RETRY utilized size, all previous internal trace entries remain
INTERVAL: interval in the table. If the trace table size is smaller than the
previously utilized size, only the most recent entries
that can fit in the new size are saved.
Explanation
Trace table size is applicable only when the SNA
As part of the TOPOSNA QUERYDEF output, this topology manager tracing mode is internal.
message indicates the time (in seconds) between the
attempts by the SNA topology manager to connect to
CMIP Services when the CMIP Services connection is Operator response
lost. This is an informational message that shows when the
Message Variables TOPOSNA TRACE MODE=INT,SIZE=number command
changes the trace table size. This command must be
interval queued to the FLBTOPO autotask. Its completion
Interval of time in seconds between retries might be delayed if the FLBTOPO autotask is busy
processing other TOPOSNA commands.
Operator response
FLB533W SNA TOPOLOGY MANAGER
If the CMIP Services retry interval is not set properly, INTERNAL TRACE TABLE SIZE
use the TOPOSNA SETDEFS CMPRETRY command to WAS NOT CHANGED
set the limit correctly.
FLB529I CMIP SERVICES RETRY LIMIT: Explanation
limit The requested SNA topology manager internal-trace
table size request was not processed because of a
Explanation storage shortage.
As part of the TOPOSNA QUERYDEF output, this
message indicates the maximum number of times the System action
SNA topology manager will attempt to connect to The internal-trace table size remains unchanged.
CMIP Services when the CMIP Services connection is
lost. Operator response
Message Variables Request less storage for the SNA topology manager
limit internal-trace table. Allowable size range is 10–999
The maximum number of retries pages, where each page is 4096 bytes.

To determine the current internal-trace table size, nodename
issue the TOPOSNA TRACE,QUERY command. The control point name of the agent node, or if you
were monitoring a logical link's LU collection, the
System programmer response name of the logical link
If a larger internal trace table size is required, but

System action
cannot be allocated within the current virtual-storage
limit of NetView program, increase the amount of Monitoring is started.
virtual storage allocated to NetView program.
FLB534E TOPOSNA requestparm COMMAND Operator response
HAS INCORRECT RODM OBJECT Look for message FLB552I to indicate that the initial
ID 'rodmobjectid' transfer of data on the LU collection has completed.
FLB541W OPERATOR operid STOPPED
Explanation
MONITORING LU COLLECTION
The operator issued a TOPOSNA operator command FROM nodename
with an incorrect RODM object identifier. The specified
object ID is not in RODM. Explanation
Message Variables The operator stopped monitoring all of the logical units
requestparm owned, controlled, supported by or directly attached
The name of the TOPOSNA request parameter to the specified node by issuing a TOPOSNA STOP
command. Monitoring stopped even if the initial
rodmobjectid transfer of LU collection data was not complete.
The RODM object identifier specified on the
operator command Message Variables
operid
System action The name of the operator who issued the
The command is ignored. TOPOSNA STOP command
nodename
Operator response The control point name of the agent node, or if you
Enter the command again with the correct RODM name of the logical link
object ID.
FLB540I REQUESTED MONITORING OF LU System action
COLLECTION FROM nodename Monitoring is stopped.
Explanation FLB542E MONITORING OF THE LU

COLLECTION FROM NODE
The manager has sent the agent node a request to nodename FAILED
monitor its LU collection, or, if the specified node is a
logical link, the logical link's LU collection. The agent
Explanation
responds with an initial transfer of data. When
response is complete, the SNA topology manager The SNA topology manager cannot start the
issues message FLB552I. Following the initial transfer, monitoring of the LU collection associated with the
the agent node sends updates as they occur. specified node, cannot complete the initial transfer of
Monitoring continues until the TOPOSNA STOP LU collection data, or lost communications with the
operator command is issued or the monitor time agent node after the initial transfer was complete. The
specified on the TOPOSNA MONITOR operator error is considered unrecoverable and no retry occurs.
command expires. If the SNA topology manager is
The probable cause of the error is a system error at the
stopped and warm-started, it resumes monitoring
agent node.
automatically.
Message Variables
Message Variables
nodename
The control point name of the agent node, or if you
name of the logical link

Monitoring ends and no retry occurs. See the messages in the NetView log to diagnose the
error. If the error is because the time interval specified
Operator response on the MAXREPLY parameter of the NETVIEW
See the messages in the NetView log to diagnose the interval in order to reduce the frequency of this
error. If you are unable to fix the problem, notify your condition. Otherwise, no action is necessary in
system programmer. response to this message. If the SNA topology
manager cannot restart the monitoring, it will issue
System programmer response message FLB542E or FLB545E.
See the messages in the NetView log and to the IBM Z FLB544W MONITORING OF THE LU
NetView Troubleshooting Guide to diagnose and COLLECTION FROM NODE
correct the error. Refer also to the system error log at nodename WILL BE RETRIED
the agent node to determine whether an agent system
error occurred; if it did, take the appropriate action to Explanation
fix the problem at the agent node. Then restart
monitoring of the LU collection. If necessary, contact The SNA topology manager cannot start the
IBM Software Support. monitoring of the LU collection associated with the
specified node. The error is considered recoverable
FLB543W MONITORING OF THE LU and retries begin at the end of the first LU collection
COLLECTION FROM NODE retry interval. The SNA topology manager retries until
nodename IS BEING RETRIED it successfully completes the initial transfer, exceeds
the LU collection retry limits, or encounters an
Explanation unrecoverable error. The retry intervals and limits are
specified on the TOPOSNA SETDEFS operator
The SNA topology manager started monitoring the LU
command.
collection associated with the specified node, but
either cannot complete the initial transfer of LU The probable cause of the error is:
collection data, or lost communications with the agent
node after the initial transfer was complete. The error
cannot be established, or the session failed and
is considered recoverable and retry occurs
immediately. The SNA topology manager retries until it
successfully completes the initial transfer, exceeds • The agent node does not have a topology agent
the retry limits for LU collection, or encounters an installed and running.
unrecoverable error. The retry limits are specified on • The specified node does not exist in the network, or
the TOPOSNA SETDEFS operator command. the node name was not typed correctly on the
The probable cause of the error is: TOPOSNA MONITOR operator command.
• The agent node is not powered on or it does not exist
• The session from the NetView host to the agent node
in the network.
failed.
• The topology agent program has been stopped. Message Variables
• The time interval specified on the MAXREPLY nodename

parameter of the NETVIEW DEFAULTS command The control point name of the agent node, or if you
expired before the initial transfer of LU collection were monitoring a logical links' LU collection, the
data was complete. name of the logical link
Message Variables
System action
nodename
The SNA topology manager will begin retrying after the
The control point name of the agent node, or if you
LU collection retry interval.
name of the logical link
Operator response
System action No action is necessary in response to this message.
However, if the SNA topology manager cannot start
The SNA topology manager immediately begins
the monitoring, it issues message FLB542E or
retrying.
FLB545E. You can force a new attempt to start

monitoring the LU collection at any time with the correct the error. Then, monitor the LU collection
TOPOSNA MONITOR operator command. Otherwise, again. If necessary, contact IBM Software Support.
the SNA topology manager tries to restart the
FLB546I SNA LU COLLECTION IMMEDIATE
monitoring at intervals specified on the RETRY
RETRY INTERVAL: defaultset
parameter of the TOPOSNA SETDEFS operator
command.
Explanation
FLB545E MONITORING OF LU COLLECTION
FROM NODE nodename FAILED This message shows the default setting for the
ALL RETRIES immediate retry time interval in seconds for
monitoring a node's LU collection. When the SNA
topology manager fails to complete the initial transfer
Explanation
of LU collection data for a given node, the SNA
The SNA topology manager cannot restart the topology manager retries at the indicated interval of
monitoring of the LU collection associated with the time.
specified node. The error is considered recoverable,
Message Variables
but the SNA topology manager has exhausted the LU
collection retry limits. The retry limits are specified on defaultset
the TOPOSNA SETDEFS operator command. The default setting for the immediate retry time
interval for monitoring a node's LU collection
The probable cause of the error is:
FLB547I SNA LU COLLECTION IMMEDIATE
cannot be established, or the session failed and RETRY LIMIT: defaultset
Explanation
• The agent node does not have a topology agent
installed and running. This message shows the default setting for the
• The specified node does not exist in the network, or immediate retry limit for monitoring a node's LU
the node name was typed incorrectly on the collection. When the SNA topology manager fails to
TOPOSNA MONITOR operator command. complete the initial transfer of LU collection data for a
given node, the SNA topology manager retries up to
• The agent node is not powered on or it does not exist the indicated number of retries. The default setting
in the network. indicated in the message is the upper limit for the
Message Variables number of retries.
nodename Message Variables
The control point name of the agent node, or if you defaultset
were monitoring a logical link's LU collection, the The default setting for the immediate retry limit for
name of the logical link monitoring a node's LU collection
System action FLB548I SNA LU COLLECTION LONG-TERM

RETRY INTERVAL: defaultset
Monitoring is not restarted.
Explanation
Operator response
This message shows the default setting for the long
See the messages in the NetView log to diagnose the term retry time interval in seconds for monitoring a
error. node's LU collection. When the SNA topology manager
You might be able to start monitoring the LU collection fails to complete the initial transfer of LU collection
later from the agent. Issue a TOPOSNA QUERYDEF data for a given node and exceeds the number of
operator command to determine if the retry limits immediate retries allowed, it retries at the indicated
must be increased. If you are unable to correct the long-term interval of time.
problem, notify your system programmer. Message Variables
defaultset
The default setting for the long term retry time
See the messages in the NetView log and to the IBM Z interval for monitoring a node's LU collection
NetView Troubleshooting Guide to diagnose and
FLB549I SNA LU COLLECTION LONG-TERM
RETRY LIMIT: defaultset

This message shows the default setting for the long- Messages FLB554I, FLB555I, FLB556I, FLB557I, and
term retry limit for monitoring a node's LU collection. FLB558I follow this message.
When the SNA topology manager fails to complete the
FLB554I STORAGE SIZE ALLOCATED USED
initial transfer of LU collection data for a given node
ALLOCATED USED %
and exceeds the number of immediate retries allowed,
it retries up to the indicated long-term limit. The
default setting indicated in the message is the upper Explanation
limit of the number of retries. This message is the first line of the header that results
Message Variables from the TOPOSNA LISTPOOL command to list SNA
topology manager internal storage-pool statistics. This
defaultset message is part of a multiple-line message.
The default setting for the long term retry limit for
monitoring a node's LU collection
System action
FLB552I INITIAL TRANSFER OF LU
COLLECTION DATA FROM NODE
nodename IS COMPLETE FLB555I TYPE IN BYTES COUNT COUNT
STORAGE-K STORAGE-K USED
Explanation
The SNA topology manager has requested data on all Explanation
logical units owned, controlled, supported by or This message is the second line of the header that
directly attached to the specified node (its LU results from the TOPOSNA LISTPOOL command to list
collection) as a result of the TOPOSNA MONITOR SNA topology manager internal storage-pool statistics.
operator command, or because the SNA topology This message is part of a multiple-line message.
manager restarted monitoring during its warm-start
processing. It has received all of the initial transfer of System action
data from the agent node, and SNA topology manager
has processed and stored topology data in the RODM Message FLB556I follows this message.
data cache; updates might also have been received.
FLB556I ----------- --------- --------- ---------
The agent node continues to send updates to the
--------- --------- ----
manager as they occur, until monitoring is stopped by
issuing the TOPOSNA STOP operator command.
Explanation
Message Variables
This message is the third (last) line of the header that
nodename results from the TOPOSNA LISTPOOL command to list
The target name of the agent node SNA topology manager internal storage-pool statistics.
This message is part of a multiple-line message.
System action
Monitoring continues until a TOPOSNA STOP System action
command is issued, the time specified on the Multiple FLB557I messages follow this message.
MONTIME parameter of the TOPOSNA MONITOR
command expires, or an error occurs that stops the FLB557I storagetype size allocated-count
monitoring. used-count allocated-storage used-
storage percentage-used
FLB553I SNA TOPOLOGY MANAGER
STORAGE POOL STATISTICS Explanation
FOLLOW
Explanation the TOPOSNA LISTPOOL command that lists SNA
topology manager internal storage-pool statistics. This
This is the first message in response to the TOPOSNA message is part of a multiple-line message.
LISTPOOL operator command. The TOPOSNA
LISTPOOL command lists SNA topology manager Message Variables
internal storage-pool statistics. The end of the
storage-pool statistics is indicated with message
FLB558I.

storagetype Explanation
The storage subpool type. The actual name of the
This message is the first line of the header for the
type will vary depending upon the internal storage
output from the TOPOSNA LISTREQS command that
structure.
lists the outstanding monitors. The outstanding
size monitors are a result of the TOPOSNA MONITOR
The size of the storage structure in bytes. operator command. This message is part of a multiple-
allocated-count line message.
The number of allocated storage structures of this NODE NAME
type. The control point name of the agent node. This is
used-count the value entered for the NODE parameter of the
The number of used storage structures of this TOPOSNA MONITOR operator command.
type. LOCAL NAME
allocated-storage The name of the logical link that the LU collection
The amount of storage in kilobytes allocated for is processing. This value is entered for the
this storage type. LCLNAME parameter for the TOPOSNA MONITOR
LUCOL operator command.
used-storage
The used amount of storage in kilobytes allocated MONITOR TYPE
for this storage type. The type of monitor being processed. The possible
types include: NETWORK, LOCAL, and LUCOL,
percentage-used
The ratio of used storage to allocated storage for which are entered on the TOPOSNA MONITOR
operator command.
this storage type expressed as a percentage.
MONITOR STATUS
System action The status of the monitor being processed. The
possible statuses include: REQUESTED,
Message FLB558I follows multiple FLB557I messages INCOMPLETE, COMPLETE and RETRY. For a
to indicate the end of data for the TOPOSNA LISTPOOL definition of these statuses, see message
command. FLB564I.
FLB558I END OF STORAGE POOL MONITOR TIME
STATISTICS-------------------------- The time that this monitor is in effect, or the time
----------- remaining before another retry of a monitor will
occur.
Explanation
System action
The display of SNA topology manager internal storage
pool statistics is complete. Message FLB562I follows this message.
FLB560I SNA TOPOLOGY MANAGER FLB562I NAME NAME TYPE STATUS TIME
PENDING REQUESTS FOLLOW:
Explanation
Explanation This message is the second line of the header for the
This is the first message in response to the TOPOSNA output from the TOPOSNA LISTREQS command that
LISTREQS operator command, which lists the pending lists the outstanding monitors. The outstanding
requests the topology manager currently has with its monitors are a result of the TOPOSNA MONITOR
agent nodes. The messages containing the information operator command. This message is part of a multiple-
about the pending requests follow this message. The line message.
topology manager issues message FLB411I when it NODE NAME
has finished listing the information about its pending The control point name of the agent node. This is
requests or message FLB576I if there are no pending the value entered for the NODE parameter of the
requests. TOPOSNA MONITOR operator command.
FLB561I NODE LOCAL MONITOR MONITOR LOCAL NAME
MONITOR The name of the logical link that the LU collection
is processing. This value is entered for the
LCLNAME parameter for the TOPOSNA MONITOR
LUCOL operator command.

MONITOR TYPE monitortype
The type of monitor being processed. The possible The type of monitor being processed. The possible
types include: NETWORK, LOCAL, and LUCOL, types include: NETWORK, LOCAL, and LUCOL,
which are entered on the TOPOSNA MONITOR which are entered on the TOPOSNA MONITOR
operator command. operator command.
MONITOR STATUS monitorstatus
The status of the monitor being processed. The The status of the monitor being processed. The
possible statuses include: REQUESTED, possible statuses include: REQUESTED,
INCOMPLETE, COMPLETE and RETRY. For a INCOMPLETE, COMPLETE and RETRY.
definition of these statuses, see message REQUESTED
FLB564I. The SNA topology manager has not yet
MONITOR TIME received any of the initial transfer of topology
The time that this monitor is in effect, or the time data from the agent.
remaining before another retry of a monitor will INCOMPLETE
occur. The SNA topology manager has received some
of the initial transfer of topology data from the
System action agent node, but not all of it.
Message FLB563I follows this message. COMPLETE
The SNA topology manager has received all of
FLB563I ------------ ------- ------- -------- the initial transfer of topology data from the
-------------------- agent node, and might have also received
some topology updates.
Explanation
RETRY
This message is the third line of the header for the The SNA topology manager cannot start
output from the TOPOSNA LISTREQS command that monitoring the topology from the specified
lists the outstanding monitors. The outstanding agent node, or it started monitoring the
monitors are a result of the TOPOSNA MONITOR topology from the agent node and cannot
operator command. This message is part of a multiple- complete the initial transfer of data, or it lost
line message. communication with the agent node after the
initial transfer was complete.
System action monitortime
LISTREQS data for outstanding monitors follows this The time that this monitor is in effect, or the time
message. remaining before another retry of a monitor will
occur.
FLB564I nodename localname monitortype
x MINUTES
monitorstatus monitortime
The monitor time-out value, in minutes,
specified on the MONTIME parameter of the
Explanation TOPOSNA MONITOR operator time. If the
This message is one of the data items in response to monitor status is REQUESTED or INCOMPLETE,
the TOPOSNA LISTREQS command that will list this timer has not started. The timer will start
outstanding monitors that are being processed. This when the SNA topology manager has received
message is part of a multiple-line message. all of the initial transfer of topology data from
the agent node. If the monitor status is
Message Variables COMPLETE, the time is the remaining amount
nodename of time, in minutes, until the SNA topology
The control point name of the agent node. This is manager stops monitoring the topology from
the value entered for the NODE parameter of the the agent node. You can issue the TOPOSNA
TOPOSNA MONITOR operator command. STOP operator command to stop the
monitoring before time expires.
localname
The name of the logical link that the LU collection x SECONDS
is processing. This value is entered for the The remaining time, in seconds, until the SNA
LCLNAME parameter for the TOPOSNA MONITOR topology manager will retry to start monitoring
LUCOL operator command. the topology from the agent node.

CONTINUOUS Explanation
The agent node continues to send updates to
The SNA topology manager storage-pool support
the manager as they occur, until monitoring is
encountered an internal processing error. A storage
stopped by issuing the TOPOSNA STOP
location was overlaid.
operator command.
Message Variables
System action type
LISTREQS data for outstanding monitors is included in The value GET or FREE to indicate the storage
this message. operation during which the overlay was detected
hexaddr
FLB565I END OF MONITOR
The hex address of the storage location in error
REQUESTS---------------------------
----------- storagetype
The storage type name, which will match one of
the storage types listed by the TOPOSNA
Explanation
LISTPOOL command
The display of outstanding monitors from the
LISTREQS command is complete. System action
FLB566E SNA TOPOLOGY MANAGER SNA topology manager issues a user abend X'186',
DETECTED A DOUBLE FREE AT dump, then ends.
ADDRESS hexaddr FOR STORAGE
TYPE storagetype
Operator response
The SNA topology manager storage-pool support

encountered an internal processing error; a storage
location was freed twice. Contact IBM Software Support; this message is only
issued for a program defect.
Message Variables
FLB575I nodename RECYCLE PORT
hexaddr
The hex address of the storage location in error portname
storagetype
Explanation
The storage type name, that will match one of the
storage types listed by the TOPOSNA LISTPOOL The operator issued a TOPOSNA RECYCLE command.
command The SNA topology manager has instructed the agent
node to recycle the logical link. When this message is
System action issued, the topology manager has not received a
response from the agent node indicating that the link
SNA topology manager issues a user abend X'186', has been recycled.
dump, then ends.
Message Variables
Operator response nodename
portname
The name of the port as it is known to the agent
node
Contact IBM Software Support; this message is only
issued for a program defect. FLB576I NO SNA TOPOLOGY MANAGER
REQUESTS PENDING
DETECTED A type STORAGE Explanation
OVERLAY AT ADDRESS hexaddr
FOR STORAGE TYPE storagetype This is a message in response to the TOPOSNA
LISTREQS operator command, which lists the pending
requests the topology manager currently has with its

agent nodes. There are no requests currently pending Explanation
at this time.
FLB577I SNA TOPOLOGY MANAGER the TOPOSNA LISTSTOR command that will list
STORAGE USAGE FOLLOWS: topology manager storage usages. This message is
part of a multiple-line message.
This is the first message in response to the TOPOSNA resource
LISTSTOR operator command, which lists the internal The storage resource type, which might
topology manager storage usage. The messages correspond to a RODM object class.
containing the information about the storage usages
follow this message. The topology manager issues The following RESOURCE TYPE entries do NOT
message FLB582I when it has finished listing the correspond to RODM object classes, and only the
information about its storage usages. COUNT1 column, the TOTAL STORAGE-K, and
TOTAL MAXIMUM-K columns have data.
FLB578I RESOURCE CACHE1 CACHE2
AttrSets
TOTAL TOTAL
Attribute Sets, an internal representation of
the fields (attributes) of a RODM object. The
Explanation COUNT column represents the current number
This message is the first line of the header for the of allocated Attribute Sets.
output from the TOPOSNA LISTSTOR command that X-AttrSets
lists the internal topology manager storage usages. Extended Attribute Sets, extra storage for
This message is part of a multiple-line message. attributes when the standard (above) version
of attribute sets is not large enough to hold all
System action of an objects attributes.
Message FLB579I follows this message. CritLUs

Critical LUs. The COUNT column represents the
FLB579I TYPE COUNT1 STORAGE-K current number of Critical LUs being
COUNT2 STORAGE-K STORAGE-K monitored.
MAXIMUM-K NodeTable
Internal node lookup cache. The COUNT
Explanation column represents the current number of node
This message is the second line of the header for the table entries.
output from the TOPOSNA LISTSTOR command that RodmMain
lists the topology manager storage usages. This RODM interface storage. The COUNT column
message is part of a multiple-line message. will always be 1.
StatHist
System action Status History entries. The COUNT column
indicates how many objects are currently
maintaining a status history.
FLB580I -------- ------ --------- ------ -------- Heap
-------- --------- SNA topology manager C run-time heap
utilization. The COUNT column indicates how
Explanation many storage requests are currently allocated
from the heap.
This message is the third line of the header for the
output from the TOPOSNA LISTSTOR command that The following RESOURCE TYPE entries correspond
lists the topology manager storage usages. This to RODM object classes, and all columns are filled
message is part of a multiple-line message. in. Note that some entries represent multiple
RODM classes that share common storage. For
System action instance, the TG/Circuit entry represents both TGs
and Circuits for both the APPN and subarea
LISTSTOR data follows this message. versions.
FLB581I resource count1 cache1stor count2 CDRM
cache2stor totstor maxstor Cross Domain Resource Manager objects.

DefGroup objects, represents the total count of that object
Definition group objects. currently active in CACHE1 (note this value might
EN differ from the COUNT2 field).
End node objects. cache1stor
ICN The amount of storage (in kilobytes) currently
Interchange node objects. utilized by the RESOURCE TYPE in CACHE1.
LEN count2
Low Entry Networking objects. For the resources that do not correspond to RODM
objects, no entry is made. For the resources that
MDH do correspond to RODM objects, represents the
Migration Data Host objects. total count of that object currently active in
NN CACHE2 (note this value might differ from the
Network node objects. COUNT1 field).
SnaNode cache2stor
SNA Node objects. The amount of storage (in kilobytes) currently
T2.1 utilized by the RESOURCE TYPE in CACHE2.
T2.1 objects. totstor
T4 The total amount of storage currently utilized by
T4 objects. the RESOURCE TYPE (note that for resources that
have CACHE1 and CACHE2 entries, this value is
T5 the total of the CACHE1 and CACHE2 values).
T5 objects.
maxstor
VRN The maximum amount of storage that this
Virtual routing node objects. RESOURCE TYPE has utilized (the highwater mark).
Link
Logical link objects. System action
LU LISTSTOR data for topology manager storage usages is
Logical unit objects (includes logical unit, LU included in this message.
group, and Cross Domain Resource RODM
classes). FLB582I END OF SNA TOPOLOGY
Port MANAGER STORAGE
Port objects. USAGE--------------------
TG/Circuit
Transmission group and transmission group Explanation
circuit objects (includes both subarea and The display of topology manager storage usages from
APPN). the LISTSTOR command is complete.
IntDomCirc FLB583W TOPOSNA MONITOR COMMAND
InterDomain circuit objects. FOR LU COLLECTION AT LOGICAL
IntNetCirc LINK linkname IS TERMINATED
InterDomainNetwork Circuit Objects. BECAUSE THE LU COLLECTION IS
nnDomain BEING MONITORED FROM SSCP
nnDomain objects. sscpname
nnDomNet
nnDomainNetwork objects. Explanation
SnaLocal A monitor for the LU collection residing at a logicalLink

SnaLocal topology objects. was previously requested. Then the local topology
from the same agent was requested. The SNA
TOTAL
Topology Manager discovered that this logicalLink is
Totals.
multiply-owned. Thus, the logicalLink needs to be
count1 converted from a non-multiply-owned resource to a
For the resources that do not correspond to RODM multiply-owned resource. However, the multiply-
objects, represents the total count of that resource owned resource already has LU collection monitoring
type. For resources that do correspond to RODM occurring from another agent node. Thus, the LU

collection is ended by the topology manager. Note that Explanation
in message FLB541W, which follows this message, the
The SNA topology manager is already monitoring the
operator will be 'FLBTOPO' because the SNA Topology
LU collection of this logicalLink from a different SSCP
Manager is forcing the stop monitor of the LU
than the current TOPOSNA MONITOR command is
collection.
requesting. A logicalLink can be owned by more than
Message Variables one SSCP, but only one monitor for the LU collection is
allowed.
linkname
The name of the non-multiply-owned logicalLink If the TOPOSNA command was entered by selecting
whose LU collection monitoring was requested, in the logicalLink object on an NMC screen, the SNA
the form of netid.sscpname.linkname topology manager will determine the SSCP name to
sscpname use for logicalLinks that can be owned by more than
The name of the SSCP that is already monitoring one SSCP. The SNA topology manager selects the
the LU collection for this multiply-owned SSCP name to use by examining the status history
logicalLink. records for this logicalLink and using the first SSCP
name that reports this logicalLink as active. If the
SSCP name is not the one that you want, you can
System action override this name by specifying the SSCP name in a
The TOPOSNA STOP command is executed for the LU TOPOSNA MONITOR command, as shown below:
collection at agent nodeName1 for logicalLink
TOPOSNA MONITOR,LUCOL,NODE=netid.sscpname,
linkname. LCLNAME=linkname
Operator response Be sure to stop the monitoring of the LU collection

from the current SSCP name if you desire to monitor
If you want to monitor the LU collection from the agent
the LU collection from a different SSCP name.
name in the first two parts of linkname, you must first
stop the monitoring of the LU collection from the agent Message Variables
named sscpname. Use the following TOPOSNA STOP
linkname
command to perform this task:
The name of the logicalLink whose LU collection
TOPOSNA STOP,LUCOL,NODE=netid.sscpname, monitoring was requested, in the form of
LCLNAME=linkname netid.sscpname.linkname
sscpname
Caution: The above command might stop the
The name of the SSCP that is already monitoring
monitoring of an LU collection that was requested by
the LU collection for this logicalLink.
another operator.
FLB584I COMPLETED MONITORING LU System action
COLLECTION DATA FROM NODE
nodename The TOPOSNA command is ignored.
The SNA topology manager has completed the If you want to monitor the LU collection from the SSCP
requested monitoring of the LU collection at the name that you entered (or was selected for you; see
specified node. the explanation above), you must first stop the
monitoring of the LU collection from the previous SSCP
Message Variables name. Use the following TOPOSNA STOP command to
nodename perform this task:
The name of the node whose LU collection the SNA TOPOSNA STOP,LUCOL,NODE=netid.sscpname,
topology has completed monitoring. LCLNAME=linkname
FLB585E TOPOSNA MONITOR COMMAND Caution: The TOPOSNA STOP command might stop
FOR LU COLLECTION AT LOGICAL the monitoring of an LU collection that has been
LINK linkname IS IGNORED requested by another operator.
BECAUSE THE LU COLLECTION IS
ALREADY BEING MONITORED FLB586E TOPOSNA STOP COMMAND
FROM SSCP sscpname IGNORED BECAUSE LU

COLLECTION OF NODE nodename TOPOSNA MONITOR,LUCOL,NODE=netid.sscpname,
IS NOT BEING MONITORED LCLNAME=linkname
Explanation FLB588E SNA TOPOLOGY MANAGER'S

MONITORING OF CRITICAL LU
The SNA topology manager is not monitoring the LU luname FAILED
collection of the specified node. The request to stop
monitoring is ignored.
Explanation
Message Variables
This message might indicate either of two situations:
nodename
• The topology manager attempted to begin
The name of the node whose LU collection
monitoring a logical unit or cross domain resource
monitoring was asked to be stopped.
that you identified as critical (it is to be monitored
continuously); however, the attempt failed. The
System action failure might be caused by one of the following
The TOPOSNA command is ignored. reasons:
FLB587E TOPOSNA MONITOR COMMAND – The logical unit or cross domain resource that you
FOR LU COLLECTION AT LOGICAL specified in the TOPOSNA CRITICAL command
LINK linkname IS IGNORED does not exist in the network.
BECAUSE THE LOGICAL LINK IS – No session with the agent has been established or
MULTIPLY OWNED AND THERE IS an existing session has failed.
NO STATUS HISTORY AVAILABLE – There is no agent at the node to which the monitor
TO SUPPLY THE SSCP NAME request was directed.
– The agent at the node to which the monitor
Explanation request was directed is inactive or has failed.
The SNA topology manager was requested to monitor – The topology manager has an internal failure.
the LU collection at a logicalLink. An object ID was
• The topology manager was monitoring a critical
specified on the TOPOSNA command. The logicalLink
logical unit or cross domain resource, but the
was determined to be potentially owned by more than
monitor has failed. The failure might be caused by
one SSCP at a time. The name for this object in RODM
one of the following reasons:
does not contain an SSCP name for the agent to which
commands will be sent. Therefore, the SNA topology – The resource is a dynamically created cross
manager queried its status history cache to find the domain resource that has been inactivated.
agent that last reported this logicalLink as active. – The session with the agent has failed.
However, the SNA topology manager had no status
history entries in its cache for this resource, because – The topology manager has an internal failure.
no topology agent has reported status on this object Message Variables
since the SNA topology manager was initialized.
luname
Message Variables The name of the critical logical unit or cross
linkname domain resource that the topology manager was
The name of the logicalLink, the monitoring of monitoring or attempted to monitor.
whose LU collection was requested as
netid.linkname. System action
Topology manager processing continues, but the
System action specified logical unit, cross domain resource will not
The TOPOSNA command is ignored. be monitored.
If you know the SSCP name to which you want this If the resource in question was a dynamically created
command sent, provide the SSCP name on the cross domain resource, no action is required; you
TOPOSNA command, as shown: might however want to determine whether the
inactivation was appropriate. Otherwise, check the
accuracy of the logical unit or cross domain resource

name that you entered in the TOPOSNA CRITICAL System action
command. If there is a typographical error, correct it
SNA topology manager lists the logicalUnits and
and enter the command again. If it is correct and you
crossDomainResources that it is monitoring
believe that the problem comes from one of the other
continuously, along with the status of each monitor.
reasons listed in the explanation above, notify your
system programmer. FLB591I RESOURCE NAME RESOURCE
TYPE MONITOR STATUS
Explanation
Review the diagnostic messages in the NetView log. If
indicated in the diagnostic messages, check the node As part of a multiple-line message, this message is the
that was the intended target of the monitor request header for the output from the TOPOSNA CRITICAL
and the communications to that node. If a topology LIST command. That command lists the logicalUnits
manager internal failure is indicated, notify IBM and crossDomainResources that SNA topology
Software Support. manager is monitoring continuously and the status of
those monitors. The columns contain the following
FLB589E SNA TOPOLOGY MANAGER COULD
information:
NOT LOCATE OR CREATE NODE
nodename INTERNALLY RESOURCE NAME
The full name of the resource being monitored.
Explanation RESOURCE TYPE
The type of the resource being monitored. Possible
The SNA topology manager's attempt to create an
values are LU (logicalUnit) and CDRSC
internal representation of the specified node failed,
(crossDomainResource).
possibly because of a lack of storage.
MONITOR STATUS
Message Variables The status of the monitor being processed. The
nodename possible statuses include MONITORING,
The name of the node for which the topology REQUESTED, FAILED, and INITIALIZED. For an
manager attempted to created an internal explanation of these statuses, see the message
representation description for FLB593I.
Topology manager processing continues, but Processing continues.

operations that are in progress relating to the specified
FLB592I ----------------------------------------
node will be ended.
------------- -----------------
Operator response
Explanation
As part of a multiple-line message, this message is the
second line of the header for the output from the
System programmer response TOPOSNA CRITICAL LIST command.
Check for a storage shortage. If this is indicated, take
the appropriate measures to relieve the shortage. If System action
there is no storage shortage, collect all available
A list of the logicalUnits and crossDomainResources
diagnostic information from the NetView log and notify
that the SNA topology manager is monitoring
continuously follows this message.
FLB590I SNA TOPOLOGY MANAGER FLB593I resname restype monstat
CRITICAL LU LIST FOLLOWS:
Explanation
Explanation
As part of a multiple-line message that is the output
The operator has asked the SNA topology manager to from the TOPOSNA CRITICAL LIST command, this
list all the logicalUnits and crossDomainResources message displays information relating to one of the
that it is monitoring continuously. That list follows. logicalUnits or crossDomainResources that the SNA
topology manager is monitoring continuously.

resname Processing continues.
The full name of the resource.
FLB596I MONITORING OF CRITICAL LU
restype luname ALREADY REQUESTED OR
The resource type. Possible values are: LU IN PROGRESS
(logicalUnit) and CDRSC (crossDomainResource).
monstat Explanation
The status of the monitor. Possible values are:
You asked the SNA topology manager to start
MONITORING continuous monitoring of the specified resource. The
SNA topology manager issued the monitor monitor for this resource is active and data is being
request and has received data in response reported, or SNA topology manager has requested
REQUESTED data from the agent for the resource but has not yet
SNA topology manager has issued the monitor received a response.
request, but has not received a response Message Variables
FAILED
luname
SNA topology manager's attempt to monitor
The name of the logicalUnit or
the resource failed
crossDomainResource that you asked SNA
INITIALIZED topology manager to monitor continuously
SNA topology manager is preparing to issue
the monitor request, but has not yet issued it.
System action
Processing continues. FLB597I OPERATOR operid STOPPED

MONITORING OF CRITICAL LU
FLB594I END OF CRITICAL LU luname
LIST-----------------------------------
----------
Explanation
Explanation At the request of the specified operator, SNA topology

manager has stopped continuous monitoring of the
The display of logicalUnits and crossDomainResources specified resource.
that the SNA topology manager is monitoring
continuously has completed. Message Variables
operid
System action The operator ID of the operator who requested
SNA topology manager to stop continuous
monitoring of the specified resource.
FLB595I REQUESTED MONITORING OF luname
CRITICAL LU luname The name of the logicalUnit or
crossDomainResource that SNA topology manager
Explanation has stopped monitoring continuously.
In order to begin continuous monitoring, SNA topology
manager has issued the appropriate commands to the System action
agent for the specified resource. No response has Processing continues.
been received yet.
FLB598I SNA TOPOLOGY MANAGER IS NOT
Message Variables CURRENTLY MONITORING ANY
luname CRITICAL LUS
crossDomainResource that SNA topology manager Explanation
has begun continuous monitoring
You requested a list of logicalUnits and
crossDomainResources that the SNA topology
manager is continuously monitoring. Currently, the

SNA topology manager is not continuously monitoring numbytes
these resources. The number of bytes of data associated with this
error.
System action
System action
Depends on the error.
FLB599I luname NOT FOUND AMONG
CRITICAL LUS
Explanation See the preceding messages in the NetView log in
conjunction with this message, and to messages
You asked the SNA topology manager to stop FLB603I and FLB604I, if present, to determine the
continuous monitoring of the specified logicalUnit or cause of the failure. See IBM Z NetView
crossDomainResource. The SNA topology manager did Troubleshooting Guide for more information on the
not find that resource among the logicalUnits and cause of the error and the format of the log data and
crossDomainResources that it is monitoring take corrective action.
continuously.
FLB601W PROBEID probeid MAJOR CODE
Message Variables
majcode MINOR CODE mincode
luname LOG DATA SIZE : numbytes BYTES
crossDomainResource that you asked SNA Explanation
topology manager to stop monitoring
This message contains information associated with an
error detected by a component of the SNA topology
System action
manager. The message is sent only to the NetView log.
Processing continues. This message is associated with errors from which the
component attempts to recover by taking error-
FLB600E PROBEID probeid MAJOR CODE specific actions.
majcode MINOR CODE mincode
LOG DATA SIZE : numbytes BYTES If log data is associated with this log entry, FLB601W
is the first part of a multiple-line message. The other
Explanation messages that make up this multiple-line message
(FLB603I and FLB604I) contain the data associated
This message contains information associated with an with this error. If log data is not associated with this
error detected by a component of the SNA topology log entry, FLB601W is the only message logged for this
manager. The message is sent only to the NetView log. error.
If log data is associated with this log entry, FLB600E is Message Variables
the first part of a multiple-line message. The other
messages that make up this multiple-line message probeid
(FLB603I and FLB604I) contain the data associated The internal identification used by IBM Software
with this error. If log data is not associated with this Support. All messages for a log entry specify the
log entry, FLB600E is the only message logged for this same value.
error. majcode
The major code identifies the class of error and
Message Variables
component.
probeid mincode
The internal identification used by IBM Software The minor code identifies the specific type of error.
Support. All messages for a log entry specify the
same value. numbytes
The number of bytes of data associated with this
majcode error.
The major code identifies the class of error and
component.
System action
mincode
The minor code identifies the specific type of error. Depends on the error.

System programmer response Message FLB603I logs some of the data associated
with the error or event indicated by those messages.
See the preceding messages in the NetView log in
Additional FLB603I messages might follow, depending
conjunction with this message, and to messages
on the amount of additional data associated with the
FLB603I and FLB604I, if present, to determine the
error or event being logged. The final piece of the data
cause of the failure. See the IBM Z NetView
is logged by message FLB604I, which also indicates
Troubleshooting Guide for more information on the
the end of the multiple-line message.
cause of the error and the format of the log data, and
take corrective action. Message Variables
FLB602I PROBEID probeid MAJOR CODE probeid
majcode MINOR CODE mincode The internal identification used by IBM Software
LOG DATA SIZE : numbytes BYTES Support. All messages for a log entry specify the
same value.
Explanation offset
Identifies what part of the additional data is
This message contains information associated with a
supplied by this message. This is the byte offset of
normal event. The SNA topology manager component
the beginning of the data in this message within
logs this message only to the NetView log. This
the additional data.
message is logged, for example, when the topology
manager receives APPN local topology data from an data
agent node, and the data contains an attribute the Up to 32 bytes of data. The data from this message
topology manager does not support. and from any additional FLB603I messages is
combined with the data contained in the related
If log data is associated with this log entry, FLB602I is message FLB604I to provide additional data
the first part of a multiple-line message. The other associated with the error or event.
messages that make up this multiple-line message
(FLB603I and FLB604I) contain the data associated
with this event. If log data is not associated with this
log entry, FLB602I is the only message logged for this See the first message in this multiple-line message
event. (either FLB600E, FLB601W, FLB602I) for the
appropriate response. Combine the data contained in
Message Variables
this message with the data from other related FLB603I
probeid messages, if present, and with the data in FLB604I to
The internal identification used by IBM Software obtain the additional data associated with the error or
Support. All messages for a log entry specify the event.
same value.
FLB604I PROBEID probeid DATA offset:
majcode data
The major code identifies the component.
mincode Explanation
The minor code identifies the type of information.
This message is the final part of a multiple-line
numbytes
message begun by message FLB600E, FLB601W, or
The number of bytes of data associated with this
FLB602I. Message FLB604I logs the last (or only)
event.
piece of data associated with the error or event
indicated by those messages.
Message Variables
See messages FLB603I and FLB604I, if present, to
obtain the data associated with this event. See IBM Z probeid
NetView Troubleshooting Guide for more information The internal identification used by IBM Software
on the event and the format of the log data. Support. All messages for a log entry specify the
same value.
FLB603I PROBEID probeid DATA offset: offset
data Identifies what part of the additional data is
supplied by this message. This is the byte offset of
Explanation the beginning of the data in this message within
This message is a part of a multiple-line message the additional data.
begun by message FLB600E, FLB601W, or FLB602I.

data command
Up to 32 bytes of data. This data is combined with The name of the command
the data contained in related FLB603I messages, if requestparm
present, to provide the additional data associated The name of the request parameter the operator is
with the error or event. not authorized to use

See the first message in this multiple-line message The command is ignored.
(either FLB600E, FLB601W, FLB602I) for the
appropriate response. Combine this data with the data
Operator response
contained in related FLB603I messages, if present, to
obtain the additional data associated with the error or Notify your system programmer if you need authority
event. to issue this command.
FLB610I TASK taskname IS STARTING
LOGOFF PROCESSING System programmer response
If appropriate, give the operator authority to use this
The task is starting its logoff processing in order to FLB613E OPERATOR 'operid' IS NOT
ensure that any connections to other components are AUTHORIZED TO ISSUE THE
properly disconnected. command requestparm COMMAND
Message Variables WITH PARAMETER 'parameter'
taskname Explanation
The name of the task that is logging off
The operator issuing the SNA topology manager
System action (TOPOSNA) command is not authorized to use the
indicated parameter of this command.
The task begins its logoff processing.
Message Variables
FLB611I TASK taskname HAS COMPLETED
operid
ITS LOGOFF PROCESSING
The operator identification of the operator issuing
the command
Explanation
command
The task has completed its logoff processing. The name of the command
Message Variables requestparm
The name of the request parameter
taskname
The name of the task that has logged off parameter
The parameter name the operator is not
authorized to use
System action
The task ends. System action
FLB612E OPERATOR 'operid' IS NOT The command is ignored.
AUTHORIZED TO ISSUE THE
command requestparm COMMAND Operator response
Explanation Issue the command without this parameter if the

parameter is not required for the command. Notify
The operator issuing the SNA topology manager your system programmer if you need authority to use
(TOPOSNA) command is not authorized to do so. this parameter of the command.
Message Variables
operid
The operator identification of the operator issuing If appropriate, give the operator authority to use this
the command parameter of the command.

FLB614E OPERATOR 'operid' IS NOT Operator response
AUTHORIZED TO ISSUE THE Determine whether the autotask is already started and
command requestparm COMMAND operational. If it is, no further action is required. If the
WITH PARAMETER 'parameter'
autotask is started but it is not operational, wait for the
AND VALUE 'value'
autotask to end, or issue the EXCMD taskname,
LOGOFF command to send the autotask a logoff
Explanation command. After the autotask ends, or if the autotask is
The operator issuing the SNA topology manager not started, issue the AUTOTASK OPID=taskname
(TOPOSNA) command is not authorized to use the command to start the autotask. Otherwise, notify your
indicated value of this parameter and command. system programmer.

operid See error messages in the NetView log to determine
The name of the operator issuing the command the cause of the error. Correct the error and start the
command autotask.
FLB617E AN UNEXPECTED RETURN CODE
requestparm 'return_code' WAS RECEIVED
The name of the request parameter WHEN AN AUTHORIZATION
parameter CHECK WAS MADE FOR THE
The name of the parameter 'cmdname' 'requestparm'
value COMMAND
The value the operator is not authorized to use
Explanation
System action The specified operator command cannot be processed
The command is ignored. because of an unexpected error during a command
authorization check.
Issue the command without this value or with a return_code
different value on the parameter. Notify your system The return code from the CNMSCOP service
programmer if you need authority to use this value on cmdname
the parameter and command. The name of the SNA topology manager
(TOPOSNA) command
System programmer response requestparm
If appropriate, give the operator authority to use this The name of the request parameter
value on the parameter and command.
System action
FLB615E AUTOMATED START OF TASK
taskname FAILED The command is ignored.

The automation command list FLBCMIPA tried to start Notify the person in your organization responsible for
the autotask indicated in the message and failed all security administration that you are unable to issue
retry attempts. The probable cause is that the the command.
autotask is already started.
taskname Check the NetView log to determine if any other

The name of the autotask messages were issued that give an indication of what
error occurred. See IBM Z NetView Programming: PL/I
and C for a description of the CNMSCOP return code. If
System action
the cause of the error cannot be determined, contact
The command list FLBCMIPA does not start the IBM Software Support.
autotask.

FLB620E SNA TOPOLOGY MANAGER REASON
ENCOUNTERED AN ERROR ON A The RODM reason code.
CALL TO RODM OBJECTID
The RODM object ID. This is the object ID that the
Explanation SNA topology manager method was processing
when the RODM MAPI error occurred.
This message is the first line of a heading for a
multiple-line message. This multiple-line message is DISPLAY RESOURCE NAME
displayed when an RODM MAPI error has been The name of the resource that the SNA topology
detected by the SNA topology manager method. manger method was processing when the RODM
MAPI error occurred.
System action
System action
Message FLB621E or FLB622E follows this message.
Message FLB624E follows this message.
FLB621E MAPI ERROR WAS ENCOUNTERED
IN THE STATUS METHOD FLB624E ---- -- ------ ----------------
---------------------
Explanation
Explanation
This message is the second line of a heading for a
multiple-line message. This multiple-line message is This message is the fourth line of a heading for a
displayed when an RODM MAPI error has been multiple-line message. This multiple-line message is
detected by the status method of the SNA topology displayed when an RODM MAPI error has been
manager. detected by the SNA topology manager.
Message FLB623E follows this message. RODM MAPI error data follows this message.
FLB622E MAPI ERROR WAS ENCOUNTERED FLB625E function_id return_code

IN THE EXCEPTION VIEW reason_code objectid drn
METHOD
Explanation
Explanation This message is one of the RODM MAPI errors that the
This message is the second line of a heading for a SNA topology manager method detected. This
multiple-line message. This multiple-line message is message is part of a multiple-line message.
displayed when an RODM MAPI error has been Message Variables
detected by the exception view method of the SNA
topology manager. function_id
The RODM function ID that the SNA topology
manager was executing when the RODM MAPI
System action
error occurred.
Message FLB623E follows this message. return_code
FLB623E F_ID RC REASON OBJECTID The RODM return code that the SNA topology
DISPLAY RESOURCE NAME manager received when an RODM MAPI function
was executing. This variable contains NA when the
RODM return code is not available to the SNA
Explanation
topology manager. This can occur for query field
This message is the third line of a heading for a and trigger object independent customer method
multiple-line message. This multiple-line message is RODM functions.
displayed when an RODM MAPI error has been reason_code
detected by the SNA topology manager. The heading The RODM reason code that the SNA topology
explanations follow: manager received when an RODM MAPI function
F_ID was executing. When the RODM function is query
The RODM function ID. field (1501), the reason code is an internal code
RC rather than a RODM reason code.
The RODM return code.

objectid Operator response
The RODM objectid of the object that the SNA
topology manager was processing when the RODM
MAPI error occurred. This variable contains NA
when the RODM MAPI error occurred when System programmer response
processing a RODM class rather than an RODM See the IBM Z NetView Resource Object Data Manager
object. and GMFHS Programmer's Guide for the return code
drn and reason code and, if possible, take corrective
The DisplayResourceName of the object that the action. Otherwise, contact IBM Software Support.
SNA topology manager was processing when the
FLB627E END OF MAPI RODM ERROR
RODM MAPI error occurred. This variable contains
DISPLAY--------------------------
the RODM class name when the RODM MAPI error
occurred when processing a RODM class rather
than a RODM object. Explanation
The display of RODM MAPI errors that were detected
System action by the SNA topology manager method is complete.
For query field, query multiple subfield, and change FLB628E ADDITIONAL MAPI ERRORS HAVE
multiple field RODM functions, the method stops BEEN DETECTED BUT NOT
executing the current object. For trigger object DISPLAYED
independent customer method RODM function, the
SNA topology manger method execution continues. Explanation
For query multiple subfield and change multiple field
RODM functions, this might cause the current SNA The SNA topology manager method detected
topology manager operation (such as a TOPOSNA additional RODM MAPI errors, but is not able to
MONITOR) to end; or if the error is severe, this might display the details of these additional errors. This
cause the SNA topology manager to end. message is part of a multiple-line message.

Notify your system programmer. Notify your system programmer.

See the IBM Z NetView Resource Object Data Manager See the IBM Z NetView Resource Object Data Manager
and GMFHS Programmer's Guide for the return code and GMFHS Programmer's Guide for the return code
and reason code and, if possible, take corrective and reason code displayed in message FLB625E of
action. Otherwise, contact IBM Software Support. this multiple-line message. If possible take corrective
action and retry the operation. This operation can be a
FLB626E ABOVE REASON CODE TOPOSNA MONITOR, TOPOSNA CRITICAL, TOPOSNA
ENCOUNTERED WHEN INVOKING REFRESH EXVIEW CLASS=, or NMC Locate Resource.
USER METHOD method_name If corrective action is not possible, contact IBM
Software Support.
Explanation
This message provides more information for an RODM RECEIVED AN INVALID RESPONSE
MAPI error that was displayed in message FLB625E. BLOCK FROM METHOD
Message FLB626E is displayed when the SNA topology method_name FOR DRN drn
manager method attempted to trigger an object OBJECTID objectid
independent customer method. This message is part
of a multiple-line message. Explanation
Message Variables The SNA topology manager exception view RODM
method_name method invoked a customer exception view method
The name of the customer object independent successfully; however, the response block returned by
method that the SNA topology manger method the customer method is not valid.
attempted to invoke. Message Variables

method_name FLB631E SNA TOPOLOGY MANAGER
The name of the customer object independent DISCOVERED THAT RODM
method rodm_name IS OUT OF STORAGE
drn
The DisplayResourceName of the object being Explanation
processed when the SNA topology manager
The SNA topology manager received a RODM reason
exception view method detected the incorrect
code that indicates that RODM is out of storage.
response block.
objectid Message Variables
The RODM objectid of the object being processed rodm_name
when the SNA topology manager exception view The name of the RODM that the SNA topology
method detected the incorrect response block. manager is using

The response block from the customer method is The SNA topology shuts down.
ignored. Processing continues using the exception
views defined in the FLBEXV initialization file. Operator response
System programmer response Correct the shortage of storage in RODM and restart
the SNA topology manager, or restart the SNA
Verify that the customer method is formatting the topology manager and reduce the number of
RODM response block as documented in the sample C resources that the SNA topology must be monitoring.
header file FLBTREM.
FLB636W THE TRACE REQUEST SPECIFIES
FLB630E SNA TOPOLOGY MANAGER THAT TRACING BE TURNED ON
RECEIVED MULTIPLE RESPONSE BUT THE GTF TRACE CATEGORY
BLOCK ERRORS FROM CUSTOMER 'tracecat' IS NOT ACTIVE
METHODS DURING EXCEPTION
VIEW PROCESSING Explanation
Explanation The TOPOSNA TRACE request specified ON for

category 05E8. However, the attempt to start tracing
The SNA topology manager exception view RODM on GTF failed, because either GTF is not started or the
method invoked a customer exception view method GTF trace category is inactive.
successfully; however, the SNA topology manager
method detected more than one response block error Message Variables
from more than one invocation of the customer tracecat
method. This first response block error is displayed in The GTF trace category for the TOPOSNA TRACE
message FLB629E. The incorrect response block command, which is 05E8.
might be from the same method as displayed in
FLB629E or might be a different customer method. System action
Operator response The command is ignored, and tracing is not turned on.
System programmer response If GTF is not started, start it. Otherwise, start the GTF
trace category.
Correct the problem that was displayed in message
FLB629E. Then issue TOPOSNA REFRESH EXVIEW FLB637E TASK taskname FAILED TO WRITE
CLASS= to invoke the customer method again. TRACE DATA USING GTF
BECAUSE OF AN ERROR

An error occurred when the task taskname attempted The SNA topology manager responded to a request
to write trace data using GTF. from the CNMTAMEL task. However, when the
topology manager sent the response to CNMTAMEL,
Message Variables
CNMTAMEL responded with an error condition.
taskname
The task from which the trace command was Operator response
issued
System action
The trace data is discarded.
Operator response
correct the error. If necessary, contact IBM Software
Notify your system programmer. Support.
System programmer response ENCOUNTERED AN INCLUDE
See error messages in the NetView log, and take ERROR 'code' IN CUSTOMIZATION
appropriate action. TABLE table WITH ENTRY 'record'
FLB650I MONITOR SNA NETWORK

Explanation
TOPOLOGY FOR NEW T5 NODES:
defaultset SNA topology manager encountered an error
processing an include statement in the specified table.
This message shows the default setting for whether code
the topology manager must automatically monitor the The error code returned from CNMMEMR
SNA network topology for newly-discovered t5 nodes. (CNMREADMEM).
The default setting indicated in the message is YES or
table
NO.
The table for which this message was generated.
Message Variables record
defaultset The record which was in error. This record might
The default setting for monitoring SNA network be from an included member.
topology from t5 nodes
System action
FLB651I MONITOR SNA LOCAL TOPOLOGY
FOR NEW T5 NODES: defaultset The SNA topology manager continues initialization and
ignores the entry.
Explanation
Operator response
This message shows the default setting for whether
the topology manager must automatically monitor the Notify your system programmer.
SNA local topology for newly discovered t5 nodes. The
default setting indicated in the message is YES or NO. System programmer response
Message Variables Correct the error in the table using information from
defaultset the return code. See IBM Z NetView Programming: PL/I
The default setting for monitoring SNA local and C for CNMMEMR return codes to help diagnose the
topology from t5 nodes problem. The problem might be in an included
member.
FLB652E A FAILURE OCCURRED WHEN THE
SNA TOPOLOGY MANAGER SENT FLB661W SNA TOPOLOGY MANAGER
DATA TO TASK CNMTAMEL CUSTOMIZATION TABLE
membername CONTAINS A
KEYWORD 'keyword' WITH A NULL
VALUE

Explanation keyword
The keyword in the table that has an incorrect
The SNA topology manager customization table
value assigned to it.
as: value
The incorrect value that was specified for the
KEYWORD="value" keyword.
The keyword indicated in the message has no value

System action
assigned to it.
The SNA topology manager skips the record and
Message Variables
continues processing. The internal table will be
membername created with missing data.
The DSIPARM member name of the table that has
a keyword in error: FLBOSIDS for the OSI-Display Operator response
status table, FLBSRT for the Status Resolution
table, or FLBEXV for the Exception View table. Notify your system programmer.
keyword
The keyword in the table that has no value System programmer response
assigned to it Change the customization table so that the keyword
has a valid value specified. Run the TOPOSNA
System action REFRESH command to create the table again.
The SNA topology manager skips the record and FLB663W SNA TOPOLOGY MANAGER
continues processing. The internal table will be CUSTOMIZATION TABLE
created with missing data. membername CONTAINS THE
KEYWORD 'keyword' MULTIPLE
Operator response TIMES WITH THE SAME VALUE
'value' FOR OBJECT CLASS class
Explanation
Change the customization table so that the keyword includes keywords and associated values expressed
has a valid value specified. Run the TOPOSNA as:
REFRESH command to create the table again.
KEYWORD="value"
CUSTOMIZATION TABLE The keyword indicated in the message was specified
membername CONTAINS A multiple times for the object class contained in the
KEYWORD 'keyword' WITH AN message.
INCORRECT VALUE 'value'
Message Variables
Explanation membername
a keyword in error: FLBOSIDS for the OSI-Display
as:
table, or FLBEXV for the Exception View table.
KEYWORD="value" keyword
The keyword in the table that was specified
The keyword indicated in the message has an incorrect multiple times.
value assigned to it.
value
Message Variables The value for keyword that was specified multiple
times.
membername
The DSIPARM member name of the table that has class
a keyword in error: FLBOSIDS for the OSI-Display The object identifier of the class for which the
status table, FLBSRT for the Status Resolution keyword was specified multiple times.

The duplicate keyword and associated value is The SNA topology manager customization table
ignored. The first keyword and value for that object includes keywords and associated values expressed
class is used. Processing continues. as:
KEYWORD="value"
Operator response
Notify your system programmer. The keyword indicated in the message is not a valid
keyword.
Change the customization table so that the keyword is membername
not duplicated for that object class. Run the TOPOSNA The DSIPARM member name of the table that has
REFRESH command to create the table again. a keyword in error: FLBOSIDS for the OSI-Display
CUSTOMIZATION TABLE
membername CONTAINS A keyword
SYNTAX ERROR, DATA 'entry' The incorrect keyword in the table.

Data was entered incorrectly in a SNA topology The SNA topology manager skips the record in error
manager customization table. and continues processing. The internal table will be
created with missing data and might incorrectly
Message Variables associate entries directly following the record in error,
membername with the wrong object class or resource.
a syntax error: FLBOSIDS for the OSI-Display Operator response
table, or FLBEXV for the Exception View table. Notify your system programmer.
entry
The entry in the table that contained the syntax
error. Change the customization table so that the keyword
specified is a valid keyword. Run the TOPOSNA
System action REFRESH command to create the table again.
SNA topology manager skips the record and continues FLB666W SNA TOPOLOGY MANAGER
processing. The internal table will be created with CUSTOMIZATION TABLE
missing data and might incorrectly associate entries membername DOES NOT CONTAIN
directly following the record-in-error with the wrong ALL REQUIRED OBJECT CLASSES
object class or resource.
Explanation
Operator response One or more required object classes are missing from
Notify your system programmer. a SNA topology manager customization table.
Message Variables
membername
Change the customization table to correct the syntax The DSIPARM member name of the table that does
error. Run the TOPOSNA REFRESH command to create not contain all required object classes: FLBOSIDS
the table again. for the OSI-Display status table, FLBSRT for the
Status Resolution table, or FLBEXV for the
Exception View table.
CUSTOMIZATION TABLE
membername CONTAINS AN
INVALID KEYWORD 'keyword' System action
The SNA topology manager continues processing. The
internal table will be created with missing data.

Statuses or views associated with the missing object resource IN CLASS class, BUT WAS
classes might result in defaults that you might not NOT FOUND IN CUSTOMIZATION
want. For example, if the object class is missing from TABLE membername (statesIn-
the OSI-Display status table, statuses received from statesOut)
an agent for a resource in that object class defaults to
the unknown display statuses. Explanation
The SNA topology manager received an OSI status
Operator response
from an agent or Resource Status Focal Point for a
Notify your system programmer. resource in the object class specified in the message.
However, that OSI status was not found in the
System programmer response customization table specified in the message.
Change the customization table to include the missing Message Variables

object classes. Run the TOPOSNA REFRESH command status
to create the table again. The OSI status that was received from an agent or
FLB667W SNA TOPOLOGY MANAGER Resource Status Focal Point. Browse member
CUSTOMIZATION TABLE FLBOSIDS for a description of the OSI status.
membername DOES NOT SPECIFY The OSI status might have been overridden by a
A DEFAULT SET OF OSI/DISPLAY customer-provided RODM method. See the IBM Z
STATUS MAPPINGS FOR OBJECT NetView SNA Topology Manager Implementation
CLASS class Guide for a description on how to specify methods
to override OSI status in the FLBOSIDS or FLBSRT
Explanation initialization files.
The initialization file FLBOSIDS does not contain a An asterisk means that the SNA topology manager
default set of OSI to DisplayStatus mappings for the cannot interpret the OSI status. If the
object class listed in the message. This occurs when administrativeState, operationalState, or
all sets of OSI to DisplayStatus mappings for this usageState contains a value that is not valid, a
object class contain the RESOURCE keyword. There single asterisk is specified in its place. If
must be one set of OSI to DisplayStatus mappings availabilityStatus or proceduralStatus contain a
without the RESOURCE keyword as the default set for X'FF', '*AS*' or '*PS*' are specified respectively. If
this object class. any of the right three bits of procedurealStatus are
'1'b, '**' is specified for each bit that is '1'b. If
Message Variables unknownStatus contains a value other than X'00'
membername or X'01', '*UN*' is specified.
The DSIPARM member name of FLBOSIDS resource
class The name of the resource for which the status was
The object class that is missing in the information received.
class
System action The name of the class that did not contain the OSI
The SNA topology manager continues processing. The status specified in the message.
SNA topology manager internal copy of the FLBOSIDS membername
table will be created with missing data. The DSIPARM member name of the table that did
not contain the OSI status: FLBOSIDS for the OSI-
Operator response Display status table or FLBSRT for the Status
Resolution table.
statesIn
The hexadecimal representation of the OSI status
System programmer response that was received from an agent or Resource
Change the customization table FLBOSIDS to include Status Focal Point, and sent to the SNA topology
the set of OSI to DisplayStatus mappings for the object manager status method to calculate the
class listed in the message. Run the TOPOSNA DisplayStatus. If the resource is potentially
REFRESH command to create the table again. multiply owned, this value is also used to resolve
the overall status.
FLB668W AN OSI STATUS OF 'status' WAS
RECEIVED FOR RESOURCE

Some of the values might contain a X'FF' which Explanation
means that the SNA topology manager will use the
The CNMTAMEL task is either not active or not a focal
previous value reported. A value of X'FE' for
point.
nativeStatus will force the nativeStatus to a resting
state of X'FF', which means that it is not currently
set. See the 'states' field in the IBM Z NetView Data System action
Model Reference for a description of this value. The SNA topology manager continues processing.
This insert is not decoded and placed in the status
insert. Operator response
statesOut Contact your system programmer.
The hexadecimal representation of the OSI status
that was actually used to calculate the System programmer response
DisplayStatus and resolved status (if the resource
is multiply-owned). Start the CNMTAMEL task as a focal point if you
require status updates to be forwarded from the
When membername is FLBOSIDS and the resource Resource Status Collectors and if you need the
is multiply-owned, this is the unresolved status workstation to communicate with GMFHS.
used to find a match in the FLBOSIDS table. When
membername is FLBOSIDS and the resource is not FLB670I SNA TOPOLOGY MANAGER HAS
multiply-owned, this is the value used after all ESTABLISHED COMMUNICATIONS
X'FF' values were replaced with the previous value. WITH THE RESOURCE STATUS
FOCAL POINT
When membername is FLBSRT, this is the OSI
status that was received from an agent or
Resource Status Focal Point that was not located Explanation
in the FLBSRT table. The SNA topology manager has established or re-
If a user method was specified in the FLBOSIDS or established communication with the Resource Status
FLBSRT customization table, and the user method Focal Point.
has overridden the OSI status value, this is the
value after it was overridden and used to calculate System action
DisplayStatus and resolved status (if the resource The SNA topology manager will continue executing.
is multiply owned).
This is the value that was decoded and placed in
CUSTOMIZATION TABLE
the status insert.
membername DOES NOT SPECIFY
A DEFAULT STATUS HIERARCHY
System action FOR OBJECT CLASS class
If the status was not found in the FLBOSIDS table, the
display status is set to unknown. If the status was not Explanation
found in the FLBSRT table, the resolved status that
The initialization file FLBSRT does not contain a
was calculated might not be the correct status.
default status hierarchy for the object class listed in
the message. This status hierarchy is used to resolve
Operator response the status of a resource that can be reported by more
Notify your system programmer. than one topology agent. The warning condition occurs
when all the status hierarchies for this object class
also contain the RESOURCE keyword. There must be
one status hierarchy without the RESOURCE keyword
Change the customization table to include the OSI as the default status hierarchy for this object class.
status for the appropriate object class.
Message Variables
FLB669W SNA TOPOLOGY MANAGER membername
CANNOT COMMUNICATE WITH The DSIPARM member name of FLBSRT
THE RESOURCE STATUS FOCAL
POINT class
The object class that is missing the information

The SNA topology manager continues processing. The SNA Topology Manager received an error attempting to
SNA topology manager internal copy of the FLBSRT connect to VTAM CMIP Services.
table will be created with missing data.
Message Variables
Operator response retcode

The return code from a call to MIBConnect
retflag
The return flag from a call to MIBConnect
Change the customization table FLBSRT to include System action
default status hierarchy for the object class listed in
The SNA topology manager ends.
this message. Run the TOPOSNA REFRESH command
to create the customization table again.
Operator response
CUSTOMIZATION TABLE Notify your system programmer.
membername DOES NOT SPECIFY
A DEFAULT EXCEPTION VIEW System programmer response
NAME FOR OBJECT CLASS class
Refer to the appropriate manual in the z/OS
Communications Server library for the meaning of the
Explanation return code and flag.
The initialization file FLBEXV does not contain a FLB678W SNA TOPOLOGY MANAGER FAILED
default exception view name for the object class listed TO CONNECT TO CMIP SERVICES
in the message. This occurs when all the exception AND WILL RETRY, CMIP
view names for this object class also contain the SERVICES IS NOT ACTIVE
RESOURCE keyword. There must be one exception
view name without the RESOURCE keyword that will
Explanation
be the default exception view name for this object
class. The SNA topology manager received an error
attempting to connect to the VTAM CMIP services,
Message Variables
which indicated that the VTAM CMIP services are not
membername active.
The DSIPARM member name of FLBEXV
class System action
The object class that is missing the information
The SNA topology manager attempts to reconnect to
the VTAM CMIP services, based on the CMIP retry
System action value settings or until the TOPOSNA STOPMGR
The SNA topology manager continues processing. The command is issued.
SNA topology manager internal copy of the FLBEXV
table will be created with missing data. Operator response
Start VTAM CMIP services. When VTAM CMIP services
Operator response initialization is complete, the SNA topology manager
Notify your system programmer. will connect automatically.
System programmer response CUSTOMIZATION TABLE table
Change the customization table FLBSRT to include SPECIFIES EXVWNAME 'name'
default exception view name for the object class listed WHICH WAS NOT FOUND IN
in the message. Run the TOPOSNA REFRESH RODM
command to create the customization table again.
Explanation
TO CONNECT TO CMIP SERVICES SNA topology manager cannot find an Exception View
retcode, retflag in RODM with the name specified in FLBEXV.

table Correct the ExceptionViewName field in RODM so that
The table that specified the EXVWNAME keyword it is 8 characters or less. Refresh the table.
(FLBEXV).
name ENCOUNTERED AN ERROR 'code'
The value specified for the EXVWNAME keyword READING A RECORD FROM
which cannot be found as an ExceptionView in CUSTOMIZATION TABLE table
RODM.
Explanation
System action
SNA topology manager encountered an error reading a
The SNA topology manager continues initialization and record from the specified table.
ignores the entry.
Message Variables
Operator response code
The error code returned from CNMMEMR
(CNMREADMEM)
table
The table for which this message was generated
Correct the name of the view in FLBEXV so that it
matches an ExceptionView in RODM. The name is case System action
sensitive and must be an exact match. Refresh the
table. If the error occurred during SNA topology manager
initialization, the SNA topology manager ends. If the
FLB680W SNA TOPOLOGY MANAGER error occurred as a result of a TOPOSNA REFRESH
CUSTOMIZATION TABLE table command, the command processing ends but the SNA
SPECIFIES EXVWNAME 'name' topology manager continues.
WHICH CONTAINS AN INVALID
VALUE IN RODM FOR FIELD
Operator response
ExceptionViewName 'viewname'
Explanation
SNA topology manager cannot find the Exception View
indicated. However, the ExceptionViewName field is Correct the error in the table using information from
greater than 8 characters in length and cannot be the return code. See IBM Z NetView Programming: PL/I
used. and C for CNMMEMR (CNMREADMEM) return codes to
help diagnose the problem. The problem might be in
Message Variables
an included member.
table
The table that specified the EXVWNAME keyword
(FLBEXV) ENCOUNTERED AN ERROR 'code'
ATTEMPTING TO OPEN
name CUSTOMIZATION TABLE table
The value that is specified for the EXVWNAME
keyword, which was found in RODM
Explanation
viewname
The value of the ExceptionViewName field found in SNA topology manager encountered an error opening
RODM, which is too long the specified table.
Message Variables
System action
code
The SNA topology manager continues initialization and The error code returned from CNMMEMO
ignores the entry. (CNMOPENMEM)
table
Operator response The table for which this message was generated

If the error occurred during SNA topology manager The SNA topology manager will continue to initialize
initialization, the SNA topology manager ends. If the using the values as stated in the message.
error occurred as a result of a TOPOSNA REFRESH
command, the command processing ends but the SNA Operator response
topology manager continues.
Correct the FLBSYSD entry in error by changing the
keyword value to NO.
Operator response
DISCOVERED THAT CMIP
SERVICES IS TERMINATING
Correct the error in the table using information from Explanation
the return code. See IBM Z NetView Programming: PL/I
The SNA topology manager received an indication that
and C for CNMMEMO (CNMOPENMEM) return codes to
VTAM CMIP services is terminating.
diagnose the problem.
FLB683I SNA TOPOLOGY MANAGER System action
KEYWORD 'keyword' WITH A The SNA topology manager reinitializes and attempts
CONFLICTING VALUE OF 'value1'. to connect to the VTAM CMIP services, based on the
VALUE OF 'value2' IS USED CMIP retry value settings or until the TOPOSNA
STOPMGR command is issued.
Explanation
Operator response
This message relates to the FLBSYSD entries:
Restart VTAM CMIP services.
AGGREGATE_TO_CLUSTER
AGGREGATE_TO_NNDOMAIN_NETWORK FLB685W NO ACTIVE PATH TO NODE
AGGREGATE_TO_NNDOMAIN nodename OR CMIP SERVICES
NOT ACTIVE ON THIS NODE OR
The possible values for these keywords are YES and INCORRECT NODE NAME
NO. There is a hierarchy to the values. If
AGGREGATE_TO_NNDOMAIN has a value of NO, Explanation
AGGREGATE_TO_NNDOMAIN_NETWORK and
AGGREGATE_TO_CLUSTER must also have a value of Request for topology to node nodename has failed
NO. If AGGREGATE_TO_NNDOMAIN_NETWORK has a because of one or more of the following reasons:
value of NO, then AGGREGATE_TO_CLUSTER must • There is no active path or session between these two
have a value of NO. control points.
If this hierarchy is not followed, this message will be • The CMIP services might not be active on node
issued and a value of NO will be used where nodename, or CMIP services are not supported on
appropriate (SNA topology manager initialization will this control point.
continue with the substituted values).
• This message is also issued if the nodename is
Message Variables incorrect.
keyword Message Variables
One of the following keywords in FLBSYSD:
nodename
AGGREGATE_TO_CLUSTER The control point name of the node
AGGREGATE_TO_NNDOMAIN_NETWORK
AGGREGATE_TO_NNDOMAIN System action
value1 The SNA topology manager might retry this request.
This value is set to YES.
value2 System programmer response
This value is set to NO. Look at the NetView log for other messages. If the
nodename is incorrect, stop the topology request.

Issue the topology request again with the correct Message Variables
nodename. If the nodename is correct, see if there is
resource
an active path or session from this control point to the
The name of the resource that is entered in the
nodename in this message. If there is an active path or
locate resource window
session between the two control points check if the
CMIP services are active. If the CMIP services are not node
active on this nodename activate the CMIP services. The node to which the locate request was sent
For session related problems, refer to the appropriate
manual in the z/OS Communications Server library. System action
FLB686E SNA TOPOLOGY MANAGER DATA Resources that are found are returned to the operator.
MODEL IS NOT COMPLETELY
LOADED Operator response
If the desired resource was not found, and CMIP
Explanation
Services is active at the specified node, contact your
The SNA topology manager has been started and is system programmer.
initializing, but the SNA topology manager data model
is not completely loaded into RODM. After the data System programmer response
model is completely loaded, initialization of the SNA
topology manager continues. Look in the NetView log for related messages and
probe IDs to diagnose the problem.
System action FLB688I SNA TOPOLOGY MANAGER WAS
The SNA topology manager will retry the access to the UNABLE TO INDIVIDUALLY
RODM data cache based on the MONITOR 'luname', CMIP CREATE
RODM_RETRY_INTERVAL and RODM_RETRY_LIMIT EFD FAILED
values in initialization file FLBSYSD. If this message is
issued during a reinitialization, the values set by Explanation
TOPOSNA SETDEFS,RDMRETRY will be used instead of SNA topology manager cannot individually monitor the
the FLBSYSD values. specified LU because an error was received from the
CMIP CREATE EFD request.
Operator response
Message Variables
luname
The name of the Logical Unit that cannot be
System programmer response monitored
If the SNA topology data model is not currently
loading, load it into RODM. If the value of the System action
SUPER_CLUSTER_VIEW_NAME keyword in FLBSYSD
has been modified, the value in the MyName field of The resource is displayed with an unknown status.
the Network_View_Class in member FLBTRDMA must
also be modified (these values must be the same). Operator response
The GMFHS data model must be successfully loaded If this is a VTAM Logical Unit and CMIP Services is
prior to loading the SNATM data model. active at node specified in the luname, then contact
your system programmer. If this is not a VTAM logical
FLB687I SNA TOPOLOGY MANAGER Unit, then it cannot be monitored individually and this
ENCOUNTERED AN ERROR WHILE is normal processing.
ATTEMPTING TO LOCATE
RESOURCE 'resource' FROM NODE
'node'
Look in the NetView log for related messages and
Explanation probe IDs to diagnose the problem.
SNA topology manager encountered an error FLB689I SNA TOPOLOGY MANAGER WAS
processing the locate resource request. Resource UNABLE TO INDIVIDUALLY
might or might not have been returned in conjunction MONITOR 'luname', CMIP GET
with the request. FAILED

Explanation • An agent node first reports an adjacent node as
nodename1 and later reports this node as
SNA topology manager cannot individually monitor the
nodename2 with its subarea number information. If
specified LU because an error was received from the
netid is NETA and the subarea number is provided,
CMIP GET request.
the SNA topology manager replaces nodename1 in
Message Variables RODM with nodename2.
luname Message Variables
The name of the Logical Unit that cannot be
nodename1
monitored
The old node that is named by its subarea number
(netid.subarea_number).
System action
nodename2
The resource is displayed with an unknown status. The new node that is named by its real name
(netid.name).
Operator response class
If this is a VTAM Logical Unit and CMIP Services is The RODM class of the new node (nodename2).
active at node specified in the luname, then contact The new node can be created in the same class as
your system programmer. If this is not a VTAM logical the old node, or merged with an existing node that
Unit, then it cannot be monitored individually and this is already named with its real name.
is normal processing. rodmobjectid
The RODM object ID of the new node
System programmer response (nodename2).
Look in the NetView log for related messages and

System action
probe IDs to diagnose the problem.
The SNA topology manager deletes the existing object
FLB690I NODE nodename1 OF CLASS class named with its subarea number. The SNA topology
IS REPLACED WITH THE NODE manager either creates a new object in RODM with the
nodename2 WITH RODM OBJECT updated name in RODM in the same class as the old
ID rodmobjectid node, or merges the old node into the new node if the
new node already exists. The SNA topology manager
Explanation preserves the links of the old node to other objects in
The node was named with its subarea number in RODM.
RODM and is either replaced in RODM with its real The SNA topology manager does not copy customer-
name in the same RODM class, or is merged with the defined fields from the old object to the updated
new node if the new node already exists. For a VTAM object in RODM. Set the customer-defined fields for
node (t5Node in RODM), the new name is the SSCP the new RODM object; see the IBM Z NetView Resource
name of the VTAM node. For a NCP node (t4Node in Object Data Manager and GMFHS Programmer's Guide
RODM), the new name is the NCP name. for more information.
The SNA topology manager creates an object in RODM
named with its subarea number when the node is System programmer response
down level (VTAM release prior to V4R3, and NCP To enable the SNA topology manager to correctly
release prior to V7R1) and does not provide its real name the node even when only the subarea number is
name when contacting adjacent nodes (see IBM Z provided, code the SN_to_NM parameter in the
NetView SNA Topology Manager Implementation Guide FLBSYSD initialization file.
for more information). This change occurs when the
SNA topology manager receives updated information FLB691E NODE nodename IS AN END NODE,
about an existing node, where the new information NETWORK MONITORING IS NOT
provides the relationship between the subarea number SUPPORTED FOR END NODES
and the real name.
For example: Explanation
• The nodename1 named by netid.subarea (for A network monitor command was issued against node
example, NETA.00000001) nodename, but nodename is an end node and does not
support network monitors (only local monitors are
• The nodename2 named by netid.name (for example,
supported).
NETA.NCP1)

Message Variables • CMIP responses
nodename • CMIP rejects
The name of the target node • CMIP linked-replies
The following maps the SNA topology manager
System action internal error value to its corresponding CMIP
The network monitor command fails. value ASN.1 label.
ASN.1 label
Operator response Defined in
Issue a local monitor command (TOPOSNA MONITOR, 0
LOCAL,NODE=nodename) for topology information The error is not a recognized CMIP error. This
instead of a network monitor command. error is generated because either the SNA
topology manager did not recognize the error
FLB692W SNA TOPOLOGY MANAGER value in the received CMIP response, or CMIP
ENCOUNTERED A CMIP SERVICES services cannot send the request to the agent
ERROR. TARGET NAME node and generated an internal error.
'targetname'. SERVICE ERROR
CODE 'serviceErrorCode'. ERROR 1 unrecognizedAPDU
VALUE 'errorValue'. GENERIC OSI Remote Operations (ISO 8072)
VALUE 'genericValue'. SENSE 2 mistypedAPDU
CODE X'senseCode'. OSI Remote Operations (ISO 8072)
3 badlyStructuredAPDU
Explanation OSI Remote Operations (ISO 8072)
The SNA topology manager attempted to send a CMIP 4 duplicateInvocation
request to an agent to begin a monitor operation, end OSI Remote Operations (ISO 8072)
a monitor operation, or locate an LU using one of the 5 unrecognizedOperation
following: OSI Remote Operations (ISO 8072)
• NMC locate resource function 6 mistypedArgument
• TOPOSNA CRITICAL command OSI Remote Operations (ISO 8072)
7 resourceLimitation
The CMIP services responded with an error condition;
OSI Remote Operations (ISO 8072)
either the agent node or CMIP services rejected the
CMIP request. 8 initiatorReleasing
Message Variables
9 unrecognizedLinkedID
targetname OSI Remote Operations (ISO 8072)
The name of the node to which the SNA topology
10 linkedResponseUnexpected
manager attempted to send a request, or the name
of the resource that was the target of the request.
The name will have one of the following formats: 11 unexpectedChildOperation
• netid.CP_name
12 unrecognizedInvocation
• netid.CP_name.luName OSI Remote Operations (ISO 8072)
• netid.CP_name.netid.luName 13 resultResponseUnexpected
The first two parts of the name are the agent OSI Remote Operations (ISO 8072)
name. 14 mistypedResult
serviceErrorCode OSI Remote Operations (ISO 8072)
A return code provided by CMIP services. Refer to 15 errorResponseUnexpected
the appropriate VTAM manual for a description of OSI Remote Operations (ISO 8072)
this code.
16 unrecognizedError
errorValue OSI Remote Operations (ISO 8072)
The error value is an internal indicator used to map
17 unexpectedError
the CMIP error value into a contiguous set of error
codes. The error value can be received from:

18 mistypedParameter genericValue
OSI Remote Operations (ISO 8072) The processing failure error code is an internal
19 accessDenied indicator used to map the CMIP generic error
OSI CMIP (ISO 9596) values into a contiguous set of error codes. These
generic error values are optional and are supplied
20 classInstanceConflict when the CMIP request fails because of a
OSI CMIP (ISO 9596) processing failure (CMIP error value of
21 complexityLimitation processingFailure). The following maps the SNA
OSI CMIP (ISO 9596) topology manager internal generic error value to
22 duplicateManagedObjInstance its corresponding CMIP generic error ID (ASN.1
OSI CMIP (ISO 9596) label).
23 getListError CMIP Generic Error ID (ASN.1 label)

OSI CMIP (ISO 9596) ASN.1 Object Identifier
24 invalidArgumentValue 0
OSI CMIP (ISO 9596) The error response did not include a generic
error, or the SNA topology manager did not
25 invalidAttributeValue recognize it.
OSI CMIP (ISO 9596)
1 actionCancelled
26 invalidFilter 1.3.18.0.0.2253
OSI CMIP (ISO 9596)
2 associationLostError
27 invalidObjectInstance 1.3.18.0.0.2254
OSI CMIP (ISO 9596)
3 internalProcessingError
28 invalidScope 1.3.18.0.0.2255
OSI CMIP (ISO 9596)
4 memoryAllocationError
29 missingAttributeValue 1.3.18.0.0.2256
OSI CMIP (ISO 9596)
5 objectDeletedError
30 mistypedOperation 1.3.18.0.0.2257
OSI CMIP (ISO 9596)
6 resourceDefinitionError
31 noSuchAction 1.3.18.0.0.2258
OSI CMIP (ISO 9596)
7 stateCheckError
32 noSuchArgument 1.3.18.0.0.2259
OSI CMIP (ISO 9596)
8 createFailureNameBinding
33 noSuchAttribute 1.3.18.0.0.2261
OSI CMIP (ISO 9596)
9 createFailureNoNameBinding
34 noSuchEventType 1.3.18.0.0.2262
OSI CMIP (ISO 9596)
10 deleteFailureNameBinding
35 noSuchInvokeId 1.3.18.0.0.2263
OSI CMIP (ISO 9596)
11 deleteFailureContdObjs
36 noSuchObjectClass 1.3.18.0.0.2264
OSI CMIP (ISO 9596)
12 deleteFailureForContdObjs
37 noSuchObjectInstance 1.3.18.0.0.2265
OSI CMIP (ISO 9596)
13 snaDefinedError
38 noSuchReferenceObject 1.3.18.0.0.2266
OSI CMIP (ISO 9596)
14 resourceProcessingError
39 operationCancelled 1.3.18.0.0.2114
OSI CMIP (ISO 9596)
senseCode
40 processingFailure
The SNA sense code is provided when the request
OSI CMIP (ISO 9596)
is rejected because of a CMIP processing failure
41 setListError (CMIP error value of processingFailure) and the
OSI CMIP (ISO 9596) CMIP generic error value indicates the problem
42 syncNotSupported was a SNA-defined error. Use the NetView SENSE
OSI CMIP (ISO 9596)

command to obtain a description of the sense Message Variables
code, including possible causes of the problem.
probeid
The hexadecimal probe identifier for IBM Software
System action Support
The requested function fails. The SNA topology abendcode
manager continues to process other requests. If the The hexadecimal abend code that would have
function was initiated by an operator command, the been taken if the ABEND_AND_DUMP keyword in
operator receives an error message. FLBSYSD was set to YES
The SNA topology manager automatically retries
monitor operations that fail with the following CMIP System action
error values: The SNA topology manager initiates shutdown and
• complexityLimitation logoff.
• processingFailure, without a CMIP generic error
value System programmer response
• processingFailure, CMIP generic error ID = See the NetView log for other messages and log entry.
actionCancelled Contact IBM Software Support.
• processingFailure, CMIP generic error ID = FLB694E SNA TOPOLOGY MANAGER
associationLostError DETECTED A SEVERE ERROR
• processingFailure, CMIP generic error ID = CONDITION, ABEND X'abendcode'
memoryAllocationError TAKEN FOR FLBTOPO TASK,
PROBE probeid
• processingFailure, CMIP generic error ID =
stateCheckError
Explanation
• processingFailure, CMIP generic error ID =
snaDefinedError, sense code = X'00000000' The SNA Topology Manager has detected a severe
• processingFailure, CMIP generic error ID = processing error condition and an user abend
resourceProcessingError occurred. This user abend is taken when the
ABEND_AND_DUMP keyword is set to YES in the
• resourceLimitation FLBSYSD initialization file.
• initiatorReleasing
Message Variables
Operator response probeid

Hexadecimal probe identifier for IBM Software
Notify your system programmer. Support
abendcode
System programmer response Hexadecimal abend code
Use the CMIP error value, the CMIP generic error
value, and the SNA sense code to determine the cause System action
of the problem. Correct the problem and retry the
The topology manager abends.
operation.
FLB693E SNA TOPOLOGY MANAGER System programmer response
DETECTED A SEVERE ERROR
CONDITION, BUT A STORAGE See the NetView log for other messages and log entry.
DUMP WAS NOT REQUESTED, Contact IBM Software Support.
PROBE probeid ABEND CODE FLB695E SNA TOPOLOGY MANAGER FAILED
X'abendcode' ALL RETRIES WHEN CONNECTING
TO CMIP SERVICES
Explanation
The SNA Topology Manager has detected a severe Explanation
processing error condition but an user abend is not The CMIP Services connection retry limit has been
requested (FLBSYSD ABEND_AND_DUMP keyword is exceeded. This implies that the CMIP Services
set to NO). component of VTAM has not been started. This can be

verified by issuing the VTAM command D necessary. Start the CMIP Services component of
NET,VTAMOPTS, OPTION=OSIMGMT. VTAM.

The SNA topology manager ends. Check to ensure that the VTAM CMIP Services
component is started prior to starting the SNA
Operator response topology manager or within the retry parameters.
The TOPOSNA SETDEFS,CMPRETRY command can be

used to set the retry limit to a higher value if

Chapter 11. FLC Prefix Messages
FLC prefix messages are issued by MultiSystem Manager.

FLC000I MESSAGE message_number • MultiSystem Manager does not perform Network
ISSUED, BUT THIS MESSAGE topology initialization.
DOES NOT EXIST IN MESSAGE • MultiSystem Manager status changes to
TABLE DSIMDMFL - CALL INITIALIZATION_FAILED.
IGNORED
Operator response
Explanation
MultiSystem Manager attempted to issue the listed
message, but cannot find the message member
containing the message text.
Install a compatible version of MultiSystem Manager
Message Variables
or NetView and reissue the INITTOPO command.
message_number
FLC002E ALL GETTOPO COMMANDS FROM
The message number of the missing message
MULTISYSTEM MANAGER
INITIALIZATION FILE file_name
System action WILL NOT BE PROCESSED.
The message is not displayed.
Explanation
Operator response The MultiSystem Manager topology manager is
Notify the system programmer. ENABLED, but an error occurred during the second
phase of initialization.
If message_number is a user-coded message, add it to file_name
the message definition module. Otherwise, contact The name of the MultiSystem Manager
IBM Software Support. initialization file that is specified on the INITTOPO
command
FLC001E UNABLE TO INITIALIZE
MULTISYSTEM MANAGER.
MULTISYSTEM MANAGER version. System action
IS NOT COMPATIBLE WITH The GETTOPO commands coded in the referenced
NETVIEW version. RETURN CODE = MultiSystem Manager initialization file are not
return_code. processed.

The versions of MultiSystem Manager and NetView Contact your system programmer.
that are installed on your system are not compatible.
version Check the NetView log for messages FLC070E or
The version and release of MultiSystem Manager FLC076E. If they were issued, an error occurred while
and NetView attempting to create objects in RODM. See the
return_code description of messages FLC070E and FLC076E to
The return code from the module solve the problem.
It is also possible that other FLC messages were
System action generated if syntax errors were found in any of the
GETTOPO statements in the MultiSystem Manager
• MultiSystem Manager cancels the INITTOPO
command.

initialization file. Check the NetView log for other FLC command_name
messages and take appropriate action. The command that was issued
If messages FLC070E and FLC076E were not module_name
generated, all of the GETTOPO statements in the The name of the module that was running at the
MultiSystem Manager initialization file were coded time the error was discovered
incorrectly. Check the NetView log for associated FLC return_code
messages and take appropriate action. The return code from the module
Reissue the INITTOPO command once the problems
have been resolved. System action
FLC003I TRACE MODULE module_name. MultiSystem Manager cancels the command.

data.
Operator response
Explanation 1. Ensure that the service point name is spelled
This message is generated whenever YES, ALL, ENTRY, correctly.
or EXIT is entered for the GETTOPO TRACE= keyword. 2. If spelled incorrectly, fix the spelling error and
Message Variables reenter the command.
3. If this does not resolve the problem, or if the name
module_name
was spelled correctly:
The name of the module being traced by
MultiSystem Manager. a. Issue the appropriate GETTOPO xxxONLY
data command for the network for which you are
The trace information related to the option requesting topology data and status. This
specified on the TRACE= keyword. This is one or all retrieves the topology data and status and adds
of the following: it to RODM.
b. Retry the original command.
• For ALL, the trace information displayed for
ENTRY, EXIT, and YES. c. If the problem is still unresolved, contact your
system programmer.
• For ENTRY, the parameter list passed to the
module.
• For EXIT, the return code value when the module
is exited. Determine that the correct service point name is
specified on the GETTOPO command. Ensure that the
• For YES, the RUNCMD command issued by
topology information for this service point is in RODM.
module_name.
This is accomplished during MultiSystem Manager
FLC006E OBJECT REPRESENTING SERVICE initialization or by issuing a GETTOPO command.
POINT sp_name DOES NOT EXIST
FLC008E RUNCMD RETRY COUNT LIMIT OF
IN RODM. command_name
runcmd_retry_count EXCEEDED.
COMMAND ENDED IN MODULE
command_name COMMAND
module_name WITH RETURN
ENDED IN MODULE module_name
CODE return_code.
WITH RETURN CODE return_code.
Explanation
Explanation
A request was issued to retrieve topology data and
An error has occurred while processing a RUNCMD
status from a resource whose associated service point
command. The command has been retried the number
is not defined to RODM. The service point must be
of times set by the RUNCMDRETRY initialization
defined to RODM in order to send topology requests to
statement.
resources reporting to the topology agent associated
with this service point. Message Variables
Message Variables runcmd_retry_count
The retry count specified in the RUNCMDRETRY
sp_name
initialization file statement
The name of the service point to which the
command was sent command_name
The command that was issued

module_name last_valid_value
The name of the module that was running at the The value used in the last successful request.
time the error was discovered sp_name
return_code The name of the service point to which the
The return code from the module command was sent.
application.element
System action The name of the network management application
that processes the command string at this service
MultiSystem Manager cancels the command.
point. When multiple applications are supported
the format is application.element, where element is
Operator response the name of the subapplication running.
Examine the associated RUNCMD failure messages to
determine which commands have failed. Follow the System action
recommended actions to resolve the problem. If the
problem still exists, contact your System Programmer.
Operator response
• Change the RUNCMDRETRY parameter for your
network.
• Check the RUNCMD Timeout variable and update it if
appropriate. See the DEFAULTS COSTIME command Ensure the field_length is being calculated correctly
in IBM Z NetView Command Reference Volume 1 (A- and is greater than 1.
N) for information on changing this value.
FLC011W RESPONSE COMPLETE WITH
FLC010E FIELD NAME LENGTH field_length NETWORK ERRORS AT SERVICE
IS NOT VALID. FUNCTION = POINT sp_name WHILE
function, OBJECT CLASS = PROCESSING RUNCMD runcmd
object_class, OBJECT NAME =
object_name, LAST VALID FIELD = Explanation
last_valid_field last_valid_type
last_valid_value, SERVICE POINT = A NetWare network error occurred while processing a
sp_name, APPLICATION NAME = NetWare QUERY STATUS command.
application.element. Message FLCE041W is received in conjunction with
this message.
Explanation
Message Variables
This message is generated when the field_length
sp_name
specified has a value less than 1.
Message Variables command was sent.
field_length runcmd
The length of the field name. The RUNCMD command containing the QUERY
STATUS command.
function
The function to be performed on the target object.
System action
object_class
The RODM object class of the target object. The MultiSystem Manager agent remains operational
and GETTOPO commands are still processed.
object_name
The RODM object name of the target object.
Operator response
last_valid_field
The field name used in the last successful request. Issue the QUERY STATION ROUTES command at the
last_valid_type failing server. If this command completes with errors,
The RODM type used in the last successful the NetWare IPX diagnostic services might not be
request. completing successfully. Contact your NetWare
system administrator for assistance.
Chapter 11. FLC Prefix Messages 589

FLC012W GMFHS_AGGREGATE_ Explanation
OBJECTS_CLASS OBJECTS CAN This message is generated when the value_length
NOT USE THE DOMAIN LINK. specified is less than 1 and the field_name is a
SERVICE POINT = sp_name, reserved keyword for a field that requires data.
APPLICATION NAME =
application.element. COMMAND Message Variables
ENDED IN MODULE module_name. value_length
The length of the value to be added to RODM.
Explanation
function
This message is generated when the DOMAIN Link The function to be performed on the target object.
field is specified with a object_class
GMFHS_AGGREGATE_OBJECTS_CLASS Object. The RODM object class of the target object.
GMFHS does not support the domain link for its
aggregate class. The MSM System View classes do object_name
support the domain link for aggregate classes. The RODM object name of the target object.
field_name
Message Variables
The field name being used.
sp_name field_type
The name of the service point to which the The RODM type being used.
command was sent.
sp_name
application.element The name of the service point to which the
The name of the network management application command was sent.
point. When multiple applications are supported application.element
the format is application.element, where element is The name of the network management application
the name of the subapplication running. that processes the command string at this service
module_name the format is application.element, where element is
The name of the module that was running at the the name of the subapplication running.
time the error was discovered.
module_name
The name of the module that was running at the
System action time the error was discovered.
The MultiSystem Manager agent remains operational
and GETTOPO commands are still processed. System action
Operator response
Notify the system programmer. Operator response
Find where the domain link is being built and change System programmer response
either the class name or the link name depending on
what link is really wanted. Ensure the calculation for value_length is correct and
data is being sent for the field.
FLC013E FIELD VALUE LENGTH
value_length IS NOT VALID. FLC014E OBJECT NAME object_name WAS
FUNCTION = function, OBJECT SPECIFIED BEFORE ANY OBJECT
CLASS = object_class, OBJECT CLASS WAS SPECIFIED. SERVICE
NAME = object_name, FIELD = POINT = sp_name, APPLICATION
field_name field_type, SERVICE NAME = application.element.
POINT = sp_name, APPLICATION COMMAND ENDED IN MODULE
NAME = application.element. module_name.
module_name.

This message is generated when the object_name is
specified before the object class, when building a object_class
target object. The RODM object class of the target object.
Message Variables object_name
object_name
sp_name
sp_name command was sent.
application.element
command was sent.
The name of the network management application
application.element that processes the command string at this service
The name of the network management application point. When multiple applications are supported
that processes the command string at this service the format is application.element, where element is
point. When multiple applications are supported the name of the subapplication running.
module_name
the name of the subapplication running.
module_name time the error was discovered.
time the error was discovered. System action
System action MultiSystem Manager cancels the command.
MultiSystem Manager cancels the command. Operator response
System programmer response Ensure the value being sent for field_type matches the
data type defined in RODM for that field_name and the
Ensure the object class is being built before the object value sent for the field_value is of the same type.
name.
FLC016E OBJECT CLASS object_class WAS
FLC015E VALUE IS INCONSISTENT WITH SPECIFIED BEFORE A FUNCTION
DATA TYPE FOR FIELD field_name WAS SPECIFIED. FIELD =
field_type field_value. FUNCTION = field_name field_type field_value,
function, OBJECT CLASS = SERVICE POINT = sp_name,
object_class, OBJECT NAME = APPLICATION NAME =
object_name, SERVICE POINT = application.element, COMMAND
sp_name, APPLICATION NAME = ENDED IN MODULE module_name.
application.element. COMMAND
ENDED IN MODULE module_name. Explanation
Explanation A function describes the action to perform on a RODM

object. In the data stream, a function must be
This message is generated when the value sent by the specified before any objects to be used by that
agent for the field_value has a different data type than function are specified.
defined by the field_type value sent by the agent.
Message Variables
Message Variables
object_class
field_name The RODM object class of the target object.
field_name
field_type The field name being used.
The RODM type being used.
field_type
field_value The RODM type being used.
The value to be added to the RODM field.

field_value field_type
The value to be added to the RODM field. The RODM type being used.
sp_name field_value
The name of the service point to which the The value to be added to the RODM field.
command was sent. sp_name
application.element The name of the service point to which the
The name of the network management application command was sent.
that processes the command string at this service application.element
point. When multiple applications are supported The name of the network management application
the format is application.element, where element is that processes the command string at this service
the name of the subapplication running. point. When multiple applications are supported
module_name the format is application.element, where element is
The name of the module that was running at the the name of the subapplication running.
System action
System action
Operator response
Operator response
Ensure the option flag sent is one of the valid values
Ensure that a function is specified before an object. defined in the C toolkit or agent documentation.
FLC017E FLAG SPECIFIED FOR 'FROM' FLC018E FLAG SPECIFIED FOR OBJECT
FIELD link_from_field IN LINK CLASS link_class IN LINK
STRUCTURE IS NOT VALID. STRUCTURE IS NOT VALID.
FUNCTION = function, OBJECT FUNCTION = function, OBJECT
CLASS = object_class, OBJECT CLASS = object_class, OBJECT
NAME = object_name, FIELD = NAME = object_name, FIELD =
field_name field_type field_value, field_name field_type field_value,
SERVICE POINT = sp_name, SERVICE POINT = sp_name,
APPLICATION NAME = APPLICATION NAME =
application.element. application.element.
This message is generated when the option flag This message is generated when the option flag
specified for the link_from_field is not valid. The option specified for the link_class is not valid. The option flag
flag indicates the type of the value sent. specifies the type of value sent.
link_from_field link_class
The RODM link field name being used. The RODM link class.
function function
The function to be performed on the target object. The function to be performed on the target object.
object_class object_class
The RODM object class of the target object. The RODM object class of the target object.
object_name object_name
The RODM object name of the target object. The RODM object name of the target object.
field_name field_name
The field name being used. The field name being used.

field_type field_type
The RODM type being used. The RODM type being used.
field_value field_value
The value to be added to the RODM field. The value to be added to the RODM field.
sp_name sp_name
The name of the service point to which the The name of the service point to which the
command was sent. command was sent.
application.element application.element
The name of the network management application The name of the network management application
that processes the command string at this service that processes the command string at this service
point. When multiple applications are supported point. When multiple applications are supported
the format is application.element, where element is the format is application.element, where element is
the name of the subapplication running. the name of the subapplication running.

MultiSystem Manager cancels the command. MultiSystem Manager cancels the command.


Ensure the option flag sent is one of the valid values Ensure the option flag sent is one of the valid values
defined in the C toolkit or agent documentation. defined in the C toolkit or agent documentation.
FLC019E FLAG SPECIFIED FOR OBJECT FLC020E FLAG SPECIFIED FOR 'TO' FIELD
NAME = link_object IN LINK link_to_field IN LINK STRUCTURE
STRUCTURE IS NOT VALID. IS NOT VALID. FUNCTION =
FUNCTION = function, OBJECT function, OBJECT CLASS =
CLASS = object_class, OBJECT object_class, OBJECT NAME =
NAME = object_name, FIELD = object_name, FIELD = field_name
field_name field_type field_value, field_type field_value, SERVICE
SERVICE POINT = sp_name, POINT = sp_name, APPLICATION
APPLICATION NAME = NAME = application.element.
application.element
Explanation
Explanation
This message is generated when the option flag
This message is generated when the option flag specified for the link_to_field is not one of the valid
specified for the link_object is not valid. The option flag choices. The option flag indicates the type of the
specifies the type of value sent. link_to_field.
link_object link_to_field
The RODM link object name. The RODM link field name being used.
function function

field_type field_value
The RODM type being used. The value to be added to the RODM field.
field_value sp_name
The value to be added to the RODM field. The name of the service point to which the
sp_name command was sent.
The name of the service point to which the application.element
command was sent. The name of the network management application
application.element that processes the command string at this service
The name of the network management application point. When multiple applications are supported
that processes the command string at this service the format is application.element, where element is
point. When multiple applications are supported the name of the subapplication running.
the name of the subapplication running. System action
System action
Operator response
Ensure a valid value is being used. If the C toolkit is
System programmer response being used, the valid values are a field name or a
Ensure the option flag sent is one of the valid values hexadecimal value in the range for field nicknames as
defined in the C toolkit or agent documentation. listed in MultiSystem Manager: Topology Agent
Developer's Guide. If the C toolkit is not being used an
FLC021E VALUE FOR 'FROM' FIELD 8-byte hexadecimal number representing a field
link_from_field IN LINK identifier can be used.
STRUCTURE IS NOT VALID.
FUNCTION = function, OBJECT FLC022E VALUE FOR OBJECT CLASS
CLASS = object_class, OBJECT link_class IN LINK STRUCTURE IS
NAME = object_name, FIELD = NOT VALID. FUNCTION = function,
field_name field_type field_value, OBJECT CLASS = object_class,
SERVICE POINT = sp_name, OBJECT NAME = object_name,
APPLICATION NAME = FIELD = field_name field_type
application.element. field_value, SERVICE POINT =
sp_name, APPLICATION NAME =
application.element.
Explanation
This message is generated when the value specified Explanation
for the link_from_field is not valid.
This message is generated when the value specified
Message Variables for the link_class is not a valid class name or a valid
link_from_field hexadecimal number in the range for class nicknames.
The RODM link field name being used. Message Variables
function link_class
The function to be performed on the target object. The RODM link class.
object_class function
The RODM object class of the target object. The function to be performed on the target object.
object_name object_class
The RODM object name of the target object. The RODM object class of the target object.
field_name object_name
The field name being used. The RODM object name of the target object.
field_type field_name
The RODM type being used. The field name being used.

field_type object_name
The RODM type being used. The RODM object name of the target object.
field_value field_name
The value to be added to the RODM field. The field name being used.
sp_name field_type
The name of the service point to which the The RODM type being used.
command was sent. field_value
application.element The value to be added to the RODM field.
The name of the network management application sp_name
that processes the command string at this service The name of the service point to which the
point. When multiple applications are supported command was sent.
the name of the subapplication running. application.element
System action point. When multiple applications are supported
MultiSystem Manager cancels the command. the format is application.element, where element is
Operator response
System action
Operator response
being used, the valid values are a class name or a Notify the system programmer.
hexadecimal value in the range for class nicknames as
listed in MultiSystem Manager: Topology Agent System programmer response
Developer's Guide. If the C toolkit is not being used, an
8-byte hexadecimal number representing a field Ensure a valid value is being used. If the C toolkit is
identifier can be used. being used, only object names are supported. If the C
toolkit is not being used, ensure the value being sent is
FLC023E OBJECT ID link_object_id IN LINK a 16-byte hexadecimal number.
STRUCTURE IS NOT VALID.
FUNCTION = function, OBJECT FLC024E VALUE FOR 'TO' FIELD link_to_field
CLASS = object_class, OBJECT IN LINK STRUCTURE IS NOT
NAME = object_name, FIELD = VALID. FUNCTION = function,
field_name field_type field_value, OBJECT CLASS = object_class,
SERVICE POINT = sp_name, OBJECT NAME = object_name,
APPLICATION NAME = FIELD = field_name field_type
application.element. field_value, SERVICE POINT =
Explanation
This message is generated when the value specified Explanation
for the object is not a 16-byte hexadecimal number
and the option flag sent indicates that an object This message is generated when the value specified
identifier is being specified. for the link_class is not an 8-byte hexadecimal number
and the option flag sent indicates that a field identifier
Message Variables is being specified.
link_object_id Message Variables
The RODM link object.
link_to_field
function The RODM link field name being used.
function
object_class The function to be performed on the target object.
The RODM object class of the target object.
object_class

object_name point. When multiple applications are supported
The RODM object name of the target object. the format is application.element, where element is
field_name the name of the subapplication running.
The field name being used. module_name
field_type The name of the module that was running at the
The RODM type being used. time the error was discovered.
field_value
System action
sp_name MultiSystem Manager cancels the command.
command was sent. Operator response
application.element Notify the system programmer.
that processes the command string at this service System programmer response
the format is application.element, where element is Ensure the value of time_stamp is in the correct format
the name of the subapplication running. and that each value is in the correct range, as follows:
ddd
System action 0–365 days
MultiSystem Manager cancels the command. hh
0–23 hours
Operator response mm
00–59 minutes
ss
00–59 seconds
Minimum
Ensure a valid value is being used. If the C toolkit is :00 (0 seconds)
being used, ensure a valid value was sent in the valid
range for field nicknames, as specified in MultiSystem Default
Manager: Topology Agent Developer's Guide. If the C 1 day (24 hours)
toolkit is not being used, an 8-byte hexadecimal FLC026E TRACE PARAMETER purge_trace
number indicating a field identifier can be used. SPECIFIED FOR PURGE IS NOT
FLC025E TIME STAMP time_stamp VALID. SERVICE POINT =
SPECIFIED FOR PURGE IS NOT sp_name, APPLICATION NAME =
VALID. SERVICE POINT = application.element. COMMAND
sp_name, APPLICATION NAME = ENDED IN MODULE module_name.
ENDED IN MODULE module_name. Explanation
This message is generated when the purge_trace value
Explanation specified is not a Y or an N.
This message is generated when the time_stamp Message Variables
specified is not of the form ddd hh mm ss.
purge_trace
Message Variables Tells whether to trace the code or not.
time_stamp sp_name
The time stamp in the form ddd hh mm ss (days The name of the service point to which the
hours minutes seconds). command was sent.
sp_name application.element
The name of the service point to which the The name of the network management application
command was sent. that processes the command string at this service
application.element point. When multiple applications are supported
The name of the network management application the format is application.element, where element is
that processes the command string at this service the name of the subapplication running.

module_name Operator response

System action
Ensure the value being sent is one of the Reserved
field names found in MultiSystem Manager: Topology
Agent Developer's Guide.
Operator response
FLC028E INVALID FIELD VALUE
Notify the system programmer. STRUCTURE. FUNCTION =
function, OBJECT CLASS =
System programmer response object_class, OBJECT NAME =
object_name, FIELD = field_name
Ensure the value being sent up is a Y or an N.
field_type field_value, SERVICE
FLC027E RESERVED FIELD reserved_field IS POINT = sp_name, APPLICATION
NOT VALID. FUNCTION = function, NAME = application.element.
OBJECT CLASS = object_class, COMMAND ENDED IN MODULE
OBJECT NAME = object_name, module_name.
SERVICE POINT = sp_name,
APPLICATION NAME = Explanation
ENDED IN MODULE module_name. This message is generated when the requested
number of bytes to get for a field value, is greater than
the specified length of the structure.
Explanation
Message Variables
for the reserved_field is not one of the predefined function
values. The function to be performed on the target object.
Message Variables object_class
reserved_field
The reserved field indicating what action to object_name
perform. The RODM object name of the target object.
function field_name
The function to be performed on the target object. The field name being used.
object_class field_type
The RODM object class of the target object. The RODM type being used.
object_name field_value
The RODM object name of the target object. The value to be added to the RODM field.
sp_name sp_name
module_name module_name
The name of the module that was running at the The name of the module that was running at the
time the error was discovered. time the error was discovered.

Operator response module_name

System action
Ensure the lengths of the fields are being calculated
correctly for this object, along with the length of the
overall structure. The requested number of bytes to
get is determined by the previous field length value. Operator response
The length of the structure is the first length given Notify the system programmer.
before any information in the structure.
FLC029E THE REQUESTED NUMBER OF System programmer response
BYTES bytes_to_get WOULD Ensure the lengths of the fields are being calculated
EXCEED THE BUFFER LENGTH correctly for this object, along with the length of the
buffer_length. BYTES RETURNED = overall buffer structure. If you are using the C toolkit
bytes_returned, FUNCTION = verify that flc_finish_func is being called as the last
function, OBJECT CLASS = thing before sending the data to the host.
object_name, SERVICE POINT = FLC030E NUMBER OF EXPECTED BYTES
sp_name, APPLICATION NAME = NOT FOUND. FUNCTION =
application.element. COMMAND function, OBJECT CLASS =
ENDED IN MODULE module_name. object_class, OBJECT NAME =
object_name, LAST VALID FIELD =
Explanation last_valid_field last_valid_type
last_valid_value, SERVICE POINT =
This message is generated when the requested sp_name, APPLICATION NAME =
number of bytes to get is greater than the overall application.element. COMMAND
length of the data available. The requested number of ENDED IN MODULE module_name.
bytes to get is determined by the previous field length
value.
Explanation
Message Variables
This message is generated when the number of
bytes_to_get expected bytes is not found in the data stream. Either
The number of bytes to get for the field. the overall length of the buffer is incorrect or the data
buffer_length did not get completely built.
The length of the buffer which is in the first eight Message Variables
bytes of the data stream.
function
bytes_returned The function to be performed on the target object.
The number of bytes read so far.
object_class
function The RODM object class of the target object.
object_name
object_class The RODM object name of the target object.
last_valid_field
object_name The field name used in the last successful request.
last_valid_type
sp_name The RODM type used in the last successful
The name of the service point to which the request.
command was sent.
last_valid_value
application.element The value used in the last successful request.
that processes the command string at this service sp_name
point. When multiple applications are supported The name of the service point to which the
the format is application.element, where element is command was sent.

application.element Operator response
the format is application.element, where element is System programmer response
the name of the subapplication running. Ensure the overall length of the buffer is being
module_name calculated correctly and added to the data stream as
The name of the module that was running at the an 8-byte hexadecimal number. If you are using the C
time the error was discovered. toolkit, call the flc_finish_func function which formats
the buffer_length and places it in the buffer correctly.
System action FLC032E HEX VALUE EXPECTED FOR
MultiSystem Manager cancels the command. PROTOCOL VERSION NUMBER
version. SERVICE POINT =
Operator response
Notify the system programmer. ENDED IN MODULE module_name.

Ensure the overall length of the buffer is being This message is generated when the value specified
calculated correctly and that the data is being added for the version is not a valid 4-byte hexadecimal
to the buffer correctly. number.
FLC031E HEX VALUE EXPECTED FOR Message Variables
CONTAINER LENGTH version
buffer_length. SERVICE POINT = The version of the agent code running.
application.element. COMMAND sp_name
ENDED IN MODULE module_name. The name of the service point to which the
command was sent.
Explanation application.element
This message is generated when the value specified that processes the command string at this service
for the buffer_length is not a valid 8-byte hexadecimal point. When multiple applications are supported
number. the format is application.element, where element is
Message Variables the name of the subapplication running.
buffer_length module_name
The length of the buffer. Buffer_length is contained The name of the module that was running at the
in the first 8-bytes of the data stream. time the error was discovered.
sp_name
System action
command was sent. MultiSystem Manager cancels the command.
application.element
The name of the network management application Operator response
the name of the subapplication running. System programmer response
module_name Ensure the version is being added to the buffer as a 4-
The name of the module that was running at the byte hexadecimal number. If you are using the C
time the error was discovered. toolkit, call the flc_finish_func function which formats
the version and places it in the buffer correctly.
System action FLC033E HEX VALUE EXPECTED FOR
MultiSystem Manager cancels the command. SEQUENCE NUMBER seq_number.

APPLICATION NAME = Message Variables
field_length
ENDED IN MODULE module_name.
The length of the field name.
object_class
for the seq_number is not a valid 8-byte hexadecimal The RODM object class of the target object.
number.
object_name
Message Variables The RODM object name of the target object.
seq_number last_valid_field
The sequence number indicating which run The field name used in the last successful request.
command response contains the topology last_valid_type
updates. The RODM type used in the last successful
sp_name request.
The name of the service point to which the last_valid_value
command was sent. The value used in the last successful request.
application.element sp_name
The name of the network management application The name of the service point to which the
that processes the command string at this service command was sent.
the format is application.element, where element is application.element
the name of the subapplication running. The name of the network management application
module_name point. When multiple applications are supported
The name of the module that was running at the the format is application.element, where element is
time the error was discovered. the name of the subapplication running.



Ensure the seq_number is being added to the buffer as Ensure the field_length is being calculated correctly
an 8-byte hexadecimal number. If you are using the C and added to the buffer as a 4-byte hexadecimal
toolkit, call the flc_finish_func function which formats number.
the seq_number and places it in the buffer correctly.
FLC035E HEX VALUE EXPECTED FOR FIELD
FLC034E HEX VALUE EXPECTED FOR FIELD TYPE field_type. FUNCTION =
NAME LENGTH field_length function, OBJECT CLASS =
FUNCTION = function, OBJECT object_class, OBJECT NAME =
CLASS = object_class, OBJECT object_name, LAST VALID FIELD =
NAME = object_name, LAST VALID last_valid_field last_valid_type
FIELD = last_valid_field last_valid_value, SERVICE POINT =
last_valid_type last_valid_value, sp_name, APPLICATION NAME =
SERVICE POINT = sp_name, application.element.
APPLICATION NAME =
Explanation
Explanation This message is generated when the value for the
field_type is not a 2-byte hexadecimal number.
This message is generated when the value for the
field_length is not a 4-byte hexadecimal number. Message Variables

field_type value_length
The RODM type being used. The length of the value to be added to RODM.
function function
last_valid_field last_valid_field
The field name used in the last successful request. The field name used in the last successful request.
last_valid_type last_valid_type
The RODM type used in the last successful The RODM type used in the last successful
request. request.
last_valid_value last_valid_value
The value used in the last successful request. The value used in the last successful request.
sp_name sp_name



Ensure the field_type is being added to the buffer as a Ensure the value_length is being calculated correctly
2-byte hexadecimal number. If the C toolkit is being and added to the buffer as a 4-byte hexadecimal
used the field_type will be converted to hexadecimal. number.
FLC036E HEX VALUE EXPECTED FOR FIELD FLC037W CAN NOT AGGREGATE TO THE
VALUE LENGTH value_length NETWORK VIEW CLASS OBJECT
FUNCTION = function, OBJECT link_object. FUNCTION = function,
CLASS = object_class, OBJECT OBJECT CLASS = object_class,
NAME = object_name, LAST VALID OBJECT NAME = object_name,
FIELD = last_valid_field FIELD = field_name field_type
last_valid_type last_valid_value, field_value, SERVICE POINT =
SERVICE POINT = sp_name, sp_name, APPLICATION NAME =
APPLICATION NAME = application.element.
Explanation
Explanation
This message is generated when an aggregate link is
This message is generated when the value for the attempted to the Network_View_Class object. There
value_length is not a 4-byte hexadecimal number. are no aggregation links defined to the
Network_View_Class, so in this case, only the parent
Message Variables
connection is made.

Message Variables field_name
link_object
The RODM object to link the target object to. field_type
function
The function to be performed on the target object. field_value
object_class
The RODM object class of the target object. sp_name
object_name
command was sent.
application.element
field_name
field_type point. When multiple applications are supported
The RODM type being used. the format is application.element, where element is
field_value the name of the subapplication running.
The value to be added to the RODM field. module_name
sp_name The name of the module that was running at the
The name of the service point to which the time the error was discovered.
command was sent.
application.element System action
The name of the network management application MultiSystem Manager cancels the command.
Operator response
the name of the subapplication running. Notify the system programmer.

MultiSystem Manager agent remains operational and Ensure a target object is added to the buffer before
GETTOPO commands are still processed. any associated fields are specified. If you are using the
C toolkit call the target_object function before adding
Operator response fields.
Notify the system programmer. FLC039E NO OBJECTS SPECIFIED.

FUNCTION = function, SERVICE
System programmer response POINT = sp_name, APPLICATION
NAME = application.element.
Find where the aggregate link is being used with the COMMAND ENDED IN MODULE
Network_View_Class and change it to link to a module_name.
different object, or use a different link.
FLC038E FIELD field_name field_type Explanation
field_value SPECIFIED BEFORE This message is generated when a function that
ANY OBJECT WAS SPECIFIED. requires objects is specified but no target object is
SERVICE POINT = sp_name, specified.
APPLICATION NAME =
application.element. COMMAND Message Variables
ENDED IN MODULE module_name. function
Explanation sp_name
This message is generated when field_name, The name of the service point to which the
field_type and field_value are specified before a target command was sent.
object is specified. application.element
Message Variables The name of the network management application

the format is application.element, where element is FLC042I THE LINK BETWEEN object_name1
the name of the subapplication running. FIELD field_name1 AND
module_name object_name2 FIELD field_name2
The name of the module that was running at the WAS REMOVED.
Explanation
System action A link between the specified fields of two objects was
MultiSystem Manager cancels the command. removed. The link's removal is subject to the Purge
attribute and display-status criteria. It is possible that
some links did not meet the criteria. In that case, you
Operator response
also receive message FLC041I for this object.
When a REMVOBJS command is issued with
TRACE=YES, you can receive multiple FLC040I,
System programmer response FLC041I, and FLC042I messages tracing the removal
Ensure a target object is specified after the function is of the object and its children. See the IBM Z NetView
specified. User's Guide: NetView Management Console for
additional information concerning the removal of
FLC040I OBJECT object_name AND ALL OF objects from RODM.
ITS LINKS WERE REMOVED.
Message Variables
Explanation object_name1
The RODM Object Name of the first object
The listed object and all of its links have been removed
from RODM. The object's removal is subject to the field_name1
Purge attribute and display-status criteria. The RODM Field Name for the link of the first
object
When a REMVOBJS command is issued with
object_name2
TRACE=YES, you might receive multiple FLC040I,
The RODM Object Name of the second object
FLC041I, and FLC042I messages tracing the removal
of the object and its children. field_name2
The RODM Field Name for the link of the second
Message Variables object
object_name
FLC043I MULTISYSTEM MANAGER
The RODM object name
PROCESSING HAS BEEN
FLC041I OBJECT object_name AND ITS RESUMED.
LINKS WERE NOT REMOVED.
Explanation
Explanation MultiSystem Manager processing was suspended. The
The listed object and its links were not removed from RESTOPO command has been issued to resume
RODM. The object's removal is subject to the Purge processing.
attribute and display-status criteria. It is possible that
some of the links met the criteria. In that case, you System action
also receive message FLC042I for this object.
MultiSystem Manager processes GETTOPO commands
When a REMVOBJS command is issued with when they are issued.
TRACE=YES, you might receive multiple FLC040I,
FLC041I, and FLC042I messages tracing the removal FLC044I MULTISYSTEM MANAGER
of the object and its children. See the IBM Z NetView PROCESSING HAS BEEN
User's Guide: NetView Management Console for SUSPENDED.
additional information concerning the removal of
objects from RODM. Explanation
Message Variables The SUSPTOPO command has been issued to suspend
MultiSystem Manager processing.
object_name
The RODM object name

System action FLC046E MULTISYSTEM MANAGER
CANNOT BE RESUMED.
MultiSystem Manager does not process GETTOPO
commands.
FLC045E MULTISYSTEM MANAGER HAS WITH RETURN CODE return_code.
NOT BEEN INITIALIZED OR
PROCESSING HAS BEEN Explanation
SUSPENDED. command_name
COMMAND ENDED IN MODULE The RESTOPO command was issued to resume
module_name WITH RETURN MultiSystem Manager processing, but MultiSystem
CODE return_code. Manager is not in SUSPENDED state.
Message Variables
Explanation
command_name
A topology request was issued but MultiSystem The command that was issued
Manager is currently unable to process the request. module_name
MultiSystem Manager has not been initialized, or The name of the module that was running at the
processing has been suspended. time the error was discovered
Message Variables return_code
command_name The return code from the module.
System action
module_name
The name of the module that was running at the MultiSystem Manager does not process the RESTOPO
time the error was discovered command.
return_code
The return code from the module Operator response
1. Issue the DISPTOPO command to determine the
System action status of MultiSystem Manager. If MultiSystem
MultiSystem Manager cancels the command. Manager is already ENABLED, no further action is
required.
Operator response 2. If the status of the MultiSystem Manager is
NEVER_INITIALIZED or INITIALIZATION_FAILED,
1. Issue the DISPTOPO command to determine the issue the INITTOPO command to initialize
status of MultiSystem Manager. MultiSystem Manager.
• If the status of the MultiSystem Manager is 3. If the initialization fails, contact your system
SUSPENDED: programmer.
a. Issue the RESTOPO command to resume
processing. System programmer response
b. Enter the topology request again. 1. Correct any coding errors in your MultiSystem
• If the MultiSystem Manager status is Manager initialization file.
NEVER_INITIALIZED or 2. Reissue the INITTOPO command.
INITIALIZATION_FAILED:
FLC047E MULTISYSTEM MANAGER
a. Issue the INITTOPO command to initialize the CANNOT BE SUSPENDED.
MultiSystem Manager. command_name COMMAND
b. Reenter the topology request. ENDED IN MODULE module_name
2. If this does not resolve the problem, contact your
system programmer.
Explanation
System programmer response The SUSPTOPO command was issued to suspend
MultiSystem Manager processing but the MultiSystem
If the INITTOPO command failed, look for coding
Manager is not in ENABLED state.
errors in your MultiSystem Manager initialization file.
Message Variables

command_name BEEN UPDATED FOR RESOURCE
The command that was issued resource_name.
module_name
The name of the module that was running at the Explanation
time the error was discovered The command sent to the specified service point has
return_code been processed successfully.
The return code from module
Message Variables
System action command_name

The command that was issued.
MultiSystem Manager does not process the SUSPTOPO
command. sp_name
command was sent.
Operator response
application_name
1. Issue the DISPTOPO command to determine the The name of the network management application
status of MultiSystem Manager. If MultiSystem that processes the command string at this service
Manager is already SUSPENDED, no further action point. This is also referred to as application ID.
is required.
keyword
2. If the status of MultiSystem Manager is The keyword or keywords specified on the
NEVER_INITIALIZED, or INITIALIZATION_FAILED, GETTOPO command. This defines the type of
topology requests are not currently being GETTOPO command that was issued. For example
processed. If the desired status is SUSPENDED, IPRES.
a. Issue INITTOPO to initialize MultiSystem resource_name
Manager. The name of the resource that was updated. This is
b. Issue the SUSPTOPO command to suspend the name of the resource as it was specified on the
processing. original command.
FLC048I GETTOPO COMMANDS FROM FLC050E AUTOTASK autotask CANNOT BE

MULTISYSTEM MANAGER ACTIVATED. command_name
INITIALIZATION FILE file_name COMMAND ENDED IN MODULE
ARE NOW BEING PROCESSED. module_name WITH RETURN
CODE return_code.
Explanation
Explanation
The listed MultiSystem Manager initialization file has
been read successfully. The GETTOPO commands A GETTOPO command was issued to run under an
coded in the initialization file are being processed. autotask that was not active. Attempts to activate the
autotask and reissue the command under the default
Message Variables autotask have failed.
file_name Message Variables
The name of the MultiSystem Manager
initialization file that is specified on the INITTOPO autotask
command The name of the autotask
command_name
System action The command that was issued.
MultiSystem Manager processes GETTOPO commands module_name

when they are issued. The name of the module that was running at the
time the error was discovered
FLC049I command_name COMMAND FOR return_code
SERVICE POINT sp_name WITH The return code from the module
APPLICATION NAME
application_name HAS
COMPLETED SUCCESSFULLY. System action
keyword WAS SPECIFIED ON THE • First, MultiSystem Manager attempts to run the
command_name COMMAND. GETTOPO command under the specified autotask.
TOPOLOGY AND STATUS HAVE

• If the autotask is inactive, MultiSystem Manager Operator response
attempts to activate the autotask and reissue the
If AUTOTASK was specified on the GETTOPO
GETTOPO command.
command, check the spelling of the autotask name.
• If this fails and the specified autotask is not the
default autotask, MultiSystem Manager tries to run • If the autotask name was misspelled, there is no
the GETTOPO command under the default autotask. need to reissue the command since the command
was sent to the default autotask.
• If both attempts fail, MultiSystem Manager cancels
the GETTOPO command. • If the autotask name was spelled correctly, notify
the system programmer.
Operator response
If AUTOTASK was specified on the GETTOPO
command, check the spelling of the autotask name. Check the operator definitions, for example, DSIOPF,
Correct any errors you find and reissue the command. to ensure that the specified autotask is defined to
If problem persists, notify the system programmer. NetView program. Activate the specified autotask.
FLC052E command_name COMMAND
System programmer response ENDED DUE TO REXX NOVALUE
ERROR FOR VARIABLE variable IN
Check the operator definitions, for example, DSIOPF,
LINE line_number OF MODULE
to ensure that this autotask and the default autotask
module_name. RETURN CODE =
specified in the MultiSystem Manager initialization file
return_code.
have been defined to NetView program. Activate the
autotasks.
Explanation
FLC051I AUTOTASK autotask IS NOT
ACTIVE. THE command_name A REXX NOVALUE error occurred for the listed variable
COMMAND HAS BEEN SENT TO at the specified line of the specified module.
THE DEFAULT AUTOTASK Message Variables
default_autotask.
command_name
Explanation
variable
A GETTOPO command was issued to run under an The name of the variable.
inactive autotask. The GETTOPO command was run
line_number
under the default autotask.
The number of the line in which the error occurred
Message Variables module_name
autotask The name of the module in which the error
The name of the autotask occurred
command_name return_code
The name of the command The return code for the module
default_autotask
The name of the default autotask specified by System action
DEF_AUTOTASK in the MultiSystem Manager The command is cancelled.
initialization file
Operator response
System action
After finding the specified autotask inactive,
MultiSystem Manager attempts to activate the
autotask and reissue the GETTOPO command. This
message indicates that the second attempt failed and Contact IBM Software Support and provide the
MultiSystem Manager ran the GETTOPO command information from this message.
under the default autotask.
ENDED DUE TO REXX SYNTAX
ERROR IN LINE line_number OF

MODULE module_name. RETURN System action
CODE = return_code.
The command is cancelled.
Explanation
Operator response
A REXX syntax error was encountered at the specified
Reissue the command with the keyword specified only
line of the specified module.
once.
Message Variables
FLC055E KEYWORD keyword IS NOT VALID.
command_name command_name COMMAND
The name of the command ENDED IN MODULE module_name
line_number WITH RETURN CODE return_code.
The number of the line in which the error occurred
module_name Explanation
The name of the module in which the error The specified command contained a keyword that is
occurred not valid.
The REXX return code
keyword
The keyword that is not valid
System action
command_name
The command is cancelled. The command that was issued
module_name
Operator response
Notify the system programmer. time the error was discovered
return_code
System programmer response The return code from the module
Contact IBM Software Support and provide the
information from this message. System action
FLC054E KEYWORD keyword SPECIFIED The command is cancelled.

MORE THAN ONCE.
command_name COMMAND Operator response
Reissue the command with valid keywords specified.
See the NetView online help for the command syntax.
Explanation FLC056E KEYWORD keyword_a IS NOT

VALID WHEN SPECIFIED WITH
A command was issued that contained a duplicate KEYWORD keyword_b.
keyword. command_name COMMAND
Message Variables ENDED IN MODULE module_name
keyword
The name of the keyword which was specified
more than once Explanation
command_name The specified command contained two keywords that

The command that was issued cannot be specified together.
module_name Message Variables
keyword_a
A keyword that cannot be used with keyword_b
return_code
keyword_b
The return code from the module
A keyword that cannot be used with keyword_a
command_name

The listed keyword cannot be used as the first
keyword on the listed command.
return_code
The return code from the module You will also receive this message if you code
something other than xxxRES or xxxONLY as the first
keyword on a GETTOPO statement in a MultiSystem
System action Manager initialization file. GETTOPO xxxRES and
The command is cancelled. GETTOPO xxxONLY are the only variations of the
GETTOPO command that can be coded in a
Operator response MultiSystem Manager initialization file.
Reissue the command with valid keyword Message Variables

combinations specified. See the NetView online help keyword
for the command syntax. The keyword used as the first keyword in the
command
FLC057E VALUE value IS NOT VALID FOR
KEYWORD keyword. command_name
command_name COMMAND The command that was issued
ENDED IN MODULE module_name module_name
WITH RETURN CODE return_code. The name of the module that was running at the
The listed value is not valid for the listed keyword. The return code from the module
Message Variables
System action
value
The value that is not valid for listed keyword
keyword
Operator response
A keyword for which the value was specified
command_name Reissue the command with a valid first keyword. See
The command that was issued the NetView online help for the command syntax.
module_name FLC059I MULTISYSTEM MANAGER

The name of the module that was running at the INITIALIZATION FILE file_name
time the error was discovered HAS BEEN READ SUCCESSFULLY.
return_code THE MULTISYSTEM MANAGER IS
The return code from the module NOW ENABLED.
Explanation
System action
The listed MultiSystem Manager initialization file was
The command is cancelled.
run successfully. MultiSystem Manager is now able to
process topology requests.
Operator response
Message Variables
Reissue the command with a valid value for the listed
keyword. See the NetView online help for the file_name
command syntax. The name of the MultiSystem Manager
initialization file that is specified on the INITTOPO
FLC058E KEYWORD keyword IS NOT VALID command
AS FIRST KEYWORD ON
command_name.COMMAND. FLC060E REQUIRED KEYWORD keyword
command_name COMMAND MISSING. command_name
ENDED IN MODULE module_name COMMAND ENDED IN MODULE
WITH RETURN CODE return_code. module_name WITH RETURN
CODE return_code.

Explanation INITIALIZATION FILE file_name.
INITIALIZATION STATEMENT
A required keyword is missing from the listed
statement IS NOT VALID. RETURN
command.
CODE = return_code.
Message Variables
keyword Explanation
The missing keyword. It is possible for this insert MultiSystem Manager attempted to initialize the
to be blank, meaning that no keywords were network topology but cannot do so because of an
entered for the command. incorrect initialization file statement.
command_name Message Variables
file_name
module_name
initialization file specified on the INITTOPO
command
return_code
statement
The return code from the module.
The statement that is not valid
System action return_code

System action
Operator response
Reissue the command with all of the required command.
keywords. See the NetView online help for the
• MultiSystem Manager does not perform Network
command syntax.
topology initialization.
FLC061E command_name COMMAND • MultiSystem Manager status changes to
ENDED IN MODULE module_name INITIALIZATION_FAILED.
Operator response
Explanation
The listed command has failed.
command_name 1. Correct the specified initialization statement in the
The command that was issued initialization file. See IBM Z NetView Installation:
module_name Configuring Graphical Components for the
The name of the module that was running at the initialization statement syntax.
time the error was discovered 2. Reissue the INITTOPO command to restart the
return_code initialization process.
The return code from the module FLC063E UNABLE TO INITIALIZE
MULTISYSTEM MANAGER WITH
System action INITIALIZATION FILE file_name.
INITIALIZATION STATEMENT
The system cancels the command.
statement SPECIFIED MORE THAN
ONCE. RETURN CODE =
Operator response return_code.
Explanation
System programmer response The listed initialization statement is specified more
Contact IBM Software Support. than once in the initialization file. MultiSystem
Manager cannot initialize topology and status.
MULTISYSTEM MANAGER WITH Message Variables

file_name • MultiSystem Manager does not perform Network
The name of the MultiSystem Manager topology initialization.
initialization file that is specified on the INITTOPO • MultiSystem Manager status changes to
command INITIALIZATION_FAILED.
statement
The statement that is specified more than once Operator response
return_code Notify the system programmer.

System action
1. Add the missing statement to your initialization file.
• MultiSystem Manager cancels the INITTOPO If the file in error is the initialization file that is
command. specified on the INITTOPO command, see IBM Z
• MultiSystem Manager does not perform Network NetView Installation: Configuring Graphical
topology initialization. Components for the initialization statement syntax.
• MultiSystem Manager status changes to If the file in error is the exception view file that is
INITIALIZATION_FAILED. specified on the EXCEPTION_VIEW_FILE
statement, see the prologue of sample FLCSEXV for
direction.
Operator response
2. Reissue the INITTOPO command to restart the
Notify the system programmer. initialization process.
System programmer response FLC065I SERVICE POINT sp_name NOT

DEFINED TO VTAM. OBJECTS
1. Specify the initialization statement only once in the REPRESENTING THIS SERVICE
listed initialization file. POINT WILL BE STORED IN RODM.
initialization process. Explanation
FLC064E UNABLE TO INITIALIZE You requested to retrieve topology data and status
MULTISYSTEM MANAGER WITH from a service point that is not defined to VTAM. The
INITIALIZATION FILE file_name. objects representing this service point are stored in
REQUIRED STATEMENT MISSING. RODM and GETTOPO processing continues.
RETURN CODE = return_code.
Message Variables
Explanation sp_name
A required initialization statement is missing from the command was sent
MultiSystem Manager initialization file. MultiSystem
Manager cannot initialize topology and status.
System action
Message Variables
GETTOPO processing continues.
file_name
The name of the MultiSystem Manager Operator response
initialization file specified on the INITTOPO
command or the name of the exception view file If you specified the service point name correctly, but it
specified on the EXCEPTION_VIEW_FILE was not known to VTAM at the time you issued the
statement in the MultiSystem Manager GETTOPO command, the objects representing the
initialization file. service point are stored in RODM and no action is
required.
return_code
The return code from the module. If you did not specify the service point name correctly,
the objects representing the service point are still
System action stored in RODM. Delete these extraneous objects from
RODM. Contact your system programmer if you do not
• MultiSystem Manager cancels the INITTOPO have authority to delete the objects from RODM.
command. Reissue the GETTOPO command with the correct
service point name.

System programmer response INITIALIZATION FILE file_name.
VALUE value IS NOT VALID FOR
If the service point name was specified correctly,
KEYWORD keyword. RETURN
define the service point to VTAM. Otherwise, remove
CODE = return_code.
the extraneous service point objects from RODM.
FLC066E UNABLE TO INITIALIZE Explanation
INITIALIZATION FILE file_name. The listed value is not valid for the listed keyword in
INITIALIZATION FILE file_name the initialization file.
DOES NOT EXIST. RETURN CODE = Message Variables
return_code.
file_name
Explanation initialization file specified on the INITTOPO
MultiSystem Manager cannot initialize topology and command
status because it cannot find the specified initialization value
file. The value that is not valid for the listed keyword
Message Variables keyword
The keyword with the value that is not valid
file_name
The name of the MultiSystem Manager return_code
initialization file specified on the INITTOPO The return code from the module
command or the name of the exception view file
specified on the EXCEPTION_VIEW_FILE System action
statement in the MultiSystem Manager
initialization file. • MultiSystem Manager cancels the INITTOPO
command.
return_code
The return code from the module. • MultiSystem Manager does not perform Network
topology initialization.
System action • MultiSystem Manager status changes to
INITIALIZATION_FAILED.
command.
Operator response
• MultiSystem Manager does not perform Network
topology initialization. Notify the system programmer.
• MultiSystem Manager status changes to

INITIALIZATION_FAILED.
1. Correct the value for the keyword in the listed
Operator response initialization file. See IBM Z NetView Installation:
Configuring Graphical Components for the
Was a valid initialization file specified on the initialization statement syntax.
INITTOPO command?
• No, reissue the command with a valid initialization initialization process.
file specified.
• Yes, notify the system programmer.
INITIALIZATION FILE file_name.
System programmer response RETURN CODE = return_code.
1. Find or create the specified MultiSystem Manager
initialization file. See IBM Z NetView Installation: Explanation
Configuring Graphical Components for the
An attempt to initialize topology and status failed.
initialization statement syntax.
2. Reissue the INITTOPO command to restart the Message Variables
initialization process.

file_name • If this error was encountered during MultiSystem
The name of the MultiSystem Manager Manager initialization and message FLC059I was not
initialization file that is specified on the INITTOPO received, the problem occurred while the system
command was creating the topology manager class objects in
return_code RODM. Ensure that all keyword values of the
The return code from the module GETTOPO statements in the MultiSystem Manager
initialization file are correct.
System action • If this error was encountered during MultiSystem
Manager initialization and message FLC059I was
• MultiSystem Manager cancels the INITTOPO received, ensure that all keyword values of the
command. GETTOPO statements in the MultiSystem Manager
• MultiSystem Manager does not perform Network initialization file are correct.
topology initialization. • If any keyword values are incorrect, reissue the
• MultiSystem Manager status changes to command with the correct values, or correct the
INITIALIZATION_FAILED. initialization file, as appropriate.
• If all keyword values are correct, notify the system
System programmer response • Ensure that the data model is loaded and that RODM
is correctly processing function requests from
applications.
FLC070E RODM PROCESSING ERROR. • Check the NetView log for message FLC076E.
• Contact IBM Software Support if you cannot resolve
the problem.
FLC071E UNABLE TO PROCESS option
Explanation OPTION ON command_name
COMMAND. MULTISYSTEM
MultiSystem Manager encountered a RODM
MANAGER FEATURE NOT
processing error when running the listed command.
INSTALLED. command_name
Message Variables COMMAND ENDED IN MODULE
command_name
CODE return_code.
The command or initialization file statement that
was issued
Explanation
module_name
The name of the module that was running at the The MultiSystem Manager feature required to process
time the error was discovered the listed option is not installed.
option
The option specified on the listed command
System action
command_name
The system cancels the command and does not The command that was issued
process the failed RODM request. If this request is one module_name
in a group of requests, the remaining requests in the The name of the module that was running at the
group are not to be processed either. Message time the error was discovered.
FLC076E is logged to the NetView log whenever
message FLC070E is generated. return_code
Operator response
System action
• If this message reflects a command error, ensure
that all command keyword values are correct. MultiSystem Manager cancels the command.

Operator response module_name WITH RETURN
CODE return_code.
Explanation
The listed command cannot run under the specified
Install the required MultiSystem Manager feature. See
type of task.
the IBM Z NetView Installation: Getting Started for
installation information. Message Variables
FLC072E REQUIRED FIELD field IS NULL IN command_name
RODM. OBJECT IDENTIFIER = The command that was issued
object_identifier OBJECT CLASS = task_type
object_class OBJECT NAME = The type of task (for example, OST, PPT)
object_name command_name
module_name
CODE return_code.
return_code
Explanation The return code from the module
The listed command queried the value of a required System action

RODM field but the value of the required field is null.
Message Variables
field Operator response
The RODM field that is required
Reissue the command under the appropriate type of
object_identifier task.
RODM object identifier
object_class FLC074E RODM NAME AND RODM
RODM object class APPLICATION ID HAVE NOT BEEN
INITIALIZED. command_name
object_name COMMAND ENDED IN MODULE
RODM object name module_name WITH RETURN
command_name CODE return_code.
The name of the module that was running at the MultiSystem Manager cannot process this command
time the error was discovered because the RODM name and RODM application ID
return_code global variables are not initialized.
Message Variables
System action command_name

module_name
Operator response time the error was discovered
Notify the system programmer. return_code
Contact IBM Software Support. System action
CANNOT BE EXECUTED UNDER
TASK task_type. command_name Operator response
COMMAND ENDED IN MODULE 1. Issue the DISPTOPO command to check the values
for RODM name and application ID.

2. Then, System programmer response
• If the vales are incorrect or null, initialize See message number FLC070E.
topology and status by issuing the INITTOPO
FLC077E FAILURE WHILE PROCESSING
command.
RUNCMD FOR SERVICE POINT
• If the values are correct, notify the system sp_name - runcmd.
programmer. command_name COMMAND
System programmer response WITH RETURN CODE return_code.
Explanation
FLC075E LENGTH OF RUNCMD EXCEEDS
MAXIMUM OF 240 CHARACTERS. The RUNCMD built to process command_name failed
command_name COMMAND during processing.
ENDED IN MODULE module_name Message Variables
sp_name
Explanation command was sent
When MultiSystem Manager built the RUNCMD for the runcmd
listed command, the RUNCMD exceeded the maximum The RUNCMD command that failed
length of 240 characters.
command_name
Message Variables The command that was issued
command_name module_name
The command that was issued The name of the module that was running at the
module_name
The name of the module that was running at the return_code
time the error was discovered The return code from the module
return_code
The return code from the module System action
The system cancels the command.
System action
• If this error was encountered while issuing a
Operator response GETTOPO command, ensure that all keyword values
are correct, and reissue the command.
Reenter the command, ensuring that it is less than 240
characters in length. • If this error was encountered during MultiSystem
Manager initialization, ensure that all keyword values
FLC076E RODM OBJECT INFORMATION. on the GETTOPO statements in the MultiSystem
Manager initialization file are correct, and reissue the
Explanation INITTOPO command.
A RODM processing error was encountered. • If all keyword values are correct, notify the system
programmer.
System action
• The system cancels the command associated with
the RODM processing error. Examine the associated RUNCMD failure messages
and follow the recommended actions to resolve the
• The system logs the RODM objects being processed
problem.
at the time of the error to the NetView log along with
other pertinent information. FLC078I command_name COMMAND HAS
COMPLETED SUCCESSFULLY.
Operator response

The listed MultiSystem Manager command was Notify the system programmer.
processed successfully by MultiSystem Manager.
command_name Ensure the buffer is being built correctly and data is

The command that was issued being sent.
FLC079I command_name COMMAND HAS FLC081E VALUE FOR CLASS NAME IS NOT
COMPLETED SUCCESSFULLY. VALID. FUNCTION = function,
number OBJECTS WERE FIELD = field_name field_type
REMOVED. field_value, SERVICE POINT =
Explanation
The listed MultiSystem Manager command was
processed successfully by MultiSystem Manager. The Explanation
specified number of objects were removed. See the
IBM Z NetView User's Guide: NetView Management This message is generated when the value specified
Console for additional information concerning the for the class name is not a valid hexadecimal number,
removal of objects from RODM. or is not in the range for valid class nicknames.
command_name function
The command that was issued The function to be performed on the target object.
number field_name
The number of objects removed The field name being used.
field_type
FLC080E NO TOPOLOGY DATA PRESENT.
APPLICATION NAME = field_value
application.element. COMMAND The value to be added to the RODM field.
ENDED IN MODULE module_name. sp_name
Explanation command was sent.
This message is generated when there is no data in the application.element
buffer. The name of the network management application
Message Variables point. When multiple applications are supported
sp_name the format is application.element, where element is
The name of the service point to which the the name of the subapplication running.
command was sent. module_name
application.element The name of the module that was running at the
The name of the network management application time the error was discovered
point. When multiple applications are supported System action
module_name Operator response
time the error was discovered. Notify the system programmer.

MultiSystem Manager cancels the command. Ensure a valid hexadecimal value is being used. If the
C toolkit is being used, a hexadecimal number in the
range for class nicknames must be specified. If the C

toolkit is not being used, a hexadecimal number FLC083E STATUS PARAMETER status
representing a class identifier must be specified. SPECIFIED FOR PURGE IS NOT
VALID. SERVICE POINT =
FLC082E OBJECT ID IS NOT VALID.
FUNCTION = function, OBJECT
CLASS = object_class, FIELD =
field_name field_type field_value,
APPLICATION NAME = Explanation
application.element. COMMAND This message is generated when the value specified
ENDED IN MODULE module_name. for status is not valid.
Message Variables
Explanation
status
The status of the objects to remove.
for the object is not a 16-byte hexadecimal number
and the option flag sent indicates that an object sp_name
identifier is specified. The name of the service point to which the
command was sent.
Message Variables
application.element
function The name of the network management application
The function to be performed on the target object that processes the command string at this service
object_class point. When multiple applications are supported
The RODM object class of the target object the format is application.element, where element is
field_name
The field name that is being used module_name
field_type
The RODM type that is being used
field_value System action
The value to be added to the RODM field
sp_name
command was sent Operator response
application.element Notify the system programmer.
the format is application.element, where element is Ensure a valid status value is being used. The valid
the name of the subapplication running. values are listed in MultiSystem Manager: Topology
Agent Developer's Guide.
module_name
The name of the module that was running at the FLC084E VALUE FOR NAME nickname IN
time the error was discovered. FIELD VALUE STRUCTURE IS NOT
VALID. FUNCTION = function,
System action OBJECT CLASS = object_class,
OBJECT NAME = object_name,
MultiSystem Manager cancels the command. FIELD = field_name field_type
field_value, SERVICE POINT =
Operator response sp_name, APPLICATION NAME =
Explanation
for the nickname is not a valid hexadecimal number.
being used, only object names are supported. If the C
toolkit is not being used, ensure the value being sent is Message Variables
a 16-byte hexadecimal number.

nickname Explanation
The hexadecimal number representing a field
name or Field Identifier.
for the nicktype is not a valid 2-byte hexadecimal
function number.
Message Variables
object_class
The RODM object class of the target object. nicktype
The 2-byte hexadecimal number representing
object_name
RODM type.
function
field_name
object_class
field_type
object_name
field_value
field_name
sp_name
command was sent. field_type
application.element
The name of the network management application field_value
that processes the command string at this service The value to be added to the RODM field.
point. When multiple applications are supported sp_name
the format is application.element, where element is The name of the service point to which the
the name of the subapplication running. command was sent.
application.element
System action The name of the network management application
MultiSystem Manager cancels the command. that processes the command string at this service
Operator response
System action
being used, ensure a 4-byte hexadecimal value in the Operator response
valid range for field nicknames was sent. If the C
toolkit is not being used, and the value is not a 4-byte Notify the system programmer.
hexadecimal identifier, then it must be an 8-byte field
identifier. System programmer response
FLC085E HEX VALUE EXPECTED FOR TYPE Ensure a valid RODM type is being used and sent as a
nicktype IN FIELD VALUE 2-byte hexadecimal number.
STRUCTURE. FUNCTION =
FLC086E 'TO' FIELD LENGTH to_field_length
function, OBJECT CLASS =
IN LINK STRUCTURE IS NOT
VALID. FUNCTION = function,
object_name, FIELD =field_name
OBJECT CLASS = object_class,
field_type field_value, SERVICE
OBJECT NAME = object_name,
POINT = sp_name, APPLICATION
FIELD = field_name field_type
field_value, SERVICE POINT =

This message is generated when the length specified This message is generated when the length specified
for the to_field_length is not a valid hexadecimal for the from_field_length is not a valid hexadecimal
number. number.
to_field_length from_field_length
The length of the field. The length of the Field.
function function
field_type field_type
The RODM type being used. The RODM type being used.
field_value field_value
The value to be added to the RODM field. The value to be added to the RODM field.
sp_name sp_name



Ensure a valid length is being sent as a hexadecimal Ensure a valid length is being sent as a hexadecimal
number. number.
FLC087E 'FROM' FIELD LENGTH FLC088E CLASS LENGTH class_length IN
from_field_length IN LINK LINK STRUCTURE IS NOT VALID.
STRUCTURE IS NOT VALID. FUNCTION = function, OBJECT
FUNCTION = function, OBJECT CLASS = object_class, OBJECT
CLASS = object_class, OBJECT NAME = object_name, FIELD =
NAME = object_name, FIELD = field_name field_type field_value,
field_name field_type field_value, SERVICE POINT = sp_name,
SERVICE POINT = sp_name, APPLICATION NAME =
APPLICATION NAME = application.element.

This message is generated when the length specified This message is generated when the length specified
for the class_length is not a valid hexadecimal number. for the object_length is not a valid hexadecimal
number.
Message Variables
Message Variables
class_length
The length of the RODM class. object_length
function The length of the RODM object name.
The function to be performed on the target object. function
The RODM object class of the target object. object_class
object_name The RODM object class of the target object.
The RODM object name of the target object. object_name
field_name The RODM object name of the target object.
The field name being used. field_name
The RODM type being used. field_type
The value to be added to the RODM field. field_value
sp_name The value to be added to the RODM field.
The name of the service point to which the sp_name
command was sent. The name of the service point to which the
application.element command was sent.
The name of the network management application application.element
that processes the command string at this service The name of the network management application
point. When multiple applications are supported that processes the command string at this service
the format is application.element, where element is point. When multiple applications are supported
the name of the subapplication running. the format is application.element, where element is
System action
System action
Operator response
Operator response
Ensure a valid length is being sent as a hexadecimal
number. Ensure a valid length is being sent as a hexadecimal
number.
FLC089E OBJECT LENGTH object_length IN
LINK STRUCTURE IS NOT VALID. FLC090E VALUE FOR DISPLAY RESOURCE
FUNCTION = function, OBJECT TYPE IS NOT VALID. FUNCTION =
CLASS = object_class, OBJECT function, OBJECT CLASS =
NAME = object_name, FIELD = object_class, OBJECT NAME =
field_name field_type field_value, object_name, FIELD = field_name
SERVICE POINT = sp_name, field_type field_value, SERVICE
APPLICATION NAME = POINT = sp_name, APPLICATION
application.element. NAME = application.element.
module_name.

Explanation COMMAND ENDED IN MODULE
module_name.
for the Display Resource Type is not a valid
hexadecimal number representing a nickname for a Explanation
DRT, and the option flag sent indicates that a This message is generated when the value specified in
nickname is being specified. the structure is not the same data type as the RODM
Message Variables predefined data type of the field to update.
function Message Variables

The function to be performed on the target object. function
The RODM object class of the target object. object_class
object_name The RODM object class of the target object.
The RODM object name of the target object. object_name
field_name The RODM object name of the target object.
The field name being used. field_name
The RODM type being used. field_type
The value to be added to the RODM field. field_value
The name of the service point to which the sp_name
command was sent. The name of the service point to which the
The name of the network management application application.element
that processes the command string at this service The name of the network management application
point. When multiple applications are supported that processes the command string at this service
the format is application.element, where element is point. When multiple applications are supported
the name of the subapplication running. the format is application.element, where element is
module_name the name of the subapplication running.
The name of the module that was running at the module_name
time the error was discovered. The name of the module that was running at the
System action
MultiSystem Manager cancels the command. System action
Operator response
Ensure a valid 4-byte hexadecimal number is System programmer response
specified. This number must be in the range for valid Ensure the value being sent for field_type matches the
DRT nicknames. data type defined in RODM for that field_name and the
FLC091E VALUE IS INCONSISTENT WITH value sent for the field_value is of the same type.
DATA TYPE IN FIELD VALUE FLC092E OBJECT REPRESENTING
STRUCTURE. FUNCTION = keyword_name keyword_value
function, OBJECT CLASS = DOES NOT EXIST IN RODM.
object_class, OBJECT NAME = command_name COMMAND
object_name, FIELD = field_name ENDED IN MODULE module_name
field_type field_value, SERVICE WITH RETURN CODE return_code.

Explanation object_class
A request was issued to retrieve topology data. The
request cannot be completed. The resource specified object_name
in the command must exist in RODM before the The RODM object name of the target object.
request can be completed. field_name
Message Variables The field name being used.
field_type
keyword_name
The keyword specified on the related GETTOPO
command. field_value
keyword_value
The value specified for that keyword on the related sp_name
GETTOPO command. This is the object that caused The name of the service point to which the
the message to be generated. command was sent.
command_name application.element
The command that was issued. The name of the network management application
module_name
return_code
module_name
The return code from the module.
System action
Operator response
Ensure that the resource name is spelled correctly and Operator response
that the resource is in RODM. If this does not resolve
the problem, notify the system programmer.

Ensure a hexadecimal number is being sent for the
Determine the correct name of the resource or
field_value.
determine why the resource is not in RODM.
FLC094E MESSAGE TO OPERATOR
FLC093E HEX VALUE EXPECTED FOR THE
REJECTED. REASON =
VALUE OF THE RESERVED WORD.
error_reason, TYPE = error_type,
DATA = error_data. COMMAND
CLASS = object_class, OBJECT
NAME = object_name, FIELD =
SERVICE POINT = sp_name, Explanation
APPLICATION NAME = This message is generated when there is an error with
application.element. COMMAND the Message To Operator command sent. Data is also
ENDED IN MODULE module_name. piped to the log.
Message Variables
Explanation
error_reason
The reason the Message To Operator failed
for the field_value is not a hexadecimal value.
error_type
Message Variables The type of error, which parameter was not valid
function error_data
The function to be performed on the target object. The data that was not valid

Ensure each data record starts with a TX=(and ends
with a closing ).
System action FLC096E THE AGENT DOES NOT SUPPORT

THE VALUE SPECIFIED FOR THE
MultiSystem Manager cancels the command. PARAMETER keyword_parm.
Operator response APPLICATION NAME =

Explanation
Ensure the Message To Operator command is being
built correctly with correct header information. Correct
for the keyword_parm is not supported by the agent.
and reissue the command.
This error is generated by the agent and returned to
FLC095E THE FORMAT OF THE DATA SENT the host.
FROM THE AGENT IS INVALID.
Message Variables
APPLICATION NAME = keyword_parm
application.element, RECORD: The value of the keyword.
record. COMMAND ENDED IN sp_name
MODULE module_name. The name of the service point to which the
command was sent.
Explanation application.element
This message is generated when a data record is found The name of the network management application
without the TX=( preceding it, or a closing ) following that processes the command string at this service
it. point. When multiple applications are supported
Message Variables the name of the subapplication running.
sp_name module_name
The name of the service point to which the The name of the module that was running at the
command was sent. time the error was discovered.
record
The data record in error. System action
application.element MultiSystem Manager cancels the command.
Operator response
the format is application.element, where element is Notify the system programmer.
Reissue the GETTOPO command with a correct value
in the keyword_parm parameter. Refer to the agent
documentation.
System action
FLC097E THE FUNCTION function MUST BE
MultiSystem Manager cancels the command. SPECIFIED WITHOUT ANY OTHER
FUNCTIONS. SERVICE POINT =
Operator response sp_name, APPLICATION NAME =
Notify the system programmer. application.element. COMMAND

Explanation object_name
This message is generated when a function must be
specified alone and other functions are sent with it. field_name
Message Variables
field_type
function The RODM type being used.
field_value
sp_name
command was sent.
application.element
module_name the name of the subapplication running.
module_name
System action
Operator response
Ensure the function being sent can have data following System programmer response
it. If the function does not allow data, remove the
Ensure the value for field_value being sent is valid for
excess data. Refer to the agent documentation for a
the field_name specified. MultiSystem Manager:
list of functions that must be sent alone.
Topology Agent Developer's Guide lists the valid values.
FLC098E THE VALUE SPECIFIED FOR THE
FLC099E THE FUNCTION function IS NOT
RESERVED WORD IS NOT VALID.
VALID FOR COMMAND TYPE
command_type. SERVICE POINT =
CLASS = object_class, OBJECT
NAME = object_name, FIELD =
APPLICATION NAME =
application.element. COMMAND Explanation
ENDED IN MODULE module_name. This message is generated when a function is sent that
is not valid for the command_type type running.
Explanation
Message Variables
function
for the field_value is not valid for the field_name
specified.
command_type
Message Variables The number indicating which command type was
function being run.
The function to be performed on the target object. sp_name
object_class The name of the service point to which the
The RODM object class of the target object. command was sent.

module_name module_name
The name of the module that was running at the The name of the module that was running at the
time the error was discovered. time the error was discovered.



Ensure the function sent is valid for the type of Ensure the value being sent for DISPLAY STATUS is
command running. The following are the valid hexadecimal.
command types and numbers.
FLC101E THE AGENT IS UNABLE TO
1 OBTAIN SYSTEM RESOURCES
Initial Contact NECESSARY TO CONTINUE
2 PROCESSING. SERVICE POINT =
Send Topology sp_name, APPLICATION NAME =
3
Send Topology Updates
4
Explanation
Message to Operator
5 This message is generated when the agent is unable to
Alerts and Resolves obtain system resources necessary to continue
processing. This error is generated by the agent and
6 returned to the host.
Heartbeat
Message Variables
7
Return Code sp_name
FLC100E HEX VALUE EXPECTED FOR command was sent.
DISPLAY STATUS CODE. SERVICE
POINT = sp_name, APPLICATION application.element
NAME = application.element. The name of the network management application
COMMAND ENDED IN MODULE that processes the command string at this service
module_name. point. When multiple applications are supported
Explanation
module_name
This message is generated when a value sent for The name of the module that was running at the
DISPLAY STATUS is not hexadecimal. time the error was discovered.
Message Variables
System action
sp_name
The name of the service point to which the MultiSystem Manager cancels the command.
command was sent.

Notify the system programmer. This message is generated when the agent receives a
command to send topology updates but no updates
System programmer response exist. This error is generated by the agent and returned
to the host.
Ensure the agent has enough resources to complete
the command. Refer to the agent documentation for Message Variables
additional information. sp_name
FLC102E THE AGENT IS UNABLE TO The name of the service point to which the
COLLECT TOPOLOGY command was sent.
INFORMATION. SERVICE POINT = application.element
sp_name, APPLICATION NAME = The name of the network management application
application.element. COMMAND that processes the command string at this service
ENDED IN MODULE module_name. point. When multiple applications are supported
Explanation the name of the subapplication running.
module_name
This message is generated when the agent is unable to
collect topology information. This error is generated by
the agent and returned to the host.
command was sent.
Operator response
application.element
The name of the network management application Notify the system programmer.
point. When multiple applications are supported System programmer response
Determine why the agent does not have any topology
updates. Reissue the GETTOPO command.
module_name
The name of the module that was running at the FLC104E THE AGENT RECEIVED A SEND
time the error was discovered. TOPOLOGY COMMAND, BUT NO
SESSION EXISTS. SERVICE POINT
= sp_name, APPLICATION NAME =
System action
MultiSystem Manager cancels the command. ENDED IN MODULE module_name.

Notify the system programmer. This message is generated when the agent receives a
command but no session has been established. This
System programmer response error is generated by the agent and returned to the
host.
Determine why the agent can not collect topology and
fix the problem. Refer to the agent documentation for Message Variables
additional information. sp_name
FLC103E THE AGENT RECEIVED A SEND The name of the service point to which the
TOPOLOGY UPDATES COMMAND, command was sent.
BUT NO UPDATES EXIST. SERVICE application.element
POINT = sp_name, APPLICATION The name of the network management application
NAME = application.element. that processes the command string at this service
COMMAND ENDED IN MODULE point. When multiple applications are supported
module_name. the format is application.element, where element is

module_name sp_name, APPLICATION NAME =
The name of the module that was running at the application.element. COMMAND
time the error was discovered. ENDED IN MODULE module_name.

MultiSystem Manager cancels the command. This message is generated when the agent has
experienced a problem. This error is generated by the
Operator response agent and returned to the host. The agent has
generated a return code value of 2000 to MultiSystem
Notify the system programmer. Manager and has provided MultiSystem Manager with
the problem text for this message.
Message Variables
Determine why no session exists and fix the problem.
problem
Reissue the GETTOPO command.
Information about the problem experienced.
FLC105E THE AGENT IS TERMINATING. sp_name
SERVICE POINT = sp_name, The name of the service point to which the
APPLICATION NAME = command was sent.
application.element
Explanation point. When multiple applications are supported
This message is generated when the agent is ending. the format is application.element, where element is
This error is generated by the agent and returned to the name of the subapplication running.
the host. module_name
Message Variables The name of the module that was running at the
sp_name
The name of the service point to which the System action
command was sent.
application.element
that processes the command string at this service Operator response
point. When multiple applications are supported If the PROBLEM TEXT is NULL, this error can occur if
the format is application.element, where element is the command was issued with SECURE=NO to a port
the name of the subapplication running. that had been set up to be secure. In this case, check
module_name the security of the port and reissue the command with
The name of the module that was running at the the correct parameters. Notify the system
time the error was discovered. programmer.

MultiSystem Manager cancels the command. Determine what problem the agent experienced and
fix it. Refer to the agent documentation for additional
Operator response information.
Notify the system programmer. FLC107E THE AGENT HAS FAILED. SERVICE
System programmer response NAME = application.element.
Determine why the agent is ending. Refer to the agent module_name.
documentation for additional information.
FLC106E THE AGENT EXPERIENCED A Explanation
PROBLEM. PROBLEM TEXT: This message is generated when the agent has failed.
problem. SERVICE POINT = This error is generated by the agent and returned to

the host. The agent has not provided MultiSystem System action
Manager with a valid return code.
Message Variables
sp_name Operator response
The name of the service point to which the Notify the system programmer.
command was sent.
application.element System programmer response
that processes the command string at this service Determine what command was sent and correct it.
point. When multiple applications are supported Refer to the agent documentation for additional
the format is application.element, where element is information.
the name of the subapplication running. FLC109E THE AGENT DOES NOT SUPPORT
module_name THE PARAMETER parameter.
The name of the module that was running at the SERVICE POINT = sp_name,
time the error was discovered. APPLICATION NAME =
System action ENDED IN MODULE module_name.
MultiSystem Manager cancels the command. Explanation
Operator response This message is generated when an unsupported

parameter is sent to the agent. This error is generated
Notify the system programmer. by the agent and returned to the host.
Message Variables
parameter
Determine why the agent failed. Refer to the agent The parameter sent to the agent.
documentation for additional information.
sp_name
FLC108E THE COMMAND RECEIVED BY THE The name of the service point to which the
AGENT WAS NOT VALID. SERVICE command was sent.
application.element
module_name.
Explanation the name of the subapplication running.
This message is generated when an incorrect module_name
command is sent to the agent. This error is generated The name of the module that was running at the
by the agent and returned to the host. time the error was discovered.
Message Variables
System action
sp_name
The name of the service point to which the MultiSystem Manager cancels the command.
command was sent.
application.element Operator response
The name of the network management application Notify the system programmer.
the name of the subapplication running. Determine why the parameter sent is unsupported,
module_name correct the parameter and retry the command. Refer
The name of the module that was running at the to the agent documentation for additional information.
time the error was discovered. FLC110E VALUE SPECIFIED FOR THE ALERT
LOGGING AND STATUS CHANGE

INDICATOR IS NOT VALID. application.element
SERVICE POINT = sp_name, The name of the network management application
APPLICATION NAME = that processes the command string at this service
application.element. COMMAND point. When multiple applications are supported
ENDED IN MODULE module_name. the format is application.element, where element is
Explanation module_name
This message is generated when the status change
and alert history log parameter is incorrect.
command was sent.
Operator response
application.element
The name of the network management application Reissue the command with the required parameter.
that processes the command string at this service FLC112E FILTER filter_parm IS NOT VALID
point. When multiple applications are supported FOR THE COMMAND SPECIFIED.
the format is application.element, where element is SERVICE POINT = sp_name,
the name of the subapplication running. APPLICATION NAME =
module_name application.element. COMMAND
The name of the module that was running at the ENDED IN MODULE module_name.
Explanation
System action
MultiSystem Manager cancels the command. for the filter_parm is not valid for the command
specified.
Notify the system programmer. filter_parm
The filter parameter to be used with the command.
System programmer response sp_name
Determine why the specified parameter is incorrect The name of the service point to which the
and correct it. command was sent.
application.element
FLC111E THE AGENT REQUIRES THE
parameter PARAMETER TO BE
SPECIFIED. SERVICE POINT =
module_name
Explanation The name of the module that was running at the
This message is generated when the parameter is not
specified on the GETTOPO command. System action
Message Variables MultiSystem Manager cancels the command.
parameter
The name of the parameter that is required by the Operator response
agent.
sp_name
command was sent.

Reissue the command where the value of the This message is generated when the object specified
filter_parm is equal to 1STFIELD. can not be found in RODM. If an object identifier is
specified, only the object_class_id value will be
FLC113E MULTISYSTEM MANAGER displayed in the message. If both the object class and
REQUIRES THAT THE FOLLOWING name are specified, both will be displayed in the
PROGRAMS ARE RUNNING ON message.
SERVICE POINT sp_name.
command_name COMMAND Message Variables
ENDED IN MODULE module_name command_name
WITH RETURN CODE return_code The command that was issued
required_programs
module_name
Explanation
A request was issued to retrieve topology data. The object_identifier
request cannot be completed because MultiSystem The RODM object identifier
Manager has determined that all required programs
are not running on the specified service point. return_code
For service points running in a distributed
object_class_id
environment, such as IBM Z NetView, these required
The RODM object class of the object or the object
programs might be running on systems other than the
identifier whichever is specified
service point.
object_name
Message Variables The RODM object name of the object, if specified
sp_name
The name of the service point to which the System action
GETTOPO command was sent
command_name
Operator response
module_name
The name of the module that was running at the Notify the system programmer.
return_code
The return code from the module Reissue the command with a valid RODM object class
required programs and name or object identifier that is already defined in
A list of the programs that MultiSystem Manager RODM.
expect to be running FLC115E THE ELEMENT KEYWORD MUST BE
SPECIFIED FOR AGENTS WHICH
System action SUPPORT agent_type. SERVICE
MultiSystem Manager cancels the command. POINT = sp_name, APPLICATION
Operator response module_name.
Ensure that the required programs are running.
Explanation
FLC114E SPECIFIED OBJECT DOES NOT
EXIST IN RODM. OBJECT This message is generated when the ELEMENT
IDENTIFIER = object_identifier, keyword is not specified and the agent_type indicates
OBJECT CLASS = object_class_id, that multiple applications, known as elements, can be
OBJECT NAME = object_name. running on the same service point. The ELEMENT
command_name COMMAND keyword is used to differentiate between different
ENDED IN MODULE module_name subapplications running at the service point.
Message Variables

agent_type System action
The type of agent that is running.
sp_name
Operator response
command was sent.
application.element
point. When multiple applications are supported Check the log for the RODM processing errors, correct
the format is application.element, where element is the problems and reissue the command.
module_name
INITIALIZATION FILE file_name.
IT IS NOT VALID FOR THE
next_statement STATEMENT TO
System action FOLLOW THE previous_statement
MultiSystem Manager cancels the command. STATEMENT. command_name
Operator response
CODE return_code.
Explanation
MultiSystem Manager cannot initialize topology and
Reissue the command with the ELEMENT keyword status because the statements in the exception view
specifying a subapplication. file are out of sequence.
FLC116W RODM PROCESSING ERROR. Message Variables
ERROR OCCURRED WHILE
file_name
PROCESSING RESPONSE FROM
The name of the MultiSystem Manager exception
AGENT. GETTOPO PROCESSING
view file specified on the EXCEPTION_VIEW_FILE
CONTINUES. SERVICE POINT =
initialization file
ENDED IN MODULE module_name. next_statement
The statement specified after previous_statement
Explanation previous_statement
The statement specified before next_statement
This message is generated when an error with the data
the agent has sent occurs, but it was not severe command_name
enough for processing to be halted. The command that was issued.
module_name
Message Variables
sp_name time the error was discovered
The name of the service point to which the return_code
command was sent. The return code from the module
application.element
The name of the network management application System action
point. When multiple applications are supported • MultiSystem Manager cancels the INITTOPO
the format is application.element, where element is command.
the name of the subapplication running. • MultiSystem Manager does not perform Network
module_name topology initialization.
The name of the module that was running at the • MultiSystem Manager status changes to
time the error was discovered. INITIALIZATION_FAILED.

Notify the system programmer. If the exception view name specified on the
EXVWNAME statement in the exception view
System programmer response initialization file is incorrect, correct the error and
reissue the INITTOPO command. If the exception view
Correct the error in the MultiSystem Manager name specified on the EXVWNAME statement is
exception view initialization file and reissue the correct, the exception view class object needs to be
INITTOPO command. See the prologue of sample created in RODM. Modify the appropriate sample
FLCSEXV for more detail regarding exception view loader file to create the exception view class object.
processing. The sample loader files that create the exception view
FLC119E UNABLE TO INITIALIZE class objects start with FLCSDM6. See the prologue of
MULTISYSTEM MANAGER WITH sample FLCSEXV for information regarding exception
INITIALIZATION FILE file_name. view processing.
EXCEPTION VIEW CLASS OBJECT FLC120E ELEMENT AND CMD KEYWORD
object DOES NOT EXIST IN RODM. CAN NOT BE SPECIFIED
command_name COMMAND TOGETHER. SERVICE POINT =
ENDED IN MODULE module_name sp_name, APPLICATION NAME =
WITH RETURN CODE return_code. application.element. COMMAND
command_name ENDED IN
Explanation MODULE module_name.
MultiSystem Manager cannot initialize topology and
status. An exception view class is specified in the Explanation
exception view file but the RODM object representing The specified command contains the ELEMENT and
this class does not exist. CMD keywords which cannot be specified together.
file_name sp_name
The name of the MultiSystem Manager exception The name of the service point to which the
view file specified on the EXCEPTION_VIEW_FILE command was sent.
initialization file application.element
object processing the command string at this service
The RODM object specified in the MultiSystem point. When multiple applications are supported
Manager exception view name the format is application.element, where element is
command_name the name of the running subapplication.
The command that was issued command_name
module_name The command that was issued.
The name of the module that was running at the module_name
time the error was discovered The name of the module that was running at the
return_code time the error was discovered.
System action
System action
command. Operator response
• MultiSystem Manager does not perform Network Reissue the command with valid keywords. See the
topology initialization. NetView online help for the command syntax.
• MultiSystem Manager status changes to
INITIALIZATION_FAILED. FLC121E UNABLE TO COMMUNICATE WITH
THE AGENT AT SERVICE POINT =
Operator response application.element. COMMAND
Notify the system programmer. command_name ENDED IN
MODULE module_name.

The specified command was sent to the service point
but the service point was unable to communicate with
the agent. System action
Message Variables MultiSystem Manager cancels the command.
sp_name
Operator response
command was sent. Reissue the command with double quotation marks
application.element around the value for the listed keyword. See the
The name of the network management application NetView online help for the correct command syntax.
processing the command string at this service FLC126I GETTOPO COMMANDS FROM
point. When multiple applications are supported MULTISYSTEM MANAGER
the format is application.element, where element is INITIALIZATION FILE file_name
the name of the running subapplication. HAVE BEEN PROCESSED.
command_name
The command that was issued. Explanation
module_name The GETTOPO commands coded in the MultiSystem
The name of the module that was running at the Manager file_name have been processed.
Message Variables
System action file_name
The name of the initialization file that was
processed.
Operator response FLC130I THRESHOLD NAME STATUS

Verify that the NetView for AIX GUI and the
msmatm_agent process are active at the agent, and Explanation
reissue the command. The agent provides a SMIT This message contains the list of threshold names and
interface to check the status of its processes. their associated status.
FLC122E VALUE value IS NOT VALID FOR FLC131I THERE ARE NO THRESHOLDS IN
KEYWORD keyword. REQUIRED NON-SATISFACTORY STATUS.
DOUBLE QUOTES ARE MISSING.
command_name COMMAND Explanation
WITH RETURN CODE return_code. The DISPTHR command was issued, but there are no
threshold names in an unsatisfactory status.
Explanation FLC132I THRESHOLD NAME MONITOR
Double quotation marks are required around the NAME STATUS
specified value.
Explanation
Message Variables
This message contains the list of threshold names and
value
their associated monitor names and status.
The value that is not valid for the specified
keyword FLC133I THERE ARE NO MONITORS IN
keyword NON-SATISFACTORY STATUS.
A keyword for which the value was specified
command_name Explanation
The command that was issued The DISPMON command was issued, but there are no
module_name monitors with thresholds in an unsatisfactory status.
The name of the module that was running at the FLC134I PROCESS NAME

This message contains the list of processes that did MultiSystem Manager cancels the command.
not load or were unable to load.
FLC135I THERE ARE NO PROCESSES IN Operator response
NON-SATISFACTORY STATUS. Check that the service point and port number were
specified correctly. Check the TCP/IP connectivity
Explanation between the service point and NetView program.
The DISPPRC command was issued, but there are no
processes that cannot be loaded. System programmer response
Ensure TCP/IP is running and any required links to the
FLC136I PROTOCOL NAME::ADDRESS
service point are up.
STATUS
FLC141E FLCACCHK HAS DENIED ACCESS
Explanation TO SERVICE POINT sp_name FOR
APPLICATION application AND
This message contains the list of protocol names and PORT port WITH RETURN CODE
addresses and their associated status. return_code FOR COMMAND
FLC137E THE OBJECT DOES NOT BELONG command_name.
TO CLASS object_class. COMMAND
command_name IS ONLY Explanation
ALLOWED FOR OBJECTS
The NetView operator does not have access to the
BELONGING TO THIS CLASS.
command_name command being issued to the
specified service point and application.
Explanation
Message Variables
The command that was issued is not a valid command
for the object class of the specified RODM object ID. sp_name
Message Variables command was sent
object_class application
The RODM object class of the target object The name of the network management application
command_name that processes the command string at this service
The command that was issued point
port
System action The number of the port in which to communicate
with the agent
return_code
Operator response
command_name
Reissue the command with an object ID of the correct The command that was issued
class.
FLC140E TCP/IP ERROR WITH socket_call System action
CALL: tcpip_error.
Explanation
Operator response
The following TCP/IP error occurred tcpip_error in the
Ensure the module FLCACCHK is configured to allow
socket_call phase.
operators to access the correct commands.
Message Variables
socket_call System programmer response
The phase of the socket call that failed Determine which authority is incorrect and update
tcpip_error FLCACCHK with the corrections.
The error information returned from TCP/IP

FLC145W THE FOLLOWING MESSAGE(S) Operator response
INDICATE TOPOLOGY Look for more related messages until message
INCONSISTENCIES DETECTED BY FLC179I is received.
THE MSM AGENT. command_name
keyword COMMAND FOR SERVICE
POINT sp_name WITH System programmer response
APPLICATION NAME Look for more related messages until message
application_name WILL CONTINUE FLC179I is received.
PROCESSING.
FLC179I PROCESSING COMPLETE
Explanation
Explanation
There were inconsistencies in the topology data
gathered for the specified service point. The command Any FLCV2RCM messages concerning the current
will continue processing. invocation will follow this message.
Message Variables
Operator response
command_name
Previous messages concerning this invocation will be
logged starting with the FLC178I message.
keyword
The keyword or keywords specified on the System programmer response
GETTOPO command that define the type of
GETTOPO command that was issued. Previous messages concerning this invocation will be
logged starting with the FLC178I message.
sp_name
The name of the service point where the command FLC180E EMPTY statement STATEMENT
was sent. ENDING ON LINE line.
application_name
The name of the network management application Explanation
processing the command string at this service
point. The application_name is also referred to as No valid statements followed the VIEW or
the application ID. AGGREGATE statement.
Message Variables
System action statement
The system logs the inconsistencies found by the One of: VIEW or AGGREGATE, indicating the type
MultiSystem Manager agent. of collection being defined.
The MultiSystem Manager agent remains operational line
and GETTOPO commands are still processed. The line number of the input that contained the
VIEW or AGGREGATE statement.
Operator response
System action
The indicated view or aggregate is ignored.
Operator response
Resolve the agent inconsistencies.
Check for FLC184E messages following this message;
FLC178I Messages they indicate other statements that can be present,
but in error. Correct the input and retry.
Explanation
Any FLCV2RCM messages concerning the current
invocation will follow this message. Check for FLC184E messages following this message;
they indicate other statements that can be present,
System action but in error. Correct the input and retry.
Related messages follow this one. FLC181E NO INPUT RECEIVED

No input was sent to FLCV2RCM. FLCV2RCM is Processing stops.
typically invoked as a PIPE stage; when FLCV2RCM
was invoked, there was no input available. Operator response
Operator response
Check that the invocation is correct, and that input is System programmer response
being sent to FLCV2RCM.
Check the return and reason codes in the IBM Z
NetView Resource Object Data Manager and GMFHS
Programmer's Guide for help diagnosing the problem.
Check that the invocation is correct, and that input is Common FLCARODM function problems are RODM
being sent to FLCV2RCM. name and RODM authority definitions. See the
CNMSTYLE member for information on setting these
FLC182E ERROR INVOKING FLCARODM: values.
Explanation FLC184E UNSUPPORTED STATEMENT

statement ENDING ON LINE line
FLCARODM was invoked as part of FLCV2RCM
processing, but errors were encountered. Those error
Explanation
messages from FLCARODM follow this message.
A statement was encountered that is not supported.
Processing Stops. statement
The unsupported statement.
Operator response line
Check the log for FLCARODM messages, and correct The last line number of the input that concerns this
the resulting problems. statement.
Common FLCARODM function problems are RODM Processing continues.

name and RODM authority definitions. See the
CNMSTYLE member for information on setting these Operator response
values.
Check the input from the indicated line and work
FLC183I return_code/reason_code ARE THE backwards to find the unsupported statement. Correct
FLCARODM FUNCTION function that statement and retry.
RODM RETURN/REASON CODES
If this message is from the RODM collection manager
GUI, see sysprog.
Explanation
FLCARODM was invoked as part of FLCV2RCM System programmer response
processing, but an error as encountered. Those error
Check the input from the indicated line and work
messages from FLCARODM follow this message.
backwards to find the unsupported statement. Correct
Message Variables that statement and retry.
return_code If this message is from the RODM collection manager
The RODM return code of the request. GUI, record the steps taken and contact IBM Software
reason_code Support.
The RODM reason code of the request. FLC185E UNABLE TO READ CONTROL FILE
function file
The FLCARODM function being performed.

FLCV2RCM needs the control file to operate; this file file
defines the supported statements and corresponding The name of the control file.
actions to take on them. If that file cannot be found,
operation cannot continue. System action
Message Variables Processing stops.
file
The name of the control file that should exist in the Operator response
DSIPARM concatenation.
System action
Processing stops.
Check to see that File, which exists in the DSIPARM
concatenation, is the same as what was shipped with
Operator response NetView program.
Notify the system programmer. FLC187I CREATED COLLECTION OBJECT
object IN CLASS class
Check that the control file exists and is in the Explanation
DSIPARM concatenation of the NetView JCL The collection named object was successfully created.
procedure. Determine the cause of the error. If you
edited the data set since the NetView program was Message Variables
initialized, the data set might need to be compressed object
or reaccessed using the REACC command. The name of the collection.
FLC186E NO OBJECT TYPES WERE class
RECOGNIZED IN CONTROL FILE The name of the RODM class that contains the
file collection.
Explanation
The control file file was found, but it did not contain
usable information.

Chapter 12. FLCI Prefix Messages
FLCI prefix messages are issued by MultiSystem Manager Internet Protocol agent.
FLCI000E Processing finished, output file If it does, you must chose another socket and
name is: file_name. specify it in the topology agent's NetView for AIX
registration file usr/OV/registration/C/
Explanation flci.reg.
2. Retry the operation.
The MultiSystem Manager IP topology agent has
successfully written the specified topology file. FLCI003E Unable to allocate socket.
FLCI001E Unable to communicate to local
AIX host. Explanation
An error occurred while trying to allocate a socket for
Explanation AIX process flcidrv.
The MultiSystem Manager IP topology agent driver
was unable to communicate with the local AIX host System action
system. AIX process flcidrv ends.

AIX process flcidrv ends. Retry the operation. If it still fails, contact the system
programmer.
Operator response
1. Verify that the socket specified in the topology
System programmer response agent's NetView for AIX registration file does not
conflict with another socket address specified in
The local AIX operating environment might have
the /etc/services file.
become unstable. See NetView for AIX Problem
Determination for problem resolution. If it does, you must chose another socket and
specify it in the topology agent's NetView for AIX
FLCI002E Unable to use specified socket. registration file usr/OV/registration/C/
flci.reg.
Explanation
2. Retry the operation. If the problem persists, the
An unusable socket number was given to AIX process local AIX operating environment might have
flcidrv. become unstable. See NetView for AIX Problem
Determination for problem resolution.
System action FLCI004E Unable to connect to server:
AIX process flcidrv ends. connection_error
Retry the operation with a socket number that is both The listed connection error occurred while trying to
greater than 2999 and not in use. If the operation still establish a socket connection between AIX processes
fails, contact the system programmer. flcitopo and flcidrv.
1. Verify that the socket specified in the topology AIX process flcidrv ends.
agent's NetView for AIX registration file does not
conflict with another socket address specified in
the /etc/services file.

Retry the operation. If it still fails, contact the system An error occurred while attempting to use the
programmer. specified file for topology data.

Restart the topology agent. If the problem persists, Topology file is not created.
the local AIX operating environment might have
become unstable. See NetView for AIX Problem Operator response
Retry the operation. If it still fails, contact the system
FLCI005E Unable to send to server: programmer.
send_error
Explanation
Verify that file permissions allow AIX process flcitopo
The listed error occurred while attempting to send a to write the file in the specified location.
message from AIX process flcidrv to flcitopo.
FLCI008E OVw database returned a null
map.
System action
AIX process flcidrv ends. Explanation
The MultiSystem Manager IP topology agent was
Operator response
unable to obtain map information from NetView for
Retry the operation. If unsuccessful, contact the AIX.
system programmer.
System action
Topology file is not created.
become unstable. See NetView for AIX Problem Operator response
Verify that NetView for AIX is running and responds
FLCI006E Unable to receive from server: normally to user input. Retry the operation. If it still
receive_error fails, contact the system programmer.

The listed error occurred while AIX process flcidrv Restart NetView for AIX. If the problem persists, see
attempted to receive a message from flcitopo. NetView for AIX Problem Determination for problem
resolution.
System action
FLCI009E OVw database returned a null
AIX process flcidrv ends. symbol list.

Retry the operation. If it still fails, contact the system The MultiSystem Manager IP topology agent was
programmer. unable to obtain a submap symbol list from NetView
for AIX.
System action
become unstable. See NetView for AIX Problem Topology file is not created.
FLCI007E Unable to use specified file name: Operator response
file_name Retry the operation. If the problem persists, contact

Restart NetView for AIX. If the problem persists, see Retry the operation using the correct parameters.
NetView for AIX Problem Determination for problem
FLCI013E Undefined return code received
resolution.
from AIX process flcitopo.
FLCI010E OVw database returned a null field
bind list. Explanation
AIX process flcidrv received an undefined return code
Explanation
from flcitopo.
The MultiSystem Manager IP topology agent was
unable to obtain an object's field value list from System action
NetView for AIX.
AIX process flcidrv ends.
System action
Operator response
Topology file is not created.
Retry the operation. If the problem persists, contact
Operator response
Retry the operation. If it still fails, contact the system System programmer response
programmer.
become unstable. See NetView for AIX Problem
Determination for more information that can help you
Restart NetView for AIX. If the problem persists, see solve the problem.
NetView for AIX Problem Determination for more
information that can help you solve the problem. FLCI014E Topology agent request timed out.
FLCI011E Topology agent is managing map: Explanation

attached_map_name
A timeout occurred while AIX process flcidrv was
waiting for a response from AIX process flcitopo
Explanation
Process FLCITOPO is currently attached to a map that System action
does not match the requested map.
System action
Operator response
The topology file is not created.
Stop any unnecessary processes to free system
resources. Retry the operation. If the problem
Operator response
persists, contact the System Programmer.
1. Open the desired map through the NetView for AIX
end user interface. System programmer response
2. Stop and restart the MultiSystem Manager topology The AIX system might be too busy to process the
agent. topology information before the mainframe NetView
3. Retry the operation. COS gateway timeout occurs. If the AIX system
performance cannot be improved by increasing paging
FLCI012E Incorrect invocation.
space or by stopping unnecessary processes, increase
the mainframe NetView COS gateway timeout and
Explanation specify a longer timeout value for the AIX process
AIX process flcidrv was invoked with incorrect flcidrv.
parameters. FLCI015E Topology agent fatal condition:
exit_condition_text
System action
Chapter 12. FLCI Prefix Messages 639

The MultiSystem Manager IP topology agent logged a The current MultiSystem Manager IP topology agent
fatal condition. configuration.
FLCI019E Topology agent did not find
System action specified resource: resource_name
AIX process flcitopo ends.
Explanation
Operator response The specified resource does not exist in the NetView
Contact the system programmer. for AIX database.
Check the file /usr/OV/log/flcitopolog for the cause of Topology file is not created.
the problem.
Operator response
FLCI016E Topology agent error: error_text
1. Verify that the resource actually exists in NetView
Explanation for AIX by using NetView for AIX's Locate Objects
By Selection Name function.
The MultiSystem Manager IP topology has logged an
2. Retry the operation, specifying a resource that
error.
exists in NetView for AIX.
System action FLCI020E Topology agent unavailable.

Explanation
Operator response The topology agent is not currently running.
System action
System programmer response AIX process flcidrv ends.
Check the file /usr/OV/log/flcitopolog for the
cause of the error. Operator response
Verify that NetView for AIX, including the user
FLCI017I Topology agent message:
interface, is running.
message_text
1. If it is, select the NetView for AIX menu option to
Explanation restart the MultiSystem Manager topology agent.
The MultiSystem Manager IP topology agent logged a 2. If NetView for AIX is not running, restart it.
message. 3. Retry the operation.
FLCI021E Topology agent unable to write
System action specified file: file_name
Agent processing continues.
Explanation
FLCI018I Current® topology agent
configuration: Agent=status The MultiSystem Manager IP topology agent was
Port=socket_port unable to write the specified file. The problem might
Host=AIX_host_name be in the AIX file system.
NvLevel=NetView for AIX_version
AgentLevel=agent_version System action
DrvLevel=driver_version
MapName=attached_map_name Topology file is not created.

Retry the operation. If problem persists, contact the Run ovtopofix against the database in which the
system programmer. looping error occurred.
FLCI024E GETTOPO command has been
System programmer response issued but no response is
1. Verify that there is enough room in the specified file received.
system and that file permissions allow the NetView
for AIX operator to write. Explanation
2. Delete old or unnecessary files. No response for GETTOPO command can indicate the
3. Retry the operation. agent is busy.
If the problem persists, the local AIX operating
environment is probably unstable. See NetView for AIX System action
Problem Determination for problem resolution The GETTOPO command cannot be completed.
information.
FLCI022I Stop message has been sent to Operator response
topology agents. Retry the operation. If the condition persists, contact
Explanation
Running topology agents were instructed to stop after System programmer response
they complete their last pending request. Determine whether the agent is taking an abnormally
FLCI023E OVw database contains a loop long time to complete the task. This time frame can be
concerning these objects: established by system programmer experience or by
objects_in_error looking at differences in timestamps between start
and end log entries in the /usr/OV/log/flcitopolog log.
If the command is taking too long to complete, the
Explanation
problem might be in database. Check the cache size of
The MultiSystem Manager IP topology agent ovwdb versus how many objects are in the database.
encountered a looping condition in the OVw database. There should be a 15% cushion. If this is not the cause
of the problem, issue the following command:
System action
ovtopofix -f
Operator response
Chapter 12. FLCI Prefix Messages 641

Chapter 13. IHS Prefix Messages Issued from the
Host
IHS prefix messages are used for NetView instrumentation. This chapter describes IHS prefix messages
that are issued from the host. Chapter 14, “IHS Prefix Messages Issued from the NetView Management
Console Workstation,” on page 699 describe IHS prefix messages that are issued from the NetView
management console workstation.
Note: In some instances, a message number issued from the host might be identical to a message
number issued from the NetView management console workstation, differing only in the suffix. Both the
text of the message and the explanation of the message are very different. For example, IHS0200I is
issued from the host, while IHS0200E is issued from the workstation.
Message IHS0200I reads:
"service: Number of ServerPorts (number) exceeds the maximum of maximum; ignoring extras."
An explanation follows, providing additional details specific to the IHS0200I message.
Message IHS0200E reads:
"The configuration file ihscacm.cfg was not found. Verify that the file exists in the $BINDIR/TDS/
Server/config directory and that the BINDIR environment variable is set."
An explanation follows, providing additional details specific to the IHS0200E message,
IHS001I HEARTBEAT INTERVAL FOR CMAS System programmer response
COMPONENTS IS SET TO number Specify the correct parameters in DSIAMII.
MINUTES.
IHS003E CICS MONITORING NOT STARTED.
Explanation START PARAMETER NOT VALID.
The current heartbeat interval (number) in minutes for

Explanation
the CICSPlex® SM address space (CMAS) components.
CICSPlex SM Instrumentation cannot start CICS®
Message Variables
monitoring because one or more parameters in the
number IHSCCIIN call in DSIAMII were missing or not valid.
The number of minutes to which the heartbeat
interval is set as returned by the Query Pulse task. System action
IHS002E CMAS MONITORING NOT CICS monitoring is not started, processing continues.
STARTED. START PARAMETER
NOT VALID. Operator response
CICSPlex SM Instrumentation cannot start CICSPlex System programmer response

SM address space (CMAS) monitoring because one or
more parameters in the IHSCCMIN call in DSIAMII Specify the correct parameters in DSIAMII.
were missing or not valid.
IHS004E CICSPLEX SM INSTRUMENTATION
RELEASE NOT VALID.
System action
CMAS monitoring is not started, processing continues. Explanation
The start parameter in the IHSCCIIN call in DSIAMII
Operator response for the product release was missing or not valid.
Notify your system programmer
System action
CICSplex SM Instrumentation does not proceed.

Operator response module name
The routine to which the incorrect CID was passed.
component ID
System programmer response The passed component identifier.
return code
Specify the correct parameters in DSIAMII. The return code identifying the failure.
IHS005I EVENT IDENTIFIER NOT FOUND.
System action
Explanation The current task fails to complete.
The Display Last Event task ran, but no events exist for
the component at the present time. Operator response
IHS007E CPSMAPI FAILED text, RESPONSE Notify your system programmer.
value, REASON value, RESULT
value System programmer response
See the IBM CICSPlex System Manager for MVS/ESA
Explanation
Application Program Interface for details about return
CICSPlex SM Instrumentation cannot establish a codes for the specified API.
connection due a CICSPlex SM API problem.
IHS010I IRC STATE IS value
Message Variables
text Explanation
Error text that explains the API call being executed The current interregion communication (IRC) state
when the failure occurred. For example, "ERROR value.
PERFORMING TPARSE".
Message Variables
value
The response, reason, and result values returned value
by the API called. The current IRC state value as returned by the
Query IRC State task.
The result value is optionally returned.
IHS012I VTAM STATE IS value.
System action
CICSPlex SM instrumentation does not proceed. Explanation
The current VTAM state value.
Notify your system programmer. value
The current VTAM state value as returned by the
System programmer response Query VTAM State task.
See the IBM CICSPlex System Manager for MVS/ESA IHS013E INPUT PARAMETER parm NOT
Application Program Interface manual for more VALID.
information about the returned response, reason and
result values.
Explanation
IHS008E module name FAILED FOR CICSPlex SM Instrumentation ran an internal task
component ID, RETURN return using a parameter that was not valid.
code.
Message Variables
Explanation parm
The incorrect parameter value.
The specified IBM Z NetView Instrumentation Facility
API call failed for the specified component.
System action
Message Variables
The current task fails to complete.

Notify your system programmer. The current task fails to complete.

Contact IBM Software Support. Notify the system programmer.
IHS014I HEARTBEAT INTERVAL FOR CICS
COMPONENTS IS SET TO number System programmer response
MINUTES. Contact IBM Software Support.
IHS503E LOCATE TASK CONTAINS
Explanation
INCORRECT INPUT VALUE
The heartbeat for the CICS components is currently resource_name IN CLIST
set at the time interval (number) in minutes. module_name.
Message Variables
Explanation
number
The number of minutes to which the time interval The user has entered an incorrect resource name in
is set as returned by the Query Pulse task. the LOCATE pop-up dialog.
IHS500E GLOBAL VARIABLE PREFIX Message Variables

IHS.DB2.GLOBAL.PREFIX NOT resource_name
DEFINED. INITAMI HAS NOT BEEN The erroneous value passed to the LOCATE task.
RUN.
module_name
The name of the module that detected the error.
Explanation
The INITAMI command was not run before the System action
instrumentation routines were called. Do not issue the
The LOCATE task fails to complete.
DB2® CLISTs directly.
Operator response
System action
Ensure the name entered is formatted correctly (as per
DB2 instrumentation ends.
DB2 SQL statement conventions). Then issue the
LOCATE task again.
Operator response
IHS504E GEM API API_name FAILED WITH
Notify the system programmer. RC return_code FOR CID IN CLIST
module_name.
Run the NetView INITAMI command. Explanation
IHS502E GLOBAL VARIABLE variable name The Tivoli GEM API API_name return code was not
NOT DEFINED IN CLIST module zero.
name. Message Variables
API_name
Explanation
The name of the Tivoli GEM API routine that failed.
The IBM Z NetView global variable variable name was return_code
not initialized. The return code from the Tivoli GEM API routine.
Message Variables CID
variable name The component identifier.
The name of the global variable. module_name
module name The module from which the Tivoli GEM API was
The name of the module from which the global called.
variable was referenced.
Chapter 13. IHS Prefix Messages Issued from the Host 645
The current task fails to complete. A utility in the specified DB2 subsystem ended
abnormally.
Notify the system programmer. subsystem
The DB2 subsystem name.
IHS509I DDF FOR subsystem UP AND
Report to IBM Software Support any return codes that OPERATIONAL.
are more severe than the warning level as documented
in the Tivoli GEM Advanced Business System Explanation
Enablement Guide.
The distributed data facility (DDF) for the specified
IHS505I INCORRECT INPUT VALUE FOR DB2 subsystem started successfully.
ACCESS TYPE. VALUE MUST BE
RW OR RO. Message Variables
subsystem
Explanation The DB2 subsystem prefix.
The access type entered was not RW (read write) or IHS510I API namemessage text
RO (read only).
Explanation
System action
This message is used to prefix the output of all DB2
The task fails to complete. commands issued from the Tivoli GEM console.
Message Variables
Operator response
message text
Specify the correct access type parameter, then invoke The output of all DB2 commands issued from the
the task again. Tivoli GEM console.
IHS506I subsystem NOT STARTED
System action
Explanation The specified Tivoli GEM API ran successfully.
The specified DB2 subsystem was not started. IHS511I DATABASE DSNDB01 (SYSTEM
Message Variables DIRECTORY) CANNOT BE
QUERIED.
subsystem
Explanation
System action The LOCATE task cannot query database DSNDB01

because it is the system directory.
No instrumentation will be performed for this DB2
subsystem. IHS512E DSIGET FAILURE.
IHS507I DDF FOR subsystem NOT
Explanation
STARTED.
The NetView DSIGET command failed in the
Explanation IHSB2SQL routine.
The distributed data facility (DDF) for the specified

System action
DB2 subsystem was not started.
Message Variables
subsystem Operator response
IHS508I UTILITY ABENDED FOR
subsystem.

Contact IBM Software Support. Contact IBM Software Support.
IHS513E A MINIMUM OF 2 PARAMETERS IHS516E THE SQL STATEMENT EXCEEDS
REQUIRED. THE MAXIMUM OF 256
CHARACTERS.
Explanation
Explanation
A parameter that was passed to the IHSB2SQL routine
was not valid. A parameter that was passed to the IHSB2SQL routine
was not valid.
System action
System action
Operator response
Operator response
IHS514E THE DB2 SUBSYSTEM NAME MUST
BE 1-4 CHARACTERS LONG. IHS517E CONNECT TO DB2 SUBSYSTEM
"subsystem" FAILED. RETURN
Explanation CODES return_code/reason_code

Explanation
was not valid.
The IHSB2SQL routine failed to connect to the DB2
System action subsystem.
The LOCATE task fails to complete. Message Variables

subsystem
Operator response The DB2 subsystem name.
Notify the system programmer. return_code
The return code from the DB2 Call Attachment
Facility.
reason_code
Contact IBM Software Support. The reason code from the DB2 Call Attachment
IHS515E THE SECOND PARAMETER MUST Facility.
BE "SELECT".
System action
Explanation The LOCATE task fails to complete.
was not valid. Operator response
System action
The LOCATE task fails to complete. System programmer response
Be sure that the DB2 subsystem is active before
Operator response contacting your DB2 system administrator. If you
Notify the system programmer. continue to receive this message. Contact IBM
Software Support.
IHS518E SQL ERROR RETURNED
SQLCODE=return_code
A serious SQL error occurred when executing the Contact IBM Software Support.
LOCATE task.
IHS521E COLUMN TYPE IS NOT SMALLINT,
Message Variables INT, CHAR, VARCHR.
return_code
The SQL return code. Explanation
An incorrect SQL call has been attempted.
System action
The LOCATE task fails to complete. System action
Operator response
Contact IBM Software Support System programmer response
IHS519E SQL WARNING RETURNED Contact IBM Software Support.

SQLCODE=return_code IHS522E SQL DATA BUFFER OVERFLOW.
An SQL warning level error occurred when executing An SQL error occurred when executing the LOCATE
the LOCATE task. task.
Message Variables
System action
return_code
The SQL return code. The LOCATE task fails to complete.

The LOCATE task fails to complete. Notify the system programmer.

Notify the system programmer. Contact IBM Software Support.
IHS523E MSG DATA BUFFER OVERFLOW.
Contact IBM Software Support. Explanation
IHS520E TOO MANY COLUMNS An SQL error occurred when executing the LOCATE
REQUESTED. task.

The data returned from the SQL request exceeds the The LOCATE task fails to complete.
space available to hold it.
Operator response
System action
Operator response

IHS527E CALL TO DB2 DSNWLI FAILED. Explanation
DB2 RETURN CODES xxxxxxxx/ Along with the IBM Z NetView message automation
yyyyyyyy table, DB2 for z/OS instrumentation uses this message
to return data from the DISPLAY NUMBER OF
Explanation THREADS task.
The IHSB2IFI routine received a non-zero return code Message Variables
from DSNWLI.
nn
Message Variables Returned data field.
xxxxxxxx IHS532I NO TARGET NETVIEWS FOUND IN
Register 15 value after the DSNWLI call. THIS FOCAL POINT'S SPHERE OF
yyyyyyyy CONTROL.
Register 0 (zero) value after the DSNWLI call.
Explanation
System action No targets are currently defined for this IBM Z NetView
The current task fails to complete. focal point. Instrumentation will only be performed for
the DB2 subsystems that run on the system focal
Operator response point.
Contact IBM Software Support. System programmer response

IHS528E CALL TO DB2 IFI FAILED. DB2 The IBM Z NetView FOCALPT DISPSOC command
RETURN CODES xxxxxxxx/yyyyyyyy returned no target for the ALERT category. Confirm
that you have correctly defined all required targets to
Explanation the focal point.
The call to DSNWLI was successful, but non-zero IHS533W NO RESOURCES FOUND FOR DB2
return codes were returned from the DB2 subsystem ON domain
Instrumentation Facility Interface (IFI).
xxxxxxxx No databases, tablespaces, or indexes were found for
Return code from the DB2 IFI. the specified DB2 subsystem. This DB2 subsystem
might not currently be active.
yyyyyyyy
Reason code from the DB2 IFI. Message Variables
DB2 subsystem
System action The DB2 subsystem for which instrumentation is
The current task fails to complete. being performed.
domain
Operator response The NetView domain name associated with the
operating system on which this DB2 subsystem is
Notify the system programmer. running.

Contact IBM Software Support. Notify the system programmer.
IHS529I IDBACK=nn IDFORE=nn
CTHREAD=nn MAXDBAT=nn System programmer response
When the DB2 subsystem is active and no resources
are discovered, contact IBM Software Support.
IHS540E INPUT VALUES CANNOT BE Operator response
ENTERED FOR BOTH TABLESPACE Ensure that the option is either YES or NO. Then issue
AND INDEX. the task again with the correct option set.
Explanation IHS545I INSTANCE FILTERING FOR

database ALREADY state. NO
Both a tablespace name and an index name were ACTION TAKEN.
entered in the LOCATE task dialog box. One or the
other must be used.
Explanation
System action No action is taken as the database is already enabled

or disabled for instance filtering.
Message Variables
Operator response database
Database name.
Enter a tablespace name or an index name for the
LOCATE task. state
Enabled or Disabled.
IHS541E IHSB2REG FAILURE FOR
suborigin. RC=return code.
System action
Explanation No action taken as the database is already enabled or

disabled for instance filtering.
The heartbeat routine ended because a FATAL error
occurred for the Tivoli GEM Register Component API IHS546W GEMAPI GEMAPI FAILED WITH RC
GEMREG. RC FOR CID IN module.
PROCESSING CONTINUES.
Message Variables
suborigin Explanation
The suborigin name of the component being
A Tivoli GEM API call returned a non-fatal return code.
registered.
return code Message Variables
Return code from Tivoli GEM API GEMREG. GEMAPI
Name of the Tivoli GEM API which failed.
System action RC
Heartbeat routine ends. The return code.
CID
Operator response The component identifier.
Notify the system programmer. module
CLIST from which the failed Tivoli GEM API was
called.
Contact IBM Software Support. System action
IHS544I INCORRECT OPTION user option Processing continues.
FOR INSTANCE FILTERING. TRY
'YES' OR 'NO'. IHS547I INSTANCE FILTERING WILL BE
state FOR THIS DATABASE.
Explanation
Explanation
The user entered an incorrect value for an instance
filter. Instance filtering for this database will be enabled or
disabled.
Message Variables
Message Variables
user option
Parameter entered in the instance filter dialog. state
Enabled or Disabled.

IHS548I INSTANCE FILTERING WILL BE Operator response
state FOR ALL DATABASES Check the DB2 configuration file for correct subsystem
BELONGING TO THIS name entry.
SUBSYSTEM.
IHS551W DOMAIN domain WAS LISTED IN
Explanation THE GEM CONFIGURATION FILE
BUT IS NOT IN THIS NETVIEW'S
Instance filtering has been enabled or disabled for this SPHERE OF CONTROL.
DB2 subsystem.
state A user specified IBM Z NetView domain was found in
Enabled or Disabled. the configuration file but does not exist.
IHS549W DB2 RELEASE LEVEL COULD NOT Message Variables
BE DETERMINED FOR subsystem domain
Domain name entered in the DB2 configuration
Explanation file.
Unable to determine the DB2 release level.
System action
Message Variables
Processing continues. Any subsystems specified on
subsystem this domain will be ignored.
The current DB2 subsystem.
Operator response
System action
Check the DB2 configuration file for correct domain
Processing continues. name entry.
Operator response IHS552E THE INPUT VALUE FOR field MUST

BE NUMERIC.
Explanation
A type mismatch has occured for this field in the DB2
Contact IBM Software Support. configuration file.
IHS550W DB2 SUBSYSTEM subsystem WAS Message Variables
LISTED IN THE GEM
CONFIGURATION FILE. IT WAS field
NOT FOUND ON domain The field in the DB2 configuration file with the type
mismatch.
Explanation
System action
A user specified subsystem was found in the DB2
configuration file but did not exist on the IBM Z The task fails.
NetView domain.
Operator response
Message Variables
Reenter the data as a numeric field.
subsystem
DB2 subsystem entered in the DB2 configuration IHS553E MONITOR NAME monitor IS NOT
file. VALID.
domain
Domain name entered in the configuration file. Explanation
The GEM API GEMTHRSH call failed because of a
System action monitor name that was not valid.
Processing continues. The subsystem is ignored. Message Variables
monitor Explanation
The incorrect monitor name entered.
With the discovery type set to 'CONFIGURE' there are
no possible resources to instrument.
System action
Instrumentation can not continue.
Operator response
Edit the Tivoli GEM configuration file to specify at least
System programmer response one DB2 subsystem or set the discovery type to
Contact IBM Software Support. 'DYNAMIC' and issue INITAMI again.
IHS554E UNKNOWN MONITOR NAME IHS557E GEM CONFIGURATION FILE

monitor filename READ FAILED.
DISCOVERY TERMINATED.
Explanation
Explanation
The specified monitor name monitor is not known to
DB2 for z/OS instrumentation. Tivoli GEM was unable to read the DB2 configuration
file. Either the DB2 configuration file does not exist or
Message Variables there has been an I/O error in reading the file.
monitor Message Variables
The unknown monitor name entered.
filename
The name of the Tivoli GEM DB2 configuration file.
System action
Processing ends.
Operator response
Ensure that the name entered is a valid monitor name. Operator response
If it is a valid monitor name, contact your system
programmer. Processing ends. Ensure that the configuration file
exists.
IHS555I THIS COMMAND VALID ONLY FOR
DB2 VERSION 6.1. IHS558E GEM CONFIGURATION FILE
configuration filename COULD NOT
INCLUDE THE FILE filename
Explanation
User error. A task valid only for DB2 V6.1 was Explanation
performed on a non V6.1 DB2.
The configuration file has one or more %INCLUDE
statments specifying included files. The included file
System action
cannot be read.
The task fails and processing continues.
Message Variables
IHS556W GEM CONFIGURATION FILE configuration filename
CONTAINED NO DB2 The name of the Tivoli GEM DB2 configuration file.
SUBSYSTEMS AND DISCOVERY
WAS SET TO 'CONFIGURE'. filename
The name of the file that cannot be included.
System action

Ensure that the included file exists and is in the Processing continues. The entry is ignored.
NetView DSIAPRM data set concatenation.
Operator response
Edit the Tivoli GEM DB2 configuration file.
IHS562W VALUE FOR fieldname FIELD MUST
IHS559W SSNAME PARAMETER NOT FOUND BE NUMERIC. SET TO DEFAULT
IN GEM CONFIGURATION FILE VALUE value FOR
ENTRY. domain.subsystem
An user error occurred in defining the GEM DB2 A numeric parameter was specified as non-numeric.
configuration file as a SSNAME field was not found.
Message Variables
System action fieldname

Tivoli GEM DB2 configuration file field name with
Processing continues. The entry is ignored. non-numeric value specified.
value
Operator response Value entered.
Edit the Tivoli GEM DB2 configuration file. domain.subsystem
The current domain and subsystem name for
IHS560W DOMAIN PARAMETER NOT FOUND
fieldname.
IN GEM CONFIGURATION FILE
ENTRY.
System action
Explanation The field is set to a default value and processing
continues.
A user error occurred in defining the Tivoli GEM DB2
configuration file as the DOMAIN field was not found. IHS563W VALUE FOR fieldname FIELD
BEYOND MAX/MIN BOUNDS. SET
System action TO value FOR domain.subsystem
Processing continues. The entry is ignored.
Explanation
Operator response A value was specified for the field that was outside of
the minimum or maximum.
Edit the Tivoli GEM DB2 configuration file.
Message Variables
IHS561W UNRECOGNIZED PARAMETER
parm DEFINED FOR fieldname
domain.substem IN filename. parm Tivoli GEM DB2 configuration file field name for
IS INGNORED. which the incorrect value was set.
value
Explanation Value entered for field name.
An unrecognized parameter was found in the Tivoli domain.subsystem
GEM DB2 configuration file and will be ignored. The domain and subsystem name.
Message Variables
System action
parm
The field is given the default value and processing
Value entered in the field DOMAIN.
continues.
domain.substem
Domain and subsystem specified in the Tivoli GEM IHS564E INCORECT VALUE value SET FOR
DB2 configuration file. DISCOVER FIELD IN filename.
VALID VALUES ARE /
filename
The name of the Tivoli GEM DB2 configuration file.
CONFIGURE/OR/DYNAMIC. Message Variables
DISCOVERY TERMINATED.
monitor
The name of the monitor updated.
Explanation
IHS569I THIS COMMAND CANNOT BE
An incorrect value was specified for the Tivoli GEM ISSUED AS THE DDF HAS NOT
DB2 configuration file field DISCOVERY. BEEN STARTED.
Message Variables
Explanation
value
Value entered for DISCOVERY field in the Tivoli A task that required the distributed data facility (DDF)
GEM DB2 configuration file. to be started is failed.
filename
Name of the Tivoli GEM DB2 configuration file. Operator response
Start DDF and issue the task again.
System action
IHS570I INSTANCE FILTERING NOT
Processing ends. AVAILABLE FOR SUBSYSTEMS IN
EXCEPTION MODE.
Operator response
Correct the entry in the Tivoli GEM DB2 configuration Explanation
file and reissue INITAMI. Exception mode and instance filtering are mutually
IHS565I *** END OF DISPLAY FOR LOCATE exclusive.
***
Operator response
Explanation Edit the configuration file to change the exception
A trailer message issued from the LOCATE task to entry to NO.
delimit the display. IHS571I INCORRECT INPUT PARAMETER
IHS566I THE HEARTBEAT INTERVAL IS FOR value. ONLY 'FULL' OR
value 'EXCEPTION' ARE VALID.
Informational message. Incorrect value entered for SET DISCOVERY OPTION

task.
Message Variables
Message Variables
value
Time of the Heartbeat interval in hrs:min:sec. value
The value entered.
IHS567I THE STATUS MONITOR INTERVAL
IS value Operator response
Explanation Enter the correct value.
Informational message. IHS572I field name threshold - value 1.

value 2 messages per time
Message Variables interval.
value
Time of the monitor refresh rate in hrs:min:sec. Explanation
IHS568I monitor parameters successfully User defined value set for threshold parameters for
updated. every interval.
Message Variables
Explanation
field name
The Deadlock or Timeout threshold parameters have The parameter name.
been updated successfully.

value 1 IHS576I subsys WILL NOT BE
The number of fieldname. REGISTERED, AS IT IS RUNNING
value 2 A LEVEL OF DB2 NOT SUPPORTED
The interval time. BY THIS PRODUCT.
IHS573I The time interval is value seconds. Explanation
Explanation An unsupported level of DB2 was discovered.
The specified threshold interval value. Message Variables
Message Variables subsys

Name of the unsupported DB2 sub-system.
value
Interval time in seconds. Operator response
IHS574I Command not If you want to run this task, follow these steps:
issued.domain.subsys is down.
1
Remove the subsys from the DB2 configuration
Explanation
file.
Because the specified sub-system is in a down state, 2
the issued task cannot be run. Refresh the configuration file.
Message Variables
domain.subsys
The name of the sub-system that is in the down Ensure the unsupported version of DB2 is required. If
state. it is not required, shut down the DB2 system with the
unsupported level.
Operator response
IHS577E KEYWORD field NOT FOUND IN
If you want to run the task, do the following: THE DB2 CONFIGURATION FILE.
THIS DISCOVERY TERMINATED.
1
Start the specified sub-system.
Explanation
2
Issue the task again. A mandatory field field in the DB2 configuration file
was not located. Instrumention remains the same.
IHS575I This task only available when
discovery is DYNAMIC. Update Message Variables
config file and issue Refresh field
Config task. The field not found in the DB2 configuration file.

The issued task can only be run when the DISCOVERY If you want to run this task, follow these steps:
type is DYNAMIC.
1
Edit the DB2 configuration file.
Operator response
2
If you want to run this task, follow these steps: Ensure the flagged field is present in the DB2
1 configuration file.
Edit the DB2 configuration file, changing the 3
DISCOVERY option to DYNAMIC. Refresh the configuration file.
2
IHS578W INCORRECT VALUE
Refresh the configuration file.
DISCOVERY=value1 IN filename.
3 DISCOVERY CONTINUES USING
Issue the task again. PREVIOUS VALUE OF
DISCOVERY=value2.
Explanation msgnum
The number of the missing message.
A value other than that permitted was entered in the
SET DISCOVERY task option. Discovery continues with
previous value set. System action
Message Variables System action is unpredictable.
value1
Operator response
Incorrect value entered for field.
filename Notify the system programmer.
Name of the DB2 configuration file.
value2
Value which was set previously. Contact IBM Software Support.
IHS0001E errorcode parm1 parm2 parm3
Operator response
If you want to run this task, follow these steps: Explanation
1 An error occurred during initialization before the
Edit the DB2 configuration file. console message file can be correctly loaded. The
2 error code and the parameters indicate the cause of
Ensure the permissable value is specified. the error, which is described below.
3 Message Variables
Refresh the configuration file.
errorcode
IHS579W value1 IS NOT VALID. 'YES' OR One of the following error codes was returned:
'NO' ARE VALID. DEFAULT SET TO 1
'YES'. An error occured while attempting to install an
error handler. parm1 can be SIGTERM,
Explanation SIGINT, or SIGPIPE.
Value other than that permissable was specified for 3
DB2 configuration field. Value is set to default value. An error occured while attempting to open the
Discovery continues. console message file. parm1 contains the
name of the message file.
Message Variables
4
value1 A message in the message file does not have a
Incorrect value entered for field. valid format. parm1 contains the name of the
message file. parm2 contains the line number
Operator response in the message file of the message in error.
If you want to run this task, follow these steps: 5
The message number was defined earlier in
1
the file. parm1 contains the name of the
Edit the DB2 configuration file.
message file. parm2 contains the line number
2 in the message file of the message in error.
Ensure the permissable value is specified.
6
3 The message was longer than the valid
Refresh the configuration file. maximum length, which is 1024 characters.
parm1 contains the name of the message file.
IHS0000I Message msgnum is not in the
parm2 contains the line number in the
message file IHSAMSG1.
message file of the message in error.
Explanation 7
The standard output stream file for the task
An Event/Automation Service module issued an IHS cannot be opened. parm1 contains the name of
prefix message that was not defined in the message the standard output stream that cannot be
definition module. opened. parm2 contains an error number.
Message Variables

System action IHS0009I EVENT ADAPTER SDUMP FOR
TASK task COMPLETED, RETURN
The Event/Automation Service ends.
CODE = X'retcode', REASON CODE
= X'rescode'
Operator response
An Event/Automation Service request for SVC dump,
System programmer response using the SDUMP macro, completed on the indicated
If you receive error code 1, contact IBM Software task with the return code and reason code shown.
Support. Message Variables
If you receive error code 3, ensure that the console task
messages file is in the correct data set or HFS The name of the Event/Automation Service task
directory, and is named correctly when starting the whose abend is the reason for the SVC dump
Event/Automation Service. request.
If you receive error codes 4, 5, and 6, ensure you are retcode
using the installed copy of the console messages file. The return code from the SDUMP macro.
If so, contact IBM Software Support.
rescode
For error code 7, ensure that the data set definition The reason code from the SDUMP macro.
statements for IHSASTD, IHSBSTD, IHSCSTD,
IHSESTD, IHSMSTD, IHSNSTD and IHSTSTD files exist System action
in your startup procedure (these must not be modified
from their settings in the installation sample). If SDUMP succeeds, the SVC dump is captured and is
expected to be written to a dump data set.
IHS0008I EVENT ADAPTER IS DUMPING
FOR TASK task, COMPLETION Operator response
CODE = X'hhhhhh'
Explanation
An Event/Automation Service task has ended
abnormally and an SVC dump is being requested using Investigate the reason for the abend that caused the
the SDUMP macro. SVC dump.
Message Variables IHS0010E adapter: Line line could not be
retrieved from FMT file file.
task
The name of the Event/Automation Service task
where the abend occurred. Explanation
hhhhhh The next line from the specified format (FMT) file
The completion code, in hexadecimal. Nonzero cannot be retrieved because of a file I/O error. The file
values in the first three digits indicate a system I/O error is provided in the Event/Automation Service
abend, and nonzero values in the last three digits log.
indicate a user abend. Message Variables
System action adapter

The event adapter designator.
An SVC dump is requested and a message with the
line
results follow.
The file line number that was to be retrieved.
file
Operator response
The name of the format file.
System action
The adapter task ends.
Investigate the reason for the abend.
Notify the system programmer. The adapter task ends.

Find message IHS0010E in the Event/Automation Notify the system programmer.
Service log. Message IHS0114E will precede this
message in the log. IHS0114E contains specific System programmer response
information about the type of I/O error that occurred.
If the problem cannot be resolved from this Find message IHS0012A in the Event/Automation
information, notify IBM Software Support. Service log. Message IHS0015A will follow this
message in the log. IHS0015A contains the line
IHS0011A adapter: FMT file file could not be number and position of the beginning of the comment.
opened. Inspect the format file and correct the problem.
IHS0013A adapter: Incomplete string in FMT
Explanation
file file, line line.
The attempt to open the specified format (FMT) file
received a file I/O error. The file I/O error is provided in Explanation
the Event/Automation Service log.
A string map slot value was not closed before the end
Message Variables of the current line in the specified format file.
adapter Message Variables
adapter
file The event adapter designator.
file
System action
line
The adapter task ends. The line in the format file with the incomplete
string.
Operator response
The message adapter task ends.
Find message IHS0011A in the Event/Automation Operator response
Service log. Message IHS0114E will precede this Notify the system programmer.
message in the log. IHS0114E contains specific
information on the type of file I/O error that occurred.
If the problem cannot be resolved from this
information, notify IBM Software Support. Find message IHS0013A in the Event/Automation
Service log. Message IHS0015A will follow this
IHS0012A adapter: Incomplete comment in
FMT file file.
number and position of the beginning of the string.
Inspect the format file and correct the problem.
Explanation
IHS0014A adapter: Incorrect map state
A comment was not closed before the specified format token in FMT file file.
file completed.
adapter A format specification map statement in the file format
The event adapter designator. file is not valid.
file Message Variables
adapter

file file
The name of the format file. The name of the format file.

The adapter task ends. The message adapter task ends.


Find message IHS0014A in the Event/Automation Find message IHS0016A in the Event/Automation
Service log. Message IHS0015A will follow this Service log. Message IHS0015A will follow this
message in the log. IHS0015A contains the line message in the log. IHS0015A contains the line
number and position of the map statement error. number and position of the map statement error. It is
Inspect the format file and correct the problem. possible that either the FOLLOWS or base class name
was misspelled, or the base class was left out of the
IHS0015A ==>line number line, character format file.
position position.
IHS0017A adapter: Incorrect FORMAT line
Explanation token in FMT file file.
This message will be issued only to the Event/

Explanation
Automation Service log. It indicates the line number
and position on the line of the syntax error indicated A syntax error was encountered in a format
by the previous message in the log. specification between the FORMAT keyword and the
beginning of the format string for the specified format
Message Variables
file.
line
Message Variables
The line number of the format file.
position adapter
The position on the line of the format file. The event adapter designator.
file
System action The name of the format file.

System action
Operator response The adapter task ends.

Operator response
Use the information in this message and the preceding

message to correct the problem in the format file.
Find message IHS0017A in the Event/Automation
IHS0016A adapter: FOLLOWS event class not Service log. Message IHS0015A will follow this
defined in FMT file file. message in the log. IHS0015A contains the line
number and position of the FORMAT line error. Inspect
Explanation the format file and correct the error.
The event class specified on the FOLLOWS statement IHS0018A adapter: Incorrect format begin
in the specified format file was not previously defined. state token in FMT file file.
Message Variables
adapter
A syntax error was encountered in a format file The number of variables declared in the format string
between the end of one format specification and the portion of the format specification exceeds the
beginning of another. number of format string variable components (those
that are %s, %s*, and %s+).
Message Variables
Message Variables
adapter
The event adapter designator. adapter
file The event adapter designator.
The name of the format file. variable
The variable that is out of range.
System action maxvar
The maximum number of variables allowed in this
format specification.
Operator response
System action

Operator response
Find message IHS0018A in the Event/Automation
Service log. Message IHS0015A will follow this
number and position of the format file error. Inspect System programmer response
the format file and correct the error. Change the variable substitution to correspond to a
IHS0019E adapter: Processing for this event number within the allowable range of format string
has prematurely terminated. variables.
IHS0021A adapter: Maximum number of
Explanation variable mappings (maxvar)
An error occurred that caused the processing of the exceeded in FMT file file.
current event to end. Additional log or console
messages will be issued to help determine the cause Explanation
of the error. The number of variables declared in the format string
Message Variables portion of the format specification exceeds the
maximum number allowed.
adapter
The event adapter designator. Message Variables
adapter
System action The event adapter designator.
The current event is discarded. maxvar
The maximum number of variables allowed in a
Operator response format specification.
file

System action
Find message IHS0019E in the Event/Automation
Service log. Other messages will follow this message
to determine the cause of the error.
Operator response
IHS0020A adapter: Slot map variable
$variable out of range. It must be Notify the system programmer.
between $1 and $maxvar

Redefine the format specifications so that the A request failed with the indicated error number.
maximum number of variable substitutions is not
Message Variables
exceeded.
service
IHS0022E Unable to open DD member for The name of the service
initialization.
request
The request that failed
Explanation
number
The member specified as the event receiver The error number associated with the failure
configuration file cannot be opened.
member If the message was issued for a socket used for
The name of the file being used to provide the communication in an IP network, the socket is closed.
configuration parameters for an Event/Automation Processing continues.
Service task
Operator response
System action
Initialization of the task fails.
Operator response
Perform problem determination procedures. If the
Notify the system programmer. error cannot be attributed to a specific user action,
IHS0025I service: Negative response limit
Verify that the DD member defined by the user on the for an event exceeded. The event
start command of the default initialization member will be discarded
(IHSAINIT) is present. Correct the error and reinitialize
the event receiver task. Explanation
IHS0023E Incorrect data received by event For an event that was sent (and resent) by a confirmed
receiver. Data will be discarded. adapter, the number of negative responses received
exceeded the BufEvtNegRespLimit value. The event
Explanation was then discarded.
An event was received that cannot be properly parsed. Message Variables

service
System action The confirmed adapter that detected the
condition. The possible values are:
Processing will continue. The current event data will
be discarded. • Confirmed Message Adapter
• Confirmed Alert Adapter
Operator response
The confirmed adapter logs the discarded event to its
System programmer response log or trace file. Processing continues.
Check the Event/Automation Service log for related
messages. Verify that other events are properly Operator response
received and processed. If the problem persists, notify Notify the system programmer.
IHS0024E service: request failed, errno System programmer response
number
Perform problem determination procedures. Check for
log information at the event server or servers to
determine the reason for the negative responses. If System programmer response
the error is not temporary or you cannot correct it,
messages, including IHS0114E. Verify that the TCP/IP
IHS0026I service: Connection with server at stack is properly configured and active. If the problem
IP address ipaddress closed persists, notify IBM Software Support.
IHS0028E Incorrectly delimited value in
Explanation event.
The identified adapter discovered that the event server
closed the connection that was initiated by that Explanation
adapter.
The event receiver cannot parse the event.
Message Variables
service System action
The adapter that detected the loss of the Processing continues. The event is discarded.
connection
ipaddress Operator response
The IP address of the event server with which the
connection was lost Notify the system programmer.
For a confirmed adapter, the loss of connection Check the Event/Automation Service log to find the
occurred while waiting for the event server to reply to event that is not valid. If the event is correct in the log,
an event that was sent by that adapter. The confirmed notify IBM Software Support. Otherwise, contact the
adapter treats the condition as a failed send and service organization for the sender of the event.
enters retry processing. Retry processing might IHS0029I service: The current
include sending the event to the next server in the ServerLocation is location location,
ServerLocation list (if any) and caching the event (if the address address, port port.
confirmed adapter was configured with
BufferEvent=yes).
Explanation
Operator response A connection is made to the server for the given

ServerLocation. This message is issued only when an
Notify the system programmer. event is sent to a server that is not the same as the
server used for the previous event.
Message Variables
Perform problem determination procedures. Check the
service
event server log information to determine the status of
The service that is issuing this message.
the connection. If the error is not due to network
failure, contact IBM Software Support. location
The location in the ServerLocation list. The first
IHS0027E Unable to receive data from server in the list is indexed as location 1.
socket.
address
The IP address of the server.
Explanation
port
The event receiver task was unsuccessful in The IP port of the server.
attempting to receive data from a socket.
System action
System action
Processing continues. If a partial event was received, it
is discarded. IHS0030W Unable to allocate a new socket.
The retry limit is exceeded.
Operator response

A remote program was unsuccessful in attempting to Check the Event/Automation Service log for related
connect to the Event Receiver task. messages, including IHS0114E. Verify that TCP/IP is
properly configured and active. If the problem
System action persists, notify IBM Software Support.
Processing continues; however, the program IHS0033E Retry limit exceeded on socket
attempting to connect cannot send data to the event close.
receiver task.
Explanation
Operator response The event receiver task was unsuccessful in
Notify the system programmer. attempting to close a socket.
Check the Event/Automation Service log for related Processing continues; however, the socket will remain
messages, including IHS0114E. Verify that TCP/IP is open.
persists, notify IBM Software Support. Operator response
IHS0031E Unable to allocate a new socket. Notify the system programmer.

A remote program was unsuccessful in attempting to Check the Event/Automation Service log for related
connect to the Event Receiver task. messages, including IHS0114E. Verify that TCP/IP is
System action persists, notify IBM Software Support.
The event receiver task ends. IHS0034E Unable to close socket.
Notify the system programmer. The event receiver task, the confirmed message
adapter, or the confirmed alert adapter was
unsuccessful in attempting to close a socket.
Check the Event/Automation Service log for related System action
messages, including IHS0114E. Verify that TCP/IP is
properly configured and active. If the problem Processing continues; however, the socket will remain
persists, notify IBM Software Support. open.
IHS0032E Unable to make socket non-

Operator response
blocking.
Explanation
A service was not able to make (subsequent) requests
on a socket non-blocking. Check the Event/Automation Service log for related
System action properly configured and active. If the problem
persists, notify IBM Software Support.
The event receiver task ends.
IHS0035E If you do not want to use
Operator response portmapper you must specify an
initial port for the event receiver.
Explanation Trap data that was received by the trap-to-alert
conversion task could not be converted from ASCII to
There is an inconsistency in the statements in the
EBCDIC.
configuration file for the event receiver. One of the
statements, UsePortmapper=no or PortNumber=0,
must be changed. System action
Processing continues; however, the event or trap is
System action discarded.
Initialization of the event receiver task fails.
Operator response
System programmer response Check the Event/Automation Service log for related
messages, including IHS0114E. If the problem
If you want to use portmapper, code
UsePortmapper=yes. If you do not want to use
portmapper, code a valid number on the PortNumber IHS0038E The event received was
statement. The default configuration file is IHSAECFG. incomplete or not valid.
IHS0036E Setup for ASCII to EBCDIC
conversion failed. Explanation
The event receiver task received data that was not
Explanation recognized as an event.
The event cannot be processed because a call to
'setlocale' failed. If the trap-to-alert conversion task System action
issued the message, an SNMP trap cannot be Processing continues; however, the data will be
processed because a call to 'setlocale' failed. discarded.

The task that issued the message ends and the Event Notify the system programmer.
Integration Facility (EIF) event or SNMP trap is
discarded.
Operator response Check the Event/Automation Service log for related

messages. If the problem persists, notify IBM
Notify the system programmer. Software Support.
IHS0039E Unsuccessful attempt to wait for
socket activity.
messages. Also, check other system logs for TCP/IP- Explanation
related problems. Verify that TCP/IP is properly
configured and active. If the problem persists, notify A call to 'selectex' was unsuccessful.
System action
IHS0037E ASCII to EBCDIC conversion
failed. The task that is experiencing the problem ends. The
task might be the event receiver or the trap-to-alert
Explanation conversion task.
Event data that was received by the event receiver,

Operator response
confirmed message adapter, or confirmed alert
adapter could not be converted from ASCII to EBCDIC. Notify the system programmer.

Check the Event/Automation Service log for related Processing continues; however, the program
messages, including IHS0114E. Verify that TCP/IP is attempting to connect will not be able to send data to
properly configured and active. If the problem the event receiver task.
IHS0040E TCP/IP may not be active. Operator response
Explanation
The TCP/IP program is not active. System programmer response
Try using a connection-less transport for programs
System action attempting to connect to the event receiver task. If the
problem persists, notify IBM Software Support.
Processing continues; however, the Event/Automation
Service will not be able to send or receive events. IHS0043W The data received is not valid.
numbytes bytes discarded.
Operator response
Explanation
The event receiver or the trap-to-alert conversion task
System programmer response that was not recognized.
Start the TCP/IP program. Message Variables
IHS0041W Unable to make socket non- numbytes

blocking. Retry limit exceeded. The number of bytes discarded.
A service was not able to make (subsequent) requests Processing continues; however, the data will be
on a socket non-blocking. discarded.
Processing continues; however, the program Notify the system programmer.

attempting to connect will not be able to send data to
the event receiver task. System programmer response
Operator response messages, including a hexadecimal dump of the
Notify the system programmer. discarded data. If the problem persists, notify IBM
Software Support.
System programmer response IHS0044W Unsuccessful call to pmap_unset.
messages, including IHS0114E. Verify that TCP/IP is Explanation
properly configured and active. If the problem During the termination of the event receiver task, an
persists, notify IBM Software Support. unsuccessful attempt was made to unregister with the
IHS0042E Maximum connections, number, portmapper.
exceeded.
System action
Explanation event receiver task termination will continue.
A remote program was unsuccessful in attempting to However, the portmapper registration might not have
connect to the Event Receiver task. been removed. The next time you start the Event
Receiver, you might get message IHS0052W indicating
Message Variables that the registration has been replaced.
number
The maximum number of connections allowed.

Verify that TCP/IP is properly configured and active. Check the Event/Automation Service log for related
Verify that the portmapper is active. If the problem messages, including IHS0114E. Verify that TCP/IP is
persists, notify IBM Software Support. properly configured and active. If the problem
IHS0045E Unable to obtain a socket.
IHS0048E Unable to determine port number.
Explanation
Explanation
The event receiver task was unable to initialize.
System action
System action
Operator response
Operator response
messages, including IHS0114E. Verify that TCP/IP is Check the Event/Automation Service log for related
properly configured and active. If the problem messages, including IHS0114E. Verify that TCP/IP is
persists, notify IBM Software Support. properly configured and active. If the problem
IHS0046E Unable to bind a socket to a port.
IHS0049E Unsuccessful call to pmap_set.
Explanation
Explanation
System action
System action
Operator response
Operator response
messages, including IHS0114E. Verify that TCP/IP is Verify that TCP/IP is properly configured and active.
properly configured and active. If the problem Verify that the portmapper is active. If the problem
persists, notify IBM Software Support. persists, notify IBM Software Support.
IHS0047E Unable to set up socket queue. IHS0050E For Tivoli Customer Support use
only: servicedata
Explanation
Explanation
This message is written only to the Event/Automation
System action Service network log and is intended for IBM Software
Support to use in debugging internal Event/
The event receiver task ends. Automation Service errors. This message accompanies
message IHS0081E, which is displayed at the console.

servicedata If the Event/Automation Service was previously
The data to assist IBM Software Support in cancelled, you might be able to ignore this message. If
problem determination. you are running multiple copies of the Event/
Automation Service, ensure that only one copy is
System action started with UsePortmapper=yes specified in the
event receiver configuration file. The default
Processing continues. configuration file is IHSAECFG.
IHS0053E Retry limit exceeded on receive
Operator response
from socket.
Explanation
The event receiver task was unsuccessful in
Notify IBM Software Support. Depending on the nature attempting to receive data from a socket.
of the internal error, you might need to recycle either
the entire Event/Automation Service or one of its System action
tasks.
Processing continues. If a partial event was received, it
IHS0051E The alert received is too large to will be discarded.
be processed.
Operator response
Explanation
The event receiver task received an alert that was too
large to be processed.
System action Check the Event/Automation Service log for related

Processing continues; however, the alert will be properly configured and active. If the problem
discarded. persists, notify IBM Software Support.
IHS0054E Detected incorrect data number
Operator response
bytes into 'string'.
Explanation
The event receiver is unable to parse the event.
Message Variables
messages, including a hex dump of the discarded
alert. If the problem persists, notify IBM Software number
Support. The number of bytes into the value where a
parsing error was detected.
IHS0052W Event Receiver portmapper
registration will be replaced. string
The value portion of a 'keyword=value' slot in an
event.
Explanation
The event receiver task was already registered with System action
the portmapper.
Processing continues. The event will be discarded.
System action
Operator response
Portmapper registration is replaced and processing
continues. Notify the system programmer.
Notify the system programmer. Check the Event/Automation Service log to find the
event that is not valid. If the event is correct in the log,
notify IBM Software Support. Otherwise, contact the cannot accept new connections to receive events.
service organization for the sender of the event. Using a connectionless transport for programs that are
attempting to connect to the event receiver task might
IHS0055E Unable to open member for
free up unused connections.
initialization.
IHS0057I Unable to set the socket option
Explanation SO_KEEPALIVE, Error code is
errcode.
The member specified as the initialization file on the
start command cannot be opened.
Explanation
Message Variables
The event receiver task encountered an error when
member setting the setsockopt SO_KEEPALIVE keepalive
The name of the file being used by the Event/ socket option. The socket might be lost if the
Automation Service to provide initialization connection is ended before the socket can be shut
parameters. down and closed.
Message Variables
System action
errcode
Initialization of the Event/Automation Service fails. The error code for the setsockopt failure.


Verify that the DD member defined by the user on the Notify the system programmer.
start command or the default initialization member
IHSAINIT is present. Correct the error and reinitialize
the Event/Automation Service.
IHS0056W number1 of number2 connections messages, including IHS0114E. Verify that TCP/IP is
are already being used. properly configured and active. If the problem
Explanation
IHS0058E The PPI receiver ID receiverid is
number1 out of a maximum of number2 connections not valid.
are already in use.
number1 The receiverid specified is not a valid value. The
The number of active connections. receiverid must be 1–8 alphanumeric characters.
number2 Message Variables
The maximum number of connections allowed by
the E/AS event receiver task. receiverid
The program-to-program interface receiver ID for
IHSAEVNT.
System action
Processing continues. This is a warning message only. System action
Initialization of the Event/Automation Service fails.
Operator response
If this message is issued repeatedly in a short period Operator response
of time, notify the system programmer.
Notify the system programmer that an incorrect value
was specified for the PPI receiver ID in the Event/
System programmer response Automation Service initialization file.
When the maximum number of connections is reached
(IHS0042E is issued), the E/AS event receiver task

System programmer response MESSAGEC
The confirmed message adapter
Determine the error with the specified PPI receiver ID
in the initialization file and correct it. Reinitialize the TRAPALRT
Event/Automation Service. The trap-to-alert service
IHS0073I Current TRACE settings: level

The tracing level, which is one of the following:
Explanation OFF
No tracing
This is part of a multiline display generated in
response to a TRACE command you issued without LOW
parameters. This message is followed by IHS0076I. Low tracing level
NORMAL
IHS0075I Event/Automation service started. Normal tracing level
Subtask initialization is in
progress for task VERBOSE
Full tracing
Explanation iptrace
Whether tracing of IP connection data is enabled,
The Event/Automation Service CONTROL task has which is one of the following:
completed its initialization, and all tasks that are to be
started have been attached. OFF
No tracing
Message Variables
ON
task Tracing is enabled
IHS0079I GTF specified for output, but the
GTF is not active.
System action
Initialization proceeds for the tasks. Explanation
IHS0076I TASK=task LEVEL=level IP=iptrace The user specified a value of GTF for OUTPUT on the
TRACE command, or for OUTPUT in IHSAINIT.
Explanation However, GTF has not been started.
This is part of a multiline display generated in
response to a TRACE command you issued without System action
parameters. This message shows the status of tracing Trace output will be written to the system audit log.
for each Event/Automation Service task.
task Start GTF or issue the TRACE command with
The identifier of the Event/Automation Service OUTPUT=SYSOUT.
task. The task can be one of the following:
IHS0080E Recording to GTF failed with
ALERTA return code retcode.
The alert adapter
ALERTC Explanation
The confirmed alert adapter
The user was writing output to GTF, but GTF has been
ALRTTRAP stopped.
The alert-to-trap service
Message Variables
CONTROL
The main control task retcode
The return code from the MVS GTRACE macro.
EVENTRCV
The event adapter
MESSAGEA
The message adapter
System action the NetView CLISTs CNMEALUS and CNMEMSUS for
examples of Name/Value pair bindings.
Trace data is no longer being recorded to GTF.
Messages that are not from the console are being Message Variables
routed to the system audit log.
adapter
The adapter that detected the error.
Operator response
Restart GTF or issue the TRACE command with System action
OUTPUT=SYSOUT.
Processing continues with the next Name/Value pair.

Operator response
If the return code is other than 4 or 24, see the
GTRACE macro in z/OS MVS Authorized Assembler
Macros and take appropriate action. Contact IBM
Software Support if necessary. System programmer response
IHS0081E Event Service encountered an Find message IHS0082E in the Event/Automation

internal error in task taskname. Service network log. Following this message is a hex
Unexpected results may occur as dump that displays the incorrect Name/Value pair. The
processing continues. first two bytes of the dump contain the length of the
name (including the length bytes), which is 0x0002
because the name is null. The next two bytes contain
Explanation the length of the value, followed by the value. Inspect
An Event/Automation Service component encountered this data to determine the source of the incorrect
an internal error. This message is accompanied by one Name/Value pair and correct it.
or more IHS0050E messages in the Event/Automation
IHS0083E adapter: Encountered a Name in a
Service network log. Save the log entries to assist IBM
Name/Value pair that contains
Software Support in debugging internal errors.
only spaces. The Name/Value pair
Message Variables is ignored.
taskname
The data to assist IBM Software Support in Explanation
problem determination. The name in a Name/Value pair binding contains only
spaces. Name/Value pair names can be 1–31
System action characters in length and begin with an alphabetic
character. See the NetView sample CNMSIHSA and
Event/Automation Service processing continues, but
the NetView CLISTs CNMEALUS and CNMEMSUS for
unexpected results can occur.
Notify the system programmer. adapter

System action
Notify IBM Software Support. Depending on the nature
of the internal error, you might need to recycle the Processing continues with the next Name/Value pair.
IHSAEVNT procedure.
Operator response
IHS0082E adapter: Encountered a null Name
in a Name/Value pair. Name/Value Notify the system programmer.
pair is ignored.
Explanation Find message IHS0083E in the Event/Automation
The name in a Name/Value pair binding has a null Service network log. Following this message is a hex
name (zero length). Name/Value pair names can be 1– dump that displays the incorrect Name/Value pair. The
31 characters in length and begin with an alphabetic first two bytes of the dump contain the length of the
character. See the NetView sample CNMSIHSA and name (including the length bytes), followed by the

name. The next two bytes contain the length of the System programmer response
value, followed by the value. Inspect this data to
determine the source of the incorrect Name/Value pair
messages, including a hex dump of the discarded
and correct it.
alert. If the problem persists, notify IBM Software
IHS0084E adapter: Encountered a Name in a Support.
Name/Value pair that contains
IHS0086A Incorrect startup procedure
leading spaces. The Name/Value
parameter 'parameter'.
pair is ignored.
Explanation
Explanation
One of the Event/Automation Service initialization
The name in a Name/Value pair binding contains
parameters provided by the startup procedure is in
leading spaces. Name/Value pair names can be 1–31
error.
characters in length and begin with an alphabetic
character. See the NetView sample CNMSIHSA and Message Variables
the NetView CLISTs CNMEALUS and CNMEMSUS for
parameter
The parameter and its value.
Message Variables
adapter System action
The adapter that detected the error. The Event/Automation Service program ends.

Processing continues with the next Name/Value pair. If you provided a parameter override value to the
Event/Automation Service startup procedure, the
Operator response provided value is in error. Correct the value and restart
the procedure.

If you have modified the default Event/Automation
Service startup procedure, ensure that the parameters
Service network log. Following this message is a hex
passed to the Event/Automation Service entry point
dump that displays the incorrect Name/Value pair. The
module are correct. A parameter keyword that is not
first two bytes of the dump contain the length of the
recognized by the Event/Automation Service program
name (including the length bytes), followed by the
or a default value that is not valid for one of these
name. The next two bytes contain the length of the
parameters will cause this error. Correct the error and
value, followed by the value. Inspect this data to
restart the procedure.
determine the source of the incorrect Name/Value pair
and correct it. IHS0087A PPI receiver ID ppi-id is already in
use.
IHS0085E The alert received has an
improperly formed header.
Explanation
Explanation The PPI receiver ID that the Event/Automation Service
program uses to register with the NetView program-
The event receiver task received an alert with an
to-program interface is already in use.
improperly formed header.
Message Variables
System action ppi-id
Processing continues; however, the alert will be The PPI identifier for the Event/Automation Service
discarded. program.
Notify the system programmer. The Event/Automation Service program ends.
Operator response ppi-id
The PPI mailbox identifier that receives the
Another program is registered to the PPI with this
message.
identifier. If you are starting more than one Event/
Automation Service program, ensure that you have retcode
provided different PPI identifiers for each. Use a The SendBuffer function return code. The possible
different PPI identifier for the current invocation of the return values are:
Event/Automation Service program. 1
This error will result if you are starting more than one The PPI is temporarily unavailable. This type of
copy of the Event/Automation Service program and problem might resolve itself or require
using the default PPI identifier for both. intervention by the operator (for example, the
NetView subsystem might be unavailable).
The PPI is permanently unavailable. This is
If you have modified the default Event/Automation usually the result of an error that should not
Service startup procedure and provided a PPI have occurred.
identifier default within the procedure, ensure that it
does not conflict with existing users of the PPI. 3
Data was not provided. This is an error that
IHS0088A PPI inaccessible; timeout of time should not occur.
seconds in progress. 4
A incorrect input parameter was passed to a
Explanation PPI service routine. This is an error that should
The PPI or the NetView subsystem is unavailable. not occur.
After the specified timeout, an attempt to reconnect to 5
the PPI will occur. This timeout will continue The PPI interface is being recycled by the
indefinitely until the PPI becomes available or the Event/Automation Service program. The
procedure is ended. reason for the PPI interface being recycled has
been given in a previous error message.
Message Variables
time System action
The PPI timeout value.
The Event/Automation Service program will discard
the data and recycle the PPI.
System action
The Event/Automation Service program will ignore all Operator response
data until the PPI becomes available.
Operator response
Ensure the NetView subsystem interface is active and
the program-to-program interface option is enabled. If
this was not the source of the problem, notify IBM
Ensure the NetView subsystem interface is active and Software Support.
the program-to-program interface option is enabled.
IHS0090A Receive from PPI receiver ppi-id
IHS0089A Send to PPI receiver ppi-id failed failed with return code retcode.
with return code retcode.
Explanation
Explanation
The attempt to receive data from the PPI mailbox
The attempt to send data to the PPI receiver was identifier was unsuccessful. The return code indicates
unsuccessful. The return code indicates the possible the possible causes.
causes. The data is discarded in all cases.
Message Variables
Message Variables
ppi-id
The PPI mailbox receiver identifier.

retcode maxeventlength
The RecvBuffer function return code. The possible The maximum length allowed for an event. The
return codes are: default value is 4096. It can be overridden with the
1 EventMaxSize keyword in the adapter
The PPI is temporarily unavailable. This type of configuration file.
problem might resolve itself or require
intervention by the operator (for example, the System action
NetView subsystem might be unavailable). Processing continues.
2
The PPI is permanently unavailable. This is Operator response
usually the result of an error that should not
have occurred. Notify the system programmer.
3
Data was not provided. This is an error that System programmer response
should not occur. Find message IHS0091E in the Event/Automation
5 Service network log. The constructed event is
The PPI interface is being recycled by the displayed following this message. Inspect the event
Event/Automation Service program. The and the EventMaxSize keyword in the configuration
reason for the PPI interface being recycled has file. Then, either change the appropriate files (for
been given in a previous error message. example, CDS and FMT) to build a shorter event, or
specify a larger EventMaxSize in the configuration file.
System action IHS0092E adapter: EIF function eif_function
For return codes 3 and 5, processing continues. For failed. The event cannot be sent to
the other return codes, an attempt to reconnect to the the event server.
PPI interface will be made after a timeout.
Explanation
Operator response The adapter was in the process of constructing an
Notify the system programmer. event to send to the event server. The adapter invoked
eif_function as part of this processing and the function
failed. The event was not sent to the event server.
Message Variables
Ensure the NetView subsystem interface is active and
the program-to-program interface option is enabled. If adapter
this was not the source of the problem, notify IBM The adapter that detected the error.
Software Support. eif_function
IHS0091E adapter: The event length of The EIF function that failed.
eventlength exceeds the max
length of maxeventlength. The System action
event cannot be sent to the event Processing continues.
server.
Operator response
Explanation
The adapter was constructing an event to send to the
event server, and the length exceeds the maximum
allowable length of maxeventlength. The event was not System programmer response
sent to the event server. Find message IHS0092E in the Event/Automation
Message Variables Service network log. Other messages related to this
same error will be near this message in the log. These
adapter messages contain information that can help you
The adapter that detected the error. identify the problem.
eventlength IHS0094E service: Initialization failed. The
The length specified for an event.
configuration file is configfile.
Explanation messages contain information that can help you
identify the problem. Correct the incorrect statements
The initialization of the service failed because of an
and recycle the IHSAEVNT procedure.
incorrect or missing statement in the service
configuration file. Note:
Message Variables The file name indicated on message IHS0096E is
always the first file that was processed. Included file
service
names (that is, files that might be included by using a
The name of the service.
$INCLUDE statement) are not used on message
configfile IHS0096E.
The name of the configuration file.
IHS0097E adapter: Encountered a Name in a
Name/Value pair that has a length
System action
that exceeds maxlength. It is
The service ends. truncated.

Notify the system programmer. The adapter encountered an error when processing an
event that contains an appended Name/Value pair.
System programmer response The length of the name exceeds the maximum
allowable length of maxlength. The name is truncated
Additional information appears in the Event/ to maxlength characters and processing for the event
Automation Service output log that describes the continues.
problem. Inspect the configuration file and correct the
error. Restart the service. Message Variables
IHS0096E adapter: Initialization failed. adapter

filetype file file contains incorrect The adapter that detected the error.
statements. maxlength
The maximum length allowed for a name in a
Explanation Name/Value pair.
The adapter encountered a syntax error in file.

System action
Initialization ends, the adapter task ends, and the
adapter is now inactive. Processing continues.
Message Variables
Operator response
adapter
The adapter that detected the error. Notify the system programmer.
filetype
The file type is either CDS for a CDS file or FMT for System programmer response
a Message Adapter format file. Find message IHS0097E in the Event/Automation
file Service network log. Following this message is a hex
The file that contains incorrect statements. dump that displays the incorrect name of the Name/
Value pair. The first two bytes of the dump contain the
length of the name (including the length bytes),
System action
followed by the name. Inspect this data to determine
Processing continues. the source of the incorrect Name/Value pair and
correct it.
Operator response IHS0098I adapter: Encountered a Value in a
Notify the system programmer. Name/Value pair that has a length
that exceeds maxvaluelength. It is
System programmer response truncated.

Service network log. Other messages related to this
same error will be near this message in the log. These

Explanation varname
The variable being referenced.
The adapter encountered an error when processing an
event that contains an appended Name/Value pair. line
The length of the value exceeds the maximum The line number in the CDS file where the
allowable length of maxvaluelength. The value is reference was detected.
truncated to maxvaluelength characters and index
processing for the event continues. The index number in the CDS file where the
Message Variables reference was detected.
adapter System action

maxvaluelength
The maximum length allowed for a value in a
Name/Value pair. Operator response
System action
Processing continues. System programmer response
Correct the variable reference in the CDS file and
Operator response recycle the IHSAEVNT procedure.
Notify the system programmer. IHS0100I servicedata

Find message IHS0098E in the Event/Automation This message is written only to the Event/Automation
Service network log. Following this message is a hex Service network log and is intended to assist IBM
dump that displays the incorrect value of the Name/ Software Support in debugging errors when the
Value pair. The first two bytes of the dump contain the customer requires assistance.
length of the value (including the length bytes),
followed by the value. Inspect this data to determine IHS0100I differs from IHS0050E. IHS0050E is issued
the source of the incorrect Name/Value pair and when Event/Automation Service internal errors are
correct it. detected. IHS0100I is issued to provide extra
information concerning usage errors. For example, if
IHS0099E Improper variable reference you modify a configuration file and receive an error
varname on line line, index index. message identifying an improper keyword or value, the
error message might be accompanied by one, or more,
Explanation IHS0100I messages in the log.
The adapter was reading and parsing the adapter CDS Message Variables
file during initialization processing when a syntax error servicedata
was detected. Console message IHS0096E identifies The data to assist IBM Software Support in
the adapter and the CDS file name. An incorrect problem determination.
reference was detected involving varname on the
indicated line and index in the CDS file.
Consider the following example:
If the error message does not provide enough
CLASS SNA_Equipment_Malfunction information to identify the problem, contact IBM
SELECT Software Support, which can use the information in
1: ATTR(=,$ALERT_CDPT), VALUE(PREFIX,$V3);
# Error, can't reference any corresponding IHS0100I messages to resolve the
# $V3 at this point problem.
END
IHS0101E Incorrect line numbering on line
In this example, $V3 is an incorrect variable reference line. correctnumber must be used
because no previous SELECT statement established instead of incorrectnumber.
this value.
Message Variables
Explanation IHS0102E is the line number relative to the single CDS
file.
The adapter was reading and parsing the adapter CDS
file during initialization processing when a syntax error For example, if the error was at line 20 of CDS file
was detected. Console message IHS0096E identifies CDS2, and file CDS2 was included in file CDS1 with a
the adapter and the CDS file name. The line numbering %INCLUDE CDS2 statement at line 30, the message
on the specified line is incorrect. IHS0096E indicates that the line in error to be line 49;
this is because the %INCLUDE on line 30 of file CDS1
is replaced with line 1 of file CDS2.
CLASS SNA_Equipment_Malfunction The CDS file name indicated on message IHS0096E is
SELECT
2: ATTR(=,$ALERT_CDPT), VALUE(PREFIX,"10"); always the first CDS file that was processed. Included
# Error, improper line CDS file names are not used on message IHS0096E.
numbering.
# Should be 1, not 2. Consider the following example:
END
CLASS SNA_Equipment_Malfunction
Message Variables SELECT
1: ATXR(=,$ALERT_CDPT), VALUE(PREFIX,"10");
line # Error, "ATXR" rather than "ATTR".
The line number in the CDS file where the incorrect END
line numbering was detected.
Message Variables
correctnumber
The expected line number. line_number
The line number in the CDS file where the syntax
incorrectnumber
error was detected.
The incorrect line number.
token
The token at, or near, the syntax error.
System action
Operator response
Correct the line numbering in the CDS file and recycle System programmer response
the IHSAEVNT procedure.
Correct the syntax error in the CDS file and recycle the
IHS0102E Incorrect syntax detected on line IHSAEVNT procedure.
line_number. The current token is
token. IHS0103E Required keyword keyword is not
present.
Explanation
Explanation
The adapter was reading and parsing the adapter CDS
file during initialization processing when a syntax error The adapter was processing an event against the
was detected. Console message IHS0096E identifies statements in the CDS file when a syntax error was
the adapter and the CDS file name. The error was detected. Console message IHS0104E identifies the
detected on line_number near token token. adapter and the CDS file name. The required keyword
keyword is missing.
Note: If one or more %INCLUDE statements was used
to include CDS files, the line_number indicated in Consider the following example:
message IHS0102E might not be the actual line
number in the CDS file that contains the error. This is # Error, the SELECT statement is
because a single CDS file is created from all included # missing
END
CDS files. The %INCLUDE statement itself is replaced
with the first line of the CDS file that is being included.
Message Variables
Therefore, the line_number indicated in message

keyword Explanation
The required keyword that is missing.
The adapter was processing an event against the
statements in the CDS file when a syntax error was
System action detected. Console message IHS0104E identifies the
Processing continues. adapter and the CDS file name. The attribute variable
in a CDS SELECT ATTR statement has a type that
differs from the type in its corresponding KEY or
Operator response
VALUE statement.
System programmer response CLASS SNA_Equipment_Malfunction

SELECT
Correct the syntax error in the CDS file and recycle the 1: ATTR(=,$ALERT_CDPT), VALUE(PREFIX,10);
# Error, type mismatch. $ALERT_CDPT
IHSAEVNT procedure. # has type 'string', 10 has type
# 'integer'. Use double quotes around
IHS0104E adapter: Syntax error detected in # 10, i.e. "10", to make it a
CDS file file involving class class. 'string'.
END

The adapter was constructing an event to send to the name
event server when a syntax error was encountered in The name of the attribute variable in a CDS SELECT
CDS file file. The event was not sent to the event ATTR statement. Built-in keywords such as
server. $ALERT_CDPT are displayed without the leading $.
Message Variables In this example, ALERT_CDPT is displayed.
vartype
adapter
The type of the attribute variable, such as 'string'
The adapter that detected the error, such as the
or 'integer').
alert adapter.
keyword
file
The VALUE or KEY clause.
The CDS file that contains improper statements.
keywordtype
class
The type of the value in the VALUE or KEY clause.
The syntax error was detected under this CLASS
statement in the CDS file.
System action
Operator response
System programmer response Correct the syntax error in the CDS file and recycle the
IHSAEVNT procedure.
See message IHS0104E in the Event/Automation
Service network log. Other messages related to this IHS0106E Type mismatch: ATTR variable
same error will be close to IHS0104E in the log. These 'name' has type 'vartype', but
messages, along with the class, will help you identify 'operator' operator for keyword
the syntax error in the CDS file. Correct the incorrect keyword requires type
statements and recycle the IHSAEVNT procedure. 'requiredtype'.
IHS0105E Type mismatch: ATTR variable
'name' has type 'vartype'; keyword Explanation
keyword has type 'keywordtype'. The adapter was processing an event against the
statements in the CDS file when a syntax error was
detected. Console message IHS0104E identifies the
adapter and the CDS file name. The attribute variable
in a CDS SELECT ATTR statement has a type that time
conflicts with the type required by the operator The time in seconds that the event receiver will
operator. wait before recycling
System action
SELECT The task will not perform its function until it is
1: ATTR(=,$ALERT_CDPT), VALUE(>=,"10"); successfully initialized.
# Error, type mismatch. $ALERT_CDPT
# has type 'string', however the >=
# operator does not support type Operator response
# 'string', it supports only
integers.
END

name If the task requests a service, such as TCP/IP, ensure
The name of the attribute variable in a CDS SELECT that the TCP/IP program is active.
ATTR statement. Built in keywords such as
IHS0110W The Event Receiver task will be
$ALERT_CDPT are displayed without the leading $.
recycled in time seconds.
In this example, ALERT_CDPT is displayed.
vartype
Explanation
The type of the attribute variable, such as 'string'
or 'integer'). The event receiver is unable to initialize or receive
operator data. TCP/IP might be unavailable. After the specified
The operator, for example >, >=, PREFIX. timeout, the event receiver will be stopped and
restarted. This message will be reissued indefinitely
keyword until the event receiver is initialized or stopped by an
The VALUE or KEY clause. operator command.
requiredtype
Message Variables
The type required by the operator.
time
System action The time in seconds that the event receiver will
wait before recycling.
System action
Operator response
The event receiver will ignore all data until
Notify the system programmer. reinitialization.

Correct the syntax error in the CDS file and recycle the Notify the system programmer.
IHSAEVNT procedure.
IHS0109W The taskname task will be System programmer response
recycled in time seconds. Ensure the TCP/IP program is active.
Explanation IHS0111A adapter: Incorrect %INCLUDE line

in FMT file file.
An Event/Automation Service task is unable to
initialize or receive data. A required service, such as
Explanation
TCP/IP, might be unavailable. After the specified
timeout, the task will be stopped and restarted. This A format file line with the %INCLUDE keyword has a
message will be reissued until the task is initialized or syntax error.
stopped by an operator command.
Message Variables
Message Variables
adapter
taskname The event adapter designator.
The name of the task

file Explanation
The format file processing ended before the
completion of the current format specification.
System action
Message Variables
adapter
Operator response
file
Notify the system programmer. The member name of the format file.

Find message IHS0111A in the Event/Automation The message adapter task ends.
Service log. Message IHS0015A follows this message
and contains the line number and position of the
Operator response
format file error. Inspect the format file and correct
the error. Notify the system programmer.
IHS0112A adapter: Too many %INCLUDE
statements in file file1, including System programmer response
file2. Correct the format file information so that a complete
format specification is at the end of the file. Message
Explanation IHS0015A follows this message and contains the line
number and position of the format file error. Inspect
The maximum number of format files that are
the format file and correct the error. Restart the Event/
concurrently open for processing has been reached.
Automation Service.
The maximum number of nested files is currently 20.
An attempt to open the specified file for processing IHS0114E Unsuccessful call to function,
exceeds this limit. errno=errno, description
Message Variables
Explanation
adapter
The event adapter designator. The Event/Automation Service received an error on a
library function call.
file1
The file where the %INCLUDE statement resides. Message Variables
file2 function
The name of the file to be included. The name of the library function.
errno
System action The errno returned from the function call.
The message adapter task ends. description
A description of the returned errno.
Operator response
System action
Operator response
Reorganize the format file information so that there is
no need to have more than 20 nested files. Message Notify the system programmer.
IHS0015A follows this message and contains the line
number and position of the format file error. Inspect System programmer response
the format file and correct the error. Restart the Event/
Automation Service. If the problem persists, notify IBM Software Support.
IHS0113A adapter: Incomplete format IHS0115E Unable to access the C runtime

specification in FMT file file. library. OpenEdition MVS may not
be started.
A call to a library function returned an error of 167. baseclass
The base format specification class name.
System action bindclass
The bound format specification class name.
System action
Operator response
The input message is discarded.
Operator response
error messages. Start z/OS UNIX System Services
(formerly named OpenEdition MVS). If the problem System programmer response
persists, notify IBM Software Support. Use the information in this message and the message
IHS0116A adapter: Generic class does not preceding this one to correct the problem in the format
follow from bind class; input file.
message is discarded. IHS0118I adapter task has terminated.
A message that is bound to a particular format This message indicates that an Event/Automation
specification in the format file cannot successfully Service task has ended.
bind to the more generic format specifications
indicated by the FOLLOWS keyword. A format Message Variables
specification that follows another must be a more Adapter
specific derivation of the base format specification. The task identifier can be one of the following
Message Variables values:
adapter Alert Adapter

The event adapter designator. The alert adapter task
Alert to Trap Conversion
System action The alert-to-trap conversion task
The input message is discarded. Confirmed Alert Adapter

The confirmed alert adapter task
Operator response Confirmed Message Adapter
The confirmed message adapter task
Event Receiver
The event receiver task.
Message Adapter
Correct the format specification in error. Recycle the The message adapter task
message adapter task. If the problem persists, recycle
Trap to Alert Conversion
the Event/Automation Service.
The trap-to-alert conversion task
IHS0117A ==>Generic class : baseclass, Bind
class : bindclass. System action
Processing continues for other Event/Automation
Explanation Service tasks. If the entire Event/Automation Service
This message is issued only to the Event/Automation ends, all Event/Automation Service tasks end prior to
Service log. It indicates the base format specification the Event/Automation Service ending.
class name and the format specification class name
IHS0119I Event/automation service is
that was bound from the input message for message
terminating due to an operator
IHS0116A.
request.

The Event/automation service is ending. All tasks end An Event/Automation Service task STOP modify
normally. command cannot be executed because the task has
already stopped or is in the process of stopping. This
System action message might occur with the RECYCLE modify
command if the task is already stopped.
The Event/automation service ends.
Message Variables
IHS0121I service: Reset of backup server
connection was successful. adapter
The task identifier can be one of the following
values:
Explanation
Alert Adapter
A RESETSRV command was successfully processed. The alert adapter task.
Message Variables Alert to Trap Conversion
service The alert-to-trap conversion task
The service that is issuing this message. Confirmed Alert Adapter
IHS0122I adapter task already started or
start in progress. Confirmed Message Adapter
Explanation Event Receiver
An Event/Automation Service task START modify
command cannot be executed because the task has Message Adapter
already started or is in the process of starting. The message adapter task.
Trap to Alert Conversion
Message Variables
The trap-to-alert conversion task.
adapter
The task identifier can be one of the following System action
values:
Alert Adapter
The alert adapter task IHS0124I adapter task initialization
Alert to Trap Conversion complete.
The alert-to-trap conversion task
Explanation
Confirmed Alert Adapter
The confirmed alert adapter task An Event/Automation Service task has completed its
Confirmed Message Adapter initialization and is ready to handle input messages,
The confirmed message adapter task alerts, or events.
Event Receiver Message Variables

The event receiver task adapter
Message Adapter The task identifier can be one of the following
The message adapter task values:
Trap to Alert Conversion Alert Adapter
The trap-to-alert conversion task The alert adapter task.
Alert to Trap Conversion
System action The alert-to-trap conversion task
Processing continues. Confirmed Alert Adapter
IHS0123I adapter task already stopped or
stop in progress. Confirmed Message Adapter
Event Receiver
Message Adapter System action
The message adapter task.
An attempt will be made to connect to an alternate
Trap to Alert Conversion event server if one is specified in the configuration file
The trap-to-alert conversion task. for the adapter. If connection_less mode is being
used, this can be an indication that the event server
System action was recycled. In this case, an attempt is made to
connect using a different port. If the second attempt is
Processing continues. also unsuccessful, an attempt to connect to another
IHS0125A The NetView subsystem has server is made. If another server is not specified or a
terminated. connection cannot be established to any server, then
the event is buffered.
Explanation
Operator response
The NetView subsystem is no longer available. The
NetView subsystem includes the program-to-program Notify the system programmer.
(PPI) interface.
System action Ensure that the event server is active.
The Event/Automation Service attempts to reconnect IHS0128E OpenEdition MVS is not active.
with the PPI every 30 seconds.
Explanation
Operator response
An Event/Automation Service adapter attempted to
Restart the NetView subsystem.
use a z/OS UNIX System Services (formerly named
IHS0126A The FMT file file contains no OpenEdition MVS) function, but the z/OS UNIX System
FORMAT specifications. Services program is not available.
The specified format file does not contain valid format The adapter ends.
specifications.
Operator response
Message Variables
file
System action Activate z/OS UNIX System Services and restart the
adapter.
IHS0130E EAS initialization file error ==>
Operator response
This is a message header indicating that there was
System programmer response some error while processing the initialization file. More
messages will follow this message indicating the
Check for block comments that are out of position. If
specific error.
the format file specifications are included in a
commented-out block, there are no valid format
specifications processed by the message adapter. System action
IHS0127E The job ends.

Connection was refused.
Operator response
Explanation
An Event/Automation Service adapter cannot establish
a connection to an event server. The connection was
refused.

System programmer response in error. If the error occurred on a MODIFY command
line, the MODIFY command is ignored.
Use the following messages to determine the actual
cause of the failure.
Operator response
IHS0131E File file, line line, position position.
Notify the system programmer or reissue the correct
MODIFY command.
Explanation
This message contains file, line number, and line System programmer response
position information for any configuration file
initialization errors. More messages will follow this Correct the statement in the configuration file.
message indicating the specific error. IHS0133E command command syntactically
Message Variables incorrect.
file
Explanation
The configuration file name of the configuration file
in error. This message indicates that the command in the
line configuration file or on the MODIFY command line
The line number of the configuration file in error. contains syntax that is not valid.
position Message Variables

The character position after which the error has command
occurred. Depending on the specific error, the The command with the incorrect syntax.
actual position on the line where the error
occurred is anywhere from the specified character
System action
position to the end of the line.
If the error occurred in a configuration file, the Event/
System action Automation Service address space or the specific
service task ends, depending on the configuration file
The Event/Automation Service address space or the in error. If the error occurred on a MODIFY command
specific service task ends, depending on the line, the MODIFY command is ignored.
configuration file in error.
Operator response
Operator response
Notify the system programmer or reissue the correct
Notify the system programmer. MODIFY command.

Use the following messages to determine the actual Correct the statement in the configuration file.
IHS0134E command command value value
IHS0132E command command unknown. not supported.
This message indicates that the command in the This message indicates that the value given for a
configuration file or on the MODIFY command line is command in a configuration file was not supported,
not supported. such as a nonnumeric value where a number is
Message Variables expected, or a value that is too long.

The unsupported command. command
The command that failed.
System action value
If the error occurred in a configuration file, the Event/ The value in error.
Automation Service's address space or the specific
service task ends, depending on the configuration file
The Event/Automation Service address space or the If an input parameter or configuration file statement is
specific service task ends, depending on the in error, the Event/Automation Service address space
configuration file in error. or the specific service task ends. If the error occurred
on a MODIFY command line, the MODIFY command is
Operator response ignored.

Operator response
System programmer response Notify the system programmer or reissue a correct

MODIFY command.
Correct the statement in the configuration file.
IHS0135E keyword keyword unknown. System programmer response
Correct the statement in the configuration file or the
Explanation Event/Automation Service input parameter.
This message indicates that the keyword in the IHS0137E keyword keyword value value not
configuration file, the MODIFY command line, or an supported.
Event/Automation Service input parameter is
unknown.
Explanation
Message Variables
This message indicates that the keyword value in the
keyword configuration file, the MODIFY command line, or an
The unsupported keyword. Event/Automation Service input parameter was not
supported. For example, a nonnumeric value where a
System action number is expected or a value that is too long.
If an input parameter or configuration file statement is Message Variables

in error, the Event/Automation Service address space keyword
or the specific service task ends. If the error occurred The keyword that failed.
on a MODIFY command line, the MODIFY command is
value
ignored.
The value in error.
Operator response
System action
Notify the system programmer or reissue a correct
If an input parameter or configuration file statement is
MODIFY command.
in error, the Event/Automation Service address space
or the specific service task ends. If the error occurred
System programmer response on a MODIFY command line, the MODIFY command is
Correct the statement in the configuration file or the ignored.
Event/Automation Service input parameter.
Operator response
IHS0136E keyword keyword syntactically
incorrect. Notify the system programmer or reissue a correct
MODIFY command.
Explanation
This message indicates that the keyword in the
configuration file, the MODIFY command line, or an Correct the statement in the configuration file or the
Event/Automation Service input parameter contains Event/Automation Service input parameter.
syntax that is not valid.
IHS0138E MODIFY command error, position
Message Variables position ==>
keyword
The keyword with the incorrect syntax.

This message header indicates that there was an error Notify the system programmer.
while processing a MODIFY command. Additional
messages will follow indicating the specific error. System programmer response
Message Variables Correct the parameter in the event receiver
position configuration file.
The character position after which the error has IHS0141I SERVICE STATUS ADDITIONAL
occurred. Depending on the specific error, the INFO
position on the line where the error occurred can
be from the specified character position to the end
Explanation
of the line.
This is a message header that occurs in response to a
System action DISPLAY STATUS command issued to the Event/
Automation Service.
The MODIFY command is ignored.
IHS0142I ------- ------ ---------------
Operator response
Explanation
Use the following messages to determine the actual
cause of the failure, or notify the system programmer. This is a message header that occurs in response to a
DISPLAY STATUS command issued to the Event/
System programmer response Automation Service.
Use the following messages to determine the actual IHS0143I service status addinfo
Explanation
IHS0139E Program input parameter error
==> This message contains inserts to fill in the service
name, status, and other information that relates to the
Explanation service.
This message header indicates that there was an error Message Variables
while processing a program input parameter. service
Additional messages will follow indicating the specific The name of the service being reported:
error.
• ALERTA
System action • ALERTC
• ALRTTRAP
The Event/Automation Service ends.
• EVENTRCV
Operator response • MESSAGEA
Notify the system programmer. • MESSAGEC
• PPI
System programmer response • TRAPALRT
Use the following messages to determine the actual • TCP/IP
These values represent the Event/Automation
IHS0140E Parameter parameter is incorrect. Service subtasks, the NetView Subsystem PPI
interface, and the connection to the TCP/IP
Explanation service.
status
This message indicates that the parameter value in the
The status of the service. See the DISPLAY
event receiver configuration file was incorrect.
STATUS command in the NetView online help for
more information.
System action
The event receiver subtask ends.
addinfo • EVENTRCV
The additional information for each service. See • MESSAGEA
the DISPLAY STATUS command in the NetView
online help for more information. • MESSAGEC
• TRAPALRT
IHS0144E Event Receiver CFG file error ==>
qcount
Explanation The number of data buffers that have been sent to
the subtask, but have not yet been processed by
This message header indicates that there was an error the subtask.
while processing the event receiver configuration file.
sent
Additional messages will follow indicating the specific
The number of data buffers that have been sent by
error.
this subtask to another subtask.
recvd
System action
The number of data buffers that have been
The event receiver subtask ends. processed by this subtask.
IHS0148E adapter: CDS file file cannot be
Operator response opened.
Explanation
System programmer response The attempt to open the specified CDS file received a
Use the following messages to determine the actual file I/O error. The file I/O error is provided in the
cause of the failure. Event/Automation Service log.
IHS0145I TASK QCOUNT TOTAL SENT TOTAL Message Variables

RCVD adapter
Explanation file
This message header occurs in response to a DISPLAY The name of the CDS file.
QSTATS command issued to the Event/Automation
Service. System action
IHS0146I ---- ------ ---------- ---------- The adapter task ends.

This message header occurs in response to a DISPLAY Notify the system programmer.
QSTATS command issued to the Event/Automation
Service. System programmer response
IHS0147I task qcount sent recvd Find message IHS0148E in the Event/Automation
Service log. Message IHS0114E will follow this
Explanation message in the log. IHS0114E contains specific
information on the type of file I/O error that occurred.
This message contains inserts to fill in the task name,
If the problem cannot be resolved from this
current task queue count, number of messages
information, notify IBM Software Support.
received, and number of messages sent.
IHS0149E adapter: File read error in CDS file
Message Variables
file.
task
The name of the task being reported: Explanation
• ALERTA The next line from the specified CDS file cannot be
• ALERTC retrieved because of a file I/O error. The file I/O error
• ALRTTRAP is provided in the Event/Automation Service log.
• CONTROL Message Variables

adapter system1
The event adapter designator. The environment for which the specified startup
file parameters match.
The name of the CDS file. system2
The enviroment under which the Event/Automation
System action Service was started.

System action
Operator response The Event/Automation Service ends.

Operator response
System programmer response Correct the startup parameters to match the startup
environment or notify the system programmer.
Service log. Message IHS0114E will precede this
message in the log. IHS0114E contains specific
information on the type of file I/O error that occurred. Correct the startup parameters to match the startup
If the problem cannot be resolved from this environment.
information, notify IBM Software Support.
IHS0152E The $CDS_GROUP keyword is
IHS0150E adapter: CDS INCLUDE file name missing from a select group.
file is incorrect.
Explanation
Explanation
The CDS file, which is used by the event receiver, has a
A CDS file line with the %INCLUDE keyword has a CDS that is missing a check for the $CDS_GROUP
syntax error. keyword in one of its Select segments.
Message Variables
System action
adapter
The event adapter designator. The event receiver ends.
file
The name of the CDS file. Operator response
Correct the CDS file and restart the event receiver or
System action notify the system programmer.
Operator response Correct the CDS file and restart the event receiver.
Notify the system programmer. IHS0153E A CONTINUE slot value of
"slotvalue" is incorrect.
Explanation
Inspect the CDS file and correct the error.
The CDS file used by the event receiver has a
IHS0151E Startup parameters for system1 CONTINUE slot with an incorrect value.
are incorrect; started from
system2. Message Variables
slotvalue
Explanation The incorrect slot value.
An attempt was made to start the Event/Automation
Service from an environment that does not match the System action
format of the input parameters. The event receiver ends.
Message Variables
Correct the CDS file and restart the event receiver or While attempting to translate a subvector slot, there
notify the system programmer. were more closing subvector length braces found in
the slot value than opening braces. This applies to the
System programmer response event receiver and the trap-to-alert conversion task.
Correct the CDS file and restart the event receiver.

System action
IHS0154E An NMVT_TYPE slot value of The translation of the Event Integration Facility (EIF)
"slotvalue" is incorrect. event or SNMP trap ends.

The CDS file used by the event receiver has an Correct the CDS file and restart the event receiver or
NMVT_TYPE slot with an incorrect value. notify the system programmer.
Message Variables
slotvalue System programmer response
The incorrect slot value. Correct the CDS file and restart the event receiver. This
error message and the untranslated slot value will be
System action logged in the error/output file for the event receiver.
The event receiver ends. IHS0157E Found a closing suspend
translation brace without an
Operator response opening brace.

Explanation
While attempting to translate a subvector slot, there
System programmer response were more closing suspend translation braces found in
the slot value than opening braces. This error message
Correct the CDS file and restart the event receiver. and the untranslated slot value will be logged in the
IHS0155E A BUILD_SV31LIST slot value of error/output file for the task that issued the message,
"slotvalue" is incorrect. which is either the event receiver or the trap-to-alert
conversion task.
Explanation
System action
The CDS file used by the event receiver has a
BUILD_SV31LIST slot with an incorrect value. The translation of the Event Integration Facility (EIF)
event or SNMP trap ends.
Message Variables
slotvalue Operator response
The incorrect slot value. Correct the CDS file and restart the event receiver or
System action
The event receiver ends. System programmer response
Operator response
IHS0158E Found an incorrect character in
Correct the CDS file and restart the event receiver or the subvector translation stream.
Explanation
While attempting to translate a subvector slot, a
Correct the CDS file and restart the event receiver. nonhexadecimal character was found in an
IHS0156E Found a closing subvector length unsuspended translation stream. This applies to the
brace without an opening brace. event receiver and the trap-to-alert converstion task.

The translation of the Event Integration Facility (EIF) calclength
event or SNMP trap ends. The length of the subvector as calculated by the
task that issued the message
Operator response
System action
notify the system programmer. The translation of the Event Integration Facility (EIF)
Operator response
IHS0159I The calculated length (calclength) notify the system programmer.
and user specified length
(userlength) of a subvector do not
match. Using calculated length. System programmer response
Explanation
IHS0161E The length (length) of a subfield
An error occurred while translating a subvector slot runs beyond the subvector or is
because the total length of a subvector does not zero.
match the length that was coded in the subvector slot
value. Explanation
Message Variables During the calculation of the alert ID for the generic
calclength alert subvector, a subfield length was found to extend
The length of the subvector as calculated by the beyond the end of the subvector. This applies to the
event receiver or the trap-to-alert conversion task event receiver and the trap-to-alert conversion task.
userlength Message Variables
The length of the subvector as specified in the CDS
length
file
The length of the subfield.
System action
System action
The calculated length is used and processing
The translation of the Event Integration Facility (EIF)
continues.
event ends.
Operator response
Operator response
Correct the CDS file to avoid receiving this message in
the future and restart the event receiver, or notify the
system programmer.

Correct the CDS file to avoid receiving this message in
the future and restart the event receiver. IHS0162E Found at least one opening
subvector length brace without a
IHS0160E The calculated length (calclength) corresponding closing brace.
of a subvector is not between 2
and 255 bytes.
Explanation
Explanation An error occurred while attempting to translate a
subvector slot because there were fewer closing
While attempting to translate a subvector slot, the subvector length braces found in the slot value than
actual total length of a subvector is not in the range of opening braces. This error message and the
2—255 bytes. This message applies to the event untranslated slot value will be logged in the error/
receiver and the trap-to-alert converstion task.
output file for the event receiver or the trap-to-alert System action
conversion task.
The alert is discarded and processing continues.
System action
Operator response
If the alert was created because of translation of a
Event Integration Facility (EIF) event by the event
receiver, then correct the configuration file for the
Operator response event receiver and restart the conversion task. If the
Correct the CDS file and restart the event receiver or alert was created because of translation of an SNMP
notify the system programmer. trap by the trap-to-alert conversion task, then correct
the configuration file for the trap-to-alert conversion
task and restart it. Otherwise, notify the system
programmer.
IHS0163E Found at least one opening System programmer response
suspend translation brace without If using the event receiver to convert Event Integration
a corresponding closing brace. Facility (EIF) events to alerts, then correct the event
receiver configuration file and restart the conversion
Explanation task. If using the trap-to-alert conversion task to
convert SNMP traps to alerts, then correct the trap-to-
An error occurred while attempting to translate a alert conversion task and restart it.
subvector slot because there were fewer closing
suspend translation braces found in the slot value than IHS0165I The OUTPUT is set to destination.
opening braces. This error message and the
untranslated slot value will be logged in the error/ Explanation
output file for the event receiver or the trap-to-alert
conversion task. This is the first line generated in response to an
OUTPUT command that was issued without
parameters.
System action
Message Variables
event or SNMP trap ends. destination
The destination of Event/Automation Service
Operator response output (GTF, SYSOUT, or both).
Correct the CDS file and restart the event receiver or IHS0166E Unable to set the socket option
notify the system programmer. SO_LINGER.

Correct the CDS file and restart the event receiver. The event receiver task was unable to initialize.
IHS0164E The Alert Receiver PPI mailbox

System action
mailbox is not defined. The alert
will be discarded. The event receiver task ends.

An attempt to send a Event Integration Facility (EIF) Notify the system programmer.
event that has been translated to an alert to the
designated PPI receiver has failed because the PPI System programmer response
mail box for the designated receiver is not defined.
Message Variables messages, including IHS0114E. Verify that TCP/IP is
mailbox properly configured and active. If the problem
The name of the PPI mail box. persists, notify IBM Software Support.
IHS0167I The OUTSIZE is set to size bytes.

This is the second line generated in response to an This message header indicates that there was an error
OUTPUT command that was issued without while processing the named task's configuration file.
parameters. It specifies the setting of the OUTSIZE Additional messages indicating the specific error will
parameter. follow.
size taskname
The number of bytes to write before the output file The name of the task whose configuration file has
is closed and switched. an error.
IHS0168I task output file is file
System action
Explanation The task that issued the message ends.
This is the third and following lines generated in
response to an OUTPUT command that was issued Operator response
without parameters. It specifies the current output file Notify the system programmer.
for each task.
task Use the messages that follow this header to determine
The name of the task. the actual cause of error.
file IHS0179E Found a closing translation
The name of the output file. If the output file is not bracket without an opening
an HFS, or a sequential data set or PDS member, bracket.
the name will be the data set definition of the file.
IHS0169E Failure opening or writing to Explanation
OUTPUT file outfile. Standard While attempting to translate a subvector slot in the
output will be used. CDS file, there were more closing translation brackets
found in the slot value than opening brackets. This
Explanation error message and the untranslated slot value will be
logged in the error/output file for the trap-to-alert
The specified output file cannot be opened. The
conversion task.
standard output stream will instead be used.
outfile The translation of the SNMP trap ends.
The name of the output file.
Operator response
System action
Correct the CDS file and restart the trap-to-alert
The output file is ignored. All output for the service conversion task or notify the system programmer.
task will be placed in the standard output stream.
Operator response
Notify the system programmer. conversion task.
System programmer response IHS0180E Found at least one opening

translation bracket without a
Specify a valid output file, within the startup corresponding closing bracket.
procedures output data set definitions, or with the -E
option when starting from the OE command shell.
Explanation
IHS0178E taskname task CFG file error ==> An error occurred while attempting to translate a
subvector slot in the CDS file because there were
fewer closing translation brackets found in the slot
value than opening brackets. The error message and service
the untranslated slot value will be logged in the error/ The name of the service for which the settings are
output file for the trap-to-alert conversion task. displayed. It can have the following values:
Alert Adapter
System action The alert adapter service.
The translation of the SNMP trap ends. Alert to Trap Conversion
The alert-to-trap conversion service.
Operator response Confirmed Alert Adapter
The confirmed alert adapter service.
conversion task or notify the system programmer. Confirmed Message Adapter
The confirmed message adapter service.
System programmer response E/AS Global
The global settings for the Event/Automation
Service.
conversion task.
Event Receiver
IHS0181E The service will continue recycling The event receiver service.
until it can successfully define a
Message Adapter
socket.
The message adapter service.
Explanation Trap to Alert Conversion
The trap-to-alert conversion service.
The named service cannot successfully define and
register a server socket with TCP/IP. IHS0183I CFG file : cfgfilename (fromtype)
Message Variables
Explanation
service
This is a message in response to a SETTINGS
The name of the service which cannot register its
command issued to the Event/Automation Service.
socket.
Message Variables
System action cfgfilename
The service waits for 60 seconds before again The full name of the configuration file used by this
attempting to define and register a socket. The service service.
continues to recycle until the socket is registered or fromtype
the service ends. An indication of how the configuration file was
specified. It can have the following values:
Operator response C
Notify the system programmer. The configuration file was specifed on a global
initialization file statement.
System programmer response D
The configuration file was specified by default.
Use the information in the output log and any
corresponding console messages which preceded this P
message to determine why the service is not able to The configuration file was specified as a
register with TCP/IP. startup parameter.
IHS0182I <==Current service Service IHS0184I ** The service is not active **

Settings==>
Explanation
Explanation This is a message in response to SETTINGS command
This is a message header in response to a SETTINGS issued to the Event/Automation Service. This message
command issued to the Event/Automation Service. indicates that there is no SETTINGS data available for
this service because the service is not active.
Message Variables
IHS0185I setting = value (fromtype)

This is a message in response to a SETTINGS number
command issued to the Event/Automation Service. The number of the FilterCache statement for which
the settings are displayed. This number
Message Variables
corresponds to the position of this FilterCache
setting statement in the service configuration file relative
The name of the setting that is displayed. to the other FilterCache statements in the file.
value IHS0189I The adapter services are running
The value of the setting. in secure mode.
fromtype
An indication of how the setting was specified. It Explanation
can have the following values:
C command issued to the Event/Automation Service.
The configuration file was specifed on a global This message appears only for the alert adapter or
initialization file statement. message adapter service if the service has been
D started with the -S option from a UNIX System
The configuration file was specified by default. Services command shell. The SETTINGS data is not
available for services started with the -S option.
P
The configuration file was specified as a IHS0190E service: Could not access the
startup parameter. TestMode file.
IHS0186I Filter number slots:
Explanation
Explanation The service is operating in test mode as specified by
the TestMode statement. The event data is written to
the file specified by the ServerLocation statement
when the service is running in test mode. This
Message Variables message indicates that there is a problem accessing
this file.
number
The number of the Filter statement for which the Message Variables
settings are displayed. This number corresponds
service
to the position of this Filter statement in the
The name of the service which issued the
service configuration file, relative to the other
message.
Filter statements in the file.
IHS0187I slotname=slotvalue; System action
The event is not copied to the test mode file.
Explanation
command issued to the Event/Automation Service. Operator response
slotname
The name of a slot from a Filter or FilterCache System programmer response
statement.
Additional information describing the problem is
slotvalue written to the output log for this service. Use this
The value of a slot from a Filter or FilterCache information to correct the problem and recycle the
statement. service task. If the source of the problem cannot be
IHS0188I FilterCache number slots:
Software Support.
Explanation IHS0191I service: Number of

ServerLocations (number) exceeds
the maximum of maximum;
ignoring extras.
The ServerLocation statement for the service contains If this is not an expected condition, such as a known
more locations than the maximum allowed. outage by the event server or servers, see the IBM Z
NetView Troubleshooting Guide for more information
Message Variables
on diagnosing TCP/IP connectivity problems for the
service Event/Automation Service.
IHS0193I service: Server connections have
message.
been resumed.
number
The number of locations that are defined on the
Explanation
ServerLocation statement.
maximum This message occurs if the server connections are
The maximum number of locations that are currently suspended and an event is successfully sent
allowed on the ServerLocation statement. to one of the locations specified on the ServerLocation
statement.
The additional locations are ignored. Processing service
continues. The name of the service which issued the
message.
Operator response
System action
If events were saved in the cache file, the cache file is
System programmer response flushed. Processing continues.
Change the ServerLocation statement to remove the IHS0194E service: A file access error
extra locations and recycle the service task. occurred for the cache file.
IHS0192I service: Server connections are Explanation

suspended.
The service is attempting to cache an event and there
Explanation is a problem accessing the cache file. When this
message appears, events are not cached until
This message occurs when an event cannot be sent to message IHS0196I is issued.
any of the locations specified on the ServerLocation
statement. This message is issued only if the Message Variables
connections are not already suspended. When this service
message appears, events are not sent to any of the The name of the service which issued the
locations on the ServerLocation statement until message.
message IHS0193I is issued.
service The current operation ends and processing continues
The name of the service which issued the with the next event. If the cache file cannot be
message. accessed during an attempt to buffer an event, the
event is not buffered. The state of the cache file
System action depends on when and what type of error occurred.
If event buffering is allowed, the event is copied to the Operator response

cache file. Otherwise, the event is discarded.
Processing continues with the next event. Notify the system programmer.

Notify the system programmer. Additional information describing the problem is
written to the output log for this service. Use this
information to correct the problem and recycle the

service task. If the source of the problem cannot be IHS0197E service: Cache file corrupted. The
determined from this information, contact IBM current contents will be discarded.
Software Support.
IHS0195E service: An event cannot be Explanation
cached: The event size is greater This message can occur during an attempt to cache an
than the maximum cache file size. event in the cache file. The event at the end of the
cache file does not end with a valid event separator.
Explanation This indicates that the cache file has been corrupted.
The service attempted to cache an event that has a Message Variables
size greater than the maximum size allowed for the
service
cache file. The maximum cache file size is specified on
the BufEvtMaxSize statement.
message.
Message Variables
service System action
The name of the service which issued the The current contents of the cache file are discarded.
message. The event that is to be cached is then written to the
cache file and processing continues.
System action
The current event is discarded and processing Operator response
continues with the next event. Notify the system programmer.

Notify the system programmer. Additional information describing the problem is
written to the output log for this service. This problem
System programmer response can occur if the cache file was modified by an operator
with a system editor. If the file was not intentionally
modifed by an operator and the problem cannot be
determined from the information in the output log,
occurs only if an event is unusually large or the
BufEvtMaxSize statement contains a value which is
unusually small. Increase the BufEvtMaxSize to handle IHS0198E service: An event in the cache file
this event size and recycle the service task. is not properly terminated. The
event will be discarded.
IHS0196I service: File access errors have
been corrected. Caching is
resumed. Explanation
This message can occur during an attempt to flush
Explanation events from the cache file. The event at the end of the
cache file does not end with a valid event separator.
This message occurs if the event caching was
This indicates that the cache file has been corrupted.
previously stopped because of a cache file access
error and the error was corrected. The current event is Message Variables
successfully cached.
service
Message Variables The name of the service which issued the
message.
service
message. System action
The current event is discarded. Since it is the last
System action event in the cache file, the flushing of the cache
completes and processing continues.
The current event is cached and processing continues
with the next event.
Operator response
System programmer response number
The number of ports that are defined on the
ServerPort statement.
can occur if the cache file was modified by an operator maxnum
with a system editor. If the file was not intentionally The maximum number of ports that are allowed on
modifed by an operator and the problem cannot be the ServerPort statement.
determined from the information in the output log,
contact IBM Software Support. System action
IHS0199E service: An event in the cache file The additional ports are ignored. Processing
is too large for the Read buffer. continues.
The event will be discarded.
Operator response
Explanation
This message can occur during an attempt to flush
events from the cache file. The event currently being System programmer response
flushed is larger than the size of the buffer used to
read data from the cache file. The size of this buffer is Change the ServerPort statement to remove the extra
specified by the BufEvtRdBlkLen statement. ports and recycle the service task.
Message Variables IHS0201I service: At least one

ServerLocation must be specified.
service
message. Explanation
The configuration file of the named service did not
System action contain a ServerLocation statement. This service
requires at least one ServerLocation.
The current event is discarded and processing
continues with the next event in the cache file. Message Variables
service
Operator response The name of the service which issued the
Notify the system programmer. message.
Additional information describing the problem is The service terminates.

can occur if the BufEvtRdBlkLen setting is unusually Operator response
small or if an event written to the cache file is Notify the system programmer.
unusually large. Increase the BufEvtRdBlkLen to
handle this event size and recycle the service task.
IHS0200I service: Number of ServerPorts
Add a ServerLocation to the services configuration file.
(number) exceeds the maximum of
maxnum; ignoring extras. IHS0317E No valid CDS statements found in
adapter CDS file name.
Explanation
Explanation
The ServerPort statement for the service contains
more ports than the maximum allowed. No CDS statements were found during CDS file
processing. Alerts cannot be converted to traps or
Message Variables
Event Integration Facility (EIF) events (depending on
service which adapter is initializing).
Message Variables
message.
adapter
The name of the adapter that is initializing.

name System action
The name of the CDS file being processed.
System action
Operator response
The task that issued the message ends.
Verify that the z/OS SNMP agent is active. If not,
activate it and recycle the ALRTTRAP task. Otherwise,
Operator response contact the system programmer
System programmer response Examine the Event/Automation Service log and the log
Verify that the correct CDS file is being processed by output for the z/OS SNMP agent for error messages
adapter initialization. If so, examine the CDS file and pertaining to the failure. If the failure cannot be
ensure there are valid CDS statements in the file. determined, IBM Software Support.
IHS0318W Unable to format alert to trap. IHS0320E Unable to connect to OS/390

SNMP agent.
Explanation
Explanation
The alert-to-trap conversion task was unable to create
an SNMP trap from an alert. Possible causes include The Event/Automation Service ALRTTRAP task was
errors in the Class Definition File or internal errors in unable to obtain a connect to the z/OS SNMP agent.
z/OS TCP/IP services.
System action
System action ALRTTRAP initialization is stopped.
Operator response
Operator response Verify that the z/OS SNMP agent is active. If not,
Notify the system programmer. activate it and restart the ALRTTRAP task. Otherwise,
Examine the Event/Automation Service network log for
error messages pertaining to the failure, such as an If the SNMP agent is active, examine the Event/
incorrect format for the SPECIFIC value in the CDS file. Automation Service network log and the SNMP agent
If CDS errors are detected, correct the CDS file and log for error messages pertaining to the failure.
recycle the ALRTTRAP task. If the cause of the error Possible causes of failure include:
cannot be determined, contact IBM Software Support. • Invalid host name or community specification in the
IHS0319W Unable to send trap to OS/390 IHSAATCF file. In particular, the community name
SNMP agent. might need to be defined in the TCP/IP PW.SRC file.
• Inability to start the SNMP agent because of errors in
Explanation the TCP/IP configuration for the SNMP agent.
The Event/Automation Service was unable to send a

trap to the z/OS SNMP agent for processing.
Chapter 14. IHS Prefix Messages Issued from the
NetView Management Console Workstation
This chapter describes IHS prefix messages that are issued from the NetView management console
workstation. Chapter 13, “IHS Prefix Messages Issued from the Host,” on page 643 describe IHS prefix
messages that are issued from the host.
Note:
1. In some instances, a message number issued from the host might be identical to a message number
issued from the NetView management console workstation, differing only in the suffix. Both the text of
the message and the explanation of the message are very different. For example, IHS0200I is issued
from the host, while IHS0200E is issued from the workstation.
Message IHS0200I reads:
"service: Number of ServerPorts (number) exceeds the maximum of maximum; ignoring extras."
An explanation follows, providing additional details specific to the IHS0200I message.
Message IHS0200E reads:
"The configuration file ihscacm.cfg was not found. Verify that the file exists in the
$BINDIR/TDS/Server/config directory and that the BINDIR environment variable is set."
An explanation follows, providing additional details specific to the IHS0200E message,
2. The IHS prefix messages for the NetView management console topology console and the NetView
management console topology server are available on the workstation where the console or server is
installed. You can access the help for these messages from an active NetView management console,
or directly from a Web browser on a computer that has the NetView management console or NetView
management console server installed by entering one of these URLs on your Web browser:
• On a NetView management console
file:///basedir/bin/generic_unix/TDS/client/
help/ihs_hlp_using_languageid.html
• On a NetView management server
file:///basedir/bin/w32-ix86/TDS/server/db/current
/help/ihs_hlp_using_languageid.html
where basedir is the base path of the NetView management console or NetView management
console server and languageid is the numeric language identifier (for example, 437 for English or
932 for Japanese) for the type of help that is installed on your system.
On Windows systems, the default for basedir is
C:\usr\local\Tivoli
On UNIX and AIX platforms, the default for basedir is
/usr/local/Tivoli
IHS0200E The configuration file ihscacm.cfg Explanation

was not found. Verify that the file The topology communications server cannot find the
exists in the $BINDIR/TDS/ configuration file ihscacm.cfg. Verify that the BINDIR
Server/config directory and that environment variable is properly set and that the file
the BINDIR environment variable exists in the $BINDIR/TDS/server/config directory.
is set.

System action one instance of the
communications server can be
The topology communications server ends.
active at a time.
Operator response
Explanation
Check that the file exists in the $BINDIR/TDS/server/
An attempt was made to start the topology
config directory. If not, contact your system
communications server, but the program was already
programmer.
active.

System action
Reinstall the topology server.
The second attempt to load the topology
IHS0201E The configuration file ihscacm.cfg communications server is ignored.
is not valid.
Operator response
Explanation Contact your system programmer.
The format of the configuration file is not valid. This
occurs when the file is unintentionally modified. System programmer response
If you want to restart the server, stop the server that is
System action currently running, then restart the server. Otherwise,
The topology communications server ends. no action is required.
IHS0204E The communications server
Operator response program's name is not properly
Notify the system programmer. defined in the SNA
communications server
transaction program profile.
Reinstall the topology server. Explanation
IHS0202E An unexpected error occurred The remotely attachable transaction program profile,
during initialization. in the IBM Communications Server configuration file,
does not contain the topology communications server
Explanation transaction program's name (30F0F4F4) or is not
properly defined.
A system error occurred during the initialization of the
topology communications server. This error can be
caused by an out-of-memory condition. System action
The topology communications server logs the error
System action and continues operation.
Operator response
When an out-of-memory condition exists, you can free
some memory by stopping other applications or by System programmer response
adding memory to the system. Also confirm that Check the configuration of the IBM Communications
swapping is enabled. If you cannot resolve the error, Server. If you cannot resolve the error, contact IBM
contact the system programmer. Software Support.
program is ending due to an
Check for an out-of-memory condition. If the condition internal error.
does not exist, contact IBM Software Support.
program is already active. Only

An internal error occurred in the topology Depending on the severity of the SNA error, the
communications server. This error can be caused by topology communications server might end.
configuration errors.
Operator response
System action
Operator response
Restart the SNA communications server, then restart
Notify the system programmer. the topology server.
IHS0208E The SNA communications server
System programmer response APPC subsystem is not loaded.
Check the configuration of the IBM Communications
Server. If you cannot resolve the error, contact IBM Explanation
Software Support.
The IBM Communications Server LU 6.2 subsystem
IHS0206E The APPC attach manager is not was not active before the topology communications
active. server transaction program was started.

The IBM Communications Server LU 6.2 attach The topology communications server logs the error
manager is not active. The topology communications and continues.
server logs the error and continues.
Operator response
System action
The topology communications server retries the
operation. System programmer response
Check the configuration of the IBM Communications
Operator response
Server. For more information, refer to the IBM
Activate the attach manager using the IBM communications server online documentation. If you
Communications Server Subsystem Management cannot resolve the error, contact IBM Software
menu. Notify the system programmer. Support.
IHS0209E An error occurred while
System programmer response attempting to start a thread in the
Modify the IBM Communications Server SNA base communications server program.
profile in the IBM Communications Server
configuration file to automatically activate the attach Explanation
manager.
An out-of-memory condition causes the topology
IHS0207E The SNA processing is ending communications server to end.
because the SNA communications
server APPC subsystem has ended System action
abnormally.
Explanation
Operator response
The topology communications server is ending
because the IBM Communications Server LU 6.2 You can free some memory by stopping other
subsystem stopped unexpectedly. Further LU 6.2 applications, or by adding memory to the system. Also
communications with the host are not possible. To re- check that swapping is enabled. If the error still exists,
enable LU 6.2 support, recycle the topology notify the system programmer.
communication server.
Chapter 14. IHS Prefix Messages Issued from the NetView Management Console Workstation 701
Confirm that an out-of-memory condition exists. If the An error occurred because a partner transaction
condition does not exist, contact IBM Software program did not follow the correct protocol, or
Support. because an error was encountered in a partner
transaction program. Further LU 6.2 communications
IHS0210E The communications server with the host are not possible. To re-enable LU 6.2
program is ending due to a support, recycle the topology communication server.
memory allocation error.
System action
Explanation
An out-of-memory condition causes the topology and continues.
communications server to end.
Operator response
System action

Operator response
You can free some memory by stopping other
applications, or by adding memory to the system. Also IHS0213E An APPC session has ended
check that swapping is enabled. If the error still exists, abnormally.
Explanation
The session with a partner transaction program ended
Confirm that an out-of-memory condition exists. If the unexpectedly. This warning is caused by the
condition does not exist, contact IBM Software unexpected stopping of a partner transaction program,
Support. the IBM Communications Server, or VTAM.
deallocating a SNA session. Operator response
Check for the cause of the session termination, and
Explanation restart the session.
An LU 6.2 error occurred when the LU 6.2 session was IHS0214E An error occurred while converting
deallocated. This warning can be caused by errors in a string from EBCDIC to ASCII.
other components, or by the unexpected stopping of
the IBM Communications Server. This warning is not Explanation
critical and does not impact the use of the topology
server. This error can be the result of an error in the
configuration of the IBM Communications Server.
System action
System action
The server continues to run.
and continues.
Operator response
If the warning occurs often and you cannot resolve the System programmer response
error, contact IBM Software Support.
Correct the configuration of the IBM Communications
IHS0212E The SNA processing is ending due Server.
to an APPC protocol error.
IHS0215E Communications Server
configuration file. Sense code

code1. Primary Return Code code2. System programmer response
Secondary Return Code code3.
Correct the configuration of the IBM Communications
Server LU 6.2 subsystem.
Explanation
IHS0217E The maximum number of
The IBM Communications Server LU 6.2 subsystem is transaction programs has been
not properly configured. exceeded for LU luname.
Message Variables
Explanation
code1
Sense code An LU 6.2 configuration error existed in the IBM
code2 Communications Server.
Primary return code Message Variables
code3 luname
Secondary return code The name of the local LU.

The topology communications server logs the error The transaction program ends.
and continues.
Operator response
Operator response

Set the Maximum Number of Transaction Programs
Correct the configuration of the IBM Communications parameter to zero in the IBM Communications Server
Server. local LU profile. When the Maximum Number of
IHS0216E An error occurred while Transaction Programs=0, IBM Communications Server
attempting to allocate a session to allows an unlimited number of transaction programs.
LU luname. Verify that the LU is IHS0218E The communications server
active. program received bad data. The
data will be logged to the error log.
Explanation
This error can occur because the destination LU is not Explanation
active. The error can also occur when an LU 6.2 The topology communications server program
configuration error exists in the IBM Communications received a data packet that contained a format that is
Server. not valid. This message can be caused by an error in
Message Variables another component of the topology server, or by
another application erroneously sending data to the
luname topology communications server.
The name of the destination LU.
System action
System action
The bad data is logged and the topology
Communication to the destination LU is not communications server continues.
established.
Operator response
Operator response
Check that the destination LU is active. If the
destination LU is active and the error still exists, notify
the system programmer. System programmer response
If this error exists because an error occurred in
another component of the topology server, disregard
the error message. Check whether another application
is sending data to the topology communications server Explanation
and correct the error.
A system error occurred during the initialization of the
IHS0223E The topology communications topology communications server. This error can be
server program encountered an caused by the topology server being unable to
error during initialization. attached to the required IPC resources.

The topology communications server program The topology server ends.
encountered an error while performing initialization
processing. The error might be caused by one of the Operator response
following reasons:
When the error occurs, stop all of the topology server
• An IP address cannot be determined for the TCP/IP processes by issuing tstop, then issue tstop -f to
host name of the NetView management console ensure that all of the IPC resources have been cleaned
server. For example, a gethostbyname() call failed up. If the problem persists, contact your system
for the host name. programmer.
• The ihscacm.cfg configuration file in the
$BINDIR/TDS/server/config directory might be System programmer response
missing or corrupted.
• Some other internal error was encountered. Support.
System action IHS0228I The SNA communications server

subsystem is not active. If SNA LU
The topology communications server ends. 6.2 communication services are
needed, verify that the subsystem
Operator response has been started.
Do the following:
Explanation
• Ensure that the host name of the NetView
management console server has a corresponding The topology communications server was unable to
valid IP address. For example, an incorrect host connect to the SNA communications server.
name in the /etc/hosts file (or its equivalent,
depending on the operating system) can cause this System action
problem. The topology communications server logs the error
• Ensure the ihscacm.cfg file is present in the and continues.
$BINDIR/TDS/server/config directory. If not, the
NetView management console server installation Operator response
files have been corrupted. You must uninstall and
reinstall the NetView management console server. When the error occurs, verify that the SNA
communications server daemons have been started. If
Stop the server and then start it again. If the problem not, then start them. If the problem persists, contact
persists, contact your system programmer. your system programmer.

Contact IBM Software Support. If the condition persists, contact IBM Software
IHS0227E An operating system error Support.
occurred during initialization. The IHS0229E The communications server
topology communications server program was unable to establish a
program was unable to attach to connection with the host. Verify
the required shared memory or that the Transaction Program
was unable to allocate required Name (TPN) 30F0F4F4 does not
semaphores. appear in a SNA Communications
Server TPN Profile.

The topology communications server was unable to The topology communications server received
establish an LU 6.2 connection, possibly because of an incorrect data from the host during connection
error in the Transaction Program profile. establishment. A GET_PARAMETERS request failed.

The topology communications server logs the error The topology communications server logs the error
and continues. and continues.

When the error occurs, verify that the Transaction When the error occurs, verify that the profiles for the
Program Name (TPN) 30F0F4F4 does not appear in session that the topology server is using are correct.
the SNA communications server TPN Profile. If the Check the host logs for additional information. If the
problem persists, contact your system programmer. problem persists, contact your system programmer.

If the condition persists, contact IBM Software If the condition persists, contact IBM Software
Support. Support.
IHS0230E The communications server IHS0232E The communications server
program received incorrect data program failed on a SNA OPEN
from the host during connection request.
establishment. The connection
failed. Explanation
The topology communications server received
Explanation
incorrect data from the host during connection
The topology communications server received establishment. An OPEN request failed.
establishment. System action
System action
and continues.
and continues. Operator response
When the error occurs, verify that the profiles for the
Operator response
session that the topology server is using are correct.
When the error occurs, verify that the profiles for the Check the host logs for additional information. If the
session that the topology server is using are correct. problem persists, contact your system programmer.
Check the host logs for additional information. If the
problem persists, contact your system programmer. System programmer response
Support.
Support.
program failed on a SNA Open. The
IHS0231E The communications server maximum number of allowed file
program was unable to establish a descriptors is currently open.
connection with the host. Data
received from a Explanation
GET_PARAMETERS request was
incorrect. The topology communications server received
establishment. An OPEN request failed because the
maximum number of allowed file descriptors has been Explanation
reached.
The SELECT function is used to check the I/O status of
one or more connections. An unexpected error was
System action returned from this function.
and continues. System action
Operator response and ends.
When the error occurs, stop daemons and programs
that are running that are not needed. Increase the Operator response
system limit for the number of allowed file descriptors.
Stop all of the topology daemons with tstop. Run tstop
If the problem persists, contact your system
with the -f flag and then restart the daemons. If the
programmer.
problem persists, contact your system programmer.

Support.
Support.
program failed on a SNA
program failed on a SNA
ALLOCATE_LISTEN request. SNA
GET_PARAMETERS request. SNA
processing is ending.
processing is ending.
Explanation
Explanation
ALLOCATE_LISTEN registers a list of LU 6.2 TPNs for
The server was attempting to retrieve data associated
which the server wants to accept allocate requests
with the receipt of an allocate request for the server's
from remote transaction programs. This registration
TPN, when and error occurred on the connection.
failed. This problem is generally caused by a
configuration error. Further LU 6.2 communications
with the host are not possible. To re-enable LU 6.2 System action
support, recycle the topology communication server. The topology communications server logs the error
and ends.
System action
The topology communications server logs the error Operator response
and ends. Stop all of the topology server daemons by issuing
tserver stop, followed by tserver stop -f. Then restart
Operator response the daemons. If the problem persists, contact your
system programmer.
Check the host logs for additional information. If the System programmer response
problem persists, contact your system programmer. If the condition persists, contact IBM Software
Support.
If the condition persists, contact IBM Software program encountered an error
Support. while allocating a conversation
with the host. The session from
the host to the workstation is
program failed on a SELECT
terminated.
request. Possible storage
allocation problem.
Explanation
The topology communications server encountered an
error while allocating a conversation with the host. The

session from the host to the workstation ends. This GET_PARAMETERS request. The connection to the
problem is generally caused by a configuration error. host has failed.


When the error occurs, verify that the profiles for the When the error occurs, verify that the profiles for the
session that the topology server is using are correct. session that the topology server is using are correct.
Check the host logs for additional information. If the Check the host logs for additional information. If the
problem persists, contact your system programmer. problem persists, contact your system programmer.

If the condition persists, contact IBM Software If the condition persists, contact IBM Software
Support. Support.
IHS0238E The communications server IHS0240E The communications server
program encountered an error program was unable to allocate a
while allocating a conversation session with the host. The
with the host. The session connection to the host has failed.
parameters conflicted with those
at the host. Explanation
The topology communications server was unable to
Explanation
allocate a session with the host. The connection to the
The topology communications server encountered an host has failed.
error while allocating a conversation with the host. The
session parameters conflicted with those at the host. System action
System action
and continues.
and continues. Operator response
Operator response
When the error occurs, verify that the profiles for the Check the host logs for additional information. If the
session that the topology server is using are correct. problem persists, contact your system programmer.
Check the host logs for additional information. If the
problem persists, contact your system programmer. System programmer response
Support.
Support.
program received a SIGUSR1
IHS0239E The communications server signal. Communications with the
program received an incorrect host may be lost.
number of parameters from a
GET_PARAMETERS request. The Explanation
connection to the host has failed.
The topology communications server received a
SIGUSR1 signal. The SNA communications server
Explanation
issues a SIGUSR1 when a connection is lost. It is
The topology communications server received an possible the communications with the host might have
incorrect number of parameters from a been ended.

A SIGUSR1 is generated when the communications A SIGDANGER signal indicates that paging space is
server is stopped. Restart the SNA communications low. Stop unneeded programs or increase paging
server. If the problem persists, contact your system space. If the shortage continues, stop the topology
programmer. server. If the problem persists, contact your system
programmer.
Support. If the condition persists, contact IBM Software
Support.
program was unable to send data IHS0245E TCP socket connection failed
to the host. Either the session was (connection refused).
deactivated or data was delivered
to the host in error. The session is Explanation
terminated.
The topology communications server received a
"connection refused" error code while attempting to
Explanation
set up a socket.
send data to the host. Either the session was System action
deactivated or data was delivered to the host in error.
The session ends. The topology communications server logs the error
and continues.
System action
Operator response
and continues. When the error occurs, verify that the server that you
are trying to connect to is running and ready to accept
connections. Verify that a path exists to the server. If
Operator response
the problem persists, contact your system
When the error occurs, verify that the profiles for the programmer.
Check the host logs for additional information. If the System programmer response
problem persists, contact your system programmer.
Support.
IHS0246E The topology communications
Support. server program was unable to load
the SNA stack DLLs wappc32.dll
IHS0244E The communications server and wincsv32.dll. The LU 6.2
program received a SIGDANGER communications function has been
signal. A paging space shortage disabled.
may exist.
Explanation
Explanation
The communications server received a SIGDANGER load the SNA DLLs wappc32.dll and wincsv32.dll.
signal. These DLLs are required if LU 6.2 communications is to
be used for conversation with IBM Z NetView.

The topology communications server logs the error An unrecoverable error occurred in the topology
and continues. communications server.

If LU 6.2 communications is not needed, then ignore The communications server ends.
this message. If LU 6.2 communications is needed,
then verify that the location of these DLLs is included Operator response
in the PATH environment variable. If the problem
persists, contact your system programmer. Contact the system programmer responsible for the
topology communications server.
Support. Try to restart the communications server. If the
problem persists, check the message and error logs. If
IHS0252I Issue the tserver stop command to you cannot correct the problem, contact IBM Software
end this process. Support.
IHS0400E The path specified for the error log
System action
file does not exist. Create the
After issuing tstop, the process ends. directory.

Contact your system programmer. The directory specified for the error log does not exist.

Stop the process by issuing the tstop command from The log entry was not written to the error log.
the $BINDIR/TDS/server/bin directory.
IHS0253I SNA communications have been Operator response
disabled. Recycle the Either change the log file directory with the IHSZSET
communications server to tool, or create the specified directory.
reestablish the service.
IHS0401E The error log could not be opened
because too many files are already
Explanation
open. Stop other applications in
The topology communication server thread controlling the system.
SNA communications has ended. See previous
messages indicating why the thread was ended. Explanation
The error log cannot be opened because too many files
System action
are already open.
The server continues to operate, but SNA
communications are disabled. System action
The log entry was not written to the error log.
Operator response
If you need SNA communications, resolve the problem Operator response
that caused SNA co
Stop other applications that are running in the system,
IHS0260I The communications server is until the error is corrected.
terminating due to an internal
error. IHS0402E The error log file was not opened
because the disk is full.
The error log file was not opened because the disk is If the problem persists, recycle the topology server. If
full. this does not correct the problem, contact IBM
Software Support.
System action IHS0406E Message message in file file was
The log entry was not written to the error log. not found
Free some space on the disk or change the trace log A message was to be issued, but cannot be found in
path to a different disk. the message file.
IHS0403E The error log file name is not valid. Message Variables
message
Explanation Message ID to be issued.
The file name specified for the error log is not valid. message variable
File where the message was expected to be found.
System action
Operator response
Operator response
Change the error log file name with the IHSZSET tool.
IHS0404E An error log entry failed because
storage could not be allocated. IHS0411E A time out occurred while waiting
for all tasks to complete.
Explanation
Explanation
The error logging facility was unable to obtain system
memory. This condition occurs when a task ends abnormally
while logging a trace entry.
System action
System action
The trace buffer has been cleaned up and logged to
the disk.
Operator response
Free some storage by stopping other applications or by Operator response
adding storage to the system. Also, confirm that
swapping is enabled. Contact your system programmer.
IHS0405E An attempt was made to log a

trace entry that was larger than
the trace buffer. Contact IBM Software Support.
IHS0412E The path specified for the trace log
System action file does not exist. Create the
The system continues, but trace data is discarded. directory.
Contact your system programmer. The directory specified for the trace log does not exist.
System action
The log entry was not written to the trace log.

Operator response line. The operating system error
code is error code.
Either change the log file directory with the IHSZSET
tool, or create the specified directory.
Explanation
IHS0413E The trace log could not be opened
because too many files are already During internal processing, an operating system
open. Stop other applications in function call has returned an error code that was
the system. unexpected for the requested function.
Message Variables
Explanation module
The trace log cannot be opened because too many Module where error occurred.
files are already open. line
Line number within the module where error
System action occurred.
The log entry was not written to the trace log. error code
Error code returned by the operating system.
Operator response
System action
Stop other applications that are running in the system
until the error is corrected. The action being performed is cancelled.
IHS0414E The trace log file was not opened

Operator response
because the disk is full.
System action
Operator response IHS0420E The path specified for the message
Free some space on the disk or change the trace log log file does not exist. Create the
path to a different disk. directory.
IHS0415E The trace log file name is not valid.

Explanation
System action The directory specified for the message log does not
exist.
System action
Operator response
The log entry was not written to the message log.
Change the trace log file name with the IHSZSET tool.
IHS0416E An internal error occurred in Operator response
module at line number line Either change the log file directory with the IHSZSET
tool, or create the specified directory.
System action
IHS0421E The message log could not be
The action being performed is cancelled. opened because too many files are
already open. Stop other
Operator response applications in the system.
System action
System programmer response The log entry was not written to the message log.
IHS0419E An operating system error
occurred in module at line number
Stop other applications that are running in the system The command exit facility ends without completing the
until the error is corrected. command.
IHS0422E The message log file was not
opened because the disk is full. Operator response
When an out-of-storage condition exists, you can free
System action some storage by stopping other applications or by
adding storage to the system. Also confirm that
The log entry was not written to the message log. swapping is enabled. If you cannot resolve the error,
contact the system programmer.
Operator response
Free some space on the disk or change the message System programmer response
log path to a different disk. Check for an out-of-storage condition. If the condition
IHS0423E The message log file name is not does not exist, contact IBM Software Support.
valid. IHS0527E An error occurred while loading
the string table from the dynamic
System action load library dllname.
The log entry was not written to the message log.
Explanation
Operator response An error occurred while loading the string table from
Change the message log file name with the IHSZSET the specified dynamic load library.
tool. Message Variables
IHS0525E The command exit facility is dllname
ending due to a missing dll file. The name of the DLL that cannot be found.

The command exit facility cannot find either the Notify your system programmer. table-driven
IHSX.DLL file or the IHSUR.DLL file. Verify that the command exit.
$BINDIR/TDS/Server/bin directory is in the PATH.
System action
Ensure that the correct version of the dynamic load
The command exit facility ends without completing the library file is the first file of that name encountered in
command. the PATH statement. If this does not resolve the
Operator response IHS0528E An error occurred during
Contact your system programmer. semaphore initialization. Press
enter to terminate the command
System programmer response exit facility.
Verify that both IHSX.DLL and IHSUR.DLL exist in the

Explanation
path specified by PATH.
An internal error occurred during semaphore
IHS0526E The command exit facility is initialization in the table driven command exit.
ending due to an internal error.
Operator response
Explanation
Press Enter to end the table-driven command exit.
An internal error occurred in the command exit facility. Retry the command.
The cause of this error is normally related to
constraints on system resources, such as storage or
disk space. Detailed error information has been logged
to the topology server error log. Contact IBM Software Support.

IHS1000W Unable to connect to the topology Explanation
server at host hostname. You are not authorized, with the user name specified
in the User name field of the Sign On window, to sign
Explanation on to the topology server.
The topology console was unable to connect to the Message Variables
topology server at hostname. The host name might be
incorrect or the topology communication server is not username
running at the specified host. The name entered in the User name field of the
Sign On window.
Message Variables
hostname System action
The name entered in the Hostname field. The sign on request does not complete. The Sign On
window remains open.
System action
The sign-on request was not completed. The Sign On Operator response
window remains open. Do one of the following:
Operator response • Retry the sign on request, specifying a user name

that is authorized for NetView management console
Correct the host name and try to sign on again. If this sign on.
does not resolve the problem, contact your system
• Contact your system administrator.
programmer.
IHS1003I The user name and password are
System programmer response not authorized to connect to this
topology server. Make sure the
Ensure that the communications server has been user name and password are
started on hostname. If you cannot resolve the correctly specified.
IHS1001I User username is not authorized as Explanation
an administrator.
This error might be caused by any of the following:
Explanation • The user name is not defined to the topology server.

• The password is not correct for the specified user
You selected Administrator access when signing on to
name.
the topology server, but you are not authorized to act
as an administrator. • The user name is not a member of the tsadmn or
tsuser group at the server.
Message Variables
username System action
The name entered in the User name field.
The sign-on request does not complete. The Sign On
System action
The sign on request does not complete. The Sign On Operator response
Correct the user name or password and retry the sign-
on request.
Operator response
IHS1004I A session with host hostname is
Retry the sign-on request, but do one of the following:
already established.
• Specify a user name that is authorized for
administrator access. Explanation
• Do not select Administrator access.
The console has detected that a previous connection
IHS1002I User username is not authorized to to a topology server is still active.
sign on to the NetView Message Variables
management console.
hostname System programmer response
The name entered in the Hostname field.
Contact IBM Software Support if you are unable to
System action
IHS1007W An error occurred while sending a
The sign-on request does not complete. The Sign On request to the topology server.
Explanation
Operator response
An error was detected as a request was being sent to
Close and re-open the console and retry the sign-on the topology server.
request.
IHS1005I Host hostname is not known. System action
The request does not complete.
Explanation
hostname is not an existing host on the visible Operator response
network.
Contact your system programmer if you are unable to
Message Variables resolve the problem.
hostname
The name entered in the Hostname field. System programmer response
System action resolve the problem.
The sign on request does not complete. The Sign On IHS1008W The CLASSPATH environment
window remains open. variable does not include either
ihseuc.jar or ihseucd.jar. Correct
Operator response and restart the console.
CLASSPATH=classpath.
Correct the host name and retry the sign-on request.
IHS1006W The processing of a request at the Explanation
topology server was interrupted.
While initializing the topology console, the analysis of
Exception
the Java™ CLASSPATH definition did not locate the
required JAR file.
Explanation
Message Variables
A request sent to the topology server was interrupted
before the expected response was received. classpath
The CLASSPATH value when the console started.
Message Variables
exception System action
Additional exception text.
The console closes.
System action
Operator response
Operator response
If this was a sign-on request, the topology
communications server is running at the specified
host, but the topology server is not. IHS1010W The session with hostname was
Contact the system programmer if you are unable to lost; accurate information cannot
resolve the problem. be displayed. Select OK to sign off.

The communications session with the topology server The class value is obtained from the user's command
has unexpectedly disconnected. Any currently open profile. Check the command definition of the selected
views no longer correctly reflect the information at the command.
server.
IHS1018E Syntax to the IBM Z NetView
To resynchronize the views, sign off and sign on to the domain ID is not correct. Domain
server again. ID:"domainID"
Message Variables
Explanation
hostname
The host name of the server. The NetView domain ID contains incorrect syntax. The
domain ID must meet the following criteria:
System action • It must be between 1 and 5 characters in length.
You are signed off the topology console and all • The first character must be alphabetic (either upper
unsaved changes are lost. or lower case) or one of the following national
characters: @ # $.
Operator response • The remaining characters (second through fifth)
must be alphabetic (either upper or lower case),
Sign on to the server again.
numeric, or one of the following national characters:
IHS1011W Unable to start a Java application. @ # $.
Class: class Why: exception Phase: Message Variables
phase
domainID
Explanation The IBM Z NetView domain ID.
The specified Java application cannot be started. System action

Message Variables The console ignores the specified value.
class
The application's fully qualified Java class name. Operator response
exception Correct the domain ID and retry.
The Java exception that prevented the successful
start of the application. If exception is IHS1021W The request could not be
java.lang.NoClassDefFoundError, then the class completed because the topology
name that follows was not available at the server was unable to communicate
topology console. The software providing this class with IBM Z NetView.
might not have been installed at the console or
was not included in the CLASSPATH specification Explanation
when the console was started.
The topology server is unable to communicate with
phase IBM Z NetView, or IBM Z NetView is experiencing a
The specific phase in the Java application starting heavy workload and did not respond to the topology
process during which the exception was detected. server within a reasonable amount of time.
This value is intended for problem analysis, if
necessary.
System action
System action The request is ignored.
The class application is not started. The console

Operator response
continues.
If the problem persists, contact the system

Ensure that the communication session between IBM You must start the scope checker DUIFSSCO IBM Z
Z NetView and the topology server is started. If NetView task before you can issue this command. This
necessary, issue the NETCONV ACTION=START task performs scope checking, span checking, and
command from IBM Z NetView to start the alert history request support for the IBM Z NetView
communication session with the topology server. Graphic Monitor Facility host subsystem (GMFHS).
Determine if the IBM Z NetView, including Graphic
Monitor Facility Host System (GMFHS), is experiencing System action
a heavy workload.
IHS1022W The IBM Z NetView hardware
monitor encountered an error Operator response
while processing the request.
Start the DUIFSSCO task in IBM Z NetView. If
Explanation DUIFSSCO remains unavailable, contact your system
programmer.
IBM Z NetView encountered an error while processing
a request. System programmer response
System action Verify that the GMFHS interface to the scope checker
is available by issuing the GMFHS STATUS command
Data is not sent for the request. from the NetView operator. See IBM Z NetView
Command Reference Volume 1 (A-N) for information on
Operator response GMFHS operator commands.
Contact your system programmer. IHS1025W IBM Z NetView detected a
formatting error in the command
System programmer response sent from the topology server.
Check the IBM Z NetView log for error messages from

Explanation
the DUIFFSCO and BNJDSERV tasks. If you cannot
resolve the errors, contact IBM Software Support. The workstation submitted a command request the
host cannot recognize.
IHS1023W The IBM Z NetView GMFHS
encountered an error while
processing the request. System action
The error is logged in the GMFHS error log.
Explanation
The Graphic Monitor Facility host subsystem (GMFHS) Operator response
encountered errors while processing the request. Contact your system programmer.

Data is not sent for the request. Find the error report in the GMFHS error log and have
the information available when you contact IBM
Operator response Software Support.
Contact the system programmer. See the IBM Z NetView Troubleshooting Guide for
additional information.
System programmer response IHS1026W The request to the IBM Z NetView
Locate the error report in the GMFHS error log and task DUIFSSCO timed out.
have the information available when you contact IBM
Software Support. Explanation
See the IBM Z NetView Troubleshooting Guide for The request to the Tivoli NetView DUIFSSCO task has
additional information. timed out.
IHS1024W The IBM Z NetView task
DUIFSSCO is not active.

System action monitor-arguments
The optional argument list that, combined with
monitor-name, uniquely identifies the failing
monitor.
Operator response
resource-name
Retry the request. If the error occurs again, contact The name of the resource associated with the
your system programmer. failing monitor.

Increase the value of LCON-ALERT-CMD-TIMEOUT in The view is not updated with the current values for the
DUIGINIT, if necessary. See the IBM Z NetView specified monitors. The topology server continues to
Security Reference for information. periodically poll the specified monitors. The frequency
with which the server queries the selected monitors is
IHS1027W The user name and password are
set in the Polling Interval field on the Information page
not authorized to sign on to IBM Z
of the Resource Properties notebook.
NetView. Make sure the user name
and password are specified
correctly. Operator response
Do the following:
Explanation
• If the error occurs again when the polling interval for
This user name is not authorized to access IBM Z the resource expires, contact your system
NetView for one of the following reasons: programmer.
• The operator ID is not defined. • Use the Monitor Counts function to deselect the
failing monitors on the specified resources to avoid
• The password or password phrase is not correct.
the periodic display of this message. To do this,
• The password or password phrase is expired. select Monitor Counts For each of the resources
identified by the resource-name message insert,
System action then deselect the failing monitor, identified by the
monitor-name and monitor-argument inserts.
The request is not completed.

Operator response
You can find additional messages that describe the
Verify that you typed the user name and password or exact cause of this error in the ihsmessage.log file in
password phrase correctly, then try to sign on again. the topology server's LOG directory. Search the
IHS1028W An error occurred while querying ihsmessage.log file for a reference to message
one or more monitor counts. IHS2221I that identifies resource-name. Subsequent
monitor-name with arguments messages will detail the execution of the Query Task,
"monitor-arguments" on resource- any response from the Query Task, and the parsing of
name. the Query Task response by the topology server. These
messages will provide additional detail about the
error.
Explanation
Depending on the nature of the error, you might need
The topology server was unable to successfully query
to contact the provider of the instrumentation. For
the current value for one or more monitors selected
example, if the IHS22xx messages in the
with the Monitor Counts function.
ihsmessage.log indicate that the Query Task is
Message Variables returning a response that is not syntactically correct,
the provider of the instrumentation for the failing
At least one, but up to four, of the following can be
resource will need to correct the Query Task
displayed in one message:
implementation.
monitor-name
The name of the failing monitor. IHS1033W Unable to sign on to IBM Z
NetView. Null operator IDs are not
supported on this system.
Explanation IHS1035W Unable to sign on to IBM Z
NetView. The operator is not
You did not enter a user name in the Sign On window
logged on.
and one is required for your system.
Explanation
System action
This operator ID is not logged on IBM Z NetView.
The Sign On window displays again.
System action
Operator response
The Sign On window displays again.
Enter a valid user name and password or password
phrase.
Operator response
If you think that you received this message in error,
contact your system programmer or the person Log on to IBM Z NetView and try to sign on again.
responsible for security administration. IHS1036W The topology server is connected
to a IBM Z NetView system that
System programmer response does not support networking
If null operator IDs must be allowed on your system, views.
verify that the NULLGDSOPIDS keyword in DUIFPMEM
is set to YES. Explanation
IHS1034W IBM Z NetView has not responded The topology server is connected to a IBM Z NetView
to the topology server within the in which one of the following has occurred:
expected time period. 1. IBM Z NetView is not at the minimum software
level required to display networking views for the
Explanation current level of the NetView management console.
The topology server sent a request to IBM Z NetView. 2. GMFHS is not started.
A response was not received within the expected time 3. GMFHS and IBM Z NetView are not in
period. communication. For example, the DOMAIN of the
This message can occur if requests are temporarily NetView is not specified correctly to GMFHS.
overloading the server or the server is waiting on a
response from the host. System action
The request cannot be completed.
System action
If error occurred while signing on, the Sign On window Operator response
is displayed again. Otherwise the request is ignored.
Operator response
Retry the request. If the problem persists, contact
1. Ensure that the IBM Z NetView is running at the
same or later level than the NetView management
console.
2. Ensure that GMFHS is started.
Try the following: 3. Ensure that GMFHS contains the DOMAIN name of
• If you suspect that the server is running on a the IBM Z NetView program, where the NETCONV
computer that does not have enough speed or command was issued.
capacity, increase the size of the computer.
IHS1040W An error occurred while accessing
• Ensure that the networking links between the server TEC. Error: error
and IBM Z NetView are not overloaded.
• Ensure that the IBM Z NetView computer is not Explanation
overloaded.
An error was detected while trying to access Tivoli
Enterprise Console® for event services.

error Correct the value in the specified field.
The initial lines of the error that was detected.
IHS1052W You must enter a value in the field
field.
System action
The originating request is ignored. Explanation
Input is required in the specified entry field.
Operator response
Message Variables
resolve the problem. field
The name of the field which requires a value.
System action
Typically, error is either a Tivoli platform or Tivoli
Enterprise Console services message. Ensure that the The request is not processed.
topology server has adequate authorization to access
Tivoli Enterprise Console. The server message log Operator response
might contain additional information.
Enter a value in the specified field.
IHS1050W You must specify at least one type
IHS1053W An internal error has occurred.
column.
Exception: exception Method:
method
Explanation
No fields were defined for use as either display or sort Explanation
columns.
An unexpected error was detected.
Message Variables
Message Variables
type
exception
The type of column to be specified, for example a
The Java exception that was detected.
display column or sort column.
method
System action The method in which the exception was detected
and reported.
The properties are not saved.
System action
Operator response
The requested action does not complete.
Specify one or more fields to be used for the specified
column. Operator response
IHS1051W The value entered in the field field Retry the action. If the problem persists, contact your
is not valid. system programmer.

An improper value was entered in the specified field. Contact IBM Software Support if you are unable to
Message Variables resolve the problem.
field IHS1054W An error occurred while opening a

The name of the field which contains the improper file. File: file Type: type
value. Description: desc

The request is not processed. An error was detected while trying to open the
specified file at the topology server.
file An error was detected while writing to the specified
The name of the file being opened. file at the topology server.
The type of the file being opened.
file
desc The name of the file being written.
Optional additional description text.
type
The type of the file being written.
System action
desc
The requested file operation cannot be completed. Optional additional description text.

Retry the operation. Contact your system programmer The requested file operation cannot be completed.
if you are unable to resolve the problem.
Operator response
Retry the operation. Contact your system programmer
Check the server message log for additional if you are unable to resolve the problem.
information. Contact IBM Software Support if you are
unable to resolve the problem.
IHS1055W An error occurred while reading a Check the server message log for additional
file. File: file Type: type information. Contact IBM Software Support if you are
Description: desc unable to resolve the problem.
Explanation IHS1057W An error occurred in the topology

server. Data 1: data1 Data 2:
An error was detected while reading the specified file data2 Data 3: data3 Data 4: data4
at the topology server.
file An error was detected in the topology server while
The name of the file being read. processing a request.
The type of the file being read.
data1
desc Problem diagnosis data supplied by the server.
data2
Problem diagnosis data supplied by the server.
System action
data3
The requested file operation cannot be completed. Problem diagnosis data supplied by the server.
data4
Operator response Problem diagnosis data supplied by the server.
Retry the operation. Contact your system programmer
if you are unable to resolve the problem. System action
The requested action cannot be completed.
Check the server message log for additional Operator response
information. Contact IBM Software Support if you are
unable to resolve the problem.
IHS1056W An error occurred while writing a
file. File: file Type: type
Description: desc

Check the server message log for additional Check the server message log for additional
information. Contact IBM Software Support if you are information. Contact IBM Software Support if you are
unable to resolve the problem. unable to resolve the problem.
IHS1058W The value entered in the field field IHS1070W The data for window command
must be in the range min to max. was not found.
The value in field is not within the required range. The expected data required to construct the command
dialog window was not received from the topology
Message Variables
server.
field
Message Variables
The name of the field containing the incorrect
value. command
min The name of the command selected from the
The minimum value for the field. resource context menu.
max
System action
The maximum value for the field.
The dialog window for the command is not displayed.
System action
Operator response
The properties are not saved.
Operator response resolve the problem.
Correct the value in the specified field so that it falls

within the given range.
Check the server message log for additional
IHS1059W An error occurred while deleting a
information.
file. File: filename Type: type
Description: desc If command is a TME library task, verify its definition.
Explanation resolve the problem.
An error was detected while deleting the specified file IHS1071W The command string is null.
at the server.
Explanation
Message Variables
The command string in the dialog window contains no
file
text.
The name of the file being read.
type
System action
The type of the file being read.
desc The send request is ignored.
Operator response
System action Enter data in the dialog window, then retry the send
The requested file operation cannot be completed. request.
IHS1072W The resource was not found.
Operator response
Retry the operation. Contact your system programmer Explanation
if you are unable to resolve the problem. The resource list for the selected GUI component
contained no entries. This might not be a problem if
the task performed a dynamic query and no
appropriate resources were found.
System action • The number of items in the default value is not a
multiple of 3.
The resource list is not displayed. The dialog remains
open. • Too many items were supplied.
• The operator value is out of the range 0-11.
Operator response • The severity value is out of the range 0-5.
Contact your system programmer if you are unable to value
resolve the problem. The default value that was not correct.

Rerun the task from the Tivoli desktop. Compare its The dialog is displayed, but the default for threshold is
resource list contents with this dialog. If necessary, ignored. threshold is displayed with an empty
check the TME task library definition for the command threshold value.
selected from the resource context menu. Contact
IBM Software Support if you are unable to resolve the
Operator response
problem.
IHS1073W Too much text has been entered in
the field field. This field allows a
maximum of length characters. System programmer response
Check the TME task library definition for the command
Explanation selected from the resource context menu.
You have entered too many characters in field. A threshold default value is specified as a comma
delimited list of one to six threshold triplets. Each
Message Variables triplet consists of the following:
field 1. A threshold value
The name of the text field in which too many
characters were entered. 2. A relative operator enum value
length 3. A severity enum value
The maximum number of characters that can be Contact IBM Software Support if you are unable to
entered in field. resolve the problem.
IHS1075W The specified value is not correct.
System action
Threshold: threshold Severity:
The request is not processed. severity Reason: reason

Specify fewer characters in the appropriate field. The value entered in the severity value cell is not
correct.
IHS1074W The default value that was
supplied is not correct and will be Message Variables
ignored. Threshold: threshold
threshold
Reason: reason Value: value
The name of the threshold.
severity
Explanation
The specific severity row.
The default value supplied for the threshold is not reason
correct and will be ignored. One of the following:
Message Variables • There is no input for this specified operator.
threshold • There is a comma in the input value.
• The length of value string exceeds the required
reason number.
One of the following:

The send request is not processed. The topology server did not find the requested view.
This can happen for one of the following reasons:
Operator response • A lower-level view cannot be dynamically created
Correct the severity cell and retry the send request. • If the view is from IBM Z NetView and you selected a
configuration view or a more detailed view, the
IHS1076W All operators are "Not used." At
RODM definitions do not exist for that type of view
least one must be specified.
Threshold: threshold • If you selected Locate Failing Resources, all real
resources have a satisfactory status
Explanation • If the view is from IBM Z NetView, IBM Z NetView
has an out-of-storage condition
All values in the operator column cannot be set to "Not
Used" at the same time. • You might not have span authorization to the view
itself or to resources within the view
Message Variables
threshold System action
System action
Operator response
The send request is not processed.
Contact your system programmer if the view exists.
Operator response
Specify at least one threshold operator cell value and
Do one of the following:
retry the send request.
• Determine if the view exists on the server. If not,
IHS1077W The value entered in the field field create it.
is not valid. Value: value Pattern:
pattern • For GEM instrumented views, ensure that the AMS
definition files are correctly created.
Explanation • For IBM Z NetView views, if the RODM definitions do
not exist, create the RODM definitions.
The value entered in the text field is not valid. The
value must match the required pattern. • If the IBM Z NetView operator console messages
indicate a storage shortage, correct the problem.
Message Variables
• If the IBM Z NetView operator console messages
field indicate that a timeout has occurred, try to increase
The text field containing the incorrect value. the View Request Timeout Value specified in
value DSICTMOD at the status focal point. Increasing this
The value entered. value allows the resource status manager to wait
longer before it sends a view list back to the server.
pattern After increasing the value, retry the request.
The regular expression that the input must match.
IHS1081I Resource resourcename already
System action exists in this view.
The command is not sent.

Explanation
Operator response You cannot move or copy this resource to the target
view it already exists in that view.
Enter a valid value in the text field.
Message Variables
IHS1080I The requested view was not
resourcename
found.
The name of the duplicate resource.
The resource is not moved or copied. The current look of the topology console window is
saved, as well as any windows you have detached with
IHS1082W Do you want to save changes to the Tear Away functions. This selection overrides the
view viewname? save setting you have specified on the General page of
the Console Properties notebook.
Explanation
The following things are saved:
You have made customization changes to a view and
one of the following has happened: • Window positions
• Window sizes
• You have closed the view without saving your
changes to the topology server. • Slider positions
• The view has received an update from the server • Display and tear away selections on the View menu
before you saved your changes. If you use the Save Preferences on Exit function, the
• You have signed off or exited the topology console next time you sign on to the topology console, you can
before saving your changes. specify whether you want these saved settings
restored. You can continue to restore these settings
If you choose not to save your changes, all changes
until they are overwritten by another save action.
are lost.
viewname The current look of the console window and any
The name of the view to be saved. windows you have detached with the Tear Away
functions are saved when you exit.
System action
• If Yes is selected, the changes to the view are saved Operator response
to the server before being closed, or before updates If you want to toggle your selection, select Save
are applied to the view. Preferences on Exit again.
• If No is selected, the changes to the view are not If you want to prevent this message from displaying
saved. whenever you change your Save Preferences on Exit
selection, select Do not show this dialog again. This
Operator response prevents the message from displaying for any future
• Select Yes to save your changes. changes to the Save Preferences on Exit selection.
• Select No to discard your changes. IHS1085I You have requested not to have
your window characteristics saved
IHS1083W You cannot copy or move text to when you exit. In order to
another view. preserve this state, you must set it
in the Console Properties
Explanation notebook.
You have attempted to copy or move text from one
view to another. This is not allowed. Explanation
The current look of the console window is not saved,
System action nor are any windows you have detached with the Tear
The operation is not completed. Away functions. This selection overrides the save
setting you have specified on the General page of the
IHS1084I You have requested to save your Console Properties notebook.
window characteristics when you
The following things are not saved:
exit. In order to preserve this
state, you must set it in the • Window positions
Console Properties notebook. • Window sizes
• Slider positions
• Display and tear away selections on the View menu

System action are not. If you select Cancel, the requested action is
canceled.
The current look of the console window and any
windows you have detached with the Tear Away
functions are not be saved when you exit. Operator response
Initially, all of the changed views in the list are
Operator response selected. Deselect any views whose changes are not to
be saved, then do one of the following:
If you want to toggle your selection, select the Save
Preferences on Exit option again. • Select Save Selected Views to save the selected
views and continue the requested action.
If you want to prevent this message from displaying
whenever you change your Save Preferences on Exit • Select Save None to discard all of the changes and
selection, select Do not show this message again. This continue the requested action.
prevents the message from displaying for any future • Select Cancel to cancel the requested action.
changes to the Save Preferences on Exit selection.
IHS1092I You have requested to close view
IHS1086W You must have administrator viewname. It is the parent of at
access to perform this operation. least one other open view. You
must close these descendant
Explanation views first.
You have attempted an operation that requires
administrator access. Explanation
You have attempted to close a view that has one or
System action more child views still open.
The operation is not completed. Message Variables
viewname
Operator response The name of the view you are attempting to close.
To perform the desired operation, you must be
authorized as an administrator and request System action
Administrator access when you sign on.
The view is not closed.
IHS1088W You cannot copy or move
resources to another view. Operator response
First close any open views that are descendants of the
Explanation view you are attempting to close, then close the parent
You have attempted to copy or move resources from view. You can determine which views are descendants
one view to another. This operation is not allowed at by looking for the parent view in the available view tree
this time. and then checking child "branches" underneath the
parent view.
System action IHS1093W Do you want to remove all
The copy or move is not completed. customization changes from view
viewname?
IHS1090I These views have been modified.
Select the view(s) you want to Explanation
save.
You have requested to remove all changes from the
customized version of viewname. This is a
Explanation
confirmation to verify the requested action.
The views in the list have been modified. You must
Message Variables
specify which changes you wish to save.
viewname
System action The name of the customized view.
If you select Save Selected View, the requested

changes are saved. If you select Save None, changes
• If Yes is selected, all customization changes are • Select Yes if you want to run the command.
deleted and the view will be replaced with the • Select No if you do not want to run the command.
version currently defined at the topology server.
IHS1096W An update or refresh is pending for
• If No is selected, no action is taken.
view view name. Do you want to
save changes to this view before
Operator response refreshing?
• Select Yes to remove all customization from this
view. Explanation
• Select No to preserve the customization. A view with unsaved customization changes has
IHS1094W Do you want to delete resource received an update or a refresh request. You can save
from all views? your changes and merge them with the update prior to
the refresh, or discard the changes.
You have chosen to delete a resource from all views. view name
This is a confirmation to verify the requested action. The name of the view for which a refresh is
This action deletes the resource from the topology pending.
server and removes it from all views that contain it.
resource • If Yes is selected, changes are saved. The view is

The name of the resource to be deleted. refreshed immediately after the changes are merged
with the current state of the view.
System action • If No is selected, the view is refreshed immediately
and any changes are discarded.
• If Yes is selected, the resource is deleted from the
server. All views containing the resource receive an
Operator response
update.
• If No is selected, no action is taken. • Select Yes to save your changes before the view is
refreshed. The view is refreshed as soon as your
changes are merged.
Operator response
• Select No to refresh the view now and discard your
• Select Yes to remove the resource from the server changes.
and from all views.
IHS1097W The server is unable to delete
• Select No to keep the resource.
resource resource name.
IHS1095W You have requested to run
command. Do you wish to Explanation
proceed?
A request to delete a resource from the topology
server was unsuccessful.
Explanation
Message Variables
You have selected to run command. The command
profile definition of this command specifies that its use resource name
be verified whenever it is issued. The name of the resource that cannot be deleted.
Message Variables
System action
command
The command selected from a context menu. Processing continues after OK is selected. The
resource is not deleted.
System action
Operator response
• If Yes is selected, the specified command is run.
Select OK to continue. Contact your system
• If No is selected, the specified command is not run. programmer.

Check the server for error messages to determine why The server database has been modified in a manner
the resource cannot be deleted. that might have caused some stored console
preferences to be lost.
IHS1098W The topology server is unable to
remove all customization changes
from view view name. System action
Some stored console preferences might have been
Explanation lost.
An attempt to remove all customization changes from
the view was unsuccessful. Operator response
Message Variables If any preferences were lost, reconfigure the console

and save preferences.
view name
The name of the view from which customization IHS1101I The selected views have been
changes cannot be removed. saved. Do you wish to action now?
Processing continues after OK is selected. The All selected views have been saved.
customization changes remain. Message Variables
action
Operator response
The action you wish to continue or stop; either Exit
Select OK to continue. Contact your system or Sign off.
programmer.
System action
• If Yes is selected, you will continue to exit or sign off.
Check the topology server for error messages to • If No is selected, you are returned to the console
determine why the customization changes cannot be window.
deleted.
IHS1099I All resources have been deleted Operator response
from view view name. This view
Select Yes to sign off or exit, or No to return to the
will be closed.
console window.
Explanation IHS1104W There are connections that cannot

be displayed because of collapsed
An open view has had all resources deleted from it and nodes.
is no longer a valid view. The view is closed after OK is
selected.
Explanation
Message Variables
You requested to show connections for a particular
view name object in the Verify view. However, at least one
The name of the view from which all resources connection points to an object that is not currently
have been deleted. visible in the Verify view because nodes have been
collapsed.
System action
System action
The view is closed.
Some connections are not displayed.
IHS1100W Not all stored preferences were
restored because the topology
server database has changed. Operator response
To see all connections, expand your nodes and
request to show the connections again.
IHS1105W There are outstanding requests. System programmer response
There must not be any outstanding If the resource is a IBM Z NetView RODM resource,
requests before switching modes. check the RODM definitions to make sure the resource
Select Yes to cancel all requests.
is properly defined.
Select No to allow requests to
complete. IHS1108W Resource resource was not located
in any view and extended search
Explanation cannot be performed.
You attempted to switch into or out of the a life cycle

Explanation
mode while there were outstanding requests to the
server or tasks in process. Either the SNA topology manager is inactive, or GMFHS
timed out while waiting for a response from the
System action manager.
If you select Yes, all outstanding requests and tasks Message Variables
are canceled and the mode is switched. If you select resource
No all requests and tasks continue running and you The resource name specified in the Locate
remain in the current mode. Resource window.

Select Yes to cancel all outstanding requests and tasks GMFHS cannot provide a view. It is possible that
and switch modes. Select No to keep requests and another view source might provide a view to satisfy
tasks running and remain in the current mode. your request.
IHS1107W Resource name was not located in
any view. Operator response
If you know the name of the manager that is registered
Explanation with RODM, check for its presence or status in the
A view that satisfied your Locate Resource request Topology Display Subsystem view.
was not found. Possible explanations for this message
are: System programmer response
• The resource name was not entered correctly. Ensure that the SNA topology manager is active. If
necessary, increase the GMFHS timeout value. This is
• If this is a RODM resource, the resource might not
controlled by the LCON-SNATM-TIMEOUT statement
have the proper connectivity relationships defined.
in initialization member DUIGINIT. You might also
See the IBM Z NetView Resource Object Data
need to increase the workstation timeout value. Refer
Manager and GMFHS Programmer's Guide for more
to the NGMF documentation for more information on
information.
customizing the workstation timeout values.
• The resource is a SNA LU that does not currently
exist in RODM. IHS1109W An unknown exception was
received from the topology server.
Message Variables ID: id Data 1: data1 Data 2: data2
name Data 3: data3 Data 4: data4
The resource name specified in the Locate
Resource window Explanation
An exception was received from the server. The
System action topology console does not recognize the exception.
The locate request is not completed. Message Variables
Operator response id
Topology server exception ID.
Retry the request and correct the resource name. If
data1
applicable, select the Extended search checkbox.
If the problem persists, contact your system
programmer.

data2 System programmer response
If the IBM Z NetView operator console messages
data3 indicate that a storage shortage exists, correct the
Problem diagnosis data supplied by the server. problem.
data4 IHS1112I The view list created for this
request may not be complete.

Contact your system programmer. The view list created might not show all of the views
that actually contain the resource. This can happen for
System programmer response one of the following reasons:
Contact IBM Software Support. • The GMFHS found more views than can be returned
in one request, so the view list was truncated.
IHS1110W You requested to clear number
suspended resources. Do you wish • A RODM method failed while creating a view.
to proceed? • One or more view names in RODM are too long.
• IBM Z NetView has an out-of-storage condition.
Explanation
You have selected a number of resources to clear. You System action
are requested to verify your request.
The view list is displayed.
Message Variables
number Operator response
The number of resources elected. Contact your system programmer.

If you select Yes, the suspended flags of the resources Check for one or more of the following:
are cleared. If you select No, the suspended flags are
not cleared and the List Suspended Resources window • If the IBM Z NetView operator console messages
is displayed again. indicate that a storage shortage exists, perform any
required error recovery.
Operator response • For performance reasons, no more than 12 views are
returned in a view list, unless you customized the
Select Yes to clear the suspended flags of the selected LCON-MAX-LOCATE-RESOURCE-VIEWS parameter
resources. Select No if you do not want to clear the in DUIGINIT. However, it is possible to receive a
suspended flags. You will return to the List Suspended partial view list with fewer than 12 views. This might
Resources window. happen if views have a missing view information
IHS1111W The view created for this request object and cannot be opened. If you suspect that a
may not be complete. view is missing for this reason, check the RODM log
for specific information. This can help you determine
which view is in error, so you can correct the
Explanation
problem.
The view created might not show one or more • If you receive this message and there are 12 views in
resources. This can happen if IBM Z NetView has an the lists, increase the number of views returned to
out-of-storage condition. the server by GMFHS. Increasing this number might
cause timeouts on the server.
System action
• If a RODM method failed while creating a view,
The partial view opens. check the GMFHS and RODM logs for specific
information about the method failure.
Operator response To determine which view in the list encountered a
Contact your system programmer. method failure, do the following:
1. Select the GMFHS views in the list.
2. Open the views. System action
IHS1113W is displayed for the view containing the If this is the first time you are attempting to open the
method failure. view, the view does not open. If you are attempting to
• The value of the MyName field of objects in the refresh the view, the view closes.
Network_View_Class and the
Configuration_Peer_View class are limited to 32 Operator response
bytes. You can increase the DUIGINIT value. Record the information in the message window and
However, increasing the value can cause timeouts at contact your system programmer.
the workstation.
IHS1113W A RODM method failed while System programmer response
creating view. Notify the system
Check the RODM log for information about the objects
programmer responsible for
that are not defined and define the missing objects.
RODM.
See the IBM Z NetView Resource Object Data Manager
Explanation and GMFHS Programmer's Guide and the IBM Z
NetView Troubleshooting Guide for more information.
A RODM method failure occurred during the creation of
the view. IHS1115W A layout error was detected while
processing view. Layout code: code
view
Notify the system programmer
The view name.
responsible for RODM.
If this is the first time you are attempting to open the
view, the view does not open. If this occurs while Explanation
refreshing the view, the view closes.
The view was successfully created and transferred to
the server. A layout error occurred while positioning
Operator response
resources according to their LayoutType attributes.
Record the information in the message window and
Message Variables
contact your system programmer.
view
System programmer response The name of the view.
Check the GMFHS and RODM logs for specific code

information about the method failure. This information The specific layout error code.
is needed to isolate and correct any RODM definition
error. Correct any RODM errors. System action
See IBM Z NetView Troubleshooting Guide for more If this is the first time you are attempting to open the
information. view, the view does not open. If this occurs while
IHS1114W Objects required to create view are
not defined. The RODM view
Operator response
definition is incomplete or in error.
Notify the system programmer Record the information in the message window and
responsible for RODM. contact your system programmer.

The RODM definition for the view is incomplete or in 1. See the following list of error codes for the
error. explanation of the detected problem. Use the
LC_RC_xxxx value as the look-up key. If the error
Message Variables
code is not listed in the table, contact IBM Software
view Support.
The view name. 2. See the IBM Z NetView Resource Object Data
Manager and GMFHS Programmer's Guide for a
mapping of layout utility to RODM terminology.

3. Correct the layout attribute in the RODM definition LC_RC_TOO_MANY_LINKS_HIER
for the view. A view with LayoutType set to six contains more
than the maximum number of links.
LC_RC_BAD_BUS_CONNECTION
A view with LayoutType set to five contains a node LC_RC_TOO_MANY_LINKS
that is connected to the bus node by multiple links, A view contains more than the maximum number
or a node connected to the bus node in addition to of links.
other nodes on the main site circle. LC_RC_TOO_MANY_NODES_ELLIPSE
LC_RC_BAD_LAYOUT_TYPE A view with LayoutType set to seven contains more
The LayoutType field contains a value that is not than the maximum number of nodes.
valid. LC_RC_TOO_MANY_NODES_CON_TREE
LC_RC_BROKEN_TOKEN_RING A view with LayoutType set to eight contains more
A view with LayoutType set to four has nodes on than the maximum number of nodes.
the main site circle that do not form a complete LC_RC_TOO_MANY_NODES_HIER
ring. Note that this condition might also generate A view with LayoutType set to six contains more
the return codes than the maximum number of nodes.
LC_RC_INVALID_FIRST_NODE_ID or
LC_RC_TOO_MANY_NODES_RADIAL
LC_RC_BROKEN_TOKEN_RING.
A view with LayoutType set to one, two, three,
LC_RC_INSUFF_MEMORY four, or five contains more than the maximum
The requested function cannot complete because number of nodes.
of insufficient free memory.
LC_RC_TOO_MANY_NODES
LC_RC_INVALID_BUS_NODE_ID A view contains more than the maximum number
BusNode specified a node that was not in the view. of nodes.
LC_RC_INVALID_FIRST_NODE_ID LC_RC_TOO_MANY_TEXTS
FirstNode specified a node that was not in the view The view exceeds the maximum number of text
or on the main site circle. This condition might also strings.
be caused by a broken main site circle or a view
LC_RC_VIEW_TOO_COMPLEX
with multiple rings.
The view is too complex for the layout function.
LC_RC_INVALID_LINK_OPT Reduce the total number of links, tackpoints, and
LinkCrossOption is not in the range of zero to six. nodes in the view.
LC_RC_INVALID_SECOND_NODE_ID
IHS1116I The list created for this request
SecondNode specified a node that was not in the
may not be complete.
view or on the main site circle. This condition
might also be caused by specifying a node that is
not connected to the first_node_id node. Explanation
LC_RC_MULTI_TOKEN_RINGS The list created for your request might not show all
A view with LayoutType set to four contains possible values. Possible reasons for this are:
multiple token rings that are interconnected. • GMFHS is not currently available, so information
LC_RC_OVERFLOW about RODM resources cannot be included.
The area required to lay out the view overflows the • The topology server timed out while waiting for a
current coordinate system. Reduce the number of response from GMFHS.
nodes, links, and tackpoints in the view, or reduce
the field in the VS_SEG_HEADER. • The session between the topology server and IBM Z
NetView has ended.
LC_RC_TOO_MANY_LINKS_RADIAL
A view with LayoutType set to one, two, three,
four, or five contains more than the maximum System action
number of links. The requested action continues, but some expected
LC_RC_TOO_MANY_LINKS_CON_TREE information will not be available.
A view with LayoutType set to eight contains more
than the maximum number of links. Operator response
LC_RC_TOO_MANY_LINKS_ELLIPSE This problem might occur because the Tivoli NetView
A view with LayoutType set to seven contains more OST task was stopped while the request for data was
than the maximum number of links. being processed. The OST task is the task used by the
NETCONV command to establish a session between
IBM Z NetView and the server. If necessary, restart the System action
OST task and re-issue the NETCONV command.
If this is the first time you are attempting to open the
If this does not fix the problem, contact your system view, the view does not open. If this occurs while
programmer responsible for GMFHS or for the session refreshing the view, the view closes.
between the topology server and IBM Z NetView.
IHS1117I The layout parameters specified Operator response
for view are not correct. Default Record the information in the message window and
layout parameters have been contact your system programmer.
used. Notify the system
programmer responsible for System programmer response
RODM.
Check the GMFHS and RODM logs for specific
Explanation information about which layout parameters are not
correctly specified. Correct the RODM definition error.
The layout parameters specified in RODM for the view See the IBM Z NetView Resource Object Data Manager
are not correct. Default parameters have been and GMFHS Programmer's Guide and the IBM Z
automatically substituted. NetView Troubleshooting Guide for more information.
Message Variables IHS1119W Objects required to create view are
view in error. Notify the system
The name of the view. programmer responsible for
RODM.
System action
Explanation
The view created with default layout parameters
opens. The view cannot be created because an error was
detected in a RODM class, object, or attribute
specification.
Operator response
Message Variables
contact your system programmer. view
The view name.
System action
information about which layout parameters are not If this is the first time you are attempting to open the
correctly specified. Correct the RODM definition error. view, the view does not open. If this occurs while
and GMFHS Programmer's Guide and the IBM Z
NetView Troubleshooting Guide for more information. Operator response
IHS1118W The layout parameters specified Record the information in the message window and
for view are not correct. The view contact your system programmer.
cannot be created. Notify the
system programmer responsible System programmer response
for RODM. Check the IBM Z NetView GMFHS and RODM logs for
specific information about which class, object, or
Explanation attribute is not correctly specified. Correct the RODM
The layout parameters specified in RODM for the view definition error.
are not correct. Default parameters cannot be IHS1120I The view created is not complete.
automatically substituted. Notify the system programmer
Message Variables responsible for RODM.
view
Explanation
The view name.
The view created will not display all RODM-defined
resources for one of the following reasons:

• The view contained more resources than allowed by reason code
the RODM ObjectSetCriteriaCount attribute. The reason code supplied by the server.
• The view contains more than the maximum allowed
number of nodes or links. System action
The reason code is ignored. The request processing
System action continues, but functions might be disabled.
The view opens, but it does not include all possible
resources. Operator response
Operator response
Contact your system programmer. System programmer response
IHS1123I A RODM method failed while
Do one or both of the following: creating the view_name view
• Increase the RODM ObjectSetCriteriaCount
attribute. Explanation
• Reduce the number of nodes or links in the specified A RODM method failure occurred during the creation of
view to the allowed maximum. the view. The view is too large and complex to open.
Notify the system programmer responsible for RODM.
IHS1121I The resource does not support this
view request. Message Variables
view_name
Explanation The view name
IBM Z NetView GMFHS cannot create a view for this
request on a particular resource. The RODM class System action
definition for this resource does not include the
If you are trying to open the view, the view does not
requested view type.
open. If you are trying to refresh the view, the view
closes.
System action
If this is the first time you are attempting to open the Operator response
view, the view does not open. If this occurs while
contact your system programmer.
Operator response
Reduce the size and complexity of the view by
reducing the number of nodes or links in the specified
System programmer response view to the allowed maximum.
Check the GMFHS and RODM logs for specific See the ObjectSetCriteriaCount information in the IBM
information about which class, object, or attribute Z NetView Data Model Reference for details on view
caused the problem. To support the view type, add the limits.
appropriate VIO to the RODM definition. If necessary,
correct the RODM definition error. IHS1132W A general processing exception
was received from the topology
IHS1122W An unknown reason code was server. ID: id Data 1: data1 Data 2:
received from the topology server. data2 Data 3: data3 Data 4: data4
RC: reason code
Explanation
Explanation
A general processing exception was received from the
The reason code returned by the server was not an server.
expected value.
Message Variables
Message Variables
id System action
The topology server exception ID.
Whether the view is deleted depends on where the
data1 error occurred. If the view still displays in the business
Problem diagnosis data supplied by the server. tree, it was not completely deleted from the server
data2 databases.
Problem diagnosis data supplied by the server. If the view does not display, it was completely
data3 deleted.
data4 Operator response
Problem diagnosis data supplied by the server. Contact your system programmer.

Contact your system programmer. Save the server error log and contact IBM Software
Support.
IHS1135W An error occurred while saving
Contact IBM Software Support. view.
IHS1133W The topology server could not
complete the request because of Explanation
insufficient memory. An error occurred while saving a customized view.
A request to allocate either system or topology view

communication server memory failed. The requested The name of the view being saved.
memory resource is exhausted.
System action
System action The request is ignored.
The topology server closes.
Operator response
Operator response Retry the request. If the problem persists, contact
Record the information from the message window. Try your system programmer.
the following at the server workstation: System Operator Response: Contact IBM Software
• Close unnecessary applications to free system Support.
memory. IHS1136W You have requested to delete
• Close all topology server applications (including resource. This will also delete any
command exits) to free server memory. contained resources and cannot
• Free disk space by deleting files that are no longer be undone. Any affected view will
required. be saved with the resource
deleted. Do you wish to proceed?
• Install more memory.
IHS1134W An error occurred while deleting Explanation
view. You selected to delete a resource. If the resource
contains other resources (for example, a subsystem
Explanation that contains applications), the contained resources
An error occurred while deleting a view from the will also be deleted.
topology server databases.
System action
Message Variables
If Yes is selected, the resource and all contained
view resources are permanently deleted. The delete
The name of the view being deleted. operation cannot be undone.

Operator response IHS1139W You have requested to delete the
component type component type.
Select Yes to delete the resource and all contained
Any instances of this component
resources. Select No if you do not want to delete the
type will be changed to the
resource.
Undefined generic component
IHS1137W A newer version of one or more type. Do you want to proceed?
files is required to communicate
with this topology server. You Explanation
must download the newer version
before you can sign on. Choosing You have requested to delete the specified component
"No" returns you to the Sign On type.
window. Do you want to update to Message Variables
the newer version now?
component type
The name of the component type.
Explanation
To sign on to the specified server, you must update the System action
files to the newer version.
If the user selects Yes, the application type is deleted.
All existing applications that use this application type
System action
will change to the default type. The delete operation
If you select Yes, the newer version of the files is cannot be undone.
installed from the server. The console is recycled and
If the user selects No, the application type is not
the Sign On window is redisplayed.
deleted.
If you select No, the files are not updated and you are
returned to the Sign On window. Operator response
Operator response
• Select Yes to delete the specified application type.
Select Yes if you want to update the files and sign on
to the specified server. Select No if you do not want to • Select No if you do not want to delete the specified
update the files. application type.
IHS1138W You have requested to delete the IHS1140W Application type name cannot be
last subsystem in this business deleted because it is currently
system. This will delete the reference by one or more open
business system. Do you wish to views. Close all views that contain
proceed? this application type, then retry
the Remove operation.
Explanation
Explanation
Business systems must contain at least one
subsystem. You have selected to delete the last You selected to delete an application type that is
subsystem in the business system, which will also currently referenced by one or more open views.
delete the business system.
System action
System action The specified application type is not deleted.
If Yes is selected, the subsystem and its parent
business system are deleted. The delete operation Operator response
cannot be undone.
Close all views that contain the application type, then
retry the delete operation.
Operator response
IHS1141W You have deselected the
Select Yes to delete the subsystem and its parent
Aggregate checkbox. Any
business system. Select No if you do not want to
aggregate views and their
delete the subsystem.
contained resources will be
deleted. You cannot undo this Explanation
action. Do you wish to proceed?
You attempted to create a connection with the same
application as both source and target.
Explanation
You deselected the Aggregate checkbox, then selected System action
to save the application. If the application contains any
You are returned to the properties window.
aggregate views, those views and all contained
resources will be deleted.
Operator response
System action Ensure that the source and target applications are
different.
If you select Yes, the application is no longer an
aggregate and all aggregated views and their IHS1145W There must be at least two
contained resources are deleted. The delete operation applications in the current view
cannot be undone. before a connection can be
created.
Operator response
Explanation
Select Yes to specify that the application is no longer
and aggregate and to delete the aggregated views. You attempted to create a connection, but there are
Select No to return to the properties window. less than two applications in the current subsystem.
IHS1142W Properties have been changed. Do
you want to save the changes? System action
You are returned to the console.
Explanation
You changed the properties for a resource, then Operator response
selected to cancel or close the window without saving Ensure that there are at least two applications in the
changes. current subsystem before creating a connection.
IHS1146W Aggregate name already exists.
System action
If you select Yes, the changes are saved. If you select Explanation
No, the changes are discarded. If you select Cancel,
you are returned to the properties window. The specified aggregate name exists. Only one
aggregate can exist with that name.
Select Yes to save the changes. Select No to discard name
the changes. Select Cancel to return to the properties The name of the aggregate.
window.
IHS1143W A required field is empty. System action
You are returned to the console.
Explanation
No data was entered in a required field. Operator response
Specify a different aggregate name.
System action
IHS1147W Aggregate name already exists.
You are returned to the properties window. The resources were not added.

Ensure that all required fields are filled in. The specified aggregate already exists. Only one
aggregate can exist with that name.
IHS1144W The source and target cannot be
the same application. Message Variables

name Operator response
The name of the aggregate.
Select Yes if you want the Export file name and
Product fields updated with the new name. Select No if
System action you do not.
You are returned to the console. The resources are not IHS1151I The specified directory directory
added. name does not exist. Do you wish
to create it?
Operator response
Specify a different aggregate name. Explanation
IHS1148W The aggregate no longer exists. The directory specified in the Export window does not
exist.
The aggregate has been deleted. directory name
The directory name that does not exist.
System action
System action
The resource is not added to the aggregate.
If you select Yes, the directory is created. If you select
Operator response No, the operation is canceled and you are returned to
the Export window.
Create the aggregate or add the resource to another
aggregate.
Operator response
IHS1149W Application name cannot be Select Yes to create a directory with the specified
deleted because it has name. Select No to cancel the operation and return to
connections to other applications. the Export window. .
Explanation IHS1152I The specified file filename already

exists. Do you wish to overwrite it?
You attempted to delete an application that still has
connections to other applications.
Explanation
System action The file specified in the Export window already exists.
You are returned to the console. Message Variables

filename
Operator response The name of the file that already exists.
Delete all connections to the application, then try to
delete the application. System action
IHS1150W You have changed the name of this If you select Yes, the file is overwritten. If you select
item. Do you want the "Export file No, the operation is canceled and you are returned to
name" and "Product" fields the Export window.
updated with the new name?
Operator response
Explanation Select Yes to overwrite file. Select No to cancel the
You changed the name of the item. You can have the operation and return to the Export window.
Export file name and Product fields automatically IHS1153W Any existing business definition
updated with the new name, if you desire. files in the directory directory
name will be overwritten. Do you
System action wish to continue?
If you select Yes, the Export file name and Product
fields are updated with the new name. Otherwise, they
are not.
Explanation must close these properties
windows first.
If any BDF files with the same file names as the ones
being written out exist in the specified directory, they
will be overwritten. Explanation
Message Variables The view that you have requested to close has one or
more properties windows open. These windows must
directory name be closed before you can close the view.
The name of the directory containing the BDFs.
Message Variables
System action view
The name of the view you requested to close.
If you select Yes, files might be overwritten. If you
select No, the operation is canceled and you are
returned to the Export window. System action
The view is not closed.
Operator response
Select Yes to continue. Files might be overwritten. Operator response
Select No to cancel the operation and return to the Close all properties windows associated with the view,
Export window. then close the view.
IHS1154I A product incompatibility exists IHS1156E Unable to create a Monitor view
between the console and the due to missing or corrupt data in
server. The console product is the filename file.
consoleproduct. The server
product is serverproduct.
Explanation
Explanation The file used to store resource information has missing

or corrupt information. This can be the result of
The topology console cannot connect to the topology manual editing of the file.
server because of a product incompatibility.
Message Variables
Message Variables
filename
consoleproduct The name of the affected data file.
The product name of the console.
serverproduct System action
The product name of the server.
The monitor view will not be shown.
System action
Operator response
The sign-on request was not completed. The Sign On
window remains open. The original file will need to be restored for monitor
views to be available in Plan mode. .
Operator response IHS1157E Unable to launch bean due to
invalid bean name name.
If the servers from both products are installed, change
the host name to use the correct server, then sign on
again. If the problem persists, contact your system Explanation
programmer. The bean name is not specified correctly.
Message Variables
name
Ensure that the correct products are installed for both
The name of the bean that was to be launched.
the console and the server.
IHS1155I You have requested to close view Operator response
view. This view has one or more
properties windows open. You Verify that the name of the bean was specified
correctly in the command profile editor.

IHS1158E Unable to instantiate bean name. IHS1161E Aggregate thresholds are not
valid.
Explanation
Explanation
The bean cannot be instantiated by the Java Virtual
Machine. The value of the aggregate thresholds not correct.
Message Variables
Operator response
name
The name of the bean that was to be launched. Close the message window and specify valid
aggregation threshold values.
Operator response IHS1162E Aggregation priority is not valid.
Verify the following:
Explanation
• That the name of the bean was specified correctly in
the command profile editor The value of the aggregation priority is outside the
accepted range.
• That the JAR file for the bean is available at the
topology server in the %BINIDIR%\TDS\server\db
\current\lib Operator response
• That the JAR file contains the bean. Close the message window and specify a valid
aggregation priority.
IHS1159I Non-visual bean loaded name.
IHS1163E Flag is not valid.
Explanation
Explanation
The bean that was launched does not have a window.
One of the flags that has been changed cannot be set
Message Variables on the Resource Properties window.
name
The name of the bean that was launched. Operator response
Close the message window and set the flag correctly.
System action
IHS1164E Polling interval is not valid.
Explanation
Operator response
The value for the polling interval is outside the
Check the log for any output.
permitted range.
IHS1160E The entered task arguments are
not valid. Task: task name Reason: Operator response
reason code
Close the message window and specify a valid polling
interval.
Explanation
IHS1165E Resource name is not valid.
The values entered in the entry fields for the bean are
not valid.
Explanation
Message Variables
The name of the resource is not valid.
task name
The name of the task whose arguments are
Operator response
collected by the bean.
reason code Close the message window and specify a valid
The reason the entry fields were not valid. resource name.
IHS1166W You have requested to delete the
Operator response application name. This will also
delete any software components
Close the message window and reenter the values in
the entry fields for the bean.
defined for the application. Do you Message Variables
want to continue?
{0}
Name of the field which must contain a greater
Explanation value.
You have requested to delete an application. Deleting {1}
an application also deletes all information about any Name of the field which must contain a lesser
software components that have been defined as part value.
of this application.
name Ensure that the value in field {0} is greater than the
The name of the application to be deleted. value in field {1}.
IHS1175W On the Web Server page, the
System action default value for the port number
If you select Yes, the application and any associated cannot be restored without first
software components are deleted. If you select No, stopping the web server.
the application is not deleted.
Explanation
Operator response To restore the default value for the web server port
Select Yes to delete the Application and all associated number, you must first stop the web server.
software components. Select No if you do not want to
delete this application. System action
IHS1167W You have requested to delete the The default port number cannot be restored.
software component name. This
will also delete all information Operator response
about the component. Do you want
To restore the port number to its default value, follow
to continue?
these steps:
Explanation 1. On the web server page of the Console Properties

notebook, stop the web server.
You have requested to delete a software component.
Deleting this component will delete all information 2. On the web server page of the Console Properties
about the component. notebook, click Default.
Message Variables IHS1176W The specified port port number is

already in use. On the Web Server
name page of the Console Properties
The name of the software component you have notebook, select a different port
asked to delete. number. Apply the change and
then restart the web server.
System action
If you select Yes, the software component is deleted. Explanation
If you select No, it is not deleted. This console currently uses a port number that is
already in use by another web server. Multiple web
Operator response servers cannot use the same port number.
Select Yes to delete the software component. Select Message Variables
No if you do not want to delete this software
Port Number
component.
The port number used by the web server.
IHS1174E \"{0}\" field must be greater than
the \"{1}\" field. System action
The web server was not started.
Explanation
Field {0} can not be less than field {1}.

To specify a unique port number, follow these steps: Specify a different port number range as follows:
1. On the web server page of the Console Properties 1. On the web server page of the Console Properties
notebook, specify a different port number. notebook, change the port number range.
2. Apply the change. 2. Apply the change.
3. Start the web server again. 3. Start the web server again.
IHS1177W You are about to stop your web IHS1179I The web server has been
server. Doing this will result in all successfully started using port
servable files being deleted. portnum.
When you stop the web server, all views that are The web server was started using the port number
serviced by the web server for this console are deleted indicated.
so that another client on this computer cannot obtain
Message Variables
that same port number and serve the views you have
opened. portnum
The port number used by the web server.
System action
System action
Any views which have already been created for the
web server will be removed from the servable list. None

Do one of the following: None
• Click Stop web server to stop the web server and IHS1180W The AMP packaging file should end
delete the views. with ".amp" or ".pkg" Do you want
• Click Cancel to leave the web server running. to continue processing file
filename? Select Yes to continue.
IHS1178W All ports in the specified range Select No to choose another file.
(startportnum to endportnum) are
already in use. On the Web Server Explanation
page of the Console Properties
notebook, select a different start The file you selected does not end with one of the
of port range or end of port range. preferred extensions: ".amp" or ".pkg". You can
Apply the change and then restart continue processing, but this indicates that the file is
the web server. not a valid package file.
Message Variables
Explanation
filename
All the ports defined for the web server in the Console The name of the selected file.
Properties notebook are currently in use.
startportnum If you select Yes, the system tries to process the file. If
The start of the port number range you select No, you can choose another file.
endportnum
The end of the port number range Operator response
System action
• Select Yes to continue processing the file.
The web server was not started. • Select No to choose another package file.
IHS1181I An AMP was added to the server Operator response
by user user name. The console log Make sure that duplicate JAR files are not present in
has additional details. multiple AMPs.
Explanation IHS1184W Problems were encountered in

loaded JAR files. One or more
The AMP was successfully loaded by the specified applications may fail. Please
user. check the console log for details.
Note: If you have used the Verify function in this
console session (this is indicated in the message) your Explanation
verification business tree and views might not
The JAR files cannot be loaded and processed
accurately represent the newly added AMP. To see the
successfully.
new AMP information, sign off and back onto the
console.
System action
Message Variables
The system will not process the JAR file if there was
user name any error while loading it.
The user who loaded the new AMP.
Operator response
System action
Make sure that duplicate JAR files are not present in
The AMP is now available for use. multiple AMPs or that the same fully qualified class
names are not stored in more than one JAR file.
Operator response
IHS1185W Multiple definitions of the same
Check the console log for more information about the class name occur in different JAR
specific entities that were added. files. One or more applications
may fail. Please check the console
IHS1182E The AMP was not successfully
log for details.
processed. Please check the
console log for details.
Explanation
Explanation You tried to load the more than one JAR file, each of
which contains the same fully qualified class name.
There was a failure in loading the selected AMP
package file.
System action
System action The system will not load the JAR files.
The system cannot load the selected AMP package
file. The AMP is not available for use. Operator response
Make sure that the JAR files do not contain the same
Operator response fully qualified class names.
Check the console log for specific failure information. IHS1186W File filename does not exist.
IHS1183W The same JAR file is being loaded
more than once. Please check the Explanation
console log for details. The file you specified in the file selection dialog does
not exist.
Explanation
Message Variables
You tried to load a JAR file that has already been
filename
loaded and processed.
The file specified in the file selection dialog.
System action
System action
The system will not load the JAR file if it has already
The system is not able to load the specified file.
been loaded.

Operator response • If the command exit on the server is provided by the
customer, then ensure that this command exit can
Specify another file or cancel the operation.
get to the source of it's data.
IHS1187E Command exit exitname on the • If the command exit is IHSXTHCE, ensure that the
server has timed out. network traffic between the topology server and IBM
numresponses command Z NetView is acceptable.
responses were received. The
command responses may not be If you cannot resolve the problem, contact IBM
complete. Command String: Software Support.
stringname Time out value: value IHS1188E Command exit exitname on the
server failed. Return Code:
Explanation 0xreturncode Command String:
stringname
The topology console started a command exit on the
topology server, but the topology server timed out
while waiting on the command responses. It is very Explanation
likely that the command responses are not complete. The topology console invoked a command exit on the
Message Variables topology server, but the topology server received a
non-zero return code from the command exit. The
exitname return code came from the IhsiSend API on the server.
The name of the command exit that was invoked
on the server. Message Variables
numresponses exitname
The number of command responses that the The name of the command exit that was invoked
console received from the server, and thus, this is on the server.
the number of responses that the server received returncode
from the command exit. The return code that the server received from the
stringname IhsiSend API while calling the command exit.
The command string that was sent to the stringname
command exit on the server to carry out. The command string that was sent to the
value command exit on the server for execution.
The number of seconds that the server waited for
all command responses. System action
The server command exit failed. The command did not
System action
complete.
It is likely that the command responses were
processed by the console; however, this depends on Operator response
what program started the server command exit on the
console. This might have been a customer-provided Contact your system programmer.
console command exit, which might or might not
process the available command responses. System programmer response
Look up this return code in the IBM Z NetView User's
Operator response Guide: NetView Management Console and take the
Try the request again. If the same failure occurs, appropriate action. If you cannot resolve the problem,
increase the request timeout on the General page of contact IBM Software Support.
the Console Properties dialog. If this does not resolve IHS1190E The URL variable is not defined in
the problem, contact your system programmer. the command string.

Do one or more of the following: You attempted to connect to a web page, but no web
• If the program that started the server command exit page address was provided.
on the console is a customer-provided command
exit, then increase the time out value.
The request for a web page will not be completed. Verify that the command specified in the message is
executable from the command line of this system in
Operator response any directory. Also verify that security is configured
properly.
IHS1193E No match for operating system
operating_system and a program
type of program_type could be
Using the CPE utility to ensure that there is a %url% found in the properties file.
entry in the command string for this command.
IHS1191E The process invoked returned a Explanation
non-zero return code. The command invoked attempted to start a process on
this workstation, but an entry for this program type
Explanation and operating system cannot be found in the
properties file.
The selected command invoked a process on this
workstation. The launched application process Message Variables
returned a non-zero return code to the operating
operating_system
system. This might or might not be an error, depending
The name of the operating system.
on the process invoked.
program_type
The alias for the process that attempted to be
System action
started.
The system continues.
System action
Operator response
Since this operating system and program type cannot
Contact the system programmer to see if this message be resolved in the properties file, no action is taken.
is expected. The system continues.

Look in the error log to see the name of the process Contact your system programmer.
and the return code. Verify that this return code is
acceptable for this process. System programmer response
IHS1192E The system could not invoke the Edit the usercmdinv.properties or
process process defaultcmdinv.properties file and add an entry for this
program type and operating system. The properties
Explanation files are located in the settings directory of the current
server database.
The selected command attempted to invoke a process
on this workstation, but that process cannot be IHS1194E Unable to retrieve session data
started. from session monitor because a
Message Variables required task on IBM Z NetView is
not active.
process
The complete string that was passed to the Explanation
operating system to invoke the process.
The session monitor task AAUTSKLP was not activated
System action or failed to initialize on the NetView program that the
console has logged onto. This prevents retrieval of
The command cannot be completed. The system session data from this and any other NetView domain.
continues.
Operator response
Operator response
Start the session monitor task on host NetView by
Contact your system programmer. entering STARTCNM NLDM on a host NetView

command line. For more information, enter HELP session monitor in the specified domain. A cross-
AAU923 on a host NetView command line, or contact domain session cannot be established.
Message Variables
System programmer response domainID

The NetView domain ID entered in the Session
On a host NetView command line, enter HELP AAU923 Data window, or the domain ID that was converted
for more information on what actions to take. from the NETID and SSCP name of the selected
IHS1195W No data exists for the resources resource, when no NetView domain ID was
specified. Resource: resourcename entered in the Session data dialog.
Partner resource: partnername
Domain ID: domainID Operator response
If you entered a domain ID in the Session Data
Explanation window, ensure that you specified the correct domain
There is no data in the session monitor VSAM database identifier, Verify that the session monitor is active in
or in session monitor storage for the resources the specified domain. For more information, enter
specified at the specified view domain. The resource HELP AAU926 on the host NetView command line or
name might not be valid or there might not be any data contact your system programmer.
for that resource.
Message Variables
On a host NetView command line, enter HELP AAU926
resourcename for information on what actions to take.
The name of the resource entered in the Session
Data window. IHS1197E The SSCP name could not be
partnername translated into a IBM Z NetView
The name of the partner resource entered in the domain ID. Resource:
Session Data window, or <empty> if no resource resourcename Partner resource:
was entered. partnername NetID: netid SSCP
name: sscpname
domainID
The name of the NetView domain ID entered in the
Session Data window. Explanation
The NetView that the console has logged onto cannot
Operator response translate the NETID and the SSCP name to a NetView
domain ID. The session monitor does not have any
If a partner resource name was entered in the Session internal information to map the SSCP name into a
Data window, verify that this resource name was NetView domain ID.
entered correctly. For more information, enter HELP
AAU925 on a host NetView command line, or contact Message Variables
your system programmer. resourcename
System programmer response Data window.
On a host NetView command line, enter HELP AAU925 partnername
for more information on what actions to take. The name of the partner resource entered in the
Session Data window, or (empty) if no resource
IHS1196E Unable to retrieve data from IBM Z was entered.
NetView domain domainID.
Reason: The NetView program netid
cannot establish a cross-domain The network identifier of the selected resource. It
session at the adjacent NetView can be none if the name of the selected resource
domain. does not contain a netID.
sscpname
Explanation The system services control point that reported
the selected resource.
The session monitor in the NetView program which the
console is logged onto, cannot communicate with the
Operator response started or the process returned a non-zero return code
to the operating system.
If the NetView domain ID is known, provide this
information in the Session Data window. For more Message Variables
information, enter HELP AAU974 on a host NetView
process
command line, or contact your system programmer.
The complete string that was passed to the
operating system to invoke the process.
return code
On a host NetView command line, enter HELP AAU974 The return code that the process returned.
for more information on what actions to take.
IHS1198E A failure occurred on IBM Z System action
NetView while retrieving session The command cannot be completed.
data. Resource: resourcename
Partner resource: partnername
Operator response
Domain ID: domainid NetView
message: netviewmessage Contact your system programmer. This message might
or might not be expected.
Explanation
Message Variables
Do either of the following:
resourcename
• Verify that the command specified in the message is
executable from the command line of this system in
Data window.
any directory. Also verify that security is configured
partnername properly.
The name of the partner resource entered in the
• Look in the error log to review the name of the
Session Data window, or (empty) if no resource
process and the return code. Verify that this return
was entered.
code is acceptable for this process.
domainid
The name of the NetView domain ID entered in the IHS1200W No selected resources are
Session Data window. applicable for processing.
netviewmessage
The host NetView error message that was Explanation
generated when the session data was retrieved. You tried to update the flags for one or more resources
via the resource-specific pop-up menu. However, none
Operator response of the selected resources allows you to update the flag
as requested. You are not allowed to update the flags
For more information, enter HELP messagenumber on
for a resource if:
a host NetView command line, where messagenumber
is the message number in netviewMessage, or contact • You are setting (or clearing) a flag on a resource that
your system programmer. has already been set (or cleared).
• You are trying to update a flag on a resource for
System programmer response which that flag is not applicable.
a host NetView command line, where messagenumber System action
is the message number in netviewMessage. The request is ignored.
IHS1199E The system could not invoke the
process: process or the process Operator response
returned a non-zero return code: Select OK to close the message window.
return code
IHS1201I The More Detail function is not
Explanation available from customized
dynamic views.
The selected command attempted to invoke a process
on this workstation, but either the process cannot be

Explanation name
The name of the view that you requested.
Invocation of the More Detail function is not supported
from customized dynamic views.
System action
System action If you are attempting to open a view, the view does not
open. If you are attempting to refresh the view, the
The NetView management console topology server
view closes.
does not support the More Detail function when
invoked from a customized dynamic view.
Operator response
Operator response Do the following:
Perform the More Detail function from the dynamic 1. Select OK to close the message window.
view in the Network Views or Located Views list. 2. Ensure that the appropriate spans are started.
IHS1202I The view list created for this 3. If you cannot fix the problem, contact your system
request is not complete. One or programmer or the person in your organization
more views are not within your responsible for security administration.
span of control.
System Programmer Response: Do the following:
Explanation 1. Determine which view is involved.

One or more views were found that match your 2. See the IBM Z NetView Security Reference for
selection criteria but are not within your span of information about using spans to protect resources
control. and views, and also for debugging security
problems.
System action IHS1204I The view list created for this
request is not complete. No
The number of views in the created list determines the
resources in one or more views are
action:
within your span of control.
• If no views are found, the request is ignored.
• If one view is found, it is opened. Explanation
• If more than one view is found, a selection list is One or more views were found that match your
displayed. selection criteria, but you are not authorized to display
Operator Response: Do the following: any of the resources in one or more of those views.
1. Select OK to close the message window. System action

2. Ensure that the appropriate spans are started.
The number of views in one or more of the created list
3. If you cannot fix the problem, contact your system determines the action:
programmer or the person in your organization
responsible for security administration. • If no views are found, the request is ignored.
• If one view is found, it is opened.
• If more than one view is found, a selection list is
1. Determine which views are involved. displayed.
2. See the IBM Z NetView Security Reference for
Operator Response: Do the following:
information about using spans to protect resources
and views, and also for debugging security 1. Select OK to close the message window.
problems. 2. Ensure that the appropriate spans are started.
IHS1203I The requested view name is not 3. If you cannot fix the problem, contact your system
within your span of control. programmer or the person in your organization
responsible for security administration.
Explanation System Programmer Response: Do the following:
You are not authorized to display the requested view. 1. Determine which views are involved.
Message Variables
2. See the IBM Z NetView Security Reference for 3. If you cannot fix the problem, contact your system
information about using spans to protect resources programmer or the person in your organization
and views, and also for debugging security responsible for security administration.
problems.
IHS1205I No resources in the requested 1. Determine which resources are involved.
view name are within your span of
control. 2. See the IBM Z NetView Security Reference for
and views, and also for debugging security
Explanation
problems.
You are not authorized to display any resources in the
IHS1207I The specified resource is not
requested view.
Message Variables Unable to display view name.
name
The name of the view that you requested. Explanation
The view is not displayed because you do not have
System action authorization to view the selected resource. If you
selected the resource from an open view, the
If you are attempting to open a view, the view does not
authorization for this resource might have changed
open. If you are attempting to refresh the view, the
since you opened the original view.
view closes.
Message Variables
Operator response name
Do the following: The view name that is not displayed.
1. Select OK to close the message window.

System action
3. If you cannot fix the problem, contact your system
responsible for security administration. Operator response
System Programmer Response: Do the following: Do the following:
1. Determine which view is involved. 1. Select OK to close the message window.
2. See the IBM Z NetView Security Reference for 2. Ensure that the appropriate spans are started.
information about using spans to protect resources 3. If you cannot fix the problem, contact your system
and views, and also for debugging security programmer or the person in your organization
problems. responsible for security administration.
IHS1206I The specified resource is not System Programmer Response: Do the following:
within your span of control. 1. Determine which resource is involved.
Explanation IHS1208I One or more resources are not

One or more resources were found that match your
selection criteria, but you are not authorized to display
Explanation
them.
If changing flags or aggregation values, this request
System action will not affect one or more of the selected resources
because you do not have the proper span authority to
The request is ignored. issue commands against these resources. If listing
suspended resources, one or more resources were
Operator response found that you are not authorized to display.
Do the following:

System action • If you are attempting to open a single view, the view
does not open.
If changing flags or aggregation values, the request is
ignored for those resources that are not within your • If you are attempting to open multiple views, and
span of control. When listing suspended resources, the exactly one view is valid, it is opened.
resources that you are not authorized to display will • If you are attempting to open multiple views, and
not appear in the window. more than one view is valid, a selection list is
displayed.
Operator response • If you are attempting to refresh a view, the view
Do the following: closes.
• If you are attempting to list suspended resources,
suspended RODM resources are not displayed.
• If you are attempting to update user status or
3. If you cannot fix the problem, contact your system aggregation values, RODM resources will not be
programmer or the person in your organization updated.
System Programmer Response: Do the following: System programmer response
1. Determine which resources are involved. Check for one or more of the following:
2. See the IBM Z NetView Security Reference for • Load the span authorization table.
• Ensure that the host scope checker task (DUIFSSCO)
is started.
problems.
• Ensure that GMFHS and RODM are active.
IHS1209I Unable to perform span
• Ensure that the session between the graphic data
authorization.
server and IBM Z NetView is active.
Explanation • Look in the IBM Z NetView log for span authorization

messages.
A span authorization failure occurred for the request.
• If a RODM method failed while creating a view,
This can happen for one of the following reasons:
check the GMFHS and RODM logs for specific
• The span authorization table has not been loaded. information about the method failure.
• The NetView host scope checker task (DUIFSSCO) • To determine which view in the list encountered a
might be down. method failure, do the following:
• GMFHS or RODM is not currently available, so 1. Select the GMFHS views in the list.
information about RODM resources cannot be
2. Open the views.
included.
• The server timed out while waiting for a response IHS1113W is displayed for the view containing the
from GMFHS. method failure.
• The session between the server and IBM Z NetView • The value of the MyName field of objects in the
has gone down. Network_View_Class and the
Configuration_Peer_View class are limited to 32
• The scope checker detected an error during the span bytes. You can increase the DUIGINIT value.
authorization check. However, increasing the value can cause timeouts at
• GMFHS found more views than can be returned in the workstation.
one request, so the view list was truncated.
IHS1210I Unable to perform span
• A RODM method failed while creating a view. authorization because the
• One or more view names in RODM are too long. operator is no longer logged on to
• The NetView domain name has insufficient authority host IBM Z NetView.
to query RODM.
Explanation
System action A span authorization failure occurred because you are
The action depends upon the user's request. no longer logged on to IBM Z NetView.
System action 2. See the IBM Z NetView Security Reference for
The action depends upon the user's request.
• If you are attempting to open a single view, the view problems.
does not open.
IHS1214I The displayed view tree is not
• If you are attempting to open multiple views, and complete. One or more views in
exactly one view is valid, it is opened. the tree are not within your span
• If you are attempting to open multiple views, and of control.
more than one view is valid, a selection list is
displayed. Explanation
• If you are attempting to refresh a view, the view The displayed view tree is incomplete. Some views in
closes. the view tree are not within your span of control and
• If you are attempting to list suspended resources, thus are not displayed.
suspended RODM resources are not displayed.
• If you are attempting to update user status or System action
aggregation values, RODM resources will not be The partial view tree is displayed. It contains only
updated. views within your span of control.

Log on to the NetView program. Do the following:
IHS1211I The view list created for this 1. Select OK to close the message window.
request is not complete. The
specified resource is not within 2. Ensure that the appropriate spans are started.
your span of control. 3. If you cannot fix the problem, contact your system
Explanation responsible for security administration.
One or more resources were found that match your

selection criteria, but you are not authorized to display
them. Do the following:
1. Determine which views are involved.
System action
2. See the IBM Z NetView Security Reference for
The number of views in the created list determines the information about using spans to protect resources
action: and views, and also for debugging security
problems.
• If there is one view, it is opened.
• If there is more than one view, a selection list is IHS1215I The displayed view tree is not
displayed. complete. Unable to perform span
authorization.
Operator response
Explanation
Do the following:
The displayed view tree is incomplete because a span
1. Select OK to close the message window. authorization failure occurred while trying to obtain
2. Ensure that the appropriate spans are started. the view tree. This can happen for one of the following
3. If you cannot fix the problem, contact your system reasons:
programmer or the person in your organization • The span authorization table has not been loaded.
• The NetView host scope checker task (DUIFSSCO)
might be down.
• GMFHS or RODM is not currently available, so
Do the following: information about RODM resources cannot be
1. Determine which resources are involved. included.

• The server timed out while waiting for a response increasing the value can cause timeouts at the
from GMFHS. workstation.
• The session between the server and IBM Z NetView IHS1216I The displayed view tree is not
has gone down. complete. Unable to perform span
• The scope checker detected an error during the span authorization because the
authorization check. operator is no longer logged on to
host IBM Z NetView.
• GMFHS found more views than can be returned in
one request, so the view list was truncated.
Explanation
• A RODM method failed while creating a view.
• One or more view names in RODM are too long. The displayed view tree is incomplete because a span
authorization failure occurred while trying to obtain
• The NetView domain name has insufficient authority the view tree. This happened because the operator is
to query RODM. no longer logged on to host IBM Z NetView.

The partial view tree is displayed. It contains only The partial view tree is displayed. It contains only
views that do not require span authorization. views that do not require span authorization.

Do the following: Select OK to close the message window. Log on to IBM
1. Select OK to close the message window. Z NetView.
2. Ensure that the appropriate spans are started. IHS1217I NETCONV session started from
3. If you cannot fix the problem, contact your system IBM Z NetView host hostname.
programmer responsible for security
administration. Explanation
NETCONV session has started from host NetView to
System programmer response the NetView management console server.
Check for one or more of the following: Message Variables
• Load the span authorization table. hostname
• Ensure that the host scope checker task (DUIFSSCO) The IBM Z NetView from which the NETCONV was
is started. started.
• Ensure that GMFHS and RODM are active. IHS1218I NETCONV session stopped from
• Ensure that the session between the graphic data IBM Z NetView host hostname.
server and IBM Z NetView is active.
• Look in the IBM Z NetView log for span authorization Explanation
messages. The NETCONV session from NetView host to the
• If a RODM method failed while creating a view, NetView management console server has been
check the GMFHS and RODM logs for specific stopped.
information about the method failure.
Message Variables
• To determine which view in the list encountered a
method failure, do the following: hostname
The IBM Z NetView from which the NETCONV was
1. Select the GMFHS views in the list. started.
2. Open the views.
Operator response
IHS1113W is displayed for the view containing the
method failure. The value of the MyName field of Start the NETCONV session from NetView host.
objects in the Network_View_Class and the
Configuration_Peer_View class are limited to 32 bytes. IHS1219I No matching resources were
You can increase the DUIGINIT value. However, found.
An attempt to find one or more resources using the Using the Command Profile Editor (CPE), edit the
Find or Advanced Find dialog failed. There were no definition for this command and ensure that it is not
resources in the view that matched the Find or defined as resource independent.
Advanced Find search criteria.
IHS1223E The object objectname does not
have a valid RODM object ID.
Operator response
Review and change the search criteria if you expect Explanation
one or more objects to be found.
The selected resource does not have a valid RODM ID,
IHS1220I Syntax of the resource pattern is which is required by this command. This might occur if
not correct. the command was issued against an aggregate object.
Message Variables
Explanation
objectname
An attempt to find one or more resources using the The display name of the object the command was
Find or Advanced Find dialog failed. The search issued against.
pattern for one or more fields does not have the
correct syntax for the selected expression type (either
System action
DOS wild card or regular expression type).
The command is not issued.
Operator response
Operator response
Correct the search pattern and retry the request.
Verify that you selected the correct object for this
IHS1221I Resource navigation is command and retry the command. If the problem
terminating. viewname has persists, contact your system programmer.
changed such that it contains
fewer than two matching
resources. System programmer response
Using the Command Profile Editor (CPE), verify that the
Explanation command is valid for the defined object types.
Viewname has changed such that it contains fewer IHS1224E The object objectname does not
than two matching resources. have a valid TCP/IP address.
Message Variables
Explanation
viewname
The name of the view for which resource A TCP/IP command was issued against a selected
navigation is terminating. object, but that object does not have a TCP/IP address
defined in RODM.
IHS1222E This command can not be defined
as resource independent. Message Variables
objectname
Explanation The display name of the object the command was
issued against.
This command has been defined as resource
independent in the commands database.
System action
System action The command is not issued.
Operator response
Operator response Verify that the command is valid for the selected
resource.

Verify that the object has a TCP/IP address and that The command is not issued.
the address is being added to the object in RODM.
IHS1225E Not authorized to issue this Operator response
command. Verify that you selected the correct object for this
command and that it has MIB information. Then, retry
Explanation the command.
You attempted to issue a command that your operator IHS1228I A message could not be delivered.
ID is not authorized to issue. Reason: reason Message: message

The command is not issued. An attempt to send a message using the Send
Message dialog failed. The reason for the failure is
Operator response specified in the reason message insert.
Contact your system programmer. Message Variables

reason
System programmer response The reason that the message cannot be sent. The
reason is one of the following:
See the appendix in the IBM Z NetView Security
Reference for instructions on setting up security. • No other operators are signed on to the same
server to receive the broadcast message
IHS1226E This command is not installed at
the host. • The operator is either not signed on or is the
message originator.
Explanation message
The message that cannot be sent.
The command issued interacts with modules on the
host. Those modules cannot be located.
System action
System action The message is not sent.
Operator response
Operator response Verify that the operator identifier that you want to
send the message to is correct and send the message
again.
System programmer response IHS1229E The requested status minutes are

not valid.
Verify that the NetView host is at the proper level.
Also, verify that the command CNMMIBBR is available
on NetView host. Explanation
The value specified for the status minutes search
IHS1227E SNMP is not installed on object
criteria on the Find Advanced dialog is not valid.
objectname.
Operator response
Explanation
Change the status minutes search criteria and try the
A command was issued to start the MIB Browser, but
request again.
the selected object does not have MIB Information
defined in RODM. IHS1230E Error loading file filename from the
Message Variables server. A default set of wrappable
characters will be used.
objectname
The display name of the object the command was
issued against.
The system cannot find the specified file in the This error occurs when the "Use my default web
following directory: browser" or the "Let me specify my own browser"
command is chosen on the General tab of the Console
• For Intel: %BINDIR%\TDS\server\db\current
Properties dialog, and the system encounters a
\settings
problem starting the external browser.
• For UNIX: $BINDIR/TDS/server/db/current/settings
The wraplabelbreaks.properties file defines the set of System action
characters that is used to determine where to wrap The external browser did not start and the online help
labels. did not display.
Message Variables
filename Operator response
Typically, this is the wraplabelbreaks.properties Do one of the following:
file.
• If you want to use an external browser for viewing
the online help, verify that your system has sufficient
System action resources to start a program. Then, try to open the
The system uses the following default set of help facility again. If the problem persists, contact
characters to determine where to wrap the labels: your system programmer.
• Space ( ' ' ) • Use the built-in help facility. On the General tab of
the Console Properties dialog, select Use built-in
• Dash ( '-' ) Help facility.
• Period ( '.' ) • If you are on a platform other than Windows, verify
• A colon ( ':' ) that the name of your Internet browser is in your
• A dollar sign ( '$') executable path statement.
• A percent sign ( '%') • If you are on a SUN system, you must execute "xhost
+" on the system prior to launching the external
• At symbol ( '@' ) browser for help.
• Slash ( '/' ) • If you choose "Let me specify my own browser",
• Backslash ( '\' ) verify that you entered the correct command. The
• A right parenthesis ( ')' ) error message that is displayed when the error
occurs shows the command that is issued.
• A right curly bracket ( '}' )
• A right bracket ( ']' ) System programmer response
Verify that the system has sufficient resources to start
Operator response
a program. If you cannot resolve the problem, contact
Do one of the following: IBM Software Support.
• Specify that you do not want to wrap labels on the IHS1232I Because this is the first instance of
View properties page. the component type component
• Use the default set of characters for wrapping the type in this business system, you
labels. must complete the component
type settings. The Component
• If you do not want to use the default character set
Type Properties window will be
for wrapping labels, verify that the file has not been
opened for you.
renamed. If it has not been renamed, contact your
system programmer to reinstall the program.
Explanation
System programmer response You must define each component type in a business
system using the Component Type Properties window.
Verify that the file has not been renamed. If it has not
Because this is the first instance of the specified
been renamed, reinstall the program.
component type you have added to this business
IHS1231E Error attempting to launch system, the Component Type Properties window
external browser for help. opens automatically for you.

component type Verify that the specified file exists and that the user
Component type name has write access to the specified subdirectory.
IHS1236E An error occurred closing the
Operator response following file: file name
Click OK to open the Component Type Properties
window. Explanation
IHS1233E An error occurred opening the An error occurred when trying to close the specified
following file: file name file.
Message Variables
Explanation
file name
An error occurred when trying to open the specified file name
file.
System Response: The export operation ends.
Message Variables
file name Operator response
file name
Verify that the specified subdirectory exists and that
System Response: The export operation ends. there is disk space available.
IHS1237E An error occurred adding the
Operator response following file file name to the
Verify that the file exists and can be read. package file.
IHS1234E An error occurred creating the

Explanation
following file: file name
An error occurred when trying to add the specified file
Explanation to the package file (.pkg).
An error occurred when trying to create the specified Message Variables

file. file name
Message Variables file name
file name System Response: The export operation ends.

file name
Operator response
Verify that there is disk space available.
Operator response IHS1238E An error occurred writing to the
Verify that the specified subdirectory exists and that following directory: directory
the user has write access to the specified name.
subdirectory.
Explanation
IHS1235E An error occurred deleting the
following file: file name An error occurred when trying to write to the specified
directory.
An error occurred when trying to delete the specified directory name
file. directory name
Message Variables
System action
file name
file name The export operation ends.
Operator response 1. Verify that the Tivoli Module Builder has been
installed correctly on the same computer as the
Verify that the specified directory exists and that the
Tivoli GEM Console.
user has write access to the specified subdirectory.
2. Verify that the specified command points to the
IHS1239E The Tivoli Module Builder or Tivoli correct subdirectory in which the Tivoli Module
Module Designer is already Builder was installed.
running.
IHS1242E There are no real components in
the current subsystem.
Explanation
Only one instance of the Tivoli Module Builder or the Explanation
Tivoli Module Designer can be launched from the Tivoli
GEM Console at a time. You can filter out instances of real component types
from a subsystem, based on filter criteria that you
System Response: The Tivoli Module Builder or the specify. To use instance membership filtering, you
Tivoli Module Designer is not launched. must have at least one real component in the
subsystem before you can specify the filter criteria.
Operator response
Close the instance of the Tivoli Module Builder or the Operator response
Tivoli Module Designer that is currently running. Follow these steps:
IHS1240E The specified command to launch 1. Click OK to return to the subsystem.
the Tivoli Module Designer is not
2. Place at least one real component in the
valid.
subsystem.
Explanation 3. Click Filter to bring up the Instance Membership

Filter Properties window and specify the filter
The Tivoli GEM Console failed to launch the Tivoli criteria.
Module Designer using the command given by the
user. IHS1243W You have requested to delete all
instances of the component type
System Response: The Tivoli Module Designer is not type in the current view. You
launched. cannot undo this action. Do you
want to continue?
Operator response
Do the following: Explanation
1. Verify that the Tivoli Module Designer has been You have requested to delete all instances of the
installed correctly on the same computer as the specified component type in the current view. You
Tivoli GEM Console. cannot undo this action.
2. Verify that the specified command points to the Message Variables
correct subdirectory in which the Tivoli Module type
Designer was installed. The type of the component to be deleted.
IHS1241E The specified command to launch
the Tivoli Module Builder is not Operator response
valid.
Explanation 1. Click Yes to delete all instances of the specified

component type.
The Tivoli GEM Console failed to launch the Tivoli
Module Builder using the command given by the user. 2. Click No to cancel the operation. No instances of
the specified component are deleted.
System Response: The Tivoli Module Builder is not
launched. IHS1244E The selected component cannot be
included in an aggregate, because
it has no component information
Operator response
tasks defined.
Do the following:

Explanation 2. For real components, select the connection types
that apply for this component type. For generic
To include a component in an aggregate, the
components, add the connection types that apply
component type must have component information
for this component.
tasks defined in the component definition file (CDF).
3. Select the two components and then click the
Connection button.
Operator response
To include the component in the aggregate, do either IHS1247E A connection cannot be made
of the following: between the selected
components, because they have
• Select another component type that has component no connection types in common.
information tasks.
• Contact the provider of the component definition file Explanation
(CDF) and have the appropriate component
To make a connection between two components, the
information tasks added to the CDF.
components must have a connection type in common.
IHS1245E To define a connection, you must
have two (and only two) Operator response
components selected. Note: To
select multiple components, hold To add the connection, follow these steps:
down the Ctrl key. 1. For one of the components, open the Component
Type Properties window.
Explanation 2. Do one of the following:
To define a connection, you must first select two • For real components, in the Connections list
components before clicking the Connection button. To select the connection types that apply for this
select multiple components, hold down the Ctrl key. component type.
• For generic components, in the Connections list,
Operator response click the Add button to add the connection types
To define a connection, follow these steps: that apply for this component.
1. Select two components. 3. Select the two components and then click the
Connection button.
2. Click the Connection button.
IHS1248I The connection connection type
IHS1246E The component component, which name between resource name and
is an instance of the component resource name in view view name
type component type, has no has been deleted because it is no
connection types defined as part longer valid.
of its business definition.
Explanation
Explanation
One of the endpoints of a connection no longer
To define a connection between component types, the supports that connection type. The connection has
component types must have at least one connection been deleted from the view. When component type
type defined as part of their business definitions. properties are changed, such as deleting or renaming a
Message Variables connection type associated with that component type,
any connections of that type in that view are no longer
component valid and are automatically deleted.
Component name
Message Variables
component type
Component type name connection type name
Name of the connection type
Operator response resource name
Do the following: Name of the resource
view name
1. Open the Component Type Properties window.
Name of the view
If you want to restore the connection between the two username
component types, do either of the following: The name of the user in the following format:
username@hostname
• In the Business Component Properties window,
specify the connection type.
Operator response
• Redefine the connection with a valid connection type
that is supported by the two component types. Do one of the following:
IHS1249I One or more resources have been • If you are sure that the specified user is not using
changed to the Undefined Generic Plan mode, click the OK button to open this view
component type in the view name with all editing controls enabled.
view. • Click the Read-only button to open this view with all
editing controls disabled, in read-only mode. Then, if
Explanation you need to make changes while in Plan mode, try to
open this view again later.
A component type has been deleted. Resources
defined with that component type are no longer valid IHS1251E The aggregate aggregate name is
and have been changed to the "Undefined generic" empty, and it will not be exported.
component type.
view name The specified aggregate is empty. To export the

Name of the view aggregate to the Tivoli GEM server, you must have at
least one real component in the aggregate.
Do the following: aggregate name
The fully qualified name of the aggregate, including
1. Open the Business Component Properties window
the names of all of its parents.
for the resource identified with the "Undefined
generic" component type.
System action
2. Specify a new component type.
Validation stops with an error.
IHS1250W User username has accessed Plan
mode on the same Tivoli GEM
Operator response
server and may still be using it. If
two people use Plan mode on the Do one of the following:
same Tivoli GEM server
• Remove the aggregate.
simultaneously, data might be
lost. Select OK if you know that • Add at least one component to the aggregate and
the above user is no longer using then export the business system again.
Plan mode. Select Read-only to
IHS1252E There are no components in this
use Plan mode in read-only mode.
business system.
Explanation
Explanation
According to the PlanMode.user file, another user
There are no components in the business system. To
currently has Plan mode open on the same Tivoli GEM
export the business system, at least one component
server. When you open a view in Plan mode in read/
must be defined.
write mode, your username is stored in the
PlanMode.user file.
System action
If two people use Plan mode on the same Tivoli GEM
server simultaneously, changes might be overwritten Validation stops with an error.
and data might be lost.
Operator response
To ensure that no data is lost, open Plan mode in read-
only mode until you can verify that no one else has Add at least one component to the business system
Plan mode open. and then export the business system again.

IHS1253E There are no real components in the corresponding changes in the component
this business system. properties.
Message Variables
Explanation
CDF filename
There are no real components in the business system. The CDF filename for the real component.
To export the business system to the Tivoli GEM
server, you must define at least one real component. System action
System action Validation continues with a warning.
Validation stops with an error. Operator response
Do the following: • Select Ignore to continue exporting the current

version of the business system.
1. Add at least one real component
• Make the appropriate changes to the component
2. Export the business system again. properties from the new CDF on the Tivoli GEM
server.
IHS1254W There are some generic
components in this business • Export the business system again.
system that will not be exported.
IHS1256E The CDF file CDF filename does not
exist.
Explanation
The business system contains generic components Explanation
that will not be exported to the Tivoli GEM server.
The CDF file for a component in the business system is
However, if you export the business system as a
missing.
package file or to the Tivoli Module Designer, these
generic components will be exported. Message Variables
CDF filename
System action The CDF filename for the real component.
Validation continues with a warning.
System action
Operator response Validation stops with an error.
Operator response
• Click Ignore to ignore the warning message and
export the business system. Do one of the following:
• Click Cancel to cancel the export operation. If you • Delete the component that uses that CDF and then
want these components to be exported, convert export the business system again.
them to real components and then export the
• Install the CDF for that component and then export
business system again.
the business system again.
IHS1255W The CDF file CDF filename has
IHS1257E The CDF CDF triplet is used in
been changed on the Tivoli GEM
multiple levels of aggregation.
server and may be inconsistent
with the local version you are
using. Explanation
The specified real component is used in multiple levels
Explanation of aggregation. Components can only be used in one
level of aggregation.
The CDF file has been changed on the Tivoli GEM
Server and might be inconsistent with the local version Message Variables
you are using. To include the latest information from
CDF triplet
the CDF file on the Tivoli GEM server, you must make
The Manufacturer, Product and Version of the real
component.
Validation stops with an error. component type
Component type name
Operator response
System action
Do the following:
1. Delete the component from the multiple levels of
aggregation.
2. Export the business system again.
Examine the NetView log for more details. The
IHS1258E The generic component generic command issued can be trying to request a field in
component name is used in RODM that is not available for the resource selected.
multiple levels of aggregation. Correct the command in the server command
response file and rerun CPEBATCH.
Explanation
IHS1270E A failure occurred on IBM Z
The specified generic component is used in multiple NetView while executing a
levels of aggregation. Components can only be used in command. NetView message:
one level of aggregation. netviewmessage
Message Variables
Explanation
generic component name
The name of the generic component. A command was executed on IBM Z NetView and an
error message was returned.
Validation stops with an error. netviewmessage
The Tivoli NetView host message that was
Operator response generated.
Do the following:
System action
1. Delete the component from the multiple levels of
aggregation. The topology server ends.
2. Export the business system again.
Operator response
IHS1259W There are no real components in
this business system.
a host Tivoli NetView command line, where
messagenumber is the message number in
Explanation netviewmessage, or contact your system programmer.
There are no real components in the business system.
The business system can be exported as a package file System programmer response
or to the Tivoli Module Designer (TMD) for further
definition.
a host NetView command line, where messagenumber
is the message number in netviewmessage.
Operator response
IHS1271E An error occurred retrieving a
Click the Ignore button and continue with validation. variable from RODM.
IHS1260E The CDF file for the component
type component type does not Explanation
exist.
A command was issued that required information from
RODM. Either RODM cannot be contacted, or the
Explanation information requested does not exist in RODM.
The CDF file for this component type cannot be found
on the local GEM console computer. The business Operator response
system will not be exported.
Do the following to export the business system:

1. Open the business system. All components of the Operator response
specified component type are converted to
undefined generic components.
2. Export the business system again. • Click the Yes button to synchronize the clients
connected to the server. You are prompted for a
IHS1272E Too many Service Points are message and time range to broadcast to all users
selected. Only one selection is requesting that they log off. Once the time range has
allowed when the global wild card expired, you can either force the users off of the
is specified. clients or cancel your Load AMP request.
• Click the No button to cancel the operation.
Explanation
IHS1301I All clients are currently in the
The wild card "*.*.*.*" was entered in the Host name or resynchronization process. No
IP address field, and more than one service point was AMP can be loaded at this time.
selected in the list. Only a single selection is allowed
for this wild card. This is restricted because of
Explanation
performance considerations.
A previous request to load an AMP occurred and the
Operator response clients are currently being resynchronized. The AMP
cannot be loaded during a resynchronization process.
Either specify a different host name or IP address, or
only select a single service point in the list.
System action
IHS1273E Wild card characters are not The AMP is not loaded.
supported for TN3270 Service
Points. Deselect the TN3270
Service Points or do not use wild Operator response
card characters. When the resynchronization process completes, load
the AMP again.
Explanation
IHS1302W The server is currently
Wild card characters are not supported by TN3270 resynchronizing. You can wait
Service Points. until the resynchronization
process ends or cancel the sign on
Operator response request. Click the Ok button to
wait. Click the Cancel button to
Either deselect the TN3270 Service Points, or specify sign off.
the specific TCP/IP host name or IP address for which
to collect IP connection data.
Explanation
IHS1300W This AMP has been previously You cannot sign on to the server during a
loaded. To reload the AMP, all resynchronization process.
clients connected to the server
must be resynchronized. Do you
want to continue? Select Yes to System action
continue. Select No to cancel the You are not signed on.
operation.
Operator response
Explanation
When you change an AMP and load the modified AMP,
the clients connected to the server must be • Click the Ok button to wait for the resynchronization
resynchronized. To synchronize the clients, no users process to complete and to sign on to the server.
can be logged on, so you might have to force users off • Click the Cancel button to sign off of the server and
of the clients. sign on at a later time.
IHS1401W You must enter an integer in the
System action field field
The system responds based on the operator's
response.
Explanation altered from the normal max
allowed by Unix. You can change
A non-integer was entered into the field.
this max in
Message Variables DefaultScheme.properties.
WARNING: Changing this max can
field
potentially cause problems to your
The field in which to enter an integer.
network.
System action
Explanation
Unless you are an administrator, the value for the
number of probes to be sent must be between 1 and
Operator response the maximum value defined in the
Correct the value in the specified field. defaultscheme.properties file.
IHS1402W The text in the field field does not Note: Caution: This maximum value can be changed,
contain a valid IP Address or valid but if it is set too high, this can cause serious problems
TCP Host Name. to the network.
Message Variables
Explanation field
An IP address cannot contain blanks or commas. the number of Probes to be sent.
Message Variables Min
will always be 1.
field
Max
The field in which to enter the IP address or TCP
a number between 1 and 20, as defined in the
host name of the resource.
defaultscheme.properties file.
System action
System action
Operator response
Operator response
Enter a valid IP address in the specified field.
Enter a valid number between Min and Max or change
IHS1403W The text in the field field does not the defaultscheme.properties file.
contain a valid IP Address.
Caution: If the maximum is set too high in the
defaultscheme.properties file, this can cause serious
Explanation problems to the network.
An IP address cannot contain blanks or commas. IHS1410W CollectionType collection
Message Variables "CollectionName" will be deleted.
Are you sure?
field
The field in which to enter the IP address of the
resource. Explanation
You have requested to delete a collection; this
System action message requests confirmation.
The request is not processed. Message Variables
CollectionType
Operator response The type of collection: either View or Aggregate.
Enter a valid IP address in the specified field. CollectionName
The name of collection to be deleted.
IHS1404W The value entered in the field field
must be in the Min to Max range.
System action
Since you are not an
Administrator, the max has been The system responds based on the operator response.

Do one of the following: Progression to the next panel is suspended until the
value is corrected. The cursor is placed on the field in
• Click the Yes button if you are sure you want to
error.
delete the collection.
• Click the No button if you do not want to delete the Operator response
collection.
Correct the value.
IHS1411W Values must be greater than or
equal to -2. IHS1414W The collection must have a name.
You have entered an exact value for a threshold that is The collection name field cannot be left blank; it must
less than -2; these values must be at least -2 or contain a name.
greater.
System action
System action Progression to the next panel is suspended until the
Progression to the next panel is suspended until the value is corrected. The cursor is placed on the field in
value is corrected. The cursor is placed on the field in error.
error.
Operator response
Operator response Enter a name for this collection.
Enter a value that is at least -2 or greater.
IHS1415W The collection name cannot
IHS1412W Percentage values must be contain spaces.
between 0 and 100.
Explanation
Explanation The collection name cannot contain space or other
You have entered a percentage value that is not special characters; see the IBM Z NetView Resource
between 0 and 100. Object Data Manager and GMFHS Programmer's Guide
for specific object naming rules.
System action
System action
Progression to the next panel is suspended until the
value is corrected. The cursor is placed on the field in Progression to the next panel is suspended until the
error. value is corrected. The cursor is placed on the field in
error.
Operator response
Operator response
Enter a value that is between 0 and 100.
Correct the name so that it does not contain spaces.
IHS1413W Values must not decrease as
severities increase. IHS1416W The host data set name cannot be
blank.
Explanation
Explanation
The threshold values must not decrease in number as
severity increases. For example, if you have "exactly 1" When saving collection text in RODM loader format to
set for the first severity value, and "exactly 2" set for the host, the specified data set name cannot be left
the second severity value, you cannot set "exactly 1" blank.
for the third severity value as this is a decrease.
System action
value is corrected.
Operator response Selection or IP Service Point Selection) that serve only
to refine the search criteria for other objects.
Correct the error. If you decide not to save the
collection text to the host, uncheck the "Save to host
data set" checkbox. System action
IHS1417W At least one status must be Progression to the next panel is suspended until the
selected. Select the "All" button to value is corrected.
allow all statuses.
Operator response
Explanation Choose at least one object type to collect by moving it
The "Selected" radio button is active, but no status from the Available Types table to the Selected Types/
values from the table have been selected. If you want Names table. Alternatively, an object visible in a view
to use individual statuses as opposed to all status can be dragged and dropped onto the area marked
values, at least one value from the table must be "Drag and drop individual resources here."
selected. IHS1420W Enter the name of the object (or
objects, using pattern matching
System action characters) to collect. Enter "ALL"
to collect all objects of a particular
type.
value is corrected.
Explanation
Operator response
The Object name field has been left blank; it must
Either choose All to ignore status as part of the
contain a value.
collection criteria, or select at least one status value
from the table.
System action
IHS1418W Changes will not be saved. Are you
sure you want to cancel? Progression to the next panel is suspended until the
value is corrected.
Explanation
Operator response
You have indicated that you want to cancel the
collection that is currently open; this message Enter the name of the object to be collected. If you
requests confirmation. want to collect all objects of this type, enter ALL into
the field.
System action IHS1421I Do you want this new collection to
be represented as a View or as an
The system responds based on the operator response.
Aggregate object? Views are
visible in the console view tree.
Operator response Aggregate objects eventually need
Do one of the following: to be included in a view to be
visible.
• Click the Yes button if you are sure you want to
cancel editing the collection.
Explanation
• Click the No button if you do not want to cancel
editing the collection. This message is asking what type of collection to
create. There are two types of collections:
IHS1419W At least one type of object (other
View
than the "Selection" types) must
Collections that are visible on the NetView
be chosen and moved over to the
management console console view tree, like all
right side.
other networking views.
Aggregate
Explanation
Collections that only exist in RODM, and do not
There are no object types to collect. The Selected become visible until they are included in a
Types/Names table is either empty or contains only networking view or view collection.
"Selection" types of objects (for example, SNA Domain

The system responds based on the operator response. When attempting to save the collection in RODM
loader format at the host, an error was encountered
Operator response when accessing the requested host data set.
Do one of the following: Message Variables
• Click the View button to create a view collection. Message

The message as received from NetView program.
• Click the Aggregate button to create an aggregate
collection.
System action
• Click the Cancel button to cancel creating this
collection. The collection, in some circumstances, is sent to
RODM, but the data set does not contain the RODM
IHS1422W A collection with this name loader format data.
already exists. Overwrite it?
Operator response
Explanation
See the NetView online help for the message and
You have specified that you want to create a correct the problem.
collection, but a collection with this name and type
already exists. You are being asked to confirm the IHS1425E Warning or error messages from
decision to overwrite the existing collection. FLCV2RCM were encountered
when processing the collection
System action request: Messages
The system responds based on the operator response. Explanation
Operator response Collections are first sent to NetView to be processed

by an Executable file, FLCV2RCM. That EXEC
Do one of the following: encountered warning or error messages while
• Click the Yes button to overwrite the collection. processing the collection. These messages are in the
netlog of NetView program, and up to five of them are
• Click the No button to indicate that you do not want also available in this message box.
to overwrite the collection. You can then go back and
change the collection name to one that does not Message Variables
exist. Messages
IHS1423E The collection could not be sent to Up to the first five messages as issued by
the host. FLCV2RCM in the range of FLC003 and FLC178
through FLC187
Explanation
System action
The request to send the collection to the host has
encountered a communication failure. The collection might or might not have been added,
based on the severity of the FLCV2RCM messages.
System action
Operator response
The collection is not sent to the host.
Operator response
Check communication between the NetView
management console client and the NetView Review the messages as logged in the netlog of
management console server, and from the NetView NetView. Follow the procedures as described in this
management console server to NetView program. book for the messages received.
Ensure that GMFHS is available. Retry the request. IHS1426E The collection could not be
IHS1424E The collection text could not be created. Error code from GMFHS:
saved. Host message: Message ReturnCode:GMFHSMessageNumbe
r
GMFHS encountered an error when processing the Ensure that other NetView management console
collection. operations are still functioning. Retry the request.
Message Variables IHS1429E The list of collections could not be
retrieved due to a communications
ReturnCode
timeout.
The return code associated with
GMFHSMessageNumber.
Explanation
GMFHSMessageNumber
The message number issued by GMFHS. The request for the collection was sent to the NetView
management console server, but a response was not
Note: If this value is 100, contact IBM Software
received within the expected timeout period.
Support.
Operator response
System action
Ensure that other NetView management console
The collection definition object is created in RODM, but
operations are still functioning. Retry the request.
the collection creation object is not. The collection is
not complete because either the collection is in error IHS1430E The delete request could not be
or a RODM processing error occurred. sent to the host.

Notify the system programmer. The request to delete the collection encountered a
communication failure.
Follow procedures as described in the this book for the Operator response
message and return code received, unless the value Ensure that GMFHS is available. Retry the request.
for GMFHSMessageNumber is 100. In that case,
contact IBM Software Support. IHS1431E The delete request could not be
sent to the host.
IHS1427E The collection could not be sent to
the host due to a communications Explanation
timeout.
The request to refresh the list of collections
encountered a communication failure.
Explanation
The collection was sent to the NetView management Operator response
console server, but a response was not received within
the expected timeout period. Ensure that GMFHS is available. Retry the request.
IHS1432E The entry field cannot contain the
Operator response reserved sequence of characters,
Ensure that other NetView management console sequence.
operations are still functioning. Retry the request.
Explanation
IHS1428E The collection could not be
deleted due to a communications The sequence of characters sequence are reserved for
timeout. use by the RODM Collection Manager. The entry field
cannot contain this sequence of characters.
The delete request was sent to the NetView sequence
management console server, but a response was not The character string that was entered into an entry
received within the expected timeout period. field.

System action IHS1452E The Display ID of NMC and TBSM
does not match. TBSM will not be
After the OK button is pushed on the message box, the
launched.
entry field containing the sequence string is activated,
enabling the character string to be replaced.
Explanation
Operator response This message only applies to UNIX environments. The
NetView management console $DISPLAY ID does not
Remove the sequence of characters sequence from
match Tivoli Business Service Manager.
the entry field and retry the request.
IHS1450W Name of Resource is an object of a System action
SNA Topology Manager Class that
is not supported when launching The resource is not displayed in Tivoli Business
to TBSM from NMC. Service Manager.
There are 4 classes from the SNA Topology Manager Change the NetView management console display ID
Data Model that are not supported when launching to match that of the computer on which Tivoli Business
from the NetView management console to Tivoli Service Manager is installed.
Business Service Manager. These classes are as IHS1453E There is an error on line line
follows: number in TBSMLaunch.dat.
• SNA Node Launch will not proceed. Error
code: error code. Refer to online
• T2-1Node
help for code description.
• SNA Local Topology (EN)
• SNA Local Topology (NN) Explanation
Message Variables There is an error on the line number indicated in this
Name of Resource message which is located in the TBSMLaunch.dat file
The SNA Topology Manager resource object that is in the settings directory on the server.
not supported. Message Variables
line number
System action The line number, in the TBSMLaunch.dat file, on
The resource is not displayed in Tivoli Business which the error occurred.
Service Manager. error code
This field can contain any of the following error
codes:
attempting to display the resource
in TBSM. • 1001 - Line did not contain a required KEY. Valid
keys are:
Explanation – PLATFORM
An error occurred in launching Tivoli Business Service – MIN_PORT
Manager.
– WAIT_TIME
– RETRY_COUNT
System action
– PROGRAM_NAME
The resource is not displayed in Tivoli Business
Service Manager. – ROGRAM_DATA
• 1002 - The field on the line number indicated
Operator response must contain an integer.
Ensure that Tivoli Business Service Manager is • 1003 - The line number indicated must contain a
installed. If the TBSMLaunch.data file does not fully ":" delimiter between the key and the data of the
qualify the command line to the program, add the key. For example: PLATFORM: Windows.
appropriate Tivoli Business Service Manager directory • 1004 - The data on the line number indicated is a
to the PATH. blank. This field requires data.
• 1005 - An ambiguous problem exists on the line IHS1456E An error occurred during launch
number indicated. processing. TBSM will not be
launched.
System action
Explanation
Service Manager. The Tivoli Business Service Manager launch failed
during processing of the TBSMLaunch.dat file.
Operator response
System action
Correct the data on the line number indicated in the
TBSMLaunch.dat file. Tivoli Business Service Manager is not launched.
IHS1454E There is no definition for operating
system Operating System in the Operator response
launch. TBSM will not be Check the TBSMLaunch.dat file for incorrect syntax.
launched.
IHS1457E The ports specified in
TBSMLaunch.dat cannot be
Explanation
acquired.
An entry for the operating system on which you are
running does not exist in the TBSMLaunch.dat file. The Explanation
operating system name is case sensitive.
The ports specified in the TBSMLaunch.dat file cannot
Message Variables be acquired.
operating system
Name of operating system on which you are System action
running.
Tivoli Business Service Manager is not launched.
System action IHS1500E An error has occurred while

processing a command request.
Exit name: exitName Exit RC:
Service Manager.
exitRC Command: command
Operator response
Explanation
Add an entry for the operating system on which you
An error occurred on the server while calling a
are running or correct the syntax for your operating
command exit.
system in the TBSMLaunch.dat file.
Message Variables
IHS1455E TBSM application can not be
started. exitName
The name of the command exit.
Explanation exitRC
Return value from the exit invocation.
The Tivoli Business Service Manager application
cannot be started. command
The text of the command.
System action
System action
Tivoli Business Service Manager is not launched.
The command request is ignored.
Operator response
Operator response
Ensure that the PROGRAM_NAME field in the
TBSMLaunch.dat file is set correctly. The fully qualified Contact your system programmer.
path to the TBSMConsole.exe file must be either in the
PATH or PROGRAM_NAME field.

System programmer response exitRC
Save the server workstation error log file. Contact the
Tivoli Support Center to check records of logged errors command
for more information. The text of the command.
IHS1501E An error has occurred while

System action
The command exit was not The command request is ignored.
installed. Exit name: exitName Exit
RC: exitRC Command: command Operator response
If you cannot solve the problem, contact your system
Explanation
programmer.
The command exit is not installed at the server
workstation. System programmer response
Message Variables Ensure that the IP or LU 6.2 communication session
exitName between IBM Z NetView and the server is started. If
The name of the command exit. necessary, issue the NETCONV ACTION=START name
command from IBM Z NetView to start the
exitRC communication session.
command IHS1503E An error has occurred while
The text of the command. processing a command request.
The operator is no longer logged
on to host IBM Z NetView. Exit
System action
name: exitName Exit RC: exitRC
The command request is ignored. Command: command

Contact your system programmer. The command request cannot be verified for
authorization because of one of the following reasons:
System programmer response • The operator is not logged onto IBM Z NetView.
Install the program specified in the Exit name field of • The operator ID is not defined.
the selected command on the server workstation. The • The password or password phrase is not correct.
Exit name field is defined using the command profile
editor. • The password or password phrase is expired.
Message Variables
processing a command request. exitName
The topology server was unable to The name of the command exit.
communicate with IBM Z NetView. exitRC
Exit name: exitName Exit RC: Return value from the exit invocation.
exitRC Command: command
command
The text of the command.
Explanation
An error occurred for one of the following reasons: System action
• The required IP or LU 6.2 communication session The command request is ignored.
between the server and the IBM Z NetView program
is not active.
Operator response
• IBM Z NetView is busy processing other requests.
If you are not currently logged on to the IBM Z
Message Variables NetView program, log on and retry the request.
exitName
If you are currently logged on to the IBM Z NetView System action
program, correct the operator ID and password or
password phrase.
IHS1504E The command request could not Operator response
be processed. A previous
command request has not Ensure that the operator ID was entered correctly, or
completed. Exit name: exitName enter another operator ID that is authorized to use
Exit RC: exitRC Command: commands.
command
Explanation If the operator ID must have authorization for
The command exit cannot complete this request commands, change the NGMFCMDS keyword in the
because a prior request is still processing. The operator profile to YES.
command exit might be waiting for a user action. IHS2000E The topology server is ending due
Message Variables to an internal error. The databases
will not be saved, therefore they
exitName may not reflect the latest changes.
exitRC Explanation
The topology server is ending because of an internal
command error. The databases will not be saved, therefore they
The text of the command. will not reflect the latest changes.

The command request is ignored. The topology server ends.

At the workstation where the command exit is running, Contact your system programmer.
complete the actions required by the command exit.
These might include closing any active windows,
completing entry fields, and others.
Collect the logs in $BINDIR/TDS/Server/log. Restart
the topology server processes. If the problem persists,
The operator is not authorized to
use commands on NetView host. IHS2001W Views from RODM are not
Exit name: exitName Exit RC: supported. The level of IBM Z
exitRC Command: command NetView is incompatible with the
server.
Explanation
Explanation
The operator ID you specified in either the topology
console Sign On window or the IBM Z NetView Sign On A NETCONV command was issued from an
window is not authorized to use IBM Z NetView incompatible version of the IBM Z NetView program
commands. and specified this workstation as the destination.
Message Variables
System action
exitName
The name of the command exit. The NETCONV session is still established, commands
to IBM Z NetView are still allowed, and business views
exitRC
(instrumentation) can still be supported. However,
views that are retrieved by GMFHS (Graphic Monitor
command Facility host subsystem) out of RODM (Resource
The text of the command. Object Model) are not supported.

Contact your system programmer. The backup database is copied to the current database
and initialization continues.
Operator response
If you need to display the views out of RODM, then
install the correct version of the IBM Z NetView If the topology server initializes, no additional action is
program. See the IBM Z NetView Installation: Migration needed.
Guide for information on migration.
IHS2002E The topology server is ending due System programmer response
to a missing DLL file. Determine the cause of database corruption. Possible
causes are:
Explanation • A server trap
The topology server is ending because of a missing • Out of disk space during server termination
library.
• Files deleted from the database.
Operator response If the backup databases are also corrupted, stop the
server, erase the backup databases, and then restart
Check that the $BINDIR/TDS/Server/bin directory is the server using the default databases.
included in the PATH environment variable. Check this
directory to ensure that the DLL is in this directory. IHS2021E The topology server is ending due
to an internal error. The databases
System programmer response will not be saved, therefore they
may not reflect the latest changes.
IHS2003E The topology server is already Explanation
active. Only one instance of the These errors are usually caused by a failure associated
server is allowed. This instance of with the execution of a system function that is
the topology server will end. unrecoverable. The topology server is unable to save
the databases because of this error. Therefore, any
Explanation changes that have been made since the topology
server was last started might be lost.
You can only start one instance of the topology server
at a time.
System action
System action The topology server process ends. It does not write
the databases out to disk. Therefore, updates, such as
This instance of the topology server ends.
added resources and customization, might be lost.
Operator response
Operator response
Operator response
If you want to restart the server, stop the current
Stop the remaining server processes, then restart the
instance of the server, then restart. Otherwise, no
topology server.
action is required.
IHS2022E The topology server is ending due
IHS2020E Corrupt datab databases
to insufficient available threads.
detected. Restoring from the
The maximum number of threads
backup databases.
has been started.
Explanation
Explanation
The current database was corrupted.
The topology server allows a maximum of 64 threads
to run concurrently. The maximum number is already
running. This error might be the result of an earlier Operator response
error which has prevented previously started threads
from terminating.

System action
Do the following:
The topology server process ends. All databases are
written to disk before termination. 1. Add more swapping or paging space to the system.
2. Add more physical memory, if possible.
Operator response 3. Restart the topology server. If the problem
Contact your system programmer. persists, contact IBM Software Support.
IHS2026E Corrupt backup databases
System programmer response detected. Restoring from the
Restart the topology server daemon. If the problem default databases.
Explanation
to insufficient memory. Free or The backup databases are corrupted. The databases
add memory in the system, then are located in one of the following directories:
restart the topology server. • Intel: %BINDIR%\TDS\server\db\backup\datab
• UNIX: $BINDIR/TDS/server/db/backup/datab
Explanation
The topology server tried to obtain (malloc) storage System action
but was unable to.
The default database is copied to the current database
System action
The topology server process ends. All databases are Operator response
written to disk before termination.
If the server initializes satisfactorily, no additional
action is needed.
Operator response
Determine the cause of the database corruption.
Possible causes are:
Do the following:
• A server trap
1. Increase the amount of swapping or paging space • Out of disk space during server termination
on the system.
• Files deleted from the database.
2. Add more memory, if possible.
Erase the backup databases and restart the server
3. Restart the topology server. If the problem
using the default databases.
IHS2027E The topology server cannot
IHS2025E The topology server cannot
continue due to insufficient disk
continue due to insufficient
space. The topology server will
memory.
terminate.
Explanation
Explanation
The system has a resource shortage, either with
One of the disks used by the topology server is full.
swapping, paging space, or physical memory.
System action
System action
The topology server process will end.
The server process ends.

Contact your system programmer. The data sent over this connection is ignored.

Do the following: Contact your system programmer.
1. Add more space to the file system, if possible.
2. If the disk that is full contains the topology server
databases and additional space cannot be added to Install the correct version of the IBM Z NetView
the drive or file system, move the topology server program. This workstation cannot communicate with
databases to a new disk and filesystem by copying down-level versions of IBM Z NetView. See the IBM Z
all files and directories below and including NetView Installation: Migration Guide for information
$BINDIR/TDS/Server/db to the new disk. Set the on migration.
topology_DB environment variable to the new
IHS2032W The session between topology
location. Also make sure you update the
server and host NetView program
$BINDIR/TDS/Server/bin/tserver.sh file.
had ended. Contact your system
3. Restart the topology server. programmer responsible for the
topology server.
IHS2028E The workstation has received
information that is not valid from
the host. Explanation
The communications session between IBM Z NetView
Explanation and the topology server has ended. The reason is
unknown.
Data was received that did not contain valid header
information. The topology server does not understand
how to process the data. The data will be written to System action
the error log and then discarded. The topology server continues to run, but is unable to
send commands to IBM Z NetView or to query
System action information.
The data is written to the topology server error log and
then discarded. Operator response
Operator response
Restart the connection between host IBM Z NetView
System programmer response and the topology server by issuing the NetView
NETCONV command. If the connection continues to
If the problem persists, stop and restart the topology
fail, contact IBM Software Support. The topology
server. If this does not correct the problem, contact
server error and message logs might provide
IHS2030W An incompatible version of IBM Z
IHS2035E No backup databases found.
NetView has attempted to
Restoring from the default
establish a session to the topology
databases.
server. The data sent over this
connection is ignored.
Explanation
Explanation The backup database was empty or missing files.
A NETCONV command was issued from an
incompatible version of the IBM Z NetView program System action
and specified this workstation as the destination. The default database is copied to the current database
If the server initializes, no additional action is needed. Contact your system programmer.

Determine why the backup database files were not Restore the default databases in directory
found. The most likely reason is that files in the $BINDIR/TDS/Server/db/default/datab, then restart
backup directory were deleted. the topology server.
IHS2037E The topology server is ending due IHS2042E IHS2042E: The topology server is
to missing subdirectories. Contact ending due to a failure copying
the system programmer databases. Contact your system
responsible for the topology programmer responsible for the
server. topology server.
The topology server is dependent on a specific The topology server was writing data to its database
directory structure below $BINDIR/TDS/Server/db. when a write action failed. The specific write action
This structure does not exist, so specific files such as that failed is written to the topology error log.
databases, icons, help, backgrounds, and BDF and
CDF files might be missing. System action
The topology server ends.
System action
The topology server ends. Operator response
Operator response
Do the following:
1. Ensure that there is sufficient disk space and
This problem is generally the result of directories
proper permissions on the $BINDIR/TDS/Server/db
missing below $BINDIR/TDS/Server/db. Restore the
directory and subdirectories.
missing subdirectories and restart the topology server.
2. Restart the topology server.
3. If the problem persists, contact your Tivoli Support
to missing default databases.
Center.
Contact your system programmer
responsible for the topology IHS2048E The topology server cannot
server. initialize because the databases
are being accessed by another
Explanation process. The topology server will
end.
The topology server cannot find databases under the
current or backup subdirectories, so it is looking for
databases under the default subdirectory. The Explanation
topology server must have a set of databases to start. Only one process can access the topology databases
The default databases under $BINDIR/TDS/server/db/ at a time. Another process, possibly another instance
default/datab (UNIX) or %BINDIR%/TDS/server/db/ of the topology server, has the databases open.
default/datab (Intel) are shipped with the product, but
have either been erased or are inaccessible because of
System action
directory permissions.
The topology server process ends.
System action
Operator response

If the topology server is currently running, you will Record the view name from the message window.
need to stop it before another image can be started. If Contact your system programmer responsible for
the topology server is not running, do the following: RODM.
• UNIX: Run tserver stop -f twice, then restart the
server. System programmer response
• Intel: Use the Task Manager to check that no Check the IBM Z NetView Graphic Monitor Facility host
topology server processes or command exits are subsystem (GMFHS) and RODM logs for specific
running. If they are, stop them, then restart the information about which class, object, or attribute is
server. not correctly specified. Correct the RODM definition
error.
If the problem persists, reboot the computer. If this
does not correct the problem, contact IBM Software IHS2056E The host reported an error while
Support. processing a request from the
topology server. Information may
IHS2049E The topology server is ending due not be correct at the workstation.
to an error accessing a database. Contact your system programmer
The databases will not be saved, responsible for RODM.
therefore they may not reflect the
latest changes.
Explanation
Explanation The host cannot fully process a request from the
topology server. The information presented at the
The topology server was trying to either read from or workstation might not be accurate.
write to a database when the action failed.
System action
System action
The topology server continues.
Operator response
Operator response
Contact your system programmer responsible for
Contact your system programmer. RODM.

Restart the topology server. If the error persists, then Check the IBM Z NetView Graphic Monitor Facility host
contact IBM Software Support. subsystem (GMFHS) and RODM logs for specific
IHS2053E Objects required to create view are information about the error. Once the error has been
in error. Contact your system corrected, recycle the connection to the topology
programmer responsible for server that reported the error.
RODM. IHS2057W The host detected view names
that were not valid while
Explanation processing a request from the
The view cannot be created because an error was topology server. Contact your
detected in a Resource Object Data Manager (RODM) system programmer responsible
class, object, or attribute specification. for RODM.

view There are two possible causes for this message:
The view name.
• The host detected network or exception view names
System action that were the same except for case. All except the
first were discarded.
The view is not created.
• The host detected a network or exception view name
that is longer than 32 characters.
System action resource
The name of the selected resource or None, if a
The topology server continues.
resource was not required to be selected for the
command.
Operator response
exitRC
Contact your system programmer responsible for Return value from IhsiSend function call.
RODM. exit parameters
Key value pairs displaying the fields from the
System programmer response EGVE_PARAMETERS32 structure in ihsiexit.h.
Check the RODM log for specific information about the
error. Once the error has been corrected, recycle the System action
connection to the topology server that reported the The command request is ignored.
error.
IHS2058W The resource does not support this Operator response
view request.
Explanation
The IBM Z NetView Graphic Monitor Facility host
Save the server workstation error log file. Contact the
subsystem (GMFHS) cannot create a view for the view
Tivoli Support Center to check records of logged errors
request on a particular resource.
The Resource Object Data Manager (RODM) class
definition for a resource does not include the IHS2068I An error has occurred while
requested view type. processing a command request.
Necessary system resources were
not available for command exit
System action
execution. Command: command
The topology server continues. Resource: resource Exit RC: exitRC
Exit Parms: exit parameters
Operator response
Explanation
A command request cannot be processed because of
System programmer response inadequate system resources, such as memory or disk
space, at the command exit workstation.
information about which class, object, or attribute Message Variables
caused the problem. command
To support the view type, add the appropriate VIO to The selected command.
the RODM definition. If necessary, correct the RODM resource
definition error. The name of the selected resource or None, if a
IHS2067W An error has occurred while command.
sending a command request to the
topology server. Command: exitRC
command Resource: resource Exit Return values from IhsiSend function call.
RC: exitRC Exit Parms: exit exit parameters
parameters Key value pairs displaying the fields from the
EGVE_PARAMETERS32 structure in ihsiexit.h.
Explanation
System action
An error occurred on the server while calling a
command exit. The command request is ignored.
Message Variables
command
The selected command.

At the server workstation, do one or more of the Install the program specified in the Exit name field of
following: the selected command on the server workstation. The
Exit name field is defined using the command profile
• Close unnecessary views to free system resources.
editor.
• Close unnecessary applications to free system
resources. IHS2070W An error has occurred while
• Check the amount of free disk space of the paging The topology server was unable to
file. communicate with the NetView
• If necessary, free disk space by deleting files that program. Command: command
are no longer required. Resource: resource Exit RC: exitRC
• If necessary, install more workstation memory. Exit Parms: exit parameters
Then retry the request. If you cannot solve the

Explanation
problem, contact your system programmer.
An error occurred for one of the following reasons:
System programmer response • The required IP or LU 6.2 communication session
Save the server workstation error log file. Contact the between the server and the IBM Z NetView program
Tivoli Support Center to check records of logged errors is not active.
for more information. • IBM Z NetView is busy processing other requests.
IHS2069W An error has occurred while Message Variables
command
The command exit was not
installed. Command: command
Resource: resource Exit RC: exitRC resource
Exit Parms: exit parameters The name of the selected resource or None, if a
command.
Explanation
exitRC
The command exit is not installed at the server Return values from IhsiSend function call.
workstation.
exit parameters
Message Variables Key value pairs displaying the fields from the
command EGVE_PARAMETERS32 structure in ihsiexit.h.
resource System action
The name of the selected resource or None, if a The command request is ignored.
command. Operator response
exitRC
If you cannot solve the problem, contact your system
Return values from IhsiSend function call.
programmer.
exit parameters
Ensure that the IP or LU 6.2 communication session
System action between IBM Z NetView and the server is started. If
necessary, issue the NETCONV ACTION=START name
The command request is ignored. command from IBM Z NetView to start the
communication session.
Operator response
IHS2071W An error has occurred while
Contact your system programmer. processing a command request.
No domains were found for the
resource. Command: command
Resource: resource Exit RC: exitRC • The operator is not logged onto IBM Z NetView.
Exit Parms: exit parameters • The operator ID is not defined.
• The password or password phrase is not correct.
Explanation
• The password or password phrase is expired.
resource was not found in any NetView domain. For
resources managed by the SNA topology manager, this Message Variables
can occur when translating the SSCP names that have command
reported this resource into a NetView domain name. The selected command.
This can happen if:
resource
1. Task DSI6DST is not active in the IBM Z NetView The name of the selected resource or None, if a
that resides at the SSCP node. resource was not required to be selected for the
2. The PPI is not active in the IBM Z NetView that command.
resides at the SSCP node. exitRC
3. The NetView program is not using VTAMCP Return values from IhsiSend function call.
USE=YES in DSIDMN in the IBM Z NetView that exit parameters
resides at the SSCP node. Key value pairs displaying the fields from the
Message Variables
command System action
resource
resource was not required to be selected for the Operator response
command. If you are not currently logged on to the NetView
exitRC program, log on and retry the request.
Return values from IhsiSend function call. If you are currently logged on to the NetView program,
exit parameters correct the operator ID and password or password
Key value pairs displaying the fields from the phrase.
System action
The command string does not
The command request is ignored. represent a valid command.
Command: command Resource:
Operator response resource Exit RC: exitRC Exit
Parms: exit parameters
Explanation
The command string is not a valid command.
It might be necessary to start the DSI6DST or the PPI
task at the remote NetView program or code VTAMCP Message Variables
USE=YES in DSIDMN at the remote NetView program. command
processing a command request. resource
The operator is no longer logged The name of the selected resource or None, if a
on to host NetView. Command: resource was not required to be selected for the
command Resource: resource Exit command.
RC: exitRC Exit Parms: exit exitRC
parameters Return values from IhsiSend function call.
exit parameters
Explanation Key value pairs displaying the fields from the
The command request cannot be verified for EGVE_PARAMETERS32 structure in ihsiexit.h.
authorization because of one of the following reasons:

System action operation is not available. Some possible definition
errors are:
• A command exit expects to receive control
Operator response information in the command string field, but the
command definition has left the field empty.
Correct the command string if it is one you entered
• A command exit expects to receive information
yourself. If not, contact your system programmer.
about a specific resource, but the command
definition specifies a command enablement attribute
System programmer response of Resource independent.
Use the command profile editor to correct the Another possible reason for this error is that you
command string, if necessary. issued the command against an aggregate resource,
IHS2074W The command request for resource but the command you issued does not support
resource could not be processed. A aggregates.
previous command request has not Message Variables
completed.
command
Explanation
resource
The command exit cannot complete this request The name of the selected resource or None, if a
because a prior request is still processing. The resource was not required to be selected for the
command exit might be waiting for a user action. command.
Message Variables exitRC
command Return values from IhsiSend function call.
The selected command. exit parameters
resource Key value pairs displaying the fields from the
The name of the selected resource or None, if a EGVE_PARAMETERS32 structure in ihsiexit.h.
command. System action
System action
The command request is ignored. Operator response
Operator response
At the workstation where the command exit is running, System programmer response
complete the actions required by the command exit. Use the command profile editor to correct the
These can include closing any active windows, command definition, if necessary.
completing entry fields, and others.
IHS2075W The command exit detected an processing a command request.
error or inconsistency while The return code is in the user
validating the command exit data. specified range. Command:
Command: command Resource: command Resource: resource Exit
resource Exit RC: exitRC Exit RC: exitRC Exit Parms: exit
Parms: exit parameters parameters
The data passed to the command exit was either not A command exit returned a return code from the
valid or was not consistent with the exit's IhsiSend API in the user-specified range. This range is
requirements. The command request cannot be defined in the ihsiexit.h header file.
processed.
Message Variables
The most probable cause is that the command
definition is not correctly specified. When the command
command exit is driven, data necessary for proper The selected command.
resource Operator response
Make sure that you entered the operator ID correctly,
or enter another operator ID that is authorized to use
command.
commands.
exitRC
Return values from IhsiSend function call. System programmer response
exit parameters
If the operator ID must have authorization for
commands, change the NGMFCMDS keyword in the
operator profile to YES.
System action IHS2078E Unable to sign on to IBM Z

NetView. User name 'username' is
The command request is ignored. not authorized to use
administration functions.
Operator response
The specified user name is not authorized to perform
System programmer response administration functions.
Contact the provider of the command exit. Message Variables
IHS2077W An error has occurred while username
processing a command request. The user name you entered. It can be blank if no
The operator is not authorized to user name was entered.
use commands on NetView host.
Command: command Resource: System action
resource Exit RC: exitRC Exit
Parms: exit parameters The IBM Z NetView Sign On Window displays again.
The operator ID you specified in either the topology If you do not want to perform administration, do the
console Sign On window or the IBM Z NetView Sign On following:
window is not authorized to use IBM Z NetView 1. Select the Cancel button.
commands.
2. Sign off the console
Message Variables
3. Sign on again, but this time deselect Administrator
command access in the Sign On window.
If you want to perform administration, make sure that
resource you entered the name correctly, or enter another name
The name of the selected resource or None, if a that is authorized to use administration functions.
command. If the problem recurs, contact your system
exitRC responsible for IBM Z NetView security administration.
exit parameters System programmer response
EGVE_PARAMETERS32 structure in ihsiexit.h. If the operator ID must have authorization for
administration functions, change the NGMFADMN
keyword in the operator profile to YES.
System action
IHS2079E Unable to sign on to IBM Z
NetView. User name username is
not authorized to use IBM Z
NetView.

The specified user name is not authorized to sign on to If you want IBM Z NetView to automatically log on this
IBM Z NetView for one of the following reasons: user name, use the AUTOLOGN parameter of the IBM
Z NetView DEFAULTS command.
• The user name is not defined.
• The password or password phrase is not correct. IHS2082W An error has occurred while
• The password or password phrase has expired. The IBM Z NetView domain ID is
syntactically incorrect. Command:
System action command Resource: resource Exit
The IBM Z NetView Sign On Window displays again. RC: exitRC Exit Parms: exit
parameters
Operator response
Explanation
Make sure that you entered the user name and
password or password phrase correctly, then try to The NetView domain ID contains incorrect syntax. The
sign on again. domain ID must meet the following criteria.
• It must be between 1 and 5 characters in length.
IHS2080E Topology server internal error.
• The first character must be alphabetic (either upper
Explanation or lower case) or one of the following national
characters: @ # $.
An internal error occurred in the topology server.
• The remaining characters (second through fifth)
must be alphabetic (either upper or lower case),
Operator response numeric, or one of the following national characters:
Contact your system programmer. @ # $.
Message Variables
command
Contact IBM Software Support. The selected command.
IHS2081E Unable to sign on to IBM Z resource
NetView. User name username is The name of the selected resource or None, if a
not logged onto IBM Z NetView. resource was not required to be selected for the
command.
Explanation exitRC
You cannot sign on because you are not currently
logged on to IBM Z NetView. You must be logged onto exit parameters
IBM Z NetView so that the topology server can send Key value pairs displaying the fields from the
commands from the console to IBM Z NetView for EGVE_PARAMETERS32 structure in ihsiexit.h.
execution.
System action
Message Variables
username
The user name you entered.
Operator response
System action Correct the domain ID and retry.
The IBM Z NetView Sign On Window displays again. IHS2083E Database checkpoint failed.
Databases may be corrupt.
Operator response
Explanation
Log on to IBM Z NetView and try to sign on again.
An error occurred during the database checkpoint
process. The checkpoint cannot be completed.
System action IHS2130E correlator Error code waiting for
command response for command.
Explanation
Operator response
An error was encountered while waiting for a
Restart the server to restore from the backup
command response.
databases.
Message Variables
IHS2128E correlator Error code locating
command response for command. correlator
A code that corresponds to the previous
Explanation informational message.
code
The topology server was unable to locate the
The command error code.
command response for a topology server command.
command
Message Variables The command for which a response is expected.
correlator
A code that corresponds to the previous Operator response
informational message.
code
The command error code.
command
The command for which no response was located. Contact IBM Software Support.
IHS2131E Incorrect discover connections
Operator response response.
Explanation
System programmer response An incorrect response was received from an discover
Contact IBM Software Support. connections task issued by the topology server.
IHS2129E correlator Error code issuing Operator response

command command.
Explanation
An error was received while attempting to issue an
topology server command. Contact the support group responsible for the
instrumentation of the application.
Message Variables
IHS2132I Deleting non-reported connection
correlator name.
A code that corresponds to the previous
informational message.
Explanation
code
The command error code. A connection that was previously reported for this
component was not reported in the discover
command
connections response and will be deleted.
The issued command.
Message Variables
Operator response name
Contact your system programmer. The name of the connection that was not reported.
IHS2133I The server must be run under a
System programmer response user ID that has 'Act as part of the
operating system' user right. The
If you cannot correct the problem, contact IBM
server is ending.
Software Support.

'Act as part of the operating system' user rights are not Contact your system programmer.
assigned to the NT user account under which the
server runs. System programmer response
Reinstall the server.
System action
IHS2152I Waiting up to number seconds for
The server ends.
command_exit to terminate.
Operator response
System action
Contact your NT system administrator responsible for
The topology server will eventually end.
user accounts.
System programmer response to an internal error. The resource
type database has been corrupted.
See the IBM Z NetView Installation: Getting Started for It appears that BDF or CDF files
information on installing the topology server on an NT have been deleted or modified.
system. You must grant specific user rights to the
account where the server is run.
Explanation
IHS2134E Unknown event class received
The current set of description files is missing data that
class.
the server needs to initialize properly. The server
cannot start.
Explanation
An unknown event was received. System action
Message Variables The topology server ends.
class
The name of the event class that was received. Operator response
Operator response
• Replace the old set of description files.
Contact your system programmer. • Erase the current and backup server databases and
restart.
IHS2165E No missingCompType was found
Investigate to determine whether the instrumentation below lastDescFile in the
is sending the correct information event class. description file hierarchy.
IHS2135E The server detected an installation Component ID Group information:
error: rc. Manufacturer: manufacturer
Product: product Version: version
Component Type:lastCompType
Explanation
The server detected a corrupted file during Explanation
initialization.
The topology server has found an incomplete branch in
Message Variables the tree. The information expected to be in the missing
Description of message variables, if any. M;P;V triplet is displayed.
rc Message Variables
The server internal return code. missingCompType
Component type that is missing
System action lastDescFile
The server ends. Filename of the description file with missing
component type
manufacturer Operator response
Manufacturer of missing component type
Do the following:
product
Product of missing component type 1. Check the description files for a missing or
incorrect file and correct the problem.
version
Version of missing component type 2. Restart the server.
lastCompType 3. If the server restarts with no errors and information

Component type of the description file with is still missing, erase the server databases and
missing component type restart the server. Erasing the databases will cause
you to lose any customization you might have done.
Below are the possible combinations of lastDescFile For that reason, create a backup prior to erasing
type and missingCompType: the databases so that you can restore them if the
For Business systems only: problem persists.
• lastDescFile = business system description file IHS2166W Unable to find match for
relationship in CDF file.
• missingCompType = business subsystem component Relationship type: relationship
type type Direction: relationship
For Business systems only: direction Mapping file: BDF
filename Component file: CDF
• lastDescFile = business subsystem description file filename
missingCompType = business subsystem component
type
Explanation
• missingCompType = business component
component type The topology server cannot find the specified
relationship (found in a mapping or business
The first two are for business systems only because component file) in the CDF.
applications, databases and middleware do not have
subsystems. Message Variables
For applications, databases middleware systems only relationship type
The relationship type name specified in the BDF.
lastDescFile = business system description file
relationship direction
missingCompType = business component
The relationship direction specified in the BDF.
component type
BDF filename
The next pairs can apply to any of the types of Filename of the BDF that the relationship is
software systems: referenced.
• – lastDescFile = business subsystem description file CDF filename
– missingCompType = business component Filename of the CDF that is referenced by the
component type specified BDF.
lastDescFile = business component description file
missingCompType = business mapping component System action
type The topology server continues with missing
lastDescFile = business mapping description file information.
missingCompType = software component component
type Operator response
You will not see this combination because GDFs are Do the following:
optional: lastDescFile = component description file 1. Check the description files for a missing or
missingCompType = application component type incorrect group descriptions and correct the
problem.
System action
2. Restart the server.
The topology server continues with missing 3. If the server restarts with no errors and information
information. is still missing, erase the server databases and
restart the server. Erasing the databases will cause

For that reason, create a backup prior to erasing name
the databases so that you can restore them if the Name of the monitor that was not found in CDF.
problem persists. instance
IHS2167W Unable to find match for task task Monitor instance value of the monitor that was not
name in CDF file. Mapping file: BDF found. If this instance value if 0 it represents an
filename Component file: CDF Asynchronous Monitor, any other value indicates a
filename Synchronous Monitor Instance.
BDF filename
Explanation Filename of the BDF that specified or tried to map
the specified monitor.
The topology server cannot find the specified task
(found in a mapping or business component file) in the CDF filename
CDF. Filename of the CDF that is referenced by the
specified BDF.
Message Variables
task name System action
Name of task that was not found in CDF. The topology server continues with missing
BDF filename information.
Filename of the BDF that specified or tried to map
the specified task. Operator response
CDF filename
Do the following:
Filename of the CDF that is referenced by the
specified BDF. 1. Check the description files for a missing or
incorrect monitor and correct the problem.
System action 2. Restart the server.
The topology server continues with missing 3. If the server restarts with no errors and information
Operator response you to lose any customization you might have done.
For that reason, create a backup prior to erasing
Do the following: the databases so that you can restore them if the
1. Check the description files for a missing or problem persists.
incorrect task and correct the problem. IHS2169E Internal error message in file
2. Restart the server. filename.
3. If the server restarts with no errors and information
is still missing, erase the server databases and Explanation
restart the server. Erasing the databases will cause An internal error occurred during processing of the
you to lose any customization you might have done. specified file. The error message will indicate the
For that reason, create a backup prior to erasing problem.
the databases so that you can restore them if the
problem persists. Message Variables
IHS2168W Unable to find match for monitor message

name instance instance in Message indicating problem.
component file. Mapping file: BDF filename
filename Component file: CDF Filename of BDF or CDF being processed at the
filename time of the error.

The topology server cannot find the specified monitor The topology server continues with missing
(found in a Mapping or Business Component file) in the information.
CDF.
Do the following:
1. Check for available system resources, memory, and IHS2172W No synchronous monitor group
disk space, and correct the problem. information was found.
2. Restart the server. Insufficient data to create
monitors.
is still missing, erase the server databases and
restart the server. Erasing the databases will cause Explanation
you to lose any customization you might have done. A synchronous monitor instance group was defined,
For that reason, create a backup prior to erasing but the topology server cannot find a synchronous
the databases so that you can restore them if the monitor group or table. The monitor instances cannot
problem persists. be properly created. The next message will indicate
4. If the problem recurs, contact IBM Software the file in which the error was found. The topology
Support. server uses synchronous monitor instances as
specified in the AMS (Application Management
IHS2171I No information found for group Specification). In order to create these instances it
group in file filename. needs to correlate information from the synchronous
monitor instance group, which specifies monitor
Explanation instances, and the synchronous monitor group, which
contains a base template of information. If a monitor
The topology server cannot find a group description, or
name specified in a monitor instance is not included in
a table, for the specified group. The group is not a
the synchronous monitor group, the topology server
required group, so this does not necessarily indicate
does not have sufficient information available to use
an error. Some groups that the topology server uses
the monitor.
are optional. For example, groups like the Icon and
Help groups provide additional information to make
the product more usable. Specifying monitors or System action
connections for a business system is also optional. If The topology server continues with missing
information appears to be missing on the topology information.
console, a missing or improperly defined group might
be the problem. If the desired group must be present,
Operator response
corrective action is needed.
Do the following:
Message Variables
1. Correct or replace the file in which the error was
group
found.
Name of group in description file.
file name
File name of BDF or CDF with missing group 3. If the server restarts with no errors and information
System action
The topology server continues. the databases so that you can restore them if the
problem persists.
Operator response
IHS2173E Internal error parsing group group
Do the following, if necessary: in file filename. RC = return code
1. Check the description files for missing information
and correct the problem, if desired. Explanation
2. Restart the server. An error occurred while parsing the specified group.
3. If the server restarts with no errors and information Message Variables
group
Name of group where error occurred.
For that reason, create a backup prior to erasing filename
the databases so that you can restore them if the Filename of BDF or CDF that contains the specified
problem persists. group.

return code 1. Correct or replace the specified file.
Return code from parser. Used for 2. Restart the server.
System action
The topology server continues with missing restart the server. Erasing the databases will cause
information. you to lose any customization you might have done.
Operator response the databases so that you can restore them if the
problem persists.
Do the following:
IHS2175W Error - duplicate path definition.
1. Check the syntax of the specified group and make
any necessary corrections.
Explanation
A duplicate path description was specified in the CDF
3. If the server restarts with no errors and information file. A previous message indicated the file in which the
is still missing, erase the server databases and error was found.
System action
the databases so that you can restore them if the The topology server continues.
problem persists.
IHS2174W No match was found in the Operator response
synchronous monitor group for Do the following:
monitor instance name in file file?
1. Correct or replace the specified file.
Explanation 2. Restart the server.
The topology server cannot find a monitor with the 3. If the server restarts with no errors and information
specified name in the synchronous monitor group, so a is still missing, erase the server databases and
monitor instance cannot be created. The topology restart the server. Erasing the databases will cause
server uses synchronous monitor instances as you to lose any customization you might have done.
specified in the AMS (Application Management For that reason, create a backup prior to erasing
Specification). In order to create these instances it the databases so that you can restore them if the
needs to correlate information from the synchronous problem persists.
monitor instance group, which specifies monitor IHS2176E Error opening file file. Component
instances, and the synchronous monitor group, which information may be incomplete or
contains a base template of information. If a monitor unavailable.
name specified in a monitor instance is not included in
the synchronous monitor group, the topology server
Explanation
does not have sufficient information available to use
the monitor. The topology server is unable to open the specified
file.
Message Variables
Message Variables
name
Name of monitor being looked for. file
file Filename of BDF or CDF that cannot be opened.
Filename of CDF with error.
System action
System action The topology server is unable to open the file, and
The topology server continues with missing continues with missing information.
information.
Operator response
Do the following: 1. Check the file permissions, and availability of
system resources.
2. Restart the server. the databases so that you can restore them if the
3. If the server restarts with no errors and information problem persists.
is still missing, erase the server databases and IHS2179W Error with group group while
restart the server. Erasing the databases will cause creating object for file file.
Explanation
problem persists. A previous error indicates the actual problem. This
message is provided to help isolate the area in which
IHS2177W Error getting command indicator the error occurred.
for resource.
Message Variables
Explanation group
The topology server was unable to create a command Name of group where error occurred.
indicator for the resource indicated. No commands will file
be available for this resource. Filename of BDF or CDF with incorrect group
information.
Message Variables
resource System action
The name of the resource that did not get a
command indicator. The topology server continues with missing
information.
System action
Operator response
The topology server continues with missing
information. Do the following:
Operator response: 1. Correct or replace the appropriate file.

IHS2178W Error parsing group group. Group
has no key or ID. 3. If the server restarts with no errors and information
Explanation restart the server. Erasing the databases will cause
The specified group does not have an ID or key For that reason, create a backup prior to erasing
specified. The AMS specification requires one of these. the databases so that you can restore them if the
A previous message will indicate the file that is in problem persists.
error.
IHS2180E Internal error during object
Message Variables construction for file file.
group
The name of the group with the missing key or ID. Explanation
An error occurred while constructing an internal object
System action for the specified file.
The topology server continues with missing Message Variables
information.
file
Filename of BDF or CDF object was being created
Operator response
for.
Do the following:
1. Correct or replace the appropriate file. System action
2. Restart the server. The topology server continues with missing
information.
restart the server. Erasing the databases will cause Operator response
you to lose any customization you might have done. Do the following:

1. Correct or replace the appropriate file. Operator response
2. Restart the server. Do the following:
3. If the server restarts with no errors and information 1. Correct or replace the appropriate file.
restart the server. Erasing the databases will cause 2. Restart the server.
you to lose any customization you might have done. 3. If the server restarts with no errors and information
For that reason, create a backup prior to erasing is still missing, erase the server databases and
the databases so that you can restore them if the restart the server. Erasing the databases will cause
problem persists. you to lose any customization you might have done.
IHS2181E Problem parsing file file. the databases so that you can restore them if the
Component information may be problem persists.
incomplete or unavailable.
IHS2183W Error parsing table table, row row,
Explanation col column.
An error occurred while parsing the specified file.

Explanation
Message Variables
An error occurred while parsing the specified table.
file
Message Variables
Filename of BDF or CDF that had parsing problem.
table
System action Name of table where error occurred.
row
Table row number of error.
information.
column
Operator response Column number of attribute with error.
Do the following: System action

1. Correct or replace the appropriate file. The topology server continues with missing
2. Restart the server. information.
is still missing, erase the server databases and Operator response
Do the following:
For that reason, create a backup prior to erasing 1. Correct or replace the appropriate file.
the databases so that you can restore them if the 2. Restart the server.
problem persists.
IHS2182W Error parsing group group. is still missing, erase the server databases and
Component information may be restart the server. Erasing the databases will cause
incomplete or unavailable. you to lose any customization you might have done.
Explanation the databases so that you can restore them if the
problem persists.
An error occurred while parsing the specified group.
Other messages will indicate the actual error and file. IHS2184W Error parsing attribute attribute.
Message Variables
Explanation
group
The name of the group where the error occurred. An error occurred while parsing the specified attribute.
Additional messages will provide more details on the
error.
System action
Message Variables
information. attribute
Name of the attribute in error.
The topology server continues with missing The data type of the specified attribute did not match
information. the one specified in the group description.
Message Variables
Operator response
group
Do the following: Group where error occurred.
1. Correct or replace the appropriate file. attribute
2. Restart the server. Name of attribute in error.
3. If the server restarts with no errors and information expected
is still missing, erase the server databases and Data type expected.
restart the server. Erasing the databases will cause found
you to lose any customization you might have done. Data type found.
the databases so that you can restore them if the System action
problem persists.
IHS2185W Value missing for required information.
attribute. Group: group Attribute
ID: attribute
Operator response
Explanation Do the following:
The specified attribute requires a value, but none was 1. Correct or replace the appropriate file.
specified in the table and no default is defined in the 2. Restart the server.
group description. 3. If the server restarts with no errors and information
Message Variables is still missing, erase the server databases and
group you to lose any customization you might have done.
Name of group with missing attribute. For that reason, create a backup prior to erasing
attribute the databases so that you can restore them if the
ID of attribute with missing value. problem persists.
IHS2187W Error - duplicate attribute ID
System action
specified. Group: group Attribute
The topology server continues with missing name: attribute, ID: id
information.
Explanation
Operator response The specified group contained two attributes with the
Do the following: same attribute ID. Attribute IDs must be unique within
a group.
1. Correct or replace the appropriate file.
Message Variables
3. If the server restarts with no errors and information group
is still missing, erase the server databases and Name of group with error.
restart the server. Erasing the databases will cause attribute
you to lose any customization you might have done. Name of second attribute with matching id.
For that reason, create a backup prior to erasing id
the databases so that you can restore them if the Attribute ID number that is duplicated in this
problem persists. group.
IHS2186W Data type mismatch for group
group, attribute attribute. System action
Expected type: expected Found
type: found
information.

Operator response table
Name of table in error.
Do the following:
row
1. Correct or replace the appropriate file. Table row where error occurred.
3. If the server restarts with no errors and information System action
is still missing, erase the server databases and The topology server continues with missing
restart the server. Erasing the databases will cause information.
the databases so that you can restore them if the Operator response
problem persists. Do the following:
IHS2188W Data type mismatch for attribute 1. Correct or replace the appropriate file.
attribute. Expected type: expected 2. Restart the server.
Found type: found
Explanation
The data type of the specified attribute does not match you to lose any customization you might have done.
that defined in the group description. For that reason, create a backup prior to erasing
Message Variables
problem persists.
attribute
Name of attribute in error. IHS2191W Attribute error in table table, row
row, attribute attribute.
expected
Data type expected.
Explanation
found
Data type found. An error occurred while processing the specified
attribute. Other messages will indicate the problem,
and the file where the error occurred.
System action
Message Variables
information. table
Name of table with error.
Operator response row
Table row in error.
Do the following:
attribute
1. Correct or replace the appropriate file. Name of attribute in error.
3. If the server restarts with no errors and information System action
information.
problem persists. Do the following:
IHS2190W Error - too many attributes in table 1. Correct or replace the appropriate file.
row. Table: table, row row 2. Restart the server.
Explanation
The specified table had too many attributes specified restart the server. Erasing the databases will cause
for the group definition. you to lose any customization you might have done.
Message Variables
the databases so that you can restore them if the Explanation
problem persists.
The enumeration symbol value was not found in the
IHS2192W Error - enum found with no name. group description.
Message Variables
Explanation
symbol
An enumeration was specified with no name. Enumeration symbol that had no corresponding
integer value.
System action
The topology server continues with missing System action
information. The topology server continues with missing
information.
Operator response
Do the following: Operator response
1. Correct or replace the appropriate file. Do the following:
2. Restart the server. 1. Correct or replace the appropriate file.

3. If the server restarts with no errors and information 2. Restart the server.
is still missing, erase the server databases and 3. If the server restarts with no errors and information
restart the server. Erasing the databases will cause is still missing, erase the server databases and
you to lose any customization you might have done. restart the server. Erasing the databases will cause
For that reason, create a backup prior to erasing you to lose any customization you might have done.
the databases so that you can restore them if the For that reason, create a backup prior to erasing
problem persists. the databases so that you can restore them if the
problem persists.
IHS2193W Error - enum name not found.
IHS2195W Error - enum error in attribute
Explanation attribute.
The enumerated type specified was not found in the
group description. Explanation
Message Variables There was a general syntax error in the specified

attribute. Additional messages will provide more
name detail.
Name of the enum being looked for.
Message Variables
System action attribute
Name of attribute where error occurred.
information.
System action
Operator response The topology server continues with missing
information.
Do the following:
1. Correct or replace the appropriate file. Operator response
2. Restart the server. Do the following:
restart the server. Erasing the databases will cause 2. Restart the server.
you to lose any customization you might have done. 3. If the server restarts with no errors and information
For that reason, create a backup prior to erasing is still missing, erase the server databases and
the databases so that you can restore them if the restart the server. Erasing the databases will cause
problem persists. you to lose any customization you might have done.
IHS2194W Error - enum symbol symbol not
found.

problem persists.
Do the following:
IHS2196W Error - unsupported type type in
table table, row row, col column.
Explanation 3. If the server restarts with no errors and information
A table entry contains a type not supported by the restart the server. Erasing the databases will cause
current code. you to lose any customization you might have done.
Message Variables For that reason, create a backup prior to erasing
type problem persists.
Type of data provided.
IHS2198I Parsing file file.
table
Name of table with error.
Explanation
row
Table row with error. The specified file is being parsed.
column Message Variables
Column number in table with error.
file
Name of file currently being parsed.
System action
The topology server continues with missing System action
information.
The topology server parses file.
Operator response IHS2202W Unable to place BDF file in the BDF
hierarchy. File name: filename
Do the following:
Description: file description
2. Restart the server. Explanation
3. If the server restarts with no errors and information topology typically uses the following four types of BDF
is still missing, erase the server databases and files:
you to lose any customization you might have done. • Business system
For that reason, create a backup prior to erasing • Business subsystem
the databases so that you can restore them if the • Business system component
problem persists.
• Mapping
IHS2197W Error - table missing class name.
When the topology server starts, it reads all of the BDF
Table ID = table.
and CDF files from the %BINDIR%\TDS\Server\db
\current\appdefs subdirectory on non-UNIX platforms
Explanation or the $BINDIR/TDS/Server/db/current/appdefs
A table was found that did not have a class name subdirectory on UNIX platforms. BINDIR is an
specified. environment variable by the installation code to
indicate the root location of the topology server code.
Message Variables It then places the BDF files into an internal BDF
table hierarchy according to the following rules:
ID of table with missing class name. 1. Place all of the business system BDFs on the top
row of the hierarchy as peers.
System action 2. Repeatedly iterate through all of the BDFs that have
The topology server continues with missing not been placed in the hierarchy until you make a
information. complete pass through all BDFs without placing
any.
3. Examine each of the remaining BDFs. If its parent is – The BDF that should be this BDF's parent is
already placed in the BDF hierarchy, then place the missing or was not placed in the BDF hierarchy
unplaced BDF in the hierarchy as a child of that because of some other error.
parent BDF.
IHS2206E Remap of a customized view
When this process is complete, all BDF files must be failed: rc=return code,
placed in the hierarchy. This message is written to the layout_rc=layout return code.
message log for each BDF file that is not placed in the
hierarchy. Explanation
Message Variables During the creation of a customized view, the server
filename positions the resources and creates view information
The file name of the BDF file the was not placed. for use by the console. The function that handles the
positioning of resources in the view has failed. This
file description
error might be caused by the database file containing
The description of the BDF file that was extracted
the customized view information being corrupt or
from the BDF file.
missing.
The specified BDF file is not used by the server. Events return code
defined by this BDF file might not be recognized. Global return code from the function.
layout return code
Operator response Internal return code from layout
Contact your system programmer or the person
responsible for the BDF files. System action
In order to position the resources, the server invokes
System programmer response another function. The result is that the customized
view information will not be displayed.
Correct the BDF file or contact someone who can. The
most common causes of this problem are:
Operator response
• For a Business Subsystem BDF
Undo the customization for the view. Make view
– The parent ID is incorrect in the subsystem BDF. changes and save it again.
– The component ID is incorrect in the business
system BDF that should be this BDF's parent. System programmer response
– The business system BDF that should be this Examine the error log for additional information.
BDF's parent is missing or was not placed in the
BDF hierarchy because of some other error. IHS2207E An error occurred during the Save
View request.
• For a Business System Component BDF:
– The component ID of the business system Explanation
component BDF is incorrect.
An error occurred when the topology console
– The subcomponent group of the business system
requested to save a view on the server. This is caused
BDF or business subsystem BDF that should be
by an internal error in the server, such as the view not
this BDF's parent is incorrect.
being found in the server database.
– The business system BDF or business subsystem
BDF that should be this BDF's parent is missing or System action
was not placed in the BDF hierarchy because of
some other error. The topology server ignores the request to save the
view.
• For a Mapping BDF:
– The parent ID group of the mapping BDF is Operator response
incorrect.
Contact the server administrator.
– The component ID of the BDF that should be this
BDF's parent is incorrect.

Examine the log file for additional information. The topology server detected an entry identifier in the
Query Task response that is not valid. Valid identifiers
IHS2208E An installation error was detected for Query Task response entries are: 1, 2, 3, 4, 5, 7,
(rc). The server will terminate. and 8.
Please contact IBM Software
Support. Message Variables
entry-identifier
Explanation The identifier of the Query Task response entry.
The server detected a corrupted file during
initialization. System action
Message Variables The topology server ignores any remaining Query Task
response entries. The monitor associated with the
rc failing Query Task is not updated.
The server internal return code.
Operator response
System action
Contact the provider of the Query Task
The server ends. instrumentation.
Operator response IHS2213E Query Task response entry with

identifier entry-identifier has
Contact your system programmer. number-received data tokens.
Expected number-expected data
System programmer response tokens.
Reinstall the server.
Explanation
IHS2211E Enclosing parenthesis for Query
Task response entry are not The topology server detected an entry in the Query
matched or ordered correctly. Task response that specified an incorrect number of
data tokens.
Each entry in the Query Task response must begin with entry-identifier
an open parenthesis and end with a closed The identifier of the Query Task response entry.
parenthesis. The topology server detected that the number-received
Query Task response contained an entry that did not The actual number of data tokens in the Query
begin with an open parenthesis or did not end with a Task response entry.
closed parenthesis. This message is also issued when
number-expected
two open parentheses are found without an
The correct number of data tokens for the Query
intervening closed parenthesis.
Task response entry.
System action
System action
The topology server ignores any remaining Query Task
failing Query Task is not updated.
failing Query Task is not updated.
Operator response
Operator response
instrumentation.
instrumentation.
IHS2212E Entry identifier entry-identifier for
IHS2214E No entry with identifier entry-
a Query Task response entry is
identifier found in Query Task
missing or not a valid identifier.
response.
The topology server detected a missing entry in the The monitor associated with the failing Query Task is
Query Task response. not updated.
Message Variables
Operator response
entry-identifier
The identifier of the entry which is required but not Contact the provider of the Query Task
present in the Query Task response entry. instrumentation.
IHS2217I Query Task response contains
System action valid syntax. Proceeding with
monitor value updates.
failing Query Task is not updated. Explanation
The topology server successfully parsed the syntax of
Operator response the Query Task response returned from the
instrumentation.
instrumentation.
System action
IHS2215E Found number-received entries
with identifier entry-identifier in The topology server proceeds with monitor updates
Query Task response. Only one based on the information in the Query Task response.
such entry permitted. IHS2218E No entry with identifier entry-
identifier-1 or entry-identifier-2
Explanation found in Query Task response. At
The topology server detected multiple entries having least one expected.
an entry identifier of entry-identifier. The Query Task
response can have only one entry with that entry Explanation
identifier. The Query Task response must have at least one entry
Message Variables with either of the specified entry identifiers.
number-received Message Variables

The actual number of entries with the specified entry-identifier-1
entry identifier found in the Query Task response. Identifier of a Query Task response entry.
entry-identifier entry-identifier-2
The identifier of the Query Task response entry. Identifier of a Query Task response entry.

The topology server ignores any remaining Query Task The topology server ignores any remaining Query Task
response entries. The monitor associated with the response entries. The monitor associated with the
failing Query Task is not updated. failing Query Task is not updated.

Contact the provider of the Query Task Contact the provider of the Query Task
instrumentation. instrumentation.
IHS2216E Query Task response contains IHS2219E Each Query Task response entry
incorrect syntax. No monitor value must start with open parenthesis.
updates will be performed.
Explanation
Explanation
The topology server detected that the Query Task
The topology server detected one or more errors in the response contained an entry that did not begin with an
syntax of the Query Task response returned from the open parenthesis.
instrumentation.

System action All four of these identifiers are the same in
descriptionFile1 and descriptionFile2, so
descriptionFile2 is not used.
failing Query Task is not updated. Message Variables
descriptionFile1
Operator response The description file that was already parsed by the
Contact the provider of the Query Task server and contained the same four key identifiers
instrumentation. as descriptionFile2.
descriptionFile2
IHS2220I Setting value of monitor resource
The description file that has the same four key
monitor-name to monitor-value.
identifiers as descriptionFile1.
Explanation
System action
The topology server is updating the value for a monitor
The server logs this message and continues running.
resource.
monitor-name Contact your system programmer.
The name of the monitor being updated.
monitor-value System programmer response
The new value for the monitor.
Remove or modify one or both of the files in order to
IHS2221E Performing periodic polling of resolve the conflict. If you are unable to fix the
selected monitors on resource problem, contact the suppliers of the description files.
resource-name.
IHS2223E Aggregation task
aggregation_task_name for exit
Explanation
exit_name failed with return code
The polling interval for the specified resource has return_code_value.
expired. The topology server will begin querying
selected monitors on that resource and updating views Explanation
with the current monitor values.
IHSXSRV.EXE encountered an error while invoking the
Message Variables designated aggregation query task.
resource-name Message Variables
The name of the resource whose monitors will be
queried. task_name
The name of the invoked aggregation task, prior to
IHS2222E The file descriptionFile2 has the variable substitution.
same manufacturer, product, exit_name
version and abstraction level as The name of the exit that is handling the task
descriptionFile1 which was parsed invocation.
earlier. This is not allowed.
return_code_value
Error code returned from the exit.
Explanation
Description files must be uniquely identified by the System action
combination of their following four key identifiers:
The component for which this task was defined is
Identifier Source group added to the last successfully queried aggregate, and
marked for retry. The next time a heartbeat is received
manufacturer component ID group
for this component, the aggregation tasks are retried
product component ID group (unless this component is manually moved to another
aggregate).
version component ID group
abstraction level component type group
Verify that the specified aggregation task is correctly This instance of the component was not included as a
defined and installed. If the problem persists, contact member of the specified business system. This is
your system programmer. usually a normal condition and indicates that
membership criteria specifications supplied in the
System programmer response business system mapping were not met by this
component instance. It can also mean that the criteria
If the specified aggregation task is correctly defined are not valid or the component information tasks
and installed, contact IBM Software Support. cannot be run.
IHS2229E Component information task Message Variables
task_name for exit exit_name
failed with return code component_name
return_code_value. The name of the affected component.
business_system_name
Explanation The name of the business system from which the
component instance is being excluded.
The topology server encountered an error while
origin, suborigin, and subsource
invoking the specified component information task.
These fields help identify the particular component
Message Variables instance that is being excluded.
task_name
The name of the invoked component information System action
task, prior to variable substitution. The specified instance of the component is not
exit_name included in any views related to the business system.
The name of the exit that is handling the task
invocation. Operator response
return_code_value If the component instance is a member of the
Error code returned from the exit. business system, check the message log for additional
messages indicating a problem. The membership
System action criteria specified in the instrumentation might not have
The instance of the component for which this task was been valid or the component information tasks might
defined is not included as a member of the business not have run successfully. Check the helps for any
system to which it is being mapped. This task is messages for more information.
marked for retry and will be attempted again on the If no other messages were logged, then the output
next heartbeat. from the component information tasks does not meet
the membership criteria, and one or both must be
Operator response modified in order for the component instance to be
included.
Verify that the specified component information task is
correctly defined and installed. If the problem IHS2231E Component component_name in
persists, contact your system programmer. business system
business_system_name had errors
System programmer response in the membership criteria
specification.
If the specified component information task is
correctly defined and installed, contact IBM Software
Explanation
Support.
A component information change event was received,
IHS2230I Component component_name is but there was no resource in the resource database, or
not a member of business system there was no previous component information
business_system_name. Origin: available for the specified task.
origin Suborigin: suborigin
Subsource: subsource Message Variables
component_name
The name of the affected component.

business_system_name Operator response
The name of the business system to which the
If this component information task is being used for
component is being mapped.
specifying aggregation information, but not
membership information, ignore this message. In
System action other cases, check the error log for additional
The specified instance of the component is not messages that might indicate that the task did not run
included in any views related to the business system. successfully.
IHS2234E Component information
Operator response substitution value
substitution_value could not be
Check the message log for additional messages
resolved.
indicating a problem with instance membership
criteria specification.
Explanation
IHS2232E Component information change
event did not have a matching The topology server was unable to substitute any
resource or any matching resource instance data for the specified substitution
component information. Business value. The value is probably not one of the support
system: business_system_name values.
Origin: origin Suborigin: suborigin Message Variables
Subsource: subsource Task Name:
component_information_task_nam substitution_value
e Task Value: The name of the substitution value that was not
component_information_task_valu resolved.
e Change: type_of_change
System action
Explanation The instance of the component for which this
The mapping of the business system to the component substitution value was defined is not included in the
had errors in the specification of the membership business system to which it is being mapped. This
criteria in the management tool extensions. message will continue to be logged each time
membership evaluation is attempted for this resource.
Message Variables
business_system_name Operator response
The name of the business system to which the
Make sure that the substitution value is one of the
component is being mapped.
values supported. If it is supported, notify your system
origin, suborigin, and subsource programmer.
These fields help identify the particular component
instance that is being excluded. System programmer response
component_information_task_name
The name of the component information task for
which the output values are changing. IHS2235I Do you want to delete Customized
component_information_task_value Dynamic View view_name?
The actual value being added or removed from the
output of the component information task. Explanation
type_of_change This message is a confirmation message to insure you
1 = value has been added; 2 = value has been want to delete the customization of the dynamic view
removed. you have selected.
Message Variables
System action
view_name
The change event is ignored and the instance
The name of the customized dynamic view you
membership is unaffected.
have selected for deletion.
System action line_number
The line number of the failed entry in the specified
If you respond YES, the view will be deleted, if you
configuration file.
respond NO, no action is taken.
configuration_file_name
Operator response The name of the configuration file the server tried
to open. This contains a directory specification
Confirm either YES or NO for deleting or not deleting appended with the file name ihstec.cfg.
the customized dynamic view.
System action
No events will be sent to the specified Tivoli Enterprise
None Console server from this topology server.
IHS2250E Unable to open configuration file
configuration_file_name. Operator response
Verify that the specified Tivoli Enterprise Console
Explanation server exists and is listening on the specified port (if
the portmapper is not in use on the Tivoli Enterprise
The topology server encountered an error while trying
Console server computer). Check the syntax of the
to open the specified configuration file.
configuration file entry using the instructions in the
Message Variables comments contained in the file.
configuration_file_name
The name of the configuration file the server tried System programmer response
to open. This contains a directory specification If the Tivoli Enterprise Console server specification is
appended with the file name ihstec.cfg. correct and specifies a valid active Tivoli Enterprise
Console server, contact IBM Software Support.
System action
IHS2252E Error sending
No events will be sent to the Tivoli Enterprise Console APM_NOTIFICATION event to
from this topology server. server server_name,port
port_number. Resource:
Operator response resource_label Old status:
old_status New status: new_status
Verify that the configuration file exists exactly as
shown in the message and can be accessed by the
computer on which the topology server is running. Explanation
The specified event was created but cannot be
System programmer response successfully sent to the specified Tivoli Enterprise
Console server. The server was located and
If the configuration file exists in the expected location, communications was established, but the topology
contact IBM Software Support. server was unsuccessful in opening a port and sending
IHS2251E Error in server specification or the event data to the Tivoli Enterprise Console server.
connecting to server specified on Message Variables
line line_number of configuration
file. server_name
The name of the Tivoli Enterprise Console server
as read from the configuration file.
Explanation
port_number
The topology server encountered an error while trying The port number determined to be used by the
to parse the specified line in the specified Tivoli Enterprise Console server either as specified
configuration file. Another possible cause is that the in the configuration file is determined from the
line was successfully parsed, but communications portmapper.
cannot be established with the server specified on the
line. resource_label
The label used to identify the resource whose
Message Variables status changed.
old_status
The previous status of the resource.

new_status Explanation
The updated status of the resource.
An error was encountered while compiling an
extended regular expression used for instance
System action membership filtering. This indicates that the specified
No event was sent to the specified Tivoli Enterprise ExtRegExp is not a valid extended regular expression.
Console server, but the topology server will attempt to The source of the ExtRegExp in error is an entry in the
send the event to any other Tivoli Enterprise Console management tool extensions group with a variable
servers specified in the configuration file. name of InstanceMembershipCondition or
InstanceMembershipTest in Filename.
Consult with your system programmer to determine if ErrType
the specified server/port combination represents a The type of error that was encountered. Possible
valid active Tivoli Enterprise Console server. values are:
• Invalid regular expression
• Invalid collating element
If the Tivoli Enterprise Console server specification is • Invalid character class
correct and specifies a valid active Tivoli Enterprise
Console server, contact IBM Software Support. • Last character is \
• Invalid number in \digit
IHS2260I The server is terminating due to an
internal error, RC=retcode. • [] imbalance
•  or () imbalance
Explanation • \{ \} or { } imbalance
An unrecoverable error occurred in the topology • Invalid \{ \} range expression
server. • Invalid range expression endpoint
Message Variables • Out of memory
retcode • ?*+ not preceded by valid regular expression
The return code from the function in error. • Invalid multibyte character
• Unknown
System action
ExtRegExp
The topology server ends. Databases might not be
The extended regular expression that is causing
saved.
the error.
Filename
Operator response
The name of the file containing the management
Contact your system programmer responsible for the tool extensions group that contains the ExtRegExp
topology server. entry that is in error.

Try to restart the server. If the problem persists, check The InstanceMembershipCondition and
the message and error logs for information. If you are InstanceMembershipTest entries in the management
unable to fix the problem, contact IBM Software tool extensions group of the specified file are not used
Support. for instance membership filtering.
IHS2262E An error was encountered during
the compilation of an extended Operator response
regular expression used for Correct the extended regular expression that is in error
instance membership filtering. and restart the topology server.
Type of error: ErrType Extended
regular expression: ExtRegExp IHS2263E An error was encountered during
Filename: Filename the evaluation of an extended
regular expression used for
instance membership filtering.
Type of error: ErrType Extended Operator response
regular expression: ExtRegExp
Correct the extended regular expression that is in error
Filename: Filename String
and restart the topology server.
evaluated: StringEvaluated
IHS2264E An invalid sequence number was
Explanation found in an
InstanceMembershipCondition
An error was encountered while evaluating the entry in the management tool
specified string using the extended regular expression extension group. Filename:
ExtRegExp for the purpose of instance membership Filename Sequence number:
filtering. This indicates that the extended regular SeqNumber
expression is not valid. The source of the erroneous
expression is an entry in the management tool
Explanation
extensions group with a variable name of
InstanceMembershipCondition or Sequence numbers are used to determine the order in
InstanceMembershipTest in Filename. which InstanceMembershipCondition entries must be
evaluated. These sequence numbers must have the
Message Variables
following characteristics:
ErrType
• They must range in value from 1 to the number of
The type of error that was encountered. Possible
InstanceMembershipCondition entries in the
values are:
management tool extensions group of the specified
• Invalid regular expression file.
• Invalid collating element • They must be distinct within the management tool
• Invalid character class extensions group of a given file. Duplicates are not
allowed.
• Last character is \
• They do not have to be in any particular order, but, if
• Invalid number in \digit sorted, they must be contiguous. No holes in the
• [] imbalance sequence are allowed.
•  or () imbalance The sequence number of the entry in error violates one
• \{ \} or { } imbalance of these required characteristics.
• Invalid \{ \} range expression Message Variables
• Invalid range expression endpoint Filename
• Out of memory The filename of the file containing the
management tool extensions group with the
• ?*+ not preceded by valid regular expression
InstanceMembershipCondition entry whose
• Invalid multibyte character sequence number is in error.
• Unknown SeqNumber
ExtRegExp The sequence number that is in error.
The extended regular expression that is causing
the error. System action
Filename The InstanceMembershipCondition and
The name of the file containing the management InstanceMembershipTest entries in the management
tool extensions group that contains the ExtRegExp tool extensions group of the specified file are not used
entry that is in error. for instance membership filtering.
StringEvaluated
The string that was being evaluated when the error Operator response
occurred.
Correct the sequence number or numbers that are in
error and restart the topology server.
System action
IHS2265E More than one
Some or all of the resources of the type described by
InstanceMembershipTest entry
Filename might not be included in the appropriate
was found in the management tool
views.
extensions group. Filename:
Filename

Explanation IHS2267I Message from sender
sender_name: the_message
More than one InstanceMembershipTest entry was
encountered in the management tool extensions group
in the specified file. Only one Explanation
InstanceMembershipTest entry is allowed per A message has been sent to you from the topology
management tool extensions group. server or another topology console.
Filename sender_name
The name of the file whose management tool The topology console that sent the message, or
extensions group contains more than one 'topology server' if this was sent by the topology
InstanceMembershipTest entry. server that the topology console is signed on.
the_message
System action The message that was sent.
The InstanceMembershipCondition and
IHS2268I Keyword keyword name Value
InstanceMembershipTest entries in the management
keyword value seconds
tool extensions group of the specified file are not used
for instance membership filtering.
Explanation
Operator response This message displays a keyword and its value in
seconds read from the server.properties file. For more
Remove all but one of the InstanceMembershipTest
information, see the server.properties file.
entries from the management tool extensions group of
the specified file and restart the topology server. Message Variables
IHS2266E A syntax error was encountered in keyword name
an InstanceMembershipCondition The name of the keyword read from the
entry in the management tool server.properties file.
extensions group. Filename: keyword value
Filename The value in seconds of the keyword read from the
server.properties file.
Explanation
The syntax is not valid in one or more keyword value intervals
InstanceMembershipCondition entries in the
management tool extensions group of the specified Explanation
file.
This message displays a keyword and its value in
Message Variables intervals read from the server.properties file. For more
Filename information, see the server.properties file.
The filename of the file containing the Message Variables
management tool extensions group that has one or
more InstanceMembershipCondition erroneous keyword name
entries. The name of the keyword read from the
System action keyword value
The value in intervals of the keyword read from the
The InstanceMembershipCondition and server.properties file.
InstanceMembershipTest entries in the management
tool extensions group of the specified file are not used IHS2270I Keyword keyword name Value
for instance membership filtering. keyword value percent

Correct the syntax of the InstanceMembershipTest This message displays a keyword and its value in
entries in the management tool extensions group of percent read from the server.properties file. For more
the specified file and restart the topology server. information, see the server.properties file.
Message Variables IHS2274I Message from sender to receiver
not sent. receiver is either not
keyword name
signed on or is the message
The name of the keyword read from the
originator. Message was the
message.
keyword value
The value in percent of the keyword read from the
Explanation
The message cannot be delivered because the receiver
IHS2271I Keyword keyword name Value is either not signed or is the originator of the message.
keyword value
Message Variables
Explanation sender
This message displays a keyword and its value read The name of the topology console or topology
from the server.properties file. For more information, server sending the message.
see the server.properties file. receiver
The name of the console receiving the message
Message Variables
the message
keyword name The message text that was trying to be sent.
server.properties file. IHS2275I Message from sender to all
keyword value consoles not sent. No applicable
The value of the keyword read from the consoles signed on. Message was
server.properties file. the message
IHS2272I Message sent from sender to all Explanation

consoles. Message is the message
This message indicates that a broadcast message
cannot be delivered because no receiving consoles
Explanation
were signed on.
This message confirms that a broadcast message has
Message Variables
been sent to all consoles logged on to the server.
sender
Message Variables
The name of the topology console or topology
sender server sending the message.
The name of the topology console or topology the message
server sending the message. The message text that was trying to be sent.
the message
The message text that was sent.
keyword value milliseconds
IHS2273I Message sent from sender to
receiver. Message is the message Explanation
This message displays a keyword and its value in
Explanation
milliseconds read from the server.properties file. For
This message confirms that a broadcast message has more information, see the server.properties file.
been sent to a specific console.
Message Variables
Message Variables
keyword name
sender The name of the keyword read from the
The name of the topology console or topology server.properties file.
server sending the message. keyword value
receiver The value in milliseconds of the keyword read from
The name of the console receiving the message the server.properties file.
the message IHS2277I Keyword keyword name Value
The message text that was sent. keyword value ticks

Explanation The specified Tivoli Framework command was run by
the server, but did not produce a valid value.
This message displays a keyword and its value in ticks
read from the server.properties file. For more Message Variables
information, see the server.properties file.
command
Message Variables The command the server executed to determine
the value for an operating system resource. The
keyword name
operating system name is included in the
command string.
keyword value System action
The value in ticks of the keyword read from the
server.properties file. The operating system resource is placed under a
default platform aggregate.
keyword value
Operator response
statusUpdateIntervals
Run the specified Tivoli Framework command outside
Explanation the context of the server and try to determine the
reason for the failure. If you cannot resolve the
This message displays a keyword and its value in problem, contact your system programmer.
statusUpdateIntervals read from the server.properties
file. For more information, see the server.properties
file.
Run the specified Tivoli Framework command outside
Message Variables
the context of the server and try to determine the
keyword name reason for the failure. If you cannot resolve the
The name of the keyword read from the problem, contact IBM Software Support.
IHS2306W A blank host name was
keyword value encountered. No system resource
The value in statusUpdateIntervals of the keyword is created. Origin: origin Suborigin:
read from the server.properties file. suborigin
keyword value Explanation
viewChangeIntervals
The server was trying to create a system resource from
a heartbeat or system monitor event, but the host
Explanation name passed in the event was blank. A system
This message displays a keyword and its value in resource cannot be created from this event.
viewChangeIntervals read from the server.properties Message Variables
file.
origin and suborigin
Message Variables These fields help identify the event for which the
keyword name server was trying to create a system resource.
server.properties file. System action
keyword value A system resource is not created for the heartbeat or
The value in viewChangeIntervals of the keyword system monitor event. For heartbeat events, the
read from the server.properties file. corresponding business resource will not reflect any
status information for the operating system on which it
IHS2305I Unable to determine operating
is running.
system platform using command:
command
Operator response
Explanation No response is necessary if system information is not
required for the resources in question.
The server attempted to determine the platform of an
operating system resource, but was not successful.
If you want system information to be shown, then a persists, contact IBM Software
host name must be provided with the events: Support.
• For a system monitor event, the event can be resent
after a host name is provided. Explanation
• For a heartbeat event, you must delete the affected The topology server or ihsaunpk command line utility
business resource, then resend the heartbeat attempted to open an AMP file, but the open failed
containing the host name. because of an incorrect parameter. This is probably
caused by an AMP file that is not valid.
IHS2307W While writing to the databases, a
string was truncated to the Message Variables
maximum length of maximum AMPFilename
length. This may cause unexpected The filename of the AMP for which the open failed.
results if you continue to use the
databases. Truncated string:
System action
string
The action being attempted on the AMP file was not
Explanation completed successfully.
Strings associated with database resources, such as

Operator response
the display name, are limited to the specified number
of characters when written to disk. The string Ensure that the AMP file is valid and retry the
committed to the database was longer than the operation. One test of validity is to run the ihsaunpk
specified number of characters and was truncated. utility with the -v parameter in order to list its
contents.
Message Variables
maximum length IHS2401E An attempt was made to open an
The maximum number of characters for the string. AMP file whose format is not valid.
Filename: AMPFilename Replace
string the AMP file and, if the problem
The specified database resource string that was persists, contact the provider of
truncated. the AMP.

The topology server continues to operate normally, The topology server or ihsaunpk command line utility
unless you were shutting down when the databases attempted to open an AMP file whose format is not
were being written. If you continue to use the valid.
databases without removing the corrupted resource,
unexpected results can occur. Your results will depend Message Variables
on which string is truncated and how that string gets AMPFilename
used by the topology server. The filename of the AMP file whose format is not
valid.
Operator response
Do the following: System action
1. Locate the resource that contains the truncated The action being attempted on the AMP file was not
string. completed successfully.
2. Remove the resource.
Operator response
3. Shorten the string for the database resource.
4. Resend the heartbeat for the resource or wait for Ensure that the AMP file is valid, replacing it if
the next heartbeat cycle. necessary, and retry the operation. One test of validity
is to run the ihsaunpk utility with the -v parameter in
IHS2400E An invalid parameter was passed order to list its contents.
to the AMP open routine. AMP
IHS2402E An internal error occurred while
Filename: AMPFilename Replace
processing an AMP file. AMP
the AMP file, and if the problem
Filename: AMPFilename

The topology server or ihsaunpk command line utility The topology server or ihsaunpk utility read a line from
encountered an internal error while processing an AMP the AMP unpacking configuration file whose syntax
file. was not valid.
AMPFilename AMPUnpackingConfigFilename
The filename of the AMP file that was being The filename of the AMP file unpacking
processed when the internal error was configuration file in which the syntax error was
encountered. encountered.
lineNumber
System action The line number of the line in
AMPUnpackingConfigFilename on which the syntax
error was encountered.
completed successfully.
System action
Operator response
The line with the syntax error and any lines that follow
Ensure that the AMP file is valid, replacing it if
it in the AMP unpacking configuration file are not
necessary, and retry the operation. One test of validity
processed. The AMP files being processed might have
order to list its contents. been processed successfully, but not according to the
rules specified in the AMP file unpacking configuration
IHS2403E A CRC error was detected while file.
opening an AMP file. AMP
Filename: AMPFilename Operator response
Correct the syntax error in the AMP unpacking
Explanation
configuration file and retry the operation.
The topology server or ihsaunpk command line utility
IHS2405E An error occurred opening the
detected a CRC error indicating that the AMP file being
processed is not valid. AMP unpacking configuration file.
Filename:
Message Variables AMPUnpackingConfigFilename
AMPFilename
The filename of the AMP file that was being Explanation
processed when the CRC error was encountered. The topology server or ihsaunpk utility cannot open
the AMP unpacking configuration file.
System action
Message Variables
AMPUnpackingConfigFilename
completed successfully.
The filename of the AMP file unpacking
configuration file which cannot be opened.
Operator response
Ensure that the AMP file is valid, replacing it if System action
necessary, and retry the operation. One test of validity
The action requested on the AMP file is performed
using the default AMP file unpacking rules.
order to list its contents.
IHS2404E A syntax error was encountered in Operator response
the AMP unpacking configuration
file. Filename: Check the file permissions on the AMP file unpacking
AMPUnpackingConfigFilename Line configuration file and change them if necessary.
number: lineNumber Ensure that the file is not locked by some other
application.
IHS2406E An error occurred opening an AMP
file. AMP Filename: AMPFilename
Explanation AMPFilename
The filename of the AMP file in which the global
The topology server or ihsaunpk utility was unable to
information cannot be accessed.
open the specified AMP file.
AMPFilename The action requested on the AMP file is not performed.
The filename of the AMP file that cannot be
opened.
Operator response
System action Ensure that the specified file is a valid AMP file and
retry the operation. The most likely cause of this error
The action requested on the specified AMP file was not is a corrupted AMP file or attempting an AMP file
performed. operation on a file that is not an AMP file.
IHS2409E An error occurred getting the
Operator response
information for an entry in an AMP
Check the file permissions on the AMP file unpacking file. AMP Filename: AMPFilename
configuration file and change them if necessary.
Ensure that the file is not locked by some other Explanation
application. Ensure that the AMP file is valid, replacing
it if necessary, and retry the operation. One test of The topology server or ihsaunpk utility was unable to
validity is to run the ihsaunpk utility with the -v access the information for an AMP file entry in the
parameter in order to list its contents. specified AMP file.
IHS2407E An error occurred while closing an Message Variables

AMP file. AMP Filename: AMPFilename
AMPFilename Replace the AMP file The filename of the AMP file in which the
and if the problem persists contact information for an AMP file entry cannot be
Tivoli Service. accessed.

The topology server or ihsaunpk utility was unable to The requested action is not successfully performed on
close the specified AMP file after processing it. the specified AMP file.
AMPFilename
The filename of the AMP file that cannot be closed. Operator response
Ensure that the specified file is a valid AMP file and
System action retry the operation. The most likely cause of this error
The action requested on the specified AMP file might is a corrupted AMP file or attempting an AMP file
or might not have been performed successfully. operation on a file that is not an AMP file.
IHS2410E An error occurred seeking to an
Operator response entry in an AMP file. AMP
Make sure that the file has not been locked by some Filename: AMPFilename Previous
other application. Terminate the program that entry name: PreviousEntryName
generated this message and retry the operation.
Explanation
IHS2408E An error occurred getting the
global information from an AMP The topology server or ihsaunpk utility was unable to
file. AMP Filename: AMPFilename access the information for an AMP file entry in the
specified AMP file.
The topology server or ihsaunpk utility was unable to AMPFilename
access the global information in the specified AMP file. The filename of the AMP file in which the
information for an AMP file entry cannot be
Message Variables
accessed.

PreviousEntryName AMPFilename
The name of the AMP file entry in the specified The filename of the AMP file in which the entry
AMP file that immediately preceded the AMP file failed to be closed.
entry that cannot be accessed. AMPEntryName
The name of the AMP file entry that failed to be
System action closed.
The requested action is not performed successfully on
the specified AMP file. System action
The requested action might or might not have been
Operator response performed on the specified AMP file.
Ensure that the specified file is a valid AMP file and
retry the operation. The most likely cause of this error Operator response
is a corrupted AMP file or attempting an AMP file Ensure that the specified file is a valid AMP file and
operation on a file that is not an AMP file. retry the operation. The most likely cause of this error
IHS2411E An error occurred while extracting is a corrupted AMP file or attempting an AMP file
an entry from an AMP file. AMP operation on a file that is not an AMP file.
Filename: AMPFilename Entry IHS2413E An error occurred during AMP file
name: AMPEntryName extraction while opening a target
file. Target Filename:
Explanation targetFilename
The topology server or ihsaunpk utility encountered an
error while trying to extract the specified entry from Explanation
the specified AMP file. The topology server or ihsaunpk utility encountered an
Message Variables error opening the specified target file while trying to
extract an entry from an AMP file.
AMPFilename
The filename of the AMP file from which the entry Message Variables
failed to be extracted. targetFilename
AMPEntryName The filename of the target file that cannot be
The name of the AMP file entry that failed to be opened.
extracted.
System action
System action
The specified target file is not written and the
The specified entry is not extracted from the specified corresponding AMP entry is not extracted.
AMP file.
Operator response
Operator response
Ensure that the specified target file is a valid filename
Ensure that the specified file is a valid AMP file and and that the subdirectory actually exists. Also ensure
retry the operation. The most likely cause of this error that the file permission settings on the subdirectory
is a corrupted AMP file or attempting an AMP file and the target file itself will allow the file to be created
operation on a file that is not an AMP file. or overwritten. If the target filename was acquired
from the AMP unpacking configuration file and is not
IHS2412E An error occurred while closing an correct, make corrections to the AMP unpacking
entry in an AMP file. AMP configuration file. Then retry the operation.
Filename: AMPFilename Entry
name: AMPEntryName IHS2414E An error occurred during AMP file
extraction while writing to a target
Explanation file. Target Filename:
targetFilename
error while trying to close the specified entry in the
specified AMP file.
Message Variables
Explanation configuration file. Ensure that the target disk is not full.
Then retry the operation.
error writing to the specified target file while trying to IHS2416I A file was successfully created
extract an entry from an AMP file. from an AMP file entry. AMP
Filename: AMP_filename Entry
Message Variables
name: AMPEntryName File
targetFilename created: FileCreated
The filename of the target file that had the write
error. Explanation
The topology server or ihsaunpk utility successfully
System action
extracted the specified entry from the specified AMP
The specified target file is not successfully written and file and created the specified file.
the corresponding AMP entry is not completely
Message Variables
extracted.
AMP_filename
Operator response The filename of the AMP file from which the entry
was extracted.
and that the subdirectory actually exists. Also ensure AMPEntryName
that the file permission settings on the subdirectory The name of the AMP file entry that was extracted.
and the target file itself will allow the file to be created FileCreated
or overwritten. If the target filename was acquired The filename of the file that was created as a result
from the AMP unpacking configuration file and is not of the extraction.
correct, make corrections to the AMP unpacking
configuration file. Ensure that the target disk is not full. System action
Then retry the operation.
An entry is extracted from the AMP file and a new file
IHS2415E An error occurred during AMP file is created.
extraction while closing a target
file. Target Filename: IHS2417I A file was successfully overwritten
targetFilename by an AMP file entry. AMP
Filename: AMP_filename Entry
name: AMPEntryName File
Explanation
overwritten: FileOverwritten
error closing the specified target file while trying to Explanation
extract an entry from an AMP file.
The topology server or ihsaunpk utility successfully
Message Variables extracted the specified entry from the specified AMP
targetFilename file and overwrote the specified file.
The filename of the target file that had the close Message Variables
error.
AMP_filename
The filename of the AMP file from which the entry
System action
was extracted.
The specified target file might not be successfully AMPEntryName
written and the corresponding AMP entry might not be The name of the AMP file entry that was extracted.
not completely extracted.
FileOverwritten
The filename of the file that was overwritten as a
Operator response result of the extraction.
and that the subdirectory actually exists. Also ensure System action
that the file permission settings on the subdirectory
and the target file itself will allow the file to be created An entry is extracted from the AMP file and an older
or overwritten. If the target filename was acquired file is overwritten.
from the AMP unpacking configuration file and is not
correct, make corrections to the AMP unpacking

IHS2418I AMP entry was not extracted. AMP Operator response
entry is not newer than the target Invoke ihsaunpk using the correct command line
file. AMP Filename: AMP_filename syntax.
Entry name: AMPEntryName
Target Filename: targetFilename IHS2420E No files meeting the file
specification were found. File
Explanation specification: AMPFileSpecification
The topology server or ihsaunpk utility did not extract

Explanation
the specified entry from the specified AMP file
because the AMP file entry has a timestamp that is not The ihsaunpk utility found no files meeting the
newer than the last modification timestamp of the specified AMP file specification that was passed on the
specified target file. command line.
AMP_filename AMPFileSpecification
The filename of the AMP file from which the entry The AMP file specification for which no files were
was not extracted. found.
AMPEntryName
The entry that was not extracted. System action
targetFilename No AMP files are processed and the command line
The target file that was not overwritten. syntax message is displayed.

The specified target file is not modified and the Re-start the utility using one or more valid AMP file
specified entry is not extracted. specifications.
IHS2419I Syntax is: ihsaunpk [-v|-k|-K] [-t IHS2421E Unable to delete fileToDelete
testbedDirName] [-n] amp1spec
[amp2spec ... [ampNspec]] Explanation
The topology server or ihsaunpk utility was unable to
Explanation
delete the specified file.
The ihsaunpk utility was invoked with incorrect
Message Variables
command line syntax.
fileToDelete
Message Variables
The filename of the file that cannot be deleted.
testbedDirName
The name of the testbed subdirectory in which the System action
AMP file is to be unpacked.
The specified file is not deleted.
amp1name
The file specification of one or more AMP files to
be processed. Operator response
amp2name Check the file permissions on the specified files and
Another file specification of one or more AMP files modify them if necessary. Ensure that no other
to be processed. applications have the file locked. Then retry the
operation.
ampNname
Yet another file specification of one or more AMP IHS2422I Deleted fileToDelete.
files to be processed.
Explanation
System action
The topology server or ihsaunpk utility deleted the
This informational message is displayed. specified file.
Message Variables
fileToDelete name has already been installed.
The filename of the file that was deleted. AMP Filename: AMP_filename

The specified file is deleted. A request was made to the topology server to
dynamically load a new AMP file. An AMP file with the
IHS2423W The AMP file being imported specified filename already exists on the topology
contains an entry with the same server. This is not allowed.
name as an existing
instrumentation file. AMP Message Variables
Filename: AMP_filename Existing AMP_filename
Instrumentation Filename: The filename of the new AMP file for which the
existingFilename dynamic load request was made.

A request was made to the topology server to The AMP file is not loaded by the server.
dynamically load a new AMP file. The AMP file contains
an entry with the same filename as an existing
instrumentation that has previously been installed. Operator response
This is not allowed. New in this context means not Verify that the correct AMP filename has been
containing any files that collide with instrumentation specified. If so, notify your system programmer.
files already installed on the topology server.
AMP_filename If the AMP files are actually different sets of
The filename of the new AMP file for which the instrumentation, rename one of them and try again.
dynamic load request was made.
IHS2425I The AMP file import completed.
existingFilename AMP Filename: AMP_filename
The filename of the already installed
instrumentation file to be overwritten if the
Explanation
requested new AMP file had been dynamically
loaded. The topology server successfully loaded the specified
AMP file.
The AMP file is not loaded by the server. AMP_filename
The filename of the AMP file that was successfully
Operator response loaded.
Verify that the correct AMP filename has been
specified. If so, notify your system programmer. System action
The AMP file is successfully loaded by the topology
System programmer response server.
Contact the provider of the AMP file and ask that the IHS2426E The AMP file was not imported
entry in the AMP file be renamed to a name that does because an error occurred during
not collide with any previously installed files. This extraction. AMP Filename:
might or might not require that corresponding changes AMP_filename
be made to other entries in the AMP file that reference
the renamed entry. You might want to use the Explanation
ihsaunpk utility on the topology server to try to
manually install the AMP. You can then examine the A request was made to the topology server to
AMP file unpacking log to determine if there are any dynamically load a new AMP file. An error occurred
additional conflicts. during the extraction of one or more entries. The AMP
file was not loaded.
IHS2424E The AMP file cannot be imported
because an AMP file with this Message Variables

AMP_filename that contain a syntax error or are missing a required
The filename of the new AMP file for which the group.
dynamic load request was made.
Message Variables
System action ampFilename

The filename of the new AMP that was requested
The AMP file is not loaded by the server. to be loaded.
ampEntryFilename
Operator response The filename of the entry within the AMP file that
Verify that the correct AMP filename has been contains the syntax error or is missing a required
specified. group.
Verify that the format of the AMP file is correct by The AMP file is not loaded.
using the tserver ihsaunpk utility on the server with the
-v parameter to list its contents. Operator response
IHS2429I The instrumentation description Verify that the correct AMP filename was specified.
files for the following business
system have been installed on the System programmer response
topology server. Manufacturer:
Manufacturer Product: Product Correct the syntax error or add the missing required
Version: Version group in the specified AMP file entry and try importing
the AMP file again.
Explanation IHS2431E The AMP file cannot be imported
The AMP file for the specified business system was because the internal identifiers of
successfully loaded by the topology server. one of its entries are the same as
an existing file. AMP Filename:
Message Variables ampFilename AMP Entry:
Manufacturer ampEntryFilename Existing
The manufacturer of the business system for Filename: existingFilename
which the AMP was installed.
Explanation
Product
The product name of the business system for A request was made to the topology server to
which the AMP was installed. dynamically load an AMP file. The specified AMP file
Version contains one or more entries which are description
The product version of the business system for files whose internal identifiers are the same as an
which the AMP was installed. existing description file that is already installed on the
topology server. This is not allowed.
The instrumentation description files for the specified ampFilename
business system were loaded by the topology server. The AMP file that the topology server was
requested to load.
because one of its entries contains ampEntryFilename
a syntax error or is missing a The entry in the specified AMP file which is a
required group. AMP Filename: description file whose internal identifiers are the
ampFilename AMP Entry: same as an existing description file that is already
ampEntryFilename installed on the topology server.
existingFilename
Explanation The existing description file that is already
installed on the server with which the specified
A request was made to the topology server to AMP file entry conflicted.
dynamically load a new AMP file. One or more of the
entries in the specified AMP file are description files
System action topology server. Then change any entries in the AMP
file that reference the renamed entry to the new name,
The AMP file is not imported.
and try reloading the AMP file.
Operator response IHS2433W The AMP file contained no entries

to be extracted that were not
Verify that the correct AMP file was specified. If so, already installed on the server.
notify your system programmer. AMP Filename: ampFilename

Modify the contents of the conflicting AMP file entry to A request was made to the topology server to
eliminate the conflict and modify any other entries in dynamically load an AMP file. All of the entries to be
the AMP that reference the entry being modified. The extracted from the specified AMP were already
internal identifiers for a description file are the installed on the topology server and they are identical
following: to the entries in the specified AMP file.
• Manufacturer Message Variables
• Product
ampFilename
• Version The AMP file that the topology server was
• Abstraction level requested to load.

System action
because it would overwrite an
existing file. AMP Filename: The AMP file is not imported.
ampFilename Existing Filename:
existingFilename Operator response
Verify that the correct AMP file was specified.
Explanation
IHS2500E xdfmaint command queue file not
A request was made to the topology server to
dynamically load an AMP file. The specified AMP file found.
contains one or more entries whose filenames are the
same as files already installed on the topology server, Explanation
but whose contents are different than the files that The server attempted to read the xdfmaint command
they overlay if the AMP file were loaded. This is not queue file but was not successful.
allowed.
ampFilename No queued xdfmaint commands are processed.
The AMP file that the topology server was
requested to load. Operator response
existingFilename
Before you execute the run or runforce commands,
The existing file that is already installed on the
queue the xdfmaint commands.
server whose filename is the same as one of the
entries in the specified AMP file.
System action If the xdfmaint commands were queued prior to
executing the run or runforce commands, and you
The AMP file is not imported.
cannot resolve the problem, contact IBM Software
Support.
Operator response
IHS2501I Removing MIF object ID:
Verify that the correct AMP file was specified. mpvTriplet Abstraction Level:
absLevel Filename: xdfFilename
Change the file name of the conflicting AMP file entry Explanation
to a filename that does not already exist on the The server is removing a MIF Object from its database.

Message Variables xdfFilename
The filename of the BDF, CDF, or GDF file that is
mpvTriplet
being removed.
The "Manufacturer;Product;Version" triplet that
uniquely identifies the MIF object that is being
removed. System action
absLevel The file is not removed from the server database.
The abstraction level of the MIF object that is
being removed. Operator response
xdfFilename Ensure the file is the correct one to be removed.
The filename of the BDF, CDF, or GDF file that
contains the MIF object that is being removed.
System action Ensure the file is the correct one to be removed. If you
cannot resolve the problem, contact IBM Software
The MIF object is removed from the server database. Support.
IHS2502E Error deleting BDF file Filename: IHS2504E Error deleting CDF file Filename:
bdfFilename ID: mpvTriplet Level: cdfFilename
absLevel
Explanation
Explanation
The server attempted to delete a CDF file from its
The server attempted to delete a BDF file from its database but was not successful.
database but was not successful.
Message Variables
Message Variables
cdfFilename
bdfFilename The filename of the CDF file that is being removed.
The filename of the BDF file that is being removed.
mpvTriplet System action
uniquely identifies the component that is being The CDF file is not removed from the server database.
removed.
absLevel Operator response
The abstraction level of the component that is Ensure the CDF file is the correct one to be removed.
being removed.
System action
Ensure the CDF file is the correct one to be removed. If
The BDF file is not removed from the server database. you cannot resolve the problem, contact IBM Software
Support.
Operator response
IHS2505E An error occurred while deleting a
Ensure the BDF file is the correct one to be removed. resource type database entry ID:
mpvTriplet Abstraction Level:
System programmer response absLevel Filename: xdfFilename
Ensure the BDF file is the correct one to be removed. If

Explanation
you cannot resolve the problem, contact IBM Software
Support. The server attempted to delete a resource type from
its database but was not successful.
IHS2503E Error deleting file Filename:
xdfFilename Message Variables
mpvTriplet
Explanation The "Manufacturer;Product;Version" triplet that
The server attempted to delete an BDF, CDF, or GDF uniquely identifies the resource type that is being
file from its database but was not successful. removed.
Message Variables
absLevel System programmer response
The abstraction level of the resource type that is
Ensure the CDF is the correct one to be removed. If
being removed.
you cannot resolve the problem, contact IBM Software
xdfFilename Support.
The filename of the BDF, CDF, or GDF file that is
being removed. IHS2507I Command added to queue
The resource type is not removed from the server The xdfmaint command has been successfully added
database. to the server xdfmaint command queue file.
Ensure the resource type is the correct one to be The xdfmaint command has been successfully queued.
removed. It will be processed when the run or runforce
command is executed.
System programmer response IHS2508E File not found. Filename: filename
Ensure the resource type is the correct one to be
removed. If you cannot resolve the problem, contact Explanation
IBM Software Support. The server cannot find the required file.
IHS2506E The CDF cannot be removed Message Variables
because it is still referenced by a
GDF. CDF ID: cdfMpvTriplet CDF filename
Filename: cdfFilename GDF ID: The filename that the server was looking for.
gdfMpvTriplet GDF Filename:
gdfFilename System action
Since the required file cannot be found, no action was
Explanation taken by the server.
The server attempted to delete a CDF from its
database but was not successful because the CDF was Operator response
referenced by an existing GDF.
Ensure that the specified file exists.
Message Variables
cdfMpvTriplet System programmer response
The "Manufacturer;Product;Version" triplet that Ensure that the specified file exists. If you cannot
uniquely identifies the CDF that is being removed. resolve the problem, contact IBM Software Support.
cdfFilename
IHS2509E Clients remained logged on.
The filename of the CDF file that is being removed.
Requests not processed.
gdfMpvTriplet
Explanation
uniquely identifies the GDF that references the
CDF. The server attempted to process the queued xdfmaint
gdfFilename commands but was not successful because all of the
The filename of the GDF file that references the clients did not log off within the required time period.
CDF.
System action
System action No action was taken by the server, because some
The CDF is not removed from the server database. clients remained logged on.
Ensure the CDF is the correct one to be removed. Do the following:

1. Ensure all clients log off the server.

2. Run the command again. System programmer response
Processing continues, so no intervention required.
IHS2512E A file being extracted from the
Do the following: AMP already exists with a
1. Ensure all clients log off the server. different M;P;V triplet. AMP
filename: ampFile Existing
2. Run the command again.
filename: existFile
IHS2510E Unable to lock databases.
Requests not processed. Explanation
The server has found a file being extracted from the
Explanation specified AMP already exists, and the existing file has
The server attempted to process the queued xdfmaint a different M;P;V triplet. This cannot be resolved.
commands but was not successful because it cannot Message Variables
lock its databases.
ampFile
System action The filename of the AMP being loaded.
existFile
No action was taken by the server, because the
The filename of the existing file containing a
databases cannot be locked.
deferent M;P;V triplet.
Operator response
System action
Do the following:
Since the M;P;V discrepancy cannot be resolved, the
1. Verify that the server is in a proper state. load AMP/load changed AMP command is stopped.
Operator response
System programmer response Either remove the package that contains the
Do the following: conflicting M;P;V, or the new package cannot be
added. Contact the vendor of the package to report the
1. Verify that the server is in a proper state. error in conflicting file names.
IHS2511E An invalid xdfmaint command was
found and ignored. Command: Either remove the package that contains the
command conflicting M;P;V, or the new package cannot be
added. Contact the vendor of the package to report the
Explanation error in conflicting file names.
The server has found an incorrect command queued in IHS3700I The command command for
the xdfmaint command queue file. resource resource is scheduled.
Message Variables
Explanation
command
The incorrect command found in the xdfmaint The generic command is scheduled for delivery to the
command queue file. appropriate gateway. Response data is expected.
Message Variables
System action command
The incorrect command is ignored and the processing The generic command that is delivered. Examples
of the command queue continues. of the generic command are Current status,
Activate, Inactivate, and Recycle.
Operator response IHS3701I command
Processing continues, so no intervention required.
The network command or resource-specific command The IBM Z NetView Graphic Monitor Facility host
is scheduled for delivery to the appropriate gateway. subsystem (GMFHS) processes the command.
Response data is expected.
command Contact your system programmer if responses are

The command that is delivered. expected or needed.
IHS3702I A status of status for resource System programmer response

resource was returned from the
command command. This message If responses for this domain are wanted, verify that the
displays after an IHS3700I command response bit of the DomainCharacteristics
message. attribute in RODM is not set to zero. If changes are
made and loaded into RODM, issue the GMFHS
Explanation command CONFIG NETWORK from a IBM Z NetView
operator to allow GMFHS access to the configuration
The generic command successfully completed. The changes.
resulting resource status is displayed as part of the
message. See the IBM Z NetView Resource Object Data Manager
and GMFHS Programmer's Guide for additional
Message Variables information.
status IHS3705E The NMG NMG reported that the
The status of the resource after the command is command was not recognized.
completed.
resource Explanation
The resource name.
The Network Management Gateway (NMG) or element
command management system did not recognize the command
The generic command that is issued. as a valid command. The associated command was
IHS3703I response previously displayed with an IHS3700I or an
IHS3701I message.
This is a network command response or resource- NMG
specific command response. The associated command The name of the NMG.
was previously displayed with an IHS3701I message.
response Ensure that the command was entered correctly and

The text of the command response. then retry the command. If the command was entered
correctly and the problem persists, contact your
IHS3704I No response is expected for this system programmer.
domain.
Explanation
Ensure that the command was correctly defined in the
A response is not sent back for this command for Resource Object Data Manager (RODM) for this NMG or
either of the following reasons: element management system. See the IBM Z NetView
• The IBM Z NetView system processing this Resource Object Data Manager and GMFHS
command is not at the correct level to return Programmer's Guide for additional information.
responses to commands. The command is still IHS3706E The gateway gateway reported
executed. that it cannot send the command
• The command response bit of the to the NMG or the element
DomainCharacteristics attribute in RODM is set to management system.
zero. When this bit is set to zero, command
responses are not supported for the domain.

The gateway cannot transport the command to the domain
Network Management Gateway (NMG) or the element The name of the IBM Z NetView Graphic Monitor
management system. The associated command was Facility host subsystem (GMFHS) domain.
previously displayed with an IHS3700I or an
IHS3701I message. Operator response
Message Variables Enter a valid command parameter and retry the
gateway command.
The name of the gateway. IHS3709I The NMG or element management
system reported that the
Operator response command is not allowed.
Explanation
System programmer response The Network Management Gateway (NMG) or element
management system rejected the command as not
Restore the connection to the NMG or the element
being allowed from this operator. The associated
management system.
command was previously displayed with an IHS3700I
IHS3707E The element management system or an IHS3701I message.
reported that the resource
resource is unknown to it. Operator response
Ensure that the command was entered correctly. If the
Explanation
command was entered correctly and you get this
The target resource of the command is not known to message, contact your system programmer.
the element management system.
resource Correct the span and scope authorization tables for

The name of the resource that is unknown to the this NMG or element management system.
element management system. IHS3710E The command is currently not
allowed.
Operator response
The Network Management Gateway (NMG) or the
System programmer response element management system rejected the command
as not being allowed currently (but not permanently
Ensure that the Resource Object Data Manager
disallowed) from this operator. The associated
(RODM) is correctly defined for this resource and that
the element management system is correctly set up to
or an IHS3701I message.
recognize this resource. See the IBM Z NetView
Programmer's Guide for additional information. Operator response
IHS3708E The NMG or element management Retry the command. If the condition persists, contact
system for domain domain your system programmer.
reported that a command
parameter was not valid. System programmer response
Determine the cause of the problem at the NMG or
Explanation element management system and then correct the
The Network Management Gateway (NMG) or element problem.
management system for this domain reports that the IHS3711I The command was cancelled in
command contains an incorrect or unknown the native network.
parameter. The associated command was previously
displayed with an IHS3700I or an IHS3701I message.
The Network Management Gateway (NMG) or element Retry the command. If the condition persists, contact
management system reports that the command has your system programmer.
been cancelled. The associated command was
previously displayed with an IHS3700I or an System programmer response
IHS3701I message.
Determine which task, COS gateway, or GMFHS, timed
out the command and, if defined, verify that the
Operator response
domain attribute CommandTimeoutInterval is properly
Retry the command. If the condition persists, contact defined in the Resource Object Data Manager (RODM).
your system programmer. See the IBM Z NetView Resource Object Data Manager
and GMFHS Programmer's Guide for information about
System programmer response attributes for timeout intervals.
Determine the cause of the cancellation at the NMG or IHS3714E The NMG NMG reported a system
element management system and correct the error.
problem.
Explanation
IHS3712E The native element manager
reported that the command failed The Network Management Gateway (NMG) reports a
due to a permanent failure. system error. The associated command was previously
The Network Management Gateway (NMG) or element NMG
management system reports that the command failed The name of the NMG.
because of a permanent failure. The associated
System action
or an IHS3701I message.
The error is logged in the IBM Z NetView Graphic
Operator response Monitor Facility host subsystem (GMFHS) error log.
Retry the command. If the problem persists, contact

Operator response
Determine the cause of the failure at the NMG or
element management system and correct the Locate the error report in the GMFHS error log and
problem. determine the cause of the error. If you cannot correct
the error, save the error log file and have the
IHS3713E The command timed out. information available when you contact your IBM
Support Center. See the IBM Z NetView Resource
Explanation Object Data Manager and GMFHS Programmer's Guide
The Common Operations Services (COS) gateway or additional information.
the IBM Z NetView Graphic Monitor Facility host IHS3715E The command is not supported.
subsystem (GMFHS) reports that a response was not
received for the command within a timeout interval. If
Explanation
the CommandTimeoutInterval domain attribute was
not defined, then the default timeout interval is 2 The Network Management Gateway (NMG), element
minutes. management system, or the IBM Z NetView Graphic
Monitor Facility host subsystem (GMFHS) reports that
System action the command is not supported.
The command is cancelled by GMFHS and an If the PresentationProtocolName that is defined in the
important message will be logged in the GMFHS error IBM Z NetView Resource Object Data Manager (RODM)
log by the Network Command Manager. for this domain is PASSTHRU, then Activate,
Inactivate, Recycle, and Display status are rejected by

GMFHS. The associated command was previously IHS3718E You are not allowed to enter this
displayed with an IHS3700I or an IHS3701I message. command for resource resource.

Verify that the command was entered correctly. If the You are not authorized to issue this command for this
problem persists, contact your system programmer. resource. The resource is not in your span of control.
The associated command was previously displayed
System programmer response with an IHS3700I or an IHS3701I message.
Ensure that the NMG or element management system Message Variables
is configured correctly and is initialized to support this
command. See the IBM Z NetView Resource Object resource
Data Manager and GMFHS Programmer's Guide for The name of the resource.
Operator response
IHS3716E The command failed, please retry
later. Do the following:
1. Ensure that you entered the command correctly.
Explanation
2. Check your profile to see if this resource is in your
The Network Management Gateway (NMG) or element span of control.
management system reports that the command failed 3. If the problem persists, contact your system
for a temporary reason and that you can resubmit it at programmer.
a later time. The associated command was previously
Operator response Ensure that the operator is authorized to issue this
command for this resource.
Retry the command. If the condition persists, contact
your system programmer. IHS3719I GMFHS is not ready to accept
commands.
Explanation
Determine the reason for the failure at the NMG or
element management system and correct the The IBM Z NetView Graphic Monitor Facility host
problem. subsystem (GMFHS) is not ready to accept commands.
This can be because:
IHS3717E The operator is no longer logged
on to IBM Z NetView or is not • The Resource Object Data Manager (RODM)
authorized to issue this command. application program interface is temporarily
unavailable.
Explanation • The configuration initialization of GMFHS is not
complete.
You are not authorized to issue this command or you
are not logged on to IBM Z NetView. The associated • The Network Management Gateway (NMG) session is
command was previously displayed with an IHS3700I not completely established.
or an IHS3701I message. The associated command was previously displayed
with an IHS3700I or an IHS3701I message.
Operator response
Ensure that you entered the correct command and that Operator response
you are logged on to IBM Z NetView. If the problem Retry the command. If the condition persists, contact
persists, contact your system programmer. your system programmer.

Ensure that the operator is authorized to issue this Verify that RODM, GMFHS, and NMG sessions have
command and that the operator is logged on to IBM Z completed initialization.
NetView.
IHS3720E The resource resource is unknown not real resources and cannot be acted upon with
to GMFHS. network control commands.

The target resource of a command is not defined The command is not executed. An important message
within the Resource Object Data Manager (RODM). will be logged in the IBM Z NetView Graphic Monitor
This error can be caused by the dynamic Facility host subsystem (GMFHS) error log by the
reconfiguration of a domain's resources in RODM or Network Command Manager.
because the resource has been deleted.
resource Do not issue network commands against domain

The name of the resource. objects. Their status must only be monitored as an
indication of the status of the session between GMFHS
and the domains.
Operator response
IHS3724I Parameter substitution is
Retry the command. If the condition persists, contact
incorrect for this resource
resource.

Explanation
Verify that the resource is defined and that it is loaded
A network command or resource-specific command
correctly into RODM. See the IBM Z NetView Resource
included substitution parameters, but the Resource
Object Data Manager and GMFHS Programmer's Guide
Object Data Manager (RODM) was not configured
for additional information.
properly to support the substitution of the service
IHS3722I The command is not supported by point name or application name for this resource. The
the gateway gateway. associated command was previously displayed with a
IHS3700I or a IHS3701I message.
The command is not supported by the required resource
gateway. The associated command was previously The name of the resource.
gateway The command is not delivered to the element
The name of the IBM Z NetView Graphic Monitor management system.
Facility host subsystem (GMFHS) gateway.
Operator response
Operator response Verify that you are using the correct parameter
Ensure that you entered the correct command. If you substitution and then retry the command. If the
entered the correct command and the error persists, substitution failure persists, contact your system
contact your system programmer. programmer.

Ensure that the gateway is defined to support this Ensure that RODM attributes for the resource are
command. defined to support parameter substitution. See the
IBM Z NetView Resource Object Data Manager and
IHS3723I Network commands are not GMFHS Programmer's Guide for additional information.
allowed for domain objects.
IHS3725E The gateway gateway session is
Explanation unavailable. The status of the
command is unknown.
A network command was entered against a view
object which is a domain object. Domain objects are

The command cannot be delivered because of one of A system error occurred in the scope-checker task
the following reasons: DUIFSSCO while processing this command. The
associated command was previously displayed with a
• The gateway session is inactive.
IHS3700I or a IHS3701I message.
• The gateway session across which the command
was sent was lost before the command response System action
was received.
The error is logged in the IBM Z NetView error log.
with a IHS3700I or a IHS3701I message.
Operator response
Message Variables
gateway
The name of the Network Management Gateway System programmer response
(NMG).
Locate the error in the IBM Z NetView log and have the
Operator response information available when you contact your IBM
Support Center.
Retry the command later. If the gateway session is not
restored, contact your system programmer. See IBM Z NetView Troubleshooting Guide for
System programmer response IHS3728I The total length of the command
text exceeds the maximum
Restore the gateway session.
allowed by GMFHS.
IHS3726E A system error occurred in
GMFHS. Explanation
The command text that was entered is greater than
Explanation the maximum that is allowed by the Tivoli NetView
An internal error occurred while the Tivoli NetView Graphic Monitor Facility host subsystem (GMFHS).
Graphic Monitor Facility host subsystem (GMFHS) was
processing a network command. An error report is System action
logged by the Network Command Manager in the
GMFHS error log. The associated command was The command is not sent.
previously displayed with a IHS3700I or a IHS3701I
message. Operator response
Determine the maximum length that is allowed. If
System action possible, shorten the command and then send the
The error is logged in the GMFHS log. command again. If the problem persists, contact your
system programmer.
Operator response
Shorten the length of the command text. See the IBM Z
System programmer response Programmer's Guide for information about commands
Locate the error report in the GMFHS error log and that are to be sent to Network Management Gateways
determine the cause of the system error. If you cannot and element management systems using GMFHS.
correct the error, save the error log file and have the
IHS3729E A system error has occurred
information available when you contact your IBM
formatting the command in the
Support Center
workstation.
See IBM Z NetView Troubleshooting Guide for
additional information. Explanation
IHS3727E A system error occurred in The workstation created a command that the host
DUIFSSCO while processing this cannot recognize. The associated command was
command.
previously displayed with a IHS3700I or a IHS3701I System action
message.
The command execution fails because it cannot be
delivered to the NMG. This error is logged in the
System action GMFHS error log for the Network Command Manager
The error is logged by the Network Command Manager component.
in the IBM Z NetView Graphic Monitor Facility host
subsystem (GMFHS) error log. Operator response
Operator response
Activate the program-to-program receiver application.
System programmer response See the IBM Z NetView Application Programmer's
Find the error report in the GMFHS error log and have Guide for information about setting up a program-to-
the information available when you contact your IBM program receiver application, and see IBM Z NetView
Support Center. User's Guide: NetView for information about activating
program-to-program applications.
additional information. IHS3759I The remote console string is not
defined correctly.
IHS3733E A system error occurred on the
workstation.
Explanation
Explanation An error occurred while looking for the remote console

command or its parameters.
A general system error has occurred during the
command exit execution.
System action
System action The remote console is not started.
The command exit fails and the error is logged in the

Operator response
Tivoli NetView Graphic Monitor Facility error log.
Operator response
Do the following:
System programmer response • See the IBM Z NetView Customization Guide for
Locate the error report in the Tivoli NetView Graphic information about remote console support, and
Monitor Facility error log and have the information correct the remote console command string
available when you contact your IBM Support Center. definition for the appropriate resources in the
• Reload RODM.
IHS3755E GMFHS has determined that the
PPI receiver application is not
information.
active.
IHS3760I The remote console support failed
Explanation to start.
The Tivoli NetView Graphic Monitor Facility host
Explanation
subsystem (GMFHS) Network Command Manager has
determined that the program-to-program Interface An error occurred starting the remote console. The
(PPI) Network Management Gateway (NMG) transport error was caused by one of the following reasons:
application is not active.
• The remote console command is not executable on
the console's operating system.

• There are insufficient system resources to start the appropriately defined. Increase the appropriate
program. timeout values if necessary.
• Incorrect parameters were supplied to the remote See IBM Z NetView Troubleshooting Guide for
console command. additional information on command request timeout
scenarios.
System action
IHS3762I The NetView task DUIFSSCO is not
A remote console is not started. active.

Contact your system programmer. You must start the scope checker DUIFSSCO IBM Z
NetView task before you can issue this command. This
System programmer response task performs scope checking, span checking, and
Alert history request support for the Tivoli NetView
Do the following: Graphic Monitor Facility host subsystem (GMFHS).
• Correct the definition in the remote console
command string for the appropriate resources in the Operator response
Start the DUIFSSCO task in IBM Z NetView. If
• Reload RODM. DUIFSSCO remains unavailable, contact your system
See the IBM Z NetView Resource Object Data Manager programmer.
information. System programmer response
IHS3761I GMFHS is not available or the Verify that the GMFHS interface to Scope checker is
command has timed out at the available by issuing the GMFHS STATUS command
workstation. from the IBM Z NetView operator.
See IBM Z NetView Command Reference Volume 1 (A-
Explanation N) for information on GMFHS operator commands.
The Tivoli NetView Graphic Monitor Facility host IHS3763E GMFHS has encountered an error
subsystem (GMFHS) session is inactive for one of the in the RODM configuration
following reasons: attributes.
• GMFHS has not been started.
Explanation
• The connection to GMFHS is inactive.
• The graphic data server timed out the request to An error occurred when the Tivoli NetView Graphic
GMFHS. Monitor Facility host subsystem (GMFHS) attempted to
process a network command. The resource
configuration definition in the Resource Object Data
Operator response
Manager (RODM) is not valid and GMFHS has been
Do the following: initialized with configuration errors.
• If the session with IBM Z NetView failed, issue a
NETCONV command to re-establish your session System action
with the topology server and IBM Z NetView. The error is logged in the GMFHS error logs.
• Contact your system programmer to start GMFHS if
NETCONV is successful and the GMFHS session is Operator response
still inactive.
Start GMFHS if it is not active. If GMFHS is active,
verify that all GMFHS subtasks are initialized and ready Do the following:
to receive requests. • Locate the information in GMFHS error logs for
Verify that the timeout values that are specified for the Network Configurator Manager.
workstation application issuing this message are
• Reconfigure the resource definitions in the RODM See IBM Z NetView Troubleshooting Guide and the IBM
database to enable the command execution. Z NetView Resource Object Data Manager and GMFHS
• Synchronize GMFHS with RODM by issuing a GMFHS Programmer's Guide for additional information.
CONFIG NETWORK command. IHS3767I The COS gateway reported an
See IBM Z NetView Troubleshooting Guide and the IBM error from the service point
Z NetView Resource Object Data Manager and GMFHS application.
Programmer's Guide for additional information.
Explanation
IHS3764I The RODM configuration attributes
for the NMG or domain are not The Common Operations Services (COS) gateway
defined for commands. attempted to deliver the command to the service point
application and received an error condition that
Explanation indicated either no response was received or that the
response was not valid.
The Tivoli NetView Graphic Monitor Facility host
subsystem (GMFHS) cannot process the network Operator response
control command. The resource configuration
definition for the Network Management Gateway If the error persists, contact your system programmer.
(NMG) or domain in the Resource Object Data Manager
(RODM) database is valid, but is not applicable for the System programmer response
attempted network control command.
Verify that the service point application is working
Possible reasons for the error are: correctly.
• The TransportProtocolName in the NMG_Class is IHS3768I The COS gateway task is not
NONE. active.
• The TransportProtocolName in the NMG_Class is
OST and the SessionProtocolName in the Explanation
Non_SNA_Domain_Class is DOMS010.
The Common Operations Services (COS) gateway task
• The SessionProtocolName in the DUIFCSGW is not available for one of the following
Non_SNA_Domain_Class is NONE. reasons:
• The PresentationProtocolName in the
• COS gateway autotask is not initialized.
Non_SNA_Domain_Class is NONE.
• COS gateway ended abnormally.
• The PresentationProtocolName in the
Non_SNA_Domain_Class is DOMP020 and no
command text is specified in the command text Operator response
attributes of the Non_SNA_Domain_Class of the Contact your system programmer.
GMFHS_Managed_Real_Resources_Class.
System action
Start the COS gateway autotask. If this is
The error is logged in the GMFHS error log. unsuccessful, retrieve the IBM Z NetView log and
contact your IBM Support Center.
Operator response
Contact your system programmer. additional information.
IHS3769I The COS gateway cannot establish
System programmer response a session with a distributed
Do the following: NetView program.
• Locate the information in the GMFHS error log.
Explanation
• Reconfigure the resource definitions in the RODM
database to enable the command execution. The Common Operations Services (COS) gateway
cannot establish a session with a distributed NetView
• Issue a GMFHS CONFIG NETWORK command to give
program for one or more of the following reasons:
GMFHS access to the configuration changes.
• The distributed IBM Z NetView is not active.

• The COS gateway autotask is not active on a • Browse the IBM Z NetView log. If installation exit
distributed IBM Z NetView. DSIEX19 rejected the command, message BNH192E
• The Resource Object Data Manager (RODM) attribute is logged.
CommandRouteLUName does not match the IHS3771E The RODM NMG attributes are not
distributed IBM Z NetView name. defined correctly or the NMG has
detected an error while
Operator response attempting to deliver a command.
Explanation
System programmer response This error might have occurred for one of the following
reasons:
Do the following:
• The Resource Object Data Manager (RODM)
• Verify that the distributed IBM Z NetView and COS
TransportProtocolName attribute is not defined
gateway autotasks are active.
correctly.
• Verify that the RODM attribute
• An incorrect service point name was entered in the
CommandRouteLUName matches the distributed
command.
IBM Z NetView name.
• The PU or LU is not active.
and GMFHS Programmer's Guide for additional • The service point application is on an SSCP-PU NMG
information. and the RODM NMG WindowSize attribute is not set
to one.
IHS3770E The COS gateway does not • The service point application is on an SSCP-PU NMG
recognize the command or and another application has generated a command
received an error from the Tivoli to the service point application that has caused a
NetView RUNCMD processor task collision.
DSIGDS.
System action
Explanation
The command is not delivered and command
The Common Operations Services (COS) gateway does execution fails. An error report is logged to the Tivoli
not recognize the command for one of the following NetView Graphic Monitor Facility host subsystem
reasons: (GMFHS) database. An error message will also be
• The RUNCMD command processor DSIGDS is not logged by the COS Gateway autotask in the IBM Z
active. NetView system log. The associated command was
previously displayed with a IHS3700I or a IHS3701I
• The command contains characters that are not valid
message.
or has an incorrect length.
• The operator is not authorized to issue the
Operator response
command.
• Installation exit DSIEX19 rejected the command. Retry the command. If the error persists, contact your
system programmer.
Operator response
First ensure that the RODM TransportProtocolName
and the NMG WindowSize attributes are correctly
System programmer response defined. Then ensure that the PU and LU are active.
Do the following: Check the IBM Z NetView log for error messages
related to COS Gateway processing errors to
• If necessary, activate the RUNCMD command determine if this failure occurred because of a collision
processor DSIGDS. or some other related failure. The associated COS
• Verify that the command is correct. Gateway message is DUI394E.
• Verify that the operator is authorized to issue the See the IBM Z NetView Resource Object Data Manager
command. and GMFHS Programmer's Guide and IBM Z NetView
User's Guide: NetView for additional information.
IHS3772I The OST or PPT is not active. Explanation
The NetView Graphic Monitor Facility host subsystem
Explanation (GMFHS) cannot complete a command because the
You issued a command but your IBM Z NetView OST is targeted resource's domain was added to the
not active or IBM Z NetView is in the process of Resource Object Data Manager (RODM) after GMFHS
ending. was configured. Commands will not be executed for
resources within this domain until GMFHS is
reconfigured.
Operator response
Message Variables
Log on to IBM Z NetView if your previous session
ended. If IBM Z NetView is down, notify your system domain
programmer. The name of the domain.

Restart IBM Z NetView. The command will not be sent to the native element
management system. The error is logged in the
IHS3781E An error has been detected in the GMFHS error log by the Network Command Manager.
response returned from the NMG
for domain domain.
Operator response
Explanation Contact your system programmer.
The NetView Graphic Monitor Facility host subsystem

(GMFHS) detected missing data or data that is not
valid in the response that was returned from the Issue the GMFHS CONFIG NETWORK command to
Network Management Gateway (NMG) for the reconfigure the entire network with the current RODM
specified domain. definitions. Or, locate the error report in the GMFHS
error log and issue the GMFHS CONFIG DOMAIN
Message Variables
command for the domain that has been reported as
domain uninitialized to GMFHS.
The domain name.
System action information about reconfiguring GMFHS.
The status of the command at the service point is IHS3813I The command command is
unknown.
scheduled to be run.

Retry the command. If the error persists, contact your The command is scheduled for running by the host
system programmer. IBM Z NetView program. The response data will be
displayed with a IHS3814I message. The correlator
System programmer response number connects the command to the response.
Do the following: Message Variables
• Locate the message that is logged by the Network command
Command Manager in the GMFHS error log and The command that is run by the IBM Z NetView
determine the cause for the error. program.
• Determine the cause of the problem at the NMG or IHS3814I response
element management system and fix the problem.
IHS3783I The domain domain was added to Explanation
RODM after GMFHS was
configured and commands are not
with a IHS3813I message. The same correlator
currently allowed for resources
number is on both the response and the command.
within this domain.
Message Variables

response Operator response
The text of the command response.
Retry the command. If the error occurs again, contact
IHS3815I The task DUIFSSCO has your system programmer.
encountered a RODM query
failure. System programmer response
Increase the value of LCON-ALERT-CMD-TIMEOUT in
Explanation nDUIGINIT, if necessary. See the Graphic Monitor
The IBM Z NetView task DUIFSSCO cannot Facility host subsystem keywords section in the IBM Z
successfully query the Resource Object Data Manager NetView Troubleshooting Guide for information.
(RODM) for a list of resource span names. The
IHS4000I Server Properties file could not be
associated command was previously displayed with a
accessed. Program Defaults will
IHS3700I or IHS3701I message.
be used.
System action
Explanation
The resource specific command is not processed. A
The server.properties file which contains
message will be logged in the IBM Z NetView log by
customization parameters for the NetView
the scope checker task DUIFSSCO.
management console topology server cannot be
accessed.
Operator response
Contact your system programmer. System action
The topology server will utilize predetermined default
System programmer response values for all of the customization parameters.
Locate the IBM Z NetView scope checker host
message BNH088I which indicates the return code Operator response
and reason code that are associated with the RODM
Issue the tserver utility -p command to obtain a
query request that failed. Take the appropriate
summary of the current settings for all customization
corrective actions and have the user retry the request
parameters.
if necessary. See the IBM Z NetView Resource Object
Data Manager and GMFHS Programmer's Guide for
additional information. System programmer response
IHS3816I No response is expected for this Do the following:

command. 1. Verify the BINDIR setting and determine if the
\BINDIR\TDS\server\config\server.properties file
Explanation exists.
You have issued either the Cancel or the Go command. 2. If server.properties file can not be found reinstall
No response is generated for either of these the topology server.
commands. As a result of this command, responses IHS4001I Unknown keyword
can be generated for previously issued commands and unknown_keyword found in server
will be displayed under the previous command's properties file on line linenum.
correlator number. There is no action to be taken.
IHS3817I The request to the NetView task Explanation
DUIFFSCO timed out.
While reading the server.properties configuration file,
an unknown keyword was found. The keyword and its
Explanation value, if any, are disregarded.
The request to the NetView DUIFSSCO task has timed Message Variables
out. The timeout value is defined by LCON-ALERT-
CMD-TIMEOUT in DUIGINIT. unknown_keyword
The name of the unknown keyword that was
detected.
System action
linenum linenum
The line number in the server.properties file where The line number in the server.properties file where
the unknown key word was detected. the keyword without '=' delimiter was found.

The topology server disregards the unknown keyword The NetView management console topology server
and its value, if any. uses the value of the last entry found.

Edit the server.properties file and remove or comment Edit the server.properties file and remove or comment
out the unknown keyword. This will keep this message out the unwanted entry. Reinitialize the topology
from reappearing if the topology server is reinitialized. server.
IHS4002I No = delimiter found for keyword IHS4004I Invalid value found for keyword
keyword on line linenum. Default inv_keyword on line linenum.
will be used. Default will be used.
While reading the server.properties configuration file While reading the server.properties configuration file
no '=' delimiter was found for a valid keyword. In this an incorrect value was found for a specific keyword.
case the default value for the keyword will be used. The default value for this keyword will be used.
keyword inv_keyword
The name of a valid keyword which has no '=' The name of a valid keyword which was found to
delimiter. have an incorrect value.
linenum linenum
The line number in the server.properties file where The line number in the server.properties file where
the keyword without '=' delimiter was found. the incorrect value was found.

The NetView management console topology server The topology server uses the default value of the
uses the default value for the keyword. keyword.

Edit the server.properties file and add the '=' delimiter. Edit the server.properties file and correct the incorrect
Reinitialize the topology server. value. Reinitialize the NetView management console
topology server.
IHS4003I Multiple entry found for keyword
keyword on line linenum. Last one IHS4005I Invalid syntax found for keyword
read will be used. inv_keyword on line linenum.
Default will be used.
Explanation
Explanation
While reading the server.properties configuration file
multiple entries were found for the same keyword. In While reading the server.properties configuration file
this case the value for the last one read will be used. incorrect syntax was found for a specific keyword. The
default value for this keyword will be used.
Message Variables
Message Variables
keyword
The name of a valid keyword which has no '=' inv_keyword
delimiter. The name of a valid keyword which was found to
have an incorrect syntax.

linenum example, the tserver command file or script sets up
The line number in the server.properties file where the environment for the component of the topology
the incorrect syntax was found. server to run under. Reinitialize the topology server.
IHS4008I Value for keyword max_keyword
System action on line linenum is greater than
The topology server uses the default value of the max_default. Maximum value
keyword. max_default will be used.
Edit the server.properties file and correct the incorrect Many of the configuration parameters used in the
syntax. Reinitialize the topology server. server.properties file have maximum limits. If the user
enters a value which exceeds the maximum allowed,
IHS4006I No entry found for keyword the topology server will adjust the value to the
no_keyword. Default will be used. maximum allowed.
Message Variables
Explanation
max_keyword
While reading the server.properties configuration file
The name of a valid keyword which was found to
no entry was found for one of the defined keywords.
have exceeded its maximum value.
Default value for this keyword will be used.
linenum
Message Variables The line number in the server.properties file where
no_keyword the incorrect value was specified.
The name of a valid keyword which was found to max_default
have no entry. The maximum value allowed for this keyword.

The topology server uses the default value of the The topology server uses the maximum default value
keyword. of the keyword.

Edit the server.properties file and add an entry for the Follow these steps:
missing keyword. Reinitialize the topology server.
1. Edit the server.properties file and correct the value
IHS4007I No value found for BINDIR. Can to the maximum allowed.
not access Server Properties file. 2. Reinitialize the server.
Program Defaults will be used.
IHS4009I Value for keyword min_keyword on
Explanation line linenum is less than
min_default. Minimum value
While trying to read the server.properties file the min_default will be used.
topology server found no value for the BINDIR
environment variable. As a result program defaults for
Explanation
all the customization parameters will be used.
Many of the configuration parameters used in the
System action server.properties file have minimum limits. If the user
enters a value which is less than the minimum
The NetView management console topology server allowed, the topology server will adjust the value to
uses the program defaults for all values normally the minimum allowed.
found in the server.properties file.
Message Variables
System programmer response min_keyword
Ensure that the command to start the topology server
be less than its minimum value.
component defined the BINDIR environment variable,
which gives access to server.properties file. For
linenum 1. Edit the server.properties file and correct the
The line number in the server.properties file where timeout values to conform to the keyword
the incorrect value was specified. dependency.
min_default 2. Reinitialize the topology server.
The minimum value allowed for this keyword.
IHS4011I Value for keyword max_keyword
on line linenum is greater than
System action max_default. Maximum value
The topology server uses the minimum default value of max_default will be used.
the keyword.
Explanation
System programmer response Many of the configuration parameters used in the
Follow these steps: server.properties file have maximum limits. If the user
enters a value which exceeds the maximum allowed,
1. Edit the server.properties file and correct the value the topology server will adjust the value to the
to the minimum allowed. maximum allowed.
2. Reinitialize the topology server.
Message Variables
IHS4010I Value for keyword time_keyword max_keyword
has been adjusted to time_value The name of a valid keyword which was found to
+1, 1 greater than time_value. have exceeded its maximum value.
linenum
Explanation
The line number in the server.properties file where
The keywords timeoutSmall, timeoutMedium, the incorrect value was specified.
timeoutLarge, and timeoutHuge are dependent on one max_default
another: The maximum value allowed for this keyword.
• Medium must be at least one greater than Small
• Large must be at least one greater than Medium System action
• Huge must be at least one greater than Large. The topology server uses the maximum default value
of the keyword.
This message is issued when the topology server must
adjust one of these keyword values to conform to this
dependency. System programmer response
Message Variables Follow these steps:
time_keyword 1. Edit the server.properties file and correct the value

The name of a valid timeout keyword which had to to the maximum allowed.
be adjusted. 2. Reinitialize the server.
time_value+1 IHS4012I Value for keyword min_keyword on
The new value that this timeout keyword was line linenum is less than
adjusted to. min_default. Minimum value
time_value min_default will be used.
The name of a timeout keyword which this
keyword must be one greater than. Explanation
Many of the configuration parameters used in the
System action
server.properties file have minimum limits. If the user
The topology server adjusts the timeout values to enters a value which is less than the minimum
conform to the keyword dependency. allowed, the topology server will adjust the value to
the minimum allowed.
Follow these steps: min_keyword
be less than its minimum value.

linenum 2. Reinitialize the topology server.
The line number in the server.properties file where
IHS4014E Unable to write to audit log. Error
the incorrect value was specified.
occurred in module1 on line line1.
min_default Audit entry originated in module2
The minimum value allowed for this keyword. line2 is not written to the audit log.

The topology server uses the minimum default value of An error occurred while attempting to write to the
the keyword. audit log.
Message Variables
module1
Follow these steps:
The module name in which the error occurred.
1. Edit the server.properties file and correct the value line1
to the minimum allowed. The line number, in module1, where the error
2. Reinitialize the topology server. occurred.
IHS4013I String size string_size for keyword module2
keyword on line linenum is greater The module name in which the audit log entry
than allowed. String is truncated originated.
to maximum length of max_length. line2
The line number, in module2, where the audit log
Explanation entry originated.
The string value for this keyword in the

System action
server.properties file can not exceed the maximum
length. If the user enters a value which is greater than The message is also written to the message log,
the maximum length allowed, the topology server will ihsmessage.log. The audit log entry is not written to
truncate the value to the maximum length allowed. the audit log. Processing of the topology server
continues.
Message Variables
string_size System programmer response
The size of the user-specified string value for
keyword. Ensure that your operating system is able to access
the audit log. The audit log, ihsaudit.xml, is located in
keyword
one of the following directories:
The name of a valid keyword, in the
server.properties file, that was found to contain a • For Windows: %BINDIR%\TDS\server\log
value which was greater in length than the • For UNIX: %BINDIR%/TDS/server/log
maximum length allowed.
More information about the audit log can be found in
linenum
the IBM Z NetView User's Guide: NetView Management
The line number, in the server.properties file,
Console.
where the incorrect value was specified.
max_length Though this is a suspected operating system file
The maximum length of the value allowed for this access error, rename the audit log so that a new
keyword. ihsaudit.xml file will be created the next time an audit
log entry is generated.
System action If the error persists, contact IBM Software Support.
The topology server truncates the value of the IHS4015E Return code rc from module
keyword to the maximum allowed length. module1 called from module
module2 on line line_num
System programmer response indicates an error when accessing
the audit log.
Follow these steps:
1. Edit the server.properties file and correct the length
of the value to the maximum allowed.
An error occurred while attempting to access the audit Re-issue the command. If the problem persists,
log. contact your system programmer.
Message Variables
rc
The return code indicating the error. Check the error and message logs for information. If
you cannot fix the problem, contact IBM Software
module1 Support.
The module name returning the error.
module2 IHS4121E Error sending data to task
The module name in which the error occurred. task_name. Error code
major_error_code -
line_num minor_error_code.
The line number, in module2, where the error
occurred.
Explanation
System action The command was not able to send data to the
process that handles your request.
The message is also written to the message log,
ihsmessage.log. The audit log entry is not written to Message Variables
the audit log. Processing of the topology server task_name
continues. The name of the task that processes the request.
major_error_code
System programmer response The major error code.
Ensure that your operating system is able to access minor_error_code
the audit log. The audit log, ihsaudit.xml, is located in The minor error code.
one of the following directories:
• For Windows: %BINDIR%\TDS\server\log System action
• For UNIX: %BINDIR%/TDS/server/log The command stops.
More information about the audit log can be found in
the IBM Z NetView User's Guide: NetView Management System programmer response
Console. Re-issue the command.
Though this is a suspected operating system file If the problem persists, check the error and message
access error, rename the audit log so that a new logs for information. If you cannot fix the problem,
ihsaudit.xml file will be created the next time an audit contact IBM Software Support.
log entry is generated.
IHS4122E Error sending data to task
If the error persists, contact IBM Software Support.
task_name. Error code
IHS4120I An error occurred trying to major_error_code -
determine the PID (process ID) for minor_error_code. Ensure that the
a process. Command processing destination task is running.
terminates.
Explanation
Explanation The command was not able to send data to the
A process ID (PID) was needed to execute a process that handles your request, most likely
command, but the information was not available. because the task that processes your request is not
running.
The command stops. task_name
The name of the task that processes the request.
major_error_code
The major error code.

minor_error_code System programmer response
The minor error code.
Try the operation again. If the problem persists, follow
these steps:
System action
1. Stop the topology server and the topology
The command stops. communications server.
On UNIX, after stopping these processes, run the
tserver stop -f command).
Ensure that the task is running. If the task is running, 2. Restart the server.
try the operation again.
If the problem persists, check the error and message
logs for information. If you cannot fix the problem, IHS4125E Error registering task task_name.
contact IBM Software Support. Error code major_error_code -
minor_error_code. Contact the
IHS4123E Ihsccmd was invoked with only system programmer.
parameter_number parameters. At
least three parameters are
Explanation
required.
The command being run is trying to register a task with
Explanation the ACM communications subsystem. The registration
is failing.
The script that invoked the ihsccmd executable did not
include the correct number of parameters. Message Variables
Message Variables task_name

The name of the task being registered.
parameter_number
The number of parameters passed to the ihsccmd major_error_code
executable. The major error code.
minor_error_code
System action The minor error code.
The command stops.

System action
System programmer response The command stops.

IHS4124E Error registering task task_name. Contact IBM Software Support.
The task is already registered.
Rerun the command. If the IHS4126E Error freeing ACM memory. Error
problem persists restart the code major_error_code -
system. minor_error_code. Function
completed, but future work may
Explanation be impaired.
The command being run is trying to register a task with

Explanation
the ACM communications subsystem. The registration
is failing because the task is already registered and The command attempted to free ACM memory, but the
duplicate registrations are not allowed. The problem free operation failed. The command that was
might result from a process that temporarily has the executing at the time completed successfully, but this
task registered. error might indicate a more serious problem in the
system.
Message Variables
Message Variables
task_name
The name of the task being registered. major_error_code
The major error code.
System action minor_error_code
The command stops.
The command completed successfully, but the ACM The command completed.
memory was not freed.
If task registration errors occur for this task in the
If these types of errors persist, stop and restart the future, reinitialize the server.
server.
If the problem continues, contact IBM Software
If the problem persists, contact IBM Software Support. Support.
IHS4127E Error allocating ACM memory. IHS4131E Unable to queue request for later
Error code major_error_code - processing. Error at location
minor_error_code. location, error code error code.
The command attempted to allocate memory from the The command cannot be queued for later processing.
ACM memory pool. The allocation failed and the The error code identifies a possible explanation as to
command did not complete successfully. the cause of this error.
major_error_code location
The major error code. The location of the error.
minor_error_code error_code
The minor error code. On UNIX systems, the error codes are located in
the /usr/include/sys/errno.h file. On Intel systems,
System action the error codes are:
The memory allocation failed and the command failed. • 1253 - Error writing to the specified file
• 1254 - Error closing the specified file
System programmer response • 1250 - Error opening the specified file
Try the command again. If the problem persists, • 1251 - Out of memory error
reinitialize the server. • 1252 - Out of memory error
If the problem still persists, contact IBM Software
Support. System action
IHS4128E Error deregistering task The command is not queued.
task_name. Error code
major_error_code - System programmer response
minor_error_code. If future errors
occur, restart the system. Do one of the following:
• If an out of memory condition occurred, verify that
Explanation the system has enough virtual memory.
A task registered to the ACM subsystem cannot be • If an error occurred reading, writing, or closing a file,
deregistered. This might stop you from executing verify that the filename is valid.
commands in the future. Try the command again. If the problem persists,
Message Variables contact IBM Software Support.
task_name IHS5001A Unable to sign on to the topology

The name of the task. server. User name: name. Reason:
major_error_code User name and password not
The major error code. authorized to connect to the
topology server.
minor_error_code

Explanation IHS5004A Unable to sign on to the topology
server. Reason: Versions are not
The specified user name is not defined to the server, or
compatible.
the password is incorrect for the user name.
name The version of the topology server is not compatible
The user name entered as a command parameter with this version of the command profile editor.
or at the command prompt.
System action
System action
The program ends.
The program ends.
Operator response
Operator response
Ensure that the topology server and the command
Correct the user name or the password. profile editor are running the same versions.
IHS5002A Unable to sign on to the topology IHS5005A Unable to sign on to the topology
server. Reason: Unable to server. Reason: User name name
communicate with NetView host. already signed on to command
profile editor.
Explanation
The topology server is unable to communicate with Explanation
NetView host. The user specified in name is already signed on to the
command profile editor. Only one user can be signed
System action on to the command profile editor at a time.
The program ends. Message Variables
name
Operator response The user is already signed on to the command
Ensure that the communications session between the profile editor.
topology server and host NetView program is started.
If necessary, issue the host NetView command System action
NETCONV to establish the session.
The program ends.
IHS5003A Unable to sign on to the topology
server. User name: name Operator response
Wait until the instance currently running ends, and
Explanation
then try to sign on again.
An error occurred when you signed on to the topology
IHS5006A Unable to sign on the topology
server, but the specific reason cannot be determined.
server. Reason: The topology
Message Variables server is not available.
name
The user name entered as a command parameter Explanation
or at the command prompt. This message is issued when the topology server does
not reply at the given IP host name or address.
System action
The program ends. System action
The program ends.
Operator response
Save the topology server error log file. The file name is Operator response
defined by the EGVERRORFILE in the CONFIG.SYS file. Contact the IBM Support Center.
Contact the IBM Support Center for assistance in
examining this file.
IHS5008A The connection to the topology Operator response
server has been lost. If the command indicator must be deleted, first
remove it from each command that is using it.
Explanation
IHS5015A Unable to run the command profile
The command profile editor has lost connectivity with editor. The command profile editor
the topology server. is already in use.

The command profile editor cannot continue to Only one instance of the command profile editor can
operate without the services of the topology server. be run at one time.
The command profile editor program ends.
System action
Operator response
The program ends.
Note any other messages and see the IBM Z NetView
Troubleshooting Guide for more information regarding
Operator response
this error.
Wait until the instance currently running ends, and
IHS5011A The topology server has not then try to sign on again.
responded within the expected
time period. IHS5016A Unable to sign on to the topology
server while view conversion is in
Explanation progress.
The topology server failed to respond to a request

Explanation
from the command profile editor.
The topology server is currently converting views. A
System action sign on is not allowed at this time.
The command profile editor ends.

System action
Operator response The program ends.
Contact the IBM Support Center.

Operator response
IHS5013A The command indicator name Wait until topology server has completed converting
cannot be deleted because it is in views, and then try to sign on again.
use by the following commands:
commands IHS5017A A command set cannot contain
itself.
Explanation
Explanation
Each command set name must be unique. During the
creation of a new command set or the update of an You attempted to include a command set inside itself.
existing command set, a name was entered that was
already in use. System action
Message Variables The addition is ignored.
name IHS5018A Removal of object name failed -
The name of command set being used. not found in the command set or
commands profile.
The commands using the current command
indicator. Explanation
The object specified was not removed.
System action
Message Variables
The command indicator description is reset to its
original text.

object name System action
The name of the object being removed.
The program ends.
System action
Operator response
The program continues processing the response file
Examine the error log file to determine the cause of
and updates the command database.
the system error. If the cause of the system error
cannot be determined or corrected, save the log file
Operator response and contact the IBM support center.
If the object to be removed is incorrect, update the IHS5024A Response file response file has one
response file with the correct information and run the or more syntax errors. See log log
utility again. Otherwise, no action is required. file for more information.
IHS5020A An internal error has occurred.
Function: function Line: line Explanation
Exception Name: exception name
The response file contains one or more syntax errors.
Error ID: errorid
The error log file lists each of the errors along with the
line numbers in the response file where each was
Explanation found.
Each command profile must have a unique name. The Message Variables
name of the command profile being created or
updated is already in use. response file
The name of the response file.
Message Variables
log file
function The name of the log file.
The name of the function that caused the error.
line System action
The line in which the error occurred.
The program ends.
exception name
The name of the exception generated. Operator response
errorid
Examine the error log file and correct each response
The error ID of the exception.
file syntax error listed. Run the utility again with the
modified response file.
System action
IHS5025A Response file response file could
The program ends.
not be generated. Possible disk
write failure.
Operator response
Copy the information from the message and save a Explanation
copy of the error log. The error log is specified in the
An attempt to write the response file to the disk failed.
CONFIG.SYS file in the EXQERRORFILE line. Contact
the IBM support center. Message Variables
IHS5022A Unexpected system error has response file

occurred. See log log file for more The name of the response file.
information.
System action
Explanation The program ends.
An unexpected system error was encountered. The
error log file will contain additional information, such Operator response
as the system call that failed and the return code.
Ensure that enough free disk space exists to generate
Message Variables the response file. Run the utility again.
log file
The name of the error log file.
IHS5026A Response file response file could Explanation
not be processed successfully. See A DOS error was encountered while processing the
log log file for more information. response file.
The response file contains errors which prevent the function

utility from properly updating the command database. The function being performed when the error
These errors are listed in the error log file. occurred.
rcode
Message Variables
The DOS return code.
response file file name
The name of the response file being processed. The name of the response file being processed.
log file line
The name of the error log file being processed. The line in the response file that was being
processed when the error occurred.
System action
The program ends.
Operator response
Examine the error log file and correct each response Operator response
file error listed. Run the utility again with the modified Ensure that the path and file name are correctly
response file. specified on the command line. Ensure that the file is
IHS5027A Unable to open file file name. not being used by another process and is not
protected. Examine the error log file for any system
errors that might have been logged.
Explanation
If the cause of the error cannot be determined, contact
A file cannot be opened for one of the following
the IBM support center.
reasons:
IHS5029A Utility started processing response
• The file cannot be found.
file response file on date at time
• The file is protected or is being used by another
process.
Explanation
Message Variables
This message marks the date and time when the utility
file name began processing or generating a response file.
The path and file name of the file to be opened.
Message Variables
System action response file

The response file being processed.
The program ends.
date
The start date.
Operator response
time
Ensure that the path and file name are correctly The start time
specified on the command line. Ensure that the file is
not being used by another process and is not System action
protected. Examine the error log file for any system
errors that might have been logged. The program continues running.
IHS5028A DOS error encountered,

Operator response
function=function, rc = rcode, file =
file name, line = line. None
IHS5030A Utility completed processing on
date at time.

Explanation parameter
The duplicated parameter.
This message marks the date and time when the utility
ended.
System action
Message Variables
The program ends.
date
The end date.
Operator response
time
The end time. Run the utility again without the duplicate parameter.
IHS5034A The parameter1 and parameter2
System action parameters are mutually
exclusive.
The program ends.
Explanation
Operator response
Only one of the two listed command line parameters
None
can be used in a single invocation of the utility
IHS5031A Out of memory. program.
Message Variables
Explanation
parameter1
There is not enough memory to run the utility program. The first command line parameter.
parameter2
System action The second command line parameter.
The program ends.
System action
Operator response The program ends.
Stop any unnecessary processes to make more
memory available. Run the utility again. Operator response
IHS5032A Invalid file specification file name. See the syntax of the cpebatch command to determine
which of the two parameters is required for the task.
Explanation Run the utility again.
The path, file name, or both are incorrectly specified IHS5035A No input response file specified.
on the command line.
Explanation
Message Variables
The /I parameter was specified on the command line,
file name
but no response file name was specified.
The path and file name of the file being opened.
System action
System action
The program ends.
The program ends.
Operator response
Operator response
Run the utility again with a valid response file path and
Ensure that the path and file name are correctly
name. See the syntax of the cpebatch command for
specified on the command line.
more information.
IHS5033A Duplicate parameter parameter.
IHS5036A Parameter parameter has invalid
value value.
Explanation
A command line parameter was specified more than Explanation
once.
A command line parameter has an incorrect value.
Message Variables
parameter The input response file was not found in the specified
The command line parameter. path.
value Message Variables
The incorrect value of the parameter.
response file
The input response file name.
System action
The program ends.
Operator response
See the syntax of the cpebatch command to determine Operator response
the correct value for the parameter. Run the utility
again. Ensure that the path and file name are correctly
specified on the command line. Run the utility again.
IHS5037A Unknown parameter parameter.
IHS5040A Unmatched parenthesis detected
in response file response file.
Explanation
An unrecognized command line parameter was Explanation
specified.
The input response file has an unmatched parenthesis.
Message Variables
Message Variables
parameter
The unknown command line parameter. response file
The input response file name.
System action
System action
The program ends.
The program ends.
Operator response
Operator response
See the syntax of the cpebatch command to determine
the correct value for the parameter. Run the utility Determine the location of the unmatched parenthesis
again. in the response file and correct the problem. Run the
utility again with the modified response file.
IHS5038A Missing parameter parameter.
IHS5041A Invalid keyword keyword.
Explanation
Explanation
A required command line parameter is missing.
A keyword in the response file is unrecognized or
Message Variables contains an incorrect character.
parameter Message Variables
The missing command line parameter.
keyword
The incorrect keyword.
System action
The program continues processing the response file to
Operator response find other possible errors, then ends without changing
See the syntax of the cpebatch command to determine the command database.
the correct value for the parameter. Run the utility
again. Operator response
IHS5039A Unable to locate response file Correct the keyword, then run the utility again with the
response file. modified response file.

IHS5042A Unmatched right parenthesis. Operator response
Correct the keyword, then run the utility again with the
Explanation modified response file.
A right parenthesis does not have a corresponding left IHS5045A Duplicate keyword keyword is not
parenthesis. allowed.

The program ends. A keyword was encountered that is already in use.
Message Variables
Operator response
keyword
Match the parenthesis, then run the utility again with
The duplicate keyword.
the modified response file.
IHS5043A Line is too long. System action
Explanation find other possible errors, then ends without changing
A line in the response file is too long. the command database.

The program continues processing the response file to Remove the duplicate keyword, then run the utility
find other possible errors, then ends without changing again with the modified response file.
the command database.
IHS5046A Required keyword keyword
missing in stanza stanza.
Operator response
Shorten the line or, if possible, break it into multiple Explanation
statements. Run the utility again with the modified
A stanza is missing a required keyword.
response file.
Message Variables
IHS5044A Keyword keyword used
improperly. keyword
The required keyword.
Explanation stanza
The stanza requiring the keyword.
A keyword is improperly used if the keyword is one of
the following:
System action
• a list keyword that does not begin a list.
• a single value keyword that begins a list. find other possible errors, then ends without changing
• improperly nested. the command database.
• not contained within a stanza.
Operator response
Message Variables
Add the required keyword to the stanza, then run the
keyword
The improperly used keyword.
IHS5047A Keyword keyword does not belong
System action in stanza stanza.
find other possible errors, then ends without changing Explanation
the command database. A stanza contains a keyword that does not belong
there.
Message Variables
keyword Explanation
The incorrect keyword.
The DELETE keyword is improperly used to delete an
object that was not found in a folder.
System action
Message Variables
find other possible errors, then ends without changing object name
the command database. The name of the object being deleted.
Remove the keyword from the stanza, then run the The program continues processing the response file
utility again with the modified response file. and updates the command database.
IHS5048A Object object name is incomplete. Operator response
Explanation If the object to be deleted is incorrect, update the

response file with the correct information and run the
An object being added to the command database with utility again. Otherwise, no action is required.
incomplete information.
IHS5052A Undefined object object name
Message Variables referenced.
object name
The name of the object being added. Explanation
An object references another object which has not yet
System action been defined.
The program continues processing the response file to Message Variables
find other possible errors, then ends without changing
the command database. object name
The name of the unknown object being referenced.
Operator response
System action
Ensure that the object has all required keywords
correctly specified. Run the utility again with the The program continues processing the response file to
modified response file. find other possible errors, then ends without changing
IHS5049A Update is not allowed. Use /M
option. Operator response
Explanation Ensure that the referenced object is defined before the

current object in the response file. Run the utility again
The response file will cause the utility program to with the modified response file.
modify or delete existing information in the current
command database. The /M option must be used to IHS5053A Field field name has invalid value
alter the database in this way. value.
The program continues processing the response file to An attempt to set a field was not successful because
find other possible errors, then ends without changing the value is incorrect. The value is incorrect for one of
the command database. the following reasons:
• The text is null.
Operator response • The text contains an incorrect character.
Run the utility again with the /M option. • The command indicator is assigned a value that is
IHS5051A not an integer.
Delete of object name failed.
Message Variables

field name System action
If this message occurs while running the utility
value.
program, the program continues processing the
value response file to find other possible errors, then ends
The incorrect value. without changing the command database.

If this message occurs while running the utility If this message occurs while running the utility
program, the program continues processing the program, remove the duplicate object from the MENU
response file to find other possible errors, then ends stanza, then run the utility again with the modified
without changing the command database. response file.
IHS5057A Field field name value value is out
Operator response
of range.
Correct the field value. If this message occurs while
running the utility program, run the utility again with Explanation
An attempt to set a field was unsuccessful because
IHS5054A Field field name has too long a the value is beyond the acceptable range of values.
value.
Message Variables
Explanation field name
The name of the field.
the value exceeds the maximum length for that field. value
The incorrect value.
Message Variables
field name System action
System action the command database.
find other possible errors, then ends without changing Operator response
Correct the field value, then run the utility again with
Operator response
IHS5058A Field field value value is not
Shorten the length of the field value, then run the contiguous.
IHS5055A An object type with name object Explanation
name already exists.
the field value is not contiguous with existing values.
Explanation
Message Variables
An attempt to add an object to a menu was
unsuccessful because the menu already contains that field name
object. The name of the field.
value
Message Variables
The incorrect value.
object type
The type of object being added to the menu. System action
object name
The name of object being added to the menu.
response file to find other possible errors, then ends
without changing the command database.
If this message occurs while running the utility object name
program, make the value contiguous, then run the The name of the object which cannot be added.
IHS5059A Keyword field name has already System action
been set. If this message occurs while running the utility
Explanation response file to find other possible errors, then ends
A field which can only be set once has already been
set.
Operator response
Message Variables
Remove unneeded objects from the folder, then try to
field name add the new object.
IHS5062A Add of object object name failed -
invalid position.
System action
The program continues processing the response file to Explanation
the command database. An attempt to add an object to a menu was
unsuccessful because it is being added at an incorrect
position. This is an internal error.
Operator response
Message Variables
Remove the field from the stanza, then run the utility
again with the modified response file. object name
The name of the object being added.
IHS5060A Field field name value value is
already being used.
System action
Explanation The program continues processing the response file to
An attempt to set a field was unsuccessful because the command database.
the same value is used elsewhere.
field name Contact the IBM support center.
IHS5064A Delete of object manager name
value
failed - manager in use by the
The value assigned to the field.
following commands: command
list.
System action
The program continues processing the response file to Explanation
The manager cannot be deleted because it is used by
one or more commands.
Change the value to one that is unique, then run the manager name
utility again with the modified response file. The name of the manager to be deleted.
command list
IHS5061A Add of object object name failed - The list of commands using the manager.
folder is full.
System action
Explanation
An attempt to add an object to a folder failed because program, the program continues processing the
the folder contains the maximum number of objects.

response file to find other possible errors, then ends Operator response
Remove the dependency of each of the listed
operators before deleting each of them.
Operator response
IHS5067A Delete of command set command
Remove the dependency of each of the listed set name failed - command set in
commands before deleting each of them. use by the following profiles:
IHS5065A Delete of command command profile list.
name failed - command in use by
the following profiles or command Explanation
sets: object list.
The command set cannot be deleted because it is
used by one or more profiles.
Explanation
Message Variables
The command cannot be deleted because it is used by
one or more profiles or command sets. command set name
The name of the command set being deleted.
Message Variables
profile list
command name The list of profiles using the command set.
The name of the command being deleted.
object list System action
The list of profiles or command sets using the
command.
System action without changing the command database.
program, the program continues processing the Operator response
Remove the dependency of each of the listed profiles
on the command set before deleting each of them.
Operator response IHS5068A Field field name cannot be set -

manager undefined.
Remove the dependency of each of the listed profiles
or command sets before deleting each of them
Explanation
IHS5066A Delete of profile profile name
An attempt to set a field was unsuccessful because it
failed - profile in use by the
references an undefined manager.
following operators: operator list.
Message Variables
The profile cannot be deleted because it is used by The name of the field.
one or more operators.
System action
Message Variables
profile name
The name of the profile being deleted.
operator list
The list of operators using the profile. Operator response
System action Ensure that the referenced manager is defined earlier

in the response file, then run the utility again with the
If this message occurs while running the utility modified response file.
response file to find other possible errors, then ends IHS5069A Field field name cannot be set -
without changing the command database. command is resource
independent.
An attempt to set PAGE_ID or INDICATOR_LIST on a
command page was unsuccessful because the
command is resource independent. A resource System action
independent command cannot specify command The program continues processing the response file to
indicators. find other possible errors, then ends without changing
Message Variables the command database.
field name
Operator response
Remove this field from the command page stanza,
System action then run the utility again with the modified response
file.
find other possible errors, then ends without changing IHS5072A Field field name cannot be set -
the command database. any manager not allowed.
Remove this field from the command page stanza, An attempt to set MANAGER_NAME to 'ANY' on a
then run the utility again with the modified response command page was unsuccessful because the
file. command already has pages with indicators defined.
IHS5070A Field field name cannot be set - Message Variables

command page has defined field name
command indicators. The name of the field.

An attempt to set a field was unsuccessful because The program continues processing the response file to
the command has specified command indicators. find other possible errors, then ends without changing
Message Variables the command database.
field name
Operator response
Remove all pages with defined indicators from this
System action command, then set MANAGER_NAME to ANY. Run the
find other possible errors, then ends without changing IHS5073A Field field name cannot be set -
the command database. command indicator undefined.
Remove this field from the command page stanza, An attempt to add a command indicator to a command
then run the utility again with the modified response page was unsuccessful because the command
file. indicator is undefined.
IHS5071A Field field name cannot be set - Message Variables

command applies to any manager. field name
Explanation
An attempt to set PAGE_ID or INDICATOR_LIST on a System action
command page was unsuccessful because the The program continues processing the response file to
command page has MANAGER_NAME = ANY. A find other possible errors, then ends without changing
command which applies to any manager cannot the command database.
specify command indicators.
Message Variables

Define the command indicator to a manager in the If this message occurs while running the utility
response file, then run the utility again with the program, the program continues processing the
modified response file. response file to find other possible errors, then ends
IHS5074A Unknown error.
Operator response
Explanation
Change the field to a unique value. If this message
An unknown error was encountered. This is an internal occurs while running the utility program, run the utility
error. again with the modified response file.
System action IHS5079A object type object name has

duplicate information in the
If this message occurs while running the utility following profiles or command
program, the program continues processing the sets: object list.
Explanation
Operator response An attempt to add a command or command set to a

folder was unsuccessful because it creates duplicate
Contact the IBM support center. information in one or more profiles or command sets.
IHS5077A The topology server has Message Variables
encountered an internal error.
object type
The type of object being added.
Explanation
object name
The topology server notified the command profile The name of object being added.
editor of an internal error in the server.
object list
The list of profiles or command sets.
System action
The command profile editor closes without saving any System action
changes to your data.
Operator response response file and updates the command database.
See the IBM Z NetView Troubleshooting Guide for more IHS5083A The resource description
information regarding this error. Contact the IBM
description is already in use for
Support Center for further assistance.
this resource manager
IHS5078A Field field name has duplicate
value value in the following Explanation
profiles or command sets: object
Resource descriptions must be unique for each
list.
command indicator under a resource manager.
The listed fields have identical values. The values must description
be unique. The resource description which is not unique for
this resource manager.
Message Variables
field name Operator response
Change the resource description and run the utility
value again.
The duplicated value.
IHS5084A Field field name cannot be set to
object list
value - command indicators exist
The list of profiles or command sets.
outside this boundary.
You attempted to set a field to an incorrect value. Remove the existing response file or specify a different
file name for the output response file and run the
Message Variables
utility again.
field name
IHS5088I Command profile editor utility
program. usage: cpebatch
value.
filename -I | -O [-U:userID] [-
value P:password] [-L1:log file] [-G | -M]
The incorrect value. [-V]

Correct the value. The utility was invoked without parameters or with the
IHS5085A Name or address hostname cannot -? (help) parameter.
be resolved to a valid IP address
or an LU name. Operator response
Invoke the utility using the syntax described in the
Operator response message. See the syntax of the cpebatch command for
Correct the host name. more information.
IHS5086I (rc=return code) IHS5200E The command profile editor is

ending due to a missing DLL file.
Explanation
Explanation
The Command Profile Editor utility has completed
processing. The command profile editor cannot find the IHSE.DLL
file. Verify that the $BINDIR/TDS/server/bin (UNIX) or
Message Variables %BINDIR%\TDS\server\bin (Intel) directory is in the
0 PATH.
No errors
System action
4
Warning logged - processing continues and the The command profile editor ends.
database is updated.
8 Operator response
Error logged - processing continues but the
database is not updated.
Error logged - immediate termination.
Verify that IHSE.DLL exists in the path specified by
Operator response PATH.
Correct the host name. IHS5201E The command profile editor is out
of memory.
IHS5087A Response file Response file already
exists. Explanation
Explanation The command profile editor was unable to obtain

system memory.
The output response file already exists and will not be
overwritten. System action
Message Variables The command profile editor ends.
response file
The name of the existing response file that cannot
be overwritten.

Operator response NT_service_name
The name of the NT service specified on the API
Free some storage by stopping other applications or by
call.
adding storage to the system. Also, confirm that
swapping is enabled. NT_service_call
The name of the NT service API call that failed.
IHS5800E The specified task was not found
NT_specific_return_call
The enum name or numeric value of the error
System action return code as specified in the error.h file that
The task is not executed. ships with the Microsoft Windows SDK.
Contact your system programmer. The IHSXSRV command fails.
Investigate the TMR environment and verify that the Retry the request. Many of the possible errors are self-
task exists. explanatory. Take corrective action if necessary.
IHS5803E Bad CommandString: Invalid input

parms
Explanation IHS5962I Requesting server send message
The command string in the command profile editor is processing.
not valid.
Explanation
Operator response This message confirms that you have requested server
Contact your system programmer. send message processing.
Make sure that the command string in the command The topology server will complete the send message
profile editor is valid. processing you have requested.
IHS5811E No return message was posted by IHS5965I Requesting server configuration

the task. properties display.
The task either timed out or did not return any This message confirms that you have requested to
messages. display the current settings of the configuration
properties.
Operator response
System action
Increase the timeout value in the Console Properties
window. The topology server will display the server
configuration properties in the window in which the
IHS5951E NT_service_name NT_service_call server is running.
API call failed with NT return code
of NT_specific_return_code. IHS5969E Unrecognized service state for
Windows_service_name, state
Explanation returned is
Windows_service_state.
IHSXSRV.EXE encountered an NT API error during
execution. Explanation
Message Variables IHSXSRV.EXE encountered a QueryServiceStatus API
error. An unexpected service state was returned.
Message Variables IHS5976E Cannot open Services Control
Manager, OpenSCManager rc =
Windows_service_name
NT_specific_return_code
The name of the Windows service specified on the
API call
Explanation
Windows_service_state
The service state value IHSXSRV.EXE encountered an OpenSCManager API
error.
The IHSXSRV command fails. NT_specific_return_code
The enum name or numeric value of the error
Operator response return code as specified in the error.h file that
ships with the Microsoft Windows SDK.
Retry the request. If the problem persists, contact
System action
System programmer response The IHSXSRV command fails.
If the problem persists, analyze the unrecognized
state. States are documented in the Microsoft Operator response
Windows SDK help for the QueryServiceStatus API call Retry the request. Many of the possible errors are self-
for Windows. explanatory. Take corrective action if necessary.
IHS5973E Unable to find the PID for process
ihsctp. System programmer response
Explanation
IHS5981I Run 'tserver dbtransfer' before
While trying to stop the topology communications attempting to start the server.
server (ihsctp) process, the process id (PID) for this
process cannot be found. Usually, this error occurs
Explanation
because the process is not currently running.
Additional information might be printed on the line You have installed a new version of the topology
following this message. server, and are using the TSERVER_DB variable to
store the topology server databases in another
System action location, rather than the default installation
directories. However, you have not run the 'tserver
The topology communications server process is not dbtransfer' utility to copy the newly installed
stopped. databases into the location defined by the
TSERVER_DB variable.
If the ihsctp process was not already running, no System action
action is required. The topology server program ends.
If the ihsctp process is running, contact IBM Software
IHS5974I Processing completed for this Notify the system programmer.
command. Requested processes
stopping. System programmer response
Run the 'tserver dbtransfer' utility, and restart the
Explanation topology server.
Each of the processes that you requested to stop have
IHS5982I Record Count: count Bytes Used:
been signaled. These processes are stopping, although
bytes Average Record Size: size
it might take several minutes to complete.
Explanation
Displays data relevant to the Event Enablement cache.

Message Variables will be queued until the cache
request has completed.
count
The number of events in the cache.
Explanation
bytes
The number of bytes of data in the cache. The utility -c command was issued to clear the Event
Enablement cache. The cache is currently in use. The
size
request to clear the cache will be queued until the
The average size of an event contained in the
cache is free, at which time the cache will be cleared.
cache.
IHS5983I A request for cached data is
pending. The clear cache request
Chapter 15. Graphic Monitor Facility Host Subsystem
Method Error Messages
These messages are written to the RODM log when an error has occurred when executing a Graphic
Monitor Facility host subsystem (GMFHS) method. There is no online message help available for these
messages.
0001 Error in log message build request: Explanation
Incorrect message index (insert_1) A request has been made to build a message for the
RODM log but the message skeleton contains a
Explanation variable substitution number of zero or greater than
A request has been made to build a message for the nine.
RODM log but the message index provided is less than Message Variables
1 or greater than the maximum index.
insert_1
Message Variables variable substitution.
insert_1
Message index value. System action
This message is issued to the log and processing
System action continues.
There is a programming error or an error in the string
System programmer response table where the messages are defined. Contact IBM
There is a programming error or incompatibility Software Support for assistance.
between program component levels. Contact IBM 0004 Error in log message build request
Software Support for assistance. processing: incorrect return code
0002 Error in log message build request: (insert_1) from DUIFLSVS
Incorrect argument or argument
list Explanation
A request has been made to build a message for the
Explanation RODM log. The function which substitutes variable
A request has been made to build a message for the information into the message skeleton completed with
RODM log but the parameters provided to the function an unknown return value.
which builds the message are incorrect. Message Variables
insert_1
System action Message index value.
System programmer response continues.
There is a programming error. Contact IBM Software
0003 Error in log message build request: There is a programming error. Contact IBM Software
Incorrect argument number in Support for assistance.
message skeleton: insert_1
0016 Important message:

Explanation search structure follows if given a
good pointer.
Specifies that this log entry is documenting a condition
for which eventual action is required. 0023 The method attempted to obtain
the MSA but has a dependency on
System action GMFHS being active and GMFHS is
not active.
continues. 0025 Important message:
Correct the error situation and retry the operation. GMFHS attempted to connect to a RODM that was
already connected to another GMFHS.
0017 Internal error:
System action
Explanation
The message is logged and the method ends.
Specifies that this log entry is documenting an error
condition which requires immediate attention. System programmer response
System action Ensure that the name of the RODM application as

specified in the GMFHS initialization member
This message is issued to the log and processing (DUIGINIT) is correct. No more than one GMFHS
continues. application is allowed to connect to RODM.
0026 Important message:
Correct the error situation and retry the operation. Explanation
0020 Internal error: Storage overlay An attempt was made to connect a GMFHS application
detected. First 64 and last 64 to a RODM that has an incompatible version of the
bytes follow (or dumped if less GMFHS methods installed.
than 128 bytes).
System action
Explanation
The message is logged and the method ends.
The GMFHS storage macros pad all storage requests
with recognizable values. When freeing storage, if the System programmer response
values have changed, we have a storage overlay. The
module and line number where the storage was Ensure that the name of the RODM application as
allocated are contained within the storage header, specified in the GMFHS initialization member
assuming the storage header was not affected by the (DUIGINIT) is correct. The version of the GMFHS
overlay. application must be the same as the version of the
GMFHS methods installed in RODM.
0021 Internal error: Storage not
deallocated. First 64 bytes of each 0101 malloc() failed
buffer will be dumped.
Explanation
Explanation Unable to allocate memory
The storage header will contain the module and line
number that allocated the storage. Use this System action
information to determine who sh have freed the
storage. Note that when this error was detected, the This message is issued to the log and caused the
storage was deallocated. abend.
0022 Tried doing a locate on an Indexed System programmer response

list field (insert1) for more than
one value – searches with only one There is a system error. Contact IBM Software Support
value are allowed. A dump of the for assistance.

0103 RODM data is longer than View 0109 Method Response Block Overflow
Manager allows. Truncation will RODM Error
occur. The RODM data is:
Explanation
Explanation
RODM reported that a response block was too small to
The data specified in RODM for this field is longer than satisfy a request. RODM did not report the proper size
view manager allows. The RODM data is displayed to required.
help you identify the problem.
System action
System action
This message is issued to the log and the current
The message is logged and processing continues. request ends.

Determine if this is a problem. Certain data can be There is a system error. Contact IBM Software Support
truncated with no significant effect. On the other hand, for assistance.
resource names and other data might cause problems.
0111 RODM data: VIEW NAME is longer
Correct the RODM load statements.
than View Manager allows. The
0106 Unable to find the Object ID of maximum length of VIEW NAME is
SNA resource 32. The VIEW NAME will be
omitted from VIEW LIST. The
Explanation RODM data is:
An SNA resource is specified on the request but

Explanation
GMFHS is unable to locate the resource in RODM.
The view name in RODM for this field is longer than
System action view manager allows. The RODM data is displayed to
help you identify the problem.
The message is logged and processing continues.
System action
If the resource does exist, determine the cause of the
error from the RODM log and correct it. Incomplete or
erroneous RODM definitions are probable causes.
Determine if this is a problem. Certain data can be
0107 A variable length View Manager truncated with no significant effect. On the other hand,
field does not have the length field resource names and other data can cause problems.
set. The data cannot be read. The Correct the RODM load statements.
RODM data is:
0114 Subscribe for Delete of objectid:
Explanation insert_1 failed. Requesting
Graphic Data Server: insert_2.
View manager is attempting to read a variable length
field but has not set the maximum length it can read.
Explanation
The data cannot be read because storage overwrite
might occur. An attempt to add an Object Deletion subscription to a
resource failed.
This message is issued to the log and processing of insert_1
this request ends. RODM ObjectID.
insert_2
System programmer response Graphic Data Server LU name.
There is a system error. Contact IBM Software Support
for assistance.
Chapter 15. Graphic Monitor Facility Host Subsystem Method Error Messages 857
The message is logged and processing continues. Because of this error, a view building method is unable
to install notification subscriptions.
Determine from the information in the RODM log insert_1
whether an error has occurred. If so, either correct the View name.
error or contact IBM Software Support for assistance.
insert_2
0116 A notification queue name is not Graphic Data Server LU name.
available for view: insert_1 insert_3
requested by Graphic Data Server: Return code number.
insert_2.
insert_4
Return code description.
Explanation
insert_5
A notification queue was not provided to the view RODM object class.
building method for use with topology subscriptions.
insert_1 Building of the view ends.
View name.
insert_2 System programmer response
Graphic Data Server LU name. This is a system error. Contact IBM Software Support
for assistance.
System action
0128 Unrecognized View type in request
Building of the view ends. block insert_1

This is a system error. Contact IBM Software Support View Notification Granularity initialization method
for assistance. DUIFVNGI does not recognize an input view_type.
0120 Unable to send output response to Message Variables
caller
insert_1
View Type.
Explanation
An attempt to return the response block failed. System action
Processing of this request is ended.
GMFHS VIEWMGR ends.
System action
The message is logged and processing of this request
is ended. This is a system error. Contact IBM Software Support
for assistance.
System programmer response 0132 The error: insert_1 - insert_2
occurred while processing
ClassID: insert_3 / ClassName:
for assistance.
insert_4 for view: insert_5
0127 During installation of view requested by Graphic Data Server:
notification subscriptions for view: insert_6.
insert_1 requested by Graphic
Data Server: insert_2, error Explanation
insert_3 - insert_4, was detected
during insert_5 processing. This message displays the class information that
caused a View Notification Granularity error.
Message Variables

insert_1 System action
Return code number.
GMFHS VIEWMGR ends, and an error is returned to
insert_2 Graphic Data Server.
Return code description.
ClassID.
This is a system error. Contact IBM Software Support
insert_4 for assistance.
ClassName.
0135 RODM return code insert_1, reason
insert_5
code insert_2, was received while
View name.
installing notification method
insert_6 DUIFVNGN on ClassID: insert_3 /
Graphic Data Server LU name. ClassName: insert_4, FieldID:
insert_5 / FieldName: insert_6, for
System action view: insert_7 requested by
Graphic Data Server: insert_8.
GMFHS VIEWMGR ends, and an error is returned to
Graphic Data Server.
Explanation
System programmer response This message displays the RODM return and reason
codes that were received while installing a notification
This is a system error. Contact IBM Software Support method at the class level.
for assistance.
Message Variables
0133 The error: insert_1 - insert_2
occurred while processing insert_1
ClassID: insert_3 / ClassName: Return code
insert_4 FieldID: insert_5 / insert_2
FieldName: insert_6, for view: Reason code
insert_7 requested by Graphic
insert_3
Data Server: insert_8.
ClassID
insert_4
Explanation
ClassName
This message displays the class and field information insert_5
that caused a View Notification Granularity error. FieldID
Message Variables insert_6
insert_1 FieldName
Return code number. insert_7
insert_2 View name
Return code description. insert_8
insert_3 Graphic Data Server LU name
ClassID.
ClassName. View building ends, and an error is returned to Graphic
insert_5 Data Server.
FieldID.
FieldName. Use the Data Model Reference to get an explanation
insert_7 for this return/reason code combination. Also check
View name. prior log entries associated with this class, field, or
view. If unable to solve this problem, contact IBM
insert_8
Graphic Data Server LU name.
0136 RODM return code insert_1, reason
code insert_2 was received while
installing notification method Explanation
DUIFVNGN on ClassID: insert_3 /
This message is issued by View Notification method
ClassName: insert_4, ObjectID:
DUIFVNGI if it is unable to install a notification
insert_5 / ObjectName: insert_6,
method.
FieldID: insert_7 FieldName:
insert_8 for view: insert_9. Message Variables
insert_1
Explanation Return code
This message displays the RODM return and reason insert_2
codes that were received while installing a notification Reason code
method on an object. insert_3
Message Variables ClassID
insert_1
Return code System action
insert_2 GMFHS VIEWMGR ends.

Reason code
ClassID Use the Data Model Reference to get an explanation
insert_4 for this return/reason code combination. Also check
ClassName prior log entries associated with this class or field. If
unable to solve this problem, contact IBM Software
insert_5
ObjectID
insert_6 0141 Field not found
ObjectName
insert_7 Explanation
FieldID A required RODM field cannot be found.
insert_8
FieldName System action
insert_9 The message is logged and processing continues.
View name. Subsequent processing might determine that the
current request cannot be satisfied. If so, the current
System action request ends and another message issued.
View building ends, and an error is returned to Graphic
Data Server. System programmer response
If processing continues and the desired results are
System programmer response obtained, no action is required. Otherwise, determine
Use the Data Model Reference to get an explanation which field is missing and take corrective action.
for this return/reason code combination. Also check 0142 Query View Parent Class Error
prior log entries associated with this class, field, or
view. If unable to solve this problem, contact IBM
Explanation
There was an error while querying the View Parent
0137 RODM return code insert_1, reason Class.
code insert_1 was received while
System action
DUIFVNGN on the
MyObjectChildren of ClassID: The message is logged and processing continues.
insert_3. Subsequent processing might determine that the
request ends and another message issued.

If processing continues and the desired results are The message is logged and processing continues.
obtained, no action is required. Otherwise, determine Subsequent processing might determine that the
the cause of the error and take corrective action. current request cannot be satisfied. If so, the current
Incomplete or erroneous RODM definitions are request ends and another message issued.
probable causes.
0143 Query View Info Ref Class Error System programmer response
Explanation obtained, no action is required. Otherwise, determine
the cause of the error and take corrective action.
There was an error while querying the View Info Ref Incomplete or erroneous RODM definitions are
Class. probable causes.
System action 0146 Query PS Global Parms Object

Class Error
Subsequent processing might determine that the
Explanation
request ends and another message issued. There was an error while querying the PS Global Parms
Object Class.
System action
obtained, no action is required. Otherwise, determine The message is logged and processing continues.
the cause of the error and take corrective action. Subsequent processing might determine that the
Incomplete or erroneous RODM definitions are current request cannot be satisfied. If so, the current
probable causes. request ends and another message issued.
0144 Query View Info Object Class Error
Explanation If processing continues and the desired results are
obtained, no action is required. Otherwise, determine
There was an error while querying the View Info Object the cause of the error and take corrective action.
Class. Incomplete or erroneous RODM definitions are
probable causes.
System action
0147 RODM MAPI Call Error, RC/RS :
Explanation
request ends and another message issued. A non-zero return or reason code was returned from
the RODM method application program interface
System programmer response (MAPI) call.

System action
the cause of the error and take corrective action. The message is logged and processing continues.
Incomplete or erroneous RODM definitions are Subsequent processing might determine that the
probable causes. current request cannot be satisfied. If so, the current
0145 Query View Layout Parms Object
Class Error
Explanation If processing continues and the desired results are
There was an error while querying the View Layout the cause of the error, based on the return code and
Parms Object Class. reason code, and take corrective action.
0148 Return/Reason code set error
The method was unable to set the return and reason The message is logged and processing continues.
code.
0150 The view type insert_1 is not System programmer response
recognized. Determine if this is a problem. Certain data can be
truncated with no significant effect. On the other hand,
Explanation resource names and other data might cause problems.
View Notification granularity does not recognize the
input view type. 0156 Unsubscribe for Delete of
objectID: insert_1 failed.
Message Variables
Requesting Graphic Data Server is
insert_1 insert_2.
View type.
Explanation
System action
An attempt to remove an Object Deletion subscription
Building of the view ends. from a resource failed.
Message Variables
insert_1
This is a system error. Contact IBM Software Support ObjectID.
for assistance.
insert_2
0153 Query Display Resource Type error Graphic Data Server LU name.

There was an error while querying the Displayable This message is logged and processing continues.
Resource Type object.
System action
Determine why unsubscribe failed from the data in the
The message is logged and processing continues. RODM log. Correct the problem or contact IBM
Subsequent processing might determine that the Software Support for assistance.
0157 Duplicate Layout Parm Objects
Explanation
There are two Layout Parm objects located for the
same resource.
Incomplete or erroneous RODM definitions are System action
probable causes. The message is logged and processing continues.
0154 Annotation field on the view Subsequent processing might determine that the
named insert_1 is too long and will current request cannot be satisfied. If so, the current
be truncated request ends and another message issued.
The data specified in RODM for this field is longer than If processing continues and the desired results are
view manager allows. The RODM data is displayed to obtained, no action is required. Otherwise, determine
help you identify the problem. the cause of the error and take corrective action.
Incomplete or erroneous RODM definitions are
Message Variables probable causes.
insert_1 0158 RODM data: View Name is the
View Name. same as another View Name with

different case. This View Name no error is found, contact IBM Software Support for
will be omitted from the View List. assistance.
The RODM data is: insert_1.
0160 Mismatch datatype: actual
Explanation
Explanation
The View Name in RODM for the MyName field of this
The data type expected from the RODM query does not
view object is the same as a View Name for another
match the actual data type received.
view object of the same View Class, only different
case. Although RODM allows the same name to be
used with different case, VIEWMGR does not. The System action
RODM data is displayed to help you identify the The message is logged and processing continues.
problem. Subsequent processing might determine that the
Message Variables current request cannot be satisfied. If so, the current
insert_1
RODM data.
System action If processing continues and the desired results are

This message is logged and processing continues. the cause of the error and take corrective action.
System programmer response probable causes.
Ensure all MyNames of view object of the same class 0161 Mismatch datatype: expected
are unique regardless of case. Then correct the RODM
load statements.
Explanation
0159 During construction of view: The data type expected from the RODM query does not
insert_1, RODM return code match the data type received.
insert_2, reason code insert_3,
was received during query of
System action
View_Layout_Parameters object
with ObjectID: insert_4. The message is logged and processing continues.
Explanation current request cannot be satisfied. If so, the current
Query of View_Layout_Parameters object failed.
insert_1 If processing continues and the desired results are
View Name. obtained, no action is required. Otherwise, determine
insert_2 the cause of the error and take corrective action.
RODM return code. Incomplete or erroneous RODM definitions are
probable causes.
insert_3
RODM reason code. 0162 Error obtaining View Table
insert_4
ObjectID. Explanation
The RODM method is not able to obtain the View Table
System action necessary for view building.
This message is logged and the view build ends.
System action
System programmer response The message is logged and processing ends.
Check the DetailLayoutParmListForSelectedResource
attribute on the resource associated with this view. If
If the problem is not corrected by subsequent retries This message displays the RODM return and reason
of the view request, GMFHS must be recycled. codes that were received while installing a notification
method.
0163 Error obtaining storage
Message Variables
Explanation insert_1
The RODM method encountered a storage failure while RODM return code.
building a view or view update. insert_2
RODM reason code.
System action insert_3
ClassID.
The message is logged and processing ends.
insert_4
System programmer response FieldID.
If the problem is not corrected by subsequent retries System action

of the view request, storage must be added or freed in
the RODM address space. Notification method is not installed, processing
continues.
0164 Error getting access to the Method
System Area
Explanation An explanation of the return and reason code values

can be found in the IBM Z NetView Resource Object
The RODM method cannot get access to the Method Data Manager and GMFHS Programmer's Guide. Also
System Area. check prior log entries associated with this class or
field. These can help to identify the source of the
System action problem.
The message is logged and processing ends. 0167 RODM return codeinsert_1, reason
codeinsert_2was received when
System programmer response performing a RODM query,
function ID = insert_3.
If the problem is not corrected by subsequent retries
of the request, GMFHS must be recycled.
Explanation
0165 Error sending notification to IPC
This message displays the RODM return and reason
notification queue
codes that were received when a method attempted a
RODM query.
Explanation
Message Variables
A method was unable to send a notification to the IPC
notification queue DUIFI000. insert_1
RODM return code.
RODM reason code.
insert_3
Function ID (class and field) of attempted query.
Examine the RODM log for any MAPI failures System action
proceeding this message.
The method ends.
0166 RODM return codeinsert_1, reason
codeinsert_2was received while System programmer response
DUIFVNOT on ClassID:insert_3, For an explanation of the return and reason code
FieldID: insert_4. values, see the IBM Z NetView Resource Object Data
Manager and GMFHS Programmer's Guide. Also check

prior log entries associated with this method. These System programmer response
can help to identify the source of the problem.
0168 Rule insert_1not recognized by the
0171 New value provided to the change
DUIFVNOT notification method
method is not of the appropriate
data type for the insert_1field of
Explanation object insert_2. The type supplied
The rule used in the long-lived parameters of a is insert_3 and the expected type
notification subscription is not valid. is insert_4.
Message Variables
Explanation
insert_1
The change method expects a certain data type for the
Rule number.
new value but the value provided is of a different type.
Method DUIFVNOT ends. insert_1

Field to be changed.
System programmer response insert_2
Object to which field belongs.
Use the IBM Z NetView Resource Object Data Manager
and GMFHS Programmer's Guide for a list of the valid insert_3
rules used for view notification subscriptions. Incorrect data type.
insert_4
0169 Unable to get ALET Expected data type.

Internal error occurred while attempting to obtain This message is issued to the log and the method
cross memory storage. ends.

A message is written to the log indicating the return Check to be sure that the method is installed on the
and reason code values and the RODM method ends. correct field and class. Correct this if necessary.
0170 RODM data: ExceptionViewName 0172 New value provided to the change
is longer than 8 characters. method is not of the appropriate
ExceptionViewName is an length for the insert_1field of
asttribute for objects under the object insert_2. Length supplied is
ExceptionViewName will be insert_3 and the expected length
omitted from VIEW LIST. The is insert_4.
ExceptionViewName is: insert_1
Explanation
Explanation
The change method expects a new data value of a
The ExceptionViewName in RODM is longer than eight specific length but the value provided has a different
characters. The RODM data is displayed to help the length.
user identify the problem.
Message Variables
Message Variables
insert_1
insert_1 Field to be changed.
ExceptionViewName value.
insert_2
System action
insert_3
The message is logged and processing continues. Incorrect length.
insert_4
Expected length.
This message is issued to the log and the method This message is issued to the log and the method
ends. ends.

Check to be sure that the method is installed on the Check the RODM log to ensure an internal error
correct field and class. Correct this if necessary. condition in RODM has not occurred. Correct this if
necessary.
0173 The ExceptionViewList field
cannot be located for the resource 0176 RODM daata: ExceptionViewName
object for which the change is is longer than eight characters.
intended. The view name of the object for
this invalid ExceptionViewName
Explanation will be omitted from the VIEW
LIST. The omitted view name from
The change method expects the field for which the the VIEW LIST is: insert_1.
change method has been triggered to exist.
Explanation
System action
The ExceptionViewName in RODM is longer than eight
This message is issued to the log and the method characters. The RODM data is displayed to help the
ends. user identify the problem.
Message Variables
insert_1
Check the RODM log to ensure an internal error
Name of view that was omitted from the VIEW
condition in RODM has not occurred. Correct this if
LIST.
necessary.
0174 The ResourceTraits field cannot be System action
located for the resource object fo
which the change is intended. This message is issued to the log and processing
continues.
Explanation
The change method expects the field for which the
change method has been triggered to exist. Correct the RODM load statements.
0177 RODM daata: Error querying
System action ExceptionViewName field for
exception view name:insert_1.
This message is issued to the log and the method
ends.
Explanation
System programmer response While processing the list of exception views, the host
cannot query the ExceptionViewName field.
Check the RODM log to ensure an internal error
condition in RODM has not occurred. Correct this if Message Variables
necessary.
insert_1
0175 The change method is unable to Name of view.
locate the ObjectID for the
resource for which the change is System action
intended.
This message is issued to the log and processing of the
graphical list of views is stopped.
Explanation
The change method expects the ObjectID for which System programmer response
the method has been triggered to exist.
Ensure the ExceptionViewName field for this view is
defined correctly in RODM.

0179 RODM data: Error locating 0183 RODM data: Error locating
ExceptionViewList value:insert_1. ResourceTraits for view: insert_1.
The ExceptionViewList in RODM cannot be located The ResourceTraits field in RODM cannot be located
with the LMAH_Locate routine. with the LMAH_Locate routine.
insert_1 insert_1
ExceptionViewList value. Name of view.

This message is logged and processing continues. The requested view can not be built. The message is
logged and processing continues.
Verify any changes to the data model.
0180 Invalid Self Defining
EKG_CHAR_VAR 0185 Invalid Self Defining field Type
The Self Defining EKG_CHAR_VAR field is not The SelfDefining field is not formatted properly and
formatted properly. cannot be processed.

The message is logged and processing continues. The message is logged and processing continues.
Subsequent processing might determine that the Subsequent processing might determine that the
current request cannot be satisfied. If so, the current current request cannot be satisfied. If so, the current
request ends and another message issued. request ends and another message issued.

If processing continues and the desired results are If processing continues and the desired results are
obtained, no action is required. Otherwise, determine obtained, no action is required. Otherwise, determine
the cause of the error and take corrective action. the cause of the error and take corrective action.
0181 Unable to process all Self Defining 0186 Unrecognized RODM Data Type
entries
Explanation
Explanation
The RODM data type returned on the query cannot be
The SelfDefining field is not formatted properly and recognized and cannot be processed.
cannot be processed.
System action
System action
The message is logged and processing continues. Subsequent processing might determine that the
Subsequent processing might determine that the current request cannot be satisfied. If so, the current
current request cannot be satisfied. If so, the current request ends and another message issued.
If processing continues and the desired results are obtained, no action is required. Otherwise, determine
obtained, no action is required. Otherwise, determine the cause of the error and take corrective action.
0189 Error retrieving Object Information System action
The message is logged and processing for this view
Explanation object ends.
There was an error while querying the required
information for an object. System programmer response
Look at the description of the ExceptionViewName
System action field in the IBM Z NetView Resource Object Data
The message is logged and processing ends. Manager and GMFHS Programmer's Guide and
determine which fields you specified incorrectly.
Specifically, look for a bit that was set that is
System programmer response designated as a reserved bit.
Use the RODM log to determine the cause of the error
0192 ExceptionViewFilter is invalid —
and take corrective action. Incomplete or erroneous
RC=2. RODM data: Error with
RODM definitions are probable causes.
ExceptionViewFilter: insert_1
0190 Attempted to link a shadow object
to a DRT object but resource name Explanation
insert_1 of the shadow object is
invalid. The link operation is not One or more UserStatus values in the
performed. The resource name ExceptionViewFilter were given an incorrect value of 3.
format for shadow objects is Valid values are 0, 1 or 2.
NETWORK.RESOURCE where Message Variables
NETWORK can be 0–8 characters
and RESOURCE can be 1–8 insert_1
characters. NETWORK and ExceptionViewFilter value.
RESOURCE must adhere to the
same character restrictions as System action
VTAM network and resource The message is logged and processing for this view
names. object ends.

The specified resource name is not of the proper Look at the description of the ExceptionViewName
format. field in the IBM Z NetView Resource Object Data
Message Variables Manager and GMFHS Programmer's Guide and
determine which fields you specified incorrectly.
insert_1 Specifically, you have set one or more UserStatus
Incorrect resource name of the shadow object. values as 3, instead of 0, 1, or 2.
System action 0193 ExceptionViewFilter is invalid —

RC=3. RODM data: Error with
The message is logged. The link is not performed. ExceptionViewFilter: insert_1

The RODM definitions must be updated to properly A bit was incorrectly set in the ExceptionViewFilter. In
specify the resource name. addition, one or more UserStatus values in the
0191 ExceptionViewFilter is incorrect — ExceptionViewFilter were given an incorrect value of 3.
RC=1. RODM data: Error with Valid values are 0, 1, or 2.
ExceptionViewFilter: Message Variables
insert_1
Explanation ExceptionViewFilter value.
A bit was incorrectly set in the ExceptionViewFilter.

The message is logged and processing for this view A required RootNode attribute is not specified for this
object ends. view.

Look at the description of the ExceptionViewName This message is issued to the log and construction of
field in the IBM Z NetView Resource Object Data the view ends.
Manager and GMFHS Programmer's Guide and
determine which fields you specified incorrectly. System programmer response
Specifically, look for a bit that was set that is
designated as a reserved bit. In addition, look for This message is issued when LayoutType = 8 and a
where you have set one or more UserStatus values as RootNode has not been specified. See the description
3, instead of 0, 1, or 2. of the connectivity tree layout view in the IBM Z
0195 RODM data: Error locating Programmer's Guide. If this LayoutType is used, a
ResourceTraits value: insert_1 RootNode must be specified.
0199 Object name insert_1 under Class
Explanation
name insert_2 did not have a
The ResourceTraits field in RODM cannot be located DisplayResourceType or a
with the LMAH_Locate routine. The error occurred ViewInfoObject.
during build of an exception view, specifically while
filtering UserStatus values. Explanation
insert_1 The object will be deleted from the view. View
ResourceTraits value. processing will continue.
insert_1
System action
Name of object.
The message is logged and processing continues. insert_2
Name of class.
Verify any changes to the data model. System action
0196 RODM data: Error locating The message is logged and processing continues.
ResourceTraits value: insert_1 0200 Alpha View Header is missing.
The ResourceTraits field in RODM cannot be located The Alpha View Header was not found.
with the LMAH_Locate routine. The error occurred
during build of an exception view, specifically while 0202 Object name insert_1 under Class
filtering UserStatus values. name insert_2 did not have a
ViewInfoObject.
insert_1
ResourceTraits value.
Explanation
System action The object will be deleted from the view. View
processing will continue.
insert_1
System programmer response Name of object.
insert_2
Name of class.
0197 Required RootNode not specified
for view: viewname System action
0204 RODM data: ExceptionViewName Explanation
is not unique. ExceptionViewName The change method expects one data type for the new
is an attribute for objects under value but the value provided has a different type.
the Exception_View_Class. The
view name of the object for this Message Variables
duplicate ExceptionViewName will insert_1
be omitted from VIEW LIST. The Field name.
ExceptionViewName is: insert_1.
insert_2
Class name.
Explanation
insert_3
The ExceptionViewName in RODM is not unique. The Incorrect data type.
RODM data is displayed to help the user identify the
problem. insert_4
Expected data type.
insert_1
ExceptionViewName value. System action
System action This message is issued to the log and the method
ends.
method is invalid for the
insert_1field of cbjectinsert_2. The
Correct the RODM load statements. value supplied is insert_3 and the
length of the value is insert_4. The
0205 RODM data: ExceptionViewName value must be changed to be less
is not unique. ExceptionViewName than or equal to 8 characters. The
is an attribute for objects under change method is terminated.
the Exception_View_Class. The
view name of the object for this
duplicate ExceptionViewName will Explanation
be omitted from VIEW LIST. The The change method expects the value to be less than
ExceptionViewName is: insert_1. or equal to 8 characters.
Message Variables
Explanation
insert_1
The ExceptionViewName in RODM is not unique. The Field to be changed.
RODM data is displayed to help the user identify the
problem. insert_2
insert_1
insert_3
Name of view.
Incorrect data value.

Expected data length.
System action
Correct the RODM load statements. ends.
method is not of the appropriate System programmer response
data type for the insert_1field of Change the value to be less than or equal to 8
class insert_2. The type supplied is characters.
insert_3 and the expected type is
insert_4. 0211 New value provided to the change
method is invalid for the
insert_1field of class insert_2. The
value supplied is insert_3 and the

length is insert_4. The value must Explanation
be changed to be less than or
A VCMH_OBJ_INFOP pointer cannot be relocated.
equal to 8 characters.
System action
Explanation
This message is issued to the log and construction of
The change method expects the value to be less than
the view ends.
or equal to 8 characters.
insert_1 There is a system error. Contact IBM Software Support
Field name. for assistance.
insert_2
0235 Error encountered while
Class name.
processing view connectivity
insert_3
Incorrect data value. Explanation
insert_4
An error forced the end of the processing of the view
Incorrect data length.
connectivity.
System action
System action
The construction of the view ends.
ends.

An error was previously encountered during
Change the value to be less than or equal to 8
processing of view connectivity. Examine the RODM
characters.
log for the specific error.
0217 Error encountered querying
0236 Reset to default
field(s) in an attempt to send an
LinkCrossOptionValue View Name:
exception view update. Update
insert_1
will be ignored — see previous
message for details.
Explanation
Explanation The specified LinkCrossOptionValue is out of range. A
default value is used.
An exception view update cannot be processed
because of errors in RODM. See previous message for Message Variables
details and correct the problem.
insert_1
0219 Could not relocate Object Info View Name.
structure
System action
Explanation
The message is logged, the default is set, and
A VCMH_OBJ_INFOP pointer cannot be relocated. processing continues.

This message is issued to the log and construction of Set a valid LinkCrossOptionValue value.
the view ends.
0237 Reset to default BinPackingFlag
View Name: insert_1
There is a system error. Contact IBM Software Support Explanation
for assistance.
The specified BinPackingFlag is out of range. A default
0233 C not relocate Object Info value is used.
structure
insert_1 The specified LayoutType is out of range. A default
View Name. value is used.
Message Variables
System action
insert_1
The message is logged, the default is set, and View Name.
System action
Set a valid BinPackingFlag value. processing continues.
0238 Reset to default LayoutOrientation
View Name: insert_1 System programmer response
Set a valid LayoutType value.
Explanation
The specified LayoutOrientation is out of range. A SymbolRadiusValue View Name:
default value is used. insert_1
Message Variables
Explanation
insert_1
View Name. The specified SymbolRadiusValue is out of range. A
default value is used.
The message is logged, the default is set, and insert_1
processing continues. View Name.

Set a valid LayoutOrientation value. The message is logged, the default is set, and
0239 Reset to default processing continues.
DefaultRowSpacing View Name:
Set a valid SymbolRadiusValue value.
Explanation
The specified DefaultRowSpacing is out of range. A EllipseAspectRatioHeight View
default value is used. Name: insert_1
Message Variables
Explanation
insert_1
View Name. The specified EllipseAspectRatioHeight is out of range.
A default is used.
The message is logged, the default is set, and insert_1
processing continues. View Name.

Set a valid DefaultRowSpacing value. The message is logged, the default is set, and
0241 Reset to default LayoutType View processing continues.
Name: insert_1
Set a valid EllipseAspectRatioHeight.

0246 Reset to default System action
EllipseAspectRatioWidth View This message is issued to the log and processing
Name: insert_1 continues.

The specified EllipseAspectRatioWidth is out of range.
Set a valid HierarchicalPriority value.
A default value is used.
0255 The insert_1field on object insert2
Message Variables
is incorrect. See the RODM and
insert_1 GMFHS Programming Guide for a
View Name. description of the field and its
expected content.
System action
Explanation
processing continues. The method has encountered an incorrect value in a
field. Another message sh follow indicating if the
System programmer response method can continue.
Set a valid EllipseAspectRatioWidth. Message Variables
0247 Invalid LayoutSequence specified insert_1

View Name: insert_1 Field Name.
insert_2
Explanation Object to which field belongs.
The specified LayoutSequence is out of range.

System action
Message Variables
This message is issued to the log and and processing
insert_1 continues.
View Name.
System action
Determine the cause of the incorrect field value, and
The message is logged, and the current request ends. correct if necessary.
0263 Unable to resolve specification of
System programmer response LINK as Root-Node
Set a valid LayoutSequence value.
Explanation
0248 Invalid HierarchicalPriority View
Name: insert_1 A LINK is specified as the Root-Node and there is not a
NULL endpoint on the LINK.
Explanation
System action
The specified HierarchicalPriority is out of range.
Message Variables
insert_1 current request cannot be satisfied. If so, the current
Field Name request ends and another message issued.
insert_2
Object to which field belongs. System programmer response
Message Variables If processing continues and the desired results are
obtained, no action is required. Otherwise, specify the
insert_1 LINK with at least one NULL endpoint or specify a
View Name. NODE as the Root-Node.
0264 Redefine View with node object as
Root-Node
A LINK is specified as the Root-Node and there is not a The NULL Object cannot be located. A NULL Object is
NULL endpoint on the LINK. required for view processing.

The message is logged and processing continues. The message is logged and processing continues.
Subsequent processing might determine that the Subsequent processing might determine that the
current request cannot be satisfied. If so, the current current request cannot be satisfied. If so, the current
request ends and another message issued. request ends and another message issued.

If processing continues and the desired results are If processing continues and the desired results are
obtained, no action is required. Otherwise, specify the obtained, no action is required. Otherwise, determine
LINK with at least one NULL endpoint or specify a the cause of the error and take corrective action.
NODE as the Root-Node. Incomplete or erroneous RODM definitions are
probable causes.
0265 NULL pointer to Object Info block
0270 Maximum number of nodes
Explanation exceeded
A NULL pointer is passed as a parameter to a function

Explanation
that requires an Object Info block.
The Node control blocks have all been used.
System action
System action
Subsequent processing might determine that the The message is logged and processing continues.
current request cannot be satisfied. If so, the current Subsequent processing might determine that the
request ends and another message issued. current request cannot be satisfied. If so, the current
obtained, no action is required. Otherwise, a RODM There is a system error. Contact IBM Software Support
definition error is a probable cause. for assistance.
0266 Error retrieving Object Link List 0271 Maximum number of links
exceeded
Explanation
Explanation
There was an error while retrieving an Object Link List.
The Link control blocks have all been used.
System action
System action
Subsequent processing might determine that the The message is logged and processing continues.
current request cannot be satisfied. If so, the current Subsequent processing might determine that the
request ends and another message issued. current request cannot be satisfied. If so, the current
obtained, no action is required. Otherwise, determine There is a system error. Contact IBM Software Support
the cause of the error and take corrective action. for assistance.
0275 Required attr, First|Second node
probable causes.
not set:: View Name: insert_1
0267 Failed to locate NULL Object

The required First and Second Node are not set. There was an error while querying the Aggregate
Object.
Message Variables
View Name.
System action
The message is logged and processing of this request request ends and another message issued.
ends.
Set the proper First and Second Node attributes. obtained, no action is required. Otherwise, determine
0276 Required attr, Bus node not set:: Incomplete or erroneous RODM definitions are
View Name: insert_1 probable causes.
Explanation 0279 Query Monitorable Object error
The required Bus Node is not set.

Explanation
Message Variables
There was an error while querying the Monitorable
insert_1 Object.
View Name.
System action
System action
The message is logged and processing of this request Subsequent processing might determine that the
ends. current request cannot be satisfied. If so, the current
Set the proper Bus Node attribute.
0277 Query Real Object error obtained, no action is required. Otherwise, determine
Explanation Incomplete or erroneous RODM definitions are
There was an error while querying the Real Object. probable causes.
0280 Query Displayable Object error
System action
The message is logged and processing continues. Explanation
Subsequent processing might determine that the There was an error while querying the Displayable
current request cannot be satisfied. If so, the current Object.
System action
If processing continues and the desired results are Subsequent processing might determine that the
obtained, no action is required. Otherwise, determine current request cannot be satisfied. If so, the current
the cause of the error and take corrective action. request ends and another message issued.
probable causes.
0278 Query Aggregate Object error If processing continues and the desired results are
Incomplete or erroneous RODM definitions are Explanation
probable causes.
There was an error while retrieving the PS Global
0288 Query DisplayResourceType Parms class.
children error
System action
Explanation
There was an error while querying the children of the
DisplayResourceType class. System programmer response
Determine the cause of the error and take corrective
System action action. Incomplete or erroneous RODM definitions are
The message is logged and processing continues. probable causes.
0300 Failed to find Fast Path View
object:: Object Name:insert_1
Explanation
The specified resource that represents the root object
for this view cannot be found.
the cause of the error and take corrective action. Message Variables
insert_1
probable causes.
Object Name.
0293 Failed to allocate response buffer
System action
Explanation The message is logged and construction of this view
Unable to allocate memory for the response block. ends.

This message is issued to the log and processing ends. If this view does not exist, no action is required. If the
view does exist, examine the RODM log for the cause
System programmer response of the error and take the appropriate corrective action.
There is a system error. Contact IBM Software Support 0301 Failed to find Network View
for assistance. object:: View Name: insert_1
0295 Failed to get response block to Explanation

send response
The specified object that represents this view cannot
Explanation be found.
Unable to allocate memory for the response block. Message Variables

insert_1
System action View Name.
This message is issued to the log and processing ends.
System action
System programmer response The message is logged and construction of this view
ends.
for assistance.
0298 PS Global Parms retrieval error
If this view does not exist, no action is required. If the
of the error and take the appropriate corrective action.

0304 No Aggregate Children for this insert_1
resource Name of view.

The specified resource does not have any Aggregate The message is logged and processing ends.
Children. The view is not created.
System action Determine the cause of the error and take corrective
The message is logged and construction of this view action. Incomplete or erroneous RODM definitions are
ends. probable causes.
0309 Failed to find View Layout Parm
If this view does not exist, no action is required. If the Explanation
A specific View Layout Parm Object cannot be found.
Also, you might have erroneous or incomplete RODM
definitions. System action
0305 Failed to find Fast Path View class The message is logged and processing ends.
There was an error while retrieving the Fast Path View Determine the cause of the error and take corrective
class. action. Incomplete or erroneous RODM definitions are
probable causes.
System action 0310 Failed to retrieve ContainsObjects
field
Explanation
The ContainsObjects field is empty or it does not exist.
The ContainsObjects field is required to build this
action. Incomplete or erroneous RODM definitions are
view.
probable causes.
0306 Failed to retrieve ViewInfoList System action
The message is logged and construction of the view
Explanation ends.
There was an error while retrieving the View Info List.
System action If the view does not exist, no action is required. If the
The message is logged and processing ends. view does exist, examine the RODM log for the cause
System programmer response Also, you might have incomplete or erroneous RODM
definitions.
action. Incomplete or erroneous RODM definitions are 0311 Failed to build View Info Object
probable causes. blocks
0307 Failed to retrieve ViewInfoObject Explanation

for view name insert1
There was an error while obtaining storage for the
Explanation View Info Object blocks.
A specific View Info Object cannot be found.

Message Variables
The message is logged and processing ends. insert_1
View Name.
System action
for assistance. The attempt to display the view is halted, and this
message is logged.
0312 Failed to find Display Resource
Type:: View Name: insert_1 Object
Name: insert_2 System programmer response
Check the RODM log for related messages and reduce
Explanation the resources in the view.
The Display Resource Type object cannot be found.
User response
Message Variables
Record the view that was requested and contact the
insert_1 system programmer.
View name.
0317 View insert1truncated due to
insert_2 ObjectSetCriteriaCount.
Object name.
Explanation
System action
The maximum number of objects allowed for this view
has been reached. Objects in excess of this count are
not included in this view.
Message Variables
action. Incomplete or erroneous RODM definitions are insert_1
probable causes. View Name.
0313 The seclected object is not System action

allowed as a root object in this
view type. The message is logged and processing continues.
The RootObjectAllowed field in RODM is set to X'00' If this truncation is undesirable, set the
for the selected object. ObjectSetCriteriaCount to a higher value.
0318 Unable to retrieve Unique
System action LayoutParmsObject
Processing ends for this view. Other views might be
built. Explanation
There are two or more Layout Parm Objects for the
System programmer response resource. Default layout parms are used.
If normal, ignore. Otherwise, change the value of
RootObjectAllowed in RODM for the selected object. System action
0316 View insert_1 cannot be displayed This message is issued to the log and processing
due to requiring too many Null continues.
nodes or links. The view is too
large and complex. System programmer response
Determine why there are multiple layout parms for the
Explanation resource. Erroneous RODM definitions are a probable
There is too much in the view to be able to effectively cause.
lay out and display it in the available space and time.

0319 View Definition Changing - 0328 There are no Network Views
Request Rejected defined
Your request to build the view was rejected. GMFHS is The user has not defined any network views to RODM.
unable to build the view because the view definition is
changing. The processing of this request ends. System action
System action
continues.
0333 Invalid resource name
ends.
(xxxxxxxx.yyyyyyyy)

Explanation
Determine the cause of the changing view definitions.
The specified resource name is not of the proper
Correct the problem or wait until the changes are
format.
complete and retry the request.
0320 Lock of View Objects failed - System action
Request Rejected
Explanation
GMFHS was unable to lock the objects required for this request ends and another message issued.
view. The processing of this request ends.
System action
Update the RODM definitions to properly specify the
The message is logged and processing of this request resource name.
ends.
0334 No SNA resources were found
Explanation
Use the RODM log to determine the cause of the lock
You have not defined SNA resources to RODM.
failure. Correct the problem or wait until the other
processes that have the locks complete processing
and retry the request. System action
0327 Failed to retrieve view data This message is issued to the log and processing
continues.
Explanation 0337 Root Object for this View not found
Required View Class fields cannot be retrieved for this
view. Explanation
The specified object that represents the root object for
System action this view cannot be found.
Subsequent processing might determine that the System action
current request cannot be satisfied. If so, the current The message is logged and construction of this view
request ends and another message issued. ends.

If processing continues and the desired results are If this view does not exist, no action is required. If the
obtained, no action is required. Otherwise, determine view does exist, examine the RODM log for the cause
the cause of the error and take corrective action. of the error and take the appropriate corrective action.
probable causes.
0343 Failed to find Configuration View Explanation
class There was an error attempting to send the response
for the Get Name Map request.
Explanation
There was an error while retrieving the Configuration System action
View class.
The message is logged and processing for this request
ends.
System action
The message is logged and processing ends. System programmer response
Use the RODM log to determine the cause of the error.
0383 Failed to find MDR view class
Explanation
probable causes.
There was an error while retrieving the Configuration
0351 This view has no objects because View class.
no relationships were specified.
System action
Explanation
The root object for this view did not have any
relationship fields specified. Therefore, no objects can
be found for the view. System programmer response
System action action. Incomplete or erroneous RODM definitions are
probable causes.
continues. It is reported that this view was not found. 0385 More Detail View for this resource
was not found
Explanation
Determine if there is an error and take corrective
action. Incomplete or erroneous RODM definitions are A More Detail View is not defined for this resource.
probable causes.
0362 Unable to locate specified root System action
resource The message is logged and construction of this view
ends.
Explanation
The specified resource that represents the root object System programmer response
for this view cannot be found. If this view does not exist, no action is required. If the
System action of the error and take the appropriate corrective action.
Also, incomplete or erroneous RODM definitions are
The message is logged and construction of this view probable causes.
ends.
0389 Failed to find Peer View object
Explanation
view does exist, examine the RODM log for the cause The view object that represents this view cannot be
of the error and take the appropriate corrective action. found.
0380 Get Name Map Response error
System action
The message is logged and construction of this view
ends.

System programmer response The query failed with return code
insert_2 and reason code insert_3
of the error and take the appropriate corrective action. Explanation
0391 Request type not recognized An error occurred while retrieving the value of the field
on the Configuration_Logical_Connectivity_View class
object.
Explanation
Message Variables
A View Request Type was specified that was out of
range. Processing of this request ends. insert_1
Field name.
Return code.
ends. insert_3
Reason code.
System action
for assistance. The message is logged and the processing of the view
request ends.
0393 Unable to query
Configuration_Peer_View_Class
Explanation Examine the RODM log for both RODM- and GMFHS-
generated error messages. Determine the cause of the
There was an error while retrieving the Configuration error and take corrective action. Issue the view
Peer View class. request again.
0396 Unable to query field insert_1 of
System action
the Configuration_Physical_
The message is logged and processing continues. Connectivity_View class object.
The query failed with return code
System programmer response insert_2 and reason code insert_3
Explanation
probable causes. An error occurred while retrieving the value of the field
on the Configuration_Physical_Connectivity_View
class object.
Network_View_Class
Message Variables
There was an error while retrieving the Network View Field name.
class. insert_2
Return code.
The message is logged and processing continues. Reason code.
Determine the cause of the error and take corrective The message is logged and the processing of the view
action. Incomplete or erroneous RODM definitions are request ends.
probable causes.
0395 Unable to query field insert_1 of
the Configuration_Logical_ Examine the RODM log for both RODM- and GMFHS-
Connectivity_View class object. generated error messages. Determine the cause of the
error and take corrective action. Issue the view insert_2
request again. Object name.
0397 This resource object insert_1 has
not defined a related Display System action
Resource Type object. The message is logged and the construction of the
view ends.
Explanation
An error occurred while retrieving the value of the field System programmer response
on the Configuration_Physical_Connectivity_View The resource identified by Object Name is an SNA
class object. resource that must have its name adjusted to conform
Message Variables to the SNA name format.
insert_1 0446 Unable to query

Object name. MDR_Logical_View_Class
The message is logged and the processing of the view There was an error while retrieving the More Detail
request ends. Logical View Class.
Examine the RODM log for both RODM- and GMFHS- The message is logged and processing continues.
generated error messages. Determine the Display
Resource Type object related to this resource object. System programmer response
Take corrective action and issue the view request
again.
0398 Unable to query a probable cause.
Configuration_Backbone_View_Cl
ass
MDR_Physical_View_Class
Explanation
Explanation
There was an error while retrieving the Configuration
There was an error while retrieving the More Detail
Backbone View class.
Logical View Class.
System action
System action

a probable cause.
a probable cause.
0403 SNA resource name length error.
0449 A required field on a RODM object
View Name: insert_1 Object Name:
was not present.
insert_2
Explanation
Explanation
A query failed against a field that sh have been
The SNA resource name exceeds the maximum
present.
allowed length or the name is incomplete.
Message Variables
insert_1
View name.

This message is issued to the log and the method This message is issued to the log and processing
ends. continues.

Determine why query failed from data in the RODM Correct the field's value so that this log entry is no
log. longer issued.
0502 New insert_1 field value of 0504 Method has been triggered at the
insert_2 provided to change object level which is not allowed.
method is not valid for this field This method must be triggered at
for object insert_3. the insert_1 class level.
The change method cannot change the field's value The method can only be triggered at the indicated
because the new value provided to the change method class level but it was triggered for an object of some
is not valid for this field in an object of this class. class.
insert_1 insert_1
Field to be changed. Correct class level.
insert_2
New value. System action
insert_3 The method ends.
Object name.
System action
Verify that the method is properly installed and is
This message is issued to the log and the method being triggered correctly.
ends.
method is not of the appropriate
data type for the insert_1 field of
Correct the field value and retry. the insert_2 class. The type
supplied is insert_3 and the
0503 The insert_1 value of object expected type is insert_4.
insert_2 is incorrect (insert_3). A
default value of insert_4 is
Explanation
assumed for it.
The method has received a new value for the field and
Explanation class indicated but this value does not have a correct
data type.
The method encountered an incorrect value in a field
and substituted a default value for it. Message Variables

Field to be changed.
insert_1
Field to be changed. insert_2
Class to which field belongs.
insert_2
Object name. insert_3
Data type supplied.
insert_3
Incorrect value. insert_4
Expected data type.
insert_4
Default value.
The method ends. You need to properly install the method and trigger it
as a named method only. If you install the method as a
System programmer response different method type, you sh remove this definition of
the method.
Verify that the method is installed on the correct field
and class and that the field is defined as having the 0508 Method has been triggered at the
expected data type. insert_1 class level which is not
allowed. This method must be
0506 Method has been triggered for the triggered at the instance level.
insert_1 field of object insert_2
instead of the insert_3 field as
Explanation
required.
The method is intended to be triggered for objects but
Explanation it was triggered for an object class.
The method has been associated with an object field Message Variables
other than that for which it is intended to be insert_1
associated. Method name.
Message Variables
System action
insert_1
Field for which method triggered. This message is issued to the log and the method is
insert_2 ended.
Object to which field belongs to.
insert_3
Field intended for the method. Ensure that all requests or actions that cause this
method to be triggered are done for an object.
System action
0509 Short lived input parameters are
This message is issued to the log and the method is missing or invalid for the
ended. invocation of this method for
insert_1. Parameter pointer =
System programmer response insert_2. If the pointer is not zero,
a dump of the parameters will
Remove the association of this method with the first follow.
field identified in the message.
0507 insert_1 method has been invoked Explanation
as other than a named method. A null, short-lived parameter pointer has been passed
to the method, or the parameters that are pointed to
Explanation contain incorrect data.
The indicated method sh be invoked as a named Message Variables
RODM method, but was invoked as a different type of
insert_1
method.
object for which method invoked.
insert_1 Parameter pointer.
Method name.
System action
System action This message is issued to the log and the method is
This message is issued to the log and the method is ended.
ended.
If the pointer is zero, make sure that the method is
triggered with the required parameters. If the pointer

is non-zero, check the dump of the parameters, which Explanation
will be in a subsequent log entry, to see what errors
The field value identified in the message was changed
are in the parameters.
successfully, but the reason code from the method
0510 Update of the DisplayStatus value application program interface (MAPI) field change
of insert_1 failed after the request was in the range which might indicate that a
SourceStatusUpdateTime value notification method installed on the field has failed.
was updated. Message Variables
Field name.
The SourceStatusUpdateTime field of the indicated
insert_2
object has been updated with the time provided in the
Object name.
method's short-lived parameters, but the subsequent
attempt to update the object's DisplayStatus field insert_3
value failed. RODM return code.

RODM reason code.
insert_1
Object for which DisplayStatus updated. System action
System action Processing related to the field change continues.
This message is issued to the log and the method is System programmer response
ended.
Check the RODM log entries preceding the one
System programmer response containing this message to determine what method
set the reason code. Correct the condition indicated by
To determine why the update of the DisplayStatus the reason code.
field value failed, check the RODM log entries prior to
the one containing this message. Correct the condition 0513 Unable to query the insert_1 field
causing the error and retry the request if necessary. of object insert_2.
0511 Function requires a non-null Explanation

pointer to an Object ID when
called from an object independent The object independent method cannot successfully
method but none was specified. query the specified field of the object identified in the
message.
The caller of this function did not provide an object insert_1
identifier and this identifier is required. Field name.
insert_2
System action Object name.
Contact IBM Software Support for assistance. This
message indicates a program logic error. System programmer response
0512 Apparent notification method Check the RODM log entries preceding the one
failure after an update of the containing this message for one indicating why the
insert_1 field of insert_2. Reason query failed. If necessary, correct the condition
code insert_3 (insert_4). causing this failure.
0514 Unable to execute a Query Object
Name RODM MAPI call for object
insert_1. Return code insert_2, Explanation
Reason code insert_3
The object-specific method can not successfully query
for the name of the field whose identifier is provided in
Explanation the message.
The object-specific method cannot successfully query Message Variables
the object name of the object identified in the
message. insert_1
Field name.
Message Variables
insert_2
insert_1 RODM return code.
insert_2 RODM reason code.
RODM return code.
RODM reason code.
continues.
System action
This message is issued to the log and processing System programmer response
continues.
Check the RODM log entries preceding this message
for one indicating why the query failed. If necessary,
System programmer response correct the condition causing this failure.
If necessary, correct the condition causing this failure. 0517 Unable to execute a Query Field
RODM return and reason codes in the message identify Name RODM MAPI call for field ID
the reason the query failed. insert_1 and object ID insert_2.
0515 Cannot convert insert_1 to a Return code insert_3, Reason code
subfield name. insert_4.
The number identified in the message was provided to The object-independent method cannot successfully
a function that, when provided with a valid subfield query for the name of the field whose identifier is
identifier, provides a text string containing the name provided in the message.
for that subfield type. The number, however, is not a Message Variables
valid subfield identifier.
insert_1
Message Variables Field name.
insert_1 insert_2
Object ID. Object name.
insert_3
System action RODM return code.
This message is issued to the log and processing insert_4
continues. RODM reason code.

Contact IBM Software Support for assistance. This This message is issued to the log and processing
message reports a condition caused by a program continues.
logic error.
0516 Unable to execute a Query Field System programmer response
Name RODM MAPI call for field ID Check the RODM log entries preceding this message
insert_1. Return code insert_2, for one indicating why the query failed. If necessary,
Reason code insert_3 correct the condition causing this failure.

0518 Unable to execute a Where Am I Explanation
RODM MAPI call. Return code A request to allocate a storage area of the size
insert_1, Reason code insert_2. indicated in the message was rejected.
The 'Where Am I' method application program insert_1

interface (MAPI) function did not successfully Number of bytes requested.
complete.
System action
Message Variables
insert_1 ends.
RODM return code.
RODM reason code.
Check for other log entries or console messages
indicating what storage type in RODM has been
System action
exhausted. It might be necessary to change the RODM
This message is issued to the log and the method customization parameters to provide a larger storage
ends. area for this type of storage.
0521 Lock objects request failed. Return
code insert_1, reason code
Correct the condition described by the RODM method insert_2. List of objects with
application program interface (MAPI) return and associated lock reason codes
reason codes provided in the message. follows.
0519 Unable to execute a Query
Explanation
Function Block Contents RODM
MAPI call. Return code insert_1, A method has requested that explicit object locks be
Reason code insert_2. obtained but RODM has rejected the request.
Message Variables
Explanation
insert_1
The 'Query Function Block Contents' method RODM return code.
application program interface (MAPI) function did not
successfully complete. insert_2
RODM reason code.
Message Variables
RODM return code. This message is issued to the log and the method
insert_2 ends.
RODM reason code.
System action
Correct the condition associated with the RODM
This message is issued to the log and the method method application program interface (MAPI) return
ends. and reason codes provided in the message. Also see
the subsequent log entries that provides the lock
System programmer response request reason code for each object in the request.
Correct the condition described by the RODM method 0522 insert_1 lock return code insert_2.
application program interface (MAPI) return and
reason codes provided in the message. Explanation
0520 Lock objects request failed due to This message follows messages 0521 and provides
function block memory allocation the name of an object and the lock reason code
failure. Requested insert_1 bytes. associated with the attempt to lock the specific object.
There will be as many of this message as there are insert_2
objects specified in the failing lock request. Attempted RODM reason code.
RODM return code.
insert_1
RODM reason code.
insert_2
lock return code.
System action
System action This message is issued to the log and an attempt is

made to set the method's return code to
This message is issued to the log and the method EKG_RC_ERROR (8) and its reason code to
ends. LMAH_RS_CANNOT_SET_CODES (45074).

See the response for message 0521 Correct the condition associated with the RODM
0523 Unlock objects request failed. method application program interface (MAPI) return
Return code insert_1, reason code and reason codes provided in the message.
insert_2. 0525 Output to log request failed due to
text buffer memory allocation
Explanation failure. Requested insert_1 bytes.
A method requested that all held object locks be
released and RODM rejected the request. Explanation
Message Variables A request to allocate a storage area of the size

indicated in the message was rejected.
insert_1
RODM return code. Message Variables
insert_2 insert_1
RODM reason code. Number of bytes requested.

This message is issued to the log and the method This message is issued to the log and processing
ends. continues. The log entry is not written.

Correct the condition associated with the RODM Check for other log entries or console messages
method application program interface (MAPI) return indicating what storage type in RODM has been
and reason codes provided in the message. exhausted. It might be necessary to change the RODM
customization parameters to provide a larger storage
0524 Error encountered attempting to area for this type of storage.
set the return and reason codes to
insert_1 and insert_2. Return code 0527 Failure to allocate insert_1 bytes
from attempt was insert_3; reason of memory updating the
code was insert_4. aggregation counters on insert_2.
A method has made a method application program A request to allocate a storage area of the size
interface (MAPI) request to set return and reason indicated in the message was rejected.
codes. This request has been rejected by RODM.
Message Variables
Message Variables
insert_1
insert_1 Number of bytes requested.
Attempted RODM return code.

insert_2 insert_2
Object name. Object 2 name.
insert_3
This message is issued to the log and the method insert_4
ends. RODM reason code.

Check for other log entries or console messages The method calling the link function might end
indicating what storage type in RODM has been depending upon the reason code and other
exhausted. It might be necessary to change the RODM circumstances. If the method does end, there are
customization parameters to provide a larger storage subsequent log entries to indicate why.
area for this type of storage.
0528 Incorrect parameter type flag
encountered in 'insert_1' at If the error caused the method to fail, see the
position insert_2. subsequent RODM log entry from the method and
follow the instructions indicated by that message.
Explanation 0530 Unlink request between 'insert_1'
A request was made to create the structure that and 'insert_2' failed. Return code
contains all the information required to query or insert_3, reason code insert_4.
change a RODM object field value. The request
contained an incorrect or misplaced parameter type Explanation
flag.
A request was made to unlink the indicated objects
Message Variables and fields. The request was rejected for the reason
insert_1 indicated by the RODM method application program
Parameter string. interface (MAPI) return and reason codes in the
message.
insert_2
Position. Message Variables
insert_1
System action Object 1 name.
This message is issued to the log. Processing insert_2
continues but a subsequent query or change request Object 2 name.
might fail. insert_3
RODM return code.
Contact IBM Software Support. This condition is RODM reason code.
caused by a program logic error.
System action
0529 Link request between 'insert_1'
and 'insert_2' failed. Return code The method calling the unlink function might end
insert_3, reason code insert_4. depending upon the reason code and other
circumstances. If the method does end, there will be
Explanation subsequent log entries indicating why.
A request was made to link the indicated objects and

fields. The request was rejected for the reason
indicated by the RODM method application program If the error caused the method to fail, see the
interface (MAPI) return and reason codes in the subsequent RODM log entry from the method and
message. perform the action indicated by that message.
Message Variables 0531 Field query failed for field insert_1
insert_1 of class insert_2, object insert_3.
Object 1 name.
Return code insert_4, reason code asynchronous execution failed.
insert_5. Return code insert_2, reason code
insert_3.
Explanation
Explanation
A method application program interface (MAPI)
request failed on a 'query a field' transaction. This message provides the method API return and
reason codes from a failed request to trigger an
Message Variables
object-independent method for asynchronous
insert_1 execution.
Field name.
Message Variables
insert_2
Class name. insert_1
Method name.
insert_3
RODM return code.
insert_4
RODM Return Code. insert_3
RODM reason code.
insert_5
RODM Reason Code.
System action
System action Subsequent log messages indicate the impact of this
failure.
Processing continues, but most methods end when
they observe this condition.
System programmer response Check the RODM documentation for the meaning of
the return and reason codes indicated. Take the
Correct the condition associated with the RODM corrective action as indicated.
method application program interface (MAPI) return
and reason codes provided in the message. 0535 Query unsuccessful due to
memory allocation failure -- size =
0532 EKGMAPI function insert_1 got insert_1 bytes.
reason code insert_2.
Explanation
Explanation
A request to allocate a storage area of the size
A method application program interface (MAPI) indicated in the message was rejected.
request failed with the return and reason codes
indicated. Message Variables

Number of bytes requested.
insert_1
RODM Return Code.
System action
insert_2
RODM Reason Code. This message is issued to the log and the method
ends.
System action
The method ends.
Check the RODM documentation for the meaning of customization parameters to provide a larger storage
the return and reason codes indicated. Take the area for this type of storage.
corrective action indicated there.
0536 Required field insert_1 (subfield
0534 Request to schedule object- insert_2) not found for query.
independent method insert_1 for Class insert_3, object insert_4.

A 'query a field' or a 'query multiple subfield' method An error occurred during a 'query field', 'query
API (MAPI) request did not succeed because the subfield', or 'query multiple subfield' method API
requested field does not exist on the object. (MAPI) transaction.
insert_1 insert_1
Field name. Field name.
insert_2 insert_2
Subfield name. Subfield name.
insert_3 insert_3
Class name. Class name.
insert_4 insert_4
Object name. Object name.
insert_5
The method invoking the query will probably end when insert_6
it observes this error. RODM reason code.

Ensure the method is using the correct object. Also, The method will probably end when it observes this
make sure that this object is in the correct RODM error condition.
class, and that this class has all of its fields properly
defined. System programmer response
0537 Object insert_1 not found for Determine the cause of the failure based on the
query. information provided in the message and correct the
problem.
Explanation 0539 Query failed due to unexpected
A 'query a field' or a 'query multiple subfield' method data type. Field insert_1 (subfield
API (MAPI) transaction did not succeed because the insert_2), class insert_3, object
requested object is not found. insert_4, expected type insert_5,
type of queried data insert_6.
Message Variables
Object name.
The data returned from a field query was not the data
type expected by the method.
System action
Message Variables
The method involved will probably end when it
observes this error condition. insert_1
Field name.
Subfield name.
Ensure that the method was accessing the intended
object. Also, determine if another RODM application insert_3
deleted the object while the method was running. Class name.
insert_4
0538 Query of field insert_1 (subfield
Object name.
insert_2) failed on class insert_3
object insert_4. Return code insert_5
insert_5, reason code insert_6. Expected data type.
insert_6
Data type returned by RODM.
The method will probably end when it observes this This message is issued to the log and the method
error. ends.

Correct the definition of the field to the correct type. Check for other log entries or console messages
0540 Field query failed due to incorrect exhausted. It might be necessary to change the RODM
data length. Field insert_1 customization parameters to provide a larger storage
(subfield insert_2), class insert_3, area for this type of storage.
object insert_4 expected length
insert_5, length of queried data 0542 Object id insert_1 not found for
insert_6. query of insert_2.
A query of a field, probably of type AnonymousVar, A 'query a field' method application program interface
returned the wrong amount of data. (MAPI) transaction did not succeed because the
requested object was not found.
Message Variables
Message Variables
insert_1
Field name. insert_1
insert_2 Object ID.
Subfield name. insert_2
insert_3 Field name.
Class name.
System action
insert_4
Object name. The method involved will probably end when it
insert_5 observes this error condition.
Expected data length.
Length returned by RODM. Ensure that the method was accessing the intended
object. Also determine if a RODM application deleted
System action the object while the method was running.
The method will probably end when it observes this 0543 A insert_1 request has been made
error. for the insert_2 object which is not
of a class for which this request is
System programmer response allowed.
Correct the value, which might be inherited, for the

Explanation
field. Also ensure that no application or method
changes this field to an incorrect value. A request of the type indicated was made for the
object indicated. The request was rejected because
0541 Field query unsuccessful due to the object is in the wrong class.
memory allocation failure - size =
insert_1 bytes. Message Variables
insert_1
Explanation Type of request.
A request to allocate a storage area of the size insert_2
indicated in the message was rejected. Object name.
Message Variables
System action
insert_1
Number of bytes requested. This message is issued to the log and the method
ends.

Correct the condition causing this failure and retry the Check the dump of the update mask, which will be in a
request. subsequent log entry, to see what errors are in the
update mask.
missing or incorrect for UserStatus 0546 New value provided to the change
update of insert_1. Parameter method is not of the appropriate
pointer = insert_2. If the pointer is length for the insert_1 field of
not zero, a dump of the object insert_2. Length supplied is
parameters will follow. insert_3 and the expected length
is insert_4.
Explanation
Explanation
A null short-lived parameter pointer has been passed
to the method, or the parameters pointed to contain The change method expects a data value of a specific
incorrect data. length for the new value but the value provided has a
different length.
Message Variables
Message Variables
insert_1
Parameter pointer. insert_2
Object name.
Supplied length.
ends. insert_4
Expected length.
System action
triggered with the required parameters. If the pointer This message is issued to the log and the method
is non-zero, check the dump of the parameters, which ends.
will be in a subsequent log entry, to determine what
errors are in the parameters. System programmer response
0545 The insert_1 update mask of Ensure that the method is installed on the correct field
insert_2 includes bits that are not and class. Correct this if necessary.
relevant for the insert_3 object.
0547 New insert_1 field value of
insert_2 provided to change
Explanation
method is not valid for this field
The indicated update mask includes bits that are not for object insert_3.
relevant for the indicated object. A dump of the update
mask follows. Explanation
Message Variables The change method cannot change the field's value
insert_1 because the new value provided to the change method
is not valid for this field in an object of this class.
insert_2
Message Variables
insert_3
Field name.
This message is issued to the log and the method Field value.
ends. insert_3
Object name.
This message is issued to the log and the method This message is issued to the log and processing ends.
ends. The response block is not returned.

Correct the new field value and retry. Check for other log entries or console messages
0548 Short lived input parameters are exhausted. It might be necessary to change the RODM
missing or incorrect for insert_1 customization parameters to provide a larger storage
update request. Parameter pointer area for this type of storage.
= insert_2. If the pointer is not
zero, a dump of the parameters 0550 Overflow has occurred for the
will follow. insert_1 field of insert_2
A null short-lived parameter pointer has been passed The maximum numeric value of the indicated field is
to the method, or the parameters pointed to contain exceeded, causing the value to become negative.
incorrect data.
Message Variables
Message Variables
insert_1
Type of update request. insert_2
insert_2 Object name.
Parameter pointer.
System action
System action
This message is issued to the log and the method ends.
ends.
Arrange the aggregation hierarchy again so that fewer
If the pointer is zero, make sure that the method is real resources appear beneath this aggregate.
is non-zero, check the dump of the parameters, which 0551 The value of the insert1filed on the
will be in a subsequent log entry, to see what errors insert2object must be changed at
are in the parameters. the class level.
0549 Cannot process insert_1 update Explanation

request because of a memory
allocation failure. Requested The value of the field must be changed at the class
insert_2 bytes. A dump of the level. The new value will be inherited by all objects
short-lived parameters for this unless the value has been changed on a lower level
method follow. class.
Message Variables
Explanation
insert_1
A request to allocate a storage area of the size Field name.
indicated in the message was rejected. insert_2
Message Variables Object name.
insert_1
System action
Type of update request.
insert_2 This message is written to the RODM log and the value
Number of requested bytes. of the field is unchanged.

Determine if the attempted change is valid for a Remove the loop from the aggregation hierarchy and
specific class. If the change is valid, then the value of resynchronize it by running the DUIFFAWS method or
the field sh be changed on that class object. by restarting GMFHS.
0552 The AggregationPriorityHistogram 0554 Excessive depth has been found in
field of insert_1 is not consistent the aggregation hierarchy at
with the insert_1. The aggregation path
PriorityValueUnsatisfactory value involved will be shown in
(insert_2) of that object. A dump of subsequent log entries.
the AggregationPriorityHistogram
follows. Explanation
A resource encountered in the network had too many
Explanation
generations of aggregation ancestors.
Internal aggregation counters in the GMFHS data
Message Variables
model have been corrupted.
insert_1
Message Variables
Resource name.
insert_1
Field name. System action
insert_2 This message is issued to the log and the method
Value. ends.

This message is issued to the log and the method Reduce the number of generations in the aggregation
ends. hierarchy and resynchronize it by running the
DUIFFAWS method or by restarting GMFHS.
Resynchronize the counters by triggering DUIFFAWS missing or incorrect for the trigger
or restarting GMFHS. of this method. Parameter pointer
0553 A loop has been encountered in = insert_1. If the pointer is not
the aggregation hierarchy at zero, a dump of the parameters
insert_1. The aggregation path for will follow.
this loop is shown in subsequent
log entries. Explanation
Explanation to the method, or the parameters pointed to contain
An illegal aggregation hierarchy has been encountered incorrect data.
in that a resource is one of its own aggregation Message Variables
ancestors.
insert_1
Message Variables Parameter pointer.
insert_1
Resource name. System action
System action ends.
ends. System programmer response
is non-zero, check the dump of the parameters, which
will be in a subsequent log entry, to see what errors System programmer response
Correct the problem and retry.
0557 The insert_1 named method was
0559 Required field insert_1 (subfield
not triggered for insert_2 which is
insert_2) not found for write. Class
linked to domain insert_3 because
insert_3, object insert_4.
the insert_4 field was not found on
that object. insert_2 might be of
the wrong object class. Explanation
A 'change a field' method application program
Explanation interface (MAPI) request did not succeed because the
requested field does not exist on the object.
An attempt to trigger the indicated named method
failed because the field on which the method is Message Variables
installed is not defined on the object.
insert_1
Message Variables Field name.
insert_1 insert_2
Method name. Subfield name.
insert_2 insert_3
Object name. Class name.
insert_3 insert_4
Domain name. Object name.
insert_4
Field name. System action
The method invoking the change will probably end
System action when it observes this error.
Ensure that the correct object is being used by the
System programmer response method. Also, ensure that this object is in the correct
RODM class, and that all of the fields for this class are
properly defined.
0558 The insert_1 field was not found
0560 Object not found for write. Class
for insert_2 which is linked to
insert_1, object insert_2.
domain insert_3. insert_2 might be
of the wrong object class.
Explanation
Explanation A 'change a field' method application program
interface (MAPI) transaction did not succeed because
An attempt to query the indicated field failed because
the requested object is not found.
the field is not defined on the object.
Message Variables
Message Variables
insert_1
insert_1
Class name.
Method name.
insert_2
insert_2
Object name.
Object name.
Domain name.
The method involved will probably end when it
System action observes this error condition.

continues.

Object name.insert.
Ensure that the method was accessing the intended
object. Also, determine if another RODM application
deleted the object while the method was running. System action
0561 Field change failed for field The method will probably end on finding this error.
insert_1 (subfield insert_2) of class
insert_3, object insert_4. Return System programmer response
code insert_5, reason insert_6. Ensure that the method is running on the correct
object, that the object is in the correct class, and that
Explanation the class is correctly defined.
An unusual error occurred during a 'change a field' or 0563 Object not found for insert_1
'change a subfield' method application program named method trigger. Class
interface (MAPI) transaction. insert_2, object insert_3.
Message Variables
Explanation
insert_1
Field name. An attempt to trigger a named method through the
insert_2 method application program interface (MAPI) failed
Subfield name. because the object specified in the request is not
found.
insert_3
Class name. Message Variables
insert_4 insert_1
Object name. Method name.
insert_5 insert_2
RODM return code. Class name.
insert_6 insert_3
RODM reason code. Object name.

The method will probably end when it observes this The method will probably end on finding this error.
error condition.
Ensure that the method is running on the correct
Determine the cause of the failure based on the object, that the object exists, and that the object has
information provided in the message and correct the not been recently deleted by another process.
problem.
0564 Trigger named method failed on
0562 Named method field insert_1 not field insert_1 of class insert_2,
found. Class insert_2, object object insert_3. Return code
insert_3. insert_4, reason insert_5.
An attempt to trigger a named method through the An attempt to trigger a named method failed for an
method application program interface (MAPI) failed unusual reason.
because the MethodSpec field naming the method is
Message Variables
not found.
insert_1
Message Variables
Field name.
insert_1 insert_2
Field name. Class name.
insert_2 insert_3
Class name. Object name.
RODM return code.
A request to send a notification through the method
insert_5 application program interface (MAPI) to a RODM
RODM reason code. application failed.
Message Variables
System action
insert_1
The method will probably end on finding this error. Application name.
insert_2
Queue name.
Use the information contained in the log entry to insert_3
resolve the problem. User word.
0565 Request to schedule named insert_4
method for asynchronous RODM Return code.
execution failed for field insert_1 insert_5
of class insert_2, object insert_3. RODM Reason code.
Return code insert_4, reason
insert_5.
System action
Explanation The notification is written to the RODM log, and
An attempt to trigger a named method using the
'message triggered action' function failed.
Message Variables
Inspect the RODM error log for any other messages
insert_1 that might be related to notification queue problems.
Field name. The return and reason code in this log entry sh provide
insert_2 additional information.
Class name. 0567 Error encountered in issuing
insert_3 output to the response block.
Object name. Return code insert_1, reason
insert_4 insert_2. RODM function id
RODM return code. insert_3, data pointer insert_4. A
dump of the function block and
insert_5
response data follows.
RODM reason code.
Explanation
System action
An 'output to response block' method application
The method will probably end upon encountering this program interface (MAPI) transaction failed for the
error. indicated return and reason codes.
Use the information contained in the log entry to try to insert_1

resolve the problem. RODM return code.
insert_2
0566 Request to send a notification to RODM reason code.
application insert_1 and queue
insert_2 failed. User word insert_3 insert_3
Return code insert_4, reason code RODM function ID.
insert_5. Notification data follows. insert_4
Data pointer.

Object name.
The intended response data is written to the RODM
error log. The method attempting to issue the
response data will probably end. System action
Ensure that the response block size provided to the 0570 The insert_1 value of insert_2
method is sufficient. Also, check the return and reason cannot be calculated because the
codes in the log entry and see if they identify other indicated object contains
causes for the problem. inconsistent field values.
0568 Request to trigger object
independent method insert_1 Explanation
failed. Return code insert_2, The indicated field value cannot be calculated for the
reason code insert_3. indicated object because field values required for the
calculation are inconsistent. This might be the result of
Explanation high RODM activity where asynchronous method
invocations are performed out of order. If this is the
A method attempted to trigger an object independent
case, the delayed method invocations sh run later and
method for synchronous execution. Either the
correct this situation. This might also be the result of
triggering mechanism or the method failed.
having thresholds on the aggregate that are higher
Message Variables than the total number of resources under the
aggregate. This can only be corrected by lowering the
insert_1
thresholds. In either case, message 0569 will be
Method name.
generated when the condition has been corrected.
insert_2
RODM return code. Message Variables
insert_3 insert_1
RODM reason code. Field name.
insert_2
System action Object name.
The method ends.
System action
System programmer response This message is issued to the log and the method
ends.
Determine the cause of the failure from the return and
reason codes given. A copy of the level-n method's
short-lived parameters follow this log entry. There System programmer response
might be other messages in the RODM log to assist in If the thresholds are in error, correct them and retry.
problem determination. Otherwise the problem sh correct itself.
0569 The insert_1 value of insert_2 can 0571 The insert_1 field of the insert_2
now be calculated because the object is linked to other than a
object's field values have been insert_3 class instance.
corrected.
Explanation
Explanation
The indicated field is linked to an object in an incorrect
This message is generated whenever the problem that class.
generated message 0570 has been corrected. The
aggregate's status will now be valid. Message Variables

Field name.
insert_1
insert_2
Field name.
Object name.
Class name.
System action is non-zero, check the dump of the parameters, which
This message is issued to the log and the method will be in a subsequent log entry, to see what errors
ends. are in the parameters.
0574 Cannot retrieve the aggregation
System programmer response profile for object insert_1 because
it is neither real nor aggregate (the
insert_2 field is not defined on its
0572 An object (insert_1) in the class).
aggregation hierarchy is of a class
that does not include the insert_2 Explanation
field, so it is neither a real nor an
aggregate object. The object specified in a get aggregation profile
request is not one that is involved in aggregation.
A method encountered an object which does not insert_1
represent a GMFHS real or aggregate resource. Object name.
Field name.
insert_1
Object name.
System action
insert_2
Field name. The method ends.
The method ends. Determine the object for which that retrieval was
intended. Ensure that this object is in a class that is
properly defined for aggregation.
Ensure that the method is triggered on an appropriate 0575 Cannot retrieve the aggregation
object, that the object is in a class that contains real or profile for object insert_1 because
aggregate objects, and that the class is properly an object with this identifier
defined in the GMFHS structure load input file. cannot be found.
0573 Short lived input parameters are Explanation

missing or invalid for a get object
profile request. Short lived A request to get an aggregation profile was made, but
parameter pointer is insert_1. If the object specified in the request does not exist.
the pointer is not zero, a dump of Message Variables
the parameters will follow.
insert_1
Object name.
Explanation
A get aggregation profile request was made with System action
missing or garbled input parameters.
The method ends.
Message Variables
Parameter pointer.
No response is required if the object was legitimately
deleted from the system. If the object is sh exist at this
System action time, determine why the object is not there.
The method ends.

0576 Cannot retrieve the aggregation 0578 Cannot update the aggregation
profile for object insert_1 because profile for object insert_1 because
it is linked via its insert_2 field to a it is neither real nor aggregate (the
insert_3 class instance instead of a insert_2 field is not defined on its
insert_4 class instance. class).
An aggregate is not linked to a Display Resource Type The object specified in an update aggregation profile
object as required, but is instead linked to an object in request is not one that is involved in aggregation.
another class.
Message Variables
Message Variables
insert_1
Field name.
Class linked to. The method ends.
insert_4
Class sh be linked to. System programmer response
Determine the object for which the update was
System action
intended. Ensure that this object is in a class that is
The method ends. properly defined for aggregation.
0579 Cannot update the aggregation
profile for object insert_1 because
Link the aggregate to an appropriate display resource an object with this identifier
type. cannot be found.
Explanation
missing or invalid for an update
object profile request. Short lived A request to update an aggregation profile was made,
parameter pointer is insert_1. If but the object specified in the request does not exist.
the pointer is not zero, a dump of
Message Variables
insert_1
Explanation Object name.
An update aggregation profile request was made with

System action
missing or garbled input parameters.
The method ends.
Message Variables
Parameter pointer.
If the object was legitimately deleted from the system,
no response is required. If the object sh exist at this
System action
time, determine why it is not there.
The method ends.
0580 The insert_1 field of object
insert_2 was corrected from
insert_3 to insert_4.
triggered with the required parameters. If the pointer Explanation
is non-zero, check the dump of the parameters, which
will be in a subsequent log entry, to see what errors A method encountered an aggregation parameter that
are in the parameters. is incorrectly defined. The method opted to replace
the incorrect value with a default.
insert_1 A request to allocate a storage area of the size
Field name. indicated in the message was rejected.
insert_2 Message Variables
Object name.
insert_1
insert_3 Requested number of bytes.
Incorrect value.
Default value.
ends.
System action
Processing continues. Warning return codes and System programmer response
reason codes are set when the method ends.
Determine why the field was improperly set, and customization parameters to provide a larger storage
ensure that the default chosen by the method is the area for this type of storage.
desired one.
0581 Short lived input parameters are missing or incorrect for an update
missing or incorrect for a get resource type profile request.
resource type profile request. Short lived parameter pointer is
Short lived parameter pointer is insert_1. If the pointer is not zero,
insert_1. If the pointer is not zero, a dump of the parameters will
a dump of the parameters will follow.
follow.
Explanation
Explanation
A null, short-lived parameter pointer has been passed to the method, or the parameters pointed to contain
to the method, or the parameters pointed to contain incorrect data.
incorrect data.
Message Variables
Message Variables
insert_1
insert_1 Parameter pointer.
Parameter pointer.
System action
System action
This message is issued to the log and the method ends.
ends.
If the pointer is zero, make sure the method is
If the pointer is zero, make sure that the method is triggered with the required parameters. If the pointer
triggered with the required parameters. If the pointer is non-zero, check the dump of the parameters, which
is non-zero, check the dump of the parameters, which will be in a subsequent log entry, to see what errors
will be in a subsequent log entry, to see what errors are in the parameters.
0584 Update resource type profile
0582 Get resource type aggregation request processing failed: The
profile request not processed due request contained a type number,
to memory allocation failure. insert_1 (hex insert_2), for which a
Requested insert_1 bytes. A dump insert_3 class object cannot be
of the short lived parameters found. A dump of the complete
including the request will follow. short lived parameters follows.

An object in the specified class with specified type An aggregate object has a null link to a display
number does not exist. resource type object so default aggregation thresholds
are not available for the aggregate object.
Message Variables
Message Variables
insert_1
Type number. insert_1
insert_2 Aggregate name.
Hexadecimal value of type number. insert_2
Class name. insert_3
Default aggregation threshold.
System action
System action
ends. This message is issued to the log and -1 (never
exceeded) is used as the default threshold value.
Determine whether a Display Resource Type class
object with the indicated type number sh exist, and if Establish a link between the aggregate object
so, restore its definition. identified in the message and an appropriate resource
type object.
0585 Update resource type profile
request processing failed for a 0587 Short lived input parameters
insert_1 class object with type provided to the change method for
number insert_2 (hex insert_3). A field insert_1 of object insert_2 are
dump of the complete short lived missing or incorrect. Parameter
parameters follows. pointer = insert_3. If the pointer is
not zero, a dump of the
Explanation parameters will follow.
The update of an object in the specified class with the

Explanation
specified type number failed.
A null, short-lived parameter pointer has been passed
Message Variables
to the method, or the parameters pointed to contain
insert_1 incorrect data.
Class name.
Message Variables
insert_2
Type number. insert_1
Field name.
insert_3
Hexadecimal value of type number. insert_2
Object name.
Parameter pointer.
ends.
System action
System programmer response This message is issued to the log and the method
ends.
Check for prior log entries which indicate the reason
for the failure. Correct the problem indicated in these
entries and retry the request.
0586 Aggregate insert_1 is not linked to triggered with the required parameters. If the pointer
a insert_2 object. insert_3 is being is non-zero, check the dump of the parameters, which
used for the default aggregation
threshold values.
will be in a subsequent log entry, to see what errors 0591 Short lived input parameters are
are in the parameters. missing or invalid for a update
aggregation path request. Short
lived parameter pointer is
missing or invalid for a
insert_1. If the pointer is not zero,
ChangeAggregationPriority
request for insert_1. Short lived
follow.
parameter pointer is insert_2. If
the pointer is not zero, a dump of
the parameters will follow. Explanation
An Update Aggregation Path request made with
Explanation missing or unusable input parameters.
A request to change a resource's aggregation priority Message Variables
was made with missing or unusable input parameters.
insert_1
Message Variables Parameter pointer.
insert_1
Resource name. System action
insert_2 The method ends.
Parameter pointer.
System action Correct the input parameters and retry the request.
The method ends.
0592 insert_1 object (object id insert_2)
in the insert_3 update aggregation
System programmer response path request was not found.
If you invoked this method, correct the input
parameters to the method. If GMFHS invoked this Explanation
method, contact IBM Software Support for assistance.
An object that was specified by RODM object identifier
0589 New insert_1 field value of in an Update Aggregation Path request was not found.
insert_2 provided to change Message Variables
method is not valid for this field
for class insert_3. insert_1
Object name.
Object ID.
The change method cannot change the field's value
because the new value provided to the change method insert_3
is not valid for this field and class. Type of request.
Message Variables
System action
insert_1
The method ends.
Field name.
insert_2
Field value.
insert_3 Ensure that the input parameters for the request are in
Class name. the correct format, that the object is specified
correctly, and that it exists.
System action 0593 insert_1 in the update aggregation
path request is not of a valid class
for this request.
ends.

Correct the new field value and retry.

One of the objects in the Update Aggregation Path XCPT is assumed and processing continues.
request is not a member of the appropriate class; it is
not a real or aggregate object as required. System programmer response
Message Variables Update the DisplayStatus field on the object —that will
insert_1 cause ResourceTraits to be updated correctly.
Object name. 0596 Update aggregation path request
to insert_1 insert_2 and insert_3
System action failed because a stable list of the
objects affected by the request
The method ends.
cannot be built and locked. A
dump of the lock function blocks
System programmer response follow.
Determine if the input parameters to the Update
Aggregation Path request are reversed. Also, ensure Explanation
that the objects specified in the request are of the
Either several Update Aggregation Path requests or a
correct types, and that their classes are properly
RODM or GMFHS structure or object load is in
defined in the GMFHS structure load.
progress.
0594 Update aggregation path request
Message Variables
rejected because the identifiers in
the input parameters are of the insert_1
same object (insert_1). Object name.
insert_2
Explanation Object name.
You requested that an object become its own insert_3
aggregation parent. This is not allowed. Object name.
Message Variables
System action
insert_1
Object name. The method ends.
The method ends. Wait until existing RODM and GMFHS activity is
substantially reduced, and retry the request. Avoid
submitting a large number of requests simultaneously.
0597 A request to allocate insert_1
Correct the request to specify a valid aggregation
bytes of memory failed.
relationship.
0595 The ResourceTraits field of the Explanation
object insert_1does not contain an
exception status (XCPT or NOXCPT A request to allocate a storage area of the size
values), XCPT is assumed. indicated in the message is rejected.
Message Variables
GMFHS is dependent upon those values for Number of bytes requested.
aggregation calculation and exception views. One of
those values must be present. System action
Message Variables This message is issued to the log and the method
insert_1 ends.
Object name.
System programmer response Trigger DUIFFAWS or reinitialize GMFHS to
resynchronize the aggregation hierarchy. Retry the
request.
exhausted. It might be necessary to change the RODM 0605 Short lived input parameters are
customization parameters to provide a larger storage missing or invalid for a list
area for this type of storage. suspended resources request.
Short lived parameter pointer is
0599 An update aggregation path
insert_1. If the pointer is not zero,
request will fail because object
insert_1 has been encountered in
follow.
the aggregation hierarchy and this
object's class does not have the
required insert_2 field. Explanation
No short-lived parameters are provided in the List
Explanation Suspended Resources request, or those that are
provided are incomplete or in the wrong format.
An object in the aggregation hierarchy does not have
its class correctly defined. Message Variables
Parameter pointer.
insert_1
Object name.
System action
insert_2
Field name. The method ends.

The method ends. Correct the input parameters to the method and retry
the list. If the method was invoked by GMFHS, contact
System programmer response IBM Software Support for assistance. GMFHS code sh
use the correct format.
Ensure that the object is in the appropriate class and
that it belongs in the aggregation hierarchy. Also, 0606 The list suspended resources
ensure that the class is correctly defined in the GMFHS request cannot be processed due
structure load. to a memory allocation failure.
Requested insert_1 bytes.
0604 Update aggregation path failed
because the aggregation counters Explanation
on insert_1 are not consistent.
A request to allocate a storage area of the size
Explanation indicated in the message is rejected.
Inconsistent data was found in an object involved in an Message Variables

Update Aggregation Path request. The inconsistency insert_1
was probably caused by the failure of an earlier Number of bytes requested.
method.
insert_1 This message is issued to the log and the method
Object name. ends.

The method is ends. Check for other log entries or console messages
System programmer response exhausted. It might be necessary to change the RODM
customization parameters to provide a larger storage
Check the log for evidence of methods which failed area for this type of storage.
earlier, possibly corrupting aggregation counters.

0607 Short lived input parameters are Explanation
missing or invalid for a link An object specified in a Link Resource Type request is
resource type request. Short lived not appropriate for the transaction. One object sh be a
parameter pointer is insert_1. If Display Resource Type, and the other sh be a real,
the pointer is not zero, a dump of aggregate, or shadow object.
Message Variables
No short-lived parameters are provided in the Link Object name.
Resource Type request, or those that are provided are
incomplete or in the wrong format. System action
Message Variables The method ends.
insert_1
Parameter pointer. System programmer response
Ensure that the two resources specified in the
System action method's input parameters are in the correct order. If
they are reversed, this error w occur. Also, ensure that
The method ends. the resources are in the appropriate classes, and that
the classes are correctly defined.
0610 An invalid value (insert_1) was
Correct the input parameters to the method and retry found in the insert_2 field of the
the link. insert_3 object in processing a link
0608 insert_1 object (object id insert_2) resource type request. A value of
in the insert_3 Resource Type insert_4 was used in place of the
request was not found. invalid value.
A Link Resource Type request was made on an object An incorrect value was encountered in the indicated
that did not exist at the time of the request or was object for a Link Resource Type request.
deleted before the request completed. Message Variables
insert_1 Incorrect field value.
Object ID. insert_3
Type of resource type request. insert_4
Default value used.
System action
System action
The method ends.
A default value (shown in the message) is substituted
System programmer response for the incorrect value and processing continues.
Determine why the object that was specified does not

exist, and take corrective action. It is not necessary to
resynchronize the network, because no aggregation Correct the field's value. Also, determine what
counters have been corrupted. application or user set the wrong field value.
0609 insert_1 in the link resource type 0611 Object insert_1, specified in a
request is not of a valid class for insert_2 Resource Type request,
this request. was not found.
Object name.
A Link Resource Type request was made on an object
that either did not exist at the time of the request or
was deleted before the request completed. System action
Message Variables The method ends.
insert_1
Object name.
insert_2 This is probably caused by a method logic error. If
Type of resource type request. prior log entries do not contain messages that indicate
why this error occurred and what corrects must be
made, contact IBM Software Support for assistance.
System action
0614 The insert_1 field of insert_2 had
The method ends.
an invalid value (insert_3). This
value was updated to insert_4.
Determine why the object that was specified does not Explanation
exist and take corrective action if necessary.
The indicated field has a value that is not valid for the
0612 Object insert_1, specified in a object class to which the specified object belongs. This
insert_2 Update Aggregation Path condition was detected during an update operation
request, was not found. and the incorrect value has been replaced by that
supplied in the update request.
An Update Aggregation Path request was made on an insert_1
object that did not exist at the time of the request or Field name.
was deleted before the request completed.
insert_2
Message Variables Object name.
insert_1 insert_3
Object name. Incorrect field value.
insert_2 insert_4
Type of request. Default value used.
The method ends. Processing continues.
Determine why the object that was specified does not This message probably indicates that the value
exist, and take corrective action if necessary. subfield of the field was changed so that the normal
edit to guard against unusable values is not done. No
0613 An attempt to over-synchronize action is required because the unusable value has
aggregate object insert_1 has been been corrected.
detected.
0615 The insert_1 field of the insert_2
Explanation class had an invalid value
(insert_3). This value was updated
The UpdateAggregationCounters named method, to insert_4.
triggered for an aggregation hierarchy
resynchronization (aggregation warmstart), has Explanation
detected that resynchronization has already been
completed for the aggregate object for which it was The indicated field has a value that is not valid for the
triggered. object class. This was detected during an update
operation and the incorrect value has been replaced
Message Variables by that supplied in the update request.

insert_1 Processing continues.
Field name.
Class name. This message probably indicates that the value
insert_3 subfield of the field was changed so that the normal
Incorrect field value. edit to guard against unusable values was not done.
insert_4 No action is required because the unusable value has
Default value used. been corrected.
Abend Codes
Appendix A. Codes
This appendix provides information about the following abend and sense codes:
• NetView program abend codes, including:
– GMFHS abend codes
– RODM abend codes
– SNA topology manager abend codes
• Alias sense codes
• LUC conversation request service return codes and sense codes
• Generic alert code points
NetView Abend Codes

An abend code is generated for an unrecoverable error. This completion code is issued when a logic error
occurs or a serious problem is detected. The code is presented on the abend dump listing as user code
Uxxxx, where xxxx is the decimal code as described in this section.
The system action for all codes is for the abending task to stop running.
This section contains abend codes issued by:
• AAU module
• Alias name translation facility
• BNJ module
• CNM module
• Command list function
• DSIOST and DSINNT
• DSIPPT
• DSIZDST
• DUI module
• DWO module
• GMFHS
• RODM
• SNA topology manager
Table 1. NetView Abend Codes

Decimal Hex Explanation of the Abend
Code Code
001 X'001' NetView initialization failed. See the system log for any error messages that
indicate the reason for the failure.
002 X'002' OPEN failed for the NetView main task ACB.
003 X'003' SHOWCB failed for VTAM API control blocks.
004 X'004' DSIGET failed for the NetView main task APPLID suffix table.
006 X'006' SETLOGON START to accept logons failed.

Abend Codes
Table 1. NetView Abend Codes (continued)

Code Code
009 X'009' The NetView main task cannot load the NetView message definition modules
DSIMDM or DSIMDMV. Verify that the required modules, panels, or tables are
properly installed. Also, verify that the modules, panels, or tables can be accessed
by the NetView application.
010 X'00A' The primary POI task ended abnormally because the maximum retry count for this
view was exceeded.
Note: A message might have preceded this abend.
011 X'00B' Control blocks cannot be built for the NetView main task.
012 X'00C' An installation exit that runs in 24-bit addressing mode needs to address a data
area that resides in 31-bit storage. The data area is at least one of the following:
the CNM input buffer, VSAM user data area, or VSAM key.
013 X'00D' The NetView program encountered an unsupported internal command request
code.
015 X'00F' NPS DST initialization failed.
016 X'010' The count fields of the control blocks DSIRAL and DSILAL or DSISAL are not equal.
This causes errors when calling NetView service routines.
017 X'011' The DSIRNK table is not large enough to hold the keywords of the command it is
processing. This abend only occurs if more keywords are defined for a command,
and the DSIRNK table in DSIYOSR is not updated to reflect the change.
018 X'012' Storage does not belong to the caller, or the length of the data record exceeds the
limit.
019 X'013' The NetView main task uses this code in response to a CLOSE ABEND command.
020 X'014' The NetView main task uses this code in response to a CLOSE DUMP command.
021 X'015' STACK is exceeded because of EXIT interrupts.
023 X'017' DSIGMN or DSIFMN is indicating that the issuing module cannot obtain a working
storage area because all working storage areas are in use.
024 X'018' LERAD/SYNAD stack was exceeded because of exit interrupts.
025 X'019' The interface to the high-level language (MVS only) environment (DSIHLINK) was
invoked for reasons other than initialization, resume, abend, logoff, or termination.
026 X'01A' The user attempted to use DSIHLLAR to perform illegal multitasking from a task
control block (TCB).
027 X'01B' The matching RPL is not found in the queue of waiting request blocks. Issued by
VPDTASK.
029 X'01D' The DSICES macro gives a return code that is not 0 or 20. The CNMTAMEL DSCP
verb name (DUIADISP) cannot be found. Abend issued from module DUIATIMR.
DUMP(NO).
030 X'01E' Resume issued for an ADX that was not suspended. Abend issued from module
DUIARES. DUMP(YES).
031 X'01F' Logic error. Abend issued from module DUISHMQA. DUMP (YES).

Abend Codes

Code Code
032 X'020' The DSILOD macro failed to load message table DUIAMSGS or service module
table DUIISVCT. Verify that these modules are properly installed. Also, verify that
the modules can be accessed by the NetView program. Abend issued from module
DUIINITA. DUMP(NO).
033 X'021' Cannot get storage during CNMTAMEL task initialization. Abend issued from
module DUIINITA. DUMP(YES).
034 X'022' Logic error. Abend issued from module DUISHQMA. DUMP(YES).
035 X'023' The DSILOD macro failed to load service modules. Verify that the NetView program
is properly installed and that all NetView modules can be accessed. Abend issued
from modules DUIDLOAD and DUIALOAD. DUMP(YES).
036 X'024' The DSIGET macro failed. Abend issued from module DUIMENTR. DUMP(YES).
037 X'025' Logic error. Abend issued from module DUISHMQA. DUMP(YES).
038 X'026' The LU 6.2 command processor definition macro DSIL6DFS failed. Abend issued
from module DUIINITA. DUMP(NO).
039 X'027' Cannot obtain required ADX control blocks. Abend issued from module DUIINITA.
DUMP(NO).
040 X'028' There is not enough available storage to build and initialize the resource status
collector list with the user-specified MAXSCCOUNT number. Abend issued from
module DUIDIMDP. DUMP(YES).
043 X'02B' There is not enough available storage to build the resource status collector list.
Abend issued from module DUIDITTP. DUMP(YES).
044 X'02C' VTAM APPCCMD macro not accepted or bad command verb. Abend issued from
modules DUIACNOS and DUIAAPPC. DUMP(YES).
045 X'02D' Call to module DUIACMIO is not valid. Abend issued from module DUIACNOS.
DUMP(YES).
046 X'02E' CNOS APPCCMD not accepted. Abend issued from module DUIACNOS.
DUMP(YES).
047 X'02F' APPCCMD completed with return code ABEND. Abend issued from module
DUIADETE. DUMP(YES).
048 X'030' ADX pool value is not valid. Abend issued from module DUIAADXM. DUMP(YES).
049 X'031' Incorrect task when buffer origin is DSICRTR. Abend issued from module
DUISHQMA. DUMP(YES).
050 X'032' Incorrect buffer origin. Abend issued from module DUISHQMA. DUMP(YES).
051 X'033' Status sent by resource status collector in either a REPLY SYNCH or an UPDATE
vector is not valid. Abend issued from modules DUIDGADE and DUIDGUPE.
DUMP(YES).
053 X'035' Logic error. Abend issued from module DUIDIMRP. DUMP(YES).
054 X'036' Logic error. Abend issued from module DSIFRCFP. DUMP(YES).
055 X'037' Logic error. Abend issued from module DSIFRCFP. DUMP(YES).
056 X'038' Logic error. Abend issued from module DUISHMQA. DUMP(YES).
Appendix A. Codes 913

Abend Codes

Code Code
057 X'039' The DSILOD macro failed to load module DUIALOAD. Verify that this module is
properly installed and that it can be accessed by the NetView program. Abend
issued from module DUIINITA. DUMP(NO).
058 X'03A' The DSILOD macro failed to load module DUIDINIT. Verify that this module is
installed and that it can be accessed by the NetView program. Abend issued from
module DUIINITA. DUMP(NO).
059 X'03B' Logic error. Abend issued from module DSICSND. DUMP(YES).
060 X'03C' Call to DUIADISP is not valid. Abend issued from module DUIADISP. DUMP(YES).
061 X'03D' Logic error. Abend issued from module DUISHSNA. DUMP(YES).
063 X'03F' NETTYPE control block not found. Abend issued from module DUIDSSEG.
DUMP(YES).
064 X'040' Logic error. Abend issued from module DUIADISP. DUMP(YES).
067 X'043' Error in hashing function. Abend issued from module DUIDFPUR. DUMP(YES).
068 X'044' CNMTAMEL task initialization failed. Abend issued from module DUISDISP.
DUMP(NO).
069 X'045' A buffer was queued that was not valid. Abend issued from module DUIADISP.
DUMP(YES).
070 X'046' Logic error. Abend issued from module DUISHDEA. DUMP(YES).
072 X'048' Logic error. Abend issued from module DUIDHSHS. DUMP(YES).
073 X'049' Logic error. Abend issued from module DUIDHSHS. DUMP(YES).
074 X'04A' Logic error. Abend issued from module DUIDHSHS. DUMP(YES).
075 X'04B' Logic error. Abend issued from module DUIDIMNP. DUMP(YES).
076 X'04C' Logic error. Abend issued from module DUIDIMDP. DUMP(YES).
077 X'04D' Logic error. Abend issued from module DUIDIDCP. DUMP(YES).
078 X'04E' Logic error. Abend issued from module DUIATRPR. DUMP(YES).
079 X'04F' Logic error. Abend issued from module DUIDMQRY. DUMP(YES).
080 X'050' CSCF attempted to acquire storage using DSIGET. The attempt failed.
081 X'051' This code is used by the operator station task (OST) when an incorrect data stream
is received from a hardware device.
082 X'052' Used for stack overflow or underflow.
083 X'053' The NetView program detected an overlay of the DSICWB control block possibly
caused by the abending task's misuse of the CWBADATD field. This abend might be
accompanied by user abend 2304 (X'900') or other abends that indicate a storage
overlay.

Abend Codes

Code Code
085 X'055' The initialization routine cannot obtain storage for the primary anchor control block
whose address is returned in the bhlbptr parameter of CNMETIN (CNMETINIT).
Initialization of the server support API failed.
086 X'056' The initialization routine cannot load either of the required NetView load modules
DSIEHLAR, DSIEHL24, or both. Initialization of the server support API failed.
087 X'057' This abend code can be issued as follows:
• The MDS-RECEIVE cannot be defined.
• The PUSH of the logoff routine failed.
• A terminating error was encountered by the other initialization modules for the
transport.
• Bad syntax on the PARTNER statement.
• Failure in operations management or focal point initialization.
• Failure when attempting to issue a timer services request during task
initialization.
• Failure when attempting to push a logoff routine from the task being initialized.
This can be caused by a missing CMDDEF statement.
• Failure when attempting to define to the command facility one of the LU 6.2
transaction programs that the transport uses.
089 X'059' Unexpected error occurred in automation table processing. DUMP (YES).
090 X'05A' A return code that is not valid was received during GLOBALV processing.
091 X'05B' Should not occur: severe error returns from the NetView Bridge dispatcher.
092 X'05C' Logic error. Abend issued from module DUIDUPRQ. DUMP(YES).
093 X'05D' Logic error. Abend issued from module DUIDMCFV. DUMP(YES).
094 X'05E' Logic error. Abend issued from module DUIDMLUV. DUMP(YES).
095 X'05F' Logic error. Abend issued from module DUIDICDP. DUMP(YES).
096 X'060' Logic error. Abend issued from module DSIIBMHL. DUMP(YES).
097 X'061' DSIWAT time-out. A limit set in the DSIMVT control block was reached while task
message queues were blocked. See DSIMVT maco label MVTCPAWT for details.
098 X'062' Unrecoverable SELECT error. Abend issued from DUIASELE. DUMP(YES).
112 X'070' A Graphic Monitor Facility host subsystem (GMFHS) method detected an out-of-
storage condition. The Resource Object Data Manager (RODM) generates a log
record type 7 containing this abend code. The user application program triggering
the abending method receives a return code 12 with reason code 194.
113 X'071' The security software initialization for the primary POI task has failed.
115 X'073' The DSIPUSH macro failed. Abend issued from BNJAPAMA.
257 X'101' RESET IMMED or RESET DUMP command was issued. The error recovery routine of
some system services can generate a dump. See the STOP command in NetView
online help for more information.
258 X'102' Unexpected LERAD error under non-TAF environment.

Abend Codes

Code Code
259 X'103' An installation exit returned a return code that is not valid or USERSWAP is
selected, but the buffer is too small to hold the new record. Register 5 contains an
installation exit number, and register 6 contains a return code from the installation
exit.
261 X'105' Unexpected LOSTERM entry.
262 X'106' An installation exit returned a return code that is not valid or USERSWAP is
selected, but the buffer is too small to hold the new record. Register 5 contains an
installation exit number, and register 6 contains a return code from the installation
exit.
263 X'107' Installation exit DSIEX01 returned a code that is not valid or USERSWAP is
selected, but the buffer is too small to hold the new record. Register 3 contains the
installation exit return code.
264 X'108' The internal function request code is not valid.
266 X'10A' Terminal session was lost while a command was running in DSIRCV.
267 X'10B' Terminal session was lost while a command was running in DSIPS14.
268 X'10C' Unexpected SYNAD error. Hardware type error, see message DSI625I.
269 X'10D' Unexpected LERAD error under TAF environment.
270 X'10E' Unexpected DSIGET failure while processing a RMTCMD or ENDTASK command.
See NetView online help for information about the RMTCMD and ENDTASK
commands.
271 X'10F' A NetView function called another function (such as a SAF product) and the
maximum amount of time allowed for that call was exceeded. The task
experienced this abend to interrupt the request that was taking too long. If the
function called was an SAF product, the maximum time that is allowed is 10
seconds.
320 X'140' Unexpected return code from DSIDKS macro in module DSICCGO.
321 X'141' Unexpected function type returned by dictionary services in module DSICCFCN.
322 X'142' Unexpected return code from dictionary services in the DSICCSUB module and the
DSIRXFCR module.
323 X'143' Unexpected return code from the ISGLPRG service routine in the DSILPRGI
module.
336 X'150' Should not occur: either an unknown or unexpected return code was returned from
the REXX interpreter, or the requested storage length is a negative value or zero.
337 X'151' REXX obtained storage is not freed. DSIFRE was invoked to free storage on behalf
of REXX. Storage was not freed, but a dump was taken.
384 X'180' Unexpected return code from DSIKVS macro in module DSISTP.
385 X'181' Unexpected return code from DSIKVS macro in module DSISWCP.
386 X'182' Unexpected return code from DSIKVS macro in module DSISRP.
387 X'183' Unexpected return code from DSIKVS macro in module DSIEVP.
388 X'184' Unexpected return code from DSIKVS macro in module DSIATP.

Abend Codes

Code Code
389 X'185' This abend occurs only when the ABEND_AND_DUMP parameter in the FLBSYSD
initialization file is set to YES and the SNA topology manager detects a severe
problem with RODM.
initialization file is set to YES and the SNA topology manager detects a storage
overlay condition.
initialization file is set to YES and the SNA topology manager detects an internal
error.
518 X'206' An installation exit returned a code that is not valid or USERSWAP is selected, but
the buffer is too small to hold the new record. Register 5 contains the installation
exit number, and register 6 contains the return code from the installation exit.
520 X'208' A function type that is not valid was received.
550 X'226' DSIITM has detected a BUFHDR that is not valid in a buffer being traced for either
the PSS, QUE, or UEXIT trace option. Contact IBM Software Support for
programming assistance.
600 X'258' Logic error occurred in the NetView program. Contact IBM Software Support for
666 X'29A' Logic error occurred in the NetView program. Contact IBM Software Support for
668 X'29C' A reference to a freed CCV has been detected by the NetView program.
1024 X'400' I/O error during VSAM VERIFY macro processing.
1025 X'401' DSIGET failed to obtain storage.
1026 X'402' Subtask cannot complete initialization.
1027 X'403' Unable to send reply request unit to VTAM by the communication network
management interface.
1028 X'404' Logic error in alias application. Index value in control block is wrong.
1029 X'405' Unrecoverable error during alias initialization. Preceded by a description message.
1030 X'406' Unexpected return code following a DSIDKS macro.
1031 X'407' The VSAM POINT macro failed on the event log database in the database server
VSAM I/O initiate routine.
1032 X'408' The VSAM GET macro failed on the event log database in the database server VSAM
I/O initiate routine.
1033 X'409' The VSAM POINT macro failed in the COMPUTE INITIAL DATABASE STATUS
MODULE READ FIRST RECORD routine.
1034 X'40A' The VSAM GET macro failed in the COMPUTE INITIAL DATABASE STATUS MODULE
READ FIRST RECORD routine.
1035 X'40B' The VSAM POINT macro failed in the COMPUTE INITIAL DATABASE STATUS
MODULE READ MIDDLE RECORD routine.
1036 X'40C' The VSAM GET macro failed in the COMPUTE INITIAL DATABASE STATUS MODULE
READ MIDDLE RECORD routine.

Abend Codes

Code Code
1037 X'40D' Logic error. The first record in a logical wrap database is a seed record but the last
is not a seed.
1038 X'40E' Logic error. The binary search to locate the absolute low and high bounds of a
logical wrap database failed.
1039 X'40F' Logic error. A record returned from the VSAM GET macro did not match the
requested database ID.
1040 X'410' The VSAM GET macro failed in the COMPUTE INITIAL DATABASE STATUS MODULE
READ FIRST RECORD routine.
1041 X'411' The VSAM POINT macro failed in the COMPUTE INITIAL DATABASE STATUS
MODULE SEQUENTIAL READ RECORD routine.
1042 X'412' The VSAM GET macro failed in the COMPUTE INITIAL DATABASE STATUS MODULE
SEQUENTIAL READ RECORD routine.
1043 X'413' The VSAM GET macro failed in the GET FIRST RECORD FORWARD routine.
1044 X'414' The VSAM POINT macro failed in the READ PREVIOUS routine.
1045 X'415' The VSAM GET macro failed in the READ PREVIOUS routine.
1046 X'416' The VSAM GET macro failed in the READ LOGICAL WRAP RECORD routine.
1048 X'418' Logic error. Address of the positioning keys pointer in the READ LOGICAL WRAP
RECORD routine was zero.
1281 X'501' NetView issues this abend to cause task recovery. Indications are that this task
took an abend in NetView code running in an asynchronous exit while the task
mainline code was processing a REXX command procedure. The asynchronous exit
abend was intercepted by a REXX ESTAE routine that cleared REXX, then returned
control to this NetView task. The REXX intercept of the asynchronous task abend
did not allow NetView to correctly recover from the abend. NetView issues abend
1281 to achieve drive NetView task abend recovery. Check your system log for
information pertaining to the asynchronous exit abend. A dump is taken by this
abend in case it is needed to determine the cause of the asynchronous exit abend.
2000 X'7D0' Reserved for IBM Software Support
2304 X'900' Module requires a larger work area than found, for successful entry linkage.
2305 X'901' Status monitor did not initialize successfully.

Abend Codes

Code Code
2306 X'902' Nonzero return code received from DSILOD of any status monitor module. Verify
that the required modules, panels, or tables are properly installed. Also, verify that
the modules, panels, or tables can be accessed by the NetView application.
2307 X'903' Status monitor internal error.
2310 X'906' Five consecutive SNDCMD or RCVCMD failures occurred in CNMTARCA.
2311 X'907' The module called by CNMTFLTR to process message text has returned a result
larger than expected. Storage might have been overwritten.
2312 X'908' Status monitor initialization failed. Verify that the module ISTIECCE is available to
VTAM as outlined in IBM Z NetView Installation: Configuring Additional
Components.
2320 X'910' A DROP = YES condition was encountered while in a full-screen panel. The session
was dropped.
2501 X'9C5' Note: This is a system abend code.
With Reason Code 0: RODM has cancelled the transaction based on the reply to
message EKG1326D. Message EKG1326D is issued when there are transactions
still running in RODM during RODM checkpoint or RODM termination.
With Reason Code 33: A RODM internal error has occurred; contact IBM Software
Support for programming assistance.
2816 X'B00' NetView subsystem detected a PC call to PPI service routine that is not valid.
2977 X'BA1' Session monitor detected a connectivity chain that is not valid. Contact IBM
2982 X'BA6' The session monitor detected a connectivity chain that is not valid. Contact IBM
2983 X'BA7' The session monitor detected a connectivity chain that is not valid. Contact IBM
2989 X'BAD' NetView has detected that a VTAM send has not completed. Either the send was
issued more than 3 minutes ago or the data queues are overloaded. Presentation
services output queues overload is defined as exceeding twice the value of
NORMQMAX as specified in the operators SCRNFMT. This is probably either an
operator terminal or VTAM problem.
3002 X'BBA' There is no page number table primary segment address in the hierarchy table.

Abend Codes

Code Code
3008 X'BC0' The NetView display panel size (PDXDVSIZ) is less than 21 lines, but it must be at
least 21 (24 minus 3) lines.
3010 X'BC2' The DSIPSS macro gives a nonzero return code. The FIRST, MIDDLE, and LAST
operands are not specified in the correct order, or too many DSIPSS macros have
been issued for the display panel size.
3083 X'C0B' The DSIGET macro is unable to obtain enough storage for the DSIMQS buffer.
3085 X'C0D' The DSIGET macro is unable to obtain enough storage for the DSIMAS buffer.
3086 X'C0E' The DSICES macro gives a nonzero return code. The routine failed to successfully
transfer control because it cannot find the task ID or the verb associated with it.
3089 X'C11' The DSIMBS macro gives a return code not equal to 0 or 12. The NetView program
cannot retrieve a message and message BNJ322I has been issued.
3339 X'D0B' The DSIGET macro gives a nonzero return code. A GETMAIN was unsuccessful.
3341 X'D0D' An unknown task ID was found in the CNMTAMEL request block.
3342 X'D0E' Incorrect receiver state of receiving session found.
3345 X'D11' Attempt to send a NetView message to authorized receiver using DSIMQS failed.
3346 X'D12' A call to DSILCS macro to free the allocated SWB was not successful.
3347 X'D13' Attempt to get the message size using DSIMBS failed.
3348 X'D14' A call to DUIFSMSG was not successful.
3349 X'D15' Testing of DSIDELAY flag is on.
3351 X'D17' Incorrect parameters passed to service routine DUIFEXPP.
3357 X'D1D' The MSU within an AIFR has garbled data that prevents it from being sent to the
GMFHS address space.
3358 X'D1E' Incorrect parameters passed to service routine DUIFEXPP.
3376 X'D30' Storage overlay has occurred. The storage suffix of the area to be freed is not valid.
3377 X'D31' Logic error in the GET QUEUE routine. A queue element in the queue map indicated
as free contains data.
3378 X'D32' Logic error in the FREE QUEUE routine. A queue entry to be freed was not found in
the queue map.
3380 X'D34' Logic error in the FREE MCB routine. The MCB entry to be freed was not found in
the MCB map.
3381 X'D35' A subtask within GMFHS did not end within 1 minute of the request to end the
address space. The subtask was abnormally ended.
3399 X'D47' An internal error in GMFHS has been detected. Contact IBM Software Support for
3500 X'DAC' The DSIGET macro gives a nonzero return code. The routine was unable to load the
message buffer.
3501 X'DAD' The DSICES macro gives a return code that is not 0 or 20. The DSCP verb name
cannot be found.

Abend Codes

Code Code
3502 X'DAE' The DSIMQS macro gives a nonzero return code. A message to the NetView
authorized operator failed.
3601 X'E11' Neither screen buffer was flagged as active.
3602 X'E12' BNJCGTDA returned with a nonzero return code.
3603 X'E13' A data record that is not valid was detected.
3604 X'E14' BNJCRHTA returned a nonzero return code.
3605 X'E15' BNJCHUPA returned a nonzero return code.
3606 X'E16' BNJCSNDA returned a nonzero return code.
3607 X'E17' DSIGET failure detected.
3608 X'E18' Unknown parameter data detected by BNJP109A or BNJP110A.
3609 X'E19' The NetView DSCP verb is not defined in CNMCMD.
3610 X'E1A' An attempt to send a message using DSIMQS to the authorized operator failed.
3611 X'E1B' Internal processing error detected by BNJP101A.
3780 X'EC4' This is a system abend code. This abend is not an error; it is a normal result. If a
system recovery routine is in control (for example, for the consoles component) a
dump might be produced. These are some of the situations that can result in a
X'EC4' abend:
• OMVS was not started.
• VOST timeouts (for example, SNMP timeouts during resolver calls, or agent not
responding).
• NetView operator logoff hangs.
• The STOP FORCE command was issued against a task in the NetView address
space (MVS) to force the target task to stop.
• As the final step of NetView CLOSE IMMED processing, the abend was issued
against remaining tasks.
Note: CLOSE STOP is the recommended method to end the NetView program.
3994 X'F9A' The DSIMQS macro gives a nonzero return code. A message to the authorized
NetView operator failed.
3995 X'F9B' The DSIMBS macro gives a return code not equal to 0, 4, or 12. The NetView
program cannot construct a message.
3997 X'F9D' The DSIGET macro failed to obtain storage for the DSX.
3998 X'F9E' The DSIMQS macro gives a nonzero return code. A message to the NetView
authorized operator failed.
3999 X'F9F' The DSILCS macro failed for service work block (SWB).
4000 X'FA0' A format error was detected while deblocking the logical records within a
temporary database physical record.
4001 X'FA1' AAUCLODA cannot find the current panel hierarchy entry name in the node table,
and issued a return code of 4.

Abend Codes

Code Code
4002 X'FA2' There is no primary segment address in the page number table of the hierarchy
table.
4003 X'FA3' DSIGET was unable to obtain storage for a temporary record buffer.
4004 X'FA4' DSIGET was unable to obtain storage for a temporary record buffer.
4005 X'FA5' Module AAUSPOOL did not find the page identifier PGBN when attempting to free
storage. This might be caused by a bad pointer passed to AAUSPOOL.
4006 X'FA6' DSIMQS failed.
4007 X'FA7' DSIGET was unable to obtain storage for the NetView control block ADX.
4008 X'FA8' The NetView display panel size (PDXDVSIZ) is less than 21 lines, or NetView
termination was in progress while attempting to enter the session monitor. The
display panel size for the NetView program must be at least 21 (24 minus 3) lines.
4009 X'FA9' DSIGET was unable to obtain storage for a send or default receive control queue
element, or for a default send or receive buffer.
4010 X'FAA' An unrecoverable full-screen panel failure occurred. One possible cause for this is
entering NLDM X at a terminal that does not have extended data support.
4011 X'FAB' DSIGET was unable to obtain enough storage for a temporary buffer.
4012 X'FAC' DSICES was unable to obtain temporary work storage.
4013 X'FAD' AAUCGTDA cannot get a record and issued a return code greater than 4.
4015 X'FAF' The page number was not found in the buffer.
4017 X'FB1' No NetView control block SWB was provided by NetView macro DSILCS.
4018 X'FB2' Abend caused by any one of the following:
• Because of an incorrect SYSGEN, a PIU that is too large is sent to the terminal.
• NLDM X is entered from a terminal that does not have extended data support.
Use NLDM instead of NLDM X.
• A permanent I/O error.
No dump is provided for this abend.
4019 X'FB3' AAUMHTM cannot create a required session monitor hash table during
initialization. The most probable cause is insufficient memory.
4020 X'FB4' DSIGET was unable to obtain storage for the AAUTDIB pool.
4021 X'FB5' Both screen buffers are active.
4022 X'FB6' AAUCGTDA cannot get a record and issued a return code greater than 4.
4023 X'FB7' AAUMGTD failed while trying to get the next logical data record because a bad
record identification was retrieved.
4024 X'FB8' AAUCRHTA failed to reset the hierarchy table and issued a nonzero return code.
4025 X'FB9' AAUCHUPA failed to update the hierarchy table and issued a nonzero return code.
4026 X'FBA' AAUCSNDA issued a nonzero return code because of a DSIMQS failure.
4027 X'FBB' DSIGET was unable to obtain storage for a temporary record buffer.

Abend Codes

Code Code
4031 X'FBF' There is a slot in the output buffer that is not valid.
4033 X'FC1' A named storage area was not found.
4036 X'FC4' The address of the presentation services module to receive control is unresolved in
the node table.
4047 X'FCF' AAUCMBSA cannot retrieve a message and issued a nonzero return code.
4048 X'FD0' AAUCHUPA failed to update the hierarchy table and issued a nonzero return code.
4050 X'FD2' There is no space in the NetView SCT control block for a verb.
4051 X'FD3' DSIGET failed during PSCP initialization.
4052 X'FD4' AAUPCPEX failed to load.
4053 X'FD5' A named storage area was not found.
4064 X'FE0' Session monitor control block corruption detected. Contact IBM Software Support
for programming assistance.
4065 X'FE1' DSILOD failed to load module AAUDMMTA, AAUDBRPA, AAUDBINA, or the failing
load module name is in message AAU083I. Verify that the required modules,
panels, or tables are properly installed. Also, verify that the modules, panels, or
tables can be accessed by the NetView application.
4066 X'FE2' DSIGET cannot obtain storage for AAUTNDB.
4067 X'FE3' This abend is issued from AAUACMPA under one of the following conditions:
• A VSAM record type cannot be found in the table of valid record types.
• The calculated target address of a record expansion operation exceeds the limit
of the buffer.
This abend can be caused by a record on the session monitor VSAM database that
is not valid (or corrupt) or, less likely, a storage overlay of the in-storage record
type table. A dump (IDCAMS print) of the session monitor VSAM database is
required to diagnose this abend (in addition to the abend dump of the NetView
address space.)
4068 X'FE4' Session monitor detected an active session control block chain that is not valid.
Contact IBM Software Support for programming assistance.
4070 X'FE6' A named storage area was not found.
4071 X'FE7' No free ADX control blocks are available.
4072 X'FE8' A function that is not valid was requested for internal queue processing.
4073 X'FE9' Module AAUAHNDA issues this abend when:
• It is driven with a DSRB containing zeroes in both the DSRBUSER and DSRBUBUF
fields.
• An ADX is found with both the ADXLCFLG and ADXVFLG flags set.
4082 X'FF2' AAUZDSPA is not driven under OST or PPT.

4083 X'FF3' The DSIGET macro is unable to obtain enough storage for the DSIMQS buffer.
4085 X'FF5' The DSIMQS macro is unable to obtain enough storage for the DSIMQS buffer or
the format of the buffer is not valid.

Sense Codes

Code Code
4086 X'FF6' The DSICES macro failed to transfer control because it cannot find the task
identification or the verb associated with it. DSICES issued a nonzero return code.
4087 X'FF7' The DSIFRE service routine cannot free storage that was obtained using the
DSIGET macro. DSIFRE issued a nonzero return code.
4088 X'FF8' The control flag of the logical record cannot be found.
4092 X'FFC' The DSIGET macro is unable to obtain enough storage.
4093 X'FFD' DSIGET was unable to obtain storage for NetView control block SCT.
4094 X'FFE' DSIGET was unable to obtain storage for NetView control block ADX.
4095 X'FFF' The DSICES macro cannot find a required session monitor command processor.
DSICES issues a nonzero return code.
Alias Sense Codes

This section lists the global and alias request sense codes.
Global Sense Codes

Table 2. Global Sense Codes
Sense Description of Global Sense Code
Code
0000 Request processed successfully.
1002 Inconsistent length fields in RU or too many specific requests in a single RU.
1003 A request code that is not valid is in network services (NS) header.
0812 Insufficient resources to process request.
FFFF Internal system failure.
Specific-Request Sense Codes

Table 3. Specific-Request Sense Codes
Sense Description of Sense Code
Code
0000 Request processed successfully.
0004 Associated network ID for name to be translated is not specified or is not valid.
0008 Name type specified in request is not valid.
000C Name length specified in request is not valid.
0014 No table exists for the origin network ID for the name.
0018 No table entry exists within the origin network table for specified name.
001C No table entry exists within the origin network table for combination of input name and
destination network ID.

Sense Codes
Table 3. Specific-Request Sense Codes (continued)

Sense Description of Sense Code
Code
0020 No table exists for the destination of name network ID.
0024 Specific request entry length is too small.
LUC Conversation Request Service Return Codes and Sense Codes

Table 4 on page 925 lists and describes LUC conversation request service return codes displayed in
messages DUI170E, DUI172E, DUI173E, DUI175E, and DUI176E.
Table 4. LUC Conversation Request Service Return Codes

Retur Description of Return Code
n
Code
X'02' CNM DATA TASK IS NOT AVAILABLE
X'04' SESSION IS NOT AVAILABLE
X'06' RESOURCES/STORAGE UNAVAIL
X'08' RESOURCE ID INCORRECT
X'0C' PENDING REQUEST NOT COMPLETE
X'10' DEALLOCATE NORMAL
X'14' DEALLOCATE ABEND: MAPPING OF INBOUND FMH7 SENSE CODES 08640000, 08640001,
AND 08640002
X'18' DEALLOCATE PENDING
X'1C' CONVERSATION STATE ERROR
X'20' INCOMPLETE LL SENT
X'24' TPN DEFINED-NO TRUNCATION: MAPPING OF INBOUND FMH7 SENSE CODE 08890000
X'28' TPN DEFINED-NO TRUNCATION: MAPPING OF INBOUND FMH7 SENSE CODE 08890001
X'2C' SVC DEFINED-NO TRUNCATION: MAPPING OF INBOUND FMH7 SENSE CODE 08890100
X'30' SVC DEFINED-TRUNCATION: MAPPING OF INBOUND FMH7 SENSE CODE 08890101
X'34' ALLOCATION ERROR: MAPPING OF INBOUND FMH7 SENSE CODES 10086021, 10086031,
10086032, 10086034, 10086041, 10086042, 10086043, 084C0000, 080F6051, 10086044
X'36' TPNAME NOT AVAIL - RETRY REQUEST: MAPPING OF INBOUND FMH7 SENSE CODE 084B6031
X'FO' SYSTEM ERROR
X'FF' REQUEST NOT VALID
Use the SENSE command to obtain descriptions of the sense codes listed in Table 4 on page 925. See
NetView online help for information about the SENSE command.
Table 5 on page 926 lists and describes LUC macro failure return codes displayed in messages
DUI171E, DUI172E, and DUI174E.

Code Points
Table 5. LUC Macro Failure Return Codes

Retur Description of Return Code
n
Code
X'04' INSUFFICIENT STORAGE
X'08' REPLPRC IS NOT VALID
X'0C' LUC FUNCTION NOT AVAILABLE
X'10' SEND DATA BUFFER LENGTH < = 0
X'14' RECEIVE DATA BUFFER LENGTH < = 0
Use the SENSE command to obtain descriptions of the sense codes listed in Table 5 on page 926. See
NetView online help for information about the SENSE command.
Generic Alert Code Points

This section contains a list of the generic alert code points that the NetView program provides. The code
points are divided according to the subvector or subfield that carries the code point.
If you want information Refer to

On the code points provided by the NetView Systems Network Architecture Formats
program and the generic alert architecture
On defining your own NetView code points IBM Z NetView Customization Guide
Code Point Format

Some code points have qualifier or product set identifier information embedded within the code point
text. The position of the qualifier or product set identifier is marked by a $ within the text.
Explanation of Code Point Formats

These alerts are formatted as code points and text. The code point is a 1- or 2-byte hexadecimal value,
unique to each text. The text is the message displayed on the panel.
Resource Types (X'05')

The X'05' common subvector flows in management services units (MSUs) to communicate resource
names between MS components in nodes. When flowing in an MSU to a focal point, the Hierarchy/
Resource List (HRL) includes the names of the resources of the domain hierarchy for the affected
resource. The HRL containing the complete domain hierarchy is built from configuration knowledge in the
control point, the transmission header, and, if present in the NMVT for which this CP-MSU is being sent,
data from the HRL (containing a partial domain hierarchy) or the SNA address list (X'04') subvector, or
both.
The HRL subvector also carries the hierarchy of control points that received, processed, and forwarded a
CP-MSU, and, in some cases, the names of one or more resources; for example, session partners logically
associated with the reported hierarchy.
To view a listing of both the displayed text for the code point (1–4 characters) and the actual meaning of
the abbreviation, access member BNJRESTY in data set BNJPNL2.

On the format of code point 05 Systems Network Architecture Formats

Code Points
Recommended Actions (X'81')

The X'81' subfield has unique recommended action codes. This subfield contains code points for stored
text describing recommended actions to be taken to rectify an alert condition.
text. To view a listing of Recommended Actions (X'81'), access member BNJ81TBL in data set BNJPNL1.

On customizing recommended action panels IBM Z NetView Customization Guide
On the format of the X'81' subfield Systems Network Architecture Formats
Detail Data (X'82')

The X'82' subfield contains product-specific detailed data to be displayed at an alert receiver. To view
Detail Data (X'82'), access member BNJ82TBL in data set BNJPNL1.

Detail Data (X'85')

The X'85' subfield contains product-specific detailed data to be displayed at an alert receiver. To view
Detail Data (X'85'), access member BNJ85TBL in data set BNJPNL1.

Actual Actions (X'86')

The X'86' subfield contains actual actions data. These major vectors are logged to the hardware monitor
database. To view Actual Actions (X'86'), access member BNJ86TBL in data set BNJPNL1.

Generic Alert Data/Resolution Data (X'92')

The X'92' subvector transports alert information in the form of code points that correspond to strings of
text stored at the alert receiver. It also transports an alert ID number that uniquely identifies a particular
alert.
The X'92' subvector can have two versions of message text as follows:
• Full version message text
• Abbreviated version message text
The abbreviated version of message text appears on the Alerts panel. The full version of the message text
appears on the Detail panel. To view Generic Alert Data/Resolution Data (X'92'), access member
BNJ92TBL in data set BNJPNL1.

On the format of the X'92' subvector Systems Network Architecture Formats

Code Points
Probable Causes (X'93')

The X'93' subvector contains one or more code points denoting probable causes of the alert condition.
The probable causes appear in order of decreasing probability.
The X'93' subvector can have two versions of message text as follows:
• Full version message text
• Abbreviated version message text
The abbreviated version of message text appears on the Alerts panel. The full version of the message text
appears on the Detail panel. To view listing of Probable Causes (X'93'), access member BNJ93TBL in data
set BNJPNL1.

User Causes (X'94')

The X'94' subvector transports code points for stored text detailing the probable user causes for the alert
condition and the recommended actions to be taken in connection with these causes. This subvector can
also transport additional detailed data to be inserted into the text, or indexed by the user cause or the
recommended action code points, or both.
text. To view a listing of User Causes (X'94'), access member BNJ94TBL in data set BNJPNL1.

Install Causes (X'95')

The X'95' subvector transports code points for stored text detailing the probable install causes for the
alert condition and the recommended actions to be taken in connection with these causes. This subvector
can also transport additional detailed data to be inserted into the text, or indexed by the install cause or
the recommended action code points, or both. An install cause is a condition that results from the initial
installation or setup of some equipment.
To view a listing of Install Causes (X'95'), access member BNJ95TBL in data set BNJPNL1.

Failure Causes (X'96')

The X'96' subvector transports code points for stored text detailing the probable failure causes for the
alert condition and the recommended actions to be taken in connection with these causes. This subvector
can also transport additional detailed data to be inserted into the text, or indexed by the failure cause or
the recommended action code points, or both.
text. To view a listing of Failure Causes (X'96'), access member BNJ96TBL in data set BNJPNL1.


Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not give you any license to these patents. You can send
license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road

Austin, TX 78758
U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
Programming Interfaces
This publication documents information that is NOT intended to be used as Programming Interfaces of
IBM Z NetView.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml .
Adobe is a trademark of Adobe Systems Incorporated in the United States, and/or other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or
both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and service names might be trademarks of IBM or other companies.
Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies
or other technologies to collect product usage information, to help improve the end user experience, to
tailor interactions with the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings can help enable you to
collect personally identifiable information. If this Software Offering uses cookies to collect personally
identifiable information, specific information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect personally identifiable
information.
If the configurations deployed for this Software Offering provide you as customer the ability to collect
personally identifiable information from end users via cookies and other technologies, you should seek
your own legal advice about any laws applicable to such data collection, including any requirements for
notice and consent.

For more information about the use of various technologies, including cookies, for these purposes, See
IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://
www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and Other Technologies” and
the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/
software/info/product-privacy.
Notices 931
IBM®
GC27-2857-08

Messages and Codes v2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Messages and Codes v2

Uploaded by

Copyright:

Available Formats

IBM Z NetView

Messages and Codes

About this publication............................................................................................v

Chapter 1. DUI Prefix Messages............................................................................. 1

Chapter 2. DWO Prefix Messages....................................................................... 143

Chapter 3. EJN Prefix Messages......................................................................... 289

Chapter 4. EKG Prefix Messages.........................................................................291

Chapter 5. EKGK Prefix Messages...................................................................... 365

Chapter 6. EKGV Prefix Messages...................................................................... 369

Chapter 7. EZL Prefix Messages......................................................................... 381

Chapter 8. FKV Prefix Messages......................................................................... 459

Chapter 9. FKX Prefix Messages.........................................................................489

Chapter 10. FLB Prefix Messages....................................................................... 521

Chapter 11. FLC Prefix Messages....................................................................... 587

Chapter 12. FLCI Prefix Messages...................................................................... 637

Chapter 15. GMFHS Method Error Messages....................................................... 855

IBM Z NetView library

© Copyright IBM Corp. 1997, 2019 v

vi IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Terminology in this Library

Using IBM Z NetView online help

About this publication vii

Tivoli user groups

viii IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Conventions used in this publication

Operating system-dependent variables and paths

About this publication ix

Marks the beginning of the command syntax.

Marks the end of the command syntax.

Indicates that the command syntax is continued on the next line.

Indicates that a statement is continued from the previous line.

Punctuation and parentheses

x IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Required syntax elements

Optional syntax elements

Default keywords and values

About this publication xi

Multiple operands or values

Syntax that is longer than one line

xii IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Explanation DUI101I NETCONV COMMAND PROCESSED

© Copyright IBM Corp. 1997, 2019 1

DUI103E NETCONV START COMMAND

Explanation System action

System action DUI107I A DUPLICATE NETCONV START

2 IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

• The operator who issued the stop command did not

Explanation Message Variables

The operator station task (OST) that issued the luname

Chapter 1. DUI Prefix Messages 3

4 IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

Chapter 1. DUI Prefix Messages 5

System programmer response 4. Issue NETCONV ACTION=LIST OPID=ALL to

System action Operator response

Operator response System programmer response

6 IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

All LU 6.2 connections to the data server workstation

System programmer response DUI150E ERROR IN 'initmem' AT RECORD

luname Examine the member or file named in the message.

DUI125I OPERATOR operatorid IS NOT DUI152I VTAM APPCCMD MACRO appccmd

Chapter 1. DUI Prefix Messages 7

System action System action

8 IBM Z NetView: Messages and Codes Volume 2 (DUI-IHS)

System programmer response