Chapter 115 TCP/IP (Parallel Library) Messages

The messages in this chapter are generated by the TCP/IP (Parallel Library) subsystem. The subsystem ID displayed by these messages includes ZTCP as the subsystem name. These messages should not be confused with those generated by the TCP/IP subsystem that include the ZTCI 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.

1 (Critical Event)

TCPIP no longer operational on CPU cpu, cause.

`cpu`	is the CPU where the event was reported.
`cause`	contains information about the halt.

Cause An internal error was detected in the PTCPIP subsystem and the PTCPIP subsystem could not recover.

Effect The processor is halted. The PTCPIP subsystem in the halted processor is no longer operational. All the established PTCPIP connections through that processor are lost.

Recovery Restart the PTCPIP subsystem on the processor where the event occurred and send the online processor dump file to your service provider for analysis.

2 (Critical Event)

ARP: Duplicate IP address ip_addr from Ethernet address enet_addr.

`ip_addr`	is the IP address in dotted notation.
`enet_addr`	is the Ethernet address.

Cause Another machine on the network is broadcasting the same IP address as the machine on which the PTCPIP subsystem is reporting the event.

Effect Either of the machines with the IP address conflict could get packets intended for the other and would not function properly.

Recovery Determine which machine is in error and assign a unique IP address to that machine.

3 (Critical Event)

ARP: Ethernet broadcast address (FF.FF.FF.FF.FF.FF) used by IP address ip_addr

ip_addr

is the IP address in dotted notation.

Cause A machine on the Ethernet LAN is using a broadcast address as its Ethernet address.

Effect This causes all packets sent to the broadcast address to be received by all machines on the Ethernet LAN. Performance on all machines is adversely affected. In addition, some implementations of TCP/IP might try to forward the packet(s) back over the Ethernet LAN, flooding the LAN and crashing most machines on the LAN.

Recovery Determine which machine is using the broadcast address as its Ethernet address and correct the problem. Note that you cannot reassign an Ethernet address.

4 (Critical Event)

The TCPIP monitor failed to open $Receive. CPU cpu, Error err_code.

`cpu`	is the processor where the event was reported.
`err_code`	is the file system error that occurred. See Appendix B for information on the specified error.

Cause The monitor process in the PTCPIP subsystem failed to open $Receive during initialization.

Effect There is a loss of the PTCPIP subsystem in that processor until the PTCPIP monitor is restarted.

Recovery Restart the PTCPIP monitor on the processor where the event occurred. If the problem persists, take an online processor dump and send the dump file to your service provider for analysis. This event is an indication of an internal system problem.

5 (Critical Event)

en if_unit can't handle af family.

`if_unit`	is the Interface unit.
`family`	is the Protocol family.

Cause The loopback module of the PTCPIP subsystem detected a protocol family that is not supported. This is an internal problem in the PTCPIP subsystem.

Effect All PTCPIP subsystem activities related to the loopback interface will not function.

6 (Critical Event)

in_cksum out of mbufs.

Cause A Checksum calculation failed in the checksum routine.

Effect There may be a loss of connection.

Recovery The checksum routine used for Internet Protocol family headers failed. Report the incident to your service provider.

7 (Critical Event)

Error err_code on LIF lif_name.

err_code

is the error number returned by the QIO subsystem. Possible values are:

5	ZSM_ERR_SEGMENT_NOT_INITIALIZED
35	ZSM_ERR_Q_FULL
73	ZSM_ERR_BAD_Q_ID
75	ZSM_ERR_BAD_USER_DATA_PTR

lif_name

is the name of the LIF involved.

Cause The PTCPIP subsystem failed to communicate with the underlying LIF.

Effect The PTCPIP subsystem will attempt to register/de-register the filter, or attempt the last I/O. If this problem continues, the LIF becomes inaccessible.

Recovery Operator intervention might be required to ensure that the processor has access to the LIF and that the LIF and the QIO subsystem are in the proper working state. If problems are found and corrected and the event still occurs, report the incident to your service provider.

8 (Critical Event)

Could not create QIO queue for Subnet subnet, Error err_code.

subnet

is the name of the subnet.

err_code

is the error code returned from the QIO subsystem. Possible values are:

5	ZSM_ERR_SEGMENT_NOT_INITIALIZED
10	ZSM_ERR_GETPOOL_FAILED
30	ZSM_ERR_Q_DUPLICATE
72	ZSM_ERR_BAD_MODULE_ID

Cause The QIO interface module of the PTCPIP subsystem failed to create an inbound queue for filter use.

Effect The subnet configured in the PTCPIP subsystem will not function until the problem is resolved.

Recovery Examine the state of the QIO subsystem to ensure that it is in proper working state. If problems are found and corrected and the event still occurs, report the incident to your service provider.

9 (Critical Event)

LIF lif_name not in STARTED State in CPU cpu.

`lif_name`	is the name of the LIF involved.
`cpu`	is the processor where the event was reported.

Cause The LIF is not in the STARTED state.

Effect The LIF configured in the PTCPIP subsystem will not function until the problem is resolved.

Recovery Ensure the LIF is in the STARTED state.

10 (Critical Event)

LIF lif_name access Down in CPU cpu.

`lif_name`	is the name of the LIF involved.
`cpu`	is the processor where the event was reported.

Cause The LIF is not accessible.

Effect The LIF configured in the PTCPIP subsystem will not function until the problem is resolved.

Recovery Ensure that the access state of the LIF is UP.

11 (Noncritical Event)

info_text.

info_text

is the text explaining this informational event.

Cause This event is used for informational purposes.

Effect None

Recovery Informational message only; no corrective action is needed.

12 (Noncritical Event)

TCPIP monitor process stopped by operator.

Cause The PTCPIP Process was stopped by the operator.

Effect The PTCPIP monitor process was brought down. All the network activity through that CPU ceases.

Recovery Since the PTCPIP subsystem was brought down by an operator, no further action is recommended.

13 (Critical Event)

Subnet subnet, LIF Filter register timeout.

subnet

is the name of the PTCP/IP subsystem subnet trying to register the filter.

Cause The PTCPIP subsystem timed out while waiting for a filter registration to complete.

Effect The PTCPIP subsystem will attempt to re-register the filter. If the problem continues, the LIF becomes inaccessible.

Recovery If this event continues after a second attempt to register the filter, abort and restart the LIF.

14 (Critical Event)

Unable to access LIF lif_name from cpu cpu.

`lif_name`	is the name of the inaccessible LIF.
`cpu`	is the number of the processor that couldn’t access the LIF.

Cause The LIF is not accessible by the PTCPIP subsystem.

Effect The LIF configured in the PTCPIP subsystem is inaccessible until the problem is resolved.

Recovery Ensure the LIF is accessible from the processor where the event occurred.

15 (Critical Event)

Unknown Device lif_name.

lif_name

is the name of the inaccessible LIF.

Cause The device name specified for configuring the subnet does not exist.

Effect The LIF configured in the PTCPIP subsystem is not inaccessible until the problem is resolved.

Recovery Ensure the LIF is configured in the SLSA subsystem.

16 (Critical Event)

Device lif_name returned a NULL MAC address.

lif_name

is the name of the LIF associated with this event.

Cause The QIO subsystem returned a NULL MAC address to the PTCPIP subsystem when PTCPIP tried to obtain the MAC address for the interface.

Effect The LIF configured in the PTCPIP subsystem is inaccessible until the problem is resolved.

Recovery Ensure the LIF is properly configured in the SLSA subsystem.

17 (Critical Event)

name: Filter Register for IP address ip_addr failed. Error = err_code, Filter Type = type, Local Port = port.

name

is the name of the interface (subnet name) or a filter name.

ip_addr

is the IP address in dotted notation.

err_code

is the filter registration error code. The possible values of err_code are:

200	Filter exists
201	Invalid owner
202	No filter tree
203	No filter
204	Invalid parent filter
205	Bad LIF header
206	Filter other
207	Device inaccessible
208	Invalid parameter

type

is the type of filter registration. The possible values of type are:

Value	Type	Category	Value	Type	Category
1	ARP request	Subnet	10	TCP client	Port Level
2	ARP response	Subnet	11	TCP server	Port Level
3	MMAC	Subnet	12	TCP server any	Port Level
4	SNAP	Subnet	13	UDP client	Port Level
5	IP broadcast	Subnet	14	UDP server	Port Level
6	IP default	Subnet	15	UDP server any	Port Level
7	IP alias	Subnet	16	ICMP default	Subnet
8	TCP default	Subnet	17	IP fragmentation	Subnet
9	UPD default	Subnet

port

is the local port number.

Cause A filter registration failed on subnet name for the ip_addr. This event could be due to an improperly configured PTCPIP subsystem or an internal PTCPIP subsystem problem.

Effect The PTCPIP subsystem will attempt to re-register the filter. If the filter registration category is Subnet and the problem continues, the subnet becomes inaccessible. If the filter registration category is Port Level and the problem continues, filter registration will fail.

Recovery Using the filter type and the cause of the failed registration from the err_code value, correct the problem. Using the filter type and the cause of the failed de-registration from the err_code value, try to resolve the problem. If you cannot resolve the problem, report it to your service provider, providing an online processor dump and a copy of the routing tables.

18 (Critical Event)

if_name: Filter Register for IP address ip_addr failed, Timed Out

`if_name`	is the subnet name.
`ip_addr`	is the IP address in dotted notation.

Cause Filter registration timed out on subnet if_name for ip_addr.

Effect None

Recovery The PTCPIP subsystem will retry the filter registration. No operator intervention is required.

19 (Critical Event)

Name: Filter Register for IP address ip_addr failed, Already In Use. Filter Type = type, Local Port = l_port, Foreign Port = f_port.

Name

is the name of the interface (subnet name) or a filter name.

ip_addr

is the IP address in dotted notation.

type

is the type of filter registration. The possible values of type are:

Value	Type	Category	Value	Type	Category
1	ARP request	Subnet	10	TCP client	Port Level
2	ARP response	Subnet	11	TCP server	Port Level
3	MMAC	Subnet	12	TCP server any	Port Level
4	SNAP	Subnet	13	UDP client	Port Level
5	IP broadcast	Subnet	14	UDP server	Port Level
6	IP default	Subnet	15	UDP server any	Port Level
7	IP alias	Subnet	16	ICMP default	Subnet
8	TCP default	Subnet	17	IP fragmentation	Subnet
9	UPD default	Subnet

l_port

is the local port number.

f_port

is the foreign port number.

Cause The specified filter was previously registered and it is already in use on subnet Name for ip_addr. This event may be due to an improperly configured PTCPIP subsystem or an internal subsystem problem.

Effect No retry will be done by the PTCPIP subsystem. The application will receive an error code that can be used to help pin-point the cause of the failure.

Recovery Using the filter type and the cause of the failed registration from the err_code value, correct the problem. Using the filter type and the cause of the failed de-registration from the err_code value, try to resolve the problem. If you cannot resolve the problem, report the it to your service provider, providing an online processor dump and a copy of the routing tables.

20 (Critical Event)

name: Filter De-register for IP address ip_addr failed. Error = err_code, Filter Type = type, Local Port = port.

name

is the name of the interface (subnet name) or a filter name.

ip_addr

is the IP address, in dotted notation, for which filter de-registration failed.

err_code

is the filter de-registration error code. The possible values of err_code are:

200	Filter exists
201	Invalid owner
202	No filter tree
203	No filter
204	Invalid parent filter
205	Bad LIF header
206	Filter other
207	Device inaccessible. Check the availability of the PIF associated with the filter.
208	Invalid parameter

type

is the type of filter de-registration. The possible values of type are:

Value	Type	Category	Value	Type	Category
1	ARP request	Subnet	10	TCP client	Port Level
2	ARP response	Subnet	11	TCP server	Port Level
3	MMAC	Subnet	12	TCP server any	Port Level
4	SNAP	Subnet	13	UDP client	Port Level
5	IP broadcast	Subnet	14	UDP server	Port Level
6	IP default	Subnet	15	UDP server any	Port Level
7	IP alias	Subnet	16	ICMP default	Subnet
8	TCP default	Subnet	17	IP fragmentation	Subnet
9	UPD default	Subnet

port

is the local port number.

Cause A filter de-registration failed on subnet name for ip_addr. This event could be due to an improperly configured PTCPIP subsystem or an internal PTCPIP subsystem problem.

Effect None

Recovery Report the problem to your service provider, providing the IP-address type and port as well as an online processor dump and a copy of the routing tables.

21 (Noncritical Event)

module: No ARP cache for Route route_name, IP address ip_addr

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`route_name`	is the name of the route.
`ip_addr`	is the IP address, in dotted notation.

Cause The PTCPIP subsystem failed to resolve an IP address into an ethernet address.

Effect Any attempt to communicate with this IP address will fail until the problem is resolved.

Recovery Examine the routing tables in the processor where this event was reported and ensure that they are set up properly. Also ensure that the routers attached to the network are functioning and that the LIF associated with the subnet is in a working state. If the problem persists, report the problem to your service provider, providing an online processor dump and a copy of the routing tables.

22 (Critical Event)

module: No Route entry for IP address ip_addr

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`ip_addr`	is the IP address, in dotted notation.

Cause An attempt to locate the route entry for a given IP failed.

Effect Any attempt to communicate with this IP address will fail until the problem is resolved.

23 (Critical Event)

module: Bad Interface, Type interface_type.

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`interface_type`	is the value of the unsupported interface type.

Cause An invalid interface type was detected during ARP logic processing.

Effect An internal PTCPIP problem occurred. You may observe abnormal PTCPIP behaviors such as connection drops or failures to connect.

Recovery This event indicates an internal problem in either the routing or the ARP logic. Report the problem to your service provider, providing an online processor dump and a copy of the routing tables.

24 (Critical Event)

module: Bad Gateway values. SA Family = sa_value, SA length = sa_len, Route Destination IP address ip_addr

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`sa_value`	is the socket address family.
`sa_len`	is the length of the socket address family.
`ip_addr`	is the route destination IP address in dotted decimal notation.

Cause An invalid socket address family or invalid length of a socket address family was detected during ARP processing.

Effect A link-level route for this IP address could not be created. Any attempt to communicate with this IP address will fail until the problem is resolved.

Recovery This event indicates an internal problem in either the routing or ARP logic. Report the problem to your service provider, providing an online CPU dump and a copy of the routing tables.

25 (Critical Event)

module: ARP Info overwritten for IP address ip_addr from Ethernet address enet_addr.

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`ip_addr`	is the route destination IP address in dotted decimal notation.
`enet_addr`	is the Ethernet address (MAC).

Cause An IP address was resolved with an Ethernet/MAC address.

Effect This is an informational event that occurs when an IP address is resolved with a MAC address. No other effect should occur in the PTCPIP subsystem.

Recovery This event is usually observed when the subnets are first configured and brought up. If this event happens continuously, report the incident to your service provider.

26 (Critical Event)

module: Unable to create ARP entry. IP address ip_addr Route Destination IP address route_addr

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`ip_addr`	is the IP address related to ARP creation, in dotted decimal notation.
`route_addr`	is the route destination IP address in dotted decimal notation.

Cause An attempt to either look up or create an ARP entry failed.

Effect Since the ARP cache lookup failed, a new connection attempt will fail to connect and existing connections may be temporarily lost. If the problem continues, all the existing connections will be lost.

Recovery Examine the command attempting to generate the route that failed. If a route associated with the ARP entry already exists, this event is informational only. If no route associated with the ARP cache exists, send a copy of the routing tables to your service provider for analysis.

27 (Critical Event)

module: Route Mask already exists. Mask value mask_val

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`mask_val`	is the mask value associated with the route in dotted notation.

Cause The routing module of the PTCPIP subsystem detected the existence of a duplicate network mask during an attempt to create a network route.

Effect The route failed to enter the routing table. No other effect should occur in the PTCPIP subsystem.

Recovery Examine the command attempting to generate the route that failed. Ensure that the route destination address, the netmask associated with the route, and the gateway address associated with the route are unique.

28 (Critical Event)

module: Route not freed. Route route_name, Reference Count -cnt.

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`route_name`	is the name of the route.
`cnt`	is the negative reference count of this route.

Cause An attempt to free a routing structure has failed because the reference count of the route entry was negative.

Effect The route associated with this event becomes unusable. The connections through this route may experience abnormal behavior. Another possible effect is a memory leak.

Recovery This event is an indication that the reference count of the route was incremented or decremented incorrectly. Send a copy of the routing tables to your service provider for analysis.

29 (Noncritical Event)

module: Trace Buffer is full on CPU cpu.

`module`	is the function routine in the PTCPIP subsystem where this event was generated.
`cpu`	is the processor number where the event was reported.

Cause One of the QIO buffers used for TCPMON/TCPLIB trace buffering does not have enough room for another trace record.

Effect None

Recovery Informational message only; no corrective action is needed. If the problem persists, report the problem to your service provider.

30 (Critical Event)

module: TCPMON failed to update a record to CONFIG DB. Error err_code, Record Type type, CPU cpu.

module

is the function routine in the PTCPIP subsystem where this event was generated.

err_code

is the internal error code associated with the event.

type

is the record type. The currently defined record types are:

180	Config_DB_TYPE_TCP_PROCESS
181	Config_DB_TYPE_TCP_SUBNET
182	Config_DB_TYPE_TCP_ROUTE
183	Config_DB_TYPE_TCP_ENTRY

cpu

is the processor number where the event was reported.

Cause An internal error occurred during configuration database management.

Effect This error may lead to inconsistent subnet or route structures among processors.

Recovery Examine the subnet and routing topology in all processors with running PTCPIP processes. If any inconsistency exists among the processors, disable the configuration database for PTCPIP and re-configure the subnets and routes. Regardless of the condition of the database, this error should be reported to your local service provider for a complete analysis of the problem.

31 (Critical Event)

module: TCPMON failed to fetch a record from CONFIG DB. Error err_code, Record Type type, CPU cpu.

module

is the function routine in the PTCPIP subsystem where this event was generated.

err_code

is the internal error code associated with the event.

type

is the record type. The currently defined record types are:

180	Config_DB_TYPE_TCP_PROCESS
181	Config_DB_TYPE_TCP_SUBNET
182	Config_DB_TYPE_TCP_ROUTE
183	Config_DB_TYPE_TCP_ENTRY

cpu

is the processor number where the event was reported.

Cause An internal error occurred during configuration database management.

Effect This error may lead to inconsistent subnet or route structures among processors.

32 (Critical Event)

module: TCPMON Unexpected Socket migration request. Originated from CPU cpu, IP address ip_addr from Port port.

`module`	is the Function routine in the PTCPIP subsystem where this event was generated.
`cpu`	is the processor number where the event was reported.
`ip_addr`	is the remote IP address associated with this migration request, in dotted decimal notation.
`port`	is the remote port number associated with this migration request.

Cause No memory is available to format the migration request.

Effect The migration request is discarded and the socket is not migrated to a new processor.

Recovery Informational message only; no corrective action is needed.

33 (Critical Event)

module: TCPMON Socket migration request, get MBUF failed. Originated from CPU cpu, IP address ip_addr from Port port.

`module`	is the Function routine in the PTCPIP subsystem where this event was generated.
`cpu`	is the processor number where the event was reported.
`ip_addr`	is the remote IP address associated with this migration request, in dotted decimal notation.
`port`	is the remote port number associated with this migration request.

Cause No memory is available to format the migration request.

Effect The migration request is discarded and the socket is not migrated to a new processor.

Recovery Informational message only; no corrective action is needed.

200 (Critical Event)

TCPMAN Unable to start backup process. Error err_num, Error-detail err_detail.

`err_num`	is the error number reporting the reason that the backup did not start. See Appendix D for information on the specified error.
`err_detail`	is the detailed information about the error.

Cause The TCPMAN backup process cannot be started and the cause can be determined using err_num and error_detail.

Effect The backup TCPMAN process is not created.

Recovery The primary TCPMAN process continues to run and attempts to restart the backup until the backup process starts. If the problem persists, contact your service provider and provide the following:

Descriptions of the problem and accompanying symptoms
Details from this, and any other relevant messages
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

201 (Critical Event)

TCPMAN Checkpoint Error. Entity rept_entity, Chkpt Type chkpt_type, Cause cause.

rept_entity

is the TCPMAN checkpoint destination object type. The possible values of rept_type are:

0	A configuration change checkpoint failed. An SCF command did not checkpoint correctly to the backup TCPMAN process.
1	A process change checkpoint failed. The TCPMAN backup started, but it did not receive all the sync data from the primary process.
2	An OPEN checkpoint failed. The TCPMAN backup did not receive an OPEN checkpoint from the TCPMAN primary.
3	A Manager checkpoint failed. The TCPMAN backup did not receive a sync data checkpoint from the primary process.

chkpt_type

is the type of checkpoint that failed. The possible values of chkpt_type are:

5001	ZCOM_CMD_ABORT
5003	ZCOM_CMD_ADD
5005	ZCOM_CMD_ALTER
5007	ZCOM_CMD_DELETE
5014	ZCOM_CMD_START
5015	ZCOM_CMD_STOP
5017	ZCOM_CMD_SWITCH
5018	ZCOM_CMD_TRACE

cause

specifies why this error occurred. The possible values of cause are:

1	The backup process received a subdevice number that is not configured.
2	The backup process received checkpoint data of the wrong size.
3	READLINK failed when reading checkpoint data.
4	The backup could not obtain memory for checkpointing additional control blocks.
5	The backup received a checkpoint with an unexpected type.

Cause The backup process cannot process a checkpoint.

Effect No immediate problems result.

Recovery Halt and dump the processor of the TCPMAN backup process; then reload the processor to restart the TCPMAN backup process.

If the problem persists, do not reload the backup; contact your support representative and provide the following:

Descriptions of the problem and accompanying symptoms
Details from this, and any other relevant messages
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.




	NOTE: SCF commands that cause checkpoints are those that alter configuration such as ADD SUBNET. The STATUS, INFO, and STATS commands do not require checkpoints. Sync data includes all the current "known" configuration information as stored in the system configuration database (CONFIG). SCF commands that alter the current configuration require updating the CONFIG, checkpointing the actual configuration change, and finally checkpointing the sync data to ensure that the primary and backup are exactly in sync.

202 (Noncritical Event)

TCPMAN Switched from CPU from_cpu to CPU to_cpu.

`from_cpu`	is the processor from which the TCPMAN process switched.
`to_cpu`	is the processor to which the TCPMAN process switched.

Cause An operator requested a processor switch using SCF.

Effect The TCPMAN is running in a different processor.

Recovery Informational message only; no corrective action is needed.

203 (Noncritical Event)

TCPMAN Error notification. Function notif_func, Error notif_err. Info1 notif_info1, Info2 notif_info2, Line line_num, Module mod_name [ , Name notif_name ].

notif_func

is the name of the function that failed.

notif_err

is the completion code returned by Guardian. The possible values of notif_err are:

1	Normal, voluntary termination with WARNING diagnostics. For example, if the process is a compiler, the compilation terminated with WARNING diagnostics after building a complete object file.
2	Abnormal, voluntary termination with FATAL errors or diagnostics. For example, if the process is a compiler, the compilation terminated with FATAL diagnostics and either an object file was not built or, if built, might be incomplete. A complete listing is generated.
3	Abnormal, voluntary, but premature termination with FATAL errors or diagnostics. For example, if the process is a compiler, the compilation terminated with FATAL diagnostics, with either no object file or an incomplete object file being built and an incomplete listing generated (the compiler quit compiling prematurely).
4	Process never got started. This completion code exists primarily for the use of the command interpreter or other command language interpreters that can act as the executor process of a batch job. This code allows the executor process to detect that a process associated with a RUN statement never got started. In that sense, this completion code is a “fake” completion code. The command interpreter acts as though it received a termination message from the process that it tried to create, when in fact it received an error returned by the procedure or OSS function that launched the process. The command interpreter then makes the completion code and the error returned by the procedure or OSS function that launched the process available for evaluation, for example, by a batch job executor process.
5	Process calls PROCESS_STOP_ (with abnormal termination specified) or ABEND on itself. This code is the default completion code for the PROCESS_STOP_ procedure (when abnormal termination is specified) and the ABEND procedure.
6	PROCESS_STOP_, STOP, or ABEND was called to delete a process by an external, but authorized, process. The system includes this completion code in the process deletion message. If the process cannot be stopped, the request is saved so that when the process calls SETSTOP this completion code is sent with the process deletion message. The user id, the PCBCRAID (CAID), and the process ID of the process that caused the termination are included in the termination message.
7	Restart this job. This completion code is used by the NetBatch scheduler and an executor process. The executor process sets its completion code to this value upon termination; the scheduler interprets this completion code and restarts a “restartable” job.
8	Code 8 is the same as code 1, normal termination, except that the user must examine the listing file to determine whether the results are acceptable. Completion code 8 is typically used by compilers.
9	The kill() or raise() function generated a signal that stopped the process. The termination information provides the signal number.

notif_info1 and notif_info2

provide context pertaining to the error.

line_num

is the line number in the module reporting the error notification.

mod_name

is the name of the TCPMAN module reporting the error notification.

notif_name

if present, is the entity in TCPMAN associated with the error.

Cause The cause depends on the notif_func and notif_err.

Effect TCPMAN continues to run.

Recovery Contact your service provider and provide all relevant information.

204 (Critical Event)

TCPMAN Process Abended. Error err_code, Cause reason, Line line_num, Module module_name.

err_code

is the file system error that occurred. See Appendix B for information on the specified error.

reason

indicates the reason that TCPMAN abended during initialization. The possible values of reason are:

1	An error was encountered in the system configuration database.
2	Too few start-up arguments.
3	Invalid start-up argument.
4	Specified backup processor invalid.
5	Invalid queue name specified.
10	Checkpoint error.
11	TCPMAN received an unexpected request.
12	A process that was being monitored abended.
13	An internal processing error occurred during backup takeover.

line_num

is the line number in the module where the internal error was detected.

module_name

is the name of the TCPMAN module that detected the internal error.

Cause The TCPMAN process detected an error during process initialization and it is unable to proceed.

Effect TCPMAN terminates abnormally.

Recovery Restart TCPMAN. If the process abends again, contact your service provider and provide the following:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

205 (Noncritical Event)

Master TCPMON Process tcpmon_name started on CPU cpu.

`tcpmon_name`	is the name of the master TCPMON process.
`cpu`	is the processor number where the master TCPMON process started.

Cause There was no master TCPMON.

Effect None. This event is informational only.

Recovery Informational message only; no corrective action is needed.

206 (Noncritical Event)

TCPMON Process tcpmon_name started on CPU cpu.

`tcpmon_name`	is the name of the TCPMON process.
`cpu`	is the processor number where the TCPMON process started.

Cause The operator started a TCPMON or a processor was brought up where a TCPMON was configured.

Effect None. This event is informational only.

Recovery Informational message only; no corrective action is needed.

207 (Noncritical Event)

TCPMON Process tcpmon_name stopped on CPU cpu.

`tcpmon_name`	is the name of the TCPMON process.
`cpu`	is the processor number where the TCPMON process was stopped.

Cause An operator stopped the monitor using SCF.

Effect None. This event is informational only.

Recovery Informational message only; no corrective action is needed.

208 (Noncritical Event)

Master TCPMON switched from process tcpmon_name1 on CPU cpu_number1 to process tcpmon_name2 on CPU cpu_number2.

`tcpmon_name1`	is the name of the TCPMON process that was formerly the Master TCPMON.
`cpu_number1`	is the processor number where the former Master TCPMON process resided.
`tcpmon_name2`	is the name of the new Master TCPMON process.
`cpu_number2`	is the processor number where the new Master TCPMON process resides.

Cause The old Master TCPMON was stopped.

Effect The default filter is moved to the new Master TCPMON.

Recovery None

209 (Critical Event)

No Master TCPMON Process on system.

Cause An operator stopped either the PTCPIP subsystem or the only TCPMON in the system.

Effect There is no PTCPIP subsystem running.

Recovery Restart the TCPMON processes.