Version 4.Release 2 IBM Z System Automation

IBM Z System AutomationVersion 4.Release 2

Messages and Codes

IBM

SC34-2719-02

Note

Before using this information and the product it supports, read the information in Appendix G,“Notices,” on page 597.

Edition Notes

This edition applies to IBM Z System Automation (5698-SA4) Version 4 Release 2, an IBM® licensed program, and to allsubsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SC34-2719-01.© Copyright International Business Machines Corporation 1996, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Tables................................................................................................................... v

Accessibility........................................................................................................ viiUsing assistive technologies...................................................................................................................... viiKeyboard navigation of the user interface................................................................................................. vii

About this publication...........................................................................................ixWho Should Use This Publication............................................................................................................... ixHow to Use This Publication....................................................................................................................... ixWhere to Find More Information.................................................................................................................ix

Z System Automation Library................................................................................................................ ixRelated Product Information..................................................................................................................x

Chapter 1. About Z System Automation Messages.................................................. 1Format of Z System Automation Messages.................................................................................................1Message Text................................................................................................................................................2Who Receives Messages.............................................................................................................................. 2

Displaying Notification Operator Settings..............................................................................................2Message Classes.......................................................................................................................................... 3MVS Descriptor Codes..................................................................................................................................4

Chapter 2. Messages AOF000I to AOF969I............................................................. 5

Chapter 3. Messages AOFS000I to AOFS820I..................................................... 163

Chapter 4. Messages EVE120I to EVE842E (CICS Automation)............................ 179Error Codes.............................................................................................................................................. 185

Chapter 5. Messages EVI022I to EVI844A (IMS automation)............................... 193

Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation).............................. 197Codes Posted to TWS by TWS Automation............................................................................................. 213

Chapter 7. Messages HSAH001I to HSAL6999I................................................... 215

Chapter 8. Messages HSAM1000I to HSAM5411I................................................233

Chapter 9. Messages ING001I to INGY1337I...................................................... 267

Chapter 10. Messages ISQ001I to ISQ901I.........................................................419

Chapter 11. Messages ISQX998I and ISQX999I.................................................. 507

Chapter 12. Messages ISQtt001I to ISQtt0723I..................................................509

Appendix A. Abend Codes and Reason Codes Issued By the AutomationManager........................................................................................................ 535

iii

Communication DST and Automation Manager Abend Codes............................................................... 535

Appendix B. Response Messages, Error Strings, Condition Codes........................ 537Response Messages (AOFA0000–AOFA0099)....................................................................................... 537Asynchronous Response Messages (AOFA0100–AOFA0999)...............................................................550Condition Codes.......................................................................................................................................554

Hardware Communication Task Condition Codes "00B00xxx"........................................................ 554Data Exchange Services "0B100xxx"................................................................................................ 559Command Services "0B200xxx"........................................................................................................562Internal Transport Services "0Bx00xxx"........................................................................................... 566

Appendix C. Sense Codes, Hardware Object Status Summary............................. 571Sense Codes............................................................................................................................................ 571Hardware Object Status Summary..........................................................................................................573

Appendix D. Automation Manager Reason Codes................................................ 575

Appendix E. Sysplex Communication Services Return and Reason Codes............ 579

Appendix F. End-to-End Automation Adapter Messages...................................... 583

Appendix G. Notices.......................................................................................... 597Trademarks.............................................................................................................................................. 598Terms and conditions for product documentation................................................................................. 598

Glossary............................................................................................................ 601

iv

Tables

1. Z System Automation library........................................................................................................................ ix

2. Message Classes............................................................................................................................................3

3. Combinations of Error Types and Error Codes........................................................................................... 61

4. Reason Text for Return Codes.................................................................................................................. 318

5. Return Codes from INGRXCMJ................................................................................................................. 318

6. Reserved Return Codes............................................................................................................................ 324

7. Return Codes of ING338I......................................................................................................................... 326

8. Error Text for INGPC028I......................................................................................................................... 372

9. Return and Reason Codes of INGY1000I.................................................................................................395

10. First byte (function code) of the reason code........................................................................................ 410

11. Hardware Communication Task Condition Codes..................................................................................554

12. Data Exchange Services Condition Codes..............................................................................................560

13. Command Services Condition Codes..................................................................................................... 562

14. Internal Transport Services Condition Codes........................................................................................ 567

15. Status Values for CPC and Image Objects Provided by the z Systems API.......................................... 573

16. Automation Manager Reason Codes...................................................................................................... 575

17. Sysplex Communication Manager API Function Codes.........................................................................579

18. Error Codes from Message AOF350E.....................................................................................................581

v

vi

Accessibility

Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, touse software products successfully. IBM Z System Automation supports several user interfaces. Productfunctionality and accessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:

• Use assistive technologies such as screen reader software and digital speech synthesizer, to hear whatis displayed on screen. Consult the product documentation of the assistive technology for details onusing those technologies with this product and screen magnifier software

• Operate specific or equivalent features using only the keyboard• Magnify what is displayed on screen.

The product documentation includes the following features to aid accessibility:

• All documentation is available to both HTML and convertible PDF formats to give the maximumopportunity for users to apply screen-reader software

• All images in the documentation are provided with alternative text so that users with vision impairmentscan understand the contents of the images.

Using assistive technologiesAssistive 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 toaccess z/OS interfaces.

Keyboard navigation of the user interfaceUsers can access z/OS user interfaces using TSO/E or ISPF. Refer to z/OS TSO/E Primer, z/OS TSO/E User'sGuide, and z/OS ISPF User's Guide Vol 1 for information about accessing TSO/E and ISPF interfaces. Theseguides describe how to use TSO/E and ISPF, including the use of keyboard shortcuts or function keys (PFkeys). Each guide includes the default settings for the PF keys and explains how to modify their functions.

© Copyright IBM Corp. 1996, 2019 vii

viii IBM Z System Automation Messages and Codes :

About this publication

This publication contains problem determination information for IBM Z System Automation (SA z/OS).This information includes messages, return codes, reason codes and status codes.

Who Should Use This PublicationThis publication is intended for operators and system programmers of Z System Automation (SA z/OS).

How to Use This PublicationThis publication lists all SA z/OS messages, return codes, and reason codes. The messages are sortedalphabetically by the first four characters.

Where to Find More Information

Z System Automation LibraryTable 1 on page ix shows the information units in Z System Automation library. These manuals can bedownloaded from IBM Documentation.

Table 1. Z System Automation library

TitleFormNumber

Description

Get Started Guide SC27-9532 This book is intended for SA z/OS beginners. It contains theinformation about early planning, configuring the product,making it secure, customizing your automation environment,and the basic operational tasks that you perform on a dailybasis.

Planning and Installation SC34-2716 Describes SA z/OS new capabilities and how to plan, install,configure, and migrate SA z/OS.

Customizing andProgramming

SC34-2715 Describes how to adapt the standard installation, add newapplications to automation, write your own automationprocedures, monitor applications, enable alerting, and more.

Defining Automation Policy SC34-2717 Describes how to define and maintain the automation policy.

User's Guide SC34-2718 Describes SA z/OS functions and how to use SA z/OS tomonitor and control systems.

Messages and Codes SC34-2719 Describes the problem determination information ofSA z/OS, including messages, return codes, reason codes,and status codes.

Operator's Commands SC34-2720 Describes the operator commands available with SA z/OS,including their purpose, format, and specifics of how to usethem.

Programmer's Reference SC34-2748 Describes the programming interfaces of SA z/OS and thedefinitions for the status display facility (SDF).

© Copyright IBM Corp. 1996, 2019 ix

https://www.ibm.com/docs/en/z-system-automation/4.2.0?topic=downloadable-pdf-files

Table 1. Z System Automation library (continued)

TitleFormNumber

Description

End-to-End Automation SC34-2750 Describes the end-to-end automation adapter for z/OS andhow it enables end-to-end automation and how it connectsto Service Management Unite Automation.

Service Management UniteAutomation Installationand Configuration Guide

SC27-8747 Describes how to plan, install, set up, configure, andtroubleshoot Service Management Unite Automation.

Product AutomationProgrammer's Referenceand Operator's Guide

SC34-2714 Describes how to customize and operate productautomation components (CICS, Db2, and IMS automation)with SA z/OS to provide a simple and consistent way tomonitor and control all of the CICS, Db2, and IMS regions,both local and remote, within your organization.

Workload SchedulerProgrammer's Referenceand Operator's Guide

SC34-2749 Describes how to customize and operate ZWS/TWSAutomation.

Related Product InformationFor information that supports Z System Automation, visit the z/OS library in IBM Documentation (https://www.ibm.com/docs/en/zos).

x IBM Z System Automation Messages and Codes :

https://www.ibm.com/docs/en/zos

https://www.ibm.com/docs/en/zos

Chapter 1. About Z System Automation Messages

This book describes Z System Automation messages and codes. It enables system operators and systemprogrammers to respond to messages appropriately and efficiently.

Format of Z System Automation MessagesEach Z System Automation system message begins with a unique message identifier, followed bymessage text.

In general, the message format is as follows:

XXXynnnt MESSAGE TEXT

where:

XXX or XXXXIs the program identifier. It identifies where in Z System Automation the message originated from. Itcan have three or four characters

• AOF: System operations• EVE: CICS®-related messages• EVI : IMS-related messages• EVJ: TWS-related messages• HSA: Automation manager• ING: Z System Automation, general parts• ISQ: Processor operations

YIs the Z System Automation component specific identifier.

nnnIs the message identification number. It is a three-digit or four-digit number that uniquely identifieseach message.

tIs the message type. It is a letter that helps indicate the purpose of the message and the type ofresponse required for the message. The message types are:A

Immediate Action. Requires the system operator to do something now. The associated task doesnot continue until the operator performs the requested action.

DImmediate Decision. Requires the system operator to make a decision and select a reply nowfrom the available options specified on the message. The associated task does not continue untilthe operator responds to the system.

EEventual Action. Requires eventual action by the system operator. The associated task continuesindependent of the operator action.

IInformation. Requires no action. This message is used only for advisory purposes.

WSystem Wait. Requires system operator action immediately. The system or a major subsystemmust be restarted.

About Z System Automation Messages

© Copyright IBM Corp. 1996, 2019 1

Message TextThe message text provides concise information about an event or condition of interest to an operator orsystem programmer. Variable text is used to identify system components and to provide other detailedinformation. 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 singleoccurrence 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 bybrackets ([ and ]).

In some cases " - FROM=sysname" is appended to the message text, where sysname indicates the systemwhere the message originated. This normally applies where the message was received by a slave processrunning on a remote system.

Who Receives MessagesZ System Automation 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 Z System Automation notification messages, ormessages about actions Z System Automation either detects or takes. Notification messages are routedto one or more assigned, logged-on operators. Notification operators can be defined the following ways:

• Using the Operator Notification panel in the customization dialogs. Refer to IBM Z System AutomationDefining Automation Policy for further information on how to use the customization dialogs.

• Using the INGNTFY command. Refer to IBM Z System Automation User's Guide for more information onhow to use the INGNTFY command.

Displaying Notification Operator SettingsIf 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.

AOFKAANT SA z/OS - Command Dialogs Line 1 of 3 Domain ID = IPSNO ---------- INGNTFY ---------- Date = 09/15/11 Operator ID = OPID Time = 10:22:29 Cmd: A Add C Show/Change settings D Delete O Turn OFF msg receiving Cmd Operator System Log Rcv Description Classes --- -------- -------- --- --- ----------- ------- AUTNOTI1 AOC4 Y N MSG AOP NOTI1 AOC4 N Y 40 41 42 43 44 NOYI2 AOC4 Y Y 80 81 82 Command ===> PF1=Help PF2=End PF3=Return PF6=Roll PF9=Refresh PF12=Retrieve

Figure 1. Example DISPNTFY Command Dialog


2 IBM Z System Automation Messages and Codes :

Notification operators can be logged on without receiving messages if they have used the INGNTFYcommand to turn off messages. Refer to IBM Z System Automation User's Guide for further information.

Message ClassesSome messages generated by Z System Automation 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 classmatching the message’s class receives the message.

To find out which classes of messages are assigned to each operator, use the customization dialogs. Forfurther information on the customization dialogs, refer to IBM Z System Automation Defining AutomationPolicy.

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

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


Chapter 1. About Z System Automation Messages 3

Table 2. Message Classes (continued)

Message Class Description

89 Satisfactory: All resources

90 SA z/OS Infrastructure/Environment

MVS Descriptor CodesThe Z System Automation AOCMSG common automation routine handles descriptor codes to assist in themanagement 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.



Chapter 2. Messages AOF000I to AOF969I

AOF000I MESSAGE message_numberISSUED BUT DOES NOT EXIST INMESSAGE TABLE table - CALLIGNORED

ExplanationSystem automation attempted to issue a message, butno text could be found for the message in the messagetable.

The variable message_number shows the numberof the message that text was missing for.The variable table shows the name of the messagelibrary member that the message should have beenfound in.

System actionNone.

Operator responseNone.

System programmer responseThis message indicates that there might have been aproblem installing Z System Automation. Make surethe message library is allocated to DSIMSG DD.

ClassesNone.

AOF001I REQUEST request WASSUCCESSFUL FOR entry_type

ExplanationThe request for the record has been completedsuccessfully.

The variable request shows the function performedon the record.The variable entry_type shows the function or key ofthe record that was processed.

System actionNone.


System programmer responseNone.

ClassesNone.

AOF002I END OF MULTILINE MESSAGEGROUP

ExplanationThis message identifies the end of a multiline messagegroup.

System actionNone.



ClassesNone.

AOF003I function IS NOT ACTIVE

ExplanationAn operator dialog issues this message. An inactive PFkey was pressed.

The variable function shows the PF key that waspressed.

System actionNone.

Operator responsePress a key that is active. For more information, callhelp from the panel that this message appears on.


Messages AOF000I to AOF969I


ClassesNone.

AOF004I PROCESSING FAILED FORcommand COMMAND

ExplanationThe entered command (command) failed to process.This could be because of an error, or because thecommand requested something that was already ineffect. Other messages preceding this one indicate thereason for the failure.

System actionNone.

Operator responseMake sure the proper command was entered and lookfor messages preceding this message to determine thecause of the failure. If you cannot determine the causeof the failure, contact your system programmer.

System programmer responseReview the netlog (which was active at the time thecommand was rejected) to see whether a messagewas routed correctly.

ClassesNone.

AOF005I MEMBER member CURRENTLYBEING action FOR THE CONTROLFILE

ExplanationThis is the first line of a multiline message group.

• The variable member shows the name of themember currently being used.

• The variable action shows where the automationcontrol file resides. It can be one of the following:USED

The status display is for the current in-storagemember

SAVEDThe status display is for the currently savedmember

System actionNone.



ClassesNone.

AOF006I text

ExplanationThis message is part of a multiline message group thatbegins with message AOF005I.

• The variable text shows detailed information aboutan automation control file. It can be one of thefollowing:

BUILT BY name ON date AT TIMELOADED BY name ON date at timeCONFIGURATION TOKEN = tokenCONFIGURATION DATASET = dataset_name

The variable name shows the name of anoperator.The variable date shows the date the action wasdone.The variable time shows the time the action wasdone.The variable token shows the currentconfiguration token.The variable dataset_name shows the name ofcurrent configuration data set.

System actionNone.



ClassesNone.

AOF007I A RESOURCE TYPE IS REQUIREDFOR THIS SELECTION



ExplanationA resource type was not entered as a selection on theprompt screen.

System actionNone.

Operator responseEnter the resource type.


ClassesNone.

AOF008I A SELECTION MUST BE MADE

ExplanationAn operator dialog issues this message. This messageindicates that you must make a selection on theprompt screen.

System actionNone.

Operator responseMake a selection on the prompt screen. For moreinformation, call help from the panel that this messageappears on.


ClassesNone.

AOF009I MAXIMUM NUMBER OF keywordOPERANDS EXCEEDED

ExplanationThe maximum number of operands allowed for thekeyword identified in this message was exceeded.

The variable keyword shows the keyword that toomany operands were specified for.

System actionNone.

Operator responseEnter the command again, making sure that thecorrect number of operands is specified for thekeyword you specify.


ClassesNone.

AOF010I WRONG NUMBER OFPARAMETERS ENTERED

ExplanationToo few or too many parameters were entered with acommand or request.

System actionNone.

Operator responseEnter the command or request again, this time usingthe right number of parameters.


ClassesNone.

AOF011I EXPECTING AN ENDING delimiterFOR parameter

ExplanationThe operand was entered without a closing delimiter.

The variable delimiter shows the characterexpected as the delimiter.The variable parameter shows the parameter thatwas in error.

System actionNone.


Chapter 2. Messages AOF000I to AOF969I 7

Operator responseEnter the command again using the correct delimiter.


ClassesNone.

AOF012I message_ID message_text

ExplanationGeneral purpose message entry. Specifically used formessage forwarding of messages from users or othercomponents. The AOF012I message identifier is notdisplayed to an operator who receives this message.

The variable message_ID shows the messageidentifier of the forwarded message.The variable message_text shows the message textof the forwarded message.

System actionNone.



ClassesNone.

AOF013I SPECIFIED OPERAND operandINVALID FOR parameter

ExplanationAn operand that is not valid was specified for thisparameter.

The variable operand shows the operand that is notvalid.The variable parameter shows the parameter thatwas entered.

System actionNone.

Operator responseEnter the command again using the correct operands.


ClassesNone.

AOF014I SPECIFIED PARAMETERparameter INVALID

ExplanationThe specified parameter (parameter) is not valid forthis command.

System actionNone.

Operator responseEnter the command again using the correctparameters.


ClassesNone.

AOF015I INVALID DELIMITER OF delimiterENCOUNTERED

ExplanationA delimiter that is not valid (delimiter) was entered fora command.

System actionNone.

Operator responseEnter the command again using the correct syntax.




ClassesNone.

AOF016I Too few screen rows (min. nnrequired).

Explanation:The function requires at least the indicated number ofrows for displaying the panels.

System action:The function is terminated.

Operator response:Use a terminal that fits the required screen size andredo the function.

System programmer response:None.

ClassesNone.

AOF017I EXPECTED PARAMETER(S)MISSING FOR REQUEST request

ExplanationRequired parameters for this request are missing ornull. If a parameter was entered, no operand wasspecified.

The variable request shows the request used.

System actionNone.



ClassesNone.

AOF018I INVALID SEARCH RANGESPECIFIED

ExplanationThe specified starting search range is greater than theending search range.

System actionNone.



ClassesNone.

AOF019I time: INVALID SYNTAX FORCOMMAND cmd_name parmstr

ExplanationCommand cmd_name was invoked with invalid syntaxon the command line.

The variable time shows the time the error wasgenerated.The variable cmd_name is the name of the failingcommand.The variable parmstr is the parameter string passedto the failing command, where available.

System actionProcessing is terminated.

Operator responseIf operator initiated, correct and reissue the command,otherwise contact your system programmer.

System programmer responseCorrect and reissue the command.

ClassesNone.

AOF020A macro/type REQUEST WASUNSUCCESSFUL RC=rc A=xx I=yyFOR function

ExplanationThe program made a macro type request. The macrowas not able to satisfy the request and returned valuesfor use in problem determination. These values aredisplayed in this message.

The variable macro/type shows the request type.



The variable rc shows the return code from themacro.The variable xx shows the major return code from aVSAM request.The variable yy shows the minor return code from aVSAM request.The variable function shows the name of the macro.

System actionNone.

Operator responseContact your system programmer.

System programmer responseCheck the VSAM return code values to determine thecause of the problem.

ClassesNone.

AOF021I CONFLICTING PARAMETERSparameters SPECIFIED forcommand

ExplanationAn invalid combination of parameters was specified forcommand. The variable parameters lists the conflictingparameters. The variable command shows the name ofthe issued command.

System actionNone.

Operator responseEnter the command again with a valid combination ofparameters

System programmer responseNone

ClassesNone.

AOF022E MODULE module DETECTEDERROR IN SERVICE service. RC=rc,RS=rs

ExplanationA service was invoked and returned an unexpectedreturn code or reason code. This message is logged inthe netlog.

The variable module shows the name of the modulethat invoked the service.The variable service shows the name of the servicethat was invoked.The variable rc shows the return code that wasreceived.The variable rs shows the reason code that wasreceived.

System actionProcessing stops. The message is logged in the netlog.

Operator responseRefer to the documentation of the service that wasinvoked for more information.


ClassesNone.

AOF024I A NULL FIELD WAS ENTERED

ExplanationA null field is not acceptable.

System actionNone.

Operator responseCorrect the command syntax and reissue thecommand.


ClassesNone.

AOF025I SYNTAX ERROR FOR command



ExplanationA syntax error was encountered in the command thatwas entered.

System actionNone.



ClassesNone.

AOF026I module DETECTED A VERSIONMISMATCH. REASON nn

ExplanationModule module detected a version mismatch.

• The variable module shows the name of the modulethat invoked the service.

• The variable rs shows the reason code. Valid reasoncodes are:01

The version of AOFRASFX does not match.02

The version of a status file record does notmatch.

System actionThe request is not processed.

Operator responseCheck the system setup and reissue the command.


ClassesNone.

AOF027I THE FOLLOWING SA AUTOMATIONOPERATORS COULD NOT BESTARTED:

ExplanationThis is the first message of a multiline message groupthat lists all automation operators that could not bestarted.

System actionNone.



ClassesNone.

AOF028I automation operator name -NETVIEW TASK taskname status


• The variable automation operator name shows thename of the SA z/OS automation operator that couldnot be started.

• The variable taskname shows the name of theNetView task that caused the problem.

• The variable status shows:

– UNDEFINED if the NetView task is currently notdefined.

– INACTIVE if it could not be started.

System actionNone.


System programmer responseDefine the missing NetView task names or review thenetlog for reasons why it could not be started.

ClassesNone.



AOF029I DYNAMIC ADD OF SAAUTOMATION OPERATORS FAILED

ExplanationThis message follows the multiline message group thatbegins with message AOF027I.

System actionNone.


System programmer responseDefine the missing NetView task names (see messageAOF028I) or review the netlog for reasons why it couldnot be started.

ClassesNone.

AOF030I task_name IS INACTIVE

ExplanationThe called task (task_name) is not active at this time.

System actionNone.

Operator responseStart the task by issuing START TASK=xxxxxxx, wherexxxxxxx is:

• AOFTSTS for the status file


ClassesNone.

AOF031I Configuration Refresh on 'system'is 'status'.

ExplanationThe message is generated when the status of theconfiguration refresh changes. It shows the actualstatus of the configuration refresh.

The variable system shows the system name where theconfiguration refresh is processed.

The variable status shows the actual status of theconfiguration refresh.

System action:None.

Operator response:None.


ClassesNone.

AOF032I USAGE util %, LONG LINEARpred1, SHORT LINEAR pred2, 1STORDER pred3

ExplanationThis message is posted to SDF when JES2 spoolrecovery has been initiated and SA z/OS makespredictions about future spool usage. There are threedifferent prediction methods:Long Linear

This method looks at the first data point and thelatest data point, and does a linear extrapolation topredict how long it will take for the spool to reach100% utilization.

Data points occur if either the pass processor runs,or a spool recovery initialization message(HASP050 or HASP355) is received.

Short LinearThis method is like long linear, but is based on thelast two data points.

Short 1st OrderThis method takes the last 3 data points, works outthe rate of change between each pair ofconsecutive points, then works out the variationbetween these two rates of change. It thenextrapolates using this quadratic variation topredict when the spool will reach 100% utilization.

• The variable util shows the current percentutilization of all active spool volumes.

• The variables pred1, pred2, pred3 are spool usagepredictions. They can have the following values:hh:mm:ss

The predicted time for the spool to reach 100%utilization.

NONEInsufficient data points were collected to makethe prediction.



STABLEThere is no change in spool usage between thedata points. Spool usage is neither increasing nordecreasing.

SAFEThe projected spool usage falls below the lowestdata point rather than reaching 100% utilization.

DROPPINGThe latest data point is lower than the others.

FULLThe current data point shows 100% spoolutilization.

System actionNone.



ClassesNone.

AOF035I MEMBER member I/O ERROROCCURRED WHILE PROCESSING

ExplanationAn I/O error occurred during processing of themember identified by the variable member.

System actionProcessing ends.

Operator responseMake sure the member identified in the message isvalid. If the member identified in the message is valid,contact your system programmer for further analysis.

System programmer responseVerify that the member name exists in the file pointedto by the procedure in use at the time of the error.Review the netlog being used at the time of the errorto see whether there was a system error that couldhave prevented the member from being found.

ClassesNone.

AOF036I MEMBER member could not beprocessed.

ExplanationAn error occurred during processing of the membermember. The netlog file active at the time of the failuremight contain information indicating why theprocessing failed.

If the member name contains INGWHYIN, INGWHYU,or INGWHYSA, this member must reside in a librarythat is part of the DSIPARM concatenation. INGWHYINis created temporarily as an in-storage member byroutine INGWHY. INGWHYIN is a Data REXX file that isbuilt from either INGWHYU or INGWHYSA. Thismessage appears while reading or writing thereferenced member(s).

The variable member shows the name of themember currently being used

System actionIf the member name contains INGWHYU orINGWHYSA, further processing depends on thecontext:

• If INGWHYU is displayed, processing continues.• If INGWHYSA is displayed, processing stops.

Operator response:Contact your system programmer.

System programmer responseIf the member name contains INGWHYU, verify thatINGWHYU is defined as a Data REXX module in Logicmode. The first 9 characters in the first line mustcontain the keyword '/*%LOGIC' .

If the member name contains INGWHYU orINGWHYSA, verify that INGWHYU and INGWHYSA aremembers of a DSIPARM library. If the DSIPARM libraryis allocated using dynamic extents, then verify whetherDD DSIPARM must be reaccessed.

Analyze the messages that are related to the failedrequest in the NetView log to determine the cause ofthe failure. If the messages in the NetView log refer toINGWHYIN and message AOF036I contains INGWHYUor INGWHYIN, then a typical error is a Data REXXsyntax error. Correct the code in INGWHYU.

ClassesNone.

AOF040I CONTROL FILE INACTIVE



ExplanationA request to the automation policy was not successfulbecause the automation control file was not active.This message can also be a response to the ACFSTATUS command.

System actionNone.

Operator responseTo activate the automation control file, specify the ACFREFRESH or the INGAMS command.


ClassesNone.

AOF041I UNABLE TO FIND entry type

ExplanationThe task did not find any data for the specified entry-type pair.

The variable entry shows the entry field of theentry-type pair the task tried to locate.The variable type shows the type field of the entry-type pair the task tried to locate.

System actionNone.



ClassesNone.

AOF042I MEMBER name NOT FOUND

ExplanationSA z/OS attempted to prepare the member named inthe message but could not find it.

The variable name is the name of member thatcould not be found.

System actionProcessing continues.


System programmer responseMake sure that the member identified in the messageis valid. Add the member in the DSIPARMconcatenation chain or correct the SDF paneldefinitions that refer to the erroneous member.

AOF043I task IS ACTIVE

ExplanationThe task task has been activated.

System actionNone.



ClassesNone.

AOF044I task IS TERMINATING

ExplanationThe task task is ending.

System actionNone.





ClassesNone.

AOF045I task TERMINATED

ExplanationThe task task has ended.

System actionNone.



ClassesNone.

AOF057I REQUEST FAILED. TIMERID=timer_ID ALREADY EXISTS

ExplanationAn attempt was made to add a timer ID that alreadyexists.

The variable timer_ID shows the timer ID thatalready exists.

System actionNone.

Operator responseSpecify a timer ID that does not already exist.


ClassesNone.

AOF058I AOFCTMSG ERROR -message_number

ExplanationThe status display facility attempted to issue themessage indicated, but no text could be found for themessage in its internal message table (AOFCTMSG).

The variable message_number shows the numberof the message that text was missing for.

System actionNone.


System programmer responseDetermine what operation was being performed whenthe error occurred, and note the message number. Thisinformation should be forwarded to your IBM productsupport contact.

ClassesNone.

AOF059I REQUEST FOR name LOCKS TO BECLEARED WAS CANCELED

ExplanationThe request to clear locks was canceled. No lockswere cleared.

The variable name shows the subsystem namewhose locks were to be cleared.

System actionNo locks were cleared.



ClassesNone.

AOF060I OPERATOR ID operator_ID NOTFOUND



ExplanationThe operator ID identified in this message(operator_ID) was not found.

System actionNone.

Operator responseSpecify the operator ID again.


ClassesNone.

AOF064I time: ident WAITING FOR event

ExplanationAutomation is waiting for an event to complete.

The variable time shows the time the message wasissued.The variable ident shows the CLIST that issued themessage.The variable event shows the event the CLIST iswaiting for.

When event is "PAM GETTING READY", it means thatthe automation registration-related processing iswaiting until the Primary Automation Manager is readyto process requests.

System actionSystem automation waits until the event hascompleted.



Classes40, 43.

AOF069I data

ExplanationThis message is given in conjunction with asubsequent error message that explains what isincorrect. It shows the SDF panel statement that isincorrect.

The variable data identifies the buffer data in error.

System actionNone.


System programmer responseCorrect the panel definitions.

ClassesNone.

AOF076I REPEAT FIND WILL NOT WORKUNTIL YOU HAVE ISSUED A FIND

ExplanationTo use the repeat function a find command must havebeen entered previously.

System actionThe requested command is not performed.

Operator responseSpecify a find command first, for example, FIND abc.


ClassesNone.

AOF077I USE P OR N TO SPECIFY FINDDIRECTION

ExplanationAn invalid value for the find direction has beenspecified. P and N are valid values.

System actionThe requested command is not performed.



Operator responseSpecify P (previous) or N (next) for the direction of theFIND command, for example, FIND abc N.


ClassesNone.

AOF078I subsys SPOOL RECOVERED TOBELOW nn%, text

ExplanationSystem automation SPOOL recovery was successful.

The variable subsys shows the name of thesubsystem.The variable nn% shows the spool percentage.The variable text shows either RECOVERY STOPPEDor RECOVERY DONWGRADED TO SHORT.




Classes40, 43.

AOF081I SECURITY FACILITY IS NOTACTIVE

ExplanationA request or function was not performed, because thesecurity facility was not active.

System actionNone.

Operator responseTake steps to activate the security facility. Contactyour system programmer.

System programmer responseDetermine why the security facility was not active andtake steps to ensure that it is available whennecessary.

ClassesNone.

AOF082I SAVE REQUEST REJECTED –ORIGINAL DATA HAS BEENMODIFIED

ExplanationA request to save changed data was issued. However,the original data that you have changed has in themeantime been modified by another process and is nolonger up-to-date. The request is therefore rejected.

System actionThe requested function is not performed.

Operator responseRefresh the displayed data and redo the changesbased on the new data.


ClassesNone.

AOF083I FIELD field_name EXCEEDS THEALLOWABLE FIELD LENGTH

ExplanationThe field identified in this message (field_name) is toolong.

System actionNone.

Operator responseDetermine the correct length for the field and try theoperation again.




ClassesNone.

AOF084I PARAMETERS EXCEED THEMAXIMUM LENGTH

ExplanationThe command could not be processed because theparameters exceeded the maximum length.

System actionNone.

Operator responseTry to reduce the length of the parameters.


ClassesNone.

AOF085I PRESS PF5 TO SAVE OR PF3AGAIN TO IGNORE CHANGES

ExplanationFunction key PF3 has been issued to leave a panelwithout having saved temporary modifications of thedisplayed data. The requested function is rejected.


Operator responseFollow the instruction of the message.


AOF086I time : phase DEFINITIONS TOsubsystem RESTORED BY task

ExplanationThis message is written to the NetView log whenpreviously stored start or stop definitions to anapplication have been restored after they have beenmodified.

The variable time shows the time this message wasgenerated.The variable phase shows whether START or STOPdefinitions have been modified.The variable subsystem shows the name of theresource.The variable task shows the name of the task thatrequested the function.




AOF087I action REQUEST REJECTED -phase IN PROGRESS

ExplanationA request was issued to save modified start or stopdefinitions for an application or to discard changes byresetting the previously loaded definitions.

• The variable action shows whether a save or resetfunction has been requested.

• The variable phase shows the reason why therequested 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.


Operator responseReissue the request either after the start or stop of theapplication has completed or after SA z/OS hasinitialized.


AOF088I command: COMMAND ONLYALLOWED IN FULLSCREEN MODE



ExplanationA command was issued that is only allowed infullscreen mode. The command is rejected becausethe executing task does not support fullscreen mode.

The variable command shows the command thatwas issued.

System actionNone.



AOF089I time : phase DEFINITIONS TOsubsystem MODIFIED BY task

ExplanationThis message is written to the NetView log when startor stop definitions to an application have beenmodified during runtime.

The variable time shows the time this message wasgenerated.The variable phase shows whether START or STOPdefinitions have been modified.The variable subsystem shows the name of theresource.The variable task shows the name of the task thatrequested the function.




AOF090I IPLDATE= date, IPLTIME= time

ExplanationThis message shows the date and time of the lastinitial program load (IPL).

System actionNone.



ClassesNone.

AOF094I operator_ID IS NOT AUTHORIZEDTO USE INGNTFY COMMAND

ExplanationAn operator dialog issues this message. An operatorwho is not authorized to use the INGNTFY commandattempted to do so.

The variable operator_ID shows the ID of theoperator who attempted to use the command.

System actionNone.

Operator responseIf you need more information about this message, callhelp from the panel that this message appears on.


ClassesNone.

AOF095I function_name FUNCTIONSUCCESSFULLY COMPLETED

ExplanationAn operator dialog issues this message. Processing ofa function called by a command has been successfullycompleted.

The variable function_name identifies the functionthat processing has been completed for.

System actionNone.



Operator responseNone. For more information about this message, callhelp from the panel that this message appears on.


ClassesNone.

AOF096I A COMMAND MUST BE SPECIFIED

ExplanationYou are expected to enter a command.

System actionNone.

Operator responseEnter a command.


ClassesNone.

AOF097I A RESOURCE NAME IS REQUIREDFOR THIS SELECTION

ExplanationYou made an operator dialog panel selection thatrequires a resource name, but you did not enter aresource name.

System actionNone.

Operator responseEnter a resource name. For more information, requesthelp for this operator dialog panel.


ClassesNone.

AOF098I COMMAND FAILED - REFER TONETVIEW LOG

ExplanationProcessing of a request or function failed to becompleted successfully. The netlog file active at thetime of the failure might contain information indicatingwhy processing failed.

System actionNone.


System programmer responseReview the netlog for messages related to the requestthat failed. Determine the cause of the failure byanalyzing these messages. If there are no relatedmessages, determine whether the command is stillactive on the maintenance level that was active whenthis message was generated.

ClassesNone.

AOF099I FUNCTION COMPLETED

ExplanationAn operator dialog issues this message. It indicatesthat processing of the command completed. If no errormessage is shown previously, it also indicates that thefunction completed successfully.

System actionNone.



ClassesNone.



AOF100I time: command COMMAND ISSUEDdata

ExplanationThe request you made has been processed or hasbeen issued and is processing.

The variable time shows the time this message wasgenerated.The variable command shows the name of thecommand that failed.The variable data shows detailed information aboutwhere the command was issued.

System actionNone.



Classes. 40 43.

AOF101I CONFIRMATION RESPONSE ISREQUIRED

ExplanationAn operator dialog issues this message.

System actionNone.

Operator responseFor more information, call help from the panel that thismessage appears on.


ClassesNone.

AOF102I CORRECT FIELDS IN ERROR


System actionNone.



ClassesNone.

AOF103I CURRENT TIME PAST REQUESTEDTIME time

ExplanationA time that has already passed was specified. Thespecified time cannot be processed.

The variable time shows the time specified in therequest.

System actionNone.

Operator responseSpecify a valid time in the request.


ClassesNone.

AOF104I DEFAULT (IF ANY) IN WHITE, NONEED TO ENTER SEL NUMBER

ExplanationOn the NNT selection panel, the first defined session isthe default selection for initiation/termination. It isselected automatically if you do not enter a selectionnumber.

System actionNone.





ClassesNone.

AOF105I DELETE SUCCESSFUL

ExplanationA request to delete is complete.

System actionNone.



ClassesNone.

AOF106I ENTER A SELECTION


System actionNone.



ClassesNone.

AOF107I ENTER TO DISPLAY

ExplanationAn operator dialog issues this message. This messageis usually displayed after an invalid command isentered.

System actionNone.

Operator responseMake a selection from the list displayed on the paneland press the key designated as the Enter key.


ClassesNone.

AOF108E ERROR OCCURRED DURINGprocess PROCESS

ExplanationAn error occurred during the process identified in thismessage.

The variable process shows the name of theprocess during which the error occurred.

System actionNone.

Operator responseNotify your system programmer.

System programmer responseExamine other messages related to the process toidentify the error and its cause.

ClassesNone.

AOF109I EXITS CANNOT BE ENABLED -EXITS DO NOT EXIST

ExplanationAn attempt was made to enable exits. Because noexits exist, no action was performed.



System actionNone.



ClassesNone.

AOF110I name BEING USED FOR THEAUTOMATION CONTROL FILE -origin

ExplanationThe automation control file member was either loaded,restored, or refreshed successfully.

• The variable name shows the name of the memberthat was loaded.

• The variable origin shows where the automationcontrol file came from. It can be:

LOADED from data sets in the DSIPARMconcatenation.RESTORED using NetView Save/Restore facility.REFRESHED as for LOADED but from changeddata only.

System actionNone.



ClassesNone.

AOF111I AUTOMATION CONFIGURATIONDISPLAY - ENTRY= entry

ExplanationThis is the first message of a multiline message groupthat displays the current automation configuration.

The variable entry shows the name of the entry thatwill be displayed.

System actionNone.



ClassesNone.

AOF112I ACTIVE TYPE= active_type ,DESIRED TYPE= desired_type


The variable active_type shows the name of thetype that satisfied the request.The variable desired_type shows the name of thetype that was requested.

System actionNone.



ClassesNone.

AOF113I DATA IS data


The variable data shows the data area of the entryand type being displayed.



System actionNone.



ClassesNone.

AOF114I REQUESTED STATE state FORSUBSYSTEM subsystem ISALREADY SET


The variable state shows the requested state.The variable subsystem shows the affectedsubsystem.

System actionNone.



ClassesNone.

AOF115I REQUESTED TIMERtimer_identification WASCHANGED

ExplanationThe requested timer change was made.

The variable timer_identification shows the name ofthe timer that was changed.

System actionNone.



ClassesNone.

AOF116I REQUESTED TIMERS WEREDELETED

ExplanationThe request to delete timers was completedsuccessfully. The timers specified in the request weredeleted.

System actionNone.



ClassesNone.

AOF117I RETURN CODE return_codeRECEIVED FROM LIST TIMERCOMMAND

ExplanationA non-zero return code was generated duringprocessing of the LIST TIMER command. Processing ofthe request is not complete.

The variable return_code shows the return codegenerated.

System actionNone.




System programmer responseRefer to the description of the NetView LIST TIMERcommand in IBM Z NetView Command ReferenceVolume 1 (A-N) for an explanation of the return code.

ClassesNone.

AOF118I SECOND PARAMETER SHOULD BEBLANK OR T

ExplanationA non-blank value other than "T" was specified for thesecond parameter of the entered command. Thisparameter must be blank or have a value of T.

System actionNone.

Operator responseEnter the command again, specifying valid values forall parameters.


ClassesNone.

AOF119I SELECT ONE PARAMETER THENPRESS THE ENTER KEY

ExplanationThis message is a prompt for you to select aparameter.

System actionNone.

Operator responseSelect a parameter and press the Enter key.


ClassesNone.

AOF121I HIT ENTER KEY

ExplanationThis message is a prompt for you to press the Enterkey.

System actionNone.

Operator responsePress the key on your keyboard that performs theEnter function.


ClassesNone.

AOF122I INVALID CONFIRMATIONREQUEST OF function ENTERED

ExplanationAn operator dialog issues this message. A confirmationrequest that is not valid was entered.

The variable function shows the request entered.

System actionNone.

Operator responseEnter a valid confirmation request. For moreinformation about this message, call help from thepanel that this message appears on.


ClassesNone.

AOF123D INVALID INPUT -- ENTERCOMMAND, SET COMMAND, T TOTERMINATE OR I TO INITIATE

ExplanationData that is not valid was entered.



System actionNone.

Operator responseEnter one of the following:

• A valid command• SET• T• I


ClassesNone.

AOF124D INVALID INPUT -- ENTER IMSCOMMAND, SET COMMAND OR TTO TERMINATE

ExplanationData that is not valid was entered.

System actionNone.

Operator responseEnter the data again, making sure that it is valid.


ClassesNone.

AOF125A INVALID OPERATOR ID - PLEASERE-ENTER

ExplanationAn operator ID that is not valid was entered.

System actionNone.

Operator responseEnter a valid operator ID.


ClassesNone.

AOF126A INVALID PASSWORD - PLEASE RE-ENTER

ExplanationA password that is not valid was specified.

System actionNone.

Operator responseEnter a valid password.


ClassesNone.

AOF129I INVALID SELECTION


System actionNone.

Operator responseFor more information, call help from the panel that thismessage appears on. Choose an option that is withinthe valid range.


ClassesNone.

AOF130I INVALID SUBSYSTEM NAMEinvalid_name



ExplanationAn operator dialog issues this message. This messagemay also be issued during the automation control fileload or refresh.

The variable invalid_name shows the invalid name.

System actionFor automation control file load or refresh the Entry/Type is ignored.

Operator responseFor more information, call help from the panel that thismessage appears on. If the message is issued duringthe configuration file load or refresh then the Entry/Type in the file must be corrected.


ClassesNone.

AOF131I MISSING OR INVALID parameter

ExplanationA parameter or keyword in the entered command ismissing or is not valid.

The variable parameter shows the parameter orkeyword that is missing or is not valid.

System actionNone.

Operator responseSpecify valid parameters and reissue the command.


ClassesNone.

AOF132I NO AUTOMATION FLAGS SET


System actionNone.



ClassesNone.

AOF133I NO ENTRIES HAVE BEEN DEFINED

ExplanationThe information that was requested does not exist.

System actionNone.



ClassesNone.

AOF134I NO FUNCTION WAS SELECTED

ExplanationYou did not specify a function.

System actionNone.

Operator responseSpecify a function.




ClassesNone.

AOF135I NO HELP PANEL IS AVAILABLE

ExplanationHelp information was requested when none isavailable.

System actionNone.



ClassesNone.

AOF136I NO MORE HELP IS AVAILABLE

ExplanationAll available help text has been displayed.

System actionNone.



ClassesNone.

AOF137I NO NOTIFY OPERATORS DEFINED

ExplanationThe request was not performed, because there are nonotify operators.

System actionNone.



ClassesNone.

AOF138I NO SCHEDULED AUTOMATIONOVERRIDES


System actionNone.



ClassesNone.

AOF139I NO THRESHOLDS DEFINED - ATLEAST ONE THRESHOLD VALUE ISREQUIRED

ExplanationNo threshold values have been defined. You mustdefine at least one threshold value.

System actionNone.


System programmer responseDefine at least one threshold value. For informationabout defining threshold values, refer to IBM Z SystemAutomation Defining Automation Policy.



ClassesNone.

AOF140I NO TIMERS ARE SCHEDULED

ExplanationNo timers are scheduled, so there is nothing to display.

System actionNone.



ClassesNone.

AOF141I NUMBER 0 IS NOT VALID

ExplanationThe value "0" was specified for the field. This is not avalid value for the field.

System actionNone.

Operator responseSpecify a valid value for the field.


ClassesNone.

AOF142I ONLY ONE DATE/DAY MAY BESPECIFIED

ExplanationMore than one day or date was specified. Only one dayor date can be accepted.

System actionNone.

Operator responseSpecify only one day or date.


ClassesNone.

AOF143I ONLY ONE SELECTION ISALLOWED, PLEASE RESPECIFY

ExplanationMore than one selection was made. Only one selectioncan be accepted.

System actionNone.

Operator responseMake only one selection.


ClassesNone.

AOF144I PARAMETER parameter_nameINVALID

ExplanationAn operator dialog issues this message. A parameterthat is not valid (parameter_name) was entered.

System actionNone.





ClassesNone.

AOF145I PARAMETER MISSING


System actionNone.



ClassesNone.

AOF146I PARAMETER MUST BE NUMERIC

ExplanationA non-numeric value was entered in a field thatrequires a numeric value.

System actionNone.

Operator responseEnter a numeric value for the field.


ClassesNone.

AOF147I REPLY FAILED - REFER TONETWORK LOG

ExplanationThe reply failed. The netlog contains additionalinformation about the failure.

System actionNone.


System programmer responseMake sure the reply specification is correct. Identifyand correct any other causes of the failure.

ClassesNone.

AOF148I REPLYID IS NOT VALID, CORRECTAND RE-ENTER

ExplanationThe reply ID is not valid.

System actionNone.

Operator responseEnter a valid reply ID.


ClassesNone.

AOF149I REQUEST FAILED. DATE/TIME(date time) IS INVALID

ExplanationThe date or time specified is not valid.

The variable date shows the date specified.The variable time shows the time specified.

System actionNone.

Operator responseSpecify a valid date and a valid time. Make sure thatthe day you specify is valid for the month and year youspecify, and that the time is specified in 24-hour-clockformat.




ClassesNone.

AOF150I STATISTICS DISPLAY REQUESTEDFOR from_resource THRUto_resource

ExplanationThis is the first message in a group of messages thatdisplay statistics from a resource structure.

The variable from_resource shows the highestresource name in the resource structure requestedto be displayed.The variable to_resource shows the lowest resourcename in the resource structure requested to bedisplayed.

System actionNone.



ClassesNone.

AOF151I ID= resource , TYPE= type ,STATUS= status


The variable resource shows the name of theresource being displayed.The variable type shows the type of resource beingdisplayed.The variable status shows the status of theresource being displayed.

System actionNone.



ClassesNone.

AOF152I LAST UPDATED BY operator_ID ,RECORD TYPE= record_type


The variable operator_ID shows the ID of theoperator who last updated the record for theresource.The variable record_type shows the type of therecord that was updated.

System actionNone.



ClassesNone.

AOF153I LAST event_type EVENT: TS= datetime , TYPE=type


The variable event_type shows the event type,which is one of START, AVAIL, STOP, or DOWN. Theevent types describe the lifecycle milestones of theresource.The variable date time shows the time stamp in theform mm/dd/yyyy hh:mm:ss.The variable type shows the start or stop type thatis associated with the event.



System actionNone.



ClassesNone.

AOF154I LAST TERMCODE= code


The variable code shows the termination (abend)code.

System actionNone.



ClassesNone.

AOF155I OPERATOR NOTIFIED: notify

ExplanationThis message is part of a multiline message group thatbegins with message AOF150I. This messageindicates whether an operator has been notified of thecurrent error.

System actionNone.



ClassesNone.

AOF156I LAST STATUS CHANGE DATE= mm/dd/yy , TIME= hh.mm.ss , OPER=operator_ID

ExplanationThis message shows the date and time of the laststatus change, and the operator ID at the point of thestatus 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.The variable operator_ID shows the operator ID atthe point of the last status change.

System actionNone.



ClassesNone.

AOF158I USER = information

ExplanationInformational message returning up to 20 charactersof data.

The variable information shows information by user.

System actionNone.





ClassesNone.

AOF159I NO DATA AVAILABLE

ExplanationThis message is part of a multiline message group thatbegins with message AOF150I. There is no error dataavailable for the resource.

System actionNone.



ClassesNone.

AOF160I ERROR COUNT DATE TIME

ExplanationThis message is part of a multiline message group thatbegins with message AOF150I. This message providesthe headings for the data shown in message AOF161I.

System actionNone.



ClassesNone.

AOF161I nn mm/dd/yy hh:mm:ss

ExplanationThis message is part of a multiline message group thatbegins with message AOF150I. This message showsthe current error count (nn) and the date and time ofthe last error.

System actionNone.



ClassesNone.

AOF162I INVALID SCROLL AMOUNT -SPECIFY "HALF", "PAGE", "MAX",OR A NUMBER

ExplanationAn invalid value was entered in the scroll field.

System actionNone.

Operator responseCorrect the scroll amount and retry.


ClassesNone.

AOF163I LAST THRESHOLD EXCEEDED -threshold

ExplanationThis message is part of a multiline message group thatbegins with message AOF150I. The last thresholdsetting for the resource has been exceeded.

The variable threshold shows the last thresholdsetting.



System actionNone.



ClassesNone.

AOF165I REQUEST FAILED. TASKtask_name NOT ACTIVE

ExplanationThe task identified in this message must be active forprocessing of the request to be completedsuccessfully. Because this task was not active, therequest failed.

The variable task_name shows the name of thetask that was not active.

System actionNone.

Operator responseContact your system programmer. Start the taskidentified by task_name and issue the original requestagain.

System programmer responseDetermine why the task identified by task_name wasnot active and correct the problem.

ClassesNone.

AOF166I REQUEST FOR number LOCKS TOBE CLEARED WAS SUCCESSFULLYCOMPLETED

ExplanationA request to clear locks was successful.

The variable number shows the number of lockscleared.

System actionNone.



ClassesNone.

AOF169I THE LAST LINE IS ALREADYDISPLAYED ON THE SCREEN

ExplanationYou tried to scroll forward to display more data on thescreen, but there is no more data to display; the lastline of data is already being displayed.

System actionNone.



ClassesNone.

AOF170I THE TOP LINE IS ALREADYDISPLAYED ON THE SCREEN

ExplanationYou tried to scroll backward to display more data onthe screen, but there is no more data to display; thefirst line of data is already being displayed.

System actionNone.





ClassesNone.

AOF171I TIMEOUT OF number SECONDSEXPIRED

ExplanationProcessing of the request was not completed withinthe number of seconds shown by this message.

The variable number shows the number of secondstaken by processing of the request beforeprocessing was suspended.

System actionNormal system processing proceeds; processing of therequest was suspended.



ClassesNone.

AOF172I TIMER ID MUST BE CHANGED FORADD PROCESSING

ExplanationThe timer ID was not changed for an add operation.

System actionNone.

Operator responseSpecify the timer ID again.


ClassesNone.

AOF173I TIMER SCHEDULED BUT TIMERDISPLAY FAILED

ExplanationThe requested time was set. However, in an attempt toverify the request by displaying the timer ID, theNetView LIST TIMER command failed.

System actionNone.

Operator responseVerify that your requested timer was set.


ClassesNone.

AOF174I UNKNOWN ERROR OCCURRED,REFER TO NETWORK LOG FORDETAILS

ExplanationAn unexpected return code was received, indicating anerror condition. Additional information about the errorcondition can be found in the NetView log.

System actionNone.


System programmer responseCheck the netlog for messages related to the requestthat resulted in the error condition.

ClassesNone.

AOF175I YOU MUST ENTER YOURPASSWORD

ExplanationA password was not entered.



System actionNone.

Operator responseEnter your password.


ClassesNone.

AOF176I YOU MUST ENTER YOUR USER ID

ExplanationA user ID was not specified.

System actionNone.

Operator responseEnter your user ID.


ClassesNone.

AOF177I YOUR REQUESTED NUMBER ISNOT ON THE LIST

ExplanationYour selection number is greater than the number inthe list of valid selections on this panel.

System actionNone.

Operator responseSelect a number that is included in the selection list.


ClassesNone.

AOF179I REQUEST NOT COMPLETED - WAITTIME EXPIRED

ExplanationProcessing of the request was not complete after thelength of time specified as the "wait time." Processingof the request is suspended. Other processingcontinues.

System actionProcessing of the request might be completed afterthis message is issued or the request is incomplete.

Operator responseRetry your request or determine whether itsubsequently completes.


ClassesNone.

AOF180I REQUEST NOT COMPLETED BYcommand_name COMMANDFAILURE

ExplanationProcessing of a request was not completed becausethe command identified in this message failed.

The variable command_name shows the name ofthe command that failed.

System actionNone.


System programmer responseCheck the netlog for related error messages todetermine the reason why the command failed.

ClassesNone.



AOF181I MULTIPLE SELECTIONS NOTALLOWED

ExplanationA command entered on the selection line wasinterpreted as an attempt to select more than oneoption. Only one option can be selected.

System actionNone.

Operator responseSelect one of the options displayed on the panel andpress the key designated as the Enter key.


ClassesNone.

AOF186I parameter PARAMETERSPECIFIED MORE THAN ONCE

ExplanationA parameter was used in a command more than once,or was specified more than once for a subsystemdefinition in the automation control file.

The variable parameter shows the duplicatedparameter.

System actionThe entered command is not processed. Forautomation control file processing the parameter isignored.

Operator responseEnter the command again, using the correct syntax.


ClassesNone.

AOF187I SPECIFIED OPERAND operandINVALID FOR parameter FOR A

CROSS DOMAIN REQUEST TOcross_domain

ExplanationThe specified operand (operand) cannot be used withthe specified parameter (parameter) for a crossdomain request to the specified cross domain(cross_domain).

System actionThe entered command is not processed.



ClassesNone.

AOF188I FROM= AND TO= PARAMETERSARE INVALID FOR REQ=REPL|DELREQUESTS

ExplanationThe FROM parameter and TO parameter specified inthe command are not valid for replace or deleterequests.




ClassesNone.

AOF189I FOR REQ=DEL THE ONLY VALIDPARAMETER IS: ID=

ExplanationA parameter other than ID= was entered. This is theonly valid parameter.






ClassesNone.

AOF199I FOR REQ=DISP THE ONLY VALIDPARAMETERS ARE: ID=, FROM=,and TO=

ExplanationA parameter other than ID=, FROM=, or TO= wasentered. These are the only valid parameters.




ClassesNone.

AOF200I time: COMMAND init_cmd FAILED.RECEIVED RETURN CODE rr FROMfail_cmd

ExplanationA command issued by the initiating command endedwith a non-zero return code.

The variable time shows the time that this messagewas generated.The variable init_cmd shows the name of theinitiating command.The variable rr shows the condition code that wasreturned by the failing command.The variable fail_cmd shows the name of the failingcommand.



System programmer responseDetermine why the command failed and correct theproblem.

Classes0.

AOF201I time : CLIST clist_name: msg_input

ExplanationAn error occurred during processing of a command list.

The variable time shows the time this message wasgenerated.The variable clist_name shows the name of thecommand list that was being processed when theerror occurred.The variable msg_input describes the error.

System actionProcessing of the command list ends with anappropriate return code.


System programmer responsePerform problem determination on the command.

Classes0.

AOF203I command INVOKED BYUNAUTHORIZED USER (user_ID).REQUEST DENIED: request

ExplanationA command was called by a user who is not authorizedto do so. The request to process the command wasdenied.

The variable command shows the command thatwas called.



The variable user_ID shows the ID of the user whocalled the command.The variable request shows the request thataccompanied the call the command.

System actionThe command identified in the message is notprocessed.

Operator responseIf you feel that you should be authorized for thiscommand, request authorization from your systemprogrammer.

System programmer responseEvaluate the need the operator has for this function. Ifauthorization should be granted, notify the securityadministrator.

Classes0.

AOF204I time: EXPECTED PARAMETERSMISSING OR INVALID FORREQUEST command -parameter_name

ExplanationOne or more parameters that must be passed to thecommand identified in this message are missing or arenot valid.

The variable time shows the time this message wasgenerated.The variable command shows the name of thecommand that the variables must be passed to.The variable parameter_name shows the name ofthe parameter that was missing or not valid.

System actionNone.

Operator responseMake sure that the syntax is correct and enter therequest again. The netlog will show both the messageand the request as processed. Notify your systemprogrammer if the request fails again.

System programmer responseReview the user input to determine the validity of therequest and instruct the operator on the properprocedure. If the user input is correct, set debuggingon for the command to determine the source of theerror.

Classes0.

AOF205A time : command COMMAND FAILEDFOR clist_name: interval - WAITTIME EXPIRED

ExplanationProcessing of the command identified by this messagefailed because it took too much time. The timerinterval for command processing was exceeded.

The variable time shows the time this message wasgenerated.The variable command shows the name of thecommand that failed.The variable clist_name shows the name of thecommand list that was requested.The variable interval shows the timer interval thatwas exceeded.

System actionNone.

Operator responseCheck the netlog that was active when the messagewas received to see whether other command timershave expired. If no other timers have expired, reviewthe syntax for the command and issue the commandagain. If other command timers have been exceededor if processing of the command fails again, notify yoursystem programmer.

System programmer responseReview the user input to determine the validity of therequest and instruct the operator on the properprocedure. If the user input is correct, review thenetlog that was active at the time of the message tosee whether there is a reason for delays in commandlist processing. Note the value of the timer interval tosee whether the timer default should be changed.

Classes0, 40, 44.



AOF206I time : "command" COMMANDFAILED FOR clist_name: RECEIVEDreceived_ID "received_value"

ExplanationProcessing of the command identified in this messagefailed. The command list identified in this messagereceived a return code or a message indicating theproblem.

The variable time shows the time this message wasgenerated.The variable command shows the command thatwas processed.The variable clist_name shows the command listthat was requested.The variable received_ID shows either a messageID or the text string "RETURNCODE=".The variable received_value shows the messagetext or the return code.

System actionNone.


System programmer responseCheck the netlog for further information. Performproblem determination on the command list identifiedin this message.

Classes0.

AOF207E time: NO DEFAULTS SET FORresource_name, CLIST HALTED

ExplanationCommand list processing has been halted becauseautomation defaults have not been set for the resourceidentified in this message.

The variable time shows the time this message wasgenerated.The variable resource_name shows the name of theresource that automation defaults are not definedfor.

System actionThe process is ended.


System programmer responseCorrect the automation control file entries for theresource identified in this message.

Classes0.

AOF208I USER user_ID IS NOTAUTHORIZED TO INVOKECOMMAND command WITHPARAMETER parameter

ExplanationA command was called with a parameter by a userwho is not authorized to do so. The request to processthe command was denied.

The variable command shows the command thatwas called.The variable user_ID shows the ID of the user whocalled the command.The variable parameter shows the parameter whichis not authorized for the user.

System actionThe command identified in the message is notprocessed.

Operator response:If you feel that you should be authorized for thiscommand and this parameter, request authorizationfrom your system programmer.

System programmer response:Evaluate the need the operator has for this function. Ifauthorization should be granted, notify the securityadministrator.

Classes0.

AOF211E time: NO AUTOOPS ENTRIES HAVEBEEN DEFINED - AUTOMATIONCANNOT CONTINUE

ExplanationNo automated operator (AUTOOPS) entries have beendefined in the automation control file for theautomation environment.



The variable time shows the time this message wasgenerated.

System actionAutomation initialization is ended.


System programmer responseAdd the appropriate automated operator entries in theautomation control file using the customizationdialogs. See IBM Z System Automation DefiningAutomation Policy for more information.

In addition, since processing of the AUTOOPSENTRIES is performed on task AUTINIT2, verifyAUTINIT2 is active and available (and not scheduled toprocess other work that might prevent SA z/OS fromusing it).

Classes0.

AOF216I time: command YOUR COMMANDCANNOT BE PROCESSED - THEAUTOMATION ENVIRONMENT HASNOT BEEN INITIALIZED

ExplanationThe command that was entered cannot be processedbecause the automation environment has not beencompletely initialized.

The variable time shows the time when thismessage was generated.The variable command shows the command thatwas not processed, or the name of the REXX scriptprocessing the command.

System actionThe command is not processed.

Operator responseIf the automation environment has been completelyinitialized, message AOF540I is issued. Then reenterthe command.


ClassesNone.

AOF217I time: command IS NOTSUPPORTED

ExplanationThe command that was entered cannot be processedbecause this command is not supported in thisenvironment.

The variable time shows the time when thismessage was generated.The variable command shows the command thatwas not processed, or the name of the REXX/Command List processing the command.




ClassesNone.

AOF219I "OPID=" ONLY VALID WHEN"STATUS=" IS SPECIFIED

ExplanationYou can change the operator ID (OPID) only when thestatus is specified to be changed.


Operator responseEnter the command again and specify both theSTATUS= and OPID= parameters or do not specify theOPID= parameter.


ClassesNone.



AOF221I time: NO PRIMARY FOCAL POINTDOMAIN HAS BEEN DEFINED -DEFAULT OF domain_ID USED

ExplanationA primary focal point domain was not defined in theautomation control file member. The domain ID shownby the variable domain_ID will be assigned to theprimary focal point.


System actionThe current domain is assigned as the primary focalpoint.


System programmer responseIf the default value is not desired, use thecustomization dialogs to correct the automationcontrol file member. For more information, refer to IBMZ System Automation Defining Automation Policy.

ClassesNone.

AOF222I time: NO BACK UP FOCAL POINTDOMAIN HAS BEEN DEFINED -DEFAULT OF domain_ID USED

ExplanationA backup focal point domain was not defined in theautomation control file member. The domain ID shownby the variable domain_ID will be assigned to thebackup focal point.


System actionThe current domain is assigned as the backup focalpoint.


System programmer responseIf you do not want the default backup focal pointdomain to be used, use the customization dialogs tospecify a backup focal point domain in the automationcontrol file member. For more information, refer to IBMZ System Automation Defining Automation Policy.

ClassesNone.

AOF223I SETSTATE REJECTED -SUBSYSTEM name INVOLVED IN ASHUTDOWN

ExplanationA SETSTATE command has been requested for asubsystem but it or one of its dependants is in theprocess of shutting down.

The variable name shows the subsystem involved inthe shutdown.

System actionThe request is denied.

Operator responseWait for the shutdown to complete then reissue theSETSTATE request.


ClassesNone.

AOF224I time: JOB jobname HAS BEENDEFINED TO RUN ONLY ONCE -STATE NOT SET

ExplanationA transient job has been defined to run only once and arequest was made for its status to be changed.

The variable time shows the time this message wasgenerated.The variable jobname shows the job involved.

System actionRequest rejected for this job.





Classes40, 43.

AOF225I DUPLICATE KEYWORD keywordFOUND FOR SUBSYSTEMsubsystem. FIRST OCCURRENCEUSED

ExplanationWhile loading an automation control file, a duplicatekeyword was found for a subsystem, its value wasignored.

The variable keyword shows the duplicatedkeyword.The variable subsystem is the name of thesubsystem containing the keyword.

System actionThe first occurrence of the keyword value is used.


System programmer responseRemove the duplicate entry from the automationcontrol file.

Classes40, 43.

AOF227I UNABLE TO PROCESS command -reason

ExplanationSystem automation is not able to process therequested action.

The variable command shows the affectedcommand.The variable reason gives an explanation.

System actionProcessing stops.



ClassesNone.

AOF229I time: NO ENTRY FOR resname(entry type) HAS BEEN DEFINED -DEFAULT OF value USED

ExplanationThe system type was not defined in the automationcontrol file.

The variable time shows the time this message wasgenerated.The variable resname shows the name of thekeyword being defined.The variable entry shows the name of the entry inthe automation control file member.The variable type shows the name of the type in theautomation control file member.The variable value shows the value assigned to theentry within the specified resource.

System actionDefault value is assigned.


System programmer responseIf the default value is not desired, use thecustomization dialogs to correct the automationcontrol file member. For more information, refer to IBMZ System Automation Defining Automation Policy.

ClassesNone.

AOF233I SHUTDOWN REJECTED -SUBSYSTEM name INACTIVE

ExplanationThe subsystem you are trying to shutdown is inactive.

The variable name shows the name of thesubsystem.



System actionNone.



ClassesNone.

AOF240I REQUESTED TIMER timerid WASADDED

ExplanationThis message is a response to the TIMER ADDcommand. Processing of the command was completedsuccessfully.

The variable timerid shows the ID of the timer.

System actionThe timer is scheduled, with the requested name andfunction.



ClassesNone.

AOF241I time: EXPECTED PARAMETERSMISSING OR INVALID FORREQUEST clist_name -PARAMETER parm_list

ExplanationOne or more of the parameters that needed to bepassed to a command list during shutdown processingwere missing or were not valid.

The variable time shows the time this message wasgenerated.The variable clist_name identifies the requestedcommand list.

The variable parm_list lists all of the parametersthat were missing or were not valid.

System actionThe shutdown process ends.

Operator responseMake sure valid parameters are entered.

System programmer responseMake sure valid parameters are entered. Check theparameters in the automation control file.

Classes0.

AOF244I time: SHUTDOWN PROCESSINGON restype resname (JOBjob_name) SUSPENDED FORinterval MINUTES

ExplanationShutdown processing has been suspended for the jobidentified by the variable job_name for the number ofminutes shown by the variable interval. This allowsusers of the job to end their activities before the job isshut down.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.The variable resname shows the name of theresource.

System actionThe Shutdown process begins again after the numberof minutes specified in this message.



Classes40, 43, 44, 46.

AOF245I time: restype resname (JOBjob_name) STATUS IS status -



SHUTDOWN WILL BYPASSISSUING msgtype COMMANDS

ExplanationThe shutdown processing has determined that the jobidentified by the variable job_name is already shuttingdown. The shutdown processing will bypass issuingfurther commands.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.The variable resname shows the name of theresource.The variable status shows the status of theresource.The variable msgtype shows the command type tobe issued (SHUTINIT,SHUTDOWN).

System actionThe status of the job is either stopping or abending.The job is checked to see whether it is down, so thatshutdown processing may complete. If the job doesnot end, manual intervention will be required.

Operator responseNone. This message is sent to the netlog only.

System programmer responseCheck why the job was in stopping or abending status.

Classes40, 43.

AOF246A time: SHUTDOWN PROCESSINGFAILED FOR SUBSYSTEMsubsystem_name - SHUTDOWNMAY NOT COMPLETESUCCESSFULLY

ExplanationAn error occurred during shutdown processing. Amessage describing the error was issued previously.

The variable time shows the time when thismessage was generated.The variable subsystem_name shows thesubsystem that the message was for.

System actionNone.

Operator responseSee the message describing the error that was issuedpreviously to determine why shutdown processingfailed.


Classes40, 43.

AOF247E time: SHUTDOWN PROCESSINGFAILURE FOR restype resname(JOB job_name) - ALL COMMANDS/REPLIES MAY NOT HAVE BEENISSUED - command_typeerror_type FOR PASS pass_numberHAD ERROR

ExplanationShutdown processing has failed for the subsystemidentified by the resource name (resname) and the jobname (job_name).

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.command_type shows the command type to beissued (SHUTINIT,SHUTDOWN).The variable error_type shows whether a commandor reply had errors.The variable pass_number shows the pass numberin error.

System actionThe shutdown processing ends.

Operator responseCheck for the type of errors identified by error_typeand contact your system programmer.

System programmer responseReview the automation control file, looking for the jobidentified by this message. Correct the errors observedby the operator. Look for message AOF206I in thenetlog that was active at the time this message wasissued. Message AOF206I contains information youcan use to determine why processing of the commandor reply failed. The syslog contains commands andreplies that can be checked against what should havebeen issued.



Classes40, 43.

AOF249E time: resource CGLOBAL cglobalWAS NOT PROPERLY INITIALIZED

ExplanationThe cglobal variable identified in this message was notproperly initialized for the resource identified in thismessage.


System actionCurrent® processing might not be completedsuccessfully.

Operator responseReview the netlog that was active at the time of thismessage for related messages that help define theproblem. Contact your system programmer.

System programmer responseReview the initialization procedures and the control fileto determine why the cglobal variable is not beinginitialized properly. You might need to set debuggingon to identify the problem. Correct the problem.

ClassesNone.

AOF251I SHUTDOWN type REJECTED -subsystem_type ALREADY INPROGRESS

ExplanationA shutdown has been requested but a shutdown iscurrently executing involving this subsystem or one ofits children.

The variable type shows the shutdown type.The variable subsystem_type shows the name ofthe subsystem.

System actionNone.



ClassesNone.

AOF252I time: TIMER ID = timer_ID NOTSCHEDULED - reason

ExplanationThe timer identified by the variable timer_ID could notbe scheduled.

The variable time shows the time this message wasgenerated.The variable reason gives an explanation of failure,such as TASK NOT ACTIVE.

System actionThe timer identified in the message is not scheduled.

Operator responseFind the reason the timer was not scheduled, correctthe problem, and issue the time request again.


Classes40, 43.

AOF253I time: REQUESTED TIMER =timer_ID NOT FOUND

ExplanationThis 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.



Operator responseVerify that the timer does not exist by refreshing thetimer display.




Classes0, 40, 43.

AOF255I time: EXIT exit_name IN entry typeIS INVALID, RC=return_code

ExplanationAn exit name that is not valid (shown by the variableexit_name) was found when calling user exits.

The variable time shows the time this message wasgenerated.The variable entry identifies the entry field in theautomation control file where the exit was defined.The variable type identifies the type field in theautomation control file where the exit was defined.The variable return_code shows a return code thatidentifies why the exit was not valid: If the returncode is 04, the exit name was not 1 to 8 characterslong; if the return code is 08, the exit name was nota valid module or command list.

System actionThe exit code for the routine that is not valid isbypassed.


System programmer responseCorrectly define the exit routine or remove it from theexit list.

Classes0, 40, 44.

AOF256I time: EXIT exit_name BEINGINVOKED.

ExplanationA user exit (shown by the variable exit_name) hasbeen invoked.


System actionNone.



ClassesNone.

AOF257I time: EXIT exit_name ENDEDWITH RC=return_code.

ExplanationA user exit (shown by the variable exit_name) hasended.

The variable time shows the time this message wasgenerated.The variable return_code shows the return codegiven by the user exit.

System action:None.



ClassesNone.

AOF262E MESSAGE ID message_IDINVALID, MUST BE "NNN","ABCNNN" OR "ABCDNNN"

ExplanationThe specified message ID is invalid. Three message IDforms are valid:

• Three decimal digits (NNN)• A three-character prefix followed by three decimal

digits (the prefix may contain numeric values)• A four-character prefix followed by three decimal

digits (the prefix may contain numeric values).

The variable message_ID shows the message IDspecified as the second parameter of the AOCMSGcommand. This message ID is not valid.

System actionNone.




System programmer responseCorrect the message ID specified as the secondparameter of the AOCMSG command.

ClassesNone.

AOF263I MESSAGE ID NUMERICmessage_ID IS NOT NUMERIC

ExplanationThe specified message ID is not valid because it doesnot end with three numeric digits.

The variable message_ID shows the message IDspecified as the second parameter of the AOCMSGcommand. This message ID is not valid.

System actionNone.


System programmer responseCorrect the message ID specified as the secondparameter of the AOCMSG command.

ClassesNone.

AOF264I TOO FEW PARAMETERS ONAOCMSG COMMAND, 2 ISMINIMUM

ExplanationThe AOCMSG command was issued without one ormore required parameters. At least two parametersmust be specified for the command to be processedsuccessfully.

System actionNone.


System programmer responseMake sure that the coding of the AOCMSG commandspecifies a message ID value as the second parameter.If you do not want to specify a value for the firstparameter, code a comma in its position as a placeholder (AOCMSG ,001).

ClassesNone.

AOF271I clist_name: DATATYPE "data_type"FOR entry NOT KNOWN, IGNORED

ExplanationThe data_type keyword specified in entry entry is notrecognized. It is being ignored.

The variable clist_name shows the name of thecommand list that generated this message.

System actionNone.



Classes40.

AOF282I clist_name: SDF DATA LOADED

ExplanationThe status display facility (SDF) portion of systemautomation initialization is complete.


System actionNone.





ClassesNone.

AOF283I clist_name: number SUBSYSTEMSCURRENT STATUS PRIMED

ExplanationThis message reports the number of subsystemsprocessed.


System actionNone.



ClassesNone.

AOF284I clist_name: number NOTIFYOPERATORS READIED

ExplanationThis message reports the number of notificationoperators that have been processed and initialized.


System actionNone.



ClassesNone.

AOF286I clist_name: SUBSYSTEM STATUSVERIFIED

ExplanationSubsystem status information has been verified withthe active cglobal variables.


System actionNone.



ClassesNone.

AOF287I clist_name: COMPLETE

ExplanationProcessing of the command list has been completednormally.


System actionNone.



ClassesNone.

AOF288I clist_name: subsystem_nameJOBNAME IS DUPLICATE,SUBSYSTEM IGNORED

ExplanationSubsystem subsystem_name has a job name that is aduplicate. This subsystem is ignored.




System actionNone.


System programmer responseMake sure that the subsystem subsystem_name doesnot have a duplicate job name.

Classes40.

AOF290I clist_name: SUBSYSTEM -subsystem_name SCHEDULINGSUBSYSTEMscheduling_subsystem_ nameINVALID

ExplanationThe scheduling_subsystem_name is not defined as avalid Job Entry Subsystem, and therefore cannot beused to schedule subsystem subsystem_name

The variable clist_name shows the name of thecommand that generated this message.

System actionThe primary JES subsystem will be used.


System programmer responseCorrect the subsystem definition to identify asubsystem of type JES2 or JES3.

Classes40.

AOF291I clist_name: NO JES2 OR JES3SUBSYSTEMS DEFINED; SUBSYS =subsystem_name SET

Explanation

No subsystems were defined as being type JES2 orJES3, and therefore the validity of the subsystemidentified as the primary Job Entry Subsystem (JES)cannot be validated.


System actionThe identified subsystem will be used withoutvalidation.


System programmer responseCorrect the subsystem definition to properly identifythe one or more Job Entry Subsystems, and verify thatthe correct subsystem is identified as the primary JES.

Classes40.

AOF293I time: THERE IS NO OUTSTANDINGREPLY STORED BY SA z/OS FORSUBSYSTEM sname.

ExplanationSystem automation cannot determine from itsCGLOBALS the reply ID for this subsystem.

The variable time shows the time the error messagewas generated.The variable sname shows the subsystem to bereplied to.



System programmer responseCheck why the reply ID is not stored by SA z/OS.

Classes40, 43, 44.

AOF294I SPOOL type RECOVERYCOMMANDS EXHAUSTED, SPOOLTGS IS NOT RELIEVED,OPERATION INTERVENTION ISREQUIRED



ExplanationWhile attempting to recover from a spool shortage,SA z/OS ran out of defined recovery commands. Userhas chosen not to reissue the spool commands.

The variable type shows the type of spool problembeing recovered.

System actionThe spool recovery has stopped.

Operator responseYou need to have a look at your spool usage. SA z/OShas issued all the defined spool recovery passes andthe spool TGS is not relieved. Manual intervention byoperators is required.

System programmer responseReview your spool recovery commands.

Classes40, 43, 44.

AOF296I TARGET AND RESOURCE_SYSTEMSPECIFICATION ARE DIFFERENT(TARGET IGNORED)

ExplanationThe target and resource system specification in theINGREQ command are different. Therefore the targetspecification has been removed.

System actionNone.



ClassesNone.

AOF300I A REPLY MUST BE SPECIFIED

ExplanationYou must specify a reply.

System actionNone.

Operator responseSpecify a reply.


Classes. None.

AOF302I time: REQUEST clist_name actionBY oper_id IS COMPLETED FORresname

ExplanationThe request to set a function ON or OFF for thespecified resource was successful.

The variable time shows the time this message wasgenerated.The variable clist_name shows the name of therequested command list or command.The variable action shows the function of therequested command list or command.The variable oper_ID shows the name of theoperator that issued the request.The variable resname shows the name of theresource affected.

System actionThe requested function is performed on the specifiedresource.



ClassesNone.

AOF306I time: NO auto_type AUTOMATIONREQUIRED FOR restype resname

ExplanationAutomation was requested for the resource and it wasfound that no action was required.



The variable auto_type shows the type ofautomation requested.The variable restype shows the type of resource.The variable resname shows the name of theresource.The variable time shows the time this message wasgenerated.

System actionNone.



ClassesNone.

AOF307I time: REQUEST clist_name actionBY oper_id WAS UNSUCCESSFULFOR resname, STATE IS ALREADYSET

ExplanationThe request to set a function ON or OFF for thespecified resource was not successful.

The variable time shows the time this message wasgenerated.The variable clist_name shows the name of therequested command list or command.The variable action shows the function of therequested command list or command.The variable resname shows the name of theresource.The variable oper_id shows the name of theoperator that issued the request.

System actionNone.



ClassesNone.

AOF309I time: OPERATOR operator_IDEXECUTED TIMER timer_ID FORCATCHUP - COMMAND: cmd

ExplanationThe command cmd was executed for timer timer_IDbecause the current time was past the execution timeand CATCHUP=YES was specified.

The variable time shows the time this message wasgenerated.The variable operator_ID shows the name of theoperator that executed the command.The variable timer_ID shows the name of the timerthat was executed.The variable cmd shows the command that wasexecuted.




Classes40, 43.

AOF310I time : resname autotype IS SET ON- autotype action NOT FOUND FORmsg_type WITH SELECTIONselection

ExplanationThe specified automation flag is on, but the commandor reply to be issued could not be found in theautomation control file.

The variable time shows the time when thismessage was generated.The variable resname shows the name of theresource.The variable autotype shows the automation flagthat has been checked.The variable action shows the type of action thatshould have been taken. Possible values areCOMMAND and REPLY.



The variable msg_type shows the message ID thatthe specified action has been searched under in theautomation control file.The variable selection shows the pass or selectionstring that the entry that was searched for couldnot be found on.



System programmer responseUse the customization dialog to check the entriesspecified by the resource name, the message ID andthe selection string in the automation control file. Forfurther information, refer to IBM Z System AutomationDefining Automation Policy.

Classes40, 43.

AOF311I time : restype resname (JOBjob_name) DID NOT HAVE ANOUTSTANDING REPLY ONmsg_type PASS pass_number

ExplanationThe automation policy for shutting down a resourceindicates that a reply should be issued for thecommand type identified in this message. However,there was no outstanding message that a reply couldbe issued for on the pass shown by pass_number.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.The variable resname shows the name of theresource.The variable job_name shows the name of the job.The variable msg_type shows the command type tobe issued (SHUTINIT,SHUTDOWN).



System programmer responseMake sure that the automation control file policy forshutting down the resource identified in this messageis accurate.

Classes40, 43.

AOF313I time : START FOR restype resname(JOB job_name ) WAS NOTATTEMPTED - reason

ExplanationSA z/OS attempted to start a resource but could not forthe reason given.

The variable time shows the time this message wasgenerated.The variable restype shows the type of theresource.The variable resname shows the name of theresource.The variable job_name shows the name of the job.The variable reason shows the reason that theresource could not be started.

System actionIf the resource was not started because a flag wasturned off it will be left in its current state and the flagrechecked each time the monitor cycle runs. Noattempt will be made to start its parents until the flagis turned on. If the resource was not started because it(or one of its parents) was involved in a shutdown itsstatus may be changed to AUTODOWN. It will not startuntil the shutdown has finished.

Operator responseIf the resource failed to start because a flag was set offand you want it to start you should use INGAUTO tochange the flag. If the resource did not start becauseof a shutdown and you want it to start you must eitherwait for the shutdown to finish or clear the shutdown.


Classes40, 43.

AOF314I time : CATCHUP TIMER ID timer_IDNOT EXECUTED. TASK operator_IDNOT LOGGED ON.



ExplanationA timer was unable to be restored because thescheduled time had already occurred. Catch-upprocessing unsuccessfully attempted to issue thecommand. The command failed because the operator(operator_ID) was not logged on to receive and run thecommand.

The variable time shows the time this message wasgenerated.The variable timer_ID shows the name of the timerthat was not able to be restored.The variable operator_ID shows the name of theoperator where the timer command should haverun.


Operator responseIssue the command manually under the appropriateoperator ID.


Classes0, 40, 43.

AOF315I time : TIMER timer_ID PURGED byoperator operator_ID

ExplanationA timer was deleted from the NetView timer list by theoperator.

The variable time shows the time this message wasgenerated.The variable timer_ID shows the name of the timerthat was deleted (purged).The variable operator_ID shows the name of theoperator who deleted the timer.




Classes40, 43.

AOF316I time : SHUTDOWN FOR restyperesname (JOB job_name) DELAYEDinterval MINUTES - RECEIVEDEXIT CODE code FROM exit_name

ExplanationShutdown processing has been suspended for a jobbecause a return code received from an exit matched ashutdown return code that temporarily stopsprocessing.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.The variable resname shows the name of theresource.The variable job_name shows the name of the jobthat processing has been suspended for.The variable interval shows the number of minutesprocessing will be suspended.The variable code shows the return code receivedfrom the exit.The variable exit_name shows the exit that thereturn code was received from.

System actionShutdown will be retried after the interval. Retries willcontinue until subsystem is shutdown.

Operator responseIf the delay is excessive, investigate the reason andcontact your system programmer.

System programmer responseIf delay is excessive, investigate why the exit istemporarily suspending shutdown.

Classes40, 43.

AOF319I time : OPERATOR operator1SCHEDULED TIMER timer_IDUNDER OPERATOR operator2 -COMMAND: text



ExplanationAn operator created and scheduled a new timer.

The variable time shows the time this message wasgenerated.The variable operator1 shows the name of theoperator who created the timer.The variable timer_ID shows the name of the timerthat was scheduled.The variable operator2 shows the operatoridentification where the timer was scheduled.The variable text shows the text of the timercommand that was scheduled.




Classes40, 43.

AOF320I time : ASSIST LOG FOR:resource_type/resource_name -KEY: entry/type/keyword -COMMAND: text

ExplanationThis message is generated when assist mode is activefor a resource and a command is issued for thatresource. This message identifies the resourceassociated with the command and shows the text ofthe command. This message is logged in the netlog.

The variable time shows the time this message wasgenerated.The variable resource_type shows the type ofresource associated with the command.The variable resource_name shows the name of theresource associated with the command.The variable entry shows the entry field from theautomation control file entry that defines thecommand. If it is internally generated, this valuewill be FUNC.The variable type shows the type field from theautomation control file entry that defines thecommand. If it is internally generated, this valuewill be ISSUED.

The variable keyword shows the commandselection field from the automation control fileentry.The variable text shows the text of the commandthat was issued, after variable substitution.

System actionThis message is logged in the netlog.


System programmer responseReview the netlog to verify that the action reported bythis message was intended and that variablesubstitution worked properly.

ClassesNone.

AOF323I time : ASSIST LOG FOR:resource_type/resource_name -KEY: entry/type/keyword - REPLY:text

ExplanationThis message is generated when assist mode is activefor a resource and a reply is issued for that resource.This message identifies the resource associated withthe reply and shows the text of the reply. This messageis logged in the netlog.

The variable time shows the time this message wasgenerated.The variable resource_type shows the type ofresource associated with the reply.The variable resource_name shows the name of theresource associated with the reply.The variable entry shows the entry field from theautomation 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 theautomation control file entry that defines the reply.If it is internally generated, this value will beISSUED.The variable keyword shows the reply selectionfield from the automation control file entry.The variable text shows the text of the reply thatwas issued, after variable substitution.

System actionThis message is logged in the netlog.




System programmer responseReview the netlog to verify that the action reported bythis message was intended and that variablesubstitution worked properly.

ClassesNone.

AOF325I CHRON COMMAND IN ERROR:chron_command

ExplanationThe CHRON command processor rejected thecommand.

The variable chron_command shows the name ofthe command that could not be executed.


Operator responseReenter the correct command, if applicable.


ModuleAOFRAAT1

ClassesNone.

AOF326I STOP TIME MUST BE LATER THANSTART TIME

ExplanationThe stop time of the EVERY timer is earlier than thestart time.


Operator responseReenter the correct command, if applicable.


ModuleINGRYTIM

ClassesNone.

AOF331I SUBSYSTEM name IS NOTDEFINED ON THE LOCAL SYSTEM

ExplanationThe specified subsystem is defined more than oncewithin the systems in the sysplex. Because thecommand is operating in line mode and the subsystemis not defined locally, system automation cannotdetermine which of the subsystems the commandshould be routed to.

An operator dialog issues this message.

The variable name shows the specified subsystemname.

System actionNone.

Operator responseReenter the correct command. Specify the TARGETparameter to identify the system that the commandshould be routed to.


ClassesNone.

AOF332I SUBSYSTEM name COULD NOT BELOCATED ON target

ExplanationThe specified subsystem is neither defined in the localsystem nor in any other system of the sysplex.

If the target is outside the local sysplex, there could bea problem with the RMTCMD link. If this is the case,additional NetView messages have been issued.

The variable name shows the specified subsystemname.



The variable target shows the target, or the list oftargets where the subsystem is not defined.

System actionNone.

Operator responseReenter the correct command.


ClassesNone.

AOF333I function CALL FAILED WITH RC=return_code IN CLIST name

ExplanationThe specified clist detected an error while attemptingto schedule a remote procedure call (RPC) to run aclist or a command on a remote system in the sysplex.The return code indicates which type of error occurred:

12An invalid handle was specified. The handle iscurrently in use, or the handle was already deleted,or it is being deleted.

16Processing of the remote procedure call (RPC)failed.

24The target is not active, or it is not contained in themember table.

32REXX variable pool problem.

36Other severe error.

40The Sysplex Communication Manager Environmentis not available, for example, because the SysplexCommunication Manager task was not started.

44An ABEND occurred.


The variable function shows the service that causesthe problem.The variable return_code shows the return codefrom the failing function.

The variable name shows the name of the clist thatinvoked the failing function.

System actionNone.

Operator responseIssue the command again. If the problem persists,contact your IBM Support Center for furtherassistance.

System programmer responseExamine the return code of the failing service for thecause of the error. For a list of possible error codevalues and their meaning, refer to the explanation ofmessage AOF350E. If you cannot resolve the problem,contact your IBM Support Center.

Classes0.

AOF334I UNABLE TO RECEIVE THE OUTPUTFROM THE REQUESTED SYSTEM(S)system

ExplanationOne or more remote procedure calls (RPCs) werescheduled to get data from the remote system(s). It ispossible that the commands were successfullyprocessed on the remote system(s). However, the“OK” result was not returned in time.

The variable system shows the list of systems thatdid not provide the output in time.

System actionNone.

Operator responseCheck whether processing has completedsuccessfully, then reenter the command. If theproblem persists, contact your IBM Support Center.

System programmer responseExamine the netlog for additional information. Ifnecessary, increase the maximum wait time,"aofrpcwait". If communication is via the NetViewRMTCMD, increase the default CORRCMD wait timevalue in the DSICCDEF or use "aofrmtcmdwait".



ClassesNone.

AOF335I UNRECOGNIZED ACTION CODE

ExplanationAn action code that is not valid was entered.

System actionNone.

Operator responseEnter a correct action code. For a list of valid actioncodes (or selection codes), call help from the panelthat this message appears on.


ClassesNone.

AOF336I SUBSYSTEM name NOT DEFINEDON SYSTEMS sysname_list

ExplanationThe specified subsystem is not defined on thesystem(s) identified with the TARGET parameter or theappropriate panel field.


The variable name shows the specified subsystemname.The variable sysname_list shows the systems thatdo not have the subsystem defined.

System actionNone.



ClassesNone.

AOF337I ONLY ONE TARGET IS ALLOWED

ExplanationMore than one system name or domain ID wasspecified for the TARGET parameter. However, onlyone name is allowed.

System actionNone.



ClassesNone.

AOF338I CONFLICTING TARGETSPECIFICATION

ExplanationALL and at least one other system name or domain IDhave been specified for the TARGET parameter.


System actionNone.



ClassesNone.

AOF339I name DOES NOT CORRESPOND TOAN ACTIVE TARGET WITHIN THEenvironment

ExplanationThe specified name is neither the system name nor thenetwork domain ID of an active target within thespecified environment.



The following reasons can cause the dialog to issuethis message:

• The specified target name is not valid.• If the specified target is outside the local sysplex,

the GATEWAY connection to that target could beinactive.

• If the target is outside the local sysplex, there couldbe a problem with the RMTCMD link. If this is thecase, additional NetView messages have beenissued.

The variable name shows the unrecognized name.

The variable environment shows the environment thedialog searched for. It is either sysplex or enterprise.

System actionNone.



ClassesNone.

AOF340I NO RESPONSE RECEIVED FROMSYSTEM system_name

ExplanationA remote procedure call (RPC) was sent to thespecified system, but the remote system did not replywith an answer within the expected time period.

The variable system_name identifies the system thatdid not respond.

System actionNone.

Operator responseIssue the command again. If the problem persists,contact your local support personnel for furtherassistance.

System programmer responseExamine the netlog for additional information. Ifnecessary, increase the maximum waittime“aofrpcwait.”

ClassesNone.

AOF341I time : clist_name RETURN CODE:xx SYSTEM: name ERROR: error

ExplanationThis is an internal message that is used to transmitcommand completion information from the systemthat processed the command back to the system thatrequested the command execution. The message willnot appear on any screen.

System actionNone.



ClassesNone.

AOF343I NOTHING TO DISPLAY

ExplanationNo data is available for display.

System actionNone.



ClassesNone.

AOF344I CLIST clist_name DOES NOT EXIST

ExplanationThe specified clist could not be found.

The variable clist_name shows the name of the clist.



System actionNone.

Operator responseIssue the command again.


ClassesNone.

AOF345I RUNMODE CHANGED FOR system.PLEASE REVISE RUNMODEQUALIFICATIONS

ExplanationThe runmode has been changed and there are stillresources that have been qualified earlier by anINGRUN command.

The variable system shows the system for whichrunmode was changed.

System actionNone.

Operator responseRevise the displayed list and decide whether therunmode qualification for those resources can bedeleted.


ClassesNone.

AOF346I RUNMODE *ALL ALREADY SET

ExplanationINGRUN was called to set the runmode to *ALL while itwas already *ALL.

System actionNone.

Operator responseNone, because *ALL is already set. You can specifyanother runmode.


ClassesNone.

AOF347I NO RUNMODE DEFINED FORsystem

ExplanationINGRUN was called to set a runmode but there arenone defined on the given system.

The variable system shows the name of the affectedsystem.

System actionNone.


System programmer responseDefine runmodes for the given system in theautomation control file.

ClassesNone.

AOF350E COMMUNICATION ERROR:SYSTEM=system nameERRTYPE=error typeERRCODE=error codeSERVICE=service RET=return codeRSN=reason code DIAG=moduleremainder

ExplanationAn error was detected during communication toanother system. This message always contains thename of the system where the error occurred, the typeof error and the error code. The other keywords areoptional.

The variable system name shows the name of the z/OSsystem where the error occurred.



The variable error type shows a decimal number thatspecifies the type of the error. It can have the followingvalues:

4Input checking failed. User specified input, forexample, global variables, that were not set upcorrectly. The variable error code provides furtherinformation.

8The system automation communication managerData Service Task (DST) could not be initialized.

12Termination error of the system automationcommunication manager Data Service Task.

16An internal communication pipe service providedby a system automation system failed.

20A remote procedure call (RPC) Handler failed.

24A system service failed.

28A REXX API failed.

32A storage problem occurred.

36An internal error occurred.

40The system automation communication servicescould not be initialized.

The variable error code shows a unique number thatspecifies where in the code the error occurred.

The variable service shows the name of the servicethat caused the error.

The variable return code shows the return code of thefailing service (hex number). This variable will only bereturned in combination with the service variable.

The variable reason code shows the reason code of thefailing service (hex number). This variable will only bereturned in combination with the service variable.

The module remainder variable shows diagnosticinformation. It specifies the name of the failingmodule. The remaining items vary depending on theerror code. The module remainder variable data isintended for your IBM Support Center.

The following table shows the possible combinationsof error types and error codes and their meaning. Thisinformation also applies to message HSAM1050E.

Table 3. Combinations of Error Types and Error Codes

ErrorType

ErrorCode

Meaning

4 72136140284

ExplanationInput checking error. Invalid format ofa handle.

ActionContact your IBM Support Center(ISC).

4 260

ExplanationInput checking error. The sysplexgroup name is not known. The reasonis that the retrieval of the commonglobal variable AOFXCFGROUP failedor it contains a null string.

ActionSet AOFXCFGROUP up properly.

4 268

ExplanationInput checking error. Target sysplexmember, representing the targetNetView or the automation manager,is not valid.

ActionSpecify a valid target sysplex memberor start the SA z/OS sysplexcommunication manager in NetViewfor the specified system or start theautomation manager.

4 541550

ExplanationInput checking error. Target sysplexmember, representing the primaryautomation manager, is not active.

ActionCheck whether the member name inthe DIAGNOSTIC field is a valid XCFmember name. Specify a valid targetsysplex member or start theautomation manager.

8 131620

ExplanationDST initialization error. There is notenough storage available.

ActionIncrease the region size.



Table 3. Combinations of Error Types and Error Codes(continued)

ErrorType

ErrorCode

Meaning

8 31170

ExplanationDST initialization error. An SA z/OScommunication service modulecannot be loaded.

ActionCheck return code of the load service.

8 208

ExplanationDST initialization error. An SA z/OScommunication environment cannotbe created.

ActionCheck the z/OS return code.

8 244248573574

ExplanationDST initialization error. An SA z/OScommunication provided NetViewcommand processor cannot be addedto the NetView environment.

ActionCheck the NetView return code.

8 300348

ExplanationDST initialization error. An attemptwas made to start SA z/OScommunication on an OS/390 systemlower than Release 3.

ActionInstall an OS/390 or z/OS Releasesupporting XCF Ordered MessageDelivery.

8 571

ExplanationDST initialization error. The DSTreceiver task (DSR) cannot be stared.

ActionCheck the return and reason codes. Ifnecessary contact your IBM SupportCenter.

8 489

ExplanationAutomation manager initializationerror. The MTIB could not beinitialized.


ErrorType

ErrorCode

Meaning

ActionIncrease the region size and ifnecessary contact your IBM SupportCenter.

8 517

ExplanationAutomation manager initializationerror. A subtask could not beinitialized.

ActionContact your IBM Support Center.

8 520

ExplanationAutomation manager initializationerror. The subtask shell logon to theCommunication Manager failed.





ErrorType

ErrorCode

Meaning

8 532

ExplanationAutomation manager initializationerror. A control block cannot becreated that is anchored to the MTIB.One of the following return codes inhexadecimal 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 toerrors in the automation managerparmlib member.

X'198' (408)PKVT cannot be initialized for theautomation manager due tomissing parmlib member. See alsomessage HSAM5206E for moreinformation.

X'1F8' (504)Pre-initialization of the controlblock failed

X'1FC'(508)Post-initialization of the controlblock 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 isa setup problem of the componenttrace 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:


ErrorType

ErrorCode

Meaning

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) thenthere might be too manyautomation manager instances onthe MVS™ image. The limit is 9.

2707No longer MODE=SUP

ActionCheck the return code and othermessages that may be issued with thismessage. If necessary contact yourIBM Support Center.

8 533

ExplanationAutomation manager initializationerror. Not all modules could beloaded.

ActionCheck the STEPLIB concatination. Ifnecessary contact your IBM SupportCenter.

8 536

ExplanationAutomation manager initializationerror. Cannot open the task lib.

ActionCheck the HSAMODLE DD statementin the start procedure of theautomation manager and if necessarycontact your IBM Support Center.

8 561

ExplanationAutomation manager initializationerror. The MVS console interface couldnot be initialized.





ErrorType

ErrorCode

Meaning

8 564

ExplanationDST initialization error. The erroroccurred when parsing the DST initmember INGXINIT.

ActionCheck the DSIPARM memberINGXINIT for syntax errors.

8 566

ExplanationDST initialization error. A globalNetView variable could not becreated.


8 700

ExplanationInvalid Suffix for XCF group INGPX$xx.

ActionModify INGXINIT and set parameterPLEXID correctly.

8 701

ExplanationRPC with type=SYSPLEX was calledalthough PLEXID was not specified.


8 702

ExplanationMember table extension cannot beupdated (internal error).


8 703

ExplanationCommand scheduling failed duringinitialization of INGPXDST.

ActionCheck if the target task is available orcheck the netlog for any relatedNetView error message.

12 11 ExplanationDST Termination. The SA z/OScommunication manager is waiting toterminate the DST because there isanother task that is still using its


ErrorType

ErrorCode

Meaning

resources. The waiting time dependson the value of the global variableXDOMTIME. If XDOMTIME contains anull string or an invalid value then DSTtermination will continue after 60seconds. Otherwise, the value ofXDOMTIME is multiplied by 5seconds. For example, ifXDOMTIME=120 then the DST willwait 600 seconds.

ActionStop the REXX program that is usingthe SA z/OS communication services.

12 12 ExplanationDST Termination. The SA z/OScommunication manager terminationcontinued but the SA z/OS sysplexcommunication block was not freedsince another task still holds a lock.

ActionStop the REXX program that is usingthe old SA z/OS communicationenvironment.

12 499

ExplanationDST Termination. The Automationmanager termination is unable tounregister task.

ActionCheck the return and reason codes. Ifnecessary contact your IBM SupportCenter.

12 535

ExplanationAutomation manager terminationerror. The subtask shell terminationfailed.





ErrorType

ErrorCode

Meaning

12 562

ExplanationAutomation manager termination. Thecleanup of a control block anchored tothe MTIB failed. The return code thatwill be supplied with this message isone of those explained in the row ofERROR TYPE 4 and ERROR CODE 532.

ActionCheck the return code. If necessarycontact your IBM Support Center.

12 602572

ExplanationDSR Termination. The DST ReceiverTask could not be terminated.


16 24 ExplanationRPC Pipe error. Pipe cannot becreated. There is probably not enoughstorage.


16 44100503527

ExplanationRPC Pipe error. Write failed, probablydue to lack of storage.

ActionFor return codes 12, 16 or 56 increasethe region size. Return code 84indicates that the write was canceledbecause of a DST termination request,and no action is required. In case ofany other return code, contact yourIBM Support Center.

16 4864132146328504514

ExplanationRPC Pipe error. Close failed.



ErrorType

ErrorCode

Meaning

529555

16 56128144510525554592

ExplanationRPC Pipe error. An open failedbecause the RPC handle to be openedcannot be found, is currently in use oris disabled. Error code 592 is a failingopen during retry.


16 60513

ExplanationRPC Pipe error. Read request failed,probably due to lack of storage.

ActionFor return codes 12, 16 or 56 increasethe region size. Return code 84indicates that the read was canceledbecause of a DST termination request,and no action is required. In case ofany other return code contact yourIBM Support Center.

16 150154512526

ExplanationOne possible reason is that while aSAM is taking over the PAM role,communication to the PAM is notpossible. Another reason is RPC Pipeerror. Pipe is broken.

ActionFor the first reason, wait until takeoveris over and try again.

For the second reason, look foradditional AOF350E messages thatdescribe the reason for the brokenpipe, for example messages with errortype 20.




ErrorType

ErrorCode

Meaning

16 320505

ExplanationRPC Pipe error. Create request for aremote pipe failed, probably due tolack of storage for the pipe object.

ActionIncrease the NetView region size.

16 372

ExplanationRPC Pipe error. Pipe is broken. TheSA z/OS communication manager on apipe's target system was terminated.The pipe object is disabled,communication is no longer possible.

ActionRestart the SA z/OS communicationmanager (INGPXDST), or recycleNetView.

16 392

ExplanationRPC Pipe error. The DST or theautomation manager cannot send thepipe data to the target. This is eitherdue to an XCF problem, or an internalproblem. The return code (RET) is thereturn code of the RPC pipe service.The reason code (RSN) describes thereturn code of the package service.The return and reason codes are fordiagnostic purposes only.

ActionCheck whether additional messageswere issued, for example,HSAM1050E with error type 24 andanalyze whether an XCF erroroccurred. If necessary contact yourIBM Support Center.

16 521

ExplanationRPC Pipe error. A subtask cannotreceive the data buffer.

ActionContact your IBM Support Center

16 57559759

ExplanationRPC Pipe error. The DST or theautomation manager cannot send thepipe data to the target system. The


ErrorType

ErrorCode

Meaning

8599623638

send request was retried but the retrylimit exceeded.

ActionThe communication path is probablybroken. Make sure thatcommunication can work properly. Incase of XCF customize the XCFsubsystem. For example, increase thenumber of XCF buffers or install a newmessage buffer class dedicated to theDST, or do both. Check whether thereare additional AOF350 or HSAM1050messages that might explain thereason why communication does notwork. If necessary contact your IBMSupport Center.

20 400

ExplanationRPC Command Handler error. The RPCcommand handler INGRXCMD failed.The reason code contains the REXXline number where the error conditionwas trapped.


20 404408412

ExplanationRPC Command Handler error. The RPCcommand handler INGRXCMD failed.

ActionLook for the corresponding additionalerror message AOF350E with errortype 16 for more information. Ifnecessary, contact your IBM SupportCenter.

20 416

ExplanationRPC Command Handler error. The RPCcommand handler INGRXCMD cannotexecute the command because theNetView PIPE failed.

ActionCheck the return code of the NetViewPIPE command. Contact your IBMSupport Center.




ErrorType

ErrorCode

Meaning

24 40174178190232233234236476480482483

ExplanationSystem Service error. The specifiedXCF system service failed.

The return and reason codes ofsystem service IXCxxxx, for example,IXCMSGO, are described in z/OS MVSProgramming Sysplex ServicesReference (SA22-7618).

ActionCheck the return code and reasoncode of the system service. Ifnecessary contact your IBM SupportCenter.

24 272336

ExplanationSystem Service error. The specifiedNetView service failed while aNetView command cannot bescheduled.


24 516

ExplanationSystem Service error. The activaterecovery failed (ESTEA).


24 523556

ActionIgnore the error if this error occurswhile the automation manager isterminating.


ErrorType

ErrorCode

Meaning

24 537

ExplanationSystem Service error. A task cannot beattached.


24 568569576577601620643

ExplanationSystem Service error. The specifiedMVS system service failed.


24 674675676677683684

ExplanationNetView PPI service failed.

ActionCheck the return code of the PPIservice. It is given in RSNCODE for683,674 through 677, or RETCODE for684. If necessary contact your IBMSupport Center.

24 679

ExplanationNetView service failed while adding orremoving a command processor.

ActionCheck the return code and reasoncode of the PPI service. If necessarycontact your IBM Support Center.




ErrorType

ErrorCode

Meaning

28 104

ExplanationREXX API error. A REXX API failedwhile a stem element retrieval wasattempted from the REXX variablepool, caused by INGPXSND() orINGPXRPC().

ActionCheck the return code and reasoncode of the REXX IRX EXCOM API. Ifnecessary contact your IBM SupportCenter.

28 112

ExplanationREXX API error. A REXX API failedwhile attempting to set a stemelement in the REXX variable pool,caused by INGPXRCV().


28 116

ExplanationREXX API error. A REXX API failedwhile INGPXRCV() attempted to setthe number of stem elements variable(stem.0) in the REXX variable pool.


28 120296312

ExplanationREXX API error. A call to the REXX APIfailed.


32 8488929618

ExplanationStorage problem. There is insufficientstorage for the queue, table or bufferoperation requested.




ErrorType

ErrorCode

Meaning

2186198204216220292332340485487488493496498500543560567585586594595596608613624626631621640678680685


36 380

ExplanationAn abend occurred.

RET describes the system or usercompletion code of the abend.

RSN describes the reason code of theabend.

ActionFor the meaning of system completioncode and reason code see z/OSmanual for system code.

The user completion code may bedescribed in Language EnvironmentMessages Manual or in other z/OScomponents.

See also additional error messagesfrom other z/OS components. Forexample, message CEE5101C mightbe issued if you missed to assign anOMVS segment to the user id.

36 523

This means that the data of an XCFrequest was received but it cannot bescheduled to the Automation Managerreceiver-queue because thecorresponding thread is no longerregistered to receive requests. If thishappens during termination of theAutomation Manager the message can beignored.

Error code 556 is caused by error code523 so message HSAM1050E with errorcode 556 may also appear.


ErrorType

ErrorCode

Meaning

36 nnn ExplanationInternal error.


40 440444448452456460464468

ExplanationEnvironment error.

ActionStart the DST INGPXDST.

System actionNone.

Operator responseRefer to the documentation of message AOF333I.

System programmer responseContact your IBM Support Center.

Classes0.

AOF351E COMMUNICATION MANAGERINITIALIZATION FAILED

ExplanationAn error was detected during initialization of thesystem automation communication manager DataService Task (DST).



System actionThe Data Service Task terminates.

Operator responseAnalyze the problem, referring to the explanation ofmessage AOF350E. Correct your input and retry thetask.


Classes0.

AOF352I COMMUNICATION MANAGERINITIALIZATION COMPLETE

ExplanationThe initialization module of the system automationcommunication manger has successfully initialized theData Service Task (DST).

System actionNone.



ClassesNone.

AOF353I EXTENDED XCF COMMUNICATIONDISABLED, LIMIT OF nnEXCEEDED

Explanation:For Automation Control, the number of AutomationAgents that can run concurrently in the same extendedXCF communication group is limited to three. The limitis reached and therefore the current Automation Agentcannot join the extended XCF group. The extended XCFcommunication group is identified by the parameterPLEXID in the member INGXINIT.

System action:Communication task continues but did not join theextended XCF communication group.

Operator response:

None.


AOF355E INCORRECT CALL TO FUNCTIONname RC=rc

ExplanationAn error was detected during parameter list validationof a system automation REXX API function.

System actionThe REXX function terminates due to a REXX syntaxerror.

Operator responseAnalyze the return code. Invoke the REXX functionname with a correct parameter list. The return code rccan have one the following values:

ValueMeaning

4An incorrect number of arguments was specified.

8Either the value of the data parameter is no stem,or stem.0 is nonnumeric, or a negative number.

12The value of the handle parameter is too long.

16The value of the records parameter is zero ornonnumeric.

20The value of the task parameter is too long.

24The value of the target parameter is too long.

40The handle parameter is required but no value wasspecified.

44The data parameter is required but no value wasspecified.

48The task parameter is required but no value wasspecified.

52The records parameter is required but no valuewas specified.




Classes0.

AOF356E COMMAND HANDLER INGRXCAMFAILED: ERROR=xx FN=yy RC=zz

ExplanationThe command handler failed with a return code. It canhave the following values:Value

Meaning4

Invalid RPC type8

REXX function failed. If xx is 8 then yy shows thereturn code from the REXX function.

12NetView pipe failed. If xx is 12 then yy=null and zzshows the return code from the pipe.

16Buffer.0 is wrong

System actionThe command handler terminates.

Operator responseRetry the operation. If the problem persists, contactyour system programmer.

System programmer responseRetry the operation. If the problem persists, contactyour system programmer.

AOF359I DIAGNOSTIC INFO: MOD=moduleINCIDENT=incident diagnostic-text

ExplanationThe purpose of this message is to provide diagnosticinformation to IBM service staff.

The variable module shows name of the modulethat detected the incident.The variable incident shows a unique ID for aninternally detected incident.The variable diagnostic-text shows useful text infree format. The text depends on the incident thatoccurred. For example, for INCIDENT=100, this isthe duplicate handle + seq-number.




AOF364I type entry INVALID TYPE OFSUBSYSTEM. EXPECTING value1,GOT value2, FOR MESSAGE msg

ExplanationA SA z/OS message trap routine is processing amessage. The job that issued the message isassociated with a subsystem that has a type that is notvalid for the message.

This typically happens when either the type isunspecified 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 inerror.The variable value1 is the TYPE that was expectedfor this message.The variable value2 is the TYPE specified in theACF.The variable msg is the message that triggered theproblem.

System actionProcessing stops. Automation for the messagespecified is not processed. This may cause furtherautomation errors if the message is required forautomation information, for example, UPMSG, etc.

Operator responseReport this error to your system programmer. This is aconfiguration error.

System programmer responseCorrect the configuration of the subsystem specified inthe Policy Database. Rebuild the Automation ControlFile and reload.

ClassesNone.



AOF365I NO ACTIVE LINK FOUND

ExplanationThe link between a consumer subsystem and aprovider subsystem is already in the requested state.The link status can be either ACTIVE or INACTIVE.

System actionNone.



ClassesNone.

AOF366I NO DYNAMIC LINK CONFIGUREDIN THE POLICY BETWEENconsumer AND provider

ExplanationActivating or deactivating a link between a consumersubsystem and a provider subsystem failed becausethe link was either not defined at all or it was notdefined as DYNAMIC in the automation policy.

The variable consumer is the subsystem name ofthe consumer.The variable provider is the subsystem name of theprovider.

System actionNone.

Operator responseVerify that you defined the correct consumer andprovider names. If these are correct, notify yoursystem programmer.

System programmer responseDefine a dynamic link in the automation policybetween the consumer and the provider.

ClassesNone.

AOF367I LINK ACTIVATED BETWEENconsumer AND provider

ExplanationLink activation was successful between the consumerand the provider application.


System actionNone.



ClassesNone.

AOF368I LINK DEACTIVATED BETWEENconsumer AND provider

ExplanationLink deactivation was successful between theconsumer and the provider application.


System actionNone.



ClassesNone.



AOF401E UNEXPECTED TIMEOUT FROMcommand in clist. PROCESSINGTERMINATED.

ExplanationA message was expected but was not received beforethe ‘WAIT’ time expired.

System actionThe requested function has not completedsuccessfully.



ClassesNone.

AOF403E UNEXPECTED WAIT EVENT(WC=wc) FROM command IN clist.PROCESSING TERMINATED.

ExplanationA message was expected, but instead an unexpectedevent code was returned.

System actionThe requested function has not completedsuccessfully.

Operator responseRefer to NetView Customization: Writing CommandLists for an explanation of the code. If it is anunexplained wait code, for example, an error code,contact your IBM Support Center. If it is a G code, forexample, GO, do not enter GO while waiting for thatcommand to process.


ClassesNone.

AOF408I MISSING OR INVALIDPARAMETER parm DETECTED INcommand. PROCESSINGTERMINATED.

ExplanationThe command command contains an invalid or missingparameter.

System actionProcessing stops. The requested function is notcompleted successfully.


System programmer responseCorrect the function call.

ClassesNone.

AOF415I NO SERVICE PERIODS DEFINEDFOR applid

ExplanationThe Automation engine found no service periodsdefined in the control file for this application.


Operator responseNone. This is an internal message.


ClassesNone.

AOF432I INVALID EVENT NAME

ExplanationThe event name was not found. Either it is not definedin system automation, or it contains invalid characters.




Operator responseEnter a valid event name.


ClassesNone.

AOF435I TYPE AN EVENT NAME AND PRESSENTER

ExplanationSystem automation is waiting for an event name to bespecified.


Operator responseType a valid event name.


ClassesNone.

AOF436I TYPE A RESOURCE NAME ANDPRESS ENTER

ExplanationSystem automation is waiting for an application nameto be specified.


Operator responseType a valid application name.


ClassesNone.

AOF438I EVENT event DEFINED BUT NOTUSED BY ANY TRIGGER

ExplanationThe event is defined in the automation control file(ACF), but it is not used by any trigger in the sysplex.




AOF440I NO TRIGGER DEFINED FOR applid

ExplanationThere is no trigger defined for the specifiedapplication.




ClassesNone.

AOF441E SETEVENT FAILED: FUNCTIONPARAMETER MUST BE SET ORUNSET

ExplanationSETEVENT/INGEVENT failed because the functionparameter was neither SET nor UNSET.




Operator responseSpecify the correct function parameter SET or UNSET.


ClassesNone.

AOF442I SET|UNSET EVENT event DONEFOR ALL AFFECTEDAPPLICATIONS ON system

ExplanationThe INGEVENT routine successfully completed thestatus file update for this event and all affectedapplications.




ClassesNone.

AOF447I DATE OUT OF RANGE

ExplanationThe date could generate a schedule conflict because itis in the range of 12/26/yy and 12/31/yy where yy iscomputed by the common global variableAOCCENTURYSWITCH and the current year.


Operator responseChange the date.


ClassesNone.

AOF448I INVALID DATE

ExplanationThe specified date is not valid.


Operator responseSpecify a valid date.


ClassesNone.

AOF449I OVERLAP EXISTS BETWEENACTIVE type TIMESLOT timeslotAND SPECIFIED type TIMESLOTtimeslot

ExplanationThe specified timeslot is in conflict with the currentlyactive timeslot. A timeslot is active when the start timehas passed, but not the end time.

The variable type shows the type of the timeslot(UP or DOWN).The variable timeslot shows the start and end timeof the time window.

System actionNone.

Operator responseCorrect the command.


ClassesNone.

AOF450I ORIGINAL TIME HAS PASSED ANDCANNOT BE CHANGED



ExplanationA time specified on the service periods panel is beforethe current time.


Operator responseEnter service period times later than the current time.


ClassesNone.

AOF451I PREVIOUS STOP TIME IS NOT‘****’

ExplanationThe ‘****’ in service periods shows that the serviceperiod will remain active the next day. If the last stoptime is ‘****’, the next start time must also be ‘****’indicating the continuity. Here, the operator modifiedthe service hours and specified ‘****’ as the first starttime, but the previous stop time is not ‘****’.


Operator responseEither change the last stop time to ‘****’, or change thefirst start time appropriately.


ClassesNone.

AOF452I PREVIOUS STOP TIME IS ‘****’.

ExplanationThe operator modified the service hours and did notspecify ‘****’ as the first start time, but the previousday’s last stop time is ‘****’.


Operator responseEither change the last stop time to ‘****’, or change thefirst start time appropriately.


ClassesNone.

AOF453I NEXT START TIME IS ‘****’

ExplanationThe next day’s first start time is ‘****’, but when theoperator modified the service hours, ‘****’ was notspecified as the last stop time.


Operator responseEither change the start time to ‘****’, or change the laststop time accordingly.


ClassesNone.

AOF454I NEXT START TIME IS NOT ‘****’

ExplanationThe ‘****’ in service periods indicates that the serviceperiod will remain active the next day. If the last stoptime is ‘****’, the next start time must also be ‘****’indicating the continuity. In this case, the operatormodified the service hours and specified ‘****’ as thelast stop time, but the next start time is not ‘****’.




Operator responseEither change the start time to ‘****’, or change the laststop time accordingly.


ClassesNone.

AOF456I No times allowed after ‘DOWN’

ExplanationWhen ‘DOWN’ is the first start or stop time, no timescan be entered later that day. The operator modifiedthe service hours and specified ‘DOWN’ as the firststart time, but additional times follow it.


Operator responseCorrect the service hours.


ClassesNone.

AOF457I BOTH 'FROM' AND 'TO' TIMESMUST BE ENTERED, OR BOTHMUST BE BLANK

ExplanationA 'From' or 'To' time was entered. Either both 'From'and 'To' times must be entered, or both must be blank.


Operator responseEnter both 'From' and 'To' times, or blank both out.


ClassesNone.

AOF458I NO TIMES ALLOWED AFTER ‘****’

ExplanationBecause ‘****’ shows that a service period will remainactive until the next day, no times are allowed after the‘****’.


Operator responseCorrect the service hours.


ClassesNone.

AOF459I INVALID TIME

ExplanationThe specified time is not valid. The time must bebetween 0000 and 2359.


Operator responseEnter a valid time.


ClassesNone.

AOF461I TIME MUST ALSO BE ‘DOWN’.

ExplanationEither in the first Start or in the Stop field of thewindow, DOWN was specified. DOWN must bespecified in both, the first Start and first Stop window.




Operator responseEither specify DOWN in both, the Start and Stop firstservice period fields, or specify valid times in both.


ClassesNone.

AOF462I ONLY THE FIRST START TIME MAYBE ‘****’

Explanation‘****’ was specified in a Start field other than the firstone. ‘****’ is a valid entry only in the first Start field,because it indicates that a service period continuesfrom the previous day.


Operator responseCorrect the time.


ClassesNone.

AOF463I TIME MUST BE NUMERIC

ExplanationThe 'From' or 'To' time specified is not numeric,asterisks, or DOWN.


Operator responseCorrect the time.


ClassesNone.

AOF464I THE FIRST 'FROM' AND 'TO' TIMECANNOT BE BLANK

ExplanationThe first 'From' and 'To' time must be specified. Theyare required parameters.


Operator responseCorrect the time by specifying valid times in the firstfields.


AOF465I TRIGGER trigger HAS NO SERVICEPERIODS

ExplanationNo service periods are defined for this trigger.




ClassesNone.

AOF466I CHANGED TIME MUST BE LATERTHAN CURRENT TIME

ExplanationThe time change specified was prior or equal to thecurrent time.




Operator responseSpecify a time change later than the current time, orquit the function.


ClassesNone.

AOF467I DELETION NOT ALLOWEDBECAUSE IT CREATES ASCHEDULE CONFLICT

ExplanationThe overrides cannot be deleted because this wouldcreate a conflict in the existing schedule(s). At first, theearliest start time of the regular schedule and of theoverride is determined. Then the latest stop time ofboth schedules is determined. If the actual time of theday is between those two times specified, this resultsin a schedule conflict. DOWN-DOWN is treated as‘0000-2400’.


Operator responseChange the schedule to eliminate the conflict, or quitthe function.


ClassesNone.

AOF468I TYPE ‘D’ IF DELETE REQUIRED

ExplanationAn invalid character was specified in the Delete field.


Operator responseType ‘D’ to delete the override.


ClassesNone.

AOF469I 'FROM' TIME MUST BE LATERTHAN PREVIOUS 'TO' TIME

ExplanationThe 'From' time of the service window is not later thanthe 'To' time of the previous service window.


Operator responseCorrect either the 'From' or the 'To' time.


AOF470I 'TO' TIME MUST BE LATER THAN'FROM' TIME

ExplanationThe 'To' time of the service window is not later thanthe 'From' time of the same service window.


Operator responseCorrect either the 'From' or the 'To' time.


AOF475I EVENT event IS NOT USED BYRESOURCE applid

ExplanationThe event is not defined in the trigger that is used bythe resource.



The variable event shows the event that is not used.The variable applid shows the APPLID of theresource.

System actionThe command terminates immediately.

Operator responseCheck the scope parameters of the command, correctthe value(s). Then issue the command again.


AOF476I EVENT event IS NOT USED ONSYSTEM system

ExplanationThe event is defined but it is not used by any trigger onthe specified system.

The variable event shows the event that is not used.The variable system shows the name of the system.

System actionThe command terminates immediately.

Operator responseCheck the RANGE parameter of the command andcorrect the value. Then issue the command again.


AOF478I WILDCARDS ARE NOTSUPPORTED

ExplanationThe INGEVENT command supports down-levelsystems. Because a down-level system does not knowa wildcard, this support is suppressed for the timethese down-level systems are supported.

System actionThe command is not executed.

Operator responseCorrect the parameter and reissue the command.


ModuleINGRYEV0

AOF479I SERVICE PERIOD REQUESTS TOUP-LEVEL SYSTEMS ARE NOTSUPPORTED

ExplanationA service period request in line mode to an up-levelsystem is not supported. The reason for this is that thedefinitions of service periods on two different systemlevels, for example SA OS/390 1.3 and SA OS/390 2.1,are not compatible.

System actionThe request is rejected.



ModuleINGRVP90

AOF501E time : RECOVERY FOR restyperesname HALTED - numberERRORS SINCE error_time ONerror_date - CRITICAL ERRORTHRESHOLD EXCEEDED

ExplanationThe resource has experienced the indicated number oferrors during the time interval defined in theautomation control file for the critical error threshold.

The variable time shows the time the exceptionmessage was generated.The variable restype shows the type of theresource.The variable resname shows the name of theresource.The variable number shows the number of errorsthat has occurred.The variable error_time shows the time of the firsterror to occur within the time interval.



The variable error_date shows the date of the firsterror to occur within the time interval.

System actionIf resname is a network resource, the recovery processis ended. If resname is a system resource, the recoveryprocess is ended or the appropriate commands areissued.



Classes: 40 41 44 51.

AOF502I time : RECOVERY FOR restyperesname, CONTINUING - numberERRORS SINCE error_time ONerror_date - FREQUENT ERRORTHRESHOLD EXCEEDED

ExplanationThe frequent error threshold has been exceeded for aresource. This message reports the number of errorsthat occurred during the time interval defined in theautomation control file for the frequent errorthreshold.

The variable time shows the time the exceptionmessage was generated.The variable restype shows the type of theresource.The variable resname shows the name of theresource.The variable number shows the number of errorsthat occurred.The variable error_time shows the time of the firsterror that occurred within the time interval.The variable error_date shows the date of the firsterror that occurred within the time interval.

System actionIf the resource identified in this message is a networkresource, the recovery process continues. If it is asystem resource, the appropriate commands areissued.


System programmer responseMake sure the policy for shutting down this resource inthe automation control file is accurate. Determinewhether other action needs to be taken.

Classes: 40 43 51.

AOF503I time : RECOVERY FOR restyperesname CONTINUING - numberERRORS SINCE error_time ONerror_date - INFREQUENT ERRORTHRESHOLD EXCEEDED

ExplanationThe infrequent error threshold has been exceeded fora resource. This message reports the number of errorsthat occurred during the time interval defined in theautomation control file for the infrequent errorthreshold.

The variable time shows the time the exceptionmessage was generated.The variable restype shows the type of theresource.The variable resname shows the name of theresource.The variable number shows the number of errorsthat has occurred.The variable error_time shows the time of the firsterror to occur within the time interval.The variable error_date shows the date of the firsterrorto occur within the time interval.

System actionIf the resource identified in this message is a networkresource, the recovery process continues. If it is asystem resource, the appropriate commands areissued.


System programmer responseMake sure the policy for shutting down this resource inthe automation control file is accurate. Determinewhether other action needs to be taken.

Classes: 40 43 52.

AOF510I time : resname flag FLAG HASBEEN SET TO status BY OPERATORoperator_ID



ExplanationThe flag status for the resource identified in thismessage has been set as indicated.

The variable time shows the time when thismessage was generated.The variable resname shows the name of theresource.The variable flag shows the name of the automationflag that is set.The variable status shows the automation status.The variable operator_ID shows the name of theoperator who changed the automation status.

System actionThe automation status is set.

Operator responseYou can issue the DISPFLGS command to view actualand effective values for the specific resource flag.


Classes40, 43.

AOF511I time : member AUTOMATIONCONTROL FILE COMMON VALUESHAVE BEEN INITIALIZED

ExplanationThe automation control file data has been used tocreate common variables used throughout theautomation process.

The variable time shows the time this message wasgenerated.The variable member shows the name of theconfiguration member used.




Classes40, 43.

AOF512I time : resname flag FLAG HASBEEN RESET BY OPERATORoperator_ID. THE EFFECTIVE FLAGVALUE IS: efinfo

ExplanationThe flag status for the resource identified in thismessage has been set as indicated.

The variable time shows the time when thismessage was generated.The variable resname shows the name of theresource.The variable flag shows the name of the automationflag that is set.The variable operator_ID shows the name of theoperator who changed the automation status.The variable efinfo shows the effective value of flagafter RESET operation.

The additional EFFECTIVE FLAG VALUE information isonly displayed for INGAUTO RESET with SCOPE=ONLY.

System actionThe automation status is set.

Operator responseYou can issue the DISPFLGS command to view actualand effective values for the specific resource flag.


Classes40, 43.

AOF513I time : resname flag flag cannot beset or reset by operatoroperator_ID. The resource issuspended.

ExplanationThe flag status for the resource cannot be set or resetbecause the resource has been suspended by theINGSUSPD command.

The variable time shows the time when thismessage was generated.The variable resname shows the name of theresource.



The variable flag shows the name of the automationflag that was affected.The variable operator_ID shows the name of theoperator who wanted to change the automationstatus.

System action:The automation status is not changed.

Operator response:You can use the INGSUSPD command to reset the flagto its original value.


Class40, 43.

AOF514I RESOURCE resname HAS BEENSUSPENDED

ExplanationThe agent has processed the manager order tosuspend the resource resname.

The resname variable shows the name of thesuspended resource.

System action:The resource is suspended.



AOF515I RESOURCE resname HAS BEENRESUMED

ExplanationThe agent has processed the manager order to resumethe resource resname.

The resname variable shows the name of theresumed resource.

System action:The resource is resumed.



AOF521I MONITORING target FAILED : text

ExplanationMonitoring failed for the reason specified in themessage text.

The variable target shows the name of the targetsystem.

System actionNone.


System programmer responseDetermine the cause of the problem from the messagetext. Contact the IBM support representative ifrequired.

Classes0.

AOF522I SYSTEM target IS LOADING: text

ExplanationTarget system is loading. The message text indicatesthe system loading status.





Classes0.

AOF523W SYSTEM target IS INACTIVE: text

ExplanationDefinition or hardware problem detected.




System actionSystem target status changed to inactive.


System programmer responseDetermine the cause of the problem from the messagetext. Correct the problem as indicated in the messagetext.

Classes0.

AOF524I MONITORING target : text

ExplanationOperational or configuration problem detected.


System actionNone.

Operator responseTry to correct the problem. Contact your systemprogrammer if required.

System programmer responseCorrect the problem as indicated in the message text.

Classes0.

AOF530I time : CONFIGURATION TIMERPROCESSING HAS BEENCOMPLETED

ExplanationThis message issued when all the timer entries in theautomation control file have been processed and therequired actions have been performed.





Classes40, 43.

AOF531I time : OUTSTANDING REPLYPROCESSING HAS BEENCOMPLETED

ExplanationThis message is issued when outstanding replies havebeen captured and forwarded to SDF (Status DisplayFacility). It is produced at system automation startup,when SDF is recycled, or whenever the gatewayconnection to the focal point is established, changed,or reset.





Classes40, 43.

AOF532I time : AUTOMATIONENVIRONMENT HAS BEENINITIALIZED

ExplanationThe automation environment has been initialized.







Classes40, 43.

AOF534I time : AUTOMATION TIMERS HAVEBEEN INITIALIZED ORRESTARTED

ExplanationThe automation timers have been initialized orrestarted.





Classes40, 43.

AOF535I time : AUTOMATIONENVIRONMENT HAS BEENCLEARED

ExplanationAfter an ACF COLD command is issued to reload anautomation control file, the existing common globalvariables are cleared in readiness for fresh data.





Classes40, 43.

AOF537I time : resname status - restyperesname cmd COMMAND(S) NOTFOUND FOR console - text

ExplanationOne or more commands issued from the consoleidentified in this message could not be processed.

The variable time shows the time this message wasgenerated.The variable resname shows the name of theresource.The variable status shows the status of theresource.The variable restype shows the type of theresource.The variable cmd shows the command to beprocessed.The variable console shows the console-ID orconsole-CUU having difficulty.The variable text shows the short form of themessage.

System actionNone.


System programmer responseDetermine whether a configuration error or a usererror exists, by reviewing the values supplied and theautomation control file.

Classes: 40 43 52.

AOF538I time : OUTSTANDING REPLY: MVS -reply_ID msg_text

ExplanationAutomation will not reply to an outstanding reply.

The variable time shows the time this message wasgenerated.The variable reply_ID identifies the outstandingreply that will not be replied to.



The variable msg_text shows the message text forthe outstanding reply.

System actionNone.

Operator responseReply to outstanding reply accordingly.


Classes: 40 41.

AOF540I time : INITIALIZATION RELATEDPROCESSING HAS BEENCOMPLETED

ExplanationProcessing required to complete initialization after theautomation environment has been initialized has beencompleted.

The variable time shows the time that the messagewas generated.




Classes40, 43.

AOF541I time : SYSTEM MONITORINGFUNCTION COMPLETED FORresourcelist

ExplanationIndicates completion of a monitor cycle initiated eitherby using a timer or by operator request.

• The variable time shows the time that the messagewas generated.

• The variable resourcelist shows one of:

– ALL SUBSYSTEMS WITH NO INDIVIDUALMONITORING (MONITOR $SYSTEM)

– ALL SUBSYSTEMS (MONITOR ALL or *)– A list of resources that monitoring has been

completed for as the result of a single subsystemor wildcard request




Classes40, 43.

AOF542I Load of dynamic resources ispending

Explanation:This message is issued after the initialization of thestatic resources is completed and before the dynamicresources are loaded.

System action:Processing continues.



Classes40, 43.

AOF543E time : COMMAND cmd WASCANCELED. RC=retcode

ExplanationCommand cmd was canceled because the prevailingenvironmental conditions for system automation werenot adequate for the command to completesuccessfully.

The variable time shows the time this message wasgenerated.The variable cmd shows the command that wasaffected.



The variable retcode shows the condition codeidentifying the reason for the cancelation of thecommand. outstanding reply.

System actionThe command is terminated.

Operator responseTry re-issuing the command later.


Classes40, 43.

AOF545I clist: KEYWORD keyword HAS ANINVALID VALUE value,PARAMETER IGNORED

ExplanationEither the keyword identified in this message or thevalue specified for it is not valid. The parametercontaining this value will be ignored.

The variable clist shows the name of the commandlist.The variable keyword shows the keyword that is notvalid or has a value that is not valid.The variable value shows the value specified for thekeyword.

System actionNone.


System programmer responseCorrect the problem by changing the coding for thekeyword or value.

ClassesNone.

AOF546I clist: NO FUNCTION REQUESTED,NOTHING DONE

ExplanationNo function keyword was specified to cause an action.No action was taken.

System actionNone.


System programmer responseDetermine the cause of the problem. See whethermessage AOF545I was also issued. It is likely that acoding error caused the problem. For example, akeyword might have been specified with no defaultvalue possible, due to a coding error.

ClassesNone.

AOF547I Load of dynamic resources isstarting

Explanation:This message is issued right before the dynamicresources are loaded.




Classes40,43

AOF548I Load of dynamic resourcescompleted

Explanation:This message is issued after the dynamic resourceshave been loaded successfully or after a failureoccurred.






Classes40,43

AOF550I STATUS OF monitor MONITOR :OBSERVED=observedHEALTH=health - text

ExplanationThis message is generated when either the status of amonitor resource or the health status of the objectsthat the monitor is watching changes. It shows theresource's new status.

The variable monitor shows the name of themonitor resource.The variable observed shows the observed status ofthe monitor resource.The variable health shows the health status of themonitored objects.The variable text shows additional information.

System actionNone.



AOF551I group GROUP STATUS FOR typeAPPLGROUP IS observed

ExplanationThis message is generated when the status of anapplication group changes. It shows the group's newstatus.

The variable group shows the name of theapplication group.The variable type shows whether the applicationgroup belongs to a system or a sysplex.The variable observed shows the observed status ofthe application group.

System actionNone.



AOF561A time : JES2 RESOURCE DRAINING- opt COMMAND NOT FOUND TOFORCE DRAIN. OPS ACTIONREQUIRED

ExplanationThe indicated resource is shutting down, but nocommands were found to drain the indicated resourcewith the method of FORCE.

The variable time shows the time this message wasgenerated.The variable opt shows the parameter for FORCEDRAIN.

System actionNone.

Operator responseManually drain the indicated resource.

System programmer responseUse the customization dialogs to add commands forthe indicated action to the automation control file. Forfurther information, refer to IBM Z System AutomationDefining Automation Policy.

Classes40, 43, 44, 46.

AOF562I time : JES2 RESOURCE DRAINING- resource IS status. OPS ACTIONREQUIRED TO DRAIN

ExplanationThe JES2 resource status is not ACTIVE, INACTIVE,DRAINING, or DRAINED.

The variable time shows the time this message wasgenerated.The variable resource shows the name of theresource.The variable status shows the JES2 resourcestatus.

System actionNone.



Operator responseManually drain the resource.


Classes40, 43, 44, 46.

AOF563A time : JES2 RESOURCE DRAINING- UNKNOWN RESTYPE: resource.OPS ACTION REQUIRED TO DRAIN

ExplanationThe resource identified in this message is unknown.

The variable time shows the time this message wasgenerated.The variable resource shows the name of theresource.

System actionNone.

Operator responseManually drain the resource.

System programmer responseCheck the netlog for further information and performproblem determination.

Classes40, 43, 44, 46.

AOF564A {time: JES2 SHUTTING DOWN -message - OPERATORINTERVENTION REQUIRED | title |task_names| job_names|device_names}

ExplanationThis message reports that JES2 is being shut downand there are jobs or tasks (or both) that are active, ordevices that have not yet been drained, or all of these.This message is followed by one or more AOF654Amessages that lists the jobs or tasks that are active(job_names, task_names) or the devices that have notbeen drained (device_names). Each of these messagesshows a list of job names, task names or devicenames.

• The variable time• The variable message• The variable title is one of:

TASKSJOBSDEVICES

• The variable task_names shows the names of tasksthat are still active.

• The variable job_names shows the names of jobsthat are still active.

• The variable device_names shows the names ofdevices that are still active.

System actionThe system waits for devices and initiators to bedrained. This message is repeated until JES2 is shutdown.

Operator responseWait for devices and jobs to complete and automationto shutdown JES2. Commands can be issued to forcejobs or drain devices. Consult your systemprogrammer if the situation requires manualintervention.

System programmer responseIf this situation requires immediate shutdown instructoperations personnel as to how to accomplish this.

Classes40, 43, 44, 46.

AOF565A time : JES2 RESOURCESDRAINING BUT DRAIN COMMANDTURNED OFF ONsubsystem_function ENTRY FORresource_name - recommendation

ExplanationJES2 resources are draining. However, the draincommand is turned off for the identified subsystemfunction (subsystem_function) and resource(resource_name).

The variable time shows the time this message wasgenerated.The variable subsystem_function shows thefunction being performed.The variable resource_name shows the name of theresource.



The variable recommendation shows an actionrecommended for solving the problem.

System actionNone.

Operator responseIssue commands to drain the resource identified inthis message. Contact your system programmer.

System programmer responseIf you want to automate draining of the resourceidentified in this message, use the customizationdialogs to correct the automation control file entry forthe subsystem function and resource. For moreinformation, refer to IBM Z System Automation DefiningAutomation Policy.

Classes40, 43, 44, 46.

AOF566I time: JES2 PROCESSINGREJECTED IN command - JES2NOT IN SHUTDOWN PROCESS

ExplanationShutdown related JES2 processing rejected in routinecommand, because shutdown isn't in progress forJES2.

The variable time shows the time this message wasgenerated.The variable command shows the name of theroutine, rejecting JES2 processing.

System actionNone.


System programmer responseCheck the netlog for further information on whycommand has been issued outside the shutdownprocess of JES2.

Classes:None

AOF568I time : STATUS OF domainOUTBOUND GATEWAY TO DOMAINtarget_domain IS status

ExplanationThis message shows the status of the outboundgateway from this domain to the target domain.

The variable time shows the time this message wasgenerated.The variable domain shows the domain initiatingthe connection to the target domain.The variable target_domain shows the domain thatthe gateway is connected to.The variable status shows the current status of thegateway connection.

System actionNone.



Classes40, 43, 44, 46.

AOF569I time : STATUS OF domainINBOUND GATEWAY FROMDOMAIN target_domain IS status

ExplanationThis message shows the status of the inboundgateway from the requested target domain to thisdomain.

The variable time shows the time this message wasgenerated.The variable domain shows the name of thisdomain.The variable target_domain shows the requestedtarget domain connected to this domain.The variable status shows the current status of thegateway connection.

System actionNone.





Classes40, 43, 44, 46.

AOF570I time : ISSUED "command" FORrestype resname - text

ExplanationA command has been issued for the resourceidentified in the message.

The variable time shows the time this message wasgenerated.The variable command shows the command thathas been issued.The variable restype shows the type of theresource.The variable resname shows the name of theresource.The variable text shows additional information.

System actionNone.



Classes40, 43.

AOF571I time : resname SUBSYSTEMSTATUS FOR JOB job_name ISstatus - text

ExplanationThis message is generated when the status of aresource changes. It shows the resource’s new status.

The variable time shows the time this message wasgenerated.The variable resname shows the name of theresource.The variable job_name shows the name of the job.The variable status shows the new status of theresource.The variable text shows additional information.

System actionNone.



Classes: 40 43 45.

AOF572I CGLOBALS NOT INITIALIZED FORAUTOMATED FUNCTION autofunc -UNABLE TO ROUTE COMMANDcommand, operand_1, operand_2,operand_3

ExplanationThe command identified in this message could not berouted properly. The first three operands of thecommand are shown in the message, to aid analysis ofthe problem.

The variable autofunc shows the automatedfunction that the command could not be routed to.If no automated function was specified, this will beblank.The variable command shows the command thatwas not routed properly.The variable operand_1 shows the first operand ofthe command. This variable is blank if thecommand has no required operands.The variable operand_2 shows the second operandof the command. This variable is blank if thecommand has less than two required variables.The variable operand_3 shows the third operand ofthe command. This variable is blank if thecommand has less than three required variables.

System actionNone.


System programmer responseCheck the netlog for messages related to aninitialization failure. Determine the cause of the failureand correct the problem.

Classes: 40 43 45.



AOF573I time : AUTOMATED task restypeHAS BEEN RESTARTED

ExplanationAn automated task has been restarted.

The variable time shows the time this message wasgenerated.The variable task shows the task identifier of thetask that has been restarted.The variable restype shows the type of theresource.

System actionNone.



Classes: 40 43 45.

AOF574I time : RECOVERY INITIATED, JOBjob_name, - RECEIVED MSG "text"

ExplanationRecovery has been started for a job.

The variable time shows the time this message wasgenerated.The variable job_name shows the name of the jobthat recovery has been started for.The variable text shows the message text received.

System actionNone.



Classes: 40 43 45.

AOF575A time : JOB job_name HAS ENDED -AUTOMATED RECOVERY NOT INPROGRESS - OPERATIONINTERVENTION REQUIRED

ExplanationA job has ended and automation has determined thatoperator intervention is required.

The variable time shows the time this message wasgenerated.The variable job_name shows the name of the jobthat ended.

System actionAutomation is discontinued for the specified job.

Operator responseDetermine what is wrong with the job and contact yoursystem programmer.

System programmer responseReview the netlog to determine when and whyprocessing of the job failed. You might need to modifythe automation control file to correct the problem ifyou 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 INTERVENTIONREQUIRED

ExplanationA job has ended and automation is set to OFF for theresource. Operator intervention is required to restartthe resource.

The variable time shows the time this message wasgenerated.The variable job_name shows the name of the jobthat ended.The variable status shows the status of theresource.The variable autotype shows the type ofautomation.

System actionNone. No automation is attempted.

Operator responseRestart the resource.




Classes: 40 41 44 45 46.

AOF577E time : RECOVERY FOR restyperesname (JOB job_name) HALTED -CRITICAL THRESHOLD EXCEEDED

ExplanationAutomated recovery of a resource will not occurbecause the critical error threshold set for theresource has been exceeded. Operator intervention isrequired to restart the resource.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resource.The variable resname shows the name of theresource.The variable job_name shows the name of the job.

System actionNo automated recovery of the resource occurs.


System programmer responseCheck the netlog for further information on why theresource has failed.

Classes: 40 41 44 50.

AOF578I time : RECOVERY FOR restyperesname (JOB job_name)CONTINUING - FREQUENTTHRESHOLD EXCEEDED

ExplanationA resource has failed and automated recovery isoccurring. The frequent error threshold set for theresource has been exceeded, but automationcontinues the recovery.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resourcethat failed.The variable resname shows the name of theresource that failed.The variable job_name shows the name of the job.

System actionAutomated recovery of the resource continues.


System programmer responseCheck the netlog for further information on why theresource has failed.

Classes: 40 43 51.

AOF579I time : RECOVERY FOR restyperesname (JOB job_name)CONTINUING - INFREQUENTTHRESHOLD EXCEEDED

ExplanationAutomated recovery is occurring for a resource. Theinfrequent error threshold set for the resource hasbeen exceeded, but automation continues therecovery.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resourcethat automated recovery is occurring for.The variable resname shows the name of theresource that automated recovery is occurring for.The variable job_name shows the name of the job.

System actionAutomated recovery for the resource continues.


System programmer responseCheck the netlog for further information as to why theindicated resource failed.

Classes: 40 43 52.

AOF580I time : auto AUTOMATION FORrestype resname (JOB job_namejob_number) IS SET OFF -AUTOMATION NOT ATTEMPTEDFOR MSG text

ExplanationAutomation has been set to OFF for a resource. As aresult, no automation has been attempted for themessage shown.




The variable auto shows the type of automation.The variable restype shows the type of resourcethat automation has been set OFF for.The variable resname shows the name of theresource 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 thejob.The variable text shows the message that has notbeen automated.

System actionNone.



Classes40, 43, 44.

AOF581I time : autotype SUCCESSFUL FORresource - text

ExplanationAutomation caused by a message was successful for aresource.

The variable time shows the time this message wasgenerated.The variable autotype shows the type ofautomation.The variable resource shows the name of theresource that automation was successful for.The variable text shows the message that causedautomation to be initiated.

System actionNone.



Classes: 40 43 45.

AOF582A time : RECOVERY UNSUCCESSFUL- JOB job_name - OPERATORINTERVENTION REQUIRED FORMESSAGE text

ExplanationRecovery was not successful for a job. Operatorintervention is required for the message shown, whichcould not be automated.

The variable time shows the time this message wasgenerated.The variable job_name shows the name of the jobthat recovery was not successful for.The variable text shows the message that could notbe automated.

System actionNone.

Operator responseManual intervention is required to handle the problem.

System programmer responseDetermine from the netlog why recovery wasunsuccessful. Review the commands coded in theautomation control file.

Classes: 40 43 44 45 46.

AOF583I time : auto AUTOMATION FORrestype resname (JOB job_name)IS SET OFF - AUTOMATION NOTATTEMPTED

ExplanationAutomation has been set to OFF for resource. As aresult, no automation has been attempted.

The variable time shows the time this message wasgenerated.The variable auto shows the type of automationflag.The variable restype shows the type of resourcethat automation has been set OFF for.The variable job_name shows the name of the job.

System actionNone.





Classes40, 43, 44.

AOF584I time : resname autotype IS SET ON- autotype action NOT FOUND FORrestype resname - "text"

ExplanationAutomation was set ON for a resource, but nocommands or replies were found in the automationcontrol file for the type of automation described by thevariable autotype.

The variable time shows the time this message wasgenerated.The variable resname shows the resource name.The variable autotype shows the type of automationthat no commands or replies were found for.The variable action shows the type of action thatshould have been taken. Possible values areCOMMAND and REPLY.The variable restype shows the type of resource.The variable text shows the message that calledautomation.

System actionAutomation is not performed for the message shown.


System programmer responseCheck the entries in the automation control file andcorrect them as needed.

Classes40, 43, 44.

AOF585I time : autotype OF resname ISALREADY IN PROGRESS - text

ExplanationAutomation is in progress for a resource. No additionalautomation of the same type will occur until thecurrent automation is complete.


The variable autotype shows the type of automationin progress.The variable resname shows the name of theresource that automation is in progress for.The variable text shows the message that calledautomation.

System actionThe current automation continues.



Classes40, 43, 44.

AOF586A time : TIME OUT OCCURRED : MVSD C,B FAILED - AUTOMATIONRECOVERY ATTEMPTTERMINATED

ExplanationA console buffer shortage recovery attempt has timedout. The recovery attempt is terminated.

The variable time shows the time when thismessage was generated.

System actionNone.


System programmer responseDetermine why the MVS D C,B system command isnot responding. Should the console be overloadedwith excessive messages, issue the MVS K commandto resolve console buffer shortages. Refer to MVS/ESASystem Commands for further details.

Classes40, 43, 44, 46.

AOF587I time : RECOVERY FOR restyperesname CONTINUING - CRITICALTHRESHOLD action



ExplanationRecovery for a resource is in progress and the criticalerror threshold for the resource has been exceeded.The commands specified to be issued when thishappens have been issued.

The variable time shows the time this message wasgenerated.The variable restype shows the type of the resourcethat recovery is in progress for.The variable resname shows the name of theresource that recovery is in progress for.The variable action is either 'COMMANDS ISSUED'or 'EXCEEDED'

System actionIf action is 'COMMANDS ISSUED' then automationissues the commands specified in the automationcontrol file for critical threshold. If action is'EXCEEDED' processing continues.


System programmer responseDetermine why the critical threshold has been reachedfor this resource.

Classes: 40 41 44 50.

AOF588I time : RECOVERY FOR restyperesname CONTINUING -FREQUENT THRESHOLD action

ExplanationRecovery is in progress for a resource and the frequenterror threshold has been exceeded. The commandsspecified to be issued when this happens have beenissued.

The variable time shows the time this message wasgenerated.The variable restype shows the type of the resourcethat recovery is in progress for.The variable resname shows the name of theresource that recovery is in progress for.The variable action is either 'COMMANDS ISSUED'or 'EXCEEDED'.

System actionIf action is 'COMMANDS ISSUED' then automationissues the commands specified in the automation

control file for the frequent error threshold. If action is'EXCEEDED' processing continues.


System programmer responseDetermine why the frequent error threshold for thisresource was exceeded.

Classes: 40 43 51.

AOF589I time : RECOVERY FOR restyperesname CONTINUING -INFREQUENT THRESHOLD action

ExplanationRecovery is in progress for a resource and theinfrequent error threshold for the resource has beenexceeded. The commands specified to be issued whenthis happens have been issued.

The variable time shows the time this message wasgenerated.The variable restype shows the type of the resourcethat recovery is in progress for.The variable resname shows the name of theresource that recovery is in progress for.The variable action is either 'COMMANDS ISSUED'or 'EXCEEDED'

System actionIf action is 'COMMANDS ISSUED' then automationissues the commands specified in the automationcontrol file for the infrequent error threshold. If actionis 'EXCEEDED' processing continues.


System programmer responseDetermine from the netlog why the errors areoccurring.

Classes: 40 43 52.

AOF592E SHUTDOWN REJECTED - autotypeFLAG FOR subsystem IS OFF

ExplanationShutdown processing is rejected for a resource thatautomation is set to OFF for.



The variable autotype shows the type of automation(AUTOMATION or TERMINATION).The variable subsystem indicates the resource inquestion.

System actionNone.

Operator responseShut down the resource manually or change theautomation flag to ON, and re-invoke theINGREQ=STOP command.


ClassesNone.

AOF593A time : ALL SHUTDOWNCOMMANDS/REPLIES FOR restyperesname (JOB job_name) HAVEBEEN ISSUED - OPERATORINTERVENTION REQUIRED

ExplanationAll shutdown commands in the automation control filehave been issued and a resource still has not shutdown. Operator intervention is required to shut downthe resource.

The variable time shows the time this message wasgenerated.The variable restype shows the type of resourcethat has not shut down.The variable resname shows the name of theresource that has not shut down.The variable job_name shows the name of the job.

System actionAutomation waits for the resource to be shut downmanually.

Operator responseShut down the resource manually and notify yoursystem programmer.

System programmer responseDetermine from the netlog why the resource did notshut down.

Classes40, 43, 44, 46.

AOF595E time : restype resname (JOBjob_name) STATUS NOTAUTODOWN - STATUS IS status -RESTART NOT ATTEMPTED

ExplanationA resource has been shut down but its status is notAUTODOWN. No restart will be attempted.

The variable time shows the time this message wasgenerated.The variable restype shows the type of the resourcethat was shut down.The variable resname shows the name of theresource that was shut down.The variable job_name shows the name of the job.The variable status shows the status of theresource.

System actionNone.


System programmer responseDetermine why the status of the resource is notAUTODOWN after shutdown. Either you must restartthe resource manually or you must change the statusto DOWN using the SETSTATE command and allowautomation to start the resource.

Classes40, 43.

AOF597A time : percent% MAX PASSESREACHED FOR console_ID -suggestion

ExplanationCommands have been exhausted for a console.

The variable time shows the time this message wasgenerated.The variable percent shows the percentage of WTObuffer shortage.The variable console_ID identifies the console thatreached the buffer storage percentage.



The variable suggestion shows a recommendedaction for resolving the condition reported by themessage.

System actionRecovery ends.

Operator responseCheck for any outstanding REPLY, MOUNT, or multilinemessages that are being held. These messages usethe WTO buffer storage.


Classes: 40 43 52.

AOF598A time : percent% MAX PASSESREACHED FOR ALL CONSOLESUSING > count BUFFERS - autotypeATTEMPT ENDED - suggestion

ExplanationCommands have been exhausted for all consoles.

The variable time shows the time this message wasgenerated.The variable percent shows the percentage of WTObuffer shortage.The variable count shows the number of buffersused.The variable autotype shows the type ofautomation.The variable suggestion shows a recommendedaction for resolving the condition reported by themessage.

System actionRecovery ends.

Operator responseCheck for any outstanding REPLY, MOUNT, or multilinemessages that are being held. These messages useWTO buffer storage.


Classes: 40 43 52.

AOF599A time : percent% NO CONSOLESFOUND USING MORE THAN count

BUFFERS - autotype ATTEMPTENDED

ExplanationNo console has reached the threshold set for numberof buffers. No recovery is attempted.

The variable time shows the time this message wasgenerated.The variable percent shows the percentage of WTObuffer shortage.The variable count shows the number of buffersused.The variable autotype shows the type ofautomation.

System actionNone.

Operator responseIf you suspect a problem with WTO buffers, additionalchecking is required to correct the problem. Contactyour system programmer.

System programmer responseEither verify that the “number of buffers” threshold isset to a value that will accommodate demands, orallow recovery to detect that the threshold has beenexceeded.

Classes: 40 43 52.

AOF601E product_name IS DOWNLEVEL -PREREQ FOR SA z/OS IS NOTFULFILLED

ExplanationThe prerequisites for SA z/OS are not fulfilled. SA z/OScannot be started.

The variable product_name indicates the product inquestion

System actionProcessing terminates.


System programmer responseInstall the required prerequisites.



ClassesNone.

AOF602D ENTER 'RETRY' OR 'CANCEL' –DOMAIN domid

ExplanationA severe error, indicated by other messages, occurredduring base initialization.

The variable domid shows the NetView domain ID.

System actionThe system waits for an operator response.

Operator responseAn associated message will provide more details aboutthe problem. If necessary, contact your systemprogrammer.

System programmer responseFind and fix the problem with your customization ofsystem automation. If you cannot determine the causeof the problem, contact your IBM Support Center.

ClassesNone.

AOF603D ENTER AUTOMATION OPTIONS OR'R' (RE-DISPLAY) - DOMAIN domid

ExplanationThis message is issued at the beginning of systemautomation initialization. Its purpose is to give theoperator the opportunity to stop, pause, or overrideautomation. A reply is generated automatically for thismessage if there is no response from the operator.

The variable domid shows the NetView targetdomain ID.

System actionThe system waits two minutes for a reply. If there is noreply after two minutes, automation continues.

Operator responseNo reply is necessary if you want automation tocontinue with the default actions. Pressing Enter withno input causes automation to continue immediatelyusing the default actions. Other options that may bespecified are documented in the preceding multiline

message, AOF767I. See AOF767I help for details orreply 'R' to redisplay message AOF767I.


ClassesNone.

AOF604I AUTOMATION PAUSED BYOPERATOR REQUEST

ExplanationAutomation has been paused due to an operatorrequest.

System actionAutomation is paused.



Classes40, 43.

AOF605I AUTOMATION DISABLED BYOPERATOR REQUEST

ExplanationAutomation has been disabled as a result of theoperator replying STOP to message AOF603D ormessage AOF606D.

System actionAutomation is disabled.



Classes40, 43.



AOF606D AUTOMATION PAUSED, ENTEROPTIONS OR 'R' (RE-DISPLAY) –DOMAIN domid

ExplanationAutomation has been paused as a result of theoperator replying PAUSE to message AOF603D.

The variable domid shows the NetView targetdomain ID.

System actionAutomation pauses and waits for a reply to thismessage.

Operator responsePressing Enter with no input causes automation tocontinue immediately using default values. Otheroptions that may be specified are documented in thepreceding multiline message, AOF767I. See AOF767Ihelp for details or reply 'R' to redisplay messageAOF767I.


Classes40, 43.

AOF607I AN action OF THE AUTOMATIONENVIRONMENT IS IN PROGRESS

ExplanationThe automation is either initializing or reloading itsautomation environment.

• The variable action shows which action is beingperformed in the automation environment. It can beone of the following:BUILD

The automation is either initializing, reloading, orrestoring its automation environment

REFRESHThe automation is refreshing its automationenvironment

System actionIf the action is BUILD, the automation is unavailableuntil the environment is established.

If the action is REFRESH, processing continues.



Classes40.

AOF608E REXX Function PackageINGRXFPG not installed

ExplanationThe SA z/OS required REXX function INGRXFPG is notinstalled. However, the function package is mandatoryfor running SA z/OS.



System programmer responseInstall the required REXX function package. See IBM ZSystem Automation Planning and Installation forfurther guidance.

ClassesNone.

AOF609I INVALID REPLY: reason

ExplanationMay be one of the following:

• An operator command such as INGREQ or INGMOVEhas issued a WTOR but the response to the WTOR iswrong

• The reply you gave in response to AOF603D orAOF606D WTOR is incorrect

The variable reason gives a brief explanation ofwhat went wrong.

System actionDepending on the explanation, may be one of thefollowing:



• The command re-issues the WTOR asking theoperator for the correct answer.

• Automation is paused (if it was not already paused),the AOF767I message is reissued, and an AOF606DWTOR is issued so you can enter a correct response.

Operator responseReply to the new WTOR.

Classes40 44 46.

AOF610I SHUTDOWN REJECTED -subsystem_name HAS NO SHUTshut_type DEFINED

ExplanationThe shutdown type specified for this shutdownrequest has not been defined in the automationcontrol file for the indicated subsystem.

The variable subsystem_name indicates thesubsystem in question.The variable shut_type shows the type of shutdown,NORM, IMMED, or FORCE.

System actionNone.

Operator responseEither shut down the subsystem manually, or reissuethe shutdown request with a higher priority shutdowntype.

System programmer responseInclude the shutdown type specification in theautomation control file definition.

ClassesNone.

AOF611I SHUTDOWN REJECTED -subsystem_name SHUT shut_typeHAS NO COMMAND/REPLY

ExplanationThe shutdown type specified for this shutdownrequest has no command or reply defined in theautomation control file for the indicated subsystem.

The variable subsystem_name indicates thesubsystem in question.The variable shut_type shows the type of shutdown,NORM, IMMED, or FORCE.

System actionNone.

Operator responseEither shut down the subsystem manually, or reissuethe shutdown request with a higher priority shutdowntype.

System programmer responseInclude the shutdown type specification in theautomation control file definition.

ClassesNone.

AOF613D SPECIFY NEW RUNMODE.RUNMODE runmode NO LONGEREXISTS - DOMAIN domid

ExplanationThe message is issued at the beginning of systemautomation initialization. A runmode is currently setwhich does not exist in the policy.

The variable runmode shows the name of thecurrent runmode.The variable domid shows the NetView targetdomain id.

System actionThe system waits for a reply.

Operator responseSpecify a valid runmode or *ALL forRUNMODE=keyword. RUNMODE=? lists all possiblerunmodes. Although it is not recommended, you cankeep the current runmode followed by an exclamationmark(!).


ClassesNone.



AOF614I TIMER timerid IS DEFINED BUT ISMORE THAN 2 YEARS FROM NOW

ExplanationThe requested timer is defined successfully but the YYportion of the requested date is more than 2 years pastthe current year.

The variable timerid shows the ID of the timer beingdefined.

System actionThe requested timer is defined.

Operator responseCheck that you have specified the year that youintended. If necessary, update the timer definitionusing the SETTIMER command.


ClassesNone.

AOF615I UNABLE TO START TASK task

ExplanationThe task could not be started.

System actionAutomation is paused. The message is followed byAOF604I and AOF767I.

Operator responseReply to AOF767I. If the problem persists, contactyour system programmer.

System programmer responseCheck your DSIDMN file, or NetView style sheetDSIPARM member for the task in question.

Also study the SYSLOG for associated IEC* messagesto indicate an associated dataset issue.

Classes40, 43.

AOF617I SA Z/OS INITIALIZATIONSTARTED

ExplanationInitialization of SA z/OS has started.




ClassesNone.

AOF618I NO VALID ACF FOUND FORsysname - reason

ExplanationThe automation configuration file found could not beloaded by the product.

• The variable sysname shows the system name thatan automation control file could not be found for.

• The variable reason shows the reason for the failure.Possible reasons are:NO DEFAULT ACF FOUND IN AOFACFMP

The ACF mapping member does not contain aconfiguration for this system.

ACF MEMBER NOT AVAILABLEThe ACF member could not be accessed.

ACF TOKEN MISMATCHThe ACF does not have the same token as theautomation manager configuration file.

ACF CONTENT NOT VALIDThe ACF was not built using the correct versionof the customization dialogs or was corrupted.

ALLOCATION OF dataset FAILEDSystem automation was not able to dynamicallyallocate the ACF data set.

AUTOMATION TABLE member IN ERRORThe test of a NetView automation table failed.Browse the netlog for further details and see theINGERRLS listing in the DSILIST data set.

MESSAGE REVISION TABLE IN ERRORThe test of a NetView message revision tablefailed. Browse the netlog for further details andsee the INGERRLS listing in the DSILIST data set.



ACF CHECK FAILED WITH RC=rcAn error occurred while checking the ACF.Contact your IBM Support Center.

CURRENT RUNMODE runmode NO LONGER EXISTSThe ACF does not contain the runmode which iscurrently set.

ACF IS NOT VALID FOR THIS PRODUCTThe ACF contains more systems than can besupported by this product.

AUTOMATION TABLE member NOT VALID FORTHIS PRODUCT

The NetView automation table contains userspecific changes which cannot be supported bythis product.

MESSAGE REVISION TABLE NOT VALID FOR THISPRODUCT

The NetView message revision table containsuser specific changes which cannot be supportedby this product.

AUTOMATION TABLE member NOT FOUNDThe NetView automation table could not befound in DSIPARM.

System actionACF load/refresh processing terminates.


System programmer responseFix the problem by providing a valid configuration forthe automation agent:

1. Copy the configuration that the automationmanager was loaded from back into yourconfiguration data set and instruct the automationagent to Retry its cold start. This is only possible ifyou still have a copy of that data.

2. Instruct the automation manager to load theconfiguration currently on disk with FAM,REFRESH,*.

3. Instruct the automation manager and theautomation agent to load their configuration from adifferent configuration file with FAM,REFRESH,file_name. Like option 1, this onlyworks if you have an alternative file available.

For more information on how to manage control filedata sets, see this technote.

Classes40, 43.

AOF620I clist time LENGTH ERROR, FORMATSHOULD BE HH.MM, H.MM, MM, M,HH.M, HH., H., H.M or HH.MM.SS

ExplanationA timer value specified is not valid.

The variable clist shows which CLIST issues thismessage.The variable time shows the timer interval entered.

System actionNone.

Operator responseEnter the command again, specifying a valid value.


ClassesNone.

AOF621I clist INVALID TIME SPECIFIEDtime_value/maximum_value

ExplanationA timer value specified is not valid.

The variable clist shows which CLIST issues thismessage.The variable time_value shows the timer intervalvalue.The variable maximum_value shows the maximumvalue for either hours (24), minutes (59) or seconds(59).

System actionNone.

Operator responseEnter the command again, specifying a valid value.


ClassesNone.



https://www-01.ibm.com/support/docview.wss?uid=ibm10879939

AOF622A NEW STATUS OF auto_status NOTVALID WHEN THE type STATUS ISother_status

ExplanationThe automation status specified in the SETSTATEcommand is not valid for the current applicationmonitor routine status or ARM status of the resource.

The variable auto_status shows the automationstatus specified in the SETSTATE command.The variable type shows the type of resource statusthat is being compared with the automation status.The type value can be either MONITOR or ARM.The variable other_status shows the applicationmonitor or ARM status that the automation status isnot valid for.

System actionNone.

Operator responseCorrect the automation status and reissue theSETSTATE command, or investigate the status of theresource.


ClassesNone.

AOF624I NEW STATUS of auto_status NOTVALID FOR SUBSYSTEM OF TYPEtype

ExplanationThe automation status specified in the SETSTATEcommand is not valid for this type of subsystem.

The variable auto_status shows the automationstatus specified in the SETSTATE command.The variable type shows the type of the subsystem,for example, MVS.

System actionNone.

Operator responseCorrect the automation status and reissue theSETSTATE command.

AOF625I CONFIGURATION REFRESHSTAGED FOR THE FOLLOWINGREASON(S):

ExplanationThis message is the header line of a multiline message.A configuration refresh was delayed for the reasonslisted with messages AOF626I.

System actionThe configuration refresh is retried after 5 minutes.


ClassesNone.

AOF626I restype resname IS IN action

ExplanationThis message is part of a multiline message. Itprovides information about the reasons for aconfiguration 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 currentlyperformed for the resource.

System actionThe configuration refresh is delayed for this resource.


ClassesNone.

AOF632I REFRESHING OF SDF PANELSWILL NOT OCCUR

ExplanationThis message indicates that the SDFQNM commandwas not executed successfully during a reload orrecycle, due to mismatching sysnames.





System programmer responseEnsure the sysname matches the root system namedefined in AOFTREE.

AOF641E time : CLIST name FAILED. PPIRECEIVER ID id DOES NOT EXIST.MESSAGES WILL NOT BEFORWARDED TO TEC

ExplanationDuring the initialization of the TEC Notification service,it was detected that the PPI receiver ID of the GEMEvent Adapter is not available.

The variable time shows the time when thismessage was generated.The variable name shows the CLIST that issued thismessage.The variable id shows the ID of the PPI receiver ofthe GEM Event Adapter.

System actionEvents will not be forwarded to TEC.


System programmer responseCheck whether the GEM Event Adapter is up andrunning. If this is the case, check whether the PPIreceiver ID used by the GEM Event Adapter is thesame as the one that is expected by the TECNotification service.

Classes0, 40, 44.

AOF642I time : TIVOLI ENTERPRISECONSOLE NOTIFICATION SERVICEIS ENABLED

ExplanationThe T/EC Notification service is fully initialized and theE/AS Message Adapter that the TEC Notification sends

messages to for conversion to TEC Events is up andrunning.


System actionFrom now on system automation messages areforwarded to TEC via the E/AS Message Adapter.



Classes40.

AOF643I time : TIVOLI ENTERPRISECONSOLE NOTIFICATION SERVICEIS DISABLED

ExplanationThe TEC Notification service has stopped forwardingmessages to the E/AS Message Adapter.


System actionMessages are no longer forwarded to TEC.


System programmer responseThe PPI receiver ID of the E/AS Message Adapter wasno longer available to the TEC Notification Service.Ensure that the E/AS Message Adapter is up andrunning.

Classes40.

AOF644E time : CLIST name FAILED. FOCALPOINT VARIABLE varname NOTSET. EVENTS WILL NOT BEFORWARDED TO TEC



ExplanationThe system tried to retrieve the system automationprimary focal-point name from the NetView globalvariable varname. If the name cannot be retrieved,message AOF644E is issued. The E/AS MessageAdapter is expected to run on the system automationprimary focal-point system.

The variable time shows the time when thismessage was generated.The variable name shows the name of the CLISTthat issued the message.The variable varname shows the name of the focalpoint system.

System actionEvents will not be forwarded to TEC.


System programmer responseMake sure that you have customized the focal pointforwarding path correctly.

Classes: 0 40 44.

AOF646I time : TIVOLI ENTERPRISECONSOLE NOTIFICATION SERVICEIS INITIALIZED

ExplanationThe Tivoli Enterprise Console® Notification service isinitialized successfully. The TEC Notification service isready to forward messages to the E/AS MessageAdapter. As soon as the E/AS Message Adapter is upand running, the AOF642I message is issuedindicating that from now on messages will beforwarded to the E/AS Message Adapter.





Classes40.

AOF660I CURRENT FOCAL POINT ISdomain_ID_1 , WAS domain_ID_2 ,FOR domain_ID_3 SYSTEMsystem_name

ExplanationThe focal point has been established or changed.

The variable domain_ID_1 shows the domain ID ofthe current focal point.The variable domain_ID_2 shows the domain ID ofthe prior focal point.The variable domain_ID_3 shows the domain IDthat is using domain_ID_1 as its focal point.The variable system_name shows the name of thisdomain.

System actionCommunications to the focal point from domain_ID_3will now use domain_ID_1.



Classes40.

AOF661I DOMAIN domain_ID_1 ISCOMMUNICATING WITHdomain_ID_2 , VIA domain_ID_3 ,system_info, product version

ExplanationCommunication is established to domain_ID_2 fromdomain_ID_1 via domain_ID_3.

The variable domain_ID_1 shows the domain IDthat established communications.The variable domain_ID_2 shows the domain IDthat is now ready for communications.The variable domain_ID_3 shows the domain IDthat is first in the communication path todomain_ID_2. This is equal to domain_ID_2 if thecommunication 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 ondomain_ID_2 runs in a parallel sysplex.The variable product shows the automation productrunning in domain_ID_2.The variable version shows the version of thatproduct in the format VnRnMn.

System actionAny other domains that were waiting on the activationof this domain are notified. If this domain is defined asa focal point, focal point reassignment is considered. Ifdomain_ID_1 has domains that have not yetestablished communication, and if this domain hasbeen defined as a path to it, the other domain isqueried in domain_ID_2 for its status.



Classes40.

AOF662I DOMAIN domain_ID_1 HASSTOPPED COMMUNICATING WITHdomain_ID_2 system_name

ExplanationCommunication has been interrupted for the specifieddomain.

The variable domain_ID_1 shows the domain IDthat stopped communicating.The variable domain_ID_2 shows the domain IDthat cannot be reached.The variable system_name shows the name ofdomain_ID_2.

System actionNone.



Classes40.

AOF663I DOMAIN domain_ID STATUS ISstatus, REPORTED BYreporting_domain

ExplanationThe reporting domain has reported the status ofdomain ID and the status was not a known status.Known statuses are ACTIVE, INACTIVE, and INVALID.

The variable domain_ID shows the domain IDwhose status is being reported.The variable status shows the status value of thedomain ID.The variable reporting_domain shows the domainID of the domain reporting.

System actionNone.


System programmer responseThe status is not a known status; further action is notpossible. The origin of this status is reporting domain;it is either in error or it supports domain statuses thatthis product does not.

Classes: 1 40.

AOF664I NO FOCAL POINT AVAILABLE

ExplanationThere is no focal point system available at this time.

System actionNone.



Classes40.



AOF667I REQUEST TO DOMAINdomain_ID_1 WAS REJECTED ATdomain_ID_2, NO ROUTE DEFINED

ExplanationA request issued for domain_ID_1 was rejected bydomain_ID_2 because no route to domain_ID_1 isdefined.

The variable domain_ID_1 shows the domain IDthat the request was issued to.The variable domain_ID_2 shows the domain IDthat rejected the request.

System actionNone.


System programmer responseThe message can be used to analyze gateway activity.

Classes: 1.

AOF668I DOMAIN domain_ID REJECTEDREQUEST: request

ExplanationThe identified domain rejected the request shown.

The variable domain_ID shows the domain ID thatrejected the request shown.The variable request shows the request that wasrejected.

System actionNone.


System programmer responseEither the domain ID does not support the request orthe request is not valid.

Classes: 1.

AOF669I REQUEST LOOPED BACK TOdomain_ID_1, SENT ONdomain_ID_2, RECEIVED FROMdomain_ID_3, REQUEST: request

ExplanationA request that originated in this domain looped back tothis domain. The loop is stopped here and loggedthrough this message.

The variable domain_ID_1 shows the domain IDthat received its own request back.The variable domain_ID_2 shows the domain IDthat the request was probably sent out on. Thisdomain is the domain that is currently being usedto communicate to the target domain; this mayhave changed since this request was sent.The variable domain_ID_3 shows the domain IDthat the request was received from. That domainshould have been the next domain en route to thetarget domain.The variable request shows the looping request.The target domain is contained in this request.

System actionNone.


System programmer responseScrutinize the gateway definitions in the path towardsthe target domain, including the alternate routingdefinitions. Expect to find a path that leads back to thisdomain that would result in an endless loop that neverreaches the target domain.

Classes: 1.

AOF670I COMMAND (command_text) WASEXECUTED IN DOMAIN domain_IDBY OPERATOR operator_ID

ExplanationA command was issued by this operator in thisdomain.

The variable command_text shows the text of thecommand executed.The variable domain_ID shows the domain that thecommand was executed in.The variable operator_ID shows the ID of theoperator issuing the command.

System actionNone.





ClassesNone.

AOF671I COMMAND (command_text)FAILED EXECUTION IN DOMAINdomain_ID, RC=return_code

ExplanationAn INGSEND with RESP=ACK was issued by anoperator from this domain. This message is anacknowledgment that the command executed on thetarget domain, but failed.

The variable command_text shows the text of thecommand attempted.The variable domain_ID shows the domain that thecommand was attempted in.The variable return_code shows the value returnedfor the failing command.

System actionNone.

Operator responseThe return code is specific to the command. Preservethe information for follow up action.

System programmer responseCheck the command return codes for a match todetermine the cause of failure and possible resolution.

ClassesNone.

AOF672I COMMAND (command_text) WASEXECUTED IN DOMAIN domain_IDBY A crm COMMAND FROMOPERATOR operator_ID

ExplanationAn INGSEND with RESP=ACK was issued by anoperator from this domain. This message is anacknowledgment that the command executedsuccessfully on the target domain.

The variable command_text shows the text of thecommand executed.The variable domain_ID shows the target domainthat the command was executed in. If thecommand routing mechanism used was RMTCMD,the domain may be qualified by a network ID, or "*"indicating that the default network ID was used toroute the command.The variable crm shows the command routingmechanism used. Possible values are ROUTE orRMTCMD.The variable operator_ID shows the ID of theoperator who issued the INGSEND command.

System actionNone.



ClassesNone.

AOF700I CLIST name EXECUTING ON taskWITH PARMS > parmstr

ExplanationWhen debugging is active, this message is written tothe netlog each time a command list is processed.

The variable name is the name of the clist.The variable task is the name of the task that theclist ran on.The variable parmstr shows the parametersprocessed.

System actionNone.





ClassesNone.

AOF701A MESSAGE TABLE table WAS NOTLOADED - DETECTED ERRORS

ExplanationLoading of the message automation table failed. Errorswere detected while attempting to load table.Preceding messages describe the errors.

The variable table shows the name of the messageautomation table.

System actionNone.


System programmer responseFollow the response instructions given in thedescription of the preceding messages. Correct theerrors and reload the failing table via AUTOTBL or ACFATLOAD command.

Classes: 40 44 46.

AOF702I CLIST name COMPLETED ON taskWITH RETURN CODE rc

ExplanationWhen debugging is active, this message is written tothe 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 theclist ran on.The variable rc is the return code given by the clist.

System actionNone.



ClassesNone.

AOF705I user ISSUED COMMAND commandWITH parameters

ExplanationThe specified user issued the command with thespecified parameters. The message is only issued ifcommand logging is enabled.

The variable user is the NetView user ID.The variable command is the command that wasissued.The variable parameters lists the variousparameters for the command (either specified ordefaulted).

System actionNone.



ClassesNone.

AOF708I THE LINE NUMBER ENTERED ISINVALID

ExplanationWhen attempting to change the number of the line thatis displayed, an invalid line number was entered.

System actionNone.

Operator responseEnter a valid line number.


ClassesNone.



AOF709I THE COMMAND ENTERED ISINVALID

ExplanationThe command that was specified is not valid.

System actionNone.

Operator responseType a valid command.


ClassesNone.

AOF710A request INPUT AND THEN PRESSENTER

ExplanationInput displayed on an operator dialog needs updatingor validating before a command can be issued.

The variable request specifies the action required.

System actionNone.

Operator responsePerform the requested action.


ClassesNone.

AOF711I AUTOMATION OFF FOR subsys ,value EFFECTIVE WHENAUTOMATE SET ON

ExplanationAutomation has been set to OFF for a resource. Whenautomation is reset to ON, the requested update to theflag will become enabled.

The variable subsys shows the name of theresource.The variable value shows the flag that is to beupdated and the value the flag is to be updated to.

System actionNone.



ClassesNone.

AOF712I INVALID CHARACTER character INfield_type field

ExplanationA data field of an automation control file contains anincorrect character.

The variable character shows the incorrectcharacter.The variable field_type shows the type of the fieldthat contains the incorrect character. The field typecan be either ENTRY or TYPE.The variable field shows the field that contains theincorrect character.

System actionNone.

Operator responseSpecify valid entry/type fields with correct characters.Refer to IBM Z System Automation Defining AutomationPolicy for information about the correct syntax.


ClassesNone.

AOF713A CALL TO macro FAILED, RC rc



ExplanationA system automation program detected anunacceptable return code from a macro that it called.The meaning of the return code depends on the macrothat issued it. Common examples are: DSICDS,28 :attempt to set a REXX variable failed as not calledfrom REXX DSIDKS(FIND),4 : member not found orempty.

The variable macro shows the name of the macrothat returned the error.The variable rc shows the return code.

System actionThe routine that called the macro continuesprocessing if possible. If the routine cannot continue itwill terminate with a non-zero return code. Othermessages may be issued indicating that a problemoccurred.

Operator responseTake appropriate corrective action. The action neededwill depend upon the problem that caused the failure.For example the routine should be run from REXX ifnecessary. For empty or missing members eithercorrect the member name or create the necessarymember.

System programmer responseIf the fixes under operator responses do not workmake a note of the issuing routine, the macro and thereturn code and contact your IBM servicerepresentative for assistance.

ClassesNone.

AOF717I SPECIFIED MEMBER NAME IS TOOLONG

ExplanationA string passed to a routine as the name of a memberis more than 8 characters long.

System actionThe routine terminates with a non-zero return code.

Operator responseIf issuing the command directly, reissue it with thecorrect member name. If the command is issued froma CLIST refer the problem to your system programmer.

System programmer responseIf the command is issued from a CLIST, fix the CLIST.

ClassesNone.

AOF718A SYS-OPS UNABLE TO CONTINUE -OPERATOR ASSISTANCEESSENTIAL

ExplanationThe system automation program has encountered aproblem that it is unable to bypass. Such problems aregenerally related to corrupt message tables orautomation control files that are missing essentialinformation.

System actionSystem automation stops working. Some messageautomation may occur if there was an active NetViewautomation table when the problem was found.

Operator responseAn associated message will give more details of theproblem. If necessary, contact your systemprogrammer.

System programmer responseFind and fix the problem with your customization ofsystem automation. If you cannot identify the cause ofthe problem, contact your IBM Support Center.

Classes: 40, 46.

AOF719I clist : type COMMAND commandFAILED - reason

ExplanationA CLIST issued a command and did not get theexpected result.

The variable clist shows the name of the CLIST thatissued the command.The variable type shows the type of command thatwas issued, for example MVS, or JES.The variable command shows the command thatfailed.The variable reason gives a description of problemencountered.

System actionCLIST processing usually stops.




System programmer responseIf the reason is timeout, change the timeout values inthe automation control file. Fix any customizationerrors. If the problem persists, contact your IBMSupport Center.

Classes: 40 46.

AOF720E NO VALID DATA FOUND INAUTOMATION CONTROL FILE

ExplanationThe automation control file is empty or all data wasinvalid.

System actionNone.


System programmer responseCorrect the automation control file. Refer to IBM ZSystem Automation Defining Automation Policy forinformation on the syntax.

ClassesNone.

AOF721I EASY MESSAGE MANAGEMENTDISABLED BY AOFSMARTMATSETTING

ExplanationEasy Message Management is not active. The NetViewautomation table built by the customization dialogswill not be used.

System actionProcessing continues with the AT from DSIPARM.


System programmer responseTo enable Easy Message Management set the AAOAOFSMARTMAT to 2 using the NetView stylesheet.

Classes40 43.

AOF722E MEMBER member NOT FOUND INdataset - USING DEFAULT defmemFROM ddname

ExplanationEasy Message Management is enabled, but theNetView automation table built by the customizationdialogs could not be found.

The variable member is the name of the missing ATfragment.The variable dataset is the name of theconfiguration data set.The variable defmem is the name of the default ATfragment.The variable ddname is the name of the DDstatement within the NetView startproc that is usedto search for defmem.

System actionThe default AT delivered by SA z/OS is used.


System programmer responseDetermine why the dynamically built AT fragment isnot available.

Classes40 46.

AOF723I MEMBER member FROM datasetLOADED INTO STORAGE ASAUTOMATION TABLE FRAGMENTdefmem

ExplanationEasy Message Management is enabled and theNetView automation table built by the customizationdialogs replaces the default AT fragment deliveredwith SA z/OS.

The variable member is the name of the missing ATfragment.



The variable dataset is the name of theconfiguration data set.The variable defmem is the name of the default ATfragment.

System actionProcessing continues with the replaced AT fragment.



Classes40 43.

AOF724I MEMBER member FROM datasetLOADED INTO STORAGE ASMESSAGE REVISION TABLEdefmem

ExplanationEasy Message Management is enabled and theNetView message revision table (MRT) built by thecustomization dialogs is activated, replacing anypreviously active MRT.

The variable member is the name of the missingMRT fragment.The variable dataset is the name of theconfiguration data set.The variable defmem is the name of the activatedMRT.

System actionProcessing continues with the replaced MRT.



Classes40 43.

AOF726I FUNCTION SUCCESSFULLYCOMPLETED - WARNINGSWRITTEN TO NETWORK LOG

ExplanationThe function requested has been successfullyexecuted. During execution warning messages havebeen written to the network log.

System actionNone.

Operator responseRefer to the netlog for further information.


ClassesNone.

AOF727I request EXITS CANNOT BEENABLED, EXITS DO NOT EXIST -FLAG SET TO ON

ExplanationA request has been made to enable the exits for aresource automation flag. Because no exits have beencoded in the automation control file for this resourceflag, the flag has been set to ON.

The variable request shows the resource name andautomation flag.

System actionNone.



ClassesNone.

AOF728I subsystem type RECOVERYCOMMANDS EXHAUSTED, BACKTO PASS 1

ExplanationWhile attempting to recover a spool or buffer shortagesystem automation ran out of defined recovery



commands before recovery was complete. Systemautomation will re-execute the recovery commandsequence starting from the first pass.

This situation may occur if the earlier recoverycommands have disposed of excessive spool or bufferbut more has accumulated while the earlier passeswere running.

The variable subsystem shows the subsystemname.The variable type shows the type of shortageproblem being recovered. Possible values areSHORT and FULL.The variable resource shows the resource having ashortage problem.

System actionThe shortage recovery continues.

Operator responseYou need to have a look at your spool or buffer usage.System automation may need some assistance to keepit in control. Look for tasks generating spool orconsuming buffer that the recovery commands do notaffect.

System programmer responseReview your recovery commands. You may wish tomake them more aggressive or to add some more ofthem.

Classes: 40 45.

AOF729I subsystem SPOOL type RECOVERYSUSPENDED ON PASS pass :reason

ExplanationWhile attempting to recover a spool shortage systemautomation found a reason why it could not continuewith spool recovery. The most likely reason is that theRecover automation flag is or has been turned off.While the flag remains off spool usage will bemonitored, but no recovery commands will be issued.If the flag is reset, the recovery commands will bereissued from the pass indicated in the message.

The variable subsystem shows the subsystemname.The variable type shows the type of spool problembeing recovered. Possible values are SHORT andFULL.The variable pass shows the recovery pass that wasto be issued.

The variable reason shows the reason that systemautomation has not issued the recovery pass.

System actionThe spool recovery continues. No recovery passes areissued.

Operator responseReset the Recover automation flag if that is theproblem and you wish the suspended recoverycommands to be reissued.

System programmer responseInvestigate the cause of the blockage. Takeappropriate action to stop it from occurring again.

Classes: 40 45.

AOF730I SPECIFIED OPERAND operandINVALID FOR request

ExplanationAn operand specified on a command conflicts with therequest.

The variable operand shows the operand that isinvalid.The variable request shows the parameter that theoperand conflicts with and why.

System actionNone.

Operator responseReenter the request with the correct operand.


Classes: None.

AOF732I SHUTDOWN PROCESSINGRESUMED

ExplanationShutdown processing has been resumed. Shutdownattributes have not been updated.

The variable shutdown_id shows the ID of theshutdown that has been resumed.



System actionNone.



ClassesNone.

AOF735I UNABLE TO PROCESS SHUTDOWN- AUTOMATION IS SET OFF FORsubsystem

ExplanationShutdown processing was unable to shut down thesubsystem because the Terminate flag was set to OFF.Because the option for overriding the Terminate flagwas set to NO, the shutdown could not be performed.

The variable subsystem shows the name of theaffected subsystem.

System actionNone.

Operator responseIf you want to shut down the subsystem regardless ofits flag setting, reissue the INGREQ REQ=STOPrequest specifying OVERRIDE=FLG, or ALL if you alsowant to override other conditions.


ClassesNone.

AOF742D ENTER >GO< TO PROCEED OR>CANCEL< TO CANCEL REQUESTOR >R< TO REDISPLAY,USER=userid

ExplanationAn operator command such as INGREQ or INGMOVEhas been entered with VERIFY=WTOR specified.AOF742D is preceded by AOF778I that lists theresources that will be affected by the request.

The variable userid shows the operator ID wherethe request originated. This can be used to tieAOF742D to the associated AOF778I.

System actionThe operator is prompted by a WTOR.

Operator responseVerify the list of affected resources and reply witheither GO or CANCEL to the WTOR or reply R toredisplay message AOF778I.


ClassesNone.

AOF743I SHUTDOWN WILL NOT(RE)PROCESS SUBSYSTEMsubsystem AS IT IS status

ExplanationThe shutdown considered shutting the namedsubsystem down, but then did not because it was notin a suitable state.

The variable subsystem shows the name of thesubsystem being processed.The variable status shows the current state of thesubsystem.

System actionThe thread of the shutdown process that found theproblem will cease. The message does not necessarilyindicate a problem.

Operator responseIf the subsystem is in an error state you should recoverit manually.

System programmer responseThis message normally indicates that the shutdownprocess has already started to shut a subsystem down.This message may also be issued if the subsystem is ina STOPPING or DOWN status.

Classes40, 43.



AOF745E SHUTDOWN FOR SUBSYSTEMsubsystem : SUBSYSTEM NOTFOUND AND NO FINALTERMINATION MESSAGERECEIVED. SHUTDOWNSUSPENDED FOR time MINUTES

ExplanationThe shutdown monitoring has detected that thenamed subsystem has cleared address space, but thatits final termination message was not received withinat least 60 seconds of this happening.

The variable subsystem shows the name of thesubsystem being processed.The variable time shows the number of minutes thesystem will wait.

System actionThe system waits up to time minutes for thesubsystem's final termination message to arrive. If itdoes not, the shutdown will assume that thesubsystem has terminated and issue the appropriatefinal message for the subsystem.

Operator responseCheck that the subsystem has properly terminated. Ifit has not, you must help it manually as no moreshutdown commands will be issued for it. If it hasterminated normally, refer the problem to your systemprogrammer.

System programmer responseDetermine the reason that the final terminationmessage was missed. You may need to correct yourNetView automation table, or change it to use a bettermessage. MPF is another place where the messagecould have been lost.

Classes: 40 46.

AOF746A SHUTDOWN FOR SUBSYSTEMsubsystem : NORMAL SHUTDOWNPROCESSING HAS BEENSUSPENDED AS THE SUBSYSTEMIS status

ExplanationA subsystem being shutdown by a normal shutdown(SHUTNORM) has entered either an ABENDING orBREAKING status. No further SHUTNORM commandswill be issued.

The variable subsystem shows the name of thesubsystem being processed.The variable status shows the current status of thesubsystem.

System actionThe shutdown is suspended until the subsystem stopsor the shutdown is modified to use a more aggressiveset of shutdown commands. Both immediate and forceshutdown commands can be issued against suchsubsystems.

Operator responseDetermine the state of the subsystem. If it willeventually terminate you don't have to do anything. Ifmore commands are needed to effect a shutdown,either issue them manually or modify the type of theshutdown for that subsystem. Refer the problem toyour system programmer.

System programmer responseExamine the shutdown commands and the NetViewautomation table entries. If the normal shutdowncommands cause the subsystem to abend thissituation will recur.

Classes: 40 46.

AOF747A SHUTDOWN FOR SUBSYSTEMsubsystem IS STUCK. THESUBSYSTEM IS NOT SHUT DOWNBUT THERE ARE NO MORE typePASSES TO ISSUE

ExplanationSA z/OS has issued all defined shutdown passes for asubsystem, but the subsystem has not stopped.Operator assistance is required to continue with theshutdown.

The variable subsystem shows the name of thesubsystem being processed.The variable type shows the type of shutdowncommands being issued.

System actionThe shutdown of the subsystem is unable to proceed.It will hang until either the subsystem is stopped by anexternal agency or the shutdown is cleared.

Operator responseDetermine the status of the subsystem. If it is in theprocess of stopping, wait. If the subsystem is not



stopping, either upgrade the type of shutdowncommands being issued or shut it down manually.Inform your system programmer of the problem.

System programmer responseExamine your shutdown commands. If they are notsufficient to stop the subsystem, upgrade them. If thesubsystem is consistently taking too long to stop eitherincrease the subsystem’s delay or add some dummypasses to the end of the shutdown commands.

Classes: 40 46.

AOF748E SHUTDOWN FOR SUBSYSTEMsubsystem : SUBSYSTEM NOTFOUND AND NO FINALTERMINATION MESSAGERECEIVED. AUTOMATEDSHUTDOWN RESUMES

ExplanationThe system is resuming a shutdown that wassuspended when a subsystem cleared address spacewithout issuing a final termination message. No suchmessage has since been received, and it seemsunlikely that one will be.

The variable subsystem shows the name of thesubsystem being processed.

System actionSystem automation issues the final terminationmessage on behalf of the subsystem. The shutdownproceeds as if the message had arrived normally.

Operator responseInform your system programmer about the failure ofthe system to recognize the subsystem’s finaltermination message.

System programmer responseExamine your shutdown commands and NetViewautomation table entries. It is likely that they are nottrapping the subsystem’s final termination message,and this is causing unnecessary delays in yourshutdown processing.

Classes: 40 46.

AOF749I SHUTDOWN COMPLETE FORresource. (RESTART=restart,TYPE=shuttype)

ExplanationThe indicated shutdown has completed successfully.

The variable resource shows the name of theresource that has been shut down.The variable restart indicates what happens to theresource after the shutdown is complete. The valueof restart can be YES.The variable shuttype indicates the shutdown type.

System actionNone.



Classes40, 43.

AOF750I SHUTDOWN FOR SUBSYSTEMsubsystem MAY HAVE FAILED TOISSUE SOME shuttype itemtype ONPASS pass

ExplanationWhile issuing the shutdown commands for the namedpass return codes from AOFCMD or AOFRPY indicatedthat they may have failed to issue some of theircommands or replies.

The variable subsystem shows the name of thesubsystem being processed.The variable shuttype shows the type of shutdownpasses being issued.The variable itemtype shows the COMMANDS orREPLIES indicating what failed.The variable pass shows the pass of shutdownprocessing that it occurred on.

System actionThe shutdown continues. If it did fail to issue thecommands the shutdown may become stuck and issuean AOF747E message when it runs out of passes.

Operator responseCheck the netlog and the system log to see whetherthe proper shutdown commands were issued. If they



were not, you may need to shut the subsystem downmanually.

System programmer responseCheck that the shutdown commands are all valid whenissued from a NetView console. If they are not, fixthem. If you still get regular occurrences of thismessage try altering your shut delay times orcontacting your IBM Support Center, or both.

Classes: 40 46.

AOF751I CLEAN UP FOR SHUTDOWN DIDNOT CHANGE THE STATUS OFSUBSYSTEM subsystem TORESTART BECAUSE reason

ExplanationWhile a shutdown with RESTART=YES was beingcleaned up, the status of the specified subsystem wasnot changed to RESTART for the reason given.

The variable subsystem shows the name of thesubsystem being processed.The variable reason shows the reason that thechange was not made.

System actionThe clean up continues. The named subsystem and itschildren will not be restarted when it is complete.

Operator responseTo restart the subsystem, use the SETSTATEcommand.

System programmer responseIf the message was issued because the subsystemabended or broke, you should check it out and, if theprocess was a normal part of its shutdown, changeyour automation so that it no longer enters an errorstate.

Classes: 40 43.

AOF752E SHUTDOWN FOR SUBSYSTEMsubsys SUSPENDED. THETERMINATE FLAG IS CURRENTLYTURNED OFF

ExplanationWhen the shutdown attempted to shut the specifiedsubsystem down it checked its Terminate flag andfound it to be turned off. No passes will be processedfor the subsystem until the flag is turned on.

The variable subsys shows the name of thesubsystem being processed.

System actionThe shutdown is suspended. The shutdown CLISTs willbe redriven every shut delay to recheck the Terminateflag. As soon as they find it turned on the next pass ofshutdown commands will be issued.

Operator responseIf you do nothing the shutdown remains suspendeduntil the flag is turned on (possibly at the end of aNOAUTO or a TIMEOUT period). You could force theflag to change with the INGAUTO command.

System programmer responseCheck whether the reason why the flag was turned offwas valid. Ensure that the operators have instructionsto deal with this situation should it arise again.

Classes: 40 46.

AOF755I SHUTDOWN FOR SUBSYSTEMsubsystem : type PASS pass :AOFSHUTMOD SET TO value

ExplanationThe shutdown processing found that theAOFSHUTMOD variable had been set to a non-nullvalue by the subsystem’s shutdown commands.

The variable subsystem shows the name of thesubsystem being processed.The variable type shows the type of shutdown beingprocessed.The variable pass shows the pass of the shutdownbeing processed.The variable value shows the value of the TGLOBAL.

System actionThe shutdown process continues. If the value isrecognized by the shutdown process it will be used toalter the shutdown’s flow. If it is not recognized it willbe ignored. Recognized keywords are NOW, DELAY,ABORT and NEXTPASS. Note that both DELAY andNEXTPASS require their parameters to be correct.

Operator responseNotify your system programmer if the value is invalid.Note that if the parameter on a DELAY statement wasinvalid the automated shutdown will have stopped andyou should shut the affected subsystem downmanually.



System programmer responseIf the value is invalid, set the value in theAOFSHUTMOD variable correctly.

Classes40, 43.

AOF757I UNABLE TO PROCESS action FORresource - reason

ExplanationYou invoked INGREQ for a resource.

The variable action shows the action that cannot beperformed, for example, STARTUP.The variable resource shows the name of theaffected resource.The variable reason shows an explanation why theaction could not be performed.

System actionINGREQ stops processing.

Operator responseChange the parameters in the INGREQ call. Ifnecessary, contact your system programmer.

System programmer responseEnsure that the resource can be managed by systemautomation (start and stop commands defined,automation flags turned on, etc.).

ClassesNone.

AOF759A AUTOMATED STARTUP FORSUBSYSTEM subsystem MAY HAVEFAILED : RC rc FROM "ACFCMDMSGTYPE=STARTUP,ENTRY=subsystem"

ExplanationSystem automation tried to start a subsystem. TheACFCMD call failed, giving the indicated return code.

The variable subsystem shows the name of thesubsystem being processed.The variable rc shows the return code from theACFCMD call.

System actionThe startup will probably fail. The subsystem’s statuswill have been updated to INACTIVE with anappropriate message. If the subsystem does start, itwill be processed normally.

Operator responseYou must start the subsystem manually. Refer theproblem to your system programmer.

System programmer responseThe definition for the subsystem is either wrong orincomplete. Fix the definitions through thecustomization dialgos.

Classes: 40 46.

AOF760E condition CONDITION TRAPPED INclist LINE sourceline (CODEerror_num) DESCRIPTIONdescription

ExplanationA 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 thatthe error was trapped in.The variable sourceline shows the source linenumber where the condition occurred.The variable error_num shows N/A or SYNTAX errornumber or FAILURE return code.The variable description shows the NOVALUEvariable name, SYNTAX error description etc.

System actionThe CLIST ends with code -5, causing calling CLISTs toend.

Operator responseReport the problem to your system programmer,unless the condition is operator caused (for example,NetView CLOSE causing a HALT condition).

System programmer responseReport the problem to your IBM Support Center.

Classes: 40 46.

AOF761E entry NOT ACTIVE; description



ExplanationThe ACF loader did not find an expected entry to beACTIVE.

The variable entry shows the entry that wasexpected to be ACTIVE.The variable description shows details about theprobable consequences of the entry not beingACTIVE.



System programmer responseInvestigate why this entry is not ACTIVE and correctthe error. Then issue a cold start.

Classes: 40 46.

AOF762I entry NOT ACTIVE; description

ExplanationThe ACF loader did not find an expected entry to beACTIVE.

The variable entry shows the entry that wasexpected to be ACTIVE.The variable description shows details about theprobable consequences of the entry not beingACTIVE.

System actionNone.


System programmer responseExamine the description and determine whether or notyou wish this entry to be ACTIVE. If you do not requirethis entry to be ACTIVE, correct the reason why it isnot ACTIVE. Then issue a cold start.

Classes: 40 46.

AOF763I GATEWAY EXCMD TO OPERATORoperator_ID FAILED, RC=return_code , COMMAND( command_text )

ExplanationA Gateway operation cannot be completed becausethe EXCMD to transfer command has failed.

The variable command_text shows the commandthat failed.The variable operator_ID shows the ID of theoperator that the command was sent to.The variable return_code shows the return codefrom the failed command.

System actionThe CLIST continues. The command will not have beenactioned.

Operator responseReport the problem to your system programmer.

System programmer responseDetermine why the operator is inactive or the EXCMDfailed. If the command is AOFMSG, check whetheranother domain is sending messages to be issued by anon-existent operator.

Classes40, 43.

AOF764I field_name DOMAIN NAMEdomain_ID INVALID - reason

ExplanationWhile reading the control file or when processing thedomain operand of a command or panel a domain_IDhas been rejected.

The variable field_name shows the field where thedomain_ID is declaredThe variable domain_ID shows the domain_ID thathas been rejected. The variable reason shows theexplanation for the rejection.

System actionThe control file entry, or the command is ignored.

Operator responseIf a control file error, report the problem to yoursystem programmer. If a command error, correct thedomain name if in error.



System programmer responseCorrect the domain name in the control file entry, ordefine the domain in the DSIPARM data set, memberDSIDMN, or the NetView style sheet.

ClassesNone.

AOF765E NO entry DEFINED; description

ExplanationThe ACF loader did not find an expected entry in theautomation control file.

The variable entry shows the entry that wasexpected.The variable description shows details about theprobable consequences of not supplying the entry.



System programmer responseAdd the required data through the customizationdialogs.

Classes: 40 46.

AOF766I NO entry DEFINED; description

ExplanationThe loader did not find an expected entry in theautomation control file.

The variable entry shows the entry that wasexpectedThe variable description details the likelyconsequences of not supplying the entry.

Note that when the description indicates thatPLEXOPER is not defined and "PROCESSOR AND/ORIMAGECNTL DATA IGNORED", the ISQSTARTcommand will fail and ProcOps will be unavailableunless the Automated Function PLEXOPER is correctlydefined in the OPERATORS Policy Item.

System actionNone.


System programmer responseExamine the description and determine whether or notyou wish to include the entry.

Classes: 40 46.

AOF767I AUTOMATION OPTIONS:

ExplanationThis is the first line in a multiline message block thatappears at system automation initialization. The linesof the message block define the options that can bespecified for system automation initialization.

Note: Your response to this message block and itsfollowing WTORs is the chief means of determininghow your system is automated. You should understandclearly the details of the message block as explained inthe IBM Z System Automation User's Guide.

System actionAOF767I is followed by either an AOF603D or anAOF606D message. These are WTORs that can beresponded to. System automation repliesautomatically to an AOF603D after two minutes withdefault values unless this has been changed as a partof your site’s automation policy. System automationdoes not automatically reply to an AOF606D messageunless this has been changed as a part of your site’sautomation policy.

Operator responseVaries. Refer to IBM Z System Automation User's Guidefor details. Generally, reply to the AOF603D orAOF606D WTOR, or, for the AOF603D WTOR, let ittime out.

System programmer responseVaries. Refer to IBM Z System Automation User's Guidefor details.

ClassesNone.

AOF768I SUBSYSTEM subsys_nameREQUIRES entry : NOT FOUND INAUTOMATION CONTROL FILE



ExplanationAn entry that is required for a specific subsystem wasnot found in the automation control file. You may havea problem using this subsystem.

The variable subsys_name shows the name of thesubsystem in question.The variable entry shows the entry missing from theautomation control file.

System actionNone.


System programmer responseConsider adding the appropriate entry to theautomation control file.

Classes: 40 46.

AOF769I TIMER IDS STARTING WITH prefixARE RESERVED FOR SYS-OPSSYSTEM USE

ExplanationAn attempt was made to delete, change or add a timerwith a timer ID that starts with the character sequenceprefix.

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 andSA z/OS user timers. The operator interface preventsthese timers from being altered. The control fileinitialization will not set a timer that starts with 'AOF','ING' or 'ITMR' because it might override a SA z/OSsystem timer. Note timers with a prefix of 'ITMR'cannot be deleted.

System actionThe timer request was not processed.

Operator responseChange the timer ID to have another prefix. If you wantto delete a SA z/OS system timer, use the NetViewPURGE TIMER command. Do not purge any SA z/OSsystem timer unless you are certain of theconsequences.


Classes40, 43.

AOF770I THIS FUNCTION IS NOTAVAILABLE IN LINEMODE

ExplanationAn attempt was made to execute a CLIST as alinemode command when the CLIST does not supportthe linemode facility.

System actionNone.

Operator responseIssue command on an OST task to see commandoutput.


ClassesNone.

AOF771I REQUEST command REJECTED,action IN PROGRESS

ExplanationThe issued request cannot be processed at this timebecause a startup or shutdown is still in progress.

The variable command shows the request thatfailed.The variable action shows either STARTUP orSHUTDOWN.

System actionRequest is canceled.

Operator responseWait for startup or shutdown to complete or clearshutdown before reissuing request.




ClassesNone.

AOF772I PARSING ERROR PROCESSINGinput - error

ExplanationWhile processing the indicated item of input theparsing routine found an error.

The variable input shows the input that was beingparsed when the error was detected.The variable error shows the error that occurred.

System actionThe command stops processing.

Operator responseCorrect the parameter strings and rerun the command.

System programmer responseIf the error occurred from within a CLIST you must editthe CLIST to fix the problem.

ClassesNone.

AOF773I YOUR INSTALLATIONAUTOMATION POLICY DISALLOWSAN ACF RELOAD

ExplanationA reload of the automation control file has beenrequested but your automation flags indicate that areload is not allowed.

System actionThe reload process is abandoned.



Classes40, 43.

AOF774A YOUR INSTALLATIONAUTOMATION POLICY REQUIRESCONFIRMATION OF AN ACFRELOAD - ENTER “GO” TOCONTINUE OR “CANCEL” IF YOUDO NOT WISH TO PROCEED

ExplanationA reload of the automation control file has beenrequested but your installation automation policyrequires confirmation from the operator.

System actionWaits for operator response.

Operator responseEnter "GO" or "CANCEL".


ClassesNone.

AOF775I OPERATOR ENTERED response -action

ExplanationThis message confirms a response entered by anoperator.

The variable response shows the operatorresponse.The variable action shows the action taken by thesystem.

System actionAs described in action.



Classes40, 43.



AOF776I CONNECTION FROM DOMAINdomain_id_1 sdfroot_nameREJECTED AT DOMAINdomain_id_2 - reason

ExplanationAn attempt to establish a cross-domain gateway hasfailed.

The variable domain_id_1 shows the domainattempting to connect.The variable sdfroot_name shows the systemattempting to connect.The variable domain_id_2 shows the domainrejecting the connection.The variable reason shows the reason for rejectingthe connection.

System actionThe connection will be tried again at gateway monitortime.


System programmer responseThe gateway definitions in the automation control fileon either or both domains need correction to ensurecompatibility.

Classes40, 43.

AOF778I VERIFY AFFECTED RESOURCESFOR REQUEST "request",USER=userid

ExplanationAn operator command such as INGREQ or INGMOVEhas been entered with VERIFY=WTOR specified. Thismultiline WTO lists all the resources that will beaffected by the request.

The variable request shows the type of requestentered.The variable userid shows the operator IDoriginating the request. This can be used to tieAOF778I to the associated AOF742D.

System actionWTOR message AOF742D will be issued afterAOF778I.

Operator responseVerify the list of affected resources before replying tomessage AOF742D.


ClassesNone.

AOF779I VALID RUNMODES ARE:

ExplanationThis is the first line in a multiline message block thatappears when RUNMODE=? was entered as a responseto AOF603D. The lines of the message block show allvalid runmodes and their runtokens for the currentsystem.

System actionAOF767I and AOF603D are re-displayed.



ClassesNone.

AOF780E INTERNAL ERROR AT LOCATIONloc. UNABLE TO CONTINUE

ExplanationAn internal error occurred at the specified location inthe program code.



System programmer responseContact IBM Support Center.



ClassesNone.

AOF781I SERVICE REQUEST req FAILED ATLOCATION loc WITH RC= rc

ExplanationA service routine ended with a non-zero return code.

The variable req identifies the service request thatfailed.The variable loc identifies the location in the codewhere the failure occurred.The variable rc is the return code from the serviceroutine.



System programmer responsePerform problem determination and correct theproblem.

ClassesNone.

AOF782I AUTOMATION CONTROL FILEPROCESSING COMPLETED

ExplanationThe automation control file was processed andcompleted with no errors.




ClassesNone.

AOF783A AUTOMATION CONTROL FILEPROCESSING HAS FAILED

ExplanationThe processing of the automation control file resultedin a fatal error. No control information is processed.



System programmer responseCorrect the problem identified by other messages.

ClassesNone.

AOF784I AUTOMATION CONFIGURATIONFILE MEMBER file IS EMPTY ORDOES NOT EXIST

ExplanationAn INCLUDE member was processed but did notcontain any records or the member does not exist.

The variable file shows the name of member thatcaused the error.


Operator responseThe most common reason for this failure is that theautomation configuration file is allocated withsecondary extents and a new extent was justallocated. Therefore, NetView cannot find the memberalthough it exists and has correct contents. To correctthe error, a recycle of NetView is required. Contactyour system programmer.

System programmer responseCorrect the allocation for the automation configurationfile and avoid allocating secondary extents. Consideralso the usage of PDSE.

Classes40, 43.



AOF785I INVALID INCLUDE NAME INMEMBER member name

ExplanationAn INCLUDE member name in member is invalid, blankor contains invalid characters. The member name isignored.

The variable member name shows the name ofmember that caused the error.



System programmer responseCorrect the member name.

Classes40, 43.

AOF786A NO DATA FOUND IN AUTOMATIONCONTROL FILE file

ExplanationWhen the automation control file was processed onlycomments, blank lines and INCLUDE statements werefound. There was no system automation controlinformation.



System programmer responseCorrect the automation control file.

ClassesNone.

AOF787A TERMINATING ERROR WHENPROCESSING CONTROL FILE file

ExplanationInput from automation control file file contained anerror that prevented any system automation controlinformation from being processed.


Operator responseCorrect the command or contact your systemprogrammer.

System programmer responseCorrect the automation control file or command erroras identified by other diagnostic messages.

ClassesNone.

AOF789I COMMAND LINE PARAMETERparm INVALID

ExplanationCommand line parameter parm is not valid for thecommand issued.


Operator responseReissue the command or contact your systemprogrammer.

System programmer responseCorrect the command.

ClassesNone.

AOF790I THRESHOLD INTERVALS MUST BE:CRITICAL < FREQUENT <INFREQUENT

ExplanationFor threshold checking to function correctly, the errorintervals (time interval divided by error count) must beorganized correctly. The error interval for the criticalthreshold should be a smaller interval than that for the



frequent threshold, which should be smaller than theinfrequent threshold.

System actionThe threshold values are not changed.

Operator responseIssue the INGTHRES command again and enter countand time data so that the intervals are correct.


ClassesNone.

AOF791I AUTOMATION CONTROL FILEPROCESSING COMPLETED WITHERRORS

ExplanationThe specified automation control file was processedand control data were obtained but some errors wereencountered during processing



System programmer responseCorrect the errors identified by other diagnosticmessages.

ClassesNone.

AOF797A YOUR INSTALLATION POLICY HASSTOPPED SYS-OPSINITIALIZATION BECAUSE OFERRORS

ExplanationDuring a load or reload of the automation control fileerrors were detected. Your installation has set theautomation global variable AOFACFINIT to stopinitialization.

System actionInitialization processing stops.


System programmer responseCorrect the errors to do with the automation controlfile and reload it.

Classes: 40 46.

AOF800I FOR IBM SERVICE USE ONLY:MODULE: module_name RC:return_code

ExplanationThis message is intended for your IBM Support Centerto use in debugging internal system automation errors.

The variable module_name shows the module thatissued the message.The variable return_code shows the return codefrom the module.

System actionNone.



Classes0.

AOF801E REMOTE PROCESSINGENCOUNTERED AN INTERNALERROR UNEXPECTED RESULTSMAY OCCUR AS PROCESSINGCONTINUES.

ExplanationProcessing will continue but the results will beunpredictable.

System actionNone.





Classes40.

AOF802I INTERNAL ERROR DETECTED INclist, ERROR DATA:

ExplanationAn internal error occurred in the specified CLIST.

The variable clist shows the name of the CLIST.




ClassesNone.

AOF803I data

ExplanationThis message is part of a multiline message thatbegins with message AOF802I.

The variable data contains error data specific to thefailed CLIST.

System actionNone.



ClassesNone.

AOF814I Macro aa type bb request wasunsuccessful, RC=cc, RSN=dd

ExplanationThe program called the indicated macro. The macroswas not able to satisfy the request and returned theindicated return code for use in problemdetermination.

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 themacro.

System action:None.


System programmer response:Check the return code to determine the cause of theproblem.

AOF815I AOF815I Data space servicerequest failed, RC=aa

ExplanationThe program failed to reserve a new control block inthe data space that holds status componentinformation. The reservation failed with the indicatedreturn code.

The variable aa shows the return code of therequest:36 The data space ran out of space.40 The data space could not be extended.

System action:None.


System programmer responseReturn code 36 indicates that the maximum sizedefined in the DSIPARM member AOFINIT is notsufficient for your environment. Increase the value ofthe parameter MAXTREEDSPSZ and restart the taskAOFTDDF.

Return code 40 indicates a problem in extending thecurrent size of the data space up to the maximum sizedefined in the DSIPARM member AOFINIT. Checkwhether the data space has reached the installation



limit. The command SDFQTR returns information forthe current allocation units.

AOF816I EXTENDED MCS CONSOLE consoleFOR TASK task HAS BEENOBTAINED

ExplanationThe automation obtained an extended MCS console forthe named task because the default extended MCSconsole is already in use.

The variable console shows the name of theextended MCS console obtained for the task.The variable task shows the name of the task.

System actionNone.

Operator responseIf an MVS command was issued before receiving thismessage, the command should be reissued.


ClassesNone.

AOF817I UNABLE TO OBTAIN ANEXTENDED MCS CONSOLE consoleFOR TASK task reason

ExplanationThe automation was unable to obtain an extendedMCS console for the named task.

The variable console shows the name of theextended MCS console obtained for the task.The variable task shows the name of the task.The variable reason explains why the commandAOCGETCN failed.

System actionNone.


System programmer responseIf the console is already in use, update the commonglobal variable AOFCNMASK to define a uniqueconsole name.

ClassesNone.

AOF818I RODM RETURN CODE return_code ,REASON CODE reason_code

ExplanationA call to RODM has resulted in an unexpected returncode.

The variable return_code shows the return code.The variable reason_code shows the reason code.

System actionNone.


System programmer responseExamine the return and reason codes in associationwith other messages displayed.

Classes40.

AOF821I DSIDKS FAILED FOR reasonPROCESSING, INTERNAL ERROR

ExplanationThe NetView DSIDKS macro has returned a non-zeroreturn code.

The variable reason shows the reason for thefailure. This is either CONNECT, READ, orDISCONNECT.

System actionThe request terminates.




System programmer responseRun the NetView trace. Retry the request.

ClassesNone.

AOF824I NEVER SHOULD OCCUR, INVALIDDATA, CONTACT IBM SERVICEWITH DIAGNOSTIC DUMP

ExplanationInvalid data has been detected.

System actionProduces a diagnostic dump.



ClassesNone.

AOF826I M dev,volser, RECEIVED ONmm/dd/yy AT hh:mm:ssCOMPLETED ON mm/dd/yy AThh:mm:ss

ExplanationThis message is created by tape mount monitoring. Itis generated by a delete operator message (DOM) foran outstanding tape mount. The NetView automationtable should be configured to trap this message andinitiate the deletion of the associated tape mount iconon the workstation.

The variable dev shows the device number that atape mount request for was satisfied or canceled.The variable volser shows the volume serial that atape mount request for was satisfied or canceled.The variables mm/dd/yy and hh:mm:ss show dateand time respectively.

System actionThe workstation tape mount icon for the nominateddevice and volume is deleted.



ClassesNone.

AOF830I A SPECIFIED LIST ITEM WAS NOTFOUND, AND WAS REMOVEDFROM THE LIST

ExplanationA search item that was specified was not found andhas been removed from the search list.

System actionEither re-specify search criteria or leave as is.



ClassesNone.

AOF831I THE WILDCARD CHARACTER '*'VOIDS ALL OTHER ITEMS IN THELIST

ExplanationThe "*" is a global wildcard and overrides all othersearch criteria (if any).

System actionNone.

Operator responseIf you do not want to override all other seacrch criteriarespecify search criteria.




ClassesNone.

AOF832I A DUPLICATE ITEM WASSPECIFIED IN THE LIST AND HASBEEN REMOVED

ExplanationThe search criteria had duplicate items or two itemswere specified and were reduced to a single item, forexample, JES and JES2 are reduced to JES.

System actionEither re-specify search criteria or leave as is.



ClassesNone.

AOF833I AN INCORRECT STATUS WASSPECIFIED AND HAS BEENREMOVED

ExplanationA status was specified that is not known to systemautomation.

System actionRespecify status search criteria.



ClassesNone.

AOF834I INCORRECT NESTING LEVELSPECIFIED, IT MUST BE ANUMBER OR AN '*'

ExplanationAn incorrect nesting level was specified. The nestinglevel should be re-specified as either a number (0-9)or an "*".

System actionRe-specify status search criteria.



ClassesNone.

AOF835I clist_name: ENTRYSPECIFICATION: subsystem_nameLENGTH EXCEEDS length, PLEASERE-ENTER

ExplanationAn entry name has more than the maximum number ofcharacters allowed. Reenter the entry name.

The variable clist_name shows the name of thecommand list that generated this message.The variable subsystem_name shows the offendingentry name.The variable length shows the maximumpermissible length of the entry name.

System actionNone.

Operator responseReenter entry specification.


ClassesNone.

AOF836I clist_name: TYPE SPECIFICATION:subsystem_name LENGTHEXCEEDS length, PLEASE RE-ENTER



ExplanationA type name has more than the maximum number ofcharacters allowed. Reenter the type name.

The variable clist_name shows the name of thecommand list that generated this message.The variable subsystem_name shows the offendingtype name.The variable length shows the maximumpermissible length of the type name.

System actionNone.

Operator responseReenter type specification.


ClassesNone.

AOF837I A COMMAND WAS ENTERED WITHA JES2 PREFIX character THAT ISNOT DEFINED IN THEAUTOMATION CONTROL FILE

ExplanationThe command that was entered began with acharacter that is defined as a command synonym forthe AOC/MVS JES2 command. However, it has notbeen defined in an automation control file entry forJES2. The variable charactershows the prefix.


Operator responseReenter the command with the correct prefix.

System programmer responseIf the character is not intended as a JES2 prefixremoved it from the command synonym member(usually AOFCMD). Else, define it in the customizationdialog - Application Definition panels for JES2.

ClassesNone.

AOF838A subsystem type RECOVERYCOMMANDS EXHAUSTED

ExplanationWhile attempting to perform JES3 recovery, systemautomation ran out of defined recovery commandsbefore recovery was complete. System automation willre-execute the recovery command sequence startingfrom the first pass.

The variable subsystem indicates the name of thesubsystem.

The variable type shows the type of JES3 recoverybeing performed. Possible values are:

SPOOLSHORT for SPOOLMDSCOUNTA for ALLOCATION QueueMDSCOUNTB for BREAKDOWN QueueMDSCOUNTE for ERROR QueueMDSCOUNTF for FETCH QueueMDSCOUNTQ for NUMBER OF JOBSMDSCOUNTR for RESTART QueueMDSCOUNTU for UNAVAILABLE QueueMDSCOUNTV for VERIFY QueueMDSCOUNTW for WAIT VOLUME QueueMDSCOUNTSS for SYSTEM SELECT QueueMDSCOUNTSV for SYSTEM VERIFY Queueor any user-defined type.

System actionJES3 recovery continues.

Operator responseLook at SPOOL or MDS usage. System automation mayneed some assistance to keep it in control.

System programmer responseReview your JES3 recovery commands.

Classes: 40 44

AOF839I CONTROL FILE SYNTAX ERRORTHRESHOLD REACHED. CONSOLEREPORTING OF SYNTAX ERRORSSUSPENDED - PROCCESSINGCONTINUES.

ExplanationSyntax errors that were detected when processing thisautomation control file have reached the reportingthreshold. Subsequently detected syntax errors in thisautomation control file will be recorded in the netlog,but will not be reported on the console.



System actionProcessing of the automation control file continues.

Operator responseCheck the netlog to see automation control file syntaxerror messages.


ClassesNone.

AOF840E ERROR EXTRACTING RODM DATAFOR THE type OBJECT. RODMRETURN CODE retcode. RODMREASON CODE reason.

ExplanationThe command cannot be executed because the RODMlook-up failed and vital information could not beretrieved.


The variable type is the RODM object type.The variable retcode is the RODM return code.The variable reason is the RODM reason code.


System programmer responseThe retcode and reason are the RODM return andreason codes, which are documented in theNetViewRODM Programming Guide.

ClassesNone.

AOF841E THE RODM NAME OR RODM USERID COULD NOT BE DETERMINED.

ExplanationThe command cannot be executed because the RODMname or user ID used to access RODM could not bedetermined.


Operator responseMake sure that system automation focal point hasinitialized. If the focal point is running a satellitesystem automation, make sure the satellite hasinitialized.


ClassesNone.

AOF845I COMMAND REJECTED commandCOMMAND IS TOO LONG

ExplanationThe command exceeds the maximum length ofcommands. The command cannot be executed.

The variable command shows the name of thecommand that could not be executed.

System actionNone.

Operator responseTry to simplify the command and make it shorter.


ClassesNone.

AOF850I ISSUED INGSENDRESP=resp,OPER=oper,TO=domain, CRM=crm,CORRWAIT=corr,CMD="command"

ExplanationThis is to confirm the complete INGSEND commandrouted to the target system. This message is logged tothe local and target netlog. This message is issued onlyby INGSEND when CRM=RMTCMD.

The variable onet.odom.oopr shows the originnetwork ID, domain ID and operator ID.



The variable resp shows what to do with theresponses, if any.The variable oper shows the target RMTCMDautotask ID.The variable domain shows the target domain ID.The variable crm shows the command routingmechanism used.The variable corr shows the value used on theNetView Pipe command Corrwait stage.The variable command shows the command to beexecuted.




ClassesNone.

AOF860I instruction FOR entry typeREJECTED - "reason"

ExplanationAn automation policy processing instruction could notbe completed, and was rejected for the reason given.

Note: ASSERT, MODIFY, and RETRACT are instructionsused by the system automation automation policyprocessing to add, change, or delete data in thecurrently active policy definitions. The systemautomation policy has converted your request into oneor more of these instructions.

The variable instruction shows the action beingattempted for the entry-type pair. It can be ASSERT,MODIFY, or RETRACT.The variable entry shows the entry field associatedwith the line of automation policy data beingprocessed.The variable type shows the type field associatedwith the line of automation policy data beingprocessed.The variable reason shows the reason why theaction on the entry-type pair was rejected.

System actionThe entry-type pair and associated data is ignored.

Operator responseFix the problem if you can, using the information givenin the message, or inform your system programmer.

System programmer responseFix the problem using the information given in themessage.

Classes: 40 46.

AOF867I WARNING: entry type - "warning"

ExplanationSystem automation has detected an inconsistency inthe data that it has been given.

The variable entry shows the entry field associatedwith the line of automation policy data beingprocessed.The variable type shows the type field associatedwith the line of automation policy data beingprocessed.The variable warning shows the potential problemthat has been found with the data.

System actionIf the error is an incorrect data value it will be ignored,and it will not be reflected in the runtime parameters.

Operator responseInform your system programmer.

System programmer responseResolve the data inconsistency.

Classes: 40 46.

AOF868I WARNING: THERE ARE NO JESSUBSYSTEMS DEFINED

ExplanationThe automation cannot work correctly without a JESsubsystem, and system automation did not define one.

System actionProcessing continues. Some automation functions maynot work properly.




System programmer responseDetermine whether JES was defined outside of systemautomation. If not, and you want your system to runwith JES, you must define it.

Classes: 40 46.

AOF869I nn ERRORS ENCOUNTEREDPROCESSING MEMBER member

ExplanationThis message indicates how many inconsistencieswere found by system automation during theprocessing of this automation control file.

The variable nn shows the number ofinconsistencies encountered during the checking ofmember.The variable member shows the name of theautomation control file member being processed.

System actionProcessing continues unless the advanced automationoption AOFACFINIT is set to 0.

Operator responseReview the NetView log for additional informationgiven in one or more of the following messages:AOF206I, AOF701A, AOF784I, AOF785I, AOF860I,AOF867I, AOF868I, AOF871I, and fix the problem ifyou can, or inform your system programmer.

System programmer responseReview the NetView log for additional informationgiven in one or more of the following messages:AOF206I, AOF701A, AOF784I, AOF785I, AOF860I,AOF867I, AOF868I, AOF871I and fix the problem.

Classes40.

AOF871I time: LESS THAN n type entry AREDEFINED - AUTOMATION WILLCONTINUE WITH DEGRADEDPERFORMANCE

ExplanationThere are not enough definitions available in theautomation control file for the entry type mentioned inthe message.


The variable type shows the type specified in theautomation control file.The variable entry shows the entry specified in theautomation control file.

System actionProcessing continues with degraded performance.


System programmer responseDefine the automation control file entries through thesystem automation customization dialogs.

ClassesNone.

AOF890I THE COMMAND WILL BE ROUTEDTO domain_ID USING THEDEFAULT OPERATOR IDoperator_ID

ExplanationThe command was issued in the form of a routecommand by operator operator_ID and executed indomain domain_ID.

The variable domain_ID shows the of the domainthat the command was executed in.The variable operator_ID shows the ID of theoperator who issued the route command.

System actionNone.



ClassesNone.

AOF892I dsn IS NOT A VSAM DATA SET ORDOES NOT HAVE THE EXPECTEDATTRIBUTES



ExplanationAn automation function could not completesuccessfully because the specified data set name doesnot represent a VSAM data set. Or, the VSAM data setdoes not have the expected attributes.

The variable dsn shows the name of the data set.


Operator responseRetry the request with a valid VSAM data set name.


Classes:None.

Module:INGRVX20

AOF893I ENTERPRISE MONITORING ISNOT ENABLED. reason

ExplanationEnterprise monitoring is not enabled.

The variable reason gives more detail about thecause of the error.

System actionNone.

Operator responseIf you do not want to use enterprise monitoring thenno action is required. Otherwise, contact your systemprogrammer.

System programmer responseUse the reason text to help determining the problem.

ClassesNone.

AOF894I DUPLICATE NAME ON SAMEHIERARCHY LEVEL FOUND INMEMBER member: name

ExplanationSDF detected a node name that is defined more thanonce on the same hierarchy level in a tree. SDFsupports identical node names on the lowest hierarchylevel only.

The variable member shows the name of theDSIPARM member that contains the duplicatename.The variable name shows the name that occursmore than once.

System action:The node name is ignored. This includes all sub-nodes.


System programmer response:Correct the definition. Restart SDF when the messageswas produced during SDF initialization. Otherwise, re-issue the SDF command that produced the message.

Classes:None.

AOF895I DUPLICATE NAME IN TREEHIERARCHY FOUND IN MEMBERmember: name

ExplanationSDF detected identical node names on differenthierarchy levels of a tree. SDF supports identical nodenames on the lowest hierarchy level only.

The variable member shows the name of theDSIPARM member that contains the duplicatename.The variable name shows the name that occursmore than once.



System programmer response:Correct the definition. Restart SDF when the messagewas produced during SDF initialization. Otherwise, re-issue the SDF command that produced the message.

Classes:None.

AOF896I NO SUBSTITUTION VALUESFOUND FOR var.

ExplanationSDF found a variable in a tree definition but nocommon global variables of type;

AOF_AAO_SDFCvar.0 n



AOF_AAO_SDFCvar.n xxx [xxx...]

that define the substitution values.

The variable var shows the name of the variable.




Classes:None.

AOF897I INVALID LEVEL OF NON-UNIQUECOMPONENT IN MEMBER member:name

ExplanationSDF detected identical node names on the first andonly sub-level of a tree. This is not supported becausethe root name of a tree must always be unique. SinceSDF traverses the tree from top to bottom and left toright it would never find the second identical nodename.

The variable member shows the name of theDSIPARM member that contains the node name inerror.The variable name shows the node name in error.

System action:The node name is ignored.



Classes:None.

AOF898I SYSTEM sysname REJECTEDCOMMAND "cmd".

ExplanationAn MVS command was sent using MVS ROUTEcommand to one or all systems in the sysplex. Theindicated system rejected the command for securityreasons. MVS commands are essential for mostsysplex automation functions, since SA z/OS may runin an SAplex which can be smaller than a sysplex.

The variable sysname shows the name of thesystem.The variable cmd shows the name of the system.

System action:All sysplex automation functions using MVS ROUTEcommand have been disabled, in particular thefollowing commands; INGCF, INGCFL, INGPLEX (CDS,CONSOLE, SDUMP, SLIP, SYSTEM) and the followingrecovery functions: local page dataset, log, long-running enqueue.


System programmer response:If one of the commands or recovery functions above isrequired for your automation ensure that all systems inthe sysplex accept MVS commands, especially theROUTE command.

ClassesNone.

AOF899I SYSPLEX AUTOMATION FUNCTIONclist DISABLED.

ExplanationSystem Automation detected that one or moresystems rejected the MVS ROUTE command. For thisreason, all sysplex automation functions have beendisabled.

The variable clist shows the name of clist that hasbeen disabled.

System action:The function is terminated immediately.


System programmer response:Search the netlog for message AOF898I to determinewhich system rejected the ROUTE command. If theindicated function is required for your automationensure that all systems in the sysplex accept the MVSROUTE command.

ClassesNone.

AOF900I AT LEAST ONE STRUCTURE ISSTILL ALLOCATED IN THE CFcfname



ExplanationThe process was started disconnecting the couplingfacility cfname from its connected systems. However,at least one structure that is still allocated wasdetected by the DRAIN function. Or, one allocatedstructure that has a connection to an application wasdetected by the FORCE function.


Operator responseCheck the allocated structures of the coupling facility.Rebuild the structures to another coupling facility ifpossible before issuing the command again.


Classes: 40, 43.

Modules: INGRX912, INGRX913.

AOF901I PATH chpid FROM SYSTEM TO CFcf_name COULD NOT BE SET TOstatus

ExplanationThe program received an unexpected message inresponse to the CF CHP command setting a senderpath from a connected system to a coupling facility toeither OFFLINE or ONLINE.



System programmer responseCheck the netlog for related messages to determinethe cause of the error.

Classes: 40 43.

Modules: INGRX913, INGRX915.

AOF902I DRAINING THE CF cf_name DIDNOT COMPLETE SUCCESSFULLY

ExplanationThe program received an unexpected message inresponse to the CF CHP command setting a senderpath from a connected system to a coupling facility toOFFLINE.




Classes: 40 43.

Modules: INGRX913.

AOF903I EITHER THE SPECIFIED CF IS NOTDEFINED OR NO CF HAS BEENDEFINED

ExplanationEither the command was executed in a sysplex thatdoes not use any coupling facility or the name of thecoupling facility is not known in the sysplex.


Operator responseSpecify a valid coupling facility name.


Modules: AOFRVX2A, AOFRVX22, AOFRX210,INGRX900, INGRX901.

AOF904I A CF/CDS PROCESS IS STILLRUNNING. ACTION action name ISREJECTED

ExplanationWhile the AUTXCF task is busy, new actions arerejected. This avoids performance degradation due tomultiple rebuild processes, or unpredictable resultsdue to multiple executions of an action.



The variable action shows the CF or CDS action thatis being performed.The variable name shows the name of the CF or theCDS.


Operator responseRetry the action later.


Modules: INGRVX3D, INGRVX90.

AOF905I action OF STRUCTURE/CF strnameFAILED

ExplanationThe program received an unexpected message inresponse to a SETXCF command. The action that isrelated to the structure or coupling facility did notcomplete successfully.

System actionProcessing stops except when all the structures of acoupling facility are being rebuilt one by one. In thiscase processing continues with the next structure.



Classes40, 43.

AOF906I TIME-OUT OCCURRED ONCOMMAND command

ExplanationThe command did not respond in time. Reasons couldbe:

• XCF commands:

These can time out because they are processed byone single task.

• Commands that implement the Health Checkerfunction:

These are INGRX352 and INGRVX35. They can timeout because there is a problem with task AOFHC, forexample, the task may not be active.

System actionProcessing terminates except when all structures of acoupling facility are being rebuilt. In this caseprocessing continues with the next structure.

Operator responseBefore executing the action again, check the netlogand the system activities to determine the cause of thetime-out.


Classes40, 43.

AOF907I STRUCTURE strname HASCONNECTIONS OTHER THANFAILED-PERSISTENT

ExplanationThe automation detected at least one connection tothe structure that does not have the status FAILED-PERSISTENT. Because XCF does not allow for thedeletion of such a structure, the action is rejected.


Operator responseMake sure that the structure has either noconnections, or only FAILED-PERSISTENT connectionsbefore you force the deletion of the structure again.


Classes: 40 43.

Modules: INGRX911.

AOF908I START OF AUTOTASK tasknameFAILED. RC = rc



ExplanationAny action that is related to a sysplex resource, forexample, a coupling facility, is performed on adedicated autotask. If the task is not active, it isstarted via the AUTOTASK command. However, thecommand failed with the return code rc.



System programmer responseAnalyze the return code and correct the error. Refer tothe description of the AUTOTASK command help in theonline help (HELP AUTOTASK).

Classes: 40 44.

Module: INGRVX90

AOF909I FUNCTION function REJECTEDDUE TO A CF STATUS CHANGE

ExplanationYou requested the function function to be performed.Meanwhile the status of the affected coupling facilityhas changed. The function is rejected because thecurrent status of the coupling facility does not matchthe status required by the function.

System actionThe program terminates.

Operator responsePress the refresh key to display the latest status.


Classes: None.

Module: INGRVX90

AOF910I POLICY policy COULD NOT BEACTIVATED

ExplanationDuring verification of the policy policy the automationdetected that the policy does no longer fulfill the

criteria to become active. The automation rejected thecommand to make the policy the active policy.


Operator responseRefresh the screen. Then retry the operation.


Classes: None.

Module: INGRVX90

AOF911I POLICY CHANGE(S) PENDING

ExplanationAfter the new policy has become active, theautomation detected that one or more structures havea policy change pending.

System actionThe command completed successfully.

Operator responseUse the command INGCF STR to find out whatstructures have a pending status. Rebuild each ofthese structures to remove its pending status.


Classes: None.

Module: INGRVX90

AOF912I XCF COMMAND 'command' IS NOTSUPPORTED BY THIS SYSTEM.

ExplanationThe designated system does not support the indicatedXCF command. START/STOP MAINTMODE requiresz/OS version 1.9 or later.




Operator responseReenter the command on a system that supports thecommand.


Classes: None.

AOF913I itemname VALUE OF CDS TYPEtype HAS BEEN CHANGED FROMoldvalue TO newvalue

ExplanationThe automation detected a situation where the size ofa couple data set must be increased to prevent anoutage situation. The value of the item itemname hasbeen increased as stated.



System programmer responseDetermine the reason for the change and take actionaccordingly.

Classes: 40, 43.

Module: INGRX711

AOF914E RECOVERY OF THE CDS TYPE typeFAILED. RSN= reason

ExplanationThe recovery of the couple data set of type type failed.Reason

Explanation10

The command ‘SETXCF COUPLE,PSWITCH’ failed.19

The LOGR couple data set(s) could not beextended.

20The control card information of the primary coupledata set could not be obtained.

21A temporary couple data set with the new itemvalues could not be formatted.

22The temporary couple data set could not beallocated.

23The old alternate couple data set could not bedeleted.

24The temporary couple data set could not be madethe primary couple data set.

25The old primary couple data set could not bedeleted.

26The old primary couple data set could not bereformatted.

27The reformatted old primary couple data set couldnot be allocated as the new alternate couple dataset.

28The reformatted old primary couple data set couldnot be made the new primary couple data set.

29The temporary couple data set could not bedeleted.

2AThe old alternate couple data set could not bereformatted.

2BEither the reformatted old alternate couple dataset or a new spare couple data set could not beallocated as the alternate couple data set.



System programmer responseCheck the netlog and the system log for related systemmessages. Determine the reason and take actionaccordingly.Reason

Explanation10

Check the system log to determine the reason whyXCF did not switch the couple data sets. If themessage was issued while extending the coupledata sets, follow the comment for reason codes 20through 29.



19Follow the description of reason codes 20 through2B.

20-2BThese codes relate to the process of extending thecurrent couple data set(s) of type type. The codesreflect the progress of the process. Determine thecurrent couple data sets and complete the processmanually. Depending on the progress, you candetermine the appropriate control card informationeither using the command INGPLEX CDSTYPE=type (reason > 24) or running the XCF utilityagainst the temporary couple data set (reason >21). If reason code 21 is issued, check the systemlog for an IXG257I or IXG261E message. If youfind them, extend the couple data set(s) byincreasing the DSEXTENT value by 1 or when notavailable by setting the value to 1. Otherwise andfor reason code 20 determine the originator of therequest to get the new item values.

Classes: 40, 43.

Module: INGRX305, INGRX711, INGRX720

AOF915E NO SPARE VOLUMES DEFINEDFOR CDS TYPE type.

ExplanationThe recovery of couple data sets of type type has beentriggered. However, the automation could notcomplete the recovery because no spare volumes havebeen defined where a couple data set could beallocated.



System programmer responseReview the netlog and the system log. If the messagehas not been issued during the initialization of theautomation, complete the recovery manually. Toprevent any future occurrence of this message, modifythe customization by adding one or more sparevolumes for the named type of couple data sets. Thenrecycle NetView.

Classes: 40, 43.

Module: INGRX720

AOF916E NO MORE SPARE VOLUMESAVAILABLE FOR CDS type type.

ExplanationThe recovery of couple data sets of type type has beentriggered. However, the automation could notcomplete the recovery because all predefined sparevolumes are either already in use, or they areunusable.



System programmer responseReview the netlog and the system log and completethe recovery manually. Then check the predefinedspare volumes of the named type of couple data sets.When less than three volumes have been defined andthe corresponding couple data sets are allocated toXCF add at least one more spare volume and thenrecycle NetView. Otherwise, determine the reason whythe spare couple data sets or volumes could not beused. One reason can be that there is not enoughcontinuous space on the volume.

Classes: 40, 43.

Module: INGRX720

AOF917E THE HIGH-LEVEL QUALIFIER HASNOT BEEN DEFINED.

ExplanationThe recovery of couple data sets has been triggered.However, the automation could not complete therecovery because the high-level qualifier that wasused to create a spare couple data set has not beendefined.



System programmer responseReview the netlog and the system log and completethe recovery manually. To prevent any futureoccurrence of this message, disable the recovery forcouple data sets. Or, modify the customization bydefining the high-level qualifier and then recycleNetView.



Classes: 40, 43.

Module: INGRX720

AOF918I THE AUTOMATION IS GOING TOSWITCH THE COUPLE DATA SETSOF type

ExplanationThe automation is going to switch the couple data setsof the specified type.

The variable type shows the type of the couple datasets that are being switched.



Classes: 40, 43.

Module: INGRX720

AOF919I function DETECTED STATUS statusFOR CF cfname

ExplanationThe function function detected a status change of thecoupling facility inhibiting the function from furtherprocessing.


Operator responsePress the REFRESH key and retry the function ifpossible.


Classes: None.

Module: INGRX914

AOF920I NO SIGNALLING PATHS MATCHTHE SPECIFIED CRITERIA criteria

ExplanationThe program set up the commands MVS DISPLAYXCF,PATHIN,DEVICE=ALL and MVS DISPLAY XCF,

PATHOUT,DEVICE=ALL. However, the messageAOF920I was returned.

The variable criteria shows the path type (eitherPATHIN or PATHOUT).




AOF921I CONSOLE console IS INACTIVE

ExplanationThe MVS command D R,LIST,T,CN=console wasissued. However, no data was returned because theconsole is INACTIVE. Therefore, no requests can bedisplayed.




Classes: None.

Module: AOFRVX41

AOF922I REBUILD OR FORCE OFSTRUCTURE structure_name NOTALLOWED

ExplanationAn attempt was made to REBUILD or FORCE acoupling facilitiy structure. However, the REBUILD orFORCE command is not supported for this structure.This can have one of the following reasons:

• The structure has no connections allocated and doesnot support system-managed rebuild.

• The structure has no active connections allocatedand does not support system-managed rebuild.



• One or more of the structure’s active connectionswas created with REBUILD=NO and system-managed rebuild is not supported.

• No alternate coupling facility is defined, available orhas sufficient space.

The variable structure_name shows the name of thestructure that the REBUILD or FORCE command isnot supported for.




AOF923I NO ACTIVE TARGET SYSTEMFOUND ON TARGET HARDWAREtarget (LU=LUNAME)

ExplanationThe 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.


Operator responseUse the processor operations command ISQXDST toverify that at least one target system is initialized. Ifnot, issue the command ISQXIII target where target isone of the target system names in the list. When thecommand completes successfully, retry the GETSPCFPcommand.

System programmer responseIf the luname has changed, correct the name in theprocessor operations control file and restart processoroperations.

Classes40, 43.

AOF924A AUTOMATION OF MESSAGEixc_msg TERMINATED. REASON:reason[, {PROCESSOR

OPERATIONS|BCPII} COMMANDRC=rc]. SYSID: sysname.

ExplanationThe variable ixc_msg shows the message thattriggered the automation. It can have the followingvalues and explanations:IXC102A

XCF is removing a system from the sysplex.IXC402D

XCF determined that a system in the sysplexappears to be inoperative.

XCF waits for the reply to proceed. However, the replycould not be automated.

• The variable reason shows the reason code that wasissued. It can have the following values:10

The message being automated has not beenformatted as expected. The message identifiercould not be located.

11A command was issued to the MVS system thatreported that a system left the sysplex. Atimeout occurred while waiting for a reply to thiscommand.

12The proxy resource name for the system leavingthe sysplex could not be determined.

13The Support Element of the system leaving thesysplex cannot be reached.

14The target system name of the ISQ900I messagecould not be obtained or the target system thatsent the ISQ900I message is not initialized toprocessor operations.

15The replyid for the message being automatedcould not be determined.

16The system name could not be located in theautomated message.

17The message that triggered the automationcould not be retrieved for automation.

18The automation requirements for the systemleaving the sysplex could not be determined.

19An error occurred while checking if the messagewas still outstanding.



30A processor operations command failed. Refer tothe appropriate command description.

31A timeout occurred while waiting for theresponse of the Processor Managementcommand.

32The reply to the outstanding WTOR could not besent.

33An error occurred while determining the status ofthe local sysplex.

• The variable rc shows the value of the return code.


Operator responseDepending on which message triggered theautomation, respond as follows:IXC102A

Complete the shutdown of the system leaving thesysplex. Then reply DOWN to the outstandingWTOR.

IXC402DEither reply 'INTERVAL=sssss' (range 0 to 86400)to give the system the specified interval to becomeoperative again. Or, complete the shutdown of thesystem leaving the sysplex. Then reply DOWN tothe outstanding WTOR.

System programmer responseCorrect the problem. If reason code 11 was issued, noaction is required.

ModuleAOFRX700, AOFRX701, AOFRX702, INGRX705,INGRX706

Classes40, 43

TECYES

AOF925I AUTOMATION OF MESSAGEixc_msg FOR system COMPLETEDSUCCESSFULLY

ExplanationThe automation of message IXC102A or IXC402D forsystem system ompleted successfully. The system isno longer part of the sysplex.

System actionNone.



ModuleAOFRX700, AOFRX701, AOFRX702, INGRX705,INGRX706.

ClassesNone.

TECNO

AOF926I ERROR error DETECTED DURINGAUTOMATION OF MESSAGEixc_msg

ExplanationThe routine responsible for the automation ofmessages IXC102A and IXC402D found an error.

• The variable error shows the error condition. Thefollowing error conditions can occur:10

The message is neither the IXC102A nor theIXC402D message.

11The same message is being processed byanother task.

12Two or more commands were defined in thecustomization dialogs for message IXC102A.However, only one ISQCCMD can be issued.

13The command defined for IXC102A message isnot an ISQCCMD command.

14The reply is no longer outstanding.



15Incorrect call of a subsequent clist.

30Using the supplied or default command, anattempt was made to deactivate the systemleaving the sysplex. Another attempt will bemade using the default command.

System actionProcessing terminates for conditions 10, 11, 14, and15. For conditions 12, 13 and 30 processing continuesusing the default processor management commandSYSRESET CLEAR.


System programmer responseIf error conditions 12, 13 or 30 occurred, correct thedefinitions and reload the automation control file.

ModuleAOFRX700, AOFRX701, AOFRX702, INGRX705,INGRX706.

ClassesNone.

TECNO

AOF927E WTOR|WTOR BUFFER SHORTAGECOULD NOT BE RESOLVED

ExplanationThe sysplex automation to recover from a WTO orWTOR buffer shortage did not complete successfully.One or multiple recovery stages signalled an error. Thisis a transient status of the recovery. The messageIEA406I/IEA232I for WTO/WTOR buffer shortagerelief may indicate that the buffer shortage has beenresolved.


Operator responseCheck the system log for message IEA406I/IEA232Iindicating a buffer shortage relief. If the messagecould not be found, perform manual recovery actions.

System programmer responseSearch the system log for message IEE889I issued bythe operating system internally. Identify the bufferingconsoles or jobs. If possible, requeue console buffersto the system log (K Q,L=conname). If possible,increase MLIM. Cancel jobs buffering messages orreplies. After message IEA406I/IEA232I is issued,check whether the current CONSOLxx definitions mayneed to be adjusted to avoid future buffer shortages.

ModuleINGRX730

Classes40, 43.

AOF928I SYSPLEX sn bt RECOVERYINCREASES THE in VALUE TO nv

ExplanationThe automation has detected a shortage of message orreply buffers. As a recovery result, the limit value isincreased to avoid further buffer shortages. Thechanged 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 replymessage buffers.The variable in RMAX specifies the maximum bufferlimit of write to operator with reply messages. If thesystem runs in SYSPLEX=LOCAL mode or thenumber of systems in the sysplex is greater thaneight, the RMAX value is set to 9999. Otherwise it isnot changed.The variable nv shows a numeric number,representing the new limit value that is going to beactive.





System programmer responseThis message may indicate that the current RMAXvalue of CONSOLxx member needs to be adjusted.

Classes: 40, 43.

Module: INGRX730

AOF929I SYSPLEX sn bt RECOVERY SETS stON SYSTEM sys

ExplanationThe automation has detected a shortage of message orreply buffers. As a recovery result, a limit value or aconsole setting is changed to avoid further buffershortages. The changed value or console setting affectthe named system in the sysplex.

The variable sn specifies the name of the sysplex.The variable bt WTOR: write to operator with replymessage buffers.The variable st shows the string representing thecommand that was issued to recover from thebuffer shortage. The limit values or console settingsstay in effect until they are changed manually. Incase of an extended recovery situation, thismessage may be is issued multiple times showingcommands increasing MLIM or RLIM values.The variable sys specifies the name of the system.


Operator responseIf this message is displayed frequently, inform yoursystem programmer.

System programmer responseMultiple occurrence of this message may indicate thatthe CONSOLxx member specified limits or consoledefinitions need to be adjusted.

Classes: 40, 43.

Module: INGRX730

AOF930I HARDWARE STATUS CHANGEDETECTED

ExplanationThe hardware monitoring program detected a statuschange of one or more hardware components definedduring customization.




Classes: None.

Module: INGRX051

AOF931I VERIFICATION OF USER-DEFINEDCDS FAILED. RSN= reasonDSN=dsname

Explanation• The variable reason shows the value of the reason

code. The following reason codes can occur:1

The automation environment has not yet beeninitialized.

2The data set name conflicts with the namingconvention of the automation when creating anew couple data set.

4The specified data set is not defined.

8The specified data set is not available.

12The specified data set is already allocated.

16An unexpected error occurred.

20The DYNALLOC macro failed.

24The specified volume does not match the actualvolume.

• The variable dsname shows the name of the dataset.


Operator responseMake sure that the name of the data set and volume (ifspecified) are correct.



System programmer responseMake sure that the data set is defined and available.

Classes: None.

Module: INGRX301

AOF932I BOTH NAME AND VOLUME AREREQUIRED.

ExplanationThe user has only specified a user couple data setname or a volume.


Operator responseSpecify both a data set name and a volume.


Classes: None.

Module: INGRX301

AOF933I ACTION CODE IS NOTSUPPORTED.

ExplanationThe action code is not supported for this entry forsome program-related reason.


Operator responseSee the panel help for the reason. Use a valid actioncode.


Classes: None.

Module: INGRX300, INGRX904

AOF934I POLICY policy HAS BEENSTARTED.

ExplanationA ‘SETXCF START,POLICY’ command has been issuedfor the policy policy.


Operator responseCheck that the policy becomes the active policy.


Classes: None.

Module: INGRVX3A

AOF935I ENTER THE COUPLE DATA SETAND VOLUME.

ExplanationThe automation is waiting for a user-defined coupledata set to be specified.

System actionNone.

Operator responseEnter the required information.


Classes: None.

Module: INGRX301

AOF936E START OF POLICY policy FAILED.

ExplanationA ‘'SETXCF START,POLICY’ command has been issuedfor the policy policy. The command failed.


Operator responseReview the netlog.




Classes: None.

Module: INGRX301

AOF937E SOME PENDING STRUCTURESCANNOT BE REBUILT ANDREMAIN PENDING.

ExplanationThe automation function responsible for releasing the'POLICY CHANGE PENDING' status of the structuresdetected that one or more structures remain in thisstatus.


Operator responseUse the command 'DXCF,STR,STATUS=POLICYCHANGE' to list thestructures whose status is pending. Determine thereason why these structures remain in the status.Manually perform the necessary actions for releasingthe status.


Classes: None.

Module: INGRX919

TECNO

AOF938E DDNAME ddname IS PENDING.

ExplanationAn automation function could not completesuccessfully because a required data set is notavailable.

The variable ddname shows the name of the dataset that is not available.



System programmer responseAdd the ddname to the NetView startup procedure. Toprevent a NetView recycle, allocate the data setdynamically using the ddname above.

Classes: None.

Module: INGRVX20, INGRX200

TECNO

AOF939I THERE IS NO ACTIVE POLICY.

ExplanationThe automation detected that no policy is active at themoment.




Classes: None.


AOF940I resource(s) AUTOMATION IS/ARENOT ENABLED.

ExplanationThe selected function is not enabled for automation.


Operator responseEnable the function by setting the RECOVERY flag ofone of the named resources to 'Y'. Then, retry thefunction.

System programmer responseIf the function should be enabled by default, updatethe customization values.



ClassesNone.

AOF941I CFRM COUPLE DATA SET IS NOTAVAILABLE.

ExplanationThe CFRM active policy could not be read because thecouple data set supporting TYPE(CFRM) is notaccessible from this system.


Operator responseIssue the request from a system with access to aCFRM couple data set.


Classes: None.

Module: INGRVX9Q

AOF942I NO POLICIES DEFINED.

ExplanationThere are no policies defined for the selected coupledata set type.

System actionNone.


System programmer responseDefine policies as necessary.

Classes: None.


AOF943I NO LOG STREAMS ORSTRUCTURES DEFINED.

ExplanationThere are no log streams or structures defined in theLOGR couple data set.

System actionNone.


System programmer responseDefine log streams and structures as necessary.

Classes: None.

Module: INGRX312

AOF944I CDS TYPE cdstype IS NOTENABLED ON SYSTEM system.

ExplanationThe couple data set type cannot be displayed becauseit is not enabled on the target system.

System actionNone.



Classes: None.

Module: INGRX310

AOF945I CDS TYPE cdstype IS NOTACCESSIBLE ON SYSTEM system.

ExplanationThe couple data set type cannot be displayed becauseit is not accessible on the target system.

System actionNone.



Classes: None.



Module: INGRX310

AOF946I SOME SENDER PATHINFORMATION COULD NOT BEDETERMINED FOR cfname.

ExplanationCurrently not all systems in the sysplex have access tothe coupling facility cfname. However, the automationcannot determine the sender paths of some or all ofthose systems.


Operator responseIf the local system does not show the control unit ofthe coupling facility, try the command from a systemthat shows the information when you enter the MVScommand D CF,CFNM=cfname.


Classes: None.

Module: INGRVX9P

AOF947I action OF STRUCTURE structure ISNOT SUPPORTED.

ExplanationThe automation detected that the action selected forthe structure is either not supported or currentlyunavailable.

The variable action shows the action to beperformed.The variable structure shows the name of thestructure.

In case of SYSTEM-MANAGED actions the cause of theproblem could be that the CFRM couple data set is notformatted properly.

System actionThe action is not performed.



ModuleINGRX904

ClassesNone.

TECNO

AOF948I FUNCTION NO LONGERSUPPORTED.

ExplanationDue to some changes in a new version of this productthis function has either been replaced or deleted.


Operator responseIf the function was replaced, use the new function.


Classes: None.

Module: INGRVX90

AOF949I NO DUMP DATA SET AVAILABLEFOR JOB jobname

ExplanationThe automation tries to take a dump before the job iscanceled. Neither system dump data sets norautomatic allocated dump data sets were available.



System programmer responseTo fix the error do one of the following:

• Add more system dump data sets or volumes forautomatically allocated dump data sets



• Clear full dump data sets to prevent furtheroccurrences of this message.

ModuleINGRX741

Classes: 40

TECNO

AOF950I JOB jobname ON sysname HOLDSAN ENQ FOR nnn SECONDS ONRESOURCE resource

ExplanationThe automation found a long blocking ENQ on theresource held by the specified job. The policy definedduring customization does not allow the cancelation ofthe job to free the resource.

The variable jobname shows the name of the job.The variable sysname shows the system where thejob is running.The variable nnn shows the waiting time inseconds. A value of 999 is the maximum waitingtime shown.The variable resource shows the name of theresource where the ENQ was found.



System programmer responseIf the waiting time is feasible, remove the resourceentry from the policy or increase the time if applicable.Otherwise allow the cancelation of the job ifnecessary.

ModuleINGRX741

Classes40, 43.

TECNO

AOF951I DUE TO A LONG ENQ DETECTIONTHE JOB jobname ON sysname ISBEING CANCELLED.

ExplanationThe automation detected a long blocking ENQ held bythe specified job. The job is being canceled based onpolicy definitions.

The variable jobname shows the name of the job.The variable sysname shows the system where thejob is running.

System actionThe job is canceled with the MVS CANCEL command.



ModuleINGRX741

Classes: 40

TECNO

AOF952I DUE TO A AUXILIARY STORAGESHORTAGE DETECTION THE JOBjobname IS BEING CANCELLED

ExplanationThe automation found an auxiliary storage shortage.The system issued a message indicating the job hadrapidly increasing storage requests. The job is beingcanceled based on policy definitions.

The variable jobname shows the name of the job.

System actionThe job is canceled with the MVS CANCEL command.





ModuleINGRX742

Classes: 40

TECNO

AOF953E RECOVERY OF AUXILIARYSTORAGE SHORTAGE COULD NOTCOMPLETE SUCCESSFULLY.REASON=reason

ExplanationThe automation could not recover an auxiliary storageshortage.

The variable reason shows the reason code. It canhave the following values:

ReasonDescription

4The recovery was enabled, but neither sparevolumes for dynamically allocated page data setsnor preallocated page data sets were defined.

8The spare volumes for dynamically allocated pagedata sets and the predefined local page data setsare used up.

12The spare volumes for dynamically allocated pagedata sets and the predefined local page data setsare used up. Some of them have been markedunusable because the system rejected the datasets when the automation tried to make themavailable.

16The IDCAMS service failed for the dynamicallocation of a page data set. Check the netlog fordetails.

20The PAGTOTL value defined in IEASYSxx memberused during IPL does not allow to add more localpage data sets.

24The system issued a message indicating a problemwhen the automation tried to make a local pagedata set available.



System programmer responseIf reason codes 4, 8, 12, or 16 occurred, add morelocal page data sets manually. If reason code 20occurred, follow the instructions given in messagesIRA200E and IRA203I. For reason code 24 follow theinstructions of the messages IEE78n issued beforethis message.

ModuleINGRX742

Classes40, 43.

TECNO

AOF954I PAGE DATA SET dsnameSUCCESSFULLY ADDED.

ExplanationDue to a recovery situation the automationsuccessfully added a local page data set to the system.

The variable dsname shows the name of the dataset.



System programmer responseDelete the page data set via the PAGEDEL commandwhen the data set is no longer needed. The data set isthen returned to the list of spare page data sets beingused by the automation. If the data set wasdynamically allocated you can also delete it physicallywhen no other page data set is active on the volumewhere the data set is allocated.

ModuleINGRX742



Classes40, 43.

TECNO

AOF955I NO DIFFERENCES FOUND

ExplanationA comparison of IPL information did not indicate anydifferences.




ModuleINGRX200, INGRX201

ClassesNone.

TECNO

AOF956I IPL INFORMATION OF timestampFROM sysname HAS BEENDELETED

ExplanationAll IPL information collected for the system after it wasIPLed at timestamp was deleted.

The variable timestamp shows the time of the IPL.The variable sysname shows the name of thesystem.




ModuleINGRVX20

ClassesNone.

TECNO

AOF957I LOG ENTRY: entry

ExplanationThe automation has logged an intermediate result ofan automated process.

The variable entry shows the log entry.




ModuleINGRVX92

ClassesNone.

TECNO

AOF958I DUMP COULD NOT BE TAKEN.RC=rc RSN=rsn.

ExplanationThe requested dump could not be taken.

• The variable rc shows the return code. It can havethe following values:RC

Description



4Only partial dump was taken.

8SDUMPX macro error occurred.




24No private storage is available.

28No common storage is available.

• The variable rsn shows the reason code.


Operator responseDepending on the return code do the following:RC

Description4

Search the system log for message IEA911E forthe reason of the partial dump.

8Refer to the return and reason code description ofthe SDUMPX macro for the reason why the dumpcould not be taken.

12, 16, 20Contact your IBM service representative.

24, 28Retry the function later.


ModuleINGRX262

ClassesNone.

TECNO

AOF959I SYSTEM sysname IS NOTREGISTERED.

ExplanationThe requested system is not registered to theautomation. However, this function requires theregistration because it invokes system services locally.


Operator responseOverride the system name with blanks to force theselection panel showing the system being registered.Or, start the automation on the requested systemusing the same XCF group as the local system.


ModuleINGRX260

ClassesNone.

TECNO

AOF960E HARDWARE INFORMATION OFsystem COULD NOT BE VALIDATED.

ExplanationThe automation detected that neither the hardwareinformation of the indicated system has been defined,nor a connection to the Support Element of theindicated system has been made for any of theregistered systems. If the system fails, the automation(if enabled) is not able to take the appropriatehardware actions to prevent possible hardware-related outages caused by the system.

The following variables are used:system

The name of a system or a coupling facility.





System programmer responseAdd the hardware definitions and make them availableto all registered systems using the ACF command. Youcan ignore this message if: the indicated system willrun the automation, you have defined the necessaryhardware information, and the system is able tocontact the hardware.


Classes40.

TECNO

AOF961I UNABLE TO CANCEL UN-NAMEDJOB (SYSTEM=sysname/ASID=asid/ TCB=tcbaddr).RESOURCE=resource.

ExplanationAutomation detected a long running enqueue but isunable to cancel the job because the job name isunknown and it is running on an un-automated system.

The following variables are used:sysname

The name of the system running the addressspace.

asidThe address space ID running the task.

tcbaddrThe TCB address of the task holding the enqueue.

resourceThe enqueue resource major and minor name.

System actionNone.


System programmer responseEnsure the enqueue is released and terminate the jobif necessary.

ModuleINGRX741

Classes40, 43.

TECYES

AOF962I UNABLE TO TERMINATE UN-NAMED JOB (SYSTEM=sysname/ASID=asid/TCB=tcbaddr).RESOURCE=resource.

ExplanationAutomation detected a long running enqueue but isunable to cancel the job because the job name isunknown. An attempt to abend the task has alsofailed. Message AOF200I will detail why the abend hasfailed.






System actionNone.


System programmer responseEnsure the enqueue is released and terminate the jobif necessary.

ModuleINGRX741



Classes40, 43.

TECYES

AOF963I UN-NAMED JOB(SYSTEM=sysname/ASID=asid/TCB=tcbaddr) IS BEINGTERMINATED.RESOURCE=resource.

ExplanationAutomation detected a long running enqueue but isunable to cancel the job because the job name isunknown. Automation is attempting to abend the task.






System actionNone.


System programmer responseCheck that the job has abended and ensure that theenqueue is released.

ModuleINGRX741

Classes40, 43.

TECYES

AOF964I Due to the detection of a longminor_res lock the task taskid in

address space asid on systemsysname is being abended.

ExplanationThe automation detected a lock on the indicated minorsystem resource being held for more than 10 seconds.To prevent the lockout of further commands the taskholding the lock is being abended with the ability to doits own recovery.

The following variables are used:minor_res

The minor resource name of the lock. The majorname is SYSIEFSD.

taskidThe task ID holding the lock.


sysnameThe name of the system running the addressspace.

System actionThe automation calls the Recovery TerminationManager to abend the indicated task.



ModuleINGRX743

Classes40, 43.

TECYES

AOF965I The command command issued byjobname is being purged due to ahung command detection.

ExplanationThe automation detected a command that is stillexecuting. The command is abended to avoid lockoutsof other commands.



The following variables are used:command

The first two words of the command text whenapplicable.

jobnameThe job name issued the command.

System actionThe automation abends the indicated command.



ModuleINGRX743

Classes40

TECNO

AOF966I Value value of type type forsysname could not be evaluated.

ExplanationThe value for the indicated type could not be verified.The reason is that the BCP internal interface to thecorresponding Support Elements could not beestablished on any of the registered systems in thesysplex.


The name of the defined operating system.value

The defined value.type

The type in question. This can be one of thefollowing:CPC

The CPC name.LPAR

The LPAR name.SYSPLEX

The SYSPLEX name.

TYPEThe operating system type, such as MVS or CF.




ModuleINGRX809

Classes40

TECNO

AOF967E Value mismatch detected betweensystem1 and system2 for system3and type type.

ExplanationThe automation detected that the value of theindicated type could not be verified. The reason is thatthe BCP internal interface to the correspondingSupport Elements wasn't established on any of theregistered systems in the sysplex. In addition, at leasttwo different definitions exist for the indicated type ondifferent systems running SA z/OS.

As soon as the automation gets access to the SupportElement, the value will be re-evaluated andautomatically corrected.

The following variables are used:system1

The name of a system running SA z/OS.system2

The name of a system running SA z/OS.system3

The name of the defined operating system.type

The type in question. This can be one of thefollowing:CPC

The CPC name.



LPARThe LPAR name.

SYSPLEXThe SYSPLEX name.

TYPEThe operating system type, such as MVS or CF.



System programmer responseCheck and correct the definitions before the next start-up of the affected systems.

Make sure that the definitions specified in theautomation policy through the SA z/OS CustomizationDialog reflect reality. For instance, when a mismatchwas detected for type SYSPLEX, verify the SysplexName specified in the Sysplex Policy Definition andchange it to the real MVS sysplex name as required.

ModuleINGRX809

Classes40

TECNO

AOF968E Value oldvalue of type type forsysname1 on sysname2 has beenreplaced by newvalue.

ExplanationThe automation detected that your hardware definitiondiffers from the actual hardware. If the local systemname is not shown in the message, a different setupother than the local system has been used. This shouldgenerally be avoided.

The following variables are used:sysname1

The name of the defined operating system.newvalue

The new value.

oldvalueThe improper value. This may be (NULL) if a valuehas been found in the hardware configuration butthere is no definition in the ACF.

sysname2The name of the system where the impropersetting was detected.

typeThe type in question. This can be one of thefollowing:CPC

The CPC name.LPAR

The LPAR name.SYSPLEX

The SYSPLEX name.TYPE

The operating system type, such as MVS or CF.

System actionThe improper definition is temporarily replaced by theactual value to prevent any outage that could becaused by the old value.


System programmer responseCheck and correct the definitions in the ACF before thenext startup of the indicated system.

ModuleINGRX809

Classes40

TECNO

AOF969I SESSION luname OF SMCSCONSOLE consname HAS BEENTERMINATED DUE TO A BUFFERSHORTAGE CONDITION.

ExplanationAutomation has detected a shortage of message orreply buffers caused by the indicated console. Toprevent the shortage from turning into an outage



condition, the console session has been terminated.This recovery action cannot be reversed on theshortage relief message.

The variable luname specifies the name of thesession.The variable consname specifies the name of theconsole.




ModuleINGRX730

Classes40

TECNO





Chapter 3. Messages AOFS000I to AOFS820I

AOFS000I aa

ExplanationThis message is given in conjunction with asubsequent error message that explains what isincorrect. It shows the SDF panel that is incorrect.

The variable aa identifies the buffer data in error.

System actionNone.



AOFS001I aa is active

ExplanationThe task aa has been activated.

The variable aa shows the name of the task.

System actionNone.



AOFS002I aa is inactive

ExplanationThe task aa is not active at this time.

The variable aa shows the name of the tasknumber.

System actionNone.

Operator responseStart the task by issuing START TASK=AOFTDDF.


AOFS003I aa is terminating.

ExplanationThe task aa is ending.


System actionNone.



AOFS004I aa is terminated

ExplanationThe task aa has ended.


System actionNone.



AOFS005I LOGON to aa was unsuccessful

ExplanationThe requested action could not be performedsuccessfully.

Messages AOFS000I to AOFS820I


The variable aa shows the name of the object thatthe action was performed on.

System actionNone.



AOFS006I LOGON denied, maximum usersexceeded.

ExplanationThe maximum number of users that can log on as SDFoperators has been reached.

System actionSDF cannot be accessed.


System programmer responseIncrease the value of MAXOPS in member AOFINIT inyour NetView DSIPARM data set. Then restart SDF.

AOFS007I Request denied because NetViewis terminating.

ExplanationSDF cannot be accessed because NetView is ending.

System actionNone.



AOFS008I Command SDF is not supportedunder a non-OST task.

ExplanationThis message is a response to an attempt to accessthe SDF from a non-OST task. Non-OST tasks cannotaccess the SDF because they do not support full-screen function.

System actionNone.



AOFS009I Extended attribute support isrequired.

ExplanationThis message is a response to a request to display aSDF panel. The panel could not be displayed becauseit requires extended console support.

System actionThe SDF request is ended.



AOFS010I Request "aa" was successful for"bb".

ExplanationThe request has been completed successfully.

The variable aa shows the request that wasperformed.The variable bb shows the component that wasprocessed.

System actionNone.





AOFS011I Request "aa cc" was successful for"bb".

ExplanationThe request has been completed successfully.

The variable aa cc shows the request that wasperformed.The variable bb shows the component that wasprocessed.

System actionNone.



AOFS012I Panel aa has been added.

ExplanationThe panel aa has been added successfully.

The variable aa shows the name of the panel.

System actionNone.



AOFS013I Panel aa has been replaced.

ExplanationThe panel aa has been replaced successfully.


System actionNone.



AOFS014I Panel aa has not been added.

ExplanationThe panel aa has not been added because of a syntaxerror condition.





AOFS015I Panel aa has not been replaced.

ExplanationThe panel aa has not been replaced because of asyntax error condition.


System actionThe former panel definitions are still valid.


System programmer responseCorrect the panel definitions and reload the panel.

AOFS020I Too many columns defined forscreen width.

ExplanationDynamic composition of a SDF panel was requestedwith BODY or CELL statements but the number ofcolumns specified exceeds the maximum panel width.


Chapter 3. Messages AOFS000I to AOFS820I 165

System actionNone.



AOFS021I Temporary screen read error.

ExplanationThe number of lines allowed has been exceeded.

System actionThe system continues to attempt to display the screendata.

Operator responseIf this condition does not change without intervention,contact your system programmer.

System programmer responseReview the adequacy of the screen display buffer forthe expected screen activity levels.

AOFS022I Temporary screen read error - limitexceeded.

ExplanationThe number of lines allowed has been exceeded.

System actionThe system terminates the function.


System programmer responseReview the adequacy of the screen display buffer forthe expected screen activity levels.

AOFS023I Buffer size specified is too smallfor screen size.

ExplanationThe screen buffer size specified in AOFINIT is toosmall for the screen.

System actionNone.


System programmer responseIncrease the value of SCREENSZ in AOFINIT in yourNetView DSIPARM data set. Then restart SDF.

AOFS030I Unable to find component aa.

ExplanationSDF did not find an entry for the component aa.

The variable aa shows the name of the componentin one of the following formats:

status_comproot.status_comproot.status_comp(group_comp)root.status_comp(major_group_comp.group_comp)

This is an informational message only and does notnecessarily indicate a problem. You can addcomponent aa to your SDF tree and the messageshould disappear. Otherwise, this message can beignored.

System actionNone. The missing component aa is ignored.


System programmer responseIgnore this message or add the component aa to yourSDF tree so the message disappears.

AOFS031I bb is unable to find component aa.

ExplanationThe command did not find an entry for the componentaa.

The variable aa shows the name of the component.The variable bb shows the name of the command.

System actionNone.





AOFS032I Unable to find component "aabb(cc)".

ExplanationSDF did not find an entry for the component aa.

The variable aa shows the root name of thecomponent.The variable bb shows the name of the component.The variable cc shows the alternate name of thecomponent.

System actionNone.



AOFS080I MIN=aa CUR=bb MAX=cc

ExplanationThe program has allocated a data space for storingstatus descriptor information. This message shows thecurrent allocation units.

The variable aa shows the minimum number ofblocks.The variable bb shows the current number ofblocks.The variable cc shows the maximum number ofblocks.

System action:None.



AOFS081I SC=aa(bb) SCD=cc(dd)SCDC=ee(ff)

ExplanationThe program has allocated a data space for storingstatus descriptor information. This message shows thecurrent allocation units.

The variable aa shows the total number of SCcontrol blocks.The variable bb shows the number of SC controlblocks in use.The variable cc shows the total number of SCDcontrol blocks.The variable dd shows the number of SCD controlblocks in use.The variable ee shows the total number of SCDCcontrol blocks.The variable ff shows the number of SCDC controlblocks in use.

System action:None.



AOFS090I aa bb cc status information

ExplanationA request to use status descriptor information hasbeen processed for the status component identified inthis message. Messages AOFS091I, AOFS092I,AOFS093I, and AOFS094I are generated after this oneand show the contents of the status descriptorsmatching the request search arguments.

The variable aa shows status component name inone of the following formats:

rootroot.group_comproot.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 passedby SDF, it appears in parentheses following theprimary status component name.

System actionProcessing continues. However, the function may notoperate as requested.





AOFS091I aa.bb(ii.cc),PR=dd,RV=ee,CO=ff,HL=gg,DP=hh

ExplanationA status descriptor has been found that matches thesearch arguments in a request to use status descriptorinformation. This message identifies the statusdescriptor and shows some of the information itcontains. This message identifies the status descriptorand shows some of the information it contains.Messages AOFS092I, AOFS093I, AOFS094I, andAOFS096I show additional information contained inthe status descriptor.

• The variable aa shows the root (system) name of therequested status component.

• The variable bb shows the status component name.• The variable cc shows the alternate status

component name.• The variable dd shows the priority associated with

the status descriptor. (This is normally specified in arequest to add the status descriptor to the chain ofdescriptors for a status component).

• The variable ee shows the reference value for thestatus descriptor.

• The variable ff shows the color associated with thestatus descriptor. If this color is not specified on arequest to add a status descriptor, the default colordefined for the priority of the status descriptor isused. The color is presented in abbreviated form asfollows:

– B (Blue)– G (Green)– P (Pink)– R (Red)– T (Turquoise)– W (White)– Y (Yellow)

• The variable gg shows the highlighting optionassociated with the status descriptor. Thehighlighting option is presented in abbreviated formas follows:

– B (Blink)– N (Normal)– R (Reverse)– U (Underscore)

• The variable hh shows the number of existingduplicate status descriptors. Duplicate statusdescriptors have identical reference value, priority,info, color, highlight, and data values.

• The variable ii shows the major component name ofthe alternate status component name if present.




AOFS092I DATE=aa,TIME=bb,REPORTER=cc(dd),PFP=ee,PU=ff,PD=gg,PLVU=hh,PLVD=ii

ExplanationA status descriptor has been found that matches thesearch arguments in a request to use status descriptorinformation. This message shows some of theinformation contained in the status descriptor.Messages AOFS091I, AOFS093I, AOFS094I, andAOFS096I contain additional information contained inthe status descriptor.

The variable aa shows the date that the statusdescriptor was created on in the formatYYYYMMDD.The variable bb shows the time that the statusdescriptor was created in the format hh:mm:ss.The variable cc shows the NetView operator ID thatmade the request to create the status descriptor.The variable dd shows the node of the reporter, ifavailable, appears in parentheses immediatelyfollowing the ID.The variable ee indicates whether or not the statuscondition is propagated to the focal point. Ifpropagation was requested, Y is shown, if not, N isshown.The variable ff indicates whether or not the statuscondition is propagated upward through the SDFtree structure. If upward propagation wasrequested, Y is shown; if not, N is shown.The variable gg indicates whether or not the statuscondition is propagated downward through the SDFtree structure. If downward was requested, Y isshown; if not, N is shown.



The variable hh shows the tree node that upwardpropagation is not performed beyond. Anasterisk(*) indicates that upward propagation endsat the root (system) node.The variable ii shows the tree node that downwardpropagation is not performed beyond. An asterisk(*) indicates that downward propagation isperformed to all subordinate nodes of the statuscomponent.




AOFS093I IN=aabbaa

ExplanationA status descriptor has been found that matches thesearch arguments in a request to use status descriptorinformation. This message shows some of theinformation contained in the status descriptor.Messages AOFS091I, AOFS092I, AOFS094I, andAOFS096I show additional information contained inthe status descriptor.

The variable aa shows the delimiter enclosing thedescriptor information.The variable bb shows the value used to replace thedefault STATUSTEXT information when the statusdescriptor is used as the basis for the STATUSFIELDand a status descriptor number other than 0 isspecified on the STATUSFIELD definition.




AOFS094I DA=aabbaa

ExplanationA status descriptor has been found that matches thesearch arguments in a request to use status descriptorinformation. This message shows some of theinformation contained in the status descriptor.Messages AOFS091I, AOFS092I, AOFS093I, andAOFS096I show additional information contained inthe status descriptor.

The variable aa shows the delimiter enclosing thedescriptor information.The variable bb shows the data displayed when thestatus descriptor is selected as the basis for adetail display.




AOFS095I End of aa status information

ExplanationThis message identifies the end of the statusinformation:

The variable aa shows the status component namein one of the following formats:

rootroot.group_comproot.status_comp(group_comp)root.status_comp(major_group_comp.group_comp)

System actionNone.



AOFS096I Uaa=bbccbb



ExplanationA status descriptor has been found that matches thesearch arguments in a request to use status descriptorinformation. This message identifies the statusdescriptor and shows some of the information itcontains. Messages AOFS091I, AOFS092I, AOFS093I,and AOFS094I show additional information containedin the status descriptor.

The variable aa shows the ID of the user data area.Currently, just one user area is supported.The variable bb shows the delimiter enclosing theuser data.The variable cc shows the data that is displayedwhen the status descriptor is selected as the basisfor a detail display.




AOFS097I aa

ExplanationThis message is generated by the command SDFQNM.It provides the name of an SDF root component of thecurrent tree structure.

The variable aa shows the SDF root componentname.




AOFS098I aa bbcc

ExplanationThis message is generated by the command SDFQNM.It provides the name of an SDF tree component for aselected root component.

The variable aa shows the level of the treecomponent right-justified.The variable bb shows the SDF tree componentname.The variable cc shows the major component namein parentheses. The name makes the treecomponent name unique if necessary.




AOFS099I End of aa

ExplanationThis message indicates the end of the command aa.

The variable aa shows the name of the command.

System actionNone.



AOFS500I Maximum number of "aa-bb"operands exceeded.

ExplanationThe maximum number of operands allowed for thekeyword identified in this message was exceeded.

The variable aa shows the name of the panel thatcontains the keyword.The variable bb shows the keyword that too manyoperands were specified for.

System actionNone.



Operator responseEnter the command again, making sure that thecorrect number of operands is specified for thekeyword you specify.


AOFS501I Specified operand "aa" invalid for"bb".

ExplanationAn operand that is not valid was specified for thiscommand.

The variable aa shows the operand that is not valid.The variable bb shows the command was entered.

System actionNone.



AOFS502I Specified operand "aa" invalid for"bb cc".


The variable aa shows the operand that is not valid.The variable bb cc shows the command that wasentered.

System actionNone.



AOFS503I Specified parameter "aa" invalid.

ExplanationThe specified parameter is not valid for this command.

The variable aa shows the parameter that is notvalid.

System actionNone.

Operator responseEnter the command again using the correctparameters.


AOFS504I Expected parameter(s) missing forrequest "aa".

ExplanationOne or more command parameters are missing.

The variable aa shows the parameter in error.

System actionNone.

Operator responseEnter the command again using the correctparameter(s).


AOFS505I Syntax error for "aa".

ExplanationA syntax error was encountered in the command thatwas entered.

The variable aa shows the parameter in error.

System actionNone.





AOFS506I First level of the tree must be a 1:aa.

ExplanationThere was an attempt to define the structure of a treewith a number other than 1.

The variable aa shows the first leaf of the tree.

System actionThe AOFTDDT task will not become active.


System programmer responseEnsure your system tree definitions in AOFTREE startwith a level number of 1. Then issue the STARTTASK=AOFTDDF command again.

AOFS507I Invalid level - less than 1: aa.

ExplanationThere was an attempt to define the structure of a treewith a number that is less than 1.

The variable aa shows the tree's leaf in error.

System actionThe AOFTDDF task will not become active.


System programmer responseMake sure that the system tree definitions in AOFTREEhave a level number of 1 or higher. Then issue theSTART TASK=AOFTDDF command again.

AOFS508I Status element in tree not found,Element=aa.

ExplanationThe root component or status component name, orboth, that were specified in an SDF STATUSFIELDstatement cannot be found in the active SDF treestructure. The information message is issued duringSDF initialization, or while processing an SDFPANEL

ADD command. If the function completes successfully,message AOFS011I is issued, indicating the panel inquestion.

The variable aa shows the name of the statuscomponent. The status component can bepreceded by the root component or by the rootcomponent and the major component nameseparated by periods.



System programmer responseEnsure that the referenced root component or statuscomponent, or both, that were specified in the SDFSTATUSFIELD statement for the loading panel exist inthe active SDF tree structure.

AOFS509I Status element major error,Element=aa.

ExplanationAn internal SDF status element chaining erroroccurred.

The variable aa shows the name of the statuscomponent. The status component can bepreceded by the root component or by the rootcomponent and the major component nameseparated by periods.

System actionSDF request ended.


System programmer responseIf you cannot determine the cause of the problemusing the information available to you, contact yourIBM service representative.

AOFS510I Tree levels out of sequence: aa.

ExplanationAn attempt was made to define the structure of a treewith the dependent subsystems numbered out ofsequence.



The variable aa shows the tree's leaf in error.

System actionThe AOFTDDF task will become active, but the statusof the subsystems will not be determined.


System programmer responseMake sure that the system tree definitions in AOFTREEfollow in a valid hierarchical sequence.

AOFS511I Member "aa" not found.

ExplanationSDF attempted to prepare the member named in themessage but could not find it.

The variable aa shows the name of the memberthat could not be found.



System programmer responseMake sure that the member identified in the messageis valid. Add the member in the DSIPARMconcatenation chain or correct the SDF paneldefinitions that refer to the erroneous member.

AOFS512I Field overlapping occurred in gg:aa(bb,cc) <-> dd(ee,ff).

ExplanationDuring the post-validation of all panels that have beendefined SDF detected an overlay between two fielddefinitions.

v

System actionThe panel is not processed.



AOFS513I Terminating propagation level"aa" not found.

ExplanationThe identified propagation level was not found the onthe chain of predecessors (ProplvLU) or among thedescendents of (ProplvLD) the status componentidentified as the target of the command.

The variable aa shows the propagation level(PropLvLU or PropLvLD) as specified by SDF.

System actionPropagation is performed; however, it ends at the rootnode or the descendent leaf nodes of the treestructure.

Operator responseCheck the propagation level value for accuracy.


AOFS514I Maximum number of aa keywordsexceeded.

ExplanationThe maximum number of occurrences of the keywordidentified in this message was exceeded. Themaximum number is normally a variable specifiedusing another keyword.

The variable aa shows the keyword that appearstoo many times.


Operator responseNote the message content and the command orfunction being attempted. Contact your systemprogrammer.

System programmer responseIncrease the number of allowable keywords bychanging or specifying the control variable.



AOFS515I Keyword aa is out of sequence.

ExplanationThe identified keyword appears incorrectly in relationto other keyword parameters specified for the functionbeing performed.

The variable aa shows the keyword that appearsincorrectly.



System programmer responseCorrect the keyword specification sequence and retrythe operation.

AOFS516I Keyword aa(bb) of cc is out ofsequence.

ExplanationThe identified keyword appears incorrectly in relationto other keyword parameters specified for the functionbeing performed.

The variable aa shows the keyword that appearsincorrectly.The variable bb shows the parameter that appearsincorrectly.The variable cc shows name of the panel.



System programmer responseCorrect the keyword specification sequence and retrythe operation.

AOFS517I Expected parameter(s) missing for"aa-bb".

ExplanationOne or more parameters are missing.

The variable aa shows the name of the panel.The variable bb shows the keyword that lacks theparameter(s).

System actionNone.


System programmer responseCorrect the panel definitions. Then enter the commandagain.

AOFS518I Expected parameter(s) missing for"aa-bb(cc)".

ExplanationOne or more parameters are missing:

The variable aa shows the name of the panel.The variable bb shows the keyword that lacks theparameter(s).The variable cc shows the parameter that ismissing.

System actionNone.



AOFS519I Specified operand "aabb" invalidfor "cc-dd(ee)".


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.The variable ee shows the parameter in error.

System actionNone.



AOFS520I Specified parameter "aa-bb"invalid.

ExplanationThe 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.

System actionNone.



AOFS521I CELL definitions do not fit in aa:BODY(bb,cc).

ExplanationDuring the post-validation of all panels that have beendefined SDF detected a BODY section with CELLdefinitions that will not fit. Either a single CELLdefinition is out of range or the total length of all CELLdefinitions is too large. The total length is computed asfollows:

#_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 panelwidth is used. In case the PANEL defines an undefinedwidth the screen width defined in member AOFINIT oron the command SDFPANEL is used.

The variable aa shows the name of the panel.The variable bb shows the actual row numberwhere the BODY field starts.The variable cc shows the actual columns numberwhere the BODY field starts.

System actionThe panel is not processed.



AOFS522I Field aa truncated bb to cc

ExplanationAn SDF command detected a keyword whose valuehas a length that exceeds the maximum length of thefield.

The variable aa shows the name of the field.The variable bb shows the original length of thefield.The variable cc shows the new length of the field.

System action:The value is truncated to the maximum possiblelength.


System programmer response:Correct the invocation of the SDF command.

AOFS523I Duplicate aa definitions found forbb

ExplanationThe task AOFTDDF detected duplicate panel or treedefinitions for the indicated name. The actualdefinitions may differ or not. SDF always uses thedefinitions that have been processed first. However,the processing sequence can differ from the sequenceof the definitions.

The variable aa shows the type of the definition.The variable bb shows the name of the panel or thetree.

System action:



Duplicate definitions are ignored.


System programmer responseRemove the duplicate definitions.

If the actual definitions differed in some data, issuethe command RESYNC SDFDEFS. This adjusts thedefinitions used by SDF.

AOFS800E Internal error: Request "aa"invalid.

ExplanationAn internal programming error occurred.

The variable aa shows the name of the request.


Operator responseRecord the type of the request, and contact yoursystem programmer.

System programmer responseContact your IBM service representative.

AOFS801E Internal error: Invalid descriptorpoint.

ExplanationAn internal programming error has occurred involvingthe propagation of status through the component treeas maintained by SDF. A request was made topropagate status without supplying the status to bepropagated.

System actionOther messages related to this problem might begenerated.


System programmer responseReport this problem to your IBM servicerepresentative. Attempt to identify the tree being used,and whether a status was being added or deletedwhen the condition was detected.

AOFS802E Internal error: Invalid state aaaction bb at cc.

ExplanationAn internal error occurred during processing of a SDFpanel definition statement. There is a syntax error inthe DSIPARM member that contains the paneldefinition.

The variable aa shows the value of the state that isnot valid.The variable bb shows the value of the action that isnot valid.The variable cc shows the position in error.

System actionNone.


System programmer responseReview the SDF panel definition and correct the syntaxthat is in error.

AOFS810I Macro aa type bb request wasunsuccessful, RC=cc.

ExplanationThe program called the indicated macro. The macrowas not able to satisfy the request and returned theindicated return code for use in problemdetermination.

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.

System actionNone.


System programmer responseCheck the return code to determine the cause of theproblem.

AOFS811I aa request was unsuccessful,RC=bb.




The variable aa shows the name of the macro.The variable bb shows the return code of themacro.

System actionNone.



AOFS812I Macro aa request wasunsuccessful, RC=bb.


The variable aa shows the name of the macro.The variable bb shows the return code of themacro.

System actionNone.



AOFS813I Macro aa request wasunsuccessful for bb, RC=cc.


The variable aa shows the name of the macro.The variable bb shows the name of the controlblock.The variable cc shows the return code of the macro.

System actionNone.



AOFS814I Macro aa type bb request wasunsuccessful, RC=cc, RSN=dd


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 themacro.

System action:None.


System programmer response:Check the return code to determine the cause of theproblem.

AOFS815I Data space service request failed,RC=aa

ExplanationThe program tried to reserve a new control block in thedata space that holds the status componentinformation. The reservation failed with the indicatedreturn code.

The variable aa shows the return code of therequest:

36 - The data space ran out of space.40 - The data space could not be extended.

System action:None.




System programmer responseReturn code 36 indicates that the maximum sizedefined in the DSIPARM member AOFINIT is notsufficient for your environment. Increase the value ofthe parameter MAXTREEDSPSZ and restart the taskAOFTDDF.

Return code 40 indicates a problem in extending thecurrent size of the data space up to the maximum sizedefined in the DSIPARM member AOFINIT. Checkwhether the data space has reached the installationlimit. The command SDFQTR returns information of thecurrent allocation units.

AOFS820I I/O error occurred whileprocessing member "aa".

ExplanationAn I/O error occurred during processing of themember aa.

The variable aa shows the name of the member.


Operator responseMake sure the member identified in the message isvalid. If the member identified in the message is valid,contact your system programmer for further analysis.

System programmer responseVerify that the member name exists in the file pointedto by the procedure in use at the time of the error.Review the Netlog being used at the time of the errorto see whether there was a system error that couldhave prevented the member from being found.



Chapter 4. Messages EVE120I to EVE842E (CICSAutomation)

This chapter contains CICS Automation messages. CICS Automation also uses the NetView HELPMSGfacility to provide message information online. To view a help panel for a specific message, enter on theCICS Automation command line:

HM EVEnnn

Where nnn is the message ID number.

EVE120I Command accepted for subsystem,APPLID = applid.

ExplanationAn EVESNCCI command has been validated and isaccepted.


EVE121E Error on DSIxxx request inprogname, RC = retcode.

ExplanationCICS Automation found an error on a DSIxxx macrorequest issued in the program identified by progname.The register 15 return code is retcode.


System programmer responseAnalyze the netlog and determine whether there is alogic error. If the problem is a CICS Automation logicerror, contact your IBM Support Center.

Problem determinationRefer to Customization: Using Assembler, for returncodes from the DSIxxx macro requests.

EVE122E EVENTASK NOT ACTIVE

ExplanationA DSIMQS macro request failed because theaddressed task identified by taskid was not active.This error can occur when any automated operatorspecified in the EVENTASK initialization member is not

active or when the EVENTASK optional task is notactive.

System actionWhen the error is met, a return code of 8 is passed tothe issue of the EVESNCCI command.

Operator responseIf the EVENTASK task is not active, start the task byissuing the "START TASK =EVENTASK" or by usingoption 9.3 from the operator interface. If one of theautomated operators is not active, start the autotaskby issuing the "AUTOTASK OPID=taskid" command.

System programmer responseDetermine why taskid was not active.

EVE125E No storage available on DSIxxxxrequest in progname.

ExplanationAn error has been met on a DSIxxx request in thespecified program, indicating that no NetView storageis available.


System programmer responseInvestigate NetView storage use. If you cannot locatethe source of the storage problem, contact your IBMSupport Center.

EVE128I Positive acknowledgement.

ExplanationA positive response (ACK) has been received on anEVESNCCI Converse request.

Messages EVE120I to EVE842E (CICS Automation)



EVE129E msgtext

ExplanationA negative response (NACK) has been received on anEVESNCCI Converse request or an error has beendetected during the processing of the request. In thelatter case, msgtext contains the EVE1nnE messagetext explaining the error.

Operator responseIf an error condition is indicated, browse the netlog todetermine the cause of the error. NACK can be a"normal" response from a CICS transaction. CSMT logmay contain useful information as well in case of anerror.

EVE130I EVENTASK ready.

ExplanationEVENTASK OPT initialization has completedsuccessfully.


EVE131I EVENTASK terminated.

ExplanationEVENTASK OPT has completed termination.


EVE132E Initialization member memnamenot found.

ExplanationThe EVENTASK initialization member memname couldnot be found in one of the DSIPARM data sets.


System programmer responseEnsure that the initialization member specified byMEM= keyword on the TASK statement for EVENTASKis 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.

ExplanationAn error of type retcode is on line linenum of theEVENTASK initialization member memname.01

Unrecognized keyword.02

Duplicate specification.03

Operand specification error.04

Too many server keywords.05

No valid servers specified.


System programmer responseCorrect the failing statement in the EVENTASKinitialization member memname and restart the taskwith the "START TASK = EVENTASK" command oroption 9.3 from the operator interface.

EVE136I Error on PPI request reqid, RC =retcode.

ExplanationThe program-to-program interface request reqidreceived a non-zero return code. This is generally anerror, however REQUEST 002 RC=014 indicates thePPI receiver is active; this is not an error condition.

System actionNone.


System programmer responseReview the NetView netlog and investigate the causeof the error. Program-to-program interface requesttypes reqid and request return codes retcode aredocumented in the appendix "Program-to-ProgramInterface Return Codes" in NetView Application



Programming Guide. reqid identifies the PPI requesttype and retcode details what the problem is in issuingthe PPI request.

EVE137E NetView subsystem not available.

ExplanationAn error has been encountered to a program-to-program interface request indicating that no NetViewsubsystem was available to act as a program-to-program interface server.

Operator responseAfter the NetView subsystem is restarted, start theEVENTASK optional task by issuing the "STARTTASK=EVENTASK" command or option 9.3 from theoperator interface.

System programmer responseDetermine why no NetView subsystem was active.

EVE140E Incorrect PPI buffer received.

ExplanationThe program-to-program interface buffer sent to theEVENTASK optional task was not correct. Possiblecauses include:

• Program-to-program interface buffer header wasincomplete.

• Request type was incorrect (not C, S, R, A, or N).• Length specification was inconsistent.


System programmer responseCorrect the routine that created the incorrect program-to-program interface buffer. If the error is caused by aCICS Automation logic error, contact your IBM SupportCenter.

EVE141E Incorrect MQS buffer received.

ExplanationThe MQS message buffer, containing a program-to-program interface request that was sent to theEVENTASK optional task, was not correct. Possiblecauses include:

• Program-to-program interface buffer header wasincomplete.

• Request type was incorrect (not C, S, R, A, or N).• Length specification was inconsistent.

Operator responseThis problem is caused by CICS Automation logic error.Contact your IBM Support Center.

EVE142E Function function not found inmemname.

ExplanationA program-to-program interface buffer sent to theEVENTASK optional task contained a function and typespecification that no entry in the EVENTASKinitialization member memname was found for.


System programmer responseAdd a request or response server for function in theEVENTASK initialization member memname if thefunction name was correct.

Programmer responseCorrect the routine that created the incorrect program-to-program interface buffer if the function namefunction was incorrect.

EVE148I Segment-chain id canceled.

ExplanationAn EVESNCCI cancel request successfully freed allsaved segments for the segment identifier id.


EVE149I Segment-chain id not found.

ExplanationAn EVESNCCI cancel request (TYPE=C) was issued.The specified segment-chain id could not be found.


EVE171E procname : Error in progname(transid), reason = reason.


Chapter 4. Messages EVE120I to EVE842E (CICS Automation) 181

ExplanationCICS Automation has detected an error in theprogram: progname in the transaction transid. Thetype of error is reason.

In all CICS messages procname is the JOB name orSTC name that identifies the CICS system that issuedthe message.

System actionDepending on reason a transaction dump is created inthe active CICS dump data set.

If the error occurred in: Then:

EVESPPIC, EVESPPIP orEVESPPIS,

The transaction isterminated.

EVESCCCI A non-zero return code ispassed to the caller.

EVESHLTH, andEVESHLTH was invokedby a converse request(TYPE=C)

A NACK response ispassed to NetView.

EVESTISP Control is relinquished toallow CICS initializationto continue, but theprogram-to-programinterface is not started.

EVESPERR or EVESPMSG Control is returned to thecalling module.


System programmer responseRefer to “Error Codes” on page 185 and if necessaryanalyze the transaction dump to determine the causeof the error, then correct the problem. If the problem iscaused by a CICS Automation logic error, contact yourIBM Support Center.

EVE172I applid : PPI active.

ExplanationThis message confirms that the program-to-programinterface successfully initialized.

The variable applid is the CICS applicationIdentifier, which is used as the PPI receiver namefor this CICS.

Operator responseNone required.

EVE173I applid : PPI inactive.

ExplanationThis message confirms that the program-to-programinterface normally terminated.



EVE174E applid : PPI not active.

ExplanationThe transaction to terminate the program-to-programinterface has been invoked, but the program-to-program interface was not active.



EVE175E applid : Function function notfound in EVESPINM.

ExplanationA program-to-program interface buffer sent fromNetView to CICS contained a function function that noentry in EVESPINM was found for.


System actionFor a converse request (TYPE=C), a NACK responsecontaining the error message text is returned to theoperator at the domain specified in the program-to-program interface buffer header. This is the operid indomainid of the originating EVESNCCI command.

For all other requests (TYPE=S, R, A or N): none.




System programmer responseAdd a request server for function in EVESPINM if thefunction name was correct.

Programmer responseCorrect the routine that created the incorrect program-to-program interface buffer if the function namefunction was incorrect.

EVE176E procname : No response expectedfor identifier id.

ExplanationA response identified by id was received fromNetView. No transaction is awaiting that response.This may be caused by:

• An incorrect id in the response• The transaction awaiting the response timing out• A C961 or C971 error occurring.


Programmer responseHave the NetView command list or commandprocessor that issues the unexpected PPI RESPONSEcorrected, or increase the timeout value on theconverse request.

EVE177E procname : NetView subsystem isnot available.

ExplanationA program-to-program interface request has beenissued, but not NetView subsystem was available toact as a program-to-program interface server.

System actionThe program-to-program interface request is ignored.The program-to-program interface is terminated.

Operator responseAfter the NetView subsystem that serves program-to-program interface requests has been (re)started,restart the program-to-program interface: "MODIFYprocname,COPS". COPS can also be restarted viasupport panel option 9.3.

System programmer responseDetermine why the NetView subsystem was notavailable.

EVE178E procname : PPI already active.

ExplanationThe transaction to start the program-to-programinterface was invoked. The program-to-programinterface was not inactive, however.

System actionThe program-to-program interface start-up request isignored.


EVE179E procname : Receiver programprogname problem, reason =reason.

ExplanationAn error has been encountered on a program-to-program interface request indicating that the specifiedreceiver program progname was "not defined" or "notactive."

System actionReturn code 8 and an error code (C226 or C204)identifying the precise cause of the failure are set forthe caller.


System programmer responseAnalyze the cause of the failure, then correct theproblem. Ensure that RECEIVERID= operand in theEVESPINM initialization member is identical toRECEIVERID= operand in the EVENTASK initializationmember.

EVE181E procname : Error on transactionstart copctrn for function function.

ExplanationA program-to-program interface transaction did notstart.



Operator responseEnsure that the transaction is correctly defined in theCICS subsystem and through the EVESPINM CICS PPIinitialization member.

EVE182E procname : Console has not beendefined to CICS.

ExplanationEVESPINM module specifies a console definitionwhere COPC transaction should be started. Thatconsole name is not defined in CICS.

System programmer responseEither correct EVESPINM, or define the console toCICS.

EVE209I WARNING: ACF ENTRY entrytype,HAS INVALID DATA "data" FOR"entry", reason.

ExplanationThe entry-type pair named in the message was foundby the automation routine to contain errors. Thismessage is issued when building the CICS MessageExit policy from the ACF data.

• The variable entrytype is the ENTRY-TYPE pair.• The variable data is the data that caused the error.• 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.• The variable reason is an explanation of the error.

Invalid number or invalid choice of keyword.

System actionThe message policy is loaded without the offendingdata.

In the case of MSGDISP= this might mean the entiremessage is not loaded into the policy.

In the case of TOKEN= or INSERT= the offendingTOKEN= or INSERT= statement is ignored.


System programmer responseCorrect the entry-type pair in your automation controlfile and reload it using the INGAMS command.

EVE654E No INCLUDE/EXCLUDE entriesexist in LISTSHUT table forsubsystem.

ExplanationThe LISTSHUT table must contain either INCLUDE orEXCLUDE entries for the specified subsystem in orderfor SHUTDOWN to occur.

System actionNo transactions will be purged.

Operator responseChange the table and reload the control file.

Classes40.

EVE657E Message received by EVEET050:msgtext.

ExplanationEVEET050 received an unexpected message.




Classes40.

EVE841I procname : text.

ExplanationThe CEMT command listed in text has been requestedfrom NetView through the program-to-programinterface.



System actionNone.

EVE842E procname : Unsupported CEMTcommand.

ExplanationThe CEMT command listed in the preceding EVE841Imessage is not supported by EVESCEMT, for example,CEMT PERFORM SHUTDOWN.

System actionIgnore CEMT command. If the CEMT command wasrequested with a converse request (TYPE=C), return aNACK response with message EVE842E as NACK text.


Error CodesCICS 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

ExplanationSomeone attempted to invoke a CEMT command or tostart or stop the program-to-program interface byentering the corresponding transaction name from aterminal, or someone entered the transaction name forthe long-running program-to-program interfacetransaction from a terminal.

System actionTerminate the transaction abnormally.


System programmer responseEducate your users that they should not alter thesetransactions.

ModuleEVESCEMT, EVESPPIC, EVESPPIP, and EVESPPIS.

C002

ExplanationThe address of the program-to-program interfaceIntercommunication Area (ICA) was corrupted,probably because some other program alteredunprotected storage in the CICS address space.

System actionIssue message EVE171E. Dump CICS and transactionstorage.


System programmer responseAnalyze the dump to find the cause of the error, thencorrect the problem.

ModuleEVESPPIP and EVESPPIS.

C003

ExplanationA program-to-program interface request was issuedwhile the program-to-program interface was notactive.

System actionIssue message EVE171E. Set return code 8 for caller.


System programmer responseStart PPI TASK.



ModuleEVESCCCI.

C004

ExplanationEVESCCCI has not been invoked via EXEC CICS LINK.

System actionIssue message EVE171E. Terminate transactionabnormally.



Programmer responseUse EXEC CICS LINK to invoke EVESCCCI.

ModuleEVESCCCI.

C005

ExplanationIncorrect parameter list passed to EVESCCCI.

System actionIssue message EVE171E. If the length of theparameter list is incorrect, terminate transactionabnormally; otherwise return to caller with return code12.



Programmer responseCorrect the parameter list passed via the COMMAREAon the LINK to EVESCCCI.

ModuleEVESCCCI.

C006

ExplanationThe buffer containing a program-to-program interfacerequest that was sent from NetView to CICS wasincorrect. This is caused by:

• An incomplete program-to-program interface bufferheader.

• An incorrect request type (not C, S, R, A, N).• An inconsistent length specification.• An incorrect program-to-program interface senderidentification. This is caused by a mismatch betweenthe RECEIVERID specifications in the EVENTASK andEVESPINM initialization members.

System actionIssue message EVE171E. Dump transaction storage.


System programmer responseIf caused by a mismatch between EVENTASK andEVESPINM, correct the mismatch error. Otherwise,contact your IBM Support Center because thisproblem is caused by a CICS Automation logic error.

ModuleEVESPPIC.

C007

ExplanationA CEMT request was sent over the program-to-program interface from NetView to CICS. The requestserver found that the INTDSECT block was incorrect.

System actionIssue message EVE171E. Dump transaction storage.Terminate transaction abnormally.




System programmer responseThis problem is caused by a CICS Automation logicerror. Contact your IBM Support Center.

ModuleEVESCEMT.

C008

ExplanationReturn code 12 was received from EVESCCCI becausethe OUTDSECT block was incorrect.




ModuleEVESCEMT, and EVESPPIC.

C009

ExplanationTransaction could not be started successfully.



System programmer responseIf non-terminal transaction security is not active inCICS, ensure that this function is disabled in CICSAutomation by specifying USERID=NO in the CICS PPIinitialization member EVESPINM. For furtherinformation on this member, refer to IBM Z SystemAutomation Product Automation Programmer’sReference and Operator’s Guide.

Make sure that the transaction is properly defined inthe CICS PPI initialization member EVESPINM.

If these requirements are fulfilled, contact your IBMSupport Center.

ModuleEVESPPIC

C011

ExplanationCICS WRITEQ TS failed.




ModuleEVESTISP and EVESPPIC.

C012

ExplanationCICS READQ TS failed.



System programmer responseThis problem is caused by a CICS Automation logicerror. Ensure that the PLTPI program EVESTISP hasbeen executed successfully. Contact your IBM SupportCenter.

ModuleEVESCCCI, EVESPPIC, EVESPPIP, and EVESPPIS.

C013



ExplanationCICS START failed.

System actionIssue message EVE171E. Dump CICS tables.


System programmer responseAnalyze the dump to find the cause of the failure andcorrect the problem. Ensure that the transaction thatfailed to start and the program to be invoked when thetransaction starts have been defined and enabled.Also make sure that the program resides in a DFHRPLlibrary.

ModuleEVESTISP, EVESPPIC, and EVESPPIS.

C014

ExplanationCICS RETRIEVE failed.

System actionIssue message EVE171E. Dump transaction storage. Ifthe CEMT command was requested through aconverse request (TYPE=C), return a NACK responsewith message EVE842E as NACK text. Terminatetransaction abnormally.



ModuleEVESCEMT.

C015

ExplanationCICS LINK or LOAD failed.

System actionIssue message EVE171E. Dump transaction storageand CICS tables. Terminate transaction abnormally.


System programmer responseAnalyze the dump to find the cause of the failure, thencorrect the problem. Ensure programs are defined andenabled and available in a DFHRPL library.

ModuleEVESCCCI, EVESCEMT, EVESPERR, EVESPPIC, andEVESPPIS.

C017

ExplanationCICS GETMAIN failed.



System programmer responseIncrease the region size.

ModuleEVESCCCI, EVESCEMT, and EVESPPIC.

C018

ExplanationCICS FREEMAIN failed, or, possibly, a storage violationhas occurred.





System programmer responseAnalyze the dump to find the cause of the failure, thencorrect the problem.

ModuleEVESCCCI.

C019

ExplanationCICS DELAY failed.

System actionIssue message EVE171E. Dump transaction storage.Set return code 16 for caller.



ModuleEVESCCCI.

C020

ExplanationCICS CANCEL failed.




ModuleEVESPPIC.

C117

ExplanationOS GETMAIN failed.



System programmer responseAnalyze the dump to find the cause of the failure. thencorrect the problem. Increase the region size oramend SIT parameters to allow for sufficient OSCOR.

ModuleEVESTISP.

C2nn

ExplanationA program-to-program interface problem hasoccurred. nn identifies the program-to-programinterface return code.

System actionFor nn = 20, 22, 23, 25, 31, 33, 36, 40, and 90, issuemessage EVE171E and dump transaction storage. Forall other values of nn, no message is issued.


System programmer responseDetermine the cause of the error. If the error is causedby a CICS Automation logic error, contact your IBMSupport Center.

Problem determinationProgram-to-program interface request return codesretcode are documented in Application ProgrammingGuide: Program-to-Program Interface,.

ModuleEVESCCCI and EVESPPIC.

C950



ExplanationThe TWA size of the COMT transaction is too small.



System programmer responseEnsure that the TWO size of the COMT transaction isgreater than or equal to the TWA size of the CEMTtransaction (512 bytes).

ModuleEVESCEMT.

C960

ExplanationA TS item passed to EVESCCCI by EVESPPIC when aresponse is received from NetView has an incorrectlength

System actionIssue message EVE171E. Dump transaction storage.Set return code 16 for the caller.



ModuleEVESCCCI.

C961

ExplanationRQE chain corrupted.

System actionIssue message EVE171E. Dump transaction storage.Set return code 16 for the caller.


System programmer responseThis problem is caused by a transaction that alteredstorage in the CICS address space, or by a CICSAutomation logic problem. Determine the cause of theproblem. If the problem is caused by a CICSAutomation logic problem, contact your IBM SupportCenter.

ModuleEVESCCCI.

C971

ExplanationRQE chain corrupted.

System actionIssue message EVE171E. Dump transaction storage.Ignore all RQEs that currently exist, which may resultin several EVE176E messages later.


System programmer responseThis problem is caused by a transaction that alteredstorage in the CICS address space, or by a CICSAutomation logic problem. Determine the cause of theproblem. If the problem is caused by a CICSAutomation logic problem, contact your IBM SupportCenter.

ModuleEVESPPIC.

C980

ExplanationUndefined error code.






ModuleEVESPERR.

C990

ExplanationUndefined message ID.




ModuleEVESPMSG.





Chapter 5. Messages EVI022I to EVI844A (IMSautomation)

Messages generated by IMS automation are built from the DFS, and DXR messages issued by IMS/VS, inaddition to the AVM, IOS, and IEF messages issued by the MVS Availability Manager, the Input/OutputSupervisor, and the MVS Job Scheduler respectively.

IMS automation supports the NetView Help Message command (HM). By entering HM plus the message IDon 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 operatorentries in the control file need to have these message classes defined in the CLASS= parameter.

EVI022I Bad return code retcode fromroutine.

ExplanationIMS automation issued an internal command or macrocall and received a non-zero return code. This mayindicate an internal error.

The variable retcode shows the return code.The variable routine shows the command, moduleor macro name that issued the return code.



System programmer responseCheck the return code of the indicated routine and anyassociated messages on the system log and NetLog.Contact your IBM Support Center for furtherassistance.

ClassesNone.

EVI030I resource not defined to SystemAutomation

ExplanationOne of the SA z/OS commands was entered against adependent region that is not defined to SA z/OS.

The variable resource is the name of the resourcethat is unknown to SA z/OS.

System actionThe system does not process this action and stopsprocessing multiple actions.

Operator responseCorrect the action character if it was enteredincorrectly 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 /STOPREGION commands for the dependent region.

ModuleEVIRYDP0

ClassesNone.

EVI031I resource cannot process action &2

ExplanationThis message may be issued for the following reasons:

1. One of the actions entered against a dependentregion cannot be processed by that dependentregion. This is usually due to an /ASSIGN against adependent region that has no classes.

2. One of the actions entered against a resource in theTCO list cannot be processed by the resource type.This is usually due to issuing a LOAD requestagainst the LTERM, or issuing a START or STOPrequest against a MEMBER resource.

The variable resource is the name of the resource.The variable &2 is the action.

Messages EVI022I to EVI844A (IMS automation)


System actionThe system does not process this action and stopsprocessing multiple actions.

Operator responseUse the appropriate line command against theappropriate resource type.

ModuleEVIRYTCO

ClassesNone.

EVI326I No TCO definitions found.

ExplanationWhen attempting to issue the requested command(s)for the TCO option selected by the operator, theprocess was unable to find any entries in the controlfile for this request.

System actionThe request is denied.

Operator responseNotify your system programmer that the functionselected is not defined in the control file.

System programmer responseVerify that the control file contains the required entriesfor the function selected by the operator.

EVI350I TCO HAS NOT BEEN INITIALIZED,REQUEST REJECTED

ExplanationA TCO function has been attempted and TCO is notsupported by this IMS at this time.

System actionThe request function is not executed.

Operator responseEnsure that the IMS that is associated with the requestis active. Use option 1, inquiry, from the IMSautomation panels to find out. If it is active, check with

your system programmer to ensure that this IMS hasbeen setup to include IMS TCO support.

System programmer responseEnsure that the IMS associated with the TCO requesthas been setup to include IMS TCO support. Forexample, IMS uses 2 logical terminals, as well as a DDstatement in the IMS startup PROC to support TCOrequests to start, stop, and load a TCO member.

EVI421I Request ignored, 'IMS' is not up.

ExplanationThe requested action is invalid because IMS is not up.

Operator responseStartup the IMS subsystem. After a successful startup,retry the request.

EVI706E Syntax error - parameter"parmtype" = "parmvalue".msgtext

ExplanationInvalid value specified in the Automation control filemember for keyword (refer to PARAMETER value inEVI706E message).

System actionThe CLIST is terminated.


System programmer responseCorrect the value for the parmtype keyword in thepolicy and refresh the configuration.

Classes40, 47, 60.

EVI844A subsystem RESYNC FAILURE -UNABLE TO COMPLETE commandCOMMAND

ExplanationThis message indicates that a problem occurred duringIMS resynchronization processing.

The variable subsystem shows the name of the IMSsubsystem.



The variable command shows the failed command.

System actionThe resynchronization processing may be incomplete.

Operator responseReview the netlog for errors. Report the problem toyour system programmer.

System programmer responseBrowse the netlog to determine the cause of the error.

Classes0, 40, 60.


Chapter 5. Messages EVI022I to EVI844A (IMS automation) 195



Chapter 6. Messages EVJ000I to EVJ440I (TWSAutomation)

EVJ000I date time module ENTRY/EXITparms/RC=rc

ExplanationWhen the trace option is activated, TWS Automationwrites this data to the log for entry and exit tracing.The date is shown in the format mm/dd/yyyy.


EVJ001I command: STARTED,PARMS=parameters

ExplanationCommand processor has been entered with theparameters shown. This is an informational messageissued for audit purposes.

System actionNone.



DestinationCommand processor name, parameters.

EVJ002I command: COMPLETEDSUCCESSFULLY, PARMS=parms

ExplanationCommand processor has completed successfully. Thisis an informational message issued for audit purposes.

System actionNone.



DestinationCommand processor name, parameters.

EVJ003E command UNABLE TO PROCESSPARMS=(parameters),REASON=reason

ExplanationOPC has initiated a request, but it cannot be processeddue to the reason shown. This message will normallybe preceded by a message giving specific details of thefailure.

System actionThe request is canceled.

Operator responseReview log for other messages.

System programmer responseResolve any system or definition problems, then resetthe request.

DestinationRequest parameters, reason text.

EVJ005E module UNABLE TO OBTAINparameter

ExplanationThe module indicated tried to obtain the value of aparameter from product globals, but the value was nullor not as expected.

System actionThe module ceases processing and returns a non-zeroreturn code to its calling routine.


Operator responseReview log for other messages and notify your systemprogrammer.

Determine the source of the failure, typically anincorrect control file value or failure of the productinitialization routines (beginning with EVJEAAIC) torun, and correct it. Call IBM Service if you requireassistance.

DestinationModule name and failing parameter

EVJ006E cmdname COMMAND FAILED FORmodule: RETURN CODE=rcPARMS=parms

ExplanationA command issued within this command processorreceived an invalid return code.

The variable cmdname shows the name of thecommand that failed.The variable module shows the name of the callingcommand processor.The variable rc shows the return code from thefailing command.The variable parms shows the parameters passedto the failing command.

System actionThe command processor terminates and logs an errormessage.

Operator responseReview the error messages in the NetView and MVSlogs.

System programmer responseReview the associated error messages in the NetViewand MVS logs. If necessary, correct definitionproblems and retry the operation.

EVJ007E SUBSYSTEM subsys IN INVALIDSTATUS stat FOR REQUEST(request)

ExplanationTWS Automation has attempted to execute therequest for the indicated subsystem, but was unable tocomplete because the subsystem was in an invalidstatus. For example, trying to start a subsystem that isalready up, or stop a subsystem that is already down.

System actionThe operation in OPC is posted in error with a U001status.

Operator responseReview NetView log for prior activity for thesubsystem.

Check for manual intervention with the subsystem,such as starts and stops performed outside ofautomation control. Also, for shutdowns, specifyRESTART=CTL so that subsystems will not be restartedby NetView initializations.

DestinationCommand processor name, subsystem, subsystemstatus, TWS Automation request type.

EVJ008E OPERATION ALREADY INPROGRESS FOR subsys,REQUEST=(reqparms)

ExplanationTWS Automation has attempted to execute therequest for the indicated subsystem, but was unable toprocess because a previous request is still outstandingfor the subsystem, or the previous request may nothave completed successfully.

The variable subsys shows the name of thesubsystem involved.The variable reqparms shows the details of theprevious request.

System actionThe new operation, indicated by additional messageEVJ003E is posted in error with a U005 status.

Operator responseReview NetView log for prior activity for thesubsystem.

Check for previous errors in the log, or review TWS andworkstation definitions. When problems are resolved,reset the TWS status file record using OPCAQRY andrerun the operation.

EVJ009E NO RESPONSE FROM SYSTEMdomainid WHILE SENDINGREQUEST (request)


ExplanationTWS Automation has attempted to forward the requestto the remote domain, but did not receive anacknowledgment from that system.

System actionThe operation in OPC is posted in error with an S999status.

Operator responseCheck status and connectivity of the system inquestion. If the problem can be resolved, rerun thefailing operation.

Your gateway to the remote NetView is blocked, or theremote system may be extremely busy. If the former,you should resolve the gateway problem. If the latteryou should schedule your operations on this remoteNetView farther apart.

DestinationDomain ID, request parameters.

EVJ010I variable data

ExplanationThis message is used internally to transfer databetween systems.

System actionNone, this is a normal message.


DestinationDate, time, message text.

EVJ011I date time OPC message text

ExplanationWhile attempting to communicate with OPC, anoperator initiated request to display or modify data hasfailed. The message text is the OPC message received.This message is normally preceded by anothermessage, indicating the TWS Automation module thatwas attempting to request data from OPC.

System actionNone.

Operator responseReview message in the appropriate OPC/ESA or OPC/Amanual.

Correct problems such as incorrect definitions of OPCsubsystem name.

DestinationDate, time, message text.

EVJ025E INVALID VALUE "value" FORkeyword

ExplanationThe parameter you have supplied is not valid.

System actionNone.

Operator responseTry again using the correct parameters.

EVJ026E MISSING PARAMETER parameter

ExplanationThe parameter is required, but was omitted.

System actionNone.

Operator responseTry again using the correct parameters.

EVJ029I command ENCOUNTEREDUNEXPECTED EVENT event_name

ExplanationThe indicated command was issued, but the responsereceived was not as desired. For example, thecommand may have timed out, or the procedure mayhave been canceled while waiting for a message.

System actionNone.

Operator responseInvestigate the cause of the failure.

EVJ040I PROCESSING COMMANDS

Chapter 6. Messages EVJ000I to EVJ440I (TWS Automation) 199

ExplanationThe TWS Batch Command Processor is starting.

System actionNone.


EVJ041E POSITIONAL PARAMETER nameMUST BE SPECIFIED

ExplanationThe parameter mentioned in the message is requiredand must be specified.

System actionBatch command processing aborts and the batch jobends with RC=16.

Operator responseCorrect the EVJRYCMD command and retry.

EVJ042E PARAMETER name ERROR, VALUENOT NUMERIC

ExplanationThe value specified in parameter name is not numeric.The value must be a number.


Operator responseCorrect the EVJRYCMD command and retry.

EVJ043E PARAMETER name ERROR,information

ExplanationThe value of the named parameter is incorrect.

The variable name represents the parameter inerror.The variable information contains the detail of theerror.



System programmer responseEnsure that the PPI destination named is 1 to 8characters in length and consists of alphanumericcharacters.

EVJ044E PARAMETER TRACE ERROR,INVALID VALUE - SEE THE REXXTRACE COMMAND

ExplanationSpecification of the TRACE= parameter requires avalue consistent with the REXX Trace command.



System programmer responseCheck with your IBM Support Center. Re-specify theTRACE= parameter with the correct value.

EVJ045I OPENING PPI INTERFACE FROMsource TO destination

ExplanationCommand Processing is about to send commands tothe SA z/OS PPI command processor. This message isissued when the PPI interface is being opened.

The variable source is the PPI Sender id used forthis batch job.The variable destination is the PPI receiver name ofthe command server. It is specified with theSERVER= parameter.





EVJ046E UNABLE TO OPEN PPI FORreceiver_name

ExplanationAn attempt to open the PPI receiver namedreceiver_name failed. This message is followed byEVJ047I that describes why the attempt to openfailed.

System actionCommand processing is aborted and the batch job willterminate with return code 20.


System programmer responseCheck message EVJ047I to find the probable cause ofthe error.

EVJ047I dsiphone_error [, PPI reasonppi_error]

ExplanationThis message provides details of the NetViewDSIPHONE error that caused processing to fail. It alsogives details of the PPI error reason if that is feasible.

The DSIPHONE error responses are:

• DSIPHONE called without arguments.• Too many parameters for this request type.• Too few parameters for this request type.• Invalid request type.• REXX stem or variable name too long.• REXX variable operation failed.• PPI receiver name is too long.• PPI request failed.• Stem's .0 element invalid.• Too many elements in stem.• First line of MLWTO not control line.• Invalid WAIT interval specified.• Argument 6 is not 'APPEND' or blank.

• PPI RECEIVE timed out.• Invalid MLWTO line type attribute.• Invalid MLWTO attribute length.• Unable to obtain storage.• Invalid attempt to call DSIPHONE from NetView.• Invalid attempt to call DSIPHONE.• Internal error.• An unknown error occurred.

The PPI error responses are:

• The specified receiver is not active.• The PPI is available.• The receiver program is active.• The receiver program is inactive.• The receiver program is already active.• The receiver ECB is not zero.• The request code is not defined.• The program is not in Primary Addressing mode.• The program is not authorized.• The PPI interface is not active.• The ASCB address is not correct.• The receiver program is not defined.• No active SSI for PPI found.• No data buffer in receiver buffer queue.• Receiver buffer is not large enough.• No NetView storage available.• Buffer length is not valid.• Receiver queue is full.• ESTAE recovery cannot be established.• Sender or Receiver ID not valid.• Processing error has occurred.• System abend occurred.• User abend occurred.• AIFR or the input length was not valid.• Could not identify the data as a message.• Incomplete multiline message was discarded.• Illegal alert forwarding loop was detected.• Specified target type does not support the data.• User is not authorized.• An unknown error occurred.

Numeric codes may also be present for either theDSIPHONE code or the PPI code.


System actionCommand processing is aborted and the batch jobterminates with return code 20.


System programmer responseFor some of the PPI error responses action can betaken to correct the error:

• "PPI receiver not defined" is usually due to anincorrect SERVER= specification.

• "PPI interface not active" or "No active SSI" isusually due to no NetView SSI subsystem havingstarted.

Most of the other reasons will require you to contactyour IBM Support Center.

EVJ048I EXECUTING COMMAND

ExplanationCommand processing is about to send a command toSA z/OS for processing.




EVJ049E UNABLE TO SEND TO destinationFOR source / EVJ049E UNABLE TORECEIVE FROM destination

ExplanationPPI processing failed to send data from the source tothe destination PPI receivers, or receive data from thedestination PPI receiver.

The variable source is the PPI Sender Id for thisbatch job.The variable destination is the PPI receiver name ofthe command server and is specified with theSERVER= parameter.

This message is followed by EVJ047I or INGPC028I todescribe the problem in more detail.

System actionProcessing is aborted and the batch job is terminatedwith return code 20.


System programmer responseRefer to the information in the following EVJ047Imessage and take any appropriate action.

EVJ052E PPI INTERFACE FAILED TO CLOSEFOR source

ExplanationThe PPI interface did not successfully close aftercommand processing was completed.

The variable source is both the PPI receiver nameof the batch job and the job name of the batch job.

System actionCommand processing is aborted and the batch job isterminated with return code 20.


System programmer responsePossibly no action. Check whether commands thatwere issued by the batch job executed correctly on theNetView by examining the NetView log.

EVJ053I BATCH COMMAND RECEIVEDFROM userid JOBNAME jobname

ExplanationAn OPC batch command has been received from abatch job and is to be executed on this NetView.

The variable userid shows the user ID of the userwho submitted the batch job.The variable jobname is the job name of the batchjob.

System actionThe command specified in message EVJ054I isprocessed.




EVJ054I BATCH COMMAND IS command-text

ExplanationAn OPC batch command has been received from abatch job and is to be executed on this NetView. Thismessage logs the command to be executed.

The variable command-text shows the batchcommand.

System actionThe command is processed.



EVJ055I PIPE PPI FOR receiver FAILED.RC=returncode - description

ExplanationA PIPE PPI command failed when attempting tocommunicate with the receiver.

The variable returncode shows either the returncode from the PIPE command or the return codefrom the PPI stage.The variable description shows a description of theerror.

System actionThe output from the current command received fromthe 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 someother error.

Operator responseFor recoverable errors such as errors with the receiver,resubmit the batch job if you are allowed to rerun thefailed batch job. For all other errors notify your systemprogrammer.

System programmer responseReport the error to your service representative.

EVJ056E Command return code nn greaterthan MAXRC mm - CommandProcessing Aborted.

ExplanationA command sent to the SA z/OS agent for processinghas executed and returned with a code greater that themaximum acceptable return code.

The variable nn shows the return code from thecommand.The variable mm shows the maximum acceptablereturn code from the MAXRC parameter of theEVJRYCMD command.

System actionThe batch interface will stop sending commands to theSA z/OS Agent and will terminate. The return code forthe batch job step will be determined by the HIGHRCparameter.

Operator responseFor recoverable errors, such as errors with thereceiver, resubmit the batch job if you are allowed torerun the failed batch job. For all other errors notifyyour system programmer.

System programmer responseIf this is not a user-defined situation, report the faultto your service representative.

EVJ060I Executing command forADID=name WSID=identifierOPNUM=nnn IATIME=timestamp>> command_text

ExplanationA command has been received from TWS and is to beexecuted on this NetView. This message logs thecommand to be executed. Note that the commandmight be truncated if it is too long.

The variable name shows the applicationdescription identifier as defined in TWS.The variable identifier shows the workstationidentifier.The variable nnn shows the TWS operation number.The variable timestamp shows the input arrival timeas determined by TWS.The variable command_text shows the command.





EVJ061I Command for ADID=nameWSID=identifier OPNUM=nnnfailed IATIME=timestamp RC=nn

ExplanationA command received via the TWS interface wasexecuted but reported a non-zero return code. See thepreceding message EVJ060I for the command in error.

The variable name shows the applicationdescription identifier as defined in TWS.The variable identifier shows the workstationidentifier.The variable nnn shows the TWS operation number.The variable timestamp shows the input arrival timeas determined by TWS.The variable nn shows return code from thecommand.

System actionNone.



EVJ062I REQUEST for wsname adnameopnum iatime purged

ExplanationWhile performing a configuration refresh, Systemautomation detected that a deleted resource wasinvolved in TWS request. Since the resource is nolonger under control of SA z/OS the request is removedfrom the internal control structure.

Variable wsname identifies the workstation nameinvolved.Variable adname identifies the application nameinvolved as defined in TWS

Variable opnum specifies the operation numberVariable iatime specifies the input arrival timeassigned to the request.



EVJ063I Command for ADID=nameWSID=identifier OPNUM=nnnIATIME=timestamp finished.ERRCODE=errcode

ExplanationA command received via the TWS interface wasexecuted and finished. See the preceding messageEVJ060I for command that was executed.

The variable name shows the applicationdescription as defined in TWS.The variable identifier shows the workstationidentifier.The variable nnn shows the TWS operation number.The variable timestamp shows the input arrival timeas determined by TWS.The variable errcode shows the error code for theoperation if the operation is in error, or the returncode if the operation is complete.

System actionNone.



EVJ100I EVJ07001: ENTERING SA z/OSTWS/OPC EXIT

ExplanationTWS has now called the EVJ07001 exit.

System actionNone.


Operator responseInformation message.

System programmer responseInformation message.

DestinationNone.

EVJ101I EVJ07001: DATA SENT=data

ExplanationThis message logs the data sent to NetView across theNetView PPI in the system log.

System actionNone.



DestinationData passed.

EVJ102I EVJ07001: PPI REQUEST nnFAILED, RC=rc

ExplanationEVJ07001 was unable to complete a NetView PPIrequest. See the NetView PPI manual for moreinformation on this request type and return code.

System actionTWS operation will be set to E status.

Operator responseReview error message in log.

System programmer responseReview error message in log.

DestinationRequest type and return code.

EVJ103I EVJ07001: GETMAIN FORWORKAREA FAILED

ExplanationEVJ07001 was unable to do a GETMAIN for work areastorage.

System actionEVJ07001 will put the TWS operation in E status.


System programmer responseReview NetView storage allocation and usage.

DestinationNone.

EVJ104I EVJ07001: OPC BAD OPERDESC:data

ExplanationEVJ07001 has found the contents of the operationdescription field to be invalid. Message EVJ105I willlist the actual error data.


Operator responseInform TWS Scheduler of possible definition error.


DestinationTWS application name.

EVJ105I EVJ07001: OPC DATA data

ExplanationEVJ07001 has found this data to be invalid.



Operator responseInform TWS Scheduler of possible definition error.


DestinationData.

EVJ106I modname1: modname2 STATUSUPDATE FAILED, RC=rc

ExplanationThe module listed was unable to update operationsstatus using DRK/EQQUSINT.

System actionWTO error message is issued.

Operator responseInform TWS schedulers and system programmers.

System programmer responseReview system and TWS/OPC message logs.

DestinationIssuing module and status update module.

EVJ107I EVJ07001: TWS/OPC FEATUREEXIT ENDED

ExplanationEVJ07001 has successfully ended.

System actionNone.



DestinationNone.

EVJ108I module-name UNABLE TO LOADMODULE CNMCNETV

ExplanationThis message is issued from the TWS status changeexit, (EQQUX007/DRKUX007), when it cannot load theNetView PPI interface.

System actionProcessing for this request halts. The operation will beposted in error with a return code of UNTV.


System programmer responseThis message most likely indicates an installationerror. You must make the NetView PPI moduleaccessible to TWS, either by STEPLIB or putting theNetView load library, CNMLINK, in LINKLST.

DestinationIssuing module name.

EVJ109I EVJ07001: LEAVING SA Z/OSTWS/OPC EXIT

ExplanationEVJ07001 has successfully ended.



DestinationModule name and successful command name.

EVJ110I modulename UNABLE TO LOADMODULE target-module-name

ExplanationThis message is issued from an TWS commandprocessor, which is unable to find or load an TWSinterface module.


System actionProcessing for this request halts.


System programmer responseThis message most likely indicates an installationerror. You must make the TWS interface moduleaccessible to NetView, either by STEPLIB (preferred)or by putting the TWS load library in LINKLST.

DestinationIssuing module name and target module name.

EVJ120I applid iatime opnum job statuswsname errcode abcode usrcodejob# stepname

ExplanationA TWS operation has been put into TWS error status orhas been reset from TWS error status. This causes aStatus Display Facility (SDF) update. For an operationchanging to error status the update will add an entry toSDF, while an operation changing from error status willremove an entry from SDF. SDF entries are added tothe 'OPC Automation Application in Error' panel(OPCERR). When enabled, alerting for the specifiedevent notification targets will occur.

The variable applid shows the TWS applicationname.The variable iatime shows the TWS input arrivaltime.The variable opnum shows the TWS operationnumber.The variable job shows the TWS job name.The variable status shows the TWS status.The variable wsname shows the TWS workstationfor 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'sstepname.

System actionSDF is updated according to the data displayed in themessage and when enabled, an alert for eventnotification targets will be generated.



EVJ121I Application jobname opno NOTRESET BECAUSE TIME LIMITEXCEEDED

ExplanationThis operation was found to be in error status in OPCwith error code, UNTV, indicating that the NetViewinterface was unavailable at the time it came READY.Now that the interface is available, the status was notreset because more time has elapsed since the failurethan is permitted by the OPRESET value in the controlfile (see ENVIRON OPCAO).

System actionOperation remains in error status.

Operator responseManually reset operation when appropriate. OPCACMDmay be used to do this.

System programmer responseDetermine whether the OPRESET value should beincreased.

DestinationApplication name, Job name, Operation number.

EVJ122E UNKNOWN TWS API SEGMENTsegment ENCOUNTERED

ExplanationWhen the INGTWS command is decoding datareturned from TWS via the API, an unknown segmentname was encountered.

The variable segment shows the name of thesegment that is unknown to the command.

System actionData from the TWS API is not successfully decoded.The command will present data that has been decodedup to the point of the failure.



System programmer responseReport the error to your service representative.

EVJ123I [DEFAULT SAFE|UPDATEPARAMETER] INVALIDMODIFICATION PARAMETERSFOLLOW:

ExplanationFor an INGTWS REQ=MOD request an invalid updateparameter was encountered that the command couldnot process. The source of the parameter in error iseither the Default Safe for the DEFAULT SAFE versionof the message or the UPDATE command parameterfor the UPDATE PARAMETER version of the message.Message EVJ124I follows this message with a list ofup to five parameter names that are in error.


Operator responseCorrect the incorrect parameter and reissue thecommand.


EVJ124I parm1 parm2 parm3 parm4 parm5

ExplanationThis message follows message EVJ123I and specifiesup to five parameter names that are in error.

System actionNone.

Operator responseCorrect the incorrect parameter/s and reissue thecommand.


EVJ125I subsystem IS NOT AN ACTIVECONTROLLER OR A TRACKER

ExplanationThis message is issued when INGOPC cannot resolvethe resource specification to an active controller or toan available tracker.

System actionNone.

Operator responseCorrect the incorrect parameter (or parameters) andreissue the command. Make sure that the resourcespecification will resolve to an active AvailableController or an Available Tracker.


EVJ201I EVJTOPPI: TASK IS ACTIVE

ExplanationNetView optional subtask initialization has completedsuccessfully.

System actionNone.



DestinationNone.

EVJ202I EVJTOPPI: PPI TO EVJTOPPIINITIALIZED

ExplanationNetView optional subtask has initialized its NetViewPPI queue.

System actionNone.




DestinationNone.

EVJ203I EVJTOPPI: PPI TO EVJTOPPIDEACTIVATED

ExplanationNetView optional subtask has deactivated the NetViewPPI queue.

System actionNone.



DestinationNone.

EVJ204I EVJTOPPI: TASK IS TERMINATED

ExplanationNetView optional subtask has terminated successfully.

System actionNone.



DestinationNone.

EVJ205E EVJTOPPI: PPI REQUEST nnFAILED, RC=rc

ExplanationEVJTOPPI was unable to complete a NetView PPIrequest. Refer to the NetView Application ProgrammingGuide: PPI for more information on the request typeand return code.

System actionNone.


System programmer responseReview log for messages that may indicate the reasonfor the failure. A possible reason is that NetView isbeing shutdown.

Note: The OPC operation status will be unchanged.User intervention may be required.

DestinationRequest type and return code.

EVJ206I EVJTOPPI: PPI DATA FROMEVJTOPPI DISCARDED

ExplanationEVJTOPPI received request data from a non-OPCsubsystem. The data is logged in the NetView log, butis not passed to EVJESPVY.

System actionNone.

Operator responseInformational. Review message EVJ214I for data.

System programmer responseInformational.

DestinationNone.

EVJ207I EVJTOPPI: DSIFRE FAILED FORUSER STORAGE

ExplanationEVJTOPPI was not able to FREE user storage beforeterminating.


System actionNone.

Operator responseReport problem to system programmer.

System programmer responseReview error.

DestinationNone.

EVJ208I EVJTOPPI: DSIFRE FAILED FORQUEUED STORAGE

ExplanationEVJTOPPI was not able to FREE queued storage beforeterminating.

System actionNone.


System programmer responseReview error.

DestinationNone.

EVJ209I EVJTOPPI: DSIGET FAILED FORUSER STORAGE

ExplanationEVJTOPPI was not able to GET user storage atinitialization.

System actionNone.


System programmer responseReview NetView storage allocation and utilization.

DestinationNone.

EVJ210I EVJTOPPI: DSILCS FAILEDTRYING TO GET A SWB

ExplanationEVJTOPPI was not able to GET a service work block.

System actionNone.


System programmer responseReview NetView storage allocation and utilization.

DestinationNone.

EVJ211I EVJTOPPI: ENQ ERROR

ExplanationEVJTOPPI was not able to perform an ENQUEUE.

System actionNone.


System programmer responseCheck for multiple EVJTOPPI tasks or possibledeadlock condition.

DestinationNone.

EVJ212I EVJTOPPI: DEQ ERROR

ExplanationEVJTOPPI was not able to perform a dequeue.

System actionNone.



System programmer responseCheck for multiple EVJTOPPI tasks started, or adeadlock condition.

DestinationNone.

EVJ213I EVJTOPPI: DSILCS FAILEDTRYING TO FREE SWB

ExplanationEVJTOPPI was not able to FREE a service work block.

System actionNone.


System programmer responseContact support center.

DestinationNone.

EVJ214I EVJTOPPI:xxxxxxxxxxxxxxxxxxxxxxxxx

ExplanationThis message is sent to the NetView log to documentthe discarded data.

System actionNone.

Operator responseInformational.


DestinationData.

EVJ300I EVJSAOPS: DRK/EQQUSINT POSTWAS SUCCESSFUL

ExplanationPost to OPC using DRK/EQQUSINT was successful.

System actionNone.

Operator responseInformational.


DestinationNone.

EVJ302I cmdname: INVALID KEYWORDSUPPLIED

ExplanationInvalid KEYWORD was issued when invoking thiscommand. Message EVJ303I will follow listing theKEYWORD and DATA in error.

Operator responseCorrect parameters used to invoke the command.

System programmer responseCorrect the command and retry.

DestinationCommand name.

EVJ303I cmdname: KEYWORD ERROR,KEYWORD(keyword) DATA(data)

ExplanationThis message gives the keywords and data that areinvalid when this command was invoked.

Operator responseReview parameters used to invoke the command.

System programmer responseModify parameters accordingly.


DestinationCommand name, keyword and data.

EVJ410I ADID JOBNAME WS OPNO S ERRCIA® OPTEXT

ExplanationThis is the first line of a multiple-line message. Itdisplays the titles for message EVJ411I.

EVJ411I applid jobname workstation opidstatus errcode IA_time text.

ExplanationThis is the second line of a multiple-line message. Itdisplays the corresponding information from messageEVJ410.

EVJ412I END OF REQUEST.

ExplanationThis message indicates the end of the data.

EVJ413I UNABLE TO FIND DATA FORREQUESTED LIST

ExplanationThis message is issued from OPCALIST or OPCACMDand indicates that no application or operation in thecurrent plan meets the combination of inputparameters specified.

System actionProcessing for this request halts.

Operator responseCorrect the input to the OPCALIST command or theOPCACMD panel. If it is not obvious which parameteris error specify fewer parameters and issue thecommand again, so that OPC may return a list of validapplication occurrences in the current plan. If thereare none go to the OPC dialog under ISPF and add anoccurrence.


DestinationNone.

EVJ424E COULD NOT LOCATE OPCCONTROLLER - reason

ExplanationThe OPC Controller as defined in the OPCA PCSautomation control file statement could not be locatedin either the local system or any of the systems in thelocal sysplex.

The reason variable (optional) shows the reason code.


Operator responseInvestigate the cause of the failure. Further diagnosticmessages may be available in the NetView log.Possible causes include:

• An error in the OPCA PCS statement in theautomation control file.

• The OPCA PCS defines the controller to be runningon another system.

• No OPC controller is running (UP status in SA z/OS)where specified.

EVJ425I NO SRSTAT ENTRY FOUND INOPCA PCS DEFINITION FOR OPCAUTOMATION.

ExplanationThe SRSTAT entry for the TWS Automation is not set.

OPCA PCS, SRSTAT=YES|NO|ALL

System actionNone.

Operator responseReport to your system programmer that the OPCA PCSstatement in the automation control file for settingspecial resources status was not defined. This entryallows TWS Automation to set OPC special resourcesfor the named job name in the OPCA OPCSRSTATdefinition.

System programmer responseRefer to IBM Z System Automation Workload SchedulerProgrammer's Reference and Operator's Guide forfurther information.


EVJ430I ADID JOBNAME WS OPNO S ERRCIA OPTEXT

ExplanationThis is the first line of a multiple-line message. Itdisplays the titles for message EVJ431E, as follows:ADID

OPC Application IDJOBNAME

MVS Job NameWS

OPC WorkstationOPNO

OPC Operation NumberS

OPC StatusERRC

OPC Error Return CodeIA

OPC Input Arrival TimeOPTEXT

OPC Operations Text

EVJ431E adid jobname ws opno s errc iaoptext

ExplanationThis is the continuation of a multiple-line messagebegun with EVJ430I.

DestinationThe inserts are as follows:adid

OPC Application IDjobname

MVS Job Namews

OPC Workstationopno

OPC Operation Numbers

OPC Statuserrc

OPC Error Return Codeia

OPC Input Arrival Timeoptext

OPC Operations Text

EVJ440I date day WORK|FREE.

ExplanationThis message tells you whether today is a work day ora free day in the OPC calendar. The date is shown inthe format mm/dd/yyyy.

Codes Posted to TWS by TWS AutomationOAUT

ExplanationIndicates that the EQQUXSAZ exit was not able to passthe request to the local SA z/OS using the NetViewPPI.

Rnnn

ExplanationThe command passed to SA z/OS for execution failed.nnn is the return code from the command. RXXX isused when the return code is >999.

S998

ExplanationJob not defined to any active system in sysplex. Arequest to run an operation from TWS was received by

TWS Automation. The control file mapped theworkstation (NVxx) to SYSPLEX. All active SA z/OSdomains in the local sysplex were queried but nodefinition was found for the job name specified in theTWS request.

This may be the result of one or more systems (or theirSA z/OS) being inactive or it may be a definition error.If all systems where the job is defined are offline thenthe operation will be retried when SA z/OS gatewayconnectivity is re-established.

S999

ExplanationGateway to remote NetView was unavailable. Arequest to run an operation from TWS was received bythe automation platform (NetView) address space, butit was destined for another NetView domain. Anattempt was made to forward this operation to thatdomain, designated by the workstation name in the

Codes Posted to TWS by TWS Automation


request, but this attempt failed. Either the gatewayfrom the local system to the remote domain was down,or no response was received from the remote systemafter waiting for one minute.

UNTV

ExplanationNetView unavailable. The TWS exit in TWS was unableto transmit this request to the automation platform(NetView) address space. Either the NetView in thesystem running the TWS/ESA Controller was down atthe time this request was initiated or the NetView SSIwas down.

U001

ExplanationInvalid status for the subsystem. The subsystem failedto start or terminate in the interval, or has changed toan unexpected status.

U002

ExplanationInvalid flag combination detected. This may indicateautotask definition errors. Review the NetView log foradditional information.

U003

ExplanationMissing or incorrect TWS Automation definitions in theAutomation control file or errors occurred reading thestatus file or executing an SA z/OS command such asINGREQ. Review the TWS policy definitions and checkthe netlog for additional messages.

U004

ExplanationConfiguration error: The EVTOPER is not defined. Thistask is used to process status change notificationsfrom the automation manager.

U005

ExplanationSequence Error. This is usually an indication of two ormore requests in progress for the same subsystem.Review the NetView log for additional information.

U006

ExplanationConfiguration Error. An Automation Configuration Filestatement of the type OPCA DOMAINID,CODE=specifies SYSPLEX. The TWS Controller is not runningin a system where SA z/OS Release 3 or later isinstalled. Use of the SYSPLEX keyword on thisstatement requires SA z/OS Release 3 or later to beinstalled where the TWS Controller runs.

U007

ExplanationExecution of the command is rejected by theinstallation exit AOFEXC20.

U008

ExplanationTimeout condition occurred while processing thecommand.

U009

ExplanationAn invalid parameter was found while processing thecommand passed from TWS.

U010

ExplanationThe completion information provided by exit AOFEX20is incorrect. See the Netlog for more details on thereasons.

Codes Posted to TWS by TWS Automation


Chapter 7. Messages HSAH001I to HSAL6999I

HSAH001I HSAET32 SERVICES verbCOMPLETE.

ExplanationProcessing of the command completed successfully.The SA-BCPii SNMP/ISQET32 or INTERNALconnections are affected.

The variable verb shows the name of the HSAET32command verb that completed successfully.

System actionService processing continues as requested by thecommand verb.



HSAH002I INVALID HSAET32 SERVICESREQUEST request.

ExplanationThe identified HSAET32 command is not valid. The SA-BCPii SNMP/ISQET32 or INTERNAL connections areaffected.

The variable request shows the name of theHSAET32 command that is not valid.

System actionNone.

Operator responseCorrect and reissue the command as necessary. Validservices are REBUILD, START, STATUS, DISABLE, andENABLE.


HSAH003I HSAET32 SERVICES REQUESTFAILED, RC=rc, REASON=rsn.

ExplanationAn error occurred during an attempt to process a validHSAET32 command. The SA-BCPii SNMP/ISQET32 orINTERNAL connections are affected.

The variable rc shows the return code that wasissued.The variable rsn shows the reason code that wasissued.

System actionNone.

Operator responseIssue an HSAET32 STATUS command and verify thatthe status reported by message HSAH004I is asexpected. Then reissue the command as appropriate.If the problem persists, notify your systemprogrammer.

System programmer responseThis message is issued with return code 8 and reasoncode 20 (14x) as a result of an HSAET32 STARTcommand if the HSAET32 services were startedpreviously (usually done during NetView initialization).If other problems occurred, contact your IBM SupportCenter.

HSAH004I HSAET32 SERVICES ARE status.

ExplanationThe variable status shows the current status ofHSAET32 services. The SA-BCPii SNMP/ISQET32 orINTERNAL connections are affected. The followingvalues can occur:INACTIVE

HSAET32 services were not initialized and areunavailable.

ENABLEDHSAET32 services were initialized and areavailable.

DISABLEDHSAET32 services were initialized but weredisabled from use.

System actionNone.

Messages HSAH001I to HSAL6288I


Operator responseVerify that the status indicated is as currently required.

System programmer responseIf the status value is INACTIVE, SA z/OS StartupHSAET32 initialization is in progress. MessageHSAH001I must follow, indicating that HSAET32SERVICES START is complete.

If this is not the case, check the netlog for additionalmessages indicating HSAET32 command problems,such as insufficient NetView operator commandauthorization. After the problem is corrected you cantry to restart the HSAET32 services manually, issuingthe IBM service command HSAET32 START, or recycleSA z/OS.

HSAL1071E CANNOT REGISTER OMVSSHUTDOWN OPTIONS,ERRNO=code1, ERRNO2=code2.

ExplanationThe 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 actionThe SA z/OS automation manager continues withinitialization.


System programmer responseExamine the error codes to determine why thefunction call failed. In most cases registration forOMVS shutdown fails because the automationmanager does not have superuser or equivalentauthority. Alternatively you may want to give theautomation manager read permission to theBPX.SHUTDOWN facility class profile.

HSAL1072I THE AUTOMATION MANAGER ISBLOCKING OMVS SHUTDOWN.

ExplanationIf an OMVS shutdown command is in progress theautomation manager will block the shutdown until theautomation manager is terminated with a STOP,DEFERor a manual STOP command.

This is because the parmlib option BLOCKOMVS is setto YES.

System actionThe automation manager continues processing.



HSAL1081I SWITCHING COMMUNICATIONFROM MQ TO XCF IS action.

ExplanationThe WebSphere MQ subsystem was stopped or anerror occurred in WebSphere MQ. The automationmanager runs on the last system within the XCF group.The automation manager continues running with XCFcommunication only rather than terminating andthereby forcing a takeover.

• The variable action may contain one of the followingvalues:STARTED

The switch from WebSphere MQ to XCF started.COMPLETED

The switch from WebSphere MQ to XCFcompleted.

System actionThe automation manager continues processing, butuses XCF for the communication between theautomation agent and the automation manager.



HSAL1082I SWITCHING COMMUNICATIONFROM XCF TO MQ IS action

ExplanationThe automation manager was started with XCFcommunication. WebSphere MQ is available and theautomation manager switches from XCF to WebSphereMQ communication.



• The variable action may contain one of the followingvalues:STARTED

The switch from XCF to WebSphere MQ started.COMPLETED

The switch from XCF to WebSphere MQcompleted.

System actionThe automation manager continues processing, usingWebSphere MQ communication.



HSAL1083I AUTOMATION MANAGER HASCREATED THE INITIAL POSIXTHREAD WITH PID @1

ExplanationThe automation manager has successfully created theinitial POSIX thread. The OMVS kernel has assignedthe specified process ID (PID) to the initial POSIXthread. If you do not see this message then theautomation manager is still waiting for OMVS to comeup. If the automation manager is running withsuperuser authority, the initial POSIX thread will becreated before OMVS initialization is completed.Otherwise the automation manager waits until OMVSinitialization is completed and message BPXI004Icomes up. This may require JES to be up.

System actionNone.



HSAL1091E INTERNAL ERROR TYPE error typeDETECTED. DIAGNOSTIC INFOMAY FOLLOW: P1=parm1P2=parm2 P3=parm3

ExplanationAn internal error was found. Up to three additionaldiagnostic information fields may be provided,depending on the error type.

• The variable parm1 shows what could not beprocessed.

• The variable parm2 shows the value of thecommand, action or termination type.

• The variable parm3 (optional) shows the firstparameter of the command.

• The variable error type shows a decimal number thatdefines the type of the error. The following valuescan occur:101

The thread manager got an invalid command,action or termination type that cannot beprocessed.

102Cannot create thread specific data object for themain thread.

103The class HsaSemaphore supports event andmutex semaphores. A method was applied for asemaphore type, that does not support thismethod.

The variable parm1 shows the semaphorename.

104The single MTIB object has not yet been created.

105The single MTIB object must not be created witha MTIBptr=zero.

106The factory tries to create a derived requesthandler but the function doCreateHandlerreturns zero.

The variable parm1 shows the handler name.

107It was attempted to add a factory into the factoryregistry. However, a factory with the same namehas already been added.

The variable parm1 shows the factory name.

108A null pointer was detected. Processing stops.

109It was attempted to find a factory within thefactory registry. However, the factory name is notcontained in the registry.

The variable parm1 shows the searchargument (=factory name).


Chapter 7. Messages HSAH001I to HSAL6999I 217

110It was attempted to access the factory registry.However, the factory registry has not yet beencreated and the static pointer to it is zero.

111Invalid attempt to reply to a RPC Handle thatdoes NOT have the response flag ON.

112Dtor of Request Handler Factory detects thatnumber of handlers is not zero.

The variable parm1 shows the factory name.The variable parm2 shows the number ofhandlers.The variable parm3 shows the ivCtorError.

113Request Handler Factory attempts to create ahandler but the factory error code ivCtorError isnot zero.

The variable parm1 shows the factory name.The variable parm2 shows the ivCtorError.

System actionThe SA z/OS automation manager terminates.



HSAL1092E INTERNAL ERROR TYPE error typeWITHIN THREAD thread nameDETECTED. DIAGNOSTIC INFOMAY FOLLOW: P1=parm1P2=parm2

ExplanationAn internal error was detected. Up to two additionaldiagnostic information fields may be provided,depending on the type of the error.

• The variable thread name shows the name of thethread where the error occurred.


The thread manager does not support to restarta thread after a thread has been terminated.

The variable parm1 shows the maximum retrycount of threads.

203A thread has been terminated and a restart iseither not possible or not allowed.

204The default implementation of a virtual functionwas called unexpectedly.

If specified the variable parm1 shows thecurrent timer.

205An attempt was made to add a thread with aduplicate thread name to the Registry.

206The system tried to find a collection classelement but the given key (=thread name) couldnot be found.

207Timer thread call handleExpiredTimer() aftercontrol was returned the timer has not beenreset correctly, for example, previous timer >=new timer.

The variable parm1 shows the previous timerspecified.The variable parm2 shows the new timerspecified.

208This exception is used if a thread has received arequest of class HsaRequest with a request typethat the function handleRequest cannot process.

The variable parm1 shows the request type.

209Function completeRequest() attempted to send arequest back to the creator thread. However, thethread name is NULL.

211LogonId not yet set or not valid.

The variable parm1 shows the logonID that isnot valid.

251The program detected an internal error thatprobably leads to thread termination.

252The program detected an error that leads tothread termination and takeover. Examine othermessages that may have been issued togetherwith this message, for example, INGY110, todetermine the cause of the error.





System programmer responseFor error type 252 try to fix the problem. For all othererror types, contact your IBM Support Center.

HSAL1093E COMMUNICATION OR SYSTEMSERVICE FAILED, ERRORTYPE=error type DIAGNOSTICINFO MAY FOLLOW: P1=parm1P2=parm2 P3=parm3 P4=parm4P5=parm5

ExplanationA system error was detected. Up to five additionaldiagnostic information fields may be provided,depending on the type of the error.


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 pthreadservice.The variable parm4 shows the current thread.The variable parm5 shows the semaphorename

302An attempt to get storage failed.

The variable parm1 shows the amount ofstorage in bytes.

303An attempt to perform an MVS system servicefailed.

The variable parm1 shows the name of theHSAAPIMV service.The variable parm2 shows the return code ofthe service.The variable parm3 shows the current thread.The variable parm4 (optional) shows the APIreturn code.The variable parm5 (optional) shows the APIreason code.

304An attempt to perform a Communication Servicefailed.

The variable parm1 shows the name of theHSAAPICO service.The variable parm2 shows the return code ofthe assembler stub.The variable parm3 shows thecommunication return code of the service.The variable parm4 (optional) shows thename of the current thread.


Operator responseNone


HSAL1094I THREAD thread name HASRECEIVED A Z/OS UNIXSIGNALsignal.

ExplanationThe signal handler got control due to a z/OS UNIXsignal. Any received z/OS UNIX signal that a signalhandler was registered for will terminate theautomation manager.

The variable thread name shows the name of thethread that received the signal.The variable signal shows the z/OS UNIX signal.



System programmer responseAnalyze the z/OS UNIX signal. If necessary, contactyour IBM Support Center.

HSAL1095I SUSPENDED THREAD thread nameHAS BEEN INTERRUPTED DUE TOA STOP REQUEST.

ExplanationThe threads have been suspended, for example, duringCONFIG load or REFRESH.



The variable thread name shows the name of thethread where the error occurred.

System actionThe SA z/OS automation manager terminatesabnormally.



HSAL1096I AUTOMATION MANAGERTERMINATION IN PROGRESS DUETO THREAD TERMINATION OREXCEPTION BY THREAD threadname

ExplanationA thread of the automation manager ends abnormally.

The variable thread name shows the name of thethread where the error occurred.



System programmer responseCheck the error message HSAL1093E, HSAL1904I, orHSAL1099I that are issued with this message fordetails of the error.

HSAL1099I any_text

ExplanationMessage HSAL1099I is a diagnostic message wherethe any_text variable is text of free format.

For example, this message might be issued to provideextra diagnostic information when the automationmanager is terminated due to an exception. Theany_text variable describes the exception.



System programmer responseCheck SYSLOG, SYSPRINT, SYSOUT, and CEEDUMP ofthe corresponding automation manager job for moredetails.

HSAL1101I DIAGINFO SNAPSHOT dsn HASBEEN CREATED

ExplanationA snapshot of all in-storage objects (state imagequeue) maintained by the automation manager hasbeen written into the named data set.

The variable dsn shows the name of the data setthat contains the snapshot.

System actionNone.



HSAL1102I DIAGINFO RECORDING INTO dsnHAS BEEN STARTED

ExplanationThe automation manager has started recording allreceived workitems into the named data set. Thisincludes writing the current state image queue into thedata set.


System actionNone.



HSAL1103I DIAGINFO RECORDING INTO dsnHAS BEEN COMPLETED



ExplanationThe automation manager has stopped recording allreceived workitems into the named data set.


System actionNone.



HSAL1104E DIAGINFO RECORDING INTO dsnHAS FAILED. REASON: reason

ExplanationThe automation manager detected an error whilerecording the received workitems into the named dataset. The cause of the error is indicated by the reasoncode.

The variable dsn shows the name of the data set.The variable reason shows the cause of the error.

System actionNone.

Operator responseCheck logs for other messages associated with thisevent 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 IBMSupport Center.


HSAL1105E IO OPERATION ON THE TAKEOVERFILE FAILED. REASON: diag_info.

ExplanationThe automation manager failed to access or use thetakeover file. The variable diag_info contains furtherdetails.

diag_info = "DSN=xxxxx: ALLOC ERROR nnnn RC=rr RSN=ssss"

The automation manager tried to allocate ordeallocate the takeover file xxxxx. If a dynalloc erroroccurs the variable diag_info provides an error codeand the dynalloc return and reason code.

Meaning of alloc or dealloc error codes:

n008 invalid dataset or member or dd-namen012 dynalloc errorn016 open errorn020 internal error

where n=1 means allocate and n=2 means deallocate.

Example:

diag_info = "ALLOC_ERROR 1012 RC=4 RSN=1056"

means allocation of the takeover file failed becausethe takeover file is already open.

For more details about dynalloc return and reasoncode refer to the chapter "Interpreting DYNALLOCReturn Codes" in MVS Authorized Assembler ServicesGuide.

For other types of diag_info see the followingdescription:

The automation manager tried to write or update thetakeover file. A file operation function failed.

• DSN= is the name of the takeover file.• The variable diag_info provides the following

information about the error:C library function

The file operation function that failed, forexample, fopen.

C library error codeThe error code issued by the file operationfunction (errno).

C library error messageThe error message text provided by the failingfile operation function.

For more details about errno for C/C++ libraryfunctions, see z/OS XL C/C++ Library Reference.

System actionThe automation manager continues running.



Operator responseCheck for I/O error messages and notify your systemprogrammer.

System programmer responsePerform a cold or warm start. Note that the automationmanager must not perform a hot-start or takeover,because the takeover file may be damaged or containold data.

HSAL1106I MQ OPERATION ON STATE QUEUEFAILED. REASON: reason.

ExplanationAn error occurred while accessing the MQ state queue.

The variable reason contains internal debugginginformation and the MQ action performed.

System actionThe automation manager stops updating the MQ statequeue but continues to maintain the resource statusin-storage and in the Takeover file.

Operator responseIf message HSAL1109I is previously issued, stop theMQ manager. This is necessary to avoid messageflooding because the automation manager attempts toaccess the MQ State queue periodically.

System programmer responseExamine the syslog for additional messages givingmore details about the cause of the error.

HSAL1107I REFRESH OF TAKEOVER FILEDSN=dataset_name WITHCURRENT AUTOMATION.

ExplanationThe automation manager starts updating the takeoverfile with the in-storage data maintained for eachresource. The first step is erasing the current data inthe takeover file. The second step is writing the in-storage data into the takeover file.

The variable dataset_name is the name of thetakeover file.

System actionNone.



HSAL1108I REFRESH OF TAKEOVER FILEDSN=dataset_name COMPLETED.

ExplanationThe automation manager has completed writing the in-storage resource data to the takeover file. The contentof the takeover file is now identical with the in-storageresource data.


System actionNone.



HSAL1109I REFRESH OF AUTOMATIONMANAGER DATA TO MQ STATEQUEUE STARTED

ExplanationThe automation manager started refreshing the MQState queue with the in-storage data maintained foreach resource. This process consists of the followingtwo steps:

1. Purging the MQSeries® State queue2. Updating the MQSeries State queue with the

resource data

System actionNone.





HSAL1110I R15 VALUE = rc REASON CODE = rsRBA = rba LAST OP = lastopEXPECTED RECORD SIZE = rsizeREPORTED IO RESULT = asize

ExplanationThe automation manager has had a VSAM I/O error.

The variable rc shows the VSAM return codeThe variable rs shows the VSAM reason code.The variable rba shows the VSAM relative byteaddress.The variable lastop shows the last I/O operationexecuted.The variable rsize shows the expected number ofbytes to be read in the I/O operation.The variable asize shows the actual number ofbytes read in the I/O operation.

System actionAdditional error message will be issued.


System programmer responseContact IBM for support.

HSAL1111I DISABLING OF TAKEOVER FILEDSN=dataset_name COMPLETED

ExplanationThe automation manager has freed the takeover fileand stopped writing to it.


System actionNone.



ClassesNone.

HSAL1113I WORKITEM EXPIRED:thread_name DATE:exp_dateTIME:exp_time SIG:wi_signature

ExplanationThe workitem has passed its expiry time.

The variable thread_name is the name of thethread.The variable exp_date is the expiry date of theworkitem.The variable exp_time is the expiry time of theworkitem.The variable wi_signature is the workitemsignature.

System actionNone.


System programmer responseTry to determine reason for expiry, for example, highsystem or automation manager activity. Examine thenetlog for additional information.

HSAL1115I START PROCESSING THESUSPEND FILE dataset_name

ExplanationThe automation manager starts reading the suspendfile. This is the first of two steps. The first stepprocesses the data set and analyzes the syntax of thedata in this data set. The second step applies the datafrom this data set and updates the data set.

The dataset_name variable is the name of thesuspend data set.

System action:None.



HSAL1116I CHECKING THE SUSPEND FILEdataset_name HAS BEENCOMPLETED

ExplanationThe automation manager has completed checking thesuspend file. If no further errors have occurred, the



automation manager will continue to apply the datafrom this data set.


System action:None.



HSAL1117I PROCESSING THE SUSPEND FILEdataset_name HAS BEENCOMPLETED

ExplanationThe automation manager has finished processing thesuspend file.


System action:None.



HSAL1118I UNABLE TO ALLOCATE THESUSPEND FILE dataset_name,ERROR CODES: REASON=code1INFORMATION=code2

ExplanationThe SA z/OS automation manager was unable todynamically allocate the named suspend file. The dataset name could not be allocated, or is not a sequentialfile, or not a partitioned data set member.

The dataset_name variable shows the name of thesuspend file that could not be allocateddynamically.The code1 and code2 variables respectively showthe error reason code and error information codefrom the failing DYNALLOC. For further analysis, seeInterpreting DYNALLOC return codes.

System action:The SA z/OS automation manager cancels the refreshprocess.


System programmer response:

Check whether the data set name is correct. Thesuspend file is specified in the SUSPENDFILEparameter within the parmlib member in HSAPRMxx.

HSAL1120I ERROR(S) IN SUSPEND FILE

ExplanationSyntax error(s) have been detected in the suspend file.The following data lines might be displayed:

INVALID PARAMETER parm IN LINE line_number

INVALID VALUE value FOR PARAMETER parm INLINE line_number

MISSING VALUE FOR PARAMETER parm IN LINEline_number

The parameter parm in line line_number is invalid.Only the parameters SCOPE=ONLY|ALL andREMOVE=NO|SYSGONE are allowed.

The parm variable is the name of the erroneousparameter.The value variable is the erroneous value that wasspecified for the valid parameter parm.The line_number variable is the number of theerroneous line in the suspend file.

INVALID RESOURCE NAME res_name IN LINEline_number

The resource name res_name specified in lineline_number is invalid. Only resources of type APL,APG, MTR, and REF are supported.

The res_name variable is the name of the invalidresource.The line_number variable is the number of theerroneous line in the suspend file.

System action• For a configuration refresh, the processing of the

suspend file is canceled.• For a manager COLD or WARM start, the processing

pauses until a WTOR is answered by selecting how toproceed with the syntax errors.


System programmer responseCorrect the errors in the suspend file.

• For a configuration refresh, you can ignore the errorsor the whole file using the INGAMS or MVS Modifycommand.

• For a manager COLD or WARM start, you can ignorethe errors or the whole suspend file by answeringthe WTOR. See message HSAM1318D for details.



https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa800/dynrtcd.htm

HSAL1121I RESOURCES TO BE SUSPENDED

Explanation:For the following resources, a suspend request withthe listed parameters is scheduled.

System action:The automation manager schedules a suspend requestfor the resources.



HSAL1122I RESOURCES NOT SUSPENDED

Explanation:The following resources are not part of theconfiguration file and suspension is ignored. They arenot going to be suspended.

System action:The automation manager ignores the non-existingresources for the further processing of the suspendfile.


System programmer response:Check that the resources are defined in theconfiguration file and the resource names are correctin the suspend file.

HSAL1300E TIMER REQUEST IS INVALID:RC=rc, TYPE=type,CREATOR=creator

ExplanationThe validation of an internal timer request failed with areturn code.

The variable rc shows the value of the return code.The variable type shows the type of the request.The variable creator shows the creator or therequest.




ModuleHSACMTMR

HSAL1301E INVALID REQUEST RECEIVED:TYPE=type, CREATOR=creator.

ExplanationAn LE component received a request of a type thatcould not be processed.

The variable type shows the type of the request.The variable creator shows the creator or therequest.


Operator responseContact your IBM Support Center.


ModuleHSACMTMR , HSAHNDLS

HSAL1400E OVERRIDE FILE NOT AVAILABLE.FUNC=function, CODE=errorcode.

ExplanationThe variable function shows the function that couldnot be performed.The variable errorcode shows the value of the errorcode that was issued (return code bytes 1-4 andreason code bytes 5-8).

System actionThe override file is marked unavailable. All requestsquerying or manipulating any overrides are rejected.Existing base schedules are still working as defined inthe customization dialogs.


System programmer responseAnalyze the function code by referring to the OS/390®

LE environment STDIO.H file. The errorcode can beanalyzed by referring to OS/390 DFSMS



Macroinstructions for Data Sets using the return andreason codes from the error code. If the problem issolved, start a secondary automation manager andinitiate a takeover. If you cannot resolve the problemcontact your IBM Support Center.

ModuleHSACMSST

HSAL1401E TIMER REQUEST FAILED. RC=rc,ORIGINATOR=name,REQUEST=req.

ExplanationA timer request has been returned with an unexpectedreturn code to the LE component that is responsiblefor schedules.

The variable rc shows the return code that wasissued.The variable name shows the name of theoriginator.The variable req shows the name of the request.

System actionThe request is ignored. This may lead to anunexpected behaviour of the affected schedule.



ModuleHSAHNDLS

HSAL1402E WORKITEM COULD NOT BEQUEUED. RC=rc.

ExplanationThe LE component responsible for schedules could notinform the component managing the resources aboutthe begin or the end of a service period.

The variable rc shows the return code that wasissued.

System actionProcessing continues. However, this may lead to anunexpected behaviour of the affected resource(s).

Operator responseInitiate® a takeover to a secondary automationmanager. If the problem persists notify your systemprogrammer.


ModuleHSACMSST, HSACMTMR

HSAL1403I A TIMER EXPIRED FOR resourceTHAT IS NO LONGER AVAILABLE.

ExplanationThe current and all future overrides of the resourcehave been deleted. Also, the current timer of theresource expired before it could be purged.

The variable resource shows the name of theresource.




ModuleHSACMSST

HSAL1404E A VSAM ERROR OCCURRED.RC=rc, RSNreason FUNCTION=function

ExplanationA function operation on the override file failed with areturn code and a reason code.

The variable rc shows the value of the return code.The variable reason shows the value of the reasoncode.The variable function shows the name of thefunction.



System actionThe override file is marked unavailable. All requestsquerying or manipulating any overrides are rejected.Existing base schedules are still working as defined inthe customization dialogs.


System programmer responseAnalyze the VSAM return code and reason code andcorrect the error condition. When the problem issolved, start a secondary automation manager andinitiate a takeover.

ModuleHSACMSST

HSAL1405I WORKITEM REQUEST FAILED.RC=rc, RSN=reason

ExplanationA function operation on the override file failed with areturn code and a reason code.

The LE component responsible for schedules receivedan unexpected response from a workitem request thatsignalled the beginning or the end of a service period.

The variable rc shows the value of the return code.The variable reason shows the value of the reasoncode.

System actionProcessing continues. However, this may lead to anunexpected behavior of the affected resources.



ModuleHSAHNDLS

HSAL1406I SERVICE PERIOD TIME SLOT HASBEEN MISSED FOR resource.

ExplanationThe LE component that is responsible for schedulesreceived an event indicating the beginning or the endof a time slot. However, the current status of theresource is equal to the status of the resource beforethe event was generated. This indicates the loss of atleast one time slot and can only have occurred whenthe automation manager or one of its components wassuspended for this time frame.

The variable resource shows the name of theaffected resource.

System actionProcessing continues. However, this may lead tounexpected behavior for the affected resource.

Operator responseCheck the service period of the indicated resource.Perform the missed action manually if necessary.


ModuleHSACMSST

HSAL5100E ENVIRONMENT SETUP FORWORKITEM CREATION FAILED.RC=rc RSN=rsn.

ExplanationThe setup function to create a work item failed. Theinternal communication based on work items is nolonger guaranteed.

The variable rc shows the value of the return code.The variable rsn shows the value of the reasoncode.

System actionThe automation manager terminates.





ModuleHSACLWI

HSAL6010A resource; INTERVENTIONREQUIRED; BEYONDAUTOMATION

ExplanationA problem with the resource has been detected thatautomation cannot handle.

The variable resource shows the name of theresource where an intervention is required.

System actionAutomation for the resource is stopped.

Operator responseFix the problem or notify your system programmer.

System programmer responseTry to fix the problem.

Classes80, 81.

HSAL6011E resource; INTERVENTIONREQUIRED; AUTOMATION DENIED

ExplanationThe resource could not be automated because theautomation flag is turned off.

The variable resource shows the name of theresource that could not be automated.


Operator responseCheck why the automation flag is turned off anddecide whether to turn it on.


Classes80, 82.

HSAL6012E resource; INTERVENTIONREQUIRED; AUTOMATIONINHIBITED

ExplanationAutomation of the resource is not possible due to anintervention required on another resource. Theimmediate problem with this resource is only thesymptom of a problem with another resource.

The variable resource shows the name of theresource where an intervention is required.


Operator responseFind the resource that is impacting this one and fix theproblem.


Classes80, 83.

HSAL6020I resource; AWAITINGAUTOMATION

ExplanationThe resource is automatable, but is waiting forprerequisites to be satisfied. These could be eitherdependencies or triggers.


System actionAutomation waits until the prerequisites forautomation are satisfied and then starts processing.

Operator responseIf the prerequisites involve operator action, forexample, manually setting a trigger, check that thiswas done.




Classes80, 84.

HSAL6030I resource IN AUTOMATION

ExplanationCommands concerning the resource have been sent tothe agent responsible for it.


System actionAutomation for the resource continues.



Classes80, 85.

HSAL6040E resource; DEGRADED

ExplanationThe resource is the target of a MakeAvailable requestand is currently degraded.

The variable resource shows the name of theresource that is degraded.

System actionAutomation continues. If an opportunity arises, theresource will be restored to Satisfactory.

Operator responseInvestigate why the resource is degraded.

System programmer responseAssist with operator action.

Classes80, 86, 87.

HSAL6041E resource; DEGRADED

ExplanationThe resource is currently degraded.

The variable resource shows the name of theresource that is degraded.

System actionAutomation continues. If possible, the resource will berestored to Satisfactory.

Operator responseInvestigate why the resource is degraded.

System programmer responseAssist with operator action.

Classes80, 87.

HSAL6050I resource; SATISFACTORY

ExplanationThe resource is the target of either a MakeAvailable orMakeUnavailable request and that status has beenachieved.

System actionAutomation proceeds normally.




Classes80, 88, 89.

HSAL6051I resource; SATISFACTORY

ExplanationThe resource has achieved its desired status.




System actionAutomation continues.



Classes80, 89.

HSAL6100I to HSAL6999IThese 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 aresubject 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 INGLKUPand make them available to IBM support.

HSAL6156I Prepare Unavailable orderforgotten (cancel sent)

ExplanationThe automation manager told the automation agent toissue the SHUTINIT commands for the resource and ithas done so. The Automation Manager has nowdecided that the resource should not be stopped andhas cleared its record that this has happened. Theautomation agent has been told to clear the shutdownprocess it has in progress for the subsystem.

Note that this message is not guaranteed to be issuedwhenever such a situation occurs. If, for example, theautomation agent were to disconnect, the record thatthe SHUTINIT had been issued would be cleared, butthis message (and the cancel order to the agent) wouldnot be sent.




Classes80, 89.

HSAL6230A resource; AGENT ORDERED TIME-OUT; LOST AGENT STATUSUPDATE?

ExplanationThe automation manager did not receive the expectedresponse within 5 minutes for an order that it sent tothe resource's automation agent.


System actionAutomation for the resource is suspended, itsautomation state will be set to Problem. In the eventthat the expected response should subsequentlyarrive, automation will be resumed.

Operator responseCheck the state of the resource with INGLIST. If itshows an outstanding operation, use Update to changethe resource's automation status to Idle. This shouldresume automation for the resource. If INGLIST doesnot show an outstanding operation, you need to firstset the resource's observed state to HardDown, thenset its automation state to Idle, and finally set itsobserved state to SoftDown. This should cause theautomation manager to resend the order to the agent.

System programmer responseCheck your service levels for XCF and SA z/OS. ContactIBM service for SA z/OS.

Classes80, 81.



HSAL6284I REQUEST FOR requesttype actionFROM source FOR resourceUNSATISFIED AFTER TIME OUT

ExplanationAutomation returns that the request has not beensatisfied within the specified time.

The variable requesttype action shows the type ofthe request and the action.The variable source shows the name of the source.The variable resource shows the name of theresource.




Classes80, 81.

HSAL6285I REQUEST FOR requesttype actionFROM source FOR resourceCANCELLED AFTER TIME OUT

ExplanationAutomation returns that the request has not beensatisfied within the specified time and therefore wasremoved.





Classes80, 81.

HSAL6286I REQUEST FOR requesttype actionFROM source FOR resourceSATISFIED

ExplanationAutomation returns that the request was satisfied.





Classes80, 88, 89.

HSAL6288I REQUEST FOR requesttype actionFROM source FOR resourceEXPIRED

ExplanationAutomation returns that the request was satisfied afterthe specified time period.







Classes80, 81.



Chapter 8. Messages HSAM1000I to HSAM5411I

HSAM1000I AUTOMATION MANAGERSUBTASKS ARE BEING STARTED.

ExplanationThe basic initialization step of the SA z/OS automationmanager has successfully completed. All subtasks arebeing attached and the main task will wait observingthe subtasks.

System actionThe SA z/OS automation manager continues with theinitialization.



HSAM1001I THE KEY keyword CANNOT BERETRIEVED FROM PKVT,CONTINUE WITH DEFAULT VALUE:default value.

ExplanationA keyword cannot be resolved. The key value specifiedin the parmlib member will be ignored.

The variable keyword shows the start parameterthat can be modified in the parmlib member.The variable default value shows the default valuespecified for the keyword. If the default value isblank, this field may be blank.




HSAM1002I AUTOMATION MANAGERINITIALIZATION DETECTED THATTHE SUBSYSTEM subsystem IS

MISSING OR CONFLICT DETECTEDWITH PARMLIB PARAMETERSCOMM/MQM.

ExplanationThe automation manager needs the specified systemcomponent for initialization.

The variable component shows the required systemcomponent, for example, the OMVS kernel or theWebSphere MQ Manager.



System programmer responseStart the required system component. Examine theautomation manager PARMLIB member for correctspecification of the COMM and MQM parameters. IfCOMM=XCF, the MQM parameter must not be specified.If COMM=MQ, a valid WebSphere MQ subsystem namemust be specified for the MQM parameter.

HSAM1003I ARM function WAS SUCCESSFULFOR ELEMENT=element TYPE=typerestart.

ExplanationAn ARM function (either register or deregister) couldbe successfully completed.

The variable function shows the ARM function. Itcan 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 ARMelement SA z/OS automation manager.The variable restart shows whether the automationwas restarted by ARM or not (RESTART=YES orRESTART=NO.)

System actionThe SA z/OS automation manager continues initializingbeing ARM enabled.

Messages HSAM1000I to HSAM5411I




HSAM1004I ARM function FAILED FORELEMENT=element TYPE=type,IXCARM RET=RC RSN=RSN restart.

ExplanationAn ARM function (either register or deregister) couldnot be completed successfully.

The variable function shows the ARM function. Itcan 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 ARMelement "SA z/OS automation manager" andoptionally the restart type which informs youwhether the automation was restarted by ARM ornot (RESTART=YES or RESTART=NO orRESTART=ERR).The variable RC shows the return code of the ARMfunction.The variable RSN shows the reason code of theARM function. If the Automation Manager retriesARM registration due to parameter ARMWAIT=nnnin parmlib member HSAPRMxx then the variableRSN has a suffix ",RETRY...". This informs you thatthe Automation Manager is waiting for ARM to beup.

System actionThe SA z/OS automation manager continues initializingwithout being ARM enabled. If RESTART=ERR then theSA z/OS automation manager was restarted on adifferent MVS system. In this case, the SA z/OSautomation manager terminates.


System programmer responseVerify if ARM was correctly customized for the SA z/OSautomation manager. If necessary, contact your IBMSupport Center.

HSAM1005I COMMUNICATION IS XCF ONLY.THE TAKEOVER FILE WILL BEUSED FOR HOT START ANDRECOVERY PURPOSES.

ExplanationThe automation manager does not use MQ Series,neither for the communication with the automationagents nor for recording the current status andsettings of the resources. Instead XCF is used for thecommunication with the automation agents.

The automation manager records all changes made tothe resources in the takeover file identified by DD-name HSATKOVR. In case of an abend or any normaltakeover (hot start), the automation manager reads thetakeover file to restore the most current status of theresources.

Note that any request that has not yet been processedby the automation manager will be lost and cannot berecovered in case of an abend or any regular takeover.

System actionNone.



HSAM1006E PARAMETER option CANNOT BERETRIEVED FROM PARMLIB.

ExplanationThe named parameter is mandatory but not specifiedin the HSAPRMxx parmlib member that is used at thestartup time of the automation manager.

The variable option is the name of the parameterthat is missing.



System programmer responseAdd the parameter in the HSAPRMxx parmlib memberthat is used at the startup time of the automationmanager.

HSAM1010I AUTOMATION MANAGERTERMINATION COMPLETE,REASON CODE = reason code



ExplanationThe automation manager main task terminates. If thereason code is zero it terminated successfully. Thereason code can have the following values:0

Successful completion1

Implicit normal termination due to directedtakeover (changed operation mode from SAM toPAM)

4Stop Immed

8Stop Force

20Initialization failed because MTIB could not becreated

24Initialization failed because MTIB Vector could notbe created

28Initialization failed because a task could not becreated

32Initialization failed because a task could not beattached

33Initialization stopped but no takeover is performed

34Either the initial storage check failed, or aGETMAIN service abended after initialization dueto a storage shortage. The automation managerneeds a minimum of 40 MB free storage.

35ARM (De)Reg failed

36z/OS UNIX System Services has canceled the job

39An I/O error occurred for the takeover file

40Implicit normal or forced termination due to errordetected by observer

44The subsystem is missing

45z/OS does not meet the prerequisites

48, 52C++ task failed. This is probably an exception

56LE task abended

60Task abended

64LE user abend

72Bad return code from subtask shell function

76Event handler detected an error

80The job was canceled

Note that for all return codes < 40 no ARM restart isperformed. It will be suppressed even if ARM isenabled, except for /Fjobname,STOP,..,RESTART.



System programmer responseAnalyze the reason code and, if issued, theHSAM1050E error message.

HSAM1011I CURRENT Z/OS SYSTEM DOES NOTMEET AUTOMATION MANAGERPREREQUISITES: xxxx

ExplanationThe automation manager requires a z/OS prerequisitethat is not met by the current z/OS system. Thefollowing prerequisites may be detected:

z/OS < 1.9The release of z/OS is earlier than V1.9.



System programmer responseRun the automation manager on a z/OS system thatmeets the specified prerequisites.

HSAM1050E AUTOMATION MANAGER ERRORDIAGNOSIS: SYSTEM=systemTASK=task name ERRTYPE=error


Chapter 8. Messages HSAM1000I to HSAM5411I 235

type ERRCODE=error codeSERVICE=service RC=return codeRSN=reason code DIAG=diagnostic

ExplanationThis is a generic error message that provides adetailed problem description of an error that wasdetected during automation manager processing.

• The variable system shows the name of the MVSsystem where the error was detected.

• The variable task name shows the name of theautomation manager task that causes the error.

• 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 serviceprovided by an SA z/OS system failed.

20RPC Command Handler failed.

24A system service named by SERVICE, such as theMVS request IXCJOIN, failed.

32Storage problem.

36Internal error.

Note: An internal error 36, combined withRC=00000EC6 and RSN=0000FF09 may indicateautomation manager termination due to OMVSshutdown.

40Environment error.

• The variable error code shows a unique number todetermine the location in the code where the errorwas detected.

See “AOF350E” on page 60 for diagnosticinformation about combinations of error type anderror code.

• The variable service shows the name of the servicethat caused the error.

• The variable return code shows the return code ofthe failing service (hex number). This token isspecified together with service.

• The variable reason code shows the reason code ofthe failing service (hex number). This token isspecified together with service.

• The variable diagnostic shows diagnostic informationin a string of tokens. The first token specifies thename of the failing module. All remaining tokens varydepending on the error code. Data provided bydiagnostic is intended for IBM service

• personnel.

For further information about the combinations oferror types and error codes and their meaning, refer to“AOF350E” on page 60.

System actionNone.


System programmer responseLook into the table for combinations of error type/codes for a detailed explanation of the error. Examinethe return code and reason code of the failing service ifavailable. If necessary, contact your IBM SupportCenter.

HSAM1051E SYSPLEX COMMUNICATIONMANAGER INITIALIZATIONFAILED.

ExplanationAn error was detected during initialization of thesysplex communication manager task in the SA z/OSautomation manager.



System programmer responseLook for additional HSAM1050E messages that areissued with this message.

HSAM1052I SYSPLEX COMMUNICATIONMANAGER INITIALIZATIONCOMPLETE.



ExplanationThe sysplex communication manager task of theSA z/OS automation manager could be successfullyinitialized and is ready to receive.




HSAM1059I DIAGNOSTIC INFO: MOD=moduleINCIDENT=incident diagnostic-text

ExplanationThe purpose of this message is to provide diagnosticinformation to IBM service staff.

The variable module shows name of the modulethat detected the incident.The variable incident shows a unique ID for aninternally detected incident.The variable diagnostic-text shows useful text infree format. The text depends on the incident thatoccurred. For example, for INCIDENT=100, this isthe duplicate handle + seq-number.




HSAM1301I SA z/OS AUTOMATION MANAGERWAITING FOR INITIALIZATIONDELAY COMPLETION.

ExplanationAn automation manager initialization delay of greaterthan 30 seconds was specified. The specified delayallows another automation manager to assume prioritycontrol of the automation sysplex if started within thedelay period.

System actionThe SA z/OS automation manager suspendsinitialization until the specified delay expires or iscanceled through an operator command. This messageis deleted when the specified delay is no longer ineffect.

Operator responseThe delay may be canceled by routing an MVSModify(F) <jobname>,GO command to the issuingsystem image.


HSAM1302A SPECIFY SA z/OS AUTOMATIONCONFIGURATION DATA SETNAME.

ExplanationThe SA z/OS automation manager has been startedwith PROMPT=YES in effect. If requested, thismessage will appear on the first SA z/OS automationmanager instance to assume control of the automationsysplex following a sysplexwide IPL or similarautomation shutdown.

System actionThe SA z/OS automation manager waits for a responseto this request.

Operator responseA null or asterisk (*) response may be used to indicatethat the default data set as determined by the starttype is to be used. For a warm start, this default is thedata set that was in use when the previous primaryautomation manager instance terminated. For a coldstart, the default is the data set or generation datagroup (GDG) member as specified for the installationthrough the selected parmlib member.

The response may also be a fully qualified data set orGDG member name. If the default configuration dataset is a GDG member, a different member of the sameGDG may be specified using an asterisk followed bythe relative GDG number in parentheses, for example,*(0) or *(-1).




HSAM1303I SA z/OS AUTOMATION MANAGERIS WAITING FOR MQSERIESCONNECTION

ExplanationThe SA z/OS automation manager is checking whetherMQSeries is ready.

System actionIf MQSeries is not ready the SA z/OS automationmanager retries until the TAKEOVERTIMEOUT definedin the parmlib is expired. If it is expired the SA z/OSautomation manager switches from hot to warm start.



HSAM1304A SPECIFY SA z/OS AUTOMATIONCONFIGURATION DATA SETNAME.

ExplanationThe SA z/OS automation manager was unable todetermine or otherwise process the configuration dataset as specified through the HSAM1302A response, ordefaulted from prior use. Additional messages willindicate any errors encountered while attempting toprocess the specified or default data set.

System actionThe SA z/OS automation manager waits for a responseto this request.

Operator responseThe response must be the fully qualified MVS data setor GDG member name containing the SA z/OSconfiguration data. If the default configuration data setis a GDG member, a different member of the sameGDG may be specified using an asterisk followed bythe relative GDG number in parentheses, for example,*(0) or *(-1). The automation manager may also bestopped if no valid configuration data is available.


HSAM1305I UNABLE TO PROCESS SA z/OSAUTOMATION CONFIGURATIONDATA SET dataset

ExplanationThe SA z/OS automation manager was unable todynamically allocate the named configuration data set.The named data set name was successfully allocated,but cannot be used by the issuing automation managerinstance. Additional messages will indicate any errorsencountered while attempting to process the specifiedor default data set.

The variable dataset shows the name of theconfiguration data set that could not be allocateddynamically.

System actionThe SA z/OS automation manager instance promptsfor a new configuration data set name via messageHSAM1304A.

Operator responseCheck that the data set has not been incorrectlymodified prior to starting the affected automationmanager instance. Also check whether all copyoperations from the configuration dialog outputcompleted successfully. Respond to the HSAM1304Aprompt with a new or backup data set name asdescribed in the installation procedures.


HSAM1306I UNABLE TO ALLOCATE SA z/OSAUTOMATION CONFIGURATIONDATA SET dataset

ExplanationThe SA z/OS automation manager was unable todynamically allocate the named configuration data set.The data set name could not be allocated or is not apartitioned data set. Additional dynamic allocationmessages will indicate any errors encountered whileattempting to allocate the data set.

The variable dataset shows the name of theconfiguration data set that could not be allocateddynamically.



System actionThe SA z/OS automation manager instance promptsfor a new configuration data set name via messageHSAM1304A.

Operator responseCheck that the data set name is correct and that it is acorrectly catalogued partitioned data set. Respond tothe HSAM1304A prompt with a new or backup dataset name described in the installation procedures.


HSAM1307I SA z/OS SECONDARYAUTOMATION MANAGERINITIALIZATION COMPLETE.

ExplanationThe SA z/OS automation manager instance hascompleted initialization as a secondary manager, andis ready to assume automation sysplex control withminimum delay in case the primary managerterminates.

System actionThe SA z/OS automation manager instance monitorsfor changes in the configuration status, and attemptsto assume control of the automation sysplex in casethe primary automation manager terminates.



HSAM1308I SA z/OS PRIMARY AUTOMATIONMANAGER INITIALIZATIONCOMPLETE, TYPE=type

ExplanationThe SA z/OS automation manager instance hascompleted initialization as the primary automationmanager, and has assumed control of the automationsysplex.

The variable type shows the start type. It can beCOLD, WARM, or HOT.

System actionThe SA z/OS automation manager instance monitorsfor changes in the configuration status, and is ready toservice requests from all automation agents defined tothe automation sysplex.



HSAM1309I SA z/OS PRIMARY AUTOMATIONMANAGER HOT TAKEOVERCOMPLETE.

ExplanationThe SA z/OS automation manager instance hassuccessfully completed a takeover operation and isnow the primary automation manager. This messagemay also appear when a START=HOT is used tomanually restart the manager.

Note: Although the Automation Manager takeover isnow complete, the Automation Agents might still be inthe process of loading the Automation Control File(ACF). During the ACF load process, the AutomationAgent will reflect status SUSPENDED on the INGAMSdisplay.

Issuing an INGAMS REFRESH command while anAgent is SUSPENDED will interfere with the stillongoing load process and will result in a delay for theprocessing of the INGAMS REFRESH command. It isrecommended that you wait until all agents are in theREADY status before issuing the INGAMS REFRESHcommand.

System actionThe SA z/OS automation manager instance monitorsfor changes in the configuration status, and is ready toservice requests from all automation agents defined tothe automation sysplex.



HSAM1310I RC=rc REAS=reason OPCODE=@5(@3.@4) @6.



ExplanationThis is an internal message for diagnostic purposesonly.

Ignore messages with RC=2.

System actionNone.



HSAM1311I @1


System actionNone.



HSAM1314I TAKEOVER WILL BE DELAYED FORtimeout SECONDS.

ExplanationTakeover will be delayed for a number of seconds if itis done from the VSAM takeover file.

The variable timeout is taken from theTAKEOVERTIMEOUT parameter of the HSAPRMxxparmlib member.

System actionProcessing continues. Any stop command is acceptedbut does not cause termination until the time that isspecified in TAKEOVERTIMEOUT has expired.



ClassesNone.

HSAM1315I SUCCESSFUL ALLOCATION OFTAKEOVER FILE dataset_name.

ExplanationThe automation manager issues this message whenthe takeover file has been allocated successfully.

The variable dataset_name is the name of thetakeover file as specified in the HSAPRMxx parmlibmember.

System actionThe SA z/OS automation manager continues withinitialization.



HSAM1316I ALLOCATION OF TAKEOVER FILEdataset_name FAILED WITHRC=code: DIAGNOSTIC INFORETCODE=retcodeREASON=reason.

ExplanationThe automation manager tried to allocate the specifiedtakeover file but this failed.

• The variable dataset_name is the name of thetakeover file as specified in the HSAPRMxx parmlibmember.

• The variable code explains why the allocation failed.It can have the following values:98

No more memory99

Invalid input parameter10nn

Allocation failed20nn

Deallocation failedwhere nn is one of the following:



8Invalid data set name, member name, or DD-name.

12Allocation error. retcode and reason are thereturn code and reason code from the SVC 99(DynAlloc).

• The variable retcode gives more details about whythe allocation failed.

• The variable reason is the reason code.

System actionThe automation manager continues and issuesmessage HSAM1317A, asking the operator how tocontinue.


System programmer responseAnalyze why the allocation failed. Look for additionalmessages (HSAL1105E in case of an I/O error) that areissued with this message.

HSAM1317A REPLY "HOT" TO RETRY HOT-START OR "WARM" TO CONTINUEWITH WARM-START OR "CANCEL".

ExplanationDuring the initialization of the automation managerperforming a hot-start, an error occurred whileaccessing the takeover file. Either the allocation failedor a VSAM read/write error occurred or the takeoverfile was disabled by the previous PAM.

System actionThe automation manager waits for an operatorresponse.

Operator responseSpecify:HOT

To retry hot-start processing by allocating thetakeover file again.

WARMTo continue with a warm start.

CANCELResults in HSAM1390E with the option to stop theautomation manager.


HSAM1318D Reply "NOSUSPEND" or"FORCESUSPEND" to continue or"CANCEL".

ExplanationDuring the initialization of the automation managerperforming a COLD or WARM start, the processing ofthe suspend file failed due to an allocation failure, aread error or syntax error(s).

The NOSUSPEND option continues the automationmanager's initialization without processing thesuspend file.The FORCESUSPEND option continues processingthe suspend file and ignores possible errors.The CANCEL option stops the automation manager.

System action:The automation manager waits for an operatorresponse.

Operator response:Specify one of the valid options.


HSAM1319I INPUT DATA NOT ACCEPTED

Explanation:A WTOR was issued and asked the operator to enterinput data. However, the input data was incorrect.

System action:The WTOR is reissued to ask for valid input data.

Operator response:Enter the correct input data. See message text of thecorresponding WTOR.


HSAM1320E SA z/OS AUTOMATION MANAGERrequest REQUEST TIMED OUT.

ExplanationThe named internal automation manager request didnot complete within the time limit associated with therequest.

The variable request shows the name of the requestthat timed out.

This may be due to temporary system performancefactors, delays caused by an unusual amount ofautomation activity, or problems processing thenamed request.



System actionThe SA z/OS automation manager instance continuesmonitoring for commands and configuration changes,and resumes normal operation when the namedrequest completes. The message will also be deletedwhen the request has completed.

Operator responseIf this message appears often or remains outstandingfor an extended period, advise your systemprogrammer of the condition.

System programmer responseInvestigate the following request specific possibilities:

• AMS_READ_CONFIGURATION

This request is issued during Primary automationmanager startup, automation manager takeover, andwhen a configuration refresh is requested. If themessage appears during a hot start or takeoveroperation, the delay is probably MQSeries related. Ifit appears during a Warm or Cold start, orconfiguration refresh operation, the delay is probablyI/O related.

Another reason might be that the automationmanager does not run as super user for UNIX SystemServices or one of your file system managementaddress spaces does not run with SUB=MSTR. Seealso message HSAL1083I for more information.

• AMS_APPLY_CONFIGURATION

While the timeout value for most automationmanager requests is determined by IBM, theAMS_APPLY_CONFIGURATION timeout value may bespecified through the HSAPRMxx parametermember. The time necessary to complete thisfunction depends on the number of resourcesdefined, and the temporary appearance of theHSAM1320E message may indicate that thespecified or default timeout value is too low.

HSAM1321I SA z/OS AUTOMATION AGENTrequest REQUEST TIMED OUT.

ExplanationAn automation agent request did not complete withinthe time limit. This may be due to temporary systemperformance factors, delays caused by an unusualamount of automation activity, or problems processingthe named request.

The variable request shows the name of the requestthat timed out.

For a configuration refresh it is required that checkACF is complete on all agents. Note that aconfiguration refresh operation is considered completewhen the automation manager configuration has beenupdated, and does not require that all automationagents have completed their correspondingconfiguration update activity.

System actionThe SA z/OS automation manager instance continuesmonitoring for commands and configuration changes,and resumes normal operation when the namedrequest completes. The message will be deleted whena response was received from all affected agents.

Operator responseVerify that all active automation agents appear to beworking correctly and are communicating with theautomation manager.

If this message appears often or remains outstandingfor an extended period, advise your systemprogrammer of the condition.


HSAM1323I UNABLE TO OBTAIN PREVIOUSCONFIGURATION INFORMATION,RC=rc, Reason=reason.

ExplanationThe SA z/OS automation manager was unable to readthe data set defined by the HSACFGIN DD statement.


System actionThe SA z/OS automation manager instance terminates.

Operator responseCheck that the data set defined by the HSACFGIN DDstatement of the automation manager start procedureis available and correctly initialized. Restart theautomation manager using an alternate data set ifavailable, or contact your systems programmer.

System programmer responseAll instances of the automation manager within theautomation sysplex must point to the same CFGINFO



data set. A new data set can be initialized by startingthe automation manager with TYPE=COLD.

HSAM1324E UNABLE TO UPDATECONFIGURATION INFORMATION,RC=rc, REASON=reason

ExplanationThe SA z/OS automation manager could not update thedata set defined by the HSACFGIN DD statement.


System actionIf this message appears during initial automationmanager startup, the instance continues to runnormally. However, a subsequent warm may not bepossible. If the error occurs during a configurationrefresh operation, the configuration refresh will beaborted.

Operator responseCheck that the data set defined by the HSACFGIN DDstatement of the automation manager start procedureis available and correctly allocated. Also check that theautomation manager has the necessary authorizationto update it. When the problem is resolved, perform aconfiguration refresh using the correct data set name.

System programmer responseAll instances of the automation manager within theautomation sysplex must point to the same CFGINFOdata set. Also, all automation manager instances musthave the correct SAF authority to allow it to beupdated. 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 duringautomation manager initialization.

HSAM1330I request REQUEST COMPLETEDSUCCESSFULLY ON agent.

ExplanationAn automation manager request has successfullycompleted on an automation agent.

The variable request shows the request that wascompleted.The variable agent shows the name of theautomation agent.

System actionThe SA z/OS automation manager instance continuesnormal processing relative to the identified automationagent.



HSAM1331I request REQUEST FOR agentFAILED

ExplanationAn automation manager request failed on anautomation agent.

The variable request shows the request that failed.The variable agent shows the name of theautomation agent.

System actionThe automation manager action depends on therequest that failed and on the reason why the requestwas issued. In general however, the actions are asfollows:

• Load_ACF Request

The affected agent is unable to initialize or performautomation until the cause of the failure is identifiedand resolved. The most common cause of this failureis a mismatch between the ACF available to theagent and the current automation managerconfiguration. Additional automation agentmessages may provide more detailed informationabout the reason for the failure.

• Check_ACF request

This request is normally issued during aconfiguration refresh operation to verify that the newconfiguration is available to all automation agents.The configuration refresh operation is terminated asa result of this condition.

• Refresh_ACF

This request is normally issued at the end of aconfiguration refresh operation to activate therevised ACF. The affected agent should continue tooperate in a compatible manner with the newconfiguration using the previously active ACF data.Thus, newly added resources will not be automatedand existing resources will be automated using thepreviously defined automation policy.



Operator responseContact your system programmer. When the problemhas been resolved, reissue a configuration refreshcommand to retry the failed request.

System programmer responseThe most common cause of Load_ACF failure is thatthe ACF available to the automation agent isincompatible with the current manager configuration.Similarly, a Check_ACF failure often indicates anincompatibility between the available ACF and the newautomation manager configuration. Other possiblecauses include corruption of the ACF content andvarious other problems verifying its content. Thereporting automation agent should provide additionalinformation about the reason for the failure.

The failure of a Refresh_ACF request indicatesproblems were encountered while activating thechanges contained in the new configuration. Anyresources that were deleted or added by the newconfiguration will not be automated, and existingresources will be automated using the previous agentpolicy.

HSAM1332I INVALID response RESPONSEFROM agent, REASON=reason.

ExplanationAn invalid response for a request was received from anautomation agent.

The variable response shows the invalid responsethat the automation agent issued.The variable agent shows the name of theautomation agent that issued the response.The variable reason shows the value of the reasoncode that the automation agent issued.

System actionIf the request is Check_ACF, the associatedconfiguration refresh operation will be terminated.Otherwise, the automation manager operationcontinues as if the return code had been zero.

Operator responseReport the message to your system programmer.Check whether the identified agent operates correctly.Also check whether any error messages are issuedthat indicate problems when processing the namedrequest.

System programmer responseThis message indicates a software problem. Report theproblem to your IBM Support Center.

HSAM1333I request REQUEST PROCESSED ONagent.

ExplanationThe automation manager has completed processing ofa request.

The variable request shows the name of therequest.The variable agent shows the name of theautomation agent where the request wasprocessed.

Normally, the automation manager then goes back toready state. However, this message does not confirmthat the request was processed successfully. It mayalso have failed. In case of a failure, an additionalmessage may be issued, for example, if a refreshrequest fails, message HSAM1337I is issued.

System actionThe SA z/OS automation manager instance continuesprocessing normally. Additional messages, forexample message HSAM1330I, may be issued due toevents that are received later on.



HSAM1336I UNABLE TO PROCESS THESUSPEND FILE dataset_name.

ExplanationA configuration refresh could not finish successfully.The automation manager was unable to process thesuspend file for one of the following reasons:

• The file was not allocated successfully.• The file could not be read.• Access rights are not defined correctly.• A syntax error occurred when checking the file

content.

The dataset_name variable shows the name of thesuspend file.



Additional messages will indicate any errorsencountered while attempting to process the specifiedsuspend file.

System action:The previous configuration remains active.

Operator response:Verify that the suspend file exists and the access rightsare correctly defined. Look for additional messagesthat may describe the reasons for the error.


HSAM1337I CONFIGURATION REFRESHREQUEST TERMINATED.

ExplanationA configuration refresh request has been terminateddue to errors or automation agent incompatibilities. Nochanges to the automation manager configurationhave been implemented and no automation agentupdates have been scheduled as a result of therequest.

System actionAutomation continues using the configuration in effectwhen the request was issued.

Operator responseCheck for other messages indicating the reason for thetermination of the request. Determine the cause of theerror and correct your data. Then reissue the request.


HSAM1338I CONFIGURATION REFRESHREQUEST COMPLETED WITHAGENT UPDATE ERRORINDICATIONS.

ExplanationA configuration refresh request has completedsuccessfully on the automation manager. However,one or more automation agents have reportedproblems when implementing the ACF changes.Message HSAM1331I contains more informationabout the affected agent(s), and the individual agentsshould have issued messages indicating the problemdetails.

System actionAutomation continues using the new automationmanager configuration. The affected agent(s) shouldcontinue to operate in a compatible manner with thenew configuration using the previously active ACFdata. Thus, newly added resources will not beautomated. Existing resources will be automated usingthe previously defined automation policy.

Operator responseContact your system programmer. When the cause hasbeen determined, issue a configuration refreshcommand to retry the failed request.

System programmer responseCheck for automation agent error messages indicatingthe cause of the ACF refresh failure and correct yourdata accordingly.

The failure of a Refresh_ACF request indicatesproblems were encountered while activating thechanges contained in the new configuration. Anyresources that were deleted or added by the newconfiguration will not be automated. Existing resourceswill be automated using the previous agent policy.

HSAM1339I CONFIGURATION REFRESHREQUEST COMPLETEDSUCCESSFULLY.

ExplanationThis message is issued when a configuration refreshrequest has been completed successfully. It indicatesthat the primary automation manager and all SA z/OSautomation agents within the automation sysplex haveprocessed the request and have indicated normalcompletion of the update process.

System actionAutomation continues using the requestedconfiguration.


HSAM1360I UNABLE TO RETRIEVE RECOVERYINFORMATION - WARM STARTRECOVERY IN PROGRESS.



ExplanationA takeover or startup with TYPE=HOT cannot completebecause the recovery information needed to do so iseither unavailable or has been invalidated.

System actionThe automation manager performs a warm start toreach an operational state. Automation continues afterthe warm start operation completes. This operationmay take some time to complete because eachautomation agent must reconnect with the automationmanager and present status for all resources under itscontrol.

Operator responseAny automation manager requests that wereincomplete when the previously active PAMterminated may need to be resubmitted.


HSAM1361I UNABLE TO PROCESS RECOVERYINFORMATION - ABNORMALTERMINATION IN PROGRESS

ExplanationA takeover, ARM restart, or restart with TYPE=HOTcannot complete because the recovery informationneeded to do so is invalid.

System actionThe automation manager instance will be abnormallyterminated after invalidating the recovery information.This prevents a subsequent takeover or restart fromattempting a retry using the invalid recovery data.

Operator responseIf another automation manager instance is available, itshould attempt a takeover operation, detect theinvalidated restart information, and recover byattempting a warm start (see message HSAM1360I).Otherwise, the current automation manager instancewill be restarted by ARM if defined by the installationas eligible for restart. If neither of these two conditionsapply, manually restart the automation managerinstance specifying either TYPE=WARM or TYPE=HOT.

HSAM1370I TAKEOVER WILL BE DONE FROMTAKEOVER FILE:dsn.

ExplanationThe automation manager performs a hot start or atakeover from the takeover file with the namespecified in dsn.

System actionNone.



HSAM1371I TAKEOVER FILE CANNOT BE READOR IS CORRUPTED.

ExplanationThe automation manager tried to read the takeoverfile. However, the data set is either not readable or isnot a valid takeover file (does not contain a valididentifier).

System actionThe automation manager continues with a warm start.


System programmer responseCheck that the data set has a valid takeover fileidentifier. The first four bytes must contain the binaryvalue X'12345678'.

HSAM1372I FORCE WARM START DUE TOTAKEOVER FILE OR OPERATORRESPONSE.

ExplanationThe automation manager tried to perform a hot start ora takeover from the takeover file. This action failed andthe hot start was degraded to a warm start. The reasonfor the failure is that the operation code at offset 16was previously set to 'W' or that it is not valid. Thismay occur when the previous automation managerinstance has invalidated the takeover file, for example,because of an I/O problem or an internal problem.



System actionThe automation manager continues with a warm start.



HSAM1373I PROBLEM WITH TAKEOVER FILEDETECTED. REASON=rr, INFO=yyy

ExplanationThe automation manager detected one of the followingproblems regarding the takeover:

• The reason code rr describes the problem:

DisabledThe previous PAM has disabled the takeover file.The takeover file might therefore be outdated.

IOErrorThe previous PAM has detected an I/O error for thetakeover file. The takeover file might therefore beoutdated.

LoadErrorThe previous PAM has suffered an ABEND whileloading the takeover file. The most likely reason isa corrupted takeover file.

MismatchDuring takeover a mismatch was detectedbetween the takeover file name in the HSAPRMxxparmlib member and the name that was used bythe previous PAM.

Possible MismatchDuring startup of a SAM, a mismatch is detectedbetween the takeover file name in the HSAPRMxxparmlib member and the name that was used bythe previous PAM. This message might be anindication that the SAM and PAM do not use thesame parmlib member HSAPRMxx. However, thereis a time window where the SAM and the PAM arestarted concurrently where this possible mismatchcan occur and can possibly be ignored. This is thecase when the pending PAM has not yet finishedreading the configuration file and has not yetupdated the HSACFGIN accordingly. In any case itis recommended to check that the parmlibmembers are still valid.

• The variable yyy='tkovfile_dsn1, tkovfile_dsn2 wheretkovfile_dsn1 is taken from HSAPRMxx andtkovfile_dsn2 is the takeover file that was used by theprevious PAM.

System actionThe automation manager also issues messageHSAM1317A and waits for a response. This is not thecase for reason 'Possible Mismatch'.

Operator responseDepending on the reason code, proceed as follows:

• If rr=Disabled or IOError, check that the takeover fileis valid.

• If rr=Mismatch, cancel the automation manager andcorrect the HSAPRMxx parmlib member. See alsomessage HSAM1317A.

• If rr=Mismatch and you decide to enter HOT, theautomation manager uses the same takeover file aswas used by the previous PAM rather than thetakeover file name that is specified in the HSAPRMxxparmlib member.

• If rr=Mismatch and you decide to enter WARM, theautomation manager that is specified in theHSAPRMxx parmlib member.

• If rr=LoadError, check if the takeover file iscorrupted. If you can repair the file, then you canreply HOT to message HSAM1317A. Otherwise,continue with an Automation Manager WARM start.

HSAM1380I request REQUEST ACCEPTED.

ExplanationA request has been received and validated by theautomation manager.

The variable request shows which request wasreceived and validated.

System actionThe automation manager instance processes therequest.



HSAM1381I INVALID verb REQUESTPARAMETER, request REQUESTIGNORED.

ExplanationA parameter specified with a request is invalid for therequest verb.



The variable verb shows the request verb that oneof the parameters specified on the request isinvalid for.The variable request shows the request that couldnot be processed.

System actionThe automation manager instance ignores the request.

Operator responseSpecify valid parameters and reissue the request.


HSAM1382I UNSUPPORTED COMMAND VERB,request REQUEST IGNORED.

ExplanationAn unsupported command verb was used to route arequest to the automation manager. The automationmanager supports only the MVS MODIFY (F) commandfor request input.

The variable request shows the request that couldnot be processed.



System programmer responseThe automation manager command interface receivedthe identified request with an MVS command requestcode other than that used for the MVS Modifycommand.

HSAM1383I verb REQUEST REJECTED:INCORRECT AUTOMATIONMANAGER ROLE OR STATUS.INVALID verb REQUESTPARAMETER, request REQUESTIGNORED.

ExplanationAn MVS MODIFY (F) command was routed to anautomation manager instance that is not in a role orstate compatible with the requested request verb.Because most automation manager requests run only

on the primary automation manager (PAM), it is likelythat the command was routed to a secondary instance.Other requests require that the target automationmanager be in a "ready" state to be accepted.

The variable verb shows the specified request verb.The variable request shows the request that couldnot be processed.


Operator responseVerify that the command was routed to the correctautomation manager instance and that the instance isin a ready state. Reissue the command accordingly


HSAM1384I INVALID REQUEST verb, requestREQUEST IGNORED. INVALID verbREQUEST PARAMETER, requestREQUEST IGNORED.

ExplanationAn MVS MODIFY (F) command was received with aninvalid request verb.


Operator responseCorrect the verb and parameter syntax and reissue therequest.

HSAM1389I BUILD ID FOR HSAPIEHM xxx yyy

ExplanationThis is an information message for IBM Service. Thefields xxx and yyy provide the compilation date of theevent handler, for example, 2009154 152228.

System actionNone.


HSAM1390E REPLY "YES" TO CONFIRM OR"NO" TO CANCEL SA z/OS



AUTOMATION MANAGER STOPREQUEST.

ExplanationA conditional request has been made to stop anSA z/OS automation manager. No other SA z/OSautomation manager instances are available and readyto assume automation sysplex control if this request isallowed to continue. This will result in an interruptionof automation services.

System actionThe SA z/OS automation manager waits for a responseto this request, and continues automation sysplexcontrol until confirmation is received.

Operator responseReply 'YES' to terminate SA z/OS automation, 'NO' tocancel the stop request. Another SA z/OS automationmanager instance may be started prior to confirmingthe request to avoid an interruption of automationservices.


HSAM1391E INVALID RESPONSE: REPLY "YES"TO CONFIRM OR "NO" TO CANCELSTOP REQUEST.

ExplanationAn invalid response has been given to messageHSAP1390E. Refer to the explanation of that messagefor additional information.

System actionThe SA z/OS automation manager waits for a responseto this request, and continues automation sysplexcontrol until confirmation is received.

Operator responseReply 'YES' to terminate SA z/OS automation, 'NO' tocancel the stop request. Another SA z/OS automationmanager instance may be started prior to confirmingthe request to avoid an interruption of automationservices.


HSAM1392I AUTOMATION MANAGER STOPREQUEST CANCELLED.

ExplanationA request to confirm an automation manager stoprequest has been denied. Refer to the explanation ofmessage HSAM1390E for additional information.

System actionThe issuing SA z/OS automation manager continuesprocessing.



HSAM1393I DEFERRED STOP REQUESTWAITING FOR AUTOMATIONAGENT TERMINATION.

ExplanationA deferred stop request was issued to the primaryautomation manager. Upon the expiration of the stopdelay, one or more automation agents were active andno secondary automation manager was available toaccomplish a takeover.

System actionThe SA z/OS automation manager waits until allautomation agents are disconnected or anotherautomation manager instance is started.

Operator responseA deferred stop cannot be canceled. However, startinga new automation manager instance will result in thetermination of the current primary manager with atakeover by that new instance.


HSAM1396I SA z/OS AUTOMATION MANAGERSHUTDOWN IN PROGRESS, TYPE=type

ExplanationA request has been received to stop an SA z/OSautomation manager instance.



The variable type indicates the type of shutdown asrequested by the initiating command.

System actionThe SA z/OS automation manager instance terminatesafter performing cleanup activities.



HSAM1399I @1


System actionNone.



HSAM5100E NO SQA STORAGE AVAILABLE.

ExplanationThe first automation manager running after an IPLallocates storage in the system queue area (SQA) tohold information shared by all automation managersrunning on the single image and the component traceitself. This area could not be allocated.

System actionThe component trace of all automation managers isdisabled.


System programmer responseIncrease the system queue area size.

ModuleHSAPICB7

HSAM5101I NUMBER OF ACTIVE AMSEXCEEDS THE NUMBER OF ASIDSSUPPORTED FOR THECOMPONENT TRACE.

ExplanationThe number of active automation managers exceedsthe number of address space IDs supported for thecomponent trace. Therefore, the automation managerissuing this message did not find a free entry in thesystem queue area (SQA) to store its information.

System actionThe automation manager’s component trace isdisabled.



ModuleHSAPICB7

HSAM5102E NAME/TOKEN SERVICE FAILED.RC=rc.

ExplanationThe name/token pair could not be created or deletedduring initialization or termination of the automationmanager.

The variable rc shows the value of the return codethat was issued.

System actionThe automation manager component trace is disabled.


System programmer responseAnalyze the return code (see IEANTCR/IEANTDL inz/OS MVS Assembler Service Reference).



ModuleHSAPICB7, HSAPICB8

HSAM5103E MODULE module NOT FOUND.

ExplanationThe automation manager component traceinitialization routine could not load the requiredmodule.

The variable module shows the name of the modulethat could not be loaded.

System actionIf this message is followed by message HSAM5109Ithe component trace is disabled. Otherwise, theautomation manager is terminated.


System programmer responseMake the required module available to the automationmanager.

ModuleHSAPICB7

HSAM5104I SQA ENTRY NOT FOUND.

ExplanationThe automation manager component trace terminationroutine could not clear its system queue areainformation.




ModuleHSAPICB8

HSAM5105E DE-/REGISTRATION TO THECOMPONENT TRACE FAILED.RC=rc RSN=rsn.

ExplanationRegistration to or deregistration from the componenttrace failed.

The variable rc shows the return code that wasissued.The variable rsn shows the reason code that wasissued.

System actionThe automation manager component trace is disabledon registration.


System programmer responseAnalyze the return code and the reason code (seeCTRACE in the z/OS Authorized Assembler ServiceReference ).

ModuleHSAPICB7, HSAPICB8

HSAM5106I ERROR OCCURRED WHENWRITING A TRACE RECORD.POS=position, SYSTEM CC=cc.

ExplanationThe PC routine writing the trace records abended withthe system completion code cc.

The variable position shows the position inside themodule where the abend occurred.The variable cc shows the completion code.






ModuleHSAPSTAR

HSAM5107I ERROR OCCURRED IN START/STOP ROUTINE. POS=position,SYSTEM CC=cc.

ExplanationThe automation manager start/stop routine of thecomponent trace abended with the system completioncode cc.

The variable position shows the position inside themodule where the abend occurred.The variable completion_code shows thecompletion code.

System actionThe TRACE command is not processed.



ModuleHSAPSTSS

HSAM5108I COMPONENT component_nameALREADY DEFINED TO THECOMPONENT TRACE.

ExplanationAn automation manager could not be registered to thecomponent trace because a previous automationmanager did not deregister itself.




ModuleHSAPICB7

HSAM5109E NAME/TOKEN SERVICE ISUNAVAILABLE.

ExplanationThe MVS name/token services IEANTCR/RT/DL are notavailable.



System programmer responseMake the MVS name/token service available.

ModuleHSAPICB7

HSAM5110I Error occurred in display routine.Pos=position, System CC=cc.

ExplanationThe automation manager display routine of thecomponent trace abended.

The variable position shows the position in themodule where the abend occurred.The variable cc shows the system completion codethat the display routine abended with.

System actionThe TRACE command is not processed.



ModuleHSAPSCTD

HSAM5120E LISTENER USER EXITINITIALIZATION FAILED. RC=rc.



ExplanationThe activation of the System Logger user exit failedwith a return code.

The variable rc shows the value of the return code.



System programmer responseIf the return code is greater than 4, refer to the returncodes of the macro ENFREQ in z/OS MVS AuthorizedAssembler Service Reference for further information.

ModuleHSAPICB7, HSAPNCTI

HSAM5121E LISTENER USER EXIT DELETIONFAILED. RC=rc.

ExplanationThe deactivation of the System Logger user exit failedwith a return code.




System programmer responseIf the return code is greater than 4, refer to the returncodes of the macro ENFREQ in z/OS MVS AuthorizedAssembler Service Referencefor further information.

ModuleHSAPICB8, HSAPNCTI

HSAM5160I VSAM request ERROR OCCURRED.RC=rc REASON=reason

ExplanationThe VSAM macro instruction that corresponds to therequest failed.

The variable request shows the request that failed.The variable rc shows the return code that wasissued.The variable reason shows the reason code thatwas issued.



System programmer responseCheck the return and reason codes in DFSMS/MVSMacro Instructions for Data Sets, in the chapter aboutVSAM Macro Return and Reason Codes. Correct theerror accordingly. Then rerun the program with thePARM parameter 'RERUN'.

ModuleHSAPSIPL

DestinationNone.

TEC: NO

HSAM5170I UNKNOWN TRACE OPTIONFOUND: option

Explanation• The variable option shows the trace option specified

on the OPTIONS parameter of the IPCS CTRACEcommand. The following are valid values:

– Communication– Event– Instruction– Lock– Schedule– Workitem


Operator responseCorrect or delete the option.




ModuleHSAPSTUE

HSAM5171I UNKNOWN KEYWORD FOUND:keyword.

ExplanationThe parser found a keyword that is not valid.

The variable keyword shows the specified filteroption.

The following are valid values:

• AM• CALLID• ITEM• KEY• METHOD• MODULE• TASKID

System actionThe keyword is ignored.

Operator responseSpecify a correct keyword.


ModuleHSAPSTUE

HSAM5172I TOO MANY VALUES SPECIFIEDFOR KEYWORD keyword.

ExplanationAll keyword options except AM on the OPTIONSparameter support up to five different values.However, the parser found at least one additionalvalue for keyword option keyword.

The variable keyword shows the specified filteroption.

System actionThe values that exceed the number of five are ignored.

Operator responseCorrect the keyword option.


ModuleHSAPSTUE

HSAM5173I N (ST/ND/RD/TH) VALUE OFKEYWORD keyword IS EMPTY.

ExplanationThe parser expects a string of at least one characterfor the keyword option keyword on the OPTIONSparameter. However, it found no string, or a stringrepresenting the NULL string.

The variable N shows the number of missing values.The variable keyword shows the specified filteroption.

System actionThe value is ignored.

Operator responseCorrect the value.


ModuleHSAPSTUE

HSAM5174I VALUE value OF KEYWORDkeyword IS NOT NUMERIC.

ExplanationThe parser expects an integer for the keyword optionkeyword on the OPTIONS parameter. However, it founda non-numeric value.

The variable value shows the value that is notnumeric.The variable keyword shows the specified filteroption.



System actionThe value is ignored.

Operator responseCorrect the value.


ModuleHSAPSTUE

HSAM5175I PARSING OF THE OPTIONSPARAMETER STOPPED ATCOLUMN col.

ExplanationA column value greater than 0 indicates one of thefollowing:

• A keyword is not spelled correctly.• A keyword is incorrectly delimited.• A trace option is incorrectly delimited.

A column value of 0 can be caused by one of thefollowing:

• A parameter consisting of blanks and commas only• A parameter length greater than 32K• An allocation error of temporary storage

The variable col shows which column the parserstopped at.


Operator responseCorrect the OPTION parameter, or increase the regionsize.


ModuleHSAPSTUE

HSAM5185I THE EXTERNAL WRITER HASBEEN STARTED AUTOMATICALLY.

ExplanationThe start/stop routine detected that the external writeris not active. Because the automation managercomponent trace requires an active external writer, thestart/stop routine issued the appropriate TRACEcommand.




ModuleHSAPSTSS

HSAM5186I ENVIRONMENTAL ERROROCCURRED DURING POST OF THELAST ACTIVE AM.

ExplanationPOST of the automation manager waiting for thecompletion of the start/stop routine failed.

System actionProcessing continues. But the automation manager isstill waiting.

Operator responseStop the automation manager manually.


ModuleHSAPSTSS

HSAM5187I PARAMETER WTR= IS MISSING.

ExplanationThe start/stop routine detected that the WTRparameter is missing in the reply to the precedingTRACE command.



System actionThe TRACE command is discarded.

Operator responseRe-issue the TRACE command and add the WTRparameter to the reply.


ModuleHSAPSTSS

HSAM5188I PARSING OF TRACE OPTIONSFAILED. RC=rc.

ExplanationThe start/stop routine scheduled in the *MASTER*address space encountered a storage problem whenparsing the OPTION parameter.



Operator responseTry the command later. If the problem persists,contact your IBM Support Center.


ModuleHSAPSTSS

HSAM5189E ACCESS TO DATA SPACE FAILED.RC=rc.

ExplanationThe data space where the trace records aretemporarily stored could not be accessed.


System actionAt least the last trace buffer is lost when the externalwriter is stopped.


System programmer responseAnalyze the return code (see ALESERV in z/OSAuthorized Assembler Service Reference).

ModuleHSAPSTSS

HSAM5190E TCB TOKEN OF PARENT TASKCOULD NOT BE OBTAINED. RC=rc.

ExplanationThe TCB token of the parent task of the start/stoproutine could not be obtained.




System programmer responseAnalyze the return code (see TCBTOKEN in the z/OSAuthorized Assembler Service Reference).

ModuleHSAPSTSS

HSAM5191I PARAMETER WTR=DISCONNECTIS NOT SUPPORTED ON A STARTTRACE COMMAND.

ExplanationThe start/stop routine expects the name of the startupprocedure of the external writer to be used. But itfound the reserved word DISCONNECT.


Operator responseReissue the TRACE command and correct the WTRparameter.




ModuleHSAPSTSS

HSAM5192I INVALID TRACE OPTIONSPECIFIED.

ExplanationThe specified trace options could not be determinedbecause of a parsing error.

System actionThe TRACE command is rejected.

Operator responseReissue the TRACE command and correct the OPTIONparameter. Valid options are ALL or a combination of :

• [B]ase• [COM]munication• [CON]trol• [EN]gine• [EV]ent• [F]ramework• [HA]rdware• [HI]story• [I]nstruction• [L]ock• [M]emory• [REQ]uest• [REX]x• [SCH]edule• [SD]F• [W]orkitem

The options must be separated by a comma.


ModuleHSAPSTSS

HSAM5193I NO TRACE OPTION SPECIFIED.

ExplanationEither the OPTION parameter was omitted, or no valuewas specified for it.


Operator responseSee message HSAM5192I for further information.


ModuleHSAPSTSS

HSAM5194I UNKNOWN TRACE OPTIONFOUND: option.

ExplanationThe start/stop routine found an unsupported traceoption.

The variable option shows the specified traceoption.


Operator responseSee message HSAM5192I.


ModuleHSAPSTSS

HSAM5195E SQA HAS BEEN CORRUPTED. EYE-CATCHER=string.

ExplanationThe start/stop routine detected that the system queuearea has been overwritten by another task or addressspace.






ModuleHSAPSTSS

HSAM5196E NAME/TOKEN token_name COULDNOT BE FOUND.

ExplanationThe start/stop routine could not obtain the address ofthe system queue area (SQA). If the message is issuedas a response to a STOP command, the data spacethat holds the trace buffers before they are passed tothe external writer, can no longer be deleted.

The variable token_name shows the specified tokenname.




ModuleHSAPSTSS

HSAM5197E RETRIEVING NAME/TOKENtoken_name FAILED. RC=rc.

ExplanationThe start/stop routine encountered an error whencalling the MVS service IEANTRT. If the message isissued as a response to a STOP command, the dataspace that holds the trace buffers before they arepassed to the external writer, can no longer bedeleted.

The variable token_name shows the specified tokenname.The variable rc shows the value of the return code.



System programmer responseAnalyze the return code (see IEANTRT in z/OS MVSAuthorized Assembler Service Reference).

ModuleHSAPSTSS

HSAM5198E DATA SPACE CREATION FAILED.RC=rc RSN=rsn.

ExplanationThe start/stop routine could not create the data spaceholding the trace buffers before they are passed to theexternal writer.




System programmer responseAnalyze the return code and the reason code (seeDSPSERV in the z/OS MVS Authorized AssemblerService Reference).

ModuleHSAPSTSS

HSAM5199I LAST TRACE BUFFER COULD NOTBE WRITTEN. RC=rc RSN=rsn.

ExplanationThe start/stop routine encountered an error whenwriting the last trace buffer to the external writersynchronously.






System programmer responseAnalyze the return code and the reason code (seeCTRACEWR in z/OS Authorized Assembler Reference).

ModuleHSAPSTSS

HSAM5200E UNKNOWN KEYWORD FOUND:keyword.

ExplanationA library member (see the preceding IEE252Imessage) or the PARM parameter of the startupprocedure contains a keyword that is not known to theautomation manager.

The variable keyword shows the value of theunknown keyword.



System programmer responseCorrect or delete the keyword depending on where it isspecified.

ModuleHSAPSPLM

HSAM5201E INVALID KEYWORD FOUND:keyword.

ExplanationA library member (see the preceding IEE252Imessage) or the PARM parameter of the automationmanager startup procedure contains a keyword thatwas not spelt correctly.

The variable keyword shows the value of the invalidkeyword.



System programmer responseCorrect the keyword depending on where it isspecified.

ModuleHSAPSPLM

HSAM5202E INVALID KEYWORD VALUEDETECTED: KEYWORD=keywordValue=value.

ExplanationA library member (see the preceding IEE252Imessage) or the PARM parameter of the automationmanager startup procedure contains an invalidkeyword.

The variable keyword shows the name of thekeyword.The variable value shows the value of the invalidkeyword.



System programmer responseCorrect the value of the keyword depending on whereit is specified.

ModuleHSAPSPLM

HSAM5203E VALIDATION ROUTINE moduleNOT FOUND.

ExplanationA keyword validation routine could not be loaded.

The variable module shows the name of themodule.





System programmer responseMake sure that the SA z/OS library SINGLOAD is in theSTEPLIB concatenation of the automation managerstartup procedure and that the module is cataloguedin this library.

ModuleHSAPSPLM

HSAM5204E INVALID KEYWORD DETECTED ATcolumn IN string.

ExplanationThe parse service detected an invalid delimiter of akeyword. The invalid delimiter was found either in alibrary member (see the preceding IEE252I message)or in the PARM parameter of the automation managerstartup procedure.

The variable column shows the column where theinvalid delimiter was detected.The variable string shows the string that containsthe invalid delimiter.

System actionAll keywords of the string string are ignored.


System programmer responseCorrect the delimiter depending on where it isspecified.

ModuleHSAPSPLM

HSAM5205I PROCESSING MEMBER member.

ExplanationThe specified library member (see the precedingIEE252I message) is being processed.

The variable member shows the name of themember being processed.




ModuleHSAPSPLM

HSAM5206E MEMBER member NOT FOUND.

ExplanationThe specified library member resides neither in thelibrary concatenation of DD name HSAPLIB when thismessage is preceded by message IEF761I nor in thelibrary of the PARMLIB concatenation.

The variable member shows the name of themember that could not be found.



System programmer responseEither make sure that the member is available orchange the value of the keyword member to a suffixthat is available. If the default member HSAPRM00cannot be found, copy it from the SA z/OS librarySINGSAMP to a library of the appropriateconcatenation.

ModuleHSAPSPLM

HSAM5207I PARMLIB SERVICE FAILED WHENREADING member, RC=rcReason=rsn.



ExplanationDuring initialization of the automation manager theMVS PARMLIB service failed.

The variable member shows the name of themember being processed when the MVS PARMLIBservice failed.The variable rc shows the value of the return code.The variable rsn shows the value of the reasoncode.



System programmer responseRefer to z/OS MVS Assembler Services Reference forinformation about the reason and return codes.

ModuleHSAPSPLM

HSAM5208I INVALID STRING FOUND INmember: string.

ExplanationThe parser service detected more than one keyword ina single line of a member.

The variable member shows the name of themember where the error occurred.

System actionAll keywords specified in the string are ignored.


System programmer responseCorrect the line in the library member member (see thepreceding IEE252I message)

ModuleHSAPSPLM

HSAM5209I MEMBER member TOO LARGE:

ExplanationThe indicated member contains more than 10240 linesof data.

The variable member shows the name of themember being processed using the MVS PARMLIBservice.

System actionThe data is truncated after line 10239.



ModuleHSAPSIPL

HSAM5210I MEMBER member EMPTY:

ExplanationThe indicated member has no data.


System actionNone.



ModuleHSAPSIPL

HSAM5211I MEMBER member FOUND IN dsn.

ExplanationThe indicated member has been found in the indicateddata set of the PARMLIB concatenation.




The variable dsn shows the data set name that themember has been read from.

System actionNone.



ModuleHSAPSIPL

HSAM5212E I/O ERROR READING MEMBERmember.

ExplanationAn I/O error occurred when trying to read the indicatedPARMLIB member.


System actionNone.


System programmer responseCorrect the problem and re-run the program.

ModuleHSAPSIPL

HSAM5213E VALUE MISSING FOR KEYWORDkeyword.

ExplanationA library member (see the preceding IEE252Imessage) or the PARM parameter of the automationmanager startup procedure contains a keyword thathas no value defined.

The variable keyword shows the name of thekeyword.



System programmer responseCorrect the value of the keyword depending on whereit is specified.

ModuleHSAPSPLM

HSAM5214I THE NEXT MESSAGES APPLY TOMEMBER member.

ExplanationThe library member (see the preceding IEE252Imessage) contains at least one improper specification.This message is followed by further HSAM52nnmessages.

The variable member shows the name of themember being processed using the MVS parmlibservice.




ModuleHSAPSPLM

HSAM5215I THE NEXT MESSAGES APPLY TOPARM STRING.

ExplanationThe PARM parameter of the startup procedurecontains at least one improper specification. Thismessage is followed by further HSAM52nn messages.






ModuleHSAPSPLM

HSAM5300E MESSAGE MODULE module NOTFOUND.

ExplanationThe automation manager initialization routine couldnot load the required message module.

The variable module shows the name of the modulethat could not be found.

System actionThe automation manager terminates.


System programmer responseMake sure that the SA z/OS library SINGLOAD is theSTEPLIB concatenation of the automation managerstartup procedure and that the module is cataloguedin this library. Then, restart the automation manager.

ModuleHSAPICB9

HSAM5301E MESSAGE msgno NOT FOUND INMODULE module.

ExplanationThe message service of SA z/OS could not find theindicated message number in the message module.

The variable msgno shows the message numberthat could not be found in the indicated messagemodule.The variable module shows the name of the modulethat does not contain the indicated messagenumber.



System programmer responseMake sure that the indicated module is in the correctSA z/OS library.

Module Library Concatenation

HSAAMME SINGLINK LNKLST

HSAAMLE SINGLOAD STEPLIB

INGAMYE SINGLINK LNKLST

Verify that this library is part of the correspondingconcatenation. In case two versions of SA z/OS exist inthe concatenation ensure that the latest versionprecedes the older version.

ModuleHSAPSMSG

HSAM5400I logname LOG REQUEST requestFAILED. RC=rc, RSN=reason.

ExplanationThe request request to the log logname ended with theunexpected reason code reason.

System actionProcessing continues. Depending on the reason codethe affected log is marked either permanentlyunavailable:

• 0409• 040A• 080C• 080D• 0813• 081A• 081F• 0820• 082E• 0843• 0850• 0851• 0853• 085D• 0890• 08E2



• 08E3

or temporarily unavailable:

• 0406• 0860• 0861• 0862• 0863• 0864• 0865• 0867• 0868• 0891


System programmer responseSee “return and reason codes” of the related IXG...macro in z/OS MVS Authorized Assembler ServiceReference for further analysis. In case the log ismarked permanently unavailable and the problem canbe solved, start a secondary automation manager andinitiate a takeover. In addition, recycle the affectedNetView(s).

ModuleHSAPSSLG

HSAM5401E SYSTEM LOGGER HASINSUFFICIENT ACCESSAUTHORITY TO log. COMPONENTTRACE.

ExplanationThe system logger address space does not haveaccess authority to the coupling facility structureassociated with the log stream log.

System actionProcessing continues. The log is marked permanentlyunavailable.


System programmer responseMake sure the system logger address space has SAFaccess to the structure. Then, start a secondaryautomation manager and initiate a takeover. Inaddition, recycle the affected NetView(s).

ModuleHSAPSSLG

HSAM5402I STRUCTURE STRNAME IS NOTDEFINED IN THE CFRM POLICY.

ExplanationThe structure strname is not defined in the currentlyactive CFRM policy.



System programmer responseDefine the structure strname in the policy and activatethe policy. Then, start a secondary automationmanager and initiate a takeover. In addition, recyclethe affected NetView(s).

ModuleHSAPSSLG

HSAM5403I STREAM streamname IS NOTDEFINED IN THE LOGR POLICY.

ExplanationThe log stream name streamname has not beendefined in the LOGR policy.





System programmer responseDefine the log stream streamname in the LOGR policy.Then, start a secondary automation manager andinitiate a takeover. In addition, recycle the affectedNetView(s).

ModuleHSAPSSLG

HSAM5404I XES FAILED. DIAG1=XES_RC,DIAG2=XES_RSN.

ExplanationA severe cross-system extended services (XES) errorhas occurred.

System actionProcessing continues. The affected log is markedpermanently unavailable.


System programmer responseAnalyze the XES return code and the XES reason code.

ModuleHSAPSSLG

HSAM5405I text

ExplanationThe message is issued in conjunction with messageHSAM5400I and reason code 081F. The reason codeindicates that the system logger encountered aninternal problem while processing the LOGR coupledata set. The two or more messages represent thecontent of the 'answer area' that must be provided byeach logger request.

System actionNone.



ModuleHSAPSSLG

HSAM5406I Some blocks of log logname havebeen deleted.

ExplanationThe message is issued in conjunction with messageHSAM5400I and the reason codes 0408 and 085C. Tosatisfy a write log request, log blocks older than sixdays have been deleted. The deletion is repeated dayby day until the free space is large enough to satisfythe write request.

The variable logname shows the name of the logthat blocks have been deleted from.

System actionNone.



ModuleHSAPSSLG

HSAM5407I logname LOG IS NOT AVAILABLE.

ExplanationThe system logger address space is not available forthe remainder of this IPL.

System actionProcessing continues. All logs are marked permanentlyunavailable.



ModuleHSAPSSLG



HSAM5408I logname LOG WAS TEMPORARILYUNAVAILABLE FROM from_time TOto_time.

ExplanationWhile the specified log was temporarily unavailable, aWRITE request to the log had to be rejected. After thelog has become available again, this message iswritten to the log documenting that one or moreWRITE requests were not logged.

The variable logname shows the name of the logthat was not available.The variables from_time and to_time show the timespan during which the log was not available.




ModuleHSAPSSLG

HSAM5409I logname LOG HAS BEEN DELETEDFROM THE FIRST GAP.

ExplanationThe message is issued in conjunction with messageHSAM5400I and the reason codes 0402, 0403, 0836,and 084B. The log has been deleted from the first gapbeing detected when reading the log from the mostrecent data to the earliest data. One reason could bethat the log stream has been defined with an incorrectVSAM share option, for example, SHR(1 3).

System actionNone.


System programmer responseCheck and correct the VSAM definitions of the affectedlog stream.

ModuleHSAPSSLG

HSAM5410E logname LOG REQUEST requestFAILED. RC=rc, RSN=reason,Type=type.

ExplanationThe request request to the log logname ended with theunexpected reason code reason.

System actionProcessing continues. The log logname is markedpermanently unavailable.


System programmer responseCheck the system log for associated IXG prefixedmessages. Check the relevant zOS MVS SystemMessages manual for the IXG message details. If youcannot resolve the problem, contact your IBM SupportCenter.

ModuleHSAPSSLG

HSAM5411I logname LOG HAS BEEN DELETED.

ExplanationThe message is issued in conjunction with messageHSAM5400I and the reason codes 0405, 0407, 0408,and 085C. The whole log must be deleted to satisfy awrite log request.

System actionNone.



ModuleHSAPSSLG



Chapter 9. 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

ExplanationSA z/OS detected an error.

The variable aaaa shows the service or commandthat failed.The variable bb shows the value of the return code.The variable ccccccccc shows the value of thereason code.

System actionNone.

Operator responseIf an INGOMX error occurred, see the online commandhelp of INGOMX or see the "INGOMX" topic in IBM ZSystem Automation Programmer's Reference for furtherdetails about the return code.

If a NetView command error occurred, see theappropriate IBM Z NetView manual.

In all other cases, contact IBM Support.

System programmer responseFor service HSAPRHFR, see the "Configure the SystemLogger" topic in IBM Z System Automation Planningand Installation for instructions of how to correctly setup for logging with the system logger. Also, ensure thatthe LOGSTREAM parameter that is specified in theautomation manager's parameter file HSAPRMxx andin the automation agent's DSIPARM memberINGXINIT are identical.

For service INGPXMEM, ensure that SA z/OS has beeninitialized correctly and that the data service taskINGPXDST is active. When the common globalAOFINIT is set to a value greater than 0, the basicinitialization completes successfully. When AOFINIT isnot set, no initialization is attempted. In this case,ensure that AOFRANTL is called as an initial commandout of your NetView stylesheet (CNMSTYLE).Otherwise, examine the netlog for messages that areissued during initialization and correct the errors.

If task INGPXDST is not active, try to start the task byusing:

START TASK=INGPXDST

.

ING002I name IS NOT A SECONDARYAUTOMATION MANAGER

ExplanationThe specified command or action is only applicable fora secondary automation manager.

The variable name shows the name of theautomation manager that is not defined assecondary automation manager.


Operator responseSpecify the correct automation manager name andreissue the command.

ING003I name IS NOT A PRIMARYAUTOMATION MANAGER

ExplanationThe specified command or action is only applicable forthe primary automation manager.

The variable name shows that name of theautomation manager that is not defined as primaryautomation manager.



ING004I REQUEST request SUBMITTED

Messages ING001I to INGY1336I


ExplanationThe request to update the operation mode of thedesignated automation manager has been submittedunder this task or another work operator.

The variable request shows the submitted request.


ING005I RESOURCE name IS AMBIGUOUS

ExplanationThere is more than one resource with the specifiedname within the domain of the automation manager incharge. Because the command is running in line mode,SA z/OS is unable to determine which of the resourcesthe command should be applied to.

The variable name shows the name of the resourcethat is not unique.


Operator responseSpecify the fully qualified resource name and reissuethe command.

ING006I THERE IS NO RESOURCE name

ExplanationNone of the resources defined in the sysplex matchesthe specified name pattern.

The variable name shows the name of the resourcethat could not be found.

System actionNone.

Operator responseCorrect the name of the resource and reissue thecommand.


ING007I name IS NOT AN APPLICATIONGROUP

ExplanationThe display "group members" action was requestedfor a resource that is not an application group.

The variable name shows the name of the resourcethat is not an application group.

System actionNone.


ING008I name SERVICE FAILED,RC=return_code, REASON=reason.

ExplanationA service routine was called that ended with a non-zero return code.

The variable name shows the name of the functionthat encountered the error. For function INGSTX,see the online command help of INGSTX or see the"INGSTX" topic in IBM Z System AutomationProgrammer's Reference for further details.The variable return_code shows the return codethat the failing service routine returned.The variable reason shows descriptive text aboutthe cause of the error.



System programmer responseDetermine why the service routine failed and correctthe problem. Examine the netlog for additionalinformation.

For REASON=TIMEOUT, see the "Work Item Statistics"and "Workitem Queue Monitoring" topics in "AppendixC. Problem Determination" of IBM Z SystemAutomation User's Guide.

The information there can help you to understandbetter the automation manager's workload andperformance. TIMEOUT means that the automationagent stops waiting for a command response from theautomation manager after the specified wait time. Thewait time is controlled by the WAIT parameter that isavailable for most commands, (INGLIST, INGREQ,



WAIT= nnn | NO). The default wait time is 30 secondsbut you can adjust it. For details, see the "ParameterDefaults for Commands" topic in IBM Z SystemAutomation Customizing and Programming.

In addition, the INGRPT command providesinformation about the automation manager'sperformance from a statistical point of view, like thetotal number of timeouts, average wait time, maximumwait time.

ING009I UPDATE OF parameterCOMPLETED; SET TO value

ExplanationThe requested function has been successfullycompleted.

The variable parameter shows the name of theparameter that was updated.The variable value shows the new value of theparameter.

System actionNone.


ING010I warning/error information

ExplanationThe variable warning/error information showsdescriptive text from the automation managerabout the cause of the error.

System actionNone.


ING011I CONFLICT DETECTED BETWEENUP AND DOWN TIMESLOTS

ExplanationThere is an overlap between an UP time slot and aDOWN time slot.

System actionNone.

Operator responseCorrect the time specification.

ING012I name IS NOT AN AUTOMATIONMANAGER

ExplanationThe specified command or action is only valid for anautomation manager.

The variable name shows the name of the systemwhere the command could not be processed.



ING013I PARAMETER parameter_name ISNOT APPLICABLE FORRESOURCES OF TYPE type

ExplanationThe specified parameter is not valid for resources ofthe specified type.

The variable parameter_name shows the name ofthe parameter that is not valid.The variable type shows the type of the resource.


Operator responseCorrect the format and reissue the command.

ING014I CONFLICTING PARAMETERSSPECIFIED.

ExplanationSelf-explanatory.




Chapter 9. Messages ING001I to INGY1337I 269

ING015I NO MATCHING REQUEST FOUNDFOR resource - SOURCE=sourceREQUEST=request

ExplanationAn INGSET CANCEL was issued but the requestidentified by its type and source does not exist.

The variable resource shows the name of theresource.The variable source shows the name of the source.The variable request shows the name of the requestthat could not be found.



ING016I SCOPE=scope IS NOT VALID FORtype REQUEST

ExplanationThe specified scope is not valid for the type of request.

The variable scope shows the scope that wasspecified for the request.The variable type shows the type of the request.



ING017I EXPIRATION TIME timestamp HASPASSED ON system

ExplanationThe specified expiration date or time is in the past.

The variable timestamp shows the specifiedtimestamp.The variable system shows the name of the system.


Operator responseSpecify an expiration time or date that is in the futureand reissue the command.

ING018I ONLY ONE GROUP ALLOWED FORACTION action

ExplanationYou specified more than one group name for anINGGROUP action of ADJUST or MEMBERS.

The variable action shows the action that could notbe performed.


Operator responseSpecify only one group name and reissue thecommand.

ING019I REQUESTED ACTION IGNOREDFOR RESOURCE resource

ExplanationAn INGGROUP ACTION EXCLUDE, AVOID, DEFAULT, orINCLUDE was requested for a group of nature basic.




ING020I DATASET datasetname NOTFOUND OR NOT ACCESSIBLE

ExplanationEither the specified data set does not exist, or it is notaccessible, or, if it is a configuration data set it is not aPDS.

The variable datasetname shows the name of thedata set that is not available.

System actionNone.



Operator responseCorrect the name of the data set and reissue thecommand.

ING021I STATISTICS COUNTERS RESET ONSYSTEM sysname

ExplanationThe statistics counts have been reset on the specifiedsystem.

The variable sysname shows the name of thesystem whose statistics counts were reset.



ModuleINGRVRPX

ING022I THRESHOLD SETTINGS FORresource CANNOT BE DELETED

ExplanationThe threshold settings for DEFAULTS, MVSESA andSUBSYSTEM cannot be deleted.

The variable resource shows the name of theresource that the threshold settings cannot bedeleted for.

System actionNone.


ModuleINGRYTH0

ING023I command COMMAND NOTALLOWED TO RUN UNDER taskTASK.

ExplanationThe specified command cannot run under thespecified task.

The variable command shows the name of thecommand that cannot be run.The variable task shows the name of the task thatthe command cannot be run under.


Operator responseReissue the command under another task.

ModuleINGRYRPX

ING024I DELETION OF INTERNAL REQUESTIS NOT ALLOWED.

ExplanationThe selected request is created by the automationmanager due to:

1. Vote propagation for an application group. Thisrequest cannot be canceled. It will be automaticallyremoved when the vote that initiated the request isremoved.

2. A service period UP or DOWN window. This requestcannot be canceled. It will be automaticallyremoved when the UP or DOWN window ends.

System actionNone.


ING025I OUTBOUND CONNECTION WITHDOMAIN domain RUNNINGproduct ESTABLISHED.

ExplanationThe local system has established a communicationpath 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 runningon the remote system.

System actionNone.




ING026I ROUTINE clistname SENT TODOMAIN domain LEVEL clist_level.

ExplanationThe local system has sent the current version of theINGRVXMT slave routine to the remote system. Thisenables the local system to communicate with theremote system via the "remote procedure call"technique rather than NNT sessions.

The variable clistname is the name of the slaveroutine.The variable domain identifies the remote systemby its domain ID.The variable clist_level shows the last APARnumber, if present, and compile date.

System actionNone.


ING027I SLAVE ROUTINE clistnameRECEIVED FROM DOMAIN domainRUNNING product LEVELclist_level.

ExplanationAnother system, identified by its domain ID, has sent aslave routine to communicate with the local system viathe "remote procedure call" technique rather thanNNT sessions.

The variable clistname is the name of the slaveroutine.The variable domain is the domain ID of the remotesystem.The variable product is the SA z/OS release levelrunning on the remote system.The variable clist_level shows the last APARnumber and compile data of the slave routine.

System actionNone.


ING028I command: PARAMETER parameterMISSING OR INVALID value

ExplanationThe specified parameter is either wrong or missing.

The variable command is the name of the commandbeing processed.The variable parameter is the parameter that isinvalid or missing.The variable value is the value of the parameterthat is wrong.

System actionNone.


ING029I SLAVE ROUTINE clistname ISCOMPILED. CANNOT BE SENT TODOMAIN domain

ExplanationBecause the clist that is named in the message iscompiled, it cannot be sent to the remote system. Thisis done for two reasons:

1. The REXX runtime library might not be installed onthe remote system.

2. The compiled REXX routine does not contain anyindication of its software level (release number, lastAPAR).

The variable clistname is the name of the slaveroutine.The variable domain identifies the remote systemby its domain ID.

System actionNone.


ING030I Group group_name cannot bemoved to another system - reason

ExplanationAn attempt was made to move the group away fromthe system that it currently runs on, but no othersystem is available.



The variable group_name is the move groupconcerned.The variable reason explains in more detail why thegroup cannot be moved.

System actionNone.



ING031I EVENT SUBSCRIPTIONCONSUMER name IS UNKNOWN.

ExplanationThe consumer specified in the INGEVOBS call is notdefined, which means that the consumer is notregistered.

The variable name is the name of the consumer asspecified in the INGEVOBS command.

System actionThe command is rejected.

Operator responseReenter the correct command, if applicable or registerthe consumer first.

ClassesNone.

ING032I AVAILABILITY TARGET avtgtCANNOT BE LESS THAN THESATISFACTORY TARGET sattgt

ExplanationYou have specified either a satisfactory target valuethat is larger than the availability target, or anavailability target that is less than the satisfactorytarget assigned to the server group.

The variable avtgt is the availability target assignedto the group.The variable sattgt is the satisfactory targetassigned to the group.



ClassesNone.

ING033I INBOUND SESSION STATUSCORRECTED FOR domain. SETstatus

ExplanationThe gateway monitoring routine found an inboundsession status that does not match the actual status.The session status is corrected.

The variable domain is the name of the domain thatthe local system has an inbound session with.The variable status is the new inbound sessionstatus.



ClassesNone.

ING034I STATUS stat OF SUBSYSTEMsubsys IS NOT VALID FORFUNCTION function

ExplanationAOFRYSAB was called to perform a function for asubsystem. The status of the subsystem does notallow this function.

The variable stat is the current status of thesubsystem.The variable subsys is the subsystem that thefunction is to be performed on.The variable func is the function that is to beperformed

System actionThe function is not performed.




ClassesNone.

ING035I system_name IS NOT A VALIDSYSTEM FOR GROUP group_name

ExplanationThe specified system name is either unknown or not avalid choice for the group.

The variable system_name is the invalid systemname.The variable group_name is the move groupconcerned.

System actionNone.

Operator responseSpecify a valid system that the group can be moved to.

ModuleINGRYMV0

ClassesNone.

ING036I GROUP group_name CANNOT BEMOVED TO SYSTEM system_name -reason

ExplanationYou attempted to move the group to the specifiedsystem either now or at the next recycle, but one of thefollowing conditions is true:

• The system is down or System Automation is notfully initialized.

• The member on that system is not startable.• The group is already running on that system.

System actionNone.

Operator responseSpecify another system that the group should bemoved to.

ModuleINGRYMV0

ClassesNone.

ING037I GROUP group_name CANNOT BEBOXED - NOT ACTIVE

ExplanationYou attempted to box the group but the applicationgroup is not active.

System actionNone.


ModuleINGRYMV0

ClassesNone.

ING038I CONFLICTING PARAMETERS ORVALUES SPECIFIED => p1 - p2

ExplanationThe specified parameters (or their values) conflict.

The variable p1 is the first invalid parameter.The variable p2 is the second invalid parameter.

System actionNone.

Operator responseReenter the command with valid parameters.

ModuleINGRYST0



ClassesNone.

ING039I SESSION name IS UNKNOWN

ExplanationThe specified session is not defined in theconfiguration file (ACF).

The variable name is the session name.

System actionNone.

Operator responseReenter the command with a valid session name.

ModuleINGRVSS0

ClassesNone.

ING040I THE FOLLOWING IS MISSING:keywords

ExplanationA command was entered but one or more requiredparameters were not specified.

The variable keywords shows a list of all the missingparameters.


Operator responseEnter the command again and specify the requiredparameters.

ClassesNone.

ING041I ONE OF THE FOLLOWING ISMISSING: keywords

ExplanationA command was entered but a required parameterwas not specified.

The variable keywords shows a list of possibleparameters to be specified.


Operator responseEnter the command again and specify one of thesuggested parameters.

ClassesNone.

ING042I keyword1 MUST BE SPECIFIEDWITH keyword2

ExplanationA command was entered but one of its parametersrequires another one to be also specified.

The variable keyword1 shows the parameter thatrequires keyword2 to be specified.The variable keyword2 shows the additionalparameter that is required.


Operator responseEnter the command again and specify the missingparameter.

ClassesNone.

ING043I keyword1 MUST NOT BESPECIFIED WITH keyword2

ExplanationA command was entered but one of its parametersdisallows another one to be also specified.

The variable keyword1 shows the parameter thatexcludes the use of keyword2.The variable keyword2 shows the parameter that isexcluded by the use of keyword1.




Operator responseEnter the command again and specify either keyword1or keyword2.

ClassesNone.

ING044I keyword1 MUST BE GREATERTHAN OR EQUAL TO keyword2

ExplanationA command was entered with two parameters. Thetwo values define a range. The second value must begreater than or equal to the first value.

The variable keyword1 shows the parameter thatdefines the end of the range.The variable keyword2 shows the parameter thatdefines the start of the range.


Operator responseEnter the command again and specify a value forkeyword1 that is greater than or equal to the valuegiven for keyword2.

ClassesNone.

ING045I keyword MUST BE IN THE FORMATformat

ExplanationA command was entered with a parameter thatrequires a certain data format.

• The variable keyword shows the parameter thatrequires the format.

• The variable format shows the format that isrequired as one of the following, or any other self-explanatory text:MM/DD/YYYY

A valid date in the form month/day/yearHH:MM

A valid time in the form hour:minuteCn

1–n charactersDn

1–n numeric digits

Note that there might be additional lines that explainthe problem in further detail.


Operator responseEnter the command again and specify a value thatconforms to the required format.

ClassesNone.

ING046I keyword MUST BE ONE OF THEFOLLOWING: list

ExplanationA command was entered with a parameter thatrequires a certain value.

The variable keyword shows the parameter thatrequires the value.The variable list shows a list of valid values that theparameter can take.


Operator responseEnter the command again and specify a value from thelist.

ClassesNone.

ING047I keyword MUST BE IN THE RANGEFROM from TO to

ExplanationA command was entered with a parameter that mustbe in a certain range.

The variable keyword shows the name of theparameter that must be in the range.The variable from shows the lowest possible value.The variable to shows the highest possible value.




Operator responseEnter the command again and specify a value in thegiven range.

ClassesNone.

ING048I subsystem NOT DEFINED AS typeSUBSYSTEM

ExplanationThe specified subsystem is not of the required type.

The variable subsystem identifies the subsystem.The variable type defines the type (CICS, IMS, etc.).

System actionNone.

Operator responseSpecify a valid subsystem of the required type.

ClassesNone.

ING049I No xxxx data to display forsubsystem

ExplanationThere are no commands specified in the policy for thespecified subsystem.

The variable xxxx identifies the keyword that nocommands have been defined for. It can beDISPINFO, IMSINFO, or CICSINFO.The variable subsystem identifies the subsystem.

System actionNone.


ClassesNone.

ING050I HBEAT BEAT parameter

ExplanationA heartbeat was issued.

The variable parameter shows the parameters thatwere specified with the heartbeat.




ING051I HBEAT RECV parameter

ExplanationA heartbeat was received.

The variable parameter shows the parameters thatwere specified.




ING052I HBEAT FAIL parameter

ExplanationA heartbeat with the specified parameters failed.

The variable parameter shows the parameters ofthe failed heartbeat.






ING053I HBEAT SDWN parameter

ExplanationA heartbeat with the specified parameters is shutdown.

The variable parameter shows the parameters ofthe shutdown heartbeat.




ING054I MAJOR RESOURCE object nameCANNOT BE FOUND

ExplanationAn invalid major resource was specified for thecreation of a minor resource.

The variable object name shows the name of theresource that could not be found.

System actionProcessing continues unless no replacement anchorcan be found.


System programmer responseIf the originator is a customized INGPOST call, correctthe call. If not, contact your IBM Support Center.

ING055I INVALID 'STATE=state'CONVERTED TO 'STATE=ALERT'

ExplanationAn invalid state was specified in the INGPOST call. Thestate is converted to 'ALERT'.

The variable state shows the incorrect state thatwas converted to 'ALERT'.




ING057I command FAILED, GENALERTTEXT PARAMETER LONGER THAN244 CHARS

ExplanationThe resulting GENALERT parameter string exceeds themaximum length for GENALERTs.

The variable command shows the command thatcould not be executed.

System actionThe command is canceled.



ING058I module function UNEXPECTEDRESPONSE FROM service function :return code

ExplanationThe service called for the specified function returnedan unexpected return code.

The variable module shows the name of the modulewhere the error occurred.The variable function shows the name of functionthat called the service.The variable service shows the service that wascalled.The variable function shows the function of theservice that was called.The variable return code shows the value of thereturn code that was issued.






ING059I USERSTATUS FOR OBJECT objectUPDATED TO status value (statusname)

ExplanationThe status of the object has been set to the referredvalue.

The variable object shows the object whose statuswas updated.The variable status value shows the status value ofthe object.The variable status name shows the status name ofthe object.




ING060I USERDATA FOR OBJECT objectUPDATED: value

ExplanationThe user data of the object has been updated to thespecified value.

The variable object shows the object whose statuswas updated.The variable value shows the new status of theobject.




ING061I INGPOST command NOT ALLOWEDFOR OBJECT object

ExplanationThe specified INPOST command is not allowed for theobject.

The variable command shows the name of theINGPOST command that is not allowed for theobject.The variable object shows the name of the resourcethat the command is not valid for.




ING062I command mode PROCESSINGSTARTED

ExplanationThe command with the specified mode has started.

The variable command shows the name of thecommand that processing started for.The variable mode shows the mode of thecommand.




ING063I command mode PROCESSINGCOMPLETED RC return code

ExplanationThe command with the specified mode completed.

The variable command shows the name of thecommand that processing completed for.



The variable mode shows the mode of thecommand.The variable return code shows the value of thereturn code that was issued. A non-zero returncode indicates that the command was in error.


Operator responseIn case of a non-zero return code inform your systemprogrammer.

System programmer responseIn case of a non-zero return code investigate forproceeding.

ING064I ISSUING: command

ExplanationThe command is issued by the command router.

The variable command shows the name of thecommand that is being issued.




ING066I COMMAND NOT ISSUED: reason

ExplanationThe command could not be executed.

The variable reason shows the reason why thecommand could not be executed.


Operator responseMake sure the specified command was valid within thecontext. If it was valid, inform your systemprogrammer.

System programmer responseInvestigate the cause of the failure and take theappropriate steps.

ING068I CHANGES WILL BE LOST - PRESSfunction_key TO ACTIVATE

ExplanationAt least one group policy attribute has been modifiedbut not yet committed.

The variable function_key is the function key thatactivates the group policy change.

System actionNone.

Operator responsePress the appropriate function key to commit thechanges.


ING069E ERROR LOADING topo file - reason

ExplanationThe interpretation of the topo file could not beprocessed successfully.

The variable topo file shows the name of the topofile that could not be loaded.The variable reason shows the reason why the topofile could not be loaded.



System programmer responseCheck the topo file for the specified failure.

ING070E UNEXPECTED RESPONSE FROMsystem RC return code

ExplanationThe processing of a remote command on the specifiedsystem returned an unexpected return code.



The variable system shows the name of the systemthe returned the return code.The variable return code shows the value of thereturn code.

System actionProcessing continues, unless it was the last targetsystem in the sysplex to make contact with.

Operator responseCheck the final message ING063I and act according toits state.


ING072E INITIAL COMMUNICATION WITHsystem FAILED

ExplanationThe attempt to communicate with the specifiedsystem was unsuccessful.

The variable system shows the name of the system.



System programmer responseInvestigate the cause of the failure and take theappropriate steps.

ING074I RESOURCE resource HAS THESTATUS BOXED

ExplanationThe desired action cannot be performed. The indicatedresource has the status BOXED which cannot beoverruled.

The variable resource shows the name of the resource.

System action:The action is rejected.



ING075I RESOURCE resource IS NOTSELECTABLE. RSN=reason

ExplanationThe desired action cannot be performed. The resourceis not available ("Non-Startable") for the indicatedreason.

The variable resource shows the name of theresource.The variable reason shows the reason for theunavailability.

System action:The action is rejected.



ING076I ACTION action IS NOTSUPPORTED BY THE RESOURCE

ExplanationThe indicated action is not supported by the groupmodel of the resource.

The variable action shows the value of the parameterACTION.

System action:The command is rejected.

Operator response:Retry the command using an ACTION parameter thatis accepted by the resource.


ING077I module VERSION version IS NOTSUPPORTED BY slave

ExplanationThe indicated module tries to execute the commandon a target system that runs an SA agent with higherversion, release, or modification level. The data thatshould be returned cannot be processed by the localsystem.

The variable module shows the name of the localsystem's module.The variable version shows the version of the localsystem's module in the format VvRrMm.The variable slave shows the name of the targetsystem's module.

Note: This message is logged on the target system.

System action:



The command is rejected.

Operator response:Retry the command using a resource that is acceptedby both systems.


ING078I NO MEMBERS ARE DEFINED FORTHE GROUP

Explanation:The command did not find any member defined for thegroup. Note that some other information is notavailable as well due to the empty group.

System action:The command continues.



ING080I Monitor_name Session_nameLogon_type Exception_text

ExplanationING080I is issued on behalf of a monitor resource thatuses the monitor command INGMTRAP to define atrap for one or more OMEGAMON® exceptions. It isissued for each exception that trips.

Monitor_name is the fully qualified monitorresource name in the format monitor_name/MTR/system_name, which indicates the monitorresource that this exception message was issuedfor. Note that monitor_name is known toINGMTRAP through the task global &SUBSAPPL.Session_name is the name of the OMEGAMONsession as it was specified by the NAME keywordon the INGMTRAP command.Logon_type is the type attribute used by theOMEGAMON session named Session_name asdefined in the automation policy.Exception_text is the exception text as returned byOMEGAMON without the leading ‘+’ sign.

ING081I Monitor_name Session_nameLogon_type NO EXCEPTION FOUND

ExplanationMessage ING081I is never issued to an operatorconsole, but is written to a monitor resource’s history.This happens when the monitor resource uses themonitor command INGMTRAP to define a trap for oneor more OMEGAMON exceptions and no exception hastripped.

Monitor_name is the fully qualified monitor name inthe format monitor_name/MTR/system_name,which indicates the monitor resource that thisexception message was issued for. Note thatmonitor_name is known to INGMTRAP through thetask global &SUBSAPPL.Session_name is the name of the OMEGAMONsession as it was specified by the NAME keywordon the INGMTRAP command.Logon_type is the type attribute used by theOMEGAMON session named Session_name asdefined in the automation policy.

ING082I NO SESSION OPERATORS HAVEBEEN DEFINED – OMEGAMONSESSION INITIALIZATIONTERMINATED.

ExplanationThe installation failed to define session operatorentries in the automation policy.

System actionAutomation initialization continues.


System programmer responseMake sure you have defined at least one sessionoperator AOFSESnn in the automation policy andassigned it to an automation operator, for example,AUTSESnn.

ING083I COMMAND command ISSUED BYoperator IN SESSIONsession_name.

ExplanationMessage ING083 is issued each time a list of one ormore commands is sent to the OMEGAMON sessionthat is denoted by session_name.

command is the first command in the list ofcommands that was issued with the INGOMX API.operator is the operator or automation operatorthat issued the command.session_name is the name of the OMEGAMONsession that is to receive the command.

System actionNone.





ING084I REQUEST FOR OMEGAMONSESSION session_name FAILED.REASON CODE rsn

ExplanationSA z/OS failed to communicate with the OMEGAMONsession denoted by session_name. The variable rsncontains more specific error information.

System actionThe request is not executed.


System programmer responseThe reason code, rsn, provides details about the causeof the failure. It is in hexadecimal encoding and it canbe any of the following:00000001 (Authentication unsuccessful)

The userid defined for this session is not permittedto log on to OMEGAMON. Possible reasons are:

• The user ID is invalid.• The password is invalid.• SAFPW was specified as the password, but no

password data set was specified in the NetViewstartup procedure.

• SAFPW was specified as the password, but thepassword found in the password data set iseither invalid, does not exist, or was fetchedusing an invalid owner. See IBM Z SystemAutomation Planning and Installation forinformation about how to set up your securityenvironment to use this function.

00000002 (Not an OMEGAMON session)The session that was established between SA z/OSand the VTAM® APPLID defined for this session isnot an OMEGAMON session. Validate and, ifnecessary, correct your session definitions in thecustomization dialog.

00000003 (VTAM not available)VTAM was not active at the time the INGOMX APIwas invoked.

00000004 (Timeout occurred)The request was interrupted due to a timeout thathas been specified for this session. Either thetimeout is too aggressive or too few sessionoperators are defined to handle all assignedsessions.

00000005 (Password update failed)The password of the user defined for this session iscontrolled by the system using SA z/OS passwordprotection feature. Command INGPW failed toupdate the password in the SA z/OS password dataset after OMEGAMON authentication with the newpassword.

Reset the session user's OMEGAMON passwordand re-initialize the system-controlled password inthe SA z/OS password data set using INGPW.

00000006 (TAF fullscreen session not established)NetView could not create a Terminal AccessFacility (TAF) fullscreen session using theBGNSESS command. Refer to the netlog foradditional messages issued by NetView.

0001nnnn (ATTACH of VOST failed with RC=nnnn)SA z/OS failed to attach a virtual terminal. Refer tothe NetView ATTACH command description fordetails of the return code represented by nnnn inbytes 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 tothe NetView DETACH command description fordetails of the return code represented by nnnn inbytes 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.

ING085I OMEGAMON SESSIONsession_name {STARTED |STOPPED}. NEW STATE IS status.

ExplanationMessage ING085I is issued each time SA z/OSestablished or destroyed an OMEGAMON session,denoted by session_name.

The action can be either of the following:

• STARTED

The session was started.• STOPPED

The session was stopped.

The current status is indicated in variable status.



System actionNone.



ING087I task_name: PPI RECEIVERreceiver_name READY

ExplanationThe task task_name has initialized completely and thePPI receiver named receiver_name is ready forprocessing requests.

System actionProcessing continues



ING088I task_name: PPI RECEIVERreceiver_name TERMINATED

ExplanationThe task task_name has deleted the PPI receivernamed receiver_name. No more requests can beprocessed.

System actionProcessing terminates



ING089I task_name: INVALID BUFFERRECEIVED, DATA DROPPED.RELATED INFO: request_data

ExplanationThe PPI receiver owned by the task task_namereceived an invalid request buffer. The first 64 bytesare dumped with the message in the variablerequest_data.

System actionProcessing continues


System programmer responseEnsure that only the SA z/OS monitoring agent issending requests to the PPI receiver that is owned bythe task task_name.

ING090I TASK task_name IS NOW ACTIVE

ExplanationThe task task_name has been activated.




ING091I task_name ALREADY ACTIVE ORIN PROCESS OF BECOMINGACTIVE

ExplanationYou started the task task_name but the task is alreadyactive or in the process of becoming active.






ING092I task_name: service_nameSERVICE FAILED, RC=rc. ERRORINFORMATION: error_info

ExplanationDuring the execution of the service service_name, anerror occurred. The variable error_info indicates inwhat context the service was invoked by the tasktask_name.

For detailed error information, see NetView:Customization - Using Assembler. In the case ofNetView Program-to-Program Interface (PPI) errorssee NetView: Application Programming Guide for moreinformation related to the service return code rc.



System programmer responseDetermine why the service routine failed and correctthe problem. Examine the netlog for additionalinformation. If necessary, contact your local IBMSupport Center for further assistance.

ING093I task_name: INVALID KEYWORDOR SYNTAX ERROR. RELATEDINFORMATION: error_info

ExplanationAn invalid keyword or value was specified in theinitialization member for the task task_name. Relatederror information is provided in the variable error_info.



System programmer responseSee "Step 2. Configure SA z/OS and NetView" in thechapter "Beginning the installation and configuration"in Service Management Unite Automation Installationand Configuration Guide for a list of valid keywords andvalues and correct the problem.

ING094I TASK task_name HASTERMINATED

ExplanationThe task task_name has terminated.




ING095I task_name: NO ACTIVE OPERATORFOUND

ExplanationThe PPI receiver owned by task task_name received arequest for monitoring data but could not find anactive automation operator to process the request.

System actionThe message is sent back to the requestor andprocessing continues.


System programmer responseRefer to IBM Z System Automation Monitoring AgentConfiguration and User's Guide for instructions how toset up automation operators for this function andcorrect the problem.

ING096I function : text

ExplanationDuring processing the function request for monitoringdata any of the following errors as indicated by textoccurred. Examples for text are:

• NetView RC rc from: command• Timeout occurred• ING008I …



System actionThe message is sent back to the requestor andprocessing continues.


System programmer responseIf text contains an existing SA z/OS message ID, referto the message help for problem resolution.

In case of a timeout, increase the time allotted for thelongest request.

For return codes returned by SA z/OS or NetViewservices refer to related documentation or contactyour local IBM Support Center for further assistance.

ING101I subsystem CONNECTION TOextsysid (connection_id) IS DOWN.

ExplanationWhen monitoring a connection between a subsystemand a DB2® or IBM MQ external subsystem, theconnection was determined to be in the status notconnected.

The variable subsystem shows the subsystem nameas defined in SA z/OS.The variable extsysid shows the external subsystemID of DB2 or IBM MQ.The variable connection_id identifies the affectedconnection.

System actionNone.

Operator responseCheck whether the subsystem is not connected to theexternal subsystem as a result of normal operation. Ifit is not, investigate why the connection is not up.


ING102I subsystem CONNECTION TOextsysid (connection_id) IS UP.

ExplanationWhen monitoring a connection between a subsystemand a DB2 or IBM MQ external subsystem, the

connection was determined to be in the statusconnected.

The variable subsystem shows the subsystem nameas defined in SA z/OS.The variable extsysid shows the external subsystemID of DB2 or IBM MQ.The variable connection_id identifies the affectedconnection.

System actionNone.



ING103I THREADS COULD NOT BETERMINATED FROM subsystem

ExplanationThis message introduces a list of ING104I messagesthat show threads that remain with a DB2 master aftera thread termination process has completed.

The variable subsystem shows the name of the DB2master that threads could not be terminated for.

System actionThe requested function could not be performed.

Operator responseInvestigate why the threads that are listed in thefollowing ING104I messages could not be terminatedand retry the termination command.


Classes40, 44.

ING104I connection_ID THREADcorrelation_ID ddf_ID

ExplanationThis message shows a thread that remains with a DB2master after a thread termination process has



completed. It is part of a multiline message thatbegins with message ING103I.

The variable connection_ID shows the connectionID of a thread that could not be terminated.The variable correlation_ID shows the correlationID of a thread that could not be terminated.The variable ddf_ID shows the token associated toa distributed database access thread that could notbe terminated.

System actionThe requested function could not be performed.

Operator responseInvestigate why the indicated thread could not beterminated and retry the termination command.


ClassesNone.

ING106I INDOUBT THREADS EXIST FORname

ExplanationThere are indoubt threads existing with the DB2subsystem named in the message. The message isgiven when invoking the INGDB2 command checkingfor indoubt threads.

Variable name identifies the DB2 subsystem.



ING108I NO THREADS LEFT IN subsystem.

ExplanationThere are no threads left with this DB2 subsystem forthe thread termination process to cancel.

The variable subsystem identifies the DB2subsystem.

System actionNone.



Classes40, 44.

ING109E thread_number THREADS COULDNOT BE TERMINATED FROMsubsystem.

ExplanationThreads remain with this DB2 subsystem after thethread termination process has completed.

The variable thread_number shows the number andtype of threads.The variable subsystem identifies the DB2subsystem.

System actionNone.


System programmer responseInvestigate why the number of indicated threads arenot terminated and retry the termination command.

Classes40, 44.

ING112I YOUR TSO DB2 (subsystem)THREAD IS ABOUT TO BETERMINATED BY AUTOMATION.

ExplanationThis message is broadcast to effected TSO users dueto a DB2 thread termination request.




System actionNone.



Classes40, 43.

ING113I YOUR TSO DB2 (subsystem)THREAD HAS BEEN TERMINATEDBY AUTOMATION.

ExplanationThis message is broadcast to effected TSO users as aresult of a DB2 thread termination request.


System actionCancels the TSO users of the indicated DB2subsystem.



Classes40, 43.

ING114E jobname CANCELLED BYAUTOMATION DUE TO subsystemTHREAD TERMINATION.

ExplanationThis message is issued for batch job cancellations dueto a DB2 thread termination or DB2 shutdown process.

The variable jobname identifies the DB2 batch job.The variable subsystem identifies the DB2subsystem.

System actionCancels the batch job for the indicated DB2subsystem.



Classes40, 44.

ING127A THREADS FOUND AFTER LASTCYCLE OF DB2 (subsystem), FORCESHUTDOWN.

ExplanationAfter the final cycle (as defined by the DBITTH timeoutvariable), threads were still found to exist for this DB2subsystem.


System actionNone.


System programmer responseInvestigate why this process has not been able toterminate existing threads. If this DB2 needs to beshut down use the FORCE option.

Classes40, 44.

ING129E jobname CANCELLED.TABLESPACE dbname.tsname(subsystem) NEEDED TO BESTOPPED

ExplanationThe job was canceled due to a tablespace that neededto be stopped.

The variable jobname shows the job name for thejob canceled.The variable dbname.tsname identifies thetablespace.The variable subsystem identifies the DB2subsystem.



System actionThe identified tablespace is stopped and the job iscanceled.



Classes40, 44.

ING130I TABLESPACE dbname.tsname(subsystem) IS TO BE STOPPED.PLEASE STOP USING IT.

ExplanationThe tablespace indicated is being stopped.

The variable dbname.tsname identifies thetablespace.The variable subsystem identifies the DB2subsystem.

System actionThe identified tablespace will be stopped.



Classes40, 43.

ING131I YOU WERE CANCELLED,TABLESPACE dbname.tsname(subsystem) IS TO BE STOPPED.

ExplanationThe indicated tablespace is being stopped andoperator sessions using it are canceled.

The variable dbname.tsname identifies thetablespace.The variable subsystem identifies the DB2subsystem.

System actionThe operator session is canceled.



Classes40, 43.

ING132I thread_number CANCELLED DUETO STOP OF TABLESPACEdbname.tsname (subsystem).

ExplanationThe tablespace indicated is being stopped and allthreads are canceled.

The variable thread_number shows the number andtype of threads canceled.The variable dbname.tsname identifies thetablespace.The variable subsystem identifies the DB2subsystem.

System actionThe indicated threads are canceled.



Classes40, 43.

ING133I YOUR USER ID WAS CANCELED INORDER TO ENABLE DSNTERMINATION FOR subsystem

ExplanationAll threads are being stopped by operator request. TSOusers with a DSN session are canceled in order toenforce the termination of their DSN session.

The variable subsystem identifies the name of theDB2 subsystem.



System actionThe operator session is canceled.



Classes40, 43.

ING140I ALERT 'alert' FOR 'resource' ON'system' AT timestamp

ExplanationThis message is produced by SA z/OS and sent totargets such as System Automation for IntegratedOperations Management (SA IOM), Netcool®/OMNIbus, or the Tivoli Enterprise Console (TEC) forevent notification.

The variable alert shows the alert identifier thatwas specified when INGALERT was invoked, or thedefault that was used.The variable resource shows the resource namethat was specified when INGALERT was invoked, orthe default that was used.The variable system shows the system name thatINGALERT was invoked on.The variable timestamp shows the time when theevent was originally produced. It is in the formathh:mm:ss mm/dd/yyyy.

System actionThe event is passed to the intended event notificationtarget.



ClassesNone.

ING141I SENDING OF ALERT 'alertid' FOR'resource' WAS SUCCESSFUL

ExplanationAn event was successfully sent to targets such asSystem Automation for Integrated OperationsManagement (SA IOM), Netcool/OMNIbus, or the TivoliEnterprise Console (TEC) for event notification. In thecase of SA IOM, it has acknowledged receipt of thealert.

The variable alertid shows the alert identifier thatwas specified when INGALERT was invoked or thedefault that was used.The variable resource shows the resource namethat was specified when INGALERT was invoked orthe default that was used.

System actionThe event was successfully sent to the intended eventnotification targets



ClassesNone.

ING142I SENDING OF ALERT 'alertid' FOR'resource' IGNORED

ExplanationAn event was not sent to targets such as SystemAutomation for Integrated Operations Management(SA IOM), Netcool/OMNIbus, or the Tivoli EnterpriseConsole (TEC) for event notification because theconfiguration does not allow this. Events are ignored inthe following cases:

1. Event notification is not enabled on this agent forany of the intended event notification targets.

2. The Inform List of the resource does not containthe intended event notification target.

3. Code match checking with the message IDINGALERT of the subject resource returned eitherno data or the value IGNORE.




System actionThe event was not sent to the intended eventnotification targets.


System programmer responseIf the event should not be ignored, determine thecause of the problem by using the INGCNTL commandto check the alert mode on this agent and checking theInform List and the code definitions for the subjectresource in the automation policy.

ClassesNone.

ING143I SENDING OF ALERT 'alertid' FOR'resource' FAILED

ExplanationAn event was not sent to targets such as SystemAutomation for Integrated Operations Management(SA IOM), Netcool/OMNIbus, or the Tivoli EnterpriseConsole (TEC) for event notification because of anerror. The error is detected by the command slave.Messages that are generated by the slave (or slaves)are appended to the above message text.


System actionThe event was not sent to the intended eventnotification targets.


System programmer responseCheck the additional message lines and determine thecause of the problem.

ClassesNone.

ING144I CDEMATCH FOR entry type WITHCODES (code1,code2,code3)RETURNED INVALID VALUE: value

ExplanationDuring code match checking a matching codedefinition was found. However, the value returned bythe matching code definition is invalid.

The variable entry shows the entry name of thedefinition in the MESSAGES/USER DATA policy itemof the automation policy where the matching codedefinitions were searched for.The variable type shows the message ID of thedefinition in the MESSAGES/USER DATA policy itemof the automation policy where the matching codedefinitions were searched for.The variables code1, code2, and code3 show thevalues that were used to search for a matchingcode definition in the MESSAGES/USER DATA policyitem of the specified entry and type.The variable value shows the value that is returnedfrom the matching code definition.

System actionFurther processing depends on the context. Processingusually stops.

Operator responseCheck for more information.

System programmer responseCheck the configuration and correct the problem.

ClassesNone.

ING145I type INFORMATION ISINCOMPLETE

ExplanationAn event is to be sent however the information aboutthe event notification target is incomplete.

• The variable type shows the event notification targetthat could not be notified. It is one of the following:IOM

System Automation for Integrated OperationsManagement (SA IOM) could not be reached. Theinformation specified with the ALERTHOSTparameter of the INGCNTL command isincomplete.



EIFAn EIF event could not be generated. The EASPPI receiver name to be specified with theEIFPPI parameter of the INGCNTL command ismissing.

TTTA trouble ticket could not be generated becausethe address data for the TDI server or the dataset characteristics for the trouble ticket detaildata are missing or incomplete. This data shouldbe specified with the TTTHOST and TTTDATAparameters of the INGCNTL command.

USRA user event could not be generated. The nameof the automation procedure that is used tohandle user events is missing. The procedurename should be specified with the USRHANDLERparameter of the INGCNTL command.

System actionThe event is not sent to the indicated event notificationtarget. The request is rerouted to the next availableagent in the sysplex (if any).



ClassesNone.

ING146I ALERTING IS DISABLED

ExplanationAn alert is to be sent to targets such as SystemAutomation for Integrated Operations Management(SA IOM), Netcool/OMNIbus, or the Tivoli EnterpriseConsole (TEC) for event notification. However eventnotification is not enabled on this agent for anysupported event notification target.

System actionThe event is not sent to the indicated event notificationtarget.

Operator responseTurn on event notification for the intended target withthe INGCNTL command if desired.


ClassesNone.

ING147I ALERTING IS NOT SUPPORTEDFOR RESOURCE TYPE 'type'

ExplanationAn event is to be sent to an event notification targetsuch as IOM, EIF, TTT or USR. However, the resourcetype specified is not supported for event notification.

The variable type shows the type of the resourcethat was specified, which is not valid for eventnotification.

System actionThe event is not sent to the intended event notificationtarget.

Operator responseCorrect the problem and reissue the command.


ClassesNone.

ING148I function : request REQUEST TIMEDOUT

ExplanationA request timed out.

The variable function shows the name of thefunction that detected the time out.The variable request shows the request that timedout.

System actionNone.

Operator responseCheck other messages for more information.




ClassesNone.

ING149I LIST CONTROL SETTINGS

ExplanationThis message provides header information for theINGCNTL LIST command.




ClassesNone.

ING150I timestamp : object severityjobname DATA= data

ExplanationING150I represents an event that was injected intothe system by an external or internal monitor. TypicallyINGMON is called from the NetView automation tableas an action for this event. INGMON will find thecorresponding monitor resources and triggerautomation there if applicable.

The variable timestamp is the time that the eventwas originally produced or when the message wascreated. It is in the format hh:mm:ss mm/dd/yyyy.The variable object specifies the monitored objectthat this event is related to.The variable severity specifies the severity of thestatus of the monitored object that led to thisevent.The variable jobname specifies the job name thatthe monitored object is related to or 'N/A' if there isnone.The variable data can be any data the monitorprovides that might be useful for automation orrecovery actions.




ClassesNone.

ING151I ATTACH OF name SUCCESSFUL

ExplanationThe ATTACH of a virtual operator station task (VOST)was successful.

The variable name specifies the attach name of theVOST. Note that this name is the content ofTGLOBAL SUBSJOB, that is, the job name of theVOST management APL.




ClassesNone.

ING152I ATTACH OF name FAILED WITHRC=rc

ExplanationThe ATTACH of a virtual operator station task (VOST)failed with a return code greater than 0.

The variable name specifies the attach name of theVOST. Note that this name is the content ofTGLOBAL SUBSJOB, that is, the job name of theVOST management APL.The variable rc shows the return code given by theATTACH command.



System actionThe VOST is not started.


System programmer responseReview the netlog for additional messages issued bythe ATTACH command and correct the problem.

ClassesNone.

ING153I command OF name SUCCESSFUL

ExplanationThe stopping of a virtual operator station task (VOST)was initiated successfully. Note that the VOST may stillbe active for a certain time after this message isissued.

The variable command shows the command usedto stop the VOST.The variable name specifies the attach name of theVOST. Note that this name is the content ofTGLOBAL SUBSJOB, that is, the job name of theVOST management APL.




ClassesNone.

ING154I command OF name FAILED WITHRC=rc

ExplanationThe stopping of a virtual operator station task (VOST)failed with a return code greater than 0.

The variable command shows the command usedto stop the VOST.

The variable name specifies the attach name of theVOST. Note that this name is the content ofTGLOBAL SUBSJOB, that is, the job name of theVOST management APL.The variable rc shows the return code given by thecommand.

System actionThe VOST is not stopped.


System programmer responseReview the netlog for additional messages issued bythe specified command and correct the problem.

ClassesNone.

ING155I ENVIRONMENT CHECK FAILEDFOR command. REASON=rs

ExplanationA command was issued in an unsupportedenvironment.

• The variable command shows the command thatwas executed.

• The variable rs shows the reason code that can havethe following values:1

Required task globals not set2

Running on an unsupported task3

Configuration not fully loaded4

Main include member could not be read5

ACFLEVEL could not be determined6

ACFLEVEL mismatch

System actionThe command stops processing.




System programmer responseSee the documentation of the command that issuedthe message and correct the problem.

ClassesNone.

ING156I name ENDED WITH RC=rc

ExplanationThe command executed in a virtual operator stationtask (VOST) ended.

The variable name specifies the attach name of theVOST.The variable rc shows the return code of thecommand that ran in the VOST.

System actionThe VOST is stopped.



ClassesNone.

ING157I INVALID VALUE FOR name: value

ExplanationData was found that is not valid.

The variable name specifies the context.The variable value shows the invalid data.



System programmer responseSee the documentation of the command that issuedthe message and correct the problem.

ClassesNone.

ING158I SENDING OF ALERT alertid FORresource PARTIALLY FAILED

ExplanationAn event was only partially sent to the designatedtargets.

Variable alertid identifies the alert identifier thatwas specified when INGALERT was invoked or thedefault was used.Variable resource identifies the resource.



ING159I EXIT exitname RETURNEDUNEXPECTED RESULTS. REASONreason

ExplanationAn exit was called but returned either an invalid returncode or invalid data.

• The variable exitname shows the name of the exitthat was called.

• The variable reason shows why the exit is consideredto be in error:01

Unexpected return code02

Invalid number of data lines returned03

Invalid data found in the returned lines

System actionFurther processing depends on the context. Processingusually stops.

Operator responseCheck for more information.




ClassesNone.

ING160I RESPONSE FROM SOAP SERVER:server_nameattribute_name_1 sepattribute_name_2 sep ...attribute_name_nsepattribute_value_1 sepattribute_value_2 sep ...attribute_value_n sep

ExplanationThis message displays the names and values of theattributes that have been requested by an ITM SOAPrequest. The attribute names and values are separatedby the separator character, sep, of value X'FF'.

The first line of this multiline message denotes theSOAP server, server_name, that provided thisresponse.

The second line contains the attribute namesseparated by the separator character. All the followinglines contain the attribute values separated by theseparator character.

This message is written to the console only.

System actionNone.



ING161I SENDING SOAP REQUEST TOSERVER: server_name

ExplanationA SOAP request is being sent to the SOAP serverdenoted by server_name. This message is written tothe netlog only.

System actionNone.



ING162I SOAP FAULT CODE code. REASON:reason

ExplanationThe SOAP request failed with a fault code of code.Possible codes are Client, VersionMismatch,MustUnderstand, and Server. The Client fault codeindicates that the SOAP message was incorrectlyformed.

The reason text indicates the particular fault.


System actionNone.


System programmer responseFor a Client fault code, correct the SOAP message andtry again. For any other fault code, contact your IBMsupport representative.

ING163I FAULT DETAIL: text

ExplanationThis message provides further detail in variable textabout the fault reported in the preceding ING162Imessage. This message spans multiple lines if furtherfault details are reported in the SOAP response.


System actionNone.


System programmer responseFor a Client fault code (see ING162I), correct theSOAP message and try again. For any other fault code,contact your IBM support representative.

ING164I SOAP REQUEST FAILED, REASON:reason SERVER: server_name



ExplanationAn error occurred while attempting to process a SOAPrequest on the SOAP server denoted by server_name.The actual error reason is encoded in the separatereason variable.


The following reasons are defined:00000004

A timeout occurred and the connection wasterminated.

0001nnnnINGOMX failed to connect to, send to, or receivefrom a socket created to communicate with theSOAP server denoted by server_name. The socketerror is encoded in bytes 2 and 3 represented byvariable nnnn.

0002nnnnThe output returned from the IBM Tivoli®Monitoring SOAP server could not be handled bythe XML parser. The XML parser reason code isencoded in bytes 2 and 3 represented by variablennnn.

0003nnnnAn internal error occurred. The variable nnnnrepresents the internal error code.

0004xyyyAn HTTP error occurred while processing therequest. If x=0, yyy denotes the 3-digit HTTPresponse code, for example, 404. If x=1 and y=008check userID and password otherwise the variableyyy represents the internal error code.

0005nnnnAn error occurred while allocating or reading theSOAP request data set. The pipe QSAM return codeis encoded in bytes 2 and 3 represented byvariable nnnn.

0006nnnnAn error occurred while processing a CORRCMDpipe stage. The return code is encoded in bytes 2and 3 represented by variable nnnn.

System actionNone.


System programmer responseFor reason code 00000004, increase the timeoutvalue. The parameter default variable INGOMX_WAITcan be set to increase the timeout.

For reason codes 0001nnnn and 0004xyyy, ensure youhave connectivity to the SOAP server and verify theport and path of the SOAP service.

For reason code 0005nnnn, specify the correct dataset name or fix the I/O error.

In any other case, contact your IBM supportrepresentative.

ING165I protocol status-code reason-phrase

ExplanationThis message reflects the status line of a precedingHTTP request in case of a non-zero status code.

The variable protocol reports the HTTP protocolused by the server.The variable status-code reports the status of therequest.The variable reason-phrase contains humanreadable information explaining the status-code.

This message is written to the netlog only.

System actionNone.


System programmer responseFor status codes 1xx and 2xx, no action is required.

For status codes 3xx, check out message ING167I forthe new location and try again.

For status codes 4xx, check out the details reported bymessage ING166I and fix the problem.

For status codes 5xx, collect the details reported bymessage ING166I and contact your IBM supportrepresentative.

ING166I HTTP-RESPONSE INFORMATION:text

ExplanationThis message reports additional information about theHTTP response, where the variable text containsgeneral header fields, response header fields, andentity header fields.

This message is written to the netlog only.



System actionNone.


System programmer responseSee message ING165I about how to use thisinformation depending on the status code returned bythe server.

ING167I NEW LOCATION: location

ExplanationThis message is issued as the result of a 3xx statuscode received as the response of the HTTP SOAPrequest. The request URI was either temporarily orpermanently moved to a new location or is onlyaccessible through the proxy server at the reportedlocation. The request must be redirected to the newlocation reported by the variable location.


System actionNone.


System programmer responseCorrect the server information in the customizationdialog to use the reported location and then try therequest again.

ING170I THE FOLLOWING ENTRY-TYPESHAVE BEEN DELETED: entry-type

ExplanationThis message is issued by the INGCLEAN utility whenentry-types have been deleted. The deleted entry-types are appended to the above message text. Notethat the entry-types for which a default has beenrestored are not included in this list.

The variable entry-type displays any entry-typesthat have been deleted.

System actionProcessing was successful.



ClassesNone.

ING172I Resource resource_name has beenreleased.

ExplanationThe named resource has been released from waiting infront of a pacing gate. It immediately starts or stopsdepending on the pacing gate type.

The resource_name variable shows the resource inautomation manager notation that has beenreleased.

System action:None.



ING177I command_name command isignored because resource_nameresource is suspended.

ExplanationThe command_name command has detected thatresource_name resource is suspended and thereforedid not perform its action.

The command_name variable shows the commandthat issues this message.The resource_name variable shows the resource inautomation manager notation that is suspended.

System action:None.


System programmer response:None. If the invocation of the command_namecommand was triggered by an installation-writtenscript, consider avoiding the invocation for asuspended resource.

ING178I No valid resource was found forcommand command.



ExplanationNone of the resources that are defined in the sysplexmatches the specified name pattern or their types arenot supported by the named command.

The command variable shows the command forwhich a resource cannot be found.

System action:None.

Operator response:Refer to the description of the command in Operator'sGuide or Programmer's Reference for further details.


ING179I The service xxx failed withRC=retcode REASON=reason_text

ExplanationThe SA z/OS function XVP (XCF variable pool) tried toexecute a service that failed. XVP manages sharedvariables within different SAplexes in the samephysical sysplex. The XVP function is internally usedby SA z/OS. There is no direct external interface.

The xxx variable indicates the service that failed.The retcode variable indicates the return code ofthe service that failed.The reason_text variable provides extra errordescription.

The possible return codes are as follows.

8 A timeout occurred.

1nn Failed to check the input data.

104 aof_xvpin.0 is not numeric.112 The variable name is notalphanumeric plus @$#_.

2nn Failed to send a command to theautomation manager (see nn for rc fromINGPXRPC)

3nn Failed to receive response from theautomation manager (see nn for rc fromINGPXRPC). For example, 316 occursbecause the automation manager is nolonger running.

4nn The XVP service failed.

404 The pool does not exist.408 The variable does not exist.412 The update is still in progress.

416 The initialization is not yetcompleted.424 The variable is read only.428 A replication error occurred.432 The command is invalid.436 The minor ENQ name is longer than255 bytes.440 ENQ lock is already obtained.444 ENQ failed.445 DEQ failed.499 Failed to get MASTER lock.

5nn Failed to check the input arguments of thecommand.

508 The service is invalid.512 An argument is not alphanumericplus @$#_.516 The 1st char in option is invalid.517 The 2nd char in option is invalid.518 The 3rd char in option is invalid.520 The timeout format is invalid.

System actionThe processing of the XVP command terminates.


System programmer responseDetermine why the service failed and correct theproblem. Examine the netlog for extra information.

ING200W SA event with NoStatusChangereason in domain domain

ExplanationThis message is created by the SA z/OS internalnotification function to send current status informationto the end-to-end automation adapter.

System actionNone.





ING201W SA detected a status change ofresource resource in domaindomain. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the status of a resourcechanges. It shows the resource’s new status in theend-to-end automation resource data model.

The variable resource shows the name of theresource.The variable domain shows the name of the end-to-end automation domain.The variable observed shows the observed state ofthe resource.The variable desired shows the desired state of theresource.The variable operational shows the operationalstate of the resource.The variable compound shows the compound stateof the resource.

System actionNone.



ING202I SA turned the resource resourcerequest as requested in domaindomain. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when a request has been issuedto start or stop a resource. It shows the resource’scurrent status in the end-to-end automation resourcedata model.


The variable request indicates if an Online or Offlinerequest has been issued.The variable domain shows the name of the end-to-end automation domain.The variable observed shows the observed state ofthe resource.The variable desired shows the desired state of theresource.The variable operational shows the operationalstate of the resource.The variable compound shows the compound stateof the resource.

System actionNone.



ING203I SA detected that the systemsystem joined the domain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the observed status of a system resourcehas 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 actionNone.



ING204W SA detected that the systemsystem left the domain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation manager



reports that the observed status of a system resourcehas become Sysgone.


System actionNone.



ING205I SA turned off the automation forresource resource in domaindomain. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when a request has been issuedto switch on or off the automation flag of a resource. Itshows the resource’s current status in the end-to-endautomation resource data model.


System actionNone.



ING206W SA detected a warning in domaindomain. The resource resource hasbeen degraded. Common observedstate: observed, Common desiredstate: desired, Commonoperational state: operational,Common compound state:compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the observed status of the resource hasbecome degraded. It shows the resource’s currentstatus in the end-to-end automation resource datamodel.


System actionNone.



ING207W SA detected a warning in domaindomain. The resource resource hasa performance problem. Commonobserved state: observed,Common desired state: desired,Common operational state:operational, Common compoundstate: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the health status of the resource hasbecome degraded. It shows the resource’s current



status in the end-to-end automation resource datamodel.


System actionNone.



ING208W SA detected a warning in domaindomain. The resource resource hasproblems caused by a dependencyto another resource. Commonobserved state: observed,Common desired state: desired,Common operational state:operational, Common compoundstate: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the startable status of the resource hasbecome inhibited. It shows the resource’s currentstatus in the end-to-end automation resource datamodel.

The variable resource shows the name of theresource.The variable domain shows the name of the end-to-end automation domain.The variable observed shows the observed state ofthe resource.The variable desired shows the desired state of theresource.The variable operational shows the operationalstate of the resource.

The variable compound shows the compound stateof the resource.

System actionNone.



ING209W SA detected a problem in domaindomain. The resource resourcecan't be turned into the requestedstate. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports a problem in the automation state or theobserved state. It shows the resource’s current statusin the end-to-end automation resource data model.


System actionNone.



ING210W SA detected a problem in domaindomain. The resource resource



needs a manual reset by theoperator. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the observed status of the resource haschanged to harddown. It shows the resource’s currentstatus in the end-to-end automation resource datamodel.


System actionNone.



ING211W SA detected a problem in domaindomain. The resource resource hasproblems caused by an offlinesystem. Common observed state:observed, Common desired state:desired, Common operationalstate: operational, Commoncompound state: compound

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the observed status of the resource haschanged to sysgone. It shows the resource’s currentstatus in the end-to-end automation resource datamodel.


System actionNone.



ING212W SA event with unknown reason indomain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managersends an event with an unknown reason.

The variable domain shows the name of the end-to-end automation domain.

System actionNone.



ING213I SA detected that systemautomation is ready in domaindomain

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that the status of the automationdomain is Online.




System actionNone.



ING214W SA detected that systemautomation is broken in domaindomain

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that the status of the automationdomain is Offline.


System actionNone.



ING215I SA detected a configuration policyrefresh in domain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that the automation policy hasbeen refreshed in the automation domain.


System actionNone.



ING216I SA detected a new configuration indomain domain. New resourceresource created.

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a new resource has beencreated in the automation domain.

The variable resource shows the name of theresource.The variable domain shows the name of the end-to-end automation domain.

System actionNone.



ING217I SA detected a deletedconfiguration in domain domain.Resource resource deleted.

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a resource has been deletedin the automation domain.


System actionNone.





ING218I SA detected a new configuration indomain domain. Request actionrequest issued for resourceresource

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a new request has beenissued 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 theresource.

System actionNone.



ING219I SA detected a deletedconfiguration in domain domain.Request action request deleted forresource resource

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a request for the resource inthe 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 theresource.

System actionNone.



ING220I SA detected a new configuration indomain domain. New relationshiprelationship with source resourcesource and target resource targetcreated.

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a new relationship has beencreated between the source resource and the targetresource in the automation domain.

The variable domain shows the name of the end-to-end automation domain.The variable relationship shows the name of therelationship.The variable source shows the name of thedependent resource.The variable target shows the name of thesupporting resource.

System actionNone.



ING221I SA detected a deletedconfiguration in domain domain.Relationship relationship withsource resource source and targetresource target deleted.

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that a relationship between thesource resource and the target resource in theautomation domain has been deleted.

The variable domain shows the name of the end-to-end automation domain.The variable relationship shows the name of therelationship.The variable source shows the name of thedependent resource.



The variable target shows the name of thesupporting resource.

System actionNone.



ING222I SA detected an automation statuschange in domain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function to inform the end-to-endautomation adapter that properties have beenchanged in the automation domain.


System actionNone.



ING223W SA detected that the systemsystem switched into maintenancemode by operator command indomain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the desired status of a system resourcehas changed to Available.


System actionNone.



ING224I SA detected that the systemsystem switched back toautomation mode by an operatorcommand in domain domain

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the desired status of a system resourcehas changed to Unavailable.


System actionNone.



ING225W SA suspended automation forresource resource in domaindomain as requested.

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the automation flag of the resource hasbeen switched off.


System actionNone.





ING226I SA resumed automation forresource resource in domaindomain as requested.

ExplanationThis message is created by the SA z/OS internal eventnotification function when the automation managerreports that the automation flag of the resource hasbeen switched on.


System actionNone.



ING230E Addressed consumer consumer notregistered. Event not forwarded.

ExplanationAn event was received with a consumer that was notregistered as the target address. The event thereforecannot be forwarded to the addressed consumer.

The variable consumer shows the name of theevent consumer that was specified as the targetaddress of the event, and that the event shouldhave been forwarded to.

System actionProcessing of the event is terminated.


System programmer responseCheck whether event notification has been correctlyinitialized and end-to-end automation has beenregistered as an event consumer.

ING231E Event notification service returnsrc. Event not forwarded toreceiver_id.

ExplanationThe event could not be forwarded to the addressedconsumer.

The variable rc shows the return code.The variable receiver_id shows the name of the PPIreceiver ID.

If the NetView EA/S is used for event forwarding, thenrc is the return code from PIPE stage TECROUTE.

If the NetView EA/S is not used for event forwarding,then rc is the return code from the System Automationinternal event forwarding mechanismAOF_PPI_CALLJAVA. Check if the E2E adapter isalready running since the event is sent directly to theE2E adapter without using EA/S.

System actionProcessing of the event is stopped.


System programmer responseCheck whether the status of the PPI receiver ID isactive. The status of PPI receivers can be listed withthe command DISPPI.

ING232I PPI receiver ID for E2E adapter isset to receiver_id.

ExplanationThe PPI receiver ID for the message adapter of theevent/automation service, which is used to forwardevents to the automation adapter, has been set to thespecified receiver ID.

System actionNone.





ING233E Event forwarding task EVTOPERfor E2E not defined.

ExplanationThe primary agent cannot be started because theautomated function EVTOPER, which is used toforward the events to the automation adapter, has notbeen defined in the automation policy.



System programmer responseDefine the automated function EVTOPER.

ING234E Request 'request' failed: RC=rccommand='command'reason='reason'

ExplanationThe specified command abended.

The variable request shows the request that wasreceived from the automation adapter forexecution.The variable rc shows the return code of thecommand.The variable command shows the command thatimplements the request.The variable reason shows text that describes theerror.

System actionExecution of the request stops.


System programmer responseAnalyze the return code and reason code for theabending command.

ING235W No information from automationmanager.event event not createdfor consumer.

ExplanationAn error occurred when requesting information fromthe automation manager that needed to be included ina domain event. The event has not been created.

• The variable event specifies the event to be created.Possible values are: READY, REFRESH, CHANGE.

A READY event is created at initialization time of theautomation domain and after having recovered frommiscellaneous error situations.

A REFRESH event is created after having refreshedthe configuration policy.

A CHANGE event is created after a takeover of theautomation manager if the outage has not exceededa given time interval.

• The variable consumer shows the name of the eventconsumer that the event should have beenforwarded to.

System actionProcessing of the event is stopped.


System programmer responseAnalyze the NetView log for further SA z/OS messagesconcerning the communication between the primaryagent and the automation manager.

ING236W Task execution request requestprocessed with warnings:COMMAND='command'REASON='reason'

ExplanationA warning was issued when executing a task executionrequest. The message variables are:request

The name of the task execution requestcommand

The command that failed.reason

Text that describes the error.

System actionThe request is executed with warnings.




System programmer responseAnalyze the reason code of the warning message.

ING237W Request 'request' processed withwarnings: COMMAND='command'REASON='reason'

ExplanationA warning was issued when executing an end-to-endrequest.

The variable request shows the name of the end-to-end request.The variable command shows the issued commandthat implements the request.The variable reason specifies the warning message.

System actionThe end-to-end request executes.

Operator responseAnalyze the reason code of the warning message.


ING238E Task execution requesttex_request failed:ERROR=error_codeSERVICE='service' RC=return_codeREASON='reason'

ExplanationThe REXX function INGRXTX0 and common REXXmacros issue this message if there is an error. Themessage variables are:tex_request

The name of the task execution requesterror_code

The REXX function INGRXTX0 and the commonREXX macros issue the following error codes:1

RPC service failed: either INGPXSND,INGPXRCV or INGPXDEL.

2Read from or write to the task execution datastream failed.

3Unknown task execution operation name.

4Execution of a task execution request startedbut failed. The REXX macro that implementedthe execution of the request did not issue anerror message. This is the default return codeand the standard ING238E message is writtenwith SERVICE=OperationName andRC=OperationReturnCode.

5Authorization error: the user that made therequest is not authorized to make it.

6At least one request in the list of requestsfailed.

7The execution of a task execution requestfailed for any other reason.

8The execution of a task execution requestfailed because service INGPYAMC failed.

9Execution of a task execution request wasrejected because of expired expiration time.

10User command executed but failed becausereturn code is greater than zero.

11Cannot start the user command because usercommand not found on target system.

12Cannot start the user command becausecommand user ID not defined on targetsystem.

13Cannot start the user command.

24Task execution request contains no meta data.

28The task execution command handler abortsbecause there is not enough time to send backthe response data. No response is returned.

32The task execution command handler abortsbecause of a REXX signaling error.

36The automation adapter is not supported bythis product.

serviceThe service that failed.



return_codeThe return code of the service that failed.

reasonText that describes the error.

The service, return_code, or reason variables may nothave a value.

System actionExecution of the request failed for the reason given inthe message.


System programmer responseCheck the netlog and correct the error. If ERROR=28,increase the timeout value in seconds. For details, seeEnd-to-End Automation ->Chapter ProblemDetermination of the End-to-End Adapter ->TimeoutProblems.

ING239W Value in advanced automationoption name not valid. Defaultvalue used.

ExplanationThe value provided in the advanced automation optionis not accepted as a valid value.

The variable name shows the name of the advancedautomation option.The variable value shows the value of the advancedautomation option.

System actionProcessing continues with the default value for thespecified advanced automation option.


System programmer responseCorrect the value provided in the advanced automationoption.

ING240E Unexpected task executionrequest name tex_request.

ExplanationThe REXX macro implemented to execute the taskexecution request was called with an unexpected taskexecution request name.

The variable tex_request shows the name of thetask execution request.

System actionProcessing of the task execution request fails.



ING241E Unexpected task executionelement type type.

ExplanationThe REXX macro implemented to execute the taskexecution request was called with an unexpected taskexecution request type.

The variable type shows the type of task executionelement.




ING242E Cannot read task executionelement from data stream.

ExplanationThe REXX macro implemented to execute the taskexecution request cannot read the task executionelement from the data stream.






ING243E Cannot write task executionelement to data stream.

ExplanationThe REXX macro implemented to execute the taskexecution request cannot write to the data stream toreturn data to the calling routine.




ING244E Invalid filter element name filter.

ExplanationThe REXX macro implemented to execute the taskexecution request was passed an invalid filter elementname.

The variable filter shows the name of the filterelement.




ING245E Duplicate filter element namefilter.

ExplanationThe REXX macro implemented to execute the taskexecution request was passed duplicate filter elementnames.

The variable filter shows the name of the filterelement.




ING246E Invalid combination of filterelement names filter1 and filter2.

ExplanationThe REXX macro implemented to execute the taskexecution request was passed an invalid combinationof filter element names.

The variables filter1 and filter2 show the names ofthe two filter elements.




ING247E Invalid filter element filter. Filtervalue unknown: value

ExplanationThe REXX macro implemented to execute the taskexecution 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.






ING248E Invalid filter element filter. Filteroperator unknown: operator

ExplanationThe REXX macro implemented to execute the taskexecution request was passed a filter element with anunknown operator comparing the filter name and filtervalue.

The variable filter shows the name of the filter.The variable operator shows the filter operator.




ING249E Execution of a task executionrequest timed out. The expirationtime time was too short –missing_time.

ExplanationThe expiration time that was provided for the taskexecution request was too short.

The variable time shows the expiration time thatwas provided for the task execution request.The variable missing_time specifies the missingtime interval.



System programmer responseCheck the defined timeout interval for the end-to-endautomation request. The expiration time of an end-to-end automation request is determined by where it isissued, as follows:

Request issuedfrom: Expiration time determined by:

The SMU WebUIor SystemAutomationApplicationManager

The timeout interval that is definedin the WebSphere® Admin Consolefor the environment variablecom.ibm.eez.aab.invocation-timeout-seconds

The automationadapter (such asINIT_DOMAIN)

The timeout interval that is definedin the automation adaptering.adapter.plugin.propertiesconfiguration file

E2E agent The timeout intervalINGAGT_CON_TIMEOUT that isdefined in the automation agentinge2eagt.properties configurationfile

It is possible that an end-to-end automation requestthat has been issued might be queued in theautomation adapter or the NetView operator task for acertain period of time. You can therefore increase thetimeout interval to take this delay into account.

If the timeout occurs during INIT_DOMAIN, you canalso increase the TIMEOUT parameter ining.adapter.plugin.properties.

ING250E Execution of a service timed out.The expiration time time wasreduced to number seconds.

ExplanationA service routine timed out without exploiting theexpiration time that was provided for the execution ofthe task execution request. The execution time wasreduced to the maximum value for the WAITparameter of the executed service.

The variable time shows the expiration time thatwas provided for the task execution request.The variable number shows the value for the WAITparameter of the executed service.






ING251E Invalid combination of filterelements filter1 and filter2. Valuesvalue1 and value2 are mutuallyexclusive.

ExplanationThe REXX macro implemented to execute the taskexecution request was passed an invalid combinationof values for the filter elements.

The variables filter1 and filter2 show the names ofthe two filter elements.The variables value1 and value2 show the values ofthe two filter elements.




ING252E Domain initialization failed.Automation environment notinitialized.

ExplanationInitialization of the automation domain failed becauseinitialization of the system automation environment ofthe primary agent has not yet been completed.

System actionThe start of the automation adapter fails.

Operator responseRestart the automation adapter after the initializationof the automation environment of the primary agenthas completed.


ING253E Domain initialization failed.Primary agent already started onsystem system.

ExplanationInitialization of the automation domain failed becausethe primary agent is already running on anothersystem within the subplex.

The variable system shows the system name.


Operator responseCheck whether the automation adapter should bestopped on the other system.


ING254E Domain initialization failed. PPIreceiver receiver of EAS notACTIVE.

ExplanationInitialization of the automation domain failed becausethe PPI receiver ID of the NetView event/automationservice is not active.

The variable receiver shows the name of the PPIreceiver.


Operator responseAnalyze the status of the PPI receivers by usingcommand DISPPI. Check whether the event/automation service has been started and hassuccessfully initialized its receiver ID at the PPI.


ING255E Requesting information fromAutomation Manager of domaindomain failed.

ExplanationRequesting information from automation manager ofan automation domain failed. Requesting informationfrom automation is necessary during the initializationof the automation domain or when requestinginformation about the automation domain.



The variable domain shows the name of theautomation domain.

System actionThe task execution request fails.


System programmer responseAnalyze the problem. Examine the NetView log forfurther information. If the problem persists contactyour IBM Support Center.

ING256E Health check failed. Eventforwarding switched off.

ExplanationEvents were lost when trying to forward them from theprimary agent to the automation adapter. Eventforwarding has therefore been switched off, whichresults in failing the health check of the automationdomain.

System actionThe automation adapter will stop. A subsequentrestart enforces the re-initialization of the automationadapter and a refresh of the status information aboutfirst-level automation resources on the end-to-endserver.

Operator responseCheck the communication path from the primaryautomation agent to the NetView event/automationservice. As soon as the communication path isavailable again, the automation adapter can berestarted.


ING257E Health check failed. PPI receiverreceiver of EAS not ACTIVE.

ExplanationThe PPI receiver identifier of the event/automationservice is not in the status ACTIVE. This results infailing the health check of the automation domain.

The variable receiver shows the PPI receiver ID ofthe NetView event/automation service.

System actionThe automation adapter does not send a heartbeatevent. Thus the communication status of the domainon the end-to-end management server changes.

Operator responseAnalyze the status of the PPI receivers by usingcommand DISPPI. Check whether the event/automation service has been started and hassuccessfully initialized its receiver ID at the PPI.


ING258E Execution of service service failed.Unexpected data received.

ExplanationThe requested service did not return the expecteddata.

The variable service shows the name of therequested service.



System programmer responseDetermine why the service routine fails. Examine theNetView log for additional information.

ING259E Invalid request element. Requestname unknown: name

ExplanationAn end-to-end request with an unknown name wasreceived.

The variable name shows the request name.






ING260E Invalid request element. Requesttype unknown: type

ExplanationAn end-to-end request with an unknown type wasreceived.

The variable type shows the request type.




ING261E Invalid request element. Multiplesolicited requests are notsupported.

ExplanationMultiple solicited end-to-end requests were receivedto be executed by the primary agent. Only onesolicited end-to-end request can be accepted.




ING262W An attempt was made to overwriteat least one restricted parameter.Input parameters have beenignored: parameters

ExplanationAn end-to-end request was received with parametersthat attempted to overwrite restricted parameters. Theparameters are ignored.

The variable parameters shows a list of the ignoredparameters.




ING263E Request rejected becausemandatory parameter SOURCE ismissing.

ExplanationAn end-to-end request was received without thespecified originator of the request via parameterSOURCE.




ING264E Reset_from_NRE rejected becauseagent status of resource resourceis CTLDOWN.

ExplanationA reset-from-non-recoverable-error request wasreceived for a resource that is in agent statusCTLDOWN. Such a request is not supported forresources in agent status CTLDOWN.

The variable resource shows the name of theresource that the request was issued for.


Operator responseCheck the agent status of the resource that therequest was issued for.




ING265E Reset_from_NRE rejected becauseobserved status of resourceresource is not HARDDOWN.

ExplanationA reset-from-non-recoverable-error request wasreceived for a resource that is not in statusHARDDOWN. Such a request is only supported forresources in status HARDDOWN.



Operator responseCheck the status of the resource.


ING266E Reset_from_NRE failed becauseno data to resource resourcereceived from AutomationManager.

ExplanationA reset-from-non-recoverable-error request wasreceived for a resource. An error occurred whenrequesting information from the automation managerabout the resource that the request was issuedagainst.



Operator responseCheck whether the resource that the request wasissued for is known to the automation manager.


ING267E Reset_from_NRE rejected becauseresource resource is not of classAPL.

ExplanationA reset-from-non-recoverable-error request wasreceived for a resource that is not of class APL. Thisrequest is only supported for resources of type APL.



Operator responseCheck the type of the resource that the request wasissued for.


ING268E request rejected because systemname is missing.

ExplanationAn end-to-end request concerning a system wasissued, but the system name was not specified.

The variable request shows the name of the end-to-end request.


Operator responseCheck that the request was issued against a resourceof class SYS.


ING269E Native command contains aninvalid value for parameter$WAIT: wait

ExplanationAn invalid value was specified as the WAIT parameterwhen issuing a native command.

The variable wait shows the value for the WAITparameter that was received.

System actionProcessing of the task execution request fails





ING270E User user is not authorized toexecute command: command

ExplanationThe execution of the specified command is rejected bythe authorization user exit AOFEXE2E.

The variable user shows the user ID that isassociated with the command.The variable command shows the rejectedcommand resulting from the related end-to-endrequest.


Operator responseContact your system programmer to obtain thenecessary authorization to execute the command.

System programmer responseIf it is appropriate, authorize the user to issue thespecified command.

ING271E Command execution failed.Waiting for asynchronous outputtimed out.

ExplanationA timeout occurred when waiting for asynchronousoutput generated by a command that was issued fromwithin a PIPE.

System actionProcessing of the task execution request fails


System programmer responseDetermine why the command does not return itsoutput within the expected time. Examine the NetViewlog for additional information.

ING272E More than one request in a listfailed.

ExplanationMore than one request in a list of requests that wereincluded in a task execution request failed.

System actionProcessing of the related requests fails.

Operator responseExamine the NetView log for additional informationabout the single requests that were processed witherrors.


ING273W More than one request in a listprocessed with warnings.

ExplanationMore than one request in a list of requests that wereincluded in a task execution request were processedwith warnings.

System actionProcessing of the task execution request continues.

Operator responseExamine the NetView log for additional informationabout the single requests that were processed withwarnings.


ING274E A query to the automationmanager failed due tounsuccessful execution of serviceINGPYAMC.



ExplanationAn error occurred when requesting information fromthe automation manager via the automation managerAPI INGPYAMC.


Operator responseCheck the communication path from the primary agentto the automation manager and examine the NetViewlog for additional information. If the problem persistscontact your IBM Support Center.


ING275E Processing failed for command:command

ExplanationA command was called that ended with a non-zeroreturn code.

The variable command shows the failed command.

System actionProcessing of the command stops.

Operator responseFor commands that are described in IBM Z SystemAutomation Operator's Commands or in IBM Z SystemAutomation Programmer's Reference, determine whythe command failed and correct the problem.


ING276E Execution of a service timed out.

ExplanationThe return code of the requested service indicates atimeout problem.

System actionThe requested service does not complete successfully.


System programmer responseDetermine why the service routine timed out. Examinethe NetView log for additional information.

ING277I Command Handler INGRXCMJFAILED: RC=nn ReasonText

ExplanationThe command handler of the Automation Agent Java™

Framework detected an error.

The variable RC is the return code from thecommand handler INGRXCMJ as described below.The variable ReasonText is the description of theerror, as described below.

Table 4. Reason Text for Return Codes

Return Code Reason Text

54 CMD_RC=cmd_rc CMD=cmdshortERRMSG=errormsg

58 PIPE ERROR PIPE_RC=pipe_rc

59 PIPE ERROR STAGE=stage RC=scrCMD=cmdshort

60 PIPE ERROR STAGE CORRWAITASYNCH TIMEOUT

nn CMD=short command that failed

Note: For rc=1..32, message AOF356 was issued(command handler failed).

Table 5. Return Codes from INGRXCMJ

Return Code Explanation

0 Success

4 Invalid RPC Type

8 REXX function failed

12 NetView pipe failed

16 buffer.0 is wrong

20 Route cmd failed

24 JVM stuff failed

28 INGPXRCV rc<>0

32 Remote_Command failed (forremote target only)



Table 5. Return Codes from INGRXCMJ (continued)

Return Code Explanation

52 Invalid data stream

54 CMD_RC=cmd_rc CMD=cmdshortERRMSG=errormsg

58 PIPE ERROR PIPE_RC=pipe_rc

59 PIPE ERROR STAGE=stage RC=srcCMD=cmdshort

60 PIPE ERROR STAGE CORRWAITASYNCH TIMEOUT

74 INGEXEC error

75 PIPE error

76 At least one command failed on theremote system

77 Target missing

Note: For return codes 74 to 77, seeAOF_JVM_Route_Command (AOFC0210).

System actionThe command has not been executed successfully.


System programmer responseAnalyze the NetView log and search for further errormessages which may provide more details about thereason of the error. If rc=54, look for the description ofthe associated command. If necessary, contact yourIBM Contact Support Center.

ING278I System Automation E2E Agentcannot find resources of type xxx.

Explanation:The E2E agent queries the automation manager forDMN and REF resources. However there are no DMN orREF resources defined in the configuration filecurrently loaded by the automation manager. Theplaceholder xxx defines the type of resource, forexample DMN or REF.

System action:E2E agent initialization continues and the status of theE2E agent application will be set to HALTED.



Check the System Automation policy for DMN and REFresources.

ING279I Resource type xxx not supported.

Explanation:The specified resource type disallowed for executionof a command or for a dialog. The placeholder xxxspecifies the unsupported resource type, for exampleDMN.

System action:None.

Operator response:Specify a resource with valid type.


ING300I Command command finishedsuccessfully

ExplanationA command has finished processing and achievedwhat it has been asked to do, for example, starting aresource.

The variable command is the command beingexecuted.

System actionNone.



ING301I Command command failed -unexpected results after waitingfor hh:mm:ss

ExplanationA command has finished processing but has notachieved what it has been asked to do. For example,when starting a resource, the resource is not in theexpected state after the allowed time period.

The variable command is the command beingexecuted.The variable hh:mm:ss is the timer period.

System actionNone.





ING302I Nothing to cancel

ExplanationNo request exists for the specified resource thatoriginated from the same source.

System actionNone.



ING304I Waiting for termination of nameaborted - reason

ExplanationZ System Automation was waiting for the terminationof the name component, but the termination commandwas aborted.

Variable name is the name of component.Variable reason explains why the terminationcommand was aborted.



System programmer responseIf the component is OMVS, consider adding commandF BPXOINIT,SHUTDOWN=FORKINIT command asSHUTINIT command for JES in the policy.

ING305I System shutdown started for name

ExplanationIndicates that the termination of the system has beenstarted. The shutdown was either requested by thelocal operator, GDPS® or the Active/Active controller.

Variable name identifies the name of the system.


System programmer responseNone required.

ING306I System shutdown nearly completefor name

ExplanationIndicates that the shutdown of the names system isnearly finished. Only NetView is still active.




ING307I System shutdown for namealready in progress

ExplanationIndicates that Z System Automation is already workingon shutting down the named system.



ING308A Waiting for termination of name

ExplanationSystem automation is in the middle of shutting downthe system and is waiting for the termination of thenamed component / address space. The terminationprocess is on halt till the named component becomesinactive.





Operator responseStop the named component / address space.


ING309I System shutdown for nameredirected due to GDPS Tower,STOPAPPL=resource

ExplanationA system shutdown was requested by means of theINGREQ ALL command. Since the system is undercontrol of GDPS, only the toplevel resource identifiedby means of the GDPS STOPAPPL parameter in theGEOPLEX OPTIONS member is terminated.

Variable name identifies the name of the system.Variable resource identifies the GDPS STOPAPPLresource.




ING310I data

ExplanationThis message is used to transport the completionblock from the system being terminated back to theActive/Active Controller.



ING311I Workload name not defined in theSA policy

ExplanationThe Active/Active controller has requested either toStart, Stop a workload or to query the status of theworkload, but the workload is not defined in the ZSystem Automation policy. Workload must be definedin the GDPS_WORKLOAD policy under the MVScomponent.

Variable name identifies the workload.


System programmer responseDefine the workload in the Z System Automationpolicy, if necessary.

ING312I action of Workload name failed.

ExplanationThe Active/Active controller has requested either toStart or Stop a workload, but this failed. See theNetView log for more details about the failure whenthe workload is managed by Z System Automation orthe system log otherwise.

Variable action identifies the action beingperformed (START or STOP).Variable name identifies the workload.



ING313I time: IPL completed withinexpected time period, elapsedtime was duration

ExplanationIPL completed within the expected time period. Thismeans all required resources have reached one of thespecified statuses. The specified statuses are shown inDISPSYS. This message will only be reported on theconsole.

Variable time shows the time when this messagewas generated.Variable duration shows the time it took all requiredresources to reach one of the specified statuses.



System actionNone.



ING314I time: IPL not completed withinlimit: limit. Failing resources:resource

ExplanationIPL did not complete within the maximum time limit.This means not all required resources have reachedone of the specified statuses. The specified statusesare shown in DISPSYS. The failing resources areappended to the above message test. This messagewill only be reported on the console.

Variable time shows the time the message wasgenerated.Variable limit shows the specified maximum timelimit within an IPL is considered to be completedsuccessfully.Variable resource displays the names of allresources which have not reached one of thespecified statuses.

System actionNone.

Operator responseCheck the failing resources and correct the problem(s)which are blocking the resources to reach one of thespecified statuses.


ING315I time: IPL completed afterexpected time period, elapsedtime was duration

ExplanationIPL completed after the expected time period. Thismeans all required resources have finally reached oneof the specified statuses but not within the expectedtime period. The specified statuses are shown inDISPSYS. This message will only be reported on theconsole.

Variable time shows the time when this messagewas generated.Variable duration shows the time it took all requiredresources to reach one of the specified statuses.

System action:None.



ING321I Unsupported function commandfound in emulator command,Caller: caller

ExplanationThe IMFEXEC command was invoked passing afunction code that is not supported by Z SystemAutomation.

Variable emulator is the name of the command, forexample IMFEXEC or OPSCMD.Variable command identifies the function that is notsupported by Z System Automation.Variable caller identifies the REXX script that calledthe IMFEXEC command.


System programmer responseModify the script invoking the IMFEXEC command.

ING322I emulator function commands areno longer allowed, Caller: caller

ExplanationThe IMFEXEC CMD command was called, but no longersupported in the NetView/Z System Automationenvironment.

Variable emulator is the name of the command, forexample IMFEXEC or OPSCMD.Variable function identifies the function.Variable caller identifies the REXX script that calledthe IMFEXEC command.





ING323I emulator function does not supportparameter parameter, Caller: caller

ExplanationThe IMFEXEC command was called for a supportedfunction, but the specified parameter is not supportedby the Z System Automation emulator.

Variable emulator is the name of the command, forexample IMFEXEC or OPSCMD.Variable function identifies the function.Variable parameter identifies the parameter that isnot supported.Variable caller identifies the REXX script that calledthe IMFEXEC command.



ING325I alert-message

ExplanationThis message is used to carry the alert text from anIMFEXEC ALERT function call



ING326I No command specified

ExplanationThe OPSCMD command was invoked but no commandwas specified.


System programmer responseModify the script invoking the OPSCMD command.

ING327I parameter parameter value is notallowed

ExplanationThe OPSCMD command was invoked specifying a valuefor a parameter that is not supported by the Z SystemAutomation provided emulator.

Variable parameter names the parameter.Variable value is the value.



ING328I parameter parameter value isunknown

ExplanationThe OPSCMD was invoked specifying a system that isnot known in Z System Automation.

Variable parameter is SYSID/SYSTEM.Variable value is the name of the system that isunknown.



ING329I Job=jobname User=userid issued:command

ExplanationThe OPSCMD was invoked to execute the specifiedcommand.

Variable jobname is the name of the job whooriginated the OPSCMD call.Variable userid is the user id associated with thejob.Variable command is the command being used.





ING330I Command execution wassuccessful

ExplanationFrom TSO, the function INGRCRPC was called toexecute a command in the SA NetView agent.

This command was executed successfully. Output datamight have been returned to the caller.

System actionThe program exits.



ING331I Command execution failed.Waiting for asynchronous outputhas been interrupted due totimeout.

ExplanationFrom TSO, the function INGRCRPC was called toexecute a command in the SA NetView agent.

This command execution failed due to timeout. Outputdata has not been returned to the caller.

The command might still be running on the NetViewtask until it is completed. However, the connection tothe command execution task has been interrupted andno data will be returned to the TSO caller.

System actionNone.


System programmer responseIncrease the timeout value in function INGRCRPC.

Check if the command is still running or it is waiting inthe NetView tasks queue.

Try to increase the number of working tasks for thecommand receiver.

ING332I Command execution failed. RC=rcSYSTEM=sys Command=cmdREASON:xxxx

ExplanationFrom TSO, the function INGRCRPC was called toexecute a command in the System Automation Agent.

The execution of command cmd failed with returncode rc in the System Automation Agent on systemsys. Additional error description xxxx might beavailable and describes the reason for the error. If therc is not one of the following reserved return codes,the reason is the first message that could be collected.

Reserved Return Codes:

The System Automation command receiver thatcontrols the execution of the command within theNetView task may return the following reserved returncodes.

Table 6. Reserved Return Codes

RC REASON DESCRIPTION

9001

CMD_NOT_AUTHORIZED NetViewcommandauthorizationerror.

9002

CMD_NOT_FOUND Invalid commandor command notfound.

9003

CMD_CAUSED_NEGRETC Commandreturned anegative returncode or aninternally usedNetView PIPEerror wasdetected.

CMD_CAUSED_HALTCOND HALT conditionraised due tocommand returncode -5.

REXX_PROCESSING_ERROR REXXprogrammingerror detected.



Table 6. Reserved Return Codes (continued)

RC REASON DESCRIPTION

9004

OPERID_INVALID Invalid orinactive targettask.

USERID_INVALID TSO user ID doesnot match anactive NetViewoperator task.

USERID_ERROR Internal error.

9005

INTERNAL_ERROR Internal error.

System actionThe function or command terminated.


System programmer responseAnalyze the netlog and search for further errormessages. For example, see explanation of errormessage ING338I.

In case of return code 9002, you can look for messageDSI002I. Return code 9002 may also be issued if thecommand resides in a PDS that has been appended toDSICLD via the OVERRIDE command, but the autotaskhas no authority to read from it.

In case of return code 9003, analyze your REXXprogram for possible programming errors. Forexample, see explanation of error message IRXnnnI.

In case of return code 9004, check if thecorresponding operator task exists and is active. Theoperator task is either equal to the TSO user ID thatcalled INGRCRPC, or was specified as the tasknameparameter in function INGRCRPC, or is per default oneof the SA auto operator functions AOFCMDnn(nn=01,02,…). INGRCRPC accepts a SystemAutomation automated function as target task. In thiscase, check that it contains an active operator task.

For commands executed by EVJRYCMD or AOFRYCM,the following help applies:

In case of return code 9002, you can find additionalinformation in //SYSTSPRT or in the redirected data setof your choice.

ING333I Receiver is starting for PPI=xxx

ExplanationThe RPC receiver with PPI receiver ID xxx is starting.

System actionThe receiver is ready to receive remote command.



ING334I Receiver is already running forPPI=xxx

ExplanationThe RPC receiver with PPI receiver id xxx is alreadyrunning.

System actionThe receiver terminates.

Operator responseSpecify a different PPI receiver id if you want to start anew receiver.


ING335I Execute remote command onbehalf of JOB=job_nameUSER=user_ID OPER=task_nameCLIST=clist_name COMMAND=cmd

ExplanationFrom TSO, the function INGRCRPC was called toexecute a command in the SA NetView agent. Thiscommand cmd will be executed on the NetView tasktask_name on behalf of the TSO job job_name, TSOuser user_ID, and TSO CLIST clist_name.

System actionNone.





ING336I Receiver PPI=xxx will be stoppeddue to operator request

ExplanationThe RPC receiver with PPI receiver id xxx is stoppingdue to operator request. A stop-command has beenreceived and issued by 'INGRCRCV STOP PPI=xxx'




ING337I PPI RECEIVER STATUS LIST

ExplanationThese messages are output of the command'INGRCRCV QUERY' and display all receiver PPI idsstarted via command 'INGRCRCV START'. Thefollowing example displays a list of two PPI receivers.One is running in a VOST.

ING337I PPI RECEIVER STATUS LIST STATUS PPI TASK VOST ------ -------- -------- -------- ACTIVE INGRCRCV DSI#0020 EMURCV2 ACTIVE PPIABC BDOW

System actionNone.



ING338I Function or command xxxx failed,RC=nn REASON=yyyy

ExplanationA function or a command with name xxxx failed withreturn code nn. Additional error description is given inyyyy.

It might be that an error has occurred in the past whileinitializing the RDS environment.

For explanation of return code nn see the table below.



System programmer responseDetermine why the function or command failed.Examine the netlog. If necessary, contact your IBMSupport Center.

Use Table 7 on page 326 to determine the returncodes used in message ING338I:

Table 7. Return Codes of ING338I

ModuleName ReturnCode and Description

INGRCVAF

204 Invalid name mask205 Invalid name mask, stem contains either + or *206 Invalid parmlist207 Invalid name mask, length of stem>8208 Invalid action212 Unsupported action216 Error in helper function, for example, INGPCGLB or INGPCREX

INGRCVAL

200 Invalid call to routine204 Invalid input name205 Invalid old value for action=A208 Invalid action212 Unsupported action216 Error in helper function, for example, INGPCGLB218 Error when global variable not exist for action=O220 Function aborted224 Syntax error in subroutine(procedure)236 EMULATOR INIT STATUS is not OK



Table 7. Return Codes of ING338I (continued)


INGRCVAX

0 OK2 RPC timeout4..24 RPC error60 Invalid SOURCE name104 Decode data items error108 Expected at least 1 data item112 Expected at least 1 data item114 service routine failed, for example, INGPCREX116 Host not supported200 Execution of remote command failed Return code from remote command is unknown or invalid200 Execution of remote command failed+nnn nnn is the remote return code from INGRCVAC or from INGRCVAL, for example, 404 means invalid input INGRCVAL

INGRCVAC

0 OK2 Mandatory parms missing4 Error in AOF_PPI_PARSE_DATA8 Error parsing DataItems12 Error parsing parmlist15 Error sending data, PIPE PPI error16 Error sending data, PIPE error20 INGRCVAL failed21 INGPCGLB failed22 INGRCVAF failed23 INGRCVAL failed for POOLIST24 Unexpected error28 Standard Safe not supported for action34 Triggering message missing36 ARCHIVE failed because RESTORE not OK1nn ARCHIVE failed2nn 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) failedSee also message ING344I for possible VSAM IO error description.

INGRCRPC

0 OK2 TIMEOUT4 Missing Input8 INGPCREX call failed9 INGPCSTK call failed10 Decoding response data items failed (stem)16 PPI error 20 REXX error such as Syntax, Novalue, and so on24 Invalid data buffer28 AOCT0000.REXMAC initialization failed32 Error while preparing input stem

INGRCRCV

0 OK4 Invalid action8 RECEIVER already active12 PPI error16 PIPE error20 Invalid parameter list24 Service failed28 Auto OPS environment checking failed40 Initialization failed

INGRCMDH

0 OK4 Not a RPC8 Invalid RPC input data15 Sending response via PPI failed. This might be the case due to timeout condition.16 Command execution failed





INRCEXC

0 OK1 Routing the command failed2 Executing the command failed on THIS task4 Bad input arguments8 AOF_PPI_PARSE_DATA failed

INGRCCSA

201 Memory object name exist already202 Init of lookup table failed203 Invalid object name too long (max 12 char)204 Invalid object name205 Invalid size, not a number206 Invalid parmlist207 Invalid trace parameters208 Invalid action212 Unsupported action216 Error in function INGPCCSA

INGRCRDX

2 INGRCRPC timeout4..24 INGRCRPC error104 Decode data items error108 Expected at least 1 data item112 Unexpected remote message116 Host not supported117 RDS working dataset not configured in CSA118 Must be called as command120 Service routine failed122 Incomplete installation detected for SA TSO REXX200 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

INGRCRDS

nnn<200 Error due to underlying services201 VALUE missing or invalid202 Mandatory parms missing203 Table name missing or invalid204 Error in AOF_PPI_PARSE_DATA205 COLUMNS missing or invalid206 Invalid parameter value208 Error parsing DataItems212 Error parsing parmlist215 Error sending data, PIPE PPI error216 Error sending data, PIPE error



220 No match, nothing updated or deleted221 INGPCGLB failed222 INGRCVAL syntax error223 Invalid action224 DEQ failed225 Export to Dataset failed226 Import to Dataset failed 227 Cannot determine data format from DSN229 ARCHIVE table name pre-validation failed230 INGRCREX (PUT) failed231 INGRCREX (GET) failed232 PUT/GET sequence violation233 Invalid environment. Must be called from REXX environment and must not be called from a PIPE stage.





INGRCRDSunderlyingservice

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 nameCreateTableRow: 11 Truncated at least one column 12 Unequal number of column names/values 13 Max length of a row is exceededUpdateTableRow:InsertTable: 21 Invalid column nameReadTextTableData/Header: 31 bad column delimiter 35 bad import headerCreateTable: 100 Table exist alreadyUpdateTableControl: 101 Table does not existModifyTableControl: 102 Table LOCK does not matchIterateTable: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 dataCreateTable:InsertTable:GlobalDatastore: 120 INGRCVAL failed, see GlobalDatastore(vn,'U')ListOfTables:ListOfPools: 130 INGPCGLB(QUERY_ACL) failed 131 INGPCGLB(QUERY_ACL) returns no



hexdataParser 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)

ING339I Receiver PPI=xxx recovers badcommand execution, continue...

ExplanationThe RPC receiver with PPI receiver id xxx executed aremote command which failed. However, the receivercontinues processing and waits for the next command.

System actionExecution of the current command terminates.Receiver continues.


System programmer responseDetermine why the remote command failed. Examinethe netlog.

ING340I Deleted n1 of n2 pattern matchingglobal symbols

ExplanationThe function INGRCVAF has filtered n1 number ofglobal variables. n2 global variables have beendeleted. If n2 is smaller than n1 then either the globalvariable cannot be found or an error occurred.



System actionAs many global variables have been deleted aspossible.



ING341I Receiver PPI=xxx has beenstopped

ExplanationThe RPC receiver with PPI receiver id xxx has beenstopped.




ING342I No receivers are started

ExplanationCommand 'INGRCRCV QUERY' does not find anyreceivers that were started.

System actionNone.

System actionNone.


ING343I Parameter xxxx is not supportedby function or command yyyy

ExplanationThe function or command yyyy was invoked passing aparameter that is not supported by Z SystemAutomation.

Variable xxxx identifies the parameter that is notsupported by Z System Automation.Variable yyyy is the name of the command thatdetected the error.


System programmer responseModify the script invoking the command.

ING344I JOB job_name FAILED: error_text

ExplanationThis message is used by command INGVALUE in orderto report an error, while performing an archive/restoreoperation. This message might be trapped by theautomation table.

Token 3 of the message is the subsystem job name,token 5 the subcommand that failed and token 6 thekind of error. For example, VSAM_IO_ERROR.

You can use this message to set the resourceRDSARCH, 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 thefailing NetView service.

ARCHIVE VSAM_IO_ERROR INGRCVSM RC=nnThe number is nn is the return code fromINGRCVSM.

ARCHIVE ERROR 36During SA initialization INGRDS was not initialized.

ARCHIVE ERROR 1nn - reasonAny other error during archiving RDS or other longglobal variables occurred. The reason describesthe error code nn.

RESTORE ERROR 3nn - reasonAny other error during restoring RDS or other longglobal variables occurred. The reason describesthe error code nn.

System actionThe originating command terminated.




System programmer responseDetermine why the function or command failed.Examine the netlog. You might want to check for themessage ING338I that provides additional informationabout the module that causes the error.

ING345I Status of long global variables: xxx

ExplanationCommand 'INGVALUE STATUS' reports the status ofthe long global variable framework. This message isalso written if the command 'INGVALUE RESTORE' wassuccessful.

xxx might have the following values:

• RESTORE SUCCESSFUL - Persistent long globalvariables were restored successfully.

• INITIAL RESTORE OK - Initialization of persistentlong global variables was successful duringinitialization of Z System Automation.

• INITIAL RESTORE NOT DONE - Initialization ofpersistent long global variables was not done duringinitialization of Z System Automation.

• INITIAL RESTORE FAILED - Initialization ofpersistent long global variables failed during ZSystem Automation initialization.

System actionNone.


System programmer responseDetermine why the function or command failed.Examine the netlog if the status is not successful.

ING346I Abort function xxx on purpose atLINE nn

ExplanationThe REXX function xxx detected an error at line nn. Thepurpose is that the error causes invalid call toroutine. This can only be achieved by returningnothing on purpose. See example:

ING338I Function or command INGRCVAL failed, RC=204 REASON=invalid character foundING346I Abort function INGRCVAL on purpose at LINE 83 270 +++ returnIRX0045I Error running INGRCVAL, line

270: No data specified on function RETURN

System actionThe function or command terminated.


System programmer responseAnalyse the netlog and search for further errormessages. See explanation of error message ING338I.

Note: Ignore the error the IRX0045I, since No dataspecified on function RETURN was done onpurpose. The real reason was detected earlier in thefailing program which caused message ING346I.

ING347I Receiver PPI=id does not start dueto an unsupported environment forxxx

ExplanationThe receiver task was started by command 'INGRCRCVSTART OPF=xxx'. The receiver searches for theexistence of the automation operator task (forexample, if xxx is AOFCMDOPER then the tasks areAOFCMDnn, nn=00,01,02,..) but no active task wasfound.

System actionReceiver terminates.


System programmer responseCheck if the operator tasks are defined or why they areinactive.

ING348I Receiver PPI=id starts with adegraded operator function arraymm of nn for xxx.

ExplanationThe receiver task was started by command 'INGRCRCVSTART OPF=xxx'. The receiver searches for theexistence of the automation operator task (forexample, AOFEMUnn, nn=00,01,02,...) but found atleast one task that was inactive or not defined.



The receiver task continues running but executingincoming commands might be degraded because theinactive tasks are skipped, and commands might bequeued.

• The number mm is the number of active tasks• The number nn is the number of defined tasks• The variable xxx is the name of the operator function

array.

System actionReceiver continues.


System programmer responseCheck why not all operator tasks are inactive.

ING350I Improper Job Log Monitoringdefinitions detected for name,RSN=rsn

ExplanationDuring initialization SA z/OS detected an improperdefinition for the Job Log Monitoring task.

• The variable name shows the subsystem name thatis affected.

• The variable rsn shows the reason:10

Job Log Monitoring interval defined but nomessage ID.

11Offset specification is invalid.

12Token specification is invalid.

13Message ID defined even if JOBLOGALL has beenspecified.

14Message offset is 0 but no token has beendefined.

15Token has been defined but no message offset.

16Monitoring interval is invalid.

17DD name specification is invalid.

18Message ID is invalid.

System actionThe definition is ignored.

Operator responseCorrect the definition and refresh the configuration ifdesired.


ING360I Security check failed RC=nnReason: reason_text

ExplanationSystem Automation security checking fails such thatnot one of the other security messages can be issuedany more. The reason_text explains the error.

System actionSystem Automation does not grant access.


System programmer responseThe reason_text may help you determine the reasonfor the error. If an internal API error occurred switchon trace and rerun the command.

ING361I Security check for resource(s)failed.

Explanation:System Automation security checking for one or moreresources failed. In the NETLOG this is a multilinemessage with additional ING362 message lines.

System action:The System Automation command is not carried out.

Operator response:Check the NETLOG for more information, especiallythe ING362 message lines or messages issued by SAFproduct. Request access to the listed resource and trythe command again.


ING362I profile=profile access=accessuserid=userid rc=rc

Explanation:System Automation checking for the specifiedresources failed. This message denotes the resource



profile, the access authority requested and the useridfor which the check was done. It further shows thereturn 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 SAFproduct. If the return code is 4 theSECOPTS.SARESAUT is set to ON.FAIL and no profileexists. If the return code is 8 you do not have therequired access rights.


ING365I Security check for target domaintargetdomid failed.

ExplanationA System Automation command tries to access anagent on a remote system. SAF check failed for thefollowing profile within class SYSAUTO:

AGT.sysplex.xcfgrp.TARGET.FROMDOM.domain.TODOM.targetdomid

System actionThe System Automation command is not sent to theremote system.


System programmer responseCheck if the user of the System Automation commandis allowed to execute the command on a remotesystem. Give the user READ permission to thecorresponding SAF profile. There might be additionalSAF messages such as ICH408I for additionalinformation.

ING366I System Automation third partysecurity check failed: reason_text

ExplanationA command received from outside NetView (forexample, via PPI) is rejected for execution. SAFchecking against following profile within classNETCMDS failed: netid.domid.command

The reason_text provides more detail:

Access denied for USER=user CLASS=NETCMDSPROFILE=xxxx. In this case, grant the user accessto the specified profile.Profile not defined PROFILE=xxxx inCLASS=NETCMDS. In this case, define the specifiedprofile in NETCMDS.

System actionSystem Automation does not grant access.


System programmer responseThe reason_text may help you to determine the reasonfor the error. There might be additional SAF messagessuch as ICH408I for additional information.

ING370I

ExplanationThis message is used to return command responsedata of any kind. It helps to distinguish between thevarious systems that were specified in the TARGETparameter.

The first 10 characters specify always the systemname where the response comes from. The responsedata starts at position 11. If the response has multiplelines, then ING370I will be returned multiple times.

System action:None.



ING371I Execution result SYSTEM=ssssssssCOM=ccccc RC=nn

ExplanationThis message is used to return command completioninformation. It helps to distinguish between thevarious systems that were specified in the TARGETparameter.

This message may occur only once per target system.

• The ssssssss specifies the name of the system wherethe command was executed.

• The nn specifies the command return code.



• The ccccc specifies the communication type that isused to transmit the command to the target system.The following types are supported.LOCAL

The command was executed on local systemXCF

XCF communication within the same SAplexGWAY

Gateway and using remote commandRMTCMD

Remote commandEXTXCF

Extended XCF within the extended XCFcommunication group

OTHEROther communication mechanism

System action:None.



ING372I Transmission error, RC=nnREASON: xxxxx

ExplanationThis message is used to return the overall commandtransmission code.

This message might occur at most once if commandexecution fails on at least one of the target systems orif another kind of error occurs before the commandcan be sent.

The message is issued by the System Automationinternal function INGPYCOM which might be called byexternal commands.

The reason xxxxx variable describes the return code intext form.

Return Code nn:

Success:

0 OK command executed

4 OK but NO data returned (only ifRESP=YES)

No attempt to execute remote command:

10 No command in default safe

11 TARGET= parameter not available or novalue

12 Parameter parsing error

14 Target is not active

15 Only one target is allowed (only ifSNGLTGT=YES)

Failure when attempting to execute remote command:

20 Default command transmission error

21 Timeout

22 Invalid command on target system

23 Command is not authorized

24 Command returned a negative returncode or PIPE error or PIPE stage errordetected

25 Command caused halt condition (forexample, NOVALUE)

26 Operator task is not active on localsystem

27 User command was executed on targetsystem but failed with RC<>0

28 Cannot execute user command due toinvalid user ID

29 Cannot execute user command due tointernal error in INGRYCOM

System action:The command execution failed on at least one targetsystem.


System programmer response:A return code value that is smaller than 20 might becaused by invalid input parameters. Normally thismessage is accompanied by other messages that areissued by a System Automation command that actuallytransmits another command to remote systems. Checkthe NETLOG for extra error messages.

ING376I The E2E agent cannot connect todmn because reason.

ExplanationA request cannot be sent to a remote automationdomain because the connection data is not available.It is either because the E2E adapter on the remotedomain is not yet started, or because the E2E adapteris already running but it's the first time that thecorresponding DMN has been loaded, for example bycommand "INGAMS REFRESH". This message is oftenaccompanied with message ING377I.



The variable dmn shows the name of the remoteautomation domain.The variable reason shows an explanation of theerror.

System action:The processing of the E2E agent continues.

Operator response:Notify your system programmer.

System programmer response:Start or recycle the E2E adapter on the remoteautomation domain.

ING377I The E2E agent service xxx failedwith RC=retcode,REASON=reason_text

ExplanationThe E2E agent tried to execute a service that failed.

• The xxx variable specifies the service that failed.• The retcode variable specifies the return code of the

failing service.• The reason_text variable provides extra error

description.

Possible return codes for INGRE2E and INGRE2E1 areas follows:

201 An error occurred when the parameter list isparsed.

202 The action is not supported.

203 The parameter is invalid.

204 Mandatory parameter is missing.

205 Cannot find resource.

219 Timeout during invocation of Java plug-in

220 Domain has no short name mapping.

221 Invocation of the java service failed viaINGJAVA.

222 INGPYAMC failed.

223 Transmission to remote system failed.

224 No current system was found for E2E agentin SYSPLEX/GRP.

225 An Online or Offline request failed due to baddomain, for example, there is no persistentdata available for this domain.

226 QRYINFO detects that the E2E agentinitialization is not yet complete.

227 Initialization is aborted because the E2Eagent exists on same or remote system.

228 Cannot refresh the E2E agent becauseINGREQ fails.

229 Necessary CGlobals are not defined orcorrupted. The E2E agent might be stopped.

230 Cannot send an event E2EAGT_ON orE2EAGT_OFF to the E2E adapter.

231 REFRESH is pending.

232 Internal service failed.

233 Cannot get domain information becausethere is no persistent data available for thisdomain or the domain is not running. Recyclethe E2E adapter on the remote domain.

234 Cannot get domain information because thedomain is unknown or disabled.

235 Got TCP/IP connection error to the remoteE2E adapter

236 The E2E agent terminated itself because theprimary automation manager (PAM) was notavailable.

237 Execution of an MVS or NetView commandfailed.

System action:The processing terminates.

Operator response:Notify your system programmer.

System programmer response:Determine why the service failed and correct theproblem. Examine the netlog for extra information.

ING378I The E2E agent task tasknamefailed for domain dom, reason.

ExplanationThis diagnostic message is issued by the E2E agent tosignal that a task was executed unsuccessfully withinthe USS process of the E2E agent. For example, thetask might be an online, offline, or subscriptionrequest to the remote domain that is specified in thevariable dom. Many of these tasks might be processedwithin a thread pool in parallel and an unsuccessfulresult will be reported for each task and remotedomain.

The task can be one of the following types.online

Start request of remote resource.offline

Stop request of remote resource.subscribe

Subscription request for remote domain.



unsubscribeUnsubscription request for remote domain.

ResynchDomainSynchronization request of remote resource.

The variable reason shows the text that explains whatfails.

• Unknown resource resource

The specified remote resource is not known on theremote domain.

• resource ref, remote resource resource

The task cannot be executed successfully for theremote resource. See extra error messages.

The ref variable shows the SA resource referenceand the resource variable shows the referencedresource on the remote domain.

This diagnostic message appears in a multi-linemessage together with other error messages that aredetected by the E2E agent. The multi-line message iswritten to NETLOG only.

System action:None


System programmer response:Analyze the error messages and check the reason ofthe problem.

ING379I The E2E agent is not running.

Explanation:This message is issued by the E2E agent to signal thatthe command cannot be executed by the USS processof the E2E agent because the E2E agent is not started.

System action:None


System programmer response:Start the E2E agent.

ING380I Persistent data store is initializing

Explanation:This message is used to indicate that the persistentdata store is being starting up.

System action:None.



ING381I Persistent data store is started

Explanation:This message is used to indicate that the persistentdata store is fully initialized and operational.

System action:None.



ING382I Persistent data store isterminating

Explanation:This message is used to indicate that the persistentdata store is being shut down.

System action:None.



ING383I Persistent data store is terminated

Explanation:This message is used to indicate that the persistentdata store is shut down completely.

System action:None.



ING384I Persistent data store is notavailable

Explanation:This message is used to indicate that the persistentdatastore is not available.

System action:The requested operation is not carried out.

Operator response:Start the APL representing the persistent data store.


ING385I Persistent data storecommunication failed - diagnosisinfo:

Explanation:



This message is used for diagnosis purposes. It is thefirst line of a multi-line message and is written to theNetlog only. Subsequent lines provide moreinformation.

System action:None.



ING386I Persistent data storecommunication failed

Explanation:Although the persistent data store is available, aproblem exists with the communication. See Netlog formessage ING385I.

System action:None.



ING387I Persistent data storecommunication timed out

Explanation:A timeout occurred in the communication to thepersistent data store. The wait time of 5 seconds wasexceeded.

System action:None.

Operator response:Retry the action again.

System programmer response:Check whether the persistent data store worksproperly.

ING388I Persistent data store is breaking

Explanation:This message is used to indicate that the persistentdata store has encountered a severe error and willshut down.

System action:The application shuts down.



ING389E Persistent data store is broken

Explanation:This message is used to indicate that the persistentdata store is shut down completely but is unable torestart without any additional action.

System action:None.


System programmer response:Check the error description that is provided with themessage and take additional steps to resolve theissue.

ING390I Only current templates can beused to create dynamic resources

Explanation:You are trying to create a dynamic resource from anoutdated template.

System action:None.

Operator response:Choose a current template.


ING391I Creation failed. Resource: name

ExplanationAn automated resource could not be created. SeeNetlog for message ING413I.

The variable name identifies the resource that was notcreated.

System action:None.



ING392I Creation was successful.Resource: name

ExplanationAn automated resource was successfully created.

The variable name identifies the resource that wascreated.

System action:A resource was created and added to automation.

Operator response:



None.


ING393I Deletion was successful. Filter:filter - Resources: num

ExplanationOne or more automated resources were successfullydeleted.

The variable filter shows the filter that was used toidentify the resources.The variable num shows the number of deletedresources.

System action:One or more resources were deleted.



ING394I Resource cannot be created onsystem name

ExplanationAn automated resource is intended to be created on aninvalid system.

The variable name specifies the name of the invalidsystem.

System action:No resource is created.

Operator response:When dynamically creating an automated resource ona particular system, verify that the system can beaccessed and that the template does exist there.


ING395I Multiple matches. Filter: filter

ExplanationThe specified filter yields more than one result whereonly one was expected.

The variable filter shows the filter that was specified.

System action:None.

Operator response:Choose a more precise filter.


ING396I No match. Filter: filter

ExplanationThe specified filter yields zero results where at leastone was expected.


System action:None.

Operator response:Choose a less precise filter.


ING397I Deletion failed. Filter: filter

ExplanationOne or more automated resources could not becreated. See Netlog for message ING414I.


System action:None.



ING400I BCPM Work order work_order iscreated on BCPM server server,system system.

ExplanationThis message displays the identifier of a work ordercreated in the Business Continuity Process Manager(BCPM) as the result of an outage event on the system.

System actionNone.



ING401E Unable to create BCPM Workorder. Return code return_codefrom BCPM server server, systemsystem.



ExplanationAn outage event from the system cannot be deliveredor processed by the Business Continuity ProcessManager (BCPM) server.

System actionNone.

Operator responseInform the IT Service Continuity administrator aboutthe outage.

System programmer responseRefer to the netlog for additional messages issued bythe SA z/OS INGOMX command.

ING402I BCPM server server is notifiedabout completion of task task withcode code, system system.

ExplanationThe task triggered by the Business Continuity ProcessManager (BCPM) has completed. BCPM has receivedand processed the task completion information.

System actionNone.



ING403E Unable to notify BCPM serverserver about completion of tasktask with code code, systemsystem. INGOMX command hasreturned error_code.

ExplanationThe task triggered by the Business Continuity ProcessManager (BCPM) has completed, but the BCPM cannotreceive the task completion information. The INGOMXcommand ended with an error.

System actionNone.

Operator responseInform the IT Service Continuity administrator aboutthe problem.

System programmer responseRefer to the netlog for additional messages issued bythe INGOMX command. Check for the reason for theINGOMX error.

ING404E BCPM server server cannotprocess notification from tasktask. BCPM exception isexception_code.

ExplanationThe task triggered by the Business Continuity ProcessManager (BCPM) has completed, but the BCPM cannotprocess the task completion information.

System actionNone.



ING405I BCPM replied to the WTOR wtorwith ID reply_id with reply onsystem system.

ExplanationThe outstanding WTOR was reprocessed by theBusiness Continuity Process Manager (BCPM).

System actionA process requested WTOR is continued.



ING406E BCPM unable to reply to the WTORwtor with reply on system system.RC=rc.



ExplanationThe outstanding WTOR is either no longer active andhas already been reprocessed by an operator orautomation product, or it cannot be reprocessed bythe Business Continuity Process Manager (BCPM).

System actionNone.

Operator responseCheck for outstanding WTORs on the system. Informthe Service Continuity Team about the problem.


ING407E BCPM unable to execute GDPSbatch script batch_script. Returncode rc, reason reason.

ExplanationThe GDPS batch script was triggered by the BusinessContinuity Process Manager (BCPM), but cannot beexecuted.

System actionThe script is not executed.


System programmer responseRefer to the netlog for additional messages issued byGDPS.

ING408I BCPM command command endedwith rc=rc.

ExplanationThe command triggered by the Business ContinuityProcess Manager (BCPM) has completed.

System actionNone.



ING410I Persistent data store backup wassuccessful:

Explanation:This message indicates that the backup of thepersistent data store was successful. The messagealso contains the USS path to the backup directory.

System action:None.



ING411I Persistent data store backupfailed:

Explanation:This message indicates that the backup of thepersistent data store failed.

System action:None.



ING412I Persistent data store backupsmust be deleted manually:

Explanation:This message indicates that the application wasunable to delete old backups.

System action:None.



ING413I Dynamic resource creation failed -diagnosis info:

Explanation:This message is used for diagnosis purposes. It is thefirst line of a multi-line message and is written to theNetlog only. Subsequent lines provide moreinformation.

System action:



None.



ING414I Dynamic resource deletion failed -diagnosis info:

Explanation:This message is used for diagnosis purposes. It is thefirst line of a multi-line message and is written to theNetlog only. Subsequent lines provide moreinformation.

System action:None.



ING420I IBM Z System AutomationOperations REST server isinitializing

Explanation:This message is used to indicate that the SystemAutomation Operations REST server is starting up.

System action:None.



ING421I IBM Z System AutomationOperations REST server isinitialized

Explanation:This message is used to indicate that the SystemAutomation Operations REST server is fully initializedand operational.

System action:None.



ING422I IBM Z System AutomationOperations REST server isterminating

Explanation:This message is used to indicate that the SystemAutomation Operations REST server is shutting down.

System action:None.



ING423I IBM Z System AutomationOperations REST server isterminated

Explanation:This message is used to indicate that the SystemAutomation Operations REST server is shut downcompletely.

System action:None.



ING424I IBM Z System AutomationOperations REST server isbreaking

Explanation:This message is used to indicate that the SystemAutomation Operations REST server has encountereda severe error and will shut down.

System action:The application shuts down.



ING425E IBM Z System AutomationOperations REST server is broken:&1

ExplanationThis message is used to indicate that the SystemAutomation Operations REST server is shut downcompletely but is unable to restart without anyadditional action.

The &1 variable describes the error that the SystemAutomation Operations REST server encountered.

System action:None.

Operator response:



None.


ING500I error_text

ExplanationA program that has failed has produced this additionalinformation regarding the error. See precedingmessages.

System actionExecution probably halts. See subsequent messages.


System programmer responseAssist the operator. Contact your IBM Support Center.

ING501I debug_text

ExplanationThis is a generic informational message that shows theflow within the function.

System actionExecution continues.



ING502I SA z/OS Discovery Library Adapterstarted date time

ExplanationThis indicates the time that the SA z/OS DLA startedexecution.




ING503I SA z/OS Discovery Library Adaptercompleted date time, RC=nn

ExplanationThis indicates the time that the SA z/OS DLAcompleted execution.

System actionExecution finishes.

Operator responseIf RC=0 the output file is now ready to be downloaded.


ING504I Checksum data updated

ExplanationFollowing a successful run, the checksum data(member @CHCKSUM) stored in the output data sethas been updated.




ING505I Checksum data cleared; bad run

ExplanationThe SA z/OS DLA has failed during its execution and,because it has not been able to generate a valid outputbook, it has cleared the checksum data.




Operator responseAnalyze the problem and, when fixed, rerun theSA z/OS DLA to generate a valid book.

System programmer responseAssist the operator.

ING507I Data in dataset_name truncated;Increase output LRECL

ExplanationThis indicates that the SA z/OS DLA tried to write a lineto the output data set that was longer than the dataset's LRECL.

The variable dataset_name identifies the fullyqualified name of the data set.

System actionThe book is generated with the truncated line.Depending on the nature of the truncated data, theiDML book that is generated may or may not be valid.

Operator responseReallocate the data set with a longer LRECL and rerunthe SA z/OS DLA.

System programmer responseAssist the operator.

ING508I Output of book book skipped;checksum matches

ExplanationThe SA z/OS DLA has successfully executed, howeverthe contents of the generated book are the same asthe previously generated book in the same output dataset. Generation of a book from the newly generateddata is therefore suppressed in order to preservediscovery date and time information in the previouslygenerated book.

The variable book identifies the book.




ING509I Data set name is not a partitioneddata set

ExplanationThe specified output data set is not a partitioned dataset.

The variable name identifies the data set.

System actionNone.

Operator responseCorrect the name of the data set and reissue thecommand.


ING510I program Directory OPEN failed forDDName ddname, RC rc

ExplanationThe program was unable to open the directory for thedata set that is pointed to by the ddname. The OPENmacro gave the specified return code.


Operator responseThe output data set must be a PDS—you cannot use asequential file. Contact your system programmer.


ING511I program Directory READ failed forDDName ddname, RC rc RS rsn

ExplanationThe program tried to read the directory for the data setthat is pointed to by the ddname, but received theunexpected return and reason codes indicated.




Operator responseThe output data set must be a PDS—you cannot use asequential file. Contact your system programmer.


ING512I program STORAGE macro callfailed for type type, RC rc

ExplanationThe program received an unexpected return code froma call to the STORAGE macro for the type of storagethat was requested.



System programmer responseThere may be other messages in the netlog or syslogat the time of the incident that will give more details. IfNetView is not running REGION=0M, try increasing itsregion size. Contact your IBM Support Center.

ING513I program Codepage TranslationRoutine CUNLCNV returned RC rc,RS rsn

ExplanationThe program called the CUNLCNV routine and receivedan unexpected return and reason code.




ING520I REQUEST request WASSUCCESSFUL FOR function

ExplanationThe specified request for the specified recordcompleted successfully.

The variable request identifies the request.The variable function identifies the function.

ING521I REQUEST request wasUNSUCCESSFUL FOR function

ExplanationThe specified request for the specified function failedto process.

The variable request identifies the request.The variable function identifies the function.

ING522I TOO FEW PARAMETERSSPECIFIED

ExplanationYou did not enter the minimum number of parametersrequired for the operand used for the INGPWcommand.

Operator responseIssue the command again using the correct number ofparameters.

ING523I INVALID DELIMITER OF delimiterENCOUNTERED

ExplanationYou entered the specified delimiter, but the delimiter isnot correct for the INGPW command.

The variable delimiter identifies the incorrectdelimiter.

Operator responseIssue the command again using the correct syntax.

ING524I request ERROR PROCESSINGVSAM DATASET

ExplanationINGPW issued a VSAM function and received an errorwhile processing a request.

The variable request identifies the name of theVSAM macro request that was processing when theerror occurred.



System actionThe INGPW command fails and does not perform itsfunction.


System programmer responseBrowse the NETLOG for the specific VSAM errormessage that signalled the error. Refer to the VSAMreference manuals to correct the error. If the errorpersists, contact IBM Software Support.

ING525I PARAMETER parameter INVALIDfor REQUEST command

ExplanationThe specified parameter that must be passed to thespecified command is incorrect.

The variable parameter identifies the incorrectparameter.The variable command identifies the name of thecommand.

System actionThe command fails and does not perform its function.

Operator responseIf the message appears on an operator panel, correctthe parameter and re-enter the command. Ifnecessary, view the help for the INGPW command toassist in entering a valid command. If the messageappears in the NETLOG, notify your systemprogrammer.

System programmer responsePerform the problem determination function on thecommand. Find the error in the NETLOG and contactIBM Software Support.

ING526I EXPECTED PARAMETERSMISSING FOR REQUEST command– request

ExplanationThe specified parameter that must be passed to thespecified command is missing.

The variable command identifies the incorrectcommand.

The variable request identifies the name of therequest.

System actionThe command fails and does not perform its function.

Operator responseIf the message appears on an operator panel, correctthe input and re-enter the command. If necessary,view the help for the INGPW command to assist inentering a valid command. If the message appears inthe NETLOG, notify your system programmer.


ING527I EXPECTED PARAMETERS INVALIDFOR REQUEST command -parameter = value

ExplanationThe parameter that must be passed to the specifiedcommand is incorrect.

The variable command identifies the name of thecommandThe variable parameter identifies the name of theparameterThe variable value identifies the value of theparameter that is incorrect.

ExplanationThe command fails and does not perform its function.

Operator responseIf the message appears on an operator panel, correctthe input and re-enter the command. If necessary,view the help for the INGPW command to assist inentering a valid command. If the message appears inthe NETLOG, notify your system programmer.


ING529I p1 p2 p3 p4 p5



ExplanationThe report is the response to an INGPW request.

Operator responseRefer to the INGPW reference manuals for details.

ING530I operator NOT AUTHORIZED TOrequest RECORD FOR user owner

Explanationoperator is not authorized to execute specified INGPWrequest. The execution of the request is rejected.

The variable operator identifies the NetViewOperator attempting to execute the INGPWrequest.The variable request identifies the attemptedINGPW operation.The variable user identifies the userid of the INGPWrequest for which password maintenance servicesare required.The variable owner identifies the owning entity forwhich password maintenance services arerequired.

System action:Processing of the INGPW request fails.

Operator response:Contact your system programmer to obtain thenecessary authorization to execute the command.

System programmer responseExamine the SYSLOG for ICH408I messages givingmore details about the effective ACEE and requiredpermissions.

Evaluate the need the operator has for the INGPWrequest. If authorization should be granted, notify thesecurity administrator.

Command INGPW requires the following permissionsto the resource ING.PW.user.owner in the classSYSAUTO:

READ for INGPW READ request

UPDATE for INGPW UPDATE request

CONTROL for INGPW INIT and REGENrequests

ALTER for INGPW DELETE request

ING531I PASSWORD IS TOO length

ExplanationYou specified a new password with an incorrect lengthon the INGPW command. Passwords must be aminimum of 4 characters and a maximum of 20characters.

The variable length contains the value LONG orSHORT and explains why there are too many or toofew characters.

System actionThe INGPW command fails.

Operator responseReissue the command with a new password of thecorrect length.

ING532I NETVIEW PASSWORD DATASETNOT ALLOCATED

ExplanationThe password data set is not allocated in the ProductJob Control Language (JCL).


System programmer responseAdd an INGPSWD DD statement to the procedure toallocate the VSAM data set.

ING533I ERROR OPENING PASSWORDDATASET

ExplanationINGPW cannot open the INGPSWD DD password dataset.


System programmer responseEnsure that the INGPSWD DD password data set isallocated correctly and is defined to the Product.

ING534I RECORD FOR data1 data2 NOTFOUND



ExplanationThe information for the specified data cannot befound.

The variable data1 identifies the unique dataidentiferThe variable data2 identifies a second unique dataidentifier.

Operator responseIf the data specified is a user ID and an owner ID,notify your system programmer. If the data specifiedrelates to another function, modify any filter settingsthat are in effect. If problem persists, notify yoursystem programmer.

System programmer responseIf the data specified is a user ID and an owner ID, usethe INIT option to specify a password record for theuser. For any other data, browse the NETLOG forinformational messages, and ensure that the relevantfunction has initialized successfully.

ING535I CURRENT PASSWORD IS current

ExplanationINGPW retrieved the specified current password fromthe password data set.

The variable current identifies the currentpassword.


System programmer responseEnsure that the message is suppressed so that it doesnot appear in the log or on an operator terminal.

ING536I CURRENT/NEW PASSWORD iscurrent/new

ExplanationThe INGPW command randomly generated thespecified new password because the current passwordwas defined with an expiration date and is expired, ornew password was requested by the INGPW REGENcommand.

The variable current identifies the currentpassword.The variable new identifies the new password.


System programmer responseAutomation Product suppresses this message, but theroutines that perform cross-product logons can stilluse it. Change the external product password for theaffected user and update the record in the passworddataset using INGPW UPDATE command, if required.

ING537I CURRENT PASSWORD IS password- ERROR CREATING NEWPASSWORD

ExplanationThis message displays the current password. Thepassword record was defined with an expiration dateand is expired, but the INGPW command cannotgenerate and store a new one because of a VSAMerror.

The variable password identifies the currentpassword.


System programmer responseThe Automation Product suppresses this message, butthe routines that perform cross-product logons canstill use it. Browse the NETLOG for the specific VSAMerror message that signalled the error. Refer to theVSAM reference manuals to correct the error. If theerror persists, contact IBM Software Support.

ING538I NEW PASSWORD UPDATE FAILED- VSAM ERROR

ExplanationVSAM could not update the current password held inthe INGPSWD DD password data set to the newpassword because of a VSAM error.


System programmer responseBrowse the NETLOG for the specific VSAM errormessage that signalled the error. Refer to the VSAMreference manuals to correct the error.



ING539I NEW PASSWORD UPDATE FAILED- NO NEW PASSWORD

ExplanationVSAM cannot update the current password held in thepassword data set to the new password because nopassword has been assigned.


System programmer responseWait until the password expires before issuing theUPDATE parameter, or use the REGEN parameter togenerate a new password.

ING600I LOOPING ADDRESS SPACESUPPRESSION REPORT

ExplanationThis is a multiline message that is generated wheneverthe Looping Address Space Suppression Monitor runs.It contains information about the results of the queryto OMEGAMON the routine has made and details ofany apparently looping address spaces that are found,along with details of any planned corrective actions.

This message only appears in the Netlog and is notavailable for automation.

System action:The monitor runs again after the appropriate interval,any corrective actions indicated will be taken.



Classes: None.

ING601E LOOPING ADDRESS SPACEDETECTED: jobname stepname(ASID asid)

Explanation:The Looping Address Space Suppression monitor hasfound an address space that appears to be in a CPUintensive loop and has been instructed to issue awarning message. The variables identify the addressspace in question.

System action:The monitor takes any corrective actions specified byyour policy for it. It then runs again after theappropriate interval. At this point it may take moreactions, including issuing another warning message.

Operator response:Investigate. Notify your system programmer.

System programmer response:Fix the problem. If it is a known false positive result,update your policy to ignore it.

Classes: 40 44

ING602I LOOPING ADDRESS SPACEDIAGNOSTIC REPORT

ExplanationWhen the Looping Address Space Suppression monitorexecutes a DIAG instruction it produces a diagnosticreport. The report is a multiline message and is onlyavailable in English.

The report is generated through OMEGAMON Inspectfunctionality and indicates where the instructionpointer was within the looping address during a smallsampling window. For address spaces that are in atight CPU loop, this will identify the portion of the codewhere 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 thesame one), and then gives a list of CSECTs and offsetsalong with a percentage indicating how often thelooping 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 theapplication. If it is a known false positive result,update your policy to ignore it.

Classes: None

ING800I VERIFYING type-modelHARDWARE AUTOMATIONINTERFACE

ExplanationA check of the type and model of the hardwareautomation interface is performed.

The variable type-model shows the type and modelof the hardware being verified.

System actionThe verification process for the specified processor isstarting.





ING801I AUTOMATION INTERFACE NOTSUPPORTING type-modelHARDWARE

ExplanationVerification determined that the processor hardware isnot supported

The variable type-model shows the type and modelof the hardware.

System actionNone.



ING802I HARDWARE INTERFACECOMPONENT HSAET32 CANNOTBE ACTIVATED

ExplanationAn error was reported by the HSAET32 internalcommand. The command that establishes andactivates the hardware interface failed.

System actionNone.


System programmer responseCheck the netlog or the system log for HSAxxxxmessages about the problem.

ING803I HARDWARE INTERFACE AUTOOPERATOR autotask CANNOT BESTARTED

ExplanationThe named autotask failed to start. The hardwareinterface cannot be used.

The variable autotask shows the autotask thatcould not be started.

System actionNone.


System programmer responseCheck the netlog for additional messages. Correct theproblem and activate the autotask again. This willinitialize the hardware interface.

ING804I HARDWARE AUTOMATIONINTERFACE OF type-modelPROCESSOR VERIFIED

ExplanationThe verification for the specified processor has ended.

The variable type-model shows the type and modelof the hardware.

System actionNone.



ING805I requestor REQUESTS TO CONNECTTO CPC cpcaddr

ExplanationThe hardware interface tries to establish a connectionto the indicated processor hardware.

The variable requestor shows the originator of therequest.The variable cpcaddr shows the address of the CPC.






ModuleINGRVX80

class40.

ING806E COMMUNICATION WITH CPCcpcaddr CANNOT BEESTABLISHED

ExplanationA failure occurred while the processor hardware wascontacted through the hardware interface.

The variable cpcaddr shows the address of the CPCthat a session could not be established with.

System actionNone.


System programmer responseCheck the netlog for AOFAxxxx messages to obtainmore information, for example, the available conditionand sense codes. Correct the problem and restart thesession to the CPC.

ModuleINGRVX80

ING807I OPERATOR opid IS WAITING FORSYSOPS INITIALIZATION TOCOMPLETE

ExplanationThe operator task is currently executing the clistINGRX810 or INGRX805 and halts processing until theNetView common global variable AOFCOMPL has avalue of YES, which indicates that SA z/OS SysOpsinitialization is complete. This halt is a temporarycondition. Processing continues once SA z/OS SysOpsis initialized. Message ING808I is issued to indicate

that the continuation of the clist execution for theoperator task.

The variable opid shows the name of the affectedNetView operator task.

System actionNone.


System programmer responseIn situations when SA z/OS SysOps cannot initialize,you can use the STOP FORCE command to end thecurrent command of such an operator. For moreinformation about the SA z/OS common global variableAOFCOMPL, see IBM Z System Automation Customizingand Programming.


ING808I OPERATOR opid ENDED TO WAITFOR SYSOPS INITIALIZATION

ExplanationThe operator task continues to execute the clistINGRX810 or INGRX805 after processing was halted.Message ING807I was issued to indicate the haltcondition for the operator task.

The variable opid shows the name of the affectedNetView operator task.

System actionNone.




ING809I BCPII EVENT ERROR(rc) BETWEENCPC cpcaddr AND domain/operator. LASTS(stime)



ExplanationA general BCPii event wait occurred. The BCPiiconnection will be terminated.

The variable rc is the HwmcaWaitEvent return codepassed back from the System z API to the caller(INGHWCOM), while waiting for event data from theSupport Element.

The variable cpcaddr is the Processor name defined asSA-PDB/Connection Flag/CPC Name of the processorin SNA netid.nau format. The connection flag indicates:L

BCPii local connection. SA z/OS targets its ownCPC.

RBCPii connection to a remote CPC using a HMC forrouting.

.The Connection Flag information is not available.

The variable domain is the NetView domain name ofthe BCPii connection.

The variable operator is the operator task name of theevent session for the affected BCPii connection.

The variable stime is the Date/Time stamp of the lastsuccessful connection start in the formatyymmddhhmmss.

System action:The BCPii session terminates.


System programmer response:For return code information, refer to the conditioncodes table in the appendix section “InternalTransport Services "0Bx00xxx"” on page 566 of IBM ZSystem Automation Messages and Codes.

Module:INGCHW0E

Classes40

ING810I requestor REQUESTS TODISCONNECT FROM CPC cpcaddr

ExplanationThe hardware interface terminates the communicationwith the indicated processor hardware.

The variable requestor shows the originator of therequest.The variable cpcaddr shows the address of the CPC.




ModuleINGRVX80

class40.

ING811I BCPII CONNECTION HEARTBEATBETWEEN CPC cpcaddr ANDdomain/operator FAILED.LASTS(stime)

ExplanationFor a period of 4 minutes, the Support Element of theaddressed CPC has not responded to the BCPiiheartbeat request of the operator task running in theNetView domain. The BCPii event connection is nolonger working.

• The variable cpcaddr is the Processor name definedas SA-PDB / Connection Flag / CPC Name of theprocessor in SNA netid.nau format. The ConnectionFlag indicates:L


RBCPii connection to a remote CPC using a HMCfor routing.


• The variable domain is the NetView domain name ofthe BCPii connection.

• The variable operator is the operator task name ofthe event session of the affected BCPii connection.

• The variable stime is the Date/Time stamp of theLAST successful connection start in the formatyymmddhhmmss.

System actionThe BCPii connection is internally restarted. If therestart is successful, message ING812I is issued. If



the restart fails, message ING813E is issued withadditional information.



ModuleINGCHW0E

Classes40.

ING812I BCPII LINK BETWEEN CPCcpcaddr AND domain/operator RE-ESTABLISHED. NEW LASTS(stime)

ExplanationAfter a BCPii event session heartbeat failure, the BCPiiconnection has been successfully restarted.






• The variable operator is the operator task name ofthe event session for the affected BCPii connection.

• The variable stime is the Date/Time stamp of theLAST successful connection start in the formatyymmddhhmmss. The connection start initializes theLASTS value and is therefore prefixed with NEW.



System programmer response:For additional information, refer to the event handlerasynchronous response report “AOFA0998” on page553.

ModuleINGCHW0E

Classes40.

ING813E BCPII CONNECTION RECOVERYFROM domain/operator TO CPCcpcaddr FAILED. RSN(rsncode)LASTS(stime)

ExplanationAfter a BCPii event session heartbeat failure betweenthe targeted CPC and the operator task of the NetViewdomain, the internal BCPii connection restart failed.


BCPii local connection. System Automationtargets its own CPC.





• The variable rsncode is the reason code. For fulldetails, refer to the appendix section “InternalTransport Services "0Bx00xxx"” on page 566 of IBMZ System Automation Messages and Codes.


System actionThe BCPii connection to the addressed CPC is closed.

Operator responseSince the BCPii connections are monitored by SA z/OSor GDPS, a start of a failing connection is retried



automatically at each defined monitor cycle time. Nofurther action is required. If the heartbeat failuremessage ING811I was preceded by a ING814Emessage, additional error cause and reasoninformation is available.


ModuleINGCHW0E

Classes40.

ING814E BCPII CONNECTION TO domain/operator ABORTED BY THE CPCcpcaddr SUPPORT ELEMENT.CAUSE(cause_type)REASON(rsn_str) LASTS(stime)

ExplanationThe CPC Support Element has sent an'Application_Ended' event over an active BCPiiconnection to indicate the communication with theNetView domain/operator is about to end. Note thatthis event message is provided only for BCPiiconnections to z10 and newer processors.







• The variable cause_type is the action that caused theconsole application to end. Depending on the typegiven, a possible console application outage timecan be predicted.SHUTDOWN_CONSOLE

Long outage, manual intervention is required torecover.

RESTART_APPLICATIONMedium outage of 10 - 20 minutes can beexpected until the console application is fullyoperational.

RESTART_CONSOLEMedium outage of 10 - 20 minutes can beexpected until the console device and consoleapplication are fully operational again.

UNKNOWNThe type code in the event data is unknown. Longoutage, manual intervention may be required torecover.

• The variable rsn_str refers to the issuer that causedthe 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.• The variable stime refers to the Date/Time stamp of

the LAST successful connection start in the formatyymmddhhmmss.


Operator responseUse the cause_type information of the message todetermine the BCPii connection outage time that canbe expected. In case of a long outage time, considerthe SUSPEND command for the BCPii connection.


ModuleINGCHW0E

Classes40.

ING815I BCPII CONNECT FROM domain/operator TO CPC cpacaddrRETURNED: resp



ExplanationRequest to contact the CPC Support Element ofcpcaddr over the BCPii from domain/operator returneda response of resp.







• The variable resp is: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 554 in "ResponseMessages, Error Strings, Condition Codes" ofIBM Z System Automation Messages andCodes. Select the table that lists the reasoncode together with the error description.

System actionIf the connect was successful, session initializationcontinues with CPC configuration discovery. MessageING817I will be issued when this is complete. If theconnect processing failed, no further sessioninitialization is done and processing stops.

When a BCPii connection monitoring interval is definedto SA z/OS or GDPS HMC monitoring is used forcpcaddr, the connect requests will be retriedautomatically.



ModuleINGCHW0A

Classes40.

ING816I BCPII AWAIT CMD SESSIONTERMINATION TO CPC cpcaddr INdelay SECONDS: DOMAIN(domain)OPID(operator) CMD(cmd)LASTS(stime)

ExplanationThe HW event handler for CPC (cpcaddr) sessionreturned an error and the asynchronous sessionterminates. In order to perform a save memorycleanup, an ongoing HW command for the CPC runningin task (operator) needs to be terminated first. Wait for(delay) seconds for normal command termination.





• The variable cmd is the command token of thecurrently executed HW command.


• The variable delay is the time in seconds thecommand session is given to end.

• The variable operator is the operator task name ofthe command session using the affected BCPiiconnection.







ModuleINGCHW0M

Classes40.

ING817I BCPII DISCOVERY OF cpcaddr FORdomain/operator RETURNED: resp

ExplanationThe initial discovery request from domain/operator forconfiguration information of cpcaddr ended with aresponse of: resp







• The variable resp is:SUCCESS NEW LASTS(stime)

All required CPC configuration information hasbeen retrieved. The BCPii connection is now fullyoperational.stime

Date/Time stamp of the LAST successfulconnection start in the formatyymmddhhmmss. The connection startinitializes the LASTS value and is thereforeprefixed with NEW.

FFDC(ffdc_id)Failure to retrieve the required CPC configurationinformation. The BCPii session cannot be used.ffdc_id

The four character ID string represents theexit point from the discovery processing and

can be used by IBM to locate the failingretrieval.




ModuleINGCHW0A

Classes40.

ING818I BCPII LINK BETWEEN domain/operator AND CPC cpcaddr IS NOWTERMINATED. NEWSTATUS(connstat) OLDLASTS(stime)

ExplanationThe connection to the cpcaddr has been successfullyclosed from the domain/operator side. Beforeapplications can use the connection again, they mustrestart it. If the connection was closed, because of asession suspension, before restarting it, the sessionmust be resumed.


BCPii local connection, SA z/OS targets its ownCPC.





• The variable connstat is the new connection-sessionstatus:



NOT_CONNECTEDConnection-session can be restarted again.

SUSPENDEDConnection is suspended from normal usage. Itis required to resume it first, before restarting aBCPii session over this connection.

• The variable stime is the Date/Time stamp of theLAST successful connection start in the formatyymmddhhmmss. Since the connection is no longeractive the LASTS is prefixed with OLD.




ModuleINGCHW0C, INGCHW0D

Classes40.

ING819I BCPII ROUTE domain/operator -cpcaddr cstat LASTS(stime)

ExplanationThe BCPii connection monitor, configured for CPCcpcaddr has detected a connection status of cstat.Note that connection monitoring can be suppressed byspecifying an interval value of 'NONE' in the PDBprocessor entry for a CPC. Processors specified in theGEOPLEX definitions of GDPS are automaticallyexcluded from monitoring since GDPS provides theHMC Monitor to supervise BCPii connections.

For the eligible CPCs, the BCPii connection monitorstarts running after the SA z/OS agent initiallyactivates the configured BCPii connections. The sameapplies if changes in the processor definitions,affecting the current or new BCPii connections areactivated with an ACF REFRESH or ACF COLD atSA z/OS agent runtime.







• The variable cstat is:CONNECTED

The BCPii connection is established.NOT_CONNECTED

No BCPii connection is active.• The variable operator is the operator task name of

the event session for the monitored BCPiiconnection. If cstat is NOT_CONNECTED the LASTSfield value is a dot.

• The variable stime is the Date/Time stamp of theLAST successful connection Start in the formatyymmddhhmmss. If cstat is NOT_CONNECTED theLASTS field value is a dot.

System actionIf the connection status is NOT_CONNECTED, themonitor will try to start it. If the connection status isCONNECTED, no extra processing is done. In any case,the next monitor run is scheduled, using theconfigured monitor interval to set up a NetView timerfor this monitor run.

Operator responseWhen needed, the BCPii connection monitoring can bestopped by using the SA z/OS SETTIMER commanddialog. Look for the 'AOFRASCD HWOPER01INGRX830 1' cmd string and perform the delete actionof the associated TIMER-ID in the dialog.


ModuleINGRX830

Classes40.



ING820I BCPII SESSION MANAGEMENTFUNCTION LIMITATION IN FAVOROF APPLICATION appl_designatorWAS REQUESTED BY oper ONDOMAIN domain.

ExplanationCommand INGHWSRV BCPIIPRIO was issued to blockBCPii session restarts from interrupting importantapplication operation.

Message variables:appl_designator

Name of the favored application.oper

NetView operator or autotask, who issued thecommand.

domainNetView domain name.

System action:The BCPii session management function operationsare only limited.



Module:INGRX815

Classes40.

ING821I BCPII SESSION MANAGEMENTFUNCTION LIMITATIONRELEASED BY oper ON DOMAINdomain

ExplanationCommand INGHWSRV BCPIIPRIO was issued torestore normal SA-BCPII session managementoperation.

Message variables:oper

NetView operator or autotask, who issued thecommand.


System action:The BCPii session management function runs innormal mode.

Operator response:

None.


Module:INGRX815

Classes40.

ING822I BCPII SESSION MANAGEMENT TOPROCESSOR processor ISCURRENTLY LIMITED BYappl_designator ON domain.

ExplanationBCPii session re-cycle operation was blocked. Themanagement operation that terminates the session isnot executed. Command INGHWSRV can be used torestore normal operation mode for the session whichwas previously limited in favor of appl_designator.

Message variables:processor

Target processor of the blocked session. Forapplication GDPS, only processors defined in theGEOPLEX domain/options are affected.

appl_designatorName of the blocking application.


System action:The BCPii session management function continueswithout terminating the session.



Module:INGRX806, INGRVX80

Classes40.

ING823I THE CURRENT BCPII SESSIONMANAGEMENT PRIORITY IS SETTO appl_designator ON DOMAINdomain.

ExplanationDisplays the current BCPII session managementpriority setting of the domain. Command INGHWSRVBCPIIPRIO 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.



Module:INGRX815

Classes40.

ING824I requestor requests to connect toCPC cpc which is not in scope withthe local processor

ExplanationThe BCPii hardware interface tries to connect to theindicated processor hardware that is defined with adifferent connection scope.

• The requestor variable shows the originator of therequest.

• The cpc variable shows the address of the targetCPC.



System programmer response:Verify your automation policy definitions for theprocessor cpc. If connection to the CPC is required forthe application, make sure that SA policy for both localand remote processors contain equal ConnectionScope definitions. Otherwise, verify the applicationconnecting to the CPC and insure correct applicationconfiguration.

ING825I GDPS can now request control ofINTERNAL CPC connections

ExplanationThe connection to the CPC's local Support Element isoperational. GDPS can now request and later returnexclusive session control of all processors that have'INTERNAL' specified as their connection protocol inthe active SA policy. In case a processor has multiple

connection protocols specified, the exclusive sessioncontrol applies only to the 'INTERNAL' session.

Exclusive session control means that starting,stopping, and monitoring of the session is performedby GDPS. The connection test to the local CPC isalways tried by SA, independently from GDPS.However, monitoring and termination of the session tothe local CPC can be controlled by GDPS.

This message is issued only after an SOCNTL/ACF loadprocessing and processor definitions have beeninitially loaded or refreshed. Another condition for thismessage to occur is that the SA.GDPS tower has beenset in the active CNMSTYLE definitions.

System action:None.



Module:INGRX806

Classes:40

ING826I GDPS has control of the INTERNALconnection to CPC cpc_name(netid.nau)

ExplanationGDPS, which is configured on this SA agent instance,has indicated to take exclusive session control of theINTERNAL protocol connection to the named CPC. Thiscontrol includes the monitoring of the INTERNALconnection.

The cpc_name variable shows the Entry Name ofthe processor entry as defined in the processor infopolicy.The netid variable shows the Network Name of theprocessor entry as defined in the processor infopolicy.The nau variable shows the HW Resource Name ofthe processor entry as defined in the processor infopolicy.

System action:The SA connection monitoring, if configured in theprocessor policy, stops.



Module:



INGRX830

Classes:40

ING827I Automation has control of theINTERNAL connection to CPCcpc_name (netid.nau)

ExplanationSA now has session control of the named CPC, which isconfigured on this SA agent instance. INTERNALprotocol connection monitoring, if configured, is doneby SA.

The cpc_name variable shows the Entry Name ofthe processor entry as defined in the processor infopolicy.The netid variable shows the Network Name of theprocessor entry as defined in the processor infopolicy.The nau variable shows the HW Resource Name ofthe processor entry as defined in the processor infopolicy.

System action:The SA connection monitoring, if configured in theprocessor policy, starts.



Module:INGRX830

Classes:40

ING828I GDPS currently cannot use thelocal SE connection

ExplanationSA tried to establish an INTERNAL connection to thelocal Support Element (SE), but an error occurred. Alocal SE connection must be possible before remoteCPC connections are made. The used netid.nauaddress was not confirmed by the SE to be the localaddress due to the connection error.

This message is issued only after an SOCNTL/ACF loadprocessing and processor definitions have beeninitially loaded or refreshed. Another condition for thismessage to occur is that the SA.GDPS tower has beenset in the active CNMSTYLE definitions.

System actionIf the local SE connection remains under SA controland has a connection monitor interval configured, SAretries the local SE connection.

If GDPS requested and got control of the local SEconnection, its connection monitoring logic retries thelocal SE connection.


System programmer response:If the SA-BCPii messages in the netlog do not showwhich failing SE address is the local one, use theNetView QRYGLOBL command to display CglobalING.0HWSERIAL. The serial number value is the oneof your local CPC. Use an HMC where your CPC withthis serial number is defined. The CPC/SE networkdetails show the netid and nau address values of yourlocal SE.

Module:INGRX806

Classes:40

ING920I COMMAND cmd ISSUED BYjobname INHIBITS OTHERCOMMANDS/JOBS FROMEXECUTING

ExplanationSA z/OS found a command or job that inhibits at leastone other command from completing its execution.The policy defined during customization does notallow for abending the command.

The variable cmd shows the command name.The variable jobname shows the name of the job.



System programmer responseCheck the execution time of the command. If theexecution time is not reasonable, add the command tothe policy along with a reasonable execution time. Thisallows the cancelation of the job if necessary.

ModuleINGRX744



Classes40, 43.

propdYES

ING921I THE JOB jobname IS BEINGABENDED DUE TO A HUNGCOMMAND DETECTION ONRESOURCE resource

ExplanationSA z/OS detected a job that owns a resource thatinhibits commands from executing successfully. Thejob is abended with U2047 RSNC9D5C740 to avoidlockouts of other commands.

The variable resource shows the major and minorname of the resource.The variable jobname shows the name of the job.

System actionAutomation abends the indicated job.



ModuleINGRX744

Classes40, 43.

propdYES

ING922I DUE TO COMMAND FLOODDETECTION THE JOB job IN asidON system IS BEING ABENDED

ExplanationSA z/OS detected a job that is flooding the master orconsole address space with commands. To avoidlockouts of other commands the job is canceled and allof its commands are abended with U2047RSNC9D5C740.

The variable job shows the name of the job.The variable asid shows the address space IDrunning the job.The variable system shows the name of the systemrunning the job.

System actionSA z/OS cancels the indicated job and abends all itscommands in the command class where theautomation detected the command flooding.


System programmer responseDetermine the reason why the job was flooding themaster or console address space with commands.Make the necessary changes to prevent futureoccurrences of this situation before you restart the job.

ModuleINGRX746

Classes40, 43.

propdNO

ING923I LONG-RUNNING ENQAUTOMATION IS ACTIVE

ExplanationAutomation has started monitoring of long-runningENQs sysplexwide.




ModuleINGRX745



ClassesNone.

propdNO

ING924E AUTOMATION DETECTED THE JOBjob IN asid ON system FLOODINGTHE COMMAND CLASS cc

ExplanationSA z/OS detected a job that floods the indicatedcommand class. However, the policy defines the job asnon-cancelable. For this reason the automation leavesthe job and the commands that have been issued bythe job untouched.

The variable job shows the name of the job issuingthe command.The variable asid shows the address space IDrunning the job.The variable system shows the name of the systemrunning the job.The variable cc shows the name of the commandclass that is affected.

This message is issued approximately every 60seconds until there are no more commands waiting forexecution.


Operator responseObserve the command class to determine whether thejob still floods the class. If this is the case, cancel thejob because this is a serious situation that inhibitsother commands from being executed in the indicatedclass.

After you have canceled the job clean up the commandclass. Use the command CMDS SHOW to determinethe IDs of the commands that have been issued by theindicated job. Then use the command CMDS REMOVEto remove any commands that are waiting, and thecommand CMDS ABEND to terminate any commandsthat are executing.


ModuleINGRX746

Classes40, 43.

propdNO

ING925E CF cfname IS INNORMAL_OFFLINE STATE,UNABLE TO function

ExplanationSA z/OS is unable to enable or populate the couplingfacility. SA z/OS has issued V PATH(cfname,chp),ONLINE commands on all systems in the sysplex, butat least one system is unable to connect to thecoupling facility. This condition has persisted for 30seconds.

The variable cfname is the coupling facility name.The variable function is either ENABLE orPOPULATE.



System programmer responseEnsure that every system in the sysplex has at leastone channel path that is online to the coupling facility.

Classes40, 43.

propdYES

ING926I JOB jobname INHIBITS OTHERCOMMANDS FROM EXECUTING.RESOURCE=qname rname

ExplanationSA z/OS found a job that inhibits at least one othercommand from completing its execution. The policydefined during customization does not allow forterminating the task that holds the resource lock.

The variable jobname shows the name of the job.



The variable qname shows the major resourcename that is enqueued by the job and required bythe command.The variable rname shows the minor resourcename that is enqueued by the job and required bythe command.



System programmer responseCheck the execution time of the command. If theexecution time is not reasonable, add the command tothe policy along with a reasonable execution time. Thisallows the cancelation of the job if necessary.

ModuleINGRX744.

Classes40, 43.

propdYES

ING927E HSAPRGRS ENQ REQUEST FAILED.REQUEST request RETURN CODEreturn code REASON CODE reasoncode

ExplanationHSAPRGRS was called for ENQ processing but failed.This may be an ENQ/GRS issue or a programming errorin HSAPRGRS. For ENQ failures the requested resourcemay already be in use and not available or the GRSenvironment may not be valid.

The variable request shows the request type forHSAPRGRS/GQSCAN.The variable return code shows the return codefrom HSAPRGRS or the GQSCAN macro.The variable reason code shows the reason codefrom HSAPRGRS or the GQSCAN macro.

System actionProcessing is halted.


System programmer responseCheck the return codes listed below:

CodeMeaning

0Request successfully completed.

4CHNG

Status cannot be changed. Other tasks sharethe resource.

EXCL/SHR/TESTResource is not immediately available.

RELResource control requested but not yetassigned.

SCANNo resources matched the request.

8CHNG

Status cannot be changed. No ENQ has beenrequested.

EXCL/MOVE/SHR/TESTA previous request was made. The task alreadyhas control of the resource.

RELResource is already released or the task doesnot have control of the resource.

SCANThe area is too small.

For return codes 10 and 12 a reason code from macroGQSCAN is also returned (see z/OS MVS AssemblerReference).

10SCAN

GQSCAN failed. Check the reason code.12

SCANGQSCAN failed. Check the reason code.

20CHNG/EXCL/MOVE/SHR/TEST

A previous request was made. The task doesnot have control of the resource.

24EXCL/MOVE/SHR

ENQ limit reached.



32No storage available for GQSCAN.

36Resource not owned by the task with the TCBaddress.

-1IRXEXCOM error.

-2IRXEXCOM error.

n01nth parameter not specified.

n02Length of nth parameter is greater than 240.

n03nth parameter doesn't represent a stem variable.

n04Value of nth parameter is invalid.

n05Invalid parameter.

1nnnIRXEXCOM error 'nnn'.

Classes40, 43.

INGC1010I Exit exitname has been disabled.

ExplanationThe exit named in exitname has been disabled.exitname can have the values of XMEOUT for the CICSmessage exit, or XDTOUT for the Transient Data Queueexit.

This message will be issued if an existing policy hasenabled the specified exits and a refresh of the policyis in progress. The exits are disabled and thenoptionally re-enabled based on the new policy.

System actionProcessing continues and the specified exit is notinvoked to process messages.

Operator responseThis is not an error message. The product will functioncorrectly with one or both the exits disabled. However,this message should be followed by INGC1011I if theuser has specified a message exit policy according tothe IBM Z System Automation Product AutomationProgrammer’s Reference and Operator’s Guide manual.

INGC1011I Exit exitname has been enabled.

ExplanationThe exit named in exitname has been enabled.exitname can have the values of XMEOUT for the CICSmessage exit, or XDTOUT for the Transient Data Queueexit.

This message will be issued if a refresh of the policy isin progress. The exits are enabled if the user hasspecified policy information in the MESSAGES/USERDATA policy. The XMEOUT exit will be enabled for anymessage in the policy that starts with DFH and has anOFFSET= value specified in the USER DATA section.The XTDOUT exit will be enabled for any message thathas the OFFSET= and TDQUEUE= values specified inthe USER DATA section.

System actionProcessing continues and the specified exit will beinvoked to process messages.


INGC1012I No message policy definitionsfound. Exits will not be enabled.

ExplanationThere are no USER DATA policy definitions for theXMEOUT or XTDOUT exits and so the exits will not beenabled.

System actionProcessing continues and the exits will not be invokedto process messages.

Operator responseIf messages should be processed, check that theOFFSET= parameter has been specified in the USERDATA section of the message policy. Also check thatthe TDQUEUE= parameter is specified for TransientData Messages.

INGC1013I Processing function. CICS serviceService failed withEIBRCODE=code

ExplanationIn the process of refreshing the message exit policy inthe CICS subsystem, a CICS service has returned anunexpected return code.

The variable function can be one of:



XMEOUTPolicy was being processed for the XMEOUT exit.

XDTOUTPolicy was being processed for the XTDOUT exit.

BOTHPolicy was being processed for both the XMEOUTand 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 EXECCICS EXTRACT.

FREEMAINStorage was being released via EXEC CICSFREEMAIN.

GETMAINStorage was being obtained via EXEC CICSGETMAIN.

MSGBUILDA message was being built. EIBRCODE refers tothe code returned from this routine and not anEXEC CICS function.

The variable code is the EIBRCODE of the EXEC CICSfunction or the return code as specified above.

System actionProcessing is aborted and exits may or may not beenabled or disabled.

Operator responseFor MSGBUILD make sure that the INGAMCE moduleis in the DFHRPL concatenation. If it is and for all othercircumstances, report this error to service.

INGI1010I Automated Operator ExitInitialized for IMS ims Level level

ExplanationThe SA z/OS exit has been initialized and the IMScontrol region is running at the specified level.

The variable ims is the IMS subsystem id.The variable level is the Version ModificationRelease of the IMS.



INGI1011I No message policy definitionsfound. Exits will not be enabled forIMS ims.

ExplanationThere are no USER DATA policy definitions for the IMSsubsystem and so the exits will not be enabled.

The variable ims is the IMS subsystem id.

System actionProcessing continues and the exits will not be invokedto process messages.

Operator responseIf messages should be processed, check that theOFFSET= parameter has been specified in the USERDATA section of the message policy.

INGI1012I Exit DFSAOE00 has been disabledfor IMS ims.

ExplanationThe DFSAOE00 exit has been disabled.

This message will be issued if an existing policy hasenabled the specified exits and a refresh of the policyis in progress. The exits are disabled and thenoptionally re-enabled based on the new policy.


System actionProcessing continues and the specified exit is stillinvoked, however as no message policy is present, itwill not take any actions.

Operator responseThis is not an error message. The product will functioncorrectly with the exit disabled. However, this messageshould be followed by INGI1013I if you have specifiedmessage exit policy according to the IBM Z SystemAutomation Product Automation Programmer’sReference and Operator’s Guide manual.

INGI1013I Exit DFSAOE00 has been enabledfor IMS ims.

ExplanationThe DFSAOE00 exit has been enabled.



This message will be issued if a refresh of the policy isin progress. The exits are enabled if the user hasspecified policy information in the MESSAGES/USERDATA policy. The exit will be enabled for any messagein the policy that has the OFFSET= value specified inthe USER DATA section.


System actionProcessing continues and the specified exit will beinvoked to process messages.


INGLCR01E Dynamic allocation failed forDSN=file name.

ExplanationLife Cycle Recording (LCR) cannot allocate the data setspecified in file name.

System actionEither LCR cannot be enabled or the error occurredwhile offloading the data space to a data set (using theSAVE command).

Operator responseCheck that you have specified a correct data set namevia the command INGRXQRY LCR, or in HSAPRMxx orINGXINIT.


INGLCR02I Close life cycle recording.

ExplanationSA z/OS starts closing Life Cycle Recording (LCR) foreither the primary automation manager (PAM) or anautomation agent.

System actionThe data space is automatically offloaded to the dataset.



INGLCR03I Begin blocking access to LCR.

ExplanationWhen Life Cycle Recording (LCR) is about to close oroffload the data space, activities by other tasks areblocked until the data space has been written to disk.

System actionNone.



INGLCR04I End blocking access to LCR.

ExplanationThe Life Cycle Recording (LCR) close or offload processhas finished.

System actionNone.



INGLCR05E ABEND xxxx-rcrcrcrc occurred foroutput media media_type

ExplanationAn abend occurred during the I/O operation for a dataset or data space for Life Cycle Recording (LCR).

The variable xxxx is the system completion code.The variable rcrcrcrc is the corresponding reasoncode.

System actionLife Cycle Recording is disabled.



Operator responseCollect additional information about the reason for theabend, for example, the data set was too small. If youcannot fix the problem, report the error to your IBMSupport Center.


INGLCR06E Cannot open/write output media.

ExplanationLife Cycle Recording (LCR) cannot complete one of thefollowing:

• Opening a data set or a data space• Writing a record to the data space• Offloading the data space to data set

System actionLife Cycle Recording is disabled.

Operator responseLook for additional error messages, such asINGLCR05.


INGLCR07I Life cycle recording has beenenabled, NAME=dataset_name

ExplanationLife Cycle Recording (LCR) has been enabled with thedataset_name that will later be used as the offloaddata set.

System actionNone.



INGLCR08I Life cycle recording is currentlystatus, NAME=dataset_name

ExplanationStatus message indicating the current status of LifeCycle Recording (LCR), which is either enabled ordisabled.

System actionNone.



INGLCR09I Life cycle recording will bedisabled.

ExplanationAn abend occurred and Life Cycle Recording (LCR) isabout to be disabled.

System actionNone.



INGLCR10I Life cycle recording has beensuccessfully initialized,NAME=dataset_name

ExplanationLife Cycle Recording (LCR) has been initialized. A dataset was allocated and an initial record was written (anyold data is lost). The data space has been allocated.

System actionLife Cycle Recording is ready for the command toenable it.





INGLCR11I Successfully flushed records, totalsize #rec(KB)=size1(size2).

Explanationsize1 is the total number of checkpoint records everwritten by Life Cycle Recording (LCR) to the dataspace. This is an accumulated number and is not resetdue to possible wraparound.

size2 is the number of bytes actually allocated by thedata space. Later when the data space is saved to disk,size2 is written.

System actionNone.



INGLCR12I Switch output media for Life cyclerecording.

ExplanationLife Cycle Recording (LCR) has switched the outputmedia. The old data space is offloaded to the old dataset. A new, empty data space is allocated andinitialized with an initial record. A new data space iscreated.

System actionNone.



INGLCR13E Switching output media for lifecycle recording failed.

ExplanationLife Cycle Recording (LCR) cannot switch the outputmedia.

System actionNone.



INGLCR15E Creation of data space failed forDSP=file name

ExplanationLife 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 taskor the SA z/OS primary automation manager (PAM).

System actionLCR cannot be enabled.

Operator responseLook for additional error messages, such asINGLCR23E.


INGLCR21I Start offloading data space.

ExplanationLife Cycle Recording (LCR) starts offloading the dataspace to the data set.

System actionNone.



INGLCR22I End offloading data space.

ExplanationLife Cycle Recording (LCR) has finished offloading thedata space to the data set.



System actionNone.



INGLCR23E function failed, rc=rc frc=frcrsn=rsn

ExplanationLife Cycle Recording (LCR) detected an error whileprocessing the function function. Diagnosticinformation is provided as the return code (rc),function return code (frc), and reason code (rsn).

• The variable function shows the function thatproduced the error. It can be OPEN, CLOSE,OFFLOAD, or FLUSH.

• The variable rc shows the return code:32

REXX V-pool error40

Communication environment not available81

Initialization of lifecycle recording failed99

Invalid input arguments<100

Internal error by INGPXILC108

Internal. Invalid parameter list109

Internal. LCR control block has not beeninitialized

112Internal. Invalid function

116Dynamic allocation failed

120File open failed

121File put failed

122, 123Writing a control record failed while closing thefile

128Get record failed

132Function rejected because a server erroroccurred previously

136ESTAE cannot be established

140An abend occurred

144DSP Create failed

145DSP Delete failed

146DSP Put failed

147DSP Get failed

148DSN is missing

149Semicolon missing in INGRXQRY command

150Invalid size

>200ENQ failed

>300DEQ failed

>400NetView ALLOC error

489Invalid parameter list

• The variable frc shows the function return code. Thisis additional diagnostic information that is intendedfor the IBM Support Center.

• The variable rsn shows the reason code. This isadditional diagnostic information that is intended forthe IBM Support Center.

System actionLCR is disabled.

Operator responseCollect additional error messages, if available.


INGPC010I pgm is unable to perform functionservice, PPI_id=xxxxxxxx



ExplanationThe program pgm failed to perform the PPI functionservice with PPI using the PPI ID xxxxxxxx. Functioncould be:

• open DSIPHONE(OPENRECV)• close DSIPHONE(CLOSE)• send DSIPHONE(SEND)• AOF_PPI_SEND• receive DSIPHONE(RECEIVER)


Operator responseCheck if a correct PPI receiver ID was specified.Message INGPC011I might also be issued andprovides additional PPI and DSIPHONE errorinformation.

For AOF_PPI_SEND, a security error might haveoccurred. Search for message INGPC028I.


INGPC011I xxxxx, PPI Reason: yyyy

ExplanationThe message provides DSIPHONE error informationxxxxx and optional PPI error info yyyy. When sendingover secure PPI then xxxxx describes the error infoabout the SA secure PPI interface INGPAUTH insteadof DSIPHONE. It will be issued in addition toINGPC010I.

System actionNone.



INGPC012I The program pgm detectedmissing or invalid input forargument n

ExplanationThe program pgm failed because the input argument nis missing or invalid.



System programmer responseCheck input arguments.

INGPC015I cond condition trapped in scriptpgm Line: sigl Code: rc Description:desc

ExplanationThe program pgm failed due to a REXX script error.


Operator responseReport problem to your system programmer unless thecondition is triggered by the operator, such as a HALTcondition.


INGPC016I INGPCxxx service failed, RC=nn

ExplanationThe program INGPCxxx failed with return code nn.




INGPC017I pgm failed. Reason



ExplanationThe program pgm failed. Additional error info isprovided in Reason.



System programmer responseAnalyze the return code and/or additional errormessage. Resolve the problem and rerun thecommand.

INGPC018I pgm terminates with error, rc=nnn

ExplanationThe program pgm terminates due to an error. Returncode nnn is provided.



System programmer responseAnalyze the return code and/or additional errormessage. Resolve the problem and rerun thecommand.

INGPC019I pgm does not support host: HOSTASP

ExplanationThe program pgm does not support the REXX hostenvironment. HOST and ASP is extracted from REXX'parse source'.


Operator responseCheck why the program was called in the wrongenvironment.


INGPC020I pgm detected bad response:reason

ExplanationThe program pgm failed since an unexpected responsewas received. Reason describes the error.


Operator responseReport problem to your system programmer.


INGPC021I pgm is called with invalid namecpyname

ExplanationThe program pgm failed since the REXX program wascopied with an unsupported name or alias cpyname.



System programmer responseUse supported OPSxxxx names when copying ordefining an alias of pgm.

INGPC022I pgm is called as cpyname for aninvalid mode: mode

ExplanationThe program pgm failed since it was called ascommand but only function call is supported or viceversa. The invalid mode is either COMMAND orFUNCTION.




Operator responseInvoke the function only as the supported mode.


INGPC023I RACF® check failed: reason. Forinfo.

ExplanationOn TSO the emulator commands check the TSO user idagainst a profile. This message will be issued if accessis not granted or if an RACF error message occurred.reason might be one of the following:

• Access Allowed• Profile not Defined• User not Authorized• HSAPRRAC rc=nnn

Info is given in the following format, for example:UserID=BDOW Clist=INGRCCMX Class=FACILITYPROFILE=ING.EMULATOR.CMD

The high level qualifier ING was customized viacommand "INGCSA SET NAME=EMU.RACF.HLQVALUE=ING". The qualifier EMULATOR is a fixed stringand CMD depends on the calling clist being one of thefollowing:{CMD,VAL,SQL,DFLT}. If EMU.RACF.HLQ wasnot customized, RACF checking is ignored.

System actionThe calling program terminates.


System programmer responseGive the TSO user the correct RACF access rights orcorrect the RACF HLQ.

INGPC024I SA REXX function aborted due tono data specified on RETURN

ExplanationA System Automation REXX function running underTSO detected an error. A typical scenario might be:Due to the RACF checking of the TSO user id, anemulated function fails. Since a value must bereturned for this error, the emulator must force anIncorrect call to routine by returning nothing.This forces REXX error message IRX0045I on purpose.

The originating error is described in an additionalmessage, for example INGPC023I.

System actionThe REXX function exits.

Operator responseReport the problem to the system programmer.

System programmer responseAnalyze additional message accompanied withINGPC024I and fix the problem in the REXX userprogram.

INGPC025I Incorrect call to name

ExplanationThe named program was called directly rather thanfrom a REXX script.



INGPC026I error information

ExplanationAn error occurred as reported by the previously issuedmessage for example, INGPC017I. This message givesadditional information.



System programmer responseIf necessary, report the problem to your IBM SupportCenter.

INGPC027I command. Parameter parmmissing or invalid value

ExplanationThe specified parameter is either wrong or missing.



The variable command is the name of the commandbeing processed.The variable parm is the parameter that is invalid ormissing.The variable value is the value of the parameterthat is wrong. The variable is only present whenapplicable.

System actionNone.


INGPC028I Security check for TSO user faileddue to errtext.

ExplanationA TSO program tries to send a command viaINGRCRPC to the System Automation/NetView Agenton a secure channel. Message INGPC028I will beissued if the SAF front-end security checking failed.

If the TSO user runs the batch API, the TSO user IDmust have READ access to the following SAF front-endprofile:

• TSO.plexname.system.CMDRCVR.SEND

If the TSO user calls INGRCRPC, the TSO user ID musthave READ access to one or both of the followingprofiles:

• TSO.plexname.system.CMDRCVR.SEND• TSO.plexname.system.CMDRCVR.SEND.USERTASK

Table 8. Error Text for INGPC028I

errtext Description

HSAPRRAC error Internal API returns anerror.

invalid parameter Internal API detects aninvalid input argument.

invalid class The class SYSAUTO is notauthorized.

user not authorized TSO userid is notauthorized to access theprofile.

resource not protected The profile is not defined.

System actionRequest was not sent to the System Automation/NetView agent.


System programmer responseSearch for additional security messages, such asICH408I.

Check if the profile was correctly defined and the TSOuser ID has READ access. If an internal API erroroccurred, switch on trace and rerun the command.

INGPC029I Parameter xxxx is not supportedby emulator for yyyy.

ExplanationThe emulated command or function for yyyy wascalled on TSO but the parameter xxxx is not supportedby the SA z/OS emulator.

System actionThe program continues.


System programmer responseModify the script invoking the emulator.

INGV0001I Library aa.bb is not APFauthorized.

ExplanationThe indicated library is not APF authorized.

The variable aa identifies the high-level qualifier ofthe library as found in the configuration file.The variable bb identifies the type of the library.

The verification ends with warnings.

System actionNone.


System programmer responseCorrect the panel descriptions.

INGV0002I LPA Module aa not found.



ExplanationThe indicated module is required to be stored in theLPA. However, the verification routine could not locatethe module in the LPA.

The variable aa identifies the name of the module.


System actionNone.


System programmer responseEnsure the content of the library ending with SINGLPAis loaded into the LPA.

INGV0003I Library aa.bb not in LNKLST.

ExplanationThe indicated library is not found in the currentLNKLST concatenation.

The variable aa identifies the high-level qualifier ofthe library as found in the configuration file.The variable bb identifies the type of library.


System actionNone.


System programmer responseAdd the indicated library to the current LNKLST.

INGV0004I Library aa.bb preceded by cc.

ExplanationThe indicated library has been found in the currentLNKLST set. However, the verification routine alsodetected that another library of the same typeprecedes the library.

The variable aa identifies the high-level qualifier ofthe library as found in the configuration file.The variable bb identifies the type of library.

The variable cc shows the data set name of thelibrary that precedes this library.


System actionNone.


System programmer responseMove the entry to the top of the current LNKLST set.

INGV0005I Improper PPT entry found for aa,RSN=bb

ExplanationThe verification routine either did not find theindicated module in the program property table (PPT)or the corresponding PPT entry shows an improper ormissing attribute.

• The variable aa shows the name of the module.• The variable bb shows one or more reasons:

80NOCANCEL not specified.

40KEY(8) not specified.

20NOSWAP not specified.


System actionNone.


System programmer responseCorrect the PPT entry of the indicated moduledepending on the reason code.

INGV0006I Log stream aa not defined.

ExplanationThe verification routine could not connect to theindicated log stream because it is not defined to thecurrent LOGR policy.



The variable aa shows the name of the log stream.


System actionNone.


System programmer responseDefine the indicated log stream to the current LOGRpolicy.

INGV0007I System logger still active.

ExplanationThe verification routine found the System Loggeraddress space active. However, the configuration fileindicates the configuration for a GDPS KSYS system.This type of system does not allow an active SystemLogger.


System actionNone.


System programmer responseStop the System Logger address space.

INGV0008I REXX package aa not found.

ExplanationThe verification routine could not locate the indicatedREXX function package in the LPA or the LNKLSTconcatenation.

The variable aa shows the name of the functionpackage.


System actionThe verification step is skipped.


System programmer responseAdd the indicated REXX function package either to theLPA or to the LNKLST.

INGV0009I REXX function package aa notfound in bb.

ExplanationThe verification routine could not find the requiredREXX function package in the indicated module.

The variable aa shows the name of the SA functionpackage.The variable bb shows the name of the REXXfunction package.


System actionNone.


System programmer responseEdit the source member of the module and add therequired REXX function package to the module. Re-assemble and re-link the module and add it to the LPAor to the LNKLST.

INGV0010I Version mismatch found, aa - bb.

ExplanationThe verification routine detected a version mismatchbetween two ISPF dialog members, ISPF tableAOFTOPOL and panel AOFG#NL1.

The variable aa shows the version of the ISPF table.The variable bb shows the version of the ISPFpanel.


System actionNone.


System programmer responseVerify that the ISPF installation libraries are set upcorrectly.



INGV0011I Major node aa not found.

ExplanationThe verification routine detected that the NetViewmajor node has not been defined to VTAM.

The variable aa shows the NetView major nodename.


System actionNone.


System programmer responseAdd the major node definition to VTAM and activate it.

INGV0012I Applid aa not found in bb.

ExplanationThe verification routine detected that the NetViewapplid has not been defined in the indicated VTAMmajor node.

The variable aa shows the NetView applid.The variable bb shows the NetView major nodename.


System actionNone.


System programmer responseCorrect the VTAM major node definition and activate it.

INGV9000I Verification step "aa" notexecuted.

ExplanationThe verification could not switch into a mode and keythat is required to perform the indicated verificationstep.

The variable aa shows the description of the step.

System actionThe step is not performed.


System programmer responseEnsure that the library containing the verification isAPF authorized. Then, repeat the verification.

INGV9001I Parse error occurred, Text<aa>Pos=bb, RC=cc.

ExplanationThe verification parses the configuration file created bythe wizard. The parser found an error condition.

The variable aa shows the text around the error.The variable bb shows the position in error relativeto the beginning of the text.The variable cc shows the return code returned bythe parser.

System actionVerification is terminated.


System programmer responseContact the IBM support center.

INGV9002I Keyword aa not found.

ExplanationThe indicated keyword could not be found in theconfiguration file. Or, the keyword is found but has novalue.

The variable aa shows the name of the keyword.






INGV9003I Macro aa failed, RC=bb, RSN=cc.

ExplanationThe indicated macro failed.

The variable aa shows the name of the macro.The variable bb shows the return code of themacro.The variable cc shows the reason code of themacro.




INGV9004I Configuration file error.

ExplanationThe verification routine requires the configuration filecreated by the wizard. Either the ddname INGCFG wasnot specified or the record format of the file isUNDEFined or a read error occurred.



System programmer responseCorrect the error condition and re-run the verification.

INGV9005I aa authority missing, CLASS=bb,RESOURCE=cc.

ExplanationThe verification routine requires the indicatedauthorization when the Security Authorization Facility(SAF) is available.

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.



System programmer responseGrant the required authorization to the verificationroutine and re-run the verification.

INGV9006I Member aa(bb) not allocated,RC=cc, RSN=dd.

ExplanationThe verification routine failed to allocate the indicatedmember.

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 theDYNALLOC macro.The variable dd shows the reason code of theDYNALLOC macro.

System actionVerification step is terminated.


System programmer responseEnsure that the data set is available on the currentsystem and re-run the verification.

INGV9007I Member aa(bb) could not beopened, RC=cc.

ExplanationThe verification routine failed to open the indicatedmember.

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 OPENfunction.






INGV9008I Release information not found inmember aa(bb).

ExplanationThe verification routine could not find the releaseinformation in the indicated member.

The variable aa shows the name of the data set.The variable bb shows the name of the member.




INGV9009I System Logger not active.

ExplanationThe verification routine did not find the System Loggeraddress space active. This inhibits the routine fromverifying the definitions of the automation-specific logstreams.



System programmer responseStart the System Logger address and re-run theverification.

INGX1001E PLX STACK OVERFLOW: modulecompile_date info

ExplanationSA z/OS detected an internal error due to a PLX stackoverflow.

The variable module shows the name of the modulethat detected the stack overflow.The variable compile_date shows the date that themodule was compiled.The variable info gives additional information aboutthe overflow.

System actionNone. The function terminates with abend 3999.


System programmer responseCheck the syslog for the associated messages anddump information, and contact your IBM SupportCenter.

INGX1002I SHORT ON XCF BUFFERS - RETRY

ExplanationThe SA z/OS communication framework cannot senddata segments due to the condition "Short On XCFBuffers". SA z/OS will try to resend the data segmentafter a timeout delay. If this is not successful a timeouterror message ING008I is issued.

System actionNone.


System programmer responseCheck the syslog for the associated messageHSAM1050E that contains further debugginginformation. If the problem persists considerincreasing the number of XCF buffers. The maximumXCF buffer size for SA z/OS is 4028.

INGX1011I INBOUND DIAGNOSTICS: DIF=nnABS=nn QUE=n EXP=n SEC=nnCPU=nnn OUT=nn RSP=nn FAF=nn

ExplanationThis message is issued by the automation managerwork item queue monitoring routine when it detectsthat more work items are arriving than can beprocessed by the automation manager within themonitoring interval.



DIFThe number of incoming work items that have notyet been processed during the monitoring interval.It is the number of work items in the queue at thecurrent monitoring time minus the number of workitems in the queue at the last monitoring. If thenumber is positive and grows it is an indicationthat the automation manager is being put understress.

ABSThe total number of work items in the input andoutput queues. This value includes the number ofwork items that have been processed but that havenot been through the cleanup process. Thenumber is typically higher than the QUE number. Ifthe number differs greatly from the QUE value, itmight be an indication that the automationmanager is unable to deliver command responsesto the automation agents. A value that is slightlyhigher than QUE is acceptable.

QUEThe current size of the work item queue.

EXPThe number of work items in the input queue thathave already expired. Expired work items are notprocessed by the automation manager but causean ING008 timeout message.

SECThe monitoring interval. It is customizable andruns from 10 to 999 seconds.

CPUThe total accumulated CPU time used by theautomation manager

OUTThe number of outbound orders that are waiting tobe sent to the agent or agents.

RSPThe query work items in the input queue.

FAFThe number of work items in the input queue thatdo not require a response. Typically, these arestatus updates.




INGX9601I System Automation WebServicesAdapter jobname failed: reason

Explanation:The WebServices Adapter caught an exception. Thereason describes the kind of exception.

System action:The HTTP request has been aborted. However,processing of the WebServices Adapter continues.


System programmer response:Check the reason and try to resolve the problem. Ifnecessary, contact your IBM Support Center.

INGX9602I System Automation WebServicesAdapter jobname accepts HTTPrequests via remote_contact.

Explanation:The WebServices Adapter is ready to accept HTTPrequests via the IP address and port as specified inremote_contact.




INGX9603I System Automation WebServicesAdapter jobname initializationcomplete for automation domainname.

Explanation:The WebServices Adapter is ready to work automationdomain name.




INGX9604I System Automation WebServicesAdapter jobname internal errorerror_code, reason.

ExplanationThe WebServices Adapter suffers an internal error thatis not expected to be caused by any input URL or inputparameter.

The internal error_code and the reason is additionaldebug information for IBM support.



System action:The WebServices Adapter continues running orterminates depending on the error scenario.


System programmer response:Contact your IBM Support Center.

INGX9605I System Automation WebServicesAdapter jobname does not acceptreason.

Explanation:The URL associated with the HTTP request is notaccepted due to the specified reason. In most casesthe URL has an invalid format or unsupportedparameters.

System action:The HTTP request is rejected. The WebServicesAdapter continues running.



INGX9632I System Automation E2E agentjobname terminates: reason

ExplanationThe E2E agent detects an error most likely during theinitialization of its USS process.

The variable reason provides diagnostic informationabout the error that occurred.

System action:E2E agent terminates.


System programmer responseDetermine why the E2E agent failed and correct theproblem. Examine the syslog and netlog for additionalinformation. If the reason is the failing commandINGRE2E, look for message ING377I in the netlog andcheck the return code.

Make sure that you always use the code page IBM1047 for the E2E agent configuration file. If not, theinput check might fail and this message might show anunpredictable character string as a result.

INGX9633I System Automation E2E Agentjobname initialization complete

Explanation:

The E2E agent initialization is completed and is readyto accept connections from remote automationdomains.




INGX9634I System Automation E2E agentjobname user ID or password isnot correctly specified or thecredential file cannot be loadedfrom path.

ExplanationThe E2E agent initialization tries to load the fileinge2eagt.credentials.properties, whichcontains the user ID and password that are needed toconnect to the remote automation domains. The filecannot be loaded or it does not contain a user ID andpassword pair for each domain that was loaded by theE2E agent.

The variable jobname shows the name of the job.The variable path shows the path of the credentialfile.

System action:Processing terminates.


System programmer response:Create a credential fileinge2eagt.credentials.properties and copy itinto the configuration directory of the E2E agent. Eachdomain that is defined in the policy needs to haveeither a specific or a generic credential statement. Foreach specified user ID, you must also specify apassword. For a remote z/OS domain, the user ID mustbe a valid SAF user ID. See also the parameterINGAGT_CRED_CFG in the configuration fileinge2eagt.properties.

INGX9635I System Automation E2E agentjobname rejects a join event fromhostname host of the unknownautomation domain: dom.

ExplanationThe E2E agent has received a join event from a remoteautomation domain that is not known. There is nocorresponding DMN object defined in the currentlyloaded SA automation policy. Therefore, theconnection to the E2E agent is rejected.



The variable jobname shows the name of the E2Eagent's job.The variable host shows the TCP/IP hostname or IPaddress of the remote automation domain.The variable dom shows the name of the remoteautomation domain.

System action:The processing continues.


System programmer response:Check whether the unknown automation domain hasbeen defined in the SA automation policy and correctthe problem.

INGX9636I System Automation E2E agentjobname connection failed todom(hostname) with exception:exception_text

ExplanationThe E2E agent cannot establish a TCP/IP connection toa remote automation domain.

The variable jobname shows the name of the E2Eagent's job. o The variable dom shows the name ofthe remote automation domain.The variable hostname shows the TCP/IP hostnameor IP address of the remote automation domain.The variable exception_text shows the text of theexception.



System programmer response:Check the text of the exception. Possible reasons forTCP/IP connection errors might be an SSL handshakeproblem or a firewall problem.

INGX9701I ingadapter.sh [-](start|stop|GenerateSampleKeys|IBMSupport|traceON|traceOFF)[suffix]

ExplanationDescribes the syntax of the automation adapter start/stop command. It is also shown if there are invalidarguments or no arguments specified.

System actionNone.

Operator responseSpecify command syntax as described.

INGX9702I Script ingadapter.sh completedsuccessfully.

ExplanationThe end-to-end automation adapter start script endedsuccessfully.

System actionNone.


INGX9703E Script ingadapter.sh completedunsuccessfully.

ExplanationAn error occurred during script execution.

System actionScript execution is interrupted.

Operator responseCheck previous error messages for more details.

INGX9704I Preparing the environment to startthe automation adapter usingcustom root directory xxx.

ExplanationThe script ingadapter.sh performs a validation and acleanup step before starting the automation adapter.The script determines whether an automation adapteron the same port is already running, or if there are anyopen connections left by a failed automation adaptershutdown. In the former case the script aborts and inthe latter case the connections are dropped. Moreover,any existing pid-file of a failed automation adaptershutdown is deleted.

xxx specifies the USS path of the currently used E2Eadapter custom root directory.

System actionNone.



Operator responseIf the automation adapter cannot be started or theconnections cannot be dropped, check whether theuser ID that was used to run the automation adapterhas the correct access rights. For details see thechapter "Operating the End-to-End AutomationAdapter" in IBM Z System Automation End-to-EndAutomation.

INGX9705E Cannot start automation adapterwith the same configuration:hostname:port

ExplanationThe automation adapter cannot be started twice withthe same port number and hostname as specified inthe automation adapter master configuration file. Thisis determined by examining an existing pid-file whosefilename is constructed from the hostname and portnumber. The containing process-id is used todetermine whether another automation adapter isrunning or if the pid-file has been left over by a failedautomation adapter shutdown. If the correspondingautomation adapter USS process does not exist thendelete the pid file and restart the automation adapter.The pid file resides in the automation adapter datadirectory with extension '.pid'.


Operator responseStart the automation adapter with a differentconfiguration.

INGX9706I Trying to drop possible open,unused connections. Processingport: port_number

ExplanationThe script tries to close possible open and unusedconnections that have been left by a failed automationadapter shutdown. These connections are detectedwith the netstat command. The connection will bedropped using the command netstat -d conid, ifspecific access rights have been granted.

System actionConnections are dropped.

Operator responseIf the ingadapter.sh script cannot drop connectionscheck whether the user ID that was used to run theautomation adapter has the correct access rights. Fordetails see the chapter "Operating the End-to-EndAutomation Adapter" in IBM Z System Automation End-to-End Automation.

INGX9707I Status of the process: process isrunning.

ExplanationThe process is already running.

The process can be one of the following:

• automation adapter• E2E agent

.

System actionNone.


INGX9708I Status of the automation adapter:adapter is not running.

ExplanationInformation about the status of the automationadapter.

System actionNone.


INGX9709E Rights to access process list havenot been granted. Changepermissions.

ExplanationThe necessary rights to show all processes have notbeen granted to the current user. The script cannotcorrectly determine the automation adapter status.




Operator responseChange access rights to show all processes. For moreinformation, see Chapter 9. Customizing USS andTCP/IP in E2E Automation.

INGX9710I Could not retrieve installedcodepage. Trying with defaultcodepage:

ExplanationThe script was not able to determine the installedcodepage because environment variable CODEPAGEhas not been set correctly. It attempts to use thedefault codepage.

System actionThe system uses the default codepage.

Operator responseSet the environment variable CODEPAGE in theconfiguration fileing.adapter.plugin.properties to the desiredcodepage.

INGX9711E The automation adapterconfiguration file is missing.

ExplanationThe automation adapter master configuration file,ing.adapter{suffix}.properties, was not found. Thesuffix is optional and can be specified as the secondargument of ingadapter.sh.


Operator responseIf you use a suffix make sure you have specified it asthe second argument for ingadapter.sh. Theautomation adapter master configuration file isexpected to be located in the configuration directory.Also check the customization section of the scriptingadapter.sh. Check manual for correspondinginformation.

INGX9712I Generating Sample Keys for testpurposes.

ExplanationThe script generates sample keystore and truststorefiles for SSL. These keys are for testing purpose only.

System actionNone.


INGX9713E Keytool was not found. Pleaseinstall a java-sdk and customizeingadapter.sh accordingly.

ExplanationThe automation adapter script, ingadapter.sh,attempted to use the keytool from the Java SDK butthe tool was not found. The keytool is used to generatesample keys for SSL.

System actionCannot create sample keys.

Operator responseInstall a Java SDK and adapt the path to the keytoolusing the variable JAVA_KEYTOOL in thecustomization section of the script ingadapter.sh.

INGX9714I Trace was set to: level.

ExplanationThe script has successfully set the specified level. levelis either OFF or DEBUG_MAX.

System actionNone.


INGX9715E An error occurred while trying toset log level.

ExplanationThe script failed in at least one case to set thespecified log level. Use the counterpart of thecommand to reset the logger to its previous state.Ignore failures that are reported by the script in thisundo step. Those commands that succeeded the firsttime will succeed in the undo step and those that didnot will not succeed the second time.

System actionNone.



Operator responseUndo changes by invoking the opposite tracecommand: for example, traceOFF if traceON hasfailed.

INGX9717I Cannot write file or directory:uss_path

ExplanationThe script failed because it has no write access to thespecified file or directory or the file or directory doesnot exist at all.

System actionThe script terminates.


System programmer responseCheck if you have properly set up the configuration fileingadapter.properties for the E2E adapter oringe2eagt.properties for the E2E agent. Youmight have to set the variable E2E_CUSTOM_ROOT to apath that is not read only. If this variable is not set,then the default path is the path that is specified inE2E_INSTALL_ROOT. The configuration file is used inthe STDENV DD of the corresponding startupprocedure of the JCL.

INGX9718I Cannot create file or directory:uss_path

ExplanationThe script failed because it cannot create the specifiedfile or directory by using the mkdir command .

System actionThe script terminates.


System programmer responseCheck if you have properly set up the configuration fileingadapter.properties for the E2E adapter oringe2eagt.properties for the E2E agent. Youmight have to set the variable E2E_CUSTOM_ROOT to apath that is not read only. If this variable is not set,then the default path is the path that is specified in

E2E_INSTALL_ROOT. The configuration file is used inthe STDENV DD of the corresponding startupprocedure of the JCL.

INGX9719I Shell script command 'cmd' result

ExplanationThe script cannot run the specified command cmdsuccessfully or the specified command returns anunexpected value.

The cmd variable shows the command specified in thescript.

The result variable shows one of the following values:

• Failed• Returns unexpected value xxx

System action:The script terminates if the specified command failed.Otherwise, the script continues running.


System programmer responseIf the command is 'hostname -p stackname', thencheck that the stackname is valid and check that thehostname from the default TCP/IP stack is differentfrom the hostname of the separate TCP/IP stack.

The command hostname is used to determine theTCP/IP hostname automatically. If you specify thecorrect IP address or hostname directly in theparameter eez-remote-contact-hostname in theconfiguration file ing.adapter.properties, youcan avoid executing the command hostname.

INGX9730I Starting Automation Agent JavaPlugin Adapter Script:start_parameters

ExplanationThe USS script of the System Automation Agent JavaAdapter starts. The start parameters are a list of name-value pairs which might be useful for diagnosticpurposes.






INGX9731I Finished Automation Agent JavaAdapter Script: RC=retcode

ExplanationThe USS script of the System Automation Agent JavaAdapter has been terminated. The final return code isprovided in retcode.

System actionProcessing finished.


System programmer responseIf the retcode is not zero, look for additional messagesand analyze the reason for the problem.

0Success.

1Java environment setup failed for example due toimproper parameter values ininge2eagt.properties.

2USS script failed.

>2Java mainline failed, see also messageINGX9877I.

INGX9732I Cannot create logger outputdirectory: logdir

ExplanationThe USS script of the System Automation Agent JavaAdapter cannot create the logger output directory asspecified by logdir.



System programmer responseCheck that the USS script has correct write accesspermissions.

INGX9733I Bad Java version foundVersion,required is requiredVersion.

ExplanationThe USS script compares the required minimum Javaversion with the actual version found by java version.

The foundVersion variable has the value 'or java notinstalled' if Java is not installed at all. Otherwise, itshows the installed Java version that is notsupported.The requiredVersion variable shows the requiredminimum Java version.



System programmer responseInstall and set up at least the required Java version.

INGX9800E Cannot find message file ormessage ID file_or_msgid

ExplanationThe message file cannot be loaded or the message IDcannot be found in the message file.

The variable file_or_msgid shows the name of theassociated message file or ID.

System actionNone.

Operator responseCheck the class path.


INGX9801E INGXLogger cannot setupcom.ibm.log.PDLogger

ExplanationInitialization of the message and trace log servicefailed.



System actionThe message or trace data cannot be written to the logfile.

Operator responseCheck the classpath or the logger configuration file,eezjlog.properties.


INGX9802I INGXLogger has successfully beeninitialized using configuration fileconfig_file from path path.

ExplanationInitialization of the message and trace log service wassuccessful. The logger configuration data were readfrom the specified configuration file.

The variable config_file shows the name of theconfiguration file that the logger configuration datawas read from.The variable path shows the path of theconfiguration file.

System actionMessage and trace data will be written to the log file.



INGX9803E INGXLogger is not available :message

ExplanationAn attempt was made to write a message to the loggerbut the logger was not initialized.

The variable message shows the message thatcould not be written to the logger.

System actionThe message is written to the stderr.txt file.



INGX9810I Timeout after interval seconds.

ExplanationA connection from the JVM to the SA z/OScommunication manager (INGPXDST) timed out.

The variable interval shows the duration of thetimeout.

System actionThe response from the associated request is notreceived.

Operator responseIncrease the timeout.


INGX9820E JNI function function failed withreturn code return_code.

ExplanationA function call to the specified JNI DLL failed.

• The variable function shows the function call thatfailed.

• The variable return_code shows the return code thatspecifies the reason for the failure:10

Internal—invalid field ID (attribute not availablein Java class)

20Internal—handle cannot be saved in Java longsince long too small

21Internal—handle is invalid, for example, nullpointer

22Handle cannot be created since no memory

23Internal—handle iterator already used (numberof slots too small)

25The ASCB address is no longer correct. Recyclethe End-to-end automation adapter.



26Internal—invalid array size (Java array size iszero or too small)

27Internal—invalid object (null pointer or anunexpected class)

30Internal—invalid parameter (unexpected inputargument)

31Invalid buffer length (input data buffer hasunexpected length)

32A Java class that was accessed via JNI hasthrown an exception

33Creation of a new Java array failed

34Creation of a new Java string failed

35Out of memory

36A Java class cannot be found

40Catastrophic error—an unexpected exceptionoccurred

1000PPI receive timeout

11nnPPI subsystem not available

12nnPPI initialization of receiver queue failed

13nnThe PPI receiver queue exists already

14nnPPI NetView posted PPI ECB due to subsystemerror

15nnPPI cannot receive data

16nnPPI cannot delete receiver queue

17nnPPI cannot send data

where nn denotes the PPI-specific return code asdescribed in the NetView Application Programmer'sGuide, for example:04

The PPI receiver is not active. For example, theSA z/OS agent is not available or is not properlycustomized.

24The PPI is not active.

25The ASCB address is no longer correct. Recyclethe automation adapter.

26The receiver program is not defined, for example,PPI=YES has not been added to INGXINIT.

28An active subsystem interface address spacewas found, but an active PPI address space wasnot found.

32No NetView storage is available.

35The receiver buffer queue is full.

System actionThe corresponding request failed.

Operator responseAnalyze the return code. If necessary, contact yoursystem programmer.

System programmer responseAnalyze the return code. For example:

• RC=1300 indicates that another SA Java process isrunning on the system and uses the same PPIreceiver ID. Verify with D OMVS,A=nnnn whetherthere is another SA Java process running, wherennnn is the ASID of the PPI receiver ID that youobtained with the NetView DISPPI command.

For example, PPI receiver ID INGEVE2E is used bythe automation adapter and INGJVMxx is used bythe End-to-End agent.

• RC=1726 indicates that there might be a mismatchof the XCF group ID in the configuration file for theautomation adapter or End-to-End agent. Verifywhether it matches the XCF group ID that wasdefined in INGXINIT for the automation agent andHSAPRMxx for the automation manager.Alternatively, the statement PPI=YES might bemissing in the INGXINIT member.

The configuration fileing.adapter.plugin.properties defines theXCF group ID for the automation adapter. Theconfiguration file inge2eagt.properties definesthe XCF group ID for the End-to-End agent. Thisvalue might be overwritten by the start procedure



itself or by the start parameters of the correspondingAPL entry in the automation policy.

INGX9821E Object of class class has alreadybeen destroyed.

ExplanationInternal error.




INGX9822E Environment error. Check handlefailed with return codereturn_code.

ExplanationInternal error.




INGX9823E Class class cannot load DLL dll.

ExplanationThe JNI DLL cannot be loaded from the specified Javaclass.

System actionAll communication services will fail.

Operator responseCheck the libpath.


INGX9830E INGXStream failed reading fromthe data stream. Attempted toread expected bytes and got actualbytes.

ExplanationThe data stream decoder expected to read expectednumber of bytes but got only actual bytes.

System actionThe corresponding request fails.

Operator responseCheck why connection was broken.


INGX9831E INGXStream failed reading fromthe data stream. Foundunexpected end-of-data.

ExplanationThe data stream decoder did not find the end-of-datamarker. Data might be corrupted. The connectionmight have broken or there is an internal data streamerror.


Operator responseCheck why connection was broken.


INGX9833E INGXStream failed due to invalidheader.

ExplanationThe data stream decoder found an invalid header inthe data stream.






INGX9840E Execution of a remote REXXcommand handler aborted.

ExplanationThe corresponding request cannot be executed withinthe SA z/OS NetView backend.


Operator responseAnalyze the NetView log for more SA z/OS messages orREXX syntax errors, or both.


INGX9850E FileIO function function failed,rc=rc reclen=rl fname=dsnfmode=mode

ExplanationAn I/O error occurred while accessing a z/OS data setfrom a Java program. For example, opening or readingthe SMF report.

The variable function is the name of the functionthat detected the IO error.The variable rc is the return code from the I/Oservice routine libingjrio.so.The variable rl is the local record length used toaccess the data set.The variable dsn is the name of the data set.The variable mode is the file mode used to accessthe data set.


Operator responsePerform problem determination and correct theproblem.

INGX9854E At least one input parameter ismissing.

ExplanationThis is a generic message that is issued when at leastone input parameter was not specified or its value isnull.


Operator responsePerform problem determination, for example, checkthe input data, and correct the problem.

INGX9855E function has been stopped due to afailure, rc=rc

ExplanationAn error occurred and the specified functionterminates.

• The variable function is the name of the function thatterminates due to an error.

• The variable rc is the return code:16

The logger object cannot be instantiated.32

Processing failed due to an exception.40

Exception occurred during cleanup.


Operator responsePerform problem determination, analyze associatedexceptions and correct the problem.

INGX9856E Illegal syntax or format, data

ExplanationThis is a generic message that is issued when aconversion error occurred in a Java program. Forexample, the data and time string from an SMF reportare converted to an integrated timestamp of a specificformat.

The variable data is diagnostic data that mightdescribe the reason for the problem in more detail.




Operator responsePerform problem determination, for example, checkthe input data, and correct the problem or contact yourIBM Support Center.

INGX9860I function starting to feed theSA z/OS SMF report into DB2table.

ExplanationThe program is being started. It reads the SMF report,converts it to EEZ format and puts it into the DB2table. This message is written to syslog.

The variable function is the name of the functionthat issued the message.

System actionNone.


INGX9861I function is going to connect toDB2.

ExplanationThe program tries to connect to the remote or localDB2 via JDBC driver.


System actionNone.


INGX9862I function is going to open the SMFreport dsn

ExplanationThe program tries to open the SMF report. The SMFreport must have been generated before this programruns.


The variable dsn is the name of the data set thatcontains the SMF report to be processed.

System actionNone.


INGX9863I function is going to feed DB2 withthe SMF report.

ExplanationThe program attempts to read the SMF report, andconverts each record from the SMF report to a row inthe corresponding EEZ tables in DB2.


System actionNone.


INGX9864I function fed num eventssuccessfully into the DB2 tablewithin time seconds.

ExplanationThe program has successfully put the specifiednumber of events from the SMF report into the DB2table.

The variable function is the name of the functionthat issued the message.The variable num is the number of recordsconverted.The variable time is the number of seconds takenby the program to feed DB2 with the SMF records.

System actionNone.


INGX9865I Contents of EEZFeeder propertiesfile: config_parms



ExplanationThe input data from STDENV is converted to aninternal properties file for the eezfeeder.jar.

The variable config_parms is the list ofconfiguration parameters that is passed toeezfeeder.jar.

System actionNone.


INGX9866I function completed successfully.

ExplanationThe program has successfully put the SMF report intothe EEZ tables in DB2.


System actionNone.


INGX9870I System Automation Agent JavaPlugin 'nickname' failed: 'reason'

ExplanationThe Automation Agent Java Framework invoked aplugin with name nickname. The plugin failed and areason is provided which describes the error.

System actionThe Java plugin cannot execute the request.Processing of the Automation Agent Java Adaptercontinues.


System programmer responseUsually, the reason starts with a message ID. Look forthat message description in this case. Otherwisereason describes the error. Analyze the log file of theassociated Automation Agent Java Adapter. Search for

further error messages which may provide moredetails about the reason of the error.

INGX9871I System Automation Agent RPCfrom Java Plugin to Netviewfailed:'reason'

ExplanationThe Automation Agent Java Framework attempted tocall a NetView command but the attempt failed. Thereason of the failure is described in the reason text.

System actionThe Java plugin cannot execute a command on thelocal System Automation NetView Agent. Processing ofthe Automation Agent Java Adapter continues.


System programmer responseThe reason starts with a message ID. Look for thatmessage description. Analyze the log file of theassociated Automation Agent Java Adapter space.Search for further error messages which may providemore details about the reason of the error.

INGX9872I System Automation Agent JavaPlugin with nickname 'nickname'not found.

ExplanationThe Automation Agent Java Framework tries to invokea plugin with name 'nickname'. However a plugin withmatching 'nickname' cannot be found.

System actionNone.


System programmer responseLook in the NetView log and search for correlated errormessages in order to find the System Automationcommand that tried to call the Java plugin. Check ifthis command requires a Java plugin installation.

INGX9873I System Automation Java Pluginsare not available or not initialized



ExplanationDuring the startup of the Automation Agent JavaAdapter, it will be checked that at least one plugin isavailable and successfully initialized. If this is not thecase, this message is issued and the address spacestops.

System actionAddress space stops.


System programmer responseSearch for additional messages that explain the reasonwhy the plugin cannot be initialized. For examplebecause the plugin class cannot be found in classpath.

INGX9874I System Automation Agent JavaAdapter 'subsjob' is active.

ExplanationMessage used for automation of the Automation AgentJava Adapter via System Automation policy.

System actionNone.



INGX9875I System Automation Agent JavaAdapter 'subsjob' is ready.


System actionNone.



INGX9876I System Automation Agent JavaAdapter 'subsjob' has beenstopped.


System actionNone.



INGX9877I System Automation Agent JavaAdapter 'jobname' has beenstopped due to failure, rc=returncode

ExplanationThe Automation Agent Java Adapter terminatesabnormally. You may exploit this message for use bydefining a System Automation policy for setting theAutomation Agent Java Adapter in the statusABENDED.

• The variable jobname is the name of thecorresponding job.

• The variable return code can be:0

Success4

Abend posted by plugin8

Abend mainline

System actionAutomation Agent Java Adapter terminates.





INGX9879I System Automation Agent JavaPlugin with nickname 'nickname'cannot be invoked: errortext.

ExplanationThe Automation Agent Java Framework tries to invokea plugin with name 'nickname'. However a plugin withmatching nickname cannot be invoked because anerror occurred. The errortext described the reason ofthe error.

System actionNone.


System programmer responseTry to fix the problem if errortext gives you anindication. If necessary, contact IBM support Center.

INGX9880I System Automation Java Plugin'nickname' cannot be loaded

ExplanationThe Automation Agent Java Framework tries to reloadthe Java class representing the plugin with name'nickname'. However the class cannot be found.

System actionNone.


System programmer responseAdapt the classpath in the script ingjava accordingly.

INGX9881I System Automation Java Plugin'nickname' terminates adapter dueto: 'description'

ExplanationThe plugin encountered a problem that requires theadapter to terminate. The 'description' describes thereason given by the plugin.

System actionAdapter terminates.


System programmer responseTry to solve the problem described by 'description'.

INGX9882I System Automation Agent Adapterjobname terminates unexpectedlydue to reason

ExplanationThe Automation Agent Java Adapter terminatesabnormally due to an unhandled exception that iscaught by the mainline.

The jobname variable is the name of thecorresponding job.The reason variable provides diagnostic informationabout the abnormal termination.

System actionThe Automation Agent Java Adapter terminates.


System programmer responseCheck the reason that this message provides and try tofind the cause of the problem.

Analyze the log file of the associated AutomationAgent Java Adapter. Search for further error messagesthat might provide more details about the cause of theerror.

INGX9901E INGXPluginLogger cannotinitializecom.ibm.log.EEZLoggerJLog.

ExplanationAn attempt to create a logger for the SA z/OS plug-incomponent was unsuccessful.

System actionNo message or trace data is written to the loggeroutput destination.




INGX9902I INGXPluginLogger hassuccessfully been initialized usingconfiguration file file from pathpath.

ExplanationThe message and trace data of the SA z/OS plug-in willbe written to the logger output destination.

System actionNone.


INGX9904E Adapter plug-in initialization wasunsuccessful.

ExplanationThe initialization of the SA z/OS plug-in was notsuccessful.

System actionStart up of plug-in is stopped.

Operator responseInstallation or customization was erroneous, forexample, the logger or the plug-in configuration file.Also check whether the automation adaptercustomization for NetView is correct.

INGX9905E Adapter function function failed:exception text

ExplanationThe specified adapter plug-in function wasunsuccessful. An exception was caught from anunderlying component.

System actionNone.

Operator responseRead the original exception and follow its explanation.

INGX9906E Error message from SA z/OS:SA z/OS message

ExplanationExecution of a command using SA z/OS wasunsuccessful. This message presents the extractederror message.

System actionNone.

Operator responseFor details about the extracted error message see IBMZ System Automation Messages and Codes or IBM ZNetView Messages and Codes.

INGX9910I The command cmd will beperformed for resource res onbehalf of user usr with comment:cmt

ExplanationA user has issued a command that relates to aresource. This command has been received by theadapter and will be performed by automation on theindicated resource.

The variable cmd shows the end-to-end commandthat was issued against the adapter.The variable res shows the name of the SA z/OSresources.The variable usr shows the end-to-end operatorname that issued the command.The variable cmt shows the comment that wasentered by the operator.

System actionThe command has been received and will be executedfor the resource.


INGX9911I The command cmd will beperformed for system sys onbehalf of user usr

ExplanationA user has issued a command that relates to a system.This command has been received by the adapter andwill be performed by automation on the specifiedsystem.

The variable cmd shows the end-to-end commandthat was issued against the adapter.



The variable sys shows the name of the system thatis involved with the command.The variable usr shows the end-to-end operatorname that issued the command.

System actionThe command has been received and will be executed.


INGX9912I The command to move resourcegroup grp away from system syswill be performed on behalf ofuser usr with comment: cmt

ExplanationA user has issued a request to move a resource groupaway from specified system. This command has beenreceived by the adapter and will be performed byautomation.

The variable grp shows the name of the group thatis involved with the command.The variable sys shows the name of the system thatis involved with the command.The variable usr shows the end-to-end operatorname that issued the command.The variable cmt shows the comment that wasentered by the operator.



INGX9913I The command to move resourcegroup grp to the home system willbe performed on behalf of user usrwith comment: cmt


The variable grp shows the name of the group thatis involved with the command.The variable usr shows the end-to-end operatorname that issued the command.

The variable cmt shows the comment that wasentered by the operator.



INGX9914I The command to move resourcegroup grp to system sys will beperformed on behalf of user usrwith comment: cmt


The variable grp shows the name of the group thatis involved with the command.The variable sys shows the name of the system thatis involved with the command.The variable usr shows the end-to-end operatorname that issued the command.The variable cmt shows the comment that wasentered by the operator.



INGX9915I Command reset from non-recoverable error will beperformed on resource res onbehalf of user usr

ExplanationA user found a non-recoverable resource, whichmeans the resource is not automated until a userissues the reset command. The reset command hasbeen received by the adapter and will be performed byautomation on the indicated resource.

The variable res shows the name of the SA z/OSresources.The variable usr shows the end-to-end operatorname that issued the command.



System actionThe command has been received and will be executedfor the resource.


INGY1000I service FAILED IN MODULEmodule, RC=return_code,REASON=reasoncode error_info

ExplanationAn unexpected return code was retrieved from theservice call mentioned in the message.

The variable service shows the name of the servicethat failed.The variable module shows the name of the modulewhere the error occurred.The variable return_code shows the value of thereturn code that was issued.The variable reason error_info shows the value ofthe reason code that was returned and indicatesthe cause of the error.

Use Table 9 on page 395 to determine the cause of theerror:

Table 9. Return and Reason Codes of INGY1000I

Service

ReturnCode

ReasonCode

Explanation

INGPYENC

8 1 Incorrect parameter passed tothe encoding routine.

INGPYENC

8 2 The generated instructionstream is on a higher level thanallowed.

INGPYDEC

8 1 CRC value mismatch detected.

INGPYDEC

8 2 Incorrect table identifier foundin the instruction stream.

INGPYDEC

8 3 Incorrect agent role/commandcombination found in theinstruction stream.

INGPYDEC

8 4 Bad work item received: totallength of work item is less than0.

INGPXRPC

0 20 REXX variable pool problem.

Table 9. Return and Reason Codes of INGY1000I(continued)

Service

ReturnCode

ReasonCode

Explanation

INGPYRCV

INGPXRPCINGPYRCV

0 24 A severe error occurred. See thenetlog for further details.

INGPXRPCINGPYRCV

0 28 The sysplex communicationmanger is not available.

INGPXRPCINGPYRCV

0 2C An abend occurred.

INGPOPPI

any any See the appropriate NetViewmanual where the service callthat is mentioned in themessage is described.


User responseFor module names prefixed with INGPX, see alsoAppendix E, “Sysplex Communication Services Returnand Reason Codes,” on page 579.

Examine the return and reason codes from the servicecall and contact your system programmer.

INGY1001I SEVERE ERROR DETECTED INMODULE module, REASON=reason

ExplanationAn internal error has occurred.

• The variable module shows the name of the modulewhere the error occurred.

• The variable reason shows the value of the reasoncode that was returned and indicates the cause ofthe error. It can have the following values:



1An incorrect function code was specified forinvoking the instruction builder.

2An incorrect request code was specified forinvoking the instruction builder.

3The data contained in the passed data stem doesnot fit in the work buffer.

4Incorrect parameters detected when theautomation manager interface routine wascalled. The number of specified parametersexceeds the maximum number allowed.

System actionThe request is canceled. A return code is sent to theprogram that issued the request.

User responseExamine the reason code for the possible cause of theerror and contact your system programmer.

INGY1002I NOT ENOUGH STORAGE TOHANDLE COMMAND/REQUEST

ExplanationA GETMAIN failure occurred.

System actionThe command or process in progress when the erroroccurred terminates.

User responseNone.

INGY1003E ABNORMAL TERMINATIONabend_code,REASON=abend_reason,MODULE=module,FOOTPRINT=footprint

ExplanationA system service or instruction has failed.

The variable abend_code shows the value of theabend code.The variable abend_reason shows the value of theabend reason.The variable module shows the name of the modulewhere the error occurred.

The variable footprint shows the information aboutthe caller of the routine.

System actionThe command or process in progress when the erroroccurred is terminated.

User responseNone.

INGY1004I AUTOMATION MANAGER CALLFAILED. RC=returncode,REASON=reason

ExplanationAn error occurred while communicating with theautomation manager.

• The variable returncode shows the value of thereturn code that was issued. It can have thefollowing values:4

The request was processed. However, theautomation manager found minor problems withthe work item composed for the request.

8An instruction that is part of the work item is inerror. The reason code provides more detailsabout the cause of the error.

12There is a severe problem with the work item. Itdid not pass the instruction interpretation phasein the automation manager.

• The variable reason shows the value of the reasoncode that was issued. The reason code is for internaldiagnosis only.

Reason

Meaning

10E0 The configuration data set does not containan entry for the system that the automationmanager is running on.

See Appendix D, “Automation Manager ReasonCodes,” on page 575 for details.

System actionThe instance terminates.

User responseExamine the netlog for additional messages with moredetails about the cause of the error. In case that return



codes 8 or 12 were issued report the error to your IBMSupport Center if necessary.

INGY1005I TOO MANY PARAMETERSSPECIFIED FOR FUNCTIONfunction

ExplanationToo many parameters are specified for the function.

The variable function shows the name of thefunction that failed.

System actionThe command or process in progress when the erroroccurred is terminated.

User responseCheck whether WebSphere MQ is set up properly as az/OS subsystem. See WebSphere MQ for z/OS SystemAdministration Guide for further information. Alsocheck whether your specifications in SA z/OS arecorrect. See HSAPRMxx for information about theautomation manager part and INGXINIT forinformation about the SA z/OS NetView agent.

INGY1006I NO COMMUNICATION PATHAVAILABLE TO destination

ExplanationThe communication with the designated automationmanager could not be established.

The variable destination shows the name of theautomation manager that the command was routedto.

System actionNone.

User responseWait until the designated automation managerbecomes available and reissue the command.

Verify that an automation manager was started. Makesure that the GRPID specifications in memberHSAPRMxx and the corresponding DSIPARM memberINGXINIT are identical.

INGY1010E LICENSE MANAGER CALL serviceFAILED, RC=return_code,STATUS=status_code

ExplanationWhen SA z/OS was initializing, a license check for thisinstance of SA z/OS was performed. An error occurredand a correct license certificate could not be found. Acombination of return code and status code can beused to determine the cause of the error.

The variable service shows the name of the servicethat failed.The variable return_code shows the value of thereturn code that was issued.The variable status_code shows the value of thestatus code that was returned.

System actionThe SA z/OS initialization stops and SA z/OSterminates.

System programmer responseMake sure that a valid license certificate for SA z/OSexists in the IBM License Manager database. If a validlicense certificate exists and the error persists, contactyour IBM Support Center.

User responseNotify your system programmer.

INGY1011I No License obtained for currentSA z/OS version

ExplanationWhen SA z/OS was initializing, a license check forVersion 2 of SA z/OS was performed. A valid licensecertificate for Version 2 could not be found, or the IBMLicense Manager reported an error condition.

System actionThe SA z/OS initialization stops and SA z/OSterminates.

System programmer responseMake sure that a valid license certificate for SA z/OSexists in the IBM License Manager database. If a validlicense certificate exists and the error persists, contactyour IBM Support Center.


INGY1012I Component component is notsupported



ExplanationWhen the indicated component was initializing, acapability check was performed. The capabilitymodule does not allow use of the component.

The variable component shows the name of thecomponent.

System actionThe initialization stops and the component terminates.


System programmer responseIn case an improper capability module is being usedby the indicated component, replace the module by acapability module that supports the component.

INGY1013I Module module not found

ExplanationWhen the indicated component was initializing, acapability check was performed. However, thecapability module could not be located in the LPA, theSTEPLIB concatenation, or the LNKLST concatenation.

The variable module shows the name of thecapability module.

System actionThe initialization stops and the component terminates.


System programmer responseAdd the required capability module to either locationLPA, STEPLIB, or LNKLST and restart the component.

INGY1015E CONVERSION ERROR DETECTED.SEE INGDUMP DATA SET FORDETAILS

ExplanationRoutine INGPYDEC has detected a conversion errorwhile decoding the buffer received from theautomation manager. The buffer contains data that theINGPYDEC routine does not understand.

The INGPYDEC routine provides debugginginformation in the INGDUMP data set.

System actionSA z/OS continues ignoring the data that cannot beconverted.

System programmer responseContact your IBM Support Center and provide theinformation in the INGDUMP data set.


INGY1020I Parameter value is not a validparameter

ExplanationThe specified parameter is invalid.

The variable value shows the value of theparameter. The value is invalid.The variable parameter shows the name of theparameter.

System actionNone.

Operator responseCorrect the invalid parameter value.


INGY1021I Required Parameter parametermissing.

ExplanationThe named parameter is not specified.

The variable parameter shows the name of theparameter that is missing.

System actionNone.

Operator responseSpecify the missing parameter.




INGY1022I REXX module name - Invalidsyntax

ExplanationAn SA z/OS REXX function detected a syntax error inits invocation. This error can result from extraoperands being specified or expected operands thatare missing.

The variable name is the name of the REXX routinethat contains the error.

System actionThe REXX function ends.

Operator responseNotify your system programmer that there are errors inthe named REXX module.

System programmer responseCorrect the statement in the REXX module.

INGY1023I REXX module name - Unknownvariable name var_name

ExplanationAn SA z/OS REXX function detected a syntax error inits invocation. The specified variable name was notrecognized.

The variable name is the name of the REXX routinethat contains the error.The variable var_name is the name of the variablethat is unknown.




INGY1024I REXX module name - Erroroccurred. Reason=reason

ExplanationAn SA z/OS REXX function detected an error duringprocessing.

• The variable name is the name of the REXX routinethat contains the error.

• The variable reason indicates the cause of the error.It can have the following value:1

Retrieval of the NetView common global that isassociated with the variable failed.

2SA z/OS is not fully initialized.


Operator responseExamine the reason code for the possible cause of theerror and contact your system programmer ifnecessary.

System programmer responseFor reason code 2, examine the NetView log foradditional messages that explain why accessing thecommon global failed.

INGY1025I REXX module name - Unknownsubsystem/job name res_name

ExplanationAn SA z/OS REXX function detected a syntax error inits invocation. The specified subsystem name or its jobname is not defined to SA z/OS.

The variable name is the name of the REXX routinethat contains the error.The variable res_name is the name of the resource.It can be a subsystem name or its associated jobname.




INGY1026I Invalid Parameter value,Reason=reason



ExplanationAn SA z/OS routine attempted to access the SA z/OScapability file but specified an invalid parameter.

The variable value specifies the parameter in error.The variable reason specifies why the parameterwas rejected.



System programmer responseContact IBM Service.

INGY1090I Program name is not APFauthorized

ExplanationThe SA z/OS discovery engine was invoked but themodule named in the message does not reside in anAPF authorized library. The discovery engine must beauthorized in order to pickup sensitive data such asprogram name or program parameters from thevarious address spaces.

The variable name holds the name of the program.

System actionThe discovery engine terminates.

System programmer responsePlace the named module into an authorized library.

INGY1097I Job jobname - STCname - Userended. RC=rc

ExplanationThis message indicates that a started task (STC) thatwas initiated by SA z/OS has ended. The return codeinforms SA z/OS of the result and acts accordingly.Additional messages may be issued to the netlog.

• The variable jobname indicates the job name thatthis STC was assigned.

• The variable STCname indicates the STC that wasinvoked.

• The variable User indicates the user that this job wasrun under.

• The variable rc indicates the return code returned bythe job:0

Okay1

There was a parameter mismatch3

A timeout occurred10nn

nn is the return code from the STC

System actionNone.



INGY1100I AN SA AUTOMATION MANAGERTAKEOVER HAS BEEN REQUESTED

ExplanationThe SA z/OS automation manager found anWebSphere MQaccess problem. A takeover to anotherautomation manager instance was forced. MessageINGY1103I shows the reason for the takeover.

System actionAn SA z/OS automation manager takeover is triggered.However, if the automation manager runs on the lastsystem within the XCF group the takeover request isignored. Instead, a switch from WebSphere MQ to XCFcommunication will be performed.

User responseNone.

INGY1101I FAILED MQ FUNCTION WILL BERETRIED

ExplanationA WebSphere MQ access problem has been detected,the failed function will be retried. See messageINGY1103I for further information about theWebSphere MQ problem.



System actionThe failed SA z/OS function is retried.

System programmer responseExamine preceding message INGY1103 or INGY1104to understand the WebSphere MQ specific reason forthe failure.

User responseNone.

INGY1102I AUTOMATION STATE QUEUE ISCORRUPTED, PROCESSINGCONTINUES

ExplanationA problem with the StateQueue has been detected.The SA z/OS automation manager now frees theStateQueue access. The queue is marked as GET/PUTdisabled.

System actionThe SA z/OS automation manager tries to continue itswork without the StateQueue. However, severeproblems may result in a takeover when the failedUOW ends. If the SA z/OS manager can continue, it willmonitor the queue and try to reconnect when thequeue is GET/PUT enabled again.

User responseAnalyze the queue problem described in messageINGY1103I. Redefine the StateQueue and mark it asGET/PUT enabled.

INGY1103I MQ FUNCTION function FAILED.REASON = MQreason'

ExplanationA WebSphere MQ function failed.

The variable function shows the function that failed.The variable reason shows the reason code thatindicates the cause of the error. See WebSphere MQfor z/OS Application Programming Reference for adescription of the reason code.

System actionDepending on the severity and the SA z/OS instancehaving that problem it can be one of the following:

• The WebSphere MQ function may be retried.• A manager takeover might be triggered.

• The SA z/OS instance terminates.

User responseWhen the instance terminates, analyze the WebSphereMQ problem and restart the failed instance.

INGY1104I SEVERE MQ LINKAGE PROBLEM.REASON = reason

ExplanationThis message indicates that WebSphere MQ is not setup correctly.

The variable reason shows the reason code thatindicates the cause of the error.


User responseSee WebSphere MQ for z/OS System AdministrationGuide for further information. If you cannot resolve theproblem contact your IBM Support Center.

INGY1105I MQ SUBSYSTEM mqssid NOTDEFINED OR INVALID.

ExplanationThis message indicates that WebSphere MQ is not setup correctly.

The variable mqssid shows which WebSphere MQdefinition is missing or invalid.


User responseRefer to WebSphere MQ for z/OS System AdministrationGuide (SC34-6585-00) for further information. If youcannot resolve the problem contact your IBM SupportCenter.

INGY1106I INVALID MAXMSGLSPECIFICATION FOUND FOR THEqueue, SPECIFIED VALUE =yourValue, REQUIRED VALUE =requiredValue. PROCESSINGCONTINUES



ExplanationSA z/OS found inconsistent definitions in the queue.This can happen when samples that are provided withSA z/OS are used that do not reflect the latestWebSphere MQ versions.

The variable queue shows the name of the queuethat contains incorrect definitions.The variable yourValue shows the value that is notcorrect.The variable requiredValue shows the value thatshould be specified.

System actionThe instance continues processing, but the overallprocessing performance might be impacted when therequired value is less than the one you specified.

User responseCorrect the length and rerun the queue definition jobswhen applicable.

INGY1107I PROBLEM DETECTED WITH THEAUTOMATION STATE QUEUE.QUEUE REMOVED FROMPROCESSING

ExplanationThis message is issued after INGY1102, when themanager was able to complete processing. However,the State Queue remains corrupted and is nowremoved.

System actionThe automation manager frees the State Queue fromall accesses. After that you are able to redefine thequeue.

User responseAnalyze the reason for the corruption and redefine thequeue.

INGY1108I AUTOMATION STATE QUEUEINSERTED AGAIN

ExplanationThis message is related to message INGY1107. Itcontains notification that the manager tried toreinstate the queue again. This will happen when themanager detects that the queues are marked GET/PUTenabled again.

System actionThe manager tries to reinstate the State Queue again.

User responseNone.

INGY1109I RECOVERY FOR THE queue HASBEEN STARTED. ACTIONCODE =action

ExplanationThe manager detected a Queue Full condition anddecided to recover from that situation.

The variable queue shows the name of the queuethat is full.The variable action shows the recovery action thatis taken.

System actionThe automation manager automatically tries to resolvequeue full situations. The following action codes canoccur:1

Query requests from the work item queue aredeleted without any processing.

2The manager stops the update process to avoid anoverflow of the agent queue.

3All agents are asked to enter a slowdown mode.That means only important requests are sent tothe manager.

4Is a combination of actions 1 and 3.

5The agent queue will be determined and 'zombie'messages are deleted. 'Zombie' messages areorders and responses and agents that are currentlynot active.

6Is a combination of actions 1 and 5.

User responseNone.

INGY1111I WAITING FOR MQ QUEUEMANAGER mqssid TO COME UP



ExplanationEither the automation manager or one of it's agents iswaiting for the WebSphere MQ manager to come up.As long as is not running as an WebSphere MQapplication, the automation manager cannot berestarted without possible loss of data.

The variable mqssid shows the subsystem ID of theWebSphere MQ Manager that SA z/OS tries toconnect to.


User responseNone.

INGY1112I WAITING FOR MQ PEER/LOCALRECOVERY TO COMPLETE

ExplanationTakeover is waiting for WebSphere MQ peer/localrecovery to complete.

System actionTakeover processing will actively poll WebSphere MQto recognize when the WebSphere MQ peer recoveryhas been completed.

User responseNone.

INGY1113I SEVERE MQ QUEUE RECOVERYPROBLEM, CANNOT CONTINUE

ExplanationDuring a takeover SA z/OS detected a severeWebSphere MQ related processing problem.

System actionThe takeover cannot be completed HOT, and will bereset to WARM. However, processing continues.

User responseAnalyze the reason of this problem using WebSphereMQ diagnostic means.

INGY1114I FOUND DEFECT WORKITEMS,CANNOT CONTINUE

ExplanationDuring a takeover SA z/OS detected that anautomation manager request in the work item queuehas been rolled back twice. It looks like a HOTtakeover would again result in a termination.

System actionThe takeover cannot be completed HOT, and will bereset to WARM. However, processing continues.

User responseAnalyze the reason of the repeated termination of themanager.

INGY1120I Starting modname

ExplanationThis message is written to indicate that the programhas started.

The variable modname is the name of the modulebeing started.

System actionNone.

User responseNone.

ModuleINGPUSMF

classNone.

INGY1121I Ending modname

ExplanationThis message is written to indicate that the programhas ended.

The variable modname is the name of the modulethat has ended.

System actionNone.

User responseNone.



ModuleINGPUSMF

classNone.

INGY1122I Unable to open the filename file.RC=retcode

ExplanationSA z/OS attempted to open the named file. The OPENservice failed.

The variable filename is the ddname of the data set.The variable retcode is the return code from theOPEN call that failed.

System actionThe INGPUSMF utility program ends.

User responseExamine the return code from the service call.

ModuleINGPUSMF

classNone.

INGY1123I filename has unexpected recordlength of nnn

ExplanationWhile opening the named file, the utility programdetected that the record length does not match theexpected length of 80.

The variable filename is the ddname of the data set.The variable nnn is the record length.

System actionThe file that is in error is ignored and considered to benot present.

User responseAllocate the data set with the correct record length.

ModuleINGPUSMF

classNone.

INGY1124I Specified user parameters

ExplanationThis message documents the options that theINGPUSMF utility program works with.

System actionNone.

User responseNone.

ModuleINGPUSMF

classNone.

INGY1125I Invalid parameter detected: option

ExplanationThe INGPUSMF utility program encountered an invalidparameter option.

The variable option identifies the option that isinvalid.

System actionThe option that is in error is ignored.

User responseNone.

ModuleINGPUSMF

classNone.

INGY1126I All SMF records will be selectedfor processing



ExplanationThis message indicates that no filtering option wasspecified when invoking the INGPUSMF utilityprogram. Filter options are SYSID, FROM, and TO.

System actionNone.

User responseNone.

ModuleINGPUSMF

classNone.

INGY1127I nnnnn records {read in |processed}

ExplanationThis message records the number of records eitherread or processed.

The variable nnnnn is the number of records eitherread in or processed.

System actionNone.

User responseNone.

ModuleINGPUSMF

classNone.

INGY1130I debug_text

ExplanationThis is a generic informational message that showsdebug information.




INGY1131I PPI Receiver name is active.TASK=taskname

ExplanationThe task identified by its name has been activated.




INGY1132I PPI Receiver name hasterminated. TASK=taskname

ExplanationThe task identified by its name has been terminated.




INGY1133E Command command to receiverfailed with RC=retcode -description

ExplanationThe SA z/OS USS process exit routine or itscorresponding receiver attempted to execute aNetView PPI command that has failed.

The variable command indicates in the CNMNETVfunction that failed.The variable receiver is the name of the PPI receiverthat experienced the error.



The variable retcode is the return code from theCNMNETV call.The variable description gives an explanation of theerror.

For detailed error information, see IBM Z NetViewProgramming: Assembler. In case of NetView Program-to-Program Interface (PPI) errors see IBM Z NetViewApplication Programmer’s Guide for more informationrelated to the service return code rc.


Operator responseReport the error condition to your system programmer.

System programmer responseReport the problem to the SA z/OS service team forfurther diagnosis.

INGY1201E Unable to load NetView modulemodule-name

ExplanationThe TWS command exit module supplied by SA z/OSwas unable to load the named module for execution.

System actionThe command exit module supplied by SA z/OSreturns a code of 4 to TWS. This forces the operationinto an error state with error code 'OAUT'. Processingcontinues.

Operator responseDetermine why the exit could not load the module.Ensure that the NetView load libraries are in either thelink list or the STEPLIB concatenation for the TWSController address space.

System programmer responseIf the module name is CNMNETV, ensure that theNETVIEW.CNMLINK data set is either in the systemlink list or in the STEPLIB concatenation for the TWSController address space.

INGY1202E PPI Command command-name toreceiver-id failed with error-text

ExplanationThe TWS command exit module supplied by SA z/OSattempted to execute a NetView PPI command thathas failed.

command-name has the following values:

CommandName

Meaning

QUERYPPI PPI request 1, Query if PPI servicesare available

QUERYRCV PPI request 2, Query the receiver IDstatus

SEND PPI request 14, Send a buffer to areceiver ID

receiver-id is the name of the PPI receiver thatexperienced the error. This can be ignored for theQUERYPPI command.

error-text gives an explanation of the error, as follows:

Text Meaning

Receiver isDisabled

RC=4. The receiver is not active.

The receiver ID is defined but notactive, so PPI has accepted a copyof the data buffer and queued it tothe receiver ID queue.

PPI is Available RC=10. The PPI is available toprocess requests.

This is the result of a QUERYPPIcommand.

Receiver isActive

RC=14. The PPI receiver IDspecified is active.

This is the result of a QUERYRCVcommand.

Receiver isInactive

RC=15. The PPI receiver IDspecified is inactive.


Receiveralready Active

RC=16. The PPI receiver IDspecified is already active.

Receiver ECBnot zero

RC=18. The ECB specified in therequest is not zero.

This occurs if the program does notclear the ECB before executing aRECEIVE command.

Request codenot defined

RC=20. The request code is notdefined.



Text Meaning

Not in PrimaryMode

RC=22. The program that issued thisrequest is not running in PRIMARYmode.

PPI uses z/OS Cross-Memoryservices so the program must berunning in PRIMARY mode for it tobe successful.

Not Authorized RC=23. The program that issued thisrequest is not authorized.

If the receiver ID has been definedto accept buffers only fromauthorized programs, this erroroccurs if the sender program is notauthorized.

PPI is notAvailable

RC=24. The PPI is not available.

This is the result of a QUERYPPIcommand.

ASCB ID isInvalid

RC=25. The ASCB address is notcorrect.

In a RECEIVE command, the ASCBaddress is specified. If this does notmatch the address specified in theOPEN command this error occurs.

Receiver is notDefined

RC=26. The receiver program is notdefined.


No PPIAddress Space

RC=28. The NetView SSI addressspace is running, but no PPIfunction is defined to it.

The NetView SSI address spaceshould be enabled to process PPIrequests.

No Data inQueue

RC=30. The data buffer queue forthe receiver ID is empty.

This is the result of issuing aRECEIVE command but the bufferqueue is empty.

Receive bufferis too small

RC=31. The receive buffer specifiedin the request is too small to holdthe queued buffer.

This occurs when the RECEIVEcommand specifies a buffer areathat is too small to hold the queueddata buffer. Re-issue the requestspecifying a larger buffer area.

Text Meaning

No NetViewStorageAvailable

RC=32. The PPI has run out ofNetView Storage.

Buffer length isinvalid

RC=33. The buffer length supplied inthe request is invalid.

Receive Queueis full

RC=35. The receiver ID queue is full.

This occurs for a SEND commandwhen the receiver's buffer queuehas reached its defined limit.

ESTAE cannotbe established

RC=36. A recovery environmentcould not be established.

SENDER,RECEIVER IDsare invalid

RC=40. Either the sender or receiverID is not valid.

Processingerror hasoccurred

RC=90. An internal processing errorhas occurred.


Operator responseReport the error condition to your system programmer.

System programmer responseReport the problem to the SA z/OS service team forfurther diagnosis.

INGY1203I Request failed for adname-opnum(jobname) on wsname

ExplanationThis is an information message to describe the TWSfunction that incurred an error during processing. Thiserror message is always issued in addition to errormessages INGY1201 and INGY1202.

adname is the TWS Application Description.opnum is the TWS Operation Number in theApplication Description.jobname is optional and is the TWS jobname that isassociated with the Operation Number.wsname is the TWS Workstation name that wasprocessing the Operation at the time of the error.




Operator responseNo action is required. This message providesinformation that can be used to help diagnose theproblem.


INGY1300I aa bb cc dd ee

ExplanationThe Job Log Monitoring has read a message from a logdata set and has sent this message to NetView forautomation.

This message is a multi-line message. The first line is alabel line showing the following tokens:

The variable aa is the owner of the job. The value is8 characters long and filled with blanks ifnecessary.The variable bb is the name of the job. The value is8 characters long and filled with blanks ifnecessary.The variable cc is the job identifier. The value is 8characters long and filled with blanks if necessary.The variable dd is the ddname of the correspondingspooled data set. The value is 8 characters long andfilled with blanks if necessary.The variable ee is the message ID that has beendefined in the ISPF dialogs as one of the filtercriteria. The value is up to 32 characters long andleft-justified. The variable shows the value 'N/A' forall non-SA controlled jobs.

Each subsequent line represents a line of the originalmessage.


System programmer responseProcessing continues.


INGY1301I Job Log Monitoring is ready forrequests.

ExplanationThe Job Log Monitoring task has been started and isnow ready for processing requests.




INGY1302I Job Log Monitoring is beingterminated.

ExplanationJob Log Monitoring task has been stopped by aNetView stop command or during NetViewtermination. All opened data sets are closed anddeallocated. And all monitoring information is deleted.

System actionThe task is terminated.



INGY1303I Job Log Monitoring has beensuspended.

ExplanationThe Job Log Monitoring task has been stopped onrequest. All opened data sets are closed anddeallocated. The monitoring information is kept forrestarting the task later.






INGY1304I JES2 or JES3 is not the primaryjob entry subsystem.

ExplanationSA z/OS only supports Job Log Monitoring for JES2 andJES3. Since the task may be started before any jobentry subsystem is started the job entry subsystemcheck is delayed until the first request is received.



System programmer responseRemove all definitions from Job Log Monitoring fromyour PDB and rebuild the PDB. This prevents SA z/OSfrom starting the task the next time when theconfiguration is being refreshed.

INGY1305I Job Log Monitoring has beenstarted for uid-jnm-jid-ddn.

ExplanationThe Job Log Monitoring task has allocated the spooldata set that corresponds to indicated ddname andmonitors new incoming messages. Note that emptymessages lines are suppressed.

The variable uid is the owner of the job.The variable jnm is the name of the job.The variable jid is the job identifier.The variable ddn is the ddname of the monitoredspool data set.




INGY1306I Job Log Monitoring has beenstopped for uid-jnm-jid-ddn.

ExplanationThe Job Log Monitoring task has removed thecorresponding spool data set from monitoring. Thedata set has been closed and deallocated.





INGY1307I Error condition detected whenprocessing uid-jnm-jid-ddn, RC=rcRSN=rsn.

ExplanationThe Job Log Monitoring detected an error conditionwhen it processes the spool data set that correspondsto the ddname. The return and reason codes describethe particular reason.

• The variable uid is the owner of the job.• The variable jnm is the name of the job.• The variable jid is the job identifier.• The variable ddn is the ddname of the monitored

spool data set.• The variable rc shows the return code:

8Message retrieval failed.

12Stop monitoring failed.

16Start monitoring failed.

• The variable rsn shows the reason code inhexadecimal characters. The first byte of the reasoncode describes the function, the second byte is thereturn code of the failing macro, and the last twobytes represent the reason code of the failing macro.See Table 10 on page 410.



Table 10. First byte (function code) of the reason code

Function Failing Macro Terminate

'01'x ESTAE Yes

'11'x STORAGEOBTAIN

Yes

'12'x STORAGERELEASE

Yes

'21'x DYNALLOCALLOCATE

Yes

'22'x DYNALLOC FREE Yes

'31'x GENCB ACB

'32'x GENCB RPL Yes

'33'x OPEN ACB

'34'x MODCB RPL

'35'x CLOSE ACB Yes

'36'x POINT RPL

'37'x GET RPL

'41'x GET CGLOBAL Yes

'42'x SET CGLOBAL Yes

'51'x RACROUTEAUTH

'61'x CREATE Name/Token

Yes

'62'x DELETE Name/Token

Yes

'63'x READ Name/Token

Yes

'71'x DSPSERVCREATE

Yes

'72'x DSPSERVEXTEND

'73'x ALESERV ADD Yes

'74'x ALESERVDELETE

Yes

'75'x TCBTOKEN Yes

'76'x SRB Yes

'77'x LOAD Yes

System actionIf the message was issued by the task INGTJLM, thetask is terminated depending on the function that wasperformed (see Table 10 on page 410).


System programmer responseCorrect the error condition that relates to the functionspecific return and reason codes. Restart the task ifnecessary.

INGY1308I Internal error condition detected.RC=rc RSN=rsn.

ExplanationThe Job Log Monitoring could not initializesuccessfully.

• The variable rc shows the return code.• The variable rsn shows the reason code. For a

description of the reason codes, refer to Table 10 onpage 410.

System actionThe task is terminated when rc shows a value of 12 orhigher.


System programmer responseIf the task is terminated contact your IBM SupportCenter.

INGY1309I Job Log Monitoring encounteredabend SCC=scc RSN=rsn.

ExplanationThe Job Log Monitoring encountered the indicatedabend. The system completion and reason codesdescribe the abend condition.

The variable scc shows the system completioncode.The variable rsn shows the abend reason code.

System actionAfter all data sets have been closed and deallocatedthe task is terminated.




System programmer responseWhen the cause of the abend is eliminated you mayrestart the task using the NetView command START.

INGY1310I Syntax error on parm.

ExplanationThe command processor for Job Log Monitoringdetected a syntax error.

• The variable parm shows the parameter in error.CMD

A required parameter is missing. Or, an impropercombination of parameters or an unknownparameter has been detected.

DDNThe keyword value is not a valid ddname.

INTERVALThe monitoring interval is not in the range 1 to3600.

JOBIDThe job identifier is incorrect or too long.

JOBNMThe job name is incorrect or too long.

POLLThe polling time is not in the range from 1 to3600.

OWNERThe name of the job owner is incorrect or is toolong.

REQThe request is not one of the following: RECYCLE,START, STOP, STATUS, SUSPEND


Operator responseCorrect the error condition and reissue the command.


INGY1311I Application jobnm(subsysnm) willnot be monitored, RSN=rsn

ExplanationMonitoring is disabled for the indicated applicationbecause no filter criteria have been defined or theapplication does not run under control of JES2 orJES3.

• The variable jobnm shows the job name of theapplication.

• The variable subsysnm shows the subsystem nameof the application.

• The variable rsn shows one of the following reasons:1

No filter criteria have been defined.2

Application does not run under control of JES2 orJES3.



System programmer responseCorrect the policy data, rebuild the ACF, and refreshthe configuration data.

Note: You need to define at least one filter criteriaeven if all messages are processed.

INGY1312I Command processing failed, RC=rcRSN=rsn.

ExplanationThe command processor for Job Log Monitoringdetected an internal error.

• The variable rc shows the return code of the internalerror condition.

• The variable rsn shows the reason code of theinternal error condition:12

No filter criteria found for the job.16

Job has not been defined for monitoring.20

No filter criteria could be found.




Operator responseIn case of reason code 20 verify that the filter criteriahave been defined and that the clist INGRJLMP ransuccessfully.


INGY1313I Job Log Monitoring task is notactive

ExplanationThe command processor found the Job Log Monitoringtask inactive.


Operator responseStart the task and reissue the command.


INGY1314I uid-jnm-jid-ddn is already beingmonitored

ExplanationJob Log Monitoring does already monitor the spooldata set that corresponds to the indicated ddname.


System actionThe command is ignored.



INGY1315I uid-jnm-jid-ddn has not beenactivated for monitoring.

ExplanationJob Log Monitoring has not been instructed to monitorthe spool data set of the indicated data set.


System actionThe command is ignored.



INGY1316I Automation environment has notbeen initialized.

ExplanationThe Job Log Monitoring task detected that theautomation environment has not been initialized. If thetask was already active all monitoring is delayed untilthe automation environment is initialized.

System actionThe task is terminated if it was started by thecommand.

Operator responseRetry the command after the automation environmenthas been initialized.


INGY1317I Job uid-jnm-jid not found.

ExplanationThe Job Log Monitoring task did not find the indicatedjob active or on the output queue.

The variable uid is the owner of the job.The variable jnm shows the job name.The variable jid shows the job identifier.




Operator responseIn case a parameter was misspelled, correct the valueand reissue the command.


INGY1318I Job Log Monitoring has beenterminated for uid-jnm-jid-ddn.

ExplanationThe Job Log Monitoring task did not find the job active,but on the output queue. After all messages have beenprocessed the monitoring is terminated for the spooldata set that corresponds to the indicated ddname.





INGY1319I No Job Log Monitoring definitionsfound.

ExplanationThe Job Log Monitoring task did not find anymonitoring definitions. However, because of the ACFinformation SysOps assumes that the monitoringdefinitions are available.

System actionThe ACF-based request is rejected. Only manualmonitoring requests are honored.


System programmer responseCheck the NetView log and the policy databasedefinitions as to why the task could not find anymonitoring definitions. The clist INGRJLMP preparesand stores the definitions used by the monitoring task.

INGY1320I DDname ddn of jnm/jid not found

ExplanationThe Job Log Monitoring task did not find the indicatedddname in JCL image of the job.

Variable ddn shows the ddname.Variable jnm shows the job name.Variable jid shows the job identifier.


Operator responseIn case one of the keyword values was misspelled,correct the value and reissue the command.


INGY1321I Multiple job ids (jid/jid) exist forjnm.

ExplanationAn INGJLM START | STOP command was issuedwithout the JOBID parameter. However, the Job LogMonitoring function found at least two job ids for thespecified job name. The first two job ids are presentedin the message.

The variable jnm shows the job name.The variable jid shows a job identifier.


Operator responseReissue the command using a specific job id.


INGY1322I Multiple jobs (uid/uid) exist forjnm.



ExplanationAn INGJLM START | STOP command was issuedwithout the OWNER parameter. However, the Job LogMonitoring function found at least two jobs for thespecified job name but with different owners. Theowners of the first two jobs are presented in themessage.

The variable uid shows an owner of the job name.The variable jnm shows the job name.


Operator responseReissue the command using a specific job id.


INGY1323I reqtype job id failed. RC=rc1/rc2.

ExplanationThe task INGTJLM failed to receive or return a job id.

Only when NetView has been started with SUB=MSTRand the task DSIRQJOB has not been defined,INGTJLM tries to receive a job id from the primary JESduring task initialization. The job id is normallyrequested by DSIRQJOB. When the job id is notreceived any spool data set browse request results inassigning a non-printable job id which leaves JES 'notdormant' (message $HASP607) on shutdown andrequires the CANCEL command to terminate JES.

The variable reqtype shows the type of request.The variable rc1 shows the SSI return code.The variable rc2 shows additional return codeinformation for return code 0.

Refer to "MVS Using the Subsystem Interface" for adetailed explanation of the return codes.


Operator responseCorrect the error condition and restart the task.


INGY1324I Job id jid received.

ExplanationThe task INGTJLM received the indicated job id fromJES.

Only when NetView has been started with SUB=MSTRand the task DSIRQJOB has not been defined,INGTJLM requests a job id from the primary JES duringtask initialization. Without a job id any spool data setbrowse request results in assigning a non-printable jobid which leaves JES 'not dormant' (message$HASP607) on shutdown and requires the CANCELcommand to terminate JES.

The variable jid shows the job id.

Note: The request was done without requiring theallocation of a joblog.

System actionProcessing continues. The job id will be returned toJES at task termination.



INGY1325I Job id jid returned.

ExplanationThe task INGTJLM returned the indicated job id to JES.The job id was requested during task initializationbecause NetView has been started with SUB=MSTRand the task DSIRQJOB has not been defined.

The variable jid shows the job id.




INGY1326I Job Log Monitoring suspended dueto missing job id.



ExplanationThe task INGTJLM detected that the task DSIRQJOBhas not received a job id from JES or has returned thejob id to JES. Without a job id any spool data setbrowse request results in assigning a non-printable jobid which leaves JES 'not dormant' on shutdown andrequires the CANCEL command to terminate JES. Toprevent JES from being canceled the task performs aninternal SUSPEND command. All open data sets areclosed and deallocated. The monitoring information iskept for restarting.



System programmer responseDetermine the reason why the job id is not available.After the task DSIRQJOB has received a job id again(refer to message DWO154I) the task INGTJLM isautomatically restarted.

INGY1327I req_type of JES node informationfailed. RC=rc1/rc2/rc3

ExplanationThe task INGTJLM failed to determine the owner or thetask could not release the node of JES2 informationprovided by JES.

The node id is part of the resource name that is usedto perform the SAF check for verifying read access to aJESSPOOL resource associated with a spool data set.

• The variable req_type shows the type of request.• The variable rc1 shows the SSI return code.• The variable rc2 shows the SSOBRETN field.• The variable rc3 shows the SSJPRETN field.

System action:The task is terminated.


System programmer response:Correct the error condition and restart the task.

INGY1328I No READ access to internal spooldata set of owner-job-jid

ExplanationJob log monitoring has no READ access to an internalspool data set of the indicated job. The internal spooldata set holds relationship information betweenddnames and spool data sets.

The variable owner shows the owner of the job.The variable job shows the name of the job.The variable jid shows the job identifier.

System action:The request is rejected.


System programmer response:Search the netlog or syslog of the profile name thatinhibits Job Log Monitoring from accessing the spooldata set. Correct the problem and re-issue therequest.

INGY1329I SAF check of request aa failed,RC=bb

ExplanationThe issuer of the command is not allowed to performthe indicated request.

• The variable aa shows the request.• The variable bb shows the return code of the

NetView service DSIKVS.


Operator responseRe-issue the command after you have been granted toperform the request.


INGY1330I No valid primary job entrysubsystem found.

Explanation:The Job Log Monitoring system could not detect a validprimary job entry subsystem. Either the supportedsubsystem has not initialized yet or an unsupportedsubsystem is the primary job entry subsystem.


Operator response:



When the primary job entry subsystem is supported,re-issue the command after the subsystem hasinitialized.


INGY1331I IEFSSREQ request req failed foruid-jnm-jid-ddn with RC=ssirc

ExplanationThe job marked the spool data set for spinning off. Thetask INGTJLM failed to determine the current data setname of the indicated ddname.

The variable req shows the type of request.The variable uid shows the owner of the job.The variable jnm shows the name of the job.The variable jid shows the job identifier.The variable ddn shows the DD name.The variable ssirc shows the SSI return code.

Refer to 'SSI Function Code 80' in MVS Using theSubsystem Interface for a detailed explanation of thereturn code.



System programmer responseFor return code 4, remove the JESLOG parameter andrestart the job.

For return code 24, wait for the completion of the SSIand start the monitoring manually.

For all other return codes, contact your IBM SupportCenter.

INGY1332I Next SPIN data set for uid-jnm-jid-ddn not found.

ExplanationThe indicated job ended before Job Log Monitoringcould allocate the next spool data set in sequence. Alldata of this data set is lost.

The variable uid shows the owner of the job.The variable jnm shows the name of the job.The variable jid shows the job identifier.The variable ddn shows the DD name.

System action:Monitoring for the indicated DD name is terminated.



Hold the spool data set until Job Log Monitoring hasprocessed the data set. Check for messagesINGY1333I or INGY1306I to determine when thespool data set can be released.

INGY1333I SPIN message found: aa-bb-cc-dd-ee-ff

ExplanationJob Log Monitoring has trapped the SPIN message forthe indicated data set. This means JES has allocated anew spool data set for the ddname. And, subsequentmessages are written to the data set.

The variable aa shows the owner of the job.The variable bb shows the name of the job.The variable cc shows the job identifier.The variable dd shows the DD name.The variable ee shows the spool data set identifier.The variable ff shows the SYSOUT identifier of thejob output that is associated with the spool dataset.

The SYSOUT identifier can be used in subsequentspool commands to release or cancel the data set, forexample, on the OUTGRP parameter of a JES2 spoolcommand, or on the DSN parameter of a JES3 spoolcommand.

System action:Processing of the indicated spool data set identifierhas finished.



INGY1334I req request failed, RSN=rsn

ExplanationThe command processor could not complete theindicated request successfully.

The variable req shows the request.The variable rsn shows the reason code. For adescription of the reason codes, refer to table Table10 on page 410.

System action:The command is rejected.


System programmer response:Contact your IBM Support Center.

INGY1335I req request failed, RC=rc COMP=ccCODE=code RSN=rsn.



ExplanationJob Log Monitoring scheduled an SRB in the Masteraddress to create, extend, or delete a data space. TheSRB did not complete successfully for the indicatedreason.

The variable req shows the request.The variable rc shows the return code of the macroIEAMSCHD.The variable cc shows the completion code of themacro IEAMSCHD.The variable code shows information associatedwith the completion code.The variable rsn shows additional informationassociated with the completion code.

System action:If the message is issued by the task INGTJLM the taskis terminated.


System programmer response:If the task is terminated, contact your IBM SupportCenter.

INGY1336I RECYCLE behavior has been set toval.

ExplanationThe behavior of Job Log Monitoring after a NetViewrecycle has been set to the indicated value.

The variable val shows one of the following values:RESET - The internal structure is cleared on thenext start after NetView has been recycled.RESUME - Job Log Monitoring continues themonitoring on the next start after NetView has beenrecycled using the last information that is kept inthe internal structure before monitoring is stopped.

System action:The command completed successfully.



INGY1337I Job Log Monitoring suspendedsince JES had not initialized yet.

Explanation:The task INGTJLM detected that the Job EntrySubsystem had not initialized yet. The function issuspended and will automatically be resumed as soonas the task DSIRQJOB receives a job ID. In case thatthis task is not defined to NetView, either JES message(HASP492 or IAT2645) will restart INGTJLM.

System action:The task is terminated.







Chapter 10. Messages ISQ001I to ISQ901I

ISQ001I cmd_entity CANNOT FINDPARAMETER ENTITY OR ENTITYNEEDS MORE PARAMETERS.

ExplanationThe parameter entity specified with the command wasnot found in the ProcOps tables, or if it is definedadditional parameter(s) are required to process thecommand successfully.

cmd_entities can be target system names with consoledesignators SC or OC, or path names together with aconsole designator of 'S'.

System actionThe command does not complete.

Operator responseIf this message does not show a command name, seethe NetView log if additional error messages areshown at the time of the error and contact your systemprogrammer.

System programmer responseIf the used parameter entity is not defined make sureit is defined using the SA z/OS Customization Dialogs.Use the Dialog Build function to generate a new ACF tobe used with ProcOps. Reload the ACF and recycleProcOps, then repeat the command.

Modules: ISQXLOC, ISQXUNL, ISQOVRD

ISQ003I SEVERE INTERNAL ERROR FOUNDBY routine-name.

ExplanationAn internal error has occurred. After this messageappears, other messages that contain informationabout the error are written to the NetView log.

System actionThe command or process in progress when the erroroccurred does not complete.

Operator responseWrite down the routine name shown in this message.Also, save or print a copy of the NetView log, andcontact your system programmer.

System programmer responseContact an IBM support representative.

ISQ004I INDEX TO target-table IN source-table ENTRY entry-location.

ExplanationThis message may be preceded by message ISQ003I.It contains internal error information and is written tothe netlog. This message is for IBM service use only.

System actionSA z/OS processing continues. Other messagesindicate whether the command or process associatedwith this message succeeded or failed.

Operator responseWrite down the information shown in this message.Also, save or print a copy of the netlog, and contactyour system programmer.


ISQ005I UNEXPECTED RETURN CODEreturn-code FROM program.

ExplanationThis message may be preceded by message ISQ003I.It contains internal error information and is written tothe netlog. This message is for IBM service use only.


Operator responseSave or print a copy of the netlog and contact yoursystem programmer.


Messages ISQ001I to ISQ901I


ISQ006I MSGID: message-identifier TASK:task-name COMMAND: command-name CSECt: module-name.

ExplanationThis is a netlog entry. It appears only if the DEBUGparameter of the ISQSTART command was specified.

System actionNone.

Operator responseFollow the directions for the message identified withinthis message.


ISQ011I LOSS OF CONSOLE LOCK [TO task-name].

ExplanationYou no longer own the lock for the port that you issuedthe ISQSEND command to. Another task took the lockfor the console using the ISQOVRD command whilethe ISQSEND command was running. Because of this,the results of issuing the ISQSEND command areunpredictable.

If another task currently owns the lock for the port, itis identified by the variable task-name in the message.If no task currently owns the port, no task-namevariable appears in the message.


Operator responseDetermine which task should properly own the lock forthe console and establish this ownership.


ISQ012I INCORRECT SYNTAX FORcommand-name COMMAND.

ExplanationThe command identified in this message was notentered correctly.

System actionProcessing of the command ends before it is complete.

Operator responseReenter the command after checking to be sure itssyntax is correct.


ISQ013I command-name: EITHER TARGETAND CONSOLE OR PATH ANDCONNECTION REQUIRED.

ExplanationThe command you entered (command-name) requiresthat you specify either a path name and a connectioncharacter or a target name and a console identifier.


Operator responseReenter the command, including all neededparameters.


ISQ014I command-name: PARAMETERNUMBER argument-number ISproblem.

ExplanationThe command argument entered (identified byargument-number) is not valid, for one of severalreasons. The variable problem identifies the reasonwhy the argument is not valid. Possible reasons are:

• There are too many characters in the argument.• The argument is not a valid option for the command.• A value that is not acceptable was entered for the

argument. (In this case, the problem variable liststhe acceptable values.)




Operator responseReenter the command after checking to be sure itssyntax is correct.


ISQ015I command-name: entity-name ISNOT A VALID ENTITY NAME.

ExplanationAs part of the command command-name, the entityname you entered is not valid. Entity names can betarget system or target hardware names. Refer to thecommand help to learn which entity types are valid forcommand-name.


Operator responseReenter the command, making sure that the entityname is correct and that it identifies a defined targetsystem or target hardware name.


ISQ016I command-name: console-ID ISNOT A VALID CONSOLEIDENTIFIER.

ExplanationAs part of the command command-name, you entereda console identifier (console-ID) that is not valid. Theonly valid console identifiers are:

• SC• OC• SCA• SCB• OCA• OCB

Not all of these console identifiers are valid for allcommands.


Operator responseReenter the command, specifying a valid consoleidentifier.


ISQ017I command-name COMPLETEDSUCCESSFULLY.

ExplanationProcessing of the command completed successfully.

System actionNone.



ISQ021I TARGET PATH target-name portHAS NOT BEEN INITIALIZED

ExplanationThis message appears in response to the ISQEXECcommand. The specified target system target-namewas not initialized.

System actionThe command terminates before it is complete.

Operator responseInitialize the target system using command ISQXIII,then repeat the ISQEXEC command.


ISQ022I command-name COMMAND HASBEEN QUEUED FOR PROCESSINGBY TASK task-name.


Chapter 10. Messages ISQ001I to ISQ901I 421

ExplanationThis message appears in response to the ISQEXECcommand. A user automation command (command-name) was sent to a target control task (task-name) forprocessing.

System actionNone.



ISQ023I No command entered in command-name request.

ExplanationThis message appears in response to a command. Thecommand was issued without any Commandparameter specified.


Operator responseReenter the command, specifying a value for thecommand parameter.


ISQ024I command-name PROCESSINGUNDER TASK task-name WASSCHEDULED BY initiating-task.

ExplanationThis message is written to the NetView log as part ofan audit trail when the DEBUG parameter of theISQSTART command has been specified. This messageis for IBM service use only.

System actionNone.



ISQ025I task- name AND SUBSEQUENTTASKS ARE NOT STARTED.

ExplanationAn attempt was made to start a NetView task but noconfirmation message was received within therequired time.

The variable task- name shows the name of thetask that did not start.

System actionSA z/OS processor operations initialization continuesbut function and/or performance may be limited. Noattempt will be made to start other tasks in the samegroup. For example, if ISQBT003 is indicated as thetask that failed to start no attempt will be made tostart task ISQBT004 and higher.

Operator responseTake a note of the details and contact your systemprogrammer.

System programmer responseEnsure that the NetView operator and task definitionsbuilt from the SA z/OS dialogs have been included intoDSIOPF and DSIDMN respectively. Further messagesmay be available in the NetView log if processoroperations is started with the DEBUG option onISQSTART.

ISQ026I value-passed IS NOT A VALID type-of-value VALUE FOR command-name.

ExplanationThis message is written to the NetView log and is forIBM service use only.


Operator responseSave or print the NetView log, and contact your systemprogrammer.




ISQ027I TEXT IS MISSING FOR ISQmessage-number MESSAGE.

ExplanationNo message text exists for a message entry. MessageISQ027I is issued in place of the message that text ismissing for.

System actionNone.

Operator responseContact your system programmer. Find the messagethat text is missing for in this manual orthe online helpand follow the operator response instructions given forit.

System programmer responseMake sure the messages library (ISQ.ISQMLIB) isconcatenated to the NetView data sets. Check theappropriate DSIISQxx message member, where xx arethe first two digits of the message number. If the textis missing, edit the member.

ISQ028I ENTRY COUNT DISCREPANCYBETWEEN INTERESTEDOPERATOR LIST AND INDEX.




System programmer responseIf this problem recurs after SA z/OS is restarted,contact an IBM support representative.

ISQ030I CANNOT RUN command-nameUNTIL PROC-OPS HAS STARTED.

ExplanationProcessor operations must be started before thiscommand can be executed. If command-namevariable is blank, this message was issued frominternal ProcOps routines that requires ProcessorOperations to be started. If the command-namevariable contains a command name, the ISQCHKcommand was executed with the command-name asparameter. See command ISQCHK for moreinformation.


Operator responseStart processor operations by issuing the ISQSTARTcommand.


ISQ031I TARGET HARDWARE target-hardware-name TYPE IS NOTVALID.

ExplanationThis message is written to the netlog and is for IBMservice use only.




ISQ032I COMMAND command_nameCANNOT BE EXECUTED. REASONCODE: rsn

ExplanationThis message appears in response to an ISQCCMDcommand. The associated reason code contains theerror condition, as follows:



1The command has been identified as using theProcOps communication paths SNMP or TCP, butthe required SA Subtower statement PROCOPS isnot defined in the NetView style sheet.

2The command has been identified as using theProcOps communication paths SNMP or TCP, butProcOps is not active.

3The command has been identified as using theSA z/OS BCPii communication path, but theconnection is either not defined correctly or hasnot started.

System actionThe ISQCCMD command is rejected.

Operator responseVerify that the error is corrected and reenter thecommand.

System programmer responseFor reason code 1, make sure there is an SA.TOWERstatement for PROCOPS available in your NetViewstyle sheet definitions, before you start ProcOps.

For reason code 2, make sure that ISQSTART isprocessed before issuing an ISQCCMD commoncommand. If you expect this command to use theBCPii path, make sure that the processor and systemdefinitions are correctly defined for an INTERNAL(BCPii) connection.

For reason code 3, make sure SA z/OS is fullyinitialized. If it is fully initialized, use the SA z/OS testcommand HSAET32 STATUS to validate that the BCPiiservices are enabled. If they are enabled, verify thatthe processor and system definitions are correctlydefined for an INTERNAL (BCPii) connection in yourSA z/OS policy database.

ISQ033I THE INTERESTED OPERATOR LISTFOR target-system-name console-ID IS FULL.

ExplanationThis message appears in response to the ISQXMONand ISQXIII commands. A console can have amaximum of 12 entries in its interested operators list.The list for this console is currently full.

System actionIf this message appears in response to the ISQXMONcommand, processing of the command ends before itis complete and no operator is added to the interestedoperators list. If this message appear in response tothe ISQXIII command, processing continues.

Operator responseDetermine whether or not all operators currently onthe interested operators list need to be there. Reenterthe command after someone has left the list.


ISQ034I THE SYSTEM LIMIT OF xxxINTERESTED OPERATORS WASREACHED.

ExplanationThis message appears in response to the ISQXMONand ISQXIII commands. The maximum number ofinterested operators is currently defined. No operatorscan be added to any interested operators list.

The parameter xxx describes the number ofreached operators.

System actionIf this message appears in response to the ISQXMONcommand, processing of the command ends before itis complete and no operator is added to the interestedoperators list. If this message appears in response tothe ISQXIII command, processing continues.

Operator responseDetermine whether or not any operator IDs can betaken off the list. Reenter the command aftermodifying the list.


ISQ035I number-of-argumentsARGUMENTS ARE REQUIRED ONTHE command-name COMMAND.

ExplanationThe specified command that does not have the correctnumber of arguments.




Operator responseReenter the command, making sure that it is correct.


ISQ036I operator-name NOW HASINTERESTED OPERATOR LISTSTATUS status FOR entity-name.

ExplanationThe operator has been added to or removed from thelist of interested operators to receive messages fromentity-name.

• The variable operator-name is the name of theoperator issuing the ISQXMON command.

• The variable status can be one of the following:

– ON indicating operator has been added to the list– OFF indicating operator has been taken from the

list.• The variable entity-name can be a valid Target

System Name.

System actionNone.



ISQ037I command-name HAS COMPLETEDWITH A RETURN CODE OF return-code.

ExplanationThis is a netlog trace message that appears when theDEBUG parameter of the ISQSTART commandspecified. This message is for IBM service use only.

System actionNone.



ISQ038I CANNOT RUN command-nameWHILE PROCOPS IS STARTING ORSTOPPING

ExplanationProcessor Operations must be active in order toexecute this command. Either ISQSTART is not yetcompleted or ProcOps is stopping through theISQSTOP command.

If command-name variable is blank, this message wasissued from internal ProcOps routines that requiresProcessor Operations to be active. If command-namevariable contains a command name, the ISQCHKcommand was executed with command-name asparameter. See command ISQCHK for moreinformation


Operator responseWait for completion of the active ISQSTART commandor start the Processor Operations again.


ISQ039I command-name task priority foroperator commands must be LOW.

Explanation:Processor Operations command ISQSTART detectedthat the task priority for operator command is notLOW. This is required for ISQCCMD commoncommands to execute correctly.

System action:The command is not processed.

Operator response:Use NetView LIST OVERRIDE command to check thevalue of the CMD setting. Contact your systemprogrammer and repeat ISQSTART once the CMDsetting has been set to LOW.



System programmer responseEnsure that the CMD setting corresponds to one of thefollowing 3 settings supported by ProcessorOperations (output from LIST OVERRIDE command):

DEFAULTS OVERRIDES

CMD: LOWCMD: HIGH LOWCMD: LOW LOW

ISQ041I ccmd IS NOT SUPPORTED BYISQSEND, USE ISQCCMD.

ExplanationThe common command ccmd is not supported by theISQSEND command. It is supported by the ISQCCMDcommand.

System actionThe ISQSEND command is rejected.

Operator responseReenter the command using ISQCCMD.


ISQ042I command-name: console-typeconsole has not been defined fortarget system target-system-name.

ExplanationProcessing of the command ends before it iscompleted because the specified console was notdefined for the target system. The variable console-type shows the type of console that needs to bedefined. Possible values for console-type are:

• Active operating system• Active system• Backup operating system• Backup system• An MVS system• A VM

System actionProcessing of the ISQXCLS command ends before it iscomplete.


System programmer responseMake sure the console for the target system is definedin the SA OS/390 configuration dialogs

ISQ044I DIAGNOSTIC TRACE MESSAGE:trace-message.

ExplanationThis is a NetView log trace message appears whendebugging is active for SA z/OS. Debugging is activatedwhen the ISQSTART command is issued with theDEBUG option specified.

System actionNone.



ISQ052I Command command-name failed.

ExplanationProcessing of the command identified in this messageends before it is complete. Other messages provideadditional information about the problem.


Operator responseTry to determine the cause of the failure, usinginformation from the messages that appear. Reenterthe command. If the problem persists, contact yoursystem programmer.

System programmer responseRefer to IBM Z System Automation User's Guide and toIBM Z System Automation Operator's Commands forinformation about the command that failed. Use thisinformation and message information to determine thecause of the failure.



ISQ059I ALL LPARS ARE ALREADY ACTIVEON SYSTEM target-hardware-name.

ExplanationThis message appears in response to a command toinitialize a target system running on a logicallypartitioned target hardware. All logical partitions onthe target hardware are active. No additional targetsystems can be initialized for this target hardware.


Operator responseClose one of the target systems that are active on thetarget hardware and reenter the command.

Caution: If you are using the ISQXIPL command or theISQCCMD ACTIVATE command with the FORCE optionto initialize a target system, you may disrupt a targetsystem that is already active on the target hardware.


ISQ061I LOCK STACK {OVERFLOW |UNDERFLOW} IN PROGRAMprogram-name.

ExplanationAn internal error has occurred. This message is for IBMservice use only.

System actionProcessing of the internal command ends before it iscomplete.

Operator responseRecord the information in this message and contactyour system programmer.


ISQ062I TARGET system-name HAS BEENINITIALIZED.

ExplanationThis message appears in response to the ISQXIIIcommand to initialize a target system. Processing ofthe command completed successfully.

This does not mean necessarily that the connection tothe SE/HMC of the processor for the target systemitself was successfully established.

For target systems, a ProcOps status of INITIALIZEDmeans that in case of communication problems duringISQXIII processing, ProcOps will automatically retry toestablish a connection. This depends on the setting ofa POLL FREQUENCY value in SA customization dialogsfor the processor of this target system.

System actionNone.



ISQ063I TARGET system-name ISINITIALIZED ALREADY.

ExplanationThis message appears in response to the ISQXIIIcommand to initialize a target system. The targetsystem is already initialized.

System actionProcessing of the command ends before it is complete.The target entity is not re-initialized.



ISQ067I PF-key IS NOT A VALID FUNCTIONKEY. PLEASE SELECT ANOTHER.

ExplanationThis message appears when you press a function keythat is not defined for the current status panel.



System actionProcessing of the command continues.

Operator responseSelect a function key from the list of valid keys at thebottom of the status panel.


ISQ069I Cursor is not on a valid object.

ExplanationYou tried to select an option on a status panel, but thecursor was not positioned so that an option could beselected.


Operator responseMove the cursor to the line that contains what youwant to select and press the PF key again.


ISQ070I UNABLE TO LOCATE data-identifier.

ExplanationThis message appears in response to an attempt todisplay a status panel. The panel cannot be displayed,due to an internal error.


Operator responseSave or print a copy of the NetView log and contactyour system programmer.


ISQ075I SCHEDULING OF COMMANDcommand_name ENDED WITH RCcmd_rc

ExplanationThe command command_name issued per commandcharacter from the ISQXDST target system summarypanel for a selected target system, was scheduled forexecution on the target system's control task. Thescheduling ended with a return code of cmd_rc. Whencommand_name completes, the target system statuswill be updated.

System actionNone.



ISQ076I LAST TARGET IS ALREADYDISPLAYED; CANNOT SCROLLDOWN.

ExplanationThis message appears when you press the PF8 key toscroll the screen down and there are no more targetsystems to display.

System actionThe request to scroll the screen is ignored.



ISQ077I ALREADY AT THE TOP; CANNOTSCROLL UP.

ExplanationThis message appears when you press the PF7 key toscroll the screen up and there are no previous targetsystems to display.

System actionThe request to scroll the screen is ignored.





ISQ078I PATH path-name IS NOW CLOSED.

ExplanationThis message appears in response to a command toclose a port. The command was processedsuccessfully and the port is now closed.

System actionNone.



ISQ079I COMMAND command_nameENDED WITH RC cmd_rc

ExplanationThe command command_name issued per commandcharacter from the ISQXDST target system summarypanel for a selected target system, ended with a returncode of cmd_rc:

System actionNone.



ISQ080I command-name MAY TAKESEVERAL MINUTES.

ExplanationThe command you entered normally takes up toseveral minutes to be processed.




ISQ088I CONNECTION TO TARGETHARDWARE target-hardware-name NOT ESTABLISHED.

ExplanationThis message appears in response to an ISQCCMDcommon command request with a target hardwarename as parameter. There is no connectionestablished to this target hardware and the commoncommand is not executed. If the common command isprocessed in an LPAR Management (SA-BCPii)environment, a configuration problem may cause thismessage.

System actionISQCCMD processing ends. The common command isnot executed.

Operator responseFor ProcOps (SNMP protocol) defined target-hardware-name, at least one target system running on the targethardware must have been initialized to establish aconnection to the target hardware. To perform thenecessary initialization, use the ISQXIII command,followed by a valid target system name for this targethardware. This establishes a connection to the targethardware and then the ISQCCMD common commandrequest can be retried.

System programmer responseIf the ISQCCMD was used to perform an LPARManagement request over a SA-BCPii connection,make sure that a target system is defined that has thetarget-hardware-name and an LPAR assigned. Notethat this target system must also be a member of anSA group (SYSPLEX/STANDARD). Correct your PDBwhen needed and re-build your SOCNTL/ACF file.Refresh your active configuration and retry theISQCCMD.

ISQ089I TARGET target-system-name HASNOT BEEN INITIALIZED.



ExplanationOne of the following conditions exists:

• The command you issued did not complete becausethe target system identified in the message is notinitialized.

• The command you issued to initialize the targetsystem identified in the message did not completesuccessfully.


Operator responseIf the command you issued did not complete becausethe target system is not initialized, issue an ISQXIIIcommand to initialize the target system and thenreenter the original command.

If the command you issued to initialize the targetsystem failed, see the message that is displayedpreceding or following this one to learn why thecommand failed.


ISQ090I THE MESSAGE MONITOR TASKSCOULD NOT BE STOPPED.

ExplanationThis message appears when the ISQSTOP command isunable to stop the processor operations messagemonitor tasks.

System actionProcessing of the ISQSTOP command continues.

Operator responseThis is an informational message only. It may,however, indicate that additional errors may follow.

System programmer responseThis message may indicate that the operator task orautotask that the operator ISQSTOP command wasinvoked on is not allowing processor operations OSTtasks in the NetView address space sufficient CPUtime to free their resources and to terminate. Ifpossible, ensure the ISQSTOP command is issued fromtasks that receive limited message traffic, DOM's, andautomation. This message is more likely to be received

on a focal-point system that is running on auniprocessor or an LPAR on a multiprocessor that isdefined to run with only one processor.

ISQ091I PROC-OPS SHUTTING DOWN.DATA MAY NOT BE CURRENT.PLEASE EXIT.

ExplanationThis message appears on a SA z/OS status panel.SA z/OS is shutting down as a result of the ISQSTOPcommand. Data displayed on the panel may not beaccurate.

System actionProcessing of the ISQSTOP command continues.

Operator responsePress a function key to exit from the status panel.


ISQ092I PROC-OPS HAS STOPPED.

ExplanationThis message appears when you try to display a statuspanel after processor operations has been shut down.It is also displayed when you exit from a status panelafter processor operations has been shut down.

System actionNone.



ISQ095I message-ID AUTOMATION FAILED.error-description ERROR.

ExplanationThe automation routine that should normally beprocessed in response to the message message-IDwas not processed. The variable error-descriptioncontains text describing the type of error thatoccurred.



System actionThe automation routine is not processed.

Operator responseSave or print the NetView log and contact your systemprogrammer.

System programmer responseIf the error-description variable contains the words"message text error" check the text of the messagethat automation failed for in the NetView log. Makesure that the message table is correct and that none ofthe original entries have changed. If you still cannotlocate the source of the problem, contact an IBMsupport representative.

If the error-description variable contains any othertext, contact an IBM support representative.

ISQ100I UNABLE TO OBTAIN STORAGE FORINTERNAL TABLES.

ExplanationThe amount of storage required for processoroperations internal tables cannot be allocated.



System programmer responseIncrease the amount of storage available, byincreasing NetView storage allocations. If this does notsolve the problem, contact an IBM supportrepresentative.

ISQ101I UNABLE TO ALLOCATE DATA SETdata-set-name.

ExplanationThe option file that was specified in the ISQSTARTcommand cannot be allocated. See the precedingNetView messages for details. You should only specifyan option file should when advised to do so by IBMsupport.


Operator responseDetermine whether the specified data set name isvalid. If it is, correct the problem with the option filedata set.


ISQ102I PROC-OPS IS ALREADY STARTED.

ExplanationThe ISQSTART command was issued with an incorrectstart parameter that was specified when processoroperations was already running. If processoroperations is already running, you can only useISQSTART paramter DEBUG to initiate a warm start indebug mode.


Operator responseIf you want to restart processor operations with newconfiguration data, issue the ISQSTOP command andthen issue ISQSTART with the ACF parameter.

If you want to restart processor operations with thesame configuration, issue the ISQSTART commandwithout the ACF parameter to initiate a warm start.


ISQ103I WARM START ATTEMPTED WHENPROC-OPS WAS NOT ACTIVE.COLD START REQUIRED.

ExplanationThe ISQSTART command was issued without aconfiguration parameter when processor operationswas not active. If processor operations is not active,the ISQSTART command must include the ACFparameter.


Operator responseReenter the ISQSTART command, including the ACFparameter.




ISQ104I ERROR FREEING TABLE table-name. TABLE IS NOT FREED.

ExplanationThis message is a response to the ISQSTOP command.Due to an error the command did not completesuccessfully.

System actionProcessing of the ISQSTOP command ends before it iscomplete.

Operator responseRecord the information in this message and contactyour system programmer.


ISQ105I OUT OF SCOPE entity_typeENTRIES DETECTED, numDEFINITION(S) IGNORED

ExplanationThe license environment valid when processoroperations was started, has a limited target scope. Thefollowing entity_type definitions are ignored if theirscope is not local:entity_type

• PROCESSOR• PSM

numThe number of definitions for an entity_type whichhave been ignored.

The scope 'local' designates the central processorcomplex (CPC) on which the processor operationsprogram code is running. The defined PSMs must runas guests of z/VM host systems on the local processor.

System actionThe ISQSTART processing continues with theprocessor operations initialization for local entity_typesonly.


System programmer responseLook for additional messages in the netlog. If you findan ISQ124I message, this processor operationsconfiguration cannot be used in your current licenseenvironment, because it contains no entity_types witha local scope.

If the ISQ105I message occurred and ISQSTARTcompleted successfully, you may still find messages inthe netlog informing you about other configurationissues, which could be handled by processoroperations automatically. Depending on thesemessages, you may decide to change your processoroperations configuration and re-cycle processoroperations.

ISQ106I COLD START PROCESSINGSTARTED.

ExplanationThis message appears in response to an ISQSTARTcommand that includes the ACF parameter. Processingof the command completes successfully and processoroperations continues to start.

System actionNone.



ISQ107I WARM START PROCESSINGSTARTED.

ExplanationThis message appears in response to an ISQSTARTcommand that does not include the ACF parameter.Processing of the command completed successfullyand the processor operations warm start continues.

System actionNone.





ISQ108I EMPTY DATA SET data-set-name.

ExplanationThe option file that was specified in the ISQSTARTcommand does not contain any data records.


Operator responseDetermine whether the specified data set is valid andcontains appropriate XML control records. You shouldonly specify an option file when advised to do so byIBM support.


ISQ109I DATA SET data-set-name IS NOT AVALID XML FILE.

ExplanationThe data set that was specified in the ISQSTARTcommand does not contain XML style data.


Operator responseDetermine whether the specified option file is validand contains appropriate XML control records. Thefirst character of the data set must be <.

You should only specify an option file when advised todo so by IBM support.


ISQ110I ISQSTOP ISSUED FROM A TARGETCONTROL TASK.

ExplanationThe ISQSTOP command is running under a targetcontrol task.

System actionProcessing of the ISQSTOP command continues, butthe target control task is not ended.

Operator responseIssue a NetView STOP TASK command to end thetarget control task after processing of the ISQSTOPcommand is complete.


ISQ111I task-name WILL NOT BECANCELLED.

ExplanationThe ISQSTOP command is running under the targetcontrol task identified in this message. This task is notcanceled by the command.

System actionProcessing of the ISQSTOP command continues, butthe target control task is not ended.

Operator responseIssue a NetView STOP TASK command to end thetarget control task after processing of the ISQSTOPcommand is complete.


ISQ112I UNEXPECTED END OF CONTROLFILE DETECTED.

ExplanationThe end of the control file was reached before all ofthe required information was read.


Operator responseCheck that the correct control file data set is specified.


ISQ113I CONTROL FILE CONTAINS ARECORD OF AN INCORRECTLENGTH.



ExplanationThe control file contains a record that is either too longor too short.


Operator responseMake sure that the correct control file data set isspecified.


ISQ114I UNABLE TO OPEN THE CONTROLFILE DATA SET.

ExplanationThe request to OPEN the control file data set failed.


Operator responseCheck that the correct control file data set is specifiedon the ISQSTART command.


ISQ115I I/O ERROR OCCURRED READINGTHE CONTROL FILE DATA SET.

ExplanationThe specified control file data set could not be read.


Operator responseMake sure that the control file data set is properlyallocated and that the correct data set was specified.


ISQ116I AN ERROR CONDITION condition-code HAS BEEN RAISED.



Operator responseSave or print a copy of the NetView log and contactyour system programmer.


ISQ117I Target hardware thw is notreferenced by any target systems.

ExplanationThe ISQSTART processing detected that no targetsystems are associated with the target hardwareidentified in the message.thw

message variable containing the name of the targethardware without a reference.

System actionThe definition of the target hardware identified in themessage is ignored.

Operator responseContact your System Programmer.

System programmer responseIf you want this target hardware to be defined, use theconfiguration dialogs to change at least one targetsystem definition so that it references this targethardware. Then rebuild the processor/system entry inthe Policy Database and refresh the ACF on theProcOps FP system. In order to activate the changes inProcOps, issue command ISQSTOP, followed by aISQSTART ACF command.

ISQ118I No target hardware has beenspecified for target system tgt

ExplanationThe ISQSTART processing detected that no targethardware has been specified for the target systemidentified in this message.



tgtmessage variable containing the name of thereferenced target system.

System actionThe target system is ignored.


System programmer responseIf you want the target system defined, specify a targethardware for this system using the PROCESSOR policyunder the system entry type. Then rebuild theprocessor/system entry in the Policy Database andrefresh the ACF on the ProcOps FP system. In order toactivate the changes in ProcOps, issue commandISQSTOP, followed by a ISQSTART ACF command.

ISQ119I Target system tgt referenced inLPAR TABLE is not defined

ExplanationThe ISQSTART processing detected that the targetsystem name used in the LPAR TABLE of a targethardware (processor) is not defined.tgt

message variable containing the name of thereferenced target system.

System actionThe target system is ignored.


System programmer responseVerify the PROCESSOR entries for ProcOps in yourPolicy Database. Make sure that the LPAR list entriescontain only target system names of actually definedSYSTEM entries, or leave the system field blank. Thenrebuild the processor/system entry in the PolicyDatabase and refresh the ACF on the ProcOps FPsystem. In order to activate the changes in ProcOps,issue command ISQSTOP, followed by a ISQSTARTACF command.

ISQ120I INDEX VALUE FOR A TABLE ENTRYIS NOT AVAILABLE

ExplanationThe ISQSTART processing detected that an indexvalue, required to correlate the entries of differenttable types, could not be determined. Without its tableentries correlated, ProcOps cannot be used.



System programmer responseSince this problem may have been caused bysuperfluous configuration variables still available aftera SA configuration refresh, it is recommended torecycle ProcOps using the ISQSTART ACFCLEANcommand. If the problem persists, contact IBMSupport.

ISQ121I SENDING ISQXIII target-system-name TO TARGET CONTROL TASKtask-name.

ExplanationThe command to initialize the target system target-system-name was sent to the target control task task-name for processing.


Operator responseWait until the target system is initialized before takingany action.


ISQ122I FAILURE DURINGINITIALIZATION OF ENTITYentity-name. CLOSING ENTITY.

ExplanationThis message appears in response to a ISQXIIIcommand to initialize a connection to this entity. Anerror occurred that prevented the entity from beinginitialized, and the entity was closed.



System actionThe entity is closed.

Operator responseLook for other messages that describe the error thatcaused the failure. Follow the directions given in thedescriptions of those messages in this book.


ISQ123I command-name: entity NAME ISNEITHER A TARGET SYSTEM OR ATARGET HARDWARE.

ExplanationThe processing of the command ended before it wascomplete because the entity name specified was notrecognized as a target system or target hardware byProcOps.

Variable command-name shows the name of thecommand that this message is a response to.Variable entity identifies the target system or targethardware specified to be initialized.


Operator responseMake sure to specify the name of a defined entity inthe command.


ISQ124I This ProcOps configuration is notusable

ExplanationProcessor Operations minimum requirement is to haveat least one valid target hardware definition with atleast one valid target system definition that hasselected this target hardware.

System actionISQSTART processing is aborted.

Operator responseSave the NetView log and inform the systemprogrammer.

System programmer responseLook for the following messages in the NetView log toidentify the reasons why the required ProcOpsdefinitions/tables could not be built: ISQ117I,ISQ118I, ISQ126I, ISQ127I, ISQ129I. Correct theProcOps definitions in SA policy DB and rebuild theACF for your ProcOps FP system. Refresh the SAconfiguration on this system, then issue the ISQSTARTcommand again.

ISQ127I Target hardware definition thwignored by ProcOps.

ExplanationThe ISQSTART processing detected a target hardwaredefinition with a processor connection protocol otherthan SNMP or TCP/IP. ProcOps cannot manage thisprocessor. This informational message is displayedwhen BCPii/INTERNAL processor connections andProcOps processor connections are configured to runon the same SA agent.thw

message variable containing the name of thereferenced target hardware.

System actionProcOps ignores the target hardware definition.


System programmer responseIf you want this target hardware to be managed byProcOps, specify a supported connection protocol forthe processor. Then rebuild the processor entry in thePolicy Database and refresh the ACF on the ProcOpsFP system. In order to activate the changes inProcOps, issue command ISQSTOP, followed by aISQSTART ACF command.

ISQ128I THE CONTROL FILE CONTAINS ANINCONSISTENT VERSIONIDENTIFIER.

ExplanationThis message appears in response to the ISQSTARTcommand. The control file specified in the commandhas a different version number than expected.



System actionProcessing of the ISQSTART command ends before itis complete.


System programmer responseGenerate the control file again. If doing this does notsolve the problem, verify that the installationprocedure you used is correct. Make sure that theversion of the configuration dialogs and the generatefunction you are using is the same as the version of theISQSTART command.

ISQ129I Table TARGET table-name has noentries

ExplanationThe ISQSTART processing detected that the tableidentified in this message contains no information. TheTARGET HARDWARE table is built from processorinformation and the TARGET SYSTEM table is builtfrom the available system information of the loadedACF.table-name

message variable containing the name of theempty table.



System programmer responseReview the configuration dialogs and enter all targethardware/processor information and all target systeminformation that is needed. At least one targethardware with at least one target system is required tostart ProcOps successfully. Then rebuild theprocessor/system entry in the Policy Database andrefresh the ACF on the ProcOps FP system. In order toactivate the changes, issue an ISQSTART ACFcommand.

ISQ130I THE STORED VALUE IS: value

ExplanationThis message appears in response to the ISQVARScommand. The MSG option was specified for a GET

request. value is the value of the processor operationskeyword requested.

System actionNone.



ISQ131I TOO FEW PARAMETERS HAVEBEEN ENTERED.

ExplanationThis message appears in response to the ISQXOPTcommand or the ISQVARS command. Not all of theparameters that should have been specified for thecommand were specified.


Operator responseReenter the command, making sure that all necessaryparameters are specified.


ISQ132I SECOND PARAMETER, value-entered, IS NOT VALID.

ExplanationThis message appears in response to the ISQVARScommand. The value entered for the secondparameter of the command is not valid. The validvalues for this parameter are:

• TGT• THW• LIST• GRP• OCF• LUN



System actionProcessing of the ISQVARS command ends before it iscomplete.

Operator responseReenter the ISQVARS command, making sure that thevalue of the second parameter in the command isvalid.


ISQ133I INCORRECT FORM OF COMMAND,form-used, HAS BEEN USED WITHTHE "LIST" OPTION.

ExplanationThis message appears in response to the ISQVARScommand. The LIST option was specified together withthe PUT option in the command. This is not a validform of the command. The LIST option can be usedonly if the ISQVARS command is issued from anautomation procedure and a form of the GET option isspecified.


Operator responseReenter the command, specifying a form of the GEToption with the LIST option.


ISQ134I "MSG" AND "LIST" OPTIONS AREMUTUALLY EXCLUSIVE.

ExplanationThis message appears in response to the ISQVARScommand. The command was issued with both theMSG and LIST options specified. This is not a validform of the command. Commands that contain theLIST option must be issued from an automationprocedure. Commands that contain the MSG optionoriginate from an operator.


Operator responseMake sure that an ISQVARS command that has theLIST option specified originates from a NetViewcommand list or a REXX automation procedure.


ISQ135I UNKNOWN FORM OF COMMAND,form-used, HAS BEEN ENTERED.

ExplanationThis message appears in a response to the ISQVARScommand. The command was issued with neither theGET option nor the PUT option specified. For anISQVARS command to be valid, either a form of theGET option or the PUT option must be specified.


Operator responseReenter the ISQVARS command, making sure thateither a form of the GET option or the PUT option isspecified.


ISQ136I UNBALANCED QUOTES INCOMMAND.

ExplanationThis message appears in response to the ISQVARScommand. An incorrect number of quotes were used inthe command.


Operator responseReenter the ISQVARS command, making sure that itcontains the correct number of quotes.




ISQ137I QUOTED STRING MUST BE THELAST ARGUMENT.

ExplanationThis message appears in response to the ISQVARScommand. A string of characters with quotes around itwas found in a parameter other than the lastparameter in the command. Quotes can only be usedin the last parameter of the ISQVARS command.


Operator responseReenter the command, making sure that quotes arenot used in any parameter of the command other thanthe last parameter.


ISQ138I UNABLE TO WRITE TO CALLER’SLOCAL VARIABLE, local-variable-name.

ExplanationThis message appears in response to an ISQVARScommand that includes a form of the GET option. Theinformation requested in the command has beenobtained. However, this information cannot be writtento a NetView variable (if a variable name is specified inthe command) or displayed on the console (if the MSGoption is specified in the command).


Operator responseReenter the ISQVARS command, making sure that aNetView variable is correctly specified, or that the MSGoption is correctly specified. Make sure that the MSGoption is not enclosed in quotes.


ISQ139I UNABLE TO RETRIEVE CALLER’SLOCAL VARIABLE, local-variable-name.

ExplanationThis message appears in response to an ISQVARScommand that includes the PUT option. The localvariable or literal value specified in the commandcannot be read.

System actionProcessing of the ISQVARS command ends before it iscomplete. The keyword specified in the command isnot updated with the value of a local variable or literalvalue.

Operator responseReenter the command. If you specify a local variable,make sure that its name is spelled correctly. If youspecify a literal value, make sure that it is enclosed inquotes.


ISQ140I ISQVARS PUT SUCCESSFUL.

ExplanationProcessing of the ISQVARS command completedsuccessfully.

System actionNone.



ISQ141I MSG IS A KEYWORD AND CANNOTBE USED AS A VARIABLE NAME.

ExplanationThis message appears in response to an ISQVARScommand. The term MSG was used as a variable namein the command. Because MSG is the name of anoption of the ISQVARS command, it cannot be used asa variable name.




Operator responseReenter the ISQVARS command. If you use the MSGoption, make sure that it appears in its proper positionin the command. Also, make sure that you havespecified the GET option for the command.


ISQ142I VARIABLE variable-nameTRUNCATED TO MAXIMUMLENGTH, 255.

ExplanationThis message appears in response to an ISQVARScommand. The data for the variable identified in thismessage has been collected, but it has been truncatedto 255 bytes. This occurs when the amount of datacollected exceeds 255 bytes and the ISQVARScommand was issued from a NetView command list ora high-level language other than REXX. When theISQVARS command is issued in this way, it usesNetView global variables. These variables have a limitof 255 bytes of data. This limit does not exist when theISQVARS command is issued from a REXX automationprocedure.

System actionOnly the first 255 bytes of data collected for thevariable are stored with it.



ISQ143I VARIABLE TRUNCATED TOMAXIMUM LENGTH, 32767.

ExplanationThis message appears in response to an ISQVARScommand. The data for the variable identified in thismessage was collected, but it was truncated to 32,767bytes. This occurs when the amount of data collectedexceeds 32,767 bytes and the ISQVARS command wasissued from a REXX automation procedure.

System actionOnly the first 32,767 bytes of data collected for thevariable are stored with it.



ISQ144I DYNAMIC TARGET SYSTEM SETUPSKIPPED DUE TO INVALIDPATTERN: pattern-value.

ExplanationAAO variable AOF_AAO_ISQ_DYNTGT contains a wrongor invalid pattern for creating dynamic target systemnames.

The pattern-value variable is the value defined for theAOF_AAO_ISQ_DYNTGT variable.

System actionThe ISQSTART processing continues, but all LPARentries without preset target system names areskipped from processing.


System programmer responseSet AOF_AAO_ISQ_DYNTGT to a correct pattern value.For information about the pattern, seeAOF_AAO_ISQ_DYNTGT description in IBM Z SystemAutomation Customizing and Programming

ISQ145I DYNAMIC TARGET SYSTEM target-system-name (LPARNAME: lpar-name) SKIPPED – DUPLICATEENTRY

ExplanationThe composed dynamic target system name alreadyexists. The LPAR name is displayed in the message asreference.

The target-system-name variable shows the composeddynamic target system name.

The lpar-name variable shows the LPAR name.



System actionThe ISQSTART processing continues, but the dynamictarget system is skipped from processing as targetsystem names must be unique.


System programmer responseRe-evaluate AOF_AAO_ISQ_DYNTGT pattern value tocreate unique target system names. For informationabout the pattern, see AOF_AAO_ISQ_DYNTGTdescription in IBM Z System Automation Customizingand Programming.

ISQ146I KEYWORD keyword MAY NOT SETA VALUE TO BLANKS. INTERNALDATA UNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. The command specified that the internalvariable referenced by ISQVARS keyword keywordshould be set to blanks. This internal variable cannotbe set to blanks.

System actionProcessing of the ISQVARS command ends before it iscomplete. The value of the internal variable referencedin the command is not changed.

Operator responseRefer to IBM Z System Automation Programmer'sReference for the values that the internal variablereferenced in the ISQVARS command can be set to.Reenter the ISQVARS command to set the internalvariable to a valid value.


ISQ149I STRING ENTERED, string,CONTAINS TOO MANYCHARACTERS. INTERNAL DATAUNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. An attempt was made to set the internalvariable referenced by an ISQVARS keyword to a value

containing more than the allowed number ofcharacters.

System actionProcessing of the ISQVARS command ends before it iscomplete. The value of the internal variable referencedby the keyword is not changed.

Operator responseReenter the ISQVARS command, specifying a validvalue for the internal variable referenced by theISQVARS keyword.


ISQ150I THE MAXIMUM CP DESIGNATIONSUPPORTED FOR THE processor-type IS CP-number.

ExplanationThis message appears in response to the ISQVARScommand. An attempt was made to set the internalvariable for CPx and x is a number greater than themaximum CP number supported for the processortype (processor-type). The variable CP-number showsthe greatest CP number supported by the processor.

System actionProcessing of the ISQVARS command ends before it iscomplete. No internal variable value is changed.

Operator responseReenter the ISQVARS command, specifying thekeyword for a CP that has a number supported by theprocessor type.


ISQ151I VECTORS ARE NOT SUPPORTEDON THIS MACHINE.

ExplanationThis message appears in response to the ISQVARScommand. An attempt was made to set the value of aninternal variable for a vector. (The ISQVARS keywordspecified in the command was vectorn, where n isthe number of the vector.) The processing of thecommand ends before it completes because theprocessor does not support vectors.



System actionProcessing of the ISQVARS command ends before it iscomplete. No internal variable values are changed.



ISQ152I ONLY THREE OR FOURCHARACTER ADDRESSESSUPPORTED. ENTERED VALUEWAS address.

ExplanationThis message appears in response to the ISQVARScommand. An attempt was made to set the internalvariable referenced by ISQVARS keyword dvol to avalue consisting of more than four characters. Thevalue specified for this internal variable can have amaximum of four characters.

System actionProcessing of the ISQVARS command ends before it iscomplete. No internal variable value is changed.

Operator responseReenter the ISQVARS command, specifying a validvalue with the dvol keyword.


ISQ153I PROCESSING WEIGHT OF 0 ISNOT PERMITTED.

ExplanationThis message appears in response to the ISQVARScommand. An attempt was made to set the internalvariable referenced by ISQVARS keyword lparpw to 0.The value of this internal variable must be between 1and 999 (inclusive) or it must be D (dedicated).

System actionProcessing of the ISQVARS command ends before it iscomplete. No internal variable values are changed.

Operator responseReenter the ISQVARS command, specifying a validvalue with the lparpw keyword.


ISQ161I target-hardware-name IS NOT AVALID TARGET HARDWARE NAME.

ExplanationThis message appears in response to the ISQVARS orISQIPSWT command. The target hardware specified inthe command is not defined to SA z/OS.

System actionProcessing of the ISQVARS or ISQIPSWT commandends before it is complete.

Operator responseIssue the ISQVARS or ISQIPSWT or command again,making sure that target hardware name is correct. Ifyou receive this message again in response, contactyour system programmer.

System programmer responseMake sure that the target hardware name used by theoperator is the name of a target hardware defined inthe SA z/OS configuration dialogs. If the targethardware is defined in the configuration dialogs andyou still cannot solve the problem, contact an IBMsupport representative.

ISQ162I keyword IS NOT A VALIDKEYWORD.

ExplanationThis message appears in response to the ISQVARScommand. The keyword specified in the command isnot valid.


Operator responseReenter the ISQVARS command, making sure that thekeyword is spelled correctly and that it is a validISQVARS keyword. For a list of valid ISQVARS



keywords, refer to the IBM Z System AutomationProgrammer's Reference.


ISQ163I target-system-name IS NOT AVALID TARGET NAME.

ExplanationThis message appears in response to the ISQVARScommand when the target system name specified inthe command is not valid. It also appears when theCHSTATUS is not available to a zSeries, or 390-CMOSprocessor.


Operator responseReenter the ISQVARS command, making sure that thetarget system name is correct. If you receive thismessage again in response, contact your systemprogrammer.

System programmer responseMake sure that the target system name used by theoperator is the name of a target system defined in theSA z/OS configuration dialogs. If the target system isdefined in the configuration dialogs and you stillcannot solve the problem, contact an IBM supportrepresentative.

ISQ164I path-name IS NOT A VALID PATHNAME.

ExplanationThis message appears in response to the ISQVARScommand. The path specified in the command is notvalid.


Operator responseReenter the ISQVARS command, making sure that thepath is correct. If you receive this message again inresponse, contact your system programmer.

System programmer responseMake sure that the pathname used by the operator isthe name of a processor defined in the SA z/OScustomization dialogs. If the processor is defined inthe customization dialogs and you still cannot solvethe problem, contact an IBM support representative.

ISQ166I NOT AN LPAR-MODE SYSTEM:KEYWORD IS ONLY FOR LPAR-MODE SYSTEMS.

ExplanationThis message appears in response to the ISQVARScommand. The keyword specified in the command isnot valid for the target system or port ID specified. It isvalid only for a target system running on a logicallypartitioned target hardware.


Operator responseMake sure that the target system name or the port IDand the keyword you specify in the ISQVARS commandare correct. If both are correct and you receive thismessage when you issue the ISQVARS command,contact your system programmer.

System programmer responseDetermine why there is a conflict between thekeyword used and the target system name or port IDspecified. Make sure that the definitions in the SA z/OSconfiguration dialogs were entered correctly, and makesure that the correct data set name was specified forthe ISQSTART command used to start SA z/OS.

ISQ167I CONSOLE CONNECTION port-ID ISNOT AN OPERATOR CONSOLE.

ExplanationThis message appears in response to the ISQVARScommand. The port specified in the command is notvalid for use with the keyword specified. The keywordcan only be used with a port that is connected to anoperator console.




Operator responseMake sure that the port letter and the keyword youspecify in the ISQVARS command are correct. If bothare correct and you receive this message when youissue the ISQVARS command, contact your systemprogrammer.

System programmer responseDetermine why there is a conflict between thekeyword used and the port letter specified. Make surethat the definitions in the SA z/OS configurationdialogs were entered correctly, and make sure that thecorrect data set name was specified for the ISQSTARTcommand used to start SA z/OS.

ISQ168I CONSOLE CONNECTION port-ID ISNOT A SYSTEM CONSOLE.

ExplanationThis message appears in response to the ISQVARScommand. The port specified in the command is notvalid for use with the keyword specified. The keywordcan only be used with a port that is connected to asystem console.


Operator responseMake sure that the port letter and the keyword youspecify in the ISQVARS command are correct. If bothare correct and you receive this message when youissue the ISQVARS command, contact your systemprogrammer.

System programmer responseDetermine why there is a conflict between thekeyword used and the port letter specified. Make surethat the definitions in the SA z/OS configurationdialogs were entered correctly, and make sure that thecorrect data set name was specified for the ISQSTARTcommand used to start SA z/OS.

ISQ169I THE TARGET HARDWARE IS INLPAR MODE BUT NO TARGETS AREINITIALIZED.

ExplanationThis message appears in response to the ISQVARScommand. The target hardware specified in the

command is indicated as being in LPAR mode, but noassociated target systems were initialized.




ISQ170I CANNOT LOCATE SYSTEMCONSOLE.

ExplanationThis message appears in response to the ISQVARScommand. The port definition and the target hardwaredefinition in the SA z/OS configuration dialogs conflictwith one another, making identification of the systemconsole impossible.




ISQ171I CANNOT LOCATE OPERATORCONSOLE.

ExplanationThis message appears in response to the ISQVARScommand. The port definition and target systemdefinition in the SA z/OS configuration dialogs conflictwith one another, making identification of the operatorconsole impossible.






ISQ172I "PUT" NOT ALLOWED FORKEYWORD keyword.

ExplanationThis message appears in response to the ISQVARScommand. A keyword that can only be used with aform of the GET option was specified with the PUToption.


Operator responseReenter the ISQVARS command, making sure that thecorrect keyword and PUT or GET option are specified.


ISQ174I INTERNAL LOCKING SEQUENCEERROR.

ExplanationThis message appears in response to the ISQVARScommand. Because of an internal error, the requestedinformation could not be accessed.


Operator responseSave or print a copy of the NetView log, and contactyour system programmer.


ISQ175I INTERNAL ERROR. UNABLE TOOBTAIN LOCK FOR "PUT".

ExplanationThis message appears in response to the ISQVARScommand. A NetView lock could not be obtained forthe PUT option of the command. This is an internalproblem.

System actionProcessing of the ISQVARS command ends before it iscomplete. Internal data is not changed.



ISQ176I NON-HEXADECIMALCHARACTERS ENTERED,INTERNAL DATA UNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. You tried to write (by specifying the PUToption) nonhexadecimal characters to a keyword fieldthat can contain only hexadecimal characters.

System actionProcessing of the ISQVARS command ends before it iscomplete. No internal data is changed.

Operator responseReenter the ISQVARS command, making sure that onlyhexadecimal characters (0-9, A-F) are written to thekeyword field.


ISQ177I NON-INTEGER CHARACTERSENTERED, INTERNAL DATAUNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. You tried to write (by specifying the PUToption) noninteger characters to a keyword field thatcan contain only integer characters.




Operator responseReenter the ISQVARS command, making sure that onlyinteger characters (0-9) are written to the keywordfield.


ISQ178I UNKNOWN OPERATING SYSTEMTYPE FOR TARGET target-system-name.

ExplanationThis message appears in response to the ISQVARScommand. The target system identified in thismessage is defined as having a type of operatingsystem not supported by SA z/OS.



System programmer responseMake sure that the SA z/OS control file was generatedproperly and that the correct control file data set wasspecified for the ISQSTART command.

ISQ179I TARGET target-system-name ISNOT RUNNING {MVS | VM}.

ExplanationThis message appears in response to the ISQVARS orISQXDRL command. The ISQVARS keyword specifiedin the command is not valid for the specified targetsystem. This keyword is only valid for a target systemthat is running the MVS or VM operating systems.


Operator responseReenter the command, specifying a different keywordor target system.


ISQ182I INCORRECT CHARACTERSENTERED. ONLY charactersALLOWED.

ExplanationThis message appears in response to the ISQVARScommand. You tried to write (by specifying the PUToption) values to a keyword field that are not validvalues for that field. The variable characters in thismessage shows the valid values for the field.


Operator responseReenter the ISQVARS command, making sure that onlyvalid values are written to the keyword field.


ISQ183I NUMBER ENTERED, value, TOOLARGE. INTERNAL DATAUNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. You tried to write (by specifying the PUToption) a value that is too large for the keyword fieldthat it is being written to. The variable value shows thevalue you tried to write to the keyword field.


Operator responseReenter the ISQVARS command, making sure that youspecify a value that is not too large for the keywordfield that it is being written to.


ISQ184I INCORRECT TIME, time-submitted,ENTERED. INTERNAL DATAUNCHANGED.



ExplanationThis message appears in response to the ISQVARScommand. You tried to write (by specifying the PUToption) a time offset value that is not valid. Validoffsets are:

• Integers in the range from -23 to +23 (inclusive)


Operator responseReenter the ISQVARS command, making sure that youspecify a valid time offset value.


ISQ185I parameter-value FORM NOTALLOWED FOR KEYWORDkeyword.

ExplanationThis message appears in response to the ISQVARScommand. You specified a parameter (parameter-value) that cannot be used with the keyword youspecified (keyword).


Operator responseReenter the ISQVARS command, specifying a differentkeyword or a different parameter value. Validparameter values are:

• LIST• TGT• THW• GRP• OCF• LUN


ISQ186I INCORRECT keyword STATUS,desired-value ENTERED.INTERNAL DATA UNCHANGED.

ExplanationThis message appears in response to the ISQVARScommand. You cannot change the internal variable(the ISQVARS keyword) from its current value to thevalue you specified (desired-value).

System actionProcessing of the ISQVARS command ends before it iscomplete. The value of the internal variable (ISQVARSkeyword) is not changed.

Operator responseRefer to the IBM Z System Automation Programmer'sReference to learn which changes are valid for theinternal variable (ISQVARS keyword) that you aretrying to change.


ISQ187I TARGET STATUS CANNOT BECHANGED MANUALLY FROM value.

ExplanationThis message appears in response to the ISQVARScommand. You cannot use the ISQVARS command tochange the current value (value) of the internalvariable (keyword) you specified.

System actionProcessing of the ISQVARS command ends before it iscomplete. The value of the internal variable (keyword)is not changed.

Operator responseRefer to IBM Z System Automation Programmer'sReference to learn which values can be changed andwhich values cannot be changed for the internalvariable (keyword) you are trying to change.


ISQ188I INCONSISTENT INFORMATION,CANNOT DETERMINE {target-system-name | partition-name}STATUS.



ExplanationThis message appears in response to the ISQVARScommand. The status of the target system or logicalpartition cannot be identified. This may be the result ofinternal variables having been changed through theuse of the ISQVARS command.

System actionProcessing of the ISQVARS command ends before it iscomplete. No internal variable is changed.

Operator responseRefer to the IBM Z System Automation Programmer'sReference to learn what the restrictions there are forthe internal variable (keyword) that you are trying tochange.


ISQ189I partition-name IS NOT A VALIDLOGICAL PARTITION NAME.

ExplanationThis message appears in response to the ISQVARScommand. The logical partition you specified is notdefined.


Operator responseMake sure the name of the logical partition is spelledcorrectly and that the logical partition is defined toSA z/OS.


ISQ191I QUALIFIED NAME ENTERED,name, IS NOT VALID.

ExplanationThe qualified name was not entered correctly. Thevariable name shows the name that was entered.


Operator responseReenter the command, making sure the qualified nameis entered correctly. The correct form is: target-hardware-name.partition-name


ISQ192I LPAR NAME MISSING. ONLYSYSTEM NAME, target-hardware-name, GIVEN.

ExplanationThe qualified name was not entered correctly. Thetarget hardware name was entered, but it was notfollowed by the name of a logical partition.


Operator responseReenter the command, making sure the qualified nameis entered correctly. The correct form is: target-hardware-name.partition-name


ISQ194I name IS NOT VALID TARGETNAME, BUT IS VALID TARGETHARDWARE NAME.

ExplanationThe name entered on the target form of an ISQVARScommand is not a valid processor operations targetsystem name, but it is a valid processor operationstarget hardware name.

System actionThe ISQVARS command is rejected.

Operator responseReenter the ISQVARS command, making sure thetarget system name is correct.


ISQ201I command-name: ERROR SENDINGvariable TO target-system-name



target-console-type. RESPONSEWAS: message-text.

ExplanationThe SA z/OS program received an unexpected reply(shown by message-text) to the command identified inthis message.

System actionProcessing of the command identified in this messageends before it is complete.


System programmer responseLook in the NetView log to determine what went wrongduring command processing. Correct the problem andreenter the command.

ISQ202I UNABLE TO UPDATE TARGETtarget-system-name IPL STATUS.

ExplanationThis message is generated by an SA z/OS automationroutine. The IPL status for a target system could not beupdated.

System actionNone.

Operator responseIssue the ISQSEND command.


ISQ203I target-system-name : DUPLICATE[SYSRES|VOLUME] volser FOUNDON DEVICE(S) device-address-1(AND device-address-2).OPERATOR INTERVENTIONREQUIRED.

ExplanationThis message is generated by an SA z/OS automationroutine if the following three conditions are true:

• The default response selection in the policydatabase for this target system is set to NO.

• During the IPL process one of the following wasdetected:

– A duplicate sysres condition. The operatingsystem sends one of the following messages tothe automation routine:

- Message IEA213A, if you use MVS/ESA SP V5, orOS/390

- Message IEA212A, if you use MVS/ESA SP V4, orprevious releases

– A duplicate volume condition. The operatingsystem sends one of the following messages tothe automation routine:

- IEA214A if you use MVS/ESA SP V5, or OS/390- IEA212A if you use MVS/ESA SP V4, or previous

releases• The automation routine cannot identify (in

conjunction with the reply list in the policy databasefor this target system) one device address as beingrequired.

System actionThe IPL process is suspended.

Operator responseIf a duplicate sysres condition was detected, verifythat you have booted the system from the correctdevice address. If the device address is correct, enterR 00,CONT at the operator console. The system setsthe address offline, where the duplicate sysres waslocated, and allows the IPL to continue. If the deviceaddress was not correct, restart the system with thecorrect device address (see also message IEA213A).

If a duplicate volume condition was detected,determine which of the two addresses is correct andreply to the other address, which should be set offline(R 00,dev-address). Then the IPL process continues(see also message IEA214A).

System programmer responseCheck the reply list and the default response selectionin the policy database for this target system. Thenspecify the correct values.

ISQ204I UNEXPECTED ERROR OCCURREDIN IPL FOR TARGET target-system-name. IPL FAILED.

ExplanationThis message is generated by a SA z/OS automationroutine. The IPL process failed for the target systemidentified in this message. The SA z/OS program



received one of the following unexpected MVSmessages: IEA305A, IEA310A, IEA317A, IEA320A,IEA332A, IEA906A.

System actionNone.

Operator responseCheck the NetView log to identify the MVS messagethat the automation program responded to. The replysent for this message by the automation program wasnot correct. Send the correct reply to the targetsystem, using the ISQSEND command.

System programmer responseCheck that the configuration dialogs have a correctreply for messages from the target system identified inthis message.

ISQ210I ENTITY entity_name WAS NOTLOCKED.

ExplanationThis message appears in response to the ISQOVRDand ISQXUNL commands. The port that the commandwas issued for was not locked at the time of thecommand. Processing of the command ends.

Entity names can either target-system or path names.Note that a console designator is shown in addition toa path or target-system name specification.

System actionNone.



ISQ211I task-name OWNS THE LOCK FORENTITY entity_name.

ExplanationThis message appears in response to the ISQOVRD,ISQXLOC, and ISQXUNL commands. For the ISQOVRDcommand, it indicates that the lock for the entity wasremoved and shows the last owner of the lock (task-name). For the ISQXLOC and ISQXUNL commands, itindicates that the command was not performed

because another task (task-name) owns the lock forthe entity_name.

Entity names can either target-system or path names.Note that a console designator is shown in addition toa path or target-system specification.

System actionFor the ISQOVRD command, processing completesand the lock is removed from the entity. For theISQXLOC and ISQXUNL commands, processing of thecommand ends before it is complete.

Operator responseIf you tried to issue the ISQXLOC command or theISQXUNL command, wait to issue these commandsuntil after the lock is removed from the entity_name.


ISQ212I THE LOCK FOR ENTITYentity_name HELD BY task-nameHAS BEEN REMOVED.

ExplanationThis message appears in response to the ISQOVRDand ISQXUNL commands. Processing of the commandcompleted successfully and the lock is removed fromthe entity_name.


System actionNone.



ISQ213I task-name NOW OWNS THE LOCKFOR ENTITY entity_name.

ExplanationThis message appears in response to the ISQXLOCcommand. Processing of the command completedsuccessfully.




System actionNone.



ISQ214I task-name ALREADY HAS THELOCK FOR ENTITY entity_name.

ExplanationThis message appears in response to the ISQXLOCcommand. The task that the command was issuedfrom already owns the lock for the entity that the lockwas requested for.


System actionProcessing of the ISQXLOC command ends before it iscomplete.



ISQ220I command: INCORRECT NUMBEROF PARAMETERS.

ExplanationAn incorrect number of parameters was entered.


Operator responseCheck message description and enter command again.


ISQ221I command: target-hardware-nameIS NOT A VALID TARGETHARDWARE NAME.

ExplanationThe target hardware target-hardware-name is notdefined in ProcOps.


Operator responseCheck message description and enter command again.


ISQ222I command: keyword IS NOT AVALID keyword. VALID KEYWORDSARE list-of-keywords.

ExplanationThe entered keyword keyword is not a valid keyword. Itmust be one of the list of keywords given.




ISQ223I command: target-hardware-nameIS NOT DEFINED AS PSM.

ExplanationThe target hardware, target-hardware-name, that wasentered is not of type PSM






ISQ224I command: THERE IS NO VM HOSTDEFINED FOR PSM target-hardware-name

ExplanationThere is no VM host defined for the ProcOps ServiceMachine (PSM) target hardware target-hardware-nameVM host and VM name are mandatory to issuecommands for the PSM.




ISQ225I command: THERE IS NO VM NAMEDEFINED FOR PSM target-hardware-name

ExplanationThere is no VM name defined for the ProcOps ServiceMachine (PSM) target hardware target-hardware-name.VM host and VM name are mandatory to issuecommands for the PSM.




ISQ226I command: THE VM HOST target-system-name OF PSM target-hardware-name IS NOT ACTIVE.

ExplanationThe VM host target-system-name is not active. Thecommand cannot be sent.




ISQ227I command: COMMAND target-hardware-name keywordSTATUS(status).

ExplanationThis message appears in response to the commandcommand. Processing of command keyword ended.The variable status indicates the ending status ofprocessing the command. Possible values for statusare:

• ACCEPTED• FAILED

The variable target-hardware-name shows the name ofthe target hardware associated with the command.

System actionProcessing of the command is complete.

Operator responseFor all ending status, look for other messages forfurther information.


ISQ228I command: PSM target-hardware-name STATUS(status).

ExplanationThis message appears in response to the commandcommand. The variable status indicates the status ofProcOps Service Machine (PSM) target-hardware-name. Possible values for status are:

• LOGGED ON• LOGGED OFF



• NOT DEFINED

System actionProcessing of the command command is complete.



ISQ229I command: AUTHORIZATIONERROR.

ExplanationThe user has an unsufficient authorization level for theentered command.




ISQ232I task-name HAS STARTED.

ExplanationThis message is generated by a SA z/OS automationroutine. The message monitor task task-name hasstarted.




ISQ236I command_name: OPERANDoperand IS NOT VALID FOR modeTARGET SYSTEMS.

ExplanationThe operand you entered, operand, is not valid formode target systems.


Operator responseReenter the command with an operand that issupported for the target system mode identified in thismessage.


ISQ237I COMMAND command IS NOTVALID FOR mode TARGETSYSTEMS.

ExplanationThe command you entered, command, is not valid formode target systems.


Operator responseIssue a command that is supported for the targetsystem mode identified in this message.


ISQ238I group name IS NOT A VALIDGROUP NAME.

ExplanationThis message is issued when a group name specifiedon a command is not valid.


Operator responseIssue the command again making sure that the groupname is correct. If you receive this message againcontact your system programmer.



System programmer responseMake sure the group name used by the operator is thename of a group defined in configuration dialogs. If thegroup name is defined in the dialogs, verify it has somevalid systems connected to it.

ISQ239I subgroup name IS NOT A VALIDSUBGROUP NAME.

ExplanationThis message is issued when a subgroup namespecified on a command is not valid.


Operator responseIssue the command again making sure that thesubgroup name is correct. If you receive this messageagain contact your system programmer.

System programmer responseMake sure the subgroup name used by the operator isthe name of a subgroup defined in configurationdialogs. If the subgroup name is defined in the dialogs,verify it has some valid systems connected to it.

ISQ301I &1: RETURN CODE FROM &3 WAS&2.

ExplanationThis message appears in response to the ISQCCMDcommand. It is issued whenever a nonzero return codeis returned from a process or subprocess called by thecommand. The variable &1 shows the commoncommand processed through the ISQCCMD command.


Operator responseExamine other messages that may appear for cluesabout the problem.


ISQ302I target-system-name common-command-name, KEYWORDkeyword: VALUE 'character-string'

IS NOT ALLOWED FOR HMCCONNECTED TARGETS.

ExplanationThe CTRLCONS common command was entered withTYPE(ALTERNATE), but the target system is connectedto an HMC, not to an SE.


Operator responseNone. As long as the target system is connected to anHMC, TYPE(ALTERNATE), cannot be used with theCTRLCONS common command.


ISQ303I target-system-name common-command-name, KEYWORDkeyword: THE STRING 'character-string' IS NOT A VALID VALUE.VALID VALUES ARE: value1 [,value2, value3, ...].

ExplanationAn incorrect value was specified for a keyword(identified by the variable keyword) in a commoncommand (identified by the variable common-command). Valid values for this keyword are listed atthe end of the message. The variable target-system-name shows the name of the target system that isassociated with the command.


Operator responseReenter the ISQCCMD command, making sure thatvalid values are specified for all common commandkeywords.


ISQ304I target-system-name common-command-name: THE STRINGcharacter-string IS NOT A VALIDKEYWORD. VALID KEYWORDSARE: keyword-list.



ExplanationThis message appears in response to the command. Akeyword that is not valid was found during processingof the command identified in this message. Thevariable target-system-name shows the name of thetarget system that is associated with the command.


Operator responseReenter the command, making sure that you specify avalid keyword. (The valid keywords are shown in thekeyword-list provided in this message.)


ISQ305I target-system-name common-command-name: REQUIREDPARAMETER, keyword, NOTFOUND.

ExplanationThis message appears in response to the commoncommand. A keyword that must be specified in thecommand was missing. The variable keyword identifiesthe missing keyword. The variable target-system-nameshows the name of the target system that is associatedwith the command.


Operator responseReenter the command, making sure that you specifythe required keyword.


ISQ306I target-system-name common-command-name: THEUNRECOGNIZED STRING'character-string' WAS FOUND. NOPARAMETERS ARE EXPECTED.

ExplanationThis message appears in response to the ISQCCMDcommand. A keyword was specified for a common

command that has no parameters (and, therefore,cannot contain any keywords). The variable target-system-name shows the name of the target systemthat is associated with the command.


Operator responseMake sure that you entered the correct commoncommand. If you entered the correct command,reenter it and do not specify keywords as part of thecommand.


ISQ307I LOAD: IPLPARM WAS SPECIFIEDWITHOUT IPL ADDRESS.

ExplanationThis message appears in response to the ISQCCMDcommand. The LOAD common command was issuedwith the IPLPARM keyword specified but without theIPL address.


Operator responseReenter the LOAD common command, making surethat both the IPLPARM keyword and the IPL addressare specified.


ISQ308I target-system-name common-command-name, KEYWORDkeyword: THE STRING 'character-string' IS NOT A VALID VALUE.

ExplanationAn incorrect value was specified for a keyword(identified by the variable keyword) in a commoncommand (identified by the variable common-command). The variable target-system-name showsthe name of the target system that is associated withthe command.






ISQ309I target-system-name common-command-name, KEYWORDkeyword: VALUE 'character-string'IS NOT ALLOWED FOR COMMAND'character-string'. VALID VALUESARE: value1 [, value2, value3, ...].

ExplanationAn incorrect value was specified for a keyword(identified by the variable keyword) in a commoncommand (identified by the variable common-command). The variable target-system-name showsthe name of the target system that is associated withthe command.




ISQ310I target-system-name COMMAND'command' variable-name1 'YES'NOT ALLOWED WITH variable-name2 'YES'

ExplanationThis message appears in response to the ISQCCMDICNTL or PROFILE Update command for either WLMEor PWIC to value YES. Updating WLME to YES is onlyallowed if PWIC has a value of NO and vice versa.


Operator responseEnter the PROFILE or ICNTL command to set the valueof the variable that inhibits the update (either PWIC orWLME) to a value of NO. Then reenter the failedcommand.


ISQ311I ISQCCMD: TARGET NOTSPECIFIED.

ExplanationThis message appears in response to the ISQCCMDcommand. A target system name was not specified inthe command. A target system name must bespecified. If the target was specified in the form oftarget_harware_name.lpar_name, a valid targetsystem name has not been found for this combinationof hardware and LPAR name.


Operator responseReenter the command, making sure to specifying avalid target system name ortarget_harware_name.lpar_name combination.


ISQ312I ISQCCMD: COMMAND NOTSPECIFIED.

ExplanationThis message appears in response to the ISQCCMDcommand. A common command name was notspecified in the command. A common command namemust be specified.


Operator responseReenter the ISQCCMD command, specifying acommon command name.




ISQ313I command-name: COMMANDcharacter-string NOTRECOGNIZED.

ExplanationThis message appears in response to the ISQCCMDcommand. A common command name that is not validwas specified in the command. A valid commoncommand name must be specified.


Operator responseReenter the ISQCCMD command, specifying a validcommon command name.


ISQ314I target-system-name common-command: REQUIREDPARENTHESIS NOT FOUNDFOLLOWING keyword.

ExplanationThis message appears in response to the ISQCCMDcommand. No parenthesis was found following akeyword, when the keyword must be followed by avalue that is surrounded by parentheses. The variabletarget-system-name shows the name of the targetsystem that is associated with the command.


Operator responseReenter the command, specifying a value surroundedby parentheses following the keyword.


ISQ315I target-system-name common-command: MATCHINGPARENTHESIS NOT FOUNDFOLLOWING keyword.

ExplanationThis message appears in response to the ISQCCMDcommand. Only one parenthesis was found following akeyword, when the keyword must be followed by avalue that is surrounded by parentheses. The variabletarget-system-name shows the name of the targetsystem that is associated with the command.


Operator responseReenter the command, specifying a value surroundedby parentheses following the keyword.


ISQ316I target-system-name common-command-name, MULTIPLEENTRIES OF KEYWORD keywordFOUND.

ExplanationThe same keyword was found more than once in thecommand string.


Operator responseReenter the ISQCCMD command, making sure thateach keyword only occurs once.


ISQ317I target-system-name COMMAND'command' WLME UPDATE 'YES'NOT ALLOWED, VALUE OF PWI ISOUT OF RANGE.

ExplanationThis message appears in response to the ISQCCMDICNTL or PROFILE Update command to set WLME tothe value YES. The value of PWI (initial processingweight) is outside the range that is defined by thePWMN (minimum processing weight) and PWMX(maximum processing weight) fields.




Operator responseUpdate the values for PWMN, PWMX, and PWI suchthat PWI fits in the range that is defined by PWMN andPWMX. Reenter the failed command.


ISQ318I target-system-name COMMAND'command' variable-name UPDATEVALUE LESS THAN MIN VALUE'min-value'

ExplanationThis message appears in response to the ISQCCMD'ICNTL' or 'PROFILE' Update command for a particularvariable-name. The update fails because the updatevalue is less than the allowed or defined minimumvalue.


Operator responseDepending on the variable to be updated, either enterthe PROFILE or ICNTL 'Update' command to set thevariable that defines the minimum value (for example,PWMN defines the minimum value for PWI) to anappropriate value, or change the value of the variableto be updated to a value that is greater than or equal tothe allowed minimum value. Then reenter the failedcommand.


ISQ319I target-system-name COMMAND'command' variable-name UPDATEVALUE GREATER THAN MAXVALUE 'max-value'

ExplanationThis message appears in response to the ISQCCMD'ICNTL' or 'PROFILE' Update command for a particularvariable-name. The update fails because the updatevalue is greater than the allowed or defined maximumvalue.


Operator responseDepending on the variable to be updated, either enterthe PROFILE or ICNTL 'Update' command to set thevariable that defines the maximum value (for example,PWMX defines the maximum value for PWI) to anappropriate value, or change the value of the variableto be updated to a value that is less than or equal tothe allowed maximum value. Then reenter the failedcommand.


ISQ320I UNKNOWN STATUS CODE status-code.

ExplanationAn asynchronous status change message delivered astatus code that is unknown to ProcOps.

System actionThe asynchronous status change message is notprocessed.



ISQ321I target-system-name CTRLCONSTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the CTRLCONS commoncommand ended.

• The variable status indicates the ending status ofprocessing of the command. Possible values forstatus are:

– ACCEPTED– FAILED– REJECTED



• The variable target-system-name shows the name ofthe target system that is associated with thecommand.

System actionProcessing of the ISQCCMD command is complete.

Operator responseFor all ending statuses, look for other messages thatcontain information about why processing of thecommand ended as it did.


ISQ322I target-system-name OOCODTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the OOCOD commoncommand ended.







ISQ323I target-system-name TCDATATSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the TCDATA commoncommand ended.







ISQ324I target-system-name TCMTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the TCM common commandended.









ISQ325I target-system-name too manyoccurrences for parm 'parm-name': allowed value, passedvalue.

ExplanationThis message appears in response to the ISQCCMDcommand. The command allows multiple occurrencesof the parameter parm-name, but the maximumnumber of allowed occurrences has been exceeded.

The variable target-system-name shows the nameof the target system that is associated with thecommand.

System actionProcessing of the ISQCCMD command is rejected.

Operator responseCorrect the number of occurrences of the parameterparm-name and retry ISQCCMD.


ISQ326I target-hardware-name RESERVETSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the RESERVE commoncommand ended.



• The variable target-hardware-name shows the nameof the target hardware that is associated with thecommand.




ISQ327I Image profile update for PWI notallowed if CPS value is set to 0.

ExplanationThe validation of a PWI update request failed. Theinitial processing weight value of the image profile canonly be set or changed if it has shared logicalprocessors defined. The corresponding CPS valuefound in the profile was 0.

The request is rejected. This message supplementsmessage ISQ419I.

System actionProcessing of the ISQCCMD PROFILE command endsbefore it is complete.


System programmer responseMake sure the image profile has the shared logicalprocessors defined and repeat the request.

ISQ328I ICNTL UPDATE for PWI notallowed if current PWI is 0.

ExplanationDuring the validation of an update request of theprocessing weight for a logical partition, it wasdetected that its current processing weight is 0. Thisindicates that the LPAR does not have a sharedprocessor assigned for it, which is required for aprocessing weight update.

The request is rejected. This message supplementsmessage ISQ419I.



System actionProcessing of the ISQCCMD ICNTL command endsbefore it is complete.


System programmer responseIf you are uncertain about the shared or dedicatedlogical processors that have been assigned for anLPAR, use its image activation profile on the HMC forverification.

ISQ329I target-system-name POWERMODTSTIME(time-stamp)STATUS(status)

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the POWERMOD commoncommand ended.

• The variable target-system-name shows the name ofthe target system associated with the command.

• The variable status indicates the ending status ofprocessing of the commands. Possible values forstatus are:





ISQ330I entity-name task-name statusprotocol endpoint stack-flag IP-addr lock-holder

ExplanationThis message appears in response to the ISQXCONhost-based status command for one or multiple targethardware connections. It is part of the multi-line

message ISQ350I. The meaning of the msg-fields(columns) is as follows:

• The variable entity-name indicates the processorname as defined in the SA z/OS customizationdialog.

• The variable task-name indicates the name of theprocessor operations message monitoring taskassociated with the entity-name for HW eventprocessing. A value of '*' indicates that currently notask is associated.

• The variable status indicates the current sessionstatus of the connection path to the entity. Possiblesettings are:A- Active

indicates the session endpoint connection isactive.

D- Dormantindicates the connection is not activated sincelast processor operations start or resumeoperation for this connection.

C- Closedindicates a previously active session has beenclosed or the session was set to an initial closedstatus at processor operations start time or apreviously suspended connection was resumedagain.

P- Problemindicates the connection protocol detected asession problem.

S- Suspendedindicates the connection path is suspended. Nosessions can be established to the connectionendpoint. This status can be changed only usingthe RESUME function (ISQXCON RESUME). Thestatus is valid for the processor operationsinstance for which the ISQXCON SUSPENDcommand was entered. Processor operationsstores the status using the DSISVRT NetViewVSAM DB in order to keep it persistent.

?- (undetermined)indicates the session status cannot bedetermined or an error occurred using processoroperations ISQVARS service for variable NVCS.

• The variable protocol indicates the transport protocoldefined for this connection. Possible settings are:SNMP

indicates the connection uses the services of theIBM Z SNMP APIs. The connection can be eitherTCP/IP or BCPii based.

TCPIPindicates the connection uses the socketinterfaces to communicate with a processor



operations Service Machine for VM guestsupport.

???indicates the protocol of the connection cannotbe determined.

• The variable endpoint indicates the connectionendpoint type. Possible settings are:SE

System z® Support ElementHMC

Hardware Management ConsolePSM

Processor operations Service Machine*

No endpoint, connection not active• The variable stack-flag indicates:

Y - Yesthe z/OS default IP stack is used for theconnection

N - Noanother IP address other than the default IPstack is used. Depending on the connectionprotocol, use ISQVARS variables IPSTACK orPSMIPST to determine the z/OS system-startedtask name of this IP stack.

.Connection redirected over BCPii.

BCPii redirected connections are identified withan IP address of ISQET32.xx.

• The variable IP-addr indicates the IP address in ASNnotation or hostname of the connection endpoint.For TCP/IP connections, the configured portnumbers of the PSM msg and cmd serverapplications are displayed. A value '???' is shown ifthe address information cannot be determined dueto an internal error.

The IP-addr ISQET32.xx, where xx represents anumeric value, indicates a BCPii connection. Itconnects the ProcOps focal point processor'sSupport Element with the Support Element of thetarget hardware. No customer network component isinvolved.

• The variable lock-holder is only displayed if aNetView autotask or operator holds a lock for theconnection to prevent others from using it or toserialize processing. Two lock types may be shown:( lock holder )

indicates user initiated lock set with theISQXLOC command

< lock holder >indicates internal set lock INGHWCMD/INGHWCOM

System actionNone.



ISQ332I target-system-name common-command-name: KEYWORDkeyword1 IS NOT COMPATIBLEWITH keyword2.

ExplanationThis message appears in response to the commoncommand. A keyword that is identified by variablekeyword1 cannot be used together with the keywordthat is identified by variable keyword2. The variabletarget-system-name shows the name of the targetsystem that is associated with the command.


Operator responseReenter the command, making sure that you specifythe correct keywords.


ISQ333I target-system-name common-command-name: OPTION option ISREQUIRED FOR keyword.

ExplanationThis message appears in response to the commoncommand. An option that must be specified in thecommand was missing. The variabletarget_system_name shows the name of the targetsystem that is associated with the command.




Operator responseReenter the command, making sure that you specify arequired option. (The required option is shown in thevariable option that is provided in this message.)


ISQ334I target-object SECLOGTSTIME(time-stamp)STATUS(status)

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the SECLOG commoncommand ended.

• The variable target-object shows the name of thetarget system or target hardware that is associatedwith the command.






ISQ335I target-system-name STPDATATSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the STPDATA commoncommand ended.


– ACCEPTED

– FAILED– REJECTED





ISQ336I target-system-name STPTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the STP common commandended.







ISQ337I The SECLOG status for thw_nameis seclog_status



ExplanationThis message appears in response to the SECLOGcommon command of ISQCCMD.

• The variable thw_name shows the name of the targethardware that is associated with the command.

• The variable seclog_status indicates if Security Logmessages from the connection endpoint areforwarded to Processor operations. Depending onthe configuration, the connection endpoint can beeither a processor Support Element (SE) or aHardware Management Console (HMC):

ON - Security Log message forwarding is activeOFF - Security Log message forwarding is inactive




ISQ350I CONNECTION STATUS SUMMARY

ExplanationThis is the header message of a multi-line messagereturned in response to the ISQXCON STATUScommand. After this header line one or multipleISQ330I messages are following. Message ISQ355Icloses the multi-line message.

System actionNone.



ISQ351I THE req FOR ent FAILED. HWcmdRC: hwrc

ExplanationThe ISQXCON function request req for the specifiedentity ent failed. hwrc contains the hardware functionreturn code. The req can be either SUSPEND orRESUME.

System actionThe function ends before it is complete.

Operator responseInform the System Programmer.

System programmer responseUse command AOCTRACE ISQXCON,ON to enable thedebug mode and repeat the request. Contact IBMService and have the NetView log with the debuginformation available if this error still occurs.

ISQ352I TOO MANY PARAMETERS HAVEBEEN ENTERED.

ExplanationThe specified command includes too manyparameters.


Operator responseReenter the command, specifying the correct numberof parameters.


ISQ353I TARGET NAME ENTERED, target-system-name, CONTAINS TOOMANY CHARACTERS.

ExplanationThe target system name specified in the command hastoo many characters.


Operator responseReenter the command, specifying the correct targetsystem name.




ISQ354I VIEW COULD NOT PRESENTPANEL panel-name. VIEW RETURNCODE = return-code.

ExplanationThe panel identified in this message could not bedisplayed using the NetView VIEW command. TheNetView VIEW command is issued automaticallyduring SA z/OS processing to display a panel.

System actionProcessing of the command to display a panel endsbefore it is complete.

Operator responseWrite down the name of the panel that could not bedisplayed and the return code. Contact your systemprogrammer.

System programmer responseTry to identify the problem by examining the panel thatcould not be displayed. Refer to the description of theVIEW command in NetView Customization Guide for adescription of the return code displayed with thismessage.

ISQ355I END OF CONNECTION STATUSSUMMARY

ExplanationThis is the closing message of multi-line messageISQ350I returned in response to the ISQXCON STATUScommand.

System actionNone.



ISQ356I ISQXCON PARAMETER ERROR:parameter_error_information

ExplanationThe ISQXCON parameter specification is incorrect.parameter_error_information can be one of thefollowing:

Unknown command specifiedThe ISQXCON sub-commands can be: STATUS,SUSPEND, or RESUME.

Not a valid target hardware nameThe specified target hardware name is not definedto the Operator Operations in the SA z/OS policydatabase.

No matching target hardware name foundThe target hardware name was specified usingwildcard option *, but no match was found.

Command allows no optionsThe ISQXCON sub-command STATUS has nooptions.

FORCE option is invalidThe ISQXCON sub-command SUSPEND FORCE orRESUME FORCE is incorrectly specified.

System actionThe function ends before it is complete.

Operator responseCorrect the parameter error and repeat the command.


ISQ357I SESSION TO thw IS ACTIVE ANDFORCE IS NOT SPECIFIED.REQUEST IGNORED.

ExplanationThe ISQXCON SUSPEND request to the specified targethardware requires the FORCE option to be specifiedbecause there are still one or more target systemsessions active, using the connection.

System actionThe request for the target hardware thw specified inthe message ends before it is complete.

Operator responseRepeat the SUSPEND with the FORCE option to closeall target systems of that target hardware usingISQXCLS first.




ISQ358I CONNECTION STATUS OF thwMUST BE SUSPENDED. REQUESTIGNORED.

ExplanationThe ISQXCON RESUME request can only be processedfor the specified target hardware if its connection pathstatus is SUSPENDED.

System actionThe request for the target hardware specified in themessage ends before it is complete.

Operator responseRepeat the RESUME request if the connection path tothe target hardware has the correct status.


ISQ359I CONNECTION TYPE ctype TO thwNOT SUPPORTED. REQUESTIGNORED.

ExplanationThe connection protocol ctype is not supported byISQXCON.

System actionThe request for the target hardware thw specified inthe message ends before it is complete.



ISQ400I entity-name UNKNOWNTSTIME(time-stamp)STATUS(REJECTED).

ExplanationThis message appears in response to the ISQCCMDcommand. The common command specified within theISQCCMD command could not be processed correctly.The variable entity-name shows the name of the targetentity associated with the command that is unknown.

For more information about the supported target entitytypes for common commands, refer to the ISQCCMDhelp.


Operator responseLook for earlier messages to indicate the reason forthe problem.

System programmer responseIf the ISQCCMD was used to perform an LPARManagement request over an SA-BCPii connection,make sure that a target system is defined that has thetargeted processor and LPAR assigned. Note that thistarget system must also be a member of an SA group(SYSPLEX/STANDARD). Correct your PDB whenneeded and re-build your SOCNTL/ACF file. Refreshyour active configuration and retry the ISQCCMD.

ISQ401I target-system-name ACTIVATETSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the ACTIVATE commoncommand ended.









ISQ402I target-system-name DEACTIVATETSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the DEACTIVATE commoncommand ended. The variable status indicates theending status of processing of the command. Possiblevalues for status are:

• ACCEPTED• FAILED• REJECTED

The variable target-system-name shows the name ofthe target system associated with the command.




ISQ403I ccmd common command notallowed for PSMs.

ExplanationThis message appears in response to the ISQCCMDcommand. The ccmd common command was issuedfor a ProcOps Service Machine (PSM). In the context ofVM Second Level System support this command canonly be used for a PSM.




ISQ407I target-system-name LOADTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the LOAD common commandhas ended. The variable status indicates the endingstatus of processing of the command. Possible valuesfor status are:






ISQ408I target-system-name RESTARTTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the RESTART commoncommand ended. The variable status indicates theending status of processing of the command. Possiblevalues for status are:








ISQ409I target-system-name CBUTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the CBU common commandended. The variable status indicates the ending statusof processing of the command. Possible values forstatus are:


The variable target-system-name shows the name ofthe target system associated with the command. If thecommon command was entered with a target-hardware-name, the first target-system-name found inthe list of target systems associated with thishardware is shown.




ISQ410I target-system-name STARTTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the START commoncommand ended. The variable status indicates theending status of processing of the command. Possiblevalues for status are:






ISQ411I target-system-name STOPTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the STOP common commandended. The variable status indicates the ending statusof processing of the command. Possible values forstatus are:






ISQ412I CPC function function-name is notavailable with connection typetype.

ExplanationThe hardware function function-name is not availablewith a SNA based NetView connection (NVC) to yourCPC or a TCPIP based connection (TCPIP) to yourProcOps Service Machine (PSM).



System actionProcessing of the ISQCCMD command ends.

Operator responseRefer to the ISQCCMD common commanddocumentation to get the information about thesupported connection types for this request.


ISQ413I target-system-name EXTINTTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the EXTINT commoncommand ended. The variable status indicates theending status of processing of the command. Possiblevalues for status are:






ISQ414I target-system-name SYSRESETTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the ISQCCMDcommand. Processing of the SYSRESET commoncommand ended. The variable status indicates theending status of processing of the command. Possiblevalues for status are:

• ACCEPTED

• FAILED• REJECTED


System actionProcessing of the ISQCCMD command complete.



ISQ415I ccmd COMMAND CANCELLED.

ExplanationThe NetView operator canceled the commoncommand ccmd


Operator responseReenter the command if desired.


ISQ416I FAILURE ISSUING ccmdCOMMAND. RETCODE=ccmd_rc

ExplanationYour attempt to issue the common command ccmdfailed. The NetView RUNCMD command received anonzero return code rc.


Operator responseReenter the command.



System programmer responseDetermine the reason for the failure. Possiblemeanings of nonzero return codes are:4

The RUNCMD command failed or no response wasreturned

16The command was canceled by the CANCMDcommand

24Some command list data was truncated

28The service point application returned more than132 responses for the RUNCMD

32COS command timeout exceeded (specified inNetView Constants module)

ISQ417I ccmdSTATUS(ccmd_completion_status)CONDITION(cond_code)SDATA(sense_data)

ExplanationThe specified status was received from the target inresponse to a common command ccmd. For an NVCconnection refer to the section "OperationsManagement Condition Code Reference" in S/390Managing Your Processors (GC38-0452) forinformation on operations management conditioncodes. For connection types other than NVC refer toAppendix B, “Response Messages, Error Strings,Condition Codes,” on page 537.

System actionIf ccmd_completion_status is SUCCESS, the commoncommand ccmd was processed at the target. Ifccmd_completion_status is FAILED, the status field willbe followed by a CONDITION and possibly SDATAfields detailing the reason for the failure. It will also befollowed by a text explanation describing the failure.Both of these messages will appear in SA z/OS statuspanels for the most recent events.

Operator responseNone. This is an informational message only.

System programmer responseNone. This is an informational message only.

ISQ418I PROFILE NOT KNOWN ONthwname

ExplanationA common command that was previously issuedspecified a profile name that was unknown at thedestination target hardware thwname. This messagesupplements message ISQ417I or ISQ419I.


Operator responseCheck the profile names associated with the targethardware thwname. Profile names that are used ascommon command parameters must exist on thetarget hardware Support Element.

System programmer responseMake sure that an existing activation profile name isused with the common command. Note that thespecified profile name must be of type RESET or LOADfor the CCNTL common command.

ISQ419I ISQCCMD ccmd PROCESSING ONthwname IS COMPLETE.

ExplanationProcessing of the common command ccmd iscomplete. The target hardware thwname is now readyto process new requests. This message supplementsmessage ISQ417I.




ISQ420I FUNCTION CANNOT BEPERFORMED IN PRESENT STATEOF THE TARGET HARDWARESYSTEM.

ExplanationThe target is in an incompatible mode to process thecommand. This message supplements messageISQ417I.




Operator responseReexamine the command in relation to the state of thetarget. Reenter the common command, specifying thecorrect target.

System programmer responseReenter the common command, specifying the correcttarget.

ISQ421I OPERATIONS MANAGEMENT ISNOT ENABLED ON thwname

ExplanationThe support element at the target hardware namethwname is not enabled to perform operationsmanagement commands. Ensure that the supportelement at the target is enabled for operationsmanagement from the hardware system console. Thismessage supplements message ISQ417I.



System programmer responseEnable operations management at the target hardwaresystem console.

ISQ422I COMMAND NOT SUPPORTED.

ExplanationThe target support element does not support theoperations management command. This messagesupplements message ISQ417I.


Operator responseEnsure that the command is a supported operationsmanagement command. Reenter the command,specifying a supported common command.

System programmer responseReenter the command, specifying a supportedcommon command.

ISQ423I INCORRECT AUTHORIZATIONCODE FOR thwname

ExplanationThe authorization token supplied on the previouscommand sent to the target hardware name thwnamewas rejected by the target. This message supplementsmessage ISQ417I.

System actionThe associated command is rejected.


System programmer responseVerify that the correct operations managementauthorization token was defined for the NetViewConnection associated with this target hardware.Correct the operations management authorizationtoken and reenter the command.

ISQ424I TARGET SYSTEM RESOURCESBUSY. ccmd COMMAND WILL BERETRIED.

ExplanationSystem resources at the target are temporarily busy,and the target hardware cannot act on the request.This message supplements message ISQ417I.

System actionThe command will be retried once.



ISQ425I TARGET SYSTEM RESOURCESBUSY. ccmd COMMAND FAILED



ExplanationSystem resources at the target are busy; the receiver isunable to process the requested command after beingretried. The command is not processed.


Operator responseReenter command when the target support element isavailable. If this response appears again, contact yoursystem programmer.

System programmer responseIf the problem persists, contact an IBM servicerepresentative.

ISQ426I SYSTEM IS RUNNING. FORCE(YES)MAY BE NEEDED ON target_name

ExplanationA disruptive common command was issued to anoperational target system or target hardware,target_name, without FORCE(YES) specified. Thecommand failed. This message supplements messageISQ417I.


Operator responseDetermine whether the target really is meant to bedisrupted. If so, reenter the command with theFORCE(YES) parameter.

System programmer responseDetermine whether the target really is meant to bedisrupted. If so, reenter the command with theFORCE(YES) parameter.

ISQ427I CPC thwname IS NOT POWEREDON

ExplanationA common command that requires a powered-ontarget hardware was issued to target hardwarethwname, which was powered off.


Operator responseEnter the ACTIVATE common command to theappropriate target system, then reenter the originalcommand, if necessary.


ISQ428I POWER-ON RESET NOT COMPLETEON thwname

ExplanationA common command that requires power-on reset tobe complete was issued to target hardware thwname,which was in the “power-on reset required” state. Thismessage supplements message ISQ417I.

System actionThe command failed.

Operator responseDetermine the cause of the failure on the targethardware thwname that caused the target to bepower-on reset required. Enter an ACTIVATEcommand, then reenter the original commoncommand.


ISQ429I SEND A STOP COMMAND, THENRESEND THE ORIGINAL REQUEST

ExplanationThe target system support element is unable toperform the common command because the targetedCPU is not in the stopped state. This messagesupplements message ISQ417I.

System actionThe processing of the command ends before it iscomplete.



Operator responseEnter the STOP common command, then reenter theoriginal command, specifying the correct targetsystem.


ISQ430I HARDWARE ERROR. ccmdCOMMAND WILL BE RETRIED

ExplanationThe common command ccmd failed due to a hardwareerror at the target. The command will be retried once.This message supplements message ISQ417I.

System actionThe command is retried.



ISQ431I HARDWARE ERROR. ccmdCOMMAND FAILED.

ExplanationThe common command ccmd failed due to a hardwareerror at the target a second time. This messagesupplements message ISQ417I.



System programmer responseCheck the NetView hardware monitor for generic alertswith this problem. Analyze the hardware systemconsole information.

ISQ432I LOCAL OPERATOR OR ANOTHERAPPLICATION IS IN CONTROL OFtarget_system_name

ExplanationA local operator or another systems managementapplication has obtained exclusive control of the targetsystem. This prevents use ofSA z/OS status data thatmay not be up-to-date and the acceptance by thehardware of SA z/OS common commands. Thismessage supplements message ISQ417I.

System actionThe processing of the command ends before it iscomplete. The target has been unconditionallyreserved.

Operator responseCommands may be reentered to the target when thetarget is released by the local operator.

Programmer responseNone.

ISQ433I Insufficient CPs to completeACTIVATE request

ExplanationAn ACTIVATE common command failed due toinsufficient CPs at the target. This messagesupplements message ISQ417I.

System actionThe processing of the ACTIVATE command endsbefore it is complete.


System programmer responseVerify that the number of dedicated CPs specified inthe profile used with the ACTIVATE command does notexceed the number of physical processors at the targethardware.

ISQ434I ONE OR MORE CHANNEL PATHSARE IN ERROR <chpid-numbers>

ExplanationThe CHPID numbers, chpid-numbers, were found to bein error during processing of the command. They weredefined in the CHPMAP operand of the image profile.This message supplements message ISQ417I.





System programmer responseDetermine the cause of the channel path error andcorrect the problem.

ISQ435I INSUFFICIENT AMOUNT OF MAINSTORAGE TO PROCESS ACTIVATEREQUEST

ExplanationAn ACTIVATE Common Command failed due toinsufficient main storage at the target. This messagesupplements message ISQ417I.



System programmer responseVerify that the amount of main storage defined in theprofile used with the ACTIVATE request does notexceed the amount of main storage available at thetarget hardware.

ISQ436I INSUFFICIENT AMOUNT OFEXPANDED STORAGE TO PROCESSACTIVATE REQUEST

ExplanationAn ACTIVATE common command failed due toinsufficient expanded storage at the target. Thismessage supplements message ISQ417I.



System programmer responseVerify that the amount of expanded storage defined inthe profile used with the ACTIVATE request does notexceed the amount of expanded storage available atthe target hardware. Determine the cause of a storageerror if the profile is correct.

ISQ437I NO S/390® CHANNELS ARECONFIGURED TO THIS LOGICALPARTITION

ExplanationA common command was issued to a logical partitionthat does not have any channels configured. Thismessage supplements message ISQ417I.



System programmer responseConsult System/390® hardware documentation toproperly configure the channels. After configuring thechannels, reenter the common command

ISQ438I ERROR IN SPECIFICATION OFCENTRAL STORAGE ORIGIN

ExplanationActivation of a target was requested with an incorrectcentral storage origin specified.



System programmer responseDetermine the cause of the storage error. Reenter thecommon command after specifying the central storageorigin.

ISQ439I REQUEST FOR CENTRAL STORAGECANNOT BE SATISFIED



ExplanationThe common command did not complete because thetarget hardware was unable to satisfy the command’simplicit request for central storage. The activationprofile identified in the CNAME parameter requestedan amount of central storage that would have includedthe hardware system area (HSA). This messagesupplements message ISQ417I.



System programmer responseDetermine the correct storage request. Reenter thecommon command after correcting the storagespecification.

ISQ440I A RESOURCE REQUIRED BY ALOGICAL PARTITION WAS NOTDEFINED

ExplanationA required resource for the logical partition was notdefined in the associated profile. This messagesupplements message ISQ417I.



System programmer responseVerify that the Image Profile for the logical partitionagrees with the available resources.

ISQ441I A REQUESTED RESOURCE IS NOTAVAILABLE TO SATISFY THEACTIVATE REQUEST

ExplanationA resource error exists that may indicate aconfiguration problem or insufficient resources toprocess the command. This message supplementsmessage ISQ417I.



System programmer responseDetermine the required resource and correct the error.Check SDATA code, if any, to identify the specificresource error.

ISQ442I COMMAND ccmd NOTSUCCESSFUL ON target_name

ExplanationThe common command ccmd was not successful onthe target system or target hardware target_name.This message supplements message ISQ417I.



System programmer responseDetermine the reason for the failure from the conditionreport code and sense data (SDATA) information in thecommand response.

ISQ443I SYSRESET HAD QUALIFIEDSUCCESS:qualification_information

ExplanationThe common command SYSRESET was partiallysuccessful. Possible qualification_information is:

• “Check PU status”• “Check I/O status”• “Check both PU and I/O status. An IOP re-IML

(power-on reset) is in progress.”• “Sense data = ‘nnnnnnnn’”.

This message supplements message ISQ417I.

System actionProcessing of the SYSRESET command is complete.




System programmer responseThe instructions given by the processor’s built-inproblem analysis facilities may provide additionalinformation. If not, refer to 390-CMOS, or zSeriesManaging Your Processors.

ISQ444I ACTIVATE HAD QUALIFIEDSUCCESS. SUCCESSFUL STEPCODE: step_number

ExplanationThe target system support element partiallycompleted the ACTIVATE request. step_number is a bitmap returned to indicate how far the ACTIVATEprocess completed.

System actionProcessing of the ACTIVATE command is complete.

Operator responseSee your system programmer.

System programmer responseThe instructions given by the processor’s built-inproblem analysis facilities may provide additionalinformation. If not, refer to 390-CMOS or zSeriesManaging Your Processors.

ISQ445I ACTIVATE THE LOGICALPARTITION AND RESEND THEREQUEST.

ExplanationThe target system support element is unable toperform the command because the target system is inthe deactivated state.


Operator responseEnter an ACTIVATE common command to the targetsystem, then reenter the original command.


ISQ446I COMMAND ISSUED: ccmdccmd_parameters

ExplanationThe common command ccmd was issued in themessage with the parameter shown.

System actionNone.

Operator responseThis is an informational message only.

System programmer responseThis is an informational message only.

ISQ447I ALERT RECEIVED ON thwname.CPC HARDWARE FAILURE.

ExplanationAn alert was received for target hardware thwnameindicating that there was a CPC hardware failure at thetarget. More information about the type of failure canbe seen in the second line of the "Last SignificantMessage" field of the "Target Hardware" panel. Use theNetView NPDA panels to get more information aboutthe alert.

System actionThe target hardware status is updated.



ISQ448I ALERT RECEIVED ON thwname:STORAGE SUBSYSTEM FAILURE.

ExplanationAn alert was received for target hardware thwnameindicating that there was a storage subsystem failure.More information about the type of failure can be seenin the second line of the "Last Significant Message"field of the "Target Hardware" panel. Use the NetViewNPDA panels to get more information about the alert.



System actionA processor operations target hardware failure alert isgenerated.



ISQ449I ACTIVATE had qualified success.Sense Data = nnnnnnnn

ExplanationAn ACTIVATE common command completed at thetarget system, but there were some errors that areidentified by the code in sense data. This messagesupplements message ISQ417I.

System actionThe ACTIVATE command partially completes.


System programmer responseRefer to 390-CMOS or zSeries Managing YourProcessors for SDATA sense data information.Determine the reason for the errors that are indicatedin the SDATA sense data information. Examine theSDATA code to determine whether action is required.

ISQ450I ALERT RECEIVED {on thwname|FORtarget_system_name}:PROCESSORENTERED HARD WAIT

ExplanationAn alert was received for target hardware thwnameindicating that one or more processors loaded adisabled wait.

System actionThe target attention status is updated.


System programmer responseFor System z processors more information about thealert may be available in the NetView log if a targetsystem, which is initialized to processor operations, isaffected by the disabled wait. Look for ISQ900Imessages which include a GETIPSW response reportAOFA0025.

ISQ451I ALERT RECEIVED ON thwname.INVALID PASSWORD.

ExplanationAn alert was received for target hardware thwnameindicating that an operator entered an incorrectpassword. More information about the type of failurecan be seen in the second line of the "Last SignificantMessage" field of the "Target Hardware" panel. UseNetView NPDA panels to get more information aboutthe alert.

System actionThe System Console logon is disallowed.


System programmer responseUse NetView NPDA panels to get more informationabout the alert. Follow the instructions given by theprocessor’s built-in problem analysis facilities.Otherwise, use normal support channels for problemdetermination or contact an IBM supportrepresentative.

ISQ452I UNRECOGNIZED PROFILE NAMESPECIFIED IN THE AUTOACTOPERAND OF THE RESET PROFILE

ExplanationThe profile name specified in the AUTOACT operand ofthe Reset profile that was specified on the ACTIVATEcommon command was not recognized by thereceiving support element at the target hardware. Thismessage supplements message ISQ417I.

System actionACTIVATE common command is rejected.




System programmer responseExamine the Reset profile that was specified by theACTIVATE command. Correct the profile namespecified in the AUTOACT operand of the Reset profile,or define the profile if necessary.

ISQ453I TIMED COMMAND REJECTEDBECAUSE TIMED OPERATIONSQUEUE IS FULL

ExplanationThe OCF timed operations queue at the target supportelement is currently full, and the most recent timedcommand cannot be accepted for future processing.This message supplements message ISQ417I.

System actionThe timed command is rejected.


System programmer responseRefer to 390-CMOS or zSeries Managing YourProcessors for information.

ISQ454I TIMING WINDOW SPECIFIED INCOMMAND REQUEST HASEXPIRED. REQUEST WILL NOT BEHONORED.

ExplanationThe current request specified a window of time forprocessing (using the XATIME, XBTIME operands) thathas already expired. The request cannot be carriedout. This message supplements message ISQ417I.

System actionThe timed command rejected.

Operator responseExamine the XATIME and XBTIME operands specifiedon the common command. Reenter the command witha valid timing window.


ISQ455I INVALID XATIME OPERAND

ExplanationThe common command was issued with an XATIMEoperand that is incorrect.


Operator responseDetermine the proper form of the XATIME operand.Correct the XATIME operand and reenter thecommand.


ISQ456I INVALID XBTIME OPERAND

ExplanationThe common command was issued with an XBTIMEoperand that is incorrect.


Operator responseDetermine the proper form of the XBTIME operand.Correct the XBTIME operand and reenter thecommand.


ISQ457I INVALID INTERVAL OPERAND

ExplanationThe common command was issued with an INTERVALoperand that is incorrect.




Operator responseDetermine the proper form of the INTERVAL operand.Correct the INTERVAL operand and reenter thecommand.


ISQ458I INVALID COUNT OPERAND

ExplanationThe common command was issued with a COUNToperand that is incorrect.


Operator responseDetermine the proper form of the COUNT operand.Correct the COUNT operand and reenter thecommand.


ISQ459I COMPLETION REPORT FORCOMMAND ccmd RECEIVED.STATUS(cmd_status)COND(cmd_cond) SDATA(sdata)

ExplanationCompletion of a previously issued timed request orcompletion of an ACTIVATE for a logical partition whena nontimed ACTIVATE request has been sent to aprimary OCF. Refer to S/390 Managing Your Processorsfor information on operations management conditioncodes.

System actionIf ccmd_completion_status is SUCCESS, commoncommand ccmd was processed at the target. Ifccmd_completion_status is FAILED, the status field willbe followed by a CONDITION and possibly SDATAfields detailing the reason for the failure. It will also befollowed by a text explanation describing the failure.Both of these messages will appear in processoroperations status panels for the most recent events.

System actionThe ACTIVATE command is complete.

Operator responseIf ccmd_completion_status is FAILED, refer to the textexplanation of the failure.

System programmer responseThis is an informational message only.

ISQ460I ALERT RECEIVED ON thwname.SUPPORT ELEMENT FAILURE

ExplanationAn alert was received for target hardware thwnameindicating that the support element failed. Remoteoperations to the affected targets may no longer bepossible

System actionNone.


System programmer responseRefer to 390-CMOS or zSeries Managing YourProcessors for information.

ISQ461I TARGET SYSTEMtarget_system_name EXISTS BUTIS NOT INITIALIZED.INITIALIZATION IS BEINGREQUESTED.

ExplanationActivation of a target system has caused activation ofanother target system on the same target hardware.This can occur on OCF-based processors if the Resetprofile specifies that multiple LPARs should beactivated.

System actionProcessor operations automatically initializes theadditional target systems being activated by ISQXIIIand updates their status.





ISQ462I TARGET SYSTEMtarget_system_name ISINITIALIZED BUT IS NO LONGERACTIVE. CLOSE PROCESSING ISBEING REQUESTED.

ExplanationProcessor operations has detected that a targetsystem is initialized but is not the target systemrunning on the target hardware. This can occur onOCF-based processors if a basic mode target systemhas been initialized, but the target hardware is nowrunning in LPAR mode.

System actionProcessor operations automatically closes the targetsystem using ISQXCLS.



ISQ463I CBU REQUEST FORtarget_hardware_name CANNOTBE EXECUTED. CONDITION CODE:cond_code

ExplanationThe ISQCCMD CBU command for the named targethardware cannot be executed because of the conditionshown in cond_code. Refer to IBM Z SystemAutomation Messages and Codes for a list of thepossible condition codes and their meaning.

System actionThe CBU request is not executed. ISQCCMDprocessing terminates with a reject messages.

Operator responseCheck whether the CBU request has been issued forthe correct hardware. Usually this message isdisplayed when a ACTIVATE, TESTACT, or UNDO CBUcommand is requested, but the CBU feature is notinstalled. Use the CBU STATUS command to determinethe current CBU status for this target hardware.

System programmer responseIf your hardware has CBU installed and enabled,contact IBM system support.

ISQ464I CBU DATA OFtarget_hardware_name IS:cbu_information

ExplanationThis message is the response to an ISQCCMD CBUCMD(STATUS) command.The cbu_information stringcontains the current status of the target hardware CBUfeature. If the feature is installed, additionalinformation, depending on the actual status isdisplayed. This information is: CBU activation andexpiration dates, and number of test activations left foruse.

System actionNone. Informational message only.



ISQ468I CCNTL error on thwname. Cannotaccess activation profiles.

ExplanationA common command that was previously issuedspecified a profile name that could not be validated.Access to the Support Element profiles failed. Thismessage supplements message ISQ419I.



System programmer responseUse the PROFILE common command to test theaccess to the activation profiles of the target hardwarethwname. If there are problems with the access, makea note of the condition codes that are displayed andcontact an IBM support representative.



ISQ505I ISQCMON COMMAND COMPLETE,CONDITION=result-of-command.

ExplanationProcessing of the ISQCMON command is complete andit has resulted in one of the following result-of-command conditions:add user

The user who issued the command is added to theSA z/OS control group.

del userThe user who issued the command is removedfrom the SA z/OS control group.


Operator responseIf necessary, reenter the command.


ISQ511I debug_information_text

ExplanationISQ511I prefixes all ProcOps main debug messages.These messages are issued permanently, if ProcOpswas started or is currently running in DEBUG mode. Inaddition, ISQ511I messages may be issueddynamically, in case of networking or ProcOpsundetermined internal processing problems, as adebug aid. Note that in such cases, only few ISQ511Imessages are issued.

The debug_information_text is text data containingstatically or dynamically determined informationrelated to the current executed ProcOps function orcalled services.

System actionProcessing of the command or function continues.

Operator responsePermanent debug messages can be disabled by usingthe Debug Off or Debug On toggle option (PF5) ofISQXDST dialog panel ISQESUM.

System programmer responseIn case of networking problems, the debuginformation text may contain TCP/IP relatedinformation, such as service names and return codesor error information.

ISQ527I ISQCMON PARAMETER NOTRECOGNIZED.

ExplanationThis message appears in response to the ISQCMONcommand. The command was issued with an optionother than ON or OFF.

System actionProcessing of the ISQCMON command ends before it iscomplete.

Operator responseReenter the ISQCMON command, to make sure thatyou specify either ON or OFF.


ISQ531I target-hardware-name command-name TSTIME(time-stamp) ENDEDRETURN CODE (return-code).

ExplanationThis message appears at the end of processing acommand.

The variable target-hardware-name shows thename of the target hardware that is associated withthe command.The variable command-name indicates thecommand executed.The variable return-code indicates the commandending return code.

System actionProcessing of the command-name commandcompletes.





ISQ535I path-name port-id STATUS IS lock-status BY task-name.

ExplanationThe task that is identified in this message eitherobtained or released the lock for the port that isidentified in the message. This message can be usedas a key for non-SA z/OS automation routines.

System actionNone.



ISQ536I COMMAND: cmd-name LOCATION:loc-name RECEIVED RC: cmd-rcFROM: called-cmd

ExplanationA command called from a processor operations routinehas returned an unexpected return code.

The variable cmd-name shows the processoroperations command name or module name thatwas running.The variable loc-name shows the location withincmd-name where the problem occurred.The variable cmd-rc shows the unexpected returncode issued from called-cmd.The variable called-cmd shows the name of thecommand and, optionally, the parameters of thecommand that returned the unexpected returncode.


Operator responseWrite down the information shown in this message.Also, save or print a copy of the netlog and contactyour system programmer.


ISQ537I COMMAND: cmd-name RECEIVED:excptn FROM: source DATA: error-data

ExplanationA processor operations command encountered anunexpected exception.

The variable cmd-name identifies the processoroperations command name or module name thatwas running.The variable excptn identifies which type of erroroccurred.The variable source indicates where the error mayhave originated from.The variable error-data contains data that may helpwith the problem resolution.


Operator responseSave or print a copy of the netlog and contact yoursystem programmer.

System programmer responseTry to determine the cause of the problem with thehelp of the information given in excptn. One possibleexception is:

INVALID_DATA_0001: An incorrect message wasreceived. Specifically, a line of data received from aSupport Element (SE) was expected to containeither a CPC name or an LPAR name and hadneither. The processor operations target hardwarename for the SE is given in source and the line ofdata in error is repeated in error-data. This problemcan occur in CPCs with more than ten CPUs if theLicensed Internal Code (LIC) in the SE is not up-to-date. Check this with your IBM customer engineer.

If the cause of the problem cannot be determinedcontact an IBM support representative.

ISQ600I PROCESSOR OPERATIONSCOMMAND CAN NOT BE ISSUEDTO THE SPECIFIED GROUP ORSUBGROUP.

ExplanationThis message is issued when a group or subgroup hasbeen specified that is not valid for ProcessorOperations commands.



System actionSpecified action will not be taken.

Operator responseSpecify the correct group or subgroup for theProcessor Operations command. If you want to issue acommand to the specified group or subgroup, youmust update the configuration dialogs.


ISQ602I PROC-OPS AUTOMATION TABLEPROCESSING OPTION tpo ISINVALID.

ExplanationDuring ISQSTART or ISQSTOP processing, theProcessor Operations-related automation table datawas processed using option value tpo, which is notvalid. The valid options are START or STOP.

System actionThe ISQSTART or ISQSTOP processing terminates.


ISQ603I PROC-OPS AUTOMATION TABLE ISALREADY tblstat.

ExplanationDuring ISQSTART or ISQSTOP processing, theProcessor Operations-related automation table datawas found already in the desired state. Automationtable state tblstat values are 'activated' for ISQSTARTand 'stopped' for ISQSTOP.

System actionThe ISQSTART or ISQSTOP processing continues.



ISQ604I PROC-OPS AUTOMATION TABLEtblaction FAILED.

ExplanationDuring ISQSTART or ISQSTOP processing, theProcessor Operations-related automation table dataprocessing tblaction failed, because the NetViewAUTOTBL command, issued internally, did not respondwith a successful completion message BNH360I. Thetblaction values can be 'removal' or 'activation' .



System programmer responseVerify if automation table member INGMSGSA isavailable and contains "GROUP:INGPOPS".

ISQ605I PROC-OPS AUTOMATION TABLEtblaction WAS SUCCESSFUL.

ExplanationDuring ISQSTART or ISQSTOP processing, theProcessor Operations-related automation table datawas processed successfully.

System actionThe ISQSTART or ISQSTOP processing continues.



ISQ606I PROC-OPS CONFIGURATIONVARIABLES vpo was successful.

ExplanationDuring ISQSTART the BUILD or ISQSTOP the DESTROYof additional configuration variables was performedsuccessfully.

System actionThe ISQSTART or ISQSTOP continues.





ISQ607I PROC-OPS CONFIGURATIONVARIABLES OPTION vpo is notvalid.

ExplanationDuring ISQSTART or during ISQSTOP the invalidprocessing option vpo was used. Valid processingoptions are BUILD or DESTROY.



System programmer responseContact the IBM system support.

ISQ608I PROC-OPS ISQVARS VARIABLEkeyvar FOUND EMPTY,PROCESSING TERMINATED.

ExplanationDuring ISQSTART a processor operations configurationwas used that contains insufficient ISQVARSinformation to build additional required configurationvariables. Additional variables need to be created forall processors with a connection type other than NVC.The keyword variable keyvar can be one of thefollowing: THWLIST, NPNETID, NPLU, CTYPE, TAUTH,SEADDR or HMCADDR.

System actionThe ISQSTART processing terminates.


System programmer responseMake sure your processor operations control file usedfor ISQSTART contains target hardware definition. Fortarget hardware with a connection type other thanNVC, verify that it has all required fields defined usingthe customization dialog. Add the processorinformation and rebuild your processor operationscontrol file. Issue ISQSTART with the new buildconfiguration file.

ISQ609I Target Hardware Name must notbe blank.

ExplanationA blank value for the mandatory ISQIPSWT commandparameter target hardware name was provided.

System actionProcessing of the ISQIPSWT command ends before itis complete.

Operator responseProvide a valid target hardware name with theISQIPSWT command.


ISQ610I Invalid parameter name entered:parameter-name.

ExplanationThe second parameter for the ISQIPSWT commandwas provided, but was not FORCE(YES) or FORCE(NO).


Operator responseProvide a valid FORCE parameter with the ISQIPSWTcommand.


ISQ611I Invalid 'FORCE' option - must be'FORCE(YES)' or 'FORCE(NO)'.

ExplanationThe FORCE parameter for the ISQIPSWT commandwas provided, but the value was not YES or NO.




Operator responseProvide a valid FORCE parameter value with theISQIPSWT command.


ISQ612I Target Hardware Connection Typeis not SNMP, but target-hardware-connection-type.

ExplanationThe target hardware is not SNMP-connected.



System programmer responseMake sure that the target hardware connection type iscorrectly defined in the SA z/OS customization dialog.

If the connection type is correctly defined (that is, theconnection type really is not SNMP), you cannot usethe ISQPSWT command for this target hardware.

If the connection type is not correctly specified,change the value to SNMP, rebuild the processoroperations control file and restart processoroperations.

ISQ613I Target Hardware Variable SEADDRor HMCADDR must not be blank.

ExplanationOne of the processor operations variables, SEADDR orHMCADDR (or both), is blank.



System programmer responseMake sure that both values are correctly defined in theSA z/OS customization dialog. To avoid restartingprocessor operations, the SEADDR or HMCADDRvalues can be set using the ISQVARS command.

ISQ614I IP connect to alternate IP addressvalue-of-HMCADDR failed forTarget Hardware target-hardware-name.

ExplanationThe ISQIPSWT command tries to contact the IPaddress that is stored in HMCADDR, but fails.

System actionIf the Target Hardware corresponds to the inputparameter of the ISQIPSWT command, processing ofthe ISQIPSWT command ends before it is complete.


System programmer responseCheck whether the SE's alternate network card worksproperly. Additionally, make sure that its value iscorrectly defined in the SA z/OS customization dialog(the TCP/IP Address or Hostname for SupportElement second Adapter or a HMC entry field in thePROCESSOR INFO policy item of the PRO entry).

ISQ615I Primary SE connection value-of-SEADDR can still be used, specifyFORCE(YES) to enforce addressswitch.

ExplanationThe ISQIPSWT command checks whethercommunication to the IP address that is stored inSEADDR is possible. In this case, FORCE(YES) must bepassed as the second command parameter in order tosuccessfully execute the command.


Operator responseRepeat the ISQIPSWT command with FORCE(YES).




ISQ616I Connection failed for systemsystem-name - ISQXIII returncode ISQXIII-return-code.

ExplanationAfter switching the SEADDR and HMCADDR values, theISQIPSWT command tries to re-initialize the systemsof the target hardware that was previously stopped byISQIPSWT. The ISQXIII command that was used toperform this task encountered an error.



System programmer responseBrowse the netlog for additional error messages. Withregard to ISQXIII, look for AOFA0002 responses withassociated condition and sense data. If possible,correct errors and retry ISQIPSWT.

ISQ617I Command partially executed - IPaddresses were not changed.

ExplanationThis message is issued with message ISQ615I toindicate that only some logic of the ISQIPSWTcommand has been executed, namely, the closing oftarget systems. Before exiting, the ISQIPSWTcommand will undo the switching of values betweenvariables SEADDR and HMCADDR.


Operator responseMake a note of the target systems that were closed bythe (failed) ISQIPSWT command. Before rerunningISQIPSWT, you can start these manually using theISQXIII command.


ISQ618I target-hardware-name ISQIPSWTTSTIME(time-stamp)STATUS(status).

ExplanationThis message appears in response to the unsuccessfulexecution of an ISQIPSWT command. Processing ofthe ISQIPSWT command ended.

The variable target-hardware-name shows thename of the target hardware that is associated withthe command.The variable status indicates the command endingstatus. Possible values for status are FAILED orREJECTED.

System actionProcessing of the ISQIPSWT command completes.



ISQ619I Command inhibited byinitialization pending for targethardware target-hardware-name.

ExplanationThis message appears in response to the ISQIPSWTcommand. Processing of the ISQIPSWT commoncommand detected that one or more target systemsare currently being processed by the ISQXIIIcommand (initialize target system connection). Inorder to avoid interference with the runninginitialization process, the ISQIPSWT commandterminates with a 'rejected' message.

The variable target-hardware-name shows thename of the target hardware that is associated withthe command.

System actionProcessing of the ISQIPSWT command completes.

Operator responseCheck that all target system connection commandshave ended for the command target hardware andrepeat the ISQIPSWT command.




ISQ620I Current IP address ip-addressdoes not match SEADDR valueSEADDR-value

ExplanationThe actual IP address used for the target hardwareconnection is different to the value stored in ISQVARS'SEADDR'. This could happen if the value of SEADDRwas changed after target hardware connectioninitialization.


Operator responseUse common command ISQVARS to update value ofSEADDR to the same value used for the actualconnection.


ISQ621I Target Hardware target-hardware-name has still status'CONNECTED'.

ExplanationClosing of all active target systems should have beendone, but the Target Hardware provided as inputparameter for ISQIPSWT still has connection status'CONNECTED'. Expected status is 'NOT_CONNECTED'.


Operator responseSave or print the NetView log and contact your systemprogrammer.

System programmer responseCheck the NetView log for errors with ISQXCLScommand execution. If possible, eliminate theproblem source and retry ISQIPSWT command.

ISQ622I Target Hardware target-hardware-name has no alternate IP addressdefined.

ExplanationFor the Target Hardware, the value for either SEADDRor HMCADDR is blank, so it is not possible to switch toa different IP address.

System actionProcessing of the ISQIPSWT continues, but targetsystem connections for that Target Hardware remainclosed.

Operator responseCorrect setup SEADDR and HMCADDR for the TargetHardware using ISQVARS and manually issue ISQXIIIfor each Target System that should have an activeconnection. Possibly, update the correspondingProcessor entry in System Automation's customizationdialog.


ISQ623I Alternate IP address ip-addresscannot use HMC connection whichis already active for another TargetHardware

ExplanationFor the Target Hardware, the value for HMCADDR is theIP address of a HMC for which an active connectionalready exists for another Target Hardware.


Operator responseManually close (Host-based command ISQXCLS) allactive target systems using that IP address and repeatthe ISQIPSWT command.


ISQ700I pppppppp SC mmmmm



ExplanationA message has been received from the ProcOpsService Machine (PSM). The original message wasreceived by the virtual machine that the PSM ControlProgram is running in.

The variable pppppppp gives the name of the PSMthat the message has been received from.The variable mmmmm gives the text of themessage that was received by the PSM.

System actionNone.



ISQ701I PSM Receive Program started.Version nnn

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been started in its Message MonitoringTask (MMT). This is a long running program thatreceives messages issued by guest machines on theVM system that are controlled by the PSM.

The variable nnn gives a value that indicates thelevel of the program run. This is used for servicepurposes only.

System actionNone. This is an informational message only. Normalprocessing continues.



ISQ703I PSM Receive Program for PSMppppppp starting on task ttttttt.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver program

ISQVMRCV has been started in its Message MonitoringTask (MMT).

The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.The variable tttttttt gives the name of the autotaskthat this copy of the program is running in.

System actionNormal processing continues.



ISQ704I PSM Receive Program for PSMppppppp will connect to IPaddress nn.nn.nn.nn

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been started in its Message MonitoringTask (MMT).

The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.The variable nn.nn.nn.nn gives the dotted-decimalIP address of the remote VM system that this copyof the program will connect to in order to receivemessages from the PSM running in that VM system.




ISQ705I PSM pppppppp has port addressnnnnn for message traffic.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver program



ISQVMRCV has been started in its Message MonitoringTask (MMT).

The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.The variable nnnnn gives the port number on theremote VM system that this copy of the programwill connect to in order to receive messages fromthe PSM running in that VM system.




ISQ706I CONNECT done for socket sss

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has issued a TCPIP CONNECT to set up aconnection to its associated PSM. The CONNECT hascompleted with a return code of zero.

The variable sss gives the socket number used forthe CONNECT call.




ISQ707I CONNECT done for socket sss.Awaits actual connection fromPSM.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has issued a TCPIP CONNECT to set up aconnection to its associated PSM.

The CONNECT has completed with a return code ofzero, but the full two-way communication has notbeen set up. The PSM is not responding to theCONNECT. Because the socket operates in non-blocking mode, the program waits until the PSM issuesa TCPIP ACCEPT, at which time a full two-wayconnection is in place.

The variable sss gives the socket number used forthe CONNECT call.


Operator responseAs soon as the Message Server on the PSM issues aLISTEN, this link should connect and an ISQ709Imessage should be seen. If it does not, ensure that thePSM on the remote VM system is active and that allparts of the IP connection between the PSM and theProcOps NetView are functioning.

Once the IP link to the PSM is restored the programshould connect automatically and the ISQ709Imessage should be seen. This reconnection may notoccur immediately after the link is established.


ISQ708E CONNECT for socket sss gaveTCPIP error number eeee

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been issued a TCPIP CONNECT to setup a connection to its associated PSM. The CONNECThas completed with an error that prevents furtherprocessing.

The variable sss gives the socket number used forthe CONNECT call.The variable eeee gives the non-zero TCPIP errornumber returned by the CONNECT call.

System actionthe PSM Message Receiver program terminates.

Operator responseReport the error to your system programmer.



System programmer responseRefer to the errno.h header file for a completedescription of the error number returned, if possible.Use this to correct the error, then reinitialize the PSMusing ISQXIII for each of its target systems that isdesired to be initialized.

ISQ709I Handshake done for socket sss toPSM pppppppp. Session fullyestablished.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has established a TCPIP connection.

The PSM has accepted the connection and has sentback a valid handshaking sequence. The two ends ofthe connection are now communicating with eachother. Up to this point a successful CONNECT mayhave been done, but it does not indicate two-waycommunication. From this point on, unsolicitedmessages may be received from the PSM.

The variable sss gives the socket number used.The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.




ISQ710I Socket nnn is in non-blockingmode.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been obtained a TCPIP socket and hasset it to non-blocking mode.

The variable nnnnnnnn gives the socket numberobtained. This socket number may be used in latermessages.




ISQ711E FCNTL request to set non-blockingmode for socket sss ended witherror number eeee

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been used the FCNTL request to setnon-blocking mode for a socket. The request ended inerror.

The variable eeee gives the non-zero TCPIP errornumber returned by the FCNTL request.

System actionthe PSM Message Receiver program terminates. Allinitialized target systems on the PSM are closed.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, if possible, then reinitialize the PSMusing ISQXIII by issuing the ISQXIII command foreach of its target systems that are to be initialized.

Otherwise, report the problem to your IBM Servicerepresentative.

ISQ712I PSM Receive Program for PSMpppppppp on task tttttttt has beencanceled.

ExplanationAs part of the shutdown of a ProcOps Service Machine(PSM), the PSM Message Receiver program ISQVMRCVhas detected that is canceled by a NetView RESET orCANCEL command has been issued, indicating that theprogram should stop execution.




System actionThe PSM Message Receiver program terminates with azero return code. Such a cancel is normally done aspart of the normal termination of a PSM connection,when the last initialized target system on a PSM isclosed. All target systems on the PSM are then closed.



ISQ713I Socket sss closed. RC =rrrr errornumber = eeee

ExplanationAs part of the termination of a Message Receiverprogram, a CLOSE has been issued for a previouslyobtained TCPIP socket. The termination may havebeen requested or be the result of an error.

The variable sss gives the socket number of thesocket that was closed.The variable rrr gives the return code from theCLOSE call.The variable eeee gives the TCPIP error numberreturned by the CLOSE call. A value of zeroindicates no error was detected.

System actionTermination of the ProcOps Service Machine (PSM)Message Receiver program continues. All initializedtarget systems on the PSM are closed.



ISQ714E SELECT call for socket sss action agave error number eeee

ExplanationThe ProcOps Service Machine (PSM) Message Receiverprogram issued a TCPIP SELECT call to check whetherit could proceed with a READ or WRITE request. TheSELECT gave an error.

• The variable sss gives the socket number of thesocket that the SELECT was made for.

• The variable a gives the desired action that theSELECT was made for:

– A value of R indicates that the program was readyto do a READ.

– A value of W indicates that the program was readyto do a WRITE, or that the program was ready toconnect to the PSM.

– Any other value indicates that the program waswaiting.

• The variable eeee gives the TCPIP error numberreturned by the SELECT call.

System actionThe PSM Message Receiver program terminates. Allinitialized target systems on the PSM are closed.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, if possible. Then reinitialize the PSMby issuing the ISQXIII command for each of its targetsystems that are to be initialized.

Otherwise report the problem to your IBM ServiceCenter.

ISQ715E Unrecoverable error for socket sssto PSM pppppppp. Programending.

ExplanationThe ProcOps Service Machine (PSM) Message Receiverprogram has sustained an error that it cannot recoverfrom. This message is preceded by one or more errormessages detailing the cause of the terminating error.

The variable sss gives the socket number of thesocket that the error occurred on.The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.





System programmer responseRefer to earlier error messages.

ISQ717I Session on socket sss to PSMpppppppp has been closed byPSM.

Explanationthe ProcOps Service Machine (PSM) Message Receiverprogram has sustained a signal indicating that theconnection has been closed as a result of programaction by the PSM. This may be the result of anintended termination, or an unexpected error detectedby the PSM.

The variable sss gives the socket number of thesocket that the error occurred on.The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.

System actionThe PSM Message Receiver program terminates with areturn code of zero.

Operator responseCheck whether the PSM terminated the connection asa result of a normal termination request. If it did not,investigate why the PSM issued the termination. Toreinitialize the PSM, issue the ISQXIII command foreach of its target systems that are to be initialized.


ISQ718E PSM Receive Program failed toobtained socket. Return code =rrrrrr

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been started in its Message MonitoringTask (MMT). It issued a TCPIP SOCKET call, but thiswas not successful.

The variable rrr gives the non-zero error numberreturned by the SOCKET call.

System actionThe PSM Message Receiver program terminates. Alltarget systems on the PSM are closed.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this todetermine the cause of the error and then re-issue theoriginal request.

Otherwise report the problem to your IBM ServiceCenter.

ISQ719I PSM Receive Program hasobtained socket number nnnn

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been obtained a TCPIP socket.

The variable nnnn gives the socket numberobtained. This socket number may be used in latermessages.




ISQ720E RECV request on socket sss gaveTCPIP error number eeee

ExplanationThe ProcOps Service Machine (PSM) Receive Programissued a TCPIP RECV request that ended in error.

The variable sss gives the socket number used inthe RECV request.The variable eeee gives the TCPIP error numberreturned by the RECV request.





System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, if possible. Then use the ISQXIIIcommand to initialize each of the target systems onthe PSM that you want to initialize.

ISQ721E FCNTL call to set non-blockingmode for socket sss ended withTCPIP error number eeee

ExplanationAs part of the processing to send a request to aProcOps Service Machine (PSM) on VM, the PSM SendProgram ISQVMSND has issued a FCNTL request to setnon-blocking mode for its TCPIP socket. The requestended in error. No command has been sent to the PSM.

The variable sss gives the socket number used inthe FCNTL request.The variable eeee gives the TCPIP error numberreturned by the FCNTL request.

System actionExecution of the PSM Send Program terminates withan error return.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, if possible, then reissue the failingcommand, if appropriate.

ISQ722I PSM Send Program for PSMpppppppp on task tttttttt has beencanceled.

ExplanationWhile sending a request to a ProcOps Service Machine(PSM), the PSM Send Program has detected that thecommand is to be canceled immediately. At the pointof cancelation, the request may or may not have beensent to the PSM. Also, some, none, or all of theimmediate responses to the request (if any) may havebeen returned as ISQ700I messages.

Any indirect messages issued as a result of the requestexecuting on the PSM (for example, CP commands to aguest machine) are returned as ISQ900I messagesusing the PSM Message Receiver and are not affected.


System actionThe PSM Send Program ends. Commands that calledthe Send Program may end successfully orunsuccessfully.



ISQ723E SELECT call for socket sss action agave TCPIP error number eeee

ExplanationWhile sending a request to a ProcOps Service Machine(PSM), the PSM Send Program issued a SELECTrequest to check whether it could proceed with aREAD or WRITE request. The SELECT request gave anerror.

• The variable sss gives the socket number of thesocket that the SELECT was made for.

• The variable a gives the desired action that theSELECT was made for:

– A value of R indicates that the program was readyto do a READ.

– A value of W indicates that the program was readyto do a WRITE, or that the program was ready toconnect to the PSM.

– Any other value indicates that the program waswaiting.

• The variable eeee gives the TCPIP error numberreturned by the SELECT request.

System actionExecution of the Send Program terminates with anerror. Depending on the point at which the erroroccurred, the request may or may not have been sentto the PSM, and some, all, or none of the responses, ifany, may have been received.

Any indirect messages issued as a result of the requestexecuting on the PSM (for example, CP commands to aguest machine) are returned as ISQ900I messagesusing the PSM Message Receiver and are not affected.



Higher level commands calling the PSM Send Programare likely to be unsuccessful.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, if possible, then reissue the failingcommand, if applicable.

ISQ724E PSM Send Program timed outwaiting to connect for PSMpppppppp.

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Program issueda TCPIP CONNECT request to the PSM. The requesttimed out.

The variable pppppppp gives the name of the PSM.

System actionThe request is not sent to the PSM. An error returncode is given to the caller of the PSM Send Program

If this occurred as a result of a command such asISQXIII or ISQSTART, the PSM and its guest targetsystems enter error status.

If this occurred as a result of a ProcOps commoncommand, the command is not executed.

Operator responseEnsure that the PSM is initialized and can be reachedthrough the IP network. When resolved, and ifappropriate, reissue the command that failed.


ISQ725E Caller not authorized to usecommand cccccccc

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Programdiscovered that the caller did not have NetViewauthorization to run the command.

The variable cccccccc gives the name of theProcOps command processor that was invoked.

System actionThe request is not sent to the PSM. An error returncode is given to the caller. Higher level commandscalling the PSM Send Program are likely to beunsuccessful.

Operator responseReport the problem to your system programmer

System programmer responseCheck that the security definitions in NetView arecorrect. (Command authorization is done using eitherCommand Authorization Table definition, or throughdefinition to an SAF product such as RACF.)

If necessary, use NetView or SAF product facilities, orboth, to update and refresh the definitions used.

ISQ726E Caller not authorized to addressPSM tttttttt

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Programdiscovered that the caller did not have NetViewauthorization to send a request to the indicated PSM.

The variable tttttttt gives the name of the PSM thatthe request was directed to.



System programmer responseThis message is likely to be preceded by NetViewmessages BHN236E and BNH237E, giving details ofthe failed authorization. Use these to check that thesecurity definitions in NetView are correct.

Access to specific PSMs is controlled by theauthorization definition for the TARGET operand of theISQVMSND command. (Command authorization isdone using either Command Authorization Tabledefinition, or through definition to a SAF product suchas RACF.)




ISQ727E Authorization checking ended withreturn code cccc

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Program issueda call to the CNMSCOP routine to check that the callerwas authorized to issue the request. The call resultedin an unexpected return code.

The variable cccc is the return code.



System programmer responseUse the return code to investigate why the unexpectedreturn code was given. The meaning of the return codefor CNMSCOP is given in the section "HLL ServiceRoutine Reference" in the NetView Customization:Using PL/I and C manual.

Check that the security definitions in NetView arecorrect. Access to specific PSMs is controlled by theauthorization definition for the TARGET operand of theISQVMSND command. (Command authorization isdone using either Command Authorization Tabledefinition, or through definition to a SAF product suchas RACF.)


ISQ728E PSM Send Program failed toobtained socket. TCPIP errornumber: eeee

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Program failedto obtain an IP socket.

The variable eeee gives the non-zero TCPIP errornumber returned by TCPIP.

System actionThe request is not sent to the PSM. An error returncode is given to the caller. Higher level commands

calling the PSM Send Program are likely to beunsuccessful.


System programmer responseRefer to the errno.h header file for a completedescription of the error number returned. Use this tocorrect the error, then reissue the request ifappropriate.

ISQ729E Message Receiver handshakefailed for socket ss to PSMpppppppp

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has established a TCPIP connection. ThePSM has accepted the connection and has sent back ahandshaking sequence. The sequence sent back doesnot match that sent.

The variable ss gives the socket number used.The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.

System actionThe connection is broken and the PSM MessageReceiver program terminates. All target systems on thePSM are closed.


System programmer responseCheck that the authorization tokens used at both endsof the connection match. If necessary make thenecessary changes.

For NetView, the Customization Dialogs must be used,and a new ProcOps control file must be built. ProcOpsis then refreshed with this updated control file.

For the PSM, stop the PSM, update the ISQPARM DATAfile, and restart the PSM.

ISQ730E Unrecoverable error for socketssss to PSM pppppppp. SendProgram ending.



ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Programencountered an error that prevented furtherprocessing. This message is preceded by othermessages that give details of the error.

The variable sss gives the socket number of thesocket being used. In some cases the error may beencountered before a socket has been obtained. Inthese cases the socket number displayed is -1.The variable pppppppp gives the name of the PSM.

System actionAn error return code is given to the caller. Higher levelcommands calling the PSM Send Program are likely tobe unsuccessful. The request may or may not havebeen sent to the PSM.

Operator responseMessages preceding this indicate in more detail thenature of the problem. Use these to respond to theerror, if appropriate. Otherwise, report the problem toyour system programmer.

System programmer responseMessages preceding this indicate in more detail thenature of the problem. Use these to respond to theerror.

ISQ731I CONNECT for socket sss gaveTCPIP error number eeee.

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Program issueda TCPIP CONNECT to set up a connection to itsassociated PSM. The CONNECT has completed with anerror that prevents further processing.

The variable sss gives the socket number beingused.The variable eeee gives the non-zero TCPIP errornumber returned by the connect call.

System actionThe request is not sent to the PSM. The Send Programterminates and an error return code is given to thecaller. Higher level commands calling the PSM SendProgram are likely to be unsuccessful.



ISQ732E Session on socket sss to PSMpppppppp has been closed byPSM.

ExplanationWhile attempting to send a request to a ProcOpsService Machine (PSM), the PSM Send Program hasreceived a signal from the PSM that the connection hasbeen forcibly reset, possibly as a result of thetermination of the PSM or a thread of the PSM.

The variable sss gives the socket number used.The variable pppppppp gives the name of the PSM.

System actionThe request may or may not have been sent to thePSM. Some, all, or none of the responses from the PSMmay have been received. The Send Programterminates and an error return code is given to thecaller. Higher level commands calling the PSM SendProgram are likely to be unsuccessful.

Operator responseCheck whether the PSM terminated the connection asa result of a normal termination request. If it did not,investigate why the PSM issued the termination.Otherwise, report the error to your systemprogrammer.


ISQ733I RECV request on socket ssss forPSM pppppppp gave TCPIP errornumber eeee

ExplanationWhile sending a request to a ProcOps Service Machine(PSM), the PSM Send Program has attempted to read a



response. The TCPIP RECV that was issued ended inerror.

The variable sss gives the socket number beingused.The variable pppppppp gives the name of the PSM.The variable eeee gives the non-zero TCPIP errornumber returned by the RECV call.

System actionThe request has been sent to the PSM. Some, all, ornone of the responses from the PSM may have beenreceived. The Send Program terminates and an errorreturn code is given to the caller. Higher levelcommands calling the PSM Send Program are likely tobe unsuccessful.



ISQ734E WRITE request on socket ssssgave TCPIP error eeee

ExplanationWhile sending a request to a ProcOps Service Machine(PSM), the PSM Send Program issued a TCPIP WRITEcall. The call ended in error.

The variable sss gives the socket number beingused.The variable eeee gives the non-zero TCPIP errornumber returned by the RECV call.

System actionThe request may or may not have been received andexecuted by the PSM. No responses from the PSMhave been received. The Send Program terminates andan error return code is given to the caller. Higher levelcommands calling the PSM Send Program are likely tobe unsuccessful.



ISQ735I PSM pppppppp has authorizationtoken tttttttt

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM Message Receiver programISQVMRCV has been started in its Message MonitoringTask (MMT).

The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.The variable tttttttt gives the authorization tokenthat is being used to validate the caller to the PSM.




ISQ736E Message traffic (includingheartbeats) from PSM pppppppphas stopped.

ExplanationOnce a TCPIP session is established between aProcOps Service Machine (PSM), and its ReceiveProgram in NetView, the Receive Program expects toreceive either normal message traffic or heartbeatmessages at regular intervals. No such messages havebeen received for an extended period.

The variable pppppppp gives the name of the PSMthat this copy of the program is communicatingwith.

System actionThe Receive Program terminates. All target systems onthe PSM are closed.



Operator responseCheck that the PSM is still operating. If the PSM or oneof its threads has failed, correct the error and then re-initialize the active target systems on the PSM usingISQXIII commands


ISQ738E PSM Send Program timed outwaiting to read for PSM pppppppp.

ExplanationWhile processing a request to a ProcOps ServiceMachine (PSM), the PSM Send Program timed outwhen waiting for responses to the request it sent tothe PSM.


System actionThe request may or may not have been sent to thePSM. Some, all, or none of any possible responses mayhave already been received (as ISQ700I messages).The Send Program terminates and an error return codeis given to the caller.

If this occurred as a result of a command such asISQXIII or ISQSTART, the PSM and its guest targetsystems enter error status.

If this occurred as a result of a ProcOps commoncommand, the command may or may not haveexecuted.

Operator responseEnsure that the PSM is initialized and can be reachedthrough the IP network. When resolved, and ifappropriate, check the status of the target systems onthe PSM, and reissue the command that failed, ifappropriate.


ISQ739E Cannot contact PSM pppppppp.Likely PSM not active or bad IPaddress.

ExplanationWhile sending a request to a ProcOps Service Machine(PSM), the PSM Send Program issued a TCPIP WRITEThe WRITE ended with TCPIP error ECONNREFUSED.

The attempt to connect to a socket was refusedbecause there was not a process listening or becausethe queue of connection requests was full and theunderlying protocol does not support retransmissions.


System actionThe request has not been received and executed bythe PSM. No responses from the PSM have beenreceived. The Send Program terminates and an errorreturn code is given to the caller. Higher levelcommands calling the PSM Send Program are likely tobe unsuccessful.

Operator responseCheck that the PSM is active. If necessary, start thePSM. Then reenter the request, if appropriate. If this isnot successful, report the error to your systemprogrammer.

System programmer responseCheck that the IP address that is specified for the PSMin the customization dialogs is correct and that thebuild has created the correct ProcOps configuration inthe automation control file (ACF), or ProcOps controlfile for systems earlier than SA z/OS 3.3. Make sure theupdated ACF information gets activated on the focalpoint system. Recycle ProcOps with the newconfiguration information.

ISQ750E An attempt to set the TCPIP stackgave error number: eeee

ExplanationAs part of the processing of a request to a ProcOpsService Machine (PSM), or as part of the initializationof the PSM Receive Program, an attempt was made tochoose the active TCPIP image stack that theapplication will connect to. The call was unsuccessful.

The variable eeee gives the non-zero TCPIP errornumber returned by the SETIBMOPT call.

System actionThe program (either the PSM Send Program or the PSMReceive Program) terminates. In the case of the PSMSend Program, no request is sent.

Operator responseLikely values for the TCPIP error number include 1011(EIBMBADTCPNAME), which indicates that the desiredimage stack is not active. If appropriate, start the job



or system task that corresponds to this stack.Otherwise, report the error to your systemprogrammer.


If the stack name is incorrect, use the customizationdialogs to set a new TCPIP Stack name for the PSM.Use the Build step to create the correct ProcOpsconfiguration in the automation control file (ACF), orProcOps control file for systems earlier than SA z/OS3.3. Make sure the updated ACF information getsactivated on the focal point system. Recycle ProcOpswith the new configuration information.

ISQ751E ISQGSMSG routine returned non-zero return code: rr

ExplanationA message has been received by the ProcOps ServiceMachine (PSM) Receive Program. The ISQGSMSGservice routine has been called to route it to interestedoperators. The routine failed.

The variable rr gives the non-zero return code fromthe ISQGSMSG routine.

System actionThe message is not routed, displayed or logged.


System programmer responseReport the problem to your IBM Service Center.

ISQ752E The program failed to resolve IPaddress for host hhhh. TCPIP errornumber: rr

ExplanationAs part of the initialization of the ProcOps ServiceMachine (PSM) Send or Receive Program, an attemptwas made to resolve the IP address for PSM hosthhhh. The call to the LE getaddrinfo routine wasunsuccessful.

The variable rr is the non-zero return code from thegetaddrinfo routine.

System actionThe program (either the PSM Send Program or the PSMReceive Program) terminates. In the case of the PSMSend Program, no request is sent.


System programmer responseCheck that the host name specified for the PSM in thecustomization dialogs is correct. Use the Build step tocreate the correct ProcOps configuration in theautomation control file (ACF), or ProcOps control filefor systems earlier than SA z/OS 3.3. Make sure theupdated ACF information gets activated on the focalpoint system. Recycle ProcOps with the newconfiguration information.

ISQ753I PSM pppppppp forces IPv4protocol for message traffic.PSMIPV4 flag is ff

ExplanationThe ProcOps Service Machine (PSM) Send Programand PSM Receive Program force will use IPv4 protocolfor communication with PSM host.

The variable pppppppp gives the name of the PSM.The variable rr gives the value of the Force to useIPv4 for Hostname flag in the ProcOps ServiceMachine Information panel of the customizationdialog.

System actionNormal processing continues using the IPv4 protocol.



ISQ755E Error determining productcapability information. PSMconnection not established.

Explanation:With Automation Control, PSM is only supported if theVM Host and Automation Control both run on the samehardware (CPC).

System action:The PSM Send Program terminates, no request is sent.



Operator response:Check the PSM setup - for example, using ISQXDST - ifthe PSM VM Host is located on the same processor(target hardware) Automation Control runs on.

System programmer response:Use the customization dialog to change the PSMsetting such that the processor entry for the VM hostruns on the same CPC as Automation Control andrebuild / load the automation control file (ACF).

ISQ809I BCPII EVENT ERROR(rc) BETWEENCPC cpcaddr AND domain/operator. LASTS(stime)

ExplanationA general BCPii event wait occurred. The BCPiiconnection will be terminated.

• The variable rc is the HwmcaWaitEvent return codepassed back from the System z API to the caller(INGHWCOM), while waiting for event data from theSupport Element.

• The variable cpcaddr is the processor name definedas SA-PDB/Connection Flag/CPC Name of theprocessor in SNA netid.nau format. The connectionflag indicates:L


RBCPii connection to a remote CPC using an HMCfor routing.




• The variable stime is the Date/Time stamp of the lastsuccessful connection start in the yymmddhhmmssformat.

System action:The BCPii session terminates.


System programmer response:For return code information, refer to “InternalTransport Services "0Bx00xxx"” on page 566.

Module:INGCHW0E

Classes:40

ISQ811I BCPII CONNECTION HEARTBEATBETWEEN CPC cpcaddr ANDdomain/operator FAILED.LASTS(stime)

ExplanationFor a period of 4 minutes, the Support Element of theaddressed CPC has not responded to the BCPiiheartbeat request of the operator task running in theNetView domain. The BCPii event connection is nolonger working.

• The variable cpcaddr is the processor name definedas SA-PDB/Connection Flag/CPC Name of theprocessor in SNA netid.nau format. The ConnectionFlag indicates:L







System action:The BCPii connection is internally restarted. If therestart is successful, message ISQ812I is issued. If itfails, message ISQ813E is issued with additionalinformation.


System programmer response:None

Module:INGCHW0E

Classes:40

ISQ812I BCPII LINK BETWEEN CPCcpcaddr AND domain/operator RE-ESTABLISHED. NEW LASTS(stime)

ExplanationAfter a BCPii event session heartbeat failure, the BCPiiconnection has been successfully restarted.









• The variable stime is the Date/Time stamp of the lastsuccessful connection start in the yymmddhhmmssformat. The connection start initializes the LASTSvalue and is therefore prefixed with NEW.



System programmer response:For additional information, refer to the event handlerasynchronous response report “AOFA0998” on page553.

Module:INGCHW0E

Classes:40

ISQ813E BCPII CONNECTION RECOVERYFROM domain/operator TO CPCcpcaddr FAILED. RSN(rsncode)LASTS(stime)

ExplanationAfter a BCPii event session heartbeat failure betweenthe targeted CPC and the operator task of the NetViewdomain, the internal BCPii connection restart failed.



• The variable cpcaddr is the processor name definedas SA-PDB/Connection Flag/CPC Name of theprocessor in SNA netid.nau format. The ConnectionFlag indicates:

LBCPii local connection. SA z/OS targets its ownCPC.



• The variable rsncode is the reason code. For fulldetails, refer to “Internal Transport Services"0Bx00xxx"” on page 566.


System action:The BCPii connection to the addressed CPC is closed.

Operator response:Since this BCPii connection is monitored by ProcOps, astart of a failing connection is retried automatically ateach defined connection poll time. No further action isrequired. If the heartbeat failure message ISQ811Iwas preceded by an ISQ814E message, additionalerror cause and reason information is available.


Module:INGCHW0E

Classes:40

ISQ814E BCPII CONNECTION TO domain/operator ABORTED BY THE CPCcpcaddr SUPPORT ELEMENT.CAUSE(cause_type)REASON(rsn_str) LASTS(stime)

ExplanationThe CPC Support Element has sent an'Application_Ended' event over an active BCPiiconnection to indicate the communication with theNetView domain/operator is about to end. This eventmessage is provided only for BCPii connections toSystem z10 and newer processors.



• The variable cpcaddr is the processor name definedas SA-PDB/Connection Flag/CPC Name of theprocessor in SNA netid.nau format. The ConnectionFlag indicates:



LBCPii local connection. SA z/OS targets its ownCPC.



• The variable cause_type is the action that caused theconsole application to end. Depending on the typegiven, a possible console application outage timecan be predicted.SHUTDOWN_CONSOLE

Long outage; manual intervention is required torecover.

RESTART_APPLICATIONMedium outage of 10 - 20 minutes can beexpected until the console application is fullyoperational.

RESTART_CONSOLEMedium outage of 10 - 20 minutes can beexpected until the console device and consoleapplication are fully operational again.

UNKNOWNThe type code in the event data is unknown. Longoutage; manual intervention may be required torecover.

• The variable rsn_str refers to the issuer that causedthe console application to end.USER

A logged-on SE user.AUTOMATION



The reason code in the event data is unknown.• The variable stime refers to the Date/Time stamp of

the LAST successful connection start in theyymmddhhmmss format.


Operator response:Use the cause_type information of the message todetermine the BCPii connection outage time that canbe expected. In case of a long outage time, considerthe SUSPEND command for the BCPii connection.


Module:INGCHW0E

Classes:40

ISQ815I BCPII CONNECT FROM domain/operator TO CPC cpacaddrRETURNED: resp

ExplanationRequest to contact the CPC Support Element ofcpcaddr over the BCPii from domain/operator returneda response of resp.







• The variable resp is:SUCCESS

SE connection established.ERROR(rsncode)

Failure to contact the SE.rsncode

For information about the reason code,please refer to the appendix “ConditionCodes” on page 554. Select the table thatlists the reason code together with the errordescription.

System actionIf the connect was successful, session initializationcontinues with CPC configuration discovery. MessageISQ817I will be issued when this is complete. If theconnect processing failed, no further sessioninitialization is done and processing stops.

If a connection polling interval is defined in the SA PDBfor this target hardware, the connect requests will beretried automatically.





Module:INGCHW0A

Classes:40

ISQ816I BCPII AWAIT CMD SESSIONTERMINATION TO CPC cpcaddr INdelay SECONDS: DOMAIN(domain)OPID(operator) CMD(cmd)LASTS(stime)

ExplanationThe HW event handler for CPC (cpcaddr) sessionreturned an error and the asynchronous sessionterminates. In order to perform a save memorycleanup, an ongoing HW command for the CPC runningin task (operator) needs to be terminated first. Wait for(delay) seconds for normal command termination.





• The variable delay is the time in seconds thecommand session is given to end.



• The variable cmd is the command token of thecurrently executed HW command.

• The variable stime refers to the Date/Time stamp ofthe LAST successful connection start in theyymmddhhmmss format.




Module:INGCHW0M

Classes:40

ISQ817I BCPII DISCOVERY OF cpcaddr FORdomain/operator RETURNED: resp

ExplanationThe initial discovery request from domain/operator forconfiguration information of cpcaddr ended with aresponse of: resp.







• The variable resp is:SUCCESS NEW LASTS(stime)

All required CPC configuration information hasbeen retrieved. The BCPii connection is now fullyoperational.stime

Date/Time stamp of the LAST successfulconnection start in the yymmddhhmmssformat. The connection start initializes theLASTS value and is therefore prefixed withNEW.

FFDC(ffdc_id)Failure to retrieve the required CPC configurationinformation. The BCPii session cannot be used.ffdc_id

The four character ID string represents theexit point from the discovery processing andcan be used by IBM to locate the failingretrieval.




Module:INGCHW0A



Classes:40

ISQ818I BCPII LINK BETWEEN domain/operator AND CPC cpcaddr IS NOWTERMINATED. NEWSTATUS(connstat) OLDLASTS(stime)

ExplanationThe connection to the cpcaddr has been successfullyclosed from the domain/operator side. Beforeapplications can use the connection again, they mustrestart it. If the connection was closed, because of asession suspension, before restarting it, the sessionmust be resumed.







• The variable connstat is the new connection sessionstatus:NOT_CONNECTED

Connection session can be restarted again.SUSPENDED

Connection is suspended from normal usage. Itis required to resume it first, before restarting aBCPii session over this connection.

• The variable stime is the Date/Time stamp of theLAST successful connection start in theyymmddhhmmss format. Since the connection is nolonger active, the LASTS is prefixed with OLD.




Module:INGCHW0C, INGCHW0D

Classes:40

ISQ900I originator console_type message.

ExplanationThis message acts as the carrier for information thatcome from SA z/OS defined processor hardware orz/VM virtual guest machines. Originator specificationsfollowing the message-id allow to identify the rootsource of the remaining message data.

This data can be operating system console messagesor hardware event data related to a processor targethardware or a target system. This message may alsobe returned in response to hardware commands orqueries from a processor target hardware or a targetsystem. Note, that if the target system is running in aprocessor partition, or as a z/VM hypervisor guest, theoriginator information is returned either inProcessor.Lpar or PSMname.guest notation.

ISQ900I messages are sent to the ProcOps focal pointafter the connection to a target system and itsassociated target hardware is fully established. TheProcOps command ISQXIII does this. Afterwards,any operating system message displayed on thesystem console facility will be automatically sent tothe ProcOps FP, embedded in a ISQ900I message. Thesame applies if the connection to a target system,running as a z/VM guest has been established. Anymessage displayed on the guest virtual machineconsole will appear as ISQ900I message. Given atarget system LPAR or virtual machine stops operating,either a status change event or a z/VM CP message (forPSM only) will be forwarded as ISQ900I message tothe ProcOps focal point. If such an event affects theCPC or the z/VM PSM itself, it will also be reported asan ISQ900I message.

The following ProcOps commands cause ISQ900Imessages to be returned:ISQSEND

Send operating system commands to a targetsystem's console.

ISQSNDHSend OS priority response to a target system'sconsole.

ISQCCMD

Execute hardware or virtual machine command(common command).

Message variable details:

• The variable originator contains the originatorinformation of the message. It can have the followingformats:



– target system name

Example:

ISQ900I KEY3 SC ISQ417I BCPCMD STATUS(SUCCESS)

Description: ProcOps command ISQSEND isissued to target system KEY3 to forward andexecute an operating system command using thesystem console interface. The internal commandBCPCMD, used for this purpose, completedsuccessfully. The ProcOps function message-idISQ417I is used to deliver this information.Because BCPCMD is a hardware command, the SCconsole type is returned.

– target hardware name.partition name

Example 1:

ISQ900I #ECL3.KEY3 SC AOFA0200 BCPCMD CC(00000000)

Description: ProcOps command ISQSEND isissued, which internally calls the hardwarecommand BCPCMD to send an operating systemcommand to the system console feature. TheBCPCMD returns an asynchronous commandcompletion response (CC) back to the caller. Thecommand is directed to #ECL3 partition nameKEY3. Because BCPCMD is a system hardwarecommand, console type SC is used. Report idAOFA0200 identifies a command completionevent. See “AOFA0200” on page 550 foradditional information about event responses.Note, that not all documented asynchronous eventmessages may be supported. The followingasynchronous event report messages areavailable in ProcOps ISQ900I messages:AOFA0100, AOFA0200, AOFA0300, AOFA0400,AOFA0500, AOFA0600, AOFA0700, AOFA0800,AOFA0996, AOFA0997, AOFA0999.

Example 2:

ISQ900I #ECL3.KEY3 OC IEE136I LOCAL: TIME=10.59.47..

Description: ProcOps command ISQSEND isissued, which internally calls BCPCMD to send anoperating system command to the addressedtarget system or processor.Lpar. In the sample,the z/OS command DT (display time) is used. Thez/OS response is message IEE136I which returnsthe current date and time of the z/OS systemrunning in Lpar KEY3 of processor #ECL3. Sincethe response is directly from an operating systemconsole, the console type OC is returned.

Example 3:

ISQ900I #ECL3.KEY3 OCP _ *00 IEA394A THIS SERVER HAS LOST CONNECTION TO ITS SOURCE OF TIME.

Description: On partition KEY3 of processor#ECL3,z/OS has detected that a STP connectionto its time source is no longer available and hasissued operator action reply IEA394A as a prioritymessage. ProcOps has recognized this and flagsthe message as console type OCP. For anautomated response, ProcOps commandISQSNDH must be used to respond to theSYNCDEST reply 00.

Example 4:

ISQ900I #ECL3.VMTSA SC AOFA0017 GETSSTAT #ECL3 STATUS(OPERATING) CPCSNAME(IBM390PS.ECL3) BUSY(NO) TSTIME(160119152917)

Description: ProcOps command ISQCCMD #ECL3GETSSTAT is issued, which internally queries thecurrent status of the ProcOps target hardware#ECL3. The response report AOFA0017 containsthe status information together with the qualifiedCPC name, the busy flag setting and a time stamp.Since GETSSTAT is a hardware command, the SCconsole type is used. Note, although a targethardware (CPC) is addressed, the ISQ900Imessage returns an originator in thetarget_hardware.Lparname form. The reasonis that in the ProcOps legacy data model messageformat, a target system (or target system partition)must appear as top level originator. In caseswhere the command addresses only the targethardware, but no target system or partition, theLPAR name of the first defined target system onthat target hardware (VMTSA) is used. See theMessages & Codes manual, Appendix "ResponseMessages" for additional information about queryresponses like AOFA0017.

– PSMname.guest

Example:

ISQ900I PSM1.LNXT1 OC Booting default (SLES11_SP3_2)

Description: ProcOps command ISQCCMD LNXT1ACTIVATE is issued to boot linux target systemLNXT1, which is running as a Linux guest under az/VM hypervisor. The first boot message is shownin this sample. PSM1 is the name of the ProcOpsservice machine, which is controlling the LNXT1guest virtual machine and is in session with theProcOps focal point. The OC console type isshown since the boot message is from anoperating system (linux) console.



• The variable message contains the message or eventinformation, including message or event identifiersand related message text or data. Messages that aredetected include:

– Messages issued by SA z/OS that refer to a targetsystem, target hardware, target hardware Lpar, ortarget PSM and guest.

– New operating system messages displayed on thehardware system console, including z/OS multi-line messages or messages from other operatingsystems or stand-alone utilities displayed on theoperating system message window (SE/HMC).Recommended reference information is availablein the "SA z/OS Planning & Installation" manual,Appendix: "Using the Hardware IntegratedConsole of System z for External Automation withSA z/OS".

• The variable console_type contains the type ofconsole the message comes from:

– OC (Operating system console)– OCP (Operating system console priority message)– SC (Hardware system console)

ISQ900I messages are written to the NetView log.

If ISQ900I messages are issued while executing SA-BCPii LPAR Management function enabled ProcOpscommands, the messages are also displayed at theNetView operator terminal. For more informationabout LPAR Management setup and usage, pleaserefer to the "SA z/OS User's Guide".

The message is used in the ProcOps supplied ATentries to update the ISQVARS and ISQXDST statusdata model and to enable the auto-responses for z/OS,z/VM IPL message, if configured. Users can add theirown ISQ900I related automation, using the suppliedAT member ISQMSGU1. Note, that this support is notprovided in the ProcOps implementation of the IBMAutomation Control product.

System actionAutomation processing is triggered by the ISQ900Iprefix. The remainder of the ISQ900I messagedetermines which (if any) automation routine isprocessed.



ISQ901I originator console_type message.

ExplanationThis message is a copy of the ISQ900I message to bedisplayed on the NetView operator terminal.

• The variable message contains the messagedetected by SA z/OS, including both the messageidentifier and the message text. Messages that aredetected include:

– Messages issued by SA z/OS that refer to a targetsystem.

– New message lines on a target system console,including multi-line messages.

• The variable originator contains the originatorinformation of the message. It can have the followingformat:

– target system name– target hardware name.partition name– PSMname.guest

• The variable console_designator contains the type ofconsole the message comes from:

– OC Operating system console– OCP Operating system console priority message– SC Hardware system console

Each ISQ901I message is displayed only to operatorsdefined as interested operators for the target systemthat the message is associated with. Interestedoperators are defined using the configuration dialogsor the ISQXMON command, or both. Please note, thatISQ901I copies are valid for ProcOps SNMP or PSMconnection only. SA z/OS LPAR Management ISQ900Imessages using the SA-BCPii connection protocol arenot copied.

System actionNone.





Chapter 11. Messages ISQX998I and ISQX999I

ISQX998I mmmmmmmm 00000000 Faaaaaaaa llllll

ExplanationThis is a trace message from the processor operationsstorage management. This message appears only ifthe debug flag (ISQ#MTRC) in the communicationvector map is set. The debug flag can be set with theDEBUG parameter in the ISQSTART and ISQSTOPcommands, or dynamically by using the ISQTCCcommand and switching the monitor on.

• The variable mmmmmmmm shows the name of theCsect issuing the message.

• The variable 00000000 shows the name of theNetView task (TVBOPID).

• The variable F shows the Get /Free indicator where:E

A DSIFRE macro with MAINTSK=YES was issuedF

A DSIFRE macro was issuedG

A DSIGET macro was issuedH

A DSIGET macro with MAINTSK=YES was issued• The variable aaaaaaaa shows the address of

allocated or freed storage.• The variable llllll shows the last six digits (decimal

value) of the bytes allocated or freed from theDSIGET/DSIFRE macro.

System actionThe interval timer device driver starts. Initialization ofthe PC continues.



ISQX999I mmmmmmmm 00000000 F llllllllrrrr

ExplanationThis is the continuation message of message ISQX998.Is is issued in the following cases:

• A nonzero return code was set by the DSIGET /DSIFRE macro.

• The number of bytes of allocated or freed storage isgreater than 999999 (decimal value). In this casethe whole length will be displayed.

• The variable mmmmmmmm shows the name of theCsect issuing the message.

• The variable 00000000 shows the name of theNetView task (TVBOPID).

• The variable F shows the Get Free indicator where:E

A DSIFRE macro with MAINTSK=YES was issued.F

A DSIFRE macro was issued.G

A DSIGET macro was issued.H

A DSIGET macro with MAINTSK=YES was issued.• The variable llllllll shows the number of bytes

(decimal value) of allocated or freed storage.• The variable rrrr shows the return code from the

DSIGET / DSIFRE macro.

System actionThe interval timer device driver starts. Initialization ofthe PC continues.



Messages ISQX998I and ISQX999I


Messages ISQX998I and ISQX999I


Chapter 12. Messages ISQtt001I to ISQtt0723I

The following messages are issued by the PSM application. The message ID has the following form:

ISQttnnnns text

where tt is the component (thread) that issued the message. Possible values are:MA

Main threadCS

Command ServerMS

Message ServerMH

Message HandlerCN

Console ServerLG

LoggerIn many cases a message is issued only by one thread and this value is shown in the description. In somecases it may be issued by two or more threads, and the message ID shows a generic format:

• nnnn is the 4-digit message number• s is the severity of the message

IInformation

WWarning

EError

The messages in this chapter are sorted according to 4-digit message number.

ISQMA0001I PSM Main Thread entered.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the main thread of its multitaskingcontrol program has started.

System actionNormal processing continues



ISQMA0002I Waiting for Command Serverthread to initialize.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the main thread of its multitaskingcontrol program has issued a request to start theCommand Server thread. The main thread waits for theCommand Server thread to initialize before starting theLogger and Console server threads.


Messages ISQtt001I to ISQtt0723I


Operator responseIf this message is not followed by messages indicatingthat the Command Server has started processing,report this to your system programmer.

System programmer responseIf this message is not followed by messages indicatingthat the Command Server has started processing,restart the program with the Command Server traceactivated.

ISQMA0005I Main Thread ending (others maystill be running).

ExplanationThe Main Thread of the PSM control program is ending.It has attempted earlier to stop all other threads, andthese may, or may not, have terminated successfully.

System actionNormal processing continues

Operator responseIf the CMS console then issues a "Ready" message, allother threads have ended. To terminate any runningthreads enter a HX command followed by a BEGINcommand. Repeat this sequence of commands untilthe "Ready" message is issued. At this point the PSMcontrol program can be restarted.


ISQMA0101I Thread ttt started as aaaaaaa

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), or as the result of a request to thePSM, the PSM control program has successfullystarted a thread.

The variable ttt gives the numerical ID of the threadthat has started.The variable aaaaa gives the description of thethread. It may be one of: CSERV (CommandServer), MSERV (Message Server), MH (MessageHandler), LOGGER (Logger) or CNSERVER (ConsoleServer).


Operator responseEnsure that the thread indicated subsequentlyinitializes correctly. If it does not, report the problemto your system programmer.

System programmer responseNone. If a thread does not initialize correctly and thereare no messages that indicate an obvious cause, setthe trace for the failing component and restart the PSMControl program.

ISQMA0103I aaaaa thread cannot be started.Reason code rrrr

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), or as the result of request to the PSM,the PSM control program has attempted to start a newthread. The request was unsuccessful.

The variable aaaaa gives the description of thethread. It may be one of: CSERV (CommandServer), MSERV (Message Server), MH (MessageHandler), LOGGER (Logger) or CNSERVER (ConsoleServer).The variable rrrr gives the reason code returned bythe call to ThreadCreate.

System actionThe PSM control program terminates.


System programmer responseThe explanation of the reason code is found in theappendix "Return and Reason Code Values" in the CMSApplication Multitasking manual. Use this to resolvethe problem, if possible. Otherwise report the problemto your IBM Service Center.

ISQMA0104E Command Server thread failedduring its initialization.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the PSM control program started theCommand Server thread. The thread then terminatedunexpectedly.






ISQMA0106E EventMonitorCreate failed withreason code rrrr. Call was cccccccc

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), or as the result of request to the PSM,the PSM control program has attempted to create anew multitasking event monitor. The request wasunsuccessful.

The variable rrrr gives the reason code returned bythe call to EventMonitorCreate.The variable cccccccc gives the name of the eventmonitor. This is an internal name used by the PSMControl Program.




ISQMA0107E SIGNAL routine failed with reasoncode rrrr for event eeeeeeee

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), or as the result of request to the PSM,the PSM control program has attempted to signal (set)an event. The request was unsuccessful.

The variable rrrr gives the reason code returned bythe call to EventSignal.The variable eeeeeeee gives the name of the event.This is an internal name used by the PSM ControlProgram.




ISQMA0110E ADDEVENT routine failed addingevent eeeeee. No space in table.

ExplanationAs part of the initialization of a ProcOps ServiceMachine (PSM), the internal ADDEVENT service wasattempted for an event. This is an internal failure.

The variable eeeeee gives the name of the event.



System programmer responseThis is an internal failure. Report the problem to yourIBM Service Center.

ISQMA0111E Thread aaaaa could not bedeleted. Reason code rrrr.Continuing...

ExplanationAs part of the shutdown of a ProcOps Service Machine(PSM), or as the result of a request to the PSM, thePSM control program has attempted to delete anexisting thread. The request was unsuccessful.

The variable aaaaa gives the description of thethread. It may be one of: CSERV (CommandServer), MSERV (Message Server), MH (MessageHandler), LOGGER (Logger) or, CNSERVER (ConsoleServer).The variable rrrrgives the reason code returned bythe call to ThreadDelete.


Chapter 12. Messages ISQtt001I to ISQtt0723I 511

System actionThe PSM control program continues.

Operator responseThe thread may be left running. If so, use the CPcommand HX (halt execution) to terminate it. If severalof these messages are given, several uses of the HXcommand may be needed. The PSM control programmay not be restartable without a re-IPL of the PSMvirtual machine or a re-logon of the PSM virtualmachine. Report the problem to your systemprogrammer.


ISQCS0200E Command Server cannot start.TERMINATE failed with result: rrrr

ExplanationAs part of the initialization of the Command Serverthread, a TCPIP TERMINATE was issued. TheTERMINATE failed.

The variable rrrr is a string containing a nonzeroreturn code, an error name, and an error message.



System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible. When corrected, restart the PSM ControlProgram.

ISQCS0201E Command Server cannot start.INITIALIZE failed with result: rrrr

ExplanationAs part of the initialization of the Command Serverthread, a TCPIP INITIALIZE was issued. TheINITIALIZE failed.

The variable rrrr is a string containing a nonzeroreturn code, an error name, and an error message.




ISQCS0204E No valid focal point addressesfound.

ExplanationAs part of the initialization of the Command Serverthread, an attempt was made to access the ISQADDRSDATA file in order to read the list of valid IP addressesfor ProcOps NetView focal points. No data set wasfound.



System programmer responseCreate an ISQADDRS DATA file with at least one validentry. Restart the PSM control program in its virtualmachine.

ISQCS0205I Command Server valid FPaddresses are nnn.nnn.nnn.nnn,nnn.nnn.nnn.nnn, ...

ExplanationAs part of the initialization of the Command Serverthread, the ISQADDRS DATA file was read. The quotedlist of valid IP addresses for ProcOps NetView focalpoints was found. Where an entry in the file was innode name form, the equivalent dotted decimal formof its address is given.

• The variable nnn.nnn.nnn.nnn is one of the following:



– The dotted decimal IPv4 address as read from thefile

– The hexadecimal IPv6 address as read from thefile

– The dotted decimal IPv4 address as resolved fromthe node name

Node names in the IPv6 environment are not yetsupported.


Operator responseNone. This is an informational message.


ISQCS0208I Session from nnn.nnn.nnn.nnn hasinvalid address. Connectionrefused.

ExplanationThe variable nnn.nnn.nnn.nnn is the client IPaddress that attempts to connect to the PSM.




ISQCS0209E In ISQADDRS file, aaaaa could notbe resolved as a valid address.

ExplanationAs part of the initialization of the Command Serverthread, the ISQADDRS DATA file was read in order tocreate a list of valid IP addresses for ProcOps NetViewfocal points. The entry quoted is neither a valid dotteddecimal address nor could it be resolved as a validaddress by a GETHOSTBYNAME call.

The variable aaaaaa is the entry as read from thefile.



System programmer responseCorrect the entry in the ISQADDRS DATA file or ensurethat the appropriate entry exists in the files used byTCPIP to resolve names to IP addresses. Restart thePSM control program in its virtual machine.

ISQCS0210E Errors found in ISQADDRS file.

ExplanationAs part of the initialization of the Command Serverthread, the ISQADDRS DATA file was read in order tocreate a list of valid IP addresses for ProcOps NetViewfocal points. Errors were found in one or more entry.



System programmer responseSee any associated ISQCS0209E and ISQCS0211Emessages for details. Correct the entries in theISQADDRS DATA file or ensure that the appropriateentry exists in the files used by TCPIP to resolve nameto IP addresses. Restart the PSM control program in itsvirtual machine.

ISQCS0211E In ISQADDRS file,nnn.nnn.nnn.nnn is not a validdotted decimal address.

ExplanationAs part of the initialization of the Command Serverthread, the ISQADDRS DATA file was read in order tocreate a list of valid IP addresses for ProcOps NetViewfocal points. The entry quoted was entered in dotteddecimal form, but is not a valid IP address.

The variable nnn.nnn.nnn.nnn is the entry as readfrom the file.





System programmer responseCorrect the entry in the ISQADDRS DATA file.Restartthe PSM control program in its virtual machine.

ISQCS0212E ACCEPT call for socket ss gaveunexpected result: rrrrr

ExplanationIn issuing an ACCEPT for an incoming CONNECT theCommand Server received an unexpected result andwas unable to complete the connection.

The variable ss is the socket number in use.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).




ISQCS0213W nn.nn.nn.nn

ExplanationThe Command Server thread has received an internalrequest to start focal point operations to a NetViewthat is not its current focal point. That is, it already hasa running connection between the Message Server andanother NetView.

This message is sent on the existing connectionimmediately before it is terminated. (It is not displayedon the VM console.) It effectively informs the currentProcOps focal point NetView that a new ProcOps focalpoint has been established.

The variable nn.nn.nn.nn is the dotted decimal IPaddress of the new ProcOps focal point NetView.

System actionImmediately following this message, the MessageServer connection to the current focal point NetView isterminated. On the current focal point NetView, targetsystems on the PSM will then go to a target systemstatus of CLOSED.



ISQCS0214E Attempt to RECEIVE request forsocket ss gave result: rrrr

ExplanationIn issuing an RECV for a connection with a ProcOpsNetView the Command Server received an unexpectedresult and was unable to continue with the connection.

The variable ss is the socket number in use.The variable rrrr is the TCPIP reason that resulted(this is displayed as a number and text description).

System actionThe request from the ProcOps NetView is notprocessed. The connection with the ProcOps NetViewis closed.


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible. When corrected, reenter the request orrestart the PSM Control Program, whichever isappropriate.

ISQCS0215W TCPIP session on socket sscanceled by NetView node.

ExplanationIn issuing an RECV for a session with a ProcOpsNetView the Command Server received a record oflength zero. This usually indicates that the connectionhas been closed by the peer node (ProcOps NetView).

The variable ss is the socket number in use.



System actionThe request from the ProcOps NetView is notprocessed. The connection with the ProcOPs NetViewis closed.


System programmer responseInvestigate whether the receipt of a zero lengthmessage resulted from a session being closed at theProcOps NetView end. If so, this is normal. Otherwisedetermine the causes of the zero length message.

ISQCS0216I Command ccccc executed. Returncode = nn

ExplanationThe Command Server has executed a request receivedfrom either a remote ProcOps NetView or the CMSconsole. The request was interpreted to be a CP orCMS command and was executed on the PSM's virtualmachine.

The variable ccccc is the full text of the commandexecuted, including all blanks and specialcharacters.The variable nn is the return code that resultedfrom the execution of this command. Because thecommand is executed using a CMS PIPE command,the return code resulting may be that of the PIPEcommand. For example, an invalid command givesa return code of -27.

System actionNo special processing is done if the return code is notzero.



ISQCS0217I Main response is <rrrrrrrr>

ExplanationThe Command Server has executed a request from aremote ProcOps NetView and has produced output(none of which is yet sent). There may be several linesof output to be sent back to the remote NetView.

The variable rrrrrrrr is the full text of the first (andmain) response message to be sent, including allblanks and special characters.

System actionThe Command Server then attempts to send theresponses back to the NetView that entered therequest, using TCPIP WRITE requests.



ISQCS0218I Request rrrrrr done.

ExplanationThe Command Server has received a special ProcOpsrequest from either a remote ProcOps NetView or theVM console. The request has been executed withoutany observed problems.

The variable rrrrrrr is the full text of the request,including all blanks and special characters.

System actionOther messages, that result from the actual executionof the request, may also be returned to the caller.



ISQCS0219I rrrrrr cannot be done. No previousFP known.

ExplanationThe Command Server has received a request from theVM console. The request cannot be done because itrequires that a previous focal point be known. Forexample, an INITCOM request from the VM consolethat no FP is given in cannot be performed if there wasno previous known focal point that the Message Servercan be connected to.

The variable rrrrrrr is the full text of the request,including all blanks and special characters.



System actionThe request is not done.

Operator responseReenter the request. Specify an IP address in theINITCOM request from the console; or, issue theINITCOM request from a ProcOps NetView. In thelatter case, the IP address of the ProcOps NetView isits implicit operand.


ISQCS0220I Send request for response onsocket ss gave result: rrrr

ExplanationThe Command Server has completed processing arequest from a remote ProcOps NetView. Inattempting to send one of the response messagescreated, a TCPIP SEND request has been issued, buthas failed with the indicated result.

The variable ss is the socket number in use.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe request may or may not have executedcompletely. Some earlier responses to the requestmay have been sent successfully. Termination of therequest ends. The Command Server closes theconnection and makes itself available to receivefurther requests.


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible, then reenter the request and restart the PSM.

ISQCS0221I No parameters in ISQPARM DATAfile, or no file.

ExplanationAs part of the initialization of the PSM, an attempt hasbeen made to access and read the ISQPARM DATA file.

The request has been unsuccessful. Either there is nofile, or there are no valid data records in the file.

System actionThe PSM terminates.


System programmer responseEnsure that there is a ISQPARM DATA file and that itcontains the necessary definitions. When done, restartthe PSM.

ISQCS0222I No specification for sssssss inISQPARM DATA file.

ExplanationAs part of the initialization of the PSM, the ISQPARMDATA file has been read. A required definition for thekeyword indicated has not been found.

The variable sssssss is the required keyword thatwas not found.



System programmer responseEnsure that there is a definition in the ISQPARM DATAfile for the required keyword When done, restart thePSM.

ISQCS0223I Invalid component cccccc

ExplanationAn ISQTRACE or ISQACT request has been sent to thePSM. The PSM component (thread) referenced in therequest is not a valid value. No action is taken.

The variable cccccc is the component valueentered.

System actionThe request terminates.



Operator responseCheck that the request syntax is correct and that oneof the valid values was used. Reenter the request.


ISQCS0224I Trace for cccccc set to vvv

ExplanationAn ISQTRACE special request has been sent to thePSM. The PSM has changed the trace setting for thecomponent.

The variable cccccc is the component (thread) valueentered.The variable vvv is the requested trace setting ofthe PSM component: ON or OFF.

System actionThe request completes successfully.



ISQCS0225W ttttttt not known as a valid thread.

ExplanationAs part of the execution of either a TERMCOM orINITCOM request to the PSM, an attempt was made todelete a thread for a PSM component. The threadappeared to be not running.

The variable ttttttt is the name of the PSMcomponent's thread.


Operator responseIf there are subsequent problems, report this messageto your system programmer.

System programmer responseIf the ProcOps termination, or initialization does notcomplete correctly for this PSM, check that theindicated thread was really inactive.

ISQCS0226I Message Queue has nnn members.

ExplanationAn ISQUERY Q request was entered to determine thenumber of messages in the PSM's Message Queue.

The variable nnn is the number of messages in thequeue.

System actionThe request completes.



ISQCS0227I List of Events and Event MonitorsDefined.

ExplanationAn ISQCMD Q E request was entered to display theevents and event monitors currently in use by the PSM.This is the header line for the responses received. Thisis followed by two lists. One list contains the names ofall events known to the PSM Control program(including all its threads). The other list contains thenumerical IDs of the event monitors known. In somecases information about the event monitor is alsoshown.

System actionThe request is completed.



ISQCS0228E Invalid value vvvv in request rrrrrrr

ExplanationA special request was received by the PSM. The valueof one of its operands was incorrect.

The variable vvvv is the invalid value entered in therequest.The variable rrrrrr is the full text of the request,including all blanks and special characters.




Operator responseIf this is the result of an operator request, check forcorrect syntax. Reenter the request. If this is not anoperator request, report the problem to your systemprogrammer.


ISQCS0229E Component cannot be started. Stillactive.

ExplanationAn ISQACT request was received by the PSM to start athread. The thread is already apparently running.

The variable vvvv is the invalid value entered in therequest.The variable rrrrrr is the full text of the request,including all blanks and special characters.


Operator responseIf this is the result of an operator request, check forcorrect syntax. Reenter the request. If this is not anoperator request, report the problem to your systemprogrammer.


ISQCS0230E q is invalid queue designator. UseM (messages) or C (cmds).

ExplanationAn ISQCLEAR request was received by the PSM toclear a queue. The value entered for the queuedesignator is invalid.

The variable q is the invalid value entered for thequeue designator.


Operator responseDetermine why the thread is still running.


ISQCS0231E Queue cleared.

ExplanationAn ISQCLEAR request was received by the PSM toclear a queue. All entries in the queue are nowdeleted.

System actionThe request is complete.



ISQCS0232E ISQCLEAR failed with reason: rrrr

ExplanationAn ISQCLEAR request was received by the PSM toclear a queue. During the request aQueueReceiveImmed call was issued but did notcomplete successfully.

The variable rrrr is the reason code returned as aresult of the QueueReceiveImmed request.

System actionThe request does not complete. Some of the entries onthe queue may have been deleted. Some entries maystill remain on the queue. The request is terminatedand the PSM awaits further requests. Future actionsinvolving the queue may or may not execute correctly.


System programmer responseThe appendix "Return and Reason Code Values" in theCMS Application Multitasking manual containsexplanations for the reason code returned. Use this todetermine the cause of the message. If necessary,contact IBM for service.



ISQCS0233E SELECT request ended in error.Result: rrrr

ExplanationThe PSM Command Server is waiting for a connectionto a ProcOps NetView. As part of this process, a TCPIPSELECT call was issued. The call gave the error resultindicated.

The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe Command Server thread of the PSM terminates.


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible. When corrected, restart the PSM ControlProgram. If this is not possible, contact IBM forservice.

ISQCS0234E Message Server initialized, but notMessage Handler.

ExplanationAs part of the initialization of a connection to a PSM, aninternal INITCOM request was sent to the PSM. ThePSM Message Server thread was initialized but itsrequired Message Handler thread appeared not toinitialize.

System actionNo further action is taken.

Operator responseInvestigate other messages issued by the PSM,specifically any from the Message Handler thread todetermine the cause. One possible reason for thismessage is that the thread did initialize, but tooklonger to do so than the Command Server waited. Ifpossible, resolve the problem and (re-)issue theISQXIII request for the target system. If the problempersists, stop the PSM using the STOPALL request, andrestart the PSM virtual machine. Then reissue theISQXIII command for the target system. If theproblem persists report the problem to your systemprogrammer.

System programmer responseContact IBM for service.

ISQCS0235E Message Handler initialized, butnot Message Server.

ExplanationAs part of the initialization of a connection to a PSM, aninternal INITCOM request was sent to the PSM. ThePSM Message Handler thread was initialized but itsrequired Message Server thread appeared not toinitialize.


Operator responseInvestigate other messages issued by the PSM,specifically any from the Message Server thread todetermine the cause. One possible reason for thismessage is that the thread did initialize, but tooklonger to do so than the Command Server waited. Ifpossible, resolve the problem and (re-)issue theISQXIII request for the target system. If the problempersists, stop the PSM using the STOPALL request, andrestart the PSM virtual machine. Then reissue theISQXIII command for the target system. If theproblem persists report the problem to your systemprogrammer.


ISQCS0236E Neither Message Server norMessage Handler initialized.

ExplanationAs part of the initialization of a connection to a PSM, aninternal INITCOM request was sent to the PSM.Neither the PSM Message Handler nor the MessageServer thread appeared to be initialized correctly.


Operator responseInvestigate other messages issued by the PSM, todetermine the cause. One possible reason for thismessage is that the threads did initialize, but tooklonger to do so than the Command Server waited. Ifpossible, resolve the problem and (re-)issue the



ISQXIII request for the target system. If the problempersists, stop the PSM using the STOPALL request, andrestart the PSM virtual machine. Then reissue theISQXIII command. If the problem persists report theproblem to your system programmer.


ISQCS0237W TERMCOM may not havesucceeded.

ExplanationAs part of the termination of a connection to a PSM, aninternal TERMCOM request was sent to the PSM. Eitherthe PSM Message Handler, or the Message Serverthread, or both appeared to be not terminatedcorrectly. This message may also be issued when aconnection to a PSM is initialized, because any existingmessage processing is terminated first.


Operator responseInvestigate other messages issued by the PSM, todetermine the cause. One possible reason for thismessage is that the threads did terminate but that theindications of their termination were not set correctly.Another possible reason is that one or both threadswere not active. If this is part of a full termination(STOPALL) check that all threads terminate on the VMmachine and that it returns to a CMS prompt. In thiscase the threads did terminate correctly.

Otherwise, at the VM console of the PSM, issue the HXcommand repeatedly to terminate any threads untilthe CMS prompt can be achieved with a BEGINcommand. The PSM can then be restarted if desired.

If this is part of an ISQXCLS or ISQSTOP request, enteran INITCOM request followed by a TERMCOM requestand check that these commands execute correctly.

If this is part of an ISQXIII request, it is followed by anattempt to start the Message Handler and MessageServer threads. If these initialize correctly, all is well,and the message can be ignored.

If the problem persists report the problem to yoursystem programmer.


ISQCS0238W tttttttt thread may not havestopped.

ExplanationAs part of the termination of a connection to a PSM, aninternal TERMCOM request was sent to the PSM. Eitherthe PSM Message Handler, or the Message Serverthread appeared not to terminate correctly. Thismessage may be issued when a connection to a PSM isinitialized, because any existing communication is thenterminated first.


Operator responseInvestigate other messages issued by the PSM, todetermine the cause. One possible reason for thismessage is that the threads did terminate but that theindications of their termination were not set correctly.If this is part of a full termination (STOPALL) check thatall threads terminate on the VM machine and that itreturns to a CMS prompt. In this case the threads didterminate correctly.

Otherwise, at the VM console of the PSM, issue the HXcommand repeatedly to terminate any threads untilthe CMS prompt can be achieved with a BEGINcommand. The PSM can then be restarted if desired.

If this is part of an ISQXCLS or ISQSTOP request, enteran INITCOM request followed by a TERMCOM requestand check that these commands execute correctly.

If the problem persists report the problem to yoursystem programmer.


ISQCS0239E QueueReceiveImmed request forCOMMAND queue gave result: rrrr

ExplanationInternally within the PSM, any PSM request entered atthe VM console is first entered on a COMMAND queueand later read from the queue to be executed. Theread from the queue failed.

The variable rrrr gives the reason code returned bythe call to QueueReceiveImmed.




Operator responseReport the problem to your system programmer.Restart the PSM.


ISQCS0240E Invalid operand: oooo. Enter Q(Message Queue) or E (Events).

ExplanationAn ISQQUERY special request was issued to the PSM,but the operand specified was not valid.

The variable oooo is the invalid operand.


Operator responseCorrect the syntax and reenter the request.


ISQCS0242W Command SET SECUSER gave rc =rrrr

ExplanationAs part of the processing for an ISQXIII or ISQXCLSrequest, the CP SET SECUSER command is used tochange the secondary user specification of a guestmachine that is a target system. The command gave anunexpected return code. (This may also be seen whenISQSTART and ISQSTOP are done.)

The variable rrrr is the return code from the CP SETSECUSER command.

System actionOperation continues.

Operator responseSee the CP Command and Utility Reference manual forthe explanation of the return code. (This is the numericpart of the HCPnnn message.) If necessary, informyour system programmer.


ISQCS0244E Authorization token does notmatch. Request not done.

ExplanationA request was sent to the PSM from a ProcOpsNetView. The authorization token embedded in therequest did not match that expected by the PSM.



System programmer responseCheck that the authorization token for the PSM, whichis specified in the ProcOps customization dialog,matches that specified for the SECURITY keyword inthe ISQPARM DATA file on the PSM.

If the change is needed on ProcOps, correct thedialogs, rebuild the ProcOps control file and restartProcOps using the new control file.

If the change is needed on the PSM, stop the PSM byissuing ISQXCLS for all its active target systems.Correct the ISQPARM DATA file and restart the PSM.Then issue ISQXIII for one or more of its targetsystems, as desired.

ISQCS0245E Cannot close PSM itself.

ExplanationAn internal CLOSE request was sent to the PSM. Theguest machine name in the CLOSE request was thename of the PSM. This is not valid.


Operator responseNone. This is an invalid request.


ISQCS0246E Request rejected. Remote nodecannot INITCOM for another node.



ExplanationThe PSM has received an internal INITCOM requestfrom a ProcOps NetView. The INITCOM has requestedinitialization for a node other than its own. This is notvalid.




ISQCS0248W Waiting for TCPIP virtual machine<vvvvvvvv> to be active.

ExplanationThe PSM has started up. Before it can do its TCPIPinitialization, it checks whether the desired TCPIPvirtual machine is running. The desired virtual machineis not running.

The variable vvvvvvvv is the name of the desiredTCPIP virtual machine.

System actionThe PSM control program continues to check, atregular intervals, whether the desired TCPIP virtualmachine is active. When it finds the machine active,normal initialization is continued. No furtherISQCS0248W messages are issued

Operator responseThis message should normally only be issued when theVM system is starting up and a PSM is started beforeTCPIP becomes active.

If it occurs at other times log on to the VM system andcheck that the desired TCPIP virtual machine is activeby issuing a CP QUERY command (for example, CPQUERY TCPIP).

The desired machine name is set in the ISQPARMDATA file. If no value is set in this file, a default nameof TCPIP is used.

If necessary, stop the PSM by issuing the HX commandrepeatedly until the CMS prompt is displayed.

System programmer responseCheck that the value of the TCPIPNAME parameter inthe ISQPARM DATA file is set correctly. If necessary,correct it and restart the PSM.

ISQCS0249I Guest...Status...

ExplanationThe PSM has received an internal PSMDATA request.This gives status of the PSM and guest machines. Thisis the heading line of the response and is followed byISQCS0250I data messages.

System actionNone.



ISQCS0251I Request <rrrrrrrr> received fromremote NetView.

ExplanationThe Command Server has received a request from aremote ProcOps NetView.

The variable rrrrrrrr is the full text of the commandexecuted, including all blanks and specialcharacters.

System actionNone.



ISQCS0252I Component... Status...

ExplanationThe PSM has received an ISQSTATUS request. Thisacts as a heading line for subsequent ISQCS0253Imessages that give the component name and status ofparts of the PSM application.



System actionNone.



ISQCS0254I Invalid value <vvvvv> forISQPARM parameter <ppppp>.

ExplanationAs part of PSM initialization, the ISQPARM file hasbeen read. The value specified for a parameter isinvalid.



System programmer responseCorrect the parameter in error. Restart the PSMprogram.

ISQMS0301I Message Server waiting forconnection to NetView.

ExplanationThe Message Server thread in the PSM has beenstarted and has issued a TCPIP LISTEN request. Itawaits a ProcOps NetView CONNECT request.

System actionThe PSM awaits a ProcOps NetView CONNECT request.

Operator responseWhen an ISQXIII or ISQSTART is issued on thecontrolling ProcOps NetView, messages indicating thata connection has been established should be issued bythe PSM. If they are not, check for other errormessages on the ProcOps NetView. If necessary,inform your system programmer.

System programmer responseCheck the NetView NETLOG for any messagesindicating why the connection is not made.

ISQMS0302E ACCEPT issued by Message Servergave result: rrrrr

ExplanationIn issuing an ACCEPT for an incoming CONNECT theMessage Server received an unexpected result andwas unable to complete the connection.


System actionThe Message Server thread terminates.



ISQMS0303I Session accepted by MessageServer. New session socket: ss

ExplanationThe Message Server thread received an incomingCONNECT.

The variable ss is the TCPIP socket numberassigned to the new connection created by theCONNECT.

System actionThe Message Server continues to create theconnection.





ISQtt0304W SETSOCKOPT issued by ccccccccthread for socket ss gave resultrrrr

ExplanationAs part of the process of initializing a TCPIP socket, athread has issued a TCPIP SETSOCKOPT call to set theoptions for the connection. An unexpected result hasbeen returned.

The variable ccccccc is the name of the PSM threadthat was running.The variable ss is the socket number in use.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe thread continues. The connection does not haveall its desired options. This can cause other errors,especially if the thread or the PSM is stopped andrestarted within a short period of time.



ISQMS0305I Handshake complete for MessageServer connection.

ExplanationAs part of the process of setting up a incomingconnection, the Message Server receives and checksan authorization token from the ProcOps NetView. Thishas been done successfully. There is now a fullyestablished connection between the PSM and ProcOpsNetView for the receipt of message traffic.

System actionThe PSM begins to send any messages it receives toProcOps NetView.



ISQMS0306I TCPIP error on Message Serverconnection. Result rrrr. Restarting.

ExplanationIn attempting to maintain a connection between itsMessage Server and a ProcOps NetView, the MessageServer has sustained a TCPIP error. Other errormessages from the Message Server appear before this.


System actionThe Message Server attempts to restart the session tothe same ProcOps NetView.


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible.

ISQMS0307E QueueOpen for queue qqqq gaveRC = cccc. Reason = rrrrrr

ExplanationIn attempting to maintain a connection between itsMessage Server and a ProcOps NetView, the MessageServer has sustained a TCPIP error. Other errormessages from the Message Server appear before this.


System actionThe Message Server attempts to restart the session tothe same ProcOps NetView.


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of the



return code given. Use this to resolve the error, ifpossible.

ISQtt0308E LISTEN by ccccccc on socket ssfailed. Result: rrrrr

ExplanationAs part of the process of setting up a incomingconnection, a thread has issued a TCPIP LISTEN call toawait a connection. An unexpected result has beenreturned.

The variable ccccccc is the name of the PSM threadthat was running.The variable ss is the socket number in use.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe thread terminates. (If the thread is the CommandServer, the PSM terminates.)


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Referencemanual for a description of thereturn code given. Use this to resolve the error, ifpossible. When corrected, restart the PSM ControlProgram. Otherwise, contact IBM for service.

ISQMS0309E GETHOSTID issued by ccccccccfailed. Result: rrrr

ExplanationAs part of the process of initializing TCPIP, a threadhas issued a TCPIP GETHOSTID call. An unexpectedresult has been returned.

The variable ccccccc is the name of the PSM threadthat was running.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe thread terminates. (if the thread is the CommandServer, the PSM terminates.).


System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible. When corrected, restart the PSM ControlProgram. Otherwise, contact IBM for service.

ISQtt0310E SOCKET issued by ccccccc failed.Result: rrrrr

ExplanationAs part of the process of obtaining a TCPIP socket, athread has issued a TCPIP SOCKET call. Anunexpected result has been returned.

The variable ccccccc is the name of the PSM threadthat was running.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).

System actionThe thread terminates. (If the thread is the CommandServer, the PSM terminates).



ISQtt0311E BIND issued by ccccccc for socketss failed. Result: rrrrr

ExplanationAs part of the process of obtaining a TCPIP socket, athread has issued a TCPIP BIND call. An unexpectedresult has been returned.

The variable ccccccc is the name of the PSM threadthat was running.The variable ss is the socket number.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).






ISQMS0312I QueueReceiveImmed request forMESSAGES queue gave result: rrrr

ExplanationThe Message Server has issued aQueueReceiveImmed call to obtain messages from theMessages Queue. An unexpected result has beenreturned.

The variable rrrr is the reason code.

System actionThe Message Server thread terminates.


System programmer responseThe explanation of the reason code is found in theappendix "Return and Reason Code Values" in the CMSApplication Multitasking manual. Use this to resolvethe problem, if possible, then restart the messageprocessing threads. If this is not successful, stop andrestart the PSM. In both cases messages stored on thequeue will be lost. Report the problem to your IBMService Center.

ISQtt0313E FCNTL issued by ccccccc for socketss failed. Result: rrrrr

ExplanationAs part of the process of obtaining a TCPIP socket, athread has issued a TCPIP FCNTL call to set the socketin non-blocking mode. An unexpected result has beenreturned.

The variable ccccccc is the name of the PSM threadthat was running.The variable ss is the socket number.The variable rrrrr is the TCPIP result (this isdisplayed as a number and text description).




ISQMS0314E Message Handler has failed.

ExplanationThe Message Server has received a signal that theMessage Handler has failed. This message is sent asan unsolicited message to the ProcOps NetView.

System actionThe message is used by ProcOps NetView to set thestatus of the target systems managed by the PSM.

Operator responseCheck why the Message Handler has failed. (Possiblereasons include the filling of the MESSAGES Queue.)To restart the Message Handler use the ISQACT MHcommand from the PSM.


ISQMS0315E CONNECT received from nodenn.nn.nn.nn that is not current FP:mm.mm.mm.mm

ExplanationThe Message Server has received a request toCONNECT from a node that is not the current ProcOpsfocal point. That is, it is not the node that last issued aINITCOM request.

This can occur if an ISQSTART or ISQXIII request isissued from one ProcOps NetView without issuing aISQXCLS or ISQSTOP command on another ProcOpsNetView that is the current focal point.

The variable nn.nn.nn.nn is the dotted decimal IPaddress of the node attempting to CONNECT.



The variable mm.mm.mm.mm is the dotted decimalIP address of the node that last issued an INITCOMrequest to this PSM.(An INITCOM request is issuedwhen a ISQXIII command is first issued for a targetsystem on that PSM. It can also be issued whenISQSTART command is issued, if there are targetsystems defined to initialize automatically.)

System actionThe request to connect is denied.

Operator responseCheck why the other PSM is trying to connect. If thewrong ProcOps NetView is the current focal point,issue a ISQSTOP request (or ISQXCLS requests for thePSM's target systems) from that NetView. Then issueISQSTART (or ISQXIII for one or more target systemson that PSM) from the NetView that is to be the focalpoint.


ISQMS0316I Message Handler has started.

ExplanationThe Message Server has received a signal that theMessage Handler has started. This message is sent asan unsolicited message to the ProcOps NetView.

System actionThe message is used by ProcOps NetView to set thestatus of the target systems managed by the PSM.



ISQMS0317E WRITE for socket ss failed withTCPIP error: rrrrr

ExplanationThe Message Server thread has issued a TCPIP WRITErequest to send data to the ProcOps NetView. Therequest failed.

The variable ss is the socket number.The variable rrrrr is the return code from therequest

System actionThe Message Server thread terminates. Target systemson the PSM are closed.

Operator responseReport the problem to your system programmer. IssueISQXIII requests for all target systems on the PSMthat were active at the time of the failure. Ensure thatthe requests are successful.

System programmer responseRefer to the "REXX Sockets Return Codes" section ofthe REXX/VM Reference manual for a description of thereturn code given. Use this to resolve the error, ifpossible.

ISQMS0318E WRITE for socket ss timed out.

ExplanationThe Message Server thread has issued a TCPIP WRITErequest to send data to the ProcOps NetView. Therequest could not be satisfied immediately. TheMessage Server waited, but after an interval of timethe WRITE request was still not possible.

The variable ss is the socket number.

System actionThe Message Server thread terminates. Target systemson the PSM are closed.

Operator responseReport the problem to your system programmer. IssueISQXIII requests for all target systems on the PSMthat were active at the time of the failure. Ensure thatthe requests are successful.


ISQtt0401E QueueSend for qqqqqq failed withRC = cccc. Reason: rrrr

ExplanationA PSM thread issued a QueueSend to put an entry(message or command) on to the indicated queue. Itreceived an unexpected return code.

The variable qqqq is the name of the queue.The variable cccc is the return code.The variable rrrr is the reason code.



System actionThe thread terminates.



ISQtt0402I Command <cccccc> entered.

ExplanationThe Console Server thread received a request and putit on the Command Queue.

The variable cccccc is the command, entered in full.

System actionThe thread continues. The command should be thenbe processed by the Command Server thread.



ISQLG0505E Logger failed to retrieve traceddata RC = cccc. Reason = rrrr.

ExplanationThe Logger thread issued an EventRetrieve to obtaindetails of an event that was signaled to it. It receivedan unexpected return code.

The variable cccc is the return code.The variable rrrr is the reason code.

System actionThe Logger thread ignores the event and it is notlogged.



ISQMH0601E Unrecoverable error for MessageHandler pipe stage. *MSG Servicemay be damaged and notrestartable.

ExplanationThe Message Handler PIPE stage (ISQRGIUC) hasencountered a problem that means it cannot continue.Other error messages should precede this, indicatingdetails of the actual error.

System actionThe stage completes. This, in turn, should cause theMessage Handler thread to complete. Because of thenature of the failure it may not be possible to recyclethe message processing threads, and it may benecessary to stop and restart the PSM virtual machine.

Operator responseSee the earlier messages to determine the actualproblem.

System programmer responseSee the earlier messages to determine the actualproblem.

ISQMH0602E MESSAGES Queue has reached itsmaximum size. Queuing stopped.

ExplanationThe Message Handler PIPE stage (ISQRGIUC) hasdetermined that the number of messages in theMessages Queue exceeds the threshold valuespecified by the installation in the ISQPARM DATA file.

System actionQueuing of messages is halted. The PIPE stagecompletes. This should cause the Message Handlerthread to complete.

Operator responseDetermine whether the cause lies elsewhere. (Forexample, a connection to the ProcOps NetView may belost.) Restart message processing when the problem iscleared, by entering the ISQXIII command for alltarget systems on the PSM that should be active. Thiswill delete any messages in the queue at the time.



System programmer responseReview the threshold number of messages specified.Change the value specified in ISQPARM DATA andrecycle the PSM, if necessary.

ISQtt0701E CREATE_EVENT_MONITOR routinecalled with no events formmmmmmmm

ExplanationA call was made to the internalCREATE_EVENT_MONITOR routine, but no eventnames were specified.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor to becreated.


Operator responseReport the problem to your system programmer. If thethread is the Logger or Console Server messageprocessing can continue, but the facilities of the failedthread are not available. If any other thread fails, stopthe PSM (if it has not stopped) and restart it.


ISQtt0702E EventMonitorCreate request formmmmmmmm ended with RC =cccc. Reason: rrrr.

ExplanationA call was made to the internalCREATE_EVENT_MONITOR routine, but theEventMonitorCreate call it issued gave an unexpectedresult.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor.The variable cccc is the return code from theEventMonitorCreate call.The variable rrrr is the reason code.




ISQtt0703E EventWait request formmmmmmmm resulted in RC=cccc. Reason = rrrr

ExplanationA call was made to the internal WAIT_FOR_EVENTroutine, but the EventWait call it issued gave anunexpected result.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor.The variable cccc is the return code from theEventWait call.The variable rrrr is the reason code.




ISQtt0704E EventWait call for mmmmmmmmresulted in event flag setting ssssfor eeeeeeee

ExplanationA call was made to the internal WAIT_FOR_EVENTroutine, but the EventWait call that it issued resulted inan error setting for one of the events that were waitedupon.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor.The variable ssss is the unexpected setting thatresulted.



The variable eeeeeeee is the name of the event.




ISQtt0705E CREATE_EVENT routine calledwith too many or no operands:<oooo>.

ExplanationA call was made to the internal CREATE_EVENTroutine, but either no event name was specified, ormore than one event name was specified.

The variable oooo is the operands, if any, specifiedin the call.




ISQtt0706E EventCreate request for eventeeeeeeee ended with RC = cccc.Reason: rrrr

ExplanationA call was made to the internal CREATE_EVENTroutine, but the EventCreate call it issued gave anunexpected result.

The variable eeeeeeee is the event name.The variable cccc is the return code from theEventCreate call.

The variable rrrr is the reason code




ISQtt0707E cccccccc thread has suffered afatal error and is ending.

ExplanationA thread indicated has suffered a fatal error thatmeans that it cannot continue.

The variable cccccccc is the name of the thread.


Operator responseThis message follows other messages that detail theactual problem. If necessary, report the problem toyour system programmer. If the thread is the Logger orConsole Server message processing can continue, butthe facilities of the failed thread are not available. Ifany other thread fails, stop the PSM (if it has notstopped) and restart it.


ISQtt0708I cccccccc thread canceled.

ExplanationA request has been entered that cancels the indicatedthread. The request has been signaled to the threadand it is beginning its processing for an orderlytermination.







ISQtt0709I cccccccc thread ending...

ExplanationEither as a result of a fatal error or a cancel request, athread has ended. (This message is issued by thethread itself as its last action, so the thread should bedeleted immediately afterwards.)



Operator responseIf this is issued as a result of a fatal error, earliermessages detail the error.


ISQtt0710I cccccccc thread entered.

ExplanationA thread has begun execution.


System actionThe thread continues.



ISQtt0711I cccccccc thread initialized.

ExplanationA thread has completed its initialization.





ISQtt0712W EvMonReset mmmmmmmm issuedby cccccccc gave RC = cccc. Reasonrrrr

ExplanationA call was made to the internalDELETE_EVENT_MONITOR routine. TheEventMonitorReset call it issued gave an unexpectedresult.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor.The variable ccccccc is the name of the thread.The variable cccc is the return code from theEventMonitorReset call.The variable rrrrr is the reason code.




ISQtt0713W EvMonDelete mmmmmmmmissued by cccccccc gave RC = cccc.Reason rrrr

ExplanationA call was made to the internalDELETE_EVENT_MONITOR routine. TheEventMonitorDelete call it issued gave an unexpectedresult.

The variable mmmmmmmm is the name usedwithin the thread to identify the event monitor.



The variable ccccccc is the name of the thread.The variable cccc is the return code from theEventMonitorDelete call.The variable rrrrr is the reason code.




ISQtt0714W EventSignal request by ccccccccfor eeeeeeee gave RC = cccc.Reason: rrrr

ExplanationA call was made to the internal SIGNAL_EVENTroutine. The EventSignal call it issued gave anunexpected result.

The variable eeeeeeee is the event name.The variable ccccccc is the name of the thread.The variable cccc is the return code from theEventMonitorDelete call.The variable rrrrr is the reason code.




ISQtt0715W QueueCreate for qqqqqqqq failedwith RC = cccc. Reason: rrrr

ExplanationA call was made to an internal routine to create amulti-tasking queue. The QueueCreate call it issuedgave an unexpected result.

The variable qqqqqqqq is the name of the queue.The variable ccccccc is the name of the thread.The variable cccc is the return code from theQueueCreate call.The variable rrrrr is the reason code.




ISQtt0717E NOVALUE error in line llll

ExplanationNote: Always followed by message ISQtt0718E.

The variable llll is the line number in the REXXprogram that gave the condition.




ISQtt0718E Statement in error is: stmt

ExplanationThe variable stmt is the REXX statement thecondition occurred in.



ISQtt0719E SYNTAX error tttt in line llll: xxxxx

ExplanationNote: Always followed by Message ISQtt0718E.

The variable tttt is the REXX error type.The variable llll is the line number in the REXXprogram the condition occurred in.The variable xxxxx is an explanation of the REXXerror type.




ISQtt0720E ERROR condition raised instatement llll RC: cccc

ExplanationNote: Always followed by Message ISQtt0718E.

The variable llll is the line number of the statementin the REXX program that caused the error.The variable cccc is the return code from thefunction or command in error.


Operator responseReport the problem to your system programmer. If thethread is the Logger or Console Server, messageprocessing can continue, but the facilities of the failedthread are not available. If any other thread fails, stopthe PSM (if it has not stopped) and restart it.


ISQtt0721E Recursive error in ttttttttt. Threadending.

ExplanationAn recursive error has occurred in a thread. The threadis ending.

The variable tttttttt is the name of the thread.

System actionThe thread terminates. Note that this message isissued only in its English language version. This isbecause a likely cause of recursive errors is when errormessages are created.

Operator responseReport the problem to your system programmer.Earlier error messages may be seen that identify theoriginal problem. If the failing thread is the Logger orConsole Server, message processing can continue, butthe facilities of the failed thread are not available. Ifany other thread fails, stop the PSM (if it has notstopped) and restart it.


ISQtt0722E In ISQADDRS file, x:x:x:x:x:x:x:x isnot a valid IPv6 hexadecimaladdress.

ExplanationAs part of the initialization of the Command Serverthread, the ISQADDRS DATA file was read in order tocreate a list of valid IP addresses for ProcOps NetViewfocal points. The entry quoted was entered in IPv6hexadecimal form, but is not a valid IP address.

The variable x:x:x:x:x:x:x:x is the entry asinterpreted from the file.



System programmer responseCorrect the entry in the ISQADDRS DATA file. Restartthe PSM control program in its virtual machine.

ISQtt0723I In ISQADDRS file, aaaaa could notbe resolved as a valid hexadecimaladdress in IPv6 network.



ExplanationAs part of the initialization of the Command Serverthread in the IPv6 environment, the ISQADDRS DATAfile was read in order to create a list of valid IPaddresses for ProcOps NetView focal points. The entryquoted cannot be resolved as a valid hexadecimal IPv6address. Host names are not yet supported in the IPv6environment.

The variable aaaaa is the entry as read from thefile.



System programmer responseCorrect the entry in the ISQADDRS DATA file. Use thecorrect hexadecimal IPv6 address or force the IPv4protocol by defining the entry PSMIPV4=Y in theISQPARM DATA file to resolve host names to IPv4addresses. Restart the PSM control program in itsvirtual machine.



Appendix A. Abend Codes and Reason Codes IssuedBy the Automation Manager

Communication DST and Automation Manager Abend CodesThis section describes the abend codes and reason codes that the automation manager may issue usingthe ABEND macro. If one of these abend codes occurs, contact your IBM Support Center.

With ABEND CODE 3998 the following reason code can be issued:X'01'

The DST abends due to a severe MQSeries related problem during MQSeries outbound or MQSeriesreceive. The DST is intentionally terminated and will be restarted by SA z/OS due to message trappingof message DSI172I.

With ABEND CODE 3999 the following reason codes can be issued:X'01'

PLX call stack storage cannot be obtained because no storage is availableX'02'

PLX call stack storage is too small. PLX call stack storage has been obtained but a nested programdoes not get enough storage from the stack.

X'0A'List of ECB to be posted exceeds the limit (16). Module INGPXIMV detected an error while processinga time exit.

X'0B'List of ECB to be posted exceeds the limit (16). Module HSAAPIMV detected an error while processinga time exit.

X'10'The threshold for the loop detector has been exceeded.

X'11'There has been an attempt to add a duplicate list element.



Appendix B. Response Messages, Error Strings,Condition Codes

Response Messages (AOFA0000–AOFA0099)Automation returns the following messages to indicate command-invocation, parameter-list, orparameter-resolution problems.

AOFA0000

ExplanationThis response message is returned as an indicator ofproblems with command invocation, parameter lists,or parameter resolution. If the AOFA0000 responsemessage is returned from the INGHWCMD commandlist, its data portion is an error string as listed below. Ifthe AOFA0000 response message is returned from theINGHWCOM communication task command processor,its data portion contains a condition code from 001through 033 (see “Hardware Communication TaskCondition Codes "00B00xxx"” on page 554).Error type Error stringsEnvironment error

Required_System_Automation_Environment_is_not_completeNetView_task_environment_must_be_CMD_LOW_for_opid()Command_not_allowed_to_run_under_PPT_task_opid()

Parameter error

Proc_or_Sys_name_and_HW_function_name_is_requiredp_session_type_not_SYNC/ASYNC/blankTimeout_range_tttt_already_defined.Timeout_tt_out_of_range_1-59.Timeout_specification_range_tt_is_not_valid.Timeout_specification_tt_is_not_valid.Timeout_specification_tttt_ends_invalid.TRACE_option_must_be_ON_or_OFFhwcmd_with_FORCE_operand_is_not_valid.hwcmd_is_not_a_supported_HW_function.p_must_be_a decimal_integer_value_or_ALLp_EXTERNAL_CPU_definition_errorCN_Activation_profile_name_not_alphanumericCN_Profile_name_is_a_positional_parmp_does_not_support_target_wildcard.p_Parm_is_in_wrong_position.lparm_load_parm_length_must_be_8.devnum_device_address_not_hexadecimal.devnum_mandatory_load_address_invalid.lval_Load_value_definition_error.lval_Load_value_is_a_positional_parm.pn_load_profile_name_not_alphanumeric.pn_Load_profile_definition_error.

pn_Profile_name_is_a_positional_parm.spc_P_and_LV_specs_are_mutually_exclusive.name_invalid_chars_in_proc_or_sys_name.name_name_longer_than_8_characters.parm_Parm_is_unknown_or_in_wrong_position.evt_is_an_invalid_event_typeevt_defined_more_than_onceALL_must_be_the_1st_or_unique_event_parmEvent_specification_is_requiredp_variable_name_APNAME_requiredp_APNAME_datalen_must_be_1-16_charsp_APNAME_data_must_not_contain_blanksp_Applid_definition_errorp_ON/OFF_missing_errorp_invalid_image_cntl_varnamep_YES/NO_missing_errorp_variable_is_READONLYp_numeric_value_out_of_rangep_value_not_numericp_value_for_variable_missingp_command_parm_not_supportedp_command_function_not_supportedp_profile_name_blank_or_gt_16charp_act_profile_varname_missingp_act_profile_vardata_def_errorp_Out_of_Range(0.01-255.0)p_processor_value_missingp_EAST/WEST_missing_errorp_value_is_not_0_15_30_or_45p_STD/LPAR_missing_errorp_PRTT_datalen_must_be_1_charp_PRTT_data_must_not_contain_blanksp_PRTT_value_not_0_or_1p_PRT_len_must_be_1-3_bytesp_PRT_value_not_1-100p_PRT_not_whole_numberp_PRT_value_not_numericp_variable_name_not_correctp_Valid_only_for_IMAGE/GROUP_profilesp_v_GROUP_or_IMAGE_prf_only

Resolve error

sysname_for_CFs_LOAD/SYSRESET_are_not_supported.sysname_type_specification_missing_or_invalid.sysname_null_string_BCP_command_error.pname_has_invalid_CPC_address_format.pname_has_no_IP_address_defined.pname__has_no_processor_address_defined.name_name_is_not_defined.pname_name_not_valid_for_CPC_command.pname_has_no_AUTHTKN_defined.No_HWOPER_task_defined.

Response Messages (AOFA0000–AOFA0018)


pname_Interface_protocol_definition error.

Check Task

hwtask_reached_QueueLimit_qlimhwtask_task_msqqeue_data_is_invalidhwtask_task_is_not_availablehwtask_task_module_INGHWCOM_not_running hwtask_RESET_failed

Hardware Interface

BCP_internal_interface_is_disabled_or_not_activeBCP_internal_interface_status_cannot_be_determined

Authorization error

hwcmd_has_undefined_access_levelacclevel_to_resname_not_allowed_for_userBadRC_during_access_chk_for_resname

Examples1. The INGHWCMD command failed returning an

AOFA0000 error string:

AOFA0000 Resolve error: "MYSYS"_is_not_a_predefined_system_or_CF-name

2. The INGHWCMD command failed. MessageAOFA0000 was returned by INGHWCOM commandprocessor. The condition code 00B00003 indicatesthat an unknown communication interface namewas passed from INGHWCMD to INGHWCOM.

AOFA0000 GETISTAT STATUS(REJECTED) CONDITION(00B00003) SENSE() CPCSNAME() TSTIME(020111073708)

AOFA0001

ExplanationThis response message is returned from a request ofthe following hardware command functions:ACTIVATE, DEACTIVATE, LOAD, OOCOD, RESTART,SYSRESET, START, STOP, CBU, EXTERNAL, RESERVE

Examples1. The hardware function STOP was successfully

performed for system KEY7:

AOFA0001 STOP KEY7 STATUS(SUCCESS) CPCSNAME(DEIBMD1.X7E1FA0A) TSTIME(020111135810)

2. The hardware function SYSRESET was rejected byINGHWCOM. The condition code 00B00056indicates that system KEY6 is still operational andcannot be disrupted. In order to perform adisruptive hardware operation, the FORCE optionmust be specified:

AOFA0001 SYSRESET KEY6 CONDITION(00B00056)SENSE()CPCSNAME(DEIBMD1.X7E1FA0A) TSTIME(020111142827)

3. The first command successfully sets a reserve forapplication ID IPSFO. The second command liststhe reserve ID as stored in the Support Element.The third command fails because it tries to releasethe reserve with an invalid reserve ID (that is, it isnot used for the reserve). The fourth command isidentical to a RESERVE LIST command. It shows areserve ID that is identical to the CPCSNAME. Thisindicates that on the SE, EXCLUSIVE CONTROL hasbeen set manually. In order to successfully releasea reserve, the RESERVE OFF request must be made,using the same application name (reserve ID) as forthe RESERVE ON request.

AOFA0001 RESERVE FREEWAY STATUS(SUCCESS) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040828172045)

INGHWCMD FREEWAY RESERVE LIST

AOFA0001 RESERVE FREEWAY STATUS(SUCCESS) APPLNAME(0AUTOOPS.IPSFO) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040828172315)

INGHWCMD FREEWAY RESERVE WHOKNOWS OFF

AOFA0001 RESERVE FREEWAY STATUS(FAILED) CONDITION(0B20000) SENSE(0838001B 0000 00000000) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040828172445)

INGHWCMD FREEWAY RESERVE

AOFA0001 RESERVE FREEWAY STATUS(SUCCESS) APPLNAME(DEIBMIP1.IP3TVMA0) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040828173117)

AOFA0002

ExplanationThis message is the response to an INITCOM request.INITCOM establishes a session between INGHWCOMand the Processor Support Element of the addressedhardware.



ExampleThe session between the INGHWCOM and theprocessor Support Element of the CPCDEIBMD1.X7E1FA0A, configured with the hardwarename "YORAMA," is established successfully:

AOFA0002 INITCOM YORAMA STATUS(SUCCESS) CPCSNAME(DEIBMD1.X7E1FA0A)TSTIME(020111143851)

Note: For Processor Operations connections, INITCOMis executed as part of the host-based commandISQXIII (Initialize target connection).

AOFA0003

ExplanationThis message is the response to an INITCOM requestto an HMC. INITCOM establishes a session betweenINGHWCOM and the addressed CPC. In case the CPCis defined over an HMC, for each CPC managed by theHMC, one extra line is shown in the report.

ExampleThe session between INGHWCOM and the HMC whereSERVER1 is a member, is established successfully.Implicitly, the sessions to the other CPCs of that HMCare also established:

AOFA0003 INITCOM SERVER1 STATUS(SUCCESS) TSTIME(030117084549) AOFA0003 INITCOM CPCSNAME(DEIBMIPS.IP3T1000) AOFA0003 INITCOM CPCSNAME(AUIBMQXP.QXPTHES1) AOFA0003 INITCOM CPCSNAME(AUIBMQXP.QXPTHES9) AOFA0003 INITCOM CPCSNAME(DEIBMD1.X7E1FA0A) AOFA0003 INITCOM CPCSNAME(DEIBMD1.X7F1E30A) AOFA0003 INITCOM CPCSNAME(DEIBMD1.X7F1F20A) AOFA0003 INITCOM REPORT COMPLETE

Note: For Processor Operations connections, INITCOMis executed as part of the host-based commandISQXIII (Initialize target connection).

AOFA0004

ExplanationThis report is the response to a TERMCOM request.TERMCOM ends a session between INGHWCOM andthe Processor Support Element of the addressedhardware.

Examples1. The session between the INGHWCOM and the

Processor Support Element of the CPCUSIBMSC.SCZP107 configured with the hardwarename "P701" is terminated successfully:

AOFA0004 TERMCOM P701 STATUS(SUCCESS) CPCSNAME(USIBMSC.SCZP701)TSTIME(020111090930)

2. The session termination between the INGHWCOMand the Processor Support Element of the CPCUSIBMSC.SCZP701 configured with the hardwarename "P701" was rejected. Condition code00B00033 indicates that no session existed toterminate:

AOFA0004 TERMCOM P701 STATUS(REJECTED) CONDITION(00B00033) SENSE() CPCSNAME(USIBMSC.SCZP701) TSTIME(020111091447)

Note: For Processor Operations connections,TERMCOM is executed as part of host-based commandISQXCLS (Close target connection).

AOFA0005

ExplanationThis report is the response to a TERMCOM request fora CPC that is defined over an HMC connection. In thiscase, TERMCOM terminates the session betweenINGHWCOM and the HMC.

ExampleThe session between INGHWCOM and the HMC whereSERVER1 is defined, is terminated successfully.Implicitly, the sessions the other CPCs of that HMC arealso terminated.

AOFA0005 TERMCOM SERVER1 STATUS(SUCCESS) TSTIME(030117085107) AOFA0005 TERMCOM CPCSNAME(DEIBMIPS.IP3T1000) AOFA0005 TERMCOM CPCSNAME(AUIBMQXP.QXPTHES1) AOFA0005 TERMCOM CPCSNAME(AUIBMQXP.QXPTHES9) AOFA0005 TERMCOM CPCSNAME(DEIBMD1.X7E1FA0A) AOFA0005 TERMCOM CPCSNAME(DEIBMD1.X7F1E30A) AOFA0005 TERMCOM CPCSNAME(DEIBMD1.X7F1F20A) AOFA0005 TERMCOM REPORT COMPLETE


Appendix B. Response Messages, Error Strings, Condition Codes 539

Note: For Processor Operations connections,TERMCOM is executed as part of host-based commandISQXCLS (Close target connection).

AOFA0006

ExplanationThis report is the response to a CCNTL LIST request fora CPC that displays the selected RESET activationprofile used at the next CPC activation, the processorruntime type PRTT (0=system controlled,1=usercontrolled), the current processor runtime value PRT inmilliseconds, and if the timeslice ends when theprocessor goes into a disabled wait. You can use theCCNTL common command to change these values atruntime.

Examples

AOFA0006 CCNTL GRY2 STATUS(ACCEPTED) CPCSNAME(IBM390PS.GRY2) TSTIME(150921153531) AOFA0006 APNAME(DEFAULT) AOFA0006 PRTT(0) AOFA0006 PRT(1) AOFA0006 ENDTSL(NO) AOFA0006 CCNTL REPORT COMPLETE

AOFA0007

ExplanationThis multiline report is the response to a ICNTLrequest. It returns either a list of all available imagevariables with their current settings, or the response toa query or set request for a single image variable. Notethat the set of image variables available may bedifferent, depending on the processor type, the imageis running on.

Examples1. An ICNTL LIST request returns a report with the

available image variables and their current settingsfor image KEY4 of CPC FREEWAY. Because theICNTL command is entered without a specificprocessor type, the default is set to GPP (GeneralPurpose Processor).

AOFA0007 ICNTL FREEWAY.KEY4 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) PT(GPP) TSTIME(040911090931) AOFA0007 DEFCAP(0) AOFA0007 PWI(30) AOFA0007 PWIC(NO) AOFA0007 PWMN(10) AOFA0007 PWMX(100) AOFA0007 PWC(30) AOFA0007 PWCC(NO)

AOFA0007 WLME(NO) AOFA0007 ICNTL REPORT COMPLETE

2. Another LIST request output is shown. Note thatLIST is the default request if no other ICNTLparameter is specified. The report shows theavailable image variables for image KEY1 of CPCSAFOS. This processor is of an older type than CPCFREEWAY from example 1. Only the initialprocessor weight (PWI) and the initial processorweight capping (PWIC) can be manipulated on thishardware type.

AOFA0007 ICNTL SAFOS.KEY1 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TKY10) PT(GPP) TSTIME(040911091922) AOFA0007 PWI(30) AOFA0007 PWIC(NO) AOFA0007 ICNTL REPORT COMPLETE

3. In this example, z/OS Workload Manager (WLM)Control is enabled for the CP resources assigned toimage KEY4 of CPC FREEWAY.

AOFA0007 ICNTL FREEWAY.KEY4 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) PT(GPP) TSTIME(040911090931) AOFA0007 WLME(YES) AOFA0007 ICNTL REPORT COMPLETE

AOFA0016

ExplanationThis report is the response to a CPCDATA request. Itreturns a report consisting of multiple AOFA0016messages. The CPCDATA request combines theGETSINFO request for a CPC with the list of GETIINFOrequest, one for each image of the CPC.

Examples1. The AOFA0016 report message consists of two

record line types. The first type is the CPC reportstarting with CPCDATA followed by the CPC's name.Depending on the amount of CPC information,multiple lines of this type are provided in thereport. The last line completes the report. Inbetween, 1-n IMAGE report lines may be displayed,depending on the number of images that aredefined for the CPC.

CPC Report:

AOFA0016 CPCDATA S35 STATUS(OPERATING) PDATA(TYPE(2964),MODEL(M49),S/N(000020089F25)) MODE(LPAR) APROF(DEFAULT) CPCSNAME(IBM390PS.S35) NAME(S35)



CPS(GPP(22),SAP(9),AAP(2),IFL(22),ICF(0),IIP(1),CBP(4))AOFA0016 CPCDATA R35 TCAP(YES) TCAP_RECS(2) MSU(PERM(1084),PERM+BILL(2224) PERM+ALL_TEMP(2224)) SW_MDL(PERM(615),PERM+BILL(722),PERM+ALL(722)) PROCSTAT(DEFECTIVE(0),SPARE(2) PENDING(0))AOFA0016 CPCDATA S35 TSTIME(110316135817)

CPC image (LPAR) reports:

AOFA0016 CPCDATA CPCINAME(LP01) STATUS(OPERATING) INUMBER(01) IDATA(OSTYPE(LINUX),OSLEVEL(Linux_2.6.32)) MODE(LINUXONLY)AOFA0016 CPCDATA CPCINAME(LP11) STATUS(EXCEPTIONS) INUMBER(0B) IDATA(OSNAME(z/VSE),OSTYPE(VSE),OSLEVEL(z/VSE_V9R1)) MODE(ESA390)AOFA0016 CPCDATA CPCINAME(LP12) STATUS(OPERATING) INUMBER(0C) IDATA(OSNAME(IRD7),OSTYPE(MVS),OSLEVEL(z/OS_V2R02), SYSPLEX(IRD7PLEX)) MODE(ESA390) AOFA0016 CPCDATA CPCINAME(LP57) STATUS(OPERATING) INUMBER(3C) IDATA(OSNAME(TRX2),OSTYPE(MVS),OSLEVEL(z/OS_V2R01) MODE(ESA390)AOFA0016 CPCDATA CPCINAME(LP60) STATUS(NOT_ACTIVATED) INUMBER() IDATA() MODE()AOFA0016 CPCDATA CPCINAME(S35LP78) STATUS(OPERATING) INUMBER(53) IDATA(OSNAME(ZVSE VNA),OSTYPE(ZAPP), OSTYPE(ZAPP),OSLEVEL(0000000000010000)) MODE(SSC)AOFA0016 CPCDATA CPCINAME(KVMPP) STATUS(OPERATING) INUMBER(19) IDATA(OSTYPE(KVMIBM), OSLEVEL(KVMIBM_1.1.0)) MODE(LINUXONLY)AOFA0016 CPCDATA CPCINAME(TRX5CF5) STATUS(OPERATING) INUMBER(55) IDATA(OSNAME(CF01), OSTYPE(CFCC),OSLEVEL(2100006801000000), SYSPLEX(TRX1PLEX)) MODE(CF)

Report completion:

AOFA0016 CPCDATA REPORT COMPLETE

The STATUS field of line one, the CPC status, canhave the following values:

OPERATINGNOT_OPERATINGNO_POWERSTATUS_CHECKEXCEPTIONS

POWERSAVESERVICELINKNOTACTIVESERVICE_REQUNKNOWN

The PDATA field of line one contains the type,model, and serial number of the CPC.

The APROF field of line one contains the lastactivation profile name used to activate the CPC.

The MODE field of line one, the CPC mode, can havethe following values:

ESA390LPARESA390TPFLINUXONLY

The MODE field can have one of the followingvalues for a CPC image:

ESA390S370ESA390TPFCFLINUXONLYZVMSSC

For each identified CPC image, an AOFA0016 reportline is generated.

The CPCINAME field of an image report linecontains the image name of an identified image.

The INUMBER field contains the two hex digitpartition number. For processor hardwaresupporting a single channel subsystem, the firstdigit is always zero. The second digit contains apartition number from 1-F. For processor hardwaresupporting multiple channel subsystems, the firsthex digit contains the channel subsystem number,starting with zero and the second digit contains thepartition number 1-F.

The IDATA field contains a collection of theavailable information supplied by the image BCP.This information can be: OSNAME, OSTYPE, orOSLEVEL; for BCPs of type MVS it can be SYSPLEX.Note that one or more IDATA fields may not beavailable in the AOFA0016, AOFA0017 responsereports. This is because not all BCPs may supplythe complete field set. If the OSLEVEL field is notshown in the response report, the BCP did notprovide this information to the hardware.

The STATUS field of an image report line containsthe same status values as supplied with theGETISTAT report message AOFA0017.

2. On processor H05 (which is a z10 hardware orlater), more AOFA0016 reports are provided



because more CPC information is available on thishardware. The CPC report is split in two.

AOFA0016 CPCDATA H05 STATUS(OPERATING)PDATA(TYPE(2097),MODEL(E26),S/N(00002001EBAE)) MODE(LPAR) APROF(DEFAULT) CPCSNAME(IBM390PS.H05) NAME(H05)CPS(GPP(3),SAP(6),AAP(1),IFL(18),ICF(1),IIP(1),CBP(4))

AOFA0016 CPCDATA H05 TCAP(YES) TCAP_RECS(2) MSU(PERM(312),PERM+BILL(312),PERM+ALL_TEMP(312)) SW_MDL(PERM(703),PERM+BILL(703),PERM+ALL(703))PROCSTAT((DEFECTIVE(0),SPARE(2),PENDING(0))TSTIME(080619175410)

AOFA0016 CPCDATA CPCINAME(…). . . .AOFA0016 CPCDATA REPORT COMPLETE

The additional information in detail is:CPS

Shows the different types and numbers ofprocessors:GPP

The number of General Purpose Processors.SAP

The number of Service Assist Processors.AAP

The number of Application Assistprocessors.

IFLThe number of Integrated Facility for Linux®

processors.ICF

The number of Internal Coupling Facilityprocessors.

IIPThe number of Integrated InformationProcessors.

CBPThe number of Container Based Processors.

TCAPIndicates whether a temporary capacity changeis allowed (YES) or not (NO).

TCAP_RECSThe number of temporary capacity recordsfound for that CPC.

MSUShows the various temporary capacity MSUvalues that are associated with softwaremodels based on:

PERMPermanent processors.

PERM+BILLPermanent plus billable processors.

PERM+ALL_TEMPPermanent plus all temporary processors.

SW_MDLShows the various Software Models related totemporary capacity, based on:PERM

Permanent processors.PERM+BILL

Permanent plus billable processorsPERM+ALL_TEMP

Permanent plus all temporary processors.PROCSTAT

Shows processor status information:DEFECTIVEPROC

The number of defective processors.SPAREPROC

The number of spare processors.PENDINGPROC

The number of pending processors.

AOFA0017

ExplanationThis report is the response to the following requests: GETSSTAT, GETSINFO, GETSDGR, GETILDI, GETISTAT,GETIINFO, GETITKN, OOCOD STATUS, and CBUSTATUS request.GETISTAT

Queries the status of an image object.GETIINFO

Queries the status of an image object and lists theavailable image information(OSname,OStype,OSlevel, SysplexName).

GETILDIQueries the last used load address and the lastused load parameter for the image.

GETITKNQueries the current IPL token set at the last z/OSIPL for the image. Note, that a System Reset or aDisabled Wait changes this token. The IPL token isa 8 byte hexadecimal value.

GETSSTATQueries the status of a CPC object.

GETSDGRQueries the degraded reason indicator of a CPCsupporting the DEGRADED status.



GETSINFOQueries the status of a CPC object and lists theavailable CPC information (machine type andmodel, CPC serial number, last used activationprofile name).

CBU STATUSThe status function of the CBU command returnsthe determined status of the optional capacitybackup processor HW feature.

OOCOD STATUSThe status function of the OOCOD commandreturns the determined status of the On/OffCapacity on Demand HW feature.

On successful completion, the status field of messageAOFA0017 may have one of the following values:

GETIINFO GETSINFO GETILDIGETISTAT CBU STATUS OOCOD STATUS GETSDGR GETSSTAT GETITKN-------- ---------- ------------ ------- --------- ------------OPERATING NOT_INSTALLED ENABLED NOT_DEGRADED OPERATING n/aNOT_OPERATING NOT_ACTIVATED NOT_ENABLED MEM_REDUCED NOT_OPERATINGNOT_ACTIVATED NOT_ENABLED INSTALLED MEM_BUS_FAILURE NO_POWERSTATUS_CHECK UNAVAILABLE NOT_INSTALLED NODE_NOT_RUNNING EXCEPTIONSEXCEPTIONS AVAILABLE ACTIVATED RING_OPEN STATUS_CHECKPOWERSAVE ACTIVATED NOT_ACTIVATED CBU_EXPIRATION POWERSAVE REMOVABLE MRU_FAILURE LINKNOTACTIVE TEMPERATURE_PROBLEM SERVICE IML_WAS_IN_DEGRADED_MODE SERVICE_REQUIRED DEGRADED

ExamplesGETISTAT

System SC50, which runs on LPAR A3 of CPCUSIBMSC.SCZP801, has a status of OPERATING.

AOFA0017 GETISTAT SC50 STATUS(OPERATING) CPCINAME(A3) CPCSNAME(USIBMSC.SCZP801)

BUSY(NO) TSTIME(020111095940)

On processor YORAMA, the logical partition KEY7 hasa status of EXCEPTIONS:

AOFA0017 GETISTAT YORAMA.KEY7 STATUS(EXCEPTIONS) CPCINAME(KEY7) CPCSNAME(DEIBMD1.X7E1FA0A) BUSY(NO) TSTIME(020204130403)

CBU STATUS

On processor FREEWAY, a Capacity Backup Upgrade isinstalled and enabled (AVAILABLE). It was ACTIVATEDon January 18th 2012 and the activation periodexpires on January 27th 2012. There are four testactivations left for processing.

AOFA0017 CBU FREEWAY STATUS(AVAILABLE,ACTIVATED) ACTIVATION(18/01/12) A-EXPIRATION(27/01/12) TESTSLEFT(4) CPCSNAME(DEIBMD1.X7E1FA0A) TSTIME(120204130403)

On processor H05 (which is a z10 hardware or later),Capacity Backup Upgrade is installed and enabled(AVAILABLE). It was ACTIVATED on March 20th 2008and the CBU record expires on December 31st 2009.There are three test activations left for processing.

AOFA0017 CBU H05 STATUS(AVAILABLE,ACTIVATED) ACTIVATION(20/03/08) R-EXPIRATION(31/12/09) TESTSLEFT(3) CPCSNAME(DEIBMD1.H05) TSTIME (080320110503)

GETIINFO

The system defined as KEY6 to SA z/OS, which runs onlogical partition KEY6 (cpciname), whose partitionnumber cannot be determined (inumber field isempty), is an MVS OS type with an OS defined nameKEY6. It runs as a member of the sysplex KEY6PLEX.The LPAR runs in ESA mode and is running on CPCDEIBMD1.X7E1FA0A.

AOFA0017 GETIINFO KEY6 STATUS(OPERATING) CPCINAME(KEY6) INUMBER(0A) IDATA(OSNAME(KEY6),OSTYPE(MVS), SYSPLEX(KEY6PLEX)) MODE(ESA) CPCSNAME(DEIBMD1.X7E1FA0A) BUSY(NO) TSTIME(020923110403)

OOCOD STATUS



Processor T60 is enabled for On/Off Capacity onDemand and the feature is installed and active. It wasACTIVATED on April 3rd 2007.

AOFA0017 OOCOD T60 STATUS(ENABLED,INSTALLED,ACTIVATED) ACTIVATION(20070403090556) CPCSNAME(IBM390PS.T60) TSTIME(070410152248)

GETSINFO

CPC T29 is a z10, machine type 2097, model S18. It isrunning in LPAR mode and has activation profileDEFAULT set to be used for CPC activation. The CPC'sSupport Element SNA style address isZZZZZZZZZ.T29. The configured CPC name is T29. TheCPC object T29 is in a BUSY state. This means that atask is currently active that may prevent other CPCtasks from being accepted for execution.

Applications should repeatedly check the BUSY stateusing GETSSTAT or GETSINFO until a BUSY(NO) isreturned in the AOFA0017 report, before issuing anoperations management command against the object.

AOFA0017 GETSINFO T29 STATUS(OPERATING) PDATA(TYPE(2097),MODEL(S18),S/N(0000200D6AAD)) MODE(LPAR) APROF(DEFAULT) CPCSNAME(ZZZZZZZZZ.T29) NAME(T29) BUSY(YES) TSTIME(160908171141)

CPC R35 is a z196, machine type 2817, model M49. Itis running in LPAR mode and has set activation profileDEFAULT to be used for CPC activation. The SE SNAstyle address for the CPC is IBM390PS.R35. Theconfigured CPC name is R35. The CPC is not in BUSYstate. Installed processors:

• General Purpose Proc (GPP) - 15• Service Assist Proc (SAP) - 9• Application Assist Proc (AAP) - 1• Integrated Facility for Linux Proc (IFL) - 22• Integrated Coupling Facility Proc (ICF) - 0• Integrated Information Proc (IIP) - 1• Container Based Proc (CBP) - 4

On R35, temporary capacity changes are allowed -TCAP(YES). There is one temporary capacity recordinstalled for full or partial activation. With this recordyou can temporarily upgrade R35 from a model 615 toa 715 model machine increasing the available MSUsfrom 1084 to 1648.

Currently 10 of the 15 GP processors are not assignedto any work.

AOFA0017 GETSINFO R35 STATUS(OPERATING) PDATA(TYPE(2817),

MODEL(M49),S/N(000020089F25)) MODE(LPAR) APROF(DEFAULT) CPCSNAME(IBM390PS.R35) NAME(R35) BUSY(NO) CPS(GPP(15),SAP(9),AAP(1),IFL(22),ICF(0),IIP(1),CBP(4)) AOFA0017 GETSINFO R35 TCAP(YES) TCAP_RECS(1) MSU(PERM(1084),PERM+BILL(1648),PERM+ALL_TEMP(1648)) SW_MDL(PERM(615),PERM+BILL(715),PERM+ALL(715)) PROCSTAT(DEFECTIVE(0),SPARE(10),PENDING(0)) AOFA0017 GETSINFO R35 TSTIME(101019100945)

GETILDI

The last used load address on image TRX1 was 5023and the last used load parameter was 410001.1

AOFA0017 GETILDI #S35.TRX1 CPCINAME(TRX1) CPCSNAME(IBM390PS.S35) LAST_LOADADDR(5023) LAST_LOADPARM(410001.1) TSTIME(151007161353)

GETITKN

The IPL token set for image TRX1 wasCFA8E1AF0DAE5E55

AOFA0017 GETITKN #S35.TRX1 CPCINAME(TRX1) CPCSNAME(IBM390PS.S35) IPL_TOKEN(CFA8E1AF0DAE5E55) TSTIME(151007161137)

AOFA0018

ExplanationThis report is returned in response to a GETCLUSTERcommand.

Examples1. From the system that you are running on ('*'), the

CPC addresses list in PDATA are in your scope ofcontrol. With a BCP Internal Interface connections,this list is determined internally from the local SEby contacting the HMC in your processor LAN thathas the "Change Management" function enabled.The content of the Defined CPCs group of this HMCrepresents the CPCs that you can contact throughthis BCP Internal Interface session. Each scope listis terminated with a "report complete" message.The PDATA field of the AOFA0018 messagecontains CPC-related information. The first PDATAentry is always the fully qualified address of theCPC (cpcsname). Other PDATA information may beadded in the future, separated by a comma.

AOFA0018 GETCLUSTER SC50 STATUS(SUCCESS) CPCSNAME(USIBMSC.SCZP801)TSTIME(020112054842)



AOFA0018 GETCLUSTER PDATA(USIBMSC.SCZP801) AOFA0018 GETCLUSTER PDATA(USIBMSC.SCZP701) AOFA0018 GETCLUSTER PDATA(USIBMSC.SCZP702) AOFA0018 GETCLUSTER PDATA(USIBMSC.SCZP601) AOFA0018 GETCLUSTER REPORT COMPLETE

2. This GETCLUSTER request failed with a conditioncode of 0B100224 representing a BCP InternalInterface transport timeout condition:

AOFA0018 GETCLUSTER SC50 STATUS(FAILED) CONDITION(0B100224) SENSE(00000000 0000 00000000) CPCSNAME(USIBMSC.SCZP801)TSTIME(020111085916)

AOFA0019

ExplanationThis report is returned in response to a FILTER LISTcommand.

Examples1. The filter list report shows the filters that are in

place for SERVER1 CPC. The defined events in thelist (EN) are only forwarded to the specifiedNetView operators or operator group, if at least onefilter is set. If a prefix field PFX was specified with afilter SET command, its text is placed in front ofevery event message (ISQ900I).

AOFA0019 FILTER SERVER1 STATUS(SUCCESS) CPCSNAME(DEIBMD1.X7F1F20A) TSTIME(030128090248) AOFA0019 FILTER CPC PDATA(EN(ST,HW) OP(TIL) PFX(ISQ900I)) AOFA0019 FILTER CPC PDATA(EN(CC,ST,HW,ALRT) OP(+A00001S) PFX(ISQ900I)) AOFA0019 FILTER CPC PDATA(EN(CC,ST,HW) OP(+O00001S) PFX(ISQ900I)) AOFA0019 FILTER REPORT COMPLETE

If a prefix field PFX was specified with a filter SETcommand, its text is placed in front of every eventmessage. If no prefix is given with a FILTER SETcommand, the default prefix AOFA0900 is used.

2. The filter list report shows the filters that are inplace for image KEY2 on CPC SERVER1.

The first filter set sends all event reports to group+GEOOPER in a event message prefixed withGEO001I. The second filter sends the eventmessages with the default prefix AOFA0900,

because in the preceeding filter set command PFXwas not specified.

AOFA0019 FILTER SERVER1.KEY2 STATUS(SUCCESS) CPCSNAME(DEIBMD1.X7F1F20A) TSTIME(030119070203) AOFA0019 FILTER INAME(KEY2) PDATA(EN(CC,ST,HW,BCP,ALRT) OP(+GEOOPER) PFX(GEO001I)) AOFA0019 FILTER INAME(KEY2) PDATA(EN(CC,ST,HW,BCP) OP(TIL) PFX(AOFA0900)) AOFA0019 FILTER REPORT COMPLETE

AOFA0020

Examples1. In this example the APROF OPEN request returns

report AOFA0020 with the number of profilesstored for each activation profile type, in thesecond line. If no profile is stored for a activationprofile type, the value 0 is returned for that type.

AOFA0020 APROF FREEWAY STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040920100843) AOFA0020 PROFILES(RESET(1),IMAGE(16),LOAD(1)) AOFA0020 APROF REPORT COMPLETE

2. In this example the APROF CLOSE request returneda successful CLOSE of the activation profiles. Notethat activation profiles must have been openedusing the APROF OPEN request, prior issuing otherprofile requests.

AOFA0020 APROF FREEWAY STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040920101023) AOFA0020 APROF REPORT COMPLETE

3. This example shows the response to an ActivationProfile List command for image profiles of CPCFR07. For each profile name listed, a newAOFA0020 report line is generated.

AOFA0020 APROF FR07 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) TSTIME(040920101055) AOFA0020 NAME(DEFAULT) AOFA0020 IMAGE(VMA) AOFA0020 IMAGE(CF1) AOFA0020 IMAGE(SYSA) AOFA0020 IMAGE(SYSB) AOFA0020 IMAGE(SYSC) AOFA0020 IMAGE(SYSD) AOFA0020 IMAGE(SYSE) AOFA0020 IMAGE(SYSF) AOFA0020 IMAGE(KEY3) AOFA0020 IMAGE(KEY4) AOFA0020 IMAGE(CIM7) AOFA0020 IMAGE(CIM8)



AOFA0020 IMAGE(CFD) AOFA0020 IMAGE(CFE) AOFA0020 IMAGE(CFF) AOFA0020 APROF REPORT COMPLETE

4. In this example the contents of image profile KEY3is read. For each profile keyword variable onereport line is generated. Keyword variable OSSLP(operating system specific load parameter) is aspecial case. The data length of this variable,together with the other associated report data,exceeds the maximum length supported for thisinterface. For this reason, the output for OSSLP issplit into 8 segments. The segment number isattached to the keyword, separated by a periodfrom the keyword name. Because the APROFcommand is entered without a specific processortype, the default is set to GPP (General PurposeProcessor).

AOFA0020 APROF FR07 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) PT(GPP) TSTIME(041002111100) AOFA0020 IMAGE(KEY3) BPS() AOFA0020 IMAGE(KEY3) BRLBA(0000000000000000) AOFA0020 IMAGE(KEY3) DEFCAP(0) AOFA0020 IMAGE(KEY3) IPLADR(NEXT) AOFA0020 IMAGE(KEY3) IPLPRM(NEXT) AOFA0020 IMAGE(KEY3) IPLTYP(NORMAL) AOFA0020 IMAGE(KEY3) LUN(0000000000000000) AOFA0020 IMAGE(KEY3) OSSLP.1( ) AOFA0020 IMAGE(KEY3) OSSLP.2( ) AOFA0020 IMAGE(KEY3) OSSLP.3( ) AOFA0020 IMAGE(KEY3) OSSLP.4( ) AOFA0020 IMAGE(KEY3) OSSLP.5( ) AOFA0020 IMAGE(KEY3) OSSLP.6( ) AOFA0020 IMAGE(KEY3) OSSLP.7( ) AOFA0020 IMAGE(KEY3) OSSLP.8( ) AOFA0020 IMAGE(KEY3) PWI(30) AOFA0020 IMAGE(KEY3) PWIC(NO) AOFA0020 IMAGE(KEY3) PWMN(10) AOFA0020 IMAGE(KEY3) PWMX(100) AOFA0020 IMAGE(KEY3) WLME(NO) AOFA0020 IMAGE(KEY3) WWPN(0000000000000000) AOFA0020 APROF REPORT COMPLETE

5. In this example a single variable, the IPLTYP of loadprofile DEFAULTLOAD is retrieved. In the responsereport, the variable name, with its current value inparenthesis is returned.

AOFA0020 APROF FR07 STATUS(ACCEPTED) CPCSNAME(DEIBMIP1.IP3TVMA0) PT(GPP) TSTIME(041002141030) AOFA0020 LOAD(DEFAULTLOAD)

IPLTYP(NORMAL) AOFA0020 APROF REPORT COMPLETE

AOFA0021

ExplanationThis report is returned in response to a CTRLCONSrequest. CTRLCONS is used to shut down or restart ahardware console (either HMC or SE).

Examples1. This example shows the successful execution of a

Restart for the hardware console that the targetsystem is connected to.

AOFA0021 CTRLCONS(KEYHMC2) SUBMITTED TSTIME(070321171541)AOFA0021 CTRLCONS T60 STATUS(SUCCESS) CPCSNAME(IBM390PS.T60) TSTIME(070321171541)AOFA0021 CTRLCONS REPORT COMPLETE

2. This example shows that the CTRLCONS commandrejected because the session mode for the targethardware is ASYNY, but must be SYNC (use theSTATCOM command to verify).

AOFA0021 CTRLCONS(KEYHMC2) SUBMITTED TSTIME(070321171541)AOFA0021 CTRLCONS T60 STATUS(FAILED) CONDITION(00B00082) SENSE() CPCSNAME(IBM390PS.T60) TSTIME(070321154745)AOFA0021 CTRLCONS REPORT COMPLETE

AOFA0022

ExplanationThis report is returned in response to a CONDATAquery request.

ExampleQuery the Support Element console of a z10:

AOFA0022 CONDATA H05 TSTIME(080708103727)AOFA0022 CONDATA NAME(H05) VER(2.10.0) TYPE(SE)AOFA0022 CONDATA IPADDR(9.152.90.35 fe80:0:0:0:21a:6bff:fe38:738 0.0.0.0 fe80:0:0:0:21a:6bff:fe38:738)AOFA0022 CONDATA ECLEVEL(F85906.108)AOFA0022 CONDATA AUTOSWITCH(YES)AOFA0022 CONDATA REPORT COMPLETE

The console application version detected is 2.10.0(2097 GA1) and it runs on a Support Element. Theconfigured set of IPv4 and IPv6 addresses is alsoreturned in the console data query. In addition the



Engineering change ID (F85906) of the consoleapplication and its active Micro Code Level (MCL) 108is shown. Finally, this Support Element is configured toswitch automatically to its alternate, in case of failure.

AOFA0022 CONDATA RAP2 TSTIME(101019095046)AOFA0022 CONDATA NAME(KEYHMC2) VER(2.11.0) TYPE(HMC)AOFA0022 CONDATA IPADDR(9.152.93.21 fe80:0:0:0:......)AOFA0022 CONDATA ECLEVEL(N29809.72)AOFA0022 CONDATA VMS(8)AOFA0022 CONDATA REPORT COMPLETE

The console application version detected is 2.11.0(2817 GA1) and it runs on a HMC. The configured setof IPv4 and IPv6 addresses is also returned with thisquery. The Engineering Change ID (N29809) of theconsole application and its active Micro Code Level(MCL) 72 is shown. Finally, this HMC has 8 virtualmachine servers (VMS) defined that can be managedfrom this console. Note that CONDATA responses of aTYPE(SE) connection cannot show virtual machineservers. VMS endpoint is always a HMC.

AOFA0023

ExplanationThese reports are returned in response to a TCDATAquery request.

Examples1. Query the list of the installed capacity records:

AOFA0023 TCDATA ECL2 TSTIME(090610101910)AOFA0023 TCDATA RECORDID(M0002460)AOFA0023 TCDATA RECORDID(CR7LYKLY)AOFA0023 TCDATA REPORT COMPLETE

2. Query the details of OOCOD record with ID05961411:

AOFA0023 TCDATA OBJECT(TEMPORARY CAPACITY RECORD) OBJECT ID(05961411) TSTIME(081015162834)AOFA0023 TCDATA RECORDTYPE(OOCOD)AOFA0023 TCDATA STATUS(Real)AOFA0023 TCDATA PROCESSORINFO(1) TYPE(CP)AOFA0023 TCDATA PROCESSORINFO(1) PROCSTEP(2)AOFA0023 TCDATA PROCESSORINFO(1) MAX(-1)AOFA0023 TCDATA PROCESSORINFO(1) REMAININGPROCDAYS(-1)AOFA0023 TCDATA PROCESSORINFO(1) REMAININGMSUDAYS(-1)AOFA0023 TCDATA PROCESSORINFO(2) TYPE(IFL)AOFA0023 TCDATA PROCESSORINFO(2) PROCSTEP(0)AOFA0023 TCDATA PROCESSORINFO(2) MAX(2)AOFA0023 TCDATA PROCESSORINFO(2) REMAININGPROCDAYS(-1)AOFA0023 TCDATA PROCESSORINFO(3)

TYPE(AAP)AOFA0023 TCDATA PROCESSORINFO(3) PROCSTEP(0)AOFA0023 TCDATA PROCESSORINFO(3) MAX(2)AOFA0023 TCDATA PROCESSORINFO(3) REMAININGPROCDAYS(-1)AOFA0023 TCDATA PROCESSORINFO(4) TYPE(IIP)AOFA0023 TCDATA PROCESSORINFO(4) PROCSTEP(0)AOFA0023 TCDATA PROCESSORINFO(4) MAX(2)AOFA0023 TCDATA PROCESSORINFO(4) REMAININGPROCDAYS(-1)AOFA0023 TCDATA MAXREALDAYS(0)AOFA0023 TCDATA MAXTESTDAYS(0)AOFA0023 TCDATA TARGET(1) PROCSTEP(0)AOFA0023 TCDATA TARGET(1) SPEEDSTEP(0)AOFA0023 TCDATA TARGET(1) SOFTWAREMODEL(705)AOFA0023 TCDATA TARGET(1) BILLABLEMSUCOST(176)AOFA0023 TCDATA TARGET(1) BILLABLEMSUDELTA(0)AOFA0023 TCDATA TARGET(2) PROCSTEP(-1)AOFA0023 TCDATA TARGET(2) SPEEDSTEP(0)AOFA0023 TCDATA TARGET(2) SOFTWAREMODEL(704)AOFA0023 TCDATA TARGET(2) BILLABLEMSUCOST(89)AOFA0023 TCDATA TARGET(2) BILLABLEMSUDELTA(-87)AOFA0023 TCDATA TARGET(3) PROCSTEP(-2)AOFA0023 TCDATA TARGET(3) SPEEDSTEP(0)AOFA0023 TCDATA TARGET(3) SOFTWAREMODEL(703)AOFA0023 TCDATA TARGET(3) BILLABLEMSUCOST(0)AOFA0023 TCDATA TARGET(3) BILLABLEMSUDELTA(-176)AOFA0023 TCDATA REPORT COMPLETE

To learn more about the TCDATA records shown, seeSystem z Application Programming Interface,SB10-7030, Appendix F and IBM System z10 Capacityon Demand.

AOFA0024

ExplanationThis report is returned in response to a STPDATA queryrequest.

ExampleAOFA0024 STPDATA CTNID STPID(lnxhmc2)AOFA0024 STPDATA PREFERRED NODENAME(T63)AOFA0024 STPDATA PREFERRED NODEID TYPE(002094)AOFA0024 STPDATA PREFERRED NODEID MODEL(S38)AOFA0024 STPDATA PREFERRED NODEID MANUF(IBM)AOFA0024 STPDATA PREFERRED NODEID POMANUF(02)AOFA0024 STPDATA PREFERRED NODEID SEQNUM(00000002D09E)AOFA0024 STPDATA BACKUP NODENAME(H05)AOFA0024 STPDATA BACKUP NODEID TYPE(002097)AOFA0024 STPDATA BACKUP NODEID MODEL(E26)AOFA0024 STPDATA BACKUP NODEID MANUF(IBM)AOFA0024 STPDATA BACKUP NODEID POMANUF(02)AOFA0024 STPDATA BACKUP NODEID



SEQNUM(00000001EBAE)AOFA0024 STPDATA CURRENTTIMESERVER(Preferred)AOFA0024 STPDATA REPORT COMPLETE

This report shows information about a coordinatedtimer network with the name lnxhmc2. It hasconfigured a preferred (T63) and a backup (H05) node.Both nodes are System z mainframes. For each ofthem the machine type and model information,manufacturing information, and the CPC serialnumbers are provided. Finally it is indicated that thecurrent time server role is assigned to the preferredtime server, T63.

For more information about STP see the IBMRedbooks®, Server Time Protocol Planning Guide(SG24-7280) and Server Time Protocol ImplementationGuide (SG24-7281).

AOFA0025

ExplanationThis report is returned as a response to a GETIPSWquery request.

Example:

AOFA0025 GETIPSW R35.R35LP53 TSTIME(100722161059)AOFA0025 CP(0) PSW(07060001800000000000000000116816)AOFA0025 CP(1) PSW(00000000000000000000000000000000)AOFA0025 GETIPSW REPORT COMPLETE

This report shows the PSW information of the twocentral processors assigned to image R35LP53 of CPCR35.

AOFA0028

ExplanationThis report is returned in response to a HWMSGmessage management command.

Example:

AOFA0028 HWMSG G14 STATUS(SUCCESS) CPCSNAME(IBM390PS.G14) TSTIME(120721182328)

A message DELETE request was successfully executedfor a HW message issued on CPC G14 console (SE/HMC). The HW message with the specified timestampis deleted and is no longer available for the View HWmessages task on the console.

AOFA0030

Explanation:This report is returned in response to a GETRAW queryrequest.

ExampleISQCCMD S313 GETRAW 19.0 AOFA0030 GETRAW S313 MIB(1.3.6.1.4.1.2.6.42.1.0.19.0.4264836715) TYPE(4) BYTES(13) AOFA0030 GETRAW 30303030323030433533323700 AOFA0030 GETRAW REPORT COMPLETE

This report shows the MIB data of CPC attribute 19.0,which is the central processor complex serial number.The addressed target hardware processor name isS313.

The number of data bytes returned is 13.

MIB Type 4 means OCTETSTRING.

Character data from SE/HMC is stored as null-terminated string in hexadecimal ASCII code. Afterconversion from ASCII to EBCDIC characters, theserial number is: 0000200C5327.

AOFA0097

ExplanationThis report is returned in response to a RESUMErequest.

Examples1. In the following example the connection to CPC

ECL2 was successfully resumed. The returnedresume reason MANUAL indicates that this sessionor connection state was set manually using theRESUME command.

AOFA0097 RESUME ECL2 STATUS(SUCCESS) REASON(MANUAL) CPCSNAME(IBM390PS.ECL2) TSTIME(090530132623)

2. In this example you can see the response if you tryto resume a session or connection that is notsuspended:

AOFA0097 SUSPEND ECL2 STATUS(REJECTED) REASON(NOT_SUSPENDED) CPCSNAME(IBM390PS.ECL2) TSTIME(090530134423)

3. The following example illustrates the response ifthere was an error accessing the common globalvariables that are used to control the suspend orresume mode:

INGHWCMD H05 RESUME



AOFA0097 RESUME H05 STATUS(FAILED) CONDITION(00B000B1) CPCSNAME(IBM390PS.H05) TSTIME(090530142212)

AOFA0098

ExplanationThis report is returned in response to a SUSPENDrequest.

Examples1. In the following example the connection to CPC

ECL2 was successfully suspended. The returnedsuspend reason MANUAL indicates that this sessionor connection state was set manually using theSUSPEND command.

AOFA0098 SUSPEND ECL2 STATUS(SUCCESS) REASON(MANUAL) CPCSNAME(IBM390PS.ECL2) TSTIME(090530132623)

2. In this example you can see the response if you tryto suspend a session or connection that is alreadysuspended:

AOFA0098 SUSPEND ECL2 STATUS(REJECTED) REASON(ALREADY_SUSPENDED) CPCSNAME(IBM390PS.ECL2) TSTIME(090530134423)

3. The following example illustrates the response ifthere was an error accessing the common globalvariables that are used to control the suspendmode:

AOFA0098 SUSPEND H05 STATUS(FAILED) CONDITION(00B000B0) CPCSNAME(IBM390PS.H05) TSTIME(090530142212)

AOFA0026

ExplanationThis report is returned as response to a POWERMOD'STATUS' request.

ExamplesINGHWCMD R35 POWERMOD STATUS AOFA0026 POWERMOD R35 CURRENT MODE(100) SUPPORTED MODES(100 83) SAVE MODE ALLOWED(YES) CPCSNAME(IBM390PS.R35)TSTIME(100817131434)

This report shows, for CPC R35, the current mode (100= High Performance), the supported modes (83 = Low

Power), and if Power Save Mode is allowed Yes/No. ACURRENT MODE value 'STATIC' indicates that the CPCdoes not support Power Mode changes.

AOFA0099

ExplanationThis report is returned as the response to a connectionstatus request command.

Examples1. The CPC SERVER1 is connected to this NetView

using task AUTHW007. The connection is madeeither through INTERNAL or SNMP transport. TheBCP Internal Interface uses the internal transportand always has the Support Element (SE) as target.For the SNMP transport, either SE or HMC can bethe target. A TRANSPORT value of A-INTERNALindicates an asynchronous session, whereas S-INTERNAL indicates a synchronous session. A valueof SNMP indicates that a standard SNMP session isestablished, which is always asynchronous.

AOFA0099 STATCOM SERVER1 STATUS(CONNECTED) TASK(AUTHW007) TRANSPORT(A-INTERNAL) TARGET(SE) CPCSNAME(IBM390PS.P1234567) TSTIME(030104091131)

2. The CPC SAFOS is currently not connected to theINGHWCMD hardware interface.

AOFA0099 STATCOM SAFOS STATUS(NOT_CONNECTED) CPCSNAME(DEIBMD1.X7F1F20A) TSTIME(030104091145)

3. The CPC YORAMA is currently connected to theINGHWCMD hardware interface with a synchronousSNMP session. Synchronous sessions (SNMP orINTERNAL) allow the polling of CPC and imagestatus and the retrieval of object information. HWevents, such as status changes or messages fromthe HW or BCPs, cannot be processed withsynchronous sessions.

AOFA0099 STATCOM SAFOS STATUS(CONNECTED) TASK(ISQCM001) TRANSPORT(S-SNMP) TARGET(SE) CPCSNAME(DEIBMIP1.IP3T1100) TSTIME(030104091145)



Asynchronous Response Messages (AOFA0100–AOFA0999)Events from CPCs or CPC images arrive as asynchronous messages in NetView.

The following event types are supported by the INGHWCMD interface:

• Messages from the Operating System (BCP messages)• Status Changes of CPC or CPC image objects• Hardware Messages from the CPC and its associated CPC images• SNA Alert data from the CPC and its associated CPC images

AOFA0100 NEWSTATUS(obj_status_number)OLDSTATUS(obj_status_number)

ExplanationThis message indicates a status change event of a CPCor CPC image object. Before you can receive this typeof message, you must have successfully initialized anasynchronous session. Secondly, you must havespecified a FILTER command with a NetView operatoror group name as the receiver for each image or CPCthat you target. See “Hardware Object StatusSummary” on page 573 for a list of the supportedobject status numbers and their meaning.

ExamplePartition KEY4 of FREEWAY was successfully CPstopped. The status changed from OPERATING (0001)to NOT_OPERATING (0002).

After the LPAR was CP started again, its status wentback to OPERATING. Note that Prefix messageAOFA0900 was used, because the FILTER commandwas specified without a PFX. No operating systemmessages are shown either, because the eventnotification that was enabled with the FILTER requestwas only ST, for object status change events.

INGHWCMD FREEWAY INITCOM ASYNC INGHWCMD FREEWAY.KEY4 FILTER SET(ST) OP(TIL) INGHWCMD FREEWAY.KEY4 STOP

AOFA0001 STOP FREEWAY.KEY4 STATUS(ACCEPTED) CPCINAME(KEY4) CPCSNAME(DEIBMD1.X7F1E30A) TSTIME(030208143117)

AOFA0900 FREEWAY.KEY4 SC AOFA0100 NEWSTATUS(0002) OLDSTATUS(0001)

INGHWCMD FREEWAY.KEY4 START

AOFA0001 START FREEWAY.KEY4 STATUS(ACCEPTED) CPCINAME(KEY4) CPCSNAME(DEIBMD1.X7F1E30A) TSTIME(030208143134)

AOFA0900 FREEWAY.KEY4 SC AOFA0100 NEWSTATUS(0001) OLDSTATUS(0002)

AOFA0200 CpcName.ImageName ConIDCommand_completion_response

ExplanationThis event report message returns the commandcompletion information of the asynchronouslyexecuted hardware commands. This type of commanddoes not return results before all related work in thehardware has completed. After that, a commandcompletion event is emitted which provides the finalcompletion information of the command.CpcName.ImageName

Specifies the name of the processor as defined inthe SA z/OS policy and the image or LPAR namethat this asynchronous command completionmessage originates from.

ConIDAlways SC for System Console.

Command_completion_responseFormat is CC(xxxxxxxx), where xxxxxxxx is acompletion code in hex or decimal notation.00000000

The asynchronous command, specified in thisreport, completed successfully.

00000026 - 00000070 (value range)Completion responses specific to CBU, OOCOD,TCM, and STP commands. For details, seesectionHWMCA_EVENT_COMMAND_RESPONSE returncodes of this response. It is documented in theappendix of hardware manual IBM Z SNMPApplication Programming Interfaces.

0806000A (134610954) - 80180002(2149056514) (value range)

General hardware command completionresponses. For details, see sectionHWMCA_EVENT_COMMAND_RESPONSE returncodes of this response. It is documented in theappendix of hardware manual IBM Z SNMPApplication Programming Interfaces.

System programmer response:If the completion code details suggest to retry therequest after the noted conditions are met, do so. Ifit's stated that a hardware error may cause this

Asynchronous Response Messages (AOFA0100–AOFA0999)


condition, perform the HMC task 'Report a Problem' toinform IBM about the problem.

AOFA0300 Power® Mode Change occurred,Old Status (Old-value) New Status(New-value) Object (CpcName)

ExplanationThis message indicates a change related to the CPC'sPower Mode settings. This message uses the followingvariables:Old-value

Value before Power Mode was changed.New-value

New Power Mode value.CpcName

Specifies the name of the processor as defined inthe SA z/OS policy.

AOFA0400 CpcName ConID HW_message

ExplanationThis response message uses the following variables:CpcName



HW_messageThe message text is identical to the short messagetext displayed on the SE or HMC that an HWmessage is waiting for, when a CPC object hasbeen marked. Note that the message detailinformation can only be accessed using the HMC orSE GUI.

AOFA0444 CpcName.ImageNameCons_designator DISABLED WAITCP (num) PSW(xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)

ExplanationCpcName.ImageName

Specifies the name of the processor as defined inthe SA policy and the partition name where theWAIT occurred.

Cons_designatorAlways SC for System Console.

numNumber of central processor that entered thedisabled wait state.

xxx...xxxThe current Program Status Word (PSW) of thecentral processor num, displayed as 32 hexcharacters. For information about the wait statecode shown in the PSW, refer to the appropriateOS documentation.

AOFA0500 CpcName ConID TemporaryCapacity Record record_id Changeoccurred (change_code)

ExplanationThis message indicates a change related to aTemporary Capacity record. It uses the followingvariables:CpcName



record_idAn 8 digit record number of the temporary capacityrecord.

change_codeA numeric code that indicates the type of change.Possible values are:0

Capacity Record 'Add' occurred1

Capacity Record: Delta2

Capacity Record 'Delete' occurred3

Capacity Record Accounting Data change4

Capacity Record Activation Level change5

Capacity Record: Priority Pending6

Capacity Record: Other changes

AOFA0600 CpcName Cons_designatorTemporary Capacity Changeoccurred(change_code)

ExplanationThis message indicates a change related to TemporaryCapacity management of the Target Hardware. It usesthe following variables:CpcName

Specifies the name of a processor as defined in theSA z/OS policy.



Cons_designatorIs always SC for System Console.

change_codeA numeric code that indicates the type of change.Possible values are:0

Capacity: Fenced Book1

Capacity: Defective Processor2

Capacity: Concurrent Book Replace3

Capacity: Concurrent Book Add4

Capacity: Capacity Check Stop5

Temporary Capacity Changes Allowed6

Temporary Capacity Changes Not Allowed

AOFA0700 APPL_ENDEDCONSOLE(con_name)REASON(reason) TYPE(type)COMPONENT(comp)

ExplanationThis message indicates the end of the consoleapplication operation. This is the software on theSupport Elements (SEs)/ Hardware ManagementConsoles (HMCs) that permits OperationsManagement tasks. SA z/OS requires this componentto be operational in order to communicate with the SE/HMC.con_name

Name of the affected console. For SE connections,this name is identical to the NAU name part of theCPC network address. For HMC connections thisname is identical to the Console Name definedwith the Customize Network Settings task from theHMC Console Settings Work Area.

reasonIssuer that caused the console application to end.USER

A logged on userAUTOMATION



The reason code in the event data is unknown.

typeSpecifies the action that caused the consoleapplication to end. Depending on the type given, apossible console application outage time can bepredicted.SHUTDOWN_CONSOLE

Long outage, manual intervention is required torecover.

RESTART_APPLICATIONMedium outage of 10 - 20 minutes can beexpected until the console application is fullyoperational again.

RESTART_CONSOLEMedium outage of 10 -20 minutes can beexpected until the console application is fullyoperational again.

UNKNOWNThe type code in the event data is unknown.Long outage, manual intervention may berequired to cover.

compNames the component that is involved in thisevent. In the case of reason code AUTOMATION,the involved component may be API. Note that thecomponent information given in this report doesnot exceed more than 20 characters.

AOFA0800 CONSOLE(con_name) SECLOGREPORT date_time_stampsecurity_log_message

ExplanationThis message report is issued each time a newmessage is written to the Security Log of the SupportElement (SE)/ Hardware Management Console (HMC)that is in session with SA z/OS. Depending on thelength of the security_log_message, this report mayhave more than three AOFA0800 report lines. With aprocessor operations SNMP connection, you can usethe ISQCCMD SECLOG common command to turn thisfunction on or off.con_name

Name of the affected console. For SE connections,this name is identical to the NAU name part of theCPC network address. For HMC connections thisname is identical to the Console Name definedwith the Customize Network Settings task from theHMC Console Settings Work Area.

date_time_stampIndicates the date and time, the record was writtenin the log. Date format is month-day-year and timeformat is hh:mm:ss:hss.



security_log_messageFor more information about what types ofmessages are written to the console security log,use the 'View Security Logs' task of your SE/HMCconsole.

AOFA0900 CpcName.ImageName ConIDEvent_message_string

ExplanationThis response message uses the following variables:CpcName.ImageName

Specifies the name of the processor as defined inthe SA z/OS policy and the image or LPAR namethat this event message originates from.

ConIDFor BCP message events the ID is OC, indicating amessage from the operator console. For all otherevent messages, the ID is SC, indicating a messagefrom the system console.

Event_message_stringSpecifies the message text from the operatingsystem as shown on the SE or HMC, or themessage string specific to the other events type.

AOFA0996 WAIT sec SECOND FORTERMINATION OF A COMMANDSESSION: OPID(opid)CPCSNAME(cpc) TSTIME(time)COMMAND(command).

ExplanationThe HW event handler for the CPC (cpc) sessionreturned an error and the asynchronous sessionterminates. To perform a save memory cleanup, an HWcommand that is still active for the CPC running in task(opid) must be terminated first. Wait for (sec) secondsfor normal command termination.

AOFA0997 EVENT HANDLER ERROR,CORRUPTED TCPIP PACKETRECEIVED REASON (reason),SESSION IS TERMINATING.

ExplanationThe HW handler for this SE or HMC session hasreceived a corrupted or uncompleted TCPIP packet.The asynchronous session terminates.

This report might be issued in case of disruption of theIP connection to the hardware management console(SE or HMC). Possible reason codes:

HWMCA_INCOMPLETE_TRAP 0HWMCA_BADTRAP_NO_SEQUENCE

10001HWMCA_BADTRAP_BAD_INITIAL_LENGTH 10002HWMCA_BADTRAP_BAD_VERSION_LENGTH 10003HWMCA_BADTRAP_BAD_COMMUNITY_LENGTH 10004HWMCA_BADTRAP_BAD_PDUTYPE 10005HWMCA_BADTRAP_BAD_PDU 10006HWMCA_BADTRAP_BAD_PDU_LENGTH 10007HWMCA_BADTRAP_BAD_ENTERPRISE_LENGTH 10008HWMCA_BADTRAP_BAD_ADDRESS_LENGTH 10009HWMCA_BADTRAP_BAD_GENERIC_LENGTH 10010HWMCA_BADTRAP_BAD_TIMESTAMP_LENGTH 10011HWMCA_BADTRAP_BAD_VARBIND_LENGTH 10012HWMCA_BADTRAP_BAD_VARBIND_SEQUENCE 10013HWMCA_BADTRAP_BAD_VARBIND_SEQ_LENGTH 10014HWMCA_BADTRAP_BAD_VARBIND_OID_LENGTH 10015HWMCA_BADTRAP_BAD_VARBIND_DATA_LENGTH 10016HWMCA_BADTRAP_BAD_SPECIFIC_LENGTH 10017

AOFA0998 EVENT HANDLER WARNING:ASYNCHRONOUS SESSION HASBEEN REESTABLISHED

ExplanationThe HW event handler for this SE/HMC recovered amissing heartbeat condition signaled by the BCPInternal Interface. Some events might have been lost.Applications should query status information of theCPC or image in order to determine the current status.Note that BCP messages that are transported as HWevents are not buffered and cannot be recovered ifthey are lost.

AOFA0999 EVENT HANDLER ERROR RC(rc) ,ASYNCHRONOUS SESSION ISTERMINATING.

ExplanationThe HW event handler for this SE or HMC sessionreturned an error return code (rc). The asynchronoussession terminates. An INITCOM ASNC must be issuedto reactivate the session. Refer to “Data ExchangeServices "0B100xxx"” on page 559 if the return codenumber is less than 100. Refer to “Internal TransportServices "0Bx00xxx"” on page 566 for return codesgreater than 100. Note that only if you set a CPC eventfilter will you receive this event handler terminationreport.



This report might be issued in case of an unplanned orplanned outage of the hardware management console(SE or HMC). For planned outages (maintenance), it isstrongly recommended to first close the ongoing activetarget hardware connections to that hardwaremanagement console using command TERMCOM, orfor Processor Operations users, command ISQXCLS.

Note: For Processor Operations connections, INITCOMis executed as part of host-based command ISQXIII(Initialize target connection).

Condition CodesThis section gives further information about the condition codes for errors that are associated with thefollowing:

• “Hardware Communication Task Condition Codes "00B00xxx"” on page 554• “Data Exchange Services "0B100xxx"” on page 559• “Command Services "0B200xxx"” on page 562• “Internal Transport Services "0Bx00xxx"” on page 566

Hardware Communication Task Condition Codes "00B00xxx"Table 11 on page 554 lists the condition codes for Hardware Communication Task "00B00xxx".

Table 11. Hardware Communication Task Condition Codes

Reason Code Error String Error Description

001 ING_invalid_HLL_buffer INGHWCOM was invoked, but the NetView HLL buffer found for C/C++is not valid.

002 ING_origuser_invalid The user ID and output correlator passed to INGHWCOM are not valid.

003 ING_interface_invalid The hardware interface name passed to INGHWCOM is not valid.Allowed interface names are INTERNAL, SNMP, or SNA.

004 ING_interface_missing No hardware interface name is passed to INGHWCOM.

005 ING_tgt_length-error Parsing Error: The target object name (processor or image name) hasan invalid length. It must be 1 to 8 characters.

006 ING_tgt_missing Parsing Error: The target object name (processor or image name) isnot specified.

007 ING_cpc_length_error Parsing Error: The CPC address specification netid.nau has an invalidlength. It must not exceed 17 characters.

008 ING_cpc_missing Parsing Error: The CPC address specification, which is a requiredparameter for the request, is missing.

009 ING_imgname_length_err. Parsing Error: The image name (LPAR name) parameter has an invalidlength.

00A ING_imgname_missing Parsing Error: The image name (LPAR name) is a required parameterfor the request, but has not been specified.

00B ING_force_invalid Parsing Error: The FORCE option is specified in the request but is notsupported for the HW function. The following HW functions allow theFORCE option:

ACTIVATE, DEACTIVATE, SYSRESET, LOAD

00C ING_force_missing Parsing Error: The FORCE option is required for the request, but hasnot been specified.

00D ING_auth_missing Parsing Error: The AUTHENTICATION specification that is required foreach request is missing.

00E ING_timeout_missing Parsing Error: The required TIMEOUT parameter is missing in therequest.

Condition Codes


Table 11. Hardware Communication Task Condition Codes (continued)


00F ING_OCFCMD_truncated Parsing Error: The HW function (OCFCMD) exceeds the maximumallowed length, which is 40 characters.

010 ING_OCFCMD_missing Parsing Error: No HW function (OCFCMD) was specified in the request.

011 ING_V3USER_missing Parsing Error: SNMPv3 User required for SNMPv3 authentication ismissing.

012 ING_V3PWD_missing Parsing Error: SNMPv3 Password required for SNMPv3 authenticationis missing.

020 ING_SNMP_noIP_address Parameter Resolution Error: The SNMP interface was specified for theHW request, but no IP address information is available.

021 ING_OCF_resolve_failed Parameter Resolution Error: No HW function name to resolve, same aserror 010.

022 ING_OCF_not_resolved Parameter Resolution Error: An invalid HW function name wasdetected.

023 ING_BCP_null_cmd Parameter Resolution Error: The BCP command retrieved fromNetView common global variable ING.xxxx.CMDTXT was empty.

024 ING_BCP_cmd_acc Parameter Resolution Error: The NetView common global variablecontaining the BCP command could not be retrieved.

025 ING_session_type_missing_or_invalid

Parameter Resolution Error: Session type values SYNC or ASYNCmissing, or an invalid session type value was passed.

026 ING_active_session_type_mismatch Parameter Resolution Error: A session was requested having adifferent session type SYNC/ASYNC than the active session. Reissuethe INITCOM request with the correct session type or terminate theactive session prior to requesting a new one.

030 ING_nt_alloc_error Storage Allocation Error: The Netid base table could not be allocatedusing CNMNAMS services.

031 ING_img_alloc_error Storage Allocation Error: The storage for a system image could not beallocated using CNMNAMS services.

032 ING_img_locate_error Storage Allocation Error: The previously allocated storage for a systemimage could not be located using CNMNAMS services.

033 ING_notinit_error Storage Allocation Error: An HW function request was issued for aprocessor or system image without having allocated storage for thatprocessor or system image. This happens if no INITCOM request wasmade prior to the first a HW function request.

050 ING_notinitized_error HW Function Error: An HW function request was issued for a processoror system image without having done an INITCOM. Same as error 033.

051 ING_imgnotfound_error HW Function Error: An HW function request was issued for a partitionthat could not be located on the addressed CPC. Possible causes are:

1. The image name may be misspelled.2. The name was taken from incorrect configuration data.3. The CPC's partition configuration was dynamically changed while

the session was active. Newly added or deleted partitions are notrecognized without an SA configuration update, followed by asession restart.

4. A HW command request was entered without a required imagename target parameter.

5. Partitions running on CPCs that support BCPii permission settings,are only recognized and shown to the hardware command issuer, ifthey have the permission checkboxes enabled. Otherwise, theseLPARs are considered to be hidden for the BCPii transport. If theconnection to the CPC runs over TCP/IP, BCPii permission settingsare ignored.

052 ING_funcunknown_error HW Function Error: An unknown HW function name was requested.Same as error 022.

Condition Codes




053 ING_nocpcobject_error HW Function Error: GETCLUSTER failed. Cluster list attribute notresolved by the processor support element.

054 ING_nocluster_error HW Function Error: GETCLUSTER failed. The cluster list returned bythe processor support element was empty.

055 ING_nohwstatus_error HW Function Error: An HW function that requires the determination ofthe status of the object prior to execution cannot be processedbecause the object status cannot be determined. This error is validonly for processors where the FORCE option has to be emulated byINGHWCOM.

056 ING_disruptive_cmd HW Function Error: A disruptive HW function was requested withoutthe FORCE option and the processor/image object is in an operationalstate. INGHWCOM uses FORCE(NO) (allow no disruptive commands)as default. If you want to allow disruptive commands you must specifythe FORCE option in the INGHWCMD request.

057 ING_noistatus_error HW Function Error: CBU or OOCOD failed. A CBU or OOCOD functionwas requested but the current CBU / OOCOD status cannot bedetermined.

058 ING_noiobject_error HW Function Error: Command failed. The processor hardware does notsupport the specified object attribute or the object attribute has ablank value.

059 ING_cbustatus_error HW Function Error: CBU failed. A CBU status was returned that doesnot allow the request.

060 ING_filter_error HW Function Error: A filter SET/UNSET command failed. Either a filtertable is full and no new filters can be set, or a specified image namedoes not exist on the CPC. A maximum of 10 filter entries can be setper image. This error is also shown when doing a SET for an event typeof BCP for a CPC object in LPAR mode. For CPC objects, this type ofevent is only supported when running in a BASIC processor mode.

061 ING_filter_not_async HW Function Error: A filter command was entered for aSYNCHRONOUS session of the BCP Internal Interface, where filtercommands are not supported. Synchronous sessions over the BCPInternal Interface are established if the SE MCL does not supportasynchronous sessions.

062 ING_noobjvar_error CCNTL, ICNTL, APROF error. The variable name that represents anobject attribute for a CPC or image was not specified. The execution ofthe command is rejected. Contact your IBM Support Center.

063 ING_objvar_invalid_error CCNTL, ICNTL, APROF error. The variable name that was specified inthe HW command is not supported; the command is rejected. Specifya valid variable name and retry the command.

064 ING_objvar_opcode_error CCNTL, ICNTL, APROF error. The internal opcode indicating a GET or aSET operation was not recognized. The command failed. Contact yourIBM Support Center.

065 ING_noobjvar_value_error CCNTL, ICNTL, APROF error. The required value operand for a SEToperation was not specified. The command is rejected. Contact yourIBM Support Center.

066 ING_aprf_error APROF OPEN error. The allocation of storage for a activation profile listfailed. Contact your IBM Support Center.

067 ING_isopen_error APROF OPEN error. Activation profiles are already open, the requestwas rejected. Issue a APROF CLOSE request first.

068 ING_ptype_error APROF error. The specified activation profile type is wrong. Allowedprofile types are: RESET, IMAGE, or LOAD

069 ING_not_open_error APROF error. Profiles are not OPEN. The requested profile function isrejected. Perform APROF OPEN and repeat the request.

Condition Codes




06A ING_profile_not_found APROF READ/UPDATE error. The profile name that was specified in therequest was not found. Verify the named activation profile and repeatthe request. If the profile was newly created since the last APROFOPEN, close and open the profiles again to pick up the new profilename.

06B ING_profupd_op_error APROF UPDATE error. The update operator in the APROF requestparameter list was not recognized. The request is rejected due to aninvalid parameter list. Contact your IBM Support Center.

06C ING_list_of_vars_error APROF UPDATE error. The variable name list for this profile type couldnot be located. Contact your IBM Support Center.

06D ING_variable_name_not_found_error

APROF UPDATE error. The specified variable name could not be foundin the list of variables for that profile type. Use a valid variable namefor the profile type and reissue the request.

06E ING_variable_value_error APROF UPDATE error. The value specified for the variable was notaccepted. Correct the value and reissue the request.

06F ING_OSSLP_acc_error APROF UPDATE error. The common global access to retrieve theOSSLP data failed. Contact your IBM Support Center.

06G ING_noproctype_error ICNTL and APROF error. The processor type value of the request isinvalid. The request is rejected.

06J ING_DESC_acc_error APROF Update error. The common global access to retrieve the DESCdata failed. Contact your IBM support center.

070 ING_hmccpc_tbl_error Initialization Error: An internal HMC/CPC/IMG table error occurredduring INITCOM processing. Enable AOCTRACE and rerun INITCOM toget additional information about the problem.

071 ING_cpcimg_alloc_error Initialization Error: For an image, the dynamic storage allocationrequest failed during INITCOM processing. Enable AOCTRACE andrerun INITCOM to get additional information about the problem.

072 ING_cpc_config_mismatch Initialization Error: SNMP connections only. For SE connections , theCPC SNA address returned from the SE is different to the CPC SNAaddress configured for the CPCname used in the INITCOM request.For HMC connections, the configured SNA address of the CPCname ofthe INITCOM request is not defined on this HMC. For both connectiontypes the communication is terminated.

080 ING_applname_error RESERVE error. The application name specified to request or release aRESERVE, is not valid. The name must be one to eight characters long.The strings 'LIST,' 'ON', or 'OFF' are not allowed as application names.

081 ING_rsvparm_error RESERVE error. The parameter values following the application name,must be either ON or OFF.

082 ING_session_not_sync CTRLCONS error. Invalid session type of ASYNC encountered. It mustbe SYNC.

083 ING_oocodcmd_error OOCOD error. Invalid OOCOD command provided (it must be STATUS,ACTIVATE, or UNDO).

084 ING_oocodprm_error OOCOD error. No Order Number provided for the OOCOD ACTIVATEcommand.

085 ING_oocodstatus_error OOCOD error. The current ooCoD status of the target does not allowthe action (for example, an UNDO without a previous ACTIVATE).

0A0 ING_invalid_task HW Task Error: The HW communication interface is running on aNetView task that is not the configured task. Module INGHWCOMterminates. For SA z/OS, make sure that you have defined autotasknames with keyword HWOPERnn in your active automation policy. Usethe SA z/OS Config Dialog to verify this.

Condition Codes




0A2 ING_config_error HW Task Error: The configuration information about the NetViewautotask names to be used for the HW communication interfacecannot be retrieved. This happens if the interface is called but SA z/OSinitialization is not complete. This error also happens if the autotasksare not defined. See error code 0A0 for additional information.

0A3 ING_capability_check_err HW Task Error: During INGHWCOM initialization on the HW task, theproduct's capability information could not be accessed or is not valid.The INGHWCOM module terminates. Verify that this INGHWCOMmodule is called in the correct product environment, which mustprovide capability information.

0A4 ING_capability_scope_exceeded HW Task Error: After successfully establishing a connection, it wasdetected that the addressed target CPC is not the local CPC. Theproduct licence capability scope however supports only localconnections. This condition is detected during INITCOM discovery.The request is REJECTED. Repeat the local connection request,addressing the local CPC.

090 ING_tcmnolist_error No temporary capacity record list found.

091 ING_notobject_error Object not found. In this case, the temporary capacity record objectwas not found.

092 ING_tcmrecfnd_error No matching record found for the provided record ID.

093 ING_xml_parse_error Error found while parsing temporary capacity record XML data.

094 ING_xml_compose_error Error found while composing temporary capacity add or remove XMLdata.

095 ING_cpctcm_alloc_error Error occurred while allocating storage for TCM records data.

096 ING_stpnodata_error STP error. STP information could not be retrieved from the HW. Eitherthe HW does not support STP or the XML data is invalid.

097 ING_pwrnostat_error POWERMOD error. Current power mode value could not be retrieved.

098 ING_pwrnolist_error POWERMOD error. Supported power modes list could not be retrieved.

099 ING_pwrnoallw_error POWERMOD error. Power mode change allowed flag could not beretrieved.

100 ING_pwrcommnd_error POWERMOD error. Invalid command used with POWERMOD.

101 ING_pwrattrib_error POWERMOD error. Invalid UPDATE parameter.

102 ING_XML_alloc_error The allocation of storage for XML parser failed. Contact your IBMSupport Center.

0AA ING_session_suspended HW Task Error: Connections or sessions to the addressed CPC havebeen previously suspended. In this state any HW request or sessioninitialization request is rejected. You must use the RESUME commandto restore the normal operation mode for this CPC connection.

0B0 ING_suspend_set_error SUSPEND error: While executing a SUSPEND request an erroroccurred. (1) The suspend state is controlled with the common globalvariable xxx.0SUSPEND.cpcnetid.cpcnau (where xxx is either ING orISQ) and there was an error reading or setting this variable. Look foradditional messages in the netlog. It may be necessary to correct thesuspend flag common global variable manually.

0B1 ING_resume_set_error RESUME error: While executing a RESUME request an error occurred.(1) A suspend state is controlled with the common global variablexxx.0SUSPEND.cpcnetid.cpcnau (where xxx is either ING or ISQ) andthere was an error resetting this variable. Look for additionalmessages in the netlog. It may be necessary to correct the suspendflag common global variable manually to resume the session.

0B2 ING_suspend_term_error SUSPEND error: While executing a SUSPEND request an erroroccurred. The session termination failed. The suspend state is set. If aRESUME is executed, it does not attempt to reinitialize the connection.

Condition Codes




0B3 ING_resume_init_error RESUME error: While executing a RESUME request an error occurred.The session reinitialization failed. The suspend state is unset. Youmust perform session reinitialization using INITCOM.

0B4 ING_suspend_prohibited_for_HMC SUSPEND error: A Suspend operation was attempted while an HMCconnection was being used to communicate with the addressed CPC.Only SE connections are supported.

Data Exchange Services "0B100xxx"Table 12 on page 560 lists the condition codes that are returned if there is an error with the followingINGHWCMD functions:

• ACTIVATE• APROF• CCNTL• CBU• CTRLCONS• DEACTIVATE• EXTERNAL• GETISTAT• GETSINFO• GETSSTAT• ICNTL• INITCOM• LOAD• OOCOD• RESERVE• RESTART• START• STOP• SYSRESET• TERMCOM

The condition code data "xxx" prefixed by 0B100 is returned as part of the following response messages,with a status value of REJECTED or FAILED:

• AOFA0001• AOFA0002• AOFA0004• AOFA0006• AOFA0007• AOFA0017• AOFA0018• AOFA0020

For additional return code information see the section "Data Exchange API Call Return Codes", in theappendix "API Return Codes" of the most current release of System z Application Programming Interface,SB10-7030.

Condition Codes


Table 12. Data Exchange Services Condition Codes

Condition Code Error String

001 HWMCA_DE_NO_SUCH_OBJECT This condition indicates that an object (CPC, Image, Profile) or anassociate attribute cannot be found for this request in the SNMP MIB data base of the SE or HMC. Apossible cause can be that an object has been requested that is not available on this CPC's type orCPC's micro code level.

Additional information for INITCOM requests:

• If this condition code is returned from an INITCOM request, a Set request for the console object itselfdid not work. A possible cause is an API configuration problem on the target SE or HMC.

1. The community name settings in the SE or HMC may not allow access from your location due toan invalid netmask specification.

2. (BCPii only) Make sure that the community name that is specified in the Enable API window isalso defined in the SNMP Settings window and has the IP address of the first LAN adapter of theSE defined with it. This information is valid only for SE Workplace versions 1.6.2–1.8.2.

002 HWMCA_DE_INVALID_DATA_TYPE

003 HWMCA_DE_INVALID_DATA_LENGTH

004 HWMCA_DE_INVALID_DATA_PTR

005 HWMCA_DE_INVALID_DATA_VALUE If this condition code is returned from an ICNTL request, thevariable value is not accepted by the HW. This means either the value is below or above a range ofaccepted values (such as a negative value, where only 0 or positive values are allowed), or a certainvariable value conflicts with the setting of a related variable. If, for example, the value of the initialprocessing weight, PWI, is set below the value of the minimum processing weight, PWMN this requestfails with a condition code of 005.

006 HWMCA_DE_INVALID_INIT_PTR

007 HWMCA_DE_INVALID_ID_PTR

008 HWMCA_DE_INVALID_BUF_PTR

009 HWMCA_DE_INVALID_BUF_SIZE

010 HWMCA_DE_INVALID_DATATYPE_PTR

011 HWMCA_DE_INVALID_TARGET

012 HWMCA_DE_INVALID_EVENT_MASK

013 HWMCA_DE_INVALID_PARAMETER

014 HWMCA_DE_READ_ONLY_OBJECT

015 HWMCA_DE_SNMP_INIT_ERROR This is a condition code that can be retried.

016 HWMCA_DE_INVALID_OBJECT_ID

017 HWMCA_DE_REQUEST_ALLOC_ERROR

018 HWMCA_DE_REQUEST_SEND_ERROR For SNMP sessions only: If possible, enable the INGHWCOM traceand repeat the request. Additional TCP/IP error information will be in an error message (EDC) from theLE runtime environment. Have the z/OS LE Run-Time Messages manual available for reference.

019 HWMCA_DE_TIMEOUT For SNMP sessions only: If possible, enable the INGHWCOM trace and repeat therequest. Additional TCP/IP error information will be in an error message (EDC) from the LE runtimeenvironment. Have the z/OS LE Run-Time Messages manual available for reference. Verify if the networkaddress and the network mask specified in the SE/HMC for the community name are valid. Addressfield and mask field are logically ANDed. If the result is 0, the request may fail with a TIMEOUT. Notethat address and mask fields positions that are both 0 are not ANDed.

020 HWMCA_DE_REQUEST_RECV_ERROR

Condition Codes


Table 12. Data Exchange Services Condition Codes (continued)


021 HWMCA_DE_SNMP_ERROR Check that the SNMP API is enabled on the SE/HMC. Check if the SNMPcommunity name access is set to READ & WRITE.

For BCPii connections check if the loopback address 127.0.0.1 is defined to SNMP and to TCP/IP. Onthe SE use the Network Diagnostic Information to determine this.

For GET*, ICNTL, or APROF(Profile) requests this error may also indicate one of the following:

(1) - Same as 005 HWCA_DE_INVALID_DATA_VALUE(2) - Same as 001 HWCA_DE_NO_SUCH_OBJECT(3) - Error in SE/HMC microcode for an object attribute used in the request

022 HWMCA_DE_INVALID_TIMEOUT

028 HWMCA_DE_INVALID_HOST

029 HWMCA_DE_INVALID_COMMUNITY There are two possible reasons for this:

1. SNMP community on the HMC/SE does not match the SA Policy coding. Compare the coding in theSA Policy Processor entry and the one on the HMC/SE. Please note that the Community name iscase-sensitive, on the HMC/SE. Community names must be entered in uppercase.

2. RACF profiles (HSA.ET32TGT.xxxx) are missing. Check if required HSA.ET32TGT.xxxx profiles exist.For details about required RACF Profiles, please refer to the appendix "Security and Authorization"of IBM Z System Automation Planning and Installation.

For INTERNAL (BCPii) connections, this condition code report may also provide the following senseinformation: 080F0001 End-user not authorized: The requesting end-user does not have access to therequested resource.

1. Make sure, the Auth Token/Community Name specifications of the Processor Information policy arein upper case and are identical to the upper case definitions made in the addressed SE/HMC. Usethe ACSADMIN task "API Settings" to validate the definitions on the SE/HMC side.

Besides, check if all other parameters of the "API Settings" entry (Address, Network Mask, AccessType) are defined as documented in Step 7: Preparing the Hardware of IBM Z System AutomationPlanning and Installation.

2. Make sure, the Cross Partition Authority Flag of the requesting system's LPAR is enabled. Performthe SYSPROG task "Change LPAR Security" on the Support Element of the requesting system's CPCto validate this. This is applicable for INTERNAL connections only.

3. Make sure, the 'LIC Change enabled' flag is set on all HMCs in your processor LAN, in case therequest fails only if it targets another than the local CPC. Perform the SYSPROG task "CustomizeConsole Services" to validate and change the flag. This is applicable for INTERNAL connectionsonly.

4. Make sure, the UNICODE libraries SYS1.SCUNLOCL and SYS1.SCUNTBL are both available,accessible and cataloged on the system that issues the request.

5. If steps 1-4 could not resolve this condition code, look for any SAF messages, like RACF's ICH408Iwhich may indicate the user not being authorized to access the HW resource.

030 HWMCA_DE_INVALID_QUALIFIER

074 HWMCA_DE_AUTHORIZATION_ERROR

A data exchange API request was issued targeting a CPC or CPC image over BCPii. The targeted CPChas BCPii permission settings that do not allow this from the requesting CPC image.

BCPii permission settings are controlled using the Image Activation Profile of the targeted CPCpartition.

095 HWMCA_DE_UNKNOWN_USERNAME

SNMPv3 User on the HMC/SA does not match the System Automation policy definitions.

096 HWMCA_DE_INCORRECT_PASSWORD

SNMPv3 Password on the HMC/SA does not match the System Automation policy definitions forSNMPv3 user. If keyword SAFPW is used in the System Automation Policy, then incorrect password isstored in the System Automation Password store (INGPW).

Condition Codes


https://www.ibm.com/support/knowledgecenter/SSWRCJ_4.2.0/com.ibm.safos.doc_4.2/InstallPlan/Configurestep_hw_prepare.html

Table 12. Data Exchange Services Condition Codes (continued)


097 HWMCA_DE_INVALID_STACKNAME (SNMP connections only)

During INITCOM request, the IP stackname supplied caused the internal setibmopt() call in theHwmcaInitialize() request to fail. The setibmopt call sets which IP stack is to be used for allsubsequent TCP/IP calls over a socket connection.

The IP stackname must be stored in the NetView Cglobal variable 'ISQHW.netid.nau.OTCP' prior to theINITCOM call. Note that the CS TCP/IP configuration must have the usage of multiple IP stacks enabledcorrectly, otherwise any setibmopt call will fail, even if the default stackname is specified. If multiple IPstack environment is not configured on the system, do not specify a stackname for SNMP connections.This definition is done in the SA Customization dialog, Option 10 'Processors', Processor Info, entry field'IP stack'.

098 HWMCA_DE_REQUIRES_QUALIFIER

099 HWMCA_DE_TRANSPORT_ERROR Check that the BCP Internal Interface modules are correctly installed.Module or module version error detected in LPA lib or LNKLST.

Command Services "0B200xxx"Table 13 on page 562 lists the condition codes that are returned if there is an error with the followinghardware functions:

• ACTIVATE• CBU• DEACTIVATE• EXTERNAL• LOAD• OOCOD• RESTART• START• STOP• SYSRESET• TCM• POWERMOD• STP

The condition code data "xxx" prefixed by 0B200 is returned as part of the AOFA0001 response messagewith a status value of REJECTED or FAILED.

For additional return code information refer to the section "Data Exchange API Call Return Codes", in theappendix "API Return Codes" of the most current release of System z Application Programming Interface,SB10-7030.

Table 13. Command Services Condition Codes


000 HWMCA_CMD_STARTED_BUT_COMPLETION_MAY_HAVE_FAILED

An HW command was successfully started. For SYNC sessions check the AOFA0001 commandcompletion report for additional sense information about the actual command completion. With ASYNCsessions, the command completion event report contains this information, and applications can registerfor it with the FILTER command.

001 HWMCA_CMD_NO_SUCH_OBJECT

An HW command has been requested that is not available on this HW type or microcode level.

002 HWMCA_CMD_INVALID_DATA_TYPE

Condition Codes


Table 13. Command Services Condition Codes (continued)


003 HWMCA_CMD_INVALID_DATA_LENGTH

004 HWMCA_CMD_INVALID_DATA_PTR

005 HWMCA_CMD_INVALID_DATA_VALUE

006 HWMCA_CMD_INVALID_INIT_PTR

007 HWMCA_CMD_INVALID_ID_PTR

010 HWMCA_CMD_INVALID_DATATYPE_PTR

011 HWMCA_CMD_SNMP_ERROR_INCONSISTENT_NAME

A command request was received while a prior request was just finished. The prior task is still notcomplete, but it has released the RESERVE already. This is a temporary condition and the request canbe repeated.

013 HWMCA_CMD_INVALID_PARAMETER

017 HWMCA_CMD_REQUEST_ALLOC_ERROR

018 HWMCA_CMD_REQUEST_SEND_ERROR

For SNMP sessions only: If possible, enable the INGHWCOM trace and repeat the request. AdditionalTCP/IP error information will be in an error message (EDC) from the LE runtime environment. Have thez/OS LE Run-Time Messages manual available for reference.

019 HWMCA_CMD_TIMEOUT

For SNMP sessions only: If possible, enable the INGHWCOM trace and repeat the request. AdditionalTCP/IP error information will be in an error message (EDC) from the LE runtime environment. Have thez/OS LE Run-Time Messages manual available for reference.

020 HWMCA_CMD_REQUEST_RECV_ERROR

021 HWMCA_CMD_SNMP_ERROR

022 HWMCA_CMD_INVALID_TIMEOUT

023 HWMCA_CMD_INVALID_CMD

024 HWMCA_CMD_OBJECT_BUSY

025 HWMCA_CMD_INVALID_OBJECT

026 HWMCA_CMD_COMMAND_FAILED

027 HWMCA_CMD_INITTERM_OK

028 HWMCA_CMD_CBU_DISRUPTIVE_OK

029 HWMCA_CMD_CBU_PARTIAL_HW

030 HWMCA_CMD_CBU_NO_SPARES

031 HWMCA_CMD_CBU_TEMPORARY

032 HWMCA_CMD_CBU_NOT_ENABLED

033 HWMCA_CMD_CBU_NOT_AUTHORIZED

034 HWMCA_CMD_CBU_FAILED

035 HWMCA_CMD_CBU_ALREADY_ACTIVE

036 HWMCA_CMD_CBU_INPROGRESS

038 HWMCA_CMD_INVALID_MACHINE_STATE

The command request cannot be performed at this time because the target object is currently not in anappropriate state (that is, it is not powered on).

039 HWMCA_CMD_NO_RECORDID

The command request was unsuccessful because the specified capacity record with the specifiedidentifier does not exist.

Condition Codes




040 HWMCA_CMD_NO_SW_MODEL

The command request was unsuccessful because the specified software model is invalid for the targetobject.

041 HWMCA_CMD_NOT_ENOUGH_RESOURCES

The command request was unsuccessful because the request specifies more resources than arecurrently available on the target object.

042 HWMCA_CMD_NOT_ENOUGH_ACTIVE_RESOURCES

The command request was unsuccessful because the request specifies more resources than arecurrently active on the target object.

043 HWMCA_CMD_ACT_LESS_RESOURCES

The command request for additional resources was unsuccessful because the request specifies a netdecrease in the resources for the target object.

044 HWMCA_CMD_DEACT_MORE_RESOURCES

The command request for the removal of resources was unsuccessful because the request specifies anet increase in the resources for the target object.

045 HWMCA_CMD_ACT_TYPE_MISMATCH

The command request was unsuccessful because the type value specified (real or test) was not valid forthe type of capacity record being used.

046 HWMCA_CMD_API_NOT_ALLOWED

The command request was unsuccessful because the target Defined CPC was configured not to allowcapacity changes via the Console Application Programming Interfaces.

047 HWMCA_CMD_CDU_IN_PROGRESS

The command request cannot be performed at this time because a concurrent driver upgrade operationis being performed.

048 HWMCA_CMD_MIRRORING_RUNNING

The command request cannot be performed at this time because a support element mirror operation isbeing performed.

049 HWMCA_CMD_COMMUNICATIONS_NOT_ACTIVE

The command request cannot be performed at this time because communications with the Defined CPCobject are not active.

050 HWMCA_CMD_RECORD_EXPIRED

The command request was unsuccessful because the capacity record being used for the operation hasexpired.

051 HWMCA_CMD_PARTIAL_CAPACITY

The command request was successful, but not all of the resources that were requested could be madeavailable.

052 HWMCA_CMD_INVALID_REQUEST

The command request was unsuccessful because it is not valid to be performed at this time due to oneof the following conditions.

• An Enhanced Driver Maintenance (EDM) operation is currently in progress.• The target of the request is configured to not allow capacity change API requests.• The targeted system is not in the correct state to perform the request.

Retry the command request at a later time after the system is in the correct state to allow the operation.

053 HWMCA_CMD_ALREADY_ACTIVE

The command request was unsuccessful because there is a different capacity record that is alreadyactive.

Condition Codes




054 HWMCA_CMD_RESERVE_HELD

The command request was unsuccessful because a task running on the targeted system has reservedcontrol. Wait until the task is complete and retry the command request.

055 HWMCA_CMD_GENERAL_XML_PARSING_ERROR

The command request was unsuccessful because the XML specified on the command is not well formedand could not be parsed properly. Retry the command request with a well formed XML document.

056 HWMCA_CMD_STP_NOT_ENABLED

The command request was unsuccessful because STP is not enabled on the target system. Verify thatthe request is targeted toward a system that has the STP feature enabled.

057 HWMCA_CMD_STP_MUST_TARGET_CTS

The command request failed because the targeted system is not the Current Time Server for the STP-only Coordinated Timing Network (CTN) or the system specified to become the Current Time Serverdoes not match the targeted system.

Verify that the request is targeted toward the system that will be the Current Time Server after thecommand request and resubmit the request.

058 HWMCA_CMD_STP_INVALID_CONFIG_SPECIFIED

The command request was unsuccessful because the specified STP configuration is not valid. Verify thatthe current configuration will support the command request and that the configuration specified in thecommand request is valid. Retry the command request with an appropriate STP configuration.

059 HWMCA_CMD_STP_WRONG_CTN

The command request was unsuccessful because the CTN ID of the current STP configuration is notvalid for the request. This is most likely the result of the configuration changing between the time thatthe command request was created and the time the request was processed.

Verify that the current configuration will support the command request and that the configurationspecified in the command request is valid. Then retry the command request with an appropriate STPconfiguration.

060 HWMCA_CMD_STP_NOT_VALID_FOR_CTS

The command request cannot be processed on the Current Time Server. Certain actions are not allowedon the Current Time Server because the result would be disruptive to the entire STP-only CTN. Verifythat the request is targeted toward the appropriate system.

061 HWMCA_CMD_STP_IN_ETR_MIGRATION

The command request was unsuccessful because the CPC is a member of an STP-only CTN that ismigrating back to a Mixed CTN, which uses a Sysplex Timer. STP-related commands are not alloweduntil this procedure is complete. Determine the appropriate action after the ETR migration is complete.

062 HWMCA_CMD_STP_NODE_NOT_FOUND_IN_SYSTEM_LIST

The command request was unsuccessful because the specified NodeName could not be converted intoa NodeID. The system referenced in the NodeName tag needs to be a Defined CPC object on the HMCconsole. Add the object to the HMC and retry the command request.

063 HWMCA_CMD_STP_CTNID_TAG_ERROR

The command request was unsuccessful because the CTN ID portion of the set STP configuration XMLwas not correct. Retry the command request after verifying that the specified CTN ID information is inthe proper format.

064 HWMCA_CMD_STP_NODE_TAG_ERROR

The command request was unsuccessful because the Preferred Time Server, Backup Time Server, orArbiter portion of the set STP configuration XML was not correct. Retry the command request afterverifying that the specified node information is in the proper format.

065 HWMCA_CMD_STP_CONFIG_TAG_NOT_FOUND

The command request was unsuccessful because the STPConfiguration tag was not found in the set STPconfiguration XML. Specify STPConfiguration as the outermost tag of the XML document and retry thecommand request.

Condition Codes




066 HWMCA_CMD_STP_ACTIVE_CTS_TAG_ERROR

The command request was unsuccessful because the CurrentTimeServer portion of the set STPconfiguration XML was not correct. Verify that the specified CurrentTimeServer information is in theproper format and retry the command request.

067 HWMCA_CMD_STP_INITIALIZE_INCOMPLETE

The command request was unsuccessful because the specified STP configuration cannot be set untilinitialization of the STP-only CTN is complete. The time zone and leap second values need to be set.Manually set the time zone and leap second values via the Initialize Time button on the NetworkConfiguration tab in the System (Sysplex) Time task and retry the command request.

068 HWMCA_CMD_STP_INVALID_STP_ID

The command request was unsuccessful because the STP ID specified on the command was notcorrect. Retry the command request specifying an STP ID with 1-8 valid characters.

069 HWMCA_CMD_STP_LINKS_ERROR

The command request was unsuccessful because the communication links between the Preferred TimeServer, Backup Time Server, and/or Arbiter systems in the STP-only CTN are not active. Manually checkthe links between systems in the STP-only CTN with the roles of Preferred Time Server, Backup TimeServer, and/or Arbiter or retry the command request with force, if applicable.

070 HWMCA_CMD_STP_REQUIRES_FORCE_TO_CONFIGURE

The command request was unsuccessful because of the current state of the targeted system.Verification of connections between systems with key roles in the STP-only CTN is done to ensure thatthe configuration will function properly. Once the connections are verified, the force parameter isrequired to ensure that the customer is not creating an island STP-only CTN. Retry the set configurationcommand request with force, if applicable.

071 HWMCA_CMD_PROCESSOR_POWER_MODE_NOT_ENTITLED

072 HWMCA_CMD_PROCESSOR_POWER_MODE_NOT_ALLOWED

073 HWMCA_CMD_PROCESSOR_POWER_MODE_GROUP_CONTROLLED

074 HWMCA_CMD_AUTHORIZATION_ERROR

A command service API request was issued targeting a CPC or CPC image over BCPii. The targeted CPChas BCPii permission settings that do not allow this from the requesting CPC image.

BCPii permission settings are controlled using the Image Activation Profile of the targeted CPC partition.

099 HWMCA_TRANSPORT_ERROR

Before the HwmcaCmd was invoked, an internally issued data entry Hwmca call terminated with CC 99.Same as HWMCA_DE_TRANSPORT_ERROR condition code 0B100099.

Internal Transport Services "0Bx00xxx"Note that this set of condition codes applies to BCP Internal Interface connections only.

Table 14 on page 567 lists the condition codes that are returned if there is an error with the followingINGHWCMD functions:

• ACTIVATE• CBU• CTRLCONS• DEACTIVATE• EXTERNAL• GETISTAT• GETSSTAT• INITCOM• LOAD

Condition Codes


• OOCOD• RESTART• START• STOP• SYSRESET• TERMCOM

The condition code data "xxx" prefixed by 0B100 or 0B200 is returned as part of the following responsemessages, with a status value of REJECTED or FAILED:

• AOFA0001• AOFA0002• AOFA0004• AOFA0017• AOFA0018

Table 14. Internal Transport Services Condition Codes

Reason Code Error Description

100 A problem was encountered prior to sending the request to the HSAET32 API for processing. This islikely due to a failure to an environmental error. Check whether the Support Element is fully operational.A running reboot of the SE may have caused this problem.

101 A request incomplete condition occurred.

102 A report list overflow occurred. This return code should not currently be issued for SNMP requests,however is included for OCF query (Query-Read-Cluster) compatibility.

110 The issuer of the request is not (RACF) authorized to the requested function. Note that (like HCD) theHSAET32 services require that RACF or a compatible SAF product be installed and operational.

An RACF system message ICH408I is issued with additional information. If no ICH408I message isissued, make sure the class FACILITY is RACLISTed and repeat the request.

111 The control block ID or version of the HSDB passed to HSAET32 services is invalid. For hwmcaapirequests, this indicates that HSAPHCPI is incompatible with the supporting HSAPHARI module.

112 The requested function is invalid or not supported by the current level of HSAET32 services. Forhwmcaapi requests, this indicates an incompatibility between HSAPHCPI and the supportingHSAPHARI module.

113 The control block ID of the request list passed to HSAET32 services is invalid or inappropriate for therequested function. For hwmcaapi requests, this indicates a problem in module HSAPHCPI.

114 The request list entry count passed to HSAET32 services is invalid or inappropriate for the requestedfunction. For hwmcaapi requests, this indicates a problem in module HSAPHCPI.

115 The request list entry pointer passed to HSAET32 services is null and therefore invalid. For hwmcaapirequests, this indicates a problem in module HSAPHCPI.

116 Some of the input areas passed to HSAET32 services exist in a storage area that the caller does nothave authority to fetch or update.

117 The input parameter list generated by the HSAXHARI (or CBDIHSD) macro does not have the correctversion ID or type, or does not point to an HSDB.

118 The control block ID of the Output Report request list passed to HSAET32 services is invalid orinappropriate for the requested function. For hwmcaapi requests, this indicates a problem in moduleHSAPHCPI.

119 The session token is invalid. This is probably due to a previous failure of the hwmcainitialize request, anhwmcaterminate request being issued for the session, or improper modification of theHWMCA_SCLP_TARGET_INFO structure.

120 The host environment does not support HSAET32 services. HSAET32 services are not currently on VMhosts.

121 An address space resource manager could not be established.

Condition Codes


Table 14. Internal Transport Services Condition Codes (continued)


122 A task resource manager could not be established.

123 The HSAET32 associated recovery routine (HSAPHARR) was entered due to an unexpected errorprocessing the request.

124 The CBDMHWA CSECT could not be found in the nucleus.

125 The HSAET32 monitor exit (HSAPHMON) could not be established as the secondary ET32 listner exit forthe application.

126 The system date and time could not be obtained to correlate HRE and associated MDS-MU's.

127 A failure occurred attempting to access the HWAX.

129 An attempt to send the MDS_MU requests across the BCP Internal Interface interface failed.

130 Either the EP_OPERATIONS_MGMT vector (9F22) from the event type 30 data was not available or itslength was invalid.

131 Either the application name-group for the EP_OPERATIONS_MGMT application (event type 30 data) wasnot returned in the 9F22 vector or its length was invalid.

132 Either the NetID of the local support element was not returned in the application name-group for theEP_OPERATIONS_MGMT application (event type 30 data) or its length was invalid.

133 Either the NAU of the local support element was not returned in the application name-group for theEP_OPERATIONS_MGMT application (event type 30 data) or its length was invalid.

134 Either the CPC image name vector (9F70) from the event type 30 data was not available or its lengthwas invalid.

135 Error in ET30 ESTAE routine. Module HSAPHSDI was unable to establish an ESTAEX recoveryenvironment.

136 Either the primary OCF name vector (9F81) from the event type 30 data was not available or its lengthwas invalid.

140 BCP Internal Interface Access Error. HSAET32 services have been disabled or were not been started.

148 BCP Internal Interface Session Error. The hardware session with the target CPC has terminated. This iscondition is raised due to a missing heartbeat from the ET32 agent code running on the target SE. Torecover from this situation the application should perform a TERMCOM followed by an INITCOM in orderto reestablish session communication. The occurrence of this RC indicates that possibly events havebeen lost.

150 Error in ET32 ESTAE routine.

151 HSAPHSPI identified a parameter that is not contextually valid.

152 HSAPHSPI identified a missing parameter that is contextually required.

153 HSAPHSPI identified a parameter value that is syntactically incorrect.

160 IEAMSCHD_Error. An error has occurred attempting to schedule HSAPHDSC for execution. AnIEAMSCHD return code is also provided to further explain the cause of the error.

161 CSS_Error. An error condition was raised using callable supervisor services facilities. The IEAVxxxxreturn code is also provided to further explain the cause of the error.

162 CPSS_Error. An error condition was raised using cellpool services facilities. The CSRPxxx return code isalso provided to further explain the cause of the error.

163 HSAPHDSC_Error. An error condition was raised using callable supervisor services facilities. TheIEAVxxxx return code is also provided to help identify the cause of the error.

164 CTRACE_Error. An error condition was encountered by module HSAPHDSC, and is further identified bythe return code also provided.

165 An error condition was encountered while attempting define (or delete) the application to ComponentTrace. The CTRACE return code is also returned to help identify the cause of the error.

166 HSAPHDSC Error. The Access List Service macro ALESERV returned an error condition. Report theavailable sense data of the AOFA0001 response when contacting your IBM Support Center.

Condition Codes




167 HSAPHDSC Error. The TCB Token Service macro TCBTOKEN returned an error condition. Report theavailable sense data of the AOFA0001 response when contacting your IBM Support Center.

168 HSAPHDSC/HSAPHMNX Error. The Data Space Service macro DSPSERV returned an error condition.Report the available sense data of the AOFA0001 response when contacting your IBM Support Center.

169 HSAPHARI Error. The Component Trace Service returned an error condition. Report the available sensedata of the AOFA0001 response when contacting your IBM Support Center.

170 HSAPHARI/HSAPHMNX Error. The Callable CellPool Service CSRPEXP returned an error condition.Report the available sense data of the AOFA0001 response when contacting your IBM Support Center.This condition, together with sense code 09000008, indicates a shortage of HSAET32 dataspace. As acircumvention, in some cases it helps to restart NetView auto operators (AUTHWnnn tasks) used forINTERNAL connection. Issue command: STOP TASK=AUTHWnnn - the AUTHWnnn task will beautomatically restarted.

171 HSAPHARI Error. The Name Token Service IEANTCR returned an error condition. Report the availablesense data of the AOFA0001 response when contacting your IBM Support Center.

180 HSAPHMNX Error. The maximum length (HSDB_SPMAX), a Support Element spanned data package canbe transported over the SA-BCPii, is exceeded. The transport of the data package is aborted. ContactIBM Support and have the information about the failing request available.

181 HSAPHMNX Error. A Support Element spanned data package is detected, however its type isundermined. The transport of data package is aborted. Contact IBM Support and have the informationabout the failing request available.

204 The request was accepted by the local support element and will be processed asynchronously. Nofurther reason code is provided. (This function is not currently used by the hwmcaapi implementation).

208 Execution of request was failed by the target support element. This indication is normally accompaniedby a condition report that is returned as the error reason, and may also be accompanied by sense datafurther identifying the cause of the failure.

212 The request was rejected by the local Support Element (SE). This indication is normally accompanied bya condition report that is returned as the error reason.

1. This condition, together with sense code 081C00BA, may occur if the addressed CPC is not identicalwith your own CPC and is correctly defined to the SA z/OS BCPii, but is not defined as a CPC to themaster HMC. The master HMC is used by the HW to route a request to a remote CPC.

In the processor LAN environment, an HMC acts as a master HMC if it has the LIC Change servicesflag enabled. If you have several master HMCs in your environment, each master HMC should havethe same set of CPCs defined for it that you want to access over the BCPii. If you are connected toyour own CPC, you can use the GETCLUSTER common command to find out which other CPCs aredefined to the master HMC that the BCPii is currently using.

2. At the time this error occurred, the SE was not available due to a reboot or the SE was disconnectedto the processor HW.

3. This condition, together with sense code 080F0001, may occur if

a. The Cross Partition Authority Flag is not set for the logical partition that is issuing the SA-BCPiiHW request.

b. On CPCs supporting BCPii permissions, the check-box flag "Enable the partition to sendcommands" is not set.

216 An MDS-MU error message was received from the target support element. The condition report code isreturned as the error reason.

220 HSAPHMNX detected a structural error while processing the incoming report from the target SupportElement. If the SENSE field contains data, check whether the first byte has a value of X'27'. In this case,a request length difference was detected between the data coming from the OS and what was returnedfrom the target Support Element. Note that in this case a LOGREC software symptom record is writtencontaining additional data. (HSAET32)

224 No response was received within the time interval designated for the request. No further reason codeprovided.

228 An error was detected in a request list entry. An internal reason code is generated to identify the field inerror. (This code is not used for hwmcaapi requests).

232 A routing error has occurred while forwarding the requests for processing. This indication is normallyaccompanied by a condition report that is returned as the error reason.

Condition Codes




270 HSAPHMNX Error. The Callable CellPool Service CSRPGET returned an error condition. Report theavailable sense data of the AOFA0001 report when contacting your IBM Support Center.

This condition, together with sense code 09000008, indicates a shortage of the HSAET32 dataspace. Asa circumvention, in some cases it helps to restart the NetView auto operators (AUTHWnnn tasks) usedfor INTERNAL connection. Issue the command: STOP TASK=AUTHWnnn - the AUTHWnnn task will beautomatically restarted.

Condition Codes


Appendix C. Sense Codes, Hardware Object StatusSummary

Sense CodesNote that for BCP Internal Interface connections the sense codes are copied from the request responsereport information into the AOFAxxxx messages.

For detailed sense data information refer to the appendix "HWMCA_EVENT_COMMAND_RESPONSEReturn Codes" in the most current release of System z Application Programming Interface, SB10-7030.

To display online help for a sense code, use the NetView SENSE command followed by the 8-charactersense code parameter from the AOFAxxxx report string that is returned.

0806000A RESOURCE UNKNOWN

ExplanationThe profile name (CNAME) specified in a operationscommand is not recognized by the receiving node.

System programmer responseCorrect the configuration identifier and resend therequest.

08090000 Mode inconsistency: Therequested function cannot beperformed in the present state ofthe receiver.

ExplanationThis command is prohibited because the target is in anincompatible mode. For example, an ITIMER request isnot accepted when the system is power-on reset inLPAR mode.

System programmer responseThis function cannot be performed in the present stateof the receiver. Retry the request after the target modestatus has changed.


ExplanationAcceptance of the command is prohibited because thetarget is in an incompatible mode. For example, anITIMER request is not accepted when the system ispower-on reset in LPAR mode.

System programmer responseNone. This function cannot be performed in thepresent state of the receiver.


ExplanationThe receiving Hardware Management Console is not inthe correct state to automatically dial out using theattached modem.

System programmer responseEnsure the receiving Hardware Management Consoleis customized to use the autodial and RSF functions.


ExplanationOperations management control is not enabled.

System programmer responseEnable the system for automated operations andresend the request. Ensure that the Emergency PowerOff switch is on.

080A000A Permission rejected: The receiverhas denied an implicit or explicitrequest of the sender.


ExplanationA STATLEV request was rejected because it was notcompatible with the status reporting values set in thereceiver.

System programmer responseCorrect the STATLEV value and resend the request.

080A000C Permission rejected: The receiverhas denied an implicit or explicitrequest of the sender.

ExplanationA SETCLOCK request has failed because it requiredthat a clock be set in a configuration where a dominanttiming source has priority.

System programmer responseIf the Sysplex Timer is the dominant timing source theSOURCE, TIME, UTCO, and OFFSET operands cannotbe used in the command string. Remove theseoperands and resend the request.

080C0005 Procedure not supported: Aprocedure specified is notsupported in the receiver.

ExplanationThe command is not supported.

System programmer responseResend the request using a supported command, ifpossible.

080C0007 Procedure not supported: Aprocedure specified is notsupported in the receiver.

ExplanationA request for a function is supported by the receiver,but the resource identified in the request does notsupport that function. This function cannot becanceled.


080F0001 End-user not authorized: Therequesting end-user does not haveaccess to the requested resource.

ExplanationAuthorization checks have not been successfullypassed.

System programmer responseCorrect the command authorization-token and resendthe request.

08120000 Insufficient resource: The receivercannot act on the request becauseof a temporary lack of resource.

ExplanationSystem resources are temporarily busy.

System programmer responseResend command if required.


ExplanationInsufficient storage is available to the targetcomponent to satisfy the request.

System programmer responseResend command.


ExplanationA timed command was rejected because the OCFtimed operations queue was full.

System programmer responseCancel any unnecessary scheduled requests andresend the command.

08150001 Function active: A request toactivate an element or procedurewas received, but the element orprocedure was already active.

ExplanationUnable to perform the command because the targetCPC Subset or CPC Image is operational and the forceoperand has not indicated the override selection.


System programmer responsePut the system in the appropriate state and resend thecommand.

081A0000 Request sequence error.

ExplanationUnable to perform the command because the targetpartition is in the deactivated state.

System programmer responseActivate the logical partition, then resend the originalrequest.

Hardware Object Status SummaryTable 15 on page 573 lists the status values for CPC and image objects provided by the z Systems API.The status description was taken from the HMC online help because the API documentation does notprovide this information. Note that the status numbers are displayed with the asynchronous reportmessage AOFA0100.

Table 15. Status Values for CPC and Image Objects Provided by the z Systems API

Status Value Number Description

OPERATING 0001 Image: All of the image's processors are operating.

CPC: All of the CPC's processors are operating.

NO POWER® 0004 CPC: CPC power is off.

NOT OPERATING 0002 Image: None of the image's processors are operating, but the exact status of theprocessors vary.

CPC:

If a power-on reset has not been performed: The CPC's processors cannot operate untila power-on reset of the CPC is performed.If a power-on reset was performed: None of the CPC's processors are operating, butthe exact status of the processors vary.

NOT ACTIVATED 0008 Image: The image is defined in the CPC's current input/output (I/O) configuration, but isnot activated.

EXCEPTIONS 0010 Image: At least one of the image's processors is operating, and at least one processor isnot operating, but the exact status of the processors vary.

CPC: At least one of the CPC's processors is operating, and at least one processor is notoperating, but the exact status of the processors vary.

STATUS CHECK 0020 Image: The CPC is not communicating with the support element. The status of the imageand its CPs cannot be determined.

CPC: The CPC is not communicating with the support element.

POWERSAVE 0100 CPC: Utility power for the CPC failed, and one or more of its active control programs putthe CPC in a power save state. The CPC is using only enough power from its alternate,temporary power source to preserve data for the control programs that put it in the powersave state.

Image: The image cannot operate until power for the CPC is restored.

LINK NOT ACTIVE 0080 CPC: The CPC's support element is not communicating with this HMC. The status of theCPC cannot be determined.

SERVICE 0040 CPC: A console operator enabled service status for the CPC (ordinarily done at the requestof a service representative to allow providing service for the CPC).

SERIOUSALERT 0200 No explanation found on the HMCs.

ALERT 0400 No explanation found on the HMCs.

ENVALERT 0800 No explanation found on the HMCs.

SERVICE REQUIRED 1000 The next disruption will result in the CPC operating in degraded capacity, or it will fail tooperate.

Hardware Object Status Summary

Appendix C. Sense Codes, Hardware Object Status Summary 573

Table 15. Status Values for CPC and Image Objects Provided by the z Systems API (continued)

Status Value Number Description

DEGRADED 2000 The CPC was found operating in a degraded state. Note that this status is set on specifichardware. Use the HW command GETSGDR to determine the reason.

Hardware Object Status Summary


Appendix D. Automation Manager Reason Codes

These reason codes listed in Table 16 on page 575 are given in message INGY1004I to indicate that anerror occurred in communicating with the automation manager.

Table 16. Automation Manager Reason Codes

Description Code

PREPROCESSOR_FAILURE 0x00008000

NO_RESOURCES_SELECTED 0x00001004

NO_MATCHES 0x00001008

BROKEN_RELATIONSHIPS 0x0000100C

NO_AGENTS_SELECTED 0x00001010

ROLE_NOT_FOUND 0x00001014

AGENT_NOT_FOUND 0x00001018

NOT_AN_AGENT 0x0000101C

MULTIPLE_AGENTS_FOUND 0x00001020

TABLE_OVERRIDE 0x00001024

TABLE_NOT_FOUND 0x00001028

UNKNOWN_TABLE_SCOPE 0x0000102C

PROCEDURE_NOT_FOUND 0x00001030

INTERNAL_AGENT_SELECTED 0x00001034

REQUEST_SOURCE_NOT_FOUND 0x00001038

REQUEST_NOT_FOUND 0x0000103C

ORDER_IS_NOT_SUPPORTED 0x00001040

RELATIONSHIP_COULD_NOT_BE_ADDED 0x00001044

RELATIONSHIP_NOT_FOUND 0x00001048

TRIGGER_NOT_FOUND 0x0000104C

TRIGGER_LINK_NOT_FOUND 0x00001050

AGENT_LINK_NOT_FOUND 0x00001054

NON_GROUP_AGENT_SELECTED 0x00001058

GROUP_MEMBER_NOT_FOUND 0x0000105C

NOT_A_GROUP_MEMBER 0x00001060

GROUP_POLICY_COULD_NOT_BE_SET 0x00001064

GROUP_MEMBER_POLICY_COULD_NOT_BE_SET 0x00001068

CONFIGURATION_UPDATE_MODE_IS_NOT_SET 0x0000106C

PROCEDURE_COULD_NOT_BE_ADDED 0x00001070

ORDER_NOT_FOUND 0x00001074

PROPAGATION_NOT_FOUND 0x00001078

REQUIRED_TRIGGER_NOT_FOUND 0x0000107C

RESOURCE_COULD_NOT_BE_CREATED 0x00001080

GROUP_COULD_NOT_BE_CREATED 0x00001084

Automation Manager Reason Codes


Table 16. Automation Manager Reason Codes (continued)

Description Code

AGENT_COULD_NOT_BE_CREATED 0x00001088

UNKNOWN_GROUP_TYPE 0x00001090

SUPPORTING_RESOURCE_NOT_FOUND 0x00001094

CONFIGURATION_UPDATE_MODE_IS_STILL_SET 0x00001098

CONFIGURATION_SOURCE_NOT_FOUND 0x0000109C

CONDITION_COULD_NOT_BE_ADDED 0x000010A0

CONDITION_NOT_FOUND 0x000010A4

UNSUPPORTED_INSTRUCTION 0x000010A8

UNKNOWN_INSTRUCTION 0x000010AC

NO_HISTORIES_FOUND 0x000010B0

INVALID_TABLE_SCOPE 0x000010B4

VARIABLE_HISTORY_NOT_FOUND 0x000010B8

VSAM_ERROR 0x000010BC

RESOURCE_NOT_IN_LIST 0x000010C0

SCHEDULE_COULD_NOT_BE_CREATED 0x000010C4

GROUP_MEMBER_COULD_NOT_BE_ADDED 0x000010C8

INVALID_CONFIG_LOCATION 0x000010D0

CONFIG_MAP_COULD_NOT_BE_OPENED 0x000010D4

CONFIG_MAP_READ_ERROR 0x000010D8

CONFIG_MAP_IS_NOT_VALID 0x000010DC

CONFIG_ID_NOT_FOUND 0x000010E0

CONFIG_SET_COULD_NOT_BE_OPENED 0x000010E4

CONFIG_SET_MISSING_PART_ID 0x000010E8

CONFIG_SET_MISSING_PART_TYPE 0x000010EC

CONFIG_SET_INVALID_PART_TYPE 0x000010F0

CONFIG_SET_MISSING_PART_SIGNATURE 0x000010F4

CONFIG_SET_READ_ERROR 0x000010F8

CONFIG_PART_DUPLICATE_SKIP 0x00001104

CONFIG_PART_NO_UPDATE_SKIP 0x00001108

CONFIG_SET_NO_PARTS_FOUND 0x0000110C

CONFIG_PART_COULD_NOT_BE_OPENED 0x00001110

CONFIG_PART_IS_NOT_VALID 0x00001114

CONFIG_PART_READ_ERROR 0x00001118

NO_CONFIG_PARTS_FOUND_FOR_UPDATE 0x0000111C

PROCESSING_CONFIG_PART 0x00001120

DELETING_CONFIG_PART 0x00001124

MESSAGE_NOT_FOUND 0x00001128

NO_MESSAGE_CLASSES_DEFINED 0x0000112C

MESSAGE_IS_NOT_VALID 0x00001130



Table 16. Automation Manager Reason Codes (continued)

Description Code

MESSAGE_COULD_NOT_BE_LOAD 0x00001134

CONFIG_SET_NO_CONFIG_LEVEL_DEFINED 0x00001138

QUALIFIER_IS_NOT_SUPPORTED 0x0000113C

COLUMN_IS_NOT_SUPPORTED 0x00001140

UNREFERENCED_BRANCH_LABEL 0x00001144

BRANCH_LABEL_NOT_FOUND 0x00001148

ARRAY_IS_EMPTY 0x0000114C

TIMER_NOT_FOUND 0x00001150

TIMER_IS_NOT_RUNNING 0x00001154

TIMER_OVERRIDE 0x00001158

TIMER_RESOURCE_NOT_FOUND 0x0000115C

QUALIFIED_TABLE_WITH_BLOCK_COLUMNS 0x00001160

INCOMPATIBLE_PERSISTENT_STATE_IMAGE 0x00001164

PERSISTENT_STATE_IMAGE_PART_COULD_NOT_BE_OPENED 0x00001168

PERSISTENT_STATE_IMAGE_PART_IS_NOT_VALID 0x0000116C

PERSISTENT_STATE_IMAGE_PART_READ_ERROR 0x00001170

PERSISTENT_STATE_IMAGE_PART_WRITE_ERROR 0x00001174

PERSISTENT_STATE_QUEUE_CORRUPTED 0x00001178

OVERRIDE_FILE_NOT_AVAILABLE 0x0000117C

RELATIONSHIP_CLASS_NOT_FOUND 0x00001180

DST_DEACTIVATION_OCCURED 0x00001184

RELATIONSHIP_LOOP_DETECTED 0x00001188

DIAG_INFO_RECORDING_FAILURE 0x0000118C

ALREADY_IN_DIAG_INFO_RECORDING_MODE 0x00001190

NOT_IN_DIAG_INFO_RECORDING_MODE 0x00001194

TIMEREF_NOT_FOUND 0x00001198

AGENT_COMMS_ADDRESS_NOT_SET 0x0000119C

REQUEST_NOT_LOCKED 0x000011A0

DEPENDENCY_NOT_FOUND 0x000011A4

INVALID_STATE_MODEL 0x000011A8


Appendix D. Automation Manager Reason Codes 577



Appendix E. Sysplex Communication Services Returnand Reason Codes

Table 17 on page 579 and Table 18 on page 581 list the return and reason codes associated withSysplex Communications Services internal APIs. These are displayed in messages INGY1000I andAOF350E.

INGY1000I INGPXxxx FAILED IN MODULE modname, RC=x'nnnn', REASON=x'nnnn'

Where RC=return code and REASON=function code from Table 17 on page 579 (depending on the failingINGPXxxx module).

Note: AOF355E will be issued with RC=40 (invalid call to routine) if any of the following functions arecalled with invalid parameters.

Table 17. Sysplex Communication Manager API Function Codes

Return Code Function Code Explanation

Module INGPXRPC

0 X'00' 0 OK, command and data accepted and queued. A handle is returned if the targetparameter was specified.

0 X'18' 24 Target name is not active or not in the member table. The member table is maintainedby the Sysplex Communication Manager and can be displayed via the REXX programINGRXQRY.

0 X'20' 32 REXX variable pool problem (IRXEXCOM error).

0 X'24' 36 Any other internal error.

0 X'28' 40 Sysplex Communication Manager Environment is not available. This may happen, forexample, if the Sysplex Communication Manager DST is not started.

0 An ABEND occurred. The function was recovered, but returned unsuccessfully.

0 X'34' 52 Invalid request type was specified.

0 X'38' 56 The is no Primary Automation Manager (PAM) active.

Module INGPXRCV


0 X'00' 0 Successful completion. For a complete receive request all output was completelyreceived and placed into stem data. Data.0 specifies the number of stem elements. Ifthe response was an empty stem data.0 contains 0. For a partial receive request therequested number or less than the requested number of command output recordswere received and placed into stem data. Data.0 will contain the number of outputrecords that were received. This might be zero.

0 X'04' 4 Successful completion, but more data is available. (Applicable only to a partialreceive).

0 X'08' 8 Data is not yet completely received. (Applicable only to a complete receive).

0 X'0C' 12 Invalid handle. Handle is currently in use or has been deleted or is being deleted.

0 X'10' 16 Processing of the RPC request failed. The Communication Manager detected an errorwhile processing the pipe identified by the handle. This error took place either on thelocal system or on the remote system. The Communication Manager issued messageAOF350E to explain the error in more detail (see Table 18 on page 581).





Table 17. Sysplex Communication Manager API Function Codes (continued)


0 X'2C' 44 An ABEND occurred. The function was recovered, but returned unsuccessfully.

0 X'30' 48 The third parameter (number of records) was specified as zero.

Module INGPXSND


0 X'00' 0 Successful completion. All command output has been accepted and queued to besent to the RPC originator.


0 X'10' 16 Processing of the RPC request failed. The Communication Manager detected an errorwhile processing the pipe identified by the handle. This error took place either on thelocal system or on the remote system. The Communication Manager issued messageAOF350E to explain the error in more detail (see Table 18 on page 581).





Module INGPXDEL


0 X'00' 0 Successful completion. Handle has been deleted.


0 X'10' 16 Processing of the RPC request failed. The Communication Manager detected an errorwhile processing the pipe identified by the handle. his error took place either on thelocal system or on the remote system. The Communication Manager issued messageAOF350E to explain the error in more detail (see Table 18 on page 581).




0 X'2C' 44 An ABEND occurred. The function was recovered, but returned unsuccessfully

Module INGPXWAT


0 X'00' 0 Successful completion. Wait time has expired.

0 nn STIMER error code.

Module INGPXMEM


0 X'00' 0 Successful completion.





0 X'34' 52 Invalid function specified.

Module INGPXUTI



Table 17. Sysplex Communication Manager API Function Codes (continued)



0 X'1C' 28 Invalid request specified as the first parameter.




Module INGPXQRY



0 X'190' 400 Any REXX signal on failure. first parameter.

0 X'194' 404 Receiving the command failed.

0 X'198' 408 Receiving the input data for the command failed.

0 X'19C' 412 Sending the command response back to the originating RPC failed.

0 X'1A0' 416 NetView PIPE failed.

Module INGPXCAM The command handler INGPXCAM issues message AOF356 with RC=nn if any of the following errors aredetected.


4 Error, invalid RPC type.

8 Error, REXX function failed.

12 Error, NetView PIPE failed.

16 Error, buffer.0 is wrong.

AOF350E SYSPLEX COMMUNICATION ERROR: SYSTEM=sysname ERRTYPE=nn ERRCODE=nnDIAG='INGPXxxx '

Where ERRTYPE=function code from Table 17 on page 579 (depending on the failing DIAG=INGPXxxxmodule) and ERRCODE=error code from Table 18 on page 581.

Table 18. Error Codes from Message AOF350E.

Error Codes from Message AOF350E

Error Code Description

1 Read detects queue is empty.

4 TOD damaged.

8 CommEnv block is invalid.

12 Cannot add buffer to outbound queue.

16 Cannot create new package buffer.

20 Cannot pack data into package buffer.

24 Cannot unpack package buffer.

28 More buffer expected but not available.

32 Cannot initialize package buffer (read).

36 Cannot release package buffer (read).

40 Dequeue outBndQ failed.

Appendix E. Sysplex Communication Services Return and Reason Codes 581

Table 18. Error Codes from Message AOF350E.

Error Codes from Message AOF350E

(continued)

Error Code Description

44 Cannot initialize package buffer (outbnd).

48 Cannot release package buffer (outbnd).

52 Cannot write buffer to outbound queue.

56 Cannot add message to inbound queue.

60 Cannot send message.

64 Cannot free pipe into buffer pool.

68 Cannot make buffer from pipe object.

72 Cannot initialize package buffer (close).

76 Remote pipe is damaged.

80 Delete pipe failed.

84 Terminate (DST) was requested.

88 SynchOutbound.

92 SynchOutbound add to queue.

96 SynchOutbound null buffer.

100 SynchOutbound get buffer.

104 SynchOutbound add inbound queue.

108 SynchOutbound reuse buffer.

112 SynchOutbound pipe not synch.

116 Outbound fails with retry (outbound).

120 Outbound retry limit exceeded (outbound).

124 Remote pipe signals error.

128 Remote pipe leave XCF group.

136 Unlock from pipelist error.

144 Inbound queue is out of synch.

148 Pipe cannot be removed.

152 Dequeue outbound failed.

156 Cannot initialize package buffer (copy).

160 Cannot release package buffer (copy).

164 Outbound fails with retry (copy).

168 Outbound retry limit exceeded (copy).

172 Cannot send (copy).

176 Cannot add FIFO into PPI list.


Appendix F. End-to-End Automation AdapterMessages

The following messages are issued by the end-to-end automation adapter.

Note that within NetView an additional * may be appended to the end of the message text.

EEZA0001E Syntax error on line line number

ExplanationA syntax error has occurred in the configuration file, forexample, a leading = on a line.

System actionThe automation adapter stops.

Operator responseAnalyze the configuration file for invalid syntax.

EEZA0002E Wrong datatype in key the key.Expected the desired type, foundvalue "the value that was found"

ExplanationThe value of the given key cannot be interpreted as thedesired type. For example, the system expected aboolean value but found the string "hello".


Operator responseAnalyze the configuration file for invalid key/valuepairs.

EEZA0003E The key "the key that was notfound" was not found and nodefault value was given

ExplanationThe system wanted to retrieve from the configurationfile a value that did not exist and no default value wasgiven.


Operator responseSupply a value for the key in the configuration file.

EEZA0004E Integer out of bounds in key "thekey". Expected value between thelower bound expected and theupper bound expected, found thevalue parsed

ExplanationThe system expected an integer value between thegiven bounds (inclusive) for the given key, but found avalue outside these bounds.


Operator responseSupply a value within the given bounds for the key.

EEZA0005I At least one system symbol cannotbe resolved: text-line

Explanation:The text line in error contains the system symbol thatcannot be resolved. A system symbol is consideredunresolved if it is either not defined or empty.

System action:The automation adapter stops.

Operator response:If available, refer to message EEZA0031E thatspecifies the name of the configuration file in error.Check the text line in error for an invalid systemsymbol. The system symbol in the corresponding z/OSIEASYMxx parmlib member might not be defined. Ifyou are authorized to do so, enter the z/OS DISPLAYSYMBOLS command to display the system symbolsand associated substitution texts that are in effect,and then define the corresponding system symbol ifit's missing.

EEZA0006E Cannot create an instance of theclass because class not found:class name


ExplanationThe automation adapter cannot load the class.

System actionThe automation adapter rejects the request.

Operator responseCheck whether the class name is valid and is availablein the corresponding class path.

EEZA0007E Cannot create an instance of theclass because method not found:class name

ExplanationThe automation adapter can load the class but cannotcreate an instance.


Operator responseCheck whether the class is valid.

EEZA0008E Cannot create an instance of theclass because of an unknownerror: class name

ExplanationThe automation adapter cannot load the class orcreate an instance.


Operator responseCheck whether the class is valid and analyze theattached original exception.

EEZA0009E Invocation of adapter plug-infailed: plug-in=plug-in name,method=method name,internalRetcode=internal returncode, taskRetcode=task returncode

ExplanationThe automation adapter client API was called toexecute a task on the remote automation adapter.There are three error categories:

• The client suffers an error on the connection• The execution of the task within the automation

adapter backend failed• Execution failed in the automation adapter plug-in.

Automation adapter internal return codes:3

Backend detects that the request expired before itwas started.

4Backend cannot be loaded.

22Backend cannot load the plug-in Java class.

23An exception occurred in the backend or the plug-in returns a non-zero task return code.

24Backend rejects the execution of the task. See theautomation adapter trace for details.

30Backend detects invalid input arguments. Cannotexecute task. This is an internal error.

40Authentication failed. The user ID or password hasnot been specified or an internal error occurred.

41Authentication failed. The user ID or password isinvalid on the automation adapter host.

42Authentication failed. The user ID has beenrevoked. JAAS login modules may not provide thisinformation or may also use it if the password hasexpired.

43Authentication failed. The password has expired.JAAS login modules may not provide thisinformation.

The automation adapter client connection internalreturn codes:101

Connection timed out while open.102

Connection failed during open/read/write becausepeer closed.

103Not all data received. The data was readsuccessfully but the number of bytes is too small.This might be an internal error.

104Unable to connect to the automation adapter.


105Unable to close connection. This might be aninternal error.

106Unable to send data. Connection has been aborteddue to, for example, SSL mismatch or theautomation adapter stopped.

107Marshal error occurred while sending or receivingdata. This is an internal error.

108Connection is invalid, for example, connection hasnot been opened or previously failed.

109Read response failed. Data is zero, for example,the connection has been aborted due to an SSLmismatch.

110Connection timed out during read/write.

Predefined task return codes from plug-in:<0

Internally used task return codes have beenmapped to one of the automation adapter returncodes.

0The plug-in was successful.

4004The plug-in connection timed out.

4008The plug-in authorization is missing to execute therequest.

4009The plug-in authentication failed.

4012The plug-in failed but might execute the nextrequest successfully. This is the default returncode if the plug-in throws an exception but theplug-in return code is zero.

4016The plug-in failed and might not execute the nextrequest successfully.

4020The plug-in failed and forces the entire automationadapter to stop.

4024The plug-in cannot find the policy. For example,this may occur if the policy should be activated.

4028The plug-in has found an error in the automationpolicy. For example, a policy rule was violated.

System actionExecution of the remote task fails.

Operator responseAnalyze the return code description. If it is an internalerror, check IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/

EEZA0010E Request expired before theadapter passes it to the adapterplug-in. Timeout period is timeoutvalue seconds

ExplanationAll requests have an associated expiration date. Therequest is scheduled to an execution thread thatdetected that the expiration time had expired.


Operator responseAnalyze the reason (for example, high working load).Increase the timeout period if necessary.

EEZA0011E The backend programspecification is invalid

ExplanationThe backend program is not a Java program or theJava program name was not specified.


Operator responseCheck the program that called the automation adapterclient API.

EEZA0012E Invalid parameter list

ExplanationThe automation adapter detected a request that isassociated with an invalid parameter list.


Appendix F. End-to-End Automation Adapter Messages 585

Operator responseCheck the program that called the automation adapterclient API.

EEZA0013E Authentication for user ID username was unsuccessful

ExplanationThe request is associated with a user ID and passwordthat have been validated unsuccessfully.


Operator responseCheck whether the user ID is authorized for the systemand check the security policy. Also check if you havestored a user ID and password for this domain in thecredential store of the Dashboard Application ServicesHub.

EEZA0014E The original exception original-class needs to be transported tothe remote caller

ExplanationAn exception from an underlying component needs tobe transported to the remote caller.

System actionNone.

Operator responseAnalyze the original exception attached with thismessage.

EEZA0015E Method not supported: name of themissing method

ExplanationThe automation adapter detected an unknown methodname. The list of all valid method names is defined inthe EEZAdapterInteraction interface.


Operator responseCheck IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/

EEZA0017E Request not supported: name ofthe unsupported request

ExplanationThe automation adapter plug-in does not support thespecified request.

System actionThe request might be rejected depending on thebehavior of the plug-in.

Operator responseCheck whether the automation domain supports thistype of request. Check whether you have installed thelatest E2E adapter version.

EEZA0022E Adapter client is unable to connectto the adapter at host:port due toexception: the exception that wascaught

ExplanationThe automation adapter client cannot connect to theserver at the given host and port. The originalexception text is provided.

System actionThe connection is not established.

Operator responseAnalyze the original exception. For example, checkfirewall settings.

EEZA0023E Cache directory is invalid

ExplanationThe EIF cache directory is not a directory.


Operator responseCorrect the configuration file.


EEZA0024E EIF sender and receiver must notbe equal

ExplanationThe EIF configuration parameters are not allowed topoint to each other.


Operator responseCorrect the master configuration file. For example,compare parameter eif-receive-send-hostname witheif-receive-from-hostname and compare parameter eif-send-from-port with eif-receive-from-port.

EEZA0025E Cannot find the plug-inconfiguration file: configuration filename

ExplanationThe master configuration file contains the name of aplug-in configuration file that cannot be found.


Operator responseCorrect the configuration file. Check parameter plugin-configfile-xxx, where for example xxx stands forsa4zos.

EEZA0026E No plug-in configuration file wasspecified

ExplanationThe master configuration file must contain at least oneplug-in configuration file.


Operator responseCorrect the configuration file. Compare parameterplugin-impl-class with the IBM provided settings.

EEZA0027E Cannot load configuration file:configuration file name

ExplanationThe specified configuration file cannot be loaded.


Operator responseMake sure that the configuration file resides in yourcustomized E2E adapter configuration directory.

EEZA0028E Plug-in configuration file does notcontain all mandatory parameters:configuration file name

ExplanationThe specified configuration file does not contain allmandatory parameters. The plug-in is not used.

System actionThe automation adapter does not deploy the plug-in.

Operator responseCompare the configuration file with the IBM providedsettings.

EEZA0029E Cannot create the first instance ofthe plug-in class: class name

ExplanationAn attempt was made to create the first instance of theplug-in during initialization. Creation failed.


Operator responseCompare parameter plugin-impl-class with the IBMprovided settings.

EEZA0030E Cannot set up event subscriptionlist for plug-in configuration file:plug-in configuration file name

ExplanationThe specification of the EIF event classes in the plug-in configuration file is invalid.



Operator responseCompare parameter plugin-event-classes with the IBMprovided settings.

EEZA0031E Cannot load configuration filefrom: plug-in configuration filename

ExplanationThe automation adapter cannot load the specifiedconfiguration file because either no configuration fileor an invalid one was specified.


Operator responseCheck whether the name of the configuration file iscorrect. Compare parameter plugin-configfile-xxx withthe IBM provided settings.

EEZA0032E Initialization of the adapter failed:original exception

ExplanationAn error occurred in the initialization step of theautomation adapter.


Operator responseAnalyze the associated exception. If there is noexception text for this message, try to find additionalmessages in the adapter log.

EEZA0033E Unable to create type of factorySocketFactory

ExplanationThe automation adapter server or client cannot createa socket factory for the remote contact.

System actionThe automation adapter client cannot create aconnection or the automation adapter server cannotreceive connections.

Operator responseAnalyze the reason by using previous messages.

EEZA0036E The adapter suffered anunexpected interruption: originalexception

ExplanationThe automation adapter waits for a terminationcommand. An unexpected interruption occurred.


Operator responseAnalyze the original exception.

EEZA0037E The adapter stops because noplug-in has been successfullyinitialized

ExplanationAt least one plug-in must have been successfullyinitialized otherwise the automation adapter stops.


Operator responseAnalyze previous messages and exceptions that areissued by the failing plug-in.

EEZA0038E A (SSL) socket configuration erroroccurred: exception text

ExplanationAn error occurred during the loading or processing of(SSL) socket-related configuration data. An SSLhandshake exception will only be reported duringinitial contact.

System actionThe automation adapter client cannot create aconnection or the automation adapter server cannotreceive connections.

Operator responseAnalyze the exceptions text. Check the SSLconfiguration file, ing.adapter.ssl.properties,if necessary.

EEZA0039E Not all data was read from socket:number of bytes read bytes read,


number of bytes expected bytesexpected to be read

ExplanationThe incoming request has a length in bytes, but not allbytes can be read.


Operator responseCheck why the socket connection was broken whiletransferring data.

EEZA0040E The adapter client cannotestablish connection to theadapter: string representation ofthe connection

ExplanationOpening the connection failed. A request cannot besent to the automation adapter. The stringrepresentation of the connection contains detailsabout the connection.

System actionThe automation adapter frontend failed.

Operator responseAnalyze the connection information.

EEZA0041E The adapter client cannot invokean adapter request:InternalRC=internal return code,TaskRC=task return code

ExplanationA connection to the automation adapter has beensuccessfully established. The automation adapterfrontend might have sent a request to the automationadapter but the request failed. If the internal or taskreturn codes are not applicable (n/a), some otherunexpected exception occurred.


Operator responseAnalyze the internal and task return codes (seeEEZA0009E for an explanation of the return codes).

EEZA0042E The adapter has thrown a remoteexception: InternalRC=internalreturn code, TaskRC=task returncode. The original message was:message text

ExplanationA connection to the automation adapter has beensuccessfully established. The automation adapterfrontend has sent a request to the automation adapterbut the plug-in has thrown an exception.

System actionNone.

Operator responseAnalyze the internal and task return codes (seeEEZA0009E for an explanation of the return codes).

EEZA0043E A required command lineparameter is missing

ExplanationOne of the required command line parameters ismissing (such as -start,-stop or -terminate).


Operator responseSpecify the required command-line parameters and tryagain.

EEZA0045E The adapter cannot establish aserver socket due to illegalarguments: exception text

ExplanationThe automation adapter cannot establish a receiverthread and cannot accept incoming connections.


Operator responseAnalyze the configuration file for an invalid IP address.

EEZA0047E The adapter is unable to acceptconnections due to socketexception "exception"


ExplanationAn exception occurred as the automation adapter wasabout to accept an incoming connection.


Operator responseAnalyze the exception text.

EEZA0051W Termination of the adapter faileddue to exception: error message

ExplanationThe attempt to stop the receiver thread failed becausean exception occurred.

System actionNone.

Operator responseAnalyze the exception text.

EEZA0052E Cannot create an in-storage EIFconfiguration file: exception text

ExplanationAn instance of the Java class ByteArrayInputStreamcannot be created or written.


Operator responseThis is probably an internal error. The exception textmight give the reason for the problem.

EEZA0053E Missing argument for commandline parameter "the parameter"

ExplanationA required argument for a command line parameter(such as -start) is missing. For example,AdapterCmd -start would be incorrect because -start requires an argument. A correct example wouldbe: AdapterCmd -startcom.ibm.ing.saplugin.INGXPluginInvocation

System actionProcessing of this command ends.

Operator responseCheck the documentation for information about validcommand line arguments and their parameters.

EEZA0055E Remote Contact inactivitythreshold exceeded: elapsedseconds=elapsed secondsthreshold=threshold

ExplanationThe automation adapter calculates the elapsed timesince the last synchronous request was received. Theautomation adapter stops itself if this time exceedsthe number specified in the parameter eez-remote-contact-activity-interval-seconds. Any incoming eventis used as a trigger for the calculation.


Operator responseYou might want to increase the number of secondsspecified by the parameter eez-remote-contact-activity-interval-seconds. Setting this parameter to 0(zero) means it never expires.

EEZA0056I Initial contact was enabled andthe connection to the managementserver has been established

ExplanationThe parameter eez-initial-contact was set to true andthe automation adapter attempted to connect themanagement server. The handshake to themanagement server was successful.

System actionNone.

Operator responseNo action required.

EEZA0057E The connection to themanagement server cannot beestablished


ExplanationThe automation adapter stops attempting to connectto the management server because the timeoutinterval is over.


Operator responseYou might want to increase the number of minutesspecified by the parameter eez-initial-contact-retry-interval-minutes. Specify the value 0 (zero) in order toretry forever.

EEZA0058E The plug-in has not been deployedor not yet started: name of theJava plug-in class

ExplanationAn attempt was made to issue a request against a non-deployed plug-in or a plug-in that has not beenstarted.


Operator responseCheck the plug-in configuration file and deploy themissing plug-in class. Search for message EEZA0115I.

EEZA0059E An internal error occurred

ExplanationThe automation adapter detected an internal error.

System actionNone.

Operator responseContact your IBM Electronic Support for additionalinformation - http://www.ibm.com/support/entry/portal/

EEZA0060I The termination of the adapter isdelayed for duration of the delay inseconds seconds

ExplanationStopping the automation adapter is delayed for a shortwhile until it has sent the appropriate domain leave

events. You can configure the duration of this delaywith the eez-stop-delay-seconds parameter.

System actionThe automation adapter attempts to send domainleave events.


EEZA0061E Unable to bind a socket to addresseez-remote-contact-hostname atport eez-remote-contact-port.Reason: message of the exception

ExplanationThe automation adapter was unable to use thisaddress or port. Possible causes of the problem are:

• The port is already in use by another program.• The address could not be assigned.


Operator responseMake sure that no program is using this port (that is, anautomation adapter that is already running). If anotherprogram needs this port configure the automationadapter to use another port (with the eez-remote-contact-port parameter in the master configurationfile). Ensure that the address is valid.

EEZA0062I The start command of theautomation plug-in name of theJava plug-in class was successful

ExplanationThe selected automation plug-in was successfullystarted.

System actionThe automation adapter has started the automationplug-in.


EEZA0063I The stop command of theautomation plug-in name of theJava plug-in class was successful


ExplanationThe selected automation plug-in was successfullystopped.

System actionThe automation adapter has stopped the automationplug-in.


EEZA0064I The termination command for theadapter was successful

ExplanationThe automation adapter was successfully stopped.



EEZA0070E The host name eez-remote-contact-hostname is unknown

ExplanationThe automation adapter was unable to resolve thehost name.


Operator responseSpecify a host name in parameter eez-remote-contact-hostname.

EEZA0071E The domain name is either null orempty

ExplanationThe plug-in returned an invalid domain name since it iseither null or empty.

System actionThe plug-in cannot be started.

Operator responseSpecify a domain name in the plug-in configurationfile. Use parameter plugin-domain-name or commentit out and use the default.

EEZA0100I The adapter has been started

ExplanationThis is the first of a sequence of three messages untilthe automation adapter is ready. The automationadapter starts initialization and will try to connect tothe management server if eez-initial-contact=true.

System actionNone.


EEZA0101I The adapter is active

ExplanationThe automation adapter becomes active after aconnection has been successfully established to themanagement server. The automation adaptercontinues initialization, finds and starts up all plug-ins.

System actionNone.


EEZA0102I The adapter is ready

ExplanationThe automation adapter startup sequence is complete.

System actionNone.


EEZA0103I The adapter is stopping

ExplanationAn internal or an external stop command has beenreceived.


System actionThe automation adapter is about to stop.


EEZA0104I The adapter has been stopped

ExplanationThe automation adapter termination is complete. Allpossible stop delay periods are over. The processstops immediately.

System actionThe automation adapter has stopped.


EEZA0105I The adapter has been stopped dueto a failure, rc=return code

ExplanationThe automation adapter stopped because an erroroccurred. All possible stop delay periods are over. Theprocess stops immediately. The return code might be:12

if initial contact failed13

if the remote contact activity threshold is exceeded16

if a plug-in forced termination of the automationadapter

20if initialization failed

24if an error occurred after initialization wassuccessful

28if an unsupported environment is detected


Operator responseSearch for error messages that were issued previously.On z/OS return code 28 might be caused by the 64-bitJVM. You should use the 32-bit JVM instead.

EEZA0111I The plug-in is starting: name of theJava plug-in class

ExplanationThe automation adapter has already successfullycreated an instance of the plug-in class and will nowcall function INIT_DOMAIN.

System actionNone.


EEZA0112I The plug-in has been started:name of the Java plug-in class

ExplanationThe automation adapter plug-in has successfullyinitialized the domain (INIT_DOMAIN).

System actionNone.


EEZA0113I The plug-in is stopping: name ofthe Java plug-in class

ExplanationThe automation adapter will call plug-in functionTERM_DOMAIN.

System actionNone.


EEZA0114I The plug-in has been stopped:name of the Java plug-in class

ExplanationThe automation adapter plug-in has successfullystopped the domain (TERM_DOMAIN).


System actionNone.


EEZA0115I The plug-in startup failed: name ofthe Java plug-in class

ExplanationThis message might follow after EEZA0111I, but theattempt to start the plug-in via function INIT_DOMAINfailed. The automation adapter plug-in will not bestarted automatically.

System actionThe plug-in will be disabled. A join event was not sent.

Operator responseYou might want to restart the plug-in using theautomation adapter start command. Analyze furtherplug-in messages.

EEZA0116I The status of the event senderchanged: Address=Address,Port=Port, Status=Status

ExplanationThis message occurs if the status of the EIFconnection changed. The reason could be that a newEIF connection is created or an existing EIF connectionis lost. The reason can be found in the status. Astatus='connection timed out' is expected if themanagement server is stopped, for example if themanagement server moves to another system andtherefore the adapter needs to change the EIF senderdestination. The status can be:1

connection created2

connection changed4

connection closed8

connection timed out

System actionNone.


EEZA9991E The message file is not installed

ExplanationThe English message file must be available.


Operator responseMake sure that the message file is in the class path

EEZA9992E EEZAdapterLogger is not available

ExplanationThe automation adapter logging component has notbeen initialized.

System actionThe automation adapter stops. Other processes usingthe automation adapter client API will be unable towrite messages to log and trace files.

Operator responseCheck IBM Electronic Support for additional support -http://www.ibm.com/support/entry/portal/

EEZC0001I Setting up Tivoli CommonDirectory at location where TivoliCommon Directory is being set up.

ExplanationThe Tivoli Common Directory path was set to itsdefault value, as shown in the message text.

System actionNo system action required.

Operator responseNo operator action required.

EEZC0002I Unable to determine TivoliCommon Directory. Divertingserviceability related output toalternative location.


ExplanationThe system was not able to determine the TivoliCommon Directory.

System actionProcessing continues. The application will attempt todivert serviceability related output to another locationfor this session.

Operator responseIn order to manage its serviceability related output,the application should be granted read/writepermission to the location /etc/ibm/tivoli/common(UNIX) or <Program_Files_Dir>\ibm\tivoli\common(Windows).

EEZC0003I Base output directory forserviceability related files (forexample, message log files andtrace files) has been set to newoutput directory.

ExplanationThe output directory for serviceability related files wasset to its default value, as shown in the message text.

System actionFrom now on the application will write serviceabilityrelated information to the directory that is contained inthe message text.

Operator responseNo action is required if the base output directory forserviceability related files is acceptable. Otherwise, ifit is required to relocate the base output directory,modify the entry in log.properties, which should belocated at <Program_Files_dir>\ibm\tivoli\common\cfg (Windows) or /etc/ibm/tivoli/common/cfg/log.properties (UNIX). Changes to this file will takeeffect once the corresponding component is restarted.

EEZC0004I Changing base output directory forserviceability related files of nameof logger from old output directoryto new output directory.

ExplanationDue to changes in configuration settings the outputdirectory of serviceability related files has beenrelocated.

System actionFrom now on the system will write serviceabilityrelated information to the new location.

Operator responseNo action is required if the base output directory forserviceability related files is acceptable. Otherwise, ifit is required to relocate the base output directory,modify the entry in log.properties, which should belocated at <Program_Files_dir>\ibm\tivoli\common\cfg (Windows) or /etc/ibm/tivoli/common/cfg/log.properties (UNIX). Changes to this file will takeeffect once the corresponding component is restarted.

EEZK0003E String someString is too long: themaximum length ofnameOfTheString Strings ismaxLength.

ExplanationSetting the String to the specified value did notsucceed due to string length.

System actionThe current task ends.

Operator responseVerify the input parameters. If the problem persists,supply the trace file and this message text to your IBMSupport Center.

EEZK0004E String named someStringNamemust not be null and must notexceed the maximum length ofmaxLength.

ExplanationSetting the String to null is not allowed.

System actionThe current task ends.

Operator responseVerify the input parameters. If the problem persists,supply the trace file and this message text to your IBMSupport Center.

EEZK0005E An exception, which is not aninstance ofEEZApplicationException has beenpassed to the


EEZApplicationTransientException. The type of the message isexceptionType. The exceptionmessage is: exceptionMessage.

ExplanationThis is an unexpected behavior.

System actionThe current task will continue. The exception will beprocessed.

Operator responseProvide the logs and traces for more details, if anyother error occurs.


Appendix G. Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

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 inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

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 APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade 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 thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US


Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

The performance data and client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

ApplicabilityThese terms and conditions are in addition to any terms of use for the IBM website.


http://www.ibm.com/legal/us/en/copytrade.shtml

Personal useYou may reproduce these publications for your personal, noncommercial use provided that all proprietarynotices are preserved. You may not distribute, display or make derivative work of these publications, orany portion thereof, without the express consent of IBM.

Commercial useYou may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

RightsExcept as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS AREPROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,AND FITNESS FOR A PARTICULAR PURPOSE.

Appendix G. Notices 599


Glossary

This glossary includes terms and definitions from:

• The IBM Dictionary of Computing New York: McGraw-Hill, 1994.• The American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright

1990 by the American National Standards Institute (ANSI). Copies can be purchased from the AmericanNational Standards Institute, 1430 Broadway, New York, New York 10018. Definitions are identified bythe symbol (A) after the definition.

• The Information Technology Vocabulary developed by Subcommittee 1, Joint Technical Committee 1, ofthe International Organization for Standardization and the International Electrotechnical Commission(ISO/IEC JTC1/SC1). Definitions of published parts of this vocabulary are identified by the symbol (I)after the definition; definitions taken from draft international standards, committee drafts, and workingpapers being developed by ISO/IEC JTC1/SC1 are identified by the symbol (T) after the definition,indicating that final agreement has not yet been reached among the participating National Bodies ofSC1.

The following cross-references are used in this glossary:

Contrast with. This refers to a term that has an opposed or substantively different meaning.Deprecated term for. This indicates that the term should not be used. It refers to a preferred term,which is defined in its proper place in the glossary.See. This refers the reader to multiple-word terms in which this term appears.See also. This refers the reader to terms that have a related, but not synonymous, meaning.Synonym for. This indicates that the term has the same meaning as a preferred term, which is definedin the glossary.Synonymous with. This is a backward reference from a defined term to all other terms that have thesame meaning.

AACF

See automation configuration file.ACF/NCP

Advanced Communications Function for the Network Control Program. See AdvancedCommunications Function and Network Control Program.

ACF/VTAMAdvanced Communications Function for the Virtual Telecommunications Access Method. Synonym forVTAM. See Advanced Communications Function and Virtual Telecommunications Access Method.

active monitoringIn SA z/OSautomation control file, the acquiring of resource status information by soliciting suchinformation at regular, user-defined intervals. See also passive monitoring.

adapterHardware card that enables a device, such as a workstation, to communicate with another device,such as a monitor, a printer, or some other I/O device.

adjacent hostsSystems connected in a peer relationship using adjacent NetView sessions for purposes of monitoringand control.

adjacent NetViewIn SA z/OS, the system defined as the communication path between two SA z/OS systems that do nothave a direct link. An adjacent NetView is used for message forwarding and as a communication linkbetween two SA z/OS systems. For example, the adjacent NetView is used when sending responsesfrom a focal point to a remote system.


Advanced Communications Function (ACF)A group of IBM licensed programs (principally VTAM, TCAM, NCP, and SSP) that use the concepts ofSystems Network Architecture (SNA), including distribution of function and resource sharing.

advanced program-to-program communication (APPC)A set of inter-program communication services that support cooperative transaction processing in aSystems Network Architecture (SNA) network. APPC is the implementation, on a given system, ofSNA's logical unit type 6.2.

Advanced Workload Analysis Reporter (zAware)IBM analytics appliance running in a z Systems® partition, activated in zACI mode. Customers can usethe appliance to monitor the console message streams of other LPARs running in the same IBM Zcluster and create trend reports. Exploiting zAware and these trend reports can help to better predictOS outages or performance degradations and initiate proactive clusters.

alertIn SNA, a record sent to a system problem management focal point or to a collection point tocommunicate the existence of an alert condition.In NetView, a high-priority event that warrants immediate attention. A database record is generatedfor certain event types that are defined by user-constructed filters.

alert conditionA problem or impending problem for which some or all of the process of problem determination,diagnosis, and resolution is expected to require action at a control point.

alert thresholdAn application or volume service value that determines the level at which SA z/OS changes theassociated icon in the graphical interface to the alert color. SA z/OS may also issue an alert. Seewarning threshold.

AMCSee Automation Manager Configuration.

American Standard Code for Information Interchange (ASCII)A standard code used for information exchange among data processing systems, data communicationsystems, and associated equipment. ASCII uses a coded character set consisting of 7-bit codedcharacters (8-bit including parity check). The ASCII set consists of control characters and graphiccharacters. See also Extended Binary Coded Decimal Interchange Code.

APFSee authorized program facility.

APISee application programming interface.

APPCSee advanced program-to-program communication.

applicationIn SA z/OS, applications refer to z/OS subsystems, started tasks, or jobs that are automated andmonitored by SA z/OS. On SNMP-capable processors, application can be used to refer to a subsystemor process.

Application entryA construct, created with the customization dialogs, used to represent and contain policy for anapplication.

application groupA named set of applications. An application group is part of an SA z/OS enterprise definition and isused for monitoring purposes.

application programA program written for or by a user that applies to the user's work, such as a program that doesinventory or payroll.A program used to connect and communicate with stations in a network, enabling users to performapplication-oriented activities.


application programming interface (API)An interface that allows an application program that is written in a high-level language to use specificdata or functions of the operating system or another program.

ApplicationGroup entryA construct, created with the customization dialogs, used to represent and contain policy for anapplication group.

ARMSee automatic restart management.

ASCBAddress space control block.

ASCB statusAn application status derived by SA z/OS running a routine (the ASCB checker) that searches the z/OSaddress space control blocks (ASCBs) for address spaces with a particular job name. The job nameused by the ASCB checker is the job name defined in the customization dialog for the application.

ASCIISee American Standard Code for Information Interchange.

ASFSee automation status file.

authorized program facility (APF)A facility that permits identification of programs that are authorized to use restricted functions.

automated console operations (ACO)The use of an automated procedure to replace or simplify the action that an operator takes from aconsole in response to system or network events.

automated functionSA z/OS automated functions are automation operators, NetView autotasks that are assigned toperform specific automation functions. However, SA z/OS defines its own synonyms, or automatedfunction names, for the NetView autotasks, and these function names are referred to in the samplepolicy databases provided by SA z/OS. For example, the automation operator AUTBASE correspondsto the SA z/OS automated function BASEOPER.

automatic restart management (ARM)A z/OS recovery function that improves the availability of specified subsystems and applications byautomatically restarting them under certain circumstances. Automatic restart management is afunction of the Cross-System Coupling Facility (XCF) component of z/OS.

automatic restart management element nameIn MVS 5.2 or later, z/OS automatic restart management requires the specification of a unique sixteencharacter name for each address space that registers with it. All automatic restart management policyis defined in terms of the element name, including the SA z/OS interface with it.

automationThe automatic initiation of actions in response to detected conditions or events. SA z/OS providesautomation for z/OS applications, z/OS components, and remote systems that run z/OS. SA z/OS alsoprovides tools that can be used to develop additional automation.

automation agentIn SA z/OS, the automation function is split up between the automation manager and the automationagents. The observing, reacting and doing parts are located within the NetView address space, andare known as the automation agents. The automation agents are responsible for:

• Recovery processing• Message processing• Active monitoring: they propagate status changes to the automation manager

automation configuration fileThe SA z/OS customization dialogs must be used to build the automation configuration file. It consistsof:

Glossary 603

• The automation manager configuration file (AMC)• The NetView automation table (AT)• The NetView message revision table (MRT)• The MPFLSTxx member

automation control file (ACF)In SA z/OS, a file that contains system-level automation policy information. There is one masterautomation control file for each NetView system that SA z/OS is installed on. Additional policyinformation and all resource status information is contained in the policy database (PDB). The SA z/OScustomization dialogs must be used to build the automation control files. They must not be editedmanually.

automation flagsIn SA z/OS, the automation policy settings that determine the operator functions that are automatedfor a resource and the times during which automation is active. When SA z/OS is running, automationis controlled by automation flag policy settings and override settings (if any) entered by the operator.Automation flags are set using the customization dialogs.

automation managerIn SA z/OS, the automation function is split up between the automation manager and the automationagents. The coordination, decision making and controlling functions are processed by each sysplex'sautomation manager.

The automation manager contains a model of all of the automated resources within the sysplex. Theautomation agents feed the automation manager with status information and perform the actions thatthe automation manager tells them to.

The automation manager provides sysplex-wide automation.

Automation Manager ConfigurationThe Automation Manager Configuration file (AMC) contains an image of the automated systems in asysplex or of a standalone system. See also automation configuration file.

Automation NetViewIn SA z/OS the NetView that performs routine operator tasks with command procedures or uses otherways of automating system and network management, issuing automatic responses to messages andmanagement services units.

automation operatorNetView automation operators are NetView autotasks that are assigned to perform specificautomation functions. See also automated function. NetView automation operators may receivemessages and process automation procedures. There are no logged-on users associated withautomation operators. Each automation operator is an operating system task and runs concurrentlywith other NetView tasks. An automation operator could be set up to handle JES2 messages thatschedule automation procedures, and an automation statement could route such messages to theautomation operator. Similar to operator station task. SA z/OS message monitor tasks and targetcontrol tasks are automation operators.

automation policyThe policy information governing automation for individual systems. This includes automation forapplications, z/OS subsystems, z/OS data sets, and z/OS components.

automation policy settingsThe automation policy information contained in the automation control file. This information isentered using the customization dialogs. You can display or modify these settings using thecustomization dialogs.

automation procedureA sequence of commands, packaged as a NetView command list or a command processor written in ahigh-level language. An automation procedure performs automation functions and runs underNetView.


automation routinesIn SA z/OS, a set of self-contained automation routines that can be called from the NetViewautomation table, or from user-written automation procedures.

automation status file (ASF)In SA z/OS, a file containing status information for each automated subsystem, component or dataset. This information is used by SA z/OS automation when taking action or when determining whataction to take. In Release 2 and above of AOC/MVS, status information is also maintained in theoperational information base.

automation table (AT)See NetView automation table.

autotaskA NetView automation task that receives messages and processes automation procedures. There areno logged-on users associated with autotasks. Each autotask is an operating system task and runsconcurrently with other NetView tasks. An autotask could be set up to handle JES2 messages thatschedule automation procedures, and an automation statement could route such messages to theautotasks. Similar to operator station task. SA z/OS message monitor tasks and target control tasksare autotasks. Also called automation operator.

availableIn VTAM programs, pertaining to a logical unit that is active, connected, enabled, and not at its sessionlimit.

BBase Control Program (BCP)

A program that provides essential services for the MVS and z/OS operating systems. The programincludes functions that manage system resources. These functions include input/output, dispatchunits of work, and the z/OS UNIX System Services kernel. See also Multiple Virtual Storage and z/OS.

basic modeA central processor mode that does not use logical partitioning. Contrast with logically partitionedmode.

BCPSee Base Control Program.

BCP Internal InterfaceProcessor function of IBM Z processor families. It allows for communication between basic controlprograms such as z/OS and the processor support element in order to exchange information or toperform processor control functions. Programs using this function can perform hardware operationssuch as ACTIVATE or SYSTEM RESET.

beaconingThe repeated transmission of a frame or messages (beacon) by a console or workstation upondetection of a line break or outage.

BookManager®An IBM product that lets users view softcopy documents on their workstations.

Ccentral processor (CP)

The part of the computer that contains the sequencing and processing facilities for instructionexecution, initial program load (IPL), and other machine operations.

central processor complex (CPC)A physical collection of hardware that consists of central storage, (one or more) central processors,(one or more) timers, and (one or more) channels.

central siteIn a distributed data processing network, the central site is usually defined as the focal point foralerts, application design, and remote system management tasks such as problem management.

channelA path along which signals can be sent; for example, data channel, output channel. See also link.

Glossary 605

channel path identifierA system-unique value assigned to each channel path.

channel-attachedAttached directly by I/O channels to a host processor (for example, a channel-attached device).Attached to a controlling unit by cables, rather than by telecommunication lines. Contrast with link-attached. Synonymous with local.

CHPIDIn SA z/OS, channel path ID; the address of a channel.

CHPID portA label that describes the system name, logical partitions, and channel paths.

CISee console integration.

CICS/VSCustomer Information Control System for Virtual Storage. See Customer Information Control System.

CLISTSee command list.

cloneA set of definitions for application instances that are derived from a basic application definition bysubstituting a number of different system-specific values into the basic definition.

clone IDA generic means of handling system-specific values such as the MVS SYSCLONE or the VTAM subareanumber. Clone IDs can be substituted into application definitions and commands to customize a basicapplication definition for the system that it is to be instantiated on.

commandA request for the performance of an operation or the execution of a particular program.

command facilityThe component of NetView that is a base for command processors that can monitor, control,automate, and improve the operation of a network. The successor to NCCF.

command list (CLIST)A list of commands and statements, written in the NetView command list language or the REXXlanguage, designed to perform a specific function for the user. In its simplest form, a command list is alist of commands. More complex command lists incorporate variable substitution and conditionallogic, making the command list more like a conventional program. Command lists are typicallyinterpreted rather than being compiled.In SA z/OS, REXX command lists that can be used for automation procedures.

command procedureIn NetView, either a command list or a command processor.

command processorA module designed to perform a specific function. Command processors, which can be written inassembler or a high-level language (HLL), are issued as commands.

Command Tree/2An OS/2-based program that helps you build commands on an OS/2 window, then routes thecommands to the destination you specify (such as a 3270 session, a file, a command line, or anapplication program). It provides the capability for operators to build commands and route them to aspecified destination.

common commandsThe SA z/OS subset of the CPC operations management commands.

Common User Access (CUA) architectureGuidelines for the dialog between a human and a workstation or terminal.


communication controllerA type of communication control unit whose operations are controlled by one or more programsstored and executed in the unit or by a program executed in a processor to which the controller isconnected. It manages the details of line control and the routing of data through a network.

communication lineDeprecated term for telecommunication line.

connectivity viewIn SA z/OS, a display that uses graphic images for I/O devices and lines to show how they areconnected.

console automationThe process of having NetView facilities provide the console input usually handled by the operator.

console connectionIn SA z/OS, the 3270 or ASCII (serial) connection between a PS/2 computer and a target system.Through this connection, the workstation appears (to the target system) to be a console.

console integration (CI)A hardware facility that if supported by an operating system, allows operating system messages to betransferred through an internal hardware interface for display on a system console. Conversely, itallows operating system commands entered at a system console to be transferred through an internalhardware interface to the operating system for processing.

consolesWorkstations and 3270-type devices that manage your enterprise.

couple data setA data set that is created through the XCF couple data set format utility and, depending on itsdesignated type, is shared by some or all of the z/OS systems in a sysplex. See also sysplex coupledata setand XCF couple data set.

coupling facilityThe hardware element that provides high-speed caching, list processing, and locking functions in asysplex.

CPSee central processor.

CPCSee central processor complex.

CPC operations management commandsA set of commands and responses for controlling the operation of System/390 CPCs.

CPC subsetAll or part of a CPC. It contains the minimum resource to support a single control program.

CPUCentral processing unit. Deprecated term for processor.

cross-system coupling facility (XCF)A component of z/OS that provides functions to support cooperation between authorized programsrunning within a sysplex.

Customer Information Control System (CICS)A general-purpose transactional program that controls online communication between terminal usersand a database for a large number of end users on a real-time basis.

customization dialogsThe customization dialogs are an ISPF application. They are used to customize the enterprise policy,like, for example, the enterprise resources and the relationships between resources, or theautomation policy for systems in the enterprise. How to use these dialogs is described in IBM ZSystem Automation Customizing and Programming.

DDataPower® X150z

See IBM Websphere DataPower Integration Appliance X150 for zEnterprise® (DataPower X150z).

Glossary 607

DASDSee direct access storage device.

data services task (DST)The NetView subtask that gathers, records, and manages data in a VSAM file or a network device thatcontains network management information.

data setThe major unit of data storage and retrieval, consisting of a collection of data in one of severalprescribed arrangements and described by control information to which the system has access.

data set membersMembers of partitioned data sets that are individually named elements of a larger file that can beretrieved by name.

DBCSSee double-byte character set.

DCCFSee disabled console communication facility.

DCFSee Document Composition Facility.

DELAY ReportAn RMF report that shows the activity of each job in the system and the hardware and softwareresources that are delaying each job.

deviceA piece of equipment. Devices can be workstations, printers, disk drives, tape units, remote systemsor communications controllers. You can see information about all devices attached to a particularswitch, and control paths and jobs to devices.

DEVR ReportAn RMF report that presents information about the activity of I/O devices that are delaying jobs.

dialogInteractive 3270 panels.

direct access storage device (DASD)A device that allows storage to be directly accessed, such as a disk drive.

disabled console communication facility (DCCF)A z/OS component that provides limited-function console communication during system recoverysituations.

disk operating system (DOS)An operating system for computer systems that use disks and diskettes for auxiliary storage ofprograms and data.Software for a personal computer that controls the processing of programs. For the IBM PersonalComputer, the full name is Personal Computer Disk Operating System (PCDOS).

displayTo present information for viewing, usually on the screen of a workstation or on a hardcopy device.Deprecated term for panel.

distribution managerThe component of the NetView program that enables the host system to use, send, and delete filesand programs in a network of computers.

Document Composition Facility (DCF)An IBM licensed program used to format input to a printer.

domainAn access method and its application programs, communication controllers, connecting lines,modems, and attached workstations.


In SNA, a system services control point (SSCP) and the physical units (PUs), logical units (LUs), links,link stations, and associated resources that the SSCP can control with activation requests anddeactivation requests.

double-byte character set (DBCS)A character set, such as Kanji, in which each character is represented by a 2-byte code.

DP enterpriseData processing enterprise.

DSIPARMThis file is a collection of members for NetView customization.

DSTData Services Task.

EEBCDIC

See Extended Binary Coded Decimal Interchange Code.ECB

See event control block.EMCS

Extended multiple console support. See also multiple console support.enterprise

The composite of all operational entities, functions, and resources that form the total businessconcern and that require an information system.

Enterprise Systems Architecture (ESA)A hardware architecture that reduces the effort required for managing data sets and extendsaddressability for system, subsystem, and application functions.

entriesResources, such as processors, entered on panels.

entry typeResources, such as processors or applications, used for automation and monitoring.

environmentData processing enterprise.

error thresholdAn automation policy setting that specifies when SA z/OS should stop trying to restart or recover anapplication, subsystem or component, or offload a data set.

ESASee Enterprise Systems Architecture.

eventIn NetView, a record indicating irregularities of operation in physical elements of a network.An occurrence of significance to a task; for example, the completion of an asynchronous operation,such as an input/output operation.Events are part of a trigger condition, such that if all events of a trigger condition have occurred, astartup or shutdown of an application is performed.

event control block (ECB)A control block used to represent the status of an event.

exception conditionAn occurrence on a system that is a deviation from normal operation. SA z/OS monitoring highlightsexception conditions and allows an SA z/OS enterprise to be managed by exception.

Extended Binary Coded Decimal Interchange Code (EBCDIC)A coded character set of 256 8-bit characters developed for the representation of textual data. Seealso American Standard Code for Information Interchange.

Glossary 609

extended recovery facility (XRF)A facility that minimizes the effect of failures in z/OS, VTAM, the host processor, or high availabilityapplications during sessions between high availability applications and designated terminals. Thisfacility provides an alternate subsystem to take over sessions from the failing subsystem.

Ffallback system

See secondary system.field

A collection of bytes within a record that are logically related and are processed as a unit.file manager commands

A set of SA z/OS commands that read data from or write data to the automation control file or theoperational information base. These commands are useful in the development of automation thatuses SA z/OS facilities.

focal pointIn NetView, the focal-point domain is the central host domain. It is the central control point for anymanagement services element containing control of the network management data.

focal point systemA system that can administer, manage, or control one or more target systems. There are a number ofdifferent focal point system associated with IBM automation products.SA z/OS Processor Operations focal point system. This is a NetView system that has SA z/OS hostcode installed. The SA z/OS Processor Operations focal point system receives messages from thesystems and operator consoles of the machines that it controls. It provides full systems andoperations console function for its target systems. It can be used to IPL these systems. Note thatsome restrictions apply to the Hardware Management Console for an S/390 microprocessor cluster.SA z/OS SDF focal point system. The SA z/OS SDF focal point system is an SA z/OS NetView systemthat collects status information from other SA z/OS NetViews within your enterprise.Status focal point system. In NetView, the system to which STATMON, VTAM and NLDM send statusinformation on network resources.Hardware Management Console. Although not listed as a focal point, the Hardware ManagementConsole acts as a focal point for the console functions of an S/390 microprocessor cluster. Unlike allthe other focal points in this definition, the Hardware Management Console runs on a LAN-connectedworkstation,

frameFor a System/390 microprocessor cluster, a frame contains one or two central processor complexes(CPCs), support elements, and AC power distribution.

full-screen modeIn NetView, a form of panel presentation that makes it possible to display the contents of an entireworkstation screen at once. Full-screen mode can be used for fill-in-the-blanks prompting. Contrastwith line mode.

Ggateway session

An NetView-NetView Task session with another system in which the SA z/OS outbound gatewayoperator logs onto the other NetView session without human operator intervention. Each end of agateway session has both an inbound and outbound gateway operator.

generic alertEncoded alert information that uses code points (defined by IBM and possibly customized by users orapplication programs) stored at an alert receiver, such as NetView.

groupA collection of target systems defined through configuration dialogs. An installation might set up agroup to refer to a physical site or an organizational or application entity.

group entryA construct, created with the customization dialogs, used to represent and contain policy for a group.


group entry typeA collection of target systems defined through the customization dialog. An installation might set up agroup to refer to a physical site or an organizational entity. Groups can, for example, be of typeSTANDARD or SYSPLEX.

HHardware Management Console (HMC)

A user interface through which data center personnel configure, control, monitor, and manage IBM Zhardware and software resources. The HMC communicates with each defined central processorcomplex (CPC) through the Support Element.

Hardware Management Console Application (HWMCA)A direct-manipulation object-oriented graphical user interface that provides a single point of controland single system image for hardware elements. The HWMCA provides grouping support, aggregatedand real-time system status using colors, consolidated hardware messages support, consolidatedoperating system messages support, consolidated service support, and hardware commands targetedat a single system, multiple systems, or a group of systems.

help panelAn online panel that tells you how to use a command or another aspect of a product.

hierarchyIn the NetView program, the resource types, display types, and data types that make up theorganization, or levels, in a network.

high-level language (HLL)A programming language that provides some level of abstraction from assembler language andindependence from a particular type of machine. For the NetView program, the high-level languagesare PL/I and C.

HLLSee high-level language.

host (primary processor)The processor that you enter a command at (also known as the issuing processor).

host systemIn a coupled system or distributed system environment, the system on which the facilities forcentralized automation run. SA z/OS publications refer to target systems or focal-point systemsinstead of hosts.

HWMCASee Hardware Management Console Application.

HypervisorA program that allows multiple instances of operating systems or virtual servers to run simultaneouslyon the same hardware device. A hypervisor can run directly on the hardware, can run within anoperating system, or can be imbedded in platform firmware. Examples of hypervisors include PR/SM,z/VM®, and PowerVM® Enterprise Edition.

IIBM Secure Service Container (SSC)

IBM Z partitions, activated to run in SSC operating mode, provide the basic infrastructure runtime anddeployment support for firmware or software based appliances, such as zAware or z/VSE® VNA.

IBM System z Application Assist Processor (zAAP)A specialized processor that provides a Java execution environment, which enables Java-based webapplications to be integrated with core z/OS business applications and backend database systems.

IBM System z Integrated Information Processor (zIIP)See Integrated Information Processor (IIP).

IBM Websphere DataPower Integration Appliance X150 for zEnterprise (DataPower X150z)A purpose-built appliance that simplifies, helps secure, and optimizes XML and Web servicesprocessing.

Glossary 611

IBM Workload Scheduler (IWS)See ZWS.

IBM Z Workload Scheduler (ZWS)The scheduler that plans, executes, and tracks jobs in z/OS environments. It's previously called IBMWorkload Scheduler for z/OS (IWS), IBM Tivoli Workload Scheduler for z/OS (TWS), or OPC/A.

IBM zEnterprise 196 (z196)The newest generation of System z family of servers built on a new processor chip, with enhancedmemory function and capacity, security, and on demand enhancements to support existing mainframeworkloads and large scale consolidation.

I/O resource numberCombination of channel path identifier (CHPID), device number, etc. See internal token.

imagesA grouping of processors and I/O devices that you define. You can define a single-image mode thatallows a multiprocessor system to function as one central processor image.

IMSSee Information Management System.

IMS/VSSee Information Management System/Virtual Storage.

inboundIn SA z/OS, messages sent to the focal-point system from the PC or target system.

inbound gateway operatorThe automation operator that receives incoming messages, commands, and responses from theoutbound gateway operator at the sending system. The inbound gateway operator handlescommunications with other systems using a gateway session.

Information Management System (IMS)Any of several system environments available with a database manager and transaction processingthat are capable of managing complex databases and terminal networks.

Information Management System/Virtual Storage (IMS/VS)A database/data communication (DB/DC) system that can manage complex databases and networks.Synonymous with Information Management System.

initial microprogram loadThe action of loading microprograms into computer storage.

initial program load (IPL)The initialization procedure that causes an operating system to commence operation.The process by which a configuration image is loaded into storage at the beginning of a workday orafter a system malfunction.The process of loading system programs and preparing a system to run jobs.

initialize automationSA z/OS-provided automation that issues the correct z/OS start command for each subsystem whenSA z/OS is initialized. The automation ensures that subsystems are started in the order specified in theautomation control files and that prerequisite applications are functional.

input/output configuration data set (IOCDS)A configuration definition built by the I/O configuration program (IOCP) and stored on disk filesassociated with the processor controller.

input/output support processor (IOSP)The hardware unit that provides I/O support functions for the primary support processor andmaintenance support functions for the processor controller.

Integrated Information Processor (IIP)A specialized processor that provides computing capacity for selected data and transactionprocessing workloads and for selected network encryption workloads.


Interactive System Productivity Facility (ISPF)An IBM licensed program that serves as a full-screen editor and dialog manager. Used for writingapplication programs, it provides a means of generating standard screen panels and interactivedialogs between the application programmer and the terminal user. See also Time Sharing Option.

interested operator listThe list of operators who are to receive messages from a specific target system.

internal tokenA logical token (LTOK); name by which the I/O resource or object is known; stored in IODF.

IOCDSSee input/output configuration data set.

IOSPSee input/output support processor..

IPLSee initial program load.

ISPFSee Interactive System Productivity Facility.

ISPF consoleYou log on to ISPF from this 3270-type console to use the runtime panels for SA z/OS customizationpanels.

issuing hostThe base program that you enter a command for processing with. See primary host.

JJCL

See job control language.JES

See job entry subsystem.JES2

An MVS subsystem that receives jobs into the system, converts them to internal format, selects themfor execution, processes their output, and purges them from the system. In an installation with morethan one processor, each JES2 processor independently controls its job input, scheduling, and outputprocessing. See also job entry subsystem and JES3

JES3An MVS subsystem that receives jobs into the system, converts them to internal format, selects themfor execution, processes their output, and purges them from the system. In complexes that haveseveral loosely coupled processing units, the JES3 program manages processors so that the globalprocessor exercises centralized control over the local processors and distributes jobs to them using acommon job queue. See also job entry subsystem and JES2.

jobA set of data that completely defines a unit of work for a computer. A job usually includes allnecessary computer programs, linkages, files, and instructions to the operating system.An address space.

job control language (JCL)A problem-oriented language designed to express statements in a job that are used to identify the jobor describe its requirements to an operating system.

job entry subsystem (JES)An IBM licensed program that receives jobs into the system and processes all output data that isproduced by jobs. In SA z/OS publications, JES refers to JES2 or JES3, unless otherwise stated. Seealso JES2 and JES3.

KKanji

An ideographic character set used in Japanese. See also double-byte character set.

Glossary 613

LLAN

See local area network.line mode

A form of screen presentation in which the information is presented a line at a time in the messagearea of the terminal screen. Contrast with full-screen mode.

linkIn SNA, the combination of the link connection and the link stations joining network nodes; forexample, a System/370 channel and its associated protocols, a serial-by-bit connection under thecontrol of synchronous data link control (SDLC). See synchronous data link control.In SA z/OS, link connection is the physical medium of transmission.

link-attachedDescribes devices that are physically connected by a telecommunication line. Contrast with channel-attached.

Linux on z SystemsUNIX-like open source operating system conceived by Linus Torvalds and developed across theinternet.

localPertaining to a device accessed directly without use of a telecommunication line. Synonymous withchannel-attached.

local area network (LAN)A network in which a set of devices is connected for communication. They can be connected to alarger network. See also token ring.A network that connects several devices in a limited area (such as a single building or campus) andthat can be connected to a larger network.

logical partition (LP)A subset of the processor hardware that is defined to support an operating system. See also logicallypartitioned mode.

logical token (LTOK)Resource number of an object in the IODF.

logical unit (LU)In SNA, a port through which an end user accesses the SNA network and the functions provided bysystem services control points (SSCPs). An LU can support at least two sessions, one with an SSCPand one with another LU, and may be capable of supporting many sessions with other LUs. See alsophysical unit and system services control point.

logical unit 6.2 (LU 6.2)A type of logical unit that supports general communications between programs in a distributedprocessing environment. LU 6.2 is characterized by:

• A peer relationship between session partners• Efficient use of a session for multiple transactions• A comprehensive end-to-end error processing• A generic application program interface (API) consisting of structured verbs that are mapped to a

product implementation

Synonym for advanced program-to-program communication.logically partitioned (LPAR) mode

A central processor mode that enables an operator to allocate system processor hardware resourcesamong several logical partitions. Contrast with basic mode.

LOGRThe sysplex logger.


LPSee logical partition.

LPARSee logically partitioned mode.

LUSee logical unit.

LU 6.2See logical unit 6.2.

LU 6.2 sessionA session initiated by VTAM on behalf of an LU 6.2 application program, or a session initiated by aremote LU in which the application program specifies that VTAM is to control the session by using theAPPCCMD macro. See logical unit 6.2.

LU-LU sessionIn SNA, a session between two logical units (LUs) in an SNA network. It provides communicationbetween two end users, or between an end user and an LU services component.

MMAT

Deprecated term for NetView automation table.MCA

See Micro Channel architecture.MCS

See multiple console support.member

A specific function (one or more modules or routines) of a multisystem application that is defined toXCF and assigned to a group by the multisystem application. A member resides on one system in thesysplex and can use XCF services to communicate (send and receive data) with other members of thesame group.

message automation table (MAT)Deprecated term for NetView automation table.

message classA number that SA z/OS associates with a message to control routing of the message. Duringautomated operations, the classes associated with each message issued by SA z/OS are compared tothe classes assigned to each notification operator. Any operator with a class matching one of themessage’s classes receives the message.

message forwardingThe SA z/OS process of sending messages generated at an SA z/OS target system to the SA z/OSfocal-point system.

message groupSeveral messages that are displayed together as a unit.

message monitor taskA task that starts and is associated with a number of communications tasks. Message monitor tasksreceive inbound messages from a communications task, determine the originating target system, androute the messages to the appropriate target control tasks.

message processing facility (MPF)A z/OS table that screens all messages sent to the z/OS console. The MPF compares these messageswith a customer-defined list of messages (based on this message list, messages are automatedand/or suppressed from z/OS console display), and marks messages to automate or suppress.Messages are then broadcast on the subsystem interface (SSI).

message suppressionThe ability to restrict the amount of message traffic displayed on the z/OS console.

Glossary 615

Micro Channel architectureThe rules that define how subsystems and adapters use the Micro Channel bus in a computer. Thearchitecture defines the services that each subsystem can or must provide.

microprocessorA processor implemented on one or a small number of chips.

migrationInstallation of a new version or release of a program to replace an earlier version or release.

MPMultiprocessor.

MPFSee message processing facility.

MPFLSTxxThe MPFLST member that is built by SA z/OS.

multi-MVS environmentphysical processing system that is capable of operating more than one MVS image. See also MVSimage.

multiple console support (MCS)A feature of MVS that permits selective message routing to multiple consoles.

Multiple Virtual Storage (MVS)An IBM operating system that accesses multiple address spaces in virtual storage. The predecessor ofz/OS.

multiprocessor (MP)A CPC that can be physically partitioned to form two operating processor complexes.

multisystem applicationAn application program that has various functions distributed across z/OS images in a multisystemenvironment.

multisystem environmentAn environment in which two or more systems reside on one or more processors. Or one or moreprocessors can communicate with programs on the other systems.

MVSSee Multiple Virtual Storage.

MVS imageA single occurrence of the MVS operating system that has the ability to process work. See also multi-MVS environment and single-MVS environment.

MVS/ESAMultiple Virtual Storage/Enterprise Systems Architecture. See z/OS.

MVS/JES2Multiple Virtual Storage/Job Entry System 2. A z/OS subsystem that receives jobs into the system,converts them to an internal format, selects them for execution, processes their output, and purgesthem from the system. In an installation with more than one processor, each JES2 processorindependently controls its job input, scheduling, and output processing.

NNAU

See network addressable unit.See network accessible unit.

NCCFSee Network Communications Control Facility..

NCPSee network control program (general term).See Network Control Program (an IBM licensed program). Its full name is Advanced CommunicationsFunction for the Network Control Program. Synonymous with ACF/NCP.


NCP/token ring interconnectionA function used by ACF/NCP to support token ring-attached SNA devices. NTRI also providestranslation from token ring-attached SNA devices (PUs) to switched (dial-up) devices.

NetViewAn IBM licensed program used to monitor a network, manage it, and diagnose network problems.NetView consists of a command facility that includes a presentation service, command processors,automation based on command lists, and a transaction processing structure on which the sessionmonitor, hardware monitor, and terminal access facility (TAF) network management applications arebuilt.

NetView (NCCF) consoleA 3270-type console for NetView commands and runtime panels for system operations and processoroperations.

NetView automation proceduresA sequence of commands, packaged as a NetView command list or a command processor written in ahigh-level language. An automation procedure performs automation functions and runs under theNetView program.

NetView automation table (AT)A table against which the NetView program compares incoming messages. A match with an entrytriggers the specified response. SA z/OS entries in the NetView automation table trigger an SA z/OSresponse to target system conditions. Formerly known as the message automation table (MAT).

NetView command list languageAn interpretive language unique to NetView that is used to write command lists.

NetView hardware monitorThe component of NetView that helps identify network problems, such as hardware, software, andmicrocode, from a central control point using interactive display techniques. Formerly called networkproblem determination application.

NetView logThe log that NetView records events relating to NetView and SA z/OS activities in.

NetView message tableSee NetView automation table.

NetView paths via logical unit (LU 6.2)A type of network-accessible port (VTAM connection) that enables end users to gain access to SNAnetwork resources and communicate with each other. LU 6.2 permits communication betweenprocessor operations and the workstation. See logical unit 6.2.

NetView-NetView task (NNT)The task that a cross-domain NetView operator session runs under. Each NetView program must havea NetView-NetView task to establish one NNT session. See also operator station task.

NetView-NetView task sessionA session between two NetView programs that runs under a NetView-NetView task. In SA z/OS,NetView-NetView task sessions are used for communication between focal point and remote systems.

networkAn interconnected group of nodes.In data processing, a user application network. See SNA network.

network accessible unit (NAU)In SNA networking, any device on the network that has a network address, including a logical unit(LU), physical unit (PU), control point (CP), or system services control point (SSCP). It is the origin orthe destination of information transmitted by the path control network. Synonymous with networkaddressable unit.

network addressable unit (NAU)Synonym for network accessible unit.

Glossary 617

Network Communications Control Facility (NCCF)The operations control facility for the network. NCCF consists of a presentation service, commandprocessors, automation based on command lists, and a transaction processing structure on which thenetwork management applications NLDM are built. NCCF is a precursor to the NetView commandfacility.

Network Control Program (NCP)An IBM licensed program that provides communication controller support for single-domain,multiple-domain, and interconnected network capability. Its full name is Advanced CommunicationsFunction for the Network Control Program.

network control program (NCP)A program that controls the operation of a communication controller.A program used for requests and responses exchanged between physical units in a network for dataflow control.

Networking NetViewIn SA z/OS the NetView that performs network management functions, such as managing theconfiguration of a network. In SA z/OS it is common to also route alerts to the Networking NetView.

NIPSee nucleus initialization program.

NNTSee NetView-NetView task.

notification messageAn SA z/OS message sent to a human notification operator to provide information about significantautomation actions. Notification messages are defined using the customization dialogs.

notification operatorA NetView console operator who is authorized to receive SA z/OS notification messages. Authorizationis made through the customization dialogs.

NTRISee NCP/token ring interconnection.

nucleus initialization program (NIP)The program that initializes the resident control program; it allows the operator to request last-minutechanges to certain options specified during system generation.

Oobjective value

An average Workflow or Using value that SA z/OS can calculate for applications from past service data.SA z/OS uses the objective value to calculate warning and alert thresholds when none are explicitlydefined.

OCAIn SA z/OS, operator console A, the active operator console for a target system. Contrast with OCB.

OCBIn SA z/OS, operator console B, the backup operator console for a target system. Contrast with OCA.

OPC/ASee Operations Planning and Control/Advanced.

OPC/ESASee Operations Planning and Control/Enterprise Systems Architecture.

operating system (OS)Software that controls the execution of programs and that may provide services such as resourceallocation, scheduling, input/output control, and data management. Although operating systems arepredominantly software, partial hardware implementations are possible. (T)

operationsThe real-time control of a hardware device or software function.


Operations Planning and Control/Advanced (OPC/A)A set of IBM licensed programs that automate, plan, and control batch workload. OPC/A analyzessystem and workload status and submits jobs accordingly.

Operations Planning and Control/Enterprise Systems Architecture (OPC/ESA)A set of IBM licensed programs that automate, plan, and control batch workload. OPC/ESA analyzessystem and workload status and submits jobs accordingly. The successor to OPC/A.

operatorA person who keeps a system running.A person or program responsible for managing activities controlled by a given piece of software suchas z/OS, the NetView program, or IMS.A person who operates a device.In a language statement, the lexical entity that indicates the action to be performed on operands.

operator consoleA functional unit containing devices that are used for communications between a computer operatorand a computer. (T)A display console used for communication between the operator and the system, used primarily tospecify information concerning application programs and to monitor system operation.In SA z/OS, a console that displays output from and sends input to the operating system (z/OS, LINUX,VM, VSE). Also called operating system console. In the SA z/OS operator commands and configurationdialogs, OC is used to designate a target system operator console.

operator station task (OST)The NetView task that establishes and maintains the online session with the network operator. Thereis one operator station task for each network operator who logs on to the NetView program.

operator viewA set of group, system, and resource definitions that are associated together for monitoring purposes.An operator view appears as a graphic display in the graphical interface showing the status of thedefined groups, systems, and resources.

OperatorView entryA construct, created with the customization dialogs, used to represent and contain policy for anoperator view.

optimizerA special-purpose hardware component or appliance that can perform a limited set of specificfunctions with optimized performance when compared to a general-purpose processor. Because of itslimited set of functions, an optimizer is an integrated part of a processing environment, rather than astand-alone unit.

OSSee operating system.

OSTSee operator station task.

outboundIn SA z/OS, messages or commands from the focal-point system to the target system.

outbound gateway operatorThe automation operator that establishes connections to other systems. The outbound gatewayoperator handles communications with other systems through a gateway session. The automationoperator sends messages, commands, and responses to the inbound gateway operator at thereceiving system.

Ppage

The portion of a panel that is shown on a display surface at one time.To transfer instructions, data, or both between real storage and external page or auxiliary storage.

Glossary 619

panelA formatted display of information that appears on a terminal screen. Panels are full-screen 3270-type displays with a monospaced font, limited color and graphics.By using SA z/OS panels you can see status, type commands on a command line using a keyboard,configure your system, and passthru to other consoles. See also help panel.In computer graphics, a display image that defines the locations and characteristics of display fieldson a display surface. Contrast with screen.

parameterA variable that is given a constant value for a specified application and that may represent anapplication, for example.An item in a menu for which the user specifies a value or for which the system provides a value whenthe menu is interpreted.Data passed to a program or procedure by a user or another program, specifically as an operand in alanguage statement, as an item in a menu, or as a shared data structure.

partitionA fixed-size division of storage.In VSE, a division of the virtual address area that is available for program processing.On an IBM Personal Computer fixed disk, one of four possible storage areas of variable size; one canbe accessed by DOS, and each of the others may be assigned to another operating system.

partitionable CPCA CPC that can be divided into 2 independent CPCs. See also physical partition, single-image mode,MP, and side.

partitioned data set (PDS)A data set in direct access storage that is divided into partitions, called members, each of which cancontain a program, part of a program, or data.

passive monitoringIn SA z/OS, the receiving of unsolicited messages from z/OS systems and their resources. Thesemessages can prompt updates to resource status displays. See also active monitoring

PCEA processor controller. Also known as the support processor or service processor in some processorfamilies.

PDBSee policy database.

PDSSee partitioned data set.

physical partitionPart of a CPC that operates as a CPC in its own right, with its own copy of the operating system.

physical unit (PU)In SNA, the component that manages and monitors the resources (such as attached links andadjacent link stations) of a node, as requested by a system services control point (SSCP) through anSSCP-PU session. An SSCP activates a session with the physical unit to indirectly manage, through thePU, resources of the node such as attached links.

physically partitioned (PP) configurationA mode of operation that allows a multiprocessor (MP) system to function as two or moreindependent CPCs having separate power, utilities, and maintenance boundaries. Contrast withsingle-image mode.

PLEXID groupPLEXID group or "extended XCF communication group" is a term used in conjunction with a sysplex.The PLEXID group includes System Automation Agents for a subset of a sysplex or for the entiresysplex. It is used to provide XCF communication beyond the SAplex boundaries. For a detaileddescription, refer to "Defining the Extended XCF Communication Group" in IBM Z System AutomationPlanning and Installation.


POISee program operator interface.

policyThe automation and monitoring specifications for an SA z/OS enterprise. See IBM Z SystemAutomation Defining Automation Policy.

policy databaseThe automation definitions (automation policy) that the automation administrator specifies using thecustomization dialog is stored in the policy database. Also known as the PDB. See also automationpolicy.

PORSee power-on reset.

portSystem hardware that the I/O devices are attached to.An access point (for example, a logical unit) for data entry or exit.A functional unit of a node that data can enter or leave a data network through.In data communication, that part of a data processor that is dedicated to a single data channel for thepurpose of receiving data from or transmitting data to one or more external, remote devices.

power-on reset (POR)A function that re-initializes all the hardware in a CPC and loads the internal code that enables theCPC to load and run an operating system. See initial microprogram load.

PPSee physical partition.

PPISee program to program interface.

PPTSee primary POI task.

PR/SMSee Processor Resource/Systems Manager.

primary hostThe base program that you enter a command for processing at.

primary POI task (PPT)The NetView subtask that processes all unsolicited messages received from the VTAM programoperator interface (POI) and delivers them to the controlling operator or to the command processor.The PPT also processes the initial command specified to execute when NetView is initialized andtimer request commands scheduled to execute under the PPT.

primary systemA system is a primary system for an application if the application is normally meant to be runningthere. SA z/OS starts the application on all the primary systems defined for it.

problem determinationThe process of determining the source of a problem; for example, a program component, machinefailure, telecommunication facilities, user or contractor-installed programs or equipment,environment failure such as a power loss, or user error.

processorA device for processing data from programmed instructions. It may be part of another unit.In a computer, the part that interprets and executes instructions. Two typical components of aprocessor are a control unit and an arithmetic logic unit.

processor controllerHardware that provides support and diagnostic functions for the central processors.

processor operationsThe part of SA z/OS that monitors and controls processor (hardware) operations. Processor operationsprovides a connection from a focal-point system to a target system. Through NetView on the focal-

Glossary 621

point system, processor operations automates operator and system consoles for monitoring andrecovering target systems. Also known as ProcOps.

Processor Resource/Systems Manager (PR/SM)The feature that allows the processor to use several operating system images simultaneously andprovides logical partitioning capability. See also logically partitioned mode.

ProcOpsSee processor operations.

ProcOps Service Machine (PSM)The PSM is a CMS user on a VM host system. It runs a CMS multitasking application that serves as"virtual hardware" for ProcOps. ProOps communicates via the PSM with the VM guest systems that aredefined as target systems within ProcOps.

product automationAutomation integrated into the base of SA z/OS for the products CICS, Db2, IMS, IBM WorkloadScheduler (formerly called features).

program operator interface (POI)A NetView facility for receiving VTAM messages.

program to program interface (PPI)A NetView function that allows user programs to send or receive data buffers from other userprograms and to send alerts to the NetView hardware monitor from system and application programs.

protocolIn SNA, the meanings of, and the sequencing rules for, requests and responses used for managing thenetwork, transferring data, and synchronizing the states of network components.

proxy resourceA resource defined like an entry type APL representing a processor operations target system.

PSMSee ProcOps Service Machine.

PUSee physical unit.

RRACF

See Resource Access Control Facility.remote system

A system that receives resource status information from an SA z/OS focal-point system. An SA z/OSremote system is defined as part of the same SA z/OS enterprise as the SA z/OS focal-point system towhich it is related.

requesterA workstation from that user can log on to a domain from, that is, to the servers belonging to thedomain, and use network resources. Users can access the shared resources and use the processingcapability of the servers, thus reducing hardware investment.

resourceAny facility of the computing system or operating system required by a job or task, and including mainstorage, input/output devices, the processing unit, data sets, and control or processing programs.In NetView, any hardware or software that provides function to the network.In SA z/OS, any z/OS application, z/OS component, job, device, or target system capable of beingmonitored or automated through SA z/OS.

Resource Access Control Facility (RACF)A program that can provide data security for all your resources. RACF protects data from accidental ordeliberate unauthorized disclosure, modification, or destruction.

resource groupA physically partitionable portion of a processor. Also known as a side.


Resource Measurement Facility (RMF)A feature of z/OS that measures selected areas of system activity and presents the data collected inthe format of printed reports, System Management Facility (SMF) records, or display reports.

restart automationAutomation provided by SA z/OS that monitors subsystems to ensure that they are running. If asubsystem fails, SA z/OS attempts to restart it according to the policy in the automation configurationfile.

Restructured Extended Executor (REXX)A general-purpose, high-level, programming language, particularly suitable for EXEC procedures orprograms for personal computing, used to write command lists.

return codeA code returned from a program used to influence the issuing of subsequent instructions.

REXXSee Restructured Extended Executor.

REXX procedureA command list written with the Restructured Extended Executor (REXX), which is an interpretivelanguage.

RMFSee Resource Measurement Facility.

SSAF

See Security Authorization Facility.SA IOM

See System Automation for Integrated Operations Management.SAplex

SAplex or "SA z/OS Subplex" is a term used in conjuction with a sysplex. In fact, a SAplex is a subsetof a sysplex. However, it can also be a sysplex. For a detailed description, refer to "Using SA z/OSSubplexes" in IBM Z System Automation Planning and Installation.

SA z/OSSee “IBM Z System Automation” on page 627.

SA z/OS customization dialogsAn ISPF application through which the SA z/OS policy administrator defines policy for individual z/OSsystems and builds automation control data.

SA z/OS customization focal point systemSee focal point system.

SA z/OS data modelThe set of objects, classes and entity relationships necessary to support the function of SA z/OS andthe NetView automation platform.

SA z/OS enterpriseThe group of systems and resources defined in the customization dialogs under one enterprise name.An SA z/OS enterprise consists of connected z/OS systems running SA z/OS.

SA z/OS focal point systemSee focal point system.

SA z/OS policyThe description of the systems and resources that make up an SA z/OS enterprise, together with theirmonitoring and automation definitions.

SA z/OS policy administratorThe member of the operations staff who is responsible for defining SA z/OS policy.

SA z/OS SDF focal point systemSee focal point system.

Glossary 623

SCAIn SA z/OS, system console A, the active system console for a target hardware. Contrast with SCB.

SCBIn SA z/OS, system console B, the backup system console for a target hardware. Contrast with SCA.

screenDeprecated term for panel.

screen handlerIn SA z/OS, software that interprets all data to and from a full-screen image of a target system. Theinterpretation depends on the format of the data on the full-screen image. Every processor andoperating system has its own format for the full-screen image. A screen handler controls one PS/2connection to a target system.

SDFSee status display facility.

SDLCSee synchronous data link control.

SDSFSee System Display and Search Facility.

secondary systemA system is a secondary system for an application if it is defined to automation on that system, but theapplication is not normally meant to be running there. Secondary systems are systems to which anapplication can be moved in the event that one or more of its primary systems are unavailable.SA z/OS does not start the application on its secondary systems.

Security Authorization Facility (SAF)An MVS interface with which programs can communicate with an external security manager, such asRACF.

serverA server is a workstation that shares resources, which include directories, printers, serial devices, andcomputing powers.

service language command (SLC)The line-oriented command language of processor controllers or service processors.

service periodService periods allow the users to schedule the availability of applications. A service period is a set oftime intervals (service windows), during which an application should be active.

service processor (SVP)The name given to a processor controller on smaller System/370 processors.

service thresholdAn SA z/OS policy setting that determines when to notify the operator of deteriorating service for aresource. See also alert threshold and warning threshold.

sessionIn SNA, a logical connection between two network addressable units (NAUs) that can be activated,tailored to provide various protocols, and deactivated, as requested. Each session is uniquelyidentified in a transmission header by a pair of network addresses identifying the origin anddestination NAUs of any transmissions exchanged during the session.

session monitorThe component of the NetView program that collects and correlates session-related data andprovides online access to this information. The successor to NLDM.

shutdown automationSA z/OS-provided automation that manages the shutdown process for subsystems by issuingshutdown commands and responding to prompts for additional information.

sideA part of a partitionable CPC that can run as a physical partition and is typically referred to as the A-side or the B-side.


Simple Network Management Protocol (SNMP)A set of protocols for monitoring systems and devices in complex networks. Information aboutmanaged devices is defined and stored in a Management Information Base (MIB).

single imageA processor system capable of being physically partitioned that has not been physically partitioned.Single-image systems can be target hardware processors.

single-MVS environmentAn environment that supports one MVS image. See also MVS image.

single-image (SI) modeA mode of operation for a multiprocessor (MP) system that allows it to function as one CPC. Bydefinition, a uniprocessor (UP) operates in single-image mode. Contrast with physically partitioned(PP) configuration.

SLCSee service language command.

SMP/ESee System Modification Program/Extended.

SNASee Systems Network Architecture.

SNA networkIn SNA, the part of a user-application network that conforms to the formats and protocols of systemsnetwork architecture. It enables reliable transfer of data among end users and provides protocols forcontrolling the resources of various network configurations. The SNA network consists of networkaddressable units (NAUs), boundary function components, and the path control network.

SNMPSee Simple Network Management Protocol.

solicited messageAn SA z/OS message that directly responds to a command. Contrast with unsolicited message.

SSCPSee system services control point.

SSISee subsystem interface.

start automationAutomation provided by SA z/OS that manages and completes the startup process for subsystems.During this process, SA z/OS replies to prompts for additional information, ensures that the startupprocess completes within specified time limits, notifies the operator of problems, if necessary, andbrings subsystems to an UP (or ready) state.

startupThe point in time that a subsystem or application is started.

statusThe measure of the condition or availability of the resource.

status display facility (SDF)The system operations part of SA z/OS that displays status of resources such as applications,gateways, and write-to-operator messages (WTORs) on dynamic color-coded panels. SDF showsspool usage problems and resource data from multiple systems.

steady state automationThe routine monitoring, both for presence and performance, of subsystems, applications, volumesand systems. Steady state automation may respond to messages, performance exceptions anddiscrepancies between its model of the system and reality.

structureA construct used by z/OS to map and manage storage on a coupling facility.

Glossary 625

subgroupA named set of systems. A subgroup is part of an SA z/OS enterprise definition and is used formonitoring purposes.

SubGroup entryA construct, created with the customization dialogs, used to represent and contain policy for asubgroup.

subplexSee SAplex.

subsystemA secondary or subordinate system, usually capable of operating independent of, or asynchronouslywith, a controlling system.In SA z/OS, an z/OS application or subsystem defined to SA z/OS.

subsystem interface (SSI)The z/OS interface over which all messages sent to the z/OS console are broadcast.

support element (SE)A hardware unit that provides communications, monitoring, and diagnostic functions to a centralprocessor complex (CPC).

support processorAnother name given to a processor controller on smaller System/370 processors. See serviceprocessor.

SVPSee service processor.

symbolic destination name (SDN)Used locally at the workstation to relate to the VTAM application name.

synchronous data link control (SDLC)A discipline for managing synchronous, code-transparent, serial-by-bit information transfer over a linkconnection. Transmission exchanges may be duplex or half-duplex over switched or nonswitchedlinks. The configuration of the link connection may be point-to-point, multipoint, or loop. SDLCconforms to subsets of the Advanced Data Communication Control Procedures (ADCCP) of theAmerican National Standards Institute and High-Level Data Link Control (HDLC) of the InternationalStandards Organization.

SYSINFO ReportAn RMF report that presents an overview of the system, its workload, and the total number of jobsusing resources or delayed for resources.

SysOpsSee system operations.

sysplexA set of z/OS systems communicating and cooperating with each other through certain multisystemhardware components (coupling devices and timers) and software services (couple data sets).

In a sysplex, z/OS provides the coupling services that handle the messages, data, and status for theparts of a multisystem application that has its workload spread across two or more of the connectedprocessors, sysplex timers, coupling facilities, and couple data sets (which contains policy and statesfor automation).

A Parallel Sysplex® is a sysplex that includes a coupling facility.

sysplex application groupA sysplex application group is a grouping of applications that can run on any system in a sysplex.

sysplex couple data setA couple data set that contains sysplex-wide data about systems, groups, and members that use XCFservices. All z/OS systems in a sysplex must have connectivity to the sysplex couple data set. See alsocouple data set.


Sysplex TimerAn IBM unit that synchronizes the time-of-day (TOD) clocks in multiple processors or processor sides.External Time Reference (ETR) is the z/OS generic name for the IBM Sysplex Timer (9037).

systemIn SA z/OS, system means a focal point system (z/OS) or a target system (MVS, VM, VSE, LINUX, orCF).

System Automation for Integrated Operations ManagementAn outboard automation solution for secure remote access to mainframe/distributed systems. TivoliSystem Automation for Integrated Operations Management, previously Tivoli AF/REMOTE, allowsusers to manage mainframe and distributed systems from any location.The full name for SA IOM.

IBM Z System AutomationThe full name for SA z/OS.

system consoleA console, usually having a keyboard and a display screen, that is used by an operator to control andcommunicate with a system.A logical device used for the operation and control of hardware functions (for example, IPL, alter/display, and reconfiguration). The system console can be assigned to any of the physical displaysattached to a processor controller or support processor.In SA z/OS, the hardware system console for processor controllers or service processors ofprocessors connected using SA z/OS. In the SA z/OS operator commands and configuration dialogs,SC is used to designate the system console for a target hardware processor.

System Display and Search Facility (SDSF)An IBM licensed program that provides information about jobs, queues, and printers running underJES2 on a series of panels. Under SA z/OS you can select SDSF from a pull-down menu to see theresources’ status, view the z/OS system log, see WTOR messages, and see active jobs on the system.

System entryA construct, created with the customization dialogs, used to represent and contain policy for asystem.

System Modification Program/Extended (SMP/E)An IBM licensed program that facilitates the process of installing and servicing an z/OS system.

system operationsThe part of SA z/OS that monitors and controls system operations applications and subsystems suchas NetView, SDSF, JES, RMF, TSO, ACF/VTAM, CICS, IMS, and OPC. Also known as SysOps.

system services control point (SSCP)In SNA, the focal point within an SNA network for managing the configuration, coordinating networkoperator and problem determination requests, and providing directory support and other sessionservices for end users of the network. Multiple SSCPs, cooperating as peers, can divide the networkinto domains of control, with each SSCP having a hierarchical control relationship to the physical unitsand logical units within its domain.

System/390 microprocessor clusterA configuration that consists of central processor complexes (CPCs) and may have one or moreintegrated coupling facilities.

Systems Network Architecture (SNA)The description of the logical structure, formats, protocols, and operational sequences fortransmitting information units through, and controlling the configuration and operation of, networks.

TTAF

See terminal access facility.target

A processor or system monitored and controlled by a focal-point system.

Glossary 627

target control taskIn SA z/OS, target control tasks process commands and send data to target systems and workstationsthrough communications tasks. A target control task (a NetView autotask) is assigned to a targetsystem when the target system is initialized.

target hardwareIn SA z/OS, the physical hardware on which a target system runs. It can be a single-image orphysically partitioned processor. Contrast with target system.

target systemIn a distributed system environment, a system that is monitored and controlled by the focal-pointsystem. Multiple target systems can be controlled by a single focal-point system.In SA z/OS, a computer system attached to the focal-point system for monitoring and control. Thedefinition of a target system includes how remote sessions are established, what hardware is used,and what operating system is used.

taskA basic unit of work to be accomplished by a computer.In the NetView environment, an operator station task (logged-on operator), automation operator(autotask), application task, or user task. A NetView task performs work in the NetView environment.All SA z/OS tasks are NetView tasks. See also message monitor task, and target control task.

telecommunication lineAny physical medium, such as a wire or microwave beam, that is used to transmit data.

terminal access facility (TAF)A NetView function that allows you to log onto multiple applications either on your system or othersystems. You can define TAF sessions in the SA z/OS customization panels so you don't have to setthem up each time you want to use them.In NetView, a facility that allows a network operator to control a number of subsystems. In a full-screen or operator control session, operators can control any combination of subsystemssimultaneously.

terminal emulationThe capability of a microcomputer or personal computer to operate as if it were a particular type ofterminal linked to a processing unit to access data.

thresholdA value that determines the point at which SA z/OS automation performs a predefined action. Seealert threshold, warning threshold, and error threshold.

time of day (TOD)Typically refers to the time-of-day clock.

Time Sharing Option (TSO)An optional configuration of the operating system that provides conversational time sharing fromremote stations. It is an interactive service on z/OS, MVS/ESA, and MVS/XA.

Time-Sharing Option/Extended (TSO/E)An option of z/OS that provides conversational timesharing from remote terminals. TSO/E allows awide variety of users to perform many different kinds of tasks. It can handle short-runningapplications that use fewer sources as well as long-running applications that require large amounts ofresources.

timersA NetView instruction that issues a command or command processor (list of commands) at a specifiedtime or time interval.

TODTime of day.

token ringA network with a ring topology that passes tokens from one attaching device to another; for example,the IBM Token-Ring Network product.


TPSee transaction program.

transaction programIn the VTAM program, a program that performs services related to the processing of a transaction.One or more transaction programs may operate within a VTAM application program that is using theVTAM application program interface (API). In that situation, the transaction program would requestservices from the applications program using protocols defined by that application program. Theapplication program, in turn, could request services from the VTAM program by issuing the APPCCMDmacro instruction.

transitional automationThe actions involved in starting and stopping subsystems and applications that have been defined toSA z/OS. This can include issuing commands and responding to messages.

translating hostRole played by a host that turns a resource number into a token during a unification process.

triggerTriggers, in combination with events and service periods, are used to control the starting and stoppingof applications in a single system or a parallel sysplex.

TSOSee Time Sharing Option.

TSO consoleFrom this 3270-type console you are logged onto TSO or ISPF to use the runtime panels for SA z/OScustomization panels.

TSO/ESee Time-Sharing Option/Extended.

TWSSee ZWS.

Uunsolicited message

An SA z/OS message that is not a direct response to a command.uniform resource identifier (URI)

A uniform resource identifier is a string of characters used to identify a name of a web resource. Suchidentification enables interaction with representations of the web resource over the internet, usingspecific protocols.

user taskAn application of the NetView program defined in a NetView TASK definition statement.

UsingAn RMF Monitor III definition. Jobs getting service from hardware resources (processors or devices)are using these resources. The use of a resource by an address space can vary from 0% to 100%where 0% indicates no use during a Range period, and 100% indicates that the address space wasfound using the resource in every sample during that period.

Vview

In the NetView Graphic Monitor Facility, a graphical picture of a network or part of a network. A viewconsists of nodes connected by links and may also include text and background lines. A view can bedisplayed, edited, and monitored for status information about network resources.

Virtual ServerA logical construct that appears to comprise processor, memory, and I/O resources conforming to aparticular architecture. A virtual server can support an operating system, associated middleware, andapplications. A hypervisor creates and manages virtual servers.

Glossary 629

Virtual Server CollectionA set of virtual servers that supports a workload. This set is not necessarily static. The constituents ofthe collection at any given point are determined by virtual servers involved in supporting the workloadat that time.

virtual Server ImageA package containing metadata that describes the system requirements, virtual storage drives, andany goals and constraints for the virtual machine {for example, isolation and availability). The OpenVirtual Machine Format (OVF) is a Distributed Management Task Force (DMTF) standard that describesa packaging format for virtual server images.

Virtual Server Image CaptureThe ability to store metadata and disk images of an existing virtual server. The metadata describes thevirtual server storage, network needs, goals and constraints. The captured information is stored as avirtual server image that can be referenced and used to create and deploy other similar images.

Virtual Server Image CloneThe ability to create an identical copy (clone) of a virtual server image that can be used to create anew similar virtual server.

Virtual Storage Extended (VSE)A system that consists of a basic operating system (VSE/Advanced Functions), and any IBM suppliedand user-written programs required to meet the data processing needs of a user. VSE and thehardware that it controls form a complete computing system. Its current version is called VSE/ESA.

Virtual Telecommunications Access Method (VTAM)An IBM licensed program that controls communication and the flow of data in an SNA network. Itprovides single-domain, multiple-domain, and interconnected network capability. Its full name isAdvanced Communications Function for the Virtual Telecommunications Access Method. Synonymouswith ACF/VTAM.

VM Second Level Systems SupportWith this function, Processor Operations is able to control VM second level systems (VM guestsystems) in the same way that it controls systems running on real hardware.

VM/ESAVirtual Machine/Enterprise Systems Architecture. Its current version is called z/VM.

volumeA direct access storage device (DASD) volume or a tape volume that serves a system in an SA z/OSenterprise.

VSESee Virtual Storage Extended.

VTAMSee Virtual Telecommunications Access Method.

Wwarning threshold

An application or volume service value that determines the level at which SA z/OS changes theassociated icon in the graphical interface to the warning color. See alert threshold.

workstationIn SA z/OS workstation means the graphic workstation that an operator uses for day-to-dayoperations.

write-to-operator (WTO)A request to send a message to an operator at the z/OS operator console. This request is made by anapplication and is handled by the WTO processor, which is part of the z/OS supervisor program.

write-to-operator-with-reply (WTOR)A request to send a message to an operator at the z/OS operator console that requires a responsefrom the operator. This request is made by an application and is handled by the WTO processor, whichis part of the z/OS supervisor program.


WTOSee write-to-operator.

WTORSee write-to-operator-with-reply.

WWVThe US National Institute of Standards and Technology (NIST) radio station that provides standardtime information. A second station, known as WWVB, provides standard time information at adifferent frequency.

XXCF

See cross-system coupling facility.XCF couple data set

The name for the sysplex couple data set prior to MVS/ESA System Product Version 5 Release 1. Seealso sysplex couple data set.

XCF groupA set of related members that a multisystem application defines to XCF. A member is a specificfunction, or instance, of the application. A member resides on one system and can communicate withother members of the same group across the sysplex.

XRFSee extended recovery facility.

Zz/OS

An IBM mainframe operating system that uses 64-bit real storage. See also Base Control Program.z/OS component

A part of z/OS that performs a specific z/OS function. In SA z/OS, component refers to entities that aremanaged by SA z/OS automation.

z/OS subsystemSoftware products that augment the z/OS operating system. JES and TSO/E are examples of z/OSsubsystems. SA z/OS includes automation for some z/OS subsystems.

z/OS systemA z/OS image together with its associated hardware, which collectively are often referred to simply asa system, or z/OS system.

z196See IBM zEnterprise 196 (z196).

zAAPSee IBM System z Application Assist Processor (zAAP).

zCPCThe physical collection of main storage, central processors, timers, and channels within a zEnterprisemainframe. See also central processor complex.

Glossary 631


IBM®

SC34-2719-02

Documents

Version 4.Release 2 IBM Z System Automation