IBM Tivoli NetView for z/OS, Version 6.2

DISPLAY (EAS)

Syntax


DISPLAY (EAS)

>>-MODIFY-- --procname--,--DISPLAY-- --+-STATUS-+--------------><
                                       '-QSTATS-'

IBM-Defined Synonyms

Command or Operand	Synonym
MODIFY	F

Purpose of Command

The DISPLAY command displays operational characteristics of the Event/Automation Service. The STATUS option displays information about the operational status of each service and additional information about the connectivity of the service outside of the Event/Automation Service address space.

Operand Descriptions

procname

Specifies the Event/Automation Service job name.

STATUS

Displays the status of the following:

The alert adapter service task
The confirmed alert adapter service task
The message adapter service task
The confirmed message adapter service
The event receiver service task
The trap-to-alert service
The alert-to-trap service
PPI connection
TCP/IP connection.

QSTATS

Displays information about the number of data buffers sent and received by all of the subtasks that make up the Event/Automation Service, and the total number of data buffers that are currently queued to a subtask and have not been processed.

Example: Displaying Event/Automation Service status

To display the status for the Event/Automation Service job named IHSAEVNT, enter:

F IHSAEVNT,DISPLAY,STATUS

A response similar to the following is displayed:

IHS0141I  SERVICE   STATUS   ADDITIONAL INFO
IHS0142I  -------   ------   ---------------
IHS0143I  ALERTA    CO-IDLE  9.18.27.36
IHS0143I                     9.18.27.37
IHS0143I  MESSAGEA  UP       9.18.27.38
IHS0143I  EVENTRCV  IPCYCLE  NETVALRT,1001
IHS0143I  TRAPALRT  DOWN     *
IHS0143I  ALRTTRAP  UP       9.18.27.39
IHS0143I  MESSAGEC  UP       9.18.27.38
IHS0143I  ALERTC    UP       9.18.27.36
IHS0143I  PPI       UP       IHSATEC
IHS0143I  TCP/IP    UP       9.18.27.39

The ADDITIONAL INFO provides connectivity information for each service. The information displayed for each service is as follows:

ALERTA, ALERTC, MESSAGEA, MESSAGEC: One or more IP addresses, which are taken from the ServerLocation statement of the configuration file of the service. These addresses are listed one per output line. The service name is not repeated for each address after the first address. If a host name is supplied on the ServerLocation statement instead of an IP address, the value represents the host name resolved to the IP address. If the value cannot be resolved, *NR* is displayed instead of an IP address.
EVENTRCV, TRAPALRT: The name of the PPI mailbox to which the service forwards alerts, followed by the port number which the service has registered with TCP/IP in order to act as an IP server.
ALRTTRAP: The IP address from the HostName statement of the configuration file of the service. If a host name is supplied on the HostName statement instead of an IP address, the value represents the host name resolved to the IP address.
PPI: The name of the mailbox that the Event/Automation Service has registered with the NetView® Program to Program interface (PPI). This mailbox is used to receive data from the NetView address space.
TCP/IP: The IP address of the local host on which the Event/Automation Service is running. For any service that is not active, for example the STATUS is DOWN, the ADDITIONAL INFO contains an asterisk (*).

The STATUS can be one of the following:

CLOSE

For ALERTA and MESSAGEA, this status indicates that the service is closing the connection to a designated event server and there is a delay in closing the connection. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service is closing the connection to an event server and there is a delay in closing the connection. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

CO-IDLE

For ALERTA and MESSAGEA, this status indicates that the service has a connection to a designated event server that is idle. An idle connection is a connection where data is not in the process of being sent or received. This status appears only for services that have a ConnectionMode of ConnectionOriented. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service has a connection to an event server that is idle. An idle connection is a connection where data is not in the process of being sent or received. This status appears only for services that have a ConnectionMode of ConnectionOriented. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

CONNECT

For ALERTA and MESSAGEA, this status indicates that the service is attempting to connect to a remote designated event server and there is a delay in connecting with the server. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service is attempting to connect to a remote event server and there is a delay in connecting with the server. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

DOWN

For the Event/Automation Service, this status indicates that the service is stopped. For PPI and TCP/IP, this status indicates that the Event/Automation Service is not able to contact the service which typically indicates that it is not active.

FL-IDLE

For ALERTA and MESSAGEA, this status indicates that the service sent the number of events from the data cache that corresponds to the BufferFlushRate setting, and is waiting until more events can be sent. The amount of wait time is dependent on how much time remains in the current send window. It can never be more than 60 seconds. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service sent the number of events from the data cache that corresponds to the BufferFlushRate setting, and is waiting until more events can be sent. The amount of wait time is dependent on how much time remains in the current send window. It can never be more than 60 seconds. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

GETPORT

For ALERTA and MESSAGEA, this status indicates that the service is attempting to retrieve a port of the designated event server from the portmapper of the server and there is a delay in retrieving the port. The status appears on the line that contains the IP address of the designated event server. This status does not occur for any other service.

IPCYCLE

For EVENTRCV and TRAPALRT, this status indicates that the service cannot register its port with TCP/IP. This can occur for a number of reasons, including the following:

TCP/IP might not be active.
The port might be reserved by TCP/IP or registered with TCP/IP by another program.
For EVENTRCV only, the portmapper program might not be active. This can occur only if the UsePortmapper setting is Yes.

The service task is recycled every 60 seconds until it can register its port with TCP/IP. The status remains IPCYCLE until the port can be successfully registered, or the service is manually stopped with the STOP command. This status does not occur for any other service.

RETRY

For ALERTA and MESSAGEA, this status indicates that the service has disconnected from a designated event server and is waiting for a 60 second interval before attempting to reconnect to a designated event server. This status appears only for services that have a ConnectionMode of connection_oriented. The status is not related to a specific IP address and therefore appears on the first line of the service output.

For ALERTC and MESSAGEC, this status indicates that the service has disconnected from an event server and is waiting for a 60 second interval before attempting to reconnect to the event server. This status appears only for services that have a ConnectionMode of connection_oriented. The status is not related to a specific IP address and therefore appears on the first line of the service output. This status does not occur for any other service.

SEND

For ALERTA and MESSAGEA, this status indicates that the service is sending an event to a designated event server and there is a delay in sending the event. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service is sending an event to an event server and there is a delay in sending the event. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

SOCKET

For ALERTA and MESSAGEA, this status indicates that the service is attempting to retrieve a socket in preparation for connecting to a designated event server and there is a delay in retrieving the socket. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service is attempting to retrieve a socket in preparation for connecting to an event server and there is a delay in retrieving the socket. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

SHUTDWN

For ALERTA and MESSAGEA, this status indicates that the service is shutting down the connection to a designated event server and there is a delay in shutting down the connection. The status appears on the line that contains the IP address of the designated event server.

For ALERTC and MESSAGEC, this status indicates that the service is shutting down the connection to an event server and there is a delay in shutting down the connection. The status appears on the line that contains the IP address of the event server. This status does not occur for any other service.

UP

For PPI, this status indicates that the NetView Program to Program interface (PPI) is active and the Event/Automation Service has successfully registered a mailbox name with the PPI.

For TCP/IP, this status indicates that TCP/IP is active and the Event/Automation Service is able to retrieve the IP address of the host on which the service is running.

For ALERTA and MESSAGEA, this status indicates that the service is active and currently not connected through TCP/IP to a designated event server. This status is not associated with a specific IP address and is always displayed on the first output line for the service, regardless of how many addresses were specified on the ServerLocation statement of the service. If the ConnectionMode of the service is connection_oriented, the status indicates UP until the first Event Integration Facility (EIF) event is sent to one of the designated event servers. A connection to a designated event server is not established until an event is sent to the server.

For ALERTC and MESSAGEC, this status indicates that the service is active and currently not connected through TCP/IP to an event server. This status is not associated with a specific IP address and is always displayed on the first output line for the service, regardless of how many addresses were specified on the ServerLocation statement of the service. If the ConnectionMode of the service is connection_oriented, the status indicates UP until the first event is sent to one of the designated event servers. A connection to an event server is not established until an event must be sent to the server. The event server then replies with a confirmation that indicates acceptance of the event.

For EVENTRCV and TRAPALRT, this status indicates that the service is active and has registered a port with TCP/IP.

For ALRTTRAP, this status indicates that the service is active and has connected through TCP/IP to the SNMP agent.

WAITRSP

For ALERTC and MESSAGEC, this status indicates that the adapter is waiting for event confirmation from an event server to which an EIF event was sent. The adapter waits for a response up to the amount of time specified on the RetryInterval statement in its configuration file.

Example: Displaying queue count information

To display the current internal queue information for the Event/Automation Service job named IHSAEVNT, enter:

F IHSAEVNT,DISPLAY,QSTATS

A response similar to the following is displayed:

IHS0145I TASK      QCOUNT      TOTAL SENT  TOTAL RCVD
IHS0146I ----      ------      ----------  ----------
IHS0147I CONTROL   0           12          9
IHS0147I ALERTA    3           0           3
IHS0147I MESSAGEA  0           0           4
IHS0147I EVENTRCV  0           7           0
IHS0147I TRAPALRT  0           2           0
IHS0147I ALRTTRAP  0           0           2
IHS0147I MESSAGEC  0           0           4
IHS0147I ALERTC    4           0           4

The QCOUNT column represents the total number of data buffers that are waiting on the input queue. The TOTAL SENT column represents the total number of data buffers queued from this task to any other task. The TOTAL RCVD column represents the total number of data buffers received and processed by this task.

Feedback