Messages ING001I to INGY1337I

Explanation

SA z/OS detected an error.

• The variable aaaa shows the service or command that failed.
• The variable bb shows the value of the return code.
• The variable ccccccccc shows the value of the reason code.

Explanation

The specified command or action is only applicable for a secondary automation manager.

• The variable name shows the name of the automation manager that is not defined as secondary automation manager.

Explanation

The specified command or action is only applicable for the primary automation manager.

• The variable name shows that name of the automation manager that is not defined as primary automation manager.

Explanation

The request to update the operation mode of the designated automation manager has been submitted under this task or another work operator.

• The variable request shows the submitted request.

Explanation

There is more than one resource with the specified name within the domain of the automation manager in charge. Because the command is running in line mode, SA z/OS is unable to determine which of the resources the command should be applied to.

• The variable name shows the name of the resource that is not unique.

Explanation

None of the resources defined in the sysplex matches the specified name pattern.

• The variable name shows the name of the resource that could not be found.

Explanation

The display "group members" action was requested for a resource that is not an application group.

• The variable name shows the name of the resource that is not an application group.

Explanation

A service routine was called that ended with a non-zero return code.

• The variable name shows the name of the function that encountered the error. For function INGSTX, see the online command help of INGSTX or see the INGSTX topic in IBM Z System Automation Programmer's Reference for further details.
• The variable return_code shows the return code that the failing service routine returned.
• The variable reason shows descriptive text about the cause of the error.

Explanation

The requested function has been successfully completed.

• The variable parameter shows the name of the parameter that was updated.
• The variable value shows the new value of the parameter.

Explanation

• The variable warning/error information shows descriptive text from the automation manager about the cause of the error.

Explanation

There is an overlap between an UP time slot and a DOWN time slot.

Explanation

The specified command or action is only valid for an automation manager.

• The variable name shows the name of the system where the command could not be processed.

Explanation

The specified parameter is not valid for resources of the specified type.

• The variable parameter_name shows the name of the parameter that is not valid.
• The variable type shows the type of the resource.

Explanation

Self-explanatory.

Explanation

An INGSET CANCEL was issued but the request identified by its type and source does not exist.

• The variable resource shows the name of the resource.
• The variable source shows the name of the source.
• The variable request shows the name of the request that could not be found.

Explanation

The specified scope is not valid for the type of request.

• The variable scope shows the scope that was specified for the request.
• The variable type shows the type of the request.

Explanation

The specified expiration date or time is in the past.

• The variable timestamp shows the specified timestamp.
• The variable system shows the name of the system.

Explanation

You specified more than one group name for an INGGROUP action of ADJUST or MEMBERS.

• The variable action shows the action that could not be performed.

Explanation

An INGGROUP ACTION EXCLUDE, AVOID, DEFAULT, or INCLUDE was requested for a group of nature basic.

• The variable resource shows the name of the resource.

Explanation

Either the specified data set does not exist, or it is not accessible, or, if it is a configuration data set it is not a PDS.

• The variable datasetname shows the name of the data set that is not available.

Explanation

The statistics counts have been reset on the specified system.

• The variable sysname shows the name of the system whose statistics counts were reset.

Explanation

The threshold settings for DEFAULTS, MVSESA and SUBSYSTEM cannot be deleted.

• The variable resource shows the name of the resource that the threshold settings cannot be deleted for.

Explanation

The specified command cannot run under the specified task.

• The variable command shows the name of the command that cannot be run.
• The variable task shows the name of the task that the command cannot be run under.

Explanation

The selected request is created by the automation manager due to:

1. Vote propagation for an application group. This request cannot be canceled. It will be automatically removed when the vote that initiated the request is removed.
2. A service period UP or DOWN window. This request cannot be canceled. It will be automatically removed when the UP or DOWN window ends.

Explanation

The local system has established a communication path with the named system.

• The variable domain identifies the remote system. It is the domain ID of the remote system.
• The variable product is the SA z/OS release running on the remote system.

Explanation

The local system has sent the current version of the INGRVXMT routine to the remote system. This enables the local system to communicate with the remote system via the "remote procedure call" technique rather than NNT sessions.

• The variable clistname is the name of the routine.
• The variable domain identifies the remote system by its domain ID.
• The variable clist_level shows the last APAR number, if present, and compile date.

Explanation

Another system, identified by its domain ID, has sent a routine to communicate with the local system via the "remote procedure call" technique rather than NNT sessions.

• The variable clistname is the name of the routine.
• The variable domain is the domain ID of the remote system.
• The variable product is the SA z/OS release level running on the remote system.
• The variable clist_level shows the last APAR number and compile data of the routine.

Explanation

The specified parameter is either wrong or missing.

• The variable command is the name of the command being processed.
• The variable parameter is the parameter that is invalid or missing.
• The variable value is the value of the parameter that is wrong.

Explanation

Because the clist that is named in the message is compiled, it cannot be sent to the remote system. This is done for two reasons:

1. The REXX runtime library might not be installed on the remote system.
2. The compiled REXX routine does not contain any indication of its software level (release number, last APAR).

• The variable clistname is the name of the routine.
• The variable domain identifies the remote system by its domain ID.

Explanation

An attempt was made to move the group away from the system that it currently runs on, but no other system is available.

• The variable group_name is the move group concerned.
• The variable reason explains in more detail why the group cannot be moved.

Explanation

The consumer specified in the INGEVOBS call is not defined, which means that the consumer is not registered.

• The variable name is the name of the consumer as specified in the INGEVOBS command.

Explanation

You have specified either a satisfactory target value that is larger than the availability target, or an availability target that is less than the satisfactory target assigned to the server group.

• The variable avtgt is the availability target assigned to the group.
• The variable sattgt is the satisfactory target assigned to the group.

Explanation

The gateway monitoring routine found an inbound session status that does not match the actual status. The session status is corrected.

• The variable domain is the name of the domain that the local system has an inbound session with.
• The variable status is the new inbound session status.

Explanation

AOFRYSAB was called to perform a function for a subsystem. The status of the subsystem does not allow this function.

• The variable stat is the current status of the subsystem.
• The variable subsys is the subsystem that the function is to be performed on.
• The variable func is the function that is to be performed

Explanation

The specified system name is either unknown or not a valid choice for the group.

• The variable system_name is the invalid system name.
• The variable group_name is the move group concerned.

Explanation

You attempted to move the group to the specified system either now or at the next recycle, but one of the following conditions is true:

• The system is down or System Automation is not fully initialized.
• The member on that system is not startable.
• The group is already running on that system.

Explanation

You attempted to box the group but the application group is not active.

Explanation

The specified parameters (or their values) conflict.

• The variable p1 is the first invalid parameter.
• The variable p2 is the second invalid parameter.

Explanation

The specified session is not defined in the configuration file (ACF).

• The variable name is the session name.

Explanation

A command was entered but one or more required parameters were not specified.

• The variable keywords shows a list of all the missing parameters.

Explanation

A command was entered but a required parameter was not specified.

• The variable keywords shows a list of possible parameters to be specified.

Explanation

A command was entered but one of its parameters requires another one to be also specified.

• The variable keyword1 shows the parameter that requires keyword2 to be specified.
• The variable keyword2 shows the additional parameter that is required.

Explanation

A command was entered but one of its parameters disallows another one to be also specified.

• The variable keyword1 shows the parameter that excludes the use of keyword2.
• The variable keyword2 shows the parameter that is excluded by the use of keyword1.

Explanation

A command was entered with two parameters. The two values define a range. The second value must be greater than or equal to the first value.

• The variable keyword1 shows the parameter that defines the end of the range.
• The variable keyword2 shows the parameter that defines the start of the range.

Explanation

A command was entered with a parameter that requires a certain data format.

• The variable keyword shows the parameter that requires the format.
• The variable format shows the format that is required as one of the following, or any other self-explanatory text:

  MM/DD/YYYY

  A valid date in the form month/day/year

  HH:MM

  A valid time in the form hour:minute

  Cn

  1–n characters

  Dn

  1–n numeric digits

  Note that there might be additional lines that explain the problem in further detail.

Explanation

A command was entered with a parameter that requires a certain value.

• The variable keyword shows the parameter that requires the value.
• The variable list shows a list of valid values that the parameter can take.

Explanation

A command was entered with a parameter that must be in a certain range.

• The variable keyword shows the name of the parameter that must be in the range.
• The variable from shows the lowest possible value.
• The variable to shows the highest possible value.

Explanation

The specified subsystem is not of the required type.

• The variable subsystem identifies the subsystem.
• The variable type defines the type (CICS®, IMS, etc.).

Explanation

There are no commands specified in the policy for the specified subsystem.

• The variable xxxx identifies the keyword that no commands have been defined for. It can be DISPINFO, IMSINFO, or CICSINFO.
• The variable subsystem identifies the subsystem.

Explanation

A heartbeat was issued.

• The variable parameter shows the parameters that were specified with the heartbeat.

Explanation

A heartbeat was received.

• The variable parameter shows the parameters that were specified.

Explanation

A heartbeat with the specified parameters failed.

• The variable parameter shows the parameters of the failed heartbeat.

Explanation

A heartbeat with the specified parameters is shut down.

• The variable parameter shows the parameters of the shutdown heartbeat.

Explanation

An invalid major resource was specified for the creation of a minor resource.

• The variable object name shows the name of the resource that could not be found.

Explanation

An invalid state was specified in the INGPOST call. The state is converted to 'ALERT'.

• The variable state shows the incorrect state that was converted to 'ALERT'.

Explanation

The resulting GENALERT parameter string exceeds the maximum length for GENALERTs.

• The variable command shows the command that could not be executed.

Explanation

The service called for the specified function returned an unexpected return code.

• The variable module shows the name of the module where the error occurred.
• The variable function shows the name of function that called the service.
• The variable service shows the service that was called.
• The variable function shows the function of the service that was called.
• The variable return code shows the value of the return code that was issued.

Explanation

The status of the object has been set to the referred value.

• The variable object shows the object whose status was updated.
• The variable status value shows the status value of the object.
• The variable status name shows the status name of the object.

Explanation

The user data of the object has been updated to the specified value.

• The variable object shows the object whose status was updated.
• The variable value shows the new status of the object.

Explanation

The specified INPOST command is not allowed for the object.

• The variable command shows the name of the INGPOST command that is not allowed for the object.
• The variable object shows the name of the resource that the command is not valid for.

Explanation

The command with the specified mode has started.

• The variable command shows the name of the command that processing started for.
• The variable mode shows the mode of the command.

Explanation

The command with the specified mode completed.

• The variable command shows the name of the command that processing completed for.
• The variable mode shows the mode of the command.
• The variable return code shows the value of the return code that was issued. A non-zero return code indicates that the command was in error.

Explanation

The command is issued by the command router.

• The variable command shows the name of the command that is being issued.

Explanation

The command could not be executed.

• The variable reason shows the reason why the command could not be executed.

Explanation

At least one group policy attribute has been modified but not yet committed.

• The variable function_key is the function key that activates the group policy change.

Explanation

The interpretation of the topo file could not be processed successfully.

• The variable topo file shows the name of the topo file that could not be loaded.
• The variable reason shows the reason why the topo file could not be loaded.

Explanation

The processing of a remote command on the specified system returned an unexpected return code.

• The variable system shows the name of the system the returned the return code.
• The variable return code shows the value of the return code.

Explanation

The attempt to communicate with the specified system was unsuccessful.

• The variable system shows the name of the system.

Explanation

The variable resource shows the name of the resource.

Explanation

• The variable resource shows the name of the resource.
• The variable reason shows the reason for the unavailability.

Explanation

The variable action shows the value of the parameter ACTION.

Explanation

• The variable module shows the name of the local system's module.
• The variable version shows the version of the local system's module in the format VvRrMm.
• The variable worker shows the name of the target system's module.

Note: This message is logged on the target system.

Explanation

Explanation

ING080I is issued on behalf of a monitor resource that uses the monitor command INGMTRAP to define a trap for one or more OMEGAMON® exceptions. It is issued for each exception that trips.

• Monitor_name is the fully qualified monitor resource name in the format monitor_name/MTR/system_name, which indicates the monitor resource that this exception message was issued for. Note that monitor_name is known to INGMTRAP through the task global &SUBSAPPL.
• Session_name is the name of the OMEGAMON session as it was specified by the NAME keyword on the INGMTRAP command.
• Logon_type is the type attribute used by the OMEGAMON session named Session_name as defined in the automation policy.
• Exception_text is the exception text as returned by OMEGAMON without the leading ‘+’ sign.

Explanation

Message ING081I is never issued to an operator console, but is written to a monitor resource’s history. This happens when the monitor resource uses the monitor command INGMTRAP to define a trap for one or more OMEGAMON exceptions and no exception has tripped.

• Monitor_name is the fully qualified monitor name in the format monitor_name/MTR/system_name, which indicates the monitor resource that this exception message was issued for. Note that monitor_name is known to INGMTRAP through the task global &SUBSAPPL.
• Session_name is the name of the OMEGAMON session as it was specified by the NAME keyword on the INGMTRAP command.
• Logon_type is the type attribute used by the OMEGAMON session named Session_name as defined in the automation policy.

Explanation

The installation failed to define session operator entries in the automation policy.

Explanation

Message ING083 is issued each time a list of one or more commands is sent to the OMEGAMON session that is denoted by session_name.

• command is the first command in the list of commands that was issued with the INGOMX API.
• operator is the operator or automation operator that issued the command.
• session_name is the name of the OMEGAMON session that is to receive the command.

Explanation

SA z/OS failed to communicate with the OMEGAMON session denoted by session_name. The variable rsn contains more specific error information.

Explanation

Message ING085I is issued each time SA z/OS established or destroyed an OMEGAMON session, denoted by session_name.

The action can be either of the following:

• STARTED

  The session was started.

• STOPPED

  The session was stopped.

The current status is indicated in variable status.

Explanation

The task task_name has initialized completely and the PPI receiver named receiver_name is ready for processing requests.

Explanation

The task task_name has deleted the PPI receiver named receiver_name. No more requests can be processed.

Explanation

The PPI receiver owned by the task task_name received an invalid request buffer. The first 64 bytes are dumped with the message in the variable request_data.

Explanation

The task task_name has been activated.

Explanation

You started the task task_name but the task is already active or in the process of becoming active.

Explanation

During the execution of the service service_name, an error occurred. The variable error_info indicates in what context the service was invoked by the task task_name.

For detailed error information, see NetView: Customization - Using Assembler. In the case of NetView Program-to-Program Interface (PPI) errors see NetView: Application Programming Guide for more information related to the service return code rc.

Explanation

An invalid keyword or value was specified in the initialization member for the task task_name. Related error information is provided in the variable error_info.

Explanation

The task task_name has terminated.

Explanation

The PPI receiver owned by task task_name received a request for monitoring data but could not find an active automation operator to process the request.

Explanation

During processing the function request for monitoring data any of the following errors as indicated by text occurred. Examples for text are:

• NetView RC rc from: command
• Timeout occurred
• ING008I …

Explanation

When monitoring a connection between a subsystem and a DB2® or IBM MQ external subsystem, the connection was determined to be in the status not connected.

• The variable subsystem shows the subsystem name as defined in SA z/OS.
• The variable extsysid shows the external subsystem ID of DB2 or IBM MQ.
• The variable connection_id identifies the affected connection.

Explanation

When monitoring a connection between a subsystem and a DB2 or IBM MQ external subsystem, the connection was determined to be in the status connected.

• The variable subsystem shows the subsystem name as defined in SA z/OS.
• The variable extsysid shows the external subsystem ID of DB2 or IBM MQ.
• The variable connection_id identifies the affected connection.

Explanation

This message introduces a list of ING104I messages that show threads that remain with a DB2 main after a thread termination process has completed.

• The variable subsystem shows the name of the DB2 main that threads could not be terminated for.

Explanation

This message shows a thread that remains with a DB2 main after a thread termination process has completed. It is part of a multiline message that begins with message ING103I.

• The variable connection_ID shows the connection ID of a thread that could not be terminated.
• The variable correlation_ID shows the correlation ID of a thread that could not be terminated.
• The variable ddf_ID shows the token associated to a distributed database access thread that could not be terminated.

Explanation

There are indoubt threads existing with the DB2 subsystem named in the message. The message is given when invoking the INGDB2 command checking for indoubt threads.

• Variable name identifies the DB2 subsystem.

Explanation

There are no threads left with this DB2 subsystem for the thread termination process to cancel.

• The variable subsystem identifies the DB2 subsystem.

Explanation

Threads remain with this DB2 subsystem after the thread termination process has completed.

• The variable thread_number shows the number and type of threads.
• The variable subsystem identifies the DB2 subsystem.

Explanation

This message is broadcast to effected TSO users due to a DB2 thread termination request.

• The variable subsystem identifies the DB2 subsystem.

Explanation

This message is broadcast to effected TSO users as a result of a DB2 thread termination request.

• The variable subsystem identifies the DB2 subsystem.

Explanation

This message is issued for batch job cancellations due to a DB2 thread termination or DB2 shutdown process.

• The variable jobname identifies the DB2 batch job.
• The variable subsystem identifies the DB2 subsystem.

Explanation

After the final cycle (as defined by the DBITTH timeout variable), threads were still found to exist for this DB2 subsystem.

• The variable subsystem identifies the DB2 subsystem.

Explanation

The job was canceled due to a tablespace that needed to be stopped.

• The variable jobname shows the job name for the job canceled.
• The variable dbname.tsname identifies the tablespace.
• The variable subsystem identifies the DB2 subsystem.

Explanation

The tablespace indicated is being stopped.

• The variable dbname.tsname identifies the tablespace.
• The variable subsystem identifies the DB2 subsystem.

Explanation

The indicated tablespace is being stopped and operator sessions using it are canceled.

• The variable dbname.tsname identifies the tablespace.
• The variable subsystem identifies the DB2 subsystem.

Explanation

The tablespace indicated is being stopped and all threads are canceled.

• The variable thread_number shows the number and type of threads canceled.
• The variable dbname.tsname identifies the tablespace.
• The variable subsystem identifies the DB2 subsystem.

Explanation

All threads are being stopped by operator request. TSO users with a DSN session are canceled in order to enforce the termination of their DSN session.

• The variable subsystem identifies the name of the DB2 subsystem.

Explanation

This message is produced by SA z/OS and sent to targets such as System Automation for Integrated Operations Management (SA IOM), Netcool®/OMNIbus, or the Tivoli Enterprise Console (TEC) for event notification.

• The variable alert shows the alert identifier that was specified when INGALERT was invoked, or the default that was used.
• The variable resource shows the resource name that was specified when INGALERT was invoked, or the default that was used.
• The variable system shows the system name that INGALERT was invoked on.
• The variable timestamp shows the time when the event was originally produced. It is in the format hh:mm:ss mm/dd/yyyy.

Explanation

An event was successfully sent to targets such as System Automation for Integrated Operations Management (SA IOM), Netcool/OMNIbus, or the Tivoli Enterprise Console (TEC) for event notification. In the case of SA IOM, it has acknowledged receipt of the alert.

• The variable alertid shows the alert identifier that was specified when INGALERT was invoked or the default that was used.
• The variable resource shows the resource name that was specified when INGALERT was invoked or the default that was used.

Explanation

An event was not sent to targets such as System Automation for Integrated Operations Management (SA IOM), Netcool/OMNIbus, or the Tivoli Enterprise Console (TEC) for event notification because the configuration does not allow this. Events are ignored in the following cases:

1. Event notification is not enabled on this agent for any of the intended event notification targets.
2. The Inform List of the resource does not contain the intended event notification target.
3. Code match checking with the message ID INGALERT of the subject resource returned either no data or the value IGNORE.

• The variable alertid shows the alert identifier that was specified when INGALERT was invoked or the default that was used.
• The variable resource shows the resource name that was specified when INGALERT was invoked or the default that was used.

Explanation

An event was not sent to targets such as System Automation for Integrated Operations Management (SA IOM), Netcool/OMNIbus, or the Tivoli Enterprise Console (TEC) for event notification because of an error. The error is detected by the command worker. Messages that are generated by the worker (or workers) are appended to the above message text.

• The variable alertid shows the alert identifier that was specified when INGALERT was invoked or the default that was used.
• The variable resource shows the resource name that was specified when INGALERT was invoked or the default that was used.

Explanation

During code match checking a matching code definition was found. However, the value returned by the matching code definition is invalid.

• The variable entry shows the entry name of the definition in the MESSAGES/USER DATA policy item of the automation policy where the matching code definitions were searched for.
• The variable type shows the message ID of the definition in the MESSAGES/USER DATA policy item of the automation policy where the matching code definitions were searched for.
• The variables code1, code2, and code3 show the values that were used to search for a matching code definition in the MESSAGES/USER DATA policy item of the specified entry and type.
• The variable value shows the value that is returned from the matching code definition.

Explanation

An event is to be sent however the information about the event notification target is incomplete.

• The variable type shows the event notification target that could not be notified. It is one of the following:

  IOM

  System Automation for Integrated Operations Management (SA IOM) could not be reached. The information specified with the ALERTHOST parameter of the INGCNTL command is incomplete.

  EIF

  An EIF event could not be generated. The EAS PPI receiver name to be specified with the EIFPPI parameter of the INGCNTL command is missing.

  TTT

  A trouble ticket could not be generated because the address data for the TDI server or the data set characteristics for the trouble ticket detail data are missing or incomplete. This data should be specified with the TTTHOST and TTTDATA parameters of the INGCNTL command.

  USR

  A user event could not be generated. The name of the automation procedure that is used to handle user events is missing. The procedure name should be specified with the USRHANDLER parameter of the INGCNTL command.

Explanation

An alert is to be sent to targets such as System Automation for Integrated Operations Management (SA IOM), Netcool/OMNIbus, or the Tivoli Enterprise Console (TEC) for event notification. However event notification is not enabled on this agent for any supported event notification target.

Explanation

An event is to be sent to an event notification target such as IOM, EIF, TTT or USR. However, the resource type specified is not supported for event notification.

• The variable type shows the type of the resource that was specified, which is not valid for event notification.

Explanation

A request timed out.

• The variable function shows the name of the function that detected the time out.
• The variable request shows the request that timed out.

Explanation

This message provides header information for the INGCNTL LIST command.

Explanation

ING150I represents an event that was injected into the system by an external or internal monitor. Typically INGMON is called from the NetView automation table as an action for this event. INGMON will find the corresponding monitor resources and trigger automation there if applicable.

• The variable timestamp is the time that the event was originally produced or when the message was created. It is in the format hh:mm:ss mm/dd/yyyy.
• The variable object specifies the monitored object that this event is related to.
• The variable severity specifies the severity of the status of the monitored object that led to this event.
• The variable jobname specifies the job name that the monitored object is related to or 'N/A' if there is none.
• The variable data can be any data the monitor provides that might be useful for automation or recovery actions.

Explanation

The ATTACH of a virtual operator station task (VOST) was successful.

• The variable name specifies the attach name of the VOST. Note that this name is the content of TGLOBAL SUBSJOB, that is, the job name of the VOST management APL.

Explanation

The ATTACH of a virtual operator station task (VOST) failed with a return code greater than 0.

• The variable name specifies the attach name of the VOST. Note that this name is the content of TGLOBAL SUBSJOB, that is, the job name of the VOST management APL.
• The variable rc shows the return code given by the ATTACH command.

Explanation

The stopping of a virtual operator station task (VOST) was initiated successfully. Note that the VOST may still be active for a certain time after this message is issued.

• The variable command shows the command used to stop the VOST.
• The variable name specifies the attach name of the VOST. Note that this name is the content of TGLOBAL SUBSJOB, that is, the job name of the VOST management APL.

Explanation

The stopping of a virtual operator station task (VOST) failed with a return code greater than 0.

• The variable command shows the command used to stop the VOST.
• The variable name specifies the attach name of the VOST. Note that this name is the content of TGLOBAL SUBSJOB, that is, the job name of the VOST management APL.
• The variable rc shows the return code given by the command.

Explanation

A command was issued in an unsupported environment.

• The variable command shows the command that was executed.
• The variable rs shows the reason code that can have the following values:

  1

  Required task globals not set

  2

  Running on an unsupported task

  3

  Configuration not fully loaded

  4

  Main include member could not be read

  5

  ACFLEVEL could not be determined

  6

  ACFLEVEL mismatch

Explanation

The command executed in a virtual operator station task (VOST) ended.

• The variable name specifies the attach name of the VOST.
• The variable rc shows the return code of the command that ran in the VOST.

Explanation

Data was found that is not valid.

• The variable name specifies the context.
• The variable value shows the invalid data.

Explanation

An event was only partially sent to the designated targets.

• Variable alertid identifies the alert identifier that was specified when INGALERT was invoked or the default was used.
• Variable resource identifies the resource.

Explanation

An exit was called but returned either an invalid return code or invalid data.

• The variable exitname shows the name of the exit that was called.
• The variable reason shows why the exit is considered to be in error:

  01

  Unexpected return code

  02

  Invalid number of data lines returned

  03

  Invalid data found in the returned lines

Explanation

This message displays the names and values of the attributes that have been requested by an ITM SOAP request. The attribute names and values are separated by the separator character, sep, of value X'FF'.

The first line of this multiline message denotes the SOAP server, server_name, that provided this response.

The second line contains the attribute names separated by the separator character. All the following lines contain the attribute values separated by the separator character.

This message is written to the console only.

Explanation

A SOAP request is being sent to the SOAP server denoted by server_name. This message is written to the netlog only.

Explanation

The SOAP request failed with a fault code of code. Possible codes are Client, VersionMismatch, MustUnderstand, and Server. The Client fault code indicates that the SOAP message was incorrectly formed.

The reason text indicates the particular fault.

This message is written to the console only.

Explanation

This message provides further detail in variable text about the fault reported in the preceding ING162I message. This message spans multiple lines if further fault details are reported in the SOAP response.

This message is written to the console only.

Explanation

An error occurred while attempting to process a SOAP request on the SOAP server denoted by server_name. The actual error reason is encoded in the separate reason variable.

This message is written to the console only.

Explanation

This message reflects the status line of a preceding HTTP request in case of a non-zero status code.

• The variable protocol reports the HTTP protocol used by the server.
• The variable status-code reports the status of the request.
• The variable reason-phrase contains human readable information explaining the status-code.

This message is written to the netlog only.

Explanation

This message reports additional information about the HTTP response, where the variable text contains general header fields, response header fields, and entity header fields.

This message is written to the netlog only.

Explanation

This message is issued as the result of a 3xx status code received as the response of the HTTP SOAP request. The request URI was either temporarily or permanently moved to a new location or is only accessible through the proxy server at the reported location. The request must be redirected to the new location reported by the variable location.

This message is written to the console only.

Explanation

The caller of INGOMX attempted to activate an OMEGAMON session or to perform a SOAP request using a PassTicket for authentication. However, the caller is not authorized to generate a PassTicket on behalf of the user defined for this OMEGAMON session or SOAP server, respectively.

This message is written to the Netlog only.

• The variable reason shows the return and reason codes of the underlying applications, such as the SAF application, RACF, or the PassTicket service.

Explanation

The caller of INGOMX attempted to activate an OMEGAMON session or to perform a SOAP request using a PassTicket for authentication. However, the system was not able to generate a PassTicket.

This message is written to the Netlog only.

Explanation

• The variable entry-type displays any entry-types that have been deleted.

Explanation

• The resource_name variable shows the resource in automation manager notation that has been released.

Explanation

• The command_name variable shows the command that issues this message.
• The resource_name variable shows the resource in automation manager notation that is suspended.

Explanation

• The command variable shows the command for which a resource cannot be found.

Explanation

Explanation

This message is created by the SA z/OS internal notification function to send current status information to the end-to-end automation adapter.

Explanation

This message is created by the SA z/OS internal event notification function when the status of a resource changes. It shows the resource’s new status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when a request has been issued to start or stop a resource. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable request indicates if an Online or Offline request has been issued.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the observed status of a system resource has changed from Sysgone.

• The variable system shows the name of the system.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the observed status of a system resource has become Sysgone.

• The variable system shows the name of the system.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when a request has been issued to switch on or off the automation flag of a resource. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the observed status of the resource has become degraded. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the health status of the resource has become degraded. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the startable status of the resource has become inhibited. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports a problem in the automation state or the observed state. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the observed status of the resource has changed to harddown. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the observed status of the resource has changed to sysgone. It shows the resource’s current status in the end-to-end automation resource data model.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.
• The variable observed shows the observed state of the resource.
• The variable desired shows the desired state of the resource.
• The variable operational shows the operational state of the resource.
• The variable compound shows the compound state of the resource.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager sends an event with an unknown reason.

• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that the status of the automation domain is Online.

• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that the status of the automation domain is Offline.

• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that the automation policy has been refreshed in the automation domain.

• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a new resource has been created in the automation domain.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a resource has been deleted in the automation domain.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a new request has been issued for the resource in the automation domain.

• The variable domain shows the name of the end-to-end automation domain.
• The variable resource shows the name of the resource.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a request for the resource in the automation domain has been deleted.

• The variable domain shows the name of the end-to-end automation domain.
• The variable resource shows the name of the resource.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a new relationship has been created between the source resource and the target resource in the automation domain.

• The variable domain shows the name of the end-to-end automation domain.
• The variable relationship shows the name of the relationship.
• The variable source shows the name of the dependent resource.
• The variable target shows the name of the supporting resource.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that a relationship between the source resource and the target resource in the automation domain has been deleted.

• The variable domain shows the name of the end-to-end automation domain.
• The variable relationship shows the name of the relationship.
• The variable source shows the name of the dependent resource.
• The variable target shows the name of the supporting resource.

Explanation

This message is created by the SA z/OS internal event notification function to inform the end-to-end automation adapter that properties have been changed in the automation domain.

• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the desired status of a system resource has changed to Available.

• The variable system shows the name of the system.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the desired status of a system resource has changed to Unavailable.

• The variable system shows the name of the system.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the automation flag of the resource has been switched off.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

This message is created by the SA z/OS internal event notification function when the automation manager reports that the automation flag of the resource has been switched on.

• The variable resource shows the name of the resource.
• The variable domain shows the name of the end-to-end automation domain.

Explanation

An event was received with a consumer that was not registered as the target address. The event therefore cannot be forwarded to the addressed consumer.

• The variable consumer shows the name of the event consumer that was specified as the target address of the event, and that the event should have been forwarded to.

Explanation

The event could not be forwarded to the addressed consumer.

• The variable rc shows the return code.
• The variable receiver_id shows the name of the PPI receiver ID.

If the NetView EA/S is used for event forwarding, then rc 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 Automation internal event forwarding mechanism AOF_PPI_CALLJAVA. Check if the E2E adapter is already running since the event is sent directly to the E2E adapter without using EA/S.

Explanation

The PPI receiver ID for the message adapter of the event/automation service, which is used to forward events to the automation adapter, has been set to the specified receiver ID.

Explanation

The primary agent cannot be started because the automated function EVTOPER, which is used to forward the events to the automation adapter, has not been defined in the automation policy.

Explanation

The specified command abended.

• The variable request shows the request that was received from the automation adapter for execution.
• The variable rc shows the return code of the command.
• The variable command shows the command that implements the request.
• The variable reason shows text that describes the error.

Explanation

An error occurred when requesting information from the automation manager that needed to be included in a domain event. The event has not been created.

• The variable event specifies the event to be created. Possible values are: READY, REFRESH, CHANGE.

  A READY event is created at initialization time of the automation domain and after having recovered from miscellaneous error situations.

  A REFRESH event is created after having refreshed the configuration policy.

  A CHANGE event is created after a takeover of the automation manager if the outage has not exceeded a given time interval.

• The variable consumer shows the name of the event consumer that the event should have been forwarded to.

Explanation

Explanation

A warning was issued when executing an end-to-end request.

• The variable request shows the name of the end-to-end request.
• The variable command shows the issued command that implements the request.
• The variable reason specifies the warning message.

Explanation

The service, return_code, or reason variables may not have a value.

Explanation

The value provided in the advanced automation option is not accepted as a valid value.

• The variable name shows the name of the advanced automation option.
• The variable value shows the value of the advanced automation option.

Explanation

The REXX macro implemented to execute the task execution request was called with an unexpected task execution request name.

• The variable tex_request shows the name of the task execution request.

Explanation

The REXX macro implemented to execute the task execution request was called with an unexpected task execution request type.

• The variable type shows the type of task execution element.

Explanation

The REXX macro implemented to execute the task execution request cannot read the task execution element from the data stream.

Explanation

The REXX macro implemented to execute the task execution request cannot write to the data stream to return data to the calling routine.

Explanation

The REXX macro implemented to execute the task execution request was passed an invalid filter element name.

• The variable filter shows the name of the filter element.

Explanation

The REXX macro implemented to execute the task execution request was passed duplicate filter element names.

• The variable filter shows the name of the filter element.

Explanation

The REXX macro implemented to execute the task execution request was passed an invalid combination of filter element names.

• The variables filter1 and filter2 show the names of the two filter elements.

Explanation

The REXX macro implemented to execute the task execution request was passed an unknown filter value.

• The variable filter shows the name of the filter.
• The variable value shows the value of the filter.

Explanation

The REXX macro implemented to execute the task execution request was passed a filter element with an unknown operator comparing the filter name and filter value.

• The variable filter shows the name of the filter.
• The variable operator shows the filter operator.

Explanation

The expiration time that was provided for the task execution request was too short.

• The variable time shows the expiration time that was provided for the task execution request.
• The variable missing_time specifies the missing time interval.

Explanation

A service routine timed out without exploiting the expiration time that was provided for the execution of the task execution request. The execution time was reduced to the maximum value for the WAIT parameter of the executed service.

• The variable time shows the expiration time that was provided for the task execution request.
• The variable number shows the value for the WAIT parameter of the executed service.

Explanation

The REXX macro implemented to execute the task execution request was passed an invalid combination of values for the filter elements.

• The variables filter1 and filter2 show the names of the two filter elements.
• The variables value1 and value2 show the values of the two filter elements.

Explanation

Initialization of the automation domain failed because initialization of the system automation environment of the primary agent has not yet been completed.

Explanation

Initialization of the automation domain failed because the primary agent is already running on another system within the subplex.

• The variable system shows the system name.

Explanation

Initialization of the automation domain failed because the PPI receiver ID of the NetView event/automation service is not active.

• The variable receiver shows the name of the PPI receiver.

Explanation

Requesting information from automation manager of an automation domain failed. Requesting information from automation is necessary during the initialization of the automation domain or when requesting information about the automation domain.

• The variable domain shows the name of the automation domain.

Explanation

Events were lost when trying to forward them from the primary agent to the automation adapter. Event forwarding has therefore been switched off, which results in failing the health check of the automation domain.

Explanation

The PPI receiver identifier of the event/automation service is not in the status ACTIVE. This results in failing the health check of the automation domain.

• The variable receiver shows the PPI receiver ID of the NetView event/automation service.

Explanation

The requested service did not return the expected data.

• The variable service shows the name of the requested service.

Explanation

An end-to-end request with an unknown name was received.

• The variable name shows the request name.

Explanation

An end-to-end request with an unknown type was received.

• The variable type shows the request type.

Explanation

Multiple solicited end-to-end requests were received to be executed by the primary agent. Only one solicited end-to-end request can be accepted.

Explanation

An end-to-end request was received with parameters that attempted to overwrite restricted parameters. The parameters are ignored.

• The variable parameters shows a list of the ignored parameters.

Explanation

An end-to-end request was received without the specified originator of the request via parameter SOURCE.

Explanation

A reset-from-non-recoverable-error request was received for a resource that is in agent status CTLDOWN. Such a request is not supported for resources in agent status CTLDOWN.

• The variable resource shows the name of the resource that the request was issued for.

Explanation

A reset-from-non-recoverable-error request was received for a resource that is not in status HARDDOWN. Such a request is only supported for resources in status HARDDOWN.

• The variable resource shows the name of the resource that the request was issued for.

Explanation

A reset-from-non-recoverable-error request was received for a resource. An error occurred when requesting information from the automation manager about the resource that the request was issued against.

• The variable resource shows the name of the resource that the request was issued for.

Explanation

A reset-from-non-recoverable-error request was received for a resource that is not of class APL. This request is only supported for resources of type APL.

• The variable resource shows the name of the resource that the request was issued for.

Explanation

An end-to-end request concerning a system was issued, but the system name was not specified.

• The variable request shows the name of the end-to-end request.

Explanation

An invalid value was specified as the WAIT parameter when issuing a native command.

• The variable wait shows the value for the WAIT parameter that was received.

Explanation

The execution of the specified command is rejected by the authorization user exit AOFEXE2E.

• The variable user shows the user ID that is associated with the command.
• The variable command shows the rejected command resulting from the related end-to-end request.

Explanation

A timeout occurred when waiting for asynchronous output generated by a command that was issued from within a PIPE.

Explanation

More than one request in a list of requests that were included in a task execution request failed.

Explanation

More than one request in a list of requests that were included in a task execution request were processed with warnings.

Explanation

An error occurred when requesting information from the automation manager via the automation manager API INGPYAMC.

Explanation

A command was called that ended with a non-zero return code.

• The variable command shows the failed command.

Explanation

The return code of the requested service indicates a timeout problem.

Explanation

The command handler of the Automation Agent Java™ Framework detected an error.

• The variable RC is the return code from the command handler INGRXCMJ as described below.
• The variable ReasonText is the description of the error, as described below.

Explanation

Explanation

Explanation

A command has finished processing and achieved what it has been asked to do, for example, starting a resource.

• The variable command is the command being executed.

Explanation

A command has finished processing but has not achieved what it has been asked to do. For example, when starting a resource, the resource is not in the expected state after the allowed time period.

• The variable command is the command being executed.
• The variable hh:mm:ss is the timer period.

Explanation

No request exists for the specified resource that originated from the same source.

Explanation

Z System Automation was waiting for the termination of the name component, but the termination command was aborted.

• Variable name is the name of component.
• Variable reason explains why the termination command was aborted.

Explanation

Indicates that the termination of the system has been started. The shutdown was either requested by the local operator, GDPS® or the Active/Active controller.

• Variable name identifies the name of the system.

Explanation

Indicates that the shutdown of the names system is nearly finished. Only NetView is still active.

• Variable name identifies the name of the system.

Explanation

Indicates that Z System Automation is already working on shutting down the named system.

Explanation

System automation is in the middle of shutting down the system and is waiting for the termination of the named component / address space. The termination process is on halt till the named component becomes inactive.

• Variable name identifies the name of the system.

Explanation

A system shutdown was requested by means of the INGREQ ALL command. Since the system is under control of GDPS, only the toplevel resource identified by means of the GDPS STOPAPPL parameter in the GEOPLEX OPTIONS member is terminated.

• Variable name identifies the name of the system.
• Variable resource identifies the GDPS STOPAPPL resource.

Explanation

This message is used to transport the completion block from the system being terminated back to the Active/Active Controller.

Explanation

The Active/Active controller has requested either to Start, Stop a workload or to query the status of the workload, but the workload is not defined in the Z System Automation policy. Workload must be defined in the GDPS_WORKLOAD policy under the MVS component.

• Variable name identifies the workload.

Explanation

The Active/Active controller has requested either to Start or Stop a workload, but this failed. See the NetView log for more details about the failure when the workload is managed by Z System Automation or the system log otherwise.

• Variable action identifies the action being performed (START or STOP).
• Variable name identifies the workload.

Explanation

IPL completed within the expected time period. This means all required resources have reached one of the specified statuses. The specified statuses are shown in DISPSYS. This message will only be reported on the console.

• Variable time shows the time when this message was generated.
• Variable duration shows the time it took all required resources to reach one of the specified statuses.

Explanation

IPL did not complete within the maximum time limit. This means not all required resources have reached one of the specified statuses. The specified statuses are shown in DISPSYS. The failing resources are appended to the above message test. This message will only be reported on the console.

• Variable time shows the time the message was generated.
• Variable limit shows the specified maximum time limit within an IPL is considered to be completed successfully.
• Variable resource displays the names of all resources which have not reached one of the specified statuses.

Explanation

• Variable time shows the time when this message was generated.
• Variable duration shows the time it took all required resources to reach one of the specified statuses.

Explanation

The IMFEXEC command was invoked passing a function code that is not supported by Z System Automation.

• Variable emulator is the name of the command, for example IMFEXEC or OPSCMD.
• Variable command identifies the function that is not supported by Z System Automation.
• Variable caller identifies the REXX script that called the IMFEXEC command.

Explanation

The IMFEXEC CMD command was called, but no longer supported in the NetView/Z System Automation environment.

• Variable emulator is the name of the command, for example IMFEXEC or OPSCMD.
• Variable function identifies the function.
• Variable caller identifies the REXX script that called the IMFEXEC command.

Explanation

The IMFEXEC command was called for a supported function, but the specified parameter is not supported by the Z System Automation emulator.

• Variable emulator is the name of the command, for example IMFEXEC or OPSCMD.
• Variable function identifies the function.
• Variable parameter identifies the parameter that is not supported.
• Variable caller identifies the REXX script that called the IMFEXEC command.

Explanation

This message is used to carry the alert text from an IMFEXEC ALERT function call

Explanation

The OPSCMD command was invoked but no command was specified.

Explanation

The OPSCMD command was invoked specifying a value for a parameter that is not supported by the Z System Automation provided emulator.

• Variable parameter names the parameter.
• Variable value is the value.

Explanation

The OPSCMD was invoked specifying a system that is not known in Z System Automation.

• Variable parameter is SYSID/SYSTEM.
• Variable value is the name of the system that is unknown.

Explanation

The OPSCMD was invoked to execute the specified command.

• Variable jobname is the name of the job who originated the OPSCMD call.
• Variable userid is the user id associated with the job.
• Variable command is the command being used.

Explanation

From TSO, the function INGRCRPC was called to execute a command in the SA NetView agent.

This command was executed successfully. Output data might have been returned to the caller.

Explanation

From TSO, the function INGRCRPC was called to execute a command in the SA NetView agent.

This command execution failed due to timeout. Output data has not been returned to the caller.

The command might still be running on the NetView task until it is completed. However, the connection to the command execution task has been interrupted and no data will be returned to the TSO caller.

Explanation

From TSO, the function INGRCRPC was called to execute a command in the System Automation Agent.

The execution of command cmd failed with return code rc in the System Automation Agent on system sys. Additional error description xxxx might be available and describes the reason for the error. If the rc 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 that controls the execution of the command within the NetView task may return the following reserved return codes.

Explanation

The RPC receiver with PPI receiver ID xxx is starting.

Explanation

The RPC receiver with PPI receiver id xxx is already running.

Explanation

From TSO, the function INGRCRPC was called to execute a command in the SA NetView agent. This command cmd will be executed on the NetView task task_name on behalf of the TSO job job_name, TSO user user_ID, and TSO CLIST clist_name.

Explanation

The RPC receiver with PPI receiver id xxx is stopping due to operator request. A stop-command has been received and issued by 'INGRCRCV STOP PPI=xxx'

Explanation

ING337I PPI RECEIVER STATUS LIST 
        STATUS   PPI      TASK     VOST
        ------   -------- -------- --------
        ACTIVE   INGRCRCV DSI#0020 EMURCV2
        ACTIVE   PPIABC   BDOW     

Explanation

A function or a command with name xxxx failed with return code nn. Additional error description is given in yyyy.

It might be that an error has occurred in the past while initializing the RDS environment.

For explanation of return code nn see the table below.

Explanation

The RPC receiver with PPI receiver id xxx executed a remote command which failed. However, the receiver continues processing and waits for the next command.

Explanation

The function INGRCVAF has filtered n1 number of global variables. n2 global variables have been deleted. If n2 is smaller than n1 then either the global variable cannot be found or an error occurred.

Explanation

The RPC receiver with PPI receiver id xxx has been stopped.

Explanation

Command 'INGRCRCV QUERY' does not find any receivers that were started.

Explanation

The function or command yyyy was invoked passing a parameter that is not supported by Z System Automation.

• Variable xxxx identifies the parameter that is not supported by Z System Automation.
• Variable yyyy is the name of the command that detected the error.

Explanation

This message is used by command INGVALUE in order to report an error, while performing an archive/restore operation. This message might be trapped by the automation table.

Token 3 of the message is the subsystem job name, token 5 the subcommand that failed and token 6 the kind of error. For example, VSAM_IO_ERROR.

You can use this message to set the resource RDSARCH, for example, to status abending.

Explanation

Command 'INGVALUE STATUS' reports the status of the long global variable framework. This message is also written if the command 'INGVALUE RESTORE' was successful.

xxx might have the following values:

• RESTORE SUCCESSFUL - Persistent long global variables were restored successfully.
• INITIAL RESTORE OK - Initialization of persistent long global variables was successful during initialization of Z System Automation.
• INITIAL RESTORE NOT DONE - Initialization of persistent long global variables was not done during initialization of Z System Automation.
• INITIAL RESTORE FAILED - Initialization of persistent long global variables failed during Z System Automation initialization.

Explanation

ING338I Function or command INGRCVAL failed, 
RC=204 REASON=invalid character found
ING346I Abort function INGRCVAL on purpose at LINE 83
   270 +++ return
IRX0045I  Error running INGRCVAL, line 270: 
No data specified on function RETURN

Explanation

The receiver task was started by command 'INGRCRCV START OPF=xxx'. The receiver searches for the existence of the automation operator task (for example, if xxx is AOFCMDOPER then the tasks are AOFCMDnn, nn=00,01,02,..) but no active task was found.

Explanation

The receiver task was started by command 'INGRCRCV START OPF=xxx'. The receiver searches for the existence of the automation operator task (for example, AOFEMUnn, nn=00,01,02,...) but found at least one task that was inactive or not defined.

The receiver task continues running but executing incoming commands might be degraded because the inactive tasks are skipped, and commands might be queued.

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

Explanation

During initialization SA z/OS detected an improper definition for the Job Log Monitoring task.

• The variable name shows the subsystem name that is affected.
• The variable rsn shows the reason:

  10

  Job Log Monitoring interval defined but no message ID.

  11

  Offset specification is invalid.

  12

  Token specification is invalid.

  13

  Message ID defined even if JOBLOGALL has been specified.

  14

  Message offset is 0 but no token has been defined.

  15

  Token has been defined but no message offset.

  16

  Monitoring interval is invalid.

  17

  DD name specification is invalid.

  18

  Message ID is invalid.

Explanation

System Automation security checking fails such that not one of the other security messages can be issued any more. The reason_text explains the error.

Explanation

Explanation

Explanation

AGT.sysplex.xcfgrp.TARGET.FROMDOM.domain.TODOM.
targetdomid

Explanation

A command received from outside NetView (for example, via PPI) is rejected for execution. SAF checking against following profile within class NETCMDS failed: netid.domid.command

The reason_text provides more detail:

• Access denied for USER=user CLASS=NETCMDS PROFILE=xxxx. In this case, grant the user access to the specified profile.
• Profile not defined PROFILE=xxxx in CLASS=NETCMDS. In this case, define the specified profile in NETCMDS.

Explanation

This message is used to return command response data of any kind. It helps to distinguish between the various systems that were specified in the TARGET parameter.

The first 10 characters specify always the system name where the response comes from. The response data starts at position 11. If the response has multiple lines, then ING370I will be returned multiple times.

Explanation

This message is used to return command completion information. It helps to distinguish between the various systems that were specified in the TARGET parameter.

Explanation

This message is used to return the overall command transmission code.

This message might occur at most once if command execution fails on at least one of the target systems or if another kind of error occurs before the command can be sent.

The message is issued by the System Automation internal function INGPYCOM which might be called by external commands.

The reason xxxxx variable describes the return code in text form.

Return Code nn:

Explanation

• The variable dmn shows the name of the remote automation domain.
• The variable reason shows an explanation of the error.

Explanation

Explanation

This diagnostic message is issued by the E2E agent to signal that a task was executed unsuccessfully within the USS process of the E2E agent. For example, the task might be an online, offline, or subscription request to the remote domain that is specified in the variable dom. Many of these tasks might be processed within a thread pool in parallel and an unsuccessful result will be reported for each task and remote domain.

This diagnostic message appears in a multi-line message together with other error messages that are detected by the E2E agent. The multi-line message is written to NETLOG only.

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

Explanation

The variable name identifies the resource that was not created.

Explanation

The variable name identifies the resource that was created.