System Automation for z/OS Messages and Codes

System Automation for z/OS Messages and Codes
System Automation for z/OS
IBM
Messages and Codes
Version 3 Release 5
SC34-2719-00
System Automation for z/OS
IBM
Messages and Codes
Version 3 Release 5
SC34-2719-00
Note
Before using this information and the product it supports, read the information in Notices.
Edition Notes
This edition applies to IBM Tivoli System Automation for z/OS (5698-SA3) Version 3 Release 5, an IBM licensed
program, and to all subsequent releases and modifications until otherwise indicated in new editions.
This edition replaces SC34-2648-00.
|
IBM welcomes your comments. You may forward your comments electronically, or address your comments to:
IBM Deutschland Research & Development GmbH
Department 3282
Schoenaicher Strasse 220
71032 Boeblingen
Germany
FAX: (Germany): 07031 16-3456
FAX: (Other countries): +49 7031 16-3456
Internet e-mail: s390id@de.ibm.com
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright IBM Corporation 1996, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . v
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Accessibility . . . . . . . . . . . . vii
Using assistive technologies . . . . . .
Keyboard navigation of the user interface .
.
.
.
.
. vii
. vii
How to send your comments to IBM . . ix
About this publication . . . . . . . . xi
Who Should Use This Publication .
How to Use This Publication. . .
Where to Find More Information .
The System Automation for z/OS
Related Product Information . .
. . .
. . .
. . .
Library
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xi
xi
xi
xi
xi
Chapter 1. About System Automation for
z/OS Messages. . . . . . . . . . . . 1
Format of System Automation for z/OS Messages .
Message Text . . . . . . . . . . . . .
Who Receives Messages . . . . . . . . .
Displaying Notification Operator Settings. . .
Message Classes . . . . . . . . . . . .
MVS Descriptor Codes . . . . . . . . . .
.
.
.
.
.
.
1
2
2
2
3
4
Chapter 2. Messages AOF000I to
AOF969I. . . . . . . . . . . . . . . 5
Chapter 3. Messages AOFS000I to
AOFS820I . . . . . . . . . . . . . 107
Chapter 4. Messages EVE120I to
EVE842E (CICS Automation) . . . . . 117
Error Codes .
.
.
.
.
.
.
.
.
.
.
.
.
. 121
Chapter 7. Messages HSAH001I to
HSAL6999I . . . . . . . . . . . . 139
Chapter 8. Messages HSAM1000I to
HSAM5411I . . . . . . . . . . . . 151
Chapter 9. Messages IHVA100I to
IHVZ760. . . . . . . . . . . . . . 173
Chapter 10. Messages ING001I to
INGY1337I . . . . . . . . . . . . . 229
Chapter 11. Messages ISQ001I to
ISQ901I . . . . . . . . . . . . . . 323
Chapter 12. Messages ISQX998I and
ISQX999I . . . . . . . . . . . . . 385
Chapter 13. Messages ISQtt001I to
ISQtt0723I . . . . . . . . . . . . . 387
Appendix A. Return Codes, Status
Codes, and Reason Codes . . . . . 405
I/O Operations Return Codes . . . . . . . .
I/O Operations Status Codes for a Dynamic Switch
I/O Operations Reason Codes . . . . . . . .
Reason Codes Associated With Several Return
Codes . . . . . . . . . . . . . . .
Reason Codes Associated With RC=0 . . . .
Reason Codes Associated With RC=4 or RC=8
Reason Codes Associated With RC=12 . . . .
Reason Codes Associated With RC=16 . . . .
Reason Codes Associated With RC=20 . . . .
405
405
405
405
407
407
410
410
413
Chapter 5. Messages EVI022I to
EVI844A (IMS automation) . . . . . . 125
Appendix B. Abend Codes and
Reason Codes Issued By the
Automation Manager . . . . . . . . 415
Chapter 6. Messages EVJ000I to
EVJ440I (TWS Automation) . . . . . 127
Communication DST and Automation Manager
Abend Codes . . . . . . . . . . . .
Codes Posted to TWS by TWS Automation
.
.
. 137
Appendix C. Response Messages,
Error Strings, Condition Codes. . . . 417
Response Messages (AOFA0000–AOFA0099) .
Asynchronous Response Messages
(AOFA0100–AOFA0999) . . . . . . . .
Response Messages (AOFB0000-AOFB0099) .
Asynchronous Response Messages
(AOFB0100-AOFB0999) . . . . . . . .
Condition Codes . . . . . . . . . .
Hardware Communication Task Condition
Codes "00B00xxx" . . . . . . . . .
© Copyright IBM Corp. 1996, 2014
. 415
.
. 417
.
.
. 425
. 429
.
.
. 444
. 445
.
. 445
iii
Data Exchange Services "0B100xxx" . . .
Command Services "0B200xxx" . . . .
Internal Transport Services "0Bx00xxx" . .
Ensemble HMC API Exchange Services
Condition Codes . . . . . . . . .
Ensemble Communication Task Condition
Codes "00B600xxx . . . . . . . . .
.
.
.
. 450
. 453
. 455
Appendix E. Automation Manager
Reason Codes . . . . . . . . . . . 471
.
. 459
Appendix F. Sysplex Communication
Services Return and Reason Codes. . 475
.
. 462
Appendix D. Sense Codes, Hardware
Object Status Summary . . . . . . . 467
Sense Codes . . . . . . . .
Hardware Object Status Summary
iv
.
.
.
.
.
.
.
.
.
.
System Automation for z/OS Messages and Codes:
. 467
. 468
Appendix G. End-to-End Automation
Adapter Messages . . . . . . . . . 479
Glossary . . . . . . . . . . . . . 489
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 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
USA
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 Deutschland Research and Development GmbH
Department 3248
Schoenaicher Strasse 220
D-71032 Boeblingen
Federal Republic of Germany
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
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 may 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.
© Copyright IBM Corp. 1996, 2014
v
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.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
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.
Trademarks
The following terms, used in this book, are trademarks of the IBM Corporation in
the United States or other countries:
vi
CICS/ESA
DataPower
DFSMS/MVS
BladeCenter
CICSPlex®
DB2®
ESCON
FFST/2™
IMS™
MVS™
OS/390®
PowerVM
RACF®
S/390®
System/390®
VM/ESA
z/OS®
z9
FICON®
IMS/ESA®
NetView
POWER
PR/SM™
System x
SP
Tivoli®
VSE/ESA
z/VM
zEnterprise
System Automation for z/OS Messages and Codes:
CICS®
Current
DFS
First Failure Support
Technology/2™
IBM
MQSeries®
OMEGAMON
POWER7
PS/2
System z
Sysplex Timer
Tivoli Enterprise Console®
VTAM®
z10
zSeries
Accessibility
Accessibility features help users with physical disabilities, such as restricted
mobility or limited vision, to use software products successfully. System
Automation for z/OS supports several user interfaces. Product functionality and
accessibility features vary according to the interface.
The major accessibility features in this product enable users in the following ways:
v Use assistive technologies such as screen reader software and digital speech
synthesizer, to hear what is displayed on screen. Consult the product
documentation of the assistive technology for details on using those technologies
with this product and screen magnifier software
v Operate specific or equivalent features using only the keyboard
v Magnify what is displayed on screen.
The product documentation includes the following features to aid accessibility:
v All documentation is available to both HTML and convertible PDF formats to
give the maximum opportunity for users to apply screen-reader software
v All images in the documentation are provided with alternative text so that users
with vision impairments can understand the contents of the images.
Using assistive technologies
Assistive technology products, such as screen readers, function with the user
interfaces found in z/OS. Consult the assistive technology documentation for
specific information when using such products to access z/OS interfaces.
Keyboard navigation of the user interface
Users can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/E
Primer, z/OS TSO/E User's Guide, and z/OS ISPF User's Guide Vol 1 for information
about accessing TSO/E and ISPF interfaces. These guides describe how to use
TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PF
keys). Each guide includes the default settings for the PF keys and explains how to
modify their functions.
© Copyright IBM Corp. 1996, 2014
vii
viii
System Automation for z/OS Messages and Codes:
How to send your comments to IBM
We appreciate your input on this publication. Feel free to send us any comments
you might have.
If you have feedback to the manuals
If you have comments on the manuals, like clarity, accuracy, and completeness of
the information, use the following method to send your comments:
Send an email through "Contact Us" at the bottom right of IBM Knowledge Center.
Include the following information:
v The publication title, for example, IBM System Automation for z/OS V3R50
Messages and Codes
v The topic and page number related to your comment
v The text of your comment
If you have a technical problem
Use one of the following feedback methods:
v Contact your IBM service representative
v Call IBM technical support
v Visit the IBM zSeries support web page at www.ibm.com/systems/z/support/
When you send comments to IBM, you grant IBM a nonexclusive right to use or
distribute your comments in any way it believes appropriate without incurring any
obligation to you.
IBM or any other organizations will only use the personal information that you
supply to contact you about the issues that you submit.
© Copyright IBM Corp. 1996, 2014
ix
x
System Automation for z/OS Messages and Codes:
About this publication
This publication contains problem determination information for IBM Tivoli
System Automation for z/OS (SA z/OS). This information includes messages,
return codes, reason codes and status codes.
Who Should Use This Publication
This publication is intended for operators and system programmers of System
Automation for z/OS (SA z/OS).
How to Use This Publication
This publication lists all SA z/OS messages, return codes, and reason codes. The
messages are sorted alphabetically by the first four characters.
Where to Find More Information
The System Automation for z/OS Library
Table 1 shows the information units in the System Automation for z/OS library:
Table 1. System Automation for z/OS Library
Title
Order Number
IBM Tivoli System Automation for z/OS Planning and Installation
SC34-2716
IBM Tivoli System Automation for z/OS Customizing and Programming
SC34-2715
IBM Tivoli System Automation for z/OS Defining Automation Policy
SC34-2717
IBM Tivoli System Automation for z/OS User's Guide
SC34-2718
IBM Tivoli System Automation for z/OS Messages and Codes
SC34-2719
IBM Tivoli System Automation for z/OS Operator's Commands
SC34-2720
IBM Tivoli System Automation for z/OS Programmer's Reference
SC34-2748
IBM Tivoli System Automation for z/OS Product Automation Programmer's
Reference and Operator's Guide
SC34-2714
IBM Tivoli System Automation for z/OS TWS Automation Programmer's and SC34-2749
Operator's Reference Guide
IBM Tivoli System Automation for z/OS End-to-End Automation Adapter
SC34-2750
IBM Tivoli System Automation for z/OS Monitoring Agent Configuration and SC34-2751
User's Guide
SA z/OS Home Page:
For the latest news on SA z/OS, visit the SA z/OS home page at:
http://www-03.ibm.com/software/products/en/tivosystautoforzos
Related Product Information
|
|
|
For information that supports Tivoli System Automation for z/OS, visit the z/OS
library in IBM Knowledge Center (www.ibm.com/support/knowledgecenter/
SSLTBW/welcome).
© Copyright IBM Corp. 1996, 2014
xi
xii
System Automation for z/OS Messages and Codes:
Chapter 1. About System Automation for z/OS Messages
This book describes System Automation for z/OS messages and codes. It enables
system operators and system programmers to respond to messages appropriately
and efficiently.
Format of System Automation for z/OS Messages
Each System Automation for z/OS system message begins with a unique message
identifier, followed by message text.
In general, the message format is as follows:
XXXynnnt
MESSAGE TEXT
where:
XXX or XXXX
Is the program identifier. It identifies where in System Automation for
z/OS the message originated from. It can have three or four characters
v AOF: System operations
v EVE: CICS-related messages
v EVI : IMS-related messages
v EVJ: TWS-related messages
v HSA: Automation manager
v IHV: I/O operations
v ING: System Automation for z/OS, general parts
v ISQ: Processor operations
Y
Is the SA z/OS component specific identifier.
nnn
Is the message identification number. It is a three-digit or four-digit
number that uniquely identifies each message.
t
Is the message type. It is a letter that helps indicate the purpose of the
message and the type of response required for the message. The message
types are:
© Copyright IBM Corp. 1996, 2014
A
Immediate Action. Requires the system operator to perform an action.
The associated task does not continue until the requested action is
taken.
D
Immediate Decision. Requires the system operator to make a decision
from the available options specified on the message. For example, if a
request for a particular tape drive cannot be satisfied, a system
operator will have to communicate a decision (REPLY “RETRY” or
“CANCEL”) back to the system. The associated task is suspended until
the operator communicates the decision to the system.
E
Eventual Action. Requires eventual action by the system operator. The
associated task continues independent of the operator action.
I
Information. Requires no action. This message is used only for
advisory purposes.
W
System Wait. Requires system operator action immediately. The system
or a major subsystem must be restarted.
1
About System Automation for z/OS Messages
Message Text
The message text provides concise information about an event or condition of
interest to an operator or system programmer. Variable text is used to identify
system components and to provide other detailed information. In this book,
variable text in messages is italicized, for example, job_name.
Some messages include two or more alternate text strings, only one of which is
generated with any single occurrence of the message. The text string generated
depends on the condition the message is reporting. In this book, alternate text
strings are surrounded by braces ({ and }) and are separated by the OR bar (|). For
example: {domain | operator}.
In some cases, messages include optional text. Optional text might or might not
appear with the message, depending on the condition reported by the message. In
this book, optional text is surrounded by brackets ([ and ]).
In some cases " - FROM=sysname" is appended to the message text, where sysname
indicates the system where the message originated. This normally applies where
the message was received by a slave process running on a remote system.
Who Receives Messages
System Automation for z/OS messages are received by automation operators and
notification operators. Automation operators are automated operator tasks or
autotasks that can respond to operating system, subsystem, and network messages
without requiring a human operator.
Notification operators are NetView® operators who receive System Automation for
z/OS notification messages, or messages about actions System Automation for
z/OS either detects or takes. Notification messages are routed to one or more
assigned, logged-on operators. Notification operators can be defined the following
ways:
v Using the Operator Notification panel in the customization dialogs. Refer to IBM
Tivoli System Automation for z/OS Defining Automation Policy for further
information on how to use the customization dialogs.
v Using the INGNTFY command. Refer to IBM Tivoli System Automation for z/OS
User's Guide for more information on how to use the INGNTFY command.
Displaying Notification Operator Settings
If you want to find out who is currently receiving SA z/OS messages, use the
INGNTFY command dialog.
INGNTFY displays a list of notification operators, whether they are logged on and
are receiving messages, and a description of the operator from either the
automation control file or the INGNTFY command dialog.
2
System Automation for z/OS Messages and Codes:
About System Automation for z/OS Messages
AOFKAANT
Domain ID
= IPSNO
Operator ID = OPID
Cmd: A Add
Cmd Operator
--- -------AUTNOTI1
NOTI1
NOYI2
Command ===>
PF1=Help
SA z/OS - Command Dialogs
---------- INGNTFY ----------
C Show/Change settings
System
Log
-------- --AOC4
Y
AOC4
N
AOC4
Y
Rcv
--N
Y
Y
PF2=End
D Delete
Description
----------MSG AOP
Line 1
of 3
Date = 09/15/11
Time = 10:22:29
O Turn OFF msg receiving
Classes
------40 41 42 43 44
80 81 82
PF3=Return
PF9=Refresh
PF6=Roll
PF12=Retrieve
Figure 1. Example DISPNTFY Command Dialog
Notification operators can be logged on without receiving messages if they have
used the INGNTFY command to turn off messages. Refer to IBM Tivoli System
Automation for z/OS User's Guide for further information.
Message Classes
Some messages generated by System Automation for z/OS have a message class.
During automated operations, the class of the message is compared to the class of
each notification operator. Any operator with a class matching the message’s class
receives the message.
To find out which classes of messages are assigned to each operator, use the
customization dialogs. For further information on the customization dialogs, refer
to IBM Tivoli System Automation for z/OS Defining Automation Policy.
The message classes are shown in the following table:
Table 2. Message Classes
Message Class
Description
General Message Classes
0
Errors
1
Debug
Automation Agent-Related Message Classes
40
All Automation agent messages
|
41
No longer used
|
42
No longer used
43
Information
44
Action
45
Status
46
User intervention
50
Critical threshold setting exceeded
Chapter 1. About System Automation for z/OS Messages
3
About System Automation for z/OS Messages
Table 2. Message Classes (continued)
Message Class
Description
51
Frequent threshold setting exceeded
|
52
Infrequent threshold exceeded
|
55
No longer used
60
IMS Automation messages
Automation Manager-Related Message Classes
|
80
All automation manager messages
81
Intervention required
82
Automation denied
83
Impacted
84
Awaiting automation
85
In automation
86
Degraded: Target resources
87
Degraded: All resources
88
Satisfactory: Target resources
89
Satisfactory: All resources
90
SA z/OS Infrastructure/Environment
MVS Descriptor Codes
The System Automation for z/OS AOCMSG common automation routine handles
descriptor codes to assist in the management of the SA z/OS messages at master
consoles (with respect to highlighting, color, and hold/nohold).
The following convention exists:
Type Code
Descriptor Code
W
1
A
2
D
2
I
6
For more details, refer to z/OS MVS System Messages.
4
System Automation for z/OS Messages and Codes:
Chapter 2. Messages AOF000I to AOF969I
AOF000I
MESSAGE message_number ISSUED BUT
DOES NOT EXIST IN MESSAGE
TABLE table - CALL IGNORED
Explanation: System automation attempted to issue a
message, but no text could be found for the message in
the message table.
The variable function shows the PF key that was
pressed.
System action: None.
Operator response: Press a key that is active. For
more information, call help from the panel that this
message appears on.
The variable message_number shows the number of
the message that text was missing for.
System programmer response: None.
The variable table shows the name of the message
library member that the message should have been
found in.
Classes: None.
AOF004I
System action: None.
Operator response: None.
System programmer response: This message indicates
that there might have been a problem installing System
Automation for z/OS. Make sure the message library
SINGNMSG is allocated to DSIMSG DD.
Classes: None.
AOF001I
REQUEST request WAS SUCCESSFUL
FOR entry_type
Explanation: The request for the record has been
completed successfully.
The variable request shows the function performed
on the record.
The variable entry_type shows the function or key of
the record that was processed.
System action: None.
Explanation: The entered command (command) failed
to process. This could be because of an error, or
because the command requested something that was
already in effect. Other messages preceding this one
indicate the reason for the failure.
System action: None.
Operator response: Make sure the proper command
was entered and look for messages preceding this
message to determine the cause of the failure. If you
cannot determine the cause of the failure, contact your
system programmer.
System programmer response: Review the netlog
(which was active at the time the command was
rejected) to see whether a message was routed correctly.
Classes: None.
AOF005I
Operator response: None.
System programmer response: None.
PROCESSING FAILED FOR command
COMMAND
MEMBER member CURRENTLY BEING
action FOR THE CONTROL FILE
Explanation: This is the first line of a multiline
message group.
Classes: None.
v The variable member shows the name of the member
currently being used.
AOF002I
v The variable action shows where the automation
control file resides. It can be one of the following:
END OF MULTILINE MESSAGE
GROUP
Explanation: This message identifies the end of a
multiline message group.
USED
System action: None.
SAVED
Operator response: None.
System programmer response: None.
Classes: None.
AOF003I
function IS NOT ACTIVE
Explanation: An operator dialog issues this message.
An inactive PF key was pressed.
© Copyright IBM Corp. 1996, 2014
The status display is for the current
in-storage member
The status display is for the currently saved
member
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
5
AOF006I • AOF012I
AOF006I
text
The variable keyword shows the keyword that too
many operands were specified for.
Explanation: This message is part of a multiline
message group that begins with message AOF005I.
System action: None.
v The variable text shows detailed information about
an automation control file. It can be one of the
following:
Operator response: Enter the command again, making
sure that the correct number of operands is specified
for the keyword you specify.
BUILT BY name
ON date AT TIME
LOADED BY name ON date at time
CONFIGURATION TOKEN = token
CONFIGURATION DATASET = dataset_name
The variable name shows the name of an operator.
The variable date shows the date the action was
done.
The variable time shows the time the action was
done.
The variable token shows the current
configuration token.
The variable dataset_name shows the name of
current configuration data set.
System action: None.
System programmer response: None.
Classes: None.
AOF010I
WRONG NUMBER OF PARAMETERS
ENTERED
Explanation: Too few or too many parameters were
entered with a command or request.
System action: None.
Operator response: Enter the command or request
again, this time using the right number of parameters.
System programmer response: None.
Classes: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF007I
A RESOURCE TYPE IS REQUIRED
FOR THIS SELECTION
Explanation: A resource type was not entered as a
selection on the prompt screen.
AOF011I
EXPECTING AN ENDING delimiter FOR
parameter
Explanation: The operand was entered without a
closing delimiter.
The variable delimiter shows the character expected
as the delimiter.
The variable parameter shows the parameter that
was in error.
System action: None.
System action: None.
Operator response: Enter the resource type.
System programmer response: None.
Operator response: Enter the command again using
the correct delimiter.
Classes: None.
System programmer response: None.
Classes: None.
AOF008I
A SELECTION MUST BE MADE
Explanation: An operator dialog issues this message.
This message indicates that you must make a selection
on the prompt screen.
System action: None.
Operator response: Make a selection on the prompt
screen. For more information, call help from the panel
that this message appears on.
System programmer response: None.
Classes: None.
AOF012I
message_ID message_text
Explanation: General purpose message entry.
Specifically used for message forwarding of messages
from users or other components. The AOF012I message
identifier is not displayed to an operator who receives
this message.
The variable message_ID shows the message
identifier of the forwarded message.
The variable message_text shows the message text of
the forwarded message.
System action: None.
AOF009I
MAXIMUM NUMBER OF keyword
OPERANDS EXCEEDED
Explanation: The maximum number of operands
allowed for the keyword identified in this message was
exceeded.
6
System Automation for z/OS Messages and Codes:
Operator response: None.
System programmer response: None.
Classes: None.
AOF013I • AOF020A
AOF013I
SPECIFIED OPERAND operand
INVALID FOR parameter
Explanation: An operand that is not valid was
specified for this parameter.
The variable operand shows the operand that is not
valid.
The variable parameter shows the parameter that
was entered.
AOF017I
EXPECTED PARAMETER(S) MISSING
FOR REQUEST request
Explanation: Required parameters for this request are
missing or null. If a parameter was entered, no operand
was specified.
The variable request shows the request used.
System action: None.
System action: None.
Operator response: Enter the command again using
the correct syntax.
Operator response: Enter the command again using
the correct operands.
System programmer response: None.
System programmer response: None.
Classes: None.
AOF014I
SPECIFIED PARAMETER parameter
INVALID
Explanation: The specified parameter (parameter) is not
valid for this command.
System action: None.
Operator response: Enter the command again using
the correct parameters.
System programmer response: None.
Classes: None.
AOF015I
INVALID DELIMITER OF delimiter
ENCOUNTERED
Explanation: A delimiter that is not valid (delimiter)
was entered for a command.
System action: None.
Operator response: Enter the command again using
the correct syntax.
System programmer response: None.
Classes: None.
|
AOF016I
|
|
Explanation: The function requires at least the
indicated number of rows for displaying the panels.
|
System action: The function is terminated.
|
|
Operator response: Use a terminal that fits the
required screen size and redo the function.
|
System programmer response: None.
|
Classes: None.
Too few screen rows (min. nn required).
Classes: None.
AOF018I
INVALID SEARCH RANGE SPECIFIED
Explanation: The specified starting search range is
greater than the ending search range.
System action: None.
Operator response: Enter the command again using
the correct syntax.
System programmer response: None.
Classes: None.
AOF019I
time: INVALID SYNTAX FOR
COMMAND cmd_name parmstr
Explanation: Command cmd_name was invoked with
invalid syntax on the command line.
The variable time shows the time the error was
generated.
The variable cmd_name is the name of the failing
command.
The variable parmstr is the parameter string passed
to the failing command, where available.
System action: Processing is terminated.
Operator response: If operator initiated, correct and
reissue the command, otherwise contact your system
programmer.
System programmer response: Correct and reissue the
command.
Classes: None.
AOF020A
macro/type REQUEST WAS
UNSUCCESSFUL RC=rc A=xx I=yy FOR
function
Explanation: The program made a macro type request.
The macro was not able to satisfy the request and
returned values for use in problem determination.
These values are displayed in this message.
The variable macro/type shows the request type.
The variable rc shows the return code from the
macro.
Chapter 2. Messages AOF000I to AOF969I
7
AOF021I • AOF028I
The variable xx shows the major return code from a
VSAM request.
The variable yy shows the minor return code from a
VSAM request.
The variable function shows the name of the macro.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the VSAM
return code values to determine the cause of the
problem.
Classes: None.
System programmer response: None.
Classes: None.
AOF025I
SYNTAX ERROR FOR command
Explanation: A syntax error was encountered in the
command that was entered.
System action: None.
Operator response: Correct the command syntax and
reissue the command.
System programmer response: None.
Classes: None.
AOF021I
CONFLICTING PARAMETERS
parameters SPECIFIED for command
Explanation: An invalid combination of parameters
was specified for command. The variable parameters lists
the conflicting parameters. The variable command shows
the name of the issued command.
System action: None.
Operator response: Enter the command again with a
valid combination of parameters
System programmer response: None
Classes: None.
AOF026I
module DETECTED A VERSION
MISMATCH. REASON nn
Explanation: Module module detected a version
mismatch.
v The variable module shows the name of the module
that invoked the service.
v The variable rs shows the reason code. Valid reason
codes are:
01 The version of AOFRASFX does not match.
02 The version of a status file record does not
match.
System action: The request is not processed.
AOF022E
MODULE module DETECTED ERROR
IN SERVICE service. RC=rc, RS=rs
Explanation: A service was invoked and returned an
unexpected return code or reason code. This message is
logged in the netlog.
The variable module shows the name of the module
that invoked the service.
Operator response: Check the system setup and
reissue the command.
System programmer response: None.
Classes: None.
AOF027I
The variable service shows the name of the service
that was invoked.
The variable rc shows the return code that was
received.
The variable rs shows the reason code that was
received.
THE FOLLOWING SA AUTOMATION
OPERATORS COULD NOT BE
STARTED:
Explanation: This is the first message of a multiline
message group that lists all automation operators that
could not be started.
System action: None.
System action: Processing stops. The message is
logged in the netlog.
Operator response: None.
Operator response: Refer to the documentation of the
service that was invoked for more information.
Classes: None.
System programmer response: None.
Classes: None.
AOF024I
A NULL FIELD WAS ENTERED
System programmer response: None.
AOF028I
automation operator name - NETVIEW
TASK taskname status
Explanation: This message is part of a multiline
message group that begins with message AOF027I.
System action: None.
v The variable automation operator name shows the
name of the SA z/OS automation operator that
could not be started.
Operator response: Correct the command syntax and
reissue the command.
v The variable taskname shows the name of the
NetView task that caused the problem.
Explanation: A null field is not acceptable.
8
System Automation for z/OS Messages and Codes:
AOF029I • AOF032I
v The variable status shows:
– UNDEFINED if the NetView task is currently not
defined.
– INACTIVE if it could not be started.
System action: None.
Operator response: None.
System programmer response: Define the missing
NetView task names or review the netlog for reasons
why it could not be started.
Classes: None.
AOF029I
System action: None.
Operator response: None.
System programmer response: Define the missing
NetView task names (see message AOF028I) or review
the netlog for reasons why it could not be started.
Classes: None.
task_name IS INACTIVE
USAGE util %, LONG LINEAR pred1,
SHORT LINEAR pred2, 1ST ORDER
pred3
Explanation: This message is posted to SDF when
JES2 spool recovery has been initiated and SA z/OS
makes predictions about future spool usage. There are
three different prediction methods:
Long Linear
This method looks at the first data point and
the latest data point, and does a linear
extrapolation to predict how long it will take
for the spool to reach 100% utilization.
DYNAMIC ADD OF SA
AUTOMATION OPERATORS FAILED
Explanation: This message follows the multiline
message group that begins with message AOF027I.
AOF030I
AOF032I
Data points occur if either the pass processor
runs, or a spool recovery initialization message
(HASP050 or HASP355) is received.
Short Linear
This method is like long linear, but is based on
the last two data points.
Short 1st Order
This method takes the last 3 data points,
works out the rate of change between each
pair of consecutive points, then works out the
variation between these two rates of change. It
then extrapolates using this quadratic variation
to predict when the spool will reach 100%
utilization.
Explanation: The called task (task_name) is not active
at this time.
v The variable util shows the current percent utilization
of all active spool volumes.
System action: None.
v The variables pred1, pred2, pred3 are spool usage
predictions. They can have the following values:
Operator response: Start the task by issuing START
TASK=xxxxxxx, where xxxxxxx is:
v AOFTSTS for the status file
System programmer response: None.
Classes: None.
hh:mm:ss
The predicted time for the spool to reach
100% utilization.
NONE Insufficient data points were collected to
make the prediction.
STABLE
There is no change in spool usage between
the data points. Spool usage is neither
increasing nor decreasing.
|
|
AOF031I
|
|
|
Explanation: The message is generated when the
status of the configuration refresh changes. It shows the
actual status of the configuration refresh.
|
|
The variable system shows the system name where the
configuration refresh is processed.
|
|
The variable status shows the actual status of the
configuration refresh.
|
System action: None.
|
Operator response: None.
System action: None.
|
System programmer response: None.
Operator response: None.
|
Classes: None.
System programmer response: None.
Configuration Refresh on 'system' is
'status'.
SAFE
The projected spool usage falls below the
lowest data point rather than reaching 100%
utilization.
DROPPING
The latest data point is lower than the
others.
FULL
The current data point shows 100% spool
utilization.
Classes: None.
Chapter 2. Messages AOF000I to AOF969I
9
AOF035I • AOF058I
AOF035I
MEMBER member I/O ERROR
OCCURRED WHILE PROCESSING
Explanation: An I/O error occurred during processing
of the member identified by the variable member.
System programmer response: Make sure that the
member identified in the message is valid. Add the
member in the DSIPARM concatenation chain or correct
the SDF panel definitions that refer to the erroneous
member.
System action: Processing ends.
Operator response: Make sure the member identified
in the message is valid. If the member identified in the
message is valid, contact your system programmer for
further analysis.
System programmer response: Verify that the member
name exists in the file pointed to by the procedure in
use at the time of the error. Review the netlog being
used at the time of the error to see whether there was a
system error that could have prevented the member
from being found.
Classes: None.
AOF040I
CONTROL FILE INACTIVE
Explanation: A request to the automation policy was
not successful because the automation control file was
not active. This message can also be a response to the
ACF STATUS command.
AOF043I
task IS ACTIVE
Explanation: The task task has been activated.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF044I
task IS TERMINATING
Explanation: The task task is ending.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
System action: None.
AOF045I
Operator response: To activate the automation control
file, specify the ACF REFRESH or the INGAMS
command.
Explanation: The task task has ended.
System programmer response: None.
Operator response: None.
Classes: None.
System programmer response: None.
task TERMINATED
System action: None.
Classes: None.
AOF041I
UNABLE TO FIND entry type
Explanation: The task did not find any data for the
specified entry-type pair.
The variable entry shows the entry field of the
entry-type pair the task tried to locate.
The variable type shows the type field of the
entry-type pair the task tried to locate.
AOF057I
REQUEST FAILED. TIMERID =timer_ID
ALREADY EXISTS
Explanation: An attempt was made to add a timer ID
that already exists.
The variable timer_ID shows the timer ID that
already exists.
System action: None.
System action: None.
Operator response: None.
Operator response: Specify a timer ID that does not
already exist.
System programmer response: None.
Classes: None.
System programmer response: None.
Classes: None.
AOF042I
MEMBER name NOT FOUND
Explanation: SA z/OS attempted to prepare the
member named in the message but could not find it.
The variable name is the name of member that could
not be found.
System action: Processing continues.
Operator response: None.
10
System Automation for z/OS Messages and Codes:
AOF058I
AOFCTMSG ERROR - message_number
Explanation: The status display facility attempted to
issue the message indicated, but no text could be found
for the message in its internal message table
(AOFCTMSG).
The variable message_number shows the number of
the message that text was missing for.
AOF059I • AOF078I
System action: None.
Operator response: Contact your system programmer.
System programmer response: Determine what
operation was being performed when the error
occurred, and note the message number. This
information should be forwarded to your IBM product
support contact.
Classes: None.
AOF059I
REQUEST FOR name LOCKS TO BE
CLEARED WAS CANCELED
Explanation: The request to clear locks was canceled.
No locks were cleared.
The variable name shows the subsystem name
whose locks were to be cleared.
System action: No locks were cleared.
Operator response: None.
System programmer response: None.
Classes: None.
AOF060I
OPERATOR ID operator_ID NOT
FOUND
Explanation: The operator ID identified in this
message (operator_ID) was not found.
AOF069I
Explanation: This message is given in conjunction
with a subsequent error message that explains what is
incorrect. It shows the SDF panel statement that is
incorrect.
The variable data identifies the buffer data in error.
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions.
Classes: None.
AOF076I
System programmer response: None.
Classes: None.
AOF064I
time: ident WAITING FOR event
Explanation: Automation is waiting for an event to
complete.
The variable time shows the time the message was
issued.
The variable ident shows the CLIST that issued the
message.
The variable event shows the event the CLIST is
waiting for.
When event is "ENVIRON SETUP EXITS TO FINISH" it
means that the automation initialization-related
processing is suspended. Automation initialization will
not complete until the exits have run.
System action: System automation waits until the
event has completed.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
REPEAT FIND WILL NOT WORK
UNTIL YOU HAVE ISSUED A FIND
Explanation: To use the repeat function a find
command must have been entered previously.
System action: The requested command is not
performed.
Operator response: Specify a find command first, for
example, FIND abc.
System programmer response: None.
Classes: None.
AOF077I
System action: None.
Operator response: Specify the operator ID again.
data
USE P OR N TO SPECIFY FIND
DIRECTION
Explanation: An invalid value for the find direction
has been specified. P and N are valid values.
System action: The requested command is not
performed.
Operator response: Specify P (previous) or N (next)
for the direction of the FIND command, for example,
FIND abc N.
System programmer response: None.
Classes: None.
AOF078I
subsys SPOOL RECOVERED TO
BELOW nn%, text
Explanation: System automation SPOOL recovery was
successful.
The variable subsys shows the name of the
subsystem.
The variable nn% shows the spool percentage.
The variable text shows either RECOVERY
STOPPED or RECOVERY DONWGRADED TO
SHORT.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Chapter 2. Messages AOF000I to AOF969I
11
AOF081I • AOF087I
Classes: 40, 43.
AOF081I
SECURITY FACILITY IS NOT ACTIVE
Explanation: A request or function was not
performed, because the security facility was not active.
System action: None.
Operator response: Take steps to activate the security
facility. Contact your system programmer.
System programmer response: Determine why the
security facility was not active and take steps to ensure
that it is available when necessary.
AOF085I
PRESS PF5 TO SAVE OR PF3 AGAIN
TO IGNORE CHANGES
Explanation: Function key PF3 has been issued to
leave a panel without having saved temporary
modifications of the displayed data. The requested
function is rejected.
System action: The requested function is not
performed.
Operator response: Follow the instruction of the
message.
System programmer response: None.
Classes: None.
AOF086I
AOF082I
SAVE REQUEST REJECTED –
ORIGINAL DATA HAS BEEN
MODIFIED
Explanation: A request to save changed data was
issued. However, the original data that you have
changed has in the meantime been modified by another
process and is no longer up-to-date. The request is
therefore rejected.
System action: The requested function is not
performed.
Operator response: Refresh the displayed data and
redo the changes based on the new data.
time : phase DEFINITIONS TO subsystem
RESTORED BY task
Explanation: This message is written to the NetView
log when previously stored start or stop definitions to
an application have been restored after they have been
modified.
The variable time shows the time this message was
generated.
The variable phase shows whether START or STOP
definitions have been modified.
The variable subsystem shows the name of the
resource.
The variable task shows the name of the task that
requested the function.
System programmer response: None.
System action: Processing continues.
Classes: None.
Operator response: None.
AOF083I
FIELD field_name EXCEEDS THE
ALLOWABLE FIELD LENGTH
Explanation: The field identified in this message
(field_name) is too long.
System action: None.
Operator response: Determine the correct length for
the field and try the operation again.
System programmer response: None.
Classes: None.
AOF084I
PARAMETERS EXCEED THE
MAXIMUM LENGTH
Explanation: The command could not be processed
because the parameters exceeded the maximum length.
System action: None.
Operator response: Try to reduce the length of the
parameters.
System programmer response: None.
Classes: None.
12
System Automation for z/OS Messages and Codes:
System programmer response: None.
AOF087I
action REQUEST REJECTED - phase IN
PROGRESS
Explanation: A request was issued to save modified
start or stop definitions for an application or to discard
changes by resetting the previously loaded definitions.
v The variable action shows whether a save or reset
function has been requested.
v The variable phase shows the reason why the
requested function was rejected:
START
A startup of the application is in progress.
STOP
A shutdown of the application is in progress.
INITIALIZATION
SA z/OS is not initialized.
System action: The requested function is not
performed.
Operator response: Reissue the request either after the
start or stop of the application has completed or after
SA z/OS has initialized.
System programmer response: None.
AOF088I • AOF098I
AOF088I
command: COMMAND ONLY
ALLOWED IN FULLSCREEN MODE
Explanation: A command was issued that is only
allowed in fullscreen mode. The command is rejected
because the executing task does not support fullscreen
mode.
The variable command shows the command that was
issued.
System action: None.
Operator response: None.
System programmer response: None.
AOF089I
time : phase DEFINITIONS TO subsystem
MODIFIED BY task
Explanation: This message is written to the NetView
log when start or stop definitions to an application
have been modified during runtime.
System programmer response: None.
Classes: None.
AOF095I
function_name FUNCTION
SUCCESSFULLY COMPLETED
Explanation: An operator dialog issues this message.
Processing of a function called by a command has been
successfully completed.
The variable function_name identifies the function
that processing has been completed for.
System action: None.
Operator response: None. For more information about
this message, call help from the panel that this message
appears on.
System programmer response: None.
Classes: None.
The variable time shows the time this message was
generated.
AOF096I
The variable phase shows whether START or STOP
definitions have been modified.
Explanation: You are expected to enter a command.
The variable subsystem shows the name of the
resource.
The variable task shows the name of the task that
requested the function.
A COMMAND MUST BE SPECIFIED
System action: None.
Operator response: Enter a command.
System programmer response: None.
Classes: None.
System action: Processing continues.
Operator response: None.
System programmer response: None.
AOF090I
IPLDATE= date, IPLTIME= time
Explanation: This message shows the date and time of
the last initial program load (IPL).
AOF097I
A RESOURCE NAME IS REQUIRED
FOR THIS SELECTION
Explanation: You made an operator dialog panel
selection that requires a resource name, but you did not
enter a resource name.
System action: None.
System action: None.
Operator response: Enter a resource name. For more
information, request help for this operator dialog panel.
Operator response: None.
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
AOF098I
AOF094I
operator_ID IS NOT AUTHORIZED TO
USE INGNTFY COMMAND
Explanation: An operator dialog issues this message.
An operator who is not authorized to use the
INGNTFY command attempted to do so.
The variable operator_ID shows the ID of the
operator who attempted to use the command.
System action: None.
Operator response: If you need more information
about this message, call help from the panel that this
message appears on.
COMMAND FAILED - REFER TO
NETVIEW LOG
Explanation: Processing of a request or function failed
to be completed successfully. The netlog file active at
the time of the failure might contain information
indicating why processing failed.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Review the netlog for
messages related to the request that failed. Determine
the cause of the failure by analyzing these messages. If
there are no related messages, determine whether the
command is still active on the maintenance level that
Chapter 2. Messages AOF000I to AOF969I
13
AOF099I • AOF107I
was active when this message was generated.
AOF103I
Classes: None.
AOF099I
FUNCTION COMPLETED
Explanation: An operator dialog issues this message.
It indicates that processing of the command completed.
If no error message is shown previously, it also
indicates that the function completed successfully.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF100I
time: command COMMAND ISSUED data
Explanation: The request you made has been
processed or has been issued and is processing.
The variable time shows the time this message was
generated.
The variable command shows the name of the
command that failed.
The variable data shows detailed information about
where the command was issued.
CURRENT TIME PAST REQUESTED
TIME time
Explanation: A time that has already passed was
specified. The specified time cannot be processed.
The variable time shows the time specified in the
request.
System action: None.
Operator response: Specify a valid time in the request.
System programmer response: None.
Classes: None.
AOF104I
DEFAULT (IF ANY) IN WHITE, NO
NEED TO ENTER SEL NUMBER
Explanation: On the NNT selection panel, the first
defined session is the default selection for
initiation/termination. It is selected automatically if
you do not enter a selection number.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
System action: None.
Operator response: None.
System programmer response: None.
Classes. 40 43.
AOF105I
DELETE SUCCESSFUL
Explanation: A request to delete is complete.
System action: None.
Operator response: None.
AOF101I
CONFIRMATION RESPONSE IS
REQUIRED
System programmer response: None.
Classes: None.
Explanation: An operator dialog issues this message.
System action: None.
AOF106I
Operator response: For more information, call help
from the panel that this message appears on.
Explanation: An operator dialog issues this message.
System programmer response: None.
Classes: None.
ENTER A SELECTION
System action: None.
Operator response: For more information, call help
from the panel that this message appears on.
System programmer response: None.
AOF102I
CORRECT FIELDS IN ERROR
Classes: None.
Explanation: An operator dialog issues this message.
System action: None.
AOF107I
Operator response: For more information, call help
from the panel that this message appears on.
Explanation: An operator dialog issues this message.
This message is usually displayed after an invalid
command is entered.
System programmer response: None.
Classes: None.
ENTER TO DISPLAY
System action: None.
Operator response: Make a selection from the list
displayed on the panel and press the key designated as
the Enter key.
14
System Automation for z/OS Messages and Codes:
AOF108E • AOF114I
System programmer response: None.
Classes: None.
The variable entry shows the name of the entry that
will be displayed.
System action: None.
AOF108E
ERROR OCCURRED DURING process
PROCESS
Explanation: An error occurred during the process
identified in this message.
The variable process shows the name of the process
during which the error occurred.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Examine other
messages related to the process to identify the error
and its cause.
Classes: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF112I
ACTIVE TYPE= active_type , DESIRED
TYPE= desired_type
Explanation: This message is part of a multiline
message group that begins with message AOF111I.
The variable active_type shows the name of the type
that satisfied the request.
The variable desired_type shows the name of the type
that was requested.
System action: None.
AOF109I
EXITS CANNOT BE ENABLED - EXITS
DO NOT EXIST
Explanation: An attempt was made to enable exits.
Because no exits exist, no action was performed.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF110I
name BEING USED FOR THE
AUTOMATION CONTROL FILE - origin
Explanation: The automation control file member was
either loaded, restored, or refreshed successfully.
Operator response: None.
System programmer response: None.
Classes: None.
AOF113I
DATA IS data
Explanation: This message is part of a multiline
message group that begins with message AOF111I.
The variable data shows the data area of the entry
and type being displayed.
System action: None.
Operator response: None.
System programmer response: None.
v The variable name shows the name of the member
that was loaded.
Classes: None.
v The variable origin shows where the automation
control file came from. It can be:
LOADED from data sets in the DSIPARM
concatenation.
RESTORED using NetView Save/Restore facility.
REFRESHED as for LOADED but from changed
data only.
AOF114I
System action: None.
REQUESTED STATE state FOR
SUBSYSTEM subsystem IS ALREADY
SET
Explanation: An operator dialog issues this message.
The variable state shows the requested state.
The variable subsystem shows the affected
subsystem.
Operator response: None.
System action: None.
System programmer response: None.
Operator response: For more information, call help
from the panel that this message appears on.
Classes: None.
AOF111I
AUTOMATION CONFIGURATION
DISPLAY - ENTRY= entry
System programmer response: None.
Classes: None.
Explanation: This is the first message of a multiline
message group that displays the current automation
configuration.
Chapter 2. Messages AOF000I to AOF969I
15
AOF115I • AOF123D
AOF115I
REQUESTED TIMER timer_identification
WAS CHANGED
Explanation: The requested timer change was made.
The variable timer_identification shows the name of
the timer that was changed.
System action: None.
AOF119I
SELECT ONE PARAMETER THEN
PRESS THE ENTER KEY
Explanation: This message is a prompt for you to
select a parameter.
System action: None.
Operator response: None.
Operator response: Select a parameter and press the
Enter key.
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
AOF116I
AOF121I
REQUESTED TIMERS WERE DELETED
HIT ENTER KEY
Explanation: The request to delete timers was
completed successfully. The timers specified in the
request were deleted.
Explanation: This message is a prompt for you to
press the Enter key.
System action: None.
Operator response: None.
Operator response: Press the key on your keyboard
that performs the Enter function.
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
AOF117I
RETURN CODE return_code RECEIVED
FROM LIST TIMER COMMAND
Explanation: A non-zero return code was generated
during processing of the LIST TIMER command.
Processing of the request is not complete.
The variable return_code shows the return code
generated.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Refer to the
description of the NetView LIST TIMER command in
Tivoli NetView for z/OS Command Reference Vol. 1 for an
explanation of the return code.
Classes: None.
AOF118I
SECOND PARAMETER SHOULD BE
BLANK OR T
Explanation: A non-blank value other than “T” was
specified for the second parameter of the entered
command. This parameter must be blank or have a
value of T.
System action: None.
AOF122I
INVALID CONFIRMATION REQUEST
OF function ENTERED
Explanation: An operator dialog issues this message.
A confirmation request that is not valid was entered.
The variable function shows the request entered.
System action: None.
Operator response: Enter a valid confirmation request.
For more information about this message, call help
from the panel that this message appears on.
System programmer response: None.
Classes: None.
AOF123D
INVALID INPUT -- ENTER
COMMAND, SET COMMAND, T TO
TERMINATE OR I TO INITIATE
Explanation: Data that is not valid was entered.
System action: None.
Operator response: Enter one of the following:
v A valid command
v SET
System action: None.
v T
Operator response: Enter the command again,
specifying valid values for all parameters.
v I
System programmer response: None.
Classes: None.
Classes: None.
16
System Automation for z/OS Messages and Codes:
System programmer response: None.
AOF124D • AOF135I
AOF124D
INVALID INPUT -- ENTER IMS
COMMAND, SET COMMAND OR T
TO TERMINATE
Explanation: Data that is not valid was entered.
System action: None.
Operator response: Enter the data again, making sure
that it is valid.
System programmer response: None.
Classes: None.
AOF125A
INVALID OPERATOR ID - PLEASE
RE-ENTER
from the panel that this message appears on. If the
message is issued during the configuration file load or
refresh then the Entry/Type in the file must be
corrected.
System programmer response: None.
Classes: None.
AOF131I
MISSING OR INVALID parameter
Explanation: A parameter or keyword in the entered
command is missing or is not valid.
The variable parameter shows the parameter or
keyword that is missing or is not valid.
System action: None.
Explanation: An operator ID that is not valid was
entered.
Operator response: Specify valid parameters and
reissue the command.
System action: None.
System programmer response: None.
Operator response: Enter a valid operator ID.
Classes: None.
System programmer response: None.
Classes: None.
AOF132I
NO AUTOMATION FLAGS SET
Explanation: An operator dialog issues this message.
AOF126A
INVALID PASSWORD - PLEASE
RE-ENTER
Explanation: A password that is not valid was
specified.
System action: None.
Operator response: Enter a valid password.
System action: None.
Operator response: For more information, call help
from the panel that this message appears on.
System programmer response: None.
Classes: None.
System programmer response: None.
AOF133I
Classes: None.
Explanation: The information that was requested does
not exist.
AOF129I
System action: None.
INVALID SELECTION
NO ENTRIES HAVE BEEN DEFINED
Explanation: An operator dialog issues this message.
Operator response: None.
System action: None.
System programmer response: None.
Operator response: For more information, call help
from the panel that this message appears on. Choose an
option that is within the valid range.
Classes: None.
System programmer response: None.
Classes: None.
AOF130I
INVALID SUBSYSTEM NAME
invalid_name
Explanation: An operator dialog issues this message.
This message may also be issued during the
automation control file load or refresh.
The variable invalid_name shows the invalid name.
AOF134I
NO FUNCTION WAS SELECTED
Explanation: You did not specify a function.
System action: None.
Operator response: Specify a function.
System programmer response: None.
Classes: None.
AOF135I
NO HELP PANEL IS AVAILABLE
System action: For automation control file load or
refresh the Entry/Type is ignored.
Explanation: Help information was requested when
none is available.
Operator response: For more information, call help
System action: None.
Chapter 2. Messages AOF000I to AOF969I
17
AOF136I • AOF144I
Operator response: None.
System programmer response: None.
Classes: None.
AOF140I
NO TIMERS ARE SCHEDULED
Explanation: No timers are scheduled, so there is
nothing to display.
System action: None.
AOF136I
NO MORE HELP IS AVAILABLE
Explanation: All available help text has been
displayed.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF141I
NUMBER 0 IS NOT VALID
Explanation: The value “0” was specified for the field.
This is not a valid value for the field.
System action: None.
AOF137I
NO NOTIFY OPERATORS DEFINED
Explanation: The request was not performed, because
there are no notify operators.
System action: None.
Operator response: None.
Operator response: Specify a valid value for the field.
System programmer response: None.
Classes: None.
AOF142I
System programmer response: None.
ONLY ONE DATE/DAY MAY BE
SPECIFIED
Classes: None.
Explanation: More than one day or date was
specified. Only one day or date can be accepted.
AOF138I
System action: None.
NO SCHEDULED AUTOMATION
OVERRIDES
Explanation: An operator dialog issues this message.
System action: None.
Operator response: For more information, call help
from the panel that this message appears on.
Operator response: Specify only one day or date.
System programmer response: None.
Classes: None.
AOF143I
System programmer response: None.
ONLY ONE SELECTION IS ALLOWED,
PLEASE RESPECIFY
Classes: None.
Explanation: More than one selection was made. Only
one selection can be accepted.
AOF139I
System action: None.
NO THRESHOLDS DEFINED - AT
LEAST ONE THRESHOLD VALUE IS
REQUIRED
Explanation: No threshold values have been defined.
You must define at least one threshold value.
Operator response: Make only one selection.
System programmer response: None.
Classes: None.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Define at least one
threshold value. For information about defining
threshold values, refer to IBM Tivoli System Automation
for z/OS Defining Automation Policy.
Classes: None.
AOF144I
PARAMETER parameter_name INVALID
Explanation: An operator dialog issues this message.
A parameter that is not valid (parameter_name) was
entered.
System action: None.
Operator response: For more information, call help
from the panel that this message appears on.
System programmer response: None.
Classes: None.
18
System Automation for z/OS Messages and Codes:
AOF145I • AOF152I
AOF145I
PARAMETER MISSING
Explanation: An operator dialog issues this message.
System action: None.
Operator response: For more information, call help
from the panel that this message appears on.
System programmer response: None.
Classes: None.
AOF146I
PARAMETER MUST BE NUMERIC
Explanation: A non-numeric value was entered in a
field that requires a numeric value.
System action: None.
specified in 24-hour-clock format.
System programmer response: None.
Classes: None.
AOF150I
STATISTICS DISPLAY REQUESTED
FOR from_resource THRU to_resource
Explanation: This is the first message in a group of
messages that display statistics from a resource
structure.
The variable from_resource shows the highest
resource name in the resource structure requested to
be displayed.
The variable to_resource shows the lowest resource
name in the resource structure requested to be
displayed.
Operator response: Enter a numeric value for the
field.
System action: None.
System programmer response: None.
Operator response: None.
Classes: None.
System programmer response: None.
Classes: None.
AOF147I
REPLY FAILED - REFER TO
NETWORK LOG
Explanation: The reply failed. The netlog contains
additional information about the failure.
System action: None.
AOF151I
ID= resource , TYPE= type , STATUS=
status
Explanation: This message is part of a multiline
message group that begins with message AOF150I.
Operator response: Contact your system programmer.
The variable resource shows the name of the
resource being displayed.
System programmer response: Make sure the reply
specification is correct. Identify and correct any other
causes of the failure.
The variable type shows the type of resource being
displayed.
Classes: None.
The variable status shows the status of the resource
being displayed.
System action: None.
AOF148I
REPLYID IS NOT VALID, CORRECT
AND RE-ENTER
Operator response: None.
Explanation: The reply ID is not valid.
System programmer response: None.
System action: None.
Classes: None.
Operator response: Enter a valid reply ID.
System programmer response: None.
Classes: None.
AOF149I
REQUEST FAILED. DATE/TIME (date
time) IS INVALID
Explanation: The date or time specified is not valid.
The variable date shows the date specified.
The variable time shows the time specified.
System action: None.
Operator response: Specify a valid date and a valid
time. Make sure that the day you specify is valid for
the month and year you specify, and that the time is
AOF152I
LAST UPDATED BY operator_ID ,
RECORD TYPE= record_type
Explanation: This message is part of a multiline
message group that begins with message AOF150I.
The variable operator_ID shows the ID of the
operator who last updated the record for the
resource.
The variable record_type shows the type of the
record that was updated.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
Chapter 2. Messages AOF000I to AOF969I
19
AOF153I • AOF161I
AOF153I
LAST event_type EVENT: TS= date time ,
TYPE=type
Explanation: This message is part of a multiline
message group that begins with message AOF150I.
System action: None.
Operator response: None.
The variable event_type shows the event type, which
is one of START, AVAIL, STOP, or DOWN. The
event types describe the lifecycle milestones of the
resource.
System programmer response: None.
The variable date time shows the time stamp in the
form mm/dd/yyyy hh:mm:ss.
AOF158I
The variable type shows the start or stop type that is
associated with the event.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF154I
LAST TERMCODE= code
Explanation: This message is part of a multiline
message group that begins with message AOF150I.
The variable code shows the termination (abend)
code.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF155I
OPERATOR NOTIFIED: notify
Explanation: This message is part of a multiline
message group that begins with message AOF150I. This
message indicates whether an operator has been
notified of the current error.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF156I
LAST STATUS CHANGE DATE=
mm/dd/yy, TIME= hh.mm.ss , OPER=
operator_ID
Explanation: This message shows the date and time of
the last status change, and the operator ID at the point
of the status change.
The variables mm, dd, and yy show the month, day,
and year, respectively, of the last status change.
The variables hh, mm and ss show the hour, minute,
and second of the last status change.
20
The variable operator_ID shows the operator ID at
the point of the last status change.
System Automation for z/OS Messages and Codes:
Classes: None.
USER = information
Explanation: Informational message returning up to
20 characters of data.
The variable information shows information by user.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF159I
NO DATA AVAILABLE
Explanation: This message is part of a multiline
message group that begins with message AOF150I.
There is no error data available for the resource.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF160I
ERROR COUNT
DATE
TIME
Explanation: This message is part of a multiline
message group that begins with message AOF150I. This
message provides the headings for the data shown in
message AOF161I.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF161I
nn
mm/dd/yy hh:mm:ss
Explanation: This message is part of a multiline
message group that begins with message AOF150I. This
message shows the current error count (nn) and the
date and time of the last error.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF162I • AOF172I
AOF162I
INVALID SCROLL AMOUNT SPECIFY "HALF", "PAGE", "MAX", OR
A NUMBER
Explanation: An invalid value was entered in the
scroll field.
Operator response: None.
System programmer response: None.
Classes: None.
AOF169I
System action: None.
Operator response: Correct the scroll amount and
retry.
System programmer response: None.
Classes: None.
THE LAST LINE IS ALREADY
DISPLAYED ON THE SCREEN
Explanation: You tried to scroll forward to display
more data on the screen, but there is no more data to
display; the last line of data is already being displayed.
System action: None.
Operator response: None.
AOF163I
LAST THRESHOLD EXCEEDED threshold
Explanation: This message is part of a multiline
message group that begins with message AOF150I. The
last threshold setting for the resource has been
exceeded.
The variable threshold shows the last threshold
setting.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
System programmer response: None.
Classes: None.
AOF170I
THE TOP LINE IS ALREADY
DISPLAYED ON THE SCREEN
Explanation: You tried to scroll backward to display
more data on the screen, but there is no more data to
display; the first line of data is already being displayed.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF165I
REQUEST FAILED. TASK task_name
NOT ACTIVE
Explanation: The task identified in this message must
be active for processing of the request to be completed
successfully. Because this task was not active, the
request failed.
The variable task_name shows the name of the task
that was not active.
System action: None.
Operator response: Contact your system programmer.
Start the task identified by task_name and issue the
original request again.
System programmer response: Determine why the
task identified by task_name was not active and correct
the problem.
Classes: None.
AOF166I
REQUEST FOR number LOCKS TO BE
CLEARED WAS SUCCESSFULLY
COMPLETED
Explanation: A request to clear locks was successful.
The variable number shows the number of locks
cleared.
System action: None.
AOF171I
TIMEOUT OF number SECONDS
EXPIRED
Explanation: Processing of the request was not
completed within the number of seconds shown by this
message.
The variable number shows the number of seconds
taken by processing of the request before processing
was suspended.
System action: Normal system processing proceeds;
processing of the request was suspended.
Operator response: None.
System programmer response: None.
Classes: None.
AOF172I
TIMER ID MUST BE CHANGED FOR
ADD PROCESSING
Explanation: The timer ID was not changed for an
add operation.
System action: None.
Operator response: Specify the timer ID again.
System programmer response: None.
Classes: None.
Chapter 2. Messages AOF000I to AOF969I
21
AOF173I • AOF181I
AOF173I
TIMER SCHEDULED BUT TIMER
DISPLAY FAILED
Explanation: The requested time was set. However, in
an attempt to verify the request by displaying the timer
ID, the NetView LIST TIMER command failed.
System action: None.
Operator response: Verify that your requested timer
was set.
System programmer response: None.
Classes: None.
AOF174I
UNKNOWN ERROR OCCURRED,
REFER TO NETWORK LOG FOR
DETAILS
Explanation: An unexpected return code was received,
indicating an error condition. Additional information
about the error condition can be found in the NetView
log.
Operator response: Select a number that is included
in the selection list.
System programmer response: None.
Classes: None.
AOF179I
REQUEST NOT COMPLETED - WAIT
TIME EXPIRED
Explanation: Processing of the request was not
complete after the length of time specified as the “wait
time.” Processing of the request is suspended. Other
processing continues.
System action: Processing of the request might be
completed after this message is issued or the request is
incomplete.
Operator response: Retry your request or determine
whether it subsequently completes.
System programmer response: None.
Classes: None.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the netlog for
messages related to the request that resulted in the
error condition.
Classes: None.
AOF175I
YOU MUST ENTER YOUR
PASSWORD
Explanation: A password was not entered.
AOF180I
REQUEST NOT COMPLETED BY
command_name COMMAND FAILURE
Explanation: Processing of a request was not
completed because the command identified in this
message failed.
The variable command_name shows the name of the
command that failed.
System action: None.
Operator response: Contact your system programmer.
Operator response: Enter your password.
System programmer response: Check the netlog for
related error messages to determine the reason why the
command failed.
System programmer response: None.
Classes: None.
System action: None.
Classes: None.
AOF176I
YOU MUST ENTER YOUR USER ID
AOF181I
MULTIPLE SELECTIONS NOT
ALLOWED
System action: None.
Explanation: A command entered on the selection line
was interpreted as an attempt to select more than one
option. Only one option can be selected.
Operator response: Enter your user ID.
System action: None.
System programmer response: None.
Operator response: Select one of the options
displayed on the panel and press the key designated as
the Enter key.
Explanation: A user ID was not specified.
Classes: None.
System programmer response: None.
AOF177I
YOUR REQUESTED NUMBER IS NOT
ON THE LIST
Explanation: Your selection number is greater than the
number in the list of valid selections on this panel.
System action: None.
22
System Automation for z/OS Messages and Codes:
Classes: None.
AOF186I • AOF201I
AOF186I
parameter PARAMETER SPECIFIED
MORE THAN ONCE
Explanation: A parameter was used in a command
more than once, or was specified more than once for a
subsystem definition in the automation control file.
The variable parameter shows the duplicated
parameter.
Operator response: Enter the command again, using
the correct syntax.
System programmer response: None.
Classes: None.
AOF199I
FOR REQ=DISP THE ONLY VALID
PARAMETERS ARE: ID=, FROM=, and
TO=
System action: The entered command is not
processed. For automation control file processing the
parameter is ignored.
Explanation: A parameter other than ID=, FROM=, or
TO= was entered. These are the only valid parameters.
Operator response: Enter the command again, using
the correct syntax.
System action: The entered command is not
processed.
System programmer response: None.
Operator response: Enter the command again, using
the correct syntax.
Classes: None.
System programmer response: None.
AOF187I
SPECIFIED OPERAND operand
INVALID FOR parameter FOR A CROSS
DOMAIN REQUEST TO cross_domain
Explanation: The specified operand (operand) cannot
be used with the specified parameter (parameter) for a
cross domain request to the specified cross domain
(cross_domain).
System action: The entered command is not
processed.
Classes: None.
AOF200I
time: COMMAND init_cmd FAILED.
RECEIVED RETURN CODE rr FROM
fail_cmd
Explanation: A command issued by the initiating
command ended with a non-zero return code.
The variable time shows the time that this message
was generated.
Operator response: Enter the command again, using
the correct syntax.
The variable init_cmd shows the name of the
initiating command.
System programmer response: None.
The variable rr shows the condition code that was
returned by the failing command.
Classes: None.
AOF188I
FROM= AND TO= PARAMETERS ARE
INVALID FOR REQ=REPL|DEL
REQUESTS
Explanation: The FROM parameter and TO parameter
specified in the command are not valid for replace or
delete requests.
System action: The entered command is not
processed.
Operator response: Enter the command again, using
the correct syntax.
System programmer response: None.
Classes: None.
AOF189I
FOR REQ=DEL THE ONLY VALID
PARAMETER IS: ID=
Explanation: A parameter other than ID= was entered.
This is the only valid parameter.
System action: The entered command is not
processed.
The variable fail_cmd shows the name of the failing
command.
System action: Processing is terminated.
Operator response: Notify your system programmer.
System programmer response: Determine why the
command failed and correct the problem.
Classes: 0.
AOF201I
time : CLIST clist_name: msg_input
Explanation: An error occurred during processing of a
command list.
The variable time shows the time this message was
generated.
The variable clist_name shows the name of the
command list that was being processed when the
error occurred.
The variable msg_input describes the error.
System action: Processing of the command list ends
with an appropriate return code.
Operator response: Contact your system programmer.
System programmer response: Perform problem
Chapter 2. Messages AOF000I to AOF969I
23
AOF203I • AOF206I
determination on the command.
AOF205A
Classes: 0.
AOF203I
clist_name INVOKED BY
UNAUTHORIZED USER (user_ID).
REQUEST DENIED: request
Explanation: A command list was called by a user
who is not authorized to do so. The request to process
the command list was denied.
The variable clist_name shows the command list that
was called.
The variable user_ID shows the ID of the user who
called the command list.
The variable request shows the request that
accompanied the call the command list.
System action: The command list identified in the
message is not processed.
Operator response: If you feel that you should be
authorized for this command list, request authorization
from your system programmer.
System programmer response: Evaluate the need the
operator has for this function. If authorization should
be granted, notify the security administrator.
Classes: 0.
AOF204I
time: EXPECTED PARAMETERS
MISSING OR INVALID FOR REQUEST
clist_name - parameter_name
Explanation: One or more parameters that must be
passed to the command list identified in this message
are missing or are not valid.
The variable time shows the time this message was
generated.
The variable clist_name shows the name of the
command list that the variables must be passed to.
The variable parameter_name shows the name of the
parameter that was missing or not valid.
System action: None.
Operator response: Make sure that the syntax is
correct and enter the request again. The netlog will
show both the message and the request as processed.
Notify your system programmer if the request fails
again.
System programmer response: Review the user input
to determine the validity of the request and instruct the
operator on the proper procedure. If the user input is
correct, set debugging on for the command list to
determine the source of the error.
Classes: 0.
time : command COMMAND FAILED
FOR clist_name: interval - WAIT TIME
EXPIRED
Explanation: Processing of the command identified by
this message failed because it took too much time. The
timer interval for command processing was exceeded.
The variable time shows the time this message was
generated.
The variable command shows the name of the
command that failed.
The variable clist_name shows the name of the
command list that was requested.
The variable interval shows the timer interval that
was exceeded.
System action: None.
Operator response: Check the netlog that was active
when the message was received to see whether other
command timers have expired. If no other timers have
expired, review the syntax for the command and issue
the command again. If other command timers have
been exceeded or if processing of the command fails
again, notify your system programmer.
System programmer response: Review the user input
to determine the validity of the request and instruct the
operator on the proper procedure. If the user input is
correct, review the netlog that was active at the time of
the message to see whether there is a reason for delays
in command list processing. Note the value of the timer
interval to see whether the timer default should be
changed.
Classes: 0, 40, 44.
AOF206I
time : "command" COMMAND FAILED
FOR clist_name: RECEIVED received_ID
"received_value"
Explanation: Processing of the command identified in
this message failed. The command list identified in this
message received a return code or a message indicating
the problem.
The variable time shows the time this message was
generated.
The variable command shows the command that was
processed.
The variable clist_name shows the command list that
was requested.
The variable received_ID shows either a message ID
or the text string "RETURNCODE=".
The variable received_value shows the message text
or the return code.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Check the netlog for
further information. Perform problem determination on
24
System Automation for z/OS Messages and Codes:
AOF207E • AOF221I
The variable command shows the command that was
not processed, or the name of the REXX script
processing the command.
the command list identified in this message.
Classes: 0.
AOF207E
System action: The command is not processed.
time: NO DEFAULTS SET FOR
resource_name, CLIST HALTED
Operator response: If the automation environment has
been completely initialized, message AOF540I is issued.
Then reenter the command.
Explanation: Command list processing has been
halted because automation defaults have not been set
for the resource identified in this message.
System programmer response: None.
The variable time shows the time this message was
generated.
The variable resource_name shows the name of the
resource that automation defaults are not defined
for.
System action: The process is ended.
Operator response: Contact your system programmer.
System programmer response: Correct the automation
control file entries for the resource identified in this
message.
Classes: 0.
AOF211E
time: NO AUTOOPS ENTRIES HAVE
BEEN DEFINED - AUTOMATION
CANNOT CONTINUE
Explanation: No automated operator (AUTOOPS)
entries have been defined in the automation control file
for the automation environment.
The variable time shows the time this message was
generated.
Classes: None.
|
AOF217I
|
|
|
|
|
|
|
|
Explanation: The command that was entered cannot
be processed because this command is not supported in
this environment.
|
System action: The command is not processed.
|
Operator response: None.
|
System programmer response: None.
|
Classes: None.
time: command IS NOT SUPPORTED
The variable time shows the time when this message
was generated.
The variable command shows the command that was
not processed, or the name of the REXX/Command
List processing the command.
AOF219I
"OPID=" ONLY VALID WHEN
"STATUS=" IS SPECIFIED
System action: Automation initialization is ended.
Explanation: You can change the operator ID (OPID)
only when the status is specified to be changed.
Operator response: Notify your system programmer.
System action: The command is not processed.
System programmer response: Add the appropriate
automated operator entries in the automation control
file using the customization dialogs. See IBM Tivoli
System Automation for z/OS Defining Automation Policy
for more information.
Operator response: Enter the command again and
specify both the STATUS= and OPID= parameters or
do not specify the OPID= parameter.
In addition, since processing of the AUTOOPS
ENTRIES is performed on task AUTO2, verify AUTO2
is active and available (and not scheduled to process
other work that might prevent SA z/OS from using it).
Classes: 0.
AOF216I
time: command YOUR COMMAND
CANNOT BE PROCESSED - THE
AUTOMATION ENVIRONMENT HAS
NOT BEEN INITIALIZED
Explanation: The command that was entered cannot
be processed because the automation environment has
not been completely initialized.
The variable time shows the time when this message
was generated.
System programmer response: None.
Classes: None.
AOF221I
time: NO PRIMARY FOCAL POINT
DOMAIN HAS BEEN DEFINED DEFAULT OF domain_ID USED
Explanation: A primary focal point domain was not
defined in the automation control file member. The
domain ID shown by the variable domain_ID will be
assigned to the primary focal point.
The variable time shows the time this message was
generated.
System action: The current domain is assigned as the
primary focal point.
Operator response: None.
System programmer response: If the default value is
not desired, use the customization dialogs to correct the
Chapter 2. Messages AOF000I to AOF969I
25
AOF222I • AOF229I
automation control file member. For more information,
refer to IBM Tivoli System Automation for z/OS Defining
Automation Policy.
Classes: 40, 43.
AOF225I
Classes: None.
AOF222I
time: NO BACK UP FOCAL POINT
DOMAIN HAS BEEN DEFINED DEFAULT OF domain_ID USED
Explanation: A backup focal point domain was not
defined in the automation control file member. The
domain ID shown by the variable domain_ID will be
assigned to the backup focal point.
The variable time shows the time this message was
generated.
System action: The current domain is assigned as the
backup focal point.
Operator response: None.
System programmer response: If you do not want the
default backup focal point domain to be used, use the
customization dialogs to specify a backup focal point
domain in the automation control file member. For
more information, refer to IBM Tivoli System Automation
for z/OS Defining Automation Policy.
Classes: None.
AOF223I
SETSTATE REJECTED - SUBSYSTEM
name INVOLVED IN A SHUTDOWN
Explanation: A SETSTATE command has been
requested for a subsystem but it or one of its
dependants is in the process of shutting down.
The variable name shows the subsystem involved in
the shutdown.
System action: The request is denied.
Operator response: Wait for the shutdown to
complete then reissue the SETSTATE request.
System programmer response: None.
Classes: None.
AOF224I
time: JOB jobname HAS BEEN DEFINED
TO RUN ONLY ONCE - STATE NOT
SET
Explanation: A transient job has been defined to run
only once and a request was made for its status to be
changed.
Explanation: While loading an automation control file,
a duplicate keyword was found for a subsystem, its
value was ignored.
The variable keyword shows the duplicated keyword.
The variable subsystem is the name of the subsystem
containing the keyword.
System action: The first occurrence of the keyword
value is used.
Operator response: None.
System programmer response: Remove the duplicate
entry from the automation control file.
Classes: 40, 43.
AOF227I
UNABLE TO PROCESS command - reason
Explanation: System automation is not able to process
the requested action.
The variable command shows the affected command.
The variable reason gives an explanation.
System action: Processing stops.
Operator response: None.
System programmer response: None.
Classes: None.
AOF229I
time: NO ENTRY FOR resname (entry
type) HAS BEEN DEFINED - DEFAULT
OF value USED
Explanation: The system type was not defined in the
automation control file.
The variable time shows the time this message was
generated.
The variable resname shows the name of the
keyword being defined.
The variable entry shows the name of the entry in
the automation control file member.
The variable type shows the name of the type in the
automation control file member.
The variable value shows the value assigned to the
entry within the specified resource.
The variable time shows the time this message was
generated.
System action: Default value is assigned.
The variable jobname shows the job involved.
Operator response: None.
System action: Request rejected for this job.
Operator response: None.
System programmer response: None.
26
DUPLICATE KEYWORD keyword
FOUND FOR SUBSYSTEM subsystem.
FIRST OCCURRENCE USED
System Automation for z/OS Messages and Codes:
System programmer response: If the default value is
not desired, use the customization dialogs to correct the
automation control file member. For more information,
AOF233I • AOF246A
refer to IBM Tivoli System Automation for z/OS Defining
Automation Policy.
AOF244I
Classes: None.
AOF233I
SHUTDOWN REJECTED SUBSYSTEM name INACTIVE
Explanation: The subsystem you are trying to
shutdown is inactive.
The variable name shows the name of the
subsystem.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF240I
REQUESTED TIMER timerid WAS
ADDED
Explanation: This message is a response to the TIMER
ADD command. Processing of the command was
completed successfully.
Explanation: Shutdown processing has been
suspended for the job identified by the variable
job_name for the number of minutes shown by the
variable interval. This allows users of the job to end
their activities before the job is shut down.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource.
The variable resname shows the name of the
resource.
System action: The Shutdown process begins again
after the number of minutes specified in this message.
Operator response: None.
System programmer response: None.
Classes: 40, 43, 44, 46.
AOF245I
The variable timerid shows the ID of the timer.
System action: The timer is scheduled, with the
requested name and function.
Operator response: None.
System programmer response: None.
Classes: None.
AOF241I
time: EXPECTED PARAMETERS
MISSING OR INVALID FOR REQUEST
clist_name - PARAMETER parm_list
Explanation: One or more of the parameters that
needed to be passed to a command list during
shutdown processing were missing or were not valid.
The variable time shows the time this message was
generated.
The variable clist_name identifies the requested
command list.
The variable parm_list lists all of the parameters that
were missing or were not valid.
System action: The shutdown process ends.
Operator response: Make sure valid parameters are
entered.
System programmer response: Make sure valid
parameters are entered. Check the parameters in the
automation control file.
Classes: 0.
time: SHUTDOWN PROCESSING ON
restype resname (JOB job_name)
SUSPENDED FOR interval MINUTES
time: restype resname (JOB job_name)
STATUS IS status - SHUTDOWN WILL
BYPASS ISSUING msgtype
COMMANDS
Explanation: The shutdown processing has
determined that the job identified by the variable
job_name is already shutting down. The shutdown
processing will bypass issuing further commands.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource.
The variable resname shows the name of the
resource.
The variable status shows the status of the resource.
The variable msgtype shows the command type to be
issued (SHUTINIT,SHUTDOWN).
System action: The status of the job is either stopping
or abending. The job is checked to see whether it is
down, so that shutdown processing may complete. If
the job does not end, manual intervention will be
required.
Operator response: None. This message is sent to the
netlog only.
System programmer response: Check why the job
was in stopping or abending status.
Classes: 40, 43.
AOF246A
time: SHUTDOWN PROCESSING
FAILED FOR SUBSYSTEM
subsystem_name - SHUTDOWN MAY
NOT COMPLETE SUCCESSFULLY
Explanation: An error occurred during shutdown
Chapter 2. Messages AOF000I to AOF969I
27
AOF247E • AOF253I
processing. A message describing the error was issued
previously.
The variable time shows the time when this message
was generated.
The variable subsystem_name shows the subsystem
that the message was for.
System action: None.
Operator response: See the message describing the
error that was issued previously to determine why
shutdown processing failed.
System programmer response: None.
System action: Current® processing might not be
completed successfully.
Operator response: Review the netlog that was active
at the time of this message for related messages that
help define the problem. Contact your system
programmer.
System programmer response: Review the
initialization procedures and the control file to
determine why the cglobal variable is not being
initialized properly. You might need to set debugging
on to identify the problem. Correct the problem.
Classes: None.
Classes: 40, 43.
AOF251I
AOF247E
time: SHUTDOWN PROCESSING
FAILURE FOR restype resname (JOB
job_name) - ALL COMMANDS/REPLIES
MAY NOT HAVE BEEN ISSUED command_type error_type FOR PASS
pass_number HAD ERROR
Explanation: Shutdown processing has failed for the
subsystem identified by the resource name (resname)
and the job name (job_name).
The variable time shows the time this message was
generated.
The variable restype shows the type of resource.
command_type shows the command type to be issued
(SHUTINIT,SHUTDOWN).
The variable error_type shows whether a command
or reply had errors.
The variable pass_number shows the pass number in
error.
System action: The shutdown processing ends.
Operator response: Check for the type of errors
identified by error_type and contact your system
programmer.
System programmer response: Review the automation
control file, looking for the job identified by this
message. Correct the errors observed by the operator.
Look for message AOF206I in the netlog that was active
at the time this message was issued. Message AOF206I
contains information you can use to determine why
processing of the command or reply failed. The syslog
contains commands and replies that can be checked
against what should have been issued.
Classes: 40, 43.
Explanation: A shutdown has been requested but a
shutdown is currently executing involving this
subsystem or one of its children.
The variable type shows the shutdown type.
The variable subsystem_type shows the name of the
subsystem.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF252I
time: resource CGLOBAL cglobal WAS
NOT PROPERLY INITIALIZED
Explanation: The cglobal variable identified in this
message was not properly initialized for the resource
identified in this message.
The variable time shows the time this message was
generated.
28
System Automation for z/OS Messages and Codes:
time: TIMER ID = timer_ID NOT
SCHEDULED - reason
Explanation: The timer identified by the variable
timer_ID could not be scheduled.
The variable time shows the time this message was
generated.
The variable reason gives an explanation of failure,
such as TASK NOT ACTIVE.
System action: The timer identified in the message is
not scheduled.
Operator response: Find the reason the timer was not
scheduled, correct the problem, and issue the time
request again.
System programmer response: None.
Classes: 40, 43.
AOF253I
AOF249E
SHUTDOWN type REJECTED subsystem_type ALREADY IN
PROGRESS
time: REQUESTED TIMER = timer_ID
NOT FOUND
Explanation: This message is a response to an attempt
to delete (purge) a timer (identified by the variable
timer_ID). The timer to be deleted could not be found.
The variable time shows the time this message was
generated.
AOF255I • AOF264I
System action: Processing continues.
|
System programmer response: None.
Operator response: Verify that the timer does not exist
by refreshing the timer display.
|
Classes: None.
System programmer response: None.
AOF262E
Classes: 0, 40, 43.
AOF255I
time: EXIT exit_name IN entry type IS
INVALID, RC=return_code
Explanation: An exit name that is not valid (shown by
the variable exit_name) was found when calling user
exits.
The variable time shows the time this message was
generated.
The variable entry identifies the entry field in the
automation control file where the exit was defined.
The variable type identifies the type field in the
automation control file where the exit was defined.
The variable return_code shows a return code that
identifies why the exit was not valid: If the return
code is 04, the exit name was not 1 to 8 characters
long; if the return code is 08, the exit name was not
a valid module or command list.
System action: The exit code for the routine that is not
valid is bypassed.
Operator response: Contact your system programmer.
System programmer response: Correctly define the
exit routine or remove it from the exit list.
Classes: 0, 40, 44.
MESSAGE ID message_ID INVALID,
MUST BE "NNN", "ABCNNN" OR
"ABCDNNN"
Explanation: The specified message ID is invalid.
Three message ID forms are valid:
v Three decimal digits (NNN)
v A three-character prefix followed by three decimal
digits (the prefix may contain numeric values)
v A four-character prefix followed by three decimal
digits (the prefix may contain numeric values).
The variable message_ID shows the message ID
specified as the second parameter of the AOCMSG
command. This message ID is not valid.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Correct the message ID
specified as the second parameter of the AOCMSG
command.
Classes: None.
AOF263I
MESSAGE ID NUMERIC message_ID IS
NOT NUMERIC
Explanation: The specified message ID is not valid
because it does not end with three numeric digits.
The variable message_ID shows the message ID
specified as the second parameter of the AOCMSG
command. This message ID is not valid.
|
AOF256I
|
|
|
|
Explanation: A user exit (shown by the variable
exit_name) has been invoked.
|
System action: None.
System programmer response: Correct the message ID
specified as the second parameter of the AOCMSG
command.
|
Operator response: None.
Classes: None.
|
System programmer response: None.
|
Classes: None.
|
|
AOF257I
|
|
|
|
|
|
Explanation: A user exit (shown by the variable
exit_name) has ended.
|
System action: None.
|
Operator response: None.
time: EXIT exit_name BEING INVOKED.
The variable time shows the time this message was
generated.
time: EXIT exit_name ENDED WITH
RC=return_code.
The variable time shows the time this message was
generated.
The variable return_code shows the return code
given by the user exit.
System action: None.
Operator response: Contact your system programmer.
AOF264I
TOO FEW PARAMETERS ON
AOCMSG COMMAND, 2 IS
MINIMUM
Explanation: The AOCMSG command was issued
without one or more required parameters. At least two
parameters must be specified for the command to be
processed successfully.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Make sure that the
coding of the AOCMSG command specifies a message
ID value as the second parameter. If you do not want
to specify a value for the first parameter, code a comma
Chapter 2. Messages AOF000I to AOF969I
29
AOF271I • AOF290I
in its position as a place holder (AOCMSG ,001).
AOF286I
Classes: None.
AOF271I
clist_name: DATATYPE "data_type" FOR
entry NOT KNOWN, IGNORED
Explanation: The data_type keyword specified in entry
entry is not recognized. It is being ignored.
The variable clist_name shows the name of the
command list that generated this message.
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40.
AOF282I
Explanation: Subsystem status information has been
verified with the active cglobal variables.
The variable clist_name shows the name of the
command list that generated this message.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF287I
clist_name: COMPLETE
Explanation: Processing of the command list has been
completed normally.
clist_name: SDF DATA LOADED
Explanation: The status display facility (SDF) portion
of system automation initialization is complete.
The variable clist_name shows the name of the
command list that generated this message.
System action: None.
Operator response: None.
System programmer response: None.
The variable clist_name shows the name of the
command list that generated this message.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF288I
Classes: None.
AOF283I
clist_name: SUBSYSTEM STATUS
VERIFIED
clist_name: number SUBSYSTEMS
CURRENT STATUS PRIMED
Explanation: This message reports the number of
subsystems processed.
The variable clist_name shows the name of the
command list that generated this message.
clist_name: subsystem_name JOBNAME IS
DUPLICATE, SUBSYSTEM IGNORED
Explanation: Subsystem subsystem_name has a job
name that is a duplicate. This subsystem is ignored.
The variable clist_name shows the name of the
command list that generated this message.
System action: None.
Operator response: Contact your system programmer.
Operator response: None.
System programmer response: Make sure that the
subsystem subsystem_name does not have a duplicate
job name.
System programmer response: None.
Classes: 40.
System action: None.
Classes: None.
AOF290I
AOF284I
clist_name: number NOTIFY OPERATORS
READIED
clist_name: SUBSYSTEM subsystem_name SCHEDULING
SUBSYSTEM scheduling_subsystem_ name
INVALID
Explanation: This message reports the number of
notification operators that have been processed and
initialized.
Explanation: The scheduling_subsystem_name is not
defined as a valid Job Entry Subsystem, and therefore
cannot be used to schedule subsystem subsystem_name
The variable clist_name shows the name of the
command list that generated this message.
The variable clist_name shows the name of the
command that generated this message.
System action: None.
Operator response: None.
System action: The primary JES subsystem will be
used.
System programmer response: None.
Operator response: Contact your system programmer.
Classes: None.
System programmer response: Correct the subsystem
definition to identify a subsystem of type JES2 or JES3.
30
System Automation for z/OS Messages and Codes:
AOF291I • AOF306I
Classes: 40.
AOF291I
System programmer response: Review your spool
recovery commands.
clist_name: NO JES2 OR JES3
SUBSYSTEMS DEFINED; SUBSYS =
subsystem_name SET
Explanation: No subsystems were defined as being
type JES2 or JES3, and therefore the validity of the
subsystem identified as the primary Job Entry
Subsystem (JES) cannot be validated.
The variable clist_name shows the name of the
command list that generated this message.
System action: The identified subsystem will be used
without validation.
Classes: 40, 43, 44.
AOF296I
TARGET AND RESOURCE_SYSTEM
SPECIFICATION ARE DIFFERENT
(TARGET IGNORED)
Explanation: The target and resource system
specification in the INGREQ command are different.
Therefore the target specification has been removed.
System action: None.
Operator response: None.
Operator response: Contact your system programmer.
System programmer response: None.
System programmer response: Correct the subsystem
definition to properly identify the one or more Job
Entry Subsystems, and verify that the correct
subsystem is identified as the primary JES.
Classes: None.
AOF300I
A REPLY MUST BE SPECIFIED
Explanation: You must specify a reply.
Classes: 40.
System action: None.
AOF293I
time: THERE IS NO OUTSTANDING
REPLY STORED BY SA z/OS FOR
SUBSYSTEM sname.
Explanation: System automation cannot determine
from its CGLOBALS the reply ID for this subsystem.
Operator response: Specify a reply.
System programmer response: None.
Classes. None.
time: REQUEST clist_name action BY
oper_id IS COMPLETED FOR resname
The variable time shows the time the error message
was generated.
AOF302I
The variable sname shows the subsystem to be
replied to.
Explanation: The request to set a function ON or OFF
for the specified resource was successful.
System action: Processing continues.
Operator response: Notify your system programmer.
System programmer response: Check why the reply
ID is not stored by SA z/OS.
Classes: 40, 43, 44.
AOF294I
SPOOL type RECOVERY COMMANDS
EXHAUSTED, SPOOL TGS IS NOT
RELIEVED, OPERATION
INTERVENTION IS REQUIRED
Explanation: While attempting to recover from a spool
shortage, SA z/OS ran out of defined recovery
commands. User has chosen not to reissue the spool
commands.
The variable type shows the type of spool problem
being recovered.
The variable time shows the time this message was
generated.
The variable clist_name shows the name of the
requested command list or command.
The variable action shows the function of the
requested command list or command.
The variable oper_ID shows the name of the
operator that issued the request.
The variable resname shows the name of the
resource affected.
System action: The requested function is performed
on the specified resource.
Operator response: None.
System programmer response: None.
Classes: None.
time: NO auto_type AUTOMATION
REQUIRED FOR restype resname
System action: The spool recovery has stopped.
AOF306I
Operator response: You need to have a look at your
spool usage .SA z/OS has issued all the defined spool
recovery passes and the spool TGS is not relieved.
Manual intervention by operators is required.
Explanation: Automation was requested for the
resource and it was found that no action was required.
The variable auto_type shows the type of automation
requested.
Chapter 2. Messages AOF000I to AOF969I
31
AOF307I • AOF311I
The variable restype shows the type of resource.
AOF310I
The variable resname shows the name of the
resource.
The variable time shows the time this message was
generated.
System action: None.
time : resname autotype IS SET ON autotype action NOT FOUND FOR
msg_type WITH SELECTION selection
Explanation: The specified automation flag is on, but
the command or reply to be issued could not be found
in the automation control file.
Operator response: None.
The variable time shows the time when this message
was generated.
System programmer response: None.
The variable resname shows the name of the
resource.
Classes: None.
AOF307I
time: REQUEST clist_name action BY
oper_id WAS UNSUCCESSFUL FOR
resname, STATE IS ALREADY SET
Explanation: The request to set a function ON or OFF
for the specified resource was not successful.
The variable time shows the time this message was
generated.
The variable clist_name shows the name of the
requested command list or command.
The variable action shows the function of the
requested command list or command.
The variable resname shows the name of the
resource.
The variable autotype shows the automation flag that
has been checked.
The variable action shows the type of action that
should have been taken. Possible values are
COMMAND and REPLY.
The variable msg_type shows the message ID that
the specified action has been searched under in the
automation control file.
The variable selection shows the pass or selection
string that the entry that was searched for could not
be found on.
System action: Processing continues.
Operator response: None.
Operator response: None.
System programmer response: Use the customization
dialog to check the entries specified by the resource
name, the message ID and the selection string in the
automation control file. For further information, refer to
IBM Tivoli System Automation for z/OS Defining
Automation Policy.
System programmer response: None.
Classes: 40, 43.
The variable oper_id shows the name of the operator
that issued the request.
System action: None.
Classes: None.
AOF311I
AOF309I
time: OPERATOR operator_ID
EXECUTED TIMER timer_ID FOR
CATCHUP - COMMAND: cmd
Explanation: The command cmd was executed for
timer timer_ID because the current time was past the
execution time and CATCHUP=YES was specified.
The variable time shows the time this message was
generated.
The variable operator_ID shows the name of the
operator that executed the command.
The variable timer_ID shows the name of the timer
that was executed.
The variable cmd shows the command that was
executed.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
32
System Automation for z/OS Messages and Codes:
time : restype resname (JOB job_name) DID
NOT HAVE AN OUTSTANDING
REPLY ON msg_type PASS pass_number
Explanation: The automation policy for shutting down
a resource indicates that a reply should be issued for
the command type identified in this message. However,
there was no outstanding message that a reply could be
issued for on the pass shown by pass_number.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource.
The variable resname shows the name of the
resource.
The variable job_name shows the name of the job.
The variable msg_type shows the command type to
be issued (SHUTINIT,SHUTDOWN).
System action: Processing continues.
Operator response: Contact your system programmer.
System programmer response: Make sure that the
automation control file policy for shutting down the
resource identified in this message is accurate.
AOF313I • AOF316I
Classes: 40, 43.
AOF313I
time : START FOR restype resname (JOB
job_name ) WAS NOT ATTEMPTED reason
Explanation: SA z/OS attempted to start a resource
but could not for the reason given.
The variable time shows the time this message was
generated.
Classes: 0, 40, 43.
AOF315I
time : TIMER timer_ID PURGED by
operator operator_ID
Explanation: A timer was deleted from the NetView
timer list by the operator.
The variable time shows the time this message was
generated.
The variable restype shows the type of the resource.
The variable timer_ID shows the name of the timer
that was deleted (purged).
The variable resname shows the name of the
resource.
The variable operator_ID shows the name of the
operator who deleted the timer.
The variable job_name shows the name of the job.
System action: Processing continues.
The variable reason shows the reason that the
resource could not be started.
Operator response: None.
System action: If the resource was not started because
a flag was turned off it will be left in its current state
and the flag rechecked each time the monitor cycle
runs. No attempt will be made to start its parents until
the flag is turned on. If the resource was not started
because it (or one of its parents) was involved in a
shutdown its status may be changed to AUTODOWN.
It will not start until the shutdown has finished.
Operator response: If the resource failed to start
because a flag was set off and you want it to start you
should use INGAUTO to change the flag. If the
resource did not start because of a shutdown and you
want it to start you must either wait for the shutdown
to finish or clear the shutdown.
System programmer response: None.
Classes: 40, 43.
AOF316I
time : SHUTDOWN FOR restype resname
(JOB job_name) DELAYED interval
MINUTES - RECEIVED EXIT CODE
code FROM exit_name
Explanation: Shutdown processing has been
suspended for a job because a return code received
from an exit matched a shutdown return code that
temporarily stops processing.
The variable time shows the time this message was
generated.
System programmer response: None.
The variable restype shows the type of resource.
Classes: 40, 43.
The variable resname shows the name of the
resource.
AOF314I
time : CATCHUP TIMER ID timer_ID
NOT EXECUTED. TASK operator_ID
NOT LOGGED ON.
Explanation: A timer was unable to be restored
because the scheduled time had already occurred.
Catch-up processing unsuccessfully attempted to issue
the command. The command failed because the
operator (operator_ID) was not logged on to receive and
run the command.
The variable time shows the time this message was
generated.
The variable timer_ID shows the name of the timer
that was not able to be restored.
The variable operator_ID shows the name of the
operator where the timer command should have
run.
System action: Processing continues.
Operator response: Issue the command manually
under the appropriate operator ID.
The variable job_name shows the name of the job
that processing has been suspended for.
The variable interval shows the number of minutes
processing will be suspended.
The variable code shows the return code received
from the exit.
The variable exit_name shows the exit that the return
code was received from.
System action: Shutdown will be retried after the
interval. Retries will continue until subsystem is
shutdown.
Operator response: If the delay is excessive,
investigate the reason and contact your system
programmer.
System programmer response: If delay is excessive,
investigate why the exit is temporarily suspending
shutdown.
Classes: 40, 43.
System programmer response: None.
Chapter 2. Messages AOF000I to AOF969I
33
AOF319I • AOF325I
AOF319I
time : OPERATOR operator1
SCHEDULED TIMER timer_ID UNDER
OPERATOR operator2 - COMMAND: text
Classes: None.
AOF323I
Explanation: An operator created and scheduled a
new timer.
The variable time shows the time this message was
generated.
The variable operator1 shows the name of the
operator who created the timer.
The variable timer_ID shows the name of the timer
that was scheduled.
The variable operator2 shows the operator
identification where the timer was scheduled.
The variable text shows the text of the timer
command that was scheduled.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF320I
time : ASSIST LOG FOR:
resource_type/resource_name - KEY:
entry/type/keyword - COMMAND: text
Explanation: This message is generated when assist
mode is active for a resource and a command is issued
for that resource. This message identifies the resource
associated with the command and shows the text of the
command. This message is logged in the netlog.
The variable time shows the time this message was
generated.
The variable resource_type shows the type of
resource associated with the command.
The variable resource_name shows the name of the
resource associated with the command.
The variable entry shows the entry field from the
automation control file entry that defines the
command. If it is internally generated, this value
will be FUNC.
The variable type shows the type field from the
automation control file entry that defines the
command. If it is internally generated, this value
will be ISSUED.
The variable keyword shows the command selection
field from the automation control file entry.
The variable text shows the text of the command
that was issued, after variable substitution.
System action: This message is logged in the netlog.
Operator response: None.
System programmer response: Review the netlog to
verify that the action reported by this message was
intended and that variable substitution worked
properly.
34
System Automation for z/OS Messages and Codes:
time : ASSIST LOG FOR:
resource_type/resource_name - KEY:
entry/type/keyword - REPLY: text
Explanation: This message is generated when assist
mode is active for a resource and a reply is issued for
that resource. This message identifies the resource
associated with the reply and shows the text of the
reply. This message is logged in the netlog.
The variable time shows the time this message was
generated.
The variable resource_type shows the type of
resource associated with the reply.
The variable resource_name shows the name of the
resource associated with the reply.
The variable entry shows the entry field from the
automation control file entry that defines the reply.
If it is internally generated, this value will be
FUNC.
The variable type shows the type field from the
automation control file entry that defines the reply.
If it is internally generated, this value will be
ISSUED.
The variable keyword shows the reply selection field
from the automation control file entry.
The variable text shows the text of the reply that
was issued, after variable substitution.
System action: This message is logged in the netlog.
Operator response: None.
System programmer response: Review the netlog to
verify that the action reported by this message was
intended and that variable substitution worked
properly.
Classes: None.
AOF325I
CHRON COMMAND IN ERROR:
chron_command
Explanation: The CHRON command processor
rejected the command.
The variable chron_command shows the name of the
command that could not be executed.
System action: Processing continues.
Operator response: Reenter the correct command, if
applicable.
System programmer response: None.
Module: AOFRAAT1
Classes: None.
AOF326I • AOF334I
AOF326I
STOP TIME MUST BE LATER THAN
START TIME
Explanation: The stop time of the EVERY timer is
earlier than the start time.
System action: Processing continues.
Operator response: Reenter the correct command, if
applicable.
AOF333I
Explanation: The specified clist detected an error
while attempting to schedule a remote procedure call
(RPC) to run a clist or a command on a remote system
in the sysplex. The return code indicates which type of
error occurred:
12
An invalid handle was specified. The handle is
currently in use, or the handle was already
deleted, or it is being deleted.
16
Processing of the remote procedure call (RPC)
failed.
24
The target is not active, or it is not contained
in the member table.
32
REXX variable pool problem.
36
Other severe error.
40
The Sysplex Communication Manager
Environment is not available, for example,
because the Sysplex Communication Manager
task was not started.
44
An ABEND occurred.
System programmer response: None.
Module: INGRYTIM
Classes: None.
AOF331I
SUBSYSTEM name IS NOT DEFINED
ON THE LOCAL SYSTEM
Explanation: The specified subsystem is defined more
than once within the systems in the sysplex. Because
the command is operating in line mode and the
subsystem is not defined locally, system automation
cannot determine which of the subsystems the
command should be routed to.
An operator dialog issues this message.
The variable name shows the specified subsystem
name.
System action: None.
Operator response: Reenter the correct command.
Specify the TARGET parameter to identify the system
that the command should be routed to.
System programmer response: None.
Classes: None.
AOF332I
SUBSYSTEM name COULD NOT BE
LOCATED ON target
Explanation: The specified subsystem is neither
defined in the local system nor in any other system of
the sysplex.
If the target is outside the local sysplex, there could be
a problem with the RMTCMD link. If this is the case,
additional NetView messages have been issued.
An operator dialog issues this message.
The variable function shows the service that causes
the problem.
The variable return_code shows the return code from
the failing function.
The variable name shows the name of the clist that
invoked the failing function.
System action: None.
Operator response: Issue the command again. If the
problem persists, contact your IBM Support Center for
further assistance.
System programmer response: Examine the return
code of the failing service for the cause of the error. For
a list of possible error code values and their meaning,
refer to the explanation of message AOF350E. If you
cannot resolve the problem, contact your IBM Support
Center.
The variable name shows the specified subsystem
name.
Classes: 0.
The variable target shows the target, or the list of
targets where the subsystem is not defined.
AOF334I
System action: None.
Operator response: Reenter the correct command.
System programmer response: None.
Classes: None.
function CALL FAILED WITH RC=
return_code IN CLIST name
UNABLE TO RECEIVE THE OUTPUT
FROM THE REQUESTED SYSTEM(S)
system
Explanation: One or more remote procedure calls
(RPCs) were scheduled to get data from the remote
system(s). It is possible that the commands were
successfully processed on the remote system(s).
However, the “OK” result was not returned in time.
The variable system shows the list of systems that
did not provide the output in time.
Chapter 2. Messages AOF000I to AOF969I
35
AOF335I • AOF340I
System action: None.
Operator response: Check whether processing has
completed successfully, then reenter the command. If
the problem persists, contact your IBM Support Center.
System programmer response: Examine the netlog for
additional information. If necessary, increase the
maximum wait time, "aofrpcwait". If communication is
via the NetView RMTCMD, increase the default
CORRCMD wait time value in the DSICCDEF or use
"aofrmtcmdwait".
Classes: None.
AOF338I
CONFLICTING TARGET
SPECIFICATION
Explanation: ALL and at least one other system name
or domain ID have been specified for the TARGET
parameter.
An operator dialog issues this message.
System action: None.
Operator response: Reenter the correct command.
System programmer response: None.
Classes: None.
AOF335I
UNRECOGNIZED ACTION CODE
Explanation: An action code that is not valid was
entered.
System action: None.
Operator response: Enter a correct action code. For a
list of valid action codes (or selection codes), call help
from the panel that this message appears on.
AOF339I
name DOES NOT CORRESPOND TO
AN ACTIVE TARGET WITHIN THE
environment
Explanation: The specified name is neither the system
name nor the network domain ID of an active target
within the specified environment.
System programmer response: None.
The following reasons can cause the dialog to issue this
message:
Classes: None.
v The specified target name is not valid.
AOF336I
SUBSYSTEM name NOT DEFINED ON
SYSTEMS sysname_list
Explanation: The specified subsystem is not defined
on the system(s) identified with the TARGET parameter
or the appropriate panel field.
An operator dialog issues this message.
The variable name shows the specified subsystem
name.
The variable sysname_list shows the systems that do
not have the subsystem defined.
v If the specified target is outside the local sysplex, the
GATEWAY connection to that target could be
inactive.
v If the target is outside the local sysplex, there could
be a problem with the RMTCMD link. If this is the
case, additional NetView messages have been issued.
The variable name shows the unrecognized name.
The variable environment shows the environment the
dialog searched for. It is either sysplex or enterprise.
System action: None.
System action: None.
Operator response: Reenter the correct command.
Operator response: Reenter the correct command.
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
AOF337I
ONLY ONE TARGET IS ALLOWED
Explanation: More than one system name or domain
ID was specified for the TARGET parameter. However,
only one name is allowed.
AOF340I
NO RESPONSE RECEIVED FROM
SYSTEM system_name
Explanation: A remote procedure call (RPC) was sent
to the specified system, but the remote system did not
reply with an answer within the expected time period.
System action: None.
The variable system_name identifies the system that did
not respond.
Operator response: Reenter the correct command.
System action: None.
System programmer response: None.
Operator response: Issue the command again. If the
problem persists, contact your local support personnel
for further assistance.
Classes: None.
System programmer response: Examine the netlog for
additional information. If necessary, increase the
36
System Automation for z/OS Messages and Codes:
AOF341I • AOF350E
maximum waittime “aofrpcwait.”
Classes: None.
AOF341I
time : clist_name RETURN CODE: xx
SYSTEM: name ERROR: error
Explanation: This is an internal message that is used
to transmit command completion information from the
system that processed the command back to the system
that requested the command execution. The message
will not appear on any screen.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF343I
NOTHING TO DISPLAY
|
AOF346I
|
|
Explanation: INGRUN was called to set the runmode
to *ALL while it was already *ALL.
|
System action: None.
|
|
Operator response: None, because *ALL is already set.
You can specify another runmode.
|
System programmer response: None.
|
Classes: None.
AOF347I
RUNMODE *ALL ALREADY SET
NO RUNMODE DEFINED FOR system
Explanation: INGRUN was called to set a runmode
but there are none defined on the given system.
The variable system shows the name of the affected
system.
System action: None.
Explanation: No data is available for display.
Operator response: Contact your system programmer.
System action: None.
System programmer response: Define runmodes for
the given system in the automation control file.
Operator response: None.
System programmer response: None.
Classes: None.
AOF344I
CLIST clist_name DOES NOT EXIST
Explanation: The specified clist could not be found.
The variable clist_name shows the name of the clist.
System action: None.
Operator response: Issue the command again.
System programmer response: None.
Classes: None.
AOF345I
RUNMODE CHANGED FOR system.
PLEASE REVISE RUNMODE
QUALIFICATIONS
Explanation: The runmode has been changed and
there are still resources that have been qualified earlier
by an INGRUN command.
The variable system shows the system for which
runmode was changed.
System action: None.
Operator response: Revise the displayed list and
decide whether the runmode qualification for those
resources can be deleted.
System programmer response: None.
Classes: None.
Classes: None.
AOF350E
COMMUNICATION ERROR:
SYSTEM=system name ERRTYPE=error
type ERRCODE=error code
SERVICE=service RET=return code
RSN=reason code DIAG=module remainder
Explanation: An error was detected during
communication to another system. This message always
contains the name of the system where the error
occurred, the type of error and the error code. The
other keywords are optional.
The variable system name shows the name of the
OS/390 or z/OS system where the error occurred.
The variable error type shows a decimal number that
specifies the type of the error. It can have the following
values:
4 Input checking failed. User specified input, for
example, global variables, that were not set up
correctly. The variable error code provides further
information.
8 The system automation communication manager
Data Service Task (DST) could not be initialized.
12 Termination error of the system automation
communication manager Data Service Task.
16 An internal communication pipe service provided
by a system automation system failed.
20 A remote procedure call (RPC) Handler failed.
24 A system service failed.
28 A REXX API failed.
32 A storage problem occurred.
36 An internal error occurred.
40 The system automation communication services
could not be initialized.
Chapter 2. Messages AOF000I to AOF969I
37
AOF350E
The variable error code shows a unique number that
specifies where in the code the error occurred.
The variable service shows the name of the service that
caused the error.
The module remainder variable shows diagnostic
information. It specifies the name of the failing module.
The remaining items vary depending on the error code.
The module remainder variable data is intended for your
IBM Support Center.
The variable return code shows the return code of the
failing service (hex number). This variable will only be
returned in combination with the service variable.
The following table shows the possible combinations of
error types and error codes and their meaning. This
information also applies to message HSAM1050E.
The variable reason code shows the reason code of the
failing service (hex number). This variable will only be
returned in combination with the service variable.
Table 3. Combinations of Error Types and Error Codes
Error Type Error Code Meaning
4
4
72
136
140
284
260
Explanation
Input checking error. Invalid format of a handle.
Action Contact your IBM Support Center (ISC).
Explanation
Input checking error. The sysplex group name is not known. The reason is that
the retrieval of the common global variable AOFXCFGROUP failed or it contains
a null string.
Action Set AOFXCFGROUP up properly.
4
268
Explanation
Input checking error. Target sysplex member, representing the target NetView or
the automation manager, is not valid.
Action Specify a valid target sysplex member or start the SA z/OS sysplex
communication manager in NetView for the specified system or start the
automation manager.
4
541
550
Explanation
Input checking error. Target sysplex member, representing the primary
automation manager, is not active.
Action Check whether the member name in the DIAGNOSTIC field is a valid XCF
member name. Specify a valid target sysplex member or start the automation
manager.
8
13
16
20
Explanation
DST initialization error. There is not enough storage available.
Action Increase the region size.
8
31
170
Explanation
DST initialization error. An SA z/OS communication service module cannot be
loaded.
Action Check return code of the load service.
8
208
Explanation
DST initialization error. An SA z/OS communication environment cannot be
created.
Action Check the z/OS return code.
38
System Automation for z/OS Messages and Codes:
AOF350E
Table 3. Combinations of Error Types and Error Codes (continued)
Error Type Error Code Meaning
8
244
248
573
574
Explanation
DST initialization error. An SA z/OS communication provided NetView
command processor cannot be added to the NetView environment.
Action Check the NetView return code.
8
300
348
Explanation
DST initialization error. An attempt was made to start SA z/OS communication
on an OS/390 system lower than Release 3.
Action Install an OS/390 or z/OS Release supporting XCF Ordered Message Delivery.
8
571
Explanation
DST initialization error. The DST receiver task (DSR) cannot be stared.
Action Check the return and reason codes. If necessary contact your IBM Support Center.
8
489
Explanation
Automation manager initialization error. The MTIB could not be initialized.
Action Increase the region size and if necessary contact your IBM Support Center.
8
517
Explanation
Automation manager initialization error. A subtask could not be initialized.
Action Contact your IBM Support Center.
8
520
Explanation
Automation manager initialization error. The subtask shell logon to the
Communication Manager failed.
Action Contact your IBM Support Center.
Chapter 2. Messages AOF000I to AOF969I
39
AOF350E
Table 3. Combinations of Error Types and Error Codes (continued)
Error Type Error Code Meaning
8
532
Explanation
Automation manager initialization error. A control block cannot be created that is
anchored to the MTIB. One of the following return codes in hexadecimal will be
supplied:
X'64' (100)
Message control block (MSIB) creation failed
X'190' through X'1F3' (400 + nn)
PKVT cannot be initialized
X'194' (404)
PKVT cannot be initialized due to errors in the automation manager
parmlib member.
|
|
|
X'198' (408)
PKVT cannot be initialized for the automation manager due to missing
parmlib member. See also message HSAM5206E for more information.
X'1F8' (504)
Pre-initialization of the control block failed
X'1FC'(508)
Post-initialization of the control block failed
X'256' (598)
Message control block (MSIB) creation failed
X'257' (599)
Message control block (MSIB) creation failed
X'2BC' through X'31F' (700 + nn)
Initialization of the CTCB failed
X'320' through X'383'(860 + nn)
Deletion of the CTCB failed. This is a setup problem of the component
trace of the system logger.
X'384' through X'3E7' (900 + nn)
Initialization of the MTIB failed
X'3E8' through X'7CF' (1000 + nn)
where if:
nn=13,16,20,472
it is a storage problem. If:
nn=31,170
it is a load module problem.
Communication initialization failed
If RET=X'000496' (1174) then there might be too many automation
manager instances on the MVS image. The limit is 9.
2707
No longer MODE=SUP
Action Check the return code and other messages that may be issued with this message.
If necessary contact your IBM Support Center.
40
System Automation for z/OS Messages and Codes:
AOF350E
Table 3. Combinations of Error Types and Error Codes (continued)
Error Type Error Code Meaning
8
533
Explanation
Automation manager initialization error. Not all modules could be loaded.
Action Check the STEPLIB concatination. If necessary contact your IBM Support Center.
8
536
Explanation
Automation manager initialization error. Cannot open the task lib.
Action Check the HSAMODLE DD statement in the start procedure of the automation
manager and if necessary contact your IBM Support Center.
8
561
Explanation
Automation manager initialization error. The MVS console interface could not be
initialized.
Action Contact your IBM Support Center.
8
564
Explanation
DST initialization error. The error occurred when parsing the DST init member
INGXINIT.
Action Check the DSIPARM member INGXINIT for syntax errors.
8
566
Explanation
DST initialization error. A global NetView variable could not be created.
Action Increase the region size.
|
|
|
8
700
|
|
|
|
Action Modify INGXINIT and set parameter PLEXID correctly.
8
701
|
|
|
|
Explanation
RPC with type=SYSPLEX was called although PLEXID was not specified.
Action Contact your IBM Support Center.
8
702
|
|
|
|
Explanation
Invalid Suffix for XCF group INGPX$xx.
Explanation
Member table extension cannot be updated (internal error).
Action Contact your IBM Support Center.
8
703
|
|
Explanation
Command scheduling failed during initialization of INGPXDST.
Action Check if the target task is available or check the netlog for any related NetView
error message.
12
11
Explanation
DST Termination. The SA z/OS communication manager is waiting to terminate
the DST because there is another task that is still using its resources. The waiting
time depends on the value of the global variable XDOMTIME. If XDOMTIME
contains a null string or an invalid value then DST termination will continue after
60 seconds. Otherwise, the value of XDOMTIME is multiplied by 5 seconds. For
example, if XDOMTIME=120 then the DST will wait 600 seconds.
Action Stop the REXX program that is using the SA z/OS communication services.
Chapter 2. Messages AOF000I to AOF969I
41
AOF350E
Table 3. Combinations of Error Types and Error Codes (continued)
Error Type Error Code Meaning
12
12
Explanation
DST Termination. The SA z/OS communication manager termination continued
but the SA z/OS sysplex communication block was not freed since another task
still holds a lock.
Action Stop the REXX program that is using the old SA z/OS communication
environment.
|
|
|
|
12
499
|
|
|
|
Action Check the return and reason codes. If necessary contact your IBM Support Center.
12
535
|
|
|
|
|
|
12
562
Explanation
Automation manager termination. The cleanup of a control block anchored to the
MTIB failed. The return code that will be supplied with this message is one of
those explained in the row of ERROR TYPE 4 and ERROR CODE 532.
Action Check the return code. If necessary contact your IBM Support Center.
12
602
572
|
|
|
|
Explanation
Automation manager termination error. The subtask shell termination failed.
Action Contact your IBM Support Center.
|
|
||
|
Explanation
DST Termination. The Automation manager termination is unable to unregister
task.
Explanation
DSR Termination. The DST Receiver Task could not be terminated.
Action Contact your IBM Support Center.
16
24
|
Explanation
RPC Pipe error. Pipe cannot be created. There is probably not enough storage.
Action Increase the region size.
|
||
||
|
|
|
16
|
||
||
|
|
|
|
|
|
16
|
||
||
||
||
|
|
16
42
44
100
503
527
48
64
132
146
328
504
514
529
555
56
128
144
510
525
554
592
Explanation
RPC Pipe error. Write failed, probably due to lack of storage.
Action For return codes 12, 16 or 56 increase the region size. Return code 84 indicates
that the write was canceled because of a DST termination request, and no action
is required. In case of any other return code, contact your IBM Support Center.
Explanation
RPC Pipe error. Close failed.
Action Contact your IBM Support Center.
Explanation
RPC Pipe error. An open failed because the RPC handle to be opened cannot be
found, is currently in use or is disabled. Error code 592 is a failing open during
retry.
Action Contact your IBM Support Center.
System Automation for z/OS Messages and Codes:
AOF350E
|
Table 3. Combinations of Error Types and Error Codes (continued)
|
Error Type Error Code Meaning
|
||
|
16
60
513
|
|
|
Action For return codes 12, 16 or 56 increase the region size. Return code 84 indicates
that the read was canceled because of a DST termination request, and no action is
required. In case of any other return code contact your IBM Support Center.
|
||
||
|
|
16
|
||
|
|
16
150
154
512
526
320
505
|
|
|
|
|
|
16
372
16
392
Explanation
RPC Pipe error. Create request for a remote pipe failed, probably due to lack of
storage for the pipe object.
Explanation
RPC Pipe error. Pipe is broken. The SA z/OS communication manager on a
pipe's target system was terminated. The pipe object is disabled, communication
is no longer possible.
Explanation
RPC Pipe error. The DST or the automation manager cannot send the pipe data to
the target. This is either due to an XCF problem, or an internal problem. The
return code (RET) is the return code of the RPC pipe service. The reason code
(RSN) describes the return code of the package service. The return and reason
codes are for diagnostic purposes only.
Action Check whether additional messages were issued, for example, HSAM1050E with
error type 24 and analyze whether an XCF error occurred. If necessary contact
your IBM Support Center.
16
521
|
Explanation
RPC Pipe error. A subtask cannot receive the data buffer.
Action Contact your IBM Support Center
|
||
||
||
|
|
|
|
|
|
16
|
|
|
|
|
20
|
Action Look for additional AOF350E messages that describe the reason for the broken
pipe, for example messages with error type 20. Contact your IBM Support Center.
Action Restart the SA z/OS communication manager (INGPXDST), or recycle NetView.
|
|
|
|
|
|
Explanation
RPC Pipe error. Pipe is broken.
Action Increase the NetView region size.
|
|
|
|
|
|
|
|
Explanation
RPC Pipe error. Read request failed, probably due to lack of storage.
575
597
598
599
623
638
400
Explanation
RPC Pipe error. The DST or the automation manager cannot send the pipe data to
the target system. The send request was retried but the retry limit exceeded.
Action The communication path is probably broken. Make sure that communication can
work properly. In case of XCF customize the XCF subsystem. For example,
increase the number of XCF buffers or install a new message buffer class
dedicated to the DST, or do both. Check whether there are additional AOF350 or
HSAM1050 messages that might explain the reason why communication does not
work. If necessary contact your IBM Support Center.
Explanation
RPC Command Handler error. The RPC command handler INGRXCMD failed.
The reason code contains the REXX line number where the error condition was
trapped.
Action Contact your IBM Support Center.
Chapter 2. Messages AOF000I to AOF969I
43
AOF350E
|
Table 3. Combinations of Error Types and Error Codes (continued)
|
Error Type Error Code Meaning
|
||
||
|
|
20
|
|
|
|
20
404
408
412
Action Look for the corresponding additional error message AOF350E with error type 16
for more information. If necessary, contact your IBM Support Center.
416
|
|
24
|
||
|
|
24
40
174
178
190
232
233
234
236
476
480
482
483
272
336
|
|
Explanation
System Service error. The specified XCF system service failed.
The return and reason codes of system service IXCxxxx, for example, IXCMSGO,
are described in z/OS MVS Programming Sysplex Services Reference (SA22-7618).
Action Check the return code and reason code of the system service. If necessary contact
your IBM Support Center.
Explanation
System Service error. The specified NetView service failed while a NetView
command cannot be scheduled.
Action Check the return code and reason code of the system service. If necessary contact
your IBM Support Center.
24
516
|
|
Explanation
System Service error. The activate recovery failed (ESTEA).
Action Check the return code and reason code of the system service. If necessary contact
your IBM Support Center.
|
||
24
523
556
|
|
|
24
537
|
|
|
||
||
|
|
|
|
Explanation
RPC Command Handler error. The RPC command handler INGRXCMD cannot
execute the command because the NetView PIPE failed.
Action Check the return code of the NetView PIPE command. Contact your IBM Support
Center.
|
||
||
|
|
|
||
||
|
|
|
|
|
|
|
Explanation
RPC Command Handler error. The RPC command handler INGRXCMD failed.
Action Ignore the error if this error occurs while the automation manager is terminating.
Explanation
System Service error. A task cannot be attached.
Action Check the return code and reason code of the system service. If necessary contact
your IBM Support Center.
24
44
568
569
576
577
601
620
643
Explanation
System Service error. The specified MVS system service failed.
Action Check the return code and reason code of the system service. If necessary contact
your IBM Support Center.
System Automation for z/OS Messages and Codes:
AOF350E
|
Table 3. Combinations of Error Types and Error Codes (continued)
|
Error Type Error Code Meaning
|
||
||
|
|
|
24
|
|
|
24
674
675
676
677
683
684
679
|
|
|
|
|
|
28
104
28
112
Explanation
REXX API error. A REXX API failed while a stem element retrieval was attempted
from the REXX variable pool, caused by INGPXSND() or INGPXRPC().
Explanation
REXX API error. A REXX API failed while attempting to set a stem element in the
REXX variable pool, caused by INGPXRCV().
Action Check the return code and reason code of the REXX IRX EXCOM API. If
necessary contact your IBM Support Center.
28
116
|
|
|
||
||
|
|
Explanation
NetView service failed while adding or removing a command processor.
Action Check the return code and reason code of the REXX IRX EXCOM API. If
necessary contact your IBM Support Center.
|
|
|
|
|
|
Action Check the return code of the PPI service. It is given in RSNCODE for 683,674
through 677, or RETCODE for 684. If necessary contact your IBM Support Center.
Action Check the return code and reason code of the PPI service. If necessary contact
your IBM Support Center.
|
|
|
|
|
|
Explanation
NetView PPI service failed.
Explanation
REXX API error. A REXX API failed while INGPXRCV() attempted to set the
number of stem elements variable (stem.0) in the REXX variable pool.
Action Check the return code and reason code of the REXX IRX EXCOM API. If
necessary contact your IBM Support Center.
28
120
296
312
Explanation
REXX API error. A call to the REXX API failed.
Action Check the return code and reason code of the REXX IRX EXCOM API. If
necessary contact your IBM Support Center.
Chapter 2. Messages AOF000I to AOF969I
45
AOF350E
|
Table 3. Combinations of Error Types and Error Codes (continued)
|
Error Type Error Code Meaning
|
||
||
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
32
|
|
|
36
84
88
92
96
182
186
198
204
216
220
292
332
340
485
487
488
493
496
498
500
543
560
567
585
586
594
595
596
608
613
624
626
631
621
640
678
680
685
380
Explanation
Storage problem. There is insufficient storage for the queue, table or buffer
operation requested.
Action Increase the region size.
Explanation
An abend occurred.
|
RET describes the system or user completion code of the abend.
|
RSN describes the reason code of the abend.
|
|
Action For the meaning of system completion code and reason code see z/OS manual
for system code.
|
|
The user completion code may be described in Language Environment Messages
Manual or in other z/OS components.
|
|
|
See also additional error messages from other z/OS components. For example,
message CEE5101C might be issued if you missed to assign an OMVS segment to
the user id.
46
System Automation for z/OS Messages and Codes:
AOF351E • AOF355E
Table 3. Combinations of Error Types and Error Codes (continued)
Error Type Error Code Meaning
36
523
This means that the data of an XCF request was received but it cannot be scheduled to the
Automation Manager receiver-queue because the corresponding thread is no longer
registered to receive requests. If this happens during termination of the Automation
Manager the message can be ignored.
Error code 556 is caused by error code 523 so message HSAM1050E with error code 556
may also appear.
36
nnn
Explanation
Internal error.
Action Contact your IBM Support Center.
40
440
444
448
452
456
460
464
468
Explanation
Environment error.
Action Start the DST INGPXDST.
System action: None.
|
|
AOF353I
|
|
|
|
|
|
|
|
Explanation: For Automation Control, the number of
Automation Agents that can run concurrently in the
same extended XCF communication group is limited to
three. The limit is reached and therefore the current
Automation Agent cannot join the extended XCF
group. The extended XCF communication group is
identified by the parameter PLEXID in the member
INGXINIT.
Explanation: An error was detected during
initialization of the system automation communication
manager Data Service Task (DST).
|
|
System action: Communication task continues but did
not join the extended XCF communication group.
|
Operator response: None.
System action: The Data Service Task terminates.
|
System programmer response: None.
Operator response: Refer to the documentation of
message AOF333I.
System programmer response: Contact your IBM
Support Center.
Classes: 0.
AOF351E
COMMUNICATION MANAGER
INITIALIZATION FAILED
Operator response: Analyze the problem, referring to
the explanation of message AOF350E. Correct your
input and retry the task.
System programmer response: None.
Classes: 0.
AOF352I
COMMUNICATION MANAGER
INITIALIZATION COMPLETE
AOF355E
EXTENDED XCF COMMUNICATION
DISABLED, LIMIT OF nn EXCEEDED
INCORRECT CALL TO FUNCTION
name RC=rc
Explanation: An error was detected during parameter
list validation of a system automation REXX API
function.
System action: The REXX function terminates due to a
REXX syntax error.
Explanation: The initialization module of the system
automation communication manger has successfully
initialized the Data Service Task (DST).
Operator response: Analyze the return code. Invoke
the REXX function name with a correct parameter list.
The return code rc can have one the following values:
System action: None.
Value
Meaning
Operator response: None.
4
An incorrect number of arguments was
specified.
System programmer response: None.
Classes: None.
Chapter 2. Messages AOF000I to AOF969I
47
AOF356E • AOF366I
Either the value of the data parameter is no
stem, or stem.0 is nonnumeric, or a negative
number.
8
12
The value of the handle parameter is too long.
16
The value of the records parameter is zero or
nonnumeric.
20
The value of the task parameter is too long.
24
The value of the target parameter is too long.
40
The handle parameter is required but no value
was specified.
44
The data parameter is required but no value
was specified.
48
The task parameter is required but no value
was specified.
The records parameter is required but no
value was specified.
52
System action: Processing continues.
Operator response: None.
System programmer response: None.
AOF364I
type entry INVALID TYPE OF
SUBSYSTEM. EXPECTING value1, GOT
value2, FOR MESSAGE msg
Explanation: A SA z/OS message trap routine is
processing a message. The job that issued the message
is associated with a subsystem that has a type that is
not valid for the message.
This typically happens when either the type is
unspecified or incorrectly specified, for example,
specified CICS for an IMS subsystem.
The variable type is the SUBSYSTEM.
The variable entry is the name of the subsystem in
error.
System programmer response: None.
The variable value1 is the TYPE that was expected
for this message.
Classes: 0.
The variable value2 is the TYPE specified in the
ACF.
AOF356E
COMMAND HANDLER INGRXCAM
FAILED: ERROR=xx FN=yy RC=zz
Explanation: The command handler failed with a
return code. It can have the following values:
Value
Meaning
4
Invalid RPC type
8
REXX function failed. If xx is 8 then yy shows
the return code from the REXX function.
12
NetView pipe failed. If xx is 12 then yy=null
and zz shows the return code from the pipe.
16
Buffer.0 is wrong
System action: The command handler terminates.
Operator response: Retry the operation. If the
problem persists, contact your system programmer.
System programmer response: Retry the operation. If
the problem persists, contact your system programmer.
AOF359I
DIAGNOSTIC INFO: MOD=module
INCIDENT=incident diagnostic-text
Explanation: The purpose of this message is to
provide diagnostic information to IBM service staff.
System action: Processing stops. Automation for the
message specified is not processed. This may cause
further automation errors if the message is required for
automation information, for example, UPMSG, etc.
Operator response: Report this error to your system
programmer. This is a configuration error.
System programmer response: Correct the
configuration of the subsystem specified in the Policy
Database. Rebuild the Automation Control File and
reload.
Classes: None.
AOF365I
NO ACTIVE LINK FOUND
Explanation: The link between a consumer subsystem
and a provider subsystem is already in the requested
state. The link status can be either ACTIVE or
INACTIVE.
System action: None.
Operator response: None.
System programmer response: None.
The variable module shows name of the module that
detected the incident.
Classes: None.
The variable incident shows a unique ID for an
internally detected incident.
AOF366I
The variable diagnostic-text shows useful text in free
format. The text depends on the incident that
occurred. For example, for INCIDENT=100, this is the
duplicate handle + seq-number.
48
The variable msg is the message that triggered the
problem.
System Automation for z/OS Messages and Codes:
NO DYNAMIC LINK CONFIGURED
IN THE POLICY BETWEEN consumer
AND provider
Explanation: Activating or deactivating a link between
a consumer subsystem and a provider subsystem failed
AOF367I • AOF432I
because the link was either not defined at all or it was
not defined as DYNAMIC in the automation policy.
The variable consumer is the subsystem name of the
consumer.
The variable provider is the subsystem name of the
provider.
System action: None.
Operator response: Verify that you defined the correct
consumer and provider names. If these are correct,
notify your system programmer.
System programmer response: Define a dynamic link
in the automation policy between the consumer and the
provider.
Classes: None.
AOF367I
LINK ACTIVATED BETWEEN consumer
AND provider
Explanation: Link activation was successful between
the consumer and the provider application.
problem persists, contact your system programmer.
System programmer response: Contact your IBM
Support Center.
Classes: None.
AOF403E
UNEXPECTED WAIT EVENT (WC=wc)
FROM command IN clist. PROCESSING
TERMINATED.
Explanation: A message was expected, but instead an
unexpected event code was returned.
System action: The requested function has not
completed successfully.
Operator response: Refer to NetView Customization:
Writing Command Lists for an explanation of the code. If
it is an unexplained wait code, for example, an error
code, contact your IBM Support Center. If it is a G
code, for example, GO, do not enter GO while waiting
for that command to process.
System programmer response: None.
The variable consumer is the subsystem name of the
consumer.
Classes: None.
The variable provider is the subsystem name of the
provider.
AOF408I
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF368I
LINK DEACTIVATED BETWEEN
consumer AND provider
Explanation: Link deactivation was successful
between the consumer and the provider application.
The variable consumer is the subsystem name of the
consumer.
The variable provider is the subsystem name of the
provider.
MISSING OR INVALID PARAMETER
parm DETECTED IN command.
PROCESSING TERMINATED.
Explanation: The command command contains an
invalid or missing parameter.
System action: Processing stops. The requested
function is not completed successfully.
Operator response: None.
System programmer response: Correct the function
call.
Classes: None.
AOF415I
NO SERVICE PERIODS DEFINED FOR
applid
System action: None.
Explanation: The Automation engine found no service
periods defined in the control file for this application.
Operator response: None.
System action: Processing continues.
System programmer response: None.
Operator response: None. This is an internal message.
Classes: None.
System programmer response: None.
Classes: None.
AOF401E
UNEXPECTED TIMEOUT FROM
command in clist. PROCESSING
TERMINATED.
AOF432I
INVALID EVENT NAME
Explanation: A message was expected but was not
received before the ‘WAIT’ time expired.
Explanation: The event name was not found. Either it
is not defined in system automation, or it contains
invalid characters.
System action: The requested function has not
completed successfully.
System action: Processing continues.
Operator response: Retry the operation. If the
Operator response: Enter a valid event name.
Chapter 2. Messages AOF000I to AOF969I
49
AOF435I • AOF449I
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
AOF435I
AOF442I
TYPE AN EVENT NAME AND PRESS
ENTER
Explanation: System automation is waiting for an
event name to be specified.
System action: Processing continues.
Operator response: Type a valid event name.
System programmer response: None.
Classes: None.
AOF436I
TYPE A RESOURCE NAME AND
PRESS ENTER
Explanation: System automation is waiting for an
application name to be specified.
SET|UNSET EVENT event DONE FOR
ALL AFFECTED APPLICATIONS ON
system
Explanation: The INGEVENT routine successfully
completed the status file update for this event and all
affected applications.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: None.
AOF447I
DATE OUT OF RANGE
Operator response: Type a valid application name.
Explanation: The date could generate a schedule
conflict because it is in the range of 12/26/yy and
12/31/yy where yy is computed by the common global
variable AOCCENTURYSWITCH and the current year.
System programmer response: None.
System action: Processing continues.
Classes: None.
Operator response: Change the date.
System action: Processing continues.
System programmer response: None.
AOF438I
EVENT event DEFINED BUT NOT
USED BY ANY TRIGGER
Explanation: The event is defined in the automation
control file (ACF), but it is not used by any trigger in
the sysplex.
Classes: None.
AOF448I
INVALID DATE
Explanation: The specified date is not valid.
System action: Processing continues.
System action: Processing continues.
Operator response: None.
Operator response: Specify a valid date.
System programmer response: None.
System programmer response: None.
Classes: None.
AOF440I
NO TRIGGER DEFINED FOR applid
Explanation: There is no trigger defined for the
specified application.
System action: Processing continues.
Operator response: None.
System programmer response: None.
AOF449I
OVERLAP EXISTS BETWEEN ACTIVE
type TIMESLOT timeslot AND
SPECIFIED type TIMESLOT timeslot
Explanation: The specified timeslot is in conflict with
the currently active timeslot. A timeslot is active when
the start time has passed, but not the end time.
Classes: None.
The variable type shows the type of the timeslot (UP
or DOWN).
AOF441E
The variable timeslot shows the start and end time
of the time window.
SETEVENT FAILED: FUNCTION
PARAMETER MUST BE SET OR
UNSET
Explanation: SETEVENT/INGEVENT failed because
the function parameter was neither SET nor UNSET.
System action: Processing continues.
Operator response: Specify the correct function
parameter SET or UNSET.
50
System Automation for z/OS Messages and Codes:
System action: None.
Operator response: Correct the command.
System programmer response: None.
Classes: None.
AOF450I • AOF458I
AOF450I
ORIGINAL TIME HAS PASSED AND
CANNOT BE CHANGED
Explanation: A time specified on the service periods
panel is before the current time.
System action: Processing continues.
Operator response: Enter service period times later
than the current time.
System programmer response: None.
Classes: None.
AOF454I
NEXT START TIME IS NOT ‘****’
Explanation: The ‘****’ in service periods indicates
that the service period will remain active the next day.
If the last stop time is ‘****’, the next start time must
also be ‘****’ indicating the continuity. In this case, the
operator modified the service hours and specified ‘****’
as the last stop time, but the next start time is not ‘****’.
System action: Processing continues.
Operator response: Either change the start time to
‘****’, or change the last stop time accordingly.
System programmer response: None.
AOF451I
PREVIOUS STOP TIME IS NOT ‘****’
Explanation: The ‘****’ in service periods shows that
the service period will remain active the next day. If the
last stop time is ‘****’, the next start time must also be
‘****’ indicating the continuity. Here, the operator
modified the service hours and specified ‘****’ as the
first start time, but the previous stop time is not ‘****’.
System action: Processing continues.
Operator response: Either change the last stop time to
‘****’, or change the first start time appropriately.
System programmer response: None.
Classes: None.
Classes: None.
AOF456I
No times allowed after ‘DOWN’
Explanation: When ‘DOWN’ is the first start or stop
time, no times can be entered later that day. The
operator modified the service hours and specified
‘DOWN’ as the first start time, but additional times
follow it.
System action: Processing continues.
Operator response: Correct the service hours.
System programmer response: None.
Classes: None.
AOF452I
PREVIOUS STOP TIME IS ‘****’.
Explanation: The operator modified the service hours
and did not specify ‘****’ as the first start time, but the
previous day’s last stop time is ‘****’.
System action: Processing continues.
Operator response: Either change the last stop time to
‘****’, or change the first start time appropriately.
System programmer response: None.
Classes: None.
AOF457I
BOTH 'FROM' AND 'TO' TIMES MUST
BE ENTERED, OR BOTH MUST BE
BLANK
Explanation: A 'From' or 'To' time was entered. Either
both 'From' and 'To' times must be entered, or both
must be blank.
System action: Processing continues.
Operator response: Enter both 'From' and 'To' times,
or blank both out.
System programmer response: None.
AOF453I
NEXT START TIME IS ‘****’
Explanation: The next day’s first start time is ‘****’,
but when the operator modified the service hours, ‘****’
was not specified as the last stop time.
System action: Processing continues.
Operator response: Either change the start time to
‘****’, or change the last stop time accordingly.
System programmer response: None.
Classes: None.
Classes: None.
AOF458I
NO TIMES ALLOWED AFTER ‘****’
Explanation: Because ‘****’ shows that a service period
will remain active until the next day, no times are
allowed after the ‘****’.
System action: Processing continues.
Operator response: Correct the service hours.
System programmer response: None.
Classes: None.
Chapter 2. Messages AOF000I to AOF969I
51
AOF459I • AOF468I
AOF459I
INVALID TIME
Explanation: The specified time is not valid. The time
must be between 0000 and 2359.
System action: Processing continues.
System programmer response: None.
AOF465I
TRIGGER trigger HAS NO SERVICE
PERIODS
Operator response: Enter a valid time.
Explanation: No service periods are defined for this
trigger.
System programmer response: None.
System action: Processing continues.
Classes: None.
Operator response: None.
System programmer response: None.
AOF461I
TIME MUST ALSO BE ‘DOWN’.
Classes: None.
Explanation: Either in the first Start or in the Stop
field of the window, DOWN was specified. DOWN
must be specified in both, the first Start and first Stop
window.
AOF466I
System action: Processing continues.
Explanation: The time change specified was prior or
equal to the current time.
Operator response: Either specify DOWN in both, the
Start and Stop first service period fields, or specify
valid times in both.
System programmer response: None.
Classes: None.
CHANGED TIME MUST BE LATER
THAN CURRENT TIME
System action: Processing continues.
Operator response: Specify a time change later than
the current time, or quit the function.
System programmer response: None.
Classes: None.
AOF462I
ONLY THE FIRST START TIME MAY
BE ‘****’
Explanation: ‘****’ was specified in a Start field other
than the first one. ‘****’ is a valid entry only in the first
Start field, because it indicates that a service period
continues from the previous day.
System action: Processing continues.
Operator response: Correct the time.
System programmer response: None.
Classes: None.
AOF463I
TIME MUST BE NUMERIC
Explanation: The 'From' or 'To' time specified is not
numeric, asterisks, or DOWN.
System action: Processing continues.
Operator response: Correct the time.
System programmer response: None.
Classes: None.
AOF467I
DELETION NOT ALLOWED BECAUSE
IT CREATES A SCHEDULE CONFLICT
Explanation: The overrides cannot be deleted because
this would create a conflict in the existing schedule(s).
At first, the earliest start time of the regular schedule
and of the override is determined. Then the latest stop
time of both schedules is determined. If the actual time
of the day is between those two times specified, this
results in a schedule conflict. DOWN-DOWN is treated
as ‘0000-2400’.
System action: Processing continues.
Operator response: Change the schedule to eliminate
the conflict, or quit the function.
System programmer response: None.
Classes: None.
AOF468I
TYPE ‘D’ IF DELETE REQUIRED
Explanation: An invalid character was specified in the
Delete field.
System action: Processing continues.
AOF464I
THE FIRST 'FROM' AND 'TO' TIME
CANNOT BE BLANK
Explanation: The first 'From' and 'To' time must be
specified. They are required parameters.
System action: Processing continues.
Operator response: Correct the time by specifying
valid times in the first fields.
52
System Automation for z/OS Messages and Codes:
Operator response: Type ‘D’ to delete the override.
System programmer response: None.
Classes: None.
AOF469I • AOF501E
AOF469I
'FROM' TIME MUST BE LATER THAN
PREVIOUS 'TO' TIME
AOF478I
WILDCARDS ARE NOT SUPPORTED
Explanation: The 'From' time of the service window is
not later than the 'To' time of the previous service
window.
Explanation: The INGEVENT command supports
down-level systems. Because a down-level system does
not know a wildcard, this support is suppressed for the
time these down-level systems are supported.
System action: Processing continues.
System action: The command is not executed.
Operator response: Correct either the 'From' or the
'To' time.
Operator response: Correct the parameter and reissue
the command.
System programmer response: None.
System programmer response: None.
Module: INGRYEV0
AOF470I
'TO' TIME MUST BE LATER THAN
'FROM' TIME
Explanation: The 'To' time of the service window is
not later than the 'From' time of the same service
window.
System action: Processing continues.
Operator response: Correct either the 'From' or the
'To' time.
System programmer response: None.
AOF475I
EVENT event IS NOT USED BY
RESOURCE applid
Explanation: The event is not defined in the trigger
that is used by the resource.
The variable event shows the event that is not used.
The variable applid shows the APPLID of the
resource.
System action: The command terminates immediately.
Operator response: Check the scope parameters of the
command, correct the value(s). Then issue the
command again.
System programmer response: None.
AOF476I
EVENT event IS NOT USED ON
SYSTEM system
Explanation: The event is defined but it is not used by
any trigger on the specified system.
The variable event shows the event that is not used.
The variable system shows the name of the system.
System action: The command terminates immediately.
Operator response: Check the RANGE parameter of
the command and correct the value. Then issue the
command again.
System programmer response: None.
AOF479I
SERVICE PERIOD REQUESTS TO
UP-LEVEL SYSTEMS ARE NOT
SUPPORTED
Explanation: A service period request in line mode to
an up-level system is not supported. The reason for this
is that the definitions of service periods on two
different system levels, for example SA OS/390 1.3 and
SA OS/390 2.1, are not compatible.
System action: The request is rejected.
Operator response: None.
System programmer response: None.
Module: INGRVP90
AOF501E
time : RECOVERY FOR restype resname
HALTED - number ERRORS SINCE
error_time ON error_date - CRITICAL
ERROR THRESHOLD EXCEEDED
Explanation: The resource has experienced the
indicated number of errors during the time interval
defined in the automation control file for the critical
error threshold.
The variable time shows the time the exception
message was generated.
The variable restype shows the type of the resource.
The variable resname shows the name of the
resource.
The variable number shows the number of errors
that has occurred.
The variable error_time shows the time of the first
error to occur within the time interval.
The variable error_date shows the date of the first
error to occur within the time interval.
System action: If resname is a network resource, the
recovery process is ended. If resname is a system
resource, the recovery process is ended or the
appropriate commands are issued.
Operator response: None.
System programmer response: None.
Classes: 40 41 44 51.
Chapter 2. Messages AOF000I to AOF969I
53
AOF502I • AOF511I
AOF502I
time : RECOVERY FOR restype resname,
CONTINUING - number ERRORS
SINCE error_time ON error_date FREQUENT ERROR THRESHOLD
EXCEEDED
Explanation: The frequent error threshold has been
exceeded for a resource. This message reports the
number of errors that occurred during the time interval
defined in the automation control file for the frequent
error threshold.
The variable time shows the time the exception
message was generated.
The variable restype shows the type of the resource.
The variable resname shows the name of the
resource.
The variable number shows the number of errors
that occurred.
The variable error_time shows the time of the first
error that occurred within the time interval.
The variable error_date shows the date of the first
error that occurred within the time interval.
System action: If the resource identified in this
message is a network resource, the recovery process
continues. If it is a system resource, the appropriate
commands are issued.
System action: If the resource identified in this
message is a network resource, the recovery process
continues. If it is a system resource, the appropriate
commands are issued.
Operator response: Contact your system programmer.
System programmer response: Make sure the policy
for shutting down this resource in the automation
control file is accurate. Determine whether other action
needs to be taken.
Classes: 40 43 52.
AOF510I
time : resname flag FLAG HAS BEEN SET
TO status BY OPERATOR operator_ID
Explanation: The flag status for the resource identified
in this message has been set as indicated.
The variable time shows the time when this message
was generated.
The variable resname shows the name of the
resource.
The variable flag shows the name of the automation
flag that is set.
The variable status shows the automation status.
The variable operator_ID shows the name of the
operator who changed the automation status.
Operator response: Contact your system programmer.
System action: The automation status is set.
System programmer response: Make sure the policy
for shutting down this resource in the automation
control file is accurate. Determine whether other action
needs to be taken.
Operator response: You can issue the DISPFLGS
command to view actual and effective values for the
specific resource flag.
Classes: 40 43 51.
AOF503I
time : RECOVERY FOR restype resname
CONTINUING - number ERRORS
SINCE error_time ON error_date INFREQUENT ERROR THRESHOLD
EXCEEDED
Explanation: The infrequent error threshold has been
exceeded for a resource. This message reports the
number of errors that occurred during the time interval
defined in the automation control file for the infrequent
error threshold.
The variable time shows the time the exception
message was generated.
The variable restype shows the type of the resource.
The variable resname shows the name of the
resource.
The variable number shows the number of errors
that has occurred.
The variable error_time shows the time of the first
error to occur within the time interval.
The variable error_date shows the date of the first
errorto occur within the time interval.
54
System Automation for z/OS Messages and Codes:
System programmer response: None.
Classes: 40, 43.
AOF511I
time : member AUTOMATION
CONTROL FILE COMMON VALUES
HAVE BEEN INITIALIZED
Explanation: The automation control file data has
been used to create common variables used throughout
the automation process.
The variable time shows the time this message was
generated.
The variable member shows the name of the
configuration member used.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF512I • AOF531I
AOF512I
time : resname flag FLAG HAS BEEN
RESET BY OPERATOR operator_ID. THE
EFFECTIVE FLAG VALUE IS: efinfo
Explanation: The flag status for the resource identified
in this message has been set as indicated.
The variable time shows the time when this message
was generated.
The variable resname shows the name of the
resource.
The variable flag shows the name of the automation
flag that is set.
The variable operator_ID shows the name of the
operator who changed the automation status.
The variable efinfo shows the effective value of flag
after RESET operation.
The additional EFFECTIVE FLAG VALUE information
is only displayed for INGAUTO RESET with
SCOPE=ONLY.
System action: The automation status is set.
AOF523W
SYSTEM target IS INACTIVE: text
Explanation: Definition or hardware problem
detected.
The variable target shows the name of the target
system.
System action: System target status changed to
inactive.
Operator response: Contact your system programmer.
System programmer response: Determine the cause of
the problem from the message text. Correct the problem
as indicated in the message text.
Classes: 0.
AOF524I
MONITORING target : text
Explanation: Operational or configuration problem
detected.
The variable target shows the name of the target
system.
Operator response: You can issue the DISPFLGS
command to view actual and effective values for the
specific resource flag.
System action: None.
System programmer response: None.
System programmer response: Correct the problem as
indicated in the message text.
Classes: 40, 43.
Operator response: Try to correct the problem.
Contact your system programmer if required.
Classes: 0.
AOF521I
MONITORING target FAILED : text
Explanation: Monitoring failed for the reason specified
in the message text.
The variable target shows the name of the target
system.
System action: None.
Operator response: Contact your system programmer.
AOF530I
time : CONFIGURATION TIMER
PROCESSING HAS BEEN
COMPLETED
Explanation: This message issued when all the timer
entries in the automation control file have been
processed and the required actions have been
performed.
The variable time shows the time this message was
generated.
System programmer response: Determine the cause of
the problem from the message text. Contact the IBM
support representative if required.
System action: Processing continues.
Classes: 0.
Operator response: None.
AOF522I
SYSTEM target IS LOADING: text
Explanation: Target system is loading. The message
text indicates the system loading status.
The variable target shows the name of the target
system.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 0.
System programmer response: None.
Classes: 40, 43.
AOF531I
time : OUTSTANDING REPLY
PROCESSING HAS BEEN
COMPLETED
Explanation: This message is issued when outstanding
replies have been captured and forwarded to SDF
(Status Display Facility). It is produced at system
automation startup, when SDF is recycled, or whenever
the gateway connection to the focal point is established,
changed, or reset.
Chapter 2. Messages AOF000I to AOF969I
55
AOF532I • AOF540I
The variable time shows the time this message was
generated.
System action: Processing continues.
Operator response: None.
console identified in this message could not be
processed.
The variable time shows the time this message was
generated.
System programmer response: None.
The variable resname shows the name of the
resource.
Classes: 40, 43.
The variable status shows the status of the resource.
The variable restype shows the type of the resource.
AOF532I
time : AUTOMATION ENVIRONMENT
HAS BEEN INITIALIZED
Explanation: The automation environment has been
initialized.
The variable time shows the time this message was
generated.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
The variable cmd shows the command to be
processed.
The variable console shows the console-ID or
console-CUU having difficulty.
The variable text shows the short form of the
message.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Determine whether a
configuration error or a user error exists, by reviewing
the values supplied and the automation control file.
Classes: 40 43 52.
AOF534I
time : AUTOMATION TIMERS HAVE
BEEN INITIALIZED OR RESTARTED
Explanation: The automation timers have been
initialized or restarted.
The variable time shows the time this message was
generated.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF538I
time : OUTSTANDING REPLY: MVS reply_ID msg_text
Explanation: Automation will not reply to an
outstanding reply.
The variable time shows the time this message was
generated.
The variable reply_ID identifies the outstanding
reply that will not be replied to.
The variable msg_text shows the message text for
the outstanding reply.
System action: None.
AOF535I
time : AUTOMATION ENVIRONMENT
HAS BEEN CLEARED
Explanation: After an ACF COLD command is issued
to reload an automation control file, the existing
common global variables are cleared in readiness for
fresh data.
The variable time shows the time this message was
generated.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF537I
time : resname status - restype resname cmd
COMMAND(S) NOT FOUND FOR
console - text
Explanation: One or more commands issued from the
56
System Automation for z/OS Messages and Codes:
Operator response: Reply to outstanding reply
accordingly.
System programmer response: None.
Classes: 40 41.
AOF540I
time : INITIALIZATION RELATED
PROCESSING HAS BEEN
COMPLETED
Explanation: Processing required to complete
initialization after the automation environment has
been initialized has been completed.
The variable time shows the time that the message
was generated.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF541I • AOF551I
AOF541I
time : SYSTEM MONITORING
FUNCTION COMPLETED FOR
resourcelist
Operator response: None.
System programmer response: Correct the problem by
changing the coding for the keyword or value.
Explanation: Indicates completion of a monitor cycle
initiated either by using a timer or by operator request.
Classes: None.
v The variable time shows the time that the message
was generated.
AOF546I
v The variable resourcelist shows one of:
– ALL SUBSYSTEMS WITH NO INDIVIDUAL MONITORING
(MONITOR $SYSTEM)
clist: NO FUNCTION REQUESTED,
NOTHING DONE
Explanation: No function keyword was specified to
cause an action. No action was taken.
– ALL SUBSYSTEMS (MONITOR ALL or *)
System action: None.
– A list of resources that monitoring has been
completed for as the result of a single subsystem
or wildcard request
Operator response: Contact your system programmer.
System programmer response: None.
System programmer response: Determine the cause of
the problem. See whether message AOF545I was also
issued. It is likely that a coding error caused the
problem. For example, a keyword might have been
specified with no default value possible, due to a
coding error.
Classes: 40, 43.
Classes: None.
System action: Processing continues.
Operator response: None.
AOF543E
time : COMMAND cmd WAS
CANCELED. RC=retcode
Explanation: Command cmd was canceled because the
prevailing environmental conditions for system
automation were not adequate for the command to
complete successfully.
The variable time shows the time this message was
generated.
The variable cmd shows the command that was
affected.
The variable retcode shows the condition code
identifying the reason for the cancelation of the
command. outstanding reply.
AOF550I
STATUS OF monitor MONITOR :
OBSERVED=observed HEALTH=health text
Explanation: This message is generated when either
the status of a monitor resource or the health status of
the objects that the monitor is watching changes. It
shows the resource's new status.
The variable monitor shows the name of the monitor
resource.
The variable observed shows the observed status of
the monitor resource.
The variable health shows the health status of the
monitored objects.
The variable text shows additional information.
System action: The command is terminated.
System action: None.
Operator response: Try re-issuing the command later.
Operator response: None.
System programmer response: None.
System programmer response: None.
Classes: 40, 43.
AOF551I
AOF545I
clist: KEYWORD keyword HAS AN
INVALID VALUE value, PARAMETER
IGNORED
Explanation: Either the keyword identified in this
message or the value specified for it is not valid. The
parameter containing this value will be ignored.
The variable clist shows the name of the command
list.
The variable keyword shows the keyword that is not
valid or has a value that is not valid.
The variable value shows the value specified for the
keyword.
System action: None.
group GROUP STATUS FOR type
APPLGROUP IS observed
Explanation: This message is generated when the
status of an application group changes. It shows the
group's new status.
The variable group shows the name of the
application group.
The variable type shows whether the application
group belongs to a system or a sysplex.
The variable observed shows the observed status of
the application group.
System action: None.
Operator response: None.
System programmer response: None.
Chapter 2. Messages AOF000I to AOF969I
57
AOF561A • AOF565A
AOF561A
time : JES2 RESOURCE DRAINING - opt
COMMAND NOT FOUND TO FORCE
DRAIN. OPS ACTION REQUIRED
Classes: 40, 43, 44, 46.
AOF564A
Explanation: The indicated resource is shutting down,
but no commands were found to drain the indicated
resource with the method of FORCE.
The variable time shows the time this message was
generated.
The variable opt shows the parameter for FORCE
DRAIN.
System action: None.
Operator response: Manually drain the indicated
resource.
System programmer response: Use the customization
dialogs to add commands for the indicated action to
the automation control file. For further information,
refer to IBM Tivoli System Automation for z/OS Defining
Automation Policy.
Classes: 40, 43, 44, 46.
AOF562I
time : JES2 RESOURCE DRAINING resource IS status. OPS ACTION
REQUIRED TO DRAIN
Explanation: The JES2 resource status is not ACTIVE,
INACTIVE, DRAINING, or DRAINED.
The variable time shows the time this message was
generated.
The variable resource shows the name of the
resource.
The variable status shows the JES2 resource status.
System action: None.
Operator response: Manually drain the resource.
System programmer response: None.
Classes: 40, 43, 44, 46.
{time: JES2 SHUTTING DOWN - message
- OPERATOR INTERVENTION
REQUIRED | title | task_names|
job_names| device_names}
Explanation: This message reports that JES2 is being
shut down and there are jobs or tasks (or both) that are
active, or devices that have not yet been drained, or all
of these. This message is followed by one or more
AOF654A messages that lists the jobs or tasks that are
active (job_names, task_names) or the devices that have
not been drained (device_names). Each of these messages
shows a list of job names, task names or device names.
v The variable time
v The variable message
v The variable title is one of:
TASKS
JOBS
DEVICES
v The variable task_names shows the names of tasks
that are still active.
v The variable job_names shows the names of jobs that
are still active.
v The variable device_names shows the names of
devices that are still active.
System action: The system waits for devices and
initiators to be drained. This message is repeated until
JES2 is shut down.
Operator response: Wait for devices and jobs to
complete and automation to shutdown JES2.
Commands can be issued to force jobs or drain devices.
Consult your system programmer if the situation
requires manual intervention.
System programmer response: If this situation
requires immediate shutdown instruct operations
personnel as to how to accomplish this.
Classes: 40, 43, 44, 46.
AOF563A
time : JES2 RESOURCE DRAINING UNKNOWN RESTYPE: resource. OPS
ACTION REQUIRED TO DRAIN
Explanation: The resource identified in this message is
unknown.
The variable time shows the time this message was
generated.
The variable resource shows the name of the
resource.
System action: None.
Operator response: Manually drain the resource.
System programmer response: Check the netlog for
further information and perform problem
determination.
58
System Automation for z/OS Messages and Codes:
AOF565A
time : JES2 RESOURCES DRAINING
BUT DRAIN COMMAND TURNED
OFF ON subsystem_function ENTRY FOR
resource_name - recommendation
Explanation: JES2 resources are draining. However,
the drain command is turned off for the identified
subsystem function (subsystem_function) and resource
(resource_name).
The variable time shows the time this message was
generated.
The variable subsystem_function shows the function
being performed.
The variable resource_name shows the name of the
resource.
AOF566I • AOF571I
The variable recommendation shows an action
recommended for solving the problem.
AOF569I
System action: None.
Operator response: Issue commands to drain the
resource identified in this message. Contact your
system programmer.
System programmer response: If you want to
automate draining of the resource identified in this
message, use the customization dialogs to correct the
automation control file entry for the subsystem function
and resource. For more information, refer to IBM Tivoli
System Automation for z/OS Defining Automation Policy.
Classes: 40, 43, 44, 46.
time : STATUS OF domain INBOUND
GATEWAY FROM DOMAIN
target_domain IS status
Explanation: This message shows the status of the
inbound gateway from the requested target domain to
this domain.
The variable time shows the time this message was
generated.
The variable domain shows the name of this domain.
The variable target_domain shows the requested
target domain connected to this domain.
The variable status shows the current status of the
gateway connection.
System action: None.
AOF566I
time: JES2 PROCESSING REJECTED IN
command - JES2 NOT IN SHUTDOWN
PROCESS
Explanation: Shutdown related JES2 processing
rejected in routine command, because shutdown isn't in
progress for JES2.
The variable time shows the time this message was
generated.
The variable command shows the name of the
routine, rejecting JES2 processing.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the netlog for
further information on why command has been issued
outside the shutdown process of JES2.
Classes:None
AOF568I
Operator response: None.
System programmer response: None.
Classes: 40, 43, 44, 46.
AOF570I
time : ISSUED "command" FOR restype
resname - text
Explanation: A command has been issued for the
resource identified in the message.
The variable time shows the time this message was
generated.
The variable command shows the command that has
been issued.
The variable restype shows the type of the resource.
The variable resname shows the name of the
resource.
The variable text shows additional information.
time : STATUS OF domain OUTBOUND
GATEWAY TO DOMAIN target_domain
IS status
Explanation: This message shows the status of the
outbound gateway from this domain to the target
domain.
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
The variable time shows the time this message was
generated.
AOF571I
The variable domain shows the domain initiating the
connection to the target domain.
Explanation: This message is generated when the
status of a resource changes. It shows the resource’s
new status.
The variable target_domain shows the domain that
the gateway is connected to.
The variable status shows the current status of the
gateway connection.
System action: None.
Operator response: None.
time : resname SUBSYSTEM STATUS
FOR JOB job_name IS status - text
The variable time shows the time this message was
generated.
The variable resname shows the name of the
resource.
The variable job_name shows the name of the job.
System programmer response: None.
The variable status shows the new status of the
resource.
Classes: 40, 43, 44, 46.
The variable text shows additional information.
System action: None.
Chapter 2. Messages AOF000I to AOF969I
59
AOF572I • AOF576A
Operator response: None.
AOF574I
System programmer response: None.
Classes: 40 43 45.
AOF572I
CGLOBALS NOT INITIALIZED FOR
AUTOMATED FUNCTION autofunc UNABLE TO ROUTE COMMAND
command, operand_1, operand_2, operand_3
Explanation: The command identified in this message
could not be routed properly. The first three operands
of the command are shown in the message, to aid
analysis of the problem.
The variable autofunc shows the automated function
that the command could not be routed to. If no
automated function was specified, this will be
blank.
Explanation: Recovery has been started for a job.
The variable time shows the time this message was
generated.
The variable job_name shows the name of the job
that recovery has been started for.
The variable text shows the message text received.
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40 43 45.
AOF575A
The variable command shows the command that was
not routed properly.
The variable operand_1 shows the first operand of
the command. This variable is blank if the
command has no required operands.
The variable operand_2 shows the second operand of
the command. This variable is blank if the
command has less than two required variables.
The variable operand_3 shows the third operand of
the command. This variable is blank if the
command has less than three required variables.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the netlog for
messages related to an initialization failure. Determine
the cause of the failure and correct the problem.
Classes: 40 43 45.
AOF573I
time : AUTOMATED task restype HAS
BEEN RESTARTED
Explanation: An automated task has been restarted.
The variable time shows the time this message was
generated.
The variable task shows the task identifier of the
task that has been restarted.
The variable restype shows the type of the resource.
System action: None.
Operator response: None.
time : RECOVERY INITIATED, JOB
job_name, - RECEIVED MSG “text”
time : JOB job_name HAS ENDED AUTOMATED RECOVERY NOT IN
PROGRESS - OPERATION
INTERVENTION REQUIRED
Explanation: A job has ended and automation has
determined that operator intervention is required.
The variable time shows the time this message was
generated.
The variable job_name shows the name of the job
that ended.
System action: Automation is discontinued for the
specified job.
Operator response: Determine what is wrong with the
job and contact your system programmer.
System programmer response: Review the netlog to
determine when and why processing of the job failed.
You might need to modify the automation control file
to correct the problem if you can find no other cause of
the failure.
Classes: 40 41 44 45 46.
AOF576A
time : JOB job_name HAS status - autotype
AUTOMATION SET OFF OPERATION INTERVENTION
REQUIRED
Explanation: A job has ended and automation is set to
OFF for the resource. Operator intervention is required
to restart the resource.
The variable time shows the time this message was
generated.
System programmer response: None.
The variable job_name shows the name of the job
that ended.
Classes: 40 43 45.
The variable status shows the status of the resource.
The variable autotype shows the type of automation.
System action: None. No automation is attempted.
Operator response: Restart the resource.
60
System Automation for z/OS Messages and Codes:
AOF577E • AOF581I
System programmer response: None.
Classes: 40 41 44 45 46.
AOF577E
time : RECOVERY FOR restype resname
(JOB job_name) HALTED - CRITICAL
THRESHOLD EXCEEDED
Explanation: Automated recovery of a resource will
not occur because the critical error threshold set for the
resource has been exceeded. Operator intervention is
required to restart the resource.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource.
The variable resname shows the name of the
resource.
The variable job_name shows the name of the job.
System action: No automated recovery of the resource
occurs.
resource has been exceeded, but automation continues
the recovery.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource that
automated recovery is occurring for.
The variable resname shows the name of the
resource that automated recovery is occurring for.
The variable job_name shows the name of the job.
System action: Automated recovery for the resource
continues.
Operator response: Notify your system programmer.
System programmer response: Check the netlog for
further information as to why the indicated resource
failed.
Classes: 40 43 52.
AOF580I
Operator response: Contact your system programmer.
System programmer response: Check the netlog for
further information on why the resource has failed.
Classes: 40 41 44 50.
time : auto AUTOMATION FOR restype
resname (JOB job_name job_number) IS
SET OFF - AUTOMATION NOT
ATTEMPTED FOR MSG text
Explanation: Automation has been set to OFF for a
resource. As a result, no automation has been
attempted for the message shown.
time : RECOVERY FOR restype resname
(JOB job_name) CONTINUING FREQUENT THRESHOLD EXCEEDED
The variable time shows the time this message was
generated.
Explanation: A resource has failed and automated
recovery is occurring. The frequent error threshold set
for the resource has been exceeded, but automation
continues the recovery.
The variable restype shows the type of resource that
automation has been set OFF for.
AOF578I
The variable time shows the time this message was
generated.
The variable restype shows the type of resource that
failed.
The variable resname shows the name of the
resource that failed.
The variable job_name shows the name of the job.
The variable auto shows the type of automation.
The variable resname shows the name of the
resource that automation has been set OFF for.
The variable job_name shows the name of the job.
The variable job_number shows the number of the
job.
The variable text shows the message that has not
been automated.
System action: None.
System action: Automated recovery of the resource
continues.
Operator response: None.
Operator response: Notify your system programmer.
Classes: 40, 43, 44.
System programmer response: Check the netlog for
further information on why the resource has failed.
AOF581I
Classes: 40 43 51.
AOF579I
time : RECOVERY FOR restype resname
(JOB job_name) CONTINUING INFREQUENT THRESHOLD
EXCEEDED
Explanation: Automated recovery is occurring for a
resource. The infrequent error threshold set for the
System programmer response: None.
time : autotype SUCCESSFUL FOR
resource - text
Explanation: Automation caused by a message was
successful for a resource.
The variable time shows the time this message was
generated.
The variable autotype shows the type of automation.
The variable resource shows the name of the
resource that automation was successful for.
Chapter 2. Messages AOF000I to AOF969I
61
AOF582A • AOF586A
The variable text shows the message that caused
automation to be initiated.
AOF584I
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40 43 45.
AOF582A
time : RECOVERY UNSUCCESSFUL JOB job_name - OPERATOR
INTERVENTION REQUIRED FOR
MESSAGE text
Explanation: Recovery was not successful for a job.
Operator intervention is required for the message
shown, which could not be automated.
The variable time shows the time this message was
generated.
The variable job_name shows the name of the job
that recovery was not successful for.
The variable text shows the message that could not
be automated.
System action: None.
Operator response: Manual intervention is required to
handle the problem.
System programmer response: Determine from the
netlog why recovery was unsuccessful. Review the
commands coded in the automation control file.
Classes: 40 43 44 45 46.
AOF583I
time : auto AUTOMATION FOR restype
resname (JOB job_name) IS SET OFF AUTOMATION NOT ATTEMPTED
Explanation: Automation has been set to OFF for
resource. As a result, no automation has been
attempted.
The variable time shows the time this message was
generated.
The variable auto shows the type of automation flag.
time : resname autotype IS SET ON autotype action NOT FOUND FOR restype
resname - "text"
Explanation: Automation was set ON for a resource,
but no commands or replies were found in the
automation control file for the type of automation
described by the variable autotype.
The variable time shows the time this message was
generated.
The variable resname shows the resource name.
The variable autotype shows the type of automation
that no commands or replies were found for.
The variable action shows the type of action that
should have been taken. Possible values are
COMMAND and REPLY.
The variable restype shows the type of resource.
The variable text shows the message that called
automation.
System action: Automation is not performed for the
message shown.
Operator response: Notify your system programmer.
System programmer response: Check the entries in
the automation control file and correct them as needed.
Classes: 40, 43, 44.
AOF585I
time : autotype OF resname IS ALREADY
IN PROGRESS - text
Explanation: Automation is in progress for a resource.
No additional automation of the same type will occur
until the current automation is complete.
The variable time shows the time this message was
generated.
The variable autotype shows the type of automation
in progress.
The variable resname shows the name of the
resource that automation is in progress for.
The variable text shows the message that called
automation.
The variable restype shows the type of resource that
automation has been set OFF for.
System action: The current automation continues.
The variable job_name shows the name of the job.
Operator response: None.
System action: None.
System programmer response: None.
Operator response: None.
Classes: 40, 43, 44.
System programmer response: None.
Classes: 40, 43, 44.
AOF586A
time : TIME OUT OCCURRED : MVS D
C,B FAILED - AUTOMATION
RECOVERY ATTEMPT TERMINATED
Explanation: A console buffer shortage recovery
attempt has timed out. The recovery attempt is
terminated.
The variable time shows the time when this message
was generated.
62
System Automation for z/OS Messages and Codes:
AOF587I • AOF592E
System action: None.
If action is 'EXCEEDED' processing continues.
Operator response: Notify your system programmer.
Operator response: None.
System programmer response: Determine why the
MVS D C,B system command is not responding.
Should the console be overloaded with excessive
messages, issue the MVS K command to resolve
console buffer shortages. Refer to MVS/ESA System
Commands for further details.
System programmer response: Determine why the
frequent error threshold for this resource was exceeded.
Classes: 40 43 51.
AOF589I
Classes: 40, 43, 44, 46.
AOF587I
time : RECOVERY FOR restype resname
CONTINUING - CRITICAL
THRESHOLD action
Explanation: Recovery for a resource is in progress
and the critical error threshold for the resource has
been exceeded. The commands specified to be issued
when this happens have been issued.
The variable time shows the time this message was
generated.
The variable restype shows the type of the resource
that recovery is in progress for.
The variable resname shows the name of the
resource that recovery is in progress for.
The variable action is either 'COMMANDS ISSUED'
or 'EXCEEDED'
System action: If action is 'COMMANDS ISSUED' then
automation issues the commands specified in the
automation control file for critical threshold. If action is
'EXCEEDED' processing continues.
Operator response: None.
System programmer response: Determine why the
critical threshold has been reached for this resource.
Classes: 40 41 44 50.
AOF588I
time : RECOVERY FOR restype resname
CONTINUING - FREQUENT
THRESHOLD action
Explanation: Recovery is in progress for a resource
and the frequent error threshold has been exceeded.
The commands specified to be issued when this
happens have been issued.
The variable time shows the time this message was
generated.
The variable restype shows the type of the resource
that recovery is in progress for.
The variable resname shows the name of the
resource that recovery is in progress for.
time : RECOVERY FOR restype resname
CONTINUING - INFREQUENT
THRESHOLD action
Explanation: Recovery is in progress for a resource
and the infrequent error threshold for the resource has
been exceeded. The commands specified to be issued
when this happens have been issued.
The variable time shows the time this message was
generated.
The variable restype shows the type of the resource
that recovery is in progress for.
The variable resname shows the name of the
resource that recovery is in progress for.
The variable action is either 'COMMANDS ISSUED'
or 'EXCEEDED'
System action: If action is 'COMMANDS ISSUED' then
automation issues the commands specified in the
automation control file for the infrequent error
threshold. If action is 'EXCEEDED' processing
continues.
Operator response: None.
System programmer response: Determine from the
netlog why the errors are occurring.
Classes: 40 43 52.
AOF592E
SHUTDOWN REJECTED - autotype
FLAG FOR subsystem IS OFF
Explanation: Shutdown processing is rejected for a
resource that automation is set to OFF for.
The variable autotype shows the type of automation
(AUTOMATION or TERMINATION).
The variable subsystem indicates the resource in
question.
System action: None.
Operator response: Shut down the resource manually
or change the automation flag to ON, and re-invoke the
INGREQ=STOP command.
System programmer response: None.
Classes: None.
The variable action is either 'COMMANDS ISSUED'
or 'EXCEEDED'.
System action: If action is 'COMMANDS ISSUED' then
automation issues the commands specified in the
automation control file for the frequent error threshold.
Chapter 2. Messages AOF000I to AOF969I
63
AOF593A • AOF599A
AOF593A
time : ALL SHUTDOWN
COMMANDS/REPLIES FOR restype
resname (JOB job_name) HAVE BEEN
ISSUED - OPERATOR INTERVENTION
REQUIRED
Explanation: All shutdown commands in the
automation control file have been issued and a resource
still has not shut down. Operator intervention is
required to shut down the resource.
The variable time shows the time this message was
generated.
The variable restype shows the type of resource that
has not shut down.
The variable resname shows the name of the
resource that has not shut down.
The variable job_name shows the name of the job.
System action: Automation waits for the resource to
be shut down manually.
Operator response: Shut down the resource manually
and notify your system programmer.
System programmer response: Determine from the
netlog why the resource did not shut down.
AOF597A
Explanation: Commands have been exhausted for a
console.
The variable time shows the time this message was
generated.
The variable percent shows the percentage of WTO
buffer shortage.
The variable console_ID identifies the console that
reached the buffer storage percentage.
The variable suggestion shows a recommended
action for resolving the condition reported by the
message.
System action: Recovery ends.
Operator response: Check for any outstanding REPLY,
MOUNT, or multiline messages that are being held.
These messages use the WTO buffer storage.
System programmer response: None.
Classes: 40 43 52.
AOF598A
Classes: 40, 43, 44, 46.
AOF595E
time : restype resname (JOB job_name)
STATUS NOT AUTODOWN - STATUS
IS status - RESTART NOT ATTEMPTED
Explanation: A resource has been shut down but its
status is not AUTODOWN. No restart will be
attempted.
The variable time shows the time this message was
generated.
The variable restype shows the type of the resource
that was shut down.
The variable resname shows the name of the
resource that was shut down.
The variable job_name shows the name of the job.
The variable status shows the status of the resource.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Determine why the
status of the resource is not AUTODOWN after
shutdown. Either you must restart the resource
manually or you must change the status to DOWN
using the SETSTATE command and allow automation
to start the resource.
Classes: 40, 43.
time : percent% MAX PASSES REACHED
FOR console_ID - suggestion
time : percent% MAX PASSES REACHED
FOR ALL CONSOLES USING > count
BUFFERS - autotype ATTEMPT ENDED suggestion
Explanation: Commands have been exhausted for all
consoles.
The variable time shows the time this message was
generated.
The variable percent shows the percentage of WTO
buffer shortage.
The variable count shows the number of buffers
used.
The variable autotype shows the type of automation.
The variable suggestion shows a recommended
action for resolving the condition reported by the
message.
System action: Recovery ends.
Operator response: Check for any outstanding REPLY,
MOUNT, or multiline messages that are being held.
These messages use WTO buffer storage.
System programmer response: None.
Classes: 40 43 52.
AOF599A
time : percent% NO CONSOLES FOUND
USING MORE THAN count BUFFERS autotype ATTEMPT ENDED
Explanation: No console has reached the threshold set
for number of buffers. No recovery is attempted.
The variable time shows the time this message was
generated.
64
System Automation for z/OS Messages and Codes:
AOF601E • AOF606D
The variable percent shows the percentage of WTO
buffer shortage.
The variable count shows the number of buffers
used.
The variable autotype shows the type of automation.
System action: None.
Operator response: If you suspect a problem with
WTO buffers, additional checking is required to correct
the problem. Contact your system programmer.
System programmer response: Either verify that the
“number of buffers” threshold is set to a value that will
accommodate demands, or allow recovery to detect
that the threshold has been exceeded.
Classes: 40 43 52.
for this message if there is no response from the
operator.
The variable domid shows the NetView target
domain ID.
System action: The system waits two minutes for a
reply. If there is no reply after two minutes, automation
continues.
Operator response: No reply is necessary if you want
automation to continue with the default actions.
Pressing Enter with no input causes automation to
continue immediately using the default actions. Other
options that may be specified are documented in the
preceding multiline message, AOF767I. See AOF767I
help for details or reply 'R' to redisplay message
AOF767I.
System programmer response: None.
AOF601E
product_name IS DOWNLEVEL PREREQ FOR SA z/OS IS NOT
FULFILLED
Explanation: The prerequisites for SA z/OS are not
fulfilled. SA z/OS cannot be started.
The variable product_name indicates the product in
question
System action: Processing terminates.
Operator response: None.
System programmer response: Install the required
prerequisites.
Classes: None.
AOF604I
AUTOMATION PAUSED BY
OPERATOR REQUEST
Explanation: Automation has been paused due to an
operator request.
System action: Automation is paused.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
Classes: None.
AOF605I
AOF602D
ENTER 'RETRY' OR 'CANCEL' –
DOMAIN domid
Explanation: A severe error, indicated by other
messages, occurred during base initialization.
The variable domid shows the NetView domain ID.
AUTOMATION DISABLED BY
OPERATOR REQUEST
Explanation: Automation has been disabled as a result
of the operator replying STOP to message AOF603D or
message AOF606D.
System action: Automation is disabled.
System action: The system waits for an operator
response.
Operator response: None.
Operator response: An associated message will
provide more details about the problem. If necessary,
contact your system programmer.
Classes: 40, 43.
System programmer response: Find and fix the
problem with your customization of system
automation. If you cannot determine the cause of the
problem, contact your IBM Support Center.
Classes: None.
AOF603D
ENTER AUTOMATION OPTIONS OR
'R' (RE-DISPLAY) - DOMAIN domid
Explanation: This message is issued at the beginning
of system automation initialization. Its purpose is to
give the operator the opportunity to stop, pause, or
override automation. A reply is generated automatically
System programmer response: None.
AOF606D
AUTOMATION PAUSED, ENTER
OPTIONS OR 'R' (RE-DISPLAY) –
DOMAIN domid
Explanation: Automation has been paused as a result
of the operator replying PAUSE to message AOF603D.
The variable domid shows the NetView target
domain ID.
System action: Automation pauses and waits for a
reply to this message.
Operator response: Pressing Enter with no input
causes automation to continue immediately using
default values. Other options that may be specified are
documented in the preceding multiline message,
Chapter 2. Messages AOF000I to AOF969I
65
AOF607I • AOF613D
AOF767I. See AOF767I help for details or reply 'R' to
redisplay message AOF767I.
v The command re-issues the WTOR asking the
operator for the correct answer.
System programmer response: None.
v Automation is paused (if it was not already paused),
the AOF767I message is reissued, and an AOF606D
WTOR is issued so you can enter a correct response.
Classes: 40, 43.
AOF607I
AN action OF THE AUTOMATION
ENVIRONMENT IS IN PROGRESS
Explanation: The automation is either initializing or
reloading its automation environment.
v The variable action shows which action is being
performed in the automation environment. It can be
one of the following:
BUILD The automation is either initializing,
reloading, or restoring its automation
environment
REFRESH
The automation is refreshing its automation
environment
System action: If the action is BUILD, the automation
is unavailable until the environment is established.
If the action is REFRESH, processing continues.
Operator response: None.
System programmer response: None.
Classes: 40.
Operator response: Reply to the new WTOR.
Classes: 40 44 46.
AOF610I
SHUTDOWN REJECTED subsystem_name HAS NO SHUT shut_type
DEFINED
Explanation: The shutdown type specified for this
shutdown request has not been defined in the
automation control file for the indicated subsystem.
The variable subsystem_name indicates the subsystem
in question.
The variable shut_type shows the type of shutdown,
NORM, IMMED, or FORCE.
System action: None.
Operator response: Either shut down the subsystem
manually, or reissue the shutdown request with a
higher priority shutdown type.
System programmer response: Include the shutdown
type specification in the automation control file
definition.
Classes: None.
AOF608E
REXX Function Package INGRXFPG not
installed
Explanation: The SA z/OS required REXX function
INGRXFPG is not installed. However, the function
package is mandatory for running SA z/OS.
System action: Processing terminates.
Operator response: None.
System programmer response: Install the required
REXX function package. See IBM Tivoli System
Automation for z/OS Planning and Installation for further
guidance.
Classes: None.
AOF609I
INVALID REPLY: reason
Explanation: May be one of the following:
v An operator command such as INGREQ or
INGMOVE has issued a WTOR but the response to
the WTOR is wrong
v The reply you gave in response to AOF603D or
AOF606D WTOR is incorrect
The variable reason gives a brief explanation of what
went wrong.
System action: Depending on the explanation, may be
one of the following:
66
System Automation for z/OS Messages and Codes:
AOF611I
SHUTDOWN REJECTED subsystem_name SHUT shut_type HAS NO
COMMAND/REPLY
Explanation: The shutdown type specified for this
shutdown request has no command or reply defined in
the automation control file for the indicated subsystem.
The variable subsystem_name indicates the subsystem
in question.
The variable shut_type shows the type of shutdown,
NORM, IMMED, or FORCE.
System action: None.
Operator response: Either shut down the subsystem
manually, or reissue the shutdown request with a
higher priority shutdown type.
System programmer response: Include the shutdown
type specification in the automation control file
definition.
Classes: None.
AOF613D
SPECIFY NEW RUNMODE.
RUNMODE runmode NO LONGER
EXISTS - DOMAIN domid
Explanation: The message is issued at the beginning
of system automation initialization. A runmode is
AOF614I • AOF618I
currently set which does not exist in the policy.
The variable runmode shows the name of the current
runmode.
The variable domid shows the NetView target
domain id.
AOF618I
|
|
v The variable reason shows the reason for the failure.
Possible reasons are:
Operator response: Specify a valid runmode or *ALL
for RUNMODE=keyword. RUNMODE=? lists all
possible runmodes. Although it is not recommended,
you can keep the current runmode followed by an
exclamation mark(!).
NO DEFAULT ACF FOUND IN AOFACFMP
The ACF mapping member does not contain
a configuration for this system.
System programmer response: None.
ACF MEMBER NOT AVAILABLE
The ACF member could not be accessed.
Classes: None.
ACF TOKEN MISMATCH
The ACF does not have the same token as
the automation manager configuration file.
TIMER timerid IS DEFINED BUT IS
MORE THAN 2 YEARS FROM NOW
ACF CONTENT NOT VALID
The ACF was not built using the correct
version of the customization dialogs or was
corrupted.
Explanation: The requested timer is defined
successfully but the YY portion of the requested date is
more than 2 years past the current year.
The variable timerid shows the ID of the timer being
defined.
ALLOCATION OF dataset FAILED
System automation was not able to
dynamically allocate the ACF data set.
System action: The requested timer is defined.
Operator response: Check that you have specified the
year that you intended. If necessary, update the timer
definition using the SETTIMER command.
System programmer response: None.
Classes: None.
AOF615I
|
|
|
|
|
Explanation: The task could not be started.
System action: Automation is paused. The message is
followed by AOF604I and AOF767I.
ACF CHECK FAILED WITH RC=rc
An error occurred while checking the ACF.
Contact your IBM Support Center.
Operator response: Reply to AOF767I. If the problem
persists, contact your system programmer.
CURRENT RUNMODE runmode NO LONGER
EXISTS
The ACF does not contain the runmode
which is currently set.
System programmer response: Check your DSIDMN
file, or NetView style sheet DSIPARM member for the
task in question.
Classes: 40, 43.
AOF617I
SA Z/OS INITIALIZATION STARTED
Explanation: Initialization of SA z/OS has started.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: None.
AUTOMATION TABLE member IN ERROR
The test of a NetView automation table
failed. Browse the netlog for further details
and see the INGERRLS listing in the
DSILIST data set.
MESSAGE REVISION TABLE IN ERROR
The test of a NetView message revision
table failed. Browse the netlog for further
details and see the INGERRLS listing in the
DSILIST data set.
UNABLE TO START TASK task
Also study the SYSLOG for associated IEC* messages
to indicate an associated dataset issue.
Explanation: The automation configuration file found
could not be loaded by the product.
v The variable sysname shows the system name that an
automation control file could not be found for.
System action: The system waits for a reply.
AOF614I
NO VALID ACF FOUND FOR sysname reason
|
|
|
ACF IS NOT VALID FOR THIS PRODUCT
The ACF contains more systems than can be
supported by this product.
|
|
|
|
|
AUTOMATION TABLE member NOT VALID FOR
THIS PRODUCT
The NetView automation table contains user
specific changes which cannot be supported
by this product.
|
|
|
|
|
MESSAGE REVISION TABLE NOT VALID FOR
THIS PRODUCT
The NetView message revision table
contains user specific changes which cannot
be supported by this product.
Chapter 2. Messages AOF000I to AOF969I
67
AOF620I • AOF625I
|
|
|
AUTOMATION TABLE member NOT FOUND
The NetView automation table could not be
found in DSIPARM.
Classes: None.
AOF622A
System action: ACF load/refresh processing
terminates.
Operator response: Contact your system programmer.
System programmer response: Fix the problem by
providing a valid configuration for the automation
agent:
1. Copy the configuration that the automation
manager was loaded from back into your
configuration data set and instruct the automation
agent to Retry its cold start. This is only possible if
you still have a copy of that data.
2. Instruct the automation manager to load the
configuration currently on disk with F
AM,REFRESH,*.
3. Instruct the automation manager and the
automation agent to load their configuration from a
different configuration file with F
AM,REFRESH,file_name. Like option 1, this only
works if you have an alternative file available.
Classes: 40, 43.
NEW STATUS OF auto_status NOT
VALID WHEN THE type STATUS IS
other_status
Explanation: The automation status specified in the
SETSTATE command is not valid for the current
application monitor routine status or ARM status of the
resource.
The variable auto_status shows the automation
status specified in the SETSTATE command.
The variable type shows the type of resource status
that is being compared with the automation status.
The type value can be either MONITOR or ARM.
The variable other_status shows the application
monitor or ARM status that the automation status is
not valid for.
System action: None.
Operator response: Correct the automation status and
reissue the SETSTATE command, or investigate the
status of the resource.
System programmer response: None.
Classes: None.
AOF620I
clist time LENGTH ERROR, FORMAT
SHOULD BE HH.MM, H.MM, MM, M,
HH.M, HH., H., H.M or HH.MM.SS
Explanation: A timer value specified is not valid.
The variable clist shows which CLIST issues this
message.
The variable time shows the timer interval entered.
System action: None.
Operator response: Enter the command again,
specifying a valid value.
System programmer response: None.
Classes: None.
AOF621I
clist INVALID TIME SPECIFIED
time_value/maximum_value
Explanation: A timer value specified is not valid.
NEW STATUS of auto_status NOT
VALID FOR SUBSYSTEM OF TYPE type
Explanation: The automation status specified in the
SETSTATE command is not valid for this type of
subsystem.
The variable auto_status shows the automation
status specified in the SETSTATE command.
The variable type shows the type of the subsystem,
for example, MVS.
System action: None.
Operator response: Correct the automation status and
reissue the SETSTATE command.
AOF625I
CONFIGURATION REFRESH STAGED
FOR THE FOLLOWING REASON(S):
The variable clist shows which CLIST issues this
message.
Explanation: This message is the header line of a
multiline message. A configuration refresh was delayed
for the reasons listed with messages AOF626I.
The variable time_value shows the timer interval
value.
System action: The configuration refresh is retried
after 5 minutes.
The variable maximum_value shows the maximum
value for either hours (24), minutes (59) or seconds
(59).
Operator response: None.
System action: None.
Operator response: Enter the command again,
specifying a valid value.
System programmer response: None.
68
AOF624I
System Automation for z/OS Messages and Codes:
Classes: None.
AOF626I • AOF644E
AOF626I
restype resname IS IN action
Explanation: This message is part of a multiline
message. It provides information about the reasons for
a configuration refresh staging.
The variable restype is the resource type (that is,
SUBSYSTEM).
The variable resname is the resource name.
The variable action is the action that is currently
performed for the resource.
System action: The configuration refresh is delayed
for this resource.
Operator response: None.
Classes: None.
AOF632I
REFRESHING OF SDF PANELS WILL
NOT OCCUR
Explanation: This message indicates that the
SDFQNM command was not executed successfully
during a reload or recycle, due to mismatching
sysnames.
System action: Processing continues.
Operator response: Notify your system programmer.
System programmer response: Ensure the sysname
matches the root system name defined in AOFTREE.
AOF641E
time : CLIST name FAILED. PPI
RECEIVER ID id DOES NOT EXIST.
MESSAGES WILL NOT BE
FORWARDED TO TEC
Explanation: During the initialization of the TEC
Notification service, it was detected that the PPI
receiver ID of the GEM Event Adapter is not available.
The variable time shows the time when this message
was generated.
The variable name shows the CLIST that issued this
message.
The variable id shows the ID of the PPI receiver of
the GEM Event Adapter.
System action: Events will not be forwarded to TEC.
Operator response: Notify your system programmer.
System programmer response: Check whether the
GEM Event Adapter is up and running. If this is the
case, check whether the PPI receiver ID used by the
GEM Event Adapter is the same as the one that is
expected by the TEC Notification service.
Classes: 0, 40, 44.
AOF642I
time : TIVOLI ENTERPRISE CONSOLE
NOTIFICATION SERVICE IS
ENABLED
Explanation: The T/EC Notification service is fully
initialized and the E/AS Message Adapter that the TEC
Notification sends messages to for conversion to TEC
Events is up and running.
The variable time shows the time when this message
was generated.
System action: From now on system automation
messages are forwarded to TEC via the E/AS Message
Adapter.
Operator response: None.
System programmer response: None.
Classes: 40.
AOF643I
time : TIVOLI ENTERPRISE CONSOLE
NOTIFICATION SERVICE IS
DISABLED
Explanation: The TEC Notification service has stopped
forwarding messages to the E/AS Message Adapter.
The variable time shows the time when this message
was generated.
System action: Messages are no longer forwarded to
TEC.
Operator response: Notify your system programmer.
System programmer response: The PPI receiver ID of
the E/AS Message Adapter was no longer available to
the TEC Notification Service. Ensure that the E/AS
Message Adapter is up and running.
Classes: 40.
AOF644E
time : CLIST name FAILED. FOCAL
POINT VARIABLE varname NOT SET.
EVENTS WILL NOT BE FORWARDED
TO TEC
Explanation: The system tried to retrieve the system
automation primary focal-point name from the
NetView global variable varname. If the name cannot be
retrieved, message AOF644E is issued. The E/AS
Message Adapter is expected to run on the system
automation primary focal-point system.
The variable time shows the time when this message
was generated.
The variable name shows the name of the CLIST
that issued the message.
The variable varname shows the name of the focal
point system.
System action: Events will not be forwarded to TEC.
Operator response: Notify your system programmer.
System programmer response: Make sure that you
Chapter 2. Messages AOF000I to AOF969I
69
AOF646I • AOF663I
have customized the focal point forwarding path
correctly.
Classes: 0 40 44.
AOF646I
time : TIVOLI ENTERPRISE CONSOLE
NOTIFICATION SERVICE IS
INITIALIZED
Explanation: The Tivoli Enterprise Console
Notification service is initialized successfully. The TEC
Notification service is ready to forward messages to the
E/AS Message Adapter. As soon as the E/AS Message
Adapter is up and running, the AOF642I message is
issued indicating that from now on messages will be
forwarded to the E/AS Message Adapter.
The variable domain_ID_3 shows the domain ID that
is first in the communication path to domain_ID_2.
This is equal to domain_ID_2 if the communication
is direct.
The variable system_info shows the sysplex name,
the system name, and the sdfroot of domain_ID_2 in
the format sysplex.system(sdfroot). The sysplex
(including the dot) is only shown if SA z/OS on
domain_ID_2 runs in a parallel sysplex.
The variable product shows the automation product
running in domain_ID_2.
The variable version shows the version of that
product in the format VnRnMn.
Operator response: None.
System action: Any other domains that were waiting
on the activation of this domain are notified. If this
domain is defined as a focal point, focal point
reassignment is considered. If domain_ID_1 has domains
that have not yet established communication, and if
this domain has been defined as a path to it, the other
domain is queried in domain_ID_2 for its status.
System programmer response: None.
Operator response: None.
Classes: 40.
System programmer response: None.
The variable time shows the time when this message
was generated.
System action: Processing continues.
AOF660I
CURRENT FOCAL POINT IS
domain_ID_1 , WAS domain_ID_2, FOR
domain_ID_3 SYSTEM system_name
Classes: 40.
AOF662I
Explanation: The focal point has been established or
changed.
DOMAIN domain_ID_1 HAS STOPPED
COMMUNICATING WITH domain_ID_2
system_name
The variable domain_ID_1 shows the domain ID of
the current focal point.
Explanation: Communication has been interrupted for
the specified domain.
The variable domain_ID_2 shows the domain ID of
the prior focal point.
The variable domain_ID_1 shows the domain ID that
stopped communicating.
The variable domain_ID_3 shows the domain ID that
is using domain_ID_1 as its focal point.
The variable domain_ID_2 shows the domain ID that
cannot be reached.
The variable system_name shows the name of this
domain.
The variable system_name shows the name of
domain_ID_2.
System action: Communications to the focal point
from domain_ID_3 will now use domain_ID_1.
System action: None.
Operator response: None.
System programmer response: None.
System programmer response: None.
Classes: 40.
Operator response: None.
Classes: 40.
AOF663I
AOF661I
DOMAIN domain_ID_1 IS
COMMUNICATING WITH
domain_ID_2, VIA domain_ID_3 ,
system_info, product version
Explanation: Communication is established to
domain_ID_2 from domain_ID_1 via domain_ID_3.
The variable domain_ID_1 shows the domain ID that
established communications.
The variable domain_ID_2 shows the domain ID that
is now ready for communications.
70
System Automation for z/OS Messages and Codes:
DOMAIN domain_ID STATUS IS status,
REPORTED BY reporting_domain
Explanation: The reporting domain has reported the
status of domain ID and the status was not a known
status. Known statuses are ACTIVE, INACTIVE, and
INVALID.
The variable domain_ID shows the domain ID whose
status is being reported.
The variable status shows the status value of the
domain ID.
The variable reporting_domain shows the domain ID
of the domain reporting.
AOF664I • AOF671I
System action: None.
AOF669I
Operator response: Notify your system programmer.
System programmer response: The status is not a
known status; further action is not possible. The origin
of this status is reporting domain; it is either in error or
it supports domain statuses that this product does not.
Classes: 1 40.
AOF664I
Explanation: A request that originated in this domain
looped back to this domain. The loop is stopped here
and logged through this message.
The variable domain_ID_1 shows the domain ID that
received its own request back.
NO FOCAL POINT AVAILABLE
Explanation: There is no focal point system available
at this time.
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40.
AOF667I
REQUEST TO DOMAIN domain_ID_1
WAS REJECTED AT domain_ID_2, NO
ROUTE DEFINED
Explanation: A request issued for domain_ID_1 was
rejected by domain_ID_2 because no route to
domain_ID_1 is defined.
The variable domain_ID_1 shows the domain ID that
the request was issued to.
The variable domain_ID_2 shows the domain ID that
rejected the request.
System action: None.
Operator response: None.
The variable domain_ID_2 shows the domain ID that
the request was probably sent out on. This domain
is the domain that is currently being used to
communicate to the target domain; this may have
changed since this request was sent.
The variable domain_ID_3 shows the domain ID that
the request was received from. That domain should
have been the next domain en route to the target
domain.
The variable request shows the looping request. The
target domain is contained in this request.
System action: None.
Operator response: None.
System programmer response: Scrutinize the gateway
definitions in the path towards the target domain,
including the alternate routing definitions. Expect to
find a path that leads back to this domain that would
result in an endless loop that never reaches the target
domain.
Classes: 1.
AOF670I
System programmer response: The message can be
used to analyze gateway activity.
COMMAND (command_text) WAS
EXECUTED IN DOMAIN domain_ID BY
OPERATOR operator_ID
Explanation: A command was issued by this operator
in this domain.
Classes: 1.
AOF668I
REQUEST LOOPED BACK TO
domain_ID_1, SENT ON domain_ID_2,
RECEIVED FROM domain_ID_3,
REQUEST: request
DOMAIN domain_ID REJECTED
REQUEST: request
Explanation: The identified domain rejected the
request shown.
The variable domain_ID shows the domain ID that
rejected the request shown.
The variable request shows the request that was
rejected.
The variable command_text shows the text of the
command executed.
The variable domain_ID shows the domain that the
command was executed in.
The variable operator_ID shows the ID of the
operator issuing the command.
System action: None.
Operator response: None.
System action: None.
System programmer response: None.
Operator response: None.
Classes: None.
System programmer response: Either the domain ID
does not support the request or the request is not valid.
AOF671I
Classes: 1.
COMMAND (command_text) FAILED
EXECUTION IN DOMAIN domain_ID,
RC=return_code
Explanation: An INGSEND with RESP=ACK was
issued by an operator from this domain. This message
is an acknowledgment that the command executed on
Chapter 2. Messages AOF000I to AOF969I
71
AOF672I • AOF705I
the target domain, but failed.
System action: None.
The variable command_text shows the text of the
command attempted.
Operator response: None.
System programmer response: None.
The variable domain_ID shows the domain that the
command was attempted in.
Classes: None.
The variable return_code shows the value returned
for the failing command.
AOF701A
System action: None.
Operator response: The return code is specific to the
command. Preserve the information for follow up
action.
System programmer response: Check the command
return codes for a match to determine the cause of
failure and possible resolution.
|
|
|
|
|
Explanation: Loading of the message automation table
failed. Errors were detected while attempting to load
table. Preceding messages describe the errors.
|
System action: None.
Classes: None.
AOF672I
COMMAND (command_text) WAS
EXECUTED IN DOMAIN domain_ID BY
A crm COMMAND FROM OPERATOR
operator_ID
Explanation: An INGSEND with RESP=ACK was
issued by an operator from this domain. This message
is an acknowledgment that the command executed
successfully on the target domain.
The variable command_text shows the text of the
command executed.
The variable domain_ID shows the target domain
that the command was executed in. If the command
routing mechanism used was RMTCMD, the
domain may be qualified by a network ID, or "*"
indicating that the default network ID was used to
route the command.
The variable crm shows the command routing
mechanism used. Possible values are ROUTE or
RMTCMD.
The variable operator_ID shows the ID of the
operator who issued the INGSEND command.
MESSAGE TABLE table WAS NOT
LOADED - DETECTED ERRORS
The variable table shows the name of the message
automation table.
Operator response: Contact your system programmer.
|
|
|
|
System programmer response: Follow the response
instructions given in the description of the preceding
messages. Correct the errors and reload the failing table
via AUTOTBL or ACF ATLOAD command.
Classes: 40 44 46.
AOF702I
CLIST name COMPLETED ON task
WITH RETURN CODE rc
Explanation: When debugging is active, this message
is written to the netlog each time a command list has
finished.
The variable name is the name of the clist.
The variable task is the name of the task that the
clist ran on.
The variable rc is the return code given by the clist.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF700I
CLIST name EXECUTING ON task
WITH PARMS > parmstr
Explanation: When debugging is active, this message
is written to the netlog each time a command list is
processed.
user ISSUED COMMAND command
WITH parameters
Explanation: The specified user issued the command
with the specified parameters. The message is only
issued if command logging is enabled.
The variable user is the NetView user ID.
The variable command is the command that was
issued.
The variable parameters lists the various parameters
for the command (either specified or defaulted).
The variable name is the name of the clist.
System action: None.
The variable task is the name of the task that the
clist ran on.
Operator response: None.
The variable parmstr shows the parameters
processed.
72
AOF705I
System Automation for z/OS Messages and Codes:
System programmer response: None.
Classes: None.
AOF708I • AOF717I
AOF708I
THE LINE NUMBER ENTERED IS
INVALID
Explanation: When attempting to change the number
of the line that is displayed, an invalid line number
was entered.
System action: None.
Operator response: Enter a valid line number.
System programmer response: None.
Classes: None.
AOF712I
INVALID CHARACTER character IN
field_type field
Explanation: A data field of an automation control file
contains an incorrect character.
The variable character shows the incorrect character.
The variable field_type shows the type of the field
that contains the incorrect character. The field type
can be either ENTRY or TYPE.
The variable field shows the field that contains the
incorrect character.
System action: None.
AOF709I
THE COMMAND ENTERED IS
INVALID
Explanation: The command that was specified is not
valid.
Operator response: Specify valid entry/type fields
with correct characters. Refer to IBM Tivoli System
Automation for z/OS Defining Automation Policy for
information about the correct syntax.
System action: None.
System programmer response: None.
Operator response: Type a valid command.
Classes: None.
System programmer response: None.
Classes: None.
AOF710A
request INPUT AND THEN PRESS
ENTER
Explanation: Input displayed on an operator dialog
needs updating or validating before a command can be
issued.
The variable request specifies the action required.
System action: None.
Operator response: Perform the requested action.
System programmer response: None.
Classes: None.
AOF711I
AUTOMATION OFF FOR subsys , value
EFFECTIVE WHEN AUTOMATE SET
ON
Explanation: Automation has been set to OFF for a
resource. When automation is reset to ON, the
requested update to the flag will become enabled.
The variable subsys shows the name of the resource.
The variable value shows the flag that is to be
updated and the value the flag is to be updated to.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF713A
CALL TO macro FAILED, RC rc
Explanation: A system automation program detected
an unacceptable return code from a macro that it called.
The meaning of the return code depends on the macro
that issued it. Common examples are: DSICDS,28 :
attempt to set a REXX variable failed as not called from
REXX DSIDKS(FIND),4 : member not found or empty.
The variable macro shows the name of the macro
that returned the error.
The variable rc shows the return code.
System action: The routine that called the macro
continues processing if possible. If the routine cannot
continue it will terminate with a non-zero return code.
Other messages may be issued indicating that a
problem occurred.
Operator response: Take appropriate corrective action.
The action needed will depend upon the problem that
caused the failure. For example the routine should be
run from REXX if necessary. For empty or missing
members either correct the member name or create the
necessary member.
System programmer response: If the fixes under
operator responses do not work make a note of the
issuing routine, the macro and the return code and
contact your IBM service representative for assistance.
Classes: None.
AOF717I
SPECIFIED MEMBER NAME IS TOO
LONG
Explanation: A string passed to a routine as the name
of a member is more than 8 characters long.
System action: The routine terminates with a non-zero
return code.
Chapter 2. Messages AOF000I to AOF969I
73
AOF718A • AOF722E
Operator response: If issuing the command directly,
reissue it with the correct member name. If the
command is issued from a CLIST refer the problem to
your system programmer.
System programmer response: If the command is
issued from a CLIST, fix the CLIST.
Classes: None.
AOF718A
SYS-OPS UNABLE TO CONTINUE OPERATOR ASSISTANCE ESSENTIAL
Explanation: The system automation program has
encountered a problem that it is unable to bypass. Such
problems are generally related to corrupt message
tables or automation control files that are missing
essential information.
System action: System automation stops working.
Some message automation may occur if there was an
active NetView automation table when the problem
was found.
Operator response: An associated message will give
more details of the problem. If necessary, contact your
system programmer.
System programmer response: Find and fix the
problem with your customization of system
automation. If you cannot identify the cause of the
problem, contact your IBM Support Center.
Classes: 40, 46.
AOF719I
clist : type COMMAND command FAILED
- reason
Explanation: A CLIST issued a command and did not
get the expected result.
The variable clist shows the name of the CLIST that
issued the command.
AOF720E
NO VALID DATA FOUND IN
AUTOMATION CONTROL FILE
Explanation: The automation control file is empty or
all data was invalid.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Correct the automation
control file. Refer to IBM Tivoli System Automation for
z/OS Defining Automation Policy for information on the
syntax.
Classes: None.
AOF721I
EASY MESSAGE MANAGEMENT
DISABLED BY AOFSMARTMAT
SETTING
Explanation: Easy Message Management is not active.
The NetView automation table built by the
customization dialogs will not be used.
System action: Processing continues with the AT from
DSIPARM.
Operator response: None.
System programmer response: To enable Easy
Message Management set the AAO AOFSMARTMAT to
2 using the NetView stylesheet.
Classes: 40 43.
AOF722E
MEMBER member NOT FOUND IN
dataset - USING DEFAULT defmem
FROM ddname
Explanation: Easy Message Management is enabled,
but the NetView automation table built by the
customization dialogs could not be found.
The variable type shows the type of command that
was issued, for example MVS, or JES.
The variable member is the name of the missing AT
fragment.
The variable command shows the command that
failed.
The variable dataset is the name of the configuration
data set.
The variable reason gives a description of problem
encountered.
The variable defmem is the name of the default AT
fragment.
System action: CLIST processing usually stops.
Operator response: Notify your system programmer.
System programmer response: If the reason is
timeout, change the timeout values in the automation
control file. Fix any customization errors. If the problem
persists, contact your IBM Support Center.
Classes: 40 46.
The variable ddname is the name of the DD
statement within the NetView startproc that is used
to search for defmem.
System action: The default AT delivered by SA z/OS
is used.
Operator response: Notify your system programmer.
System programmer response: Determine why the
dynamically built AT fragment is not available.
Classes: 40 46.
74
System Automation for z/OS Messages and Codes:
AOF723I • AOF729I
AOF723I
MEMBER member FROM dataset
LOADED INTO STORAGE AS
AUTOMATION TABLE FRAGMENT
defmem
Explanation: Easy Message Management is enabled
and the NetView automation table built by the
customization dialogs replaces the default AT fragment
delivered with SA z/OS.
The variable member is the name of the missing AT
fragment.
The variable dataset is the name of the configuration
data set.
The variable defmem is the name of the default AT
fragment.
System action: Processing continues with the replaced
AT fragment.
AOF727I
Explanation: A request has been made to enable the
exits for a resource automation flag. Because no exits
have been coded in the automation control file for this
resource flag, the flag has been set to ON.
The variable request shows the resource name and
automation flag.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF728I
Operator response: None.
System programmer response: None.
Classes: 40 43.
AOF724I
MEMBER member FROM dataset
LOADED INTO STORAGE AS
MESSAGE REVISION TABLE defmem
Explanation: Easy Message Management is enabled
and the NetView message revision table (MRT) built by
the customization dialogs is activated, replacing any
previously active MRT.
The variable member is the name of the missing
MRT fragment.
The variable dataset is the name of the configuration
data set.
The variable defmem is the name of the activated
MRT.
System action: Processing continues with the replaced
MRT.
Operator response: None.
System programmer response: None.
Classes: 40 43.
AOF726I
FUNCTION SUCCESSFULLY
COMPLETED - WARNINGS WRITTEN
TO NETWORK LOG
Explanation: The function requested has been
successfully executed. During execution warning
messages have been written to the network log.
System action: None.
Operator response: Refer to the netlog for further
information.
System programmer response: None.
Classes: None.
request EXITS CANNOT BE ENABLED,
EXITS DO NOT EXIST - FLAG SET TO
ON
subsystem type RECOVERY
COMMANDS EXHAUSTED, BACK TO
PASS 1
Explanation: While attempting to recover a spool or
buffer shortage system automation ran out of defined
recovery commands before recovery was complete.
System automation will re-execute the recovery
command sequence starting from the first pass.
This situation may occur if the earlier recovery
commands have disposed of excessive spool or buffer
but more has accumulated while the earlier passes were
running.
The variable subsystem shows the subsystem name.
The variable type shows the type of shortage
problem being recovered. Possible values are
SHORT and FULL.
The variable resource shows the resource having a
shortage problem.
System action: The shortage recovery continues.
Operator response: You need to have a look at your
spool or buffer usage. System automation may need
some assistance to keep it in control. Look for tasks
generating spool or consuming buffer that the recovery
commands do not affect.
System programmer response: Review your recovery
commands. You may wish to make them more
aggressive or to add some more of them.
Classes: 40 45.
AOF729I
subsystem SPOOL type RECOVERY
SUSPENDED ON PASS pass : reason
Explanation: While attempting to recover a spool
shortage system automation found a reason why it
could not continue with spool recovery. The most likely
reason is that the Recover automation flag is or has
been turned off. While the flag remains off spool usage
will be monitored, but no recovery commands will be
issued. If the flag is reset, the recovery commands will
Chapter 2. Messages AOF000I to AOF969I
75
AOF730I • AOF743I
be reissued from the pass indicated in the message.
The variable subsystem shows the subsystem name.
The variable type shows the type of spool problem
being recovered. Possible values are SHORT and
FULL.
The variable pass shows the recovery pass that was
to be issued.
The variable reason shows the reason that system
automation has not issued the recovery pass.
System action: The spool recovery continues. No
recovery passes are issued.
Operator response: Reset the Recover automation flag
if that is the problem and you wish the suspended
recovery commands to be reissued.
System programmer response: Investigate the cause
of the blockage. Take appropriate action to stop it from
occurring again.
Classes: 40 45.
AOF730I
SPECIFIED OPERAND operand
INVALID FOR request
Explanation: An operand specified on a command
conflicts with the request.
The variable operand shows the operand that is
invalid.
The variable request shows the parameter that the
operand conflicts with and why.
flag was set to NO, the shutdown could not be
performed.
The variable subsystem shows the name of the
affected subsystem.
System action: None.
Operator response: If you want to shut down the
subsystem regardless of its flag setting, reissue the
INGREQ REQ=STOP request specifying
OVERRIDE=FLG, or ALL if you also want to override
other conditions.
System programmer response: None.
Classes: None.
AOF742D
ENTER >GO< TO PROCEED OR
>CANCEL< TO CANCEL REQUEST OR
>R< TO REDISPLAY, USER=userid
Explanation: An operator command such as INGREQ
or INGMOVE has been entered with VERIFY=WTOR
specified. AOF742D is preceded by AOF778I that lists
the resources that will be affected by the request.
The variable userid shows the operator ID where the
request originated. This can be used to tie AOF742D
to the associated AOF778I.
System action: The operator is prompted by a WTOR.
Operator response: Verify the list of affected resources
and reply with either GO or CANCEL to the WTOR or
reply R to redisplay message AOF778I.
System action: None.
System programmer response: None.
Operator response: Reenter the request with the
correct operand.
Classes: None.
System programmer response: None.
AOF743I
Classes: None.
AOF732I
SHUTDOWN PROCESSING RESUMED
Explanation: Shutdown processing has been resumed.
Shutdown attributes have not been updated.
The variable shutdown_id shows the ID of the
shutdown that has been resumed.
System action: None.
Operator response: None.
System programmer response: None.
SHUTDOWN WILL NOT
(RE)PROCESS SUBSYSTEM subsystem
AS IT IS status
Explanation: The shutdown considered shutting the
named subsystem down, but then did not because it
was not in a suitable state.
The variable subsystem shows the name of the
subsystem being processed.
The variable status shows the current state of the
subsystem.
System action: The thread of the shutdown process
that found the problem will cease. The message does
not necessarily indicate a problem.
Classes: None.
Operator response: If the subsystem is in an error
state you should recover it manually.
AOF735I
System programmer response: This message normally
indicates that the shutdown process has already started
to shut a subsystem down. This message may also be
issued if the subsystem is in a STOPPING or DOWN
status.
UNABLE TO PROCESS SHUTDOWN AUTOMATION IS SET OFF FOR
subsystem
Explanation: Shutdown processing was unable to shut
down the subsystem because the Terminate flag was set
to OFF. Because the option for overriding the Terminate
76
System Automation for z/OS Messages and Codes:
Classes: 40, 43.
AOF745E • AOF748E
AOF745E
SHUTDOWN FOR SUBSYSTEM
subsystem : SUBSYSTEM NOT FOUND
AND NO FINAL TERMINATION
MESSAGE RECEIVED. SHUTDOWN
SUSPENDED FOR time MINUTES
Explanation: The shutdown monitoring has detected
that the named subsystem has cleared address space,
but that its final termination message was not received
within at least 60 seconds of this happening.
The variable subsystem shows the name of the
subsystem being processed.
The variable time shows the number of minutes the
system will wait.
System action: The system waits up to time minutes
for the subsystem's final termination message to arrive.
If it does not, the shutdown will assume that the
subsystem has terminated and issue the appropriate
final message for the subsystem.
Operator response: Check that the subsystem has
properly terminated. If it has not, you must help it
manually as no more shutdown commands will be
issued for it. If it has terminated normally, refer the
problem to your system programmer.
System programmer response: Determine the reason
that the final termination message was missed. You
may need to correct your NetView automation table, or
change it to use a better message. MPF is another place
where the message could have been lost.
Classes: 40 46.
AOF746A
SHUTDOWN FOR SUBSYSTEM
subsystem : NORMAL SHUTDOWN
PROCESSING HAS BEEN
SUSPENDED AS THE SUBSYSTEM IS
status
Explanation: A subsystem being shutdown by a
normal shutdown (SHUTNORM) has entered either an
ABENDING or BREAKING status. No further
SHUTNORM commands will be issued.
The variable subsystem shows the name of the
subsystem being processed.
The variable status shows the current status of the
subsystem.
System action: The shutdown is suspended until the
subsystem stops or the shutdown is modified to use a
more aggressive set of shutdown commands. Both
immediate and force shutdown commands can be
issued against such subsystems.
Operator response: Determine the state of the
subsystem. If it will eventually terminate you don't
have to do anything. If more commands are needed to
effect a shutdown, either issue them manually or
modify the type of the shutdown for that subsystem.
Refer the problem to your system programmer.
System programmer response: Examine the shutdown
commands and the NetView automation table entries. If
the normal shutdown commands cause the subsystem
to abend this situation will recur.
Classes: 40 46.
AOF747A
SHUTDOWN FOR SUBSYSTEM
subsystem IS STUCK. THE SUBSYSTEM
IS NOT SHUT DOWN BUT THERE
ARE NO MORE type PASSES TO ISSUE
Explanation: SA z/OS has issued all defined
shutdown passes for a subsystem, but the subsystem
has not stopped. Operator assistance is required to
continue with the shutdown.
The variable subsystem shows the name of the
subsystem being processed.
The variable type shows the type of shutdown
commands being issued.
System action: The shutdown of the subsystem is
unable to proceed. It will hang until either the
subsystem is stopped by an external agency or the
shutdown is cleared.
Operator response: Determine the status of the
subsystem. If it is in the process of stopping, wait. If
the subsystem is not stopping, either upgrade the type
of shutdown commands being issued or shut it down
manually. Inform your system programmer of the
problem.
System programmer response: Examine your
shutdown commands. If they are not sufficient to stop
the subsystem, upgrade them. If the subsystem is
consistently taking too long to stop either increase the
subsystem’s delay or add some dummy passes to the
end of the shutdown commands.
Classes: 40 46.
AOF748E
SHUTDOWN FOR SUBSYSTEM
subsystem : SUBSYSTEM NOT FOUND
AND NO FINAL TERMINATION
MESSAGE RECEIVED. AUTOMATED
SHUTDOWN RESUMES
Explanation: The system is resuming a shutdown that
was suspended when a subsystem cleared address
space without issuing a final termination message. No
such message has since been received, and it seems
unlikely that one will be.
The variable subsystem shows the name of the
subsystem being processed.
System action: System automation issues the final
termination message on behalf of the subsystem. The
shutdown proceeds as if the message had arrived
normally.
Operator response: Inform your system programmer
about the failure of the system to recognize the
Chapter 2. Messages AOF000I to AOF969I
77
AOF749I • AOF752E
subsystem’s final termination message.
System programmer response: Examine your
shutdown commands and NetView automation table
entries. It is likely that they are not trapping the
subsystem’s final termination message, and this is
causing unnecessary delays in your shutdown
processing.
your shut delay times or contacting your IBM Support
Center, or both.
Classes: 40 46.
AOF751I
Classes: 40 46.
AOF749I
SHUTDOWN COMPLETE FOR resource.
(RESTART=restart, TYPE=shuttype)
Explanation: The indicated shutdown has completed
successfully.
The variable resource shows the name of the
resource that has been shut down.
The variable restart indicates what happens to the
resource after the shutdown is complete. The value
of restart can be YES.
The variable shuttype indicates the shutdown type.
System action: None.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF750I
SHUTDOWN FOR SUBSYSTEM
subsystem MAY HAVE FAILED TO
ISSUE SOME shuttype itemtype ON PASS
pass
Explanation: While issuing the shutdown commands
for the named pass return codes from AOFCMD or
AOFRPY indicated that they may have failed to issue
some of their commands or replies.
The variable subsystem shows the name of the
subsystem being processed.
The variable shuttype shows the type of shutdown
passes being issued.
The variable itemtype shows the COMMANDS or
REPLIES indicating what failed.
The variable pass shows the pass of shutdown
processing that it occurred on.
System action: The shutdown continues. If it did fail
to issue the commands the shutdown may become
stuck and issue an AOF747E message when it runs out
of passes.
Operator response: Check the netlog and the system
log to see whether the proper shutdown commands
were issued. If they were not, you may need to shut
the subsystem down manually.
System programmer response: Check that the
shutdown commands are all valid when issued from a
NetView console. If they are not, fix them. If you still
get regular occurrences of this message try altering
78
System Automation for z/OS Messages and Codes:
CLEAN UP FOR SHUTDOWN DID
NOT CHANGE THE STATUS OF
SUBSYSTEM subsystem TO RESTART
BECAUSE reason
Explanation: While a shutdown with RESTART=YES
was being cleaned up, the status of the specified
subsystem was not changed to RESTART for the reason
given.
The variable subsystem shows the name of the
subsystem being processed.
The variable reason shows the reason that the
change was not made.
System action: The clean up continues. The named
subsystem and its children will not be restarted when it
is complete.
Operator response: To restart the subsystem, use the
SETSTATE command.
System programmer response: If the message was
issued because the subsystem abended or broke, you
should check it out and, if the process was a normal
part of its shutdown, change your automation so that it
no longer enters an error state.
Classes: 40 43.
AOF752E
SHUTDOWN FOR SUBSYSTEM subsys
SUSPENDED. THE TERMINATE FLAG
IS CURRENTLY TURNED OFF
Explanation: When the shutdown attempted to shut
the specified subsystem down it checked its Terminate
flag and found it to be turned off. No passes will be
processed for the subsystem until the flag is turned on.
The variable subsys shows the name of the
subsystem being processed.
System action: The shutdown is suspended. The
shutdown CLISTs will be redriven every shut delay to
recheck the Terminate flag. As soon as they find it
turned on the next pass of shutdown commands will
be issued.
Operator response: If you do nothing the shutdown
remains suspended until the flag is turned on (possibly
at the end of a NOAUTO or a TIMEOUT period). You
could force the flag to change with the INGAUTO
command.
System programmer response: Check whether the
reason why the flag was turned off was valid. Ensure
that the operators have instructions to deal with this
situation should it arise again.
Classes: 40 46.
AOF755I • AOF760E
AOF755I
SHUTDOWN FOR SUBSYSTEM
subsystem : type PASS pass :
AOFSHUTMOD SET TO value
Explanation: The shutdown processing found that the
AOFSHUTMOD variable had been set to a non-null
value by the subsystem’s shutdown commands.
The variable subsystem shows the name of the
subsystem being processed.
AOF759A
AUTOMATED STARTUP FOR
SUBSYSTEM subsystem MAY HAVE
FAILED : RC rc FROM "ACFCMD
MSGTYPE=STARTUP,ENTRY=
subsystem"
Explanation: System automation tried to start a
subsystem. The ACFCMD call failed, giving the
indicated return code.
The variable type shows the type of shutdown being
processed.
The variable subsystem shows the name of the
subsystem being processed.
The variable pass shows the pass of the shutdown
being processed.
The variable rc shows the return code from the
ACFCMD call.
The variable value shows the value of the
TGLOBAL.
System action: The shutdown process continues. If the
value is recognized by the shutdown process it will be
used to alter the shutdown’s flow. If it is not
recognized it will be ignored. Recognized keywords are
NOW, DELAY, ABORT and NEXTPASS. Note that both
DELAY and NEXTPASS require their parameters to be
correct.
Operator response: Notify your system programmer if
the value is invalid. Note that if the parameter on a
DELAY statement was invalid the automated shutdown
will have stopped and you should shut the affected
subsystem down manually.
System programmer response: If the value is invalid,
set the value in the AOFSHUTMOD variable correctly.
Classes: 40, 43.
AOF757I
UNABLE TO PROCESS action FOR
resource - reason
Explanation: You invoked INGREQ for a resource.
System action: The startup will probably fail. The
subsystem’s status will have been updated to
INACTIVE with an appropriate message. If the
subsystem does start, it will be processed normally.
Operator response: You must start the subsystem
manually. Refer the problem to your system
programmer.
System programmer response: The definition for the
subsystem is either wrong or incomplete. Fix the
definitions through the customization dialgos.
Classes: 40 46.
AOF760E
condition CONDITION TRAPPED IN
clist LINE sourceline (CODE error_num)
DESCRIPTION description
Explanation: A REXX CLIST has encountered a fatal
error condition.
The variable condition shows one of NOVALUE,
SYNTAX, HALT, or FAILURE.
The variable clist shows the name of the CLIST that
the error was trapped in.
The variable action shows the action that cannot be
performed, for example, STARTUP.
The variable sourceline shows the source line
number where the condition occurred.
The variable resource shows the name of the affected
resource.
The variable error_num shows N/A or SYNTAX
error number or FAILURE return code.
The variable reason shows an explanation why the
action could not be performed.
The variable description shows the NOVALUE
variable name, SYNTAX error description etc.
System action: INGREQ stops processing.
Operator response: Change the parameters in the
INGREQ call. If necessary, contact your system
programmer.
System programmer response: Ensure that the
resource can be managed by system automation (start
and stop commands defined, automation flags turned
on, etc.).
Classes: None.
System action: The CLIST ends with code -5, causing
calling CLISTs to end.
Operator response: Report the problem to your
system programmer, unless the condition is operator
caused (for example, NetView CLOSE causing a HALT
condition).
System programmer response: Report the problem to
your IBM Support Center.
Classes: 40 46.
Chapter 2. Messages AOF000I to AOF969I
79
AOF761E • AOF766I
AOF761E
entry NOT ACTIVE; description
Explanation: The ACF loader did not find an expected
entry to be ACTIVE.
The variable entry shows the entry that was
expected to be ACTIVE.
The variable description shows details about the
probable consequences of the entry not being
ACTIVE.
System action: Processing terminates.
Operator response: None.
System programmer response: Investigate why this
entry is not ACTIVE and correct the error. Then issue a
cold start.
Classes: 40 46.
AOF762I
entry NOT ACTIVE; description
Explanation: The ACF loader did not find an expected
entry to be ACTIVE.
The variable entry shows the entry that was
expected to be ACTIVE.
The variable description shows details about the
probable consequences of the entry not being
ACTIVE.
System action: None.
Operator response: None.
System programmer response: Examine the
description and determine whether or not you wish
this entry to be ACTIVE. If you do not require this
entry to be ACTIVE, correct the reason why it is not
ACTIVE. Then issue a cold start.
Classes: 40 46.
AOF763I
GATEWAY EXCMD TO OPERATOR
operator_ID FAILED, RC= return_code ,
COMMAND ( command_text )
Explanation: A Gateway operation cannot be
completed because the EXCMD to transfer command
has failed.
Classes: 40, 43.
AOF764I
field_name DOMAIN NAME domain_ID
INVALID - reason
Explanation: While reading the control file or when
processing the domain operand of a command or panel
a domain_ID has been rejected.
The variable field_name shows the field where the
domain_ID is declared
The variable domain_ID shows the domain_ID that
has been rejected. The variable reason shows the
explanation for the rejection.
System action: The control file entry, or the command
is ignored.
Operator response: If a control file error, report the
problem to your system programmer. If a command
error, correct the domain name if in error.
System programmer response: Correct the domain
name in the control file entry, or define the domain in
the DSIPARM data set, member DSIDMN, or the
NetView style sheet.
Classes: None.
AOF765E
NO entry DEFINED; description
Explanation: The ACF loader did not find an expected
entry in the automation control file.
The variable entry shows the entry that was
expected.
The variable description shows details about the
probable consequences of not supplying the entry.
System action: Processing terminates.
Operator response: None.
System programmer response: Add the required data
through the customization dialogs.
Classes: 40 46.
The variable command_text shows the command that
failed.
AOF766I
The variable operator_ID shows the ID of the
operator that the command was sent to.
Explanation: The loader did not find an expected
entry in the automation control file.
The variable return_code shows the return code from
the failed command.
System action: The CLIST continues. The command
will not have been actioned.
Operator response: Report the problem to your
system programmer.
System programmer response: Determine why the
operator is inactive or the EXCMD failed. If the
80
command is AOFMSG, check whether another domain
is sending messages to be issued by a non-existent
operator.
System Automation for z/OS Messages and Codes:
NO entry DEFINED; description
The variable entry shows the entry that was
expected
The variable description details the likely
consequences of not supplying the entry.
Note that when the description indicates that
PLEXOPER is not defined and "PROCESSOR AND/OR
IMAGECNTL DATA IGNORED", the ISQSTART
command will fail and ProcOps will be unavailable
AOF767I • AOF771I
unless the Automated Function PLEXOPER is correctly
defined in the OPERATORS Policy Item.
appropriate entry to the automation control file.
Classes: 40 46.
System action: None.
Operator response: None.
System programmer response: Examine the
description and determine whether or not you wish to
include the entry.
Classes: 40 46.
AOF767I
AUTOMATION OPTIONS:
Explanation: This is the first line in a multiline
message block that appears at system automation
initialization. The lines of the message block define the
options that can be specified for system automation
initialization.
Note: Your response to this message block and its
following WTORs is the chief means of determining
how your system is automated. You should understand
clearly the details of the message block as explained in
the IBM Tivoli System Automation for z/OS User's Guide.
System action: AOF767I is followed by either an
AOF603D or an AOF606D message. These are WTORs
that can be responded to. System automation replies
automatically to an AOF603D after two minutes with
default values unless this has been changed as a part of
your site’s automation policy. System automation does
not automatically reply to an AOF606D message unless
this has been changed as a part of your site’s
automation policy.
Operator response: Varies. Refer to IBM Tivoli System
Automation for z/OS User's Guide for details. Generally,
reply to the AOF603D or AOF606D WTOR, or, for the
AOF603D WTOR, let it time out.
System programmer response: Varies. Refer to IBM
Tivoli System Automation for z/OS User's Guide for
details.
Classes: None.
AOF769I
TIMER IDS STARTING WITH prefix
ARE RESERVED FOR SYS-OPS
SYSTEM USE
Explanation: An attempt was made to delete, change
or add a timer with a timer ID that starts with the
character sequence prefix.
The value of the variable prefix is either 'AOF',
'ING', or 'ITMR'.
SA z/OS uses a timer ID prefix of 'AOF', 'ING', or
'ITMR' to distinguish its timers from other NetView
timers and SA z/OS user timers. The operator interface
prevents these timers from being altered. The control
file initialization will not set a timer that starts with
'AOF', 'ING' or 'ITMR' because it might override a
SA z/OS system timer. Note timers with a prefix of
'ITMR' cannot be deleted.
System action: The timer request was not processed.
Operator response: Change the timer ID to have
another prefix. If you want to delete a SA z/OS system
timer, use the NetView PURGE TIMER command. Do
not purge any SA z/OS system timer unless you are
certain of the consequences.
System programmer response: None.
Classes: 40, 43.
AOF770I
THIS FUNCTION IS NOT AVAILABLE
IN LINEMODE
Explanation: An attempt was made to execute a
CLIST as a linemode command when the CLIST does
not support the linemode facility.
System action: None.
Operator response: Issue command on an OST task to
see command output.
System programmer response: None.
AOF768I
SUBSYSTEM subsys_name REQUIRES
entry : NOT FOUND IN AUTOMATION
CONTROL FILE
Explanation: An entry that is required for a specific
subsystem was not found in the automation control file.
You may have a problem using this subsystem.
The variable subsys_name shows the name of the
subsystem in question.
The variable entry shows the entry missing from the
automation control file.
System action: None.
Operator response: None.
System programmer response: Consider adding the
Classes: None.
AOF771I
REQUEST command REJECTED, action
IN PROGRESS
Explanation: The issued request cannot be processed
at this time because a startup or shutdown is still in
progress.
The variable command shows the request that failed.
The variable action shows either STARTUP or
SHUTDOWN.
System action: Request is canceled.
Operator response: Wait for startup or shutdown to
complete or clear shutdown before reissuing request.
Chapter 2. Messages AOF000I to AOF969I
81
AOF772I • AOF779I
System programmer response: None.
System action: As described in action.
Classes: None.
Operator response: None.
System programmer response: None.
AOF772I
PARSING ERROR PROCESSING input error
Explanation: While processing the indicated item of
input the parsing routine found an error.
The variable input shows the input that was being
parsed when the error was detected.
The variable error shows the error that occurred.
System action: The command stops processing.
Operator response: Correct the parameter strings and
rerun the command.
System programmer response: If the error occurred
from within a CLIST you must edit the CLIST to fix the
problem.
Classes: None.
AOF773I
YOUR INSTALLATION AUTOMATION
POLICY DISALLOWS AN ACF
RELOAD
Classes: 40, 43.
AOF776I
CONNECTION FROM DOMAIN
domain_id_1 sdfroot_name REJECTED AT
DOMAIN domain_id_2 - reason
Explanation: An attempt to establish a cross-domain
gateway has failed.
The variable domain_id_1 shows the domain
attempting to connect.
The variable sdfroot_name shows the system
attempting to connect.
The variable domain_id_2 shows the domain
rejecting the connection.
The variable reason shows the reason for rejecting
the connection.
System action: The connection will be tried again at
gateway monitor time.
Operator response: None.
Explanation: A reload of the automation control file
has been requested but your automation flags indicate
that a reload is not allowed.
System programmer response: The gateway
definitions in the automation control file on either or
both domains need correction to ensure compatibility.
System action: The reload process is abandoned.
Classes: 40, 43.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
AOF774A
YOUR INSTALLATION AUTOMATION
POLICY REQUIRES CONFIRMATION
OF AN ACF RELOAD - ENTER “GO”
TO CONTINUE OR “CANCEL” IF YOU
DO NOT WISH TO PROCEED
Explanation: A reload of the automation control file
has been requested but your installation automation
policy requires confirmation from the operator.
System action: Waits for operator response.
Operator response: Enter "GO" or "CANCEL".
System programmer response: None.
Classes: None.
AOF778I
VERIFY AFFECTED RESOURCES FOR
REQUEST "request", USER=userid
Explanation: An operator command such as INGREQ
or INGMOVE has been entered with VERIFY=WTOR
specified. This multiline WTO lists all the resources that
will be affected by the request.
The variable request shows the type of request
entered.
The variable userid shows the operator ID
originating the request. This can be used to tie
AOF778I to the associated AOF742D.
System action: WTOR message AOF742D will be
issued after AOF778I.
Operator response: Verify the list of affected resources
before replying to message AOF742D.
System programmer response: None.
Classes: None.
AOF775I
OPERATOR ENTERED response - action
Explanation: This message confirms a response
entered by an operator.
The variable response shows the operator response.
The variable action shows the action taken by the
system.
82
System Automation for z/OS Messages and Codes:
AOF779I
VALID RUNMODES ARE:
Explanation: This is the first line in a multiline
message block that appears when RUNMODE=? was
entered as a response to AOF603D. The lines of the
message block show all valid runmodes and their
runtokens for the current system.
AOF780E • AOF787A
System action: AOF767I and AOF603D are
re-displayed.
Operator response: Contact your system programmer.
Operator response: None.
System programmer response: Correct the problem
identified by other messages.
System programmer response: None.
Classes: None.
Classes: None.
AOF784I
AOF780E
INTERNAL ERROR AT LOCATION loc.
UNABLE TO CONTINUE
Explanation: An internal error occurred at the
specified location in the program code.
System action: Processing is terminated.
Operator response: Contact your system programmer.
AUTOMATION CONTROL FILE
MEMBER file IS EMPTY OR DOES
NOT EXIST
Explanation: An INCLUDE member was processed
but did not contain any records or the member does
not exist.
The variable file shows the name of member that
caused the error.
System programmer response: Contact IBM Support
Center.
System action: Processing continues.
Classes: None.
System programmer response: Correct the automation
control file.
AOF781I
SERVICE REQUEST req FAILED AT
LOCATION loc WITH RC= rc
Explanation: A service routine ended with a non-zero
return code.
The variable req identifies the service request that
failed.
The variable loc identifies the location in the code
where the failure occurred.
The variable rc is the return code from the service
routine.
System action: Processing terminates.
Operator response: Contact your system programmer.
System programmer response: Perform problem
determination and correct the problem.
Classes: None.
Operator response: Contact your system programmer.
Classes: 40, 43.
AOF785I
Explanation: An INCLUDE member name in member
is invalid, blank or contains invalid characters. The
member name is ignored.
The variable member name shows the name of
member that caused the error.
System action: Processing continues.
Operator response: Contact your system programmer.
System programmer response: Correct the member
name.
Classes: 40, 43.
AOF786A
AOF782I
AUTOMATION CONTROL FILE
PROCESSING COMPLETED
INVALID INCLUDE NAME IN
MEMBER member name
NO DATA FOUND IN AUTOMATION
CONTROL FILE file
System action: Processing continues.
Explanation: When the automation control file was
processed only comments, blank lines and INCLUDE
statements were found. There was no system
automation control information.
Operator response: None.
System action: Processing stops.
System programmer response: None.
Operator response: Contact your system programmer.
Classes: None.
System programmer response: Correct the automation
control file.
AOF783A
Classes: None.
Explanation: The automation control file was
processed and completed with no errors.
AUTOMATION CONTROL FILE
PROCESSING HAS FAILED
Explanation: The processing of the automation control
file resulted in a fatal error. No control information is
processed.
System action: Processing is terminated.
AOF787A
TERMINATING ERROR WHEN
PROCESSING CONTROL FILE file
Explanation: Input from automation control file file
contained an error that prevented any system
automation control information from being processed.
Chapter 2. Messages AOF000I to AOF969I
83
AOF789I • AOF802I
System action: Processing stops.
AOF797A
Operator response: Correct the command or contact
your system programmer.
System programmer response: Correct the automation
control file or command error as identified by other
diagnostic messages.
Classes: None.
YOUR INSTALLATION POLICY HAS
STOPPED SYS-OPS INITIALIZATION
BECAUSE OF ERRORS
Explanation: During a load or reload of the
automation control file errors were detected. Your
installation has set the automation global variable
AOFACFINIT to stop initialization.
System action: Initialization processing stops.
AOF789I
COMMAND LINE PARAMETER parm
INVALID
Explanation: Command line parameter parm is not
valid for the command issued.
Operator response: Notify your system programmer.
System programmer response: Correct the errors to
do with the automation control file and reload it.
Classes: 40 46.
System action: Processing is terminated.
Operator response: Reissue the command or contact
your system programmer.
AOF800I
System programmer response: Correct the command.
Explanation: This message is intended for your IBM
Support Center to use in debugging internal system
automation errors.
Classes: None.
AOF790I
THRESHOLD INTERVALS MUST BE:
CRITICAL < FREQUENT <
INFREQUENT
Explanation: For threshold checking to function
correctly, the error intervals (time interval divided by
error count) must be organized correctly. The error
interval for the critical threshold should be a smaller
interval than that for the frequent threshold, which
should be smaller than the infrequent threshold.
System action: The threshold values are not changed.
Operator response: Issue the INGTHRES command
again and enter count and time data so that the
intervals are correct.
The variable module_name shows the module that
issued the message.
The variable return_code shows the return code from
the module.
System action: None.
Operator response: None.
System programmer response: Contact IBM Support
Center.
Classes: 0.
AOF801E
System programmer response: None.
Classes: None.
AOF791I
AUTOMATION CONTROL FILE
PROCESSING COMPLETED WITH
ERRORS
Explanation: The specified automation control file was
processed and control data were obtained but some
errors were encountered during processing
System action: Processing continues.
Operator response: Contact your system programmer.
System programmer response: Correct the errors
identified by other diagnostic messages.
Classes: None.
FOR IBM SERVICE USE ONLY:
MODULE: module_name RC: return_code
REMOTE PROCESSING
ENCOUNTERED AN INTERNAL
ERROR UNEXPECTED RESULTS MAY
OCCUR AS PROCESSING
CONTINUES.
Explanation: Processing will continue but the results
will be unpredictable.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Contact IBM Support
Center.
Classes: 40.
AOF802I
INTERNAL ERROR DETECTED IN
clist, ERROR DATA:
Explanation: An internal error occurred in the
specified CLIST.
The variable clist shows the name of the CLIST.
System action: The requested function is not
performed.
84
System Automation for z/OS Messages and Codes:
AOF803I • AOF818I
Operator response: Contact your system programmer.
System programmer response: Contact your IBM
Support Center.
Classes: None.
AOF803I
data
Explanation: This message is part of a multiline
message that begins with message AOF802I.
The variable data contains error data specific to the
failed CLIST.
current size of the data space up to the maximum size
defined in the DSIPARM member AOFINIT. Check
whether the data space has reached the installation
limit. The command SDFQTR returns information for
the current allocation units.
AOF816I
EXTENDED MCS CONSOLE console
FOR TASK task HAS BEEN OBTAINED
Explanation: The automation obtained an extended
MCS console for the named task because the default
extended MCS console is already in use.
System action: None.
The variable console shows the name of the extended
MCS console obtained for the task.
Operator response: None.
The variable task shows the name of the task.
System programmer response: Contact your IBM
Support Center.
Classes: None.
AOF814I
Macro aa type bb request was
unsuccessful, RC=cc, RSN=dd
Explanation: The program called the indicated macro.
The macros was not able to satisfy the request and
returned the indicated return code for use in problem
determination.
System action: None.
Operator response: If an MVS command was issued
before receiving this message, the command should be
reissued.
System programmer response: None.
Classes: None.
AOF817I
The variable aa shows the name of the macro.
The variable bb shows the type of the request.
The variable cc shows the return code of the macro.
The variable dd shows the reason code of the macro.
UNABLE TO OBTAIN AN EXTENDED
MCS CONSOLE console FOR TASK task
reason
Explanation: The automation was unable to obtain an
extended MCS console for the named task.
The variable console shows the name of the extended
MCS console obtained for the task.
System action: None.
The variable task shows the name of the task.
Operator response: Contact your system programmer.
The variable reason explains why the command
AOCGETCN failed.
System programmer response: Check the return code
to determine the cause of the problem.
System action: None.
Operator response: Notify your system programmer.
AOF815I
AOF815I Data space service request
failed, RC=aa
Explanation: The program failed to reserve a new
control block in the data space that holds status
component information. The reservation failed with the
indicated return code.
System programmer response: If the console is
already in use, update the common global variable
AOFCNMASK to define a unique console name.
Classes: None.
RODM RETURN CODE return_code ,
REASON CODE reason_code
The variable aa shows the return code of the
request:
AOF818I
36 The data space ran out of space.
Explanation: A call to RODM has resulted in an
unexpected return code.
40 The data space could not be extended.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Return code 36
indicates that the maximum size defined in the
DSIPARM member AOFINIT is not sufficient for your
environment. Increase the value of the parameter
MAXTREEDSPSZ and restart the task AOFTDDF.
The variable return_code shows the return code.
The variable reason_code shows the reason code.
System action: None.
Operator response: None.
System programmer response: Examine the return
and reason codes in association with other messages
displayed.
Return code 40 indicates a problem in extending the
Chapter 2. Messages AOF000I to AOF969I
85
AOF821I • AOF833I
Classes: 40.
AOF821I
AOF830I
DSIDKS FAILED FOR reason
PROCESSING, INTERNAL ERROR
Explanation: The NetView DSIDKS macro has
returned a non-zero return code.
The variable reason shows the reason for the failure.
This is either CONNECT, READ, or DISCONNECT.
System action: The request terminates.
Operator response: None.
System programmer response: Run the NetView
trace. Retry the request.
Explanation: A search item that was specified was not
found and has been removed from the search list.
System action: Either re-specify search criteria or
leave as is.
Operator response: None.
System programmer response: None.
Classes: None.
AOF831I
Classes: None.
AOF824I
NEVER SHOULD OCCUR, INVALID
DATA, CONTACT IBM SERVICE WITH
DIAGNOSTIC DUMP
Explanation: Invalid data has been detected.
A SPECIFIED LIST ITEM WAS NOT
FOUND, AND WAS REMOVED FROM
THE LIST
THE WILDCARD CHARACTER '*'
VOIDS ALL OTHER ITEMS IN THE
LIST
Explanation: The "*" is a global wildcard and
overrides all other search criteria (if any).
System action: None.
System action: Produces a diagnostic dump.
Operator response: If you do not want to override all
other seacrch criteria respecify search criteria.
Operator response: Notify your system programmer.
System programmer response: None.
System programmer response: Contact your IBM
Support Center.
Classes: None.
Classes: None.
AOF832I
AOF826I
M dev,volser, RECEIVED ON mm/dd/yy
AT hh:mm:ss COMPLETED ON mm/dd/yy
AT hh:mm:ss
Explanation: This message is created by tape mount
monitoring. It is generated by a delete operator
message (DOM) for an outstanding tape mount. The
NetView automation table should be configured to trap
this message and initiate the deletion of the associated
tape mount icon on the workstation.
The variable dev shows the device number that a
tape mount request for was satisfied or canceled.
The variable volser shows the volume serial that a
tape mount request for was satisfied or canceled.
The variables mm/dd/yy and hh:mm:ss show date and
time respectively.
System action: The workstation tape mount icon for
the nominated device and volume is deleted.
Operator response: None.
System programmer response: None.
Classes: None.
A DUPLICATE ITEM WAS SPECIFIED
IN THE LIST AND HAS BEEN
REMOVED
Explanation: The search criteria had duplicate items
or two items were specified and were reduced to a
single item, for example, JES and JES2 are reduced to
JES.
System action: Either re-specify search criteria or
leave as is.
Operator response: None.
System programmer response: None.
Classes: None.
AOF833I
AN INCORRECT STATUS WAS
SPECIFIED AND HAS BEEN
REMOVED
Explanation: A status was specified that is not known
to system automation.
System action: Respecify status search criteria.
Operator response: None.
System programmer response: None.
Classes: None.
86
System Automation for z/OS Messages and Codes:
AOF834I • AOF838A
AOF834I
INCORRECT NESTING LEVEL
SPECIFIED, IT MUST BE A NUMBER
OR AN '*'
Explanation: An incorrect nesting level was specified.
The nesting level should be re-specified as either a
number (0-9) or an "*".
AOF837I
A COMMAND WAS ENTERED WITH
A JES2 PREFIX character THAT IS NOT
DEFINED IN THE AUTOMATION
CONTROL FILE
Operator response: None.
Explanation: The command that was entered began
with a character that is defined as a command
synonym for the AOC/MVS JES2 command. However,
it has not been defined in an automation control file
entry for JES2. The variable charactershows the prefix.
System programmer response: None.
System action: The command is not processed.
Classes: None.
Operator response: Reenter the command with the
correct prefix.
System action: Re-specify status search criteria.
AOF835I
clist_name: ENTRY SPECIFICATION:
subsystem_name LENGTH EXCEEDS
length, PLEASE RE-ENTER
Explanation: An entry name has more than the
maximum number of characters allowed. Reenter the
entry name.
The variable clist_name shows the name of the
command list that generated this message.
The variable subsystem_name shows the offending
entry name.
The variable length shows the maximum permissible
length of the entry name.
System action: None.
Operator response: Reenter entry specification.
System programmer response: None.
Classes: None.
AOF836I
clist_name: TYPE SPECIFICATION:
subsystem_name LENGTH EXCEEDS
length, PLEASE RE-ENTER
Explanation: A type name has more than the
maximum number of characters allowed. Reenter the
type name.
The variable clist_name shows the name of the
command list that generated this message.
System programmer response: If the character is not
intended as a JES2 prefix removed it from the
command synonym member (usually AOFCMD). Else,
define it in the customization dialog - Application
Definition panels for JES2.
Classes: None.
subsystem type RECOVERY
COMMANDS EXHAUSTED
AOF838A
Explanation: While attempting to perform JES3
recovery, system automation ran out of defined
recovery commands before recovery was complete.
System automation will re-execute the recovery
command sequence starting from the first pass.
The variable subsystem indicates the name of the
subsystem.
The variable type shows the type of JES3 recovery being
performed. Possible values are:
SPOOLSHORT for SPOOL
MDSCOUNTA for ALLOCATION Queue
MDSCOUNTB for BREAKDOWN Queue
MDSCOUNTE for ERROR Queue
MDSCOUNTF for FETCH Queue
MDSCOUNTQ for NUMBER OF JOBS
MDSCOUNTR for RESTART Queue
The variable subsystem_name shows the offending
type name.
MDSCOUNTU for UNAVAILABLE Queue
The variable length shows the maximum permissible
length of the type name.
MDSCOUNTW for WAIT VOLUME Queue
MDSCOUNTV for VERIFY Queue
MDSCOUNTSS for SYSTEM SELECT Queue
System action: None.
MDSCOUNTSV for SYSTEM VERIFY Queue
Operator response: Reenter type specification.
or any user-defined type.
System programmer response: None.
System action: JES3 recovery continues.
Classes: None.
Operator response: Look at SPOOL or MDS usage.
System automation may need some assistance to keep
it in control.
System programmer response: Review your JES3
recovery commands.
Classes: 40 44
Chapter 2. Messages AOF000I to AOF969I
87
AOF839I • AOF851I
AOF839I
CONTROL FILE SYNTAX ERROR
THRESHOLD REACHED. CONSOLE
REPORTING OF SYNTAX ERRORS
SUSPENDED - PROCCESSING
CONTINUES.
Explanation: Syntax errors that were detected when
processing this automation control file have reached the
reporting threshold. Subsequently detected syntax
errors in this automation control file will be recorded in
the netlog, but will not be reported on the console.
System action: Processing of the automation control
file continues.
AOF845I
COMMAND REJECTED command
COMMAND IS TOO LONG
Explanation: The command exceeds the maximum
length of commands. The command cannot be
executed.
The variable command shows the name of the
command that could not be executed.
System action: None.
Operator response: Try to simplify the command and
make it shorter.
System programmer response: None.
Operator response: Check the netlog to see
automation control file syntax error messages.
Classes: None.
System programmer response: None.
AOF850I
Classes: None.
AOF840E
ERROR EXTRACTING RODM DATA
FOR THE type OBJECT. RODM
RETURN CODE retcode. RODM
REASON CODE reason.
Explanation: The command cannot be executed
because the RODM look-up failed and vital information
could not be retrieved.
System action: The command is not executed.
The variable type is the RODM object type.
The variable retcode is the RODM return code.
The variable reason is the RODM reason code.
Operator response: Notify your system programmer.
System programmer response: The retcode and reason
are the RODM return and reason codes, which are
documented in theNetView RODM Programming Guide.
Classes: None.
AOF841E
THE RODM NAME OR RODM USER
ID COULD NOT BE DETERMINED.
Explanation: The command cannot be executed
because the RODM name or user ID used to access
RODM could not be determined.
ISSUED INGSEND
RESP=resp,OPER=oper,TO=domain,
CRM=crm,CORRWAIT=corr,
CMD="command"
Explanation: This is to confirm the complete
INGSEND command routed to the target system. This
message is logged to the local and target netlog. This
message is issued only by INGSEND when
CRM=RMTCMD.
The variable onet.odom.oopr shows the origin
network ID, domain ID and operator ID.
The variable resp shows what to do with the
responses, if any.
The variable oper shows the target RMTCMD
autotask ID.
The variable domain shows the target domain ID.
The variable crm shows the command routing
mechanism used.
The variable corr shows the value used on the
NetView Pipe command Corrwait stage.
The variable command shows the command to be
executed.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: None.
System action: The command is not executed.
Operator response: Make sure that system automation
focal point has initialized. If the focal point is running a
satellite system automation, make sure the satellite has
initialized.
System programmer response: None.
Classes: None.
AOF851I
INVALID SYSPLEX DEFINITION 'data'. ENTRY IGNORED
Explanation: You have something coded on the
ENVIRON SYSPLEX definition in your automation
control file that system automation does not
understand.
The variable data shows what is not being
recognized.
System action: The entry is ignored. If the entry was
for something important (such as the group name) this
may have other consequences.
88
System Automation for z/OS Messages and Codes:
AOF852I • AOF869I
Operator response: Inform your system programmer.
System programmer response: If the automation
control file was built with the customization dialogs,
contact your IBM Support Center.
The variable entry shows the entry field associated
with the line of automation policy data being
processed.
Classes: None.
The variable type shows the type field associated
with the line of automation policy data being
processed.
AOF852I
The variable warning shows the potential problem
that has been found with the data.
SYSPLEX GROUP ENTRY MISSING SYSPLEX WILL NOT BE SUPPORTED
Explanation:
System action:
Operator response:
System action: If the error is an incorrect data value it
will be ignored, and it will not be reflected in the
runtime parameters.
Operator response: Inform your system programmer.
System programmer response:
System programmer response: Resolve the data
inconsistency.
Classes: 40 46
Classes: 40 46.
AOF860I
instruction FOR entry type REJECTED "reason"
AOF868I
WARNING: THERE ARE NO JES
SUBSYSTEMS DEFINED
Explanation: An automation policy processing
instruction could not be completed, and was rejected
for the reason given.
Explanation: The automation cannot work correctly
without a JES subsystem, and system automation did
not define one.
Note: ASSERT, MODIFY, and RETRACT are
instructions used by the system automation automation
policy processing to add, change, or delete data in the
currently active policy definitions. The system
automation policy has converted your request into one
or more of these instructions.
System action: Processing continues. Some automation
functions may not work properly.
The variable instruction shows the action being
attempted for the entry-type pair. It can be ASSERT,
MODIFY, or RETRACT.
The variable entry shows the entry field associated
with the line of automation policy data being
processed.
The variable type shows the type field associated
with the line of automation policy data being
processed.
The variable reason shows the reason why the action
on the entry-type pair was rejected.
System action: The entry-type pair and associated
data is ignored.
Operator response: Fix the problem if you can, using
the information given in the message, or inform your
system programmer.
System programmer response: Fix the problem using
the information given in the message.
Classes: 40 46.
AOF867I
WARNING: entry type - "warning"
Explanation: System automation has detected an
inconsistency in the data that it has been given.
Operator response: Inform your system programmer.
System programmer response: Determine whether JES
was defined outside of system automation. If not, and
you want your system to run with JES, you must
define it.
Classes: 40 46.
AOF869I
nn ERRORS ENCOUNTERED
PROCESSING MEMBER member
Explanation: This message indicates how many
inconsistencies were found by system automation
during the processing of this automation control file.
The variable nn shows the number of
inconsistencies encountered during the checking of
member.
The variable member shows the name of the
automation control file member being processed.
System action: Processing continues unless the
advanced automation option AOFACFINIT is set to 0.
Operator response: Review the NetView log for
additional information given in one or more of the
following messages: AOF206I, AOF701A, AOF784I,
AOF785I, AOF860I, AOF867I, AOF868I, AOF871I, and
fix the problem if you can, or inform your system
programmer.
System programmer response: Review the NetView
log for additional information given in one or more of
the following messages: AOF206I, AOF701A, AOF784I,
Chapter 2. Messages AOF000I to AOF969I
89
AOF871I • AOF895I
AOF785I, AOF860I, AOF867I, AOF868I, AOF871I and
fix the problem.
Operator response: None.
System programmer response: None.
Classes: 40.
AOF871I
Classes: None.
Classes:
time: LESS THAN n type entry ARE
DEFINED - AUTOMATION WILL
CONTINUE WITH DEGRADED
PERFORMANCE
AOF893I
Explanation: There are not enough definitions
available in the automation control file for the entry
type mentioned in the message.
ENTERPRISE MONITORING IS NOT
ENABLED. reason
Explanation: Enterprise monitoring is not enabled.
The variable reason gives more detail about the
cause of the error.
The variable time shows the time when this message
was generated.
System action: None.
Operator response: If you do not want to use
enterprise monitoring then no action is required.
Otherwise, contact your system programmer.
The variable type shows the type specified in the
automation control file.
The variable entry shows the entry specified in the
automation control file.
System programmer response: Use the reason text to
help determining the problem.
System action: Processing continues with degraded
performance.
Classes: None.
Operator response: None.
System programmer response: Define the automation
control file entries through the system automation
customization dialogs.
|
|
|
AOF894I
Classes: None.
Explanation: SDF detected a node name that is
defined more than once on the same hierarchy level in
a tree. SDF supports identical node names on the
lowest hierarchy level only.
Explanation: The command was issued in the form of
a route command by operator operator_ID and
executed in domain domain_ID.
|
|
|
|
|
|
|
|
|
The variable domain_ID shows the of the domain
that the command was executed in.
|
|
System action: The node name is ignored. This
includes all sub-nodes.
The variable operator_ID shows the ID of the
operator who issued the route command.
|
Operator response: None.
|
|
|
|
System programmer response: Correct the definition.
Restart SDF when the messages was produced during
SDF initialization. Otherwise, re-issue the SDF
command that produced the message.
|
Classes: None.
|
|
|
AOF895I
|
|
|
|
|
|
|
Explanation: SDF detected identical node names on
different hierarchy levels of a tree. SDF supports
identical node names on the lowest hierarchy level
only.
AOF890I
THE COMMAND WILL BE ROUTED
TO domain_ID USING THE DEFAULT
OPERATOR ID operator_ID
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
AOF891I
SSV ERROR OBTAINING SYSPLEX
item
Explanation: This message indicates a non-zero return
code has been returned from NetView when SA z/OS
was trying to query a NetView CGLOBAL value. This
is likely to have been caused by NetView and RODM
being out of synchronization.
The variable item shows what SA z/OS was trying
to resolve when the error occurred.
System action: The query is rejected by NetView and
the SA z/OS request abends.
90
System Automation for z/OS Messages and Codes:
DUPLICATE NAME ON SAME
HIERARCHY LEVEL FOUND IN
MEMBER member: name
The variable member shows the name of the
DSIPARM member that contains the duplicate
name.
The variable name shows the name that occurs more
than once.
DUPLICATE NAME IN TREE
HIERARCHY FOUND IN MEMBER
member: name
The variable member shows the name of the
DSIPARM member that contains the duplicate
name.
AOF896I • AOF900I
|
|
The variable name shows the name that occurs more
than once.
|
|
AOF898I
|
|
|
|
|
|
|
|
Explanation: An MVS command was sent using MVS
ROUTE command to one or all systems in the sysplex.
The indicated system rejected the command for security
reasons. MVS commands are essential for most sysplex
automation functions, since SA z/OS may run in an
SAplex which can be smaller than a sysplex.
|
|
|
|
|
|
System action: All sysplex automation functions using
MVS ROUTE command have been disabled, in
particular the following commands; INGCF, INGCFL,
INGPLEX (CDS, CONSOLE, SDUMP, SLIP, SYSTEM)
and the following recovery functions: local page
dataset, log, long-running enqueue.
AOF_AAO_SDFCvar.0 n
|
Operator response: None.
AOF_AAO_SDFCvar.n xxx [xxx...]
|
|
|
|
|
System programmer response: If one of the
commands or recovery functions above is required for
your automation ensure that all systems in the sysplex
accept MVS commands, especially the ROUTE
command.
|
Classes: None.
|
|
AOF899I
|
|
|
|
|
|
Explanation: System Automation detected that one or
more systems rejected the MVS ROUTE command. For
this reason, all sysplex automation functions have been
disabled.
|
|
System action: The function is terminated
immediately.
|
Operator response: None.
|
|
|
|
|
System programmer response: Search the netlog for
message AOF898I to determine which system rejected
the ROUTE command. If the indicated function is
required for your automation ensure that all systems in
the sysplex accept the MVS ROUTE command.
|
Classes: None.
|
|
System action: The node name is ignored. This
includes all sub-nodes.
|
Operator response: None.
|
|
|
|
System programmer response: Correct the definition.
Restart SDF when the message was produced during
SDF initialization. Otherwise, re-issue the SDF
command that produced the message.
|
Classes: None.
|
|
AOF896I
|
|
|
|
Explanation: SDF found a variable in a tree definition
but no common global variables of type;
|
|
that define the substitution values.
|
|
System action: The node name is ignored. This
includes all sub-nodes.
|
Operator response: None.
|
|
|
|
System programmer response: Correct the definition.
Restart SDF when the message was produced during
SDF initialization. Otherwise, re-issue the SDF
command that produced the message.
|
Classes: None.
|
|
|
AOF897I
|
|
|
|
|
|
|
|
|
|
Explanation: SDF detected identical node names on
the first and only sub-level of a tree. This is not
supported because the root name of a tree must always
be unique. Since SDF traverses the tree from top to
bottom and left to right it would never find the second
identical node name.
|
System action: The node name is ignored.
|
Operator response: None.
|
|
|
|
System programmer response: Correct the definition.
Restart SDF when the message was produced during
SDF initialization. Otherwise, re-issue the SDF
command that produced the message.
|
Classes: None.
NO SUBSTITUTION VALUES FOUND
FOR var.
The variable var shows the name of the variable.
INVALID LEVEL OF NON-UNIQUE
COMPONENT IN MEMBER member:
name
The variable member shows the name of the
DSIPARM member that contains the node name in
error.
The variable name shows the node name in error.
SYSTEM sysname REJECTED
COMMAND "cmd".
The variable sysname shows the name of the system.
The variable cmd shows the name of the system.
SYSPLEX AUTOMATION FUNCTION
clist DISABLED.
The variable clist shows the name of clist that has
been disabled.
AOF900I
AT LEAST ONE STRUCTURE IS STILL
ALLOCATED IN THE CF cfname
Explanation: The process was started disconnecting
the coupling facility cfname from its connected systems.
However, at least one structure that is still allocated
was detected by the DRAIN function. Or, one allocated
structure that has a connection to an application was
detected by the FORCE function.
System action: Processing terminates.
Operator response: Check the allocated structures of
Chapter 2. Messages AOF000I to AOF969I
91
AOF901I • AOF906I
the coupling facility. Rebuild the structures to another
coupling facility if possible before issuing the command
again.
System programmer response: None.
Classes: 40, 43.
Modules: INGRX912, INGRX913.
AOF904I
A CF/CDS PROCESS IS STILL
RUNNING. ACTION action name IS
REJECTED
Explanation: While the AUTXCF task is busy, new
actions are rejected. This avoids performance
degradation due to multiple rebuild processes, or
unpredictable results due to multiple executions of an
action.
PATH chpid FROM SYSTEM TO CF
cf_name COULD NOT BE SET TO status
The variable action shows the CF or CDS action that
is being performed.
Explanation: The program received an unexpected
message in response to the CF CHP command setting a
sender path from a connected system to a coupling
facility to either OFFLINE or ONLINE.
The variable name shows the name of the CF or the
CDS.
AOF901I
System action: Processing terminates.
Operator response: None.
System programmer response: Check the netlog for
related messages to determine the cause of the error.
Classes: 40 43.
Modules: INGRX913, INGRX915.
AOF902I
DRAINING THE CF cf_name DID NOT
COMPLETE SUCCESSFULLY
System action: Processing terminates.
Operator response: Retry the action later.
System programmer response: None.
Modules: INGRVX3D, INGRVX90.
AOF905I
action OF STRUCTURE/CF strname
FAILED
Explanation: The program received an unexpected
message in response to a SETXCF command. The action
that is related to the structure or coupling facility did
not complete successfully.
Explanation: The program received an unexpected
message in response to the CF CHP command setting a
sender path from a connected system to a coupling
facility to OFFLINE.
System action: Processing stops except when all the
structures of a coupling facility are being rebuilt one by
one. In this case processing continues with the next
structure.
System action: Processing terminates.
Operator response: None.
Operator response: None.
System programmer response: Check the netlog for
related messages to determine the cause of the error.
System programmer response: Check the netlog for
related messages to determine the cause of the error.
Classes: 40 43.
Modules: INGRX913.
AOF903I
EITHER THE SPECIFIED CF IS NOT
DEFINED OR NO CF HAS BEEN
DEFINED
Explanation: Either the command was executed in a
sysplex that does not use any coupling facility or the
name of the coupling facility is not known in the
sysplex.
System action: Processing terminates.
Operator response: Specify a valid coupling facility
name.
System programmer response: None.
Modules: AOFRVX2A, AOFRVX22, AOFRX210,
INGRX900, INGRX901.
92
System Automation for z/OS Messages and Codes:
Classes: 40, 43.
AOF906I
TIME-OUT OCCURRED ON
COMMAND command
Explanation: The command did not respond in time.
Reasons could be:
v XCF commands:
These can time out because they are processed by
one single task.
v Commands that implement the Health Checker
function:
These are INGRX352 and INGRVX35. They can time
out because there is a problem with task AOFHC, for
example, the task may not be active.
System action: Processing terminates except when all
structures of a coupling facility are being rebuilt. In this
case processing continues with the next structure.
Operator response: Before executing the action again,
check the netlog and the system activities to determine
the cause of the time-out.
AOF907I • AOF913I
System programmer response: None.
AOF910I
Classes: 40, 43.
AOF907I
STRUCTURE strname HAS
CONNECTIONS OTHER THAN
FAILED-PERSISTENT
Explanation: The automation detected at least one
connection to the structure that does not have the
status FAILED-PERSISTENT. Because XCF does not
allow for the deletion of such a structure, the action is
rejected.
System action: Processing terminates.
Operator response: Make sure that the structure has
either no connections, or only FAILED-PERSISTENT
connections before you force the deletion of the
structure again.
System programmer response: None.
Classes: 40 43.
Modules: INGRX911.
POLICY policy COULD NOT BE
ACTIVATED
Explanation: During verification of the policy policy
the automation detected that the policy does no longer
fulfill the criteria to become active. The automation
rejected the command to make the policy the active
policy.
System action: Processing terminates.
Operator response: Refresh the screen. Then retry the
operation.
System programmer response: None.
Classes: None.
Module: INGRVX90
AOF911I
POLICY CHANGE(S) PENDING
Explanation: After the new policy has become active,
the automation detected that one or more structures
have a policy change pending.
System action: The command completed successfully.
AOF908I
START OF AUTOTASK taskname
FAILED. RC = rc
Explanation: Any action that is related to a sysplex
resource, for example, a coupling facility, is performed
on a dedicated autotask. If the task is not active, it is
started via the AUTOTASK command. However, the
command failed with the return code rc.
Operator response: Use the command INGCF STR to
find out what structures have a pending status. Rebuild
each of these structures to remove its pending status.
System programmer response: None.
Classes: None.
Module: INGRVX90
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: Analyze the return
code and correct the error. Refer to the description of
the AUTOTASK command help in the online help
(HELP AUTOTASK).
Classes: 40 44.
Module: INGRVX90
AOF909I
FUNCTION function REJECTED DUE
TO A CF STATUS CHANGE
Explanation: You requested the function function to be
performed. Meanwhile the status of the affected
coupling facility has changed. The function is rejected
because the current status of the coupling facility does
not match the status required by the function.
System action: The program terminates.
Operator response: Press the refresh key to display
the latest status.
System programmer response: None.
Classes: None.
Module: INGRVX90
AOF912I
XCF COMMAND 'command' IS NOT
SUPPORTED BY THIS SYSTEM.
Explanation: The designated system does not support
the indicated XCF command. START/STOP
MAINTMODE requires z/OS version 1.9 or later.
System action: Processing stops.
Operator response: Reenter the command on a system
that supports the command.
System programmer response: None
Classes: None.
AOF913I
itemname VALUE OF CDS TYPE type
HAS BEEN CHANGED FROM oldvalue
TO newvalue
Explanation: The automation detected a situation
where the size of a couple data set must be increased to
prevent an outage situation. The value of the item
itemname has been increased as stated.
System action: Processing continues.
Operator response: None.
System programmer response: Determine the reason
for the change and take action accordingly.
Chapter 2. Messages AOF000I to AOF969I
93
AOF914E • AOF916E
Classes: 40, 43.
couple data sets, follow the comment for
reason codes 20 through 29.
Module: INGRX711
AOF914E
RECOVERY OF THE CDS TYPE type
FAILED. RSN= reason
Explanation: The recovery of the couple data set of
type type failed.
Reason Explanation
19
Follow the description of reason codes 20
through 2B.
20-2B
These codes relate to the process of extending
the current couple data set(s) of type type. The
codes reflect the progress of the process.
Determine the current couple data sets and
complete the process manually. Depending on
the progress, you can determine the
appropriate control card information either
using the command INGPLEX CDS TYPE=type
(reason > 24) or running the XCF utility
against the temporary couple data set (reason
> 21). If reason code 21 is issued, check the
system log for an IXG257I or IXG261E
message. If you find them, extend the couple
data set(s) by increasing the DSEXTENT value
by 1 or when not available by setting the
value to 1. Otherwise and for reason code 20
determine the originator of the request to get
the new item values.
10
The command ‘SETXCF COUPLE,PSWITCH’
failed.
19
The LOGR couple data set(s) could not be
extended.
20
The control card information of the primary
couple data set could not be obtained.
21
A temporary couple data set with the new
item values could not be formatted.
22
The temporary couple data set could not be
allocated.
23
The old alternate couple data set could not be
deleted.
Classes: 40, 43.
24
The temporary couple data set could not be
made the primary couple data set.
Module: INGRX305, INGRX711, INGRX720
25
The old primary couple data set could not be
deleted.
AOF915E
26
The old primary couple data set could not be
reformatted.
27
The reformatted old primary couple data set
could not be allocated as the new alternate
couple data set.
Explanation: The recovery of couple data sets of type
type has been triggered. However, the automation could
not complete the recovery because no spare volumes
have been defined where a couple data set could be
allocated.
28
The reformatted old primary couple data set
could not be made the new primary couple
data set.
29
The temporary couple data set could not be
deleted.
2A
The old alternate couple data set could not be
reformatted.
2B
Either the reformatted old alternate couple
data set or a new spare couple data set could
not be allocated as the alternate couple data
set.
NO SPARE VOLUMES DEFINED FOR
CDS TYPE type.
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: Review the netlog and
the system log. If the message has not been issued
during the initialization of the automation, complete
the recovery manually. To prevent any future
occurrence of this message, modify the customization
by adding one or more spare volumes for the named
type of couple data sets. Then recycle NetView.
Classes: 40, 43.
Module: INGRX720
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: Check the netlog and
the system log for related system messages. Determine
the reason and take action accordingly.
Reason Explanation
10
94
Check the system log to determine the reason
why XCF did not switch the couple data sets.
If the message was issued while extending the
System Automation for z/OS Messages and Codes:
AOF916E
NO MORE SPARE VOLUMES
AVAILABLE FOR CDS type type.
Explanation: The recovery of couple data sets of type
type has been triggered. However, the automation could
not complete the recovery because all predefined spare
volumes are either already in use, or they are unusable.
System action: Processing terminates.
Operator response: Inform your system programmer.
AOF917E • AOF922I
System programmer response: Review the netlog and
the system log and complete the recovery manually.
Then check the predefined spare volumes of the named
type of couple data sets. When less than three volumes
have been defined and the corresponding couple data
sets are allocated to XCF add at least one more spare
volume and then recycle NetView. Otherwise,
determine the reason why the spare couple data sets or
volumes could not be used. One reason can be that
there is not enough continuous space on the volume.
Operator response: Press the REFRESH key and retry
the function if possible.
Classes: 40, 43.
Explanation: The program set up the commands MVS
DISPLAY XCF,PATHIN,DEVICE=ALL and MVS
DISPLAY XCF, PATHOUT,DEVICE=ALL. However, the
message AOF920I was returned.
Module: INGRX720
AOF917E
THE HIGH-LEVEL QUALIFIER HAS
NOT BEEN DEFINED.
Explanation: The recovery of couple data sets has
been triggered. However, the automation could not
complete the recovery because the high-level qualifier
that was used to create a spare couple data set has not
been defined.
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: Review the netlog and
the system log and complete the recovery manually. To
prevent any future occurrence of this message, disable
the recovery for couple data sets. Or, modify the
customization by defining the high-level qualifier and
then recycle NetView.
System programmer response: None.
Classes: None.
Module: INGRX914
AOF920I
NO SIGNALLING PATHS MATCH
THE SPECIFIED CRITERIA criteria
The variable criteria shows the path type (either
PATHIN or PATHOUT).
System action: Processing terminates.
Operator response: None.
System programmer response: None.
AOF921I
CONSOLE console IS INACTIVE
Explanation: The MVS command D
R,LIST,T,CN=console was issued. However, no data was
returned because the console is INACTIVE. Therefore,
no requests can be displayed.
System action: Processing terminates.
Operator response: None.
Classes: 40, 43.
System programmer response: None.
Module: INGRX720
Classes: None.
Module: AOFRVX41
AOF918I
THE AUTOMATION IS GOING TO
SWITCH THE COUPLE DATA SETS OF
type
Explanation: The automation is going to switch the
couple data sets of the specified type.
The variable type shows the type of the couple data
sets that are being switched.
System action: Processing continues.
Operator response: None.
Classes: 40, 43.
Module: INGRX720
AOF919I
function DETECTED STATUS status FOR
CF cfname
Explanation: The function function detected a status
change of the coupling facility inhibiting the function
from further processing.
System action: Processing terminates.
AOF922I
REBUILD OR FORCE OF STRUCTURE
structure_name NOT ALLOWED
Explanation: An attempt was made to REBUILD or
FORCE a coupling facilitiy structure. However, the
REBUILD or FORCE command is not supported for
this structure. This can have one of the following
reasons:
v The structure has no connections allocated and does
not support system-managed rebuild.
v The structure has no active connections allocated and
does not support system-managed rebuild.
v One or more of the structure’s active connections
was created with REBUILD=NO and
system-managed rebuild is not supported.
v No alternate coupling facility is defined, available or
has sufficient space.
The variable structure_name shows the name of the
structure that the REBUILD or FORCE command is
not supported for.
System action: Processing terminates.
Chapter 2. Messages AOF000I to AOF969I
95
AOF923I • AOF925I
Operator response: None.
System programmer response: None.
AOF923I
NO ACTIVE TARGET SYSTEM
FOUND ON TARGET HARDWARE
target (LU=LUNAME)
Explanation: The operator issued the command
GETSPCFP luname. Either the target hardware has not
been initialized yet, or the LU name of the Support
Element has changed.
System action: Processing terminates.
Operator response: Use the processor operations
command ISQXDST to verify that at least one target
system is initialized. If not, issue the command ISQXIII
target where target is one of the target system names in
the list. When the command completes successfully,
retry the GETSPCFP command.
System programmer response: If the luname has
changed, correct the name in the processor operations
control file and restart processor operations.
Classes: 40, 43.
AOF924A
AUTOMATION OF MESSAGE ixc_msg
TERMINATED. REASON: reason[,
{PROCESSOR OPERATIONS|BCPII}
COMMAND RC=rc]. SYSID: sysname.
Explanation: The variable ixc_msg shows the message
that triggered the automation. It can have the following
values and explanations:
IXC102A
XCF is removing a system from the sysplex.
IXC402D
XCF determined that a system in the sysplex
appears to be inoperative.
XCF waits for the reply to proceed. However, the reply
could not be automated.
v The variable reason shows the reason code that was
issued. It can have the following values:
10 The message being automated has not been
formatted as expected. The message identifier
could not be located.
11 A command was issued to the MVS system that
reported that a system left the sysplex. A
timeout occurred while waiting for a reply to
this command.
12 The proxy resource name for the system leaving
the sysplex could not be determined.
13 The Support Element of the system leaving the
sysplex cannot be reached.
14 The target system name of the ISQ900I message
could not be obtained or the target system that
sent the ISQ900I message is not initialized to
processor operations.
96
System Automation for z/OS Messages and Codes:
15 The replyid for the message being automated
could not be determined.
16 The system name could not be located in the
automated message.
17 The message that triggered the automation could
not be retrieved for automation.
18 The automation requirements for the system
leaving the sysplex could not be determined.
19 An error occurred while checking if the message
was still outstanding.
30 A processor operations command failed. Refer to
the appropriate command description.
31 A timeout occurred while waiting for the
response of the Processor Management
command.
32 The reply to the outstanding WTOR could not
be sent.
33 An error occurred while determining the status
of the local sysplex.
v The variable rc shows the value of the return code.
System action: Processing terminates.
Operator response: Depending on which message
triggered the automation, respond as follows:
IXC102A
Complete the shutdown of the system leaving
the sysplex. Then reply DOWN to the
outstanding WTOR.
IXC402D
Either reply 'INTERVAL=sssss' (range 0 to
86400) to give the system the specified interval
to become operative again. Or, complete the
shutdown of the system leaving the sysplex.
Then reply DOWN to the outstanding WTOR.
System programmer response: Correct the problem. If
reason code 11 was issued, no action is required.
Module: AOFRX700, AOFRX701, AOFRX702,
INGRX705, INGRX706
Classes: 40, 43
TEC: YES
AOF925I
AUTOMATION OF MESSAGE ixc_msg
FOR system COMPLETED
SUCCESSFULLY
Explanation: The automation of message IXC102A or
IXC402D for system system ompleted successfully. The
system is no longer part of the sysplex.
System action: None.
Operator response: None.
System programmer response: None.
Module: AOFRX700, AOFRX701, AOFRX702,
INGRX705, INGRX706.
Classes: None.
AOF926I • AOF929I
TEC: NO
AOF926I
ERROR error DETECTED DURING
AUTOMATION OF MESSAGE ixc_msg
Explanation: The routine responsible for the
automation of messages IXC102A and IXC402D found
an error.
v
The variable error shows the error condition. The
following error conditions can occur:
10 The message is neither the IXC102A nor the
IXC402D message.
11 The same message is being processed by another
task.
12 Two or more commands were defined in the
customization dialogs for message IXC102A.
However, only one ISQCCMD can be issued.
13 The command defined for IXC102A message is
not an ISQCCMD command.
14 The reply is no longer outstanding.
15 Incorrect call of a subsequent clist.
30 Using the supplied or default command, an
attempt was made to deactivate the system
leaving the sysplex. Another attempt will be
made using the default command.
System action: Processing terminates for conditions
10, 11, 14, and 15. For conditions 12, 13 and 30
processing continues using the default processor
management command SYSRESET CLEAR.
Operator response: None.
System programmer response: If error conditions 12,
13 or 30 occurred, correct the definitions and reload the
automation control file.
Module: AOFRX700, AOFRX701, AOFRX702,
INGRX705, INGRX706.
possible, requeue console buffers to the system log (K
Q,L=conname). If possible, increase MLIM. Cancel jobs
buffering messages or replies. After message
IEA406I/IEA232I is issued, check whether the current
CONSOLxx definitions may need to be adjusted to
avoid future buffer shortages.
Module: INGRX730
Classes: 40, 43.
AOF928I
SYSPLEX sn bt RECOVERY INCREASES
THE in VALUE TO nv
Explanation: The automation has detected a shortage
of message or reply buffers. As a recovery result, the
limit value is increased to avoid further buffer
shortages. The changed value affects all active members
in a sysplex, because the modified limit has sysplex
scope.
The variable sn specifies the name of the sysplex.
The variable bt WTOR: write to operator with reply
message buffers.
The variable in RMAX specifies the maximum
buffer limit of write to operator with reply
messages. If the system runs in SYSPLEX=LOCAL
mode or the number of systems in the sysplex is
greater than eight, the RMAX value is set to 9999.
Otherwise it is not changed.
The variable nv shows a numeric number,
representing the new limit value that is going to be
active.
System action: Processing continues.
Operator response: Inform your system programmer.
Classes: None.
System programmer response: This message may
indicate that the current RMAX value of CONSOLxx
member needs to be adjusted.
TEC: NO
Classes: 40, 43.
Module: INGRX730
AOF927E
WTOR|WTOR BUFFER SHORTAGE
COULD NOT BE RESOLVED
Explanation: The sysplex automation to recover from
a WTO or WTOR buffer shortage did not complete
successfully. One or multiple recovery stages signalled
an error. This is a transient status of the recovery. The
message IEA406I/IEA232I for WTO/WTOR buffer
shortage relief may indicate that the buffer shortage has
been resolved.
System action: Processing continues.
Operator response: Check the system log for message
IEA406I/IEA232I indicating a buffer shortage relief. If
the message could not be found, perform manual
recovery actions.
System programmer response: Search the system log
for message IEE889I issued by the operating system
internally. Identify the buffering consoles or jobs. If
AOF929I
SYSPLEX sn bt RECOVERY SETS st ON
SYSTEM sys
Explanation: The automation has detected a shortage
of message or reply buffers. As a recovery result, a
limit value or a console setting is changed to avoid
further buffer shortages. The changed value or console
setting affect the named system in the sysplex.
The variable sn specifies the name of the sysplex.
The variable bt WTOR: write to operator with reply
message buffers.
The variable st shows the string representing the
command that was issued to recover from the buffer
shortage. The limit values or console settings stay in
effect until they are changed manually. In case of an
extended recovery situation, this message may be is
Chapter 2. Messages AOF000I to AOF969I
97
AOF930I • AOF935I
issued multiple times showing commands
increasing MLIM or RLIM values.
The variable sys specifies the name of the system.
System action: Processing continues.
Operator response: If this message is displayed
frequently, inform your system programmer.
System programmer response: Multiple occurrence of
this message may indicate that the CONSOLxx member
specified limits or console definitions need to be
adjusted.
Classes: 40, 43.
Module: INGRX730
AOF930I
HARDWARE STATUS CHANGE
DETECTED
Classes: None.
Module: INGRX301
AOF932I
BOTH NAME AND VOLUME ARE
REQUIRED.
Explanation: The user has only specified a user couple
data set name or a volume.
System action: Processing stops.
Operator response: Specify both a data set name and
a volume.
System programmer response: None.
Classes: None.
Module: INGRX301
Explanation: The hardware monitoring program
detected a status change of one or more hardware
components defined during customization.
AOF933I
ACTION CODE IS NOT SUPPORTED.
System action: Processing continues.
System action: Processing stops.
Operator response: None.
System programmer response: None.
Operator response: See the panel help for the reason.
Use a valid action code.
Classes: None.
System programmer response: None.
Module: INGRX051
Classes: None.
Explanation: The action code is not supported for this
entry for some program-related reason.
Module: INGRX300, INGRX904
AOF931I
VERIFICATION OF USER-DEFINED
CDS FAILED. RSN= reason DSN=dsname
Explanation:
v The variable reason shows the value of the reason
code. The following reason codes can occur:
AOF934I
POLICY policy HAS BEEN STARTED.
Explanation: A ‘SETXCF START,POLICY’ command
has been issued for the policy policy.
System action: Processing continues.
1
The automation environment has not yet
been initialized.
2
The data set name conflicts with the naming
convention of the automation when creating
a new couple data set.
System programmer response: None.
4
The specified data set is not defined.
Module: INGRVX3A
8
The specified data set is not available.
12
The specified data set is already allocated.
16
An unexpected error occurred.
20
The DYNALLOC macro failed.
24
The specified volume does not match the
actual volume.
v The variable dsname shows the name of the data set.
System action: Processing terminates.
Operator response: Make sure that the name of the
data set and volume (if specified) are correct.
System programmer response: Make sure that the
data set is defined and available.
98
System Automation for z/OS Messages and Codes:
Operator response: Check that the policy becomes the
active policy.
Classes: None.
AOF935I
ENTER THE COUPLE DATA SET AND
VOLUME.
Explanation: The automation is waiting for a
user-defined couple data set to be specified.
System action: None.
Operator response: Enter the required information.
System programmer response: None.
Classes: None.
Module: INGRX301
AOF936E • AOF942I
AOF936E
START OF POLICY policy FAILED.
Explanation: A ‘'SETXCF START,POLICY’ command
has been issued for the policy policy. The command
failed.
System action: Processing stops.
Operator response: Review the netlog.
System programmer response: None.
Classes: None.
AOF939I
THERE IS NO ACTIVE POLICY.
Explanation: The automation detected that no policy
is active at the moment.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: None.
Module: INGRX311, INGRX313, INGRX314
Module: INGRX301
AOF940I
AOF937E
SOME PENDING STRUCTURES
CANNOT BE REBUILT AND REMAIN
PENDING.
Explanation: The automation function responsible for
releasing the 'POLICY CHANGE PENDING' status of
the structures detected that one or more structures
remain in this status.
System action: Processing continues.
Operator response: Use the command 'D
XCF,STR,STATUS=POLICYCHANGE' to list the
structures whose status is pending. Determine the
reason why these structures remain in the status.
Manually perform the necessary actions for releasing
the status.
System programmer response: None.
Classes: None.
Module: INGRX919
Explanation: The selected function is not enabled for
automation.
System action: Processing terminates.
Operator response: Enable the function by setting the
RECOVERY flag of one of the named resources to 'Y'.
Then, retry the function.
System programmer response: If the function should
be enabled by default, update the customization values.
Classes: None.
AOF941I
CFRM COUPLE DATA SET IS NOT
AVAILABLE.
Explanation: The CFRM active policy could not be
read because the couple data set supporting
TYPE(CFRM) is not accessible from this system.
System action: Processing terminates.
TEC: NO
AOF938E
resource(s) AUTOMATION IS/ARE NOT
ENABLED.
DDNAME ddname IS PENDING.
Explanation: An automation function could not
complete successfully because a required data set is not
available.
The variable ddname shows the name of the data set
that is not available.
System action: Processing stops.
Operator response: Notify your system programmer.
System programmer response: Add the ddname to
the NetView startup procedure. To prevent a NetView
recycle, allocate the data set dynamically using the
ddname above.
Operator response: Issue the request from a system
with access to a CFRM couple data set.
System programmer response: None.
Classes: None.
Module: INGRVX9Q
AOF942I
NO POLICIES DEFINED.
Explanation: There are no policies defined for the
selected couple data set type.
System action: None.
Operator response: Inform your system programmer.
Classes: None.
System programmer response: Define policies as
necessary.
Module: INGRVX20, INGRX200
Classes: None.
TEC: NO
Module: INGRX311, INGRX313, INGRX314
Chapter 2. Messages AOF000I to AOF969I
99
AOF943I • AOF949I
AOF943I
NO LOG STREAMS OR STRUCTURES
DEFINED.
Explanation: There are no log streams or structures
defined in the LOGR couple data set.
Classes: None.
Module: INGRVX9P
AOF947I
System action: None.
Operator response: Inform your system programmer.
System programmer response: Define log streams and
structures as necessary.
Classes: None.
Module: INGRX312
AOF944I
CDS TYPE cdstype IS NOT ENABLED
ON SYSTEM system.
Explanation: The couple data set type cannot be
displayed because it is not enabled on the target
system.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
action OF STRUCTURE structure IS NOT
SUPPORTED.
Explanation: The automation detected that the action
selected for the structure is either not supported or
currently unavailable.
The variable action shows the action to be
performed.
The variable structure shows the name of the
structure.
In case of SYSTEM-MANAGED actions the cause of the
problem could be that the CFRM couple data set is not
formatted properly.
System action: The action is not performed.
Operator response: None.
System programmer response: None.
Module: INGRX904
Classes: None.
TEC: NO
Module: INGRX310
AOF948I
AOF945I
CDS TYPE cdstype IS NOT
ACCESSIBLE ON SYSTEM system.
Explanation: The couple data set type cannot be
displayed because it is not accessible on the target
system.
System action: None.
FUNCTION NO LONGER
SUPPORTED.
Explanation: Due to some changes in a new version of
this product this function has either been replaced or
deleted.
System action: Processing terminates.
Operator response: None.
Operator response: If the function was replaced, use
the new function.
System programmer response: None.
System programmer response: None.
Classes: None.
Classes: None.
Module: INGRX310
Module: INGRVX90
AOF946I
AOF949I
SOME SENDER PATH INFORMATION
COULD NOT BE DETERMINED FOR
cfname.
Explanation: Currently not all systems in the sysplex
have access to the coupling facility cfname. However,
the automation cannot determine the sender paths of
some or all of those systems.
System action: Processing continues.
Operator response: If the local system does not show
the control unit of the coupling facility, try the
command from a system that shows the information
when you enter the MVS command 'D
CF,CFNM=cfname'.
System programmer response: None.
100
System Automation for z/OS Messages and Codes:
NO DUMP DATA SET AVAILABLE
FOR JOB jobname
Explanation: The automation tries to take a dump
before the job is canceled. Neither system dump data
sets nor automatic allocated dump data sets were
available.
System action: Processing continues.
Operator response: Inform your system programmer.
System programmer response: To fix the error do one
of the following:
v Add more system dump data sets or volumes for
automatically allocated dump data sets
AOF950I • AOF953E
v Clear full dump data sets to prevent further
occurrences of this message.
AOF952I
Module: INGRX741
Classes: 40
TEC: NO
AOF950I
JOB jobname ON sysname HOLDS AN
ENQ FOR nnn SECONDS ON
RESOURCE resource
Explanation: The automation found a long blocking
ENQ on the resource held by the specified job. The
policy defined during customization does not allow the
cancelation of the job to free the resource.
The variable jobname shows the name of the job.
The variable sysname shows the system where the
job is running.
Explanation: The automation found an auxiliary
storage shortage. The system issued a message
indicating the job had rapidly increasing storage
requests. The job is being canceled based on policy
definitions.
The variable jobname shows the name of the job.
System action: The job is canceled with the MVS
CANCEL command.
Operator response: None.
System programmer response: None.
Module: INGRX742
Classes: 40
The variable nnn shows the waiting time in seconds.
A value of 999 is the maximum waiting time shown.
TEC: NO
The variable resource shows the name of the
resource where the ENQ was found.
AOF953E
System action: Processing continues.
Operator response: Inform your system programmer.
System programmer response: If the waiting time is
feasible, remove the resource entry from the policy or
increase the time if applicable. Otherwise allow the
cancelation of the job if necessary.
Module: INGRX741
The variable reason shows the reason code. It can
have the following values:
Reason Description
4
The recovery was enabled, but neither spare
volumes for dynamically allocated page data
sets nor preallocated page data sets were
defined.
8
The spare volumes for dynamically allocated
page data sets and the predefined local page
data sets are used up.
12
The spare volumes for dynamically allocated
page data sets and the predefined local page
data sets are used up. Some of them have been
marked unusable because the system rejected
the data sets when the automation tried to
make them available.
16
The IDCAMS service failed for the dynamic
allocation of a page data set. Check the netlog
for details.
20
The PAGTOTL value defined in IEASYSxx
member used during IPL does not allow to
add more local page data sets.
24
The system issued a message indicating a
problem when the automation tried to make a
local page data set available.
TEC: NO
DUE TO A LONG ENQ DETECTION
THE JOB jobname ON sysname IS BEING
CANCELLED.
Explanation: The automation detected a long blocking
ENQ held by the specified job. The job is being
canceled based on policy definitions.
The variable jobname shows the name of the job.
The variable sysname shows the system where the
job is running.
System action: The job is canceled with the MVS
CANCEL command.
Operator response: None.
System programmer response: None.
Module: INGRX741
Classes: 40
TEC: NO
RECOVERY OF AUXILIARY STORAGE
SHORTAGE COULD NOT COMPLETE
SUCCESSFULLY. REASON=reason
Explanation: The automation could not recover an
auxiliary storage shortage.
Classes: 40, 43.
AOF951I
DUE TO A AUXILIARY STORAGE
SHORTAGE DETECTION THE JOB
jobname IS BEING CANCELLED
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: If reason codes 4, 8, 12,
Chapter 2. Messages AOF000I to AOF969I
101
AOF954I • AOF958I
or 16 occurred, add more local page data sets manually.
If reason code 20 occurred, follow the instructions
given in messages IRA200E and IRA203I. For reason
code 24 follow the instructions of the messages IEE78n
issued before this message.
System programmer response: None.
Module: INGRVX20
Classes: None.
TEC: NO
Module: INGRX742
Classes: 40, 43.
AOF957I
TEC: NO
Explanation: The automation has logged an
intermediate result of an automated process.
AOF954I
PAGE DATA SET dsname
SUCCESSFULLY ADDED.
Explanation: Due to a recovery situation the
automation successfully added a local page data set to
the system.
The variable dsname shows the name of the data set.
LOG ENTRY: entry
The variable entry shows the log entry.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGRVX92
Classes: None.
System action: Processing continues.
TEC: NO
Operator response: None.
System programmer response: Delete the page data
set via the PAGEDEL command when the data set is no
longer needed. The data set is then returned to the list
of spare page data sets being used by the automation.
If the data set was dynamically allocated you can also
delete it physically when no other page data set is
active on the volume where the data set is allocated.
AOF958I
DUMP COULD NOT BE TAKEN. RC=rc
RSN=rsn.
Explanation: The requested dump could not be taken.
v The variable rc shows the return code. It can have
the following values:
RC
Description
Module: INGRX742
4
Only partial dump was taken.
Classes: 40, 43.
8
SDUMPX macro error occurred.
TEC: NO
12
An internal error occurred.
16
An internal error occurred.
20
An internal error occurred.
24
No private storage is available.
28
No common storage is available.
AOF955I
NO DIFFERENCES FOUND
Explanation: A comparison of IPL information did not
indicate any differences.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGRX200, INGRX201
Classes: None.
TEC: NO
AOF956I
IPL INFORMATION OF timestamp
FROM sysname HAS BEEN DELETED
Explanation: All IPL information collected for the
system after it was IPLed at timestamp was deleted.
The variable timestamp shows the time of the IPL.
The variable sysname shows the name of the system.
System action: Processing continues.
Operator response: None.
102
System Automation for z/OS Messages and Codes:
v The variable rsn shows the reason code.
System action: Processing continues.
Operator response: Depending on the return code do
the following:
RC
Description
4
Search the system log for message IEA911E for
the reason of the partial dump.
8
Refer to the return and reason code
description of the SDUMPX macro for the
reason why the dump could not be taken.
12, 16, 20
Contact your IBM service representative.
24, 28
Retry the function later.
System programmer response: None.
Module: INGRX262
AOF959I • AOF963I
Classes: None.
TEC: NO
name is unknown and it is running on an
un-automated system.
The following variables are used:
AOF959I
SYSTEM sysname IS NOT
REGISTERED.
Explanation: The requested system is not registered to
the automation. However, this function requires the
registration because it invokes system services locally.
System action: Processing continues.
Operator response: Override the system name with
blanks to force the selection panel showing the system
being registered. Or, start the automation on the
requested system using the same XCF group as the
local system.
sysname
The name of the system running the address
space.
asid
The address space ID running the task.
tcbaddr The TCB address of the task holding the
enqueue.
resource The enqueue resource major and minor name.
System action: None.
Operator response: None.
System programmer response: None.
System programmer response: Ensure the enqueue is
released and terminate the job if necessary.
Module: INGRX260
Module: INGRX741
Classes: None.
Classes: 40, 43.
TEC: NO
TEC: YES
AOF960E
HARDWARE INFORMATION OF
system COULD NOT BE VALIDATED.
AOF962I
UNABLE TO TERMINATE UN-NAMED
JOB (SYSTEM=sysname/ASID=asid/
TCB=tcbaddr). RESOURCE=resource.
Explanation: The automation detected that neither the
hardware information of the indicated system has been
defined, nor a connection to the Support Element of the
indicated system has been made for any of the
registered systems. If the system fails, the automation
(if enabled) is not able to take the appropriate
hardware actions to prevent possible hardware-related
outages caused by the system.
Explanation: Automation detected a long running
enqueue but is unable to cancel the job because the job
name is unknown. An attempt to abend the task has
also failed. Message AOF200I will detail why the abend
has failed.
The following variables are used:
sysname
system
The following variables are used:
The name of the system running the address
space.
The name of a system or a coupling facility.
System action: Processing continues.
asid
Operator response: None.
tcbaddr The TCB address of the task holding the
enqueue.
System programmer response: Add the hardware
definitions and make them available to all registered
systems using the ACF command. You can ignore this
message if: the indicated system will run the
automation, you have defined the necessary hardware
information, and the system is able to contact the
hardware.
Module: INGRX804, INGRX809
Classes: 40.
resource The enqueue resource major and minor name.
System action: None.
Operator response: None.
System programmer response: Ensure the enqueue is
released and terminate the job if necessary.
Module: INGRX741
Classes: 40, 43.
TEC: NO
AOF961I
The address space ID running the task.
TEC: YES
UNABLE TO CANCEL UN-NAMED
JOB (SYSTEM=sysname/ASID=asid/
TCB=tcbaddr). RESOURCE=resource.
Explanation: Automation detected a long running
enqueue but is unable to cancel the job because the job
AOF963I
UN-NAMED JOB (SYSTEM=sysname/
ASID=asid/TCB=tcbaddr) IS BEING
TERMINATED. RESOURCE=resource.
Explanation: Automation detected a long running
enqueue but is unable to cancel the job because the job
Chapter 2. Messages AOF000I to AOF969I
103
AOF964I • AOF966I
name is unknown. Automation is attempting to abend
the task.
AOF965I
The following variables are used:
The name of the system running the address
space.
Explanation: The automation detected a command
that is still executing. The command is abended to
avoid lockouts of other commands.
The address space ID running the task.
The following variables are used:
sysname
asid
The command command issued by
jobname is being purged due to a hung
command detection.
tcbaddr The TCB address of the task holding the
enqueue.
command
The first two words of the command text
when applicable.
resource The enqueue resource major and minor name.
System action: None.
jobname The job name issued the command.
Operator response: None.
System action: The automation abends the indicated
command.
System programmer response: Check that the job has
abended and ensure that the enqueue is released.
Operator response: None.
Module: INGRX741
Classes: 40, 43.
System programmer response: None.
Module: INGRX743
Classes: 40
TEC: YES
TEC: NO
AOF964I
Due to the detection of a long minor_res
lock the task taskid in address space asid
on system sysname is being abended.
AOF966I
Value value of type type for sysname
could not be evaluated.
Explanation: The automation detected a lock on the
indicated minor system resource being held for more
than 10 seconds. To prevent the lockout of further
commands the task holding the lock is being abended
with the ability to do its own recovery.
Explanation: The value for the indicated type could
not be verified. The reason is that the BCP internal
interface to the corresponding Support Elements could
not be established on any of the registered systems in
the sysplex.
The following variables are used:
The following variables are used:
minor_res
The minor resource name of the lock. The
major name is SYSIEFSD.
sysname
taskid
The task ID holding the lock.
asid
The address space ID running the task.
sysname
The name of the system running the address
space.
System action: The automation calls the Recovery
Termination Manager to abend the indicated task.
Operator response: None.
System programmer response: None.
Module: INGRX743
Classes: 40, 43.
TEC: YES
The name of the defined operating system.
value
The defined value.
type
The type in question. This can be one of the
following:
CPC
The CPC name.
LPAR
The LPAR name.
SYSPLEX
The SYSPLEX name.
TYPE
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGRX809
Classes: 40
TEC: NO
104
System Automation for z/OS Messages and Codes:
The operating system type, such as
MVS or CF.
AOF967E • AOF969I
AOF967E
Value mismatch detected between
system1 and system2 for system3 and type
type.
Explanation: The automation detected that the value
of the indicated type could not be verified. The reason
is that the BCP internal interface to the corresponding
Support Elements wasn't established on any of the
registered systems in the sysplex. In addition, at least
two different definitions exist for the indicated type on
different systems running SA z/OS.
As soon as the automation gets access to the Support
Element, the value will be re-evaluated and
automatically corrected.
newvalue
The new value.
oldvalue
The improper value. This may be (NULL) if a
value has been found in the hardware
configuration but there is no definition in the
ACF.
sysname2
The name of the system where the improper
setting was detected.
The following variables are used:
The type in question. This can be one of the
following:
system1 The name of a system running SA z/OS.
CPC
The CPC name.
system2 The name of a system running SA z/OS.
LPAR
The LPAR name.
system3 The name of the defined operating system.
SYSPLEX
The SYSPLEX name.
type
The type in question. This can be one of the
following:
CPC
The CPC name.
LPAR
The LPAR name.
SYSPLEX
The SYSPLEX name.
TYPE
|
|
|
|
|
|
sysname1
The name of the defined operating system.
The operating system type, such as
MVS or CF.
type
TYPE
The operating system type, such as
MVS or CF.
System action: The improper definition is temporarily
replaced by the actual value to prevent any outage that
could be caused by the old value.
Operator response: None.
System action: Processing continues.
System programmer response: Check and correct the
definitions in the ACF before the next startup of the
indicated system.
Operator response: None.
Module: INGRX809
System programmer response: Check and correct the
definitions before the next start-up of the affected
systems.
Classes: 40
Make sure that the definitions specified in the
automation policy through the SA z/OS Customization
Dialog reflect reality. For instance, when a mismatch
was detected for type SYSPLEX, verify the Sysplex
Name specified in the Sysplex Policy Definition and
change it to the real MVS sysplex name as required.
Module: INGRX809
Classes: 40
TEC: NO
AOF968E
Value oldvalue of type type for sysname1
on sysname2 has been replaced by
newvalue.
Explanation: The automation detected that your
hardware definition differs from the actual hardware. If
the local system name is not shown in the message, a
different setup other than the local system has been
used. This should generally be avoided.
The following variables are used:
TEC: NO
AOF969I
SESSION luname OF SMCS CONSOLE
consname HAS BEEN TERMINATED
DUE TO A BUFFER SHORTAGE
CONDITION.
Explanation: Automation has detected a shortage of
message or reply buffers caused by the indicated
console. To prevent the shortage from turning into an
outage condition, the console session has been
terminated. This recovery action cannot be reversed on
the shortage relief message.
The variable luname specifies the name of the
session.
The variable consname specifies the name of the
console.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGRX730
Chapter 2. Messages AOF000I to AOF969I
105
Messages AOF000I to AOF969I
Classes: 40
TEC: NO
106
System Automation for z/OS Messages and Codes:
Chapter 3. Messages AOFS000I to AOFS820I
AOFS000I
aa
Explanation: This message is given in conjunction
with a subsequent error message that explains what is
incorrect. It shows the SDF panel that is incorrect.
The variable aa identifies the buffer data in error.
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions.
AOFS001I
aa is active
Explanation: The task aa has been activated.
The variable aa shows the name of the task.
System action: None.
Operator response: None.
System programmer response: None.
AOFS002I
aa is inactive
Explanation: The task aa is not active at this time.
The variable aa shows the name of the task number.
System action: None.
Operator response: Start the task by issuing START
TASK=AOFTDDF.
System programmer response: None.
AOFS003I
aa is terminating.
Explanation: The task aa is ending.
The variable aa shows the name of the task number.
System action: None.
Operator response: None.
System programmer response: None.
AOFS004I
aa is terminated
Explanation: The task aa has ended.
The variable aa shows the name of the task number.
Explanation: The requested action could not be
performed successfully.
The variable aa shows the name of the object that
the action was performed on.
System action: None.
Operator response: None.
System programmer response: None.
AOFS006I
LOGON denied, maximum users
exceeded.
Explanation: The maximum number of users that can
log on as SDF operators has been reached.
System action: SDF cannot be accessed.
Operator response: None.
System programmer response: Increase the value of
MAXOPS in member AOFINIT in your NetView
DSIPARM data set. Then restart SDF.
AOFS007I
Request denied because NetView is
terminating.
Explanation: SDF cannot be accessed because NetView
is ending.
System action: None.
Operator response: None.
System programmer response: None.
AOFS008I
Command SDF is not supported under a
non-OST task.
Explanation: This message is a response to an attempt
to access the SDF from a non-OST task. Non-OST tasks
cannot access the SDF because they do not support
full-screen function.
System action: None.
Operator response: None.
System programmer response: None.
AOFS009I
Extended attribute support is required.
Operator response: None.
Explanation: This message is a response to a request
to display a SDF panel. The panel could not be
displayed because it requires extended console support.
System programmer response: None.
System action: The SDF request is ended.
System action: None.
Operator response: None.
AOFS005I
LOGON to aa was unsuccessful
© Copyright IBM Corp. 1996, 2014
System programmer response: None.
107
AOFS010I • AOFS023I
AOFS010I
Request "aa" was successful for "bb".
Explanation: The request has been completed
successfully.
The variable aa shows the request that was
performed.
The variable bb shows the component that was
processed.
System action: None.
Operator response: None.
AOFS015I
Panel aa has not been replaced.
Explanation: The panel aa has not been replaced
because of a syntax error condition.
The variable aa shows the name of the panel.
System action: The former panel definitions are still
valid.
Operator response: None.
System programmer response: Correct the panel
definitions and reload the panel.
System programmer response: None.
AOFS020I
AOFS011I
Request "aa cc" was successful for "bb".
Explanation: The request has been completed
successfully.
The variable aa cc shows the request that was
performed.
The variable bb shows the component that was
processed.
System action: None.
Operator response: None.
System programmer response: None.
AOFS012I
Panel aa has been added.
Explanation: The panel aa has been added
successfully.
The variable aa shows the name of the panel.
System action: None.
Operator response: None.
System programmer response: None.
AOFS013I
The variable aa shows the name of the panel.
System action: None.
Operator response: None.
System programmer response: None.
Panel aa has not been added.
Explanation: The panel aa has not been added because
of a syntax error condition.
The variable aa shows the name of the panel.
System action: Processing continues.
Operator response: None.
System programmer response: Correct the panel
definitions.
108
Explanation: Dynamic composition of a SDF panel
was requested with BODY or CELL statements but the
number of columns specified exceeds the maximum
panel width.
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions.
AOFS021I
Temporary screen read error.
Explanation: The number of lines allowed has been
exceeded.
System action: The system continues to attempt to
display the screen data.
Operator response: If this condition does not change
without intervention, contact your system programmer.
System programmer response: Review the adequacy
of the screen display buffer for the expected screen
activity levels.
Panel aa has been replaced.
Explanation: The panel aa has been replaced
successfully.
AOFS014I
Too many columns defined for screen
width.
System Automation for z/OS Messages and Codes:
AOFS022I
Temporary screen read error - limit
exceeded.
Explanation: The number of lines allowed has been
exceeded.
System action: The system terminates the function.
Operator response: Contact your system programmer.
System programmer response: Review the adequacy
of the screen display buffer for the expected screen
activity levels.
AOFS023I
Buffer size specified is too small for
screen size.
Explanation: The screen buffer size specified in
AOFINIT is too small for the screen.
System action: None.
Operator response: None.
AOFS030I • AOFS091I
System programmer response: Increase the value of
SCREENSZ in AOFINIT in your NetView DSIPARM
data set. Then restart SDF.
AOFS030I
Unable to find component "aa."
Explanation: SDF did not find an entry for the
component aa.
The variable aa shows the name of the component
in one of the following formats:
status_comp
root.status_comp
root.status_comp(group_comp)
root.status_comp(major_group_comp.group_comp)
System action: None.
Operator response: None.
System programmer response: None.
AOFS031I
bb is unable to find component "aa."
Explanation: The command did not find an entry for
the component aa.
The variable aa shows the name of the component.
The variable bb shows the name of the command.
root.status_comp(group_comp)
root.status_comp(major_group_comp.group_comp)
The variable bb shows the status component name. If
an alternate status component name was passed by
SDF, it appears in parentheses following the primary
status component name.
System action: Processing continues. However, the
function may not operate as requested.
Operator response: None.
System programmer response: None.
AOFS091I
aa.bb(ii.cc),PR=dd,RV=ee,CO=ff,HL=gg,
DP=hh
Explanation: A status descriptor has been found that
matches the search arguments in a request to use status
descriptor information. This message identifies the
status descriptor and shows some of the information it
contains. This message identifies the status descriptor
and shows some of the information it contains.
Messages AOFS092I, AOFS093I and AOFS094I show
additional information contained in the status
descriptor.
System action: None.
v The variable aa shows the root (system) name of the
requested status component.
Operator response: None.
v The variable bb shows the status component name.
System programmer response: None.
v The variable cc shows the alternate status component
name.
AOFS032I
Unable to find component "aa bb(cc)".
Explanation: SDF did not find an entry for the
component aa.
The variable aa shows the root name of the
component.
The variable bb shows the name of the component.
The variable cc shows the alternate name of the
component.
System action: None.
Operator response: None.
System programmer response: None.
AOFS090I
aa bb cc status information
Explanation: A request to use status descriptor
information has been processed for the status
component identified in this message. Messages
AOFS091I, AOFS092I, AOFS093I, and AOFS094I are
generated after this one and show the contents of the
status descriptors matching the request search
arguments.
The variable aa shows the status component name in
one of the following formats:
root
root.group_comp
v The variable dd shows the priority associated with
the status descriptor. (This is normally specified in a
request to add the status descriptor to the chain of
descriptors for a status component).
v The variable ee shows the reference value for the
status descriptor.
v The variable ff shows the color associated with the
status descriptor. If this color is not specified on a
request to add a status descriptor, the default color
defined for the priority of the status descriptor is
used. The color is presented in abbreviated form as
follows:
– B (Blue)
– G (Green)
– P (Pink)
– R (Red)
– T (Turquoise)
– W (White)
– Y (Yellow)
v The variable gg shows the highlighting option
associated with the status descriptor. The
highlighting option is presented in abbreviated form
as follows:
– B (Blink)
– N (Normal)
– R (Reverse)
– U (Underscore)
Chapter 3. Messages AOFS000I to AOFS820I
109
AOFS092I • AOFS097I
v The variable hh shows the number of existing
duplicate status descriptors. Duplicate status
descriptors have identical reference value, priority,
info, color, highlight, and data values.
AOFS093I
Explanation: A status descriptor has been found that
matches the search arguments in a request to use status
descriptor information. This message shows some of
the information contained in the status descriptor.
Messages AOFS091I, AOFS093I, and AOFS094I show
additional information contained in the status
descriptor.
v The variable ii shows the major component name of
the alternate status component name if present.
System action: Processing continues.
Operator response: None.
The variable aa shows the value used to replace the
default STATUSTEXT information when the status
descriptor is used as the basis for the STATUSFIELD
and a status descriptor number other than 0 is
specified on the STATUSFIELD definition.
System programmer response: None.
AOFS092I
DATE=aa,TIME=bb,REPORTER=cc(dd),
PFP=ee, PU=ff,PD=gg,PLVU=hh,PLVD=ii
System action: Processing continues.
Explanation: A status descriptor has been found that
matches the search arguments in a request to use status
descriptor information. This message shows some of
the information contained in the status descriptor.
Messages AOFS091I, AOFS093I, and AOFS094I contain
additional information contained in the status
descriptor.
|
|
|
Operator response: None.
System programmer response: None.
AOFS094I
The variable bb shows the time that the status
descriptor was created in the format hh:mm:ss.
The variable cc shows the NetView operator ID that
made the request to create the status descriptor.
The variable aa shows the data displayed when the
status descriptor is selected as the basis for a detail
display.
The variable dd shows the node of the reporter, if
available, appears in parentheses immediately
following the ID.
System action: Processing continues.
The variable ee indicates whether or not the status
condition is propagated to the focal point. If
propagation was requested, Y is shown, if not, N is
shown.
Operator response: None.
System programmer response: None.
The variable ff indicates whether or not the status
condition is propagated upward through the SDF
tree structure. If upward propagation was
requested, Y is shown; if not, N is shown.
AOFS095I
The variable hh shows the tree node that upward
propagation is not performed beyond. An asterisk(*)
indicates that upward propagation ends at the root
(system) node.
Operator response: None.
System programmer response: None.
110
System Automation for z/OS Messages and Codes:
End of aa status information
Explanation: This message identifies the end of the
status information:
The variable aa shows the status component name
in one of the following formats:
root
root.group_comp
root.status_comp(group_comp)
root.status_comp(major_group_comp.group_comp)
The variable gg indicates whether or not the status
condition is propagated downward through the SDF
tree structure. If downward was requested, Y is
shown; if not, N is shown.
System action: Processing continues.
DA=aa
Explanation: A status descriptor has been found that
matches the search arguments in a request to use status
descriptor information. This message shows some of
the information contained in the status descriptor.
Messages AOFS091I, AOFS092I, and AOFS093I show
additional information contained in the status
descriptor.
The variable aa shows the date that the status
descriptor was created on in the format
YYYYMMDD.
The variable ii shows the tree node that downward
propagation is not performed beyond. An asterisk
(*) indicates that downward propagation is
performed to all subordinate nodes of the status
component.
IN=aabbcc
System action: None.
Operator response: None.
System programmer response: None.
|
AOFS097I
|
|
|
|
|
Explanation: This message is generated by the
command SDFQNM. It provides the name of an SDF
root component of the current tree structure.
aa
The variable aa shows the SDF root component
name.
AOFS098I • AOFS505I
|
System action: Processing continues.
|
Operator response: None.
|
System programmer response: None.
|
AOFS098I
|
|
|
Explanation: This message is generated by the
command SDFQNM. It provides the name of an SDF
tree component for a selected root component.
aa bb cc
The variable aa shows the level of the tree
component right-justified.
|
|
The variable bb shows the SDF tree component
name.
The variable cc shows the major component name in
parentheses. The name makes the tree component
name unique if necessary.
System action: Processing continues.
Operator response: Enter the command again using
the correct operands.
System programmer response: None.
AOFS502I
Specified operand "aa" invalid for "bb
cc".
Explanation: An operand that is not valid was
specified for this command.
The variable aa shows the operand that is not valid.
The variable bb cc shows the command that was
entered.
System action: None.
Operator response: Enter the command again using
the correct operands.
System programmer response: None.
Operator response: None.
AOFS503I
System programmer response: None.
Explanation: The specified parameter is not valid for
this command.
End of aa
The variable aa shows the parameter that is not
valid.
AOFS099I
Explanation: This message indicates the end of the
command aa.
The variable aa shows the name of the command.
Specified parameter "aa" invalid.
System action: None.
System action: None.
Operator response: Enter the command again using
the correct parameters.
Operator response: None.
System programmer response: None.
System programmer response: None.
AOFS500I
Maximum number of "aa-bb" operands
exceeded.
Explanation: The maximum number of operands
allowed for the keyword identified in this message was
exceeded.
AOFS504I
Expected parameter(s) missing for
request "aa".
Explanation: One or more command parameters are
missing.
The variable aa shows the parameter in error.
System action: None.
The variable aa shows the name of the panel that
contains the keyword.
Operator response: Enter the command again using
the correct parameter(s).
The variable bb shows the keyword that too many
operands were specified for.
System programmer response: None.
System action: None.
Operator response: Enter the command again, making
sure that the correct number of operands is specified
for the keyword you specify.
System programmer response: None.
AOFS501I
Specified operand "aa" invalid for "bb".
Explanation: An operand that is not valid was
specified for this command.
AOFS505I
Syntax error for "aa".
Explanation: A syntax error was encountered in the
command that was entered.
The variable aa shows the parameter in error.
System action: None.
Operator response: Correct the command syntax and
reissue the command.
System programmer response: None.
The variable aa shows the operand that is not valid.
The variable bb shows the command was entered.
System action: None.
Chapter 3. Messages AOFS000I to AOFS820I
111
AOFS506I • AOFS512I
AOFS506I
First level of the tree must be a 1: aa.
AOFS509I
Status element major error, Element=aa.
Explanation: There was an attempt to define the
structure of a tree with a number other than 1.
Explanation: An internal SDF status element chaining
error occurred.
The variable aa shows the first leaf of the tree.
The variable aa shows the name of the status
component. The status component can be preceded
by the root component or by the root component
and the major component name separated by
periods.
System action: The AOFTDDT task will not become
active.
Operator response: Contact your system programmer.
System programmer response: Ensure your system
tree definitions in AOFTREE start with a level number
of 1. Then issue the START TASK=AOFTDDF
command again.
AOFS507I
Invalid level - less than 1: aa.
Explanation: There was an attempt to define the
structure of a tree with a number that is less than 1.
The variable aa shows the tree's leaf in error.
System action: The AOFTDDF task will not become
active.
System action: SDF request ended.
Operator response: Contact your system programmer.
System programmer response: If you cannot
determine the cause of the problem using the
information available to you, contact your IBM service
representative.
AOFS510I
Explanation: An attempt was made to define the
structure of a tree with the dependent subsystems
numbered out of sequence.
The variable aa shows the tree's leaf in error.
Operator response: Contact your system programmer.
System programmer response: Make sure that the
system tree definitions in AOFTREE have a level
number of 1 or higher. Then issue the START
TASK=AOFTDDF command again.
AOFS508I
Status element in tree not found,
Element=aa.
Explanation: The root component or status component
name, or both, that were specified in an SDF
STATUSFIELD statement cannot be found in the active
SDF tree structure. The information message is issued
during SDF initialization, or while processing an
SDFPANEL ADD command. If the function completes
successfully, message AOFS011I is issued, indicating the
panel in question.
The variable aa shows the name of the status
component. The status component can be preceded
by the root component or by the root component
and the major component name separated by
periods.
System action: Processing continues.
Operator response: None.
System programmer response: Ensure that the
referenced root component or status component, or
both, that were specified in the SDF STATUSFIELD
statement for the loading panel exist in the active SDF
tree structure.
Tree levels out of sequence: aa.
System action: The AOFTDDF task will become
active, but the status of the subsystems will not be
determined.
Operator response: None.
System programmer response: Make sure that the
system tree definitions in AOFTREE follow in a valid
hierarchical sequence.
AOFS511I
Member "aa" not found.
Explanation: SDF attempted to prepare the member
named in the message but could not find it.
The variable aa shows the name of the member that
could not be found.
System action: Processing continues.
Operator response: None.
System programmer response: Make sure that the
member identified in the message is valid. Add the
member in the DSIPARM concatenation chain or correct
the SDF panel definitions that refer to the erroneous
member.
AOFS512I
Field overlapping occurred in gg:
aa(bb,cc) <-> dd(ee,ff).
Explanation: During the post-validation of all panels
that have been defined SDF detected an overlay
between two field definitions.
v
System action: The panel is not processed.
Operator response: None.
112
System Automation for z/OS Messages and Codes:
AOFS513I • AOFS519I
System programmer response: Correct the panel
definitions.
AOFS513I
Terminating propagation level "aa" not
found.
Explanation: The identified propagation level was not
found the on the chain of predecessors (ProplvLU) or
among the descendents of (ProplvLD) the status
component identified as the target of the command.
The variable aa shows the propagation level
(PropLvLU or PropLvLD) as specified by SDF.
System action: Propagation is performed; however, it
ends at the root node or the descendent leaf nodes of
the tree structure.
Operator response: Check the propagation level value
for accuracy.
System programmer response: None.
AOFS514I
Maximum number of aa keywords
exceeded.
Explanation: The maximum number of occurrences of
the keyword identified in this message was exceeded.
The maximum number is normally a variable specified
using another keyword.
The variable aa shows the keyword that appears too
many times.
System action: Processing continues. However, the
function may not operate as requested.
Operator response: Note the message content and the
command or function being attempted. Contact your
system programmer.
System programmer response: Increase the number of
allowable keywords by changing or specifying the
control variable.
AOFS515I
Keyword aa is out of sequence.
Explanation: The identified keyword appears
incorrectly in relation to other keyword parameters
specified for the function being performed.
The variable aa shows the keyword that appears
incorrectly.
System action: Processing continues. However, the
function may not operate as requested.
Operator response: Note the message content and the
command or function being attempted. Contact your
system programmer.
System programmer response: Correct the keyword
specification sequence and retry the operation.
AOFS516I
Keyword aa(bb) of cc is out of sequence.
Explanation: The identified keyword appears
incorrectly in relation to other keyword parameters
specified for the function being performed.
The variable aa shows the keyword that appears
incorrectly.
The variable bb shows the parameter that appears
incorrectly.
The variable cc shows name of the panel.
System action: Processing continues. However, the
function may not operate as requested.
Operator response: Note the message content and the
command or function being attempted. Contact your
system programmer.
System programmer response: Correct the keyword
specification sequence and retry the operation.
AOFS517I
Expected parameter(s) missing for
"aa-bb".
Explanation: One or more parameters are missing.
The variable aa shows the name of the panel.
The variable bb shows the keyword that lacks the
parameter(s).
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions. Then enter the command again.
AOFS518I
Expected parameter(s) missing for
"aa-bb(cc)".
Explanation: One or more parameters are missing:
The variable aa shows the name of the panel.
The variable bb shows the keyword that lacks the
parameter(s).
The variable cc shows the parameter that is missing.
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions. Then enter the command again.
AOFS519I
Specified operand "aabb" invalid for
"cc-dd(ee)".
Explanation: An operand that is not valid was
specified for this command.
The variable aa shows the operand that is not valid.
The variable bb indicates if the operand is too long.
The variable cc shows the name of the panel.
The variable dd shows the keyword in error.
Chapter 3. Messages AOFS000I to AOFS820I
113
AOFS520I • AOFS802E
The variable ee shows the parameter in error.
System action: None.
Operator response: None.
System programmer response: Correct the panel
definitions. Then enter the command again.
AOFS520I
Specified parameter "aa-bb" invalid.
Explanation: The specified parameter is not valid for
the keyword.
The variable aa shows the name of the panel.
The variable bb shows the keyword in error.
The variable aa shows the type of the definition.
The variable bb shows the name of the panel or the
tree.
System action: The duplicate definition has been
deleted.
Operator response: None.
System programmer response: Remove the duplicate
definitions.
If the actual definitions differed in some data, issue the
command RESYNC SDFDEFS. This adjusts the
definitions used by SDF.
System action: None.
AOFS800E
Operator response: None.
Explanation: An internal programming error occurred.
System programmer response: Correct the panel
definitions. Then enter the command again.
AOFS521I
CELL definitions do not fit in aa:
BODY(bb,cc).
Explanation: During the post-validation of all panels
that have been defined SDF detected a BODY section
with CELL definitions that will not fit. Either a single
CELL definition is out of range or the total length of all
CELL definitions is too large. The total length is
computed as follows:
#_cols (BODY) * rightmost end_pos (CELL) +
(#_cols (BODY) - 1) * distance (BODY) + 1
The length of the body section is calculated as follows:
end_pos - start_pos + 1
If the BODY defines an undefined end_pos the panel
width is used. In case the PANEL defines an undefined
width the screen width defined in member AOFINIT or
on the command SDFPANEL is used.
The variable aa shows the name of the panel.
The variable bb shows the actual row number where
the BODY field starts.
The variable cc shows the actual columns number
where the BODY field starts.
System action: The panel is not processed.
Operator response: None.
System programmer response: Correct the panel
definitions.
AOFS523I
Duplicate aa definitions found for bb
Explanation: The task AOFTDDF detected duplicate
panel or tree definitions for the indicated name. The
actual definitions may differ or not. SDF always uses
the definitions that have been processed first. However,
the processing sequence can differ from the sequence of
the definitions.
114
System Automation for z/OS Messages and Codes:
Internal error: Request "aa" invalid.
The variable aa shows the name of the request.
System action: The request is rejected.
Operator response: Record the type of the request,
and contact your system programmer.
System programmer response: Contact your IBM
service representative.
AOFS801E
Internal error: Invalid descriptor point.
Explanation: An internal programming error has
occurred involving the propagation of status through
the component tree as maintained by SDF. A request
was made to propagate status without supplying the
status to be propagated.
System action: Other messages related to this problem
might be generated.
Operator response: Contact your system programmer.
System programmer response: Report this problem to
your IBM service representative. Attempt to identify
the tree being used, and whether a status was being
added or deleted when the condition was detected.
AOFS802E
Internal error: Invalid state "aa" action
"bb".
Explanation: An internal error occurred during
processing of a SDF panel definition statement. There is
a syntax error in the DSIPARM member that contains
the panel definition.
The variable aa shows the value of the state that is
not valid.
The variable bb shows the value of the action that is
not valid.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Review the SDF panel
definition and correct the syntax that is in error.
AOFS810I • AOFS820I
AOFS810I
Macro aa type bb request was
unsuccessful, RC=cc.
Explanation: The program called the indicated macro.
The macro was not able to satisfy the request and
returned the indicated return code for use in problem
determination.
The variable aa shows the name of the macro.
The variable bb shows the type of the request.
The variable cc shows the return code of the macro.
Operator response: Contact your system programmer.
System programmer response: Check the return code
to determine the cause of the problem.
AOFS820I
I/O error occurred while processing
member "aa".
Explanation: An I/O error occurred during processing
of the member aa.
The variable aa shows the name of the member.
System action: None.
System action: Processing terminates.
Operator response: Contact your system programmer.
Operator response: Make sure the member identified
in the message is valid. If the member identified in the
message is valid, contact your system programmer for
further analysis.
System programmer response: Check the return code
to determine the cause of the problem.
AOFS811I
aa request was unsuccessful, RC=bb.
Explanation: The program called the indicated macro.
The macro was not able to satisfy the request and
returned the indicated return code for use in problem
determination.
System programmer response: Verify that the member
name exists in the file pointed to by the procedure in
use at the time of the error. Review the Netlog being
used at the time of the error to see whether there was a
system error that could have prevented the member
from being found.
The variable aa shows the name of the macro.
The variable bb shows the return code of the macro.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the return code
to determine the cause of the problem.
AOFS812I
Macro aa request was unsuccessful,
RC=bb.
Explanation: The program called the indicated macro.
The macro was not able to satisfy the request and
returned the indicated return code for use in problem
determination.
The variable aa shows the name of the macro.
The variable bb shows the return code of the macro.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Check the return code
to determine the cause of the problem.
AOFS813I
Macro aa request was unsuccessful for
bb, RC=cc.
Explanation: The program called the indicated macro.
The macro was not able to satisfy the request and
returned the indicated return code for use in problem
determination.
The variable aa shows the name of the macro.
The variable bb shows the name of the control block.
The variable cc shows the return code of the macro.
System action: None.
Chapter 3. Messages AOFS000I to AOFS820I
115
Messages AOFS000I to AOFS820I
116
System Automation for z/OS Messages and Codes:
Chapter 4. Messages EVE120I to EVE842E (CICS Automation)
This chapter contains CICS Automation messages. CICS Automation also uses the
NetView HELPMSG facility to provide message information online. To view a help
panel for a specific message, enter on the CICS Automation command line:
HM EVEnnn
Where nnn is the message ID number.
EVE120I
Command accepted for subsystem,
APPLID = applid.
Explanation: An EVESNCCI command has been
validated and is accepted.
Operator response: None.
EVE121E
Error on DSIxxx request in progname, RC
= retcode.
Explanation: CICS Automation found an error on a
DSIxxx macro request issued in the program identified
by progname. The register 15 return code is retcode.
Operator response: None.
System programmer response: Analyze the netlog
and determine whether there is a logic error. If the
problem is a CICS Automation logic error, contact your
IBM Support Center.
Problem determination: Refer to Customization: Using
Assembler, for return codes from the DSIxxx macro
requests.
EVE122E
EVENTASK NOT ACTIVE
Explanation: A DSIMQS macro request failed because
the addressed task identified by taskid was not active.
This error can occur when any automated operator
specified in the EVENTASK initialization member is not
active or when the EVENTASK optional task is not
active.
System action: When the error is met, a return code of
8 is passed to the issue of the EVESNCCI command.
Operator response: If the EVENTASK task is not
active, start the task by issuing the "START TASK
=EVENTASK" or by using option 9.3 from the operator
interface. If one of the automated operators is not
active, start the autotask by issuing the "AUTOTASK
OPID=taskid" command.
Explanation: An error has been met on a DSIxxx
request in the specified program, indicating that no
NetView storage is available.
Operator response: None.
System programmer response: Investigate NetView
storage use. If you cannot locate the source of the
storage problem, contact your IBM Support Center.
EVE128I
Positive acknowledgement.
Explanation: A positive response (ACK) has been
received on an EVESNCCI Converse request.
Operator response: None.
EVE129E
msgtext
Explanation: A negative response (NACK) has been
received on an EVESNCCI Converse request or an error
has been detected during the processing of the request.
In the latter case, msgtext contains the EVE1nnE
message text explaining the error.
Operator response: If an error condition is indicated,
browse the netlog to determine the cause of the error.
NACK can be a “normal” response from a CICS
transaction. CSMT log may contain useful information
as well in case of an error.
EVE130I
EVENTASK ready.
Explanation: EVENTASK OPT initialization has
completed successfully.
Operator response: None.
EVE131I
EVENTASK terminated.
Explanation: EVENTASK OPT has completed
termination.
Operator response: None.
System programmer response: Determine why taskid
was not active.
EVE132E
EVE125E
Explanation: The EVENTASK initialization member
No storage available on DSIxxxx request
in progname.
© Copyright IBM Corp. 1996, 2014
Initialization member memname not
found.
117
EVE133E • EVE142E
memname could not be found in one of the DSIPARM
data sets.
the "START TASK=EVENTASK" command or option 9.3
from the operator interface.
Operator response: None.
System programmer response: Determine why no
NetView subsystem was active.
System programmer response: Ensure that the
initialization member specified by MEM= keyword on
the TASK statement for EVENTASK is contained in one
of the DSIPARM data sets. Restart the task by issuing
the "START TASK = EVENTASK" command or option
9.3 from the operator interface.
EVE133E
Error in memname at line linenum, code =
retcode.
Explanation: An error of type retcode is on line
linenum of the EVENTASK initialization member
memname.
01
Unrecognized keyword.
02
Duplicate specification.
03
Operand specification error.
04
Too many server keywords.
05
No valid servers specified.
Operator response: None.
System programmer response: Correct the failing
statement in the EVENTASK initialization member
memname and restart the task with the "START TASK =
EVENTASK" command or option 9.3 from the operator
interface.
EVE140E
Incorrect PPI buffer received.
Explanation: The program-to-program interface buffer
sent to the EVENTASK optional task was not correct.
Possible causes include:
v Program-to-program interface buffer header was
incomplete.
v Request type was incorrect (not C, S, R, A, or N).
v Length specification was inconsistent.
Operator response: None.
System programmer response: Correct the routine
that created the incorrect program-to-program interface
buffer. If the error is caused by a CICS Automation
logic error, contact your IBM Support Center.
EVE141E
Incorrect MQS buffer received.
Explanation: The MQS message buffer, containing a
program-to-program interface request that was sent to
the EVENTASK optional task, was not correct. Possible
causes include:
v Program-to-program interface buffer header was
incomplete.
v Request type was incorrect (not C, S, R, A, or N).
v Length specification was inconsistent.
EVE136I
Error on PPI request reqid, RC = retcode.
Explanation: The program-to-program interface
request reqid received a non-zero return code. This is
generally an error, however REQUEST 002 RC=014
indicates the PPI receiver is active; this is not an error
condition.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Review the NetView
netlog and investigate the cause of the error.
Program-to-program interface request types reqid and
request return codes retcode are documented in the
appendix “Program-to-Program Interface Return
Codes” in NetView Application Programming Guide. reqid
identifies the PPI request type and retcode details what
the problem is in issuing the PPI request.
EVE137E
NetView subsystem not available.
Explanation: An error has been encountered to a
program-to-program interface request indicating that no
NetView subsystem was available to act as a
program-to-program interface server.
Operator response: After the NetView subsystem is
restarted, start the EVENTASK optional task by issuing
118
System Automation for z/OS Messages and Codes:
Operator response: This problem is caused by CICS
Automation logic error. Contact your IBM Support
Center.
EVE142E
Function function not found in memname.
Explanation: A program-to-program interface buffer
sent to the EVENTASK optional task contained a
function and type specification that no entry in the
EVENTASK initialization member memname was found
for.
Operator response: None.
System programmer response: Add a request or
response server for function in the EVENTASK
initialization member memname if the function name
was correct.
Programmer response: Correct the routine that created
the incorrect program-to-program interface buffer if the
function name function was incorrect.
EVE148I • EVE175E
EVE148I
Segment-chain id canceled.
Explanation: An EVESNCCI cancel request
successfully freed all saved segments for the segment
identifier id.
Operator response: None.
EVE149I
Segment-chain id not found.
Explanation: An EVESNCCI cancel request (TYPE=C)
was issued. The specified segment-chain id could not
be found.
Operator response: None.
EVE171E
procname : Error in progname (transid),
reason = reason.
Explanation: CICS Automation has detected an error
in the program: progname in the transaction transid. The
type of error is reason.
In all CICS messages procname is the JOB name or STC
name that identifies the CICS system that issued the
message.
System action: Depending on reason a transaction
dump is created in the active CICS dump data set.
If the error occurred in:
Then:
EVESPPIC, EVESPPIP or
EVESPPIS,
The transaction is
terminated.
EVESCCCI
A non-zero return code is
passed to the caller.
EVESHLTH, and
EVESHLTH was invoked
by a converse request
(TYPE=C)
A NACK response is
passed to NetView.
EVESTISP
Control is relinquished to
allow CICS initialization
to continue, but the
program-to-program
interface is not started.
EVESPERR or EVESPMSG Control is returned to the
calling module.
EVE172I
applid : PPI active.
Explanation: This message confirms that the
program-to-program interface successfully initialized.
The variable applid is the CICS application Identifier,
which is used as the PPI receiver name for this
CICS.
Operator response: None required.
EVE173I
applid : PPI inactive.
Explanation: This message confirms that the
program-to-program interface normally terminated.
The variable applid is the CICS application Identifier,
which is used as the PPI receiver name for this
CICS.
Operator response: None required.
EVE174E
applid : PPI not active.
Explanation: The transaction to terminate the
program-to-program interface has been invoked, but
the program-to-program interface was not active.
The variable applid is the CICS application Identifier,
which is used as the PPI receiver name for this
CICS.
Operator response: None.
EVE175E
applid : Function function not found in
EVESPINM.
Explanation: A program-to-program interface buffer
sent from NetView to CICS contained a function
function that no entry in EVESPINM was found for.
The variable applid is the CICS application Identifier,
which is used as the PPI receiver name for this
CICS.
System action: For a converse request (TYPE=C), a
NACK response containing the error message text is
returned to the operator at the domain specified in the
program-to-program interface buffer header. This is the
operid in domainid of the originating EVESNCCI
command.
For all other requests (TYPE=S, R, A or N): none.
Operator response: None.
System programmer response: Refer to “Error Codes”
on page 121 and if necessary analyze the transaction
dump to determine the cause of the error, then correct
the problem. If the problem is caused by a CICS
Automation logic error, contact your IBM Support
Center.
Operator response: None.
System programmer response: Add a request server
for function in EVESPINM if the function name was
correct.
Programmer response: Correct the routine that created
the incorrect program-to-program interface buffer if the
function name function was incorrect.
Chapter 4. Messages EVE120I to EVE842E (CICS Automation)
119
EVE176E • EVE209I
EVE176E
Explanation: A response identified by id was received
from NetView. No transaction is awaiting that response.
This may be caused by:
v An incorrect id in the response
v The transaction awaiting the response timing out
v A C961 or C971 error occurring.
Operator response: None.
Programmer response: Have the NetView command
list or command processor that issues the unexpected
PPI RESPONSE corrected, or increase the timeout value
on the converse request.
EVE177E
the failure, then correct the problem. Ensure that
RECEIVERID= operand in the EVESPINM initialization
member is identical to RECEIVERID= operand in the
EVENTASK initialization member.
procname : No response expected for
identifier id.
procname : NetView subsystem is not
available.
Explanation: A program-to-program interface request
has been issued, but not NetView subsystem was
available to act as a program-to-program interface
server.
|
|
EVE181E
|
|
Explanation: A program-to-program interface
transaction did not start.
|
|
|
Operator response: Ensure that the transaction is
correctly defined in the CICS subsystem and through
the EVESPINM CICS PPI initialization member.
EVE182E
procname : Error on transaction start
copctrn for function function.
procname : Console has not been defined
to CICS.
Explanation: EVESPINM module specifies a console
definition where COPC transaction should be started.
That console name is not defined in CICS.
System programmer response: Either correct
EVESPINM, or define the console to CICS.
System action: The program-to-program interface
request is ignored. The program-to-program interface is
terminated.
EVE209I
Operator response: After the NetView subsystem that
serves program-to-program interface requests has been
(re)started, restart the program-to-program interface:
"MODIFY procname,COPS". COPS can also be restarted
via support panel option 9.3.
Explanation: The entry-type pair named in the
message was found by the automation routine to
contain errors. This message is issued when building
the CICS Message Exit policy from the ACF data.
System programmer response: Determine why the
NetView subsystem was not available.
v The variable data is the data that caused the error.
EVE178E
procname : PPI already active.
Explanation: The transaction to start the
program-to-program interface was invoked. The
program-to-program interface was not inactive,
however.
System action: The program-to-program interface
start-up request is ignored.
Operator response: None.
EVE179E
procname : Receiver program progname
problem, reason = reason.
Explanation: An error has been encountered on a
program-to-program interface request indicating that
the specified receiver program progname was “not
defined” or “not active.”
System action: Return code 8 and an error code (C226
or C204) identifying the precise cause of the failure are
set for the caller.
Operator response: None.
System programmer response: Analyze the cause of
120
System Automation for z/OS Messages and Codes:
WARNING: ACF ENTRY entrytype, HAS
INVALID DATA "data" FOR "entry",
reason.
v The variable entrytype is the ENTRY-TYPE pair.
v The variable entry is:
– "INSERT=" for messages beginning with DFH.
– "TOKEN=" for TD Queue messages.
– "MSGDISP=" for both.
It refers to the statement that contained the error.
v The variable reason is an explanation of the error.
Invalid number or invalid choice of keyword.
System action: The message policy is loaded without
the offending data.
In the case of MSGDISP= this might mean the entire
message is not loaded into the policy.
In the case of TOKEN= or INSERT= the offending
TOKEN= or INSERT= statement is ignored.
Operator response: None required.
System programmer response: Correct the entry-type
pair in your automation control file and reload it using
the INGAMS command.
EVE654E • C004
EVE654E
No INCLUDE/EXCLUDE entries exist in
LISTSHUT table for subsystem.
Explanation: The LISTSHUT table must contain either
INCLUDE or EXCLUDE entries for the specified
subsystem in order for SHUTDOWN to occur.
EVE841I
procname : text.
Explanation: The CEMT command listed in text has
been requested from NetView through the
program-to-program interface.
System action: None.
System action: No transactions will be purged.
procname : Unsupported CEMT
command.
Operator response: Change the table and reload the
control file.
EVE842E
Classes: 40.
Explanation: The CEMT command listed in the
preceding EVE841I message is not supported by
EVESCEMT, for example, CEMT PERFORM
SHUTDOWN.
EVE657E
Message received by EVEET050: msgtext.
Explanation: EVEET050 received an unexpected
message.
System action: Processing is terminated.
Operator response: Notify your system programmer.
System programmer response: Contact your IBM
Support Center.
System action: Ignore CEMT command. If the CEMT
command was requested with a converse request
(TYPE=C), return a NACK response with message
EVE842E as NACK text.
Operator response: None.
Classes: 40.
Error Codes
CICS error codes start with the following letters:
A
These are standard CICS error codes. Refer to CICS Messages and Codes.
C
These are CICS Automation program-to-program interface error codes. See
below.
C001
Explanation: Someone attempted to invoke a CEMT
command or to start or stop the program-to-program
interface by entering the corresponding transaction
name from a terminal, or someone entered the
transaction name for the long-running
program-to-program interface transaction from a
terminal.
System action: Terminate the transaction abnormally.
System programmer response: Analyze the dump to
find the cause of the error, then correct the problem.
Module: EVESPPIP and EVESPPIS.
C003
Explanation: A program-to-program interface request
was issued while the program-to-program interface was
not active.
Operator response: None.
System action: Issue message EVE171E. Set return
code 8 for caller.
System programmer response: Educate your users
that they should not alter these transactions.
Operator response: None.
Module: EVESCEMT, EVESPPIC, EVESPPIP, and
EVESPPIS.
Module: EVESCCCI.
C002
C004
Explanation: The address of the program-to-program
interface Intercommunication Area (ICA) was
corrupted, probably because some other program
altered unprotected storage in the CICS address space.
Explanation: EVESCCCI has not been invoked via
EXEC CICS LINK.
System action: Issue message EVE171E. Dump CICS
and transaction storage.
Operator response: None.
Operator response: None.
System programmer response: Start PPI TASK.
System action: Issue message EVE171E. Terminate
transaction abnormally.
System programmer response: None.
Chapter 4. Messages EVE120I to EVE842E (CICS Automation)
121
C005 • C011
Programmer response: Use EXEC CICS LINK to
invoke EVESCCCI.
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESCCCI.
Module: EVESCEMT.
C005
C008
Explanation: Incorrect parameter list passed to
EVESCCCI.
Explanation: Return code 12 was received from
EVESCCCI because the OUTDSECT block was
incorrect.
System action: Issue message EVE171E. If the length
of the parameter list is incorrect, terminate transaction
abnormally; otherwise return to caller with return code
12.
System action: Issue message EVE171E. Dump
transaction storage. Terminate transaction abnormally.
Operator response: None.
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
System programmer response: None.
Programmer response: Correct the parameter list
passed via the COMMAREA on the LINK to
EVESCCCI.
Module: EVESCEMT, and EVESPPIC.
Module: EVESCCCI.
C009
C006
Explanation: Transaction could not be started
successfully.
Explanation: The buffer containing a
program-to-program interface request that was sent
from NetView to CICS was incorrect. This is caused by:
System action: Issue message EVE181E. Dump
transaction storage.
Operator response: None.
v An incomplete program-to-program interface buffer
header.
System programmer response: If non-terminal
transaction security is not active in CICS, ensure that
this function is disabled in CICS Automation by
specifying USERID=NO in the CICS PPI initialization
member EVESPINM. For further information on this
member, refer to IBM Tivoli System Automation for z/OS
Product Automation Programmer's Reference and Operator's
Guide.
v An incorrect request type (not C, S, R, A, N).
v An inconsistent length specification.
v An incorrect program-to-program interface sender
identification. This is caused by a mismatch between
the RECEIVERID specifications in the EVENTASK
and EVESPINM initialization members.
System action: Issue message EVE171E. Dump
transaction storage.
Operator response: None.
System programmer response: If caused by a
mismatch between EVENTASK and EVESPINM, correct
the mismatch error. Otherwise, contact your IBM
Support Center because this problem is caused by a
CICS Automation logic error.
Module: EVESPPIC.
Make sure that the transaction is properly defined in
the CICS PPI initialization member EVESPINM.
If these requirements are fulfilled, contact your IBM
Support Center.
Module: EVESPPIC
C011
Explanation: CICS WRITEQ TS failed.
System action: Issue message EVE171E. Dump
transaction storage. Terminate transaction abnormally.
C007
Explanation: A CEMT request was sent over the
program-to-program interface from NetView to CICS.
The request server found that the INTDSECT block was
incorrect.
System action: Issue message EVE171E. Dump
transaction storage. Terminate transaction abnormally.
Operator response: None.
System programmer response: This problem is caused
122
|
|
System Automation for z/OS Messages and Codes:
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESTISP and EVESPPIC.
C012 • C117
C012
Module: EVESCCCI, EVESCEMT, EVESPERR,
EVESPPIC, and EVESPPIS.
Explanation: CICS READQ TS failed.
System action: Issue message EVE171E. Dump
transaction storage. Terminate transaction abnormally.
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Ensure that the
PLTPI program EVESTISP has been executed
successfully. Contact your IBM Support Center.
Module: EVESCCCI, EVESPPIC, EVESPPIP, and
EVESPPIS.
C017
Explanation: CICS GETMAIN failed.
System action: Issue message EVE171E. Terminate
transaction abnormally.
Operator response: None.
System programmer response: Increase the region
size.
Module: EVESCCCI, EVESCEMT, and EVESPPIC.
C013
C018
Explanation: CICS START failed.
Explanation: CICS FREEMAIN failed, or, possibly, a
storage violation has occurred.
System action: Issue message EVE171E. Dump CICS
tables.
Operator response: None.
System programmer response: Analyze the dump to
find the cause of the failure and correct the problem.
Ensure that the transaction that failed to start and the
program to be invoked when the transaction starts
have been defined and enabled. Also make sure that
the program resides in a DFHRPL library.
Module: EVESTISP, EVESPPIC, and EVESPPIS.
System action: Issue message EVE171E. Dump
transaction storage.
Operator response: None.
System programmer response: Analyze the dump to
find the cause of the failure, then correct the problem.
Module: EVESCCCI.
C019
Explanation: CICS DELAY failed.
C014
Explanation: CICS RETRIEVE failed.
System action: Issue message EVE171E. Dump
transaction storage. If the CEMT command was
requested through a converse request (TYPE=C), return
a NACK response with message EVE842E as NACK
text. Terminate transaction abnormally.
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESCEMT.
System action: Issue message EVE171E. Dump
transaction storage. Set return code 16 for caller.
Operator response: None.
System programmer response: Analyze the dump to
find the cause of the failure, then correct the problem.
Module: EVESCCCI.
C020
Explanation: CICS CANCEL failed.
System action: Issue message EVE171E. Dump
transaction storage. Terminate transaction abnormally.
Operator response: None.
C015
Explanation: CICS LINK or LOAD failed.
System programmer response: Analyze the dump to
find the cause of the failure, then correct the problem.
System action: Issue message EVE171E. Dump
transaction storage and CICS tables. Terminate
transaction abnormally.
Module: EVESPPIC.
Operator response: None.
Explanation: OS GETMAIN failed.
System programmer response: Analyze the dump to
find the cause of the failure, then correct the problem.
Ensure programs are defined and enabled and available
in a DFHRPL library.
System action: Issue message EVE171E. Dump
transaction storage.
C117
Operator response: None.
Chapter 4. Messages EVE120I to EVE842E (CICS Automation)
123
C2nn • C990
System programmer response: Analyze the dump to
find the cause of the failure. then correct the problem.
Increase the region size or amend SIT parameters to
allow for sufficient OSCOR.
Module: EVESTISP.
C961
Explanation: RQE chain corrupted.
System action: Issue message EVE171E. Dump
transaction storage. Set return code 16 for the caller.
Operator response: None.
C2nn
Explanation: A program-to-program interface problem
has occurred. nn identifies the program-to-program
interface return code.
System action: For nn = 20, 22, 23, 25, 31, 33, 36, 40,
and 90, issue message EVE171E and dump transaction
storage. For all other values of nn, no message is
issued.
System programmer response: This problem is caused
by a transaction that altered storage in the CICS
address space, or by a CICS Automation logic problem.
Determine the cause of the problem. If the problem is
caused by a CICS Automation logic problem, contact
your IBM Support Center.
Module: EVESCCCI.
Operator response: None.
C971
System programmer response: Determine the cause of
the error. If the error is caused by a CICS Automation
logic error, contact your IBM Support Center.
Explanation: RQE chain corrupted.
Problem determination: Program-to-program interface
request return codes retcode are documented in
Application Programming Guide: Program-to-Program
Interface,.
Module: EVESCCCI and EVESPPIC.
C950
Explanation: The TWA size of the COMT transaction
is too small.
System action: Issue message EVE171E. Dump
transaction storage. Ignore all RQEs that currently exist,
which may result in several EVE176E messages later.
Operator response: None.
System programmer response: This problem is caused
by a transaction that altered storage in the CICS
address space, or by a CICS Automation logic problem.
Determine the cause of the problem. If the problem is
caused by a CICS Automation logic problem, contact
your IBM Support Center.
Module: EVESPPIC.
System action: Issue message EVE171E. Terminate
transaction abnormally.
C980
Operator response: None.
Explanation: Undefined error code.
System programmer response: Ensure that the TWO
size of the COMT transaction is greater than or equal to
the TWA size of the CEMT transaction (512 bytes).
System action: Issue message EVE171E. Dump
transaction storage.
Module: EVESCEMT.
C960
Explanation: A TS item passed to EVESCCCI by
EVESPPIC when a response is received from NetView
has an incorrect length
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESPERR.
C990
System action: Issue message EVE171E. Dump
transaction storage. Set return code 16 for the caller.
Explanation: Undefined message ID.
Operator response: None.
System action: Issue message EVE171E. Dump
transaction storage.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESCCCI.
Operator response: None.
System programmer response: This problem is caused
by a CICS Automation logic error. Contact your IBM
Support Center.
Module: EVESPMSG.
124
System Automation for z/OS Messages and Codes:
Chapter 5. Messages EVI022I to EVI844A (IMS automation)
Messages generated by IMS automation are built from the DFS, and DXR messages
issued by IMS/VS, in addition to the AVM, IOS, and IEF messages issued by the
MVS Availability Manager, the Input/Output Supervisor, and the MVS Job
Scheduler respectively.
IMS automation supports the NetView Help Message command (HM). By entering
HM plus the message ID on a NetView or IMS automation command line, you can
access the message documentation online.
Important note for system programmers:
The IMS messages use message classes 0, 40, 43, 44, 46, 47 and 60. This means that
the notify operator entries in the control file need to have these message classes
defined in the CLASS= parameter.
EVI022I
Bad return code retcode from routine.
Explanation: IMS automation issued an internal
command or macro call and received a non-zero return
code. This may indicate an internal error.
The variable retcode shows the return code.
The variable routine shows the command, module or
macro name that issued the return code.
System action: Processing is terminated.
Operator response: Contact your system programmer.
System programmer response: Check the return code
of the indicated routine and any associated messages
on the system log and NetLog. Contact your IBM
Support Center for further assistance.
Classes: None.
EVI030I
resource not defined to System
Automation
Explanation: One of the SA z/OS commands was
entered against a dependent region that is not defined
to SA z/OS.
The variable resource is the name of the resource that
is unknown to SA z/OS.
System action: The system does not process this
action and stops processing multiple actions.
Operator response: Correct the action character if it
was entered incorrectly or do not request SA z/OS
actions for non-SA z/OS regions. The exceptions are
START and STOP, which will issue the /START
REGION and /STOP REGION commands for the
dependent region.
Module: EVIRYDP0
EVI031I
resource cannot process action &2
Explanation: This message may be issued for the
following reasons:
1. One of the actions entered against a dependent
region cannot be processed by that dependent
region. This is usually due to an /ASSIGN against a
dependent region that has no classes.
2. One of the actions entered against a resource in the
TCO list cannot be processed by the resource type.
This is usually due to issuing a LOAD request
against the LTERM, or issuing a START or STOP
request against a MEMBER resource.
The variable resource is the name of the resource.
The variable &2 is the action.
System action: The system does not process this
action and stops processing multiple actions.
Operator response: Use the appropriate line command
against the appropriate resource type.
Module: EVIRYTCO
Classes: None.
EVI326I
No TCO definitions found.
Explanation: When attempting to issue the requested
command(s) for the TCO option selected by the
operator, the process was unable to find any entries in
the control file for this request.
System action: The request is denied.
Operator response: Notify your system programmer
that the function selected is not defined in the control
file.
System programmer response: Verify that the control
Classes: None.
© Copyright IBM Corp. 1996, 2014
125
EVI350I • EVI844A
file contains the required entries for the function
selected by the operator.
System programmer response: Browse the netlog to
determine the cause of the error.
Classes: 0, 40, 60.
EVI350I
TCO HAS NOT BEEN INITIALIZED,
REQUEST REJECTED
Explanation: A TCO function has been attempted and
TCO is not supported by this IMS at this time.
System action: The request function is not executed.
Operator response: Ensure that the IMS that is
associated with the request is active. Use option 1,
inquiry, from the IMS automation panels to find out. If
it is active, check with your system programmer to
ensure that this IMS has been setup to include IMS
TCO support.
System programmer response: Ensure that the IMS
associated with the TCO request has been setup to
include IMS TCO support. For example, IMS uses 2
logical terminals, as well as a DD statement in the IMS
startup PROC to support TCO requests to start, stop,
and load a TCO member.
EVI421I
Request ignored, 'IMS' is not up.
Explanation: The requested action is invalid because
IMS is not up.
Operator response: Startup the IMS subsystem. After
a successful startup, retry the request.
EVI706E
Syntax error - parameter "parmtype" =
"parmvalue". msgtext
Explanation: Invalid value specified in the
Automation control file member for keyword (refer to
PARAMETER value in EVI706E message).
System action: The CLIST is terminated.
Operator response: Notify your system programmer.
System programmer response: Correct the value for
the parmtype keyword in the policy and refresh the
configuration.
Classes: 40, 47, 60.
EVI844A
subsystem RESYNC FAILURE - UNABLE
TO COMPLETE command COMMAND
Explanation: This message indicates that a problem
occurred during IMS resynchronization processing.
The variable subsystem shows the name of the IMS
subsystem.
The variable command shows the failed command.
System action: The resynchronization processing may
be incomplete.
Operator response: Review the netlog for errors.
Report the problem to your system programmer.
126
System Automation for z/OS Messages and Codes:
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
EVJ000I
date time module ENTRY/EXITparms/
RC=rc
Explanation: When the trace option is activated, TWS
Automation writes this data to the log for entry and
exit tracing. The date is shown in the format
mm/dd/yyyy.
Operator response: None.
EVJ001I
command: STARTED, PARMS=parameters
Explanation: Command processor has been entered
with the parameters shown. This is an informational
message issued for audit purposes.
System action: The module ceases processing and
returns a non-zero return code to its calling routine.
Operator response: Review log for other messages
and notify your system programmer.
Determine the source of the failure, typically an
incorrect control file value or failure of the product
initialization routines (beginning with EVJEAAIC) to
run, and correct it. Call IBM Service if you require
assistance.
Destination: Module name and failing parameter
EVJ006E
System action: None.
Operator response: None.
System programmer response: None.
Destination: Command processor name, parameters.
EVJ002I
command: COMPLETED
SUCCESSFULLY, PARMS=parms
Explanation: Command processor has completed
successfully. This is an informational message issued
for audit purposes.
System action: None.
Operator response: None.
System programmer response: None.
Destination: Command processor name, parameters.
EVJ003E
command UNABLE TO PROCESS
PARMS=(parameters), REASON=reason
Explanation: OPC has initiated a request, but it cannot
be processed due to the reason shown. This message
will normally be preceded by a message giving specific
details of the failure.
System action: The request is canceled.
Operator response: Review log for other messages.
System programmer response: Resolve any system or
definition problems, then reset the request.
Destination: Request parameters, reason text.
EVJ005E
module UNABLE TO OBTAIN parameter
Explanation: The module indicated tried to obtain the
value of a parameter from product globals, but the
value was null or not as expected.
© Copyright IBM Corp. 1996, 2014
cmdname COMMAND FAILED FOR
module: RETURN CODE=rc
PARMS=parms
Explanation: A command issued within this command
processor received an invalid return code.
The variable cmdname shows the name of the
command that failed.
The variable module shows the name of the calling
command processor.
The variable rc shows the return code from the
failing command.
The variable parms shows the parameters passed to
the failing command.
System action: The command processor terminates
and logs an error message.
Operator response: Review the error messages in the
NetView and MVS logs.
System programmer response: Review the associated
error messages in the NetView and MVS logs. If
necessary, correct definition problems and retry the
operation.
EVJ007E
SUBSYSTEM subsys IN INVALID
STATUS stat FOR REQUEST (request)
Explanation: TWS Automation has attempted to
execute the request for the indicated subsystem, but
was unable to complete because the subsystem was in
an invalid status. For example, trying to start a
subsystem that is already up, or stop a subsystem that
is already down.
System action: The operation in OPC is posted in
error with a U001 status.
Operator response: Review NetView log for prior
activity for the subsystem.
Check for manual intervention with the subsystem,
such as starts and stops performed outside of
automation control. Also, for shutdowns, specify
127
EVJ008E • EVJ041E
RESTART=CTL so that subsystems will not be restarted
by NetView initializations.
Destination: Command processor name, subsystem,
subsystem status, TWS Automation request type.
EVJ008E
OPERATION ALREADY IN PROGRESS
FOR subsys, REQUEST=(reqparms)
Explanation: TWS Automation has attempted to
execute the request for the indicated subsystem, but
was unable to process because a previous request is
still outstanding for the subsystem, or the previous
request may not have completed successfully.
The variable subsys shows the name of the
subsystem involved.
The variable reqparms shows the details of the
previous request.
System action: The new operation, indicated by
additional message EVJ003E is posted in error with a
U005 status.
Operator response: Review NetView log for prior
activity for the subsystem.
Check for previous errors in the log, or review TWS
and workstation definitions. When problems are
resolved, reset the TWS status file record using
OPCAQRY and rerun the operation.
EVJ009E
NO RESPONSE FROM SYSTEM
domainid WHILE SENDING REQUEST
(request)
Explanation: TWS Automation has attempted to
forward the request to the remote domain, but did not
receive an acknowledgment from that system.
System action: The operation in OPC is posted in
error with an S999 status.
Operator response: Check status and connectivity of
the system in question. If the problem can be resolved,
rerun the failing operation.
EVJ011I
date time OPC message text
Explanation: While attempting to communicate with
OPC, an operator initiated request to display or modify
data has failed. The message text is the OPC message
received. This message is normally preceded by another
message, indicating the TWS Automation module that
was attempting to request data from OPC.
System action: None.
Operator response: Review message in the
appropriate OPC/ESA or OPC/A manual.
Correct problems such as incorrect definitions of OPC
subsystem name.
Destination: Date, time, message text.
EVJ025E
INVALID VALUE "value" FOR keyword
Explanation: The parameter you have supplied is not
valid.
System action: None.
Operator response: Try again using the correct
parameters.
EVJ026E
MISSING PARAMETER parameter
Explanation: The parameter is required, but was
omitted.
System action: None.
Operator response: Try again using the correct
parameters.
EVJ029I
command ENCOUNTERED
UNEXPECTED EVENT event_name
Explanation: The indicated command was issued, but
the response received was not as desired. For example,
the command may have timed out, or the procedure
may have been canceled while waiting for a message.
Your gateway to the remote NetView is blocked, or the
remote system may be extremely busy. If the former,
you should resolve the gateway problem. If the latter
you should schedule your operations on this remote
NetView farther apart.
System action: None.
Destination: Domain ID, request parameters.
Explanation: The TWS Batch Command Processor is
starting.
EVJ010I
variable data
Operator response: Investigate the cause of the failure.
EVJ040I
PROCESSING COMMANDS
System action: None.
Explanation: This message is used internally to
transfer data between systems.
Operator response: None.
System action: None, this is a normal message.
EVJ041E
Operator response: None.
Destination: Date, time, message text.
POSITIONAL PARAMETER name
MUST BE SPECIFIED
Explanation: The parameter mentioned in the message
is required and must be specified.
System action: Batch command processing aborts and
128
System Automation for z/OS Messages and Codes:
EVJ042E • EVJ047I
the batch job ends with RC=16.
System action: Processing continues.
Operator response: Correct the EVJRYCMD command
and retry.
Operator response: None.
EVJ042E
PARAMETER name ERROR, VALUE
NOT NUMERIC
Explanation: The value specified in parameter name is
not numeric. The value must be a number.
System action: Batch command processing aborts and
the batch job ends with RC=16.
Operator response: Correct the EVJRYCMD command
and retry.
EVJ043E
PARAMETER name ERROR, information
Explanation: The value of the named parameter is
incorrect.
The variable name represents the parameter in error.
The variable information contains the detail of the
error.
System action: Batch command processing aborts and
the batch job ends with RC=16.
System programmer response: None.
EVJ046E
UNABLE TO OPEN PPI FOR
receiver_name
Explanation: An attempt to open the PPI receiver
named receiver_name failed. This message is followed by
EVJ047I that describes why the attempt to open failed.
System action: Command processing is aborted and
the batch job will terminate with return code 20.
Operator response: Contact your system programmer.
System programmer response: Check message
EVJ047I to find the probable cause of the error.
EVJ047I
dsiphone_error [, PPI reason ppi_error]
Explanation: This message provides details of the
NetView DSIPHONE error that caused processing to
fail. It also gives details of the PPI error reason if that is
feasible.
The DSIPHONE error responses are:
Operator response: Contact your system programmer.
v DSIPHONE called without arguments.
System programmer response: Ensure that the PPI
destination named is 1 to 8 characters in length and
consists of alphanumeric characters.
v Too many parameters for this request type.
EVJ044E
PARAMETER TRACE ERROR,
INVALID VALUE - SEE THE REXX
TRACE COMMAND
Explanation: Specification of the TRACE= parameter
requires a value consistent with the REXX Trace
command.
v Too few parameters for this request type.
v Invalid request type.
v REXX stem or variable name too long.
v REXX variable operation failed.
v PPI receiver name is too long.
v PPI request failed.
v Stem's .0 element invalid.
v Too many elements in stem.
System action: Batch command processing aborts and
the batch job ends with RC=16.
v First line of MLWTO not control line.
Operator response: Contact your system programmer.
v Argument 6 is not 'APPEND' or blank.
System programmer response: Check with your IBM
Support Center. Re-specify the TRACE= parameter with
the correct value.
v Invalid WAIT interval specified.
v PPI RECEIVE timed out.
v Invalid MLWTO line type attribute.
v Invalid MLWTO attribute length.
v Unable to obtain storage.
EVJ045I
OPENING PPI INTERFACE FROM
source TO destination
Explanation: Command Processing is about to send
commands to the SA z/OS PPI command processor.
This message is issued when the PPI interface is being
opened.
The variable source is the PPI Sender id used for this
batch job.
The variable destination is the PPI receiver name of
the command sever. It is specified with the
SERVER= parameter.
v Invalid attempt to call DSIPHONE from NetView.
v Invalid attempt to call DSIPHONE.
v Internal error.
v An unknown error occurred.
The PPI error responses are:
v The specified receiver is not active.
v The PPI is available.
v The receiver program is active.
v The receiver program is inactive.
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
129
EVJ048I • EVJ053I
v The receiver program is already active.
EVJ049E
v The receiver ECB is not zero.
v The request code is not defined.
v The program is not in Primary Addressing mode.
UNABLE TO SEND TO destination FOR
source / EVJ049E UNABLE TO RECEIVE
FROM destination
Explanation: PPI processing failed to send data from
the source to the destination PPI receivers, or receive
data from the destination PPI receiver.
v The program is not authorized.
v The PPI interface is not active.
The variable source is the PPI Sender Id for this
batch job.
v The ASCB address is not correct.
v The receiver program is not defined.
The variable destination is the PPI receiver name of
the command server and is specified with the
SERVER= parameter.
v No active SSI for PPI found.
v No data buffer in receiver buffer queue.
v Receiver buffer is not large enough.
v No NetView storage available.
v Buffer length is not valid.
v Receiver queue is full.
v ESTAE recovery cannot be established.
|
This message is followed by EVJ047I or INGPC028I to
describe the problem in more detail.
System action: Processing is aborted and the batch job
is terminated with return code 20.
v Sender or Receiver ID not valid.
Operator response: Contact your system programmer.
v Processing error has occurred.
System programmer response: Refer to the
information in the following EVJ047I message and take
any appropriate action.
v System abend occurred.
v User abend occurred.
v AIFR or the input length was not valid.
v Could not identify the data as a message.
v Incomplete multiline message was discarded.
v Illegal alert forwarding loop was detected.
v Specified target type does not support the data.
v User is not authorized.
v An unknown error occurred.
Numeric codes may also be present for either the
DSIPHONE code or the PPI code.
EVJ052E
PPI INTERFACE FAILED TO CLOSE
FOR source
Explanation: The PPI interface did not successfully
close after command processing was completed.
The variable source is both the PPI receiver name of
the batch job and the job name of the batch job.
System action: Command processing is aborted and
the batch job is terminated with return code 20.
Operator response: None.
Operator response: Contact your system programmer.
System programmer response: Possibly no action.
Check whether commands that were issued by the
batch job executed correctly on the NetView by
examining the NetView log.
System programmer response: For some of the PPI
error responses action can be taken to correct the error:
EVJ053I
System action: Command processing is aborted and
the batch job terminates with return code 20.
v “PPI receiver not defined” is usually due to an
incorrect SERVER= specification.
v “PPI interface not active” or “No active SSI” is
usually due to no NetView SSI subsystem having
started.
Most of the other reasons will require you to contact
your IBM Support Center.
EVJ048I
EXECUTING COMMAND
Explanation: Command processing is about to send a
command to SA z/OS for processing.
System action: Processing continues.
Operator response: None.
System programmer response: None.
130
System Automation for z/OS Messages and Codes:
BATCH COMMAND RECEIVED FROM
userid JOBNAME jobname
Explanation: An OPC batch command has been
received from a batch job and is to be executed on this
NetView.
The variable userid shows the user ID of the user
who submitted the batch job.
The variable jobname is the job name of the batch
job.
System action: The command specified in message
EVJ054I is processed.
Operator response: None.
System programmer response: None.
EVJ054I • EVJ062I
EVJ054I
BATCH COMMAND IS command-text
Explanation: An OPC batch command has been
received from a batch job and is to be executed on this
NetView. This message logs the command to be
executed.
The variable command-text shows the batch
command.
System action: The command is processed.
Operator response: None.
System programmer response: None.
EVJ055I
PIPE PPI FOR receiver FAILED.
RC=returncode - description
Explanation: A PIPE PPI command failed when
attempting to communicate with the receiver.
The variable returncode shows either the return code
from the PIPE command or the return code from the
PPI stage.
The variable description shows a description of the
error.
System action: The output from the current command
received from the batch job will not be sent to the batch
job. However, the command may have run successfully.
The batch job will probably time out or produce some
other error.
Operator response: For recoverable errors such as
errors with the receiver, resubmit the batch job if you
are allowed to rerun the failed batch job. For all other
errors notify your system programmer.
System programmer response: Report the error to
your service representative.
EVJ056E
Command return code nn greater than
MAXRC mm - Command Processing
Aborted.
Explanation: A command sent to the SA z/OS agent
for processing has executed and returned with a code
greater that the maximum acceptable return code.
The variable nn shows the return code from the
command.
The variable mm shows the maximum acceptable
return code from the MAXRC parameter of the
EVJRYCMD command.
System action: The batch interface will stop sending
commands to the SA z/OS Agent and will terminate.
The return code for the batch job step will be
determined by the HIGHRC parameter.
Operator response: For recoverable errors, such as
errors with the receiver, resubmit the batch job if you
are allowed to rerun the failed batch job. For all other
errors notify your system programmer.
user-defined situation, report the fault to your service
representative.
EVJ060I
Executing command for ADID=name
WSID=identifier OPNUM=nnn
IATIME=timestamp >> command_text
Explanation: A command has been received from
TWS and is to be executed on this NetView. This
message logs the command to be executed. Note that
the command might be truncated if it is too long.
The variable name shows the application description
identifier as defined in TWS.
The variable identifier shows the workstation
identifier.
The variable nnn shows the TWS operation number.
The variable timestamp shows the input arrival time
as determined by TWS.
The variable command_text shows the command.
System action: The command is processed.
Operator response: None.
System programmer response: None.
EVJ061I
Command for ADID=name
WSID=identifier OPNUM=nnn failed
IATIME=timestamp RC=nn
Explanation: A command received via the TWS
interface was executed but reported a non-zero return
code. See the preceding message EVJ060I for the
command in error.
The variable name shows the application description
identifier as defined in TWS.
The variable identifier shows the workstation
identifier.
The variable nnn shows the TWS operation number.
The variable timestamp shows the input arrival time
as determined by TWS.
The variable nn shows return code from the
command.
System action: None.
Operator response: None.
System programmer response: None.
EVJ062I
REQUEST for wsname adname opnum
iatime purged
Explanation: While performing a configuration
refresh, System automation detected that a deleted
resource was involved in TWS request. Since the
resource is no longer under control of SA z/OS the
request is removed from the internal control structure.
Variable wsname identifies the workstation name
involved.
System programmer response: If this is not a
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
131
EVJ063I • EVJ105I
Variable adname identifies the application name
involved as defined in TWS
Variable opnum specifies the operation number
Variable iatime specifies the input arrival time
assigned to the request.
System action: Processing continues.
Operator response: None.
EVJ063I
Command for ADID=name
WSID=identifier OPNUM=nnn
IATIME=timestamp finished.
ERRCODE=errcode
Explanation: A command received via the TWS
interface was executed and finished. See the preceding
message EVJ060I for command that was executed.
The variable name shows the application description
as defined in TWS.
The variable identifier shows the workstation
identifier.
The variable nnn shows the TWS operation number.
The variable timestamp shows the input arrival time
as determined by TWS.
The variable errcode shows the error code for the
operation if the operation is in error, or the return
code if the operation is complete.
EVJ102I
EVJ07001: PPI REQUEST nn FAILED,
RC=rc
Explanation: EVJ07001 was unable to complete a
NetView PPI request. See the NetView PPI manual for
more information on this request type and return code.
System action: TWS operation will be set to E status.
Operator response: Review error message in log.
System programmer response: Review error message
in log.
Destination: Request type and return code.
EVJ103I
EVJ07001: GETMAIN FOR WORKAREA
FAILED
Explanation: EVJ07001 was unable to do a GETMAIN
for work area storage.
System action: EVJ07001 will put the TWS operation
in E status.
Operator response: Report the problem to your
system programmer.
System programmer response: Review NetView
storage allocation and usage.
Destination: None.
System action: None.
EVJ104I
Operator response: None.
System programmer response: None.
Explanation: EVJ07001 has found the contents of the
operation description field to be invalid. Message
EVJ105I will list the actual error data.
EVJ100I
System action: EVJ07001 will put the TWS operation
in E status.
EVJ07001: ENTERING SA z/OS
TWS/OPC EXIT
Explanation: TWS has now called the EVJ07001 exit.
System action: None.
Operator response: Information message.
System programmer response: Information message.
EVJ07001: OPC BAD OPERDESC: data
Operator response: Inform TWS Scheduler of possible
definition error.
System programmer response: None.
Destination: TWS application name.
Destination: None.
EVJ105I
EVJ101I
Explanation: EVJ07001 has found this data to be
invalid.
EVJ07001: DATA SENT=data
EVJ07001: OPC DATA data
Explanation: This message logs the data sent to
NetView across the NetView PPI in the system log.
System action: EVJ07001 will put the TWS operation
in E status.
System action: None.
Operator response: Information message.
Operator response: Inform TWS Scheduler of possible
definition error.
System programmer response: Information message.
System programmer response: None.
Destination: Data passed.
Destination: Data.
132
System Automation for z/OS Messages and Codes:
EVJ106I • EVJ120I
EVJ106I
modname1: modname2 STATUS UPDATE
FAILED, RC=rc
Explanation: The module listed was unable to update
operations status using DRK/EQQUSINT.
System action: WTO error message is issued.
Operator response: Inform TWS schedulers and
system programmers.
System programmer response: Review system and
TWS/OPC message logs.
Destination: Issuing module and status update
module.
EVJ107I
EVJ07001: TWS/OPC FEATURE EXIT
ENDED
Explanation: EVJ07001 has successfully ended.
System action: None.
Operator response: Information message.
System programmer response: Information message.
Destination: None.
EVJ108I
module-name UNABLE TO LOAD
MODULE CNMCNETV
Explanation: This message is issued from the TWS
status change exit, (EQQUX007/DRKUX007), when it
cannot load the NetView PPI interface.
System action: Processing for this request halts. The
operation will be posted in error with a return code of
UNTV.
Operator response: Notify your system programmer.
System programmer response: This message most
likely indicates an installation error. You must make the
NetView PPI module accessible to TWS, either by
STEPLIB or putting the NetView load library,
CNMLINK, in LINKLST.
Destination: Issuing module name.
EVJ109I
EVJ07001: LEAVING SA Z/OS
TWS/OPC EXIT
Explanation: EVJ07001 has successfully ended.
Operator response: Information message.
System programmer response: Information message.
Destination: Module name and successful command
name.
EVJ110I
modulename UNABLE TO LOAD
MODULE target-module-name
Explanation: This message is issued from an TWS
command processor, which is unable to find or load an
TWS interface module.
System action: Processing for this request halts.
Operator response: Notify your system programmer.
System programmer response: This message most
likely indicates an installation error. You must make the
TWS interface module accessible to NetView, either by
STEPLIB (preferred) or by putting the TWS load library
in LINKLST.
Destination: Issuing module name and target module
name.
EVJ120I
applid iatime opnum job status wsname
errcode abcode usrcode job# stepname
Explanation: A TWS operation has been put into TWS
error status or has been reset from TWS error status.
This causes a Status Display Facility update and an
NMC update to occur. For an operation changing to
error status the update will add an entry to SDF and
NMC while an operation changing from error status
will remove an entry from SDF and NMC. SDF entries
are added to the 'OPC Automation Application in
Error' panel (OPCERR). When enabled, alerting for the
specified event notification targets will occur.
The variable applid shows the TWS application
name.
The variable iatime shows the TWS input arrival
time.
The variable opnum shows the TWS operation
number.
The variable job shows the TWS job name.
The variable status shows the TWS status.
The variable wsname shows the TWS workstation for
this operation.
The variable errcode shows the TWS error code.
The variable abcode shows the TWS abend code.
The variable usrcode shows the TWS user code.
The variable job# shows the TWS job number.
The variable stepname shows the TWS job's
stepname.
System action: SDF and NMC are updated according
to the data displayed in the message and when
enabled, an alert for event notification targets will be
generated.
Operator response: None.
System programmer response: None.
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
133
EVJ121I • EVJ203I
EVJ121I
Application jobname opno NOT RESET
BECAUSE TIME LIMIT EXCEEDED
Explanation: This operation was found to be in error
status in OPC with error code, UNTV, indicating that
the NetView interface was unavailable at the time it
came READY. Now that the interface is available, the
status was not reset because more time has elapsed
since the failure than is permitted by the OPRESET
value in the control file (see ENVIRON OPCAO).
EVJ124I
parm1 parm2 parm3 parm4 parm5
Explanation: This message follows message EVJ123I
and specifies up to five parameter names that are in
error.
System action: None.
Operator response: Correct the incorrect parameter/s
and reissue the command.
System programmer response: None.
System action: Operation remains in error status.
Operator response: Manually reset operation when
appropriate. OPCACMD may be used to do this.
EVJ125I
System programmer response: Determine whether the
OPRESET value should be increased.
Explanation: This message is issued when INGOPC
cannot resolve the resource specification to an active
controller or to an available tracker.
Destination: Application name, Job name, Operation
number.
EVJ122E
UNKNOWN TWS API SEGMENT
segment ENCOUNTERED
Explanation: When the INGTWS command is
decoding data returned from TWS via the API, an
unknown segment name was encountered.
The variable segment shows the name of the
segment that is unknown to the command.
System action: Data from the TWS API is not
successfully decoded. The command will present data
that has been decoded up to the point of the failure.
subsystem IS NOT AN ACTIVE
CONTROLLER OR A TRACKER
System action: None.
Operator response: Correct the incorrect parameter (or
parameters) and reissue the command. Make sure that
the resource specification will resolve to an active
Available Controller or an Available Tracker.
System programmer response: None.
EVJ201I
EVJTOPPI: TASK IS ACTIVE
Explanation: NetView optional subtask initialization
has completed successfully.
System action: None.
Operator response: Notify your system programmer.
Operator response: Information message.
System programmer response: Report the error to
your service representative.
System programmer response: Information message.
EVJ123I
[DEFAULT SAFE|UPDATE
PARAMETER] INVALID
MODIFICATION PARAMETERS
FOLLOW:
Explanation: For an INGTWS REQ=MOD request an
invalid update parameter was encountered that the
command could not process. The source of the
parameter in error is either the Default Safe for the
DEFAULT SAFE version of the message or the
UPDATE command parameter for the UPDATE
PARAMETER version of the message. Message EVJ124I
follows this message with a list of up to five parameter
names that are in error.
System action: Processing stops.
Destination: None.
EVJ202I
EVJTOPPI: PPI TO EVJTOPPI
INITIALIZED
Explanation: NetView optional subtask has initialized
its NetView PPI queue.
System action: None.
Operator response: Information message.
System programmer response: Information message.
Destination: None.
EVJ203I
EVJTOPPI: PPI TO EVJTOPPI
DEACTIVATED
Operator response: Correct the incorrect parameter
and reissue the command.
Explanation: NetView optional subtask has
deactivated the NetView PPI queue.
System programmer response: None.
System action: None.
Operator response: Information message.
System programmer response: Information message.
Destination: None.
134
System Automation for z/OS Messages and Codes:
EVJ204I • EVJ212I
EVJ204I
EVJTOPPI: TASK IS TERMINATED
Explanation: NetView optional subtask has terminated
successfully.
System action: None.
Operator response: Information message.
System programmer response: Information message.
Destination: None.
EVJ205E
EVJTOPPI: PPI REQUEST nn FAILED,
RC=rc
Explanation: EVJTOPPI was unable to complete a
NetView PPI request. Refer to the NetView Application
Programming Guide: PPI for more information on the
request type and return code.
EVJ208I
EVJTOPPI: DSIFRE FAILED FOR
QUEUED STORAGE
Explanation: EVJTOPPI was not able to FREE queued
storage before terminating.
System action: None.
Operator response: Report problem to system
programmer.
System programmer response: Review error.
Destination: None.
EVJ209I
EVJTOPPI: DSIGET FAILED FOR USER
STORAGE
Explanation: EVJTOPPI was not able to GET user
storage at initialization.
System action: None.
System action: None.
Operator response: Notify your system programmer.
Operator response: Report problem to system
programmer.
System programmer response: Review log for
messages that may indicate the reason for the failure. A
possible reason is that NetView is being shutdown.
Note: The OPC operation status will be unchanged.
User intervention may be required.
Destination: Request type and return code.
EVJ206I
EVJTOPPI: PPI DATA FROM EVJTOPPI
DISCARDED
Explanation: EVJTOPPI received request data from a
non-OPC subsystem. The data is logged in the NetView
log, but is not passed to EVJESPVY.
System action: None.
Operator response: Informational. Review message
EVJ214I for data.
System programmer response: Review NetView
storage allocation and utilization.
Destination: None.
EVJ210I
EVJTOPPI: DSILCS FAILED TRYING
TO GET A SWB
Explanation: EVJTOPPI was not able to GET a service
work block.
System action: None.
Operator response: Report problem to system
programmer.
System programmer response: Review NetView
storage allocation and utilization.
Destination: None.
System programmer response: Informational.
Destination: None.
EVJ207I
EVJTOPPI: DSIFRE FAILED FOR USER
STORAGE
EVJ211I
EVJTOPPI: ENQ ERROR
Explanation: EVJTOPPI was not able to perform an
ENQUEUE.
System action: None.
Explanation: EVJTOPPI was not able to FREE user
storage before terminating.
Operator response: Report problem to system
programmer.
System action: None.
System programmer response: Check for multiple
EVJTOPPI tasks or possible deadlock condition.
Operator response: Report problem to system
programmer.
Destination: None.
System programmer response: Review error.
Destination: None.
EVJ212I
EVJTOPPI: DEQ ERROR
Explanation: EVJTOPPI was not able to perform a
dequeue.
System action: None.
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
135
EVJ213I • EVJ424E
Operator response: Report problem to system
programmer.
System programmer response: Check for multiple
EVJTOPPI tasks started, or a deadlock condition.
Destination: None.
EVJ213I
EVJTOPPI: DSILCS FAILED TRYING
TO FREE SWB
Explanation: EVJTOPPI was not able to FREE a
service work block.
System action: None.
Operator response: Report problem to system
programmer.
System programmer response: Contact support center.
EVJ303I
cmdname: KEYWORD ERROR,
KEYWORD(keyword) DATA(data)
Explanation: This message gives the keywords and
data that are invalid when this command was invoked.
Operator response: Review parameters used to invoke
the command.
System programmer response: Modify parameters
accordingly.
Destination: Command name, keyword and data.
EVJ410I
ADID JOBNAME WS OPNO S ERRC
IA OPTEXT
Explanation: This is the first line of a multiple-line
message. It displays the titles for message EVJ411I.
Destination: None.
EVJ411I
EVJ214I
EVJTOPPI: xxxxxxxxxxxxxxxxxxxxxxxxx
Explanation: This message is sent to the NetView log
to document the discarded data.
applid jobname workstation opid status
errcode IA_time text.
Explanation: This is the second line of a multiple-line
message. It displays the corresponding information
from message EVJ410.
System action: None.
Operator response: Informational.
EVJ412I
System programmer response: Informational.
Explanation: This message indicates the end of the
data.
Destination: Data.
EVJ300I
EVJSAOPS: DRK/EQQUSINT POST
WAS SUCCESSFUL
EVJ413I
END OF REQUEST.
UNABLE TO FIND DATA FOR
REQUESTED LIST
System action: None.
Explanation: This message is issued from OPCALIST
or OPCACMD and indicates that no application or
operation in the current plan meets the combination of
input parameters specified.
Operator response: Informational.
System action: Processing for this request halts.
System programmer response: Informational.
Operator response: Correct the input to the
OPCALIST command or the OPCACMD panel. If it is
not obvious which parameter is error specify fewer
parameters and issue the command again, so that OPC
may return a list of valid application occurrences in the
current plan. If there are none go to the OPC dialog
under ISPF and add an occurrence.
Explanation: Post to OPC using DRK/EQQUSINT
was successful.
Destination: None.
EVJ302I
cmdname: INVALID KEYWORD
SUPPLIED
Explanation: Invalid KEYWORD was issued when
invoking this command. Message EVJ303I will follow
listing the KEYWORD and DATA in error.
Operator response: Correct parameters used to invoke
the command.
System programmer response: Correct the command
and retry.
Destination: Command name.
System programmer response: None.
Destination: None.
EVJ424E
COULD NOT LOCATE OPC
CONTROLLER - reason
Explanation: The OPC Controller as defined in the
OPCA PCS automation control file statement could not
be located in either the local system or any of the
systems in the local sysplex.
The reason variable (optional) shows the reason code.
System action: Processing is terminated.
136
System Automation for z/OS Messages and Codes:
EVJ425I • S999
Operator response: Investigate the cause of the failure.
Further diagnostic messages may be available in the
NetView log. Possible causes include:
v An error in the OPCA PCS statement in the
automation control file.
v The OPCA PCS defines the controller to be running
on another system.
v No OPC controller is running (UP status in
SA z/OS) where specified.
EVJ425I
NO SRSTAT ENTRY FOUND IN OPCA
PCS DEFINITION FOR OPC
AUTOMATION.
Explanation: The SRSTAT entry for the TWS
Automation is not set.
OPCA PCS,
SRSTAT=YES|NO|ALL
JOBNAME
MVS Job Name
WS
OPC Workstation
OPNO OPC Operation Number
OPC Status
S
ERRC
OPC Error Return Code
®
OPC Input Arrival Time
IA
OPTEXT
OPC Operations Text
EVJ431E
adid
jobname ws opno s errc ia optext
Explanation: This is the continuation of a multiple-line
message begun with EVJ430I.
Destination: The inserts are as follows:
OPC Application ID
System action: None.
adid
Operator response: Report to your system
programmer that the OPCA PCS statement in the
automation control file for setting special resources
status was not defined. This entry allows TWS
Automation to set OPC special resources for the named
job name in the OPCA OPCSRSTAT definition.
jobname
MVS Job Name
System programmer response: Refer to IBM Tivoli
System Automation for z/OS TWS Automation
Programmer's and Operator's Reference Guide for further
information.
EVJ430I
ADID JOBNAME WS OPNO S ERRC
IA OPTEXT
Explanation: This is the first line of a multiple-line
message. It displays the titles for message EVJ431E, as
follows:
ADID
ws
OPC Workstation
opno
OPC Operation Number
s
OPC Status
errc
OPC Error Return Code
ia
OPC Input Arrival Time
optext
OPC Operations Text
EVJ440I
date day WORK|FREE.
Explanation: This message tells you whether today is
a work day or a free day in the OPC calendar. The date
is shown in the format mm/dd/yyyy.
OPC Application ID
Codes Posted to TWS by TWS Automation
OAUT
Explanation: Indicates that the EQQUXSAZ exit was
not able to pass the request to the local SA z/OS using
the NetView PPI.
Rnnn
Explanation: The command passed to SA z/OS for
execution failed. nnn is the return code from the
command. RXXX is used when the return code is >999.
S998
Explanation: Job not defined to any active system in
sysplex. A request to run an operation from TWS was
received by TWS Automation. The control file mapped
the workstation (NVxx) to SYSPLEX. All active
SA z/OS domains in the local sysplex were queried
but no definition was found for the job name specified
in the TWS request.
This may be the result of one or more systems (or their
SA z/OS) being inactive or it may be a definition error.
If all systems where the job is defined are offline then
the operation will be retried when SA z/OS gateway
connectivity is re-established.
S999
Explanation: Gateway to remote NetView was
unavailable. A request to run an operation from TWS
was received by the automation platform (NetView)
address space, but it was destined for another NetView
domain. An attempt was made to forward this
operation to that domain, designated by the
Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation)
137
UNTV • U010
workstation name in the request, but this attempt
failed. Either the gateway from the local system to the
remote domain was down, or no response was received
from the remote system after waiting for one minute.
U007
Explanation: Execution of the command is rejected by
the installation exit AOFEXC20.
UNTV
U008
Explanation: NetView unavailable. The TWS exit in
TWS was unable to transmit this request to the
automation platform (NetView) address space. Either
the NetView in the system running the TWS/ESA
Controller was down at the time this request was
initiated or the NetView SSI was down.
Explanation: Timeout condition occurred while
processing the command.
U009
Explanation: An invalid parameter was found while
processing the command passed from TWS.
U001
Explanation: Invalid status for the subsystem. The
subsystem failed to start or terminate in the interval, or
has changed to an unexpected status.
U002
Explanation: Invalid flag combination detected. This
may indicate autotask definition errors. Review the
NetView log for additional information.
U003
Explanation: Missing or incorrect TWS Automation
definitions in the Automation control file or errors
occurred reading the status file or executing an
SA z/OS command such as INGREQ. Review the TWS
policy definitions and check the netlog for additional
messages.
U004
Explanation: Configuration error: The EVTOPER is
not defined. This task is used to process status change
notifications from the automation manager.
U005
Explanation: Sequence Error. This is usually an
indication of two or more requests in progress for the
same subsystem. Review the NetView log for
additional information.
U006
Explanation: Configuration Error. An Automation
Configuration File statement of the type OPCA
DOMAINID,CODE= specifies SYSPLEX. The TWS
Controller is not running in a system where SA z/OS
Release 3 or later is installed. Use of the SYSPLEX
keyword on this statement requires SA z/OS Release 3
or later to be installed where the TWS Controller runs.
138
System Automation for z/OS Messages and Codes:
U010
Explanation: The completion information provided by
exit AOFEX20 is incorrect. See the Netlog for more
details on the reasons.
Chapter 7. Messages HSAH001I to HSAL6999I
HSAH001I
HSAET32 SERVICES verb COMPLETE.
Explanation: Processing of the command completed
successfully.
The variable verb shows the name of the HSAET32
command verb that completed successfully.
System action: HSAET service processing continues as
requested by the command verb.
Operator response: None.
System programmer response: None.
HSAH002I
INVALID HSAET32 SERVICES
REQUEST request.
Explanation: The identified HSAET32 command is not
valid.
The variable request shows the name of the
HSAET32 command that is not valid.
System action: None.
Operator response: Correct and reissue the command
as necessary. Valid services are
REBUILD,START,STATUS,DISABLE,ENABLE.
System programmer response: None.
HSAH003I
HSAET32 SERVICES REQUEST
FAILED, RC=rc, REASON rsn.
Explanation: An error occurred during an attempt to
process a valid HSAET32 command.
The variable rc shows the return code that was
issued.
The variable rsn shows the reason code that was
issued.
System action: None.
Operator response: Issue an HSAET32 STATUS
command and verify that the status reported by
message HSAH004I is as expected. Then reissue the
command as appropriate. If the problem persists, notify
your system programmer.
System programmer response: This message is issued
with return code 8 and reason code 20 (14x) as a result
of an HSAET32 START command if ET32 services were
started previously (usually done during NetView
initialization). If other problems occurred, contact your
IBM Support Center.
v The variable status shows the current status of ET32
services. The following values can occur:
INACTIVE
HSAET32 services were not initialized and
are unavailable.
ENABLED
HSAET32 services were initialized and are
available.
DISABLED
HSAET32 services were initialized but were
disabled from use.
System action: None.
Operator response: Verify that the status indicated is
as currently required.
System programmer response: If the status value is
INACTIVE, SA z/OS Startup HSAET32 initialization is
in progress. Message HSAH001I must follow, indicating
that HSAET32 SERVICES START is complete.
If this is not the case, check the netlog for additional
messages indicating HSAET32 command problems,
such as insufficient NetView operator command
authorization. After the problem is corrected you can
try to restart the HSAET32 services manually, issuing
the IBM service command HSAET32 START, or recycle
SA z/OS.
HSAL1071E CANNOT REGISTER OMVS
SHUTDOWN OPTIONS, ERRNO=code1,
ERRNO2=code2.
Explanation: The automation manager called the
C-function __shutdown_registration, which failed.
The variable code1 is the error return code.
The variable code2 is the error return code.
System action: The SA z/OS automation manager
continues with initialization.
Operator response: None.
System programmer response: Examine the error
codes to determine why the function call failed. In most
cases registration for OMVS shutdown fails because the
automation manager does not have superuser or
equivalent authority. Alternatively you may want to
give the automation manager read permission to the
BPX.SHUTDOWN facility class profile.
HSAL1072I
HSAH004I
HSAET32 SERVICES ARE status.
Explanation:
© Copyright IBM Corp. 1996, 2014
THE AUTOMATION MANAGER IS
BLOCKING OMVS SHUTDOWN.
Explanation: If an OMVS shutdown command is in
progress the automation manager will block the
139
HSAL1081I • HSAL1091E
shutdown until the automation manager is terminated
with a STOP,DEFER or a manual STOP command.
This is because the parmlib option BLOCKOMVS is set
to YES.
System action: The automation manager continues
processing.
Operator response: None.
System programmer response: None.
HSAL1081I
SWITCHING COMMUNICATION
FROM MQ TO XCF IS action.
Explanation: The WebSphere MQ subsystem was
stopped or an error occurred in WebSphere MQ. The
automation manager runs on the last system within the
XCF group. The automation manager continues
running with XCF communication only rather than
terminating and thereby forcing a takeover.
v The variable action may contain one of the following
values:
STARTED
The switch from WebSphere MQ to XCF
started.
COMPLETED
The switch from WebSphere MQ to XCF
completed.
HSAL1083I
AUTOMATION MANAGER HAS
CREATED THE INITIAL POSIX
THREAD WITH PID @1
Explanation: The automation manager has
successfully created the initial POSIX thread. The
OMVS kernel has assigned the specified process ID
(PID) to the initial POSIX thread. If you do not see this
message then the automation manager is still waiting
for OMVS to come up. If the automation manager is
running with superuser authority, the initial POSIX
thread will be created before OMVS initialization is
completed. Otherwise the automation manager waits
until OMVS initialization is completed and message
BPXI004I comes up. This may require JES to be up.
System action: None.
Operator response: None.
System programmer response: None.
HSAL1091E INTERNAL ERROR TYPE error type
DETECTED. DIAGNOSTIC INFO MAY
FOLLOW: P1=parm1 P2=parm2 P3=parm3
Explanation: An internal error was found. Up to three
additional diagnostic information fields may be
provided, depending on the error type.
v The variable parm1 shows what could not be
processed.
System action: The automation manager continues
processing, but uses XCF for the communication
between the automation agent and the automation
manager.
v The variable parm2 shows the value of the command,
action or termination type.
Operator response: None.
v The variable error type shows a decimal number that
defines the type of the error. The following values
can occur:
System programmer response: None.
HSAL1082I
SWITCHING COMMUNICATION
FROM XCF TO MQ IS action
Explanation: The automation manager was started
with XCF communication. WebSphere MQ is available
and the automation manager switches from XCF to
WebSphere MQ communication.
v The variable parm3 (optional) shows the first
parameter of the command.
101
The thread manager got an invalid
command, action or termination type that
cannot be processed.
102
Cannot create thread specific data object for
the main thread.
103
The class HsaSemaphore supports event and
mutex semaphores. A method was applied
for a semaphore type, that does not support
this method.
v The variable action may contain one of the following
values:
STARTED
The switch from XCF to WebSphere MQ
started.
COMPLETED
The switch from XCF to WebSphere MQ
completed.
System action: The automation manager continues
processing, using WebSphere MQ communication.
Operator response: None.
System programmer response: None.
140
System Automation for z/OS Messages and Codes:
The variable parm1 shows the semaphore
name.
104
The single MTIB object has not yet been
created.
105
The single MTIB object must not be created
with a MTIBptr=zero.
106
The factory tries to create a derived request
handler but the function doCreateHandler
returns zero.
HSAL1092E
The variable parm1 shows the handler
name.
107
It was attempted to add a factory into the
factory registry. However, a factory with the
same name has already been added.
v The variable error type shows a decimal number that
defines the type of the error. The following values
can occur:
202
The variable parm1 shows the factory
name.
108
109
A null pointer was detected. Processing
stops.
It was attempted to find a factory within the
factory registry. However, the factory name
is not contained in the registry.
The variable parm1 shows the maximum
retry count of threads.
203
A thread has been terminated and a restart
is either not possible or not allowed.
204
The default implementation of a virtual
function was called unexpectedly.
The variable parm1 shows the search
argument (=factory name).
110
It was attempted to access the factory
registry. However, the factory registry has
not yet been created and the static pointer
to it is zero.
111
Invalid attempt to reply to a RPC Handle
that does NOT have the response flag ON.
112
Dtor of Request Handler Factory detects
that number of handlers is not zero.
If specified the variable parm1 shows the
current timer.
205
An attempt was made to add a thread with
a duplicate thread name to the Registry.
206
The system tried to find a collection class
element but the given key (=thread name)
could not be found.
207
Timer thread call handleExpiredTimer() after
control was returned the timer has not been
reset correctly, for example, previous timer
>= new timer.
The variable parm1 shows the factory
name.
The variable parm1 shows the previous
timer specified.
The variable parm2 shows the number of
handlers.
The variable parm3 shows the
ivCtorError.
113
The thread manager does not support to
restart a thread after a thread has been
terminated.
The variable parm2 shows the new timer
specified.
Request Handler Factory attempts to create
a handler but the factory error code
ivCtorError is not zero.
This exception is used if a thread has
received a request of class HsaRequest with
a request type that the function
handleRequest cannot process.
The variable parm1 shows the factory
name.
The variable parm1 shows the request
type.
The variable parm2 shows the
ivCtorError.
System action: The SA z/OS automation manager
terminates.
208
209
Function completeRequest() attempted to
send a request back to the creator thread.
However, the thread name is NULL.
211
LogonId not yet set or not valid.
The variable parm1 shows the logonID
that is not valid.
Operator response: None.
System programmer response: Contact your IBM
Support Center.
HSAL1092E INTERNAL ERROR TYPE error type
WITHIN THREAD thread name
DETECTED. DIAGNOSTIC INFO MAY
FOLLOW: P1=parm1 P2=parm2
Explanation: An internal error was detected. Up to
two additional diagnostic information fields may be
provided, depending on the type of the error.
v The variable thread name shows the name of the
thread where the error occurred.
251
The program detected an internal error that
probably leads to thread termination.
252
The program detected an error that leads to
thread termination and takeover. Examine
other messages that may have been issued
together with this message, for example,
INGY110, to determine the cause of the
error.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: For error type 252 try
Chapter 7. Messages HSAH001I to HSAL6999I
141
HSAL1093E • HSAL1096I
to fix the problem. For all other error types, contact
your IBM Support Center.
HSAL1093E COMMUNICATION OR SYSTEM
SERVICE FAILED, ERROR TYPE=error
type DIAGNOSTIC INFO MAY
FOLLOW: P1=parm1 P2=parm2 P3=parm3
P4=parm4 P5=parm5
Explanation: A system error was detected. Up to five
additional diagnostic information fields may be
provided, depending on the type of the error.
v The variable error type shows a decimal number that
defines the type of the error. The following values
can occur:
301
A z/OS UNIX pthread service failed.
The variable parm1 shows the return
code.
The variable parm2 shows the error
number.
The variable parm3 shows the pthread
service.
The variable parm4 shows the current
thread.
The variable parm5 shows the semaphore
name
302
An attempt to get storage failed.
The variable parm1 shows the amount of
storage in bytes.
303
An attempt to perform an MVS system
service failed.
HSAL1094I
THREAD thread name HAS RECEIVED
A Z/OS UNIXSIGNAL signal.
Explanation: The signal handler got control due to a
z/OS UNIX signal. Any received z/OS UNIX signal
that a signal handler was registered for will terminate
the automation manager.
The variable thread name shows the name of the
thread that received the signal.
The variable signal shows the z/OS UNIX signal.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: Analyze the z/OS
UNIX signal. If necessary, contact your IBM Support
Center.
HSAL1095I
SUSPENDED THREAD thread name
HAS BEEN INTERRUPTED DUE TO A
STOP REQUEST.
Explanation: The threads have been suspended, for
example, during CONFIG load or REFRESH.
The variable thread name shows the name of the
thread where the error occurred.
System action: The SA z/OS automation manager
terminates abnormally.
Operator response: None.
The variable parm2 shows the return
code of the service.
System programmer response: None.
The variable parm3 shows the current
thread.
HSAL1096I
The variable parm5 (optional) shows the
API reason code.
An attempt to perform a Communication
Service failed.
The variable parm1 shows the name of
the HSAAPICO service.
The variable parm2 shows the return
code of the assembler stub.
The variable parm3 shows the
communication return code of the
service.
The variable parm4 (optional) shows the
name of the current thread.
System action: The SA z/OS automation manager
terminates.
142
System programmer response: Contact your IBM
Support Center.
The variable parm1 shows the name of
the HSAAPIMV service.
The variable parm4 (optional) shows the
API return code.
304
Operator response: None
System Automation for z/OS Messages and Codes:
AUTOMATION MANAGER
TERMINATION IN PROGRESS DUE
TO THREAD TERMINATION OR
EXCEPTION BY THREAD thread name
Explanation: A thread of the automation manager
ends abnormally. Analyze the error message
HSAL1093E or HSAL1904I issued with this message.
The variable thread name shows the name of the
thread where the error occurred.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: None.
HSAL1101I • HSAL1105E
HSAL1101I
DIAGINFO SNAPSHOT dsn HAS BEEN
CREATED
Explanation: A snapshot of all in-storage objects (state
image queue) maintained by the automation manager
has been written into the named data set.
The variable dsn shows the name of the data set that
contains the snapshot.
System action: None.
Operator response: None.
System programmer response: None.
HSAL1102I
DIAGINFO RECORDING INTO dsn
HAS BEEN STARTED
Explanation: The automation manager has started
recording all received workitems into the named data
set. This includes writing the current state image queue
into the data set.
The variable dsn shows the name of the data set.
System action: None.
Operator response: None.
System programmer response: None.
HSAL1103I
DIAGINFO RECORDING INTO dsn
HAS BEEN COMPLETED
Explanation: The automation manager has stopped
recording all received workitems into the named data
set.
The variable dsn shows the name of the data set.
System action: None.
Operator response: None.
System programmer response: None.
HSAL1105E IO OPERATION OF THE TAKEOVER
FILE FAILED. REASON: diag_info.
Explanation: The automation manager failed to access
or use the takeover file. The variable diag_info contains
further details.
diag_info = "DSN=xxxxx: ALLOC ERROR nnnn RC=rr RSN=ssss"
The automation manager tried to allocate or deallocate
the takeover file xxxxx. If a dynalloc error occurs the
variable diag_info provides an error code and a dynalloc
return and reason code.
Meaning of alloc or dealloc error codes:
n008 invalid dataset or member or ddname
n012 dynalloc error
n016 open error
n020 internal error
where n=1 means allocate and n=2 means deallocate.
Example:
diag_info = "ALLOC ERROR 1012 RC=4 RSN=1056"
means the allocation of the takeover file failed because
the takeover file is already open.
For more details about the dynalloc return and reason
code refer to the chapter 'Interpreting DYNALLOC
Return Codes' in MVS Authorized Assembler Services
Guide.
For other types of diag_info see the following
description:
System programmer response: None.
The automation manager tried to write or update the
takeover file. A file operation function failed.
HSAL1104E DIAGINFO RECORDING INTO dsn
HAS FAILED. REASON: reason
v The variable DSN is the name of the takeover file.
Explanation: The automation manager detected an
error while recording the received workitems into the
named data set. The cause of the error is indicated by
the reason code.
The variable dsn shows the name of the data set.
The variable reason shows the cause of the error.
System action: None.
Operator response: Check logs for other messages
associated with this event and data set.
If the data set experienced an out-of-space condition,
consider increasing its size.
Restart the recording.
If the error cannot be corrected, contact your IBM
Support Center.
v The variable diag_info provides the following
information about the error:
C library function
The file operation function that failed, for
example, fopen.
C library error code
The error code issued by the file operation
function (errno).
C library error message
The error message text provided by the
failing file operation function.
For more details about errno for C/C++ library
functions, see z/OS XL C/C++ Library Reference.
System action: The automation manager continues
running.
Chapter 7. Messages HSAH001I to HSAL6999I
143
HSAL1106I • HSAL1111I
Operator response: Check for I/O error messages and
notify your system programmer.
System programmer response: Perform a cold or
warm start. Note that the automation manager must not
perform a hot-start or takeover, because the takeover
file may be damaged or contain old data.
HSAL1106I
MQ OPERATION ON STATE QUEUE
FAILED. REASON: reason.
Explanation: An error occurred while accessing the
MQ state queue.
The variable reason contains internal debugging
information and the MQ action performed.
System action: The automation manager stops
updating the MQ state queue but continues to maintain
the resource status in-storage and in the Takeover file.
Operator response: If message HSAL1109I is
previously issued, stop the MQ manager. This is
necessary to avoid message flooding because the
automation manager attempts to access the MQ State
queue periodically.
HSAL1109I
REFRESH OF AUTOMATION
MANAGER DATA TO MQ STATE
QUEUE STARTED
Explanation: The automation manager started
refreshing the MQ State queue with the in-storage data
maintained for each resource. This process consists of
the following two steps:
1. Purging the MQSeries State queue
2. Updating the MQSeries State queue with the
resource data
System action: None.
Operator response: None.
System programmer response: None.
HSAL1110I
R15 VALUE = rc REASON CODE = rs
RBA = rba LAST OP = lastop EXPECTED
RECORD SIZE = rsize REPORTED IO
RESULT = asize
Explanation: The automation manager has had a
VSAM I/O error.
System programmer response: Examine the syslog for
additional messages giving more details about the
cause of the error.
The variable rc shows the VSAM return code
HSAL1107I
The variable lastop shows the last I/O operation
executed.
REFRESH OF TAKEOVER FILE
DSN=dataset_name WITH CURRENT
AUTOMATION.
Explanation: The automation manager starts updating
the takeover file with the in-storage data maintained
for each resource. The first step is erasing the current
data in the takeover file. The second step is writing the
in-storage data into the takeover file.
The variable dataset_name is the name of the
takeover file.
System action: None.
Operator response: None.
System programmer response: None.
HSAL1108I
REFRESH OF TAKEOVER FILE
DSN=dataset_name COMPLETED.
Explanation: The automation manager has completed
writing the in-storage resource data to the takeover file.
The content of the takeover file is now identical with
the in-storage resource data.
The variable dataset_name is the name of the
takeover file.
System action: None.
Operator response: None.
System programmer response: None.
144
System Automation for z/OS Messages and Codes:
The variable rs shows the VSAM reason code.
The variable rba shows the VSAM relative byte
address.
The variable rsize shows the expected number of
bytes to be read in the I/O operation.
The variable asize shows the actual number of bytes
read in the I/O operation.
System action: Additional error message will be
issued.
Operator response: Contact your system programmer.
System programmer response: Contact IBM for
support.
HSAL1111I
DISABLING OF TAKEOVER FILE
DSN=dataset_name COMPLETED.
Explanation: The automation manager has freed the
takeover file and stopped writing to it.
The variable dataset_name is the name of the
takeover file.
System action: None.
Operator response: None.
System programmer response: None.
Classes: None.
HSAL1113I • HSAL1402E
HSAL1113I
WORKITEM EXPIRED: thread_name
DATE:exp_date TIME:exp_time
SIG:wi_signature
Explanation: The workitem has passed its expiry time.
The variable thread_name is the name of the thread.
The variable exp_date is the expiry date of the
workitem.
The variable exp_time is the expiry time of the
workitem.
The variable wi_signature is the workitem signature.
System action: None.
Operator response: Notify your system programmer.
System programmer response: Try to determine
reason for expiry, for example, high system or
automation manager activity. Examine the netlog for
additional information.
HSAL1300E TIMER REQUEST IS INVALID: RC=rc,
TYPE=type, CREATOR=creator
Explanation: The validation of an internal timer
request failed with a return code.
System action: The override file is marked
unavailable. All requests querying or manipulating any
overrides are rejected. Existing base schedules are still
working as defined in the customization dialogs.
Operator response: Notify your system programmer.
System programmer response: Analyze the function
code by referring to the OS/390 LE environment
STDIO.H file. The errorcode can be analyzed by
referring to OS/390 DFSMS Macroinstructions for Data
Sets using the return and reason codes from the error
code. If the problem is solved, start a secondary
automation manager and initiate a takeover. If you
cannot resolve the problem contact your IBM Support
Center.
Module: HSACMSST
HSAL1401E TIMER REQUEST FAILED. RC=rc,
ORIGINATOR=name, REQUEST=req.
Explanation: A timer request has been returned with
an unexpected return code to the LE component that is
responsible for schedules.
The variable rc shows the return code that was
issued.
The variable rc shows the value of the return code.
The variable name shows the name of the originator.
The variable type shows the type of the request.
The variable req shows the name of the request.
The variable creator shows the creator or the request.
System action: The request is rejected.
System action: The request is ignored. This may lead
to an unexpected behaviour of the affected schedule.
Operator response: None.
Operator response: Notify your system programmer.
System programmer response: None.
System programmer response: Contact your IBM
Support Center.
Module: HSACMTMR
Module: HSAHNDLS
HSAL1301E INVALID REQUEST RECEIVED:
TYPE=type, CREATOR=creator.
Explanation: An LE component received a request of a
type that could not be processed.
The variable type shows the type of the request.
The variable creator shows the creator or the request.
System action: The request is rejected.
Operator response: Contact your IBM Support Center.
HSAL1402E WORKITEM COULD NOT BE
QUEUED. RC=rc.
Explanation: The LE component responsible for
schedules could not inform the component managing
the resources about the begin or the end of a service
period.
The variable rc shows the return code that was
issued.
Module: HSACMTMR , HSAHNDLS
System action: Processing continues. However, this
may lead to an unexpected behaviour of the affected
resource(s).
HSAL1400E OVERRIDE FILE NOT AVAILABLE.
FUNC=function, CODE=errorcode.
Operator response: Initiate® a takeover to a secondary
automation manager. If the problem persists notify
your system programmer.
System programmer response: None.
Explanation:
The variable function shows the function that could
not be performed.
System programmer response: Contact your IBM
Support Center.
Module: HSACMSST, HSACMTMR
The variable errorcode shows the value of the error
code that was issued (return code bytes 1-4 and
reason code bytes 5-8).
Chapter 7. Messages HSAH001I to HSAL6999I
145
HSAL1403I • HSAL6010A
HSAL1403I
A TIMER EXPIRED FOR resource THAT
IS NO LONGER AVAILABLE.
Explanation: The current and all future overrides of
the resource have been deleted. Also, the current timer
of the resource expired before it could be purged.
The variable resource shows the name of the
resource.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: HSACMSST
HSAL1404E A VSAM ERROR OCCURRED. RC=rc,
RSNreason FUNCTION= function
Explanation: A function operation on the override file
failed with a return code and a reason code.
HSAL1406I
SERVICE PERIOD TIME SLOT HAS
BEEN MISSED FOR resource.
Explanation: The LE component that is responsible for
schedules received an event indicating the beginning or
the end of a time slot. However, the current status of
the resource is equal to the status of the resource before
the event was generated. This indicates the loss of at
least one time slot and can only have occurred when
the automation manager or one of its components was
suspended for this time frame.
The variable resource shows the name of the affected
resource.
System action: Processing continues. However, this
may lead to unexpected behavior for the affected
resource.
Operator response: Check the service period of the
indicated resource. Perform the missed action manually
if necessary.
The variable rc shows the value of the return code.
System programmer response: None.
The variable reason shows the value of the reason
code.
Module: HSACMSST
The variable function shows the name of the
function.
System action: The override file is marked
unavailable. All requests querying or manipulating any
overrides are rejected. Existing base schedules are still
working as defined in the customization dialogs.
HSAL5100E ENVIRONMENT SETUP FOR
WORKITEM CREATION FAILED.
RC=rc RSN=rsn.
Explanation: The setup function to create a work item
failed. The internal communication based on work
items is no longer guaranteed.
Operator response: Notify your system programmer.
The variable rc shows the value of the return code.
System programmer response: Analyze the VSAM
return code and reason code and correct the error
condition. When the problem is solved, start a
secondary automation manager and initiate a takeover.
The variable rsn shows the value of the reason code.
System action: The automation manager terminates.
Operator response: Inform your system programmer.
Module: HSACMSST
System programmer response: Contact your IBM
Support Center.
HSAL1405I
Module: HSACLWI
WORKITEM REQUEST FAILED. RC=rc,
RSN=reason
Explanation: A function operation on the override file
failed with a return code and a reason code.
HSAL6010A resource; INTERVENTION REQUIRED;
BEYOND AUTOMATION
The LE component responsible for schedules received
an unexpected response from a workitem request that
signalled the beginning or the end of a service period.
Explanation: A problem with the resource has been
detected that automation cannot handle.
The variable rc shows the value of the return code.
The variable reason shows the value of the reason
code.
System action: Processing continues. However, this
may lead to an unexpected behavior of the affected
resources.
Operator response: Notify your system programmer.
System programmer response: Contact your IBM
Support Center.
Module: HSAHNDLS
146
System Automation for z/OS Messages and Codes:
The variable resource shows the name of the
resource where an intervention is required.
System action: Automation for the resource is
stopped.
Operator response: Fix the problem or notify your
system programmer.
System programmer response: Try to fix the problem.
Classes: 80, 81.
HSAL6011E • HSAL6051I
HSAL6011E resource; INTERVENTION REQUIRED;
AUTOMATION DENIED
Explanation: The resource could not be automated
because the automation flag is turned off.
The variable resource shows the name of the
resource that could not be automated.
System action: Automation for the resource is
stopped.
Operator response: Check why the automation flag is
turned off and decide whether to turn it on.
System programmer response: None.
Classes: 80, 82.
HSAL6012E resource; INTERVENTION REQUIRED;
AUTOMATION INHIBITED
Explanation: Automation of the resource is not
possible due to an intervention required on another
resource. The immediate problem with this resource is
only the symptom of a problem with another resource.
The variable resource shows the name of the
resource where an intervention is required.
System action: Automation for the resource is
stopped.
Operator response: None.
System programmer response: None.
Classes: 80, 85.
HSAL6040E resource; DEGRADED
Explanation: The resource is the target of a
MakeAvailable request and is currently degraded.
The variable resource shows the name of the
resource that is degraded.
System action: Automation continues. If an
opportunity arises, the resource will be restored to
Satisfactory.
Operator response: Investigate why the resource is
degraded.
System programmer response: Assist with operator
action.
Classes: 80, 86, 87.
HSAL6041E resource; DEGRADED
Explanation: The resource is currently degraded.
The variable resource shows the name of the
resource that is degraded.
Operator response: Find the resource that is impacting
this one and fix the problem.
System action: Automation continues. If possible, the
resource will be restored to Satisfactory.
System programmer response: None.
Operator response: Investigate why the resource is
degraded.
Classes: 80, 83.
HSAL6020I
resource; AWAITING AUTOMATION
Explanation: The resource is automatable, but is
waiting for prerequisites to be satisfied. These could be
either dependencies or triggers.
The variable resource shows the name of the
resource.
System action: Automation waits until the
prerequisites for automation are satisfied and then
starts processing.
Operator response: If the prerequisites involve
operator action, for example, manually setting a trigger,
check that this was done.
System programmer response: None.
Classes: 80, 84.
System programmer response: Assist with operator
action.
Classes: 80, 87.
HSAL6050I
Explanation: The resource is the target of either a
MakeAvailable or MakeUnavailable request and that
status has been achieved.
System action: Automation proceeds normally.
The variable resource shows the name of the
resource.
Operator response: None.
System programmer response: None.
Classes: 80, 88, 89.
HSAL6051I
HSAL6030I
resource IN AUTOMATION
Explanation: Commands concerning the resource have
been sent to the agent responsible for it.
The variable resource shows the name of the
resource.
System action: Automation for the resource continues.
resource; SATISFACTORY
resource; SATISFACTORY
Explanation: The resource has achieved its desired
status.
The variable resource shows the name of the
resource.
System action: Automation continues.
Chapter 7. Messages HSAH001I to HSAL6999I
147
HSAL6156I • HSAL6285I
Operator response: None.
Classes: 80, 89.
System programmer response: None.
HSAL6100I to HSAL6999I
These messages have the following meaning unless stated by individual message
entries:
Explanation: These messages are generated by the automation manager's internal
logic trace and are subject to change by APAR in both content and flow. They are
not documented for customer use.
System action: Automation continues.
Operator response: None.
System programmer response: If requested, extract the messages via INGINFO,
INGHIST, or INGLKUP and make them available to IBM support.
HSAL6156I
Prepare Unavailable order forgotten
(cancel sent)
Explanation: The automation manager told the
automation agent to issue the SHUTINIT commands
for the resource and it has done so. The Automation
Manager has now decided that the resource should not
be stopped and has cleared its record that this has
happened. The automation agent has been told to clear
the shutdown process it has in progress for the
subsystem.
Note that this message is not guaranteed to be issued
whenever such a situation occurs. If, for example, the
automation agent were to disconnect, the record that
the SHUTINIT had been issued would be cleared, but
this message (and the cancel order to the agent) would
not be sent.
System action: Automation continues.
Operator response: None.
use Update to change the resource's automation status
to Idle. This should resume automation for the
resource. If INGLIST does not show an outstanding
operation, you need to first set the resource's observed
state to HardDown, then set its automation state to
Idle, and finally set its observed state to SoftDown.
This should cause the automation manager to resend
the order to the agent.
System programmer response: Check your service
levels for XCF and SA z/OS. Contact IBM service for
SA z/OS.
Classes: 80, 81.
HSAL6284I
REQUEST FOR requesttype action FROM
source FOR resource UNSATISFIED
AFTER TIME OUT
Explanation: Automation returns that the request has
not been satisfied within the specified time.
System programmer response: None.
The variable requesttype action shows the type of the
request and the action.
Classes: 80, 89.
The variable source shows the name of the source.
HSAL6230A resource; AGENT ORDERED TIME-OUT;
LOST AGENT STATUS UPDATE?
Explanation: The automation manager did not receive
the expected response within 5 minutes for an order
that it sent to the resource's automation agent.
The variable resource shows the name of the
resource.
System action: Automation for the resource is
suspended, its automation state will be set to Problem.
In the event that the expected response should
subsequently arrive, automation will be resumed.
Operator response: Check the state of the resource
with INGLIST. If it shows an outstanding operation,
148
System Automation for z/OS Messages and Codes:
The variable resource shows the name of the
resource.
System action: Automation continues.
Operator response: None.
System programmer response: None.
Classes: 80, 81.
HSAL6285I
REQUEST FOR requesttype action FROM
source FOR resource CANCELLED AFTER
TIME OUT
Explanation: Automation returns that the request has
not been satisfied within the specified time and
therefore was removed.
HSAL6286I • HSAL6288I
The variable requesttype action shows the type of the
request and the action.
The variable source shows the name of the source.
The variable resource shows the name of the
resource.
System action: Automation continues.
Operator response: None.
System programmer response: None.
Classes: 80, 81.
HSAL6286I
REQUEST FOR requesttype action FROM
source FOR resource SATISFIED
Explanation: Automation returns that the request was
satisfied.
The variable requesttype action shows the type of the
request and the action.
The variable source shows the name of the source.
The variable resource shows the name of the
resource.
System action: Automation continues.
Operator response: None.
System programmer response: None.
Classes: 80, 88, 89.
HSAL6288I
REQUEST FOR requesttype action FROM
source FOR resource EXPIRED
Explanation: Automation returns that the request was
satisfied after the specified time period.
The variable requesttype action shows the type of the
request and the action.
The variable source shows the name of the source.
The variable resource shows the name of the
resource.
System action: Automation continues.
Operator response: None.
System programmer response: None.
Classes: 80, 81.
Chapter 7. Messages HSAH001I to HSAL6999I
149
Messages HSAH001I to HSAL6288I
150
System Automation for z/OS Messages and Codes:
Chapter 8. Messages HSAM1000I to HSAM5411I
HSAM1000I AUTOMATION MANAGER
SUBTASKS ARE BEING STARTED.
Explanation: The basic initialization step of the
SA z/OS automation manager has successfully
completed. All subtasks are being attached and the
main task will wait observing the subtasks.
System action: The SA z/OS automation manager
continues with the initialization.
Operator response: None.
System programmer response: None.
HSAM1001I THE KEY keyword CANNOT BE
RETRIEVED FROM PKVT, CONTINUE
WITH DEFAULT VALUE: default value.
Explanation: A keyword cannot be resolved. The key
value specified in the parmlib member will be ignored.
The variable keyword shows the start parameter that
can be modified in the parmlib member.
The variable default value shows the default value
specified for the keyword. If the default value is
blank, this field may be blank.
System action: The SA z/OS automation manager
continues with the initialization.
Operator response: None.
System programmer response: Contact your IBM
Support Center.
HSAM1002I AUTOMATION MANAGER
INITIALIZATION DETECTED THAT
THE SUBSYSTEM subsystem IS
MISSING OR CONFLICT DETECTED
WITH PARMLIB PARAMETERS
COMM/MQM.
Explanation: The automation manager needs the
specified system component for initialization.
The variable component shows the required system
component, for example, the OMVS kernel or the
WebSphere MQ Manager.
System action: The SA z/OS automation manager
terminates.
Operator response: Inform your system programmer.
System programmer response: Start the required
system component. Examine the automation manager
PARMLIB member for correct specification of the
COMM and MQM parameters. If COMM=XCF, the MQM
parameter must not be specified. If COMM=MQ, a valid
© Copyright IBM Corp. 1996, 2014
WebSphere MQ subsystem name must be specified for
the MQM parameter.
HSAM1003I ARM function WAS SUCCESSFUL FOR
ELEMENT=element TYPE=type restart.
Explanation: An ARM function (either register or
deregister) could be successfully completed.
The variable function shows the ARM function. It
can be either register or deregister.
The variable element shows the ARM element,
representing the SA z/OS automation manager.
The variable type shows the type of the ARM
element SA z/OS automation manager.
The variable restart shows whether the automation
was restarted by ARM or not (RESTART=YES or
RESTART=NO.)
System action: The SA z/OS automation manager
continues initializing being ARM enabled.
Operator response: None.
System programmer response: None.
HSAM1004I ARM function FAILED FOR
ELEMENT=element TYPE=type, IXCARM
RET=RC RSN=RSN restart.
Explanation: An ARM function (either register or
deregister) could not be completed successfully.
The variable function shows the ARM function. It
can be either register or deregister.
The variable element shows the ARM element,
representing the SA z/OS automation manager.
The variable type shows the type of the ARM
element "SA z/OS automation manager" and
optionally the restart type which informs you
whether the automation was restarted by ARM or
not (RESTART=YES or RESTART=NO or
RESTART=ERR).
The variable RC shows the return code of the ARM
function.
The variable RSN shows the reason code of the
ARM function. If the Automation Manager retries
ARM registration due to parameter ARMWAIT=nnn
in parmlib member HSAPRMxx then the variable
RSN has a suffix ",RETRY...". This informs you that
the Automation Manager is waiting for ARM to be
up.
System action: The SA z/OS automation manager
continues initializing without being ARM enabled. If
RESTART=ERR then the SA z/OS automation manager
was restarted on a different MVS system. In this case,
151
HSAM1005I • HSAM1010I
the SA z/OS automation manager terminates.
1
Implicit normal termination due to directed
takeover (changed operation mode from SAM
to PAM)
4
Stop Immed
8
Stop Force
20
Initialization failed because MTIB could not be
created
24
Initialization failed because MTIB Vector could
not be created
28
Initialization failed because a task could not be
created
32
Initialization failed because a task could not be
attached
33
Initialization stopped but no takeover is
performed
34
Either the initial storage check failed, or a
GETMAIN service abended after initialization
due to a storage shortage. The automation
manager needs a minimum of 40 MB free
storage.
Note that any request that has not yet been processed
by the automation manager will be lost and cannot be
recovered in case of an abend or any regular takeover.
35
ARM (De)Reg failed
36
z/OS UNIX System Services has canceled the
job
System action: None.
39
An I/O error occurred for the takeover file
Operator response: None.
40
Implicit normal or forced termination due to
error detected by observer
44
The subsystem is missing
HSAM1006E PARAMETER option CANNOT BE
RETRIEVED FROM PARMLIB.
45
z/OS does not meet the prerequisites
48, 52
Explanation: The named parameter is mandatory but
not specified in the HSAPRMxx parmlib member that is
used at the startup time of the automation manager.
C++ task failed. This is probably an exception
56
LE task abended
60
Task abended
The variable option is the name of the parameter
that is missing.
64
LE user abend
72
Bad return code from subtask shell function
76
Event handler detected an error
80
The job was canceled
Operator response: None.
System programmer response: Verify if ARM was
correctly customized for the SA z/OS automation
manager. If necessary, contact your IBM Support
Center.
HSAM1005I COMMUNICATION IS XCF ONLY.
THE TAKEOVER FILE WILL BE USED
FOR HOT START AND RECOVERY
PURPOSES.
Explanation: The automation manager does not use
MQ Series, neither for the communication with the
automation agents nor for recording the current status
and settings of the resources. Instead XCF is used for
the communication with the automation agents.
The automation manager records all changes made to
the resources in the takeover file identified by
DD-name HSATKOVR. In case of an abend or any
normal takeover (hot start), the automation manager
reads the takeover file to restore the most current status
of the resources.
System programmer response: None.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: Add the parameter in
the HSAPRMxx parmlib member that is used at the
startup time of the automation manager.
Note that for all return codes < 40 no ARM restart is
performed. It will be suppressed even if ARM is
enabled, except for /F jobname,STOP,..,RESTART.
HSAM1010I AUTOMATION MANAGER
TERMINATION COMPLETE, REASON
CODE = reason code
System action: The SA z/OS automation manager
terminates.
Explanation: The automation manager main task
terminates. If the reason code is zero it terminated
successfully. The reason code can have the following
values:
System programmer response: Analyze the reason code
and, if issued, the HSAM1050E error message.
0
152
Successful completion
System Automation for z/OS Messages and Codes:
Operator response: None.
HSAM1011I • HSAM1052I
HSAM1011I CURRENT Z/OS SYSTEM DOES NOT
MEET AUTOMATION MANAGER
PREREQUISITES: xxxx
Explanation: The automation manager requires a
z/OS prerequisite that is not met by the current z/OS
system. The following prerequisites may be detected:
z/OS < 1.9
The release of z/OS is earlier than V1.9.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: Run the automation
manager on a z/OS system that meets the specified
prerequisites.
See “AOF350E” on page 37 for diagnostic
information about combinations of error type and
error code.
v The variable service shows the name of the service
that caused the error.
v The variable return code shows the return code of the
failing service (hex number). This token is specified
together with service.
v The variable reason code shows the reason code of the
failing service (hex number). This token is specified
together with service.
v The variable diagnostic shows diagnostic information
in a string of tokens. The first token specifies the
name of the failing module. All remaining tokens
vary depending on the error code. Data provided by
diagnostic is intended for IBM service
v
HSAM1050E AUTOMATION MANAGER ERROR
DIAGNOSIS: SYSTEM=system
TASK=task name ERRTYPE=error type
ERRCODE=error code SERVICE=service
RC=return code RSN=reason code
DIAG=diagnostic
Explanation: This is a generic error message that
provides a detailed problem description of an error that
was detected during automation manager processing.
v The variable system shows the name of the MVS
system where the error was detected.
v The variable task name shows the name of the
automation manager task that causes the error.
v The variable error type shows the type of the error.
The following values can occur:
4
Input checking failed.
8
Initialization error.
12 Termination error.
16 An internal sysplex communication pipe service
provided by an SA z/OS system failed.
20 RPC Command Handler failed.
24 A system service named by SERVICE, such as
the MVS request IXCJOIN, failed.
32 Storage problem.
36 Internal error.
Note: An internal error 36, combined with
RC=00000EC6 and RSN=0000FF09 may indicate
automation manager termination due to OMVS
shutdown.
40 Environment error.
v The variable error code shows a unique number to
determine the location in the code where the error
was detected.
personnel.
For further information about the combinations of error
types and error codes and their meaning, refer to
“AOF350E” on page 37.
System action: None.
Operator response: None.
System programmer response: Look into the table for
combinations of error type/codes for a detailed
explanation of the error. Examine the return code and
reason code of the failing service if available. If
necessary, contact your IBM Support Center.
HSAM1051E SYSPLEX COMMUNICATION
MANAGER INITIALIZATION FAILED.
Explanation: An error was detected during
initialization of the sysplex communication manager
task in the SA z/OS automation manager.
System action: The SA z/OS automation manager
terminates.
Operator response: None.
System programmer response: Look for additional
HSAM1050E messages that are issued with this
message.
HSAM1052I SYSPLEX COMMUNICATION
MANAGER INITIALIZATION
COMPLETE.
Explanation: The sysplex communication manager
task of the SA z/OS automation manager could be
successfully initialized and is ready to receive.
System action: The SA z/OS automation manager
continues with the initialization.
Operator response: None.
System programmer response: None.
Chapter 8. Messages HSAM1000I to HSAM5411I
153
HSAM1059I • HSAM1305I
HSAM1059I DIAGNOSTIC INFO: MOD=module
INCIDENT=incident diagnostic-text
Explanation: The purpose of this message is to
provide diagnostic information to IBM service staff.
The variable module shows name of the module that
detected the incident.
The variable incident shows a unique ID for an
internally detected incident.
The variable diagnostic-text shows useful text in free
format. The text depends on the incident that
occurred. For example, for INCIDENT=100, this is the
duplicate handle + seq-number.
System action: Processing continues.
Operator response: None.
System programmer response: None.
HSAM1301I SA z/OS AUTOMATION MANAGER
WAITING FOR INITIALIZATION
DELAY COMPLETION.
Explanation: An automation manager initialization
delay of greater than 30 seconds was specified. The
specified delay allows another automation manager to
assume priority control of the automation sysplex if
started within the delay period.
System action: The SA z/OS automation manager
suspends initialization until the specified delay expires
or is canceled through an operator command. This
message is deleted when the specified delay is no
longer in effect.
Operator response: The delay may be canceled by
routing an MVS Modify(F) <jobname>,GO command to
the issuing system image.
System programmer response: None.
HSAM1302A SPECIFY SA z/OS AUTOMATION
CONFIGURATION DATA SET NAME.
Explanation: The SA z/OS automation manager has
been started with PROMPT=YES in effect. If requested,
this message will appear on the first SA z/OS
automation manager instance to assume control of the
automation sysplex following a sysplexwide IPL or
similar automation shutdown.
System action: The SA z/OS automation manager
waits for a response to this request.
Operator response: A null or asterisk (*) response may
be used to indicate that the default data set as
determined by the start type is to be used. For a warm
start, this default is the data set that was in use when
the previous primary automation manager instance
terminated. For a cold start, the default is the data set
or generation data group (GDG) member as specified
for the installation through the selected parmlib
member.
154
System Automation for z/OS Messages and Codes:
The response may also be a fully qualified data set or
GDG member name. If the default configuration data
set is a GDG member, a different member of the same
GDG may be specified using an asterisk followed by
the relative GDG number in parentheses, for example,
*(0) or *(-1).
System programmer response: None.
HSAM1303I SA z/OS AUTOMATION MANAGER
IS WAITING FOR MQSERIES
CONNECTION
Explanation: The SA z/OS automation manager is
checking whether MQSeries is ready.
System action: If MQSeries is not ready the SA z/OS
automation manager retries until the
TAKEOVERTIMEOUT defined in the parmlib is
expired. If it is expired the SA z/OS automation
manager switches from hot to warm start.
Operator response: None.
System programmer response: None.
HSAM1304A SPECIFY SA z/OS AUTOMATION
CONFIGURATION DATA SET NAME.
Explanation: The SA z/OS automation manager was
unable to determine or otherwise process the
configuration data set as specified through the
HSAM1302A response, or defaulted from prior use.
Additional messages will indicate any errors
encountered while attempting to process the specified
or default data set.
System action: The SA z/OS automation manager
waits for a response to this request.
Operator response: The response must be the fully
qualified MVS data set or GDG member name
containing the SA z/OS configuration data. If the
default configuration data set is a GDG member, a
different member of the same GDG may be specified
using an asterisk followed by the relative GDG number
in parentheses, for example, *(0) or *(-1). The
automation manager may also be stopped if no valid
configuration data is available.
System programmer response: None.
HSAM1305I UNABLE TO PROCESS SA z/OS
AUTOMATION CONFIGURATION
DATA SET dataset
Explanation: The SA z/OS automation manager was
unable to dynamically allocate the named configuration
data set. The named data set name was successfully
allocated, but cannot be used by the issuing automation
manager instance. Additional messages will indicate
any errors encountered while attempting to process the
specified or default data set.
HSAM1306I • HSAM1310I
The variable dataset shows the name of the
configuration data set that could not be allocated
dynamically.
System action: The SA z/OS automation manager
instance prompts for a new configuration data set name
via message HSAM1304A.
Operator response: Check that the data set has not
been incorrectly modified prior to starting the affected
automation manager instance. Also check whether all
copy operations from the configuration dialog output
completed successfully. Respond to the HSAM1304A
prompt with a new or backup data set name as
described in the installation procedures.
System programmer response: None.
HSAM1306I UNABLE TO ALLOCATE SA z/OS
AUTOMATION CONFIGURATION
DATA SET dataset
Explanation: The SA z/OS automation manager was
unable to dynamically allocate the named configuration
data set. The data set name could not be allocated or is
not a partitioned data set. Additional dynamic
allocation messages will indicate any errors
encountered while attempting to allocate the data set.
The variable dataset shows the name of the
configuration data set that could not be allocated
dynamically.
System action: The SA z/OS automation manager
instance prompts for a new configuration data set name
via message HSAM1304A.
Operator response: Check that the data set name is
correct and that it is a correctly catalogued partitioned
data set. Respond to the HSAM1304A prompt with a
new or backup data set name described in the
installation procedures.
System programmer response: None.
HSAM1307I SA z/OS SECONDARY AUTOMATION
MANAGER INITIALIZATION
COMPLETE.
Explanation: The SA z/OS automation manager
instance has completed initialization as a secondary
manager, and is ready to assume automation sysplex
control with minimum delay in case the primary
manager terminates.
System action: The SA z/OS automation manager
instance monitors for changes in the configuration
status, and attempts to assume control of the
automation sysplex in case the primary automation
manager terminates.
HSAM1308I SA z/OS PRIMARY AUTOMATION
MANAGER INITIALIZATION
COMPLETE, TYPE=type
Explanation: The SA z/OS automation manager
instance has completed initialization as the primary
automation manager, and has assumed control of the
automation sysplex.
The variable type shows the start type. It can be
COLD, WARM, or HOT.
System action: The SA z/OS automation manager
instance monitors for changes in the configuration
status, and is ready to service requests from all
automation agents defined to the automation sysplex.
Operator response: None.
System programmer response: None.
HSAM1309I SA z/OS PRIMARY AUTOMATION
MANAGER HOT TAKEOVER
COMPLETE.
Explanation: The SA z/OS automation manager
instance has successfully completed a takeover
operation and is now the primary automation manager.
This message may also appear when a START=HOT is
used to manually restart the manager.
Note: Although the Automation Manager takeover is
now complete, the Automation Agents might still be in
the process of loading the Automation Control File
(ACF). During the ACF load process, the Automation
Agent will reflect status SUSPENDED on the INGAMS
display. Issuing an INGAMS REFRESH command while
an Agent is SUSPENDED will interfere with the still
ongoing load process and will result in a delay for the
processing of the INGAMS REFRESH command. It is
recommended that you wait until all agents are in the
READY status before issuing the INGAMS REFRESH
command.
System action: The SA z/OS automation manager
instance monitors for changes in the configuration
status, and is ready to service requests from all
automation agents defined to the automation sysplex.
Operator response: None.
System programmer response: None.
HSAM1310I RC=rc REAS=reason OPCODE=@5
(@3.@4) @6.
Explanation: This is an internal message for diagnostic
purposes only.
Ignore messages with RC=2.
Operator response: None.
System action: None.
System programmer response: None.
Operator response: None.
Chapter 8. Messages HSAM1000I to HSAM5411I
155
HSAM1311I • HSAM1320E
System programmer response: Contact your IBM
Support Center.
HSAM1311I @1
Explanation: This is an internal message for diagnostic
purposes only.
System action: None.
Operator response: None.
System programmer response: None.
HSAM1314I TAKEOVER WILL BE DELAYED FOR
timeout SECONDS.
Explanation: Takeover will be delayed for a number
of seconds if it is done from the VSAM takeover file.
The variable timeout is taken from the
TAKEOVERTIMEOUT parameter of the HSAPRMxx
parmlib member.
System action: Processing continues. Any stop
command is accepted but does not cause termination
until the time that is specified in TAKEOVERTIMEOUT
has expired.
Operator response: None.
99 Invalid input parameter
10nn
Allocation failed
20nn
Deallocation failed
where nn is one of the following:
8
Invalid data set name, member name, or
DD-name.
12 Allocation error. retcode and reason are the return
code and reason code from the SVC 99
(DynAlloc).
v The variable retcode gives more details about why the
allocation failed.
v The variable reason is the reason code.
System action: The automation manager continues
and issues message HSAM1317A, asking the operator
how to continue.
Operator response: None.
System programmer response: Analyze why the
allocation failed. Look for additional messages
(HSAL1105E in case of an I/O error) that are issued
with this message.
System programmer response: None.
Classes: None.
HSAM1315I SUCCESSFUL ALLOCATION OF
TAKEOVER FILE dataset_name.
Explanation: The automation manager issues this
message when the takeover file has been allocated
successfully.
The variable dataset_name is the name of the
takeover file as specified in the HSAPRMxx parmlib
member.
System action: The SA z/OS automation manager
continues with initialization.
Operator response: None.
System programmer response: None.
HSAM1316I ALLOCATION OF TAKEOVER FILE
dataset_name FAILED WITH RC=code:
DIAGNOSTIC INFO RETCODE=retcode
REASON=reason.
HSAM1317A REPLY "HOT" TO RETRY HOT-START
OR "WARM" TO CONTINUE WITH
WARM-START OR "CANCEL".
Explanation: During the initialization of the
automation manager performing a hot-start, an error
occurred while accessing the takeover file. Either the
allocation failed or a VSAM read/write error occurred
or the takeover file was disabled by the previous PAM.
System action: The automation manager waits for an
operator response.
Operator response: Specify:
HOT
To retry hot-start processing by allocating the
takeover file again.
WARM To continue with a warm start.
CANCEL
Results in HSAM1390E with the option to stop
the automation manager.
System programmer response: None.
Explanation: The automation manager tried to allocate
the specified takeover file but this failed.
HSAM1320E SA z/OS AUTOMATION MANAGER
request REQUEST TIMED OUT.
v The variable dataset_name is the name of the takeover
file as specified in the HSAPRMxx parmlib member.
Explanation: The named internal automation manager
request did not complete within the time limit
associated with the request.
v The variable code explains why the allocation failed.
It can have the following values:
98 No more memory
156
System Automation for z/OS Messages and Codes:
The variable request shows the name of the request
that timed out.
HSAM1321I • HSAM1324E
This may be due to temporary system performance
factors, delays caused by an unusual amount of
automation activity, or problems processing the named
request.
System action: The SA z/OS automation manager
instance continues monitoring for commands and
configuration changes, and resumes normal operation
when the named request completes. The message will
also be deleted when the request has completed.
System action: The SA z/OS automation manager
instance continues monitoring for commands and
configuration changes, and resumes normal operation
when the named request completes. The message will
be deleted when a response was received from all
affected agents.
Operator response: Verify that all active automation
agents appear to be working correctly and are
communicating with the automation manager.
Operator response: If this message appears often or
remains outstanding for an extended period, advise
your system programmer of the condition.
If this message appears often or remains outstanding
for an extended period, advise your system
programmer of the condition.
System programmer response: Investigate the
following request specific possibilities:
System programmer response: None.
v AMS_READ_CONFIGURATION
HSAM1323I UNABLE TO OBTAIN PREVIOUS
CONFIGURATION INFORMATION,
RC=rc, Reason=reason.
This request is issued during Primary automation
manager startup, automation manager takeover, and
when a configuration refresh is requested. If the
message appears during a hot start or takeover
operation, the delay is probably MQSeries related. If
it appears during a Warm or Cold start, or
configuration refresh operation, the delay is probably
I/O related.
Another reason might be that the automation
manager does not run as super user for UNIX
System Services or one of your HFSs is not mounted
with SUB=MSTR. See also message HSAL1083I for
more information.
v AMS_APPLY_CONFIGURATION
While the timeout value for most automation
manager requests is determined by IBM, the
AMS_APPLY_CONFIGURATION timeout value may
be specified through the HSAPRMxx parameter
member. The time necessary to complete this
function depends on the number of resources
defined, and the temporary appearance of the
HSAM1320E message may indicate that the specified
or default timeout value is too low.
HSAM1321I SA z/OS AUTOMATION AGENT
request REQUEST TIMED OUT.
Explanation: An automation agent request did not
complete within the time limit. This may be due to
temporary system performance factors, delays caused
by an unusual amount of automation activity, or
problems processing the named request.
The variable request shows the name of the request
that timed out.
For a configuration refresh it is required that check
ACF is complete on all agents. Note that a
configuration refresh operation is considered complete
when the automation manager configuration has been
updated, and does not require that all automation
agents have completed their corresponding
configuration update activity.
Explanation: The SA z/OS automation manager was
unable to read the data set defined by the HSACFGIN
DD statement.
The variable rc shows the value of the return code.
The variable reason shows the value of the reason
code.
System action: The SA z/OS automation manager
instance terminates.
Operator response: Check that the data set defined by
the HSACFGIN DD statement of the automation
manager start procedure is available and correctly
initialized. Restart the automation manager using an
alternate data set if available, or contact your systems
programmer.
System programmer response: All instances of the
automation manager within the automation sysplex
must point to the same CFGINFO data set. A new data
set can be initialized by starting the automation
manager with TYPE=COLD.
HSAM1324E UNABLE TO UPDATE
CONFIGURATION INFORMATION,
RC=rc, REASON=reason
Explanation: The SA z/OS automation manager could
not update the data set defined by the HSACFGIN DD
statement.
The variable rc shows the value of the return code.
The variable reason shows the value of the reason
code.
System action: If this message appears during initial
automation manager startup, the instance continues to
run normally. However, a subsequent warm may not be
possible. If the error occurs during a configuration
refresh operation, the configuration refresh will be
aborted.
Operator response: Check that the data set defined by
Chapter 8. Messages HSAM1000I to HSAM5411I
157
HSAM1330I • HSAM1332I
the HSACFGIN DD statement of the automation
manager start procedure is available and correctly
allocated. Also check that the automation manager has
the necessary authorization to update it. When the
problem is resolved, perform a configuration refresh
using the correct data set name.
System programmer response: All instances of the
automation manager within the automation sysplex
must point to the same CFGINFO data set. Also, all
automation manager instances must have the correct
SAF authority to allow it to be updated. If the instance
was started with TYPE=COLD, this may be the initial
access to the data set. Otherwise, the data set is opened
and read during automation manager initialization.
HSAM1330I request REQUEST COMPLETED
SUCCESSFULLY ON agent.
Explanation: An automation manager request has
successfully completed on an automation agent.
The variable request shows the request that was
completed.
The variable agent shows the name of the
automation agent.
System action: The SA z/OS automation manager
instance continues normal processing relative to the
identified automation agent.
Operator response: None.
System programmer response: None.
v Refresh_ACF
This request is normally issued at the end of a
configuration refresh operation to activate the revised
ACF. The affected agent should continue to operate
in a compatible manner with the new configuration
using the previously active ACF data. Thus, newly
added resources will not be automated and existing
resources will be automated using the previously
defined automation policy.
Operator response: Contact your system programmer.
When the problem has been resolved, reissue a
configuration refresh command to retry the failed
request.
System programmer response: The most common
cause of Load_ACF failure is that the ACF available to
the automation agent is incompatible with the current
manager configuration. Similarly, a Check_ACF failure
often indicates an incompatibility between the available
ACF and the new automation manager configuration.
Other possible causes include corruption of the ACF
content and various other problems verifying its
content. The reporting automation agent should
provide additional information about the reason for the
failure.
The failure of a Refresh_ACF request indicates
problems were encountered while activating the
changes contained in the new configuration. Any
resources that were deleted or added by the new
configuration will not be automated, and existing
resources will be automated using the previous agent
policy.
HSAM1331I request REQUEST FOR agent FAILED
Explanation: An automation manager request failed
on an automation agent.
The variable request shows the request that failed.
The variable agent shows the name of the
automation agent.
System action: The automation manager action
depends on the request that failed and on the reason
why the request was issued. In general however, the
actions are as follows:
v Load_ACF Request
The affected agent is unable to initialize or perform
automation until the cause of the failure is identified
and resolved. The most common cause of this failure
is a mismatch between the ACF available to the
agent and the current automation manager
configuration. Additional automation agent messages
may provide more detailed information about the
reason for the failure.
v Check_ACF request
This request is normally issued during a
configuration refresh operation to verify that the new
configuration is available to all automation agents.
The configuration refresh operation is terminated as
a result of this condition.
158
System Automation for z/OS Messages and Codes:
HSAM1332I INVALID response RESPONSE FROM
agent, REASON=reason.
Explanation: An invalid response for a request was
received from an automation agent.
The variable response shows the invalid response
that the automation agent issued.
The variable agent shows the name of the
automation agent that issued the response.
The variable reason shows the value of the reason
code that the automation agent issued.
System action: If the request is Check_ACF, the
associated configuration refresh operation will be
terminated. Otherwise, the automation manager
operation continues as if the return code had been zero.
Operator response: Report the message to your
system programmer. Check whether the identified
agent operates correctly. Also check whether any error
messages are issued that indicate problems when
processing the named request.
System programmer response: This message indicates
a software problem. Report the problem to your IBM
Support Center.
HSAM1333I • HSAM1360I
HSAM1333I request REQUEST PROCESSED ON
agent.
Explanation: The automation manager has completed
processing of a request.
The variable request shows the name of the request.
The variable agent shows the name of the
automation agent where the request was processed.
Normally, the automation manager then goes back to
ready state. However, this message does not confirm
that the request was processed successfully. It may also
have failed. In case of a failure, an additional message
may be issued, for example, if a refresh request fails,
message HSAM1337I is issued.
System action: The SA z/OS automation manager
instance continues processing normally. Additional
messages, for example message HSAM1330I, may be
issued due to events that are received later on.
Operator response: None.
System programmer response: None.
HSAM1337I CONFIGURATION REFRESH
REQUEST TERMINATED.
Explanation: A configuration refresh request has been
terminated due to errors or automation agent
incompatibilities. No changes to the automation
manager configuration have been implemented and no
automation agent updates have been scheduled as a
result of the request.
System action: Automation continues using the
configuration in effect when the request was issued.
Operator response: Check for other messages
indicating the reason for the termination of the request.
Determine the cause of the error and correct your data.
Then reissue the request.
System programmer response: None.
HSAM1338I CONFIGURATION REFRESH
REQUEST COMPLETED WITH AGENT
UPDATE ERROR INDICATIONS.
Explanation: A configuration refresh request has
completed successfully on the automation manager.
However, one or more automation agents have
reported problems when implementing the ACF
changes. Message HSAM1331I contains more
information about the affected agent(s), and the
individual agents should have issued messages
indicating the problem details.
resources will not be automated. Existing resources will
be automated using the previously defined automation
policy.
Operator response: Contact your system programmer.
When the cause has been determined, issue a
configuration refresh command to retry the failed
request.
System programmer response: Check for automation
agent error messages indicating the cause of the ACF
refresh failure and correct your data accordingly.
The failure of a Refresh_ACF request indicates
problems were encountered while activating the
changes contained in the new configuration. Any
resources that were deleted or added by the new
configuration will not be automated. Existing resources
will be automated using the previous agent policy.
HSAM1339I CONFIGURATION REFRESH
REQUEST COMPLETED
SUCCESSFULLY.
Explanation: This message is issued when a
configuration refresh request has been completed
successfully. It indicates that the primary automation
manager and all SA z/OS automation agents within
the automation sysplex have processed the request and
have indicated normal completion of the update
process.
System action: Automation continues using the
requested configuration.
Operator response: None.
HSAM1360I UNABLE TO RETRIEVE RECOVERY
INFORMATION - WARM START
RECOVERY IN PROGRESS.
Explanation: A takeover or startup with TYPE=HOT
cannot complete because the recovery information
needed to do so is either unavailable or has been
invalidated.
System action: The automation manager performs a
warm start to reach an operational state. Automation
continues after the warm start operation completes.
This operation may take some time to complete
because each automation agent must reconnect with the
automation manager and present status for all
resources under its control.
Operator response: Any automation manager requests
that were incomplete when the previously active PAM
terminated may need to be resubmitted.
System programmer response: None.
System action: Automation continues using the new
automation manager configuration. The affected
agent(s) should continue to operate in a compatible
manner with the new configuration using the
previously active ACF data. Thus, newly added
Chapter 8. Messages HSAM1000I to HSAM5411I
159
HSAM1361I • HSAM1373I
HSAM1361I UNABLE TO PROCESS RECOVERY
INFORMATION - ABNORMAL
TERMINATION IN PROGRESS
that it is not valid. This may occur when the previous
automation manager instance has invalidated the
takeover file, for example, because of an I/O problem
or an internal problem.
Explanation: A takeover, ARM restart, or restart with
TYPE=HOT cannot complete because the recovery
information needed to do so is invalid.
System action: The automation manager continues
with a warm start.
System action: The automation manager instance will
be abnormally terminated after invalidating the
recovery information. This prevents a subsequent
takeover or restart from attempting a retry using the
invalid recovery data.
Operator response: If another automation manager
instance is available, it should attempt a takeover
operation, detect the invalidated restart information,
and recover by attempting a warm start (see message
HSAM1360I). Otherwise, the current automation
manager instance will be restarted by ARM if defined
by the installation as eligible for restart. If neither of
these two conditions apply, manually restart the
automation manager instance specifying either
TYPE=WARM or TYPE=HOT.
HSAM1370I TAKEOVER WILL BE DONE FROM
TAKEOVER FILE:dsn.
Explanation: The automation manager performs a hot
start or a takeover from the takeover file with the name
specified in dsn.
System action: None.
Operator response: None.
System programmer response: None.
Operator response: None.
System programmer response: None.
HSAM1373I PROBLEM WITH TAKEOVER FILE
DETECTED. REASON=rr, INFO=yyy
Explanation: The automation manager detected one of
the following problems regarding the takeover:
v The reason code rr describes the problem:
Disabled
The previous PAM has disabled the takeover file.
The takeover file might therefore be outdated.
IOError
The previous PAM has detected an I/O error for
the takeover file. The takeover file might therefore
be outdated.
LoadError
The previous PAM has suffered an ABEND while
loading the takeover file. The most likely reason is
a corrupted takeover file.
Mismatch
During takeover a mismatch was detected between
the takeover file name in the HSAPRMxx parmlib
member and the name that was used by the
previous PAM.
System programmer response: Check that the data set
has a valid takeover file identifier. The first four bytes
must contain the binary value X'12345678'.
Possible Mismatch
During startup of a SAM, a mismatch is detected
between the takeover file name in the HSAPRMxx
parmlib member and the name that was used by
the previous PAM. This message might be an
indication that the SAM and PAM do not use the
same parmlib member HSAPRMxx. However, there
is a time window where the SAM and the PAM are
started concurrently where this possible mismatch
can occur and can possibly be ignored. This is the
case when the pending PAM has not yet finished
reading the configuration file and has not yet
updated the HSACFGIN accordingly. In any case it
is recommended to check that the parmlib
members are still valid.
HSAM1372I FORCE WARM START DUE TO
TAKEOVER FILE OR OPERATOR
RESPONSE.
v The variable yyy='tkovfile_dsn1, tkovfile_dsn2 where
tkovfile_dsn1 is taken from HSAPRMxx and
tkovfile_dsn2 is the takeover file that was used by the
previous PAM.
HSAM1371I TAKEOVER FILE CANNOT BE READ
OR IS CORRUPTED.
Explanation: The automation manager tried to read
the takeover file. However, the data set is either not
readable or is not a valid takeover file (does not
contain a valid identifier).
System action: The automation manager continues
with a warm start.
Operator response: None.
Explanation: The automation manager tried to
perform a hot start or a takeover from the takeover file.
This action failed and the hot start was degraded to a
warm start. The reason for the failure is that the
operation code at offset 16 was previously set to 'W' or
160
System Automation for z/OS Messages and Codes:
System action: The automation manager also issues
message HSAM1317A and waits for a response. This is
not the case for reason 'Possible Mismatch'.
System action: The automation manager also issues
message HSAM1317A and waits for response.
HSAM1380I • HSAM1389I
Operator response: Depending on the reason code,
proceed as follows:
v If rr=Disabled or IOError, check that the takeover file
is valid.
v If rr=Mismatch, cancel the automation manager and
correct the HSAPRMxx parmlib member. See also
message HSAM1317A.
v If rr=Mismatch and you decide to enter HOT, the
automation manager uses the same takeover file as
was used by the previous PAM rather than the
takeover file name that is specified in the
HSAPRMxx parmlib member.
v If rr=Mismatch and you decide to enter WARM, the
automation manager that is specified in the
HSAPRMxx parmlib member.
v If rr=LoadError, check if the takeover file is
corrupted. If you can repair the file, then you can
reply HOT to message HSAM1317A. Otherwise,
continue with an Automation Manager WARM start.
HSAM1380I request REQUEST ACCEPTED.
Explanation: A request has been received and
validated by the automation manager.
The variable request shows which request was
received and validated.
System action: The automation manager instance
processes the request.
Operator response: None.
System programmer response: None.
HSAM1381I INVALID verb REQUEST PARAMETER,
request REQUEST IGNORED.
Explanation: A parameter specified with a request is
invalid for the request verb.
The variable verb shows the request verb that one of
the parameters specified on the request is invalid
for.
The variable request shows the request that could
not be processed.
System action: The automation manager instance
ignores the request.
Operator response: Specify valid parameters and
reissue the request.
The variable request shows the request that could
not be processed.
System action: The automation manager instance
ignores the request.
Operator response: Contact your system programmer.
System programmer response: The automation
manager command interface received the identified
request with an MVS command request code other than
that used for the MVS Modify command.
HSAM1383I verb REQUEST REJECTED:
INCORRECT AUTOMATION
MANAGER ROLE OR STATUS.
INVALID verb REQUEST PARAMETER,
request REQUEST IGNORED.
Explanation: An MVS MODIFY (F) command was
routed to an automation manager instance that is not in
a role or state compatible with the requested request
verb. Because most automation manager requests run
only on the primary automation manager (PAM), it is
likely that the command was routed to a secondary
instance. Other requests require that the target
automation manager be in a "ready" state to be
accepted.
The variable verb shows the specified request verb.
The variable request shows the request that could
not be processed.
System action: The automation manager instance
ignores the request.
Operator response: Verify that the command was
routed to the correct automation manager instance and
that the instance is in a ready state. Reissue the
command accordingly
System programmer response: None.
HSAM1384I INVALID REQUEST verb, request
REQUEST IGNORED. INVALID verb
REQUEST PARAMETER, request
REQUEST IGNORED.
Explanation: An MVS MODIFY (F) command was
received with an invalid request verb.
System action: The automation manager instance
ignores the request.
System programmer response: None.
Operator response: Correct the verb and parameter
syntax and reissue the request.
HSAM1382I UNSUPPORTED COMMAND VERB,
request REQUEST IGNORED.
HSAM1389I BUILD ID FOR HSAPIEHM xxx yyy
Explanation: An unsupported command verb was
used to route a request to the automation manager. The
automation manager supports only the MVS MODIFY
(F) command for request input.
Explanation: This is an information message for IBM
Service. The fields xxx and yyy provide the compilation
date of the event handler, for example, 2009154 152228.
System action: None.
Operator response: None.
Chapter 8. Messages HSAM1000I to HSAM5411I
161
HSAM1390E • HSAM5100E
HSAM1390E REPLY "YES" TO CONFIRM OR "NO"
TO CANCEL SA z/OS AUTOMATION
MANAGER STOP REQUEST.
HSAM1393I DEFERRED STOP REQUEST WAITING
FOR AUTOMATION AGENT
TERMINATION.
Explanation: A conditional request has been made to
stop an SA z/OS automation manager. No other
SA z/OS automation manager instances are available
and ready to assume automation sysplex control if this
request is allowed to continue. This will result in an
interruption of automation services.
Explanation: A deferred stop request was issued to
the primary automation manager. Upon the expiration
of the stop delay, one or more automation agents were
active and no secondary automation manager was
available to accomplish a takeover.
System action: The SA z/OS automation manager
waits for a response to this request, and continues
automation sysplex control until confirmation is
received.
Operator response: Reply 'YES' to terminate SA z/OS
automation, 'NO' to cancel the stop request. Another
SA z/OS automation manager instance may be started
prior to confirming the request to avoid an interruption
of automation services.
System programmer response: None.
HSAM1391E INVALID RESPONSE: REPLY "YES" TO
CONFIRM OR "NO" TO CANCEL
STOP REQUEST.
Explanation: An invalid response has been given to
message HSAP1390E. Refer to the explanation of that
message for additional information.
System action: The SA z/OS automation manager
waits for a response to this request, and continues
automation sysplex control until confirmation is
received.
Operator response: Reply 'YES' to terminate SA z/OS
automation, 'NO' to cancel the stop request. Another
SA z/OS automation manager instance may be started
prior to confirming the request to avoid an interruption
of automation services.
System programmer response: None.
HSAM1392I AUTOMATION MANAGER STOP
REQUEST CANCELLED.
Explanation: A request to confirm an automation
manager stop request has been denied. Refer to the
explanation of message HSAM1390E for additional
information.
System action: The issuing SA z/OS automation
manager continues processing.
Operator response: None.
System programmer response: None.
System action: The SA z/OS automation manager
waits until all automation agents are disconnected or
another automation manager instance is started.
Operator response: A deferred stop cannot be
canceled. However, starting a new automation manager
instance will result in the termination of the current
primary manager with a takeover by that new instance.
System programmer response: None.
HSAM1396I SA z/OS AUTOMATION MANAGER
SHUTDOWN IN PROGRESS, TYPE=
type
Explanation: A request has been received to stop an
SA z/OS automation manager instance.
The variable type indicates the type of shutdown as
requested by the initiating command.
System action: The SA z/OS automation manager
instance terminates after performing cleanup activities.
Operator response: None
System programmer response: None.
HSAM1399I @1
Explanation: This is an internal message for diagnostic
purposes only.
System action: None.
Operator response: None.
System programmer response: None.
HSAM5100E NO SQA STORAGE AVAILABLE.
Explanation: The first automation manager running
after an IPL allocates storage in the system queue area
(SQA) to hold information shared by all automation
managers running on the single image and the
component trace itself. This area could not be allocated.
System action: The component trace of all automation
managers is disabled.
Operator response: Inform your system programmer.
System programmer response: Increase the system
queue area size.
Module: HSAPICB7
162
System Automation for z/OS Messages and Codes:
HSAM5101I • HSAM5107I
HSAM5101I NUMBER OF ACTIVE AMS EXCEEDS
THE NUMBER OF ASIDS SUPPORTED
FOR THE COMPONENT TRACE.
Explanation: The number of active automation
managers exceeds the number of address space IDs
supported for the component trace. Therefore, the
automation manager issuing this message did not find
a free entry in the system queue area (SQA) to store its
information.
System action: The automation manager’s component
trace is disabled.
Operator response: None.
System programmer response: None.
Operator response: None.
System programmer response: None.
Module: HSAPICB8
HSAM5105E DE-/REGISTRATION TO THE
COMPONENT TRACE FAILED. RC=rc
RSN=rsn.
Explanation: Registration to or deregistration from the
component trace failed.
The variable rc shows the return code that was
issued.
The variable rsn shows the reason code that was
issued.
Module: HSAPICB7
System action: The automation manager component
trace is disabled on registration.
HSAM5102E NAME/TOKEN SERVICE FAILED.
RC=rc.
Operator response: Inform your system programmer.
Explanation: The name/token pair could not be
created or deleted during initialization or termination
of the automation manager.
The variable rc shows the value of the return code
that was issued.
System action: The automation manager component
trace is disabled.
Operator response: None.
System programmer response: Analyze the return
code (see IEANTCR/IEANTDL in z/OS MVS Assembler
Service Reference).
Module: HSAPICB7, HSAPICB8
HSAM5103E MODULE module NOT FOUND.
Explanation: The automation manager component
trace initialization routine could not load the required
module.
The variable module shows the name of the module
that could not be loaded.
System action: If this message is followed by message
HSAM5109I the component trace is disabled.
Otherwise, the automation manager is terminated.
Operator response: Inform your system programmer.
System programmer response: Make the required
module available to the automation manager.
System programmer response: Analyze the return
code and the reason code (see CTRACE in the z/OS
Authorized Assembler Service Reference ).
Module: HSAPICB7, HSAPICB8
HSAM5106I ERROR OCCURRED WHEN WRITING
A TRACE RECORD. POS=position,
SYSTEM CC=cc.
Explanation: The PC routine writing the trace records
abended with the system completion code cc.
The variable position shows the position inside the
module where the abend occurred.
The variable cc shows the completion code.
System action: The automation manager component
trace is disabled.
Operator response: Inform your system programmer.
System programmer response: Contact your IBM
Support Center.
Module: HSAPSTAR
HSAM5107I ERROR OCCURRED IN START/STOP
ROUTINE. POS=position, SYSTEM
CC=cc.
Explanation: The automation manager start/stop
routine of the component trace abended with the
system completion code cc.
Module: HSAPICB7
The variable position shows the position inside the
module where the abend occurred.
HSAM5104I SQA ENTRY NOT FOUND.
The variable completion_code shows the completion
code.
Explanation: The automation manager component
trace termination routine could not clear its system
queue area information.
System action: Processing continues.
System action: The TRACE command is not
processed.
Operator response: Inform your system programmer.
Chapter 8. Messages HSAM1000I to HSAM5411I
163
HSAM5108I • HSAM5170I
System programmer response: Contact your IBM
Support Center.
Module: HSAPSTSS
HSAM5108I COMPONENT component_name
ALREADY DEFINED TO THE
COMPONENT TRACE.
Explanation: An automation manager could not be
registered to the component trace because a previous
automation manager did not deregister itself.
System action: Processing continues.
System programmer response: If the return code is
greater than 4, refer to the return codes of the macro
ENFREQ in z/OS MVS Authorized Assembler Service
Reference for further information.
Module: HSAPICB7, HSAPNCTI
HSAM5121E LISTENER USER EXIT DELETION
FAILED. RC=rc.
Explanation: The deactivation of the System Logger
user exit failed with a return code.
The variable rc shows the value of the return code.
Operator response: None.
System action: Processing continues.
System programmer response: None.
Operator response: Inform your system programmer.
Module: HSAPICB7
System programmer response: If the return code is
greater than 4, refer to the return codes of the macro
ENFREQ in z/OS MVS Authorized Assembler Service
Referencefor further information.
HSAM5109E NAME/TOKEN SERVICE IS
UNAVAILABLE.
Explanation: The MVS name/token services
IEANTCR/RT/DL are not available.
System action: The automation manager component
trace is disabled.
Operator response: None.
System programmer response: Make the MVS
name/token service available.
Module: HSAPICB7
HSAM5110I Error occurred in display routine.
Pos=position, System CC=cc.
Explanation: The automation manager display routine
of the component trace abended.
The variable position shows the position in the
module where the abend occurred.
The variable cc shows the system completion code
that the display routine abended with.
System action: The TRACE command is not
processed.
Operator response: Notify your system programmer.
System programmer response: Contact your IBM
Support Center.
Module: HSAPSCTD
Module: HSAPICB8, HSAPNCTI
HSAM5160I VSAM request ERROR OCCURRED.
RC=rc REASON=reason
Explanation: The VSAM macro instruction that
corresponds to the request failed.
The variable request shows the request that failed.
The variable rc shows the return code that was
issued.
The variable reason shows the reason code that was
issued.
System action: Processing terminates.
Operator response: Inform your system programmer.
System programmer response: Check the return and
reason codes in DFSMS/MVS Macro Instructions for Data
Sets, in the chapter about VSAM Macro Return and
Reason Codes. Correct the error accordingly. Then rerun
the program with the PARM parameter 'RERUN'.
Module: HSAPSIPL
Destination: None.
TEC: NO
HSAM5170I UNKNOWN TRACE OPTION FOUND:
option
Explanation:
HSAM5120E LISTENER USER EXIT
INITIALIZATION FAILED. RC=rc.
Explanation: The activation of the System Logger user
exit failed with a return code.
The variable rc shows the value of the return code.
System action: Processing continues.
Operator response: Inform your system programmer.
164
System Automation for z/OS Messages and Codes:
v The variable option shows the trace option specified
on the OPTIONS parameter of the IPCS CTRACE
command. The following are valid values:
– Communication
– Event
– Instruction
– Lock
HSAM5171I • HSAM5185I
– Schedule
– Workitem
The variable keyword shows the specified filter
option.
System action: Processing continues.
System action: The value is ignored.
Operator response: Correct or delete the option.
Operator response: Correct the value.
System programmer response: None.
System programmer response: None.
Module: HSAPSTUE
Module: HSAPSTUE
HSAM5171I UNKNOWN KEYWORD FOUND:
keyword.
HSAM5174I VALUE value OF KEYWORD keyword IS
NOT NUMERIC.
Explanation: The parser found a keyword that is not
valid.
Explanation: The parser expects an integer for the
keyword option keyword on the OPTIONS parameter.
However, it found a non-numeric value.
The variable keyword shows the specified filter
option.
The following are valid values:
v AM
The variable value shows the value that is not
numeric.
The variable keyword shows the specified filter
option.
v CALLID
System action: The value is ignored.
v ITEM
Operator response: Correct the value.
v KEY
v METHOD
v MODULE
v TASKID
System action: The keyword is ignored.
Operator response: Specify a correct keyword.
System programmer response: None.
Module: HSAPSTUE
HSAM5175I PARSING OF THE OPTIONS
PARAMETER STOPPED AT COLUMN
col.
System programmer response: None.
Explanation: A column value greater than 0 indicates
one of the following:
Module: HSAPSTUE
v A keyword is not spelled correctly.
v A keyword is incorrectly delimited.
HSAM5172I TOO MANY VALUES SPECIFIED FOR
KEYWORD keyword.
v A trace option is incorrectly delimited.
Explanation: All keyword options except AM on the
OPTIONS parameter support up to five different
values. However, the parser found at least one
additional value for keyword option keyword.
A column value of 0 can be caused by one of the
following:
The variable keyword shows the specified filter
option.
System action: The values that exceed the number of
five are ignored.
Operator response: Correct the keyword option.
v A parameter consisting of blanks and commas only
v A parameter length greater than 32K
v An allocation error of temporary storage
The variable col shows which column the parser
stopped at.
System action: Processing terminates.
System programmer response: None.
Operator response: Correct the OPTION parameter, or
increase the region size.
Module: HSAPSTUE
System programmer response: None.
HSAM5173I N (ST/ND/RD/TH) VALUE OF
KEYWORD keyword IS EMPTY.
Explanation: The parser expects a string of at least
one character for the keyword option keyword on the
OPTIONS parameter. However, it found no string, or a
string representing the NULL string.
The variable N shows the number of missing values.
Module: HSAPSTUE
HSAM5185I THE EXTERNAL WRITER HAS BEEN
STARTED AUTOMATICALLY.
Explanation: The start/stop routine detected that the
external writer is not active. Because the automation
manager component trace requires an active external
Chapter 8. Messages HSAM1000I to HSAM5411I
165
HSAM5186I • HSAM5192I
writer, the start/stop routine issued the appropriate
TRACE command.
System action: At least the last trace buffer is lost
when the external writer is stopped.
System action: Processing continues.
Operator response: Inform your system programmer.
Operator response: None.
System programmer response: Analyze the return
code (see ALESERV in z/OS Authorized Assembler Service
Reference).
System programmer response: None.
Module: HSAPSTSS
Module: HSAPSTSS
HSAM5186I ENVIRONMENTAL ERROR
OCCURRED DURING POST OF THE
LAST ACTIVE AM.
HSAM5190E TCB TOKEN OF PARENT TASK
COULD NOT BE OBTAINED. RC=rc.
Explanation: The TCB token of the parent task of the
start/stop routine could not be obtained.
Explanation: POST of the automation manager
waiting for the completion of the start/stop routine
failed.
The variable rc shows the value of the return code.
System action: Processing continues. But the
automation manager is still waiting.
System action: The TRACE command is discarded.
Operator response: Stop the automation manager
manually.
System programmer response: None.
System programmer response: Analyze the return
code (see TCBTOKEN in the z/OS Authorized Assembler
Service Reference).
Module: HSAPSTSS
Module: HSAPSTSS
HSAM5187I PARAMETER WTR= IS MISSING.
HSAM5191I PARAMETER WTR=DISCONNECT IS
NOT SUPPORTED ON A START
TRACE COMMAND.
Operator response: Inform your system programmer.
Explanation: The start/stop routine detected that the
WTR parameter is missing in the reply to the preceding
TRACE command.
Explanation: The start/stop routine expects the name
of the startup procedure of the external writer to be
used. But it found the reserved word DISCONNECT.
System action: The TRACE command is discarded.
Operator response: Re-issue the TRACE command
and add the WTR parameter to the reply.
System action: The TRACE command is discarded.
System programmer response: None.
Operator response: Reissue the TRACE command and
correct the WTR parameter.
Module: HSAPSTSS
System programmer response: None.
Module: HSAPSTSS
HSAM5188I PARSING OF TRACE OPTIONS
FAILED. RC=rc.
HSAM5192I INVALID TRACE OPTION SPECIFIED.
Explanation: The start/stop routine scheduled in the
*MASTER* address space encountered a storage
problem when parsing the OPTION parameter.
Explanation: The specified trace options could not be
determined because of a parsing error.
The variable rc shows the value of the return code.
System action: The TRACE command is rejected.
System action: The TRACE command is discarded.
Operator response: Try the command later. If the
problem persists, contact your IBM Support Center.
System programmer response: None.
Module: HSAPSTSS
HSAM5189E ACCESS TO DATA SPACE FAILED.
RC=rc.
Explanation: The data space where the trace records
are temporarily stored could not be accessed.
The variable rc shows the value of the return code.
166
System Automation for z/OS Messages and Codes:
Operator response: Reissue the TRACE command and
correct the OPTION parameter. Valid options are ALL
or a combination of :
|
|
|
|
|
|
|
|
|
v [B]ase
v [COM]munication
v [CON]trol
v [EN]gine
v [EV]ent
v [F]ramework
v [HA]rdware
v [HI]story
v [I]nstruction
HSAM5193I • HSAM5199I
|
|
|
|
|
|
|
v [L]ock
v [M]emory
v [REQ]uest
v [REX]x
v [SCH]edule
v [SD]F
the data space that holds the trace buffers before they
are passed to the external writer, can no longer be
deleted.
The variable token_name shows the specified token
name.
System action: The TRACE command is discarded.
v [W]orkitem
Operator response: Inform your system programmer.
The options must be separated by a comma.
System programmer response: Contact your IBM
Support Center.
System programmer response: None.
Module: HSAPSTSS
Module: HSAPSTSS
HSAM5193I NO TRACE OPTION SPECIFIED.
Explanation: Either the OPTION parameter was
omitted, or no value was specified for it.
System action: The TRACE command is rejected.
Operator response: See message HSAM5192I for
further information.
HSAM5197E RETRIEVING NAME/TOKEN
token_name FAILED. RC=rc.
Explanation: The start/stop routine encountered an
error when calling the MVS service IEANTRT. If the
message is issued as a response to a STOP command,
the data space that holds the trace buffers before they
are passed to the external writer, can no longer be
deleted.
System programmer response: None.
The variable token_name shows the specified token
name.
Module: HSAPSTSS
The variable rc shows the value of the return code.
System action: The TRACE command is discarded.
HSAM5194I UNKNOWN TRACE OPTION FOUND:
option.
Operator response: Inform your system programmer.
Explanation: The start/stop routine found an
unsupported trace option.
System programmer response: Analyze the return
code (see IEANTRT in z/OS MVS Authorized Assembler
Service Reference).
The variable option shows the specified trace option.
System action: The TRACE command is rejected.
Operator response: See message HSAM5192I.
System programmer response: None.
Module: HSAPSTSS
HSAM5195E SQA HAS BEEN CORRUPTED.
EYE-CATCHER=string.
Explanation: The start/stop routine detected that the
system queue area has been overwritten by another
task or address space.
System action: The TRACE command is discarded.
Operator response: Inform your system programmer.
System programmer response: Contact your IBM
Support Center.
Module: HSAPSTSS
HSAM5196E NAME/TOKEN token_name COULD
NOT BE FOUND.
Explanation: The start/stop routine could not obtain
the address of the system queue area (SQA). If the
message is issued as a response to a STOP command,
Module: HSAPSTSS
HSAM5198E DATA SPACE CREATION FAILED.
RC=rc RSN=rsn.
Explanation: The start/stop routine could not create
the data space holding the trace buffers before they are
passed to the external writer.
The variable rc shows the value of the return code.
The variable rsn shows the value of the reason code.
System action: The TRACE command is discarded.
Operator response: Inform your system programmer.
System programmer response: Analyze the return
code and the reason code (see DSPSERV in the z/OS
MVS Authorized Assembler Service Reference).
Module: HSAPSTSS
HSAM5199I LAST TRACE BUFFER COULD NOT
BE WRITTEN. RC=rc RSN=rsn.
Explanation: The start/stop routine encountered an
error when writing the last trace buffer to the external
writer synchronously.
The variable rc shows the value of the return code.
Chapter 8. Messages HSAM1000I to HSAM5411I
167
HSAM5200E • HSAM5205I
The variable rsn shows the value of the reason code.
System action: Processing continues.
the keyword depending on where it is specified.
Module: HSAPSPLM
Operator response: Inform your system programmer.
System programmer response: Analyze the return
code and the reason code (see CTRACEWR in z/OS
Authorized Assembler Reference).
Module: HSAPSTSS
HSAM5203E VALIDATION ROUTINE module NOT
FOUND.
Explanation: A keyword validation routine could not
be loaded.
The variable module shows the name of the module.
HSAM5200E UNKNOWN KEYWORD FOUND:
keyword.
System action: The keyword is ignored.
Explanation: A library member (see the preceding
IEE252I message) or the PARM parameter of the
startup procedure contains a keyword that is not
known to the automation manager.
System programmer response: Make sure that the
SA z/OS library SINGMOD1 is in the STEPLIB
concatenation of the automation manager startup
procedure and that the module is catalogued in this
library.
The variable keyword shows the value of the
unknown keyword.
Operator response: Inform your system programmer.
Module: HSAPSPLM
System action: The keyword is ignored.
Operator response: Inform your system programmer.
System programmer response: Correct or delete the
keyword depending on where it is specified.
Module: HSAPSPLM
HSAM5201E INVALID KEYWORD FOUND: keyword.
Explanation: A library member (see the preceding
IEE252I message) or the PARM parameter of the
automation manager startup procedure contains a
keyword that was not spelt correctly.
The variable keyword shows the value of the invalid
keyword.
HSAM5204E INVALID KEYWORD DETECTED AT
column IN string.
Explanation: The parse service detected an invalid
delimiter of a keyword. The invalid delimiter was
found either in a library member (see the preceding
IEE252I message) or in the PARM parameter of the
automation manager startup procedure.
The variable column shows the column where the
invalid delimiter was detected.
The variable string shows the string that contains
the invalid delimiter.
System action: All keywords of the string string are
ignored.
System action: The keyword is ignored.
Operator response: Inform your system programmer.
Operator response: Inform your system programmer.
System programmer response: Correct the delimiter
depending on where it is specified.
System programmer response: Correct the keyword
depending on where it is specified.
Module: HSAPSPLM
Module: HSAPSPLM
HSAM5205I PROCESSING MEMBER member.
HSAM5202E INVALID KEYWORD VALUE
DETECTED: KEYWORD=keyword
Value=value.
Explanation: The specified library member (see the
preceding IEE252I message) is being processed.
Explanation: A library member (see the preceding
IEE252I message) or the PARM parameter of the
automation manager startup procedure contains an
invalid keyword.
System action: Processing continues.
The variable keyword shows the name of the
keyword.
System programmer response: None.
The variable value shows the value of the invalid
keyword.
System action: The keyword is ignored.
Operator response: Inform your system programmer.
System programmer response: Correct the value of
168
System Automation for z/OS Messages and Codes:
The variable member shows the name of the member
being processed.
Operator response: None.
Module: HSAPSPLM
HSAM5206E • HSAM5212E
HSAM5206E MEMBER member NOT FOUND.
HSAM5209I MEMBER member TOO LARGE:
Explanation: The specified library member resides
neither in the library concatenation of DD name
HSAPLIB when this message is preceded by message
IEF761I nor in the library of the PARMLIB
concatenation.
Explanation: The indicated member contains more
than 10240 lines of data.
The variable member shows the name of the member
that could not be found.
The variable member shows the name of the member
being processed using the MVS PARMLIB service.
System action: The data is truncated after line 10239.
Operator response: None.
System action: Processing continues.
System programmer response: None.
Operator response: Inform your system programmer.
Module: HSAPSIPL
System programmer response: Either make sure that
the member is available or change the value of the
keyword member to a suffix that is available. If the
default member HSAPRM00 cannot be found, copy it
from the SA z/OS library SINGSAMP to a library of
the appropriate concatenation.
Module: HSAPSPLM
HSAM5210I MEMBER member EMPTY:
Explanation: The indicated member has no data.
The variable member shows the name of the member
being processed using the MVS PARMLIB service.
System action: None.
Operator response: None.
HSAM5207I PARMLIB SERVICE FAILED WHEN
READING member, RC=rc Reason=rsn.
Explanation: During initialization of the automation
manager the MVS PARMLIB service failed.
The variable member shows the name of the member
being processed when the MVS PARMLIB service
failed.
The variable rc shows the value of the return code.
The variable rsn shows the value of the reason code.
System action: Processing continues.
Operator response: Inform your system programmer.
System programmer response: Refer to z/OS MVS
Assembler Services Reference for information about the
reason and return codes.
System programmer response: None.
Module: HSAPSIPL
HSAM5211I MEMBER member FOUND IN dsn.
Explanation: The indicated member has been found in
the indicated data set of the PARMLIB concatenation.
The variable member shows the name of the member
being processed using the MVS PARMLIB service.
The variable dsn shows the data set name that the
member has been read from.
System action: None.
Operator response: None.
System programmer response: None.
Module: HSAPSPLM
Module: HSAPSIPL
HSAM5208I INVALID STRING FOUND IN member:
string.
HSAM5212E I/O ERROR READING MEMBER
member.
Explanation: The parser service detected more than
one keyword in a single line of a member.
Explanation: An I/O error occurred when trying to
read the indicated PARMLIB member.
The variable member shows the name of the member
where the error occurred.
System action: All keywords specified in the string
are ignored.
Operator response: Inform your system programmer.
System programmer response: Correct the line in the
library member member (see the preceding IEE252I
message)
The variable member shows the name of the member
being processed using the MVS PARMLIB service.
System action: None.
Operator response: Inform your system programmer.
System programmer response: Correct the problem
and re-run the program.
Module: HSAPSIPL
Module: HSAPSPLM
Chapter 8. Messages HSAM1000I to HSAM5411I
169
HSAM5213E • HSAM5400I
HSAM5213E VALUE MISSING FOR KEYWORD
keyword.
Explanation: A library member (see the preceding
IEE252I message) or the PARM parameter of the
automation manager startup procedure contains a
keyword that has no value defined.
The variable keyword shows the name of the
keyword.
System action: The keyword is ignored.
Operator response: Inform your system programmer.
System programmer response: Correct the value of
the keyword depending on where it is specified.
Module: HSAPSPLM
concatenation of the automation manager startup
procedure and that the module is catalogued in this
library. Then, restart the automation manager.
Module: HSAPICB9
HSAM5301E MESSAGE msgno NOT FOUND IN
MODULE module.
Explanation: The message service of SA z/OS could
not find the indicated message number in the message
module.
The variable msgno shows the message number that
could not be found in the indicated message
module.
The variable module shows the name of the module
that does not contain the indicated message number.
HSAM5214I THE NEXT MESSAGES APPLY TO
MEMBER member.
System action: Processing continues.
Explanation: The library member (see the preceding
IEE252I message) contains at least one improper
specification. This message is followed by further
HSAM52nn messages.
System programmer response: Make sure that the
indicated module is in the correct SA z/OS library.
The variable member shows the name of the member
being processed using the MVS parmlib service.
System action: Processing continues.
Operator response: Inform your system programmer.
Module
Library
Concatenation
HSAAMME
SINGMOD2
LNKLST
HSAAMLE
SINGMOD1
STEPLIB
INGAMYE
SINGMOD2
LNKLST
Operator response: None.
System programmer response: None.
Module: HSAPSPLM
Verify that this library is part of the corresponding
concatenation. In case two versions of SA z/OS exist in
the concatenation ensure that the latest version
precedes the older version.
HSAM5215I THE NEXT MESSAGES APPLY TO
PARM STRING.
Module: HSAPSMSG
Explanation: The PARM parameter of the startup
procedure contains at least one improper specification.
This message is followed by further HSAM52nn
messages.
HSAM5400I logname LOG REQUEST request FAILED.
RC=rc, RSN=reason.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: HSAPSPLM
HSAM5300E MESSAGE MODULE module NOT
FOUND.
Explanation: The automation manager initialization
routine could not load the required message module.
The variable module shows the name of the module
that could not be found.
System action: The automation manager terminates.
Operator response: Inform your system programmer.
System programmer response: Make sure that the
SA z/OS library SINGMOD1 is the STEPLIB
170
System Automation for z/OS Messages and Codes:
Explanation: The request request to the log logname
ended with the unexpected reason code reason.
System action: Processing continues. Depending on
the reason code the affected log is marked either
permanently unavailable:
v 0409
v 040A
v 080C
v 080D
v 0813
v 081A
v 081F
v 0820
v 082E
v 0843
v 0850
v 0851
HSAM5401E • HSAM5406I
v 0853
v 085D
v 0890
v 08E2
v 08E3
or temporarily unavailable:
v 0406
v 0860
v 0861
System programmer response: Define the structure
strname in the policy and activate the policy. Then, start
a secondary automation manager and initiate a
takeover. In addition, recycle the affected NetView(s).
Module: HSAPSSLG
HSAM5403I STREAM streamname IS NOT DEFINED
IN THE LOGR POLICY.
Explanation: The log stream name streamname has not
been defined in the LOGR policy.
v 0863
System action: Processing continues. The log is
marked permanently unavailable.
v 0864
Operator response: Inform your system programmer.
v 0865
System programmer response: Define the log stream
streamname in the LOGR policy. Then, start a secondary
automation manager and initiate a takeover. In
addition, recycle the affected NetView(s).
v 0862
v 0867
v 0868
v 0891
Operator response: Inform your system programmer.
System programmer response: See “return and reason
codes” of the related IXG... macro in z/OS MVS
Authorized Assembler Service Reference for further
analysis. In case the log is marked permanently
unavailable and the problem can be solved, start a
secondary automation manager and initiate a takeover.
In addition, recycle the affected NetView(s).
Module: HSAPSSLG
HSAM5401E SYSTEM LOGGER HAS
INSUFFICIENT ACCESS AUTHORITY
TO log. COMPONENT TRACE.
Explanation: The system logger address space does
not have access authority to the coupling facility
structure associated with the log stream log.
System action: Processing continues. The log is
marked permanently unavailable.
Operator response: Inform your system programmer.
System programmer response: Make sure the system
logger address space has SAF access to the structure.
Then, start a secondary automation manager and
initiate a takeover. In addition, recycle the affected
NetView(s).
Module: HSAPSSLG
HSAM5404I XES FAILED. DIAG1=XES_RC,
DIAG2=XES_RSN.
Explanation: A severe cross-system extended services
(XES) error has occurred.
System action: Processing continues. The affected log
is marked permanently unavailable.
Operator response: Inform your system programmer.
System programmer response: Analyze the XES
return code and the XES reason code.
Module: HSAPSSLG
HSAM5405I text
Explanation: The message is issued in conjunction
with message HSAM5400I and reason code 081F. The
reason code indicates that the system logger
encountered an internal problem while processing the
LOGR couple data set. The two or more messages
represent the content of the 'answer area' that must be
provided by each logger request.
System action: None.
Operator response: Inform your system programmer.
Module: HSAPSSLG
System programmer response: Contact your IBM
Support Center.
HSAM5402I STRUCTURE STRNAME IS NOT
DEFINED IN THE CFRM POLICY.
Module: HSAPSSLG
Explanation: The structure strname is not defined in
the currently active CFRM policy.
HSAM5406I Some blocks of log logname have been
deleted.
System action: Processing continues. The log is
marked permanently unavailable.
Explanation: The message is issued in conjunction
with message HSAM5400I and the reason codes 0408
and 085C. To satisfy a write log request, log blocks
older than six days have been deleted. The deletion is
Operator response: Inform your system programmer.
Chapter 8. Messages HSAM1000I to HSAM5411I
171
HSAM5407I • HSAM5411I
repeated day by day until the free space is large
enough to satisfy the write request.
The variable logname shows the name of the log that
blocks have been deleted from.
System action: None.
Operator response: None.
System programmer response: None.
Module: HSAPSSLG
HSAM5407I logname LOG IS NOT AVAILABLE.
Explanation: The system logger address space is not
available for the remainder of this IPL.
System action: Processing continues. All logs are
marked permanently unavailable.
Module: HSAPSSLG
HSAM5410E logname LOG REQUEST request FAILED.
RC=rc, RSN=reason, Type=type.
Explanation: The request request to the log logname
ended with the unexpected reason code reason.
System action: Processing continues. The log logname
is marked permanently unavailable.
Operator response: Inform your system programmer.
System programmer response: Check the system log
for associated IXG prefixed messages. Check the
relevant zOS MVS System Messages manual for the
IXG message details. If you cannot resolve the problem,
contact your IBM Support Center.
Module: HSAPSSLG
Operator response: None.
System programmer response: None.
HSAM5411I logname LOG HAS BEEN DELETED.
Module: HSAPSSLG
Explanation: The message is issued in conjunction
with message HSAM5400I and the reason codes 0405,
0407, 0408, and 085C. The whole log must be deleted to
satisfy a write log request.
HSAM5408I logname LOG WAS TEMPORARILY
UNAVAILABLE FROM from_time TO
to_time.
Explanation: While the specified log was temporarily
unavailable, a WRITE request to the log had to be
rejected. After the log has become available again, this
message is written to the log documenting that one or
more WRITE requests were not logged.
The variable logname shows the name of the log that
was not available.
The variables from_time and to_time show the time
span during which the log was not available.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: HSAPSSLG
HSAM5409I logname LOG HAS BEEN DELETED
FROM THE FIRST GAP.
Explanation: The message is issued in conjunction
with message HSAM5400I and the reason codes 0402,
0403, 0836, and 084B. The log has been deleted from
the first gap being detected when reading the log from
the most recent data to the earliest data. One reason
could be that the log stream has been defined with an
incorrect VSAM share option, for example, SHR(1 3).
System action: None.
Operator response: Inform your system programmer.
System programmer response: Check and correct the
VSAM definitions of the affected log stream.
172
System Automation for z/OS Messages and Codes:
System action: None.
Operator response: None.
System programmer response: None.
Module: HSAPSSLG
Chapter 9. Messages IHVA100I to IHVZ760
IHVCnnn Messages without a message type indicate that these messages are
displayed on console without its message ID.
IHVA100I
Cannot UNALLOCATE/DETACH device
number bb (LSN aa).
Explanation: I/O operations sent an UNALLOCATE
(MVS) or DETACH (VM) for the specified switch,
which failed. This occurs when an attempt is made to
close a switch that does not have a specified DDNAME
allocated, or the switch was never opened.
The variable aa shows the switch device number.
The variable bb shows the logical switch number.
User response: This message is informational. Actions
proceed. Check whether the DDNAME associated with
the switch device number is still allocated.
IHVA200I
Error detected on switch aa.
Explanation: I/O operations has detected an error on
the indicated switch. This only appears on the message
log.
The variable aa shows the switch device number.
User response: None.
IHVB900I
STORAGE OBTAIN failed in aa.
Explanation: There has been a STORAGE OBTAIN
failure. This could have been caused by an operating
system problem.
The variable aa shows the name of the module.
System programmer response: Determine why there
was not enough storage and correct the condition.
Restart I/O operations.
IHVB990I
STORAGE RELEASE failed in aa.
Explanation: There has been a STORAGE RELEASE
failure. The error indicates a system storage problem.
The variable aa shows the name of the module.
User response: Report the problem to your IBM
Support Center.
IHVC000I
aa command successful.
Explanation: The command completed successfully.
The variable aa shows the name of the command.
IHVA201I
Switch aa Port bb state changed.
Explanation: I/O operations detected a change in the
status of the indicated port. This appears only on the
message log.
The variable aa shows the switch number.
The variable bb shows the port address.
User response: None.
IHVB001I
Elapsed times
Explanation: This message is the header message of a
series of IHVB002I messages.
User response: None.
IHVB002I
aa bb:cc:dd.ee
Explanation: This message shows the elapsed time of
a particular module that the module has consumed
during the startup process of I/O operations.
The variable aa shows the module's short name.
The variables bb, cc, dd, and ee show the elapsed
time.
User response: None.
User response: None.
IHVC001I
aa command successful, RC=bb RSN=cc.
Explanation: The command completed, but some
condition was detected that caused a nonzero return
code. For example, if the FORCE option was used and
a host voted no, the command would still be processed.
The variable aa shows the name of the command.
The variable bb shows the return code that was
issued.
The variable cc shows the reason code that was
issued.
User response: Refer to the subsequent message, or
use the DISPLAY RESULTS command to determine
what condition was detected that caused the nonzero
return code.
IHVC002I
aa command failed, RC=bb RSN=cc.
Explanation: The command failed.
The variable aa shows the name of the command.
The variable bb shows the return code.
The variable cc shows the reason code.
User response: Use the DISPLAY RESULTS command
© Copyright IBM Corp. 1996, 2014
173
IHVC080I • IHVC211
to determine why the command failed. Correct the
condition and reenter the command.
User response: None.
IHVC204I
IHVC080I
Command not supported by this
host’s aa level
Explanation: The command failed because it is not
supported at this level of operating environment.
The variable aa shows the MVS release.
BACKOUT
VARYs:
aa
bb
(cc,dd)(ee,ff)( gg,hh)
Explanation: This message is the output of a DISPLAY
HOST command.
The variable aa shows the number of attempted
Varys.
The variable bb shows the number of failed Varys.
User response: None.
The variables cc, ee and gg show the device number.
IHVC100I
aa failed bb authority for cc.
Explanation: The specified user does not have the
specified access authority for the command
The variables dd, ff and hh show the CHPID.
User response: None.
The variable aa shows the user ID.
IHVC205I
The variable bb shows the authorization level (read,
update, control).
Explanation: An attempt was made to chain a port to
itself. The CHAIN command was specified with the
same port on the same switch. This is not allowed.
The variable cc shows the RACF entity name.
User response: Contact your security administrator for
the proper authorization.
aa
IHVC200I
bb
cc
Explanation: This message is the output of Display
commands.
Cannot CHAIN a port to itself
User response: Check the parameters on the CHAIN
command.
IHVC206I
aa
bb
Explanation: This message is the output of display
commands.
The variable aa shows the switch device number.
The variable aa shows the TCP/IP host name.
The variable bb shows the logical switch number.
The variable bb shows the IP address of this host,
either in IPv4 format or IPv6 format.
The variable cc shows the switch unique identifier.
User response: None.
User response: None.
IHVC201I
aa/bb
cc
dd
Explanation: This message is the output of a DISPLAY
HOST command.
IHVC210
aa
Connected to:
cc
Explanation: This message is the output of a DISPLAY
CHP command.
The variable aa shows the VTAM name.
The variable aa shows the port.
The variable bb shows the TCP/IP host name.
The variable bb shows the port status.
The variable cc shows the name of the sysplex.
The variable cc shows the port name.
The variable dd shows the name of the system.
bb
User response: None.
User response: None.
IHVC211
IHVC202I
aa
bb cc dd ee ff
Explanation: This message is the output of a Display
command.
Chained to:
aa bb
cc dd
ee
Explanation: This message is the output of a DISPLAY
CHP command.
The variable aa shows the switch device number.
The variable aa shows the VTAM name.
The variable bb shows the logical switch number.
The variable bb shows the Version of I/O operations
on this host (format Vx).
The variable cc shows the port.
The variable cc shows the Release of I/O operations
on this host (format Ry).
The variable ee shows the port name.
The variable dd shows the physical ID of this host.
The variable ee shows the name of the sysplex.
The variable ff shows the name of the system.
174
System Automation for z/OS Messages and Codes:
The variable dd shows the port status.
User response: None.
IHVC212 • IHVC225
The variable cc shows the port.
IHVC212
(aa,bb)(cc,dd)(ee,ff)( gg,hh)
Explanation: This message is the output of a DISPLAY
VARY command.
The variables aa, cc, ee and gg show the device
number.
The variables bb, dd, ff and hh show the CHPID.
User response: None.
The variable dd shows the port status.
The variable ee shows the port name.
User response: None.
IHVC221
Port
Explanation: This message is the output of a DISPLAY
CHP command.
User response: None.
IHVC213
aa caused VARYs by bb on cc
Explanation: This message is a header line for the
DISPLAY VARY command, which gives information
about the status of the previous operation that caused a
configuration change. This message gives information
regarding the last command entered and the user who
entered it.
IHVC222
aa connected to: bb cc dd ee
Explanation: This message is the output of a DISPLAY
NAME or DISPLAY PORT command.
The variable aa shows the midport of chain.
The variable bb shows the port name.
The variable aa shows the last command entered.
The variable cc shows the port.
The variable bb shows the user ID of the user who
entered the command.
The variable dd shows the port status.
The variable cc shows the system ID where the last
command was entered.
User response: None.
IHVC214
ONLINE
aa
bb (cc,dd,"ee")
The variable aa shows the number of attempted
Varys.
The variable bb shows the number of failed Varys.
The variable cc shows the device number.
The variable dd shows the CHPID.
The variable ee shows the reason why VARY failed.
aa
bb
(cc,dd,"ee")
Explanation: This message is the output of a DISPLAY
VARY command.
The variable aa shows number of attempted Varys.
The variable bb shows the number of failed Varys.
The variable cc shows the device number.
The variable dd shows the CHPID.
The variable ee shows the reason why VARY failed.
User response: None.
IHVC220
aa chained to:
cc
dd ee ff
bb
Explanation: This message is the output of a DISPLAY
NAME or DISPLAY PORT command.
The variable aa shows the midport of chain.
The variable bb shows the switch device number.
The variable cc shows the logical switch number.
The variable dd shows the port.
The variable ee shows the port status.
The variable ff shows the port I/O definition.
User response: None.
User response: None.
BACKOUT
User response: None.
IHVC223
Explanation: This message is the output of a DISPLAY
VARY command.
IHVC215
The variable ee shows the port I/O definition.
Cntl unit data:aa bb
IHVC224
Explanation: This message is the output of a DISPLAY
DEV command.
The variable aa shows the switch device number.
The variable bb shows the logical switch number.
bb cc dd
Explanation: This message is the output of a DISPLAY
CHP command.
The variable aa shows the midport of chain.
The variable bb shows the port.
The variable cc shows the port status.
The variable dd shows the port name.
User response: None.
IHVC225
cc dd ee
aa connected to:
aa chained to:bb cc
dd
ee
ff
Explanation: This message is the output of a DISPLAY
CHP command.
The variable aa shows the midport of chain.
The variable bb shows the switch device number.
The variable cc shows the logical switch number.
Chapter 9. Messages IHVA100I to IHVZ760
175
IHVC230I • IHVC243
The variable dd shows the port.
User response: None.
The variable ee shows the port status.
The variable ff shows the port name.
IHVC235
User response: None.
IHVC230I
Switch(es) reported an error, display
data may be inaccurate.
Explanation: This message is the output of a DISPLAY
command when a switch reported an error.
User response: Enter DISPLAY SWITCH * to display the
status of all switches.
IHVC231
aa caused CONFIGs by bb on cc
Explanation: This message is a header for the
DISPLAY VARY command.
The variable aa shows the last command entered.
The variable aa shows the number of attempted
Configs.
The variable bb shows the number of failed Configs.
The variables cc, dd, ee, ff, gg, hh, ii, and jj show the
CHPIDs.
User response: None.
IHVC240
A/P Port
The variable cc shows the system ID where the last
command was entered.
IHVC241
Config type Tried
(Chp)
Failed 1st aa failures
The variable aa shows the number of Configs
displayed.
User response: None.
OFFLINE
gg,hh,ii,jj)
bb
(cc,dd,ee,ff,
The variable aa shows the number of attempted
Configs.
The variable bb shows the number of failed Configs.
The variables cc, dd, ee, ff, gg, hh, ii, and jj show the
CHPIDs.
The variable aa shows either A or P (allowed or
prohibited).
The variable cc shows the port name.
The variable dd shows the I/O-defined type.
User response: None.
There are no port names on switch aa.
Explanation: There are no port names on the specified
switch.
User response: None.
IHVC243
Chained to:
bb
cc dd ee
aa
Explanation: This message is the output of a DISPLAY
command.
The variable bb shows logical switch number.
aa
bb
(cc,dd,ee,ff,
Explanation: This message is the output of the
DISPLAY VARY command.
The variable aa shows the number of attempted
Configs.
The variable bb shows the number of failed Configs.
The variables cc, dd, ee, ff, gg, hh, ii, and jj show the
CHPIDs.
176
cc
The variable aa shows the switch device number.
User response: None.
BACKOUT
gg,hh,ii,jj)
dd
The variable aa shows the switch device number.
Explanation: This message is the output of the
DISPLAY VARY command.
IHVC234
bb
Explanation: This message is the output of a DISPLAY
NAME or DISPLAY PORT command.
IHVC242I
aa
aa
The variable bb shows the port.
Explanation: This is a header for the DISPLAY VARY
command.
IHVC233
I/O-Def Port name
Explanation: This is a header for the DISPLAY NAME
or DISPLAY PORT command.
User response: None.
IHVC232
bb (cc,dd,ee,ff,
Explanation: This message is the output of the
DISPLAY VARY command.
The variable bb shows the user ID of the user who
entered the command.
User response: None.
aa
ONLINE
gg,hh,ii,jj)
System Automation for z/OS Messages and Codes:
The variable cc shows the port.
The variable dd shows port status.
The variable ee shows the port I/O definition.
User response: None.
IHVC244I • IHVC277
Flags Internal flags
IHVC244I
(aa,bb,cc,dd,ee,ff,gg,hh)
Explanation: This message is the output of the
DISPLAY VARY command.
The variables aa, bb, cc, dd, ee, ff, gg, and hh show
the CHPIDs.
User response: None.
IHVC270I
No FAILed VARYs or CONFIGs
detected on previous command.
Explanation: This message is the output of a DISPLAY
command.
User response: None.
IHVC274
LIC
EC level Sense bytes
0-15
Explanation: This message is the second header line
for the DISPLAY SWITCH * DETAIL command.
LIC LIC version and release
EC level
Engineering change level
Sense
Switch sense information
User response: None.
User response: None.
IHVC275
IHVC271
SYNC SWITCH detected VARYs by aa
on bb
Explanation: This message is a header for the
DISPLAY VARY command. It informs the user that the
SYNC SWITCH command was performed with the
NOPROCESS option and Varys were detected.
The variable aa shows the user ID of the user who
entered the command.
The variable bb shows the system ID where the last
command was entered.
User response: None.
IHVC272
Explanation: This message is a header for the
DISPLAY VARY command. It informs the user that the
SYNC SWITCH command was performed with the
NOPROCESS option and ESCON Converter Model 1
CHPIDs were detected.
Sense bytes
Explanation: This message is the third header line for
the DISPLAY SWITCH * DETAIL command.
Ins
Number of installed ports
Imp Number of implemented ports
1st
Number of first implemented port
LP
Number of logical paths
Sense
Switch sense information
User response: None.
IHVC276
SYNC SWITCH detected CONFIGs by
aa on bb
Ins Imp 1st LP
16-31
aa bb
cc dd ee ff gg
Explanation: This message is the output of a DISPLAY
SWITCH * DETAIL command.
The variable aa shows the switch device number.
The variable bb shows the logical switch number if
available.
The variable cc shows the node element descriptor
(NED).
The variable aa shows the user ID of the user who
entered the command.
The variable dd shows the NED's unique identifier.
The variable bb shows the system ID where the last
command was entered.
The variable ff shows the switch status code.
User response: None.
IHVC273
Swch LSN Unique id
Tag Status
The variable ee shows the switch status information.
The variable gg shows the internal status flags.
User response: None.
SC Flags
Explanation: This message is the first header line for
the DISPLAY SWITCH * DETAIL command.
Swch
Switch device number
LSN Logical switch number
Unique id
Node element descriptor
Tag NED unique identifier
Status
Status information
SC
Status code
aa bb
IHVC277
cc dd ee ff
Explanation: This message is the output of a DISPLAY
SWITCH * DETAIL command.
The variable aa shows the LIC version and release.
The variable bb shows the EC level.
The variables cc, dd, ee, and ff show 4 bytes of sense
data in hexadecimal format.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
177
IHVC278 • IHVC407I
aa bb cc dd ee ff gg hh
IHVC278
Explanation: This message is the output of a DISPLAY
SWITCH * DETAIL command.
The variable aa shows the number of installed ports.
The variable bb shows the number of implemented
ports.
The variable cc shows the first implemented port
number.
The variable dd shows the number of logical paths.
The variables ee, ff, gg, and hh show 4 bytes of sense
data in hexadecimal format.
User response: None.
IHVC301
Port name aa already on this switch.
Explanation: The specified port name is already
defined on the switch.
The variable aa shows the port name.
User response: Do not use duplicate names on the
same switch.
IHVC400I
No switches known to I/O-OPS.
User response: Use the DISPLAY RESULTS command
for more information. Determine the correct operands
and reenter the command.
IHVC403I
aa operand(s) do not apply to switch bb.
Explanation: A switch device number was specified
with the command, but that switch was not affected by
the command. For example, the command was BLOCK
Printer_1 0123, but the switch device number 0123
does not have a port with the name Printer_1.
The variable aa shows the name of the command.
The variable bb shows the switch device number.
User response: Use the DISPLAY RESULTS command
for more information. Determine why the switch was
not affected by the operands. Reenter the command
with the correct operands.
IHVC404
Current switch data unavailable
Explanation: I/O operations did not have an
up-to-date copy of the switch data and was unable to
refresh its own database. The I/O operations data for
the switch is not correct, and commands cannot be sent
to the switch.
Explanation: There are no switches defined in the
IOCP data. This means there are no switches available
to receive commands. I/O operations cannot be used to
send commands to switches. However, some I/O
operations display capabilities are still available.
User response: Enter the RESET SWITCH command,
which will attempt to synchronize the database. If the
RESET SWITCH command cannot synchronize the
database, contact your system administrator.
User response: None.
IHVC405
IHVC401I
Host(s) unable to process the aa
command.
Explanation: One or more hosts running I/O
operations were unable to process the command. This
may be due to the Varys that were requested, VTAM or
TCP/IP communication problems, or other conditions
preventing the hosts from processing the command.
The variable aa shows the name of the command
that could not be processed.
User response: Use the DISPLAY RESULTS and
DISPLAY HOST commands to determine why the hosts
could not process the command and to determine the
status of the hosts.
IHVC402I
aa operand(s) do not apply to any
switch.
Explanation: Asterisk (*) was specified as the switch
device number, indicating that the command should be
sent to all switches. The operands given in the
command are not found on any switch. For example, if
the command was BLOCK DA *, there was no switch that
had the name DA defined.
The variable aa shows the name of the command.
178
System Automation for z/OS Messages and Codes:
Switch data has been changed
Explanation: I/O operations did not have an
up-to-date copy of the switch data for this switch but
was able to normally refresh its own database.
User response: Use the Display commands to
determine what might have changed and then reenter
the command.
IHVC406I
Some switches unable to process aa.
Explanation: The command was sent to the switches,
but one or more switches could not successfully process
the command.
The variable aa shows the name of the command.
User response: Use the DISPLAY RESULTS and the
DISPLAY SWITCH commands to determine which
switches could not process the command and what
conditions were detected that prevented them from
processing the command.
IHVC407I
Host(s) and switch(es) unable to process
aa.
Explanation: Some hosts and some switches were
unable to successfully process the command.
The variable aa shows the name of the command.
IHVC409 • IHVC419
User response: Use the DISPLAY RESULTS command
to determine which hosts and which switches could not
process the command.
User response: Reenter the CONNECT command with
2 unique ports.
IHVC415
IHVC409
Port aa does not exist
Explanation: A port was specified with a command,
but the port is outside the valid range of ports defined
by the hardware.
The variable aa shows the name of the port that
does not exist.
User response: Use the DISPLAY RESULTS command
for more information. Determine the correct port to be
used and reenter the command.
IHVC410I
Commands cannot affect port aa
(switch control unit)
Explanation: A port was specified with a command,
but the port is the control unit port of the switch.
Commands cannot affect the switch control unit port.
Port aa already CONNECTed
Explanation: An attempt to connect port aa failed
because port aa is already connected to another port.
The variable aa shows the name of the port.
User response: Determine whether the existing
connection should be disconnected. If so, enter the
DISCONNECT command. Then reenter the CONNECT
command.
IHVC416
Port aa not installed, cannot
CONNECT
Explanation: An attempt to connect port address aa
failed because port address aa is not installed.
The variable aa shows the name of the port address.
User response: Determine the correct port to be used
and reenter the command.
User response: Determine whether the correct port
address was specified with the CONNECT command.
If so, contact your system administrator to determine
why the port is not installed (physically not in the
switch).
IHVC411
IHVC417
The variable aa shows the control unit port.
Unable to return this switch to
original state
Explanation: A command was sent to multiple
switches and processed, but there was a reason to stop
the command and return this switch to its original state
(the state it was in before the command was sent). This
message was issued because I/O operations was unable
to return this switch.
User response: Enter the command that returns the
switch to its previous state. For example, if you entered
BLOCK (C0), the command to return the switch is
UNBLOCK (C0).
IHVC413I
I/O-OPS internal error
Explanation: I/O operations was unable to update its
database to include the new port name that was
defined.
User response: Enter a DISPLAY NAME command for
the port name and determine whether I/O operations
processed the command correctly. If not, reenter the
command. If the same error recurs, notify your system
programmer.
IHVC414
Attempted to CONNECT port aa to
itself
Explanation: An attempt was made to connect a port
to itself. This is not a valid operation.
The variable aa shows the name of the port.
No available paths to the switch for
the command
Explanation: There are no available paths for I/O
operations to send the command to the switch. The
command would remove the last existing path. This
could happen if there is only one path defined to the
switch and the command attempts to block or connect
this path. Furthermore, if more than one path is
defined but all the other paths have been blocked or
connected, there is only one path left, which cannot be
removed.
User response: Verify that this command is necessary.
Then reenter the command with the FORCE option
from another I/O operations that has multiple paths to
the switch.
IHVC418I
Requested change not allowed at the
switch.
Explanation: The command requested a change that
would have been rejected by the switch. For example,
the BLOCK command attempted to block the control
unit port of the switch.
User response: Enter the DISPLAY RESULTS
command to determine what was incorrect.
IHVC419
No port names exist which can be
affected by this command
Explanation: Either no port names are defined or the
only port name is for the control unit port.
Chapter 9. Messages IHVA100I to IHVZ760
179
IHVC420 • IHVC428I
User response: Refer to the command section to
determine the correct use of the command.
IHVC420
Attempted to ALLOW port aa to
itself
Explanation: The Allow command was specified with
2 identical ports.
The variable aa shows the name of the port.
IHVC421I
Switch(es) data has been changed.
Explanation: Changes have been made to one or more
switches since you entered the last command or status
of a host connected to the switch changed.
User response: Use the Display commands to
determine what might have changed and then reenter
the command.
operator's console log for detailed messages. If the I/O
operations command failed and it is determined that
the switch or configuration changes do not affect the
command, reenter the command.
IHVC425I
Explanation: A failure was detected during the update
of the I/O operations database. This may have been
caused by a problem obtaining channel subsystem
configuration information. If Vary Paths were
performed, these requests may have been based on old
database information.
User response: Consult the system operator’s console
log to determine the cause of the system error that
resulted in the database refresh failure.
IHVC426I
IHVC422I
A user obtained the I/O-OPS lock and
processed commands.
Explanation: Another user took control of I/O
operations command processing, processed I/O
operations commands, and then released control of
command processing with an UNLOCK command.
User response: Use the Display commands to
determine what might have changed. Then reenter the
command.
IHVC423I
Channel subsystem configuration data
has changed.
Explanation: During the processing of an I/O
operations command, a change was detected in the
channel subsystem configuration data. This could be
the result of configuration changes made in PR/SM
mode or through MVS Dynamic I/O. I/O operations
refreshes its view of the configuration when such
changes are made. During this refresh, user commands
cannot be processed.
User response: Use the display commands (for
example, DISPLAY CHP) to determine the change, or
consult the system operator's console log for detailed
messages. If the I/O operations command failed and it
is determined that the configuration data changes do
not affect the command, reenter the command.
IHVC424I
Switch and channel subsystem
configuration data has changed.
Explanation: During the processing of a I/O
operations command, a change was detected in the
channel subsystem configuration data and the data
associated with a switch.
User response: Use the Display commands (such as
DISPLAY SWITCH or DISPLAY CHP) to determine
what might have changed or consult the system
180
System Automation for z/OS Messages and Codes:
Refresh of I/O-OPS configuration data
failed.
Current switch and channel
configuration data unavailable.
Explanation: During the processing of a I/O
operations command, a change was detected in the
channel subsystem configuration data, and the current
switch data was not obtained.
User response: Use the Display commands (such as
DISPLAY SWITCH or DISPLAY CHP) to determine
what might have changed or consult the system
operator's console log for detailed messages. If the I/O
operations command failed and it is determined that
the switch or configuration changes do not affect the
command, reenter the command.
IHVC427I
aa does not exist on switch bb.
Explanation: The specified port name does not exist
on the specified switch.
The variable aa shows the name of the port that
does not exist.
The variable bb shows the switch device number.
User response: Use the DISPLAY NAME command to
see whether the port name exists on any other switch.
IHVC428I
Current switch data unavailable.
Explanation: I/O operations did not have an
up-to-date copy of the switch data and was unable to
refresh its own database. The I/O operations data for
the switch is not correct and commands cannot be sent
to the switch.
User response: Enter the RESET SWITCH command,
which will attempt to synchronize the database. If the
Reset Switch command cannot synchronize the
database, contact your system administrator.
IHVC429I • IHVC501
IHVC429I
Disable function for switch aa not in
effect.
Explanation: This switch is not enabled to support the
disable function of the REMOVE SWITCH command.
The variable aa shows the switch device number.
IHVC430I
Switch(es) have been REMOVEd by
another user.
Explanation: One or more switches have been
removed from your system. This was the result of a
user on another system entering the REMOVE SWITCH
command.
User response: Use the DISPLAY RESULTS command
to determine which switches have been removed.
IHVC431
Switch has been REMOVEd
Explanation: This switch has been removed from the
system.
User response: None.
IHVC432I
Switch(es) have been RESTOREd by
another user.
Explanation: One or more switches have been restored
to your system. This was the result of a user on
another system entering the RESTORE Switch
command.
User response: Use the DISPLAY RESULTS command
to determine which switches have been restored.
IHVC433
Switch has been RESTOREd
Explanation: This switch has been restored to the
system.
User response: None.
IHVC434
Name aa not valid
Explanation: The name specified contains characters
that are not supported by the current switch
configuration.
The variable aa shows the name of the port.
The variable bb shows the name of the second fibre
channel bridge port.
User response: Prohibit the dynamic connection
between the fibre channel bridge ports.
IHVC436
Cannot connect aa, because it is a
fibre channel port
Explanation: An attempt to connect a port to the fibre
channel port aa failed because a fibre channel port
cannot be part of a static connection.
The variable aa shows the name of the fibre channel
bridge port.
User response: Remove the static connection from the
fibre channel port.
IHVC437
Settings on switch prevent
configuration changes
Explanation: Someone has selected a management
setting at the switch’s local console that prevents
control of the switch via the interfaces that I/O
operations uses. I/O operations can continue to provide
configuration information about this switch. However,
I/O operations cannot change any configuration
setting, for example, port connectivity hierarchy
attributes or port names.
User response: Check whether the switch setup was
done correctly. Some switch models support multiple
types of remote management but require a customer
setup choice to designate exactly one management
agent to be able to change the switch configuration.
This can prevent uncoordinated changes. I/O
operations can provide its system integrated switching
protection only when switch settings allow it to control
the switches.
IHVC500
Swch devn LSN Unique
id
Status
Code
Explanation: This is a header for the DISPLAY
RESULTS command that shows the switch device
number, logical switch number, and the switch unique
identifier.
User response: None.
User response: Change the port name.
IHVC501
IHVC435
Attempted to ALLOW FC port aa to
FC port bb
Explanation: An attempt to allow a dynamic
connection between port aa and another fibre channel
port bb failed because both are fibre channel bridge
ports.
The variable aa shows the name of the first fibre
channel bridge port.
aa
bb
cc dd ee
Explanation: This is a header for the DISPLAY
RESULTS command:
The variable aa shows the switch device number.
The variable bb shows the logical switch number.
The variable cc shows the switch unique identifier.
The variable dd shows the switch status.
The variable ee shows the status code.
Chapter 9. Messages IHVA100I to IHVZ760
181
IHVC502 • IHVC518I
User response: None.
IHVC502
Switch not defined as a device
Explanation: The switch in the previous command has
not been defined to IOCP as a device. I/O operations
cannot communicate with this switch.
IHVC513I
Another user has the I/O-OPS lock
Explanation: This host has detected that an I/O
operations user on another system holds the I/O
operations lock.
System programmer response: Determine whether
this switch should be defined to IOCP and do so if
needed.
User response: From the host issuing this message,
enter I/O operations commands to determine which
user on which system has the lock. Contact that user to
determine when the user will enter the Unlock
command to release the lock.
IHVC505I
IHVC514I
No failures detected by this host
Explanation: The host did not detect any problems
with sending the command.
User response: None.
Another user is processing an
I/O-OPS command
Explanation: This host has detected that an I/O
operations user on another system is processing I/O
operations commands.
User response: None.
User response: From the host issuing this message,
enter I/O operations commands to determine which
user on which system is processing I/O operations
commands. Contact that user to determine when
processing is done and, if required the UNLOCK
command has been entered to release the lock.
IHVC510I
IHVC515I
IHVC506
No failures detected by this switch
Explanation: No problems were detected by the
specified switch.
I/O-OPS logical/physical component
not working
Explanation: I/O operations’s logical-to-physical
coordination component is not working on the
specified host. This could be because the Vary
concentrator is not working properly.
VTAM or TCP/IP error while
broadcasting the command
Explanation: There was a VTAM or TCP/IP error
while I/O operations was trying to communicate with
another host.
User response: Report the problem to your IBM
Support Center.
User response: Check with your system operator to
see whether VTAM and TCP/IP are active and
functioning properly.
IHVC511I
IHVC516I
VTAM not running, command not
broadcast
Explanation: VTAM is not running. The command
could not be broadcast to I/O operations on other
systems. Message IHVI003, which was sent previously,
contains the VTAM OPEN ACB error return code.
VTAM or TCP/IP session NOT
established with this host
Explanation: A VTAM or TCP/IP session could not be
established with the host. Broadcasts to that system will
not be successful.
User response: Check with your system operator to
see whether VTAM has been installed and is active.
User response: Determine why a VTAM or TCP/IP
session could not be established and correct the
problem.
IHVC512I
IHVC517I
Backout failed
Explanation: While trying to return the system to its
initial state, some or all of the VARY commands that
were done could not be restored.
User response: Enter the DISPLAY VARY command
and use the list of failed Backout Varys to resend the
requests.
No response to the command
Explanation: This host did not respond to the
command it received from the primary host.
User response: Determine why there was no response
and correct the problem.
IHVC518I
Vote of 'NO' - critical resource
protected
Explanation: A host failed Vary Path requests.
User response: Enter the DISPLAY VARY command.
Then use the list of failed VARY requests to determine
182
System Automation for z/OS Messages and Codes:
IHVC519I • IHVC530I
which paths could not be varied. Free the devices and
reenter the command. If necessary, use the FORCE
option.
IHVC519I
Backout processing in progress
Explanation: This host is still in the process of backing
out the Varys from a previous command.
IHVC525I
This host has been RESET off
Explanation: This message is issued following some
Display commands if this host has been reset off.
User response: Either reset the host on or be aware
that Display command data might not be complete,
because the host is removed from participating in
consensus processing.
User response: None.
IHVC526I
IHVC520
Command not sent to this switch
Explanation: The command was not sent to the
switch. Either the command specified a switch other
than this one, or the command specified ports or port
names that were not defined for this switch.
User response: None.
IHVC522
Could not communicate with the
switch
Explanation: The switch did not respond (or
responded with a failure status) to the command that
was entered. Two of the probable causes are that a
prerequisite EC (engineering change) has not been
installed on the switch, or the operating system is not
at the minimum level required to support the
command.
System programmer response: Determine why the
command could not be sent to the switch and correct
the problem.
IHVC523
Could not write host names to the
switch
Explanation: I/O operations was unable to write its
VTAM and TCP/IP host names to the switch. This
means that other I/O operations programs will not be
able to find out about this host, and, therefore, will not
be able to start a VTAM or TCP/IP session with this
host.
System programmer response: Determine why the
command could not be sent to the switch and correct
the problem.
IHVC524
Switch data has been changed during
command execution
Refresh of I/O-OPS configuration
data failed
Explanation: A failure was detected during the update
of the I/O operations database. This may have been
caused by a problem obtaining channel subsystem
configuration information. If Vary Paths were
performed, these requests may have been based on old
database information.
User response: Consult the system operator’s console
log to determine the cause of the system error that
resulted in the database refresh failure.
IHVC527I
Channel subsystem configuration
data has changed
Explanation: During the processing of an I/O
operations command, a change was detected in the
channel subsystem configuration data. This could be
the result of configuration changes made in PR/SM
mode or through MVS Dynamic I/O. I/O operations
refreshes its view of the configuration when such
changes are made. During this refresh, user commands
cannot be processed.
User response: Use the Display commands (such as
DISPLAY CHP) to determine the change or consult the
system operator’s console log for detailed messages. If
the I/O operations command failed and it is
determined that the configuration data changes do not
affect the command, reenter the command.
IHVC528I
aa CHPID bb is online
Explanation: An attempt was made to affect a port
communicating with an ESCON channel converter.
When the ESCON channel in converter mode is online,
a BLOCK, DISCONNECT, UNCHAIN, or REMOVE
command causes a channel error.
The variable aa shows the CHPID type.
The variable bb shows the CHPID number.
Explanation: After I/O operations verified that it had
an up-to-date database, the switch data changed. When
I/O operations tried to process the command, it no
longer had the correct data.
User response: Configure the ESCON channel in
converter mode offline and reenter the command.
User response: Determine what data was changed on
the switch.
IHVC530I
Failed VARYs Offline: Tried Failed 1st 3
failures (Dev,Chp)
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Varys
tried, the number of Varys that failed, and the first
Chapter 9. Messages IHVA100I to IHVZ760
183
IHVC531I • IHVC539I
three device number/CHPID pairs that failed.
User response: None.
IHVC531I
Failed backout VARYs: Tried Failed 1st 3
Failures (Dev,Chp)
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Varys
tried, the number of Varys that failed, and the first
three device number/CHPID pairs that failed.
IHVC532I
bb
(cc,dd)(ee,ff)(gg,hh)
Explanation: This is Display command data that
shows the number of Varys attempted by the host, the
number of Varys that failed, and the first three device
number/CHPID pairs that failed.
The variable aa shows the number of attempted
Varys.
The variable bb shows the number of failed Varys.
The variable cc shows the device number of the first
CHPID.
The variable dd shows the first CHPID.
The variable ee shows the device number for the
second CHPID.
The variable ff shows the second CHPID.
The variable gg shows the device number of the
second CHPID.
The variable hh shows the third CHPID.
User response: None.
IHVC533
aa session established with this host
Explanation: A VTAM or TCP/IP session has been
established with this host, and broadcasts to this
system should be successful.
User response: None.
IHVC536I
NO communication initialized on
this host
Explanation: This message is issued for the primary
host when I/O operations is unable to establish any
communication with either VTAM or TCP/IP, or both,
on this host.
User response: None.
aa
IHVC535I
Port aa cannot be CONNECTed while
in maintenance mode
Explanation: Port aa has been placed in maintenance
mode by a service representative. A port cannot be
connected while in maintenance mode.
User response: Verify that either VTAM or TCP/IP, or
both, are operational and that all I/O operations
installation requirements are met.
IHVC537I
aa communication is initialized on
this host
Explanation: This message is issued for the primary
host when I/O operations is operational and
communicating with either VTAM or TCP/IP, or both.
The variable aa shows the type of the
communication, either VTAM or TCP/IP.
User response: None.
IHVC538I
aa bb command not supported by this
host
Explanation: The specified command is not supported
by the target host indicated in the command. The
release level of I/O operations on that host must be
upgraded to support the requested command.
The variable aa shows the name of the I/O
operations command.
The variable bb shows the command operand.
User response: Use non-I/O operations commands to
perform the required task.
The variable aa shows the name of the port.
User response: Wait for the service representative to
complete maintenance.
IHVC534I
Failed VARYs Online : Tried Failed 1st 3
Failures (Dev,Chp)
IHVC539I
Cannot aa bb cc that is type dd
Explanation: The specified command cannot be
processed for the CHPID because I/O operations does
not support that command for the CHPID type
indicated.
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Varys
tried, the number of Varys that failed, and the first
three device number/CHPID pairs that failed.
The variable aa shows the name of the I/O
operations command.
User response: None.
The variable dd shows the CHPID type.
The variable bb shows the CHPID.
The variable cc shows the CHPID number.
User response: Use non-I/O operations commands to
perform the required task.
184
System Automation for z/OS Messages and Codes:
IHVC540I • IHVC611I
IHVC540I
Host name aa is reset off.
Explanation: The specified VTAM application name or
TCP/IP host name is reset off, so the command entered
for that host cannot be processed.
The variable aa shows the VTAM application name
or the TCP/IP host name of the host that is reset
off.
User response: Determine why the host is reset off. If
possible, reset the host on by using the RESET HOST
(ON) command and reissue your original command.
IHVC602I
WRITESWCH command request bits
incorrect.
Explanation: The requested combination of bits
specified for the WRITESWCH command are not valid.
For example, only one of the bits for the Modify, And,
or Or mask can be specified for a port on a switch.
User response: Check the WRITESWCH command
block and determine the correct setting of the request
bits.
IHVC603I
Host path status differs from switch
settings
Explanation: As a result of the SYNC SWITCH
command with the NOPROCESS option, I/O
operations determined that the host’s path status
differed from the connectivity settings at the switch.
User response: Enter the DISPLAY VARY SYNC
command, and if you want the listed Varys performed,
reenter the command with the PROCESS option.
IHVC606I
Config(s) failed
Explanation: I/O operations attempted to perform
Configs that were unsuccessful.
User response: Use operator commands to DISPLAY
CHPID status to determine the reason for the failures
and take appropriate action.
IHVC607I
Failed CONFIGs OFFLINE: Tried Failed
Failures (Chp)
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Configs
tried, the number of Configs that failed, and the first
eight Configs that failed.
User response: None.
IHVC608I
Failed CONFIGs ONLINE:
Failed Failures (Chp)
Tried
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Configs
tried, the number of Configs that failed, and the first
eight Configs that failed.
User response: None.
IHVC609I
Failed CONFIGs Backout: Tried Failed
Failures (Chp)
Explanation: This is a header for the DISPLAY
RESULTS command that shows the number of Configs
tried, the number of Configs that failed, and the first
eight Configs that failed.
User response: None.
IHVC604I
SYNC VARY(s) failed
Explanation: As a result of the SYNC SWITCH
command with the PROCESS option, some of the
required Varys failed.
User response: Enter the DISPLAY VARY command.
Then use the list of failed Vary requests to determine
which paths could not be varied and take appropriate
action.
IHVC605I
I/O-OPS unable to perform Config
Explanation: As a result of a connectivity command,
CHPIDs require either Config Offline or Online, but the
named I/O operations does not have the capability to
perform the Config. This could be caused by an
incorrect level of either I/O operations or the System
Control Program.
User response: Manually enter the necessary
commands to configure the CHPIDs to their desired
status. Then reenter the connectivity command if
appropriate.
IHVC610I
aa
bb
(cc,dd, ee,ff,gg,hh,ii,jj)
Explanation: This message is the output of a DISPLAY
RESULTS command that shows the number of Configs
tried, the number of Configs that failed, and the first
eight Configs that failed.
The variable aa shows the number of attempted
Configs.
The variable bb shows the number of failed Configs.
The variables cc, dd, ee, ff, gg, hh, ii, and jj show the
CHPIDs of the first eight Configs that failed.
User response: None.
IHVC611I
(aa,bb,cc,dd,ee,ff,gg,hh)
Explanation: This message is the output of a DISPLAY
RESULTS command.
The variables cc, dd, ee, ff, gg, and hh show the
CHPIDs.
Chapter 9. Messages IHVA100I to IHVZ760
185
IHVC612I • IHVC621I
User response: None.
IHVC612I
SYNC SWITCH command not fully
supported
Explanation: This host is not equipped with the
correct level of either I/O operations or the System
Control Program to perform the SYNC SWITCH
command. If the PROCESS option is specified with the
command, all required Varys will be attempted. If the
NOPROCESS option is specified with the command,
the list of required Varys is not created.
User response: None.
IHVC613I
Timeout occurred configuring aa
CHPID(s) bb
Explanation: An attempt was made to configure
ESCON converter CHPIDs but the current time-out
value was exceeded.
The variable aa shows the number of CHPIDs
attempted.
The variable bb shows whether the CHPIDs are
online or offline.
User response: Enter the Display Timeout command
to determine the current time-out value. Then enter the
Reset Timeout command to increase the time-out value,
and reenter the command.
IHVC614I
aa CHPID bb status can not be
verified
Explanation: An attempt was made to prevent a port
communicating through an ESCON Converter Model 1,
and there is no device associated with the converter.
I/O operations cannot determine whether the CHPID is
online or offline.
The variable aa shows the CHPID type.
The variable bb shows the CHPID.
User response: Determine the status of the CHPID. If
it is online, configure the CHPID offline. Then reenter
the command with the Force option.
IHVC615I
Host(s) issued WARNING(s) for the aa
command.
Explanation: I/O operations hosts detected one or
more of the following conditions:
User response: Enter the DISPLAY RESULTS and
DISPLAY HOST commands to determine why the hosts
responded with a warning.
IHVC616I
VARY ONLINE(s) failed
Explanation: A host failed Vary Path Online requests.
User response: Enter the DISPLAY VARY command.
Then use the list of failed Vary Online requests to
determine which paths could not be varied online.
IHVC617I
Some switches not affected by the
command.
Explanation: All switches were specified for the
switch device number, but the I/O operations
command did not affect all switches known to this
host.
User response: Enter the DISPLAY RESULTS
command to determine which switches were affected
by the command.
IHVC618I
More than one asterisk specified in port
name.
Explanation: Only one asterisk (*) can be specified in
the port name. This asterisk signifies a generic port
name.
User response: Reenter the command, specifying only
one asterisk in the port name.
IHVC619I
More than 512 ports affected by the
command.
Explanation: The generic port name that was specified
affected more than the allowable maximum of 512
ports.
User response: Reenter the command with a smaller
subset of the generic port name.
IHVC620I
ESCON Converter Model 2
processing not supported
Explanation: This message is the output of a DISPLAY
RESULTS command and indicates that the host does
not support ESCON Converter Model 2 processing.
v Failed Vary Path Online requests
User response: If it is determined that the command
should proceed, reenter the command with the
Nocheck option.
v Failed ESCON Converter Model 1 Config Online
requests
IHVC621I
v ESCON Converter Model 2 may need enablement
v VTAM or TCP/IP communication problems
v Other conditions that could cause a warning
The variable aa shows the name of the command
that caused the warning.
186
System Automation for z/OS Messages and Codes:
ESCON Converter Model 2(s)
detected
Explanation: This message is the output of a DISPLAY
RESULTS command and is followed by message
IHVC623I. As a result of a connectivity command,
ESCON Converter Model 2s were detected on paths
affected by that command.
IHVC622 • IHVC631I
User response: If it is determined that the command
should proceed, reenter the command with the
Nocheck option.
IHVC622
IHVC627
Explanation: This is the data associated with message
IHVC623I and defines the ESCON converter.
The variable bb shows the ESCON converter model.
The variable aa specfies disablement or enablement.
User response: Take the appropriate action to disable
or enable ESCON Converter Model 2 paths.
The variable cc shows the ESCON converter serial
number.
The variable dd shows the port.
The variable ee shows the name of the port.
User response: None.
IHVC628I
Id Type Mod Serial number Port
Logical name / Unique id
Explanation: This is a header for the messages
IHVC626I and IHVC627I.
Chained path associated with: aa
Explanation: The requested combination of bits
specified for the WRITESWCH command was all 0's.
bb
Explanation: This message is the output of a DISPLAY
RESULTS command and is followed by message
IHVC625I. An ESCON Converter Model 2 was detected
in a chained path.
The variable aa shows the port.
The variable bb shows the name of the port.
IHVC630I
aa on bb has the I/O-OPS lock.
Explanation: Another user has locked I/O operations
command processing. If that user is performing
connectivity changes involving any of the components
you are attempting to obtain information about, that
information might not be correct.
The variable aa shows the user ID.
User response: None.
IHVC625
No WRITESWCH command request bits
set.
User response: Check the WRITESWCH command
block and determine the correct setting of the request
bits.
User response: None.
IHVC624
dd ee
The variable aa shows the ESCON converter type.
ESCON Converter Model 2 paths
may require aa:
Explanation: This message is the output of a DISPLAY
RESULTS command and is followed by message
IHVC623I.
IHVC623
CV aa bb cc
The variable bb shows the I/O operations VTAM
name or TCP/IP host name.
Data follows for chained switch:
aa
Explanation: This message gives information for the
switch involved in the chained path referred to in
message IHVC624I.
User response: To obtain current data, reenter the
Display or Query command when the specified user
releases the lock. If you need to obtain the command
lock, enter the GETLOCK command.
The variable aa shows the switch unique identifier.
IHVC631I
User response: None.
IHVC626
CU aa bb cc
dd ee
Explanation: This is the data associated with message
IHVC623I and defines the ESCON Converter Model 2
control unit.
The variable aa shows the control unit type.
The variable bb shows the control unit model.
The variable cc shows the control unit serial
number.
The variable dd shows the port.
The variable ee shows the name of the port.
User response: None.
aa on bb has the I/O-OPS lock, data
overflowed.
Explanation: Another user has locked I/O operations
command processing. If that user is performing
connectivity changes involving any of the components
you are attempting to obtain information about, that
information might not be correct. Also, an overflow
condition occurred that was caused by the Display or
Query command generating more information than can
be returned in a single display.
The variable aa shows the user ID.
The variable bb shows the I/O operations VTAM
name or TCP/IP host name.
User response: Reenter the Display or Query
command with the appropriate range to return the
desired information. To obtain current data, reenter the
Display or Query command when the specified user
releases the lock. If you need to obtain the command
lock, enter the Getlock command.
Chapter 9. Messages IHVA100I to IHVZ760
187
IHVC640I • IHVC651
IHVC640I
Switch aa does not support the
requested function.
Explanation: You attempted a configuration file
function on a switch that does not support the function.
The variable aa shows the switch device number.
User response: Check to ensure that you entered the
correct switch number. If so, the level of microcode on
that switch may need to be upgraded to support the
attempted function.
IHVC646
Explanation: You attempted a WRITEFILE command
that will create more than the maximum number of
allowable files at the switch.
User response: Verify that you want to perform the
requested function. If so, delete an existing file, then
reenter the command.
IHVC647
IHVC641I
Switch does not support the
requested function
Explanation: You attempted a configuration file
function on a switch that does not support the function.
User response: Check to ensure that you entered the
correct switch number. If so, the level of microcode on
that switch may need to be upgraded to support the
attempted function.
IHVC642I
File name aa not valid.
Explanation: You attempted a WRITEFILE command
with a file name that is not supported at the switch.
The variable aa shows the file name.
User response: Reenter the command with a valid file
name.
IHVC643I
File descriptor aa not valid.
Explanation: You attempted a WRITEFILE command
with a file descriptor that is not supported at the
switch.
The variable aa shows the file descriptor.
User response: Reenter the command with a valid file
descriptor.
IHVC644I
Switch file in use, no access.
Explanation: You attempted to perform a
configuration file function, but the file was in use. This
could also occur if you are trying to change the IPL file,
and the current designation is ACTIVE=SAVED.
User response: Verify that the file name entered is
correct. If so, reenter the command. If not, correct the
file name and reenter.
IHVC645
Switch file in use, no access
Explanation: You attempted to perform a
configuration file function, but the file was in use. This
could also occur if you are trying to change the IPL file,
and the current designation is ACTIVE=SAVED.
User response: Verify that the file name entered is
correct. If so, reenter the command. If not, correct the
file name and reenter.
188
System Automation for z/OS Messages and Codes:
Maximum number of files saved at
the switch
File name aa does not exist on switch
Explanation: You attempted to perform a file function
and the file name does not exist on the switch.
The variable aa shows the file name.
User response: View the current list of files at the
switch, then reenter the command with the desired file
name.
IHVC648I
File name aa does not exist on switch bb.
Explanation: You attempted to perform a file function
and the file name does not exist on the switch.
The variable aa shows the file name.
The variable bb shows the switch device number.
User response: Verify that the switch device number
entered is correct, and that the file name entered is on
the current list of files at that switch. Reenter the
command with the correct file name and switch device
number.
IHVC649
Required resources not available to
access file
Explanation: You attempted to perform a
configuration file function and the required resources at
the switch were not available. For example, the buffer
space used by the switch is currently being used by
other host programs.
User response: Retry the command. If possible,
determine why the resources were not available, and
reenter the command once they become available.
IHVC650I
Error in WRITEFILE datablock.
Explanation: You entered a WRITEFILE command
with a data block that contained errors.
User response: Issue the DISPLAY RESULTS
command to determine the errors, then correct the
errors and reenter the command.
IHVC651
Connectivity attributes for port aa
conflict with port bb
Explanation: Conflicting port connectivity attributes
were detected on the indicated WRITEFILE command.
Either the mask or connect status for these ports do not
IHVC653 • IHVC720I
match. For example, if you specified that port C0
should be connected to port C1, but you also specified
that port C1 should be connected to port C2 the
connectivity attributes for ports C0 and C1 would be in
conflict.
The variable aa shows the first port.
The variable bb shows the second port.
User response: Check the Writefile data block for the
two ports, correct the error, and reenter the command.
IHVC653
Incorrect number of implemented
ports for switch
Explanation: You entered a WRITEFILE command
with a data block that did not contain the same number
of implemented ports as the specified switch.
User response: Check the data block and reenter the
command.
IHVC654I
Maximum number of files saved at
switch aa.
Explanation: You attempted to perform a
configuration file function that will create more than
the maximum number of allowable files at the switch.
The variable aa shows the switch device number.
User response: Verify that you want to perform the
requested function. If so, issue a delete request to
access additional space at the switch.
IHVC655I
Required resources not available to
access file.
Explanation: You attempted to perform a
configuration file function and the required resources at
the switch were not available. Possible causes are:
IHVC656I
Cannot delete IPL file at the switch.
Explanation: You attempted to delete the IPL file at
the switch. This is not allowed.
User response: None.
IHVC657
Cannot delete IPL file at the switch
Explanation: You attempted to delete the IPL file at
the switch. This is not allowed.
User response: None.
IHVC658I
Switch initialization not complete
Explanation: A configuration file function was
attempted while the switch was in the process of
initializing.
User response: Wait until the switch completes its
initialization and reenter the command.
IHVC659
Switch initialization not complete
Explanation: A configuration file function was
attempted while the switch was in the process of
initializing.
User response: Wait until the switch completes its
initialization and reenter the command.
IHVC660
File name aa not valid
Explanation: You attempted a WRITEFILE command
with a file name that is not supported at the switch.
The variable aa shows the file name.
User response: Reenter the command with a valid file
name.
v The I/O operations console is not available
File descriptor aa not valid
v File Access Facility is not available
IHVC661
v The specified file is locked, for example, by another
user
Explanation: You attempted a WRITEFILE command
with a file descriptor that is not supported at the
switch.
v The file key buffer is full
v No data buffer is available on File access Facility
The variable aa shows the file descriptor.
v The file was not saved because the maximum
number of saved files is reached
User response: Reenter the command with a valid file
descriptor.
v Saved file directory information is required and
initialization was not complete
IHVC720I
v The buffer space that is used by the switch is
currently being used by other host programs
User response: If possible, determine why the
resources were not available, and reenter the command
once they become available.
MVS internal error
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
189
IHVC725I • IHVC803I
IHVC725I
Path not operational
IHVC763I
Coupling facility not accessible
Explanation: This is the reason why the referenced
VARY command failed.
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
User response: None.
IHVC730I
IHVC764I
Last path to device
Coupling facility path does not exist
Explanation: This is the reason why the referenced
VARY command failed.
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
User response: None.
IHVC735I
IHVC765I
Last path (reserved)
Last path to coupling facility
Explanation: This is the reason why the referenced
VARY command failed.
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
User response: None.
IHVC737I
IHVC766I
Last path (allocated)
Last path to active coupling facility
Explanation: This is the reason why the referenced
VARY command failed.
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
User response: None.
IHVC740I
IHVC800
Reserved path
Explanation: This is the reason why the referenced
VARY command failed.
Explanation: Separator line.
User response: None.
User response: None.
IHVC802I
IHVC745I
Kept off by other source
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
IHVC750I
Path validation failed
Explanation: This is the reason why the referenced
VARY command failed.
VTAM or TCP/IP name aa not known to
this host.
Explanation: The specified VTAM application name or
TCP/IP host name is not known to the host issuing the
command.
The variable aa shows the VTAM application name
or the TCP/IP host name that is unknown.
User response: Check the name for entry errors, then
retry.
User response: None.
IHVC803I
IHVC755I
Explanation: This message is the output of a DISPLAY
HOST command.
Device not connected
This Host: aa/bb Sysplex/System: cc/dd
Explanation: This is the reason why the referenced
VARY command failed.
The variable aa shows the VTAM name.
User response: None.
The variable cc shows the name of the sysplex.
The variable bb shows the TCP/IP host name.
The variable dd shows the name of the system.
IHVC760I
Permanent error
Explanation: This is the reason why the referenced
VARY command failed.
User response: None.
190
System Automation for z/OS Messages and Codes:
User response: None.
IHVC804I • IHVC818
IHVC804I
Name
identifier
Level Physical
Sysplex System
Explanation: This is a header for display commands.
User response: None.
IHVC805I
The variable aa shows the number of Varys
displayed.
User response: None.
IHVC812
The following switches are attached:
Explanation: This is a header for display commands.
Chp
Swch
Status
Explanation: This is a header for the DISPLAY CHP
command.
User response: None.
User response: None.
IHVC813
IHVC806I
Swch
Chp Type
Devn LSN Port
C P Port name
HS
Explanation: This message is the output of display
commands.
Explanation: This is a header for the DISPLAY CHP
command.
User response: None.
User response: None.
IHVC807I
Devn LSN
Unique id
Explanation: This is a header for display commands.
User response: None.
IHVC808I
VTAMname/TCP host
System
Sysplex
bb
ee
ff gg
Explanation: This message is the output of a DISPLAY
CHP command.
The variable bb shows CHPID type.
The variable cc shows switch device number.
The variable dd shows the logical switch number.
The variable ee shows the port.
(cc,dd)(ee,ff)( gg,hh)
The variable bb shows the number of failed Varys.
The variables cc, ee, and gg show the device number.
The variables dd, ff, and hh show the CHPID.
User response: None.
CHPID aa not known to this host
Explanation: The specified CHPID is not known to the
host processing the command.
The variable aa shows the CHPID.
User response: Enter the DISPLAY CHP * command to
identify all known CHPIDs.
Vary type
Tried
(Dev,Chp,Msg)
dd
User response: None.
The variable aa shows the number of attempted
Varys.
IHVC811
cc
The variable gg shows the port name.
Explanation: This message is the output of a DISPLAY
HOST command.
IHVC810I
bb
The variable ff shows the port status.
User response: None.
OFFLINE
VARYs:
aa
aa
The variable aa shows the CHPID.
Explanation: This is a header for the DISPLAY
RESULTS commands.
IHVC809I
IHVC814
Failed 1st aa failures
Explanation: This is a header for the DISPLAY VARY
command.
IHVC815
Port
Explanation: This message is the output of a DISPLAY
CHP command.
User response: None.
IHVC816
Chp
Swch
Status
Explanation: This is a header for the DISPLAY CHP
command.
User response: None.
IHVC817
Chp
Type
Devn LSN Port H S
C P Port name
Explanation: This is a header for the DISPLAY CHP
command.
User response: None.
IHVC818
aa
bb
cc dd
ee
ff
gg
Explanation: This message is the output of a DISPLAY
CHP command.
The variable aa shows the CHPID.
Chapter 9. Messages IHVA100I to IHVZ760
191
IHVC819 • IHVC828
The variable bb shows the CHPID type.
IHVC823I
The variable cc shows the switch device number.
The variable dd shows the logical switch number.
The variable ee shows the port.
The variable bb shows the switch device number.
The variable gg shows the port name.
User response: Enter DISPLAY DEV de * to find out
which switch the device is on. Then reenter the
command with the correct switch device number.
User response: None.
OFFLINE
aa
bb
Explanation: The specified device was not found on
the specified switch.
The variable aa shows the device number.
The variable ff shows the port status.
IHVC819
Device aa not found on switch bb.
(cc,dd,"ee")
Explanation: This message is the output of a DISPLAY
VARY command.
The variable aa shows the number of attempted
Varys.
The variable bb shows the number of failed Varys.
The variable cc shows the device number.
IHVC824
Port
Explanation: This message is the output of a DISPLAY
DEV command.
User response: None.
IHVC825
Chp
Swch
Status
The variable dd shows the CHPID.
The variable ee shows the reason why this vary
failed.
User response: None.
IHVC820I
User response: None.
Device aa not known to this host.
Explanation: The specified device is not known to the
host sending the command.
The variable aa shows the device number.
User response: Verify that the correct device number
was entered. If so, enter DISPLAY DEV * sw for each
switch to find the correct device number. Then reenter
the command.
IHVC821I
Explanation: This is a header for the DISPLAY DEV
command.
Switch device aa not known to this host.
Explanation: The specified switch was not known to
the host sending the command.
The variable aa shows the switch device number.
User response: Enter DISPLAY SWITCH * to display all
switch device numbers known to the host. Then reenter
the command with the correct switch device number.
IHVC826
Devn Chp Type Devn LSN Port H S
C P Port name
Explanation: This is a header for the DISPLAY DEV
command.
User response: None.
IHVC827
aa bb
cc dd ee
ff
gg hh
Explanation: This message is the output of a DISPLAY
DEV command.
The variable aa shows the device number.
The variable bb shows the CHPID.
The variable cc shows the CHPID type.
The variable dd shows the switch device number.
The variable ee shows the logical switch number.
The variable ff shows the port.
The variable gg shows the port status.
IHVC822
(aa,bb,"cc")
Explanation: This message is the output of a DISPLAY
VARY command.
The variable aa shows the device number.
The variable bb shows the CHPID.
The variable cc shows the reason why this vary
failed.
User response: None.
The variable hh shows the port name.
User response: None.
IHVC828
Connected to:
The variable aa shows the port.
The variable bb shows the port status.
User response: None.
System Automation for z/OS Messages and Codes:
bb cc
Explanation: This message is the output of a DISPLAY
DEV command.
The variable cc shows the port name.
192
aa
IHVC829 • IHVC841I
IHVC829
Chained to:
aa bb
cc dd ee
Explanation: This message is the output of a DISPLAY
DEV command.
The variable aa shows the switch device number.
IHVC836
Status
Explanation: This is a header for the DISPLAY
SWITCH command.
User response: None.
The variable bb shows the logical switch number.
The variable cc shows the port.
IHVC837
The variable dd shows the port status.
Port H S C
P I/O-Def Port
name
The variable ee shows the port name.
Explanation: This is a header for the DISPLAY
SWITCH command.
User response: None.
User response: None.
IHVC830
aa connected to:
bb
cc dd
Explanation: This message is the output of a DISPLAY
DEV command.
The variable aa shows the midport of chain.
IHVC838
aa bb
cc dd ee ff
Explanation: This message is the output of a DISPLAY
SWITCH command.
The variable bb shows the port.
The variable aa shows the switch device number.
The variable cc shows the port status.
The variable bb shows the logical switch number.
The variable dd shows the port name.
The variable cc shows the switch unique identifier.
The variable dd shows the number of ports installed.
User response: None.
The variable ee shows the switch status information.
IHVC831
aa chained to: bb cc
dd ee ff
Explanation: This message is the output of a DISPLAY
DEV command.
The variable ff shows the switch status code.
User response: Enter the DISPLAY RESULTS
command to get more information about the switch.
The variable aa shows the midport of chain.
aa bb
dd
cc
The variable bb shows the switch device number.
IHVC839
The variable cc shows the logical switch number.
Explanation: This message is the output of a DISPLAY
SWITCH command.
The variable dd shows the port.
The variable ee shows the port status.
The variable aa shows the port.
The variable ff shows the port name.
The variable bb shows the port status.
The variable cc shows the port name.
User response: None.
IHVC834
The variable dd shows the port I/O definition.
Swch LSN Unique id
Ins Status
SC
Explanation: This is the header for the DISPLAY
SWITCH command. SWITCH * DETAIL command.
Swch
Switch device number
LSN Logical switch number
Unique id
Node element descriptor
Ins
Number of installed ports
Status
Status information
SC
Status code
User response: None.
IHVC840I
aa unknown to this host.
Explanation: The specified port name is not known to
this host.
The variable aa shows the port name.
User response: None.
IHVC841I
No BLOCKed port names on switch aa.
Explanation: There are no blocked port names on the
specified switch.
The variable aa shows the switch device number.
User response: None.
User response: None.
IHVC835
Port
Explanation: This message is the output of a DISPLAY
SWITCH command.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
193
IHVC842I • IHVC854
IHVC842I
No CONNECTed port names on switch
aa.
Explanation: There are no connected port names on
the specified switch.
The variable aa shows the switch device number.
User response: None.
Explanation: The specified port name does not exist
on the specified switch.
The variable aa shows the port name.
The variable bb shows the switch device number.
User response: Use the DISPLAY NAME command to
see whether the port name exists on any other switch.
IHVC844
User response: None.
IHVC849
Allow/Prohibit mask for this port:
User response: None.
IHVC850I
Port aa does not exist on switch bb.
Explanation: The specified port does not exist on the
specified switch.
The variable aa shows the port.
The variable bb shows the switch device number.
User response: Enter DISPLAY PORT (*) sw_dev_number
to display all ports on the switch.
Port
Explanation: This is a header for the DISPLAY NAME
or DISPLAY PORT command.
User response: None.
IHVC845
The variable dd shows the port I/O definition.
Explanation: This is a header for the DISPLAY NAME
or DISPLAY PORT command.
aa does not exist on switch bb
IHVC843
The variable cc shows the port status.
IHVC851
No BLOCKed ports on switch aa.
Explanation: There are no blocked ports on the
specified switch.
Swch
Status
I/O
The variable aa shows the switch device number.
Explanation: This is a header for the DISPLAY NAME
or DISPLAY PORT command.
User response: None.
User response: None.
IHVC852
IHVC846
Explanation: There are no connected ports on the
specified switch.
Port Name
LSN
Port H S C
Devn
P Def
No CONNECTed ports on switch aa.
The variable aa shows the switch device number.
Explanation: This is a header for the DISPLAY NAME
or DISPLAY PORT command.
User response: None.
User response: None.
IHVC853
IHVC847
aa
bb
cc
dd ee ff
Explanation: This message is the output of a DISPLAY
NAME or DISPLAY PORT command.
The variable aa shows the port name.
The variable bb shows the switch device number.
Config type
Number
CONFIGs (Chp)
1st aa
Explanation: This is a header for the DISPLAY VARY
command.
The variable aa shows the number of Configs
displayed.
User response: None.
The variable cc shows the logical switch number.
The variable dd shows the port.
The variable ee shows the port status.
The variable ff shows the port I/O definition.
User response: None.
IHVC848
Connected to:
OFFLINE
aa
(bb,cc,dd,ee,ff,gg,hh,ii)
Explanation: This message is the output of the
DISPLAY VARY command.
The variable aa shows the number of Config
Offlines.
aa bb cc dd
Explanation: This message is the output of a DISPLAY
NAME or DISPLAY PORT command.
The variable aa shows the port name.
The variable bb shows the port.
194
IHVC854
System Automation for z/OS Messages and Codes:
The variables bb, cc, dd, ee, ff, gg, hh, and ii show the
CHPIDs.
User response: None.
IHVC855 • IHVC877
IHVC855
ONLINE
aa
(bb,cc,dd,ee,ff,gg,hh,ii)
Explanation: This message is the output of the
DISPLAY VARY command.
The variable aa shows the number of Config
Onlines.
The variables bb, cc, dd, ee, ff, gg, hh, and ii show the
CHPIDs.
IHVC872
SYNC type
Number
VARYs (Dev,Chp)
1st aa
Explanation: This is a header for the DISPLAY VARY
command.
The variable aa shows the number of Sync Varys
displayed.
User response: None.
User response: None.
IHVC873
IHVC856I
Explanation: This message is the output of a DISPLAY
VARY command.
CVC CHPIDs may require
ENABLEMENT: aa,bb,cc,dd,ee,ff,gg,hh
Explanation: This message is the first line of the
output of a DISPLAY RESULTS command that shows
the CHPID numbers of CVC CHPIDs that might need
to be configured online.
The variables aa, bb, cc, dd, ee, ff, gg, and hh show
the CHPID numbers.
User response: Determine whether the CHPID must
be configured online to make it operational, and take
the appropriate action.
aa,bb,cc,dd,ee,ff,gg, hh
IHVC857I
Explanation: This message is the second line of the
output of a DISPLAY RESULTS command that shows
the CHPID numbers of CVC CHPIDs that might need
to be configured online.
The variables aa, bb, cc, dd, ee, ff, gg, and hh show
the CHPID numbers.
User response: Determine whether the CHPID must
be configured online to make it operational, and take
the appropriate action.
IHVC860I
Current timeout value is aa seconds.
Explanation: This message is the result of a DISPLAY
TIMEOUT command.
OFFLINE
aa
(bb,cc)(dd,ee)(ff,gg)(hh,ii)
The variable aa shows the number of Sync Offline
Varys to be done.
The variables bb, dd, ff, and hh show the device
number.
The variables cc, ee, gg, and ii show the CHPID.
User response: None.
IHVC874
ONLINE
dd,ee)(ff,gg)(hh,ii)
aa
(bb,cc)(
Explanation: This message is the output of a DISPLAY
VARY command.
The variable aa shows the number of Sync Online
Varys to be done.
The variables bb, dd, ff, and hh show the device
number.
The variables cc, ee, gg, and ii show the CHPID.
User response: None.
IHVC875
No SYNC VARYs detected on previous
command
Explanation: This message is the output of a DISPLAY
command.
User response: None.
The variable aa shows the timeout value in seconds.
User response: None.
IHVC876I
IHVC870I
Explanation: This message is the output of a DISPLAY
command.
Number of VARYs specified must be
between 1 and 1500.
Explanation: I/O operations can only display the first
1500 Varys. This message is the output of a DISPLAY
command.
User response: None.
IHVC871
No VARYs failed on previous command
Explanation: This message is the output of a DISPLAY
command.
No VARYs or CONFIGs detected on
previous command.
User response: None.
IHVC877
No SYNC CONFIGs detected on
previous command
Explanation: This message is the output of a DISPLAY
command.
User response: None.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
195
IHVC878I • IHVC891I
IHVC878I
No SYNC VARYs or CONFIGs detected
on previous command
Explanation: This message is the output of a DISPLAY
command.
User response: None.
IHVC879
No failed CONFIGs on previous
command
Explanation: This message is the output of a DISPLAY
command.
the appropriate range to return the desired information.
IHVC884I
Explanation: This message is the result of a DISPLAY
HOST * command. Following this message is a list of
systems that are not associated with a VTAM name or
TCP/IP host name.
User response: None.
IHVC885I
User response: None.
IHVC880I
ONLINE VARYs:
(cc,dd)( ee,ff)(gg,hh)
aa
bb
Explanation: This message is the output of a DISPLAY
command. For an example of how the command
output appears when it is formatted, refer to the
appropriate command section.
The variable aa shows the number of Varys.
The variable bb shows the number of failed Varys.
The variables cc, ee and gg show the device number.
The variables dd, ff and hh show the CHPID.
User response: None.
IHVC881I
Display command caused data overflow.
Explanation: The command completed, but an
overflow condition occurred that resulted in a non-zero
return code. This overflow condition was caused by the
DISPLAY command generating more information than
can be returned in a single display.
User response: Reenter several DISPLAY commands
with smaller ranges.
IHVC882I
Starting number must be less than or
equal to ending number.
Explanation: The DISPLAY command failed because
the user entered a value for the starting number that
was greater than the ending number. The starting
number must contain a value that is less than or equal
to the value of the ending number.
Sysplex system(s) not associated with a
host name detected:
Sysplex <- Systems
------------------------------------->
Explanation: This is a header for the DISPLAY HOST
* command. Following this message is a list of systems
that are not associated with a VTAM name or TCP/IP
host name.
User response: None.
IHVC886I
aa
bb, cc, dd, ee, ff,
Explanation: This message is the output of DISPLAY
HOST * command. It displays a list of systems that are
not associated with a VTAM name or a TCP/IP host
name.
The variable aa shows the name of the sysplex.
The variables bb, cc, dd, ee, and ff show system
names.
User response: None.
bb, cc, dd, ee, ff,
IHVC887I
Explanation: This message is the output of DISPLAY
HOST * command, and is a continuation of message
IHVC886I. It displays a list of systems that are not
associated with a VTAM name or a TCP/IP host name.
The variables aa, bb, cc, dd, ee, and ff show system
names.
User response: None.
IHVC890I
Device is not known to I/O-OPS.
Explanation: The VARY command failed because the
device was not found in the I/O operations database.
User response: Reenter the DISPLAY command with
the appropriate range to return the desired information.
User response: Verify the device number and reissue
the command with the correct number.
IHVC883I
IHVC891I
No devices found in the specified range
on switch aa.
Explanation: The DISPLAY command failed because
no devices were found in the specified range on the
specified switch.
The variable aa shows the switch device number.
User response: Reissue the DISPLAY command with
196
System Automation for z/OS Messages and Codes:
Device is a coupling facility.
Explanation: The Vary command failed because the
device attempted to be varied is a coupling facility.
User response: Verify the device number and reissue
the command with the correct number.
IHVC892I • IHVC913I
IHVC892I
No device for aa.
Explanation: The VARY command failed because no
devices were found for the input token.
The variable aa shows the token.
User response: Verify the token number and reissue
the command with the correct number.
IHVC893I
No device for aa.
Explanation: The VARY command failed because no
devices were found for the input token.
The variable aa shows the token.
User response: Verify the token number and reissue
the command with the correct number.
IHVC902I
Switch aa not opened.
Explanation: The specified switch has not been
opened prior to receiving a command.
The variable aa shows the switch device number.
User response: Enter the Reset Switch command to
try to open the switch. The switch may not be varied
online. Vary it online and reissue the command.
IHVC908
Ports aa and bb are not CONNECTed
to each other
Explanation: The user tried to disconnect two ports
that are not connected to each other. However, one of
the ports is involved in a dedicated connection with a
different port.
The variable aa shows the first port.
The variable bb shows the second port.
User response: Reenter the command with the correct
ports.
IHVC909
Execution of the CHAIN command
will form a closed loop
Explanation: The user entered a CHAIN command
that will cause the chained path to be a closed loop.
User response: Reenter the command with the correct
operands.
IHVC910
Port aa is not part of a CHAINed
path
Explanation: The port that was specified in the
UNCHAIN command is not part of a chained path.
The variable aa shows the port.
IHVC903
Port aa already CHAINed
Explanation: On a CHAIN command, one of the
specified ports was already part of a chained
connection.
User response: Reenter the UNCHAIN command with
the correct command parameters.
IHVC911
The variable aa shows the port.
User response: Enter Display Switch
sw_device_number to get the status of each port on the
switch.
IHVC905I
Not allowed to purge resident host.
Explanation: The RESET HOST command with the
PURGE option was specified for the resident host. This
is not allowed.
Explanation: The specified ports in the UNCHAIN
command are not part of the same chained path.
The variable aa shows the first port.
The variable bb shows the second port.
User response: Reenter the UNCHAIN command with
the correct command parameters.
IHVC912
User response: Reevaluate which host is to be purged.
IHVC906
Cannot aa CHAINed port bb
Explanation: The DISCONNECT command cannot be
used to remove the dedicated connection in a chained
path. The CONNECT command cannot be used to
establish a dedicated connection to a port defined to be
part of a chain.
The variable aa shows the name of the command.
The variable bb shows the port name.
User response: Enter the UNCHAIN command to
remove the dedicated connection. Enter the CHAIN
command to establish the dedicated connection.
Ports aa and bb are not part of the
same CHAINed path
Ports not in the correct CHAINed
path order
Explanation: The ports specified in the UNCHAIN
command were defined in a different order when
specified in the CHAIN command.
User response: Reenter the UNCHAIN command with
the correct command parameters.
IHVC913I
Command affects Inter-Switch-Link port
aa on bb.
Explanation: The port specified is implemented as a
FICON port for an Inter-Switch-Link (E_Port). A
BLOCK command is not allowed for this type of port.
This is also true for UNBLOCK, ALLOW, PROHIBIT, or
WRITEPORT unless the user specifies the option
IGNORE along with the command. The reason for
Chapter 9. Messages IHVA100I to IHVZ760
197
IHVC914 • IHVD005I
requesting the additional option is that I/O operations
can no longer guarantee "safe-switching" when an
E_Port is involved in the command being performed.
"Safe-switching" sets the paths and devices online or
offline when the path from a chpid to a device either
becomes valid or is no longer valid because of a port
manipulation. The option makes the operator aware of
this fact.
The variable aa shows the port address of the first
or only port.
The variable bb shows the switch device number of
the port.
User response: For UNBLOCK, ALLOW, PROHIBIT,
or WRITEPORT reenter the command using the option
IGNORE.
The variable aa shows the version level of I/O
operations.
The variable bb shows the release level of I/O
operations.
The variable cc shows the modification level of I/O
operations.
User response: None.
IHVD001I
Explanation: This message follows IHVD000I when
I/O operations has successfully started and is ready to
accept commands.
User response: None.
IHVD002I
IHVC914
Command affects Inter-Switch-Link
port aa
Explanation: This message occurs as the third line of
information for a particular switch device in the output
of a DISPLAY RESULTS command where a previous
command has been rejected. The port specified is
implemented as a FICON port for an Inter-Switch-Link
(E_Port). A BLOCK command is not allowed for this
type of port. This is also true for UNBLOCK, ALLOW,
PROHIBIT, or WRITEPORT unless the user specifies
the option IGNORE along with the command.
The reason for requesting the additional option is that
I/O operations can no longer guarantee
"safe-switching" when an E_Port is involved in the
command being performed.
The variable aa shows the port address of the first
or only port.
User response: For UNBLOCK, ALLOW, PROHIBIT,
or WRITEPORT reenter the command using the option
IGNORE.
IHVC998I
I/O-OPS command response
Explanation: This is the control line header for a
multiple line display.
User response: None.
IHVC999I
I/O-OPS display
Explanation: This is the control line header for a
multiple line display.
User response: None.
IHVD000I
I/O-OPS Vaa.Rbb.Mcc START in
progress.
Explanation: The system operator has entered a
START command. I/O operations sends this message to
show that it has been loaded by the system but is not
ready to accept commands.
198
System Automation for z/OS Messages and Codes:
I/O-OPS START is complete.
I/O-OPS STOP in progress.
Explanation: The system operator has entered a
command to stop I/O operations or a severe error has
caused I/O operations to stop.
User response: None.
IHVD003I
I/O-OPS STOP is complete.
Explanation: This message follows IHVD002I when
I/O operations has successfully stopped on this host.
User response: None.
IHVD004I
aa failed for bb, RC=cc.
Explanation: A system service or instruction failed.
This service or instruction is required for I/O
operations to perform its functions. This may also
indicate a previous error.
The variable aa shows the ATTACH, LOAD, or
STARTUP.
The variable bb shows the module or function
The variable rc shows the return code.
User response: Before continuing you should look for
any previous I/O operations error messages. For an
explanation of the return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. Use the return code to determine the cause of
the error. Correct the condition and restart I/O
operations.
IHVD005I
aa failed for bb cc, RSN=dd.
Explanation: A system service or instruction failed.
This service or instruction is required for I/O
operations to perform its functions.
The variable aa shows the system service or
instruction, for example, UCBSCAN, that failed.
The variable bb shows the module, function, or
system service target identifier.
IHVD006I • IHVD104I
The variable cc shows the module, function, or
system service target name.
User response: Determine the cause of the problem
and take appropriate corrective action.
The variable dd shows the reason code.
User response: For an explanation of the reason code,
refer to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405. Report the problem to
your IBM Support Center. Stop and restart I/O
operations.
IHVD006I
Data Handling system error, RSN=aa.
Explanation: A unrecoverable system error was
detected during I/O operations database processing.
IHVD013E
Explanation: The information returned by the channel
subsystem was not valid because there are no valid
CHPIDs, devices, or paths defined.
System programmer response: Report the problem to
your IBM Support Center.
IHVD014E
The variable aa shows the reason code.
User response: For an explanation of the reason code,
refer to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405. Report the problem to
your IBM Support Center. Stop and restart I/O
operations.
IHVD010I
Switch aa associated with device
number bb.
Explanation: I/O operations procedures to associate
the specified switch with a device number were
successfully completed.
The variable aa shows the logical switch number.
The variable bb shows the switch device number.
User response: None.
IHVD011I
Unable to obtain channel subsystem
configuration data.
Explanation: I/O operations was unable to obtain
channel subsystem configuration data due to hardware
or software incompatibility.
System programmer response: Report the problem to
your IBM Support Center.
IHVD102I
System page error accessing switch bb
(LSN aa).
Explanation: When attempting to access the specified
switch, the operating system detected a system paging
problem.
The variable aa shows the logical switch number.
The variable bb shows the switch device number.
User response: Report the problem to your IBM
Support Center.
Configuration has no switch.
Explanation: I/O operations detected that there are no
logical switch numbers associated with the CHPIDs in
the I/O configuration definition. I/O operations is
unable to recognize any switches in the configuration.
System programmer response: Correct any errors
found in the I/O configuration definition. Then restart
I/O operations.
IHVD012I
Channel subsystem configuration data
not valid.
Switch aa cannot be associated with a
device.
Explanation: I/O operations procedures to associate
the specified switch as a device were unsuccessful.
Some of the conditions that may cause this are:
v I/O configuration definitions for the control unit or
I/O device for the switch were missing or incorrectly
defined.
v The switch is not operational or does not exist.
v All defined paths from the CHPID to the switch
control unit were not operational or were blocked.
IHVD103I
System I/O error accessing switch bb
(LSN aa).
Explanation: When attempting to access the specified
switch, the operating system detected a system I/O
error.
The variable aa shows the logical switch number.
The variable bb shows the switch device number.
User response: Report the problem to your IBM
Support Center.
IHVD104I
Switch bb (LSN aa) issued a unit check.
Explanation: The specified switch sent a unit check.
This condition is caused by an I/O operations
programming problem.
The variable aa shows the logical switch number.
The variable bb shows the switch device number.
User response: Report the problem to your IBM
Support Center.
The variable aa shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
Chapter 9. Messages IHVA100I to IHVZ760
199
IHVD105I • IHVD306I
IHVD105I
Cannot ALLOCATE/ATTACH switch bb
(LSN aa).
Explanation: When attempting to allocate (MVS) or
attach (VM) the specified switch, the operating system
detected an error.
The variable aa shows the logical switch number.
types of remote management but require a customer
setup choice to designate exactly one management
agent to be able to change the switch configuration.
This can prevent uncoordinated changes. I/O
operations can provide its system integrated switching
protection only when switch settings allow it to control
the switches.
The variable bb shows the switch device number.
User response: This message is informational; I/O
operations will proceed. Check whether the DDNAME
associated with the switch device number is allocated
to another job or user. If so, report the problem to your
IBM Support Center.
IHVD106I
Name aa invalid for port bb on switch cc.
Explanation: The name that has been assigned to the
specified port on the specified switch is not a valid port
name.
The variable aa shows the port name.
The variable bb shows the port number.
The variable cc shows the switch device number.
User response: Change the port name. If port FE is
specified for ESCON Director Models 1 and 2, this is
the control unit port (CUP).
IHVD107I
Cannot set user alert mode at switch aa
(LSN bb).
Explanation: During open processing I/O operations
determined that it has a connection to this switch.
Therefore it issued an ENABLE USER ALERT MODE
command. However, the switch did not execute the
command successfully.
The variable aa shows the switch device number.
The variable bb shows the logical switch number.
User response: None. However, you should keep in
mind that users working directly at the director’s
switch do not get a warning that a host program is in
control of this switch.
IHVD108I
Settings on switch aa (LSN bb) prevent
configuration changes.
Explanation: Someone has selected a management
setting at the switch’s local console that prevents
control of the switch via the interfaces that I/O
operations uses. I/O operations can continue to provide
configuration information about this switch. However,
I/O operations cannot change any configuration setting
such a port connectivity hierarchy attributes or port
names.
The variable aa shows the switch device number.
The variable bb shows the logical switch number.
User response: Check whether the switch setup was
done correctly. Some switch models support multiple
200
System Automation for z/OS Messages and Codes:
IHVD201I
System swapping problem: No I/O to
switch(es) performed.
Explanation: When attempting to access the specified
switches, the operating system detected an address
space swapping request failure. This caused all I/O to
switches to be canceled.
User response: Report the problem to your IBM
Support Center.
IHVD202I
Cannot use CHAINed switch aa.
Explanation: A switch contains a defined chained
relationship to the specified switch that is either not
known to the host or is not opened.
The variable aa shows the switch unique identifier.
User response: If the specified switch is not known to
the host, no action is necessary. If the switch is known
but is not opened, the cause of the unsuccessful open
should be identified and corrected. A Reset Switch
command should then be entered for the affected
switch.
IHVD205I
CHPID aa not valid but has device paths
assigned.
Explanation: During I/O operations startup or after a
configuration change, I/O operations obtained channel
subsystem data indicating that the specified CHPID
number is not valid. This CHPID has paths to one or
more devices.
The variable aa shows the CHPID number.
System programmer response: If the CHPID was
incorrectly defined, correct any errors found in the I/O
configuration definition.
User response: If the CHPID is operational and
defined in the I/O configuration definition, report the
problem to your IBM Support Center.
IHVD306I
Port aa on LSN bb incorrectly defined as
supporting a CHAIN.
Explanation: During the refresh of the database, I/O
operations determined that a chain was defined but the
dedicated connection to support that chain did not
exist. The user must reenter the CHAIN command to
define the chained path and establish the dedicated
connection, or enter the UNCHAIN command to
remove the defined chain.
The variable aa shows the port.
IHVD307I • IHVD330I
The variable bb shows the logical switch number.
User response: Enter the CHAIN or UNCHAIN
command.
IHVD307I
Chain aa bb cc dd ee broken.
Explanation: I/O operations has determined that the
specified chain is broken. The required dedicated
connection might be missing or incorrect.
The variable aa shows the first port.
The variable bb shows the first switch device
number.
The variable cc shows the second port.
IHVD310I
Explanation: I/O operations procedures have
identified the port associated with the CHPID.
The variable aa shows the CHPID type.
The variable bb shows the CHPID.
The variable cc shows the port for CHPID.
The variable dd shows the logical switch number.
User response: None.
IHVD320I
The variable dd shows the third port.
The variable ee shows the second switch device
number.
User response: Enter the appropriate CHAIN or
UNCHAIN command.
IHVD308I
Multiple switches assigned unique id
aa.
Explanation: During verification of the switch, I/O
operations determined that more than one switch is
associated with the same unique identifier. This
situation could occur when a dedicated connection is
incorrectly specified on chained paths when I/O
operations opens a switch or when errors exist in the
I/O configuration definition. This condition should be
corrected immediately. Otherwise display and
connectivity commands could affect the wrong switch.
The variable aa shows the switch unique identifier.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Enter Display Switch * to determine
which switches are assigned to the specified unique
identifier. If errors in the I/O configuration definition
are determined to be the problem, record the condition
and report it to your system programmer.
IHVD309I
Chain redefined to aa bb cc dd ee.
Explanation: I/O operations has redefined a chain to
correspond to the physical connections at the switch.
aa CHPID bb determined to be on port
cc LSN dd.
aa CHPID bb reassigned to port cc on
LSN dd.
Explanation: During verification of CHPID ports, I/O
operations determined that a CHPID port was
incorrectly specified and corrected it in the I/O
operations database. This occurs if the I/O
configuration definition for the CHPID was incorrect,
or if a chained path was not specified at I/O operations
startup.
The variable aa shows the CHPID type.
The variable bb shows the CHPID.
The variable cc shows the port for CHPID.
The variable dd shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: If a chained path was not specified,
enter the CHAIN command for the appropriate ports.
IHVD330I
Device paths to aa CHPID bb reassigned
to LSN cc.
Explanation: During verification of device paths to
CHPIDs, I/O operations determined that a device path
was incorrectly specified and corrected it in the I/O
operations database. This occurs if the I/O
configuration definition for the CHPID was incorrect or
if a chained path was not declared at I/O operations
startup. Because devices with paths to a CHPID must
share the same logical switch association, these paths
have been reassigned to the specified switch. This
message is sent following message IHVD320I.
The variable aa shows the CHPID type.
The variable aa shows the first port.
The variable bb shows the CHPID number.
The variable bb shows the first switch device
number.
The variable cc shows the logical switch number.
The variable cc shows the second port.
The variable dd shows the third port.
The variable ee shows the second switch device
number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: If a chained path was not specified,
enter the CHAIN command for the appropriate ports.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
201
IHVD331I • IHVD341I
IHVD331I
aa bb added to I/O-OPS database.
Explanation: As a result of the refresh of the channel
subsystem configuration data, the specified channel
path or switch has been added to the I/O operations
database.
IHVD336I
Switch aa Port bb deleted from I/O-OPS
database.
Explanation: I/O operations has deleted a port from
its internal database. This appears only on the message
log.
The variable aa shows the CHPID or LSN.
The variable aa shows the switch device number.
The variable bb shows the channel port ID or logical
switch number.
The variable bb shows the port number.
User response: None.
User response: None.
IHVD337I
IHVD332I
aa bb deleted from I/O-OPS database.
Explanation: As a result of the refresh of the channel
subsystem configuration data, the specified channel
path or switch has been deleted from the I/O
operations database.
The variable aa shows the CHPID or LSN.
The variable bb shows the channel port ID or logical
switch number.
User response: None.
IHVD333I
aa bb added to I/O-OPS database.
Explanation: I/O operations added a resource to its
internal database. This appears only on the message
log.
The variable aa shows the CNTL or DEVN.
The variable bb shows the control unit number or
device number.
User response: None.
IHVD334I
aa bb deleted from I/O-OPS database.
Explanation: I/O operations deleted a resource from
its internal database. appears only on the message log.
The variable aa shows the CNTL or DEVN.
The variable bb shows the control unit number or
device number.
User response: None.
IHVD335I
Switch aa Port bb added to I/O-OPS
database.
Explanation: I/O operations has added a port to its
internal database. This appears only on the message
log.
The variable aa shows the switch device number.
The variable bb shows the port number.
User response: None.
202
System Automation for z/OS Messages and Codes:
Switch aa added to I/O-OPS database.
Explanation: I/O operations has added a switch to its
internal database. This appears only on the message
log.
The variable aa shows the switch device number.
User response: None.
IHVD338I
Switch aa deleted from I/O-OPS
database.
Explanation: I/O operations has deleted a switch from
its internal database. This appears only on the message
log.
The variable aa shows the switch device number.
User response: None.
IHVD339I
DEVN aa deleted from and added to the
I/O-OPS database
Explanation: I/O operations deleted a resource from
its internal database and then added it to its internal
database. This appears only on the message log.
The variable aa shows the device number.
User response: None.
IHVD340I
CHPID aa and its devices are no longer
associated with LSN bb.
Explanation: During verification of channel subsystem
data, it was determined that the CHPID and its paths
are no longer associated with a switch.
The variable aa shows the CHPID number.
The variable bb shows the logical switch number.
User response: None.
IHVD341I
Device aa state changed to online.
Explanation: Message issued to SYSLOG only for
RMC automation. Operator varied a device online and
the state change must be monitored by RMC. The
IEE450I or IEE457I message issued by MVS is
displayed when an operator issues a DISPLAY
command (d u,,,A80) and when an operator varys a
range of devices online or offline. In the case of the
VARY with a range, MVS issues the DISPLAY
IHVD342I • IHVD360I
command (d u,,,xxx) that shows up in the SYSLOG.
The variable aa shows the device number.
User response: None.
assigned. This occurs if there are I/O configuration
definition errors for the control unit or CNC-type
CHPID, and an expected dedicated connection is not
found.
The variable aa shows the CHPID type.
IHVD342I
Device aa state changed to offline.
Explanation: Message issued to SYSLOG only for
RMC automation. Operator varied a device offline and
the state change must be monitored by RMC. The
IEE450I or IEE457I message issued by MVS is
displayed when an operator issues a DISPLAY
command (d u,,,A80) and when an operator varys a
range of devices online or offline. In the case of the
VARY with a range, MVS issues the DISPLAY
command (d u,,,xxx) that shows up in the SYSLOG.
The variable aa shows the device number.
User response: None.
IHVD344I
Control unit aa status update.
Explanation: I/O operations has detected a status
change for the indicated control unit. This appears only
on the message log.
The variable aa shows the control unit number.
User response: None.
IHVD347I
Device paths to aa CHPID bb not
assigned to a port.
The variable bb shows the CHPID number.
The variable cc shows the port.
The variable dd shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
IHVD349I
Device paths to aa CHPID bb assigned to
port cc LSN dd.
Explanation: I/O operations procedures have
identified the port for the devices associated with the
specified CHPID.
The variable aa shows the CHPID type.
The variable bb shows the CHPID number.
The variable cc shows the port.
The variable dd shows the logical switch number.
User response: None.
IHVD350I
Port aa LSN bb has more than CHPID cc
assigned.
Explanation: During verification of device paths, I/O
operations determined that the port associated with
devices that have paths to the specified CHPID could
not be assigned. This occurs if:
Explanation: During verification of switch ports, I/O
operations determined that there was more than one
CHPID logically associated with the specified port. This
condition is physically impossible and may occur if:
1. There are I/O configuration definition errors for a
CTC_P-type CHPID, and an expected dedicated
connection is not found
v The wrong switch is specified in the I/O
configuration definition for the CHPID.
2. The CHPID is described as CTC_?, indicating that
the control unit port for the paths associated with
the CHPID can not be determined
3. Other I/O configuration definition errors have been
detected for the specified CHPID
v The CHPID is a member of a channel-to-channel
relationship, where the complete path is defined in
the I/O configuration definition. In this case, the
message is informational and might not represent an
error condition.
The variable aa shows the port.
The variable aa shows the CHPID type.
The variable bb shows the logical switch number.
The variable bb shows the CHPID number.
The variable cc shows the CHPID number.
System programmer response: Correct any errors
found in the I/O configuration definition or make the
appropriate connectivity or system changes to the
specified CHPID.
User response: Record the condition and report it to
your system programmer.
IHVD348I
Device paths to aa CHPID bb not
assigned to port cc LSN dd.
Explanation: During verification of device paths, I/O
operations determined that the port associated with
devices with paths to the specified CHPID could not be
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
IHVD360I
Port aa LSN bb has CHPID and device
paths assigned.
Explanation: During verification of switch ports, I/O
operations determined that both CHPIDs and device
paths were logically associated with the same port. This
condition is physically impossible and may occur if:
Chapter 9. Messages IHVA100I to IHVZ760
203
IHVD368I • IHVD382I
v There are errors in the I/O configuration definition
for the CHPID or control units.
v The CHPID and control unit is a member of a
channel-to-channel relationship, where the complete
path is defined in the I/O configuration definition. In
this case, the message is informational and might not
represent an error condition.
The variable aa shows the port.
The variable bb shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
IHVD368I
Cannot assign devices to
unimplemented port aa LSN bb.
Explanation: During verification of device paths, I/O
operations discovered that the control unit was
assigned to an unimplemented port. This condition is
physically impossible and occurs if there are errors in
the I/O configuration definition for the CHPID
(incorrect SWITCH=parameter), or control unit (incorrect
LINK=parameter). This will also occur if ports
associated with a control unit are defined in the I/O
configuration definition but were not implemented on
the specified switch.
The variable aa shows the port.
The variable bb shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
IHVD370I
Cannot determine port for aa CHPID bb
on LSN cc.
Explanation: During verification of CHPID ports, I/O
operations could not determine the port for the
specified CHPID on the specified switch. Possible
causes of this condition are:
v I/O configuration definition errors for the CHPID or
control unit.
The variable dd shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Determine the cause of the problem
and take the appropriate action. If the I/O
configuration definition is in error, record the problem
and report it to your system programmer.
IHVD378I
aa CHPID bb not assigned to port cc
LSN dd.
Explanation: During verification of CHPID ports, I/O
operations determined that the port associated with the
specified CHPID could not be assigned. This occurs if
there are I/O configuration definition errors for a
converter-type CHPID, and an expected dedicated
connection is not found.
The variable aa shows the CHPID type.
The variable bb shows the CHPID number.
The variable cc shows the port.
The variable dd shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
IHVD380I
Multiple LSNs incorrectly assigned to
switch aa. LSN bb chosen.
Explanation: During verification of the device number
associated with the switch, multiple logical switch
numbers were indicated for this switch in IOCP data.
Because there can be only one logical switch number
for a switch, I/O operations selected the indicated
logical switch number.
The variable aa shows the device number.
The variable bb shows the logical switch number.
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: Record the condition and report it to
your system programmer.
v The required dedicated connection between ports on
the switch has not been established to support the
switch, or the switch paths are offline.
IHVD382I
v The CHPID or the port associated with the CHPID is
not operational, or the switch port is blocked.
Explanation: During verification of the control unit
port defined in IOCP data, inconsistent port
assignments were detected. This could represent errors
in the I/O configuration definition.
v The required chain between switches has not been
established.
v In the case of a converter-type CHPID, none of the
devices defined to that CHPID could be brought
online.
The variable aa shows the CHPID type.
The variable bb shows the CHPID number.
204
System Automation for z/OS Messages and Codes:
Multiple ports incorrectly assigned to
switch aa. Port bb used.
The variable aa shows the device number.
The variable bb shows the port number.
System programmer response: Correct any errors
found in the I/O configuration definition.
IHVD385I • IHVD398I
User response: Record the condition and report it to
your system programmer.
IHVD385I
Multiple IDs for CU aa, ID bb chosen.
Explanation: During verification of the control unit,
I/O operations determined that more than one ID is
associated with the control unit. There are two
situations that create this message:
v Devices in the same control unit return node
descriptor information according to “best practice”.
In this case the message might indicate an I/O
configuration definition error or a cabling problem
for the control unit.
v Devices in the same control unit do not return node
descriptor information according to “best practice”,
which occurs when their LCUs have defined
different SDCs. In this case the message does not
indicate a problem.
Best Practice: The node ID - the rightmost part of a
node descriptor (ND) - consists of two parts:
v A 26-byte EBCDIC value that represents the SDC ID
that describes the type, model, manufacturer, and
serial number.
v A 2-byte hexadecimal interface ID that makes the
node ID unique.
The node ID must be worldwide unique. The “best
practice” defines the SDC ID to be unique for all node
IDs of a processor, switch, or control unit, which almost
all manufacturers conform to. One known exception is
EMC Disk Library for Mainframe model 4080. For
example, the I/O operations API command "Q E CU V
cu_number" returns different values in the fields PD
and CU_PTOK for the system that issues this message
but the same value for the system that does not report
the message.
The specified ID is selected to represent the control
unit.
The variable aa shows the control unit number.
The variable bb shows the unique identifier.
System programmer response: Correct any errors that
are found in the I/O configuration definition.
User response: If errors in the I/O configuration
definition are determined to be the problem, record the
condition and report it to your system programmer. If
you determine a cabling problem, take appropriate
action.
IHVD387I
aa bb misconfigured, NED=cc.
Explanation: When verifying the specified resource,
I/O operations determined that more than one node
element descriptor (NED) is associated with the
resource. This problem was probably caused by an I/O
configuration definition error, a cabling problem for the
resource, or an incorrect customization and setup of the
I/O resource. The indicated NED is selected to
represent the control unit or device.
The variable aa shows CU or DEVICE.
The variable bb shows the control unit or device
number.
The variable cc shows NED (NED selected by I/O
operations to represent the resource.)
System programmer response: Correct any errors
found in the I/O configuration definition.
User response: If errors in the I/O configuration
definition are determined to be the problem, record the
condition and report it to your system programmer. If a
cabling problem is determined, correct the error.
IHVD390I
Type for CHPID aa respecified to bb.
Explanation: I/O operations respecified this CHPID’s
type to reflect information obtained during verification.
This can occur if:
v There was a change in switch connectivity, such as
after any connectivity command was performed.
v There was a change in the operational state of the
CHPID, which could occur following a CHPID
reconfiguration or the detection of a port or cable
failure.
The variable aa shows the CHPID number.
The variable bb shows the CHPID type.
User response: None.
IHVD395I
aa CHPID bb path is misdefined.
Explanation: During verification of paths associated
with the specified CHPID, I/O operations detected a
mismatch between what is defined in the channel
subsystem configuration data and what is described in
the ESCON/FICON Director configuration. This
condition could occur if a chained path was incorrectly
defined, an error was made in the I/O configuration
data for the CHPID, or a cable was incorrectly installed.
The variable aa shows the CHPID type.
The variable bb shows the CHPID number.
User response: Determine the cause of the path
mismatch and take appropriate action.
IHVD398I
CHPID status could not be verified.
Explanation: An error was encountered during I/O
operations verification of CHPID status. This could
occur during I/O operations starting or command
processing. Possible reasons for the error could be a
GETMAIN failure or a VM Diagnose FC error.
System programmer response: Report the problem to
your IBM Support Center.
Chapter 9. Messages IHVA100I to IHVZ760
205
IHVD400I • IHVD833I
IHVD400I
Host and CHAIN data for switch aa has
been lost.
Explanation: The VTAM names or TCP/IP host names
of some I/O operations base programs and any chain
definitions associated with the switch aa have been
overlaid. Intersystem communication may not be
possible.
The variable aa shows the switch device number.
User response: Enter a Reset Switch command on all
I/O operations that have this switch allocated to them
to restore the VTAM names and TCP/IP host names. If
you suspect a chaining definition is lost, reenter the
CHAIN command.
IHVD410I
Path test was successful.
Explanation: Self-explanatory.
IHVD420I
Explanation: I/O operations has detected that the
active IODF on the first host, which is the primary host
and whose VTAM application name or TCP/IP host
name replaces aa, is no longer synchronized with the
second, or peer, host, whose VTAM application name
or TCP/IP host name replaces bb. This condition can
impair I/O operations' ability to process its
multisystem commands, such as queries, REMOVE
DEV, and RESTORE DEV, and to display unified
system images.
User response: Perform a dynamic I/O activation on
the primary host using the same IODF that has been
activated on the peer host.
IHVD421I
User response: None.
IHVD411I
Unable to perform path test, RC=aa
Reason=bb.
Explanation: The path test service failed.
The variable aa shows the service return code.
The variable bb shows the reason code.
System programmer response: Refer to the
description of the IOSPTHV macro in MVS
Programming: Authorized Assembler Services Reference,
Volume 2 (ENFREQ-IXGWRITE).
User response: Report the problem to your IBM
Support Center, supplying this message, the return
code, and the reason code, if provided.
aa and bb no longer share a common
IODF.
IODF activation caused loss of common
IODF with hosts:
Explanation: This header message precedes one or
more IHVD422I messages that list the hosts that I/O
operations detected that the I/O definition file (IODF)
was activated on, and which has caused IODF
synchronization to be lost with the peer hosts. This
condition can impair I/O operations' ability to process
its multisystem commands, such as queries, REMOVE
DEV, and RESTORE DEV, and to display unified
system images.
User response: Perform a dynamic I/O activation on
the host systems that are specified in the subsequent
IHVD422I messages, using the currently active IODF.
IHVD422I
aa, bb, cc, dd, ee, ff
Explanation: See message IHVD421I.
IHVD412I
Unable to determine the ND for path aa
of CU bb.
Explanation: I/O operations could not determine the
node descriptor for this path of the control unit. This
message is only issued for control units that are
attached to cascaded switches. A missing node
descriptor can lead to unpredictable results when
manipulating the entry port or destination port of the
path whose node descriptor is missing. For example,
the paths of the affected devices are not varied
ONLINE or OFFLINE.
The variable aa shows the CHPID number.
The variable bb shows the control unit number.
User response: Use the MVS command D M=CU(uuuu)
to determine the reason why the path is not available.
Make the path available, if needed.
The variablesaa, bb, cc, dd, ee, and ff show the VTAM
application or TCP/IP host names of the hosts.
User response: See message IHVD421I.
IHVD830I
Configuration change:
Explanation: This header message precedes one or
more IHVD333I, IHVD334I, IHVD339I, IHVD833I,
IHVD834I, and IHVD839I messages.
User response: None.
IHVD833I
DEVN aa-bb added to the I/O-OPS
database.
Explanation: I/O operations added a continuous
range of resources to its internal database. This appears
only on the message log.
v The variable aa shows the first device number.
v The variable bb shows the last device number.
User response: None.
206
System Automation for z/OS Messages and Codes:
IHVD834I • IHVI003E
IHVD834I
DEVN aa-bb deleted from the I/O-OPS
database
Explanation: I/O operations deleted a continuous
range of resources from its internal database. This
appears only on the message log.
The variable aa shows the first device number.
The variable bb shows the last device number.
User response: None.
IHVD839I
DEVN aa-bb deleted from and added to
the I/O-OPS database.
Explanation: I/O operations deleted a continuous
range of resources from its internal database and then
added the same range to its internal database. This
appears only on the message log.
v The variable aa shows the first device number.
v The variable bb shows the last device number.
User response: None.
IHVD950I
System programmer response: Identify and fix the
problem. Restart I/O operations.
I/O-OPS is not operational.
Explanation: I/O operations terminated normally or
abnormally.
User response: Try to restart I/O operations.
IHVD999E
No session with aa. OPNDST failed,
RC=bb FB=cc Loc=dd.
Explanation: A VTAM session setup request between
this host and the I/O operations host with the VTAM
name aa has failed.
The variable aa shows the I/O operations VTAM
name.
The variable bb shows the OPNDST return code.
The variable cc shows the OPNDST feedback code.
The variable dd shows M or X depending on where
the failure was detected, either in the mainline code
or in the exit code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take the appropriate action.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI002I is sent.
Lack of a session is considered a “vote of NO” in
consensus processing.
ESTAE failed.
Explanation: Owing to an ESTAE failure, the I/O
operations ESTAE environment could not be
established during program startup.
IHVD998I
IHVI001E
I/O-OPS Abend aa, CSECT=bb, PSW=cc
dd.
Explanation: A system service or instruction failed
and I/O operations cannot recover. An I/O operations
dump was generated and I/O operations stopped.
The variable aa shows the system abend code.
The variable bb shows the failing CSECT name.
The variable cc shows the failing program status
word (PSW) left half.
The variable dd shows the failing program status
word (PSW) right half.
System programmer response: Save the I/O
operations dump and the console log. Report the
problem to your IBM Support Center. Try to restart I/O
operations.
IHVI002I
Session set up between aa and bb.
Explanation: A VTAM OPNDST successfully set up a
session between the I/O operations hosts with the
VTAM names aa and bb.
The variables aa and bb show the I/O operations
VTAM names.
User response: None.
IHVI003E
No communication with VTAM. OPEN
ACB failed, RC=aa.
Explanation: The VTAM OPEN ACB request failed
with return code aa. This host is not able to
communicate with any other host and is running in the
minimal operating environment unless TCP/IP
communication could be established.
The variable aa shows the VTAM OPEN ACB error
return code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take appropriate action.
User response: Any subsequent I/O operations
command issues the OPEN ACB. If the OPEN ACB is
successful, I/O operations attempts to set up sessions
with other hosts. If the OPEN ACB fails, this host
remains in the minimal operating environment in case
a TCP/IP communication could also not be established
and requires the FORCE option to be entered with
connectivity commands.
Chapter 9. Messages IHVA100I to IHVZ760
207
IHVI004E • IHVI007E
IHVI004E
Communication with aa has been lost.
Explanation: The VTAM session between this host and
the I/O operations host with the VTAM name aa has
been lost. There is no communication between these
two hosts until the session is reestablished.
The variable aa shows the I/O operations VTAM
name.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take the appropriate action.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI002I is sent. If the
attempt fails, message IHVI001E is issued.
Lack of a session is considered a “vote of NO” in
consensus processing. If the command must be
processed, there are the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Reset Host aaOFF can be entered to temporarily
ignore the I/O operations host with the VTAM name
aa.
v Reset Host aaPURGE can be entered to permanent
ignore the I/O operations host with the VTAM name
aa.
IHVI005E
Unable to receive data. RECEIVE ANY
failed, RC=aa FB=bb.
Explanation: The VTAM RECEIVE ANY that was sent
to get data from other I/O operations hosts has failed.
The variable aa shows the VTAM return code.
The variable bb shows the VTAM feedback code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take appropriate action.
User response: Any subsequent I/O operations
command sends RECEIVE ANY. If the attempt is
successful, normal communication between hosts
continues.
If the RECEIVE ANY continues to fail, no data can be
retrieved from other I/O operations hosts. This is
considered a “vote of NO” in consensus processing.
If a command must be processed, reenter the command
with the FORCE option. This causes all “votes of NO”
to be ignored.
IHVI006E
Unable to send to aa. SEND failed,
RC=bb FB=cc Loc=dd.
Explanation: During a SEND to the I/O operations
host with the VTAM name aa, the VTAM SEND failed
with return code bb and feedback code cc. This is
considered a “vote of NO” in consensus processing.
208
System Automation for z/OS Messages and Codes:
The variable aa shows the I/O operations VTAM
name.
The variable bb shows the VTAM return code.
The variable cc shows the VTAM feedback code.
The variable dd shows M or X depending on where
the failure was detected, either in the mainline code
or in the exit code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take the appropriate action.
User response: Any subsequent I/O operations
command attempts to send data. If the SEND is
successful, normal processing continues.
Failure of the SEND results in a lack of response from
the named host. This is considered a “vote of NO” in
consensus processing. If the command must be
processed, there are the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Reset Host aaOFF can be entered to temporary ignore
the I/O operations host with the VTAM name aa.
IHVI007E
Unable to receive from aa. RECEIVE
failed, RC=bb FB=cc.
Explanation: While attempting to get data from the
I/O operations host with the VTAM name aa, the
VTAM RECEIVE failed with return code bb and
feedback code cc. This is considered a “vote of NO” in
consensus processing.
The variable aa shows the I/O operations VTAM
name.
The variable bb shows the VTAM return code.
The variable cc shows the VTAM feedback code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take appropriate action.
If return code zero indicates that the RECEIVE has
been completed successfully by VTAM, I/O operations
has detected an error within the data received, for
example, invalid record length. In this case check your
VTAM definitions for I/O operations host-to-host
communications. Check your logmode definitions for a
RUSIZE of zero as recommended on the VBUILD TYPE
APPL example. Refer to IBM Tivoli System Automation
for z/OS Planning and Installation for further information
about the VTAM definitions.
User response: Any subsequent I/O operations
command attempts to receive data. If the RECEIVE is
successful, normal processing continues.
Failure of the RECEIVE results in a lack of response
from the named host. This is considered a “vote of
NO” in consensus processing. If the command must be
processed, there are the following options:
IHVI008E • IHVI101I
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
codes and take appropriate action.
v Reset Host aaOFF can be entered to temporary ignore
the I/O operations host with the VTAM name aa.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI002I is sent.
IHVI008E
Lack of a session is considered a “vote of NO” in
consensus processing. If the command must be
processed, there are the following options:
SETLOGON failed, RC=aa FB=bb.
Explanation: The VTAM SETLOGON request has
failed with return code aa and feedback code bb. This
host is not notified of any new I/O operations host
because the SCIP exit cannot be driven.
The variable aa shows the VTAM return code.
The variable bb shows the VTAM feedback code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take appropriate action.
IHVI009E
Session not set up with aa. GENCB
failed, RC=bb FB=cc.
Explanation: The VTAM GENCB failed with return
code bb and feed back code cc. The session was not set
up between this host and the I/O operations host with
the VTAM name aa.
The variable aa shows the I/O operations VTAM
name.
The variable bb shows the VTAM return code.
The variable cc shows the VTAM feedback code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
codes and take appropriate action.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI002I is sent.
Lack of a session is considered a “vote of NO” in
consensus processing. If the command must be
processed, there are the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Reset Host aaOFF can be entered to temporarily
ignore the I/O operations host with the VTAM name
aa.
IHVI010E
No session with aa. OPNSEC failed,
RC=bb FB=cc.
Explanation: A request to establish a session from this
host to the I/O operations host with the VTAM name
aa failed with return code bb and feedback code cc>.
The variable aa shows the I/O operations VTAM
name.
The variable bb shows the OPNSEC return code.
The variable cc shows the OPNSEC feedback code.
System programmer response: Refer to VTAM
Messages and Codes for an explanation of the return
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Reset Host aaOFF can be entered to temporarily
ignore the I/O operations host with the VTAM name
aa.
IHVI011E
Unable to write host data at switch.
Explanation: An error occurred when trying to send
WRITE HOST DATA to one or more switches. This data is
the I/O operations VTAM name and TCP/IP name of
this host. If the names do not appear in the switch host
data area, other I/O operations hosts do not know of
this host and no communication occurs with this host.
User response: Use the DISPLAY SWITCH command
to determine the cause of the failure. Enter Reset
Switch to have the I/O operations VTAM name written
to the switch host data area.
IHVI012I
Cannot disable switch operator alert.
Explanation: An error occurred when trying to send
DISABLE LOCAL OPERATOR ALERT to one or more
switches. This causes a warning message to be sent to
any local switch operator when making changes to the
switch.
User response: None.
IHVI013E
Unable to erase host data at switch.
Explanation: An error occurred when trying to send
WRITE HOST DATA to one or or more switches. This host
was attempting to erase its I/O operations VTAM name
and TCP/IP host name from the host data area as I/O
operations was stopping. By leaving the name in the
host data area, any new I/O operations hosts attempt
to create a VTAM or TCP/IP session with this host.
User response: The Reset Host Purge command can
be sent from any other I/O operations host to either
erase that name from the host data area or ignore that
host in consensus processing.
IHVI101I
No TCP session with aa. bb failed,
RSN=cc.
Explanation: A TCP session setup request between
this host and the I/O operations host with the TCP/IP
host name aa has failed.
The variable aa shows the TCP/IP host name.
The variable bb shows the API function that failed.
Chapter 9. Messages IHVA100I to IHVZ760
209
IHVI102I • IHVI106E
The variable cc shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI102I is sent. Lack of
a session is considered a “vote of NO” in consensus
processing.
IHVI102I
Outbound connection set up between aa
and bb.
Explanation: A TCP/IP outbound connection has been
successfully established between the I/O operations
hosts with TCP/IP host namesaa and bb.
The variables aa and bb show TCP/IP host names.
User response: None.
IHVI103E
No communication with TCP/IP. aa
failed, RSN=bb.
Explanation: The socket of the server port could not
be bound. This host is not able to communicate with
any other host via TCP/IP. If VTAM communication is
also unavailable, this host is running in the minimal
operating environment.
The variable aa shows the API function that failed.
The variable bb shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: Any subsequent I/O operations
command issues the bind request. If the bind is
successful, I/O operations will attempt to set up
sessions with other hosts that do not have a VTAM
session with this host. If the bind fails and VTAM
communication is also unavailable, this host remains in
the minimal operating environment and requires the
FORCE option to be entered with connectivity
commands.
IHVI104E
Communication with aa has been lost.
Explanation: The TCP/IP connection between this
host and the I/O operations host with the TCP/IP host
name aa has been lost. There is no communication
between these two hosts until the connection is
reestablished.
The variable aa shows the TCP/IP host name.
User response: Any subsequent I/O operations
command attempts to establish this connection. If the
210
System Automation for z/OS Messages and Codes:
attempt is successful, message IHVI102I is sent. If the
attempt fails, message IHVI101E is issued. Lack of a
connection is considered a “vote of NO” in consensus
processing. If the command must be processed, you
have the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Enter Reset Host aa OFF to temporarily ignore the
I/O operations host with the TCP/IP host name aa.
v Enter Reset Host aa PURGE to permanently ignore
the I/O operations host with the TCP/IP host name
aa.
IHVI105E
Unable to receive data. SELECT failed.
RSN=aa.
Explanation: The TCP/IP SELECT that was issued to
get data from other I/O operations hosts has failed.
The variable rs shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: Any subsequent I/O operations
command issues the SELECT. If the attempt is
successful, normal communication between hosts
continues. If the SELECT continues to fail, no data can
be received from other I/O operations hosts. This is
considered a “vote of NO” in consensus processing. If a
command must be processed, reenter the command
with the FORCE option. This causes all “votes of NO”
to be ignored.
IHVI106E
Unable to send data to aa. RSN=bb.
Explanation: During a SEND to the I/O operations
host with the TCP/IP host name aa, the TCP/IP SEND
failed with error code bb. This is considered a “vote of
NO” in consensus processing.
The variable ho shows the TCP/IP host name.
The variable rs shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: Any subsequent I/O operations
command attempts to send data. If the SEND is
successful, normal processing continues. Failure of the
SEND results in a lack of response from the named
host. This is considered a “vote of NO” in consensus
processing. If the command must be processed, you
have the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
IHVI107E • IHVI121I
v Enter Reset Host aa OFF to temporary ignore the I/O
operations host with the TCP/IP host name aa.
IHVI107E
Unable to receive data from aa. RSN=bb.
Explanation: While attempting to get data from the
I/O operations host with the TCP/IP host name aa, the
TCP/IP RECV failed with error code bb. This is
considered a “vote of NO” in consensus processing.
The variable ho shows the TCP/IP host name.
The variable rs shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: Any subsequent I/O operations
command attempts to receive data. If the RECV is
successful, normal processing continues. Failure of the
RECV results in a lack of response from the named
host. This is considered a “vote of NO” in consensus
processing. If the command must be processed, you
have the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Enter Reset Host ho OFF to temporary ignore the I/O
operations host with the TCP/IP host name aa.
IHVI109E
Connection not set up with aa. RSN=bb.
Explanation: TCP/IP failed to connect the I/O
operations host with the TCP/IP host name aa. The
connection was not set up between this host and the
I/O operations host with the TCP/IP host name aa.
The variable ho shows the TCP/IP host name.
The variable rs shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take the
appropriate action.
User response: Any subsequent I/O operations
command attempts to establish this session. If the
attempt is successful, message IHVI102I is sent. Lack of
a session is considered a “vote of NO” in consensus
processing. If the command must be processed, you
have the following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Enter Reset Host aa OFF to temporary ignore the I/O
operations host with the TCP/IP host name aa.
IHVI114I
TCP/IP communication suppressed by
user.
Explanation: The communication via TCP/IP has been
suppressed by the user.
System programmer response: If you want to
communicate via TCP/IP the next time, make sure that
the server port is predefined in the hlq.ETC.SERVICES
data set. See the step “Define Host-to-Host
Communications” in chapter “Installing SA z/OS on
Host Systems” in IBM Tivoli System Automation for z/OS
Planning and Installation.
User response: I/O operations does not attempt to set
up sessions with other hosts using TCP/IP. If VTAM is
also unavailable, this host remains in the minimal
operating environment and requires the FORCE option
to be entered with connectivity commands.
IHVI115E
TCP/IP host name aa too long.
Explanation: I/O operations could not resolve the
TCP/IP node name into an alias name of up to 8
characters. I/O operations closes the connection to the
remote host.
The variable aa shows the TCP/IP host name.
System programmer response: If you want to
communicate via TCP/IP the next time, make sure that
you provide an alias name of up to 8 characters for the
named host.
User response: None.
IHVI116E
TCP/IP communication has terminated.
Explanation: I/O operations receives the condition
that TCP/IP has terminated.
User response: When TCP/IP becomes available again
I/O operations tries to reestablish the connections that
have been closed. These connections are currently
returning a “vote of NO” in consensus processing. If
the command must be processed, you have the
following options:
v Reenter the command with the FORCE option. This
causes all “votes of NO” from all hosts to be ignored.
v Enter Reset Host aa OFF to temporary ignore the I/O
operations host with the TCP/IP host name aa.
v Enter Reset Host aa PURGE to permanent ignore the
I/O operations host with the TCP/IP host name aa.
IHVI121I
Connection rejected. Function aa failed,
RSN=bb.
Explanation: A remote host whose name was
unknown up to this point in time sent a connection
request. The connection was rejected due to an error
condition in the named function.
The variable aa shows the API function that failed.
Chapter 9. Messages IHVA100I to IHVZ760
211
IHVI122I • IHVO003I
The variable bb shows the error code.
System programmer response: Refer to “Appendix B.
Return codes” in z/OS Communications Server: IP Sockets
Application Programming Interface Guide and Reference for
an explanation of the error code and take appropriate
action.
User response: None.
IHVI122I
Inbound connection set up between aa
and bb.
Explanation: A TCP/IP inbound connection has been
established successfully between the I/O operations
hosts with TCP/IP host namesaa and bb.
The variables aa and bb show TCP/IP host names.
User response: None.
IHVI130I
OMVS segment of aa not found,
SAF/RACF RC=bb/cc RSN=dd
Explanation: I/O operations could not find an OMVS
segment that has been defined for its user ID. Because
some TCP/IP macros require this segment, the TCP/IP
communication is ignored for the lifetime of I/O
Operations.
The variable aa shows the user ID of I/O
operations.
The variable bb shows the SAF return code of the
RACROUTE EXTRACT request.
The variable cc shows the RACF return code of the
RACROUTE EXTRACT request.
The variable dd shows the reason code of the
RACROUTE EXTRACT request.
User response: If you want I/O operations to use
TCP/IP, refer to the installation step “Customizing I/O
Operations” in IBM Tivoli System Automation for z/OS
Planning and Installation for information about how to
define an OMVS segment. After you have defined the
OMVS segment you need to restart I/O operations.
| IHVI131I
Error aa received from bb
| Explanation: I/O operations received an exception
| event from the indicated host. The connection to the
| host is closed.
|
The variable aa shows the error code.
|
The variable bb shows the name of the host or its
|
alias.
|
|
|
|
|
User response: Refer to the appendix "Return Codes"
in z/OS Communications Server: IP Sockets Application
Programming Interface Guide and Reference for an
explanation of the error code and take the appropriate
action.
212
System Automation for z/OS Messages and Codes:
IHVL001I
Message aabb not found in module cc.
Explanation: I/O operations requested a message that
could not be found in the indicated message module.
The variable aa shows the component ID and the
sub-component ID.
The variable bb shows the message number.
The variable cc shows the name of the message
module.
System programmer response: Record the sequence of
events leading up to the message, including the
message number. Report the problem to your IBM
Support Center.
IHVL005I
Command caused data overflow.
Explanation: The command completed, but an
overflow condition occurred that resulted in a non-zero
return code. This overflow condition was caused by the
command generating more information than can be
returned in a single display.
User response: Reenter several commands with
smaller ranges.
IHVO000I
I/O-OPS is ready to process operator
commands.
Explanation: Self-explanatory.
User response: Enter a I/O operations command.
IHVO001I
No I/O-OPS command was specified.
Explanation: An MVS MODIFY or a VM CP SEND
command was entered to call I/O operations but it did
not contain an I/O operations command. This could
have been entered from the system console or sent
from an application program.
User response: Enter the MODIFY or SEND command
again with a I/O operations command and any
required operands. Or, if applicable, correct the code
statement that calls the I/O operations API so that the
first parameter is an I/O operations command.
IHVO002I
aa is not a valid I/O-OPS command.
Explanation: The specified command is not a valid
I/O operations command.
The variable aa shows the incorrect command.
User response: Correct the command and reenter it.
IHVO003I
No operands were specified for the
command.
Explanation: The command that was entered requires
at least one operand.
IHVO004I • IHVO018I
User response: Enter the command with the required
operands.
IHVO004I
aa exceeds 24 characters.
Explanation: The specified operand is longer than the
maximum length of 24 characters.
The variable aa shows the first 24 characters of the
operand.
User response: Correct the operand and reenter the
command.
IHVO010I
aa is not a valid operand.
Explanation: The operand specified as aa is not valid.
For a REMOVE/RESTORE CHP command, an asterisk
(*) is not valid as an I/O operations host name.
The variable aa shows the operand that is not valid.
User response: Correct the operand and reenter the
command.
IHVO011I
One or more operands are missing.
Explanation: Self-explanatory.
IHVO005I
aa is not a valid option.
Explanation: The option specified is not a valid I/O
operations command option.
The variable aa shows the option that is not valid.
User response: Correct the option and reenter the
command.
IHVO006I
aa and bb are opposing options.
Explanation: You cannot specify the two options that
replace aa and bb in the same command. For example,
you cannot specify F and NOF in the same command.
The variable aa and bb show the conflicting options.
User response: Correct one or both options and
reenter the command.
IHVO007I
User response: Correct the parameters and reenter the
command.
Combination of '*' operands not valid.
Explanation: Specifying the all operand (*) for both
the third and fourth operands on the DISPLAY DEV or
the DISPLAY NAME command is not allowed. For
example, neither DISPLAY DEV * * nor DISPLAY NAME *
* is a valid I/O operations command.
User response: Correct the operands and reenter the
command.
IHVO009I
IHVO012I
A port name of '*' is not valid on the
WRITE command.
Explanation: A single asterisk (*) cannot be assigned
as the name of a port.
User response: Use a valid port name.
IHVO014I
Specified I/O-OPS command is not
valid on this interface.
Explanation: The specified I/O operations command
cannot be entered from the interface you are using.
User response: Reenter the command from the
appropriate interface.
Too many operands were specified.
Explanation: The number of operands specified
exceeds the maximum number that I/O operations can
process.
IHVO008I
User response: Reenter the command with the correct
number of operands.
aa is not a valid port address.
Explanation: The port address specified is not a valid
port address.
The variable aa shows the port address that is not
valid.
User response: Correct the port address and reenter
the command.
IHVO016I
aa option is limited to connectivity
commands.
Explanation: The specified option can be used with
connectivity commands only.
The variable aa shows the connectivity command
option.
User response: Correct the option and reenter the
command.
IHVO017I
NOFORCE and NOVARY are conflicting
options.
Explanation: The NOForce and NOVary options
cannot be used together in the same I/O operations
command.
User response: Correct the options and reenter the
command.
IHVO018I
FORCE, VARY and BACKOUT are
conflicting options.
Explanation: The Force, Vary, and Backout options
cannot be used together in the same I/O operations
command.
Chapter 9. Messages IHVA100I to IHVZ760
213
IHVO019I • IHVO032I
User response: Correct the options and reenter the
command.
IHVO023I
IHVO019I
Explanation: The Process and NOProcess options are
limited to the Sync Switch command.
ONLY cannot be used with a second
operand of aa.
Explanation: The ONLY option cannot be used with a
second operand of * or (*).
The variable aa is either * or (*).
For example, the following Allow commands are not
valid:
Allow PRT1 * 123 ONLY
Allow PRT2 (*) 123 ONLY
The ONLY option is limited to the Allow command.
Therefore, this error condition applies to the ALLOW
command only.
User response: Replace with port or port name.
aa option is limited to the SYNC
SWITCH command.
The variable aa is either PROCESS or NOPROCESs.
For example, the following I/O operations commands
are not valid:
BLOCK PRT1 123 PROCESS
DISPLAY CHP * NOPROCESS
User response: Remove the PROCESS or NOPROCESS
option and reenter the command.
IHVO024I
aa option is limited to the DISPLAY
VARY command.
Explanation: The SYNC and FAIL options are limited
to the DISPLAY VARY command.
The variable aa is either SYNC or FAIL.
IHVO020I
aa option is limited to the ALLOW
command.
Explanation: The ONLY and ALSO options are limited
to the ALLOW command.
The variable aa is either ONLY or ALSO.
For example, the following I/O operations commands
are not valid:
For example, the following I/O operations commands
are not valid:
BLOCK PRT1 123 SYNC
DISPLAY CHP * FAIL
User response: Remove the SYNC or FAIL option and
reenter the command.
BLOCK PRT1 123 ONLY
DISPLAY CHP * ALSO
IHVO025I
User response: Remove the ONLY or ALSO option
and reenter the command.
Explanation: The Force, NOVary, and Backout options
cannot be used together in the same I/O operations
command.
IHVO021I
aa option is limited to the REMOVE
SWITCH command.
Explanation: The NODisable and Disable options are
limited to the REMOVE SWITCH command.
The variable aa is either NODISABLE or DISABLE.
For example, the following I/O operations commands
are not valid:
BLOCK PRT1 123 NODisable
DISPLAY CHP * Disable
User response: Remove the NODISABLE or DISABLE
option and reenter the command.
IHVO022I
NOCHECK and NOVARY are
conflicting options.
Explanation: The NOCheck and NOVary options
cannot be used together in the same I/O operations
command.
User response: Correct the options and reenter the
command.
214
System Automation for z/OS Messages and Codes:
FORCE, NOVARY and BACKOUT are
conflicting options.
User response: Correct the options and reenter the
command.
IHVO032I
aa option is not valid with specified
command.
Explanation: When used as options, Block and
Connect are limited to the DISPLAY PORT, DISPLAY
NAME, and DISPLAY SWITCH commands.
The variable aa is either BLOCK or CONNECT.
For example, the following I/O operations commands
are not valid:
DISPLAY CHP * BLOCK
Allow TAPE_1 123 CONNECT
User response: Remove the BLOCK or CONNECT
option and reenter the command.
IHVO033I • IHVR001I
IHVO033I
aa option is not valid with specified
command.
Explanation: The specified option is not valid for the
command that was entered.
The variable aa shows the option that is not valid.
User response: Reenter the command with valid
command options.
Unknown PARM parameter aa.
IHVO102I
Explanation: The indicated PARM parameter is not
known by I/O operations.
The variable aa is the name of the parameter.
User response: Correct or remove the parameter and
restart I/O operations.
IHVO252E
IHVO048I
aa option is not valid with specified
command.
Explanation: The ON, OFF, and PURGE options are
limited to the RESET HOST command.
The variable aa is either ON, OFF, or PURGE.
User response: Reenter the command with a valid
option.
IHVO064I
I/O-OPS is already running.
Explanation: While I/O operations was already
running on this host, an attempt was made to start
another I/O operations. The attempt to start another
I/O operations was rejected by the I/O operations
program that is already running. The I/O operations
that is running sent this message and continues
processing.
User response: None.
IHVO065I
I/O-OPS is not running.
Explanation: A STOP command was entered.
However, I/O operations was either not started or was
already stopped.
User response: None.
IHVO100I
The PARM parameter aa has been
accepted.
Explanation: The indicated PARM parameter
overrides the corresponding default value.
The variable aa is the name of the parameter.
User response: None.
IHVO101I
PARM parameter aa incorrectly
specified.
Explanation: The indicated PARM parameter has been
incorrectly specified. Either the value is missing, or the
value is incorrect, or a value has been specified for a
positional parameter.
The variable aa is the name of the parameter.
User response: Correct the value of the indicated
parameter and restart I/O operations.
ESTAE failed, RC=aa.
Explanation: The I/O operations ESTAE environment
could not be established.
The variable aa shows the return code.
System programmer response: Determine why the
ESTAE environment could not be established.
User response: For an explanation of the return code,
refer to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405. Restart I/O operations. If
this error recurs, contact your system programmer.
IHVO253E
I/O-OPS MVS Communications Input
Buffer is not valid.
Explanation: The I/O operations MVS
Communications Input Buffer (CIB) is not valid.
System programmer response: Determine why the
CIB is not valid.
IHVO255E
Unrecoverable I/O-OPS error.
Explanation: There was an unrecoverable I/O
operations error.
System programmer response: Check the console log
and the I/O operations dump to determine why this
error occurred.
IHVQ036I
Display command caused data overflow,
RC=aa RSN=bb.
Explanation: The command completed, but an
overflow condition occurred that caused a non-zero
return code to be generated. This overflow condition
was caused by the DISPLAY command generating more
information than can be returned in a single display.
User response: The command has returned as much
of the data that you requested as possible on the
interface that you are using.
IHVR001I
I/O-OPS command
Explanation: This is the control line header for a
multiple line display.
User response: None.
Chapter 9. Messages IHVA100I to IHVZ760
215
IHVR010I • IHVR014
IHVR010I
Command entered by aa on bb:
Explanation: This is the first message of the audit trail
in the system log.
The variable aa shows the user ID that the
command was entered from.
The variable bb shows the system ID where the
command was entered.
User response: None.
IHVR011I
aa
Explanation: This is the second message of the audit
trail in the system log. It is a variable length message,
with a maximum of 120 characters, that contains the
command name, command operands, and command
options that I/O operations is about to process.
The long form of the command name, operands, and
options is used for all commands except the
WRITEPORT command. On the WRITEPORT
command, the abbreviated form of the connectivity
commands, specified as operands, and the command
options are used. The following abbreviations are used
for auditing the WRITEPORT command:
Block = B
Unblock = U
Connect = C
Disconnect = N
Noforce = NOF
Force = F
Vary = V
Novary = NOV
Backout = BA
Nobackout = NOB
On a WRITEPORT command, the 6th operand (if
specified) contains 256 characters defining the allow or
prohibit status for the specified port. For this message,
the 256 characters are converted to 8 groups of 8 hex
characters each, with each bit representing a port’s
allow or prohibit status. If the bit is 0, that port is
allowed. If it is 1, it is prohibited. The groups are
separated by blanks. Some examples of this message
are:
IHVR011I GETLOCK
IHVR011I DISPLAY HOST* 0FF0
IHVR011I ALLOW (C1) (C3) 01E4 ALSO NOFORCE VARY BACKOUT
IHVR011I WRITEPORT TEST1 0FD0 UNBLOCK CONNECT 120C
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
FFFFFFFF FFFFFFFF 60000000 0000000D
NOFORCE VARY BACKOUT
User response: None.
IHVR012
aa bb cc dd ee ff
Explanation: This is the first line of a 4-line message
block of the audit trail in the system log that records
WRITEFILE and WRITESWCH commands.
216
System Automation for z/OS Messages and Codes:
It shows the first 20 bytes of the WTFL (WRITEFILE) or
WSWT (WRITESWCH) control block of each port that
is affected by the command.
Because the control blocks do not fit into a single
output line, each control block is split into 4 output
lines. The first line of these lines is prefixed by the
control block's port number in hex, for example:
IHVR011I WRITESWCH [NO]FORCE [NO]VARY [NO]BACKOUT
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
:
User response: None.
IHVR013
aa bb cc dd
Explanation: This is the second and third message of
a 4-line message block of the audit trail in the system
log that records WRITEFILE and WRITESWCH
commands.
It shows the prohibit dynamic connection mask
(PDCM) that is part of the WTFL (WRITEFILE) or
WSWT (WRITESWCH) control block of each port that
is affected by the command, for example:
IHVR011I WRITESWCH [NO]FORCE [NO]VARY [NO]BACKOUT
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
:
User response: None.
IHVR014
<aa> bb
Explanation: This is the last message of a 4-line
message block of the audit trail in the system log that
records WRITEFILE and WRITESWCH commands.
It shows the port logical name and chain information
that are part of the WTFL (WRITEFILE) or WSWT
(WRITESWCH) control block of each port that is
affected by the command, for example:.
IHVR011I WRITESWCH [NO]FORCE [NO]VARY [NO]BACKOUT
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
pn ____ ____ ____ ____ ____
(IHVR012)
____ ____ ____ ____
(IHVR013)
____ ____ ____ ____
(IHVR013)
<____________> ____
(IHVR014)
:
IHVR020I • IHVS004I
User response: None.
IHVR020I
aa command successful.
Explanation: The command completed successfully.
This is an audit trail message.
The variable aa shows the name of the command.
User response: None.
IHVR021I
aa command successful, RC=bb RSN=cc.
Explanation: This is an audit trail message. The
command completed, but a condition was detected that
caused a non-zero return code to be generated. For
example, if the Force option was used and a host
vetoed the command, the command would still be
processed.
The variable aa shows the name of the command.
IHVS001I
aa on bb is processing an I/O-OPS
command.
Explanation: Another user is processing an I/O
operations command.
The variable aa shows the user ID that the
command was entered from.
The variable bb shows the VTAM name of the I/O
operations.
User ID ACB_SYNC is used when attempting to open
the VTAM ACB at a timed interval.
User response: Either wait until the current owner has
issued an UNLOCK command or, if you have the
authority, issue a GETLOCK command to seize the
lock. (If the user ID is HW_SYNCH, this I/O
operations ID is updating its database and will release
the lock when done.)
The variable bb shows the return code.
The variable cc shows the reason code.
User response: None.
For more information about return codes and reason
codes, refer to Appendix A, “Return Codes, Status
Codes, and Reason Codes,” on page 405.
IHVR030I
aa command failed, RC=bb RSN=cc.
Explanation: This is an audit trail message. The
command either failed, or completed only partially.
Partial completion will occur where a command applies
to all switches, but a port name specified in the
command does not exist in all of them.
The variable aa shows the name of the command.
The variable bb shows the return code.
The variable cc shows the reason code.
User response: None.
IHVR040I
aa
Explanation: This message is the array header of the
audit trail multiline input record. This message has a
maximum length of 70 characters because it is used as
part of a multiline WTO to record array data on
multisystem commands that require such data to be
recorded. This message contains the number and type
of array elements that are used in the succeeding audit
records. For example, the message could be one of the
following:
IHVR040I 3 SCOPE HOSTS :
IHVR040I 15 DEVICES :
IHVR040I 5 CHPIDS:
User response: None.
IHVS002I
aa on bb has the I/O-OPS lock.
Explanation: User ID aa caused the processing lock to
be assigned to the I/O operations whose VTAM name
is bb.
The variable aa shows the user ID.
The variable bb shows the VTAM name of the I/O
operations.
User response: See the response to IHVS001I.
IHVS003I
aa on bb has taken control from you via
GETLOCK.
Explanation: User id aa has entered a GETLOCK
command to the I/O operations whose VTAM name is
bb.
The variable aa shows the user ID.
The variable bb shows the VTAM name of the I/O
operations.
User response: Wait until the other user enters the
UNLOCK command. Then use I/O operations
DISPLAY commands to determine what changed since
the other user took control from you.
IHVS004I
I/O-OPS internal error aa.
Explanation: I/O operations detected an internal
processing error.
The variable aa shows the command code.
System programmer response: Record the sequence of
events leading up to this message, this message
number, and the command code. Report the problem to
your IBM Support Center.
Chapter 9. Messages IHVA100I to IHVZ760
217
IHVT001E • IHVT170I
IHVT001E
PC routine encountered error condition
aa, RSN=bb.
Explanation: The PC routine that writes trace records
encountered the indicated error condition. The current
trace entry has not been recorded. For details of the
error condition see z/OS MVS System Codes.
The variable aa shows the system completion code.
The variable bb shows the value of the reason code.
User response: Determine the cause of the problem
and take appropriate corrective action.
IHVT002I
Component trace has not been
registered.
Explanation: Component IHVAS has not been
registered to the MVS component trace. No tracing is
performed.
User response: Search the syslog for IHVTnnn
messages to determine the reason why the trace could
not be registered. If tracing is required you need to
recycle the I/O operations address space to register the
component trace.
IHVT003I
User response: Search the syslog for IHVTnnn
messages to determine the reason why I/O operations
failed to create the data space. If tracing is required you
need to recycle the I/O operations address space to
create the data space.
IHVT006I
Unable to process trace record.
Explanation: An unrecoverable error occurred when
I/O operations tried to process a trace record.
User response: Stop and restart I/O operations.
IHVT105I
De-/Registration from/to CT failed,
RC=aa RSN=bb.
Explanation: The registration to or deregistration from
the MVS component trace failed. Tracing is unavailable
until the next startup of I/O operations.
The variable rc shows the value of the return code.
The variable rs shows the value of the reason code.
User response: Analyze the return code and reason
code (see CTRACE in z/OS MVS Programming:
Authorized Assembler Services Reference
(ALESERV-DYNALLOC), SA22-7609).
Data space for tracing is not available.
Explanation: The data space that holds intermediate
trace data could not be created. No tracing is
performed.
User response: Search the syslog for IHVTnnn
messages to determine the reason why I/O operations
failed to create the data space. If tracing is required you
need to recycle the I/O operations address space to
create the data space.
IHVT107I
CT start/stop routine abended with
completion code aa.
Explanation: The component trace start or stop
routine abended with the system completion code aa.
The TRACE command is not processed and the trace
options remain unchanged.
The variable aa shows the system completion code
of the abend.
User response: Contact your IBM Support Center.
IHVT004I
CT registration encountered a problem,
RC=aa RSN=bb.
Explanation: The component trace registration
encountered a problem related to the CTIIHVZZ
parmlib member. The registration is retried without a
parmlib member.
The variable rc shows the value of the return code.
The variable rs shows the value of the reason code.
User response: Analyze the return code and reason
code (see CTRACE in z/OS MVS Programming:
Authorized Assembler Services Reference
(ALESERV-DYNALLOC), SA22-7609).
IHVT005I
Data space for tracing is not available,
RC=aa.
Explanation: The data space that holds intermediate
trace data could not be made available to the I/O
operations address space. No tracing is performed.
The variable rc shows the value of the return code
of the ALESERV macro.
218
System Automation for z/OS Messages and Codes:
IHVT110I
CT display routine abended with
completion code aa.
Explanation: The component trace display routine
abended with the system completion code aa. The
DISPLAY command is not processed.
The variable aa shows the system completion code
of the abend.
User response: Contact your IBM Support Center.
IHVT170I
Unknown trace option found: aa.
Explanation: The variable aa shows the trace option
specified with the OPTIONS parameter of the IPCS
CTRACE command. The following are valid values:
MAX
Show all trace entries
MORE Show MIN entries plus processing relevant
entries
MIN
Show entry and exit trace entries only
ALL
Includes all the following options
IHVT171I • IHVT188I
The access method routines
The API routines running in the user's address
space
AUDIT The message service and audit routines
BASE The routines that are common to all services
CMD The routines that handle the command input
COMMUNICATION
The communication framework
CONFIG
The routines performing hardware
configuration changes
DB
The database routines
QUERY
The service routines returning database
information
RECOVERY
The recovery routines
SCHEDULE
The schedule framework
XM
The cross-memory services
AM
API
User response: Correct or delete the option.
IHVT171I
IHVT175I
Explanation: The parser found an error condition
when parsing the OPTION parameter. Processing is
terminated.
v The variable aa shows the column that caused the
parser to stop
A column value of 0 can be caused by one of the
following:
– A parameter consisting of blanks and commas
only
– A parameter length greater than 32K
– An allocation error of temporary storage
A column value greater than 0 indicates one of the
following:
– A keyword is not spelled correctly
– A keyword is incorrectly delimited
– A trace option is incorrectly delimited
User response: Correct the OPTION parameter, or
increase the region size.
Unknown keyword found: aa.
Explanation: The parser found a keyword that is not
valid. The keyword is ignored. Valid keywords are:
v JOBNAME
v ASID
v TASKID
v MODULE
v POS
IHVT176I
Too many value(s) specified for
keyword aa.
Explanation: All keyword options that are allowed for
the OPTIONS parameter support up to five different
values. However, the parser found at least one
additional value for the indicated keyword. The surplus
values are ignored.
The variable aa shows the affected filter option.
IHVT184I
Value aa of keyword bb is missing.
Explanation: The parser expects a string of at least
one character for the keyword option aa with the
OPTIONS parameter. However, no string or a string
representing the NULL string has been found.
The external writer has been stopped
automatically.
Explanation: The component trace has been stopped
either by a TRACE command or during I/O operations
termination. The start/stop routine detected that the
external writer was active, but has not connected any
other component trace. As a result, the start/stop
routine issued the TRACE CT,WTRSTOP command.
User response: None.
IHVT185I
User response: Correct the keyword option.
IHVT173I
No SCOPE option specified.
User response: Correct the OPTIONS parameter. Refer
to "Using Trace Services for I/O Operations" in IBM
Tivoli System Automation for z/OS User's Guide for valid
trace options.
User response: Specify a correct keyword.
IHVT172I
Parsing the OPTION parameter stopped
at column aa.
The external writer has been started
automatically.
Explanation: The TRACE command specified the
parameter for the external writer. The start/stop
routine detected that the external writer has not been
started yet. As a result, the trace routine issued the
TRACE CT,WTRSTART command.
User response: None.
The variable aa shows the value that is missing.
The variable bb shows the affected filter option.
User response: Correct the value.
IHVT188I
Parse service failed, RC=aa.
Explanation: The start/stop routine encountered a
storage problem when parsing the OPTION parameter.
The TRACE command is discarded.
The variable aa shows the return code of the service.
User response: Try the command later. If the problem
Chapter 9. Messages IHVA100I to IHVZ760
219
IHVT191I • IHVU004I
persists, contact your IBM Support Center.
IHVT191I
Parameter WTR=DISCONNECT is not
supported on a start trace command.
Explanation: The start/stop routine expects the name
of the startup procedure of the external writer to be
used. However, it found the reserved word
DISCONNECT. The TRACE command is discarded.
User response: Correct the WTR parameter and
reissue the TRACE command.
IHVT192I
Invalid trace option specified.
Explanation: A non-positional trace option was found
that is not supported. The TRACE command is
discarded.
User response: Correct the OPTION parameter and
reissue the TRACE command. For valid options see
message IHVT170I.
IHVT193I
No trace option specified.
Explanation: Either the OPTION parameter was
omitted, or no value was specified for it. The trace
command is rejected.
User response: Correct the OPTION parameter and
reissue the TRACE command. For valid options see
message IHVT170I.
IHVT199I
Explanation: The start/stop routine encountered an
error when passing the last trace buffer to the external
writer synchronously. The buffer is not available in the
output data set.
The variable aa shows the value of the return code.
The variable bb shows the value of the reason code.
User response: Analyze the return code and the
reason code (see CTRACEWR in z/OS MVS
Programming: Authorized Assembler Services Reference
(ALESERV-DYNALLOC), SA22-7609).
IHVU002I
The variable aa shows the I/O operations return
code.
The variable bb shows the CMS return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the CMS return code,
refer to z/VM CP Programming Services (SC24-6084).
Unknown trace option found: aa.
Explanation: An unsupported trace option has been
detected The trace command is rejected.
The variable aa shows the improper option.
User response: Correct the OPTION parameter and
reissue the TRACE command. For valid options see
message IHVT170I.
IHVT198I
Data space could not be created, RC=aa
RSN=bb.
Explanation: The data space that holds the
intermediate trace buffers could not be created for the
indicated reason. Tracing is unavailable until the next
startup of I/O operations.
The variable aa shows the value of the return code.
The variable bb shows the value of the reason code.
User response: Analyze the return code and the
reason code (see DSPSERV in z/OS MVS Programming:
Authorized Assembler Services Reference
(ALESERV-DYNALLOC), SA22-7609).
220
System Automation for z/OS Messages and Codes:
HNDIUCV SET macro failed, I/O-OPS
RC=aa, CMS RC=bb.
Explanation: A request from I/O operations in VM to
identify itself as an IUCV program to CMS failed.
IHVU003I
IHVT194I
Last trace buffer could not be written,
RC=aa RSN=bb.
I/O-OPS not logged on. CONNECT
macro RC=aa RSN=bb.
Explanation: A request from a user in VM to establish
an IUCV communication path to I/O operations failed
because I/O operations is not logged on.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Log on I/O operations and reenter the
command. For more information about return codes
and reason codes, refer to Appendix A, “Return Codes,
Status Codes, and Reason Codes,” on page 405.
IHVU004I
CONNECT macro failed, RC=aa
RSN=bb.
Explanation: A request from a user to establish an
IUCV communication path to I/O operations failed
because the I/O operations virtual machine has not
declared an external interrupt buffer.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center. For more information about return
codes and reason codes, refer to Appendix A, “Return
Codes, Status Codes, and Reason Codes,” on page 405.
IHVU005I • IHVU012I
IHVU005I
Not IUCV authorized. CONNECT macro
RC=aa RSN=bb.
Explanation: A request from a user in VM to establish
an IUCV communication path to I/O operations failed
because the user was not authorized to establish an
IUCV path to I/O operations.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Contact your system programmer to
obtain proper IUCV authorization. For more
information about return codes and reason codes, refer
to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405.
IHVU006I
CONNECT macro failed. I/O-OPS
RC=aa, CMS RC=bb.
Explanation: A request from a user in VM to establish
an IUCV communication path to I/O operations failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the CMS return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the CMS return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU007I
SEND macro failed. I/O-OPS RC=aa,
IUCV RC=bb.
The variable cc shows the I/O operations return
code.
The variable dd shows IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU009I
Command results unknown. I/O-OPS
RC=aa, IUCV IPAUDIT=bb.
Explanation: A request from I/O operations in VM to
return data to a user through IUCV communications
failed. The command was processed, but the results are
not available.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV IPAUDIT reply
(hexadecimal).
System programmer response: For an explanation of
the I/O operations return ocde, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the meaning of the
IPAUDIT field, refer to the IUCV section of z/VM CP
Programming Services (SC24-6084).
IHVU011I
System macro aa failed. I/O-OPS RC=bb
RSN=cc.
Explanation: A MVS system macro failed.
The variable aa shows the macro name.
Explanation: A request from a user in VM to send I/O
operations command data to I/O operations failed.
The variable bb shows the I/O operations return
code.
The variable aa shows the I/O operations return
code.
The variable cc shows the I/O operations reason
code.
The variable bb shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
User response: Try the command again. If the error
occurs again, contact your system programmer.
IHVU008I
RECEIVE failed. aa on bb I/O-OPS
RC=cc, IUCV RC=dd.
Explanation: A request from I/O operations in VM to
receive command data through IUCV communications
failed, and an attempt to send the failing return code
and reason code back to the user through a SEVER also
failed. This message is sent only to the system operator.
The variable aa shows the user ID.
The variable bb shows the system id.
System programmer response: For more information
about return codes and reason codes, refer to
Appendix A, “Return Codes, Status Codes, and Reason
Codes,” on page 405. For information about MVS
macros, refer to z/OS MVS Programming: Authorized
Assembler Services Reference (SA22-7609 through ,
SA22-7612).
User response: Contact your MVS system
programmer. Enter the DISPLAY RESULTS command at
the I/O operations operator console to determine the
status of the switch.
IHVU012I
TSO Service Facility failed. I/O-OPS
RC=aa RSN=bb.
Explanation: A request from I/O operations in MVS
to IKJEFTSR failed.
The variable aa shows the I/O operations return
code.
Chapter 9. Messages IHVA100I to IHVZ760
221
IHVU015I • IHVU023I
The variable bb shows the I/O operations reason
code.
The I/O operations return codes and reason codes are
defined as follows:
v When return code = 8 and reason code = 30B0 xxxx:
The TSO service routine returned a non-zero return
code, which is the last four characters of the I/O
operations reason code.
v When return code = 8 and reason code = 30B1 xxxx:
The TSO service routine abnormally ended. The
abend code is the last 4 characters of the I/O
operations reason code.
System programmer response: For more information
about return codes and reason codes, refer to
Appendix A, “Return Codes, Status Codes, and Reason
Codes,” on page 405. Refer to TSO Programming Facility
II Description/Operations. for an explanation of the TSO
return codes and abend codes.
User response: Contact your MVS system
programmer.
IHVU015I
Unrecoverable error. The I/O-OPS
program has terminated.
Explanation: User-to-I/O operations communication
cannot occur because the I/O operations program
stopped.
IHVU020I
IUCVINI SET macro failed. I/O-OPS
RC=aa, IUCVINI RC=bb.
Explanation: A request from I/O operations in VM to
identify itself as an IUCV program to the Group
Control System failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
IHVU021I
RECEIVE macro failed. I/O-OPS RC=aa,
IUCV RECEIVE RC=bb.
Explanation: A request from I/O operations in VM to
receive command data from a user through IUCV
failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV return code.
System programmer response: Report the problem to
your IBM Support Center.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU018I
IHVU022I
HNDIUCV CLR macro failed. I/O-OPS
RC=aa, CMS RC=bb.
Explanation: A request from I/O operations in VM to
remove itself from the IUCV environment failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU019I
aa on bb is processing an I/O-OPS
command.
Explanation: Another user is processing a I/O
operations command.
REPLY failed. aa on bb I/O-OPS RC=cc,
IUCV RC=dd.
Explanation: A request from I/O operations in VM to
reply to the command data through IUCV
communications failed. An attempt to send the failing
return code and reason code back to the user also
failed. This message is sent only to the system operator.
The variable aa shows the user ID.
The variable bb shows the system id.
The variable cc shows the I/O operations return
code.
The variable dd shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
The variable aa shows the user ID.
The variable bb shows the I/O operations VTAM
name.
User response: Contact the other user to determine
when command processing is done and the UNLOCK
command has been entered.
222
System Automation for z/OS Messages and Codes:
IHVU023I
REPLY macro failed. I/O-OPS RC=aa,
IUCV REPLY RC=bb.
Explanation: A request from I/O operations in VM to
reply or send back command data to the user through
IUCV failed.
IHVU024I • IHVV100I
The variable aa shows the I/O operations return
code.
The variable cc shows the I/O operations return
code.
The variable bb shows the IUCV return code.
The variable dd shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU024I
ACCEPT failed. aa on bb I/O-OPS
RC=cc, IUCVCOM RC=dd.
Explanation: A request from I/O operations in VM to
accept a connection request from the user failed. An
attempt to send the failing return code and reason code
back to the user also failed. This message is sent only
to the system operator.
The variable aa shows the user ID.
The variable bb shows the system id.
The variable cc shows the I/O operations return
code.
The variable dd shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
IHVU025I
ACCEPT macro failed. I/O-OPS RC=aa,
IUCVCOM RC=bb.
Explanation: A request from I/O operations in VM to
accept a connection request from a user through IUCV
failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
IHVU026I
SEVER failed. aa on bb I/O-OPS RC=cc,
IUCVCOM RC=dd.
Explanation: A request from I/O operations in VM to
sever an IUCV communication path failed. An attempt
to send the failing return code and reason code back to
the user also failed. This message is only sent to the
system operator.
The variable aa shows the user ID.
The variable bb shows the system id.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084).
IHVU027I
STORAGE OBTAIN failed.
Explanation: There was a STORAGE OBTAIN failure
in I/O operations while trying to access either subpool
230, 241, 245, or user private subpool 0.
System programmer response: Determine why there
was not enough storage and correct the condition.
Reenter the I/O operations command.
IHVU028I
GETMAIN failed. aa on bb RC=cc
RSN=dd.
Explanation: A request from I/O operations in VM to
get main storage failed. An attempt to send the failing
return code and reason code back to the user also
failed. This message is sent only to the system operator.
The variable aa shows the user ID.
The variable bb shows the system id.
The variable cc shows the return code.
The variable dd shows the reason code.
System programmer response: Determine why there
was not enough storage and correct the condition.
Reenter the command. For more information about
return codes and reason codes, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405.
IHVU029I
I/O-OPS is not operational.
Explanation: The command failed because I/O
operations is not running.
User response: Start I/O operations.
IHVU030I
Another user is busy processing an
I/O-OPS command
Explanation: Another user is processing an I/O
operations command.
User response: Enter your command again. If it fails,
either enter the GETLOCK command or wait for the
other user to enter the UNLOCK command.
IHVV100I
Device aa.
Explanation: The IEEVARY return code is 0. The
reason code is 0.
The variable aa is either 'ONLINE' or 'OFFLINE'.
Chapter 9. Messages IHVA100I to IHVZ760
223
IHVV110I • IHVV143I
User response: See MVS message IEE302I or IEF281I.
IHVV110I
Device already aa.
Explanation: The IEEVARY return code is 4. The
reason code is 0.
The variable aa is either 'ONLINE' or 'OFFLINE'.
IHVV136I
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 11.
User response: See MVS message IEE791I.
IHVV137I
User response: See MVS message IEE302I or IEE303I.
IHVV120I
Device pending offline.
Device assigned to another system.
Assign conflicts with current device
status.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 12.
Explanation: The IEEVARY return code is 8. The
reason code is 0.
User response: See MVS message IEE791I.
User response: See MVS message IEE794I.
IHVV138I
IHVV130I
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 13.
Device came online with restrictions.
Assign failed.
Explanation: The IEEVARY return code is 12. The
reason code is 0.
User response: See MVS message IEE791I.
User response: See MVS message IEE476I.
IHVV139I
IHVV131I
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 14.
Device has no UCB.
Device pending offline and boxed.
Explanation: The IEEVARY return code is xx. The
reason code is x.
User response: See MVS message IEE793I.
User response: See MVS message IEE313I.
IHVV140I
IHVV132I
Device has no aa paths.
Explanation: The IEEVARY return code is 12 or 16, the
reason code is 6 or 7. See explanation for MVS message
IEE025I.
The variable aa shows either LOGICAL or
PHYSICAL.
User response: None.
IHVV133I
Device in use by system function.
Device is managed by JES3.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 21.
User response: See MVS message IEF772I.
IHVV141I
Console device is currently changing
status.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 22.
User response: See MVS message IEE339I.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 8.
IHVV142I
User response: See MVS message IEE329I.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 23.
IHVV134I
Device vary processing aborted.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 9.
User response: See MVS message IEE328I.
IHVV135I
Dynamic pathing not operational on
device.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 10.
User response: See MVS message IEE791I.
224
System Automation for z/OS Messages and Codes:
Console device does not support action.
User response: See MVS message IEE313I.
IHVV143I
Vary of master console is rejected, force
is required.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 24.
User response: See MVS message IEE276I.
IHVV144I • IHVV210I
IHVV144I
Vary of master console is rejected, other
active consoles exist.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 25.
User response: See MVS message IEE276I.
IHVV154I
Device is in use by CUIR.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 18 (CUIR = control unit initiated
reconfiguration). I/O operations does not remove or
restore this device.
User response: See MVS message IEE529I.
IHVV145I
Vary of master console failed.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 26.
User response: See MVS message IEE370I.
IHVV146I
Vary of master console candidate is
rejected.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 27.
User response: See MVS message IEE367I.
IHVV147I
Device is a hardcopy console.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 28.
User response: See MVS message IEE229I.
IHVV155I
Device is not eligible for a vary
operation.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 19.
User response: See MVS message IEE313I.
IHVV156I
Volume could not be read.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 20.
User response: See MVS message IEF502I, IEF503I, or
IEF510I.
IHVV160I
Device is offline and pending boxed.
Explanation: The IEEVARY return code is 20.
User response: See MVS message IEE845I.
IHVV150I
Device did not come aa.
Explanation: The IEEVARY return code is 16. The
reason code is 0.
The variable aa is either 'ONLINE' or 'OFFLINE'.
IHVV170I
Device is pending offline and pending
boxed.
Explanation: The IEEVARY return code is 24.
User response: See MVS message IEE845I or IEE846I.
User response: See MVS message IEE846I.
IHVV151I
IHVV180I
Device kept offline by a configuration
manager.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 15.
Unexpected error occured.
Explanation: The IEEVARY return code is 32.
User response: See MVS message IEE424I.
User response: An unexpected error occurred in MVS
while processing the IEEVARY request. Follow your
local procedures for reporting MVS errors.
IHVV152I
IHVV200I
Device is offline due to operator.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 16.
User response: See MVS message IEE113I.
IHVV153I
Device is in a system-managed tape
library.
Explanation: The IEEVARY return code is 12 or 16.
The reason code is 17.
User response: See MVS message IEE108I.
AUTOSWITCH for device aa (now bb).
Explanation: The AUTOSWITCH attribute for the
device was successfully changed.
The variable aa shows either REMOVED or
RESTORED.
The variable bb shows either OFF or ON.
User response: None.
IHVV210I
AUTOSWITCH for device already aa
(was bb).
Explanation: Device is already in requested
AUTOSWITCH mode.
The variable aa shows either REMOVED or
RESTORED.
Chapter 9. Messages IHVA100I to IHVZ760
225
IHVV230I • IHVZ210I
The variable bb shows either OFF or ON.
User response: None.
IHVV230I
Coupling Facility is not available.
Explanation: Shared tape support relies on data
sharing across the sysplex through a coupling facility.
User response: None.
problem with the IODF. Check the system log for
related HCD messages.
For other system services, refer to the description of the
system services in z/OS MVS Programming: Authorized
Assembler Services Reference (SA22-7609 through
SA22-7612), or to z/OS MVS Programming: Sysplex
Services Reference (SA22-7618) for further information on
the return code and the reason code.
Stop and start I/O operations.
IHVV236I
Device type not valid for use of
AUTOSWITCH.
Explanation: The device specified for the
AUTOSWITCH option was of an invalid type.
If this does not solve the problem, report it to your
IBM Support Center including the return code bb, the
reason code cc, and the module name dd.
User response: Contact your system programmer.
User response: None.
IHVX002I
IHVV240I
Device is not offline.
Explanation: The unit must be OFFLINE before its
AUTOSWITCH attribute can be changed.
User response: Vary the device offline.
IHVV300I
LINK failed.
Explanation: There has been a link failure. Required
module IEEVPTHI in SYS1.LINKLIB cannot be found.
System programmer response: Verify that the
required operating system and all required PTFs have
been installed.
IHVX000E
System error detected, RC=aa RSN=bb.
Explanation: I/O operations has detected damage to
storage or code and reports the return code and reason
code, which are listed in Appendix A, “Return Codes,
Status Codes, and Reason Codes,” on page 405.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Stop and start I/O operations to
recover from the error, and report the problem to your
IBM Support Center.
IHVX001I
System service aa failed, RC=bb RSN=cc
Mod=dd.
Explanation: The indicated system service called by
I/O operations failed. I/O operations storage or code
may be corrupted.
VARY SWITCH failed in module aa.
Explanation: I/O operations issued the VARY
SWITCH system service. This message occurs when the
VARY SWITCH service does not get the required
amount of storage (STORAGE OBTAIN failed).
The variable aa shows the name of the module
where the error occurred.
System programmer response: Determine why there
was not enough storage and correct the condition.
User response: Restart I/O operations if the hardware
configuration was changed. If this does not solve the
problem, report the problem to your IBM Support
Center including the module name aa.
IHVZ100I
Unrecognized parameter, RC=aa
RSN=bb.
Explanation: An incorrect parameter was found.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center.
IHVZ200I
I/O-OPS database update started.
Explanation: The I/O operations database is being
updated due to hardware reconfiguration changes.
User response: None.
IHVZ210I
I/O-OPS database update complete.
The variable aa shows the service that failed.
Explanation: The I/O operations database has been
updated due to hardware reconfiguration changes.
The variable bb shows the return code.
User response: None.
The variable cc shows the reason code.
The variable dd shows the name of the module.
System programmer response: If the system service is
either HCDSETUP or HCD OPEN, there might be a
226
System Automation for z/OS Messages and Codes:
IHVZ300I • IHVZ701I
IHVZ300I
O/S communication established.
Explanation: All required operating system
communication has been started for hardware
reconfiguration changes.
User response: None.
IHVZ400I
Communication error, RC=aa RSN=bb.
Explanation: An operating system communication
error has occurred. Restart I/O operations if any
hardware reconfiguration changes are made. If
communication is established, message IHVZ300I is
issued.
IHVZ620I
ESTAE module delete error, RC=aa
RSN=bb.
Explanation: I/O operations encountered an error
when attempting to delete IHVSTAS from virtual
storage.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center. For more information about return
codes and reason codes, refer to Appendix A, “Return
Codes, Status Codes, and Reason Codes,” on page 405.
The variable aa shows the return code.
IHVZ700I
The variable bb shows the reason code.
Explanation: A request from I/O operations in VM to
identify itself as an IUCV program to the Group
Control System failed. I/O operations cannot
automatically process hardware reconfiguration
changes.
User response: Restart I/O operations if any hardware
reconfiguration changes are made. For more
information about return codes and reason codes, refer
to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405.
IHVZ510I
O/S communication error, RC=aa
RSN=bb.
Explanation: An operating system communication
error has occurred.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center. For more information about return
codes and reason codes, refer to Appendix A, “Return
Codes, Status Codes, and Reason Codes,” on page 405.
IHVZ600I
ESTAE macro load error, RC=aa RSN=bb.
Explanation: I/O operations encountered an error
loading the ESTAE macro.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center. For more information about return
codes and reason codes, refer to Appendix A, “Return
Codes, Status Codes, and Reason Codes,” on page 405.
IHVZ610I
ESTAE macro end error, RC=aa RSN=bb.
Explanation: I/O operations encountered an error
when ESTAE 0 was issued.
The variable aa shows the return code.
The variable bb shows the reason code.
User response: Report the problem to your IBM
Support Center. For more information about return
codes and reason codes, refer to Appendix A, “Return
Codes, Status Codes, and Reason Codes,” on page 405.
I/O-OPS RC=aa, IUCVINI SET RC=bb.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCVINI SET return
code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
User response: Restart I/O operations if any hardware
reconfiguration changes are made.
IHVZ701I
I/O-OPS RC=aa, IUCVCOM CONNECT
RC=bb.
Explanation: A request from I/O operations in VM to
establish communication with the *CONFIG CP system
service failed. I/O operations cannot automatically
process hardware reconfiguration changes.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCVCOM CONNECT
return code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
User response: Restart I/O operations if any hardware
reconfiguration changes are made.
Chapter 9. Messages IHVA100I to IHVZ760
227
IHVZ710I • IHVZ760I
IHVZ710I
I/O-OPS RC=aa, IUCVINI CLR RC=bb.
Explanation: A request from I/O operations to the
Group Control System in VM to remove itself from the
IUCV environment failed.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCVCOM CLR return
code.
IHVZ740I
I/O-OPS RC=aa, IUCV RECEIVE CC=bb.
Explanation: A request from I/O operations in VM to
receive a reconfiguration record from the operating
system failed. I/O operations cannot automatically
process hardware reconfiguration changes.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV RECEIVE return
code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV condition
code, refer to z/VM CP Programming Services
(SC24-6084).
IHVZ720I
User response: Restart I/O operations if any hardware
reconfiguration changes are made.
I/O-OPS RC=aa RSN=bb.
Explanation: A connection between I/O operations
and the *CONFIG CP system service has failed. Restart
I/O operations if any hardware reconfiguration
changes are made. Any subsequent I/O operations
command attempts to reestablish the connection. If the
attempt is successful, message IHVZ300I is sent.
The variable aa shows the return code.
IHVZ750I
Unable to process hardware change.
Explanation: An unrecoverable error occurred when
I/O operations tried to process hardware
reconfiguration changes.
User response: Stop and restart I/O operations.
The variable bb shows the reason code.
User response: Restart I/O operations if any hardware
reconfiguration changes are made. For more
information about return codes and reason codes, refer
to Appendix A, “Return Codes, Status Codes, and
Reason Codes,” on page 405.
IHVZ730I
I/O-OPS RC=aa, IUCV RECEIVE RC=bb.
Explanation: A request from I/O operations in VM to
receive a reconfiguration record from the operating
system failed. I/O operations cannot automatically
process hardware reconfiguration changes.
The variable aa shows the I/O operations return
code.
The variable bb shows the IUCV RECEIVE return
code.
System programmer response: For an explanation of
the I/O operations return code, refer to Appendix A,
“Return Codes, Status Codes, and Reason Codes,” on
page 405. For an explanation of the IUCV return code,
refer to z/VM CP Programming Services (SC24-6084). For
information about the Group Control System, refer to
z/VM Group Control System (SC24-6098).
User response: Restart I/O operations if any hardware
reconfiguration changes are made.
228
System Automation for z/OS Messages and Codes:
IHVZ760I
ETR status changed.
Explanation: MVS has reported a change in status for
the Sysplex Timer, or a port or link connected to a
Sysplex Timer.
User response: Review the ETR configuration for the
system issuing the message. This can be done via the
MVS DISPLAY ETR command.
Chapter 10. Messages ING001I to INGY1337I
Note that within NetView an additional * may be appended to the end of the
message text.
Note: Because these INGXnnnnt messages are written to the syslog, the message
text must be in English.
ING001I
aaaa SERVICE FAILED, RC=bb,
REASON=cccccccc
Explanation: SA z/OS detected an error.
The variable aaaa shows the service/command that
failed.
The variable bb shows the value of the return code.
The variable ccccccccc shows the value of the reason
code.
System programmer response: None.
User response: If an INGOMX error occurred, refer to
IBM Tivoli System Automation for z/OS Programmer's
Reference.
For a NetView command error, refer to the appropriate
NetView manual.
In all other cases, contact your IBM Support Center.
ING002I
name IS NOT A SECONDARY
AUTOMATION MANAGER
Explanation: The specified command or action is only
applicable for a secondary automation manager.
The variable name shows the name of the
automation manager that is not defined as
secondary automation manager.
System action: Processing terminates.
Operator response: Specify the correct automation
manager name and reissue the command.
ING003I
name IS NOT A PRIMARY
AUTOMATION MANAGER
Explanation: The specified command or action is only
applicable for the primary automation manager.
The variable name shows that name of the
automation manager that is not defined as primary
automation manager.
System action: Processing terminates.
Operator response: Specify the correct automation
manager name and reissue the command.
ING004I
REQUEST request SUBMITTED
© Copyright IBM Corp. 1996, 2014
|
|
|
Explanation: The request to update the operation
mode of the designated automation manager has been
submitted under this task or another work operator.
The variable request shows the submitted request.
System action: Processing continues.
ING005I
RESOURCE name IS AMBIGUOUS
Explanation: There is more than one resource with the
specified name within the domain of the automation
manager in charge. Because the command is running in
line mode, SA z/OS is unable to determine which of
the resources the command should be applied to.
The variable name shows the name of the resource
that is not unique.
System action: Processing terminates.
Operator response: Specify the fully qualified resource
name and reissue the command.
ING006I
THERE IS NO RESOURCE name
Explanation: None of the resources defined in the
sysplex matches the specified name pattern.
The variable name shows the name of the resource
that could not be found.
System action: None.
Operator response: Correct the name of the resource
and reissue the command.
System programmer response: None.
ING007I
name IS NOT AN APPLICATION
GROUP
Explanation: The display "group members" action was
requested for a resource that is not an application
group.
The variable name shows the name of the resource
that is not an application group.
System action: None.
Operator response: None.
ING008I
name SERVICE FAILED, RC=return_code,
REASON=reason.
229
ING009I • ING014I
Explanation: A service routine was called that ended
with a non-zero return code.
|
|
|
The variable name shows the name of the function
that encountered the error. For function INGSTX,
refer to the help of command INGSTX.
The variable return_code shows the return code that
the failing service routine returned.
The variable reason shows descriptive text about the
cause of the error.
System action: Processing terminates.
ING010I
Explanation:
The variable warning/error information shows
descriptive text from the automation manager about
the cause of the error.
System action: None.
Operator response: None.
ING011I
Operator response: Notify your system programmer.
| System programmer response:
| Determine why the service routine failed and correct
| the problem. Examine the netlog for additional
| information.
|
|
|
|
For REASON=TIMEOUT, refer to the topic 'Work Item
Statistics' and 'Workitem Queue Monitoring' in the
"Problem Determination" appendix of IBM Tivoli System
Automation for z/OS User's Guide.
|
|
|
|
|
|
|
|
|
|
|
The information provided can help you to understand
better the automation manager's workload and
performance. TIMEOUT means that the Agent stopped
waiting for a command response from the automation
manager. The wait time is controlled by the WAIT
parameter which is available for most commands,
(INGLIST, INGREQ, WAIT= nnn | NO). The default
wait time is 30 seconds but can be adjusted (also refer
to the section 'Parameter Defaults for Commands' in
IBM Tivoli System Automation for z/OS Customizing and
Programming).
|
|
|
|
|
In addition, the command INGRPT provides
information about the automation manager's
performance from a statistical point of view, like the
total number of TimeOuts, average wait time,
maximum wait time.
| If necessary, contact your IBM Support Center for
| further assistance.
warning/error information
CONFLICT DETECTED BETWEEN UP
AND DOWN TIMESLOTS
Explanation: There is an overlap between an UP time
slot and a DOWN time slot.
System action: None.
Operator response: Correct the time specification.
ING012I
name IS NOT AN AUTOMATION
MANAGER
Explanation: The specified command or action is only
valid for an automation manager.
The variable name shows the name of the system
where the command could not be processed.
System action: Processing is terminated.
Operator response: Specify the correct automation
manager name and reissue the command.
ING013I
PARAMETER parameter_name IS NOT
APPLICABLE FOR RESOURCES OF
TYPE type
Explanation: The specified parameter is not valid for
resources of the specified type.
The variable parameter_name shows the name of the
parameter that is not valid.
The variable type shows the type of the resource.
System action: Processing terminates.
ING009I
UPDATE OF parameter COMPLETED;
SET TO value
Explanation: The requested function has been
successfully completed.
The variable parameter shows the name of the
parameter that was updated.
The variable value shows the new value of the
parameter.
System action: None.
Operator response: None.
230
System Automation for z/OS Messages and Codes:
Operator response: Correct the format and reissue the
command.
ING014I
CONFLICTING PARAMETERS
SPECIFIED.
Explanation: Self-explanatory.
System action: Processing terminates.
Operator response: Correct the format and reissue the
command.
ING015I • ING023I
ING015I
NO MATCHING REQUEST FOUND
FOR resource - SOURCE=source
REQUEST=request
Explanation: An INGSET CANCEL was issued but the
request identified by its type and source does not exist.
The variable resource shows the name of the
resource.
The variable source shows the name of the source.
The variable request shows the name of the request
that could not be found.
ING019I
REQUESTED ACTION IGNORED FOR
RESOURCE resource
Explanation: An INGGROUP ACTION EXCLUDE,
AVOID, DEFAULT, or INCLUDE was requested for a
group of nature basic.
The variable resource shows the name of the
resource.
System action: Processing terminates.
Operator response: Correct the command syntax and
reissue the command.
System action: Processing terminates.
Operator response: Correct the format and reissue the
command.
ING016I
SCOPE=scope IS NOT VALID FOR type
REQUEST
Explanation: The specified scope is not valid for the
type of request.
The variable scope shows the scope that was
specified for the request.
The variable type shows the type of the request.
ING020I
DATASET datasetname NOT FOUND OR
NOT ACCESSIBLE
Explanation: Either the specified data set does not
exist, or it is not accessible, or, if it is a configuration
data set it is not a PDS.
The variable datasetname shows the name of the data
set that is not available.
System action: None.
Operator response: Correct the name of the data set
and reissue the command.
System action: Processing terminates.
Operator response: Correct the format and reissue the
command.
ING017I
EXPIRATION TIME timestamp HAS
PASSED ON system
Explanation: The specified expiration date or time is
in the past.
The variable timestamp shows the specified
timestamp.
The variable system shows the name of the system.
System action: Processing terminates.
Operator response: Specify an expiration time or date
that is in the future and reissue the command.
ING018I
ONLY ONE GROUP ALLOWED FOR
ACTION action
Explanation: You specified more than one group name
for an INGGROUP action of ADJUST or MEMBERS.
The variable action shows the action that could not
be performed.
System action: Processing terminates.
Operator response: Specify only one group name and
reissue the command.
ING021I
STATISTICS COUNTERS RESET ON
SYSTEM sysname
Explanation: The statistics counts have been reset on
the specified system.
The variable sysname shows the name of the system
whose statistics counts were reset.
System action: Processing continues.
Operator response: None.
Module: INGRVRPX
ING022I
THRESHOLD SETTINGS FOR resource
CANNOT BE DELETED
Explanation: The threshold settings for DEFAULTS,
MVSESA and SUBSYSTEM cannot be deleted.
The variable resource shows the name of the
resource that the threshold settings cannot be
deleted for.
System action: None.
Operator response: None.
Module: INGRYTH0
ING023I
command COMMAND NOT ALLOWED
TO RUN UNDER task TASK.
Explanation: The specified command cannot run
under the specified task.
The variable command shows the name of the
command that cannot be run.
Chapter 10. Messages ING001I to INGY1337I
231
ING024I • ING029I
The variable task shows the name of the task that
the command cannot be run under.
ING027I
System action: Processing stops.
Operator response: Reissue the command under
another task.
Module: INGRYRPX
ING024I
DELETION OF INTERNAL REQUEST
IS NOT ALLOWED.
Explanation: The selected request is created by the
automation manager due to:
1. Vote propagation for an application group. This
request cannot be canceled. It will be automatically
removed when the vote that initiated the request is
removed.
2. A service period UP or DOWN window. This
request cannot be canceled. It will be automatically
removed when the UP or DOWN window ends.
System action: None.
Explanation: Another system, identified by its domain
ID, has sent a slave routine to communicate with the
local system via the "remote procedure call" technique
rather than NNT sessions.
The variable clistname is the name of the slave
routine.
The variable domain is the domain ID of the remote
system.
The variable product is the SA z/OS release level
running on the remote system.
The variable clist_level shows the last APAR number
and compile data of the slave routine.
System action: None.
Operator response: None.
ING028I
Operator response: None.
ING025I
OUTBOUND CONNECTION WITH
DOMAIN domain RUNNING product
ESTABLISHED.
Explanation: The local system has established a
communication path with the named system.
The variable domain identifies the remote system. It
is the domain ID of the remote system.
The variable product is the SA z/OS release running
on the remote system.
SLAVE ROUTINE clistname RECEIVED
FROM DOMAIN domain RUNNING
product LEVEL clist_level.
command: PARAMETER parameter
MISSING OR INVALID value
Explanation: The specified parameter is either wrong
or missing.
The variable command is the name of the command
being processed.
The variable parameter is the parameter that is
invalid or missing.
The variable value is the value of the parameter that
is wrong.
System action: None.
Operator response: None.
System action: None.
Operator response: None.
ING026I
ROUTINE clistname SENT TO DOMAIN
domain LEVEL clist_level.
Explanation: The local system has sent the current
version of the INGRVXMT slave routine to the remote
system. This enables the local system to communicate
with the remote system via the "remote procedure call"
technique rather than NNT sessions.
The variable clistname is the name of the slave
routine.
The variable domain identifies the remote system by
its domain ID.
The variable clist_level shows the last APAR number,
if present, and compile date.
System action: None.
Operator response: None.
232
System Automation for z/OS Messages and Codes:
ING029I
SLAVE ROUTINE clistname IS
COMPILED. CANNOT BE SENT TO
DOMAIN domain
Explanation: Because the clist that is named in the
message is compiled, it cannot be sent to the remote
system. This is done for two reasons:
1. The REXX runtime library might not be installed on
the remote system.
2. The compiled REXX routine does not contain any
indication of its software level (release number, last
APAR).
The variable clistname is the name of the slave
routine.
The variable domain identifies the remote system by
its domain ID.
System action: None.
Operator response: None.
ING030I • ING036I
ING030I
Group group_name cannot be moved to
another system - reason
Explanation: An attempt was made to move the
group away from the system that it currently runs on,
but no other system is available.
The variable group_name is the move group
concerned.
The variable reason explains in more detail why the
group cannot be moved.
System action: None.
Operator response: None.
System action: Processing continues.
Operator response: None.
Classes: None.
ING034I
STATUS stat OF SUBSYSTEM subsys IS
NOT VALID FOR FUNCTION function
Explanation: AOFRYSAB was called to perform a
function for a subsystem. The status of the subsystem
does not allow this function.
The variable stat is the current status of the
subsystem.
System programmer response: None.
The variable subsys is the subsystem that the
function is to be performed on.
ING031I
The variable func is the function that is to be
performed
EVENT SUBSCRIPTION CONSUMER
name IS UNKNOWN.
Explanation: The consumer specified in the
INGEVOBS call is not defined, which means that the
consumer is not registered.
The variable name is the name of the consumer as
specified in the INGEVOBS command.
System action: The function is not performed.
Operator response: None.
Classes: None.
ING035I
System action: The command is rejected.
Operator response: Reenter the correct command, if
applicable or register the consumer first.
Classes: None.
ING032I
AVAILABILITY TARGET avtgt
CANNOT BE LESS THAN THE
SATISFACTORY TARGET sattgt
Explanation: You have specified either a satisfactory
target value that is larger than the availability target, or
an availability target that is less than the satisfactory
target assigned to the server group.
system_name IS NOT A VALID SYSTEM
FOR GROUP group_name
Explanation: The specified system name is either
unknown or not a valid choice for the group.
The variable system_name is the invalid system
name.
The variable group_name is the move group
concerned.
System action: None.
Operator response: Specify a valid system that the
group can be moved to.
Module: INGRYMV0
The variable avtgt is the availability target assigned
to the group.
Classes: None.
The variable sattgt is the satisfactory target assigned
to the group.
ING036I
System action: The command is rejected.
GROUP group_name CANNOT BE
MOVED TO SYSTEM system_name reason
Classes: None.
Explanation: You attempted to move the group to the
specified system either now or at the next recycle, but
one of the following conditions is true:
ING033I
v The system is down or System Automation is not
fully initialized.
Operator response: Reenter the correct command.
INBOUND SESSION STATUS
CORRECTED FOR domain. SET status
Explanation: The gateway monitoring routine found
an inbound session status that does not match the
actual status. The session status is corrected.
v The member on that system is not startable.
v The group is already running on that system.
System action: None.
The variable domain is the name of the domain that
the local system has an inbound session with.
Operator response: Specify another system that the
group should be moved to.
The variable status is the new inbound session
status.
Module: INGRYMV0
Classes: None.
Chapter 10. Messages ING001I to INGY1337I
233
ING037I • ING044I
ING037I
GROUP group_name CANNOT BE
BOXED - NOT ACTIVE
Explanation: You attempted to box the group but the
application group is not active.
System action: None.
Operator response: None.
Module: INGRYMV0
The variable keywords shows a list of possible
parameters to be specified.
System action: The command is rejected.
Operator response: Enter the command again and
specify one of the suggested parameters.
Classes: None.
ING042I
Classes: None.
ING038I
CONFLICTING PARAMETERS OR
VALUES SPECIFIED => p1 - p2
Explanation: The specified parameters (or their
values) conflict.
The variable p1 is the first invalid parameter.
The variable p2 is the second invalid parameter.
System action: None.
Operator response: Reenter the command with valid
parameters.
keyword1 MUST BE SPECIFIED WITH
keyword2
Explanation: A command was entered but one of its
parameters requires another one to be also specified.
The variable keyword1 shows the parameter that
requires keyword2 to be specified.
The variable keyword2 shows the additional
parameter that is required.
System action: The command is rejected.
Operator response: Enter the command again and
specify the missing parameter.
Classes: None.
Module: INGRYST0
Classes: None.
ING039I
SESSION name IS UNKNOWN
Explanation: The specified session is not defined in
the configuration file (ACF).
The variable name is the session name.
System action: None.
Operator response: Reenter the command with a valid
session name.
ING043I
keyword1 MUST NOT BE SPECIFIED
WITH keyword2
Explanation: A command was entered but one of its
parameters disallows another one to be also specified.
The variable keyword1 shows the parameter that
excludes the use of keyword2.
The variable keyword2 shows the parameter that is
excluded by the use of keyword1.
System action: The command is rejected.
Module: INGRVSS0
Operator response: Enter the command again and
specify either keyword1 or keyword2.
Classes: None.
Classes: None.
ING040I
ING044I
THE FOLLOWING IS MISSING:
keywords
Explanation: A command was entered but one or
more required parameters were not specified.
The variable keywords shows a list of all the missing
parameters.
System action: The command is rejected.
Operator response: Enter the command again and
specify the required parameters.
Classes: None.
ING041I
ONE OF THE FOLLOWING IS
MISSING: keywords
Explanation: A command was entered but a required
parameter was not specified.
234
System Automation for z/OS Messages and Codes:
keyword1 MUST BE GREATER THAN
OR EQUAL TO keyword2
Explanation: A command was entered with two
parameters. The two values define a range. The second
value must be greater than or equal to the first value.
The variable keyword1 shows the parameter that
defines the end of the range.
The variable keyword2 shows the parameter that
defines the start of the range.
System action: The command is rejected.
Operator response: Enter the command again and
specify a value for keyword1 that is greater than or
equal to the value given for keyword2.
Classes: None.
ING045I • ING052I
ING045I
keyword MUST BE IN THE FORMAT
format
Explanation: A command was entered with a
parameter that requires a certain data format.
v The variable keyword shows the parameter that
requires the format.
v The variable format shows the format that is required
as one of the following, or any other self-explanatory
text:
MM/DD/YYYY
A valid date in the form month/day/year
HH:MM
A valid time in the form hour:minute
Cn
1–n characters
Dn
1–n numeric digits
Note that there might be additional lines that explain
the problem in further detail.
System action: The command is rejected.
Operator response: Enter the command again and
specify a value that conforms to the required format.
Classes: None.
ING046I
keyword MUST BE ONE OF THE
FOLLOWING: list
Explanation: A command was entered with a
parameter that requires a certain value.
The variable keyword shows the parameter that
requires the value.
The variable list shows a list of valid values that the
parameter can take.
System action: The command is rejected.
Operator response: Enter the command again and
specify a value from the list.
Classes: None.
ING048I
subsystem NOT DEFINED AS type
SUBSYSTEM
Explanation: The specified subsystem is not of the
required type.
The variable subsystem identifies the subsystem.
The variable type defines the type (CICS, IMS, etc.).
System action: None.
Operator response: Specify a valid subsystem of the
required type.
Classes: None.
ING049I
No xxxx data to display for subsystem
Explanation: There are no commands specified in the
policy for the specified subsystem.
The variable xxxx identifies the keyword that no
commands have been defined for. It can be
DISPINFO, IMSINFO, or CICSINFO.
The variable subsystem identifies the subsystem.
System action: None.
Operator response: None.
Classes: None.
ING050I
HBEAT BEAT parameter
Explanation: A heartbeat was issued.
The variable parameter shows the parameters that
were specified with the heartbeat.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING051I
HBEAT RECV parameter
Explanation: A heartbeat was received.
ING047I
keyword MUST BE IN THE RANGE
FROM from TO to
Explanation: A command was entered with a
parameter that must be in a certain range.
The variable keyword shows the name of the
parameter that must be in the range.
The variable from shows the lowest possible value.
The variable to shows the highest possible value.
The variable parameter shows the parameters that
were specified.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING052I
HBEAT FAIL parameter
Operator response: Enter the command again and
specify a value in the given range.
Explanation: A heartbeat with the specified
parameters failed.
The variable parameter shows the parameters of the
failed heartbeat.
Classes: None.
System action: Processing continues.
System action: The command is rejected.
Operator response: None.
System programmer response: None.
Chapter 10. Messages ING001I to INGY1337I
235
ING053I • ING060I
ING053I
HBEAT SDWN parameter
Explanation: A heartbeat with the specified
parameters is shut down.
The variable parameter shows the parameters of the
shutdown heartbeat.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING054I
MAJOR RESOURCE object name
CANNOT BE FOUND
Explanation: An invalid major resource was specified
for the creation of a minor resource.
The variable object name shows the name of the
resource that could not be found.
System action: Processing continues unless no
replacement anchor can be found.
Operator response: Inform your system programmer.
System programmer response: If the originator is a
customized INGPOST call, correct the call. If not,
contact your IBM Support Center.
ING055I
INVALID 'STATE=state' CONVERTED
TO 'STATE=ALERT'
Explanation: An invalid state was specified in the
INGPOST call. The state is converted to 'ALERT'.
The variable state shows the incorrect state that was
converted to 'ALERT'.
ING058I
module function UNEXPECTED
RESPONSE FROM service function :
return code
Explanation: The service called for the specified
function returned an unexpected return code.
The variable module shows the name of the module
where the error occurred.
The variable function shows the name of function
that called the service.
The variable service shows the service that was
called.
The variable function shows the function of the
service that was called.
The variable return code shows the value of the
return code that was issued.
System action: The command is canceled.
Operator response: Inform your system programmer.
System programmer response: Contact your IBM
Support Center.
ING059I
USERSTATUS FOR OBJECT object
UPDATED TO status value (status name)
Explanation: The status of the object has been set to
the referred value.
The variable object shows the object whose status
was updated.
The variable status value shows the status value of
the object.
The variable status name shows the status name of
the object.
System action: Processing continues.
System action: Processing continues.
Operator response: Inform your system programmer.
Operator response: None.
System programmer response: If the originator is a
customized INGPOST call, correct the call. If not,
contact your IBM Support Center.
System programmer response: None.
ING057I
command FAILED, GENALERT TEXT
PARAMETER LONGER THAN 244
CHARS
Explanation: The resulting GENALERT parameter
string exceeds the maximum length for GENALERTs.
The variable command shows the command that
could not be executed.
System action: The command is canceled.
Operator response: Inform your system programmer.
System programmer response: Contact your IBM
Support Center.
236
System Automation for z/OS Messages and Codes:
ING060I
USERDATA FOR OBJECT object
UPDATED: value
Explanation: The user data of the object has been
updated to the specified value.
The variable object shows the object whose status
was updated.
The variable value shows the new status of the
object.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING061I • ING069E
ING061I
INGPOST command NOT ALLOWED
FOR OBJECT object
Explanation: The specified INPOST command is not
allowed for the object.
The variable command shows the name of the
INGPOST command that is not allowed for the
object.
The variable object shows the name of the resource
that the command is not valid for.
System action: The command is canceled.
ING065I
INVOKED FROM NMC BY USER: user
ID
Explanation: The command was invoked by a user.
The variable user ID shows the user ID that the
command was invoked from.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Operator response: Inform your system programmer.
ING066I
System programmer response: If the originator is a
customized INGPOST call, correct the call. If not,
contact your IBM Support Center.
Explanation: The command could not be executed.
ING062I
command mode PROCESSING STARTED
Explanation: The command with the specified mode
has started.
The variable command shows the name of the
command that processing started for.
The variable mode shows the mode of the command.
COMMAND NOT ISSUED: reason
The variable reason shows the reason why the
command could not be executed.
System action: The command is canceled.
Operator response: Make sure the specified command
was valid within the context. If it was valid, inform
your system programmer.
System programmer response: Investigate the cause
of the failure and take the appropriate steps.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING063I
command mode PROCESSING
COMPLETED RC return code
Explanation: The command with the specified mode
completed.
The variable command shows the name of the
command that processing completed for.
The variable mode shows the mode of the command.
The variable return code shows the value of the
return code that was issued. A non-zero return code
indicates that the command was in error.
System action: Processing continues.
Operator response: In case of a non-zero return code
inform your system programmer.
System programmer response: In case of a non-zero
return code investigate for proceeding.
ING064I
ISSUING: command
Explanation: The command is issued by the command
router.
The variable command shows the name of the
command that is being issued.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING067I
REQUEST REJECTED; INGTOPO NOT
INITIALIZED
Explanation: The request was rejected because
INGTOPO was not initialized.
System action: The command is canceled.
Operator response: Start INGTOPO with "init" and
the appropriate NetView operator ID as parameter.
System programmer response: None.
ING068I
CHANGES WILL BE LOST - PRESS
function_key TO ACTIVATE
Explanation: At least one group policy attribute has
been modified but not yet committed.
The variable function_key is the function key that
activates the group policy change.
System action: None.
Operator response: Press the appropriate function key
to commit the changes.
System programmer response: None.
ING069E
ERROR LOADING topo file - reason
Explanation: The interpretation of the topo file could
not be processed successfully.
The variable topo file shows the name of the topo file
that could not be loaded.
The variable reason shows the reason why the topo
file could not be loaded.
Chapter 10. Messages ING001I to INGY1337I
237
ING070E • ING082I
System action: Processing stops.
Operator response: Inform your system programmer.
Operator response: Inform your system programmer.
System programmer response: Start Tivoli NetView
MultiSystem Manager (MSM). The MSM is a
prerequisite for the SA z/OS Topology Manager.
System programmer response: Check the topo file for
the specified failure.
ING070E
UNEXPECTED RESPONSE FROM
system RC return code
Explanation: The processing of a remote command on
the specified system returned an unexpected return
code.
The variable system shows the name of the system
the returned the return code.
ING080I
Monitor_name Session_name Logon_type
Exception_text
Explanation: ING080I is issued on behalf of a monitor
resource that uses the monitor command INGMTRAP
to define a trap for one or more OMEGAMON®
exceptions. It is issued for each exception that trips.
System action: Processing continues, unless it was the
last target system in the sysplex to make contact with.
Monitor_name is the fully qualified monitor resource
name in the format monitor_name/MTR/
system_name, which indicates the monitor resource
that this exception message was issued for. Note
that monitor_name is known to INGMTRAP through
the task global &SUBSAPPL.
Operator response: Check the final message ING063I
and act according to its state.
Session_name is the name of the OMEGAMON
session as it was specified by the NAME keyword
on the INGMTRAP command.
The variable return code shows the value of the
return code.
System programmer response: None.
ING071I
command mode SUBMITTED
Explanation: The command with the specified mode
was submitted to the Topology Manager NetView
operator ID.
The variable command shows the name of the
submitted command.
The variable mode shows the mode of the submitted
command.
System action: Processing continues.
Operator response: None.
System programmer response: None.
ING072E
INITIAL COMMUNICATION WITH
system FAILED
Explanation: The attempt to communicate with the
specified system was unsuccessful.
The variable system shows the name of the system.
System action: Processing continues.
Operator response: Inform your system programmer.
System programmer response: Investigate the cause
of the failure and take the appropriate steps.
Logon_type is the type attribute used by the
OMEGAMON session named Session_name as
defined in the automation policy.
Exception_text is the exception text as returned by
OMEGAMON without the leading ‘+’ sign.
ING081I
Explanation: Message ING081I is never issued to an
operator console, but is written to a monitor resource’s
history. This happens when the monitor resource uses
the monitor command INGMTRAP to define a trap for
one or more OMEGAMON exceptions and no
exception has tripped.
Monitor_name is the fully qualified monitor name in
the format monitor_name/MTR/system_name, which
indicates the monitor resource that this exception
message was issued for. Note that monitor_name is
known to INGMTRAP through the task global
&SUBSAPPL.
Session_name is the name of the OMEGAMON
session as it was specified by the NAME keyword
on the INGMTRAP command.
Logon_type is the type attribute used by the
OMEGAMON session named Session_name as
defined in the automation policy.
ING082I
ING073E
"INIT" FAILED: MSM HAS NOT BEEN
STARTED YET
Explanation: The Tivoli NetView MultiSystem
Manager (MSM) has not been started yet.
System action: Initialization of SA z/OS Topology
Manager canceled.
238
System Automation for z/OS Messages and Codes:
Monitor_name Session_name Logon_type
NO EXCEPTION FOUND
NO SESSION OPERATORS HAVE
BEEN DEFINED – OMEGAMON
SESSION INITIALIZATION
TERMINATED.
Explanation: The installation failed to define session
operator entries in the automation policy.
System action: Automation initialization continues.
ING083I • ING085I
Operator response: Notify your system programmer.
this session is not an OMEGAMON session.
Validate and, if necessary, correct your session
definitions in the customization dialog.
System programmer response: Make sure you have
defined at least one session operator AOFSESxx in the
automation policy and assigned it to an automation
operator, for example, AUTSESxx.
ING083I
COMMAND command ISSUED BY
operator IN SESSION session_name.
Explanation: Message ING083 is issued each time a
list of one or more commands is sent to the
OMEGAMON session that is denoted by session_name.
command is the first command in the list of
commands that was issued with the INGOMX API.
operator is the operator or automation operator that
issued the command.
session_name is the name of the OMEGAMON
session that is to receive the command.
System action: None.
Operator response: None.
System programmer response: None.
ING084I
00000003 (VTAM not available)
VTAM was not active at the time the
INGOMX API was invoked.
REQUEST FOR OMEGAMON
SESSION session_name FAILED.
REASON CODE rsn
Explanation: SA z/OS failed to communicate with the
OMEGAMON session denoted by session_name. The
variable rsn contains more specific error information.
System action: The request is not executed.
Operator response: None.
System programmer response: The reason code, rsn,
provides details about the cause of the failure. It is in
hexadecimal encoding and it can be any of the
following:
00000001 (Authentication unsuccessful)
The userid defined for this session is not
permitted to log on to OMEGAMON. Possible
reasons are:
v The user ID is invalid.
v The password is invalid.
v SAFPW was specified as the password, but
no password data set was specified in the
NetView startup procedure.
v SAFPW was specified as the password, but
the password found in the password data
set is either invalid, does not exist, or was
fetched using an invalid owner. See IBM
Tivoli System Automation for z/OS Planning
and Installation for information about how to
set up your security environment to use this
function.
00000002 (Not an OMEGAMON session)
The session that was established between
SA z/OS and the VTAM APPLID defined for
00000004 (Timeout occurred)
The request was interrupted due to a timeout
that has been specified for this session. Either
the timeout is too aggressive or too few
session operators are defined to handle all
assigned sessions.
|
|
|
|
|
|
|
00000005 (Password update failed)
The password of the user defined for this
session is controlled by the system using
SA z/OS password protection feature.
Command INGPW failed to update the
password in the SA z/OS password data set
after OMEGAMON authentication with the
new password.
|
|
|
|
Reset the session user's OMEGAMON
password and re-initialize the
system-controlled password in the SA z/OS
password data set using INGPW.
00000006 (TAF fullscreen session not established)
NetView could not create a Terminal Access
Facility (TAF) fullscreen session using the
BGNSESS command. Refer to the netlog for
additional messages issued by NetView.
0001nnnn (ATTACH of VOST failed with RC=nnnn)
SA z/OS failed to attach a virtual terminal.
Refer to the NetView ATTACH command
description for details of the return code
represented by nnnn in bytes 2 and 3 of the
reason code.
0002nnnn (DETACH of VOST failed with RC=nnnn)
SA z/OS failed to detach a virtual terminal.
Refer to the NetView DETACH command
description for details of the return code
represented by nnnn in bytes 2 and 3 of the
reason code.
0003nnnn (Internal error detected)
An internal error nnnn occurred within
SA z/OS. Report this problem to your IBM
Support Center.
OMEGAMON SESSION session_name
{STARTED | STOPPED}. NEW STATE
IS status.
ING085I
Explanation: Message ING085I is issued each time
SA z/OS established or destroyed an OMEGAMON
session, denoted by session_name.
The action can be either of the following:
v STARTED
The session was started.
Chapter 10. Messages ING001I to INGY1337I
239
ING087I • ING094I
v STOPPED
ING091I
The session was stopped.
task_name ALREADY ACTIVE OR IN
PROCESS OF BECOMING ACTIVE
System action: None.
Explanation: You started the task task_name but the
task is already active or in the process of becoming
active.
Operator response: None.
System action: Processing terminates.
System programmer response: None.
Operator response: None.
The current status is indicated in variable status.
System programmer response: None.
ING087I
task_name: PPI RECEIVER receiver_name
READY
Explanation: The task task_name has initialized
completely and the PPI receiver named receiver_name is
ready for processing requests.
System action: Processing continues
Operator response: None
System programmer response: None
ING088I
task_name: PPI RECEIVER receiver_name
TERMINATED
Explanation: The task task_name has deleted the PPI
receiver named receiver_name. No more requests can be
processed.
System action: Processing terminates
Operator response: None
System programmer response: None
ING089I
task_name: INVALID BUFFER
RECEIVED, DATA DROPPED.
RELATED INFO: request_data
Explanation: The PPI receiver owned by the task
task_name received an invalid request buffer. The first
64 bytes are dumped with the message in the variable
request_data.
ING092I
task_name: service_name SERVICE
FAILED, RC=rc. ERROR
INFORMATION: error_info
Explanation: During the execution of the service
service_name, an error occurred. The variable error_info
indicates in what context the service was invoked by
the task task_name.
For detailed error information, see NetView:
Customization - Using Assembler. In the case of NetView
Program-to-Program Interface (PPI) errors see NetView:
Application Programming Guide for more information
related to the service return code rc.
System action: Processing terminates.
Operator response: None.
System programmer response: Determine why the
service routine failed and correct the problem. Examine
the netlog for additional information. If necessary,
contact your local IBM Support Center for further
assistance.
ING093I
task_name: INVALID KEYWORD OR
SYNTAX ERROR. RELATED
INFORMATION: error_info
System action: Processing continues
Explanation: An invalid keyword or value was
specified in the initialization member for the task
task_name. Related error information is provided in the
variable error_info.
Operator response: None
System action: Processing terminates.
System programmer response: Ensure that only the
SA z/OS monitoring agent is sending requests to the
PPI receiver that is owned by the task task_name.
Operator response: None.
ING090I
TASK task_name IS NOW ACTIVE
Explanation: The task task_name has been activated.
System programmer response: See “Step 2. Configure
SA z/OS and NetView” in the chapter “Beginning the
installation and configuration” in IBM Tivoli System
Automation for z/OS Monitoring Agent Configuration and
User's Guide for a list of valid keywords and values and
correct the problem.
System action: Processing continues.
TASK task_name HAS TERMINATED
Operator response: None.
ING094I
System programmer response: None.
Explanation: The task task_name has terminated.
System action: Processing terminates.
Operator response: None.
System programmer response: None.
240
System Automation for z/OS Messages and Codes:
ING095I • ING104I
ING095I
task_name: NO ACTIVE OPERATOR
FOUND
Explanation: The PPI receiver owned by task
task_name received a request for monitoring data but
could not find an active automation operator to process
the request.
System action: The message is sent back to the
requestor and processing continues.
Operator response: None
System programmer response: Refer to IBM Tivoli
System Automation for z/OS Monitoring Agent
Configuration and User's Guide for instructions how to
set up automation operators for this function and
correct the problem.
ING096I
function : text
Explanation: During processing the function request
for monitoring data any of the following errors as
indicated by text occurred. Examples for text are:
v NetView RC rc from: command
v Timeout occurred
v ING008I ...
ING102I
subsystem CONNECTION TO db2id
(connection_id) IS UP.
Explanation: When monitoring a connection between
a subsystem and DB2, the connection was determined
to be in the status connected.
The variable subsystem shows the subsystem name
as defined in SA z/OS.
The variable db2id shows the DB2 subsystem ID.
The variable connection_id identifies the affected
connection.
System action: None.
Operator response: None.
System programmer response: None.
ING103I
THREADS COULD NOT BE
TERMINATED FROM subsystem
Explanation: This message introduces a list of
ING104I messages that show threads that remain with
a DB2 master after a thread termination process has
completed.
The variable subsystem shows the name of the DB2
master that threads could not be terminated for.
System action: The message is sent back to the
requestor and processing continues.
System action: The requested function could not be
performed.
Operator response: None
Operator response: Investigate why the threads that
are listed in the following ING104I messages could not
be terminated and retry the termination command.
System programmer response: If text contains an
existing SA z/OS message ID, refer to the message
help for problem resolution.
System programmer response: None.
In case of a timeout, increase the time allotted for the
longest request.
Classes: 40, 44.
For return codes returned by SA z/OS or NetView
services refer to related documentation or contact your
local IBM Support Center for further assistance.
ING104I
ING101I
subsystem CONNECTION TO db2id
(connection_id) IS DOWN.
Explanation: When monitoring a connection between
a subsystem and DB2, the connection was determined
to be in the status not connected.
The variable subsystem shows the subsystem name
as defined in SA z/OS.
The variable db2id shows the DB2 subsystem ID.
The variable connection_id identifies the affected
connection.
connection_ID THREAD correlation_ID
ddf_ID
Explanation: This message shows a thread that
remains with a DB2 master after a thread termination
process has completed. It is part of a multiline message
that begins with message ING103I.
The variable connection_ID shows the connection ID
of a thread that could not be terminated.
The variable correlation_ID shows the correlation ID
of a thread that could not be terminated.
The variable ddf_ID shows the token associated to a
distributed database access thread that could not be
terminated.
System action: None.
System action: The requested function could not be
performed.
Operator response: Check whether the subsystem is
not connected to DB2 as a result of normal operation. If
it is not, investigate why the connection is not up.
Operator response: Investigate why the indicated
thread could not be terminated and retry the
termination command.
System programmer response: None.
System programmer response: None.
Classes: None.
Chapter 10. Messages ING001I to INGY1337I
241
ING106I • ING129E
ING106I
INDOUBT THREADS EXIST FOR name
Explanation: There are indoubt threads existing with
the DB2 subsystem named in the message. The message
is given when invoking the INGDB2 command
checking for indoubt threads.
Variable name identifies the DB2 subsystem.
System action: Processing continues.
Operator response: None.
ING108I
NO THREADS LEFT IN subsystem.
Explanation: There are no threads left with this DB2
subsystem for the thread termination process to cancel.
ING113I
YOUR TSO DB2 (subsystem) THREAD
HAS BEEN TERMINATED BY
AUTOMATION.
Explanation: This message is broadcast to effected
TSO users as a result of a DB2 thread termination
request.
The variable subsystem identifies the DB2 subsystem.
System action: Cancels the TSO users of the indicated
DB2 subsystem.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
The variable subsystem identifies the DB2 subsystem.
System action: None.
ING114E
Operator response: None.
System programmer response: None.
Classes: 40, 44.
ING109E
thread_number THREADS COULD NOT
BE TERMINATED FROM subsystem.
Explanation: Threads remain with this DB2 subsystem
after the thread termination process has completed.
The variable thread_number shows the number and
type of threads.
The variable subsystem identifies the DB2 subsystem.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Investigate why the
number of indicated threads are not terminated and
retry the termination command.
Classes: 40, 44.
ING112I
YOUR TSO DB2 (subsystem) THREAD
IS ABOUT TO BE TERMINATED BY
AUTOMATION.
Explanation: This message is broadcast to effected
TSO users due to a DB2 thread termination request.
The variable subsystem identifies the DB2 subsystem.
System action: None.
Operator response: None.
System programmer response:
Classes: 40, 43.
jobname CANCELLED BY
AUTOMATION DUE TO subsystem
THREAD TERMINATION.
Explanation: This message is issued for batch job
cancellations due to a DB2 thread termination or DB2
shutdown process.
The variable jobname identifies the DB2 batch job.
The variable subsystem identifies the DB2 subsystem.
System action: Cancels the batch job for the indicated
DB2 subsystem.
Operator response: None.
System programmer response: None.
Classes: 40, 44.
ING127A
THREADS FOUND AFTER LAST
CYCLE OF DB2 (subsystem), FORCE
SHUTDOWN.
Explanation: After the final cycle (as defined by the
DBITTH timeout variable), threads were still found to
exist for this DB2 subsystem.
The variable subsystem identifies the DB2 subsystem.
System action: None.
Operator response: Contact your system programmer.
System programmer response: Investigate why this
process has not been able to terminate existing threads.
If this DB2 needs to be shut down use the FORCE
option.
Classes: 40, 44.
ING129E
jobname CANCELLED. TABLESPACE
dbname.tsname (subsystem) NEEDED TO
BE STOPPED
Explanation: The job was canceled due to a tablespace
that needed to be stopped.
The variable jobname shows the job name for the job
canceled.
242
System Automation for z/OS Messages and Codes:
ING130I • ING141I
The variable dbname.tsname identifies the tablespace.
ING133I
The variable subsystem identifies the DB2 subsystem.
System action: The identified tablespace is stopped
and the job is canceled.
Operator response: None.
System programmer response: None.
Classes: 40, 44.
ING130I
TABLESPACE dbname.tsname (subsystem)
IS TO BE STOPPED. PLEASE STOP
USING IT.
Explanation: The tablespace indicated is being
stopped.
YOUR USER ID WAS CANCELED IN
ORDER TO ENABLE DSN
TERMINATION FOR subsystem
Explanation: All threads are being stopped by
operator request. TSO users with a DSN session are
canceled in order to enforce the termination of their
DSN session.
The variable subsystem identifies the name of the
DB2 subsystem.
System action: The operator session is canceled.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
The variable dbname.tsname identifies the tablespace.
The variable subsystem identifies the DB2 subsystem.
System action: The identified tablespace will be
stopped.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
ING131I
YOU WERE CANCELLED,
TABLESPACE dbname.tsname (subsystem)
IS TO BE STOPPED.
Explanation: The indicated tablespace is being
stopped and operator sessions using it are canceled.
The variable dbname.tsname identifies the tablespace.
The variable subsystem identifies the DB2 subsystem.
System action: The operator session is canceled.
Operator response: None.
ING140I
ALERT 'alert' FOR 'resource' ON 'system'
AT timestamp
Explanation: This message is produced by SA z/OS
and sent to targets such as System Automation for
Integrated Operations Management (SA IOM),
Netcool/OMNIbus, or the Tivoli Enterprise Console
(TEC) for event notification.
The variable alert shows the alert identifier that was
specified when INGALERT was invoked, or the
default that was used.
The variable resource shows the resource name that
was specified when INGALERT was invoked, or the
default that was used.
The variable system shows the system name that
INGALERT was invoked on.
The variable timestamp shows the time when the
event was originally produced. It is in the format
hh:mm:ss mm/dd/yyyy.
System programmer response: None.
System action: The event is passed to the intended
event notification target.
Classes: 40, 43.
Operator response: None.
System programmer response: None.
ING132I
thread_number CANCELLED DUE TO
STOP OF TABLESPACE dbname.tsname
(subsystem).
Explanation: The tablespace indicated is being
stopped and all threads are canceled.
The variable thread_number shows the number and
type of threads canceled.
The variable dbname.tsname identifies the tablespace.
The variable subsystem identifies the DB2 subsystem.
System action: The indicated threads are canceled.
Operator response: None.
System programmer response: None.
Classes: 40, 43.
Classes: None.
ING141I
SENDING OF ALERT 'alertid' FOR
'resource' WAS SUCCESSFUL
Explanation: An event was successfully sent to targets
such as System Automation for Integrated Operations
Management (SA IOM), Netcool/OMNIbus, or the
Tivoli Enterprise Console (TEC) for event notification.
In the case of SA IOM, it has acknowledged receipt of
the alert.
The variable alertid shows the alert identifier that
was specified when INGALERT was invoked or the
default that was used.
The variable resource shows the resource name that
was specified when INGALERT was invoked or the
default that was used.
Chapter 10. Messages ING001I to INGY1337I
243
ING142I • ING145I
System action: The event was successfully sent to the
intended event notification targets
Operator response: None.
System programmer response: None.
Classes: None.
ING142I
SENDING OF ALERT 'alertid' FOR
'resource' IGNORED
Explanation: An event was not sent to targets such as
System Automation for Integrated Operations
Management (SA IOM), Netcool/OMNIbus, or the
Tivoli Enterprise Console (TEC) for event notification
because the configuration does not allow this. Events
are ignored in the following cases:
1. Event notification is not enabled on this agent for
any of the intended event notification targets.
2. The Inform List of the resource does not contain the
intended event notification target.
3. Code match checking with the message ID
INGALERT of the subject resource returned either
no data or the value IGNORE.
The variable alertid shows the alert identifier that
was specified when INGALERT was invoked or the
default that was used.
The variable resource shows the resource name that
was specified when INGALERT was invoked or the
default that was used.
System action: The event was not sent to the intended
event notification targets.
Operator response: None.
System programmer response: If the event should not
be ignored, determine the cause of the problem by
using the INGCNTL command to check the alert mode
on this agent and checking the Inform List and the
code definitions for the subject resource in the
automation policy.
Classes: None.
ING143I
SENDING OF ALERT 'alertid' FOR
'resource' FAILED
Explanation: An event was not sent to targets such as
System Automation for Integrated Operations
Management (SA IOM), Netcool/OMNIbus, or the
Tivoli Enterprise Console (TEC) for event notification
because of an error. The error is detected by the
command slave. Messages that are generated by the
slave (or slaves) are appended to the above message
text.
The variable alertid shows the alert identifier that
was specified when INGALERT was invoked or the
default that was used.
The variable resource shows the resource name that
was specified when INGALERT was invoked or the
default that was used.
System action: The event was not sent to the intended
event notification targets.
Operator response: None.
System programmer response: Check the additional
message lines and determine the cause of the problem.
Classes: None.
ING144I
CDEMATCH FOR entry type WITH
CODES (code1,code2,code3) RETURNED
INVALID VALUE: value
Explanation: During code match checking a matching
code definition was found. However, the value
returned by the matching code definition is invalid.
The variable entry shows the entry name of the
definition in the MESSAGES/USER DATA policy
item of the automation policy where the matching
code definitions were searched for.
The variable type shows the message ID of the
definition in the MESSAGES/USER DATA policy
item of the automation policy where the matching
code definitions were searched for.
The variables code1, code2, and code3 show the
values that were used to search for a matching code
definition in the MESSAGES/USER DATA policy
item of the specified entry and type.
The variable value shows the value that is returned
from the matching code definition.
System action: Further processing depends on the
context. Processing usually stops.
Operator response: Check for more information.
System programmer response: Check the
configuration and correct the problem.
Classes: None.
ING145I
type INFORMATION IS INCOMPLETE
Explanation: An event is to be sent however the
information about the event notification target is
incomplete.
v The variable type shows the event notification target
that could not be notified. It is one of the following:
IOM
System Automation for Integrated Operations
Management (SA IOM) could not be reached.
The information specified with the ALERTHOST
parameter of the INGCNTL command is
incomplete.
EIF
An EIF event could not be generated. The EAS
244
System Automation for z/OS Messages and Codes:
ING146I • ING150I
PPI receiver name to be specified with the
EIFPPI parameter of the INGCNTL command is
missing.
TTT
A trouble ticket could not be generated because
the address data for the TDI server or the data
set characteristics for the trouble ticket detail
data are missing or incomplete. This data should
be specified with the TTTHOST and TTTDATA
parameters of the INGCNTL command.
USR
A user event could not be generated. The name
of the automation procedure that is used to
handle user events is missing. The procedure
name should be specified with the
USRHANDLER parameter of the INGCNTL
command.
Operator response: Correct the problem and reissue
the command.
System programmer response: None.
Classes: None.
ING148I
function : request REQUEST TIMED OUT
Explanation: A request timed out.
The variable function shows the name of the
function that detected the time out.
The variable request shows the request that timed
out.
System action: None.
Operator response: Check other messages for more
information.
System action: The event is not sent to the indicated
event notification target. The request is rerouted to the
next available agent in the sysplex (if any).
System programmer response: None.
Operator response: None.
ING149I
System programmer response: Check the
configuration and correct the problem.
Explanation: This message provides header
information for the INGCNTL LIST command.
Classes: None.
System action: Processing continues.
ING146I
ALERTING IS DISABLED
Explanation: An alert is to be sent to targets such as
System Automation for Integrated Operations
Management (SA IOM), Netcool/OMNIbus, or the
Tivoli Enterprise Console (TEC) for event notification.
However event notification is not enabled on this agent
for any supported event notification target.
System action: The event is not sent to the indicated
event notification target.
Operator response: Turn on event notification for the
intended target with the INGCNTL command if
desired.
Classes: None.
LIST CONTROL SETTINGS
Operator response: None.
System programmer response: None.
Classes: None.
ING150I
timestamp : object severity jobname DATA=
data
Explanation: ING150I represents an event that was
injected into the system by an external or internal
monitor. Typically INGMON is called from the
NetView automation table as an action for this event.
INGMON will find the corresponding monitor
resources and trigger automation there if applicable.
Classes: None.
The variable timestamp is the time that the event
was originally produced or when the message was
created. It is in the format hh:mm:ss mm/dd/yyyy.
ING147I
The variable object specifies the monitored object
that this event is related to.
System programmer response: None.
ALERTING IS NOT SUPPORTED FOR
RESOURCE TYPE 'type'
Explanation: An event is to be sent to an event
notification target such as IOM, EIF, TTT or USR.
However, the resource type specified is not supported
for event notification.
The variable type shows the type of the resource
that was specified, which is not valid for event
notification.
System action: The event is not sent to the intended
event notification target.
The variable severity specifies the severity of the
status of the monitored object that led to this event.
The variable jobname specifies the job name that the
monitored object is related to or 'N/A' if there is
none.
The variable data can be any data the monitor
provides that might be useful for automation or
recovery actions.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Chapter 10. Messages ING001I to INGY1337I
245
ING151I • ING156I
Classes: None.
ING151I
ATTACH OF name SUCCESSFUL
Explanation: The ATTACH of a virtual operator
station task (VOST) was successful.
The variable name specifies the attach name of the
VOST. Note that this name is the content of
TGLOBAL SUBSJOB, that is, the job name of the
VOST management APL.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Classes: None.
ING152I
ATTACH OF name FAILED WITH RC=rc
Explanation: The ATTACH of a virtual operator
station task (VOST) failed with a return code greater
than 0.
ING154I
command OF name FAILED WITH RC=rc
Explanation: The stopping of a virtual operator station
task (VOST) failed with a return code greater than 0.
The variable command shows the command used to
stop the VOST.
The variable name specifies the attach name of the
VOST. Note that this name is the content of
TGLOBAL SUBSJOB, that is, the job name of the
VOST management APL.
The variable rc shows the return code given by the
command.
System action: The VOST is not stopped.
Operator response: Contact your system programmer.
System programmer response: Review the netlog for
additional messages issued by the specified command
and correct the problem.
Classes: None.
The variable name specifies the attach name of the
VOST. Note that this name is the content of
TGLOBAL SUBSJOB, that is, the job name of the
VOST management APL.
ING155I
The variable rc shows the return code given by the
ATTACH command.
v The variable command shows the command that was
executed.
System action: The VOST is not started.
Operator response: Contact your system programmer.
System programmer response: Review the netlog for
additional messages issued by the ATTACH command
and correct the problem.
Classes: None.
ING153I
command OF name SUCCESSFUL
Explanation: The stopping of a virtual operator station
task (VOST) was initiated successfully. Note that the
VOST may still be active for a certain time after this
message is issued.
ENVIRONMENT CHECK FAILED FOR
command. REASON=rs
Explanation: A command was issued in an
unsupported environment.
v The variable rs shows the reason code that can have
the following values:
1 Required task globals not set
2 Running on an unsupported task
3 Configuration not fully loaded
4 Main include member could not be read
5 ACFLEVEL could not be determined
6 ACFLEVEL mismatch
System action: The command stops processing.
Operator response: Contact your system programmer.
System programmer response: See the documentation
of the command that issued the message and correct
the problem.
The variable command shows the command used to
stop the VOST.
Classes: None.
The variable name specifies the attach name of the
VOST. Note that this name is the content of
TGLOBAL SUBSJOB, that is, the job name of the
VOST management APL.
ING156I
name ENDED WITH RC=rc
Explanation: The command executed in a virtual
operator station task (VOST) ended.
System action: Processing continues.
The variable name specifies the attach name of the
VOST.
Operator response: None.
The variable rc shows the return code of the
command that ran in the VOST.
System programmer response: None.
Classes: None.
System action: The VOST is stopped.
Operator response: None.
System programmer response: None.
246
System Automation for z/OS Messages and Codes:
ING157I • ING163I
Classes: None.
ING157I
INVALID VALUE FOR name: value
Explanation: Data was found that is not valid.
The variable name specifies the context.
The variable value shows the invalid data.
System action: Processing stops.
Operator response: Contact your system programmer.
System programmer response: See the documentation
of the command that issued the message and correct
the problem.
Classes: None.
ING158I
SENDING OF ALERT alertid FOR
resource PARTIALLY FAILED
Explanation: An event was only partially sent to the
designated targets.
Variable alertid identifies the alert identifier that was
specified when INGALERT was invoked or the
default was used.
Variable resource identifies the resource.
System action: Processing continues.
ITM SOAP request. The attribute names and values are
separated by the separator character, sep, of value
X'FF'.
The first line of this multiline message denotes the
SOAP server, server_name, that provided this response.
The second line contains the attribute names separated
by the separator character. All the following lines
contain the attribute values separated by the separator
character.
This message is written to the console only.
System action: None.
Operator response: None.
System programmer response: None.
ING161I
SENDING SOAP REQUEST TO
SERVER: server_name
Explanation: A SOAP request is being sent to the
SOAP server denoted by server_name. This message is
written to the netlog only.
System action: None.
Operator response: None.
System programmer response: None.
Operator response: None.
ING162I
ING159I
EXIT exitname RETURNED
UNEXPECTED RESULTS. REASON
reason
Explanation: An exit was called but returned either an
invalid return code or invalid data.
v The variable exitname shows the name of the exit that
was called.
v The variable reason shows why the exit is considered
to be in error:
01 Unexpected return code
02 Invalid number of data lines returned
03 Invalid data found in the returned lines
System action: Further processing depends on the
context. Processing usually stops.
SOAP FAULT CODE code. REASON:
reason
Explanation: The SOAP request failed with a fault
code of code. Possible codes are Client,
VersionMismatch, MustUnderstand, and Server. The
Client fault code indicates that the SOAP message was
incorrectly formed.
The reason text indicates the particular fault.
This message is written to the console only.
System action: None.
Operator response: Contact your system programmer.
System programmer response: For a Client fault code,
correct the SOAP message and try again. For any other
fault code, contact your IBM support representative.
Operator response: Check for more information.
System programmer response: Check the
configuration and correct the problem.
Classes: None.
ING160I
RESPONSE FROM SOAP SERVER:
server_nameattribute_name_1 sep
attribute_name_2 sep ... attribute_name_n
sepattribute_value_1 sep attribute_value_2
sep ... attribute_value_n sep
Explanation: This message displays the names and
values of the attributes that have been requested by an
ING163I
FAULT DETAIL: text
Explanation: This message provides further detail in
variable text about the fault reported in the preceding
ING162I message. This message spans multiple lines if
further fault details are reported in the SOAP response.
This message is written to the console only.
System action: None.
Operator response: Contact your system programmer.
System programmer response: For a Client fault code
(see ING162I), correct the SOAP message and try again.
Chapter 10. Messages ING001I to INGY1337I
247
ING164I • ING167I
For any other fault code, contact your IBM support
representative.
For reason code 0005nnnn, specify the correct data set
name or fix the I/O error.
ING164I
In any other case, contact your IBM support
representative.
SOAP REQUEST FAILED, REASON:
reason SERVER: server_name
Explanation: An error occurred while attempting to
process a SOAP request on the SOAP server denoted
by server_name. The actual error reason is encoded in
the separate reason variable.
This message is written to the console only.
The following reasons are defined:
00000004
A timeout occurred and the connection was
terminated.
0001nnnn
INGOMX failed to connect to, send to, or
receive from a socket created to communicate
with the SOAP server denoted by server_name.
The socket error is encoded in bytes 2 and 3
represented by variable nnnn.
0002nnnn
The output returned from the IBM Tivoli
Monitoring SOAP server could not be handled
by the XML parser. The XML parser reason
code is encoded in bytes 2 and 3 represented
by variable nnnn.
0003nnnn
An internal error occurred. The variable nnnn
represents the internal error code.
0004xyyy
An HTTP error occurred while processing the
request. If x=0, yyy denotes the 3-digit HTTP
response code, for example, 404. If x=1 and
y=008 check userID and password otherwise
the variable yyy represents the internal error
code.
0005nnnn
An error occurred while allocating or reading
the SOAP request data set. The pipe QSAM
return code is encoded in bytes 2 and 3
represented by variable nnnn.
0006nnnn
An error occurred while processing a
CORRCMD pipe stage. The return code is
encoded in bytes 2 and 3 represented by
variable nnnn.
System action: None.
ING165I
protocol status-code reason-phrase
Explanation: This message reflects the status line of a
preceding HTTP request in case of a non-zero status
code.
The variable protocol reports the HTTP protocol used
by the server.
The variable status-code reports the status of the
request.
The variable reason-phrase contains human readable
information explaining the status-code.
This message is written to the netlog only.
System action: None.
Operator response: Contact your system programmer.
System programmer response: For status codes 1xx
and 2xx, no action is required.
For status codes 3xx, check out message ING167I for
the new location and try again.
For status codes 4xx, check out the details reported by
message ING166I and fix the problem.
For status codes 5xx, collect the details reported by
message ING166I and contact your IBM support
representative.
ING166I
HTTP-RESPONSE INFORMATION: text
Explanation: This message reports additional
information about the HTTP response, where the
variable text contains general header fields, response
header fields, and entity header fields.
This message is written to the netlog only.
System action: None.
Operator response: Contact your system programmer.
System programmer response: See message ING165I
about how to use this information depending on the
status code returned by the server.
Operator response: Contact your system programmer.
ING167I
System programmer response: For reason code
00000004, increase the timeout value. The parameter
default variable INGOMX_WAIT can be set to increase
the timeout.
Explanation: This message is issued as the result of a
3xx status code received as the response of the HTTP
SOAP request. The request URI was either temporarily
or permanently moved to a new location or is only
accessible through the proxy server at the reported
location. The request must be redirected to the new
location reported by the variable location.
For reason codes 0001nnnn and 0004xyyy, ensure you
have connectivity to the SOAP server and verify the
port and path of the SOAP service.
NEW LOCATION: location
This message is written to the console only.
248
System Automation for z/OS Messages and Codes:
ING170I • ING204W
System action: None.
System action: None.
Operator response: Contact your system programmer.
Operator response: None.
System programmer response: Correct the server
information in the customization dialog to use the
reported location and then try the request again.
System programmer response: None.
ING170I
SA turned the resource resource request as
requested in domain domain. Common
observed state: observed, Common
desired state: desired, Common
operational state: operational, Common
compound state: compound
ING202I
THE FOLLOWING ENTRY-TYPES
HAVE BEEN DELETED: entry-type
Explanation: This message is issued by the
INGCLEAN utility when entry-types have been
deleted. The deleted entry-types are appended to the
above message text. Note that the entry-types for which
a default has been restored are not included in this list.
The variable entry-type displays any entry-types that
have been deleted.
System action: Processing was successful.
Operator response: None.
Explanation: This message is created by the SA z/OS
internal event notification function when a request has
been issued to start or stop a resource. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
System programmer response: None.
The variable request indicates if an Online or Offline
request has been issued.
Classes: None.
The variable domain shows the name of the
end-to-end automation domain.
ING200W
The variable observed shows the observed state of
the resource.
SA event with NoStatusChange reason
in domain domain
Explanation: This message is created by the SA z/OS
internal notification function to send current status
information to the end-to-end automation adapter.
System action: None.
Operator response: None.
System programmer response: None.
ING201W
SA detected a status change of resource
resource in domain domain. Common
observed state: observed, Common
desired state: desired, Common
operational state: operational, Common
compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when the status of a
resource changes. It shows the resource’s new status in
the end-to-end automation resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
SA detected that the system system
joined the domain domain
ING203I
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the observed status of
a system resource has changed from Sysgone.
The variable system shows the name of the system.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING204W
SA detected that the system system left
the domain domain
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the observed status of
Chapter 10. Messages ING001I to INGY1337I
249
ING205I • ING208W
The variable system shows the name of the system.
The variable desired shows the desired state of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable operational shows the operational state
of the resource.
a system resource has become Sysgone.
System action: None.
Operator response: None.
System programmer response: None.
ING205I
SA turned off the automation for
resource resource in domain domain.
Common observed state: observed,
Common desired state: desired, Common
operational state: operational, Common
compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when a request has
been issued to switch on or off the automation flag of a
resource. It shows the resource’s current status in the
end-to-end automation resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
ING207W
SA detected a warning in domain
domain. The resource resource has a
performance problem. Common
observed state: observed, Common
desired state: desired, Common
operational state: operational, Common
compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the health status of
the resource has become degraded. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
System action: None.
The variable operational shows the operational state
of the resource.
Operator response: None.
The variable compound shows the compound state of
the resource.
System programmer response: None.
System action: None.
ING206W
SA detected a warning in domain
domain. The resource resource has been
degraded. Common observed state:
observed, Common desired state: desired,
Common operational state: operational,
Common compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the observed status of
the resource has become degraded. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
250
System Automation for z/OS Messages and Codes:
Operator response: None.
System programmer response: None.
ING208W
SA detected a warning in domain
domain. The resource resource has
problems caused by a dependency to
another resource. Common observed
state: observed, Common desired state:
desired, Common operational state:
operational, Common compound state:
compound
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the startable status of
the resource has become inhibited. It shows the
resource’s current status in the end-to-end automation
resource data model.
ING209W • ING211W
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
ING209W
SA detected a problem in domain
domain. The resource resource can't be
turned into the requested state.
Common observed state: observed,
Common desired state: desired, Common
operational state: operational, Common
compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports a problem in the
automation state or the observed state. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
ING210W
SA detected a problem in domain
domain. The resource resource needs a
manual reset by the operator. Common
observed state: observed, Common
desired state: desired, Common
operational state: operational, Common
compound state: compound
internal event notification function when the
automation manager reports that the observed status of
the resource has changed to harddown. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
ING211W
SA detected a problem in domain
domain. The resource resource has
problems caused by an offline system.
Common observed state: observed,
Common desired state: desired, Common
operational state: operational, Common
compound state: compound
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the observed status of
the resource has changed to sysgone. It shows the
resource’s current status in the end-to-end automation
resource data model.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
The variable observed shows the observed state of
the resource.
The variable desired shows the desired state of the
resource.
The variable operational shows the operational state
of the resource.
The variable compound shows the compound state of
the resource.
System action: None.
Operator response: None.
System programmer response: None.
Explanation: This message is created by the SA z/OS
Chapter 10. Messages ING001I to INGY1337I
251
ING212W • ING219I
ING212W
SA event with unknown reason in
domain domain
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager sends an event with an unknown
reason.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING213I
SA detected that system automation is
ready in domain domain
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that the status of the
automation domain is Online.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING214W
SA detected that system automation is
broken in domain domain
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that the status of the
automation domain is Offline.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING215I
SA detected a configuration policy
refresh in domain domain
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that the automation
policy has been refreshed in the automation domain.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING216I
SA detected a new configuration in
domain domain. New resource resource
created.
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that a new resource has
been created in the automation domain.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING217I
SA detected a deleted configuration in
domain domain. Resource resource
deleted.
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that a resource has been
deleted in the automation domain.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
ING218I
SA detected a new configuration in
domain domain. Request action request
issued for resource resource
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that a new request has
been issued for the resource in the automation domain.
The variable domain shows the name of the
end-to-end automation domain.
The variable resource shows the name of the
resource.
System action: None.
Operator response: None.
System programmer response: None.
ING219I
SA detected a deleted configuration in
domain domain. Request action request
deleted for resource resource
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
252
System Automation for z/OS Messages and Codes:
ING220I • ING225W
end-to-end automation adapter that a request for the
resource in the automation domain has been deleted.
The variable domain shows the name of the
end-to-end automation domain.
The variable resource shows the name of the
resource.
System action: None.
Operator response: None.
System programmer response: None.
ING222I
SA detected an automation status
change in domain domain
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that properties have
been changed in the automation domain.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
ING220I
SA detected a new configuration in
domain domain. New relationship
relationship with source resource source
and target resource target created.
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that a new relationship
has been created between the source resource and the
target resource in the automation domain.
The variable domain shows the name of the
end-to-end automation domain.
The variable relationship shows the name of the
relationship.
The variable source shows the name of the
dependent resource.
The variable target shows the name of the
supporting resource.
System action: None.
Operator response: None.
System programmer response: None.
ING223W
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the desired status of a
system resource has changed to Available.
The variable system shows the name of the system.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
System programmer response: None.
SA detected that the system system
switched back to automation mode by
an operator command in domain domain
ING224I
System programmer response: None.
ING221I
SA detected a deleted configuration in
domain domain. Relationship relationship
with source resource source and target
resource target deleted.
Explanation: This message is created by the SA z/OS
internal event notification function to inform the
end-to-end automation adapter that a relationship
between the source resource and the target resource in
the automation domain has been deleted.
SA detected that the system system
switched into maintenance mode by
operator command in domain domain
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the desired status of a
system resource has changed to Unavailable.
The variable system shows the name of the system.
The variable domain shows the name of the
end-to-end automation domain.
System action: None.
Operator response: None.
The variable domain shows the name of the
end-to-end automation domain.
System programmer response: None.
The variable relationship shows the name of the
relationship.
ING225W
The variable source shows the name of the
dependent resource.
The variable target shows the name of the
supporting resource.
System action: None.
Operator response: None.
System programmer response: None.
SA suspended automation for resource
resource in domain domain as requested.
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the automation flag of
the resource has been switched off.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
Chapter 10. Messages ING001I to INGY1337I
253
ING226I • ING235W
System action: None.
ING232I
Operator response: None.
System programmer response: None.
ING226I
SA resumed automation for resource
resource in domain domain as requested.
Explanation: This message is created by the SA z/OS
internal event notification function when the
automation manager reports that the automation flag of
the resource has been switched on.
The variable resource shows the name of the
resource.
The variable domain shows the name of the
end-to-end automation domain.
PPI receiver ID for E2E adapter is set to
receiver_id.
Explanation: The PPI receiver ID for the message
adapter of the event/automation service, which is used
to forward events to the automation adapter, has been
set to the specified receiver ID.
System action: None.
Operator response: None.
System programmer response: None.
ING233E
Event forwarding task EVTOPER for
E2E not defined.
Operator response: None.
Explanation: The primary agent cannot be started
because the automated function EVTOPER, which is
used to forward the events to the automation adapter,
has not been defined in the automation policy.
System programmer response: None.
System action: Processing stops.
System action: None.
Operator response: None.
ING230E
Addressed consumer consumer not
registered. Event not forwarded.
Explanation: An event was received with a consumer
that was not registered as the target address. The event
therefore cannot be forwarded to the addressed
consumer.
The variable consumer shows the name of the event
consumer that was specified as the target address of
the event, and that the event should have been
forwarded to.
System action: Processing of the event is terminated.
Operator response: None.
System programmer response: Check whether event
notification has been correctly initialized and
end-to-end automation has been registered as an event
consumer.
System programmer response: Define the automated
function EVTOPER.
ING234E
Request 'request' failed: RC=rc
command='command' reason='reason'
Explanation: The specified command abended.
The variable request shows the request that was
received from the automation adapter for execution.
The variable rc shows the return code of the
command.
The variable command shows the command that
implements the request.
The variable reason shows text that describes the
error.
System action: Execution of the request stops.
Operator response: None.
ING231E
Event notification service returns rc.
Event not forwarded to receiver_id.
Explanation: The event could not be forwarded to the
addressed consumer via the PIPE stage TECROUTE.
The variable rc shows the return code to PIPE stage
TECROUTE.
The variable receiver_id shows the name of the PPI
receiver ID.
System action: Processing of the event is stopped.
Operator response: None.
System programmer response: Check whether the
status of the PPI receiver ID is active. The status of PPI
receivers can be listed with the command DISPPI.
254
System Automation for z/OS Messages and Codes:
System programmer response: Analyze the return
code and reason code for the abending command.
ING235W
No information from automation
manager. event event not created for
consumer.
Explanation: An error occurred when requesting
information from the automation manager that needed
to be included in a domain event. The event has not
been created.
v The variable event specifies the event to be created.
Possible values are: READY, REFRESH, CHANGE.
A READY event is created at initialization time of the
automation domain and after having recovered from
miscellaneous error situations.
ING236W • ING239W
A REFRESH event is created after having refreshed
the configuration policy.
tex_request
The name of the task execution request
A CHANGE event is created after a takeover of the
automation manager if the outage has not exceeded a
given time interval.
error_code
The REXX function INGRXTX0 and the
common REXX macros issue the following
error codes:
1 RPC service failed: either INGPXSND,
INGPXRCV or INGPXDEL.
2 Read from or write to the task execution
data stream failed.
3 Unknown task execution operation name.
4 Execution of a task execution request
started but failed. The REXX macro that
implemented the execution of the request
did not issue an error message. This is the
default return code and the standard
ING238E message is written with
SERVICE=OperationName and
RC=OperationReturnCode.
5 Authorization error: the user that made
the request is not authorized to make it.
6 At least one request in the list of requests
failed.
7 The execution of a task execution request
failed for any other reason.
8 The execution of a task execution request
failed because service INGPYAMC failed.
9 Execution of a task execution request was
rejected because of expired expiration
time.
24 Task execution request contains no meta
data.
28 The task execution command handler
aborts because there is not enough time to
send back the response data. No response
is returned.
32 The task execution command handler
aborts because of a REXX signaling error.
36 The automation adapter is not supported
by this product.
v The variable consumer shows the name of the event
consumer that the event should have been forwarded
to.
System action: Processing of the event is stopped.
Operator response: None.
System programmer response: Analyze the NetView
log for further SA z/OS messages concerning the
communication between the primary agent and the
automation manager.
ING236W
Task execution request request processed
with warnings: COMMAND='command'
REASON='reason'
Explanation: A warning was issued when executing a
task execution request. The message variables are:
request
The name of the task execution request
command
The command that failed.
reason
Text that describes the error.
System action: The request is executed with warnings.
Operator response: None.
System programmer response: Analyze the reason
code of the warning message.
ING237W
Request 'request' processed with
warnings: COMMAND='command'
REASON='reason'
Explanation: A warning was issued when executing
an end-to-end request.
The variable request shows the name of the
end-to-end request.
The variable command shows the issued command
that implements the request.
The variable reason specifies the warning message.
System action: The end-to-end request executes.
Operator response: Analyze the reason code of the
warning message.
System programmer response: None.
ING238E
Task execution request tex_request failed:
ERROR=error_code SERVICE='service'
RC=return_code REASON='reason'
Explanation: The REXX function INGRXTX0 and
common REXX macros issue this message if there is an
error. The message variables are:
|
|
service
The service that failed.
return_code
The return code of the service that failed.
reason
Text that describes the error.
System action: Execution of the request failed for the
reason given in the message.
Operator response: None.
System programmer response: Check the netlog and
correct the error.
ING239W
Value in advanced automation option
name not valid. Default value used.
Explanation: The value provided in the advanced
automation option is not accepted as a valid value.
The variable name shows the name of the advanced
automation option.
Chapter 10. Messages ING001I to INGY1337I
255
ING240E • ING247E
The variable value shows the value of the advanced
automation option.
System action: Processing continues with the default
value for the specified advanced automation option.
Operator response: None.
System programmer response: Correct the value
provided in the advanced automation option.
ING240E
Unexpected task execution request name
tex_request.
Explanation: The REXX macro implemented to
execute the task execution request was called with an
unexpected task execution request name.
The variable tex_request shows the name of the task
execution request.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING241E
Unexpected task execution element type
type.
Explanation: The REXX macro implemented to
execute the task execution request was called with an
unexpected task execution request type.
The variable type shows the type of task execution
element.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING242E
Cannot read task execution element
from data stream.
Explanation: The REXX macro implemented to
execute the task execution request cannot read the task
execution element from the data stream.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING243E
Cannot write task execution element to
data stream.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING244E
Invalid filter element name filter.
Explanation: The REXX macro implemented to
execute the task execution request was passed an
invalid filter element name.
The variable filter shows the name of the filter
element.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING245E
Duplicate filter element name filter.
Explanation: The REXX macro implemented to
execute the task execution request was passed duplicate
filter element names.
The variable filter shows the name of the filter
element.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING246E
Invalid combination of filter element
names filter1 and filter2.
Explanation: The REXX macro implemented to
execute the task execution request was passed an
invalid combination of filter element names.
The variables filter1 and filter2 show the names of
the two filter elements.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING247E
Invalid filter element filter. Filter value
unknown: value
Explanation: The REXX macro implemented to
execute the task execution request was passed an
unknown filter value.
The variable filter shows the name of the filter.
The variable value shows the value of the filter.
Explanation: The REXX macro implemented to
execute the task execution request cannot write to the
data stream to return data to the calling routine.
System action: Processing of the task execution
request fails.
System action: Processing of the task execution
request fails.
System programmer response: None.
256
System Automation for z/OS Messages and Codes:
Operator response: Contact your IBM Support Center.
ING248E • ING254E
ING248E
Invalid filter element filter. Filter
operator unknown: operator
Explanation: The REXX macro implemented to
execute the task execution request was passed a filter
element with an unknown operator comparing the filter
name and filter value.
The variable filter shows the name of the filter.
The variable operator shows the filter operator.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING249E
Execution of a task execution request
timed out. The expiration time 'time' was
too short – missing_time.
Explanation: The expiration time that was provided
for the task execution request was too short.
The variable time shows the expiration time that
was provided for the task execution request.
The variable missing_time specifies the missing time
interval.
System action: Processing of the task execution
request fails.
Operator response: Contact your system programmer.
System programmer response: Check the defined
timeout interval for task execution requests. If
necessary, increase it as described in System Automation
for z/OS: End-to-end automation adapter.
ING250E
Execution of a service timed out. The
expiration time time was reduced to
number seconds.
Explanation: A service routine timed out without
exploiting the expiration time that was provided for the
execution of the task execution request. The execution
time was reduced to the maximum value for the WAIT
parameter of the executed service.
The variable time shows the expiration time that
was provided for the task execution request.
The variable number shows the value for the WAIT
parameter of the executed service.
System action: Processing of the task execution
request fails.
Operator response: None.
System programmer response: None.
ING251E
Invalid combination of filter elements
filter1 and filter2. Values value1 and value2
are mutually exclusive.
Explanation: The REXX macro implemented to
execute the task execution request was passed an
invalid combination of values for the filter elements.
The variables filter1 and filter2 show the names of
the two filter elements.
The variables value1 and value2 show the values of
the two filter elements.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING252E
Domain initialization failed.
Automation environment not initialized.
Explanation: Initialization of the automation domain
failed because initialization of the system automation
environment of the primary agent has not yet been
completed.
System action: The start of the automation adapter
fails.
Operator response: Restart the automation adapter
after the initialization of the automation environment of
the primary agent has completed.
System programmer response: None.
ING253E
Domain initialization failed. Primary
agent already started on system system.
Explanation: Initialization of the automation domain
failed because the primary agent is already running on
another system within the subplex.
The variable system shows the system name.
System action: The start of the automation adapter
fails.
Operator response: Check whether the automation
adapter should be stopped on the other system.
System programmer response: None.
ING254E
Domain initialization failed. PPI
receiver receiver of EAS not ACTIVE.
Explanation: Initialization of the automation domain
failed because the PPI receiver ID of the NetView
event/automation service is not active.
The variable receiver shows the name of the PPI
receiver.
System action: The start of the automation adapter
fails.
Operator response: Analyze the status of the PPI
Chapter 10. Messages ING001I to INGY1337I
257
ING255E • ING261E
receivers by using command DISPPI. Check whether
the event/automation service has been started and has
successfully initialized its receiver ID at the PPI.
System programmer response: None.
Operator response: Analyze the status of the PPI
receivers by using command DISPPI. Check whether
the event/automation service has been started and has
successfully initialized its receiver ID at the PPI.
System programmer response: None.
ING255E
Requesting information from
Automation Manager of domain domain
failed.
Explanation: Requesting information from automation
manager of an automation domain failed. Requesting
information from automation is necessary during the
initialization of the automation domain or when
requesting information about the automation domain.
The variable domain shows the name of the
automation domain.
System action: The task execution request fails.
Operator response: None.
System programmer response: Analyze the problem.
Examine the NetView log for further information. If the
problem persists contact your IBM Support Center.
ING256E
Health check failed. Event forwarding
switched off.
Explanation: Events were lost when trying to forward
them from the primary agent to the automation
adapter. Event forwarding has therefore been switched
off, which results in failing the health check of the
automation domain.
ING258E
Execution of service service failed.
Unexpected data received.
Explanation: The requested service did not return the
expected data.
The variable service shows the name of the
requested service.
System action: Processing of the task execution
request fails.
Operator response: Notify your system programmer.
System programmer response: Determine why the
service routine fails. Examine the NetView log for
additional information.
ING259E
Invalid request element. Request name
unknown: name
Explanation: An end-to-end request with an unknown
name was received.
The variable name shows the request name.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System action: The automation adapter will stop. A
subsequent restart enforces the re-initialization of the
automation adapter and a refresh of the status
information about first-level automation resources on
the end-to-end server.
System programmer response: None.
Operator response: Check the communication path
from the primary automation agent to the NetView
event/automation service. As soon as the
communication path is available again, the automation
adapter can be restarted.
Explanation: An end-to-end request with an unknown
type was received.
System programmer response: None.
ING257E
Health check failed. PPI receiver receiver
of EAS not ACTIVE.
Explanation: The PPI receiver identifier of the
event/automation service is not in the status ACTIVE.
This results in failing the health check of the
automation domain.
The variable receiver shows the PPI receiver ID of
the NetView event/automation service.
System action: The automation adapter does not send
a heartbeat event. Thus the communication status of
the domain on the end-to-end automation server
changes.
258
System Automation for z/OS Messages and Codes:
ING260E
Invalid request element. Request type
unknown: type
The variable type shows the request type.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING261E
Invalid request element. Multiple
solicited requests are not supported.
Explanation: Multiple solicited end-to-end requests
were received to be executed by the primary agent.
Only one solicited end-to-end request can be accepted.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING262W • ING269E
ING262W
An attempt was made to overwrite at
least one restricted parameter. Input
parameters have been ignored:
parameters
Explanation: An end-to-end request was received with
parameters that attempted to overwrite restricted
parameters. The parameters are ignored.
The variable parameters shows a list of the ignored
parameters.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING263E
Request rejected because mandatory
parameter SOURCE is missing.
Explanation: An end-to-end request was received
without the specified originator of the request via
parameter SOURCE.
System action: Processing of the task execution
request fails.
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING264E
Reset_from_NRE rejected because agent
status of resource resource is CTLDOWN.
Explanation: A reset-from-non-recoverable-error
request was received for a resource that is in agent
status CTLDOWN. Such a request is not supported for
resources in agent status CTLDOWN.
The variable resource shows the name of the
resource that the request was issued for.
System programmer response: None.
ING266E
Reset_from_NRE failed because no data
to resource resource received from
Automation Manager.
Explanation: A reset-from-non-recoverable-error
request was received for a resource. An error occurred
when requesting information from the automation
manager about the resource that the request was issued
against.
The variable resource shows the name of the
resource that the request was issued for.
System action: Processing of the task execution
request fails.
Operator response: Check whether the resource that
the request was issued for is known to the automation
manager.
System programmer response: None.
ING267E
Reset_from_NRE rejected because
resource resource is not of class APL.
Explanation: A reset-from-non-recoverable-error
request was received for a resource that is not of class
APL. This request is only supported for resources of
type APL.
The variable resource shows the name of the
resource that the request was issued for.
System action: Processing of the task execution
request fails.
Operator response: Check the type of the resource
that the request was issued for.
System programmer response: None.
request rejected because system name is
missing.
System action: Processing of the task execution
request fails.
ING268E
Operator response: Check the agent status of the
resource that the request was issued for.
Explanation: An end-to-end request concerning a
system was issued, but the system name was not
specified.
System programmer response: None.
ING265E
Reset_from_NRE rejected because
observed status of resource resource is
not HARDDOWN.
Explanation: A reset-from-non-recoverable-error
request was received for a resource that is not in status
HARDDOWN. Such a request is only supported for
resources in status HARDDOWN.
The variable resource shows the name of the
resource that the request was issued for.
System action: Processing of the task execution
request fails.
The variable request shows the name of the
end-to-end request.
System action: Processing of the task execution
request fails.
Operator response: Check that the request was issued
against a resource of class SYS.
System programmer response: None.
ING269E
Native command contains an invalid
value for parameter $WAIT: wait
Explanation: An invalid value was specified as the
WAIT parameter when issuing a native command.
Operator response: Check the status of the resource.
Chapter 10. Messages ING001I to INGY1337I
259
ING270E • ING276E
The variable wait shows the value for the WAIT
parameter that was received.
System action: Processing of the task execution
request fails
Operator response: Contact your IBM Support Center.
System programmer response: None.
ING270E
User user is not authorized to execute
command: command
Explanation: The execution of the specified command
is rejected by the authorization user exit AOFEXE2E.
The variable user shows the user ID that is
associated with the command.
ING273W
Explanation: More than one request in a list of
requests that were included in a task execution request
were processed with warnings.
System action: Processing of the task execution
request continues.
Operator response: Examine the NetView log for
additional information about the single requests that
were processed with warnings.
System programmer response: None.
ING274E
The variable command shows the rejected command
resulting from the related end-to-end request.
System action: Processing of the task execution
request fails.
Operator response: Contact your system programmer
to obtain the necessary authorization to execute the
command.
System programmer response: If it is appropriate,
authorize the user to issue the specified command.
ING271E
Command execution failed. Waiting for
asynchronous output timed out.
Explanation: A timeout occurred when waiting for
asynchronous output generated by a command that
was issued from within a PIPE.
System action: Processing of the task execution
request fails
More than one request in a list
processed with warnings.
A query to the automation manager
failed due to unsuccessful execution of
service INGPYAMC.
Explanation: An error occurred when requesting
information from the automation manager via the
automation manager API INGPYAMC.
System action: Processing of the task execution
request fails.
Operator response: Check the communication path
from the primary agent to the automation manager and
examine the NetView log for additional information. If
the problem persists contact your IBM Support Center.
System programmer response: None.
ING275E
Processing failed for command: command
Explanation: A command was called that ended with
a non-zero return code.
The variable command shows the failed command.
Operator response: Retry the operation. If the
problem persists, contact your system programmer.
System action: Processing of the command stops.
System programmer response: Determine why the
command does not return its output within the
expected time. Examine the NetView log for additional
information.
System programmer response: None.
Operator response: Determine why the command
failed and correct the problem.
ING276E
ING272E
More than one request in a list failed.
Explanation: More than one request in a list of
requests that were included in a task execution request
failed.
System action: Processing of the related requests fails.
Operator response: Examine the NetView log for
additional information about the single requests that
were processed with errors.
System programmer response: None.
260
System Automation for z/OS Messages and Codes:
Execution of a service timed out.
Explanation: The return code of the requested service
indicates a timeout problem.
System action: The requested service does not
complete successfully.
Operator response: Retry the operation. If the
problem persists, contact your system programmer.
System programmer response: Determine why the
service routine timed out. Examine the NetView log for
additional information.
ING277I • ING301I
ING277I
Command Handler INGRXCMJ
FAILED: RC=nn ReasonText
Explanation: The command handler of the
Automation Agent Java Framework detected an error.
The variable RC is the return code from the
command handler INGRXCMJ as described below.
The variable ReasonText is the description of the
error, as described below.
Table 5. Return Codes from INGRXCMJ (continued)
Return Code
Explanation
60
PIPE ERROR STAGE
CORRWAIT ASYNCH
TIMEOUT
74
INGEXEC error
75
PIPE error
76
At least one command
failed on the remote
system
77
Target missing
Table 4. Reason Text for Return Codes
Return Code
Reason Text
54
CMD_RC=cmd_rc
CMD=cmdshort
ERRMSG=errormsg
58
PIPE ERROR
PIPE_RC=pipe_rc
59
PIPE ERROR
STAGE=stage RC=scr
CMD=cmdshort
60
PIPE ERROR STAGE
CORRWAIT ASYNCH
TIMEOUT
nn
CMD=short command
that failed
Note: For return codes 74 to 77, see
AOF_JVM_Route_Command (AOFC0210).
System action: The command has not been executed
successfully.
Operator response: None.
System programmer response: Analyze the NetView
log and search for further error messages which may
provide more details about the reason of the error. If
rc=54, look for the description of the associated
command. If necessary, contact your IBM Contact
Support Center.
Note: For rc=1..32, message AOF356 was issued
(command handler failed).
ING300I
Table 5. Return Codes from INGRXCMJ
Explanation: A command has finished processing and
achieved what it has been asked to do, for example,
starting a resource.
Command command finished
successfully
Return Code
Explanation
0
Success
4
Invalid RPC Type
8
REXX function failed
System action: None.
12
NetView pipe failed
Operator response: None.
16
buffer.0 is wrong
System programmer response: None.
20
Route cmd failed
24
JVM stuff failed
28
INGPXRCV rc<>0
32
Remote_Command failed
(for remote target only)
52
Invalid data stream
54
CMD_RC=cmd_rc
CMD=cmdshort
ERRMSG=errormsg
58
PIPE ERROR
PIPE_RC=pipe_rc
System action: None.
PIPE ERROR
STAGE=stage RC=src
CMD=cmdshort
System programmer response: None.
59
The variable command is the command being
executed.
ING301I
Command command failed - unexpected
results after waiting for hh:mm:ss
Explanation: A command has finished processing but
has not achieved what it has been asked to do. For
example, when starting a resource, the resource is not
in the expected state after the allowed time period.
The variable command is the command being
executed.
The variable hh:mm:ss is the timer period.
Operator response: None.
Chapter 10. Messages ING001I to INGY1337I
261
ING302I • ING311I
ING302I
Nothing to cancel
Explanation: No request exists for the specified
resource that originated from the same source.
System action: None.
Operator response: None.
System programmer response: None.
ING308A
Waiting for termination of name
Explanation: System automation is in the middle of
shutting down the system and is waiting for the
termination of the named component / address space.
The termination process is on halt till the named
component becomes inactive.
Variable name identifies the name of the system.
System action: Processing continues.
ING304I
Waiting for termination of name aborted
- reason
Explanation: System Automation for z/OS was
waiting for the termination of the name component, but
the termination command was aborted.
Variable name is the name of component.
Variable reason explains why the termination
command was aborted.
System action: Processing continues.
Operator response: None.
System programmer response: If the component is
OMVS, consider adding command F
BPXOINIT,SHUTDOWN=FORKINIT command as
SHUTINIT command for JES in the policy.
ING305I
System shutdown started for name
Explanation: Indicates that the termination of the
system has been started. The shutdown was either
requested by the local operator, GDPS® or the
Active/Active controller.
Variable name identifies the name of the system.
System action: Processing continues.
System programmer response: None required.
Operator response: Stop the named component /
address space.
System programmer response: None required.
ING309I
System shutdown for name redirected
due to GDPS Tower,
STOPAPPL=resource
Explanation: A system shutdown was requested by
means of the INGREQ ALL command. Since the system
is under control of GDPS, only the toplevel resource
identified by means of the GDPS STOPAPPL parameter
in the GEOPLEX OPTIONS member is terminated.
Variable name identifies the name of the system.
Variable resource identifies the GDPS STOPAPPL
resource.
System action: Processing continues.
Operator response: None.
System programmer response: None required.
ING310I
data
Explanation: This message is used to transport the
completion block from the system being terminated
back to the Active/Active Controller.
System action: Processing continues.
ING306I
System shutdown nearly complete for
name
Explanation: Indicates that the shutdown of the names
system is nearly finished. Only NetView is still active.
Variable name identifies the name of the system.
System action: Processing continues.
System programmer response: None required.
ING307I
System shutdown for name already in
progress
Explanation: Indicates that System Automation for
z/OS is already working on shutting down the named
system.
System action: Processing continues.
System programmer response: None required.
262
System Automation for z/OS Messages and Codes:
System programmer response: None.
ING311I
Workload name not defined in the SA
policy
Explanation: The Active/Active controller has
requested either to Start, Stop a workload or to query
the status of the workload, but the workload is not
defined in the System Automation for z/OS policy.
Workload must be defined in the GDPS_WORKLOAD
policy under the MVS component.
Variable name identifies the workload.
System action: Processing continues.
System programmer response: Define the workload in
the System Automation for z/OS policy, if necessary.
ING312I • ING323I
ING312I
action of Workload name failed.
Explanation: The Active/Active controller has
requested either to Start or Stop a workload, but this
failed. See the NetView log for more details about the
failure when the workload is managed by System
Automation for z/OS or the system log otherwise.
Variable action identifies the action being performed
(START or STOP).
Variable name identifies the workload.
System action: Processing continues.
System programmer response: None.
|
|
ING313I
|
|
|
|
|
|
|
|
|
Explanation: IPL completed within the expected time
period. This means all required resources have reached
one of the specified statuses. The specified statuses are
shown in DISPSYS. This message will only be reported
on the console.
|
System action: None.
|
Operator response: None.
|
System programmer response: None.
|
|
ING314I
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Explanation: IPL did not complete within the
maximum time limit. This means not all required
resources have reached one of the specified statuses.
The specified statuses are shown in DISPSYS. The
failing resources are appended to the above message
test. This message will only be reported on the console.
|
System action: None.
|
|
|
Operator response: Check the failing resources and
correct the problem(s) which are blocking the resources
to reach one of the specified statuses.
|
System programmer response: None.
time: IPL completed within expected
time period, elapsed time was duration
Variable time shows the time when this message
was generated.
Variable duration shows the time it took all required
resources to reach one of the specified statuses.
time: IPL not completed within limit:
limit. Failing resources: resource
Variable time shows the time the message was
generated.
Variable limit shows the specified maximum time
limit within an IPL is considered to be completed
successfully.
Variable resource displays the names of all resources
which have not reached one of the specified
statuses.
|
|
ING315I
|
|
|
|
|
|
|
|
|
|
Explanation: IPL completed after the expected time
period. This means all required resources have finally
reached one of the specified statuses but not within the
expected time period. The specified statuses are shown
in DISPSYS. This message will only be reported on the
console.
|
System action: None.
|
Operator response: None.
|
System programmer response: None.
time: IPL completed after expected time
period, elapsed time was duration
Variable time shows the time when this message
was generated.
Variable duration shows the time it took all required
resources to reach one of the specified statuses.
ING321I
Unsupported function command found in
emulator command, Caller: caller
Explanation: The IMFEXEC command was invoked
passing a function code that is not supported by
System Automation for z/OS.
Variable emulator is the name of the command, for
example IMFEXEC or OPSCMD.
Variable command identifies the function that is not
supported by System Automation for z/OS.
Variable caller identifies the REXX script that called
the IMFEXEC command.
System action: Processing continues.
System programmer response: Modify the script
invoking the IMFEXEC command.
ING322I
emulator function commands are no
longer allowed, Caller: caller
Explanation: The IMFEXEC CMD command was
called, but no longer supported in the NetView/System
Automation for z/OS environment.
Variable emulator is the name of the command, for
example IMFEXEC or OPSCMD.
Variable function identifies the function.
Variable caller identifies the REXX script that called
the IMFEXEC command.
System action: Processing continues.
System programmer response: Modify the script
invoking the IMFEXEC command.
ING323I
emulator function does not support
parameter parameter, Caller: caller
Explanation: The IMFEXEC command was called for a
supported function, but the specified parameter is not
supported by the System Automation for z/OS
emulator.
Chapter 10. Messages ING001I to INGY1337I
263
ING325I • ING332I
Variable emulator is the name of the command, for
example IMFEXEC or OPSCMD.
ING329I
Variable function identifies the function.
Explanation: The OPSCMD was invoked to execute
the specified command.
Variable parameter identifies the parameter that is
not supported.
Variable jobname is the name of the job who
originated the OPSCMD call.
Variable caller identifies the REXX script that called
the IMFEXEC command.
Variable userid is the user id associated with the job.
Variable command is the command being used.
System action: Processing continues.
System action: The command is processed.
System programmer response: Modify the script
invoking the IMFEXEC command.
ING325I
Job=jobname User=userid issued: command
System programmer response: None.
alert-message
ING330I
Command execution was successful
Explanation: This message is used to carry the alert
text from an IMFEXEC ALERT function call
Explanation: A remote command was executed
successfully.
System action: Processing continues.
System action: The program exits.
System programmer response: None.
Operator response: None.
System programmer response: None.
ING326I
No command specified
Explanation: The OPSCMD command was invoked
but no command was specified.
ING331I
System action: Processing continues.
Explanation: A remote command execution failed due
to timeout on the remote system.
System programmer response: Modify the script
invoking the OPSCMD command.
Command execution failed. Waiting for
asynchronous timed out for output.
System action: None.
Operator response: None.
ING327I
parameter parameter value is not allowed
System programmer response: None.
Explanation: The OPSCMD command was invoked
specifying a value for a parameter that is not supported
by the System Automation for z/OS provided emulator.
ING332I
Variable parameter names the parameter.
Variable value is the value.
System action: Processing continues.
System programmer response: Modify the script
invoking the OPSCMD command.
ING328I
parameter parameter value is unknown
Explanation: The OPSCMD was invoked specifying a
system that is not known in System Automation for
z/OS.
Variable parameter is SYSID/SYSTEM.
Variable value is the name of the system that is
unknown.
System action: Processing continues.
System programmer response: Modify the script
invoking the OPSCMD command.
Command execution failed. RC=rc
SYSTEM=sys Command=cmd
REASON:xxxx
|
Explanation:
|
|
|
|
The execution of a remote command failed with return
code rc on the System Automation Agent on system sys.
Additional error description xxxx might be available
and describes the reason for the error.
|
|
|
|
|
|
This message may be accompanied with the REXX
error messages IRX0045I and IRX0040I. For example,
|
|
|
|
|
In this case, note that a REXX error is forced
deliberately resulting in IRX0045I and IRX0040I, in
order to stop processing the function INGRCVAL. The
real reason of the error was detected earlier in failing
command cmd and is described in reason text xxxx.
IRX0045I Error running INGRCVAL, line 318:
No data specified on function RETURN
IRX0040I Error running TESTPGM, line 36:
Incorrect call to routine
System action: The function or command terminated.
Operator response: None.
System programmer response: Analyze the netlog
264
System Automation for z/OS Messages and Codes:
ING333I • ING338I
and search for further error messages. See explanation
of error message ING338I.
ING333I
System action: The receiver terminates.
Operator response: None.
System programmer response: None.
Receiver is starting for PPI=xxx
Explanation: The RPC receiver with PPI receiver id
xxx is starting.
ING337I
Explanation: These messages are output of the
command 'INGRCRCV QUERY' and display all receiver
PPI ids started via command 'INGRCRCV START'. The
following example displays a list of two PPI receivers.
One is running in a VOST.
System action: The receiver is ready to receive remote
command.
Operator response: None.
System programmer response: None.
ING334I
ING337I PPI RECEIVER STATUS LIST
STATUS PPI
TASK
VOST
------ -------- -------- -------ACTIVE INGRCRCV DSI#0020 EMURCV2
ACTIVE PPIABC BDOW
Receiver is already running for PPI=xxx
Explanation: The RPC receiver with PPI receiver id
xxx is already running.
System action: None.
System action: The receiver terminates.
Operator response: None.
Operator response: Specify a different PPI receiver id
if you want to start a new receiver.
System programmer response: None.
System programmer response: None.
ING335I
Execute remote command on behalf of
JOBID=xxx CLIST=yyy COMMAND:
cmd
Explanation: A remote command is executed on
behalf of a RPC issued by job id xxx and clist yyy. The
cmd command should be executed on the System
Automation for z/OS/NetView Agent.
System action: None.
PPI RECEIVER STATUS LIST
Function or command xxxx failed,
RC=nn REASON=yyyy
ING338I
|
Explanation:
|
|
|
A function or a command with name xxxx failed with
return code nn. Additional error description is given in
yyyy.
|
|
It might be that an error has occurred in the past while
initializing the RDS environment.
|
For explanation of return code nn see the table below.
Operator response: None.
System action: Processing terminates.
System programmer response: None.
Operator response: Notify your system programmer.
ING336I
System programmer response: Determine why the
function or command failed. Examine the netlog. If
necessary, contact your IBM Support Center.
Receiver PPI=xxx will be stopped due to
operator request
Explanation: The RPC receiver with PPI receiver id
xxx is stopping due to operator request. A
stop-command has been received and issued by
'INGRCRCV STOP PPI=xxx'
Use Table 6 to determine the return codes used in
message ING338I:
Table 6. Return Codes of ING338I
Module Name
ReturnCode and Description
INGRCVAF
204
205
206
207
208
212
216
Invalid name mask
Invalid name mask, stem contains either + or *
Invalid parmlist
Invalid name mask, length of stem>8
Invalid action
Unsupported action
Error in helper function, for example, INGPCGLB or INGPCREX
Chapter 10. Messages ING001I to INGY1337I
265
ING338I
Table 6. Return Codes of ING338I (continued)
Module Name
ReturnCode and Description
INGRCVAL
200
204
205
208
212
216
218
220
224
236
Invalid call to routine
Invalid input name
Invalid old value for action=A
Invalid action
Unsupported action
Error in helper function, for example, INGPCGLB
Error when global variable not exist for action=O
Function aborted
Syntax error in subroutine(procedure)
EMULATOR INIT STATUS is not OK
INGRCVAX
0
OK
2
RPC timeout
4..24 RPC error
60 Invalid SOURCE name
104 Decode data items error
108 Expected at least 1 data item
112 Expected at least 1 data item
114 service routine failed, for example, INGPCREX
116 Host not supported
200 Execution of remote command failed
Return code from remote command is unknown or invalid
200 Execution of remote command failed
+nnn nnn is the remote return code from INGRCVAC or from
INGRCVAL, for example, 404 means invalid input INGRCVAL
266
System Automation for z/OS Messages and Codes:
ING338I
Table 6. Return Codes of ING338I (continued)
Module Name
ReturnCode and Description
INGRCVAC
0 OK
2 Mandatory parms missing
4 Error in AOF_PPI_PARSE_DATA
8 Error parsing DataItems
12 Error parsing parmlist
15 Error sending data, PIPE PPI error
16 Error sending data, PIPE error
20 INGRCVAL failed
21 INGPCGLB failed
22 INGRCVAF failed
23 INGRCVAL failed for POOLIST
24 Unexpected error
28 Standard Safe not supported for action
34 Triggering message missing
36 ARCHIVE failed because RESTORE not OK
1nn ARCHIVE failed
2nn INGRCVAL failed (remote command only)
3nn RESTORE failed
where the return codes nn have the following meaning
4 PUT init-rec failed
8 2nd OPEN failed
10 DEL failed
12 GET failed
14 GET KEYS failed
15 RESTORE VSAM failed
16 PUT failed
18 INQUIRE failed
19 Cannot retrieve output value
20 VSAM DEL for LOOKUP failed
21 PIPE EDIT for LOOKUP failed
22 PIPE LOOKUP failed
31 ARCHIVE_VSAM failed, mdfy.0 not equal mdfyval.0
32 ARCHIVE_VSAM failed, ref.0 not equal refval.0
33 ref. or refval. are not initialized by INGPCGLB
34 INGPCGLB(QUERY) failed
35 INGPCGLB(UPD_OR_APP) failed
See also message ING344I for possible VSAM IO error description.
INGRCRPC
0 OK
2 TIMEOUT
4 Missing Input
8 INGPCREX call failed
9 INGPCSTK call failed
10 Decoding response data items failed (stem)
16 PPI error
20 REXX error such as Syntax, Novalue, and so on
24 Invalid data buffer
28 AOCT0000.REXMAC initialization failed
32 Error while preparing input stem
Chapter 10. Messages ING001I to INGY1337I
267
ING338I
Table 6. Return Codes of ING338I (continued)
Module Name
ReturnCode and Description
INGRCRCV
0 OK
4 Invalid action
8 RECEIVER already active
12 PPI error
16 PIPE error
20 Invalid parameter list
24 Service failed
28 Auto OPS environment checking failed
40 Initialization failed
|
|
|
|
|
|
|
INGRCMDH
0 OK
4 Not a RPC
8 Invalid RPC input data
15 Sending response via PPI failed.
This might be the case due to timeout condition.
16 Command execution failed
INRCEXC
0
1
2
4
8
OK
Routing the command failed
Executing the command failed on THIS task
Bad input arguments
AOF_PPI_PARSE_DATA failed
INGRCCSA
201
202
203
204
205
206
207
208
212
216
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Memory object name exist already
Init of lookup table failed
Invalid object name too long (max 12 char)
Invalid object name
Invalid size, not a number
Invalid parmlist
Invalid trace parameters
Invalid action
Unsupported action
Error in function INGPCCSA
INGRCRDX
2 INGRCRPC timeout
4..24 INGRCRPC error
104 Decode data items error
108 Expected at least 1 data item
112 Unexpected remote message
116 Host not supported
117 RDS working dataset not configured in CSA
118 Must be called as command
120 Service routine failed
122 Incomplete installation detected for SA TSO REXX
200 Execution of remote command failed
Return code from remote command is unknown or invalid
+nnn nnn is the remote return code from INGRCVAC
or from INGRCVAL, for example 404 means invalid input INGRCVAL
268
System Automation for z/OS Messages and Codes:
ING338I
Table 6. Return Codes of ING338I (continued)
Module Name
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ReturnCode and Description
INGRCRDS
nnn<200 Error due to underlying services
201 VALUE missing or invalid
202 Mandatory parms missing
203 Table name missing or invalid
204 Error in AOF_PPI_PARSE_DATA
205 COLUMNS missing or invalid
206 Invalid parameter value
208 Error parsing DataItems
212 Error parsing parmlist
215 Error sending data, PIPE PPI error
216 Error sending data, PIPE error
220 No match, nothing updated or deleted
221 INGPCGLB failed
222 INGRCVAL syntax error
223 Invalid action
224 DEQ failed
225 Export to Dataset failed
226 Import to Dataset failed
227 Cannot determine data format from DSN
229 ARCHIVE table name pre-validation failed
230 INGRCREX (PUT) failed
231 INGRCREX (GET) failed
232 PUT/GET sequence violation
233 Invalid environment.
Must be called from REXX environment and must not be called from a PIPE stage.
Chapter 10. Messages ING001I to INGY1337I
269
ING339I
Table 6. Return Codes of ING338I (continued)
Module Name
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INGRCRDS
underlying service
ING339I
ReturnCode and Description
CreateTableControl:
1 Two words required or comma missing, for example, 'NAME Char(30)'
2 NOT numeric, for example, 'NAME Char(3x)'
3 Unsupported data type, for example, 'YEAR Integer'
4 Zero columns, at least one column is required
5 Table name too long (>30 characters)
6 Max row length exceeds implementation limit 32000
7 Invalid column name
CreateTableRow:
11 Truncated at least one column
12 Unequal number of column names/values
13 Max length of a row is exceeded
UpdateTableRow:
InsertTable:
21 Invalid column name
ReadTextTableData/Header
31 bad column delimiter
35 bad import header
CreateTable:
100 Table exist already
UpdateTableControl:
101 Table does not exist
ModifyTableControl:
102 Table LOCK does not match
IterateTable:
InsertTable:
104 Table does not exist
105 Bad validation of TCR(corrupted row)
106 Row does not exist (dir.i)
IterateTable:
110 Error, no COLUMN match
115 Error WHERE/SET clause parser
116 Error match where clause (Syntax error !?)
117 Error parse or update
118 Error copy table data
CreateTable:
InsertTable:
GlobalDatastore:
120 INGRCVAL failed, see GlobalDatastore(vn,'U')
ListOfTables:
ListOfPools:
130 INGPCGLB(QUERY_ACL) failed
131 INGPCGLB(QUERY_ACL) returns no hexdata
Parser WHERE/SET:
41,42 parsing error, unmatched brackets (TokenizeWhereClause)
43 unsupported operator (TokenizeWhereClause)
44 parsing error, tokenizer failed (ParseValueClause)
46 parsing error, unmatched brackets (Tokenizer)
48,49 parsing error, column name not found (ResolveColumnsinWhereClause)
52 parsing error, invalid operator (ParseSetClause)
56 bad expression in match clause (SYNTAX, NOVALUE)
Receiver PPI=xxx recovers bad command
execution, continue...
Explanation: The RPC receiver with PPI receiver id
270
System Automation for z/OS Messages and Codes:
xxx executed a remote command which failed.
However, the receiver continues processing and waits
for the next command.
ING340I • ING345I
System action: Execution of the current command
terminates. Receiver continues.
Operator response: Notify your system programmer.
System programmer response: Determine why the
remote command failed. Examine the netlog.
ING340I
Deleted n1 of n2 pattern matching
global symbols
Explanation: The function INGRCVAF has filtered n1
number of global variables. n2 global variables have
been deleted. If n2 is smaller than n1 then either the
global variable cannot be found or an error occurred.
System action: As many global variables have been
deleted as possible.
Operator response: None.
System programmer response: None.
ING341I
Receiver PPI=xxx has been stopped
Explanation: The RPC receiver with PPI receiver id
xxx has been stopped.
System action: The receiver terminates.
Operator response: None.
System programmer response: None.
ING342I
No receivers are started
Explanation: Command 'INGRCRCV QUERY' does
not find any receivers that were started.
|
ING344I
|
|
|
|
Explanation: This message is used by command
INGVALUE in order to report an error, while
performing an archive/restore operation. This message
might be trapped by the automation table.
|
|
|
Token 3 of the message is the subsystem job name,
token 5 the subcommand that failed and token 6 the
kind of error. For example, VSAM_IO_ERROR.
|
|
You can use this message to set the resource
RDSARCH, for example, to status abending.
|
The error_text might be one of the following:
|
|
|
ARCHIVE VSAM_IO_ERROR DSIVSMXV reason
Reason will be the error message provided by
the failing NetView service.
|
|
|
ARCHIVE VSAM_IO_ERROR INGRCVSM RC=nn
The number is nn is the return code from
INGRCVSM.
|
|
|
ARCHIVE ERROR 36
During SA initialization INGRDS was not
initialized.
|
|
|
|
ARCHIVE ERROR 1nn - reason
Any other error during archiving RDS or other
long global variables occurred. The reason
describes the error code nn.
|
|
|
|
RESTORE ERROR 3nn - reason
Any other error during restoring RDS or other
long global variables occurred. The reason
describes the error code nn.
JOB job_name FAILED: error_text
|
System action: The originating command terminated.
System action: None.
|
Operator response: None.
System action: None.
|
System programmer response:
Operator response: None.
|
|
|
|
Determine why the function or command failed.
Examine the netlog. You might want to check for the
message ING388I that provides additional information
about the module that causes the error.
ING343I
Parameter xxxx is not supported by
function or command yyyy
Explanation: The function or command yyyy was
invoked passing a parameter that is not supported by
System Automation for z/OS.
ING345I
Explanation: Command 'INGVALUE STATUS' reports
the status of the long global variable framework. This
message is also written if the command 'INGVALUE
RESTORE' was successful.
Variable xxxx identifies the parameter that is not
supported by System Automation for z/OS.
Variable yyyy is the name of the command that
detected the error.
System action: Processing continues.
System programmer response: Modify the script
invoking the command.
Status of long global variables: xxx
xxx might have the following values:
|
|
|
|
|
|
|
|
v RESTORE SUCCESSFUL - Persistent long global
variables were restored successfully.
v INITIAL RESTORE NOT DONE - Initialization of
persistent long global variables was not done during
initialization of System Automation for z/OS.
v INITIAL RESTORE FAILED - Initialization of
persistent long global variables failed during System
Automation for z/OS initialization.
System action: None.
Chapter 10. Messages ING001I to INGY1337I
271
ING346I • ING360I
v The variable xxx is the name of the operator function
array.
Operator response: None.
System programmer response: Determine why the
function or command failed. Examine the netlog if the
status is not successful.
ING346I
System action: Receiver continues.
Operator response: Notify your system programmer.
System programmer response: Check why not all
operator tasks are inactive.
Abort function xxx on purpose at LINE
nn
Explanation: The REXX function xxx detected an error
at line nn. The purpose is that the error causes invalid
call to routine. This can only be achieved by
returning nothing on purpose. See example:
ING350I
Explanation: During initialization SA z/OS detected
an improper definition for the Job Log Monitoring task.
ING338I Function or command INGRCVAL failed,
RC=204 REASON=invalid character found
ING346I Abort function INGRCVAL on purpose at LINE 83
270 +++ return
IRX0045I Error running INGRCVAL, line 270:
No data specified on function RETURN
v The variable name shows the subsystem name that is
affected.
v The variable rsn shows the reason:
System action: The function or command terminated.
Operator response: None.
System programmer response: Analyse the netlog and
search for further error messages. See explanation of
error message ING338I.
Note: Ignore the error the IRX0045I, since No data
specified on function RETURN was done on purpose.
The real reason was detected earlier in the failing
program which caused message ING346I.
ING347I
Improper Job Log Monitoring
definitions detected for name, RSN=rsn
Receiver PPI=id does not start due to an
unsupported environment for xxx
Explanation: The receiver task was started by
command 'INGRCRCV START OPF=xxx'. The receiver
searches for the existence of the automation operator
task (for example, if xxx is AOFCMDOPER then the
tasks are AOFCMDnn, nn=00,01,02,..) but no active task
was found.
10
Job Log Monitoring interval defined but no
message id.
11
Offset specification is invalid.
12
Token specification is invalid.
13
Message id defined even if JOBLOGALL has
been specified.
14
Message offset is 0 but no token has been
defined.
15
Token has been defined but no message
offset.
16
Monitoring interval is invalid.
17
DD name specification is invalid.
18
Message id is invalid.
System action: The definition is ignored.
System action: Receiver terminates.
Operator response: Correct the definition and refresh
the configuration if desired.
Operator response: Notify your system programmer.
System programmer response: None.
System programmer response: Check if the operator
tasks are defined or why they are inactive.
ING348I
Receiver PPI=id starts with a degraded
operator function array mm of nn for
xxx.
Explanation: The receiver task was started by
command 'INGRCRCV START OPF=xxx'. The receiver
searches for the existence of the automation operator
task (for example, AOFEMUnn, nn=00,01,02,...) but
found at least one task that was inactive or not defined.
The receiver task continues running but executing
incoming commands might be degraded because the
inactive tasks are skipped, and commands might be
queued.
v The number mm is the number of active tasks
v The number nn is the number of defined tasks
272
System Automation for z/OS Messages and Codes:
|
|
ING360I
|
|
|
|
Explanation: System Automation security checking
fails such that not one of the other security messages
can be issued any more. The reason_text explains the
error.
|
|
System action: System Automation does not grant
access.
|
Operator response: None.
|
|
|
|
System programmer response: The reason_text may
help you determine the reason for the error. If an
internal API error occurred switch on trace and rerun
the command.
Security check failed RC=nn Reason:
reason_text
ING361I • ING402I
|
ING361I
|
|
|
|
Explanation: System Automation security checking for
one or more resources failed. In the NETLOG this is a
multiline message with additional ING362 message
lines.
|
|
System action: The System Automation command is
not carried out.
|
|
|
|
Operator response: Check the NETLOG for more
information, especially the ING362 message lines or
messages issued by SAF product. Request access to the
listed resource and try the command again.
|
System programmer response: None.
|
|
ING362I
|
|
|
|
|
|
Explanation: System Automation checking for the
specified resources failed. This message denotes the
resource profile, the access authority requested and the
userid for which the check was done. It further shows
the return code of the service called to perform the
check.
|
|
System action: The System Automation command is
not carried out.
|
|
|
|
|
Operator response: Check the NETLOG for messages
issued by the SAF product. If the return code is 4 the
SECOPTS.SARESAUT is set to ON.FAIL and no profile
exists. If the return code is 8 you do not have the
required access rights.
|
System programmer response: None.
|
|
ING365I
|
|
|
|
|
Explanation: A System Automation command tries to
access an agent on a remote system. SAF check failed
for the following profile within class SYSAUTO:
|
|
System action: The System Automation command is
not sent to the remote system.
|
Operator response: None.
|
|
|
|
|
|
System programmer response: Check if the user of
the System Automation command is allowed to execute
the command on a remote system. Give the user READ
permission to the corresponding SAF profile. There
might be additional SAF messages such as ICH408I for
additional information.
|
|
ING366I
|
|
|
Explanation: A command received from outside
NetView (for example, via PPI) is rejected for
execution. SAF checking against following profile
Security check for resource(s) failed.
profile=profile access=access userid=userid
rc=rc
Security check for target domain
targetdomid failed.
AGT.sysplex.xcfgrp.TARGET.FROMDOM.domain.TODOM.
targetdomid
System Automation third party security
check failed: reason_text
|
within class NETCMDS failed: netid.domid.command
|
|
|
|
|
|
|
The reason_text provides more detail:
|
|
System action: System Automation does not grant
access.
|
Operator response: None.
|
|
|
|
System programmer response: The reason_text may
help you to determine the reason for the error. There
might be additional SAF messages such as ICH408I for
additional information.
Access denied for USER=user CLASS=NETCMDS
PROFILE=xxxx. In this case, grant the user access to
the specified profile.
Profile not defined PROFILE=xxxx in CLASS=NETCMDS.
In this case, define the specified profile in
NETCMDS.
ING400I
BCPM Work order work_order is created
on BCPM server server, system system.
Explanation: This message displays the identifier of a
work order created in the Business Continuity Process
Manager (BCPM) as the result of an outage event on
the system.
System action: None.
Operator response: None.
System programmer response: None.
ING401E
Unable to create BCPM Work order.
Return code return_code from BCPM
server server, system system.
Explanation: An outage event from the system cannot
be delivered or processed by the Business Continuity
Process Manager (BCPM) server.
System action: None.
Operator response: Inform the IT Service Continuity
administrator about the outage.
System programmer response: Refer to the netlog for
additional messages issued by the SA z/OS INGOMX
command.
ING402I
BCPM server server is notified about
completion of task task with code code,
system system.
Explanation: The task triggered by the Business
Continuity Process Manager (BCPM) has completed.
BCPM has received and processed the task completion
information.
System action: None.
Operator response: None.
System programmer response: None.
Chapter 10. Messages ING001I to INGY1337I
273
ING403E • ING502I
ING403E
Unable to notify BCPM server server
about completion of task task with code
code, system system. INGOMX command
has returned error_code.
Explanation: The task triggered by the Business
Continuity Process Manager (BCPM) has completed,
but the BCPM cannot receive the task completion
information. The INGOMX command ended with an
error.
System action: None.
Operator response: Inform the IT Service Continuity
administrator about the problem.
System programmer response: Refer to the netlog for
additional messages issued by the INGOMX command.
Check for the reason for the INGOMX error.
ING404E
BCPM server server cannot process
notification from task task. BCPM
exception is exception_code.
Explanation: The task triggered by the Business
Continuity Process Manager (BCPM) has completed,
but the BCPM cannot process the task completion
information.
System action: None.
Operator response: Inform the IT Service Continuity
administrator about the problem.
System programmer response: None.
ING405I
BCPM replied to the WTOR wtor with
ID reply_id with reply on system system.
Explanation: The outstanding WTOR was reprocessed
by the Business Continuity Process Manager (BCPM).
System action: A process requested WTOR is
continued.
ING407E
BCPM unable to execute GDPS batch
script batch_script. Return code rc, reason
reason.
Explanation: The GDPS batch script was triggered by
the Business Continuity Process Manager (BCPM), but
cannot be executed.
System action: The script is not executed.
Operator response: Inform the IT Service Continuity
administrator about the problem.
System programmer response: Refer to the netlog for
additional messages issued by GDPS.
ING408I
BCPM command command ended with
rc=rc.
Explanation: The command triggered by the Business
Continuity Process Manager (BCPM) has completed.
System action: None.
Operator response: None.
System programmer response: None.
ING500I
error_text
Explanation: A program that has failed has produced
this additional information regarding the error. See
preceding messages.
System action: Execution probably halts. See
subsequent messages.
Operator response: Contact your system programmer.
System programmer response: Assist the operator.
Contact your IBM Support Center.
ING501I
debug_text
Operator response: None.
Explanation: This is a generic informational message
that shows the flow within the function.
System programmer response: None.
System action: Execution continues.
Operator response: None.
ING406E
BCPM unable to reply to the WTOR
wtor with reply on system system. RC=rc.
System programmer response: None.
Explanation: The outstanding WTOR is either no
longer active and has already been reprocessed by an
operator or automation product, or it cannot be
reprocessed by the Business Continuity Process
Manager (BCPM).
ING502I
System action: None.
System action: Execution continues.
Operator response: Check for outstanding WTORs on
the system. Inform the Service Continuity Team about
the problem.
Operator response: None.
System programmer response: None.
274
System Automation for z/OS Messages and Codes:
SA z/OS Discovery Library Adapter
started date time
Explanation: This indicates the time that the SA z/OS
DLA started execution.
System programmer response: None.
ING503I • ING512I
ING503I
SA z/OS Discovery Library Adapter
completed date time, RC=nn
Explanation: This indicates the time that the SA z/OS
DLA completed execution.
System action: Execution finishes.
|
|
Operator response: If RC=0 the output file is now
ready to be downloaded.
System programmer response: None.
ING504I
Checksum data updated
Explanation: Following a successful run, the checksum
data (member @CHCKSUM) stored in the output data
set has been updated.
System action: Execution continues.
Operator response: None.
to preserve discovery date and time information in the
previously generated book.
The variable book identifies the book.
System action: Execution continues.
Operator response: None.
System programmer response: None.
ING509I
Data set name is not a partitioned data
set
Explanation: The specified output data set is not a
partitioned data set.
The variable name identifies the data set.
System action: None.
Operator response: Correct the name of the data set
and reissue the command.
System programmer response: None.
System programmer response: None.
ING510I
ING505I
Checksum data cleared; bad run
Explanation: The SA z/OS DLA has failed during its
execution and, because it has not been able to generate
a valid output book, it has cleared the checksum data.
System action: Execution continues.
Operator response: Analyze the problem and, when
fixed, rerun the SA z/OS DLA to generate a valid
book.
System programmer response: Assist the operator.
ING507I
Data in dataset_name truncated; Increase
output LRECL
Explanation: This indicates that the SA z/OS DLA
tried to write a line to the output data set that was
longer than the data set's LRECL.
The variable dataset_name identifies the fully
qualified name of the data set.
System action: The book is generated with the
truncated line. Depending on the nature of the
truncated data, the iDML book that is generated may
or may not be valid.
Operator response: Reallocate the data set with a
longer LRECL and rerun the SA z/OS DLA.
System programmer response: Assist the operator.
ING508I
Output of book book skipped; checksum
matches
Explanation: The SA z/OS DLA has successfully
executed, however the contents of the generated book
are the same as the previously generated book in the
same output data set. Generation of a book from the
newly generated data is therefore suppressed in order
program Directory OPEN failed for
DDName ddname, RC rc
Explanation: The program was unable to open the
directory for the data set that is pointed to by the
ddname. The OPEN macro gave the specified return
code.
System action: Execution probably halts. See
subsequent messages.
Operator response: The output data set must be a
PDS—you cannot use a sequential file. Contact your
system programmer.
System programmer response: Assist the operator.
Contact your IBM Support Center.
ING511I
program Directory READ failed for
DDName ddname, RC rc RS rsn
Explanation: The program tried to read the directory
for the data set that is pointed to by the ddname, but
received the unexpected return and reason codes
indicated.
System action: Execution probably halts. See
subsequent messages.
Operator response: The output data set must be a
PDS—you cannot use a sequential file. Contact your
system programmer.
System programmer response: Assist the operator.
Contact your IBM Support Center.
ING512I
program STORAGE macro call failed for
type type, RC rc
Explanation: The program received an unexpected
return code from a call to the STORAGE macro for the
type of storage that was requested.
Chapter 10. Messages ING001I to INGY1337I
275
ING513I • ING526I
System action: Execution probably halts. See
subsequent messages.
Operator response: Contact your system programmer.
System programmer response: There may be other
messages in the netlog or syslog at the time of the
incident that will give more details. If NetView is not
running REGION=0M, try increasing its region size.
Contact your IBM Support Center.
ING513I
program Codepage Translation Routine
CUNLCNV returned RC rc, RS rsn
Explanation: The program called the CUNLCNV
routine and received an unexpected return and reason
code.
System action: Execution probably halts. See
subsequent messages.
Operator response: Contact your system programmer.
System programmer response: Contact your IBM
Support Center.
| ING520I
|
REQUEST request WAS SUCCESSFUL
FOR function
| Explanation: The specified request for the specified
| record completed successfully.
|
The variable request identifies the request.
|
The variable function identifies the function.
| ING521I
|
REQUEST request was UNSUCCESSFUL
FOR function
| Explanation: The specified request for the specified
| function failed to process.
|
The variable request identifies the request.
|
The variable function identifies the function.
| ING522I
| Operator response: Issue the command again using
| the correct number of parameters.
INVALID DELIMITER OF delimiter
ENCOUNTERED
| Explanation: You entered the specified delimiter, but
| the delimiter is not correct for the INGPW command.
|
The variable delimiter identifies the incorrect
|
delimiter.
| Operator response: Issue the command again using
| the correct syntax.
276
ING524I
|
|
|
|
|
Explanation: INGPW issued a VSAM function and
received an error while processing a request.
|
|
System action: The INGPW command fails and does
not perform its function.
|
Operator response: Notify your system programmer.
|
|
|
|
|
System programmer response: Browse the NETLOG
for the specific VSAM error message that signalled the
error. Refer to the VSAM reference manuals to correct
the error. If the error persists, contact IBM Software
Support.
|
|
ING525I
|
|
|
|
|
|
Explanation: The specified parameter that must be
passed to the specified command is incorrect.
|
|
System action: The command fails and does not
perform its function.
|
|
|
|
|
|
Operator response: If the message appears on an
operator panel, correct the parameter and re-enter the
command. If necessary, view the help for the INGPW
command to assist in entering a valid command. If the
message appears in the NETLOG, notify your system
programmer.
|
|
|
System programmer response: Perform the problem
determination function on the command. Find the error
in the NETLOG and contact IBM Software Support.
|
|
ING526I
|
|
|
|
|
|
Explanation: The specified parameter that must be
passed to the specified command is missing.
|
|
System action: The command fails and does not
perform its function.
|
|
|
|
|
|
Operator response: If the message appears on an
operator panel, correct the input and re-enter the
command. If necessary, view the help for the INGPW
command to assist in entering a valid command. If the
message appears in the NETLOG, notify your system
programmer.
request ERROR PROCESSING VSAM
DATASET
The variable request identifies the name of the
VSAM macro request that was processing when the
error occurred.
PARAMETER parameter INVALID for
REQUEST command
The variable parameter identifies the incorrect
parameter.
The variable command identifies the name of the
command.
TOO FEW PARAMETERS SPECIFIED
| Explanation: You did not enter the minimum number
| of parameters required for the operand used for the
| INGPW command.
| ING523I
|
|
|
System Automation for z/OS Messages and Codes:
EXPECTED PARAMETERS MISSING
FOR REQUEST command – request
The variable command identifies the incorrect
command.
The variable request identifies the name of the
request.
ING527I • ING534I
|
|
|
System programmer response: Perform the problem
determination function on the command. Find the error
in the NETLOG and contact IBM Software Support.
|
|
|
ING527I
|
|
|
|
|
|
|
|
Explanation: The parameter that must be passed to
the specified command is incorrect.
The variable value identifies the value of the
parameter that is incorrect.
||
|
|
|
|
|
|
|
|
Explanation: The command fails and does not
perform its function.
|
|
|
|
|
|
|
|
Operator response: If the message appears on an
operator panel, correct the input and re-enter the
command. If necessary, view the help for the INGPW
command to assist in entering a valid command. If the
message appears in the NETLOG, notify your system
programmer.
Explanation: You specified a new password with an
incorrect length on the INGPW command. Passwords
must be a minimum of 4 characters and a maximum of
20 characters.
|
|
|
System programmer response: Perform the problem
determination function on the command. Find the error
in the NETLOG and contact IBM Software Support.
|
|
|
|
|
|
|
|
System action: The INGPW command fails.
|
|
Operator response: Reissue the command with a new
password of the correct length.
|
|
ING532I
|
|
Explanation: The password data set is not allocated in
the Product Job Control Language (JCL).
|
Operator response: Notify your system programmer.
|
|
|
System programmer response: Add an INGPSWD DD
statement to the procedure to allocate the VSAM data
set.
The variable operator identifies the NetView
Operator attempting to execute the INGPW request.
|
|
ING533I
The variable request identifies the attempted INGPW
operation.
|
|
Explanation: INGPW cannot open the INGPSWD DD
password data set.
|
Operator response: Notify your system programmer.
|
|
|
System programmer response: Ensure that the
INGPSWD DD password data set is allocated correctly
and is defined to the Product.
|
ING534I
|
|
|
|
Explanation: The information for the specified data
cannot be found.
EXPECTED PARAMETERS INVALID
FOR REQUEST command - parameter =
value
The variable command identifies the name of the
command
The variable parameter identifies the name of the
parameter
|
ING529I
|
|
Explanation: The report is the response to an INGPW
request.
|
|
Operator response: Refer to the INGPW reference
manuals for details.
|
|
ING530I
|
|
|
|
|
|
|
|
|
|
|
|
Explanation: operator is not authorized to execute
specified INGPW request. The execution of the request
is rejected.
|
System action: Processing of the INGPW request fails.
|
|
|
Operator response: Contact your system programmer
to obtain the necessary authorization to execute the
command.
|
System programmer response: Examine the SYSLOG
p1 p2 p3 p4 p5
operator NOT AUTHORIZED TO request
RECORD FOR user owner
The variable user identifies the userid of the INGPW
request for which password maintenance services
are required.
The variable owner identifies the owning entity for
which password maintenance services are required.
|
|
for ICH408I messages giving more details about the
effective ACEE and required permissions.
|
|
|
Evaluate the need the operator has for the INGPW
request. If authorization should be granted, notify the
security administrator.
|
|
|
Command INGPW requires the following permissions
to the resource ING.PW.user.owner in the class
SYSAUTO:
READ
UPDATE
CONTROL
ALTER
ING531I
for INGPW
for INGPW
for INGPW
requests
for INGPW
READ request
UPDATE request
INIT and REGEN
DELETE request
PASSWORD IS TOO length
The variable length contains the value LONG or
SHORT and explains why there are too many or too
few characters.
NETVIEW PASSWORD DATASET NOT
ALLOCATED
ERROR OPENING PASSWORD
DATASET
RECORD FOR data1 data2 NOT FOUND
The variable data1 identifies the unique data
identifer
Chapter 10. Messages ING001I to INGY1337I
277
ING535I • ING601E
|
|
|
|
|
|
|
perform cross-product logons can still use it. Browse
the NETLOG for the specific VSAM error message that
signalled the error. Refer to the VSAM reference
manuals to correct the error. If the error persists,
contact IBM Software Support.
|
|
ING538I
|
|
|
Explanation: VSAM could not update the current
password held in the INGPSWD DD password data set
to the new password because of a VSAM error.
|
Operator response: Notify your system programmer.
|
|
|
|
System programmer response: Browse the NETLOG
for the specific VSAM error message that signalled the
error. Refer to the VSAM reference manuals to correct
the error.
|
|
ING539I
| Operator response: Notify your system programmer.
| System programmer response: Ensure that the
| message is suppressed so that it does not appear in the
| log or on an operator terminal.
|
|
|
Explanation: VSAM cannot update the current
password held in the password data set to the new
password because no password has been assigned.
|
Operator response: Notify your system programmer.
|
|
|
|
System programmer response: Wait until the
password expires before issuing the UPDATE
parameter, or use the REGEN parameter to generate a
new password.
|
|
ING600I
|
|
|
|
|
|
|
Explanation: This is a multiline message that is
generated whenever the Looping Address Space
Suppression Monitor runs. It contains information
about the results of the query to OMEGAMON the
routine has made and details of any apparently looping
address spaces that are found, along with details of any
planned corrective actions.
|
|
This message only appears in the Netlog and is not
available for automation.
|
|
|
System action: The monitor runs again after the
appropriate interval, any corrective actions indicated
will be taken.
|
Operator response: None.
|
System programmer response: None.
|
Classes: None.
|
|
|
ING601E
|
|
|
Explanation: The Looping Address Space Suppression
monitor has found an address space that appears to be
in a CPU intensive loop and has been instructed to
The variable data2 identifies a second unique data
identifier.
|
|
|
|
|
Operator response: If the data specified is a user ID
and an owner ID, notify your system programmer. If
the data specified relates to another function, modify
any filter settings that are in effect. If problem persists,
notify your system programmer.
|
|
|
|
|
|
System programmer response: If the data specified is
a user ID and an owner ID, use the INIT option to
specify a password record for the user. For any other
data, browse the NETLOG for informational messages,
and ensure that the relevant function has initialized
successfully.
| ING535I
CURRENT PASSWORD IS current
| Explanation: INGPW retrieved the specified current
| password from the password data set.
|
The variable current identifies the current password.
| ING536I
|
|
|
|
|
|
|
|
CURRENT/NEW PASSWORD is
current/new
Explanation: The INGPW command randomly
generated the specified new password because the
current password was defined with an expiration date
and is expired, or new password was requested by the
INGPW REGEN command.
The variable current identifies the current password.
The variable new identifies the new password.
| Operator response: Notify your system programmer.
|
|
|
|
|
|
System programmer response: Automation Product
suppresses this message, but the routines that perform
cross-product logons can still use it. Change the
external product password for the affected user and
update the record in the password dataset using
INGPW UPDATE command, if required.
| ING537I
|
|
|
|
|
|
|
|
CURRENT PASSWORD IS password ERROR CREATING NEW PASSWORD
Explanation: This message displays the current
password. The password record was defined with an
expiration date and is expired, but the INGPW
command cannot generate and store a new one because
of a VSAM error.
The variable password identifies the current
password.
| Operator response: Notify your system programmer.
| System programmer response: The Automation
| Product suppresses this message, but the routines that
278
System Automation for z/OS Messages and Codes:
NEW PASSWORD UPDATE FAILED VSAM ERROR
NEW PASSWORD UPDATE FAILED NO NEW PASSWORD
LOOPING ADDRESS SPACE
SUPPRESSION REPORT
LOOPING ADDRESS SPACE
DETECTED: jobname stepname (ASID
asid)
ING602I • ING804I
|
|
issue a warning message. The variables identify the
address space in question.
|
|
|
|
|
System action: The monitor takes any corrective
actions specified by your policy for it. It then runs
again after the appropriate interval. At this point it may
take more actions, including issuing another warning
message.
|
|
Operator response: Investigate. Notify your system
programmer.
System action: None.
|
|
|
System programmer response: Fix the problem. If it is
a known false positive result, update your policy to
ignore it.
System programmer response: None.
|
Classes: 40 44
|
|
ING602I
|
|
|
|
Explanation: When the Looping Address Space
Suppression monitor executes a DIAG instruction it
produces a diagnostic report. The report is a multiline
message and is only available in English.
|
|
|
|
|
|
The report is generated through OMEGAMON Inspect
functionality and indicates where the instruction
pointer was within the looping address during a small
sampling window. For address spaces that are in a tight
CPU loop, this will identify the portion of the code
where the loop is present.
|
|
|
|
|
The report identifies the program, the load module
(and the job the load module is a part of, if it is not the
same one), and then gives a list of CSECTs and offsets
along with a percentage indicating how often the
looping job was detected at this portion of the code.
|
System action: Execution continues.
|
Operator response: Notify your system programmers.
|
|
|
System programmer response: Notify the people
responsible for looping the application. If it is a known
false positive result, update your policy to ignore it.
|
Classes: None
ING800I
LOOPING ADDRESS SPACE
DIAGNOSTIC REPORT
VERIFYING type-model HARDWARE
AUTOMATION INTERFACE
Explanation: A check of the type and model of the
hardware automation interface is performed.
The variable type-model shows the type and model
of the hardware being verified.
System action: The verification process for the
specified processor is starting.
ING801I
AUTOMATION INTERFACE NOT
SUPPORTING type-model HARDWARE
Explanation: Verification determined that the
processor hardware is not supported
The variable type-model shows the type and model
of the hardware.
Operator response: None.
ING802I
HARDWARE INTERFACE
COMPONENT HSAET32 CANNOT BE
ACTIVATED
Explanation: An error was reported by the HSAET32
internal command. The command that establishes and
activates the hardware interface failed.
System action: None.
Operator response: None.
System programmer response: Check the netlog or
the system log for HSAxxxx messages about the
problem.
ING803I
HARDWARE INTERFACE AUTO
OPERATOR autotask CANNOT BE
STARTED
Explanation: The named autotask failed to start. The
hardware interface cannot be used.
The variable autotask shows the autotask that could
not be started.
System action: None.
Operator response: None.
System programmer response: Check the netlog for
additional messages. Correct the problem and activate
the autotask again. This will initialize the hardware
interface.
ING804I
HARDWARE AUTOMATION
INTERFACE OF type-model PROCESSOR
VERIFIED
Explanation: The verification for the specified
processor has ended.
The variable type-model shows the type and model
of the hardware.
System action: None.
Operator response: None.
Operator response: None.
System programmer response: None.
System programmer response: None.
Chapter 10. Messages ING001I to INGY1337I
279
ING805I • ING809I
ING805I
requestor REQUESTS TO CONNECT TO
CPC cpcaddr
Explanation: The hardware interface tries to establish
a connection to the indicated processor hardware.
IBM Tivoli System Automation for z/OS Customizing and
Programming.
Module: INGRX805, INGRX810
OPERATOR opid ENDED TO WAIT
FOR SYSOPS INITIALIZATION
The variable requestor shows the originator of the
request.
ING808I
The variable cpcaddr shows the address of the CPC.
Explanation: The operator task continues to execute
the clist INGRX810 or INGRX805 after processing was
halted. Message ING807I was issued to indicate the
halt condition for the operator task.
System action: Processing continues.
Operator response: None.
The variable opid shows the name of the affected
NetView operator task.
System programmer response: None.
Module: INGRVX80
class: 40.
ING806E
Operator response: None.
COMMUNICATION WITH CPC cpcaddr
CANNOT BE ESTABLISHED
Explanation: A failure occurred while the processor
hardware was contacted through the hardware
interface.
The variable cpcaddr shows the address of the CPC
that a session could not be established with.
System action: None.
Operator response: None.
System programmer response: Check the netlog for
AOFAxxxx messages to obtain more information, for
example, the available condition and sense codes.
Correct the problem and restart the session to the CPC.
Module: INGRVX80
ING807I
OPERATOR opid IS WAITING FOR
SYSOPS INITIALIZATION TO
COMPLETE
Explanation: The operator task is currently executing
the clist INGRX810 or INGRX805 and halts processing
until the NetView common global variable AOFCOMPL
has a value of YES, which indicates that SA z/OS
SysOps initialization is complete. This halt is a
temporary condition. Processing continues once
SA z/OS SysOps is initialized. Message ING808I is
issued to indicate that the continuation of the clist
execution for the operator task.
The variable opid shows the name of the affected
NetView operator task.
System action: None.
Operator response: None.
System programmer response: In situations when
SA z/OS SysOps cannot initialize, you can use the
STOP FORCE command to end the current command
of such an operator. For more information about the
SA z/OS common global variable AOFCOMPL, see
280
System action: None.
System Automation for z/OS Messages and Codes:
System programmer response: None.
Module: INGRX805, INGRX810
ING809I
BCPII EVENT ERROR(rc) BETWEEN
CPC cpcaddr AND domain/operator.
LASTS(stime)
Explanation: A general BCPii event wait occurred. The
BCPii connection will be terminated.
The variable rc is the HwmcaWaitEvent return code
passed back from the System z API to the caller
(INGHWCOM), while waiting for event data from the
Support Element.
The variable cpcaddr is the Processor name defined as
SA-PDB/Connection Flag/CPC Name of the processor
in SNA netid.nau format. The connection flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not available.
The variable domain is the NetView domain name of
the BCPii connection.
The variable operator is the operator task name of the
event session for the affected BCPii connection.
The variable stime is the Date/Time stamp of the last
successful connection start in the format
yymmddhhmmss.
System action: The BCPii session terminates.
Operator response: None.
System programmer response: For return code
information, refer to the condition codes table in the
appendix section “Internal Transport Services
"0Bx00xxx"” on page 455 of IBM Tivoli System
Automation for z/OS Messages and Codes.
ING810I • ING813E
Module: INGCHW0E
BCPII LINK BETWEEN CPC cpcaddr
AND domain/operator RE-ESTABLISHED.
NEW LASTS(stime)
ING812I
Classes: 40
ING810I
requestor REQUESTS TO DISCONNECT
FROM CPC cpcaddr
Explanation: The hardware interface terminates the
communication with the indicated processor hardware.
The variable requestor shows the originator of the
request.
The variable cpcaddr shows the address of the CPC.
Explanation: After a BCPii event session heartbeat
failure, the BCPii connection has been successfully
restarted.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGRVX80
class: 40.
ING811I
v The variable domain is the NetView domain name of
the BCPii connection.
BCPII CONNECTION HEARTBEAT
BETWEEN CPC cpcaddr AND
domain/operator FAILED. LASTS(stime)
Explanation: For a period of 4 minutes, the Support
Element of the addressed CPC has not responded to
the BCPii heartbeat request of the operator task
running in the NetView domain. The BCPii event
connection is no longer working.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session of the affected BCPii connection.
v The variable stime is the Date/Time stamp of the
LAST successful connection start in the format
yymmddhhmmss.
System action: The BCPii connection is internally
restarted. If the restart is successful, message ING812I
is issued. If the restart fails, message ING813E is issued
with additional information.
Operator response: None.
System programmer response: None.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable stime is the Date/Time stamp of the
LAST successful connection start in the format
yymmddhhmmss. The connection start initializes the
LASTS value and is therefore prefixed with NEW.
System action: Processing continues.
Operator response: None.
System programmer response: For additional
information, refer to the event handler asynchronous
response report AOFA0998, documented in the
appendix section “Internal Transport Services
"0Bx00xxx"” on page 455 of IBM Tivoli System
Automation for z/OS Messages and Codes.
Module: INGCHW0E
Classes: 40.
ING813E
Explanation: After a BCPii event session heartbeat
failure between the targeted CPC and the operator task
of the NetView domain, the internal BCPii connection
restart failed.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. System Automation
targets its own CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
Module: INGCHW0E
Classes: 40.
BCPII CONNECTION RECOVERY
FROM domain/operator TO CPC cpcaddr
FAILED. RSN(rsncode) LASTS(stime)
Chapter 10. Messages ING001I to INGY1337I
281
ING814E • ING815I
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable rsncode is the reason code. For full
details, refer to the appendix section “Internal
Transport Services "0Bx00xxx"” on page 455 of IBM
Tivoli System Automation for z/OS Messages and Codes.
v The variable stime is the Date/Time stamp of the
LAST successful connection start in the format
yymmddhhmmss.
System action: The BCPii connection to the addressed
CPC is closed.
Operator response: Since the BCPii connections are
monitored by SA z/OS or GDPS, a start of a failing
connection is retried automatically at each defined
monitor cycle time. No further action is required. If the
heartbeat failure message ING811I was preceded by a
ING814E message, additional error cause and reason
information is available.
System programmer response: None.
Module: INGCHW0E
Classes: 40.
ING814E
BCPII CONNECTION TO
domain/operator ABORTED BY THE CPC
cpcaddr SUPPORT ELEMENT.
CAUSE(cause_type) REASON(rsn_str)
LASTS(stime)
Explanation: The CPC Support Element has sent an
'Application_Ended' event over an active BCPii
connection to indicate the communication with the
NetView domain/operator is about to end. Note that this
event message is provided only for BCPii connections
to System z10™ and newer processors.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable cause_type is the action that caused the
console application to end. Depending on the type
given, a possible console application outage time can
be predicted.
282
System Automation for z/OS Messages and Codes:
SHUTDOWN_CONSOLE
Long outage, manual intervention is required to
recover.
RESTART_APPLICATION
Medium outage of 10 - 20 minutes can be
expected until the console application is fully
operational.
RESTART_CONSOLE
Medium outage of 10 - 20 minutes can be
expected until the console device and console
application are fully operational again.
UNKNOWN
The type code in the event data is unknown.
Long outage, manual intervention may be
required to recover.
v The variable rsn_str refers to the issuer that caused
the console application to end.
USER
A logged-on SE user.
AUTOMATION
An automation application.
OTHER
Remote action such as SE reboot from an HMC.
UNKNOWN
The reason code in the event data is unknown.
v The variable stime refers to the Date/Time stamp of
the LAST successful connection start in the format
yymmddhhmmss.
System action: Processing continues.
Operator response: Use the cause_type information of
the message to determine the BCPii connection outage
time that can be expected. In case of a long outage
time, consider the SUSPEND command for the BCPii
connection.
System programmer response: None.
Module: INGCHW0E
Classes: 40.
ING815I
BCPII CONNECT FROM domain/operator
TO CPC cpacaddr RETURNED: resp
Explanation: Request to contact the CPC Support
Element of cpcaddr over the BCPii from domain/operator
returned a response of resp.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
ING816I • ING817I
.
The Connection Flag information is not
available.
.
The Connection Flag information is not
available.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable cmd is the command token of the
currently executed HW command.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable resp is:
v The variable delay is the time in seconds the
command session is given to end.
SUCCESS
SE connection established.
ERROR(rsncode)
Failure to contact the SE.
rsncode
For information about the reason code,
please refer to the appendix section
“Condition Codes” on page 445 in
“Response Messages, Error Strings,
Condition Codes” of IBM Tivoli System
Automation for z/OS Messages and Codes.
Select the table that lists the reason code
together with the error description.
System action: If the connect was successful, session
initialization continues with CPC configuration
discovery. Message ING817I will be issued when this is
complete. If the connect processing failed, no further
session initialization is done and processing stops.
When a BCPii connection monitoring interval is defined
to SA z/OS or GDPS HMC monitoring is used for
cpcaddr, the connect requests will be retried
automatically.
Operator response: None.
System programmer response: None.
v The variable operator is the operator task name of the
command session using the affected BCPii
connection.
v The variable stime is the Date/Time stamp of the
LAST successful connection start in the format
yymmddhhmmss.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGCHW0M
Classes: 40.
ING817I
Explanation: The initial discovery request from
domain/operator for configuration information of cpcaddr
ended with a response of: resp
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
Module: INGCHW0A
Classes: 40.
ING816I
BCPII AWAIT CMD SESSION
TERMINATION TO CPC cpcaddr IN
delay SECONDS: DOMAIN(domain)
OPID(operator) CMD(cmd) LASTS(stime)
Explanation: The HW event handler for CPC (cpcaddr)
session returned an error and the asynchronous session
terminates. In order to perform a save memory
cleanup, an ongoing HW command for the CPC
running in task (operator) needs to be terminated first.
Wait for (delay) seconds for normal command
termination.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection. SA z/OS targets its own
CPC.
R
BCPii connection to a remote CPC using a HMC
for routing.
BCPII DISCOVERY OF cpcaddr FOR
domain/operator RETURNED: resp
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable resp is:
SUCCESS NEW LASTS(stime)
All required CPC configuration information has
been retrieved. The BCPii connection is now
fully operational.
stime
Date/Time stamp of the LAST successful
connection start in the format
yymmddhhmmss. The connection start
initializes the LASTS value and is therefore
prefixed with NEW.
Chapter 10. Messages ING001I to INGY1337I
283
ING818I • ING819I
FFDC(ffdc_id)
Failure to retrieve the required CPC
configuration information. The BCPii session
cannot be used.
ffdc_id
The four character id string represents the
exit point from the discovery processing and
can be used by IBM to locate the failing
retrieval.
System action: Processing continues.
Operator response: None.
System programmer response: None.
Module: INGCHW0A
Classes: 40.
ING818I
BCPII LINK BETWEEN domain/operator
AND CPC cpcaddr IS NOW
TERMINATED. NEW STATUS(connstat)
OLD LASTS(stime)
Explanation: The connection to the cpcaddr has been
successfully closed from the domain/operator side.
Before applications can use the connection again, they
must restart it. If the connection was closed, because of
a session suspension, before restarting it, the session
must be resumed.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
Operator response: None.
System programmer response: None.
Module: INGCHW0C, INGCHW0D
Classes: 40.
ING819I
BCPII ROUTE domain/operator - cpcaddr
cstat LASTS(stime)
Explanation: The BCPii connection monitor,
configured for CPC cpcaddr has detected a connection
status of cstat. Note that connection monitoring can be
suppressed by specifying an interval value of 'NONE'
in the PDB processor entry for a CPC. Processors
specified in the GEOPLEX definitions of GDPS are
automatically excluded from monitoring since GDPS
provides the HMC Monitor to supervise BCPii
connections.
For the eligible CPCs, the BCPii connection monitor
starts running after the SA z/OS agent initially
activates the configured BCPii connections. The same
applies if changes in the processor definitions, affecting
the current or new BCPii connections are activated with
an ACF REFRESH or ACF COLD at SA z/OS agent
run-time.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable cpcaddr is the Processor name defined as
SA-PDB / Connection Flag / CPC Name of the
processor in SNA netid.nau format. The Connection
Flag indicates:
L
BCPii local connection, SA z/OS targets its own
CPC.
L
R
BCPii connection to a remote CPC using a HMC
for routing.
BCPii local connection. SA z/OS targets its own
CPC.
R
.
The Connection Flag information is not
available.
BCPii connection to a remote CPC using a HMC
for routing.
.
The Connection Flag information is not
available.
v The variable domain is the NetView domain name of
the BCPii connection.
v The variable operator is the operator task name of the
event session for the affected BCPii connection.
v The variable connstat is the new connection-session
status:
NOT_CONNECTED
Connection-session can be restarted again.
SUSPENDED
Connection is suspended from normal usage. It
is required to resume it first, before restarting a
BCPii session over this connection.
v The variable stime is the Date/Time stamp of the
LAST successful connection start in the format
yymmddhhmmss. Since the connection is no longer
active the LASTS is prefixed with OLD.
System action: Processing continues.
284
System Automation for z/OS Messages and Codes:
v The variable cstat is:
CONNECTED
The BCPii connection is established.
NOT_CONNECTED
No BCPii connection is active.
v The variable operator is the operator task name of the
event session for the monitored BCPii connection. If
cstat is NOT_CONNECTED the LASTS field value is
a dot.
v The variable stime is the Date/Time stamp of the
LAST successful connection Start in the format
yymmddhhmmss. If cstat is NOT_CONNECTED the
LASTS field value is a dot.
System action: If the connection status is
NOT_CONNECTED, the monitor will try to start it. If
the connection status is CONNECTED, no extra
ING820I • ING823I
processing is done. In any case, the next monitor run is
scheduled, using the configured monitor interval to set
up a NetView timer for this monitor run.
Operator response: When needed, the BCPii
connection monitoring can be stopped by using the
SA z/OS SETTIMER command dialog. Look for the
'AOFRASCD HWOPER01 INGRX830 1' cmd string and
perform the delete action of the associated TIMER-ID in
the dialog.
System programmer response: None.
Module: INGRX830
Classes: 40.
ING820I
BCPII SESSION MANAGEMENT
FUNCTION LIMITATION IN FAVOR
OF APPLICATION appl_designator WAS
REQUESTED BY oper ON DOMAIN
domain.
Explanation: Command INGHWSRV BCPIIPRIO was
issued to block BCPii session restarts from interrupting
important application operation.
Message variables:
appl_designator
Name of the favored application.
oper
NetView operator or autotask, who issued the
command.
domain
NetView domain name.
System action: The BCPii session management
function operations are only limited.
Operator response: None.
Operator response: None.
System programmer response: None.
Module: INGRX815
Classes: 40.
ING822I
BCPII SESSION MANAGEMENT TO
PROCESSOR processor IS CURRENTLY
LIMITED BY appl_designator ON domain.
Explanation: BCPii session re-cycle operation was
blocked. The management operation that terminates the
session is not executed. Command INGHWSRV can be
used to restore normal operation mode for the session
which was previously limited in favor of
appl_designator.
Message variables:
processor
Target processor of the blocked session. For
application GDPS, only processors defined in the
GEOPLEX domain/options are affected.
appl_designator
Name of the blocking application.
domain
NetView domain name.
System action: The BCPii session management
function continues without terminating the session.
Operator response: None.
System programmer response: None.
Module: INGRX806, INGRVX80
Classes: 40.
ING823I
THE CURRENT BCPII SESSION
MANAGEMENT PRIORITY IS SET TO
appl_designator ON DOMAIN domain.
System programmer response: None.
Module: INGRX815
Classes: 40.
ING821I
BCPII SESSION MANAGEMENT
FUNCTION LIMITATION RELEASED
BY oper ON DOMAIN domain
Explanation: Command INGHWSRV BCPIIPRIO was
issued to restore normal SA-BCPII session management
operation.
Message variables:
oper
NetView operator or autotask, who issued the
command.
domain
NetView domain name.
System action: The BCPii session management
function runs in normal mode.
Explanation: Displays the current BCPII session
management priority setting of the domain. Command
INGHWSRV BCPIIPRIO can be used to change this
setting.
Message variables:
appl_designator
Name of the application that has priority, or
NONE.
domain
NetView domain name.
System action: None.
Operator response: None.
System programmer response: None.
Module: INGRX815
Classes: 40.
Chapter 10. Messages ING001I to INGY1337I
285
ING920I • ING924E
ING920I
COMMAND cmd ISSUED BY jobname
INHIBITS OTHER COMMANDS/JOBS
FROM EXECUTING
Explanation: SA z/OS found a command or job that
inhibits at least one other command from completing
its execution. The policy defined during customization
does not allow for abending the command.
The variable cmd shows the command name.
The variable jobname shows the name of the job.
System action: Processing continues.
Operator response: Inform your system programmer.
System programmer response: Check the execution
time of the command. If the execution time is not
reasonable, add the command to the policy along with
a reasonable execution time. This allows the cancelation
of the job if necessary.
The variable system shows the name of the system
running the job.
System action: SA z/OS cancels the indicated job and
abends all its commands in the command class where
the automation detected the command flooding.
Operator response: Inform your system programmer.
System programmer response: Determine the reason
why the job was flooding the master or console address
space with commands. Make the necessary changes to
prevent future occurrences of this situation before you
restart the job.
Module: INGRX746
Classes: 40, 43.
propd: NO
ING923I
Module: INGRX744
Classes: 40, 43.
propd: YES
LONG-RUNNING ENQ
AUTOMATION IS ACTIVE
Explanation: Automation has started monitoring of
long-running ENQs sysplexwide.
System action: Processing continues.
ING921I
THE JOB jobname IS BEING ABENDED
DUE TO A HUNG COMMAND
DETECTION ON RESOURCE resource
Explanation: SA z/OS detected a job that owns a
resource that inhibits commands from executing
successfully. The job is abended with U2047
RSNC9D5C740 to avoid lockouts of other commands.
The variable resource shows the major and minor
name of the resource.
The variable jobname shows the name of the job.
System action: Automation abends the indicated job.
Operator response: None.
System programmer response: None.
Module: INGRX744
Classes: 40, 43.
propd: YES
ING922I
System programmer response: None.
Module: INGRX745
Classes: None.
propd: NO
ING924E
AUTOMATION DETECTED THE JOB
job IN asid ON system FLOODING THE
COMMAND CLASS cc
Explanation: SA z/OS detected a job that floods the
indicated command class. However, the policy defines
the job as non-cancelable. For this reason the automation
leaves the job and the commands that have been issued
by the job untouched.
The variable job shows the name of the job issuing
the command.
The variable asid shows the address space ID
running the job.
DUE TO COMMAND FLOOD
DETECTION THE JOB job IN asid ON
system IS BEING ABENDED
Explanation: SA z/OS detected a job that is flooding
the master or console address space with commands.
To avoid lockouts of other commands the job is
canceled and all of its commands are abended with
U2047 RSNC9D5C740.
The variable job shows the name of the job.
The variable asid shows the address space ID
running the job.
286
Operator response: None.
System Automation for z/OS Messages and Codes:
The variable system shows the name of the system
running the job.
The variable cc shows the name of the command
class that is affected.
This message is issued approximately every 60 seconds
until there are no more commands waiting for
execution.
System action: Processing continues.
Operator response: Observe the command class to
determine whether the job still floods the class. If this
is the case, cancel the job because this is a serious
ING925E • ING927E
situation that inhibits other commands from being
executed in the indicated class.
After you have canceled the job clean up the command
class. Use the command CMDS SHOW to determine
the IDs of the commands that have been issued by the
indicated job. Then use the command CMDS REMOVE
to remove any commands that are waiting, and the
command CMDS ABEND to terminate any commands
that are executing.
System programmer response: Check the execution
time of the command. If the execution time is not
reasonable, add the command to the policy along with
a reasonable execution time. This allows the cancelation
of the job if necessary.
Module: INGRX744.
Classes: 40, 43.
propd: YES
System programmer response: None.
Module: INGRX746
ING927E
Classes: 40, 43.
propd: NO
ING925E
CF cfname IS IN NORMAL_OFFLINE
STATE, UNABLE TO function
Explanation: SA z/OS is unable to enable or populate
the coupling facility. SA z/OS has issued V
PATH(cfname,chp), ONLINE commands on all systems in
the sysplex, but at least one system is unable to connect
to the coupling facility. This condition has persisted for
30 seconds.
Explanation: HSAPRGRS was called for ENQ
processing but failed. This may be an ENQ/GRS issue
or a programming error in HSAPRGRS. For ENQ
failures the requested resource may already be in use
and not available or the GRS environment may not be
valid.
The variable request shows the request type for
HSAPRGRS/GQSCAN.
The variable return code shows the return code from
HSAPRGRS or the GQSCAN macro.
The variable reason code shows the reason code from
HSAPRGRS or the GQSCAN macro.
The variable cfname is the coupling facility name.
The variable function is either ENABLE or
POPULATE.
HSAPRGRS ENQ REQUEST FAILED.
REQUEST request RETURN CODE return
code REASON CODE reason code
System action: Processing is halted.
System action: Processing continues.
Operator response: Contact your system programmer.
Operator response: Contact your system programmer.
System programmer response: Check the return codes
listed below:
System programmer response: Ensure that every
system in the sysplex has at least one channel path that
is online to the coupling facility.
Classes: 40, 43.
Code
Meaning
0
Request successfully completed.
4
CHNG Status cannot be changed. Other tasks
share the resource.
EXCL/SHR/TEST
Resource is not immediately available.
REL
Resource control requested but not
yet assigned.
SCAN No resources matched the request.
propd: YES
ING926I
JOB jobname INHIBITS OTHER
COMMANDS FROM EXECUTING.
RESOURCE=qname rname
Explanation: SA z/OS found a job that inhibits at
least one other command from completing its
execution. The policy defined during customization
does not allow for terminating the task that holds the
resource lock.
The variable jobname shows the name of the job.
The variable qname shows the major resource name
that is enqueued by the job and required by the
command.
The variable rname shows the minor resource name
that is enqueued by the job and required by the
command.
System action: Processing continues.
Operator response: Contact your system programmer.
8
CHNG Status cannot be changed. No ENQ
has been requested.
EXCL/MOVE/SHR/TEST
A previous request was made. The
task already has control of the
resource.
REL
Resource is already released or the
task does not have control of the
resource.
SCAN The area is too small.
For return codes 10 and 12 a reason code from macro
GQSCAN is also returned (see z/OS MVS Assembler
Reference).
Chapter 10. Messages ING001I to INGY1337I
287
INGC1010I • INGC1013I
10
INGC1011I
SCAN
GQSCAN failed. Check the reason
code.
SCAN
GQSCAN failed. Check the reason
code.
12
20
CHNG/EXCL/MOVE/SHR/TEST
A previous request was made. The
task does not have control of the
resource.
24
Exit exitname has been enabled.
Explanation: The exit named in exitname has been
enabled. exitname can have the values of XMEOUT for
the CICS message exit, or XDTOUT for the Transient
Data Queue exit.
This message will be issued if a refresh of the policy is
in progress. The exits are enabled if the user has
specified policy information in the MESSAGES/USER
DATA policy. The XMEOUT exit will be enabled for
any message in the policy that starts with DFH and has
an OFFSET= value specified in the USER DATA section.
The XTDOUT exit will be enabled for any message that
has the OFFSET= and TDQUEUE= values specified in
the USER DATA section.
EXCL/MOVE/SHR
ENQ limit reached.
System action: Processing continues and the specified
exit will be invoked to process messages.
32
No storage available for GQSCAN.
Operator response: None.
36
Resource not owned by the task with the TCB
address.
INGC1012I
-1
IRXEXCOM error.
-2
IRXEXCOM error.
n01
nth parameter not specified.
n02
Length of nth parameter is greater than 240.
n03
nth parameter doesn't represent a stem
variable.
n04
Value of nth parameter is invalid.
n05
Invalid parameter.
1nnn
IRXEXCOM error 'nnn'.
Classes: 40, 43.
INGC1010I
Exit exitname has been disabled.
Explanation: The exit named in exitname has been
disabled. exitname can have the values of XMEOUT for
the CICS message exit, or XDTOUT for the Transient
Data Queue exit.
This message will be issued if an existing policy has
enabled the specified exits and a refresh of the policy is
in progress. The exits are disabled and then optionally
re-enabled based on the new policy.
System action: Processing continues and the specified
exit is not invoked to process messages.
Operator response: This is not an error message. The
product will function correctly with one or both the
exits disabled. However, this message should be
followed by INGC1011I if the user has specified a
message exit policy according to the IBM Tivoli System
Automation for z/OS Product Automation Programmer's
Reference and Operator's Guide manual.
288
System Automation for z/OS Messages and Codes:
No message policy definitions found.
Exits will not be enabled.
Explanation: There are no USER DATA policy
definitions for the XMEOUT or XTDOUT exits and so
the exits will not be enabled.
System action: Processing continues and the exits will
not be invoked to process messages.
Operator response: If messages should be processed,
check that the OFFSET= parameter has been specified
in the USER DATA section of the message policy. Also
check that the TDQUEUE= parameter is specified for
Transient Data Messages.
INGC1013I
Processing function. CICS service Service
failed with EIBRCODE=code
Explanation: In the process of refreshing the message
exit policy in the CICS subsystem, a CICS service has
returned an unexpected return code.
The variable function can be one of:
XMEOUT
Policy was being processed for the XMEOUT exit.
XDTOUT
Policy was being processed for the XTDOUT exit.
BOTH
Policy was being processed for both the XMEOUT
and XTDOUT exits.
The variable service can be one of:
DISABLE
Exit was being disabled via EXEC CICS DISABLE.
ENABLE
Exit was being enabled via EXEC CICS ENABLE.
EXTRACT
Exit information was being extracted via EXEC
CICS EXTRACT.
INGI1010I • INGLCR03I
FREEMAIN
Storage was being released via EXEC CICS
FREEMAIN.
GETMAIN
Storage was being obtained via EXEC CICS
GETMAIN.
MSGBUILD
A message was being built. EIBRCODE refers to
the code returned from this routine and not an
EXEC CICS function.
exit is still invoked, however as no message policy is
present, it will not take any actions.
The variable code is the EIBRCODE of the EXEC CICS
function or the return code as specified above.
INGI1013I
System action: Processing is aborted and exits may or
may not be enabled or disabled.
Explanation: The DFSAOE00 exit has been enabled.
Operator response: For MSGBUILD make sure that
the INGAMCE module is in the DFHRPL
concatenation. If it is and for all other circumstances,
report this error to service.
INGI1010I
Automated Operator Exit Initialized for
IMS ims Level level
Explanation: The SA z/OS exit has been initialized
and the IMS control region is running at the specified
level.
The variable ims is the IMS subsystem id.
The variable level is the Version Modification
Release of the IMS.
System action: Processing continues.
Operator response: None.
INGI1011I
No message policy definitions found.
Exits will not be enabled for IMS ims.
Explanation: There are no USER DATA policy
definitions for the IMS subsystem and so the exits will
not be enabled.
Operator response: This is not an error message. The
product will function correctly with the exit disabled.
However, this message should be followed by
INGI1013I if you have specified message exit policy
according to the IBM Tivoli System Automation for z/OS
Product Automation Programmer's Reference and Operator's
Guide manual.
Exit DFSAOE00 has been enabled for
IMS ims.
This message will be issued if a refresh of the policy is
in progress. The exits are enabled if the user has
specified policy information in the MESSAGES/USER
DATA policy. The exit will be enabled for any message
in the policy that has the OFFSET= value specified in
the USER DATA section.
The variable ims is the IMS subsystem id.
System action: Processing continues and the specified
exit will be invoked to process messages.
Operator response: None.
INGLCR01E Dynamic allocation failed for DSN=file
name.
Explanation: Life Cycle Recording (LCR) cannot
allocate the data set specified in file name.
System action: Either LCR cannot be enabled or the
error occurred while offloading the data space to a data
set (using the SAVE command).
Operator response: Check that you have specified a
correct data set name via the command INGRXQRY
LCR, or in HSAPRMxx or INGXINIT.
System programmer response: None.
The variable ims is the IMS subsystem id.
System action: Processing continues and the exits will
not be invoked to process messages.
Operator response: If messages should be processed,
check that the OFFSET= parameter has been specified
in the USER DATA section of the message policy.
INGI1012I
Exit DFSAOE00 has been disabled for
IMS ims.
Explanation: The DFSAOE00 exit has been disabled.
This message will be issued if an existing policy has
enabled the specified exits and a refresh of the policy is
in progress. The exits are disabled and then optionally
re-enabled based on the new policy.
The variable ims is the IMS subsystem id.
System action: Processing continues and the specified
INGLCR02I Close life cycle recording.
Explanation: SA z/OS starts closing Life Cycle
Recording (LCR) for either the primary automation
manager (PAM) or an automation agent.
System action: The data space is automatically
offloaded to the data set.
Operator response: None.
System programmer response: None.
INGLCR03I Begin blocking access to LCR.
Explanation: When Life Cycle Recording (LCR) is
about to close or offload the data space, activities by
other tasks are blocked until the data space has been
written to disk.
Chapter 10. Messages ING001I to INGY1337I
289
INGLCR04I • INGLCR12I
System action: None.
Operator response: None.
System programmer response: None.
INGLCR04I End blocking access to LCR.
Explanation: The Life Cycle Recording (LCR) close or
offload process has finished.
System action: None.
INGLCR08I Life cycle recording is currently status,
NAME=dataset_name
Explanation: Status message indicating the current
status of Life Cycle Recording (LCR), which is either
enabled or disabled.
System action: None.
Operator response: None.
System programmer response: None.
Operator response: None.
System programmer response: None.
INGLCR05E ABEND xxxx-rcrcrcrc occurred for output
media media_type
Explanation: An abend occurred during the I/O
operation for a data set or data space for Life Cycle
Recording (LCR).
The variable xxxx is the system completion code.
The variable rcrcrcrc is the corresponding reason
code.
System action: Life Cycle Recording is disabled.
Operator response: Collect additional information
about the reason for the abend, for example, the data
set was too small. If you cannot fix the problem, report
the error to your IBM Support Center.
System programmer response: None.
INGLCR06E Cannot open/write output media.
Explanation: Life Cycle Recording (LCR) cannot
complete one of the following:
v Opening a data set or a data space
v Writing a record to the data space
v Offloading the data space to data set
System action: Life Cycle Recording is disabled.
Operator response: Look for additional error
messages, such as INGLCR05.
System programmer response: None.
INGLCR09I Life cycle recording will be disabled.
Explanation: An abend occurred and Life Cycle
Recording (LCR) is about to be disabled.
System action: None.
Operator response: None.
System programmer response: None.
INGLCR10I Life cycle recording has been
successfully initialized,
NAME=dataset_name
Explanation: Life Cycle Recording (LCR) has been
initialized. A data set was allocated and an initial
record was written (any old data is lost). The data
space has been allocated.
System action: Life Cycle Recording is ready for the
command to enable it.
Operator response: None.
System programmer response: None.
INGLCR11I Successfully flushed records, total size
#rec(KB)=size1(size2).
Explanation: size1 is the total number of checkpoint
records ever written by Life Cycle Recording (LCR) to
the data space. This is an accumulated number and is
not reset due to possible wraparound.
size2 is the number of bytes actually allocated by the
data space. Later when the data space is saved to disk,
size2 is written.
INGLCR07I Life cycle recording has been enabled,
NAME=dataset_name
System action: None.
Explanation: Life Cycle Recording (LCR) has been
enabled with the dataset_name that will later be used as
the offload data set.
System programmer response: None.
System action: None.
Operator response: None.
System programmer response: None.
290
System Automation for z/OS Messages and Codes:
Operator response: None.
INGLCR12I Switch output media for Life cycle
recording.
Explanation: Life Cycle Recording (LCR) has switched
the output media. The old data space is offloaded to
the old data set. A new, empty data space is allocated
and initialized with an initial record. A new data space
is created.
INGLCR13E • INGLCR23E
System action: None.
Operator response: None.
System programmer response: None.
INGLCR13E Switching output media for life cycle
recording failed.
Explanation: Life Cycle Recording (LCR) cannot
switch the output media.
System action: None.
Operator response: None.
System programmer response: None.
INGLCR15E Creation of data space failed for
DSP=file name
Explanation: Life Cycle Recording (LCR) cannot create
a data space. This is caused either by the command
INGRXQRY LCR, or while initializing the SA z/OS
INGPXDST agent task or the SA z/OS primary
automation manager (PAM).
System action: LCR cannot be enabled.
Operator response: Look for additional error
messages, such as INGLCR23E.
System programmer response: None.
INGLCR21I Start offloading data space.
Explanation: Life Cycle Recording (LCR) starts
offloading the data space to the data set.
System action: None.
Operator response: None.
System programmer response: None.
INGLCR22I End offloading data space.
Explanation: Life Cycle Recording (LCR) has finished
offloading the data space to the data set.
System action: None.
Operator response: None.
System programmer response: None.
INGLCR23E function failed, rc=rc frc=frc rsn=rsn
32 REXX V-pool error
40 Communication environment not available
81 Initialization of lifecycle recording failed
99 Invalid input arguments
<100
Internal error by INGPXILC
108
Internal. Invalid parameter list
109
Internal. LCR control block has not been
initialized
112
Internal. Invalid function
116
Dynamic allocation failed
120
File open failed
121
File put failed
122, 123
Writing a control record failed while closing the
file
128
Get record failed
132
Function rejected because a sever error occurred
previously
136
ESTAE cannot be established
140
An abend occurred
144
DSP Create failed
145
DSP Delete failed
146
DSP Put failed
147
DSP Get failed
148
DSN is missing
149
Semicolon missing in INGRXQRY command
150
Invalid size
>200
ENQ failed
>300
DEQ failed
>400
NetView ALLOC error
489
Invalid parameter list
Explanation: Life Cycle Recording (LCR) detected an
error while processing the function function. Diagnostic
information is provided as the return code (rc), function
return code (frc), and reason code (rsn).
v The variable frc shows the function return code. This
is additional diagnostic information that is intended
for the IBM Support Center.
v The variable function shows the function that
produced the error. It can be OPEN, CLOSE,
OFFLOAD, or FLUSH.
v The variable rsn shows the reason code. This is
additional diagnostic information that is intended for
the IBM Support Center.
v The variable rc shows the return code:
System action: LCR is disabled.
Chapter 10. Messages ING001I to INGY1337I
291
INGPC010I • INGPC020I
Operator response: Collect additional error messages,
if available.
System programmer response: Report the problem to
your IBM Support Center.
System programmer response: None.
INGPC016I
INGPC010I
pgm is unable to perform function
service, PPI_id=xxxxxxxx
Explanation: The program pgm failed to perform the
PPI function service with PPI using the PPI id
xxxxxxxx. Function could be:
v open DSIPHONE(OPENRECV)
v close DSIPHONE(CLOSE)
v send DSIPHONE(SEND)
v receive DSIPHONE(RECEIVER)
System action: The program exits.
Operator response: Check if a correct PPI receiver id
was specified. Message INGPC011I might also be
issued and provides additional PPI and DSIPHONE
error information.
System programmer response: None.
INGPC011I
|
|
|
|
|
|
xxxxx, PPI Reason: yyyy
Explanation: The message provides DSIPHONE error
information xxxxx and optional PPI error info yyyy.
When sending over secure PPI then xxxxx describes the
error info about the SA secure PPI interface
INGPAUTH instead of DSIPHONE. It will be issued in
addition to INGPC010I.
System action: None.
Operator response: None.
System programmer response: None.
INGPC012I
The program pgm detected missing or
invalid input for argument n
Explanation: The program pgm failed because the
input argument n is missing or invalid.
System action: The program exits.
Operator response: None.
System programmer response: Check input
arguments.
INGPC015I
cond condition trapped in script pgm
Line: sigl Code: rc Description: desc
Explanation: The program pgm failed due to a REXX
script error.
System action: The program exits.
Operator response: Report problem to your system
programmer unless the condition is triggered by the
operator, such as a HALT condition.
292
System Automation for z/OS Messages and Codes:
INGPCxxx service failed, RC=nn
Explanation: The program INGPCxxx failed with
return code nn.
System action: The program exits.
Operator response: Report the problem to your
system programmer.
System programmer response: Report the problem to
your IBM Support Center.
INGPC017I
pgm failed. Reason
Explanation: The program pgm failed. Additional error
info is provided in Reason.
System action: The program exits.
Operator response: Report the problem to your
system programmer.
System programmer response: Analyze the return
code and/or additional error message. Resolve the
problem and rerun the command.
INGPC018I
pgm terminates with error, rc=nnn
Explanation: The program pgm terminates due to an
error. Return code nnn is provided.
System action: The program exits.
Operator response: Report the problem to your
system programmer.
System programmer response: Analyze the return
code and/or additional error message. Resolve the
problem and rerun the command.
INGPC019I
pgm does not support host: HOST ASP
Explanation: The program pgm does not support the
REXX host environment. HOST and ASP is extracted
from REXX 'parse source'.
System action: The program exits.
Operator response: Check why the program was
called in the wrong environment.
System programmer response: None.
INGPC020I
pgm detected bad response: reason
Explanation: The program pgm failed since an
unexpected response was received. Reason describes the
error.
System action: The program exits.
Operator response: Report problem to your system
programmer.
INGPC021I • INGPC027I
System programmer response: Report the problem to
your IBM Support Center.
INGPC021I
pgm is called with invalid name cpyname
Explanation: The program pgm failed since the REXX
program was copied with an unsupported name or
alias cpyname.
System action: The program exits.
Operator response: Report problem to your system
programmer.
System programmer response: Use supported
OPSxxxx names when copying or defining an alias of
pgm.
INGPC022I
pgm is called as cpyname for an invalid
mode: mode
Explanation: The program pgm failed since it was
called as command but only function call is supported
or vice versa. The invalid mode is either COMMAND
or FUNCTION.
System action: The program exits.
Operator response: Invoke the function only as the
supported mode.
INGPC024I
|
|
|
|
|
|
|
|
|
SA REXX function aborted due to no
data specified on RETURN
Explanation: A System Automation REXX function
running under TSO detected an error. A typical
scenario might be: Due to the RACF checking of the
TSO user id, an emulated function fails. Since a value
must be returned for this error, the emulator must force
an Incorrect call to routine by returning nothing.
This forces REXX error message IRX0045I on purpose.
The originating error is described in an additional
message, for example INGPC023I.
System action: The REXX function exits.
Operator response: Report the problem to the system
programmer.
System programmer response: Analyze additional
message accompanied with INGPC024I and fix the
problem in the REXX user program.
INGPC025I
Incorrect call to name
Explanation: The named program was called directly
rather than from a REXX script.
System action: The program exits.
Operator response: None.
System programmer response: None.
INGPC026I
INGPC023I
RACF check failed: reason. For info.
Explanation: On TSO the emulator commands check
the TSO user id against a profile. This message will be
issued if access is not granted or if an RACF error
message occurred. reason might be one of the following:
v Access Allowed
v Profile not Defined
v User not Authorized
error information
Explanation: An error occurred as reported by the
previously issued message for example, INGPC017I.
This message gives additional information.
System action: The program exits.
Operator response: Report problem to your system
programmer.
System programmer response: If necessary, report the
problem to your IBM Support Center.
v HSAPRRAC rc=nnn
Info is given in the following format, for example:
UserID=BDOW Clist=INGRCCMX Class=FACILITY
PROFILE=ING.EMULATOR.CMD
The high level qualifier ING was customized via
command "INGCSA SET NAME=EMU.RACF.HLQ
VALUE=ING". The qualifier EMULATOR is a fixed
string and CMD depends on the calling clist being one
of the following:{CMD,VAL,SQL,DFLT}. If
EMU.RACF.HLQ was not customized, RACF checking
is ignored.
System action: The calling program terminates.
Operator response: Report the problem to your
system programmer.
INGPC027I
command. Parameter parm missing or
invalid value
Explanation: The specified parameter is either wrong
or missing.
The variable command is the name of the command
being processed.
The variable parm is the parameter that is invalid or
missing.
The variable value is the value of the parameter that
is wrong. The variable is only present when
applicable.
System action: None.
Operator response: None.
System programmer response: Give the TSO user the
correct RACF access rights or correct the RACF HLQ.
Chapter 10. Messages ING001I to INGY1337I
293
INGPC028I • INGV0004I
| INGPC028I Security check for TSO user failed due
|
to errtext.
| Explanation: A System Automation TSO command
| tries to send a request to the System
|
|
|
|
|
Automation/NetView Agent on a secure channel.
Message INGPC028I will be issued if the SAF frontend
security checking failed. The TSO user id must have
READ access to the SAF frontend profile
TSO.plexname.system.CMDRCVR.SEND.
|
Table 7. Error Text for INGPC028I
|
errtext
Description
|
HSAPRRAC error
Internal API returns an error.
|
invalid parameter
Internal API detects an invalid input argument.
|
invalid class
The class SYSAUTO is not authorized.
|
user not authorized
TSO userid is not authorized to access the profile.
|
|
resource not protected
The profile is not defined.
| System action: Request was not sent to the System
| Automation/NetView agent.
|
The variable aa identifies the name of the module.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
|
System programmer response: Ensure the content of
the library ending with SINGMOD3 is loaded into the
LPA.
|
INGV0003I
Explanation: The indicated library is not found in the
current LNKLST concatenation.
| Operator response: None.
|
|
|
|
|
| System programmer response: Modify the script
| invoking the emulator.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
System programmer response: Add the indicated
library to the current LNKLST.
|
INGV0004I
|
|
|
|
|
|
|
|
|
Explanation: The indicated library has been found in
the current LNKLST set. However, the verification
routine also detected that another library of the same
type precedes the library.
|
The verification ends with warnings.
|
System action: None.
| Operator response: None.
|
|
|
|
System programmer response: Check if the profile
was correctly defined and the TSO userid has READ
access. If an internal API error occurred, switch on
trace and rerun the command.
| INGPC029I Parameter xxxx is not supported by
|
emulator for yyyy.
| Explanation: The emulated command or function for
| yyyy was called on TSO but the parameter xxxx is not
| supported by the SA z/OS emulator.
| System action: The program continues.
| INGV0001I
Library aa.bb is not APF authorized.
| Explanation: The indicated library is not APF
| authorized.
|
The variable aa identifies the high-level qualifier of
|
the library as found in the configuration file.
|
The variable bb identifies the type of the library.
| The verification ends with warnings.
| System action: None.
| Operator response: None.
| System programmer response: Correct the panel
| descriptions.
| INGV0002I
LPA Module aa not found.
| Explanation: The indicated module is required to be
| stored in the LPA. However, the verification routine
| could not locate the module in the LPA.
294
System Automation for z/OS Messages and Codes:
Library aa.bb not in LNKLST.
The variable aa identifies the high-level qualifier of
the library as found in the configuration file.
The variable bb identifies the type of library.
Library aa.bb preceded by cc.
The variable aa identifies the high-level qualifier of
the library as found in the configuration file.
The variable bb identifies the type of library.
The variable cc shows the data set name of the
library that precedes this library.
INGV0005I • INGV0010I
|
Operator response: None.
|
|
System programmer response: Move the entry to the
top of the current LNKLST set.
|
|
INGV0005I
|
|
|
|
|
|
Explanation: The verification routine either did not
find the indicated module in the program property
table (PPT) or the corresponding PPT entry shows an
improper or missing attribute.
Improper PPT entry found for aa,
RSN=bb
v The variable aa shows the name of the module.
v The variable bb shows one or more reasons:
|
80
NOCANCEL not specified.
|
40
KEY(8) not specified.
|
20
NOSWAP not specified.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
System programmer response: Correct the PPT entry
of the indicated module depending on the reason code.
|
INGV0006I
|
|
|
|
Explanation: The verification routine could not
connect to the indicated log stream because it is not
defined to the current LOGR policy.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
System programmer response: Define the indicated
log stream to the current LOGR policy.
Log stream aa not defined.
The variable aa shows the name of the log stream.
|
INGV0007I
|
|
|
|
|
Explanation: The verification routine found the
System Logger address space active. However, the
configuration file indicates the configuration for a
GDPS KSYS system. This type of system does not allow
an active System Logger.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
System programmer response: Stop the System
Logger address space.
System logger still active.
|
INGV0008I
|
|
|
|
|
Explanation: The verification routine could not locate
the indicated REXX function package in the LPA or the
LNKLST concatenation.
|
The verification ends with warnings.
|
System action: The verification step is skipped.
|
Operator response: None.
|
|
|
System programmer response: Add the indicated
REXX function package either to the LPA or to the
LNKLST.
|
|
INGV0009I
|
|
|
|
|
|
|
Explanation: The verification routine could not find
the required REXX function package in the indicated
module.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
|
|
|
System programmer response: Edit the source
member of the module and add the required REXX
function package to the module. Re-assemble and
re-link the module and add it to the LPA or to the
LNKLST.
|
INGV0010I
|
|
|
|
|
Explanation: The verification routine detected a
version mismatch between two ISPF dialog members,
ISPF table AOFTOPOL and panel AOFG#NL1.
|
The verification ends with warnings.
|
System action: None.
|
Operator response: None.
|
|
System programmer response: Verify that the ISPF
installation libraries are set up correctly.
REXX package aa not found.
The variable aa shows the name of the function
package.
REXX function package aa not found in
bb.
The variable aa shows the name of the SA function
package.
The variable bb shows the name of the REXX
function package.
Version mismatch found, aa - bb.
The variable aa shows the version of the ISPF table.
The variable bb shows the version of the ISPF panel.
Chapter 10. Messages ING001I to INGY1337I
295
INGV0011I • INGV9005I
| INGV0011I
Major node aa not found.
| Explanation: The verification routine detected that the
| NetView major node has not been defined to VTAM.
|
The variable aa shows the NetView major node
|
name.
| The verification ends with warnings.
| System action: None.
| Operator response: None.
| System programmer response: Add the major node
| definition to VTAM and activate it.
| INGV0012I
|
|
System programmer response: Contact the IBM
support center.
|
INGV9002I
|
|
|
|
Explanation: The indicated keyword could not be
found in the configuration file. Or, the keyword is
found but has no value.
|
System action: Verification is terminated.
|
Operator response: None.
|
|
System programmer response: Contact the IBM
support center.
|
INGV9003I
|
|
|
|
Explanation: The indicated macro failed.
Keyword aa not found.
The variable aa shows the name of the keyword.
Applid aa not found in bb.
| Explanation: The verification routine detected that the
| NetView applid has not been defined in the indicated
| VTAM major node.
|
The variable aa shows the NetView applid.
|
The variable bb shows the NetView major node
|
name.
Macro aa failed, RC=bb, RSN=cc.
The variable aa shows the name of the macro.
The variable bb shows the return code of the macro.
The variable cc shows the reason code of the macro.
|
System action: Verification is terminated.
| The verification ends with warnings.
|
Operator response: None.
| System action: None.
| Operator response: None.
|
|
System programmer response: Contact the IBM
support center.
| System programmer response: Correct the VTAM
| major node definition and activate it.
|
INGV9004I
|
|
|
|
|
Explanation: The verification routine requires the
configuration file created by the wizard. Either the
ddname INGCFG was not specified or the record
format of the file is UNDEFined or a read error
occurred.
|
System action: Verification is terminated.
|
Operator response: None.
| Operator response: None.
|
|
System programmer response: Correct the error
condition and re-run the verification.
| System programmer response: Ensure that the library
| containing the verification is APF authorized. Then,
| repeat the verification.
|
|
INGV9005I
|
|
|
|
|
|
Explanation: The verification routine requires the
indicated authorization when the Security
Authorization Facility (SAF) is available.
|
System action: Verification is terminated.
|
Operator response: None.
|
|
|
System programmer response: Grant the required
authorization to the verification routine and re-run the
verification.
| INGV9000I
Verification step "aa" not executed.
| Explanation: The verification could not switch into a
| mode and key that is required to perform the indicated
| verification step.
|
The variable aa shows the description of the step.
| System action: The step is not performed.
| INGV9001I
|
Parse error occurred, Text<aa> Pos=bb,
RC=cc.
| Explanation: The verification parses the configuration
| file created by the wizard. The parser found an error
| condition.
|
The variable aa shows the text around the error.
|
The variable bb shows the position in error relative
|
to the beginning of the text.
|
The variable cc shows the return code returned by
|
the parser.
| System action: Verification is terminated.
| Operator response: None.
296
System Automation for z/OS Messages and Codes:
Configuration file error.
aa authority missing, CLASS=bb,
RESOURCE=cc.
The variable aa shows the required authority.
The variable bb shows the name of the SAF class.
The variable cc shows the name of the resource.
INGV9006I • INGX1011I
|
|
INGV9006I
|
|
|
|
|
|
|
|
Explanation: The verification routine failed to allocate
the indicated member.
|
System action: Verification step is terminated.
|
Operator response: None.
|
|
|
System programmer response: Ensure that the data
set is available on the current system and re-run the
verification.
Member aa(bb) not allocated, RC=cc,
RSN=dd.
The variable aa shows the name of the data set.
The variable bb shows the name of the member.
The variable cc shows the return code of the
DYNALLOC macro.
The variable dd shows the reason code of the
DYNALLOC macro.
|
Logger address and re-run the verification.
INGX1001E
PLX STACK OVERFLOW: module
compile_date info
Explanation: SA z/OS detected an internal error due
to a PLX stack overflow.
The variable module shows the name of the module
that detected the stack overflow.
The variable compile_date shows the date that the
module was compiled.
The variable info gives additional information about
the overflow.
System action: None. The function terminates with
abend 3999.
Operator response: None.
System programmer response: Check the syslog for
the associated messages and dump information, and
contact your IBM Support Center.
|
|
INGV9007I
|
|
|
|
|
|
Explanation: The verification routine failed to open
the indicated member.
|
System action: Verification step is terminated.
System action: None.
|
Operator response: None.
Operator response: None.
|
|
System programmer response: Contact the IBM
support center.
|
|
INGV9008I
System programmer response: Check the syslog for
the associated message HSAM1050E that contains
further debugging information. If the problem persists
consider increasing the number of XCF buffers. The
maximum XCF buffer size for SA z/OS is 4028.
|
|
|
|
Explanation: The verification routine could not find
the release information in the indicated member.
|
System action: Verification step is terminated.
|
Operator response: None.
|
|
System programmer response: Contact the IBM
support center.
|
INGV9009I
|
|
|
|
Explanation: The verification routine did not find the
System Logger address space active. This inhibits the
routine from verifying the definitions of the
automation-specific log streams.
|
System action: Verification step is terminated.
|
Operator response: None.
|
System programmer response: Start the System
Member aa(bb) could not be opened,
RC=cc.
The variable aa shows the name of the data set.
The variable bb shows the name of the member.
The variable cc shows the return code of the OPEN
function.
Release information not found in
member aa(bb).
The variable aa shows the name of the data set.
The variable bb shows the name of the member.
System Logger not active.
INGX1002I
SHORT ON XCF BUFFERS - RETRY
Explanation: The SA z/OS communication framework
cannot send data segments due to the condition “Short
On XCF Buffers”. SA z/OS will try to resend the data
segment after a timeout delay. If this is not successful a
timeout error message ING008I is issued.
INGX1011I
INBOUND DIAGNOSTICS: DIF=nn
ABS=nn QUE=n EXP=n SEC=nn
CPU=nnn OUT=nn RSP=nn FAF=nn
Explanation: This message is issued by the
automation manager work item queue monitoring
routine when it detects that more work items are
arriving than can be processed by the automation
manager within the monitoring interval.
DIF
The number of incoming work items that have not
yet been processed during the monitoring interval.
It is the number of work items in the queue at the
current monitoring time minus the number of
work items in the queue at the last monitoring. If
the number is positive and grows it is an
indication that the automation manager is being
put under stress.
ABS
The total number of work items in the input and
output queues. This value includes the number of
work items that have been processed but that have
Chapter 10. Messages ING001I to INGY1337I
297
INGX9601I • INGX9702I
not been through the cleanup process. The number
is typically higher then the QUE number. If the
number differs greatly from the QUE value, it
might be an indication that the automation
manager is unable to deliver command responses
to the automation agents. A value that is slightly
higher than QUE is acceptable.
|
|
|
INGX9603I
|
|
Explanation: The WebServices Adapter is ready to
work automation domain name.
|
System action: Processing continues.
The current size of the work item queue.
|
Operator response: None.
The number of work items in the input queue that
have already expired. Expired work items are not
processed by the automation manager but cause an
ING008 timeout message.
|
System programmer response: None.
|
|
|
INGX9604I
|
|
|
Explanation: The WebServices Adapter suffers an
internal error that is not expected to be caused by any
input URL or input parameter.
|
|
The internal error_code and the reason is additional
debug information for IBM support.
|
|
System action: The WebServices Adapter continues
running or terminates depending on the error scenario.
The query work items in the input queue.
|
Operator response: None.
The number of work items in the input queue that
do not require a response. Typically, these are
status updates.
|
|
System programmer response: Contact your IBM
Support Center.
|
|
INGX9605I
|
|
|
|
Explanation: The URL associated with the HTTP
request is not accepted due to the specified reason. In
most cases the URL has an invalid format or
unsupported parameters.
|
|
System action: The HTTP request is rejected. The
WebServices Adapter continues running.
|
Operator response: None.
|
System programmer response: None.
QUE
EXP
SEC
The monitoring interval. It is customizable and
runs from 10 to 999 seconds.
CPU
The total accumulated CPU time used by the
automation manager
OUT
The number of outbound orders that are waiting to
be sent to the agent or agents.
RSP
FAF
System action: Execution continues.
Operator response: None.
System programmer response: None.
| INGX9601I
|
System Automation WebServices
Adapter jobname failed: reason
| Explanation: The WebServices Adapter caught an
| exception. The reason describes the kind of exception.
| System action: The HTTP request has been aborted.
| However, processing of the WebServices Adapter
| continues.
| Operator response: None.
| System programmer response: Check the reason and
| try to resolve the problem. If necessary, contact your
| IBM Support Center.
| INGX9602I
|
|
System Automation WebServices
Adapter jobname accepts HTTP requests
via remote_contact.
| Explanation: The WebServices Adapter is ready to
| accept HTTP requests via the IP address and port as
| specified in remote_contact.
| System action: Processing continues.
INGX9701I
System Automation WebServices
Adapter jobname initialization complete
for automation domain name.
System Automation WebServices
Adapter jobname internal error error_code,
reason.
System Automation WebServices
Adapter jobname does not accept reason.
ingadapter.sh
[-](start|stop|GenerateSampleKeys|
IBMSupport|traceON|traceOFF) [suffix]
Explanation: Describes the syntax of the automation
adapter start/stop command. It is also shown if there
are invalid arguments or no arguments specified.
System action: None.
Operator response: Specify command syntax as
described.
INGX9702I
Script ingadapter.sh completed
successfully.
| Operator response: None.
Explanation: The end-to-end automation adapter start
script ended successfully.
| System programmer response: None.
System action: None.
298
System Automation for z/OS Messages and Codes:
INGX9703E • INGX9710I
Operator response: None.
INGX9703E
Script ingadapter.sh completed
unsuccessfully.
Explanation: An error occurred during script
execution.
System action: Script execution is interrupted.
Operator response: Check previous error messages for
more details