|
|
|
Reason:
An invalid parameter was passed on the $ELSV000 command.
P1 is the keyword operand that was in error, and P2 is the invalid value.
System Action:
Topology and EventView processing not started.
User Action:
Correct operand and retry.
Reason:
The $ELCM000 procedure/command was issued with an invalid OPT parameter.
System Action:
None.
User Action:
Correct OPT= value, and retry.
Reason:
A SOLVE:Ops OV/NV command was issued, and command processing has started.
P1 is the command.
System Action:
Command processing commences.
User Action:
None. (Informational)
Reason:
A command was issued and a required operand is missing.
P1 is the missing operand.
P2 is the command.
System Action:
Command not issued.
User Action:
Re-issue the command with the required operand included.
Reason:
A workstation peer system running SOLVE:OPS OV/NV attempted to open the SOLVE:Ops OV/NV event flow on this SOLVE:Operations region. The connection was rejected because this region is not configured to use SOLVE:Ops OV/NV.
P1 Is the host name of the Unix Workstation that tried to connect.
System Action:
The SOLVE:Operations component of SOLVE:Ops OV/NV is not started.
User Action:
To configure SOLVE:Operations to connect to SOLVE:Ops OV/NV system, update the $RM WSPEER Customisation parameter group in SOLVE:Operations.
Reason:
The SOLVE:OPS OV/NV ServiceView/ResourceView component failed because a vartable allocation failed.
System Action:
SOLVE:OPS OV/NV topology processing fails.
User Action:
Terminate and re-start SOLVE:OPS OV/NV topology processing.
Reason:
An error occured when a procedure in SOLVE:OPS OV/NV tried to profile itself for a certain event type.
System Action:
SOLVE:OPS OV/NV transaction fails.
User Action:
Check SOLVE:OPS OV/NV userid Event Distribution Services (EDS) authority. Contact technical support.
Reason:
SOLVE:Ops OV/NV attempted to send a trap but failed because the component which sends the traps to the workstation was not active, or was not profiled to receive resource status events.
System Action:
Resource status events are not sent to WorkStation.
User Action:
Check event daemon started with the ServiceView/ResourceView option set or defaulted to active. Re-start the event daemon. Re-start SOLVE:OPS OV/NV using the $ELCM000 command if the initial population of the topology diagram was not complete at time of error.
Reason:
An invalid parameter was used on a procedure call in SOLVE:Ops OV/NV.
System Action:
SOLVE:Ops OV/NV topology processing fails.
User Action:
Contact technical support.
Reason:
The SOLVE:Ops OV/NV topology map processing was started. (via the $ELSV000 command). Topology processing is the flow of ServiceView and ResourceView events to the WorkStation.
P1 is the host name of the workstation to which the events are sent.
P2 is the resource filter being used.
System Action:
Topology information should soon be sent to the workstation.
User Action:
None. (Informational)
Reason:
The FILTER specified in the SOLVE:Ops OV/NV initialization script on the workstation is unknown on this SOLVE region. The normal default filter has been used instead.
System Action:
Default filter is used.
User Action:
Check filter specification in the installation script on the workstation. Check that filter exists on the SOLVE region.
Reason:
An APPC receive error starting the conversation that sends events to the workstation event manager.
System Action:
SOLVE:Operations OV/NV event flow terminates.
User Action:
Check installation details for SOLVE:Operations client on workstation, OV/NV and also on the product region server.
Reason:
An APPC SEND error occurred while sending events to the workstation event manager.
System Action:
SOLVE:Operations OV/NV event flow terminates.
User Action:
Check that workstation is active. Check that link is still active. Check Installation of SOLVE:Operations OV/NV on workstation and on the product server region.
Reason:
An error occurred while BER encoding a SOLVE:Ops OV/NV event into an SNMP trap for sending to the workstation event manager.
System Action:
Skips this event without sending it and waits for the next.
User Action:
Contact systems programmer. Check installation, including ASN1 maps are compiled on this version the product region.
Reason:
An error occured when a procedure in SOLVE:Ops OV/NV tried to profile itself for a certain event type.
System Action:
SOLVE:Ops OV/NV server terminates.
User Action:
Check SOLVE:Ops OV/NV userid Event Distribution Services (EDS) authority. Contact technical support.
Reason:
The SOLVE:Ops OV/NV SNMP trap flow is terminating because it received a termination event, probably as the result of a terminate command.
System Action:
SOLVE:Ops OV/NV server terminates completely.
User Action:
Re-start SOLVE:Ops OV/NV from workstation if required.
Reason:
The SOLVE:Operations OV/NV process that receives events and sends them as traps to the workstation has reached its queue limit, and events received discarded.
The NMIQLIM parameter controls the maximum size of the event queue. The default is 32767.
System Action:
Events are discarded until queue size drops.
User Action:
Investigate why so many events are queued.
Reason:
An error occurred trying to BER encode an event in to an SNMP trap.
P1 is the ZMDORC value,
P2 is the ZMDOFDBK value.
System Action:
SOLVE:Ops OV/NV processing terminates.
User Action:
Contact technical support.
Reason:
An error occurred trying to start the link monitor in SOLVE:Ops OV/NV.
P1 is the return code from the start.
P2 is any error message returned from the start.
System Action:
SOLVE:Ops OV/NV processing terminates.
User Action:
Contact technical support.
Reason:
SOLVE:Ops OV/NV has been started from the workstation, and the SNMP trap sender has been activated.
P1 is the host name of the workstation to which the events are sent.
System Action:
SOLVE:Ops OV/NV should receive events as they arise.
User Action:
None. (Informational)
Reason:
A workstation peer system running SOLVE:Ops OV/NV attempted to open an SNMP trap flow from this SOLVE:Operations region, however this region is not configured to use SOLVE:Ops OV/NV, so the connection was rejected. SOLVE:Ops OV/NV is configured by setting the SOLVE:Operations $RM WSPEER Customization parameter group.
System Action:
The SOLVE:Operations component of SOLVE:Ops OV/NV is not started.
User Action:
To configure SOLVE:Operations to connect to a SOLVE:Ops OV/NV system, update the $RM WSPEER Customization parameter group in SOLVE:Operations.
Reason:
A Socket error occurred while trying to start the flow of SNMP traps from SOLVE:Operations to SOLVE:Ops OV/NV running on a workstation.
System Action:
The SOLVE:Operations component of SOLVE:Ops OV/NV is not started.
User Action:
Check that the $RM WSPEER parameter group in SOLVE:Operations has been configured correctly. Check that the TCP/IP port numbers are not in use by any other applications.
Reason:
An error occured when the alert monitor was invoked to create an agent to receive alerts that are to be sent to SOLVE:Operations for OpenView and NetView. P1 contains more details of the error.
System Action:
The SOLVE:Operations for OpenView and NetView server terminates.
User Action:
Contact your support representative.
Reason:
During initialization of SOLVE:Ops OV/NV, an attempt to define an APPC mode failed.
System Action:
Mode not defined. SOLVE:Ops OV/NV may not run.
User Action:
Contact systems programmer.
Reason:
During initialization of SOLVE:Ops OV/NV an attempt to define an APPC link failed.
P1 is the error message received.
System Action:
Link not defined, meaning SOLVE:Ops OV/NV may not run.
User Action:
Contact systems programmer to check installation.
Reason:
A DEFTRANS for an APPC transaction failed during SOLVE:Ops OV/NV initialization.
P1 is the error message received.
System Action:
Transaction not defined, meaning SOLVE:Ops OV/NV can't run.
User Action:
Contact systems programmer to check installation.
Reason:
During initialization of SOLVE:Ops OV/NV, an attempt to define an APPC opset failed.
System Action:
Opset not defined. SOLVE:Ops OV/NV may not run.
User Action:
Contact systems programmer.
Reason:
During initialization of SOLVE:Ops OV/NV, appc links were defined successfully.
P1 and P2 are the lunames for which the links were defined.
System Action:
None.
User Action:
None. (Informational)
Reason:
An error occured when a procedure in SOLVE:Ops OV/NV tried to profile itself for a certain event type.
P1 is the message with the reason the profile command failed.
System Action:
SOLVE:Ops OV/NV transaction fails.
User Action:
Check SOLVE:Ops OV/NV userid Event Distribution Services (EDS) authority. Contact technical support.
Reason:
A SOLVE:Ops OV/NV procedure was unable to send an EDS event because the listener was not there.
System Action:
Topology event is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
The event flow transaction in SOLVE:Ops OV/NV appears to have terminated.
P1 is the remote system id.
System Action:
EventView flow to SOLVE:Ops OV/NV terminates.
User Action:
Check APPC links in SOLVE:Ops OV/NV.
Reason:
The SOLVE:Ops OV/NV EventView message flow was started. (via the $ELSV000 command). This is the flow of raw MVS and SNA message data as SNMP traps.
P1 is the host name of the workstation to which the events are sent.
System Action:
EventView messages should be sent to the workstation as they arise.
User Action:
None. (Informational)
Reason:
The SOLVE:Operations OV/NV EventView message flow was started. The message processor invoked the message exit procedure, P1 , but it does not exist in the COMMANDS library or the procedure name is invalid.
System Action:
The exit is disabled.
User Action:
Ensure that the EventView message exit procedure name specified in the WSPEER parameter group identifies a procedure that is available to the region.
Reason:
An error occurred when defining the SOLVE:Ops OV/NV user ID. P1 is the return code from the call to UAMS. Message EL0702 follows with a description of the error.
System Action:
SOLVE:Ops OV/NV User ID is not defined.
User Action:
Look at the error reason in message EL0702 which follows, and check the USERID parameter in the SOLVE:Ops OV/NV initialization parameters. Check that the user is defined correctly to SOLVE:Operations.
Reason:
This message is the result of a failed attempt to define the SOLVE:Ops OV/NV user id. It follows EL0701, and provides a description of the error reason. See EL0701 for additional information.
System Action:
SOLVE:Ops OV/NV User Id is not defined.
User Action:
See EL0701 message for explanation of user action.
Reason:
As part of SOLVE:Ops OV/NV installation it is necessary to specify the host IP address in the initialization parameters. The IP address parameter is missing and this parameter is mandatory. A new IP address parameter value can be specified while the SOLVE system is running by entering $ELIN07I OPT=ALLOCIP IPADDR=xxx from an OCS or command window.
System Action:
SOLVE:Ops OV/NV will not run.
User Action:
Include the IP address parameter in the SOLVE:Ops OV/NV initialization parameters.
Reason:
As part of SOLVE:Ops OV/NV initialization the IP address parameter was successfully processed. This message is also issued in response to dynamic specification of the IP address parameter from a command or OCS window.
System Action:
SOLVE:Ops OV/NV will use the new IP address in traps it generates.
User Action:
None. (Informational)
Reason:
The SOLVE:Ops OV/NV process which receives events and sends them as traps to the workstation has detected that the appc link it uses has terminated.
P1 is the LU name at the remote end of the APPC link.
System Action:
SOLVE:Ops OV/NV processing terminates completely, but should re-start automatically once the link is available again.
User Action:
Check that the SOLVE:Ops OV/NV communication path (See LUNAME indicated message parameter P1 ) is active.
Reason:
The SOLVE:Ops OV/NV event daemon host end terminated, meaning no traps can be sent to SOLVE:Ops OV/NV. This triggers SOLVE:Ops OV/NV cleanup to enable a re- start. The cause of the error could be an APPC link failing, or an NCL error. Check the log for details.
P1 is the NCLID of the event daemon procedure that failed.
System Action:
SOLVE:Ops OV/NV processing terminates completely, and should re-start if/when communication links are available.
User Action:
Check log for error messages relating to the NCL procedure that terminated, and SOLVE:Ops OV/NV error messages in general.
Reason:
SOLVE:Ops OV/NV processing is terminating completely because the special SOLVE:Director userid has been cancelled.
P1 is the SOLVE:Ops OV/NV user id.
P2 is the host name of the workstation system that SOLVE:Ops OV/NV is connected to.
System Action:
SOLVE:Ops OV/NV processing terminates completely, and should re-start automatically.
User Action:
Wait for SOLVE:Ops OV/NV to re-start. Look at log for messages relating to userid cancellation.
Reason:
SOLVE:Ops OV/NV processing is terminating completely because a system image reload occurred. SOLVE:Ops OV/NV should re-start automatically.
P1 is the host name of the workstation system that SOLVE:Ops OV/NV is connected to.
System Action:
SOLVE:Ops OV/NV processing terminates completely and should re-start automatically.
User Action:
Wait for SOLVE:Ops OV/NV to re-start.
Reason:
This message is displayed in response to a LOGMSG request received from SOLVE:Operations for OpenView/NetView.
System Action:
None.
User Action:
As indicated by the message from SOLVE:Operations for OpenView/NetView.
Reason:
Unexpected data was received on the SOLVE:Ops OV/NV host command APPC transaction.
P1 is what was received.
P2 is what was expected to be received.
System Action:
Host command transaction ends.
User Action:
Retry. Contact systems administrator.
Reason:
An APPC error occurred sending data in the OV/NV host command transaction.
P1 is the RETCODE value after the APPC SEND.
P2 is the ZFDBK value after the APPC SEND.
System Action:
Host command transaction ends.
User Action:
Retry. Check that all OV/NV links/PU's LU's are active. Contact systems administrator.
Reason:
There is a timeout period on the SOLVE:Ops OV/NV host command facility. If no response is received from a command within the timeout period then this message is issued.
System Action:
Host command transaction ends. Command may not have completed.
User Action:
Retry the command. The timeout may have been caused by slow system response times. Check that the command is intended to be a short running command. This command facility is not useful for starting long running background procedures, or commands that display panels.
Reason:
A command was issued against an object or resource, but one of the operands was missing or invalid.
P1 is the missing or invalid operand.
System Action:
The host command transaction ends.
User Action:
Correct the command, and retry.
Reason:
The command requested is not supported by this command facility.
System Action:
The command is not issued.
User Action:
Ensure that the spelling and syntax of the command is correct.
Reason:
A vartable allocation error occurred while the region was trying to run the remote command facility.
System Action:
The command does not run.
User Action:
Contact your systems programmer. The error may be because of storage shortage in the region.
Reason:
When issuing a command with OPT=LISTCMD specified, it is invalid to also specify either the COMMAND or OBJID operands.
System Action:
The command is not issued.
User Action:
For OPT=LISTCMD, do not specify any other operands.
Reason:
The P1 command is invalid for an SNA resource.
System Action:
The command is not issued.
User Action:
Use a command that is applicable for SNA resources.
Reason:
The NEL command is not supported by this command processor.
System Action:
The command is not issued.
User Action:
None.
Reason:
An error occurred while manipulating an NCL VARTABLE.
System Action:
None.
User Action:
Contact your local support representative.
Reason:
The command was processed successfully.
System Action:
None.
User Action:
None.
Reason:
The system image that manages this SNA group resource is not currently active/available.
P1 is the SNA group name.
P2 is the System Image name.
P3 is the System Image version.
System Action:
SOLVE:Ops OV/NV processing not performed for this SNA group.
User Action:
If due to a remote region not being available, rectify and re-start SOLVE:Ops OV/NV processing.
Reason:
A SOLVE:Ops OV/NV procedure was unable to send an EDS event because the listener was not there.
System Action:
SNA resource event is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
An error occurred when SOLVE:Ops OV/NV attempted to retrieve information about an SNA resource.
P1 is the name of the SNA resource.
System Action:
SNA resource information is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
The maximum domain limit managable by SOLVE:Ops OV/NV was exceeded.
P1 is the maximum number of domains.
System Action:
Resources in domains above the limit not monitored by SOLVE:Ops OV/NV.
User Action:
Contact technical support.
Reason:
An attempt to start the process which sends remote SNA Group status change events for SOLVE:Operations for OV/NV failed.
P1 is the return code from the APPC start request.
P2 is the sysmsg returned from the APPC start request.
System Action:
Remote SNA Group status change events are not forwarded to SOLVE:Operations for NV/OV.
User Action:
None.
Reason:
An attempt to attach a process to monitor SNA resource status change events for a remotely managed SNA group resource failed.
P1 is the name of the SNA group that is on the remote system.
P2 is the ACB name of the remote SOLVE:Operations region.
P3 and P4 are the APPC return code and feedback from the attach.
System Action:
Status change events are not forwarded to SOLVE:Ops OV/NV for resources that are part of this SNA resource group. The status events for the group itself are still sent.
User Action:
Check that the remote system is running. Check the status of links to the remote system by looking at the internal SOLVE:Operations resource that represents the connection to this system. Use the APPC return code and feedback information to determine the cause of the APPC error.
Reason:
An APPC receive to get SNA resource status change events for a remote SNA group failed.
P1 is the ACB name of the remote SOLVE:Operations region.
P2 and P3 are the APPC return code and feedback from the attach.
System Action:
Status change events are not forwarded to SOLVE:Ops OV/NV for resources that are part of this SNA resource group. The status events for the group itself are still sent.
User Action:
Check that the remote system is running. Check the status of links to the remote system by looking at the internal SOLVE:Operations resource that represents the connection to this system. Use the APPC return code and feedback information to determine the cause of the APPC error.
Reason:
Attempt to start a server to process requests for remote SNA group events from a linked SOLVE:Operations region failed.
P1 is the ACB name of the remote region.
P2 is the return code from the attach request.
P3 is the feedback from the attach request.
System Action:
Remote SNA Group status change events are not forwarded to SOLVE:Operations for NV/OV.
User Action:
Check that the maximum number of parallel APPC sessions between the two systems has not been exceeded by issuing a SHOW LINK MODE command.
Reason:
An attempt to start SNMP trap flow to SOLVE:Ops OV/NV from SOLVE:Operations using TCP/IP failed on a call to TCP/IP functions.
P1 IS THE RETURN CODE FROM THE TCP/IP CALL.
P2 IS THE FEEBACK CODE FROM THE TCP/IP CALL.
P3 IS THE SOCKET ERROR, P4 IS THE SOCKET COMMAND
System Action:
No SNMP traps flow to SOLVE:Ops OV/NV.
User Action:
Contact technical support.
Reason:
An attempt to start SNMP trap flow to SOLVE:Ops OV/NV from SOLVE:Operations using TCP/IP failed because no port number was specified for use by the connection.
System Action:
No SNMP traps flow to SOLVE:Ops OV/NV.
User Action:
Update the WSPEER customisation parameter group in SOLVE:Operations to specify a TCP/IP port number.
Reason:
SOLVE:Operations OV/NV didn't successfully start its TCP/IP connections, because TCP/IP support in the product region is not active, or failed to start.
System Action:
SOLVE:Operations OV/NV TCP/IP connections are not started.
User Action:
Check the status of TCP/IP using the SHOW TCPIP command. Check that the TCP/IP dataset prefix specified in the $RM WSPEER customization parameters in SOLVE:Operations is correct.
Reason:
An attempt to start SNMP host command flow to SOLVE:Ops OV/NV from SOLVE:Operations using TCP/IP failed on a call to TCP/IP functions.
P1 IS THE RETURN CODE FROM THE TCP/IP CALL.
P2 IS THE FEEBACK CODE FROM THE TCP/IP CALL.
P3 IS THE SOCKET ERROR, P4 IS THE SOCKET COMMAND
System Action:
No host commands issued from SOLVE:Commander.
User Action:
Use SHOW TCPIP command to check the status of TCP/IP. Check that the correct TCP/IP dataset prefix was specified in the $RM WSPEER customisation parameters in SOLVE:Operations. Check that SOLVE:Commander port numbers are correct and not being used by anything.
Reason:
An attempt by SOLVE:Ops OV/NV to issue a host command on SOLVE:Operations using TCP/IP failed because no port number was specified for use by the connection.
System Action:
No host commands over TCP/IP issued by SOLVE:Ops OV/NV.
User Action:
Update the WSPEER customisation parameter group in SOLVE:Operations to specify a TCP/IP port number.
Reason:
SOLVE:Operations OV/NV didn't successfully start its TCP/IP connections, because TCP/IP support is not active, or failed to start.
System Action:
SOLVE:Operations OV/NV TCP/IP connections are not started.
User Action:
Check the status of TCP/IP using the SHOW TCPIP command. Check that the TCP/IP dataset prefix specified in the $RM WSPEER customization parameters in SOLVE:Operations is correct.
Reason:
A logon from SOLVE:Ops OV/NV via TCP/IP was succesful.
System Action:
None.
User Action:
None.
Reason:
A logon from SOLVE:Ops OV/NV via TCP/IP failed for unknown reasons.
System Action:
Command fails.
User Action:
Contact technical support.
Reason:
A logon from SOLVE:Ops OV/NV failed because the users password has expired.
System Action:
Command fails.
User Action:
Enter new password in dialog box on the workstation.
Reason:
A logon from SOLVE:Ops OV/NV failed because the user is a new user, and must supply a new password.
System Action:
Command fails.
User Action:
Enter new password in dialog box.
Reason:
A logon from SOLVE:Ops OV/NV failed because an invalid password was entered.
System Action:
Command fails.
User Action:
Re-enter correct password.
Reason:
A logon from SOLVE:Ops OV/NV failed because the user is not defined.
System Action:
Command fails.
User Action:
Enter a valid userid and password.
Reason:
A logon from SOLVE:Ops OV/NV failed because user verification failed.
System Action:
Command fails.
User Action:
Check user ID and password are valid.
Reason:
A logon from SOLVE:Ops OV/NV failed because the security exit rejected the userid and password.
System Action:
Command fails.
User Action:
Enter valid userid and password.
Reason:
A host command transaction from SOLVE:Ops OV/NV to SOLVE:Operations using TCP/IP failed on a call to TCP/IP functions.
System Action:
Command fails.
User Action:
Check that TCPIP is active using the SHOW TCPIP command.
Reason:
A logon from SOLVE:Ops OV/NV failed because the new password sent was longer than the 8 character maximum password length.
System Action:
Command fails.
User Action:
Re-enter a shorter new password.
Reason:
An attempt to change a users password on the host command transaction over TCP/IP failed.
P1 is the return code from the security check call.
P2 is the feedback code from the security check call.
P3 is the message set by the security check call (may be null).
System Action:
Command fails.
User Action:
Contact systems programmer to check password/user details on the region on which the command was being issued.
Reason:
Internal message used to indicate to host command processing using TCP/IP that all command results have been returned.
System Action:
Command results sent to workstation over TCP/IP connection.
User Action:
None. Internal message not seen by user.
Reason:
A SOLVE:Ops OV/NV SNA Group display has been terminated, and the backend server NCL process for the utility is being terminated.
System Action:
Backend Server NCL process terminates normally.
User Action:
None.
Reason:
The system image that manages this SNA group resource is not currently active/available.
P1 is the SNA group name.
P2 is the System Image name.
P3 is the System Image version.
System Action:
SOLVE:Ops OV/NV processing not performed for this SNA group.
User Action:
If due to a remote region not being available, rectify and re-start SOLVE:Ops OV/NV processing.
Reason:
An error occurred when SOLVE:Ops OV/NV attempted to retrieve information about an SNA resource.
P1 is the name of the SNA resource.
System Action:
SNA resource information is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
The maximum domain limit manageable by SOLVE:Ops OV/NV was exceeded.
P1 is the maximum number of domains.
System Action:
Resources in domains above the limit not monitored by SOLVE:Ops OV/NV.
User Action:
Contact technical support.
Reason:
Internal message used to indicate to calling procedure that output from SNA resource discovery command is complete.
System Action:
Procedure that requested SNA Resource discovery terminates.
User Action:
None.
Reason:
Internal message used to indicate to calling procedure that output from SNA resource discovery command has started.
P1 is the NCLID of the NCL process that issued this message.
System Action:
None.
User Action:
None.
Reason:
The process that listens for changes to SNA resources for the SOLVE:Ops OV/NV SNA Group display utility and forwards them as SNMP traps has terminated, because the SNMP trap sending process is not active.
System Action:
Back end for the SNA Group display utility terminates.
User Action:
Determine why the connection to SOLVE:Ops OV/NV was terminated, and if necessary attempt to restart SOLVE:Ops OV/NV on the workstation.
Reason:
The process that does discovery for the SOLVE:Ops OV/NV SNA Group display and monitoring utility could not find any resources within the SNA Group that was requested.
System Action:
Back end for the SNA Group display utility terminates.
User Action:
Check that the definition for the requested SNA Group is correct, and that the group contains resources.
Reason:
The process that does discovery for the SOLVE:Ops OV/NV SNA Group display and monitoring utility could not find the SNA Group that was requested.
System Action:
Back end for the SNA Group display utility terminates.
User Action:
Check that the SNA Group requested is defined on this system. Check SOLVE:Ops OV/NV configuration on Unix. Check when SOLVE:Ops OV/NV on Unix was last refreshed, and that the active system image is the same as the one that was active when SOLVE:Ops OV/NV initialized on Unix.
Reason:
The SNA Group that was being retrieved resides on a remote SOLVE:Operations region to the one SOLVE:Operations for OV/NV is connected to, and an attempt to retrieve its resources failed, either because the group does not exist, or contains no resources.
p1 is the name of the SNA Group.
System Action:
Back end for the SNA Group display utility terminates.
User Action:
Check that the SNA Group requested is defined on the SOLVE:Operations region, and does contain resources.
Reason:
The procedure which sends SNA Group status change events to a remote system failed to start the process which receives those events on the remote system.
P1 is the remote system that was to receive the evnets.
P2 and P3 are the APPC return code and feedback respectively.
System Action:
SNA Group status change events are not forwarded to the remote system, and thus not forwarded to the SOLVE:Operations for OV/NV that is connected to the remote system.
User Action:
Check that the remote system is running. Check the status of links to the remote system by looking at the internal SOLVE:Operations resource that represents the connection to this system. Use the APPC return code and feedback information to determine the cause of the APPC error.
Reason:
An error occurred sending an SNA Group status change event to a remote SOLVE:Operations region.
p1 is the name of the remote region.
P2 is the return code from the APPC send.
P3 is the feedback code.
System Action:
SNA Group status change events are not forwarded to the remote system, and thus not forwarded to the SOLVE:Operations for OV/NV that is connected to the remote system.
User Action:
Check that the remote system is running. Check the status of links to the remote system by looking at the internal SOLVE:Operations resource that represents the connection to this system. Use the APPC return code and feedback information to determine the cause of the APPC error.
Reason:
An attempt to receive an SNA Group status change event from a remote SOLVE:Operations region failed.
P1 is the APPC return code.
P2 is the feedback code.
System Action:
The receiver terminates. SNA Group status change events are no longer received from the remote region, and thus not forwarded to the SOLVE:Operations for OV/NV connected to the local region.
User Action:
Check that the remote system is running. Check the status of links to the remote system by looking at the internal SOLVE:Operations resource that represents the connection to this system. Use the APPC return code and feedback information to determine the cause of the APPC error.
Reason:
A logon request from SOLVE:Operations for OV/NV could not be processed because the security level used is not supported in this region.
System Action:
The command is not processed.
User Action:
Either change the security level used in SOLVE:Operations for OV/NV by updating the $SOLVE_DIR/etc/hcmd.conf file, or apply the appropriate APAR (if available) to the current region so that it supports the security level that is being used.
Reason:
A logon request from a SOLVE:Link or SOLVE:Operations for OV/NV/ITO workstation was flagged as an encrypted string, but was not in the expected format.
System Action:
The command is not processed.
User Action:
Contact your local support representative.
Reason:
The panel, P1, you have chosen to be displayed as a graphical monitor is currently being updated by the user identified by P2.
System Action:
Request rejected.
User Action:
Use another panel or wait until the user currently updating the panel is finished with it.
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact your systems administrator.
Reason:
A SOLVE:Ops OV/NV procedure was unable to send an EDS event because the listener for the server P1 was not there.
System Action:
Topology event is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
The Icon view procedure is started and the ENABLE ICON VIEW flag is set to NO. This could occur if someone manually starts the procedure outside the WSPEER customisation panel.
System Action:
The procedure stops.
User Action:
Use the WSPEER panel to change the ENABLE ICON VIEW flag value and press the ACtion Key.
Reason:
Allocation for the vartable named P3 with scope P4 of type P2 was unsuccessful. FDBK P1 was returned.
System Action:
The SOON Icon Manager terminates.
User Action:
Resolve the reason for the vartable allocation failure. This may be that the region is short of storage and it may be necessary to restart the region with more storage.
Reason:
A vartable error occurred while performing function(P1) on vartable(P2). The FDBK was P3 and the entry key was P4.
System Action:
Request rejected.
User Action:
Contact your systems administrator.
Reason:
A SOLVE:Ops OV/NV procedure was unable to send an EDS event because the listener for the server P1 was not there.
System Action:
Topology event is not sent.
User Action:
Check whether any other procedures have ended abnormally.
Reason:
A panel path has been invoked in which the ICON (Resource Group) known as P1 points to the PANEL P2 which has either been referenced earlier in the path or which contains the ICON (Resource Group) identified by P1
System Action:
Entry to the Graphical Monitor is denied as this sort of recursive path leads to excessive CPU usage and degradation of performance.
User Action:
Locate where the recursion occurs in the path and correct the situation and retry.
Reason:
The resource P1 has too many parents. The parent resource P2 is not stored and it will be ignored.
System Action:
The parent is ignored.
User Action:
Verify the Panel Icon definition. Review the resource groups filters.
Reason:
The VTAM applid P1 has already been specified for field P2. The NetSpy Application ID must be unique.
System Action:
Field is set in error.
User Action:
Specify a different applid.
Reason:
The NetSpy Alert Processing is disabled.
System Action:
NetSpy Alerts processing is not activated.
User Action:
Controls for the NetSpy Alerts processing is managed via the NETSPYLINKS Initialization Parameters.
From any panel, enter /PARMS and check the setting of the $ES NETSPYLINKS parameter group. Ensure that Enable NetSpy Alert
Processing is set correctly.
Reason:
The message displays a NetSpy API trace record. P1 is the API NCL ID
P2 is the trace ID, and P3 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The required P1 parameter is missing or has an invalid value.
System Action:
The API to the NetSpy region returns the error message to the caller.
User Action:
Add the parameter or correct its value as required.
Reason:
The NetSpy API detected that the connection to NetSpy is not running. This situation may indicate that the connection to NetSpy failed, NetSpy is not active, or the NETSPYLINKS Customizer parameter group has not been activated.
If this message is issued while saving a NetSpy Monitor definition and activating the Monitor, it confirms the saving of the Monitor definition.
System Action:
The API returns the error message to the caller. In the case of the NetSpy Monitor definition, the Monitor definition panel is retained.
User Action:
Ensure that there is at least one NetSpy connected, and that the NetMaster to NetSpy interface is started and in the RUNNING state. You may need to go to /PARMS and activate the $NETSPYLINKS parameter group. If the message is received whilst saving the Monitor definition, Cancel (PF12) should be used to exit the panel, unless the updates to the definition, like the NetSpy link name, are to be retained.
Reason:
A DEFINE request to the NetSpy Interface failed.
P1 is the return code.
P2 is the feedback code (FDBK).
If shown, P3 is a message that explains the error (SYSMSG).
The following lists possible combinations of RC/FDBK:
4/01 - Partial results received
8/81 - Duplicate Internal connection ID
8/82 - Connection Define failed, see SYSMSG
8/83 - Internal connection ID not found
8/84 - Outstanding asynchronous requests on this link, see SYSMSG
8/85 - No NetSpy(s) to send the request to
8/86 - Monitor command without exact NetSpy Filter
8/87 - Send error, see SYSMSG
8/88 - Storage shortage for SEND results
8/89 - MDS error on send results
System Action:
The NetSpy API returns the error message to the caller.
User Action:
Depending on the RC/FDBK combination and SMSG presence, the following actions are recommended:
4/01 - The amount of returned data is too big to be handled by the interface. Try to limit the scope of the request and resubmit your request. Check if there is a serious virtual storage shortage in the NetMaster, NetSpy or the Operating System, resolve it and resubmit the request.
8/81 - Restart the NetSpy link, if the problem persists, contact Technical Support.
8/82 - Try to address the problem as per SMSG indication (start the NetSpy link for example). If unable to resolve the problem, contact Technical Support.
8/83 - Retry the request, restart the NetSpy link, if problem persists, contact Technical Support.
8/84 - Retry the request, restart the NetSpy link, if problem persists, contact Technical Support.
8/85 - Either no NetSpy connection present or the request asks for the data which is not currently collected by any of the connected NetSpys (for example request for NCP data and no NetSpy collecting it is connected/available). Modify your request or make sure that requested data is collected by one of the available NetSpys.
8/86 - Verify if your request satisfies NetSpy Monitor command, mofify your request accordingly. If still receiving the error, contact Technical Support.
8/87 - Try to address the problem as per SMSG indication (address the link time-outs, for example). If unable to resolve the problem, contact Technical Support.
8/88 - Check if there is a virtual storage shortage in the NetMaster, NetSpy or the Operating System, resolve it and resubmit the request.
8/89 - Internal error, contact Technical Support.
Reason:
A SEND request to the NetSpy Interface failed. See ESNS0003 message for details.
P1 is the return code.
P2 is the feedback code (FDBK). If shown, P3 is a message that explains the error (SYSMSG).
System Action:
The NetSpy API returns the error message to the caller.
User Action:
See ESNS0003 message for details.
Reason:
A DELETE request to the NetSpy Interface failed. See ESNS0003 message for details.
P1 is the return code.
P2 is the feedback code (FDBK). If shown, P3 is a message that explains the error (SYSMSG).
The situation may be caused by the NetSpy link going down since the command was defined.
System Action:
The NetSpy API returns the error message to the caller.
User Action:
See ESNS0003 message for details.
Reason:
The NetSpy Interface request returned code 0, but the reply code was not OK. P1 is the received reply. Possible causes include:
- In a multiple NetSpy configuration, the request was accepted but not all requests were satisfied.
- None of the linked NetSpy regions are configured to collect the data of the type requested. For example, the NetSpy dedicated to collecting NCP data is not connected (directly or indirectly) to the NetMaster link.
System Action:
In the case of some requests being satisfied, the NetSpy API proceeds to find out if one of interfaces provided the answers requested.
User Action:
Verify the status of the NetMaster to NetSpy links. Check if all required resources are collected by at least one of the NetSpy regions.
Reason:
A NetSpy synchronous reply was received, but it contained no data. Either there was no data for a given resource or data was not collected yet (normally at the beginning of the collection interval of 15 minutes).
System Action:
The NetSpy API receives the reply, which does not contain the expected data or NODATA condition was returned by NetSpy.
User Action:
Repeat the request later in the interval. Ensure that:
- The specified request produces output from an interactive NetSpy session
- The specified resources are known to NetSpy
- The NetSpy collecting data for a specified resource is linked to NetMaster
- There are no errors listed on the NetSpy Audit Log.
If the region is still unable to receive data, contact Technical Support.
Reason:
The command is either not supported by the API to NetSpy or is not a valid NetSpy command. The current implementation of NetMaster to NetSpy interface supports the following synchronous commands: DA, DAR, DN, DNETH, DNFR, DNLIST, DNS, DNTIC3, DNTR, DNX25, DT, DTA, DTR, and DV . The supported asynchronous command is MONITOR .
System Action:
The NetSpy API returns the error message to the caller.
User Action:
Ensure that the command is a valid NetSpy command and is supported by the API and the low level interface.
Reason:
The NetSpy synchronous request returned data in multiple, repeated units, but none of those matches the specific request. For example, DV returns information on multiple TPs but there is no data for the required one.
System Action:
The NetSpy API returns the error message to the caller.
User Action:
Check the logic of the request, pattern, and scope. If errors exist, change and resubmit the request. Verify that the required resource is known to the NetSpy regions linked to the NetMaster Interface.
Reason:
An attempt to obtain exclusive lock for the monitor list vartable failed. P1 is the return code, and P2 is the feedback code.
The error might be because of simultaneous requests for vartable access. The condition, though unlikely, might occur during region initialization.
System Action:
The NetSpy API terminates the update request.
User Action:
Check that the region completed initialization. Check for indications of virtual memory shortages. If the error persists, contact Technical Support.
Reason:
An attempt to allocate, add, or update the table that contains the monitors list failed. P1 is the return code, and P2 is feedback code.
System Action:
The NetSpy API terminates the request.
User Action:
Retry the operation. If the error persists, contact Technical Support.
Reason:
A DEFINE request to the NetSpy Interface returned a 0 return code, but the returned definition ID (&SYS.NETSPY.ID) is null.
System Action:
The NetSpy API returns the error message to the caller.
User Action:
Repeat the operation. If the error persists, contact Technical Support.
Reason:
The response to an asynchronous request did not contain data that matched the request. P1 is name of the resource for which data was requested. Unspecified is reported when no resource (generic request) was specified.
System Action:
The NetSpy API returns the error message to the caller.
User Action:
Verify the logic of the request, scope, and pattern. Verify that the resource is known to the NetSpy region. If the error persists, contact Technical Support.
Reason:
The process (NCL ID P1 ) received a request to add a monitor. The NCLID is used to communicate with the receiver which, after having the monitor defined, switches to the listening mode.
System Action:
The NetSpy API confirms receiving the request. The message is sent to the requester that provides the NCL ID of the receiver.
User Action:
None.
Reason:
A NetSpy Interface request for the monitor definition was sent to the NetSpy region. P1 is the definition and P2 is the NCL ID of the listener. The NetSpy API entered the alert listening mode and all requests are sent through the INTREAD interface.
The request has not been confirmed by NetSpy. It is possible (for example, under severe virtual memory shortage) for the request to be received but not acted on.
System Action:
The NetSpy API confirms sending the request and enters alert listening mode.
User Action:
To ensure that the monitor is defined, go to the NetSpy region to verify that the monitor exists (action 7.1.3). There may be some delay before the monitor appears on the display (up to the monitoring interval value).
Reason:
The synchronous part of the API received a request to delete a monitor from the process identified by P1 . The request was verified to be for a monitor definition monitored by this listener.
System Action:
The NetSpy API confirms receiving the request. The request will be sent to the NetSpy region.
User Action:
None.
Reason:
A request to delete a monitor was was sent to the NetSpy region. The definition is identified by P1 .
System Action:
The NetSpy API confirms sending the request. The request is sent, and the list of defined monitors is updated. The API processing terminates.
User Action:
None.
Reason:
The Netspy API detected that there are no Netspy connections defined in the NETSPYLINKS Customizer paramameter group.
System Action:
The NetSpy API listener notifies the NetSpy Alert Processor, updates the list of defined monitors, and terminates.
User Action:
Ensure that the NetSpy region is running and the NetMaster-to-NetSpy interface is defined and in the RUNNING state. You may need to go to /PARMS and reactivate the $ES NETSPYLINKS parameters. Redefine the monitor after the link has restarted.
Reason:
The asynchronous part (listener) of the NetSpy API failed while interpreting an incoming alert event.
P1 is the return code.
P2 is the map name.
P3 is the component name.
System Action:
The listener discards the received data and continues to listen for events.
User Action:
If the error persists, contact Technical Support.
Reason:
The asynchronous part (listener) of the NetSpy API detected that the NetSpy Alert Processor was not active. The NetSpy Alert Processor was started. P1 is the process NCL ID.
This message indicated that the Alert Processor, which should have been started automatically, was not started or failed.
System Action:
The NetSpy API started the necessary processor before entering the listening mode.
User Action:
None.
Reason:
The asynchroneous part (listener) of the NetSpy Interface detected that the NetSpy Alert Processor was already active. P1 is the process NCL ID.
System Action:
The listener reports that the processor is already active.
User Action:
None.
Reason:
The API listener received a request to delete a monitor through the INTREAD interface from the P1 process. The request was verified to be for a monitor definition monitored by this listener.
System Action:
The NetSpy API listener confirms receiving the request. The request will be sent to the NetSpy region.
User Action:
None.
Reason:
The P1 NetSpy API listener was stopped as the result of a request to delete the monitor.
System Action:
The NetSpy API reports stopping the listening process for the monitor definition. The list of defined monitors is updated, and the API is terminated.
User Action:
None.
Reason:
The NetSpy API listener (NCL ID P1 ) was unable to receive alerts and other notifications because of congestion in the INTREAD queue. Possible causes are as follows:
- Receipt of alerts was constrained by the virtual memory.
- Alert processing was running with a priority much lower than the alert producing process, and the number of alerts were excessive. This might indicate a logical error in the monitor definition (for example, monitoring all applications with an average host response time greater than zero).
System Action:
The API listener terminates.
User Action:
Check for system congestion and the monitoring criteria. Compare the dispatching priority of the alert processing tasks with that of the alert producing tasks.
Reason:
An request was made to define a monitor for a resource that was unknown to any of the NetSpy regions linked to this NetMaster region. P1 is the resource name.
System Action:
The request is rejected.
User Action:
Check the resource name. If it is correct, check that the links to the NetSpy regions are active. Check if the type of resource is defined to any of the linked agents.
Reason:
The asynchronous part (listener) of the NetSpy API received EDS notification that the NetSpy link servicing the monitor was stopped.
p1 is link name.
System Action:
The NetSpy API listener notifies the NetSpy Alert Processor, updates the list of defined monitors, and terminates.
User Action:
Restart the link, and reactivate the monitor.
Reason:
You were adding or deleting a NetSpy monitor. The request timed out before an Event Distribution Services (EDS) notification was received by the asynchronous part of the NetSpy API. P1 identifies the link to the NetSpy region where the monitor was to be added or deleted.
System Action:
The NetSpy API issues the message.
User Action:
Check for system congestion. Try the action later.
Reason:
An attempt to define a new monitor to NetSpy was rejected. P2 provides the reason.
DUP indicates that a duplicate monitor name exists. It may happen in situations where the region loses track of the definitions, while NetSpy still maintains the definition.
System Action:
None.
User Action:
Use the ADD, COPY, or UPDATE function to create a new definition.
Reason:
A NetSpy API Listener start command was issued for P1 on Netspy P2 as a result of the activate command.
System Action:
The NetSpy API reports stopping the listening process for the monitor definition. The list of defined monitors is updated, and the API is terminated.
User Action:
None.
Reason:
A NetSpy API Listener start command was issued for P1 on NetSpy P2 as a result of the activate command. Due to a failure, the Listener was not activated.
System Action:
The NetSpy API reports stopping the listening process for the monitor definition. The list of defined monitors is updated, and the API is terminated.
User Action:
None.
Reason:
While formatting the results returned by NetSpy, the number of data lines returned has exceeded the maximum value indicated. The displayed data is incomplete.
System Action:
None.
User Action:
Modify your request by refining your selection criteria.
Reason:
An attempt to update a monitor was rejected because the monitor is active.
System Action:
None.
User Action:
Inactivate the monitor and then request an update.
Reason:
A command was sent to the operator command queue, and confirmation was received.
System Action:
The NetMaster command environment executes the command.
User Action:
None.
Reason:
A command failed. P1 is the message related to the failure. Possible causes are as follows:
- Logical errors were detected during the execution of the NSPCONN command (for example, starting an active link or stopping an inactive one).
- The list of NetSpy links was not refreshed for a long time before executing the command, and the command was sent from the OCS environment before.
System Action:
The command failed, and message is displayed.
User Action:
Review the P1 message, and take appropriate correcting measures. Refresh (PF6) the list of links before trying the command again.
Reason:
The command was sent to the operating system for execution.
System Action:
The NetMaster command environment confirms sending the command to the operating system.
User Action:
None.
Reason:
The response to a command did not arrive within a time limit.
System Action:
Waiting for the response is terminated, and the command failed.
User Action:
Check that the system is responding to interactive requests in less than 60 seconds. Try to repeat the operation.
Reason:
A request for details on the link to a NetSpy region failed to return the expected information. P1 is the APPL to which the command was sent.
System Action:
The message is displayed, and the list of links is updated to reflect the condition.
User Action:
Refresh the link display to ensure that the link status has not changed since the last time you used the command line interface. At the command line interface, enter SHOW NETSPY to verify the status of the link and
D ID=P1 to retrieve the required information.
Reason:
An attempt was made to stop or modify a link for which the job name for the NetSpy region was unknown. Possible causes are as follows:
- Link is down.
- NetSpy was terminated, but the link status was not refreshed.
System Action:
The action will not be performed.
User Action:
Refresh the list. Ensure that the STC field is not blank or ***NA***. Repeat the action.
Reason:
The command required at least one argument, but none were specified.
System Action:
The command is not executed.
User Action:
Retry the command with the required argument(s).
Reason:
Selection table driver returned non zero return code P1 accompanied by sysmsg P2
System Action:
None.
User Action:
If it is 'VM0010 Value not selected from list' make sure to make the selection. If the problem persists, contact Technical Support.
Reason:
You caneled the action.
System Action:
You are returned to the list of NetSpy connections.
User Action:
None.
Reason:
You did not have authority to execute the command.
System Action:
The operation is rejected.
User Action:
Ensure that you have authority to perform the required action.
Reason:
The region does not support the P1 command. The supported commands are DA, DAR, DN, DNETH, DNFR, DNLIST, DNS, DNTIC3, DNTR, DNX25, DT, DTA, DTR, DV, and MONITOR.
System Action:
The command is not processed.
User Action:
Ensure that the command is supported. If you want to issue an unsupported command, enter the =SP path to access the NetSpy region and issue the command there.
Reason:
You entered P1 to select an item, but the value was not a number. The value must be a number that corresponds to the item you want to select.
System Action:
The selection is rejected.
User Action:
Enter the number that corresponds to the item you want to select.
Reason:
The value supplied for the P1 field is incorrect.
If P1 is Nodename or LUname , the value must be:
- A 1-8 character non-qualified name (for example, TERM01)
- A network-qualified name in the form netid.node , where the netid and node parts are each 1-8 character values separated by a full stop (period) without spaces (for example, NET01.TERM01). The netid value can also be expressed as an asterisk (*).
If P1 is Mode , the value can be INTERVAL, SUMMARY, or DELTA. The default is INTERVAL.
If P1 is the LU62 Selection field, the value can be ONLYLU62, EXCLU62, or blank.
If P1 is Scope , the value can be ONLY or ALL. The default is ALL. ? will show the panel with all possible scopes fpr the selected command.
If P1 is the SA , VR ,or TP field, the value must be a valid number.
If P1 is the Threshold Variable field, enter ? to list the valid values.
If P1 is the Threshold Value field, the value must be a number that is compatible with the defined threshold.
System Action:
None.
User Action:
Correct the value, and retry.
Reason:
You caneled the action.
System Action:
You are returned to the command arguments menu.
User Action:
None.
Reason:
The Listener for the Monitor, P1 failed to obtain the lock necessary to start.
System Action:
The NetSpy API reports stopping the listening process for the monitor definition. The list of defined monitors is updated, and the API is terminated.
User Action:
None.
Reason:
The API listener was not running. P1 is the last known NCL ID of the listener.
System Action:
The NetSpy Monitor Manager will not send requests to the listener. The list of defined monitors is refreshed to indicate the condition.
User Action:
If the region was restarted (recreating the list of monitors), it might indicate that the monitor requires activation. If the listener terminated abnormally without valid reason, please contact Technical Support.
Reason:
The Monitor Manager detected that the NetMaster to NetSpy Interface was not in the RUNNING state. P1 is the detected state. This situation may indicate that the link failed, NetSpy failed or the NETSPYLINKS parameter group was not activated.
System Action:
The list of monitors is updated.
User Action:
Ensure that NetSpy is running, and the NetMaster to NetSpy interface is started and in the RUNNING state. You may need to go to /PARMS and activate the $NETSPYLINKS parameters. Redefine the monitor after the link has restarted.
Reason:
A monitor definition was sent to the NetSpy Interface, but the confirmation was not received within time limit.
System Action:
The waiting is terminated. The monitor definition table might not have been updated by the API with the latest monitor definition.
User Action:
Ensure that NetSpy is responding to interactive requests in less than 120 seconds. Ensure that the monitor can be displayed from the NetSpy region. If you cannot resolve the problem, contact Technical Support.
Reason:
The reply to a request to the NetSpy API did not arrive within time limit. The API might not be active.
System Action:
The waiting is terminated, and the request fails.
User Action:
Ensure that the NetSpy region is responding to interactive requests in less than 60 seconds. Try to repeat the operation. Ensure that there are no abnormal procedure terminations. If the problem persists, contact Technical Support.
Reason:
A request was made to a monitor ( P1 ), but the received reply was for a different monitor ( P2 ).
System Action:
The request fails.
User Action:
Retry the request. If the problem persists, contact Technical Support.
Reason:
An attempt to allocate, add, or update the table that contains the list of monitors, has failed.
P1 is the return code
P2 is feedback code
P3 is a message that describes the error
System Action:
The action fails.
User Action:
Retry the operation. If the error persists, contact Technical Support.
Reason:
An error occurred while the internal table that held the list of monitors was being read. P1 is the feedback code.
System Action:
The action fails.
User Action:
Look out for abnormal situations (for example, virtual memory shortage) in the region. If the error persists, contact Technical Support.
Reason:
The Monitor Manager was called for the P1 resource but discovered that no monitors were defined for the resource.
System Action:
An empty list is presented.
User Action:
If you want to add a monitor, press F4 (Add) to go to the monitor definition panel.
Reason:
You tried to activate an active monitor. P1 is the NCL ID of the monitor listener.
System Action:
The action is rejected.
User Action:
Press F6 to refresh the list of monitors. To make sure, find out its status in the NetSpy region directly.
Reason:
A monitor definition was sent to the API, but the response was not received in the specified time.
System Action:
The waiting is terminated. The monitor definition table might not have been updated by the NetSpy API with the latest monitor definition.
User Action:
Ensure that NetSpy is responding to interactive requests in less than 120 seconds. Ensure that the monitor is visible from NetSpy. Check for system congestion.
Reason:
An error occured while the internal table that held the list of monitor definitions was being read. P1 is the system feedback code.
System Action:
The action fails.
User Action:
Look out for abnormal situations (for example, virtual memory shortage) in the region. If the error persists, contact Technical Support.
Reason:
A request to delete a monitor timed out.
System Action:
The waiting for confirmation is terminated. The monitor definition table might not have been updated by the NetSpy API with the latest monitor definition.
User Action:
Ensure that NetSpy is responding to interactive requests in less than 120 seconds. Ensure that the monitor is visible from NetSpy. If the problem persists, contact Technical Support.
Reason:
The value supplied for the P1 field was incorrect.
If P1 is Resource Name , the value must be:
- A 1-8 character non-qualified name (for example, TERM01)
- A network-qualified name in the form netid.node , where the netid and node parts are each 1-8 character values separated by a full stop (period) without spaces (for example, NET01.TERM01). The netid value can also be expressed as an asterisk (*), or as a name mask containing the asterisk (*) or the question mark (?) in any place of the mask.
- A Virtual Route definition starting from VR= . Optional Subarea (SA) and Transmission Priority (TP) can be specified as well.
If P1 is Monitor Class , the value can be VTAM or NCP.
If P1 is Resource Type , enter ? to list the valid values.
If P1 is Match Type , the value can be ALL or ANY. The default is ALL.
If P1 is Monitor Interval , the value is a number in seconds. The minimum value is 30.
If P1 is LU62 Selection , the value can be ONLYLU62, EXCLU62, or blank.
If P1 is Monitor Title , the value must not contain quotation marks.
If P1 is the Threshold Variable field, enter ? to list the valid values.
If P1 is the Threshold Relation field, the value can be GT, LT, <, or >.
If P1 is the Threshold Value field, the value is a number that is compatible with the defined threshold.
System Action:
None.
User Action:
Correct the value, and retry.
Reason:
The message displays a NetSpy Alert Events receiver trace record.
P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 .
System Action:
None.
User Action:
Contact your System Administrator.
Reason:
A copy of the NetSpy Alert Events receiver (EPS) procedure is already active on this system.
P1 is the NCL Id and the EPS Receiver Id.
System Action:
A new copy of the procedure is not started.
User Action:
Check the activity log to search for previous ESNS25* messages which would indicate when the receiver was started.
Reason:
The events receiver failed when issuing an EPS request.
P1 is the type of EPS request (for example, CONNECT).
P2 is the return code.
P3 is the error number.
P4 is the reason (for example, EPS UNAVAILABLE).
If possible, recovery is attempted as indicated by the next message (see also ESNS2504, ESNS2505, or ESNS2506).
System Action:
The events receiver attempts recovery.
User Action:
If the message was not followed by a recovery message, the error was probably related to data corruption. The event is discarded, and processing continues.
If the problem cannot be resolved, contact Technical Support.
Reason:
This message follows message ESNS2503. The recovery is attempted after an EPS request failure (see ESNS2503).
System Action:
Reconnection to EPS is attempted.
User Action:
See message ESNS2503 for the EPS return and error codes.
If the problem cannot be resolved, contact Technical Support.
Reason:
This message follows message ESNS2503. The required EPS services are currently unavailable. NetSpy Alert Events processing will resume as soon as EPS services are restored.
System Action:
Waiting on EPS to become available.
User Action:
Ensure that an SSI region is currently active with its event processor enabled.
From any panel, enter /PARMS and check the SSI parameter group. Ensure that the Sub- System Interface ID field contains the correct ID.
Reason:
This message follows message ESNS2503. An unrecoverable error occurred during an EPS request (see message ESNS2503). NetSpy Alert Events processing has stopped.
System Action:
The NetSpy Alert Events Receiver is terminated.
User Action:
Contact Technical Support.
Reason:
The NetSpy Alert Events receiver failed due to an MDO error. The failure is identified by the following:
- The statement type, ASSIGN
- The MDO return code, P1 (&ZMDORC)
- The MDO feedback code, P2 (&ZDMOFDBK)
- The map name, P3 (&ZMDOMAP)
- The full map component name, P4 (&ZMDONAME)
- The map component tag value, P5 (&ZMDOTAG)
- The ASN.1 type of the component, P6 (&ZMDOTYPE)
This failure indicates one of the following causes:
- An invalid record has been received.
- There is a mismatch between the ASN.1 map and the record.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
The NetSpy Alert Events receiver has received an event which it does not recognize, the event is ignored. The record received has a hexadecimal value of P1 at offset 1.
System Action:
The NetSpy Alert event is ignored.
User Action:
Contact Technical Support.
Reason:
A NetSpy Alert event was received from NetSpy via the EPS receiver ID P2 . However, the events processor procedure P2 is currently not active. The procedure is started.
System Action:
The NetSpy Alert Events procedure P2 is started.
User Action:
None.
Reason:
The NetSpy Alert Events receiver procedure is now ready to receive NetSpy Alert events via the EPS Services. The associated EPS receiver ID is P1 .
System Action:
The region is ready for NetSpy Alert Events processing. If required the NetSpy Alert Events processor will be started when the first event is received (message ESNS2509).
User Action:
None.
Reason:
The message displays a NetSpy Alert Processor trace record. P1 is the trace ID, and P2 is the trace text.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A request to start a copy of the $ESNS30Z procedure was ignored because another copy is currently running.
System Action:
A new copy of the procedure is not started.
User Action:
None.
Reason:
The NetSpy Alert Processor procedure has failed because of a possible data error in the event received from NetSpy. The error is identified by the following:
- Line number, P1 , and procedure name, P2 , where the error occurred
- Subroutine name, P3 , if applicable
- Error condition raised, P4
- Verb operand that has detected the error, P5 , if applicable
- NetSpy Monitor Name, P6
- Statement text where the error occurred, P7
System Action:
This message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the event in dump format. The NetSpy alert event is then ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
- Relevant messages in the activity log
Reason:
The NetSpy Alert Processor procedure has encountered a recoverable error. Check previous message(s) for the cause of the error.
System Action:
NetSpy Alert Event processing continues. However, some alert events might have been lost.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Relevant messages in the activity log
Reason:
The NetSpy Alert Processor procedure failed because of an MDO error. The failure is identified by the following:
- Statement type, ASSIGN
- MDO return code, P1 =&ZMDORC
- MDO feedback code, P2 =&ZDMOFDBK
- Map name, P3 =&ZMDOMAP
- Full map component name, P4 =&ZMDONAME
- Map component tag value, P5 =&ZMDOTAG
- ASN.1 type of the component, P6 =&ZMDOTYPE
System Action:
The message is written to the activity log and is followed by a series of messages (DD9003, DD9004, DD9006, and DD9007), which display the NetSpy alert event in dump format. The NetSpy Alert event is ignored.
User Action:
Contact Technical Support, making available the following diagnostic information:
- Full text of this message
- Record dump
- Relevant messages in the activity log
Reason:
The Alert Rule initialization action failed; the reason is given in a message (AMCALLnn) which follows.
System Action:
Alert Rule initialization is incomplete. Alert Monitoring functions will not function correctly
User Action:
Review the help for the appropriate AMCALLnn message.
Reason:
The Alert Create action failed; the reason is given in a message (AMCALLnn) which follows.
System Action:
The alert is not generated.
User Action:
Review the help for the appropriate AMCALLnn message.
Reason:
NetSpy Alert could not be processed, the reason is P3 . The NetSpy Alert monitor name is: P1 . The resource name is: P2 .
System Action:
The alert is ignored. A Hex dump of the alert is written to the activity log.
User Action:
Contact Technical Support.
Reason:
The Alert Clear action failed; the reason is given in a message (AMCALLnn) which follows.
System Action:
The alert is not cleared. A Hex dump of the alert is written to the activity log.
User Action:
Review the help for the appropriate AMCALLnn message.
Reason:
The NetSpy Alert Processor procedure has failed because of an internal system error. P1 is the reason for the failure.
System Action:
The procedure terminates.
User Action:
Contact Technical Support.
Reason:
You have selected the P1 action for an alert, but the alert resource Id was null.
System Action:
The action terminates.
User Action:
Select action VAM (View the Alert MDO), print the MAP display and contact Technical Support.
Reason:
You have selected the P1 action for an alert, but the resource associated with the alert is not currently known to the region.
System Action:
The action terminates.
User Action:
Review the Parameters Groups /PARMS SNA Automation Specifications (AUTOSNACNTL) Network Discovery Filters (page 3 of 3). Check the INCLUDE and EXCLUDE filter statements. If required Press F6 (Action) to rediscover the resources.
Reason:
You have selected the P1 action for an alert, but the request failed. The reason for the failure is P2 .
System Action:
The action terminates.
User Action:
Review the reason for the failure. Note the resource name and contact Technical Support.
| Copyright © 2012 CA. All rights reserved. |
|