IBM GC28-1982-02 Dug socket failed. Error is string, Dug Socket Select, Socket System Call

0033-1023 Ÿ 0033-1029

0033-1023 dug: socket() failed. Error is string

Explanation: The socket for communicating between the Performance Monitor and the program could not be created by dug.

Error

Class:

The socket() function failed for the indicated reason.

User

Response:

Correct

the

specified

problem.

0033-1024

dug:

socket

read

failed

string,

Node=

string.

Error

is string

Explanation:

The dug statistics collection program encountered an error reading th

from

the

statistics

gathering

daemon.

Error

Class:

The socket read() function failed for the indicated reason.

User

Response:

Correct

the

specified

problem.

0033-1025

dug:

socket

write

failed

string,

Node=

string.

Error

is string

Explanation:

The dug statistics collection program

encountered an

error writing th

from

either the

Performance

Monitor

or

the

statistics gathering

daemon.

Error

Class:

The socket write() function failed for the indicated reason.

User

Response:

Correct

the

specified

problem.

0033-1026

dug:

socket

select

failed.

Error

is

string

Explanation:

The dug statistics collection program encountered an error waiting fo

from

the

statistics

gathering

daemon

on

one

of

the nodes

being monitored.

Error

Class:

The select() function failed for the indicated reason.

User

Response:

Correct

the

specified

problem.

0033-1027

dug:

connect_dig_socket(),

socket()

system

call

failed

for

node

string.

Error

is string

Explanation:

Socket

system

call

failed

Error

Class:

The socket() function failed for the indicated reason.

User

Response:

Correct

the

specified

problem.

0033-1028

dug:

connect_dig_socket(), connect() failed

for

the

node

string.

Error is

string

Explanation:

The dug statistics collection program

did not get a response from t

Performance

Monitor while it was trying

to

write

data. dug will assume that th

Monitor

has

been

terminated and

will

terminate

itself.

Error Class: Usually because the Performance Monitor has been terminated ungracef without being able to notify dug.

User Response:	If	the Performance		Monitor	is	still active,	contact program support
0033-1029 dug:	number	unknown	commands were	received.	VT	is presumed to be	no
longer	active	and dug	is terminating

Explanation: The performance statistics collection program, dug, has received the indicated number of unknown commands and is terminating because it assumes that Performance Monitor is no longer active.

Error Class: Usually because the Performance Monitor has been terminated ungracef without being able to notify dug.

User Response: If the Performance Monitor is still active, contact program support

140 IBM PE for AIX V2R4.0: Messages