Chapter 9 CEV (TSM EMS Event Viewer) Messages

The messages in this chapter are generated by the TSM EMS Event Viewer subsystem. The subsystem ID displayed by these messages includes CEV as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

1000

TSM Event Viewer Client Application could not open $RECEIVE.

Cause The Server Manager could not open the $RECEIVE process. This is a fatal error.

Effect $ZCEV stops.

Recovery See Appendix B for the cause of the file-system error code listed in the event detail, then run CEVSTART to restart the TSM EMS Event Viewer Application.

1001

TSM Event Viewer Client Application could not open an RPC transport handle.

Cause The RPC portmapper process was not running or a problem with TCP/IP occurred.

Effect $ZCEV stops.

Recovery Make sure that the RPC portmapper process is running by using the “rpcinfo -p” command from a TACL prompt. Start the RPC portmapper process if it is not running, then run CEVSTART to restart the TSM EMS Event Viewer Application.

1002

TSM Event Viewer Client Application could not register with the PORTMAP process.

Cause The RPC portmapper process was not running.

Effect $ZCEV goes into a loop with 10-minute delays, trying to start and register with the RPC portmapper process.

Recovery Stop the $ZCEV process. Make sure that the file $SYSTEM.ZRPC.PORTMAP exists, then run CEVSTART to restart the TSM EMS Event Viewer Application.

1003

TSM Event Viewer Client Application could not duplicate the RPC transport handle.

Cause An RPC internal error occurred.

Effect $ZCEV stops.

Recovery Make sure that the RPC portmapper process is running, then run CEVSTART to restart the TSM EMS Event Viewer Application.

1004

TSM Event Viewer Client Application has started successfully.

Cause The Server Manager was up and registered with the RPC portmapper process.

Effect None.

Recovery Informational message only; no corrective action is needed.

1005

TSM Event Viewer Client Application had an error on scv_complete.

Cause The AWAITIOX procedure failed. The Server Manager could not complete a check for a socket completion after a call to AWAITIOX, which returned a code not equal to CCE.

Effect None.

Recovery Informational message only; no corrective action is needed.

1006

TSM Event Viewer Client Application had an error on svc_sendreply.

Cause An RPC internal or TCP/IP internal error occurred. The svc_sendreply function fails.

Effect The Server Manager cannot send a message to a client.

Recovery Informational message only; no corrective action is needed.

1007

TSM Event Viewer Client Application had an error on svc_postrecv.

Cause An RPC or TCP/IP internal error occurred. The Server Manager failed to post a nowaited recvfrom() on a socket.

Effect None.

Recovery Informational message only; no corrective action is needed.

1008

TSM Event Viewer Client Application had an error on svc_postreply.

Cause An RPC or TCP/IP internal error occurred. The message is generated when the Server Manager failed to post a nowaited sendto() on a socket.

Effect None.

Recovery Informational message only; no corrective action is needed.

1009

TSM Event Viewer Client Application could not start the RPC Portmapper.

Cause Probable causes are:

The Server Manager was not running as the super ID (255,255).
The file $SYSTEM.ZRPC.PORTMAP did not exist.
TCP/IP was not running.

Effect The Server Manager waits 10 minutes, then again tries to connect to the RPC portmapper process. If it fails, it tries to start the RPC portmapper process.

Recovery Stop the $ZCEV process, then run CEVSTART.

1010

user-ID logged on to CEV.

user-ID

is the NSK user ID of the logged-on user.

Cause The indicated user logged on to the TSM EMS Event Viewer Application.

Effect None.

Recovery Informational message only; no corrective action is needed.

1011

TSM Event Viewer Client Application issued the following comment: comment.

comment

is a comment added to $ZLOG through the TSM EMS Event Viewer Application.

Cause A comment was added to $ZLOG by an operator using the TSM EMS Event Viewer Application.

Effect None, other than that the event has been added to $ZLOG.

Recovery Informational message only; no corrective action is needed.

1012

Portmap process portmap has restarted. The TSM Event Viewer Client Application serverManager is stranded from clients and will stop itself.

`portmap`	is the name of a portmap process.
`serverManager`	is the name of a server manager process.

Cause Operator intervention.

Effect The TSM EMS Event Viewer Application cannot accept new clients.

Recovery If serverManager is $ZCVP0 or $ZCVP1, restarting is unnecessary; otherwise, restart the TSM EMS Event Viewer Application.

1013

Portmap process portmap has switched to backup. The TSM Event Viewer Client Application serverManager will stop itself.

`portmap`	is the name of a portmap process.
`serverManager`	is the name of a server manager process.

Cause The primary portmap process died.

Effect The CEV Server manager is not reachable.

Recovery If serverManager is $ZCVP0 or $ZCVP1, restarting is unnecessary; otherwise, restart the TSM EMS Event Viewer Application.

1014

TCPIP Process tcpip does not exist. The TSM Event Viewer Client Application serverManager has stopped itself.

`tcpip`	is the name of a TCPIP process.
`serverManager`	is the name of a server manager process.

Cause The primary and backup TCPIP processes have died,

Effect The CEV Server Manager process is not reachable.

Recovery Restart TCPIP. If serverManager is $ZCVP0 or $ZCVP1, restarting is unnecessary; otherwise, restart the TSM EMS Event Viewer Application.

1015

TSM Event Viewer Client Application serverManager cannot stop the portmap process portmap.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.

Cause The portmap process is not stoppable by the CEV Server manager.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Stop the portmap process, stop and then restart the TSM EMS Event Viewer Application.

1016

A process is using the reserved portmap process name portmap illegally. The TSM Event Viewer Client Application serverManager cannot stop nor connect to this process, so it will stop itself.

`portmap`	is the name of a portmap process.
`serverManager`	is the name of a server manager process.

Cause A process other than portmap is using a portmap reserved name and cannot be stopped.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Stop the portmap process, stop and then restart the TSM EMS Event Viewer Application.

1017

TSM Event Viewer Client Application serverManager cannot open the out file for the portmap portmap.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.

Cause Cannot open an out file for portmap.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Determine why $NULL, $VHS, $OSP are not available. Determine why files cannot be created in $SYSTEM.ZCEV. Then stop and restart the TSM EMS Event Viewer Application.

1018

TSM Event Viewer Client Application serverManager had a PROCESS_CREATE_ error while trying to start portmap portmap. NSK error code = errCode.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.
`errCode`	is the value returned by PROCESS_CREATE_.

Cause Cannot start a portmap process using PROCESS_CREATE_.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Examine the error code to determine why the create failed. Fix the problem, and then restart the TSM EMS Event Viewer Application.

1019

TSM Event Viewer Client Application serverManager cannot open portmap process portmap to write the startup message. File system error code = errCode.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.
`errCode`	is the value returned by FILE_OPEN_.

Cause Cannot open the portmap process for writing.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Examine the error code to determine why the open failed. Fix the problem, and then restart the TSM EMS Event Viewer Application.

1020

TSM Event Viewer Client Application serverManager cannot write the startup message to the portmap process portmap. Will stop portmap process. File system error code = errCode.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.
`errCode`	is the value returned by FILE_WRITE_.

Cause Cannot write a startup message to the portmap process.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Examine the error code to determine why the write failed. Fix the problem, and then restart the TSM EMS Event Viewer Application.

1021

TCPIP process tcpip has restarted. CEV Server Manager serverManager is stranded and will stop itself.

`tcpip`	is the name of a TCPIP process.
`serverManager`	is the name of a server manager process.

Cause TCPIP has been restarted.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Restart the TSM EMS Event Viewer Application.

1022

TSM Event Viewer Client Application serverManager cannot connect/register to portmap process portmap. Error = errCode

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.
`errCode`	is the value returned by SVC_REGISTER.

Cause Cannot connect to portmap process.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Examine the error code to determine why process failed. After you determine the problem, restart the TSM EMS Event Viewer Application.

1023

Portmap process portmap has stopped.

portmap

is the name of a portmap process.

Cause The portmap process has stopped.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Restart the TSM EMS Event Viewer Application.

1024

Can't create TCPIP transport handle. Error = errCode

errCode

is the value returned by T_SVCUPD_CREATE.

Cause The TSM EMS Event Viewer Application cannot get a connection to TCPIP.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Make sure TCPIP is working. If you have to restart TCPIP, be sure to restart the TSM EMS Event Viewer Application.

1025

TSM Event Viewer Client Application serverManager stopped the portmap process portmap, return code = errCode

`portmap`	is the name of a portmap process.
`serverManager`	is the name of a server manager process.
`errCode`	is the value returned by PROCESS_STOP_.

Cause The CEV Server Manager stopped the portmap process.

Effect The portmap is stopped and no communication with clients is possible unless the server manager restarts the portmap. (See event 1026 ZCEV-EVT-PMAP-START-OK EVENT.)

Recovery If the TSM EMS Event Viewer Application is no longer running, restart it.

1026

TSM Event Viewer Client Application serverManager started the portmap process portmap.

`serverManager`	is the name of a server manager process.
`portmap`	is the name of a portmap process.

Cause The CEV Server Manager started the portmap process.

Effect The portmap is started and communication with clients is possible.

Recovery None needed.

1027

TSM Event Viewer Server Manager serverManager could not start because there were no startup parameters.

serverManager

is the name of a server manager process.

Cause There were no command line parameters given to CEVSTART.

Effect The TSM EMS Event Viewer Application will not be able to serve clients.

Recovery Rerun CEVSTART with the correct command line parameters.

1028

Portmap process restarted as portmap.

portmap

is the name of a portmap process.

Cause The portmap process was restarted with a new name.

Effect The portmap is started and communication with clients is possible.

Recovery Informational message only; no corrective action is needed.

1029

Portmap process portmap was restarted by the TSM Event Viewer Server Manager serverManager.

`portmap`	is the name of a portmap process.
`serverManager`	is the name of a server manager process.

Cause The portmap process died or was stopped and had to be restarted.

Effect The portmap is started and communication with clients is possible.

Recovery Informational message only; no corrective action is needed.

1030

PROCESS_CREATE_ for CEVEVX failed with error errorCode.

errorCode

is an identifier for the error returned by PROCESS_CREATE_.

Cause The TSM Event Viewer Server Manager could not create a process.

Effect The TSM Event Viewer Server Manager will not accept logons.

Recovery Stop and restart the TSM Event Viewer Server Manager.

1031

FILE_OPEN_ on child process failed with error errorCode.

errorCode

is an identifier for the error returned by FILE_OPEN_.

Cause The TSM Event Viewer Server Manager could not open its child process to send a startup message.

Effect The TSM Event Viewer Server Manager will not accept logons.

Recovery Stop and restart the TSM Event Viewer Server Manager.

1032

Error errorCode writing to child process.

errorCode

is an identifier for the error returned by WRITEX.

Cause The TSM Event Viewer Server Manager could not write a startup message to its child.

Effect The TSM Event Viewer Server Manager will not accept logons.

Recovery Stop and restart the TSM Event Viewer Server Manager.

1033

TSM Event Viewer Server Manager serverManager was reset because it could not communicate with its daughter process.

serverManager

is the name of the server manager process

Cause The TSM Event Viewer Server Manager could not communicate with its daughter process.

Effect The TSM Event Viewer Server Manager serverManager was reset and is now available for login and event retrieval.

Recovery If the persistence manager did not restart the TSM Event Viewer Server Manager serverManager, restart it using CEVSTART.

If ZCEV event numbers 1030, 1031, or 1032 appear in the log prior to this event, please send the logs to the Global NonStop Solution Center (GNSC) for analysis on product T1048.